Hope the voltage control part of the app is not too hard to use. I didn't really like using the context menu to apply the settings and such.
You have to hit "apply" in order for the settings to be pushed to the kernel. This will also save them in a database. Then you can select "set on boot" to have those settings from the database applied on every boot.
Thanks didn't push the menu button and see the apply button. It's similar to other voltage control apps I use on my android phones. I usually mess with the voltages until I get them where I like them then set on boot.
I do have a request. Is it possible to add a wipe voltage setting in CWM? I know on my captivate some kernel devs have it and it makes it nice if you have bootloops or crashes.
For OC settings should I set on boot in your app, settings menu or both?
No this is not possible or at least not as easily done in CWM because I am not applying the voltages in early boot.
Since the voltages are not applied until boot up is completely finished there is a fairly easy workaround if you mess up your voltage settings. Worst case scenario you can just run "adb uninstall com.dalingrin.nookcolortweaks" while the CM7 boot animation is going.
Thanks that seems easy enough.
One last question. Should set on boot be performed from your app, the menu settings or both?
I was getting good deep sleep with wifi on in sleep mode, but given it's still doing "something" it was only sleeping about 70% of the time and was using around 1.5%/hr.
I've recently been having the wifi turn off at screen off and I get 100% (or more.... ) deep sleep and my drop is maybe 1% every 3-4 hours. I can go 2 days with reasonable amounts of use, 3 days with light usage this way without charging.
I'm going to leave it like this, at first I thought it'd be annoying having to wait on wifi but it really only takes about 10s. The biggest annoyance really is that it's a bit slow at first because everything is updating at once, which tends to peg the CPU.
Both, because they change different things. I know its confusing and its made me think about adding the functionality to Nook Color Tweaks but then the two could potentially conflict with each other adding even more confusion.
Think of CM7 performance settings as being able to choose the maximum stepping and the minimum stepping, not particular clock rates.
By default the Nook has 3 steppings(300mhz, 600mhz, 800mhz). In Nook Color Tweaks you can change those frequencies but you can't make it go to the 4th or 5th stepping. In other words, if you only used Nook Color Tweaks only stepping 1, stepping 2, and stepping 3 would be used.
When you increase the maximum frequency in CM7 performance settings or SetCPU, you are in essence telling the kernel to to use the 4th and/or 5th CPU stepping.
Here's how I use the two:
First thing I do is change CM7 performance settings to a max of 1200mhz. Then I choose set on boot. This makes it so the Nook will use all 5 steppings. From this point you should never need to look at CM7 performance settings again.
Now in Nook Color Tweaks you can change the clock rate for each of those 5 steppings. Once you changed that how you want it and verified its stable, you can set on boot for Nook Color Tweaks.
Note you do not need to go back to CM7 performance settings. Nook Color Tweaks changes will take affect immediately.
thanks for new kernel, 061811 OC kernel problem-free nearly 2 weeks, time to move on.
trying to undervolt cm7 on 063011 but think my nook not cooperating. at stock voltage my sr_adjust_vsel (pastebin here) somewhat resembles what searius posted few days ago, with opp1 - 3 already undervolted although not as generously as searius. if i use Nook Tweaks to reduce opp1 - 3 by 100mV each i think my nook just adjusts the voltage right back to nearly where it was, if i'm reading the sr_adjust_vsel numbers correctly (pastebin here), regardless of any concurrent underclocking.
other than that it's probably going to be problem free with 063011 kernel, like it's been for a long time now.
So what are the advantages / disadvantages to playing around with the voltage? How does it effect overclocking? Just want to understand what I'm doing before I play around too much.
Sent from my NookColor using XDA Premium App
By increasing voltage, you can potentially achieve higher overclocks, but risk damaging your hardware. By lowering voltage, you can potentially achieve better battery life without sacrificing performance, but risk instability.
I've only been playing around with undervolting for a little bit, but so far it looks like on mine, the limit for stepping 5 at 1.2ghz is 1.25v (default is 1.375). Setting it to anything lower causes the entire tablet to lock up the instant I hit apply. For stability testing I've been letting an N64 emulator run for a few minutes since it stresses the device enough to go to the highest stepping, going down in voltage a bit and repeating.
Edit: Spoke too soon. 1.25v isnt stable at that speed.
I've currently got mine at
1 (300mhz) - 0.8125v
2 (600mhz) - 1.0v
3 (800mhz) - 1.1875v
4 (1100mhz) - 1.25v
5 (1200mhz) - 1.3v
Could probably do a little better than that, I know 5 can run at 1.25 for a bit but then it starts randomly shutting off on mine. Still, its pretty good, hope its stable in actual day-to-day use. Looking forward to seeing what this does to my battery life.
I've currently got mine at
1 (300mhz) - 0.8125v
2 (600mhz) - 1.0v
3 (800mhz) - 1.1875v
4 (1100mhz) - 1.25v
5 (1200mhz) - 1.3v
Could probably do a little better than that, I know 5 can run at 1.25 for a bit but then it starts randomly shutting off on mine. Still, its pretty good, hope its stable in actual day-to-day use. Looking forward to seeing what this does to my battery life.
0c1a3f88da68f17a187e7d6535e3ecef ./090111/update-Froyo1.2-dalingrin-OC-sd-090111.zip
5673c886a08577d963be7722528a6865 ./090111/update-Froyo1.2-dalingrin-OC-emmc-090111.zip
a526a38d41a5b7a069ed5e12b8799815 ./063011/update-Froyo1.2-dalingrin-OC-sd-063011.zip
a8ba40ac44241543be52854c048b3a72 ./063011/update-Froyo1.2-dalingrin-OC-emmc-063011.zip
94ff341d338ddcd432afa313f03edaa3 ./063011/update-CM7-dalingrin-OC-sd-063011.zip
aacfb728b2a650ca5194d4ece097f22e ./063011/update-CM7-dalingrin-OC-emmc-063011.zip
130fe72bbffa0a660475c1d360de1548 ./061811/update-Froyo1.2-dalingrin-OC-emmc-061811.zip
bfc4e9e3f70d45324201bd6a14a44bc0 ./061811/update-CM7-dalingrin-OC-sd-061811.zip
7156b00dffc5a636cd6d7a53e00abe2c ./061811/update-CM7-dalingrin-OC-emmc-061811.zip
ca101e3b9a2874e3521c89453352b0ed ./061311/update-Froyo1.2-dalingrin-OC-sd-061311.zip
d17e29cc5a3a758b8a445e4d554e9538 ./061311/update-Froyo1.2-dalingrin-OC-emmc-061311.zip
1ba2195b53a15d31ef9cd23e9fc5342a ./061311/update-CM7-dalingrin-OC-sd-061311.zip
0048009800107dc596a3c06d8df33aff ./061311/update-CM7-dalingrin-OC-emmc-061311.zip
adb0afe1d5999ee30e773bf112aa6d76 ./060911/update-Froyo1.2-dalingrin-OC-sd-060911.zip
7d1c53b29f0513543b515e0c37e4c8cb ./060911/update-Froyo1.2-dalingrin-OC-emmc-060911.zip
a770009f2807e04f6761bb315309a9a4 ./060911/update-CM7-dalingrin-OC-sd-060911.zip
fd6634c0a904d8fc92b9e38583cde5ad ./060911/update-CM7-dalingrin-OC-emmc-060911.zip
52b593ddabf70cc84b24c479cdb871f1 ./052311/update-Froyo1.2-dalingrin-OC-sd-052311.zip
43e498da25b62ec0516471ecfb600eb7 ./052311/update-Froyo1.2-dalingrin-OC-emmc-052311.zip
5732fa2ef134d351ec98635e4beb8128 ./052311/update-CM7-dalingrin-OC-sd-052311.zip
d6dac86b336e4ca0f9f8daffba9237ea ./052311/update-CM7-dalingrin-OC-emmc-052311.zip
a02ebb0350533af211089cde95fb5105 ./051311/update-Froyo1.2-dalingrin-2.6.32-emmc-051311.zip
1177d17548c65f89962720ba3bbffaa4 ./051311/update-cm7-dalingrin-2.6.32-sdcard-051311.zip
bfa163bc7ad0e1208997af1dbfb9e33b ./051311/update-cm7-dalingrin-2.6.32-emmc-051311.zip
053ad16383b7b2abc859f622927c965e ./042411/update-CM7-dalingrin-OC-sd-042411.zip.md5
9d0f3fe6d4781a0a2e7b494523c1db72 ./042411/update-CM7-dalingrin-OC-sd-042411.zip
7652d13fc5f3d819b986fda7e6d3ee3f ./042411/update-CM7-dalingrin-OC-emmc-042411.zip.md5
1569ba396bdac3404f997d7e05faa247 ./042411/update-CM7-dalingrin-OC-emmc-042411.zip
6a7519ba0ae3a7b4f34e38fdb7fa0d0c ./042311/update-CM7-dalingrin-OC-sd-042311.zip
f62579042d610f4fbf739d41f7aebc48 ./042311/update-CM7-dalingrin-OC-sd-042311B.zip
a241e36f4c6c663190eb4a13b1cc73c4 ./042311/update-CM7-dalingrin-OC-sd-042311A.zip
19bd148a4a180c1bf6b88559ffc0f9f5 ./042311/update-CM7-dalingrin-OC-emmc-042311.zip
745960368e2ada7d48db13b37a997d4c ./042311/update-CM7-dalingrin-OC-emmc-042311B.zip
4fd0718b4418ccdf56f230df147e7b41 ./042311/update-CM7-dalingrin-OC-emmc-042311A.zip
b16f61d937e39f6b1fe35463d576a671 ./041911/update-froyo-dalingrin-OC-sd-041911.zip
3b44f1972c947da700a835d29c654f34 ./041911/update-froyo-dalingrin-OC-emmc-041911.zip
a335f912d3cb3faffb4366e20fda7654 ./041811/update-CM7-dalingrin-OC-sd-041811C.zip
41817da1d160733d5ce198cb0139db46 ./041811/update-CM7-dalingrin-OC-sd-041811B.zip
7b91add1ce7bdd2a6722071aec8098eb ./041811/update-CM7-dalingrin-OC-emmc-041811.zip
e77dedc60d8f0af588820af533d6004c ./041811/update-CM7-dalingrin-OC-emmc-041811B.zip
0846c996bad671a07c095a783506a139 ./041311/update-CM7-dalingrin-OC-sd-041311.zip
34a13469b79700c1ae7bcc0ab056abdc ./041311/update-CM7-dalingrin-OC-emmc-041311.zip
25610f0b29c944762b642aec495d4193 ./041211/update-froyo-dalingrin-OC-sd-041211.zip
b3efe8ac1a514e43157eb32cbefce791 ./041211/update-froyo-dalingrin-OC-emmc-041211.zip
bac72586c1fa1a4c374f3cc5ad0c1cbf ./041211/update-CM7-dalingrin-OC-sd-041211.zip
44e2984a61eca20cbde595da7e66f9f5 ./041211/update-CM7-dalingrin-OC-emmc-041211.zip
b8e5425a7288a5b43e39c5f455eeb0d7 ./041111/update-CM7-dalingrin-OC-sd-041111.zip
7181812d69ecdc80f32fc0b3f5c1181f ./041111/update-CM7-dalingrin-OC-emmc-041111.zip
def332f172d6db5822c436900d36b65a ./040511/update-CM7-dalingrin-OC-sd-040511.zip
385234a8e7f7da3212171d37eab1d95e ./040511/update-CM7-dalingrin-OC-emmc-040511.zip
bae26ee57c51ac48d687a7a3f4d1efb9 ./040411/update-froyo-dalingrin-OC-sd-040411.zip
8f99790621b3bc0fef4a7d5f3319c009 ./040411/update-froyo-dalingrin-OC-emmc-040411.zip
200be792e966453e21bbec0d6b10a288 ./040411/update-eclair-dalingrin-OC-sd-040411.zip
872dbe19f539cec5e9e58e6b36aede35 ./040411/update-eclair-dalingrin-OC-emmc-040411.zip
53e66c6328a72ed500c6d47bd9c48ea6 ./040411/update-CM7-dalingrin-OC-sd-040411.zip
abe51daa708ecdafb74d286dd21ad2d8 ./040411/update-CM7-dalingrin-OC-emmc-040411.zip
684c0a009c4503e7ad8111e4d2889d93 ./033111/update-froyo-dalingrin-OC-sd-033111.zip
e75019d04668208cbe81e5aa8daf5ed5 ./033111/update-froyo-dalingrin-OC-emmc-033111.zip
61c35771ff5ef267ca47fbae36d901df ./033111/update-eclair-dalingrin-OC-sd-033111.zip
a3da36043ea8efac3b35c5f82aa24d3d ./033111/update-eclair-dalingrin-OC-emmc-033111.zip
34bd1736b35f400a936b5adfdd5d061c ./033111/update-CM7-dalingrin-OC-sd-033111.zip
2bccf595bbec4010724ede6365a4644d ./033111/update-CM7-dalingrin-OC-emmc-033111.zip
fba87ec0d18411e72b5718fde1607e9e ./032811/update-froyo-dalingrin-OC-sd-032811.zip
6601902dbc03ea67ee97eda1a59c9fcd ./032811/update-froyo-dalingrin-OC-emmc-032811.zip
f133b2c452382f04f8b50dfb790527c7 ./032811/update-eclair-dalingrin-OC-sd-032811.zip
692330cc8b13ce1b041e2a87c633168e ./032811/update-eclair-dalingrin-OC-emmc-032811.zip
6bacc09cf04e7edf78eefcc6fb728838 ./032811/update-CM7-dalingrin-OC-sd-032811.zip
4c9102c3f2a6f253c81c777029ba7980 ./032811/update-CM7-dalingrin-OC-emmc-032811.zip
13c03150b72938fa15f43bd795969dfe ./031611/update-CM7-dalingrin-OC-sd-031611.zip
b481b9f729e465e258e4fdb85dc1700d ./031611/update-CM7-dalingrin-OC-emmc-031611.zip
4ddd47b2633b86004f970faa53aba671 ./031311/update-CM7-dalingrin-OC-sd-031311.zip
c534673e003946a6ed108f60bb075d55 ./031311/update-CM7-dalingrin-OC-emmc-031311.zip
e54bdeefac03912e4948b753ce73276b ./031111/update-CM7-dalingrin-OC-sd-031111.zip
67857a797ecb8219ad4ff3b5e5581d88 ./031111/update-CM7-dalingrin-OC-emmc-031111.zip
cbf70b6556ccc58690257026c224a56b ./031011/update-froyo-dalingrin-OC-sd-031011.zip
cfb083c3ec0816b893d43cade27e3b4e ./031011/update-froyo-dalingrin-OC-emmc-031011.zip
90aaab882957111328503573f9ffd16c ./030811A/update-froyo-dalingrin-OC-sd-030811A.zip
55c282c3928abadd0486bc04cbfd2e74 ./030811A/update-froyo-dalingrin-OC-emmc-030811A.zip
71df4553e3986719750dde72d3da5e96 ./030811A/update-CM7-dalingrin-OC-sd-030811A.zip
91637380e3ec853c8506e50e72be07ff ./030811A/update-CM7-dalingrin-OC-emmc-030811A.zip
25ba50b8865315b44fc8b98d382b5447 ./022511/update-HC-dalingrin-OC-sd-022511.zip
f08c443ed730b147e57ac224fdd521eb ./022511/update-HC-dalingrin-OC-emmc-022511.zip
3243664a945b82fde9895bdfd59db701 ./022511/update-Froyo_CM7-dalingrin-OC-sd-022511.zip
0bf22eface5c313c783b627d7a85d475 ./022511/update-Froyo_CM7-dalingrin-OC-emmc-022511.zip
6efa7c62b5edf1d313996c13bed3d224 ./022511/update-eclair-dalingrin-OC-sd-022511.zip
b2dfb032aae911e81708df8f39a22381 ./022511/update-eclair-dalingrin-OC-emmc-022511.zip
if flashing to sdcard:
adb shell mount -t vfat /dev/block/mmcblk1p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
if flashing internal eMMC
adb shell mount -t vfat /dev/block/mmcblk0p1 /emmc
adb push uImage /emmc/uImage
adb remount
adb push system /system
Reboot Nook!
well, its been about 3hrs since I log out of latitude and Im happy to report that my nook has been deep sleeping all this time. according to cpu spy, deep sleep 95% and the 5% was shared between 300 and 600
I think this is the trick to long deep sleep. Im going to turn on live wallpaper and see what happens. its going to be interesting to see how it goes over night. so far so good.
I honestly don't know what else can be done to improve Bluetooth. As of now we've backported 2.6.35+ bluetooth drivers and software to use on the Nook. Most of the important parts are controlled by a closed source proprietary firmware. Not much I do there.
For those that use Bluetooth and are comfortable with Android and Linux, you could try different bluetooth firmware/script. This is a .bts file.
There are several versions of TI's bluetooth initialization script, called the "bts" script. You can get them here:
https://gforge.ti.com/gf/project/wilink_drivers/
The .bts files (such as TIInit_7.2.31.bts) may be placed in:
/system/etc/firmware
and will automatically be loaded when needed. Try different versions and experiment to see if some work better others. (Watch the log and dmesg to verify that the bts script is running properly)
-Merge OMAP SoC optimizations into the CM7 framework(this helps us and lays the foundation for OMAP4 support in CM7)