Guide: edit build.prop to display all apps in dual window - T-Mobile LG V10 Android Development

This article is taken from the following post (which will require translation): http://lgviet.com/forum/threads/huo...-thị-tát-cả-úng-dụng-hai-của-sỏ.54907/
By default enabling dual window only allows you the option to add a handful of apps. By modifying 5 lines to =true instead of =false you will be able to add ANY app installed on the device to the dual window. I've tested this on my H901. I'll also include a copy of the edited build.prop but I'm on V20J.....if you are not then you are probably better off modifying your own build.prop.
What does this require?
1) adb pull /system/build.prop
2) edit the build.prop to match below
3) do an adb shell, su to root and run "mount -o remount,rw /system" to make your system read/write instead of only read only.
4) rename /system/build.prop to build.prop.bak
5) adb push your modified build.prop to /system
6) type "diff /system/build.prop.bak /system/build.prop" in adb shell and verify the only changes are the 5 expected.
7) reboot. If for some reason it doesn't boot don't panic...you can get into twrp and copy the build.prop.bak back over the modified build.prop then reboot and start back at step 1.
8) press the app switching button and select the "dual window" button....you will now see you can scroll through ALL your apps to put in either the top or bottom window.
When you edit your build.prop the lines will NOT be in the same order as the example. You will need to do a search on each line so you can modify it. If you use the premodifed file attached make sure you remove .txt from the end of the filename which was required to attach it to the post.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

famewolf said:
This article is taken from the following post (which will require translation): http://lgviet.com/forum/threads/huo...-thị-tát-cả-úng-dụng-hai-của-sỏ.54907/
By default enabling dual window only allows you the option to add a handful of apps. By modifying 5 lines to =true instead of =false you will be able to add ANY app installed on the device to the dual window. I've tested this on my H901. I'll also include a copy of the edited build.prop but I'm on V20J.....if you are not then you are probably better off modifying your own build.prop.
What does this require?
1) adb pull /system/build.prop
2) edit the build.prop to match below
3) do an adb shell, su to root and run "mount -o remount,rw /system" to make your system read/write instead of only read only.
4) rename /system/build.prop to build.prop.bak
5) adb push your modified build.prop to /system
6) type "diff /system/build.prop.bak /system/build.prop" in adb shell and verify the only changes are the 5 expected.
7) reboot. If for some reason it doesn't boot don't panic...you can get into twrp and copy the build.prop.bak back over the modified build.prop then reboot and start back at step 1.
8) press the app switching button and select the "dual window" button....you will now see you can scroll through ALL your apps to put in either the top or bottom window.
When you edit your build.prop the lines will NOT be in the same order as the example. You will need to do a search on each line so you can modify it. If you use the premodifed file attached make sure you remove .txt from the end of the filename which was required to attach it to the post.
Click to expand...
Click to collapse
OR..... With root, just go to /system/build.prop with any root file explorer, find persist.splitwindow.support_all=false and change false to true....

nuevosean said:
OR..... With root, just go to /system/build.prop with any root file explorer, find persist.splitwindow.support_all=false and change false to true....
Click to expand...
Click to collapse
I can't guarantee that just that one line change is going to fully do the same thing given the original poster changed 5 lines. Are you able to scroll up and down through all your apps and drag whatever one you want to the top or bottom window with only the one line changed?

famewolf said:
I can't guarantee that just that one line change is going to fully do the same thing given the original poster changed 5 lines. Are you able to scroll up and down through all your apps and drag whatever one you want to the top or bottom window with only the one line changed?
Click to expand...
Click to collapse
Absolutely. I did this about 2 months ago when I first got the phone, and again when I got the marshmallow update.

nuevosean said:
Absolutely. I did this about 2 months ago when I first got the phone, and again when I got the marshmallow update.
View attachment 3861795
Click to expand...
Click to collapse
lol, how'd you get the battery to show on the home button on the bottom middle icon of the screen.

dannieloco said:
lol, how'd you get the battery to show on the home button on the bottom middle icon of the screen.
Click to expand...
Click to collapse
xposed battery home module.

