Kindle App Working on my 10.1 0813 and now 10.2 0926 emmc install - with 384m

Kindle App Working on my 10.1 0813 and now 10.2 0926 emmc install - with 384m - Nook HD, HD+ Themes and Apps

Please note that someone tried this on their SD card install of 10.2 and it apparently rendered it unbootable somehow ( build.prop edits can be dangerous, but I have no idea what went wrong as these are just the roms previous values ). Nandroid backups if possible are always a good idea...
UPDATE 09/25/13: I am now using a heapsize of 384m, and everything seems to work quite well for me ( some things are working better than before ). Also, I am currently leaving the other two settings at their new values.
dalvik.vm.heapsize=384m
I had begun to experience intermittent lag with the higher values, and although it usually went away if I used the power button to turn off the screen and then turned it back on again...
I am finding that some programs seem to run much faster/smoother with the new heapsize of 384m.
FYI: After experimenting with just changing the heapsize, first to 512m and then to both 402m and 456m, I have gone back to my original changes of restoring all of the dalvik vm settings to their pre-0813 values. My reasons are as follows:
1) As verygreen noted, there is some lag with the 512m heapsize, but I don't experience it with the other two changes made as well.
2) If my heapsize is set to less than 512m I get intermittent screen flashing on my setup ( exacerbated when charging ).
3) Several apps that I thought had become incompatible with 4.3 actually just need the larger heapsize to operate correctly ( they had actually stopped working with the 4.2 0813 release but I originally skipped that one ).
4) The 'Stay Awake while charging' setting works properly on my setup with the changes, and I have stopped getting the 'Unfortunately XXX has stopped' type messages.
5) Finally, on my setup, for some reason the Kindle App still crashes with anything less than a 512m heapsize ( this is probably due to some of the software that I am running, most notably Resolution Changer ).
So, I went back to the original changes. Of course, your experience may vary... :cyclops:
This is the official word/fix from verygreen:
verygreen said:
New binary drop cm-10.2-20130903-UNOFFICIAL-ovation-sdcard.zip
This adjusts dalvik heap size downwards to 402M value (the highest one above 448M that it was before that works), I feel this is better than 512M heap size, as I was getting a noticeable lag with 512M heap.
The reason it matters is that the braindead kindle app apparently prelinks some internal library to an address that heap spills into when it's above 402M, but less than 500 or so (where it's relocated at a totally different place in the address space). There's really no excuse for having prelinked libraries in an app, I think.
Click to expand...
Click to collapse
It should migrate into the CM/Nightlies eventually.
leapinlar said:
I can confirm that those edits make it so my CM10.2 (8/30) on emmc runs the Kindle app. It would crash until I made those edits and rebooted.
Click to expand...
Click to collapse
It works on my Nook HD+ now, so I am curious if it is just me or these same changes might work on others CM 10.1 and 10.2 installs.
I have been trying a variety of build.prop modifications in order to try and get greater compatibility for my Nook HD+ to run apps which I have purchased from the Google Play Store and report that they are incompatible and cannot even be sideloaded. To that end I have downgraded my emmc CM install from 10.2. to 10.1 0813 version so that I could run an app called "Resolution Changer" that I purchased from the Google Play Store ( it has already helped me get DeadSpace running ). I also changed my Device/Brand/Manufacturer to get BackStab to sideload, but I originally loaded the 10.1 0812 because the Kindle App still worked with it. On my install however, the changes made to the 0813 version of CM10.1 made it more stable, so I was trying to get the Kindle App to work with that...
( Note: the following is a copy of the text I posted in the "CM10.2 updated 9/01" thread. )
verygreen said:
Known problems:
- Kindle app forcecloses.
Changelog (for sdcard builds only):
2013/08/13 - cm-10.2-20130813-UNOFFICIAL-ovation-sdcard.zip
- Fixed mounting of internal storage
- Fixed reboot to recovery
- USB quicksettings restored
- wifi sleep fix (from upstream)
- Dalvik vm settings adjustments
The changelog for CM-10.1-20130813-NIGHTLY-ovation.zip for the emmc version states:
device/bn/ovation
99298a5 Merge "Reduce Dalvik vm settings a bit" into cm-10.1
Click to expand...
Click to collapse
The Kindle App worked on the 0812 emmc release of 10.1 but not on the 0813 emmc release of 10.1, so on the assumption ( I know it is a bad idea to assume anything but... ) that it might be something simple I edited my build.prop on my 0813 emmc install to change the Dalvik vm settings back to the 0812 parameters....
It is now working on my install, so I wanted to know if the same changes might make it work on CM 10.2 - 4.3 as well ( since it carried forth the modified Dalvik settings ).
rhyang said:
Discovered by process of elimination that the build.prop tweak which is effective is this one :
dalvik.vm.heapsize=512m
The other two don't really seem to matter.
Click to expand...
Click to collapse
MY ORIGINAL CHANGES
What I changed in build.prop ( restored to 0812 values ):
dalvik.vm.heapstartsize=16m ( this was changed to 8m in 0813 )
dalvik.vm.heapgrowthlimit=192m ( this was changed to 128m in 0813 )
dalvik.vm.heapsize=512m ( this was changed to 448m in 0813 )
So by increasing the settings back to their pre-0813 values the Kindle App began to work.
So, maybe verygreen can tell us which one(s) actually fix the problem...
I HAVE been messing with my build.prop for other reasons, but these were the only changes that I made between the Kindle App not working and working....

Thanks for the the details. I just installed the CM 10.2 from 09/03 nightly and I can confirm my Kindle App does NOT work. Kind of disappointing because that's mainly why I bought the Nook to read my magazines and books.
I was not able to find any stable 10.1 versions, all nightly. So I figured I might as well install 10.2 nightly. This is my first install. Followed the CM instructions on XDA.
I dont know what emmc is, but I do know now its part of the nightlies so I should have it.

brooklynite said:
Thanks for the the details. I just installed the CM 10.2 from 09/03 nightly and I can confirm my Kindle App does NOT work. Kind of disappointing because that's mainly why I bought the Nook to read my magazines and books.
I was not able to find any stable 10.1 versions, all nightly. So I figured I might as well install 10.2 nightly. This is my first install. Followed the CM instructions on XDA.
I dont know what emmc is, but I do know now its part of the nightlies so I should have it.
Click to expand...
Click to collapse
verygreen's change is in the CM10.2 09/04 nightly, and for any before that you have to edit the build.prop file...
All emmc means is the internal memory, as opposed to an external sd card.

