So i have a bug with the camera, when i open the camera app it's says:
"Cannot connect to camera."
I have flashed throught the flashtool the lastet firmware.(bootloader is LOCKED)
I have unlocked the bootloader and the camera worked great, so i have install LuPus and install NXT2JB.
after installation the camera back to the bug after few boots.
what i can do? and why it's happening ?
Go to Quick panel settings > widget buttons, untick "Toggle LED Flashlight"
Thanks. It's Working now
Hi everyone!!!
I have a problem with my LG G3 D858HK (stock MM 6.0 with Root) phone. For some reason (I think my cat dropped it) the proximity sensor always returns "Near" value. As the result when I am making a call the screen turns black and there is no way to unlock it unless phone call ends. I tried many things to disable proximity sensor such as:
1. Engineering menu - returns "Node value is null" when trying to disable the sensor.
2. Tried to find a driver for proximity sensor in /sys/bus with no luck.
3. Added to /system/build.prop string "gsm.proximity.enable=false" - didn't help.
Finally, I installed Xposed v80 framework with Sensor Disabler module and it helped. However there is a compatibility problem with some navigation and stock LG applications which is a known problem and unacceptable to me. I also tried Xposed version 78 and got bootloop which is also a known problem on LG devices.
So how I can disable the proximity sensor without using Xposed+Sensor Disabler? Maybe there is a way to edit some library/config file in android? Many thanks for your help, guys.
1. Ambient display error : Hand wave using Proximity sensor is working but Pick up using Tilt sensor isn't work perfectly
2. App download error : https://play.google.com/store/apps/details?id=com.naver.labs.translator
When I starting download this app in Playstore and then the system were forced to reboot.
This happened on both my old and replacement Note 7.
My fingerprint reader sensor & iris scanner is not working at the lock screen. Thought it might be a hardware issue, I set up a new Iris and fingerprint and worked fine. Samsung pay works too.
Thing I have tried:
- factory reset (issues returned after restarting the phone - no apps from Play Store installed)
- removing and adding new sets of Fingerprints & Iris
- wiping cache partition (from recovery) - I did notice a flash of error saying E:failed to mount /system (Invalid argument) before restarting normally
Then I also realized that my favorite feature - Quick Launch Camera is also disabled even with the option selected in the camera app
Tried Googling around but it seems like I'm the only one having such an issue.
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 ?