Related
So some newer devices have been shipped with different components from the older ones and while everything works fine on recent miui versions, most custom roms have issues. So I'm creating this thread to document all the issues caused by these new components and any solutions to them in one thread. Please reply if you have any other issues caused by the new hardware or any solutions to them.
Fingerprint
Description:
Option to add fingerprints doesn't appear even after setting pin, pattern or password on non miui based roms.
/data folder contains goodix folder with contents on miui.
Cause:
Some devices have a new fingerprint sensor manufactured by Goodix which is not yet supported by non miui based roms.
Solutions:
miui and any miui based roms such as xiaomi.eu should still work fine.
The newest build of Santosh's CM has a fingerprint patch available that will fix it.
Wait for CM to add support for the new hardware to its source code.
Battery
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Fix was added to CM source code so the problem should be solved on all newer roms and kernels based on it now.
Flashing Radon 1.9 or above will fix it on any CM source based roms.
miui and other miui based roms such as xiaomi.eu should be fine.
Santosh's CM13 plust the camera fix works.
Mokee works fine.
Unofficial Ressurrection Remix works fine up until the 06/08 build.
This is the patch applied to Radon to fix the bug.
If you know of any other issues caused by newer hardware or solutions please tell me so that I can add it to this thread.[/QUOTE]
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
Added for the fingerprint sensor, using TWRP is still probably the easiest way to check for the battery bug.
dmemon said:
If possible, Can you also provide information about how to identify different components without changing roms?
Thank you.
Click to expand...
Click to collapse
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Santhosh's CM13 battery bug is gone if you flash his camera fix.
razr96 said:
Santhosh's CM13 battery bug is gone if you flash his camera fix.
Click to expand...
Click to collapse
Ok cool I'll add it to the post and test it out if I get a chance.
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
NTRNSTR said:
Description:
Battery is stuck at either -2% or 50%.
TWRP does not show battery percentage at all or constantly shows 50%.
Cause:
Possibly new battery controller hardware, by the looks of it the issue is related to the kernel, older CM kernel builds seem fine and so do newer miui builds however any rom using a new CM kernel build or based off it has the issue.
Solutions:
Santosh's CM13 plust the camera fix should fix it.
Click to expand...
Click to collapse
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
EkiFox said:
The camera fix works only with Santosh's CM13, not with other CM/AOSP roms
the new kernel Radon V1.8 by Umang96 does not fix the battery problem
Click to expand...
Click to collapse
I would expect it to work on all Santosh based roms, the camera fix must have modified something that flashing a new kernel overwrites, if we can figure out what the camera fix changes we might be able to get a fix for all roms.
---------- Post added at 02:11 PM ---------- Previous post was at 02:10 PM ----------
dna1982 said:
I hear of that Mokee is using Xiaomi device tree, I guess that is why it don't has the "-2% or 50%" issue...
Click to expand...
Click to collapse
Well that would explain it, but at least we have roms without the bugs, that should help figure out the problem.
any working custom kernels for -2% or 50% battery bug?
mega-samu said:
The sensor of fingerprints with aida64, it is possible to identify.
The battery only if flash the TWRP, for the present.
Click to expand...
Click to collapse
as far as i know AIDA64 is not a good way to see your fingerprint sensor it shows fpc102x for me but i have a goodix sensor, in fact i think the other ones with fpc sensors have a fpc 1035 not a 102x. i think a good was would be checking kernel log you should see the module name or checking data partition ( if you have root) or system/etc/firmware if you dont (i'm not sure about the second one but i can see some goodixfp data there)
just saying maybe it saves someone from lots and lots of confusion as i had when i bought my device
The new Radon kernel doesn't have the -2%/50% battery bug!
For the cm13 based roms : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
:victory: Now we can use any Official-CM based rom. Definitely adding this to the top of the list.
Reno_kun said:
The new Radon kernel doesn't has the -2%/50% battery bug!
For the cm13 based rom : http://forum.xda-developers.com/showthread.php?p=68012485 and few posts under there is a test version for MIUI rom
Click to expand...
Click to collapse
Yep just flashed official RR with this kernel and no battery bug!
Yes, there is just the lack of the support ou goodix fp and it will be perfect !
KaciPL said:
any working custom kernels for -2% or 50% battery bug?
Click to expand...
Click to collapse
Now there are, just updated the post.
Radon V1.9 Kernel does not cause the battery bug .......
Radon V1.9 Kernel does not cause the battery bug on "MIUI 8 by Xiaomi.eu 6.7.28 | Beta".
I got a test version from @Umang96 and successfully got below 50% battery level.
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
I lose data connection on any cm custom rom. It goes away for 50-60sec then it gets back
And if i flash radio zip, then security options crash
LiRi2000 said:
Any custom kernel working with goodfix fp ??
Sent from my Redmi Note 3 using Tapatalk
Click to expand...
Click to collapse
I don't think so, still a work in progress getting it to work.
At first Thanks to devs for a good progress in N based ROM for our little precious where miui is still on Lolypop.Though @gkalen made miuI usable for us.Thanx to him also.
I saw some debates about abandoning marshmallow based ROM halfway.But I think it's not true.Those ROMs was(not ARE) pretty much stable for us.No offence, they were much stable (I am talking about sound ,app and other crashing ,long charging period etc) than N.Yeah, I know that N is still on development. BUT now RR (M)and CM(M) are giving setting FC ,huge battery drain ,But those M based rom had no problems when there was maintainer for these ROMs.
So as the title says plz draw some attentions to those M based ROM and update them on lineage OS. I know every on busy but plzzz.M is not so outdated to be ignored.
I am mostly talking about CM (M) and RR(M).
ROCKY_ME said:
At first Thanks to devs for a good progress in N based ROM for our little precious where miui is still on Lolypop.Though @gkalen made miuI usable for us.Thanx to him also.
I saw some debates about abandoning marshmallow based ROM halfway.But I think it's not true.Those ROMs was(not ARE) pretty much stable for us.No offence, they were much stable (I am talking about sound ,app and other crashing ,long charging period etc) than N.Yeah, I know that N is still on development. BUT now RR (M)and CM(M) are giving setting FC ,huge battery drain ,But those M based rom had no problems when there was maintainer for these ROMs.
So as the title says plz draw some attentions to those M based ROM and update them on lineage OS. I know every on busy but plzzz.M is not so outdated to be ignored.
I am mostly talking about CM (M) and RR(M).
Click to expand...
Click to collapse
What you are talking about Is almost impossible
If we think on your question
There are users who will complain to update KitKat to lineage
What you are talking is and will not be done
There is a release ready version of CM 13 that is perfectly fine to use and if you want any additional features you can add xposed and customize it best as you can. I think what you are actually asking for is out of question.
The Hard Gamer said:
What you are talking about Is almost impossible
If we think on your question
There are users who will complain to update KitKat to lineage
What you are talking is and will not be done
Click to expand...
Click to collapse
Lol.....I am talking about MM to update lineage....not KitKat.
There are already lineage 6.0.1 ROMs for another device.Just for example
https://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588
ROCKY_ME said:
Lol.....I am talking about MM to update lineage....not KitKat.
There are already lineage 6.0.1 ROMs for another device.Just for example
https://forum.xda-developers.com/g4/development/rom-cyanogenmod-13-0-t3243588
Click to expand...
Click to collapse
I understand your curiosity about the update of marshmallow roms But there is nothing changed lineage Os 13.0 And also if you use nougat a week you'll forget about marshmallow
Sent from my Lenovo A6000 using Tapatalk
Prince153 said:
I understand your curiosity about the update of marshmallow roms But there is nothing changed lineage Os 13.0 And also if you use nougat a week you'll forget about marshmallow
Sent from my Lenovo A6000 using Tapatalk
Click to expand...
Click to collapse
I have been using nougat for almost 2 months .Tried almost all N based ROM.As I prefer mostly Lineage base and customizable rom.So I tried to stuck with LOS or RR or Tesla(aosp).At the point of smoothness N is better than M.But facing these issues:-
LOS:-charging time is 6hrson original charger(didn't try latest nightly build).
RR(N):-Battery drainage(don't know why )
Tesla(N):-app crashing(CoC,CoR,Boom Beach etc) and setting FC at some display option.
So I just requesting for a update of those M based ROM for regular using.Because M based ROM was much stable at these points.So I just want a single update these ROMs to lineage.As
CM(M):-can't find latest nightly download link
RR(M):-Setting is crashing after some usages and huge battery drain but at the era of M these were not present.
Now I am using miui Hellas(L) by gkalen though I am not very much fond of miui .But I have no choice.
Thanx.
Basically, marshmallow is out of range
ROCKY_ME said:
I have been using nougat for almost 2 months .Tried almost all N based ROM.As I prefer mostly Lineage base and customizable rom.So I tried to stuck with LOS or RR or Tesla(aosp).At the point of smoothness N is better than M.But facing these issues:-
LOS:-charging time is 6hrson original charger(didn't try latest nightly build).
RR(N):-Battery drainage(don't know why )
Tesla(N):-app crashing(CoC,CoR,Boom Beach etc) and setting FC at some display option.
So I just requesting for a update of those M based ROM for regular using.Because M based ROM was much stable at these points.So I just want a single update these ROMs to lineage.As
CM(M):-can't find latest nightly download link
RR(M):-Setting is crashing after some usages and huge battery drain but at the era of M these were not present.
Now I am using miui Hellas(L) by gkalen though I am not very much fond of miui .But I have no choice.
Thanx.
Click to expand...
Click to collapse
I don't know why you are facing strange issues
In lineage os charging time 2:30-3:00 hrs with original charger also i turned usb fast charge off
And in RR battery backup is average but it doesn't drain (disable all wakelocks) this will solve battery drain issue on almost every Rom
And in Tesla I used more than a month and not a single app crashes (only crashes when you change theme and its due to substratum)
If you want to use Marshmallow then use CandySix By Mr.AW it best ever battery backup on any custom Roms and disable wakelocks otherwise you'll find battery drain on any Rom
Sent from my Lenovo A6000 using Tapatalk
I allready told that i work only for Miui , i will not flash a Xiaomi device with any other type of OS , only Miui .. if i need CM or any other kind of rom i can buy any other device , Xiaomi is for Miui not other OS ..
Στάλθηκε από το wt86047 μου χρησιμοποιώντας Tapatalk
ROCKY_ME said:
I have been using nougat for almost 2 months .Tried almost all N based ROM.As I prefer mostly Lineage base and customizable rom.So I tried to stuck with LOS or RR or Tesla(aosp).At the point of smoothness N is better than M.But facing these issues:-
LOS:-charging time is 6hrson original charger(didn't try latest nightly build).
RR(N):-Battery drainage(don't know why )
Tesla(N):-app crashing(CoC,CoR,Boom Beach etc) and setting FC at some display option.
So I just requesting for a update of those M based ROM for regular using.Because M based ROM was much stable at these points.So I just want a single update these ROMs to lineage.As
CM(M):-can't find latest nightly download link
RR(M):-Setting is crashing after some usages and huge battery drain but at the era of M these were not present.
Now I am using miui Hellas(L) by gkalen though I am not very much fond of miui .But I have no choice.
Thanx.
Click to expand...
Click to collapse
you can use mokee 6.0.1... it is being actively build after every 3-4 days... The most important point being it is only released as a release candidate hence no worry about stabilty.. flash N based custom kernal or any other which suits you or if you need to and you are good to go
heres the link:- http://download.mokeedev.com/?device=wt88047
TecnoTailsPlays said:
Basically, marshmallow is out of range
Click to expand...
Click to collapse
You are right
This discussion is useless
Prince153 said:
I don't know why you are facing strange issues
In lineage os charging time 2:30-3:00 hrs with original charger also i turned usb fast charge off
And in RR battery backup is average but it doesn't drain (disable all wakelocks) this will solve battery drain issue on almost every Rom
And in Tesla I used more than a month and not a single app crashes (only crashes when you change theme and its due to substratum)
If you want to use Marshmallow then use CandySix By Mr.AW it best ever battery backup on any custom Roms and disable wakelocks otherwise you'll find battery drain on any Rom
Sent from my Lenovo A6000 using Tapatalk
Click to expand...
Click to collapse
Dont know what is happening this charging time issue in lineage .But other ROM is giving no issue .
But about app crashing in Tesla,did u try Clash of clans or Clash of royale in Tesla.It is crashing often and I don't use any theme via substratum (waiting for LATER).
Can u tell me plz if candy six use CMTE or layer?
abhianand123 said:
you can use mokee 6.0.1... it is being actively build after every 3-4 days... The most important point being it is only released as a release candidate hence no worry about stabilty.. flash N based custom kernal or any other which suits you or if you need to and you are good to go
heres the link:- http://download.mokeedev.com/?device=wt88047
Click to expand...
Click to collapse
Is they release 6.0.1 till now?
ROCKY_ME said:
Is they release 6.0.1 till now?
Click to expand...
Click to collapse
yes bro, heres the latest build:- http://rom.mk/s/0a1jxa
abhianand123 said:
yes bro, heres the latest build:- http://rom.mk/s/0a1jxa
Click to expand...
Click to collapse
But it is saying "file can not be found".And I tried to download from official site but download speed is so slow.
Is there any other download link.
abhianand123 said:
yes bro, heres the latest build:- http://rom.mk/s/0a1jxa
Click to expand...
Click to collapse
But it is saying "file can not be found".And I tried to download from official site but download speed is so slow(about 20kbps on LTE)
Is there any other download link.
ROCKY_ME said:
But it is saying "file can not be found".And I tried to download from official site but download speed is so slow(about 20kbps on LTE)
Is there any other download link.
Click to expand...
Click to collapse
https://mega.nz/#!UNA2nAqJ!BPsBKu6oJtyTscPGOrHGjhmj15452CggwKKyNux3XHA
Hi, i'm starting this thread to figure out why some moto g4 and g4 plus randomly reboots and when it happes the battery percentaje changes.
For example it is on 95% and it reboots, it changes to 65%
It often happens when a notification cames and after the vibration it reboots.
Do it happens to you??
How can we fix it?
You should mention what device, rom+version, gapps+version, baseband, kernel etc. you are using. Otherwise you cannot figure out where's the problem if everyone has different setups.
It happens only in stock (marshmallow and nougat)
Xt1621 unlocked bootloader
And if I relock the bootloader it still happens
I didnt find a 100% stable ROM to be there so I don't have that bug
ivan290 said:
It happens only in stock (marshmallow and nougat)
Xt1621 unlocked bootloader
And if I relock the bootloader it still happens
I didnt find a 100% stable ROM to be there so I don't have that bug
Click to expand...
Click to collapse
If I understand correctly(if I don't get it, please explain): the problem is only on stock roms? So why not using a custom rom?
That's Right, I don't use Roms because there isn't any stable ROM, or at least I don't know. Would you recommend me a stable ROM?
ivan290 said:
That's Right, I don't use Roms because there isn't any stable ROM, or at least I don't know. Would you recommend me a stable ROM?
Click to expand...
Click to collapse
This one http://forum.xda-developers.com/moto-g4-plus/development/xt16xx-cyanogenmod-14-1-alpha-t3492274 latest build or before the 0502 ist running without any reboot/freeze. RR is also a good choice!
BTT: as your problem is on stock roms only or you have not tested any custom rom it's hard to help you. You can try another kernel, that's all. Bug fixing a stock rom isn't possible, as the source isn't available,you understand?
So try another rom and see if you're facing same problem.
Maybe I am not clear.
Yes I tried Roms that's why I know that the bug is only in stock Roms.
Thank you!
Hello everyone, i am new to the scene of the Mi A1, i bought the phone about 1 month ago and have been observing the forums, but i would like to ask some questions the community as i have not yet managed to find clear answers to the forums if someone can help me
1. If i root the phone is there a way to revert back to complete stock and get OTA's again?
2. In custom roms, can i get the stock camera working 100%?
3. Is there any custom rom that you recommend in terms of stability and battery life?
4. Are there any drawbacks to the custom rom scene?
5. Do you recommend the stock rom with a custom kernel or a custom rom altogether?
Thank you in advance for your answers, i hope that this thread might be useful to gather some questions altogether for anyone that might have wondered the same stuff as me
Hello,
1. There is a way to update OTA with magisk, but you will need you use magisk just as systemless, without touching system stuff. Alternative you can have root and just unroot everytime you want to update the ROM or you can manually flash the update... You can try this guide... https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
2. Stock camera works in custom ROMs, someone did a port somewhere in this forums... https://forum.xda-developers.com/mi-a1/themes/oreo-mia1-stock-rom-camera-app-custom-t3758543
3 and 4. Most of the custom ROMs are based on the same sources, LineageOS was one of the first "stable" ROMs so most of the ROMs are based on it, inheriting all of its bugs (haven't found a critical bug). I've tested a few ROMs and the mosts I liked in terms of battery life and stability are... LineageOS and Pixel Experience, you will need to test them out for yourself.
5. If you want to experience a more "stable" feeling stick to Xiaomi development, the latest stable version is 8.0 (with rumors of 8.1 coming soon). If you want latest Android updates and features go for a 8.1 custom ROM.
In my experience you will need to try all this things on your own, until you find a place where you feel comfortable with your phone. Just read guides on how to recover your phone from a bootloop and you are good to go!
I will answer only question number 4 because the guy above me said everything, by the way I prefer RR.
The drawbacks I found on custom roms are 2 for me...
1) Poor signal reception compared to stock
2) Sound quality is much better in stock compared to custom... (my opinion)
I am itching to root the device but to be honest the only thing i want is android 8.1 and a better battery, other than that i am pretty much satisfied with what i have. (and this is coming from someone that changed rom every other week on previous phones) Thank you for your replies, they were informative and greatly appreciated! I just hope Xiaomi updates the phone soon because it feels kinda outdated for an android one device
Stock Rom
Rooted with magisk of course
Module magisk Pixel 2 Experience (great loock) on many features
Sound awesome flash with twrp version standard DolbyAtmos_for_Oreo_20180219.zip
GoogleCamera-Pixel3Mod-Arnova8G2-V1.apk
For update Rom flash with twrp or fastboot mode
:good:
laugeek57 said:
Stock Rom
Rooted with magisk of course
Module magisk Pixel 2 Experience (great loock) on many features
Sound awesome flash with twrp version standard DolbyAtmos_for_Oreo_20180219.zip
GoogleCamera-Pixel3Mod-Arnova8G2-V1.apk
For update Rom flash with twrp or fastboot mode
:good:
Click to expand...
Click to collapse
TX! I do the same last night. Same recipe, but dolby atmos is not working
How is your signal reception vs custom roms?
Taruxoph said:
TX! I do the same last night. Same recipe, but dolby atmos is not working
How is your signal reception vs custom roms?
Click to expand...
Click to collapse
How is the dolby Atmos not working? Have you installed the standard version? I have a good signal 4G and wifi no worries ...
laugeek57 said:
How is the dolby Atmos not working? Have you installed the standard version? I have a good signal 4G and wifi no worries ...
Click to expand...
Click to collapse
Yes, standard vers. After flashing this my phone enter in bootloop. Can you make a guide step by step, pls?
Taruxoph said:
Yes, standard vers. After flashing this my phone enter in bootloop. Can you make a guide step by step, pls?
Click to expand...
Click to collapse
I just flashed DA with twrp nothing else ...
May be a problem with another mod in magisk?
Power button after bootloop for normaly reboot?
laugeek57 said:
I just flashed DA with twrp nothing else ...
May be a problem with another mod in magisk?
Power button after bootloop for normaly reboot?
Click to expand...
Click to collapse
Already do this.
Only mods I`m using are Pixel Experience 2 and Google Sans Font...
Taruxoph said:
Already do this.
Only mods I`m using are Pixel Experience 2 and Google Sans Font...
Click to expand...
Click to collapse
Stange this try remove all mods for test just DA :good:
laugeek57 said:
Stange this try remove all mods for test just DA :good:
Click to expand...
Click to collapse
Ok, I will do this.
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Prince parth said:
My screen is entirely broken.. so i replace display at market and then almost all custom rom boot very well but after screen lock touch are note working.. we have to reboot device and first time touch working but after screen lock it's not responsive..
Resurrection Remix treble with moun kernel & stock rom working fine..
Any other rom are not working after screen lock.
Please any one help for this problem??
Click to expand...
Click to collapse
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash moun kernel in different ROMs to check whether it works or not?
ImSSin said:
I have this exact same problem. I tried with LiquidRemix and didn't check any other ROMs. Thought it was some kind of hardware problem but after reading your comment i guess it wasn't, as you said its working in RR. Thanks for finding that out. Now i am going to try each and every ROM available to check which one works and which one don't. I also think this must be a kernel problem as there are no hardware issues. Can you flash mourn kernel in different ROMs to check whether it works or not?
Click to expand...
Click to collapse
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine??
Prince parth said:
Yes I checked lineage os, all android pie based ROMs but it didn't work.. currently I'm using Miui10 port and it's working fine
Click to expand...
Click to collapse
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
ImSSin said:
Cosmicdan's Twrp is not working for me. Only mohancm's twrp 3.2.1-2 is working but after locking and relocking the screen in TWRP.
Just flashed RR non treble and the touch is not working after the screen lock
How did you flash RR treble if the cosmicdan's twrp is not working. Was your device already partitioned for treble or is there any workaround?
Click to expand...
Click to collapse
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Prince parth said:
Yes Cosmicdan's Twrp not working but if you install stock ROM and then install Cosmicdan's Twrp then it will work for sure..
Click to expand...
Click to collapse
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Don't need to flash stock ROM I'm on Resurrection Remix treble ROM and for flashing I followed steps stated in forum.. it's work for me no bootloops.
First fastboot flash userdata userdata.img and then boot into Twrp and flash ROM zip that's all.
ImSSin said:
Hmm i'll try that in a bit (making backups 1st). Can you please guide me how you got MIUI 10 working as I am not able to do so. Should i flash stock nougat ROM 1st and then flash MIUI 10? I tried following the steps stated in the forum but i am always getting bootloops.
Sorry for bugging you with my nooby questions :silly:
Click to expand...
Click to collapse
Userdata.img is not necessary, just install the rom and format data(must) then reboot
Thnx for the help guys but after spending hours flashing different ROMs, TWRPs and kernels, I finally found the solution for the touch screen bug.
eXtreme kernel is the only kernel that was able to fix the screen completely. Its working in all of the custom ROMs (tried on LOS15.1 & 16, RR, LR Oreo and pie, etc.)
The stock versions of francokernel, void kernel are able to fix the touch screen but it breaks WiFi so they are not a complete fix.
And btw stock versions of Franco,extreme,void kernels work on the stock ROM.
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
yasars said:
my touch doesnt work on pin screen and in twrp **help** after flash from stock oreo to this rom exl. format data /system and cache..
must i calibrate this or?? when i pres 1 touch meen 9 homebuttons too
is my touch broken or its a bug??
//after flash oreo 8.1 with mi flash ... touch doesnt work
Click to expand...
Click to collapse
have you tried flashing the extreme kernel?
extreme kernel v11 not working only V8 working for me.
What about you guys??
only with kernal 4.9 based custom roms, i have touch issues as described in here. and yeah i had screen replacement too.
now i can't flash any new pie roms as they all are based on 4.9 kernals and i can't find the old pie roms based on 3.18(link dead)..right now on los15.1
:crying::crying::crying::crying::crying::crying::crying:
Same problem here
ImSSin said:
have you tried flashing the extreme kernel?
Click to expand...
Click to collapse
ImSSin
Were you able to solve this problem? Can you put the link to download the kernel?