i loaded up the build from 09/25/13, yet the kindle app still crashes for me. does this still apply to fix the issue?
thanks!

scottjl said:
i loaded up the build from 09/25/13, yet the kindle app still crashes for me. does this still apply to fix the issue?
thanks!
Click to expand...
Click to collapse
Yes, but as you may have read I am now using a dalvik heapsize of 384m instead of my original 512m. The 512m size works for almost everybody that still has issues with the Kindle app crashing, but the 384m seems to be the sweet spot for me on this device. My tab is now buttery smooth...

thanks.. i ended up with setting the following:
dalvik.vm.heapstartsize=16m ( from 8m )
dalvik.vm.heapgrowthlimit=192m ( from 128m )
dalvik.vm.heapsize=384m ( from 408m )
and kindle no longer crashes. i haven't noticed much else.

scottjl said:
thanks.. i ended up with setting the following:
dalvik.vm.heapstartsize=16m ( from 8m )
dalvik.vm.heapgrowthlimit=192m ( from 128m )
dalvik.vm.heapsize=384m ( from 408m )
and kindle no longer crashes. i haven't noticed much else.
Click to expand...
Click to collapse
I only change the last one now, and leave the first two as is...
On my tab Kindle opens faster with these settings than ever before ( a lot of things are definitely faster for me, but I was running with 512m all this time... ).

thanks. i changed the first two values back. kindle still runs with the heapsize set to 384m.

Related

[KERNEL] [WIP] Quickie "Screamer" 0.2 STABLE for Froyo!

First off - I must acknowledge that that code this came from, is not mine. All credit goes to Geniusdog254, fat-tire, mbm (irc advice), and those who have committed to their branches; i would like to eventually make my own branch, but for now, this is a great start. Hopefully this is ok with them - if not, i will happily take it down.
UPDATE AT YOUR OWN RISK.
So, for all those lucky 2.1 users, you have have a nice overclocked kernel. Well, today lucky 2.2 users get the same enjoyment! Just as a teaser - Quadrant gives a score of 1618
0.2:
950Mhz: http://www.mediafire.com/?mbfnt3i39cz8q9o
900Mhz: http://www.mediafire.com/?opmajiyx1puf11t or http://www.megaupload.com/?d=AQKPIPHR
Changes:
***ROTATION IS FIXED***
Original Kernel base proved unstable for the Froyo build. So, went back to basics, and modified the original Nookie Froyo Kernel, as found here: https://github.com/fat-tire/nook_kernel
Future code will be branched from this for the time being.
Built two different kernel speeds, for those whose systems dont like 950.
0.1:
http://www.mediafire.com/?aoadpgt2foxhby9
Compiled from https://github.com/fat-tire/Quickie, as of 1/18/11.
Kernel defaults to 950Mhz
Kernel made compatible to 2.2 standards, with other minor fixes (as noted in Github
To Install:
[Pre Install]
Wipe Dalvik Cache
As suggested here: http://forum.xda-developers.com/showpost.php?p=10749287&postcount=12, it is best to wipe the dalvik cache (if this is not the first boot of the system,). To do so (after connecting your nook to a PC):
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
This can also be done in root explorer.
[Install]
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
[Tested on]
I have tested this Kernel on both a fresh copy of .5.8, as well as the custom .5.9 as posted here: http://forum.xda-developers.com/showthread.php?t=922324
[Recomendations]
Get SetCPU (from this friendly forum!), and change the governor to on-demand. It is currently defaulted to conservative for battery, but OD should give better performance.

Future & Reserved:
Ideally, i would like to build on this kernel, and add features other kernels have, such as different governors, BFS, and HAVS. I don't know much I can actually do, but as time goes I am sure i will learn more. Please be patient with me, and remember this is a WIP. While i am not new to coding, I am new this kind of kernel work, so I am still picking up things here and there..
Issues -
Quadrant is stupidly picky. I am not sure what i did to get it to run when I did, but the best i can say s to keep trying. Right now, it seems to really hang at 2/4 on the I/O.
I believe the default governor is set to conservative; i recommend downloading SetCPU and setting it to ondemand.

Woot Saw the IRC work and couldnt wait.
And i was going to say the wait at 2/4 on I/O was like that before
1607 Quadrant score

Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.

kassemja said:
Tried kernel, got one boot noticeable speed up. second boot failed, now back to standard. can't wait to this matures. great work... perhaps it may help if you clear out davlik cache via root explorer before reboot. i didn't and could not as i'm running from emmc, hence can not use clockwork recovery to clear cache.
Click to expand...
Click to collapse
Just boot a copy of nookie froyo from a mircosd and mount the /data partition from the emmc to delete the davlik cache. That's how I was making changes to nookie froyo when I was running it off the emmc. Once hardware decoding for media is supported I will put NF back on the emmc. Can't wait till clockwork supports froyo. I will be all over this!
Nook [email protected]+Nookie=Awesome

Not working on my Froyo'ed Nook
Divine_Madcat said:
To Install:
Right now, nothing more than replacing the old uImage with the new. You will find the old uImage on the SD card under /boot. Before you do ANYTHING, make a backup of your old uImage, just in case you want to go back.
Click to expand...
Click to collapse
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA

xyzolog said:
Hi! It sounds really promising.
I've tested but it failed I've taken the SD card off from the Nook, then mounted it my Linux box (in /media, the default for Ubuntu 10.10), made a copy of /media/boot/uImage, copied the uImage file I've downloaded into /media/boot, re-inserted the SD card in the Nook and relaunched it...
... I get the 1st "Loading..." message (the one well centered), the screen goes off then back on ant stays like that: blank dark screen with the backlight on.
When I restore my previous uImage backup, my Froyo'ed Nook comes back to live.
Any idea? TIA
Click to expand...
Click to collapse
Same thing happening here.

Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.

I have used the 950 kernel on 2.1 for about a week no issues. I'm happy to test again with a davlik cache wipe. On the way to work now. So hopefully you can post new build by then.
Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Sent from my Nexus S using Tapatalk

Divine_Madcat said:
Just curious, have either of you tested the 950Mhz kernel in the stock eclair build? The problem sounds suspicously like the system not handling the overclock.
However, I am working on some stuff (specifically, fixing the rotation issue), and hope to have some updates soon.
Click to expand...
Click to collapse
Yes. 950 Mhz ran fine for me. The 1Ghz though did not.
I didn't do a Dalvik cache wipe first. When i get a chance I'll try that and give it another go.

deitiphobia said:
Same thing happening here.
Click to expand...
Click to collapse
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...

jasoraso said:
I have the same thing happening - flashing loading; then the screen going blank, but staying on ... after about 2-3 retries, I can get it to boot. As long I keep it booted, I don't have any more problems.
Been running the 950 kernel w/ 2.1 no problems ...
Click to expand...
Click to collapse
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot

watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
Gave this a shot, hopefully this helps!
EDIT: first two reboots > boots fine!

watzone69 said:
Same thing here as well. I got it to boot after 5 tries. It helps if you hold the power button a little past the "Loading...".
After that I wiped dalvik-cache and it reboots fine now.
Code:
adb shell
cd /data/dalvik-cache
rm *
reboot
Click to expand...
Click to collapse
I can get it to boot every 4th or 5th time, but only into instability. It will crash shortly thereafter for one reason or another. Currently it's bootlooping, but NOT off the SD card and Nookie Froyo, it's bootlooping off of the internal memory and 2.1.
I think I'm going to give up on this for now till a more stable solution is reached.
My 2.1 is still running fine at 950Mhz though despite not being able to get this to work for Nookie Froyo.

FOr anyone interested - There are two new Kernels posted, based off different (more stable) code, with one built at 900Mhz, and the other at 950. Please test and use, i think you will find them more stable than the previous..

Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer

Homer_S_xda said:
Excellent, trying the 950 now. I couldn't get the 900 to download. I just keeps looping.
Homer
Click to expand...
Click to collapse
Download from the server? Or working on the nook?

Divine_Madcat said:
Download from the server? Or working on the nook?
Click to expand...
Click to collapse
Cannot download it from the server. The 950 was fine, but I could not get the 900 zip from the server.
My NC/NF is rocking 950! Cleared the Dalvik cache via Root Explorer, powered off via QuickBoot, swapped the uImage (after backing up the NF 0.5.9 one and verifying that my backup worked) and powered on. Booted on the first go and it already seems snappier. In the About Phone the kernel now shows as
2.6.29-omap1
[email protected] #2
UPDATE: WOW just wow! Dolphin HD is actually usable now, it was really dragging before. When this gets stable from the internal memory it will be amazing.
Excellent!
Homer

Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!

Divine_Madcat said:
Homer - not sure why its doing that, but i put up an alternate mirror just in case.. but it sounds like you don't need it.
For everyone who is trying it - please drop some feedback. I really want to learn and support this kernel, but can only do so with feedback. Thanks!
Click to expand...
Click to collapse
The alternate server worked fine. I dl'd the 900 version just in case. Will you be trying a 1GHz version?
Also, any chance you can figure out how to implement IPtables? I'm dying to get proxy for wifi working at least near to how it works on my iPod touch. I can't get over the fact that Google really doesn't seem to want to get into businesses with Android.
Homer

Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]

