Update-BN1.2-U-boot.bin
(this install will backup your original u-boot.bin to u-boot.bin.stock)
All credit goes to HTCF4N for this link.[/QUOTE]
Is this a flashable file?
Update-BN1.2-U-boot.bin
(this install will backup your original u-boot.bin to u-boot.bin.stock)
Sorry for all the confusion, I put up the "update-CM7-dalingrin-OC-sd-042411 ext4.zip" as a dropbox link (fixed the ext # and renamed) for someone who was having problems fixing the ext"4" portion of the script. It apparently has made its way around to a few who didn't understand it was for the SD version not eMMC. So, until Dal puts out the new .32 kernel, here is the links for both:
SD ext4 4/24 OC : http://db.tt/3CnQxjo
eMMC ext4 4/24 OC : http://db.tt/sMdWUs1
Update-BN1.2-U-boot.bin
(this install will backup your original u-boot.bin to u-boot.bin.stock)
So can the SD zip now be just placed in the boot section and use the power/n method to install?
Ok, I installed the above boot update, then the .32 kernel. Now boot loop, I had N#70 running before. What is this beta 3.1+ Dal is talking about?
So if I'm on phiremod 6.2 (based on CM7.02) all I need to do is flash the bin, then flash the kernel?
I give questions only if there is a reason. Its not wrong if you only ask someone and most importantly I havent seen a mention about 1.3 kernel so why not ask.
Greetings Dal, is it possible to make .32 kernel same as was your last .29 ( 1.3ghz, graphic performance improvements ) ?
-Smartass CPU governor. Very similar to the Interactive governor found in my 2.6.29 kernel but with a built in SetCPU profile-like functionality. CPU clock speed is limited to 3-600mhz when the screen is off.
can you post the referenced file? I'm curious to adjust those settings, netflix sound comes across pretty low so this could be helpful.
Thanks!
I really love my Nook Color.
I currently am running it with Nookie Froyo installed to the eMMC by following the directions found here.
Its fantastic and so far I found nothing that it can't do. It runs flawlessly.
My only gripe was the sound.
There are two issues as you probably know.
1) Low volume
2) The built in speaker is mono and only outputs one channel (left I believe)
So after trying a few things, I finally found a way to downmix stereo to mono and boost the volume a bunch. Now music is fantastic, louder and I hear both left and right channels as well!
The solution was in ALSA's asound.conf. It took me a little to figure out the best method and here is what I did.
FYI: I also have just a volume boosted version that does not downmix explained later as well.
First off, if you decide to do this, I take no responsibility for any possible damage to your Nook Color's internal speaker.
OK, that's out of the way, so here we go...
To do this you will need a working ADB setup or Root Explorer and a text editor.
I used ADB, so I will explain how to do this via that method.
You will of course need to be rooted.
I only tested this on my Nookie Froyo, but I see no reason why this won't work on any rooted setup since it is an ALSA tweak.
First off, fire up your favorite text editor and create a new asound.conf containing:
########################################
ctl.AndroidOut {
type hw
card 0
}
ctl.AndroidIn {
type hw
card 0
}
pcm.nook{
type hw
card 0
device 0
}
pcm.!default {
type route
slave.pcm nook
slave.channels 2
ttable.0.0 20
ttable.0.1 20
ttable.1.0 20
ttable.1.1 20
}
########################################
Now save it as C:\asound.conf (or whereever you want).
Make sure your text editor doesn't save it as asound.conf.txt. If it does you will need to remove the txt part before or after moving it to your Nook.
Next, backup your original asound.conf file (just in case)
########################################
adb shell
mount -o remount,rw /system
cp /system/etc/asound.conf /system/etc/asound.conf.original
mount -o remount,ro /system
exit
########################################
Now copy your new asound.conf file over to your Nook Color
########################################
adb mount -o remount,rw /system
adb push c:\asound.conf /system/etc/asound.conf
adb shell mount -o remount,ro /system
########################################
I would also suggest copying it over to your Nook as a second copy as this:
########################################
adb shell mount -o remount,rw /system
adb push c:\asound.conf /system/etc/asound.conf.downmixed
adb shell mount -o remount,ro /system
########################################
This is useful for switching back and forth as needed. i.e., if you are going to be running your Nook using headphones or to a receiver or speaker system and want to have true left and right stereo.
You now should have three asound.conf files as so:
asound.conf
asound.conf.original
asound.conf.downmixed
You can easily rename the files when needed.
YOU MUST REBOOT after you change the asound.conf file in order to have the changes take effect! I haven't found a way to restart ALSA on the Nook short of the reboot. If anyone knows how to restart alsa on the Nook, please let me know.
Ok, you can also mix it up a little and modify the stock asound.conf to boost the volume and keep the left and right mappings.
To do that, create a new asound.conf file containing:
########################################
ctl.AndroidOut {
type hw
card 0
}
ctl.AndroidIn {
type hw
card 0
}
pcm.nook{
type hw
card 0
device 0
}
pcm.!default {
type route
slave.pcm nook
slave.channels 2
ttable.0.0 20
ttable.1.1 20
}
########################################
I would save this file as asound.conf.boostedstereo or something easily identifiable.
Copy it over to the Nook as earlier done for the other files, but I would keep it named like that:
########################################
adb push c:\asound.conf.boostedstreo /system/etc/asound.conf.boostedstreo
########################################
Now to spice it up, you can use something like gscript to help you write a shell script to change the running asound files back and forth like so...
This one will move the downmixed one to be used:
########################################
mount -o remount,rw /system
cp /system/etc/asound.conf /system/etc/asound.conf.backup
cp /system/etc/asound.conf.downmixed /system/etc/asound.conf
mount -o remount,ro /system
reboot
########################################
This one will move the boosted stereo one to be used:
########################################
mount -o remount,rw /system
cp /system/etc/asound.conf /system/etc/asound.conf.backup
cp /system/etc/asound.conf.boostedstereo /system/etc/asound.conf
mount -o remount,ro /system
reboot
########################################
You get the idea.
You can also do this in the terminal or via adb.
I use both depending on what is going on since I seem to be batting 20% or so using gscript for some reason. It only works once in a while and I am at a loss. I will delve into it deeper later.
For me, for now, I don't use the headphone jack. The new downmixed stereo to mono plus the increaed volume now allows me to hear Pandora or my MP3s in the shower without my battery powered speakers. One less battery consuming device and less wires!! YAY!
The jack will come into play when I move this into the car as a replacement for my UMPC carputer once reliable bluetooth arrives so I can hook up to my car's ECU which is the final missing piece of the puzzle.
Anyway, if anyone knows why gscript might be crapping out on my shell script, let me know.
If you try this, let me know if you have any issues.
NOTE:
For some strange reason the ttable mapping isn't working as expected.
If you use the standard ttable.0.0 1 where 1 (I believe) should state full volume, or 100%, it doesn't work like that.
If you change the value from 20 as I have used, you can tweak the volume higher or lower.
I found 20 is the best for my MP3 files I tested since it had no distortion on some of my louder tracks. 30 definitely had distortion, but you might be able to tweak it up a tad more over 20.
FWIW, 20 is great for Slipknot and everything else is just fine.
You can also download the two asound.conf files if you prefer.
You will need to rename according to your needs.
RIGHT CLICK and SAVE AS or your browser's equivalent.
asound.conf.downmixed
asound.conf.boostedvolume
When questions about a new build arise, where should you look?
The OP.
I don't know if people are just getting more selective in what they read or what, but this is ridiculous. IT'S ALL IN THE OP.
I'm on Beta 3.1 with the new OC Kernal installed. The Fastest Quadrant score that I have seen with the new Smartass governor is 1696. The best that I have seen with Performance is 2255. Both were run at 300/1200 Mhz Min/Max. Nook has been stable so far. Is the Smartass governor supposed to act like this? What is the advantage of the Smartass governor?
I don't know if people are just getting more selective in what they read or what, but this is ridiculous. IT'S ALL IN THE OP.
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)