yashsingh1/xdaforums huggingface dataset:
[Android Software Development] schiphol:
Hi Guys,

I've used search but I can't for the life of me figure out how to disable the "dark curtain"/ black overlay that happens when you pull out the pie ring. Can't it be turned off?

EDIT: FIGURED THIS OUT It's gone when setting show status info =disabled... Next issue I really can't figure out though!

Also thought I'd check out the ISAS functionality; it's truly awesome but it doesn't disable the swipe action of the apps that are open if you understand what I mean. This way in many apps I unintendedly switch tabs/home screens etc when swiping from the sides ON TOP of LMT performing the requested command. What am I doing wrong?

Thanks and apologies if this had been asked before, couldn't figure it out.
[Android Software Development] noname81:
If you still want the status infos but not the curtain you can set the status infos colors. Just set the dim color there to 0 alpha...

For your isas problem: you can fine tune the isas activation area thickness in the settings so that you limit the false positives. And/or you can blacklist apps for gesture recognition...

Hth!
[Android Software Development] noname81:
Hi all,

fyi: I just uploaded LMT v2.5 beta3 to the OP. The only change is the support for Android M. Please test and let me know, if you have issues with it...

Have fun!
[Android Software Development] noname81:
Hm, I don't see any application code executed from LMT so I don't have any clue... I only see that Xposed is running and LMT is crashing indirectly, since the AccessibilityManager is not able to send an event (TYPE_WINDOW_CONTENT_CHANGED) to LMT:

E/AccessibilityManager(26355): Error during sending EventType: TYPE_WINDOW_CONTENT_CHANGED; EventTime: 213452; PackageName: com.android.lmt; MovementGranularity: 0; Action: 0 [ ClassName: android.widget.FrameLayout; Text: []; ContentDescription: null; ItemCount: -1; CurrentItemIndex: -1; IsEnabled: false; IsPassword: false; IsChecked: false; IsFullScreen: false; Scrollable: false; BeforeText: null; FromIndex: -1; ToIndex: -1; ScrollX: -1; ScrollY: -1; MaxScrollX: -1; MaxScrollY: -1; AddedCount: -1; RemovedCount: -1; ParcelableData: null ]; recordCount: 0

A workaround could be to deactivate LMT in the accessibility settings. But the real cause seems more related to a Xposed framework bug in conjunctions with the AccessibilityManager.

What phone and what Android and or ROM version is it?
[Android Software Development] IronTechmonkey:
A tangential question about ISAS (with apologies if I've missed a known workaround when searching and testing). Although I have not used ISAS much; recently while chasing issues with Moto E's poorly designed touch screen (prone to scroll bounces and taps causing scrolling) I used LMT ISAS as a test and to my delight it worked quite well but with one oddity which I'm not sure is normal. In order to use swipe down from top of screen or swipe up from bottom it seems that I have to start the swipe on the status bar or the navbar respectively and this causes unwanted other actions. Is there a workaround for that forces the down swipes area to start just below the status bar and the up swipe areas to start just above the navbar?
[Android Software Development] noname81:
Lmt's isas do not consider status bar and navbar height atm. So the issue you're describing is the current implementation status. I normally have my navbar hidden, so it's no issue for me. In addition I don't use isas from the top! :D If the activation area would not start directly at the screen border you wouldn't be able to swipe from the outside of the screen for isas. Atm it's really nice, that you can do that, considering e.g. no navbar is visible.

I could think of automatically making the top activation area bigger in case a status bar is visible and the same for the bottom activation area and the navbar. Would that help?
[Android Software Development] IronTechmonkey:
Thanks for the explanation. Those things might help but I don't think they are worth spending time on unless there is greater demand. In truth this is more of a curiosity than an issue for me. I don't really use ISAS daily (heavy Pie consumption is more my thing) but it did serve as a great control test for the screen touch issues I was chasing. Grazie mille.
[Android Software Development] noname81:
Fyi: The Android developer options have a nice touch trace and analyze tool for touch problem debugging.
[Android Software Development] IronTechmonkey:
Ha!. Perhaps you could hear the forehead slap from where you are :). "Pointer location" - Screen overlay showing current touch data". Within 30 seconds I was able to determine that occasionally single taps (with a minuscule about of roll or drag) were indeed being perceived as upward vertical swipes with length about 40% of display height. I tapped, and the indicator line drew up from the tap location like a reverse lightning strike. Diagnostically informative and nifty looking. Thanks!
[Android Software Development] MrKaon:
[MENTION=1864347]noname81[/MENTION] it is possible to add a option to hide soft keys without disabling them so key 219 would work?
[Android Software Development] Kappa Lamda:
Thank you. First of all LMT and xposed were working on all roms I tried. That's CM 12.1 official, Resurrection Remix, PAC, Liquidsmooth. This bootloop/reboot problem occurs only on XenonHD. All these roms have LP 5.1.1. Others have r18 and some r24.

