yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] paleh0rse:
Do you happen to have a good link for 0828?
[Nook Color Android Development] koopakid08:
Just download from rom manager.

---------------------------------

If this post helped you don't forget to say thanks!
[Nook Color Android Development] leapinlar:
SOD is still a problem with 7.1 Stable. I just experienced one. You will still need to use whatever workaround you have been using. Since I need wifi on during screen off to keep my google voice texting working, I use software to keep a wakelock on to prevent deep sleep and the eventual SOD.
[Nook Color Android Development] Awats:
See the bottom of the first post.

http://xdaforums.com/showthread.php?t=1297556
[Nook Color Android Development] jonrobertd:
Ok, been using nightly for about a week now, and my nook has seen more use than my computer. Coming from HCv4 this is awesome. I have a couple of questions before I upgrade again, having a few different things done than the last time I did it:

1 Do I need to uninstall Chainfire3d, and/or re-install it after upgrade?

2 I know I have to re-edit build.prop, but what about the IMEI hack?

I figured this would be better posted here than in the new ROM release thread, but if I am wrong I'm sorry mod please move to the appropriate thread.

Thanks guys and gals.
[Nook Color Android Development] SCWells72:
I also had one this morning on 7.1 Stable. Set the Nook down, jumped in the shower, came out, and had to do a hard reset. Out of curiosity, what are the various workarounds people are using successfully? Right now I've set it to turn off wifi at screen off, but I'm obviously still getting SOD, so there must be something else I need to do.
[Nook Color Android Development] BitingChaos:
Issues I've seen with build after build of CyanogenMod:

- Connecting to VPN locks the device (Link)

- Sometimes, rarely (with NO way to reliably duplicate), I get the Sleep of Death (Link)

- "Move to Phone" in Application management and other mentions of "Phone" (developers need to stop calling every Android device a PHONE).

- The device shuts off when low on battery instead of gracefully shutting down. Between 3%-8%, I lose power (this use to be as high as 24% before the patches went into the kernel to correct the battery reading).

General Android annoyances:

- UN-accelerated, choppy interface. Possibly more of an issue with nothing being accelerated in Android 2.0. Maybe 4.0 will fix this.

- Every "launcher" is just horrible:

*) LauncherPro performs well, but doesn't scale correctly with DPI. It looks fine at 240 dpi, but you end up with tiny icons at 160 dpi. It also doesn't handle orientation change correctly (and will draw all icons over top of each other).

*) ADW.Launcher (the built-in one). Performs slow and offers no bells and whistles.

*) ADX Launcher EX. Slow performance.

*) Go Launcher EX. Slow performance, draws menu behind the status bar (why would they do that?).

- no Cisco IPSec support. This has been supported "out of the box" with iOS devices for years, and is no where to be seen on Android.
[Nook Color Android Development] tsddave:
Hmmm strange.Ive never had sleep of death with my Nook using cm7 but ive had it on my Android phones.

I dont get this ungraceful shutdown you mention either and I also dont have horrible launcher issues either.I use Go launcher and I have to say the performance is nice and zippy. I get a short wait while all my apps and games show in the drawer but this is just afew seconds and to be expected when you consider im using a 32gb sd card and it and my nook are rammed with apps and games!

I dont overclock my nook either, I have tried it and for the speed gain I didnt feel it was worth the extra battery drain.

I guess not all Nooks are equal (ive seen this with Android phones also) and I guess perhaps you have been cursed with a bad one.
[Nook Color Android Development] waylo:
Have you tried Zeam? I had ADW Launcher EX on Phiremod 6.2, and it worked fine. After upgrading to 7.1, I'm going to go with Zeam, more for the wonky DPI issues with ADW Launcher EX (can't put any icons/widgets on the upper 1/5th of the screen it seems).

I also find that the status bar process sometimes goes crazy, taking up 20%+ CPU for no reason. Killing it speeds things up, for a while. This happened in Phiremod 6.2, also in 7.1.
[Nook Color Android Development] bigbob23:
I have no experience with Chainfire3d or IMEI, but there should be no need to re-edit build.prop since 160 dpi is now included in the nightlies (and 7.1).
[Nook Color Android Development] jonrobertd:
The build.prop is for nexus s samsung for gameloft games. But while I do prefer 165 on density, I use lcd switcher.
[Nook Color Android Development] leapinlar:
The setting in wifi settings to have wifi off when screen is off is sometimes not enough to prevent SOD. Apparently there is a delay built into that setting to turn off the wifi and an SOD can happen before it gets shut off.

