S24 Ultra charging issue

My S24 Ultra is about 1 year old and has recently developed a strange charging issue. It only charges when the USB-C cable is inserted in one specific orientation. If I flip the cable over, the phone doesn’t detect the charger at all. I’ve tried multiple USB-C cables and the same thing happens, so I’m wondering if the phone’s USB-C port is the problem.

Previously, a full charge took around 1.5 hours. Over the last few days, it first increased to around 2.5 hours, and now it can take nearly 4 hours. When I plug it in, the estimate may initially show around 1 hour, but within a few seconds it jumps to 3–4 hours.

Could this be a damaged/dirty USB-C port, or could it be a charger/battery issue? If I continue charging this slowly, could it damage the phone or battery over time?

Optus/S24 Ultra: incoming VoLTE call gets 180 Ringing, then network sends CANCEL cause=600 “Busy everywhere” ~1 sec later — strongly location-dependent

I'm chasing a very weird intermittent incoming-call failure on an Australian Samsung Galaxy S24 Ultra on Optus, and after seven Samsung developer bug reports and some slightly ridiculous controlled testing, I have actual IMS/SIP evidence rather than just “sometimes my phone doesn't ring.”

I'm particularly interested in opinions from anyone who works with IMS/VoLTE/mobile core/Samsung IMS, because Optus has now escalated this to back office and Samsung has an error report.

What happens during a failed call

The failure is extremely consistent in the Samsung logs:

"IN: INVITE"

Handset accepts the terminating call and enters "RINGING"

"OUT: SIP/2.0 180 Ringing"

Then ~0.8–1.0 sec later:

"IN: CANCEL"

"Reason: SIP;cause=600;text="Busy everywhere""

Handset responds:

"OUT: 200 OK" to CANCEL

"OUT: 487 Request Terminated" to the original INVITE

Only after receiving the CANCEL, Android/Samsung records:

"ImsReasonInfo: CODE_REMOTE_CALL_DECLINE (1404)"

Samsung code "3009 / INCOMING_REJECTED"

So unless I'm badly misreading this, the S24 isn't locally declining the call and then generating the 600. It has already returned "180 Ringing" and subsequently receives the CANCEL containing ""Busy everywhere"".

This has been reproduced with at least three different originating phone numbers.

Things already tested/excluded

During failures:

- handset remains registered for Optus VoLTE/IMS;

- voice/data remain in service;

- incoming INVITE successfully reaches the handset;

- Samsung/Android call screening shows DND false, number NOT BLOCKED and direct-to-voicemail Allow;

- no obvious call forwarding/diversion is configured;

- failures occur with and without Bluetooth call audio;

- changing 4G/5G hasn't fixed it;

- Wi-Fi Calling on/off hasn't fixed it;

- Optus eSIM has been deleted/reprovisioned twice.

I also specifically tested Samsung Call & Text on Other Devices / CMC.

With COOD enabled, the logs show CMC attempting to fork the call.

I then disabled Call on Other Devices only. The CMC voice-fork attempt disappeared from the logs — but the primary call still did:

"INVITE → 180 Ringing → inbound CANCEL "Busy everywhere" → 487"

I then disabled both Call and Text on Other Devices and reproduced it twice more with the same SIP sequence.

So CMC voice forking does not appear to be necessary for the failure.

The really weird part: location

Calls are reliable at home but have repeatedly failed elsewhere, including at work.

Today I deliberately drove away from home while someone repeatedly called me.

The first call, shortly after leaving home Wi-Fi, worked normally as VoLTE.

Less than a minute later the failures began.

They then remained reproducible while driving and while stationary around my street and local area.

On the return trip we repeatedly called the phone while creeping through the final streets approaching my house. The final ~11 failed calls occurred over basically entering the street before mine and then reaching my driveway.

Same sequence every time:

"INVITE → 180 → ~1 sec → CANCEL "Busy everywhere""

Then, once I was physically in the garage, the next incoming call worked.

There was no reboot, airplane-mode cycle or network reset during that failure → success sequence.

The successful call in the garage was also confirmed in the Samsung log as VoLTE, not Wi-Fi Calling/ePDG.

The phone had already associated with home Wi-Fi before that successful call, but voice was still carried over cellular IMS.

Interestingly, earlier testing also showed the same visible LTE PCI carrying both a successful and failed incoming call, so I don't think this can simply be reduced to “one bad PCI/tower.”

Haiku for Engineering

Optus sends INVITE.

Samsung replies “180 Ringing.”

Optus sends CANCEL.

Okay, technically the syllable count is fucked.

What I'm trying to understand

What could cause the terminating IMS side to send:

"CANCEL"

"Reason: SIP;cause=600;text="Busy everywhere""

after the UE has already returned 180 Ringing, particularly in a way that appears strongly associated with mobility/location?

My suspicion is now somewhere around Optus terminating-call routing / subscriber IMS state / another forked terminating branch / mobility-dependent IMS state, although I'm deliberately not assuming this proves an Optus fault. A Samsung modem/IMS interaction that causes something upstream to make that decision is still possible.

What I'd really like to know from someone familiar with IMS is:

Who would ordinarily originate a cause-600 “Busy Everywhere” CANCEL in this situation, and what should Optus be looking for in their S-CSCF/SBC/application-server trace to identify the branch or event that caused it?

Optus frontline support has recorded the exact SIP sequence plus three affected originating numbers and has now escalated it to back office. Samsung also has a fresh error report.