I use xposed v75.

This logcat is with v75 flashed in recovery but with no xposed app installed or any modules. Also I've done some more testing.

After removing LMT, I finished the set up of my phone. I installed the xposed apk, amplify, appoppsxposed and powernap modules + greenify donate. Activated all of them and rebooted without problems. I let the phone for about 5-6 hours and used it without any problems.

So I decided to take a backup and test again LMT. Till now I was using LMT 2.4. Now I downloaded 2.5 beta 2. Installed OK. When I activated LMT though, immediatly I had a reboot(hot, I mean reboot from bootanimation) and then bootloop. By bootloop I mean the continuous reboot, boot problem. So I had to restore my backup.

What looks weird to me is that with other roms I do not have any problems. Not at all.
[Android Software Development] DutchDogg54:
Hey [MENTION=1483026]MrKaon[/MENTION] - I'm fairly confident [MENTION=1864347]noname81[/MENTION] hasn't missed the numerous posts about this subject in the last 5 pages of the thread...including yours. In fact, I know he hasn't since he engaged the subject here.

You've now requested this twice today - how about you give the guy a chance to actually do life, first of all, and second of all, have a chance to actually develop something like that, if it's intention.

At this point, your breaking rule 5 about posting a message only once & 2.3 about not posting in a demanding way or disrespectful way.

Sure, you were respectful in your word choice & tone, but the content of your message is disrespectful because you're posting a request multiple times. This is a free application that freakin' rocks. In this circumstance, the right behavior is to graciously accept what we're given and enjoy. A one time mention of a request in a thread where the developer has been open to such posts, is reasonable. Beyond that you're in the "demanding" arena, outlawed by rule 2.3.

I'm not reporting anything or taking any moderator action at this point, just a friendly reminder to you and all others that when developers provide awesomeness and expect nothing in return, it's only polite to hold your tongue about requesting more features, enhancements, changes or anything.

Carry on :highfive:
[Android Software Development] Pecata:
I can confirm with beta3 the lag when using back and home button in Marshmallow is gone!

Once again-thank you [MENTION=1864347]noname81[/MENTION] for the fabulous work!
[Android Software Development] MontAlbert:
Unfortunately I'm not seeing those activities in my dialer.

My dialer is aosp dialer although I'm using xtrasmooth rom which is meant to be a stock factory image with a few tweaks? Either way, it doesn't work for me. Nexus 6
[Android Software Development] noname81:
I'm on stock and the activities you're seeing are for me under Phone Services. Seems like there are differences in your rom...
[Android Software Development] matt1515:
Just to confirm LMT is working perfectly on my Nexus 5 on 6.0(rooted) with chainfire's latest boot.img and SuperSU 2.52 on enforcing! Nice work! If anyone finds it won't work on enforcing reboot and clear cache and dalvik.
[Android Software Development] BxingFetus:
I'm having an issue on my n6 cataclysm marshmallow rom where the notification/quicksettings pulldown when put into pie controls makes the pulldown drop very slowly. Anyone else notice this?
[Android Software Development] Atomregen:
There is the same problem with gestures in Nova Launcher.
[Android Software Development] BxingFetus:
I'm using Google now and lmt is an awesome pie control. I'll peek in from time to time to see about a fix.
[Android Software Development] thedeadfish59:
For galaxy Y , v2.1 isnt working, fc at startup, have roo access, what should I do? P.S: Im on stock
[Android Software Development] noname81:
Which Android version is it? Why don't you use the latest Lmt version? Can you post a logcat from the crash? Thanks!
[Android Software Development] thedeadfish59:
I'm on 2.3 Gingerbread and you turned off comp for 2.x/3.x in latest versions :( so this is the last version for me
[Android Software Development] GatoL0c0:
Being 5 versions behind (with multiple updates in between) in Android has its downfalls. You can't expect all apps to continue functioning with an OS that old.
[Android Software Development] thedeadfish59:
Now whats the ques is why v2.1 ForceCloses in GB , if ya can help thats much appreciated :)
[Android Software Development] kenkiller:
Marshmallow bug. All non manual ways of activating the notification shade will have the same problem.
[Android Software Development] BxingFetus:
Ah I see, well, I guess it's time to go apple then.
[Android Software Development] Magpie42:
LMT does not start Apps nor KillApps