Q&A: [ROM-1.2/GRJ90] CM7Tab for the GTab (based on CM7 Nightlies) [Update: 08-15-11]
MOD EDIT: THIS IS THE Q&A SECTION FOR [ROM - 1.2] CyanogenMod 7 nightlies for the GTab
ALL Q&A FOR THIS ROM HAPPENS HERE.
Thanks.
---------------------------------------------------
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.43 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
1) latest version of CM7Tab: CM7Tab build 08082011 (Nightlies changelog)
2) Test CM7Tab with 4950 drivers: Test Build 08152011
Changes in modified version
1- replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2- vold.fstab is setup as sdcard for internal storage & emmc for external card
3- using pershoot's 2.6.32.43 GB kernel for 1.2 bootloader (For more info, check his blog.
4- Read_ahead_kd increased from 128 to 2048.
5- Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6- Replaced Camera libs & apk to stop the 8-bit pixelling.
7- Increased dalvik.vm.heapsize to 64m (07102011)
8- Set some values to improve video playback (07272011)
9- Changed values for lowmemorykiller minfree in init.rc (08072011).
10- changed EMMC to microsd (08072011)
11- updated ROM up to 2.3.5 (08072011)
12- Camera fix (08082011)
To-do list:
1- remove some apks (such as Rom manager) & create a removed apks folder.
--------------------------------
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified): Latest build: Build 07262011 (Changelog)
If you have suggestions/ideas, do not hesitate to share them.

thank you.

Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App

nelomen said:
Going to give it a try, tried cm7 a while ago and was great with it but seemed a bit slow. On Iluminate now do I have to flash back to stock?
Sent from my Android Illuminate using XDA Premium App
Click to expand...
Click to collapse
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.

Icewyng said:
As suggested, I have decided to make my own thread for the Cyanogenmod nightlies and other ROMs. It will make things a lot easier in the long run.
Disclaimer: as with the other Roms, Use at your own risk! Since the CM7 nightlies are basically an ongoing beta, you run the risk to brick your Gtab if you are not careful. Use to learn NxFlash first before attempting to flash ROMS. Also, do yourself a favor and get Titanium Backup! Always backup yours apps/settings and wipe data/cache/dalvik before flashing.
These will be using the bootloader's 1.2 Pershoot's kernel (2.6.32.42 / 1.4 ghz Kernel) for GB. This ROM works with the Gtab and should work with the ZPAD altough I have no confirmation of this yet.
Thanks goes out to: Team Douche/Cyanogenmod Devs for making a great ROM, Zyhong for showing me how to update to 1.2 and a few more tricks, Maxdamage for taking the time to compile the nightlies for 1.1 users, Pershoot for making such a great kernel and Roebeet for being the one that inspired me to take my journey down the Android rom lane.
Issues:
1) Once you set up DSPmanager, it force crashes.
1) Vanilla CM7 nightly (only vold.fstab was modified):
Latest build: Nightly build 07112011 (Changelog)
2) Modified version of the ROM: CM7Tab build 07102011
Changes in modified version
1) replaced DSPmanager.apk with a previous version that is known to work (7.0.3) (if you open it, it FCs)
2) vold.fstab is setup as sdcard for internal storage & emmc for external card
3) using pershoot's 2.6.32.42 GB kernel for 1.2 bootloader (For more info, check his blog.
4) Read_ahead_kd increased from 128 to 512.
5) Set up overclocking by default and battery saver script + cpu governors via userinit.sh (from Zyhong's ROM, based on Caulkin's scripts).
6) Replaced Camera libs & apk to stop the 8-bit pixelling.
7) Changed values for lowmemorykiller (07102011).
8- Increased dalvik.vm.heapsize to 64m (07102011)
RC1 version of the rom with changes: 7.1.0 RC1 with Pershoot 42 kernel
(Sorry if this is short but I will improve the thread as it goes)
To-do list:
1) remove some apks (such as Rom manager) & create a removed apks folder.
2) change the EMMC to Sdcard2
If you have suggestions/ideas, do not hesitate to share them.
Click to expand...
Click to collapse
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.

