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.
Related
Hello!
I'm an Android developer and I almost finished a new app called Deskbar Launcher.
I created it for many reasons. First I was fed up by the look of the system bar with Home/Back/Recent Apps and the huge waste of space it makes. Like many others I tried alternative solutions like HideBar and the likes but then I looked at my laptop and at its ribbon bar which I use all the time and I thought it would be a good idea to have something similar on Android.
{
"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"
}
Download links are now in the new thread here. If you have any comments, suggestions or problems, please report there. Thanks
Features :
-can replace your soft buttons (sadly Back button needs root, after lots of search I don't think it is possible otherwise)
-add shortcuts to your favorite apps on the bar
-music controllers to go to pause/go to next/previous song in any apps
-volume controllers
-lock button to minimize accidental input of your bar and soft buttons
-access all your apps in StartMenu as well as categories such as Pictures, Music, Settings, etc.
-(experimental)(ROOT)fullscreen mode.
Future features:
-Folders
-Themes
-Reboot button for root users
-etc
I developed it mainly on Nexus7, that's why I post here before releasing it on the Play Store. It is a Trial version of 10days and when you launch it you need internet access for verification, after it's not necessary except if you reload it. A licence key will soon be available.
There might be some bugs!
Questions
Q:I don't have Root and not having a back button is not possible for me, it seems I can't use your app.
Q:I already got rid of my system bar, it will cover screen content so it's not usable for me too.
A: You can! Deskbar Launcher has an autohide feature so you can still access your back button. Bring it up only when it's needed!
Q: I have one bar for soft buttons and notifications (no status bar on top) . Your app will cover the notification part and I won't be able to access my notifications
A. There is a setting especially for that so the Deskbar takes only half your device's width, in the future the width of Deskbar might be more customizable.
Q : Can I use it on my other tablet/phone ?
A. Yes! It is theoretically compatible with all 2.2 or + Android devices! There might be some problems on specific rom or with some manufacturers. Please report to me in this case.
i'll try and report,i haven't mean exactly what does (using it is more intuitive!)
thanks for now mate!
Will be testing this for sure!
Edit
Light usage so far
Pros:
- Quick easy access to your music, photos, and documents
- Completely changes look and feel of the bottom nav bar without need for root or new ROM
- can view and switch to apps of your choice quickly with out exiting current app
- in-depth settings with good amount of customization
- work around for non-rooted users
Cons:
- visual appeal isn't appealing( to me at least)
- nav buttons feel a little too close together
- cannot change the color of the bar
- auto hide feature needs work as it seems finicky
What I would like to see:
- short cuts to user defined app in menu
- options to change colors
- quick toggles in menu (WiFi, Bluetooth, etc...)
Other then that I really like it and its a good change. Will love to see the advancement of this project later down the road! Great work indeed!
Sent from my Nexus 7 using Tapatalk HD
Thanks for your feedback!
About suggestions and bad points:
-Yeah visual appeal is kind of generic, I'm not the best at design/art . Themes should give a workaround for those who don't like it in one of the next updates. (By the way there was a bug with the start button not showing the glowing icon when start menu was displaying . It's fixed in the new version, it's the same download link, uninstall is needed if you have the previous version.
-I plan on adding a setting to have custom distance between buttons because on some device space is precious and on others there's plenty of it.
-Themes should also address this issue
-Not sure what you mean by this, I admit it's not ideal because there's no animation, it just goes down after a 3seconds delay. I will add a smooth movement option in the future.
-user-defined shortcuts in menu is planned, as well as folders containing app shortcuts
-I'll try to add Theming fast
-Quick Toggles is indeed interesting, I'll think of ways to add it in the Menu.
Awesome! I see this as being a good hit
Sent from my Nexus 7 using Tapatalk HD
This damn thing is INTUITIVE. Seriously, I love the feel of it and it really looks quite nice on my N7. Cheers for letting us try this, I think its a really good fit and shows promise of something in the future. Killjoy question: what will the licensing price new?
Im really loving this! I do have have more thing that I would like to see added and that would be having resizeable options for the menu its self. More so users can choose exactly how many pixels the pull up menu actually takes up. I'm also picky like that though.
Sent from my Nexus 7 using Tapatalk HD
Very minor complaint: after about an hour of use, it starts to feel a bit sluggish. That is, I'll tap on home, back it recent and it'll take about a second to respond. I rebooted my tablet and suddenly I got my groove back. Maybe it's a memory issue? Just thought I'd chime in, I'm really enjoying this mod!
Love it so far!
Two little things:
-ability to change icons/icon sets of shortcuts
-expanded version of the menu to see more apps at once
Thanks
Sharpen3d said:
Killjoy question: what will the licensing price new?
Click to expand...
Click to collapse
Lol. 2.49 probably.
Sharpen3d said:
Very minor complaint: after about an hour of use, it starts to feel a bit sluggish. That is, I'll tap on home, back it recent and it'll take about a second to respond. I rebooted my tablet and suddenly I got my groove back. Maybe it's a memory issue? Just thought I'd chime in, I'm really enjoying this mod!
Click to expand...
Click to collapse
I'll need more info on this one, I did not encounter this problem. Was it only the soft buttons ? Did the other buttons (shortcuts, music, startbutton) worked correctly ? Did you add a lot of shortcuts ?
soloman56 said:
Love it so far!
Two little things:
-ability to change icons/icon sets of shortcuts
-expanded version of the menu to see more apps at once
Thanks
Click to expand...
Click to collapse
First is already in the works. For the second one maybe the default size is not big enough ?
Lots of force close on my device, Samsung Showcase. Like the idea though.
Sent from my SCH-I500 using Tapatalk 2
PenguinxEnjoi said:
Lots of force close on my device, Samsung Showcase. Like the idea though.
Sent from my SCH-I500 using Tapatalk 2
Click to expand...
Click to collapse
Hello!
Can you tell me when it's happening and if it's after a precise action ? Could you use the CatLog app (or any similar one) to get me a crash report ? Thanks!
You might be low on memory and the system decide to stop the app to free some.
srelyt said:
I'll need more info on this one, I did not encounter this problem. Was it only the soft buttons ? Did the other buttons (shortcuts, music, startbutton) worked correctly ? Did you add a lot of shortcuts ?
Click to expand...
Click to collapse
Music buttons worked great, as did the launcher button. No shortcuts added. I'm wondering if the error came from my rom or what, I'm running slim bean beta 2 with faux beta 14b01. Haven't had any issues since restarting, maybe it was a fluke?
New version uploaded which uses less memory and has a new welcome screen ( not so well done but I wanted one to have a link to the video tutorial I finished ).
Link updated in OP
Sharpen3d said:
Music buttons worked great, as did the launcher button. No shortcuts added. I'm wondering if the error came from my rom or what, I'm running slim bean beta 2 with faux beta 14b01. Haven't had any issues since restarting, maybe it was a fluke?
Click to expand...
Click to collapse
Maybe, or it's the way to simulate virtual buttons that can sometimes go wrong, it's kind of a hack but there isn't really any alternative. It should work most of the time and as well as similar apps offering virtual buttons alternative.
I have to go, I'll be back tomorrow.
EDIT:I forgot to add if you already installed it, erase app data before uninstalling and installing the new one because the way data was saved as changed.
Greats Job, Please add volume button up/down on navigation bar, thanks
PenguinxEnjoi said:
Lots of force close on my device, Samsung Showcase. Like the idea though.
Click to expand...
Click to collapse
I found what it was, it concerned all devices with Android version under 3.0. It's fixed (new version in OP) except maybe for the "Switch App" button.
Could you test for me or someone else with a device on 2.2/2.3 ? Thanks
brium13 said:
Greats Job, Please add volume button up/down on navigation bar, thanks
Click to expand...
Click to collapse
Added to the todo-list, I'll do it soon I think.
Re: [APP][BETA][TRIAL] DeskBar Launcher will replace your soft buttons and more!
As soon as I noticed the trail 10 days crap I uninstalled it. Sigh. Why can't people do things without money motivating them?
I can see if it was finished but its not even close.
Re: [APP][BETA][TRIAL] DeskBar Launcher will replace your soft buttons and more!
What a great idea. Please keep the 10 day trial available once its more refined, I will definitely try and probably buy.
Sent from my Nexus 7 using xda app-developers app
Re: [APP][BETA][TRIAL] DeskBar Launcher will replace your soft buttons and more!
So far so good. I really like the idea and the way it works. I'll report back if I have any problems.
Sent from under your bed...
So, the nav-bar eating a portion of my screen was bothering me for a while and I wanted my device to rely on gestures only, so I decided to search for the most suitable way for me to solve this problem... LMT of course, but first I got rid of the nav-bar using FullScreen Toggle.
Big thanks to the creators of both those apps
LMT can be found here: http://forum.xda-developers.com/showthread.php?t=1330150
FullScreen Toggle can be found here: http://forum.xda-developers.com/showthread.php?t=1497558
Now, as the title says, I'd like to share with you my LMT configuration. There are many things that I'm currently unable to understand about how LMT should actually be configurated, I just used a trial&error approach, but the result I got is more then decent and worthy of being shared IMO. If I'll get some suggestion on how to improve what I did I hope to turn this post in a clean LMT ISAS guide for the Nexus 4.
PLEASE NOTICE that I didn't want to use the pie and I (almost*) didn't use LMT's gestures. The following configuration is for ISAS only.
That's because I wanted to get rid of softkeys and still have an easy to use and reliable N4. Complicated gestures tend to be hard to use and to reproduce consistently, they will give you an hard learning curve and will slow down every operation. Here I'm trying to get the benefits of gestures without making everything overcomplicated.
Now... let's get into it, I'm gonna use pictures to make everything easier to understand
This is what I ideally wanted to get:
{
"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"
}
Each colored part corresponds to a ISA on LMT
YELLOW is ISA 1 (bottom left), assigned to BACK
RED is ISA 2 (bottom center), assigned to HOME
BLUE is ISA 3 (bottom right), assigned to RECENT APPS
GREEN is ISA 9 (left bottom), assigned to OPTIONS
ORANGE is ISA 6 (top right)
this is an optional one that I wanted to add. It's assigned to search longpress, wich triggers an activity of the app "Screen Off and Lock". Basically it locks the screen with a swipe.
Sadly, if you assign the ISAS as shown without changing any value within LMT your ISAS will look nothing like the picture, you'd get something like this:
Why? I promise I don't know. I read the posts about how to use LMT, but I couldn't really understand how the 4 settings for ISAS work. So as I said, I went for trial&error. At first I thought that "Activation area thickness" was the setting I had to modify to get what I wanted, but it didn't help in any way, and the same happened with "Min bbox size", so I left those two as they were by default.
Then I found out that increasing the value for "Touchscreen to screen factor Y" reduces the colored rectangles areas. I found the value 209 to be ideal. The rectangles were now more like lines closed to the frame, but many things were still off. Here's how it looked like:
The home button is far too small, everithing is too much to the left and I don't really know what the heck orange is doing down there.
Finally, I changed the "Touchscreen to screen factor X" value to 250, and it got me to my final result
It's not perfect, but it's pretty close. I would like yellow red and blue to be better centered, but this configuration is really reliable and easy to use. It actually took me some time to realize that it's not exactly as I wanted it, the only thing that you have to remember if you you're gonna use this, is to stay well to the right when you want to swipe into recent apps.
If you apply this settings you will be able to use easy gestures that can't be activated by mistake while you are using other apps or games and you'll gain precious space on your screen.
My final LMT values are:
Min bbox size: 1 (default)
Activation area thickness: 80 (default)
Touchscreen to screen factor X: 250
Touchscreen to screen factor Y: 209
*I also enabled the X shaped gesture on LMT and associated it with FullScreen Toggle. If anything goes wrong while you are using your phone and you can't open the app drawer to get to FullScreen Toggle and enable the navbar, just perform the gesture, toggle the navbar back and reboot your phone.
Known issues with this configuration.
There are two of them.
First, since you have an ISA for options, you will be able to use the options in any app that has an option menu. The problem is that for some reason when FullScreen Toggle is activated you will not be able to see the 3-dots on-screen icon that opens the menu on any apps. That icon disappears from the top right corner or wherever it's supposed to be. That means that you will have to remember which apps have an option menu or just try to swipe and open it in case there is one.
Second, with LMT ISAS change positon properly when you go from portrait to panorama mode only if you rotate your device 90° to the left. If you rotate your device to the right ISAS from the bottom go to the top and ISAS on the right side go to the left side and viceversa.
However this is not a big problem to me and maybe it will be fixed by LMT's developer anyway.
Sorry for the long post and for any grammatical error (probably a lot). Hope someone finds this intresting and helpful
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.
Marlon90 said:
I tried it but I was not satisfied with it. It's really great and extremely customizable, but in my expirience it's a bit buggy, it gave me problems right after the boot, can't remember if the auto-start was too slow or if there was actually something worse then that.
Also, it doesn't allow you to hide the navbar only, if you want to hide the navbar you have to hide the status bar too.
Click to expand...
Click to collapse
Ah ok. I dont use the hiding functions at all just use the Rom for that. The gestures aren't buggy at all and are a lot easier to set up than lmt. Also you get the launch pads.
Anyway it doesn't matter. It's a good guide and lmt is free so that's something.
Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?
ace7196 said:
Awesome post, thanks!
2 Questions...
Is there any way I can swipe back with the keyboard up without typing anything? I end up with a million drafts using LMT.
Also, is there a setting to actually see the areas like you show them for the touch locations?
Click to expand...
Click to collapse
First answer... this kind of things are the ones that bother me too with gestures, and doing what I showed in the OP I specifically tried to eliminate or reduce them. My answer to that problem was having a little line instead of a rectangle, and not so tiny that it's hard to trigger the gesture. It works well for me, and I think it requires very little getting use to.
Try it yourself if you want and maybe accomodate it to yur preference. Maybe you will type something from time to time but I hope the guide makes it so that it happens rarely.
Also, I never tried this on another N4... I don't see why it shouldn't work the same way for others, but a little feedback would be a very good thing.
As for the second question, there's no such setting that I know of, you should ask to the develoer of LMT. If there was such an option it would be so much easier to configure the app perfectly.
Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4
noname81 said:
Fyi: touchscreen to screen factors for the nexus 4 are 200/200. It's written in the OP.
Hth!
Sent from my Nexus 4
Click to expand...
Click to collapse
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles
Marlon90 said:
I know that, but does it work for you? On my device it does not, if I don't mess around with X and Y I always get rectangles
Click to expand...
Click to collapse
200 by 200 work best for me. OP: Are you able to simple press those hidden areas, or do you have to do a small swipe? I have to do the latter.
Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4
noname81 said:
Yes these are the correct values to divide each side of the screen into 3 areas with equal size.
Sent from my Nexus 4
Click to expand...
Click to collapse
Well, then I guess I'm left with a big pile of nothing... What happens to me is I have big areas in wich a swipe triggers the action. At 200 they take a big part of the sceen and if I increase Y even slightly they become lines, but some other things are off as I said. I've read around about people not being able to get ISAS to work and I thoght I was into something, but if that's just me then I'm at a loss... I guess I'll do a nanobkp and wipe and see if everything start working with 200/200
Great!, thanks for the guide.
tyraelasd said:
Great!, thanks for the guide.
Click to expand...
Click to collapse
yeah, you are welcome... read the rest of the thread, chances are this guide is useless for most people
jarayn said:
Cool guide thanks.
Did you try GMD gesture control? Seems like it would be easier to setup how you like. Complex or simple. I guess if you got LMT working fine then its all good.
Click to expand...
Click to collapse
I use both LMT and GMD for different gestures and I'm pretty satisfied, I also use glovebox for frequently used apps.
My setup is a little different, when I'm from the pc (and hopefully I'll remember XD) I'll share also my setup with you
Sent from my Nexus 4 using xda app-developers app
I personally use the Extend Desktop feature easily accessible from the power button on CM. Probably the way to go if you already have a custom ROM.
my gestures setup
I use, as I said, both LMT and GMD for my gestures setup. I tried a bit to emulate ubuntu for phones. (I also use glovebox as you see)
(In the image, the rectangles are actually the area you have to swipe to activate the gesture)
GMD custom gestures:
with a swipe from the left center you go home
with a wipe from the right center you go to the previous app
LMT ISAS:
swipe form the bottom center to go home
swipe from the bottom left to go back
swipe from the bottom right to recent apps
swipe from the top right to go back (useful when you have the keyboard open and you don't want to accidentally type)
the settings for the apps are the following
LMT
min bbox (how much do you have to swipe to activate the gesture: 5
activation area thickness: 25
touchscreen factor x,y: 200
GMD
gesture size (under "advanced"): 492
home and prevapp gesture may have to be disabled when keyboard is on depending on your keyboard
I'm pretty satisfied with this setup, only little thing that bothers me is that sometimes when I type a bottom gesture is activated, but it happens very few times
Im testing this Now, thanks
I like it. I had to use 100 instead of 80 but works mint.
issues with typing is messing with this. Also its hard to swipe up to go back on some apps. It keeps opening the keyboard.
I just wanna thank the OP and everyone on this thread. I read all the responses and was able to get it working perfectly for me. I like this setup way more than using PIE.
Find it difficult to switching between Landscape view and Portrait view when using the phone in bed, or horizontally on a desk? The screen keeps rotating back and forth when in a jolting car? They are no longer tough work with IntelliRotate! It allows you to rotate the phone freely anywhere and it will adapt the screen direction to fit your view.
How it works
There are 4 modes available now in IntelliRotate.
Auto
Simulate what the system accelerometer rotation will do, and then offset the screen by an specific angle. Quite accurate because only accelerometer sensor is used.
Absolute Direction
The most advanced mode. Given an direction (absolute 3D direction relative to the Earth) by pointing the bottom (buttons) of the screen toward, IntelliRotate will make sure that the content is always toward that direction.
The only mode efficient if you likes putting the phone on the desk.
However, due to the inaccuracy of the magnetic field sensor (compass) IntelliRotate uses to calculate the absolute direction, this mode sometimes performs badly.
Manual
Select a direction by clicking the pictures on "Basic" page or clicking the float button.
System
Turn IntelliRotate service off, and let system control the screen direction.
Screenshots
{
"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"
}
Versions
2.52
Fix some small bugs including a failure to work when running on a new ROM.
(Users before 2.5 can easily fix this problem by switching off Settings => Display => Auto rotation once)
2.5
Add a help page about some common usage. (See help)
Fix some small bugs.
2.41
July 30, 2013
Display a toast updated real-time when adjusting the settings.
Fix some small bugs.
2.3
July 28, 2013
Modify the algorithm of rotation stability (See help)
2.21
July 28, 2013
Support auto start on boot
Add an option to set rotation stability
Fix some small bugs
2.11
July 26, 2013
Greatly improve the accuracy of Absolute Mode.
2.0
July 25, 2013
Add an float window transparency slider
Add an option to automatically hide the float window after no rotation is made
Replace Auto (Half) mode with a more advanced option to ban some screen direction.
Fix some big bugs, e.g. failure to work on some custom ROM devices.
1.61
July 21, 2013
Adjust the behavior of float button.
Provide more styles of float button including a pair of rotation buttons.
Fix some small bugs.
1.5
July 20, 2013
Change error handler into a dialog.
Fix some small bugs.
1.4
July 20, 2013
Rearrange UI.
Fix some small bugs.
1.3
July 18, 2013
Signed with private keys
Add the option to adjust the size of the float button.
1.2
July 18, 2013
Slightly adjust the size of the float button.
Enable the function of the settings in help.
Add error handler.
1.1
July 17, 2013
Add one permission to prevent crash due to SecurityException on some device (e.g. Samsung Galaxy Note 8.0 with Android 4.12)
Add image resources for all the display densities
Change the mode selection into 2 lines
1.0 Beta
July 17, 2013
Initial release
Downloads
View attachment IntelliRotate_v2.52.apk
Previous releases
View attachment IntelliRotate_v2.5.apk
View attachment IntelliRotate_v2.41.apk
View attachment IntelliRotate_v2.4.apk
View attachment IntelliRotate_v2.3.apk
Very Nice. A few comments after a quick test.
I am mainly interested in the Auto (half) mode. And quick test it seems to work as wanted . I where planning* to automatically switch between the landscape orientations depending whether I was lying on my right or left side. I might not mean much in practice, which I will know after some more testing..
*I where planning on using this as a learning project for doing android programming, when (if ever) I had time and energy.
And quick comment about the radio buttons, it is not obvious, that they can be scrolled into view. I thought it was broken and outer rights modes inaccessible. Perhaps placing the vertically would be better.
I also like a quick toggle to enable disable it, e.g. widget or shortcut. I just discover this floating Icon and will see how well that work.
Great work
pmeinert said:
Very Nice. A few comments after a quick test.
I am mainly interested in the Auto (half) mode. And quick test it seems to work as wanted . I where planning* to automatically switch between the landscape orientations depending whether I was lying on my right or left side. I might not mean much in practice, which I will know after some more testing..
*I where planning on using this as a learning project for doing android programming, when (if ever) I had time and energy.
And quick comment about the radio buttons, it is not obvious, that they can be scrolled into view. I thought it was broken and outer rights modes inaccessible. Perhaps placing the vertically would be better.
I also like a quick toggle to enable disable it, e.g. widget or shortcut. I just discover this floating Icon and will see how well that work.
Great work
Click to expand...
Click to collapse
The mode selection is changed in version 1.1 now. I'm still considering other pieces of advice. Thanks.
IMPORTANT: Uninstall the previous version first or you will be puzzled. I've changed the package name since the previous domain name is already registered, so version 1.1 won't replace version 1.0.
lbell said:
The mode selection is changed in version 1.1 now. I'm still considering other pieces of advice. Thanks.
IMPORTANT: Uninstall the previous version first or you will be puzzled. I've changed the package name since the previous domain name is already registered, so version 1.1 won't replace version 1.0.
Click to expand...
Click to collapse
Better
Another tip about your help text. Remove/disable/replace with a picture the controls. One thinks, this is the real program first time, but nothings happens, when operating them which is confusing. There is also the same problem with modes radio buttons scrolling horizontally and not all visibile..
Nice looking graphics.
I will try to use it in real life the next days and see how it works out.
pmeinert said:
Better
Another tip about your help text. Remove/disable/replace with a picture the controls. One thinks, this is the real program first time, but nothings happens, when operating them which is confusing. There is also the same problem with modes radio buttons scrolling horizontally and not all visibile..
Nice looking graphics.
I will try to use it in real life the next days and see how it works out.
Click to expand...
Click to collapse
Now you can use these controls in help in version 1.3.
IMPORTANT: I'm sorry but I forgot to sign the previous versions with private keys...Please uninstall first. Thanks.
I have updated it to version 1.5!
this is a zip apk d no, I have to install it on or TWRP? thank you
wikie said:
this is a zip apk d no, I have to install it on or TWRP? thank you
Click to expand...
Click to collapse
It's just an apk. Install directly.
Note: It has been updated to version 1.6.
Thanks!
Thanks again for your effort Ibell.
A few more wishes/ideas.
1. A transparency slider for the floating icon would be nice. So it is still easy to hit, but less disturbing.
2. Floating Icon only appears shortly when phone is rotated. preferable in the center, so you don't need to look for it. Have a look at Adaptive Rotation.
3. Option to toggle between two rotation, instead of all 4 on floating icon. I prefer that over the dual rotation option, since it takes up to much screen (because at small size, the two buttons are too close). The space problem issue is less of a problem, if only appears shortly like described above and can be partially transparent, but I still prefer a 2 angle toggle option
Not working for me on Trickdroid 8 with ElementalX kernel.
pmeinert said:
Thanks again for your effort Ibell.
A few more wishes/ideas.
1. A transparency slider for the floating icon would be nice. So it is still easy to hit, but less disturbing.
2. Floating Icon only appears shortly when phone is rotated. preferable in the center, so you don't need to look for it. Have a look at Adaptive Rotation.
3. Option to toggle between two rotation, instead of all 4 on floating icon. I prefer that over the dual rotation option, since it takes up to much screen (because at small size, the two buttons are too close). The space problem issue is less of a problem, if only appears shortly like described above and can be partially transparent, but I still prefer a 2 angle toggle option
Click to expand...
Click to collapse
They are all available in version 2.0! Enjoy it!
deadman3000 said:
Not working for me on Trickdroid 8 with ElementalX kernel.
Click to expand...
Click to collapse
I'm sorry but I don't know why. Could you please install version 2.0 and try again?
lbell said:
They are all available in version 2.0! Enjoy it!
Click to expand...
Click to collapse
That steends great! Unfortunately the apk seems broking. The installer crashes
pmeinert said:
That steends great! Unfortunately the apk seems broking. The installer crashes
Click to expand...
Click to collapse
!?!? Can you install other apks? It works well here.
I had this problem several days ago (no apks could be installed then) and finally I found that it was due to no complete wiping before I restore a ViperOne ROM backup.
lbell said:
!?!? Can you install other apks? It works well here.
I had this problem several days ago (no apks could be installed then) and finally I found that it was due to no complete wiping before I restore a ViperOne ROM backup.
Click to expand...
Click to collapse
Ok, I did a wipe and restored my last backup and that solved the installation problem, thanks. It was not only yours I couldn't install.
pmeinert said:
Ok, I did a wipe and restored my last backup and that solved the installation problem, thanks. It was not only yours I couldn't install.
Click to expand...
Click to collapse
I'm glad your phone is okay now. Don't forget to update to version 2.1!
lbell said:
I'm glad your phone is okay now. Don't forget to update to version 2.1!
Click to expand...
Click to collapse
Hi Ibell. Thanks for your great work. I really like it now and it seems to cover my need, though I will keep testing. Only thing missing, is option to automatically start on boot.
For your information I test one use case and that is easy switching between sideward use in bed an normal use and I can do that now
I obtain this by using the auto mode and ban 180 + 270 degrees. Just keep in mind, that is what I need and therefor have not spend time testing the other modes.
Some ideas:
- Profiles. define profiles of the current settings (basic), which you can toggle with the floating toggle. E.g. my use case profile 1 = auto offset 0, profile 2 = auto offset 90. If more that two profiles, have option to extend the floater for directly selecting the wanted profile.
- Application specific orientation or profile. Some apps. require landscape (games), while some other require portrait (Sense).
If you split some of the functionality into a paid version, I would gladly pay for it.
pmeinert said:
Hi Ibell. Thanks for your great work. I really like it now and it seems to cover my need, though I will keep testing. Only thing missing, is option to automatically start on boot.
For your information I test one use case and that is easy switching between sideward use in bed an normal use and I can do that now
I obtain this by using the auto mode and ban 180 + 270 degrees. Just keep in mind, that is what I need and therefor have not spend time testing the other modes.
Some ideas:
- Profiles. define profiles of the current settings (basic), which you can toggle with the floating toggle. E.g. my use case profile 1 = auto offset 0, profile 2 = auto offset 90. If more that two profiles, have option to extend the floater for directly selecting the wanted profile.
- Application specific orientation or profile. Some apps. require landscape (games), while some other require portrait (Sense).
If you split some of the functionality into a paid version, I would gladly pay for it.
Click to expand...
Click to collapse
Thanks for the advice. I'm going to add support for auto-start on boot and profiles. But I am not planning to make application specific profiles so far because Sense/most games/... have already defined their ideal rotation and IntelliRotate do not force them to rotate.
lbell said:
Thanks for the advice. I'm going to add support for auto-start on boot and profiles. But I am not planning to make application specific profiles so far because Sense/most games/... have already defined their ideal rotation and IntelliRotate do not force them to rotate.
Click to expand...
Click to collapse
Ok. Yes maybe you are right. My experience was from a rotation locking app. Don't have a fresh example
Anybody running PIE controls instead navbar?
First I did hide navbar by xposed and xmiui tweaks (2.0). After that I tried different apps for PIE.
Well-known LMT launcher isn't working for me. simple PIE also isn't working properly because I don't see icons and edges of my PIE.
As last I tried xposed module "unique controls". It is working fine but hasn't second or long press actions...
Has anybody similar experiences?
{
"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"
}
Thanks for sharing information, Mix's screen is great at full!
Only edited build.prop and added lmt. All works incl. user images. Only quirk I'm having is that everytime i reboot I must make sure to go into the app first, which automatically takes me to the drawing over other apps toggle. It turns off on reboot. This is something I have come across before. Only on marshmallow roms though, not on lollipop or nougat.
qemu.hw.mainkeys = 1
for hiding navbar?
That's all or changed you anything more for working LMT?
vergilbt said:
qemu.hw.mainkeys = 1
for hiding navbar?
That's all or changed you anything more for working LMT?
Click to expand...
Click to collapse
Yup. There are two empty lines at the bottom. Just add and leave one empty line. No need to add another. Doubt it matters though.
In my "short" post here:
http://forum.xda-developers.com/mi-mix/how-to/guide-flash-global-china-rom-root-gapps-t3510592/page4
I mention lmt. Just gonna quote myself:
"On lmt launcher I had to set the touch area thickness to 35 for pie to register my finger. So i checked CIT (hardware test. Go to: about phone => press kernel version 4x).
And I can see my digitzer doesn't register my finger when I slide in from the sides up until i reach 32 pixels in. If I start from anywhere else and go towards the edge, it follows me perfectly.
Can anyone replicate this? I'm guessing this has to do with not getting unwanted touches when holding the phone."
I'm not sure the same applies to the top and bottom.
And by touch area thickness I mean activation area thickness:silly:
Thx a lot...
Only to set area thickness to 35 was my solution for get working LMT...
[emoji3] [emoji3] [emoji3]
vergilbt said:
Thx a lot...
Only to set area thickness to 35 was my solution for get working LMT...
[emoji3] [emoji3] [emoji3]
Click to expand...
Click to collapse
One thing i forgot to mention. By increasing the activation area, you are also increasing the chance of triggering pie when you hit the edgekeys on your keyboard for example. I would avoid making it long enough to reach that far down (this is if you have the triggers on the sides).
If you use bottom then the same pertains to stuff you might have there. But I guess this is very obvious.
Don't you just love it. All screen, all the time. I have yet to see a perfect alternative. All app/OS solutions still make the nav bar glitch around at times.
No worries...
I'm using LMT for many years (especially on smaller screens like Nexus 4 and 5)
[emoji6]
just wondering - did you try using the gravitybox module in xposed? i use that for pretty much everything. this is the first thing i'm going to do is setup pie controls, i really have no idea why everyone doesn't prefer them so much quicker and more efficient
Using xMIUI tweaks... Heard about some issues when using gravity box...
vergilbt said:
Using xMIUI tweaks... Heard about some issues when using gravity box...
Click to expand...
Click to collapse
where is xmiui tweaks found at? i search for it on the xposed modules and i'm not finding that. is there a different place to find modules for miui? thanks
edit - ahhh...it is in the playstore
I am using simple control from the same creator of simple pie:
https://play.google.com/store/apps/details?id=ace.jun.simplecontrol&hl=en
I found this behave much better for my taste. you click the bottom to bring up the navigation bar, you set delay and auto hide to suit your taste, the bar disappear after a while to maintain the full screen experience on Mix.
With PIE, or simple PIE, you have to swipe then click, and the pie bar is gone instantly which i don't think is ideal. And more importantly, because you need to swipe and click, that's one gesture less you are free to use.
I haven't rooted my phone (still waiting for unlock code), so the swipe up action brings the navbar back if you don't use xposed modules. Simple control solve that problem as it's purely click action.
Ok, i actually found something I think that's better, FloatMenu
https://play.google.com/store/apps/details?id=com.ksxkq.floating&hl=en_GB
No more buttons what so ever, just do swipe actions from edges and you get the home/back/recent actions. Unlike PIE which you have to swipe and click, more importantly, you don't have the ugly (imo) pie overlay. There is no overlay at all if you use Float Menu. And it has some advanced options such as disable during keyboard...etc.
p.s. I am still waiting for my BL unlock code to root my phone so I can completely get rid of Mi Nav Bar, once that's done, I can test all these methods more realistically.
wu5262 said:
Ok, i actually found something I think that's better, FloatMenu
https://play.google.com/store/apps/details?id=com.ksxkq.floating&hl=en_GB
No more buttons what so ever, just do swipe actions from edges and you get the home/back/recent actions. Unlike PIE which you have to swipe and click, more importantly, you don't have the ugly (imo) pie overlay. There is no overlay at all if you use Float Menu. And it has some advanced options such as disable during keyboard...etc.
p.s. I am still waiting for my BL unlock code to root my phone so I can completely get rid of Mi Nav Bar, once that's done, I can test all these methods more realistically.
Click to expand...
Click to collapse
When do you have to click on Pie? You just swipe in from one side and let go when you reach the right key.. you can also adjust longpress time for second layer of keys. If you use lmt, you can also add custom gestures etc. But I find it better to have an overlay with quick access to fav apps. Quicker to switch that way than through recents menu.. best would be as you say to not have anything.. Pie offers more keys/shortcuts quickly. Best would be no overlay, but hardly the most functional. Can only imagine replacing all my shortcuts/keys with gestures. Seems like a nightmare to remember.
But if you don't like it, you don't like it
benziii said:
When do you have to click on Pie? You just swipe in from one side and let go when you reach the right key.. you can also adjust longpress time for second layer of keys. If you use lmt, you can also add custom gestures etc. But I find it better to have an overlay with quick access to fav apps. Quicker to switch that way than through recents menu.. best would be as you say to not have anything.. Pie offers more keys/shortcuts quickly. Best would be no overlay, but hardly the most functional. Can only imagine replacing all my shortcuts/keys with gestures. Seems like a nightmare to remember.
But if you don't like it, you don't like it
Click to expand...
Click to collapse
I think it's all down to preference, when I said you need to click in PIE, i meant you need to swipe in from side, then you need to look at overlay and locate the keys you want to press then releáse, this whole process is longer than the method I use.
So in quick summary:
In PIE, swipe->locate->release
In Floating Menu, Swipe->release
You take out the locate step and you also get rid of the ugly(imo) overlay. Downside is you also get rid of the quick access app option but i personally don't like it at all. If quick access app is a must, there are tones of app that can let you do that with swipe action, i just don't want it to mix with my nav bar bottom swipe.
I set my floating menu at the bottom, so recent app in bottom left, home in bottom mid, back key in bottom right, just like where you have the physical or Nav bottom, and I can swipe it without looking at the phone, and because there is no overlay, i don't need to locate also. In real usage, it has the least learning curve i think.
I am enjoying this method a lot more than others apps, but that's my preference.
wu5262 said:
I think it's all down to preference, when I said you need to click in PIE, i meant you need to swipe in from side, then you need to look at overlay and locate the keys you want to press then releáse, this whole process is longer than the method I use.
So in quick summary:
In PIE, swipe->locate->release
In Floating Menu, Swipe->release
You take out the locate step and you also get rid of the ugly(imo) overlay. Downside is you also get rid of the quick access app option but i personally don't like it at all. If quick access app is a must, there are tones of app that can let you do that with swipe action, i just don't want it to mix with my nav bar bottom swipe.
I set my floating menu at the bottom, so recent app in bottom left, home in bottom mid, back key in bottom right, just like where you have the physical or Nav bottom, and I can swipe it without looking at the phone, and because there is no overlay, i don't need to locate also. In real usage, it has the least learning curve i think.
I am enjoying this method a lot more than others apps, but that's my preference.
Click to expand...
Click to collapse
When you have used pie for half a day or less, your thumb can pretty quickly slide in to the right key. You don't think consciously, just muscle memory or whatever one calls it :laugh:
But you want it clean, I understand
Can you customize the looks on simple pie? It can look better than stock. At least with lmt. Just had to squeeze that in there.
benziii said:
When you have used pie for half a day or less, your thumb can pretty quickly slide in to the right key. You don't think consciously, just muscle memory or whatever one calls it :laugh:
But you want it clean, I understand
Can you customize the looks on simple pie? It can look better than stock. At least with lmt. Just had to squeeze that in there.
Click to expand...
Click to collapse
You can certainly customize the looks on simple pie, but it remain to be "pie shape" xD, which i don't like.
I would rather go with simple control which I linked a few posts above if I still want the overlay.
wu5262 said:
You can certainly customize the looks on simple pie, but it remain to be "pie shape" xD, which i don't like.
I would rather go with simple control which I linked a few posts above if I still want the overlay.
Click to expand...
Click to collapse
I think you need to try a tasty english meat pie / apple pie, to change your perceptions on this lovely shape
benziii said:
Only edited build.prop and added lmt. All works incl. user images. Only quirk I'm having is that everytime i reboot I must make sure to go into the app first, which automatically takes me to the drawing over other apps toggle. It turns off on reboot. This is something I have come across before. Only on marshmallow roms though, not on lollipop or nougat.
Click to expand...
Click to collapse
have you figured out how to make LMT automatically launch on a reboot without making you go in and toggle the overlay again? this happens to me even sometimes without rebooting i have to go in and do it again. so annoying i also can't seem to get it working on the bottom of the screen but can on the sides.
knives of ice said:
have you figured out how to make LMT automatically launch on a reboot without making you go in and toggle the overlay again? this happens to me even sometimes without rebooting i have to go in and do it again. so annoying i also can't seem to get it working on the bottom of the screen but can on the sides.
Click to expand...
Click to collapse
No, I really haven't. As long as I have it locked in the recents menu, it never fails. But have to do the toggle on reboot. Just checked, on the bottom I can put the activation area thickness down to as little as 5 and it still responds everytime. What happens when you choose bottom?
I'm on 6.12.8 now btw. What are you on?
I'm hoping this blows over when nougat builds starts coming out, but it is not that much of a pain. Takes three seconds. I have only run nougat roms on my nexus 9, but it has never happened there.
Also, after using it for years, I don't honestly find the "pie" look that great either. I often just choose transparent for all the colors, so it's just my buttons and icons showing.
{
"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"
}
Featured by:
XDA-Developers: Customize the Google Pixel 2’s Active Edge to do any action with Edge Sense Plus [XDA Spotlight]
What is Edge Sense Plus?
Edge Sense Plus was initially just meant for the HTC U series. It let's you customize the squeeze action and adds some more squeeze gestures and features.
But with the Pixel2 and Pixel3 also coming with a squeezable frame I found a way to make it compatible too.
Since google locked active edge down to just only be able to start Assistant it will require a device rooted with magisk
Requirements
it works both on rooted and unrooted devices, the unrooted version is a bit limited on features though and requires you to make Edge Sense Plus the Default assistant
Install the Active Edge System Mod Magisk Module from the MagiskManager Repo and the EdgeSensePlus from the playstore and you are ready to go!
Telegram Group
Join Telegram Edge Sense Plus Group
How does it work
To make it working on the Pixel3 I had to modify the SystemUIGoogle.apk that runs the ElmyraService (Service that processes the squeeze gestures).
I intercept the events and pass them to the EdgeSensePlus Application that starts the appropriate action then that you selected.
Some more adjustments were made, so the squeezing also works when you are in immersive mode, camera or when Google Assistant is deactivated/uninstalled.
With Android 10 it works now also on unrooted devices but it requires you to make Edge Sense Plus the Default assistant
What can it do?
Custom actions:
Currently you can choose from over different actions
Quickly Start camera - Also when screen is off and locked
Per App Action - Execute different squeeze actions depending in what app you are!
Sidebar
Gesture Panel - Draw custom gestures to start different actions
Custom App
Shortcuts - e.g. to make direct calls, start tasker tasks and more!
Scroll up/down
Flashlight
Recent Apps
Toggle Autorotation
Autobrightness (6 states: Auto, Min, Low, Mid, High, Max)
Split Screen
Expand/Collapse Statusbar
Toggle NFC
Toggle Display on/off
Toggle Autorotation
Toggle DND
Toggle Vibration
Toggle Bluetooth
Toggle WiFi
Music Play/Pause
Previous Track
Next Track
Toggle Keep awake
Google Assistent
Lock Screen
Back
Home
Toggle Sync
Sync all accounts
Previous App
Take Screenshot
Clear all notifications
GPS
Answer/End call
Immersive Mode
Shell command
Per app actions:
With the per app action, you can define different squeeze actions per app. So the chosen action will be executed dependent in what app you are currently are.
Double Squeeze: (Premium)
If you often accidentally trigger a short squeeze, that won't happen anymore if you map your desired action to the double squeeze gesture.
You can define a double squeeze interval, to ensure you are quick enough to trigger it every time.
Long Squeeze:
Missed a long squeeze action on your Pixel? Edge Sense Plus has it!
G-Sensor usage: (Premium)
If enabled, will be able to execute different actions depending on the current position of your device, whether it is flat or upright in your hand.
That way you can have six different squeeze gestures: short, long, doublepress in flat or upright device position.
Media control:
The media control will override your set squeeze actions while media is playing so you can control your media.
That includes play/pause, increase/decrease volume and skip to next and previous track.
Squeeze sounds:
Ever thought it would be funny if a squeeze of your Pixel 3 XL would make a sound, if it is a *click*, *oink* , *fart* or whatever you think of?
You can use any .mp3 file to make that happen!
Sidebar:
The Sidebar has 4 different panels, Applications, Shortcuts, Recent Apps (Premium), Quicksettings (Premium).
Panel colors are customizable
Instructions
Unrooted Version:
Install Edge Sense Plus from the playstore and follow the in app instructions
Rooted Version:
Root with Magisk is required since the magisk module is mandatory!
It is recommended to have a working TWRP backup in case something goes wrong. Check the FAQ for help too.
Like always: Flash on your own risk. I'm not responsible for any damaga to your device
Flash the Magisk Module in Magisk Manager
Install Edge Sense Plus
Enjoy.
Downloads
Now also available via the MagiskManager Repo:
I recommend to install and update the Magisk Module directly via the MagiskManager repository directly in the MagiskManager app.
All releases will be also available on the GitHub repository
Edge Sense Plus:
Hello @j to the 4n
Was going to look for your Telegram thread, but then saw you post this here. Basically here's my post from Tulsadiver's thread with his modifications including your Active Edge module support:
https://forum.xda-developers.com/pi...sk-module-mod-installer-t3992635/post80752815
tldr of it is, when the Active Edge module is added, the phone seems to either have lag or lockups necessitating a complete reboot of the phone. Sometimes this doesn't happen for a while or sometimes is as soon as the phone boots.
Any ideas?
ilal2ielli said:
Hello @j to the 4n
Was going to look for your Telegram thread, but then saw you post this here. Basically here's my post from Tulsadiver's thread with his modifications including your Active Edge module support:
https://forum.xda-developers.com/pi...sk-module-mod-installer-t3992635/post80752815
tldr of it is, when the Active Edge module is added, the phone seems to either have lag or lockups necessitating a complete reboot of the phone. Sometimes this doesn't happen for a while or sometimes is as soon as the phone boots.
Any ideas?
Click to expand...
Click to collapse
Mhh, no clue tbh. It worked fine for years on the Pixel2/Pixel 3. The Pixel 4 Version is not any different.
Can you maybe pull a logcat when it happens again?
Or telegram is here: https://t.me/edgesenseplus
j to the 4n said:
Mhh, no clue tbh. It worked fine for years on the Pixel2/Pixel 3. The Pixel 4 Version is not any different.
Can you maybe pull a logcat when it happens again?
Or telegram is here: https://t.me/edgesenseplus
Click to expand...
Click to collapse
Sure I'll try to get a logcat when it starts up again. Thanks!
Just installed this on my P4XL.
Couple things -- I have a long press set to trigger Assistant, and it seems to launch the old Assistant, the white full screen one. Any way to launch the new Assistant at the bottom of the display?
Also, I'm rooted with Magisk, but when I try to toggle the root option on the app, it says the "device seems not to be rooted.'
calbruc said:
Just installed this on my P4XL.
Couple things -- I have a long press set to trigger Assistant, and it seems to launch the old Assistant, the white full screen one. Any way to launch the new Assistant at the bottom of the display?
Also, I'm rooted with Magisk, but when I try to toggle the root option on the app, it says the "device seems not to be rooted.'
Click to expand...
Click to collapse
The original assistant can be just called when the root option is enabled.
DId you by chance denied root access once? Check in Magisk Manager->SuperUser
j to the 4n said:
The original assistant can be just called when the root option is enabled.
DId you by chance denied root access once? Check in Magisk Manager->SuperUser
Click to expand...
Click to collapse
Weird, I don't remember denying root, but that was the problem! Thanks!
I cannot seem to enable the module on my P4XL. It's installed, but if I enable, reboot, it's disabled again.
Sent from my Pixel 2 XL using Tapatalk
dmarden said:
I cannot seem to enable the module on my P4XL. It's installed, but if I enable, reboot, it's disabled again.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
It's the bootloop protection of my module.
When an Security patch gets released I need to make the module compatible first.
Takes usually 24h when I have all files. Give me another hour and it will be done.
Then just reinstall the module.
Oh that's my bad. I saw P4XL in the change notes and since I just got the device today, I didn't even think to consider the November update.
Thanks.
Sent from my Pixel 2 XL using Tapatalk
Okay that's better. Carry on.
Has anyone been successful with setting it to take a picture once the camera is open?
srimay said:
Has anyone been successful with setting it to take a picture once the camera is open?
Click to expand...
Click to collapse
ensure that you have either "User Usage" Access permissions given or have enabled the root toggle.
If it still doesnt work, send me a logcat please.
Previous users that had issues had mutliple camers installed or somehow tasker was set as default for the camera action.
j to the 4n said:
ensure that you have either "User Usage" Access permissions given or have enabled the root toggle.
If it still doesnt work, send me a logcat please.
Previous users that had issues had mutliple camers installed or somehow tasker was set as default for the camera action.
Click to expand...
Click to collapse
I sent a logcat thru the email on your app
Are you going to be doing anything with the motion sence? I was hoping you could make another useless feature useful. Just curious.
jamiejames said:
Are you going to be doing anything with the motion sence? I was hoping you could make another useless feature useful. Just curious.
Click to expand...
Click to collapse
I was working on it, but someone beat me to it.
There was a xda article about it already
I've noticed that when I map squeeze (single) to pull down the status bar or expand/retract it doesn't work the first time and I receive a toast that ES has been granted SU and then it works after that, but occasionally without a reboot it will stop working. Squeeze always pulls up the new assistant but doesn't consistently execute the action mapped to single squeeze for me. Sometimes it will expand the status bar but also the assistant so I can't interact with the notification shade until assistant goes away. All of this happens with assistant disabled, so not sure what else I can try.
joshnichols189 said:
I've noticed that when I map squeeze (single) to pull down the status bar or expand/retract it doesn't work the first time and I receive a toast that ES has been granted SU and then it works after that, but occasionally without a reboot it will stop working. Squeeze always pulls up the new assistant but doesn't consistently execute the action mapped to single squeeze for me. Sometimes it will expand the status bar but also the assistant so I can't interact with the notification shade until assistant goes away. All of this happens with assistant disabled, so not sure what else I can try.
Click to expand...
Click to collapse
About the issue that the expand collapse action does not work at the first time sometimes:
There is no way to check, if the status bar is expanded or not. I can only save the state if the squeeze executed the expand command, so that the next squeeze will execute a collapse action.
If you would collapse the statusbar manually after the first squeeze which expanded the statusbar, the 2nd squeeze would fail too, because it would execute the collapse command, altough you already manually collapsed it before.
Expanding and collapsing the statusbar does not need root permissions, so no idea why an SU popup appears.
About your second issue I'm not sure if I understood it correctly.
You mean that sometimes the mapped action does not get executed, but instead the stock action with GA?
That would be a weird behavior, because once the magisk module is mounted, that can't happen. Or are you non rooted?