Hello,

using LMT for years now and it's really amazing, Thanks a lot! :good:

Although it worked like a charm with my old Sony Xperia Z, running AOKP Android 4.2.2,

I ran into some problems after I switched to a new Xperia Z with Stock ROM Lollipop 5.1.1.

First approach was restoring it on the new phone with Titanium, but doing so, LMT didn't ask for Root permissions again,

thus I removed it completely, installed v2.5 beta 3 from scratch and went through the config process again, step by step,

so I guess, I got a definitely clean installation now, with LMT listed in SuperSu, too.

(BTW: Would be great to have a function to ex/import the settings, for backup and transfer purposes)

Main problems:

Although builtin buttons like Home, Menu, Back and RecentApps work perfectly fine,

none of the Pie buttons will launch any Apps (neither downloaded nor stock apps)

KillApp does not do anything

Moreover I tried to set up Level 2 Pie1 to a Tasker Task

(here: "Loc w/ WLAN Enter", which switches WLAN On, disables Mobile Data, sets Silent Mode to Vibrate and launches some apps)

Although this task works fine when called from Tasker or via an icon on the homescreen,

it gives a "Broadcast Error - Failed to execute Broadcast Task" when called via LMT's Pie button.

Would be great if someone can help me fixing this ...

Thanks a lot!

Cheers, Magpie
[Android Software Development] Skripka:
Well...Gingerbread is only 5 years old, and ran like crap back then...and doesn't run any better now. Treat yourself to a new device already.

I don't understand how anyone could put up with pre-ICS for so long. It is like people still running Windows 95.
[Android Software Development] 12gage:
Is there a way to remove an app from the blacklist without having to clear the list and start selecting from scratch?
[Android Software Development] noname81:
Seems like lmt is not having root in the end. Can you post a logcat from Lmt's start after you restarted the phone or killed Lmt with a task manager?
[Android Software Development] noname81:
I've always been too lazy to implement a proper handling... :D I've put it onto my to-do list now.

In the meantime you can only edit the preferences in /data/data/com.Android.lmt/shared_prefs/LMT.xml. The blacklists are just string lists. Just kill Lmt before editing the file...
[Android Software Development] noname81:
The permission problem you mentioned is fine. I can also see the issue in the logcat you provided but I don't know how to track it down now. Can you post the full logcat? Which SuperSu version are you using?
[Android Software Development] Magpie42:
Ok, full log in attached zip - hope it helps.

SuperSu is newest, I guess, as I installed it just a week ago ... let's have a look ... v2.46 Free.

Cheers, Magpie

P.S.: This was not an adb logcat, but started in terminal right before starting LMT ... please let me know if you need an adb logcat.
[Android Software Development] 12gage:
Thank you sir, at least I can change it without resetting now
[Android Software Development] Adreaver:
Quick question/feature request:

Any way to blacklist ISAS in certain apps? Or better yet, whitelist? I am using "swipe from left edge" to launch Google now, in an approximation of the way the Google launcher works. However, this is active in every app, all the time, and I would prefer it only be active on the launcher.
[Android Software Development] Koragg618:
Hey guys, I'm wondering if there's a way to stick the PIE controls to a certain edge, even after rotating? I don't want to enable all edges because I've had misclicks with it before. Is there an app the locks LMT's orientation? I wanted to have PIE open up on the bottom part of my phone (when holding it straight), no matter what the orientation.
[Android Software Development] bahrosuz:
Gesendet von meinem D5803 mit Tapatalk
[Android Software Development] Koragg618:
Like I said, I would like to know if its possible without enabling all edges
[Android Software Development] Koragg618:
I wanted to have it at the bottom while in portrait, but on the sides for the landscape, but to do that I will have to enable all sides, which I don't want to do that since you can swipe the sides in portrait mode by mistake or swipe the bottom by mistake.

