I just updated to SuperSU 2.65 this afternoon (update showed up in the play store). Ever since, my battery has been draining at >40% per hour (standby) and the phone is hot. I'm running a stock rooted ROM, and have been for months with no issues. I tried flashing an older version of SuperSU from TWRP and it didn't fix the issue (it also removed the companion app from my phone).
I'm fairly certain that updating SuperSU is what caused it, because the only other app that updated was Google Calendar. My battery app usage doesn't show anything out of the ordinary. Any ideas on how to get this straightened out?
Thanks!
dodgeboy said:
I just updated to SuperSU 2.65 this afternoon (update showed up in the play store). Ever since, my battery has been draining at >40% per hour (standby) and the phone is hot. I'm running a stock rooted ROM, and have been for months with no issues. I tried flashing an older version of SuperSU from TWRP and it didn't fix the issue (it also removed the companion app from my phone).
I'm fairly certain that updating SuperSU is what caused it, because the only other app that updated was Google Calendar. My battery app usage doesn't show anything out of the ordinary. Any ideas on how to get this straightened out?
Thanks!
Click to expand...
Click to collapse
SuperSU settings / Cleanup for Reinstall / Reinstall from Google Play.
If that does not help try,
SuperSU settings / Switch Superuser app / Reinstall from Google Play
dodgeboy said:
I just updated to SuperSU 2.65 this afternoon (update showed up in the play store). Ever since, my battery has been draining at >40% per hour (standby) and the phone is hot. I'm running a stock rooted ROM, and have been for months with no issues. I tried flashing an older version of SuperSU from TWRP and it didn't fix the issue (it also removed the companion app from my phone).
I'm fairly certain that updating SuperSU is what caused it, because the only other app that updated was Google Calendar. My battery app usage doesn't show anything out of the ordinary. Any ideas on how to get this straightened out?
Thanks!
Click to expand...
Click to collapse
Did you reboot after the install? MI E did for a few minutes till I rebooted to complete the binary update, after that it's been back to normal...
Zdeuce2 now with golden rays of sunshine
Related
Has anyone installed andriod market 3.1.3 on the sgs2 in the UK?
If so, does it work?
Installed it last night, it's a slight improvement on the previous version which was a nightmare, there is still some lag which needs to be addressed, only a slight improvement.
jonny68 said:
Installed it last night, it's a slight improvement on the previous version which was a nightmare, there is still some lag which needs to be addressed, only a slight improvement.
Click to expand...
Click to collapse
Have you had any issues in installing apps with regards to clicking on an app, then clicking the install button, and then you just get the loading screen, but it never actually goes through with the install?
This is the problem i keep getting - i flashed the stock firmware on last night and it updated the market but fails to pull all my apps back from my google account...
Only way i can get them to install is via the market website through pushing them over the air...
Be interesting to know if this is as a result of the KG6 firmware i flashed before going back to the stock, or whether it is just a bug with the new market...
All works fine for me, on stock 2.3.3
Where can we get the apk with this new Market?
http://www.mediafire.com/?dbbwcoajt8qweo5
luke222010 said:
http://www.mediafire.com/?dbbwcoajt8qweo5
Click to expand...
Click to collapse
Thank you, I'll put it now.
luke222010 said:
Have you had any issues in installing apps with regards to clicking on an app, then clicking the install button, and then you just get the loading screen, but it never actually goes through with the install?
This is the problem i keep getting - i flashed the stock firmware on last night and it updated the market but fails to pull all my apps back from my google account...
Only way i can get them to install is via the market website through pushing them over the air...
Be interesting to know if this is as a result of the KG6 firmware i flashed before going back to the stock, or whether it is just a bug with the new market...
Click to expand...
Click to collapse
Try clearing the Market cache...
settings > applications > manage applications (all tab) > market > clear data
Can you add the apk for direct download?
Sent from my GT-I9100 using XDA App
luke222010 said:
Have you had any issues in installing apps with regards to clicking on an app, then clicking the install button, and then you just get the loading screen, but it never actually goes through with the install?
This is the problem i keep getting - i flashed the stock firmware on last night and it updated the market but fails to pull all my apps back from my google account...
Only way i can get them to install is via the market website through pushing them over the air...
Be interesting to know if this is as a result of the KG6 firmware i flashed before going back to the stock, or whether it is just a bug with the new market...
Click to expand...
Click to collapse
I got something like that.
I flashed my SGS2 to the latest XXKH3, wiping user data and cache. The first time I entered my google account my apps starts installing itself over wifi (so far so good)... During this process I launched Android Market app to see the progress, and I see the Android Market app updated... nice! But I saw that pending downloads with no progress. I switched wifi off, and the downloads continue over 3g connection... But I don't want to use my data plan downloading apps, I back to wifi but still the problem, no downloading progress...
I cleared cache for Android Market, but the same behavior
Any solutions will be appreciated... thank you
lfabresm said:
I got something like that.
I flashed my SGS2 to the latest XXKH3, wiping user data and cache. The first time I entered my google account my apps starts installing itself over wifi (so far so good)... During this process I launched Android Market app to see the progress, and I see the Android Market app updated... nice! But I saw that pending downloads with no progress. I switched wifi off, and the downloads continue over 3g connection... But I don't want to use my data plan downloading apps, I back to wifi but still the problem, no downloading progress...
I cleared cache for Android Market, but the same behavior
Any solutions will be appreciated... thank you
Click to expand...
Click to collapse
I got exactly the same issue.
This is what prompted me to go back to stock as I presumed it may be something to do with the unofficial version of KH3 causing the problem, but after going back to stock i still had the problem.
However, after leaving the phone alone for a couple of hours it seems to have fixed itself, and i can now download via wifi (albeit i'm testing it using a mates tethered sgs2).
Just wanted to say that, for me, and from many reviews in the Google Play Store, the new SuperSU causes a situation where the phone boots and finishes it's initialization but then reboots and gets stuck doing this. I resolved it by disabling SuperSU. My phone is bone stock except for being rooted.
Maybe the automatic update from the Play store caused the issue and I need to install the update through a different machanism? Anyways, disabling it solved the immediate issue, but I need and use SuperSU so I hope there is a general fix soon.
EDIT: I installed the update through TWRP, which seems to have solved the issue. Just wanted to put it out there for anyone having this problem.
Thank you for this information, this explains a problem I started having this morning.
Strange, I usually have ALL the issues, but I don't have this one.
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
stevey500 said:
I have a friends S4 here that I rooted for them a while back and installed Xposes + Wanam to make their locked bootloader device a bit more useful. It worked perfectly for many months.
Recently they come back to me to tell me their phone dies very quickly when it is not in use and does get pretty warm. Battery panel shows that Android OS is using majority of percentage and not any more detailed. I realized that it was definitely OTA updated and that Xposed stated that modules were no longer installed nor did Superuser have root. I realized I made a mistake and forgot to disable OTA services.
What I have done so far: Re-rooted by flashing old kernel, flashed back to new kernel. Reinstalled Xposed modules and things SEEM to be perfectly fine. Two days later, the same thing is still happening. Android OS is definitely still hogging the CPU doing something in a loop.
I understand that a possible factory wipe from recovery MAY fix this issue unless System files are messed up and needing to use Odin to restore BUT I figure it'd be a great idea to come here and see if there's a quick fix that may be possible that could also help other readers that have run into the issue of accidentally receiving OTA while rooted.
Thanks for reading.
Click to expand...
Click to collapse
You could downgrade back to nc5 by flashing the tar file. Nc5 tends to be more stable and battery life is decent. I tried running nk1 for awhile, running into the same issues. I went back to nc5 running echoerom v39.1
I haven't figured out the common issue here yet but in general these are the times it happens:
- when rooted on any stock or custom rom that i can find in the m4 aqua forum
The reboots tend to be mostly at random but I have noticed some consistent and more frequent reboots when installing apps from the google play store.
Currently I'm just back on the stock system flashed back with the latest firmware from my carrier with no root and I haven't noticed any reboots since yesterday (I've been getting quite a few a day while rooted)
Any ideas. I'm at a loss and have no idea where to look for help.
The same thing happened to me when i had my M4 rooted. After repairing it with PC Companion, the reboots disappeared.
Maybe Link2SD, or deleting some bloatware which shouldn't be deleted, might be causing the random reboots.
Gilmour79 said:
The same thing happened to me when i had my M4 rooted. After repairing it with PC Companion, the reboots disappeared.
Maybe Link2SD, or deleting some bloatware which shouldn't be deleted, might be causing the random reboots.
Click to expand...
Click to collapse
How do you repair it with pc companion?
ardentis said:
How do you repair it with pc companion?
Click to expand...
Click to collapse
http://support.sonymobile.com/global-en/xperiaz3compact/kb/0231018807c614a08013cec540b570068fb/
Wouldn't that wipe root off the device?
cmstew said:
Wouldn't that wipe root off the device?
Click to expand...
Click to collapse
Yes, it would.
Hey,
Just an update here. I'm still having problems with random reboots. I even tried starting totally fresh again.
Wiped:
- System
- Dalvik Cache
- Cache
- Data
All I have on this phone is:
- Unofficial TWRP Touch
- 26.1.A.2.167 (the Canadian Wind Mobile Variation using just system.ext4 and kernel.elf)
- SuperSu v2.46
- BusyBox App
- BusyBox v1.24.1-Stericson
I think somethings up with the system itself. It's not a problem with apps.
Does anyone have a method of tracking down reboots with system logs or anything?
cmstew said:
Hey,
Just an update here. I'm still having problems with random reboots. I even tried starting totally fresh again.
Wiped:
- System
- Dalvik Cache
- Cache
- Data
All I have on this phone is:
- Unofficial TWRP Touch
- 26.1.A.2.167 (the Canadian Wind Mobile Variation using just system.ext4 and kernel.elf)
- SuperSu v2.46
- BusyBox App
- BusyBox v1.24.1-Stericson
I think somethings up with the system itself. It's not a problem with apps.
Does anyone have a method of tracking down reboots with system logs or anything?
Click to expand...
Click to collapse
http://developer.android.com/intl/es/tools/help/logcat.html
Gilmour79 said:
http://developer.android.com/intl/es/tools/help/logcat.html
Click to expand...
Click to collapse
Thanks man, there's so much information out there but it's so hard to find anything useful. I read about logcat somewhere else but that it gets wiped on reboot which kind of defeats the purpose. But i've heard you can track it to the point of crashing which might just be good enough.
Thanks for the link.
cmstew said:
I haven't figured out the common issue here yet but in general these are the times it happens:
- when rooted on any stock or custom rom that i can find in the m4 aqua forum
The reboots tend to be mostly at random but I have noticed some consistent and more frequent reboots when installing apps from the google play store.
Currently I'm just back on the stock system flashed back with the latest firmware from my carrier with no root and I haven't noticed any reboots since yesterday (I've been getting quite a few a day while rooted)
Any ideas. I'm at a loss and have no idea where to look for help.
Click to expand...
Click to collapse
Did you solved the problem?
redickja said:
Did you solved the problem?
Click to expand...
Click to collapse
Nope, I have not solved the problem. Sorry.
There is a solution I've been meaning to try but haven't had the time to yet. Here is the link if you want to look into it yourself.
http://forum.xda-developers.com/xpe...b-definitive-root-remount-reboot-fix-t2317432
Currently the only solution I've found is to install the stock firmware without root.
The main reason I rooted was because I wanted to get rid of bloatware but I found out you can disable a lot of bloatware with stock android. So I'm happy for now. I'd still like root later though.
Are you using the STAMINA "feature"
I had some heat-related reboots while using that. I disabled it, and its been perfect since.
Hi everybody,
I'm using a Redmi Note2 Prime with MIUI 8 7.4.27 Beta (weekly). The phone was running very smooth, fast and reliable - battery life was always several days.
Yesterday I tried to root it using method 4 from here using recovery.img from TWRP 3.0.2-2.zip and UPDATE-SuperSU-v2.79-20161211114519.zip (SuperSU app was already installed). After several attempts (installed MI PC Suite twice until it worked on Win10) it finally worked.
I rooted since I wanted to try dual boot patcher and a MM ROM as second.
But after phone booted again it was nearly unusable. No smooth reaction I had to wait several seconds until screens changes when just scroll through them. Also apps and settings now need lots of time more before they start. Wifi is always turned off after reboot (while it was on during shutdown) and Google sync starts automatically after reboot while it is deactivated in all settings. Also background image of lock screen was changed. Google Play Services are now constantly crashing (need to click away these message requesters all the time) and Play Store does not even start anymore. Meanwhile I removed SuperSU app again since it never asked for granting root access while it was set to do so.
Installing a second ROM using Dual Boot Patcher finally also did not work (patching worked - installing not). Details are provided here.
I am still puzzled what happened here and do not have any clue since I rooted already several devices without any problems so far. Even this one some time ago IIRC.
Does anybody have any idea how I can get the phone back into a stable, usable mode? Do I have to completely reflash the MIUI8 ROM? Or do I have to use another SuperSU zip?
Any help is highly appreciated!
Thanks guys!
You can try wiping data/factory reset.
To easily install TWRP, you can use the Fastboot Install Method described here:
https://twrp.me/devices/xiaomiredminote2.html
Thanks. But doesn't this wipe/reset delete all apps and data (which I try to avoid)?
Would reflashing complete MIUI8 (version which I already have installed - without any system/data wipe) cure the problem?
TWRP app is already installed - but either TWRP recovery or SuperSU.zip crashed the Google Services (Play Services or even more) for whatever reason.
Does anybody have some idea why this might have happened? Maybe due to dalvik cache wipe which was requested?
I think that the phone become unusable a Google Services/Play Services is crashing because of wrong settings or data corruption.
That's why I said to do a factory reset.
You can try deleting just cache and data for Google Play Services and Google Play Store apps. Data are on cloud and should be restored automatically when needed.
Seems I got it working again - thanks to post #2. Used TWRP app to install another TWRP, afterwards I got a reboot loop. Then I deleted cache and dalvik cache and now everything works fine again!
Thank you!
Well Dual Boot still does not work but progressed a little bit further - but this is a different topic.
Try do delete your Rom (Backup all with Titanium backup before) and try to install latest Dev from mi-globe ! Prerootet and very smooth and good ROMs!
Thanks. But as said - got it working again (see above). The only thing which is not working is flashing a secondary ROM using Dual Boot Patcher (already opened another thread and posted it into the PATHCER thread - but seems nobody knows about some solution...).