Hello everyone,
My sensor went bad after screen replacement. It always detects as near. Until now I was using xposed to disable it. But now after upgrading to Android N, I don't have xposed and I don't know how to fix it.
The screen is turned off when I make/attend a call, making it difficult to end.
Is there any config file or something in source where I can disable it??
Thank you.
You can use settings>accessibility>Use power button to end call...
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
swapnil0545 said:
Thanks. I am doing what you said now. But still it would be better if I get and solution to disable it.
Click to expand...
Click to collapse
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
The solution for that it change the black thing make the bigger hole on sensor of light and the small one with other
Default for that is small one with sensor light and bigger one for something else
So sorry for bad language see that steps here
http://forum.xda-developers.com/nexus-4/help/proximity-sensor-fix-screen-replacement-t2657176
ze7zez said:
I have not tested in N, but it works in MM.
Copy android.hardware.sensor.proximity.xml the known position and change its string
Code:
<feature name="android.hardware.sensor.proximity" />
to
Code:
<feature name="" />
Go to the TWRP.
Mount the partition system.
Check the permission and assignment to groups for file android.hardware.sensor.proximity.xml
Rename the file android.hardware.sensor.proximity.xml
Copy the changed file android.hardware.sensor.proximity.xml to the /system/etc/permissions
Change the file permission and assignment to groups that have the original file.
Reboot.
Click to expand...
Click to collapse
I am going to try this. I hope I don't soft brick it.
swapnil0545 said:
I am going to try this. I hope I don't soft brick it.
Click to expand...
Click to collapse
Hey did you get it to work?
I've tried - no, did not work on 7.1.
Have you any other solution? I've the same issue on nexus 6p After display replacement. And now on nougat i can't fix it. Simeone Can help me?
My other solution was to recompile Dialer.apk with proximity disabled.
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Where is the apk located? I'm running 7.0 and cannot find it in the system/apps folder.
On CM14 it is in /system/priv-app/Dialer/
digital0 said:
My other solution was to recompile Dialer.apk with proximity disabled.
Click to expand...
Click to collapse
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
You are a life saver
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7 ?
sweetmyke said:
You just helped me with the biggest inconvenience on my phone. I used sensor disabler on xposed but this is a perfect fix for a broken proximity sensor and android 7
Click to expand...
Click to collapse
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
driftking132 said:
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Click to expand...
Click to collapse
You should run these commands on a PC, to which phone is connected by USB cable.
digital0 said:
Just FYI how it was done - http://forum.xda-developers.com/showpost.php?p=69507586&postcount=253
Click to expand...
Click to collapse
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
I've attached my version of the fix that I've been running since CM13, now recompiled for CM14.1. There's effectively only one line of code changed. Source is up-to-date to Feb 6, 2017.
As far as I can tell, digital0's version works just as well, so there's no reason to try mine if you're not having issues with his.
Same way to install the apk. Attached diff for the curious.
Shimakaze said:
Just out of curiousity, what was the reason to comment out the ALTER TABLE line in DialerDatabaseHelper.java?
Click to expand...
Click to collapse
The CM build I used at the time of compiling gave the error. It is most probably not needed now.
driftking132 said:
hello sir
I have this issue in my nexus 6 and want to disable Proximity Sensor but without Xposed Installer Framework for Android 7,I couldn't.
would you please tell me how did you use this Compiled App????
I don't know how I have to run these command:
adb root
adb remount
adb push Dialer.apk /system/priv-app/Dialer/Dialer.apk
Thank You.
Click to expand...
Click to collapse
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
sweetmyke said:
Sorry for taking so long to respond but I just used root explorer system/priv-app/dialer and replaced dialer.apk. Make sure that you set the permissions to rw-r-r...reboot, let me know if I helped
Click to expand...
Click to collapse
its worked but in call screen there is no answer/ reject buttons please fix this
Related
Hello to all devs
If someone can help me I would be very gratefull.
What I`m trying to do is to edit the values for screen brightness in framework-res.apk .
The problem is that after decompiling ,edit the values (values/array.xml) ,compiling and push to system/framework, after reboot the phone won`t boot anymore.It just stucks at the finish of the bootanimation.
So...please...can someone help me?
Do you get any warnings/errors while compiling? You could also try vrtheme instead of modding the apk.
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Do you get any warnings/errors while compiling? You could also try vrtheme instead of modding the apk.
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
I installed the miui framework and other dependecies and succsessfully compile a new framework-res.apk.
The problem is that after I push the modded framework to system/framework and reboot the system won`t boot anymore.I don`t like how MIUI Team set the values for brightness.It`s too dark for me.And I wanted to "light" the display without any 3rd app from market.
aresbv2000 said:
I installed the miui framework and other dependecies and succsessfully compile a new framework-res.apk.
The problem is that after I push the modded framework to system/framework and reboot the system won`t boot anymore.I don`t like how MIUI Team set the values for brightness.It`s too dark for me.And I wanted to "light" the display without any 3rd app from market.
Click to expand...
Click to collapse
Did you set permissions after pushing? Making a flashable zip may be a good idea.
Sent from my Nexus⁴ using Tapatalk 4 Beta
TToivanen said:
Did you set permissions after pushing? Making a flashable zip may be a good idea.
Sent from my Nexus⁴ using Tapatalk 4 Beta
Click to expand...
Click to collapse
The permissions were set like this:
adb shell
cd system/framework/framework-res.apk
chmod 644 framework-res.apk
Before restart i`ve checked if the permissions were right and they do.
I don`t know where the problem is
aresbv2000 said:
The permissions were set like this:
adb shell
cd system/framework/framework-res.apk
chmod 644 framework-res.apk
Before restart i`ve checked if the permissions were right and they do.
I don`t know where the problem is
Click to expand...
Click to collapse
Hm, seems fine to me.
Can you please upload the modded apk and tell me which file you edited? Imma make a vrtheme zip for you to try.
Sent from my Nexus⁴ using Tapatalk 4 Beta
Here is the two files (framework-res.apk and framework-miui-res.apk). If you have free time and want to give a try,maybe you will manage to do it right.Edit anything in the values/array.xml and I will test to see if it works.
framework-res.apk
framework-miui-res.apk
I run on my laptop Windows 7 x64.Maybe this is the problem.But if the compiling is fine...i think this is not the problem.Maybe the signature of the apk or something like that would be the problem.
Thank you for your interest.
@aresbv2000
Here you go
The zip does not replace the entire apk. It sorta injects the arrays.xml into frameworks-res.apk. I've set every auto brightness step to 250 in order to easily find out if it works. If your screen lights up 100% after enabling autobrightness, the zip worked.
Then you must open the zip using and replace my proof-of-concept arrays.xml with your own.
Cheers!
TToivanen said:
@aresbv2000
Here you go
The zip does not replace the entire apk. It sorta injects the arrays.xml into frameworks-res.apk. I've set every auto brightness step to 250 in order to easily find out if it works. If your screen lights up 100% after enabling autobrightness, the zip worked.
Then you must open the zip using and replace my proof-of-concept arrays.xml with your own.
Cheers!
Click to expand...
Click to collapse
ok....thank you so much.i will install the zip as you made it.i will report to you if it worked.
please if you have time check this thread later to see if i posted any question for you.
thank you again
it is not working my friend
the screen stays the same as usual....too dimm.
i don`t know why but if i use velis autobrightness it seems that the color tones are changing also.and i spent a week just to calibrate my display the way I like it .thank you so much for your effort.i appreciate your efforts.
After a few hours and a lot of nervs i`ve succsessfully edited the values in array.xml, compile....and VOILA>>>it worked.
It took me some time to figure out what values should I set, but now is way better than was before.
All the credis goes to this and to you for your tips.
Thank you.
Forum moderator can delete this thread as the problem is solved
aresbv2000 said:
After a few hours and a lot of nervs i`ve succsessfully edited the values in array.xml, compile....and VOILA>>>it worked.
It took me some time to figure out what values should I set, but now is way better than was before.
All the credis goes to this and to you for your tips.
Thank you.
Forum moderator can delete this thread as the problem is solved
Click to expand...
Click to collapse
Sweet. I'm glad you figured it out
Sent from my Nexus⁴ using Tapatalk 4 Beta
Has anyone received N900VVRUBMJE yet?
Not yet. I wonder if it will break root and the free Wi-Fi tethering
Sent from my SM-N900V using Tapatalk
iceman6996 said:
Not yet. I wonder if it will break root and the free Wi-Fi tethering
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
One of the mentioned updates on the little graphic for the update was "Mobile Hotspot reliability has been improved" , so I'll be very surprised if the Home button trick still works
I'm very much looking forward to better Cellular reliability. With MJ7, I often can't make a call. No signal whatsoever. If I change to MI9, I have much better reception and reliability. Not great but much better. I'm hoping MJE will be great. Fingers crossed!
What home button trick? Sorry for the noobiness...
MrWilliams2 said:
What home button trick? Sorry for the noobiness...
Click to expand...
Click to collapse
When you start the mobile hotspot and youre not subscribed it pulls up an error box telling you to subscribe. You just hit the home button and it goes away and the hotspot still stays on and works
NeoMagus said:
When you start the mobile hotspot and youre not subscribed it pulls up an error box telling you to subscribe. You just hit the home button and it goes away and the hotspot still stays on and works
Click to expand...
Click to collapse
Even if VZW fixes Hot Spot, there is a Tether patch available that will allow the hot spot to bypass the subscription check. Runandhide05 made up a .zip yesterday for the N2 running 4.3 and it works flawless.
Does this zip work for non-root, or only rooted N3s?
Cheers,
B.D.
droidstyle said:
Even if VZW fixes Hot Spot, there is a Tether patch available that will allow the hot spot to bypass the subscription check. Runandhide05 made up a .zip yesterday for the N2 running 4.3 and it works flawless.
Click to expand...
Click to collapse
Have a link to this zip? apparently the update did kill the home button bypass
Did you get the update?
NeoMagus said:
Have a link to this zip? apparently the update did kill the home button bypass
Click to expand...
Click to collapse
I got it a few minutes ago. Too soon to tell if there are any improvements.
I took the ota with root survival mode checked on the Super su pro app and kept root just fine..I first unistalled xposed and modules, defrosted the bloat I had froze with titanium, checked ota survival mode with Super SU Pro (Paid Version) while keeping root enabled, Rebooted, took OTA and it works fine while maintaining root.....to early to notice any improvements but I have notice spell checker is enabled on the Samsung keyboard...+1!
Sent from my VZW Note3..ha..ha..
I get an error while its trying to update on my stock slot following jankers method
Sent from my SM-N900V using Tapatalk
NeoMagus said:
One of the mentioned updates on the little graphic for the update was "Mobile Hotspot reliability has been improved" , so I'll be very surprised if the Home button trick still works
Click to expand...
Click to collapse
It will not work since the patch is tied into the frame work. Will need a dev to pull the update and apply the patch.
So I can enable keep root and safely update?
Sent from my SM-N900V
droidstyle said:
It will not work since the patch is tied into the frame work. Will need a dev to pull the update and apply the patch.
Click to expand...
Click to collapse
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Thanks for this. How would I modify my own file instead of copying yours?
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Worked great! Thanks!!!
Surge1223 said:
Modded it already, its been tested and confirmed working by open1your1eyes0. Download here
you have to rename it to framework-res.apk.
Edit: I assume you know you have to either flash this with a zip or copy it to /system first then change its permissions to rw-r--r-- (chmod 644) and then MOVE it to /system/framework and overwrite framework-res.apk (remember must rename N3-framework-res.apk to framework-res.apk prior to this step)
Simply copy and pasting will cause you to boot loop so instead move it to /system first and change the permissions then and only then move it to /system/framework/ and overwrite the original
Click to expand...
Click to collapse
Thanks for posting this, you kick ass! I have one question, I thought that KNOX worked in such a way that modifying anything in System could result in bad news for the KNOX fuse.. Just wanted to confirm, this didn't trip it on your device and shouldn't on mine?
Thanks again for posting this.
razzbaronz said:
Thanks for this. How would I modify my own file instead of copying yours?
Click to expand...
Click to collapse
Modify framework-res.apk with apktool
bschrib said:
Thanks for posting this, you kick ass! I have one question, I thought that KNOX worked in such a way that modifying anything in System could result in bad news for the KNOX fuse.. Just wanted to confirm, this didn't trip it on your device and shouldn't on mine?
Thanks again for posting this.
Click to expand...
Click to collapse
Didnt trip it. You should be good
Sent from my SCH-I545 using XDA Premium 4 mobile app
This solution works for anyone that doesn't want to root their device.
however required a unlocked boot loader.
you can use TWRP file manager to replace below files. (hence not needing root).
(or someone can kindly create a flashable)
I have recomplied the power.shamu.so (replacing the missing codes from https://android.googlesource.com/device/moto/shamu/+/2084f7d0cf50baf394759d175bc28ad80cf7cace^!/ )
What this does is also re-enable the double-tap to wake.
to use,
backup a copy of
/system/lib/hw/power.shamu.so
then copy the attached power.shamu.so to /system/lib/hw/
change the permission of power.shamu.so to 0644
then boot your device. volia... you now have double tap to wake again.
Note. this has been tested with my own nexus 6.
Thanks. I think this would be better in themes n apps section though.
Thank you Sir! I'm going to remove the app and try this on Elix-R!
EDIT: Works great! Thank you again.
Which permissions are 0644?
smalltownbird said:
Which permissions are 0644?
Click to expand...
Click to collapse
User: R,W
Group: R
Other: R
Thanks that's what I thought I just wanted to make sure
Can I just flash the zip file that's in the beginning of the thread? Also would I need to re-install after wiping and flashing different roms or will it stay?
Figured it out.
No Worky on Slim
mr_clean5953 said:
No Worky on Slim
Click to expand...
Click to collapse
Working fine here. You probably never set permissions
suzook said:
Working fine here. You probably never set permissions
Click to expand...
Click to collapse
I did. And triple checked it
mr_clean5953 said:
I did. And triple checked it
Click to expand...
Click to collapse
Strange working here on beta 8
suzook said:
Strange working here on beta 8
Click to expand...
Click to collapse
I redownloaded and reloaded the file and its working fine now
Awesome
.....working like charm....
Sent from my Nexus 6 using XDA Free mobile app
Working great here!!! Thank you.
Stock ROM...
Sent from my Nexus 6 using Tapatalk
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
You can do it from recovery which has system access even if the ROM doesnt have root privileges.
What I am wondering though is if you can use fastboot to simply boot recovery without flashing it, and would you be able to do that command without unlocking the bootloader? Or does booting a custom system file require it to be unlocked?
BeansTown106 said:
nice, although no root required makes no sense considering you have to copy and paste this to /system that requires root... or am i missing something?
Click to expand...
Click to collapse
Idea is just like rooting.
You need to some how replace the power.shamu.so once, and thats it.
Some people dont like phones to be rooted, as some software are really particular with root such as 'good for ent' or banking app. Idea is so that these people can still have doible tap to wake.
Hence you require a unlocked boot loader.
Eg, i guess i can also repack the file to a flashable zip, then user can just flash from recovery.
Note, i found that your tap needs to be quite consistant (can't be too fast or slow. There is a specific window)
what about pocket detection? (proximity sensor)
antiochasylum said:
what about pocket detection? (proximity sensor)
Click to expand...
Click to collapse
Don't think there is such feature. One you Mentioned is ambient display which I choose to switch off. As I believe it might detect lots of false pick up.
Awesome! Works great!
Stock rom
Sent from my Nexus 6 using Tapatalk
I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp
The setting does not stick after the reboot. You have to enable it and disable it again. Then it should be really disabled until the next reboot.
Okay, thank you. I hope they will fix it soon
I think it may be because you flashed a custom kernel.
Some custom kernels break dt2w
barni090 said:
I've installed the newest Lineage OS, but I want to turn of "Double Tab to wake". But after one day, it automatically turned on again, but without showing it in the settings (showed that it's turned of). Now I have the question if there is any possibility to turn it off?
Thanks,
Philipp
Click to expand...
Click to collapse
Until they fix this you can use a script to disable it. Use init.d or any automate app to run the script at boot. It'll turn off the tap2wake.
#!/system/bin/sh
tap2wake=/proc/touchpanel/double_tap
echo "0" > $tap2wake
could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do
barni090 said:
could you maybe tell me how to use this command? Sorry for that, but I am new in that and don't know what to do
Click to expand...
Click to collapse
Since you're new to this I'll give you the easiest way to do this.
1. Download the script from the link given below. (or use my last post's code to make a script yourself)
2. Put it in a folder in sdcard.
3. Install 'init.d scripts support' app from play store.
4. Open the app & tick 'try to aquire root privileges'. Grant root access.
5. Tick 'run scripts at boot time' option.
6. Set 'execution delay' to a desired time.
7. Select the folder you put the downloaded file.
Tap2wake disable script - http://www.mediafire.com/file/r4h5z8p1ez21jpi/tap2wakedis.sh
Done. Now every time you reboot, app will execute the scripts in the selected folder which contains our script to disable double tap2wake.
You can always execute the script using ini.d, su.d, tasker, macrodroid etc.
I have some problems with activating it, I've put the error message as attachment maybe you could look over it.
barni090 said:
I have some problems with activating it, I've put the error message as attachment maybe you could look over it.
Click to expand...
Click to collapse
I forgot to change the line ending to Unix. I edited the post check it again.
It's still not working, I used another app and it's telling me permission denied. But thank you for your help
barni090 said:
It's still not working, I used another app and it's telling me permission denied. But thank you for your help
Click to expand...
Click to collapse
Try the link again this time it should work. lol. I've added /bin/bash not /bin/sh. old habits. If you're using a terminal issue 'su' first then 'sh SCRIPT_PATH'.
worked now Thanks so much :victory:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Nikish21 said:
Ok thanks I will try it today evening
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
Best of luck. :good:
Would it work with los stock kernel?
impulsar said:
Would it work with los stock kernel?
Click to expand...
Click to collapse
No idea. I am using vegito kernel v7
riazul.islam20 said:
No idea. I am using vegito kernel v7
Click to expand...
Click to collapse
Vegito kernel by default supports dt2w right?
impulsar said:
Vegito kernel by default supports dt2w right?
Click to expand...
Click to collapse
Might be. But by default it was inactivated.
Is it possible to add screen of gestures in lenovo vibe k5
Is it possible to lock device by double taping...Just like dt2wake??
jometzz said:
Is it possible to lock device by double taping...Just like dt2wake??
Click to expand...
Click to collapse
Why not?
Just double tap on statue bar
riazul.islam20 said:
Another tweak I found to wake your Lenovo Vibe K5 Plus simply by double tapping the screen.
To activate this:
1. You must have rooted phone.
2. File manager with root access.
Method:
1. Go to root/sys/ANDROID_TOUCH.
2. Open doubletap2wake with any text editor.
3. Change the value "0" to "2".
4. Save.
5. Restart your phone.
6. Done
Hit "Thanks" if worked.
Click to expand...
Click to collapse
It gets reset to 0 on reboot. Why?
afzalsayed96 said:
It gets reset to 0 on reboot. Why?
Click to expand...
Click to collapse
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
#!/system/bin/sh
echo 2 > /sys/android_touch/doubletap2wake
Click to expand...
Click to collapse
Android_touch
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Goutham47 said:
There is no ANDROID_TOUCH folder.
I use pixel experience (8.1.0) ROM, 3.10.108 kernel(came with the ROM), solid explorer that you use.
Please help me!!
Click to expand...
Click to collapse
the same here, please help
Please someone who says the correct way to do the procedure in Rom AOSP or LineageOS in 7.1.2
Someone using dt2w on oreo? Please share info if there's a way to activate it under oreo
nonline said:
Because why not, but I found a solution.
Init.d support is needed. Probably on every custom rom this feature is working out of the box, but there is an easy way to get it on rooted stock.
How to get Init.d working? Follow this guide https://forum.xda-developers.com/showthread.php?t=1933849.
Download attached "enable_doubletouch2w.zip"(yep I f*** the filename ), extract it anywhere, copy extracted file to your phone internal storage (e.g sdcard).
Now, copy/move (whatever) it to the /etc/init.d., set correct permissions (same as other scripts in the directory) and voila. I used Root Explorer Classic.
So, on every reboot script will run and change value from 0 to 2 in /sys/ANDROID_TOUCH/doubletap2wake
Script itself:
Click to expand...
Click to collapse
bro...i m getting endless boot animation...what to do...??? plzz help