yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] mooja:
i keep having to manually mount my sd card as r/w in root explorer since installing cm10. i did a clean wipe of system, data, cache, and even the sd card when i installed.

the reason this is a big issue for me is when loadingan app like the nook app, since it cant write the sd card, it just gets into an app reboot cycle. and manually having to mount it as r/w every reboot is a huge pain in the butt.

any tips?

**edit** this is from installing b4. i hadnt tried any cm10 installations before this

**double edit** fixed my sd card issue. looks like there were some errors on the card, so i had to hook it into my computer and run error checking
[Nook Color Android Development] eyeballer:
We need someone that has an ft5x06 touchscreen for some testing.. Can someone come by the #nookcolor channel on IRC?

If you have no idea what IRC is, click the link below, choose a username and say hi :)

http://webchat.freenode.net/?channels=nookcolor

Edit: no longer needed!
[Nook Color Android Development] mooja:
how can one know if they have said touchscreen?

**edit, nm i didnt read the OP**
[Nook Color Android Development] eyeballer:
By reading the first post and following the instructions for filling out our hardware survey :)
[Nook Color Android Development] keyodi:
I guess no one wants to say hi, so here's the kernel -- https://www.box.com/s/jtebn6wpe3z51c4s2j4m

how to push the uImage

adb shell mount -t vfat /dev/block/mmcblk0p1 /emmc

adb push <path to downloaded uImage> /emmc/uImage

adb reboot
[Nook Color Android Development] Myrkrel:
I installed CM10 Beta 4 a couple days ago and things are running quite smooth so far. Clean installed on emmc - full wipe / format including SD. No SODs to report. Many thanks to the devs for all your hard work - you've renewed my interest in using the Nook!

My Nook Color stats:

SN: QI12M97R73Y

Date: 02/21/2011

CPU: OMAP3630 ES1.2

Touchscreen: cyttsp

Launcher: ADW Ex 1.3.3.7
[Nook Color Android Development] 1800collect:
I did. It works when I just use vplayer. But when I use the app or the browser it requests flash instead. This is a problem as I can't seem to get vplayer to noticed my computer when I am not at home, which is the whole purpose of PlayOn. I've narrowed it down to the user agent on the NC not being detected as I used a Nexus 7 user agent with Dolphin and it correctly requested the video player app and not flash. When I didn't it would request flash.

You can read more about my escapades here: http://www.playon.tv/forum/help/general-technical-issues/playon-android-says-i-need-install-flash

If anyone has any suggestions on changing the user agent on the stock browser to a custom user agent I am all ears. I can only figure out how to change to default user agents.

I gave up on using Apex it was too laggy. The stock launcher is much more responsive and I don't get overall slowdown. With Apex it made the whole device very sluggish as it seems to always be running.

I didn't know you were looking for surveys still since I think you asked for that back in B1 and I only joined in B3+. I went and filled it out and noted I was running B4. I'm running cyttsp so I can't help out. :(
[Nook Color Android Development] oppy:
Is this just for the ft5x06 screen?
[Nook Color Android Development] RoboticBuddy:
I don't have the ft5x06 screen, but what does this do?
[Nook Color Android Development] 1800collect:
Dang. I recreated this bug. So someone in the General thread mentioned the Speaker Boost app. I gave it a whirl because I've always boosted the little Nooks speakers.

I immediately got the loud blown out speaker noise. From what I recall last time, I installed Nook Color Tweaks to boost my speakers. But I didn't put the two and two together on making the speakers all wonky. I uninstalled Speaker Boost, but the blown out speaker noise continued. I rebooted and so far no problems so far.

So as a warning if you're trying to boost your NC speaker apps may make everything blown out.
[Nook Color Android Development] marclais:
Laggy?

