My s3 had been suffering constantly from wakelocks depending on the situation.
If I had location services and Google now closed audio_2 takeslevel.ost of my battery life (around 25% every 7 hours)
And if i turned them on audio_2 almost dissappears and url dispacthing service and npl wakelocks take over and drains the battery in the same level
Here is what I tried:
-formating phone and greenifying and non system apps
-installing a new version of cyanogen mod to 4.3.2 stable from 4.2.2 stable
-switching back to Samsung's stock 4.1.2 ROM
-using media scan
- Using task managers
-switching the battery
Seriously don't go on with there is no solution this problem is so annoying if it keeps up I'll consider throwing the phone
Related
I don't think my vibrant is sleeping properly, the Up time and awake time are pretty much the same.
Mod: CyanogenMod-Trigger (8/22 version)
Android 2.3.5
Baseband T95UVKA7
Kernel: 2.6.35.12-ge334261 ([email protected] #1)
Under battery use android system is listed as always 60+%
when I click on the android system under battery use these are the packages listed
Account and sync settings
settings storage
VPN services
Status Bar
Android System
Tweaks
Settings
CyanogenMod settings
Theme Chooser
Google Backup Transport
does anyone know how I can get it to sleep properly when the screen is off? I'm having major battery drain and even with battery calibrator it still drains 8-10% an hour while idle
Have you tried turning it off and on again ? (Roy). If you haven't then give it a reboot and it should be fine.
Sent from samsung vibrant
rebooted earlier, it has helped so far. hopefully it keeps working, when I first flashed on Thursday it drained pretty badly but then I used battery calibrator and it was working nicely until yesterday and todat
Sent from my SGH-T959 using XDA App
Try installing BetterBatteryStats. It should help identify what's keeping your phone awake.
http://forum.xda-developers.com/showthread.php?t=1179809
Read the entire thread because it contains a lot of useful information.
Hi @all,
since i switched from samsung stock rom to CM 10.1 (M3) there is a high battery drain when the phone is running on standby.
To be sure i'm getting nearly "comparable" results, i flashed both roms completly clean without any additional apps. Google services/syncs switched off, mobile data disabled.
With the samsung stock rom the battery lasts for about 3,5 days in standby. With CM10 the battery is drained after 1,5 days. 12 hours after charging BetteryBatteryStats shows a high number (~20000) of kernel wakelocks for the type "wlan_ctrl_wake" (NOT wlan_rx_wake). As far as i can see, there is no connection to any app keeping the phone from entering deepsleep. However, i only have a deepsleep rate of about 70%. Nothing suspicious in partial wakelocks.
Regarding the battery drain topic, there are many hints on google now, latitude, Gtalk and so on. Already tried those. There's no need to change the wifi settings, because on samsung stock rom everything works fine using the same settings (just about 40 wlan_ctrl_wakes within 12 hours). I'm using Fritzbox 7170 as wifi ap. Some people mentioned multicast/broadcast packages may be a reason for high wifi wakelocks. I traced the network, but nothing of the sort occurs.
Any ideas?
Thank you
Wakelock detector will link the wakelocks to the specific apps
I love Android.
I think the customization is great, and since v4 it's smoother and feels more responsive.
There are LOTS of apps and it's better than iOS.
But i'm sick of the battery issues.
I've always loved trying new features, ROMs, apps, hacks and whatever.
I now have SGS3 and it's my third android device, and i've installed ROMs dozens of times, even on my friends' devices.
One thing that always kept me alert is the battery life - the maximum I can get from my battery is around 30 hours with my usage - 1/5-2 hours of screen, ~45 minutes talk, lots of standby.
But every now and then, my girlfriend, my dad, my aunt or my friend ask me 'why does my battery drain so fast?'
Sometimes its google maps.
Sometimes its mediaserver/media scanner
Sometimes - and only I can see it cause they are not familiar with tools like BBS, it's gsf (Google Services Framework).
The point is, when you have an Android device, you need to check the battery stats every now and then to make sure nothing is unusually heavy on the battery.
I am currently experimenting with ParanoidAndroid and AOKP, which are faster and more responsive than omega/stock.
Yesterday i went to sleep (6 hours) with 25% battery (after it lasted 15 hours) and I turned off the data connection and the wireless connection.
I woke up after 6 hours (lucky..) and I saw my phone if off. after I connected it to the charger and turned it on I saw mediaserver decided to wake up in the middle of the night, after It almost did nothing during the day, and worked for 5.5 hours until the battery died!
Today I unplugged my phone and in 1 hour of standby 10% of the battery were gone, I checked what happened using BBS and saw gsf again (that GTALK_SYNC whatever wakelock) was draining battery, after I thought I fixed it yesterday when I disabled app data and browser sync in the google account sync options). I rebooted and now it seems ok again, the phone is back to ~70-80-% sleep.
I want to emphasize that I don't like all the stupid battery tips that tell me to castrate my phone:
turn off wifi when it's not needed, turn down the brightness, lower the screen timeout, disable sync (wtf? but its a smart phone, I WANT push notifications!) and that sort of things.
I KNOW I can get >24hours of battery without disabling the basic features of my phone.
And the draining battery processes that I mentioned earlier can suddenly appear even in a stock ROM, so I don't think it's PA or AOKP's fault.
What I want is that google will finally build a supervisor entity that will check what causes an unusual battery drain, check if it makes sense, and disable that cause!
It's absurd that google maps application comes with default 'enable location reporting' that constantly drains your battery and for what?? google maps doesn't run in the foreground, why the hell will I want that background location reporting draining my battery? and if so, why do you put this option enabled BY DEFAULT? The average user doesn't know this sort of stuff, and get only 10 hours of battery out of a device that should ideally provide ~30 hours!!!
Just wanted to let it out of my system...
And to get useful battery tips if any...
until a few days ago i was getting decent battery life but now battery easily drops around 40 percent overnight without any usage.. when i checked battery usage (I'm on IC) android system and google services had 21% each.. when i try to use amplify/unbounce from xposed, phone lags and random reboots and greenify doesn't help that much either...
is there something i can do?
Maybe you can try disable service and appopsxposed
bijgu said:
until a few days ago i was getting decent battery life but now battery easily drops around 40 percent overnight without any usage.. when i checked battery usage (I'm on IC) android system and google services had 21% each.. when i try to use amplify/unbounce from xposed, phone lags and random reboots and greenify doesn't help that much either...
is there something i can do?
Click to expand...
Click to collapse
Try disabling google now, turn off location, wipe cache and dalvik and check if the issue still persists. If yes, try downgrading google play services.
The best way to figure out battery drain is to install either better battery stats or wakelock detector and see which services/apps cause the drainage. I specifically stopped using and uninstalled google now (as much as I like it) and keep location tracking/gps off until I need it because of this very reason. Add in greenify and results are huge improvement in battery. Phones are useless if you don't have battery for its main purpose, phones calls and internet usage.
Sent from my cdma 4.4.2 Virgin Mobile HTC Desire 601 zara_cl
First of all, turning of location services and Google Now solved the problem for me. From now on I only turn on location services when I really need it (for example Google Maps)
Now another thing you could try is this app: https://play.google.com/store/apps/details?id=com.playfulgeeks.gservicefix
Seems to have fixed the problem for many (check the reviews)
Hello everyone. I am facing a problem since more than a month ago which is that if I turn on fast dormancy in my phone, the GCMService (Google Cloud Messaging service) causes a lot of multipdp kernel wakelocks and my phone cannot enter into deep sleep. This thing shouldn't be a problem but I have these ones. If I use an AOSP lollipop rom (to which I want to change) I cannot disable fast dormancy and if I disable the GCMService I cannot receive any notification message (e-mail, whatsapp, etc.), which for me are important, at least e-mail. Meanwhile I have a back-to-n00t based rom, in which fast dormancy toggle works.
I will now write a summary of the things I tried and how I realize that GCMServive was driving me crazy. First of all I used BetterBatteryStats to figure out what was going on behind Android OS battery usage and I saw a lot of multipdp wakelocks (arround 30% of total wakelocks and just 30% of deep sleep) under kernel wakelock tab. I did a search and I saw that it is related with fast dormancy. So I tried to disable with all the methods I could find on internet:
-Using Fast dormancy toggle for I9300 app (Play store link: https://play.google.com/store/apps/details?id=com.gokhanmoral.fastdormancytoggle.i9300 ). Worked on stock roms, not working either in CM11 nor CM 12.1.
-Using Fast dormancy toggle for I9100 app (xda thead: http://forum.xda-developers.com/galaxy-s2/themes-apps/fast-dormancy-toggle-app-version-1-5-t2647015 ). Not working on CM11. On CM 12.1 I couldn't connect anymore to the 3G network.
-Manually editing the "nwk_info.db" file. No luck.
-Editing build.prop with "ril.fast.dormancy.rule=0 and ro.config.hw_fast_dormancy=0". Bootloop on CM11 and it is not maintained anymore on CM 12+ roms, as I read here: http://forum.xda-developers.com/showpost.php?p=60511737&postcount=13426
-Using the code *#9900# with phone keyboard. Just available on stock based roms.
-Different modems and kernels. No succeed.
After all these trials I started to freeze apps and when I froze Google Play Services I could get a 93% of deep sleep and just 1% of multipdp kernel wakelock. So it was clear what was causing the wakelocks. Then I started to disable the services running in the app and when I disabled GCMService I got again a 90% of deep sleep and 1% of multipdp wakelock. But there were no e-mail notifications anymore. So I am blocked here.
Does anyone know how to reduce the activity of GCMService and still be able to receive e-mail notifications but no having wakelocks? If it is possible I prefer a solution not involving xposed.
Thanks a lot in advance.
And I want to acknowledge in advance all the rom developers who created the roms I used and the developers and researches who made the apps and procedures I used here.
More info:
Test environment: WiFi off, GPS off, Bluetooth and NFC off. Just 3G mobile data on with full bars signal and fast dormancy on.
Roms I used: Blekota Note 4, official Cyanogenmod 11, and ArchiDroid 3.1.3.
Edit: Greenifying all GCM apps doesn't work either.