yashsingh1/xdaforums huggingface dataset:
[Nook Color Android Development] JimSP:
Anyone here able to connect to a VPN?

Ever since RC1, when I connect to my home VPN my nook locks up and you have to hold the power button down until it shuts off and then reboot.

Used to work fine on 7.0.2-7.0.3.
[Nook Color Android Development] n0c:
So, I feel like this is the second time I've done this, but. I downloaded n136, opened it up in Rom Manager and chose to back up current rom and clear dalvik cache. Upon reboot, I realized too late the battery was low, and the low battery icon came up. I think recovering from this the last time was as simple as another reboot, but now it seems as though something is actually corrupt. I have fattire's boot thing installed, and cannot get the system to boot into recovery or normally ( I never set up an altboot ). My nook was on n118 installed to emmc.... any words of advice for the simplest recovery from this? Was thinking of just reflashing from another sd card where I will flash the most recent CWR...

Thanks for any advice :)
[Nook Color Android Development] dasingleton:
Everytime i try wiping Dalvik Cache...I get stuck in Recovery and I have to power off and power back on? What gives?
[Nook Color Android Development] bartonkt:
That's normal. Not sure if its something that is Nook-specific or related to a bug in CWR.
[Nook Color Android Development] quepaso:
Absolutely not normal. When i wipe, i wipe dalvik 3x, cache 3x, data 3x. And i never have issues like that. And i wipe like the best of them, aka, ive wiped more then i care to remember.
[Nook Color Android Development] Divine_Madcat:
To really confuse the matter it WAS normal, but in the most current version, it is not.

The early recovery versions DID have the bug where clearing the cache would lock up the recovery. That issue had been addressed however, and should not longer be an issue for those using the most up to date version.
[Nook Color Android Development] bradputt:
http://xdaforums.com/showthread.php?t=971197

flash the latest CWR V3.2.0.1
[Nook Color Android Development] dasingleton:
I tried flashing the latest CWR V3.2.0.1 thru Rom Manager. It says it was successful...however when i boot into recovery, it still shows an older version. Looks like I might need to start over...
[Nook Color Android Development] bigbob23:
I figure that even getting a completion was a success in itself.

I have a couple of ideas where it might have gone wrong, but didn't take the time to dig into it yesterday.

I was unaware of that. I'll give it a try on the Mac natively, which hopefully will go much more quickly. OS X has been my platform of preference for the past several years (although, as with Windows, there are many folks who haven't discovered the power of the command-line).

Thanks for the encouragement.
[Nook Color Android Development] Hindle1225:
Do you still have the old cwr boot sdcard still in the nook?
[Nook Color Android Development] dasingleton:
Yes, same card I used when I initially rooted my nook a few days ago. I haven't been able to flash any nightlies either. It completes the install process...but once I reboot, it still shows my previous nightly. Weird for sure.
[Nook Color Android Development] john10101:
Question #1: are you running an SD build of cm7?

Question #2: If not, did you install cm7 off a bootable cwm sd?

if either one is yes, then eject the sd card.
[Nook Color Android Development] MedLine:
native pptp vpn client broken with 2.6.32 cm7 builds, this is a known problem.

OpenVPN and VPNC using tun/tap works fine, including for recently released official AnyConnect client for rooted form Cisco.
[Nook Color Android Development] peramikic:
Works on n129 with OC 6/30 on SD card, OpenVPN via tap
[Nook Color Android Development] n0c:
Is there any hope for PPTP ever?
[Nook Color Android Development] n0c:
Doh,

So I put in another sd where I have CWR flashed, and it's 'continuing' the process of installing n136. I doubt it will actually work, but I'm crossing my fingers :)
[Nook Color Android Development] n0c:
Whew, got everything sorted. Was a good chance to update my recovery sd...

One question though, is it impossible to have the screen turn off when it's plugged into usb / wall wart? It will dim, but not shut off. I remember it used to be a setting under debugging, but I can no longer find it in settings or spare parts...
[Nook Color Android Development] harpo1:
After you plug it in push the power button. The option under debugging was keeping the screen on when plugged in.
[Nook Color Android Development] n0c:
gracias. I swear I tried that and it kept coming back on. Turning off the screen-off animation has helped a lot. It seemed like despite carefully pressing once, it'd always turn the screen back on. I am using a gesture lockscreen too..
[Nook Color Android Development] skwalas:
Heeeeyyyy, i'm impressed. Now I definitely believe the difference in those numbers! You'd make a good statistical lackey someday...
[Nook Color Android Development] lospulpo:
Hey I've been having a ton of wifi problems on the recent nightlies (120+). Wifi will always be turned off when waking or upon boot. I have to go into the settings app and toggle airplane and wifi until I can eventually see the nearby networks and then connect. It always works after a while though.

