How to downgrade from EMUI 9 to EMUI 8? - Honor 8 Pro Questions & Answers

Has anyone done this?

I really want to revert back to oreo! This update sucks. Everything looks enlarged, phone is freezing sometimes, touches don't get registered. And maybe I'm being paranoid but the battery is charging slowly as well! Someone find a way please! :crying:

whiskeyjakc said:
I really want to revert back to oreo! This update sucks. Everything looks enlarged, phone is freezing sometimes, touches don't get registered. And maybe I'm being paranoid but the battery is charging slowly as well! Someone find a way please! :crying:
Click to expand...
Click to collapse
Issues I am facing: 1) inconsistent touch response.
2) overheating while charging (but charges in around like 1hour 20mins)
3) Full screen Navigation Gestures are not fluid and accurate.
4) occasional freezing while gaming.

Facing same issues

Related

Crazy Touch Screen Not Responding Bugs with my G3

So most of us know about the System UI crash when using Chromecast, but this is even stranger. [Edit: an OTA update fixed this.] Some times, when I wake my phone up at the lockscreen or at times in the middle of a call - the touch screen stops responding. I can press and/or hold the volume buttons and there is a response on screen but I can not interact with the phone at that point. I can't continue to do battery pulls everytime. This is crazy. I'm on stock software. No crazy mods or anything. I've done a reset in the past and flashed the stock package again but this still happens every few hours. Only happens when the screen just wakes up...
Edit: This is a confirmed fix for me.
If you face the same issue, try:
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
I would say there is a misbehaving app causing the phone to lag in wake (that is all the unresponsiveness will be, extreme lag).
Sent from my Nexus 5 using Tapatalk
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
deedscreen said:
@Lennyuk - tried for over 30minutes after leaving it alone, I doubt it's a delay... Battery pulls work, but that's not the point.
Click to expand...
Click to collapse
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Epix4G said:
That was not his point.....to Find the app that is causing it go one by one uninstalling until you find it.... Something probably to do with app and the screen
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Totally agree with @Epix4G on this one. I am assuming you had a korean variant? The SK Telecom stock image is pretty ugly. Took me 3 debloat attempts before I had it behaving the way I wanted it to, but before I debloated, I had some lag issues (SK Telecom... grrrhhh).
Historically, Korean carriers (much like AT&T and Verizon) love putting useless junk on the phones for "productivity" but really they are there to charge Korean users more for other services, etc.
If you haven't done so, I would root and debloat, and see how big of a difference it makes (absolutely amazing performance after debloating on my F400S).
^^^^ - Will take that into consideration.
This may be a possible fix for now, can't yet confirm
open dialer
press 3845#* INSERT THREE DIGETS OF YOUR MODEL NUMBER THE PRESS #, for example, I am the F400K, so 3845#*400#
Hardware Device Test > Touch
update touch firmware
touch firmware version
wait 10 sec
reboot
It may or may not help
EDIT: It's been a few weeks and I haven't had this issue again. Usually every 4-6 hours it used to happen after powering on the screen, but so far so good.
Tried that with 855 version, it's not working. This is REALLY depressing as i just got a new phone and from day one i'm having this problem. I just can't believe LG screwed up like this, and there's no mention of this anywhere online other than this XDA thread. I hope i don't have to root and install custom rom as this really defeats the purpose of the phone.
@deedscreen
I'm having exactly the same problem on an 850 and tried your firmware method. The version number of the firmware did not change after reboot.
ic_fw_version info
SYnaptics 5.5
PanelType 1
version: v1.22
IC_product_id[PLG313]
Touch IC : s3528(family_id = 1, fw_rev = 1)
What version is your firmware? Also, did you find out about the fix from somewhere?
I have the F400K, but just got a US T-Mobile edition, (I'll eventually switch my signature). I would honestly suggest waiting for an OTA update. Call LG so they can document this. If that touchscreen update method doesn't work, I'm not sure what to do. I found the method somewhere online, I don't recall where exactly. If someone can figure out how to side load the touch screen firmware from a working Korean model to others, that would be great. For now, keep calling LG. It won't do much at first, but at least they'll have reports of this issue.
I have (RAW) touch screen firmware version: 30 05 51 96
Same problem, but not only on lock screen
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem, that the device is always unlocking itself, when in my front pocket. It's because of the Knock on feature. I deactivated this now.
But since yesterday i have the same issue: three times, i was unable to unlock my phone. The touchscreen simply did not respond. I had to remove battery. Today, I read this post and tried the firmware update of the touch, but I have the impression it did not change something in the version.
After this, today I had again once time the non responding touch while unlocking and shortly after, I had the issue after ending a phone call! The touch did no longer respond and had to remove the battery again!
I hope this is not a hardware issue, otherwise I will hurry up to the seller to exchange the phone, because its only 5 days old.
This is happening when the screen is on right? Or is the screen turning off and then not turning I again?
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Daum Ex said:
You need to keep Knock feature on, someone already said this. That's why your screen is freezing.
Click to expand...
Click to collapse
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
icon71 said:
Upps, yes, I just read this message now. To late: I was in the shop now and got mine exchanged. Anyway, that issue with the knock on feature should be solved also by LG: it's not acceptable, that the phone is always unlocking in my pocket.But then I wait with deactivating knock on for the moment.
So bad: such a good phone and such an annoying bug
Click to expand...
Click to collapse
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Daum Ex said:
I sold mine after a few days, i was sick with it. I disabled the knock feature through the hidden menu only to have the screen freeze every day. What, i can't use the phone the way i like? I have to face the screen outwards in my pocket and risk damaging it? Screw that...
That, plus the overheating and horrible build quality (back got scratched in my pocket) was a deal breaker for me...
Click to expand...
Click to collapse
Yes, indeed i also think about it. I got an official statement from support, regarding that the phone is unlocking all the time by itself in my pocket. They told me stuff like:
- this is a normal behaviour and can happen (!!)
- don't put your phone in the front pocket
- use the quick circle case to prevent...
- disable knock on (which is at least not possible over a standard setting, but only via the hidden menu).
I wrote back:
- that for me, this is not a normal behaviour
- that 90% of male users are wearing the phone in the front pocket
- that I don't like to buy a case only to prevent a bug of a premium telephone and
- finally, that they please could tell me, where and how to disable knock on
I am curious about their answer...
Good luck with that, disabling it through the settings doesn't change anything and they probably won't have a fix for months. They'll probably fix it though Android L update which will sadly come 6 months from official release at least.
Next time i purchase an Android phone i'm going with Nexus line...
icon71 said:
Since 5 days I have my G3 (855 Modell). I was happy the first two days, then I discovered the problem...
Click to expand...
Click to collapse
So what happened? How is it doing now?
Hey everyone, I just wanted to report my results of this touchscreen bug.
Well, I've only had my D851 for a week now. Of course I rooted it the same day I received it.
I had no touch issues until after restoring apps with Titanium Backup. I'd restore all user apps, then very few system app via XML. Since I just upgraded from a Galaxy S3 T999 I limited the system apps greatly. So much in fact that I only restored 1 system app......Media Storage 4.4.4 (Playlist). THAT WAS MY SCREEN KILLER!
The media scan on my D851 would render my screen unresponsive. I could only hold the power button and click power off or restart or whatever else was on that power menu. Then the phone would reboot after minutes of of a dead screen.
I flashed back to stock and reproduced the same issue. So now I've been running this device for 3 days without any screen lockups. I just have to rebuild my playlist again LOL.
I hope this helps someone here.
Knock
If you turn off the ability to wake by knocking the screen, it causes this issue where the screen locks. Turn it back on and the problem seems to go away.
I think LG really has to deal with this issue.
Hi guys, I have red a lot about this issue but I'm still confused with my LG G3 855.
First I realize problem with unlocking the phone using double click. Tried to upgrade touch software firmware using hidden menu and the screen became almost totally unresponsive. Tried to re-flash original 5.0 and 4.4.2, factory reset, battery removed, etc. but no luck.
I'm wonder if this is a software problem or became hardware. Should I consider replacing display or problem is in motherboard?
I really don't know what to do! Appreciate any comments or suggestions!!!
Thanks in advance!

LeEco Le Pro 3-- red screen occur when pressing the power button to turn off.

Hello everyone, I got LeEco Le Pro 3 two weeks ago. For the past two weeks of testing, I notice that the screen quickly turns red when pressing the power button to turn the screen off. Is any of you facing this problem? It happens randomly, not every time. I have attached the video in slow motion capture in the 7z zip file. So you can see, what I am talking about. Let me know if any of you see it.
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
marik1 said:
In mine sometimes it blink red. Power sleeping your phone rapidly. May red screen is reaction for force kill app?
Click to expand...
Click to collapse
I did not power sleep my phone rapidly. The red screen still persist. I don't know if force kill app cause it. I submit the feedback through the leeco experience center about this issue. This is what I got from them:
"Le Engineer
Hello,
I just get some information for this issue, in low battery level the red screen issue will happen sometimes. We also find the same thing on other brand device.
However R&D team are working on it. Hope it will be fixed in next generation product.
Sorry for inconvenience. Thank you for choosing the LeEco."
So I don't know if my phone is defective or not. It's hard to tell. Base on this message, look like there is no fix for this.
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
crazy1990 said:
Mine occur sometime, too. Here is what I analyze:
1. On the home screen; when pressing power button to turn off, red screen occur sometime.
2. Any app that has white background like the waze app I use in the video, red screen occur every time I turn off the screen while leaving the app running. That goes for other app like chrome, whatsapp, google map, gmail, etc. Same result.
3. On the back button, when I press hold, the screen turns off. No red issue. This was on the home screen and this rarely happen. But for apps that is open, same issue.
That is what I like to know if it is hardware defect or software EUI problem. It looks like software issues. It would be great if someone would test it with different roms such as CM13 or MIUI.
Click to expand...
Click to collapse
It could be a software issue since I don't have that on CM.
marik1 said:
I saw this movie. My phone behave as same as your <sometimes>. May it's EUI problem? Somebody on other ROM like MIUI or CM13 can say something?
Click to expand...
Click to collapse
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
losteagle said:
I never seen with MIUI 8, can anyone give me a sequence to try ?
Tried some times, shut down it's too rapid to see with MIUI.
Click to expand...
Click to collapse
If you have another phone with slow motion support just like I did, you can try that.
Other thing I want to mention, I would like to know that if the red screen does not happen to people who have CM or MIUI on lepro 3, can any of you go back to EUI and try to do the same steps? If you can. This would more confirm that the software is the issue and not the hardware defect.
Any update?
Hi folks! I've been searching for this rare issue since I got my LM2 last week. I have the very same issue and I notice the same @crazy1990 mentioned here. Besides, I notice this red light is more noticeable when the brightness is higher.
IMO, I don't feel it's a matter of bad hardware (I hope so), as there are no clues of any other issues at all. I'm also using stock (23s) and I suspect it's some poorly designed fade for the ROM.
Any updates from anyone?
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
crazy1990 said:
Yes. Red screen blink is noticeable when the brightness is high. As of June, I still have this issue since November on this stock rom 21s. So far, there was no screen degradation or any kind of lcd problem. Lcd works perfect since day one. A while back, I installed lineageOS and I still experience red screen when the rom froze and reboot. At this point, I still don't know if it is the software or hardware. I hope someone can help us out.
Click to expand...
Click to collapse
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
razmth said:
At least your report is positive. :fingers-crossed:
Did you try other custom ROMs? RR, Cuoco?
Click to expand...
Click to collapse
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
crazy1990 said:
No, but I already tried omnirom and purity rom. No red screen issue. I also tried tars 21s and turbo base rom, the issue is there.
Click to expand...
Click to collapse
Great to know it doesn't happen on Omni/Purity. My biggest concern was an increasing degradation and/or flickering issues arising when changing to a stock ROM.
Thanks for your information.
Sent from my Le X820 using Tapatalk

Touchscreen issue

IS ANYONE ELSE FACING TOUCHSCREEN ISSUE?
I'm facing some touchscreen issues like notification bar is hard to pull (meaning the edges of the screen is sometimes unresponsive)
Sometimes unresponsive screen while gaming
And the issue is most noticeable when I'm typing (Sometimes keys become unresponsive while sometimes are pressed multiple times even with a simple tap)
I'm not sure if it's a hardware issue or software issue, I'm a bit worried, If it's a software issue then it's fine but an hardware issue will cause me a lot of trouble.
Note :
I'm not using any screen filter app or haven't given any other app to draw over screen permission.
Using Resurrection Remix ROM
P12AV33N said:
IS ANYONE ELSE FACING TOUCHSCREEN ISSUE?
I'm facing some touchscreen issues like notification bar is hard to pull (meaning the edges of the screen is sometimes unresponsive)
Sometimes unresponsive screen while gaming
And the issue is most noticeable when I'm typing (Sometimes keys become unresponsive while sometimes are pressed multiple times even with a simple tap)
I'm not sure if it's a hardware issue or software issue, I'm a bit worried, If it's a software issue then it's fine but an hardware issue will cause me a lot of trouble.
Note : I'm not using any screen filter app or haven't given any other app to draw over screen permission.
Click to expand...
Click to collapse
Did you apply any thick tempered glass or screen protector? Some times a thick tempered glass reduces the touch screen accuracy
SGnoob said:
Did you apply any thick tempered glass or screen protector? Some times a thick tempered glass reduces the touch screen accuracy
Click to expand...
Click to collapse
No, I have a very thin screen protector.
If you are still on Miui 9, update Miui 10 to get better touch experience
Zanr Zij said:
If you are still on Miui 9, update Miui 10 to get better touch experience
Click to expand...
Click to collapse
Is there an official way without unlocking the device? I'd like to go to 10 but haven't unlocked yet and can't until the end of the week...
domsch1988 said:
Is there an official way without unlocking the device? I'd like to go to 10 but haven't unlocked yet and can't until the end of the week...
Click to expand...
Click to collapse
Download Miui 10 beta/dev zip file and using Updater to flash
P12AV33N said:
IS ANYONE ELSE FACING TOUCHSCREEN ISSUE?
I'm facing some touchscreen issues like notification bar is hard to pull (meaning the edges of the screen is sometimes unresponsive)
Sometimes unresponsive screen while gaming
And the issue is most noticeable when I'm typing (Sometimes keys become unresponsive while sometimes are pressed multiple times even with a simple tap)
I'm not sure if it's a hardware issue or software issue, I'm a bit worried, If it's a software issue then it's fine but an hardware issue will cause me a lot of trouble.
Note : I'm not using any screen filter app or haven't given any other app to draw over screen permission.
Click to expand...
Click to collapse
I'm having the exact issue as you described, especially when the battery falls below 50% its even more unresponsive, i tried to use multitouch app then it fails to do more than 5 fingers when flat down horizontally, i asked other whyred users in Telegram whyred Official but they can't explain or others just said its a software issue, so no one really helped me.
I tried to flash all latest firmware of MIUI 9 or 10(except those with ARB 4) and i still having the touchscreen issue, the phone is running perfectly fine in terms of battery & performance its just the touchscreen where i'm having problem, also note that i haven't experienced this on my previous Xiaomi phones that's why i can really tell the difference.
I really love this phone as much as i hate the issue, i hope someone can confirm this issue if its hardware or software related, i would be very thankful.
Zanr Zij said:
If you are still on Miui 9, update Miui 10 to get better touch experience
Click to expand...
Click to collapse
I'm using Resurrection Remix ROM.
Did you also experience these issues?
Zanr Zij said:
Download Miui 10 beta/dev zip file and using Updater to flash
Click to expand...
Click to collapse
So, I just download the global beta zip (from the XDA article for example) and apply it through the update settings as a local update? Seems easy.
P12AV33N said:
I'm using Resurrection Remix ROM.
Did you also experience these issues?
Click to expand...
Click to collapse
I have not yet tried RR
---------- Post added at 06:52 PM ---------- Previous post was at 06:52 PM ----------
domsch1988 said:
So, I just download the global beta zip (from the XDA article for example) and apply it through the update settings as a local update? Seems easy.
Click to expand...
Click to collapse
Yep
I had the same issue in the past in MIUI version 9.5.13.0. I upgraded to version 9.6.2.0 without ARB one week ago, and the issue isn't recur.
P12AV33N said:
I'm using Resurrection Remix ROM.
Did you also experience these issues?
Click to expand...
Click to collapse
i have been using aex ,lineage , aosip amd sevral othe custom rom and now RR , yeah all are same problem sometimes. when the cpu load up high , touch issue will appears, but not always.
At least now I'm sure that the issue is software based. Now I can die in peace
I have same issue
After updating to aosp 9.0 pie or pixel experience pie ROM
Yes, I am facing this issue too but I am on stock MIUI ROM (9.5.13). This issue is especially obvious when gaming as the screen suddenly becomes unresponsive randomly and I have to lock and unlock the phone again. It appears to be quite a common issue reported by many users but there seems to be no fix? It's hard to use the gestures as well as I have difficulty swiping up to go home or recent apps sometimes. It's incredibly frustrating
Same issue here.
I have also the same issue. Using aosp 9.0 pie. difficult to pulldown notification when I am in any app. if I press home then it working nice and no idea what is the reason
So, there is still no answer to repair this issue?
i have the same issue on pixel experience rom. When the phone become hot the screen unresponsive.
same issue with my redmi note 5 and miui version 10.0.4.0 its very weird touch problem
Deleted

SAMSUNG NOTE 10 PLUS SCREEN (NOT DIMMING/TIMEOUT)

Hello!
I have an issue here with my Samsung Galaxy Note 10 Plus
-screen not dimming / no time out when cable is not connected to charger
however , the phone acts normally (screen dimming out after x seconds as in the settings)
Phone is working however screen is not timing out when not connected to charger.
Hope someone could help.
do you recall when the issue started? did you remove bloatware packages. what apps do you have running. did you try in safe mode
More than likely either a hidden setting you've toggled or a 3rd party app. I recall a setting somewhere in dev setting I believe on this. If not try safe mode for a while and see if it happens then
after upgrade. would love to just do workarounds like macro etc , just dont know where to start.
Thanks for the response raul
I resolved the problem by installing custom firmware, not sure if it is just a bug on stock latest rom. Anyways this is resolved and i'm happy with the cr7 for note 10 plus. It resolved my problem plus it made my note 10 a tad faster and smoother
Xiao
Remember to clear the system cache after small updates or when experiencing odd behavior.
Sometimes a hard reboot works.
Any major upgrade needs a factory reset.
Avoid firmware updates if your 10+ is running fast, stable and fulfilling its mission.
I'm still on Pie, current OS load is over a year old with no issues, rock solid stable and fast.
blackhawk said:
Remember to clear the system cache after small updates or when experiencing odd behavior.
Sometimes a hard reboot works.
Any major upgrade needs a factory reset.
Avoid firmware updates if your 10+ is running fast, stable and fulfilling its mission.
I'm still on Pie, current OS load is over a year old with no issues, rock solid stable and fast.
Click to expand...
Click to collapse
True sir. However in my case I did all of the mentioned steps above to no avail. The only solution is to flash a custom firmware.
Thank you very much and have a great day.
henryfranz2005 said:
True sir. However in my case I did all of the mentioned steps above to no avail. The only solution is to flash a custom firmware.
Thank you very much and have a great day.
Click to expand...
Click to collapse
It should run right on the original stock firmware if it was running ok on it before.
That it's not may indicate a mobo failure. You found a work around for now but keep an eye on it. Maybe a C port PCB failure... they can do strange things.

Question AOD lagging

Hello,
I have an issue with my Pixel 6 Pro that is rooted with Magisk. When the always on screen is on and there is a timer or stopwatch running for example, it freezes for multiple seconds.
This only happens when the phone is not moving, if I pick it up from the table it starts working again...
Also, the fingerprint scanner doesn't light up when it is in this state.
I suppose it's not normal because my friend who has a Pixel 7 doesn't have this issue
Any idea of what could be causing this?
Edit: Here's a video of it happening
Edit 2: It can also be seen on screen recordings so i don't think it's a hardware issue (on these it just jumps to the next update so it doesn't hang but it skips multiple seconds at once)
I get all sorts of problems with my rooted 6 pro, including this. I've almost actually come close to snapping the device in half in my rage at the malfunction of it.
Is clock battery optimized? I can't remember if i had this issue, if i remember in thr morning i might try. What the shortest timer you've experienced this with?
fil3s said:
I get all sorts of problems with my rooted 6 pro, including this. I've almost actually come close to snapping the device in half in my rage at the malfunction of it.
Click to expand...
Click to collapse
Yeah I agree that this is really annoying, root shouldn't cause issues like this...
Nergal di Cuthah said:
Is clock battery optimized? I can't remember if i had this issue, if i remember in thr morning i might try. What the shortest timer you've experienced this with?
Click to expand...
Click to collapse
It always starts at 00:59 and it struggles to roll over to 01:00
I tried it with battery optimization off for the Clock app and turning off Adaptive battery but it didn't help
KszKristof said:
Yeah I agree that this is really annoying, root shouldn't cause issues like this...
Click to expand...
Click to collapse
After reading the post again and watching the video, this doesn't happen on my p6 pro.
How do you flash your updates? What was your experience like without magisk?
Good point in your reply, it's been so long since I've actually been non rooted
fil3s said:
After reading the post again and watching the video, this doesn't happen on my p6 pro.
How do you flash your updates? What was your experience like on stock?
Good point in your reply, it's been so long since I've actually been non rooted
Click to expand...
Click to collapse
I actually got the phone about a week ago and I rooted it instantly so I didn't use stock at all. But I flashed a13 through fastboot first to prevent bricking it due to the bootloader version.

Categories

Resources