hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Full wipe and flash rom. I'm not issue deep sleep. Full wipe sistem,data,cache,dalvik/art.....
Ivpiter said:
Full wipe and flash rom. I'm not issue deep sleep. Full wipe sistem,data,cache,dalvik/art.....
Click to expand...
Click to collapse
No. Not fixed
meysam.m09 said:
hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Click to expand...
Click to collapse
I requested respected @dr.ketan a week ago the same, but he said that he found no such issue on Nouagt.
But I'm facing it and Now you too.... You can request dr may be he can look into the issue
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
meysam.m09 said:
hi...my note 5 has deep sleep issue on android N and I've root my note with twrp but not fixed...please fix it dr.ketan :crying:
i love android N but my battery is troubling :crying:
Click to expand...
Click to collapse
install this https://play.google.com/store/apps/details?id=com.asksven.betterbatterystats and see if you really have the "deep sleep issue" because on everything stock on nougat i had no problems with deep sleep
Ijaz Farooq said:
I requested respected @dr.ketan a week ago the same, but he said that he found no such issue on Nouagt.
But I'm facing it and Now you too.... You can request dr may be he can look into the issue
Click to expand...
Click to collapse
Are you so post #06 ?
I have the same issue when I tripped my knox when I rooted my phone in MM. I had to flash a kernel when I was on MM but have not found a kernel for N yet. Now I have uodated my phone to N and the deep sleep trouble is back.
dmbOi said:
I have the same issue when I tripped my knox when I rooted my phone in MM. I had to flash a kernel when I was on MM but have not found a kernel for N yet. Now I have uodated my phone to N and the deep sleep trouble is back.
Click to expand...
Click to collapse
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Use smart switch, device initialization.
Deep sleep issues already confirmed Fix on Android N.
sunny1119 said:
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Click to expand...
Click to collapse
I did what you suggested and so far it's working fine now. ?
---------- Post added at 11:52 AM ---------- Previous post was at 11:51 AM ----------
sunny1119 said:
There is no deep sleep issue actually on Nougat. Only a few users face it. I suggest you start fresh, factory reset your device and should be good.
Click to expand...
Click to collapse
Did what you have suggested and so far it is working fine now! Thanks a lot!
I got deep sleep issue today on my note 5
Tried resetting device and flash from ordinary. Not works for me. Plz help
deep sleep issue with nougat and moto x pure?! was fine prior to 7.0 (patch level oct 1, 2017), but now stacks notifications at night but not during day. checked settings and as far as i can tell all are consistent with stay awake.
resolved
contacted motorola support. wiped cache and reinstalled nougat. seems to be ok now. first tech i talked to was not at all helpful. actually hung up on me because i was a bit slow on following his incomplete directions. second tech was helpful and resolution was quick.
Related
Hey Guys,
Finally HTC issue fix today for the ridiculous voice calling bug. For those with stock rom, kindly run software update in Setting.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Better late than never...
Ok how widespread was this bug? How did it occur because I've not had any problems at all. Sorry if I sound like a fusspot but I'm actually curious.
ss4adib said:
Ok how widespread was this bug? How did it occur because I've not had any problems at all. Sorry if I sound like a fusspot but I'm actually curious.
Click to expand...
Click to collapse
I had it with Viper 7.01.
I reverted temp. back to 5.8 Venom and didnt have it.
I read a lot of posts on it over on the Nexus 4 boards, they had it too..
Well in that case wouldn't it be classed as a Google problem? Oh well it's great that HTC have sorted it out for us at least.
tintin814 said:
Hey Guys,
Finally HTC issue fix today for the ridiculous voice calling bug. For those with stock rom, kindly run software update in Setting.
Click to expand...
Click to collapse
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?
skeleton1911 said:
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?
Click to expand...
Click to collapse
I'm waiting for this too.[emoji4]
waiting for this on developers edition.
i called HTC yesterday and they had me shut off google play framework services and ive been able to get calls since yesterday but i keep getting the google play store has stopped working msg.
Howie3045 said:
waiting for this on developers edition.
i called HTC yesterday and they had me shut off google play framework services and ive been able to get calls since yesterday but i keep getting the google play store has stopped working msg.
Click to expand...
Click to collapse
temp fix is:
look my screenshot . link
and enable the play framework services! first
skeleton1911 said:
temp fix is:
look my screenshot . link
and enable the play framework services! first
Click to expand...
Click to collapse
This fix works 100% but keeps the phone awake all the time.
smokin901 said:
This fix works 100% but keeps the phone awake all the time.
Click to expand...
Click to collapse
it shows play services yes. but it will not drain your battery.. (for me battery is fine with that fix)
skeleton1911 said:
can you upload a nandroid backup of your rom with that base..
only system partition is enough.
or do you have the ota files?
Click to expand...
Click to collapse
+1.
A nandroid backup (system partition) would be very much appreciated.
skeleton1911 said:
it shows play services yes. but it will not drain your battery.. (for me battery is fine with that fix)
Click to expand...
Click to collapse
WakeLock Detector detects that the CPU remains active and deep sleep is never achieved, so somethings up with that. I'm just going to wait it out with an older build.
Michiel0211 said:
WakeLock Detector detects that the CPU remains active and deep sleep is never achieved, so somethings up with that. I'm just going to wait it out with an older build.
Click to expand...
Click to collapse
I disabled the checkin service and Im also having a wake lock. Phone never goes into deep sleep. Is it possible to get the zip file for the OTA updates to see what is being updated from HTC? Then hopefully the ROM makers can integrate this.
That will work for root. I'm stock right now though.
Sent from my HTC One using XDA Free mobile app
Here I shared that mentioned OTA.zip. Calls work fine now. Yesterday issue appeared on my device but already today morning I got the update which fixed it.
I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu
I'm having the same problem here, confused
its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899
It's a bug of 6.0.1... Wait for small OTA or 6.0.2
Is it a bug or just an issue with custom kernels? I expect the latter.
simms22 said:
its a bug, ignore it. btw http://forum.xda-developers.com/nexus-6/help/battery-problem-6-0-1-factory-image-t3265899
Click to expand...
Click to collapse
How long do I have to ignore it? What's causing the problem?
Amos91 said:
Is it a bug or just an issue with custom kernels? I expect the latter.
Click to expand...
Click to collapse
It's not a custom kernel - its a fresh factory image install, so stock kernel.
I'd say wait for Google to push an OTA out or another factory image.
Shadester9 said:
How long do I have to ignore it? What's causing the problem?
Click to expand...
Click to collapse
cause, no idea. but i remember the M dev preview had the same issue. some were affected, some werent. id just give it a few run throughs, maybe itll fix itself?
Well, it's not the kernel, since I have the same issue with the stock kernel with 6.0.1 and LeanKernel.
This is just bad.. I can't see how long my battery will actually last
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
http://imgur.com/24jDFHQ
Yeah, I think I'm going back to 6.0. This isn't worth it.
Not only battery status messed up, the Battery tab in setting is missing as well ...
antiquezip said:
Not only battery status messed up, the Battery tab in setting is missing as well ...
Click to expand...
Click to collapse
Yeah, I accessed mine by tapping the battery icon in quick settings.
Really odd for a bug like this to go unnoticed by Google.
No issues here on a clean install (including partition trims in TWRP) of 6.0.1.
Face_Plant said:
No issues here on a clean install (including partition trims in TWRP) of 6.0.1.
Click to expand...
Click to collapse
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..
MarkPH123 said:
Nice! Mines still saying 3925% battery.. Mine was a fresh install from the Google dev images. Full wipe too..
Click to expand...
Click to collapse
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?
Face_Plant said:
That's strange. Wiping everything (including internal storage) and doing a partition trim in TWRP before flashing the image fixed it for me. Are you rooted? Custom kernel?
Click to expand...
Click to collapse
Ah I see, I was rooted beforehand but wiped everything for a clean slate.
So still stock recovery, stock kernel and no root.
Might have a go at TWRP partition trimming tomorrow when I've got some time to do it.
My battery indication shows 100%, did a clean install and no issues whatsover.
gee2012 said:
My battery indication shows 100%, did a clean install and no issues whatsover.
Click to expand...
Click to collapse
This is odd.
I did use NRT's 'Stock & Unroot' option.
It may have missed the kernel so I'll extract that and try flashing different parts of Android to see if I get any sense out of it or some sort of fix, or Google may figure it out before me (hopefully )
Shadester9 said:
I just did a no-wipe flash of 6.0.1 and then rooted with NRT and flashed LK (I had it with 6.0 too) and now my battery percentage is messed up. Keeps fluctuating in the 3000s. Any ideas?
http://imgur.com/a/90iUu
Click to expand...
Click to collapse
Congratulations man! You're battery should last a whole month without charging!!! Suh-weeeet!
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
check with better battery stats app and post Screenshots
ForcedZucchini said:
My device is constantly awake on the current build after doing a full clean flash (twice).
Something in the system is holding awake after the screen is off.
So I've tried stock OOS and CM13, and I am still getting the same wakelock so that means it is not ROM dependent, something else changed within my phone that is causing this wakelock.
I first started noticing this wakelock when I tried the offical ResurrectionRemix 7.1 from here, after flashing that ROM, I've had the wakelock on all other roms. Anyone have any ideas about how to solve this?
Click to expand...
Click to collapse
Take it off the charger.
Sent from my OnePlus 3T using XDA Labs
Try the wakelock detector app
Sent from my ONEPLUS A3000 using Tapatalk
Attaching some wakelock screenshots. These also show that it is off the charger.
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
954wrecker said:
Id format everything in twrp after saving anything valuable. Then I'd install a ROM without flashing Google apps. I wouldn't even login or sign-in or install a single app after booting up. Then see if the issue is still present. If it is gone then you know it's either your apps or Google but not the ROM or phone.
Click to expand...
Click to collapse
So here is what I've tried so far:
I installed stock OOS Recovery over TWRP. Through the stock recovery I sideloaded the official OOS 4.0 Nougat release and wiped the phone clean through recovery selecting the option (Erase everything (pics, vids, etc.)). I then rebooted the phone and completed set-up by skipping everything and no google sign in. I am still getting the constant wake issue.
I also noticed the following kernel wakelocks that show 99% and 69% usage respectively:
1. fusb301_otg_wl
2. 6a00000.ssusb
I found these threads around the wakelocks above.
https://forum.xda-developers.com/showthread.php?p=68634552#post68634552
^ This one suggests clearing cache on Play Services, I tried this and still not working.
https://forum.xda-developers.com/oneplus-3/help/otg-wakelock-problem-t3511310
https://forum.xda-developers.com/oneplus-3/help/6a00000-ssusb-wakelock-wld-bbs-t3463062
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
ForcedZucchini said:
Just wanted to update in case anyone else has this problem. I have fixed the issue.
I flashed 3.5.4 OOS and then proceeded to install CM13. I am no longer experiencing constant wake on CM or OOS.
Click to expand...
Click to collapse
Will try this. Hopefully this helps.
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
I've got already the same problem
ForcedZucchini said:
The problem has actually reappeared for me on OOS. Still not sure what is causing it...
Screenshot attached is me currently running OOS Nougat beta.
Click to expand...
Click to collapse
Did you solve the problem? I'm bored with this new phone. Thanks
Hello!
My phone doent go deep sleep randomly
BBS and kernel logs show:
-1:misconfigured IRQ 43 smp2p
-1:misconfigured IRQ 470 glink-native (!!!!!!!!! this is a main mistake)
Spoiler: previous time
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Spoiler: new time after fastboot
On any firmware / rom / kernel, stock or non-stock
I tried fastboot official rom - but problem still
It fixes only with reboot.
Pls, help me!
Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.
Bonoboo said:
Probably not in time, but will post for people googling solution.
Yes, this is common important problem which Xiaomi not rush to fix during at least 5 months. This related to modem / radio. Confirmed that changing SIM card for new from operator can fix drain but not for all.
Thankfully, @uditkarode fixed this in his έpsilon kernel.
In commit he just limits wakelock time to 250 ms instead infinity.
To install kernel you need to unlock bootloder (wait 7 days) and install TWRP.
Click to expand...
Click to collapse
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too
bodyajoy said:
still active mode randomly
Click to expand...
Click to collapse
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.
Bonoboo said:
Hmm, what wakelock shown in bugreport, same smp2p?
Also first versions of epsilon kernel till "26jul" had no fix, so maybe that was your case.
Click to expand...
Click to collapse
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it
bodyajoy said:
have no opportunity to see bugreport now
i use last version of epsilon, august
Our group (that have this problem) tried almost everything for this 5 months, every fix we found on the Enternet was tried, every custom. Last chance is crDroid + Epsilon, if it won't have problem for 1 week, our group will install it with full wipes and test it
Click to expand...
Click to collapse
Did you ever figure this out? - Having a similar problem with my Poco X3 Pro
bodyajoy said:
Thank you , i investigated that problem is modem/radio.. but no really solution
I tried epsilon + arrow, no mistakes for now, but still active mode randomly, need to reboot phone
Phone heats 43°C while talking by phone.
Some of us testing crdroid + epsilon now, 3 days without active mode, but i think that doesn't help in distance
Xiaomi doesn't want to fix that, i sent a lof of bug reports
Changing sim doesnt help too
Click to expand...
Click to collapse
Hmmmm, Are you sure about this problem?
hello, I have the soft version G781BXXU4FVI1 uploaded, and now what version of the software should I choose to download to go back to android 11, preferably 10?
you can go back as far as November 21 OneUI 3.1 update, maybe to October that year too. no further than that can be flashed as a complete firmware.
3mel said:
you can go back as far as November 21 OneUI 3.1 update, maybe to October that year too. no further than that can be flashed as a completely firmware.
Click to expand...
Click to collapse
ok Can you tell me which version to download to be correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
the earliest that should work is G781BXXU4CUH1 dated 2021-08-08
if you look at the build number I just typed, the 5th character from the end is the number 4.
any rom file for the B model with a 4 in the same exact place will flash OK because it shares the same bootloader version as we have now (#4).
As Im thinking uof upgrading to 11/12 on my G781B, @adek89 can I ask what your looking to revert..? as maybe it means I dont uprgade etc.
3mel said:
the earliest that should work is G781BXXU4CUH1 dated 2021-08-08
if you look at the build number I just typed, the 5th character from the end is the number 4.
any rom file for the B model with a 4 in the same exact place will flash OK because it shares the same bootloader version as we have now (#4).
Click to expand...
Click to collapse
ok, great, that's the answer I meant . thank you so much!
b1k3rdude said:
As Im thinking uof upgrading to 11/12 on my G781B, @adek89 can I ask what your looking to revert..? as maybe it means I dont uprgade etc.
Click to expand...
Click to collapse
I read here and somewhere else that the battery on android 12 is much weaker compared to the 10 or 11. that's why I'm thinking about uploading them,
adek89 said:
I read here and somewhere else that the battery on android 12 is much weaker compared to the 10 or 11.
Click to expand...
Click to collapse
Ok so I assume you means battery life, did you reset your battery states right after installing the new ROM? Also in that instance you can run a battery stats program and find out what app or service is using too much battery and via settings>device care>battery>app power managment> you can sleep or deep sleep the app, if you need more control, then get greenify.
And I also assume your not leaving WiFI, Data, Bluetooth on ALL the time - leaving these on when it not required will kill battery on any version of android.
b1k3rdude said:
Ok so I assume you means battery life, did you reset your battery states right after installing the new ROM? Also in that instance you can run a battery stats program and find out what app or service is using too much battery and via settings>device care>battery>app power managment> you can sleep or deep sleep the app, if you need more control, then get greenify,
Click to expand...
Click to collapse
The phone is just bought, and immediately android 12 was in it, and I only assume from reading people's posts that 12 is weaker so people say in the information. in addition, I have some my tests between 20fe and 21fe, where 21fe lasted longer on the battery. s20fe was without such strong tstow as usual use