I have this installed and I like it a lot, but everything is super laggy. Like seconds to get the pull down menu 15 seconds to open apps, etc. Is this normal? Should I wipe and reinstall? If so what are the steps? When I came to this from cm7 all I did was factory wipe, installed this and then gapps. Did I miss a step? Thanks in advance.
[Nook Color Android Development] leapinlar:
That is not normal. You might want to go back to CWM and fix permissions. If that does not help, do a complete wipe including system and flash again.
[Nook Color Android Development] bigrat:
Aside from the already-known "no wake on charge" issue, b4 has been solid as a rock for me. This is with the ES1.2 cpu and cyttsp touchscreen. Nice work!
[Nook Color Android Development] ponyboy82:
Thanks from me as well... I've been having this problem too on CM9/10 builds. It's been a while, but I don't remember the CM7 builds being so slow on my NC. I've been meaning to try another completely fresh install, but was wondering if there was any other solution.
[Nook Color Android Development] bluepen61:
I agree. I liked Apex for a short time, but a couple of full day's use and it was creeping. I uninstalled Apex, rebooted, and rebuilt my home screen.

Otherwise, CM10b4 is cruising along. <like>
[Nook Color Android Development] worldindo1:
Also, since I experienced a similar issue with my battery, if you have CWM (ClockworkMod), you can wipe "Battery Stats". As for TWRP users, you'll need to downgrade or use a bootable SD (I have 2.1.1 on my EMMC Altboot). For a while, my NC wasn't charging past 33% and would actually drain further than that (went down to 14% before I wiped). Hope this helps!
[Nook Color Android Development] 911jason:
Me neither... was hoping this was going to bring back 1.2 oc...
[Nook Color Android Development] derekr:
Just great! Here's a strange wifi issue, I wonder if anybody else has seen it?

I have two routers in my house, and I run them using MAC address authentication. After installing CM10, I couldn't connect to wifi on either router unless I disabled the MAC address authentication and made the networks wide open. Then Nookie connected just fine.

Now I haven't touched the routers for many a month. So I checked Nookie's MAC address in settings and low and behold it wasn't in the access list for either router! I entered the "new" MAC address into both routers but it was not recognised by either. I can only connect if the networks are open.

It appears that the MAC address may be being incorrectly reported in CM10??

FWIW - the MAC address is now reported as 00:d2:8b:43:9f:fd. (Settings - > About Tablet - > Status.) I'm sure it wasn't that on CM7. The MAC address is hardware and cannot change. :) I'll reinstall GB tomorrow night to check it out.

Otherwise JB is simply fantastic!
[Nook Color Android Development] leapinlar:
I had the same issue because I also use Mac address authentication. It is not that the Mac address is reported incorrectly, it is that CM10 changes it. The Mac address on the nooks are controlled by software. Putting the new Mac address in the router is the only thing you can do. When I put the new address in the router it connected fine.
[Nook Color Android Development] That Baker Guy:
we used to have a problem similar to this on the kindle fire. it would only report 1 mac address for all kindle fires so two kindles couldnt be active on the same net work at the same time.
[Nook Color Android Development] derekr:
Thanks leapinlar. I thought that MAC addresses were hardware based so as to ensure they are unique. I'm off to see if I entered the new address incorrectly on both routers...
[Nook Color Android Development] jh1521:
LOL, I finally set my own build environment and compiled my own, and 2 days later this shows up. :) Great timing.

Is there any change betwen this build and one that would have been synced on 10/15?

What I can say about the 10/15 build (compiled locally) is this: it seems a bit unresponsive (there is a split second between an action, like a screen touch or button press, and the result) but apart from that no major issues. Been using it for 2 days now. No SOD or any showstoppers. Of course netflix doesn't work but that's expected.

(edit) I see no commits since 10/15 in either the fat-tire/android-bn-encore repository, nor in the main CM/JB one - so my build should be the same as the released one.

(edit2) except for OpenGL - it is enabled in my build, but disabled in alpha1
[Nook Color Android Development] steven676:
The spec says that MAC addresses are supposed to be stable and immutable by the user, but reality has disagreed for quite a long time now.

Bingo -- it looks like we have that same issue. For reference, we changed wifi drivers when moving from 2.6.32 to 3.0 -- the old driver was a (open-source) TI vendor driver which duplicates a lot of Linux kernel functionality, while the new one is a properly integrated Linux wireless driver.
[Nook Color Android Development] jh1521:
MAC addresses are supposed to be immutable, but the reality is that ever since there have been network drivers in Linux (20+ years now) you can make quite easily any network card report any MAC address you please... :)
[Nook Color Android Development] derekr:
Just to verify, I have spent an hour trying to connect using the CM10 MAC address in my routers (Verizon and Netgear) with absolutely no luck. The Verizon one won't even accept the address, it disappears from the list when I hit the Apply. All my other devices work fine.

