yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mateorod:
First off: The new touchscreen drivers from keyodi are definitely making a big difference in my first-wave Nook! When I tried to move a cursor to a certain spot while typing, it used to jump lines, sometimes five or more. It made editing things like XDA posts a real chore. I have seen my cursor jumps reduced to no more than a character since I updated my kernel! I believe that is from the new drivers and I am real happy with that.

Also! I was posting in another thread and had a thought. Those of you who are reporting the wifi reconnect problem: how many of you are using either the "community tweaks" or V6 supercharger? If I am not mistaken the community tweaks do what the V6 certainly does, which is increase the wifi scan interval to 180. The "tweaks" may go even higher, I think maybe as high as 300 seconds. I just bet if we're having connection issues, the first suspect should be end-user alteration of the settings.

I know that pressing scan does not seem to help the issue, so it would seem to not be part of the problem. I use the V6, but realty consistent internet (unless I am repo syncing :mad:) so don't often have the problem. But the times I have, the wifi says it is connected, when really it s disconnected. It doesn't seem to rescan until I convince the nook it truly has no internet, either by toggling wifi on/off or in airplane mode. So perhaps it doesn't scan the current connection when it thinks its connected?

Just a thought, and one I haven't looked into at all. Like I said, it isn't really that big of a problem for me. For those having the issue, try lowering the scan interval in build.prop or using ROM Toolbox and see if that helps any. The only reason to increase the scan interval is battery cost, which dalingrin has assured us is negligible.

*****

I would have put this in the CM9 user thread and tried to leave this thread for more development-level issues, but it seems that bell has been rung. But it has seemed to really cover the same issues over and over. I am not volunteering for the job, but does anyone else think we could use a wii or at least a Q&A sticky? I am as guilty as anyone, but the same ground is getting covered, over and over again, in at least three separate threads, if not four. Any enterprising person think they're up to it? I am sure Leapinlar could use a break from almost single-handedly keeping people up to speed.
[Nook Color Android Development] HacDan:
A wiki already exists. Feel free to edit it here.
[Nook Color Android Development] mateorod:
Hmmm. Yeah, I was thinking more like the user CM9 experience, as in " I just flashed Samiam's build, but why won't Chrome work?" and so forth. The nookdevs portal is great, but I don't see a lot of that stuff there. And something on the site where those questions are actually posted seems like a good idea anyway.

But of course, your larger point remains, that if I think it should happen I should go ahead and do it. Which is of course true. It's just that I have been real busy overclocking the kernel.

You know, something like 1500.:eek:
[Nook Color Android Development] cybertimber2007:
Back to the topic about fattire's recovery and it not flashing properly - I did just breifly see an error pop up at the end. Something about /tmp/updatescript line 122 ... backup.sh or something.

Edit: Hey leapinair, thank you for the suggestion about CMR on SD as the alternate. I see what you mean, that it's seperate from fattires. Now I saw you said you can't flash nightlies from it... but can one flash other things, like the bootanimation.zip ?
[Nook Color Android Development] Nburnes:
Why do that? Back in early CM7 days, anything over 1200 was found to hinder performance.
[Nook Color Android Development] jskolm:
So what value are people actually overclocking to with ICS? What's stable?
[Nook Color Android Development] RETIEF:
safe overclock speed

It seems to me that 1100 is about the max speed without seeing problems. I use interactivex governer at 300 min and 1100 max. It takes a bit longer to speed up, but then I get decent batter life.
[Nook Color Android Development] mateorod:
Ummm...1500= joke.

HacDan works on kernels and has been frustrated by requests for that number before. No confusion intended, although I should have known better.

I keep it around 1100 or 1200 depending on how I feel the nook is performing.

I swear, my original plan was to try and get the thread back on topic. As you were, people.
[Nook Color Android Development] dc52317:
Reboots and screen flashes

Anyone getting reboots or screen flashes? I am running from SDCARD, and version March 14th. My screen will turn on and off while just sitting on the table. I checked to make sure no sync attempts, and I have wifi off, but it will flash on and off every so many minutes.

I have also noticed the last few nights that when I charge at night and I turn on in the morning the nook rebooted, and is now on the EMMC Nook stock boot up.

Hmm

