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.
Related
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.
I found this today on reddit, thought I'd share it with everyone. All credit goes to Lambgx02
I'm running this on CM10 and I've noticed a difference.
Link to OP & Download
Hey everyone,
So, I was experiencing significant lag as we all do from time to time, and decided I was going to get to the bottom of it.
After tracing and debugging for hours, I discovered the source of 90% of Android's lag. In a word, entropy (or lack thereof).
Google's JVM, like Sun's, reads from /dev/random. For all random data. Yes, the /dev/random that uses a very limited entropy pool.
Random data is used for all kinds of stuff.. UUID generation, session keys, SSL.. when we run out of entropy, the process blocks. That manifests itself as lag. The process cannot continue until the kernel generates more high quality random data.
So, I cross-compiled rngd, and used it to feed /dev/urandom into /dev/random at 1 second intervals.
Result? I have never used an Android device this fast.
It is literally five times faster in many cases. Chrome, maps, and other heavy applications load in about 1/2 a second, and map tiles populate as fast as I can scroll. Task switching is instantaneous. You know how sometimes when you hit the home button, it takes 5-10 seconds for the home screen to repopulate? Yeah. Blocking on read of /dev/random. Problem solved. But don't take my word for it .. give it a shot!
Update!
I've built a very simple Android app that bundles the binary, and starts/stops the service (on boot if selected). I'll be adding more instrumentation, but for now, give it a shot! This APK does not modify /system in any way, so should be perfectly safe.
This is my first userspace Android app, so bear with me!
Note that this APK is actually compatible with all Android versions, and all (armel) devices. It's not at all specific to the Captivate Glide.
Caveats
There is a (theoretical) security risk, in that seeding /dev/random with /dev/urandom decreases the quality of the random data. In practice, the odds of this being cryptographically exploited are far lower than the odds of someone attacking the OS itself (a much simpler challenge).
This may adversely affect battery life, since it wakes every second. It does not hold a wakelock, so it shouldn't have a big impact, but let me know if you think it's causing problems. I can add a blocking read to the code so that it only executes while the screen is on. On the other hand, many of us attribute lag to lacking CPU power. Since this hack eliminates almost all lag, there is less of a need to overclock, potentially reducing battery consumption.
If you try it, let me know how it goes.
ROM builders - feel free to integrate this into your ROMs (either the .apk / application, or just the rngd binary called from init.d)!
If anyone's interested, I've launched a paid app on the Play store for non-xda users. As I add features I'll post the new versions here as a thanks to you guys (and xda community at large for being such a great resource). But if anyone's interested in the market's auto-update feature, just thought I'd mention it
Click to expand...
Click to collapse
Thank you OP. ...
I'm going to get the playstore version for support purposes ...regardless of the xda report.
The developer worked hard on this. ...g
Tried it out, noticed an immediate, significant improvement!! If that was a placebo, the OP must have played it up to be a damn good one
I might be crazy (and I'm sure it's just a coincidence) but I seemed to notice an actual IMPROVEMENT in battery life after installing this.
Thanks for sharing!
I'm not sure if I've noticed any major improvement myself, but it has been a little zippier. I keep a very close eye on my battery, so I should be able to report any battery improvements. Hopefully I didn't waste a 1.50 on this app
Sent from my SAMSUNG-SGH-I717 using xda app-developers app
CPA Poke said:
Tried it out, noticed an immediate, significant improvement!! If that was a placebo, the OP must have played it up to be a damn good one
I might be crazy (and I'm sure it's just a coincidence) but I seemed to notice an actual IMPROVEMENT in battery life after installing this.
Click to expand...
Click to collapse
If you're using the apk method, it's literally impossible to have better battery life as mentioned by the guy who made it. It keeps your device awake a lot more often to refill the entropy. The difference may be small enough that it won't affect you but it can't actually increase your battery life.
I've been trying the apk method as well as the other ones without really seeing any concrete difference. Currently running the sysctl method since it's "free" and doesn't use any system resources.
http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/ just a heads up
ChronoReverse said:
If you're using the apk method, it's literally impossible to have better battery life as mentioned by the guy who made it. It keeps your device awake a lot more often to refill the entropy. The difference may be small enough that it won't affect you but it can't actually increase your battery life.
I've been trying the apk method as well as the other ones without really seeing any concrete difference. Currently running the sysctl method since it's "free" and doesn't use any system resources.
Click to expand...
Click to collapse
Haha yeah, that's why I said it was probably a coincidence Said battery "improvement" has since gone away, but my device still seems to be much snappier.
Been on it since its release and it has improved my phone. I will say, don't subscribe to the main thread though, omg notification every 2 secs....its crazy....well it has slowed down slightly but wow
Well. ..
Based on the report by arcee, whom I trust as being a top tier development expert, Im going to shut down the application.
His report is accurate in disecting the hack.
The resources used to run the hack, obviously outweigh the benefits.
It's a near placebo effect modification with no tangible performance advantage beyond what the CPU can already produce with governors and clocking tweaks.
None the less, I do believe the developer to be honest in his attempt in bringing us a well executed application with sincere intentions.
That being said, a thank you is still in order, and a small price of $1.50 is certainly not to high a price considering the work and coding involved. ...g
NO. This does NOTHING. Stop it, people.
Its been a night and day difference on my phone.
Sent from my SAMSUNG-SGH-I717 using xda premium
Another tweak is always great. Thanks for the contribution.
Sent from my SAMSUNG-SGH-I717
Tasty placebo... Seriously, people are still doing this? I thought all the threads were closed as nonsense.
Agreed ..please close this thread...
The mod does nothing...and has been confirmed by XDA ..g
Edit: reported ....people, don't waste your money.
As stated on XDA: http://www.xda-developers.com/android/entropy-seed-generator-not-all-its-hacked-up-to-be/
As is always the case, anything you use here on XDA is done at your own risk, and you assume all liability for your actions. That said, there are times we pass on inaccurate information, and this is one of those times. We do applaud all of our developers for working to find fixes for the things that nag at them. However, we jumped the gun on this, without letting adequate discussion and testing take place.
Click to expand...
Click to collapse
at first: this is not a "whats the best rom" thread.
i have 2 very focused questions:
What are the idle times with those different roms?
Are there some Main feature differences?
Aktually im running cm11 m5 snapshot with smartassv2 Governor. its smooth but the battery life is kinda poor.
Im looking for a rom with long battery life. And i dont care about google now, talking to my phone(ok google) nor i need the special features from the standart samsung rom.
Would be realy helpfull if u can review to my questions. Greetings!
pls apologize my bad english.
1 each phone is different depending on what's installed and running.
2 read there threads or flash each ROM and find out that way. You forgot about aokp?
andrewwright said:
1 each phone is different depending on what's installed and running.
2 read there threads or flash each ROM and find out that way. You forgot about aokp?
Click to expand...
Click to collapse
2. thx for informing abaout aokp!
1. im asking for someone who did a test with the same phone and all roms. i dont ask for different situations, i sked fpr idle time and features!
Probably there is somebody out there who testet it and can present his results
twinko said:
2. thx for informing abaout aokp!
1. im asking for someone who did a test with the same phone and all roms. i dont ask for different situations, i sked fpr idle time and features!
Probably there is somebody out there who testet it and can present his results
Click to expand...
Click to collapse
There are no definitive results, I have used both and I keep coming back to Omni due to the fact that on SlimKat music stutters like crazy when the screen is locked. Also, Omni updates are small enough to update often without having to download a complete update, to many users this a huge deal due to data limitations in certain countries. As for usage, idle time etc, like stated before, that depends entirely on what is installed on your device. Install a bunch of apps that need to constantly receive data updates and you will have battery drain and very little deep sleep. Where features are concerned, you kinda learn to live with limitations due to missing features on a specific rom. If you really want, you can most likely find an app that will bring a missing feature to a rom. I see a lot of people throwing their toys out the cot because one of the other does not have a specific feature implimented, yet the developers have done so with good reason, usually either performance or battery life.
With all said, there are many roms out there, Omni and SlimKat aren't the only players. It's difficult to compare roms nowadays because you are never quite sure if your kernel tweaking or custom kernel with it's hundreds of tweaks is the reason for a device not going into deep sleep either.
Give them all a try and decide for yourself, nandroid backups and apps like Titanium Backup makes it so easy.
cornelha said:
There are no definitive results, I have used both and I keep coming back to Omni due to the fact that on SlimKat music stutters like crazy when the screen is locked. Also, Omni updates are small enough to update often without having to download a complete update, to many users this a huge deal due to data limitations in certain countries. As for usage, idle time etc, like stated before, that depends entirely on what is installed on your device. Install a bunch of apps that need to constantly receive data updates and you will have battery drain and very little deep sleep. Where features are concerned, you kinda learn to live with limitations due to missing features on a specific rom. If you really want, you can most likely find an app that will bring a missing feature to a rom. I see a lot of people throwing their toys out the cot because one of the other does not have a specific feature implimented, yet the developers have done so with good reason, usually either performance or battery life.
With all said, there are many roms out there, Omni and SlimKat aren't the only players. It's difficult to compare roms nowadays because you are never quite sure if your kernel tweaking or custom kernel with it's hundreds of tweaks is the reason for a device not going into deep sleep either.
Give them all a try and decide for yourself, nandroid backups and apps like Titanium Backup makes it so easy.
Click to expand...
Click to collapse
Thx for your long, interessting and helping text!
im missing only 1 thing. if someone flashes all roms, doesnt install any apps. Only new rom and full wipe before, restart and tracks the time the phone has battery. Dont u think this is a possibility to compare the roms battery usage? i think there is no one who does this, but i probably will try this and put down a little table here. so people like me are able to see the rom with the best battery efficiency. so if they decide this rom has not enough performance, they can switch to "battery efficiency Number 2" and so on.
greetings
twinko said:
Thx for your long, interessting and helping text!
im missing only 1 thing. if someone flashes all roms, doesnt install any apps. Only new rom and full wipe before, restart and tracks the time the phone has battery. Dont u think this is a possibility to compare the roms battery usage? i think there is no one who does this, but i probably will try this and put down a little table here. so people like me are able to see the rom with the best battery efficiency. so if they decide this rom has not enough performance, they can switch to "battery efficiency Number 2" and so on.
greetings
Click to expand...
Click to collapse
Sure you can do what you stated but bear in mind how will you compare the battery life across roms..
There should be some standardized test... Like looping video playback or some other method which does not change based on you usage habits..
Sent from my GT-I9300 using Tapatalk
Pa is another you're missing from you're list of developed roms. What you could do is test video playback, calls incoming/outgoing,one game of choice "high end battery draining game" and compere them all. As for the kernel tuning.. Read about what really happens and you will fine not a lot does happen with UV/uc .
twinko said:
Thx for your long, interessting and helping text!
im missing only 1 thing. if someone flashes all roms, doesnt install any apps. Only new rom and full wipe before, restart and tracks the time the phone has battery. Dont u think this is a possibility to compare the roms battery usage? i think there is no one who does this, but i probably will try this and put down a little table here. so people like me are able to see the rom with the best battery efficiency. so if they decide this rom has not enough performance, they can switch to "battery efficiency Number 2" and so on.
greetings
Click to expand...
Click to collapse
You can compare but you have to use that phone for more days not like just one and you have to full charge and then discharge 2 or 3 times till the phone make the correct battery stats. So i think you can test but better with daily use or get an app that drains battey faster well i think this may work
Has anybody yet attempted to compile the 4.3 Kernel from Source Provided yet (device probably use some slight overclocking and light undervolting)? This device has amazing battery life and runs great. This is coming from somebody who has had 5 qualcomm 800 processor phones and no less than 400 phones (yes Really). Most people that i see with higher end phones use facebook and some other social apps, most of the processors are sitting idle for most people. I guess marketing is good now a days. Millions of people with 600-700 dollar phones with most processor cores times at idle and have no clue.
My wife got a Note 4 and I told her not to since most people have no clue of power/price to actual use/needs on a phone. Well yesterday, we kept running into each other in the house and I kept asking her about her battery percentage until at 3pm she started charging her phone and I told her Im at 70% (while laughing). Well she just ordered a HAM2 today. Yes I know you can get a 10,000Mah brick extension for the "high" end phones but damn. I guess I am getting older and seeing behind the hoopla.
Anyways rant off, but seriously any one look at the code yet. Im downloading it now.
afbcamaro said:
Has anybody yet attempted to compile the 4.3 Kernel from Source Provided yet (device probably use some slight overclocking and light undervolting)? This device has amazing battery life and runs great. This is coming from somebody who has had 5 qualcomm 800 processor phones and no less than 400 phones (yes Really). Most people that i see with higher end phones use facebook and some other social apps, most of the processors are sitting idle for most people. I guess marketing is good now a days. Millions of people with 600-700 dollar phones with most processor cores times at idle and have no clue.
My wife got a Note 4 and I told her not to since most people have no clue of power/price to actual use/needs on a phone. Well yesterday, we kept running into each other in the house and I kept asking her about her battery percentage until at 3pm she started charging her phone and I told her Im at 70% (while laughing). Well she just ordered a HAM2 today. Yes I know you can get a 10,000Mah brick extension for the "high" end phones but damn. I guess I am getting older and seeing behind the hoopla.
Anyways rant off, but seriously any one look at the code yet. Im downloading it now.
Click to expand...
Click to collapse
I use to be one of those "gotta have the latest", until I got tired of rooting, flashing (getting older). I just want to turn it on and USE it.
The mate2, WORKS. As long as the OS is stable, and none of the apps I use requires a newer OS, I'm leaving mine alone.
Coworker went from a LG G2, to a Nexus6 (since sent it back, it was "too big), we set the screen brightness to the same level, installed
the same apps on both devices, then ran them side by side. The N6 "might" have been just a hair quicker at launching apps, but NOT
for more than 2 times the price of the Mate2, not to mention the #2 thing I look for in a device (#1 being STABLE), the HUGE battery life.
His N6, would "just" make it through the day with maybe 5-6% battery left over. My mate2 might "just" make it through THREE days of
battery. The value for money, for the mate2, can't be beat.
Nobody has attempted to because 1) some people, like p51, prefer to leave the phone as is, and 2) the people who do want to modify the phone don't know how.
Supposedly there is a 5.0 update later on, but I'd prefer stock Android. But none of us on here know how to create a ROM.
I believe the rom is a pretty good and stable base. I believe that a kernel will provide the most bang for the buck. Ive ran lollipop on a couple of devices already and unfortunately im not impressed much. What they have rewritten for 5.0 is more centered on tightening up the Google ecosystem, (to make them more reliant on and integrated on google). Google is at a point where they are trying to follow in apples footsteps a bit because it makes sense for them. People have adopted one of two ecosystems and now that they are vested they can simplify and get very accurate metrics from users to sell forwards.
Anyways I may see if i can compile this thing, or i may not depending on boredom level and how bad the original code is.
yah what @scobiSTI said.. You put the piece there and the file over there and take out the 0 over there and boom I end up with a calculator program or something.
Lol let's not forget we are posting on XDA... Which is here FOR developing android for devices...
I can only comment on what people like hashcode did for the kindle fire. I'm glad that leaving well enough was not settled for. Because of development with the kindle fire I still use my first gen to this day. So I have no reason to settle for a phone that just works. Oh, one last thing... For the people commenting here. How many of you are boot loader unlocked and rooted? Just saying.
Sent from my MT2L03 using XDA Free mobile app
I've been unlocked since the release of the phone and Rooted before this thread was made. then @modding.MyMind came around and gave us TWRP! love that guy still!
Iguanadon said:
I can only comment on what people like hashcode did for the kindle fire. I'm glad that leaving well enough was not settled for. Because of development with the kindle fire I still use my first gen to this day. So I have no reason to settle for a phone that just works. Oh, one last thing... For the people commenting here. How many of you are boot loader unlocked and rooted? Just saying.
Sent from my MT2L03 using XDA Free mobile app
Click to expand...
Click to collapse
Been bootloader unlocked and rooted since the beginning of this year...and I'm loving it!!
Building the kernel isn't really necessary giving the already seen performance from this device. Could easily be done if you understand how to build from source and know a bit about C. Though typically seen with most custom kernels is a decrease in the battery life due to the more common or favorable features such as juicing up the CPU as a mere example. Plenty of tutorials on how to build from source. Once you get the hang of that you can check out other devs works on github to see what kind of patches they implemented for the purpose of learning, understanding, and applying. I personally find favor in writing scripts more than anything else, or playing around with the TWRP source.
afbcamaro said:
Has anybody yet attempted to compile the 4.3 Kernel from Source Provided yet (device probably use some slight overclocking and light undervolting)? This device has amazing battery life and runs great. This is coming from somebody who has had 5 qualcomm 800 processor phones and no less than 400 phones (yes Really). Most people that i see with higher end phones use facebook and some other social apps, most of the processors are sitting idle for most people. I guess marketing is good now a days. Millions of people with 600-700 dollar phones with most processor cores times at idle and have no clue.
My wife got a Note 4 and I told her not to since most people have no clue of power/price to actual use/needs on a phone. Well yesterday, we kept running into each other in the house and I kept asking her about her battery percentage until at 3pm she started charging her phone and I told her Im at 70% (while laughing). Well she just ordered a HAM2 today. Yes I know you can get a 10,000Mah brick extension for the "high" end phones but damn. I guess I am getting older and seeing behind the hoopla.
Anyways rant off, but seriously any one look at the code yet. Im downloading it now.
Click to expand...
Click to collapse
Exactly. Tired of $100 extra month because of four lines with contracts. Bought my wife note 3 for Xmas. Found one new in box for 450 on swappa. I tend to jump manufacturers each new phone. I plan to stay in the midrange market for the foreseeable future. Only lag I've seen is a little of keyboard lag. Other than that, no bugs or issues yet. And that battery life... First time I haven't charged phone at work in months. I like that it tells me when apps are wasting battery in the background. Great way to eliminate those apps if possible. On my G2 android services was always eating battery.
Looking forward to root just for a couple of specific things. No time these days for ROM flashing.
To fix the keyboard lag, put powersavings to normal instead of smart... 5 minutes projected off battery life was worth it to be able to write faster
Bobvark said:
To fix the keyboard lag, put powersavings to normal instead of smart... 5 minutes projected off battery life was worth it to be able to write faster
Click to expand...
Click to collapse
Or use Fleksy keyboard which is a super fast tapping keyboard. It works without lag on endurance mode.
Sent from my MT2L03 using Tapatalk
arcadesdude said:
Or use Fleksy keyboard which is a super fast tapping keyboard. It works without lag on endurance mode.
Sent from my MT2L03 using Tapatalk
Click to expand...
Click to collapse
ok, I'll give that a try... I tried swipe and it was also laggy... will try Flesky.