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

Search This thread

HeStauss

New member
Jan 28, 2022
3
3
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)
 
  • Like
Reactions: SOFO888

mik101

Senior Member
Jul 13, 2010
707
140
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
 
Last edited:

wyt18

Senior Member
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

Senior Member
Oct 10, 2016
7,191
4,641
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
 

HeStauss

New member
Jan 28, 2022
3
3
@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.
 
Last edited:
  • Like
Reactions: mik101 and SOFO888

SOFO888

Senior Member
Jan 28, 2013
254
41
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

Senior Member
Jul 13, 2010
707
140
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

Senior Member
Jul 13, 2010
707
140
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.


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

zgfg

Senior Member
Oct 10, 2016
7,191
4,641
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.


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

Senior Member
Jul 13, 2010
707
140
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

Member
Nov 23, 2013
22
4
Spacecoast
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

Member
Nov 23, 2013
22
4
Spacecoast
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
 

Attachments

  • casting.png
    casting.png
    36.4 KB · Views: 36

HeStauss

New member
Jan 28, 2022
3
3
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 ..."
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Which Android version?

    Are you saying that you didn't use AIO Tweaker?
    Android 12. No AIO Tweaker.
  • 106
    Smartphone screen on Anddroid Auto HU car screen
    For root devices only!

    a65be9f97d8097a3eeccdacfbe7ac48d.png

    b8add53a049c33be76f7e3778db2551c.png



    c1b9abbde2a1f4e7a6920f3b7bd1ffe2.png



    Application features:
    - The main reason for creating this application is working with Android 9 Pie
    1. Сompletely new application combining AAMirror & AAStream features.
    2. Additional functions: clock, dimming, selection of resolutions, etc.
    3. Ability to choose the automatic launch of any application at A2M startup.
    4. Floating button to control the application from the HU screen.
    5. Ability to reset if incorrect output and resolution distortion.
    6. Many other chips...
    1d1ca5ad04e260cb8dfa7360d36cee00.png

    Installation and setup:
    1. Download and Install Screen2Auto
    6760829d5c83bfb472ea0a96d8b0efde.png
    2. Enable developper settings in Android Auto and enable Unkown sources in developper settings.
    1. Launch on the Android Auto mobile device
    2. Open the menu, tap the tab "About Android Auto"
    3. In the menu that opens, tap on the gear (settings). Then we crawl to the very bottom of the menu that opens: "Version 4.5. *** - release".
    4. 10 times tap on the display of the version of Android Auto, a window will appear where we must agree with what we are doing. Click "Yes."
    5. Go to the menu (tap "three points") and select the tab "For Developers" that appears in the menu
    6. In the last line, put a checkmark "Unknown sources" or use other settings of the developer's menu.
    3. Use the AA AIO TWEAKER from @shmykelsa for activation third-party applications.
    4. Launch the application and perform the initial setup of permission recovery. Click on the button and save them.
    1ae13868aa9142dd0ea19722b818d9a7.jpg
    5. Make the necessary settings as desired.
    Warning:
    If, after turning off the smartphone or exiting AA (turned off the car, closed the emulator, removed the USB), the resolution of the smartphone did not return to its original state (the recovery settings, failure, smartphone features, etc. were set incorrectly, etc.), you need go to Settings → Reset settings and select the WM SIZE RESET option. Resolution will be restored to factory.
    3e5e464d111050be0db4f57505492313.png
    0222f487a017f62a6242d37d27e82b3a.png

    Don't forget to use the button (if you want course):
    cb294618ab788427637345c9f1030b77.png


    Warning! New version of the application released!
    Thanks to everyone who offered delicious coffee!
    All of this thanks to all caring people.



    Attention!
    You can download and install S2A on devices without root using the new application
    Android Auto Apps Downloader (AAAD)
    However, I still recommend using C2A on rooted devices.

    What's new

    v3.5.2beta
    • Bug fixes

    v3.5beta
    • Adapted for Non Root devices
    • Notification when pause (for automation).
    • Bug fixes
    • Languages update

    v3.4.6
    • Added persistent quick launch bar
    • Added a pause S2A. If need to use the phone (so as not to disconnect)
    • Fixed bug with floating button
    • Fixed bug with choosing launcher button and background
    • Minor fixes

    v3.4.5
    • Added the ability to change the icon of the floating button
    • Added autostart mapcam.info
    • Added starting Tasker task after completion
    • Minor fixes

    v3.4
    • Fixed jambs
    • Added Support for Screen2Echo*
    • *Screen2Echo - application idesigned to link two phones. An application for those who do not want to get root on their main phone, and the second one is always in the car . Screen2Auto and S2Echo communicate via WiFi Hotspot.
    • Added Function to enable Hotspot at phone startup

    v3.3
    • Bug fixes
    • Switch "Do not restore" in the settings
    • Fixes for some jambs version 3.2

    v3.1
    • Bug fixes
    • Fix launch on Android 5&6
    • Fix Netflix (be sure to enable accessibility)
    • Adjustment of language packs
    • Added new translations

    v3.0
    • Application optimization
    • Made initial setting (Wizard settings)
    • Updated language files. (Thanks for the translations)
    • Added driving safety warning

    32a6ff91f00801a90056ed0b6dc27241.png

    837e9dacbe128637ed1dcd820e3b0a00.png
    Preview

    29f8f3095dcb6e0f7c50945273cd8846.jpg

    74a842327d62fc08ff4094db75c5cf05.jpg

    d3ca794b3557868d6b0c5d0f1cb47726.jpg

    f12617d47c0d7ba10b38071596beea04.jpg

    2e7d1fd6cfc6285f47cb63c875f37344.jpg

    b3b5fbe231fd9037188cc9995ea7cea3.jpg

    e6cb6d066052a58c27c5fa40755c4a7b.jpg

    472ed615393e079d2cf3b0180ceb8bc5.jpg

    5798b314178fd956947295e55eac32c1.jpg

    Well, as usual, I will be glad your coffee
    8ba7613826381811e8ab595c18c11459.jpg
    Download: ↓↓↓
    10
    A new version 3.4.6 has been released

    • Added persistent quick launch bar
    • Added a pause S2A. If need to use the phone (so as not to disconnect)
    • Fixed bug with floating button
    • Fixed bug with choosing launcher button and background
    • Minor fixes
    9
    Screen2Auto upgrade to v2.8!
    • Work optimization
    • (Delete) Removed the speedometer.
    • (Add) Added switch to enable / disable the function of forced application termination
    • (Add) Added to the launcher the HOME and WORK buttons from the Yandex navigator.
    • (Add) Added Polish language (thanks wal24)
    • (Add) Launching scree2auto task from Tasker
    • (Fix) Fixed launch from the application menu
    9
    The only way (similar method from the Fermata player thread) I found to overcome the problem for now is:
    - Use Android Auto version 7.0.614104 (tried v7.1.614554, it does not work in any way).
    - Rename the Screen2Auto app v3.6.2 (change the ru.inceptive.screentwoauto name) with Lucky Patcher or any other rename apk app.
    - Uninstall the original Screen2Auto and install the renamed one.
    - Enable Unknown Sources on AA and patch/add the newly renamed app to AA with AA IO Tweaker as you normally would.

    I tried turning off/on the car, disconnected and rebooted the phone, Screen2Auto hasn't disappeared yet.
    6
    hello how do you rename the apk with lucky patcher ... i'm interested thank you
    Lucky Patcher actually calls it "Cloning".
    There are also other apps like ApkRenamer and Apk Editor Pro, but haven't tried them.
    An example of cloned app, that has been renamed to ru.inceptive.screentwoautp using Lucky PAtcher clone operation ("p" instead of "o" at the end) (** I'm not responsible if Lucky Patcher has injected anything malicious in the apk, I hope not, I'm also using the apk **):