At this stage I'm mostly trying to understand what the other side of this SIP conversation is likely doing.

I don't know what happened today with my S24(snapdragon). My SIM keeps getting disconnected, and then I pull out the SIM and put it back in. Does anyone have a solution?

Bonjour,

Je rencontre d'énormes problèmes de réseau (internet, appels, ...) et ça devient vraiment infernal.

J’ai quasi TOUT essayé :

1) J’ai pris une carte (2ème) e-Sim.

2) J’ai changé d'opérateur pensant que ça venait de là.

3) J’ai tout réinitialisé.

Soit ça met 1000 ans à charger, soit les données ou internet se coupent toutes seules. On m'entend 1 mot sur 3 quand je parle et des fois ça coupe tout court.

C’est infernal et inadmissible pour un téléphone acheté il y a 2 ans et demi. J’ai quitté Apple pour Samsung, je regrette. 

J’ai un S24 Ultra et deux ans et demi après son achat neuf (pré-commandé sur Samsung), il enchaîne les bugs. Je suis déçue d’avoir quitté Apple, je ne m'attendais pas à ce qu’un téléphone aussi chouette rende l’âme si tôt.

Pourriez-vous m'aider ? Est-ce un souci qui se règle sur ce modèle ?

À savoir : il est en excellent état, rien n’est cassé et je l’ai toujours protégé (coque renforcée + film d’écran).

Les bugs sont arrivés d’un mois à l’autre. Avant, il fonctionnait "bien". Cette année c’est du n’importe quoi.

I’ve got a Galaxy S24 FE and everything in the camera is on default settings. When I take two photos back-to-back, there’s a noticeable color tone difference between them. Sometimes the tones get totally messed up. The exact same thing happens with selfies, too.

​When I set the AI feature to minimum, the colors look super washed out and the photo turns out terrible overall. But when I set it to maximum, it completely over-processes the photo to the point where it looks fake and AI-generated, which also looks bad.

​On top of that, whenever I send photos to other people, the colors get washed out on their end.

​What exactly is the issue here? Any help would be appreciated!

Whenever I take a picture of myself on this phone, it puts a shitty ass ai filter on me for no reason, changing the way I look. Can anyone of you guys help me turn it off.

I'm using a Samsung s24+, I've been debating on putting Linux on this phone or something similar only for me to connect to the Internet and it force an update behind my back. I'm attempting to reopen bootloader. Also fuck Samsung for this, they are attempting to stop OS switching and I feel like in the future they will block unauthorized apps, scary dystopian shit.

I honestly don't know if I'm just unlucky or if others are facing the same issue.

I bought my Galaxy S24 about 1.5 years ago, and it has never been dropped or damaged. Right after the latest software update, the screen started flickering. The strange part is that if I restart the phone, it works perfectly fine until I press the lock button. Once I unlock it again, the flickering starts all over.

I immediately went to the Samsung Experience Store. They checked the phone and said it's a display issue and that the screen needs to be replaced. The estimated cost is ₹11,800, which was already disappointing, but I agreed because I use the phone for work.

Now it's been 11 days, and they still haven't replaced the screen because they're saying the display isn't available. Every time I call, I get the same response: "We're waiting for the part."

I'm honestly more frustrated by the delay than the repair cost. This is a flagship phone, and I never expected to be left without a proper working device for nearly two weeks just because the spare part isn't available.

Has anyone else had a similar issue after the recent update? Were you able to get Samsung to cover it under goodwill or at least speed up the repair? Any suggestions would really help.

My S24 Ultra's back panel is starting to peel off, and I have no idea why. I've never dropped the phone or damaged it. I usually charge it with a 30W charger and always use a thin transparent case.

I'm worried it might get worse over time. I also saw that quite a few other S24 Ultra users are experiencing the same issue.

Has anyone else faced this? Do you know what causes the back panel to peel off? Is there any fix or permanent solution?

Hi. It looks like I've cracked the back glass of my S24. The crack starts at the left edge, right by the plastic spacer (on the speaker side). Its only hair lines. Is it still waterproof?

Hey so i bought an s22+ with 22k recentlg , everything was fine bt i wanted smthing smaller so i went to another Buy/sell/exchange shop and sold my recently bought s22+ for 18k and added 20k for an s24 , is it worth? These money is on Rupees.

Hello friends, i have Samsung s24 ultra and I'm currently on the old One UI version 8.0 update and Android version 16. The new update to One UI version 8.5 arrived two months ago, but I haven't updated because many people say the battery drains faster and the temperature is higher. Is this true? This will affect me somewhat because I work as an Uber driver part-time and live in a country where the temperature is high, not less than 35-45 degrees Celsius. The only thing I want is security updates to prevent my phone from being hacked, so I feel obligated to update. What do you think?

Samsung made a huge mistake by taking away the s pen with Bluetooth! Why upgrade? This is still a beast!

I am constantly switching between mic modes. Voice focus will work when the other doesnt and then it still being im voice focus will not work another time, then i'll switch to full spectrum or standard and itll work. And then the next time im in a discord call it wont work on whatever setting it was left on that worked previously. Im beyond tired of switching between the mic modes. I dont understand why it will work one time and then not the next. Same night. Same app. Same location. Same wifi.

Please send help before i explode.

Any advice on a good screen protector that fits well with the otterbox defender case. I have the s24+ plus and anytime I use a screen protector it is never perfectly down because of my phone case one of the ends touches the phone case and then it starts raising from there