Themes / Apps / Mods [CLOSED][FIX] Proximity sensor fix - Redmi Note 10 Pro

PROXIMITY SENSOR FIX
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 :-
{Mod edit}
B. Tasker app
{Mod edit}

Related

[MOD] NFC Screen OFF (.206)

Hello,
Here I leave the NfcNci.apk modded in order to work even when the device is locked and screen is OFF
You don't have to worry about battery life, I have already tested it and it does not have any appreciable impact on it
IT MAY (SHOULD?) WORK WITH SONY XPERIA X TOO, though is untested (post here if it works for you)
Installation:
Download attached NfcNci.apk file
Overwrite it into /system/app/NfcNci.apk and chmod 0644 it
Delete /system/app/NfcNci/oat folder
Reboot or "svc power reboot" through ADB
Done
Click to expand...
Click to collapse
TESTED ON: Sony Xperia X Compact 34.2.A.2.69
UDPATE (22-08-2017):
-Now compatible with FTF build .206 (download NfcNci(.206).apk and rename it to NfcNci.apk)
If you are interested about modding it for your device, you can see what I did here:
https://github.com/bamsbamx/NFCScreenOFF
Is it possible to have a white list of what tag will be processed when the screen is off?
trewelu said:
Is it possible to have a white list of what tag will be processed when the screen is off?
Click to expand...
Click to collapse
I think there is no easy way to mod the system NFC APK to make it work like what you say. Instead, it would be possible to create an app that handles all NFC tags and override the functionality of those tags which aren't in the whitelist
Hi
Thanks for the mod.
I'm wondering if you've included support of taglost detection ?
And maybe : it is hard to have a mod for a detection on lock screen instead of "screen off" ?
For me a "screen off" detection is too annoying since my phone can be in contact with some NFC cards in my pocket/bag.
I was able to do it for android 5.x on my Z3 compact but it's a long time ago.. can't remember what I did back then
Le_Poilu said:
Hi
Thanks for the mod.
I'm wondering if you've included support of taglost detection ?
And maybe : it is hard to have a mod for a detection on lock screen instead of "screen off" ?
For me a "screen off" detection is too annoying since my phone can be in contact with some NFC cards in my pocket/bag.
I was able to do it for android 5.x on my Z3 compact but it's a long time ago.. can't remember what I did back then
Click to expand...
Click to collapse
Hi,
I dont know what do you mean by "taglost detection", but this mod is based on the SONY's stock rom NFC app, so it should be included if it's also in the original app.
I think adding just on-lock-screen detection should be hard, you can follow the quick guide I wrote here: https://github.com/bamsbamx/NFCScreenOFF/blob/master/README.md
But keep in mind if you want just lock screen you should set .field static final NFC_POLLING_MODE:I = 0x2 instead of .field static final NFC_POLLING_MODE:I = 0x1
I cant test by myself that way because I am using AOSP rom right now... But will help you if you need
bamsbamx said:
Hi,
I dont know what do you mean by "taglost detection", but this mod is based on the SONY's stock rom NFC app, so it should be included if it's also in the original app.
Click to expand...
Click to collapse
By default there's no tag lost detection.
The tag_lost detection allow to trigger action when the tag is removed, not only when the phone scan the tag.
For ex you can use this to set the phone in a particular state (commonly: car mode, desk mode, etc) while the tag is detected. When the tag is removed, you use the tag_lost trigger to get off the mode, or trigger any other action (with tasker for ex)
I just got my X compact, and still not rooted yep. At this time I'm trying to use it without root... but the nfc mod my push me to do it
If so I'll take a look at this and post here
Please support 34.3.A.0.238 ?
On my phone, introducing this will cause nfc to disappear.

Screen Dimming Temporary Fix

