Develop Bugs

Finally! Found out how to disable the proximity sensor on Gingerbread!

WARNING: I am NOT responsible if you **** up your device doing this. While I see no reason why bad things would happen, you still execute this (admittedly primitive) procedure at your own risk.
As some of you will now, the cm3602, the proximity sensor of the HTC Desire (and many other HTC devices) is a bad piece of hardware with a high tendency to malfunction. This causes users to be unable to light up the screen during calls (so you can't end calls or dial or do anything until the other person hangs up).
Well I have the solution!
But you need to be rooted
For Froyo users: append gsm.proximity.enable=false to the build.prop file (download a build.prop editor from the market, add property, as a name put gsm.proximity.enable and as key or value put false).
For people with Gingerbread or for those that find the previous method to not be working, there is the following brute force method. Again, you need to be rooted to do this.
What this does:
- This method ****s up the registry key that the system uses to load up the proximity sensor's drivers. Basically, Android doesn't know how to manage the proximity sensor so the sensor doesn't work (but you don't care because it's broken anyway)
You'll need:
- rooted phone
- the app Hex Editor (free on Google Play)
Instructions:
- Open Hex Editor
- navigate to /system/lib/hw
- click on the file sensors.bravo.so
- you'll see a bunch of numbers, some white, some green; don't worry
- in Hex Editor go to settings and check Root permissions, click allow on the SU prompt
- in Hex Editor, click on the search icon, select ASCII, and search 3602
- 4 pairs of green numbers will be highlighted. Click on any one of the pairs and change its value to something else (use 55)
- in the Edit screen, click on the little save icon to save the edited value
- keep searching for 3602 and editing it like before, there aren't many entries
- when you have edited them all, click on the save icon in Hex Editor. If everything went well, it should tell you that it has saved the file. If not, you have not given it root permissions.
- reboot the phone and try calling, your proximity sensor will be dead!
Tested on Android 2.3.7 with CronMod 1.0.6 and kernel 2.6.35.14-CronModKernel-1.6-GSM-RC
If someone with actual skills wants to build this patch into an app or flashable zip it would be great!

Thanks but neither method worked for me on Oxy ZM. The first method did nothing, the second bricked my phone forcing me to restore a nandroid.
Just a warning to anyone who tries this on any other ROM than stock.

Gingerbread method worked for me. Thank you !!
Htc desite on Mildwild CM8 GB Stable. (2.3.7)

I just registered to say THANK YOU from the bottom of my heart. I got HTC Desire a few weeks back and I've tried bunch of stuff, I've settled down for MIUI rom that has got Proximity off option in call settings, but I couldn't get past the fact Runkeeper app wasn't working for me.
To all the others, I've followed this Gingerbread tutorial with Hex Editor, step by step, I even wrote 55 instead of other values and it's all working!!! Awesome, man. Thank you. Thank you. THANK YOU! :good:

Doent work on my Desire S
I've tried everything....

[Q] System sound problem about D855 Build.prop(It is Urgent)

I'm change the value inside the build.prop to enable the split-windows for all apps, after i reboot my g3 ,it can be split-window for all apps, but i only lost my system sound(For example: lock screen sound, unlock screen sound, volume +/- sound),another notification sound is work. I have been check my setting is don`t have any problem. I have try to use http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693 SCRIPT to BACKUP and RESTORE Build.prop is can`t repair the problem. Can anyone help me? or upload the D855 v10n-HKG Build.prop.

adrianlaw666 said:
I'm change the value inside the build.prop to enable the split-windows for all apps, after i reboot my g3 ,it can be split-window for all apps, but i only lost my system sound(For example: lock screen sound, unlock screen sound, volume +/- sound),another notification sound is work. I have been check my setting is don`t have any problem. I have try to use http://forum.xda-developers.com/lg-g3/general/guide-build-prop-tweaks-free-ram-t2825693 SCRIPT to BACKUP and RESTORE Build.prop is can`t repair the problem. Can anyone help me? or upload the D855 v10n-HKG Build.prop.
Click to expand...
Click to collapse
You could re-flash the rom to fix this. Also try restoring the default value through a build prop editor.

Im having the same problem. Any solutions?

Button haptic feedback and q-button stopped working

Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.

xlJohnnyIcelx said:
Hello, this is my first time posting here. I was having some trouble with the touch screen not being responsive enough, sometimes missing my taps. So I installed this mod: http://forum.xda-developers.com/showthread.php?t=2347009&page=3
Not only did it not appear to change anything, after rebooting I found that my menu and back button no longer vibrate like they should (yes vibration is on in settings) and my q-button no longer does anything. And my home key does not turn the screen on now either. This has to be a simple key configuration change but someone please help me fix this issue Oh also I have the at&t version of the phone if that makes a difference.
Edit: I have found more information about this problem. One being that the mod I spoke of only changes the usr folder of the system folder which contains the key mappings gk-keypad-8064.kl file. I tested and trying to change the QuickButton command in the settings no longer affects this key mappings file as I believe it should. So somehow it either can't find the file (even though it's there) or thinks that the file is corrupt. So is there anyone who has the stock gk-keypad-8064.kl file I can use? Or maybe there should be different permission settings other that rw r r? Please let me know as I think this is the main problem here.
Click to expand...
Click to collapse
How about you try to flash back to the stock rom using the lg flash tool?