Icewyng said:
How long ago did you try it? I try to play areound with CM7 with the CM7tab ROM to see if I can speed it up a little as well. You can give it a try and tell me what you think.
Click to expand...
Click to collapse
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Edit: have been trying for a couple of hours now but sent me in to boot loop had nvflash back to stock, will give it another shot once this silly Tap n Tap is finished loading.
Sent from my SAMSUNG-SGH-I997 using XDA Premium App

rob_z11 said:
personally I have been using your build for a while and quite happy with it except the market which sometime shows my apps and other time it doesn't. I have not tried any market fixes yet, so it is partiality my fault as well.
Click to expand...
Click to collapse
Dalingrin was kind enough to provide a fix that seems to resolve most of the problems with market (including buying apps). It was merged in build 07092011+ so give it a try and tell me how it goes.

nelomen said:
I tried it today but was getting a lot of fc's, it did seem a little faster then I remember except the boot up was really slow as I remember. I did not give it a full try because I failed to wipe everything because I was at work and wasn't really supposed to be on it. I will do it again tonight with full wipe and see if it gives better results and let you know.
I just realized you have a tab build so I will try that one. The one thing I noticed right away with cm7 is that my tablet looked like a phone and I have been jumping around from HC roms and got used to a more tablet specific rom. I will give you update in a few hours I think.
Click to expand...
Click to collapse
The FCs you were getting were probbly from DSPManager. It is a known issue that seems to come from a "broken pipe" in one of the libs. For now, it is best just to remove it.
For the bootup, someone suggested moving apps to the SD card. Apparently, it would speed up the process.
I am conscious that 2.3.4 is made with phones in mind but it is a step up from Froyo and having partial hardware acceleration helps.

Just tried again and got stuck on CM7 logo boot loop, this was with the CM7 tab build. did full wipe of cache, dalvik, and user data. Not sure what happened. Restoring to Illuminate rom if you have some ideas on how or what else I can do to try this rom let me know.

Hey there Ice.
First off, awesome work on this and thank you for taking the time.
I would recommend editing the build.prop file to set the Manufacturer to HTC. This fixes the playback issue with Netflix (Chipmunk). I tested this out fully on my gTab last night and it's the ONLY setting that needs to be modified. Aside from that, everything seems to work.
Good work!

Hi
Has anyone tried installing volume+ on this rom? I'm on BL1.1 CM7 rom but volume+ does not install. If this works, I'll take the bold step to upgrade to BL1.2.
I don't know if it's just my hardware. My gtab's speaker is very soft and I want to try cranking it up with volume+ (which works on my phone running cm7).
thanks a lot.

DroidTV phone size not full screen....Anyone have other apps that did that after....
I was using DroidTV, and it was full-screen and then rebuild my G Tab with the cm7tabl-0710200-1.2 and when I reinstalled DroidTV it is now phone size display on the G Tablet.
I used Titanium Backup to restore the app and the settings. Anyone have issues like this with an app that did that after re-installing after a full rebuild? Any build.prop setting or somewhere I could check?
Thanks. Steve.

Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.

Icewyng said:
Thanks everyone for your feedback.
@Mike: I have heard of this before and wasn't sure if anyone would be interested in it. I will change that on the CM7Tab version in the next few days.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
@Artful: I will look into this. It might just be that the rsolution isnÈt set right. I will let you know how it goes.
Click to expand...
Click to collapse
Thanks Ice. Other than that I have yet to find any major issues that in the build.
Other than apps that open portrait only with the bottom on the side with the power button. Tried to say to not rotate 90 degrees but they still open that way Apps that open landscape then won't rotate to the 90 degree position but portrait apps still open that way
This is the most stable I have used and performance seems good. A co-workers has the same build, I installed it for them since they are techie-challenged, and theirs is turtle slow because I think they have Skype running all the time.

Icewyng said:
Thanks everyone for your feedback.
@Vhend: Yes, Vol+ works on 1.2. You enter CWM and it works great here.
Click to expand...
Click to collapse
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!

vhendsume said:
sorry for not being clear. I did not mean pressing the volume+ button. i actually meant this app to boost the volume of gtablet.
http://forum.xda-developers.com/showthread.php?t=1023433
I guess the app has dependencies on dsp manager, that's why it did not work on my B1.1 cm7. Since you have replaced the dsp with a workable one in your rom, I would like to check if the volume+ app works here.
Appreciate your work on the rom!
Click to expand...
Click to collapse
Actually, I think it has more to do with a problem with one of the audio libraries. I did a logcat and it seems something called AudioFlinger can't set a parameter properly.
If anyone can fix this, I can send the logcat to help out.

I wanted to apologize for not being able to upload the new nightly today. I had to rebuild my computer and took the opportunity to switch to a new Linux distro. Just tested the new system and all is great.
I will post Build 07172011 later this morning.

Where are the nightly's getting posted now? Thanks and this is the most stable MOD I've had on my G Tab.

Do video apps work as far as no rotation with Oovoo, yahoo, reelportal, etc? Audio work okay with chatting?

mirrors:
http://dev-host.org/cops0ujuwmm0/update-cm-7.1.0-smb_a1002-07182011-1.2.zip
http://dev-host.org/8xjvaysomd1i/update-cm7tab-07102011-1.2.zip.zip
-deck

