yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] derekr:
Does anybody know why the directory .android_secure on my SD card is emptied every time I install a new nightly? It means that I lose 4 apps each time - Alkido reader and the three flavors of Angry Birds. I can save the contents and restore after flashing but it's a royal PITA. Otherwise the installation goes fine.

Thanks.

Edit: It just gets weirder! I took the SD card out and looked at it on the PC. All the files were there! So, I replaced, rebooted NC and looked at the directory with Astro - empty. Apps not functional. All other directories on the card were there and correct. Took card out again and looked at with PC just to confirm, all present and correct with proper date stamp. Put card back in and rebooted, and voila apps are functional, and the missing files are visible in Astro.

I would suspect the SD card, but the same thing was happening on another card, and this is a new card purchased on Sunday (A-data 16 GB) for this very reason.

___________________

- Derek
[Nook Color Android Development] Oskiee:
Quick question... Why are wallpapers from the gallery pixelated horribly? The stock Wp's from CM7 dont come out that way? What can i do to fix that?
[Nook Color Android Development] Divine_Madcat:
Use the app QuickPic - something about the way Gallery sets the wallpapers never seems to get it right. Using QuickPic, you don't have the issue. Sadly, i know of no fix for gallery.
[Nook Color Android Development] jessesse:
Is the theme Chooser included in this version of cm7? I can't find anything on it...
[Nook Color Android Development] Chahk:
It's a theme with an "invisible" preview and mangled name, first on the list.
[Nook Color Android Development] Jiggity Janx:
I had noticed some funny stuff happening with this as well. There is a .android_secure on my emmc partition and at first it had the files in it and later it did not. I haven't mentioned because for stability of use for now I am still running RC4 with 3/31 OC kernel so do not have the most up to date nightly and kernel.
[Nook Color Android Development] Dhyneland:
I just got my NC this weekend, flashed CM7 and Dalingrins Kernel. I am loving this thing! Quick question. I am able to reboot into recovery from the Rom Manager app, but when I hold the power button and select Reboot then select Recovery it just reboots back into the ROM. Is there a fix for this? Thanks!
[Nook Color Android Development] Divine_Madcat:
I have had the same problem, and simply resigned myself to using the rom manager app. Not sure why it doesn't work, but i haven't seen a fix of any kind.
[Nook Color Android Development] lechiffre:
I've had that happen too. My workaround was to install the apps onto the internal memory, seems fine now.
[Nook Color Android Development] :
Been an issue forever. Not sure if it'll get fixed or not... :P
[Nook Color Android Development] nattiboy2326:
I just got cm7 supersonic. I'm liking it a lot it seems to have my battery life up a lot.
[Nook Color Android Development] newellj79:
Nope. Just have to use rom manager.
[Nook Color Android Development] GrillMouster:
Using the same microSD that I used to flash CM7, I flashed MisterMuffin's zip found in post #1 of the official CWM 3.0.1.0 thread on this forum. That replaced the recovery kernel (different from the ROM kernel, like Dalingrin's OC kernels). From what I understand, ROM Manager can't update the recovery kernel.

When I want to boot to recovery from a powered-down state I hold down the power + n button and continue holding it down for three or four full seconds after the "Touch the Future of Reading" screen appears. If I let go of the power + n button too early, it boots normally, rather than going into recovery.
[Nook Color Android Development] jessesse:
How does cm7 compare performance wise on the nook from the evo?
[Nook Color Android Development] jessesse:
Sorry it was a yes or no question and your answer makes no sense to me
[Nook Color Android Development] jaybert45:
Theme Chooser is in your app drawer...once you open theme chooser his response will make sense, as long as you have downloaded the .apk and installed.
[Nook Color Android Development] Chahk:
Misread your question. I thought you couldn't find the theme itself in the Chooser. Sorry.
[Nook Color Android Development] jessesse:
Thanks guys.. I'm always on top of the evo forums and this is going to take some time catching up here :D
[Nook Color Android Development] bekyndnunwind:
Running 18c and its GREAT :)
[Nook Color Android Development] mkm1126:
Which govenor do you recommend?
[Nook Color Android Development] Nburnes:
I prefer Interactive with min being 600 and max 1100.
[Nook Color Android Development] bekyndnunwind:
I'm using Interactive and it seems to be the most responsive. Had it on the default Performance setting and it was pretty smooth, was getting 2150 in quadrant, then switched to the Interactive governor and it went to 2550. Homescreen transitions etc seem smoother, but could just be in my head...
[Nook Color Android Development] chisleu:
Interactive is much more quick to up the clockrate than conservative/on demand.

