yashsingh1/xdaforums huggingface dataset:
[Android Software Development] noname81:
Yes, all new adaptive icon drawables do not show correctly. I already fixed the issue and it will be part of v2.9. I hope I can push a test version the next days...
[Android Software Development] cdotjames:
Same here
[Android Software Development] tardis_42:
I just got my Essential Phone and as always one of the first things I did was install LMT. Strange thing, though: the pie controls seem to read the touch position slightly incorrectly. I keep triggering the top option when my thumb is actually on the middle one, and the middle one when I'm on the bottom. A few other apps are having similar issues so hopefully Essential themselves will come up with a fix but I thought it was worth mentioning in case it's an easy fix. The pie does center right where I swipe in, by the way, so the up/down offset is only on the release.
[Android Software Development] Natakranta:
Just flashed O today on my N6P and was wandering what happened to my Google apps on LMT pie :D

Thanks a million for continuous support all these years. Loyal fan since Jelly Bean.

Looking forward to v2.9
[Android Software Development] stanley321:
How do you restore the backup??? I have used the app in 6.0 and 7.1, but I can't restore the settings in 8.0
[Android Software Development] shaggyskunk:
I just use Titanium Backup to Restore my LMT Settings ?

From Down the Rabbit Hole by:

My SM-G930W8 ??
[Android Software Development] rolear8:
I have been using this great invention from my past 3 devices, now a have a S8 + and notice that the back button sometimes do not respond the first click, I have to do it twice and sometimes even do not work at all, any idea?? Thanks in advance for everything
[Android Software Development] Natakranta:
Darn! Seeing new post in LMT thread I thought it's 2.9 test version :D
[Android Software Development] a g bell:
Where??
[Android Software Development] :
Hi how can I configure it to shut off screen on double tap anywhere on the screen?
[Android Software Development] aznriceballman:
Did anyone try the LMTFrameworkResLayer.apk with the new Andromeda thing?
[Android Software Development] Atomregen:
I have tried it manually with the "cmd overlay enable" command but the navbar is still there.
[Android Software Development] sga999:
That's a very old post. There are several after it that refer to the same problem. I don't see any posts that say what this might be, but it's still happening today on 2.8. I don't see any solution, but it's difficult to search for the exact behavior. The posts represented several different devices and roms, no commonality.

I've never seen this behavior on Nexus 4 or Nexus 5. But I got a Leeco Le Pro 3 this year, and that's where this happens. I've installed several roms on it, and most do not have this problem, but this one shows this problem. It is very random, sometimes occurring when I'm actively using the device, sometimes when it is inactive. Can someone give me an idea about what would cause LMT to toggle the "Activate LMT" switch to off, all by itself? If I know what causes it, I could ask the rom provider to look into it.
[Android Software Development] gaw316:
Did you goto settings, display, and change the theme there too as well?
[Android Software Development] Atomregen:
Yes, I tried that before and after the overlay command.
[Android Software Development] noname81:
When you see such a behavior in your ROM it means that Android was most likely killing LMT (the foreground service) due to high memory usage. Normally Android should shut down all other running apps in the background and all other background services before doing this. So with todays phones with its GBs of RAM available it should never happen, that Android has to kill foreground services. In the last years of using LMT on Google devices I have never seen such a behavior, since Android is configured correctly. Unfortunately OEMs seem to break this configuration and there is not much apps like LMT can do to solve the problem. One would have to fix it in the ROM.
[Android Software Development] Natakranta:
[MENTION=1864347]noname81[/MENTION], may I ask how's going with v2.9? Did you come across some O(bstacles) :) stopping you from releasing test version?

