Related
Is it me, or did froyo fix the "crazy screen" bug? I also noticed that my phone doesn't get as hot when it's been charging on my car dock.
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
lorin.bute said:
I'm running FRF50 since it was released. The screen issue is long gone. I use to have it a couple of times a day. I sometimes get it but that's once a week.
Click to expand...
Click to collapse
This, and I'm on FRF85B
Gotta be the best part of froyo for me, crazy screen bug fix, flash player, Jit compiler.
Which crazy thing happening are you guys screaming about? Are you talking about when the touchscreen would begin to register touches in the wrong place until the screen is turned off and on again?
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
RogerPodacter said:
Yeah that's what they are talking about. But the bad news is this problem still exists. I've had it happen many times on froyo. It's not gone at all.
Click to expand...
Click to collapse
Funny thing is that I had those issues on an AT&T-banded phone and they have gone way downhill since Froyo.
I find the granularity/preciseness of the screen better, and more responsive when, for example, you are dragging left-to-right and you start dragging up-down. However, I only do this in the browser so it could be down to better browser performance and/or JIT?
Still have screen uncalibration issues but seem to be better in 85 than 72
Does indeed seem to be a thing of the past, and on a similar note, it's improved the capacitive button accuracy as well.
Good that they've done it, but now I keep hitting them in the wrong place.
I'm using FRF91. Crazy screen bug happens with me twice a day. I don't know what I do to go away, but after a few minutes it stops by itself.
Ok I have been noticed a new problem for the past few days where the screen did not response at all when I turned on the phone. I cannot slide the unlock bar to unlock it. I had to turn it off and on again for one or two times to make the screen response again. Anyone else having this same problem?
Crazy screen occurrence definitely reduced.. however, it still happens when phone heats up significantly.. say, on a dash board while navigating. It's most definitely heat-related... so it must be hardware =(
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
vzontini said:
I'm running Geo's FRG83 and I get it quite a bit when using Skype. I've seen this problem from the beginning and haven't seen a reduction in this issue with later versions of Android. It is the only problem I have with Android/N1.
Click to expand...
Click to collapse
I've had the N1 since day one and never had this bug. But I don't use Skype...
So I love froyo and for the past week that I've had it (via ota) it has been really great, but today I began having these sudden problems:
I can't install certain apps (market or sideloaded), even though I have plenty of room for them.
Random apps that are normally stable just crash out of the blue.
The phone just keeps slowing down and things are taking longer than they should for both 2.1 and 2.2.
The phone crashed today, meaning it decided to reboot on its own accord, once when I was running a few apps at once (something that I do almost every time I pick up the phone) and was switching between them, the second time was when I had some background processes and I was browsing the web.
I was just wondering if anyone else was experiencing these problems, and if you are did it just happen suddenly one day like me or was it from the beginning? I also want to know if anyone has suggestions or a diagnosis that I should consider before emailing google.
Thanks for all the help,
Liam
Try resetting the phone to Factory (Settings-Privacy). Or if you're rooted...Wipe.
SiNJiN76 said:
Try resetting the phone to Factory (Settings-Privacy). Or if you're rooted...Wipe.
Click to expand...
Click to collapse
Does that wipe apps, settings and all other data, and is there a way to get it all back?
I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)
Where do you live? I live in florida, and this happens to me when I'm outside for an extended period on a really humid day. Once I take it in to the ac for a few, it's all ok.
Sent from my HTC Hero CDMA using XDA App
Louisiana. Doesn't seem like that would be it though. My wife has the same phone and has never experienced this problem (she has OEM 1.6 version). I am leaning towards software issue.
mar122999 said:
I recently ran into an odd problem. I updated my phone from 2.1 to 2.2 Froyo Test 4, then to RC1. I use overclocker app, launcher pro, and advance task killer mainly.
My problem is: When I use my phone, sometimes the screen will not allow me to touch icons, unlock it, ..etc. All it does it move the notification bar up and down like I am touching the top of the screen. If I keep trying to "turn screen off, back on, off, back on"...eventually, I will be able to use the phone for a couple of minutes before it happens again. I tried disabling/reducing overlock settings, uninstalling launcher pro, downgrading 2.2 to 2.1 (ICERoM 2.8). None of this helps.
Any ideas?
Note: Sorry if this was explained elsewhere. I tried searching my best.
Kernal Version: 2.6.29-Godmode-oc-bfs (toast)
Click to expand...
Click to collapse
You posted this in the wrong forum
Anyway, it could be a hardware problem, but it sounds more like a software issue. Sometimes this happens to me when the phone slows down. Are you low on RAM when this happens?
Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?
mar122999 said:
Nope. Ram is ok. 70+ Mb. Seems like it all started when I upgraded to 2.2. At times, the phone is unusable. Right now, it has been working perfect for a couple of hours. I downgraded to 2.1 thinking that 2.2 was the problem, but 5 hours ago, I encountered the same problem with 2.1. So that can't be it. Screen protector maybe?
Click to expand...
Click to collapse
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.
derekwilkinson said:
Yeah, could definitely be the screen protector is changing roms doesn't help. Could also be a bad touchscreen, but most likely screen protector.
Click to expand...
Click to collapse
+1
when i had one on my phone it would do this. i think its static tricking the touchscreen.
Hello there,
So, I installed JPM, Root and CFLagfix with Autokiller. Everything works to my liking, and is snappy enough for me until Voodoo comes out.
But here is my prolem, and since this is a phone, it is a big problem.
I can make calls out no problem with great reception, and great call quality. But as soon as my phone recives a call, it vibrates once, and then I see a forced close, and I guess the dialer is crashing. The caller just gets one ring tone, and then they get hung up on as well. I get a notification that the network is gone, but about 1 second after I look at the notification, I get full bars again. It happens the same way every time.
Any ideas?
Edit:
I found the solution.
What I did was upgrade to Froyo, and then apply ALL my settings from Titanium back-up from my 2.1 ECLAIR back-up. I even applied system settings...and that is where the big mistake was. The two system settings aren't compatible.
So I actually went back to Android 2.1, and then used Kies to upgrade to Froyo. And I left the settings alone (and only imported apps from titanium), and everything works perfectly.
And I am digging this Froyo (with CFRoot and CF Lagfix)...it is as good as My 2.1 rooted and lagfixed, with some extra features.
Had (sometimes still have) almost the same problem, mostly on JPK. Since i flashed to JP6 its better.
Sometimes when i make or receive calls the phone apk crashes and the phone turns offline mode on by itself.
Dont know why.
I'm also experiencing this problem. Did you guys restore backups before it occured? I think it might has something to do with some theme that may not be supported in Froyo?
Really looking for an answer, cause this sucks!
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
have you tried a screen protector? my screen wasnt the best for precise touches but since i put a screen protector on and clean the screen regularly it has since changed my problems to almost non existant.
Sent from my NookColor using Tapatalk
Others may be able to help you more than I can with exactly when the CM7 may be doing this, but returning to stock to find out is actually not hard at all.
In the development thread there is a post that has the 1.2 stock zips (one keeps CW in place, the other returns it completely to stock). Which ever one you pick it's still just as easy to return to stock as to reflash CM7 again. This is especially true if you used a SD card with CW to flash (which is what I do), since when you want to go back to CM7 you won't have to worry about flashing CW to emmc again.
angelic.pariah said:
No matter what I do and however many times I flash cm7, I seem to have erratic touchscreen behavior.
The nook is BRAND NEW (two days) and I flashed it with cm7 7.0.2 stable (after phiremod's 6.0 & 6.1) and flashed it about four times now.
I have tried it with the OC and without.
It's not the SD - it doesn't matter if it's in or not.
Not the wifi, since I didn't even set it up the third and fourth time - it was too erratic to even try.
Plugged in or not... still the same problem. Doesn't seem similar to the other forums topics about touchscreen issues WHILE charging.
Screen is near spotless... no smudges.
It is important to note, that it waits until I have done a few things to start going crazy. I restart it and it's fine, until I do some cpu intensive stuff - live wallpaper is the simplest activity that causes it.
Any ideas?
I have also tried NSR (screen re calibrator) to no avail.
Would love a quick fix rather than re-installing stock and returning it and convincing them to replace it. I am not sure if it does it with stock... didn't wait long enough to find out before flashing it.
Click to expand...
Click to collapse
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
dalingrin said:
Hate to say it but it sounds like it might turn out to be a hardware issue. This is not a CM7 issues that I've seen from anybody.
Can you describe the behavior in more detail?
Click to expand...
Click to collapse
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it. At one point I almost purchased an app from the market before I had to power down.
I will return it to 1.2 stock and report back. I was mainly wanting to know if these was a commonly reported issue or not. I guess it's not. Thanks for the help everyone!
angelic.pariah said:
It seems to start selecting things on its own after I have been using it for a while. It's difficult to describe except that there isn't really a pattern... it selects something different and keeps at it.
Click to expand...
Click to collapse
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
bucketheadmn said:
So my NC started to do the same thing last night. I have been running CM7 (at 7.0.2 now, but nightlies before then with dal's OC kernal) for quite a while now with no problems. Only thing I did last night was to delete about 1GB of ebooks off of my NC and reload them through Calibre.
I left it alone last night after it started doing it and then this morning it started doing crazy touches again. I was in Aldiko and it was selecting books and turning pages at random. Rebooted and it seems to be fine for now. Little odd though considering it has been running perfect for a few months.
Click to expand...
Click to collapse
So now I have installed nook stock 1.2 and NO PROBLEMS. I have run everything trying to get something to happen, and nothing.
Is it possible that I installed something the wrong way with cm7? Could I have used the wrong CWM version (3.0.0.6)?
Should I try cm7 7.0.2 or something else again?
I would try and return it, but I can't recreate the problem... if I could, I would be in their face right now.
Thanks for the help so far.
I think I solved it!
The newest nooks (in the last week or so) have 1.1.0 factory stock. Apparently there is a glitch that has been reported a lot recently about handling the touchscreen AND the SD card. These were fixed in the 1.2 upgrade. SO...
1. I flashed factory stock back on (in this case I went back to 1.0.1)
2. Then turned it off and "restored factory" settings using "Power+N" to turn it on. Repeated that a second time to get B&N's factory reset screen to come up.
3. Pressed N twice to accept restore prompts.
4. Upgraded to 1.2 (no glitches already by this point with touch or SD)
5. Booted CWM 3.0.0.6+
6. Formatted /system & /data
7. Flashed phiremod 6.1
8. OC'd to 1.1Ghz
...and DONE. No problems so far. I still see the "Read Forever" opening screen, but it still works wonders. WAY better than before.
I am still having issues with Wifi, but I can deal with that.
Now to attempt dalingrin's OC to 1.3!
Thanks guys... hope this helps others.
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
I had weird touchscreen issues when using the interactive cpu governor. I later found only performance is supported. Using performance setting, everything works much better.
queseyo said:
I think they call it "Touchscreen goshting". It started happening to me when I rooted the nook and the keyboard would go crazy. Now in CM7 7.0.2 with latest kernel, it happens more frequently. About 5 minutes in from boot, fast random touches occur. Most of the times this gets fixed by pressing the power button to turn the screen off (sleep), and on again. I guess it could be a hardware issue where some devices are affected. I haven't tried any recalibration apps to try to fix it yet, its kind of annoying when it happens in fast intervals.
Click to expand...
Click to collapse
I had the same issue. I exchanged it the other night and now my new one does not have the problem. It probably a hardware issue...i hope you are still under warranty!