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.
Related
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
anubius said:
I need an opinion on this one. I've looked for this problem but it seems not to be clear what is causing it. I have Wildfire S (EU) Marvel. The device is S-On but I unlocked the boot loader and installed CWM. I've already tried several ROMs but it doesn't help to solve the issue. The problem appears during making the call - the screen goes black when you put the phone next to head and after that doesn't want to wake up. The only thing that wakes it up is putting it next to strong light source so I think the light sensor is the one to blame. However automatic backlight seems to be working fine. I really hope that it is not hardware problem. Please give any suggestion to try solving this problem. I would even go for the option to shut down somehow the light sensor because restarting phone after each call is kind of annoying. Thank you in advance for any help you can provide. Sorry for such a long introduction.
Click to expand...
Click to collapse
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
b02 said:
long introduction is far better than a short one ...
did you install rom propperly (factory reset/cache clean/dalvik clean)?
did you try using any other dialer app just to check ?
Like this, or this
I think i have read about such problem somewhere, if i find it i will post you the link to it...
also here are some apps to check your proximity sensor :
ProxyLightTester i couldn't find it on market. (not tested)
Proximity Sensor Finder Market link. (tested) and it will report 'all or nothing'
Click to expand...
Click to collapse
Hi, Thanks a lot for suggestions. So it seems to me that proximity and light sensors work. I tried several software including the one you suggested and the proximity and light sensor respond ok. I also tried different dialer but it doesn't help. I have no idea what can it be. I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem. Thank you again for helping. And your device never had this problem?
Never had that problem.. Try reflashing w/o any app2sd gapps and stuff, just clean new rom and try it..
Sent from my HTC Wildfire using xda premium
anubius said:
I am thinking to put the device back to the factory state and maybe install official ROM but I am not sure if this will solve the problem.
Click to expand...
Click to collapse
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Tera Tike said:
Before you do that try this build.prop file and see if it helps...Just remove the ".txt" and set your permissions same as the old build.prop file you renamed.
Click to expand...
Click to collapse
Thank you guys for all the suggestions I followed your advices but the phone simply refuses to wake up after the call. I am trying to go back to factory default since this is my last hope. Really confused what is causing it.
Hey guys the official rom is out
http://blogs.att.net/consumerblog/story/a7783602
you have to update your device over kies.
Cheers
Got the message just now
" AT&T Free Msg: Samsung Captivate Glide upgrade to Android 4.0 Ice Cream Sandwich is now available! The OS update supports enhanced performance, user interface and other device improvements. Open the link from your PC (not your phone), and follow the instructions: www.samsung.com/us/attcaptivateglide/update "
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
page was working about an hour and now page not found. Maybe they pulled the update? I haven't tried it yet because of the keyboard backlight issue from other posts...and I have no desire to do any rooting/CWM stuff.
Page worked for me just now. It basically just says download kies and let it upgrade.
Does the official rom have the same version number as the leaked one?
Sent from my SAMSUNG-SGH-I927 using xda app-developers app
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
There are no bugs, samsung has fixed it all
Does the official version have CarrierIQ?
Nevermind.
R3D X said:
There are no bugs, samsung has fixed it all
Click to expand...
Click to collapse
Oh? That's not what others have reported - the keyboard backlight is supposedly still broken, unsure about tethering or the other problems.
gnahc79 said:
strange now the page works again...has anyone applied the official ICS with AT&T yet? wondering if the backlight issue is resolved.
Click to expand...
Click to collapse
No backlight on my wife's Glide... She's pissed...
Then root and install the zip
I actually passed on this phone because I was worried it might not get ICS. I'm glad it did all the same. I miss having a hard keyboard.
Sengfeng said:
No backlight on my wife's Glide... She's pissed...
Click to expand...
Click to collapse
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
gnahc79 said:
thanks for the save!!!! I was downloading the update when I saw your post. my wife would have been VERY upset as well. good luck.
I don't want to mess with rooting, CWM and all that stuff on the wife's phone just to get back a basic function. Doing all of those things to get new functions...maybe.
Click to expand...
Click to collapse
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
bakageta said:
Really, it's super-easy to install the backlight fix, and you don't even have to root or muck around all that much. You flash CWM in odin, which takes about 30 seconds, and then boot into CWM and flash a single zip file, which should take at most a minute including the reboot time. Tada, keyboard light is fixed.
Click to expand...
Click to collapse
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
gnahc79 said:
That requires root access and messing with stock recovery right? Although it can be done quickly, it could mess up any future official ICS update...you know, an official build that has the backlight fix + other fixes. I'd rather not deal with unrooting, getting stock recovery back on, and still have a risk of a soft brick....all for a backlight fix. For my scenario ICS can wait or never be applied on the glide. My wife doesn't care .
Click to expand...
Click to collapse
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
Anh56 said:
Im in the same situation can u do like a step by step how to do that cause i dont want to brick my phone in my trying to figure it out on my own
Click to expand...
Click to collapse
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
bakageta said:
To fix the keyboard backlight bug, you'll need the following:
Odin 1.85
Clockworkmod Recovery
The Keyboard Backlight fix The one labeled LH2 is for the official, the one labeled CWM is for the leak. If you're not sure what you're on, go to About Phone, and check the Baseband Version, if it ends in LH2 you're on the official, if it ends in LG9 it's the leak.
Optionally, SuperUser 3.2 RC3 if you'd like root.
First, make sure you have Kies installed, so that you have the correct USB drivers. Download the 4.0.4 .exe file from here. Power off your phone, hold Volume Up and Power to turn it back on. Keep holding them until you get a screen warning you about custom software, and release, then press volume up again to enter download mode. Hook the phone up to your pc and run Odin 1.85. Uncheck "F. Reset Time" and make sure that the only box checked is Auto Reboot, you shouldn't need to change anything else. Click on the PDA button, and load the clockworkmod .md5 file you downloaded, then press the start button and wait for the device to reboot.
This time you'll reboot into recovery. Power the phone off, hold the volume down and power button to turn the phone one. Keep holding them until you see text about entering recovery in the top left, and release. Use the volume keys to navigate and power to select, and go to Install zip from sdcard. Select the keyboard backlight fix zip. Once that's finished, if you'd like to be rooted, repeat the process to flash a zip, and this time select Choose zip from sdcard, selecting the superuser zip you downloaded earlier. Select Yes, and wait for superuser to flash. If you plan on keeping Clockwork Mod Recovery, you should make a backup now. To do so, select Backup and restore, and backup. This will take a bit, just be patient. When you're finished, select reboot system now, and you should be set.
From here, if you rooted you can install something like Titanium Backup, which will use root access to let you remove the various AT&T bloatware.
Click to expand...
Click to collapse
Yeah backlight isn't working sorry, someone on a blog had said so. Very unprofessional of samsung. A rom cooked with cm9 willl have to include the backlight fix
bakageta said:
It actually doesn't require root access, just a custom recovery, which is flashed from the PC. You can then replace it with a stock recovery, if you prefer.
I made a walkthrough for the entire leak here, but I'll snip it down and just assume you're running some form of ICS now that's completely stock:
Click to expand...
Click to collapse
:good:
Cool, thanks for the info. Good to know root is not required. I'll still hold off on the update but I'm sure others will apply ICS+backlight fix.
I updated last night, and I can report that after ending any call the phone app reports a hard stop rather than just going away, and that resets your cell connection. And I imagine the keyboard backlight will be fixed very soon. But did these issues exist on the leaked rom in its first release and then programmers modified to get them back?
-Ara
Sent from my SGH-I927 using xda app-developers app
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Have you tried flashing back to stock and seeing if that fixed these issues?
Pal Guite said:
Phone - Moto Z play XT1635-02-DS
Android- 7.1.2
Installed TWRP 3.1.1.0
Viper addison 7.1.2
Here are my problem:
1. Flashed with supersu v2.79 and also v2.82, neither works. Phone still not rooted. When i tried toa access supersu app, it says "there is no su binary installed and supersu can't install it..."
2. Camera does open but it doesn't function, it stays dark. (I have custom gapps 7.1.x)
3. Proximity sensor does not seem to be working in other cases, but the phone goes dark as soon as i press dial or as soon as i pick a call and remains so untill the other party cuts the call. Otherwise i need to shut down the phone if i have to end the call from my phone.
4. When i shut down the phone, in order to reboot manually from recovery-reboot-bootloader. Otherwise it remains in twrp recovery.
Can anyone help please?
Click to expand...
Click to collapse
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
gman88667733 said:
Have you tried flashing back to stock and seeing if that fixed these issues?
Click to expand...
Click to collapse
Thanks. But i don't have the stock rom. I didn't intend to use a custom rom. I tried to root it to recover some deleted photos and the moron that i am, i didn't back up the stock firmwares and while tweaking around in the recovery i somehow deleted the stock rom. This is my 1st time...
DroneDoom said:
This is not really a problem with the phone per se but the rom you chose to flash. The reboot issue can be checked by setting a command at bootloader using "fastboot oem fb_mode_clear".
Click to expand...
Click to collapse
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Pal Guite said:
Thanks... I tried the above command (it does recognize my device) bur this is what i get :
{bootloader} slot-count: not found
{bootloader} slot-suffixes: not found.
Click to expand...
Click to collapse
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
DroneDoom said:
Is there an option for the bootloader in developer settings in your rom similar to the screenshot I attached? Make sure it's enabled.
Click to expand...
Click to collapse
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Pal Guite said:
Thanks for your concern. Developer option is 'on' and Multiprocess webView renderers seperately - 'on'. But i get the same problem. (and how do you attach screenshots ? I don't see any option for attaching files) In anycase, like you said, i think the problem has more to do with the rom. Can you please suggest me another rom or if possible link from where i can download stock rom for my phone.
Click to expand...
Click to collapse
If your on xda with your browser, it's the paperclip icon to attach files. If you are using a 3rd party app that wraps xda into it then I can't help you there. As for going back to stock, Motorola made things a little critical when they released Nougat. Depending on how far you were on keeping the device up to date through stock, flashing the available stock images (which aren't signed) could brick the device if you aren't careful. There use to be an account on androidfilehost that uploaded current stock packages but it seems they're all gone now. If you remember the build number of the device before you rooted, that will help in picking the right stock files. I've taken a break in keeping my device rooted so I haven't kept track of the resources used to help go back to stock but they're in the MZP guide threads.
EDIT: a word of caution when reverting to stock:
-Don't use flash tools that don't let you see/edit the fastboot commands
-Do not use commands that touch modem/radio or gpt partitions
Found an upload of the latest build release keep it around when you figure out what you need to flash. It's best to clear system, data, and cache before flashing. Also have a rom (and twrp) at hand to adb sideload in case stock doesn't boot.
https://androidfilehost.com/?a=show&w=files&flid=215703
This Android version 7.1.1
Security patch: Sept 2017
Build number: NPN26.118-22-2
Thanks alot... ?
This Mod uses your fingerprint to lock your device. Longer presses will take you to the reboot menu.
:good: Download in my rom section or this quicklink.
https://forum.xda-developers.com/devdb/project/dl/?id=29427
How can i remove it from my phone?
nemanco said:
How can i remove it from my phone?
Click to expand...
Click to collapse
Unfortunately I had to reinstall my rom. :x
The problem was that the FP sensor is way too sensitive after installing the mod.
I couldn't hold the phone in the hand without instantly triggering the FP sensor.
Foremost the FP sensor doesn't react not only to saved FP's.
You should definitely look into that, Jerome.
Or at least offer a patch to uninstall the mod.
Besides that it's a very good idea, but it needs fine tuning.
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
nemanco said:
Could you please give me the uninstalation for the mode the fingerprint sensor is to sensitive, and i realy dont want to reflash the stock rom again ?
Click to expand...
Click to collapse
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment restore-fingerprint.zip
SubwayChamp said:
Put without unzip inside this zip only the META-INF folder from the zip that you flashed meanwhile OP can solve this, hope this works
View attachment 4505426
Click to expand...
Click to collapse
Worked as a charm, thanks! !!!
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
mavid26 said:
after flashing the zip file all working and really good but the volume rocker and power doesent work, I downloaded the removefingerprint.zip but also doesent work when I flashed the file.
My currently Rom is AOSP Extended 7.1
thanks.
Click to expand...
Click to collapse
Almost any rom would need a proper remover/replacer zip, last was for miui roms so try this, read the post #5 and apply to this zip before flashing it. I hope it works
View attachment restore-fingerprint-aex71.zip
I installed the lineage os 15.1 on my xiaomi redmi 5 plus, but the fingerprint settings are not there and I do not know how to put them.
Are there any mods? How can I do?
thank you
Thanks for your amazing mod it's working prefect on my miui but now i installed pixel experience rom and the mod not work. Please update it for costume roms.
Tested on MIUI 10 RN5 Global (AI) and it broke both power button and fingerprint button.
EDIT: the fix provided did not work for me. Copied the folder as requested to the zip but even after flash the buttons are still broken (had to flash the ROM, just a system restore could not fix it too.)
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
sfnemis said:
it ****ed up my Redmi 5 Plus phone i don't want to reinstall my rom please publish uninstall for oreo or Pie patch .
Click to expand...
Click to collapse
Which version firmware are you using?
lock unlock fingerpriner
does it exist for redmi note 7?
Way to fix...
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
king.com said:
Perhaps a bit late, but...
For those who lost power and volume rockers the problems is file permissions.
You have to change file permission of 3 files on /system/usr/keylayout:
- Generic.kl
- uinput-fpc.kl
- uinput-goodix.kl
and set them to "-rw-r-r--"
also set them to be owned by root:root
While booting these files must be read for non root process. On some installs the last "r--" (other user privileges) are not set correctly.
Also, you must know that each keymapping files are for each brand and model. Where key 353 if for virtual fingerprint on RN5, the same "virtual fingerprint key" is number 96 on Mi Mix2, so if you flahed these files por RN5 on other model, you should find these files from a ROM (TWRP/nandroid backup from your device previous to the flash), or other rooted device and copy them to your own.
With these instructions you could prevent flashing entire rom
Click to expand...
Click to collapse
Hi, Is there a code you know for the mi A1 (tissot) is needed to lock the screen.
or there may be a hint on where to find it, thanks :victory:
I am using Pixy Os 9.0 on Default Kernel And Phone Sensors are stopped Working like (accelerometer, proximity etc.).
I've tried going back to Oreo roms but not success.
Should I try changing kernel or something?
Try flashing this
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
That worked. Thank You
That sensor flashing is easy way. However I took a different time consuming way. Writing it down so that it may help some one else.
When I switched from Oreo AiCP to latest Pie AEX, I went via the hard way. You may read it here https://forum.xda-developers.com/le...bootloader-t3868174/post78256476#post78256476
AEX 6.0 worked well but I too was facing sensor issue. I re-flashed the ROM but no effect. CPU-Z sensor page was complete blank. Yes, I knew the sensor.zip available for flashing but I went ahead to REDO the entire ZUI 1.9 to AEX flashing process.
This time around, all sensors are working fine.
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
mirkios said:
How to flash the sensor.zip fie?
I have ZUK Z2131, Android 9 and a problem with proximity sensor, when I answer to a call the display goes black, but I hold the phone in my hand and I can stop the call only with the power button. Will this zip helpinng me? And please tell me how to use it! Many thanks!
Click to expand...
Click to collapse
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
satyen_ said:
Just goto recovery and flash the sensor.zip file.
Yes if the is due to sensors not working then it will help you but if the issue is from rom side code then it might not resolve the issue.
Are other sensors such as auto rotation working? If yes that might indicate that the issue is from rom side
Click to expand...
Click to collapse
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
mirkios said:
I don't know what about the rom, because in the first place I changed the entire frame+screen+touch, all came in one piece. Until then the phone has no OTA, was stock international rom. I changed to Chinese rom because of this problem and step by step, I updated the stock rom until I reached the last version. After that I tried a custom room (this is actually on the phone, Android 9/AospExtended-v6.5-OFFICIAL), but with all rom the phone has the same behavior. So, what do you think?
Click to expand...
Click to collapse
I think the issue is not with any ROM, it is due to the screen and all other replacements, may be after the replacement your proximity sensor is always covered or blocked with something. There are apps on playstore to see the proximity sensor data check if the always shows the same distance/reading i.e. 0 while waving your hand over it, and if yes then the issue might be what I mentioned above. If that's the case you would have to take of the screen and adjust the proximity sensory properly.
Check with this app :
https://play.google.com/store/apps/details?id=imoblife.androidsensorbox
satyen_ said:
Try flashing this
Click to expand...
Click to collapse
I have AOSP 10 on my ZUK. The sensors did not work.
Thank you. Now everything works well.