1.4.3 and application compatibility, reparted 1.4.2 to stock 1.4.3

here is situation:
1. I had rooted 1.4.2 with not blocked OTA and my NT updated to 1.4.3.
2. It is obvious that root and some apps stopped working and some of them even disappeared from the device (like WinAmp for example).
3. I rooted 1.4.3 with SDcard method and it looked like things are fine until I started to get my apps back.
4. I used FIREFOX as a main browser with 1.4.2 update and after registering at Play store on rooted 1.4.3 I read that FIREFOX is incompatible with my device!!! What the hell?
5. Also, my NT registered at Play as NEW device, not the old one as I had - so it seems my serial changed or something has changed in the build.prop or somewhere else in the identification part of device.
6. Besides, after root, i started installing apps and it seems Notification bar has some sort of glitches - it does not clear all the messages and keeps the last downloaded file in the list...
Can anyone point me how to fix incompatibility issue?
---------------
Now, second situation:
7. I reverted back to 1.4.2 with the img file from this post: http://forum.xda-developers.com/showthread.php?t=1663836
8. But the thing is that I want to try 1.4.3 again
9. I downloaded official update from B&N and put it onto the SDCard
10. It boots and progress bar starts to move but at some point (25% of bar) it shows me exclamation icon with '!' and says "Please restart your device and try again..."
What is this issue and how it can be fixed?
Thanks in advance.

Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.

titanshadow said:
Honestly, I have had similar issues with the play store and my Nook on 1.4.3 but if you want to block OTA updates more effectively, I have been told that the updater cannot run if you have CWM flashed rather than the stock recovery image. When I screwed my Tablet up I found that I couldn't get it to load the acclaim_update.zip or any update files until I reflashed the stock recovery image rather than CWM.
Click to expand...
Click to collapse
Can you share the links or files that get your nook back to normal state?
I've been reading and reading a lot the forum but still miss something important. Step-by-step guide would be much appreciated, if possible.

I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?

Nook Color
Eustace2 said:
I have found the same problem. When I run CM7 on the NT from an SD card, I have no app compatibility issues. But when I run from rooted stock 1.4.3, I get the app compatibility error. I even tried pasting the build.prop file from CM7 into 1.4.3 but that did not correct the problem. The same apps are coming up as not compatible. What else is the Market looking at to determine compatibility?
Click to expand...
Click to collapse
This was actually a fix for Nook Color... to modify the build.prop. If you copy/pasted the entire build.prop I would think it would work.
One other thing to do is
1.) manage google play
2.) clear data
3.) uninstall updates
4.) manage google market
5.) clear data
6.) manage google services framework
7.) clear data
8.) reboot
This didn't always work and I had to do this a couple time. Not sure if which step made a difference or what order but it eventually worked. And I could see as many apps as my Captivate (Galaxy I).
Anyway, again, this worked for Nook COLOR and not Tablet. Or at least I havent figured Table yet. If you figure it out. Let me know.
My recent attempt was to copy the build.prop from Nexus and I got black screen after start up. Now I had to unbrick my device and I'm back to square one.
Good luck.. Keep me posted!!!!

@rtabasco - Good plan, but it didn't work. Even when I uninstalled the update and just used the Market app. Looks like 1.4.3 may have changed something other than the build.prop file. I'll keep poking around. It would help if the Play Store would provide a little more detail about the compatibility issue.

This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?

PepeladZ said:
This just gets even more strange...
Restored with 1.4.2 image from http://forum.xda-developers.com/showthread.php?t=1663836 and Google Play (after root with sdcard method) says "FIREFOX is incompatible..."
Also tried to restore with NT_stock_1.4.2_Ribbon_Root_B&N.zip from http://forum.xda-developers.com/showthread.php?t=1494367 and Google Play still says "FIREFOX is incompatible..." Besides 'Go Weather EX' is incompatible too - this is ridiculous.
Anyone has idea how to overcome this?
Click to expand...
Click to collapse
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.

old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ? . The market is your friend.
Click to expand...
Click to collapse
I am set at 160 dpi and that didn't help.

old_fart said:
What is your DPI ? Do you have an easy ( free ) way to try 160 ?. The market is your friend.
Click to expand...
Click to collapse
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?

it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk

PepeladZ said:
You mean - can I access 'build.prop' and change DPI there to 160? I probably can, but why exactly 160?
Why not default "169.33333"? As I understand CM7 has '160'?
Click to expand...
Click to collapse
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.

Eustace2 said:
Apart from the issue we are discussing in this thread that we can't figure out, a lot of compatibility issues with a rooted NT could be eliminated by changing the screen DPI to 160 in the build.prop file. My guess is that most of the apps were written for phones with 800x480 displays (or other dimensions that are easy multiples of 800x480). Making that change had worked for me to get access to most apps I wanted until this most recent problem that has been caused by changes in 1.4.3 or in the Play Store, or both working together.
Click to expand...
Click to collapse
Thanks for explanation. I looked in build.prop from CW7 and DPI there is set to 160. I will try and report if this solved at least firefox problem.
old_fart said:
it took me less than a minute to find this one... please do more searching and reading... thank you !
http://www.youtube.com/watch?v=uKlO9gkmsKk
Click to expand...
Click to collapse
Thank you for video, but I was not asking how to edit text document, but rather what this change will give me.

Well, BNs build.prop has separate settings for X and Y dimensions. Following the logic, it does not matter if DPI is set via one command or via two... Anyway, simply changing to 160 DPI and rebooting did not help me with firefox compatibility in play store as well as other apps that were noted to show incompatible.
Any other suggestions and ideas would be very much welcome!

[Q] Play Store apps incompatible with my device on custom ROM

So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?

