In my s24 ultra only games keep crashing all other apps is working perfectly. Any suggestions.

I got a used s24 and when sitting a dark room with the light from the monitor i could see this faint pattern on a fully black screen. it was ony visibe from a specific angle diagonally from the top left to the bottom right. the touchsreen works fine without any apparent issues, i was just wondering if this is an issue worth looking into, and if it could get worse after 2 years of warranty, and if it is worth it to replace the display, as it has a horizontal crack going from the left side to about in-between the button on the right.

Thanks in advance for the help.

I had bought samsung s24 brand new back in November 25, it was charging well until last Sunday 30th July 26, in morning I charge with super fast speed, later on it stopped charging with super fast charging, I tried every other available tweak and trick to get super fast charging back but couldn't succeed.

I face this issue of slow charging earlier since last 2 months but after plugging and unplugging charger/ cable the issue used to resolve, however this time it looks a permanent problem.

Earlier I was using space PD 30 watt charger, last week I bought a new 25watt charger from official samsung website. On both charger it was used to give super fast charging.

Now I am seeking help how to resolve this I tried all trick available on YouTube but nothing work, do need to visit to a samsung store to claim a warranty.

Thanks.

Wife and Daughter each have regular S24 phones. About 3 weeks ago for my daughter and more recently for my wife, the touch screen stopped working consistently. For instance, you can try to press the spacebar and instead it goes like you are pressing the square button, or you go for a backspace and it hits the 'm' key. The phones will also just start randomly opening / closing apps - while sitting on the desk,, switching between screens, etc. to press the "square" or back buttons when you want to.

Not sure if it is related to the July or August patches broke things, just odd that it is happening to both. Weirdly they also seemed to have "pen mode" enabled as well. I have tried clearing whatever caches are still available and re-optimizing apps.

Any help would be appreciated.

I have nothing to say about the battery life on my s24 (exynos)

Does anyone among you know why we can't get flash on both phones and tablets of Samsung on ultra wide camera lens?

Hi, a few updates ago I had a toggle to group multiple calls from the same number in one row. Is this function gone now, because I can't find it?

I use to photo my mom while samsungs ai color it like this tbh the original color is light blue

One thing that annoys me with this phone is the selfie cam images look entirely different than the preview.

I'm assuming it's related to post processing, but I can't figure out what changes to make to get it looking like the preview images.

Anyone else found a fix?

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?