Related
s3 turning off randomly requiring battery pull to restart. here is the breakdown to date problem occured,verizon tech sent replacement phone, that phone did it so sent it back and kept original phone, replaced sims card, problem still there, replaced battery, problem still there replaced phone again, still there, replaced sims card and battery again,guess what phone is still shutting off randomly, stock rom,factory mode (no apps)nothing not even email linked all software ota up to date. all is documented by verizon and and sumsung but everytime i talk to them all i get is the same old we can send you a like new phone after all the resets and ect., i dont want another s3 that is reman wich i know does they same thing and i didnt really want to exchange what i thought was the best for a droid wich verizon wants to do and sammy wants to send reman. i have already had two other reman phones that do the same thing. now here is the kicker i own 3 total s3's and now guess what one of the other is doing it now too. is there anybody else having this problem? is there a way to track what is running when it shuts down?would a different kerrnel help? would a different rom help? could this be my account with verizon? any help at all i dont know what to do?
more info
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
coop245 said:
i am starting to think this is a problem with the screen not waking up and staying dark and not necessarly shutting down. any ideas on ways to check this?
Click to expand...
Click to collapse
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
prdog1 said:
Try another rom although it sounds like an app. Can't be the phone on that many of them. You only one reporting this problem so has to be something you are putting on phone.
Click to expand...
Click to collapse
both phones are doing this on stock. no apps installed
My friend had 8 replacements through verizon before he got a good one. So try a couple more times maybe. I know it is really inconvenient but honestly the GS3 is the best Android on Verizon right now (arguably atleast) and they probably won't let you trade up to a Razr HD Maxx which is the only one I would recommend.
I'm having the same problem apparently. I just bought this phone used and activated it monday night. That night, i plugged the phone into the charger while i slept and the phone shut off overnight. Phone wouldnt turn on with the power button - required a battery pull to restart.
Going through tuesday, the phone worked fine. However, in the evening, the phone was idle for a few hours, and when I went to check it before going to bed I found it had powered off again! Required another battery pull to restart...plugged it into the charger, and went to sleep. When I woke up, I again found (for the third time) that the phone had powered down, and required another battery pull to restart.
Going into wednesday, phone is working fine. Then I leave it idle in the afternoon for a few hours during work, and when I get ready to drive home, I find it is again powered down, requiring a battery pull to restart (fourth time in less than 2 days).
Now I go to visit verizon, and the rep tells me (after I think he was looking through some company forums for answers) that I should try clearing the cache from every app, since maybe the data was corrupted during my OTA update to JB (which i installed monday night), and some app was causing this problem. So I do that, and the same thing happens again overnight...battery pull etc...
I'm figuring next I'm going to do a factory data reset, possibly tonight. This is supposed to be my sister's christmas gift! Hah...trying to work the bugs out before tuesday. Any thoughts?
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
KjK89 said:
Starting a post with I'm not crazy sound like something a crazy person would say.... just saying.... But I agree with the earlier post that it could be app or rom based and only effecting the screen. These are the options I see you having:
1. Try freezing any apps you've installed one at a time and see if it stops
2. Make nandriod and try another rom and then come back if that doesnt fix it
3. Try this thread to clear everything and upgrade http://forum.xda-developers.com/showthread.php?t=1984436
-This method formats internal and external sd card AND bumps you up to rooted JB in the process. Use VRBLK3.
4. Get a replacement phone
Click to expand...
Click to collapse
These options might work for the OP, but only #4 could work for me since i'm not rooting this phone (its for my sister). If I find a fix for my issue, i'll post here.
Are you guys using an sd card? If so it might be a corrupt file that the system goes over and gets stuck on, messing the cell up. Did you try making a backup on pc, formating your card (fat32) and putting you stuff back on it? Or take the card out and see if you get the same problem without it. If you're going thru all the replacements then its gotta be something that you use in common with all of em. GL!
i have a LTE device (s-off, rooted, stock, 4.2.2) which is working great, only one annoying issue: sometimes, maybe once in two weeks, my device just turns off during charging at night while i sleep. i couldn't guess the reason for this strange behavior so far, but it can be really annoying, since i depend on the alarms set. it was the same when i was still on android 4.1.2.
is there a way, a log hidden somewhere or something to help me track the issue? anybody?
thanks!
Could the reason be, that it is getting hot and shutting down to prevent the phone get damaged?
Have heard of such things already, so maybe investigate in this direction.
i doubt, since i've had it it's never been even warm. and this always happen at night when nothing special is happening on the device. i thought maybe it's the automatic titanium backup, but the days are wrong...
is there any special log on the device that covers reboots and crashes to look at?
Don't know about log.
If you charge it, when its happening, it can get warm after some time.
Thats the only idea i have.
yes, it's always charging when it happens.
I just got a Nexus 5 for cheap, advertised on eBay as "Battery Drain Issue", I looked into it, found a few fixes, figured for the price, I could get my money back in parts so I bought it. Now that I have it and have used it for a week it quickly became my daily and I want to keep it so now some of the "bugs" are problems.
Battery Drain Issue
Obviously, there's a battery drain issue, first off, when I got it, booted it, it had a little unlocked lock under Google on boot, so I know it was tampered with, next that gave it away was it had Android 5.0.1 on it, downloaded root checker, no root, but some how SuperSU was installed as a system app that I can't delete. After some reading on here I found out this is a result of Rooted 4.4.4, and then an OTA update of 5.0 or 5.0.1 breaking root but not getting rid of system installed apps from when root was flashed. So this means even a factory reset from Settings or a wipe in recovery isn't going to get rid of SuperSU because it's embedded in the firmware itself so it'll be reflashed with it, only method is a full wipe and stock install with new firmware from Google.
So, I downloaded the 5.0.1 update from the Googles, rebooted into bootloader, plugged in USB, came up as Android with a yellow triangle on it in device manager, installed a driver I found online (not the google one from Android SDK because it didn't do anything), reads as ADB device now, ADB works, clicked the flash-all.bat, everything is going good, and then can't find system.img, did more looking into it, found a great thread somewhere on here on exactly how to make Windows 8.1 play nice with it's new friend Nexus 5, extracted the files from the zip that was in the zip from Google. Made a new batch file telling it to install the .img separate and do a full wipe and wipe cache after and reboot the phone on it's own, after it rebooted, it was at the setup screen, I rebooted back to bootloader, my batch file finished it's script by locking the bootloader and rebooting for me again, I set it up, charged it all night, next day at work I got 7 hours, had to plug it in before I left work, once it was charged after work, brightness was on full now that I'm outside and I got 4 hours.
I found a BUNCH of tips on battery life so I disabled Bluetooth, disabled GPS, disabled scanning for WiFi, bought GSAM Pro. Android System and Screen are using almost all the battery, using GSAM I found out that Android System and WiFi are actually using it all, Screen is a close third, but for some reason Android's Battery Usage under settings is hiding WiFi battery usage from me, not sure why, maybe they know of this issue and they don't want to address it yet? Android 5.1 fix perhaps?
Anyway, I've been dealing with the quick drain battery issue by getting a portable battery pack, I get almost 3 charges out of it on the go if I turn the phone off while it's charging.
Bluetooth Issue
Now the next issue is Bluetooth, I tried on 3 vehicles, all of them don't work with this phone, they work with the Note 3 (sometimes) and Xperia's (everytime), but not this one which sucks because I like this one the best and want to take it with me all the time. I get nothing, it won't even connect, I even tried doing another full wipe to Android 5.0.1, and clearing all Bluetooth devices from my headunit so only the Nexus 5 was the option it was trying to connect to.
It finds the device, says Nexus 5 and then a randomly generated number, same number appears on the phone so I tell it it's correct, tell headunit it's correct, tries to connect, phone asks if this is a trusted device, I add it to trusted devices list, wait about a minute, and then it fails, every.. single.. time.. I even tried leaving the trusted device thing to see if it connects first and it fails, and if a decline trusted device, it fails instantly. So I know the trusted device aspect is working, it just won't pair.
Aesthetics Issue
The 3rd and 4th "issues" aren't really problems, it's more like coping with OCD because I want a round battery icon with the percent in the middle on the statusbar, and the only way I know how is root, xposed, and gravitybox. The only issue with this is with the bootloader unlocked, I get to see a gross unlock icon on boot every morning which ruins the nice minimalistic look and that's one of the reasons I absolutely love this phone. If I could find a way to unlock bootloader but hide that unlock icon on boot I would be set. But I haven't found a way to do this yet. So for now, this is something that bothers me about the device is I can't make it look pretty, without making it look ugly, kind of a catch 22..
Now I just copied over my batch file to have the correct file names for 4.4.4 which I just downloaded from Google and I'm going to revert back to that, disable the update notification telling me I need the lollipops, and use that for tomorrow to see if any of this improves, but, keeping in mind, I would prefer to be on Android 5.0.1, the eye candy is very appealing to me for using this over the Xperia Z
I'm mostly just going back to 4.4.4 to see if Bluetooth works and if battery life improves so I can narrow it down between either device issues or firmware issues.
I know it's a lot to read, but I didn't want to make 3 separate threads
Any help would be greatly appreciated, I'm new to Nexus and really don't have a clue what I'm doing lol
I'd say it's worth opening the phone to see if the hardware has been tampered with. If I'm not mistaken, the battery cover has a bluetooth sticker sensor on it near the rear camera hole next to the flash.
Also, the battery may have been abused by leaving the phone charging after reaching full capacity. I know there have been articles/forums that insist it wouldn't degrade the battery but it sure killed the battery on my Logitech G930 headset. I try my best to take care of my battery powered devices and i see a noticeable difference.
VeeDaub said:
The only issue with this is with the bootloader unlocked, I get to see a gross unlock icon on boot every morning which ruins the nice minimalistic look and that's one of the reasons I absolutely love this phone. If I could find a way to unlock bootloader but hide that unlock icon on boot I would be set. But I haven't found a way to do this yet. So for now, this is something that bothers me about the device is I can't make it look pretty, without making it look ugly, kind of a catch 22..
Click to expand...
Click to collapse
There's an easy solution for this.
step 1: power on your phone.
step 2: put it down. Look away. take a sip of coffee. or anything. just don't look at the phone during initial boot up.
step 3: use your phone the way you want to use it.
or, if the unlock icon bothers you that much, and you just. can't. look. away. during boot, there are plenty of apps that will put a little circle with battery percent inside in the notification area. Without needing root or XPOSED, or anything. Power Toggles is one of those apps. I'm sure that there are many more as well.
seromba said:
...it's worth opening the phone to see if the hardware has been tampered with...the battery cover has a bluetooth sticker sensor on it near the rear camera hole next to the flash...the battery may have been abused
Click to expand...
Click to collapse
When I got the phone, it was "worked on" and the previous owner said the battery was replaced and the rear cover was broken during removal so a white one was supplied, I looked at the white one and the bluetooth/wifi antenna sticker is right beside the camera/flash but wifi works perfect, so I'm not sure if that's the issue. I flashed 4.4.4 last night and charged to 100%, it still seems to be draining fast, 5% in about 30 minutes so maybe the battery was replaced with a knock off? How do I tell if it's not official? Is there a larger capacity battery upgrade that'll fit in the stock housing/backing?
jss2 said:
...Look away. take a sip of coffee. or anything. just don't look at the phone during initial boot up.
Click to expand...
Click to collapse
I spit out my coffee everywhere lmao! I guess it's not a huge deal if it's there, and if it's scaled out, the majority of the time is spent looking at the icon I don't like rather then the momentary one I would prefer not to have.
I just like my phone to "perfect"
jss2 said:
...Power Toggles is one of those apps...
Click to expand...
Click to collapse
Power Toggles didn't work, it does put a round icon with percent, but it will only display on the left side in notifications rather then on the right with the system icons.
Thanks for the suggestion though.
I'm going to try Bluetooth to see if it works on 4.4.4, if not then there's some hardware issue that had nothing to do with firmware so if that's the case then I'll rip it apart tonight and reflow the logicboard, check for any signs of water damage and toss it back together.
This device also has a lot of LED bleed on the bottom of the display but if I push on the bottom frame of the glass, it goes away, so I'm thinking the phone was completely rebuild with cheap or spare parts.. Which would explain why it was so cheap.
Either way, I'll report back in a few hours if bluetooth works or not, I'm kind of hoping it doesn't because then it'll really narrow it down to a hardware issue.
Thanks for the help so far.
VeeDaub said:
I spit out my coffee everywhere lmao! I guess it's not a huge deal if it's there, and if it's scaled out, the majority of the time is spent looking at the icon I don't like rather then the momentary one I would prefer not to have.
I just like my phone to "perfect"
Click to expand...
Click to collapse
Don't mean to be an ass but, you get what you paid for
dicecuber said:
Don't mean to be an ass but, you get what you paid for
Click to expand...
Click to collapse
Yeah, I can tell its a cheap phone, oh well, its still my personal favorite out of the other ones I've owned.
After more testing with 4.4.4, I got 10 hours of battery life with GPS and Bluetooth on, charged again, and then 12 hours of battery life with GPS and Bluetooth off.
So, its better, but I'm still went back to 5.0.1 this morning.
Bluetooth on the headunit lastnight did the exact same thing, tries to connect, waits a bit, says failed.
I did notice another weird issue with charging it this morning, phone was plugged from 3am when I went to bed till 8am when I got up for work and turned it on, that's a decent 5 hour charge and normally it only takes about a hour to charge. The battery icon displayed full with the lightning bolt meaning charged, turned the phone on, still plugged in, shows 70% and says charged, figured it needed a minute to recalibrate the battery so I restarted, still said 70% but it said it's charging now, left it while I made coffee, came back about 30 minutes later before heading out, still said 70% and says charging. I got to work and the battery was down to 9% so I figured it needs to recalibrate so I'll let it run dead till 0%, full charge to 100%, run down to 0%, and then after its charged to 100% again use the phone as normal, nope, it got to 0% before I got in the building, its "charged to 100%" so I turned it on, 68%..
Kinda thinking I'm going buy another battery, one I know is brand new (not what the previous owner said is new) and a new backcover to see if that fixes Bluetooth.
How's the motherboard?
If you unlock the bootloader and flash a custom recovery, you can flash one of these bootloader images that change how it looks. All this does is re-skin the bootloader. http://forum.xda-developers.com/showthread.php?t=2950482
As for the circle battery icon, AICP has that option along with a lot of other options. It may even fix your Bluetooth connectivity issues with your cars (can't confirm). In the screenshot you can see the battery icon.
Sent from my Nexus 5 on AICP 5.0.2 Nightlies
procitysam;59176829All this does is re-skin the bootloader. [url said:
http://forum.xda-developers.com/showthread.php?t=2950482[/url]
Click to expand...
Click to collapse
This is exactly what I was looking for, thanks! I'm doing this as soon as I get home from work, and then root with no unlock icon, and then GravityBox LP for round battery!
As for the Bluetooth issue, I'm going to reflow the logic board, see how that goes, inspect the battery while I'm in there, maybe find an app that allows me to view battery cycle count.
Ripped the phone apart when I got home, reflowed the logic board, put it back together, tested Bluetooth, connected instantly, no hesitation.
So that's fixed, just gotta figure out a new battery, I found three replacements.
OEM LG 2300mah
X-Longer 2300mah
KBTEL 3830mah
Anyone use these or know which is best? I kinda want to try that KBTEL battery but I can't find any good info on it. I also can't find anything reiweing the LG vs X-Longer batteries either.
I just gotta figure out how to check the cycle count of this battery and if its old then I'll replace it.
VeeDaub said:
Ripped the phone apart when I got home, reflowed the logic board, put it back together, tested Bluetooth, connected instantly, no hesitation.
So that's fixed, just gotta figure out a new battery, I found three replacements.
OEM LG 2300mah
X-Longer 2300mah
KBTEL 3830mah
Anyone use these or know which is best? I kinda want to try that KBTEL battery but I can't find any good info on it. I also can't find anything reiweing the LG vs X-Longer batteries either.
I just gotta figure out how to check the cycle count of this battery and if its old then I'll replace it.
Click to expand...
Click to collapse
Glad to see you got it fixed! As the circle battery icon, I find it easier to just flash a custom ROM because xposed is kinda buggy still and a ROM like AICP has a lot of really nice features that xposed can give and a lot it doesn't have.
Sent from my Nexus 5 on AICP 5.0.2 Nightlies
procitysam said:
..because xposed is kinda buggy still and a ROM like AICP has a lot of really nice features that xposed can give and a lot it doesn't have.
Click to expand...
Click to collapse
I've noticed its buggy, it took me a few attempts just to Install, Gravitybox crashed and got the phone stuck in a bootloop, I just cleaned the cache and it started fine, haven't had any issues since it worked but the process of getting it working was something in its own.
I'll give AICP ROM a try when I get home from work, maybe it'll help with the battery issue.
I narrowed down the battery issue to WiFi. I charged to 100% yesterday, unplugged just before 1am, left everything off, battery was at 94% by 8am so it only had a 6% drain. Drove to work, had Bluetooth on and streaming google music, its all good, not a huge loss at all, actually going really well. I think I was around 85% around 11am when I realized I forgot WiFi off, turned it on, phone died just before 2pm,
So with everything off and idle, 6% battery loss over 7 hours, with wifi off it was a 9% battery loss over 3 hours, then I turned WiFi on and it was an 85% battery drain over 3 hours.
Now that that's solved, I dont think I need a new battery, I gotta find a fix for this insane WiFi battery drain.
I flashed AICP 8.0 Release yesterday along with the latest GAPPS from Paranoid Android, I used the modular GAPPS because I prefer Gallery over the "Photos" alternative from Google. Anywho, I ran into a huge issue, Chrome won't search for anything without thinking I'm a robot if I'm on Data, if I switch to WiFi it works fine. The battery life I can't really say, but I think it has something disabled or modified with WiFi because from 10pm when it got to 100%, I had it unplugged and idle till about 2am checking it once an hour and it was 99% by 2am when I went to bed. By 8am it was 98%, so there was only a 2% battery loss over night and I left WiFi and Bluetooth on, but as soon as I started using the phone, it's not even 9am yet so it hasn't even had an hour use and it's down to 82% so again there's some huge WiFi drain, but at least with AICP there's no drain at idle so I can leave it on over night if absolutely necessary.
Only other issue with this ROM is every time I boot the phone, it tells me there are 6 updates but they're all Nightly updates, I was thinking of disabling the notification but then I won't be notified if there's an official release. I do like this ROM, but the chrome issue is huge for me and AICP doesn't have their own GAPPS to use so I went with the most reliable and well known PA GAPPS but I can't search for anything when I'm not around WiFi.
I'm going to flash back to stock 5.0.1 right meow mainly because of that Chrome + Data thing being a bigger issue then battery drain because I can at least use my phone over Data and save some battery when browsing and connect WiFi for streaming videos or downloading apps but with this bug not letting me use Chrome unless I have WiFi it's going to kill my phone battery in a few hours, so I'd rather have the battery loss over WiFi on stock then require WiFi and battery drain all day.
Thanks for the ROM suggestion, it's pretty good, I like the direction of it but it's not as stable as I would like, I'm going to test it on the Xperia Z though because I do really like it, I just need to use it on a secondary phone.
Chrome issue is fixed, I used ES File Manager to remove Chrome from the System App, rebooted to recovery, wiped cashe, rebooted, installed Chrome from PlayStore, everything works fine. So its a PA GAPPS issue, not AICP. Just felt like clarifing that.
Battery life on AICP with Hybrid Kernel by @neobuddy89
Sent from my Nexus 5 on AICP 5.0.2 Nightlies
Dear all,
I am writing this post to hopefully get some help or directions regarding my issue, because I have already spent hours and hours looking on the internet trying fixes on my phone without anything working for me so far.. So I am getting a bit hopeless....
I recently got a Samsung Galaxy S6 (SM-920I model), and since the beginning i have been shocked by how CRAPPY the battery life was. To give you some ideas, my phone loses around 3-5% of battery per hour when idling and screen off, meaning I am not doing anything at all with my phone. Overnight, I lose about 15-20% battery with my phone on airplane mode, power saving, or whatever else you want, when it is not doing anything at all..
I know that my problem is a deep sleep problem, quite easy to identify i guess, so I have spent a lot of time reading and trying to fix it by myself but so far nothing worked.
To give you some background, after unpacking the phone I quickly upgraded Android from 5.0 to 5.1.1, so I cannot tell how it was working at 5.0. It is only after that I saw that a lot of people have issues on 5.1, but it is strange because just before having my S6, I was having a OnePlus One on 5.1 and I didn't have such battery problems and everything worked fine except turning off the "keep awake" setting option for GooglePlayServices.
What I can say though, is that since I upgraded I never had so much difficulties trying to fix a problem on any Android phone than before. Basically, since day 1, my phone never went a single time into deep sleep mode.
So far, to fix this, I tried all the following:
- Reflash the stock firmware (Samsung 5.1.1) --> many times, with full Cache/davik wipe and factory resets
- Root my phone using UniKernel
- Install custom ROM (I am running XtreStoLite version 2.2) + all kinds of wipe/factory reset
- Flash different kernel that are shipped with the ROM (there are 5 different ones if I remember)
- Use my phone with only stock apps (to see if the problem comes from one of my apps)
- Cold reboots
- The "DeepSleepFix" using the Android terminal as described here: http://zidroid.com/fix-battery-drain-and-deep-sleep-issue-on-galaxy-s6-and-s6-edge/
- And desperately, try to use my phone normally for now
Overall, I would say that my battery would last roughly 15 -20h in total with normal usage, not even heavy, which quite sucks..
I can show the no deep sleep issue to you with some screenshots (cf. below) , I have tried many applications to try to find the root cause such as:
- WLD
- 3C CPU
- BetterBatteryStats
- GSAM
etc.
I am monitoring my phone closely for the past 1-2 weeks and so far I have never seen it being in deep sleep at all (at least more than 0.2 seconds in total..). Also, when I check on the default Battery menu of Android, after a full day I would usually see "Android OS" on top and using 20-30% of the battery at least.
The problem seems to boil down to a process called "LHD" in the kernel wakelock. This is keeping my phone awake 100% of the time, whether I am using the phone or if I am not. However, even with this info I tried to search online and I cannot find anything about "LHD", so I am really stuck right now.. Do anybody knows what it is and why it is a problem for me?
If any of you have a solution or can give me some guidelines to help me fix this issue, I would really appreciate any help. If you need more information from me also let me know.
Thank you for taking the time to read me,
Best regards.
I have G920I too and solved my problem using deepsleepfix and taking out the GSM CHIP e put into phone again. Looks ridiculous and no sense, but worked for me...
OBS.: In BetterBatteryStats my kernel wakelock was GPSD.
Hope this will help you
I have G920I too and solved my problem using deepsleepfix and taking out the GSM CHIP e put into phone again. Looks ridiculous and no sense, but worked for me...
OBS.: In BetterBatteryStats my kernel wakelock was GPSD.
Hope this will help you
thiagomed said:
I have G920I too and solved my problem using deepsleepfix and taking out the GSM CHIP e put into phone again. Looks ridiculous and no sense, but worked for me...
OBS.: In BetterBatteryStats my kernel wakelock was GPSD.
Hope this will help you
Click to expand...
Click to collapse
Hi, thanks for your reply.
You mean you took out the GSM chip and flashed the phone using the DeepSleepFIx.zip file, and it worked? I already tried the deepsleepfix and it didn't work for me, but I didn't remove the GSM chip.
I can try that.. even though it is strange.
I just flashed the deepsleep and then took out GSM chip
Ok thanks thiagomed.
I tried what you did.. I flashed the DeepSleepFix.zip without my SIM in the phone, it changed nothing.
I also removed it and put it back later on after flashing again just to try. The problem is still there.
I really don't know what to do anymore.. Thanks for your help tough.
ImPain said:
Ok thanks thiagomed.
I tried what you did.. I flashed the DeepSleepFix.zip without my SIM in the phone, it changed nothing.
I also removed it and put it back later on after flashing again just to try. The problem is still there.
I really don't know what to do anymore.. Thanks for your help tough.
Click to expand...
Click to collapse
Have you tried a factory reset and not installing any of your apps? Maybe it's an app keeping the phone awake?
LNJ said:
Have you tried a factory reset and not installing any of your apps? Maybe it's an app keeping the phone awake?
Click to expand...
Click to collapse
As specified in my post, yes.... even when I was running the stock Android 5.1.1 with no other apps than the ones comming with the fresh OS installed, I already experienced this issue.
The problem is the process LHD in Android Kernel that is running all the time, phone on or off, and draining my battery.
I cannot find any information on this process and how to fix my issue...
Can this issue of never going into deep sleep at all (I mean I am always at 0s...) be a reason for going to Samsung support and ask for a replacement ? I find other people having no problem with their S6 and mine I tried so many things and nothing fixes my deepsleep issue... Getting sick of this phone.
ImPain said:
Can this issue of never going into deep sleep at all (I mean I am always at 0s...) be a reason for going to Samsung support and ask for a replacement ? I find other people having no problem with their S6 and mine I tried so many things and nothing fixes my deepsleep issue... Getting sick of this phone.
Click to expand...
Click to collapse
You could fix this? I have the same problem .... Thanks
superchizo said:
You could fix this? I have the same problem .... Thanks
Click to expand...
Click to collapse
Yes, after some time and a lot of trouble. I tried everything on the software side and nothing could fix it (flash, re flash, clear cache, reinstall other ROM, apply deep sleep patch fix, etc.). Nothing WORKED.
So it had to be a hardware issue.
I went to see Samsung and I had to argue with them several times showing them screenshots of my phone never sleeping over time, because they were not believing me and trying to say that this is normal..
They changed my battery first, and the problem was still there.
I went back later on to show them again, then they finally changed the whole motherboard of the phone (which includes the CPU as well) and since then everything is working as intended. My phone is now in deep sleep about 70-90% of the time depending on my usage.
To convince them to change my CPU, I had to show them stats of the same phone (S6) from one of my friends which shows the amount of deep sleep he has during the day, compared to mine which was zero. So that they cannot bull**** me it was the "normal behavior" .
Basically I did their troubleshooting job.. but thankfully in the end they manage to change the motherboard and fix this super annoying issue. Because having a phone that drains all the battery in 7h when you do nothing is really annoying.
LHD is smart feature - smart alert located in advanced features
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
blackhawk said:
If you really need that data... use a data recovery specialist. That phone, if survives the data retrieval attempt, needs to go in for repair.
You can try keeping it on the charger to see if that prevents a reboot. Even with an SD card I redundantly backup its critical data, you should too.
Click to expand...
Click to collapse
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
vinoboxer said:
Sadly, keeping it plugged in to the charger doesn't keep it on power for 24 hours - it tends to restart randomly every so often still
Well I went to an official Samsung store today in the UK - I was told that for them to fix it would involve wiping/factory resetting the phone. Losing everything (which I am not yet prepared to do).
Would rebooting to bootloader be any good? I am not good with this stuff!
Thanks
Click to expand...
Click to collapse
Try chilling it down to 50F, see if that helps.
Never attempt to charge an Li near or below freezing though. Bag it before you chill it.
The screen lock complicates everything. Files are encrypted so you need those encryption keys to access data. Way beyond the level I could troubleshoot. A data recovery specialist is your best shot. They may need to remove the chipset to access the files. Fees are around $800.
You can keep trying, get it into safe mode if possible. I never use a screen lock as you are the one most likely to be locked out, sometimes through no fault of your own. Having lost a 30yo database that's not recreatable myself, you have my empathy. Sometimes all you can do is learn from your mistakes... and not repeat them.
vinoboxer said:
Hello all,
First post here and hoping someone can help me!!
I got a Samsung S22 ultra back during launch this year (Feb or March time?) and it's an awesome phone but unfortunately, over the last few months it's begun randomly restarting/rebooting itself on it's own accord (I remember checking and I have no settings ON to make it do this). It was mildly annoying and to be honest, I just persevered and didn't do a factory reset back then which I probably should have in hindsight...
Fast forward to this week. I am out walking the dog and my battery drops to 5% and the screen darkens in an attempt to conserve battery. I think in this time I have somehow maxed out my screen unlock attempts to the point that it now says 'Try again in 24 hours' which I thought would be fine if it wasn't for the fact that every time my phone randomly restarts itself, it also restarts the 24 hour lock period.
Essentially, I am indefinitely locked out of my phone and unfortunately remote unlock is off. Why oh why I do not know but I am kicking myself.
Basically, is there ANYWAY or METHOD that anyone can help me with that would enable my phone to stay powered on for the full 24 hours? the solution seems easy enough to me, allow the countdown to reach 0 and I will be able to unlock my phone again with fingerprint/pin. I have downloaded something called 'Droidkit' from Imobie and they have a feature called system fix. Could that be installed safely to my phone and perhaps correct or update any firmware/software isssues that is causing the reset? Or is the Samsung Knox security too secure?
I am absolutely desperate as I have got no back up arranged and stand to lose nearly 2/ 3 years of photos and videos of sentimental value (wedding, honeymoon, relatives, memories etc) and it's incredibly distressing to think my only option is factory reset when if my phone COULD JUST STAY POWERED ON FOR 24 HOURS AND ALLOW ME TO UNLOCK IT.
Please help, thank you in advance.
Click to expand...
Click to collapse
you could send it to a unofficial repair store and let them check the phone, they might change the battery and check for any hardware issue or at least keep the phone on for you to be able open and backup everything from your phone.
you might lose the warranty by doing so.
i wish you the best.
All I see is you got too confident. If you have had fixed the randomly reboots when you started experiencing it this problem you have now would be easily fixed in 24 hours. Anyways, if I were in your shoes, I would try to flash the current complete firmware through Odin but flashing the HOME_CSC binary as CSC, since that one is supposed to don't wipe your data. That's what I would do (without high hopes) before doing a factory reset if that's my only option.
Try to unlock with Google's Find my phone app.
Hi, trying to boot into safe mode could potentially prevent the random reboots ONLY IF the culprit is an app.... It's worth trying anyway...
Why not factory reset in bootloader. It will trigger FRP lock but as long as you know your unlock code/password it will work fine. You'll lose your data but you'll be back in the phone
draskome said:
Why you just don't switch phone off, and leave it like that for 24 hours?
Phone doesn't need to be turned on.
Click to expand...
Click to collapse
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
simplepinoi177 said:
I'm with draskome....
I don't have a S22 and my last Galaxy S was an S5 so I doubt I know anything...but where does it say it has to be on for 24 hours straight? All the other posts on this thread seem to take that condition as a given, so maybe it's just something a non-S22 user wouldn't know.... I would think that turning it off for at least 24 hours, and then turning on & loading up the phone, the phone's internal check would find 24 hours have passed and remove the "lock" on it; and that would only need a nanosecond to confirm...
If not, what a complete oversight by Samsung! That is completely stupid requirement that it must be on for 24 hours; I would see no intrinsic value in it needing to be on for that long before removing the lock.... maybe someone can explain....
Click to expand...
Click to collapse
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
blackhawk said:
I think you're correct but maybe the OP's firmware or hardware is fubar and not following the protocol.
Got locked out of a bios like that, a hardware failure. Had I never set a password no lockout would have occured.
Click to expand...
Click to collapse
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
simplepinoi177 said:
Hmmm...I wonder...
I find it unlikely that if OP is able to keep his phone turned on (but locked out) for some time -- just not for the 24 hours straight as the phone will randomly restart -- and the phone's hardware is that "fubar" so badly that it can keep on for at least minutes (if not hours) but not be able to track or release after finding out 24 hours has passed. I might believe the "fubar" failure is that severe if the phone would crash when loading up or immediately restart when starting up -- but then OP would say "bootloop" and not merely that it "randomly restarts" -- but it seems stable enough for at least a little while....
If what you say is true in the end, then the OP probably has no hope because even stopping the random restarts might not resolve the countdown properly because the "hardware [is]....not following the protocol" regardless....
Click to expand...
Click to collapse
Don't know. Maybe if they play with it a bit... but if the lock screen pass code has been corrupted... fubar.
Always redundantly backup critical data regularly, if you have a SD card slot use it. Having a data drive many times saves the data if the phone dies. Don't encrypt it...
reflash the firmware (use home csc), boot into safe mode