Nookie Froyo 0.6.8
is a development build of Froyo 2.2.1 for the Nook Color.
ClockworkMod flashable! - info below, please *read carefully* before flashing!
This build is near-AOSP and contains almost no extra software not deemed required for the device to function normally.
It is pre-rooted with SuperUser, busybox, SoftKeys v3.07, and ROM Manager 3.0.0.5 however.
The eventual intention will be a build that other devs and users can easily fork and create their own custom builds, themes, roms, etc.
** THIS IS A DEVELOPMENT BUILD **
Use this at your own risk! Myself, XDA, and NookDevs are *NOT RESPONSIBLE* for anything that happens directly or indirectly related to this software!
We're approaching a daily driver! Most things work now, including mp3 and video playback. Post any bugs you find here!
I'd like to thank all the nook color devs involved in getting to this state, testing, documenting, etc. We've got an amazing group of minds behind this device!
INFO
The microSD card image contains 4 partitions:
/dev/block/mmcblk1p1 : boot (fat32)
/dev/block/mmcblk1p2 : system (ext2)
/dev/block/mmcblk1p3 : data (ext3)
/dev/block/mmcblk1p4 : sdcard (fat32)
Use these partition IDs when following guides that require mounting/remounting filesystems.
What's Working:
MP3 playback
Video playback
Youtube, Pandora and other mp4 streaming apps (apps not included)
Accelerometer!
Wifi (adhoc + infrastructure!)
Graphics acceleration (LWP!)
Sound
Browser
Mostly working
Lockscreen is wrong size - REBOOT to fix
Not included / Not working
gapps ( gmail, youtube, maps, etc ) - can be installed, youtube fixed!
Bluetooth
FM radio
This build was created using the B&N kernel sources for 1.0.0, Omappedia's Froyo source ( currently RLS27.9.0.RC0 ), and binary drivers from TI for wireless, SGX530 acceleration, and DSP codecs.
Download:
This SD image requires a 2GB microSD card! Bigger is OK, smaller is not ok!
Note: if you wish to use a larger microSD card, you can use a partition editor to increase the size of the /sdcard partition (partition 4, fat32) *after* writing the image to your card.
Simply unzip this image and dd the file to your (empty) SD card, just like nooter.
nookie-froyo-SDIMAGE_2GB-0.5.1.gz 76459ec18fd32885257a3c8b7dbb2b76
nookie-froyo-SDIMAGE_2GB-0.5.6.img.gz 74e5310bcc21edf326bdc73a5652c124
nookie-froyo-SDIMAGE_2GB-0.5.8.img.gz 15158e735517c209a8f2ed14683a589c
nookie-froyo-SDIMAGE_2GB-0.5.9.img.gz 7d30f56eeede98ee1e99a0766f69dea3
nookie-froyo-SDIMAGE_2GB-0.6.6.img.gz fc58aa06fcfe1f46939ab72e38292abe
nookie-froyo-SDIMAGE_2GB-0.6.7.img.gz 92ef91dbac7a7baad3999256597b7920
nookie-froyo-SDIMAGE_2GB-0.6.8.img.gz
MD5: 18e7cc8393681ec590f698b7a671e859
If you want to customize your SD card, upgrade an already burned Nookie Froyo SD, live on the edge and burn it into your eMMC, or just want to poke around, download the base filesystem:
nookie-froyo-base-0.5.1.tar.gz 3e95a33e3926bc88011e66a724dccf8f
nookie-froyo-base-0.5.6.tar.gz 4419b21dd8eb56f6a6537345aa1c8ba1
nookie-froyo-base-0.5.8.tar.gz 2c279dbdaa6aad480590d55e48abf8ca
nookie-froyo-base-0.5.9.tar.gz 093a964685f0cbea2ef1aa8f6f0d7581
nookie-froyo-base-0.6.6.tar.gz 2304e337c351c667f27eb9aa4c3791b8
nookie-froyo-base-0.6.7.tar.gz 99b6a9d991951c368cf1f6b3429be958
nookie-froyo-base-0.6.8.tar.gz
MD5 c3c7aea7cdf8a3dde32acc1694f633aa
This archive also contains an uncompressed ramdisk image which you can easily edit, package, and copy to your boot partition.
ClockworkMod Flashable ZIP!
*IMPORTANT*
- please wipe data/factory reset if you're coming from B&N stock firmware or another rom!!
- please see other threads about installing and using CWM recovery - keep this thread to NF issues please
- this has been tested only using CWM 3.0.0.5 downloaded from market, be warned it may not work with IOMonster's kit or other versions. Let us know if you try and it does!
- replaces kernel and ramdisk - if you were using an alternate kernel you'll need to reflash it.
- This will irrevocably erase and replace the software on your eMMC! MAKE BACKUPS BEFORE FLASHING, you have been warned.
If you're upgrading from an older version of Nookie Froyo, you should not have to wipe - however if you do have problems *wipe data* and try again.
*IMPORTANT* - this zip does not require any extra steps such as formatting /boot, changing system permissions, and does not replace or remove CWM. If you are coming from a ROM that required these extra steps and are having issues, *please post your questions there* so the dev can be prompted to correct those issues properly.
If you're coming from a rom that doesn't support CWM properly see the following thread:
http://forum.xda-developers.com/showthread.php?p=11437545
Installing /system will take some time, and the progress bar doesn't update in realtime; you haven't 'locked up', just be patient as it may take a few minutes.
nookie-froyo-flashable-0.6.6.zip 6f61a464483ecf45d6e6e2d199b44d6c
nookie-froyo-flashable-0.6.7.zip 9bd13877addbad725a5bfe1eb13412df
nookie-froyo-flashable-0.6.8.zip
MD5: 03544d6a5a52eebdb468c89a5a2581e9
Please do not PM me for help, that's what this forum and the IRC rooms are for - I simply do not have the time to answer all of your questions, and asking them in a public forum will allow others with the same issue to help or learn from your experience!
CHANGELOG
v 0.5.6
permissions corrected on /system/bin/input for SoftKeys
corrected default cpu governor to conservative
added SuperUser
added busybox 1.17.2
added SoftKeys 3.00 ( thanks bpk! )
AdHoc WIFI support enabled
crypto/cryptofs added in kernel for ASEC support (required for installing some apks such as Angry Birds)
v 0.5.8
uses the /cache partition on eMMC instead of combining with data
replaces u-boot.bin to remove the 'touch the future..' splash (trademark)
increased refresh rate to improve responsiveness and reduce flicker (see tips in the next post)
added sensors lib - accelerometer works!
v 0.5.9
default web browser FC fix - no longer dies on location requests!
v 0.6.6
Youtube, Pandora, and other streaming media should now work.
added codecs for more media formats - including hw accelerated mp3 and video
vold reverted - no more broken SD card message
flashable zip!
updated SoftKeys to 3.07
fixed a /cache issue which sometimes prevented market downloads
v 0.6.7
SD card mount fixed - please post if you continue to have issues
Added back Mms, Phone, Camera, Telephony apks to resolve missing apps in Market - more apps should be available
Modified CWM zip reliability
v 0.6.8
Corrected improper handling of Format SD Card option - no longer formats /boot!
Touchscreen enhancements - no need to toggle screen on boot and better responsiveness around the edges - thanks deeper-blue!
Please see the updated issues/workarounds list in the following post
For more information, sources, and install instructions, please see:
http://nookdevs.com/NookColor:_Nookie_Froyo
Need help? Want to contribute? Join us in IRC! irc.freenode.net
#nookcolor - general chat, questions, ask for help here
#nookie - development
Do not try to Format SD card from Settings -> SD & Phone storage!
- there is currently a bug that causes the system to format the /boot partition instead of /sdcard when this option is used, leaving your NC unbootable. Format your SD card in your PC or another device if you need to! - fixed in 0.6.8!
FIRST BOOT TIPS -
On first boot, Launcher and SoftKeys will fight for control of the home intent - that is, when you boot the first time, your NC will ask you to pick your home activity.
*CHOOSE LAUNCHER* at first (DO NOT select 'always use this action'), and let the system boot and stabilize (3-4 minutes).
Hit Home (the N button). You'll be asked to choose your activity again, this time choose SoftKeys.
Try using one of the SU-required buttons (back or menu), and after a few moments SuperUser will prompt you to accept the action.
SoftKeys 3.06+ now prompt for SU permission at startup, just accept the superuser prompt when it pops, you'll still want to let the system stabilize for a minute or two.
If SoftKeys fails to ask for SU permissions, "Unable to execute as root":
Go to Settings -> Applications -> Manage Applications -> 'All'
Select SoftKeys from the list
'Force close' Softkeys if it's running, then 'Clear defaults'
Hit the N button, choose SoftKeys when prompted to choose your home action, accept the SU prompt when it pops.
Workarounds for some known bugs/issues:
(default in 0.5.8+) Improved Refresh-rate (no flicker! thanks [mbm]!): this should set the refresh rate to 68hz, the supposed default for the Nook Color's LCD panel -
Code:
adb shell echo 68000,1024/70/200/40,600/10/11/10 > /sys/devices/omapdss/display0/timings
Browser: force closes when opening a website that tries to use location services, due to the missing GPS. Try browsing to a url by typing in the google search box, and if you can get into the browser menu changing your homepage away from google will stop it from FC'ing on open.
Lockscreen wrong size: Simply reboot to correct this.
Touchscreen is slow/unresponsive:
Turn your screen off and then back on.
Disable Haptic Feedback in Settings -> Sounds.
Also, see this page for a possible calibration fix: http://nookdevs.com/Recalibrate_the_NookColor_touch_screen
(fixed in 0.5.6 w/included SoftKeys 3.00) No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
(fixed in 0.5.6) SoftKeys - in 0.5.1 softkeys' buttons do not work due to a permissions issue. To fix, do:
Code:
adb shell mount -o remount,rw /dev/block/mmcblk1p2 /system
adb shell chmod 0755 /system/bin/input
Please post issues/workarounds/bugs in this thread, I'll try to keep this list updated.
To answer from the other thread...
Timeframe-- well, this isn't me doing this. But I think the devs just want to take the edges off, so be patient... I'm just the messenger on the news that it's been done. This is other people's accomplishment.
In fact, froyo was done weeks ago, though not entirely from open-source/freely distributed components like this (as far as I know).
To answer some questions--
BT not working, FM not working, accellerometer not working. Softkeys should work... dont' see why not anyway. It's stock froyo. No gapps, no Superuser.apk, no nothing over and above AOSP. Overclocking not in but should be possible... video playback hasn't been tried (it's early still!).... battery life who knows I haven't even had a chance to let it run down... I posted because the news was "out" anyway. I also can't compare to stock because I've never run stock, believe it or not. But it's based on the same kernel 2.6.29. It boots off a SD partitioned for system, data, cache, and sdcard. Only thing (I think) it touches on the internal storage is resetting that boot counter, otherwise you'd only get 7 boots at a time. Doesn't need much space. 2GB should be enough. That's what phones have anyway. Guess it depends what you want to do with it. Performance is decent, not steller compared to my g2 at least. Will benefit from OC.
devis said:
@fattire
Questions on everyone's (well, mine at least) mind... please answer as much as you can, and a big big thank you!!!
1. Is BT working?
2. Is FM working?
3. Can we still use SoftKeys for hardware key emulation?
4. Can we overclock the processor?
5. How's the video playback?
6. How's the battery life compared to stock?
7. Since you're booting from SD, does that mean the internal memory of the NC remains untouched, should we need to boot stock?
and
8. How does the device feel overall?
Click to expand...
Click to collapse
Nice stuff guys keep up the stellar work
Sent from my LogicPD Zoom2 using XDA App
So awesome, looking forward to the progression of this!
I got my SD to boot tonight!
It defiantly isn't for the faint of heart but it seems to work well enough as a good base to start on. Pretty snappy to boot.
I would like to emphasize that this is VERY rough around the edges and if you aren't planning on hacking with the kernel, or code, or attempting to make your own rom then this is NOT for you.
http://i.imgur.com/WRyNV.jpg
http://i.imgur.com/H4ahM.jpg
Defiantly awesome work (and pure AOSP + TI drivers) which means no propritary B&N bits
Thanks for releasing such and early build to the public. It's not often you see that.
(I won't even consider playing with this build)
As a humble Analysts I grovel at the feet of your magnificent tech prowess.
(thanks)
Does this include a working JIT or is that one of the things in progress?
That seems to be one of the more compelling things from froyo (at least for a device with more internal storage than a nexus one). I would expect (well, hope anyway) that the froyo JIT would have a noticeable impact on the speed...
Mods, can we please stickie this?
Very awesome... Will try it out later today!
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Novarider said:
Since this runs off the sdcard can you power down the NC and remove the sdcard and boot normally?
Click to expand...
Click to collapse
Read: http://nookdevs.com/NookColor:_Nookie_Froyo#After_you_have_burned_the_uSD_card
To get back to stock, just remove the uSD card and reboot.
Click to expand...
Click to collapse
It has all the info you want, and is mentioned in the first post.
cicada said:
Workarounds for some known bugs:
No buttons! Try: http://forum.xda-developers.com/showthread.php?t=860153
Click to expand...
Click to collapse
You also have the option of converting the volume buttons to back/menu as well. It is documented in this thread, but the filenames have changed in this build. You will need to modify the following files..
/system/usr/keylayout/qwerty.kl
/system/usr/keylayout/twl4030-keypad.kl
I am not a developer.
I am not likely to become one at this stage of the game...
I am, however, either brave or stupid because I am downloading the image and will see if it will boot on my NC.
I do this because:
A) I want to SEE froyo running on my NC, and
2) If I have any problems, feedback might help the devs
I love seeing all the progress that has been made on these things.
Is flash supported in the browser with this initial froyo build?
jay084 said:
Is flash supported in the browser with this initial froyo build?
Click to expand...
Click to collapse
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Just rebooted back to my regular rooted NC system after pulling the sdcard and can only say-
Marvelous.
Yes, it is slow, no keyboard and all of the other things that were spoken of in the initial posts, but IT WORKS.
I don't have time to do much else with it right at the moment, but I will mess with it more later.
BertoJG said:
I tested flash and it does work.. The flash plugin is not included in the build however, I had to find it and install it via ADB.
Click to expand...
Click to collapse
Could you post the flash plugin you used? I would really appreciate it. Could you also comment on the quality of flash videos online. I'd like to watch espn3 on the nook...in bed...lol
OK, so I booted the rom, and followed the instructions at nookdevs...
Installing superuser.apk and pushing su seemed to work just fine!!!
Softkeys installed and got superuser permissions and works as well.
Installed astro file manager, and that works fine too...
At that point, I wanted to mount the usb storage and move over a bunch of APK files... mounted the nook and could only see the mlo, img file etc... no problem creating an apk folder and putting files in there, but then I can't see that folder when I look for it in astro....
Any info on simply copying files via USB using this build?
Also, thanks to all the devs for the awesome work... looking forward to playing around with this more!!!
Related
I looked for a while, and found parts of the method, but no guide....
can someone give me a link as to where i can find it?
I'm not sure that all the ROM devs are using the same code, so:
"Use the force; read the source."
On my current ROM (Aloysius V12), a2sd is a shell script at /system/bin/a2sd - 453 lines long. At the beginning of that script are the comments
Code:
# A2SD version 3
# Edited By: TrevE @ xda for damagedrom
# Based on the modded Apps2SD by Robert Travis Kirton
# Automatic ZipAlign by Wes Garner
Not the easiest read in the world, but "what it does" is right there; you just need to decipher the script.
In the Aloysius version, it becomes apparent that it just "runs" automatically (started from /init.rc). It can be configured by toggles in
/data/data/com.damaged.DConfig/dc.conf -or-
/system/etc/dc.conf
It appears from examination of that version of the script that it tries to be reversible - that is, if you turn it off with a toggle in the configuration file, the next time it boots, it will move the apps back to /data. Don't quote me on that, though; YMMV.
Make sure you have backups and test thoroughly.
bftb0
There's not much of a guide for it, but I'll try to explain it as best as I can.
Apps2SD (or A2SD) is a script originally created by Cyanogen. The script, in its basic form, does one thing: moves your applications from the internal storage (/data/app and /data/app-private) to a linux-formatted (ext2, ext3 and sometimes ext4) partition created on your SD card. The way it does that is the following:
1. Creates /system/sd/app and /system/sd/app-private directories on the ext partition of your SD card
2. Moves the programs in /data/app and /data/app-private to /system/sd/app and /system/sd/app-private, respectively
3. Deletes the /data/app and /data/app-private directories
4. Recreates the /data/app and /data/app-private entries as symbolic links pointing to /system/sd/app and /system/sd/app-private, respectively.
Over time, developers such as myself has expanded on Cyanogen's basic script (even Cyanogen has improved the script quite a bit since the original version). The program has evolved to do the following (depending on developer):
1. Moving dalvik-cache to the SD card (and even to the Cache partition in Modaco's version)
2. Enabling JIT functionality (an enhanced Dalvikvm)
3. ZipAligning programs to make them load faster
4. Changing the Dalvik heap size to minimize dalvik-cache bottlenecks
5. Enabling swap partition
6. Diagnostic functions to check if your setup is correct
7. Automated repair function
Currently, there are three popular versions of Apps2SD: CyanogenMod's version by Cyanogen (commonly known as Apps2SD 1.x, though I know it has evolved as well), Darktremor A2SD by me (version 2.x), and DamageControl's version by TrevE (version 3.x). The version numbers really don't mean anything nowdays. When I created Darktremor A2SD, I based my code from CyanogenMod's first versions (1.x). TrevE based his code from my 2.5 code. At the time, TrevE's code was the most feature-rich, but over time Cyanogen's version and my version have evolved, so now all three are close to the same features.
The way each controls the various options is different. Both Cyanogen and TrevE uses custom properties (Cyanogen starts his custom properties with cm for CyanogenMod, while TrevE uses dc for DamageControl). I use a series of files stored on /system/sd (the root of the ext partition) that control which options are loaded.
Cyanogen and TrevE's versions have GUI interfaces while mine is all terminal based commands. Theirs is easier to program, but mine is more flexible with immediate feedback (designed for diagnostics). Also, whatever roms don't work with Treve's version will usually work with Cyanogen's version. Darktremor A2SD was designed to work with most roms (whether it does is another question, but that's why it's constantly evolving as well).
Trying to keep this from sounding like I'm trying to pitch my program.
I don't know what else there is to say...if you want to ask more questions, I will be happy to answer them to the best of my abilities.
adammsu said:
I looked for a while, and found parts of the method, but no guide....
can someone give me a link as to where i can find it?
Click to expand...
Click to collapse
excellent replies, thanks you very much, both of you. That definitely clears some things up.
if i were to take what i read (from this and other things) and try to make it practical for me:
1: partition SD (after backups and what not)
2: install rom that supports
3: use one of the 3 a2sd apps (depending on rom) to move the files and set up functionality
sounds about right?
adammsu said:
excellent replies, thanks you very much, both of you. That definitely clears some things up.
if i were to take what i read (from this and other things) and try to make it practical for me:
1: partition SD (after backups and what not)
2: install rom that supports
3: use one of the 3 a2sd apps (depending on rom) to move the files and set up functionality
sounds about right?
Click to expand...
Click to collapse
Steps #1 and #2 sound about right - a2sd is already set up in them, and merely detecting an ext2 (or ext3) partition on your SD card will kick it in place.
Wiring it into another ROM that doesn't already have it is a little bit more detailed, and - because you need to start up the mounting and symlinking pretty early in the boot, part of the fixups need to be done inside the boot image. (That means that you would have to unpack the boot image, edit it appropriately, repackage it, and then flash that boot.img back to the phone). A fair bit of work.
Thankfully, the ROM devs that have everything set up for you have already done this work for you... just do steps #1 and #2... and then afterwards, make sure you understand the implications of doing regular Nand backups versus Nand+ext backups.
bftb0
Introducing...
Darktremor Apps2SD 2.7.5.3 Beta 04
Date of Release: January 29, 2011
Download Current Version
Instructions - Change Log - Commands - ROM List - Developer's Guide
Darktremor Apps2SD Fan Page ----
Darktremor Apps2SD Development Group
Are you installing Darktremor Apps2SD on your phone? Here are the instructions to help you: Facebook
Are you a developer wanting to include Darktremor Apps2SD in your latest ROM? Here is the Developer Guide: Facebook
Click to expand...
Click to collapse
Update on Beta 4
It seems I'm getting mixed results with these betas. I'm not sure why this is occurring, some people have been able to get this working right while others have had a hard time with it.
Currently, I'm rebuilding the entire program. This takes a while because I have to figure out how to pack all these options into the program but make it small enough to where it will run correctly.
I will say that some of the beta features are coming back out...one of them is the search for a partition code. I suspect that code may be leading me into issues with certain platforms, so I'm going back to the 2.7.5.2 method of mounting (mmcblk0p2 or mmcblk1p2).
Also, parts of the code will use Busybox Ash (the only code that won't will be starta2sd, which will still use Bash for the time being). The startup code will definitely use Busybox Ash.
Until then, here are the links to the the last two betas and the last official release:
Version 2.7.5.3 Beta 04 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta04-signed.zip
Version 2.7.5.3 Beta 03 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.3-beta03-signed.zip
Version 2.7.5.2-1 - http://www.darktremor.info/files/a2sd/dtapps2sd-2.7.5.2-1-signed.zip
And, if you want past versions, you can view the repository: ftp://dtuser:[email protected] (ignore the smiley face...that's XDA doing that.)
Click to expand...
Click to collapse
Beta 04 took longer than I expected to release. I have done major changes to the code:
1. New commands: convert-ext4 - This will convert your EXT3 partition into EXT4. Just a friendly reminder on this command: Not every rom supports EXT4, so it is possible to go into a boot loop if you switch roms. Use with caution.
2. Reworked convert-ext3 (convert-ext4 gets similar code)...now a flag file is set before the reboot (no conversion is done before the reboot). At load time, the conversion is performed. This takes longer in the reboot process and you may think your phone has locked up...wait about five minutes before doing anything with the phone.
3. Repair is rebuilt...now it uses existing commands to repair the setup (reinstall, remove, cachesd, cachepart, nocache, datasd, nodata). Definitely shrinks the code.
4. Added fix_permissions program to the package. This may help with Superuser issues when using the datasd feature. It is used in reinstall, remove, datasd and nodata.
5. a2sd install is back!!! Both a2sd install and a2sd reinstall do the exact same thing.
6. Dalvik heap code has been shrunk and now creates a file called dalvikheap. Actually, the code has been doing this all along (since about 2.7.5.2, I think), but I never put the code in to use the file.
7. Low Memory Killer code has also been shrunk and uses a file caled dtset_lowmem to set the low memory killer parameter.
8. Replaced Busybox PS function with Toolbox PS. The issue with Busybox PS is that it gives a false reading when I look for android.process.acore (which is the main program when the GUI starts up). If that is present, the program thinks you are trying to run Darktremor without any command line parameters. This was because Busybox would report the process was there when, in reality, it wasn't (validated this when my phone was boot looping.) Toolbox's PS reports the correct setting. This should fix the bootlooping issues some people are experiencing.
9. New commands: usedtbusybox and usedefaultbusybox - these commands may help in diagnosing issues that is may be related to the native Busybox on your rom. a2sd usedtbusybox will use the Busybox that is packaged with Darktremor. a2sd usedefaultbusybox will turn back on the scan behavior of the program introduced in Beta 03.
10. Support for Darktremor Apps2SD version 2.7 and earlier has been discontinued. To upgrade correctly from one of those versions, use version 2.7.5.3 Beta 03b or earlier.
11. Finally fixed stalled boot issues (or at least my tests with several roms says so.)
See the change log for additional details.
You will notice that if the program runs repair and finds a problem, it will correct the issue and reboot. You will see a second reboot when the dalvik-cache clears (this is to fix timing issues with CyanogenMod...I can't control that startup as well as I can other roms). This only happens if repair is ran or you flash a new rom (as repair will realign all data). If you are upgrading from a previous version of Darktremor, you should not see the reboots.
Click to expand...
Click to collapse
This is Darktremor Apps2SD, a multipurpose program that primarily allows a user to execute applications created for the Android OS on their Secure Digital card (with the proper setup...more on that later). But, Darktremor Apps2SD is all about stability. The goal is to be able for all users of the Android OS to be able to take advantage of a method to run their applications from a secure digital card.
But just because the Darktremor Apps2SD is all about stability, doesn't mean it isn't packed with features:
- Move applications (both free and paid) to the Secure Digital card.
- Move Dalvik Cache to run either from your Secure Digital card or from your cache partition and clears the cache on demand.
- Boot Loop Protection: prevents the phone from boot looping in the event the SD card could not be mounted.
- Dalvik JIT for faster performance on Roms which support it.
- User selectable sizes for the Dalvik heap sizes, allowing a user to freely optimize their system.
- Activate a swap partition on your SD card and sets how often the swap partition is utilized.
- Automatically fixes configuration issues.
- Users can check the free space on their SD card and check the installation to make sure all is setup correctly.
- Runs ZipAlign on demand...this makes your programs load faster.
- Built in help system for easy reference of commands.
- All features can also be reversed without repartitioning your Secure Digital card.
- New logging features assists in troubleshooting issues.
- Commands to set the Low Memory Killer feature at boot time. Great for those people who are the "set it and forget it" type.
- And more...
Darktremor Apps2SD is not the same as Froyo Apps2SD. Froyo Apps2SD creates a secure folder on the FAT32 section of your SD card (this is the section that you see when you mount your phone to your computer) and stores the programs there. This is nice as you don't have to do anything special with the phone, but it isn't backwards compatible with older versions of Android (Cupcake, Donut, Eclair) and, because of the way Froyo works, older programs not designed for Froyo will automatically stay on your internal storage (unless you install a program that forces the move to your SD card).
Darktremor Apps2SD takes a different approach. Based on the original CyanogenMod works, Darktremor Apps2SD uses symbolic linking to force Android into moving your applications to the SD card. Because Android will not allow anything to be ran from the FAT32 partition on your SD card (and, in Froyo, it will only allow you to run programs from a special folder), Darktremor utilizes filesystems called EXT2, EXT3 and EXT4. Each one of these filesystems is native to Linux (the operating system running Android), which allows you to run programs from them (same as, say, a computer running Ubuntu). This method is completely compatible with all versions of Android, including Froyo. In fact, you can run both the Darktremor Apps2SD and Froyo Apps2SD at the same time.
Check out the list of Roms that either have Darktremor Apps2SD installed or are compatible with Darktremor Apps2SD. Click on the link labeled ROM List at the top of this message.
Darktremor Apps2SD Installation Instructions
For the list of people that helped me test this on the various roms that use or can use Darktremor Apps2SD and the changelog: http://forum.xda-developers.com/showpost.php?p=7034326&postcount=3
Click to expand...
Click to collapse
The installation instructions can be found here: http://forum.xda-developers.com/showpost.php?p=7021325&postcount=2
Click to expand...
Click to collapse
If you want a list of commands for Apps2SD, type a2sd help.
Reserved...
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
THATTON said:
Thank you so much!!! Can I flash this with ClockworkMod Recovery? I saw that you recommend Amon's but just thought I would ask before I flash back to Amon's.
Click to expand...
Click to collapse
tkirton said:
Since we only have Amon's and Darch's recoveries, those were the only ones I could test with. It's possible you may be able to use ClockworkMod (I didn't ask my testers what recovery they were using).
Do a backup of your phone, then try it. If it works, let me know and I'll update the post.
Click to expand...
Click to collapse
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
THATTON said:
Everything went well and I'm up an running. Thanks.
Ps-proud to be a test subject. Lol
Click to expand...
Click to collapse
tkirton said:
As a reward for being the test subject, I have updated both the install post to include Clockworks Recovery and added your name on the Credits post as the tester.
Click to expand...
Click to collapse
Hey, that works for me! Thank you!
Add Apps2SD support in your Rom
I created a guide in my main thread on how to add Apps2SD into roms that don't have it.
http://forum.xda-developers.com/showthread.php?t=715116
Bump....New version 2.7.5 Preview Fix 4 is out (and there was a PF3, but it was only released to Desire users to try to work through the NAND protection on their device...their changes are part of PF4).
Has anyone tried this on the latest CM6 nightly build?
Chahk said:
Has anyone tried this on the latest CM6 nightly build?
Click to expand...
Click to collapse
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
djdarkknight96 said:
I was going to, but the nightly are so often that I would hate to keep having to do it every update...well the nightlies have slowed down....I might try it out! Will report back if works!
Click to expand...
Click to collapse
Cool, let us know here and in the CM thread. I would love to know as well.
THATTON said:
Cool, let us know here and in the CM thread. I would love to know as well.
Click to expand...
Click to collapse
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
I'll check it out and see what's going on.
EDIT: It's possible that Busybox Run-Parts won't process two files with the same name. Since I can't run it, can you run a logcat so I can see what's going on. Send it to [email protected] and I'll take a look at it.
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
mightykc said:
I flashed the zip in recovery using CM6 and it did not work. The zip flashed without error but my apps did not move to the EXT partition
Click to expand...
Click to collapse
It works on CM6. All you need to do is flash boot from Modaco's (Paul's) Froyo R21 with a2sd.
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Here's how Darktremor Apps2SD works:
1. First thing it does is transfer control to launcha2sd, which is ran by using bash instead of sh (bash seems to be more stable).
2. Once launcha2sd is running, it performs a quick test to see if you are asking for help (a2sd help). If so, it displays the contents of the help file and exits.
3. Next, it checks to see if the following properties are in the init.rc:
- cm.filesystem.ready or dc.filesystem.ready (only one has to be present)
If so, it can run the more advanced boota2sd. If not, it will run a basic version of Apps2SD (FYI, these properties actually are used to stop the init.rc until Apps2SD [and any other script the rom developer deems necessary to run] are complete. This prevents dalvikvm from interferring, preventing a race condition).
4. Next, it runs starta2sd unless you don't have the properties stated before, then it continues by moving the /data/app and /data/app-private to SD card (if needed and after attempting to mount the ext partition). Then it activates swap (if available) then it exits.
5. Under starta2sd, it checks to see if a command was requested (install, remove, cachesd, cachepart, jit, nojit, etc...). If so, it runs the appropriate commands for the command requested.
6. If no command was given, it checks to see if apps2sd is being ran for the first time. If so, it transfers control to boota2sd. If not, it displays a message stating you need to supply a command and promptly exits.
7. In boota2sd, it checks for the old flag files (from version 2.5 - 2.7) and moves them to the /data directory.
8. Next, boota2sd attempts to mount the ext partition. If that fails, it will engage Boot Loop Protection, which puts your /data/app, /data/app-private and /data/dalvik-cache (if it is stored on the SD card) back to internal storage and sets the No Apps2SD flag file. This can be reversed by executing a2sd install once the issue with the ext partition is fixed.
9. Next, it checks for flag files and whether the correct setup exists. If not (say you have the Dalvik to SD cache flag file active but your dalvik-cache is being stored on your internal storage), the program initiates auto-repair.
10. Once that is complete, it checks to see if it needs to move applications to the SD card and moves them, unless the No Apps2SD flag file is present.
11. Next, it looks to see if the user has activated ZipAlign on boot (a2sd zipalign) and, if so, will proceed to zipalign the /data/app and /data/app-private directories.
12. Next, it activates the swap partition, unless the swap partition isn't present or the No Swap flag file is set.
13. The program then ends.
This is the automated boot sequence. You can control the behavior of apps2sd by using commands (a2sd install, a2sd cachepart, a2sd align...)
System files are only modified if there is a need to (i.e. JIT) and only if the user activates the correct command (i.e. a2sd jit, a2sd nojit). In fact, the only time the /system partition is changed to a read-write state is during the JIT installation (and that is changed back to read-only when the setup is complete)...otherwise, the /system partition is read-only through the entire Apps2SD run.
mlevin said:
I'm eager to try this -- but I noticed that in the update.zip, there's a "new" copy of Vending.apk. Why is the Market app being replaced? How does this one differ from the stock FRF91 copy? It makes me a bit nervous to be replacing the app. Previous apps2sd approaches haven't needed to modify this. Can you explain a bit what's going on under the covers?
I would have thought that just an init script, an ext3 partition and a few symlinks would be all that was required...
Thanks
Click to expand...
Click to collapse
tkirton said:
Don't worry about it. It only replaces the app when you execute a2sd fixmarket. This was to address an issue with a disappearing market, but since then the problem has been pointed to zipalign (which is why zipalign won't run automatically at boot).
I think PF4a doesn't even have the command anymore, so, unless you manually push it from /data/a2sd, it won't replace anything.
The upcoming RC1 version will have that removed, as it is no longer needed.
Click to expand...
Click to collapse
Awesome! Thanks so much for the quick and detailed reply!
Just read through the code. Nice work!
I see that one of the options is to put dalvik-cache in /cache. Any reason apps can't be put into this partition as well? On a rooted device, /cache is mostly wasted space. Or does /cache get wiped on reboot like /tmp?
QUICK FAQ - 2/19/11
Q: WHAT IS THIS?
A developer port of Cyanogenmod 7 for the encore device, which has been in development for about two months starting in early January and has only recently been deemed good enough for a wider range of developers to use.
Q: WHERE TO GET NEWS ON PROGRESS?
I will tweet progress from time to time.
Twitter: @dalingrin
We are usually in #nookie on freenode.
You can always check the Cyanogen [email protected] http://github.com/cyanogenmod
Q: WHAT WORKS AND WHAT DOESN'T?
As of this writing, most things do work-- touchscreen, wifi, sound, accelerometer, etc.
See the issue list here: http://forum.xda-developers.com/showthread.php?t=960537
Q: How do report a bug I find?
PLEASE post logs to pastebin.com and include them in your report.
To grab android logs you can run "adb logcat -d > log.txt"
This will output the log to the log.txt file and can then be posted on www.pastebin.com
Kernel logs can be had by running "adb shell dmeg > dmesg.txt"
This will output the dmesg log to dmesg.txt for easy posting on www.pastebin.com
Use this template to post a bug in this thread:
--------------------------------------------------------------------------
Which build are you running? Please mention any customizations:
App or process having the problem:
Steps to reproduce the problem:
Describe the issue as well as you can:
Relevant logs(logcat, dmesg)
----------------------------------------------------------------------------
Q: WHO PORTED THIS?
Cyanogenmod itself is the creation of thousands of developers.
A vast team from around the world including members of Team Douche as well as unaffiliated individual developers have been collaborating for about two months on this port. Additional contributions continue to come from around the Internet. You are invited to help by contributing YOUR fixes.
Q: WILL CM7 RUN OFF OF AN SD CARD? OR DOES IT USE THE INTERNAL STORAGE OF MY DEVICE?
The nightly builds are intended to run entirely off the internal storage device. Should you decide to install one of those .zip files, you should expect to overwrite whatever was installed in those partitions.
It is critical to understand that CM7 is development software that may cause serious issues, loss of data, and/or other problems with your device and to your life in general. By loading and/or running the software, you must understand and accept full responsibility for your actions and all consequences and agree to adhere to the varied licenses and terms and conditions that comprise the software.
Q: IS THERE AN SD-ONLY "BOOTABLE" VERSION?
Not from the nighty builds. However-- should someone want to create such a bootable SD-- (warning: Slightly technical answer all it would take to create one is a new uRamdisk file with the partitions in init.encore.rc pointing to the correct partitions on the SD card.
Q: I AM AWARE OF THE RISKS AND ACCEPT RESPONSIBILITY FOR WHATEVER RESULTS. WHERE DO I GET THIS?
Cyanogenmod 7 for encore is available as a nightly build. See the XDA dev thread for download and development discussion:
Q: WHAT IS "ENCORE" ANYWAY?
Cyanogenmod has a fun little convention to name ports after the device's original project name.
Q: WHERE IS THE SOURCE?
On Github.com.
Q: I'M A "TECCHY" PERSON-- WHAT KERNEL DOES THIS USE?
A somewhat-modified version of the "stock" 2.6.29 source provided by Barnes & Noble (in accordance with the GPL). Changes to this kernel include a fix for a temperature bug, a fix to a cache race-condition resulting in kernel panics, ext4 support, and support for large block devices, among other things.
A port to 2.6.32 is currently underway that may facilitate improved "deeper" sleep.
Q: IS THE KERNEL OVERCLOCKED?
Just like the original stock kernel, the CM7 kernel runs at 800Mhz. However, you may overclock the default kernel to 925mhz through Cyanogenmod Settings. Cyanogenmod has a policy to not include voltage modified kernels. If you want a faster overclock see Dalingrin's 1.1 Ghz kernel: http://forum.xda-developers.com/showthread.php?t=925451
Use entirely at your own risk.
Q: WHAT ARE THESE OTHER VERSIONS OF CM7-BASED ROMS?
Because CM7 is open-source software, people are free to modify it as they wish and re-release, provided they are compliant with the terms of the original licenses. The CM7 developers have nothing to do with these derivative releases, which may or may not be of decent quality.Q: WHEN WILL THE FINAL VERSION BE RELEASED?
When it's ready. Please do not ask this, as it is considered the mark of a newb. In the meanwhile, nightlies are rolling out every evening with the improvements from that day, not only to the encore port in particular, but to Cyanogenmod in general.
For a list of what's changed recently, bookmark:
--->>>>>>>>>>>>> this link <<<<<<<<<<<---
Link to the latest nightly...
http://mirror.teamdouche.net/?device=encore
The current CM7 encore zip seems like it will write to mmcblk0p5 (NC's internal EMMC). Any chance of getting one that uses something like mmcblk1p2 instead to install on my EXT4 SD Card? Why? I'd prefer my internal eclair install to remain unaffected by these experiments.
epakrat75 said:
The current CM7 encore zip seems like it will write to mmcblk0p5 (NC's internal EMMC). Any chance of getting one that uses something like mmcblk1p2 instead to install on my EXT4 SD Card? Why? I'd prefer my internal eclair install to remain unaffected by these experiments.
Click to expand...
Click to collapse
Ditto
10char
can we remove the lock screen ? ( "none" in the settings doesn't work )
fabienk said:
can we remove the lock screen ? ( "none" in the settings doesn't work )
Click to expand...
Click to collapse
A free app called no lock worked for me on other roms
Sent from one of those missing Droids
Anyone running nightlies yet? Any early reviews? Screenshots would be great too If you can even install n app to do that yet
adma84 said:
Anyone running nightlies yet? Any early reviews? Screenshots would be great too If you can even install n app to do that yet
Click to expand...
Click to collapse
I made an awful video:
http://www.youtube.com/watch?v=u1Z29zs70YE
Its fine. I got no idea on how to install it. But when video works ill look Into it. Is there a way to move the taskbar down?
Nook Color via Xda App
Install to EMMC Instructions
I dont get how to install this to EMMC. Can someone post a quick guide. Thanks in advance
myteematt said:
I dont get how to install this to EMMC. Can someone post a quick guide. Thanks in advance
Click to expand...
Click to collapse
instructions are posted in the ext4 thread.
muness said:
Caveats:
* eMMC only.
* very early test build.
Step by step instructions:
Download an ext4 compatible bootable SD recovery from http://forum.xda-developers.com/showpost.php?p=11447175&postcount=1
Verify that the download worked. md5s are at http://forum.xda-developers.com/showpost.php?p=11449725&postcount=15
Extract the .img for the .tar.gz
Burn the recovery img to an SD card as explained at http://nookdevs.com/NookColor_Rooting#Steps
Download the flashable zip. Currently available via torrent (http://tracker.cryptolect.com/IOM/update-cm-7.0.0-RC1-encore-KANG-signed.zip.torrent) and several mirrors (http://legacyschool.us.to/nookdev/cyanogenmod/update-cm-7.0.0-RC1-encore-KANG-signed.zip , http://tsunade.net/nookdev/cyanogenmod/, http://mother-douchebag.com/update-cm-7.0.0-RC1-encore-KANG-signed.zip) Check the md5 of this zip!
Download the google apps from one of the links at http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps Check the md5 of this zip!
Copy the cm7 zip and the google apps zip to the bootable SD card you created.
Unmount the SD card from your PC, insert it into your nook.
Reboot into the SD card/recovery should read version 3.0.0.6.
Under mounts Format system, data, cache.
Flash from .zip the cm7 zip and the google apps zip.
Remove the SD card.
Reboot system.
Click to expand...
Click to collapse
Hi, I watched your video on youtube, now I'm wondering what devs mean saying dsp video playback is broken, as you were playing a flash video.. can someone explain?
At this point, an sf version would be much more practical.
KitF said:
I made an awful video:
http://www.youtube.com/watch?v=u1Z29zs70YE
Click to expand...
Click to collapse
Great video, and I subscribed to your collection of videos on YouTube. Thank you for not adorning it with some idiotic music.
However, out of what I heard, I didn't understand, you sounded like Flash (10.1?) is working (and it shows full YouTube Web page where it's needed), but YouTube itself is not working. Could you elaborate on this? Could you try to adb install other versions and tweaks of YouTube apk, like "HQ" YouTube, or "signed_YouTube", or whatever?
Please post more videos on Flash/YouTube/other (mv4, avi, etc.) videos playing, Flash Web pages and elementary Flash games.
Thank you. Have posted your video in my blog, and will be posting more.
-------------------------
fineoils.blogspot.com
captive said:
Hi, I watched your video on youtube, now I'm wondering what devs mean saying dsp video playback is broken, as you were playing a flash video.. can someone explain?
Click to expand...
Click to collapse
From what Ive gathered (i could be completely wrong) it lacks video decoding drivers. Youtube.com works because its using flash and is based on the cpu. Where-as youtube apps do not use flash, and thus try to load a video codec which doesn't exist causing it to error. The youtube app alongside other non-flash video apps fail to load for me.
My Installation Diary
For those that need more in depth instructions, I logged my entire install process and am sharing. If anyone has suggestions for changes, please let me know. I might have done something different from another person, but I had no problems getting the first release installed, running and overclocked.
Your mileage may vary, I am not responsible for anything you do to your Nook, even if you did follow my advice. I am not claiming to be anything special here, just sharing what worked for me and my Nook.
faceman said:
Before beginning:
1. Booted into Recovery
2. Created new nand backup
3. Removed and stored MAIN sd
Using a new and different sd:
1. created 4gb CWR_ext4_0.1 bootable SD
2. moved flashable zip (update-cm-7.0.0-RC1-encore-KANG-signed) to SD
3. moved latest gapps (Latest Version/Google Apps - CyanogenMod Wiki) to SD
4. insert into NC
Installing
1. boot with bootable sd (CWR_ext4_0.1 - ClockworkMod Recovery v3.0.0.6
2. 'mounts and storage' --> format /system ; /data ; /cache
3. back to main menu
4. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-cm-7.0.0-RC1-encore-KANG-signed.zip"
5. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "gapps-gb-20110120-signed.zip"
6. 'mounts and storage' --> unmount sdcard --> remove sdcard
7. reboot
First Boot
1. (chills seeing that little cm7 droid boot animation)
2. @ Welcome to NookColor --> waited full 5 minutes for system to settle (?)
3. tapped Droid to begin setup
4. waited for Notification Bar to show WiFi available --> dragged down to open
5. Selected my router and logged in
6. Used built in 'Back Button' in top right of notification bar to go back to setup
7. @ Set up your Google Account --> signed in
8. @ Market Apps Installer - IMPORTANT: Read This! --> OK
9. @ Choose the apps to install --> preference i guess (gmail and google search were already installed - I added YouTube) --> ok
10. above took me to YouTube install screeen from market, seleceted Install then OK
11. @ Use Google Location --> i uncheck both since it's not a phone --> Next
12. @ Back up data --> i uncheck again --> Next
13. "Your Google Account is now linked to this phone" --> Finish setup
14. now to set time prefferences --> personal preference here (set time zone and current time will adjust) --> Next
15. WOOT! CM7 Home Screen!
16. Open Apps --> Settings --> CyanogenMod Settings --> Lockscreen --> Style Options --> Lockscreen style --> change to Sliding Tab (this is because the Rotary wheel isn't sized right yet and is real hard to use currently)
17. back @ Settings --> Applications --> check allow for Unknown Sources
18. open Market --> downloaded Titanium Backup
19. in markeet --> downloaded Screenshot It Trial
20. in market --> downloaded Flash Player 10.1
21. in market --> downloaded Linpack for Android (bench test)
22. Reboot into Recovery - forgot to flash the 1.1 oc kernel (duh)
23. 'install zip from sdcard' --> 'choose zip from sdcard' --> select "update-1100mhz-froyo_CM7-emmc-cwm.zip"
24. Reboot
Enjoying a nice overclocked CM7 build...
Click to expand...
Click to collapse
MattJ951 said:
From what Ive gathered (i could be completely wrong) it lacks video decoding drivers. Youtube.com works because its using flash and is based on the cpu. Where-as youtube apps do not use flash, and thus try to load a video codec which doesn't exist causing it to error. The youtube app alongside other non-flash video apps fail to load for me.
Click to expand...
Click to collapse
Sounds like a good enough explanation to me. Except for the part that YouTube presumably based on CPU (=software decoding?) is using Flash (? Flash requires specific hardware decoding support for its quasi-H.264 stream decoding, if none offered, it won't even install).
Missing "commercial" decoders capable to use HW assisted decoding (and rendering) in a "clean" CM7 nightly could be to blame, the question now is what decoders are missing and how to add them.
In any case, I would love to hear (and possibly see in video clips) some other experiences. Namely, my first impression was quite opposite: YouTube (inline, in a Web page, and not in apk) is now working whereas full Flash 10.1 doesn't install, or FCes if installed somehow, etc.
Lack of list with known unfixed bugs for the nightly turns the build into a puzzle. Sure the CM devs are in no way under any obligation to accommodate every piece of proprietary code (YouTube, Flash, Market, Gapps, etc.) but at least they might state simply that IVA2/DSP doesn't work yet in this initial build.
On the more positive note, I would love to hear and see the video of improved GUI responsiveness and some racing game showing nice response and detailed textures, etc. Neocore benchmark? Linpack?
aludal said:
Sounds like a good enough explanation to me. Except for the part that YouTube presumably based on CPU (=software decoding?) is using Flash (? Flash requires specific hardware decoding support for its quasi-H.264 stream decoding, if none offered, it won't even install).
Missing "commercial" decoders capable to use HW assisted decoding (and rendering) in a "clean" CM7 nightly could be to blame, the question now is what decoders are missing and how to add them.
In any case, I would love to hear (and possibly see in video clips) some other experiences. Namely, my first impression was quite opposite: YouTube (inline, in a Web page, and not in apk) is now working whereas full Flash 10.1 doesn't install, or FCes if installed somehow, etc.
Lack of list with known unfixed bugs for the nightly turns the build into a puzzle. Sure the CM devs are in no way under any obligation to accommodate every piece of proprietary code (YouTube, Flash, Market, Gapps, etc.) but at least they might state simply that IVA2/DSP doesn't work yet in this initial build.
On the more positive note, I would love to hear and see the video of improved GUI responsiveness and some racing game showing nice response and detailed textures, etc. Neocore benchmark? Linpack?
Click to expand...
Click to collapse
it's so early on, I think we are lucky to even have nightlies. I doubt they will release any 'known issues' until an RC
adma84 said:
it's so early on, I think we are lucky to even have nightlies. I doubt they will release any 'known issues' until an RC
Click to expand...
Click to collapse
yeah..., I thought so too. Still good to know that SGX GPU core has started to breathe (in GUI responsiveness and maybe in some games) instead of just sucking the battery juice for nothing.
Forgot to ask: has anyone rooted it to see and change LCD density to its physical 169.3333? Maybe some stuff with wrongly scaled lock screen, etc. will resolve better? Back arrow in a right upper corner is weird, hopefully Volume keys hack is still doable.
Forgot to ask how does new fake name "Encore" for the NC affect the completeness of the Market?
Hey everybody!
***New APK editor added! Set the keys to whatever you want, see below!***
****I will not be held responsible if your Nook Color starts eating babies!!****
****Or if it breaks either!!****
****Added a revert, for those who may have issues returning the keylayout to stock (like 1.1 users who can't run the keylayout app)****
****As an added request, if anyone knows how to reload the keylayouts sans reboot, please let me know, as that is really the only thing missing from this little thing. I would love to be able to quickly reload these as needed.****
So after creating the flashable zip file for the keylayouts, and receiving some feedback that implied it would be nice to have more options, I decided to brush up on the coding skills and write a nice little app that can re-write the keylayout files without having to flash anything. This is actually my first android app, so please provide me with any feedback you may have, the more the better. The way I see it, the more I know, the better things I can make.
The keylayout app currently supports mapping the volume keys to these items:
Volume Up
Volume Down
Menu
Back
Search
D-pad Center
and can additionally support wake on press, if desired. Once written, you will need to reboot your device for the keylayout to be effective, but it's still easier than manual edits or multiple flashes.
***Note that using the app requires su access, and also at this point requires that you first flash one of my v5 keylayout zip files***
***I have received notice that the application does not run on stock rooted 1.1.0 I will be looking into this and posting an update, and most likely a revert to stock zip in case anyone needs it.***
Thanks go to whoever first suggested this, I'll be damned if I can't remember who I got this from, but thank you, whoever you are, I'll be sure to give you props when I figure out who you are.
History over, now for the details:
To install: Simply flash either zip file in CWM after flashing your CM7 or Honeycomb build to your eMMC. Once you do this, you can install and use the apk file to make changes to the keylayouts to your heart's content.
The CWM zips have been confirmed to work on most all versions of android for the nook, and in theory, the APK should work as well, however YMMV. If it works, or if it doesn't, please please post your version or build info, and let us all know what works and what doesn't.
Feedback and/or critiques accepted, may be subject to rebuttal. Hope this helps someone else, and thanks to everyone on this forum for all the hard work you do!
FYI: For those who still want an easy way to change the volume when these keys are no longer volume keys, try replacing the longpress home app with Recent Plus, by local forum contributor timoskrempel, which I first found HERE and works very well as a replacement.
Version History
-----------------------
apkv0.1b - Initial version of the keylayout app. Feedback appreciated.
v5: added files that apparently weren't as useless as I assumed. Also created inverted keys zip, use INV zip to switch the buttons.
v4: removed useless files from update zip, cause I'm being a bit too perfectionist.
V3: added files to improve compatibility (HC v4 tested, should work on Froyo, maybe stock)
V2: removed wake on press (thanks jasoraso)
V1: First Version
I definitely prefer hard keys, even with the modifications in CM7. I'll give your zip a try next time I flash a rom (I've already changed my qwerty.kl on this rom).
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
jasoraso said:
One other thing - I also prefer to remove the "wake" for those 2 keys, I found that the NC was accidentally waking up from inadvertent keypresses on the volume keys ...
Click to expand...
Click to collapse
An excellent point. Editing my zip and attaching v2. thanks to you!
success! just flashed this along with nightly#4 and it works like a charm.
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
digitalslacker said:
I love this. always get stuck in pics in Facebook and can't get back.
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
EpicFail236 said:
Widgetsoid has a volume adjuster that I use, though more often I just use headphones with volume sliders built in, so I skip using the software entirely. Ideally, I would love to be able to mod the framework to add a quick volume adjust button to the status bar like the softkeys, however that involves code editing that I just haven't dug into yet. If I do make the edit, I'll be sure to post what i make though.
Click to expand...
Click to collapse
thanks, i'll check it out.
What would be really cool and I'm not sure it's possible and I know it's not in the scope of this thread; but a way to change functionality of the buttons per app. So for example when in Pandora (or music app of choice) buttons behave as volume buttons, but under other various apps like gallery it could be home+back button set.
Seems like you'd have to have an app running as a service and monitor the currently running focused app (not in sleep mode) and depending on what has focus do a live update to the qwerty.kl file to change buttons to expected functionality, not sure if a reboot is required after an update to the kl file though?
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Thanks for your work, installed without a hitch..
Click to expand...
Click to collapse
change mapping in step 4 from here:
http://nookdevs.com/NookColor_Remap_volume_buttons_for_back_and_menu
adb pull /system/usr/keylayout/TWL4030_Keypad.kl
adb pull /system/usr/keylayout/omap_twl4030keypad.kl
edit 'TWL4030_Keypad.kl' and 'omap_twl4030keypad.kl' with a unix line ending aware text editor (Notepad++, gedit, vi)
replace 'VOLUME_DOWN' with 'BACK' and replace 'VOLUME_UP' with 'MENU' in each (or vice-versa)
adb shell
mount -o rw,remount -t ext2 /dev/block/mmcblk0p5 /system
exit
adb push TWL4030_Keypad.kl /system/usr/keylayout/TWL4030_Keypad.kl
adb push omap_twl4030keypad.kl /system/usr/keylayout/omap_twl4030keypad.kl
adb shell
cd /system/usr/keylayout
chmod 644 omap_twl4030keypad.kl
chmod 644 TWL4030_Keypad.kl
exit
adb reboot
Click to expand...
Click to collapse
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Thanks for the heads up, will review and post v5 sometime today.
my status bar always shows with HoneyComb, so I always have the back menu buttons. are there apps where this is not the case?
Anyone try this on froyo yet?
fattymcdirty said:
not working with
[ZIP][DEV][ROM] HC v4 eMMC 2nd ed. - Flashable ZIP {02/21/11}
buttons still remain in their normal functionality...
Click to expand...
Click to collapse
Yeah, I totally deleted an extra file, added to v5 and it should now work with this eMMC build. oops.
spikey911 said:
How can you revert back to stock?
Also is there a way to swap the keys? It seems more natural to have the back key as the +
Click to expand...
Click to collapse
I will have to put together a stock zip and put it up sometime in the near future. Your swap keys is not easily done directly, but I have posted a new flashable zip that will swap the keys, flash INV-v5 to have the volup function as back and voldown to work as menu. This one I haven't tested, as I don't actually have my nook with me here now, but in theory it should be OK, as all I did was swap the mappings in the kl files.
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
rickpref said:
After setting up CM7 Nightly 4 last night I replaced the SDcard with CWM 3.0.0.6 used to install CM7 with a fat32 8gb for storage.
Afterwards I installed ROM Manager and the latest Recovery included - 3.0.0.5.
I am able to flash Dalingrin's latest kernel through here but when I went to flash todays Nightly CM7 it did not work (probably because of the 3.0.0.5 i figured). I plugged back in the 1GB SD with 3.0.0.6 and successfully flashed todays nightly.
I then tried to flash the Hard Key Mod file using the emmc recovery and it did not work so I copied it to my 1GB SD and that worked.
Anyways...I wrote this just in case someone was having the same problem I had flashing the Hard Key Mod file and to see if there is any method to set up 3.0.0.6 on the emmc so that I don't have to insert the 1GB SD every time I wanna flash CM7 nightlies.
Click to expand...
Click to collapse
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
EpicFail236 said:
My assumption (it may be wrong, as I do not have my nook present with me to confirm) is that the system partition on the CM7 builds is ext4, and as a result, 3.0.0.5 would not be able to access it to flash any data. flashing either the cm7 nightlies or my additions, both of which write to this ext4 partition, needs to be done via 3.0.0.6.
That being said. I personally managed to get 3.0.0.6 to work on my emmc by taking the uImage and uRamdisk from the SD card version, renaming them uRecRam and uRecImg, and copying them to the eMMC boot parition. I would not recommend doing this without knowing *Exactly* what you are doing, as overriding these files with other files could cause bad things to happen, and as I said above, bad things are bad.
Click to expand...
Click to collapse
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
rickpref said:
Yeah, I figured it had to be that EXT4 partitions are not compatible with 3.0.0.5 but it took me a while to get it. So I take it you need to use ADB in order to rename and copy to boot those files?
Click to expand...
Click to collapse
My ADB machine was down and out at the time, so I had to do it via ES file manager and the terminal on the nook itself, but yeah, manual replacement was the way to go. sometimes a bit of command-fu is just easier than the alternative.
digitalslacker said:
Question though, what do you all use for a good alternative to adjust the volume on the fly?
Is there a preferred widget? Right now i just have a ADW shortcut to the sound settings on the home screen.
Click to expand...
Click to collapse
I use Volume Widget by Futon Redemption. It gives you two little onscreen +/- buttons to adjust the volume.
[ROM] CM7 8GB &16GB Compatible Beta for the Nook Tablet.., Updated 7th July to Beta
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss of information with your Nook Tablet. You use this software at your own risk. By choosing to download and install this software on your device you accept that you are willing to risk your own device and that any damage and or total loss is your own responsibility.
FOR PROGRESS AND UPDATES CONTINUE TO READ THIS THREAD. FOR KNOWN BUGS AND ISSUES PLEASE SEE THIS THREAD
Below you will find Internal release of our Nook tablet CM7. This has been rebuilt from the most recent CM7 stable source. I'll update the 2nd posts with release information asap.
Please feel free to base your rom on ours, I believe it is now tested well enough and is sufficiently stable to use.
The Source for the CM7 android device folder, the kernel and meghd00ts Improved recovery can be found here Here
For information on what you can and can't do and reasons for this please visit HERE
INTERNAL VERSION 8GB & 16GB COMPATIBLE
Download HERE MD5 95043b08484aa218ccf93b5ef4785825
For the internal version you need have access to CWM either internally installed as your recovery or from an SD card. I'm not going to reinvent the wheel telling people how to do that. Just have a look through the development thread and you'll se numerous threads showing you how to do this.
This version has the ability to reboot to recovery added to the reboot option in the power menu. It does not however come with a recovery image, this was already released by lavero.burgos and can be downloaded from http://forum.xda-developers.com/showthread.php?t=1640958
PLEASE BACK EVERYTHING UP BEFORE YOUR BEGIN!!!!
Once you have CWM on screen with the downloaded update zip archive on your sd card, Follow these simple steps
1. Goto install zip from sdcard
2. Choose zip from sdcard ( if CWM hasn't recognized your SD card you need to eject it and re insert it once or twice, sometimes you need to go to mounts and unmount SD, pop it out and back in then select mount sd)
3. choose the CM7-TEAM-B-BETA1-signed.zip
4. scroll down and select Yes - Install CM7-TEAM-B-BETA1-signed.zip
5. sit back for a couple of minutes while the installation is carried out
That’s CM7 installed, next you need to prepare the rest of the device
1. press your power button once
2. ***OPTIONAL*** scroll down and select wipe data / factory reset, this is optional but if you are coming from a different OS it is recommended, if you don't it can sometimes causes force closes and various other issues.
3. you're ready to roll! scroll up and select reboot system, initial boot can take a while and does pause for a short while on the black screen between flash page and CM7 Animation, enjoy CM7 For Nook Tablet!
if you were already running a version of CM7 it is possible you may be able to skip the wipe data bit and just select wipe cache instead but it's best if you can wipe data and know that you have a clean install without any bugs remaining from a previous install. By all means try just clear cache and see how you go, if you seems to have lots of bugs we recommend doing a clear data and trying again.
SD VERSION IMAGE ***UPDATE NOT YET AVAILABLE this is the Alpha final version***
Download HERE
I've done the SD version a little different this time, it's as a 4gb SD image (the last partition is used as SDcard in CM7 so you can resize this partition to fill up your whole card if your card is bigger than 4gb). The image can be burn using windows Image writer or dd command in linux / OSX
The window software is available HERE.
To write the image on linux / osx do the following
WITHOUT your sd in the machine go to a terminal window and type
Code:
mount
Notice the drives that are showing they will be something like dev/sda. Now insert your SD and give it a moment to recognise it. Once again terminal type
Code:
mount
and you should have an extra device such as /dev/sdc showing which is your sdcard (it may say dev/sdc1 or something but you aren't interested in the number)
Once you have the SD device id use following code exchanging sdc for your device id
Code:
dd if=/location/of/SDfile.img of=/dev/sdc
Then sit back and wait, it will appear to be doing nothing and will take a long time but once done the command will complete and you have a nice new SD version of CM7 to run
Power off the nook, insert the sd and then power it on to enjoy your new CM7. If it done'st boot try completely powering of and ten connect power cable and wait for it to turn on and hopefully boot form SD. The first boot WILL take a few minutes. Consecutive boots will be faster
We've been asked a number of times for a donation link so I set one up you can click HERE. Or if you prefer to donate directly to myself or Goncezila by clicking on the donate buttons under our names. We thank you in advance for your generosity
***** DISCLAIMER ******
Please note this software is still classed as experimental and you use this at your own risk. We have done some in house testing and all has worked fine but we cannot guarantee the exact same results for everyone. We accept no responsibility for any damage or loss on information with you Nook Tablet. You use this software at your own risk.
First boot can take a little while. once in you will be requested to enter your Google account details, because your wifi is not yet connected you will be better of skipping these steps, you will be asked again as soon as you try to open Google Market anyway.
Tap the menu button and select settings (not adwsettings) go to wifi and setup your wifi connection, if for some reason wifi networks do not show, just toggle wifi off and on and it will sort it's self out
Feedback thread HERE so please make sure you post any questions and / or feedback in there and keep this thread for development only. Thank you!
Thanks and mentions
All those that support the new release, I'm sure you all know who you are
Quid246 - for his skills in photoshop to make our new splash screen (Alpha release)
Bauwks - Without him we would not be here. He blew the top off the bootloader and his thanks bar is no where near what it should be. Also a thank you for him agreeing to allow us to change his box image on the bootloader when we asked. Please find some of his posts and hit Thanks!
Loglud - again for helping us out with our research
AdamOutler - His guide was used to help us with kernel issues and build our SDcard version
succulent for pointing out that although we had commented out a file in the build, it was was still possible it was effecting up our new build. Also thanks to succulent for creating a build script that automatically added the 2nd boot onto the boot.img during source build. Thank Succulent! You’re a star, it just wasn't happening when I tried to do it
The Cyanogen Mod team for the initial build of Cyanogen mod that we ported over
Generally every other member of XDA - For being so supportive and throwing out ideas and experience!
Know issues, Hints and Tips
keyboard numbers layout when you hold a letter doesn't initially work, to fix just change keyboard language to your local setting e.g. US english
PROGRESS UPDATES
7th July 2012
Released beta update built on latest Stable CM7 source
Made some changes which will hopefully help with wifi issues
added some stability fixes
Added reboot to recovery in the reboot menu
Other minor issues tweaked to improve general overall performance and response
MARCH 20th{/I]
build.prop update zip added to support thread to cure mounting on USB issues
MARCH 9th
CM7 Final Alpha released
A complete relbuild of CM7 for the Nook Tablet. The new version is based on Gingerbread 2.3.7 CM7.2
All software updated to latest CM7.2 version and all files rebuilt to match
Full hardware video decoding for h264 encoded videos
Hardware acceleration for gfx
Wifi issues fixed so now connection should work without crashing
GAPPS removed as per Google requests and GAPPS download link added to OP
Many general system bugs fixed
Much much more that ill post here when home from vacation
MARCH 7th 2012
SD version of CM7 re-released
MARCH 5th 2012
Sorry for the lack of updates recently, Gonc and I have been really busy but we're happy to say a new build has been getting tested personally by us and has now been passed on to the testing team.
Bit more about it is HERE
FEB 19th 2012
2nd public release of CM7 for Nook Tablet.
Changes since original version are:
Format bricking issue fixed
Boot count issue where it resets your device to standard after 8 boots fixed
Market should now install any software you can get on there without the SD / USB issue
Browser should now happily play videos from mobile youtube
Graphics driver update allows playing of YouTube videos a720p without issue
Previous issues updating BusyBox should now be cured
Many games and applications that crashed on intro video will now work flawlessly
Internal media partition now fully accessible
internal media and sdcard now show when connected to USB on computer
more things which I'll add here when I remember them!
Feb 12th 2012
The new build which is alpha 8 is now ready and testing will begin in the next day or two.
Thanks to all members of the team for volunteering and to xIndirect for setting up the application forms online that everyone filled out to become members and the bug report forms he's also set up.
Goncezilla and I haven't really discussed a length of time for testing but generally Testing will continue until we believe that the remaining bugs do not cause severe problems for the end user. Once we are at that stage the donators will then get their copies which will allow us to gradually increase the testing coverage before finally being released as a beta to all member of XDA.
Myself and Goncezilla would like to take this opportunity to thank everyone for their support and understanding while we build you a version of CM7 for your Nook Tablets that we can be proud of
Feb 10th 2012
Following bugs have been fixed
SD format and bricking issue,
Market app install problem
Various software crashing when it tried to play video (even browser in mobile youtube)
Internal Media partition not mounting
Media partition not connecting to USB host when plugged in
Further information on updates and release are available HERE
Difference
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
joeras said:
Sorry for this question. What are the differences between internal and external? Does internal completely wipe and remove all Nook software, and external only boots CM7 with the card in and boots Nook style without?
Click to expand...
Click to collapse
For Internal you need to have CWM running (either from SDcard or internally) and it WILL wipe your stock setup.
External runs purely from the SDCard and will not mess with your internal data.
Remember that Celtic and I are the only ones who have tested this as of yet so there may be unfound bugs! This is Beta after all
Please report all bugs here, do not PM us. We will try to validate and then correct them.
Enjoy everyone!
tonyp22 said:
For those on Windows machines (like me!), the free Mini Partition Wizard Home Edition can be used to create the SD card partitions. In this case just make the first partition Primary and Active; that will allow it to be seen as a bootable partition.
Click to expand...
Click to collapse
Yes sure just shrink the partitions a little to fit
We'll be adding a small modification to allow SDCard simulation when booting form card which will require adding a 4th partition later to act as the SDCard
Just thought to release as was to get it to everyone
I take it there is a way to go back to stock 1.4.0 just in case?
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
arclite00 said:
I take it there is a way to go back to stock 1.4.0 just in case?
Click to expand...
Click to collapse
Yes you can flash a stock image the same way
did internal version. Downloaded to PC, unpacked, copied directly to directory via usb mount, restored. The restore went fast, and the initial boot-up was faster than my G2's backup restores...lol Connected to wifi, signed in, and up and running.. Fantastic!!! kudos!! and i used the "Thank You" button so i'm not thanking you in this reply...<snicker> Over all, everything done in less than 5 minutes. Now to tweak/customize/play with.
For those of us who don't know/have ubuntu, can you point to a good resource/post for creating the SD card under Windows 7 to run the SD card version of CM7?
Thanks!
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
offlimitz said:
If I don't see a clockworkmod folder I assume it installed wrong or I create the folder?
Click to expand...
Click to collapse
I'm pretty sure Clockworkmod makes it as standard, as long as you have clockworkmod installed you should be able to just create the folders and drop your files in, do a backup from CWM and the folder should appear anyway
Thanks man. downloading sd release now. this doesn't affect the stock NT rom, right? the SD release ofc.
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
darthvince said:
Celtic,
You may want to mention that the user may need to eject/reinsert the SD card for CWM recovery to recognize it.
Thanks for the good work!
Click to expand...
Click to collapse
I'll post that in first thread now.
Know-Fear said:
Unit is rebooting into cm7 as we speak. Looking great, speed is awesome. Great job guys.
Click to expand...
Click to collapse
After it's first boot it's a lot quicker than stock
In fact I think even the SD version is faster than stock, stock really is poor!
Just an FYI to everyone. We mounted the internal B&N partition (the 11 GB that used to locked out) to /data/media and the 1GB you used to have access to to /mnt/media.
Both fully rw!
Holy **** people!! 200 downloads already and only 20 of clicks of thanks on the first thread :s
I think my server bandwidth is going to get a hammering, I best check it's ok!
Sorry for the basic question, but when we go to CWM -> Advanced restore -> NTCM7, do we want to restore boot? system? data? cache? sd-ext? all?
Thanks!