I would like the activation point to stay at a side of the phone, regardless of the orientation (on my phone (Nexus 5), that is the side of the notification LED).
[Android Software Development] typongtv:
[MENTION=1864347]noname81[/MENTION]... Beta 3 doesn't work on nexus 7 2013 android 6. Is it just me?
[Android Software Development] lollyjay:
Working well on my N7/2013 w/stock 6.0.0 rooted
[Android Software Development] typongtv:
Alright... I shall uninstall, reboot and try one more time.
[Android Software Development] MrKaon:
Make sure you have latest SuperSU Beta.
[Android Software Development] typongtv:
Thanx..... That did the trick. ?
[Android Software Development] awakener777:
I'm still not having any luck launching apps from pie. I can do every other action from pie it seems just can't launch apps. Mostly what I use LMT for. It happened after updating cm12.1 with the new Android security updates early this month. So can't solve the issue.
[Android Software Development] IronTechmonkey:
Have you tried enabling LMT's accessibility service and changing selinux to permissive? Also, are you using CM's native SU or SuperSU?
[Android Software Development] awakener777:
Thanks that worked. For the record I'm using SuperSU. Not sure what happened to make this necessary but I appreciate your help!
[Android Software Development] IronTechmonkey:
I never had to do this in C11 or early CM12.x but since switching to a new device and using newer CM nightlys I've had to do this as well. So have a lot of other people as evidenced by posts in this thread. Google is closing some doors in the interest of security (or in the interest of their ability to be exclusive in their ability to invade our privacy). I only mentioned SuperSU because a bunch of things seem to like it better than native CM SU. Also, for those who may not be able to change selinux permission, Tasker can be used to create app shortcuts which can be invoked by LMT without those permissions. Takes a modest bit of setup but works well.
[Android Software Development] MrKaon:
On Nexus with latest SuperSU Beta, LMT is doing everything which supposed to do without any additional workaround. Except Google Tap On if soft keys were disabled by editing build.prop.
[Android Software Development] IronTechmonkey:
Thanks for the tips. I've read about a bunch of M issue resolved by superSU beta 2.52. Is that M or L you are using?
[Android Software Development] MrKaon:
Marshmallow Android 6
[Android Software Development] MrKaon:
I'm experiencing funny bug, back button doesn't work with Google Play Store!! While it is working anywhere else!

Nexus 5, Android 6, Latest SuperSU Beta.

Edit :

Restart fixed the problem.

Thanks
[Android Software Development] tkolst:
Hope somebody can help. I have note 3(n9005). rooted and flashed [ROM][AOSP][OFFICIAL][Lollipop 5.1][HLTE] PAC-ROM LP( http://xdaforums.com/galaxy-note-3/development/rom-pac-rom-lp-t3048388)

The only thing that wont work is the data toggle. There is no reaction. anybody have a solution. I read in the OP and note 3 is not mentioned. But I get to install it and so far everythings work accept data toggle.

I have installed the latest beta v3.
[Android Software Development] IronTechmonkey:
Since switching to CM12.1/L5.1.1 I have not been able to toggle mobile data with LMT's native toggle or the switches in tasker or secure settings but a Tasker task that runs "su -c svc data enable" and "su -c svc data disable" (with variables and conditions) is working as a mobile data toggle.
[Android Software Development] lollyjay:
Hi let me just say that I have used LMT for a long time on five different phones and tablets. Love it! My question is can I deactivate the capacitive keys on my Zenfone 2 and experience the "pure" LMT? I vaguely remember that I can edit keys in system. I know it's a bit off topic but maybe others would like to do it too.

EDIT: Never mind, found out elsewhere how to do it.
[Android Software Development] tkolst:
Thank You for Sharing, som no need to try anymore! Yes I also found data on off app working. Then I have to Use this. Thank You!! :)
[Android Software Development] Straynart:
Weird bug..

Hi everyone,

I use LMT for a long time now, and today I encounter a weird "bug": In the app list, first, I don't have all my app listed [e.g: whatsapp], and second, I have some apps I don't have on my device [Google Sheet, Google Slide, Swiftkey].

Does anyone have this bug ? I'm on the Beta3.

EDIT: A shutdown bring back ALL the missing apps.

