Database Info

Magic Button Question

I am using magic button to close my apps as opposed to just minimising them, however I always get the "Phone" icon left on the screen, this is the screen that appear when you dial a number (the phone pad). For some reason this just won't closed and always becomes the focused application whenever I close another application.
Is there a way around this?
Is this a bug?
Any help appreciated..
Thanks
Mark

mdavenport said:
I am using magic button to close my apps as opposed to just minimising them, however I always get the "Phone" icon left on the screen, this is the screen that appear when you dial a number (the phone pad). For some reason this just won't closed and always becomes the focused application whenever I close another application.
Is there a way around this?
Is this a bug?
Click to expand...
Click to collapse
No, it's because if you are actually closing the Phone dialer application, you are eliminating the ability to use the phone. That's why the application always runs.
Tap and hold the Phone icon, and select "Don't Show when Inactive". The icon will disappear, but the phone will still work fine. Do the same thing for ActiveSync, if its icon shows.

Thanks, thats great....

[Q] Always open Quick Settings?

Hi,
it's pretty annoying that you have to tap twice to open the quick settings... first tapping the clock and then the settings symbol.
Is there any way to always open the quick settings?
may only if there are no notifications?
Thanks!

I just put the settings app which you can find in the "other" section when you long press on your home screen, onto my home screen. Just one tap needed now to get to them.

yes, but that opens just the normal settings menu...
i like the settings-popup, it would be cool if this could be modified and always opens for quick access

[Resolved] Nexus / Play Edition Devices - Keyguard => Home Button and Top of Screen Unresponsive

Nexus / Play Edition Devices - Keyguard => Home Button and Top of Screen Unresponsive
When I installed 5.1.1 on my Nexus 7 mounted in my car, I noticed a weird bug with Car Mode Control being activated - the home button would freeze up the screen, locking it on an all black screen, and the status bar along with another 10% from the top of the screen was unresponsive to touch. Now, I know there are issues with Nexus devices running Car Mode apps, but without reinventing the wheel (or at least having to code a ton more stuff into Tasker), it's the easiest way for me to send up accompanying things, like Car Home Ultra and activating tethering, etc.
But this is just obnoxious. I can barely get the search bar to work on Google Maps, I have to hit just the very bottom of the bar to get it to open up the recent searches and allow me to type, and most 3-dot menus cannot be hit anymore. When I got my Moto X Pure, I noticed the same thing was happening, so it wasn't A) the Nexus 7, B) Car Home Ultra, C) at one point I even considered it was Nova Launcher, but rather D) just being in Car Mode. The MXPE comes out of this state easily enough with doing a screen off and back on, but the N7 does not - I either have to disable wifi tethering which disables car mode on the N7 via a Tasker task, or restart it in some extreme cases. I have Car Home Ultra on my N7 but not my MXPE, so the suggestion that it has something to do with a bug in the home button override of Car Home Ultra doesn't hold water, unfortunately (thought of that as the culprit already too).
I think this may be a "safety feature" of Nexus / PE devices that if car mode is activated, you can touch certain things and go back home, but if I can't pull down the status bar, I can't set car mode off unless I turn off my car, which kills Bluetooth and my Tasker task to keep my phone in car mode when connected to the car's BT. NOT ideal for someone who drives 1,000+ miles per week for work and needs to check and send emails while I'm stopped waiting for my next assignment to start (insurance related career). I find it even more absurd that not only is the status bar blocked from access, but all apps just below that as well, including the search bar on Google Maps as I said already. How am I even supposed to search for the next destination without being able to access that bar easily?
===========================
TD;LR - Nexus and Play Edition devices don't like Car Mode being forced on them through apps that turn on car mode, it makes them unresponsive to certain parts of the screen and doesn't allow the home button to work, is there any way to enable car mode without having to build a Tasker task that does what car mode does for me?
===========================
EDIT - Figured it out.... I had Tasker setting Keyguard Off instead of using Secure Settings to clear password when connected to the car's Bluetooth as detailed here. I've read previously that setting the keyguard off has had adverse reactions inside Android, but I didn't connect the dots here, these are the issues that occur when you set keyguard off! So yes, using Secure Settings to clear password works much better and doesn't produce these crazy bugs.

one-handed mode activity?

I'm trying to write a Tasker task that would, among other things, trigger one-handed mode on my S8+. Simulating the triple home button press doesn't work as it's too slow, and I don't want to use the swipe as it stupidly resets the size of the reduced screen to default (I prefer it a bit bigger). So now I'm trying to figure out what the activity is that launches when you put the phone in one-handed and trigger that directly. It does not appear to be something you can adjust through settings as I took a list of settings from adb before and after triggering the mode change and nothing was different. Any thoughts on locating this?

You can resize that window as well. Swipe from the edge of the screen as you normally do, then swipe towards the bottom of the screen without lifting your finger up.

BurakSsl said:
You can resize that window as well. Swipe from the edge of the screen as you normally do, then swipe towards the bottom of the screen without lifting your finger up.
Click to expand...
Click to collapse
Thanks, that might be useful. But can Tasker simulate that input of swiping up and then down without lifting?

Update: logcat shows a few interesting messages when one-handed mode is started. The first output is "SamsungPhoneWindowManager: toggleEasyOneHand() enabled=1". Then there's some stuff that seems to control the screen shrinking animation and set up the background for the non-usable screen space, and then there's a vibration call from a package called "com.sec.android.easyonehand".
I figure my best shot at doing what I'm trying to do is to either find a way to send that toggle command to the window manager directly or figure out the right activity to start in that system package. Unfortunately it looks like inspecting the package manifest is a no-go. Anyone have any thoughts on the next step?
Edit: was able to get the manifest after all. There's an intent filter action called "com.samsung.action.EASYONEHAND_SERVICE". I've tried calling that with an am start command in terminal emulator and I get "unable to resolve intent".

So you could not find a proper solution? Im interested in this too

Question [SOLVED] Wake Phone With Watch

I am wondering if there is a simple way to wake a phone's screen from the watch, similar to selecting "Edit on phone" when selecting a new watchface?
I finally have a working VNC viewer on my watch, but none of the commands will wake the phone's screen, even if the phone is already unlocked. I can wake the phone with a BT keyboard just by pressing the space bar, or some other keys, but it doesn't seem to work from the watches keyboard. From my understanding, a tasker might do the trick, but am wondering what your thoughts are? Thanks!

Ah, never mind. It was an issue with the VNC server on my phone. After updating the app, the screen wakes upon connecting.

FYI: If anyone wants another method of waking their phone from their watch, a remote input app such as WearMouse works.