Database Info

Command to turn on USB debug

So on my tablet, there is no option in "Application Settings" to turn on USB debug.
I have root and su access and a terminal.
Is there a command in terminal I can issue to turn USB debug on?

On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App

Bingo! That got me going.
Ran that command as 'su'
It didn't come back with any errors, so I assumed it worked.
Plugged into the computer, said recognize device. Listd it as a <NULL><NULL> USB Device.
Go to my My Computer, and it shows an E: drive, but cannot open it. I select to Mount my USB in the notification area and now I can see my SD card.

The code
mercianary said:
On my phone its saved at
/data/property/persist.service.adb.enable
Maybe its the same on your tablet?
Edit: If its in the same place this command should work.(not tested - use at own risk! - worst case scenario...wipe data).
echo 1 > /data/property/persist.service.adb.enable
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
_______________________________________________________________________________________________________________________
Where did you find where that is saved?

Wow! mines located there too and I can change to 1/0 by editing it through text editor program

just so you guys know. what seemed to work for me was to
go to about phone or tablet under settings
scroll to bottom where it shows build number
tap build number 7 times
developer window now shows. This works in android 4.2

This works from a terminal emulator (with root permissions) and from TWRP or any other terminal supporting recovery:
WARNING
Only use this method if you are sure the property files are located under /data/property/...
Enable adb functions:
Code:
echo 1 > /data/property/persist.service.adb.enable
echo 1 > /data/property/persist.service.debuggable
echo adb > /data/property/persist.sys.usb.config
Disable adb function:
Code:
echo 0 > /data/property/persist.service.adb.enable
echo 0 > /data/property/persist.service.debuggable
echo mass_storage > /data/property/persist.sys.usb.config
If it worked for you, a thank you is always appreciated!

Get more RAM and faster responses by disabling verify-bytecode!

Here's a little tip that would give you more RAM on your device.
AS WITH ANY MODDING PROCEDURE FOR YOUR PHONE, THIS GUIDE ALSO COMES WITH NO WARRANTY. AUTHOR HOLDS NO RESPONSIBILITY FOR ANY DIRECT AND INDIRECT CONSEQUENCES OF FOLLOWING THIS GUIDE. MAKE SURE YOU HAVE MADE A NAND BACKUP BEFORE PROCEEDING.
This is not useful in odexed ROMs & devices with 1GB or more RAM. However, this will give a performance boost in deodexed ROMs as much as odexing system & data apps. This is an alternative for odexing. It's not that you can't apply this tweak on an odexed ROM but rather, it's useless to do so.
1) Open Terminal Emulator on phone or adb shell from PC and type the following.
su
setprop dalvik.vm.verify-bytecode false
setprop dalvik.vm.dexopt-flags v=n,o=v
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
2) Add these to the /data/local.prop or build.prop.
dalvik.vm.verify-bytecode = false
dalvik.vm.dexopt-flags=v=n,o=v
(Copy local.prop or build.prop to SD and edit them. Copy back afterwards. If lines starting with dalvik.vm.verify-bytecode or dalvik.vm.dexopt-flags exist already, please modify them as above. Also type following in adb shell or terminal emulator.
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot
Advantages:
More free RAM.
Faster launch for system & user apps during the second launch.
Gives as much as of a performance boost as ODEX without odexing. Themer friendly.
Smoother app switching.
Disadvantages:
Might break some apps.
You can read more information about this on here and here.
Thanks to Danzano for testing this tweak in advance.
Reversing the change/undo tweak.
Type the following in shell.
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot

Wow. Will try it
Sent from my GT-I9100 using XDA App

GadgetCheck said:
Wow. Will try it
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
SGS2 has 1GB RAM. That's a lot. This tweak is more useful in devices with 256-512MB RAM.

Yeah I know!!
But trying dosen't hurt!
Sent from my GT-I9100 using XDA App

GadgetCheck said:
Yeah I know!!
But trying dosen't hurt!
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Thanks. Looking forward to your feedback. =)

Sounds really awesome, probably would try it. hmm... one concern, would it mess the os config.?