Will a flash update to the newest version fix some of these issues?
[Nook Color Android Development] cpkroboth:
OK.. so i have been checking back on CM 9 regularly to see progress, and decided what the heck.

Downloaded the latest build, GApps, boot animation fix, and telephony fix... Ect...

After backing up

Booted to recovery wiped and formatted System and Cache. Installed from ZIP and the install went real quick.. Like less than 20 seconds. Rebooted saw new Cyanboot (which is sweet by the way) then no boot animation, just hangs. (I am installing to EMMC)

I have run through the process twice, and both times same result. So I tried CM7 to see if anything else was messed up, and it boots perfect.

EDIT: I just tried the process from SD CARD Recovery and same results. Color me puzzled.

Any suggestions? Or did I miss something in this thread?
[Nook Color Android Development] Nburnes:
Don't need the boot animation fix anymore.
[Nook Color Android Development] DizzyDen:
Additionally... if you format system... the first flash seems too quick... try flashing again... something in the scripts has been causing an issue when checking version for backup on install.
[Nook Color Android Development] cpkroboth:
Thanks for the reply. I got it. Finally found a similar reply a few pages back. Flashed a Rom from before the 10th, then the newest. Back in business. :)

The support from the community here is awesome.
[Nook Color Android Development] leapinlar:
Just don't wipe /system next time. The new nightlies do not like that.
[Nook Color Android Development] Android311:
When over clocking to 1300mhz is that pretty pointless?
[Nook Color Android Development] cpkroboth:
Got it. Just odd that it happened when I was moving from CM7 to CM9. Seems wiping system in that case would be essential.

Thanks Again.
[Nook Color Android Development] leapinlar:
It's not necessary. The installer does it for you. And with the new nightly installer, it screws it up. I can think of no reason ever to wipe /system before installing a CM nightly. It always formats /system itself before putting it's files there. Even if installing over stock. Sometimes it's necessary to wipe /data though (especially coming from stock.) And wiping cache or dalvik cache is beneficial.
[Nook Color Android Development] deathsycthehe11:
So if I'm coming from Phiredrop 7.1 to this, I wouldn't need to factory? All I basically need to do is wipe cache?
[Nook Color Android Development] leapinlar:
A factory reset is different than wiping system. A factory reset via CWM wipes /data, /cache, sd-ext if you have it and any apps installed to SD. It does not wipe /system. You might want to backup your apps with Titanium Backup and then do a factory reset before installing the nightly. But you could install it without doing that if you want. If things don't run right you can factory reset later. Do NOT wipe system.
[Nook Color Android Development] deathsycthehe11:
Just wondering, how stable is this rom? Are most of you using it as a daily driver? Is there any bugs I should know? I've been playing with my Galaxy SII and HP Touchpad, and left my Nook Color on a shelf for a while.

I did search for posts related to stable and daily driver but most of them were pretty old.
[Nook Color Android Development] leapinlar:
I am now using it as my daily driver. I think many here are. I use the non-opengl version. I find the open-gl version to be laggy and tends to crash occasionally.

The version I use is very stable and gets better all the time. The devs keep adding cool features. Other than not running video in hd and no netflix, it's pretty good.
[Nook Color Android Development] ryuz4ki:
I've been using it as my daily driver for over a month now, upgrading weekly and have enjoyed the progress so far, I can use all of my reading apps with ease and haven't come across any problems when playing games like Angry Birds or Fruit Ninja, or with any of the Gapps except for having to watch videos on YouTube without HD, which I don't really mind. I would say you would be more hard pressed to find what you can't do over what you can do with this room, install the latest nightly and give your Nook new life!
[Nook Color Android Development] 12paq:
+1

.
[Nook Color Android Development] paleh0rse:
Before I make the leap from CM7, my main concern is the Plex app... has anyone tried it with any of the CM9 builds?
[Nook Color Android Development] Henk Poley:
Is the nightly build in this thread with or without OpenGL?
[Nook Color Android Development] bigbob23:
Without. Eyeballer's thread covers both versions.
[Nook Color Android Development] perakesson:
Hi from Sweden! I just got my first Nook (8gb Color). I love it. Our 4-year old already starts to learn to read using some apps. From stock I immediately installed latest ICS nightly without OpenGL. Result:

- some apps don't run, such as Google Earth