dannieloco said:
lol, how'd you get the battery to show on the home button on the bottom middle icon of the screen.
Click to expand...
Click to collapse
Yeah, you have to be rooted with xposed framework. The module is called "battery home button".

nuevosean said:
Yeah, you have to be rooted with xposed framework. The module is called "battery home button".
Click to expand...
Click to collapse
Thanks. I went ahead and installed it

dannieloco said:
Thanks. I went ahead and installed it
Click to expand...
Click to collapse
no problem man. sharing info is what this site's all about...

Related

[Boot Animation] OU Sooners with sound

Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Just in time for College Football. Those of you that are Sooner fans will appreciate it and those of you that aren't..well tough!
This features the stock android boot animation with added Oklahoma Sooners Flare.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Unzip the file then follow the instructions below.
Root Explorer method:
1. Rename your bootanimation to bootanimation (if not already named this)
2. Put it on your SD card
3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation
4. Reboot your phone
ADB method:
1. Make sure you have downloaded android sdk
2. Put android sdk in C:\
3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open cmd
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
-adb reboot
Click to expand...
Click to collapse
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
Originally Posted by hockeyfamily737
0. It's recommended to do a nandroid backup first!
1. Download the "bootsnd.sh" file and put it on the root of your sd card.
2. Using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media
3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh
sh bootsnd.sh
reboot
4. As the device boots up you will be greeted by the "Boomer Sooner" sound heard during football games. You are now free to replace the android_audio.mp3 file in /system/media with any .mp3 file you like as long as you rename it to "android_audio.mp3"
5. DO NOT ATTEMPT TO OUTSMART THESE DIRECTIONS OR YOU WILL BE RESTORING YOUR NANDROID BACKUP!
6. Enjoy
Click to expand...
Click to collapse
http://dl.dropbox.com/u/10373328/bootsnd.sh
This one took some time I have been trying to get it working for about 4 hours. Finally just gave up and recreated. That seemed to do the trick. UGH.
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Here is how to fix it.
Make sure you are mounting in r/w mode on each of these steps.
Using a app like root explorer, goto /system/bin and delete the file bootsound.
Back out to /system now open build.prop in text editor mode, look for this text.
Code:
ro.config.play.bootsound=1
Delete it from the build.prop and save and exit.
This is optional but recommened.
Reboot phone.
Verify no sound is playing.
Now run the script again and reboot.
You should have a boot sound again.
Click to expand...
Click to collapse

