Screen2Auto - New app for AA smartphone mirroring (only for root devices).

[tiho5]

Wee may need modded Android auto version. One that doesn't check for update internally.

 

[SOFO888]

Yeah. That's it. I tried my best, but could not make a modded Android Auto.

Perhaps someone has another idea how to do it?

 

[robi101012981]

Hello, I've received the oneui 4 android 12 for S20+ but screen2auto stopped working, it's basically crashing when I'm trying to open it onthe car...is there any fix for this?

 

[SOFO888]

As far as I know with Android 12 there is only this solution:
Post in thread 'Screen2Auto - New app for AA smartphone mirroring (only for root devices).' https://forum.xda-developers.com/t/...g-only-for-root-devices.4062787/post-86244997

With Android 12 it became really hard to use 3rd party apps on Android Auto.

 

[HeStauss]

Hello! Screen2auto works (again) on Android12 (Samsung A52) right after updating with

Android Auto 7.2.620124-release (arm64-v8a) (Android 6.0+)​

, except touchscreen functionality.
(see also Chat "Fermata Media Player - audio and video player for Android Auto", #754)

 

[mik101]

Hello! Screen2auto works (again) on Android12 (Samsung A52) right after updating with

Android Auto 7.2.620124-release (arm64-v8a) (Android 6.0+)​

, except touchscreen functionality.
(see also Chat "Fermata Media Player - audio and video player for Android Auto", #754)

Root or non-root? Did you re-enable the accessibility service?

Just working on a procedure for running everything / upgrading to Magisk24.1 / Zygist from everything working on the previous procedure using Magisk 23 right now.

Back up your HideMyAppList settings through the app.
Remove HMA, LSposed-Riru, and Riru plugins from Magisk 23 and reboot.
Install the updated Magisk Manager 24.1 and direct install Magisk 24.1 using the app.
Install LSposed - Zygist rather than LSposed Riru.
Install HideMyAppList again, and install the Zygist plugin from the app, rather than the Riru plugin.
Import your saved settings in the HMA app.
Install Magisk SafetyNetFix 2.21 if needed.
Reboot. If it bootloops clear cache and dalvik. Mine didn't but it did the last time I followed the procedure listed a few times back for Magisk 23+Riru+LSposted+HMA.
...Profit?

This is on Android 11/Lineage 18.1 but should work on Android 12 as well. There is no longer a need to use the canary build of Magisk as 24.1 has gone official. It should bring proper support for Android 12. Unfortunately the built in repo is gone (no big loss if you can find your own plugins. The biggest lost is magisk hide, which is why I included the SafetyNetFix step. I haven't had a change to see why zygist supported root hiders are out there, which the magisk dev acknowledges in his change log are actually working better than his built in implementation. Obviously he didn't want to name names.

Development on HMA has stopped as well unless you compile it yourself. The author's successor to HMA is coming, but it is still in development at the moment.

Cheers guys.

Edit: Android Auto is working fine using the procedure above to upgrade to Magisk 24.1 from 23 on Android 11/Lineage 18.1

 

[wyt18]

Root or non-root? Did you re-enable the accessibility service?

Just working on a procedure for running everything / upgrading to Magisk24.1 / Zygist from everything working on the previous procedure using Magisk 23 right now.

Back up your HideMyAppList settings through the app.
Remove HMA, LSposed-Riru, and Riru plugins from Magisk 23 and reboot.
Install the updated Magisk Manager 24.1 and direct install Magisk 24.1 using the app.
Install LSposed - Zygist rather than LSposed Riru.
Install HideMyAppList again, and install the Zygist plugin from the app, rather than the Riru plugin.
Import your saved settings in the HMA app.
Install Magisk SafetyNetFix 2.21 if needed.
Reboot. If it bootloops clear cache and dalvik. Mine didn't but it did the last time I followed the procedure listed a few times back for Magisk 23+Riru+LSposted+HMA.
...Profit?

This is on Android 11/Lineage 18.1 but should work on Android 12 as well. There is no longer a need to use the canary build of Magisk as 24.1 has gone official. It should bring proper support for Android 12. Unfortunately the built in repo is gone (no big loss if you can find your own plugins. The biggest lost is magisk hide, which is why I included the SafetyNetFix step. I haven't had a change to see why zygist supported root hiders are out there, which the magisk dev acknowledges in his change log are actually working better than his built in implementation. Obviously he didn't want to name names.

Development on HMA has stopped as well unless you compile it yourself. The author's successor to HMA is coming, but it is still in development at the moment.

Cheers guys.

Edit: Snow storm outside. I will go test Android Auto later, but there is no reason it shouldn't work. Were just using Zygist now instead of hooking the system calls in using Riru.

Edit2: Samsung Pay for my Galaxy watch is unhappy that it sees the system modified now that Magisk Hide is gone, but due to the limited support it doesn't work with any of my card issuers anyway, so no real loss.

what version of Lsposed are you using? I am on 1.6.5 (6272) and it keeps asking me to update but there's no beta update, only alpha

 

[zgfg]

what version of Lsposed are you using? I am on 1.6.5 (6272) and it keeps asking me to update but there's no beta update, only alpha

Ignore. I'm on 1.6.5 (6327). Once you install your LSPosed modules like HMA, you don't need to open LSPosed anymore, hence you don't see it asking for update that fails then

 

[SOFO888]

@HeStauss

Please let us know if your device is rooted.
Which Screen2Auto version do you use?

 

[mik101]

what version of Lsposed are you using? I am on 1.6.5 (6272) and it keeps asking me to update but there's no beta update, only alpha

LSPosed-v1.6.5-6320-zygisk-release.zip

 

[HeStauss]

@HeStauss

Please let us know if your device is rooted.
Which Screen2Auto version do you use?

Hello! My device (Samsung A52) is non rooted, Screen2auto is version 3.6.2. The accessibility service and/or the alternative touch option in Screen2auto needs to be established/reactivated for every new connection to the head unit to have the touch screen working also. Attachment to head unit (e.g. car navigation system FORD Sync3) ist done via cable connection (USB-C).
Installation of Screen2auto-app is done by AAEase V0.4. Same configuration worked well on Android 11 (non rooted), and right after factory-update to Android 12 Screen2auto crashed at every startup. After update to AA V7.2.620124-release-72620124_minAPI23(arm64-v8a) Screen2auto started correctly and mirrored the phone-screen to the head unit.

 

[SOFO888]

Thank you very much.
With Android Auto 7.1 I did not have luck. I guess I will try your version as soon as I have to update.

Thanks again. This is really helpful.

 

[mik101]

Hello! Screen2auto works (again) on Android12 (Samsung A52) right after updating with

Android Auto 7.2.620124-release (arm64-v8a) (Android 6.0+)​

, except touchscreen functionality.
(see also Chat "Fermata Media Player - audio and video player for Android Auto", #754)

That build doesn't work for me on lineage 18.1/Android 11. Back to 7.0/6.9.

 

[mik101]

Ignore. I'm on 1.6.5 (6327). Once you install your LSPosed modules like HMA, you don't need to open LSPosed anymore, hence you don't see it asking for update that fails then

Removing it after installing HMA causes a bootloop on Lineage 18.1/Android 11 on a whyred with Magisk24.1+zygist. So I'd recommend not doing that. Trying to recover my phone now...

Edit: Fixed using the magisk recovery mod found here from the terminal in TWRP. Disable all plugins from terminal to break the bootloop, reinstall LSposed-Zygist, then enable all modules again and reboot one more time.

[2019.4.4] Magisk Manager for Recovery Mode (mm)

# Magisk Manager for Recovery Mode (mm) ## LEGAL Copyright (C) 2017-2019, VR25 @ xda-developers This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the...

forum.xda-developers.com

So the lesson is, no, do not uninstall LSposed-zygist after installing HMA.

 

[SOFO888]

Did anyone else have luck with Android Auto 7.2?

 

[zgfg]

Removing it after installing HMA causes a bootloop on Lineage 18.1/Android 11 on a whyred with Magisk24.1+zygist. So I'd recommend not doing that. Trying to recover my phone now...

Edit: Fixed using the magisk recovery mod found here from the terminal in TWRP. Disable all plugins from terminal to break the bootloop, reinstall LSposed-Zygist, then enable all modules again and reboot one more time.

[2019.4.4] Magisk Manager for Recovery Mode (mm)

# Magisk Manager for Recovery Mode (mm) ## LEGAL Copyright (C) 2017-2019, VR25 @ xda-developers This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the...

forum.xda-developers.com

So the lesson is, no, do not uninstall LSposed-zygist after installing HMA.

You should not uninstall LSPosed as Magisk module - just to uninstall LSposed as apk (it will still show as LSPosed module installed)

Only if the issues you had are specific to LOS (and on your phone) - on Xiaomi, with A11, MIUI 12.5, there are no problems with uninstalling LSPosed apk, and I know several other users (Magisk general thread, Magisk TG channels, who do the same with no issues)

 

[mik101]

You should not uninstall LSPosed as Magisk module - just to uninstall LSposed as apk (it will still show as LSPosed module installed)

Only if the issues you had are specific to LOS (and on your phone) - on Xiaomi, with A11, MIUI 12.5, there are no problems with uninstalling LSPosed apk, and I know several other users (Magisk general thread, Magisk TG channels, who do the same with no issues)

Doesn't appear to have been installed as an APK in my device in the first place. I only see the magisk module. That's where the confusion came from then.

 

[drexd]

Hello! My device (Samsung A52) is non rooted, Screen2auto is version 3.6.2. The accessibility service and/or the alternative touch option in Screen2auto needs to be established/reactivated for every new connection to the head unit to have the touch screen working also. Attachment to head unit (e.g. car navigation system FORD Sync3) ist done via cable connection (USB-C).
Installation of Screen2auto-app is done by AAEase V0.4. Same configuration worked well on Android 11 (non rooted), and right after factory-update to Android 12 Screen2auto crashed at every startup. After update to AA V7.2.620124-release-72620124_minAPI23(arm64-v8a) Screen2auto started correctly and mirrored the phone-screen to the head unit.

This worked for me zf3 android 12 aaad and no root.

I can see the s2a apps and Taskbar and launch them but they all show a black screen and have to reboot the MMI head unit to rediisplay. I am so close now. Any ideas why apps go black? I am trying to run JBV1

 

[drexd]

This worked for me zf3 android 12 aaad and no root.

I can see the s2a apps and Taskbar and launch them but they all show a black screen and have to reboot the MMI head unit to rediisplay. I am so close now. Any ideas why apps go black? I am trying to run JBV1

Its working now.

The only issue I have which was causing the blank screen was that each app that was launched caused the dialogue below. I have installed and uninstalled [email protected] many times, and I am sure I granted the permission to start recoding or casting with screen2auto. Now, I keep getting that approval to launch the app. How can I best fix this permanently. ie How can I set this permission permanently??

Otherwise, its working flawlessly

 

[HeStauss]

Its working now.

The only issue I have which was causing the blank screen was that each app that was launched caused the dialogue below. I have installed and uninstalled [email protected] many times, and I am sure I granted the permission to start recoding or casting with screen2auto. Now, I keep getting that approval to launch the app. How can I best fix this permanently. ie How can I set this permission permanently??

Otherwise, its working flawlessly

For a permanently granted permission follow post # 1399 (page 70):
"...you are granting this app permission to start screen recording without prompting. No root required.

adb shell appops set ru.inceptive.screentwoauto PROJECT_MEDIA allow ..."