Thanks!
[Android Software Development] noname81:
Everything is done for the first test version. I just didn't find time to upload it this week. I will do it the next days.
[Android Software Development] divineBliss:
Don't forget to update the thread title to v2.9 ;)
[Android Software Development] noname81:
Thread title is already set to 2.8 but still showing 2.7. it's not updating it anymore - I should ask a moderator...
[Android Software Development] aznriceballman:
Anyone find a way to hide the nav bars without anything crashing?
[Android Software Development] sga999:
Thanks, [MENTION=1864347]noname81[/MENTION]. I can't prove it, but I don't believe LMT is being killed due to a ram problem. Using System Monitor app, it shows the used ram is 2.3GB and free ram is 1.4GB = total 3.7GB. For the LMT app itself, it shows it is using 21MB. This is not at the time when the problem occurs (I'm never sure when it will happen), so I understand that my numbers could be wrong at the exact moment that LMT is "deactivated". So I'm guessing that it is deactivated for some other reason.

But I can give you some more information that might give you ideas. (I'll be glad to talk to the developer of the custom rom, but I need to learn more first).

The stock rom for this Leeco Le Pro 3 works perfectly with LMT! It is not rooted, yet all functions work, e.g. back, home, recentapps. But with a custom rom, those functions of LMT do NOT work without root. However, if I give root permission to LMT on this custom rom, those functions DO work. But if I look at a catlog, those events for back, etc. don't show. For example, on rooted Nexus 5, catlog will show Fire action type: Back....etc. But for this Leeco, those touches (back, etc.) are actually working, yet no Fire Action event shows in catlog.

I have not captured a log yet where the "deactivation" occurs. But I can get a catlog for you of what I described above. Since there's not much there, I'm not sure how helpful it is. Also, I don't have a catlog of the stock rom to show you how it works perfectly. I guess I'd have to do it with ADB, but that's more trouble to set up. I'll get you whatever you need. Thanks.
[Android Software Development] noname81:
To catch the problem when LMT is being disabled, I would install logcat tools like catlog on the phone and increase the size of the logcat buffer in the developer settings. Then, when it happens again, use catlog to record the latest logcat and post it here. With the log I can check if LMT was disabled due to e.g. low memory or perhaps due to it's crashing too often.

When LMT has no root access, it is falling back to the accessibility service to issue actions like back, etc. Did you activate LMT in the accessibility settings? If yes it seems as this route is broken in the ROM.
[Android Software Development] noname81:
Before Android O the best way to hide the navbar in my opinion was to use the RRO layer theme from the OP (in case you ROM has support for it). Since O it seems to be broken. I already checked the AOSP code of O and didn't find any obvious reason why it's not working, but the theme values are just not being picked up (height for the navbar). Since hiding the navbar via build.prop is also broken, you could only use a patched framework-res.apk with modified values. A link was already posted here for the PIXEL on O via AROMA installer. The other way is permanent immersive mode. I added a new action in LMT for 2.9 to activate it. The downside of immersive mode is, that PIE from the bottom is not working (since the navbar can popup from there) and it breaks some apps. Since I use only the PIE from the sides, this is my setup atm. Let's see if someone finds a better way for Android O.
[Android Software Development] sga999:
I decided to try to get a log for you. I used logcat extreme because I had trouble with catlog. Not sure if this is good enough.

This is a recording of when I am rooted and using the custom ROM with the lmt deactivation problem. Once those last two relayout events occur, nothing is logged after that. (I was filtering on LMT) . I can do many actions, and they work fine, even the ones that require root, like back. But the log does not show them.

Sometime later on, the problem where LMT gets deactivated will occur. But I am unable to know when that will happen. I can probably get that one later on, but I thought this might be a start.
[Android Software Development] sga999:
Sorry, somehow the attachment didn't work. Trying again....
[Android Software Development] sga999:
Apologies, I didn't see your response because I was getting the logcat extreme ready! Accessibility for LMT shows disabled. But I've tried various things today, and I'm pretty sure I had it enabled at one point. Result was the same. But I wasn't getting a log at that time. I'll try that, and if it shows something new, I'll post again.

EDIT: The log seemed to look very similar after I enabled accessibility for LMT.

EDIT2: I'll let it go overnight and see if there are more events, possibly showing the disabling. Since I'm only filtering for LMT, I don't think there will be much in there, so I won't worry about buffer size yet.
[Android Software Development] CoolinHL:
I enabled permanent immersive mode in Oreo on my Nexus 6P by doing "adb shell settings put global policy_control immersive.navigation=*". However, I noticed that my battery drained significantly faster after doing this.

After some Googling, I found that others are experiencing this issue:

https://xdaforums.com/lg-g6/help/immersive-mode-causing-battery-draining-t3621622

https://xdaforums.com/showpost.php?p=72333585&postcount=69

Did you enable immersive mode the same way? Are you experiencing the battery drain issue as well?
[Android Software Development] sga999:
Here's a log of the "LMT deactivation" overnight. I don't see anything obvious at the end of the log at 1:54 am. It looks similar to events that occurred earlier. But it definitely deactivated by the time I looked at it this morning.
[Android Software Development] :
Feature request:

Can you please give LMT ability to use Android's "notification access" feature to show notifications? Instead of using the hacky Accessibility way.

Also, Pie controls built into some ROMs support being able to drag the pie to another side of the screen while you're using it by having little areas that you can slide your finger to as the pie is open to reposition the pie. I think that's really useful and would love if I could do that with LMT rather than changing the activation area manually in LMT's settings all the time.
[Android Software Development] noname81:
Yes, doing immersive mode this way is broken in Oreo as described in the thread (doze doesn't work correctly anymore). Instead of activating it for * you can just write "apps". Doing it this way works fine in Oreo. Hopefully Google fixes this in some upcoming release.
[Android Software Development] noname81:
I put it onto the todo list. Let's see when I find time... :D
[Android Software Development] noname81:
This log doesn't reveal much as you already stated. How did you filter the log? With the string "LMT" or via a log channel? Do you have the full log?
[Android Software Development] sga999:
This log from today had less in it than the one last night. Did you see that one too? It's just a few posts earlier. For both, I just entered the string LMT. I used Logcat Extreme, and it allowed me to enter anything. I had tried Catlog earlier. When I started to enter the string LMT, it did show 3 choices, but I didn't pick any of those...I just did the string LMT.. But I had problems with it capturing everything instead of what I wanted, so I gave up on it.

Maybe you can tell me exactly which app you'd like me to use. And give instructions on what to filter on, if anything. And how to change the buffer size, if you think that's necessary.

I had thought the events about scheduling/finishing stop of Activity...might give you a clue about something going wrong. It sure doesn't look at all like a "good log" on another device.
[Android Software Development] Pecata:
Do you think this would work? - A substratum theme that hides navigation bar?

---------- Post added at 20:05 ---------- Previous post was at 19:40 ----------

Same here, I am not finding any-I doubt that there are any yet. Maybe they will start releasing them now that Oreo is officially out.
[Android Software Development] maflin18:
I believe it should work. The trick is to find one that does it.
[Android Software Development] stanley321:
Would you please also make switching to the last app to use the non root method on 7.1+ using the "write secure settings"? Other apps are already doing it without root.

It's the last piece of jig saw for me to use LMT non root. Thank you for your continuous improvement.
[Android Software Development] droidgren:
Is it possible to add back key function without root? That is the only thing I need to be able to use it without root. I know the pie controls app on the play store is able to do so it should be possible. Thanks, this app is the best!
[Android Software Development] noname81:
This is already implemented. Just activate LMT in the system accessibility settings and back, home, open notifications, power dialog, quick settings, recents and toggle split screen will work without root.
[Android Software Development] ImmaN00B:
I so want to donate like something to the developer. Please add fade out after an action I have OCD
[Android Software Development] sga999:
[MENTION=731031]noname1[/MENTION], I'm trying to show you the problem where LMT deactivates without an obvious cause. I have tried to get a "good" logcat for you, but I've been unable to capture that deactivation. However, I did capture something else. I have LMT option set to autostart, but it does not. There's one event at line 498 in part2 which shows "appop denial" for LMT. I wonder if It's possible that whatever makes it not autostart is also what makes it deactivate later. I've divided it into 2 parts due to the size.

I have to activate LMT myself due to this problem. Then it may run for hours. But it seems like if I let the device sit for awhile, doing nothing, that's when it deactivates. I'll keep trying to get a log of that. But in the meantime, I thought this inability to autostart might tell you something.
[Android Software Development] Mao04:
Just a stab in the dark. Do you have app ops or privacy guard in your rom?
[Android Software Development] sga999:
My device is a Leeco Le Pro 3. There is no mention of App Ops or Privacy Guard in the XDA thread for the rom that I installed. Another version of the same developer's rom works fine. I'm willing to ask him more, but I wanted to see if I could narrow it down here first, before asking him.

From a little bit of goggling, it sounded like App Ops was removed from roms in KitKat and later. This is a Marshmallow rom. So I don't know why it would be showing in the log here. With App Ops present, do you know what to do to allow privileges for certain apps, such as LMT?
[Android Software Development] sga999:
I've learned more about Leeco device not autostarting LMT (see post prior to this one). For this rom, there is an app called Phone Manager. Then within that app, Security and Privacy and Manage Auto Launch options are there. That's where I can enable LMT to autostart! On another version of this developer's roms for this device, I have never had to use that Phone Manager app to autostart any app. So I will be asking him about this difference soon.

On this rom (but not on another), LMT has deactivated when letting the device be inactive for "a while". I don't know if that will change, now that I've turned on autostart for LMT. I'll keep monitoring for that. But thus far, I've been unable to get a log which will show that event.
[Android Software Development] Mao04:
That's what I was thinking. That there was some app that was keeping LMT from starting or running in the background. Sounds like Phone Manager may be doing that.
[Android Software Development] sga999:
I'm getting to the end of the Leeco "deactivation problem". Not only did the Phone Manager app (mentioned a couple of posts ago) stop LMT from autostarting, but it also was killing it. In that app, under Power Saving Management, there is "App Protection", which is described as "Apps that can be exempt from cleanup". Once I put LMT in that list, it no longer deactivates.

So it's solved except that I'm still curious about a couple of things. I don't know why another rom by the same developer works without having to make these changes in that app. I'll ask him about that. Also, I don't know why I don't see an event for the deactivation in the log. That's not very important, but I'll pursue it on my own.
[Android Software Development] Natakranta:
[MENTION=1864347]noname81[/MENTION], is there any way to make Google apps icons to appear on pie? Camera, Gmail, YouTube, Play Store are missing on screen shot attached. Yet I can still launch them from there.

Nexus 6P running AOSP Oreo ROM ABC. Magisk rooted. LMT 2.8
[Android Software Development] tulutoa:
I have set the longpress delay of the pie to 500ms. Sometimes it gets stuck in longpress actions. A quick fix would be resetting the longpress state each time LMT is accessed.
[Android Software Development] Borfas:
Hi, I've been using this app for a long time, I've always cherished it! But from the edge of samsung, I get tangled, I would make a small donation if you straightened out and be much more compatible with the edge screens.
[Android Software Development] Ztones:
[MENTION=1864347]noname81[/MENTION] I love this pie/launcher, but it is missing one very important feature. Can you PLEASE make a backup and restore function? I know you had said that the built-in good restore works, but it really doesn't. For me, it only restores settings for apps downloaded from the playstore. With LMT not being in the playstore, it never restores its settings. I have customized the colors, apps, etc, takes a really long time to reset everything. I tried backing up and restoring with my purchased mybackuppro, but every time I restore something with that, its no longer a clean flash and I notice the ROM has "issues", so I'd like to bypass a 3rd party backup app. Thank you!
[Android Software Development] marsian0:
There is a proven method to backup preferences, by backing up the LMT.xml file, search the thread, i use it all the time and work flawlessly. Lately I've been using it a lot because of oreo testing [emoji6]
[Android Software Development] maflin18:
Anyone have any luck using PIE on the bottom of display with Oreo? (ie, find a way to disable system nav bar....possibly with a substratum theme?)
[Android Software Development] divineBliss:
Thanks! This is the file to backup/restore with a rooted file manager:

/data/data/com.noname81.lmt/shared_prefs/LMT.xml

File permission: 660

Owner/Group: LMT/LMT
[Android Software Development] marsian0:
Sure it is, just remember to force stop the app after creating the first one pie, and set appropriate permissions and owner to the file after restoring it.
[Android Software Development] Ztones:
Thanks, but it's not working for me. I copied and pasted my old lmt.xml file to /data/data/com.noname81.lmt/shared_prefs/LMT.xml but lmt is not picking it up. No change.

Here is another bug I discovered. I never knew what caused my volume panel to be stuck on display (when hitting the volume buttons up or down, the graphic that shows the volume slider). The LMT accessibility service is messing it up. When I turn it OFF, the volume panel disappears like it should after couple of seconds. When I turn ON the LMT accessibility, then the volume panel stays stuck on display until I touch somewhere on the screen.
[Android Software Development] divineBliss:
Did you to a force stop LMT, copy the file, and change the file permissions, etc to what they need to be? See my last post for what mine are. Maybe try rebooting the phone after the force stop and copying the file. I haven't personally verified this method works on my phone since it just came up for me today.
[Android Software Development] Ztones:
I did force stop lmt and tried rebooting phone. See attached for what my options are for file permissions. I don't know how or where to set #60 (or 66? I forget what you wrote)? Thanks
[Android Software Development] divineBliss:
660 = only owner and group should have read and write checked.

Be sure to set UID and GID to correspond with LMT.

Try Total Commander file manager - it's the best :)
[Android Software Development] Ztones:
It's still not working but at least I got the total commander installed! Thanks!

I ended up using the mybackup pro restore and that did it. Now the only issue is that the volume panel doesn't go away with LMT 's accessibility turned on.
[Android Software Development] Ikkuh84:
Aaah, is LMT causing that... cause I have the same bug then. Thought it was my rom (first CM12.1 and now Lineage13 on my HTC One M8s).
[Android Software Development] xSilas43:
For anyone on Android O, you can download the Custom Navigation Bar app from the playstore to allow you to enable immersive mode everywhere for the Navbar only, aka hiding the navbar in O!! Then back to glorious free screenspace and LMT.
[Android Software Development] maflin18:
Immersive mode is not sufficient, as the system nav bar pops up every time you swipe up from the bottom of the screen (attempting to trigger LMT PIE). We need a mothod of DISABLING nav bar, not simply triggering permanent immersive mode.

Some custom ROMs support this ability (such as pure Nexus), but so far I can't find any way of doing it with stock ROM. There has to be a way to do it, though.....
[Android Software Development] marsian0:
For this, buil.prop should be modified, but the property maybe is different for every phone / android version. I have a nexus 6 and this property works only till N, in O doesn't work anymore, but through custom rom works ok.
[Android Software Development] maflin18:
This is true. However, after update to Oreo, modifying system ui on Pixel to hide nav bar is broken. Causes infinite system UI crashes, and occasionally even a forced data wipe.
[Android Software Development] Golf c:
I pm'd you a gift. Im getting tired of watching you suffer. Haha!

---------- Post added at 10:08 PM ---------- Previous post was at 10:03 PM ----------

Also this might work.

https://xdaforums.com/nexus-6p/them...-changer-android-nougat-t3447956/post73953260
[Android Software Development] xSilas43:
It's been reported that the overlay doesn't work on O anymore, so I thought I'd share the immersive mode as a temp fix.
[Android Software Development] Golf c:
The overlay doesn't work, but what about editing the dimens.xml? Haven't tried it myself. He just posted that today. Read the post I linked.
[Android Software Development] xSilas43:
Yeah you can decompile your system framework and manually change the height to 0 then recompile and replace it. That's a lot of work for a temporary solution imo, I'm sure a substratum theme will be updated shortly.
[Android Software Development] Golf c:
I thought that might be alot of work. I was looking around at the framework folders. Sounds beyond me. Thanks for confirming.
[Android Software Development] xSilas43:
You only need to decompile the android-framework.apk or whatever it's called in the /system/app or /system/priv-app/ but yeah it's a lot of work that will be replaced next time you update ROM or stock.