Performance doesn't lower the rate at all. That is it's only benefit.

Quadrant is a highly variable benchmark. People have gotten as low as 2100 and as high as 2600 with THE SAME SETTINGS.

The governor shouldn't be doing anything else. No voodoo involved, as much as it seems to be, given quadrant's score variance.

I use interactive 300/1100. I turn on performance for benchmarking for slightly more consistent (if synthetic) results (theoretically. haha)
[Nook Color Android Development] chisleu:
http://review.cyanogenmod.com/#change,4707

New wallpapers in next nightly
[Nook Color Android Development] JeremyNT:
I'm running the latest nightly and my notification power Widgets have gone AWOL despite being enabled in settings . Anybody else see this or am I off to reinstall land?

Sent from my NookColor using Tapatal
[Nook Color Android Development] ungarisch:
Did you change the theme? That requires a restart for the power widget to comeback.
[Nook Color Android Development] :
Weird install Process on CM7 final

I installed CM7 final on my Nook Color last night, and had some weird issues. So I format the system, data, and cache partitions, and then when I select the factory reset in Clockwork Mod, everything freezes - can't select anything in recovery. I reboot and all is well. I wipe the partitions a couple more times, then flash CM7. When I flashed the gapps, it said something about being unverified, then aborted. I toggeled the verification in Clockwork, then flashed again no issue. When I take out the SD card and reboot the nook, it boots as if it still had the Barnes and Noble software on it. Booted into "Touch the Future of reading," then the N logo. After that, it said it had a software error, and to reboot. I reboot again, and then it booted into CM7. It seems to be running fine now, if a bit sluggish. It's interesting to note that I rebooted again just to see what happens, and the "Touch the Future of Reading" appears again, but then it boots into the CM7 splash screen. Also, when I connect the Nook to a computer, 2 drives pop up: the SD card inside my Nook I use for extra storage, AND the standard Nook internal memory folder called MyNOOKcolor. It contains all the stock folders like My Files, B&N Downloads and so on.

Any ideas what could have gone wrong? Upon further reflection I think I should have wiped and deregistered the Nook, then booted into my SD recovery.
[Nook Color Android Development] mazook98:
A) You're adding a step you don't need...(no need for "select factory reset AFTER formatting")...

B) I've never "wiped the partitions a couple of more times", and these extra steps may have caused you to accidentally mis-step...One thing I DO make sure of that has always helped me is to make sure that my SD card is NOT mounted right before I flash anything TO EMMC...May be overkill, but it's the way I learned and has ALWAYS worked, so checking your mounts is a good habit to get into. (the only thing that could or should be mounted before a flash to EMMC is /cache/..)..Lastly,

C) Your "signature verification check" is set to ON..when it should be OFF...should solve that.....

D) All of the above won't get you CM7 if your flashable version of CWM is not the right one....make sure of that, and you can do a "factory to Cm7 transformation" in a few minutes...signing in to the market and DLing all the extra Google stuff will be the longest step...

p.s....WIPE DALVIK LAST right after making SURE your SD is unmounted.....CWM will crash.....it just does....no problem...hard power down, power on, and you are done..If you flashed GAPPS, you will see a market icon in your app drawer...go here first and Google walks you through the rest...once in a while after flashing GAPPS, the icon doesn't populate...it's flashed though...just use the file manager included in CM7 to navigate to /System/Apps/ and click on Vending.apk...same difference.

Hope this Helps.

Sent from my PC36100
[Nook Color Android Development] :
Thanks a lot.

So, do you suggest I try to reflash CM7? After I wipe partitions you're suggesting that I unmount the SD card and then flash CM7 and gapps?
[Nook Color Android Development] mazook98:
It won't be mounted after formatting system/ data/ and /cache/....just check between your flashes....then lastly..after All Flashes, unmount Sd, wipe Dalvik...power off..power on..

