Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Castaway78 said:
Hi all -
I'm on AT&T, 100% stock, non-rooted, etc. I upgraded to JB last night via Kies without issue.
However, ever since the upgrade, my phone won't go more than 5 minutes without freezing and then crashing.
It's a very odd behavior... the screen will still animate. So, if I'm playing a game with a timer, the timer will still count down. But all touch input (including menu/home/back) does nothing. Home/back don't illuminate or do anything, but they do provide haptic feedback. Power button does turn the screen on/off.
Eventually after a few minutes, the lock screen comes up with the "tip" even though I've clicked to never show it again. However, it barely registers a swipe to unlock when it freezes again. At that point, it will usually self-reboot.
I've tried to enable some of the developer options to see if maybe there was a rogue program that was incompatible with JB, and maybe causing the issue, but I couldn't see any correlations.
I really want to avoid doing a factory reset if at all possible, as I have a game that I worked really hard on to beat a few levels, and I'd hate to lose my progress.
Anyone have any ideas on what I can try?
I should note that uninstalling programs is iffy... sometimes it works, other times it just uninstalls indefinitely.
Thanks!
Click to expand...
Click to collapse
This sounds somewhat familiar to my experiences with JB. I rooted right away with the stock JB and had freezing / crash issues. So I then went pure stock and had issues (un-rooted). I then tried a custom TW-based ROM called BlackJelly and had issues. Now I am on CM10.1 which is AOSP JB4.2.1 based and things are even worse.
There seems to be no JB ROM that is stable for my phone. Getting very tired of this.
See my thread for details:
http://forum.xda-developers.com/showthread.php?t=2044769
- Ed
Strangely enough, my issue ended up going away. I think it was a rogue program that needed it's dalvik cache rebuilt. Once uninstalled, the phone worked great. Not sure what app it was.
Related
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Do you have setCPU ?
i know sometimes when people set screen off properties to low it freezes and needs a batt pull
Funny enough, I guess the problem started after I installed that. I cleared its settings and cache and uninstalled the program hoping it would fix it, but no dice. I figured that would fix the issue if it was related
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
I tried that once, didn't seem to help but I will give it another shot.
I am running stock DK28 ROM, maybe a fresh install will help?
o and you wouldn't happen to be on viper rom would you ?
iSaint said:
i guess reinstall it and set the screen off properties a little higher maybe
400 max
100 min
ondemand
(My settings)
or play with the settings till it fixes since im guessing you never reinstalled the rom your on
Click to expand...
Click to collapse
Set it at 200 min.
not running viper ROM. I am running stock froyo with root access.
DiGi: Is that what you have it set on? I thought I read somewhere not to set it that low.
I was running on 200 min just fine. I haven't had setcpu on my phone for a little while though. I think 100 is too low and causing the problem. 200 didn't cause crashes for me.
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
djbacon06 said:
I've been playing with the settings on SetCPU but to no avail. My screen still won't wake up at random.
Any other thoughts? I have again, un-installed SetCPU and am no longer using it but the problem still occurs.
Click to expand...
Click to collapse
Odin
reflash your rom
probably something went wrong when flashing
this happens to me when my battery is low (stock dk28)
it's working for me
djbacon06 said:
Hi everybody,
After running stock DK28 for a while, I decided to give rooting a try. I was able to root with no problem. However, after a couple days now, I have noticed that when my screen times out, sometimes it is unable to wake up. In other words, the screen turns off, and will not turn back on despite how many times I press the power button. The only way I am able to fix this is by taking out the battery and re-starting the phone.
The problem seems to be very intermittent and random at best. Any ideas what may be causing this?
Also on an unrelated note, I have noticed that if I leave my screen open and allow the phone to time out, the physical keyboard will light up and turn off several times by itself (this has been going on since I installed DK28). Not necessarily a problem, but kind of weird.
Thanks in advance for the advice!
Click to expand...
Click to collapse
Recently changed my phone to android and my phone wouldn't wake up every time it goes to sleep more. (Radio 2.10.50.2)
looked and tried a lot of suggestions (format SD, flash ROM, update setup.txt file and etc) but nothing worked until I flashed the new radio 2.14.50.
And it's been working fine for a day now (finger crossed).
Do you have adjbrightness? Theres a problem with it on galaxy s phone where it won't wake up that they haven't been able to fix and that may be your problem.
Did you ever figure out how to fix this "no wake up" issue? I had this problem out of the box with my mini. So does my friend.
Anyone else getting this error? After reading the two main errors seem to be faulty camera hardware and bar code scanning apps. I uninstalled my bar code scanner and the problem persists. There is a small dent next to my flash under the camera but this came with the phone and my camera worked for a while. Taking the battery out and putting it back in fixes the problem about half of the time, but only is good for one to two uses. I'm thinking of sending this in, but I'm waiting until the SGSII HD is out in case they offer to replace it with any phone. Wishful thinking, I know.
And here's the error:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
HJZS2K said:
Are you on the stock rom? I got that yesterday but a reboot fixed it.
Click to expand...
Click to collapse
Stock ROM not rooted. No modifications what-so-ever.
8mileroad said:
Stock ROM not rooted. No modifications what-so-ever.
Click to expand...
Click to collapse
Try doing a factory reset. Sometimes an app installed on the phone might screw up with a hardware's function. For example, I've always use Screebl Pro on my phone to let it control how my screen turns off. I decided to try their new Beta version. A few days later, I cannot seem to manually turn off my screen by pressing the power button. Every time I press the power button, the screen will come back on on its own. I can try up to 4-5 times before it eventually goes off. I though my phone finally broke as I tried uninstalling and reinstalling apps, changing settings here and there to no luck. I finally realized about the beta Screebl I had installed, and decided to disable it. The moment I did that, the phone was back to normal, no weird things happening to it.
So try doing a factory reset first before sending it back.
Strangely enough uninstalling Reconage has seemed to fix this. Can anyone else confirm it breaks your camera? The comments don't say it does so it must be something with the Nitro.
I get it too on cm7 all the damn time. I can record 1 video then after I stop, it messes up and I have to reboot to record again.
Any more definitive answer on this issue? My wife's Nitro HD has started giving this error in the last few days and no amount of rebooting seems to be fixing it. She is stock plus a few apps. I uninstalled nearly everything that uses the camera, reboot the phone, and still have the problem.
Alternatively, is there a way to see what apps were installed/updated by date? The last photo she took was on 6/13, so if we can figure out what apps have been updated since then that might help us get to the bottom of the issue.
I've had this problem sometime over a month now, can't remember if I did anything to make it like this. I made a post somewhere about it happening the 17th of May, so it started somewhere before that.
My phone will freeze for 2 seconds and then reboot itself.
It started while I was on stock 4.0.2 and now I'm on stock 4.0.4 IMM761. I have a GSM Galaxy Nexus.
It only happens just after the phone has been woken up and something is started. The most common (as it's my go-to-way of forcing it, to see if it's still there) is after waking up the phone, sliding down the notification bar and pressing "settings", which doesn't open but the phone freezes and reboots itself. I first discovered this when I wanted to go in there to change screen brightness. It's also happened when I went into the notification bar and pressed a battery app there. It doesn't matter if I'm doing it in the lock screen or after the lock screen.
It's also happened when I wake up the phone and enter the camera through the lock screen.
It also regularly happen if I set an alarm in the morning. When my alarm is suppose to play it freezes and reboots, and when it's rebooted, the alarm has been cancelled without ever playing.
It doesn't need to wake from deep sleep to do this, I've had it happen mere minutes after trying to see if it's there.
I don't know if it has something to do with this, but the 21st of April I tried to do the "clear google services framework" trick to force 4.0.4 ( I was on yakjuxw), but it did not work and I remember my phone acting janky and I was scared it messed something up, but I seem to remember it getting better. I can't remember what exactly it did though.
I've read that 4.0.4 would fix the reboots that a lot of people were having (don't know if it was the exact same kind of reboots as mine) so I did this to make my phone a yakju (translated from Danish):
http://translate.google.dk/translat...at-modtage-opdateringer-til-din-galaxy-nexus/
I did that the 8th of June, and it worked flawlessly and I was on 4.0.4 IMM761 in no time. Unfortunately it did nothing to stop these reboots.
As part of the process of making my phone a yakju I, of course, did a complete factory reset, although I did make a copy of my entire SD and transferred everything over again after the process.
These past two weeks I've tried the following to fix it:
Clear cache partition in recovery.
Clear google services framework.
Clear media storage.
Tried to uninstall many apps, 2-3 a day, to see if they were causing it, re-installing them when I still had the same problem. If it's an app causing this I've yet to find it, but I find it weird that an app could be causing this.
It happens once a day, but never close to each other. It seems that some time has to pass before it can happen, and it only ever happens just after the phone is woken up, either by my alarm or by me opening the notification bar and pressing something there.
Please help me, this is unbearable.
Another thing, yesterday I tried to let it run without me pulling down the notification bar and pressing "settings", which would set off the freeze-reboot. I found that my phone would not freeze-reboot but very often it would "reload" app icons and widgets when I went around my homescreens. Where I can only see my wallpaper for half a second and then the icons/widgets appear. It would do this very often throughout my 1day 5hour uptime, and a couple of times I would try to force the reboot (by pressing "settings" in the notification bar), after the icons/widgets did the invisible/load thing and it didn't reboot. This must have something to do with it?
hi,
experienced this on my nexus s back then what i did is from recovery>mount and storages>formatted system, boot, and everything else except sd card.then it was all gone.btw you will have to flash your rom and kernel again as this is a full wipe.hope i helped and do this on your own risk
daff
bump
did it cure your reboots?
daff
dark06 said:
did it cure your reboots?
daff
Click to expand...
Click to collapse
I haven't tried that yet. I'm trying a "RAM booster" app to see if that helps, but that doesn't sound too stable even if it does.
I'm going to do a full factory reset and installing nothing, or moving anything to the SD, and just let it run like that to see if it works.
Just writing an update for anyone googling themselves here with the same problem, I had it resolved.
I found out that if I didn't force the reboot (by turning on the phone and quickly pulling down the tray and pressing something there) it could last a long time with just the launcher resetting, but it would lead to complete freezes (anywhere I was on the phone) and would require a battery-pull.
My plan was to wait for jelly-bean before doing another factory reset, I got the JB update and it completely removed the problem. I still don't know why the problem suddenly started or what caused it, all I know is that the JB update fixed it, and the update is fantastic, my phone's never been better.
So I have a really strange thing going on with edge lighting which is driving me crazy.
Whenever I play Elder Scrolls Blades the edge lighting appears but only in the bottom of the screen. As far as I been able to tell this only happens in this app though I can't be 100% sure.
Now what is strange other than it happens only in the bottom of the screen is that it keeps happening every few seconds, there is no notifications received and it happens, if I disable edge lighting it still happens, no matter to what effect I set the lighting it always happens in stock blue.
I can't possibly figure out what is this and I tried everything, any ideas would be appreciated.
Same thing here, in at least 2 games...
Thought it was related to spen, but it seems not...
Tried to disable Game Launcher but still got these random bottom screen notification pulse... And stock blue aswell. Got no clue atm
Thanks for letting me know I'm not the only one experiencing this. I tried literally everything and nothing seems to fix it. What's also weird is that the lighting comes in irregular intervals, sometimes just going crazy and sometimes appearing much less.
I have just discovered this issue appears in all games so it's a bigger problem then I originally thought. If disabling the game launcher does nothing then it makes it even more strange and annoying.
Yeah, same here, happens on basically all the games.
Maybe related to game booster?
Let's try to compare our setup : are you using any notification enhancement app? (like aodNotify)
Are you using your spen while playing?
But yeah, this random glow line **** is driving me crazy too!
Currently I am using aodNotify though I tried uninstalling it and the problem persists, I also have goodlock installed and the edgeslighting+, same thing with and without it. I am not using the spen, but I have tried just taking it out while the game is running and leaving it out for 5 mins, no change. I have disabled and enabled the stock edge lighting as well and the problem is still there. Nothing seems to effect it. Its ridiculous
i tried on mobile legend adventure, no problem on it, perhaps a scaling issue?
Will try to tweak full screen mode.
Increasing dpi doesn't change the weird thing, neither switching from Samsung stock launcher to Nova...
Also I'm using gestures based navbar, but I also tried with or without tips display, standard navbar... Still occurring.
Did you go from a scratch Note 10+ or used SideSync to switch? (I was coming from a Note 8)
I don't think it has anything to do with scaling, I tried setting the game on full screen and automatic, both giving the same results.
I used Smartswitch from Note 9.
Later today the camera effect from aodnotify started appearing in the game aswell (landscape mode), along with the edge lighting.?
I uninstalled aodnotify afterwards, found out there is a aodnotify Manager plugin which stays after uninstalling the main app.
Uninstalled the plugin aswell, opened edgescreen from the system app and cleared cache.
It was showing the app was using RAM with high frequency.
I don't have the time to check now does this fix the problem but will let you know once I do.
The only other thing left to do if this doesn't work is to clear edge screen data.
Will try this aswell, and restore all the notifications and edge lightning settings...
What I wrote above didn't work so I disabled the option for edge screen to show on top of other apps, so far this seems to fix the problem.
Unfortunately I was wrong and nothing above fixes the problem. I also wiped the entire edge screen memory, no effect. This is the weirdest thing I ever encountered in my years of Samsung phones and it's extremely annoying that there is no fix.
Strange, I don't have any issue.
Did you try with and without locking the screen orientation to see if edge lightning follows settings as it should?
I personally only use auto orientation.
I also use auto rotation and it happens the same way in landscape and portrait, the most annoying thing is that it happens really much, like 2-3 times in 10 seconds, or sometimes doesn't happen for few minutes then starts going like crazy, and as I said before there is no notifications or anything.
Same here, auto rotate on, only occurring during games.
I don't even know if I can debug which process is running these random edge notifications, without dig into tons of log files...
And if not, I guess I'll try to factory reset and re-sync again..
Its incredible that a factory reset seems like only possible solution left but I hope maybe some future update will fix it since I hate doing factory reset. Please keep me posted if you discover anything new.
Hating doing it aswell but this is too damn annoying..
If no clue, I'll go for a restore without restoring system settings... Maybe some notifications behaviors have been messed up
I'll keep you in touch for sure
Tried to wipe cache partition, still no clues...
Did this also got triggered in portrait mode game?
So confusing...
Yes it happens in all games no matter of the screen orientation. I really have no more ideas aswell
Got some news, another post is talking about this : https://forum.xda-developers.com/galaxy-note-10+/help/strange-blue-bar-games-t3963939
Seems related to the new game booster feature "temp and cpu monitoring"
Will try to disable this for a specific game and see...
My wife's pixel 3xl recently started having this problem. It is completely unmodified stock, locked bootloader, reports it is on the latest update.
Wifi and bluetooth won't stay on. A reboot fixes it, but eventually they shut off again. Sometimes it lasts a few days after a reboot, sometimes less. Once they shut off, they can't be turned back on again. You can try and toggle them on with quick settings, but it doesn't actually work. Only a reboot fixes it.
I tried a factory reset a couple of weeks ago. That seemed like a cured it for about a week, but it's back.
It's a pretty aggravating problem. If I can't fix it soon, she's probably going to end up with a new phone. Anyone else seen this, or better yet, know a fix? I've done some searching in the forum and on the web in general, but I didn't find anything informative other than one webpage that talked about some pixels, especially the 4a, having problems like this after updating to android 11.
Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Edit: I have no idea why this would make a difference, but I switched unlocking method from swipe to none this morning and that eliminated that long wake-up delay. It's back to fast and responsive like it should be.
Now to see if wifi and bluetooth are going to behave better on android 10.
jason2678 said:
Well, I got fed up with android 11, and downloaded the last android 10 factory image.
After flashing that and factory resetting, I'm having different problems. Now the phone takes like 5 seconds for the screen to come on when waking with the power button.
I'm starting to think this thing is cursed, or has hardware problems. Anyone have any ideas?
Click to expand...
Click to collapse
You can try wakelock V3 and select 'CPU' and set as autostart on boot in the app settings to see if it wakes faster.
I can't believe that it worked for me. I was facing the same issue and I got frustrated. I was just serching and came across a reel showing fix regarding it. In that video person switched off his pixal tapped it on his leg (backside of phone) and then started it and keep tapping it on his leg while starting. It's really weird but I gave it a try. And can't believe it worked. Wife and Bluetooth both fixed now. Getting "on" now.