lordcheeto03 said:
So as a learning experience, I have been trying to build a ROM that hasn't been compiled for my device. I have already compiled CM10 as a trial run just to test an official build in my environment and make sure everything was set up correctly. Everything works as per the CM10 nightlies for my device. I was able to merge the CM device/kernel files into the other source and get it to compile after quite a few hours (days?) of figuring out and tracing bugs. I was then left with a build that was about 95% functional; device boots up, sound works, no real major problems that I could find. The only thing was that when trying to download certain apps from the play store, they would tell me my device wasn't compatible with the app. In other ROMs which my device is officially supported though, I have no problems with the play store.
I also noticed that my baseband was being reported as "unknown" in settings. Thinking that may have something to do with the play store, I began working on that; tracing down what in CM reports the baseband that just wasn't jiving with the ROM that I was building. After a while, I found the problem and fixed it. The new build now reported the baseband correctly, and magically the play store no longer was giving me errors. Since I now had a version where the major bugs were worked out, I wanted to change the output name of my build and change my kernel source to a different kernel. After changing that to my liking, I flashed that version onto my phone and noticed the play store was again telling me that certain apps weren't compatible with my device. Thinking maybe the kernel swap had busted my progress, I reverted the kernel changes and re-built. Still had the problem. I reverted my output name change (being the only difference now between the build that worked and now) and it was still incompatible. After flashing the new build; which should have been identical to the working build in every way, the play store was still not working correctly. I decided to flash the build that I knew was working... even the original in which all market apps could be downloaded was telling me apps weren't compatible and was acting just like every other build.
I have performed "make clean" after each build, each time I flashed my device I performed a factory reset and formatted dalvik and system. What am I missing? What does the play store use to determine compatibility? I've been told it goes by the ro.build.fingerprint in build.prop; I've tried the values used in CM10 official (which mine was in the first place, using the CM device files), CM9 official, ICS official, GB official... none of them make the play store change it's compatibility message. Also of interest, when telling me my phone is incompatible when surfing from my computer browser, it's listed the exact same as when I'm in a version of android which allows me to download.
What am I overlooking?
Click to expand...
Click to collapse
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app

bizcuite said:
Hi guy.
I dev. a rom actually not supported by cyano.
And i had fixed the pb by add of permissions files in /system/etc/permissions and complete build.prop with parameters from another device who work well with market.
Fyi, i have take sgsi9000 to build my own build.prop file
I hope that will help you.
Bizcuite
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Thank you for your input. I don't know how much of a change there will be using the /etc/permissions files from CM, though I will try it. As for the build.prop, I use the exact same build.prop in CM and the play store works 100%.
EDIT:
I looked at /etc/permissions and the only difference between CM and the one I'm working on right now is that CM has a file called com.cyanogenmod.android.xml. I don't believe that file is needed because I'm not building CM.

[ROM] CyanogenMod 11 Nightly Builds for Nook Color