Sent from my PC36100
[Nook Color Android Development] :
So, boot into recovery, wipe partitions, flash CM7, flash gapps, unmount SD card, wipe delvik, turn off nook, power on nook.
[Nook Color Android Development] mazook98:
Exactly this...I also check my mount status between flashes.(after CM7 flash, and before Gapps flash, I always unmount sd to make sure I am not flashing right back onto SD..may be moot, but like I said, definitely doesn't hurt, and always knowing where you are mounted is a GOOD THING....) if you are adding a custom kernel, add after gapps flash, or simply add later..if you add another kernel later, remember to wipe dalvik AGAIN after flashing.

Sent from my PC36100
[Nook Color Android Development] miniaturepeddler:
Rather strange, when I flashed nightlys lately it has disabled my gapps, requiring me to reflash the gapps and do my signup again. I didn't use to have to do this when updating via nightlies
[Nook Color Android Development] :
I followed these steps, and it still says "touch the future of reading" before it boots. I dunno what else to do.
[Nook Color Android Development] gordon1hd1:
That is normal. I always had that since i been flashing CM7 (since nightly 15). It always show up right after boot, then go to the CM7 boot screen...
[Nook Color Android Development] mazook98:
Agreed...always there...nothing wrong....in fact, that's the screen you hope for...since we leave the eclair boot partition alone...that's included...Go ahead..touch it.

Sent from my PC36100
[Nook Color Android Development] newellj79:
If u have done it right it will always say that.
[Nook Color Android Development] oldman_58:
As long as you see that you can "un-bork" tablet if anything goes wrong..
[Nook Color Android Development] :
Thanks for all the confirmation that it is normal, guys. A tutorial I watched on flashing CM7 to the internal memory did not have that boot screen. I thought I did something wrong. And ok, I will touch the future of reading :)
[Nook Color Android Development] Dhyneland:
I searched and did not see anything about this. I am used to using Amon-RA recovery, so Clockwork is new for me. When I select to clear dalvik cache it doesnt look like it does anything and just refreshes the screen. Is this normal behavior? I know when I clear the dalvik cache on my EVO it takes a little while.
[Nook Color Android Development] :
It happens. Flashing between kernels, sometimes it hangs on click, sometimes it just goes back to the menu instantly. IDK what's up...
[Nook Color Android Development] Divine_Madcat:
Correct. The wipe happens pretty quickly, so if it does hang, just give it a minute, then hold the power button until the device shuts down. Then you can just start it up normally again. when doing any series of flashes, it is by far the easiest to keep the dalvik wipe till the end...
[Nook Color Android Development] painter_:
I always wipe the cache and dalvik first before I do a Nandroid, then I flash.

I noticed some devices have a #42 build but we did not. I wonder why?
[Nook Color Android Development] 12paq:
I did not want to clutter the kernel developer thread, but does anyone know if the wifi drop issue has been put to rest? I have not been able to reliably use the latest test kernels due to frequent wifi internet drops. I am almost positive I have my Nook and device settings correct, but never say never..

Thanks to everyone who has worked so hard on this build! We have one hell of a reader now.
[Nook Color Android Development] chisleu:
Most people haven't had any trouble what so ever which makes debugging an issue.
[Nook Color Android Development] 12paq:
Yeah, if thats the case I understand. I have seen dalingrin mention it as well as a few other people's posts, so I thought I'd ask. I do understand these are test kernels and as stated in the OC kernel op, they are not expected to work for everyone, so thats cool I get it.

If anyone with better skills then me, (lol :rolleyes: ) who would like to take a look at this, I can predictably replicate the issue by just changing kernels and if a logcat would provide any useful data I could pull one.

Thanks again.

Edit: fyi, this issue is getting a bit more traction over at the oc kernel thread
[Nook Color Android Development] wethead4:
is there a way to get the nook ereader software on CM7 similar to the nookie froyo? i know you can download the app, but nookie actually has the "n" you can hit that takes you to the actual nook software
[Nook Color Android Development] britoso:
Can someone on the latest build (41 currently) let me know if video (hardware) playback is perfected yet... thats the only reason I'm on froyo.
[Nook Color Android Development] 12paq:
Its been very usable for a while now, perfect? Even my quad core pc has a hickup or stumble now and again, I would say 99% but your milage may vary. Maybe read the last several pages of the oc kernel thread so you can make you own call. :)
[Nook Color Android Development] britoso:
Yes the hardware acceleration was fixed some time ago, but there was still an issue with a/v sync. Is that fixed too ?
[Nook Color Android Development] dalingrin:
AFAIK, there are no A/V sync issues with hardware accelerated videos. The only time I've seen A/V sync issues is when the video is decoded in software and too high of a bit rate or resolution for the CPU to handle.
[Nook Color Android Development] wethead4:
bump. can anyone help with this?
[Nook Color Android Development] chisleu:
Video is perfect in the 4/18C test kernel and higher. There is a 4/23 kernel now which is 1.3ghz and seems to be most excellent.

