Known Issues on Android 6

Post your questions and help other users.

Moderator: Martin

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

Re: Known Issues on Android 6

Post by Martin » 20 Mar 2016 19:54

It was just luck that my test-S7 behaved the same way so I could reproduce this problem. The log indicates that the permission is missing so I switched the 'change system settings' permission off and on again and it started to work :D.

User avatar
1-2-Hak
Posts: 21
Joined: 02 Jun 2014 21:06

Re: Known Issues on Android 6

Post by 1-2-Hak » 20 Mar 2016 21:03

Good news anyhow. it was an important part of my use and had been using it for ages. Keep up the good work - love my Automagic :)

User avatar
mick64
Posts: 9
Joined: 17 Aug 2013 09:34

Re: Known Issues on Android 6

Post by mick64 » 27 Mar 2016 17:33

Bump...
Any idea why the NFC trigger isn't working? I use this to switch on several apps when I put my phone in its holder in my car. It was working OK before my S6 updated to Android 6. I've been using Automagic for years and this is the first real issue I've had.

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

Re: Known Issues on Android 6

Post by Martin » 27 Mar 2016 18:09

Sorry, I've missed your post. Are you using the trigger with a tag that was written by Automagic (Automagic Tag ID) or a read only tag (like credit card etc.)?
Try to reboot the device and toggle NFC in system settings off and on again to see if this helps.

User avatar
mick64
Posts: 9
Joined: 17 Aug 2013 09:34

Re: Known Issues on Android 6

Post by mick64 » 29 Mar 2016 14:44

Hi Martin,
I'm using a read only tag. I've tried turning the NFC off and on, etc. I've also tried turn app permissions, ect off and on as well, but nothing has worked so far.
When I first got my S6 everything was working fine. It was only when it updated to Android 6 it stopped working. I just get a message saying the tag or trigger is not available.

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

Re: Known Issues on Android 6

Post by Martin » 29 Mar 2016 18:29

Hi,

It sounds like the device might still invoke the trigger of Automagic. Is the flow with this trigger enabled in Automagic? Can you please turn on Debug Log, scan the tag one more time and then send the log to me (menu->Manage->Log, menu->Send Log)? Please also include the flows when submitting the logs so I can check if the value sent by the device matches one of the triggers.

Regards,
Martin

cridemichel
Posts: 1
Joined: 05 Apr 2016 19:29

Re: Known Issues on Android 6

Post by cridemichel » 05 Apr 2016 19:35

Hi all,
I have just bought this great app but I noticed that on my nexus 4 with cyanogenmod 13.0 snapshot
the "Set Mobile Network Mode" action is not working at all while I thought it was already fixed, isn't it?

follow-up: now it works after having enabled "telephone permissions" under Settings->App->Automagic Premium->App Permissions!

best Cristiano

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

Re: Known Issues on Android 6

Post by Martin » 06 Apr 2016 19:39

Hi,

Thanks for the report! I'll add the missing permission check to the action in the next update of Automagic.

Regards,
Martin

nbi
Posts: 25
Joined: 30 Apr 2016 21:49

Re: Known Issues on Android 6

Post by nbi » 12 May 2016 18:43

The Storage Media Event trigger for "Mounted" is not working in Android 6 (cm-13.0-20160418-SNAPSHOT-ZNH0EAO2NJ-d801). At first I tried checking with notifications, but none were generated. Then I looked at the log and there were no entries corresponding to the plugging in of my OTG USB drive, i.e. the trigger never fired. There are brute force workarounds possible, but this trigger would have made life a lot easier. I'd rather not spend my time coding extensive shell scripts to handle detection of a mount operation. If there are simpler Automagic workarounds please let me know. Thanks.

UPDATE: The other plausible events that might catch USB insertion aren't being caught neither. It seems the SME trigger is completely broken for Android 6. :(

UPDATE: The "File Observer" trigger is broken as well. I tried using this as a workaround to check for the creation of a mount point in the directory of /mnt/media_rw (where USB is mounted in Android 6) but this trigger never fires neither. I think you may need to execute 'setenforce 0' (SELinux permissive) before checking for trigger conditions (and of course reset to "enforcing" after your checks are complete).
Last edited by nbi on 17 May 2016 21:08, edited 2 times in total.

kastr
Posts: 3
Joined: 15 May 2016 16:07

Re: Known Issues on Android 6

Post by kastr » 15 May 2016 18:44

Wlan scan result not working with Android 6. Tested with Automagic 1.3.0 and 1.3.1 the variable are always empty or null. Any idea?

Galaxy Note 4

Post Reply