You can use third party software like "tasker" or "green power" to immediately force wifi off when screen is off and back on when screen is on. Responders here have reported success using this method.

I personally need wifi on when screen is off so I use "softlocker" to put a wakelock on the system to prevent deep sleep. Deep sleep with wifi left on is what leads to SOD. No deep sleep is terrible on battery, but I charge every night anyway so I don't mind.
[Nook Color Android Development] ScottyNuttz:
Anyone else been having trouble where it seems like the screen thinks it's being touched in one spot? If I'm playing a game, it will constantly move in one direction, or if I'm using the menu it will not let me input any kind of touch (I can't even shut it down).
[Nook Color Android Development] Ronin3178:
Do you happen to have it plugged in when this happens?
[Nook Color Android Development] koopakid08:
Clean your screen, turn screen on and off, download and run nook screen recalibrate, and then get a screen protector on it.

---------------------------------

If this post helped you don't forget to say thanks!
[Nook Color Android Development] DizzyDen:
1 - If you don't wipe data you shouldn't need to

2 - If you are doing any build.prop edits other than DPI = 160 then yes to both.

The IMEI hack is a modification to framework.jar and will have to be done with every update. Using my IMEI Generator you can edit build.prop and patch framework quickly and easily.
[Nook Color Android Development] Cybore:
Anybody here use shootme or vitalplayer? ever since updating from n177 (i believe that's what I had) to the newest nightlies, and now the latest stable release, they are not working as they should. Shootme gives me a "failed starting server" on startup while trying to access "playback settings" and "functions" on vital player neon pro causes the application to force close. The player plays videos just fine.

Tried several things to address the issue including deleting and reinstalling the programs, fixing permissions, checking super user settings, etc.

Not that big of a deal for me, but makes me wonder if app support is not as good in newer builds or something went wrong in my updating of nightlies. I might consider doing a fresh install to see if these issues go away.
[Nook Color Android Development] jonrobertd:
Thanks dizzyden, this thing is funner than flashin any phone I have.
[Nook Color Android Development] montresor60:
VPN?

VPN has been broken in every nightly since getting my NC (around #150) and it still appears to be the case in the 'stable' release. Connecting to VPN will either do nothing or freeze the device. VPNC works to a point but drops the connection after a while. The VPNC 'prerequisites' check reports that Advanced Routing is not present.

There does not seem to be much discussion about this issue. Can anyone confirm if they have VPN working and, if so, how it is possible?

Could a CM7 dev provide some information about this VPN bug and if anything can or will be done to resolve it, please?
[Nook Color Android Development] swaaye:
I use OpenVPN and it works great. Maybe you could try that. You only need the OpenVPN Settings app but you need to read up on how to make ovpn files to set up connections. I run through ibVPN and they have mostly ready to go ovpn files available so I imagine other places do too. I even managed to have the ovpn file load my login details from a txt file as typing username and password in so often was making me crazy.
[Nook Color Android Development] montresor60:
Yes, I tried OPENVPN; downloaded the files from my provider and followed some instructions I found somewhere to the letter but was not able to make a connection.

I understand that this is one solution that's been confirmed by several people but would appreciate it greatly if you could please post some step-by-steps, if you would be so kind. I'm sure it will help a lot of others who are in the same boat with the standard CM7 VPN.

Running MIUI, by the way, but I flashed the new 'stable' yesterday and got the same result. I read somewhere that Advanced Routing was included in the nightly build dated 20110404 (around #136), so I'll download and test that later (slowwwww day at work!).
[Nook Color Android Development] ScottyNuttz:
Nope.

Thanks for the suggestions. I already have a screen protector, but it's probably worth cleaning it off. I'll also give the book screen recalibrate a try.
[Nook Color Android Development] topcaser:
My NC shows that it uses just 1200 MHz and deep sleep. Is this quite normal?
[Nook Color Android Development] swaaye:
To get the ibVPN ovpn file working I had to edit it and remove two lines at the end, "up" and "down". These commands gave errors and don't seem to be needed with the Android app anyway.

That was all I needed to do. If you are getting other errors please make a forum thread and I'm sure we can help.
[Nook Color Android Development] newellj79:
Is anybody else getting this while trying to initialize the repository? Any ideas?

newellj79@ubuntu:~/android/system$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

/home/newellj79/bin/repo: line 1: syntax error near unexpected token `newline'

/home/newellj79/bin/repo: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'

Posted else where but no help. Can n e one here help?
[Nook Color Android Development] montresor60:
I assume the ibVPN file is the certificate for a particular server, correct?

Not really getting any errors as such. It either appears to connect (although the IP doesn't change) or stays stuck on 'Wait'. My certs don't contain the strings 'up' or 'down', so there's nothing to edit from what I can see. I can provide examples, if they'll help.

Some explanation and discussion of the various OpenVPN options would be useful, particularly the scripting preferences. I guess a new thread should be started as it might help others experiencing issues with their NC and OpenVPN.

I guess my main question is: why doesn't the standard VPN module 'Just Work'? I find it hard to believe that this isn't a problem for a lot more NC users.

UPDATE: There's a happy ending, here. It seems that the problem was due to the way the certificates were generated; i.e. from my PC at work, then copied to the /sdcard/openvpn directory on the NC. I discovered, completely by chance, that the certificates need to be generated on a machine which is connected by VPN to the VPN service provider's web site. When I generated certificates in this way, then copied them to the NC, OpenVPN worked instantly.

So, it ain't the software or the NC. They both work very well.

Thanks again for your help and interest, swaaye. I hate to admit it but I was considering dumping the NC for a (gulp!) Galaxy Tab if this VPN stuff wasn't sorted out soon.
[Nook Color Android Development] lagvoid:
I got the same error trying shootme. Didn't have any problems using it with the CM7.1 RC???
[Nook Color Android Development] Rofa1:
Agree with all the above - no issues whatsoever rather than the short wait as described.
[Nook Color Android Development] ehcan:
This is because of the change to the DPI (from 161 to 160). It appears that several apps does not like this including the B&N Nook app.

I change the DPI on my Nook to 161 and everything is back as it is in 7.1 RC1.
[Nook Color Android Development] newellj79:
When i try to run repo init as taken from the wiki i get this:

jeremy@jeremy-VGN-FW560F:~/android/system$ repo init -u git://github.com/CyanogenMod/android.git -b gingerbread

/home/jeremy/bin/repo: line 1: syntax error near unexpected token `newline'

/home/jeremy/bin/repo: line 1: `<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">'

Can somebody help me? Thanks...
[Nook Color Android Development] dvdivx:
Getting severe FC issues with DSP manager in 223. Even after a complete total wipe.
[Nook Color Android Development] newellj79:
same here. going back down.
[Nook Color Android Development] stolenmoment:
Media player in general is borked. Music skips songs at several per second.

Back to 222.
[Nook Color Android Development] boggsie:
Same here, too!

Back to 221, right!?
[Nook Color Android Development] Crissynak:
goimg to update cm7

but i am slightly unsure where to include in my file on where to flash the new 7.1 update. And do I have to be updated on the latest clockworkmod because right now I am using 3.2.0.1.

Thanks!
[Nook Color Android Development] ianPhillips1:
Same dsp fc's, even tried a titanium back up and still no go, guess the audio tweaks tubed it.

Ian

sent from my ereader
[Nook Color Android Development] stolenmoment:
Umm, yeah. I actually reflashed on the subway (Kendall to Central) and the reboot hadn't finished when I got off at Porter. One elbow hooked on a pole doesn't help reading much.
[Nook Color Android Development] bigbob23:
You can update just as you would with a nightly. ROM Manager makes it easy. 3.2.0.1 is the latest CWM recovery.
[Nook Color Android Development] boggsie:
Apologies; I didn't mean to sound like that guy I was thinking that maybe I had missed a build (222).

Thanks for clarifying ...

Best regards,

-boggsie
[Nook Color Android Development] patruns:
That is the latest version of CWR......
[Nook Color Android Development] bhrich902:
same on 225, seems the only thing i've noticed so far so freezing it did the trick...
[Nook Color Android Development] td911:
Getting the DSPManager error and now my FieldRunners is crashing as well.
[Nook Color Android Development] Awats:
Same here. I went back to the last stable until it's better understood.
[Nook Color Android Development] akenis:
Hey some of the newer cm7 performance settings changed. What's the relationship between the 16 bit transparency setting there, and unchecking 32 bit in nook tweeks app? What's a good combination of performance settings?
[Nook Color Android Development] chungylau:
working link for older nightlies?

The links in the first page of this thread do not work for nightlies older than a few days. Does anyone have links to the recent nightlies, since 8/29/11? Thanks.

The last August nightly does not give me the SOD, like the newer ones do, and I am trying to go back to it.
[Nook Color Android Development] DizzyDen:
If you can reference it by nightly number I know I have it. Are you wanting N175 or 176?
[Nook Color Android Development] ianPhillips1:
Yup, 226 is poop. DSP issues, froze it and now the youtube app wont play anything HQ or not :confused:

Ian
[Nook Color Android Development] chungylau:
It's the last one in August, before that time when nightlies were not updated. But either one probably is good. If you can send me a link, I would really appreciate it.
[Nook Color Android Development] bigbob23:
Thanks for the heads-up. I guess I'll stick with 220 a bit longer.
[Nook Color Android Development] ianPhillips1:
221 is solid if your jonesin for a flash ;)

Well just tried the latest version of Netflix and sound but no picture. YouTube is working though so I'm thinking its the Netflix app and not the 223+ "bug"

It is the netflix app, 221 is the last good nightly,

oh Dal where for art thou ,what commit is causing the sound /video issues

Ian

sent from my ereader
[Nook Color Android Development] miniaturepeddler:
interesting, I had noticed the dsp freezing, but hadn't watched my tv.com/netflix/youtube lately, so did not realize that they no longer worked.

So, lo and behold (I had updated nightly up to 226), they would not show videos.

So I began backing out updates, first going back to 223, then 220, and it did not fix my wohs. So I went to a backup from 10/02 and checked, everything worked and no dsp freezes.

So updated to 220, and system is still good, dsp not freezing, tv.com working, netflix working, and youtube working again.

So I am currently making a backup of this image and I shall creep forward.
[Nook Color Android Development] DizzyDen:
That one would be N177 with build date of Aug 31.... uploading to my RS now... will link when its done.

The link is:

https://www.rapidshare.com/files/3562820013/cm_encore_full-177.zip
[Nook Color Android Development] MadMikeSS:
Seems to be fine up to 221, then with 223 on we start seeing the DSPManager issue.
[Nook Color Android Development] christoophat:
Just did a complete wipe & dropped down to 221.

Installed Netflix again and now I get a black screen, audio but no video. Flash is installed, can login & select media normally, just everything plays as a black screen...sigh...
[Nook Color Android Development] ianPhillips1:
Its the Netflix update, there is a thread on it in nook themes /apps . I restored a titanium BU

Ian

sent from my ereader
[Nook Color Android Development] christoophat:
thanks, just saw that after browsing thru the Apps forum. Switched back to older version & all is well again.
[Nook Color Android Development] boggsie:
Any feedback re: DSP and nightly 227?

<edit>

Drat, DSP still Force Closes

</edit>

Best regards,

-boggsie
[Nook Color Android Development] miniaturepeddler:
installed 227 over 220 (which I had restored back to and had running nicely).

Upon boot, immediate force quit of dsp, answered affirmative, and then another force quit of dsp.

unable to establish network connection.

so back to my backup for me.
[Nook Color Android Development] keyodi:
Try copying the DSPmanager.apk, which is located in system/app/ from 221 to 227.
[Nook Color Android Development] dvdivx:
The audio was changed but not the drivers starting with 223 it's not a DSP issue so much as a driver issue I think
[Nook Color Android Development] keyodi:
It looks like you were right...I copied all the .so files located in /system/lib/ (not the folders) from 221 and copied them to 227. No more FCs. I'll try and narrow it down to a specific file.

Edit: The libaudio.so file is the cause of the FCs. Just replace it with the one from nightly 221

Edit2: This workaround also works with N228
[Nook Color Android Development] liam.lah:
I need some help, hopefully someone else has encountered this.

I have updated from nightly 177 to 7.1 stable, and my home screen is all buggered up.

Here is the first screenshot, on nightly 177.

Everything is nicely ordered.

On 7.1 everything has shifted, i cant put things back, (forgive the photo, screenshots no longer work on 7.1)

Ive tried putting the DPI back to 161, that makes no difference. I also changed the number of columns in ADW EX, this appears to fix it at first, but again thigns dont fit together as they originally did.

Any ideas?
[Nook Color Android Development] zequav:
I select all the options that improve performance vs quality (disable dithering, enable 16 bit transparency, disable 32 bit framebuffer in nook tweaks...). Haven't noticed any artifacts or low quality anywhere, and my nook is nice and snappy.
[Nook Color Android Development] Dj-Gutz:
I'm still trying to get USB GPS to work ( not my first post about it :\ )

I think I found the relevant code to fix the issue

Can a dev verify it and maybe implement the code?

Problem :

USB GPS isn't working , it is detected as ttyUSB0 on the system but no app recognizes it

There is only one android device that has reported working usb gps - Zenithink ZT-180

there is a big must there that the device will be recognized as ttyUSB9 ( which is what I believe the solution to our device as well - apparently the apps are looking for that port )

Solution ( I Hope ) :

I've compared the kernel sources and I found this piece of code on the zt-180 , located at /drivers/usb/serial/usb-serial.c , which is missing from the nook

if(1)
/*if( PL2303_VENDOR_ID == le16_to_cpu(serial->dev->descriptor.idVendor) // PL2303 as usb gps port
&& PL2303_PRODUCT_ID == le16_to_cpu(serial->dev->descriptor.idProduct) )*/{
if( !serial_table[9] ) { // ttyUSB9 - data
serial_table[9] = serial;
serial->port[0]->number = 9;
*minor = 9;
return serial;
}
}

https://github.com/atpboy444/ZT-180/blob/master/drivers/usb/serial/usb-serial.c

https://github.com/dalingrin/nook_kernel/blob/usbhost/drivers/usb/serial/usb-serial.c

From my little and outdated knowledge in coding , seems like this code is "forcing" the port to register as ttyUSB9

So I'm asking for help since I don't know how to compile/edit kernel code yet
[Nook Color Android Development] ianPhillips1:
Fyi the latest Netflix is cm7 friendly(it even says so in the "what's new") and works fine.

Ian

sent from space
[Nook Color Android Development] chungylau:
Thanks a lot! Just installed it, will see if there is still SOD.
[Nook Color Android Development] ianPhillips1:
Are you replacing before or after flashing?

Ian

sent from space
[Nook Color Android Development] keyodi:
This is how I did it:

extracted the file (libaudio.so) from N221

Opened N228 with winrar

Copied the file to /system/lib/ in N228

Flashed

You should be able to copy the file after you flash as well
[Nook Color Android Development] ianPhillips1:
Copied after and I boot to black, gonna pre package now

Edit:prepackaged and working like a champ.

Ian

sent from my ereader
[Nook Color Android Development] waylo:
Please keep us updated if you're experiencing SOD on 177.
[Nook Color Android Development] dxxvi:
How to delete system apk packages?

I used LMDE before (Linux Mint Debian Edition) and could adb shell to my NC (after modifying the udev rules ....). After flashing an encore nightly, I usually rebooted my NC in recovery mode and adb shell rm -f /system/app/some.apks.i.donot.need for example calculator, file manager, dspmanager ...

I just re-installed my machine with Debian Wheezy and couldn't adb shell to my NC. I can see it with `lsusb' but `adb devices' showed nothing. Is there any chance for me to delete some apk's in /system/app if I cannot adb shell to my NC?
[Nook Color Android Development] akenis:
Thanks. Don't really know what it all does, but followed ur settings. Def smoother scrolling and transitions. Don't notice anything worse about the screen quality.
[Nook Color Android Development] akenis:
U guys wipe batt stats after each nightly? I havent's done it in a couple of builds. Normally jjust use battery calibration app from market.

Thought I heard someone say that CM 7 automatically modifies batterystats file when necesssary. Any truth to that?
[Nook Color Android Development] Ronin3178:
For the Nook, yes. Fattire modded the uboot for the Nook to calibrate battery files everytime it boots up, this is my approximation of course. But it was an attempt to fix PBD "Premature Battery Death" and did in my experience. I "think" that wiping battery stats might adversely affect this.
[Nook Color Android Development] Awats:
Why is this even necessary? Something get overlooked?

:confused:
[Nook Color Android Development] bbernardini:
I've noticed that sometime in the last few nightlies, absolutely no mp4 videos will play in any player I've tried. Previously, I've been able to download YouTube videos with TubeMate and play them Moboplayer, ES Player, and the stock player. Now, I can't. This seems unrelated to the "touch to retry" problem that's common with YouTube on multiple devices. Anybody else have a similar problem?