Anyone else notice this?

Something on the task bar flashes every once and a while. It's like an icon appears for a split second and goes away. Any ideas? My eyes can barely recognize that something is happening, but I can't seem to get it to happen when my cones are updating. I see a flash, not an object. haha.
[Nook Color Android Development] painter_:
Does anyone know why almost all of the other devices have newer nightlys then the encore? They were all built on the 4/23 the nightly we had is 4/17.

Since the buildbot is hidden I can not look.
[Nook Color Android Development] tj!2k7:
zOMG, you saw it too! I've been seeing the same UFO (Unidentified Flashing Object) for months now.
[Nook Color Android Development] ylixir:
Yeah, it annoyed me at first, but I'm kinda used to it now. No idea what it is though, just a flicker out of the corner of my eye, never been looking straight at the notification bar when it happens.
[Nook Color Android Development] oldman_58:
I think it is the satellite dish for gps...
[Nook Color Android Development] adma84:
I was making a build for you guys, but it fails here

res/drawable-mdpi/wallpaper_prash_revolutionary.png:0: error: Resource entry wallpaper_prash_revolutionary is already defined.
res/drawable-mdpi/wallpaper_prash_revolutionary.jpg:0: Originally defined here.
make: *** [out/target/common/obj/APPS/CMWallpapers_intermediates/src/R.stamp] Error 1

Nothing like failing bc of wallpapers...
[Nook Color Android Development] khaytsus:
Yeah, same. At first I thought it was the full screen hide button as it flashes in and out periodically but it seems to do it fairly slow. The other seems more like a notification icon and it bumps everything over for a microsecond.

Maybe someone will be looking in the right spot one day and recognize it :)
[Nook Color Android Development] duoxx:
I caught a glimpse of it, and I think it's the fat battery icon (for me) because I set the battery to display the percentage instead.
[Nook Color Android Development] ADude:
The precise answer to the question is : The person who did it for Froyo.

I've never seen one person mention it in reference to CM7.

Does it work for the freebies ?
[Nook Color Android Development] dalingrin:
Can you be more specific. I don't know what you are talking about? NF has support for the stock B&N software?
[Nook Color Android Development] adma84:
New Afternoonly Posted

This build is made from CM GIT repo, right from source. Only change to source is disabling security check on EAS policies. If you guys request it, I will take that out.

This includes all changes identified here up to and including

Build Name: update-cm-7.0.0-encore-adma84-20110423-signed.zip

md5: f55f9e88390cf02824cb85854e319646

'Thank me' if you find this useful. You could also sign up for dropbox at the link below if you want to thank me.

Usual Disclaimers

It's always best to download nightlies from CM repos, not from some random crazy on the forums (with that said, enjoy this build :-P)

These are highly experimental, this build might not even work! (just like a nightly)

Always nandroid backup before Updating

Always nandroid before updating

wipe cache and dalvik cache for good measure (likely unnecessary, but a good idea)

check md5 hash and redownload if it doesn't match my posted hash

Thank the real devs (dalingrin, fattire, etc) I just build these for you guys, I am not providing development assistance at the moment

Grab Dalingrin's OC kernel if you want, you can get it here: Dalingrin's OC Thread

Yes, you can flash this right over your nightlies

Yes you can flash a nightly right over this

You can find my builds in my twitter link below, follow me to keep up with the builds

Nandroid backup before flashing

I do not always get a chance to test builds so post your results for everyone!

Download Link: http://www.multiupload.com/FDRQDMGEJR
[Nook Color Android Development] painter_:
Dude, that is an excellent post! You answered all of the questions people would ask.
[Nook Color Android Development] adma84:
thanks. let me know if you have any problems with the build
[Nook Color Android Development] khaytsus:
erm, just in time for 42/7.0.1 to release any time...
[Nook Color Android Development] painter_:
Flashed with out problem.

Thanks again, I hope they get the issue fixed that is stopping the buildbot.
[Nook Color Android Development] dalingrin:
Its already fixed and 7.0.1 stable will be released shortly.
[Nook Color Android Development] adma84:
thanks for the heads up.
[Nook Color Android Development] glenairlie:
Build #54?