But I still have a question: from what the apps list is made of ? I think the list is made from ALL apps installed or preinstalled even if you desactivate the app [I forgot that on the Oneplus Two, SwiftKey is preinstalled]. So can't we compose the list with only activated apps ? It would be better.
[Android Software Development] jtwebfusion:
Is there anyway to preserve the stock inner pie settings when adding to the outer ring for the first time? I'm on N6 with beta3.
[Android Software Development] ThePresence:
Hi

When I enable feedback I'm getting double vibration feedback....

I'm using Oneplus2
[Android Software Development] IronTechmonkey:
Is there a way to prevent Pie from running when an app like camera has been invoked from a lock screen shortcut while the device is still locked? I have a few pie shortcuts that I would not want available while the device is locked.
[Android Software Development] ch3mn3y:
You could probably use tasker (or alternative) to disable lmt when camera is used, byt as camera started from lockscreen is the same one started "normal" way, You wouldnt be able to use lmt any time You open camera app.

Sent using C6833 - AICP/GreatDevs
[Android Software Development] DutchDogg54:
Nope, it wipes the stock settings whenever you modify the pie mapping.

That's odd - I have a pattern lock and just accessed the camera from the lockscreen shortcut (I'm running stock rooted M) and pie would not appear at all for me.

But, I'd have to imagine if for some reason LMT did appear on the lockscreen-shortcut-initiated camera app, that any attempt to open an app or go to the home/recents/etc. would just bring you to the lockscreen pattern/pin again. You're saying that you are seeing the opposite happen - where you are able to access those things without unlocking? I've never heard of that and it's certainly a problem, if that's the case.
[Android Software Development] IronTechmonkey:
I'm running recent CM12.1 nightly but have seen things like this in CM11 and CM12.x on 2 different devices. Using pattern lock as well: Pie does not appear over the lock-screen but does appear over the camera. It does not appear over apps invoked by lock screen shortcuts or over the emergency dialer that is available when there are no shortcuts configured. After the camera is opened by lockscreen shortcut, Pie can be invoked and; although apps, home and recents are blocked, certain state changes are allowed such as Airplane Mode and possibly GPS. The native system handles this by "hiding sensitive" items from the QT when lock screen is invoked. So... the native security of QT at lock-screen is achieved by hiding those QT item at the lock-screen rather than by blocking the functions they point to some of which can be invoked in Pie. This occurs with native functions but, quite fortunately, Tasker is not allowed to run. Therein lies a workaround – using tasker to invoke those functions. Also, I can just remove the lock screen shortcuts which I actually prefer because… after all... it is a lock screen, not a GUI;).

IMO

- LMT and the camera app the should respect the same sensitive item setting as QT

- Camera run from lock-screen shortcut should be run like the emergency dialer, which seems to be a pinned-screen mode.

---------- Post added at 12:28 PM ---------- Previous post was at 12:26 PM ----------

I've use su -c killall com.android.lmt to temporarily disable LMT in an experiment with dynamic Pie icons, and still use that command along with setenforce 0 to give Pie permissive Selinux at boot, but LMT restarts immediately in those cases. I don't know how to programatically shut pie off and back on but suppose that even if that were possible I prefer the aforementioned workarounds.

[EDIT] Not an easy screen-shot to get but for having to avoid taking a picture while keeping Pie on while holding the phone with the appropriate hardware buttons pressed but, for kicks:
[Android Software Development] kolyan:
FEATURE REQUEST: Hide softkeys / navigation bar (perhaps 2 options, hide completely and automatic mode). Preferably without root
[Android Software Development] IronTechmonkey:
I think if that was easily and achievable and could be kept stable across many devices it would already be done. Also, considering that: 2 of the more popular ways to hide softykeys/navbar require root (GMD autohide softkeys app) and or direct editing of the build.prop file this does not seem to be an easy thing to just tack on. Do you know of anything that can hide softkeys and does not require root or editing of system files?
[Android Software Development] DutchDogg54:
[MENTION=5119654]IronTechmonkey[/MENTION] - Nailed it.

[MENTION=774086]kolyan[/MENTION] - This type of thing isn't possible without root because no matter the tool, it's modifying the system partition. The ability to do this is why the word "root" even means anything to us; it's the backbone of pretty much any true customization. It's certainly possible with root, and LMT acquires & uses root, so theoretically it can be done. Of course, that's up to the developer and whether he wants to make that part of his app. With Now on Tap appearing to be dependent on a non-build.prop related tweak, I'm sure he would love to include it, but as I've said before, we just need to patiently wait to see if it's something he's interested in doing.