After Oreo update, it seems there's annoying bug/feature that automatically dims my screen when using camera, Facebook, chrome, pubg mobile etc.
I tried one temporary solution for that bug which actually works on my Huawei P10.
Let me know it this solution will work on your devices.
1. Turn-off Power Saving Mode
2. Go to Go to System>Developer Options>Increase Readability Under Sunlight> Toggle Off
3. Then restart and check your apps if it still auto dimming
And if you want permanently freeze or delete power genius...that solved my problem.
But I think because I delete it now in my power usage, software ia not showing...just hardware.
I dont know if its because I delete that or was a bug that I didn't notice))
where is developer options?
_totep said:
After Oreo update, it seems there's annoying bug/feature that automatically dims my screen when using camera, Facebook, chrome, pubg mobile etc.
I tried one temporary solution for that bug which actually works on my Huawei P10.
Let me know it this solution will work on your devices.
1. Turn-off Power Saving Mode
2. Go to Go to System>Developer Options>Increase Readability Under Sunlight> Toggle Off
3. Then restart and check your apps if it still auto dimming
Click to expand...
Click to collapse
where did you find developer option. I have huawei p10 with oreo 8. No developer options
anatolee said:
where did you find developer option. I have huawei p10 with oreo 8. No developer options
Click to expand...
Click to collapse
Got to settings-system-about phone and press approximately 8 times on build number. Then developer options will appear.
developer options
thank you very much. it works :good:
Possible solution !!
After hours of "annoyance" in developer options changed that and it works!!
No more auto Dimmer !!
https://ibb.co/hS0QxU[/IMG]
Thanks for all support
hello. I do not know why but it does not help me. only locking and then re-unlocking the screen restores the normal backlight and does not dim afterwards.sorry no good English.use Google translator. Olo
it doesnt help for me. any ide of this???
Works on my P10. Thanks!
Doesn't work on my Huawei Nova 3i
It seems that Velis Auto Brightness app from Google Play Store does the trick (Honor 10 Stock Pie).
Settings:
Automatic brightness: ON
track light in graph: ON
SETTINGS: (advanced):
Automatic brightness: ON
Disable system handler: ON
Start when screen turns ON: ON
Interactive notification: ON
All other settings off/default.
When you turn off the screen and turn it on, go for the first time in notification area and set your desired value in Velis.
Turn off automatic handling of this app in battery section (app start).
If you disabled animations in developer options, enable them again (0,5x for exanple) and see the magic.
NO more dimming at all.
Hi - I see this thread was originally written 2yrs ago, but I currently have this 'screen dimming in app' problem with my P10 Plus. It started in the last couple of months and may be related to a software update - I'm currently on EMUI 9.1.0.
The Developer option on this thread unfortunately didn't resolve the problem for me (perhaps that's not longer relevant now).
Can anyone offer any other advice?l to resolve this?
Thanks.

[GUIDE] Force 90Hz for almost every App/Game (Uncaps FPS)

Oneplus 7 Pro
Force 90hz Refresh Rate in almost every App (and Games)
*also uncaps FPS (since Vsync is on by default for Android)
Requirements:
1. A Windows PC (Windows 10 64 Bit is preferred)
2. Oneplus Drivers
3. A USB Type-C Cable
4. Your Oneplus 7 Pro
Steps:
1. Plug in your Oneplus device and select File Transfer mode in your phone's notification selection, then open My Computer and you will see the drive for Oneplus Drivers.
2. Install Oneplus Drivers (you may be prompted to reboot afterwards). You may need to plug and unplug the device to finish driver recognition. Unplug your phone once it is finished.
3. In your phone, go to Settings > About Phone, and tap Build Number multiple times in fast succession until the message "you are now a developer" appears.
4. Go to Settings > System > Developer Options, and turn on USB-debugging.
5. Go to Playstore and download jOnePlus Tools
6. Plug your device in your PC.
7. Anywhere on the empty desktop of your PC, press shift + right click, and select "Open Powershell window here"
8. Wait for Powershell to load
9. Type "adb shell" without the quotes
10. A permission prompt will appear in your Oneplus 7 Pro's screen, allow it.
11. Type "adb shell" once again and press Enter, and you should see your device like this "Oneplus7Pro:/ $"
12. Type or copy-paste the text below without the quotes:
"pm grant net.jroot3d.joneplustools android.permission.WRITE_SECURE_SETTINGS", and press Enter.
13. Once you've entered that, it should repeat what you've typed in the next line.
14. Unplug your device, and open jOnePlus Tools app.
15. Tap Screen Refresh Rate and select Force 90Hz
16. Congratulations, you are done! To confirm, you can go to Settings > Display > Screen Refresh Rate and you should see it as 60Hz from the outside, but when you tap it, you will see that nothing from the 2 choices is selected. It means you are using the 3rd Hidden Setting.
Tip: You may need to reselect Force 90 Hz from the jOnePlus Tools if you have selected 90hz or 60hz from the settings.
Note: This will enable 90hz (and up to 90 fps) for apps and games, unless the app itself has an even stronger FPS-controller then it will tone-down the FPS to the standard set by that game. But for most games without an FPS controller or 30-FPS-locked games without an in-game FPS-controller, it will work 100%.
Credits:
C3C076 (XDA Developer, Dev of GravityBox)
JRoot3D.dev (jOnePlus Tools Developer)
Guide Maker: Ares (Freyelis - XDA Senior Member)
RIP Battery Life?
stanley08 said:
RIP Battery Life?
Click to expand...
Click to collapse
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Maybe I will
stanley08 said:
Maybe I will
Click to expand...
Click to collapse
Enjoy better gaming man. Try it on Assassin's Creed: Identity too, that game has awesome graphics but was locked at 30 FPS... Not anymore
Freyelis said:
No, try it. The brightness and resolution actually kills more battery than the refresh rate, so set the reso to dynamic, and the brightness to less than 50% always.
Click to expand...
Click to collapse
Anyway to set auto brightness but less than 50% always ??
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
if i restart my phone will the settings i made gone?
se7ensde said:
Or you could simply use Smurf kernel which already has this in the config and stays set through reboots. Or just use the original method from C3C076 which sets it permanently no need for this extra stuff or to have joneplus tools constantly in background for no reason...
Click to expand...
Click to collapse
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
bubu23 said:
if i restart my phone will the settings i made gone?
Click to expand...
Click to collapse
No
Xalph92 said:
Anyway to set auto brightness but less than 50% always ??
Click to expand...
Click to collapse
Either set it manually, or use YAAB app as a replacement for auto brightness, which you can set the maximum ang minimum brightness.
virtyx said:
9 hrs SOT? @op do you have qhd or fhd?
Stock kernel? Any mods?
Click to expand...
Click to collapse
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Just for information, my kernel config has a switch to apply 90Hz, auto or 60 HZ.
Gesendet von meinem xXx_NoLimits_7.1 on GM1913 mit Tapatalk
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Freyelis said:
Dynamic, stock kernel.
No mods, I just control every background app using built-in background restriction, deepclear, and deep battery optimization.
Click to expand...
Click to collapse
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
thanks!
thanks!!!so after doing this im rooted already?because jtools need root right?
Freyelis said:
Adb method from C3C076 resets after every reboot, that's why I made this tutorial for those unrooted people who wants to make the setting stick.
Click to expand...
Click to collapse
Stays through reboots for me... And like I said there are easier simpler and faster ways to achieve this without need of all this extra stuff. Smurf kernel already implemented this in his config so it stays like that too. And C3C076 had made qs tiles for this. I've been using his method for over a week now through several reboots no issues.
C3C076 said:
Did you actually test it? "ADB shell settings global put" command changes user settings that are stored in the filesystem and are thus persisted across reboots until explicitly changed by the user.
Click to expand...
Click to collapse
Sorry, thanks for the clarification sir, great work as always, will revise this one
virtyx said:
Have you restricted system apps too? Did you do this for each app one by one?
Do you have a list of what you've restricted
Click to expand...
Click to collapse
I did not restrict system apps, only the apps that I installed. Apps that I need notifications from such as Telegram, is not included in the restriction. All other apps are, like games, editors, etc..

