Related
Given that the display is widely regarded as one of the two biggest drawers of power/battery life on the N1 (the other being the radio/cell standby), and given that my battery usage breakdown *always* has Display at the top (by a large margin), I thought it might be interesting to see what other people's Display usage hovers around so we can build up a "operating range"...
(apologies if anyone has done this before, I did a few searches but nothing significant came up - please point me to previous posts if it has already been covered)
not exactly seeing an option for a Poll...would recommend setting one up before we get 100s of posts to comb through
bloke226 said:
not exactly seeing an option for a Poll...would recommend setting one up before we get 100s of posts to comb through
Click to expand...
Click to collapse
you got there darn quick - cheers for voting though!
it depends on what rom u have. my battery usage for the display was significantly different from cyanogen to desire rom.
nellyspageli said:
it depends on what rom u have. my battery usage for the display was significantly different from cyanogen to desire rom.
Click to expand...
Click to collapse
that was one of the things that prompted me to do the poll, as I'm familiar with a Desire with Sense that reports around 20%
unfortunately I don't think i can also capture the ROM here (kernel would have been nice too), but I wanted to - and think you may have a point...
Moved as not Android Dev.
Yeah, unfortunately if you are getting a low display usage if you use it a lot means that the rest of your system is really hogging the power. Cyanogenmod with a high display usage is great because it means the rest of the system is running very efficiently.
Clarkster said:
Yeah, unfortunately if you are getting a low display usage if you use it a lot means that the rest of your system is really hogging the power. Cyanogenmod with a high display usage is great because it means the rest of the system is running very efficiently.
Click to expand...
Click to collapse
It could mean a few different things, not just that. This is not a very scientific poll, sorry.
Thanks for this Poll. I was beginning to think that maybe my Nexus One was defective because the screen used so much of the battery. Unlike my HTC Magic, where the Cell Standby/Phone Idle was king.
The screen is supposed to be the highest drain. That means that the OS and all your apps are very efficient and not out of control.
just FYI, it seems on the bleeding edge kernels that a couple of kernel authors are producing at the moment, that Display usage is down. I am typically seeing no more than 40% in the stats now (down from around 60%) - will update once the kernel dust settles!
this poll isnt really effective, i have seen my screen usage from 10% all the way up to 89%, from what ive seen the percentage is based off of how long since the phone has been unplugged from a charger to the amount of time you were actually using it(had the screen on)
i can run my battery life into the ground in 6 hours or i can make it last 34 hours(max from full charge to shut down with all the fancy stuff turned off)
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
FORMAT 1:
CPU
- [FREQ1] [VOLTAGE1]
- [FREQ2] [VOLTAGE2]
- [FREQ3] [VOLTAGE3]
- ,,,
Click to expand...
Click to collapse
FORMAT 2:
CPU GLOBAL: [OFFSET]
Click to expand...
Click to collapse
I also accept 1 frequency result. You don't have to undervolt everything. I favor the last known voltage that crashes as well if you can send this I am even more happy.
Undervolted mine by 50mv
Sent from my Nexus 7 using Tapatalk 2
djjonastybe said:
If you have undervolted your Nexus 7 or any other tegra 3 based device please post the results here so I can throw them into a Excel sheet for development.
Using advanced mathematics and complex formulas I will make a undervolted kernel that's stable for everyone. For that, I need ideally 30 results or more. Less is ok but more or equal is better.
Click to expand...
Click to collapse
In order to use "advanced mathematics" and "complex formulas".. You might want to provide a format for "the results" you want people to provide.. Without a stream of formatted data to input your "complex formulas" and "advanced mathematics" is impossible..
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
djjonastybe said:
..I will make a undervolted kernel that's stable for everyone
Click to expand...
Click to collapse
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
simms22 said:
ha! good luck. considering some devices arent stable at all when undervolted just a tiny bit, and otbers are stable with a lot of undervolting, you have a tough road ahead of you.
Click to expand...
Click to collapse
I actually came back to post exactly this but Simms22 was too quick, as usual!
Sent from my GT-I9300 using xda premium
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
styckx said:
I see you went with the more direct and honest approach. I tried being more subtle with my response.. :laugh: But yeah.. Marketing hype for a kernel.
Click to expand...
Click to collapse
Might as well be honest, set him on the right track early in his dev career rather than him rely on buzzwords and fud like some people do.
These are forums for android devices, not Apple devices, the reality distortion field doesn't work here, fancy marketing terms should be left at the door.
Sent from my GT-I9300 using xda premium
My Galaxy Nexus is proof of undervolting being unstable using software while being stable with manually programming the voltages. So I am going to give this a good shot anyway.
My Galaxy Nexus uses SmartReflex to undervolt.
Look at this table I made:
https://docs.google.com/spreadsheet/ccc?key=0AuqacKmGLKJ6dEdJZG5QTmNtQnoyYk0zbm5IanluMHc#gid=1
You see the core or gpu was already crashing at 974mV, which was the reason why I stopped undervolting using the thread. But don't give up, I tried again using SmartReflex because I felt I should be able to get lower. And now I am at 911mV but I did not try to get lower yet.
I plan on undervolting by actually programming it. I don't know how you guys undervolt for the Nexus 7, since I am fairly new with this device.
READ FIRST POST for formatting
nodstuff said:
"Advanced mathematics" and "complex formulas" sounds like you are doing an infomercial.
Pure waffle.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
http://en.wikipedia.org/wiki/Student's_t-distribution
Using that I can calculate which voltage to take that will work for 90% of us or 99% of us or maybe 100% ?
For that I need some results. The more the better.
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
nodstuff said:
The only voltage settings that will work for 100% of people are stock voltages.
you will run into endless problems if you release an undervolted kernel because what works for 75% of people won't work for the rest.
If you adjust voltages to include more people the people that can handle the lower voltages aren't getting the full savings their device can handle. Which defeats the point of releasing an undervolted kernel to save battery.
Undervolting should be up to the individual, just release with stock voltages and make a guide showing people how to undervolt.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
^^ Truth
I've done a bit of pc overclocking over the years and we'd always seek out the best steppings to find cpu batches that would give a better clock speed for less volts. What would work on one person's cpu wouldn't work on another sometimes even within the same stepping. (My current machine is getting long in the tooth but it's running a 33% OC below stock volts and stable as a rock.)
When the N7 cpu's are tested the stock voltage is the point where 100% of them will run without issue. Certainly there are many, maybe even most N7's that will run undervolted but until you try it you just won't know. Undervolting needs to be done on a case by case basis.
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
sorry to break the fun lol
Opened a thread with undervolting settings in different situation. For now i think its the lowest possible
bervin said:
I uv by 100mv on every step on Franco kernel and I've never had a sod or reboot. Maybe you could release different versions like light, medium and heavy to cater to different users that have sets than can uv more or less. To address all these people naysaying I say just go for it, don't let these people dishearten you from what you want to do. I'm sure there will always be users who are willing to try
Click to expand...
Click to collapse
That's exactly the same as what I have done. 100mV right across the board, and I have also never had a reboot or any other negative effect from doing it. Just a bit more battery life.
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
phonic said:
I too UV 100mv across the board. Never had an issue. And I OC up to 1.6ghz.
Click to expand...
Click to collapse
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
davidoff59 said:
Same here, no issues with 100mv UV on stock speeds. What would happen if we went too low, would it fail to boot at all or is there some safety mechanism that would allow us to boot into boot loader?
Click to expand...
Click to collapse
When either OCing or UVing, you should ALWAYS test out the changes prior to saving them as a persistent boot state. This way, if you set something too high/low and it proves to be unstable, if you restart the device it will revert back to normal.
In the event that you OC/UV too much, yes, you would see signs of instability. In some cases it could show up as soon as you applied to change, in other cases it could take a while to notice. For example, some games or other high processing powered activities could FC/crash. Or your tablet might freeze or reboot. But again, as long as you didn't save your changes as a boot setting, it will be fine once it reboots.
In the event that you did save it, and the settings were unstable for your device, you could boot up into recovery and then manually erase them from taking effect. Recovery doesn't use those settings, as it's technically a different OS. But that can be complicated a process for some. So test test test save. Or don't save and just apply them manually.
Two other points:
Yes, most (all?) devices do have safeguards to protect itself against permanent hardware damage from OC/UVing. If it gets too hot, they will often shut down to protect themselves.
And just because one device can handle being OC'd or UV'd to a certain level doesn't mean they all can. Very minor differences in each component can impact one devices ability from another. The manufacturers only test to see if they can handle the published speeds/etc., but in many cases they can go higher if set to. In others, not so much.
Thanks for that phonic. Given the range of ROMs and kernel's available and the improvements already built in, under volting may not help a lot but every bit helps. Eg this screen on time is pretty good.Close to six hours screen on time with iirc 35% battery remaining.
Paranoid android with motley kernel. I don't over clock the nexus 7 as its fast enough. In fact I under clocked it to 1000 MHz max before and it was still fast but the screenshots are at stock volts and speeds.
it's actually plain simple. If everyone posts results. I can make a kernel with voltages that work for 75% of all people or maybe for 95% of all Nexus 7 owners.
It's called mathematics. But to do that I need as much results as possible.
Easy to do if you know what you are doing, right ?
http://en.wikipedia.org/wiki/Confidence_interval
What this app is gonna do?
This will give you some boost that is really required to play games that are demanding on GPU front.
What this app require?
You need to be ROOTed and for that there is a really great app with one touch facility available! The link is http://forum.xda-developers.com/showthread.php?t=2387507
After you get ROOTed just install the Tegra Overclock OUYA EDITION app from attachment and click on OK for one click optimization.
You can also change the actual resolution to somewhat lower to again get a massive boost in GPU intensive games or shall I say those games that scale with GPU clocks very well. (I can confirm nearly 2X boost in RipTideGP2 with all settings maxed out when comparing with 1080p to 720p option provided in the app :laugh
Any kind of hazardous warning before use?
If anything goes wrong then you know where the power switch is! Close the console and cut the power and start again. We have not implemented the on Boot settings for safety reasons...
What about future updates?
I just wish that 4.2.2 gets for the OUYA and that will be a game changer for the console as that support full screen scaling on resolution changing vs screen compensation provided by current android 4.1 version....
NOTE: The app is fully free to use one click solution for OUYA owners and don't require you to get involve in any of cracking stuff Still the app does costs us in development and support front so any kind of donation will be greatly appreciated. If you are planning to buy any Tegra device in future then you can support us by purchasing the original Tegra Overclock app from the market that will in turn benefit you as well..
BTW don't forget to hit the thanks button
EDIT: Version 1.1 Change log
*Nothing new just made the interactive governor as a default rather than performance governor due to heating concern.
*Checked the code so that 2D GPU is set to 520 MHz too, in case it still reports half let me know..
EDIT: Version 1.2 Change Log
***Added requested LBCMT (LastBootCpuMaximumTemperature!) This shows the maximum temperature your device went during last boot.
***Added apply on boot (Works only when the USB device with at least a single file is detected to ensure you don't intentionally mess up anywhere )
The LBCMT will works as soon as you boot once after you open the app for the first time. Also note that YOU SHOULD NOT KILL THE APP manually by task killers or the reporting will be fake. BEWARE....
EDIT: Version 1.3 Change LOG
***Full screen stretched resolution support for CM11 Rom users. Use the special newly added resolution (will only work for CM users currently as no other 4.3 or 4.4 Roms available)
Fixes for temp not showing on custom kernel like EPRJ Kernel.
Thank you for being patient.
Kingshoo said:
What this app is gonna do?
This will give you some boost that is really required to play games that are demanding on GPU front.
What this app require?
You need to be ROOTed and for that there is a really great app with one touch facility available! The link is http://forum.xda-developers.com/showthread.php?t=2387507
After you get ROOTed just install the Tegra Overclock OUYA EDITION app from attachment and click on OK for one click optimization.
You can also change the actual resolution to somewhat lower to again get a massive boost in GPU intensive games or shall I say those games that scale with GPU clocks very well. (I can confirm nearly 2X boost in RipTideGP2 with all settings maxed out when comparing with 1080p to 720p option provided in the app :laugh
Any kind of hazardous warning before use?
If anything goes wrong then you know where the power switch is! Close the console and cut the power and start again. We have not implemented the on Boot settings for safety reasons...
What about future updates?
I just wish that 4.2.2 gets for the OUYA and that will be a game changer for the console as that support full screen scaling on resolution changing vs screen compensation provided by current android 4.1 version....
NOTE: The app is fully free to use one click solution for OUYA owners and don't require you to get involve in any of cracking stuff Still the app does costs us in development and support front so any kind of donation will be greatly appreciated. If you are planning to buy any Tegra device in future then you can support us by purchasing the original Tegra Overclock app from the market that will in turn benefit you as well..
BTW don't forget to hit the thanks button
Click to expand...
Click to collapse
now a simple question....can you tell me which options i need to use for get a best performance in ouya games and emu?
This app has a one click solution (found in the op). All you need to do is click the button and your ouya is optimized. The op already has this information.
On another note, this app rocks. Thank you.
Awesome, finally the OUYA version, im about to jump on this right now and give it a spin!!!:good:
darkknight1812 said:
This app has a one click solution (found in the op). All you need to do is click the button and your ouya is optimized. The op already has this information.
On another note, this app rocks. Thank you.
Click to expand...
Click to collapse
i asked before install...now i saw it very nice and user friendly
.. one click optimization .. nice job .. cheers
sasuke1981 said:
now a simple question....can you tell me which options i need to use for get a best performance in ouya games and emu?
Click to expand...
Click to collapse
Just Press the OK button and wait a few seconds as the settings getting applied. After that Run your Emulator Games and you should notice a difference . Note that Resolution options also cuts the screen area so use them only if a game is unplayable!
is there no way to allow users to set advanced profiles so that they can configure a medium and max overclock setting?
i saw the temps on my core rise up pretty quickly just from fiddling with the UI, not sure if I want to subject this little guy to that much abuse with no really efficient cooling solution under the hood.
Careless_ said:
is there no way to allow users to set advanced profiles so that they can configure a medium and max overclock setting?
i saw the temps on my core rise up pretty quickly just from fiddling with the UI, not sure if I want to subject this little guy to that much abuse with no really efficient cooling solution under the hood.
Click to expand...
Click to collapse
it's understandable for the lil guy to get hot quickly when you are overclocking the GPU+CPU, can't expected to run cool unless you put a better cooling fan into you console, i don't mid my ouya running a lil hot, well mines don't get hot enough cause my ouya got a acrylic custom shell with enough vents and airflow that keeps my console way cooler then the ouya stock/factory shell...
its obvious that it would run hotter if the clock speed is higher. no one is disputing that. i just don't see how not allowing the user to specify speed as much of the other CPU overclocking programs like SetCPU allow the user to do.
It's a needed feature IF it can be supported and implemented.
Excellent!
I'll give this a bash tonight and see what improvements there are!
Careless_ said:
is there no way to allow users to set advanced profiles so that they can configure a medium and max overclock setting?
i saw the temps on my core rise up pretty quickly just from fiddling with the UI, not sure if I want to subject this little guy to that much abuse with no really efficient cooling solution under the hood.
Click to expand...
Click to collapse
Actually Temperatures are no problem for this chip as it can bear temperatures of 70 C with great ease as the manufacturer mentioned. Don't worry about that also let me know if they are above this temperature so that we can do something about that. If you ask me I am comfortable with 85C as that is what the throttle temperatures (Default mind you!). Just Relax and crush the games already
Careless_ said:
its obvious that it would run hotter if the clock speed is higher. no one is disputing that. i just don't see how not allowing the user to specify speed as much of the other CPU overclocking programs like SetCPU allow the user to do.
It's a needed feature IF it can be supported and implemented.
Click to expand...
Click to collapse
The custom CPU clock feature conflict the one click feature and not to mention lower clocks are not required as there is no trouble with the highest speed since the cooling is active and with sink. Just don't worry about the temps too much as everything is normal here and the purpose of console is to bear high temperatures with high load even with little heat management..
I have both the old app and the Ouya specific one and it looks to me that 2D GPU clock is set to 260MHz (1/2 of 3D clock). @Kingshoo, can you tell us what the "one click" settings are (governor, CPU clock, GPU, etc).
Much appreciate the work you've done.
Ipse_Tase said:
I have both the old app and the Ouya specific one and it looks to me that 2D GPU clock is set to 260MHz (1/2 of 3D clock). Can you tell us what the "one click" settings are (governor, CPU clock, GPU, etc).
Much appreciate the work you've done.
Click to expand...
Click to collapse
Oh really If its working on Half then I will bump that to full to in next iteration
Settings are nothing but final settings in one click. Meaning Performance governor (Because this one has no polling overhead as opposed to interactive). GPU to 520Mhz, CPU clock to 1.7Ghz (1.6 on all 4 cores as set by OUYA). Ram at 800Mhz and also no throttling on Ram and GPU so that performance is reduced only due to H/W limitation or by bad coding practices and not due to some power saving logics
Kingshoo said:
Oh really If its working on Half then I will bump that to full to in next iteration
Settings are nothing but final settings in one click. Meaning Performance governor (Because this one has no polling overhead as opposed to interactive). GPU to 520Mhz, CPU clock to 1.7Ghz (1.6 on all 4 cores as set by OUYA). Ram at 800Mhz and also no throttling on Ram and GPU so that performance is reduced only due to H/W limitation or by bad coding practices and not due to some power saving logics
Click to expand...
Click to collapse
Cool...thanks! Looking forward to v2
BTW...for reference, I had my governor set to performance for a while and it drove the fan to run almost at all times. To the point I ended up shelling 20 bux to buy the Noctua quiet fan. Maybe others have better luck with the stock fan - but if noise is a concern, I found that the "Interactive" governor scales pretty fast with no visible impact on performance vs "Performance".
My 2 cents.
After reading several reviews about Noctua 40x10mm A-Series Blades with AAO Frame, SSO2 Bearing Premium Retail Cooling Fan NF-A4x10, I decided to buy it. I replaced the noisy fan of my OUYA, and the difference in sound is amazing. I had to check if the fan was actually running because barely hear it. Also, the temperature of my equipment dropped ~ 10°C, so overheating issues could be easily fixed, if you decided to overclock. I recommend this product without a doubt. Check on eBay or Amazon.
If you want to replace the fan, here's a guide how to do it. youtube . com /watch?v=rra0FwlHvBA
Well honestly I wasn't able to play games on OUYA but since you people are playing games what the temps of CPU are anyways after say an hour? I am asking this because I don't see a need for custom coolers as 50C or 70C it really don't make any difference to your hardware. Yes the fan noise may be concerning to many but I have cotton plugs in my ears to keep it silent (these really costs cents and not $$!). OK so newer version will have interactive on one click..
My stock fan is totally silent anyway
Sent from my ADR6350 using Tapatalk
Ipse_Tase said:
Cool...thanks! Looking forward to v2
BTW...for reference, I had my governor set to performance for a while and it drove the fan to run almost at all times. To the point I ended up shelling 20 bux to buy the Noctua quiet fan. Maybe others have better luck with the stock fan - but if noise is a concern, I found that the "Interactive" governor scales pretty fast with no visible impact on performance vs "Performance".
My 2 cents.
Click to expand...
Click to collapse
i will also try this, i run my OUYA on performance all the time and it's pretty loud...
Is it just my tf701t with cm11 that the cpu jumps straight to 1920mz a soon as I touch the screen?
There seems to be no "middle ground" for the cpu. It's sitter 1920mhz or it sits at 306mhz. When I use a different governor it still jumps to 1920mhz but downclocks slower.
Seems like a waste of battery to have max frequency non stop while reading a ebook. The tablet gets equally hot from ebook reading as gaming, or typing with the dock.
Still an awesome rom,,,, this is the only thing I can find that's not perfect
Any advice from you guys on how to save battery? Or to inhibit the cpu from so aggressively jump straight to 1920mhz? Any compatible cpu control apps that works well with cm11 on the tf701t?
Xda = best community online,,,,, loving this place
http://forum.xda-developers.com/showpost.php?p=52028152&postcount=60
I had bought a Nook HD+ to be the replacement for my aging 1st generation Kindle Fire (Otter) tablet. However after having had it for 6 months now I've been rather disappointed with it. On paper it should have been better than my OG KF in every way but in reality that has not been true.
Nook HD+
Released 2012
1.50GHz TI OMAP 4470 (ARM Cortex A9 + PowerVR SGX 544)
1 GB of memory
32 GB storage (controller without issue too)
CM11 Nightly 2014.08.02 installed to internal storage
Davlik, stock kernel, not overclocked
Kindle Fire
Released 2011
1GHz TI OMAP 4430 (ARM Cortex A9 + PowerVR SGX540)
512 MB of memory
8 GB storage
CM11 Nightly 2014.08.02 installed to internal storage
Davlik, stock kernel, not overclocked
Whenever it comes to anything relating to the screen though this old as dirt KF tablet still performs better than this much newer and on paper better device. The Nook HD+ is obviously better as most apps perform much better like browsing FB app, looking at web pages with lots of content, running any number of non-visual intensive apps.
Places the Nook HD+ bogs down.
Paging around in the home screen stutters when loading icons even if the page has already been loaded.
Closing an app and returning to the home screen is extremely sluggish and then requires reloading of each page.
The boot animation is completely embarrassing, it jitters and skips like it's been beaten to death.
Scrolling through large pages of data in Chrome jitters rather badly.
Some games with intensive video requirements are just nasty at times. Running really slow or slowing down over time.
This video shows the KF next to the Nook HD+ to show how horrible the start animation is. After loading I page left then right and you can see the home page stutter on loading the icons when I come back left.
https://www.youtube.com/watch?v=PEJK-VUZunk
This video shows loading PvZ 2 where just the loading screens alone are running slower and jitter more. Then when loaded menus take longer to load and are very jittery compared to the KF.
https://www.youtube.com/watch?v=XCG8GKIWyso
Note - I even removed the overclock from the KF for these tests.
I realize the resolution is greater on the HD+ than the KF but the Amazon KF HD 8.9" uses the same hardware as the HD+ and it doesn't have the same issues. I also recall when running the stock firmware the system was much more responsive than it is under CM11 (any version).
This really seems like a lack of a good video driver or something wrong with the memory management.
I'm looking for serious discussion on this and not "well mine works fine so it must be yours..." or suggestions of running some random ROM or running TRIM or tweaking some random setting. This is something more than basic settings as I've already tried several over the last 6 months along with fresh installs of CM.
Your hd+ looks normal. I wouldn't think about it too much as its more than likely not getting better than that.
I just bought a new phone and the hardware made android so much more snappier then it was on the last one no matter how much people had tweaked the roms.
Just how it is. Its a cheap tablet with a nice size screen and hardware not quite capable.
sandsofmyst said:
Your hd+ looks normal. I wouldn't think about it too much as its more than likely not getting better than that.
I just bought a new phone and the hardware made android so much more snappier then it was on the last one no matter how much people had tweaked the roms.
Just how it is. Its a cheap tablet with a nice size screen and hardware not quite capable.
Click to expand...
Click to collapse
I've installed CM11 for two of my friends on their HD+'s, and their is snappier than mine. All are fresh installs. There is a very noticeable difference between mine (purchased in June, 2013), and theirs (purchased in May & June 2014). I didn't write everything down, but there was very little difference in the information for each device as reported by Quadrant.
Odenknight said:
I've installed CM11 for two of my friends on their HD+'s, and their is snappier than mine. All are fresh installs. There is a very noticeable difference between mine (purchased in June, 2013), and theirs (purchased in May & June 2014). I didn't write everything down, but there was very little difference in the information for each device as reported by Quadrant.
Click to expand...
Click to collapse
You maybe experiencing lag since you have been running longer (since 2013, not just with CM11). Also you may have a different emmc chip than they do. There are hardware differences between some devices
Sent from my BN NookHD+ using XDA Premium HD app
leapinlar said:
You maybe experiencing lag since you have been running longer (since 2013, not just with CM11). Also you may have a different emmc chip than they do. There are hardware differences between some devices
Sent from my BN NookHD+ using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for the info. I'll ask them to send me the device info and I'll compare them both. Based off of what you said earlier, it may be due to too many writes to the chip? If so, I can live with that. I did abuse the heck out of it.
Thanks to you, VG, and everyone else in the community who put all of this together.
Odenknight said:
Thanks for the info. I'll ask them to send me the device info and I'll compare them both. Based off of what you said earlier, it may be due to too many writes to the chip? If so, I can live with that. I did abuse the heck out of it.
Thanks to you, VG, and everyone else in the community who put all of this together.
Click to expand...
Click to collapse
That is exactly what I meant. But if you run CM11 enough, it may speed up due to it running TRIM in the background.
Sent from my BN NookHD+ using XDA Premium HD app
Idk. Had two of these, one for three months and this one since around when you got yours. It performs as I remember and as I expect.
But since your comparing directly to another aren't ALL electronics that way? This display is more blue than that one, this hard drive has more errors that that one. This cpu can be oc'd more than that one.
There's always things causing speed differences. Background services, amount of free space - its best to have >50% free space, amount of installed apps, what leapinlar pointed out, etc.
In one month they could have no noticeable difference. Tis all I'm saying.
[You might was to switch over to using art instead of dalvic as well if not already. It may/may not help in making it feel faster as its suppoed to be the PBT™ (Performance Boosting Thing). Mine is on art. You may also want to go into the recovery and do a full backup before that.]
sandsofmyst said:
[You might was to switch over to using art instead of dalvic as well if not already. It may/may not help in making it feel faster as its suppoed to be the PBT™ (Performance Boosting Thing). Mine is on art. You may also want to go into the recovery and do a full backup before that.]
Click to expand...
Click to collapse
Pardon my ignorance, but how do you do this?
neoage said:
Pardon my ignorance, but how do you do this?
Click to expand...
Click to collapse
This post is for a phone, but it is the same for all devices (I just randomly picked a post):
http://forums.androidcentral.com/android-4-4-kitkat/404625-enabling-art-android-4-4-3-devices.html
Quote "To enable ART, Go to settings => About Phone =>Then go to Build Number and tap on Build Number until it ask if you want to enable Developer Options (or something in that effect) Once you say yes, Go back once and above About Phone you should see Developer options.
Under Developer options, go to "Select Runtime" (which should be on Dalvik) and select ART. Once you do this it will need to reboot your phone and then it will go through an update process on your Apps. Depending on how many Apps you have this can take a bit. I suggest doing when you won't need your phone for a few minutes and also make sure to plug your phone into power to help it go faster.
Once it is done, I suggest testing one or two apps to make sure they work. Then I would reboot your phone one more time. (This seems to fix a noticed app lag after the update). Once it comes back up, use your phone as normal and enjoy the free speed boost and a little added battery life. I have not noticed any issue with the 168 apps on my Nexus 5 nor any stability issue with the device, but again you millage may vary on your device and apps."
Some additional notes:
I stress doing a full recovery backup first. If you don't have enough internal space available, then that may cause it to be unusable when android starts up due to it failing while configuring art.
Phones (and other low internal storage devices) are a bit problematic due to amount of space available. My htc sensation couldn't enable art from not enough internal space. But the nook hd+ (for instance) has plenty (assuming its not all used).
Art is supposed to be enabled automatically in the next android release.
"With the L Developer Preview, ART is now the default runtime."
https://developer.android.com/preview/api-overview.html
Art requires more space due the fact that apps are pre-compiled during install:
"ART, on the other hand, uses an Ahead-of-Time compiler (AOT) to process application instructions before they're needed so things run more smoothly for the user."
http://lifehacker.com/android-art-vs-dalvik-runtimes-effect-on-battery-life-1507264545
You'll possibly lose about half a GB or more. It just depends on how many apps including the apps included with the rom.
The reason why the hd+ has poorer performance is probably due to it dragging a 1920x1080 (2073600 pixels) screen while the Fire has a 1024x600 screen (614400 pixels). Processing a full 1080p screen vs a 600 makes a big difference. The 544 isn't much of an upgrade over the 540 to make up for it. While it doubles the frame rate in graphics by about 2x over the 540, its having to push more than 3x the pixels.
Apple had the same issue with the ipad 3 when they went to the retina screen. It was a bit of a dog on pushing the retina screen, hence the quick rollout of the ipad 4 with a much faster cpu and gpu.
Lastly, amazon has a lot of pretty good paid developers optimizing the heck out of the Fire. I doubt its running a stock google display/graphics driver.
One of the things with high density displays. They're pretty and nice for text but you need plenty of horsepower to run them.
I signed up for alerts but doesn't seem like I was getting them.
I was comparing it to the OG Kindle Fire because it was the first real Android tablet and it's old as dirt now. Also as mentioned in the other performance vs stock thread when running the default Nook HD+ OS the interface is a lot more responsive and games perform better too. It seems like there's something missing between those kernel's/drivers and the CM version.
Of note these commits might help us with some of our issues. It looks like they're enabling a 128 MB swap partition for this device.
http://review.cyanogenmod.org/#/c/68840/