Related
Hello,
I'd have posted this to the dev section but the posting rules here require non-talkative people to fabricate 10 useless posts before they can post there.
I've noticed that "Cell Standby" is far and away my greatest battery user on my Nookie Custom 0.6.8 eMMC flashed device. Now, I'm sure this is just a mislabeled "Display" usage meter, but I wanted to make sure. I'd post a screenshot, but apparently I might be a terrorist since I haven't made ten posts yet so I'm not allowed to link images yet.
Thanks In Advance
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
I'm about as new as it gets, though, so take that with a grain of salt.
junkrobot said:
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
I'm about as new as it gets, though, so take that with a grain of salt.
Click to expand...
Click to collapse
Yep, it is debunked, ignore it if battery life is the concern. If you want different info in Spare Parts for partial wake, this changes it to Android System..
junkrobot said:
As far as I know, the cell phone battery usage problem has been debunked. I could be completely wrong, but since the Nook lacks the necessary components, there's no actual way for the power to be lost in the process.
Click to expand...
Click to collapse
I believe this, however -- how hard would it be to find an app that claimed to track what was using the battery with any accuracy. Pretty sad that the built in battery monitor gives "credit" to "cell standby" for 50%+ of battery usage on a device that does not even have a cell. Anybody could build an app that hard coded battery usage stats in pre-defined chunks
I don't know why this bugs me so much...it just does.
Hello, here are some benchmark i made to test if some features being used in kernel development are usefull, useless, bull**** or make things worse.
HOW I DID THE TESTS
DEVICE= i9023.
ENVIRONMENT= fixed 25° Celsius.
OS= ANDROID 4.4.1 JRO03E Factory Image by Google.
SOFTWARE USED= 0xBenchmark 1.1.5 - AnTuTu Benchmark 2.9 - Screen Timeout Toggle.
OTHER TOOLS= A/C Charger / Standard Chronometer.
KERNEL= Kernels are built from source using the standard herring defconfig.
Additional notes:
The system is booted up once, every tutorial is closed, 0xbenchmark, Antutu and Screen Timeout Toggle are installed, airplane mode is toggled, system is rebooted in recovery, battery stats are deleted, cache and dalvik are cleared, system is nand backupped.
Every test starts after 30 min of phone off to let him cool, restoring the nand backup and waiting 5 min after system is booted up. Phone is connected to A/C charger.
Kernel are swapped after the nand restore.
Tests are done 5 times and then the average is calculated && till results are almost the same every run.
TEST N. 1
".. i use teh latest toolchain, mah kernel is imba ima pro !!111!1one!!eleven"
Google toolchain 4.4.3 vs Google toolchain 4.6
This test is inspired by an Ezekeel work that demonstrate how every different toolchain from the google base 4.4.3 used to compile our NS kernel resulted in 0 increased performance. Same goes for "optimized" compiler flags. You can see some bench here.
What i'm going to do is to test latest google prebuilt toolchain and see if it differs from above test.
- 0xBenchmark reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
Linpack [COLOR="Red"]18,81[/COLOR] 18,31
C [COLOR="Red"]21,65[/COLOR] 21,15
FFT [COLOR="Red"]13,92[/COLOR] 13,59
JSOr [COLOR="Red"]39,79[/COLOR] 39,14
MCi [COLOR="Red"]7,20[/COLOR] 6,60
Smm [COLOR="Red"]17,80[/COLOR] 17,45
dLUmf [COLOR="Red"]29,61[/COLOR] 29,17
- AnTuTu reds results are better.
Code:
Toolchain 4.4.3 Toolchain 4.6
RAM [COLOR="Red"]260[/COLOR] 257
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 105
GFX 2D [COLOR="Red"]278[/COLOR] 277
GFX 3D [COLOR="Red"]1115[/COLOR] 1111
TL;DR
USING LATEST GOOGLE TOOLCHAIN DOES IMPROVE KERNEL PERFORMANCE? NO
TEST N.2
"..undervolting teh lcd display MUST save battery!!"
LCD @ 3.0 V vs LCD undervolted to 2.4V
Same environment as before. Since % battery are not always accurate i made 3 tests:
2.1: let phone fully discharge, charge it up for 30 min. Boot it up, put max brightness and count how much time passes till it poweroff by himself.
2.2: let phone fully charge, boot it up, put max brightness and count how much time passes till it loose 10 points %.
2.3: let phone fully charge, boot it up, put max brightness and count how much time passes till it goes from 60% to 50%.
RESULTS
After days of tests, can pretty sure say that at the cost of 20% undervolt (from 3.0 to 2.4) there isn't any noticeable battery saving. What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
Remember these tests were made on a slcd panel not amoled.
Did i say these tests were made on an i9023?
Tests made on slcd i9023.
TL;DR
THERE IS ANY NOTICEABLE BATTERY SAVING UNDERVOLTING THE LCD?NO
TEST 3
".. ye ye but removing lot of crap makes mah kernel faster!"
Stock Kernel vs Config tweaked (debug and crap removed) Kernel
Removed all possible debuggers, governors, tv tuners radio and all unused crap.
Let's see if it's really better.
- 0xBenchmark reds results are better.
Code:
Stock Kernel Cleaned Kernel
Linpack [COLOR="Red"]18,81[/COLOR] 18,72
C [COLOR="Red"]21,65[/COLOR] 21,54
FFT [COLOR="Red"]13,92[/COLOR] 13,65
JSOr 39,79 [COLOR="Red"]39,85[/COLOR]
MCi [COLOR="Red"]7,20[/COLOR] 6,77
Smm 17,80 [COLOR="Red"]17,82[/COLOR]
dLUmf [COLOR="Red"]29,61[/COLOR] 29,54
- AnTuTu reds results are better.
Code:
Stock Kernel Cleaned Kernel
RAM 260 [COLOR="Red"]261[/COLOR]
CPU Integer 416 416
CPU Float-Point [COLOR="Red"]106[/COLOR] 104
GFX 2D 278 278
GFX 3D 1115 [COLOR="Red"]1116[/COLOR]
TL;DR
REMOVING CRAP FROM KERNEL LIKE UNUSED DRIVERS, USELESS GOVERNORS, ALL DEBUGS, DO INCREASE KERNEL PERFORMANCE? NO
TEST 4
".. ye ye u fools seeking big numberz! Merging kernel with latest linux mainline makes teh battery drop fastah"
Kernel merged with linux 3.0.39 / 3.0.40 / 3.0.41
Same standard condition, let phone full drain with all 4 kernels in idle / airplane mode and standard usage.
RESULTS
After comparing 4 different kernel the battery stats were all the same, no weird wakelocks no battery drains. Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge.
{
"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"
}
awesome work!
Good work.
I respect your work.
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain? I'm not too familiar with all the technical stuff, so if anyone can explain exactly what the kernel is, that might help explain things even further. I do know, and everyone else (hopefully), more aggressive scaling can have an effect on battery life . Nice to see another test showing undervolting is pretty much not needed and isn't worth the instability it may cause. But hey, whatever floats your boat.
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
"It depends on what the meaning of the word 'is' is."
"... I didn't inhale ..."
what CPU speed(high/low) are you benchmarking, I don't see it posted.
I'll just come out and say it: seems fishy.
I've seen you obsessed before at some kernel "myths" like thalamus claim that latest mainline updates were hurting performance/battery and to be honest I don't see in these studies a sufficient amount of rigor, objectivity and data to withdraw any conclusions except your clear agenda against some things that are said.
For example, some flaws:
1. 0xBenchmark and AnTuTu only measure one kind of performance, you may think you are gauging something when you're not.
2. A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
3. Such benchmarks have fluctuations, they are not particularly accurate.
4. The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
6. And once more, removing debug/crap should improve other things which were completely ignored (mm, pm, etc).
7. The last test just doesn't make sense, there are too many things involved to be that linear.
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Long story short, I can't really bring myself to take this too seriously as it lacks data and there's just too much hate undermining the credibility of the post. I should also mention that I don't have a position regarding each of those claims; I believe we should experiment, analyse, collect feedback and withdraw conclusions for everything but this just didn't convince me, especially when it comes to your neutrality. Thanks though.
chronophase1 said:
Hasn't there been devs around here that specifically said kernels don't actually affect battery drain?
Click to expand...
Click to collapse
I guess I know whom you are talking about, but may be you have not read his latest thread. lol...
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
I am glad this test has proved it actually doesn't matter.
anshumandash said:
When this dev released his .39 kernel, I asked how does it impact the battery. He shouted back at me in a rude voice saying Kernels doesn't impact battery and it is only the ROM. Fare enough.
But today he claims around that merging in to mainline from .31 to .39, .40 etc drains more battery and he is going back to .31 and says he has data etc.
Click to expand...
Click to collapse
I said generally, which is correct. The vast majority of the time the kernel has nothing to do with battery drain.
And yes, merging mainline does make a difference.
If you actually bother to read my blog post, you will see I don't actually mention battery drain at all as my reasons for ditching mainline updates.
Personally, I don't use the Nexus S enough to notice increases / decreases in drain, it's my development phone. However, quite a lot of users *have* told me that they have noticed improvements since I rolled back. Perhaps they are all wrong too?
It's not wakelocks, it's not obvious drain, it's subtle increases in drain which are impossible to track down.
However, In the case of the GNex when I merged to .40 I got 6% an hour drain, but when I went back to .31, I got less than 1% an hour drain. Merging back up again gives me the 6% an hour drain again with *nothing* else changed. It doesn't take a genius to figure out that it must be the kernel merging which has caused it, or is someone going to argue with that too? Lol.
I'm not entirely sure what myths have been busted here. It seems like a non kernel developer wasted their time to prove utterly nothing, which amuses me slightly. Do you honesty think I apply any modification, tweak or anything without testing the impact? If it makes no difference, it doesn't go in.
Removing unused stuff is simply to make the compile slightly quicker and the resulting zImage smaller. I don't believe there are any performance improvements to gain by doing that, but what is the point having junk built in which isn't needed?
As for removing all debugging, it's not a good idea, because how are you going to get a stacktrace if you panic? Again, that is something I won't do, and I know it makes little difference.
Anyway, if you want to test more accurate real world usage, use the 2D tests on 0xBench. They are CPU bound and they are greatly affected by small changes. Here are some I did a few weeks ago to test the best toolchain for the Nexus 7.
As you can see, there clearly is a difference between the speed of code that they produce. Raw speed is one thing, but graphics benchmarks more accurately represent real usage.
tl;dr: Ignore the agenda driven opinions and dubious results in the first post, they are meaningless.
simms22 said:
what CPU speed(high/low) are you benchmarking, I don't see it posted.
Click to expand...
Click to collapse
Performance, 1000.
albundy2010 said:
I find it rather strange that you claimed to use Google factory images on the 9023, but your battery screen shots show on screen buttons.
Click to expand...
Click to collapse
knzo said:
8. Why do the screenshots have battery % and the galaxy nexus keys if you were on OTA JRO0E?
Click to expand...
Click to collapse
If you read carefully i tested the battery with daily use aswell.
Quoting myself : " Also with standard usage, with data always on and few wifi and standard usage managed to reach 36 hours on same charge..
knzo said:
A more recent toolchain supposedly provides improvements in other areas which weren't taken into account.
Click to expand...
Click to collapse
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
After tons of test around the web can pretty much assure you that toolchains may give something good compiling the OS ITSELF not the kernel.
knzo said:
The LCD undervolt test lacks data results (we are to believe your word?) and the methods chosen aren't good - too many parasite variables.
Click to expand...
Click to collapse
This is a rude attitude. Why don't you explain why the methods are wrong?
If after days of testing with almost just the lcd on, seeing wich charge lasted longer isn't good feel free to explain why.
Maybe i should've used a tester? I simply want to see if my phone last longer with lcd undervolt, simply.
About data results: the results is around 5%, would it better if i wrote how much every % lasted and then making simple math operations? No thanks.
i don't like to edit OP posts so i'll write it here. Quoting myself:
What i came up with is something like 5%, that means something like 10 more screen time with standard use, even less, and considering this small margin, can also be unrelated at all to the undervolt.
i meant 10 minutes more screen time
knzo said:
5. Again, vague information (you don't specify which debugging was removed). Not to mention some debug are proven to hurt performance like Frame Pointer. If you're going against theory, one more reason to be concise.
Click to expand...
Click to collapse
I disabled them one by one aswell and never noticed an increase performance. So your statement is wrong. I don't have the config anymore but for sure kernel, slub dm and cgroup subsys were disabled.
I develop my own rom and kernel just for myself. I make these tests for myself not to prove anything, i'm just sharing.
These tests took me one week to be made. Do you really think i would ruin them posting wrong informations or ruining my reputation?
Actually i was surprised by some of them.
You're welcomed to made them again or better since you didn't like the methods.
atl4ntis said:
If you read carefully the test is inspired by the Ezekeel one, that's why i used the same tools/approach. I do thrust his work more.
Click to expand...
Click to collapse
That single sentence sums up this entire thread.
Basically, you started these tests with an agenda which was to validate ezekeels tests and you 'proved' what you wanted to prove to fit your agenda.
Anyone can do that. It doesn't actually prove anything though, it just generates FUD. Congrats.
No just one test and just becouse similar test were made.
Go troll somewhere else.
atl4ntis said:
No just one test and just becouse similar test were made.
Go troll somewhere else.
Click to expand...
Click to collapse
I'm not trolling. I'm rightly questioning your extremely dubious results and the fact you have an agenda, which you clearly do. If you don't want people to question them, perhaps go and post them on Rootzwiki instead where they will be blindly accepted as gospel.
The definition of trolling is here.
Your post is simply confusing users and generating FUD, but perhaps *that* is your true agenda, is it not?
If you think these tests are wrong just provide some proof instead of offending people or talking about agenda or even worse reporting them as wrong because "other people said so" instead of testing them by yourself or saying some issues are not trackable.lol.
Some moderator should get rid of this thanks.
I think the OP has good intentions and had shown aptitude in collecting data, which deserves praise.
Just because something isn't perfect in the first attempt doesn't mean it deserves to be torn down.
Efforts like this need to be carefully nurtured because they go towards dispelling the prevalent aura of general guff that is spouted here in the development section on a daily basis.
To improve the study, make sure you are clear about the test conditions, and run the same test repeatedly until the mean and median converge to within some acceptable tolerance, e.g. 1%
You can then use standard deviation to make accurate statements about the data including its variability.
If you run multiple benchmarks you can later do regression testing to eliminate the tests that aren't correlated to the end result. You can combine the results of multiple benchmarks using the geometric mean.
If that's confusing, then I'll happily explain it in more detail.
Any more shenanigans, this thread gets locked. Either discuss the post like an adult or don't post.
You quoted my post about battery screens + on screen buttons but have not answered what is the deal with it.
What are those on screen buttons doing there on a official ROM for the 9023?
Already answered but maybe i wasn't clear enough.
I tested those kernel with daily usage aswell, that mean with mods apps and every crap i use daily. Those ss refers to the daily usage with my rom.
Yeah yeah I know its got Stamina Mode BUT! is anyone a little worried like me that the battery is 2330 and with a 5 inch screen and all those pixels its going to drain pretty fast. Todays phones with 720 screens and less pixels aren't the best. I'm still getting the phone but anyone else think we aren't in for glorious battery life here. (Stamina Mode may be the perfect fix for this though)
im hoping we get some battery reviews in soon. i have yet to see any real in depth reviews for the battery yet.
djq said:
im hoping we get some battery reviews in soon. i have yet to see any real in depth reviews for the battery yet.
Click to expand...
Click to collapse
Yeah, thats the part of the reviews I will be taken proper interest in.
Coming from the One X, I'm not too worried about battery life as I'd be fairly confident it could last a bit longer than that phone. I charge my phone every night so once I get a day out of it thats fine.
I would like to see a review on the battery life though.
2330 AMH is really good though
I have 3100mah on my Galaxy Note 2 right now. Pretty huge battery - was supposed to last 3 days - it barely lasts 48 hours of "normal use". Not worried about Xperia Z, if 3100mah can't supply more than 5-6 screen time or 48+ hours - no battery will. If it lasts 2 full days, i'll be more than happy.
From what I've heard it's actually surprisingly good. Keep your brightness in check and you'll be fine. Both the Snapdragon S4 Pro and the MDM9215 are pretty efficient chips. The S4 Pro has (according to Qualcomm at least) a pretty high performance per watt so should do pretty well with relatively little power use.
From the 1st review:
"The Z’s battery-saving Stamina mode turns off data when the screen is off, boosting standby time by a factor of four, and we found it hardly lost any charge overnight – around 1 per cent, or none at all."
Now that's interesting.
Early tests not so encouraging. Worse than the nexus 4. Of course screen brightness etc aren't known at this point.
Let's hope it gets better with more charge cycles etc.
{
"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"
}
Doesn't look too good. 9 hours with 3h screen time... but the screen drained 42% of the battery so i guess it must have been under some heavy stress. Hope to see some more tests/reviews asap.
yeah, all we can do is wait for the NDA to break. I really hate waiting.
hope the battery's up to scratch because i haven't been this excited for a phone in a long time.
When do nda normally break? Seeing as it should release in some territories in a few weeks, I'm surprised there haven't been more reviews. Hoping to see some from the big sites any day now, especially the verge, gsmarena etc, as I'm really interested in battery life. Would need about 3.5 hours screen on time on mid brightness on 4g over say 15 hours off charger to work for me. Guess I could make do with 3 hours, but whichever of the new 5 inch phones does this will get my money. Come on Sony, don't disappoint me, cause I love the look of this phone!
Sent from my GT-I9100 using xda premium
A) reviews take time
B) It seems as though the CES units were not final... so the final product may not have been available until very recently.
Sony stores/reps are starting to get their demo units (which should be final hardware) so hopefully more reviews soon.
BTW NDA is usually to keep the details of the product hidden until Sony is ready to release. The phone has obviously been officially announced so this is not an NDA thing, just the fact that they don't want reviews done on inferior pre-release units.
M.
mattman83 said:
BTW NDA is usually to keep the details of the product hidden until Sony is ready to release. The phone has obviously been officially announced so this is not an NDA thing, just the fact that they don't want reviews done on inferior pre-release units.
M.
Click to expand...
Click to collapse
And by looking at some threads here - it's perfectly understandable. People freaking out about things that are not even present in the real device like older software, lower benchmarks due to debugging firmware etc. But i'm really dying to see the battery life... if it's non-removable and it won't last 48+ hours of normal use, than it's not good. If it won't last 24+ hours of normal use than i guess i might reconsider ( and by normal use i mean texting, calling, maybe some music - not playing with it every second, that's reserved for few first days )
That screen shot over page with 9hr 33mins battery life. I didn't see the sign for power saver/battery saving mode being used. I mean surely the phone has to last a day atleast under moderate usage. I mean it has a bigger battery than the S3 and that lasted over a day on moderate usage and the cpu in the Z is supposed to be more power efficient is it not.
I also think battery life is a subjective matter for example me and my GF both had the note 2 and I set her phone up exactly how I set mine up with the brightness etc and she was getting 4days - 5days 20hours battery life and mine was getting 1day 20hours - 2days 23hours, why? because I use my phone a damn site more than she does and the variation is because some days I use more phone more than other days so some days the battery will last more and some days it will last less.
Akiainavas said:
From the 1st review:
"The Z’s battery-saving Stamina mode turns off data when the screen is off, boosting standby time by a factor of four, and we found it hardly lost any charge overnight – around 1 per cent, or none at all."
Now that's interesting.
Click to expand...
Click to collapse
Well that's not reinventing the wheel, most battery saving apps like Juice Defender do that. However I need a stable IMAP connection and not fire up the screen constantly to check emails.
There is nothing special in making the phone last longer with software trickery, it's like making yourself last longer through thinking about your grandma.
A good battery and battery efficient hardware is needed.
redThd said:
Well that's not reinventing the wheel, most battery saving apps like Juice Defender do that. However I need a stable IMAP connection and not fire up the screen constantly to check emails.
There is nothing special in making the phone last longer with software trickery, it's like making yourself last longer through thinking about your grandma.
A good battery and battery efficient hardware is needed.
Click to expand...
Click to collapse
Juice defender kills apps but issue with this is apps relaunch itself and then juice defender kicks in and kills it again and ends up in an infinite loop of killing and reviving of processes. The difference with stamina mode is that it was officially made by manufacturer within the ROM. So when you set it to get killed when screen is off there's something within the framework of the android core which they programmed to really halt the operation of the app/process and not just killing it. So in the end it is totally stopped
R89SONY said:
That screen shot over page with 9hr 33mins battery life. I didn't see the sign for power saver/battery saving mode being used. I mean surely the phone has to last a day atleast under moderate usage. I mean it has a bigger battery than the S3 and that lasted over a day on moderate usage and the cpu in the Z is supposed to be more power efficient is it not.
I also think battery life is a subjective matter for example me and my GF both had the note 2 and I set her phone up exactly how I set mine up with the brightness etc and she was getting 4days - 5days 20hours battery life and mine was getting 1day 20hours - 2days 23hours, why? because I use my phone a damn site more than she does and the variation is because some days I use more phone more than other days so some days the battery will last more and some days it will last less.
Click to expand...
Click to collapse
redThd said:
Well that's not reinventing the wheel, most battery saving apps like Juice Defender do that. However I need a stable IMAP connection and not fire up the screen constantly to check emails.
There is nothing special in making the phone last longer with software trickery, it's like making yourself last longer through thinking about your grandma.
A good battery and battery efficient hardware is needed.
Click to expand...
Click to collapse
The thing with the S4 pro is that it can go both ways as far as efficient hardware is concerned. I think it has something to do with thermal insulation.
The nexus 4 and it's 2100ish mAh has notoriously poor battery times - in my testing, tapping out at just under 3 hours screen usage in around 8-10 hours of total use (everything stock + 4.2.1).
My padfone 2, on the other hand, with the same battery/screen size is a battery champ - regularly get 5 to 5.5 hours screen usage over a period of 18-20 hours. It beats out all my previous phones for battery life (minus the note 2), including the GS3 which had good battery life itself.
And no, i don't belive in disabling google now and push notifications. Without them the nexus 4 does better but the padfone 2 and its s4 pro do brilliant with them on.
redThd said:
Well that's not reinventing the wheel, most battery saving apps like Juice Defender do that. However I need a stable IMAP connection and not fire up the screen constantly to check emails.
There is nothing special in making the phone last longer with software trickery, it's like making yourself last longer through thinking about your grandma.
A good battery and battery efficient hardware is needed.
Click to expand...
Click to collapse
No argument here - although if it actually does work - then it's a welcome trick. Juice Defender - imo - is useless. It never saved any battery for me - quite the contrary, constant app killing in the background resulted in worse battery life on my Galaxy S/Note devices, so i'm curious how will Sony implement such a feature.
Akiainavas said:
No argument here - although if it actually does work - then it's a welcome trick. Juice Defender - imo - is useless. It never saved any battery for me - quite the contrary, constant app killing in the background resulted in worse battery life on my Galaxy S/Note devices, so i'm curious how will Sony implement such a feature.
Click to expand...
Click to collapse
Why would you guys use JD for killing apps? That doesn't make sense. Its main use is to manage radios etc. depending on battery & screen status. Anyway didn't do much for me so switched from that to Tasker.
So, Antutu have released a new version of their benchmarking tool, which has a stability test built-in. According to the thing I read, this was inspired by the issues caused by the N4. It's hard to interpret the test fully. It says a straight line is good, and a curved line is bad but under temperature the line is relatively straight however under stability the line is curvey.
I assume that means they suggest it's unstable but I don't know, I'm running it on the S1.
Samsung Galaxy S and the Nexus 4 (in that order)
The Nexus 4 has a wavier line, but does this mean anything in the grand scheme of things? I've not had any red light issues yet.
To me it looks like l'art pour l'art (art for art's sake).
It is a totally unusual use case for a mobile device.
By their nature mobile devices usually always have the "burst mode" type of workload. I.e. do something very quickly for a fraction of the second and then get to sleep.
If only for the sake of "fluidity", users expect immediate response to their touches. Preferably within 100-200ms. And if you can deliver response, then you have already mostly done with your computations and CPU can return to idle.
Of course I am oversimplyfing, but this is how it usually is.
No one is doing any large "data processing jobs" on their phones taking many minutes to complete.
One could say, that properly designed device should be capable of the sustained load over unlimited periods of time. But do we really want it?
Because there are only two posiibilities:
1. make the device bigger and heavier (i.e. add something to dissipate that heat)
2. throttle device out of the box.
Like fixing the imaginary "problem" for 0.1% of benchmark freaks by making it worse for the rest 99.9% of users.
Well, temperature rises under constant load. The higher the temperature, the less stable the device is. What I do not understand is what does y scale on stability graph mean.
Hey guys, just picked up the nexus six and am writing this all out on it right now so excuse any errors. I just have a few questions about what to expect from rooting this device/Roms in general. Roms for the device anyways...
So I've heard encryption slows the phone down by about a 50% mark and am curious as to peoples experiences before and after decryption. Does it truly feel to you that your device is 100% faster? If so, what makes you say that? The phone feels plenty fast to me at the moment, but I'm always interested in a little more...
I've also heard about the horrible battery life of the phone being caused by a sensor_Ind wake lock, among other things like the large screen and resolution. Has anyone experienced long enough to prove its not placebo, a noticeable, or even dramatic increase in battery life because of a ROM/kernel/theme. If so, what ROM/kernel/theme helped you the most?
And lastly, has anyone tried any of the more experimental mods out there on this device? Such as adding multiwindow, or blinkfeed? If so, how did it work out for you?
I'll be trying a lot of stuff while here so I'm just curious to ask the others out there how things have gone so far for them.
I am stock rooted and still encrypted, and phone is plenty fast for me. I have never unencrypted, so I can't compare the two. Currently I'm running Franco's r10 and the battery drain in deep sleep is incredibly small, and it is smooth as can be. He has done a good job on this kernel. I don't really have an issue with the sensor_ind causing excessive battery drain, but I don't monitor that kind of stuff constantly. I have uninstalled my battery monitor apps, as I find I don't need them because my phone will last me a couple days on 1 full charge.. If my battery life takes a dump, then I'll re-install them and take a look.
Is encryption worth it? A couple days is a sweet statistic though. I'll have to root soon and throw some stuff at my phone, hopefully grab one of the odexed Roms that are available as I tend to lean towards em
So far battery life to me is about 4 hours sot which isn't horrid. And I like the speed but the jitters on occaision bug me. I love the touch response on this display though feels like butter