[Boot Animation]Android Gone Wild

Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and wanted to have a bootanimation of it. Its simple yet funny/interesting. I didnt create the images I merely resized them some and packaged them up as a bootanimtion. All credit goes to the original creator of the images JaiThemes.
Preview at the bottom it flashes REALLY fast. However the actual bootanimation is a LOT slower.
Unzip the file then follow the instructions below.
Root Explorer method:
1. Rename your bootanimation to bootanimation (if not already named this)
2. Put it on your SD card
3. Open Root Explorer and copy bootanimation.zip to /system/media. This will replace the existing boot animation
4. Reboot your phone
ADB method:
1. Make sure you have downloaded android sdk
2. Put android sdk in C:\
3. Set the directory of command prompt to C:\android-sdk-windows\platform-tools. Click here for a video tutorial.
4. Rename your boot animation to bootanimation and put it in C:\android-sdk-windows\platform-tools
5. Open cmd
6. Type in order:
-adb remount
-adb push bootanimation.zip /system/media/bootanimation.zip
-adb reboot
Click to expand...
Click to collapse
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
Originally Posted by hockeyfamily737
0. It's recommended to do a nandroid backup first!
1. Download the "bootsnd.sh" file and put it on the root of your sd card.
2. Using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media
3. Open Terminal Emulator and type the following commands using the stock keyboard. Press enter after each line:
su
cd /sdcard
sh
sh bootsnd.sh
reboot
4. As the device boots up you will be greeted by "Teach me how to dougie" sound. You are now free to replace the android_audio.mp3 file in /system/media with any .mp3 file you like as long as you rename it to "android_audio.mp3"
5. DO NOT ATTEMPT TO OUTSMART THESE DIRECTIONS OR YOU WILL BE RESTORING YOUR NANDROID BACKUP!
6. Enjoy
Click to expand...
Click to collapse
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Here is how to fix it.
Make sure you are mounting in r/w mode on each of these steps.
Using a app like root explorer, goto /system/bin and delete the file bootsound.
Back out to /system now open build.prop in text editor mode, look for this text.
Code:
ro.config.play.bootsound=1
Delete it from the build.prop and save and exit.
This is optional but recommened.
Reboot phone.
Verify no sound is playing.
Now run the script again and reboot.
You should have a boot sound again.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
eollie said:
Disclaimer:I am not responsible if you break,brick,hump,throw against wall or any other action you do to your phone. By using this bootanimation you agree anything that happens is your own noobtastic fault. Any attempts at blaming me for anything other than this being fantastic will result in you being pointed and laughed at.
If you are using BACKSIDE/IHO or have already installed the script dont I REPEAT DONT run the script again. Doing so makes multiple instances of the commands and will stop the bootsound from playing. If you run the script more than once you will have to delete somethings to get it to work. SO be warned DO NOT RUN THE SCRIPT IF YOU HAVE ALREADY OR ARE USING BACKSIDEIHO ROM
Ran across this the other day and wanted to have a bootanimation of it. Its simple yet funny/interesting. I didnt create the images I merely resized them some and packaged them up as a bootanimtion. All credit goes to the original creator of the images JaiThemes.
Preview at the bottom it flashes REALLY fast. However the actual bootanimation is a LOT slower.
Unzip the file then follow the instructions below.
You can also preview your bootanimation before rebooting.
In adb type adb shell bootanimation.
To add the sound.
If you are running BACKSIDE or have already installed the script all you have to do is using root explorer copy the file "android_audio.mp3" from the zip you downloaded to /system/media.
Then reboot and you should have awesome bootsound.
If you have never run the script and are not using BACKSIDE then follow the instructions below.
http://dl.dropbox.com/u/10373328/bootsnd.sh
If for some ungodly reason you ignored the above warning and installed the script again..read below.
Click to expand...
Click to collapse
seems has taken too much vodka in disc and has gone mad in disco lights, would have been great if u would have made him dance on floor
Yeah the stupid gif converter I used only has one speed...uber fracking fast.
If I could find a decent video of the dude in andy suit doing the dougie I might have a way to make him dance. But most videos arent the greatest.
should the name of the images in the booranimation.zip file be in serial order.. like
CM7_1.png,CM7_2.png.... ??

[Guide] XML editing for framework(pictures included) Updated 240214

