No AutoMagic Menu dots acess

General discussions about Automagic and automation in general

Moderator: Martin

Post Reply
StillLearning
Posts: 7
Joined: 11 Jan 2016 04:13

No AutoMagic Menu dots acess

Post by StillLearning » 25 Apr 2016 07:34

I just added AutoMagic Premium to my Galaxy S4 but I don't have any way to set preferences as it does show the three menu dots at the top.

How do I get them?

Thank You

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: No AutoMagic Menu dots acess

Post by Martin » 25 Apr 2016 18:28

Hi

Some devices don't show the three dot menu at the top right corner, not sure if this applies to the S4 since I don't have this test device anymore.
Devices that don't show the three dot menu usually have a small three dot menu on the lower right corner or have a dedicated "hardware" menu button. On a few devices you have to long-click the app-switch button to show the menu.

What version of Android are you using? Are you using s stock ROM from Samsung?

Regards,
Martin

StillLearning
Posts: 7
Joined: 11 Jan 2016 04:13

Re: No AutoMagic Menu dots acess

Post by StillLearning » 27 Apr 2016 02:43

Right on the money Martin. The invisible button on the bottom left of the Galaxy S4 has the Automagic menu in it.

If I could pick your brain for a problem that stops me from doing alot on this phone.

When I run screencap -p /storage/emulated/0/screenshot.png , it always returns stderr=Error opening file:/storage/emulated/0/screenshot.png

Android 4.4.4 - rooted - stock ROM

screencap -h returns the -h this message -p save png ....

getExternalStorageDir() returns /storage/emulated/0

No problems created files in that directory space under File Manager HD

Can't doing much with this error rearing it's ugly head. Any help on why it states that?

Thank You again

User avatar
Martin
Posts: 4468
Joined: 09 Nov 2012 14:23

Re: No AutoMagic Menu dots acess

Post by Martin » 28 Apr 2016 18:08

Glad the menu is working now.
I assume you are using Execute Root Command to execute the command. Maybe the SE context needs to be set. Please try to use u:r:shell:s0 from the list or u:r:system_app:s0. Setting the SE context likely only works with SuperSU.

Regards,
Martin

Post Reply