I dont think im the only one with LOS after EK02, correct? Lately it almost seems worse. When i leave the 4g on all day long, I can't tell if I am experiencing a LOS until I turn it off.
For example, I was able to browse the web this morning, but when i turned off my 4g, the 3g icon never returned - so i rebooted my phone. Of course after i rebooted my phone, i'm receiving text messages that I missed during the LOS. This phone is starting to really piss me off. I was happy with it for the first few months, but now it has become a real pain. People think you are ignoring messages. My phone is completely stock, and if there is a rom that works to solve this, i'll be rooting today.
I can't say I blame you for your frustration. A new modem has been leaked called EL13 that you can get here.http://forum.xda-developers.com/showthread.php?t=1389874
People are having success flashing it on top of the stock ROM with EK02 update that you now have. I plan on trying it today.
Just my personal experiences. The only time I got a LoS on the EK02 was when i was running SetCPU and had messed with the Voltages. Once I reset Voltages back to stock rom voltages or removed SetCPU, regardless of rom my LoS issues always went away. Again this is only my experiences and in no way reflects what may be the root cause of the issue on the EK02 rom. I was clearly setting something to low for the phone to maintain service is all I was trying to point out.
I am currently having some data connectivity issues with my E4GT. I have been running the Blu Kuban rom for some time now and have been a huge fan of it, but now my phone is acting really weird (no fault to the rom at all). First my GPS wouldn't lock as I thought this was kernel related I re installed the Blu Kuban rom with both of the other kernels and still couldn't get a GPS lock. Since I use GPS daily for work I went back to my classic Epic Venum rom and the GPS worked albeit poorly, it got me through the day. When on this rom whenever I used data my phone would drop down to zero percent battery and power off, this seems to occur only over 4g/3g and not over wifi. I tried flashing multiple modems from EG30 to FI27 on a multitude of roms (both GB and ICS) and using desktop Odin, but I cannot figure out what is causing my phone to crash (which now occurs consistently). I tried installing new roms (currently on AOKP build 37) which works great until the data is used and then it crashes again. I don't think this is cause from any specific rom, and I am now fearing it is a hardware issue. To summarize GPS now works, using data causes my phone to crash regardless of the rom used. Just thought I would ask the community, any help would be greatly appreciated. Thanks!
Update: I ended up restoring to stock to see if that would fix the problem and it didn't. So I took it to the Sprint store where they discovered I had a defective battery, and it just so happened that I bought the phone a year ago today so the new battery will be covered under warranty . I will update my status upon receiving the new battery, but I am feeling optimistic at this point.
These are the two setups I have used thus far (besides full stock), and this issue has occurred on both:
http://imgur.com/EgzxWFI
http://imgur.com/FZWrdwZ
The first is on ktoonsez kernel on stock rom. The second is Slimroms Kitkat. I have been using the first much longer than the second (which I moved over to just a few weeks ago).
Basically this soft reset tends to happen when I'm driving and using the GPS most often (and I notice that's also when the phone is usually the warmest). What happens is the phone just freezes up and sits there for a bit before finally doing a vibration and starting back up to the unlock screen. Kind of like I was restarting, but not quite. If it happened in the middle of calls, somehow it would keep the call going (at least on the stock kernel, I'm not sure about the new one yet). The other person just wouldn't hear what I was saying during the "soft reset"
On the stock kernel it used to happen even when not using the GPS. It was infrequent, but occurred I would say usually when I was using the phone more heavily... mostly just random though. Sometimes it would also not happen while using the GPS. That is to say it's a sporadic issue.
On this new Kitkat kernel it happened while I was navigating recently, but has not occurred when during any other operations (yet) that I can think of. Considering that was one of the first times I tried navigating with the kernel this worries me.
Does anyone know how I could approach this problem? Perhaps some logging I could do to get to the root issue? Some firmware I should perhaps try out?
Thanks.
Sounds hardware related to me. Especially if its happening on different roms.
Then again... I just looked at you image and you are still running 4.0.4 on one. But the other you are running 4.4.4. On one or tge other you most likely have a rather large gap between your firmware build and the rom. Id try flashing full stock firmware with Odin and test for a day or two. Up to you what build you want to use, but if it were me id update to 4.3. If you go to 4.3, keep in mind there is no going back.
Hi All,
I was hoping someone might be able to shed some light on an issue I'm having. It is occurring with Franco Kernel, and it also used to happen with BluSpark, and with EX. I'm not sure it was happening on stock, as I have been flashing custom kernels since at least the Oreo betas.
Frequently when my OP5T (re)joins a public wifi (here in London it's on the Underground), it freezes and reboots. It's not every time it rejoins the network, but it is happening every day, several times. It's the sort of network with a sign in splash screen. It is driving me crazy.
Does anyone have any idea why this is? Is it likely to be a custom kernel issue (since I hear that OP custom kernels use a different WiFi solution than the stock kernel)? I don't want to go back to stock permanently since I like the SOT and the sound mods on custom kernel.
I've just flashed stock kernel again and will see if that fixes things, but I'd prefer a solution that still allows for bumping up the volume (already using V4A).
As always thank you all!
This is still happening to me... Does anyone have any idea of how to troubleshoot this. I have reinstalled stock kernel... still same problem. Dirty flashed the beta again... still a problem. It only seems to be happening with one specific (unfortunately useful) wifi network, the London Underground WiFi.
The Wifi icon gets the little circle with the 'x' in it, then the whole phone freezes. It doesn't happen every time the phone rejoins the network, but about every 4th or 5th time.
Someone has recommended factory resetting... but I'm not sure that's not a nuclear option at this point. Any idea WHAT might be causing it and is there a way to just tackle that?
help?!
Update: Found the culprit! When the phone is on a 2G network, it happens always when there is any (voice or data) communication and glitches are stronger when the signal is weaker. It's probably caused by an interference and bad shielding of components. Similarly how 2G network makes buzzing sound in radio speakers, on A52s it makes a mess on the screen.
At least one user (bellow) solved it by RMA - sending the phone to service and getting back new/fixed one.
Update 2: Problem fixed. I sent the phone to service center with description how to replicate the issue (phone must be on 2G network, ideally low signal, data or voice transfer is happening). Got it back after 2 weeks. Report says they replaced the display and also battery for "construction" reason (as they described it) and issue seems to be solved!
To conclude: It is indeed hardware issue and is fixed by replacing the display. If this happens to you too, don't wait for software update or anything else, send it to a service for a fix covered by the warranty!
Since few weeks ago, maybe since last update a month ago (security update from 1st October 2021), I'm randomly getting graphical glitches on my A52s.
It usually happens when I wake my phone after few hours of screen off but today I also saw few flashes even when playing a (graphically not demanding) game.
There is colour noise flashing over parts of the screen. It is usually just few random quick couple of 1/100 sec flashes, sometimes it stays a second and it disappears and everything is okay after that.
I also saw noise not covering the screen but flashing instead of wallpaper... Like there's a corruption in graphical memory, driver or whatever.
It doesn't make a difference whether the phone is freshly rebooted or running a week or two.
Does anybody else have this issue?
Is my phone (the memory, screen cable or something else) dying or is ist just a bug in current system update? I don't experience any other instabilities or problems.
(I'd send my phone to RMA but since I didn't find any consistent way to replicate this, it would make just as much of a difference as locking my phone in a drawer for a month.)
I'm appending mock-up screen shots how some of the flashing glitches look.
Clear system cache, hard reboot.
Huh, I didn't really ask for help, but yeah, that's a good idea with clearing the cache.
I rebooted to recovery and wiped the cache partition.
(I also accidentally hard rebooted when trying different button combos to enter the recovery LOL, so I did both things. In the end I had to enter the recovery using "adb reboot recovery" command because none of the button combos I found worked for me.)
I'll report back in few days whether it solved the issue or not.
Your screen is dying. This is hardware issue
Easy fixes are a good thing...
EugenStanis said:
Your screen is dying. This is hardware issue
Click to expand...
Click to collapse
A possibility as is a mobo failure but no harm in trying a few simple fixes first.
Samsung has been having a lot of issues with their displays this year...
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would suggest to me either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
jenda.69 said:
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would to me suggest either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
Click to expand...
Click to collapse
Factory reset. Before loading apps confirm if ok.
Then be careful what 3rd party apps you load.
If the reset doesn't work, reflash it to a known good version.
If all that fails it's likely hardware.
The most likely cause is a 3rd party app given right to overlap other apps and this 3rd party app has crashed. Uninstall apps in opposite order of installing until problem is solved. Or factory reset.
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Bvid said:
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Click to expand...
Click to collapse
So is it a hardware issue or software?
abood.mhd said:
So is it a hardware issue or software?
Click to expand...
Click to collapse
It was a hardware issue, got a new phone.
Bvid said:
It was a hardware issue, got a new phone.
Click to expand...
Click to collapse
I have the same problem, and I can't replace the phone, the question is here, will this problem increase and affect the screen more?
Same problem here...but mostly when I am on 2G network (anyone please try and post results)...Thinking of sending phone to service...will see how it goes
Huh, I didn't get notifications for my thread, so I didn't know about all the replies!
I tested different things in last few weeks and I came to the same conclusion - that it only and always happens when my phone is on 2G network. If 2G signal is strong, it's occasional small glitchy line here and there. When the signal is really bad, it just messes up the whole screen - I had my phone ringing with screen being all just noise and mess. So I guess it's probably because of interference similarly how the 2G network connection makes buzzing sound in a radio speakers. Except here it makes a mess on the screen.
Now that I know how to reliably replicate the problem, I'll back the phone up and RMA it after christmas.
i have the same problem from the first day, it happens only in 2g signal ...and only if 2g signal is weak... i sent the phone to Samsung , they inform me that they know the problem and it will be fix ..on another update ...it s software problem they told....from this day i have take 3 updates and nothing happened....the phone still have the problem
Same here, took my a52s to a Samsung authorized repair center, after 3 repairs (the third one being the display change) it seems that the problem is solved. To me, it has nothing to do with software.
So, it's a hardware issue, I face the same problem for almost 2 months, and I don't know what to do
Only solution is to contact Samsung and have it fixed
VirtualGamer20 said:
Only solution is to contact Samsung and have it fixed
Click to expand...
Click to collapse
Its not that simple...Some people send phone for repair...twice and still not fixed