Hi all XDA members, today I am going to show you how to edit xml files in your framework-res.apk so you can edit auto - rotation on lockscreen or CRT - Animation. This does not apply to the Arc only, most Android phone's framework can be edited this way except maybe Samsung or HTC phones which have an extra resource file. This guide contains screenshots and is meant to be noob friendly so everything is self explanatory, you don't need a rocket scientist to explain everything.
What you need:
Framework-res.apk you want to edit
Apktool
Notepad++ is recommended for editing XMLs.
7-zip
So let's get started:
1. If you want to edit the framework file, naturally you should have extracted it from your phone. If you have not done so, the framework-res.apk can be found in system/framework/framework-res.apk(requires root access)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Place the file into apktool directory
4. Press shift and right click the directory(don't select any file, just press shift right click in the empty space of your apktool directory, you should see "Open command window here")
5. You should see a command window like this:
6. Type this command: apktool if framework-res.apk. You should get a response like this:
7. Now type this command:apktool d framework-res.apk. This will decompile your framework-res.apk so you can access the xml files.
8. Go back to your apktool file. You should see a new folder called framework-res(Yes, please take a good look. I circled it for your sake.)
9. Open the folder. go to res/values/bools.xml
10. Right click on file, select edit with Notepad++
11. Now open in Notepad++, you can edit and choose the functions you want to add just by editing the boolean with "true" or "false"
That's it, you are now ready to choose if you want auto rotation lockscreen or enable CRT animation.
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
At the request of some users, I have updated the thread with the compiling and signing steps as well, so please continue reading.
12. Firstly we need some files to sign the apks, so go to your original framework-res.apk, right click -> 7 zip -> Open Archive
13. Extract the folder "META-INF" and the file "AndroidManifest.xml" from the framework-res.apk
13a. Alternatively, you can find the files in <your framework-res folder> -> Original // No "<>" symbols, please see attached screenshot
14. Before we compile the framework, please rename the folder to avoid any conflicts with the existing framework-res.apk
15. Type this command: apktool b <your framework-res folder> and press Enter // No "<>" symbols, please see attached screenshot
16. You should get a response like this:
17. Go to <your framework-res folder> -> dist -> framework-res.apk // No "<>" symbols, please see attached screenshot
WARNING! DO NOT PUSH THIS FILE INTO YOUR PHONE YET. IT HAS NOT BEEN SIGNED AND WILL CAUSE A BOOTLOOP IF YOU PUSH IT TO /SYSTEM. PLEASE CHECK THAT THESE FEW STEPS HAVE BEEN COMPLETED BEFORE PUSHING IT TO /SYSTEM
18. Right click the file, go to 7-zip -> Open Archive
19. Select the files you extracted or received from step 10 or 10a
20. Drag and drop into 7-zip. You will get a warning message. Press "Yes".
21. You should have both files copied into the apk. You have signed the framework-res.apk and the file is OK for use.
22. Push the framework-res.apk into /system/framework, set RW-R--R-- permissions and reboot.
That's it. Your phone should be functioning normally and the changes you did internally should take effect.
If you have found any errors in this tutorial, please send me a PM and I shall rectify it.
Also, please PM me or comment if you have questions.
If the question has been asked before, please read the previous posts if there are any.
Repeat questions will not be entertained.
popthosegaskets said:
Stay tuned to this thread, I will make a second thread about recompiling your framework and signing it for use on your phone.
Click to expand...
Click to collapse
Would be better keeping it all in one thread.
Sent from Myushi
XperienceD said:
Would be better keeping it all in one thread.
Sent from Myushi
Click to expand...
Click to collapse
Ok, thanks for the feedback
僕のLT18iから送られてきた
did you ever manage to get round to posting a recompiling guide??
Inside 4ndroid said:
did you ever manage to get round to posting a recompiling guide??
Click to expand...
Click to collapse
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
popthosegaskets said:
I'm busy with other stuff, although if you want me to redo the guide I can do so.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Inside 4ndroid said:
that would be awsome if you could write up the recompile guide.. but no rush only when you get the time... thanks
Click to expand...
Click to collapse
Ok... I shall redo this guide.
僕のLT18iから送られてきた
Thread content updated per user request.

[MOD][7.0+] Add more tiles to quick settings header

Introduction
If you have used Android N-ify before, you might like the fact that you can change the amount of tiles to be shown in qs header. But that module doesn't work on 7.0 (Everyone knows why). That was one thing i miss from that module.
So I looked into android source again and found that the value is stored in Settings.Secure and can be easily chaged.
Requirements
- Android 7.0+ (Tested on stock 39.2.A.0.327 but should work on any 7.0+ ROM)
- Root or a PC
Instructions
1. - If you have root, open Terminal Emulator, type "su", press enter and grant su permission and skip to step 6
- If you have already know how to use ADB shell, skip to step 6
2. Turn on USB debugging
3. Install ADB to your PC. You can use Minimal ADB and Fastboot or install Android SDK.
4. Open command prompt and type "adb devices". You should see your device listed there. If it says "offline", you need to press accept on your phone.
5. Type "adb shell" and you should see something on your screen.
6. Type the following command into command prompt. Replace "AMOUNT" with your preferred value.
Code:
content insert --uri content://settings/secure --bind name:s:sysui_qqs_count --bind value:i:AMOUNT
For example, If I want 6 tiles I need to type this command.
Code:
content insert --uri content://settings/secure --bind name:s:sysui_qqs_count --bind value:i:6
7. Press enter. Then the tiles amount should be changed instantly. If it your SystemUI crashed, simply click "Close app" and it will return back to normal.
8. Enjoy.
Other tweaks
Navbar buttons
You can also change navbar buttons too. The layout is stored using the key "sysui_nav_bar".
Details
Format:
Code:
{left};{center};{right}
Where {left} is buttons on the left, {center} is center buttons and {right} is buttons on the right.
You can put multiple buttons using "," to split.
For example, default button layout is space and back button on the left, home in center, recent and ime on the right. So the layout would be
Code:
space,back\;home\;recent,menu_ime
You can squeeze all buttons into one side and comfortably use your phone one-handed.
Code:
;menu_ime,space;back,home,recent
After you arranged buttons to your liking, you can put it on your phone by using the same command like qs mod. You also need to escape ; by adding \ in front of it.
Code:
content insert --uri content://settings/secure --bind name:s:sysui_nav_bar --bind value:s:\;menu_ime,space\;back,home,recent
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Screenshots
If you like it, press that thanks button.
@paphonb Thank you for this amazing guide, was just figuring out how to do this, loved your amazing Android N-ify.
This Works perfectly
True its work amazingly!! Maybe you know similar command for resizing nav bar size I mean heigh?
meistr91 said:
True its work amazingly!! Maybe you know similar command for resizing nav bar size I mean heigh?
Click to expand...
Click to collapse
There is no way to do that yet.
Sent from my F8332 using Tapatalk
paphonb said:
There is no way to do that yet.
Click to expand...
Click to collapse
Could it be that when i set 7 tiles quciksettings expand animation lagging a bit?
I followed the method but it didn't work for me any solution?
I'm using resurrection remix 5.8.1 N-7.1.1 in this version there is no option to change the option. I used both ADB and terminal.
gello0 said:
I followed the method but it didn't work for me any solution?
I'm using resurrection remix 5.8.1 N-7.1.1 in this version there is no option to change the option. I used both ADB and terminal.
Click to expand...
Click to collapse
I had the same problem, I tried doing it in terminal's phone and worked like a charm.
crisout said:
I had the same problem, I tried doing it in terminal's phone and worked like a charm.
Click to expand...
Click to collapse
how do it trough terminal?
nevermind found it!
All thumbs up for @paphonb, in the future you could do a simple app for tweaking this =)
Is there anyway I could have the layout (not the colors) looking like this (attachment).
The two (enlarged) icons at the top with 5 rows instead of 3.
Hey dev, great job. Is there something similar for data icons on status bar? I'd like to change 4G icon to that of AOSP/Google Pixel phones, just tiny LTE icon, I have Moto z play. Thanks.
How to remove or change location of the expansion Arrow ?
My device: Moto G5 (Cedric)
It did work on Stock Oreo Mi A1. Wanted to ask is there a way this can be done on the expanded QQ? Like in AICP roms, 6×3 ?
paphonb said:
5. Type "adb shell" and you should see something on your screen.
6. Type the following command into command prompt. Replace "AMOUNT" with your preferred value.
Code:
content insert --uri content://settings/secure --bind name:s:sysui_qqs_count --bind value:i:AMOUNT
For example, If I want 6 tiles I need to type this command.
Code:
content insert --uri content://settings/secure --bind name:s:sysui_qqs_count --bind value:i:6
7. Press enter. Then the tiles amount should be changed instantly. If it your SystemUI crashed, simply click "Close app" and it will return back to normal.
Click to expand...
Click to collapse
You could also do this directly, where you replace 7 with the amount you want
Code:
adb shell settings put secure sysui_qqs_count 7
Is there a command to set Quick settings rows and columns?
Darkweb_182 said:
Is there a command to set Quick settings rows and columns?
Click to expand...
Click to collapse
Supposedly for AOSP roms:
adb shell settings put secure sysui_qqs_count N
N being the number of tiles from 3-7
it works in my note 8 with oreo, but restore to stock tiles when the I restart the phone. there are some way for the changes stay applied?
billa said:
Supposedly for AOSP roms:
adb shell settings put secure sysui_qqs_count N
N being the number of tiles from 3-7
Click to expand...
Click to collapse
not that. how can we change QS row and column from 3x3 to 2x5 for example

