Page 1 of 3
Will Android 11 break Automagic?
Posted: 22 Aug 2020 09:14
by Micky Micky
Hello
I'm running AM 1.38 on Android 10.
When Samsung update my phone to Android 11 will that be the end or will I just lose some functionality?
I think the permissions changes will cause problems.
https://developer.android.com/preview/p ... ermissions
Many thanks
Micky
Re: Will Android 11 break Automagic?
Posted: 22 Aug 2020 16:52
by Desmanto
Only time can tell. From the description, it seems the app must target android 11. Since AM stop already now, so It shouldn't be affected (until some time in the future where google enforce this).
Re: Will Android 11 break Automagic?
Posted: 22 Aug 2020 19:19
by Micky Micky
So the clock is ticking.
Android 11 is at beta stage. It will be a while before Samsung releases it.
I've converted 3 flows into apps. Crude but they work. I hope to have them all done before the end of AM. After that I might have learned Java!
Many thanks
Micky
Re: Will Android 11 break Automagic?
Posted: 27 Aug 2020 16:44
by Frank16
Oh je, also sogar ab Android 10 sind schon zwei für mich wichtige AM-Funktionen nahezu unbenutzbar geworden. Automatischen Bildschirmaufnahmen sowie Screenshot sind nicht mehr möglich, weil jede (!) neue Aufnahme neu gestattet werden muss - getestet bisher mit Huawei, Motorola und OnePLus unter Android 10. Die Einschränkung wurde vermutlich aus Sicherheitsgründen in Android 10 eingeführt. Mir ist bisher kein Weg bekannt, um das zu ändern. Behelfe mich derzeit, indem diese vorgeschalteten Warnmeldungen mit einem AM-UI-Flow automatisch bestätigt werden. Zudem gibt es noch einige brauchbare Smartphones, die kein Android 10 bekommen.
Re: Will Android 11 break Automagic?
Posted: 27 Aug 2020 17:32
by Micky Micky
Translation:
Oh dear, so even from Android 10, two AM functions that are important to me have become almost unusable. Automatic screen recordings and screenshots are no longer possible because each (!) New recording must be re-enabled - tested so far with Huawei, Motorola and OnePLus under Android 10. The restriction was probably introduced in Android 10 for security reasons. I don't know of any way to change that. I am currently helping me by automatically confirming these upstream warning messages with an AM UI flow. There are also some useful smartphones that don't get Android 10.
Re: Will Android 11 break Automagic?
Posted: 27 Aug 2020 17:40
by Micky Micky
Hello
Action: TAKE SCREENSHOT throws up a warning message
- Screenshot_20200827-183338.jpg (453.94 KiB) Viewed 52301 times
But recently someone enlightened me about the function:
takeScreenshot()
This in the action CONTROL UI. Unlike TAKE SCREENSHOT you can't define where it is saved or it's filename.
Hope this helps.
Micky
Re: Will Android 11 break Automagic?
Posted: 27 Aug 2020 17:57
by Micky Micky
Samsung S10 running Android 10 has a screen recorder built-in. Accessible only from the quick setting tiles.
Screen recording via AM throws up the same warning message as mentioned before.
Re: Will Android 11 break Automagic?
Posted: 31 Aug 2020 13:29
by tsolignani
I downgraded to Android 9 to have a better Android and keep using Automagic.
For the latter, I just hope someone takes on it and keeps the development, I couldn't use the phone without it and at the worst I would convert to Tasker.
Re: Will Android 11 break Automagic?
Posted: 31 Aug 2020 20:10
by Micky Micky
Hello,
Automagic and Android 10 is okay.
Android 11 is the expected problem.
Android Studio is the way forward not Tasker etc.
You just need lots of time, eg 12 hours to create a Bluetooth trigger
Good luck with whatever path you take.
Micky
Re: Will Android 11 break Automagic?
Posted: 09 Sep 2020 11:40
by Serum_114
Just installed Android 11 and Automatic was crashing repeatedly. Once I could get in I began disabling flows in order to find the cause of the crashes. It seems that with Android 11, if you use a broken function, Automatic doesn't report the error, it just crashes. By bypassing some unsupported functions I was able to stop the endless crashing. I can live without what I've removed this far but I've been at it for a very short time.