Related
I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?
WibblyW said:
I've noticed that once phone is powered off/on after shutting down with battery dead that neither automatic sync nor background sync happens despite being ticked. I have to cycle the setting to kick it into life. Anyone else seen that?
Click to expand...
Click to collapse
Are you sure that this simply isn't they power save feature kicking in?
This can be configured using various settings from within
Settings > Power > Power save
Sent from my HTC Desire S using XDA App
Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.
WibblyW said:
Power save works fine when the battery gets below 15% (in my case). The problem is it doesn't seem to come out of power save mode properly on its own when the phone has power in it again. I find the background and auto sync settings have been reticked, but they don't seem to be effective until I un-tick/re-tick them manually.
Click to expand...
Click to collapse
Oh, must admit that I have not noticed this, although I do use tasker application to enable and then disable my various radios and sync settings based on time in order to save battery
Sent from my HTC Desire S using XDA App
This is happening on my Desire S too.
Have you found a solution as of yet?
frosticus said:
This is happening on my Desire S too.
Have you found a solution as of yet?
Click to expand...
Click to collapse
Nope. There's a LOT about the Desire S that kinda half works properly. I find its implementation really kind of sloppy. Definitely NOT a phone I go round recommending to anyone.
To ben_pyett's comment I considered Tasker. Apart from the fact that there are lots of comments that some of it's functionality is broken in 2.3 because Google messed with their APIs, when I thought about it I was pricipally going to get it to try and fix/work around all the stuff that doesn't work well in the Desire S, rather than add functionaliy. E.g.
- Auto display brightness always has the brightness too high (esp in dim ambient light) and there's no way to adjust its 'gain'
- Cycling Buetooth and WiFi and GPS availability (using various strategies based on location and time) only to mitigate poor battery life in the standard product
- Getting it to out of power save mode properly
- Stopping it making the SMS received notification noise when it was just receiving a txt delivery receipt
Sadly there's other stuff Tasker can't 'fix'.
I find myself rebooting the phone manually every two or three days when it begins to exhibit weird behaviour. It might be crashing and rebooting between those times too. I used to have a SIM PIN activated, but it would prompt for that before allowing me to even get calls after a crash, so I missed important calls before I noticed it was in that state. Now with the SIM PIN disabled it might still be crashing but I don't spot it at least.
I was a Blackberry user for years, and should never have changed. At least the BB was stable and all its features seemed to work properly (and had excellent battery life even with WiFi and Bluetooth on 24/7). I though the extra Google integration with Android was attractive and would be worth it. How wrong I was. :-(
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Dr_Nacho said:
I know I've made a few posts about this in the past, but now I've learned a few things since then.
I know the battery isn't the greatest on the infuse (no rom that I'm using atm..) but would like to get the most juice out of my device that I can. I have root access and currently use the apps "battery calibration" and "no-frills CPU control" which I set my cpu at a relatively low frequency to help keep juice.
My phone is drained throughout my day, even without use. I believe it primarily happens because my data (mobile network) consumes it. I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery. However, I have used this application in the past and after a few days of use, it shuts off my mobile connection altogether.
My question is, if I were to use this application again and my mobile network were to malfunction, would I be able to change my apn to regain my network connection? In the past I had to reset my phone to regain connection, which isn't really worth using if that's the only solution.
Or are there any other battery saver apps worth using??
Thanks
Sent from my SAMSUNG-SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
A bit more information is needed before a specific course of action can be recommended. How much battery life are you using in an average 24 hour period? Also, what version of Juice Defender(beta, free, plus, ultimate) are you using, and what specific settings are you utilizing. It is a very customizable program after all. You might look into Battery Indicator Pro, which estimates your total remaining battery life based on your level of usage. I would also recommend CPU spy, which, if your device is rooted, will show the percentages that your device is running at various CPU levels.
If you turn off all the locational stuff, turn off 'update my current location' in Navigator, and set your CPU gov to conservative, you might get better battery life. I've not had any lasting luck with any of the battery saving apps. In the end, I decided to buy a couple of Anker batteries from Amazon just in case I have a bad battery day... Also some of the battery saving mods work, but I'm not sure about applying them to ICS and JB ROMS. I haven't tried!
Battery life is what you make of it..
Anything running in the background will drain the battery.. email constantly checking for new messages, twitter, Facebook, GPS, WiFi if no connection is found, etc..
Anything that makes the phone process even while the screen is off is going to kill a battery..
What ROM are you using? Some ROMs have better life than others..
How much are you actually using the phone?
What's the brightness set at?
Have you tried changing the processor and slowed it down?
Lots of information that is missing is helpful..
Its powered by Jellybeaned AOKP!
I know apps such as "juice defender" are great at reducing idle drainage because it shuts off your network connection while in idle to save battery
Click to expand...
Click to collapse
Some have good luck with these, others don’t. I prefer to try to adjust settings myself.
I believe it primarily happens because my data (mobile network) consumes it.
Click to expand...
Click to collapse
How about putting a widget on your homescreen to toggle data on/off. Keep it on only when you need it. I go a step further, I use Tasker to automatically turn my data off every time my screen times out (because that means I’m not using it... I can restart my data later with my widget when I need it). Maybe that’s extreme, but I’m not just watching my battery.. I’m managing my limited data plan.
My phone is drained throughout my day, even without use.
Click to expand...
Click to collapse
It may be that you have wakelocks keeping your phone awake when it’s supposed to sleep. One way to see this is (in GB or above) Settings / About-Phone / Battery Use...then click on the small graph at the top... should expand it to a large graph with traces along the bottom including Awake and Screen On. If you have long periods of time where phone is awake while screen is off, that’s a wakelock problem. A good program to troubleshoot that is Better Battery Stats. If nothing else, follow the instructions in the first post in the BBS thread linked below, and then post a dump to the end of that BBS thread (the developer and a lot of other knowledgeable people follow that thread and will help you interpret results):
http://forum.xda-developers.com/showthread.php?t=1179809
Thru use of BBS, I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
electricpete1 said:
I found that Google Maps is one that was keeping mine awake and I think someone else on the forum reported the same. If that program (Maps) is causing problems, you can disable it from auto-starting on boot using Gemini Manager. It will still be available when you need it, just take a few seconds longer to load the first time after boot. Then need to reboot to stop it from causing wakelocks after use (there may be other easier ways, but this works for me).
Another program (Power Tutor) was helpful to me to see programs that were consuming unusual amount of battery although not necessarily thru wakelocks. In my case Dolphin Browser HD was occasionally drawing very high power even when that program was not actively in use.
Click to expand...
Click to collapse
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
atrix4nag said:
So how can I stop maps to running in background? only rebooting the device is the only option?or is there any other option?
TIA
Click to expand...
Click to collapse
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
electricpete1 said:
Just to provide more details on my previous post (not sure if it's answering your question):
I followed instructions here:
http://forum.xda-developers.com/showpost.php?p=29420959&postcount=7059
In particular, I installed the free program "Gemini Apps Manager". That allows you to stop programs from auto-loading at boot.
So I used the program to stopp Google Maps from auto-loading at boot.
That stopped a large chunk of my wakelocks, as long as I don't manually launch Google Maps.
If I do manually Google Maps, then those wakelocks come back, and to get rid of them I have to reboot.
I don't use Maps that often (only when I go on trips), so it's not a big problem for me to reboot when I'm finished with my trip to help keep my battery use low.
It may also be possible to kill it from the list of applications at Settings/Applications/ManageApplications and killing botht the application and the process...but I'm not sure if it will stay killed that way... haven't tried. I know some applications have hooks that make it hard to get rid of them once they're launched.
But (if you haven't already), I think it's a good idea to use BBS to find out what programs are causing problems on your phone. You may have other apps causing lot bigger problems than Maps. And it certainly may be the case that a program that acts up on one phone can be fine on another phone due to differences in the way the user configures the application settings and the phone settings (along with other possible differences in application version, ROM used, etc etc).
Click to expand...
Click to collapse
Thanks for your detail explanation. My main question was how can close the app without restarting? i feel my major battery drain is from dolphin browser, befor dolphin i used opera, even that has the same problem. Most of the time, if I dont open dolphin, my phone battery is good, but once I open it, it drains battery. So i am looking for soemthing simple which does, without rebooting the device.
Any way thanks for your help.
Can someone please help me figure out what's keeping my phone awake. As you can see my screen is only on very little but my phone is turning on quite a bit. This happens a lot unless I'm connected to wifibfor an extended amount of time.
krolla03 said:
Can someone please help me figure out what's keeping my phone awake. As you can see my screen is only on very little but my phone is turning on quite a bit. This happens a lot unless I'm connected to wifibfor an extended amount of time.
Click to expand...
Click to collapse
Probably Google Now and hotword detection. Also do you have WiFi "Scanning always available" on?
I have a related problem and didnt want to open another post. Not sure, maybe its better to do that? Dont want to steal topic.
Also, im sorry but i cannot provide battery tesing app results since im not allowed to root it...and as far as i know root is need to detect wakelocks on kitkat.
But i can provide an error report. Maybe that helps the pros. This happens on a fresh Nexus 5, without any apps besides the preinstalled gApps.
But not constantly, it didnt happen the last 2 days before. Every time it happens it is after a longer period of use. For example if i dont use it a lot and manage to come 2 days with the battery cycle and then charge the mobile, it happens after charging. But it never happened yet when i use device a lot and charge it more frequently. But that can be a coincidence too, dont let you irritate by that now. 4.4.4 Android. But sure is that both times, the only 2 times, it happened right after pull out the charger.
This is pic and error report:
Occurence 1
Occurence 2
https://drive.google.com/file/d/0Bw2HIVhZzrqQdnZ6UG4xYkxUY0E/edit?usp=sharing
Bugreport
https://drive.google.com/file/d/0Bw2HIVhZzrqQR1lId1lwNy0xOVk/edit?usp=sharing
Should i turn off the "keep WiFi on during sleep"
krolla03 said:
Should i turn off the "keep WiFi on during sleep"
Click to expand...
Click to collapse
Depends on what you want to use when screen is off. It just means that wifi is alwayys on. If not, if your phone goes into standby mode the 3G connection takes over. If you have no special data rate you can let wifi on. Your active time is pretty normal for a phone. If auto-sync is on and google now and all that, maybe facebook or whatsapp or even more. Newsapps that push all that does this.
What i would more worry about is your signal. Its very low and probably uses alot of battery. If i recheck your pic i would probably really better let Wifi on if your at home at least, so your 3G connection doesnt always have to work so much. Of course all this is only if you want to have internet...if you know you wont use it anyway, turn it off.
Until its not like me screen above i would not worry too much.
I have google now turned off it was doing way to many wakelocks. I do have hotword on but if I'm correct it only listens when the screen is on. I'm having an issue when the screen is off the phone still keep a waking up.
by the looks of it, its your apps and setup most likely. but its fairly normal, not that many wakeups/wakelocks as many others have. wakelocks are how our phones work, generally they are normal and expected. system apps/processes and user apps create them. only when the process thats associated with the wakeocks get stuck or run amuck, is when they are bad. and yours arent stuck, nor amuck.
simms22 said:
by the looks of it, its your apps and setup most likely. but its fairly normal, not that many wakeups/wakelocks as many others have. wakelocks are how our phones work, generally they are normal and expected. system apps/processes and user apps create them. only when the process thats associated with the wakeocks get stuck or run amuck, is when they are bad. and yours arent stuck, nor amuck.
Click to expand...
Click to collapse
Yeah I don't have many wakelocls but my phone is still awake 20% and the battery menu shows that the phone is waking up quite abit
krolla03 said:
Can someone please help me figure out what's keeping my phone awake. As you can see my screen is only on very little but my phone is turning on quite a bit. This happens a lot unless I'm connected to wifibfor an extended amount of time.
Click to expand...
Click to collapse
Low signal data, Google Now location based cards and Battery Saver or High accuracy mode. This combination gives me the same awake lines as seen here.
Technically having the WiFi on (or "always scanning") should help so it's not solely reliant on the weak data signal, but it doesn't seem to.
bblzd said:
Low signal data, Google Now location based cards and Battery Saver or High accuracy mode. This combination gives me the same awake lines as seen here.
Technically having the WiFi on (or "always scanning") should help so it's not solely reliant on the weak data signal, but it doesn't seem to.
Click to expand...
Click to collapse
I have google now turned off
krolla03 said:
Yeah I don't have many wakelocls but my phone is still awake 20% and the battery menu shows that the phone is waking up quite abit
Click to expand...
Click to collapse
being awake 20% of the time is not much. if you have apps that get notifications, check locations, or are just designed to occasionally check stuff, those are the one thatll cause most the wakelocks.
krolla03 said:
I have google now turned off
Click to expand...
Click to collapse
Guess it's just the WiFi locations in general. When on WiFi it'll rarely wake the phone only data. Google Search then shows more wake time so I figured it'd be Gnow.
krolla03 said:
I have google now turned off
Click to expand...
Click to collapse
See a comparison I did here, both with Battery Saver mode on. When using data the phone wakes constantly in its attempt to resolve location based information. In theory, having the WiFi chip enabled should help but it doesn't seem to do much.
So i got installing all the battery saver apps, greenify etc... they all close apps and not much else, my version comes from the mind of an electronics engineer view point...
hardware drains power NOT some little app running in the background! (Purely software programmer logic... )
So my app grabs what states wifi/gps/bt/modem at the time the screen goes off...
When the screen comes on, it re enables them! Eg go bed with 95% wake up with 94% put in your pocket it just does it...
The 2nd feature is the lost/stolen phone feature while the app itself can not get your gps data (no permissions for it) it can switch gps on/off...
So you send "on" without the surrounding quotes, the app will then switch on gps/wifi/modem/bt... it then disables itself
Now you can use wheres my droid or any other location finding app to easily pinpoint your lost or stolen phone (try getting a location with gps/agps/data disabled which people often do to save power!)
(Includes option to keep wifi/gps untouched from the app)
as for ads!... the ui has 1 ad, no popups or notifications ... and when activated the activity with the ad on is destroyed and can't touch battery life ... at all
Craig's Root Battery Saver!
https://play.google.com/store/apps/details?id=saver.battery.craigs.craigsbatterysaver
Well done
Holy crap! Someone replied (first for me here lol)
Thanks!
To be honest, your app is great when it comes to save battery, but in my opinion your approach is plain wrong in terms of the main purpose of a smartphone - receiving notifications in a timely manner, not when you turn on the screen manually. The same purpose can be achieved by using DS Battery Saver, which will in addition turn on mobile data once per specific time interval to receive push notifications.
And you should reconsider your opinion about "software does not drain battery but hardware does". Check this great thread for example. I am using a combination of different apps (Greenify, Amplify, Power Nap) to tame aggressive services/alarms/wakelocks and I am able to achieve a battery drain close to 0.0% per hour while screen is turned off with WiFi, mobile data and location turned on the whole time without losing instant notifications.
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Craig Capel said:
The app supports wake up notifications (well, will... the app's not quite finished yet, been too busy to get everything finished)
If you had gone to the playstore you'd have seen
Click to expand...
Click to collapse
I came across this, therefore my reference to DS Battery Saver, that already is capable of exact those things. Nevertheless, your app is doing what it was designed for - saving battery (and this is pretty good, indeed).
Craig Capel said:
Also you might want to reconsider what i said..... hardware drains it not software!
You refer to wake locks ... well believe it or not, wake locks turn on hardware which drains the battery, i program microcontrollers with the esp8266 / bluetooth / compass / etc ...
Software can only drain the battery if it's purposely trying to max out the cpu, and if it did you'd know it's malware... there are wakelock detectors too
Click to expand...
Click to collapse
Well, I am familiar with what wakelocks are. But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software (which results in an unneccessary wakelock) and alarms waking up your device, not from ****ty hardware. You can hunt down those wakelocks/alarms by using apps like Better Battery Stats or Wakelock Detector and reduce them to a minimum without losing functionality. Therefore I consider this as a better approach.
But without software, that produces a wakelock, there would be no noticable drain, right? Thus we can go round and round here, I guess. From my point of view the most battery drain on an Android device is the result of poorly programmed software
Click to expand...
Click to collapse
Unless the software drains it by intensive cpu work, anything else has to be hardware, if i power a gps module, talk to it via uart to enable/disable it... then it's hardware doing it not software..
Take Qualcomm, the newer cpus support an embedded DSP
https://gigaom.com/2014/12/12/5-things-to-expect-from-qualcomms-flagship-mobile-chip-in-2015/
Qualcomm*made that feature possible*in the Snapdragon 800*with its DSP, and they’re pushing hot words even farther. New devices will have the ability to passively listen, using only a small amount of power, for more than just the word “OK.” Qualcomm calls this feature Snapdragon Sense.
The first feature it will enable is a much faster Shazam search. So if you find yourself too slow on the draw when trying to identify unfamiliar music, you’ll love this: When you boot up Shazam, it’ll already have been listening just a little bit, so it can identify the song in a few seconds.
Click to expand...
Click to collapse
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
think of it like this... software simply carries instructions which can turn on hardware via a field effect transistor, that binary 1 value shows up as 3v logic and the fet begins to conduct between the drain and source, this sets a flip flop and the hardware starts wasting power...
Or to put it another way after the software enables the hardware via a gpio the software stops, or better still, show me software draining the battery with all hardware services disabled... it can't
Good
Does it really work ..
Don't you believe the title? (Really works!)
Craig Capel said:
As hardware gets smaller and uses less power, then things like the embedded dsp chip will allow you to use wakelocks without little drainage, but were no where near that yet...
Click to expand...
Click to collapse
True words. I can also see your other points and do agree with them. But as you said, we are not even close to a system where wakelocks do not drain as much as they currently do. Would we have such a system, your app wouldn't be required, I guess. Therefore taming the unneccessary wakelocks is a good way to achieve a great battery life without losing functionality for the moment.
Awesome
Awesome!!!
Can't open the settings and this sound makes me rly angry lol. Why it makes this sound? (even my phone is silence)
Gesendet von meinem ONE A2001 mit Tapatalk
There are no settings... work in progress (says so in the play store readme)
I've had the flu for the past week so i've not been developing much... expect updates shortly to remove the "settings" option which annoyingly is placed there by default... i never put it there
The sound is cool no? ... it plays a low volume sound to indicate the app is working!
Alright, update includes support for android 4.1 for gps now... i'm slowly working my way through android oddities and different techniques to switch hardware / on and off and with 5 phones to use 4 of them use kitkat!
Had to stop for a break i've had the flu all week, throwing up constantly, later on i'll add the finishing touches to wake up notifications as right now it's extreme power saving mode...
Stay tuned.... oh and i found a bug supporting lollipop, fixed that too, so if you have lollipop and it never worked, it should now ...
Antibiotics did the trick! It was sadly not the flu but some rare bug...
I've almost finished the autowakeup every x minutes 5, 10, 20 min intervals..
Unless someone here can think up a value or maybe add it as an option.
.
I removed the blocking side of things prior i used a thread/sleep now i use a timer event this stops the lag when unlocking the device on older models...
nive work :good:
I dumped the smart check (as far as i can tell anroid never fails, so i removed it)
It should now be seamless between lock screen and the main screen without any more lock up due to the threading...
Enjoy!
great!! will try it. thanks!
Hello all,
My phab 2 Pro is draining its battery too fast with the screen off. Using Battery Historian I've been able to pinpoint it down to something keeping the phone awake when it should be sleeping. The problem is it happens randomly and I haven't been able to "connect" it to a specific app or setting.
The "kernel wakeup reason" that Battery Historian shows as the (I think so anyway) culprit is "Abort:Wakeup IRQ -1169425744 (null) pending". The number after "IRQ -" changes from log to log.
Something else that keeps popping up on the "Userspace wakelock" line with short bursts is "RILJ". This is precisely during the period that the phone is "awake" but the screen is off. So maybe the RILJ and the IRQ thing have something to do with each other?
Steps I took:
Full factory reset
Uninstalled ALL apps that can be uninstalled.
Disabled ALL apps that can be disabled, apart from things that have to stay like keyboard.
Switched of any Location setting that can be switched off
Switched of all syncing that can be switched off
Enabled developer options (to be able to pull the bugreport.txt off the device using adb)
Engaged airplane mode
But even with all of these steps, which leaves the phone totally unusable (but I have another daily driver) this weird kernel wakelock still happens frequently, draining the battery very fast. Going from 38% down to 9% in just 6 hours, with the screen off(!) is plainly unacceptable.
Are there other users out there experiencing the same? I know of one guy who posted lasted year, but maybe there are more out there?
Can anybody help with this? I have no idea what to do now I more or less now where the problem lies. I'm no coder and don't know anybody at Lenovo...
Regards,
Sander
Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days
rogerbcn said:
Is not normal what happens to you, but as a remote solution ... try to get into the applications that are working, and look at google services, there is one that spends a bestiality, it is called fileakintentoperation $ external that application next to the others Spend a lot of ram, I ended up blocking the services of google play and play store, and I assure you that the battery lasts for more than two days
Click to expand...
Click to collapse
Hi Rogerbcn,
thanks for replying.
Could you type the name of the app/service again? Google doesn't return anything on "fileakintentoperation" .
I already have the Google play and Play Store apps disabled, unfortunately, that didn't help.
Regards,
Sander
Is just below, where are the services of google play, and is also a service, but after reading that you have disconnected and you also have disconnected play store, gives me your battery or is badly calibrated or is to change, Take it to the sat of lenovo and assert your guarantee that for that we have spent 500 dollars / euros,regards
[rogerbcn] is probably correct and that you may have a defective battery. I use greenify and it seems to extend battery life about 23% for app hibernation.
https://play.google.com/store/apps/details?id=com.oasisfeng.greenify&hl=en
I resolved with task killer (kil 1 sec. After lockscreen)
edit: not resolved... anyone has other experience?
Seems to be resolved.
I used greenify, with doze go (adb solution)