Related
Running dual boot with eclair ovrclocked and rooted. Works fine. The second boot on froyo seems to be victim of the screen of death issue. Running it with the froyo 1.1ghz kernel and it runs fine until I lock the screen. If left for anytime it doesn't wake up. Ideas? Fixes?
Sent from my Nook Color (zoom2) using Tapatalk
Canadoc said:
Running dual boot with exoskeleton ovrclcoked and rooted. Works fine. The second boot on froyo seems to be victim of the screen of death issue. Running it with the froyo 1.1ghz kernel and it runs fine until I lock the screen. If left for anytime it doesn't wake up. Ideas? Fixes?
Sent from my Nook Color (zoom2) using Tapatalk
Click to expand...
Click to collapse
Mount rw
then
Code:
echo "1" > /sys/power/wakelock
after every boot, or add the 'write' to the init.rc
wii try this
Can I add this line to the init.rc via root explorer text edit mode?
And if so do I just type it in exactly? If so, where in init.rc do I add the line
Decad3nce said:
Mount rw
then
Code:
echo "1" > /sys/power/wakelock
after every boot, or add the 'write' to the init.rc
Click to expand...
Click to collapse
added the line near the top in int.rc
No change in function.
Very frustrating froyo is all but unuseable now on my dual boot setup.
Any other thoughts?
Could I be using the older oc kernel from Dalingirin?
Which should I use for emmc froyo. thought i was on the latest...
Canadoc said:
Running dual boot with eclair ovrclocked and rooted. Works fine. The second boot on froyo seems to be victim of the screen of death issue. Running it with the froyo 1.1ghz kernel and it runs fine until I lock the screen. If left for anytime it doesn't wake up. Ideas? Fixes?
Sent from my Nook Color (zoom2) using Tapatalk
Click to expand...
Click to collapse
you could try this...
http://www.appbrain.com/app/softlocker-free/otis8.softlocker
Canadoc said:
Running dual boot with eclair ovrclocked and rooted. Works fine. The second boot on froyo seems to be victim of the screen of death issue. Running it with the froyo 1.1ghz kernel and it runs fine until I lock the screen. If left for anytime it doesn't wake up. Ideas? Fixes?
Sent from my Nook Color (zoom2) using Tapatalk
Click to expand...
Click to collapse
I don't have the sleep of death. But tried having my froyo overclocked to 1100 and 1000 on the dual boot setup as well. But most of my apps would run then crash. When i go back to stock it runs fine. Something about the ock'ed that the dual boot froyo doesn't like.
Would love a solution to this because i love the fact that I can dual boot to froyo so I can use flash when needed. Especially for some video streaming apps.
Sent from my "NookDroid" using XDA App
racks11479 said:
I don't have the sleep of death. But tried having my froyo overclocked to 1100 and 1000 on the dual boot setup as well. But most of my apps would run then crash. When i go back to stock it runs fine. Something about the ock'ed that the dual boot froyo doesn't like.
Would love a solution to this because i love the fact that I can dual boot to froyo so I can use flash when needed. Especially for some video streaming apps.
Sent from my "NookDroid" using XDA App
Click to expand...
Click to collapse
Wow same here. for my daily driver the stock eclair autonootered with the 1.1ghz kernel has been rock stable and problem free.Everything works just fine except no flash. The only reason I prefer froyo is for better exchange support and to watch some flash video.
Without hardware dsp it is still a bit choppy on oc froyo but manageable usually.
The constant freezing and need for reboots in the dual boot version is making it unusable for me.
Gonna try soft locker and see if it helps. if not I guess I will wait for CM& with hardware dsp.
Canadoc said:
Wow same here. for my daily driver the stock eclair autonootered with the 1.1ghz kernel has been rock stable and problem free.Everything works just fine except no flash. The only reason I prefer froyo is for better exchange support and to watch some flash video.
Without hardware dsp it is still a bit choppy on oc froyo but manageable usually.
The constant freezing and need for reboots in the dual boot version is making it unusable for me.
Gonna try soft locker and see if it helps. if not I guess I will wait for CM& with hardware dsp.
Click to expand...
Click to collapse
Thanks for confirming the issue. Thought it was just me. I'm with you on CM7.
Sent from my "NookDroid" using XDA App
Also having issues with button savior
Sent from my Nook Color (zoom2) using Tapatalk
There is a typo in this thread. It should be:
Code:
echo "1" > /sys/power/wake_lock
From what I've read, this is a workaround not a fix.
sleep of death also on Viewsonic Gtablet
this may be old news, but this problem also creeps into the Viewsonic Gtablet.
http://forum.xda-developers.com/showthread.php?t=855821&page=7
The issue with the gtab, at least in my case, is related to the apps. I am running TNT 4.4
Does anyone know if CM7 or any other ROM Build other than Nookie Froyo 0.6.8 has or is coming out with Video Hardware Acceleration? I currently use Nookie Froyo on my NC and it ROCKS! I would like to upgrade but that feature is a must.
Also has anyone else had a problem with waking the NC from sleep after 30-60 mins? I believe it's from using SetCPU. I tried different profiles and it still happens. After I uninstalled SetCPU the sleep/wake up issue went away.
Thanks!
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I have had CM7.0.2 installed for a few days now and have not had any issues with it. Did you wipe /system and /data before installing? It sounds like it could be a hardware issue if this is the case.
migrax
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
See sig...
My wifi works fine after installing 7.0.2 and the OC kernel, but the indicator in the notification bar no longer works. It shows zero bars no matter what. It's the same on two different brands of routers. No big deal though, just an aesthetic thing I guess.
I didn't wipe /system or /data, for whatever that's worth.
edit: forgetting the network and reconnecting fixed it.
I'm having the same issues...
Sent from my NookColor using XDA Premium App
I also noticed the same on 7.0.2. Perhaps is it is just aesthetics but I was noticing other minor glitches (simi clock fails and battery gauge) so fell back to 7.0 and things are moving along swimmingly.
One thing to keep an eye out for is that CM7.0.0 and 7.0.2 apparently dont like AES encryption on wifi. I had a hell of a time getting my wifi to work on my new nook as of Wednesday (omg so much fun) but once I switched my router to TKIP it works great. Kind of annoying, but a simple fix.
2.6.32 is coming *soon* and it allows me to build a new wifi driver. This will hopefully fix the AES issue that some people have.
phiremod's 6.2 has solved this wifi issue.....not sure what build he is using
AndroidDeer said:
I used Rom Manager to update to CM 7.0.2 today. I also included the gapp update. After reboot, all applications seem fine. Even my LCD density setting was as before (it's supposed to be reset at each reboot). However, my nook color cannot detect any wifi. All of them are out of range.
I rebooted several more times but that didn't help. So I just restored to old ROM. However, the problem remains. What's worse, none of my installed apps, except for the gapps, are runnable. My nook color is useless now.
I guess I will have to do everything from start again. But what was the problem? I wish I had never tried to update to 7.0.2. I was quite happy on CM7.
Click to expand...
Click to collapse
I was in the same pain, but backed down one version to the nightly 55 release and it's been beautiful. Clearly they're working on the new version, since there hasn't been a nightly in about a week. I'm fairly new to CM, and it wasn't hard. Download the ZIP, boot into recovery - flash the ZIP, wipe cache and came right up. Do your backups (nandroid and titanium) just in case, as always. ;-)
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
nemir said:
I had same problem. Then I did install official Nook Color Stock firmware. Wifi works perfectly... So CM 7.0.2 has software based problem...
By the way, I have never used OCed setting...
Click to expand...
Click to collapse
I've never used the overclocked settings beyond what CM will offer.. the 925mhz. Considering going to the 1.1ghz since others are reporting that's stable.
But seriously - go to the 55 version of the nightly build. In my experience, the WiFi is FAR more stable than the official 7.0.2 release.
http://mirror.cyanogenmod.com/?device=encore&type=nightly
Thanks, worked as a charm
ylixir said:
Dunno about the apps not running, but the wifi borking like that is a common problem.
You just have to "forget" your known wifi hotspots. I've heard people saying that forgetting just one will work. The one time it happened to me i just took them all out.
Click to expand...
Click to collapse
had tried hard reset, multiples on/off of wi-fi
but forgetting one network did the trick
Hey guys,
I recently noticed my N1 (rooted + blackrose) starts rebooting while having data enabled and browsing. The bottom of the phone gets kind of hot, I'm thinking the module overheats or something? I tried different ROMs (CM7.2 and latest HyperSense Nova). Works fine on WiFi. Is there a way to diagnose what's going on?
cheers
d1rX said:
Hey guys,
I recently noticed my N1 (rooted + blackrose) starts rebooting while having data enabled and browsing. The bottom of the phone gets kind of hot, I'm thinking the module overheats or something? I tried different ROMs (CM7.2 and latest HyperSense Nova). Works fine on WiFi. Is there a way to diagnose what's going on?
cheers
Click to expand...
Click to collapse
any1?
Try flashing an other rom or radio. Make sure you make a backup first.
Sent from my Samsung Galaxy Nexus using Tapatalk.
I did try different ROMs. I haven't changed anything and it started to reboot...Is there a way to lower the voltage maybe or check logs for errors?
Using stock Nook HD+...everything was working fine for a few weeks, but now scrolling (in firefox, chrome, etc) is jerky. Killing apps didn't help. Rebooting didn't help.
Any ideas?
ntice said:
Using stock Nook HD+...everything was working fine for a few weeks, but now scrolling (in firefox, chrome, etc) is jerky. Killing apps didn't help. Rebooting didn't help.
Any ideas?
Click to expand...
Click to collapse
You are probably suffering from need of an emmc trim. It is akin to defragging on a PC. But the issue with some HD+'s is you can brick your device doing that as some HD+ emmc chips are buggy. Read about this in the CM10.2 thread.
I don't know if this will help or not, but you could try going to my HD/HD+ CWM thread and make a bootable CWM SD, backup your device, and do an immediate restore. That re-writes everything to emmc. Then see if it helps.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You are probably suffering from need of an emmc trim. It is akin to defragging on a PC. But the issue with some HD+'s is you can brick your device doing that as some HD+ emmc chips are buggy. Read about this in the CM10.2 thread.
I don't know if this will help or not, but you could try going to my HD/HD+ CWM thread and make a bootable CWM SD, backup your device, and do an immediate restore. That re-writes everything to emmc. Then see if it helps.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Do you mean the trim is buggy on the hardware side of nook hd+?
I also experienced the slow down on stock rom and today flashed to cm10.1.3. smooth so far with occasionally screen flickering (going black and come back on). Is trim supported in cm10.1.3? And if not, can we run the lagfix in the playstore?
loveleo said:
Do you mean the trim is buggy on the hardware side of nook hd+?
I also experienced the slow down on stock rom and today flashed to cm10.1.3. smooth so far with occasionally screen flickering (going black and come back on). Is trim supported in cm10.1.3? And if not, can we run the lagfix in the playstore?
Click to expand...
Click to collapse
You can run the one from Play Store, but I'm telling you that the internal memory chip may be buggy and you could brick your device. It is a problem with the hardware.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
You can run the one from Play Store, but I'm telling you that the internal memory chip may be buggy and you could brick your device. It is a problem with the hardware.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Sure do not want to risk bricking the device, not worth it. Maybe doing back ups and refresh every a few months then. Hardware problem usually means there is nothing we can do though. Too bad.
I don't think scrolling has anything to do with the storage (everything is in RAM after all). It's like some internal Android graphics setting got changed somehow. Could an ordinary app make a permanent change like that?
Deleted. Question posed in a new thread.
ntice said:
I don't think scrolling has anything to do with the storage (everything is in RAM after all). It's like some internal Android graphics setting got changed somehow. Could an ordinary app make a permanent change like that?
Click to expand...
Click to collapse
Actually it could very well do with not trimming flash RAM, as lots of things go one in the background, including reading from/writing to DBs. After I did CWM backup/restore, my Nook HD+ 16GB was a lot smoother on browser/launcher/etc. What a sucky eMMC bug.