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...
Related
Need some advice. My program menu on my xda keeps whiting out.
On an initial start (or after editing the program list) the program list (or start menu) displays fine.
On the 2nd click some icons start doubling up at the bottom and fill the screen.
The on the 3rd click it goes off the bottom of the screen and goes completely white!
What gives? I've editing the number of items, looking in the registry at start menu opetions, deleting programs, but nothing solves it.
Performance etc not hampered but its really annoying. It MIGHT have started after installing a c++ cube program launcher (not sure).
if anyone has ideas to fix it please let me know.
TIA Sean
Hey I just had that exact same issue earlier. I was editing my \Windows\start Menu\Programs folder and making some adjustments when i noticed it happening. I kinda narrowed it down to being something to do with HButton. I was fiddling with the Hbutton display options just after modifying the programs folder. After more fiddling with the HButton display (changing colour and position) and a soft reset, my Start menu started working fine again and I havent had any problems with it again so far.
Probably nothing at all to do with it but thats what seems to have fixed mine as i didnt touch anything else but HButton and it is now resolved.
hope this helps in some way
[EDIT] completely ignore what I just put above, its just happeed again. The only thing I have done this time is Activesync and install a game. Kinda thinking it has something to do with Activesync now.......
lol oh well i guess i'll have to put up with it for now then. half a mind to send it back to O2 but its a software bug, I'll get the problem on the next phone as well.
Try to see in Memory the program values.
In my experience when tou have few program memory, start and today redrow is very difficult.
It happened me some times ago when i tryed a rom with problems of memory allocation.
You can try another rom (today you have many chose )
bigix1 said:
You can try another rom (today you have many chose )
Click to expand...
Click to collapse
Well considering my phone is one a month old I dont think I'll be flashing the rom JUST yet.
And update: for some reason the start menu is back to normal behavior! Absolutely no idea why. Just when i was getting used to it as well.
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
patrioticparadox said:
So the other day the app Widgetsoid releases a "Completely rewritten" update for their sweet app. I was obviously excited to play with this and set about recreating all of my toggles. One toggle I have is to toggle the camera flash on/off which is very handy to have a widget for on the homescreen. Another one I use toggles the screen always on/off which is handy when reading long articles. So I was using the screen always on toggle as a reading light (as the camera LED can be overly bright) when, after some time, my phone locked up. Following my natural instinct I pulled the battery and powered it back on. When it came back on I noticed that the screen always on toggle was still in the "on" position though I believe (honestly can't remember for sure) that the screen was timing out as if it were off. Anyways I put this out of my mind and decided to use the flashlight toggle as the screen hadn't been quite as bright as I wanted. However, upon toggling the flashlight to "on" The toggle froze in mid activation. I could see that I had clicked it but the animation never finished and the flashlight never turned on. I gave it several minutes to sort itself out and when it didn't I did another battery pull thinking that would clear it up. Well it didn't. Upon the phone restarting I was greeted by "Tango has stopped responding". Then when I tried the flashlight toggle again I got "Gallery has stopped responding" which flashed up and disappeared too quickly for me to click on it. I tried opening the camera to no avail. "Gallery has stopped responding". So one bug led to another to another to another as bugs so often do. No biggie, I was planning on doing a factory reset soon anyways so I backed up my data and went ahead with that. Unfortunately, when I finished the setup and went back to the camera app it gave me the same error. (please note that I did not restore anything after the reset.) So I did another just for sanity's sake but no change. I went into the bootloader and into recovery, cleared the cache and then did another factory reset. Nada. I downloaded a flashlight app to see if it could tell me anything new, which it sort of did. "Cannot connect to camera", it said when I turned it on. In my search on this forum for a similar issue I came across a post to a different issue talking about how when an app uses the camera it might not have let go when it was finished which causes problems for other apps. This makes enough sense except that I figured the reset would have resolved that issue. Unless, of course, the problem lies in the hardware which I am desperately hoping someone will tell me is foolish.
I'm not really sure what to try next in my troubleshooting short of unlocking the bootloader and flashing either the stock back over it or another ROM. I would prefer to try other possible solutions before this. Correct me if I'm wrong but shouldn't the factory reset restore the system and stock apps to their default state? Almost literally bit for bit? If that is the case then that means the issue isn't with the system or the camera app and must fall to the camera hardware itself? I feel it is worth noting that on about the third factory reset, during the initial setup (quite literally on the first screen) a popup popped saying "Talk has stopped responding". Why the Talk app would stop responding due to some issue with the camera seems out of place. Though as I said and we all know, bugs have a way of spreading to the places you least expect.
Anyways any help, suggestions or questions would be greatly appreciated. This really has me stumped.
I guess the question it boils down to (besides the three I've already asked) is how can I do a full wipe/reset that will actually reset everything? Or is it that the camera is really hung and if so any possible fixes for that? Anyone see any bright red flags waving violently in the storm?
Thanks in advance for any help you can provide
patrioticparadox
I am running 4.1.1 on a Verizon Galaxy Nexus build JRO03O
Click to expand...
Click to collapse
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware. Make sure you wipe data and dalvik a couple times and go to mounts and storage and wipe system too. Do those a couple times, I always do just to be sure it works. Then after that try to flash another ROM stock or custom doesnt matter. This will help a lot.
Just a recommendation, I use and LOVE Codename Android Rom. Very very fast and stable with a lot of features.
Anyways, post back when you wipe everything out and flash a new ROM on there and let me know the outcome.
nothing yet...
myboyblake said:
I would honestly try to flash another ROM. its hard to tell what is exactly causing this prob but I highly highly highly doubt its hardware.
Click to expand...
Click to collapse
Just finished flashing the 4.1.1 back and still the same issue (did all of the data wiping). I'll try a custom ROM now though I doubt its going to make any difference.
What in the world has got a hold of my camera?
No dice
"Unfortunately Talk has stopped responding" on the first screen. "Gallery has stopped responding" when trying to open Camera app.
So despite several wipes and two distinct ROM flashes (used PARANOIDANDROID the second time) my device is still acting up.
Please help me out people. What is causing this error that is lasting across ROM flashes? What can I try to resolve this issue?
Rewiped everything and reflashed PARANOIDANDROID (2.23) just to be sure and still the camera doesn't work
seems like perhaps the registers ended up in an odd state.. know this is for a different phone, but you might give it a shot..
http://www.droidforums.net/forum/dr...amera-app-stoped-working-wont-initialize.html
---------- Post added at 05:03 PM ---------- Previous post was at 04:46 PM ----------
Looks like OMAPFlash can do a full reset on all the camera registers from looking at:
./Targets/Definitions/definitions_omap4.txt
in the OMAPFlash zipfile..
It might be worth a shot..
Slide opultl
No dice... I assume you were referring to clearing the cache and data. I had tried this before but gave it another shot anyways. In case you meant the screenshot part, I did that too and the screenshot captures fine but still the camera does not function. Also holding down the volume down and power keys never shuts the phone off I assume that is device specific (though several seconds after the screenshot captured the screen did flash off then on very quickly). I have tried disabling Gallery and rebooting in the hopes that would free up the hardware. Failed.
I am uber stuck on this.
Why is this persisting across flashes and what can I try to resolve it?
edit: just noticed that the bottom of your post was more info and not a signature. I'll look into that. Ran out of "thanks" for today but I'll get you yours
Since it won't delete....
As an update: I have tried contacting both Verizon and Samsung about the issue. Both recommend returning the device under warranty (as was expected). This would be fine except that I LEARN NOTHING! If the Samsung techies have a protocol/enumeration/anything to discover and resolve the issue then so can I (potentially), which means the general public should have this knowledge too, right? WHAT IS MY NEXT STEP?
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Here's a link, sorry I didn't post soon - I don't check back here often..
patrioticparadox said:
(still have not yet OMAP_Flash'ed as I haven't found SOLID documentation on this yet.) (Google searching led me somewhere but left me confused. Please post documentation or the correct link if you have it and thank you) I am open to trying anything. Understand that my bottom line is giving Asurion $50 USD. "I LOST my phone, send me a [new] one". Phone gets replaced and I get to trash the old one. Sweet for everyone right? Wrong.
I don't give two runny, stinky butt creams about the phone itself. Which is not entirely, or honestly, even close to true. I'd hate to see a Nexus that can be saved be completely obliterated. If its totally bricked (which its very hard to do to a Nexus) then go for it. Smash that ***** up! But if, like mine, its recoverable then you owe it to the developer to try to save it. This Galaxy Nexus SCH-I515 reminds me of my SCH-a950. I loved that phone and literally (because of a now EX girlfriend) BEAT THE LIVING SNOT OUT OF IT. I literally threw it at my front porch as hard as I could from a good 30 yards away and yet it survived. Not only did it survive, it thrived. Never failing me (even until I finally upgraded) despite the "wear and F'ing tear" I had inflicted upon it.
I have actually dropped my Nexus several times. I have a massively cracked screen that I would love to show you all, yet the screen still functions as if there were no crack. I can click on the "options" toggle that is in the bottom right corner of many apps as if there were not a MASSIVE chunk of screen missing there. The phone is quite amazing. And before anyone says "oh you dropped it, that could have to do with the errors in the camera", NO. The camera worked just fine until what I described above. Samsung has done quite a magnificent job with this device (and all of their hardware, {I own a 26" computer monitor that kicks ass too}) making it resilient to adversity.
Now please, help me out....
I am hesitant to try the OMAP_flash as I haven't found decent documentation. PLEASE PLEASE post a link.
As I said I can always "lose" the phone and get a new one through insurance. So I'm not worried about screwing the phone, I just want to LEARN about the issue at hand.
What do YOU think is causing this issue?
If someone could post a link to the relevant info about the OMAP_flash then I will be happy to go forward with it.
Aside from all this I am shocked at the relative dismissal of this thread. I am seeking information from experienced members who have expertise on this device and while many are available I have gotten no replies as of yet. (this is not to discount those who have replied as I am very grateful for those suggestions as well) Please take two minutes and give me your thoughts. I don't believe this issue is similar to any other posts here and if you do believe it, kindly point me in that direction.
Click to expand...
Click to collapse
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
I don't think it going to do a reg reset for the camera by default..
This is from: Targets/Definitions/definitions_omap4.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET 0x4A1000C0
It is pulled in and used by:
Targets/Configurations/configuration_omap4460_tuna_8g.txt
CONTROL_CORE_PAD_CAM_GLOBALRESET needs to set for the correct location -- I have not done any digging, so I don't know what the location is..
Just Found this -- https://github.com/omapconf/omapconf/wiki
omapconf can be used to read/write/modify any register from within Android..
Mach3.2 said:
Jesus, will people stop talking about insurance fraud........
It's these kind of people that people in your country have to suffer higher insurance premiums, and the very same group of fraudsters are complaining about high insurance premiums..
Regarding OMAP flash:
1) Remove battery
2) Open device manager
3) Plug your phone to your PC/laptop
4) Right click on OMAP4460, go to properties
5) Drivers tab
6) Update drivers, direct to the OMAP flash folder
7) Run the .bat
8) Reflash a ROM just in case.
Click to expand...
Click to collapse
Insurance fraud? Um get a life! That's not why their premiums are high you ass! They do it to make more money you jack knob. My company charges $65/yr with a $25 deductible with up to 5 claims a year! That's so much better than asurion. And they give you a piece of **** replacement. Is all about money not the customer...now please me nice. Great ideas come from working together not from being an asshat!
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.
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...
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.