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

[SOFO888]

@tiho5
It's version 7.0.113904.

@tensux

Try to delete AA data and cache. Moreover check AIO tool. Or if you use AAWireless, check the companion app. But in fact, there are many possibilities to change the DPI.

 

[tensux]

That did it thanks. I had uninstalled the tool but I reinstalled it and played around with the settings and it's working now

 

[tiho5]

Or if you use AAWireless, check the companion ap

What companion app is that?

 

[SOFO888]

AAWireless setup app:

AAWireless - Android Auto - Apps on Google Play

Companion app for AAWireless

play.google.com

 

[mik101]

This should work fine. For those that don't want to use lucky patcher and king installer, just use AAAD to install Screen2Auto as it changes the package name automatically anyway. AAEase does as well. At least now S2A shows up in the AA app list again. As long as AA doesn't detect that there is an update available it should be good to go. I'll report back when the wife gets home with our other car.

My issue was Google forcing the update upon me when AA launched, like others were having.

Testing on a Whyred with this weeks lineage 18.1. I should have a PocoF3 to test on any day now as well. I also have a Carsifi on order so that we can try to test this over wireless AA using that dongle, as well as the AAWireless dongle mentioned above.

Edit: AAEase confirmed by tiho5.
Edit 2: I tried the latest available from the playstore for me (7.1.614574) and that was a no go to even have Screen2Auto show up in my app list. I will verify 6.9 later on tonight (it should be working since S2A shows up in my app list). Then I will give the 7.0 build that someone mentioned above, a try.

Cheers guys and thanks to Luiscaproducer for posting the step by step quoted below.

Screen2Auto and Fermata Auto for Android 12

Dear all, I managed to have S2A working again on Android 12...I'd like to let everyone know that I am NOT a developer and I'm just reporting here the steps that worked for me.

ROOT REQUIRED

