Related
DISCLAIMER:
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
INTRODUCTION
This thread is mainly intended for devs (pro devs don't really belong here because they're pro and this thread is useless), for someone who need help to continue the work for Nova and fix the bugs on Pie (not many left). I'll help as long as you can speak English xD (no google translate because it can cause misunderstandings). However, don't expect me to spend the same time into this as i''ve did when i've had the phone. Yes, i no longer have the phone (it's still dead) and if you're not up to date with that, then you can read the announcement here and i've mentioned that i've got a new phone here. On top of this, i can't build anymore because i can't sign up on Google Cloud Platform anymore. I've wrote about this here at the hidden content (below as a side note).
Users can also help with doing researches, testing things and logs.
I don't know if i'll consider to continue working on it myself alone without the phone. I'd need at least to be able to build and then i'd need people to test new builds / flashable zips. At some point i might consider that because i'm missing this phone and the community xD.
SOURCES
Device: https://github.com/skinzor/android_device_huawei_hwcan/tree/lineage-16.0-last
Vendor: https://github.com/skinzor/proprietary_vendor_huawei/tree/lineage-16.0-last
Kernel: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
Click to expand...
Click to collapse
There's two branches:
1) lineage-16.0: those ones were used when i've booted Pie the first time. Remember that i've wrote about it here? Those ones were updated from mido's ones.
2) lineage-16.0-last. those ones are the last ones and updated, which i've used in my last build. Those ones were continued from previous branch and updated from tissot ones which were / are updated by another dev (not the same dev as on mido). I recommend to continue with this branch, but it's up to you. You might not be able to get a successful or bootable build anymore with lineage-16.0 branch anyway because lineage's sources were updated since then.
I've used mido's trees as reference for lineage 14 and 15 trees too. You can figure that yourself if you check mido's trees and then Nova's ones, as i've cherry-picked the commits. Why did i use mido's trees? Because:
1) It has the same qcom chipset as Nova.
2) It is a popular phone.
3) A good dev was working on it.
4) It has official lineage support.
Now you might ask why i haven't did myself everything from scratch. Well, as a newbie dev, it would've been much harder and would've took much more time. Also, i'd say that there's no point at all to do something from scratch when it was already done unless you want to go the "hard" way, assuming you have time and want to learn more. I've still learnt a lot since i've started.
There are "universal" commits which are about fixes / improvements that can be related to e.g. the android version or the qcom chipset and those commits are usually found in many device trees, so you just cherry-pick them. A good example would be this commit: hwcan: Use mke2fs to create ext4 images.
FIXING THE BUGS OF LINEAGE 16 / PIE
I assume that you've used lineage-16.0-last branch as i've recommended. I no longer remember what bugs had my last build, but i think that the bluetooth was working, while it wasn't working in the build made from old lineage-16.0 branch. However, i remember that it had a new bug and as far as i remember, it was the RIL, but the baseband was showing up. I think i've tried to fix it and i've got it working (i remember that it was about the blobs), but i don't remember how. As of typing now, i've looked into the logcat which i still have and i've seen this:
Code:
F linker : CANNOT LINK EXECUTABLE "/vendor/bin/tftp_server": library "liboemaids_vendor.so" not found
That kind of error is self explanatory: the blob / lib is missing. After i've seen this, i've remembered that it's a new blob which got added in the original commit and which i've cherry-picked here. I didn't include that blob for a reason, but i don't remember that reason lol (it's not that i've forgot it, but i've skipped it for a reason). I remember that back then i've added the blob manually after i've seen the error, but i don't remember if that's what fixed the RIL, so you can try that and let me know.
As i've said already, i don't remember what bugs had that build besides the RIL, so you can try it and let me know.
At the introduction i've mentioned that i can help. I'll help only here on XDA in this thread because it may help other people too if they're having the same error / problem and after all, it's nice to have a thread like this in my opinion.
You can attach the log or paste it to gist github, pastebin, del.dog or any pasting website, but don't paste it in the XDA post because it just sucks.
Click to expand...
Click to collapse
DOWNLOADS
MEDIAFIRE | ANDROIDFILEHOST
As i've recommended to use lineage-16.0-last branch to build / continue the development, i also recommend to flash that build.
The build from lineage-16.0 branch folder doesn't boot. Back then, when i've seen that it doesn't boot and took a look at the logcat, i've tried the graphic blobs from the tree of zenfone 3 and that one was using them from nokia 7 plus (based on the commit). I had two zips in my PC and i've uploaded both. The first one created is graphic_pie_blobs_zenfone3_nokia_7_plus.zip and the second one sdm_blobs_zenfone3_nokia7_plus.zip, so you flash them in that order. As i've mentioned in that post in which i've said that i've booted Pie, there is some lag / glitches while scrolling, due the display / graphic blobs.
ENDING
As i've promised, i've pushed the tree sources and uploaded my first and last build. The reason i'm willing to help in fixing the bugs is because i'm missing this phone and this community here on XDA (as i've expected xD). It was fun and thanks to this phone and y`all for your support and kind words, i've learnt so many things in this journey. That's simply unforgettable for me.
Hopefully someone will jump on and continue the development further. I'll be here to help.
XDA:DevDB Information
[DEV][9.0] LineageOS 16, ROM for the Huawei Nova/Nova Plus
Contributors
#Henkate
Source Code: https://github.com/skinzor/android_kernel_huawei_msm8953-1/tree/lineage-16.0-last
ROM OS Version: 9.x Pie
ROM Firmware Required: Unlocked bootloader, TWRP
Version Information
Status: Testing
Created 2019-01-02
Last Updated 2019-01-05
Reserved
Reserved
Thank you for all the hard work you put into this. I would try to follow the leads, but for me this phone is dead now. I had hoped it would be something, but naw, just a hunk of something. Maybe someone can pick it up and go with it, encouraged everyone to try. If you are thinking about it Robert @#Henkate will help you. Great person, and this phone got me to know him so boom, good phone.
Maybe this should be in off topic thread, but I will post here.
Thank you for the great work that you have done. You gave us nougat, oreo, almost a pie. LineageOS 15.1 is the best firmware I have ever used. EmUi far behind. Thanks again a lot. Pie is full of bugs (I have already tried), counted a huge list of 10 items, but I think it's time to relax. You gave nova a second life and for that I am grateful to you. I found out that you are switching to another phone. Good luck in developing it, you are a good developer, the main thing is to believe in yourself!
Hi enkate... does wifi calling work on 16 ?
thanks
virusdunil said:
Hi enkate... does wifi calling work on 16 ?
thanks
Click to expand...
Click to collapse
He has no way to check. Maybe someone who has flashed it could test.
wow！thx a lot，I will try it now！
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Alee.se said:
Hey Henkate !, Yesterday I installed LOS16, the last build that you compiled, botched and everything, but at the moment of continuing with the initial configuration, the screen does not give an image, the touch works, but it runs out of image: /
Click to expand...
Click to collapse
With the first build go two files, except for the firmware, responsible for the display. Flash them after flash lineage 16 last build and everything will work
Logcats
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Vinnom said:
Hey there!
Finally tried it. I flashed just the latest build and there is what I got:
After flashing only ROM, it booted, but nothing was drawn at the display. Ok, that was expect
Then I wiped system and data again, flashed the build and both of the other zips (from the first build folder)
It booted fine, RIL was working at start, wifi ok. Many other things couldn't be tested, because randomly (one time taking photos, other when scrolling settings, other when trying to test bluetooth) screen went black the blue led got lit up.
I took a logcat only with errors and it seems there is a lot to fix. Still today (just a lot later today, I have to work) I'm gonna fetch los 16 trees, but I still have no idea how to solve any of the bugs. I'll do a lot of search though.
Here is the gist I made with the logcat I took. Any help would be appreciated.
EDIT
just forgot to mention that besides RIL working, I couldn't make a call (display went black and blue led). When rebooted it, I had no signal reception at all
Click to expand...
Click to collapse
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Disable out sim card
AssasinAkindinov said:
Disable out sim card
Click to expand...
Click to collapse
ye, phone in airmode workrd normally,
AssasinAkindinov said:
Also to the list of bugs: personally, my phone did not work with a SIM card, constant crash of applications. The YouTube crash, the camera does not take a photo (camera stock), after restarting, the fingerprint disappears (it is not deleted from memory, but it can only be unlocked if you make a new fingerprint) Any heavy application will crash after a while
Click to expand...
Click to collapse
penk3 said:
Thx for u work, I have a reboots after few mins the system starts
nova canL11, cant reply link to adb bugreport logs x_x
Click to expand...
Click to collapse
Sorry guys, no mean to be rude here, but this thread is for development purposes. My point in posting was to give a logcat and receive help to try and fix the bugs I found. I know that when possible, #Henkate gonna take a look and give some directions, so work can be done. So, if you wanna test and see if the rom works for you, that's fine, but provide logs, please. It's good to have other logs and be able to compare if the bugs are the same and I think it can help development a lot (no need to flood with logs either, be reasonable).
Unbrick no screen.
To repair the phone (when there is more image) it must start in fastboot mode and then flash boot image) wait for the phone to go off or remove the battery. When it is off plug the usb cable c on your huawei nova and the phone will show that the phone is charging. Now you can reflash another rom but not lineage os 16. Sorry i use google translation
Android 9 with jdi screen
Android 9 with jdi screen
Amazing near.
As it is known, custom firmware was not friends with the jdi screens.
And here came LOS16 on Android 9. Read reviews that it is now not usable even on smartphones with "normal" screens, what can we say about JDI
But from the realization that he had bought a new phone and having a lot of time, the thought crept in to try to put a fresh custom for total disappointment in his smartphone and quiet use of the new.
However, not everything is so simple. After the first launch, the screen began to flicker well, I thought everything had arrived, now it will get dark and the sensor will fail. Cured with just one reboot. more of this did not happen.
Sim cards did not pull out (I have 2 of them), some wrote that because of them there were some problems crashing and rebooting the system (I don’t have that)
After a night out, the interface began to respond with a delay of 0.5 seconds. (It was cured by a complete reboot) ..
Quickstep launcher is often closed with an error
The camera does not remove the drain, installed from the playlist of the market works without comments.
The navigation bar disappeared after a telephone conversation, when the interlocutor first completed the call (It was decided to reboot)
Vkontakte application crashes, but I use Kate Mobile, it flies with a bang.
YouTube crashes
The sound from the conversational dynamics is quiet, I think you can fix it in the mixer_paths but this is not exactly
Waiting for the moment until the screen fails.
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
R0mi4 said:
All right, testing 9 android is over!
Discharged the battery to 0, the phone turned off, when turned on, the painfully familiar symptom with the diagnosis "JDI", no image, the screen backlight is on.
Hope no more. I return the phone to the stock and sell it, turn to Meizu pro 7. Thank you all!
Click to expand...
Click to collapse
Ты все посты будешь переводить и сюда кидать?) (It is joke)
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Did you ever flashed Q or Downgraded from Q to P?
Sent from my Redmi K20 Pro using Tapatalk
Sukhi said:
Did you ever flashed Q or Downgraded from Q to P?
Click to expand...
Click to collapse
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Aliosa007 said:
Originally was Android 9. My first ROM flashed was Xiaomi.eu V10.4.4.0 - Android Q. Later tried Android 9 and Android 10.
I have just tried to install Lineage ROM over Stable CN 10.3.17 ROM - it misses compass app, but random app from net shows that compass works good. I mage a backup of all partitions. Maybe it is possible to restore some partition over working Xiaomi.eu ROM to keep Miui working and make compass work too?
Click to expand...
Click to collapse
Like others, most probably you broke your device sensors while downgrading. Do a clean restore of Android Pie with a fastboot image. Extract the persist.img from the fastboot package and flash it to the persist partition through LR TWRP. Reboot and Calibrate your front Camera and let other sensors Calibrate aswell. Do a hardware test (*#*#64663#*#*) and you should be able to see values for x,y,z axis for most of the sensors. If the compass still doesn't work, you might have a defective item.
Sent from my Redmi K20 Pro using Tapatalk
Redmi K20 Pro persist backup required
I have tried steps you suggested and works everything except Gyroscope. As before. I have made testing using Sensors Multitool. Rotation vector Z is swinging from -1 to 1 all the time even if phone is still. Gyroscope info shows Z axis always -7 or more. Gravity reacts to movement, but unnatural. On Q everything worked until downgraded back to P.
I have found useful topic about this problem - https://forum.xda-developers.com/pixel-3-xl/how-to/android-10-sensors-bug-t3964904 . Reading through maybe will find something useful for my phone. I have never rooted my phone. Used Magisk few times. Persist.img I used was from Android 9 Chinese ROM 10.3.16 (As my phone is Chinese version). Persist.img was installed only with TWRP, it showed no problem when processed it.
Maybe someone can share backed up persist partition of Redmi K20 Chinese version? Hardware version in "All specs" page shows "Hardware version: V1". I got instruction to retrieve it. The following should put an image of the persist partition on the phone's internal storage. It should be executed on TWRP from Advanced > Terminal window.
Code:
dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
I have made md5 checksums of all persist.img I have in each firmware. Despite file size is same, content each time is different.
Code:
7d75bd5108cf8407431033a96c9da195 *d:\temp\Xiaomi\raphael_global_images_V10.3.2.0.PFKMIXM_20190911.0000.00_9.0_global\images\persist.img
35c6ae0b8ddfffaa2f77525f7d4dc57b *d:\temp\Xiaomi\raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn\images\persist.img
80115db34f9af4b8a4a105dc675f7fa0 *d:\temp\Xiaomi\raphael_images_V10.3.17.0.PFKCNXM_20190816.0000.00_9.0_cn\images\persist.img
a7fb2b49e181096e3345b64b1982b990 *d:\temp\Xiaomi\raphael_global_images_V10.3.1.0.PFKMIXM_20190805.0000.00_9.0_global\images\persist.img
3283790361d575e355929f995c904d23 *d:\temp\Xiaomi\raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea\images\persist.img
2ceeb38f7ca1c32afe6d842d2e9f0ed4 *d:\temp\Xiaomi\raphael_images_V10.3.16.0.PFKCNXM_20190718.0000.00_9.0_cn\images\persist.img
a9e78a1299431e19de73a847c22bc7cc *d:\temp\Xiaomi\raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in\images\persist.img
b979fadaae21f397f4f1f46282305248 *d:\temp\Xiaomi\raphael_images_V10.3.15.0.PFKCNXM_20190709.0000.00_9.0_cn\images\persist.img
dad5c8526ae0c598b31a6c58184bb81b *d:\temp\Xiaomi\raphael_images_V10.3.11.0.PFKCNXM_20190619.0000.00_9.0_cn\images\persist.img
40ddaa6840e63bdf6d04bfb84352bf56 *d:\temp\Xiaomi\raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn\images\persist.img
fff3410c7cf4c3cb5f5490b1dc252c3f *d:\temp\Xiaomi\raphael_images_V10.3.7.0.PFKCNXM_20190528.0000.00_9.0_cn\images\persist.img
03a89f80aa1f3804c03403aa9bdace29 *d:\temp\Xiaomi\raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn\images\persist.img
User which requires sensors fix should do following:
1) Open root shell
2) dd if=/dev/block/by-name/persist of=/sdcard/persist_backup.img
3) Copy new persist.img to your sdcard home directory
4) dd if=/sdcard/persist.img of=/dev/block/by-name/persist
5) Reboot device
Click to expand...
Click to collapse
So, maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Hey, I have the same problem and this is getting me crazy. Have you solved the problem?
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Aliosa007 said:
No, I got tired trying and now use phone with this problem. I get to much effort live without my new phone as I need on my daily life. Lineage os is not interesting to me too use for working sensors but without miui.
Click to expand...
Click to collapse
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Ok, please returns here after your try and let us know you got sensor fixed
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
hmmm i am seeing a pattern , where many had problems after flashing roms , odd , anyway how to tell needle on the app is really facing north ?
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
mykel_s said:
It occurs also on my Mi 9T Pro with official global ROM... Compass spins constantly over Z-axis. It is especially visible for instance in Google Maps and annoys a lot. I think I will wait till MIUI 11 release and then maybe return this phone unless it will recover.
Click to expand...
Click to collapse
Yes, looks like it occurs with officials ROM too if ROM was uploaded by FASTBOOT mode. Stock sensor settings gets rewritten with universal settings which do not work as desired.
Yes it seems so. The worst thing is that, it was working just fine at the very beginning, compass was lost just few weeks after I bought the phone
In the meantime maybe there were two official OTA updates, nevertheless I cannot recall what could cause loss of this functionality.
Thanks for your comment anyway.
KingMinePlay said:
Oh, sad to hear that. Don't worry, I'm going to get a new persist.img from a friend of mine's Redmi K20 Pro next weekend. Hope it fixes the issue. I don't really know why this is happening to our phone :crying:
Click to expand...
Click to collapse
Hi, weekend had passed. Did you tried to fix your K20 pro with your friends phone`s help? It is very interesting how it gone
maybe someone with K20 Pro CN version can share their persist.img file with me and others?
Aliosa007 said:
Hello,
First firmware I was using was Chinese firmware and it worked fine (OTA was updated to 10.3.17). I used it until I got permission to unlock my bootloader. Then every other firmware from Mi or Xiaomi.eu have this problem. I cannot calibrate compass - in compass application or maps app my direction is spinning all the time counter-clockwise. Spin speed is ~5 spins in 3 second. Tried to clean compass app cache - do not help.
Tried to test sensors - in "all specs" click 5 times on Kernel and enter CIT. Result - Accelerometer looks working fine, Gyroscope - Z axis shows -7 all time, Magnetic sensor - spins counter-clockwise all the time.
My bad I have formatted all system before flashing firmware, that may get lost of original "persist" and "vendor" images if they are required.
Summary - looks like gyroscope sensor is failured - Z axis shows -7 rad/s all the time and that makes some functions hardly usable. Compass included.
Phone did not had any drops all the time. Only magnetic car holder was used, but cannot remember it happened same day. It was used with previous phone too and it still worksfine.
I have tried many Cn stable Roms, Indian roms, EEA, Xiaomi.eu. Installing in fastboot mode. No one firmware works fine with compass application.
Several fastboots tried:
Code:
raphael_eea_global_images_V10.3.1.0.PFKEUXM_20190723.0000.00_9.0_eea
raphael_images_V10.3.6.0.PFKCNXM_20190516.0000.00_9.0_cn
raphael_images_V10.3.8.0.PFKCNXM_20190601.0000.00_9.0_cn
raphaelin_in_global_images_V10.3.3.0.PFKINXM_20190711.0000.00_9.0_in
raphaels_images_V10.4.1.0.PFKCNXM_20190827.0000.00_9.0_cn
Recovery ROMs tried:
Code:
xiaomi.eu_multi_HMK20ProMI9TPro_V10.3.17.0.PFKCNXM_v10-9.zip
xiaomi.eu_multi_HMK20ProMI9TPro_V10.4.4.0.QFKCNXM_v10-10.zip
Maybe you can suggest any possibility to fix this? I assume that should be software issue.
Click to expand...
Click to collapse
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
vichucoolics said:
Even mine was screwed up..I taught I'll have to take it to service centre ....I had formatted system ...and when I installed fastbiit ROM..the gyroscope and accelerometer was not working.. unfortunately I had relocked my bootloader and had to wait for 30 days to flash persist file....so I just gave factory reset from settings a try..and it worked
Click to expand...
Click to collapse
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Aliosa007 said:
You did factory reset from ROM version you have uploaded via FASTBOOT earlier and that worked? What persist file you have used? And how compass functionality - works? Fastboot ROM version accelerometer works fine, but compass fails.
Click to expand...
Click to collapse
At first my gyroscope also wasn't working....I didn't flash any persist file but now I can see that the compass is buggy... And also the video recording is buggy.... Hope after flashing miui 11 upcoming update it fixes things
I have the same issue. Don't know how to fix it. Am already using miui 11
You are good to go: https://forum.xda-developers.com/k20-pro/help/auto-rotation-issue-custom-roms-t3983169/page2
Let me know if I helped you...
Hi,
I joined beta and updated to android 10. But it's not working fine for me and I want to revert back to colour os 6 (android 9), how can I do that ???
Thanks.
Hello, I would also like help to do the same thing .. so if a charitable soul would help us please! Me is especially for the wifi network which is really bad on Android 10 is the Stability. Thank you to those who come to help us
Hi Friend,
Let see if i can help you.
I come from LOS, after some hours i decide to come back to COS 6.1
You need to dowload COS 6.1 ozip custom recovery flashabe
Folow this steps:
Go to TWRP ( I donw know steps for OrangeFOX )
Wipe / Factory Reset ( Swipe to Right for Factory Reset )
Go to Install and Flash COS 6.1 OZIP
Reboot bootloader
Flash vbmeta stock img ( fastboot flash vbmeta vbmeta.img )
Go to TWRP Again and Format Device ( Wipe - Format, write "yes" ) after format restart system.
If you want i can share a folder with all stuff
Sorry for my english
The X2Pro Community/Information is still small.
Im on COS 6.1 BL unlocked and Rooted, and i like, all funtions work, face unlock, nfc, fp, camera modes , Macro, Ultra HD, Slow Motion, Night Mode.
Later i will Lock BL and Remove Root, stay all original, and w8 for official update, no need to use VPNS or other stuff to update for last(Beta) roms, but im afraid brick device after lock bootloader.
If Realme sell X2 Pro with COS 6.0/6.1 it means the rom full working.
I prefer wainting for stable rom like COS or RUI.
If RUI has the same funtions like COS i update.
We have alot of good devs , but i read some stuff about Realme not release kernel sources, i dont know much about this...
Tell me if steps work for you.
go back to coloros 6 android 9
LuisWRX said:
Hi Friend,
Let see if i can help you.
I come from LOS, after some hours i decide to come back to COS 6.1
You need to dowload COS 6.1 ozip custom recovery flashabe
Folow this steps:
Go to TWRP ( I donw know steps for OrangeFOX )
Wipe / Factory Reset ( Swipe to Right for Factory Reset )
Go to Install and Flash COS 6.1 OZIP
Reboot bootloader
Flash vbmeta stock img ( fastboot flash vbmeta vbmeta.img )
Go to TWRP Again and Format Device ( Wipe - Format, write "yes" ) after format restart system.
If you want i can share a folder with all stuff
Sorry for my english
The X2Pro Community/Information is still small.
Im on COS 6.1 BL unlocked and Rooted, and i like, all funtions work, face unlock, nfc, fp, camera modes , Macro, Ultra HD, Slow Motion, Night Mode.
Later i will Lock BL and Remove Root, stay all original, and w8 for official update, no need to use VPNS or other stuff to update for last(Beta) roms, but im afraid brick device after lock bootloader.
If Realme sell X2 Pro with COS 6.0/6.1 it means the rom full working.
I prefer wainting for stable rom like COS or RUI.
If RUI has the same funtions like COS i update.
We have alot of good devs , but i read some stuff about Realme not release kernel sources, i dont know much about this...
Tell me if steps work for you.
Click to expand...
Click to collapse
can you please provide some links to download or detail steps to install TWRP?
ste27.jah said:
...Me is especially for the wifi network which is really bad on Android 10 is the Stability. Thank you to those who come to help us
Click to expand...
Click to collapse
my issue is very stupid stupid stupid, did i say stupid already? the volume for in on call (non speaker mode) is SUPER loud. and yes i already have it all the way low.
it was high on coloros 6 android 9 but tolerable, but on android 10 its ridiculously loud - the office next to me can hear my conversations(and wifey when home) and i have to place phone like if i had it on speaker phone. did i already say this issue is stupid. anyone know a fix for this? (i know, i will create new post for my issue)
i really like this phone a lot for its price/spec and if there is no way to go back to coloros 6 android 9, im prob end up selling this just because of this stupid issue. Im in south cali fyi if anyone is interested in buying
Follow this tutorial:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
Humm... If you are on official Android 10 update without BL unlocked and stock recovery I think will not work .
Try this one first:
Go to this website: https://www.realme.com/eu/support/software-update
Download COS 6.1 and flash via stock recovery.
Steps: https://www.realme.com/eu/support/software-update#
Hope this helps
LuisWRX said:
Follow this tutorial:
https://forum.xda-developers.com/realme-x2-pro/how-to/guide-unlocking-bootloader-to-getting-t4010189
Humm... If you are on official Android 10 update without BL unlocked and stock recovery I think will not work .
Try this one first:
Go to this website: https://www.realme.com/eu/support/software-update
Download COS 6.1 and flash via stock recovery.
Steps: https://www.realme.com/eu/support/software-update#
Hope this helps
Click to expand...
Click to collapse
This is what i have: Realme X2 Pro global or EU version with the new Android 10 version
I tried installing COS 6.1 from your link using stock recovery "Install from storage" but i get a "Installation failed The installed version is lower than the current", which i think means that i have a higher version of android and i want to install a lower version, and it is not allowed.
are you saying that i need to have bootloader unlocked to go back to stock COS 6.1?
in my case I already had the BL unlocked when I did the update. then I go back to Android 9. in your case with the BL locked it shouldn't be the same procedure
I update today to RUI because Im facing an issue with Buttom micro, not working. I update from COS 6.1 to RUI and the problem its the same. Its a hardware problem, only top micro works.
LuisWRX said:
in my case I already had the BL unlocked when I did the update. then I go back to Android 9. in your case with the BL locked it shouldn't be the same procedure
I update today to RUI because Im facing an issue with Buttom micro, not working. I update from COS 6.1 to RUI and the problem its the same. Its a hardware problem, only top micro works.
Click to expand...
Click to collapse
i updated to the latest C24 update and i still have the same problem, voice in-call volume for the earpiece is super loud that will make me deaf if i dont place phone at least 3inches away from my face(again, basically like if it was in speaker mode but its not), and i also have similar issue like you where i think bottom mic does not work sometimes. What i have found out with the mic is if i put the phone in speaker mode then switch back to earpiece mode, the bottom mic works(i think?). Have you tried something similar?
I know you dont have the same loud ass earpiece volume issue but the mic issue is similar to mine...did we get brick/lemon phones or is this more of a software issue? Why havent more people reported this then? or nobody here makes voice calls anymore?
---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------
LuisWRX said:
in my case I already had the BL unlocked when I did the update. then I go back to Android 9. in your case with the BL locked it shouldn't be the same procedure
I update today to RUI because Im facing an issue with Buttom micro, not working. I update from COS 6.1 to RUI and the problem its the same. Its a hardware problem, only top micro works.
Click to expand...
Click to collapse
Do you know or does anybody know if when you are rooted can you adjust the "build.prop" file and adjust the top(earpiece) and bottom speakers volumes? what about the mics levels?
LuisWRX said:
We have alot of good devs , but i read some stuff about Realme not release kernel sources, i dont know much about this...
Tell me if steps work for you.
Click to expand...
Click to collapse
thanks a lot, it's working!
I've tried downgrade from realmi UI for almost 24 hours, and only your tutorial helped.
Hello
I have the RMX1931 with the bootloader unlocked and the twrp recovery [3.3.1-13] installed
I want reset my phone because have random reboots.
Download RMX1931EX_11.A.10 for twrp
First wipe this partition
Cache
Dalvik
Data
Click to expand...
Click to collapse
Then flash
Ozip RMX1931EX_11.A.10 for twrp
Vbmeta
Magisk
Click to expand...
Click to collapse
But dont boot in system
first boot not see realme logo and reboot in twrp
i try restored old backup twrp clear device but same results.
only work backup twrp with data partition full, that I did before starting this experiment.
I believe it is the given partition that makes the device boot. With this clean partition it goes into bootloop
please help me
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
Tonight i try.
Thank you
perisman said:
Flash ozip
Flash vbmeta
Flash magisk
Format data
Reboot
Click to expand...
Click to collapse
you are a genius.
IT WORKS.
Now I have installed the A10 system and restored the app backup via swiftbackup.
everything seems to work, I hope it will not restart.
if you can give me more advice.
thank you very much.
EDIT :
The phone continues to restart.
I'm thinking it can be Magisk root.
Without applications installed
I went crazy with this problem
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
it is a real dilemma because with the clean system, however, the phone has restarted for no obvious reason.
I can't understand what makes the phone restart.
only Magisk could be the cause.
I installed Magic which recommends Jerry. but even with the standard version the problem was always the same
Now I send you a screen so it's better evident.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Try Another rom, clean system one day to see what It happens
Yes I try In These Days.
Thank you so much for your support
perisman said:
Try Another rom, clean system one day to see what It happens
Click to expand...
Click to collapse
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
perisman said:
You can try with last update C25. I flashed from twrp, and now t'he device works fast and smooth. I have magisk, viper4android installed. T'he only problem us FP, because unlocked BL. You can try with a custom ROM, I have tried phh treble and aosip 10, and works very well, and FP works also. You cqn revert to color os 6.x allways flashing A10 ozip. If with other ROMs hsppens t'he random reboots, then is a hardware problem.
Click to expand...
Click to collapse
i try lienage os, but now i want return colorOS.
i try flashing A10 colorOS.ozip but color OS Boot Loop (Stuck in Realme Logo)
you have solution? for now flash lineageOS and work well but i want colorOS.
please help me
-First, change twrp. Install orangefox or skyhawk twrp (I am using skyhawk and I can revert from C10 trebled rom to
C26 backup, firsr install C26 ozip, and after first boot, reinstall twrp from fastboot and restore full backup)
-Reboot to twrp
-Flash full Ozip , I recommend C26. Works very well, antutu 501.850, no lags, with viper4android installed. With
lineage 371.056 in antutu
-flash vbmeta
-flash magisk
-format data
-reboot
-Once system boots to system, reboot to fastboot to reinstall twrp (with ozip install, you have stock recovery,
check this booting it, depends of twrp you are using. Orangefox saves twrp, skyhawk no)
I hope it helps
I should follow these steps
1 - flash recovery skyhawk twrp
2 - Reboot to twrp
3 - Flash full Ozip (i prefered pie have Fingerprint work)
4 - flash vbmeta
5 - flash magisk
6 - format data
7 - reboot
I have already done these steps with the (ozip A10 FOR TWRP) but color OS Boot Loop (Stuck in Realme Logo).
do you think that recovery creates this problem?
i now have lineageOS work but want return colorOS
thanks for the support
EDIT:
I have run your advice but unfortunately this device perhaps has a hardware problem.
Whenever it manages to boot, just 30 seconds and restart.
I noticed artifacts when starting the sistama.
I'm really desperate.
what do you advise me to do?
thanks
westenlive said:
I am now testing the LINEAGE it happened to me this I removed the SIM card and I installed the costum Rom, I made the various customizations and the phone never locked OR restarted.
I inserted the SIM card in the phone worked perfectly, then having messed up with luckypatcher I had to reinstall the Rom.
So I performed the same procedure with the SIM card inserted in the phone and already at the first start it was unstable with reboots.
Currently I have applied for a change of sim card.
As soon as it arrives I will try to remove the sim card Install from scratch The system is to insert the new SIM card only so I can have the mathematical certainty that it is the SIM card
I hope my experience can help someone
Click to expand...
Click to collapse
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
JKD23 said:
Hi, I also have rebooting issues does your X2 pro still reboots? Did changing sim cards solved your reboot problem Im getting desperate.
Click to expand...
Click to collapse
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
westenlive said:
sorry to tell you but unfortunately this phone has an underlying problem ie the modem hardware is of poor quality.
I have done 1000 tests I have tried everything and more but unfortunately it keeps restarting the user interface when a call comes in or when you try to make a call.
especially when you keep the modem busy for other chores such as navigation with Google Maps or other and you receive a call the phone suffers a stress and this causes a restart.
I have given myself this explanation because it is truly inconceivable that a top-of-the-range phone has these problems.
if you find a solution Let me know.
Thanks so much
Click to expand...
Click to collapse
Sorry to hear that ? I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. ?
If I find a solution I'll let you know.
JKD23 said:
Sorry to hear that [emoji853] I'm also suspecting that I have hardware problem it only reboots when connecting to LTE mobile data. I already tried using flash tool for a clean flash didnt work though.
I'm still hoping it's a software issue because I can still get LTE signal I just can't use mobile data. I kinda regretted buying this phone. I'm so unlucky I got a defective device. [emoji24]
If I find a solution I'll let you know.
Click to expand...
Click to collapse
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
westenlive said:
Basically these have mounted a modem on this phone which in my opinion is not fully compatible with the Snapdragon.
In fact, the price is really very low if you consider that this is a top-of-the-range Smartphone with a 90 Hertz screen and latest generation processor.
They are practically giving it away now on the official website it costs € 350.
Click to expand...
Click to collapse
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
JKD23 said:
Realme should acknowledge these problems and improve the quality of their units. Let's hope Realme Dev team would release updates that could fix our units. (fingers crossed)
Click to expand...
Click to collapse
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
westenlive said:
Dear
since you texted me I have been looking for the problem once again.
I have ILIAD as an operator.
I had self-configuring SMS sent for APNs.
With the new APN the problem seems to have disappeared.
try it too and let me know
hello [emoji1309]
Click to expand...
Click to collapse
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
JKD23 said:
That's good to hear, I tried your suggestion using self configuring apns through sms, my other operator doesn't send me any sms while the other one was not self configuring. Doesn't seems to work for me Ill try again rechecking the APNs. I also pulled an ADB bug report and sent it to Realme Devs through email they haven't replied yet. When I opened it I saw a few errors like but I couldn't understand it since im not a dev but a run some hardware and sensor diagnostics app and all sensors seems to be working fine. I hope the devs would reply sooner.
Click to expand...
Click to collapse
Hi dear
have you tried to update to Version: RMX1931EX_11.C.32.
From the log it would seem that they have solved the problems that happen to us.
I have the phone too full and rooted and I would not like to update to android 10 so I am still stuck on android 9.
Have you updated?
Hi everyone
I Update my MI 9 Global to android 10 ( MIUI 11.0.6 Stable QFAMIXM) but after setup finish and phone rebooted the touch screen dont work any more.
one month ago my phone touchscreen broke and replaced and worked great before update (android 9 on MIUI 10.2 I think )
but after update it does not react at all . i installed custom recover twrp and installed new rom from xiaomi.eu but nothing changed. :crying:
I connect optical mouse throw otg cable to phone and every thing works normal. sound , network , wifi , bluetooth , camera , .... all work great but touch screen doesnt respond .
I think the problem is kernel dont load driver for touchscreen properly or the new android dont load firmware for touchscreen.
it is dmesg output :
https://pastebin.com/i4Cfyden
if you look at dmesg log you can see some line with error like :
"Firmware in the chip different from the one that was burn! " and "fts_fw_update: firmware update failed again! ERROR 82080B02"
please help me to solve this problem . if I have to use custom kernel or change and compile the driver for new touchscreen ??
based on dmesg log (Read FW from BIN file st_fts_f1.ftb !) firmware must be in file "st_fts_f1.ftb" but I cant find this file in phone memory. I have root access to phone and searched all folder ( including vendor and persist partitions )
Just flash the previous Android version that worked. It sounds as if you bought an aftermarket screen with different hardware.
invisiblewave said:
Just flash the previous Android version that worked. It sounds as if you bought an aftermarket screen with different hardware.
Click to expand...
Click to collapse
hi thanks for your answer. I guess you are right. My Touch screen Replaced and this new hardware does not detected by kernel or need new firmware . I want to know haw can I include it in kernel .How the old vesrion can detect replaced touch screen but new one cant ?? Please Any one exprienced in Kernel Development help me to solve this problem . I dont want to downgrade to android 9 :crying:
I still have problem with android 10 roms . I install several different roms ncluding unofficial lineage 17.1 , Xiaomo.eu rom , MIUI Global 11.06 and ... but none of them detect touch screen even in twrp recovery there is no touch screen and had to use optical mouce to install and test new rom .
I currently downgrade to android 9 ( MIUI Global 10.2.14 ) and everything works normal . If anyone like me have problem with android 10 roms ? please help
MiFlash a stock Android 10 ROM
badaas said:
MiFlash a stock Android 10 ROM
Click to expand...
Click to collapse
thanks for reply:good:
I already download and installed Fastboot stock rom ( cepheus_global_images_V11.0.6.0.QFAMIXM_20200420.0000.00_10.0_global )
But again touch screen dont work . If flash using MiFlash is different from Fastboot instal ?
Yes miflash does some lower level format install
badaas said:
Yes miflash does some lower level format install
Click to expand...
Click to collapse
Ok I will check this method and report you . thanks for your suggestion
badaas said:
Yes miflash does some lower level format install
Click to expand...
Click to collapse
Hi . I flash v11.06 using miflash and again tuch screen doesnt work . I checked clean all option in flash page
I Installed android 10 GSI Rom from https://github.com/phhusson/treble_experimentations and touch screen and finger print sensor start to work !!
but GSI have some problem and limitation for mi 9 for example battery is not so good and full screen gusttures dont work. how is possible touch screen works with this rom but not by official Android 10 ?? If i can use some part of GSI with Official or Xaiomi.eu roms to enable touch screen ?
Maybe pocket mode is interfering on stock ROM?
Try a old stock Chinese ROM?
Start from very old..
badaas said:
Maybe pocket mode is interfering on stock ROM?
Try a old stock Chinese ROM?
Start from very old..
Click to expand...
Click to collapse
How Can I test that ? And yes all android 9 ( official or xiaomi.eu ) work but have some minor finger print problem . But The only Android 10 that has not problem with touch screen is GSI rom even GSI v220 ( based on android 10 ) works . I dont know how this is possible ? I based On this I am sure the problem is software not hardware . A question Sir : If touch screen driver in Kernel (boot.img) or in vendor ? I think If I can merge vendors or kernel from android 9 with system and other from android 10 the problem is solved. Thank you and Please any Of your help and info can solve the problem
I have the same problem, Mi9 running MIUI10 Global, want to upgrade to MIUI11 but after update the touchscreen doesn't work, only via otg USB mouse. Tried to flash MIUI12 ia TWRP, again touchscreen doesn't work.
Have you solved the problem?
Same problem
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
richnbeauty said:
I have the same problem, Mi9 running MIUI10 Global, want to upgrade to MIUI11 but after update the touchscreen doesn't work, only via otg USB mouse. Tried to flash MIUI12 ia TWRP, again touchscreen doesn't work.
Have you solved the problem?
Click to expand...
Click to collapse
unfortunately i dont find any solution yet. and i think no one is kind enough to help us . Now I am sure it is kernel problem. i installed GSI android 10 on android 9 vendor and touch screen works great ( but have some other problem with GIS like cant recieve or send sms messages) So the problem Is kernel used in android 10 . even i installed Quantic-Kernel on aosp and after that again touch screen stop working.Please if any senior member who is familiar with android kernel help us to compile or change touch screen driver used in version 9 and solve the problem . Please Please
br.tgo said:
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
Click to expand...
Click to collapse
Are You using android 10 or 9 ? I think your problem is different because My touch screen dont work AT ALL after upgrade to android 10 . but in android 9 there is no problem
br.tgo said:
Guys, has anyone managed to solve this problem?
Mi 9 After changing the screen the touch locks after a few minutes of use
My Mi 9's screen broke and I had to change it, but after a few minutes of use the touch simply stops working.
It happens a lot when I lock the screen, and I try to unlock it after a while.
Guys, I've been looking for the solution for some time but I just don't think so. I even found some forums saying to downgrade to version V10 but I still have this problem.
The screen is original, imported from CHINA and is of high quality.
Has anyone had this problem and can share the solution?
Click to expand...
Click to collapse
hamedpc007 said:
Are You using android 10 or 9 ? I think your problem is different because My touch screen dont work AT ALL after upgrade to android 10 . but in android 9 there is no problem
Click to expand...
Click to collapse
I'm using android 9. But even so, it keeps crashing.
br.tgo said:
I'm using android 9. But even so, it keeps crashing.
Click to expand...
Click to collapse
You can install new Rom and see if the problem gone or no . I recommentd you install new stock android 10 with MIUI 12 or xiaomi.eu rom .
If after new install problem exist it may be some hardware problem . Even before install new rom you can reset factory your phone and see what happens ( backup up your data before reset factory)
hamedpc007 said:
You can install new Rom and see if the problem gone or no . I recommentd you install new stock android 10 with MIUI 12 or xiaomi.eu rom .
If after new install problem exist it may be some hardware problem . Even before install new rom you can reset factory your phone and see what happens ( backup up your data before reset factory)
Click to expand...
Click to collapse
Right. Dude, thank you very much for your help. As I live here in Brazil, there is almost no content talking about this error. Thank you one more time!!