- The launcher is unstable, sometimes I can remove icons (long-pressing) and sometimes I must restart tablet first

- yesterday I started testing Bluetooth pairing to my Think Outside keyboard. Complete success at first try, but then tablet could not initialize Bluetooth second time and froze, had to be revived with hard reset. Strange. Maybe BT on CM9 is buggy.

Probably I will install CM7 instead, despite that Android 2.3 is more complicated to pair with BT keyboards (experience from my ZTE Blade Android phones). First I wanted to skip CM7 because of ugly default user interface, but this can be improved by customizing your laucher. A beautiful CM7 launcher is configured by jgaf here

http://xdaforums.com/showpost.php?p=23628695&postcount=1182

Remaining to solve:

- I want to learn to partition the ROM-so that more than the 1gb is available as mounted volume. On a PC it's so easy to partition Linux volumes, but I have'nt found the tool to repartition Nook ROM...

These are just first impressions. Don't know if this helps
[Nook Color Android Development] AndroidLonghorn:
I can't get Plex to work with the open-gl builds. I haven't tried the non open-gl builds yet. The app opens, but it can't find any media to play.
[Nook Color Android Development] paleh0rse:
Hmmm, that sounds like more of a network issue than anything. Have you tried to login via MyPlex instead of connecting directly to your Plex server IP address?

I just imagined that any Plex app problems with this ROM would be video playback issues, not network connection issues. If it can't even connect to our Plex servers and see the media, that's odd...
[Nook Color Android Development] leapinlar:
Look here for repartitioning:

http://xdaforums.com/showthread.php?p=14101197
[Nook Color Android Development] lekofraggle:
You can also change your mounted volume by mounting the other partition. When you make a bootable sd card, the first partition is the boot partition. When the install does its job, you get a few. The one the install script makes for your "SD" is the fourth partition. Yet, Android looks for the first partition and mounts it as your "SD" (this is because it is set to auto meaning first by default). SO, if you are using a 16 gig card, you have a lot of wasted space.

It has been a while since I have done this, but all you need to do is edit your

/system/etc/vold.fstab file and point it to the 4th partition.

Change the line that looks similar to this ---

dev_mount sdcard /mnt/sdcard auto /devices/platform/mmci-omap-hs.0/mmc_host/mmc0

To this--

dev_mount sdcard /mnt/sdcard 4 /devices/platform/mmci-omap-hs.0/mmc_host/mmc0

You can do this in root explorer or on your computer via adb.

Note, because my cm9 is on the internal card, my line may read differently. Do not copy and paste my code because it may not work. Just change the auto to 4. If it says, "auto auto" change the second auto to 4.

This can be done on the internal setup too if you have a rooted rom on the internal. Although, if you are on a different build (which you probably are), the vold file may look different. There is a little guide on the top. The variables are always in brackets so it will look like this...<auto> in the guide. One last thing is, in eclair, I think the file was called vold.conf.

If you tell both your sd install and internal to mount the same SD partition, you can share files between the two installs. Some apps like Evernote will even recognize the changes automatically as though you edited the files in the same operating system.

Good luck.