Now since ive been on Nightly 136 I've been having way more trouble. Wifi toggling detailed above takes way longer and when it falls asleep I'm getting the sleep of death.

I never had any of these issues until recently, CM7 worked great since day 1. It almost feels like instability from undervolt but I haven't changed the settings in Nook Tweaks at all. Was at 1300MHz but dropped that to 1200 and still no dice. Tried all Wifi Sleep Policies too.

Any suggestions?
[Nook Color Android Development] Taosaur:
Did you wipe cache and/or dalvik cache before flashing the new nightly? You might try wiping again. I was having some Wi-Fi issues recently (out of the blue, after running RC1 for a couple weeks with no problem) and wiping cache and installing the new nightly seemed to clear it up.
[Nook Color Android Development] khaytsus:
I've been having issues, but not quite like you describe. Since the 2.6.32 kernels up to 126 I had no problems, but later nightlies I've tried, 132 and 136, I'll find that Wifi won't come on. In the Settings it'll do Scanning, see some APs, try to connect to one and immediately goes Disconnected. Wifi Scanner apps see nothing, etc. logcat says..

D/Tethering( 1130): tiwlan0 is not a tetherable iface, ignoring
E/WifiHW ( 1130): Unable to open connection to supplicant on "tiwlan0": No such file or directory
D/WifiStateTracker( 1130): Reset connections and stopping DHCP
D/WifiStateTracker( 1130): Disabling interface
I/wpa_supplicant(13727): CTRL-EVENT-STATE-CHANGE id=-1 state=2 BSSID=00:00:00:00:00:00
V/WifiStateTracker( 1130): Connection to supplicant established, state=SCANNING
I/wpa_supplicant(13727): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
V/WifiMonitor( 1130): Event [CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00]
V/WifiStateTracker( 1130): Changing supplicant state: SCANNING ==> DORMANT
D/WifiStateTracker( 1130): Reset connections and stopping DHCP
D/WifiStateTracker( 1130): Disabling interface
I/wpa_supplicant(13727): CTRL-EVENT-DRIVER-STATE STOPPED
V/WifiMonitor( 1130): Event [CTRL-EVENT-DRIVER-STATE STOPPED]
I/wpa_supplicant(13727): CTRL-EVENT-TERMINATING - signal 15 received
I/wpa_supplicant(13727): CTRL-EVENT-TERMINATING - signal 0 received
I/wpa_supplicant(13727): CTRL-EVENT-STATE-CHANGE id=-1 state=8 BSSID=00:00:00:00:00:00
E/wpa_supplicant(13727): TI: Driver not initialized yet
E/wpa_supplicant(13727): TI: Driver not initialized yet
E/wpa_supplicant(13727): Failed to disable WPA in the driver.
E/wpa_supplicant(13727): TI: Driver not initialized yet
E/wpa_supplicant(13727): TI: Driver not initialized yet
V/WifiMonitor( 1130): Event [CTRL-EVENT-TERMINATING - signal 15 received]
D/WifiStateTracker( 1130): Reset connections and stopping DHCP
V/WifiStateTracker( 1130): Connection to supplicant lost
D/WifiStateTracker( 1130): Disabling interface
E/Tethering( 1130): attempting to remove unknown iface (tiwlan0), ignoring

I have a dmesg but it's of a different event, I'll have to grab a log of each next time this happens.

I managed once time to toggle wifi on and off a few times and it recovered, but normally the only recovery is a reboot.
[Nook Color Android Development] o0adam0o:
So i installed CM7.1 RC1 on my Nook Color yesterday (following these exact instructions http://xdaforums.com/showthread.php?t=1030227)

Ive had some issues since then.

1) I keep getting Force Close on Superuser. I first noticed this when i installed shootme that it wouldnt start. Then i realized Superuser was force closing when i tried to open shootme. Now even when i click on the Superuser icon by itself, it still force closes.

2) My screen randombly stops responding and i have to hit the power button once to turn screen off and then back on and it works again. Sometimes i have to push icons/buttons more than once.

