Related
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
kratanuva said:
So, I recently installed an ota patch from AT&T (apparently it was supposed to make the gps more accurate or something?). Since then I noticed that my battery started draining very quickly, so I entered 'top' in a terminal and found out there was a process called 'applypatch' taking up 50% of the cpu.I can't use 'killall applypatch' because it's a root process, and apparently the update also got rid of my root.
I've already tried a factory reset, but that didn't seem to help. Also, I doubt it's still installing the patch, because I left it on all of last night and it's still going at it. The bootloader is still locked, so If possible I'd like to avoid messing with that. This is my only GSM compatible phone, and I paid a lot for it.
Should I just try rooting it again and try killing the process, or do you guys have any other ideas?
Thanks!
Click to expand...
Click to collapse
You are not the only one with that problem. I have the exact same issue. Process chewing up the CPU and if you kill it the process comes right back. Hopefully someone has a good answer as to how to fix it. I actually have 2 of the phones and one is rooted, second one is not. The unrooted phone does not have the same issue as the rooted phone.
I'm having the same problem with my Atrix. Phone is stock and unrooted. Never had an issue until I installed the latest update.
Well I got a response back from Motorola about the issue. These were their recommendations.
1. Reboot phone. Duh....
2. Uninstall any apps that you installed when the problem started. Uh, it was the OTA update... Cannot be uninstalled I do not think.
3. Clear Cache partition from Fastboot menu. That did not do anything.
4. Factory reset the phone. I hate doing that. Doubt it fixes anything but I will do it anyway.
I asked them about option 5 if 1-4 did nothing and he said call and talk to support.
Just an update...
Maybe someone knows how to just kill the process. It is obviously doing nothing as the phone is already updated to 4.5.145 according to the phone info.
I've just had a quick look around about the 'apply patch' process. Not that it helps you but this problem has been ongoing since at least android 1.6!!! Unfortunately solutions to the problem were few and far between - the main one would be to roll back the update you received (if you can).
Rooting and then trying to find the process and freezing the 'apply patch' process is another (again, I didn't find much about how to do that) as is unlocking the bootloader and putting installing a custom rom is another option for you. I know you don't feel comfy unlocking your bootloader but it isn't as bad as it sounds.
If you do decide to go the unlocking way then there are guides on here which will help you.
Edit: just seen this over in the 'general' section http://forum.xda-developers.com/showthread.php?t=2145316 ... the very same problem you are having.
Ok, just to hopefully keep this going I have tried these additional steps.
Root phone.
Unroot phone
Re-root phone
Try multiple startup program apps to kill it, none show anything besides installed apps.
None work. applypatch still taking 49% cpu
Maybe there is a way to edit androids startup config file to make it stop? Not a Linux/android guy so hopefully someone smarter than me has the answer to that.
If you've rooted the phone, you might as well have deleted or renamed that program... That's what I would do.
Same problem with my Atrix........I've been following this thread and have found a temp fix that works for me. I say temp as the applypatch process will show up again on reboot
1.) Gain Root Access
2.) Download OS Monitor from PlayStore (this will show you all processes running on Android OS)
3.) Run OS Monitor ...."applypatch" should be at the top of the list with a high Load % (Note: Under Settings enable ROOT mode)
4.) Long press on applypatch process and select kill process and allow superuser/root access...should terminate
This has been working for me so far so I signed up to share with you all.....hope it helps.
And heres to hoping for a more permanent:good: solution to this issue
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
rkohlin said:
Hope you can help me - I am desperate to halt the OTA update for my galaxy s4 -
based on everything I’ve read, Samsung did a really bad job on this update, 4.4.2, and they are currently rolling out 4.4.3 and 4.4.4, but of course, the s5 is getting it well before we are.
anyway,
I have been “happily” running 4.3 and just dealing with the bluetooth issues, found enough hacks/fixes for the wifi issue that i have been ok with it since getting 4.3 in November.
There are just too many unworkable issues of battery drain, overheating, losing apps, pics, etc etc etc for me to risk the update to 4.4.2.
HERE’S MY PROBLEM - Somehow, altho i'm fairly technical, the update finally got on my phone (after having kept it off for months) and for the past month or more, I've just been
dealing with the notification, putting it off for 24 hrs at a time.
I guess it finally decided not to allow me to do that any longer, and started the installation without permission. i stopped it by pulling the battery, but when i try to start in recovery mode just so i can clear cache and hopefully reboot without actually installing the new os, I cannot - it goes through (some of) the motions but when i let go of the power button as i should when it's running normally, and would get the options of factory reset, clear cache, et al, it just brings up the android bot and shows that it is continuing to install where it left off. I’ve done this numerous times.
Tried different methods of button-holding and other trouble-shooting based on massive searching, but always get the same result. and I can only pull the battery to stop it.
Am I stuck? Do I have to install now at this point?
I do not want to perform factory reset, guess I'd rather install the 4.4.2 s/w. (altho I can't even get to that option at this point)
Sincerely hope someone out there will respond – I've posted to multiple sites, and no one is responding - gonna have to turn my phone back on at some point soon...
Thanks in advance!!
Roxanne
Click to expand...
Click to collapse
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
stvn2569 said:
Are you rooted?
SiVisPacemParaBellum
OderintDumMetuant
Click to expand...
Click to collapse
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
THis summarizes some of the reason I don't want to update the OS - -
ack - can't post links - will have to type it out if you are interested in all the bugs Samsung saddled us with -
(most egregious is the battery drain, but others are quite serious and hard to live with too)
www(dot)androidpit(dot)com(slash)samsung-galaxy-s4-update-to-android-4-4-2-littered-with-bugs
rkohlin said:
Thanks for responding stvn2569!
Nope, not rooted.
But based on all my searching I sure wish I was and likely will the next phone.
Stock Verizon Galaxy s4 - 32gb - model # SCH-I545
(Sorry, should have put this in orig message)
Click to expand...
Click to collapse
You'll need to root the phone to stop the OTA notifications, it's all very easy.
Go to settings > security > allow installations from unknown sources, check the box
Go to www.towelroot.com
Click on the lambda, download and install the towelroot.apk
Click on "make it ra1n", reboot
Download "SuperSU" from the play store
Upon opening the app, it will prompt you to "update binaries". Do this using the "normal" option
Then download "Root Explorer" from the play store
Navigate to the system and system-priv app folders
In one of those folders you'll find "FWupgrade,apk" and "SDM.apk"
Delete those apk's and no more OTA updates:good:
joshm.1219 said:
You'll need to root the phone to stop the OTA notifications, it's all very easy.
.......
:
Click to expand...
Click to collapse
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
rkohlin said:
Thanks, Josh, I appreciate your trying to help, but if you read the original post -
I CANNOT TURN ON THE PHONE, hence couldn't get to settings if I wanted to, BUT - -
It is not the notification that is the issue -
the phone has finally downloaded the OTA update and IS INSTALLING IT. (every time I turn it on)
I DO NOT WANT THIS UPDATE INSTALLED. (see prior post for the reason - it's terribly buggy update - worse than what I have)
I have to figure out how to halt it - when I try to start in "recovery mode", it doesn't give me the options
it normally would - I won't start in a normal recovery mode.
It continues the OS update.
I noted all this in the original post - I completely understand how to get rid of the update notifications.
One doesn't even have to root the phone to do this, you can just rename the SDM apk (like add .bak or something)
Do you have ideas how to stop the installation? How I can turn phone on in recovery mode?
(note the steps I've taken to do that are also in the original post)
I know there are many people out there smarter than me about this - hoping you guys can help...,
Click to expand...
Click to collapse
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
joshm.1219 said:
My bad, I would suggest booting into download mode and flashing the mk2 tar file with odin (3.09 recommended).
I didn't suggest renaming the file because it doesn't always work. Told my brother to do that on his Note 3 (no root method at the time) and it start downloading an OTA upon reboot one day.
Click to expand...
Click to collapse
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
It is Power button click and hold volume down....
rkohlin said:
Thanks, Josh!
When you say "boot into download mode" - you mean safe/recovery/download mode right?
(like when one holds (for this model) VolumeUpButton+PowerButton right?)
If that's the case, it doesn't allow me to boot that way. When I do that, it just skips right to
"Installing system update" (with the droid bot)
That's my problem.
Cannot access anything (without allowing the install). :crying:
Have also tried VolumeUpButton+PowerButton+HomeButton. Same.
Drat.
Looks like I may have to accept this OS.
Others I know that have deal with terrible battery drain issues (from 10 hrs heavy use on charge down to 2 hrs)
Click to expand...
Click to collapse
Like he said, download mode is Power+VolumeDown, press and hold.
UPDATE:
Well, never could get into download mode, so had to accept the OS update to KK 4.4.2
Guess I'm one of the lucky ones, (I do have a fairly new model S4) and I didn't lose apps or contacts.
however,
The Battery Life is TERRIBLE after the 4.4.2 update! Some WiFi issues too.
Seem to have fixed WiFi (for now anyway)
Been searching around and recalibrated my battery, am trying a battery life extender app,
turned off a huge bunch of Samsung and Google apps that evid constantly "ping" and use battery.
It's been a little better, but not a lot.
Hope for 4.4.4 to be available soon (heard 4.4.3 is not a good variant either)
Hey everyone. redoing my thread now that we have tried alot of solutions, hopefully someone has a vague idea of what we can do to my phone lol.
So then, my phone (redmi note 3 snapdragon) refuses to go into deep sleep no matter what combination I've tried.
Tried Combos
1. RR+ radon and agni
2. Miui 8 stable and dev preview (7.1.5 and 8.1.1.0)+ stock, radon, and neon kernel (flashing using miflash with unlocked bootloader official)
3. Cm13 latest nightly+ radon, stock, and agni
4. Nitrogen os+ nagato kernel (current rom)
All combinations we're tried with clean installs (factory data, system,cache and internal storage)
Hardware methods tried
1. Physically disconnecting fingerprint sensor (goodix)
now then, with wakelock detector, we can see im troubled with a 99% awake time, along with 100,00's of event wakelocks over 6hours, now event wakelocks deal with the actual hardware of the phone from what i've seen, which makes little sense to me because the screenshot i am attaching was just over an entire night of not touching the phone. so why it has any activity is bizarre to me. so heres what we have tried so far on my previous thread.
Tried methods of fixing event wakelocks
1. Greenify, force doze, wakelock blocker and blocking everything in frustration. deep sleep battery saver.
2. physically deleting events one by one (going into dev/input/eventx (x being wakelocks 1-10) after deleting some my display eventually stopped working, most likely because i just deleted the event that controls the lcd i assume. rebooting fixed the problem and remade the events in their directory so no harm done.
3. removing zram usage figuring it was a thrashing problem (saw a thread in the hd desire of the same issue. didnt help sadly.
4. flashing modem in radon thread, ended up making my phones earpiece not work for calls and still had the wakelocks.
5. disabling gps, along with auto brightness and auto rotate
so then if anyone needs any other information just let me know, currently using an iPhone for the time being so im desperate lol. but still id rather fix and find the problem then go for returning the phone. better to solve a problem for future people in my shoes then just thrust it away is how i see it. also someone bug the strix and darkstrix about this maybe they know the solution. anyway thanks for reading and i hope we can fix my phone soon
^Update^ now using epic rom 7.1.12 from the xda thread, still got wakelocks on stock without any other apps.
I have same problem in all versions of stock MIUI Rom. I too tried all sorts of combination but the problem remains. Finally I'm using RR Rom 5.7.4 (20161113 build) + radon Kernel. My deep sleep problem have been solved (though not 100%). Now my phone looses very little battery in standby time like 1-2% over a night. Before RR Rom I tried many custom Rom but had same problem. If you have not tried the ROM (RR Remix 20161113) I've mentioned above give it a try. Best Of Luck.
Thanks rj I'll install and post logs after work. Fingers crossed that it fixes my problem.
use the rom android 6.0.1 with module powernap , u can fix it !!
http://repo.xposed.info/module/net.jzhang.powernap
Small update: testing stamina mod currently with xposed. ressurection remix will be next only because xposed seemed a bit easier lol
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Then once try nexus rom i am getting good battery life in this rom too.
rjrulz007 said:
Then once try nexus rom i am getting good battery life in this rom too.
Click to expand...
Click to collapse
surer rj which one?
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
That happens to me when background data enabled . when i disable backround data through data usage settings , the battery backup gets better, but sure my social apps wont sync.
It seems the wakelock come from android system itself , go check logcat and you will get messages like "ANDR_PERF_RESOURCES FAILED TO APPLY PERFORMANCE" , the likes of "decided to move IRQ from cpu0 to cpu1" , and the likes of "FPC listener : waiting..." , thats all that i notice and thats happening every single milisecond on every MM roms i have tried so far....
Well when i used miui 7 LL global didnt get that much messages on logcat , but its LL ...
I guess the problem is related to source code , i dont know .
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
D4xel said:
Did you try to disable fingerprint also? In many previous ROM this solved the issue.
Click to expand...
Click to collapse
yes sir still nothing
rohit4kk said:
Having same problem.. Battery is draining very fast in idle mode.. Deep sleep is not working in any rom.. Something is keeping cpu awake.... If u find any solution then plz let me know bro.. Thanks
Click to expand...
Click to collapse
hey dont worry man you'll be the first when we find an answer lol
Zaccary said:
Well damn :/ tried RR rom and still nothing sadly, also powernap with RR didn't do anything as well. both were tried with radon and agni kernels
Click to expand...
Click to collapse
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
deltatux said:
Poor network signal also can cause this issue. My old carrier had crappy signal, once I switched, it increased my phone's battery since the new network has much better signal.
Click to expand...
Click to collapse
thanks for the tip but we are running on airplane mode only at this point just to make sure we don't have more things to worry about battery drain. i appreciate the information though ^_^
Mine kenzo, tried all miui version, always the same.
sbor-si said:
Mine kenzo, tried all miui version, always the same.
Click to expand...
Click to collapse
I'm not alone!!!
Hey hopefully we find an answer buddy
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
sbor-si said:
Yesterday I want to flash 7.3.2.0 xiaomi.eu version (clean install via twrp), but get bootloop. Than I flashed official global developer version (7.1.19) (fastboot via miflash, flash all), nothing better, except android system used 6%, android 39% and dex2oat 20%.
Can somebody try 7.3.2.0 version, from earlier posts is visible, that this version rocks, all later versions have issues.
Click to expand...
Click to collapse
i believe last time i tried 7.3.2.0 it gave me constant reboots and lagged quite a bit. but i also heard it was the best for battery so i can try flashing through miflash again after work. im also going to be trying this rom here https://forum.xda-developers.com/re...nzo-lldlm18-1-3m866beta-real-factory-t3375250. since it uses edl mode instead of fastboot so hey maybe that will knock something lose?
Well, right now I'm trying to get it working - without luck. I can flash 7.3.2. with miflash via edl without troubles, phone started normaly, all seems good, until "No service" for gsm signal. Bad luck. I think that modem version from that old flash is not compatible with hardware.
But it looks so good - Android takes 20% and Android system 6%...
40$ Paypal for the person who finally helps me to solve my problem!
I have a very serious battery problem with my Galaxy S7 G930F.
Even at night when I do not use it and I turn on flight mode and energy saving mode it drains up to 10% battery per hour. When I go to bed with 60% sometimes the battery is completely discharged when I wake up in the morning.
I have had that issue for a long time now an I have already tried a lot to investigate what is causing the problem.
The first thing I tried was to completely wipe everything and reflash the official Nougat ROM. It did not help at all (I did not configure anything or install any apps! so the problem can not be caused by some app).
Then I tried both the SuperStock ROM and the Superman ROM for G930F - but the problem persistet. (I fully wiped everything in TWRP before flashing the new ROMS)
Using the App Wakelock Detector I found out that my phone is unable to go to deep sleep at all - and I also found out that the Kernel Waklocks mmc0_detect and bbd_wake_lock are causing this problem.
I have found out so far that the mmc0_detect problem can be caused by a faulty SD-Card - but I have not SD-Card installed!
The bbd_wake_lock comes from the broadcom sensorhub driver.
I have no idea what to do now, because I don't have better knwoledge to resolve the root cause of the problem.
Could it be a hardware probleme since the problem persists even with a clean install of a new ROM? I did not install any apps and the problem is already there.
Thanks for your help.
i.imgur.com/FfGOKMo.png
i.imgur.com/SEhPDeY.png
(sorry I can't post images yet)
I'm having the same problem too... I've also done the same steps that you did (factory reset, clean install superman rom, removed SD card, formatted SD card on the phone etc etc)... i'm starting to think that it's hardware problem....
the only difference I have with you is that my phone's a G930FD
Hi there....I'm running into the exact same issue. This is 100% Wifi related. If I turn off Wifi both these wake locks go away. I used better battery stats to track it.
I'm not sure what can be done to prevent it (other than turning off Wifi). Any ideas??
Thanks.
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
ardrift said:
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
Click to expand...
Click to collapse
Many times, this problem is band specific. Since every country uses a different megahertz band for their LTE service, but in this case you said there wasnt any fault before. Have you tried flashing any custom kernel like francokernel?
Yes I have tried other kernels too and it didn't solve the problem, but I didn't try francokernel on the official rr oreo build yet, I'll give it a try, thanks
I also have to add that whenever I'm connected to LTE (service, not data), the signal is fluctuating heavily. If I switch to maximum HSPA+ preferred network type, the signal becomes stable again. Maybe I should try different firmware zips, idk ?
Okay, so I tried flashing the latest francokernel (r4), have been using it for 2 days, and I don't really notice any big difference in terms of battery life. I also switched the "preferred network type" option to include LTE too, but the battery started to drain immediately. Yesterday I also found a guide (on 4PDA, as I'm trying to find a solution really hard) about flashing a QCN with the qpst tool, to unlock some LTE bands and then enable carrier aggravation(?). I just completed the whole process hoping that it would solve my issue too, but after I enabled LTE again, the battery drain came back... I can't really come up with another thing now, but I'll keep searching for it.
Could anyone please share a full (without apps and data of course) backup from TWRP to see if I can restore my EFS partition successfully? Maybe it would solve my problem as I think it is related to some sorts of modem things, and as I have explained it may be a low-level problem.
Thank you in advance!
I took the time to save and search through the logs of my device, I'll attach it to the reply. This is a log taken from the phone as it was in "safe mode", just to exclude all the unnecessary logs from third-party apps, as I experienced that they don't influence the draining of my battery. As I observed, interesting parts are around line 2365 and 4494 from point of view of the phone service, SIM card, and things like that. Also, it's another interesting thing that until the 184th line, the date is way back in november, and as I looked back, it is 4 days before I wiped my EFS partition, because the phone didn't boot then. I don't know if it is connected to my issue somehow, I just noticed it. After that, until the 1886th line, the date is 2-24, when I flashed installed my current rom, and it may be a bug with the rom itself that the date switches back to the initial installation's time, it may not have anything in connection with my main issue. I would be very thankful if someone else could get something valuable out of it. Also, an EFS backup from TWRP may solve my issue... Thank you in advance!
Hey,
Any solution for this issue ? My case is the same with Lenovo z6 pro.
After accidentally erasing my imei, and flashing it back I have idle drain.
Thx
Hope some one will replay to this 'old' thread.
ardrift said:
Hi everybody, I decided to post my problem here, after not being able to find a solution on my own.
I'm experiencing the same issue as mentioned in some other threads: [1] [2] I have the drain since I wiped my EFS partition, because a corrupted twrp backup (it was a bug in a certain version that it made faulty backups) messed it up, and it wouldn't boot. So I found a solution to wipe it, but I have lost my IMEI. I didn't really notice it, because the phone was working fine, but recently I noticed that it shows "0" for both of my IMEI numbers. Also, I switched to oreo immediately after wiping the partition, initially I made the full backup just in case I had to go back to nougat. So first I thought that the problem is caused by the early oreo builds. But I have tried several nougat builds too, even miui, but I got the same issue, standby battery drain, and no IMEI, even after installing the fastboot rom of miui. Yesterday I thought that they may have something to do with each other, so I decided to try to restore the EFS, and the IMEI. I've followed some guides here on xda and also on miui forums, and after restoring the QCN file for my model (global version) and writing IMEI with the Qualcomm imei writer tool, I succeeded . I got my IMEIs back, and I hoped that it would solve the battery drain too. But today after letting it in idle, the battery drain is the same. I would rule out any ROM specific issue, because it happens on miui too, and every rom I have tried. Also I don't think it's connected to any apps, because I have tested roms also without restoring anything, I haven't even flashed gapps, and the idle battery drain was still there. I only managed to "solve" it one way: changing preferred network type to any of the options, without LTE. If the phone is connected to HSPA+/3G, (without mobile data, just the service) I can get it to last 2 days, and it's the same if I have it in airplane mode, the drain is gone. That's why I also think that it's not a hardware issue. I could use my phone without LTE, we don't even have VoLTE here, so it's not mandatory, but I would like to solve this problem If I have already spent that many hours figuring out what the solution could be. It's also important to mention that even if connected to LTE (phone service) kernel adiutor shows that when the phone is in idle, the CPU goes to deep sleep and not awake. Now I'm reaching out to you guys, could you please help me? Thank you in advance!
Click to expand...
Click to collapse
Hi, Did you get any solution for this issue? I am experiencing the same issue as you. Please share your solution (if you got it) or your experience on what you did next to solve it?
himanshuchaurasiyahc said:
Hi, Did you get any solution for this issue? I am experiencing the same issue as you. Please share your solution (if you got it) or your experience on what you did next to solve it?
Click to expand...
Click to collapse
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
ardrift said:
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
Click to expand...
Click to collapse
share it, its not my imei.
ardrift said:
Hello, sorry for replying so late.
I was provided a solution by @evil-god , he sent me a "healthy" qcn, I only had to change my IMEI to my original one using an IMEI writer, and then restore the qcn file with QPST.
Since -as far as I know-, this is a device and hardware specific file, I don't think one should try it on other devices, but it should work if you have the same model.
As the original qcn (sent by "evil-god" as written above) contains his device's IMEI, I won't share it without his agreement, but hopefully he'll see this post and reply with either his agreement or the file itself.
Click to expand...
Click to collapse
So here is the mentioned file that fixed the issue, I hope it will work for other affected users as well.