skydeve said:
Sounds really awesome, probably would try it. hmm... one concern, would it mess the os config.?
Click to expand...
Click to collapse
OS config in the sense? If you are talking about parameters given to Android in build.prop and stuff like that, it is both an yes and no.
bytecode-verify is an important dalvik-vm parameter and so, it will change the OS config for byte-code verify ONLY. Other parameters will not change.
You can undo this with,
su
setprop dalvik.vm.verify-bytecode true
rm /data/dalvik-cache/*
rm /cache/dalvik-cache/*
reboot

Someone knows of this work?
Sent from my HTC Bliss using XDA Premium App

Could you create a script to apply this fo the less proficient in these matters such as me?
Thanks for sharing! Great job!!

What about the start and stop command?

it's good for htc Sensation ?? sensation have 768MB RAM

eterno13 said:
Someone knows of this work?
Sent from my HTC Bliss using XDA Premium App
Click to expand...
Click to collapse
Worked for me and Danzano. Try it and post your results.
VeEuzUKY said:
Could you create a script to apply this fo the less proficient in these matters such as me?
Thanks for sharing! Great job!!
Click to expand...
Click to collapse
Hmm, only 5 lines of code? Open up terminal emulator and type the 5 lines starting with SU and ending with reboot.
fLipz said:
What about the start and stop command?
Click to expand...
Click to collapse
Huh?
---------- Post added at 11:20 PM ---------- Previous post was at 11:19 PM ----------
-juanito- said:
it's good for htc Sensation ?? sensation have 768MB RAM
Click to expand...
Click to collapse
Not sure. Give it a go. You can easily undo.

Might try this on my G2 - can't hurt to try for a bit.
Just wondering exactly what verify bytecode does for the dalvik-vm. Is it there to ensure data integrity, checking for errors and such? Is it sort of like what ECC is for RAM but for the dalvik-vm?

no dalvik.vm.verify-bytecode here
Hmmm, I think I dont have that prop here... getprop dalvik.vm.verify-bytecode returns nothing to me. Imediatly after boot caches come back and grow...
This is after a reboot
Code:
~ # du -hs /cache/dalvik-cache/ /data/dalvik-cache/
29.0M /cache/dalvik-cache/
23.5M /data/dalvik-cache/
~ # getprop dalvik.vm.verify-bytecode
But the idea is interesnting.

KCRic said:
Might try this on my G2 - can't hurt to try for a bit.
Just wondering exactly what verify bytecode does for the dalvik-vm. Is it there to ensure data integrity, checking for errors and such? Is it sort of like what ECC is for RAM but for the dalvik-vm?
Click to expand...
Click to collapse
An in-depth discussion has been linked at the bottom of OP. It simply makes Android ignore any possible errors in code & proceed directly to compile all classes. It also forces to compile some unsafe code. And, yes, it's mainly there to check for errors I'd say. The process is very similar to odexing with dexopt. It forces DVM to make some unsafe assumptions which dexopt makes by default. This is not very different from odexing in terms of the byte code produced.
alroger said:
Hmmm, I think I dont have that prop here... getprop dalvik.vm.verify-bytecode returns nothing to me. Imediatly after boot caches come back and grow...
This is after a reboot
Code:
~ # du -hs /cache/dalvik-cache/ /data/dalvik-cache/
29.0M /cache/dalvik-cache/
23.5M /data/dalvik-cache/
~ # getprop dalvik.vm.verify-bytecode
But the idea is interesnting.
Click to expand...
Click to collapse
This would not do anything at all to the caches. They will be reproduced after reboot. It just changes the bytecode pattern in dex/odex files. Perhaps, the cache might even be slightly bigger with this code.
Can you try dalvikvm -help and post the output? If you are in root mode, the getprop should either return a true or false. What version/device are you using?

no dalvik.vm.verify-bytecode
nibras_reeza said:
This would not do anything at all to the caches. They will be reproduced after reboot. It just changes the bytecode pattern in dex/odex files. Perhaps, the cache might even be slightly bigger with this code.
Can you try dalvikvm -help and post the output? If you are in root mode, the getprop should either return a true or false. What version/device are you using?
Click to expand...
Click to collapse
[TAB] Samsung Galaxy Tab P1000N
[ROM] CM7 Beta KANG 2011-06-16 by Technomancer
[KERNEL] CM7 #20110911 by HumberOS
Txt attached.
- XDA Premium App - SGT-P1000N CM7 Beta KANG

Originally Posted by fLipz View Post
What about the start and stop command?
Huh?
Click to expand...
Click to collapse
i read here it says
from netmite
Remember to stop and restart the runtime (adb shell stop; adb shell start).
Click to expand...
Click to collapse
do we still need to type at the Terminal Emulator the Command Start and Stop after we type the code?
and here's also my output
z71 Variant
CM7 182 Nightly Build
# dalvikvm -help
dalvikvm -help
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all}
-Xnoquithandler
-Xjnigreflimit:N (must be multiple of 100, >= 200)
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xdeadlockpredict:{off,warn,err,abort}
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-Xgenregmap
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
Configured with: debugger profiler hprof jit(armv6-vfp) show_exception=1
Dalvik VM init failed (check log file)
#
Click to expand...
Click to collapse
thank you!

Thanks for sharing, I tried it but only this part doesn't work
rm /cache/dalvik-cache/* no such directory.
I think it speed my phone a little, can I ask to is this compatible with V6 supercharger?
Thanks again.

alroger said:
[TAB] Samsung Galaxy Tab P1000N
[ROM] CM7 Beta KANG 2011-06-16 by Technomancer
[KERNEL] CM7 #20110911 by HumberOS
Txt attached. --- oops, can't upload from the tab. Looking for anything specific?
Copy/paste for now. I will clean this up later...
dalvikvm: [options] class [argument ...]
dalvikvm: [options] -jar file.jar [argument ...]
The following standard options are recognized:
-classpath classpath
-Dproperty=value
-verbose:tag ('gc', 'jni', or 'class')
-ea[:<package name>... |:<class name>]
-da[:<package name>... |:<class name>]
(-enableassertions, -disableassertions)
-esa
-dsa
(-enablesystemassertions, -disablesystemassertions)
-showversion
-help
The following extended options are recognized:
-Xrunjdwp:<options>
-Xbootclasspath:bootclasspath
-Xcheck:tag (e.g. 'jni')
-XmsN (min heap, must be multiple of 1K, >= 1MB)
-XmxN (max heap, must be multiple of 1K, >= 2MB)
-XssN (stack size, >= 1KB, <= 256KB)
-Xverify:{none,remote,all}
-Xrs
-Xint (extended to accept 'ortable', ':fast' and ':jit')
These are unique to Dalvik:
-Xzygote
-Xdexopt:{none,verified,all}
-Xnoquithandler
-Xjnigreflimit:N (must be multiple of 100, >= 200)
-Xjniopts:{warnonly,forcecopy}
-Xjnitrace:substring (eg NativeClass or nativeMethod)
-Xdeadlockpredict:{off,warn,err,abort}
-Xstacktracefile:<filename>
-Xgc:[no]precise
-Xgc:[no]preverify
-Xgc:[no]postverify
-Xgc:[no]concurrent
-Xgc:[no]verifycardtable
-Xgenregmap
-Xcheckdexsum
-Xincludeselectedop
-Xjitop:hexopvalue[-endvalue][,hexopvalue[-endvalue]]*
-Xincludeselectedmethod
-Xjitthreshold:decimalvalue
-Xjitblocking
-Xjitmethod:signature[,signature]* (eg Ljava/lang/String\;replace)
-Xjitcheckcg
-Xjitverbose
-Xjitprofile
-Xjitdisableopt
Configured with: debugger profiler hprof jit(armv7-a-neon) show_exception=1
Dalvik VM init failed (check log file)
- XDA Premium App - SGT-P1000N CM7 Beta KANG
Click to expand...
Click to collapse
Try these,
Run these commands and see what are the default values.
getprop dalvik.vm.Xverify
getprop dalbik.vm.Xdexopt
getprop dalvik.vm.dexopt-flags
Then, try running these if above commands return a value.
setprop dalvik.vm.Xverify none
setprop dalbik.vm.Xdexopt verified
setprop dalvik.vm.dexopt-flags v=n,o=v
It appears your device doesn't seem to have the properties I have changed in this guide. I'm not sure how this will turn out. But, try above commands. Am just making an intelligent guess.
---------- Post added at 03:55 PM ---------- Previous post was at 03:54 PM ----------
fLipz said:
i read here it says
from netmite
do we still need to type at the Terminal Emulator the Command Start and Stop after we type the code?
and here's also my output
z71 Variant
CM7 182 Nightly Build
thank you!
Click to expand...
Click to collapse
Not necessary to restart the shell since we are rebooting the device itself.
---------- Post added at 03:56 PM ---------- Previous post was at 03:55 PM ----------
jikantaru said:
Thanks for sharing, I tried it but only this part doesn't work
rm /cache/dalvik-cache/* no such directory.
I think it speed my phone a little, can I ask to is this compatible with V6 supercharger?
Thanks again.
Click to expand...
Click to collapse
I don't know. I haven't gone through the full source of super charger. It wouldn't really cause a problem that I can think of. This flag just changes the way Dalvik VM compiles apps. This should not interfere with anything else other than badly coded apps.

jikantaru said:
Thanks for sharing, I tried it but only this part doesn't work
rm /cache/dalvik-cache/* no such directory.
I think it speed my phone a little, can I ask to is this compatible with V6 supercharger?
Thanks again.
Click to expand...
Click to collapse
i pair this with v6 supercharger and both is work.
supercharger is for memory management..and this setting is for dalvik management..totally different working area for both setting CMIIW
confirmed work with
Nexus one with SuperOSR ROM
and Samsung Spica i5700 with CM 6.11 froyo ROM
Nice share!

[Q] Talking to modem using AT commands

Hello everyone, i'm new to this forum, so i'm not sure if i should ask for help here, but anyway.
I'm trying to do a data call using adb shell (also i view logs using logcat), but i can't find the modem file. I've read this article http://forum.xda-developers.com/showthread.php?t=1471241 but i didn't help me.
When i execute cat /proc/tty/drivers i get the following:
Code:
/dev/tty /dev/tty 5 0 system:/dev/tty
/dev/console /dev/console 5 1 system:console
/dev/ptmx /dev/ptmx 5 2 system
/dev/vc/0 /dev/vc/0 4 0 system:vtmaster
rfcomm /dev/rfcomm 216 0-255 serial
g_serial /dev/ttyGS 237 0-3 serial
serial /dev/ttyS 4 64-67 serial
pty_slave /dev/pts 136 0-1048575 pty:slave
pty_master /dev/ptm 128 0-1048575 pty:master
unknown /dev/tty 4 1-63 console
Looks like i shoud send commands to /dev/ttyGS0, but it doesn't reply. I've tried the following commands:
Code:
echo "AT\r" > /dev/ttyGS0
echo "ATD12345678900;\r" > /dev/ttyGS0
but nothing happens. Actually, i'm not sure that i have to send commands to this file, but others don't reply too. So, i'm asking for help to do a data call, thanks in advance.
Also i have huawei P1 XL (u9200) and LG P765, which are based on similar chipsets, but for some reason i can't make data call with huawei, but can do it with LG. All devices are rooted. If u have any suggestions please let me know=)

Z5 Rooting & Recovery Boot Mode (UK Xperia Z5 E6653)

Morning All,
I've been looking around for a stock Lollipop 5.1.1 Rom for the Xperia Z5 but haven't come across one yet, are there preferred site to browse for stock roms?
Also, is anyone aware of how to boot into recovery mode? Does a stock Sony Rom for Lollipop have it enabled?

http://developer.sonymobile.com/201...for-a-range-of-unlocked-xperia-devices-video/

Could you call *#*#2673#*#* in dial app?
If it doesn't blocked by security, we can enable non-secure ADB thanks to new app in Z5 system.

Does anyone know if someone working on a root method

AndroPlus said:
Could you call *#*#2673#*#* in dial app?
If it doesn't blocked by security, we can enable non-secure ADB thanks to new app in Z5 system.
Click to expand...
Click to collapse
Hello AndroPlus, sorry if this is noob question but could you explain what is it non secure adb and for what exactly it is useful? I tried dial that number and i was able to get into core settings menu with option switch non secure adb on but im still not sure what does it mean exactly and google is pretty silent about this as i can't find any informations about it
Sent from my E6653 using XDA Free mobile app

flakac said:
Hello AndroPlus, sorry if this is noob question but could you explain what is it non secure adb and for what exactly it is useful? I tried dial that number and i was able to get into core settings menu with option switch non secure adb on but im still not sure what does it mean exactly and google is pretty silent about this as i can't find any informations about it
Sent from my E6653 using XDA Free mobile app
Click to expand...
Click to collapse
You can use # (root) in adb shell if non secure adb is enabled.
We have to find how to disable dm-verity and ric to mod system partition, though...

AndroPlus said:
You can use # (root) in adb shell if non secure adb is enabled.
We have to find how to disable dm-verity and ric to mod system partition, though...
Click to expand...
Click to collapse
Nice,that's interesting, I owned every single Xperia Z and red alot about rooting on each single model but never heard about non secure adb.
But now I am huge fan of non secure adb,i hope someone will find how to disable ric!
Sent from my E6653 using XDA Free mobile app

AndroPlus said:
You can use # (root) in adb shell if non secure adb is enabled.
We have to find how to disable dm-verity and ric to mod system partition, though...
Click to expand...
Click to collapse
Does that mean you can backup TA partition in adb shell using dd command?

shoey63 said:
Does that mean you can backup TA partition in adb shell using dd command?
Click to expand...
Click to collapse
Yes, if it works.
Sometimes security feature blocks root to do any actions (they are stronger than root...), so someone should try it first.

shoey63 said:
Does that mean you can backup TA partition in adb shell using dd command?
Click to expand...
Click to collapse
Could anyone with a Z5 or Z5 Compact try this, please?
I'd love to know before buying one.

non-secure ADB works on my Z5 (sim-free UK).
What is the command to backup partitions?

okgnew said:
non-secure ADB works on my Z5 (sim-free UK).
What is the command to backup partitions?
Click to expand...
Click to collapse
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img

hm. it does not work.
I get 'permissions denied'

okgnew said:
hm. it does not work.
I get 'permissions denied'
Click to expand...
Click to collapse
If you type
Code:
id
, what do you get?

[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1011(adb),1015(sdcard_rw),1026(drmrpc),1028(sdcard_r),2993(
trimarea),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
[email protected]:/ $ dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
v/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img <
dd: /dev/block/platform/msm_sdcc.1/by-name/TA: Permission denied
---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------
W:\>adb push hosts /data/data
failed to copy 'hosts' to '/data/data/hosts': Permission denied

okgnew said:
[email protected]:/ $ id
id
uid=2000(shell) gid=2000(shell) groups=1004(input),1007(log),1011(adb),1015(sdcard_rw),1026(drmrpc),1028(sdcard_r),2993(
trimarea),3001(net_bt_admin),3002(net_bt),3003(inet),3006(net_bw_stats) context=u:r:shell:s0
---------- Post added at 09:48 PM ---------- Previous post was at 09:47 PM ----------
[email protected]:/ $ dd if=/dev/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img
v/block/platform/msm_sdcc.1/by-name/TA of=/sdcard/TA.img <
dd: /dev/block/platform/msm_sdcc.1/by-name/TA: Permission denied
---------- Post added at 09:49 PM ---------- Previous post was at 09:48 PM ----------
W:\>adb push hosts /data/data
failed to copy 'hosts' to '/data/data/hosts': Permission denied
Click to expand...
Click to collapse
You are not root, you are shell user.
You are using secure ADB.

I run 'adb root' but it did not change anything
And 'su' returns 'command not found'

After unsecuring ADB is it possible to push su and busybox via ADB with a computer

Thekjp95 said:
After unsecuring ADB is it possible to push su and busybox via ADB with a computer
Click to expand...
Click to collapse
Not that I could see. I tried a few commands which didn't work but even if you did dm-verity would have to be disabled otherwise the system would bootloop
Sent from my E6653 using Tapatalk

@DooMLoRD will you be willing to do work on the z5

Get double tap to wake in any rom

I'll be showing you how to get dt2w(double tap to wake) working in any rom
Install terminal emulator app from play store and then run these commands
su
ls /proc
cat /proc/tp_wakeup_gesture
echo 1 > /proc/tp_wakeup_gesture
NOTE:After a reboot it won't work until you enter the commands again
NOTE: Only works on goodix panels(to check if you have goodix panel install device info hw app and check if touchscreen says goodix-ts that means that you have a goodix panel)
Credits:33bca/Offain

Not working getting permission denied so probably do need root.

Thank you! Works for me. Can it be implemented as Magisk module?

worked for me too
but; as root,
also
Code:
mad.duck.ffs:/ # echo 1> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
0
while
Code:
mad.duck.ffs:/ # echo "1"> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
1
then just added it in "boot shell" app to be run every time my device started,
works perfectly, thanks.

czkb said:
worked for me too
but; as root,
also
Code:
mad.duck.ffs:/ # echo 1> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
0
while
Code:
mad.duck.ffs:/ # echo "1"> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
1
then just added it in "boot shell" app to be run every time my device started,
works perfectly, thanks.
Click to expand...
Click to collapse
Thanks! Can you guide step by step how to add commands in boot shell?

gkornaks said:
Thanks! Can you guide step by step how to add commands in boot shell?
Click to expand...
Click to collapse
click on the "+"
add command
give it a name (first line)
add the command (second line)
check run on boot
save and you're good to go.
i dont have 10 post yet so i cant post pics, but that's pretty much it.

czkb said:
click on the "+"
add command
give it a name (first line)
add the command (second line)
check run on boot
save and you're good to go.
i dont have 10 post yet so i cant post pics, but that's pretty much it.
Click to expand...
Click to collapse
Thank you! The command which starts with echo, right?

czkb said:
worked for me too
but; as root,
also
Code:
mad.duck.ffs:/ # echo 1> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
0
while
Code:
mad.duck.ffs:/ # echo "1"> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
1
then just added it in "boot shell" app to be run every time my device started,
works perfectly, thanks.
Click to expand...
Click to collapse
So, only work with root?

gkornaks said:
Thank you! The command which starts with echo, right?
Click to expand...
Click to collapse
yep
Code:
echo "1"> /proc/tp_wakeup_gesture
Batmany said:
So, only work with root?
Click to expand...
Click to collapse
no idea, i only tried as root since another member said that permission was denied when not elevated.

gkornaks said:
Thank you! Works for me. Can it be implemented as Magisk module?
Click to expand...
Click to collapse
No

czkb said:
worked for me too
but; as root,
also
while
then just added it in "boot shell" app to be run every time my device started,
works perfectly, thanks.
Click to expand...
Click to collapse
No Problem

You should maybe meantion that it just will work with goodix touchscreens...
I'll implement a toggle into my LineageOS once I've fixed it on Focaltech touchscreens too.

Thank you !! It worked for me.

33bca said:
You should maybe meantion that it just will work with goodix touchscreens...
I'll implement a toggle into my LineageOS once I've fixed it on Focaltech touchscreens too.
Click to expand...
Click to collapse
Ok,should i add it or just remove the thread?

Does it results in more battery drain?
I mean whether the phone goes to deep sleep or not?

00norman00 said:
Does it results in more battery drain?
I mean whether the phone goes to deep sleep or not?
Click to expand...
Click to collapse
For me battery is the same

czkb said:
worked for me too
but; as root,
also
Code:
mad.duck.ffs:/ # echo 1> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
0
while
Code:
mad.duck.ffs:/ # echo "1"> /proc/tp_wakeup_gesture
mad.duck.ffs:/ # cat /proc/tp_wakeup_gesture
1
then just added it in "boot shell" app to be run every time my device started,
works perfectly, thanks.
Click to expand...
Click to collapse
dude such a great help. thanks.

Thanks for sharing ? But I even turned off dt2w on stock rom, just because it too often randomly wake up and input numbers randomly while in my pocket.
I hope there is a way for dt2w to check the proximity sensor before proceeds to wake up the phone.

zogajg26 said:
I'll be showing you how to get dt2w(double tap to wake) working in any rom
Install terminal emulator app from play store and then run these commands
su
ls /proc
cat /proc/tp_wakeup_gesture
echo 1 > /proc/tp_wakeup_gesture
NOTE:After a reboot it won't work until you enter the commands again
NOTE: Only works on goodix panels(to check if you have goodix panel install device info hw app and check if touchscreen says goodix-ts that means that you have a goodix panel)
Credits:33bca/Offain
Click to expand...
Click to collapse
So this is temporary solution? If we restart the phone, it will be back to original right? (I will try, i have goodix, but odds i dont have menu to activate from the stock rom oreo)
**** Wow it worked man.. thanks

I'm getting permission denied even with root.
Sent from my Phh-Treble vanilla using Tapatalk