Develop Bugs

[FIX]Proximity Sensor (In-call) issue

Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this (PLEASE NOTE THIS IS Version 2 and please use this version to revert successfully previous version had some flaws in it): http://www.mediafire.com/?d4n1fx3cj446k1l)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you

Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
5pace said:
Do you have problems with your Proximity sensor? Phone doesn't turn on while in call or randomly reboots within a call? Well, it's entirely a hardware issue found in most of the C8 (August 2012) production batch of Nexus. Not sure what your production year and month is? It's found on the sticker put on the phone (under the battery), the fourth and fifth numbers / letters are your phone's production date. A thread covering stuff about production date can be found here.
I tested this on two C8 Nexus(es). I don't guarantee if it will work for you or not but it looks like it fixed the issue for me. The only downside of this fix is that you have to use power button in order to lock your screen while in call and after the call you have to unlock it manually (This isn't a big issue in front of this issue, right?). Oh and by the way, it works on Android JellyBean version 4.2 and is untested on previous versions of Android.
So let's start:
1. So for the first step, you have to root your phone and flash Clockworkmod recovery into your Galaxy Nexus.
(WARNING: Flashing recovery and rooting leads to loss of all the data placed in your sdcard, so make sure your backup beforehand because it's better than crying later)
2. Download this zip and place it in your phone's sdcard: http://www.mediafire.com/?ir6z384vutepdmu
(To revert you can flash this: http://www.mediafire.com/?muiza8fbwidq69d)
3. Power off the phone, after that press Volume up + Volume down + Power button to go into bootloader mode.
4. After entering into bootloader mode press Volume up two times and "Recovery Mode" should come up, press power button and the phone will restart into Recovery mode.
5. Select "install zip from sdcard" then press "choose zip from sdcard" then "0" then tap on the "ProximityFix.zip" (which you downloaded in step 2) and in last press "Yes".
6. After flashing of the zip is done tap on the "+++Go back+++" and then "reboot system now".
Voila you have a proximity sensor that no more interferes into calls or anything else!
What I did?
Basically I just Hexedit'ed "sensors.tuna.so" found inside "/system/lib/hw/" and changed "proximity" to "proximits".
What it does?
The stock "sensors.tuna.so" gets replaced by the modded "sensors.tuna.so" in order to completely disable the proximity.
CREDITS:
A very good friend of mine (zurchpet) from IRC for making edify script changes for the above supplied zip.
Alexander T. for figuring out production date.
Thank you
Click to expand...
Click to collapse

orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.

yuryvrn said:
I have a CA (Oct 2012) production batch of Nexus and have this issue too. It's just for statistics.
I also wish you would find some spare time to improve the realization of your idea by removing the proximity sensor only rather than other sensors as well.
Click to expand...
Click to collapse
orph said:
Nice idea, but your fix also removes other sensors as well, (all but sound) including screen rotation. Re-installed CM10, everything came back.
Click to expand...
Click to collapse
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.

5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I have the stock JOP40D, yakju, the phone is rooted. My sensors.tuna.so is attached. I am new to android, did I understand you correctly all I have to do is to replace the original sensors.tuna.so by the modified file you will send back? Or I need to apply your patch as described in the 1st post (since my ROM is stock)?

THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.

I have this issue too. I am on CM 10.1 EuroSkank on stock kernel. Is there a zip file I can flash? Thanks for the fix!!!
Sent from my Galaxy Nexus using xda premium

PaXGeN said:
THX 5pace,
i have the annoying bug of 8C :crying:
Paranoid Android 2.99 beta8
- sensors.tuna.so
- sensors.goldfish.so
The fix is ok, the proximity sensor is disabled.
Click to expand...
Click to collapse
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium

LKNim said:
Is it compatible on other roms such as Xylon?
I got the same annoying problem
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
You can try the Fix, if it doesn't work properly you can restore the backup with the Un-Fix :good:

Proximity Sensor Blues!
5pace said:
It happens basically (to my knowledge) because of the custom ROMs you guys are on, sometimes contain files like "sensors.goldfish.so", which makes me wonder if it has any important role to play in disabling all of the sensors. You both can tell me on which ROMs you are on and fetch "/system/lib/hw/sensors.tuna.so" and "/system/lib/hw/sensors.goldfish.so" and attach it here, I'll HexEdit those files and send it back over to you guys.
Click to expand...
Click to collapse
I'm new to this forum, so bear with me. I've been having the Proximity Sensor Blues lately and am in need of a cure. I've got a Verizon GNex (rooted and unlocked) running JB Sourcery 4.0 (soon to be 4.1 unless you tell me different) with their most recent "stock" kernel. I've attached the two files you requested, but have not tried the fix yet.
Considering the ROM I'm running and the attached files, is it OK for me to try the fix? Should I try a different kernel? Does it matter if I have TWRP instead of CWM? Please help!

Everything its ok
Sent from my Galaxy Nexus using xda premium

Sorry guys, I didn't have much time to reply this topic I had exams plus real life hassles to deal with, again I am sorry for the delay.
I've attached flashable zips files and appended your appropriate usernames with them, you can download and flash these files as per your usernames. If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
On a side note I knew about the app (even before making this mod), but I wanted my proximity sensor to be disabled without depending upon an app so I eventually came up with disabling it through lib file which was far more efficient. And these files aren't supposed to disable all the other sensors, using other ROM libs on another ROM will stop the functioning of other sensors, it's just because every ROM is unique in it's own way so these files require to be modded according to their respective ROMs source files. And yeah, again I do not guarantee this mod would work because after applying it to my Nexus, it still rebooted but the reboots were less occurring as compared to when the proximity was enabled.
P.S. I re-purchased Galaxy Nexus, the old one was a C8 (White color), and luckily the new one was a C2 (Black color) and it can do wonders in overclocking and undervolting.

On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?

bacekoko said:
On my Nexus C8 not work this trick with disabling the proximity sensor
I use Xylon ROM, with his kernel...
What alse i can try to resolve the problem?
Click to expand...
Click to collapse
You may want to try this:
5pace said:
If this still doesn't work (which means it still disables all the other sensors) you can try an app called Hardware Disabler, which you can get here: https://play.google.com/store/apps/d...dware_Disabler
After installing it and scrolling down, you will eventually find a tab called gp2a (gp2a is the name of the proximity sensor's manufacturer) and there would be a check mark under it, which would be followed by text; 4-0044 (model number of the sensor), when you press the check, it will disable proximity sensor irrespective of the ROM / Kernel you're on! The only downside is that when you reboot your phone the app would come up with a screen and you have to tap Yes for it to disable your proximity sensor.
Click to expand...
Click to collapse
If it doesn't help in your case, then I am sorry as I am out of ideas.

So far, so good. Got fed up with the PS on my phone and tried this today. The sensor is disabled as far as I can tell. THANKS!

It worked for me, thanks.

All sensors are Off
Thakyou for this fix.
Not even a single call drop since i installed but none of the sensors are working.
I don't want any sensors but just the Camera so please if u can make it work I'll be very thankful.
Currently I'm on 4.1.1 JRO03C
I tried it on JDQ39 (4.2.2) it disabled only the proximity but calls were still dropping.
If possible then please make a fix to disable all sensors on 4.2.2 except camera and sound.
Thanx again.

I've a gnex with installed custom rom( minco v5 4.1.2 )
I've tried your mod for proximity sensor fix and it worked but it disabled light sensor too. I've tried app on playstore but it does the same.
I really need to disable proximity sensor to get my phone working good, but i won't to disable light sensor. Can you help me?
thank's,
Daniele.

My sensor PLS
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4

ryza666 said:
Hi. I have the same screen problem as well. Would you prepare for me my sensor files for my device PLS.... I am on CM 10.1 M3 with leankernel 6.4
Click to expand...
Click to collapse
I've use PaXGeN's sensors modified by you 5pace and there are working on my CM 10.1 M3 ( on every kernel ). I think PaXGeN pack sensors will work on every single custom rom based on jb 4.2.2. My proximity sensor is disabled but everything else is working smooth. I've checked efficiency by Android Sensor Box. Thanks for this thread.

[Q] rw system folder

Hi all, i've recently rooted my mediapad M2 10' with kingroot but now i have a problem when i try to remove the soft buttons, modifying the file build.prop in the system folder.
The problem is that i cannot set that folder as rw, but stays ro only.
I've tried installing some apps and setting rw in the es file app with no results. Do you have any suggestions?
I already tried with the terminal emulator typing some commands but everything seems to be useless.
Thank you.

Fran1422 said:
Hi all, i've recently rooted my mediapad M2 10' with kingroot but now i have a problem when i try to remove the soft buttons, modifying the file build.prop in the system folder.
The problem is that i cannot set that folder as rw, but stays ro only.
I've tried installing some apps and setting rw in the es file app with no results. Do you have any suggestions?
I already tried with the terminal emulator typing some commands but everything seems to be useless.
Thank you.
Click to expand...
Click to collapse
you'll need a modified kernel for mounting /system rw. Only having root doesn't do the trick. So one way would be unlocking the bootloader, installing TWRP and doing your adb stuff while the tablet is in TWRP. Or waiting for a modified kernel.

toxic_garden said:
you'll need a modified kernel for mounting /system rw. Only having root doesn't do the trick. So one way would be unlocking the bootloader, installing TWRP and doing your adb stuff while the tablet is in TWRP. Or waiting for a modified kernel.
Click to expand...
Click to collapse
Thankyou so much, i've unlocked the bootloader and installed TWRP. After the respring rw system was set, and finally i could modify the build.prop file.
Greetings

Fran1422 said:
Thankyou so much, i've unlocked the bootloader and installed TWRP. After the respring rw system was set, and finally i could modify the build.prop file.
Greetings
Click to expand...
Click to collapse
glad to help. Since i don't know if i'll keep my Mediapad M2 (it's a replacement for my Shield K1 currently being RMA'd), i won't unlock the bootloader for now. But if i deceide to.... Which way of unlocking did you choose?

toxic_garden said:
glad to help. Since i don't know if i'll keep my Mediapad M2 (it's a replacement for my Shield K1 currently being RMA'd), i won't unlock the bootloader for now. But if i deceide to.... Which way of unlocking did you choose?
Click to expand...
Click to collapse
I used the simple guide posted here in xda>mediapad M2 .
It costs 4$ but i think it's worth the price because theoretically you don't loose the warranty
Ps: i think you should keep the M2, removing the soft touch buttons and setting a custom launcher it's perfect.
Onestly i don't know why huawei has implemented the soft touch buttons(wasting a lot of display surface) while you can use two simple gestures on the fingerprint sensor.

what launcher ?
Hi,
what custom launcher did you use please ? And how to replace soft touch buttons with fingerprint sensor reacting ?
On my phones I use GO launcher, will this one do the job, or it has to be really 'custom' one, specially cooked for M2 ?
And my 2 cents - yes, this tablet is perfect, hardware is awesome. I believe sooner or later a lot of 'customizations' along with EMUI replacement will appear ...
Thank you
d-
Fran1422 said:
I used the simple guide posted here in xda>mediapad M2 .
It costs 4$ but i think it's worth the price because theoretically you don't loose the warranty
Ps: i think you should keep the M2, removing the soft touch buttons and setting a custom launcher it's perfect.
Onestly i don't know why huawei has implemented the soft touch buttons(wasting a lot of display surface) while you can use two simple gestures on the fingerprint sensor.
Click to expand...
Click to collapse

dexxje said:
Hi,
what custom launcher did you use please ? And how to replace soft touch buttons with fingerprint sensor reacting ?
On my phones I use GO launcher, will this one do the job, or it has to be really 'custom' one, specially cooked for M2 ?
And my 2 cents - yes, this tablet is perfect, hardware is awesome. I believe sooner or later a lot of 'customizations' along with EMUI replacement will appear ...
Thank you
d-
Click to expand...
Click to collapse
Any custom launcher is fine, my fav. is Nova but you can choose whatever you like.
For what concerns the fingerprint gestures, are implemented in the stock rom, you can enable them in the settings menu
Cheers

Low Volume on Call

I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?

romaolp said:
I´m using the latest firmware available for oneplus 3 and the volume on call is low! Using whatsapp the volume is good.
I´ve instaled and existing fix and the problem is solved but everytime that oneplus launch an firmware update I need to root the phone and install the fix!
Anyone with the same problem?
Click to expand...
Click to collapse
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk

sakarya1980 said:
I have the same. Which fix do you installed?
Gesendet von meinem ONEPLUS A3003 mit Tapatalk
Click to expand...
Click to collapse
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.

romaolp said:
I use this fix https://androidfilehost.com/?fid=673368273298967516 - TWRP-OxygenOS-Low-InCall-Volume-Fix.zip
But in every update that is launched by oneplus you need to install it.
Click to expand...
Click to collapse
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?

pulsorock said:
Does this fix still work? I need to find a solution to the low volume when using the earpiece on the latest OxygenOS (5.0.1) with Oreo 8.0. I thought was a configuration issue, so tried a factory reset but the issue continues.
If I try this, when installing TWRP recovery, the device will lose all data, right? or this will not be the case?
Click to expand...
Click to collapse
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.

tnsmani said:
Unlocking bootloader or wiping internal storage will result in loss of data. Mere flashing TWRP, if your bootloader is unlocked already, will not affect your data.
Click to expand...
Click to collapse
Thank you @tnsmani. Yes, I just remembered that. I don't recall unlocking the bootloader on this device before.
So, can anyone using OxygenOS with Oreo 8.0 confirm if this patch works, I could go ahead and try it. It would suck going to the steps and wiping everything for it not to resolve the low volume issue.
Thanks!

Low volume in custom roms using nos

i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy

davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Code:
/system/vendor/etc/mixer_paths_tasha.xml
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!

Does it give you any error during flash of the zip?

pulsorock said:
I OEM unlocked my OP3 and then flashed TWRP (3.2.1-0). After flashing, I rebooted into recovery to make sure TWRP was installed. Then I rebooted the system. After booting system, it went back to stock recovery (when I checked again).
Tried again flashing TWRP and flashing your attached zip file immediately before rebooting the system again. Still, very low volume on call and it also went back to stock recovery again. How can I avoid this? Is it goes back to stock recovery does it means the patched file will be overwritten?
When flashing TWRP, do I need to "allow system modifications" the first time TWRP is flashed? I read that will cause a boot loop. I really don't need root, just need to be able to have the volume louder.
Thanks!
Click to expand...
Click to collapse
After flashing twrp.. Reboot into recovery and root your phone
---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------
Is there a similar file for low loudpeaker volume fix?

davide136 said:
Does it give you any error during flash of the zip?
Click to expand...
Click to collapse
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
drfox96 said:
After flashing twrp.. Reboot into recovery and root your phone
Click to expand...
Click to collapse
So rooting is required to avoid twrp being replaced by stock recovery again?

pulsorock said:
No, no error at all. Everything looks like it worked fine. just after reboot system, it seems it did nothing the patch. Then when rebooting recovery, it was reverted to stock.
---------- Post added at 08:12 AM ---------- Previous post was at 08:10 AM ----------
So rooting is required to avoid twrp being replaced by stock recovery again?
Click to expand...
Click to collapse
Yes

davide136 said:
i can tell you for sure that it does not work, better, that specific ZIP does not wwork on Oreo.
The folder is wrong, you could simply extract the xml file and drop it to
Then it should work, i'm checking right now, report back if working. Maybe i'll update the zip too..
Edit:
Tested, almost broke my ear, here is the link for the fixed one for Android Oreo (I don't know if it works with AOSP)
TWRP-OxygenOS-5.0.1-Oreo-Low-InCall-Volume-Fix.zip
Enjoy
Click to expand...
Click to collapse
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?

phrozenwire said:
Hi, I tried your fix on Open Beta Experience ROM 8.0. The volume issue was sorted but it broke the wake up system. I use face unlock and the moment I click any button, it wakes up my screen and looks for my face. After this patch, don't know how but phone stopped waking up. I had to use my fingerprint to unlock the phone. No other button was waking up the phone. Also the phone started getting hot and there was a tremendous amount of lag. I had to reflash the original OS to get it back to normal.
Know why ?
Click to expand...
Click to collapse
I can tell you that i tested with my phone and this never happened, considering that's not touching any file but this "/system/vendor/etc/mixer_paths_tasha.xml", I think it's something else causing what happened to your phone. Did you flash something else? Otherwise i'll take it down

amg_driver said:
i took a look in this file/fix.
my advice: dont flash this. imo the values are set too high and this fix could damage the hardware. as davide136 said "almost broke my ear"...
Encloused my fix created for latest NOS (Oreo).
But should work on other roms as well (if path to mixer_paths_tasha.xml is /system/vendor/etc/)
Try "88-fix". If it's a bit too low for you than flash "90-fix" - as filename suggets, its 2db louder.
Click to expand...
Click to collapse
Is it Oneplus 3T compatible?
Thank you for your work!

Hello everyone, i want to clarify something, it was never a software issue.it's just DUST, believe me.
After trying all the mods and flashable zips and increasing the values, it only increase the volume but it becomes like a walkie talkie and not clear at all. So i decided to open the phone and it's very simple you can watch a video, nothing very dagerous.
Remove the 2 screws and the sim tray, carefully try to rise the screen with a credit card from the lower part of the phone.
Disconnect the battery, remove the 8 screws and remember their placement( there is one hidden screw middle left under the white stick)
Remove the signal cable and screen and extentions ones, and carefully unclip the motherboard from the top middle and try to rise it, slowly
I advice to put some ductape on the camera lenses so no dust can go in
Remove your speaker
You'll find it clean and be surprised, but the remove the black mesh a'd then you'll be shocked.
Clean the black one with alcohol and then use alcohol+toothbrush to clean the speaker grill on the phone
Clean it till you can see light through it and when you blow on it air can pass through
Reassemble your phone and connect the battery at lassst you dont provoke a shortcut when you screw or something and VOILAAA

Fingerprint yes! Flash lineage15.1 to your P20

Hello,everybody,since no developers working on custom rom for P20,we have to flash a treble rom,or,like you see here,flash a P20pro rom.
After several days trying,I finally suggest you to flash the lineage15.1 rom ported to P20 pro from Luk.
Now,it's time to escape from Huawei EMUI，out of the limit(like more apps background running).
What's the good thing?
Fingerprint yes! Fast charge yes! Full screen apps yes! Even stock camera(from Androlark).
Any bugs?
NFC(not working at all) ,wifi-hotspot(you can use USB tethering instead).
Here is a guide for flashing:
Before you go,make sure a unlocked bootloader,and twrp for installing gapps/migisk/stock camera.And you must do a full factory reset,it's very important ,otherwise the rom can't boot.
A flashable system.img link(extract from Luk's P20 pro rom)
One-click ADB
Flash it using ADB tool.
Type the following line:
Code:
fastboot erase system
Code:
fastboot -u flash system p20-lineage15.1-system.img
Then reboot.
If you want to flash gapps,after boot worked,turn the "Developer options"-"Advanced restart",then reboot to twrp,wipe data cache dalvik again(it's necessary,if not ,you will see the apps forceclosing again and again)
Cheers:highfive:
Thanks @LuK1337 again

Reserved for Q&A.

Thanks for the thread man !
But with the upcoming update of Pie, i will wait a little bit before jumping on a new rom than the EMUI, otherwise i would already installed it.

maxime4611 said:
Thanks for the thread man !
But with the upcoming update of Pie, i will wait a little bit before jumping on a new rom than the EMUI, otherwise i would already installed it.
Click to expand...
Click to collapse
I can't wait,so I flash the rom. Apart from that,I also like original Android,with much more freedom

qisu2011 said:
I can't wait,so I flash the rom. Apart from that,I also like original Android,with much more freedom
Click to expand...
Click to collapse
Finally able to boot on the rom.
If you have trouble for install : try a different version of adb, and after a full factory reset, go to twrp and wipe dalvik, cache and internal storage again then flash.

How come hotspot is broken here but not on the official Treble Lineage 15.1 ?

maxime4611 said:
Finally able to boot on the rom.
If you have trouble for install : try a different version of adb, and after a full factory reset, go to twrp and wipe dalvik, cache and internal storage again then flash.
Click to expand...
Click to collapse
That's right bro,sorry I didn't help you in time yesterday,I'm in China,there's a time difference between us.
Upload an ADB tool I'm using,for those who need it.
One-click ADB

Thanks for the tool
- Fingerprint working
- Root & magisk supported.
- Stock Camera mod also works
- Always on display (but i really don't like it and no stock setting to disable it completely, only hide it when you turn off the screen)
So far the bugs i encounter are:
- No notch support (but icons are spread between the edge of the status bar, so only the speed meter is hidden in my case)
- The home button only works for fingerprint sensor if you have virtual button enabled.
-NFC ? (i don't use it)
Here's some screenshots to show the notification system's behavior (yes, they are expandable from the notification drawer and lockscreen :good: )

I attach a link for a simple script tool that I have used which is very useful for creating flashable system images from system.new.dat.br and system.transfer.list files.
Extractor 3.5
I have attached this so that people can make their own system image files when the Linage OS rom is updated rather than wait for someone to upload their own image files.
Instructions
1. Extract Extractor folder from attached zip.
2. Extract system.new.bat.br and system.transfer.list from rom zip file.
3. Place files in folder labelled "place_for_supported_files_here".
4. Run Extraktor_EN.cmd
5. Select option 9.
6. Use the system.new.img and flash using fastboot as detailed in the original post.

maxime4611 said:
Thanks for the tool
- Fingerprint working
- Root & magisk supported.
- Stock Camera mod also works
- Always on display (but i really don't like it and no stock setting to disable it completely, only hide it when you turn off the screen)
So far the bugs i encounter are:
- No notch support (but icons are spread between the edge of the status bar, so only the speed meter is hidden in my case)
- The home button only works for fingerprint sensor if you have virtual button enabled.
-NFC ? (i don't use it)
Here's some screenshots to show the notification system's behavior (yes, they are expandable from the notification drawer and lockscreen :good: )
Click to expand...
Click to collapse
There are options in system settings bro.
Display-advanced

At first thanks for your work :good:
Which one of Luk's builds you took?
The new (25.09.2018) or the old (28.08.2018) one ?

Schubi97 said:
At first thanks for your work :good:
Which one of Luk's builds you took?
The new (25.09.2018) or the old (28.08.2018) one ?
Click to expand...
Click to collapse
new

Man, I really want Lineage 16 instead... I've had no luck finding any Pie based rom for the P20.

qisu2011 said:
There are options in system settings bro.
Display-advanced
Click to expand...
Click to collapse
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...

Muscar said:
Man, I really want Lineage 16 instead... I've had no luck finding any Pie based rom for the P20.
Click to expand...
Click to collapse
That's the problem,no pie rom for p20 can boot except emui9 beta at the moment. I tried all I could find, including aosp pie for Honor v10,which is based on emui8.1 vendor,can boot on p20 pro.

USB C headphones doesn't work

Theo1218 said:
USB C headphones doesn't work
Click to expand...
Click to collapse
No they dont, adapter works..

maxime4611 said:
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...
Click to expand...
Click to collapse
I have tested for days bro,it's normal on my phone.
I flashed the rom based EMUI version 167sp1(for CN EML-AL00). Maybe this is the point?

maxime4611 said:
Exact i checked the same options, but when you receive a notification, it still displays the notification on the ambiant display mode... When you turn on the phone or touch it, you activate the lockscreen.
With that black screen, i miss notifications if the phone is laying on the table for exemple ...
Click to expand...
Click to collapse
I have tested for days bro,it's normal on my phone.
I flash the rom based EMUI version 167sp1(for EML-AL00),could this be the point?

Anyone tried this on their P20 yet?
https://forum.xda-developers.com/hu...r-forget-emui-9-install-aosp-android-t3855930

[ROM][UNOFFICIAL][W.I.P]LineageOS for Redmi Note 9S/9Pro[curtana/joyeuse]

tldr; use the LeddaZ build
Downloads:
ROM
Lineage Recovery
Hello XDA,
I'm posting a build using the unified curtana build code that's on github. I have a joyeuse (9 Pro) so I can't really test it on the 9S (curtana). I've been testing it out for a couple of days and haven't had any bugs other than status bar centered items.
Bugs / not working / To do:
Wireguard support Added 18-Sept
Play Store certification (Workaround using MagiskHide Props Config)
64 MP camera module seems to work only with the ANX Camera ver 185(not included). You must manually add all permissions.
Status bar text around the front camera
Code:
Source Code: https://github.com/LineageOS
Device: https://github.com/xiaomi-sm6250-devs/android_device_xiaomi_curtana-unified
Kernel: https://github.com/xiaomi-sm6250-devs/android_kernel_xiaomi_sm6250
Vendor: https://gitlab.com/m0sin/proprietary_vendor_xiaomi_curtana

Play Store certification: Have you tried with the latest gapps yet?

How to install? Anything I need to look at?

dungphp said:
Play Store certification: Have you tried with the latest gapps yet?
Click to expand...
Click to collapse
I have, it might be Magisk or I'm not hiding it properly.
Edit: I used the Magisk HideProps module and everything works fine now. I think the naming, curtana vs joyeuse and version number were causing the issue.

glurak888 said:
How to install? Anything I need to look at?
Click to expand...
Click to collapse
If you are coming from stock, I installed the Lineage recovery, installed the ROM. After it rebooted, I went back to install OpenGapps and Magisk.
I tried going from stock using Pbrp but it failed for me. After Lineage was installed, PBRP worked fine.

I have just installed it, anything I should know?

Installed successful on
Note pro 9 a Joyeuse (global) with 64mp cam , nfc and Lte aka a M2003J6B2G
Only recovery from lineage worked for me ... it also enables fastbootd !!
Rooting with magiskmanager wasnt possible via patching boot.img but flashing Magisk-v20.4.zip via recovery worked .
nfc works too
fastcharge seems so work fine ...
lte seems to work too
will try anx cam and 64 mpx tomorrow ... //edit - ANXCameraUnity_185.SaltyIntelligentPlainsqueaker and 48MPFixQ_170.SophisticatedFatBetafish make it work too ....
thx

I installed the ANXCameraUnity_185.SaltyIntelligentPlainsqueaker.zip and the camera app crash all time. Should I install and the 48MPFixQ_170.SophisticatedFatBetafish.zip?
Thank you for this nice rom, keep walking.

[email protected] said:
I installed the ANXCameraUnity_185.SaltyIntelligentPlainsqueaker.zip and the camera app crash all time. Should I install and the 48MPFixQ_170.SophisticatedFatBetafish.zip?
Thank you for this nice rom, keep walking.
Click to expand...
Click to collapse
Yes, install the 48 MP Fix to add the 48 MP camera. It's crashing because you need to manually fix the permissions on the app. After you allow everything it'll crash once then work fine.

Minor update:
September security patch
Added wireguard kernel support 1.0.20200908

moffa~ said:
If you are coming from stock, I installed the Lineage recovery, installed the ROM. After it rebooted, I went back to install OpenGapps and Magisk.
I tried going from stock using Pbrp but it failed for me. After Lineage was installed, PBRP worked fine.
Click to expand...
Click to collapse
so basically we flash on joyeuse a curtana recovery in order to flash a curtana rom and then we flash back the joyeuse recovery right?

didicola said:
so basically we flash on joyeuse a curtana recovery in order to flash a curtana rom and then we flash back the joyeuse recovery right?
Click to expand...
Click to collapse
Not sure I understand what you are saying. The build is joyeuse/curtana unified. I don't like not being able to flash zips without sideloading so I'm using the PBRP recovery. For the initial flash I used my PC and the Lineage Recovery.

Are the gapps included or do we need to flash them?

kalehrl said:
Are the gapps included or do we need to flash them?
Click to expand...
Click to collapse
Not included. Must be flashed.

Excellent rom, I have used it since its publication, and so far no problem. The performance of the battery seems to me outstanding, and to this day, it is the only one in which an indispensable application for me (Sony Music) works without problem. I hope the excellent work continues, and it even became an official version. Thanks!

I use redmi note 9s, can i flash this rom?

vanmaitrangchu said:
I use redmi note 9s, can i flash this rom?
Click to expand...
Click to collapse
Theoretically yes. Please share your experience if you try it out.

moffa~ said:
Theoretically yes. Please share your experience if you try it out.
Click to expand...
Click to collapse
When i used mi note 3, lineage is bettest rom for me. But it is officical. with mi note 9s (4/64) i got few bug, i try test it again.
first day i got:
when flash, i have some problem, but it easy, forget it. after that i reboot system, 2 minute its done. reboot to recovery to flash gapp (nano), reboot, but i can sync adress from google .
Try again, i wipe all data (rom in sd card), flash again. reboot device, wait rom instal, reboot recovery, flash gapp again, reboot, it ok :v i dont know why!
some thing i dont like with rom:
- dial not support dual sim, mean: icon sim1 sim2 when use dial pad. i use 2 sim.
- swicht speaker too much make phone restart (im shiper, i usally switch), it make me crazy.
- no 1 hand mod, i ussally use it with 1 hand, to big to use.
And else i like this rom, from mi note 3.
Sorry, my english very bad! I hope offical soon, thanks so much!

vanmaitrangchu said:
When i used mi note 3, lineage is bettest rom for me. But it is officical. with mi note 9s (4/64) i got few bug, i try test it again.
first day i got:
when flash, i have some problem, but it easy, forget it. after that i reboot system, 2 minute its done. reboot to recovery to flash gapp (nano), reboot, but i can sync adress from google .
Try again, i wipe all data (rom in sd card), flash again. reboot device, wait rom instal, reboot recovery, flash gapp again, reboot, it ok :v i dont know why!
some thing i dont like with rom:
- dial not support dual sim, mean: icon sim1 sim2 when use dial pad. i use 2 sim.
- swicht speaker too much make phone restart (im shiper, i usally switch), it make me crazy.
- no 1 hand mod, i ussally use it with 1 hand, to big to use.
And else i like this rom, from mi note 3.
Sorry, my english very bad! I hope offical soon, thanks so much!
Click to expand...
Click to collapse
Thanks for testing it out.
Unfortunately, I don't have a second sim card to test it with.
I have no problem using the speaker phone at all. Could you grab the logs, maybe I can look into it.
It looks like one-hand mode was removed from Lineage. There are gestures for navigation. It works about 90% of the time for me.
------Edit-------
I tested my phone out with a second sim card today and had no issues. Is anyone else having issues with a second sim card?

moffa~ said:
Thanks for testing it out.
Unfortunately, I don't have a second sim card to test it with.
I have no problem using the speaker phone at all. Could you grab the logs, maybe I can look into it.
It looks like one-hand mode was removed from Lineage. There are gestures for navigation. It works about 90% of the time for me.
------Edit-------
I tested my phone out with a second sim card today and had no issues. Is anyone else having issues with a second sim card?
Click to expand...
Click to collapse
The problem occurs when turning on the speakerphone while calling. End of the call without turning off the speakerphone, the next call will easily lose sound. Ratio 1/5. Trying to turn on and off the speakerphone is very easy to reset the device.
Regarding the 2 sim issue: I mean there is no separate button for the 2 sims in the dial pad. Like the dial pad of the EU version, very convenient.
I need one hand mod, too hight with my hand. like picture.