Related
Ever since I started flashing FroYo Roms my touchscreen has seemed to have issues. I saw people noticing the same thing in the early stages of the AVA Sense FroYo, then it seemed to go away for everyone else. I have tried multiple ROMs tried toasted kernel and stock kernels with every ROM, nothing seems to work.
Does anyone know the remedy? the symptoms are random non response. Sometimes I can't answer a call, sometimes I have to press twice on something to select it, and sometimes it just seem as accurate as it used to be. Before I did my first FroYo ROM, I did the wimax and radio update.
Sometimes I have to turn the screen off then on to regain control of the phone.
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
bigblueshock said:
Have a VERY weird issue going on. I've been using Burnt Droid 1.4.2 by Netarchy since it came out. I decided to flash his new 4.3.4 CFS-NoHavs,noSBC, with static undervolt (i wanted to try and see if it was stable since I had success using undervolted kernels last year). I used proper procedure and cleared cache/dalvik-cache before flash. I downloaded the new Angry Birds from amazon and started playing it for a few minutes phone started lagging very bad, then had to restart. I said forget this; undervolt is probably causing this, and reverted back to the original 4.3.1-cfs-nohavs-nosbc which I never had a problem with(used proper procedure above to flash back kernel as well).
Now a day later at night, I decide to run my phone down because I'm trying to recalibrate my battery(I'm at less than 10% at this point). So I load up Wifi, turn on Pandora, and browse the internet. Not even 5 minutes into it, here's whats occuring in order:
1) Bad lag.. Pandora starts stuttering, so I hit the home button
2) HTC Sense restarts, It doesn't even force close, or at least it's not telling me
3) a Hot restart occurs a few moments later... (no white boot screen, just starts bootin from ROM screen)
4) At this point, sometimes its still laggy, sometimes it's fine. If it's laggy I must do a battery pull because It will keep looping to this point.
I can rinse and repeat this running pandora + browsing the web, and the same 4 steps above will happen within moments of eachother. I've been using this ROM since January with no major problems like this
A few side notes:
-I have Evo hardware 0002 (launch day evo)
-Rooted with Toast's original root method, eng .76 boot loader
-Newest radio/PRI/NV/Wimax
-My phone does not randomly reboot on me normally. Reboots only occur when following the above steps.
-I do not use Set CPU
Here is where I am very superstitious. I've been closely monitoring the "Boot looping + no Recovery Access" forum, and similar forums to this. Within the past few months I have tried out a few different CM7 nightlies. I have never flashed RC2 but I have flashed some after and before and tried those out for a while. I just hope my phone isn't starting a dying phase in relation to the problems people are having now.
Is there anything else recommended before I end up doing a full wipe and reflash the rom?
Click to expand...
Click to collapse
I'm not really sure what's causing your problem, and If i was in your situation, I'd most likely do a complete wipe, including calkulin's format all, and either restore a good nandroid, or reflash the rom from scratch.
That said, I don't believe CM to be 'dangerous' to run or anything like that. Yes, it is odd that an increasing number of people are reporting somewhat major issues, with boot looping the splash screen, and being permanently stuck there. However, that doesn't mean CM is the cause. It does seem to be a common denominator in the people that this has happened to, but there are soooo many other variables that come into play with something like this. There is no proof that CM caused it, but it does seem odd that everyone it happened to was running CM. Also, I'm sure there are thousands of CM users, and a select 8-10 people have reported these issues on here. That's a very low percentage, overall. With all that said, I myself won't be running CM in the near future, either until it's confirmed or denied that it has anything to do with these issues. I'll just be playing it safe, just in case.
I'm stock everything, no root or mods and it restarts at the 4g screen skips everything else...
Sent from my PC36100 using XDA Premium App
I think I will do the format all and completetly wipe it and reflash the rom from scratch. Thank you!
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Saturn2K said:
This problem only really happens after my phone has been on for days at a time. I have had this problem on the latest stable and latest nightly for CM7 (each one cleanly installed after a total wipe).
What happens is that most screens are replaced with entirely black ones. The most consistent example of this is the settings screen. The first Settings screen (which shows Display, Sound, etc) loads correctly. If I click on any of those, I just get a black screen. This will happen in other applications too, like Baconreader or Browser. Also, another connected issue is that the lockscreen won't animate once this problem starts. I can drag it down to unlock, but the rotary wheel won't move at all. If I drag to the right to load my custom app, the lockscreen won't go away and it will force my to pull the battery.
Has anyone else run into this problem? I'd just like to know I'm not alone. I'm not really expecting a bugfix, especially when I'm not even posting a Logcat.
Click to expand...
Click to collapse
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
bootny said:
Did you fix permissions?
midget tossing is habit...2010 midwest regional champion... hw 001
Click to expand...
Click to collapse
Next time it happens I will, I'm just afraid it will break Facebook/SMS integration like I've had happen before.
It's just so weird since it breaks everything. The lockscreen, the options, Pandora's station list, the browser, and it goes on and on. It's like there's some sort of display mode that gets screwed up.
dom085 said:
I suffered this same thing today. Thankfully a full restart fixed out, but I would love to learn a real solution.
Click to expand...
Click to collapse
What version are you using. I'm going to try to install nightly 77 today after a fresh wipe.
I was seeing the same thing. Now I'm trying to figure out why my data speeds are so painfully slow on CM7 so I can't offer a fix. Flashing back to Warm to troubleshoot 3G.
I get these issues all the time no matter what kernel or nightly I'm running. It has forced me back to sense roms lol
Same problem here. I updated stable mod from stable mod. Reinstalled. Going on 4 days, no issues so far.
Sent from my PC36100 using XDA App
I have the same exact issue. This never happens on a sense rom. I did some tweaks to my system over the past week and I haven't had to reboot since this past Saturday or Sunday. I thought I had fixed it!
Then...
My phone started doing it this morning after I turned on 4G at work, literally as I was writing this post it started doing it. I then turned off 4G.. and it instantly went away. Turning back on 4G and it isnt doing it right now. Now my phone is doing something weird with go sms pro... when I get a text and I respond via the pop up message.. once my text moves to a second line I dont see what I am typing anymore... and now it has progressed to where the pop up box isnt refreshing after I send a message (this is all happening while I am typing this post). Now the phone has become laggy and somewhat unstable... rebooted! All is well. So I went roughly 4-5 days without a reboot... where as before I had to reboot at least once a day.
Thats about the best I can get with these settings:
CM7 7.0.3.1
Savaged Zen 2.6.38.5 CFS > Using SavagedZen Governor, min 384 max 998
Displaying some animations (read somewhere that is a "fix".. or helping extend the time it takes for the Black screen of death to appear).
This is after several full wipes, several when I was running Amon RA recovery 1.8 then updated to the latest and did it two more times. After upgrading Amon and wiping I did not use any backups and started completely from scratch.
So I am not sure what else to do. Some people are getting this, some are not.
Figured I'd cross post this as it seems to be an issue for a few people. ( http://forum.xda-developers.com/showthread.php?t=1951699 )
I've noticed this issue since first getting my S3 in July. So I do know it happened with 4.0.4 and now with 4.1.1. I've never used the "Stay Awake" option in the dev options and it still remains off. I've had the issue with both "Smart Stay" on and off. I've tested it with all screen time out times, as well as going through the trouble of factory resetting the device and nothing changed. The only solution I've found is reboot the phone and it will work again for a day or so until I notice it again. Very annoying and would love to find a solution to this!
I just started having the same issue. I was using Black Jelly's JB ROM for like 2 weeks without the problem then I flashed the LK3 modem and it started happening. I did a full wipe and flashed the ROM from this thread - http://forum.xda-developers.com/showthread.php?t=2034844 last night and I'm still having the problem. My touch key lights stay on all the time too along with the screen not timing out.
My S3 has been stock from day one. I also got mine a few days after it was released, starting to wonder if its a hardware issue?
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
I've noticed it on a replacement S3 I got when it wasn't an issue with the prior one. The new one (as with the old) is stock, updated to JB when I got it. GFs phone does the same.
geiswiz said:
I never had this issue on stock/rooted ICS and I've had my phone since launch. I also didn't have it until about 2 weeks after I was running a custom JB ROM. It's weird that it started after I flashed the LK3 modem. I flashed back to the original modem I was on and it is still happening. I also flashed another JB ROM and it's still happening. A reboot fixes it, but it always comes back. Today I noticed that after missing a call it started happening, then after missing another call hours later it started working again.
Click to expand...
Click to collapse
This is interesting. I've been noticing this issue ever since I updated to 4.1.1 some weeks back, but had not considered any connection with missed calls. Among the dozens of reports I see online (with not a single one resolved), I found another thread that mentions it happening after missing a call (or receiving an SMS).
I completely wiped my phone and flashed a stock 4.1.1 rom two days ago and noticed this happening again while sitting at my desk today. I did miss a call earlier, so I think there is something to that suspicion; I rebooted the phone and sure enough the screen and touch keys timeout as they should. I just received a text and that didn't trigger the issue, but I'll have to wait til I get another call to know for sure, or until I get home and have the time to test it.
Ok, yep, it definitely is somehow triggered by missing a call, but it seems to only happen some time later after the last reboot. I had rebooted my phone yesterday, missed a call not too long after, and the keys and screen would shut off normally. But I just missed a call right now and sure enough it's acting up again...
I got my Nexus 7 when it first came out last year, rooted it, installed TWRP, and have been on several different ROMs since. Didn't have any issues with random reboots for several months. Early this year, I started having an issue where the tablet would freeze while I'm using it, then automatically reboot itself. I thought perhaps it was a problem with the ROM I was running, but I had switched ROMs a few times after that, and every single ROM I've been on since then has had the same problem. It usually only happens when I'm browsing the Internet (with Chrome being my browser of choice), but I've had it happen once while using the camera app, as well.
The other day, I upgraded TWRP to the latest version, and I installed the 4.04 bootloader in preparation for Lollipop ROMs. I was hoping on some slim chance that perhaps an upgraded bootloader might fix the problem, but I'm still getting random reboots.
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
mrw1215 said:
I know I've seen people talk about random reboots as well, but in the past, I never saw anyone find any kind of solution. Is there one, or is it one of those things I just have to live with, at this point? It's odd to me that I didn't start experiencing this issue right away, and that it only started several months after I had had the device. To me, that makes it seem like it's not a hardware issue/ defect, but I guess no one has been able to pinpoint what the problem is, why it occurs, and how to fix it, huh?
Click to expand...
Click to collapse
I'd tend to agree with you it's a software thing. However, my approach would be a bit more radical than yours: that I would erase everything, including formatting the internal storage twice (after making a backup, of course), then install a completely clean rom, use it for a while to make sure it doesn't act up again before restoring any apps.
On the side, I've seen a Nexus doing random reboots whose owner had opened the back and bent the cover somehow, which slightly depressed the power button. While the button operated normally, this condition forced it to "click" randomly, which caused the reboots. It stopped after the owner replaced the back cover. You might want to check this part. Good luck.
Most of the time, random reboots are kernel related. If you are overclocked try to set max CPU lower and see if the problem fixes itself. If you don't overclock try installing something like Trickster Mod, and lower max CPU to see if that helps. What ROM and kernel are you running?
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."
I always recommend flashing back to stock to rule out software issues. If it continues, you've got a hardware issue.
I haven't really messed around with kernels, I've typically just used whatever was included in a particular ROM, and I never adjust to overclock or anything like that. I don't remember what all the ROMs I've been on are, but I've been on CM before, and I'm currently using CleanROM. I think the only time I ever specifically tried a different kernel was a while back, when I flashed an Elemental kernel, but I've since wiped and been on a different ROM.
For now, I'm trying to hold out wiping anything until a good, rooted build of Lollipop is available, at which point, I'll try wiping out everything, including internal storage, and see if that helps.
I guess I could also try flashing back to stock before I do that, though. I think I've seen one stock ROM for the N7 floating around. The only problem is, it's really hard to "test" this, because the reboots are very inconsistent. The other day, after I had updated the bootloader, I was browsing Chrome for over an hour before I got a random reboot. One time, I was browsing Chrome for an hour and had 4-5 random reboots within that hour. So, that makes it difficult to determine if it's fixed in a timely manner. :/
Alright, so now that there's a proper build of Lollipop out, I did a factory reset and wiped internal storage (twice), and I'm now running stock Lollipop. I spent about an hour or so getting everything set up, and no reboots thus far; but the reboots mainly occur when I'm using Chrome, and I didn't really do any browsing, as I was getting all my accounts and apps and whatnot set up. Hopefully within the next couple of days, I'll have used it enough to get a good idea as to whether or not I'm still experiencing issues.
So far, no reboots, though i don't want to jinx it, heh... I'll be glad if the issue is finally fixed, but I'll also feel kinda dumb that all it took to fix it was something as simple as wiping internal storage and/ or reflashing a stock ROM. Lollipop is pretty nice, as well.
Yeah I'm using a custom version of L myself. You need to flash custom kernel to get working root access with SuperSU BETA 2.19
Sent from my 2013 Nexus 7
"Until death, I will remain a Dirty Unicorn.."