~Leko
[Nook Color Android Development] AndroidLonghorn:
Plex is working on my transformer with ics, my atrix and my google tv. It sees the server, but it just goes to a black screen on the nook even with myplex.
[Nook Color Android Development] paleh0rse:
Damn... :(
[Nook Color Android Development] shumash:
Ubuntu 11.10 Repo command

Ok, I'm jumping in to try my hand at building my own stuff, and I'm already stuck at the "repo" command that doesn't seem to exist in Ubuntu. I've done everything else, i.e. the repo script is in the bin directory with proper permissions but no joy.
[Nook Color Android Development] leapinlar:
You may get more help on building if you ask your question in the Work-In-Progress thread. Most folks here don't know much about that.
[Nook Color Android Development] mateorod:
If you've initiated the repo (i.e. curl https...) and changed the permissions (chmod), try opening a new terminal for the changes in your environment to register. Some systems require a reboot.

Try

ls repo

Or

which repo

After reboot. Sometimes bash needs a reboot to register then changed info.

Check to make sure your adb paths (I put platform-tools and tools in PATH) are set correctly. If all your paths are set correctly you should be able to get that info at any location.

And yeah, don't let the board name confuse you. This and the OpenGl thread are pretty much user-end problems only. Wallpaper and Chrome, usually. The build questions have a better chance at getting answered in the [DEV][WIP] CM9 thread.

I'd love to tell you this is the first small problem you have, but it won't be. Don't give up! I learned a bunch doing this. More people should try.
[Nook Color Android Development] shumash:
Thanks for the info. I'm pretty sure that it's an issue with my path and environment variables. I have since learned that, while none of the Linux masters really consider it to be of interest, most things flat don't work if the paths are screwed up. The instructions don't really tell how to properly set the path to all the needed resources (hint, hint....)
[Nook Color Android Development] mateorod:
Ha! I completely feel you there. It can be glossed over or ignored in the resources, buto a newcomer it is the least explained and most likely to be wrong and/or the problem. Oh, I struggled.

Okay, the two things you will NEED to put in your PATH is ADB and Java. If the reboot didn't work for you above, then it is certainly a problem with your ADB path. The PATH environment variable just tells the shell where it can locate a program, permanently. Otherwise you could only run the ADB scripts in the location you store them.

I will show you ADB here. There a couple small points I have seen disregarded other places. ADB recommends that you provide an absolute path. What does that mean? No shorthand (~ is shorthand for, in your case, home/shumash/) and put a slash in front of the location. Like so:

export PATH=${PATH}:/home/shumash/android-sdk-linux/platform-tools

export PATH=${PATH}:/home/shumash/android-sdk-linux/tools

This assumes that your ask folder is named android-sdk-linux and that your user name is shumash. Change the name if necessary. If you need to check if your paths are correct, navigate to /android/system and try

which adb

and

java --version

. If your paths are correct the version should output.

Java depends where it is located, but the syntax is the same. Just look where you have it installed and make sure the program name matches the name of the program. If it is java-jdk-1.6.1 or whatever (off the top of my head) that is what you need to set the path to.
[Nook Color Android Development] shumash:
Great stuff. I'll try it when I get off work. The above is the first time I've heard of using absolute paths; almost every FAQ or suggestion uses relative paths. Thanks!
[Nook Color Android Development] tinpusher1:
So whats new in the latest (update-encore-20120330) nightly?
[Nook Color Android Development] DizzyDen:
What do you mean?
[Nook Color Android Development] tinpusher1:
i mean what has been added and/or fixed
[Nook Color Android Development] DigitalMD:
the changes are always posted here .

http://review.cyanogenmod.com/#q,status:merged,n,z
[Nook Color Android Development] ryuz4ki:
This is a good place to check for what's changed seeing as how this is the ICS branch used on the nightlies.

https://github.com/fat-tire/android_device_bn_encore/commits/ics
[Nook Color Android Development] GizmoTheGreen:
the gapps-sam-noinit has some mac-osx files in it... just a heads up
[Nook Color Android Development] neuroval:
I just flashed the latest gapps from goo-inside.me when I flashed the latest nightly, everything seems to work fine.
[Nook Color Android Development] Samiam303:
Aargh, I thought I'd fixed that. In any case, that's based on an outdated version of the gapps -- I recently set my macbook up to triple boot, so I'll repack the latest one under linux so that the junk files aren't in there anymore and upload it asap.

EDIT: Rather, Eyeballer has informed me that the OneTimeInitializer no longer seems to cause an issue, so I'll just change the link in the OP to lead to the latest ICS gapps.
[Nook Color Android Development] cajunflavoredbob:
Are there any mirrors available? I only ask because the link in the OP to the nightly builds continuously goes down. It has failed 11 times in the last hour. It seems to drop roughly every six to seven minutes. Currently, the 1 April build is hanging at 0.7/116 MB with over 11 hours remaining. It's been about four minutes so far. Perhaps I simply began downloading at the wrong time. It may just be coincidence, but nothing else on my end is acting up.

EDIT: I got up to 8.2/116 this time. It goes quickly up to a certain point, then cuts out, and doesn't download anymore.

EDIT2: My fault after all. My laptop was connecting to the wrong WiFi connection. I'm not sure why my neighbor's connection is even saved in my laptop at all. My connection is twice as fast. Anyway, I fixed it.
[Nook Color Android Development] capnblackleg:
I flashed the same gapps with the new nightly and none of the gapps will open, they all immediately close. Any ideas what to do? I've reflashed and all the usual stuff, nothing worked.

Edit - I was impatient, wiped data and all is well
[Nook Color Android Development] incubus26jc:
Got ahold of a nook color. Thought i would try this build first. Is it a known issue for flash embedded vids to not work? or just me? Yes i have latest flash. Thanks. Hope to contribute to the community in the future.
[Nook Color Android Development] leapinlar:
Flash player and flash embedded vids only work on the opengl enabled version of CM 9. Sam's here on this thread are not enabled. You need to get eyeballers version.
[Nook Color Android Development] neuroval:
The latest nightly (4/4) is only 73MBs? How did it go from 116 to 73?
[Nook Color Android Development] rampart51:
I just looked....its says 116.01 on the website. Maybe you got a bad download.

http://techerrata.com/browse/nightly_kangs/encore
[Nook Color Android Development] boomn:
That link is for eyeballer's builds, not for these builds from samiam. Samiam's site does show a smaller file
[Nook Color Android Development] neuroval:
I just looked and it now shows 87, maybe it's still uploading but really slowly...I last checked several hours ago when it was at 70-something.
[Nook Color Android Development] Samiam303:
I don't know why I had a bad upload last night, but it should be fixed now.
[Nook Color Android Development] shumash:
Put into my ICS 4.04 dualboot racks build, and it makes it fly!
[Nook Color Android Development] psychoace:
Now it's showing up as 61mb's
[Nook Color Android Development] DigitalMD:
Why are you using ADW? CM9 has a great launcher built-in.
[Nook Color Android Development] Samiam303:
I keep making the stupid mistake of rebooting my machine at night without checking that the upload is done. There'll be a fixed one up soon.

Also note that the "fixed" gapps is no longer necessary, and additionally the fix-bootanimation is only necessary if you prefer the old boot animation, as the nightlies now contain the new CM9 bootanimation.
[Nook Color Android Development] grayfoxmg1:
I would like to thank whoever rotated the cm9 bootanimation so that we could have a landscape version. I really like it that way as I normally keep my tablet in landscape orientation unless I'm reading something. So thanks:thumbup::cool:
[Nook Color Android Development] stolenmoment:
I re-installed ADW (free) because Trebuchet wastes so much screen space, and I was used to it. Can Trebuchet handle an 8x8 icon grid yet?
[Nook Color Android Development] RETIEF:
Landscape Bootaninmation

personally, I preferred the portrait one. But the devs can't please everyone.
[Nook Color Android Development] radioraheem:
What specifically doesn't work for you? I've been using ADW EX as my default for a while now and it runs great on these nightly builds.
[Nook Color Android Development] aaplus12:
I have noticed recently that when i try to flash this build on a clean Nook . i.e. after wiping "System" + "data" + "cache" then it fails.

CWM shows that its flashed successfully but it never boots. Is this normal behavior or there is something wrong with my nook?

Appreciate the responses.

Thanks

Sapien
[Nook Color Android Development] eyeballer:
It's a bug with the cm installation script. Coincidentally, I just submitted a fix for it 5 mins ago: http://review.cyanogenmod.com/#change,14651 so this should be fixed soon-ish.
[Nook Color Android Development] TheDave1022:
Why not try Apex or Nova launcher? They are ICS based with lots of options
[Nook Color Android Development] socos25:
Try Nemus Launcher in the market. It is fast, and has lots of options. The smallest memory footprint I have seen of any launcher.
[Nook Color Android Development] jvillejoe:
+1 on Apex launcher! No lag what so ever. Nova lags and so does Nemus. Apex should be built in rather than Trebuchet imo because Apex launcher just seems so much more stable. Thanks for the suggestion Dave.:D;)
[Nook Color Android Development] mulletmandan:
Gah, just ran into this problem--got a black screen after the boot logo after I tried to upgrade from CM7 to CM9. Any idea which of these nightlies I can install without that problem, or should I just wait until your fix gets pushed?

Also, eyeballer, do your nightly builds include this fix?
[Nook Color Android Development] J515OP:
I believe you need a nightly from 3/9 or earlier. You can also flash CM7 again and then flash CM9 right after without clearing /system this time. Search for leapinlar's posts he has commented on this many times.