[APP][ROOT] LMT Launcher v3.2

[DM_Sledge]

Just started using Google docs on my phone and I am reminded why I stopped. Editing any file breaks lmt pie navigation. Home works but task switcher falls silently and back tells me to enable accessibility. Disable and reenable accessibility and I can navigate again until I edit another file.

 

[ssuuddoo]

@noname81, you are our hero. Thank you very much for caring, working, trying, keeping. LMT is a supreme launcher helping me with my everydays work. I've had issues when I updated my phone (S22U) to official Android 13. Reading the forum, posts of others and downloading your fix in 3.13 the problem is solved. Thank you very much. I add some screenshots from my LMTs.
Thank you again. You've got my today's prayers . Greetings from Azerbaijan. +

 

[klark1kent]

@noname81
Android 13 user unable to achieve working Root privileges using LMT v3.3 a13_fix. I grant root permissions successfully using latest Magisk and su is recognized in su manager but LMT doesn't reflect root and unable to trigger Root shortcuts in Pie menu (i.e. KAA, Menu shortcut)

I've uninstalled, wiped app data, etc.

Runtime Permissions:
Root: false
Accessibility: true
DrawOverApps: true
ExternalStorageRead: true
ExternalStorageWrite: true
PhoneCalls: true
UsageStats: true

 

[noname81]

@noname81
Android 13 user unable to achieve working Root privileges using LMT v3.3 a13_fix. I grant root permissions successfully using latest Magisk and su is recognized in su manager but LMT doesn't reflect root and unable to trigger Root shortcuts in Pie menu (i.e. KAA, Menu shortcut)

I've uninstalled, wiped app data, etc.

Runtime Permissions:
Root: false
Accessibility: true
DrawOverApps: true
ExternalStorageRead: true
ExternalStorageWrite: true
PhoneCalls: true
UsageStats: true

Hm, I run this LMT version on a Pixel 7 Pro with Android 13 and can get root fine. So I assume it's related to your setup. Are other root apps working?

 

[klark1kent]

Hm, I run this LMT version on a Pixel 7 Pro with Android 13 and can get root fine. So I assume it's related to your setup. Are other root apps working?

EDIT: Turns out, and I'm no developer but feel confident it was improper folders/file permissions in the app data dir. I'm going to assume it worked with Root on the previous APK because I must have installed, confirmed root, and then like a lazy f*cker, restored a previous backup in order to get the pie configuration as it was previously. Not sure to be honest but it's the only thing I can think of that would have weird permissions persist after wiping data from settings. Not sure to be honest but long story short. Root functioning as normal again.


///
Other root apps are working fine - no problems. The odd thing here is that when I originally got the P7P I had the normal apk installed, the version that was producing the PIE issues prompting the Beta. On that version I'm pretty sure I actually was showing Root in the LMT menu and able to trigger Tasker Tasks and built in root functions when the Pie menu did come up briefly while still in LMT.

I'll keep tinkering with it and if I figure something out I'll let ya know in case it comes up again.

Quick question though, as I'm not going to lie, I was running Nougat before this on a samsung rom so this is crazy different for me, but do all debug apks populate in the App Compatibility Changes menu under Developer Options? If so, do you have any of the non-default selections enabled on your device?

 

[coconutxyz]

is it just me but it doesnt work in settings app or any system ui? i am rooted a12 lineage

 

[DiamondJohn]

is it just me but it doesnt work in settings app or any system ui? i am rooted a12 lineage

its a security thing, apps cant draw over settings. eg they could trick you into clicking nefarious menu items.

 

[coconutxyz]

its a security thing, apps cant draw over settings. eg they could trick you into clicking nefarious menu items.

thanks

 

[noname81]

its a security thing, apps cant draw over settings. eg they could trick you into clicking nefarious menu items.

fyi: I don't know when exactly this was introduced, but in Android 13 you can activate overlay apps in settings menus in the developer settings.

 

[coconutxyz]

fyi: I don't know when exactly this was introduced, but in Android 13 you can activate overlay apps in settings menus in the developer settings.

would that make lmt trigger-able everywhere? as a gesture app i would like it to be called everywhere because i usually disable the default gesture to create a seamless experience

 

[DiamondJohn]

Actually, I just noticed that my current custom rom DOES show my LMT style pie Maybe it was on my google Pixel stock ROM that it was disabled. I also read the security issue/block somewhere else.

PS: Im now on Bliss A11, but I am sure it was also disabled on the stock A11 pixel rom.

 