Any tricks/tips to fix this?
[Nook Color Android Development] crandy2:
In reference to my earlier post on this thread (#4321), after spending a day or so with N136, I have figured out that when I tap the power button to turn off the screen, instead it goes into some type of reboot. The screen is off for about 2 minutes, then the lockscreen reappears. Any apps I had open previously are closed.

If I let the screen turn off via a timeout, this doesn't happen, it will come right back up when you press the power button and behaves as previous builds has. It does this reboot only when I tap the power button to turn off the screen.

I flashed back to N128, and the power button works fine again. Guess it is going to take a while to get all these changes sorted out.

I posted a Last_Kmsg over in the SOD thread, if anyone needs it.
[Nook Color Android Development] lospulpo:
Hey thanks for replying. Yea I always wipe cache and dalvik cache just to be safe. I've got a alot of apps installed maybe I should try a fresh build for a while w/o restoring apps. I'm running the InteractiveX governor too by the way and since the cpu drop to 1200 it seems like it might be working a bit more stable (I was at 1300 for a atleast a month) but we'll just have to wait and see. Ill keep updating nightlies.
[Nook Color Android Development] paleh0rse:
I was getting all kinds of new SODs, FCs, reboots, and random freezes using n127 through n136, so I decided to do a total device wipe and fresh install of stock 1.2, then wiped again and flashed n136/gapps -- a process I hadn't done since n80, or so.

I then used TiBu to restore apps only, no data.

Im happy to report that after doing this, all of the problems seem to have disappeared and n136 is running smooth as silk with max 1200 and interactiveX governor... for now. :)

I highly suggest that others do the same -- especially since the OC kernel was inserted into n132+. The entire process took less than 45 minutes...
[Nook Color Android Development] khaytsus:
If you have very few apps or own TiBu. If you have 200 apps installed and manually reinstall 'em with TiBu..... QUITE a bit longer of a process.
[Nook Color Android Development] paleh0rse:
Just re-install them as you need them... I'm betting that 90+% of your 200 apps go unused for days or weeks at a time, and there are probably many that you'll never use again -- but, they're always waiting in the wings (the markets or SD card) if/when you need them again.

IMO, the system stability is well worth the effort and patience. It also cuts down on the number of random -- and often unique -- issues that get reported to the devs. Problems discovered on fresh installs are much more likely to be universal than those seen on devices with 200+ apps, so the devs can focus their time and energy on those universal bugs instead.

To each their own, of course... all I know is that my Nook is awesome again! ;)
[Nook Color Android Development] crandy2:
N138 just came out and solved my power button problem!! Woohoo!!
[Nook Color Android Development] khaytsus:
I certainly install in waves... Picking all of the important stuff first, but even at that, it's hours of work.

But hey, if something is screwed I suppose it's the way to go.
[Nook Color Android Development] doncaruana:
FWIW, nenamark scores are still ~21.5 with n138, just like n136. n131 scores are still 23.6.
[Nook Color Android Development] slider2828:
How are you scores scoring so high? Whats your OC at?

NVM - you guys are running Nenamark 2.....
[Nook Color Android Development] residentorca:
I've never had wifi problems with previous stables or nightlies until last week. I always wipe caches with every ROM/kernel update.

The problem is like lospulpo's in that when I enable wifi, it gets stuck on "connecting" and then after many cycles of toggling on and off the status finally changes to "scanning" and then actually connects to the wireless network.

At least when it does connect, it doesn't do what khaytsus described.
[Nook Color Android Development] DigitalMD:
I had a strange thing happen when I tried to update form Nightly 134 to 136. after a wipe and sucessful install, it would not boot. Just hung at the green cyanogen logo. Could not boot into recovery either. I wound up having to wipe and repartition the Nook and return to stock. I then installed 133 and everything was fine. Tried to update to 136 after a full wipe and blamo, it would not boot again. I see a lot of folks have no problem with 136 so this baffles me. I"ve been updating to almost every nightly version since about 86 and no issues until now
[Nook Color Android Development] Bimboy:
Well, I flashed n136 (from n126) and lost wifi connectivity as well.. and yes, I always wipe cache and dalvik cache. I also gained two more issues on the flash.. lost root and cannot read SD cards any longer.

Wifi continues to attempt to connect to my home network, fails, and repeats.

About to try crossing my fingers and hoping a bootable card will somehow work.. get me to be able to flash a stock build and then got from there. Gonna be a long night. :)
[Nook Color Android Development] SeaFractor:
Strange about the NB 136 problems. I've had no problem moving from 133 through 138.

What I did do each time the upgrade completed was immediately reboot into recovery and perform these three operations and then rebooted.

1. Clear cache

2. Advanced - clear dalvik cache