I need the MAC filtering to keep the neighbor's kid off my network. :) He's incorrigible!
[Nook Color Android Development] leapinlar:
I have exactly the same Mac address as you so it is the same issue as the kindle fire had. So it is a bug in CM10.

But I don't know why you can't connect to your router. Mine is a dlink router.
[Nook Color Android Development] fattire:
Don't think so.. whatever the build date is, that's pretty much it.

Yeah the only difference might be in whatever was different at that moment in the main CM10 source.

There ya go :) How do you like it compared w/the non-GL build? Congrats, btw!
[Nook Color Android Development] jh1521:
Haven't run the non-GL one yet. The OGL enabled one is a tiny bit laggy, but it isn't too bad. No major problems in 2 days.

Speaking of MACs, it would be cool if one of the developer options would allow for adjusting that. :)
[Nook Color Android Development] RallyStyle2003:
resuming from sleep

After running this for a day, I did find 2 issues I am having. After wakeup with no charging, sound is gone. I checked all volumes and everything looks good. Reboot and it comes back. Other issue is I was charging it and it won't wake up. Had to hold power until it restarted.

Other than that, everything still seems smooth and stable. I'm installing adb now so I can pull logs.
[Nook Color Android Development] pckoloji:
it crashes at first. then i went to google play and login, settings > auto update.

2 mins later google now updated itself and no more FC. it comes with pre-saved settings like my football team etc.

cause i used with SGS CM10
[Nook Color Android Development] boyoboyo:
Lost audio after a while. Not in the middle of audio play, though. Just had woken up the device after almost 24 hours without reboot, and got no audio output in YouTube. Tested in more apps and no result.

Pressed power button and again to awake, but the issue persisted.Reboot (normally) and audio is back.

How can I check what might have caused it?
[Nook Color Android Development] RallyStyle2003:
quick update. I got adb going and am trying some troubleshooting.

I have OMAP3630 ES1.2 and the Cypress display.

I'm leaving the nook on the charger with wifi off tonight and will report back.
[Nook Color Android Development] steven676:
On Nook Color hardware variants ...

While troubleshooting problems, we've discovered there are a few different variants of the Nook Color floating around. Since those of us who hack on the device seem to have similar hardware, some of these variants don't seem to be nearly as well-tested.

It'd be helpful to know which variants are most common (and just as importantly, who has them, so that we can try to maximize our testing coverage), so I'd be much obliged if you could provide the following information, whether or not you're having problems:

Motherboard serial number

Manufacture date

CPU revision

Touchscreen type

You can find instructions on how to get this information in this post (near the top of the thread).

EDIT: eyeballer's set up a survey form for you to fill out here: http://tinyw.in/I4OJ

Thanks!
[Nook Color Android Development] cybertimber2007:
Well... having tested CM10-alpha-encore-fullofbugs briefly last night I can only report one thing... it runs very damn well.

I believe the stability and smoothness I'm seeing so far is a kudos to the long process and build it yourself process.

Fattire, krylon, eyeballer and everyone else... thank you again for your efforts on this. More to come later.

May the CM upstream accept your blessed commits for the better of all... or encore. :D
[Nook Color Android Development] dparrothead1:
Motherboard SN: QI0CM9PMV1G

Manufactored Date: 12/28/2010

CPU Revision: OMAP3630 1.1

TS Type: CYTTSP

Problems: SOD every time device goes to sleep.

BUGS:

HBOGo does not work but Xfinity Player does.

Pandora does not work.

Google Now FC

Google Music is iffy but Winamp and Apollo work

Good:

MX Player

Temple Run - excellent. Couldnt play on 7.2 beause of non responsiveness.

Angry Birds - excellent.

Amazon Appstore

Kindle App

B&N App

Play Store updated to 3.9.16

Portrait to Landscape a little laggy but good.

I am using Nova Launcher. Other than the SOD, everything is excellent for an Alpha!

