I thought it was worth starting a thread specifically for data concerning the Skyrocket stats. For other folks posting, OC'd scores are welcome, but please also provide info on your OC frequency. Quadrant scores are pretty good random number generaters, but that's about it. If you want to post them, that's fine, but the variance is so high it's worthless trying to actually use them for reliable benchmarks. Several others are far better. (CF-Bench, Passmark, Antutu, etc.)
CF-Bench is a nice benchmark - only a 2-3% variation in the tests I've done so far, although there aren't any graphics tests unfortunately. There are several posts in this thread with CF-Bench results for comparison.
Monjori really pushes the GPU shader, is repeatable, and doesn't really depend on the CPU speeds that much. Thanks to Da_G for pointing it out.
[Update 12/29/2011] - More Battery Information (T989)
I recently purchased a battery from amazon (based on the comments that it was fully compatible with the Skyrocket.) Samsung ET-CGPK004GSTA T-Mobile SGH-T989 Battery Charger with Stand
The results have been amazing, with over 74 hours of battery life in my first test. Granted this was with light use, but the battery life has been by far consistently better than the one that my phone came with. Has anyone purchased this battery and had the same level of success? I seem to remember having to clear out the battery stats, but once I did, everything worked just fine.
Note that the serial numbers are slightly different, but all of the specifications seem to be identical otherwise. I didn't check to see if NFC was working however, it's not something I'm likely going to use.
Additional details are in post #56 of this thread, but I'll post the screenshot here. (Note that the desk charger I purchased also comes with the battery.)
[Update 12/10/2011] - Battery Information
It's been a while now since I've posted, so I'll try and clean up some of the misconceptions about the battery in the Skyrocket.
The below results are using Da_G's Kernel release 0.3. They are going to be somewhat better than stock, given that I was using both CPU profiles for Under/Over clocking to boost battery/performance respectively, but it was also a fairly high workload with an hour or so of GPS usage while driving, Performance Testing, long screen display times, and so forth.
To cut to the chase, From 100% to 10% Battery, I hit 31 hours in this test. Theoretically I could have received considerably more on another test when I had very light usage (26 hours from 100 -> 45%), I had to charge my phone for a trip the next day so I didn't finish it up.
On to the screenshots!
Total time and Utilization graph:
Time spent in each state:
End of test:
Estimated JuiceDefender Savings:
Current JuiceDefender Settings. These are hopefully close to what I used during the test, but I'd forgotten to take a screenshot. Hopefully they are close.
[Update: 11/20/2011] - Monjori scores, DA_G's OC kernel 0.4-pre.
(No screenshots here since they just show the FPS after the test.)
Stock Freq, ondemand : 47 FPS
Stock Freq, performance : 51 FPS
1809 Mhz, ondemand, 48 FPS
1809 Mhz, performance, 51 FPS
Scores from Da_G, same kernel:
Current tweaks are pushing 6700 in Antutu, 8200 in CF-Bench and 51 fps in monjori. These are currently the only benchmarks I am validating the kernel against as they are very repeatable (all tests within margin of error) unlike Quadrant!
Those scores are at 1.809GHz OC, on my 0.4pre kernel
Click to expand...
Click to collapse
[Update: 11/19/2011] - CF Bench Scores
This is using Da_G's OC kernel .3 @ 1.782 Ghz. Nice results with a linear ramp up in scores - what you'd expect with a reliable benchmark that mostly factors in CPU. I'm having some stability issues with graphics benchmarks, but there should be a fix out for it soon. I'm not going to bother with Quadrant - just glancing at the Dev thread shows wild variations in scores, exactly the same as what I saw. Gotta love those 1980's apple II style graphics though!
Another nice feature of this kernel is a stable 54 Mhz frequency! This means great battery savings.
[Update: 11/13/2011] - CF Bench Scores, Stock kernel.
{
"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"
}
[Update: 11/9/2011] - Passmark scores
I was originally going to post data from mobilebenchmark.net showing our results vs. the SGH-I777, then I looked closer and saw the charts were based on one sample. It's a good benchmark, currently in beta, and I'd encourage folks to get it from the market and submit some results. My results were 1660, or 8.2% higher than the OGS2 (based on 41 samples). I'd be interested in seeing what other people get.
This benchmark certainly has much more realistic tests than Quadrant. At least for now the SGH-I727 is one of the fastest phones available. I'm a little surprised we beat them out on the 3D graphics ranking (keep in mind this is still beta software) but at least it's a much more realistic test of what these phones are capable of doing. I'd be interested in the specific score breakdowns here to see how the CPU tests were broken down.
Main Site
Overall scores
3D Graphics Rating
Original Post:
Just wanted to get some benchmark scores and screenshots. If you have the OGS2 and would post benchmarks for comparison, I'd appreciate it. (Screenies as well so all the numbers can be compared.)
Quadrant seemed whacked to me - it was giving me scores all over the place, both low and high.
Best AnTuTu benchmark run: 5956
Some battery history. Basically around 10 hours of battery time went from 100% to 25%. It was fairly idle after 6pm, but I did some moderately heavy benchmarking at one point and had > 1hr at full clock frequency. This was largely at 50% brightness, wireless/bluetooth/gps/sync all on.
I'll grab and post more benchmarks tomorrow.
AnTuTu Benchmark over 6000! (Also a reserved post for later)
For some reason drocap shows in red.
5849
Sent from my SAMSUNG-SGH-I727 using xda premium
gharris040604 said:
For some reason drocap shows in red.
5849
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
I was using ScreenShot by Kastor Soft, which has worked for me with everything so far.
Skyrocket Screen comparison pictures
The OpenGL test is beautiful, and it was capping at the Vsync rate a fair amount of the time. Tons smoother than the Quadrant benchmark even though there was a huge amount more detail in the graphics. That convinces me even more that Quadrant is out of date. Unfortunately you can't get your actual results on that test without logging in to a website that didn't have a registration button, so I just skipped it for now.
So lets look at the screen display sizes and pixels. I don't have an OGS2 any more since I traded it for the Skyrocket, so for comparison I took pictures of my Captivate. (Ironically I took the captivate pictures with my Skyrocket since it was better than my old camera). The last picture was taken with my SLR camera.
One thing I saw right away was a difference if you use a downloaded font on the Skyrocket. They were crisper when seen from normal viewing distance it seemed like. Personally I'm quite happy with the screen anyway, but it did make a difference.
To my eye anyway, you can see some difference ... but only if you are so close up it's impractical. (For those of us with binocular vision anyway who read more than an inch away from the screen ... just sayin.)
Admittedly though there is some difference in vibrancy that I really can't reproduce by taking a picture with my limited equipment. I really only notice it when I switch from one phone to the other, or see them side by side.
First the Captivate. It's definitely crisp, and even the close up shot shows the very smooth letters.:
Similar picture of the Skyrocket:
Close view of Skyrocket:
Standard viewing distance:
Quadrant benchmarks
I have been very torn whether to take back my OGSGSII until I spent an
hour with the Skyrocket at the At&t store. It felt a bit laggy, the camera was
slower and the screen was definitely not as sharp. Text was fuzzy, the screen
did not seam as bright on the same settings and on lighter colored screens,
you could see the pixels. I am staying with my OGSGSII.
shootthis said:
I have been very torn whether to take back my OGSGSII until I spent an
hour with the Skyrocket at the At&t store. It felt a bit laggy, the camera was
slower and the screen was definitely not as sharp. Text was fuzzy, the screen
did not seam as bright on the same settings and on lighter colored screens,
you could see the pixels. I am staying with my OGSGSII.
Click to expand...
Click to collapse
If we don't get dev support in the next week or so this thing will go back. It's for sure laggy I agree but I love the screen on it.
Sent from my SAMSUNG-SGH-I727 using XDA App
then you probably will be taking it back. Without the source code there will be no dev support.
shootthis said:
I have been very torn whether to take back my OGSGSII until I spent an
hour with the Skyrocket at the At&t store. It felt a bit laggy, the camera was
slower and the screen was definitely not as sharp. Text was fuzzy, the screen
did not seam as bright on the same settings and on lighter colored screens,
you could see the pixels. I am staying with my OGSGSII.
Click to expand...
Click to collapse
People have been saying factory resets helped with the screen hitches. I know mine improved after removing the bloatware. For me full brightness is just too bright (on both devices) so I was usually using an Auto or 50% setting. Whether or not you like the screen is entirely subjective, and if you like the OSGS2, by all means, keep that one. (although at normal distance I'm certainly not seeing more pixellation).
I for one don't miss the Vlingo button lag!
The Quadrant scores (for me) have just been way too inconsistent for me to think it's reliable (1600 - 3500+). Here's screenshots of runs not long after you posted. (Scores at 3416, 3554, and 3710). Since it benches better than the OSGS2 scores you posted you wouldn't expect it to feel laggy. Actually this is the first time I've ran it since removing bloatware and it's faster than ever. Stock kernel and frequencies.
If we don't get dev support in the next week or so this thing will go back. It's for sure laggy I agree but I love the screen on it.
Click to expand...
Click to collapse
I'm not sure that's a realistic timeframe. Up to you, but I'd say factory reset and start removing bloatware obviously. Yeah, it's more work than flashing a ROM and have it all done for you, but to me it's part of the fun. At least I'm learning something instead of just knowing how to fire up Odin correctly.
We have CWM and root, so it's not like we can't properly use our phones for now. Even the OSGS2 took more than a week to get stable kernel's out the door and it had all the benefits of the international ROM's. But yeah, the OSGS2 will have more dev support no doubt. It's just a question of what's more important to you.
tejones36 said:
People have been saying factory resets helped with the screen hitches. I know mine improved after removing the bloatware. For me full brightness is just too bright (on both devices) so I was usually using an Auto or 50% setting. Whether or not you like the screen is entirely subjective, and if you like the OSGS2, by all means, keep that one. (although at normal distance I'm certainly not seeing more pixellation).
I for one don't miss the Vlingo button lag!
The Quadrant scores (for me) have just been way too inconsistent for me to think it's reliable (1600 - 3500+). Here's screenshots of runs not long after you posted. (Scores at 3416, 3554, and 3710). Since it benches better than the OSGS2 scores you posted you wouldn't expect it to feel laggy. Actually this is the first time I've ran it since removing bloatware and it's faster than ever. Stock kernel and frequencies.
I'm not sure that's a realistic timeframe. Up to you, but I'd say factory reset and start removing bloatware obviously. Yeah, it's more work than flashing a ROM and have it all done for you, but to me it's part of the fun. At least I'm learning something instead of just knowing how to fire up Odin correctly.
We have CWM and root, so it's not like we can't properly use our phones for now. Even the OSGS2 took more than a week to get stable kernel's out the door and it had all the benefits of the international ROM's. But yeah, the OSGS2 will have more dev support no doubt. It's just a question of what's more important to you.
Click to expand...
Click to collapse
I know all about how well this does on benchmarks, I have a post with about every app that benchmarks and the results. I have gotten rid of what I think is bloat and its helped for sure but it's still not as smooth as the original but I knew that before I bought it, I just don't know if I can deal with that lag long term... I'll figure it out in the next 20+ days. Fantastic device for sure and still head over heels better than the 4s I had for two weeks.
Sent from my SAMSUNG-SGH-I727 using XDA App
Skyler2Dope said:
I know all about how well this does on benchmarks, I have a post with about every app that benchmarks and the results. I have gotten rid of what I think is bloat and its helped for sure but it's still not as smooth as the original but I knew that before I bought it, I just don't know if I can deal with that lag long term... I'll figure it out in the next 20+ days. Fantastic device for sure and still head over heels better than the 4s I had for two weeks.
Click to expand...
Click to collapse
My benchmark's were in reply to shootthis' post, not yours ..
I recall your posts. We get the same results, but for whatever reason you are getting some kind of lag and I don't. Are you referring to that screen hitch when scrolling between screens?
Regardless, at some point the lag went away for my device. It's completely smooth, not that the slight hitch ever bothered me before. That's one reason why I can't remember when it completely went away.
I referred to your post for part of what I froze with TiBu, but there were differences. About the only other thing I can think of is I'm using setCPU profiles, and my default is the ondemand scheduler. I'm wondering if auto-brightness impacted one of my benchmarks, but probably not.
No clue. Hopefully someone will figure it out soon so we can put this thing to rest.
11/9 Update
Updated first post with Passmark benchmarks.
Horrible network speeds today - yes, I know speedtest.net isn't definitive. The main reason I ran it was that just the listing of forum posts (here) took forever to load while I was at lunch today. This was actually a faster benchmark than the server located in the city I live in ... So the poor data speed shown here was in line with what I was seeing qualitatively.
The funny thing is all of the quadrant score screenshots I posted were from the Skyrocket and not the OGSGSII.
shootthis said:
The funny thing is all of the quadrant score screenshots I posted were from the Skyrocket and not the OGSGSII.
Click to expand...
Click to collapse
Funny how? It shows that Quadrant isn't a worthwhile test. I knew that already. My scores are within a few percent of each other with Passmark, not all over the place like with Quadrant. Sort of proves the point.
First attempt with CFbench
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Danielk425 said:
First attempt with CFbench
Click to expand...
Click to collapse
Nice, hadn't run across that benchmark yet. I'll pick it up!
Its a good one chain fire makes quality apps I use the pro just to support his work
Sent from my SAMSUNG-SGH-I727 using Tapatalk
Here's mine as well...
In terms of battery..., yesterday i unplugged my phone in the morning ~9am, got to work at 10am, at work I stream high quality spotify over 4G to my BT headphones practically non stop + a 1hr tele conference over my phone
low battery warning came on at ~4:30 with the phone usage actually being the biggest drain at around 55%, screen and spotify were both less than 15%
overall I'm pretty happy with that, phone almost lasts as long as my headset will while streaming unplugged
ktiedt said:
In terms of battery..., yesterday i unplugged my phone in the morning ~9am, got to work at 10am, at work I stream high quality spotify over 4G to my BT headphones practically non stop + a 1hr tele conference over my phone
low battery warning came on at ~4:30 with the phone usage actually being the biggest drain at around 55%, screen and spotify were both less than 15%
overall I'm pretty happy with that, phone almost lasts as long as my headset will while streaming unplugged
Click to expand...
Click to collapse
After monitoring all the things using battery for a couple days, I removed the "bloat". I am a very heavy data and texting user, with maybe 20 minutes of calling. Today was the first day of being bloat free and I am at 15hrs since being unplugged and I still have 68%. I'm shocked and very happy. Lets see tomorrow if it was just a fluke..
Related
So after reading nearly 5 hours and spending my time in the wee hours of morning, I finally did all the "stable" mods for the phone... If you haven't been reading, make sure you guys check out the stuff in the development forum.
After all modifications, I was able to get 2701 points in quadrant benchmark. What mods did I do?
-i9000 eclair flash (JM5)
http://forum.xda-developers.com/showthread.php?t=734871
-Alternative mimocans lag fix
(one click installer http://forum.xda-developers.com/showthread.php?t=749495)
-One click root (googled it for i9000)
-Overclock kernel 1.0Ghz to 1.2Ghz
(http://forum.xda-developers.com/showthread.php?t=746343)
This stuff really does help out your phone folks. Bench it now with quadrant, then take a peak at the other stuff and make magic happen. If anyone needs any additional help setting up their captivate, I'm more than happy to help.
I agree those fixes help speed a lot. But the quadrant score is meaningless. the speed hack creates an io loopback. The loopback just tells quadrant what it wants to hear.
Does your BT work on the european ROM. For me all people hear is a gargeled mess on there end?
Sent from my SAMSUNG-SGH-I897 using Tapatalk
Can you post the results of these tests:
Neocore
Linpack
CPU Benchmark
I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?
jhego said:
I keep hearing about this quadrant, does it actually improve real world performance? Or is just for the sake of scores?
Click to expand...
Click to collapse
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.
modest_mandroid said:
Quadrant is just benchmarking software that takes the cpu, gpu and memory read/write speeds into account. It runs a series of tests and spits a score number out at the end, so you can compare your device to others (like comparing boner sizes, but less gay).
It doesn't actually do anything to speed up the device though.
Click to expand...
Click to collapse
This is correct and to be honest there is way to much weight in the I/O tests. That is the only reason that the stock Droid X bests the Gal X. It has more weight than cpu and gpu so you can't put to much into those scores. They really don't mean anything more than bragging rights. What I am interested in is real world usage.
Real world use with the hack provides amazing speed gains opening and switching apps. Io heavy apps are very much improved while open too. It's finally as fast as the iphone.
Whats your battery life like after the overclock?
The score ended up getting lower and lower every time i used quadrant. 2701 is the highest I was able to get so far, but that's with a fresh install of the rom and all the stuff before I started loading on apps. Everytime I ran the benchmark, I of course killed the apps beforehand.
The battery life is the same- to be honest. This is me comparing a rooted stock ROM to the somewhat fresh install of the eclair i9000. The phone is very snappy. I came from an iPhone 4 and one of the biggest eye sores to me was the less-fluidness of changing programs, response to buttons (homescreen-back button) and pinch to zoom. After all these changes, it's a whole different story. Browsing is very appealing, especially since pinch to zoom isn't jagged or slow. The smoothness of this functionality is on par to an iPhone. And there is no waiting when I press the home button or back button.
True, maybe these numbers aren't considerably accurate (as far as the lag fix and EXT2) but at least it shows raw computing capability in it's current state... meaning, the usage of a virtual EXT2. Never the less, the phone is still all around faster, even if it isn't exactly the proper way of going about it.
The only problem I've seen so far is that it likes to randomly shut off. Won't respond to anything unless if I soft reset it. I haven't really found what causes it, since the consistency of it happening goes about in a non set pattern.
I didn't see any real world increase .. so I reverted back in about 4 hours.... I'd rather have the memory than a number that don't transfer to real world speeds...
Test # 1 Video Streaming Over WiFi
ROMS Tested So Far:
Continuum
Serendipity
Precision
Firefly
Cognition
Phoenix
Paragon
Twingerbread
Supernova
Darky's
di11igaf
Dragon
Andromeda
**DISCLAIMER**
Keep in mind that results will vary for each phone and just because I get a certain battery life using the rom's and kernel's listed below does not necessarily mean that you will.
Tired of constantly flashing to find great battery life only to realize the rom didn't meet your expectations; then this thread is for you. Over the next few weeks I will test every rom imaginable and post real world results that will include battery stats, linpack and quadrant results.
**This is not meant to put down any particular ROM. Without our great dev community my captivate would have been returned and thank you all for your hard work.**
[Goal]
To provide the captivate community with real world results from top roms in everyday usage where battery life is the key focal point, but performance is not affected. Hopefully this will help save you time from having to flash multiple ROMS.
[Roms]
*This list will continue to grow*
Stock 2.2 kept fcing so will test it on test 2 this evening 3/28
[Usage]
Each night I will run the exact same VERY LONG documentary using VLC stream and convert and current widget.
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz (as suggested by a smart person listed below)
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run (0mV to make ryude get a chubby)
° Auto Sync off
° GPS off
° Zeam launcher
° VLC Steam & Convert used w/ same long documentary used each time
° Phone is placed in exact same spot every test and is unplugged as soon as I hit play
Results So Far
{
"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"
}
Test # 2 Web Browsing
Test # 2 Web Browsing on 3g
Roms Tested So Far:
Continuum
Serendipity
Precision
Stock 2.2
Firefly
Phoenix
Paragon
Currently Running:
Twingerbread
Upcoming:
Supernova
Darky's
di11igaf
Dragon
Andromeda
Juiced
Cognition
Goal:
In previous tests I tested on wifi using a vlc stream & convert. With this way of testing I'm hoping to get more realistic real-world results that you can use as a guideline to a roms overall battery performance . Keep in mind your results may vary.
Testing:
Every night I will set tab reload to 15 seconds and it will continuously reload XDA website until the phone dies. It will be placed in the same spot in my house every night and will be ran on phone data, thank god for the unlimited plan.
Applications I will be using:
- Dolphin Browser HD
- Reload tab plug-in
- Current widget
- My Settings
[Specs]
*Every rom will run "out of the box" meaning Kernel, Modem, Settings all default to how it was cooked*
° Default clockspeed 1000mhz
° 40% Brightness/Screen Timeout Turned Off
° 100% Charge each run
° Auto Sync and GPS On (To help give near real world results)
° 3g
° Zeam launcher
° Phone is placed in exact same spot every test and is unplugged as soon as I start Reload Tab Plug-in.
**Will be running all tests on 3g as some ROMs do not have HSPDA**
Results
Reserved for future use
Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...
TheSopranos16 said:
Cool. Any chance you can add stock Froyo to the list as a reference point? It would be interesting to see how much custom rom's are improving over stock...
Click to expand...
Click to collapse
Great suggestion only thing is I won't be able to undervolt so numbers will not be accurate to this testing, but I might run the best two roms after I'm done testing at there defaults against stock froyo.
Since many users are set at the standard 1000, would you consider the testing at standard 1000 speed for a more accurate battery life any user can expect. Just a suggestion
Sounds like Precision should be included, with the black theme it easily gets great battery life.
diablo009 said:
Is this under-clocked? I am on the same ROM with speed at 1000 with no under-volting.
I get 1600+ scores on quadrant, and 14+ scores on linpack (tested out even now).
Click to expand...
Click to collapse
Yes I listed in the specs what they will all be running at. All are uc/uv to 600mhz.
I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.
Enhanced said:
I have been waiting for something like this but I assume that the devs would all be up in arms if someone rated their ROMs higher/lower.
If this thread will be allowed to continue, totally looking forward to the results.
And you should totally throw Precision into the mix as it seems like the de facto battery saving ROM as it skimps on a few services.
Click to expand...
Click to collapse
Personally, if I was a dev and saw that my rom wasn't too good, I would try to make something better. So who knows how it turns out. A little competition wont hurt anyone, and hopefully have better roms! Btw, good idea with this
Sent from my SGH-I897 using XDA App
Just finished di11i on to paragon. The theme on di11i is very nice too almost a carbon fiber look.
add Torch 1.5
Also try Torch 1.5. So far been outstanding in battery department.
I know this doesn't help as far as battery life, but just for a reference as far as stock 2.2:
1. Linpack - around the 14 mflops (sometime in the 13 range, sometimes in the 14)
2. Quadrant - 1050 or so
3. Nenamark1 - 51 fps (not sure if anyone uses that one much, but thought I would throw it in as I had it available lol)
I would estimate the battery life if I didn't use the phone at all (just left it sitting in standby) would be at 60hours plus, as I get up to around 40 with light usage on 2.2 with battery to spare (haven't run it dead yet to be honest on 2.2) Still a little early though as the phone hasn't been drained and recharged full thus far.
I just checked my phone, and I have had it on for over eight hours, and I am at 92% battery left. I have hardly used the phone today (just a few texts is all), but going on that I should get around 80 hours on a single charge if I just leave it sitting there.
Great idea. I'm a huge continuum fan
Sent from my GT-I9000 using XDA App
good info to know...thanks alot!
This sounds like quite an undertaking. Good luck with the project. I'm looking forward to the comparisons. Thank you for your hard work to benefit Captivate owners out there.
Sent from my SGH-I897 using XDA Premium App
Charge drain charge drain lol gonna get online now and buy a new battery just incase i destroy this one.
LOcation matters
I am using JuicePlotter to monitor my battery usage closely. From what I see, different locations give dramatically different battery life. At home my battery drops 1% per hour. At work 20 miles away it drops 2% on captivate modems but 4-5% on i9000 modems. So the signal strength, cell tower type make big difference.
I have tried multiple Cog ROMs and Paragons ROMs, currently on Twingerbread 3.2. The best ROM in terms of battery life is cog 3.2 for me.
Yea but most people throughout the day are on the move and all I'm trying to achieve are results based on that. The constant will be the kernel in this test that way any thing I log can be directly attributed to the rom/modem. This by no means is the end all, but it will give the community a great idea of where each rom sits.
Interesting kernel choice. I've heard Suckerpunch lauded, but that ignores the fact that most of these roms flash with a different kernel by default. Is it a better test to run them all with the same kernel, or with the one they chose?
I dunno. Might be interesting to test and formally see how much kernel choice affects things.
Hey guys,
Ive been using SetCPU since it was fixed for the sensation. I am curious about what others have observed as far as battery life and performance goes.
I am running 1.8Ghz with a cpu voltage of 1.265V (1265000uV).
My battery doesnt last all that long despite all the profiles I have in place. I guess thats expected when you overclock by that much, huh? Is it worth it though?
Im sure more of you out there have experience to share. Im not talking Quadrant and benchmark scores, Im talking REAL use!
I am beginning to feel that dropping the frequency down may be in order since I cannot find anything that needs 1.8Ghz to work on this phone. Plus, less frequency means less required voltage. That would mean more battery!
Anyone care to chime in with their overclock frequency + voltage and experience?
Matt
I'm also interested in getting some input from other users, without having to clog up the respective overclocking threads in the Development section.
Yesterday after work, I set up the 1.5Ghz Undervolted option using utking's tool (http://forum.xda-developers.com/showthread.php?t=1168707). I didn't see too much need to push my CPU too hard, and a stable UV always piques my interest.
I created a couple of basic SetCPU profiles (screen off, battery below 20%, temperature < 50C), and scaling on demand up to 1512Mhz, my phone took about another 7-8 hours of moderately heavy use (Navigation, Maps, Yelp, photos, etc.) before it was on its last legs.
Bear in mind that I've been using the Anker 1900mAh battery. But even after the OC-UV that I set up, this was at least as good of battery usage as before without any SetCPU or overclocking, and actually seemed to be a little bit better to be honest.
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
I went down from 1.62 UV to 1.5 UV,because I could not see any difference in general use nad in benchmarks(except Quadrant) and battery consumption is much bigger with 1.62 with exact same profiles on setCpu.I think that this is best compromise between speed and battery life and as far as I know this is native clock speed of 8260 Snapdragon.
mrg02d said:
I just dropped down to 1.6Ghz @ 1.26V...
I couldn't keep my phone from freezing with anything less than 1.26V @ 1.6Ghz. We will see how this goes for a few days and compare to my previous 1.8Ghz @ 1.265V.
So far, speed seems to be FASTER than 1.8Ghz. My Quadrant score (only being used here for comparison reasons) was 2700 right off the bat, whereas 1.8Ghz would peak around 2700-2800 after several tries.
The carousel works much better! I can swipe through quickly and have it scroll with zero lag. I can also fast swipe and watch is spin nicely!
Google Earth and Maps is about the same as 1.8Ghz.
Before, at 1.8Ghz, I could probably get 16 hours out of my phone with VERY LIGHT use. (A few 2min phone calls, check mail throughout the day, check the web a little). I am charging the phone up and will report back later.
Matt
Click to expand...
Click to collapse
How simple is it to temp-root and overclock? I am really only interested in overclocking to speed up Sense, and you said it performs better with a speed boost.
Sent from my HTC Sensation 4G using XDA Premium App
Very,very easy,just read this tread :http://forum.xda-developers.com/showthread.php?t=1168707
I have mine undervolted at VDD_1175000 and 1500MHz. I like it very much...makes a big difference in quadarant score, but not sure in reality how much faster. Battery life is fine (when the phone is on). Have not experiened FC's
I have modified eugenes batch file to push my kernel file and preferred speed after perma-temp-root and now is all in one click...
So here is a little update:
Its been about 8 hours since full charge and I am at 55% battery left.
1.6Ghz @ 1.26V, On Demand.
Ive been checking email, making a few calls, and surfing the net with both wifi and GPRS (was out of the network, away from 4G). I also played Angry birds for a little bit and showed off Google Maps and Earth to my Mom.
Now that Im back home, ive turned back on 4G...
Ive noticed a slight amount of hesitation while opening and closing things, but nothing bad.
I havent had any profiles kick in yet, but they will soon with the battery getting low. I will resist charging the phone and see if I make it through the night, using it as I need it. I will report tomorrow.
Matt
I must be doing something wrong.
I am rooted and running LeeDriods 1.2 Rom. When I launch setcpu the only options i have are 1000 mghz? WTF am i doing wrong?
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
BigBoppa said:
i think at LeeDroid 1.2 you must not use setcpu but Demon control?
Click to expand...
Click to collapse
Hmmm, okay. I saw where set cpu was updated for the sensation in the latest release but it doesn't seem to support overclocking with this rom.
Shame that as i was about to get that rom and flash it onto my phone, glad i came in here now
Running Leedroid 1.0
Kernel @ 1.7ghz max, i have it set to 1.5ghz and 192mhz
Runs hot when i play finger racing or reckless racing or modern combat 2 or something intensive, but besides the heat, it drains just like it normally would to be honest, maybe a little quicker, definite speed increase in overall user experience, without an OC the rom just flops, better than stock but just crap, OC is needed.
Hey guys, I'm new to this forum but not Android Central. Anyways, I just recently switched to jelly beans build 14 w/lean kernel. For some reason my battery life is just terrible. I'm just barely making it through an 8 hour workday, and that's not even using it that much. I was wondering if you guys had any tips for good battery life on this ROM/Kernel combo. I do have set cpu installed and running but I'm only Overclocked to 1.6 and undervolting by 50 mv. I also have a save battery life profile that drops it down to 1026 when the screen is off, it's charging, or battery is below 40%. Can you guys give me advice on settings to use to save battery life? I really like this ROM and kernel but I'm getting such terrible battery life. I think it's probably more user error than anything but maybe you guys could provide some tips.
Thanks in advance.
Nick
sent from my Galaxy S3 on beans 14 via tapatalk 2
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
http://rootzwiki.com/topic/31329-ke...nimalistic-kernel/page__st__1410#entry1042976
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
SlimSnoopOS said:
How recently did you switch to Beans and LK combo? I wouldn't base battery life off of the first day after a flash. I use the same combo, however I use the LK exp version. I would suggest changing your voltages to match begin at a lower mv. I have mine starting at 900 mv according to Imoseyon voltage chart.
That said, I have my screen off max cpu speed at 486 so you could probably go lower. How's your signal at work as well?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
nicholi2789 said:
Hey thanks alot for the response!! It's the third day of this ROM/Kernel combo. So I can really go as low as 486 when the screen is off? I figured it probably wouldn't be very stable if I dropped it that low. I've looked at the Rootzwiki thread you posted and have set all my voltage settings as follows for the last two days:
1900mhz-1250mv
1809mhz-1200mv
1720mhz-1200mv
1620mhz-1150mv
1512mhz-1100mv
1458mhz-100mv
1350mhz-1125mv
1242mhz-1125mv
1134mhz-1125mv
1026mhz-1125mv
and its 1125 mv the rest of the way down.
So basically I'm undervolted by about 50mv at the highest clock speeds, then gradually come down to about 25mv at the lower speeds.
I'm really scared to go much more than that for fear of causing instability. I would love to be able to undervolt by more if I knew for sure it wasn't going to make it unstable. What are your voltages at the highest clock speeds and the lowest? Can I undervolt it by more when I get down below 1026 mhz? I figured they were all set to 1150mv stock for a reason. Got any advice on that? I want to squeeze as much battery as possible..
Oh and my signal is perfect! I think it's even better than it was before. This Rom didn't come with a different radio too did it?
Thanks for the reply!!
Click to expand...
Click to collapse
I actually have my voltages set to exactly what Imoseyon has listed for the nominal cpu. As far as my screen off, I honestly just picked a low number and since I don't see lag I keep it there haha in addition, I use interactive governor which scales up the cpu once the screen comes on so it balances out either way.
To check which cpu type you have, do this. Details on what the cpu differences are included in the link as well. Matching your cpu type and adjusting your voltages may help extend your battery life but some say it is marginal.
No, your radio actually stays the same unless you manually flash a different one. I should also ask, what else do you have enabled? For example, in Maps/Settings, do you have everything disabled except "Enable Location History"?
{
"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"
}
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
nicholi2789 said:
Yeah i already did that to sort out what Cpu I have as well.
And I have limit background processes enabled in developer options, limit processes 4 at most. Also where exactly are the maps settings? I have GPS off and Google maps frozen by Titanium backup (except when I use it occasionally). I also have every other unnecessary app frozen. Like the Samsung keyboard (use swiftkey) the stock email app, etc.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Click to expand...
Click to collapse
Well it's under Location Settings but if you have Maps frozen until needed then it's an unnecessary step. You have done even more than I do or suggest haha I haven't frozen anything.
What would you say you're seeing as your average screen on time?
Sent from my SCH-I535 using xda app-developers app
Oh average screen on time is probably around 2.5 to 3 hours or so. Nothing crazy. I just wanna get my battery life back to before, where basically I could leave home fully charged and work a 10-12 hour day and come home with around 30% or so battery life. That's good enough for me.
So about these recommended voltages. I have the "fast" processor, should I just st the voltages for what he recommends? Are those recommended for bet battery life or best performance? I want to undervolt as much as possible without creating an unstable system or causing damage.
And can you help me understand the governor settings, my understanding is that "ondemand" activate both cores when needed, and interactivex is all the time? Is that roughly correct?
sent from my Galaxy S3 on beans 14 via tapatalk 2
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
nicholi2789 said:
Okay nevermind about the governers. I read quite a bit more about them over the last hour and feel that I understand them at least a little bit better. hehe. So much to learn!! It seems InteractiveX is the obvious choice for performance AND battery. I'm still kinda unsure about how much undervolting I can really get away with though. I love how smooth everything runs when I'm overclocked, but i'm not sure it's worth it in terms of battery life (unless I'm playing a game, or flying my AR Drone). It seems there is still an advantage to be had by setting it to the normal clock speed (1512mhz) and then undervolting by just a bit. Might be able to squeeze just a tad more battery life out. It's still nice to have these things within my realm of control though. I understand why people find this so addicting now!
Click to expand...
Click to collapse
Yea flashing kernels and roms is very addicting. Since you have a fast cpu, you can actually UV much lower than I can with my nominal cpu. You can set your voltages to match Imoseyon's table and you'll be fine or maybe try lower. I know from experience that I can't UV lower than 900 mv without my phone immediately locking up lol You can even hold off on setting voltages at boot if you want to get a feel for performance while UV'ed.
I can't really speak on OC vs. regular clock battery life, I keep mine OC'ed at 1.62 ghz so I'd notice minor drops in battery life compared to say 1.8 ghz. I don't even have much need for that since its fast enough to me as is. I haven't noticed too much of a hit on battery, I still range between 2.5-4 hours screen on pending if I'm on LTE or wifi during that charge.
Also, if you want to try your hand at really digging into kernel settings then you should also check out the the Team Kernelizer's thread for KT747 kernel. Personally, I use LeanKernel cuz it works really good for me so I applied some settings from there but not everything was applicable. This thread has some really knowledgeable people in it. Definitely give KT747 a look, or any other kernel for that matter, and see which ones you like the best.
Yeah i think i may have had a bad battery. I checked and I know my phone is deep sleeping, but since adjusting my voltages and settings last night it'd definetely improving. I have my voltages set to 25mv under what is recommended on that chart down to 1.4 the in the lower clock settings o have it exactly at the recommended settings. Seems to work okay. I have set on boot enabled but i also have the stock voltage settings on my SD Just in case of a boot loop.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Does anyone have any suggestions? I really like this ROM and would prefer to keep it if possible but this battery life is terrible. Ant ideas on some measures I could take to try and improve it a bit?
I wiped cache partitions, davlik cache, and did factory reset before installing. I even do them twice just to be sure.
Would maybe wiping and re flashing the Rom help? I'm totally stumped here.
sent from my Galaxy S3 on beans 14 via tapatalk 2
I don't understand. I used cpu spy and i know phone is deep sleeping. I have set CPU to drop the clock speed when screens off.
Why the heck is it using so much battery? I'm dropping about 6-7% battery at idle. Somebody shed some insight.
sent from my Galaxy S3 on beans 14 via tapatalk 2
Well, Saving your phone's battery without compromising your phone's performance will be a little difficult for everyone. Everyone nowadays prefer phones which can last them for atleast a day. But what if we could extend our phone's battery life to 1.5 days or 2 days without compromising the power of your phone?
Yup. That's possible. I've been experimenting with my Note III SM-N900 [Indian Exynos Model]. I did it for almost like 6 months. My aim was to maximize my phone's battery life. And finally I found it. I wanna share all my results and the secret tips to save that last precious drop of your battery juice!
[NOTE: [Please keep in mind that I own a Exynos Model, i.e, SM-N900 and made all the customization on this model only. Many methods explained herein might not work for you.]]
:victory:
So, first a few words on my phone's history:
When I first got my brave and good looking Note 3, I was on 7th heaven. I got Android 4.3 Jellybean onboard. I used to get 2 days of unparalleled battery life. Smooth UI. But, very few customization. Previously I used to own a Galaxy SII i9100G. It had a great potential and till date is considered as the most selling Galaxy Variant. But, still I was happy. Then came the wave of KitKat 4.4.2. Guys, you won't believe, I spent weeks in the dilemma of the fact - Should I root or not root. Should I first update and then root? Should I root and then update? I was going crazy.
But then I decided. No, I should first update via OTA and then root my phone. And then, I did it. But soon I realised that I did a wrong thing. I experienced very, very poor battery life. With 3G on and screen time of 3-4 hrs, my phone used to die. But then I thoguht, there's still hope. Thus, I spend a lot of days into finding the best customisation for improving the battery life. And after 6 months, now I finally got the best battery life.
Guys, another thing I would like to say here is that, there was a very good article on saving battery life before, made by stanley08. [READ IT HERE].
STEPS TO MAXIMIZE YOUR BATTERY LIFE
1. Kernel Customisations:
Well, as you all know, kernel is the thing that sits between your software and hardware. Doing optimal changes to it is the best way out there to save battery. First of all currently there are two best kernels out there. halaszk and pekaka. Both are absolutely amazing kernels and I found halaszk to offer a greater number of modifications. But for everyday use I use pekaka now. On the top, it doesn't matter that much. So, let's get started.
First of all, halaszk kernel comes with a very powerful tool called synapse. It allows you to individually set the frequencies, voltages, GPU speed etc.
If you wanna use pekaka, then use an app such as Trickster MOD app from PlayStore.
The main part comes now:
1. Reduce all A15 cores to -25 mv each.
2. Reduce all A7 cores to -13.5 mv each.
3. Use 0 as the parameter for Multicore Power Saving
4. Use Interactive or Ondemand governor.
5. Use CPU frequencies upto 1.3 or 1.4 GhZ.
6. Use GPU frequencies upto 340 or equivalent
That's the kernel part.
2. ROM:
Using custom rom might not be that important because almost all roms available now are either stock or MIUI. So, it won't make a difference. Still some roms might be slightly better.
One rom that I found was Alba's Ultralite roms. These roms have been developed by a russian developer. The thing that's really good in these roms is that, the Ultralite series weigh around 600-700 MB and are totally debloated. So, lesser the bloatware, lesser is the memory consumed and hence, lesser is the battery consumed.
Another rom to observe is Dr. Ketan's Rom series. Many users are satisfied with the balance of battery life and lots of customisations.
Some other good roms are Alliance ROM, and Murat ROMS. There might be many more roms with good battery life. Users may leave their comment below and I'll add them.
3. Memory:
Yup, more memory means more battery. Many would disagree with me but, I tried it out and saw amazing results. I would suggest you to use Clean Master to clear cache, memory and check out your phone's temperature.
4. USPM MOD:
Xperiacle, an amazing developer[And my fav!] has developed a module called UPSM mod. Ultra Power Saving Mode, was found in Galaxy S5. He did an amazing job and has developed this module, which allows you to activate UPSM or Emergency Mode. Doing this, will limit you to basic apps such as Phone, Whatssap, etc and will prove immensely helpful for saving battery. This is highly recommended for an y battery savvy. There's also another Xposed module which reduces NLP Kernel wakelocks, thus making your phone sleep better. Download it here.
5. Reception/Signal:
Believe it or not, this is the part that takes away a huge toll on your battery. If you have bad reception, you ought to have a bad battery life. I saw the results myself. On full signal, my phone's battery dropped to around 98% after 6 hrs standby whereas on 1 bar signal, I found my battery to be 82% after 6 hrs standby. this is because, your phone tries to continuously searches for better battery.
6. 3G/ WIFI:
Personally I found 3G to consume much more battery than WiFi. So, it is advisable to keep it turned off while not in use. If you get a simultaneous screen on time and total 3G usage time of 5-6 hrs, you're great! That's the best you can get.
7. Temperature:
Your phone's temperature makes a lot of difference. Many times you might have experienced your phone's temperature shooting up like a volcano! Well it happens when your CPU or GPU is put under a lot of stress. For example while playing a high quality game. Many times it happens when some background app freezes. So, try keeping your phone a bit cool! I mean, always check if any background apps are running continuously.
8. Greenify:
Hey, I am not talking about afforestation or something! I am talking about a wonderful app called Greenify. Now, what it does is, it freezes the background processes and apps [which you select], and thus frees up a lot of memory.
9. Debloat:
Yup, lot's of apps on your phone may slow it down and deteriorate your phone's battery. Try removing apps that you don't use anymore.
Also, another thing I would like to suggest you all, is to keep reflashing your rom every 2 to 3 months. This would ensure less momory clutter and defragmentation. Also, it would keep your phone running smooth. Also, as you might already know, AMOLED displays consume much battery for bright colors and brightness level of the screen. So, it's advisable to use dark wallpapers.
So, guys these were some of the customisations I used to achieve the perfect balance of battery life and performance. If you have any more idea or trick to save battery, do post it below. We'll keep this thread updated.
Thanks! And do share this thread with others.
:fingers-crossed: :fingers-crossed:
UPDATE:13/10/2014
Here are some amazing benchmarks of my friend/contributer @Spitwista
He has also come up with a great way to save battery.
Things to look at
1. 30 Minutes gaming(Real drifting)
2. 30 minutes music (power amp)
3. 7Hrs SOT
4. More than 24Hrs full run time
5. True deep sleep
6. Smooth and 100% stable all around
7. Using Halaszk kernel v20.b2
For now, check out these screenshots:
{
"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"
}
Guys, I am currently testing on XXUENI1 the latest firmware. Will soon give the battery statistics.
Sent from my amazing Exynos Note 3.
Till now, getting really amazing battery on XXUENI1
Sent from my amazing Exynos Note 3.
thetitanium said:
Till now, getting really amazing battery on XXUENI1
Sent from my amazing Exynos Note 3.
Click to expand...
Click to collapse
Screenshots or it didn't happen ?
r-l said:
Screenshots or it didn't happen ?
Click to expand...
Click to collapse
Will give it soon.
EDIT:
Here are the screen shots. Love this firmware.
Note that I started monitoring from 85% and used mobile data all the time when WiFi wasn't on.
Will soon post a fresh screenshot.
Sent from my amazing Exynos Note 3.
Im using MultiX ROM 2.0 with stock kernel. Amazing battery life, about 2 hours screen on time with 69% battery left. Im using greenify
Sent from my SM-N9005 using Tapatalk
tarantulapg said:
Im using MultiX ROM 2.0 with stock kernel. Amazing battery life, about 2 hours screen on time with 69% battery left. Im using greenify
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
I believe MultiX is not for SM-N900..... Very less roms for exynos......
Sent from my amazing Exynos Note 3.
thetitanium said:
7. Temperature:
Your phone's temperature makes a lot of difference. Many times you might have experienced your phone's temperature shooting up like a volcano! Well it happens when your CPU or GPU is put under a lot of stress. For example while playing a high quality game. Many times it happens when some background app freezes. So, try keeping your phone a bit cool!
Click to expand...
Click to collapse
Just a minor thing - It's not the temperature that degrades battery life, but the applications that consume more resources, thereby also more battery and generating heat.
You are too much forcing yourself to lengthen the battery life while limiting yourself from users' accessibility and ease.
Sent from my SM-N900 using XDA Premium 4 mobile app
No bro..... not at all.... even I clearly mentioned it in the OP. Read and then speak bro.
Sent from my amazing Exynos Note 3.
Someguyfromhell said:
Just a minor thing - It's not the temperature that degrades battery life, but the applications that consume more resources, thereby also more battery and generating heat.
Click to expand...
Click to collapse
Maannn..... please read the 7th point carefully. Nowhere did I mention that temperature degrades battery life. Please read things carefully and then say me what's wrong with my post.
Sent from my amazing Exynos Note 3.
Let me tell all my findings from your post. I would like to say my assumtions so all may not be true.
1. You plugged in awhile AC power or USB cable to PC in between your process and thus it stretched out the battery for awhile.
2. You put in Airplane mode at the end and may be it has been since 10% battery life.
3. You increased the screen time while letting minimal CPU and GPU usage just by reading and browsing internet with chrome for a few mins. (May be brightness is set to 0)
4. I didnt see other applications such as facebook,whatsapp and so on ( you may have uninstalled them and even google play services)
For me, i didnt tweak anything about CPU or kernel. I just use official firmware, rooted and greenify only. Whenever i browse internet, i turn on 3G and then back to 2G with background applications such as viber, facebook,wechat with casuality and ease. My battery would last for a day with screen on time around 5 hrs and sometimes more than 5 hrs.
So my conclusion is your post doesn't intend for "Competition of Battery Life on Galaxy Note 3" . It should be a balance between battery life and users' accessibilty without limitations of the activities.
I appreciate your effort for this post but I dont mean to offend. I am sorry about my comment.
satslu said:
Let me tell all my findings from your post. I would like to say my assumtions so all may not be true.
1. You plugged in awhile AC power or USB cable to PC in between your process and thus it stretched out the battery for awhile.
2. You put in Airplane mode at the end and may be it has been since 10% battery life.
3. You increased the screen time while letting minimal CPU and GPU usage just by reading and browsing internet with chrome for a few mins. (May be brightness is set to 0)
4. I didnt see other applications such as facebook,whatsapp and so on ( you may have uninstalled them and even google play services)
For me, i didnt tweak anything about CPU or kernel. I just use official firmware, rooted and greenify only. Whenever i browse internet, i turn on 3G and then back to 2G with background applications such as viber, facebook,wechat with casuality and ease. My battery would last for a day with screen on time around 5 hrs and sometimes more than 5 hrs.
So my conclusion is your post doesn't intend for "Competition of Battery Life on Galaxy Note 3" . It should be a balance between battery life and users' accessibilty without limitations of the activities.
I appreciate your effort for this post but I dont mean to offend. I am sorry about my comment.
Click to expand...
Click to collapse
Now here's my clarification:
1. As I already said, I started monitoring from 85% after charging (see the pics)
2. I did put it on airplane mode for 10mins in the end. (Any person with just 2% battery will do)
3. Ya.... 3rd conclusion is true. I did everything ideal battery test guidelines as per GSMARENA. I even played a few games which didn't show up on the battery screen. Also, Whatsapp was on the whole time and my life is unimaginable without it.
4. My screen brightness was at 50% and 3g on for 4-5 hrs. I only use 3G.
Hope that classifies all your doubt. Will very soon post new battery results since the previous one was a bit controversial.
Many members of XDA are currently testing my settings and will soon give me the results. Thank you.
Sent from my amazing Exynos Note 3.
nice guide. thnaks
BiIIyTheKid said:
nice guide. thnaks
Click to expand...
Click to collapse
Thanks bro...... Any suggestions or any more tips?
Sent from my amazing Exynos Note 3.
Undervolting will make things unstable as I have heard. All I do is debloat and greenify.
That is with Facebook, Instagram on the background.
Sent from my SM-N9005 using XDA Free mobile app
Graffiti Exploit said:
Undervolting will make things unstable as I have heard. All I do is debloat and greenify.
That is with Facebook, Instagram on the background.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
See, undervolting my just a few mvs doesn't slow your phone down. That only happens when you under clock way more. By the way your phone seems quite good.
Sent from my amazing Exynos Note 3.
Guys...... New Scripts, tips and settings are soon coming..... Keep checking.....
Sent from my amazing Exynos Note 3.