3. Advanced - fix permissions

Reboot.

Totally solid. Perhaps the permissions in the image need to be checked as the operation above may be resolving that issue for me.
[Nook Color Android Development] doncaruana:
Nope - not running nenamark 2 at all - running nenamark 1.

No voltage or stepping tweaks, just OC to 1200, right out of the CM7 performance settings. I found that if you OC higher, the nenamark scores actually went down.
[Nook Color Android Development] lospulpo:
If you pay for TiBu pro you don't have to manually click install on all of your apps. When you do batch restore it just does all of them only takes me a few minutes for 100+ apps.

Ill have to try that data/system wipe and complete reinstall soon. Wait to restore my apps for a bit and try it out with clean install... Advanced > Permissions Fix too.

Ill post back ^_^
[Nook Color Android Development] slider2828:
Thanks that is interesting!!

OMG its soooo true.... I was at 1300 nenamark1 @ 16.2.... then 1200 nenark1 @ 23.2 fps.....wtf.....
[Nook Color Android Development] dalamchops:
read somewhere that (forgot if it was specifically for cm7) if you format sdcard within android you actually format the boot partition or something.
[Nook Color Android Development] rvv2002:
(Crap) Any ideas on how to restore my boot partition?
[Nook Color Android Development] dalamchops:
i've formatted my /boot before, just find the recovery thread on here and flash back to stock w/ a cwm sd card.
[Nook Color Android Development] rvv2002:
Thanks for the heads up. Replaced boot and reloading CM7 as we speak. Did you format your SD card on your computer after you loaded CM7?
[Nook Color Android Development] dalamchops:
nope, i just keep cwm on there. I take out the sd everytime i boot n push it back in
[Nook Color Android Development] donballz:
Yeah, download Easeus Partition manager. It makes it really easy. And its free.

I just bought a second 4gb sd card ($4 on ebay, steal) and keep cwr on it now. Just makes life easier.
[Nook Color Android Development] subcypher:
I made the same mistake when rooting and modding my NC the first time. I thought I bricked it, just as most people posting "OMG BRIK'D NC!" threads in the General section. I read up on it and fixed it the same way you're doing it now. Once I recovered I decided to use two different SD cards. I have a 4GB one formatted for storage. I had an old 2GB card that came in a phone I no longer use, so I formatted it with CW Bootable and I use that to update CM7 now. Of course, after I did that, CW 3.0.0.6 came out and I don't need both.
[Nook Color Android Development] combustiblemonkey:
I didnt bother to root it, I just flashed over the EMMC on my 2nd nook. Had to return the first one for a defect on the screen but I dropped it back to stock before I returned it. Took the 2nd one out of the box and popped my SD card in, booted and flashed right there in my truck in the parking lot :)

So yeah, dont bother rooting if you are going to flash the EMMC.
[Nook Color Android Development] xwint3rxmut3x:
Alright, two quick questions. Sorry if they're "noobish" but I've never been in a situation where the ROM i'm using gets updated regularly. If I flash a new nightly over an old nightly, will it erase all of my apps and settings? (is there any way for that not to happen if it's the case?)

and also is anyone else having wonky wifi issues? Mine seems to have difficulty connecting and any time I try and open wifi/network from settings it force closes on me?

Thanks in advance.
[Nook Color Android Development] tominabox1:
you should be able to flash nightlies without wiping data

as for the wifi issues, they are fixed in nightly 8.
[Nook Color Android Development] adma84:
wifi is not fixed, it may be better, but it's definitely still an outstanding issue.
[Nook Color Android Development] tominabox1:
i was merely referring to the wifi settings force closing, i am aware there are still issues as I have them myself. Really hope we get a new nightly soon!
[Nook Color Android Development] xwint3rxmut3x:
Great. Thanks guys, just wanted to make sure before I flashed a new zip, don't really want to have to redownload all my apps and stuff every time I do it. And i'm on nightly 7, so off to 8 I will go.
[Nook Color Android Development] adma84:
It's been 2 days (ughh, nights) since a nightly, right? Wonder if some MAJOR bug was found in CM7 as a whole?
[Nook Color Android Development] xwint3rxmut3x:
do i need to flash gapps each time? i'm assuming no, but figured i'd ask

