Related
Ever since I first released an undervolted kernel (can you believe that it actually used to be a new idea? Seems so normal now), its been a mad dash to see how much further down the voltage can be pushed. In light of recent events, there has been controversy regarding whether or not dropping below ~925mV actually begins to negatively impact battery life.
Without getting into the technical details behind why I believe that going that low actually does affect battery life, I'm conducting a blind study. I'm going to produce 3 kernels at three different voltages. I'm then going to send these kernels randomly to people that sign up on the attached spreadsheet in order to collect data for 7 days.
I know that this won't be 100% accurate, but I feel that if we get a large enough sample size, over 7 days, the general trend should emerge.
What I ask for you to do if you want to participate is sign up on the attached spreadsheet and try not to change your rom/usage patterns within these 7 days. Just go about your day and record your values at the end.
You will not know what the voltage of the kernel you are receiving is, so there will have to be a certain degree of trust. I promise I will do my best to not blow up your phone
This truly has to be a community effort. The more people we have, the better. Once the study has been concluded, I will reveal which kernel had the best battery life for the most amount of people.
Please spread the word about this, the more it is on blogs and the like, the greater the sample size and the more accurate the results.
Link: http://bit.ly/9YjM5X
UPDATE:
The kernels have all be emailed to people that gave me an email address. Tues-Sat, please run the kernel that is labeled CONTROL. Do not alter your day to day usage from what you always do. At the end of each day please record how long you were off charger and your percent battery left. Use your best judgement for giving statistics. The more detailed, the better.
Sunday-Thurs we will run the TEST kernel. Again do the same thing and record your usage daily.
It is VITAL that you record the statistics at the end of the day every day.
As an added bonus, I included the memory modification by coolbho3k because I know you all want the latest and greatest
Will it matter what battery we have? Or is stock battery required?
Four Fourty Four said:
Will it matter what battery we have? Or is stock battery required?
Click to expand...
Click to collapse
doesn't matter as long as you post your previous results so we have something to base it against.
This is a fantastic idea. Might actually help me recover from my kernel flashing compulsion. Prolly not though....
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
jblazea50 said:
Persiansown, what do you mean by "record your values at the end"? Are we to take a log of battery usage or just writing down on the sheet what the usage was like each day?
thanks
Click to expand...
Click to collapse
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
persiansown said:
Its going to be subjective but I'm trying to figure out the best way to record them right now. I don't need any feedback values until I actually send out the kernels though
Click to expand...
Click to collapse
yeah, i understand that it's not needed until after we start using the kernel; just wanted to know what you were actually looking for, and if it wasn't subjective
thanks and looking forward to this
im really interested in this. would it also be possible to give feedback on reception? because as of late my signal has been worse with all the uv kernels...
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Hey persian, this is a great idea!!! to get to the bottom of all this.
Can I suggest something though, and hope I don't get flamed for it, or hope you wont take it the wrong way. But will you include, an AVS kernel running 800mV as well? There have been discussions about this also. Thanks!
Each tester would have to test all three kernels and try to maintain roughly the same useage. Was this your plan?
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
This is a good approach. But I think for it to be even more standardized one would need to run this completely app and theme free. THe interaction between certain apps and usage is an unknown variable. For example, how much does K-9 mail draw? It goes without saying that themes have some sort of affect on behavior. So IMO, to be as objective as possible you would need to remove all sources of ambiguity to have this test mean something. Just my two cents
pjcforpres said:
We could also look at time spent "running" in spare parts... but that would be much more complicated and less accurate (I would hate to do the statistical break down on that)... but it would be much quicker and would provide some nice info as well... ie 5 hours spent running and 7 hours sleeping used 80% battery... where as 1 hour running and 11 hours sleeping used 50%... but we would also have to factor in so many other aspects and track those to get a truly accurate picture, ie WiFi or 3G or 2G... what is your screen brightness... and so forth.
Click to expand...
Click to collapse
That would be pretty complicated and I think Kmobs would need a grant to run the statistics. I think there would have to be a baseline established like GPS off, brightness set to x percent, bluetooth off etc. And I think as Kmobs knows, each chip was not created equally.
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Correct . This is how I thought he was gonna do it. And what I think is best.
jblazea50 said:
Persiansown, I don't think you need to start with a baseline in order to compare. Once you send out the kernel and we use it for 1 week with normal usage for each user. At the end of the week, you can send out another kernel, exactly the same this time for everyone, and we can use it for few days and we will be able to notice the difference.
Click to expand...
Click to collapse
pjcforpres said:
How are we going to set the baseline? The best way to eliminate the potential for usage differences to skew the results is for us to all run the exact same kernel for X amount of time to set a baseline, then do the blind test of the 3 different kernels, and compare the difference between before and after.
Click to expand...
Click to collapse
persiansown said:
Yeah I've been trying to think of a way that would take less time, but I think that way would be best. Anyone have a better suggestion?
Click to expand...
Click to collapse
I was trying to think of a good way to get a baseline to compare to for every one and this is my sugestion. Make three kernels at 850, 925, and control/stock. Send everyone on the list two kernels, one of the two UV kernels and one stock/control. Allow them to run the first kernel for a certain number of days, record data, then send everyone the second kernel and do the same. Randomize who gets the control first or the UV first and keep it blind. (Don't tell them which of the two is the control obviously.) This way half test the 850, half test 925, and all test the control/stock, giving you an accurate baseline for everyone's individual phone usage and battery size.
Scientific Method FTW!!!
awesome idea.
Count me in...I will sign up when I get home from work tonight. This is an excellent idea. Ideas lke this is what make xda the number one source for android information.
Was just thinking about buying the app SetCPU for root users, and was wondering if I was actually knowledgeable enough to know what I was doing. And I'm probably not.
So, could you give me the details of what this does? I know OC improves performance and UC saves battery, but is there anything else I should know?
Would this app even be necessary since the Atrix already has good battery life? I get about 18 hours with heavy use.
Basically just tell me what I need to know about SetCPU.
Ok. I guess nobody wants to help.
Never live in the past but always learn from it.
Tennis11 said:
Ok. I guess nobody wants to help.
Never live in the past but always learn from it.
Click to expand...
Click to collapse
I've never used this software before and I'm interested as well but you're jumping the gun about this... you only posted 2 hours ago...
Sorry.
Never live in the past but always learn from it.
Gotta give more time for people to reply... it's not uncommon for a thread to not have a reply for a day or 2.
As of now, it can only underclock the atrix... no overclocking really. It's a simple program in terms of ease of use. There's a minimum and maximum setting. You can lower the max to underclock if you want to save battery and you can increase the minimum performance. Someone said they felt the phone ran better when they increased the minimum, though I honestly don't see much of a difference. Increasing the minimum will cause more battery drain.
For now, I don't really see a use aside from underclocking to save battery life. I haven't personally tried that as, like you, I have been satisfied with the battery life. If I knew I wouldn't be able to charge the phone for a while, I might give it a try, but haven't really wanted to bother with it. Otherwise, you can toy around with it for a few minutes. I'm hoping we'll get an update so we can overclock sometime.
Yesturday I woke up at 5 am and flashed 1.2.6 to remove all the buggy ROM I had installed. I then rooted and downloaded a few root apps; setcpu, TI backup (for freezing some worthless moto crap), and root exporer. Then using setcpu I set my max speed to 760 and made a profile so that when the screen is off it sets the max speed to 312. I really didnt start using the phone heavily untill about 4 pm (at this time I think my battery was reading about 89%). When I say heavy, I mean more than I would normally use in one day. At 1 am this morning, still on my phone, barely able to hold my eyes open, the battery was at 10%. I really dont know if setcpu contributed to my battery length, but I'm leaving the current phone setup alone.
Hi there,
probably that request would make more sense in the developer forum but i didnt post enough yet
Actually i get insane battery batterylife with the bali 1.8.8 UV version, therefore i tried the non UV version with even more lowerd voltages via set cpu. it was stable but drained a lot faster. don´t know why.
so my request would be "pre-undervolted" bali kernels that might have even longer batteryliftime. Any hints on that? Someone who is able to compile something like this?
Best regards,
vibrantoparanto (from germany)
Hint' Bali X+Voltage control app= win !!!
Sent from my SGH-T959 using xda premium
^^ that is your answer....currently what im using
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
vibrantoparanto said:
bali-x is what i used before - i lowered the voltages up to -150mv with some frequencies but it still gave me only about half the battery lifetime (less than 24 hours with moderate use) then i get with bali uv. What did you use to manually undervolt and how is your battery lifetime?
Click to expand...
Click to collapse
i hate to burst your bubble, but youre chasing a ghost. uv'ing will not produce very noticeable changes to your battery life, especially if were are talking baout different versions of the same kernel.
take a look at this: http://forum.xda-developers.com/showpost.php?p=21024393&postcount=8
Cannot agree with that. I tried *a lot* and flashed different roms and kernels for years now. With stock kernels i get up to two days standby with low/moderate use, with bali UV i get almost three days. I have no idead why, but at least the standby time differs dramatically between kernels. At least thats for sure - under load that might be another thing. But probably you´re right and its just a "good standby behaviour" which would hardly benefit from lowered voltages. Would be still interesting to try a hardcore UV kernel
TopShelf, it is funny that you posted that note/post b/c I was just getting ready to PM you that I put part of it in my guide like I mentioned a week or so ago and the apps too.
Take a look at the Guide and maybe you will find some answers to your questions.
If you want to UV to the max, then you will have to test that yourself b/c every Vibrant reacts differently to OC/UV. Step it down -25v each day (don't set on boot until you know they work) and see where it freezes. There are OC/UV examples in the guide but beware, they are both for MIUI kernels.
Is there probably any admin out there who understands what i talk about and can move that thread to the developer forum?
this thread belongs here, you posted in the right section. posting in development will not get you answers from developers, it will only get you yelled at by hall monitors.
it is a common misconception that "developers" ONLY visit the "development" section. this is far from the truth.
sorry to say, the reason you have not gotten answers isnt because you posted in the wrong section, but because requests like these are pretty much never honored. the reason is because if a developer decides to make a slight alteration to a ROM/kernel for a member, he will then get BOMBARDED by dozens of other members who have tiny little tweaks that they would like in their ROM/kernel
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
Since you didn't like the answer you got, for clarification purposes you are basically asking for a dev to use their time for FREE an modified/debug/test a kernel with your requirements just for your own sake ?
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
i can prove to you that UVing does not make that much of a difference. if youre willing to learn, try this little experiment:
-UV your phone using your current settings
-put your phone in airplane mode
-turn it off
-charge it to 100% while its off
-after it boots up, leave it in airplane mode and immediately lock the screen
-let your phone sit idle in airplane mode from full charge to death (record the time)
--------------
Once youve done this, repeat all of the above steps but with STOCK VOLTAGE. record the time.
now compare the two times. i would be willing to bet a large sum of money that it is not a notable difference, if any.
my point is instead of trying to convince yourself that your theory of UVing is correct, why not do a TRUE battery life test, and simply find out for yourself. you cannot run true battery tests while you are actually using your phone becuase phone usage is massively different on a day to day basis, even if you dont think it is, it is. there is background data, text messages/calls, notifications, etc. (which is why i said to put it in airplane mode, that way its just sitting there, with little to no variables)
i guarantee you that you are putting way too much thought into voltage settings. they do not help as much as people want them to. dont say im wrong until you actually try what i said above. although youre probably nto going to.
vibrantoparanto said:
Still trying to bring back some life to my request with this argument: I just checked my girlfriends device (using zendroid 2.1.2 with bali 1.8.8uv) and couldnt believe it: 3 days and 14 hours since unplugged with 8% left. The battery is a stock 1500mHa. And as its my girlfriends phone its definity not "overtweaked and calibrated". Personally i care much more about standby time than super heavy usage (guess that should be fine then too).
Click to expand...
Click to collapse
sorry, but this does not prove anything. what are you comparing it to? your phone? you cant compare her battery life to your own unless you guys have the same exact setup, same exact apps, and same exact usage habits, etc.
you are not going about this battery things the right way. you NEED to be willing to learn more instead of trying to come up with your own reasons in your own head as to why your battery gets a specific lifespan. If getting THAT MUCH more battery life was as easy as UVing your phone, dont you think the manufacturers would incorporate that and use that as a marketing strategy?? "New from Samsung, the Galaxy S III!!! This will revolutionize the mobile industry, curing the battery woes across that smartphone world...now with lower voltage for drastically improved battery life!! Pick yours up today!!"
It's not that easy, you need to read up on what affects battery life.
thank you for your thoughts topshelf, but as i posted earlier i am on that topic for years now and i really tested a lot. not as scientific as running phone on idle with different frequenzies but trust me: I know a whole lot about this topic. Also i share your thought that the voltage is not that important in the end. On the other hand i have to say you guys are quite ignorant about my observations i did earlier:
1. The bali-x kernel with manual undervolting provides (provable) worse battery lifetime than
2. the 1.8.8uv kernel.
Conclusion: As you say it is not that much about the voltage but about the way the kernels work as a whole. On the other hand it would be *very* interesting if the insane battery lifetime of bali uv could be even further improved. And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Last but not least: It is true that different roms provide significantly different battery lifetimes - for whatever reason. Some roms turn your phone into a handwarmer, others give you almost the standby times you were used from the non-smarthpones. And i think even the big companies have a hard time to write device specific code that is highly optimized - i mean you still get new devices with gingerbread instead of ics and so on. conclusion: on the software side *is* much room for improvement if it comes to battery lifetime on most devices.
just my 2 cents
vibrantoparanto said:
i wanted to point out that this is a very interesting kernel with great battery lifetime. if you have a look at all the other threads of people desperatly trying to get 24h of battery then you probably wouldnt consider this request as "wasting free time of others for my own sake".
Click to expand...
Click to collapse
Look at your post, you and "others" are asking for some one to do research and development on their free time and for free ? little selfish on you.
Look at all the kernels thread in the development section and read thru all the comments, I bet there is far more people whining and complaining about this and that, than providing actually constructive and monetary feedback to the developers.
Its not as easy as it seams, ecotox already tried this before with his ultra low power kernels and some reported great succes while others couldnt even boot, it goes down to the quality of the silicon on each particular phone. no dev has the time/money to develop such request considering all the different variables involved.
lastly if you are so fond on this idea, why dont you take the initiative and learn to compile and patch and make your own kernel ?
Diff phone but a good simple guide to read:
http://arighi.blogspot.com/2011/08/howto-custom-kernel-on-samsung-galaxy-s.html
basic read:
http://stackoverflow.com/questions/5529470/how-to-compile-linux-kernel-for-real-android-phone
basic read:
http://igottadroid.com/wordpress/?p=61
For latest source:
http://opensource.samsung.com
"Be the change you want to see in the world." Mohandas Gandhi
Simple: If you want to change the world, start with yourself.
I'll read those links. Thanks for the info.
vibrantoparanto said:
And no i wont put my phone to sleep for days in order to do scientific test (whoever is willing to i will donate - battery lifetime almost like astrology)
Click to expand...
Click to collapse
im not trying to pick on you, but this sarcastic response shows your overall attitude that jrafael is trying to make you realize. you want somebody to take time out of their day/night to do something for you...yet you arent even willing to let for phone sit for a day in order to learn a thing or two...letting your phone sit doesnt even take any effort, compiling a kernel takes a lot more effort than that
i hate to say it, but why should someone help you, if you dont want to help yourself.
thank you jrafael for the links - thats a great read.
@topshelf: still think you overreact here. For one who has developed it and has the workflow it is a matter of a few minutes - and no one is forced to do anything unless he thinks its might be worth it - maybe its inspiring? i am just asking. not everything idea must be done by the one who thinks about it. and the quote about battery life is true i would say - we are really lacking valueable info on battery drain with different setups.
Hi all,
I was looking into overclocking and underclocking the hummingbird processor withing my galaxy player 5.0
The overclocking is obviously for fun (I know the risks to the CPU and battery), the uderclocking is more so for power management.
I so far have not been able to go past the 1 GHz on the stock kernel.
Has anyone else tried this on stock/custom kernel and gotten any descent results?
I'm intrested in your expierences.
---------------------------------------------------------------
I'd upload the 5.0 compatible kernel and ROM into my device to use it and try it out; I found it on this sight, but I have been stuck on attempting to backup my current Kernel and ROM, as I do not want to loose it.
(I'm trying to do it "manually" with a program that was meant for something totally different, its interesting on the parts of data I could dump, but nothing is usable).
But aside from that, I have been trying different things with just the root on stock kernel and ROM, and I have found a few things that were fun to play with like the droid wall and an SD speed up...
-----------------------------------------------------------------
honestly I do not see anything else I need/can use the root for right now...
An I missing something? Is the android that open...?!
(This is coming from someone who worked and worked to unlock an iPod touch and turned it into an iPhone and partially into a pocket PC)
I remember the kernels name: Entrophies Kernel (idk how to spell it)
(Its on this forms sight in a different category somewhere)
-I'd use it, but first I'm putting back the stock charging and battery management, I personally do not like the settings he has, Li-Ion Polymer batteries like a complete charge, and a steady charge with a taper at the end...
-----------------------------------------------------------------
Any thoughts and experiences on anything I had not asked about is also welcome.
Everywhere I look for information about this device, I keep finding random one posts with questions and never any answers.
Also, people seem to not know about this device, and also not know how to modify and back its data up, including me with my failed atempts... o_o
Ultimately, if I can figure enough out about this device, because everything I have found so far is scattered about online, I'd like to make a post and dedicate it to the galaxy 5 player eventually, with up-to-date (or as close as possible) info on many things. Because thats the biggest problem I see, nothings ever centralized.
If you have root then This should work on your 5.0 player. I just installed it (stock) to try after seeing your post and i already have my 5.0 overclocked to 1.1ghz
Tegrak Overclock is a great utility to over and under clock your CPU.
[root]How to back up your current kernel U.S 5.0 YP-G70
Download MDump Partition dumper v0.02: link in signature!
Open MDump on your device and select "mmcblk0p11"
Rename the file: mmcblk0p11.mdump -> zImage
Touch "Start Dump"
Move the file to a linux machine and put it in a tar ball. (example command: tar -H ustar -c zImage > kernel.tar)
You now have a backup of your stock kernel which you can reflash using odin! (kernel.tar)
Update: I just noticed that you wanted the ROM too, it's mmcblk0p13. You can just dump that as well; rename it "factoryfs.rfs" and include it in the tar ball.
I plan on eventually adding support for clocking at 1.2 GHz and voltage control - I've just been busy with some issues with my I777 kernel (SoDs... ) and busy with real life in general.
I won't be just grabbing rumirand's patches as his use a slightly different approach than the netarchy-style code I prefer.
wow thanks everyone for the fast replies, I'm replying to each post in order, I added quotes to show which ones I am replying to.
murph5525 said:
If you have root then This should work on your 5.0 player. I just installed it (stock) to try after seeing your post and i already have my 5.0 overclocked to 1.1ghz
Click to expand...
Click to collapse
Thanks for the link, I added the app to my device, and overjoyed, I clicked on the 1.3 GHz setting and applied it!
I do not see much of a difference as my device never lagged, if that, before.
I tried a few benchmark utilities, and it seems to surpass almost all the single core CPU phones I looked at...
dunca123 said:
Tegrak Overclock is a great utility to over and under clock your CPU.
Click to expand...
Click to collapse
I was playing with the underclocking features, and my already 2-2.5 day battery looks like it will last another day...lol
Meticulus said:
Download MDump Partition dumper v0.02: link in signature!
Open MDump on your device and select "mmcblk0p11"
Rename the file: mmcblk0p11.mdump -> zImage
Touch "Start Dump"
Move the file to a linux machine and put it in a tar ball. (example command: tar -H ustar -c zImage > kernel.tar)
You now have a backup of your stock kernel which you can reflash using odin! (kernel.tar)
Click to expand...
Click to collapse
I was not expecting this... Thank you very much, you just saved me a lot of trouble!
I'm trying this in a few days, I've got a couple tests to study for this week...
Entropy512 said:
I plan on eventually adding support for clocking at 1.2 GHz and voltage control - I've just been busy with some issues with my I777 kernel (SoDs... ) and busy with real life in general.
I won't be just grabbing rumirand's patches as his use a slightly different approach than the netarchy-style code I prefer.
Click to expand...
Click to collapse
I really like your kernel, you have done a nice job with it!
I was just wondering if you are keeping a single serries of the kernel or one with the modified power management, and one without?
Reason asking, is that I'm an EE, and I know a few people who work with battery management, and they all tell me the Li-Ion Polymer batteries like to be fully charged. I'm just curious as to your approach/reason behind stopping the charge just short of the top?
I like your selections for the custom charging with the kernel for quicker charge times... when I eventually get your kernel onto my device, I'm going to see if I can change settings while its installed, kinda like a power charge for when needed, and a regular charge for over night for less stress...
-------------------------------------------------------------
idk, I'm new to android, I've been stuck in i-Devices lingo for a long time and I'm slowly figuring this android stuff out...
So far, the only real thing I actually needed root for is overclocking and underclocking, droidwall, and tor... I like how open the system is (aside from the kernel/boxroom seeming to be locked when my friend tried a program called adb on it the other day).
Just curious, anything fun I can do with a custom kernel/rom? the only thing I see it can do so far from searching a few links is themes? idk, i need to look into it more...lol
I came across running ubuntu linux on the device through a vnc, even though its installed on the device... I was thinking of trying that if it looks like its ok...lol
I'm just a bit excited, I have this thing that can do so much, but idk what to do with it other than using it as a free wifi phone so far...lol
zBusterCB87 said:
I really like your kernel, you have done a nice job with it!
I was just wondering if you are keeping a single serries of the kernel or one with the modified power management, and one without?
Reason asking, is that I'm an EE, and I know a few people who work with battery management, and they all tell me the Li-Ion Polymer batteries like to be fully charged. I'm just curious as to your approach/reason behind stopping the charge just short of the top?
I like your selections for the custom charging with the kernel for quicker charge times... when I eventually get your kernel onto my device, I'm going to see if I can change settings while its installed, kinda like a power charge for when needed, and a regular charge for over night for less stress...
Click to expand...
Click to collapse
I'm an EE myself. That's odd - all information I've ever seen says that Li-Ion and Li-Po batteries do NOT like to be fully "topped off" or "trickle charged".
I'll try to dig up my sources later, but, from memory:
Overcharging them can result in metallic lithium plating out, which leads to permanent capacity loss. This is why all Li-Ion chargers stop charging once current drops below a certain rate in the constant-voltage phase. In the case of almost every Samsung I've ever used, CPU/power usage counts against the charge current limit - so I'm REALLY paranoid about the charger terminating properly, which is why I make it cut off earlier, as a way of offsetting some of the stress on the battery that the charging rate bump creates.
Also, Li-Ion batteries stored at maximum charge will lose capacity far faster than ones stored at around 50% charge. (This is why almost all new devices have batteries only 50% charged or so.)
I may eventually add a feature to disable the increased charging rate at runtime, however, in the case of the Galaxy Player:
It has a 2500 mAh battery, so 800 mA is actually still less than C/3 charge rate for the battery, whereas on most Galaxy S phones, they charge at 600 mA for an (approximately) 1650 mAh battery, making charge rate slightly more than C/3.
I also reduce charge rate below stock near the top - the technique is inspired by this: http://www.engadget.com/2011/02/20/apple-patent-application-points-to-denser-batteries-improved-ch/
idk, I'm new to android, I've been stuck in i-Devices lingo for a long time and I'm slowly figuring this android stuff out...
So far, the only real thing I actually needed root for is overclocking and underclocking, droidwall, and tor... I like how open the system is (aside from the kernel/boxroom seeming to be locked when my friend tried a program called adb on it the other day).
Just curious, anything fun I can do with a custom kernel/rom? the only thing I see it can do so far from searching a few links is themes? idk, i need to look into it more...lol
I came across running ubuntu linux on the device through a vnc, even though its installed on the device... I was thinking of trying that if it looks like its ok...lol
I'm just a bit excited, I have this thing that can do so much, but idk what to do with it other than using it as a free wifi phone so far...lol
Click to expand...
Click to collapse
Well, on many Android devices, root is needed to kill carrier bloatware. It happens that wifi-only non-carrier-branded devices tend to be less mangled and require less debloating. (Often none...) I've frequently run stock system firmware with custom kernels on wifi-only devices for long periods of time - but carrier-mangled devices almost always need an immediate debloat.
Right now my rom and kernel is stable but would like to have a little more battery life and consider undervolting a little.
Just wondering whether the gains of soft undervolting (-25 / -50 / -75 across all steps) are visible in terms of increased battery lives for our GS2. Anyone did any test/comparison to determine if your battery life is better/ overall temp of device is lower?
Thanks in advance!
Get Gsam battery monitor from playstore and under volt -25 and test for 2 days aleast for freezes and sods. Then drop to -50 and so on. Some phone wont drop by -25 without sods. Also setting cpu to 1000mhz Saves battery not having to jump to 1200.
In my experience, some increase in battery life. I guess it depends on what kind of user you are. If you really chew through battery & find yourself reaching for a charger/spare battery halfway through the day, it might be significant/make a real difference to you. If you're someone who charges their phone overnight/uses the phone relatively 'normally', you probably wouldn't notice any great difference, and it might not be worth your while going through the time/hassle of working out exactly how much undervolting your CPU can handle.
Well, I've read some threads on undervolting and I think having a scaling stability test using the StabilityTest app could save quite a lot of hassle to do testing for cases of freezes and SOD. That was what got me thinking about doing some undervolting but not too aggressive to the point that I'm bordering on unstability, thus this thread! :cyclops:
Ok then max Uv -50 just test that -75 prob wont work anyway without problems
andrewwright said:
Ok then max Uv -50 just test that -75 prob wont work anyway without problems
Click to expand...
Click to collapse
Just wondering if -25 will have any effect at all. Hmm.
Anyway @andrewwright you mentioned something about Gsam battery monitor, it seems to do the same as betterbatterystats. I have BBS, so that's enough right?
. Its up to you what battery monitor you use :thumbup:. With -25 shouldn't be a problem. Each phone is different. Mine is group 1 which is a bad group to have but I can and am Uv by -50. And all ok
andrewwright said:
. Its up to you what battery monitor you use :thumbup:. With -25 shouldn't be a problem. Each phone is different. Mine is group 1 which is a bad group to have but I can and am Uv by -50. And all ok
Click to expand...
Click to collapse
Haha yeah just checking to make sure its not some special app that does something else special :good:
Well, but -25 probably won't make much of a difference right? I have group 3.
iamatechnoob said:
Haha yeah just checking to make sure its not some special app that does something else special :good:
Well, but -25 probably won't make much of a difference right? I have group 3.
Click to expand...
Click to collapse
Have a go and see.
Will do right after I do a nandroid
Thanks for the help anyway!
iamatechnoob said:
Will do right after I do a nandroid
Thanks for the help anyway!
Click to expand...
Click to collapse
Just check the link below to gain some info on OC/UV before proceeding ma8
http://forum.xda-developers.com/showpost.php?p=34153152&postcount=15576
Sun90 said:
Just check the link below to gain some info on OC/UV before proceeding ma8
http://forum.xda-developers.com/showpost.php?p=34153152&postcount=15576
Click to expand...
Click to collapse
Read that before, twice!
Sun90 said:
Just check the link below to gain some info on OC/UV before proceeding ma8
http://forum.xda-developers.com/showpost.php?p=34153152&postcount=15576
Click to expand...
Click to collapse
So undervolting is useless.Display takes much power so decreasing brightness is the only way to save maximum juice.
umair42 said:
So undervolting is useless.Display takes much power so decreasing brightness is the only way to save maximum juice.
Click to expand...
Click to collapse
well, its not that 'Undervolting' is useless, but while doing so u have to take some risk, which IMO do always bring about bad results (rather than saving some Juice on ur batt, it might cause instability most of the time ).
So it would be better, the same is left to devloper's of Kernel's since they know what they r doing
This is why I have said little steps first.
I'm not going to say I'm right when a Rc is here saying don't do it but there are risks in pretty much every thing on xda.
andrewwright said:
I'm not going to say I'm right when a Rc is here saying don't do it but there are risks in pretty much every thing on xda.
Click to expand...
Click to collapse
Pretty damn right you are, I guess that's how xdadevelopers came to rise isn't it? :victory:
But well to each his/her own, there seems to be a healthy bunch of people on this forum that loves their undervolting but yes I agree that to tech noobs like me, maybe we shouldn't mess around so much unless we know for sure what we're doing haha
Thanks for the help everyone! Appreciate it!