Enable Duble Tap To Wake on "Nougat"

hi guys
Enable duble tap to wake on N rom
Requirements:
1) Be Rooted
2) need app like root explorer or ES file explorer file manager, or what ever you like.
3) go to system/buld.prop then first Press mount r/w then open buld.prop by text editor.
4) copy this line ro.config.hw_easywakeup=true and put it in the bottom of the page in a new line this line is missing in buld.prop in nougat rom but not in MM rom
5) save your change.
6) Go to system/emui/base/xml and open up that file hw_easywakeupmotion_config.xml by text editor, Find the line that says <EasyWakeupMotion name="Double_Touch" support="1" value="0" flag="0" keycode="131" /> and change the value=0 to value=1 then save your changes.
7) Restart your phone
4) Go into Settings/Smart Assistance/Motion Control and you will see Double Touch appear in SCREEN GESTURES section, Turn it on.
now you have working duble tap to wake.
test it on nougat rom on L29C185B520, C636B521 and AL10C00B577, DL00, but may also work on other variants as well.
Important Note:
source and all info and steps too from@ajsmsg78 from his thread i just change one thing this line (ro.config.hw_...............) place, this line already exist in "MM" rom buld.prop, but missing from "N" rom buld.prop.
Source
ajsmsg78 thread:
https://forum.xda-developers.com/mate-8/general/enable-double-tap-to-wake-t3312676
sorry guys about my weak language
Double tap interfers with pocket mode so be careful
hamadazh said:
hi guys
Enable duble tap to wake on N rom
Requirements:
1) Be Rooted
2) need app like root explorer or ES file explorer file manager, or what ever you like.
3) go to system/buld.prop then first Press mount r/w then open buld.prop by text editor.
4) copy this line ro.config.hw_easywakeup=true and put it in the bottom of the page in a new line this line is missing in buld.prop in nougat rom but not in MM rom
5) save your change.
6) Go to system/emui/base/xml and open up that file hw_easywakeupmotion_config.xml by text editor, Find the line that says <EasyWakeupMotion name="Double_Touch" support="1" value="0" flag="0" keycode="131" /> and change the value=0 to value=1 then save your changes.
7) Restart your phone
4) Go into Settings/Smart Assistance/Motion Control and you will see Double Touch appear in SCREEN GESTURES section, Turn it on.
now you have working duble tap to wake.
test it on nougat rom on L29C185B520, C636B521 and AL10C00B577, DL00, but may also work on other variants as well.
Important Note:
source and all info and steps too from@ajsmsg78 from his thread i just change one thing this line (ro.config.hw_...............) place, this line already exist in "MM" rom buld.prop, but missing from "N" rom buld.prop.
Source
ajsmsg78 thread:
https://forum.xda-developers.com/mate-8/general/enable-double-tap-to-wake-t3312676
sorry guys about my weak language
Click to expand...
Click to collapse
Hi,wich Twrp and Root Method to you use?
Thanks
letschky said:
Hi,wich Twrp and Root Method to you use?
Thanks
Click to expand...
Click to collapse
this root
https://forum.xda-developers.com/mate-8/general/guide-root-nougat-android-7-0-mate-8-t3516411
this twrp
https://forum.xda-developers.com/mate-8/development/unofficial-twrp-3-0-3-0-mate-8-t3524025
Thanks, but I can not install root,Error 1in superuser-r275.zip ,When I flash in twrp 3.0.3,what can i do?
letschky said:
Thanks, but I can not install root,Error 1in superuser-r275.zip ,When I flash in twrp 3.0.3,what can i do?
Click to expand...
Click to collapse
i used this method
https://forum.xda-developers.com/showpost.php?p=70249439&postcount=78
By hamadazh
build.prop
Did you share your image
saitercan said:
By hamadazh
build.prop
Did you share your image
Click to expand...
Click to collapse
of course
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
By hamadazh
The same to me
But double touch is not working
saitercan said:
By hamadazh
The same to me
But double touch is not working
Click to expand...
Click to collapse
can you make screen shot from your (buld.prop)
and also (hw_easywakeupmotion_config.xml)
version b596.
systemless way.
magisk + prop config module.
works with set a new custom prop in terminal.
no need to edit xml.
the option will be there after added the prop.

Categories

Resources