So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior
This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2
I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2
You can set the max to 384 mhz.. and still everything is smooth
Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?
Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4
What is max frequency by default?
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium
droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.
If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.
Related
First and foremost this guide is based around the Sprint Nexus S 4G. If you do not have the Nexus S 4G, Than this guide will probably not help you. =)
Secondly all credit goes to the wonderful people that work endlessly to make these wonderful Roms and Kernels. Without you guys Android wouldn't be what it is today!
Third: Please make a back up and use this guide at your own risk. I don't want to bare the weight of someone turning their phone into a paperweight by using this guide.
Alright, Now lets get to the fun part.
Case you've already forgotten why you're ready this topic. This is my rough how-to guide on getting easily over 2 days out of a single charge on your phone, Very much possible to push 3 or more days depending on use and other varying factors.
What you're going to need to start:
- Rooted Nexus S 4G with a custom recovery like Clockwork mod.
- Flash the following Rom http://forum.xda-developers.com/showthread.php?t=1417499
- Flash the following Kernel http://forum.xda-developers.com/showthread.php?t=1436313
-Flash the following "KL2" Radio update http://forum.xda-developers.com/showthread.php?t=1077168
After you have flashed all the above and confirmed your phone is running stable with all the default settings. Charge your phone to 100% and reboot back into recovery, and WIPE YOUR BATTERY STATS
Now. Lets begin configuring your rom and kernel!
- Install CPU MASTER FREE from the android market https://market.android.com/details?id=com.antutu.CpuMasterFree&hl=en
Set the following on CPU Master
- CPU Speed 800 MAX and 100MIN
- CPU Governor CONSERVATIVE
- and Scheduler set to CFQ
- Make sure to click apply on boot as well
- Now Install NSTOOLS from the Android market https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result
Set the following on NSTOOLS
- DEEP IDLE: ENABLED
- Backlight Dimmer: ENABLED
- Make sure Backlight Notifications are left disabled. It keeps phone from idling properly.
- Leave all other settings alone and make sure to check set on boot
- Now lastly install Antutu Battery Saver from the Android Market
https://market.android.com/details?id=com.antutu.powersaver&feature=search_result#?t=W251bGwsMSwxLDEsImNvbS5hbnR1dHUucG93ZXJzYXZlciJd
Activate Battery Saver and set to level 2 battery save. Easy as that.
Basically your done! =)
If you notice your phone has a slightly worse or little to no improvement on the battery this is due to you deleting your battery stats. As you use your phone it will write new stats and you will begin to notice a difference after a few cycles. Just make sure your battery is charged when you wipe them, Let the phone run almost completely dead. Plug it up, Let it charge back to 100%, Unplug it. Rinse and repeat. Just be sure to unplug it when you notice it's fully charged even if you don't plan on going anywhere. Just let it sit and run on battery so that it calibrates the battery stats while it's idle as well.
Now as you should already know your battery life is going to heavily depend on use and SIGNAL STRENGTH. It seems a lot of people don't realize the more signal you have the longer your battery will last. If you're in an area with very low signal it can kill your phone in a matter of hours.
I have attached a screen shot of my battery life using this above method. Other settings I will mention
- WIFI ENABLED and CONNECTED
- Bluetooth and NFC DISABLED
- Automatic backlight control enabled
- Facebook notifcations, Weather and Contacts are the only things set to SYNC on my phone.
- Usage: Light to moderate. This includes a few texts throughout the day. A few phone calls, and a brief checking of facebook every now and then.
If I'm missing anything I will update this post. That is all for now. Happy modding and may this tutorial work the same wonders for you as it did me.
Also I should state that the phone finally died at around 2Days 17hrs on battery. My goal for 3 straight days was cut short after a few 30 minute phone calls and other work I had to do on the phone.
If you have any questions. Feel free to post, or PM me. I'll be here =)
cwayn1989 said:
First and foremost this guide is based around the Sprint Nexus S 4G. If you do not have the Nexus S 4G, Than this guide will probably not help you. =)
Secondly all credit goes to the wonderful people that work endlessly to make these wonderful Roms and Kernels. Without you guys Android wouldn't be what it is today!
Third: Please make a back up and use this guide at your own risk. I don't want to bare the weight of someone turning their phone into a paperweight by using this guide.
Alright, Now lets get to the fun part.
Case you've already forgotten why you're ready this topic. This is my rough how-to guide on getting easily over 2 days out of a single charge on your phone, Very much possible to push 3 or more days depending on use and other varying factors.
What you're going to need to start:
- Rooted Nexus S 4G with a custom recovery like Clockwork mod.
- Flash the following Rom http://forum.xda-developers.com/showthread.php?t=1417499
- Flash the following Kernel http://forum.xda-developers.com/showthread.php?t=1436313
-Flash the following "KL2" Radio update http://forum.xda-developers.com/showthread.php?t=1077168
After you have flashed all the above and confirmed your phone is running stable with all the default settings. Charge your phone to 100% and reboot back into recovery, and WIPE YOUR BATTERY STATS
Now. Lets begin configuring your rom and kernel!
- Install CPU MASTER FREE from the android market https://market.android.com/details?id=com.antutu.CpuMasterFree&hl=en
Set the following on CPU Master
- CPU Speed 800 MAX and 100MIN
- CPU Governor CONSERVATIVE
- and Scheduler set to CFQ
- Make sure to click apply on boot as well
- Now Install NSTOOLS from the Android market https://market.android.com/details?id=mobi.cyann.nstools&feature=search_result
Set the following on NSTOOLS
- DEEP IDLE: ENABLED
- Backlight Dimmer: ENABLED
- Make sure Backlight Notifications are left disabled. It keeps phone from idling properly.
- Leave all other settings alone and make sure to check set on boot
- Now lastly install Antutu Battery Saver from the Android Market
https://market.android.com/details?...1bGwsMSwxLDEsImNvbS5hbnR1dHUucG93ZXJzYXZlciJd
Activate Battery Saver and set to level 2 battery save. Easy as that.
Basically your done! =)
If you notice your phone has a slightly worse or little to no improvement on the battery this is due to you deleting your battery stats. As you use your phone it will write new stats and you will begin to notice a difference after a few cycles. Just make sure your battery is charged when you wipe them, Let the phone run almost completely dead. Plug it up, Let it charge back to 100%, Unplug it. Rinse and repeat. Just be sure to unplug it when you notice it's fully charged even if you don't plan on going anywhere. Just let it sit and run on battery so that it calibrates the battery stats while it's idle as well.
Now as you should already know your battery life is going to heavily depend on use and SIGNAL STRENGTH. It seems a lot of people don't realize the more signal you have the longer your battery will last. If you're in an area with very low signal it can kill your phone in a matter of hours.
I have attached a screen shot of my battery life using this above method. Other settings I will mention
- WIFI ENABLED and CONNECTED
- Bluetooth and NFC DISABLED
- Automatic backlight control enabled
- Facebook notifcations, Weather and Contacts are the only things set to SYNC on my phone.
- Usage: Light to moderate. This includes a few texts throughout the day. A few phone calls, and a brief checking of facebook every now and then.
If I'm missing anything I will update this post. That is all for now. Happy modding and may this tutorial work the same wonders for you as it did me.
Also I should state that the phone finally died at around 2Days 17hrs on battery. My goal for 3 straight days was cut short after a few 30 minute phone calls and other work I had to do on the phone.
If you have any questions. Feel free to post, or PM me. I'll be here =)
Click to expand...
Click to collapse
I thought it was the More Bars you have the more Data Kills Your Battery... but sprints 3G sucks .. some users only experience a .5kbs to 1.0 Mbs (if your lucky) ... that being said I think that's why your battery lasts longer. But then again I'm on Wifi so my battery has lasted all day ^_^ 15% left. Nfc on , Bluetooth off , screen at 50% brightness and heavy usage. Buuuut in your screen shot below your on 3G ... the 2 days.. was it always on Wifi?
- Google
What is your screen on time?
I don't use any "power-saving" apps, just AOKP Milestone 2 with Steve Garon's 1.14 kernel to run 50hrs with nearly 4hrs of screen time.
100/1100mhz, interactive governor, standard voltage, bln/bld on, wifi used whenever available. It doesn't help that my office is in a poor signal area - battery life would be much better if the signal reception bar stayed green all the time.
Sent from my Nexus S 4G using xda premium
iGoogleNexus said:
I thought it was the More Bars you have the more Data Kills Your Battery... but sprints 3G sucks .. some users only experience a .5kbs to 1.0 Mbs (if your lucky) ... that being said I think that's why your battery lasts longer. But then again I'm on Wifi so my battery has lasted all day ^_^ 15% left. Nfc on , Bluetooth off , screen at 50% brightness and heavy usage. Buuuut in your screen shot below your on 3G ... the 2 days.. was it always on Wifi?
- Google
Click to expand...
Click to collapse
Screen time out is on 30 seconds. and Wifi was connected virutally through the entire time, exception was when I visited a friends house which is why in the screenshot it does not say it's connected, However it was still active.
Braneless said:
What is your screen on time?
I don't use any "power-saving" apps, just AOKP Milestone 2 with Steve Garon's 1.14 kernel to run 50hrs with nearly 4hrs of screen time.
100/1100mhz, interactive governor, standard voltage, bln/bld on, wifi used whenever available. It doesn't help that my office is in a poor signal area - battery life would be much better if the signal reception bar stayed green all the time.
View attachment 912363View attachment 912364View attachment 912365
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Those are very nice stats, Question, On your battery log, What are the massive drops in battery from? low signal or just heavy use on your phone?
Also I believe I'm going to go back an retry my experiment with SmartassV2 governor and On Demand. because I recently read they are better than conservative.
By all means play around with these settings and if you report back something I can approve on I will be happy to update this post and give credit to whoever finds more tricks to improving the battery life even more =)
cwayn1989 said:
Those are very nice stats, Question, On your battery log, What are the massive drops in battery from? low signal or just heavy use on your phone?
Also I believe I'm going to go back an retry my experiment with SmartassV2 governor and On Demand. because I recently read they are better than conservative.
By all means play around with these settings and if you report back something I can approve on I will be happy to update this post and give credit to whoever finds more tricks to improving the battery life even more =)
Click to expand...
Click to collapse
They're from heavy use, probably angry birds or web browsing. The poor signal usually results in much slower drain.
Sent from my Nexus S 4G using xda premium
Braneless said:
They're from heavy use, probably angry birds or web browsing. The poor signal usually results in much slower drain.
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
Not saying you're wrong, but based on past experience when I lived in an area where my phone was constantly losing and gaining signal or especially switching between Verizon (Roaming) and Sprint to find a signal, My phone would get very warm and it would cause massive battery drain.
Also in regards to the Sprints 3G speed.
Here in town where I live now, with the new KL2 radio
Edit:
I have attached screenshots of 3G speeds. It seems today when I ran the test the speeds aren't that special, I guess it all depends on network load.
Braneless said:
What is your screen on time?
Click to expand...
Click to collapse
This ^
I can get about 4-5 hrs on screen-on time a day with a full charge before it dies. I couldn't imagine spreading that amount of time over three days unless I was travelling again or something lol
Sent from my Nexus S 4G using Tapatalk
kyouko said:
This ^
I can get about 4-5 hrs on screen-on time a day with a full charge before it dies. I couldn't imagine spreading that amount of time over three days unless I was travelling again or something lol
Sent from my Nexus S 4G using Tapatalk
Click to expand...
Click to collapse
Haha yeah sorry about that guys, That could have been helpful for me to post, but I actually just now realized you could view your screen on hours by clicking it. I feel about stupid now.
After I tweak some more settings and do this little experiment again I'll be sure to actually include that, Seeing as it would have been helpful LOL
Braneless said:
What is your screen on time?
I don't use any "power-saving" apps, just AOKP Milestone 2 with Steve Garon's 1.14 kernel to run 50hrs with nearly 4hrs of screen time.
100/1100mhz, interactive governor, standard voltage, bln/bld on, wifi used whenever available. It doesn't help that my office is in a poor signal area - battery life would be much better if the signal reception bar stayed green all the time.
View attachment 912363View attachment 912364View attachment 912365
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
How do you get your phone to idle so well? I can never get the battery stats to flatline like that. Could it be due to me having BLN turned on as the OP said that causes an idle bug?
tycruickshank said:
How do you get your phone to idle so well? I can never get the battery stats to flatline like that. Could it be due to me having BLN turned on as the OP said that causes an idle bug?
Click to expand...
Click to collapse
There's a possibly you're running an app in the background that's preventing your phone from deep idling. Also try the battery saving app I mentioned in the post as well. It works wonders for some, and others don't notice difference. There's a lot of varying factors.
Have you wiped your battery stats and calibrated your battery with the method I mentioned above? Also you can check to see if your phone is deep idling by going into NSTools and clicking Idle stats.
If you see that your idle numbs are higher than your deep idle stats, Than yes, Something is preventing you're phone from doing so, and I would recommend disabling BLN and seeing if that fixes it.
It could be an issue with BLN and it may not be. My entire post is basically the steps and settings I've figured out and tweaked on my own to achieve maximum battery. I've read around and it seems some others have used BLN without any noticeable difference in battery at all. I guess it really just depends.
Also to the other post, The main reason I run my phone unclocked is basically, in use, I prefer the CPU to be at the lowest max speed possible, while remaining smooth, and I've noticed no lag at 800max, So therefor even when I'm using my phone it's still not going to be pulling as much power as if lets say I had it set to 1000 or 1100. Overclocking is great, Don't get me wrong, but unless you're doing something heavy like gaming or a sheet ton of crazy multitasking, I don't really think it's worth it. That's just my opinion though =)
So you're at home all this time? Then why go through all this trouble and handicapping of features and performance? Why not just plug it in?
jesusice said:
So you're at home all this time? Then why go through all this trouble and handicapping of features and performance? Why not just plug it in?
Click to expand...
Click to collapse
How exactly am I handicapping? I had people asking me how I was getting my battery life and wanted me to post up details on it, so I decided I would. I run an underclocked phone because like I stated in my previous post, I don't see the point in running a overclocked phone unless you're going for benchmarks or doing a lot of heavy multitasking and then by all means, Take the 5 seconds to change your max CPU speed. If you're referring to me not running BLN, That's because for some, including me it keeps your phone from idling and will cause battery drain. It works fine for some, others it doesn't. I'm SURE it's a problem on my end, but until I get it worked out I'm just leaving it off for now.
I've been learning about rooting and modding since the Sprint HTC Hero days. I'm far from a professional and will be the first to admit I'm an amateur compared to you guys, I cannot develop, I cannot code. I'm simply wrote this guide as a reference point for people wanting to get good battery life, That's why I said tweak with the settings and have fun.
The main reason I'm so ecstatic about the battery life, is up until now I've barely been able to get a days normal use out of an android phone even running custom roms and all that good stuff. Now I can actually use my phone throughout the day, Throw it on my dresser at night, and wake up the next morning with still enough charge to use it again without having to worry about plugging it up every night.
Home or not, this info can prove to be very useful depending on an individual's circumstance. I work multiple jobs and when I get home, sometimes I'm so tired I don't even bother to fiddle with my phone's charging cable and just crash on my bed. I've gotten great battery life using similar tactics (went to bed with a 13% charge once, woke up with the thing still alive and kicking), so again, some may find this extremely helpful. Good work!
zeigan said:
Home or not, this info can prove to be very useful depending on an individual's circumstance. I work multiple jobs and when I get home, sometimes I'm so tired I don't even bother to fiddle with my phone's charging cable and just crash on my bed. I've gotten great battery life using similar tactics (went to bed with a 13% charge once, woke up with the thing still alive and kicking), so again, some may find this extremely helpful. Good work!
Click to expand...
Click to collapse
Thank you kind sir. I'm glad you were able to find this poorly formatted guide useful! =D
Strange as the concept sounds, I get better battery life when I overclock my Epic. At first I thought this was a fluke, since a faster processor (in my head, anyways) HAS to equal more power consumed. Generally speaking, this is true...
But, here's how a higher processor speed actually helps you reduce overall battery life. During daily use, your phone throttles up the processor to get something done, and then goes back to a sleep state. Mine goes from 100 to 400 to 800 to 1100 (my overclocked speed) as I watch it, with my phone just doing it's thing.
The faster it can get a certain thing done (i.e., faster processor), the sooner it can go back to a resting state, which equals more rest and better battery life.
That's it. Of course, this only works for daily use - if you keep it running playing a few games the battery life will most likely be worse. Has anyone else experienced better battery life by overclocking? I'm curious to see if this phenomenon only effects me
My setup:
CM10.1 - Experimental (Jan 20)
NS4G modem, with nitest kernel and patch (Jan 25)
smartassV2 governer/NOOP I/O scheduler
Overclocked to 1100MHz
hmmm interesting thought... i have never overclocked my epic but im just wondering how are your boot times with it overclocked... my daily use on my phone requires bluetooth on all the time and while i am at work i play music and on breaks i play games so i do go through a battery every 2 to 4 hours (I keep 6 spares on hand at all time lol) if it didnt drain battery but sped up boot at battery change would be worth a try just always been scared to oc cause dont want to mess up my phone...
Wow, six batteries? How do you charge them all?
I've been overclocking computers and such ever since I found the clock switch on my old Packard Bell 486. The trick is to not go too crazy and start small. For example, I have two Epics in the house running at 1100, and everything is going smooth. Boot times seem pretty fast, but the overall battery life is better than it's ever been on both.
I tried to clock one of them up to 1200, and I had a couple force closes and a forced reboot, so I backed it down to 1100, and the problems went away. I've heard that others can run at 1200 all day and not have any issues, so it depends on your phone.
I'd like to hear what happens if you do OC yours - my usage is nothing like that!
Sounds about right to me, the cpu isn't working on the same thing for as long and hashes it out quickly so the battery isn't drained as fast.
Just my view, I'm a slightly advanced computer ****.
markmorto said:
Wow, six batteries? How do you charge them all?
I've been overclocking computers and such ever since I found the clock switch on my old Packard Bell 486. The trick is to not go too crazy and start small. For example, I have two Epics in the house running at 1100, and everything is going smooth. Boot times seem pretty fast, but the overall battery life is better than it's ever been on both.
I tried to clock one of them up to 1200, and I had a couple force closes and a forced reboot, so I backed it down to 1100, and the problems went away. I've heard that others can run at 1200 all day and not have any issues, so it depends on your phone.
I'd like to hear what happens if you do OC yours - my usage is nothing like that!
Click to expand...
Click to collapse
Definitely dependent on the phone as you said, back in the samurai kernel days my epic could handle 1500 no problem...
I have 2 external charger that came with 3 spare batteries... ebay like 15 bucks or so for 3 and a charger... I may give it a whirl see how it goes... what rom you using now??? Was thinking of just the regular cm10 but I really like the center clock mod of aokp... but thanks for the advice I will let you know how it goes.
Sent from my SPH-D700 using Tapatalk 2
Isn't the default lower-bound clock 200mhz on most roms? Maybe the fact that you have it going down to 100 makes a difference too?
^Pretty sure that all ROMs run 100mhz stock.
CM10 Samsung Epic - Tapatalk 2
rootsamurai said:
Isn't the default lower-bound clock 200mhz on most roms? Maybe the fact that you have it going down to 100 makes a difference too?
Click to expand...
Click to collapse
While the default is 200, 100 and 200 really aren't big enough a difference power wise to make a big jump in battery life...
wizzdome said:
I have 2 external charger that came with 3 spare batteries... ebay like 15 bucks or so for 3 and a charger... I may give it a whirl see how it goes... what rom you using now??? Was thinking of just the regular cm10 but I really like the center clock mod of aokp... but thanks for the advice I will let you know how it goes.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
In the past week, I just upgraded to a Galaxy Nexus, bit still have 2 Epics in the family. One is on CM 10 and tje other is on 10.1. Definitely like to hear how it turns out.
Although this thread is about overclocking, don't ever let your friend that knows how to change the clock speed use your phone. I let my friend use my phone to play a game, and when I got it back, it was really slow, laggy and hot. Because he thought it would be funny to change the max clock speed from 1 Ghz to 200Mhz.
Sent from my SPH-D700 using Tapatalk 2
jeffreyjicha said:
Although this thread is about overclocking, don't ever let your friend that knows how to change the clock speed use your phone. I let my friend use my phone to play a game, and when I got it back, it was really slow, laggy and hot. Because he thought it would be funny to change the max clock speed from 1 Ghz to 200Mhz.
Sent from my SPH-D700 using Tapatalk 2
Click to expand...
Click to collapse
LMAO!! That's actually pretty funny
Sprint GS3 FAQ THREAD
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours
Beerad875 said:
Hey guys. I'm wondering how much better the battery has gotten since the first week y'all got it, to now.
For me I'm satisfied with the battery and I've had it for 4 days. I get about 2-2.5 hours screen on time with fairly heavy internet usage, texting, etc.
Click to expand...
Click to collapse
I had about 3-4.5 hours of screen time other moderate to heavy usage on my first week as I was testing it's battery life. As that I just used my phone under light to moderate usage. My brightness level is always at it's lowest but when I'm outside I turn it up to about 50%. I rarely play games on my device. I read a lot on my phone. I use my phone to record lectures in class and do a bit of homework on it. 7 months later and I'm pretty much doing the same. I have a custom kernel installed and I'm really confidence about it. I carry a external battery pack with me all the time but I hardly use. After having a custom kernel for the past 7 months I can say battery life has been relativity the same screen time wise. I learned how to manage my apps so they won't prevent my phone from sleeping to save power. Your mileage will vary depending on what you're doing on your phone and how you manage your device. Cell service is crucial to the phone. If you're in area with little to no service your device will use up more power to stay connected. This is when "Airplane mode" comes in handy.
kbeezie said:
Are you taking any measures to save battery life, like certain screen brightness, disabling of certain features or radios, undervolting or CPU/Governor changes, etc?
First thing I installed on mine ( haven't had mine a week yet ) was Battery Monitor Widger Pro, since I've used that on my past devices when I was testing out generic batteries (speaking of which the 8$ ebay 3800mAh on my Desire-Z is still kicking strong after a year).
Problem with estimates, is that they are basically just that, and the difference between browsing on mobile vs browsing on wifi or mix, and your reception quality can also have an impact on your battery. (in the end, your screen is the biggest impact).
Mine lately, say if I had it charged at 100% , it'll take about 2 hours on mobile to get to 91%, with the screen being on about 25%-35% of that time (auto-brightness), receive/send text, take out of pocket to check email or facebook notifications, and so forth. Which would normally show as screen 30%, Google services 13%, Wifi 9% (when I had it on between house and destination). Phone idle 8%, Android OS 7% etc.
The widget I mentioned earlier can basically monitor your draw from time to time and if the screen was off or on and such during those times (default interval on it if using a widget is around 10 minutes on the logging, shorter may actually impact the battery it's monitoring oddly enough)
PS: The other day when I actually drained it down to 0% it took about 5-6 hours
Click to expand...
Click to collapse
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)
Sent from my Nexus 4 using xda premium
Beerad875 said:
Nah. All stock, not rooted yet, auto-brightness, No auto sync. I don't get very good service at my work and I was about 28% without service during the time I was there. I would get on facebook and message people on facebook and text, surf the internet etc because it was slow. I had maybe 2 hours screen time and 8% battery life when I left work. It was probably 9 hours off the charger. Here. I'll post a screen shot after this post (On my computer right now)
Click to expand...
Click to collapse
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.
I can say that this phone charges FAAAAAAST.
kbeezie said:
One of the benefits to custom roms (though 'stock' on a nexus is well AOSP so...) is the ability to tweak that stuff to finer details, top it off with a custom kernel and can optimize even further. Just a matter of how far you want to take it.
I have a history of immediately rooting anything I get my hands on, so I tend to have very little experience with stock. But the Nexus devices are probably the only ones I could survive having stock (but rooted) as opposed to say touchWhiz on samsung.
Click to expand...
Click to collapse
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP
Beerad875 said:
Coming from the the backflip's motoblur to the Captivate's touchwiz then onto One X's sense to AOSP.. I'm going to stay android purist from now on. I'm in love with AOSP
Click to expand...
Click to collapse
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Why do you prefer them?
So with battery monitor widget pro do I just let it run and collect data?
kbeezie said:
At least all the available kernels work just fine with AOSP. (Francos seems to be pretty popular for battery, I prefer bricked though on both my N4 and N7).
Click to expand...
Click to collapse
Guess tonight I'm going to work on getting it drained down to 0% just remembered it was my N7 that I did a full cycle on with monitoring, I haven't done so yet to the N4.
PS: I usually do a dual-graph (mV and mA), but in this screenshot you can see generally speaking with my current configuration, I tend to drain around 200-300 mA screen on, and around -20-50 with it off.
PS#2 : It only went up to the -400 or so mA on the top right because I had changed my screen brightness to about half instead of autobrightness.
Beerad875 said:
Why do you prefer them?
Click to expand...
Click to collapse
Additional options. Take for example the Bricked kernel for the N4 in my signature. This is it's feature list, it's not aimed for hardcore overclockers or such but gives you some options (The one for the Nexus 7 is a bit more configurable during the installation).
* Based upon Googles msm 3.4 source
* Various other fixes (look @ github)
* Compiled with gcc4.7.2 toolchain (linaro 09.12)
* -O3 optimized
* Snapdragon S4 & CortexA15 optimizations
* Sweep2wake
* 192Mhz min clock
* replaced qcoms hotplug binary with msm_mpdecision (IN-KERNEL, better battery life + performance)
* Extensive sysfs interface for mpdecision with all the tuneables you want (/sys/kernel/msm_mpdecision/)
* replaced the thermald binary with my IN-KERNEL solution. (/sys/kernel/msm_thermal/)
* export krait version to: /sys/kernel/debug/krait_variant
* modified ondemand governor
* Allow OC up to 1,83Ghz, faux123 (from a thermal point of view that is now SAFE)
* Fixed min cpufreq resets
* Undervolting (faux123)
* Default clocks: 384min & 1512max
Click to expand...
Click to collapse
Sweep2Wake is kind of nice too, you just slide accross the screen to turn it on without having to touch the power button (And yes your phone is still asleep doing this, it just works off interupts.)
other kernels can be a bit more involved, such as being aimed towards overclocking the CPU or GPU, or adding in extra features not normally found in stock, and so forth. I've had the best luck with Bricked and Francos'
Beerad875 said:
So with battery monitor widget pro do I just let it run and collect data?
Click to expand...
Click to collapse
Yep, if you have a widget on the home screen (I usually do 2x1 size) it'll collect every 10 mins by default. If you don't use a widget you'd have to check a box in preference to monitor without widget or it won't log times (note for example the missing 'blocks' from my history log).
---------- Post added at 11:29 PM ---------- Previous post was at 11:22 PM ----------
Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).
kbeezie said:
[/COLOR]Speaking of battery, anyone ever gotten more than say 800mA charge on their N4? Cuz even on my old Desire-Z if I plugged it into a 2.1A charger it would actually charge up around 1300-1500mA, but with the Nexus 4 seems that even on a 2.1A port it rarely charges more than 500-600mA.
It'll probably become more accurate once I actually drain it down to 0% and have the widget record it's history from 0% to 100% since it bases a lot of it's mA estimates off that (ie: off the rate of decrease of the battery's mv since batteries typically have a certain voltage once they hit near 0% and when they're at 100%, comebine that with what it knows the battery's mA to be it can determine the charge/discharge based off that).
Click to expand...
Click to collapse
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?
Beerad875 said:
I can get back to you when I figure this app out more and start using it.
What'd you say your screen on time usually was?
Click to expand...
Click to collapse
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.
My battery life has improved drastically by just sticking with one setup and letting the phone get used to it. That means keep the same rom and kernel so the phone settles in and gets used to it. After a few cycles your usage should increase.
I recommend straight CM 10.1 with Franco kernel.
Also use 2g instead of HSPA+ when you're not using data to save power.
If you're using touch control, don't, it drains more power for sure.
Undervolting helps too.
Sent from my Nexus 4 using xda app-developers app
nyyankees1237 said:
If you're using touch control, don't, it drains more power for sure.
Click to expand...
Click to collapse
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.
kbeezie said:
Can you clarify on this, other than the power/volume there's not much else to actually control the phone with.
Click to expand...
Click to collapse
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app
nyyankees1237 said:
The app 'touch control' , many nexus 4 owners use it to wake and lock the phone using touch gestures in place of the traditional power button. In my usage it definitely drains the battery quicker.
Sent from my GT-N5110 using xda app-developers app
Click to expand...
Click to collapse
Oh you mean like Sweep2Wake in the Bricked Kernel I'm using, except that doesn't use any battery cuz that's in the kernel using interrupts rather than an app that would keep the phone awake. (course that's all it does too, wake, nothing more sophisticated than that).
But yea I didn't know about that app.
kbeezie said:
Just in the last 2 hours or so, probably 30-45 minutes. I was in the car so it wasn't coming on all that often. Since I actually have the widget on my home screen now, I'll just post an update again probably in the morning as I play with the phone some more, maybe play a game or two (I'll set a Market in the battery history before I start and after I end it).
Far as figuring it out, it's pretty easy since most of it is already set up by default once you open it. You can basically just pop a 2x1 widget on the home screen and just leave it.
Click to expand...
Click to collapse
So yeah. You should drain it then report with some screenshots.
It's at 44% right now
Sent from my Nexus 4 using XDA Premium HD app
One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!
I agree, it's a very crude and inefficient way of doing it. Android is designed for maximum fluidity so they assume that every time you touch the screen the cpu will be put under load, thus the cpu ramps of the frequency - this is commonly known as touchboost. If you have a custom kernel like dorimanx you can modify it to lower the touchboost frequency and various settings so it could potentially lower battery usage during input. Although I don't know if it's worth it considering all of the various potential problems that go along with such a kernel..
iOS and android are so fundamentally different that I doubt you can (easily)modify it to perform like ios in a given workload. However, each manufacturer has their own flavor of android so they may be optimized differently. Either try several different models or just go with an iphone since you've tried it and seemed to like it - or you could always wait for android n which will hopefully be more clever and efficient..
you could try intellimn this stays at lower freq, when more power its needed it boots to higher frequencies. that along with allucard hotplug. should save battery this is with dorimanx kernel.
with ondemand its the same. or if you want more lower use smartassv2
I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?
ksc6000 said:
I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?
Click to expand...
Click to collapse
Yes you could either use twrp and back up boot. or use flashify from playstore to back up stock kernel.
ksc6000 said:
One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!
Click to expand...
Click to collapse
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.
ksc6000 said:
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.
Click to expand...
Click to collapse
if you use smartassv2 its lower.
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Its got a crappy Nvidia CPU in it, thats the issue. Like my N9, that too is crap, again, Nvidia inside.
edisso10018 said:
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
Click to expand...
Click to collapse
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Sent from my SHIELD Tablet K1 using Tapatalk
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
PearlMikeJam said:
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Click to expand...
Click to collapse
That lag is not normal. And my tablet charges from around 10% to full in about 2 hours. Maybe you should try a factory reset. If that doesn't help I would return it.
I won't buy a Samsung tablet. I would try a replacement. I own the k1 for a year now and I'm still very satisfied with. And Nvidia updates it. Which Samsung usually doesn't.
Don't listen to Nvidia trolls... ⬆
Your experience does not sound typical. Perhaps it's a hardware issue, but I agree with @edisso10018 that the first step would be a factory reset.
Wish you luck!
The Nvidia CPU is pretty good shame it's not the X1, It performs better then some of my phones with QC chips, Do a factory reset and see if the lag is still there, Battery life is poor can agree on that
My k1 is over a year old it is still playing games with no trouble yes a agree with the battery life but mine charges with no problems a have noticed a little slow down but am not running bit os updated kernel yet but a still rate 10/10 best tablet a ever owned.
Tablet is laggy, no denying it.
Sent from my Pixel XL using Tapatalk
ctap001 said:
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
Click to expand...
Click to collapse
K1 here-- I don't run stock (DU 6.0.1), but I used BitOK for a while and realized its not very good. Switched back to stock kernel (from my ROM) and its more stable. You don't lose out on much anyway-- BitOK doesn't have features I want like voltage control. Examples of instability caued by BitOK: GPU was stuck at ~350mhz, would not ramp down fully to 72mhz. Also stock is smoother. You can still use adiutor to monitor and control a few things.
One more thing: be very careful when flashing blobs and other stuff in fastboot that it is for the K1 version and not OG shield! A lot of devs posting these things arent explicit as to which version. DTBs and Blobs are specific to the shield type-- one might work for the wrong tablet version, or it might brick it, or it might be unstable.
As for the Batery life I can tell you it does suck even on the best case scenario. There is no way around this as it is small and the large screen, as nice as it is, sucks a lot of juice. Lowering brightness helps somewhat but still I'll be lucky to get a couple hours of SOT out of it.
For the price its a great tablet, with a few small compromises, such as bat life, but thats the price you pay for great screen and sound at a cheap price. We are lucky to have at least a few devs still doing work with this device, and luckier still that nvidia is STILL supporting it with updates, even if slowly. They recently announced 7.1.1 will be forthcoming.
Mine was laggy too, I flashed stock firmware with my PC and now it's working perfectly.
Bought mine as a refurb and it works fine. I think you either have bad hardware, or a bad install. Try flashing stock and see if it improves.
Tbh my only complaint is with battery life, I switched to BitO to see if it got any better, the tablet is smoother with this kernel than stock but the battery is the same, I wish we had UV'ing, my favorite setting on any kernel, back on my N10 my battery could easily be improved 10-15% and the heat was reduced drastically, good binned ones could shave up to 200mV on some steps. K wish this was implemented
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
I just bought a K1 (discount price 169€) and I don't have this problem at all. Even if I use only 1 core (settings performance) for basic app it's smooth smooth smooth.
And the battery life is huge !!
For gaming tho I switch back ofc the performance setting.
:good:
I bought a K1 three weeks ago to use as a display for my phantom 4 quadcopter. I am very impressed with its performance. I'm not experiencing any lag other than at startup. Once it's up and startup is finalized I dont have any problems. The battery life isn't great, I'll agree there but hopefully it gets better with Nougat.
Sent from my SM-G925P using XDA-Developers Legacy app
I bought a K1 last week to replace my aging Nexus 7, did a factory reset and still wasn't satisfied with it being laggy. Did my share of Google searching and finally stumbled upon a quick fix to try : disable Daydream. Since changing this one setting it has been very smooth since, no issue for lag or touch registrations.
Give it a try, might not help your charging but I did notice a much reduced battery drain while sleeping also.
My only other changes were to root, change the DPI to 240 and use the Google Now Launcher which compliments the display nicely.
I wasn't happy with it as well until I flashed cyanogenmod 13 and a custom kernel with overclock. Now it's a beast, battery is great, signal as well. And I also now have the option to OC the processor to 2.5 GHz before I play some more demanding games and then set it back to 2.2 or even lower if I won't need all the juice. Seriously, the stock marshmallow ROM sucks, I have only heard bad stuff about it. Also, the nougat update is about to come out so I'd give android N a chance, too.
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
grävling said:
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
Click to expand...
Click to collapse
Putting the CPU at 80 or 90% CPU speed in the performance settings will get you that reduced power consumption. You might not even notice the speed difference. These speed tiers also run at lower voltage.
Using the GPU frame rate limiter will dramatically extend gaming time too. I find 30 fps acceptable most of the time.
Of course it would be nice to run the thing unrestricted, but it's just not practical when you also want battery life. Look at what Nintendo is doing with the clock speeds of the X1 in the Switch.