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...
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!
Sup,
I experience lag frequently. A lot of times I can feel something in the phone spinning or vibrating as it comes out of the lag. the vibration isn't as rigorous as the notification vibrations. Also sometimes it will lag but not come out of it and completely freeze then restart itself. The freeze/restart seems to happen when surfing the web.
I'm running serendipity 7 build 2. Its happened on serendipity 6.x also. Not sure if its rom related or just my phone failing. Anyone experience this?
I should add that I have 9.31gb available out of 13 total.
Sent.
I've had similar lag and reboot issues on Serendipity 7 don't know why, but you can always just try another ROM and see if the problem persists.
Sent From My Captivating Shanna, yes I Named My Phone get over it.
nawlage said:
Sup,
I experience lag frequently. A lot of times I can feel something in the phone spinning or vibrating as it comes out of the lag. the vibration isn't as rigorous as the notification vibrations. Also sometimes it will lag but not come out of it and completely freeze then restart itself. The freeze/restart seems to happen when surfing the web.
I'm running serendipity 7 build 2. Its happened on serendipity 6.x also. Not sure if its rom related or just my phone failing. Anyone experience this?
I should add that I have 9.31gb available out of 13 total.
Sent.
Click to expand...
Click to collapse
A couple things that come to mind, one is the vibrating sounds like something is F/C'ing. Take a look at your applications, what is running, do you know what you're trying to run when it vibrates? Also take a look at your system resources, I get lag if I have too many items running and system mem gets too low
"Most" issues tend to be software related so that is where I would focus my attention. If all else fails, reinstall your ROM
kangi26 said:
A couple things that come to mind, one is the vibrating sounds like something is F/C'ing. Take a look at your applications, what is running, do you know what you're trying to run when it vibrates? Also take a look at your system resources, I get lag if I have too many items running and system mem gets too low
"Most" issues tend to be software related so that is where I would focus my attention. If all else fails, reinstall your ROM
Click to expand...
Click to collapse
It happens the most when I am browsing the web. I have been using xscope for a long time. First the free version and now pro version since it was faotd on amazon. It happened with both versions. although xscope could be the problem its not the only culprit cuz it happens when im not browsing the web also. Maybe I should install logcat and check it out after the next time it happens...?
Sent.
I noticed today that it would sometimes vibrate when exciting out the gallery with the back button. I was a couple folders deep and hit back like 3 times so its like it got over-loaded or something but didn't fc.
Sent.
Lag & auto shut down
My captivate with serendipity 7 initially seemed perfect. But after a couple of weeks of usage, it started becoming slow. I face quite a bit of lag, automatic shutdowns and poor battery. I do have a few apps running in the background, but there was no lag when i was using cognition 4 or CM7. When my phone shuts down automatically, I have to take the battery out and put it back in to restart it. Holding just the power button doesn't switch it on.
ramahari said:
My captivate with serendipity 7 initially seemed perfect. But after a couple of weeks of usage, it started becoming slow. I face quite a bit of lag, automatic shutdowns and poor battery. I do have a few apps running in the background, but there was no lag when i was using cognition 4 or CM7. When my phone shuts down automatically, I have to take the battery out and put it back in to restart it. Holding just the power button doesn't switch it on.
Click to expand...
Click to collapse
That would be SOD(sleep of death) where it is in too deep of sleep and can't wake up, were you UV?
Sent from my SAMSUNG-SGH-I897 using xda premium
ramahari said:
My captivate with serendipity 7 initially seemed perfect. But after a couple of weeks of usage, it started becoming slow. I face quite a bit of lag, automatic shutdowns and poor battery. I do have a few apps running in the background, but there was no lag when i was using cognition 4 or CM7. When my phone shuts down automatically, I have to take the battery out and put it back in to restart it. Holding just the power button doesn't switch it on.
Click to expand...
Click to collapse
Not to be an ass but you sorta jacked my topic. I'm not experiencing sleep of death. My problem has to do with the phone freezing then restarting itself.
Just don't want more posts further veering of course and hindering a solution for me. Thanks.
Sent.
Just an update...
I haven't had any freeze+ restarts since my first post. Still some occasional lag but not nearly
as much or as bad as it was.
Funny thing is I havent changed anything.
Sent.
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
I would try reflashing back to stock. Reinstall CWM, then try installing the ROM again.
Beyond that, maybe you should PM the guy who made the rom.
brianosaurus said:
I installed Thrillseeker 3.1 about 2 weeks ago, and have been noticing a few things. Sometimes the phone stops responding to touches for a while, like its locked up, or lagging, or maybe the wrong CPU governor. I don't know what's going on. Sometimes it randomly resets. One repeatable problem is that if I turn Wifi on, then off, then on again, the phone resets.
I have tried the 1.30Ghz kernel included in 3.1, the 1.38Ghz kernel, the 1.0Ghz "Saver" kernel, and the 3.12 update, but the same reset-on-wifi problem persists.
Is anyone else having similar problems? Simple fix?
Click to expand...
Click to collapse
I haven't had the reboot problems since 3.12 update from 3.11 clean install. Have had lag issue a couple times..for me restarting holo launcher corrected...tried to recreate wifi issue bit is working for me. All three kernels are very similar the saver has 1.3 and 1.2 disabled and the hotplug gov tweaked
Also posting this in my thread might get you more help.. since your running thrill seeker its ok to post problems you are having in that dev thread as others may be having same issues and ill see it quicker and try to help fix it if I can.
Sent from my LG-P925 using xda premium
yeah, i'm a noob
I'll try going back to stock and then reflash the latest thrill seeker. I would have posted in the dev forum, but I don't have 10 posts yet, so I'm restricted from posting in dev. only 8 more to go
3.12 hasn't had a random reset on me, just the wifi reset, but that one "works" every time.
Thanks,
brian
found lag problem and found possible fix
lag problem on thrillseeker 3.11/3.12 appears to be the CPU somehow resetting the Max MHz to 100MHz after the phone sleeps for 10-15 mins. Having Romtoolbox installed, then adjusting the CPU sliders quickly bypasses this issue. Although a true fix is in the coding, this workaround appears to be permanent once preformed. At least we now know it is not a flaw in the Rom as far as an overload or hang-up problem. I have not experienced the Wifi issue yet. If I can get a heads-up on how to induce it, I can look into it. Great work on the Rom!
problems im having
The rom itself is near perfect to me...I give thanks to all that put the hours and hardwork into this
I am a complete noob so any help or answers I will greatly appreciate. The only trouble I have from rom so far is if I'm using the browser while its plugged in.. might be a bad install after all. I really jumbled a few things like not making a nandriod. So I'm kinda stuck with with out a return to stock option...I have been trying to work through this but im a bit unsure how to get a stock Back on here. ..????? Any help....... back to rom I love thrillseeker 3.1....I been testing what I need in a rom and well I couldn't be happier that this rom seems to to do the job and then some....everything works perfect ....like I said the only thingthat seems fuzzy is when I plug in to wall charger and then it gets glichy.....
cpu
I adjusted sliders as well the second one seems to revert back to 100mhz often so its not a permanent fix. It does help....
Yeah. Funny thing. My phone broke (cracked screen), so I did an exchange at best buy and this rom works just fine on the new one. I guess my old one was kind of janky on the inside.
Sent from my LG-P925 using xda app-developers app
I'm sitting on the couch...look over at the phone and the screen is off, but there's all these weird yellow-ish, orange-ish vertical lines all over the screen. Power button does nothing. Plug it into the puter and adb reboot-bootloader it and the bootloader looks all jacked up. All kinds of crazy colored bars going up and down and a funky, zoomed in resolution.
0.0
I DIDN'T EVEN TOUCH IT!
I get into TWRP, which also looks pretty jacked up and flash my most recent backup.
Everything's fine again.
What in the SERIOUS **** was that?!!?!
rmp5s said:
I'm sitting on the couch...look over at the phone and the screen is off, but there's all these weird yellow-ish, orange-ish vertical lines all over the screen. Power button does nothing. Plug it into the puter and adb reboot-bootloader it and the bootloader looks all jacked up. All kinds of crazy colored bars going up and down and a funky, zoomed in resolution.
0.0
I DIDN'T EVEN TOUCH IT!
I get into TWRP, which also looks pretty jacked up and flash my most recent backup.
Everything's fine again.
What in the SERIOUS **** was that?!!?!
Click to expand...
Click to collapse
Imminent hardware failure. RMA it -before- it does it again.
c0LdFire said:
Imminent hardware failure. RMA it -before- it does it again.
Click to expand...
Click to collapse
DON'T SAY THAT! lol
It's fine now, though...
i wouldnt say that at all .... do you UV at all?
Lg...
Sent from my Nexus 4
Its probably a screen problem. So its RMA time lol
same exact thing happened to me twice in the first month I had the phone (had mine since Nov). I was running cm10 at the time, freaked me out pretty bad. screen was flickering too afterward, I had to reboot a few times to get it back to normal. after the second time I went back to stock completely (no root, locked boot loader, stock recovery) and never had this or any problem again
Sent from my Nexus 4 using xda app-developers app
Hmm...
Yes, I am undervolted. I was running AOKP Mako jb-mr1_build_3 when it happened. Flashed my most recent backup and it's fine. I was running build 2 of that ROM when I made the backup.
I tried to flash back to the build 3 version of this ROM after getting the phone back to normal but was getting the UI force close thing (flash a ROM or kernel and, when you reboot, you get repeated, rapid fire UI force closes...anyone else have that happen?) so I'm just going to leave it at build 2 for now.
That's what happen when you underclock
supersain08 said:
That's what happen when you underclock
Click to expand...
Click to collapse
Definitely sounds like an UV issue. Do you have a nominal or fast processor? What kernel and UV settings you running?
Sent from my Nexus 4
Was it .. hot?
Hot? No.
It isn't underclocked, it's undervolted.
Well...it was. I put it back to stock. Hopefully this won't happen anymore.
My phone does the same about every other week...
Sent from my Nexus 4 using xda app-developers app
I've had my screen flicker for several minutes before. I was undervolted and on CM at the time. Putting it to sleep and turning it back on, didn't help. However after a restart it was perfectly fine again. I undervolted back to the same level right after and am currently running it at that level (been about 2 months) and it's never done it again.
I don't recall the screen ever changing colors like you mentioned though. I have a fast binned cpu and my kernel was motely. I'm thinking it was just a glitch with CM.
I've noticed that one out of maybe 100 wake-ups doesn't turn the screen on when you press the power button. One day I left it like this for 30 seconds thinking it will come on, but instead the screen started fading to white from black - sort of like the brown starts on burning paper - and then when I pressed the power button again the screen was flickering. Seems to be a custom ROM/Kernel thing.