nvm, answer is no. Just flashed and checked.
[Nook Color Android Development] adma84:
no, you do not
[Nook Color Android Development] xwint3rxmut3x:
haha, thanks for the quick response. Seems solid, I like that I can at least see what the wifi is doing now, and where it's trying to connect to. I think mine was defaulting to a neighbors open network with a terrible signal.
[Nook Color Android Development] bdcrim:
Gingerbread received an update, to 2.3.3 I got it on my CDMA Hero today. Seems snappier. Good things are coming.
[Nook Color Android Development] adma84:
oh duhh, I saw that Cyanogen tweeted he was merging 2.3.3
[Nook Color Android Development] bdcrim:
Correct, the Hero update was CM7 based (I did not see the tweet). I responded to a post thinking I could cheer someone up. Nice vocabulary by the way.
[Nook Color Android Development] Anon87:
Did you do a hash check of the 136 zip?

to ensure your download wasn't corrupted/incomplete?

Sent from Soft-Rooted HTC Desire using Tapatalk
[Nook Color Android Development] Bimboy:
I only fix permissions in the rare case of having any issues. Regardless, I did try that as a remedy, and it didn't work.

I was able to go back to stock 1.2, reroot, then went to N138. Since my SD card got corrupted in the process, I had no TiBU to use, and have to scrounge up all of my apks from the market or spare SD cards that I previously used. (I searched for other M-sdhc cards, and found eight cards, ranging from 8gb - 16gb. I had no idea I had that many. :)
[Nook Color Android Development] john10101:
Hello, Yesterday i upgraded from 7.0.3 to nightly 136. everything went smooth, and the nook seems to be performing properly.

I have only had one problem, and im not sure if its related to the build, or just a fluke:

Last night when i got home i plugged the nook in, to get a full charge. Right before i went to bed, i went to check the nook and it was very hot, and frozen. I unplugged it, and forced a reboot, let it cool down for a few min, then i finished the charge (it was around 97% anyway)

has anyone else noticed problems like this? is there something to be aware of?

I do keep my nook in a neoprean case, and it was in there while charging. Ive been doing this since i got the nook(jan), and ive never had a problem.

Im a bit worred to plug it in now unattended. I usually charge it over night.
[Nook Color Android Development] rhester72:
Clocking above 1200 causes the CPU to continue to get faster but the GPU will get slower. I'm assuming Nenamark is GPU-heavy?

Rodney
[Nook Color Android Development] doncaruana:
That's it's purpose in life - it's a GPU benchmarking utility.

But has anyone tried underclocking to see what happens? When I tried it (adjusted steps to max out at 1000), I got lower nenamark scores that way too.

Thing I don't get is what happened between n131 and n134 to lower my scores - or how many others have noticed that issue.
[Nook Color Android Development] Dj-Gutz:
Same issue here , using n138 , default voltages

1200 give me +- 21.5 fps

1250 , 1300 , 1350 - +- 15.5 fps

ran it a couple of times to make sure and it stays consistent

haven't got around to flash n136 again to test this

also haven't tried underclocking
[Nook Color Android Development] doncaruana:
Numbers for me are the same with n136, but, if you can go back to n131 (last build before the OC merge) and drop Dalingrin's OC kernel on, it'd be interesting if you got the same numbers I got (~23.6).
[Nook Color Android Development] joenathane:
Personally, I run fix permissions every 30mins, it's better to be safe than sorry, it's also better to have two chimichangas than one chimichanga.
[Nook Color Android Development] khaytsus:
So for me, Fix Permissions in ROM Manager takes about 20 minutes, so you can only use your NC 20 minutes out of every hour? That sucks.

;)
[Nook Color Android Development] lospulpo:
Here's the changelog:

http://cm-nightlies.appspot.com/?device=encore

n132 added new GPU modules and libs

n136 removed them

Most likely the changes you've seen.
[Nook Color Android Development] john10101:
thats why he needs 2 chimichanga's
[Nook Color Android Development] obsidianblackhawk:
Damn, even when my nook is all jacked up, fix permissions never takes me longer than 5 min.
[Nook Color Android Development] =X=:
I've been having some serious battery issues ever since I've upgraded to 132. I've upgraded to 136 and the problems are even worse.

On 136 if WIFI is on the charge is VERY slow, and next to 0 when charging from a micro USB.

The charging icon indicator seems to always be on even when I'm not charging my device.

This morning my Nook was fully charged, in 1.5 hrs of surfing the device was down to 45%. Usually it's down only to 80% by this time.

Any ideas as to what is eating the batter so much?
[Nook Color Android Development] Ronin3178:
Check under spare parts for battery usage partial wakelock among others. Maybe charge up until you see something over 4200mVs, then boot into cwr and wipe battery stats.