My Note 9 was recently upgraded to Pie and I'm having all sorts of weird issues like the screen flickering during calls and notifications sticking around after having been dismissed.
Is there any way I can reflash the update, or will a factory reset fix this?
EShow said:
My Note 9 was recently upgraded to Pie and I'm having all sorts of weird issues like the screen flickering during calls and notifications sticking around after having been dismissed.
Is there any way I can reflash the update, or will a factory reset fix this?
Click to expand...
Click to collapse
Factory reset should fix it. Just make sure you backup with smartswitch.
For anyone who might be experiencing the same issues and found this thread, I actually figured it out - in the developer options, setting the animation scales to 0 causes these issues. I bumped them each up to 0.5 and am no longer experiencing the two issues above.
Related
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
_Boondock_ said:
I'm getting a crashed UI when checking notifications by swiping the top left corner downward.
I'll get an email or hangout and when I go to check it via the notification area it just blacks out the screen, then has a slight panic attack and switches between the home screen and the lock screen once or twice but this takes 5-10 seconds and it is obvious there is some sort of crash. However there are no crash notifications from android. Then my notifications seem to work find for a little bit.
It is similar or possibly the exact same thing as what is described here http://forum.xda-developers.com/showthread.php?t=2743255
Does anyone know of a fix for the UI / Notification Bar crashes that are happening? I'm seriously considering getting a new tablet and using this as a good excuse.
Apparently clearing the davlik, cache, and doing a factory reset doesn't seem to help.
I'm running CM 11 M6 EMMC on my Nook HD+
Click to expand...
Click to collapse
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
deleted
I can confirm the same problem. It is reproducible. Which does not mean it happens every time but over the course of using the tablet for 5 hours it happend around 3 times. Very very annoying!
Something similar happend when I heavily used Firefox without using the notification bar. Maybe it is also an issue when all memory is taken?! Should hopefully be fairly easy to fix since it was introduced somewhere between M4 and M6.
sirbender42 said:
How did you install it? Can you describe the process or link to the tutorial you used?
Did you do the factory reset before or after the install?
Click to expand...
Click to collapse
I've installed it flashing in CWM
I've tried doing the factory reset before and after the install.
Same issue here.
I am running CM 11 internal and have the same issue...
According to this post, this bug is due to be fixed in the next nightly.
ejstubbs said:
According to this post, this bug is due to be fixed in the next nightly.
Click to expand...
Click to collapse
I posted this. The bug report I posted sounds like the notification bug we see. According to the changelog the bugfix should be in starting with the cm-11-20140513-NIGHTLY-ovation.zip
You can download here: http://download.cyanogenmod.org/?type=nightly&device=ovation
Please let people know if this fixed it.
Still an issues (running 0515-nightly)
I flashed the nightly from 20140515 and am still having the resetting issue... Anyone else?
Hi all,
Need advice as my Moto X seems like sometimes it does not register the first touch to unlock from Active Display, i need to touch it again to unlock it.
Is anyone else encountering this issue?
Thank you in advance.
crazynoob said:
Hi all,
Need advice as my Moto X seems like sometimes it does not register the first touch to unlock from Active Display, i need to touch it again to unlock it.
Is anyone else encountering this issue?
Thank you in advance.
Click to expand...
Click to collapse
I have seen this issue happen to some people using xposed with lots of modifications, or a custom kernel. If you are 100% stock, I would suggest clearing cache and possibly a factory reset to see if it resolves it.
Are you using xposed or any other modifications?
samwathegreat said:
I have seen this issue happen to some people using xposed with lots of modifications, or a custom kernel. If you are 100% stock, I would suggest clearing cache and possibly a factory reset to see if it resolves it.
Are you using xposed or any other modifications?
Click to expand...
Click to collapse
Hi,
Thanks for the fast reply.
Totally stock and unrooted. I did a factory reset once, do you mean clearing cache of the Active display app?
Not sure if it's just me, i can't replicate the issue, it just occurs randomly e.g. taking phone out from pocket or pouch, when trying to unlock first time the touch seems not register or the active display lock screen need some time to react?
I am also having this problem after updating to 4.4. I first noticed this when I finished a call and after removing the phone from my ear, the display does not come back on.
Has anyone else had problems with auto screen rotation,mine has twice now in 4 days started either getting stuck in landscape mode or would start rotating back and forth by itself,I fixed it for now by clearing cache,but curious if anyone else has had this issue.
I have the same problem on 910c variant, even factory reset does nothing, I hope it is not a faulty hardware
Ditto on my 910T3 TMo. Stock rooted. Auto screen rotate stopped working 2 days ago.
I have wiped cache and dalvik.
I have tested sensors with other apps (they work).
I have run self tests (dial *#0*#)
I disabled all Xposed modules
I tried 3rd party screen rotation app
None of these have resolved the problem.
Also tried wiping Dalvik and cache and reflashing the kernel.
That didn't fix the issue either.
the problem seems to happen when the phone is hot, because when I wake up In the morning I turn it on and doesn't have the problem
I have the same exact issue. I've replaced my phone 3 times because of it. BTW I'm on 910T.
Hopefully this new software update that just rolled out fixes this issue.
I also noticed when in the camera app, if i rotate the phone between portrait and landscape, the controls on the screen rotate appropriately.
So again, that verifies the sensors are working and it isn't a hardware issue for me.
Also tried using stock launcher, but no change.
Am about ready for a factory reset.
I've experienced this also but I thought/think it was a Nova launcher bug that seems to have corrected itself.
Since the recent update everything has been running fine. So far I haven't gotten the screen rotation issue!
It used to happen at least 2 times a day. I think it might just be a software based issue.
SM-N910T still on 5.0.1 stock having the same issues. It gets stuck in landscape, stays stuck in over landscape position.
I ended up doing a factory wipe and updating to the stock rooted DOK2 rom that just came out.
So far no issues and screen rotation is working (along with several other nuisance issues that went away).
Just as an update I lost screen rotation on DOK2 stock rooted ROM. However, I believe it may have been related to some debloat cleanup I was doing.
Under Ti Backup I searched for "facebook" and manually forced uninstall of the 4 "system" apps that came up.
I don't know what any of those would have to do with screen rotation, but one of them does.
I was not able to successfully restore those files via Ti Backup either, so ended up dirty flashing the same DOK2 zip file to restore them.
That fixed it. So rather than forcing uninstall of those files I just removed updates and disabled them via the android app manager.
So far so good.
This happened to me yesterday and that was completely by mistake. I had the marshmallow update for sometime now and not experienced any major issues other than the random heating (while charging) and some drains at times.
The major issue occurred to me yesterday, when my mutli-window function got disabled by some how and then the phone did not respond to any of my finger touches anywhere on the screen. I have a password lock screen and that too stopped working because the touch response system was not usable. After a struggle for many hours and one sleepless night, the next morning, when I was just thinking of sending the phone to the service center; it just came to my mind and I tried out the SPen and that was working just fine. :victory:
So, using SPen I unlocked my phone and tried to understand what changed. As I normally enable a few functions on my phone, it easily came to my notice that the multi-window function was disabled. So, again using the SPen I enabled it and Voila!! the finger touch started working back.
This is pretty crazy and never experienced this before the marshmallow update.
PS: Even the backlit hard buttons ( left one, home, back right ) had stopped working for me for that instance.
Anyone has any clue on it?
Did you do a reset after the upgrade?
donalgodon said:
Did you do a reset after the upgrade?
Click to expand...
Click to collapse
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
vaibhavgaikwad said:
Yes, as I said the upgrade was not the issue, the issue is disabling "multi-windows" made the phone unusable for sometime till I enabled it back and it started working fine. The issue is something with that "multi-window" on marshmallow update.
I don't intend to go back to older version now.
Click to expand...
Click to collapse
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
donalgodon said:
With all due respect, there's no way to know if the "upgrade was not the issue" unless you actually did a wipe/reset to rule out the crud remaining particularly between major version number leaps.
I tested what you described as the cause of your problem on my wiped/reset device and the problem is not happening for me. Enabling and disabling multi-window causes no issues in my case.
IT might be worth doing a wipe/reset if you haven't. (It's not clear from your response if you have or not done so).
Click to expand...
Click to collapse
I think I have been more clear and transparent, if you says the multi-window is not an issue then it may be something else which I am not aware of. Though I know that over that particular day nothing new was installed on my phone (so I doubt it can be other software).
Why I am sure its the marshmallow update is because the older version I had tried disabling the mutli-window and the phone worked well, only with the marshmallow update the phone got weird (that too with that multi-window disabled) and enabling the multi-window made it work, so that's my point.
To answer you question on "Did I do a reset", the answer is no I did not, I rebooted (and shut) it couple of times thinking its overloaded but it did not change my situation. Only after I realized that SPen was working fine I could unlock the phone and enable the mutli-window and there after it started responding well to my finger touches too. It's working good today as I write this response. I can once again disable mutli-windows and check if it goes weird again. Let me know if you want me to do that?
Regards.
I recognize that doing a reset can be a pain, but it's probably worth it in the long term. It's up to you, but if it were me, I'd do a reset and start fresh.
When you make major version leaps, the chances of problems increases dramatically over point releases. (i.e. going from 5.x to 6.x is bigger than going from 5.0 to 5.1)
This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
i installed gapps and it worked for me(but with twrp - unclocked bootloader)
Bsherb said:
This issue of incoming call screen not opening just started a few days ago. I get a ringtone and vibration, but whatever screen I happen to be on stays the same. As a workaround, I enabled a notification in the notification shade from which I can answer or decline. I've tried every possible fix I can think of, even doing a factory reset as a last resort, but the problem persists. Neither Motorola nor Google has a clue. Any help would be greatly appreciated!
I should note that I am running stock Android 7.0.
Click to expand...
Click to collapse
I haven't ran 7.x for about six months so I don't remember if this is an option but try going to Settings --> Apps --> Phone and see if Phone is set as the Phone app. Also,is there a reason why you haven't updated to 7.1.1? There were a lot of bug fixes and improvements from 7.0 to 7.1.1.
This topic is obsolete (for me anyway) since I have a new phone. But to answer your question about version number, official support for the Nexus 6 ended shortly after Nougat arrived. Thanks!
Google updated the N6 to 7.1.1 before ending support [emoji39]
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers