If your double tap to wake (DT2W) is not enabled by default, and other how-tos
don't worki for you, try this:
1. You will need to edit the local build prop:
got to: /product/etc/prop and edit local.prop (your system must be rw)
2. Find the "ro.config.hw_easywakeup=false" and change the value to true, press save and exit
3. Now you need to mod the hw_easywakeupmotion_config.xml which is in /system/emui/base/xml:
Change the
Code:
<HwEasyWakeUpMotion>
<EasyWakeUpMotion name="Double_Touch" support="1" value="0" flag="11" keycode="142" />
to :
Code:
<HwEasyWakeUpMotion>
<EasyWakeUpMotion name="Double_Touch support="1" value="1" flag="11" keycode="142" />
you can edit other paramethers as well.
4. Save, exit and reboot.
5. After the reboot go to: Settings -> Smart assistance -> Motion Control -> turn the features on.
We already have a guide about this
i
Johnny TDN said:
We already have a guide about this
Click to expand...
Click to collapse
They did nkt work for me, so I tought I share my method
Related
Hi! first sorry for my bad english
There is a modificate android.policy.jar to wake the device with volume keys.
Simply replace "/system/framework/android.policy.jar" with this and set permisions to 644 (Very important!)
Tested with AOSP KitKat 4.4 for Nexus S - alpha Build 2 and build 3
Volume wake mod for Android 4.4
I cannot make it stick. Can you be more specific with your step by step procedure please? Every time I change the permission and reboot, nothing happens. It just returns to it's original setting from 644 to 0770. I definitely need this feature on AOSP 4.4, coz I don't wanna burden my previously repaired button so much. Thanks, noobie btw. =)
Good job !
killswitch70 said:
I cannot make it stick. Can you be more specific with your step by step procedure please? Every time I change the permission and reboot, nothing happens. It just returns to it's original setting from 644 to 0770. I definitely need this feature on AOSP 4.4, coz I don't wanna burden my previously repaired button so much. Thanks, noobie btw. =)
Click to expand...
Click to collapse
I downloaded a file explorer with root options, es file explorer for example, mount your system partition with read/write permisions and replace this file in system/framework. then change the permisions in properties and reboot.
javi851 said:
I downloaded a file explorer with root options, es file explorer for example, mount your system partition with read/write permisions and replace this file in system/framework. then change the permisions in properties and reboot.
Click to expand...
Click to collapse
I'm now currently running the unofficial cm 11 on my nexus s, will it work on that too? Having used the aosp ver, I'll try this again if I still couldn't get the volume wake mod I'm trying to look for. Thanks for your patience.:good:
Not working on unofficial cm11
Sent from my Nexus S using Tapatalk
DarkShadow69 said:
Not working on unofficial cm11
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Post "android.policy.jar" of your unofficial cm11 here and I will try to modify, but I don't know if it work
PD: CM11 hasn't got this option?
javi851 said:
Post "android.policy.jar" of your unofficial cm11 here and I will try to modify, but I don't know if it work
PD: CM11 hasn't got this option?
Click to expand...
Click to collapse
CM11 Euroskank has it.. Just pull the file from that ROM..
Sent from my Nexus S using XDA Premium 4 mobile app
javi851 said:
Hi! first sorry for my bad english
There is a modificate android.policy.jar to wake the device with volume keys.
Simply replace "/system/framework/android.policy.jar" with this and set permisions to 644 (Very important!)
Tested with AOSP KitKat 4.4 for Nexus S - alpha Build 2 and build 3
Click to expand...
Click to collapse
does this work on nexus 5 stock android 4.4?
in stock 4.4, android.policy.jas has been seperated with an odex file.
many thanks for the modification.
hk_aquarius said:
does this work on nexus 5 stock android 4.4?
in stock 4.4, android.policy.jas has been seperated with an odex file.
many thanks for the modification.
Click to expand...
Click to collapse
Make a backup and give it a try, or try the cm11 policy jar
Sent from my Nexus S using XDA Premium 4 mobile app
can you add Advanced 4 Way Reboot Menu
javi851 said:
Hi! first sorry for my bad english
There is a modificate android.policy.jar to wake the device with volume keys.
Simply replace "/system/framework/android.policy.jar" with this and set permisions to 644 (Very important!)
Tested with AOSP KitKat 4.4 for Nexus S - alpha Build 2 and build 3
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2536321
it work on a3
hanflang said:
http://forum.xda-developers.com/showthread.php?t=2536321
it work on a3
Click to expand...
Click to collapse
Thanks, I test it
javi851 said:
Hi! first sorry for my bad english
There is a modificate android.policy.jar to wake the device with volume keys.
Simply replace "/system/framework/android.policy.jar" with this and set permisions to 644 (Very important!)
Tested with AOSP KitKat 4.4 for Nexus S - alpha Build 2 and build 3
Click to expand...
Click to collapse
Hi there javi851,
Very useful mod!
Could you please answer the following questions for me, as I am trying to replicate this for Nexus 5:
1. What modifications have you made to android.policy.jar file?
2. What was the process you followed to make these modifications?
3. Is this an odexed or deodexed android.policy.jar file?
Many thanks for your help, it is much appreciated
Sent from my Nexus 5 using Tapatalk
I can confirm that this doesn't work on stock android 4.4. Probably because there is an odex file as well?
~S
wilskywalker said:
Hi there javi851,
Very useful mod!
Could you please answer the following questions for me, as I am trying to replicate this for Nexus 5:
1. What modifications have you made to android.policy.jar file?
2. What was the process you followed to make these modifications?
3. Is this an odexed or deodexed android.policy.jar file?
Many thanks for your help, it is much appreciated
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
This file works on deodexed roms.
I followed this guide with some variations: http://forum.xda-developers.com/showthread.php?p=18452084
in point 5 made this:
5. Navigate to android.policy.jar.out\smali\com\android\internal\ policy\impl\PhoneWindowManager.smali
6. Search for .method private isWakeKeyWhenScreenOff(I)Z
A few lines down will be 0x18 -> :sswitch_0 and 0x19 -> :sswitch_0
Delete both these lines. It should look like this towards the bottom near .end method:
PHP Code:
.sparse-switch
0x1b -> :sswitch_1
0x4f -> :sswitch_1
0x55 -> :sswitch_1
0x56 -> :sswitch_1
0x57 -> :sswitch_1
0x58 -> :sswitch_1
0x59 -> :sswitch_1
0x5a -> :sswitch_1
0x5b -> :sswitch_1
0x7e -> :sswitch_1
0x7f -> :sswitch_1
0x82 -> :sswitch_1
0xa4 -> :sswitch_0
.end sparse-switch
.end method
10. From the command line, type "java -jar smali-1.2.8.jar -o classes.dex out". You now have a new classes.dex that has your modification.
11. Open android.policy.jar file on your desktop with 7zip and insert the new classes.dex file.
12. Copy the new file to your phone (system\framework folder, ensure that you set proper permissions (chmod 644 or set permissions to rw-r-r)) and reboot.
javi851 said:
This file works on deodexed roms.
I followed this guide with some variations: http://forum.xda-developers.com/showthread.php?p=18452084
in point 5 made this:
5. Navigate to android.policy.jar.out\smali\com\android\internal\ policy\impl\PhoneWindowManager.smali
6. Search for .method private isWakeKeyWhenScreenOff(I)Z
A few lines down will be 0x18 -> :sswitch_0 and 0x19 -> :sswitch_0
Delete both these lines. It should look like this towards the bottom near .end method:
PHP Code:
.sparse-switch
0x1b -> :sswitch_1
0x4f -> :sswitch_1
0x55 -> :sswitch_1
0x56 -> :sswitch_1
0x57 -> :sswitch_1
0x58 -> :sswitch_1
0x59 -> :sswitch_1
0x5a -> :sswitch_1
0x5b -> :sswitch_1
0x7e -> :sswitch_1
0x7f -> :sswitch_1
0x82 -> :sswitch_1
0xa4 -> :sswitch_0
.end sparse-switch
.end method
10. From the command line, type "java -jar smali-1.2.8.jar -o classes.dex out". You now have a new classes.dex that has your modification.
11. Open android.policy.jar file on your desktop with 7zip and insert the new classes.dex file.
12. Copy the new file to your phone (system\framework folder, ensure that you set proper permissions (chmod 644 or set permissions to rw-r-r)) and reboot.
Click to expand...
Click to collapse
That's right!
THanks for this
game android
javi851 said:
This file works on deodexed roms.
I followed this guide with some variations: http://forum.xda-developers.com/showthread.php?p=18452084
in point 5 made this:
5. Navigate to android.policy.jar.out\smali\com\android\internal\ policy\impl\PhoneWindowManager.smali
6. Search for .method private isWakeKeyWhenScreenOff(I)Z
A few lines down will be 0x18 -> :sswitch_0 and 0x19 -> :sswitch_0
Delete both these lines. It should look like this towards the bottom near .end method:
PHP Code:
.sparse-switch
0x1b -> :sswitch_1
0x4f -> :sswitch_1
0x55 -> :sswitch_1
0x56 -> :sswitch_1
0x57 -> :sswitch_1
0x58 -> :sswitch_1
0x59 -> :sswitch_1
0x5a -> :sswitch_1
0x5b -> :sswitch_1
0x7e -> :sswitch_1
0x7f -> :sswitch_1
0x82 -> :sswitch_1
0xa4 -> :sswitch_0
.end sparse-switch
.end method
10. From the command line, type "java -jar smali-1.2.8.jar -o classes.dex out". You now have a new classes.dex that has your modification.
11. Open android.policy.jar file on your desktop with 7zip and insert the new classes.dex file.
12. Copy the new file to your phone (system\framework folder, ensure that you set proper permissions (chmod 644 or set permissions to rw-r-r)) and reboot.
Click to expand...
Click to collapse
Hi buddy,
Thank you very much for this, very helpful!!
I do not understand that how to use it
I did some research and found a way to make the quick settings tiles disappear on the lock screen. Note that your device needs to be rooted using either SuperSu or Magisk.
The first thing you have to do is download Tasker.
On the Tasker app, make a new profile
Event --> Display --> Display Off
Now make a task, we will name this task "Hide Tiles"
New Task --> Code --> Run Shell
Now important, if you're rooted with SuperSu then use the first code, if you're rooted with Magisk then use the second one.
First code is (without quotes): "settings put secure sysui_qs_tiles 0"
Second code is (WITH quotes): /sbin/su -c "settings put secure sysui_qs_tiles 0"
This is the profile that will hide the tiles when the phone is locked, now we need a profile where it shows them after the password/fingerprint is used on the phone.
Go ahead and create a new profile
Event --> Display --> Display Unlocked
Now make a task, we will name it "Show Tiles"
(SuperSu uses the first code, Magisk uses the second one)
New Task --> Code --> Run Shell
First code (without quotes): "settings put secure sysui_qs_tiles wifi,cell,location,dnd,rotation,bt,battery,flashlight,hotspot,airplane,inversion,saver,cast"
(From the screenshot you will learn which name refers to which tile, you can then add/remove/reorder them however you want)
Second code (WITH quotes): /sbin/su -c "settings put secure sysui_qs_tiles wifi,cell,location,dnd,rotation,bt,battery,flashlight,hotspot,airplane,inversion,saver,cast"
If these codes don't work with Tasker, you can use them in Secure Settings but instead of (New Task --> Code --> Run Shell) you have to do (New Task --> Plugin --> Secure Settings --> Configuration --> Action --> Run Command)
The code you'll have to use is the one we used for Supersu (it will work for both Magisk and SuperSu users) but make sure you check the USE ROOT box)
I have tried this on a Nexus 5X running Oreo 8.1 OPM3 and it works every single time.
Let me know if you have tried this on your phone so we'd know which devices it works on. Thank you!
nice, but too bad it crashes on miui based roms
Worked with Secure Settings an Oneplus 3t, Skydragon-Rom.
Thank you! :good:
There are some Quicksettings i don't know the name to let it show after unlock. Can anybody help me?
The tiles from the first picture would be great to know the correct name.
This is very interesting, thanks for the question.
Finally I successfully managed to enable built-in call recording function by modifying cscfeature.xml file.My device is Note 8- SM-N9500 (TGY) oreo 8.0
1. Open any root explorer app
2. Go to system/csc/ folder
3.Open cscfeature.xml and edit
4.Add following line at the bottom before </featureset>
<CscFeature_VoiceCall_ConfigRecording>RecordingAllowed</CscFeature_VoiceCall_ConfigRecording>
5. Reboot and enjoy.
Note: Your recordings are under folder sdcard/call
Update: This Method works on Oreo and Pie as well
Good day
First thread here so please go easy on me
This is a small guide on how to increase the headphone volume for Nokia 5 (TA-1053). Might work on other models too...
Things you need:
0. Nokia 5 TA-1053
1. Unlocked bootloader
2. Root
3. Third party file manager (Root explorer, ES, etc.)
Phase 1:
> Unlock and root your phone. This helpful thread will guide you:
https://forum.xda-developers.com/nokia-5/how-to/root-twrp-nokia-5-t3703423
**You need to downgrade to Nougat to unlock and root the phone
Phase 2: access root filesystem and Mixer_paths
> Open your file manager app
> On ES file explorer, grant root acces on app then go to Home > Local > Device > etc
> FOR ANDROID OREO/PIE: Mixer_path_nd1 is located at root/etc/vendor
> Usually on custom roms like Lineage OS for Qualcomm devices, you can find a single file named Mixer_paths.xml. however on Nokia devies it consists of 20 mixer_paths due to HMD distributing similar software across different models like the Nokia 6 (not sure why but i saw a D1C mixer_path, and D1C is a Nokia 6)
> Now look for a file named "Mixer_paths_nd1.xml" then open it via a text editor
> Scoll down until you see "these are inital mixer settings". Locate these tags:
Rx1 digital volume
Rx2 digital volume
Rx3 digital volume
Default value is 84, so change it so something higher. I set mine to 92
> After changing the mixer path value, save the file (with root access) and exit the app. And restart the phone
> Enjoy the loudness
Phase 3 (optional):
For better audio experience, try installing Viper4Audio 2.7, which can be found here:
https://www.xda-developers.com/viper4android-v2-7-new-ui-profile-management
DONE!
Thanks to:
@wolfyapl for the bootloader unlock/TWRP guide
Team DeWitt for the Viper4Audio material design app
Viper4Audio Team
HMD Nokia
XDA community
Is it possible to enable Install via USB and USB debugging (Security settings) without having a Mi account on the device? And what does MIUI optimisation options do?
Yes. MIUI optimizations heavily restrict background apps which lead to battery savings among other things.
Yes for the first question? Then how?
miravision said:
Yes. MIUI optimizations heavily restrict background apps which lead to battery savings among other things.
Click to expand...
Click to collapse
You need to root your phone. Here is a termux script that will achieve what you want without Mi account.
Code:
su
setprop persist.security.adbinstall 1
Edit file /data/data/com.miui.securitycenter/shared_prefs/remote_provider_preferences.xml
and change value to true if it's set to false or add line before the closing </map> tag. Reboot
Code:
<boolean name="security_adb_install_enable" value="true" />
Code:
reboot
I guess rooting will have to wait... can''t void warranty in a new phone before I have had a chance to test it fully. But, thank you. I will save the above.
I'm trying to disable automatic updates , i disabled them everywhere i could , including developer options but when i enable wifi , the updater app notifies me that i have a new update. Indeed, it won't update without my confirmation but i want to get rid of notifications completely . The notifications for this updater system app can not be turned off . Any workaround for this ?
miravision said:
You need to root your phone. Here is a termux script that will achieve what you want without Mi account.
Code:
su
setprop persist.security.adbinstall 1
Edit file /data/data/com.miui.securitycenter/shared_prefs/remote_provider_preferences.xml
and change value to true if it's set to false or add line before the closing </map> tag. Reboot
Code:
<boolean name="security_adb_install_enable" value="true" />
Code:
reboot
Click to expand...
Click to collapse
should this be valid in MIUI 13?
I did save the xml file twice, but after reboot the line for "install enable" was gone.
Any further ideas to mod this - without logging in to Mi Account?
Thaks
linolino
oops EDIT: I did an reboot via button instead of entering "reboot" in adb/termux - so I can confirm the toggel button is still on after command "reboot" in case of pressing button for reboot it was reverted ;-)
@miravision
is there another line for MIUI.
"Install via USB" worked to be turned on.
But still "USB debugging (Security settings)" can't be turned on in developer options.
This would be the toggle from this repeating screen shot: https://github.com/Genymobile/scrcpy/issues/70
Thanks
linolino
miravision said:
You need to root your phone.
Click to expand...
Click to collapse
this is a chicken egg problem:
in turn, root requires unlocking the bootloader (which requires logging in with a mi account over a cellular data sim, it doesn't allow this over wifi)