Related
I got my 10 today after waiting since it was released. On thing that got me was the ugly NFC icon, it is horrible!
Right bare with me...
You need a working ADB setup
Code:
Tap Settings > About > Software Information > More
Keep tapping build number until you're told you're a developer.
Plug your phone into your computer and open command prompt in your ADB folder. Type:
Code:
adb devices
You should see your device show up. Following this type
Code:
adb shell settings put secure icon_blacklist [comma separated codes here] && adb reboot
For example, if you want to get rid of the NFC icon and the Bluetooth icon your command would look like this:
Code:
adb shell settings put secure icon_blacklist nfc,bluetooth && adb reboot
Note the lack of space between the NFC and Bluetooth commands.
That's it; Done!
Enjoy a less cluttered status bar!
Edit:
Omar302 reminded me that you can hide other status bar icons using this method. This is a (likely incomplete) list of icons
Code:
Name Settings Description
cast Cast
hotspot Hotspot
bluetooth Bluetooth
zen Do not disturb
alarm_clock Alarm
managed_profile Work profile
wifi Wi-Fi
ethernet Ethernet
mobile Cellular Data
airplane Airplane Mode
One more thing worth noting:
omar302 said:
Note: Hiding an icon will cause the other icons to re-appear, so you will need to make the command to hide all your iccons with one command. Separate names of the icons with a comma ",".
Click to expand...
Click to collapse
So if you are tweaking the status bar one by one, keep a copy of your command in notepad
Thanks a lot. from your post I was able to search & find this post & this page. I was able to hide the Bluetooth & alarm clock icons using this command:
Code:
adb shell settings put secure icon_blacklist bluetooth,alarm_clock
Note: Hiding an icon will cause the other icons to re-appear, so you will need to make the command to hide all your icons with one command. Separate names of the icons with a comma ",".
omar302 said:
Thanks a lot. from your post I was able to search & find this post & this page. I was able to hide the Bluetooth & alarm clock icons using this command:
Code:
adb shell settings put secure icon_blacklist bluetooth,alarm_clock
Note: Hiding an icon will cause the other icons to re-appear, so you will need to make the command to hide all your iccons with one command. Separate names of the icons with a comma ",".
Click to expand...
Click to collapse
Cheers!
I've updated the OP ?
This doesn't appear to work in Nougat
winkins01 said:
This doesn't appear to work in Nougat
Click to expand...
Click to collapse
I'm a peasant who's still on Marshmallow (has xposed sdk 24 been released?), I don't have Nougat to mess around with. I'll update the title accordingly.
I just tried this on latest WWE Nougat (2.41.401.3) and it works.
Just a heads up, setting this to only `nfc,bluetooth` will enable the "rotate" icon (which shows if auto rotate is enabled). I had to also include the `rotate` setting to blacklist it. I think a complete list of available icons is listed here: https://android.googlesource.com/pl...nougat-release/core/res/res/values/config.xml
ramonmaruko said:
I just tried this on latest WWE Nougat (2.41.401.3) and it works.
Just a heads up, setting this to only `nfc,bluetooth` will enable the "rotate" icon (which shows if auto rotate is enabled). I had to also include the `rotate` setting to blacklist it. I think a complete list of available icons is listed here: https://android.googlesource.com/pl...nougat-release/core/res/res/values/config.xml
Click to expand...
Click to collapse
Thanks. I did not notice this as I usually leave auto rotate on. Turned it off (portrait mode) and the icon appeared. Adding "rotate" to my list removes it along with bluetooth & alarm:
Code:
adb shell settings put secure icon_blacklist bluetooth,alarm_clock,rotate
Would be nice if someone would check what is the defaul black list before making anychanges by running this command:
Code:
adb shell settings get secure icon_blacklist
Also, maybe OP could modify the title to show this also works in Nougat.
omar302 said:
Thanks. I did not notice this as I usually leave auto rotate on. Turned it off (portrait mode) and the icon appeared. Adding "rotate" to my list removes it along with bluetooth & alarm:
Code:
adb shell settings put secure icon_blacklist bluetooth,alarm_clock,rotate
Would be nice if someone would check what is the defaul black list before making anychanges by running this command:
Code:
adb shell settings get secure icon_blacklist
Also, maybe OP could modify the title to show this also works in Nougat.
Click to expand...
Click to collapse
Thanks, it works with latest EU Nougat.
Result of command before making any changes is:
Code:
adb shell settings get secure icon_blacklist
null
And is there any way to hide boomsound and night mode icons?
I'm on N and the alarm icon is finally gone (YAY!), but it didn't work for the NFC icon. Maybe on N it's not just nfc for the command?
dragunbayne said:
I'm on N and the alarm icon is finally gone (YAY!), but it didn't work for the NFC icon. Maybe on N it's not just nfc for the command?
Click to expand...
Click to collapse
On Samsung use command nfc_on instead of nfc
fritshobbe said:
On Samsung use command nfc_on instead of nfc
Click to expand...
Click to collapse
Thanks for the tip, but it did not work.
dragunbayne said:
Thanks for the tip, but it did not work.
Click to expand...
Click to collapse
Worked for me on S7 Edge Nougat if this helps anyone else or maybe I got lucky.
I ran: adb shell settings put secure icon_blacklist nfc_on,alarm_clock,rotate && adb reboot
Techknowledgy23 said:
Worked for me on S7 Edge Nougat if this helps anyone else or maybe I got lucky.
I ran: adb shell settings put secure icon_blacklist nfc_on,alarm_clock,rotate && adb reboot
Click to expand...
Click to collapse
I will give it a shot again tomorrow. I am on the S8+, so that could be my issue.
Sent from my SM-G955U using Tapatalk
dragunbayne said:
I will give it a shot again tomorrow. I am on the S8+, so that could be my issue.
Sent from my SM-G955U using Tapatalk
Click to expand...
Click to collapse
It worked for me on my S8+. I had to reboot the phone though, also I'm on AT&T I read elsewhere that some of the icons are different by carrier, not sure if that'd have any impact on the name of the icon though.
cmullinstu said:
It worked for me on my S8+. I had to reboot the phone though, also I'm on AT&T I read elsewhere that some of the icons are different by carrier, not sure if that'd have any impact on the name of the icon though.
Click to expand...
Click to collapse
Good to know! Work has been busy, we've been doing a bunch in infrastructure updating, so I haven't been able to try again.
Sent from my SM-G955U using Tapatalk
is there one for VPN?
Cryosx said:
is there one for VPN?
Click to expand...
Click to collapse
Came here looking for this too. Will update if I find it.
I'm using this new app to hide status bar icons: https://forum.xda-developers.com/android/apps-games/app-systemui-tuner-t3588675
It works really well.
Is there a possibility to access this in a build prop Editor? Or only in ADB?
D_JWhite said:
I got my 10 today after waiting since it was released. On thing that got me was the ugly NFC icon, it is horrible!
Right bare with me...
You need a working ADB setup
Code:
Tap Settings > About > Software Information > More
Keep tapping build number until you're told you're a developer.
Plug your phone into your computer and open command prompt in your ADB folder. Type:
Code:
adb devices
You should see your device show up. Following this type
Code:
adb shell settings put secure icon_blacklist [comma separated codes here] && adb reboot
For example, if you want to get rid of the NFC icon and the Bluetooth icon your command would look like this:
Code:
adb shell settings put secure icon_blacklist nfc,bluetooth && adb reboot
Note the lack of space between the NFC and Bluetooth commands.
That's it; Done!
Enjoy a less cluttered status bar!
Edit:
Omar302 reminded me that you can hide other status bar icons using this method. This is a (likely incomplete) list of icons
Code:
Name Settings Description
cast Cast
hotspot Hotspot
bluetooth Bluetooth
zen Do not disturb
alarm_clock Alarm
managed_profile Work profile
wifi Wi-Fi
ethernet Ethernet
mobile Cellular Data
airplane Airplane Mode
One more thing worth noting:
So if you are tweaking the status bar one by one, keep a copy of your command in notepad
Click to expand...
Click to collapse
How can I hide the vpn icon and carrier name?
DISCLAIMER: This guide was NOT made by me, I'm simply sharing this here because it's really useful IMO.
This is a guide made by reddit user turkcem421, on how to take advantage of this beautiful 18:9 aka 2:1 display.
Here's the link https://www.reddit.com/r/lgg6/comments/7bqy5r/guide_fullscreen_immersive_mode_with_gesture/
And some screenshots...
Very interesting, thank you. I was also looking for a way to do this after playing with a friend's iPhone X and realizing how outdated a navigation bar now feels.
I was on a different path. Instead of enabling immersive mode, my goal is to disable the soft keys entirely. This requires editing build.prop, which requires root, which I can't get on my H870DS. However it seems to be possible to edit it with adb as well, was going to try that next.
EDIT: file system is read-only, doesn't work with adb.
Also, there's an app called Pie Control that can provide gesture navigation controls and is very elegant IMHO. My goal is to use that as a replacement for soft keys.
Hi crabnebula,
Author of the reddit guide here. I actually tried the adb build.prop approach also! It was pretty tough to write it to the system successfully (as you noticed, there are a lot of weird things on the backend of the LG G6 compared to the Nexus phones that I am used to) but eventually I did manage to write it and chmod it by combining a lot of tricks I learned hereHowever it did not have any effect, i.e. the LG G6 ROM does not seem to care about what that line of build.prop says and just shows the buttons anyway. After that failure I ended up figuring out the solution that I put in the guide.
Pie controls looks nice too, I was considering it. There are two things I like about all-in-one gestures though that to my knowledge are not in the others (but I have not checked thoroughly)
1) all in one gestures includes both gesture controls and immersive mode in the same app, and the immersive mode also has a built-in fix to let the keyboard work (see my guide). I don't know another way to have immersive mode with a working keyboard, and it is also really handy that it's all one app, i.e. if for any reason the app crashes or is stopped then the nav bars also come back when the gesture controls stop working.
2) there is an 'alt-tab' functionality, comparable to double tapping on multitasking button. Very handy to do this with a single swipe. I didn't see any other apps that had this (but maybe I did not look hard enough)
@yilun thanks for posting the guide here!
Thank you! The UI looks so much better without the nav-bar and status bar there to interfere. ^^
turkcem421 said:
Hi crabnebula,
Author of the reddit guide here. I actually tried the adb build.prop approach also! It was pretty tough to write it to the system successfully (as you noticed, there are a lot of weird things on the backend of the LG G6 compared to the Nexus phones that I am used to) but eventually I did manage to write it and chmod it by combining a lot of tricks I learned hereHowever it did not have any effect, i.e. the LG G6 ROM does not seem to care about what that line of build.prop says and just shows the buttons anyway. After that failure I ended up figuring out the solution that I put in the guide.
Pie controls looks nice too, I was considering it. There are two things I like about all-in-one gestures though that to my knowledge are not in the others (but I have not checked thoroughly)
1) all in one gestures includes both gesture controls and immersive mode in the same app, and the immersive mode also has a built-in fix to let the keyboard work (see my guide). I don't know another way to have immersive mode with a working keyboard, and it is also really handy that it's all one app, i.e. if for any reason the app crashes or is stopped then the nav bars also come back when the gesture controls stop working.
2) there is an 'alt-tab' functionality, comparable to double tapping on multitasking button. Very handy to do this with a single swipe. I didn't see any other apps that had this (but maybe I did not look hard enough)
@yilun thanks for posting the guide here!
Click to expand...
Click to collapse
Thank you for the reddit guide and the further information. I really appreciate that you took the time to share!
Guess I'll give up on the build.prop setting.
After playing with AIO Gestures a little more, I have to agree with you. The combination of features makes it more useful and I actually prefer the way it works when using both the bottom edge and corners to replace the 3 usual soft keys, instead of a pie menu.
The only issue I have is that the phone seems to drop out of immersive mode when returning to the launcher and certain apps, but it's a minor nuisance.
I'm hoping that in a next version of Android and/or in future OEM updates, they are going to introduce native gesture-based navigation, at least as an option. In the meantime, it's great to have an alternative that works without root. Thanks again!
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
Greenify doesn't help me with battery drain, anyway this tip solve my problems. Thanks a lot!
Happy to help
How can I disable it?
victor19 said:
How can I disable it?
Click to expand...
Click to collapse
You mean revert the whole process?
You can do it one by one manually, but I'd recommend just making a backup and factory resetting.
The other way is extremely time consuming and not very practical at all.
PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
I updated my immersive mode with the above command and did a reboot.
Solved my battery drain and heat problems immediately.
THANKS!!!
victor19 said:
How can I disable it?
Click to expand...
Click to collapse
adb shell settings put global policy_control null*
Just like that
I have set it up correctly but have a few questions. Is op possible to disable the navbar completely everytime i swipe up to go home from the buttom. The navbar shows up and is in the way. And is it possible to disable the white glow on the screen from the all in one gestures app?
To disable glow go to "personalization" > "edge preference" and set "opacity" to 0%.
PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
Does this solve all the apps that don't support 18:9? Is there a way to tell if there are other apps that cause it?
Sent from my LG-H870 using Tapatalk
tanguita said:
Does this solve all the apps that don't support 18:9? Is there a way to tell if there are other apps that cause it?
Sent from my LG-H870 using Tapatalk
Click to expand...
Click to collapse
This will solve the battery drain. If you need to take off another app from the inmersive just added to the line. ,-app
PinG91 said:
This will solve the battery drain. If you need to take off another app from the inmersive just added to the line. ,-app
Click to expand...
Click to collapse
Indeed it does... I screwed up mixing the command with the immersion from aiog (which activated immersion for everything). Thanks again!
Sent from my LG-H870 using Tapatalk
PinG91 said:
I'm using something like this since 3 weeks. What I've did to get the immersive screen was all in adb code. What is causing the battery drain is Google apps that won't support 18:9 mode so you have to exclude them from immersive. You can still use youtube modded APK (18:9 support) and Chrome beta to get full screen.
The adb code is
adb shell settings put global policy_control immersive.navigation=apps,-com.android.chrome,-com.android.vending,-com.google.android.gm,-com.google.android.googlequicksearchbox
I use aiog too.
Click to expand...
Click to collapse
So if you force immersive this way, you still need to use AIOG with the special settings applied through adb in order for the keyboard to function in immersive mode, or do you only use AIOG for the actual gestures?
crabnebula said:
So if you force immersive this way, you still need to use AIOG with the special settings applied through adb in order for the keyboard to function in immersive mode, or do you only use AIOG for the actual gestures?
Click to expand...
Click to collapse
Just for gestures. There is no need of touching any setting for immersive on AIOG.
Can't believe how simple that all was. Only thing I couldn't do was the SVC for ls993. Literally no one has it, spend 25 min looking and 5 minutes going through the tutorial.
Only issue I know is that some apps have a very small black sliver on the bottom, is this due to not forcing long display through the SVC? Does anyone know the SVC for ls993???
Either way, the rest works 1000x better than I expected and the battery drain solutions are terrific.
Home screen looks super good too
I've put together a Tasker project (based on the information I found in this post) which allows the OP5's capacitive button backlights to be kept on all the time and to easily be switched back and forth between different states, via either a popup dialog or quick settings tile. I've only used it on Android OOS versions of Oreo 8.1 and I have no idea if it works on Pie.
Once the project has been downloaded and imported, follow these steps to get things working and looking right:
If you plan to use the popup, set a shortcut to open the task "Backlight Status Control With Icons", this will open up a dialog from which you can choose how you want the backlights to behave. There's also a profile and tasks included to set up a quick settings tile to cycle through the different settings. The dialog and quick settings tile can be used alongside each other, as can the native settings app, nothing should cause conflicts.
Dialog / Scene icons: You can use the dialog as-is, but it'll look stupid and you'll get laughed at, which is why I've uploaded icons for you to add to it. It isn't hard to do. First, download the attached icons zip file and extract it wherever. In Tasker, open the scene "Backlights Menu" for editing and click on the "AZ" icon at the bottom left. This will open a list of all the scene elements. There are three icon elements, open these one at a time and point them to the corresponding icons from the extracted zip (Image>>Local Media>>extracted folder). There are also three dividers which all use the icon "divider.png", plug these in and you're all set!
Quick Settings tile: The profile and task I set up cycle the button backlights through each of the three states (default>>always on>>always off). To set a custom QS tile, pull down quick settings and click on the pencil icon at the bottom right to open it for editing. On the bottom half of the screen are the unused tiles. Tasker has three tiles available to use, the one farthest to the right is number three, and that's the one I've set up the profile to use. (If you're already using that one, open up the tasks "Backlights QS Tile", "Backlight Reset QS Tile" and "Backlights Kill QS Tile" and edit the actions in those so they don't conflict with your current setup.) Drag that one to the top half of the screen where the active tiles are, get everything arranged how you want it and then back out and go and open up Tasker. Import the project if you haven't already. Tap on the task ""Backlights Reset QS Tile" to open it and tap the play icon at the bottom left. The tile should now be initialized.
Recommended: I put a couple icons in the zip for the QS tile, "icon_default.png" and "icon_off.png". They should be added to the tasks "Button Backlights Off" (icon_off.png), "Button Backlights On" (icon_default.png), and "Button Backlights Default" (icon_default.png). Add them by opening each task for editing, clicking the grid icon at the bottom of the screen, and then navigating to the extracted icons (Local Media>>extracted icons folder).
Hello, Thanks for the work.
Do you know if it is possible to increase the brightness?
AlexCmb said:
Hello, Thanks for the work.
Do you know if it is possible to increase the brightness?
Click to expand...
Click to collapse
I'm absolutely sure I did find something involving scripts to adjust the brightness, but right now I can't seem to find it, I'll let you know if I do.
OK, I'll go ahead and upload the continuation of my work. It's a Tasker project which, when triggered, pops up a dialog with the options of setting the backlights always on, always off, or the default behavior; basically just a cleaner and easier way to toggle the settings back and forth. It also forces the lights off almost as soon as the screen turns off, as well as when the daydream/screen saver kicks in. I would love to export this as an apk, but I haven't managed to make that work, so Tasker (and root) are required.
Import the project into Tasker and set a shortcut/trigger for the task "Backlight Status Control", it's pretty much self-explanatory from there.
Update: Figured out how to get App Factory to work, so now there's an installable apk for those who don't have Tasker installed. Still requires root, of course, and I would also recommend turning off battery optimization for the app and clearing caches, it behaved a bit strangely before I did that. If you have Tasker, I recommend importing the project anyway as it seems to run just a touch faster.
All links are in the OP.
New version up, the main difference is that the chosen state survives a reboot whereas before rebooting with the lights set to Always On caused the lights to actually be always off when the device restarted. I probably fussed with the icons a bit as well, can't remember if I had already done that or not.
Links are in the first post.
And another one. This version fixes two things. First, it only keeps the profiles active when they're actually needed rather than all the time, giving you probably a minute or two of extra battery life. And then it (hopefully) fixes the last potential conflicts when switching states in the device's settings app rather than this project's dialog. This required an extra one each of profile, task and variable as well as adding some actions to a few existing tasks.
As of right now, I'm only uploading xml's, as the exported apk's have been unstable when I've tested them on my device. If you really want to try it and don't have Tasker installed, pm me and I'll send you the app to install at your own risk.
Anyone who has downloaded and imported the xml may have correctly guessed that I don't have a whole lot of experience with Tasker. I would like to take this opportunity to invite anyone who has noticed something that could be done better and/or differently to give me honest feedback. As simple as this project is, it has nevertheless been frustrating at times and I would love to have the benefits of others experience.
Can't import, Tasker says the project "contained bad data." File seemed to download fine, 41.83 kb.
smalis said:
Can't import, Tasker says the project "contained bad data." File seemed to download fine, 41.83 kb.
Click to expand...
Click to collapse
Sorry to hear it's not working for you. I've successfully downloaded and imported the project using two different devices, so the file itself doesn't seem to be the problem. It's possible, of course, that your download somehow got mangled along the way, so if you haven't already, try downloading it again and see what happens.
And... I'm honestly not sure what other advice to give you. Google just turned up really basic stuff like making sure you're not in beginner mode and that you're not actually trying to import it as a task or profile, stuff like that.
Tasker can be massively frustrating and picky, and I'm far from being an expert on it. Considering this is the first real feedback I've gotten on this thread, I don't know if anyone else has had similar issues, I just assumed no news is good news and that it works for everyone who's tried it. If anyone else has any ideas about why this would happen, feel free to share!
New xml up. No new functionality, I just debloated and cleaned things up a bit. Instructions in the first post still apply.
Updated xml now with HAPTIC FEEDBACK omg lol! Also changed/added quite a bit of stuff to hopefully make it run a bit more efficiently in the background, so a few less toast notifications and magisk log entries to look at, otherwise nothing really noticeable.
EDIT: Apologies to those who already downloaded the new one, but I just updated the update :/ Maybe it's just placebo, but it feels like decreasing the vibrate duration made it feel a bit more responsive, no need to redownload if you're already happy with it.
Any screenshots of this same in action?
arvindgr said:
Any screenshots of this same in action?
Click to expand...
Click to collapse
I mean, the buttons aren't actually on the screen so no, I can't really screenshot how it looks. If you want a screenshot of the dialog box that you use to choose the state, then sure, I can do that...
{
"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"
}
I totally forgot that Tasker lets you set Quick Settings tiles! So I've uploaded a new version that can set up a quick tile to cycle through the button states, it's disabled by default and naturally requires a bit of work to get it going but the instructions are, as usual, in the first post along with the attachments. Note that if you're going to use the quick tile you might also want to download the new icons.zip as well, check out the instructions and screenshots to see how it looks. Otherwise the only other change is the dialog pop-up got a bit smaller and very slightly transparent, there's a screenshot of that as well to help you decide if it's worth the bother.
EDIT: If you had problems with the QS tile not cycling through the settings correctly, download the newest version, it seems to have fixed it. Sorry for the inconvenience.
New one up. The last version was inconsistent updating the QS tile when setting the lights from the settings app. Let's see how I screwed up this one then. Link and instructions in the first post, blablabla...
Another week, another try to make the QS tile behave the way I want. Seems to be working over the last days of testing it, but then I say that every time. I also changed some task names so that the labels under the QS icons are accurate, and I uploaded a new icon zip with icons that imo look better in the OOS beta builds, the ones for the stable builds are still in there as well. You guys are smart, you'll figure it out.
Hi, I'm quite new with the Tasker projects! I have tried this one on my Xiaomi Redmi Note 4x (Android 7.0 Xiaomi.eu) and Samsung Galaxy Note 2014 Edition (LineageOS 14.1). I wanted to achieve buttons backlight when charger plugged in, but without screen waking. On Xiaomi it seems to work fine, but on Samsung I ended up with the error:
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/Shell runBackground echo 1 > /sys/class/leds/button-backlight/brightness root: true timeout: -1
16.48.31/Shell start process-thread ID 341
16.48.31/E add wait type Shell1 time 2147483647
16.48.31/E add wait type Shell1 done
16.48.31/E add wait task
16.48.31/E Error: 1
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Lord Sithek said:
Hi, I'm quite new with the Tasker projects! I have tried this one on my Xiaomi Redmi Note 4x (Android 7.0 Xiaomi.eu) and Samsung Galaxy Note 2014 Edition (LineageOS 14.1). I wanted to achieve buttons backlight when charger plugged in, but without screen waking. On Xiaomi it seems to work fine, but on Samsung I ended up with the error:
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/E Run Shell: ->
16.48.31/Shell runBackground echo 1 > /sys/class/leds/button-backlight/brightness root: true timeout: -1
16.48.31/Shell start process-thread ID 341
16.48.31/E add wait type Shell1 time 2147483647
16.48.31/E add wait type Shell1 done
16.48.31/E add wait task
16.48.31/E Error: 1
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Click to expand...
Click to collapse
You're in a wrong thread and possibly wrong forum too. This is about AoD on OxygenOS, not MIUI or LOS or Tasker.
Thanks, you helped me a lot :good:
david19au said:
You're in a wrong thread and possibly wrong forum too. This is about AoD on OxygenOS, not MIUI or LOS or Tasker.
Click to expand...
Click to collapse
I mean, "Tasker" is in the thread title... And this thread is about the capacitive button backlights, which is what Lord Sithek is asking about, not AoD.
Lord Sithek said:
Can somebody explain me in a simple manner, what is wrong? I'm still begginer with Tasker ?
Click to expand...
Click to collapse
Sorry, I don't think I can help you, I don't really know that much about shell commands and definitely can't troubleshoot for an unfamiliar device. You'd be better off trying the Tasker forums on XDA or /r/tasker. Good luck!
Oh, thanks, it's a nicer reply It's true I rushed a little bit, I just googled "Tasker buttons backlight" and I didn't check what device is actually considered I'm still newbie here, but I want to learn more :cyclops: Thanks for the links, I will check the threads :good:
I haven't updated this in a few months because it more or less worked; however, I still encountered problems with the quick settings tile not cycling properly after a reboot, as well as Tasker throwing errors, although these didn't seem to affect functionality. Anyway, I had a few days off during the holidays and was able to stop the errors from occurring as well as come up with a workaround (although not a real solution) for the problems I had with the qs tile. And so, I present what should be the final version of this mod. Link in the first post, along with setup instructions.
Btw, anyone tried this with Pie? I'm not planning on making the jump anytime soon, so I'm just curious if it works or not.
Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc Files/Magisk Modules/Two-Button Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.
Is there any way to bypass the adb command since you're using a Magisk module? Does it persist through reboots? Is there a way to run the command via the su command using a terminal emulator on the device rather than using a pc to issue the adb command?
TheKnux said:
Is there any way to bypass the adb command since you're using a Magisk module? Does it persist through reboots? Is there a way to run the command via the su command using a terminal emulator on the device rather than using a pc to issue the adb command?
Click to expand...
Click to collapse
I'm a noob at Magisk modules and couldn't figure out how to pass the ADB command during the flashing process. I'm hoping I can do a v2.0 and get that in there down the road though!
But yes, it persists through reboots. The only times it will get wiped is if you update your option in Settings, or if you flash a system update.
And I could see a terminal emulator working, I just haven't tried it myself yet.
rwilco12 said:
Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc+Files/Magisk+Modules/OnePlus+Oxygen+OS+11+-+Two-Button+Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.
Click to expand...
Click to collapse
TY @rwilco12 but a thread was already initiated if I'm not wrong here : https://forum.xda-developers.com/t/how-to-enable-two-button-navigation.4260373/
Fre$h said:
TY @rwilco12 but a thread was already initiated if I'm not wrong here : https://forum.xda-developers.com/t/how-to-enable-two-button-navigation.4260373/
Click to expand...
Click to collapse
Lol I totally missed that post! I appreciate him sharing my video! The modules I posted here are different than the one he attached to his post. Same net effect, just more options.
rwilco12 said:
Hey friends! I don't know about you guys, but I really dislike the latest implementation of Gesture Navigation and the old 3-Button Navigation bar makes me feel like I'm stuck back on Ice Cream Sandwich! It made me really sad when Google forced all the OEMs to ditch 2-Button Navigation. Fortunately, we can now get it back! Even on Android 11!!
You will need USB Debugging enabled on your phone and ADB installed on your computer. You will also need your phone to be rooted with the latest version of Magisk installed.
It's a super easy process and all it takes is installing one Magisk module and an ADB command. I've created two versions of the module, one with the standard height nav bar and another with a shorter one that takes up less space on the display. You can find both versions of the module here: https://www.rwilco12.com/downloads.php?dir=Files/Misc+Files/Magisk+Modules/OnePlus+Oxygen+OS+11+-+Two-Button+Navigation
After installing the module, all you have to do is go into ADB and run this command.
adb shell cmd overlay enable com.android.internal.systemui.navbar.twobutton
Here's a helpful video we recorded that should help you through the process.
Click to expand...
Click to collapse
OP, in theory, do you think it would be possible to somehow disable onepluses built-in navigation gestures, but keeping the 'hide nav bar' feature that goes along with it? I ask this because, I'd love to use a third party app to do navigation gestures. The built-in gestures have this annoying animation when you swipe up from bottom or swipe from the sides. It's subtle and it's very brief but it's there. And my OCD wants to get rid of it. Fluid navigation gestures for example is very clean and you don't see an animation when you use any sort of gesture navigation. It looks so much sleeker and snappier.
Burt Squirtz said:
OP, in theory, do you think it would be possible to somehow disable onepluses built-in navigation gestures, but keeping the 'hide nav bar' feature that goes along with it? I ask this because, I'd love to use a third party app to do navigation gestures. The built-in gestures have this annoying animation when you swipe up from bottom or swipe from the sides. It's subtle and it's very brief but it's there. And my OCD wants to get rid of it. Fluid navigation gestures for example is very clean and you don't see an animation when you use any sort of gesture navigation. It looks so much sleeker and snappier.
Click to expand...
Click to collapse
In theory, yes, it is totally possible. I was able to do two different heights for the modules. Somebody could make one that has no height or even one that just never generates. That is beyond my skillset though. So in theory, yes, it is possible. Could I do it? Probably not.
What would be for me a better thing is just to be able to engage the gesture mode for the apps to be in full screen ( without the navbar) but with the navbar button's available too. A sort of weeding between a kingsize display with the usefull part of those buttons that I keep want to use for some reasons
Fre$h said:
What would be for me a better thing is just to be able to engage the gesture mode for the apps to be in full screen ( without the navbar) but with the navbar button's available too. A sort of weeding between a kingsize display with the usefull part of those buttons that I keep want to use for some reasons
Click to expand...
Click to collapse
Agreed!
Hello, did you remove the module? The directory is empty(
OnePlus Oxygen OS 11 - Two-Button Navigation (SHORT)
And
OnePlus Oxygen OS 11 - Two-Button Navigation (STANDARD)
bgkone said:
Hello, did you remove the module? The directory is empty(
Click to expand...
Click to collapse
Sorry about that, I must've posted the wrong link. I've updated it in the OP. Thanks!
Update: This only works if you are rooted now, since the January 2022 patch.
Hi guys, I've seen several posts asking how to remove the Gesture Pill. It's easy if you're rooted, but it's also possible if you're not rooted.
Here is a step by step guide. There is also a huge amount of UI mods that can be made using the same method.
1. Download the Shizuku app from the Playstore
2. Start the Shizuku app by running the following adb command:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
3. Download and install FabricateOverlay release from Github.
4. In FabricateOverlay click “Add Overlay”
5. Choose Android System
6. Click “Add”
7. Set “android:dimen/navigation_bar_height” to 1. Apply. Save. Tick.
8. Set “android:dimen/navigation_bar_frame_height” to 0. Apply. Save. Tick.
9. Enjoy!
Let me know in the thread if anything is unclear.
Thanks to @squee666 for an alternative solution that does not affect the keyboard! Try it out!
Credits:
Zachary Wander for the FabricateOverlay app and the instructions.
RikkaW for the Shizuku Api.
MishaalRahman, Quinny898 and various Redditors (especially LankeeM9 and audie-tron171) for the relevant settings.
Very nice, thank you for this!
Points 8 and 9 xan you be more specific.
Damn, it's too bad that the overlay system can't change fonts. I don't even want to install custom fonts, I just want to change the system default to the new Google font instead of Roboto. Without root.
Can we enable Fluid Navigation Gestures after applying a similar tweak?
tids2k said:
Points 8 and 9 xan you be more specific.
Click to expand...
Click to collapse
Basically you need to search "android:dimen/navigation_bar_height" by entering it in the search box. Then click on it. Then add the value in the value box and click "Apply". There are screenshots showing how it works here.
StrangerWeather said:
Basically you need to search "android:dimen/navigation_bar_height" by entering it in the search box. Then click on it. Then add the value in the value box and click "Apply". There are screenshots showing how it works here.
Click to expand...
Click to collapse
Thank you figured out eventually.
Guyinlaca said:
Can we enable Fluid Navigation Gestures after applying a similar tweak?
Click to expand...
Click to collapse
What do you mean?
Great! It works. Thanks!
But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.
foobar66 said:
But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.
Click to expand...
Click to collapse
Good point. However, you just need to swipe back for the keyboard to disappear.
StrangerWeather said:
Hi guys, I've seen several posts asking how to remove the Gesture Pill. It's easy if you're rooted, but it's also possible if you're not rooted.
Here is a step by step guide. There is also a huge amount of UI mods that can be made using the same method.
1. Download the Shizuku app from the Playstore
2. Start the Shizuku app by running the following adb command:
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
3. Download and install the latest FabricateOverlay release from Github
4. In FabricateOverlay click “Add Overlay”
5. Choose Android System
6. Click “Add”
7. Set “android:dimen/navigation_bar_height” to 0. Apply. Save. Tick.
8. Set “android:dimen/navigation_bar_frame_height” to 0. Apply. Save. Tick.
9. Enjoy!
Let me know in the thread if anything is unclear.
Credits:
Zachary Wander for the FabricateOverlay app and the instructions.
RikkaW for the Shizuku Api.
MishaalRahman, Quinny898 and various Redditors (especially LankeeM9 and audie-tron171) for the relevant settings.
Click to expand...
Click to collapse
What is the workaround for me that im rooted?
foobar66 said:
But there seems to be one down-side ... when you enable the overlay the Google keyboard does not longer show the "down" marker to make the keyboard disappear. The android:dimen/navigation_bar_frame_height (0) is causing that. See attached 2 screenshots. First one is without overlay enabled, second one has overlay enabled. Notice how the little downward pointing arrow is gone on the second one.
Click to expand...
Click to collapse
It might be possible to increase the bottom margin of the keyboard in system.ui. I'll check in a bit.
Edit: Actually, the handle is part of the navbar, which is the reason why it disappears when removing the navbar.
cultofluna said:
What is the workaround for me that im rooted?
Click to expand...
Click to collapse
Just open the Shizuku app and press "Start" in "Start (for rooted devices)".
So on Android 10, there was an overscan feature that allowed the 3 button navigation to be hidden and replaced with 3rd party navigation apps such as Fluid Navigation Gestures. This allowed swipe up from the bottom navigation much like OnePlus and Samsung offer. My curiosity is if this mod allows third party apps the hide and utilize the navbar.
Guyinlaca said:
So on Android 10, there was an overscan feature that allowed the 3 button navigation to be hidden and replaced with 3rd party navigation apps such as Fluid Navigation Gestures. This allowed swipe up from the bottom navigation much like OnePlus and Samsung offer. My curiosity is if this mod allows third party apps the hide and utilize the navbar.
Click to expand...
Click to collapse
Only if they integrate the Shizuku library into their app afaik.
I can confirm this working on my Pixel 3 XL on Android 12, no root, locked bootloader. Thank you so much for this!
StrangerWeather said:
Good point. However, you just need to swipe back for the keyboard to disappear.
Click to expand...
Click to collapse
Aha yes ... if you swipe above the keyboard it goes away ... did not know that! Thanks for that tip.
One question, how come that this sticks after reboot (even when disabling Shizuku/FabricateOverlay)?
foobar66 said:
One question, how come that this sticks after reboot (even when disabling Shizuku/FabricateOverlay)?
Click to expand...
Click to collapse
Basically you only need to give the app permission to change the settings (i.e. write to secure settings). Once the system setting is written it sticks. But if you want to change the value again you will need to go through the same process with both apps.