Related
Hello friends,
I recently bought Redmi Note 3 (kenzo) in August 2016. It is made in India.
I have confusion over which fingerprint sensor is on my device. Is it FPC or Goodix?
I am attaching some screenshots, which leads to think that my device may have FPC fingerprint sensor.
Friends, help me to identify FP sensor on my device. Thanks in advance.
I have the Redmi Note 3 (2gb/16gb) from the first flash sale in India ( I think March 10 , 2016 ) and ur touch panel , LCD and camera sensors are identical to mine . I can't for sure tell urs is goodix or fpc but I noticed that u have a different battery id . maybe that -2% bug might be there if u flash an incompatible kernel
NABENDU1 said:
I have the Redmi Note 3 (2gb/16gb) from the first flash sale in India ( I think March 10 , 2016 ) and ur touch panel , LCD and camera sensors are identical to mine . I can't for sure tell urs is goodix or fpc but I noticed that u have a different battery id . maybe that -2% bug might be there if u flash an incompatible kernel
Click to expand...
Click to collapse
I had flashed CM 13 build but I didn't face 2% battery bug yet
But I got FC while opening Security tab and no option to configure fingerprint also
It's confirmed now. I have FPC sensor. Also no 2% battery bug for me and both cameras work fine. :laugh::laugh::laugh: :good::good::good:
bravonova said:
It's confirmed now. I have FPC sensor. Also no 2% battery bug for me and both cameras work fine. :laugh::laugh::laugh: :good::good::good:
Click to expand...
Click to collapse
How did you confirm?
NVDX11 said:
How did you confirm?
Click to expand...
Click to collapse
Because it is working with official CM 13 as well as custom kernels too.......
Currently custom ROMs based on official CM 13 and custom kernels for CM / AOSP not support Goodix FP.
So my device definitely have FPC fingerprint sensor
bravonova said:
Because it is working with official CM 13 as well as custom kernels too.......
Currently custom ROMs based on official CM 13 and custom kernels for CM / AOSP not support Goodix FP.
So my device definitely have FPC fingerprint sensor
Click to expand...
Click to collapse
Ok,so i haven't flashed cm 13 but i previously flashed radon and blaze kernel and my FP was working,so it means i have fpc FP sensor?
Ps-i have goodix and fpc both folder in root/data/
NVDX11 said:
Ok,so i haven't flashed cm 13 but i previously flashed radon and blaze kernel and my FP was working,so it means i have fpc FP sensor?
Ps-i have goodix and fpc both folder in root/data/
Click to expand...
Click to collapse
On which ROM did you flash Radon and Blaze kernels ??
check this folder "/root/sys/class/input" There will be folders like input0...... input1 and like this.... open that folder and open "name" file in that folder wtih text viewer and check.
Also can you able to take selfies with FP scanner ??
bravonova said:
On which ROM did you flash Radon and Blaze kernels ??
check this folder "/root/sys/class/input" There will be folders like input0...... input1 and like this.... open that folder and open "name" file in that folder wtih text viewer and check.
Also can you able to take selfies with FP scanner ??
Click to expand...
Click to collapse
Ok i flashed radon and blaze while i was on miui 8 6.8.18(LP).
Currently i am on miui 8 6.9.9(MM).
I am able to take selfies with FP scanner and those name files are attached in SS
NVDX11 said:
Ok i flashed radon and blaze while i was on miui 8 6.8.18(LP).
Currently i am on miui 8 6.9.9(MM).
I am able to take selfies with FP scanner and those name files are attached in SS
Click to expand...
Click to collapse
check for other input folders too..... and you may find fpc or goodix related info in it.
Also do one thing, go to about phone..... tap 5 times on cpu..... you will get a notification of bug report creation..... complete it.....
Then a file will be created in internal storage/MIUI/bug report.zip, extract it
Open that file, there will be a text file. Open that and check for this value "androidboot.fingerprintsensor" or "androidboot.fpsensor" and check what is after "=" mark.... if it is "fpc" then you have FPC fp scanner.
bravonova said:
check for other input folders too..... and you may find fpc or goodix related info in it.
Also do one thing, go to about phone..... tap 5 times on cpu..... you will get a notification of bug report creation..... complete it.....
Then a file will be created in internal storage/MIUI/bug report.zip, extract it
Open that file, there will be a text file. Open that and check for this value "androidboot.fingerprintsensor" or "androidboot.fpsensor" and check what is after "=" mark.... if it is "fpc" then you have FPC fp scanner.
Click to expand...
Click to collapse
Ok i found input 9 folder and in the name file it is written fpc , attached in SS
And about bug report ,there are like 4-5 text file, searched for androidboot.fingerprint and androidboot.fpsensor ,but there are not a single entry like that
One thing i like to mention i found something like this in bugreportfiles which is attached in SS too.
NVDX11 said:
Ok i found input 9 folder and in the name file it is written fpc , attached in SS
And about bug report ,there are like 4-5 text file, searched for androidboot.fingerprint and androidboot.fpsensor ,but there are not a single entry like that
One thing i like to mention i found something like this in bugreportfiles which is attached in SS too.
Click to expand...
Click to collapse
You have FPC fingerprint scanner
bravonova said:
You have FPC fingerprint scanner
Click to expand...
Click to collapse
Thanx i thought so.
NVDX11 said:
Thanx i thought so.
Click to expand...
Click to collapse
I also have fpc related file in input9 folder. I was on MIUI 8 v6.9.9 MM based. And your phone configuration looks same. I think in India they have sold devices with FPC, tianma panel, and samsung camera modules
bravonova said:
I also have fpc related file in input9 folder. I was on MIUI 8 v6.9.9 MM based. And your phone configuration looks same. I think in India they have sold devices with FPC, tianma panel, and samsung camera modules
Click to expand...
Click to collapse
Yea i saw your pics in OP,the version mentioned for sensors are same and my phone is also made in india.
Thanx for the help , detection of which FP is on phone was a confusing becuz some ppl mentioned aida64 is also giving false positive results.
Needed some strong evidence. :laugh: :good:
NVDX11 said:
Yea i saw your pics in OP,the version mentioned for sensors are same and my phone is also made in india.
Thanx for the help , detection of which FP is on phone was a confusing becuz some ppl mentioned aida64 is also giving false positive results.
Needed some strong evidence. :laugh: :good:
Click to expand...
Click to collapse
Yeah... many reported that.... but with aforementioned steps we can conclude which FP sensor our device may have
bravonova said:
check for other input folders too..... and you may find fpc or goodix related info in it.
Also do one thing, go to about phone..... tap 5 times on cpu..... you will get a notification of bug report creation..... complete it.....
Then a file will be created in internal storage/MIUI/bug report.zip, extract it
Open that file, there will be a text file. Open that and check for this value "androidboot.fingerprintsensor" or "androidboot.fpsensor" and check what is after "=" mark.... if it is "fpc" then you have FPC fp scanner.
Click to expand...
Click to collapse
I've checkd it.. Input9 folder contains Name as "uinput-fpc"
That means I've FPC sensor???
In terminal emulator
Type su
Grant root access
Type cat /proc/cmdline
Find and check androidboot.fpsensor=****
Or just flash any ROM that would guaranteed break goodix for easier checking. XD
Searching for goodix on the root directory on mine yields lots of results so I first thought I have goodix. But after flashing several ROMs and not one breaking my FP, now I know I have FPC.
Hi,
I will release here my updated "boot.img" files for the Xperia XA Ultra Dual Sim.
You must have an unlocked bootloader to flash with Fastboot.
You don't need to be on the same firmware as the boot image that you want to flash.
You have to flash SuperSu again from TWRP just after flashed new boot to avoid bootloop.
All boot images have "ro.secure=0" and "ro.debuggable=1" in default.prop file
and "forcencrypt" of internal memory switched to "encryptable" in fstab.mt6755 file.
The Fastboot command is:
fastboot flash boot NAMEOFIMAGE.img
Click to expand...
Click to collapse
Follow the guide from @Yooooomi to flash new firmware on your Ultra to avoid bugs and brick: https://forum.xda-developers.com/xa-ultra/how-to/flashing-xa-ultra-flashtool-t3551319
Releases:
12/28/2016: From 36.0.B.2.109 kernel sources and Ramdisk from 36.0.B.2.109 firmware.
https://mega.nz/#!cxI3SJaC!o-aqc2gUZufDJefKaxGRxRhekEq32B1bIDB3ROxyd7Y
04/01/2017: From 36.0.B.2.146 kernel sources and Ramdisk from 36.0.B.2.146 firmware.
https://mega.nz/#!VhwRQLqR!rOqEFWeOC3IQKl4aDw7P_v0U2wmZtBPXk_MSDJMEy9k
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
twhhhco said:
hi
Does anyone has tested this ROM?
probably is break my devise, possible if there unbreak?
thanks all.
Click to expand...
Click to collapse
Hi, it's not a Rom just a boot.img for unlocked bootloaders with stock kernel built from Sony open source archive.
36.2.B.2.109 boot should fix the front camera not focusing after root.
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
klengjaua said:
After testing I found out that the boot does have problems
Which are:
1-Screen doesn't turn off completely, it stays at a very dark state which can be noticed in extreme low light conditions and if u turn the screen back on u will notice a a static on the screen and then it functions normally.
2-system brightness level meter doesn't work but third party apps can be used to change that.
Hope that helps and u come with even better boot in the future and thank u in advance.
Click to expand...
Click to collapse
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
rrvuhpg said:
Hi, thank you for the feedback. I don't have any unlocked Ultra (only have a unlocked XA F3112) so I can't test new releases or try to debug anything. I don't make any changes to the kernel source code, only build the kernel and repack it in a stock ramdisk with very small changes for root, nothing more. I hope that an user will be able to fix bugs.
Click to expand...
Click to collapse
These are the fixes you mentioned?
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
rrvuhpg said:
Yes it's the new boot who fix the front camera bug mentioned in my PM, as you can see in the comments it fix this bug but make an other bug You can flash it if your device is a dual sim. If you try it please say us if you have the same new bug.
Click to expand...
Click to collapse
I will do it with f3213
Nrsoto said:
These are the fixes you mentioned?
Click to expand...
Click to collapse
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Nrsoto said:
Sorry, how did you do it, my cel no focusing camera frontal before unlocked boot loader , you device Does the same
Click to expand...
Click to collapse
Here's step by step what I did, I hope it will work for your device too:
1. Go to xperifirm and download the 36.0.A.1.111 firmware (service unit exchange)
2. Create a bundle on the flashtool within the firmware folder
3. Flash it
4. Happy rooting!
There is however something I have to mention about this fw: you'll probably not receive any system updates
IF U ARE A SNAPCHAT USER install Snapchat before messing the system up with xposed
sexxualization said:
For those who are struggling with the front facing camera, I finally solved it without installing any kernel or modify anything from the system. Downgrade to 36.0.A.1.111 (should be the one one with service unit exchange or smth like that). Had installed gapps stock (but I suggest u don't delete the Sony camera app - Instagram and Snapchat work perfectly fine) + xposed + adoptable storage.
As a final mention my devie is F3211
Click to expand...
Click to collapse
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Talal Tango said:
Since you've mentioned snapchat allow me to ask. I'm on stock and I've just received the 36.0.B.2.109 update (hings are kinda slow in Egypt).
But no matter how many updates I get, snapchat quality is terrible on the front facing shooter. It's only good when it's really sunny. Other than that it's extremely dark to the point that sometimes you can't even recognize faces ! Have you ever run into that ? If yes or no what do you recommend ?
Click to expand...
Click to collapse
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
sexxualization said:
I had one bug with snapchat on the same firmware you are using but it was more app related rather than a camera quality issue. every time I opened sc the image would tend to get darker (not to mention the app itself was kinda slow) and the only fix I could find is moving the app back to internal storage (but again, this was an app bug). the only thing i can tell you is experimenting with other fws until you find one that could fix your issue, otherwise sorry but i have no idea.
Click to expand...
Click to collapse
I've had this issue on all firmwares up until the one i mentioned. And yeah i didn't even use my external usage yet, so it seems that im having a different issues although we both got dark images. I would try different firmwares but I dont know what sony did to make the battery much better on the recent firmware. I'll try messing around till I find the culprit.
Thanks.
Buggy with f3216...please fix
Help Downgrading to .111
So I've download the .111 service exchange unit firmware from Xpefirm, and created a bundle to flash it through flash tool, this is what I get in the attachment. What wrong am I doing here ? This is my first time dealing with Xpefirm so please guide me on what do from here
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Pandawa3 said:
Hi !
I've tested that because I really like root and it's works for me, but I have one problem with snapchat, when I try to connect I get this message :
I don't have xposed on this phone, just the root, and if I delete the root, it's the same problem.
Have you a solution for that ?
Thank you !
Click to expand...
Click to collapse
By deleting root, I assume you tried to delete the root app not root access itself.
You have to go back to stock rom, install snapchat, log in, root your phone and never log out.
szucsi1996 said:
Buggy with f3216...please fix
Click to expand...
Click to collapse
Hi, how is it buggy? I would like to root my f3216, thx.
Aphex33 said:
Hi, how is it buggy? I would like to root my f3216, thx.
Click to expand...
Click to collapse
i think, don't do it!
edit: Brightness adjustment not working, ui very buggy, etc.
I face this weird bug in newer Oreo ROMs where sometimes after rebooting the phone and when I enter my password on the lockscreen, the screen goes black and returns to the lockscreen. I faced this on latest Nos,ABC,arrow ROM, mokee ROM etc. If I want to enter into the phone then I have to remove the password from recovery. Anyone facing this issue
I faced it too on dotos
,
smatm said:
I faced it too on dotos
Click to expand...
Click to collapse
Did u face it any other roms, also which recovery
tom jp said:
,
Did u face it any other roms, also which recovery
Click to expand...
Click to collapse
no, I was on gsi rom for a while,then came back to dotos kenzo , faced that bug
recovery is twrp by atg-droid
smatm said:
no, I was on gsi rom for a while,then came back to dotos kenzo , faced that bug
recovery is twrp by atg-droid
Click to expand...
Click to collapse
Ok
tom jp said:
Ok
Click to expand...
Click to collapse
what happens after flashing lockscreen fixer ?
can I readd password ?
tom jp said:
I face this weird bug in newer Oreo ROMs where sometimes after rebooting the phone and when I enter my password on the lockscreen, the screen goes black and returns to the lockscreen. I faced this on latest Nos,ABC,arrow ROM, mokee ROM etc. If I want to enter into the phone then I have to remove the password from recovery. Anyone facing this issue
Click to expand...
Click to collapse
kindly refer to this thread its permanent solution is https://forum.xda-developers.com/re...x-wierd-lockscreen-bug-treble-treble-t3827445
Ishaan Kaushal said:
kindly refer to this thread its permanent solution is https://forum.xda-developers.com/re...x-wierd-lockscreen-bug-treble-treble-t3827445
Click to expand...
Click to collapse
Any easier fix, thanks for the help
tom jp said:
Any easier fix, thanks for the help
Click to expand...
Click to collapse
if there would be an easier fix then why have written this tough fix?
only way to fix this issue is too follow full procedure
if u dont believe on it whether try yourself because 3 friends tried and they also solved it by this method
It was probably magisk issue
nathanchance said:
also @D-m-x (and everyone else), please try this Magisk build (it can be installed in the modules tab in Magisk Manager)
https://transfer.sh/YVFdi/Magisk-v16.7-1674-.zip
It includes a commit that should fix all of the weird issues with Magisk like the PIN not being accepted after a reboot or the phone getting stuck at the Google logo with the progress bar. The root cause is services crashing during the boot chain and either causing deadlock or lack of functionality. It's entirely possible that a service crashed during boot and started causing issues.
Click to expand...
Click to collapse
Please refer to this post, thanks to @nathanchance
Dims_Camper said:
Please refer to this post, thanks to @nathanchance
Click to expand...
Click to collapse
can you re upload it ?
smatm said:
can you re upload it ?
Click to expand...
Click to collapse
Always first flash twrp official in fastboot when u come from miui. Dont flash any other recovery.
And format data using only with twrp official. Other twrp have problems decrypting miui encrypted data.
Coz It throw error when u use format data command to decrypt miui using redwolf and fox recovery.
And if u used treble twrp and cardinal treble and any other treble rom then wipe cust, vendor before u flash non treble rom.
smatm said:
can you re upload it ?
Click to expand...
Click to collapse
Latest magisk merged it already, that old magisk is no longer usable
Ishaan Kaushal said:
if there would be an easier fix then why have written this tough fix?
only way to fix this issue is too follow full procedure
if u dont believe on it whether try yourself because 3 friends tried and they also solved it by this method
Click to expand...
Click to collapse
Well, he might have written the tough fix because maybe he doesn't know about the easier fix. God, stop being arrogant.
Instagram : rishabh.rajbhar
Text me i will guide you
Hi here is a Magisk Module I created to enable support for taking pictures with the Redmi Note 3 Pro (SD) fingerprint sensor, I have tested this with stock camera app in Havoc OS 2.3 and several GCAM camera apps, I have successfully taken pictures using the fingerprint.
so far I have only tested this using HAVOC OS 2.3 (PIE), it might or might not work on other OSes/ Android versions, I also only tested with a FPC fingerprint sensor, if you have the goodix chip I added support but cannot test so it may or may not work.
Enjoy.
Magisk 18+
V1.
Initial support.
how to use this
marchellei said:
how to use this
Click to expand...
Click to collapse
Install the module under Magisk Manager - reboot.
open Gcam 5.1+ , press your finger on the fingerprint sensor and it will take a picture similar to how it functioned in MIUI .
There is a bug where it doesn't work with video recording (depending on gcam)., but general picture taking should work fine.
I have only tested it on HAVOC v2.3, so it might not work on other roms.
first i flash it via recovery and not working im on havoc 2.3
marchellei said:
first i flash it via recovery and not working im on havoc 2.3
Click to expand...
Click to collapse
do you have Magisk installed?
what device do you have kenzo snapdragon?
yes i have and kenzo sd
marchellei said:
yes i have and kenzo sd
Click to expand...
Click to collapse
do you know if your device has the FPC or goodix fingerprint reader?
yes i have
marchellei said:
yes i have
Click to expand...
Click to collapse
I think that program says that for either sensor. (could be FPC or Goodix)
anyways you can try installing this program (you can deny the root request since its not needed for the info we need.)
https://play.google.com/store/apps/details?id=aws.apps.keyeventdisplay&hl=en_US
and see what the "scancode" returns when you press the FP sensor, it should be '96' but it might be different for your device.
nothing happen no scancode..how do i install goodix
marchellei said:
nothing happen no scancode..how do i install goodix
Click to expand...
Click to collapse
hm it should show a scancode when you touch it, so maybe Goodix doesn't support input functions (if i recall correctly I don't think Goodix FP sensor worked for taking pictures in MIUI either).
you might still have a FPC sensor but something with the kernel might be blocking the input, I noticed you are using the ANGi kernel perhaps this is causing the issue, since the kernel controls a lot of hardware, I only tested with the stock Escrima kernel.
Hopefully some more users provide feedback if its working on their devices.
Working well on LOS Nougat. Thanks.
Tested with latest Pixel experience, no custom kernel. Sadly, not working. Keep up the good work though
hello guys ....awesome news
must be on MiuiMiX_2.0_grus rom
download and extract it to pc
restore this with twrp
after first boot install this https://www.apkmirror.com/apk/googl...9-2-74-120400-265167076-android-apk-download/
finish the pixel setup
bugs : FOD
rom download : https://drive.google.com/open?id=1JFnxymxmIiE9QfYShi4PK-E8wPhZv--X
Enjoy !!!
Flash it on your risk
Thanks for Erfan (for its GSI and permissiver) , PeppeCNN for its miui rom , pengus77 for its kernel
Hi.
Did you test it? BT works fine?
Can you tell us where did you get it?
Thanks.
kagazushi said:
Hi.
Did you test it? BT works fine?
Can you tell us where did you get it?
Thanks.
Click to expand...
Click to collapse
its erfan pixel 10 gsi ... bluetooth working well
sh4dow6oy said:
its erfan pixel 10 gsi ... bluetooth working well
Click to expand...
Click to collapse
Ok thanks for the precisions.
How is the notch? Is it nice like in miui or is it weird like in pixel experience? Are the corners rounded properly so that nothing is cut off by the corner? Does the fingerprint sensor not work at all or does it only work when the screen is on?
TheNikkoMan said:
How is the notch? Is it nice like in miui or is it weird like in pixel experience? Are the corners rounded properly so that nothing is cut off by the corner? Does the fingerprint sensor not work at all or does it only work when the screen is on?
Click to expand...
Click to collapse
notch seems ok to me ... rounded corners are weird ... bug from android 10 .... fod is not working
should I restore all? Or just the system partition?
ambinp said:
should I restore all? Or just the system partition?
Click to expand...
Click to collapse
restore all
I just installed it. Not worth trying. The display looks bad it's not optimized for mi 9 se
ambinp said:
I just installed it. Not worth trying. The display looks bad it's not optimized for mi 9 se
Click to expand...
Click to collapse
I dont have these problems
Everythings are working
dtosun said:
Everythings are working
Click to expand...
Click to collapse
wait for phh's gsi if you want a working in-display fingerprint
okitavera said:
wait for phh's gsi if you want a working in-display fingerprint
Click to expand...
Click to collapse
Is he already working on the gsi?
champagne66601 said:
Is he already working on the gsi?
Click to expand...
Click to collapse
yeah, I saw 10-stuff is going on at his github
Installed normal, but is crashing and appearing on the screen without stopping the following processes. There is no way to use it.
android.process.acore
android.process.media
m41k31 said:
Installed normal, but is crashing and appearing on the screen without stopping the following processes. There is no way to use it.
android.process.acore
android.process.media
Click to expand...
Click to collapse
did u format data
sh4dow6oy said:
did u format data
Click to expand...
Click to collapse
I formatted the data, installed MiuiMiX_2.0_grus rom, and restored it with twrp, rebooted and done.
So phhusson's AOSP 10.0 v200.d GSI boots on the Mi 9 SE, but camera, wifi, fingerprint sensor mobile data and sensors don't seem to work. I don't know whether that's because of lacking hardware support in the ROM or if it's something I've done wrong. The logcat says that it can't find the wifi drivers, don't know if that's a kernel or vendor problem.
I've tried vendor 9.9.3 and the MIUI 11 beta boot.img ROM. I'm gonna try V10.3.4.0 vendor.
New vendor didn't change anything, but I flashed okitavera's 8.2 kernel and now wifi, (the middle) camera and sensors work. Mobile data and fingerprint sensor still don't work. It's a shame because the rom is so beautiful and fluid, I'd love to use it daily, but it's just not usable without the fingerprint sensor and mobile data.
TheNikkoMan said:
So phhusson's AOSP 10.0 v200.d GSI boots on the Mi 9 SE, but camera, wifi, fingerprint sensor mobile data and sensors don't seem to work. I don't know whether that's because of lacking hardware support in the ROM or if it's something I've done wrong. The logcat says that it can't find the wifi drivers, don't know if that's a kernel or vendor problem.
I've tried vendor 9.9.3 and the MIUI 11 beta boot.img ROM. I'm gonna try V10.3.4.0 vendor.
New vendor didn't change anything, but I flashed okitavera's 8.2 kernel and now wifi, (the middle) camera and sensors work. Mobile data and fingerprint sensor still don't work. It's a shame because the rom is so beautiful and fluid, I'd love to use it daily, but it's just not usable without the fingerprint sensor and mobile data.
Click to expand...
Click to collapse
Use this rom with vendor and boot ... and flash phh 200d and permissiver v5 ... it will work ... but fod brightness is buggy
gapps
sh4dow6oy said:
Use this rom with vendor and boot ... and flash phh 200d and permissiver v5 ... it will work ... but fod brightness is buggy
Click to expand...
Click to collapse
How to install google apps?