[CLOSED[FIX] PROXIMITY SENSOR FIX

PROXIMITY SENSOR FIX
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 :-
{Mod edit}
B. Tasker app
{Mod edit}

General GSI issues and issue fixes

Here's a common list of GSI issues:
1. LTE is not selected as preferred by default.
Solution: Simply change the preferred type from 3G to LTE in SIM settings.
2. Bluetooth headphones don't work out of the box.
Solution: phh treble settings → misc features → other → Use System Wide BT HAL.
3. The light sensor isn't detected, breaking auto brightness.
No fix. Reported to TrebleDroid (https://github.com/TrebleDroid/treble_experimentations/issues/32)
4. The NFC service crashes when scanning certain types of cards.
No fix. Should be reported to TrebleDroid. Rebooting restarts the service
Contactless payments should work.
5. Double tap to wake (DT2W) doesn't work.
Workaround: Use Always-On Display (AOD) instead. This is likely caused by a kernel issue.
6. Biometrics are broken.
Workaround for Face Scan: https://github.com/null-dev/UniversalAuth.
Otherwise, no fix. Reported to TrebleDroid (https://github.com/TrebleDroid/treble_experimentations/issues/39).
7. Apps can't aquire wakelocks
Another issue related to sepolicy. Use the attached `wakelocker` module.
8. VoLTE is very janky
No fix. https://forum.xda-developers.com/t/realme-8-pro-gsi-overlay.4589267/post-88577935
9. Widevine is L3
No fix.
10. Jittery UI.
After ~1 hour after setup everything should be back to normal. If that doesn't work, try the attached `fast_gui` module. All this module does is set `debug.sf.latch_unsignaled` to 1.
11. AOD not working, the auto brightness button is missing, the punch hole is covered by a black square, incorrect power profile, and other problems.
To address these issues, flash the Magisk module provided in this forum post: https://forum.xda-developers.com/t/realme-8-pro-gsi-overlay.4589267/
If AOD still doesn't work, or even breaks with this overlay, (hi Project Elixir) install the attached AOD-12 magisk module.
If you encounter any other issues, please report them here, and I'll add them to the list!

Categories

Resources