The NookieDevs are pleased to announce CyanogenMod 11 nightly builds for the Nook Color!
These experimental builds contain the latest changes to CyanogenMod and to hardware support for the Nook Color. As the name suggests, new builds are made and posted (roughly) every day; these builds are fully automatic, with no testing done before posting. As CyanogenMod 11 is still under active development, regressions and general breakage are to be expected in nightly builds!
Highlights:
Linux kernel 3.0.101, plus hardware support from TI OmapZoom's android-omap3-3.0 branch and board support forward-ported from BN kernel releases.
All of the features of CyanogenMod 11, based on Android 4.4. For Nook Color, this brings a reduced memory footprint, which leads to a better all-around user experience.
Full 2D and 3D graphics acceleration using both the GPU and the display subsystem's hardware overlay acceleration (hwcomposer).
Known issues:
Video playback is slower than on previous releases -- this is most noticeable when playing HD 720p video.
Bluetooth is broken at the moment after changes for Qualcomm Bluetooth chipsets were merged into CyanogenMod.
Current releases of Netflix do not work with CM10.2 -- version 1.8.1 is the last version known to work. If you want/need a newer release of Netflix, look into the Xposed mod, which provides a workaround for Netflix -- pastordl has done a nice writeup of the process here.
ART (the experimental Android runtime introduced in 4.4) is not supported -- if you enable it, your system will not boot. (Workarounds may exist, but they are not going to be officially supported either -- use them at your own risk.)
Download:
http://download.cyanogenmod.org/?device=encore&type=nightly
Note that an updated recovery is required to install CM11. ClockworkMod 6.0.4.8 and newer versions should work, as should other recoveries provided the required changes are included. (Ask the maintainer of the recovery if you're not sure.) NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
Source code:
https://github.com/CyanogenMod/android_device_bn_encore/tree/cm-11.0 (device-specific source)
https://github.com/CyanogenMod/android_kernel_bn_encore (kernel)
https://github.com/CyanogenMod/android/tree/cm-11.0 (manifest for the rest of the CyanogenMod source)
Build instructions (discussion of build issues belongs in the development thread)
This release is the product of much effort by many people over a considerable period: many thanks to fattire, keyodi, eyeballer, krylon360, dalingrin, verygreen, iomonster, nemith, cicadaman, deeper-blue, thedude, mad-murdock, j4mm3r, unforgiven512, scepterr, rebellos, ryands, kmobs, tonsofquestions, hashcode, arcee, hacdan, drmarble, mateor, dhiru1602 and many more. Thanks are also due to the CyanogenMod project, upon which we are building, and Texas Instruments, which historically provided excellent support for its embedded platforms to the open-source hacking community.
XDA:DevDB Information
CyanogenMod 11 Nightly Builds, ROM for the Barnes & Noble Nook Color
Contributors
steven676, keyodi, fattire, The CyanogenMod Project, NookieDevs, many others (see post)
ROM OS Version: 4.4.x KitKat
ROM Kernel: Linux 3.0.x
Based On: CyanogenMod
Version Information
Status: Alpha
Created 2014-01-30
Last Updated 2014-05-15

Google Apps; other CyanogenMod builds
Google Apps
http://wiki.cyanogenmod.org/w/Google_Apps
As of 2014/07/25, the latest release for CM11 that is known to work is 20140105. DO NOT use the 20140606 release unless installing to SD card -- it contains over 100 MB of additional bloat and will not fit on an eMMC installation!
If you wish to use another Google apps package, and are installing on eMMC, please note that the Nook Color has what is by modern standards a limited amount of disk space available on /system (440 MB) -- the base system is currently in the neighborhood of 300 MB, so some of the larger packages will not fit. If you're offered different variants, choose the smallest one in order to avoid problems.
Please make sure that you have the correct Google Apps flashed before reporting problems involving the Google Apps (Play Store, Google Keyboard, etc.).
Other CyanogenMod builds
This is the thread for CM11 nightly builds. There are other official CyanogenMod builds for Nook Color available:
Stable releases of CM10.2 and CM10.1 -- these are the releases to use if you don't want to be on the bleeding edge.
Archived nightly builds for CM10.2, CM10.1, and CM10. You may find the last CM10 nightly (20130421) faster than the later releases, particularly during playback of HD 720p video.
Please check that your questions are in the appropriate thread. (If you're interested, there's lots of past discussion in those threads, as well as the development thread.)

Frequently Asked Questions and Troubleshooting
The install fails with errors from "set_metadata_recursive"!
The installation appears to succeed, but nothing's changed when I reboot!
You'll need an updated recovery to install CM11. For CM11 nightly builds from May 16 and later, any recovery that reports itself as ClockworkMod 6.0.4.8 or later should work; other non-CWM recoveries should work if they incorporate the necessary changes to suppor these builds (you'll have to ask their maintainers for details).
For older CM11 nightlies, any recovery that reports itself as ClockworkMod 6.0.3.6 or later should work; other non-CWM recoveries such as TWRP 2.6.3.0 or later should be fine provided the kernel is sufficiently new (you'll have to ask their maintainers for details). NOTE: Do not use ClockworkMod 6.0.3.x builds older than 6.0.3.6, as they contain a bug which may brick your device!
I installed CM11, wiped /data, and now my tablet's been booting for an awfully long time. Is something wrong?
First boot will take at least five minutes, and the boot animation currently stops many times during this process. If you've been waiting more than 10 minutes and it's still not booted up, you probably have a problem.
The soft keyboard keeps crashing!
The Play Store is acting up!
Did you flash the correct Google Apps? If on an eMMC install, are you sure your Google Apps fit on /system?
How do I install this to an external SD card?
See this excellent guide by leapinlar for instructions. It's reported that Google apps installation is broken in the SD card installer at the moment, so you may need to wait for that to be fixed.
What happened to the "Developer options" and "Performance" screens in Settings?
They're hidden by default now in CM10.1 and later. To show them, go into "About tablet" and tap the build number (for CM11 nightlies, it'll be something starting with "cm_encore-userdebug 4.4.2 KOT49H" or "cm_encore-userdebug 4.4.3 KTU84M") seven times.
How do I get the Honeycomb/ICS tablet UI?
You can't -- Google killed it off in Android 4.4.
The lock screen doesn't rotate!
The screen doesn't rotate to the sides I want!
Particularly if you're upgrading from an existing install, you may find that the preferences for screen rotations are incorrectly set. Go to Settings->Display->Rotation and check that "Auto-rotate screen" and (if you want the lock screen to rotate) "Rotate lock screen" are set.
For the allowed screen orientations, selecting 0, 180 and 270 degrees will cover the rotations that you probably want. If you want details:
Android likes to think of the "natural" orientation (0 degrees rotation) as landscape with the N key on the right side of the screen. (This is a change from CM10 and earlier, when we were carrying a hack to change this.) The degrees of rotation are counted in the counterclockwise direction, so in essence, each of the rotation settings allows the following:
0 degrees: landscape orientation with the N key on the right side of the screen
90 degrees: portrait orientation with the N key on top ("upside down")
180 degrees: landscape orientation with the N key on the left side of the screen
270 degrees: portrait orientation with the N key on the bottom ("right side up")
I enabled ART, and now my Nook Color won't boot!
ART isn't supported on Nook Color at the moment due to known issues:
The initial compiling pass that happens the first time you enable ART may cause your tablet to run out of both RAM and disk space.
Many of the Google apps packages for CM11 are incompatible with ART.
If you're currently stuck in a bootloop after enabling ART, boot into recovery and then see this post by fattire for advice on how to restore your system to a working state.
I can't get any of the ROMs or recoveries for Nook Color to boot!
Before you go any further -- are you sure you have a Nook Color and not a Nook Tablet? The two devices look almost identical, but Nook Color (model number BNRV200 -- check the fine print near the speaker grille on the back) has a dark gray bezel, while Nook Tablet (BNTV250) has a light gray or silver bezel. The two devices are not interchangeable -- Nook Color software will not boot on Nook Tablet and vice versa.
If you've got a Nook Tablet, you want to be in the Nook Tablet forums instead.
I'm having a problem with my Nook Color running CM11.
That's not a question
Okay, I'm having a problem with my Nook Color running CM11 -- is there something I can do to troubleshoot?
Glad you asked! Please check the following:
Does the problem occur with a clean install of CM11? This means wiping /data and not restoring a Nandroid backup afterwards. Don't restore system apps and/or their data in Titanium Backup either (user apps/data are okay).
Are you overclocking? If so, does the problem occur when you set the maximum clock speed to 1000 MHz or below? To be clear, we are not interested at this point in bug reports of any kind that happen if you have the maximum CPU speed set above 1000 MHz. If you're experiencing system crashes or "sleep of death" (SOD), you may also wish to try capping the CPU clock speed to 800 MHz (but if this helps, please report your problem here and fill out the hardware survey).
Do you have any patches, custom kernels, or other tweaks applied? If you do, does the problem occur without those applied? (We're not necessarily going to ignore bug reports from patched or tweaked systems outright, but it can make our job harder, and we do need to know what changes you have applied to judge whether or not the change might be relevant to your problem.)
I'm having no luck with the suggestions above. What information should I include with my bug report?
When reporting a problem, please include the following information if at all possible:
Full description of the problem -- "it crashes" doesn't count. How do you trigger the problem (or does it occur by itself)? What exactly happens when the problem occurs? How often does it happen?
For problems with apps or specific pieces of the system software: we'll almost certainly ask for a logcat of the event, so you'll save everyone some time by including it.
For problems involving system freezes, crashes, or SOD: if you can connect to the tablet via adb while it's "unresponsive", please provide dmesg and logcat output from that time. If you cannot, try power-cycling it while it's still plugged into USB, and provide dmesg output from immediately after the reboot, plus the contents of /proc/last_kmsg if that file exists (let us know if it doesn't).
For unexpected reboots: provide the contents of /proc/last_kmsg from after the reboot.

Now that everyone has squared me away (in the 10.2 thread) on the you-need-CWM-6.0.4.5-to-flash-CM11 issue, I hafta say, after 2-3 hrs, this CM11 is quite good! No hard numbers, sorry, but seems reliable, faster than 7.2, and, of course, the UI is vastly better. Waytago steven676, keyodi, fattire! Thanks!

Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V

volpo222 said:
Hello everyone,
To run off of an SD; I created a new SD (sandisk 8gb) with the latest image from Leapilar, the nightly and suggested GAPPS (gapps-kk-20140105-signed.zip). There were some error messages from the GAPPS (they scrolled off before I could really read them). The NC booted to the desktop but there was no play store.
Any ideas?
Thanks,
V
Click to expand...
Click to collapse
If your errors match the ones reported on the SD installer thread:
bowguy said:
I then tried to install the 2014/01/05 gapps package using your/verygreen's script and saw this message:
"Hangouts.apk exists but is not a regular file" The script died at this point and shutdown. After booting, you cannot add a google account as it appears it is a very incomplete gapps install.
Click to expand...
Click to collapse
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.

deleted

Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.

tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Just DOOOO it
(not that I'm encouraging you one way or the other)

steven676 said:
If your errors match the ones reported on the SD installer thread:
then it's the bug mentioned in the FAQ -- it looks like the SD installer needs an update.
Click to expand...
Click to collapse
Yes that's it then.
I hope this gets worked out. 4.4 was very smooth and worked well.
V

Thanks guys just flashed it and so far this looks great, I'd say it's smoother than 10.2 and multitasking is just a bit better. Couple of small issues came across were rebooting to recovery doesn't work for me it just reboots, also had a soft reboot and after it booted up the systemui kept crashing and wouldn't let you do anything, but a regular reboot fixes it.

Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.

tp2215 said:
]
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.

tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
bowguy said:
I found out how to enable ART on the Nook Color. When you select ART as the runtime in Developer options, the tablet reboots but gets stuck in a bootloop. The problem is during bootup, a lot of files are being converted but the Nook runs out of memory. Then it crashes, reboots and tries again and never gets past it. However the boot animation takes a lot of memory during this process.
Solution: Disable boot animation. What you need to do is open the File Manager app. Go to settings (lower right icon) and General Settings. Under Advanced, Access Mode, select either User Prompt or Root Access mode. You need to alter a root file. Any prompts you get make sure to allow superuser access.
Now navigate to /system touch on build.prop and open with "Editor". Add the following line to the end of the file:
debug.sf.nobootanimation=1
Save the file and exit File Manager.
DO NOT ENABLE ART NOW!!
First make sure you did this correctly by rebooting your nook. Make sure you DO NOT see the Cyanogen logo when it boots up - it will take a while with a blank screen and then go to your standard lock screen. If you see the animation logo, you did something wrong, try again.
Now you can enable ART in the Developer Options. When it reboots, wait a while (2 min?) then you should see the optimizing apps display. A basic install with gapps has about 85 apps to convert. This will take a while.
Report back with results!
Click to expand...
Click to collapse
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.

tp2215 said:
Just flashed in it looks great! Feels MUCH smoother and snappier then 10.2. Minor issue that boot take a long time. It seems to me like the boot keeps freezing but eventually continues. No force closes or anything. I am trying now to enable ART and play with it a little to see if it drasticaly improves it. It seemed to make a little bit of a difference on my S3.
Edit: You may want to add to the op, DO NOT enable ART. It sends it into a reboot loop.
Click to expand...
Click to collapse
fattire said:
Yeah, actually steven, if someone has issues with ART you might wanna link here. You can recovery from an ART bootloop w/o reinstalling or anything weird.
Click to expand...
Click to collapse
Yeah, release noted and added to the FAQ. We'd known about this earlier, but it slipped my mind when I was writing up the release notes
bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
Be aware that this may not work for you if you've installed to eMMC on a Nook Color with a 1 GB /data partition -- disabling the boot animation saves RAM, but won't prevent you from running out of disk space to store the ART compiler output (the "oat" files).

bowguy said:
We are working on it. There is a modification pending that might fix this but hasn't been tested yet.
Click to expand...
Click to collapse
If you compiled cm-11.0 with width 480 boot animation, ART will work. Initial boot and optimiziation will be longer than with Dalvik. You also get smoother boot animation. Also, revert boot to landscape in kernel config while you're at it.

tp2215 said:
Just curiuos if anyone has an oppinion to how cm11 is running on the device. I originally flashed cm10.1 when I first rooted and it ran INSANELY slow and laggy, probably due to the low ram etc. But was forced to run CM7 and it ran perfectly and have been running it ever since. I know that 4.4 is supposed to have lower dependencies for running on older/slower devices but anyone got some input on just how good it runs? I am going to probably try it later on tonight, it will just take me a while cause i got to backup my sons game data first or hill kill me.
Click to expand...
Click to collapse
Same here - both 10.1 and now 11.0 are slow. I was hoping a clean install and CM11 would cure the slowness.
I am at work and don't have my nook with me so will have to gather data tonight. its been along time since I even turned on the nook so I am no even sure what my memory config is.
But AWESOME work all you nookie devs!

For those that need them, here are flashable zips of CWM 6.0.4.7:
EMMC Recovery: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-signed.zip
EMMC AltBoot: http://techerrata.com/file/eyeballer/twrp/cwm-6.0.4.7-encore-ALT-signed.zip
Also, I've built an updated TWRP 2.6.3.0 which is compatible with CM11 and would appreciate some testers to confirm everything is working, please see here and report feedback in that thread only: http://forum.xda-developers.com/showthread.php?p=49886829

wifi bug
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.

ibilln said:
Only issue for me so far (on the 1/29) is that if I set settings/wifi/advanced to "keep wifi on during sleep/only while pugged in" it won't re-connect when waking up. Have to re-connect manually. Leaving wifi on permanently for now.
Click to expand...
Click to collapse
drmarble posted a patch in the dev thread, so you can fix it if you're building yourself.
Sadly, the official nightlies aren't fixed yet. So I can confirm this known bug
I also had a reboot while displaying a gif in QuickPic. When it came back, the default launcher was reset and its init messages were shown
It's the first reboot I ever had on CM11. I attached the last_kmesg for your troubleshooting pleasure. I hope there's something valuable in there

Better Mobile App

welcome