Related
Hi, if anyone could help me it'd be much appreciated i have tried two different roms running the new 4.3 sony firmware but in both cases my phone seems to stay awake with android os being at the top of the battery drain list. for some reason or the other i is not allowing the phone to sleep, i believe it may be kernel related but am unsure. Has anyone else encountered this problem, and does anyone know of a way to fix this. any help would be much appreciated
Current rom - existense Z V5 (with the same issue)
Techpenguin5 said:
Hi, if anyone could help me it'd be much appreciated i have tried two different roms running the new 4.3 sony firmware but in both cases my phone seems to stay awake with android os being at the top of the battery drain list. for some reason or the other i is not allowing the phone to sleep, i believe it may be kernel related but am unsure. Has anyone else encountered this problem, and does anyone know of a way to fix this. any help would be much appreciated
Current rom - existense Z V5 (with the same issue)
Click to expand...
Click to collapse
here u go
1 root ur mobile.
2 install greenify + donation apk + xposed installer modules.:angel:
3 greenify all user app + system app such as google+,maps,google search or other you dont use.
4 install rom toolbox pro and uninstall those user app which u dont wana use (backup before removing system app):laugh:
mtayabkk said:
here u go
1 root ur mobile.
2 install greenify + donation apk + xposed installer modules.:angel:
3 greenify all user app + system app such as google+,maps,google search or other you dont use.
4 install rom toolbox pro and uninstall those user app which u dont wana use (backup before removing system app):laugh:
Click to expand...
Click to collapse
Thank you for your quick response but that won't fix it as as far as I know I'm the only one having this problem on a freshly flashed fw with not even my Google account set up
I'm having the same problem.
At the moment it's on 57% of resources used. While the one below is only at 14%.
It's not all the time though... Some days it uses this much and other days it's just normal
Techpenguin5 said:
Thank you for your quick response but that won't fix it as as far as I know I'm the only one having this problem on a freshly flashed fw with not even my Google account set up
Click to expand...
Click to collapse
Personally I would like to see something similar to what BetteryBatteryStats or Wakelock Detector show. On the main screen show Google Services, but when we click it for more information it would be nice to see a breakdown of exactly what service within Google Services is using up the CPU, battery, etc ,not only u have this issue even ur using google apps or not its still working on background .so, i disabled "Google Play Services", cleared the cache of all Google Related Apps, also Uninstalled All Google Related Apps, and it seems to solve the issue...:fingers-crossed:
Fasbook and Chrome drains the battery also really much. Delete all share apks and social engines with Titanium Backup or a root browser. Before I deleted some apks I don't had more than 3.5 hours Screen on time. Now every time 4+ hours. Once up to 5.5 hours.
Bloatware drains the Battery really much.
And yeah mtayabkk is right, Greenify some apps.
ArnoudAR155 said:
I'm having the same problem.
At the moment it's on 57% of resources used. While the one below is only at 14%.
It's not all the time though... Some days it uses this much and other days it's just normal
Click to expand...
Click to collapse
Quick question is the model of your xperia Z C6602 or C6603 and i mean before you rooted,flashed a rom......
Also which model do you have mtayabkk
Techpenguin5 said:
Quick question is the model of your xperia Z C6602 or C6603 and i mean before you rooted,flashed a rom......
Click to expand...
Click to collapse
C6603 and I flashed Nuts 10.4.B.0.569 Commercial&Journalists
ArnoudAR155 said:
C6603 and I flashed Nuts 10.4.B.0.569 Commercial&Journalists
Click to expand...
Click to collapse
see i think that may be why im using a c6602 so
I have a similar problem, still trying to figure out what's causing it.
Conclusion
Ok guys ive drawn to a conclusion that the c6603 ftf file just does not go well with the c6602 model, maybe because of the radio of the c6603 model using LTE. But im not sure so if anyone with a c6602 phone wants 4.3 without battery drain youll just have to wait till sony releases it and someone makes an ftf of it
Never mind guys I reset back to 4.2.2 with ftf factory reset there flashed existence z then the stripped.ftf and now I seem to be getting no problem anyway thanks for all the suggestions
I went and downloaded newer versions of Google Play services from apk mirror and now keep getting a permissions notification.
What version are you running on your stock att branded nexus 6 and do you have the apk?
Thanks.
I have the moto version and mine came with 6.1.84. I installed 6.5 but it caused my Google Inbox to stop working along with GPM. I'm just going to wait for it to update on its own
Attached a pic of the updated version I have on my N6 (from T-Mobile). Should be the same across carriers, but someone with an AT&T version can confirm. Also, this version is giving me huge battery drain (either first or second on the list in settings). No other issues besides that though.
Sent from my Nexus 6 using XDA Free mobile app
Stock. 6.1.88 Att no issues with battery drain. Doesn't even show up on my battery use and all options are on.
Mine is running 6.1.88 -736! Looking at Google's explanation of the - XYY version, this doesn't make any sense! This is a stock ATT N6. I have only unlocked the bootloader.
I really wonder if it is on the 736 version because I bumped my Nexus 4 running lollipop for the initial setup. I have thought about flashing the factory lrx21o image and seeing what happens...
Shouldn't I have 738 or something? A
aka757 said:
Attached a pic of the updated version I have on my N6 (from T-Mobile). Should be the same across carriers, but someone with an AT&T version can confirm. Also, this version is giving me huge battery drain (either first or second on the list in settings). No other issues besides that though.
Sent from my Nexus 6 using XDA Free mobile app
Click to expand...
Click to collapse
Updated via the play store or did you manually update it?
Manually updated by downloading the apk
Someone with the stock version, do you think you could download the apk so I can flash the stock one? I want to avoid having to reflash the whole boot image just for the stock version, and I can't find the apk anywhere else.
Sent from my Nexus 6 using XDA Free mobile app
Disable the play services then downgrade it to the stock version and re-enable it.
Here is a link to the stock one that's on my phone (I didn't post the apk)
http://www.apkmirror.com/apk/google.../google-play-services-6-1-84-1532979-738-apk/
My wife's Moto X (2013) on VZW got the OTA to Lollipop last night, but today it keeps throwing an error "Update Google Play Services. Google Play services won't run unless you update Google Play services." If she follows the update link, it takes her to a blank page that has a retry button that doesn't do anything. I had her clear the Play cache and reboot, it re-compiled the apps but the phone still throws the same error message with the same result. She's on non-rooted stock (she doesn't like me messing with her gadgets too much ) so re-flashing is out of the question. I did a bit of research and found some suggestions out there that included attempting to side-load the latest Play services. Is this the best route to take or should I try something else instead? I got the newest Play services APK from Open GApps, so I know its safe, but if there is something else I can do to fix it without messing around with that I'd be a happy man.
Thanks for any advice you can offer.
It gave me those errors also, but eventually the error messages went away after a few restarts. I also installed the newest Google Play Services downloaded from APKMirror so I can get Android Pay to work properly.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
It gave me those errors also, but eventually the error messages went away after a few restarts. I also installed the newest Google Play Services downloaded from APKMirror so I can get Android Pay to work properly.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Was it a Moto X or your MAXX that it gave the error? When I get home tonight I'll try the side load to see if that fixes it.
drindianajones said:
Was it a Moto X or your MAXX that it gave the error? When I get home tonight I'll try the side load to see if that fixes it.
Click to expand...
Click to collapse
Moto X DE updated to VZW LP 5.1 yesterday like everyone else. The MAXX is my daily driver and is running Exodus LP 5.1.1, never had the Google Play Services issue with this phone.
Sent from my DROID MAXX using Tapatalk
Johnny Wong said:
Moto X DE updated to VZW LP 5.1 yesterday like everyone else. The MAXX is my daily driver and is running Exodus LP 5.1.1, never had the Google Play Services issue with this phone.
Sent from my DROID MAXX using Tapatalk
Click to expand...
Click to collapse
Wilco that.
drindianajones said:
Wilco that.
Click to expand...
Click to collapse
Is anyone else having the problem of NOT receiving OTA on DE VZW..
I'm running stock ROM with xposed I don't see why I wouldn't receive
No, it was immediate after I RSD'd back to stock. Was running AOSP 5.1.1 prior. The first was the small update then the 700mb main file. When I say immediate, it was almost as soon as the phone finished booting up. This is a VZW Moto X DE as well, so maybe try a factory reset.
Sent from my iPad using Crapatalk
After getting home, I looked at her phone and couldn't replicate the message. So I dug deeper and found that indeed the Play Services had updated itself to the newest release sometime between when she complained about the error and when I got home. So that solves that one. I did, however, side-load the latest Play Store app, for some reason hers was several versions out of date. While I don't doubt her phone would have automatically updated it eventually it did put my mind at ease. Thanks for your input on this one.
SR3TLAW said:
Is anyone else having the problem of NOT receiving OTA on DE VZW..
I'm running stock ROM with xposed I don't see why I wouldn't receive
Click to expand...
Click to collapse
Thread hijack aside...it could be that it is being rolled out in waves and you aren't in one of the waves yet. I would try a reboot followed by going to settings > system > system updates > check for system updates.
I have VZW Moto X XT1060 Developer Edition with 4.4.4. I thought it was on standard factory ROM, but apparently it was on Krypton 1.4 and obviously, no OTA for me!
As this is my daily driver, I can't really take it completely out of service for extended periods. I had this phone pretty dialed in with Xposed and all the rest, but I imagine I'll have to nuke everything and start over with Xposed L.
I did install TWRP but it's mainly to do a backup with OTG microSD adapter.
Any recommended course of action?
kschang said:
I have VZW Moto X XT1060 Developer Edition with 4.4.4. I thought it was on standard factory ROM, but apparently it was on Krypton 1.4 and obviously, no OTA for me!
As this is my daily driver, I can't really take it completely out of service for extended periods. I had this phone pretty dialed in with Xposed and all the rest, but I imagine I'll have to nuke everything and start over with Xposed L.
I did install TWRP but it's mainly to do a backup with OTG microSD adapter.
Any recommended course of action?
Click to expand...
Click to collapse
In the same exact boat bro, business has to continue. As of now and probably for the next week I'll stick to my daily driver. Running debloated stock 4.4.4 via Titanium Backup with xposed tweaked to my fancy.
It's only a matter of time till we get our hands on a flashable Zip
SR3TLAW said:
In the same exact boat bro, business has to continue. As of now and probably for the next week I'll stick to my daily driver. Running debloated stock 4.4.4 via Titanium Backup with xposed tweaked to my fancy.
It's only a matter of time till we get our hands on a flashable Zip
Click to expand...
Click to collapse
Alright, bro. Keeping the faith.
kschang said:
Alright, bro. Keeping the faith.
Click to expand...
Click to collapse
@kschang
Where do I find xposed for Lollipop? After finding this and following instructions it led me to believe its the "..sdk22-arm.zip" Is this the correct installer?
SR3TLAW said:
@kschang
Where do I find xposed for Lollipop? After finding this and following instructions it led me to believe its the "..sdk22-arm.zip" Is this the correct installer?
Click to expand...
Click to collapse
Yes, use the sdk22 (that's Lollipop) and arm which is the CPU in the Moto X.
FYI, sdk23 is Marshmallow.
I have the factory 5.1.1 5.1 all dialed in now with Xposed and other modules, rooted and everything, of course. Haven't decided if I want to play with ROM themes yet, as I prefer a dark theme over a light one.
kschang said:
I have the factory 5.1.1 all dialed in now with Xposed and other modules, rooted and everything, of course. Haven't decided if I want to play with ROM themes yet, as I prefer a dark theme over a light one.
Click to expand...
Click to collapse
What did you flash to get 5.1.1? I thought the factory version was stuck at 5.1 and that the only 5.1.1 options were third-party ROMs like OctOS and AICP. My wife's phone is in a similar predicament, it's running Krypton 4.4.4 right now and I want to get it running Lollipop, I was thinking of this stock ZIP.
Jacquestrapp said:
What did you flash to get 5.1.1? I thought the factory version was stuck at 5.1 and that the only 5.1.1 options were third-party ROMs like OctOS and AICP. My wife's phone is in a similar predicament, it's running Krypton 4.4.4 right now and I want to get it running Lollipop, I was thinking of this stock ZIP.
Click to expand...
Click to collapse
oops, you're right, it's 5.1 (and that's it)
Jacquestrapp said:
What did you flash to get 5.1.1? I thought the factory version was stuck at 5.1 and that the only 5.1.1 options were third-party ROMs like OctOS and AICP. My wife's phone is in a similar predicament, it's running Krypton 4.4.4 right now and I want to get it running Lollipop, I was thinking of this stock ZIP.
Click to expand...
Click to collapse
FYI @Jacquestrapp I had manually flash the modem using ADB and MFASTBOOT. I'm currently on the debloated 5.1 and its working well. Expect to wait a few minutes on the first boot up after flashing ROM
kschang said:
oops, you're right, it's 5.1 (and that's it)
Click to expand...
Click to collapse
Sent from my XT1060 using Tapatalk
here are my two recommendations for LP:
custom: NeXus Experience
pros:
- can install a custom kernel
- contains privacy features so that you can block wake locks, etc
- no need for xposed as all tweaks/mods are already built in
- best battery life
- developer is currently working on a build for 6.0
cons:
- Active moto display will not work (but ambient display works just fine)
stock: Stock
pros:
- most reliable
- moto active display works
cons:
- need xposed to get personal tweaks
- xposed & Gravity box still have some issues (but working for me)
- still some bloat in the debloated version, but that can be adjusted
overall, both are fine. bluetooth works fine on both (in both my car and watch)
I've used both, but keep coming back to NeXus
jco23 said:
here are my two recommendations for LP:
custom: NeXus Experience
pros:
- can install a custom kernel
- contains privacy features so that you can block wake locks, etc
- no need for xposed as all tweaks/mods are already built in
- best battery life
- developer is currently working on a build for 6.0
cons:
- Active moto display will not work (but ambient display works just fine)
stock: Stock
pros:
- most reliable
- moto active display works
cons:
- need xposed to get personal tweaks
- xposed & Gravity box still have some issues (but working for me)
- still some bloat in the debloated version, but that can be adjusted
overall, both are fine. bluetooth works fine on both (in both my car and watch)
I've used both, but keep coming back to NeXus
Click to expand...
Click to collapse
Getting gravity box system framework error? Xposed installed fine
Installed next to latest version of gravity box
Sent from my XT1060 using Tapatalk
jco23 said:
here are my two recommendations for LP:
custom: NeXus Experience
pros:
- can install a custom kernel
- contains privacy features so that you can block wake locks, etc
- no need for xposed as all tweaks/mods are already built in
- best battery life
- developer is currently working on a build for 6.0
cons:
- Active moto display will not work (but ambient display works just fine)
stock: Stock
pros:
- most reliable
- moto active display works
cons:
- need xposed to get personal tweaks
- xposed & Gravity box still have some issues (but working for me)
- still some bloat in the debloated version, but that can be adjusted
overall, both are fine. bluetooth works fine on both (in both my car and watch)
I've used both, but keep coming back to NeXus
Click to expand...
Click to collapse
Appreciate your input!
Sent from my XT1060 using Tapatalk
Hello guys,
As many of you has already experienced this problem with google apps, I think someone here could help me.
I had been using the resurrection remix OS for a while along with a friend, and two weeks ago, when we were still using Lollipop, we faced this problem after updating the google play services application(Unfortunately, Google Play services has stopped).
We managed to solve it with the recipe of uninstalling the latest updates directly on the app. However, when we updated for Marshmallow version of RR OS, the problem happened again. And unlike in the lollipop, we cannot find the way to directly uninstall the updates for the app.
Searched other methods in the XDA threads, Youtube, and found nothing to solve it. We already tried to give all permissions to google play services and other google apps, wipe cache and dalvik, clean cache, and nothing worked.
Someone here experiencing the same frustrating problem?
although I don't think the model of the phone has nothing to do with it, the problem happened in 4 cell with me and my friend, MOTO X-2014 XT1097, MOTOG2 XT1068, MOTO G-2013 XT1032 and MOTO E XT1514. Using the latest version of RR OS.
Don't know any other method or recipe to try, if someone could give me a light, so i can get back to using all google apps normally.
Thaks a lot in advance!
same problem here!
I was getting a few of those within the last week, I updated my Gapps (and CM), so far no errors, but still too early to tell for sure.
These are my current versions, so try updating your Gapps.
leftyjoe said:
Hello guys,
As many of you has already experienced this problem with google apps, I think someone here could help me.
I had been using the resurrection remix OS for a while along with a friend, and two weeks ago, when we were still using Lollipop, we faced this problem after updating the google play services application(Unfortunately, Google Play services has stopped).
We managed to solve it with the recipe of uninstalling the latest updates directly on the app. However, when we updated for Marshmallow version of RR OS, the problem happened again. And unlike in the lollipop, we cannot find the way to directly uninstall the updates for the app.
Searched other methods in the XDA threads, Youtube, and found nothing to solve it. We already tried to give all permissions to google play services and other google apps, wipe cache and dalvik, clean cache, and nothing worked.
Someone here experiencing the same frustrating problem?
although I don't think the model of the phone has nothing to do with it, the problem happened in 4 cell with me and my friend, MOTO X-2014 XT1097, MOTOG2 XT1068, MOTO G-2013 XT1032 and MOTO E XT1514. Using the latest version of RR OS.
Don't know any other method or recipe to try, if someone could give me a light, so i can get back to using all google apps normally.
Thaks a lot in advance!
Click to expand...
Click to collapse
Most people that had this issue was directly related to Amplify and Limiting the icing wakelock. Not limiting it was the solution.
ForSquirel said:
Most people that had this issue was directly related to Amplify and Limiting the icing wakelock. Not limiting it was the solution.
Click to expand...
Click to collapse
Thank you so much friend!
I disabled the icing wakelock block in the Amplify and the error seems to stop happening.
Hope it stays this way.