I fixed it with a work around. I used exposed additions to force haptic feedback and also to map the q button key. Hopefully if anyone else has this problem it will help them.

Vibration work only when charging

I´m on stock rom, but since first miui 11 update the phone only vibrates when charging. I´ve tried to change all settings on accessibility and "sound and vibration", nothing solves the problem.
Any hints?

Found a solution! Looks like a bug, vibration isn't restored when phone leaves battery saving mode. Vibrations can be restored via ADB (but you need to allow write secure settings in developer options) using
settings put global battery_saver_constants "vibration_disabled=false,animation_disabled=true,adjust_brightness_disabled=false"
EDIT: after some time vibration was disabled again, even without entering battery saving mode.

I'm facing this also with PocoF1

Themes / Apps / Mods [FIX]IN CALL PROXIMITY SENSOR FIX

Congratulations guys I have created n tested highly advanced fully automated solution , now screen will work during calls as it should W/O NEED OF PROXIMITY SENSOR, WAIT FOR NXT RELEASE, TESTING.....
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
proximity_fix2.xml
Backup from action
drive.google.com
7. What's next.
Probably u will have a very good workaround where by screen will act like it should during call WITHOUT PROXIMITY SENSOR

using this method to import the xml file ended up removing all my custom tasker profiles, so if possible please share your profile using this method: https://tasker.joaoapps.com/userguide/en/sharecreation.html
Edit: also this seems like a duplicate of this thread that was locked by a moderator a couple of days ago : https://forum.xda-developers.com/t/closed-fix-proximity-in-call-malfunction-fix.4344539/

ticktock666 said:
using this method to import the xml file ended up removing all my custom tasker profiles, so if possible please share your profile using this method: https://tasker.joaoapps.com/userguide/en/sharecreation.html
Edit: also this seems like a duplicate of this thread that was locked by a moderator a couple of days ago : https://forum.xda-developers.com/t/closed-fix-proximity-in-call-malfunction-fix.4344539/
Click to expand...
Click to collapse
yes it was locked since i had hot talk with moderator on their "rules"

varunrocks17 said:
Congratulations guys I have created n tested highly advanced fully automated solution , now screen will work during calls as it should W/O NEED OF PROXIMITY SENSOR, WAIT FOR NXT RELEASE, TESTING.....
Warning :-
I AM NOT RESPONSIBLE FOR ANY DAMAGE WHATSOEVER YOU MAY CAUSE TO YOUR DEVICE WHILE USING OR RANDOMLY EXPERIMENTING WITH THIS FIX, DONT TINKER WITH DEVICE IF U DONT KNOW WHAT U R DOING.
1. What is this fix about?
Ans. Poco F3 has an issue, that while calling screen turns on/off randomly due to proximity sensor malfunction , so to fix it I made a Tasker profile which disables proximity sensor when call is continuing, and re-enable it when call is discontinued.
2. Why to re-enable proximity sensor?
Ans. Without proximity sensor phone will have issues with deep sleep function, so to avoid it proximity sensor is to be re-enabled.
3. Any draw back of this fix?
Ans. Yes, you have to manually turnoff and turn-on the screen during call.
4. Minimum requirements for this fix?
Ans. a. Tasker app
b. Any mi device which shipped with Android 10 or 11 out-of-box , if u have any other device u can test this fix if it works , most probably it would since m using sysfs interface shell script implimented by linux kernel, which is quite universal  both miui n custom roms are compatible;
c. Root;
d. Working mind 
5. PROCEDURE :-
0. Download the "proximity_fix2.XML" from below given link n copy it to "/storage/emulated/0/Tasker/configs/user" ;
1. Go to Tasker app;(all permission to Tasker app should already be given)
2. At the right corner of Tasker app u will see menu button (3 dot button) press it;
3. Go to "Data";
4. Go to "Restore";
5. Now select the "proximity_fix2.xml" that u have downloaded;
6. Press back button repeateadly till the app is closed;
7. That's it from here on my Tasker profile will take care of things;
6. Resources
A. XML file :-
proximity_fix2.xml
Backup from action
drive.google.com
7. What's next.
Probably u will have a very good workaround where by screen will act like it should during call WITHOUT PROXIMITY SENSOR
Click to expand...
Click to collapse
Hi , i have a Redmi Note 8 Pro my sensor is completly damage i want to lock it value at 5 forever so that the screen never turn black on a Phone Calls , how can i do it please ?