[noname81]

would that make lmt trigger-able everywhere? as a gesture app i would like it to be called everywhere because i usually disable the default gesture to create a seamless experience

The setting is called: Allow screen overlays on settings, so this applies only to settings screens.

 

[IronTechmonkey]

would that make lmt trigger-able everywhere? as a gesture app i would like it to be called everywhere because i usually disable the default gesture to create a seamless experience

Just curious, where else can you not invoke LMT, and are you referring to LMT-Pie, LMT-Gestures or LMT-ISAS? That overlay setting seems to have been introduced at Android 11, and on my A11 devices with that setting enabled there has been no place that I cannot use LMT-Pie, hence my question.

 

[noname81]

Just curious, where else can you not invoke LMT, and are you referring to LMT-Pie, LMT-Gestures or LMT-ISAS? That overlay setting seems to have been introduced at Android 11, and on my A11 devices with that setting enabled there has been no place that I cannot use LMT-Pie, hence my question.

This limitation only applies to PIE. Gestures and ISAS are more low level implemented and doesn't have this problem. The only other area, where overlays are not allowed is the security screens as e.g. lockscreen.

 

[DiamondJohn]

This limitation only applies to PIE. Gestures and ISAS are more low level implemented and doesn't have this problem. The only other area, where overlays are not allowed is the security screens as e.g. lockscreen.

I have a question regarding the " low level implemented " of gestures (possibly more of a rant about google). I have a Pixel 4a running A11, using a custom launcher. I was really annoyed when I disable the stock launcher, my system gestures stoppled working.. I would of expected that it would of been part of he OS and bot handled everywhere by an app (ie the launcher, which would be high on the list of customizations) and not the system.

Is thye5r4e something I am missing?

 

[noname81]

I have a question regarding the " low level implemented " of gestures (possibly more of a rant about google). I have a Pixel 4a running A11, using a custom launcher. I was really annoyed when I disable the stock launcher, my system gestures stoppled working.. I would of expected that it would of been part of he OS and bot handled everywhere by an app (ie the launcher, which would be high on the list of customizations) and not the system.

Is thye5r4e something I am missing?

Honestly I never checked how Google implemented the system wide gestures. I would have guessed in inputflinger, because here you can still decide to recognize a gesture or to dispatch the touch events to the foreground app. But as you said, there is this coupling to launcher.

When I implemented gestures for lmt, I decided to directly read the touch events from the kernel side by side to Android. This makes it really system wide but with the downside, that you cannot sync the gestures with app gestures and they can interfere.

 

[DiamondJohn]

...smip...

When I implemented gestures for lmt, I decided to directly read the touch events from the kernel side by side to Android. This makes it really system wide but with the downside, that you cannot sync the gestures with app gestures and they can interfere.

And thats how I would of expected any self respecting developer to do it. But not google... I guess every programmer has their first day at work. Dont even get me started on how they broke the previously working non-embedded album art....

PS: I didnt check, I just observed I lost my system wide gestures when I disabled the stock launcher, and they returned when I re-enabled it.

 

[DroidFreak32]

Edit- Misjudged LMT's capabilities.
Just a suggestion if it doesn't take too much time:
How about revamping the pie colors menu to also give us direct options to pick up various system colors?
So we could choose from a list of SystemAccent, SystemPrimary, SystemBackground etc whose values can be picked directly from the system theme. I think LMT already does that in A12+ but the default colors could be rearranged.
(i mean if LMT is hardcoded to use the "Primary" color for the icons, we could change that to system "Accent" color)
Dont mind this if its hard to implement, LMT is a godsend as it is now

 

[Natakranta]

Today I got my hands on a Pixel 7 Pro, and I took the time to check LMT on this. Honestly I didn't invest much time (yet) and also only checked and fixed the "PIE not coming up" problem. Please test and let me know, what other issues you observe. Thanks!

Thank you so much!
You're absolut hero!
LMT v3.3 a13_fix.apk solved pie not activating on OnePlus 8T after update to OOS13.
Root actions (screen off & open Power Menu) are working if anybody needs confirmation.

 

[hugozo]

Thank you so much!
You're absolut hero!
LMT v3.3 a13_fix.apk solved pie not activating on OnePlus 8T after update to OOS13.
Root actions (screen off & open Power Menu) are working if anybody needs confirmation.

Waiting for this to jump into oos13
Thanks for the test and thanks to noname81 for his great job !