Hey guys, i have question regarding the deepsleep issue that a lot of people have with the s6 edge + after root. I have searched the issue but i can't find any definitive answers (maybe that's just me?). All point to modded kernels.
I rooted my phone on 5.1.1 and immediately ran into the issue where the phone refuses to go into deepsleep. I only got half a day of battery life since then. I flashed back stock firmware with odin several times, but the the issue persisted. Since then only modified kernels have been my savior. Now on 6.0.1 i'm still having the same issue. I was hoping it was a firmware bug on 5.1.1. Obviously not. I read somewhere that it was tied to KNOX, but still no definitve answer. So my question is. Will i ever be able to get the phone back to stock and working like before root? If it is possible, how would i go about this? I will sell this phone in the near future, so i would like to sell it unmodified.
Thanks in advance guys.
Unfortunately, the only time I ran into this issue is when i updated to 6.0.1. I later rooted and installed a custom ROM and kernel, and surely enough, problem was gone. I plan on staying like this since obviously, there's a lot more benefits when it comes to custom ROMs. Logically reverting back to stock should in theory should i theory fix your deep sleep issue, if this is not the case then.....sorry.
Speedster_1 said:
Unfortunately, the only time I ran into this issue is when i updated to 6.0.1. I later rooted and installed a custom ROM and kernel, and surely enough, problem was gone. I plan on staying like this since obviously, there's a lot more benefits when it comes to custom ROMs. Logically reverting back to stock should in theory should i theory fix your deep sleep issue, if this is not the case then.....sorry.
Click to expand...
Click to collapse
Going back to stock will not cure this because you have rooted the phone.I used the TWRP recovery method of rooting and only loose around 5% overnight.
Related
When attempting to wake up device (SPH-L720) from sleep using power or home button, it doesn't wake up, gets blank screen, the menu and back soft buttons LED lights come on, hangs for few secs on the black screen, then reboots by itself. Issue happens randomly and sometimes once a day or multiple times an hour. It seems like the problem existed before rooting and installing custom ROM but I've just noticed it.
I'm using TriForce 3.0 ROM (Android 4.2.2) w/ baseband L720VPUAMDL and kernel 3.4.0-KT-SGS4-ga23d84c. I've tried wiping/reinstall ROM, reflashing back stock ROM, removing microSD card. Nothing helped. The battery charges properly and is usually fully charged. No wear and tear or damage of any kind. Device is 1 month old.
Any ideas what might be causing the problem and suggestions for possible fix?
its because of the kernal, mine does this aswell..
kyledb said:
its because of the kernal, mine does this aswell..
Click to expand...
Click to collapse
Did you find a fix? Does changing the kernel fix the problem? If so, which kernel did you go with? It's driving me crazy lol. Thanks!
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
beerindex said:
I cannot speak to whether or not, as somebody else suggested, the kernal is at fault, but I too am using KT Kernal and have this issue.
Click to expand...
Click to collapse
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
verto8 said:
Did you notice if you had the issue before rooting and flashing the KT kernel? I'm trying to narrow down the cause. I'm thinking of trying another kernel to test and see if it fixes the problem.
Click to expand...
Click to collapse
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
beerindex said:
I don't recall it happening before root, but I rooted fairly soon after getting it. I cannot remember whether it happened while it was stock rooted. As to the kernel, I flashed it immediately after installing my rom, so I would not be able to distinguish between the two as a source.
Click to expand...
Click to collapse
Same situation here. I rooted and flash a custom ROM on mine right after I got it. I believe it had the issue pre-root on stock ROM/kernel, but I'm not a 100% sure. I had same issue w/ the Cyanogenmod ROM, not sure what kernel it was using.
kyledb said:
I switched to the agat kernel and it stopped rebooting until I attempted to watch videos... So I went back to ktoonz..it is most defiantly a kernel issue as this is a known issue with that kernel I deal with it everyday and its absolutely annoying
Click to expand...
Click to collapse
Do you remember if you had the issue on stock ROM before rooting? I believe mine has always existed and might be a hardware problem because I tried different ROMs/kernels and issue persisted with all of them.
ParkerParker said:
There is a nice selection to pick from.. Agates..kt...stock....chronic..and faux ..had the same issues on KT but fixed it by UV down 15 across the board ..also for some reason 8/20 worked better for me ..but my fix might not work for anyone else..I really liked chronic..running faux now ..I hated reboots ..my phone was rebooting before I ever rooted it ..who knows my carrier wanted me to bring it in for a replacement ..decided it was time to start reading
Click to expand...
Click to collapse
Is there a comparison thread of different kernels? I'm wondering what the pros/cons of each and maybe some user experience feedback. I believe mine was rebooting as well when it was on stock before rooting. This seems like it might be a hardware problem rather than software (ROM/kernel). Do you think everyone w/ a Sprint Galaxy S4 (SPH-L720) is having this issue? If so, Samsung should do something about it because it's super annoying!
Update: I've been using latest version of KT-SGS4 kernel 3.4.59 (Aug 25 build) for over a day and it's been pretty stable w/ no occurrence of the problem. I'll keep this thread posted w/ updates if I run into any problem. Thanks to everyone for their help!
2nd Update: it still has the problem.
It's still happening but at a slightly lower frequency with the latest KT-SGS4 kernel. For those who have tried a different kernel, did it fix the problem? I'm trying to narrow down the source and convince myself for certain that it's a software rather than a hardware issue.
Same issues
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
grnerd said:
I have been a lurker here for a while, and have found most of the answers that I am looking for without having to ask any questions. For that I say thank you.
I would like to let you know that I am experiencing the same issue with my rooted SGS4. I do not recall having the issue before rooting the phone (I ran it stock for a month or so before rooting it in early July). Today I did a factory reset and re-installed Tri-Force 3.0. Here is some more info if it helps.
SPH-L720
Android 4.2.2
L720VPUAMDL
Hardware Ver. L720.08
Kernel 3.4.0-KT-SGS4-ga23d84c
I am going to try to un-root it this afternoon and go back to out of the box stock to verify it is not a hardware issue.
I am mostly posting here to follow the thread hoping for a fix.
Click to expand...
Click to collapse
Try that and odin back to stock mf9 not mdl. Tri-force is mf9 based so maybe thats why you get those issues because you need firmware kernel modem and such. Also it could be that kt kernel had been reported to cause some of those issues.
i went to a new rom and new kernal and this is still happening to me, i have no idea what it is now.... any solutions from anyone?
UPDATE: BAD MICRO SD CARD!!!!!!!!!!! REMOVED MY SD CARD AND NO ISSUES IN THE PAST 2 DAYS
NEW UPDATE: SPOKE TO SOON..
Guys I need some advise, I'm experiencing regular sod's after waking up from deep sleep. I need to force reboot to get out of it, I already tried several kernels and different ROMs but it only happens on AOSP/CM ROMs. Touchwiz ones are OK and the deep sleep is perfect with waking up from it. I am on the old bootloader though. Now my question could it be the old bootloader? Should I upgrade and trip knoxx?
I already tried to get several log's with ADB but once in a sod my device isn't recognised anymore by my PC.
Has somebody else such experiences as I really like AOSP/CM ROMs but the sod's force me to use TW.
Thx in advance.
Lucius1972 said:
Guys I need some advise, I'm experiencing regular sod's after waking up from deep sleep. I need to force reboot to get out of it, I already tried several kernels and different ROMs but it only happens on AOSP/CM ROMs. Touchwiz ones are OK and the deep sleep is perfect with waking up from it. I am on the old bootloader though. Now my question could it be the old bootloader? Should I upgrade and trip knoxx?
I already tried to get several log's with ADB but once in a sod my device isn't recognised anymore by my PC.
Has somebody else such experiences as I really like AOSP/CM ROMs but the sod's force me to use TW.
Thx in advance.
Click to expand...
Click to collapse
@MAX 404 @Lennyz1988
"If someone helps, never forget to hit thanks ? "
DeepankarS said:
@MAX 404 @Lennyz1988
"If someone helps, never forget to hit thanks ? "
Click to expand...
Click to collapse
Thx DeepankarS but should I contact them or what do you try to suggest?
Lucius1972 said:
Thx DeepankarS but should I contact them or what do you try to suggest?
Click to expand...
Click to collapse
They'll come by themselves, dont worry.
If it is just on CM/AOSP IMHO it is the bootloader issue.
Plus if your phone is a year old, you can trip knox. Eitherways you wont have warranty.
"If someone helps, never forget to hit thanks ?"
It's possible that it's because of the old bootloader, but it's also possible that it's just the rom causing it.
You could try to flash the new bootloader and see if it solves it. There is no downside to it.
I see you are from the Netherlands, so you don't need to worry about voiding warranty. You can't lose it by rooting and/or tripping knox etc.
Lennyz1988 said:
It's possible that it's because of the old bootloader, but it's also possible that it's just the rom causing it.
You could try to flash the new bootloader and see if it solves it. There is no downside to it.
I see you are from the Netherlands, so you don't need to worry about voiding warranty. You can't lose it by rooting and/or tripping knox etc.
Click to expand...
Click to collapse
Hi Lennyz1988,
I already tried several cm/aosp roms and several kernels (even stock) ones. Same issue, after waking up from deep sleep (after 3-8 hours +) the system freezes and I need to hard reset phone. I'm on TW right now and no issues. I guess it's the old bootloader, weird thing is that some other users have also old bootloader and I see no such reporting from them. I first thought it's the launcher (I always use nova) but it seemed not related. I guess my S4 sleeps toooooo deep. So unroot and flash latest stock Tom from Sammy for my country (bought the so at media markt germany) and CF root again I guess.
You had same issues?
Thx again
@MAX 404 @Lennyz1988
I tripped my KNOX and flashed latest Sammy firmware for my country (NG8) but still freeze on CM/AOSP.
Now my question could it be that i didn`t install "busybox" (from the playstore)?
Could it be that CM/AOSP ROM`s need busybox installed to function 100%?
I got a netgear router WNDR3700v1, the freeze also only happens when connected to wifi, with mobile data (3G, 2G etc) everything is fine.
Maybe "downgrade" the firmware of the router.
Sry to bother you guys, but i want to get rid of this freaking issue.
Lucius1972 said:
@MAX 404 @Lennyz1988
I tripped my KNOX and flashed latest Sammy firmware for my country (NG8) but still freeze on CM/AOSP.
Now my question could it be that i didn`t install "busybox" (from the playstore)?
Could it be that CM/AOSP ROM`s need busybox installed to function 100%?
I got a netgear router WNDR3700v1, the freeze also only happens when connected to wifi, with mobile data (3G, 2G etc) everything is fine.
Maybe "downgrade" the firmware of the router.
Sry to bother you guys, but i want to get rid of this freaking issue.
Click to expand...
Click to collapse
Hi mate,
i am not an expert on CM/AOSP roms but one thing that is common to all roms is that wifi is kernel control ,anyhow is not a common problem the one you got.
Did you try different kernels?
Did you try any wifi scheduler app to switch it on or off automatically?
Hi MAX 404, Trust me I tried almost everything. Different kernels, different AOSP/CM ROMs, even tripped Knox by flashing new boot loader. But... It seems to be solved.. I installed busybox and downgraded my router firmware. This morning I had no sod after 8,5 hours deep sleep. Or it is busybox or the downgrade of the router firmware.
Lucius1972 said:
Hi MAX 404, Trust me I tried almost everything. Different kernels, different AOSP/CM ROMs, even tripped Knox by flashing new boot loader. But... It seems to be solved.. I installed busybox and downgraded my router firmware. This morning I had no sod after 8,5 hours deep sleep. Or it is busybox or the downgrade of the router firmware.
Click to expand...
Click to collapse
mate that is great news, let us know how it goes.
I will report tomorrow buddy. Thx again
Good morning MAX 404, SOD again this morning but I froze "google search" yesterday to save some battery maybe that was the cause?
Quite sleepy device I have, it sleeps to deep. What breaks my head is that this caused only with CM/AOSP Rom's and not TW.
Lucius1972 said:
Good morning MAX 404, SOD again this morning but I froze "google search" yesterday to save some battery maybe that was the cause?
Quite sleepy device I have, it sleeps to deep. What breaks my head is that this caused only with CM/AOSP Rom's and not TW.
Click to expand...
Click to collapse
After you flash CM, do you restore anything? Don't restore anything but just try it with a clean version of the rom.
Lennyz1988 said:
After you flash CM, do you restore anything? Don't restore anything but just try it with a clean version of the rom.
Click to expand...
Click to collapse
Hi Lennyz1988, yes my apps with data with Tibu except the google ones (maps, etc) I download them from play store and no system apps. I know the drill ?
Yes, that would be my last and final step before giving up and switching back to TW.
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?
lilr said:
Hey im in the same boat as you, and was doing the same things as you, have you found a fix?
Click to expand...
Click to collapse
Not Entirely, but I found a Work Around. If I get back to Lollipop, reroot (I use TWRP and SuperSU), and then install a Custom Kernel (I've tested LeanKernel and Arter97), then it works again. I'm going to now try to reflash back to Stock Kernel later this week, and test the results.
Update: Reflashed Stock Kernel provided here: http://forum.xda-developers.com/galaxy-note-3/general/direct-download-bootloaders-modems-t3258803 (Thanks to @jcadduono , very convenient) and same issue, back to Arter97 or Lean Kernel for now. Hoping someone has a fix soon.
I just made a post. Did not see this one. I'm having the same issue
Sent from my SM-N900W8 using XDA Free mobile app
Soft brick maybe?
R2pclaw said:
I've been trying some AOSP Roms and Note 5 Roms to see what kind of features I like. I've gone back to Stock, as several Apps I like don't work in Custom and I'm due for an upgrade soon. I have SM-N900W8 (Canada\Telus).
My Back Key doesn't work and my menu button is doing SFinder stuff instead in Lollipop. Here is the messed up part. If I restore back to KitKat, no issues, but even if I upgrade to Lollipop from Kit Kat, issue comes back. I've tried OTA, ODIN Flash, and Samsung Switch\Kies, nothing. If I go back to custom ROM (Most were Darklord Note 5 base, all really good work). The soft keys work.
Be aware I'm still learning the ropes here. I even used Odin to wipe my EFT and NAND my data partition, still nothing. I'm out of ideas. Can anyone point me the right way?
Click to expand...
Click to collapse
I think this might have to do with soft bricking the device, because I updated my rooted n900w8 from 4.4.3 (If im remembering correctly) to 5.0 while still rooted and ended up softbricking it. I think. But I also had to mess around with the BL, AP, and CSC to get it working again. could it be because of that ? has anyone else dealt with this as well?
I've posted my solutions here
rocked_out said:
I've posted my solutions here
Click to expand...
Click to collapse
Thank you so much, rocked_out! that worked for me!
I rooted my phone with the correct methods as in the threads below mine, and I purposely havent updated my phone for a while, just in case the root would only work for older system versions.
I'm just curious to know if, now that I'm rooted, is it safe to update to PE1, and will it fix the Android System battery drain? I've also downloaded all the root fixes too, as well as the Debloat, so my original System Updates app doesn't work anymore.
I would love to get just some answers from the pros on this before possibly bricking or boot looping my amazing phone.
Thanks!
*bump* Hate to bump, but does anyone know this question? After flashing all the fixes, I notice my battery still kinda goes down somewhat fast when in use and sometimes a bit fast when the screen is off.
Squall429 said:
*bump* Hate to bump, but does anyone know this question? After flashing all the fixes, I notice my battery still kinda goes down somewhat fast when in use and sometimes a bit fast when the screen is off.
Click to expand...
Click to collapse
I don't know if PE1 fixes the drain but it can be rooted and downgraded if needed. Same thing for the newest PF2 firmware I have here.
I have the same problem idk what to do if PE1 fixes the battery drain I'll gladly update if not I might have to go back to stock and just stay on it unless someone can find a way to unlock bootloader so we can get custom roms (only reason I wanted root tbh)
So I can just take the update now, WHILE rooted and I'll be fine? Will I have to re-root after the update is done, or do I just continue using it as normal?
Will I have to re-flash the new fixes for the PE1 version and stuff? Since I have flashed the old NON-PE1 fixes, will this brick my phone when updating to PE1?
Does anyone know of a rooting guide specifically for the 930A? I'm not a n00b, but I'm hesitant to use methods from other variants, especially if it requires having to mine from potentially hundreds of pages.
And at this point, I'm not even sure which version of the firmware is still rootable.
still works...
General_Mayhem said:
Does anyone know of a rooting guide specifically for the 930A? I'm not a n00b, but I'm hesitant to use methods from other variants, especially if it requires having to mine from potentially hundreds of pages.
And at this point, I'm not even sure which version of the firmware is still rootable.
Click to expand...
Click to collapse
As of today 2/03/2018, the latest OTA installed phone is still able to be rooted using same old EngBoot boot but requires downgrade first. Also thought I might mention that I have not noticed any battery drain issues or lag issues that have commonly plagued the engboot method. Perhaps the OTA changed something that may have been related to whatever made the engboot cause the issues related to battery drain and lag. I don't know but phone is rooted and working better then ever using engboot.
is there a guide to get this working?
alienG0D said:
As of today 2/03/2018, the latest OTA installed phone is still able to be rooted using same old EngBoot boot but requires downgrade first. Also thought I might mention that I have not noticed any battery drain issues or lag issues that have commonly plagued the engboot method. Perhaps the OTA changed something that may have been related to whatever made the engboot cause the issues related to battery drain and lag. I don't know but phone is rooted and working better then ever using engboot.
Click to expand...
Click to collapse
Which of the many threads did you use/follow to root? If you can point me in the right direction, I *may* attempt it and if I can get it to work, I *may* write up a step-by-step like I did for my TMo S5.
Thanks.