I have had some weird problems with my back and menu keys the last week or so. I have searched quite a bit but have not found anything that describes my problem. Lots of similar stuff, but nothing that really fits.
Now to the description of my problem:
After a seemingly random time after booting (~2min-2days) the phone's back and menu keys stop working. The gestures for back and menu with the S-Pen also stop working at the same time, and virtual back and menu keys stop working as well.
A reboot (or hot reboot) fixes the problem or not depending on the app used to hot reboot ("Rebooter (fast reboot)" from 'SmartUX' does not fix the problem, but "Reebooter" from 'davidjr621' does).
I have the felling that wiping the Dalvik Cache and the Cache partition has increased the time between the occurance of the problem, but since the time was very variable to begin with, I am not 100% sure about that.
Iam currently running OmegaROM v7.4, but I had the problem before upgading from v7.2.
Does someone have an idea how I can identify the source of the problem?
To me it looks like a weird software problem, like some process that is ment to handle the signals stopped working but is seemingly still runnig, since killing everything (Hot Reboot) solvesthe problem. But that is just speculation, since I don't know how exactly the back and menu key keypresses are handled in Android.
Any help would be apprciated. Places to look for clues or any ideas about what might be causing this.
The problem occurs more often when I switch from mobile data to WiFi or back, but not every time.
I will try to see if I find somethig in logcat givig any clues...
I'm sure you know that back and menu keys are temporarily disabled when you put your S-Pen near screen.
Sent from my GT-N7100
Yes, but the gestures with the pen should still work, they don't when I am having this problem.
It occurs with the pen docked as well.
I did a full wipe, including the "Internal SD-Card", and flashed OmegaROM v8.0. I am hoping that this weird problem is gone now.
By now I am sure the full wipe solved the prblem.
Just in case someone with the same problem stumbles upon this thread.
Related
I first started using CM at 6.1.2. I'm now on CM7 RC2 and the same problem still occurs. I have no idea why this happens but I'll provide as much info as possible in the hope that someone will be able to figure it out.
My phone will work completely normally for several days after I initially flash CM6.1.2 or CM7. After a few days, a crash will occur where the screen stays on but the phone is completely unresponsive to all input -- touch, softkeys, or hardware keys. The power button stops functioning. After a while, the screen dims and the phone reboots. After the reboot the phone chugs along for a few hours and then the same thing happens. This crash almost always occurs in the Browser, in the middle of loading a page. I don't think it's a memory issue because I consistently have ~100MB free for RAM.
Also, I don't know if this is at all related, but I often notice just before the crash, the haptic feedback from the phone for keyboard presses and the softkeys becomes very erratic and inconsistent.
I can never get a logcat because the phone restarts after the crash. Has anyone else seen this or know what might be the problem? Again, this has been happening all the way since CM6.1.2 (and possibly earlier, I haven't tried anything earlier than 6.1.2 though). This is driving me pretty crazy, and I really love CM and would like to continue using it, but this is kind of a dealbreaker.
Did you wipe between flashing CM6 and CM7?
Yes, I always wipe data/cache/dalvik between flashing.
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.
Having a bit of an issue with the auto rotation on my OP3 where the screen snaps back into portrait after being rotated either by me or by an app, then locks the device. (if the lockscreen is activated) most apps respond by crashing once this happens.
I've dug all through my settings and come up empty on finding something that could be responsible. So I'm thinking it must be an app, or Xposed module, but again dug through everyone's who could possibly have setting that could do it, again came up empty.
So I'm really frustrated by now and wondering if anyone else has seen behavior like this, or knows what could be the cause.
I'm on the Resurrection Remix OS and as mentioned Xposed is installed. I'd be happy to post a txt of all my apps if someone is interested.
Thanks in advance, Idk what else to do but wipe it.
So figured I'd at least ask you guys before I do, just in case.
(Edit)
Guess I can add no recents menu to the list of effected. Plus now that I have that "on button push" ability to trigger this, I see it's actually resetting the system UI. It seems to crash then reload immediately, triggering the screen back to portrait and the system bar up top to redisplay (usually hidden).
I see a factory reset in my near future...
Well that's got to be a first, seems all I had to do to fix it was threaten to wipe it and it fixed its self!?
Seriously I haven't done anything since I posted this at lunch today, except start a Titanium backup, (which is still running) and as soon as I get home ready to delete it, I opened it up to a landscape view that wasn't durping out. How bazaar... Not sure now if I can trust it to behave or maybe I should wipe it anyway to be sure...
Hi everyone, I hope someone here can help me.
I'm experiencing a bug on my phone that's bothering in several situations.
Apps in landscape mode switch to portrait and come back to landscape (or not):
http://imgur.com/gallery/vfgSCPn
Voice notes in WhatsApp get interrupted:
http://imgur.com/gallery/yXIlFbI
(you'll see that the navigation bar briefly goes white)
I've factory-wiped my phone, gradually reinstalled the apps and double-checked that there are no weird or potentially dangerous apps.
The tricky part here is that I can't find a pattern, as it randomly happens (for instance, my keyboard went down when writing this actual post).
Has anyone else experienced this problem with their phone? Any idea on what I can do? It's really hurting my experience with Samsung.
Thanks!
You might try another Android version.
Clear system cache on the boot menu.
You can try a hard reboot as well.
Test the sensor(s) that controls that (it could be an intermittent failure, the worst kind to diagnose).
Does manually locking it to landscape mode stop it?
If it's a brand new phone, get it replaced as this is not a normally seen glitch.
Reloads generally don't cure settings or hardware issues and useless it's an old load or has a worm, trojan, etc are generally a waste of time.
As invariably the original issue just gets triggered again... eventually.
Update: Found the culprit! When the phone is on a 2G network, it happens always when there is any (voice or data) communication and glitches are stronger when the signal is weaker. It's probably caused by an interference and bad shielding of components. Similarly how 2G network makes buzzing sound in radio speakers, on A52s it makes a mess on the screen.
At least one user (bellow) solved it by RMA - sending the phone to service and getting back new/fixed one.
Update 2: Problem fixed. I sent the phone to service center with description how to replicate the issue (phone must be on 2G network, ideally low signal, data or voice transfer is happening). Got it back after 2 weeks. Report says they replaced the display and also battery for "construction" reason (as they described it) and issue seems to be solved!
To conclude: It is indeed hardware issue and is fixed by replacing the display. If this happens to you too, don't wait for software update or anything else, send it to a service for a fix covered by the warranty!
Since few weeks ago, maybe since last update a month ago (security update from 1st October 2021), I'm randomly getting graphical glitches on my A52s.
It usually happens when I wake my phone after few hours of screen off but today I also saw few flashes even when playing a (graphically not demanding) game.
There is colour noise flashing over parts of the screen. It is usually just few random quick couple of 1/100 sec flashes, sometimes it stays a second and it disappears and everything is okay after that.
I also saw noise not covering the screen but flashing instead of wallpaper... Like there's a corruption in graphical memory, driver or whatever.
It doesn't make a difference whether the phone is freshly rebooted or running a week or two.
Does anybody else have this issue?
Is my phone (the memory, screen cable or something else) dying or is ist just a bug in current system update? I don't experience any other instabilities or problems.
(I'd send my phone to RMA but since I didn't find any consistent way to replicate this, it would make just as much of a difference as locking my phone in a drawer for a month.)
I'm appending mock-up screen shots how some of the flashing glitches look.
Clear system cache, hard reboot.
Huh, I didn't really ask for help, but yeah, that's a good idea with clearing the cache.
I rebooted to recovery and wiped the cache partition.
(I also accidentally hard rebooted when trying different button combos to enter the recovery LOL, so I did both things. In the end I had to enter the recovery using "adb reboot recovery" command because none of the button combos I found worked for me.)
I'll report back in few days whether it solved the issue or not.
Your screen is dying. This is hardware issue
Easy fixes are a good thing...
EugenStanis said:
Your screen is dying. This is hardware issue
Click to expand...
Click to collapse
A possibility as is a mobo failure but no harm in trying a few simple fixes first.
Samsung has been having a lot of issues with their displays this year...
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would suggest to me either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
jenda.69 said:
It doesn't really feel like screen itself is dying when glitches can appear under the home screen icons in wallpaper or in the application area with status and nav bars being untouched. But I guess it can be; I have no idea how the image on screen is being redrawn.
But it happens especially after phone display is off for longer period of time. The phone then is quite sluggish, presumably because the system paused or killed some apps and is waking them up. And glitches mainly appear then.
That would to me suggest either a system memory being corrupted or something weird happening in the cache, depending on where these apps go when they're paused/killed.
Click to expand...
Click to collapse
Factory reset. Before loading apps confirm if ok.
Then be careful what 3rd party apps you load.
If the reset doesn't work, reflash it to a known good version.
If all that fails it's likely hardware.
The most likely cause is a 3rd party app given right to overlap other apps and this 3rd party app has crashed. Uninstall apps in opposite order of installing until problem is solved. Or factory reset.
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Bvid said:
I have the same problem, sent phone for repair.
In my case, the issue is occurring when phone is on 2g network. You could try going to network and set it to 2g only, check if it's happening, and then set it to 3g and see.
Cheers!
Click to expand...
Click to collapse
So is it a hardware issue or software?
abood.mhd said:
So is it a hardware issue or software?
Click to expand...
Click to collapse
It was a hardware issue, got a new phone.
Bvid said:
It was a hardware issue, got a new phone.
Click to expand...
Click to collapse
I have the same problem, and I can't replace the phone, the question is here, will this problem increase and affect the screen more?
Same problem here...but mostly when I am on 2G network (anyone please try and post results)...Thinking of sending phone to service...will see how it goes
Huh, I didn't get notifications for my thread, so I didn't know about all the replies!
I tested different things in last few weeks and I came to the same conclusion - that it only and always happens when my phone is on 2G network. If 2G signal is strong, it's occasional small glitchy line here and there. When the signal is really bad, it just messes up the whole screen - I had my phone ringing with screen being all just noise and mess. So I guess it's probably because of interference similarly how the 2G network connection makes buzzing sound in a radio speakers. Except here it makes a mess on the screen.
Now that I know how to reliably replicate the problem, I'll back the phone up and RMA it after christmas.
i have the same problem from the first day, it happens only in 2g signal ...and only if 2g signal is weak... i sent the phone to Samsung , they inform me that they know the problem and it will be fix ..on another update ...it s software problem they told....from this day i have take 3 updates and nothing happened....the phone still have the problem
Same here, took my a52s to a Samsung authorized repair center, after 3 repairs (the third one being the display change) it seems that the problem is solved. To me, it has nothing to do with software.
So, it's a hardware issue, I face the same problem for almost 2 months, and I don't know what to do
Only solution is to contact Samsung and have it fixed
VirtualGamer20 said:
Only solution is to contact Samsung and have it fixed
Click to expand...
Click to collapse
Its not that simple...Some people send phone for repair...twice and still not fixed