Thanks again.
[Nook Color Android Development] Jainyankee1993:
Sd card install

Hi, I installed on sd card, and it doesn't get past the boot animation... been stuck on it for quite a while now...suggestions?
[Nook Color Android Development] no_cannabis:
Honeymoon past, now it's back to real life

OK, here's my post-first-day experience.

Yes, the device wakes up dead every time on a stock wall charger. Back-lit black screen and nothing.

As for MAC addresses - my phone's WiFi tether has MAC filtering turned on, and I connected to it immediately after flashing this new ROM with NO issue - the NC's MAC address stayed the same. My NC is out of the very first batches, I bought it right after I saw the first TV ad about color version.

Other than that I'll keep praising your great work, guys - it's an amazing ROM that made me thinking that a "new tablet for Christmas" project may be parked for a while now.

P.S.: It's easier to capture entire dmesg if you issue a command: adb shell dmesg > dmesg.txt
[Nook Color Android Development] eyeballer:
OC is still out for the moment, we want to be sure we have some stability issues ironed out first with the higher voltages. sluo and keyodi have been working on it. However, as we've been testing, I will say that OCing to 1.1/1.2 doesn't really seem to give as much of a performance boost as it did back on cm7 so you guys aren't missing out on much.

The test kernel implemented a newer touchscreen driver but it doesn't seem to work well so it's out again.
[Nook Color Android Development] 911jason:
If the 1.2 doesn't make much difference, why would CM10 feel so much slower than CM9 for me? It's very sluggish compared to CM9 at 1.2...
[Nook Color Android Development] 1800collect:
The blown out speaker effect is back. I'm going to attempt to fix permissions and see if that fixes it.

Edit: Nope it didn't fix it. Waking the device from sleep will put the blown out effect speaker. I really wish I never installed Speaker Boost. I didn't have this problem for days until I installed it.

Edit: So whenever the blown out speakers are in affect videos play in slow motion.
[Nook Color Android Development] lollyjay:
Did you deactivate DSP Manager? If not, it could be interfering.

QI0CM9787SV, 12/11/2010

ES1.2, cyttsp, CM10 Beta 4

Tablet UI, Go Launcher HD
[Nook Color Android Development] lollyjay:
FWIW, I've used the Go Launcher app killer feature to maximize free memory (see screenshot). Never have out-of-memory problems and b4 is smooth as silk.:D. Also useful in Settings is the Kill app back button.

QI0CM9787SV, 12/11/2010

ES1.2, cyttsp, CM10 Beta 4

Tablet UI, Go Launcher HD
[Nook Color Android Development] hwong96:
Check your build.prop file in /system. It may have been permanently altered by the SpeakerBoost app. I have attached my CM10b4 build.prop for comparison.
[Nook Color Android Development] 1800collect:
I compared the two. The only difference is you seem to have a 11-8 build while I'm on 11-6 and you have a density set to 160.

I've disable DSPManager as well to see if that fixes it.
[Nook Color Android Development] hwong96:
Also check CPU setting is @ max 1000 setting. CM10b4 has a tendency to reset to max 600 setting on its own. Could be the reason your video is slow/choppy.
[Nook Color Android Development] alexwick:
is CWR recommendet or does TWRP work as well... just more used to TWRP with my phone... (HTC EVO LTE) ??

any thoughts?

Thanks
[Nook Color Android Development] 911jason:
I just switched to TWRP last week after using CWM for the past couple years. Really like it. Just do yourself a favor and go into CWM and toggle signature verification to OFF before you try to flash it.
[Nook Color Android Development] alexwick:
Is the best way to do so with goo Managers? thats how it was installed on my phone (I believe)..!?
[Nook Color Android Development] marclais:
Thank you so much. It is much better now!
[Nook Color Android Development] 911jason:
That should work fine, but first boot into CWM and make that quick change, otherwise the install will fail.
[Nook Color Android Development] alexwick:
you are talking about rebooting in recovery in CWM correct? I cant find that toggle you are talking about....

