Add LlamaLab Automation

Go to the Main github page for explanation ("how to ..") and screenshots

Changelog:

• giladg (Gilad S.) added functionality for Llamalab Automate. A tool to automate various tasks and app flows on your Android device.

modified build for uis7862/uis8581a

Go to the Main github page for explanation ("how to ..") and screenshots

Changelog:

• Added code for better compatibilty with uis7862 (ums512) and uis8581a (sc9863a).
• code beautifying and improvements (Thanks to Mario Dantas)
• dos2unix some xmls

Beta Release 1.4.0

Main github page with some extra explanation and screenshots

Changelog:
Beta due to insufficient testing possibilities as I myself have a unit with only HOME/BACK/Vol+/Vol- buttons

In previous versions you could only start an app by package name like: com.syu.radio if you wanted to start the FYT radio (BAND) app.
Currently there are 3 options to "start something" with the "Call method"

• by package name
• by intent (package name / intent)
• by system call (terminal command(s) or script)

by package name: This is NOT the name of the apk but the internal package name.
How do you get this "package name"?

• Use the "List all Installed apps" option in the main screen of the settings. It shows the app icon, the app name and the package name. This package name is what you need. You can select it and copy & paste it into the field.
• Search in play.google.com for the app you want to start. Say you want to start the navigation app "Magic Earth" and you have selected that one in the play store (in a browser, not the android app). In the address bar you will then see "https://play.google.com/store/apps/details?id=com.generalmagic.magicearth". The bold part behind the "id=" is your package name.

by intent: Every app has a "launch" intent to start the app. Some apps can also be started with other intents to immediately start a specific function. Google Search can be started with the launch intent, but you can also start it with the Google Voice search option intent. The Google (Search) package name is "com.google.android.googlequicksearchbox", the specific intent for google voice search is "com.google.android.googlequicksearchbox.VoiceSearchActivity". The combined "String to be used" is therefore "com.google.android.googlequicksearchbox/com.google.android.googlequicksearchbox.VoiceSearchActivity".
Another example is the Joying Bluetooth apk having intents for the dialer (default launch), the call receiver, the bluetooth streaming, the pairing and a few more.

by system call: A system call can be a direct (linux) command or a shell script or a binary (to do something).
= Commands can be a single command as in:

1. "ls -l > /sdcard/some_file.txt" to capture a directory listing to a file
2. "input keyevent 3" => Go to the Home screen (of the default launcher)
3. "am start -a android.intent.action.MAIN -c android.intent.category.HOME" => Go to the Home screen (of the default launcher)
4. "input keyevent 127" => pause active media player (any media player)
5. "input key event 126" => (re)start last used media player.
6. "am start com.syu.radio/com.syu.radio.Launch" => Start the radio app with the default launch intent (or better use "by package name": com.syu.radio; Or use "by intent": com.syu.radio/com.syu.radio.Launch)

Beta release 1.3.0

Changelog:
Beta due to new combined MODE button functionality and ACC_OFF and ACC_ON functionality

Note: The BT functions in rotating MOD/SRC button/option cannot be tested by myself. The other functions in this rotating carousel MOD/SRC button/option do function.

• Add "Media Key" option to EQ button (Thanks to IG_Vasilich): If you have a unit with hardware buttons, this EQ button is pretty useless for everyday operation. So I made it possible to assign a "Media Key Event" to it if you don't want to use it for assigning an app to it (default option). This means you can assign next/previous/play/pause/toggle-playpause to it. Especially on a car without steering wheel keys and with hardware buttons on the unit this is really helpful (that is: to me in my car with my unit)
• Alter mediaplayer pause/start to ACC_OFF/ACC_ON function to same function used for EQ button.
• Add receiver for BT functions for MOD/SRC carousel button. Does it work? I don't know as I can't test it.
• Minor modifications/additions to explaining Readme on github page.

That "secondary" function of next/previous/play/pause/toggle-playpause can easily be extended to any of the currently configured buttons (apart from those nasty BT mod/src functionalities probably)

Beta release 1.2.2

Changelog:
Beta due to new combined MODE button functionality and ACC_OFF and ACC_ON functionality

Note: The BT functions in rotating MOD/SRC button/option still do not function. The others in this rotating carousel MOD/SRC button/option do function.

In 1.2.2:

1. Fix crash in ACC_ON settings
2. reactivate Sofia ACC_OFF intent (different from PX5 / 9853i)
3. Create simple About screen

From 1.2/1.2.1 (Not modified in 1.2.2):

1. Modify BT rotating again. Can't test myself.
2. Implemented ACC_OFF and ACC_ON functionality; ACC_ON only functions with nokill mainserver mod.

Beta release 1.2.1

Changelog:
Beta due to new combined MODE button functionality

1. Modify BT rotating again. Can't test myself.
2. Implemented ACC_OFF and ACC_ON functionality; ACC_ON only functions with nokill mainserver mod.

Beta release 1.1

Changelog:
early Beta due to new combined MODE button functionality

• Make copy & paste possible for package names (List apps screen to settings fields)
• Add MODE/SRC button capture. The default functionality of this button should be:
  1. radio (working)
  2. BT phone (not working)
  3. BT AV (not working)
  4. DVD (working)
  5. Aux (working)
  6. Video (working)
  7. Audio player (music) (working)
  8. iPod (not working)
  9. ??? (depending on device and configured external options?)
     Aux and iPod can't be captured. Devices and/or apps not installed/implemented in the head unit will be skipped by the$

Initial release

Version 1.0
See the Readme for the explanation.