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
Related
As the title says, I have a Goodix fingerprint sensor, and I've tried all of the methods I could find but none of them works, at least perfectly. In some cases where I applied the patch and used a custom kernel, it kinda works, but very inconsistently.
Further explanation: It only detects my finger about 20% of the time I touch it during the fingerprint setup. Even when it does detect it, sometimes it says "Couldn't process fingerprint. Please try again." After successfully setting up a fingerprint, the phone soft reboots, and then later when I try to unlock it using fingerprint, it doesn't work. Adding more fingerprints does not help in anyway, neither is deleting them.
EDIT: Only with custom ROMs, with MIUI it works fine. Sorry for the misunderstandings.
are you sure, you have goodix version?
ASDFking said:
As the title says, I have a Goodix fingerprint sensor, and I've tried all of the methods I could find but none of them works, at least perfectly. In some cases where I applied the patch and used a custom kernel, it kinda works, but very inconsistently.
Further explanation: It only detects my finger about 20% of the time I touch it during the fingerprint setup. Even when it does detect it, sometimes it says "Couldn't process fingerprint. Please try again." After successfully setting up a fingerprint, the phone soft reboots, and then later when I try to unlock it using fingerprint, it doesn't work. Adding more fingerprints does not help in anyway, neither is deleting them.
Click to expand...
Click to collapse
test on aida64 and we will see what your fingerprint :silly:
pumpkins12 said:
are you sure, you have goodix version?
Click to expand...
Click to collapse
harizinside said:
test on aida64 and we will see what your fingerprint :silly:
Click to expand...
Click to collapse
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
ASDFking said:
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
Click to expand...
Click to collapse
Thats my.. it shown a goodix
Try an librarry pacth and custom kernel.
It's work.
Ps: Sidik jari means Fingerprint
Sent from my Redmi Note 3 using XDA Labs
harizinside said:
Thats my.. it shown a goodix
Try an librarry pacth and custom kernel.
It's work.
Ps: Sidik jari means Fingerprint
Sent from my Redmi Note 3 using XDA Labs
Click to expand...
Click to collapse
Can I have the link to the library patch and the custom kernel you're using?
And also, what ROM is that?
ASDFking said:
Can I have the link to the library patch and the custom kernel you're using?
And also, what ROM is that?
Click to expand...
Click to collapse
of course
ROM= cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kenzo.zip
KERNEL=Radon Kernel V.3.4
PACTH=Goodix_FP_8
Also
Super Su
Xposed
Mising Blob front camera
and etc.
ASDFking said:
AIDA64 is known to report FPC even though devices have a goodix FP. Anyways, mine shows
Manufacturer: FPC/Goodix
Model: FPC102x / FP
And I have a "goodix" folder in root/data with some folders and files inside, there's also an fpc folder alongside the "goodix" one but there is nothing inside.
Also, running the command "getprop | grep goodix" in shell gave me a goodix result.
All the above should be enough to say that I DO have a goodix sensor. Right?
Click to expand...
Click to collapse
not yet... i think your sensor is FPC
have you try lineage os FPC version by minz1?
pumpkins12 said:
not yet... i think your sensor is FPC
have you try lineage os FPC version by minz1?
Click to expand...
Click to collapse
Yeap, tried it, doesn't work. And if my sensor was FPC, it would've worked fine on all other ROMs right? But it didn't apparently.
harizinside said:
of course
ROM= cm-13.0-20160820-SNAPSHOT-ZNH5YAO0J4-kenzo.zip
KERNEL=Radon Kernel V.3.4
PACTH=Goodix_FP_8
Also
Super Su
Xposed
Mising Blob front camera
and etc.
Click to expand...
Click to collapse
Thanks, I'll try it and report back. BTW, the order or flashing is firmware > ROM zip > Radon Kernel > Goodix patch right?
ASDFking said:
Thanks, I'll try it and report back. BTW, the order or flashing is firmware > ROM zip > Radon Kernel > Goodix patch right?
Click to expand...
Click to collapse
That's right, and don't forget for open gapps haha..
Ohh thanks button please ??
Sent from my Redmi Note 3 using XDA Labs
Nope, doesn't work.
Dude, I was in the same situation as you, and also thought that I have goodix, tried every patch, kernels, everything but it just didnt work. I was using cm13 by santhosh which works with goodix rom (but also fpc) and my fingerprint was working. So when I tried to install official cm13, I immediately installed goodix patch and my fp just didnt work. After that, I tried installing rr 5.8.0, also with goodix fix but it didnt work. And then, I wiped everything, did factory reset in twrp, installed cm13 firmware, rr 5.7.4, open gapps and rebooted the system. When fp settings came, I thought lets give it a try and added fingerprint and to my surprise, it worked. It turned out that I have fpc fingerprint. After that, I flashed radon 3.4, selected the fpc fp and worked.
So, the moral of this story is, you might have fpc fingerprint although you have goodix files in system. Try this steps that I described, or just skip everything, do factory reset and wipe in twrp, flash firmware, rom and gapps and reboot to system and set up the rom and see if it works.
{s3rious} said:
Dude, I was in the same situation as you, and also thought that I have goodix, tried every patch, kernels, everything but it just didnt work. I was using cm13 by santhosh which works with goodix rom (but also fpc) and my fingerprint was working. So when I tried to install official cm13, I immediately installed goodix patch and my fp just didnt work. After that, I tried installing rr 5.8.0, also with goodix fix but it didnt work. And then, I wiped everything, did factory reset in twrp, installed cm13 firmware, rr 5.7.4, open gapps and rebooted the system. When fp settings came, I thought lets give it a try and added fingerprint and to my surprise, it worked. It turned out that I have fpc fingerprint. After that, I flashed radon 3.4, selected the fpc fp and worked.
So, the moral of this story is, you might have fpc fingerprint although you have goodix files in system. Try this steps that I described, or just skip everything, do factory reset and wipe in twrp, flash firmware, rom and gapps and reboot to system and set up the rom and see if it works.
Click to expand...
Click to collapse
When you say it works, you mean it really works flawlessly like it did on MIUI, and it unlocks the lockscreen without the screen on?
Also, may I know the version of RR 5.7.4 that you flashed? And the CM13 firmware I suppose is the one from the official thread right?
Another thing, if you had fpc, then shouldn't the fingerprint have already worked when you first tried installing a custom ROM without any patches or kernels?
It works just like on miui, except when the phone is in deep sleep it takes him about 2 secs to unlock with fp, but if you press power button first and then put fp, it will unlock immediately.
I will provide you files in 5 mins, when I come to pc.
Another thing, if you had fpc, then shouldn't the fingerprint have already worked when you first tried installing a custom ROM without any patches or kernels?
Click to expand...
Click to collapse
I am not sure. After santhosh cm13, I tried flashing official cm13 by strix but I am not sure wether I tried to set up the rom without any patches and fixed and kernels or with them. I think that I didnt, because I thought that I have goodix fp.
Anyway, here is the link to rr 5.7.4-20161119: https://www.androidfilehost.com/?fid=385035244224399916
And here is link to firmware that I used and kernel: https://drive.google.com/open?id=0B0PETL84EtNFUFEwZUdvUGFScnM
Try that, and post results here and any further questions.
Goodluck
Thanks, will try and report back here.
BTW, is that the official ROM or an unofficial one?
Reporting back, NOPE, it doesn't work, sadly.
I am not sure, I found the link in official thread.
I'm sorry that it doesnt work, I really had my hopes up high.
Try again, or try 1113 build, in the official thread in op link.
And try without installing gapps, after you flash rom, reboot to system and set it up. If that doesnt work, try again flashing rom, without gapps and wipe dalvik and cache before first boot
I have my fingers crossed man
Okay, will give another few tried when I have the time. BTW, have you tried Lineage OS?
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.
Hey guys,
Newbie here. I am very excited about my new yet to be received phone - X829 using EUI 5.8.016S (Stable).
I care about call quality, camera quality, sound quality using the CDLA technology headphones (in this order).
I don't consider myself a heavy user - I talk maybe 30 mins per day maximum, light web browsing, no gaming...
Should I stick to the stock rom supplied EUI 5.8.016S or is it worth upgrading to something else? Like, will a custom ROM yield better call quality, camera quality and sound quality than the stock rom?
Thanks!
Andrei
Hi, i am also a X829 user and i would suggest you to try recently released EUI 6.0.030s, which has great battery life and network receiving, of course quite stable.Camera quality is also good.
This one is the same rom modified by CrisBallGreece that includes system adblocker by default and preinstalled magisk manager, removed unnecessary leeco apps and chinese garbage apps.
Here is the link:https://drive.google.com/file/d/17dVqqd_kRZol6ORhvs_Ubri7xNldRLvw/view
Google apps : https://drive.google.com/file/d/1bcmKY1yaoVAnLViL0aSabAdpjK6jpn9x/view
Hi,
Thanks for the reply. How do I get the 'cleaned-up' version installed? Not familiar with either super su or magisk. What is the easiest way to go about doing this? The threads I found make reference to super su but can't download it from the official website. Sorry if this was already addressed in a different thread...
Thanks a lot!
Follow this link :
https://forum.xda-developers.com/le-max-2/how-to/protocol-backup-stock-rom-flash-stock-t3517151
First of all, you should unlock your bootloader and flash twrp (a custom recovery mode, allows you flash rom).
Download rom and gapps then put them to your device, backup your data.Reboot to recovery mode.Press wipe - wipe data, go back and press install - find the rom you copied and flash it.Once the phone booted, go back to recovery and flash gapps in the same way then reboot.That's it.
This is the only way to flash any type of rom.
Btw, magisk is a root manager like the supersu, gives you root access of the system.
Hi,
Thanks for the very informative post. I got my phone yesterday and started to play with it As expected, I had some hard time installing the EUI 6 CBG version. I think it's because I installed a very recent (if not the most recent) version of TWRP...From memory, the one I installed is 3.2.2...Anyhow, EUI seemed to install fine and I got the success message displayed in TWRP along with the note 'phone will reboot in 5 seconds' or something like that - which never happened.
I then installed Lineage OS 15 Oreo because I didn't know how to downgrade TWRP.
So do you think that the problem I had was because of the TWRP version I used? how does one downgrade that?
Also, I installed the Gapps (https://forum.xda-developers.com/le...x-lineageos-15-1-oreo-leeco-le-max-2-t3771577) but Google services gives an error message...'Google stopped working'. Is there a workaround for that?
Thanks!
Andrei
Hi mate,
Right after that " phone will reboot ..." note, you should have rebooted the device by pressing and holding the power button for 8-9 secs and it would be fine.
No, latest twrp version works fine and is compatible with this firmware.
Hmm, you can try to delete the app data of google play services.Have you flashed the los 15 with full wipe ?
Btw los 15 is not mature enough.It still has some battery consumption problems and the battery life lasts not as long as EUI's. + I don't know if it has CDLA sound mod but it doesn't contain dolby digital sound.
Hi,
I believe I did a full wipe (dalvik, cache, system, data).
I will try again to flash EUI 6 by CBG tonight.
The workaround for gapps was to flash them at the same time with LOS 15. Previously I flashed LOS 15, rebooted into the system, went back to recovery twrp and then flashed the gapps.
Thanks!
Yeah, flashing the gapps with rom in a row is not a workaround, its a must-to-do.Unfortunately i forgot to mention this to you.Apologises..
Great, thanks a lot! it worked. I'm getting used to it right now. Will play with this ROM for a couple of weeks and then try something else...I was thinking SLIM7...any thoughts on it? have you tried it? any red flags?
Thanks!
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Drollach Gûntar said:
I am also thinking to move that rom, but later.Well its the final version so no bugs.But i don't know if it supports cdla sound mod, do you know ?
Click to expand...
Click to collapse
Not sure if it supports CDLA...I tried this rom briefly the other day and I had a hard time with the camera...battery seemed to deplete quite fast, but I'm sure it can improved with different settings, greenify, etc...try it and let me know if you like it.
Which other roms have you tried?
Thanks!
Most non-eui roms will have slightly worse battery life making greenify an absolute must.
But if you want a non-eui rom (like me, I just hate eui) I recommend lineage 15.1 or du12 by infrag(my current rom).
Hi man, after a long time, I had a change to try different rom, named mokee 7.1.2 (nougat).Well, it's not bad, performance is excellent, not a single lag at all. Also the battery backup is good, not perfect as EUI but acceptable.
Pros of this rom are, it's being updated in a nightly period and Android security patch is dated as august 5 2018 !
You may check it out if you are interested..
Regards.
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Milanche78 said:
I am also on DU12 thinking to try 1 of Android P roms, is it time or to wait ?
Click to expand...
Click to collapse
Try Aex Treble Pie, you will be satisfied.
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
Hi to everyone here... Finally a MoKee ROM is relased for Xiaomi Mi 9 SE (grus) devices!
Developer: subdragonzj
This thread will be unofficial for testing of a AOSP-MoKee ROM builded from the source...
(and ROM based on MoKee with some mods builded by myself)
Stay tuned
I have to say that I was pleasantly surprised by this ROM. It doesn't have the existential issues of PE, so it has all those little useful features out of the box (instant face unlock, double tap to sleep on the lockscreen, etc.). It's not XenonHD based, so no freezing incoming calls. Performance is good (closer to xiaomi.eu). Fingerprint scanner is reasonably fast (I say reasonably because xiaomi.eu is always two steps ahead, in this department). And battery life is also optimized to best levels.
I had issues completing Google setup and with wifi, but I have to be honest: I installed the ROM on top of the latest xiaomi.eu (without sound issues, by the way). Now I have 10.3.4 eea vendor. Let's see how it performs on everyday tasks.
PS - Also, I didn't like the ads on MoKee Center, but Adway takes care of that, of course. I have several paid apps from Play Store, so if the ROM is really good, I have no problems with donation for some extra features.
Can you tell us which steps you made to install mokee properly?
Cheers
Gesendet von meinem MI 9 SE mit Tapatalk
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
elpaablo said:
Ultrawide camera is having same problems that XenonHD had (https://forum.xda-developers.com/mi...xenonhd-9-0-experimental-15-08-t3957888/page5). Can you fix this? Probably Okita kernel will fix it, but I would like to keep this kernel for now, seems very optimized for battery.
Click to expand...
Click to collapse
Ultra-wide camera is broken due to missing some nodes at the kernel dtsi on Xiaomi side (their kernel source is too much broken stuff, even for MIUI itself, which is funny).
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.
And because MoKee dev uses Xiaomi kernel source with little modification, so it's pretty much expected.[/QUOTE]
does it support camera 2 API full
I'm using this ROM for now because it's more optimized than PE. Apart from color profiles that don't stick in any AOSP ROM and a dark theme with white notifications, everything else (except camera, as posted above) is working fine. Fingerprint scanner is reliable (although still a little slow), face unlock is instant and the only issue that needs to be solved asap is ultra wide lens not working. A custom kernel can deal with that, but the stock kernel performs better with this ROM. So, I think I'll wait for a fix or other ROM development.
Anyone getting this on any of your AOSP ROMs?
Been using for 3 days now, and by far it gives the ideal battery performance. Tried crDroid and although there were some improvements, couldn't last a day with barely 20% and high idle drain.
Will be staying with this ROM as everything that I expect from this device is provided for. Personally, no battery means no phone for me, so that's my baseline. Thanks to the other developers for their hard work and free time!
elpaablo said:
Anyone getting this on any of your AOSP ROMs?
Click to expand...
Click to collapse
For now, custom AOSP ROM have 177k-184k antutu score, and it's normal.
you can't expect it to be as close as miui (which can go between 185k-195k).
besides, antutu doesn't represent the true performance since anyone can hack it just like huawei before.
btw, this is from some unreleased custom rom that I use right now, no kernel mod, no nothing. typical custom aosp's score
Yes, but generally it gives you the right idea. The ROM is very fluid. I've installed all my stuff and it remains fluid. In fact, I think the latest nightly update has improved user experience.
Then comes maintenance and that's what worries me the most. We see ROMs (XenonHD and PE) that freeze on incoming calls. This is not just a little bug, it's a massive bug. It basically disables your phone. And it's not been solved yet? crDroid developer seems to think that SIM management is not important in a dual SIM phone. Instead, he tries to make fingerprint scanner work 0.1 seconds faster. Yes, camera is not fully working on MoKee and I really hope that this issue is solved, but at least I can receive calls and enable my data SIM card only when I use it, which saves a lot of battery.
---------- Post added at 05:57 AM ---------- Previous post was at 05:36 AM ----------
I installed latest xiaomi.eu version last week and it's way ahead in every aspect, except 2: MIUI (sucks) and SIM management. AOSP ROMs (except crDroid) handle SIM management in a much better (easier) way.
elpaablo said:
Install Vendor 10.3.3 Global or 10.3.4 EEA via fastboot
Reboot to recovery and install ROM
Do a factory reset (or format Data)
Reboot to system and do initial setup
Reboot to recovery and install Pico GAPPS + faceunlock.zip
Reboot to recovery and install Magisk
Reboot to system and finish setup.
This works for me.
Click to expand...
Click to collapse
Sorry for picking this up again, i´d like to give mokee a try.
which faceunlock.zip did you use?
https://forum.xda-developers.com/android/software-hacking/mod-fix-gapps-unlock-t3863509 The one from this thread?
Thank you, Cheers.
Sooo now i´m stuck on fastboot.
Tried flashing vbmeta using fastboot with "fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img", but it just says "fastboot.exe: unknown option -- disable-verity"
Any ideas?
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
It's the exact phrase I copy/paste.
Maybe you added a space somewhere?
If you're using power shell type cmd first.
Face unlock: https://androidfilehost.com/?fid=11410963190603910002
i used copy/paste too.. i´ve attached a screenshot.
That´s really annyoing atm..
Type cmd or just use cmd instead of PowerShell.
Yes you should always use cmd in administrator mode in the same folder than vbmeta.img
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Humpfrey said:
well... can u tell me what i´m doing wrong here again?
Sorry for the circumstances guys..
Cheers
Click to expand...
Click to collapse
Can you tell us where is located fastboot and vbmeta.img on your pc?
For instance, i have all my files in c:\Android
So I launch the cmd directly in that folder.
Started by DL https://androidfilehost.com/?fid=962187416754459552
Copied on C drive and renamed into Android
Then I copy my files on it, and right click/launch as admin on "cmd-here".