I have a Mediapad M3 Lite (10), and today I performed the recommended upgrade to Emui 5.1.2 (as recommended by the tablet). Now I have a tablet with number: BAH-W09C100B256
However, sensitivity is crazy now. Swiping seems to 'click' constantly. I becomes completely unusable. Anyone else having these issues? (It was performing very well under 5.1 (.1? I don't know what the previous version was)
What should I do next? Can I return to Emui 5.1?
I did the same update, but I don't have your issue, nevertheless it's the second time the tablet reboots by itself (never done before). Probably we should proceed with a factory reset and to see if the problems persist. Otherwise we should find a tutorial to do the downgrade.
Hi. I also installed the update to BAH-W09C100B256 Emui 5.1.2. I think I might get the sensitivity problem occasionally, but often. However, since the update my tablet takes about 4 minutes to boot up, and then the UI is completely unresponsive for another minute or so. Eventually I get a pop-up saying "Huawei Home has stopped responding. Close app or wait?" I close the app, the background goes black, but the UI starts to work again. Anyone else get this?
Is there a way to go back to previous update level?
Are there alternative ROMs for this device? Lineage or something?
Related
Is anybody else experiencing screen issues after the nougat update?
i find, periodically , particularly after disconnecting the device from hdmi and closing the lid that upon reopening the device its wholly unresponsive and requires a long hold of the power button to reboot the device?
there doesnt appear to be a constant but it never happened in the year odd of ownership prior to nougat? Any ideas?
Yep, same issue. Android System is consuming around 50% of the battery, when it was around 10% before the update. The upper back of the bottom also gets much hotter than before. Already created a support ticket with Lenovo but haven't heard back from them in almost two weeks.
Me too. Same issue.
Any answer in your case from the supportticket?
ChristophAhlgrimm said:
Me too. Same issue.
Any answer in your case from the supportticket?
Click to expand...
Click to collapse
Nope, they completely ignored me... such a Lenovo thing to do. Definitely my last Lenovo device.
Herohardcastle said:
Is anybody else experiencing screen issues after the nougat update?
i find, periodically , particularly after disconnecting the device from hdmi and closing the lid that upon reopening the device its wholly unresponsive and requires a long hold of the power button to reboot the device?
there doesnt appear to be a constant but it never happened in the year odd of ownership prior to nougat? Any ideas?
Click to expand...
Click to collapse
I was having this issue too. Seems to have been resolved with a manual cache wipe through recovery. Hasn't happened in the last 24 hours even with long periods in sleep mode.
Same Problem but in Android 6
Herohardcastle said:
Is anybody else experiencing screen issues after the nougat update?
i find, periodically , particularly after disconnecting the device from hdmi and closing the lid that upon reopening the device its wholly unresponsive and requires a long hold of the power button to reboot the device?
there doesnt appear to be a constant but it never happened in the year odd of ownership prior to nougat? Any ideas?
Click to expand...
Click to collapse
---------------------------------------------------------------------------------------------------------------------------------------------------------------
I have exactly similar problem but in Android 6 Marshmallow. I have system updated many many times. Today there was nougat update available but I have seen may users complaining about different issues regarding Nougat version. So I have not updated yet. Since I have the same hibernation (screen off/ shutdown) problem even before the update. I am thinking of updating to Nougat.
I tried many methods but did not succeed. If you have found out any solutions please share with me. So will I.
Thank you
Were you able to solve this problem? I've been living with this for the last year. When the device goes to sleep it can't wake up and I have to press the power button for 20 sec to reboot it. Very annoying since it gets hot and uses the whole battery while stuck in this mode.
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
chereko said:
I've been having a weird issue with this phone almost from the very beginning, in that the restart and shut down options in Android almost never work properly. I have seen the following take place:
When I select restart, the phone reboots into fastboot mode. Selecting the "start" option continuously reboots the phone into fastboot. I then have to hold the power button down for ~10 seconds to get it to boot normally.
When I select restart, the phone shuts down but appears to do so incorrectly, as I also have to hold the power button down for ~10 seconds to get it to start up again.
When I select shut down, the phone restarts.
This behavior happened on Nougat, so I tried sideloading the Oreo beta 3 to see if that would help. It didn't. I also did a factory reset after installing the Oreo beta, which didn't help either. I've done nothing to my phone (rooting, unlocking bootloader, etc.) besides sideloading the Oreo beta 3.
Essential support has offered to do a warranty replacement of the phone, but my problem is that I live outside the US and cannot easily send the phone back. Ideally I'd like to figure out the problem as I assume it's a software one, but am not sure what else to do. Essential support thought that the volume buttons could be defective, but in Android they function perfectly (i.e. if there was a problem with phantom presses on them I'd expect the volume to get randomly changed in Android).
The only other option I can see is flashing a full factory image, but since I just did a factory reset after installing Oreo I'd really rather not do this unless there's a high chance of it fixing the problem.
Any suggestions?
Click to expand...
Click to collapse
That's interesting. My Essential did the restart but shut down thing for the first time today. I'm not rooted and only running the current Oreo 8.0 beta. The only thing I noticed is an update yesterday from the google play store of Essential Services. I wonder if for me they are related.
It's possible but in all likelihood the problem was there before and it just never happened until now. Even on my phone, sometimes it does reboot properly and sometimes it doesn't. I haven't figured out any rhyme or reason as to why it happens. I bet this is a problem that many people haven't noticed because few of us regularly reboot or shut down our phones. For me this has been happening since Nougat, and the Oreo beta didn't change it in any way.
Help! my 15 month old Umi Super shut itself off (battery almost full) and now won't reboot. The Umi logo appears as normal, then goes to the pulsing android thing. and stays like that for a few minutes until the screen goes blank. I have to hold the power button for a couple of minutes to start the sequence again.
I haven't rooted it (wouldn't know how, or feel confident doing so) Only thing I've done recently was update the OS to Nougat, using the update feature on the phone, so it's completely unmolested apart from the update. Since then, I've lost the fast charge facility, and it auto-locks the screen, and won't display the clock overnight, like it used to do. And all the settings menus have radically changed (for the worse). Can't even turn off the Auto-lock feature, just set the delay.
Is the update to blame? Can I undo it and revert to Marshmallow? Can someone please help? All my contacts are in the phone memory...
Sorted!
Don't know what happened but it eventually rebooted itself. I then deleted all the recently installed apps, and it's now working again. Must have been a rogue app, but I don't know which one. Slowly and methodically worked through the setup menu and found, in the Security submenu, some settings I hadn't previously found and was able to set a safe location at home where it doesn't Autolock. I have my phone back! And I take it all back. Nougat is a big improvement on Marshmallow, once you know how it works. Happy Days!
Hi!
I have a Samsung S8 G950W snapdragon running Android 8.0.0 latest build BRF5.
The problem is whenever I do some intense task like as playing PUBG or some power-hungry game the phone gets warm and then it crashes. Crashes means it just goes black (Straight turn off no Samsung Logo that we usually get when turning off phone manuallly).
So, when I turn it off right after I keeps crashing. The only solution is to wait for 5-10 minutes then start phone, let it stay locked for 2-3 minutes then unlock and use with low brightness along data or WiFi off. Then after use of 10-15 minutes I can use it normally with data or wifi on.
I'm getting this issue after Oreo update, never had anything like that before on Nougat.
My question is
Is anyone having or facing the same issue or is that me? Was someone able to solve this problem and find real reason behind this? Can it be an hardware issue or software glitch?
What I tried:
I have already tried several things before asking here,
1: I uninstalled many apps which I thought could be real reason for that.
2: I soft reset phone
3: I tried factory reset too (removing everything from internal storage)
4: Also tried formatting sdcard
I am running this phone without any modification. It is stock android.
If anyone has any solution kindly tell me!
Hi, I have owned a One Plus 6T for a few years now, didn't have many issues, until the last few months. I used to be on Android 10. (something) can't remember and the issues I'm about to describe happened on that version too. I have recently updated to Android 11.1.1.1 and the problems still persisted. And I've run a factory reset a few days ago and that still hasn't solved the issues. My bootloader is unlocked and I am not rooted.
Issues:
1. Phone randomly rebooting (almost like there isn't any RAM but there's over a gig spare) eg Ill be listening to spotify and suddenly phone reboots
2. Extreme System UI delay/lag and screen lag. This is the weird one. Happens at completely random times. Phone will slow down extremely to the point where nothing will be responding. For example if I click the power button to look at the lock screen the screen will just stay black for ages. Apps will not open etc. Can barely even swipe or do anything, it happens multiple times a day too.
I was wondering if anybody knew why this might be occurring, considering I am running a fresh install, unless it comes down to just bad software.