[Q] UV, UC, other Kernel options. - Samsung Galaxy Nexus

Android 4.2.1
CyanogenMod 10.1 Snapshot M1 (21/1/13)
Franco Kernel R364
I'm trying to maximize my battery time.
(Power mode BeastlyBattery 192MHz~1036MHz, Governor: Lazy, IO Scheduler: deadline, Screen of Max Frew: 384MHz)
I want to UV my CPU (and maybe IVA and GPU also, does it helps too?) to save some battery.
Should I just decrease the voltage a bit, use stability test app and keep going till there will be errors,
or I can just decrease like someone else on the web and then keep going..?
Can it do something to the device? (because Its just undervoltage..)
For how long I need to run the stability test?
I saw this topic:
http://forum.xda-developers.com/showthread.php?t=1599025
and he says:
"1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone."
Anyone tested this?
Does UV degrades preformance?
What is SmartFlex?
Anything else I need to know about that?

Im gonna make this one quick, so my apologies if I don't address your questions directly.
Prior to my Galaxy Nexus, I had a T-Mobile SGSII. I too had the belief that undervolting/clocking would improve my battery life substantially. It seemed to work but then I was only getting the results that I wanted to get, and thats because I went to extremes to lowering my screen brightness to minimum and using my phone a fraction of what I used to.
With the help of others and trial and error, my major conclusion is that undervolting/clocking, though normal headset use will not improve your battery life by a landslide. Android is so well optimized to save you as much battery as it can. Sure there are things here in there that interrupt that optimization such as bugs or kernel issues but that something even undervolting/clocking will not be able to solve.
If you do go into undervolting/clocking your device, please keep in mind that the most you will probably get out of it is maybe 45 minutes to 1hr extension, but thats not display time.
What you can do to improve your battery life is turn off whatever sync services you don't use, lower your screen brightness ( the display is the major battery hog in the GN and SAMOLED devices), use dark wallpapers and dark themes if apps support it, use wifi, disable 3G when not in use. The radio you use can also potentially affect your battery life and signal quality.
Those are just a few suggestions, the rest is up to you.
Good luck!
P.S. Kernels also add variation to the longevity of your battery life. It's been a very long time since I touched CM10 so I'm not gonna go and defame that ROM but do try something else that possibly offers better battery life. If MODs are a MUST for you, then you will be faced with a lower battery life compared to stock based ROM's. It won't be an extreme difference but the difference will be there. If I may suggest a ROM, try this one. I can honestly say I can get up to 3-4 hours of display time on it with about a 12 hour standby.

I read a lot on the web that it does help to battery time.. :S

anyone?

You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.

063_XOBX said:
You're not going to see much difference. Running the cpu at a lower clock speed just means it will take longer to complete the same operation so you'll use just as much battery.
Click to expand...
Click to collapse
And undervoltage?
Different overnor?

Undervolting will have minimal effect during actual use and a governor is based on specific user needs. One might save me battery while another works better for your usage. You need to actually mess with setting instead of just asking others what they use.

Related

Battery Life Help

I really don't understand what is going on with my batter life. I can't get it anywhere near what people are reporting with the same configurations. I just changed roms and kernels again to Fresh and ffolkes undervolted kernel. I hope this fixes my problems because im starting to get fed up with sending 5 text messages and losing 20% in 3 hours. My setcpu has only one profile which is screen off 128 min and 245 max. Someone please help me I really can't put up with the horrible battery life I am getting.
Search around for info on powertop. If you're only running the default apps and aren't syncing a lot of stuff then it could be your battery itself. This isn't something that anybody can remotely troubleshoot for you without a lot of hassle.
Also depending, you may want the max higher on screen off. To put it simply, there is overhead with the cpu not being asleep in addition to crunching numbers. Slower processing for simple tasks may cost you more due to the CPU being on longer. Lots of variables.
Sent from my PC36100 using XDA App

[Q] setvsel cpu damage