How did we go from #41 to #54 in the nightlies?

http://cm-nightlies.appspot.com/?device=encore
[Nook Color Android Development] ADude:
Maybe the numbers 42,43,44,45,46,47,48,49,50,51,52 and 53 are considered bad luck ?

I don't remember an elevator stopping at those floors. :eek:
[Nook Color Android Development] deadbot1:
A good question was asked on the general forums. Can the internal storage be altered to use the whole 5Gb, effectively doing away with the mount point at /mnt/emmc? This would allow apps that can't see the mount point to use that space.
[Nook Color Android Development] EverythingNook:
im wondering the same thing...
[Nook Color Android Development] chadamir:
Whats the new overlay that's mentioned in the changelog?
[Nook Color Android Development] 12paq:
You don't?

;)
[Nook Color Android Development] sigma0824:
Home Button Long Press - Open Keyboard

I would like to setup a custom home button long press action. I would like it to open the soft keyboard. Anyone know how to accomplish this? Maybe a way through soft keys or button savior? Thanks.
[Nook Color Android Development] TJNooker:
Wow, huge change log for 54! This looks like a significant update.
[Nook Color Android Development] variable47:
42-53 failed to build for the Nook. Somebody finally noticed and fixed the build.
[Nook Color Android Development] dalingrin:
No :rolleyes:

Most builds went from 41 to 51 and then to 54. We had 1 nightly fail to build not 11. :p
[Nook Color Android Development] Narfx:
Yeah, I assume it didn't take THAT long to notice that simply converting wallpaper_prash_revolutionary.png to wallpaper_prash_revolutionary.jpg would fix the compilation error :p

BTW, Isn't there anybody else annoyed by the badly nine-patched expander_ic_maximized.9.png and expander_ic_minimized.9.png? It's been like this for as long as I remember:

instead of:

I've been replacing them automatically in my build script by the correctly nine-patched ones I made since CM7 came out, so I forgot about them, but I tested today with the original ones to see if they had been fixed... and they haven't.

Is it only me? :confused: Or people simply don't care about those trivial things? :p
[Nook Color Android Development] variable47:
Oops. I stand corrected. :)
[Nook Color Android Development] psychoace:
Ok this is pretty crazy but I just installed nightly 54 and now CM7 is running really poorly. First the app drawer in ADW EX is hardly scrolling. It might move a row or two if you try to flick to the bottom. Second (which might actually the problem causing the app drawer situation) the calibration for touch is back to being awful. When I play Glow Hockey my paddle ends up flying everywhere on the screen. Last I lost Live Wallpapers. I double checked to make sure I didn't flash an old nightly but when I look it says 42311 nightly. It seems I'm the only one who is having this problem though. I am going to make sure I didn't have some crc error with the downloaded file.

Oh and I am running Dalingrin's l4/23/11 kernel which was working fine on nightly #41
[Nook Color Android Development] 12paq:
Try downloading again and reflashing after checking MD5s. ;)

Whenever I have trouble like this its from not waiting several minutes for a new rom to boot up. As you probably know a new flash needs several minutes even after it looks like its booted up, to write all the new system files.

...when I'm the only one having problems, its usually me or my system. 'Usually me' happens a lot to me lol. :)
[Nook Color Android Development] psychoace:
You don't think I need to wipe or anything?
[Nook Color Android Development] xBryan:
wiping wont hurt
[Nook Color Android Development] adma84:
I think we all prefer that you would.

jk ;-)
[Nook Color Android Development] psychoace:
The people behind me in line will thank you for that.
[Nook Color Android Development] jabrams:
Animated Wallpapers Missing in Nightly 54

Anyone else missing animated wallpapers in Nightly 54? I am also running my NC @ 1300Mhz!!! Thanks to the latest OC Kernel =)
[Nook Color Android Development] psychoace:
Yup, seems like Live Wallpapers was pulled.
[Nook Color Android Development] oldman_58:
I extracted missing files for the 7.0 release and at least have a few working live wall papers.

The files missing from /system/app are:

LiveWallpapers.apk

LiveWallpapersPicker.apk

Did not restore all of the missing live but a few..
[Nook Color Android Development] yanger:
So it's safe to nandroid + flash 55, or should I nandroid + cache + flash 55? wipe shouldn't be necessary if coming from cm 7.0 stable?