Related
I just tried froyo and it was awesome! But i missed my trackball wakeup too much.
Did anyone else try froyo but revert back to CM until he releases a froyo version and how come?
Just curious and wanted some discussion
I did cause this is just a test release of froyo and is still a little buggy. I'm waiting for the cm version. To flash
-------------------------------------
Sent via the XDA Tapatalk App
Same. Messed with it a few hours and went back to CM5.
I am getting triple the battery life with froyo... sticking with it until CM6.
For trackball wake download no lock.
I for one came from cyanogen and his roms awesome for a 2.1 rom. But its not 2.2. I love flash and can't get that from 2.1. Trackball wake was hive but can use no lock till cyanogen releases a froyo rom. The speed is alot faster imo on froyo 2.2 vs 2.1. Apps open faster and placing widgets on screen opens faster. The capacitive buttons are way more sensitive and the speakers seam louder. APPS TO SD stock is great on so is having memory although on custom ya get those. Just my opinion froyo brings a all alround better experience for me. Only thing I miss from cyanogen is the stock trackball wake ( no lock for now) and full 360 rotation in the browser. Other than that I'm golden. And the reception seems better with this radio ( although you can keep that and go back to 2.1)..
Everything is not for everyone
And I lime the pinch in gallery thing.
ssmithri said:
I am getting triple the battery life with froyo... sticking with it until CM6.
Click to expand...
Click to collapse
Mine lasts longer with more use with Froyo. Will flash CM6 the second it is released !
Got Froyo as soon as the rooted version was out...Just dropped down to CM5.0.7.1 tonight.
- I seriously miss the trackball wake too
- A few games (Asphalt and Super KO Boxing 2) and apps (TuneWiki and MountUSB) are either flaky/unstable or flatout don't run
- Since having Froyo, I've had to reboot the phone at least 4 times due to touchscreen calibration going completely out of whack.
- Overall it's definitely fast, but there were definitely hiccups/lags here and there that weren't big deals on their own, but the accumulation of them got annoying.
I've tried JIT out before on eclair and Froyo (while definitely much more stable) feels like it's still got some of the JIT quirkiness.
I'll likely give it another go as soon the rooted official froyo is out...But I'm definitely chomping at the bit for CM6 action!
got a question come to my mine, those having Froyo issue did them wipe all before install?
I find the Froyo is damn stable and no such mentioning issue.
Asphalt run perfectly.
Running perfectly smooth.
Trackball Wake? - just use lockbot pro and you have trackball wake and lockscreen customization.
Battery life guarantee better than any previous Eclair ROM, this include CM ROM as well.
No touch screen alignment issue.
No radio issue.
* Everything is perfect, the only I miss now is 7 home screen, hope CM can increase to 7 home screen by using the default launcher. I also miss the color changes of status bar clock and notification font. Another wish CM implement this function as in CM 5.0.7.1 in coming CM 6.0
I updated to Froyo and changed back to CM within a couple of days. The reason for it is right now I am travelling in Asia and using wired LAN connections to my laptop. Then using a program called connetifyme that uses the laptops wireless to share the wireless lan connection over an adhoc connection. Froyo would not connect to ad-hoc, but CM does.
Once home next week I'll put Froyo back on again.
temperbad said:
For trackball wake download no lock.
I for one came from cyanogen and his roms awesome for a 2.1 rom. But its not 2.2. I love flash and can't get that from 2.1. Trackball wake was hive but can use no lock till cyanogen releases a froyo rom. The speed is alot faster imo on froyo 2.2 vs 2.1. Apps open faster and placing widgets on screen opens faster. The capacitive buttons are way more sensitive and the speakers seam louder. APPS TO SD stock is great on so is having memory although on custom ya get those. Just my opinion froyo brings a all alround better experience for me. Only thing I miss from cyanogen is the stock trackball wake ( no lock for now) and full 360 rotation in the browser. Other than that I'm golden. And the reception seems better with this radio ( although you can keep that and go back to 2.1)..
Everything is not for everyone
And I lime the pinch in gallery thing.
Click to expand...
Click to collapse
Thank you so much. I didn't know such app existed!
the bat life in froyo is garbage
lightforce said:
the bat life in froyo is garbage
Click to expand...
Click to collapse
The battery life in froyo is an improvement.
Battery life opinions are useless unless you have at least some data to back it up.
For example, I used to get around 16-18 hours a day before I had to charge. Now, I can usually last almost 20 hours.
i would also miss the black notification bar from cyanogen as well. can froyo be updated with metamorph to use the desire notification bar? that's another thing i want to update to froyo and maybe switch between cm5.0.7 and froyo, but would like desire black bar in froyo as well.
For my first post I would like to thank everyone for the great info here.
I got Auto-Nooter 2.12.25 installed and it works fine.
WiFi is currently off until I make a decision on updating.
There seems to be a few options available for going to 1.1 and it is a little confusing.
Any suggestions?
All I can see is a little snapier, wifi signal stronger and pinch to zoom on default browser. The update on the development forum work great without any affects on root, at leat for me. I was running 1.0.0
Sent from my HTC Glacier using XDA App
Purely perceptive but touch seems a little more responsive personally. The pinch zoom in the default browser adds a WTH missing feature. It also reportedly fixes the pinch zoom issue with the current version of Dolphin HD.
I've read it also ups the volume a bit so that at any given level the volume is a little bit higher. Given the default cases from B&N have no cutouts for the speaker that's a good thing.
It's also supposed to improve wifi in some fashion.
There's a 1.1.0 rooted version of the software that you can install pretty easily if you have an already rooted Nook. Some people are having some issues with it, for the most part it works well. personally the only issue I have is DropBox isn't able to download although I've also just now noticed that the wifi won't reconnect after sleeping sometimes. I have to turn it off and on, wifi that is.
If you have a nook with the sound problem (sound won't come back after a sleep) I've seen threads that this update fixes that problem.
just installed rom manager and in clockwork recovery now
1.1 r2 installed Ok
Fixes sound issue
I can verify that the 1.1.0_r2 fixes the issue where the sound did not come back on after putting the nc to sleep. Works great now!
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
Using Nookie Froyo 0.6.8 eMMC.
I noticed my Wi-Fi takes a couple minutes or more to connect after the Nook had been sleeping. So I went into the Wi-Fi settings and I see "Wi-Fi Turning off...", then it comes on, then it turns off, and repeats over and over.
Eventually it will connect. Any idea what is causing this? This is a freshly install ROM. I've wiped it and reinstalled it and still have the same problem. And it works fine after a reboot, seems to only be a problem when it's gone to sleep.
I also installed Spare Parts and set the Wi-Fi sleep profile to never (this problem was happening before installing Spare Parts by the way) however that doesn't seem to prevent it from sleeping either.
I get the same thing. I'm assuming its a kernel thing, but I don't know, I'm definitely not a dev. Its happened in all the nightlies I've flashed, though.
yep this is a kernel issue i believe as it was better on the older kernels. i think it has something to do with your security settings.
try changing from wpa/wpa2 to something else perhaps?
i went to cm7 17 and so far it has been flawless. earlier builds were almost as bad though so i'm not sure if it will last.
That started happening on mine too. I just installed the newest kernel, that clean black theme, and nookie froyo. Prob the kernel.
It seems to help me on my nooki froyo 0.6.8 to put it back in standby by hitting volume up and power button at same time, then waking it back up and waiting for wifi to turn on usually within 30 seconds. It does not help and actually seems to make it worse to go into wifi settings to watch its progress.
Known issue with dalingrin's kernel. Go look on in the development forums.
Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
This seems to be a common issue. I just turn off wifi before I hit the power button to sleep my nc. When I bring it out of sleep, I just turn wifi back on and it usually connects pretty quickly.
Which build are you using? And have you tried using a newer build?
The same issue with Nookie Froyo.
double post, please delete
buffnutz1 said:
Every other thread I see about a wifi problem kinda describes something different. My wifi messes up coming out of sleep. It will just keep connecting and disconnecting. Is their a fix for this? This is the only reason I left CM7.
Click to expand...
Click to collapse
I had the same problem with earlier builds of CM7, but switched Wifi sleep policy to never and am running CM7 nightly 19 and it no longer happens (still takes 30 seconds to a minute to reconnect if the nook has been sleeping for a long time). Now I have problems when I first turn the nook/wifi on!
I suggest updating to the newest CM7 and see if it's fixed. It doesn't seem to be specific to any one setup, but actually comes down to the individual nook.
I had the same problem with Froyo.
The problem went away after I swapped the OC kernel with stock one.
Hi! Can you tell me how you flush the stock kernel. I did the stock 1.0.1 via Rom Manager and it will just shutdown as soon as I login. Thanks.
I have the same wifi issue. I'm using Nookie Froyo 0.6.8. Everytime when I start my NC, the wifi turn on and off. Seems it's searching the signal? SOmetime it takes 1 or 2 mins. to reconnect! Originally, I thought that's hardware issue. It seems now this is a common issue for NC?
I read some post here, is to keep the wifi on, even when the NC sleep, but this will drain more battery.
Is there any better solution?
This happens with my rooted eclair NC as well. I'm now 99% sure it's an inherent NC issue. I though it was because I use Juice Defender to manage Wifi, but if manually turning it off can produce the same effect without the twitching wifi signal, then I'll do that instead.
Is there any app or method to make the wifi work better? Or is there any rom that can solve this issue?