hey guys, just wondering will using a lower vsel damage my cpu and/or battery?
i have previously beein using milestone overclock on 1ghz and 60 vsel and am adding setvsel into the mix, also any ideas on starter settings? thanks
also could someone just give me a heads up on what vsel actually IS
I don't believe there are any studies that show effects of long term use of lowering the voltage, which is what you are doing with vsel in order to save battery juice...or you could increase the voltage but that defeats the purpose and also heats up the battery which leads to shorter life span. Many use it without reporting any damage to battery or cpu, I believe it's safe (however, if you are overheating you might fry the battery or cpu, so you'll need to moniter and play with settings to get the desired effect without any overheating issues).
With regards to setvsel, there are reported issues from users with different roms...from what I've read (and you can do your own research to see if this is what you are seeing...this is the conclusion that I've come to by reading a lot of threads), it is better to use milestone to overclock and setcpu to lower the vsel.
With that being said, I've used them all and like setvsel so keep going back to it...but I've been having some issues lately so I've removed setvsel to see if that is what is causing some problems (too early to tell).
Oh, and as for settings...pop on the overclocking/undervolting thread in the development section to see a lot of different settings and remember that what works for one user might not work for you...you'll have to experiment a bit to find your ideal setting.
oh okay i think i might go back to my old settings with milestone overclock and setcpu and just lower the vsel! i was under the impression for some reason that lowering the vsel would heat the battery. Thanks!
I'm no expert to be honest, I'm more of a research kinda person. From what I've researched, undervolting can help keep temps down, and may particularly help when you overclock (as overclocking is stressing the cpu to go beyond it's normal operating design hence it may heat up...supplying it with less power, or voltage, is what helps keep the temps down.
Of course, this is given you find the optimal setting for your phone, and as it seems from reading through these forums, many users have experienced completely different results using the same settings (i.e., one user will have a stable setting without any problems while another user on the same rom using the same settings will have crashes and/or issues like overheating). Doesn't seem right, but it is what it is
yeah ive read through most of that stuff too, i went down to 1ghz at 51 vsel, seeming stable, but i decided to go with 54 anyway
1.1 GHz @ Stock vsel for over a month without any issues...I hope it lasts.
Sent from my MB525 using XDA App
Hi,
I've also read a lot regarding the underclocking 'dangers' but couldn't find anything to prove that there is such an issue. I think that it is an urban myth spread everywhere by people asking if there is a danger with low vsel [but that are never getting a positive answer on it].
The only thing I found using setvSel is that I had to first install Milestone Overclock and load its module prior to start setvsel. There is a way around it, but requires you to copy files in the system folders and change their permissions. I find that my way is much easier.
As far as over-heating goes, it's an overclocking thing; not underclocking.
My Defy is set at 900Mhz and really, I don't see the point of going much higher: everything runs smooth and lag free already.
vsel: 21/300; 32/600; 43/900 - 90% up_threshold
Been like that for about a month now and never experienced any problem at all.
The underclocking is great for saving battery; no exact numbers to give here but it feels like my battery now last 2 times longer. I can easily get 4 days between charges with low/moderate usage and would get to 6+ days "IF" I could stay away from games and having the screen ON for long sessions of browsing/video watching.
I tried SetCpu before but I didn't like the interface; the simplicity of SetvSel is really nice.
i use setcpu for scaling and profiles, and run 18/300, 36/600, 50/1000 stable and smooth as
Undervolting is not a bad thing at all. It means less Watts consumed for running (Watts = Voltage x Amperage), less of your battery consumed.
Ussually companies test a large batch of components and how they react on different voltages and freqvencies, and then they decide for a voltage that works with all components and that is safe for all cases. Eg. when they have different CPU speeds and thus different options for CPU's this is one way to decide which one work at 3GHz and which one at 2.7 GHz (the other one is demand for components).
Phisically you will not have any problems and you can't damage your phone by undervolting, so no problem here, only possible software problems if you go too low.
Advantages :
+ Lower processor temperature
+ Lower phone temperature
+ Longer battery time
+ Longer components life
Disadvantages
- Stability issues (freeze, artefacts, slowness)
maxi2mc said:
Disadvantages
- Stability issues (freeze, artefacts, slowness)
Click to expand...
Click to collapse
You know, I was recording a video and when playing back noticed that there were squiggly lines that went through the video a couple of times (in a two minute clip). This was the first time I saw this...and have recently lowered vsel by 2 on vsel3...could that be the artifacts that you are mentioning?
I just figured it perhaps I was too bouncy with the phone while recording making it glitch...but now that I see this post I'm thinking maybe I undervolted too much...what do you think?
My settings: 54/1000 44/700 28/300
I know what people mean by same settings don't work for every phone even if it's the exact same model. My Defy won't underclock as much as others. I'm using SetVesel, and I've been able to drop 5 points from each, and that's about it before it reboots itself. I only tested undervolting, but I mainly overclock to get as much speed as I can, and give it enough juice to run super fast. I'm current running [email protected], [email protected], [email protected] Threshold at 75%. The highest the temp ever got was 112F, and that was after playing a game for about an hour. Usually it stays below 90F for normal use. I get around 17-20 hours out of it with screen on time at about 3 hours @ 50% brightness. I've been running these settings about a month, and have not had any issues.
If you put something like 100vsel will the phone accept and then burn? Is there any protection? Does anyone know what's the highest acceptable vsel?
Just for curiosity...
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
stewi21 said:
im pretty sure 80 is the highest you should EVER use and that'll significantly increase the chances of your phone burning out. @bobbyphoenix you should be able to lower your vsels a fair bit or your really unlucky! i run a lower vsel for 1ghz than u do for 700mhz smooth and stable
Click to expand...
Click to collapse
CM7, rather non-technical person here. I seem to have a very happy phone at setvsel settings of [email protected], [email protected], [email protected], 86%. Been running this for the month or so since I rooted and the phone feels like it was made for this config. I've never seen the temp above ~32c. My 2¢.