should i be booting Emmc recovery or SD card recovery!?
[Nook Color Android Development] leapinlar:
That setting in CWM shows up when you select install zip from SD. And you only have to toggle that when you are flashing a zip that has not been signed properly. If you use goo manager to install TWRP, I don't think you need to mess with it.
[Nook Color Android Development] 911jason:
That was how I tried installing and it failed. Check the TWRP thread and you will see I wasn't the only one.
[Nook Color Android Development] alexwick:
havnt paid mutch attention before where i boot in recovery... but when i select reboot in recovery from the running tablet... I get the pinguin and it tries tyo install something... and than shuts down... now i was able to go to recovery in emmc... is that correct or do I have to go to recovery in SD..? I am not sure if i have to delete a file somewhere... seems like recovery tries to install something... just cant find what... boot partiotion is empty from update.zip... etc...
[Nook Color Android Development] leapinlar:
That means you are on an SD install. You do not want a normal CWM or TWRP on that.

But if you want TWRP on emmc, you need to download the zip to a regular SD (not the one with the ROM on it.) Then boot to emmc CWM and go to install zip from SD. Then select the verification toggle to turn verification off (because teamwin did not sign the zip properly). Then you can choose the TWRP zip to install. This will put TWRP on emmc.

But I am not sure why you want it with an SD install. You can't use it on that. If you want a recovery that you can use on an SD install, go to my tips thread linked in my signature and look at item B5.
[Nook Color Android Development] alexwick:
Ok let me explain.... I had a triple boot before... Emmc original CM7 and CM 9....

for whatever reason i didnt use my nook for a while and when i powered it up... i could not loging to the playstore... and i could not get it fixed....

Ao i decided for a new install... well here I am with Cm10.... My son uses also the original nook for reading books... so i found it easy to install on SD card...

now before (triple boot) I used CWR... and that seem to be standard here as well.... now with my phone (EVO LTE) I use TWRP....

now i just try to update this to TWRP.... where ever this method installs CWR I would guess on the SD card..... OR?

** funny just realized it is your thread I quoted **

please explain... is this not where it is now ? ? just CWR instead of TWRP?

THANKS!

P.s. How can i see any other partition on the SD card then boot? If i try to mount through the nook... I dont seem to get it mounted as a SD card... just tells me drivers are missing... where do i find the correct drivers!?
[Nook Color Android Development] stolenmoment:
I may be the person who mentioned SpeakerBoost; I installed it because DSPManager has no effect on BeyondPod's playback, while SpeakerBoost does, which is something I don't understand. Similarly, SpeakerBoost doesn't appear to affect Play Music.

However, I have no fidelity issues with SpeakerBoost. What level do you have it set to? I have mine at 80%. Are there audio hardware differences among NCs?

More detail: if you configure DSPManager to boost all bands, it gives a noticeable volume increase. I'd been using that in earlier ROMs, but it doesn't work (for BeyondPod only) in CM10. Play Music is affected as expected.
[Nook Color Android Development] leapinlar:
There are two kinds of SD install. The Racks dual boot type which uses a modified cwm to flash things. Apparently that is what you used to use. Now you are using the verygreen single boot system. That does not use a cwm to flash. Look at my tips thread linked in my signature and read items B1 and B8. You will see the difference.

And the only way to look at the other partitions is to use your USB cable and connect to your PC. If you plug in the card to the PC, only the boot partition can be seen.

We really need to move this conversation to my tips thread or my installation instruction thread so we are not cluttering up this thread.
[Nook Color Android Development] majorpay:
Seems all is working pretty good at this point... Only problem is browsers are slow to load and sometimes pages freeze up. Gaming and apps still work great, and nova + widget locker is a win on this Rom.
[Nook Color Android Development] Lttlwing16:
Hey fellas,

Thanks for all your hard work on this.

That said, I didn't know if it was possible to rearrange the format of where the /system and /data preside. Jt1134 moved them around for CM10 on the Fascinate and I have to say the performance is very near that of my n7..

Here is the line from the OP on the thread on rootz..

" I changed partition layout around to move system to eMMC and move data to OneNAND (greatly improves performance"

Didn't know if this is possible on the NC to help improve the butteryness in future iterations..

Thanks again!
[Nook Color Android Development] RoboticBuddy:
I found a bug, whenever I try to enable a keyboard or gamepadder IME through the app itself, the setting gets an FC.