- Uninstall any previous installed AA version (Except the factory one, if available) and install the AA 6.9.613744
- Enable 3rd party and developer mode on AA again
- Download and install (no need to open it) the latest version of Screen2Auto, Use Lucky Patcher to clone the app and save the cloned app somewhere in your device.
- Uninstall S2A
- Download and install KingInstaller 1.2 (Find Attached)
- Use KingInstaller to install the cloned version of S2A previously saved
- Use AA AIO Tweaker app to patch the app. Reboot.
- Open S2A and give all permissions.
- Use HideMyApplist to detach Google Play store to update the AA app (If you're running Magisk Canary Release download the Zygisk - LSPosed module to make HMA work). Create a Blacklist template in HideMyApplist and you select the Android Auto app, click on save. (top right icon). Always on HMA Go to "Select Effective Apps" and look for google play store and tap on it, enable the following "Enable Hide", "Enable all hide methods" applied the blacklist template. Save (top right icon).
- DONE!

Use the same process for Fermata Auto if you're interested. I don't really know if all these steps are needed to make it work but I would recommend to "stick to the plan".

PLEASE GIVE FEEDBACK IN ORDER TO CONFIRM THE FLOW.

Cheersss

 

[tiho5]

I believe AAEase does as well, but someone else will have to confirm that.

Yes it does.

 

[mik101]

AA 6.9.613744 does work when unlinked from the play store, but even though it doesn't force you to update, it does know its an old version and sets this notification shown here.



It is still better than forcing you to update and making S2A not work at all -- at least for now.

Edit: 7.0.614174 is still working fine as well, as does not set the notification that 6.9.613744 sets above.

Edit 2: 6.9 seems a little more stable on my phone than 7.0 does. But both do work once disconnected from market. If you do not disconnect it, they will all force you to update to 7.1 before working (and thus break S2A).

 

[Roland303]

Hello, what am I doing wrong? If I install the older AA version and block it according to the instructions, my Samsung Galaxy S10+ with Android 12 no longer connects. The latest version of AA must always be on it first, only then screen2Auto no longer works. It only shows a black screen for a short time and closes immediately.

 

[mik101]

Hello, what am I doing wrong? If I install the older AA version and block it according to the instructions, my Samsung Galaxy S10+ with Android 12 no longer connects. The latest version of AA must always be on it first, only then screen2Auto no longer works. It only shows a black screen for a short time and closes immediately.

Did you completely remove all AA updates and clear the storage for the AA app before installing a working version? Mine was keeping data for the built in version even when updates were uninstalled.
There are a few more reboots required than the original instructions (ie have the canary version of magisk installed for A12, Riru, lsposed and hide my applist. I had to reboot after installing each of those modules even on A11). Where I'm on A11, I was able to use the official Magisk 23. It did take some trial and error to get working properly in the end.

If you don't have root using the canary version of magisk for A12 im not 100% S2A will work on there at all. I don't have a device here with A12 on it to test at the moment. Sorry.

 

[SOFO888]

Is there also a possibility to detach Android Auto with LuckyPatcher?

LuckyPatcher does not need root.

 

[mik101]

Is there also a possibility to detach Android Auto with LuckyPatcher?

LuckyPatcher does not need root.

Luckypatcher does require root for some functions as far as I can remember. I haven't used it in a few years.
If a lower version of the AA APK or even just a stub (so play store sees it and installs AA when the apps are first updated after a fresh install) is in your system partition and you don't have root, then no you probably cant. Titanium Backup used to work for detaching, but again, root was required. (That is what I used to detach apps in earlier versions of Android on my Z2, but sometimes they would still reappear in the Play Store after a reboot).

If there is no stub for the AA apk in your system partition, you MIGHT be able to change the package name and/or resign it with your own key. This is essentially what the non-root version of YouTubeVanced does by using a different package name.
I don't know if vehicles will even launch AA if it isn't signed with Google's key or the package name is changed though.
For example: Lets look at Google Assistant support with Vanced. If you try to voice control the non-root version, GA will tell you that you don't have YT/YT music installed. If you have the root versions of Vanced, then Google Assistant will work fine, because the APKs have the package names that Google Assistant expects them to have. So as far as it knows, you have legit versions of the apps installed.

Where AA doesn't even have it's own icon in the app drawer anymore and is accessed through the settings menu, it is possible you wont even see it in there if the package name is changed. (This is speculation on my part as I have never had a reason to try that).

I would guess that without S2A being updated to support current versions of AA again without all of this screwing around, non-root users that don't still have it working are probably out of luck for now, and possibly in the not too distant future, we may all be. It seems that Google REALLY doesn't want unauthorized apps working with Android Auto, especially screen mirroring apps.

Edit: Expanded on some thoughts and fixed up some legibility issues.

 

[mik101]

If you bootloop on an OTA update (like mine just did on todays release of Lineage 18.1), force a reboot into recovery, clear cache and dalvik, and reboot again. The phone will then boot but I ended up with Lsposed being partially activated after that reboot. It says SeLinux policy not loaded properly, so the Magisk recovery script didn't run properly when the OTA update installed. Go into your Magisk app and reinstall Magisk and reboot. Then all should be well again. (I'm guessing this had something to do with Riru/Lsposed/HideMyAppList as I didn't have any of that stuff installed before any prior updates.)

 

[SOFO888]

I tried AA with s changed package name and resigned key. On the phone AA starts.
In the car: the car does not even recognize that AA is installed and you can't start AA.

 

[tensux]

Titanium Backup used to work for detaching, but again, root was required. (That is what I used to detach apps in earlier versions of Android on my Z2, but sometimes they would still reappear in the Play Store after a reboot).

Screen2auto will work for me with AA 6.96 on a pixel 6 running android 12 for about a day. then without updating anything it will stop working the next day. I need to reinstall AA and repatch to get it to work again. are you saying you can use titanium back up to solve this?

 

[Anton_Chigurh]

Screen2auto will work for me with AA 6.96 on a pixel 6 running android 12 for about a day. then without updating anything it will stop working the next day. I need to reinstall AA and repatch to get it to work again. are you saying you can use titanium back up to solve this?

Clear cache and data of AA. You must to do this everytime before you reconnect.

 

[mik101]

You can try with Titanium Backup Pro to detach AA from market to see if it still gives you problems. I'm not even sure if that function in TB will work still in A12. I haven't used that method to detach since Oreo though. This will require root.

The confirmed working method using the alpha/canary version of Magisk for A12 along with Riru+Lsposed+HideMyAppList that has already been posted previously in the thread requires root as well. This is the method I'm using on A11. (With the exception of using Magisk 23 official release instead of the canary alpha version that is needed to make it work with Android 12).

 

[mik101]

Clear cache and data of AA. You must to do this everytime before you reconnect.

For some reason that isn't happening for me, yet. AA 7.0 does need a retry once in a while on my 21 Corolla though.

 

[tensux]

You can try with Titanium Backup Pro to detach AA from market to see if it still gives you problems. I'm not even sure if that function in TB will work still in A12. I haven't used that method to detach since Oreo though. This will require root.

The confirmed working method using the alpha/canary version of Magisk for A12 along with Riru+Lsposed+HideMyAppList that has already been posted previously in the thread requires root as well. This is the method I'm using on A11. (With the exception of using Magisk 23 official release instead of the canary alpha version that is needed to make it work with Android 12).

Can you clarify what you mean by "stops working"? Is it complaining you need to update, or will it just not load?

what happens is it disappears from the android auto screen.

 

[Anton_Chigurh]

For some reason that isn't happening for me, yet. AA 7.0 does need a retry once in a while on my 21 Corolla though.

Use AA ver. 6.9. 613744.

 

[mik101]

Use AA ver. 6.9. 613744.

Already covered that in my previous post (#2047). It will likely stop working soon. I've been switching back and forth between that version and 7.0.614174.

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

Smartphone screen on Anddroid Auto HU car screen For root devices only! Application features: - The main reason for creating this application is working with Android 9 Pie 1. Сompletely new application combining AAMirror & AAStream...

forum.xda-developers.com