Hello LeMax aficionados!
I have a Le Max 2 (4gb, 64gb), bought originally as an X829. I immediately flashed the latest lineage OS and have been updating it weekly (now device info shows X820). Everything worked well for more than a month; fingerprint sensor was working well too.
At the time of the issue I was on the 16th Dec release of LOS and had the superuser addon installed. I decided to move to the latest magisk (v15) and get the systemless Xposed (sdk25) so I could try out the Leeco Infrared Fix and the InstantFaceUnlock module. This is how I went about it.
1 Flashed the superuser addon remover. Rebooted.
2 Installed the XposedInstaller (latest version from the source)
3 Flashed magisk v15.0. Rebooted.
4 Downloaded the Xposed sdk 25 from the downloads section of magisk. Rebooted.
5 Opened XposedInstalled and saw Xposed was installed and everything was green.
6 Downloaded the Leeco Infrared Fix and the InstantFaceUnlock thingy. Rebooted for it to take effect.
Here’s where the problem started. I got stuck on the boot animation screen for a long time. Unsure about what to do I left it like that for 3 hours or more (plugged in). When I finally checked it, the phone was extremely hot. I pressed the power button for 10s to force restart and had the same issue. I used the vol UP+power button combo to boot into recovery. Then:
A I flashed the Magisk uninstaller.
B Dirty flashed the Dec 23 LOS. Rebooted. Thankfully it booted properly.
C Uninstalled the XposedInstaller. Rebooted.
D Flashed the superuser addon.
E Everything seems fine. Except that the fingerprint sensor doesn’t work. Even when I remove all fingerprints and try to register it anew, the calibration process doesn’t proceed beyond the first fingerprint. (1/10).
F I flashed the chinese 26s Modem. Same problem persists.
G I did a basic wipe from TWRP. Restored a nandroid backup from a week back. Everything is fine except that the fingerprint sensor doesn’t work.
Did the overheating mess up some key component of the fingerprint sensor? Any suggestions?
Have a nice day guys!
Bump!
Any ideas guys?
I was reading before that overheating mess up with finger print.
@shanty23 any news thus far? I have the same model but my fingerprint only worked for a few seconds after I purchased the phone. I immediately flashed a custom ROM though.
pinnekeshaar said:
@shanty23 any news thus far? I have the same model but my fingerprint only worked for a few seconds after I purchased the phone. I immediately flashed a custom ROM though.
Click to expand...
Click to collapse
Exactly the same happened to me, I immediately installed a custom Oreo ROM and the fingerprint sensor died. I was resigned to live without it but after installing Xposed framework (I'm using AICP ROM) the fingerprint got back to life...
Enviado desde mi LEX820 mediante Tapatalk
cruizgaray said:
Exactly the same happened to me, I immediately installed a custom Oreo ROM and the fingerprint sensor died. I was resigned to live without it but after installing Xposed framework (I'm using AICP ROM) the fingerprint got back to life...
Enviado desde mi LEX820 mediante Tapatalk
Click to expand...
Click to collapse
Hi @cruizgaray ,
Can you specify which AICP ROM did you install and what Xposed version? Is the FP still working? before the fix did you have any signal from the FP reader? I mean like the FP gestures on camera app working.
Flash this -> https://androidfilehost.com/?fid=818070582850487752
Reflash the ROM and see if it help.
Beackman said:
Flash this -> https://androidfilehost.com/?fid=818070582850487752
Reflash the ROM and see if it help.
Click to expand...
Click to collapse
Done. No change. I'm starting to think it's a hardware failure.
Thanks anyway
surfersea said:
Done. No change. I'm starting to think it's a hardware failure.
Thanks anyway
Click to expand...
Click to collapse
Give time to the sensor, maybe they back to life.
Or, just a hardware damage like you said.
I have posted a solution for this in the treads all eui rom
Mine also dead after 3 days of purchase. But one day it accidentally started responding. Now its working fine. According to me wait for few days, it may work.
surfersea said:
Hi @cruizgaray ,
Can you specify which AICP ROM did you install and what Xposed version? Is the FP still working? before the fix did you have any signal from the FP reader? I mean like the FP gestures on camera app working.
Click to expand...
Click to collapse
Before it got fixed it was completely dead; it just worked a couple of minutes after I received it.
I installed Infrag's AICP and the last version of Xposed (not systemless) for Oreo. I' keep using Infrag's AICP and the FP is working perfectly.
Best regards
Enviado desde mi LEX820 mediante Tapatalk
Related
Hi everybody,
i'm having problems with this smartphone from the day I bought It.
I've received my phone, had a customized ROM by vendor, FP wasn't working (was like disabled). So i installed 7.5 stable (by xiaomi.eu), everything worked fine for one/two weeks, after the day that i wanted to play a game that can't run in rooted devices. First of all i checked on internet something to do, if i could run it, but nothing. So i started searching something in Link2SD and SuperSU settings.
First, i have entered to Link2SD, clicked the app, then "Convert to user app" (You'll sure ask: reasons? Well, don't know). Don't know what I was expecting but happened nothing. Then i said "let me check if there's an option in TWRP 3.0", i went to recovery mode, searched for something and I didn't find anything, so pressed Reboot > System. The smartphone stuck at MI logo and had to flash the ROM again (The same one).
After the flashing operation, there was a surprise. The battery went to -2% and kept stuck at it. I've tried EVERYTHING, installed all type of ROMS (Stable, dev, china, global, custom, etc etc) battery stuck at -2%.
Read online that was a kernel problem, so let's try to find a custom kernel or maybe the ORIGINAL kernel of Redmi Note 3 pro (Kenzo). Everybody said that Radon Kernel was what I was looking for. Installed it.
Yes! It resolved the -2% battery issue, i was so happy. At one cost: the fingerpirnt sensor. After normal reboot of the smartphone the FP sensor turns off and i'm unable to use it. With the first boot after flashing ROM and Radon Kernel, FP works perfectly, but if I reboot the smartphone then it stops run.
Tried with most of kernels for MIUI and Radon was the only one to solve the -2% battery issue.
Follow i just leave thing that i already did or i see everytime:
Discharged battery to 0%, then charged it at 100%;
Tried MIUI 7.1, 7.3, 7.5, 6.8.4 (every tipe, stables, dev, china, global etc);
Everytime i install a new ROM (TWRP or Mi Flash tool - via fastboot -) looks like TWRP disappears, i get instead a battery with low-red health and a charger;
-2% battery issue persist even with other ROMs (Flashed Cyanogenmod 13 by RR).
Still looking for the original Kernel of Kenzo, but I don't think if I will find it.
Can someone of you help me with this embarassing problem??
Thank you all.
i have the same problem, people say its an kernel issue. so far there is no fix.
edit: radon kernel fix this bug.
Use Blaze Kernel , it fixes 2% bug and also it gives more battery backup than radon. Also i get random reboots in radon but blaze has been stable for me so far
Here is the link to the kernel
Hit thanks button if you think i helped you
Being Indian said:
Use Blaze Kernel , it fixes 2% bug and also it gives more battery backup than radon. Also i get random reboots in radon but blaze has been stable for me so far
Here is the link to the kernel
Hit thanks button if you think i helped you
Click to expand...
Click to collapse
Everything is solved with the new version of the Blaze Kernel, v3. The v2 gave me the same problem as the Radon Kernel, but looks like the new version of Blaze is running good!
I can reboot my smartphone everytime i want and the FP sensor keep working!
Flash radon kernal or blaze kernal. I used both and none of them had the -2% issue.
@paprika714 what fingerprint sensor do you have? I have FPC and it doesn't work on any custom rom no matter what kernal I use.
A Sad Napkin said:
Flash radon kernal or blaze kernal. I used both and none of them had the -2% issue.
@paprika714 what fingerprint sensor do you have? I have FPC and it doesn't work on any custom rom no matter what kernal I use.
Click to expand...
Click to collapse
Yes, every custom kernel solve also for me the -2% bug, the problem was the FP sensor that stops working after i reboot the smartphone, but looks like with the new version of Blaze is solved.
If you are so gently to say to me how to check my FP model, i'll tell you.
paprika714 said:
Yes, every custom kernel solve also for me the -2% bug, the problem was the FP sensor that stops working after i reboot the smartphone, but looks like with the new version of Blaze is solved.
If you are so gently to say to me how to check my FP model, i'll tell you.
Click to expand...
Click to collapse
Aida64 you can use but its a bit hit and miss
You need to check what folder you have in the data folder, will either be FPC or goodix.
A Sad Napkin said:
Aida64 you can use but its a bit hit and miss
You need to check what folder you have in the data folder, will either be FPC or goodix.
Click to expand...
Click to collapse
FPC - FPC102x.
What' s the difference between Goodix? What is better?
paprika714 said:
FPC - FPC102x.
What' s the difference between Goodix? What is better?
Click to expand...
Click to collapse
strange how your FP works but mine doesn't and I have the same as yours lol
Goodix isn't supported yet but FPC should be.
What was your flashing procedure mate?
A Sad Napkin said:
strange how your FP works but mine doesn't and I have the same as yours lol
Goodix isn't supported yet but FPC should be.
What was your flashing procedure mate?
Click to expand...
Click to collapse
I have installed TWRP 3.0, everything is copied in my micro SD card (ROM 7.5 stable and kernel).
These are my steps:
- Wipe > Format Data;
- Wipe> Advanced Wipe > everything except external SD;
- Install > Select ROM package;
- Install > Select kernel.zip package > after installation i click wipe cache/dalvik;
- Reboot
This is my usually full wipe installation via TWRP
The gestures randomly stop working after the marshmallow update. So, I clean flashed 3.1.3 with stock recovery after deleting cache and data. Gestures randomly stop after sometime but works again if you reboot. Any way out?
Now, I am rooted with twrp recovery.
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
I think that explains it.
Exodusche said:
No such issues here. I'm no expert but I had issues with notification. So I wiped everything including internet with twrp. Be warned wiping internal is never suggested. But I had a lot of junk left over from ROMs and such. Then I flashed 2.2.2, 2.2.3 and last 3.1.3 finally reboot. Everything is working 100℅ now feels like brand new phone. Again I'm no expert and always back up your important files on your computer and or thumb drive before attempting because you will loose everything.
Click to expand...
Click to collapse
Thanks I will do my research!
pavikum said:
Thanks I will do my research!
Click to expand...
Click to collapse
No problem also meant to say gestures never worked better. . Almost to good every time I clean my screen flashlight or music starts playing lol.
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
vinz_uk80 said:
I also have random gestures not working on my fresh installed OOS 3.1.3.
It never occurred before under 2.1.3 – 2.2.0 – 2.2.1 and 2.2.2, always rooted.
To prevent from rebooting the phone, enabling the proximity wake up (in parameters, display) does the trick.
Once I activate the proximity wake up, the gestures work again.
After that, you can disable the proximity wake up, the gestures keep working. Until it fails again.
I don’t know why this occurs, but at least, it’s an easy work around.
Click to expand...
Click to collapse
Haha, at least I have some company now!. Thanks, that trick works!
maybe we followed the similar steps to arrive at this issue.
I was on Sultan CM rom 13 , when the 3.1.1 update arrived, I unrooted my phone locked the OEM and clean installed 3.1.1 through stock rcovery after clearing data and cache. My phone gesture problem started from here, I updated to 3.1.2 through OTA and that did not solve it, so I clean installed 3.1.2 and later 3.1.3. Rooted it with modified superSU and blu spark twrp recovery. Did you follow the same steps.
I am not wiping the internal storage yet, as suggested by 'Exodusche', as I am doing my research to understand the potential risks. But, I did not really find any helpful article till now.
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
I suggest you to flash the latest version of MIUI latest china dev, then from fastboot flash twrp, then clean flash rom + kernel. It takes about 30 minutes if you know what you're doing.
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
ginohabibi said:
So basically restore then start from scratch? That did cross my mind... I will give it a go. Thanks. I will report back here.
Click to expand...
Click to collapse
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
ufoshop said:
Hi if you find a fix for this problem please share it with me, I tried latest china dev rom, latest global dev rom and latest global stable rom with all versions the boot time goes to 4-5 minutes...
Click to expand...
Click to collapse
Try method in my signature.. it should work for you
khajiit said:
Try method in my signature.. it should work for you
Click to expand...
Click to collapse
Where do i find that method?
https://forum.xda-developers.com/redmi-note-3/how-to/kate-guide-install-lineage-os-locked-t3546154
Alright, im going to try that method and i will report my results here.
Followed all the steps within your guide, but that guide didnt work and has nothing to do with our slowboot issue.
Hardware related then
ginohabibi said:
I have the resurrection 5.8.0 installed (30 Dec build) and my phone takes about 5 minutes to boot. Initially it is stuck in the MI logo for about 4 minutes before the animation starts. I have used several ROMS and kernals and they all seem to do the same thing. I never had this issue with MIUI. Once the phone has booted, the phone is totally fine however I would prefer to identify and fix the problem. Any suggestions? I have already done a complete wipe, and tried various verions of TWRP with no joy. Thanks
Click to expand...
Click to collapse
Didnt you change recently some parts of the phone? Like display/baterry and so...?
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
So you say there is no solution to run the official rom without waiting 4-5 mins on boot, I have the phone from fastcardtech and maybe is a refurbished unit because they have very low prices compared to other resellers...the phone came in sealed box...
Dwnld links plzz..
Hay anybody here ...is there any other kernal for andriold n ROMs...
paladzin said:
i think dat guy replaced display module
same problem here, touchscreen cant initialize on boot
4-5mins to go... all rooms.
to solve/ n - use old Santosh kernel, mm - use neon kernel, lp - elementalx
on this cores phone starts on 20-40s
and about recovery - use twrp+ 3.0.2-2 by mr_root
Click to expand...
Click to collapse
Mine to, it 2 time I had to replace screen. I'll give a test right now and report back.
Im not using the device anymore, but i think i had to replace the screen like 3-4 times, its very fragile, even a drop from small height makes it crack. Also without case its very slippy device, but none of that matters. From the 4 displays i used, which all have been touchscreen + lcd + the frame (as i dont like to glue the display, i pay 10 dollars more and its better) had that exact same problem, which is very long waiting for the device to boot. The custom kernel solved it, but another (probably better quality) display does solve it too.
Hello Axon 7 XDA Users,
as you know, more and more users have a stupid reboot bug. Unfortunately no DEV found the time to take a look into the logs I and other users posted on the forums.
THE BUG
Soft reboots and boot loops at least once a day
- while charging
- while watching videos or surfing
- even then turned off (Ghost booting)
SOFTWARE AND DEVICES
Reports on nearly all custom roms based on LOS
All A2017 / 2017 U / 2017 G models
WORKING SOLUTIONS
A
I seem to have fixed the problem and want to ask you to try my method:
The problem is probably caused by Magisk, all versions from 13.5 till 14.5x beta
After switching to LineageOS integrated root method I am reboot-free since 3 days of intense usage.
Tutorial to uninstall magisk:
- Download magisk-uninstaller and LOS root addon on LOS ROMs (Downloads are attached)
- Reboot into recovery
- Install magisk uninstaller zip file
- Reboot into recovery (maybe not necessary)
- Install LOS root addon
- Wipe dalvik and cache.
- Profit :good: and report back
B
Only use magisk v14 or try 15.2
THX @notese
C
Try disabling Magisk hide
THY @digiNZM
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Pastinakel said:
I don't use magisk and I still have reboots. Reboots occur about once or twice a week.
Click to expand...
Click to collapse
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
I had the reboot issue with the latest lineage os and magisk on b25 universal bootstack.
Currently using Dark ROM with magisk on b32 bootstack for the past week or so and no reboots.
A2017U
SilentEYE said:
Thank you for your feedback.
Maybe you should post what setup you have and which apps you are using with root / xposed access or mods.
Click to expand...
Click to collapse
My setup is pretty plain vanilla, no mods. I have the lineage root installed, but it's disabled most of the time.
If I remove Magisk and go with Lineage root, will I lose Safetynet? I need Android Pay to work.
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
That's weird.
I'm using magisk myelf for a long time and never had reboot issues. :/
Only when using incompatible modules or bad settings.
Maybe that's where the real issue is.
P. S.
I'm using latest stable magisk on latest stable RR for a while no and I get zero reboots.
P650SE said:
I had the problem with random soft reboots for quite a few months. There would be no similarities between when the reboots happened, for example it would occur whilst watching YouTube videos, browsing Google Maps or even just leaving the phone in sleep mode. Someone on XDA suggested switching from Magisk v14.5 Beta to stable Magisk v14.0, and since then I haven't had a problem.
Advising people to ditch Magisk altogether might not be the best advice, as for me just switching back to the stable version worked. Remember there have been beta versions of Magisk v14.0 for months and it was definately affecting v14.3 as well as v14.5.
Click to expand...
Click to collapse
You probably read my advise. My fav rom is AOSP Ex and it was driving me nuts the whole random reboot thing. Your description of the symptoms are exactly like the ones I was having. At the beginning I though it was an issue with substratum but it kept happening even without having substratum installed.
I tried switching roms (Dark Rom, Lineage, and RR) and all had random reboots. The final epiphany I had was that I was using magisk beta 14.5 on all of them. I didn't install any custom kernel or any other thing beside magisk 14.5 and one module (viper). I tried reading at the logs but couldn't trace them back.
I figured to try AOSPex without root as the only common thing between the roms was magisk. After this, the reboots and crashes stopped (I tested this for a week). I started reading in the magisk forums and found people with the same symptoms as ours. I didn't see any major complain with the stable magisk 14.0.
My current setup is ASOP ex with llama kernel and magisk 14.0. I have had this for about two weeks and no random reboots so far. The only problem I have encountered was that I lost root access once and I had to reboot on my own account to regain root (maybe a module incompatibility, I have installed two additional modules since then). Other than that, all is good.
Final tip: I only turn on the magiskhide setting when I need it for a specific app. I have it off by default. I don't want an extra process running all the time if I don't need it or use it regularly (can only be a good thing for battery).
Hope this helps
I got the reboots even with magik v14.
Added @notese his solution to OP
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
hboa said:
I've only got Magisk for a month or so, but reboots began way before that. So I don't Magisk is the culprit.
Click to expand...
Click to collapse
What root method did you use before?
Which rom?
Which root apps?
If you provide us some more, maybe we can hit the sweet spot of the bug.
To all :
Write at the end of your comment your settings
Device
ROM
Kernel
Modem
Root method
Root apps
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
digiNZM said:
Had Reboots with Magisk v14.x in different ROMs (Vertex, AICP, AOSP) and with different Kernels. Since i disabled Magisk-Hide it stopped (past 3 weeks). Maybe a weird coincidence. Just thougt i share this. Maybe someone can try too?
Current: AICP (unofficial), LLAMA non-EAS Kernel, Magisk latest (v14.5), MicroG.
Click to expand...
Click to collapse
I always had magisk hide disabled and had the reboot problems.
I will add your solution to topic
I personally had some reboot and bootloop problems while on AICP and LlamaSweet and I thought it was the rom. However I then went to Dark Rom with LlamaSweet and the reboots happened again. I posted about this and someone mentioned 14.5 might be the problem. I installed 14.0 and for the past week? I haven't had a problem. So for me it seems so far to be 14.5 as well. Also as of right now I have BeastMode kernel running. Has anyone tried 14.6 yet?
I will post screenshot of my superuser and modules pages.
I have the latest beta version of Magisk and I have reboots once or twice a day, but not necessarily all days. I have the stock camera and "Enable AK4490 HIFI DAC" magisk modules.
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
eaponte23 said:
I had reboots on the latest DarkRom, Magisk many times a day for at least a month and a half. Since hurricane Maria cell service was almost impossible to find. I noticed everytime my phone lost coverage it would reboot.
Changed sim to another carrier with great coverage just a few weeks ago and reboots have since gone away. Hmmm
Click to expand...
Click to collapse
Did it hang in the soft reboot loop?
SilentEYE said:
Did it hang in the soft reboot loop?
Click to expand...
Click to collapse
Nope, it would just reboot everytime I drove thru certain areas. For instance, as soon as I passed my towns high school, boom restart.
If I had 3G then all of a sudden it dropped to zero bars, boom restart.
The only way I would not get the reboots was installing DrakenFXs B32 with Magisk. Or turning on airplane mode when I knew I would go thru an area with no service.
Convinced me LOS based rom had problems with handling towers and low signal. I tried them all same reboots.
@eaponte23
your problem seems to be different and is a combination of modems and your provider. I know that there has been similar problems with CM /LOS based ROMs on other devices, depending on the Service provider. These lead to total signal loss or reboots.
The Magisk problem is cauing constant reboots.
Hello.
For some time I have noticed that I have no vibrations anywhere: during the ringing, in any application, in diagnostics too. Unfortunately, I have not noticed when I do not have them (I mean since which ROM). ROM history on my Poco:
1. From the novelty box MIUI global 10 (Christmas 2018)
2. Immediately after unlocking the bootloader for several weeks MIUI POLSKA (weekly) (from Christmas to about first week January 2019)
3. For one week xiaomi.eu 10.1.3.0
4. Until today, MIUI POLSKA (weekly)
where: in the 1st and 2nd roms, the vibrations were working (so the hardware defect is gone), with the 3th I'm not sure (I do not remember) whether the vibrations worked, and in rom 4. I did not pay attention or specifically from some version weekly vibrations have disappeared or for some other reason. So I quickly tried downgrade to weekly 9.1.10 and also in this version there were no vibrations. I have not tried the stable version yet, as I will try to write it. Currently I have: MIUI 9.1.24 (weekly), Magisk v18, Battery Charge Limit [ROOT], Franco Kernel, (in the stock kernel also does not work).
I am asking for help.
Thank you, everyone.
Edit: I've noticed very strange thing. During charging, vibrations are working LOL
Did you solve the problem? Today Me too just vibration with charging conditions... Even after fresh install... So strange no capability to vibrate after flash some apps... if I'm not wrong after flash anx camera.... And yes Franco kernel and 10.2.2 stable here...
indhimaga said:
Did you solve the problem? Today Me too just vibration with charging conditions... Even after fresh install... So strange no capability to vibrate after flash some apps... if I'm not wrong after flash anx camera.... And yes Franco kernel and 10.2.2 stable here...
Click to expand...
Click to collapse
Hi!
I tryied dirty flash- no result.
I tryied wiping /system partition only and then flashing ROM - no result.
Only thing which helped me was to wipe EVERYTHING in TWRP ( I mean all avalible partitions in TWRP) then flashed ROM...
A bit annoying, but only this helped.
Klusio19 said:
Hi!
I tryied dirty flash- no result.
I tryied wiping /system partition only and then flashing ROM - no result.
Only thing which helped me was to wipe EVERYTHING in TWRP ( I mean all avalible partitions in TWRP) then flashed ROM...
A bit annoying, but only this helped.
Click to expand...
Click to collapse
i found its because the power saving from franco kernel... Set another performa nce and its back to narmal
indhimaga said:
i found its because the power saving from franco kernel... Set another performa nce and its back to narmal
Click to expand...
Click to collapse
Hmm. Tryied changing performance and still no vibrations. I unistall franco kernel and flashed stock kernel- still no vibrations. Any help?
Any update on a work around? I lost my vibration too
Vibration is back while plugged in to charger. Vibration not working when unplugged
Edit: Working after changed CPU governor to performance from schedutil