[DEV] [ROM] CM9 for Nook Tablet Alpha 0.06

Search This thread

C64assembly

Senior Member
Feb 6, 2012
190
82
All my roms are now without expiry. So go ahead and run what ever rom you find working for your purpose (0.05.3 should never expire).

I will most probably not release any CM9 based roms anymore.

Rgds,
Chris

And press thanks! :)
And please help with the 3.0 kernel and CM10....

Thank you Chris for all your hard work! I know Cm9 is now a lame duck but would you pretty please make one more build with a working hardware Omap? Would it be very difficult to incorporate video accel into the cm9 ROM other than adding a repo or two in the build environment? Thank you Chris and kuzma, Bawks, Nemith, oh and me for my small contributions (files for mic fix cm10, flashable zip form9 boot animation.
 

funvn

Member
Apr 20, 2012
41
5
WTF????
with cm9 0.05.3, i can't hear music when the screen turnoff nomally. it's allways has stranger sound with the music. and sometimes my nook auto restart. now,i must turnon the screen when i hear music, it's not good for battery. what must i do to fix this error? tks you.

Sent from my NookTablet using xda app-developers app
 

little8020

Senior Member
Aug 12, 2010
126
14
Attalla, AL
with cm9 0.05.3, i can't hear music when the screen turnoff nomally. it's allways has stranger sound with the music. and sometimes my nook auto restart. now,i must turnon the screen when i hear music, it's not good for battery. what must i do to fix this error? tks you.

Sent from my NookTablet using xda app-developers app

You have to set the cpu governor to performance or similar, but that makes it run at 100% all the time which will drain the battery more than usual
 
  • Like
Reactions: funvn

Top Liked Posts

  • There are no posts matching your filters.
  • 173
    CM9 for
    Nook Tablet
    Alpha 0.06 Release
    “Don’t Try To Sell This... You’ll Regret It” Edition

    Hey all,

    So it’s time. Introducing the first alpha development preview of CyanogenMod 9 for the BN Nook Tablet, aka codename: “acclaim”. This preview for the internal “emmc” storage is intended only for developers as it is in a very early development stage and not all features of the device are fully working.

    Let’s emphasize that-- THIS IS AN ALPHA, RELEASED FOR YOU TO PLAY WITH AND GET A SENSE OF WHAT’S TO COME. AND SOME THINGS DON’T WORK. REALLY. IF YOU ARE EXPECTING ANYTHING CLOSE TO PERFECTION, WALK AWAY FROM YOUR COMPUTER, LOWER YOUR EXPECTATIONS FOR AN HOUR OR SO, THEN COME BACK. MORE EXCITING DISCLAIMERS/WARNINGS IN ALL CAPITAL LETTERS CAN BE FOUND BELOW. READ THEM.

    WHAT WORKS
    • display
    • hwcomposition
    • brightness control
    • touchscreen
    • sound
    • updated 1.8 egl driver
    • new “CyanoBoot” menu bootloader
    • accelerometer
    • data statistics
    • additional kernel tweaks/improvements/history
    • mass storage
    • MTP/PTP
    • bootcount/battery updates & other acclaim peculiarities addressed

    WHAT DOESN’T WORK
    • microphone (see below for discussion)
    • random reboots/hangs during sleep (aka SOD - sleep of death)
    • ion heap
    • hw video decoding (basically all TI ducati features are not working)


    SOME THOUGHTS AND OBSERVATIONS

    • 2.6.35 kernel. We were initially going to wait to finish the 3.x kernel before releasing the first alpha of CM9, but since wifi is taking longer than we thought, we figured we may go ahead and get everyone a glimpse as to how CM9 will work, albeit with our (modified) 2.,6.35 kernel.
    • 3.x kernel status. At present, the 3.x kernel boots. We have somewhat accelerated graphics, touchscreen works, and so does accelerometer. Video HW decoding and sound don't work, and power management is questionable. These things will need to be fixed and working before CM9 will go beta.
    • THIS IS AN EMMC ROM. IT IS INTENDED TO BE RUN FROM THE INTERNAL STORAGE AND WILL OVERWRITE/REMOVE WHATEVER YOU HAVE ON THERE, INCLUDING STOCK. It might also delete purchased BN content (even though I can’t verify that as I don’t have any purchased BN content). We try to leave the BN partitions alone, but you never know. You can go back to stock if you don’t like the rom, using an SD card prepared with fattire’s cyanoboot or other bootloaders. Before installing, make sure you master those tools.
    • Microphone. We did have it working with 2.6.35, but it was crashy and rather unstable. Rather than work on it for 2.6.35, we are focusing our efforts on getting 3.x working.
    • 1.8 egl hardware accelleration. We have updated the pvr driver to use 1.8 (from 1.7), which gives us better compatibility at the expense of some performance issues with scrolling. We do not yet have ion + ducati stuff in the 2.6.35 kernel. This will most probably work in the 3.x kernel, however. So look forward to that.
    • Source. We are releasing the source for GPL components only during this test period. We would like to avoid a situation where parasites (and you know who you are) sell these alpha versions to unwitting non-developer “civilians”. As such, this alpha will “expire” after a period at which point it will no longer work. So if you are trying this software, expect to have to update soon to a newer version. Sorry to spoil your plans, kangers. And yes, the software will stop working within a period of time that will your “customers”/victims plenty of time to reverse their credit card charges and give you a bad ebay rating. Do not sell this.
    • gapps. Not included.
    • U-Boot. Using CyanoBoot. Check the CyanBoot thread for more info.


    SUPPORT

    You get none. Zero. Zip. We obligate ourselves to providing nothing further. You are on your own and will have to help each other via this thread. This is provided “as-is”, and if you don’t like it... there is always stock and CM7.

    We basically lack time to give full dedication to this rom, and we’re looking for skilled devs who know the OMAP4 platform, Android, and/or other things that might be relevant.

    Please join us on IRC: some people are on #nook-tablet (freenode).



    BUG REPORTS

    This is the format for a bug report: “XXXXX isn’t working. Here is how to fix it: [INCLUDE SOLUTION]” Don’t have source? Too bad. You’ll have to wait then.

    If you report bugs, please don’t be disappointed if we can’t fix them immediately (or even never). It’s not because we don’t care, but because we don’t have time or don’t know how to fix it.

    NOTE: DEVELOPERS WANTED. Please contact us if you are a developer with something to contribute.


    INSTALLATION:
    1. Prepare a “bootable” clockworkmod (CWM) recovery SD. There are instructions for doing this in other threads on XDA.
    2. Download the recovery.img and the update.zip files at the end of this post to your computer from the link below.
    3. Boot into a recovery SD for acclaim and use it to install the update.zip file. Warning: It should overwrite the contents of your emmc, including the stock installation or other operating systems.
    4. From ClockworkMod. perform CWM wipe data and cache (or “restore factory settings”) to clear previous content from those partitions. Again, you will be erasing anything you had on those partitions.
    5. Remove the SD card and select the reboot option. You should now boot into CM9.
    6. To address a “wake from sleep” issue, go to Settings->Display->Sleep and increment timeout to 30 minutes. Otherwise you may experience a “Sleep of Death” type of thing, which will be addressed hopefully in the 3.x kernel.

    At this point, Fattire’s CyanoBoot bootloader can be used to flash recovery.img to the internal mmc.

    To install CWM to emmc, download the recovery.img file below and do the following:
    1. Download and install fastboot for your computer’s operating system.
    2. Boot the device and hold the “n” key to get into the cyanoboot menu
    3. From the menu, choose “Enable Fastboot”
    4. On your computer, run: fastboot flash recovery recovery.img.

    EMMC? IS THERE AN SD VERSION?

    Of course it won’t be hard to do, but don’t look for an SD bootable version from us any time soon. EMMC is our thing, dig?


    RETURNING TO STOCK (THEORETICAL-- THIS MAY NOT WORK)

    If you have installed above rom and the CWM recovery and you really hate it and want to go back to stock, you may wish to try to flash the original acclaim_update.zip from BN. You have to unzip that file and edit META-INF/com/google/android/updater-script. Drop the first two lines here:

    assert(getprop("ro.product.device") == "blaze" ||
    getprop("ro.build.product") == "blaze");


    Zip the package again. Then go to CWM, flash the zip, wipe, and reboot.

    THANKS TO...

    chrmhoffmann, nemith, fattire, Texas Instruments, BN, and so many others, especially those who helped test cyanoboot. We also want to give props to “team B”, who by working on and releasing CM7 took off some pressure for us to more diligently get things ready.

    A special shout out to Bauwks is also in order., who defeated the malevelant locked bootloader with some serious geniusness.

    Working on this has been fun so far. We hope you enjoy!

    Release 0.06.1
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.06.1-fullofbugs.zip

    Fixed in 0.06.1:
    - hwcomposition flickering
    - ramconsole
    Broken in 0.06.1:
    - random hang/reboots in sleep mode (looks like pvr issue)
    - reboot into recovery seems broken

    md5sums
    61a8e4d45ec4c9ec02e53289de1c2e01 update-cm9-acclaim-alpha0.06-fullofbugs.zip

    -------------------
    Release 0.06
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.06-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.06.img

    Fixed in 0.06:
    - backported hwcomposition, i.e. scrolling e.g. in browser is much much smoother
    [help from lge-kernel-sniper (rmcc), hashcode et al.]. Screen rarely seems
    to flicker but it's quite usable already.
    - sync with CM9

    md5sums
    0e825d2a6c22fc151aaadbb5c10e8901 recovery0.06.img
    c92ec517ae60d8c298b1eebb16d1b1ae update-cm9-acclaim-alpha0.06-fullofbugs.zip

    Release 0.05.3
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.05.3-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.05.3.img

    Fixed in 0.05.3:
    - upstream cyanogenmod sync (probably not much happening there anymore on cm9)
    - new cyanoboot

    md5sums
    0bffa87c5c2e89f4c7a351cd60c4baf3 recovery0.05.3.img
    78a6f94f54afb2c5b79938a3200eaab3 update-cm9-acclaim-alpha0.05.3-fullofbugs.zip

    ------
    Older releases (files are gone due to goo-inside crash)

    Release 0.05.2
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.05.2-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.05.2.img

    Fixed in 0.05.2:
    - upstream cyanogenmod sync

    md5sums
    4aa0fbf272868f0935f3b560a350c8e9 recovery0.05.2.img
    e3f951968d4881a8b942e360d6daf305 update-cm9-acclaim-alpha0.05.2-fullofbugs.zip

    Release 0.05.1
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.05.1-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.05.1.img

    Fixed in 0.05.1:
    - chrome and others not available in play store
    - USB mass storage mount of sdcard and emmc

    md5sums
    97635e1cbd8ec55ce419990e0ea0f2ce recovery0.05.1.img
    14fef50c86f71c659881b3217c234a33 update-cm9-acclaim-alpha0.05.1-fullofbugs.zip

    Release 0.05
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.05-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.05.img

    Fixed in 0.05:
    - 1.4.3 stock kernel source updates
    - upstream cyanogenmod sync

    md5sums
    46b8e9495adc1df9762831f4b2714836 recovery0.05.img
    891a1829c04ab44752ee57278c3eda16 update-cm9-acclaim-alpha0.05-fullofbugs.zip


    Release 0.04
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.04-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.04.img

    Fixed in 0.04:
    - orientation (basically a better splash video :))
    - upstream cyanogenmod sync

    md5sums
    26a55a84cfde30908392e96321c5a29f recovery0.04.img
    a40e415c99812b549aa29ae83c736f6a update-cm9-acclaim-alpha0.04-fullofbugs.zip


    Annotation:
    This is basically the last CM9 image with an old 2.6 kernel. Hopefully the next rom will come with the 3.0 kernel. Unfortunately, we still see stability issues etc on that kernel. We encourage all developers around to concentrate on this new kernel. Also the device tree has been open-sourced to all devs. See fattire's post in this forum. We hope that this will increase interest for devs to participate to the effort.

    Release 0.03
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.03-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.03.img

    Fixed in 0.03:
    - only upstream cyanogenmod changes (i.e. no device specific fixes unfortunately)

    md5sums
    1858675e9272823a5b71880a88dc7e3a *recovery0.03.img
    e6721f21fe729a8bdcef1a307f4dc18c *update-cm9-acclaim-alpha0.03-fullofbugs.zip

    Release 0.02
    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.02-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.02.img

    Fixed in 0.02:
    • chrome beta didn't install (updated fingerprint to nexus s 4.0.4)
    • updated to ICS 4.0.4

    md5sums:
    3f455a120ce9b34e0d8a12b4437aec4f update-cm9-acclaim-alpha0.02-fullofbugs.zip
    aaf9cccf5cd9c2f025e3d8b734ae1014 recovery.0.02.img

    Release 0.01

    The files:
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0.01-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery0.01.img

    Fixed in 0.01:
    • nandroid backups
    • power consumption (even with wifi on, cpu is not stuck at 1GHz - ondemand governor by default)
    • random reboots on large file transfers
    • reboot into recovery
    • SOD (random reboots - if screen turned off - are less frequent)
    • same kernel for 512/1024MB nooks (*)

    md5sums:
    0041ec67f51ba9d4f373f5aa609c8051 recovery0.01.img
    0b8d09077d02fffb5e4ec8820b2174cf update-cm9-acclaim-alpha0.01-fullofbugs.zip

    (*) I have not tested 512MB NT. Please PM me if you are running this successfully or not.

    Instructions:
    • Upgrading from alpha0: cwm install zip and gapps again. That's it.
    • From stock. Follow above instructions for alpha0 (don't forget to wipe).

    Thanks go to:
    • nerdyjim, Morantz and others for testing
    • arcee for helping with the "reboot into recovery"
    • Hashcode for helping with usb mass storage issue (unresolved)
    • fattire, nemith, bauwks, kuzma30 and others


    Older releases
    http://goo-inside.me/devs/chrmhoffmann/cm9/update-cm9-acclaim-alpha0-fullofbugs.zip
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery.img

    md5: 549ade7e6b4640caa2abaf3e1c77215c update-cm9-acclaim-alpha0-fullofbugs.zip
    md5: 6e844c133ec3e77e0f4f5495a4aab10d recovery.img
    (kernel source)
    (cyanoboot info)

    Good luck,
    The CM9-NT team

    NOTICE: CM9 FOR NT IS HIGHLY EXPERIMENTAL AND IS NOT INTENDED TO BE USED BY NON-DEVELOPERS AND THOSE UNWILLING TO ACCEPT FULL RESPONSIBILITY FOR ANY UNTOWARD CONSEQUENCES FROM USING THE SOFTWARE. IT HAS NOT BEEN TESTED THOROUGHLY AND YOU ARE ACTING AS A .... GUINEA PIG ALL SUCH USE IS ENTIRELY AT YOUR OWN RISK. THE USE OR ATTEMPTED USE MAY HAVE UNINTENDED CONSEQUENCES, INCLUDING BUT NOT LIMITED TO LOSS OF DATA, DAMAGE TO HARDWARE, AND/OR EXPLOSIVE DIARRHEA. DO NOT USE IF YOU ARE CONTRACTUALLY OR OTHERWISE RESTRICTED FROM LEGALLY DOING SO. PLEASE READ THE GNU PUBLIC LICENSE AND OTHER RELEVANT LICENSES FOR THE FULL DISCLAIMER AND OTHER TERMS OF USE.

    Twitter:
    @chrmhoffman @fat__tire @androidnemith
    61
    My little 3rd post area

    11hqpm1.png

    (thx to succulent for the screenshot. Chris, let's add "screenshots" to the "What's Working" section :) )

    BTW-- I want to add, if you haven't yet, go up there and give chrmhoffmann a big . He's been a major contributor to this project, and been doing virtually all the hardware testing and (non cyanoboot) source maintenance in the last few weeks.

    I believe this is his first time doing this, and I know for sure he's put MANY MANY MANY hours into this-- not only doing his own thing, but also double-duty testing stuff for me. Some of those hours are pure fun, others are ridiculously frustrating, but he's been kicking some serious ass. So please, let him know you appreciate the work!
    48
    8GB/512MB model (BNTV250A)

    Hi,

    The above links apply for a 1024MB/16GB model. If your 8GB/512MB nook tablet doesn't boot/work at all, you can try the 512MB boot and recovery images that I have uploaded.

    To install the 512MB kernel:

    1) Download and install fastboot for your computer’s operating system.
    2) Boot the device and hold the “n” key to get into the cyanoboot menu
    3) From the menu, choose “Enable Fastboot”
    5) On your computer, run: fastboot flash boot boot_512MB.img.
    4) On your computer, run: fastboot flash recovery recovery_512MB.img.

    If this doesn't help... revert to stock (see post #0).

    Grab the files from here:

    http://goo-inside.me/devs/chrmhoffmann/cm9/boot_512MB.img
    http://goo-inside.me/devs/chrmhoffmann/cm9/recovery_512MB.img

    739c20a6178976a56044e9204dc4963c boot_512MB.img
    18f3dc9f4ef8b1e9d69ffaf5daff4119 recovery_512MB.img

    Rgds,
    Chris

    I do not have a 8GB/512MB model so you are pretty much on your own...
    22
    release

    All my roms are now without expiry. So go ahead and run what ever rom you find working for your purpose (0.05.3 should never expire).

    I will most probably not release any CM9 based roms anymore.

    Rgds,
    Chris

    And press thanks! :)
    And please help with the 3.0 kernel and CM10....
    14
    I've checked the flashing_boot.img part on both 0.03 and 0.04 boot.img and they're different. Something changed and it may have affected the Cyanoboot on 8GB version.

    Anyway, here's a flashable zip for boot.img I've created with 0.03 flashing_boot.img part with 0.04 boot.img body. I don't know if it'll make 0.04 work on 8GB.