After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
v12xke said:
No, but you may be installing an app that is causing it. Try replicating the issue in safe mode. Ruling that out, if you have done a clean install using the full image (not ota) and allowed it to wipe your data there is not much more to do before contacting Google. A clean install restores your phone to its "out of the box" state. If the problem persists, it is likely hardware related. You can try a factory reset from the stock recovery... that is the first thing they will insist you do before processing an RMA.
Click to expand...
Click to collapse
I didn't have the issue on Pie and haven't installed any additional apps. It mainly happens after I haven't used the device for a while. It feels like it won't wake up so I have to hold the power button to force a reboot.
darkstar73 said:
After updating to 10, a few times a day my phone becomes completely unresponsive. Since the screen is off, I'm not even sure if the phone is powering off. I've flashed the factory image to see if starting clean would fix it, but that didn't work. Anybody else experiencing this?
Click to expand...
Click to collapse
Yes.
I was just peaking to a buddy with a 2xl and he is having the same issue since 10.
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
bobbyphoenix said:
I have an issue where after about two day of it being on it will start to stutter, and then after a couple hours it reboots itself. It's done it since 10 was released. Never had an issue on 9. Now I proactively reboot it once I notice the stuttering. Kind of sucks since 9 was super stable for me. No new apps, and no settings were changed. Just updated to 10, and it started. Kind of like memory is leaking causing it to stutter/freeze, but the last patch they said they fixed the leak. Guess not.
Click to expand...
Click to collapse
I just had a random reboot while taking my dog for a walk. Was only listening to SiriusXM. Think I'm going back to Pie until Google gets the kinks ironed out on 10.
https://support.google.com/pixelphone/thread/14074635?hl=en
Booted into safe mode last night and had to force a reboot this morning to get the screen to respond. This is definitely an issue with 10 and not an app. I'm going back to Pie since having my phone turn off every night is unacceptable, especially since my phone is my alarm clock.
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
droidstyle said:
I took the OTA before setting up my new P3XL on A10 and don't have any issues. You might try wiping data then restore apps without data.
Click to expand...
Click to collapse
I flashed the A10 Oct factory image and wiped data. Still have the issue. The only thing that fixes it is going back to Pie.
So this happened to me twice now since being on 10. My screen would go black while using the phone, and then the phone would be unresponsive, so I would need to force a reboot, but after the Google splash screen it goes into recovery, and this message shows "Could not load Android OS. You can try again, or factory reset.". I did "Try again" both times, and it booted fine. Really irks me since I can't afford to do a factory reset since I use a lot of apps that have special info in them (Like Google Auth App that has many devices I need, and resetting I would have to redo every device). I hope Google can fix these issues with the next update.
I think my issue is due to the sensor bug that was introduced in 10. I have disabled the sensors on my phone and it hasn't froze since!! Hopefully Google fixes on the Nov update.
I'm having the issue that after my screen turns off, after a certain amount of time, I cannot get it to turn back on. The phone is still on, but is unresponsive to my input. I have to hard reset.
I have tried reflashing, and tried disabling sensors. I did not have an issue with the 10 September updated, but since updating to the November update, I had the issue non-stop all day.
Platform-Tools fully updated, not using gesture navigation, but the 2-button.
@MeetFace, yes! Same here since the November update. Something isn't right.
I'm still dealing with the black screen issue. Nov update didn't fix it.
https://issuetracker.google.com/issues/143288447
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
MeetFace said:
Update, I read in a thread somewhere that disabling darkmode fixed it for one person (rando I know).
I created a tasker script that disables darkmode once the screen shuts off, and enables it when it turns back on. So far, no BSOD this morning (4 hrs)
FWIW
Click to expand...
Click to collapse
Can you share the tasker script? I love darkmode, but have never used tasker.
darkstar73 said:
Can you share the tasker script? I love darkmode, but have never used tasker.
Click to expand...
Click to collapse
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
How can you tell this is working? I've got it setup ??
MeetFace said:
Yep
https://taskernet.com/shares/?user=...uZXbuaEqxZTMoTxnDDk1yI=&id=Profile:Screen+Off
Click to expand...
Click to collapse
Thanks for this! Phone hasn't gotten a frozen black screen since I loaded the script!
Related
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
nomad4ever said:
I have the above issue with stock 4.2. Sometimes the screen goes blank (like a dark Grey back light), the phone is still on, but I can't get into it anymore. It registers touches etc, just the screen doesn't get back.
Flashed clean stock Image, factory reset and data restore.
Only battery pull helps. Happens 1 or 2 times per day in various situations (texting, browsing, whatsapp). Luckily I don't have any of the other 4.2 problems, except the missing December in Contacts. The phone is otherwise snappy as hell with 167 apps installed, recent tasks and swiping to close apps are instant.
Did anyone find a solution yet?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Same thing here, never had an issue with 4.1.2 but now it happens 2-3 times a day
Sent from my Galaxy Nexus using xda premium
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
andQlimax said:
same me..
this is really annoying..anyone tried a clean install of 4.2 to see if its get solved? im bored to wipe..
Click to expand...
Click to collapse
Let me know how that works... I have been having this problem also. Screen is blank every 2 days it happens once. Ever since 4.2 update. Before that I had no issues like this.
Also un related but I've started to notice faint horizontal lines in my screen. I use auto brightness. Is this normal or return for warranty?
i can confirm this happens to me too.
4.2 stock only rooted with custom recovery.
Same here folks, It may a bug in the 4.2 builds since Sprint did not officially release 4.2 yet.
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
same issue here, I'll try to keep the brightness to manual to see if it works
chanchan305 said:
same issue here, I'll try to keep the brightness to manual to see if it works
Click to expand...
Click to collapse
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
MondoMor said:
This happens on my GSM model. It's never been rooted, and only started doing this after the 4.2 OTA.
You can shut the phone down without pulling the battery. Press the power button once to lock (or just wait until it locks on its own). Press the power button again to bring up the unlock screen, unlock and then long-press the power button. A short vibration tells you when the shutdown menu is up, and the SHUT DOWN button is across from the midpoint of the volume rocker, so you can press it without seeing it. The display works fine when it's powered back up again.
I have a theory that the problem is related to another bug in the auto-brightness in 4.2. The display always goes to maximum brightness for a split second before going black. I have set my phone to manual brightness for the last day or so and have not seen the problem again (yet).
Click to expand...
Click to collapse
bfprd0 said:
Manual brightness didn't work for me. Everything I have read seems to lead to something wacky in source. I finally went back to 4.1.2. It hurt to go backwards,but no more issues. I'll come back when it is fixed.
By the way, I did discover that if I was at my computer when it happened, I could reboot the phone using adb.
Click to expand...
Click to collapse
I experience this issue, but not that frequent. Once every 4 or 5 days, i don't know. I've managed to pull a logcat today as i was near of pc, as posted before, adb/phone is responsive, it even locks the screen normally, there was nothing useful on dmesg. I don't normally use auto-brightness, but enabled it a little while ago, although now i'm not sure if it was enabled the first time it happened. This last time, it wasn't enabled, that I'm sure.
It happened to me both when I was using XDA-app. I have almost 0 user apps installed right now, also uninstalled XDA. Reporting back in a few.
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
ogdobber said:
the issue is related to location services
the "bug" has been reported to google http://code.google.com/p/android/issues/detail?id=40140
for a temporary fix turn off services/apps that track you e.g. latitude
Click to expand...
Click to collapse
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
bk201doesntexist said:
huh... i also don't have location services active nor gps. i never do.
and, in our case, the phone is still on, it doesn't reboot, just the screen is black. it's not the same issue.
edit: if i manage to hit it again, my next step will be unroot. full stock.
Click to expand...
Click to collapse
ok...star this issue https://code.google.com/p/android/issues/detail?id=40019
I've only noticed this since running the August security updated and its happened across three ROMs so far (Screwed, Pure Nexus, LOS (No gapps)). Sometimes the screen takes for ever to power up. Once it is up the lock screens responsiveness varies greatly. Not always in the same instance as the screen issue but when unlocking the device it will momentarily freeze. Sometimes locking itself again..
Curious if anyone has seen anything similar.
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
jhs39 said:
How are you restoring your apps when you flash a ROM? If you restore them from a Google cloud backup you could be restoring corrupted data that is causing the problem. I had that happen when a utility app completely screwed up the scrolling on my phone. I did a factory reset but restored my phone from a cloud backup and the problem came back exactly the same. The next day I did another factory reset but set up the phone as new and manually downloaded my apps from the Play Store. This time the problem was gone.
Click to expand...
Click to collapse
I'm restoring from tibu.
pcriz said:
I'm restoring from tibu.
Click to expand...
Click to collapse
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
jhs39 said:
I'm not sure if that could cause the same problem but presumably you are restoring app data along with the apps so it might be possible. Have you tried using the phone in safe mode to see if the problem still persists? It seems unlikely that what you are experiencing is a known issue with the August security update since we are more than halfway through the month without anyone else reporting a similar issue.
Click to expand...
Click to collapse
It's happened without any apps installed as well. I haven't tried safe mode yet no
are you using immersive mode?
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
pcriz said:
On screwed rom I was but I am getting it on PN and I don't run that rom in immersive mode.
Click to expand...
Click to collapse
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
diabl0w said:
I run the O preview and immersive mode causes that for me... I'm sure the custom roms are pulling commits that include this bug
Click to expand...
Click to collapse
Yeah that would make sense if you are seeing the same thing. I may jump back to a known good build and see what happens
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
pTeronaut said:
I had a very similar issue with tremendous lag in screen on and unlocking.
It turned out to be Kernel related, I was using Kirisakura Harmony Kernel, while it was happening to me, I flashed Franco R8 kernel and all is well.
Click to expand...
Click to collapse
Thank you, I'll try that!
diabl0w said:
are you using immersive mode?
Click to expand...
Click to collapse
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
p1r473 said:
So I was experiencing REALLLY SLOW screen turn ons. Like it could take 30+ seconds. But the phone was awake as my LED was on, and fingerprint haptic feedback.
When looking for solutions, I found this post. I use Auto Hide Soft Keys, to hide my status bar and nav bar when I dont need them. When disabling (and even after re-enabling), the problem was fixed (for now anyways)
Can you elaborate on this post? Do you have some experience with nav bar hiding causing slow screen turn ons?
Click to expand...
Click to collapse
Check this thread. ?
https://forum.xda-developers.com/pi...e-problems-t3666479/post73629247#post73629247
I need some help guys. I received the OTA update from Sprint with my stock firmware and it totally made my phone unusable. It keeps freezing and then rebooting. I have tried everything i can think of but nothing helps.
I did i full factory reset about 3 times. 2x with the zerolemon battery i was using for the last 2 years. Then another factory reset using the stock battery that came with the phone, which didn't get used more than about 5 recharge cycles before I replaced it with the zerolemon one.
After that I thought i could undo the patch but as you guys know the QI5 firmware is not backward compatible so am i kind of screwed? I have tried rooting and loading a custom rom, the CMDMOTO is the only one I tried since it seemed to work for others using the Qi5, but i still have the same issue.
I am a bit new to the rooting world but i have been reading up to figure out my problem, any suggestions? I have TWRP, super user and titanium backup.
Thanks
Work around FOUND !
Installing the app 'Wake Lock' and using level 4 'PARTIAL_WAKE_LOCK' seems to have made everything better. I will keep this thread updated if something else happens. I guess for some reason the last patch changed something that made the cpu go inactive or sleep much more frequently or something like that.
If anyone knows how to correct this let me know. It seems that this was actually a very common problem with the other variants of the note 4 it just took a while to get to this version. I wonder if anyone else was having this issue with the N910P.
Cheers
Have you tried booting to recovery and wiping the cache partition? If it falls asleep and freezes that points to a kernel issue if I'm not mistaken. Wiping cache will NOT delete any of your data. Hold Volume Up, Home, and power til the phone turns on and you see some yellow/blue/red text in the upper left corner then release. Try wiping cache and see if it helps
lazy_dingo said:
Have you tried booting to recovery and wiping the cache partition? If it falls asleep and freezes that points to a kernel issue if I'm not mistaken. Wiping cache will NOT delete any of your data. Hold Volume Up, Home, and power til the phone turns on and you see some yellow/blue/red text in the upper left corner then release. Try wiping cache and see if it helps
Click to expand...
Click to collapse
When I did the factory wipe from the 3rd time onward I always wiped the cache and all other options that were available. As long as i keep the wakelock app active the phone does not freeze up and/or shut down but it is draining my battery pretty fast. I am thinking it has something to do with the phone going to deep sleep and unable to come out of it properly. I am playing around with 'Kernel Auditor ' to see if i can find a setting that will fix this issue. I am almost convinced it has something to do with the cpu clock states and Deep sleep not working correctly anymore.
I personally am a fan of 3c Toolbox for most of my diagnostic needs. Theres a free version available, check under the cpu manager tab for whatever info is relevant to you. Example..it will tell you live cpu frequencies/load, live power usage, wakelocks, all sorts of goodies
Have you tried to ODIN a factory .tar image?
sammobile dot com has the QI5 image. Just make sure tou grab the sprint one and not the unknown carrier version.
maluconfusion said:
Installing the app 'Wake Lock' and using level 4 'PARTIAL_WAKE_LOCK' seems to have made everything better. I will keep this thread updated if something else happens. I guess for some reason the last patch changed something that made the cpu go inactive or sleep much more frequently or something like that.
If anyone knows how to correct this let me know. It seems that this was actually a very common problem with the other variants of the note 4 it just took a while to get to this version. I wonder if anyone else was having this issue with the N910P.
Cheers
Click to expand...
Click to collapse
Thank you so much for posting this work around! My Wife's Note 4 has been working great for over a year, she bought it used. Then a few weeks ago a bunch of updates were pushed to it and it just started to act up.
I narrowed it down to always occurring after the phone was idle for more then an hour or so and started to look for a clue if this may be a known issue so your work around makes a lot of sense.
It does appear to be an issue with Googles 6.0.1 OS version since my BlackBerry Key 1 also received a bunch of updates but its fine.
S21fe updated to UI5.
Couple of issues.... Fingerprint reader sometimes doesn't work when phone hasn't been used for some time. When it happens I need to double tap the screen to wake it up and then scan my fingerprint again.
Also "back" gesture (where I swipe up from the right bottom of the screen) sometimes instead of going back brings up the list of background apps.
Both issues very annoying.
Anyone else experienced anything similar?
Try clearing the system cache. Double check all settings. If that flaws things get more complicated...
A factory reset may be needed, but hard to say if it will resolve the issues. Someone will need to try the latter if the former doesn't work. A global reset of settings is a less drastic option but it may not be enough and still take a lot of time.
This is one reason why I spurn upgrades on a platform that's fulfilling its mission. Lol, I'm still using UI 1.5, no glaring issues.
Unfortunately with latter versions an upgrade may resolve flaws in earlier post >1.5 variants. Tough choice once you are on Android 11 as there's no roll back on stock Samsung's for that. I wasn't locked into using 11 on my N10+'s and never will load it. 12 is even worse.
Roll back is an option for you if bootloader wasn't upgraded too. Eventually Samsung will fix it if it's a firmware/software glitch but don't hold your breath for that
blackhawk said:
Try clearing the system cache
Click to expand...
Click to collapse
With each major update, I always clean the system cache from the recovery !
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
That may not be enough if going from 11 to 12, etc.
Rule #1 - if the OS is fast, stable and fulfilling its mission let it be! You have little to gain and a lot to lose. Although there was a big security hole in 12, not sure if it was patched already or if the patch is in what you just install. Oddly that hole isn't in 9-11.
Gookill is a mess...
I have the same problem with fingerprint unlocking. It simply doesn't work (if I press the side button, it works). Some hours ago I wiped the system cache and after that, I didn't notice the described problem. I will see in the next few hours.
Now I changed "Fingerprints -> Show icon when screen is off" to "Tap to show" instead of "On always on display" which was the default after the upgrade to Android 13.
UPDATE: The phone still has the same problem. Sometimes it simply doesn't allow it to unlock with a fingerprint. The screen is locked as hell. Only the side button unlocks it.
If you go to Lock screen>Always On Display>Show always, does that solve your problem? Mine was set to "show for new notifications" only and the fingerprint icon would disapperar after locking it.
Mine was set to "Show for new notifications". As you suggested, I changed it to "Show always" and we will see, how it works. In my opinion, it is better to show display only when something happens. But something changed and problems occurred.
Report: it didn't help. I have found out that the issue appears if the phone is locked for a while and then a notification comes. This is the reason why this problem exists also while using Android Auto. It creates a notification when it connects ... and then the phone can be unlocked with a fingerprint until the side button is pressed. I'm sure this is a bug that didn't exist before the upgrade to Android 13.
no such issues here with the eu version. definitely an upgrade in every way.
After 3 days with Android 13 on snapdragon variant, only two minor issues found here : slow charging (2h20 from 0 to 100, less than 2h before) and an "unauthorized action due to modified device" screen when rebooting, disappearing by touching "OK" button. Don't know what is unauthorized but... well. I was rooted before, now stock unrooted and relocked bootloader. It doesn't seems to lock something, everything I use is working.
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
d0j0m0j0 said:
I have the same fingerprint issues after updating to UI5 (unlocking from turned off screen). Sometimes it works, sometimes it doesn't. It worked perfectly before I updated, didn't change any settings. Very annoying, hopefully it will be fixed in a future update.
Click to expand...
Click to collapse
The recent update with the December security patch seens to have resolved this issue for me.
Edit: scratch that, still not fixed...
Edit2: turning off lock scrern mods in Galaxy MaxHz seems to help.
jbs68 said:
With each major update, I always clean the system cache from the recovery !
Click to expand...
Click to collapse
How does one do that?
xda-eh said:
How does one do that?
Click to expand...
Click to collapse
It's on the boot menu on Samsung's.
blackhawk said:
It's on the boot menu on Samsung's.
Click to expand...
Click to collapse
You're referring to accessing the recovery mode as explained here?
xda-eh said:
You're referring to accessing the recovery mode as explained here?
Click to expand...
Click to collapse
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
blackhawk said:
This. Some have said Android 12 needs to be plugged into the PC to access the boot menu, don't know as I run Pie and Q.
Click to expand...
Click to collapse
The link I provided and the one you did refer to the same thing. Only difference is my link also provides a way to do it via ADB. In any event, thanks for your response.
Hi Guys! I am new here, my samsung A52s 5g just freezes and always going back to home screen specially when connected to wifi. It just happened all of a sudden, I didn't even downloaded anything, I just use my phone on social media platform and some games.
Here's what I did
I tried factory reset - issue still persists
I tried hard reset, clear cache - issue still persists
I tried reprograming with Odin the latest version of Odin - still didn't fix the problem I even downgraded the android version with the old A52s firmwarw with Odin but the issuw still persists.
Does anyone encountered the same issue? And know a solution? Please let me know. TIA
Welcome to XDA
Sounds like a hardware failure.
If you did all that not much else left.
I hope someone know a solution how to fix this problem. It just happened all of a sudden. The phone was working fine beforw my son just turned it off. When I turned it back on it freezes wherever I go and going back to homescreen by itself. It happens all the time when the wifi is on. But when the wifi is off, it is somehow ok.
Well leave the wifi off. You went back to a known good firmware version and set the data user partition to its default settings. Unless you installed a buggy 3rd party after that there's not much left other than a hardware failure.
Data user partition should be in default settings I guess since flashing to known good version.
Wilsaryu said:
Data user partition should be in default settings I guess since flashing to known good version.
Click to expand...
Click to collapse
You did a factory reset as well.
blackhawk said:
You did a factory reset as well.
Click to expand...
Click to collapse
Yes sir!
Sounds like you're having the same issue as me: https://forum.xda-developers.com/t/a52s-randomly-rebooting-freezing.4503129
When this happens, do you see the Samsung logo that you normally see when you turn on your phone?
Stonos said:
Sounds like you're having the same issue as me: https://forum.xda-developers.com/t/a52s-randomly-rebooting-freezing.4503129
When this happens, do you see the Samsung logo that you normally see when you turn on your phone?
Click to expand...
Click to collapse
Yes, restarting phone is fine like normal, but whenever I browse on my a52s it keeps lagging but when press the return/back button it goes back to normal but when I repeat browsing the same thing it keeps lagging, sometimes it freezes and going back to home screen.
Wilsaryu said:
Yes, restarting phone is fine like normal, but whenever I browse on my a52s it keeps lagging but when press the return/back button it goes back to normal but when I repeat browsing the same thing it keeps lagging, sometimes it freezes and going back to home screen.
Click to expand...
Click to collapse
What browser? Try clearing that browser's data.
Try a different browser like Brave.
Google chrome browser but not just on browser also in every app. Even in Settings it keeps freezing and going back to home screen
Wilsaryu said:
Google chrome browser but not just on browser also in every app. Even in Settings it keeps freezing and going back to home screen
Click to expand...
Click to collapse
That's likely a hardware failure of some type probably the mobo.
Hello guys! My A52s is now working in properly, no more freezing/lagging. What I did is I drained the battery to zero and had it fully charged then I saw an update from android 12 to android 13. Voila my a52s is back to normal like new . Thank you guys for your time to reply. God bless us all
Wilsaryu said:
Hello guys! My A52s is now working in properly, no more freezing/lagging. What I did is I drained the battery to zero and had it fully charged then I saw an update from android 12 to android 13. Voila my a52s is back to normal like new . Thank you guys for your time to reply. God bless us all
Click to expand...
Click to collapse
Time will tell. I find that disconcerting. Did Samsung release that model with that big of a glitch in the firmware for some models of that production run? Yes, well... that's Samsung.
I've had this issue. Sent it back for warranty claims and they sent me a replacement unit, Initally I though GalaxyMax Hz caused this issue - so I haven't used it again.