Related
First off, this might be a topic for the general forum, but since is pertains directly to development, i thought i would put it here... Mods.. please move if you feel this is inappropriate.
There seems to be some HUGE differences with Ava v10 and battery life and i wanted to try and narrow down what the differences are to see what is up!
What i am curious about and would like you to post is the following:
Hardware Version
Screen
Kernel you are using
battery life / Usage
If we are seeing a pattern here then we should be able to determine the problem and hopefully yield some good data for devs to use. If it is still very random.. then its got to be an app that is causing the issues.
I will start
Hardware 003
Epson
Stock Kernel
8 - 9 hours MAX on moderate - use (lots of texting, some calls, and a little web browsing) Was getting WAY better on v9 before 3.30 update (v9a)
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
It seems only hardware version 0004 is mostly unaffected by the new frame software and I know the only difference is camera hardware but that may be it
Sent from my EVO at the edge of hell
Hardware: 003
Screen: not sure how to tell I am a newbie
stock kernel that comes with AVA V10
Right now I am home and not on the road working so my useage is lighter but I did go to bed last night with >50% life remaining and the phone had been off charger >15 hours
4-5 calls none were more than 5 min long
a little texting, couple emails (with polling every 30 min from 8-8), FB and Twitter updating at a regular interval (about every 30 min)
Bluetooth on for around 2 hrs, wifi on most of the day as I was at home using my home network so it was connected and not scanning.
Went to mall for about an hour and that has notoriously bad Sprint signal inside most places.
I ran the following:
hardware 002
Novatek screen
kernel: HTC 10, HTC 11, HTC 17, Kings #10 & #11 (both variants), Netarchy 4.1.9.1 & 4.2.1 beta (havs, no havs, bfs, cfs, smartass)
Some web browsing, facebook, texts, maybe 10-20 min of calls per day if that.
I'd get MAX 6-8 hours from fully charged to completely dead.
Went back to MIUI 11.19 and am consistently getting 15+ hours with moderate to heavy use.
If I try and run any ROM with the 3.30 file system, my battery totally sucks no matter which kernel I use.
Evo hardware version: 003
Screen Type: unknown (don't know how to tell)
3.30-ROMs tested: Ava V10, EViO 2
Kernels: various, in text
When I first switched to the first 3.30-based ROM, I noticed a big reduction in battery life. I tried another and ran into the same thing.
After one day on Ava V10, on a recommendation I tried the EViO 2 v1.6, along with the "netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS)" kernel, and with extremely light usage (1 short call, and few texts) after 19-hours I was showing an 89% charge. With this kernel the phone slept very well. The problem was that with that same kernel, even moderate usage sucked the battery very quickly.
So, based on things that I read I switched to the "netarchy-toastmod-4.2.1-bfs-bfq-havs-more-smartass-universal (More Aggressive Undervolting)". Using this combo, sitting on my desk with zero usage for 11-hours it was displaying 89% charge, so sleeping did not appear to be as efficient. However through the day, normal usage (moderate) seemed to provide a bit more time per charge. It did not appear to be a drastic difference.
On another recommendation, I then tried the netarchy-toastmod-4.1.9.1-cfs-NoHAVS-universal kernel. Overnight, no usage, after 9-hours I was again at 89% charge. Normal usage netted slightly worse time than the netarchy-toastmod-4.2.1-bfs-bfq-nohavs-smartass-universal (No HAVS) kernel provided.
Behavioral observation: The 4.2.1 No HAVS kernel produced slightly higher Quadrant scores than the 4.1.9.1 kernel did, but overall in normal operation, the phone was more sluggish and draggy on the 4.2.1 kernel, while being snappier and feeling faster overall using the 4.1.9.1 kernel.
Also, please note that the best battery time I ever got on any 3.30-based ROM pales in comparison to my experience earlier in the year with DC3.5 and an older Toastmod DC-compatible kernel. Once, after almost 21-hours off the charger, light usage throughout the night and at the very end of a 3+ hour phone call, I got the charge warning that I was at 15%. I don't know why I changed.
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
bender1077 said:
Hardware Version: 0003
Screen: EPSON
Kernel you are using: STOCK
battery life / Usage: MOD to HEAVY USAGE - OVER 25 HOURS on FIRST FULL CHARGE of battery!
NOTE: I also had AUTOKILLER set to STRICT during this entire time, and not to AGGRESSIVE.
Detailed post with pic showing my over 20 hour mark still in the GREEN:
HERE!!!
I'm now in the process of trying out Net-TM 4.2.1 CFS-HAVS-LESS AGG with V10.
Click to expand...
Click to collapse
what was your "awake" time with this? This will be the tell.
When i ran ava 10 i got like 10 hours max. Alot of the 3.30 roms sucked my battery life. Fresh 3.3 rom gave me best battery life and i upgraded to his 3.4 and my bat sucked. Now im running airbourne rc4 and i think im getting the best battery I've ever had and its 3.30 based. It does have the sense launcher removed but all other sense is still there that could be the problem.
Novatek and 003
I decided to reload v10 and only restore a few essential apps and see where i was at. i did this, and had a full charge late last night.
This was with ALL settings defaulted to what is in v10 and no setcpu. The ONLY thing that i changed was the autokiller settings to "optimum"
It has now been 14.5 hours since i unplugged it (7 was me sleeping)
and "awake time" has only been 2.5 hours
It has been a pretty light day for usage - couple phone calls, mostly texts and emails and i am at 50%
This is MUCH better, but i really have not used my phone like i normally do. And this is with only a few apps installed.
frettfreak said:
what was your "awake" time with this? This will be the tell.
Click to expand...
Click to collapse
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
bender1077 said:
I think was a little over 5 hours. I'll have to remember to get a pic of that next time
Click to expand...
Click to collapse
huh.. thats pretty good! lol... hmm..
a little off topic......how do you tell who made the screen on your EVO?
skydeaner said:
It is apparent the 3.30.2/3 has drastically ****ed battery life. There has been way too many posts about it to ignore it now.
It isn't HTC kernel 17 related like someone said earlier either. It goes deeper than that because I never run HTC kernels, not even for 5 minutes after installing a rom and I notice it very much. It appears that the current during idle isn't affected. And it isn't a rogue program PR anything keeping the CPU from idling. I dunno what it is. But it really is very noticeable.
I wish more dev's would realize it and make updated 3.29s with some of the new stuff built-in like the pnotification pulldown switch thing, and stuff like that.
Thanks azrael so far for not ignoring the situation. Lol. I'm sure HTC will put out a version 3.40.00 or whatever that has ackrite for all hardware versions. And then it will be easier on the devs
Click to expand...
Click to collapse
nYdGeo said:
...
At this point I made an inquiry through a friend and was told that the difference between the 3.29-build and the 3.30-build was that the 3.30-build has a few small changes made to support hardware changes on version 004 Evo's only. I was also told that 3.30-build ROMs were not going to run well on 001-003 Evo's. I'm sure that is not absolute and they can be made to, but it may take some work.
Sorry for the novella, and I hope that it helps. Thank you for your time.
Click to expand...
Click to collapse
So dont remember where I got this from (someone in another topic), but it completely confirms everything that we have been talking about...
NO 3.30 rom is made for hardware 001-003 period.. directly from sprint.
http://community.sprint.com/baw/com.../blog/2010/11/05/htc-evo-maintenance-releases
so the problem now is devs are either going to have to split their roms in to 2 branches (one for pre-004 hardware and one for 004 hardware) OR... sprint need to come out with a unified release. SO... hopefully devs will read this and make changes accordingly
hi guys, is anyone messing about with these yet, just been flicking through the sections and didnt come across a thread for these models, just wondered why, any help appreciated!
i dont think they've sold as many as the gen 8's. simply because the releases were so close to eachother.
Close to each other?
1 year is not close.
The reason might be that the devs still are waiting for the real version, the 1.5GHz OMAP4460 before buying one.
me too
i wait !!!!!!!!!!
Not a bad idea either way... Can someone lQQk into it?
y but mainly i dont wait for the CPU power but for (hopefully) some usefull memory setup (1GB) and not the same crap they did to the Gen8 series.
Really they build such a nice device but the only thing preventing it form being AWSOME is the low memory...
What is the average data transfer rate of the WiFi radio in the Gen 9 tablets?
I'm curious if it is the same Bull Sh_t max 54 meg/sec rate in the Gen 8's, which just barely allowed Archos to label it as having 801.11n capability.
i have all gen9 with 1ghz
if you have questions !
I got the 80 G9 yesterday. Looks good. Zippy. But I see there is at least a second lag between pressing the power button and the lock screen coming on. and today morning, I think (after a night's rest), it went into a SOD. I had to hold down power screen for a reboot. Anyone else?
Had mine for over a month now...
I like it a lot. It's a lot snappier than the Gen8 models. Archos did increase the memory by 50% but didn't go to 1GB unfortunately; still, it works very well at 768MB.
I got mine on September 27th and I've been using it daily ever since. Works very well. The only negatives I have to say about it is that they haven't released the 3G stick for the US yet and it does sometimes lockup and require a reboot. Archos has released three updates since I got mine. The tablet froze on me twice the first weekend I had it; keep in mind that I was really using it hard during this time, adding apps and music and such. After I finalized my initial setup, it became more stable. I received an update the first week I had it, if memory serves, and afterward it was very stable. Then I received a second update a week or so ago and afterward, it started locking up periodically again. I downloaded the latest update last night and I'm hoping it corrects the locking up issue but nothing was said about that in the change logs. Even so, it might lock up once or twice a week and is easy and quick to reset; so, it hasn't been a major issue for me yet. I'd still like to see them stabilize the device though.
Regards,
Jack
Hi Jack,
I've just received one and it has the ripple just in front of the full size USB port when you press on the back. Have you seen this problem or heard anything definite about the fix/repair for this issue?
Thanks
Are you referring to something you see on the screen, like a pressure point as if the screen is being squeezed? If so, I have seen that on mine from time to time but haven't been concerned about it. If I had to guess, I would say that they packed a little to much hardware in the case at that point.
Is that the battery of A80 G9 is as much as the A70IT? I search on google and everything is culculated by using hour but not mA.
I don't really know if it's the same battery or not. If I had to guess, I would say it's more likely the same one that was in their 101 model from last year (or similar) because the screen on the A80 is quite a bit larger than the A70 and brighter too. But I just don't know. For all I know, it could be a completely new battery. I do know that the battery life on the tablet is very good. I mostly use mine for reading ebooks, internet browsing and e-mail and I normally get a couple of days out of it before charging and even then, it's usually at the 30 - 50% level when I plug it up. I have no complaints about the battery to date.
So how many percent that the battery drains per hour when u r brownsing via wifi or reading book? The A70IT's battery is 3850mA and it is not enough for me. But the A80 is running Android 3.0 so I think It will drain more battery than A70 running Android 2.2 does.
I have the A70 too; used that up until the A80 came out. I never really had trouble with the A70 running out of power on me but it seems to me that the A70 does drain faster than the A80. I haven't really monitored it in any scientific way. If it were giving me problems I would but it works well so I haven't bothered. I read on it more than I browse and I'll read anywhere from a few minutes, an hour or sometimes two or more hours at a time. And it seems to drain pretty slowly to me.
I also use it for testing mobile solutions at work and sometimes have it on for an hour or more at a time while running tests. I can't give you any sort of accurate number but it does do well on battery. If you've used an iPad any, I would estimate that it is comparable to the iPad for active battery use. I don't know about idle because mine is never idle more than a few hours at a time while my iPad is sometimes idle for days at a time. I suspect, that on idle, it wouldn't compare as well to the iPad because for some reason, Archos likes to leave that power LED burning all the time.
Anyway, when compared to the A70, in my usage, the A80 seems to do better on battery use. I used to have to charge my A70 every night but like I said ealier, I only charge my A80 about every other day and if anything, I use it a little more than I did the A70.
---------- Post added at 12:17 PM ---------- Previous post was at 12:13 PM ----------
Oh by the way, I used to leave the Wi-Fi turned off on my A70 to conserve battery; just turned it on when I needed it. I don't do that on the A80 and it still does better.
Thank 4 ur information. I've tested A80 at a retail store and a surprising thing was that the back of the A80 began to get hotter after 5 minutes watching youtube and began extremely hot after ~10 minutes. I dont know that device had any technical problem or not but my A70 was hot if I brownsed or watched youtube for more than half an hour. I think when the A80's chip is getting hot, It will drain more battery.
And one more thing, is the soft keyboard of A80 sensitive or not? I cant test it because the salesman was not happy when I had a device test. My A70 got a problem that after I have a long press on the screen, It will take 1s delay to press another key. For example, when Im gonna type [email protected] on my A70 soft keyboard, the screen just only appears [email protected] (letter "g" is disappeared). I make a long press on letter "A" to type "@" instead of use "alt". Is it normal or not?
So since I had my nexus 4, I had to complain about its terrible battery life.
I would never get more than 3h of screen on time, despite my best efforts in conserving battery. Even with the phone in flight mode and on Wifi, I could not cross 3h give or take a few minutes. I even tried disabling location, google now, sync and everything else.
It was deep-sleeping nice, while the screen was off, standby time was awesome for me. If I turned it on though, it started to burn through battery insanely quick. So I started monitoring the frequency states with battery spy, and noticed that as if there was a little load, it spiked to 1026MHz and then stayed there for about three seconds every time before falling back to 386 MHz. So I tried setting the max cpufreq to 916Mhz with CPU tuner, and was astonished to find out, that immediately after the load was done, it went back to the lowest frequency. Like it should be, not hanging for multiple seconds on the high step.
Also, If I start CPU tuner, the min freq is always shown as 1026MHz. So I changed min to 386 and max to 916. Afterwards, this stays until I swipe cpu tuner away from the recent apps list. If I start it again, the settings revert. Strange...
With my cpu limited to 916MHz, I get about 5h and 50 min of screen on time without any other measures. Location on, Wifi on, Google now and sync all active. If I just go one step higher and set my max frequency to 1026, the old behavior starts again, and screen time drops to 3h because it seems to be stuck on that freq. Therefore I would like everybody who also has bad screen time to try that out and report back.
I don't really understand why it would take so long to drop back from the 1GHz step, and drop back immediately from the 0,9GHz step?
Of course, this is with normal surfing via chrome, or using normal apps that are not that much CPU intensive. Also, you hardly notice the performance limitation without playing games. There probably is an easy way to fix this?
Feedback would be appreciated. Maybe I see this wrong...
Thanks
tl;dr : if screen on, for me only 1026mhz is used, if max freq is set to anything lower, the phone spends most of the time at the lowest step 386mhz, greatly increasing screen time for me.
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
NoLunchBox_ said:
Flash Franco Kernel and buy the app and you'll be set.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Maybe, but I really first wanted to examine out of the box behavior
This is caused by qualcoms Mpdecision which ramps up the cpu to 1ghz on screen on and touches. All in the name of speed. It's basically a hot plugging technique such that smoothness is guaranteed under loaded gui transitions and scrolling. Before this you would have to wait for the cpu to be loaded for it to ramp up speed. Now the OS can demand speed.
You can see in Franco kernel he replaced Mpdecision with an open source alternative and swapped the lowest cpu speed to 368mhz. Then added a load step of 768mhz (for 60% loads). This actually added a bit of lag but should be better in the battery department. Some more tweaking to be done though.
Qualcoms thermald is what is causing thermal throttling.
Edit: this could be wrong. But I think I'm in the general area of what's going on...
Sent from my Nexus 4 using xda premium
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
ArRaY92 said:
This does sound logical, but why the hell waste nearly half of the possible screen time on "perfect smoothness" when even if limited to 0,9ghz everything runs pretty amazing... I will look into francos kernel, even though I dont like to buy an app to tune it,
Click to expand...
Click to collapse
You don't have to buy an app, everything can be set through scripts. The app just automates the process, allows you to back up kernels, download the latest nightly and milestone (when one becomes available). It's really worth the investment, plus you're helping out a great Dev who has shared his awesome work with us for a long time.
Sent from my Nexus 4 using Tapatalk 2
I like my phone to sleep. I bumped it down to 384!
No need to keep it @ the 1.026, it will pretty much kill battery! Makes no sense to me.
Sent from my Nexus 4 using Tapatalk 2
You can set the max to 384 mhz.. and still everything is smooth
Can I use SetCPU or is that app defunt now? And to change my CPU speeds can that be done on a phone that's simply rooted or do I need a custom kernel?
EDIT: I downloaded CPU tuner, but I'm not sure if it's working or not. Does it work w/ stock kernel or no?
Faux's Intellidemand fixes pretty much what you're describing. Since mpdecision is not used instead of fauxs alternative.
Sent from my Nexus 4
What is max frequency by default?
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
biffsmash said:
Have to say firstly, that the perfect smoothness of this phone is what has sold me on it as the camera is well below average, it has some bugs and the output quality and volume of the audio is shocking, but it is the single smoothest phone out there.
Get rid of what I came to know as Touchboost (feature brought in in jelly bean to introduce the lag free experience of project butter I imagine) from my Sgs3 days, and the phone becomes as laggy as every other android phone out there.
Secondly, I get around 3.5 hours screen on time, without messing about, wifi on constant, depending on whether i'm on the net or not, I can get more.
I find AOKP perfect as its super fast and battery is excellent.
Franko kernel works, but the phone then feels choppy. Setting the cores to 1ghz makes the phone laggy also.
All I can say is, get lots of chargers, I have two at home, two at work, one in the car, one at the other halfs, and it's trickle charging when and if I can and I never worry about battery anyway. I find it wastes far too much life.
Good luck.
Click to expand...
Click to collapse
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
ksc6000 said:
Thank you for not contributing to this thread with that useless comment. The rest of us may not want to charge the phone 1500 times a day (or are even able to), and are looking for ways to help battery discharge go slower while using the phone. If you're fine with charging your phone nonstop, then what are you doing in this thread? Everyone knows you can buy many chargers, that's not a solution.
Click to expand...
Click to collapse
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
[hfm] said:
Welcome to Project Butter. If you want to do something different than Google's goals for UI smoothness and responsiveness, which is what everyone has been complaining about in Android vs iOS, then you'll have to go the custom ROM/kernel route. Thankfully that is easily available to you on this hardware and software platform. Me? I like the N4 just fine the way it is stock.
Click to expand...
Click to collapse
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
ArRaY92 said:
Dude, this has nothing to do with googles project, but instead with Qualcomms responsivness "fix". Please read the answer to my inital post, and you will understand. Also, the phone does in no way feel choppy if you restict it to .9ghz. Except if you load it so much, that it cant cope with this max frequency. But then again, this is not the issue, but the issue is, that 1026 stays active for to long, so that it burns through your battery. There would be only a small change needed to change this behavior, and "possibly" loosing about a fraction of a second of responsivness, that most of the time you wouldnt even notice... Everybody who tells me he is happy with barely 3h of screen time or even less is just the android equivalent of an isheep, because this is in no way acceptable.
Click to expand...
Click to collapse
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
[hfm] said:
I'm getting around 4-5. Auto brightness, 1 Gmail push, 1 touchdown push, Google now on, HD widgets weather, greader pro syncing, falcon pro syncing, all location services on (I like the monthly reports). Wi-Fi when I can.
Click to expand...
Click to collapse
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
My min CPU speed is 1 GHz and in still getting 4 hours on screen time though. I don't think setting my min at 384 MHz even made much difference in my battery, will try it again soon.
Sent from my Nexus 4 using xda premium
droyd4life said:
What kernel are u using? Im using franco kernel + latest CM 10.1 nightly.
Click to expand...
Click to collapse
Stock never rooted bootloader still locked.
If you are getting bad battery... simply flash a custom kernel. You get to keep your stock ROM or whatever but you will get substantial benefits. I prefer Trinity Kernel. Only the second or third update on this kernel and now the phone has made huge gains in battery life. Like hfm, I good on screen time... usually 5-5.5. I have auto brightness on, mobile on 100% of the time, and all Google services synced including books, gmail, currents, google now, etc etc. I have locations on, gps on... everything. Sometimes I turn off NFC because I rarely am somewhere where I can use those cool RFID card scanners. What sucks battery is probably a problem in Android 4.2. The phone does not sleep as much as it should. Go ahead and turn all your sync stuff off and keep the screen on static and let the battery die at stock clock speeds. Probably will get at least 5 hours with auto-brightness on. My phone probably sleeps 60% of the time now according to CPU spy when it sits idle in my car for my 8-10 hour work day. I usually get to the car with a bunch of emails, a text or two waiting for me, and the phone has only been asleep the aforementioned 60% and around 90-91% battery life. On a new phone, starting from full charge, this should be at least 95%. My N10 that doesn't have mobile data, only loses about 1% overnight. Apples to oranges but still. I'm convinced that stock voltages on this device are too high, and that Qualcomm did not give Google the latest drivers... maybe because it's not releasable to AOSP as of yet. I really don't know, but it's gotta be something buggy. This SoC is capable of doing better... and it does in the Optimus G and even with sense, 1080p screen, and a 100mah smaller battery the HTC Droid DNA/Butterfly gets 3.5-4 hours stock screen time. None of the other phones using the S4 Pro are running 4.2. I'm hoping either Qualcomm pulls a Samsung and releases some updated drivers/firmware that Google can incorporate or that Google fixes whatever bugs they may have not worked out. In the next calendar year other phones will be out that use the S4 Pro and 4.2 and I doubt Qualcomm wants to lose the luster it earned with the regular S4 Kraits performance/efficiency. When 4.2 comes to other devices we will probably know whether or not Google is to blame for this or that the Nexus 4 is just a poor performer.
One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!
I agree, it's a very crude and inefficient way of doing it. Android is designed for maximum fluidity so they assume that every time you touch the screen the cpu will be put under load, thus the cpu ramps of the frequency - this is commonly known as touchboost. If you have a custom kernel like dorimanx you can modify it to lower the touchboost frequency and various settings so it could potentially lower battery usage during input. Although I don't know if it's worth it considering all of the various potential problems that go along with such a kernel..
iOS and android are so fundamentally different that I doubt you can (easily)modify it to perform like ios in a given workload. However, each manufacturer has their own flavor of android so they may be optimized differently. Either try several different models or just go with an iphone since you've tried it and seemed to like it - or you could always wait for android n which will hopefully be more clever and efficient..
you could try intellimn this stays at lower freq, when more power its needed it boots to higher frequencies. that along with allucard hotplug. should save battery this is with dorimanx kernel.
with ondemand its the same. or if you want more lower use smartassv2
I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?
ksc6000 said:
I returned the iPhone. The fact that it doesn't repeat notifications for missed calls is abhorrent to me. I need to be able to glance at my phone and know that I've missed a call with the screen lighting up every few seconds or a LED light.
So I'm definitely sticking with the G2 for now.
If I install another kernel to give me more governor options, how difficult is it to put back the stock AT&T lollipop kernel? Can I back it up first in any way?
Click to expand...
Click to collapse
Yes you could either use twrp and back up boot. or use flashify from playstore to back up stock kernel.
ksc6000 said:
One thing that has always bothered me is how quickly (relatively) the battery drains on any android phone i've had in the past 6 years when typing. I can read articles, scroll webpages and whatnot for hours...but if I'm having a heavy day of instant messaging, my battery drains much faster. This makes sense due to way that this phone and most android phones ship with the ondemand governor. Just to test, and you can try this too, in better battery stats or some other app that can monitor CPU speeds, set a custom reference and then type for one minute in a note keeping app or an instant messaging app. Then go back and check. What you'll find is that the CPU frequency stays at max 80% of the time or more, because the screen is being touched the entire time. So to me, that is horribly inefficient.
I went ahead and bought an iPhone 6s to try to see if iOS handles typing better, and it does. I can get about 6-7 minutes of nonstop typing before the battery drops 1%, whereas on mine it can be anywhere from a minute and half to 3 minutes tops.
I want to see if I can clamp down on this so I found this post but it's very specific to the Nexus 5x: http://forum.xda-developers.com/nexus-5x/general/guide-advanced-interactive-governor-t3269557/page51
What do you guys think? I'm not nearly well versed in this kind of stuff so I need some help. Let me know!
Click to expand...
Click to collapse
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.
ksc6000 said:
So this is not a scientific test at all, but I usually will use whatsapp for messaging nonstop during my 1 hour lunch at work. No browsing or anything else is usually included in that. I have a few conversations going so I'm typing and getting messages non stop. Previously that would decrease the battery by 22% or so. Now by switching my governor to interactive and making tweaks to it using EX Kernel Manager, with this it's down to 14%. I will admit there is some minor stutter when first turning on the screen with the settings I'm using so I'm sure I need to keep tweaking but my main concern is the battery life while typing.
Previously as I mentioned if I'm typing, the CPU speed would go up to max and stay there until I'm done typing for a few seconds. Now with these tweaks my CPU speed barely goes up above 960 MHz...most of the time it's between 640 or 883. I think that's the reason I'm getting 4 to 4.3 minutes of screen time now while typing instead of getting anywhere between 1 and 1/2 minute or 3 at best while typing.
Click to expand...
Click to collapse
if you use smartassv2 its lower.
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Its got a crappy Nvidia CPU in it, thats the issue. Like my N9, that too is crap, again, Nvidia inside.
edisso10018 said:
For charging you need a 2 or 2,5 A charger. Then it will charge (if it's not faulty) in around 2 hours. The screen overlay message is coming from the quick launcher (or how it is called). So disable it or give it the right to draw over other apps.
I don't have problems with lags or touches. Are you on the latest updates?
Click to expand...
Click to collapse
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Sent from my SHIELD Tablet K1 using Tapatalk
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
PearlMikeJam said:
I am using the correct rated charger. This even happened when charging with the tablet off.
I am on the latest update. I waited to install my apps until after all updates were applied. The touch issues may be lag related. The back button almost always requires multiple touches. Keyboards often time register multiple touches or just freezes.
I am also noticing network issues. Apps report loss of connection when the wifi shows connected.
I hate to say it, but I am leaning towards returning this for a Samsung.
Click to expand...
Click to collapse
That lag is not normal. And my tablet charges from around 10% to full in about 2 hours. Maybe you should try a factory reset. If that doesn't help I would return it.
I won't buy a Samsung tablet. I would try a replacement. I own the k1 for a year now and I'm still very satisfied with. And Nvidia updates it. Which Samsung usually doesn't.
Don't listen to Nvidia trolls... ⬆
Your experience does not sound typical. Perhaps it's a hardware issue, but I agree with @edisso10018 that the first step would be a factory reset.
Wish you luck!
The Nvidia CPU is pretty good shame it's not the X1, It performs better then some of my phones with QC chips, Do a factory reset and see if the lag is still there, Battery life is poor can agree on that
My k1 is over a year old it is still playing games with no trouble yes a agree with the battery life but mine charges with no problems a have noticed a little slow down but am not running bit os updated kernel yet but a still rate 10/10 best tablet a ever owned.
Tablet is laggy, no denying it.
Sent from my Pixel XL using Tapatalk
ctap001 said:
Also a recent owner of the k1. Running stock firmware (1.5) but with BitO-K kernel. The only thing I am experiencing is mediocre battery life, charges from 50-100% in under an hour using a 2.5A charger. The only thing that sucks, and this goes for android tablets in general, is the removal from 4.4 of the TabletUI. Seeing we're already at 7.1 and TabletUI is still dead, it looks like we'll have to fight to get it back again.
Click to expand...
Click to collapse
K1 here-- I don't run stock (DU 6.0.1), but I used BitOK for a while and realized its not very good. Switched back to stock kernel (from my ROM) and its more stable. You don't lose out on much anyway-- BitOK doesn't have features I want like voltage control. Examples of instability caued by BitOK: GPU was stuck at ~350mhz, would not ramp down fully to 72mhz. Also stock is smoother. You can still use adiutor to monitor and control a few things.
One more thing: be very careful when flashing blobs and other stuff in fastboot that it is for the K1 version and not OG shield! A lot of devs posting these things arent explicit as to which version. DTBs and Blobs are specific to the shield type-- one might work for the wrong tablet version, or it might brick it, or it might be unstable.
As for the Batery life I can tell you it does suck even on the best case scenario. There is no way around this as it is small and the large screen, as nice as it is, sucks a lot of juice. Lowering brightness helps somewhat but still I'll be lucky to get a couple hours of SOT out of it.
For the price its a great tablet, with a few small compromises, such as bat life, but thats the price you pay for great screen and sound at a cheap price. We are lucky to have at least a few devs still doing work with this device, and luckier still that nvidia is STILL supporting it with updates, even if slowly. They recently announced 7.1.1 will be forthcoming.
Mine was laggy too, I flashed stock firmware with my PC and now it's working perfectly.
Bought mine as a refurb and it works fine. I think you either have bad hardware, or a bad install. Try flashing stock and see if it improves.
Tbh my only complaint is with battery life, I switched to BitO to see if it got any better, the tablet is smoother with this kernel than stock but the battery is the same, I wish we had UV'ing, my favorite setting on any kernel, back on my N10 my battery could easily be improved 10-15% and the heat was reduced drastically, good binned ones could shave up to 200mV on some steps. K wish this was implemented
PearlMikeJam said:
I jumped in and bought a K1 to replace my dying GPad GPE. After 3 days, this seems like a huge mistake.
The K1 is very laggy in basic apps like Play Store and Chrome, does not register touches very well and has terrible battery life. I even charged it overnight and didn't get a full charge. On top of that, I am constantly getting the screen overlay message any time I need to enable a permission.
What could be causing this? This tablet is so highly regarded I don't get it.
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
I just bought a K1 (discount price 169€) and I don't have this problem at all. Even if I use only 1 core (settings performance) for basic app it's smooth smooth smooth.
And the battery life is huge !!
For gaming tho I switch back ofc the performance setting.
:good:
I bought a K1 three weeks ago to use as a display for my phantom 4 quadcopter. I am very impressed with its performance. I'm not experiencing any lag other than at startup. Once it's up and startup is finalized I dont have any problems. The battery life isn't great, I'll agree there but hopefully it gets better with Nougat.
Sent from my SM-G925P using XDA-Developers Legacy app
I bought a K1 last week to replace my aging Nexus 7, did a factory reset and still wasn't satisfied with it being laggy. Did my share of Google searching and finally stumbled upon a quick fix to try : disable Daydream. Since changing this one setting it has been very smooth since, no issue for lag or touch registrations.
Give it a try, might not help your charging but I did notice a much reduced battery drain while sleeping also.
My only other changes were to root, change the DPI to 240 and use the Google Now Launcher which compliments the display nicely.
I wasn't happy with it as well until I flashed cyanogenmod 13 and a custom kernel with overclock. Now it's a beast, battery is great, signal as well. And I also now have the option to OC the processor to 2.5 GHz before I play some more demanding games and then set it back to 2.2 or even lower if I won't need all the juice. Seriously, the stock marshmallow ROM sucks, I have only heard bad stuff about it. Also, the nougat update is about to come out so I'd give android N a chance, too.
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
grävling said:
About the battery life -- see which apps are using the most juice under settings/battery/. Some of them may be using more CPU cores, and have a higher frame rate than is needed. Go to settings/App optimisation/ and crank the numbers down. Next go to settings/Accounts and see the long list of things that want to autosync with you. Turn the autosync off for those you aren't using. Turning off wifi except when I am using it has made a significant difference for me as well.
Click to expand...
Click to collapse
Putting the CPU at 80 or 90% CPU speed in the performance settings will get you that reduced power consumption. You might not even notice the speed difference. These speed tiers also run at lower voltage.
Using the GPU frame rate limiter will dramatically extend gaming time too. I find 30 fps acceptable most of the time.
Of course it would be nice to run the thing unrestricted, but it's just not practical when you also want battery life. Look at what Nintendo is doing with the clock speeds of the X1 in the Switch.