[GUIDE] To Maximize Galaxy Nexus Battery

This guide is not meant to be as a whole and is not meant to be followed from beginning to end. There are several recommendations based on my own experience, some of them will give you big battery savings, some of them minor ones; I tried to recopile every config that helps to save battery, but every config is not suitable for everyone. (I´ll point it at the beginning of every section in bold blue).
You'll need a Rooted Galaxy Nexus, with a custom ROM and a custom Kernel.
The custom ROM will give you the ability to make a deep configuration of the device in terms of options. I'm actually using Liquidsmooth v1.25, but AOKP, CM9 and SlimICS have the same options (if not more) than my actual.
Some custom Kernels will give you the ability to change the CPU frequency and voltage, kernels are the main reason of some drainings or fantastic battery life, choose wise.
The normal Galaxy Nexus battery life is about 4 hours screen time. If you are not achieving this, the main reasons could be:
1. Some apps are draining your battery due to a continuous use (no deep sleep or continuous wake ups).
2. Screen too bright.
3. Bad kernels with draining problems.
4. Weak signal connections.
This guide is wrote by me, a simple user that is sharing his own experience of the last 4 and a half months with the device. Some statements may be wrong. I'll appreciate any positive recommendations in order to improve the guide and help the rest of the community to achieve the best battery life the device can give us.
I'm using actually Liquidsmooth v1.25 and PopcornKernel, in a GSM GNex with standrad battery (1700mAh), and I'm getting this results:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SCREEN
Due to the big screen, this is one of the elements of the device that affects in a major way to the battery live. (Great Savings)
It has been checked that black themes have a great impact on the battery due to the fact that one black pixel does not consume any battery.
Some apps have a black theme option on them, if you choose it you will save some battery.
On the other hand the brightness is the other part in the screen that has a big impact on the battery. In a logic way, less the brightness more the battery life. (Greatest Savings)
Now the latest ROM's have a new amazing feature, we can change the interval the sensor works to achieve the ambient light, reduce the brightness minimum value (that's by defect way too high in low light conditions), and customize your prefered light levels (that are too way too high in default configuration).
By reducing the sample interval sensor a bit and reducing the minimum value a lot we can achieved abetter battery life in a great manner.
Also adjusting the light sensor levels to a more reliable one's that are by far lower than the default one's we'll achieved a more optimize system that consumes less battery.
Note: This are my actual, after 2 weeks of adjust, values but I'm still working on them, they are no 100% reliable.
CPU
The CPU is a great beast. In terms of battery is well adjusted, by as always, we can achieve a personal optimized system (this is Android, yeah!) that will balance performance and battery life. (Great Savings Underclock and Undervolt combo).
A very good speed and fluidness can be achieved with a very good optimized and well balanced performance-battery friendly system.. and yes, with the last advances in kernels and ROMs, we can have a perfectly smooth system with a top speed of 1000Mhz.
In the other hand Undervolt will help us to achieve a cooler system with some battery gain. With Undervolt we´ll limit the max. value of the Voltage for the specified frequency, if we have a kernel with Smartflex, this one we´ll allow lower voltages depending on the power need of the CPU.
Two important things:
1. It has been tested that the 700Mhz frequency is prefereable over the 300Mhz one, due to the drops on frequency signal of the phone.
2. Undervolt values are not the same for everyone, it can oscillate depending on the individual CPU. When I UV I always test my system with an Stability Test app.
Connections
GNex is a phone...also.. well, it's a super computer with phone capabilities. Due to the "always connected" philosophy the optimal baseband will save a lot of battery. An optimal Baseband and Radio (region optimized) will require less power and time to connect to the antennas and will have better connection always (less power irradiated). (Medium savings).
The Radio should be updated and region optimized, there's a magnificent post made by josteink that explains all the details concerning the Radios with links to every one available.(GSM)
[Radio] (GSM) Galaxy Nexus I9250 Baseband dumps collection & discussion
European Radio Recommended: XXKK6 (XXLA2 is giving too high "Phone Idle", resulting in drain problems)
For the CDMA version there is another magnificent post by ready5 with a compilation of every RADIO for the CDMA version of the GNex.
(CDMA) [RADIOS/HYBRIDS]*UPDATED* 4.0.4 FULL 2/6/2012 PLUS FRIED RADIO Halp!
In the GSM version on the other part the 3G, HSPDA consumes great great great battery juice. If you are not in WIFI and are not using the data connection, a great way to save battery life is changing from HSPDA or 3G to 2G networks (this is really noticeable if you travel a lot by car or train, cause you are continuing connecting a reconnecting from different radio antennas).
There's some ROMs as Liquidsmooth that allows when you are not on WIFI and after an specified delay, to change to 2G automatically (or low consuming) networks when you have the screen off. This is a great way to save battery when you are not at home, reducing the standby drain of the phone outdoors.
.
The automatic 2G when sleep is a main function of Juice defender. Thanks to a1exus for recommendation.
In the CDMA version the LTE consumes also great great great battery juice. If you are not in WIFI and are not using the data connection, a great way to save battery life is changing from LTE to 4G networks (this is really noticeable if you travel a lot by car or train, cause you are continuing connecting a reconnecting from different radio antennas).
Thanks to thenickisme for this!
WIFI
Wifi has a crazy history on the GNex. After talking and talking, posting and posting, it has been tested that WIFI always on while sleep is the best way to achieve a longer battery life. (Medium savings).
Also the new ROM's have amazing feature that change the WIFI interval (we normally stay at the same WIFI always), increasing the value will save batterty life reducing the continues scans that produce the WIFI Always ON requirement.
Services and Apps
The best thing of Android is that we can configure anything, one of the best and underestimated feature is the Freeze or Service Uninstall. We did it before in Windows and we can do it now. Through the Apps section in Preferences or the mythic Titanium Backup we can disable or uninstall an internal function of the systems that is normally used, giving more resources to the system and in some cases, saving some battery. (Low to Minimum Savings).
There are some ICS functions that no everyone uses. For example, I don't use any Bluetooth, NFC, Google Voice, Google Search or Speech function of the system, freezing or uninstalling them will optimize our system giving some battery juice.
Note: This is a dangerous thing if you don't understand what you're doing. Make always a Nandroid before Freezing or Uninstalling an essential function, just to be cautious.
According to the Apps we have to take in account the Background Syncing or Sync Interval, most of the time the apps don't need to be synced every 5 minutes, like weather, if we make longer updates we'll achieve a good saving battery related. (Great Savings if many apps with many connections).
Widgets, 5 homescreens full of widgets updating in real time could be detrimental to the battery live, take care when adding widgets and as said in the previous paragraph, change every widget preferences to update in longer times than usually they have by default. (Great Savings if many apps with many connections).
Bad Apps are the one's that not allow our device to deep sleep or wake up continuously our GNex. There are several on the market, Readability for example is a new one that wake up continuously our device attempting to download new articles, on the other part, some time ago Widgetlocker had some problems not letting deep sleep the GNexus (don't know now). (Great Savings if there is an apps giving deep sleep or wake ups problems).
Pointing on this, the best way to know if any app is not behaving well in the system is through 2 apps:
- BetterBatteryStats, that will look for any wake up of the device while sleep.
- CPU Spy, that will tell us if the device is deep sleeping ok or not.
Other things
There are other things that will help us in a great or minor manner to save battery life.
Sync Data usage (Google services like contacts, bookmarks, etc..) consumes battery, if you limit this usage, you´ll gain some juice. The new ROM's in the Powersaver tag will allow you to limit this sync usage. (Low Savings).
The Dial Pad Touch Tones and Vibration affects battery also (yepp it's true, and in a great way!), disabling this features will give you some extra battery juice. (Low to Medium Savings with combo sound plus vibration).
The Google Location services and Backup&Reset Data consumes great battery also, limiting this services will gave you some extra juice. (Medium Savings).
The last little thing that will help you save batt life will be the Automatic Date&Time option, disabling it will give you some extra juice also. (Lowest Savings, practical minimum).
Live Wallpapers, they are very nice but will drain your battery quickly. Static Wallpapers are preferred, and if posible, dark ones. (Medium to Great Savings).
Experimental
This are new tweaks that normally appear in new/advanced kernels, his use according to battery save is still not really tested or can have a detrimental on the physical conditions of the device/battery. Use them with caution or if you really know what you are doing.
[MOD][KERNEL]Battery Life eXtender (BLX), this is a tweak created by the popular Ezekeel and in his owns words: "Older types of rechargable batteries exhibited a 'memory effect' which made it neccessary to completely charge/discharge the battery when using to prevent degradation of the capacity. Modern Lithium-Ion batteries like in the Nexus S do not show this problem and thus it is not necessary to use the battery in complete (dis)charge cycles. In fact on the contrary, it is commonly accepted that both very low and very high charge states accelerate the degradation of the battery capacity (that is why you should store Li-Ion batteries at around 40% charge).
While a low charge state can be simply avoided by charging the device more often, the battery in the Nexus S by default is charged to around 95% capacity and I could not find any app or tweak to stop the charging at a lower capacity. Thus the only way was to use the manual override and pull the cable which is annoying since one had to monitor the charge state." (Unknown Savings).
Galaxy Nexus is charged by default to the 96% of this capacity, with this new tweak you can gain this 4% (don't know for sure if you can get the 101%) of battery life, in 4 hours screen time, more or less 10 minutes, but it can be detrimental on the long way to the battery physical life.
You can found this tweak in the last nightly of Franco's Kernel, and can be activated via his own app.
You can find more information in Ezekeel post here at XDA.
[MOD][KERNEL]Undervolt of IVA and CORE Voltage, new patches let undervolt the IVA (hardware media decoder) and CORE (GPU Voltage), I'vce been playing with this all the day and I've managed to undervolt a 15-20% de original frequencies. (Unknown Savings).
I understand that with this we are limiting the maximum voltage they can use, letting them to use lower ones according to GPU load. I'm not sure at this (GPU uses smartflex also ¿?) but with a descent of 20% on the voltage could result in longer battery life while playing games or seeing movies.
I'll try further undervolts, but this are my actuals on a stable system.
You can play with this voltages via the last nightly of Franco's Kernel, and via his own app.
Take care playing with this, could result in system instabilities, reboots, freezes, etc.
Links of interest
- BetterBatteryStats, A high battery drain is often a limiting factor for a great user experience.
With BetterBatteryStats you can analyse the behavior of your phone, find applications causing the phone to drain battery while it is supposed to be asleep and measure the effect of corrective action.
- CPU Spy, This is a simple app to display the time the CPU spends in each frequency state. This can be a useful tool in diagnosing battery problems or tweaking your over-clock settings.
It also displays the current kernel information.
- StabilityTest, StabilityTest is a stress-testing tool for android devices with error reporting.
StabilityTest is a CPU, GPU, RAM/memory stress-testing tool for your device, whether stock and unrooted (limited functionality) or rooted and overclocked with SetCPU, SetVsel or similar tools.
Extended Battery
At the end, the best way to extend the battery life is with an Extended Battery, they are not very expensive and only increase a little bit the thickness of the device. They can be bought at several places through the typical places as Ebay, Expansys or Amazon.
Important: Take in account that the CDMA and GSM versions have different batteries and they are not compatible, normally the GSM one is longer and black and the CDMA is wider and blue.
Borrowed from Buddy Revell
Calibration
Once a month we´ll have to calibrate our battery so that the information to be shown on screen is accurate and true. The steps are as follows.
1. Charge the Nexus until the indicator shows us is 100%.
2. Disconnect it and let it discharge until it turns off by herself.
3. Then load up fully charged. Note that this state is reached after one hour approx. since it shows that is already loaded.
Note: There are several apps in the Market that help calibrate the battery, although I have heard that in ICS Google has changed the file location does. Log of our battery so many of them may not work well if they are not updated.
great post especially for a new gnex user. will look through these options thoroughly.
Very nice. Thank you! Took a few suggestions.
Looks like I've got some work to do =D
Sent from my Galaxy Nexus using XDA
edited out
Cool story bro! Lots of good tweaks to maximize battery.
Sent from my Galaxy Nexus using xda premium
What rom is that? You should state that ...
Awesome. Those custom backlight levels are going to save a good amount of battery. I tried using a filter, but it made using the phone in sunlight impossible.
It's working inside well and based on what I see from the custom levels, it should have no issues once I take it outside.
As for the underclocking, comparing iOS and Android isn't fair. iOS has an advantage with its closed ecosystem. I personally overclock the GNex to achieve the same snappiness I had on my iPhone 4S. Sure the underclocking will save battery, but I might as well be using an older phone if I'm going to underclock.
When it comes down to it, everyone's battery is >50% screen consumption. Your custom levels are going to tremendously increase battery life.
gogol said:
What rom is that? You should state that ...
Click to expand...
Click to collapse
It's in my signature, Liquidsmooth v1.25.
myrdog said:
Awesome. Those custom backlight levels are going to save a good amount of battery. I tried using a filter, but it made using the phone in sunlight impossible.
It's working inside well and based on what I see from the custom levels, it should have no issues once I take it outside.
As for the underclocking, comparing iOS and Android isn't fair. iOS has an advantage with its closed ecosystem. I personally overclock the GNex to achieve the same snappiness I had on my iPhone 4S. Sure the underclocking will save battery, but I might as well be using an older phone if I'm going to underclock.
When it comes down to it, everyone's battery is >50% screen consumption. Your custom levels are going to tremendously increase battery life.
Click to expand...
Click to collapse
Thanks
With the iPhone comparison I just tried to emphasize that sometimes underclocking results in the same snappiest system, but yes, is a little unfair though (but I can assure that with the latest Kernels and ROMs that have been released, I have a totally fast and smooth system with only 1000Mhz).
Well done good job
Good guide. Rather than seeing multiple thread's about awful battery life its nice to see people talk about how to maximize their battery life
Sent from my Galaxy Nexus using xda premium
Good guide—thanks for taking the time to make it—but along with it’s very good parts, it has quite a few inaccuracies, is misleading in some places, doesn’t fully explain the ramification of making many of the changes that are proposed and makes questionable changes for very little gain. Amongst other things, my major issues with it are:
You wrongly assume a device that does not get four hours of screen time is not optimized—this would be incorrect as one can get four hours of screen time with the stock ROM and default configuration.
The stock ROM does not allow you to customize the backlight and CPU—so you should point this out.
It’s condescending to the iPhone (while the GN might be better in many ways, patronizing another device has no place in a “guide”).
BinkXDA said:
Good guide—thanks for taking the time to make it—but along with it’s very good parts, it has quite a few inaccuracies, is misleading in some places, doesn’t fully explain the ramification of making many of the changes that are proposed and makes questionable changes for very little gain. Amongst other things, my major issues with it are:
You wrongly assume a device that does not get four hours of screen time is not optimized—this would be incorrect as one can get four hours of screen time with the stock ROM and default configuration.
The stock ROM does not allow you to customize the backlight and CPU—so you should point this out.
It’s condescending to the iPhone (while the GN might be better in many ways, patronizing another device has no place in a “guide”).
Click to expand...
Click to collapse
Thanks, but the guide tried to be a compilation of many procedures that would give you a longer batt life. Some of the recommendations give you maybe 4-5% more autonomy, some of them 0,5%, don't know because I'm not an engineer and don't have the tools and time to measure the actual rate of discharge of the device, I'm only a user that took some time in share his personal experience in the last 4 and a half months with the device.
1. It was a way of talking, did not tried to assume anything because was not thinking in anithing out of the people that are not having more that 3 hours batt time, was a simple way of selling something (a well/bad introduction depending on the eyes or mentality of the reader)
2. We are at XDA and this is a developer device, I asume a minimal technological base, I was assuming this. But I point this out because I also think that will help some people.
3. Tried to emphasize that while the over sold as an ultra-quick device is only 1Ghz Dual-Core, the GNex can be as fast and reliable as the iPhone 4S with the same speed, and also saving batt (and in addition you have 450 more Megaherzs if you want to use them.. if you root). It’s not condescending cause if I would have liked to buy an iPhone I would bought one as the 99% of the people here.
I am a simple user, as everyone here, trying to help people as people has helped me developing great ROMs and Kernels I like positive and concrete recommendations over vague and negative ones.
hey op,
SrTapir said:
If we take in account that the Mega-Ultra-Cool-Fashion-Posh and "Ultra Quick" iPhone 4S has a only Dual Core 1Ghz processor, we can assume that with the same speed we can achieved a very good optimized and well balanced performance-battery friendly system.. and yes, with the last advances in kernels and ROMs, we can have a perfectly smooth system with a top speed of 1000Mhz.
Click to expand...
Click to collapse
i think the iphone is clocked at 800mhz even it has 1ghz
king23adrianc said:
hey op,
i think the iphone is clocked at 800mhz even it has 1ghz
Click to expand...
Click to collapse
Ups!
SrTapir said:
Ups!
Click to expand...
Click to collapse
First of all thanks to all the people for your comments!
I've updated the first post with your recommendations, and added a couple little things.
SrTapir said:
First of all thanks to all the people for your comments!
I've updated the first post with your recommendations, and added a couple little things.
Click to expand...
Click to collapse
The Calibration section is a little confusing. It only takes 1 hour to go from 0% to 100%?
Also, do you know anything about calibration with ROMs that only allow you to charge to 99%?
myrdog said:
The Calibration section is a little confusing. It only takes 1 hour to go from 0% to 100%?
Also, do you know anything about calibration with ROMs that only allow you to charge to 99%?
Click to expand...
Click to collapse
No, it takes 1 hour after the GNex indicates is fully charged. I'll try to change it in order to clarify.
No, sorry, maybe you can "delete battery logs" via recovery. (I never did it, and don't know if can be detrimental).

[Q] How do you Undervolt?

So i have Daemon Controller 3.2 something and I've seen a lot of places mention undervolting. I looked around but couldn't find much information on it.. nothing extensive anyway. So my question is: what are the good things about undervolting (besides battery life) and what are the bad things?
If i undervolt and improve battery life does it decrease performance? Any info here would be awesome. Thanks!
Info here
http://forum.xda-developers.com/showthread.php?t=1611620
PatimusXPrime said:
So i have Daemon Controller 3.2 something and I've seen a lot of places mention undervolting. I looked around but couldn't find much information on it.. nothing extensive anyway. So my question is: what are the good things about undervolting (besides battery life) and what are the bad things?
If i undervolt and improve battery life does it decrease performance? Any info here would be awesome. Thanks!
Click to expand...
Click to collapse
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
TheAtheistReverend said:
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
Click to expand...
Click to collapse
Okay cool, I get pretty good battery life too so maybe I'll just skip UV.. no awesome reward just a lot of risk
There is a balance for reward vs risk there. Undervolting by 50 isn't going to put your phone in danger. But if it gets me a couple percent/an hour of battery life, why not?
I'm a believer in doing all the little things that add up to something substantial. Undervolt, Battery MOD, wifi policies, screen on time, charging habits, Kernel, ridding of problem apps, using things like Juice Defender, etc. These all add up to give me better battery life than you can find on almost any non-Max phone. But it takes all of them together, and a constant eye oout for something else I could be doing.
Undervolting may help you.
I havent been a big fan...on my og Incredible it caused nothing but problems with signal...so I dont anymore although the Sense kernel by Dres is undervolted a tad.
Give it a shot and start with -25 increments. Will it affect battery life? Maybe, but engineering tends to dictate that lower voltages dont always affect discharge rates. Higher voltages certainly affect consumption though (and can also lead to major problems).
TheAtheistReverend said:
The only thing I can think of that you might find as a benefit from U/V is improved battery life.
If you UnderVolt too far you risk freezing and/or damaging your device.
If you successfully undervolt without going too far and causing problems, you should see no negative effect on performance. Just better battery life.
I typically U/V around 50 for all clock ranges. I have never had any negative results doing this. But I haven't been able to prove I get better battery life either. I just take faith in the fact that I theoretically am. I do get wicked good battery life, but that is probably due to many things including kernel, rom, radio, clock speed settings, U/V settings, and other mods. All these together produce noticeable results, where any one by itself would not give any substantial or noticeable improvement.
Click to expand...
Click to collapse
I use the app SetCPU for CPU profiles. If I use something like Incredicontrol to undervolt, will it mess up my phone?
zaza224 said:
I use the app SetCPU for CPU profiles. If I use something like Incredicontrol to undervolt, will it mess up my phone?
Click to expand...
Click to collapse
The only way to mess up your phone is to U/V too far and have the "Save for Boot" box checked and no NAND backup.
Make your NAND and run the U/V settings you choose for a day or two before you check the save for boot box. If it freezes up back off your settings a notch and run it for a couple more days.
I run about 50 under without any problems.

[Q] excessive battery consumption

Hello guys,
a few days ago I bought the notes 8.0 wifi and after a few hours they already had administrator permissions.
I left the tablet that becomes exhausted and completely after a night in office, in the morning I started to make some changes: new rom and kernel immediately immediately!
I state that in Italy are the CEO of an interesting blog where we treat only Google Experience products novel that I'm not really, but ...
Turning now from the Nexus 7 (I still have it) the difference for the better I feel about this tablet but I have noticed, however, an excessive drain on the battery, then not doing anything so important: the hours of active screen only 3/4 albeit with wifi always on!
I tried to set all the Governor also present with heavy undervolt but I have not noticed noteworthy improvements ...
nb. Rom and kernel belong to @civato
Tell me your experience, thanks guys
I didn't understand all of your post, but wanted to share my experience:
Leaving the screen brightness on auto is essential to get reasonable battery life. On full brightness my tablet battery runs out way too fast. I do think this device has the shortest battery life of 7 other tablet/phone devices I have previously used for multiple full days (I cannot judge with less usage). But as long as you leave it on auto brightness most of the time, it has managed to get me through each business day since it was released.
Sent from my GT-N5110 using xda app-developers app
reply
thanks for your expertise ...
you are absolutely right but also the tablet in standby consumes a small percentage of the battery, that's not good, at least to me.
I'll talk with the developers for the right settings in the kernel ... hopefully
I found that I only use a few percent when its in stand by. Heres what I have my settings as and why
Brightness - either auto +5 or 50% switching between the 2 as required.
Sync off.
Power saving mode - on unless I want to play resource heavy games.
GPS off. only turn it on if an app specifically requires it (navfree)
Bluetooth off.
spen battery saving mode on. the spen layer uses charge so no point having it on unless i need it. if im using my 8pi pen i just leave the spen out a little, using it like a switch.
Other battery saving things.
Auto airplane mode - app that turns all the signals off when the screen is off.
trickster mod - under volted by 75 on the CPU accross the board (had a few crashes on 100). also undervolted the GPU and changed the ramping threasholds.
- govner set to lulzactiveq which is a modified interactive but also with the benefit of limiting the cpu when the screen is off.
- set ignore_nice_load to 1. so that nice to have processes are now no longer run. only the higher priority ones are.
greenify - set various apps to hibernate stopping them from taking the tablet out of sleep.
Think thats everything.
The primary settings you listed @hertsjoatmon, are standard on Android (and better on Samsung devices) say: I will use them for years.
The second part is more interesting, in fact undervolt to -75 they had not yet tested on this note 8 but if you tell me that the tension holds well-being.
Also on the GPU did you apply the undervolt?? mmmm
The Governor me most is satisfying, at least in terms of battery life - albeit with some lag micro - is "ondemand" (100 -> 1200) with frequency freeze (of 4 cores), thanks to kernel @civato :good:
Standby does not consume almost nothing but if you use the goodness of the screen, wifi and all notifications accesse lead to excessive battery consumption that even my Nexus 4 behaves this way (having then 2100m)
Piè_Nexus said:
The primary settings you listed @hertsjoatmon, are standard on Android (and better on Samsung devices) say: I will use them for years.
The second part is more interesting, in fact undervolt to -75 they had not yet tested on this note 8 but if you tell me that the tension holds well-being.
Also on the GPU did you apply the undervolt?? mmmm
The Governor me most is satisfying, at least in terms of battery life - albeit with some lag micro - is "ondemand" (100 -> 1200) with frequency freeze (of 4 cores), thanks to kernel @civato :good:
Standby does not consume almost nothing but if you use the goodness of the screen, wifi and all notifications accesse lead to excessive battery consumption that even my Nexus 4 behaves this way (having then 2100m)
Click to expand...
Click to collapse
my clock and voltage settings are discussed here... http://forum.xda-developers.com/showthread.php?t=2319953
I've not really updated any of my threads since coming back from holiday. I will do at some point but im pretty happy with my set up at the moment and have only been lurking on here rather than actively contributing these last few weeks.
the situation seems to have improved a bit, with cuts of volts everywhere: P
let's see if over time more kernels will do miracles ...

Categories

Resources