yashsingh1/xdaforums huggingface dataset:
[Android Auto General] SOFO888:
That is a generel Android Auto bug. Sometimes there are no notification sounds.

You can clear data and cache and hope that it will work next time.

I had the same issues with a lot of apps...
[Android Auto General] tiho5:
So it is working for you now? In that case, please tell me what version of AA are you using.
[Android Auto General] tensux:
any idea where I might have done that? I have tried everything. I uninstalled screen2auto, femeta and the like. I used root installer trying to uninstall android auto. I have updated to the newest android auto from the playstore and it is still showing spiltscreen. Afraid I will have to have to reset the phone.
[Android Auto General] 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.
[Android Auto General] 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
[Android Auto General] tiho5:
What companion app is that?
[Android Auto General] SOFO888:
AAWireless setup app:

AAWireless for Android Auto™ - Apps on Google Play

Companion app for AAWireless, check https://aawireless.io for more information.

play.google.com
[Android Auto General] 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.
[Android Auto General] tiho5:
Yes it does.
[Android Auto General] 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).
[Android Auto General] 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.
[Android Auto General] mik101:
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.
[Android Auto General] SOFO888:
Is there also a possibility to detach Android Auto with LuckyPatcher?

LuckyPatcher does not need root.
[Android Auto General] mik101:
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.
[Android Auto General] 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.)
[Android Auto General] 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.
[Android Auto General] tensux:
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?
[Android Auto General] Anton_Chigurh:
Clear cache and data of AA. You must to do this everytime before you reconnect.
[Android Auto General] 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).
[Android Auto General] mik101:
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.
[Android Auto General] tensux:
what happens is it disappears from the android auto screen.
[Android Auto General] Anton_Chigurh:
Use AA ver. 6.9. 613744.
[Android Auto General] mik101:
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.

https://xdaforums.com/t/screen2auto...g-only-for-root-devices.4062787/post-86307955
[Android Auto General] tiho5:
Wee may need modded Android auto version. One that doesn't check for update internally.
[Android Auto General] 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?
[Android Auto General] 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?
[Android Auto General] 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://xdaforums.com/t/screen2auto...g-only-for-root-devices.4062787/post-86244997

With Android 12 it became really hard to use 3rd party apps on Android Auto.
[Android Auto General] 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)
[Android Auto General] mik101:
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
[Android Auto General] wyt18:
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
[Android Auto General] zgfg:
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
[Android Auto General] SOFO888:
@HeStauss

Please let us know if your device is rooted.

Which Screen2Auto version do you use?
[Android Auto General] mik101:
LSPosed-v1.6.5-6320-zygisk-release.zip
[Android Auto General] HeStauss:
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.
[Android Auto General] 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.
[Android Auto General] mik101:
That build doesn't work for me on lineage 18.1/Android 11. Back to 7.0/6.9.
[Android Auto General] mik101:
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.

https://xdaforums.com/t/2019-4-4-magisk-manager-for-recovery-mode-mm.3693165/#post-74261456

So the lesson is, no, do not uninstall LSposed-zygist after installing HMA.
[Android Auto General] SOFO888:
Did anyone else have luck with Android Auto 7.2?
[Android Auto General] zgfg:
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)
[Android Auto General] mik101:
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.
[Android Auto General] 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
[Android Auto General] drexd:
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 S@A 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
[Android Auto General] HeStauss:
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 ..."
[Android Auto General] BrianRC:
Yes.

I'm on a rooted Pixel 6 with Android 12 and Majisk 24.1. I've only had the phone about a week.

I was reading this article last night that led me to try AA 7.2 https://www.autoevolution.com/news/android-auto-72-likely-fixing-a-major-android-12-bug-178671.html . I downloading the following apk which is the correct one for my system https://www.apkmirror.com/apk/googl...620103-release-android-apk-download/download/.

Following instructions elsewhere, I installed S2A 3.6.2 with KingInstaller 2.1. Then I tweaked it with AA AIO Tweaker 5.01. Then I started S2A and granted all permissions requested. Then I booted up AA on my car and S2A did not appear on the screen. Now this is the critical part that made it work. I enabled devloper mode in AA 7.2 and then in devloper settings I set Application Mode to Developer and selected Unknown Sources. Then S2A appears on my AA screen and I just enjoyed watching some YouTube videos on my way to the gym. Yeah!

Having said that, when I left the gym just now S2A did not appear on my screen, so I still have some work to do. I read above someone said you have to clear cache on AA everytime before use so I will give that a try. But I consider this progress.

Hopefully other Android 12/Pixel 6 owners will give it a try and we'll soon have this figured out.
[Android Auto General] SOFO888:
Hello to everyone,

I wanted to test Screen2Auto on my old phone.

It is a Motorola Moto G5 on Android 8.1 with Android Auto 6.8.

It's crazy...I used the same apk like on my daily phone. Unfortunately Screen2Auto does not appear. Even with deleting cache and data of Google Play Services and Android Auto.

After about one hour or so, Google auto-updated Android Auto to 7.1 (even though auto updates are turned off).

I reinstalled Android Auto 6.8, deleted cache and data. However Screen2Auto does not appear.

I really do not understand why it works on my daily phone, but not on my old phone.

I just wanted to use this phone for some testing.
[Android Auto General] mik101:
It's working fine now for me on Lineage 18.1/Android 11 on a whyred with the new version of AIO patcher (5.0.1). The changelog says that the patching procedure has been updated to support newer versions of Android Auto.
[Android Auto General] Medicina200401:
Hello. The first time S2auto is run it takes a few seconds to project the screen. Then the operation is very smooth. But when a time passes without being used again, it takes time to project the screen again. (my phone is permanently in the car) Is there a way to always leave S2auto in memory so that it projects faster the first time it is executed? (S2auto is not optimized for battery saving) Thanks a lot Alexander
[Android Auto General] mik101:
Likely blacklisted the package name. Use Kinginstaller, AAEase or one of the numerous installers mentioned in this thread to install it with a different package name. It will likely work again. If playstore is forcing the 7.1 update regardless, you'll probably have to install it and then detach the APK from the store to keep it from forcing the update as many of us have in the previous pages.
[Android Auto General] mik101:
Try pinning the app in the task switcher if your android build/skin supports that feature.
[Android Auto General] SOFO888:
@mik101

I tried all 3 install methods. Nothing worked.

On my daily phone it was no problem.

Both phones are not rooted. Therefore I can't unlink the apps from the Playstore.
[Android Auto General] mik101:
That's strange. I wonder if google is changing things through the play services app then. I don't have anything non-root here to test.
[Android Auto General] SOFO888:
Yes, it is strange.

And yes, Google also forces Play Services updates. And one of the updates killed Screen2Auto about 2 months ago. When uninstalling the Play Services update, everything was ok.

After the next update of Screen2Auto everything was fine again.

I wonder if Motorola has some kind of modification/software for so called "user safety" which leads to this situation.

Perhaps this is the reason why there are some phones with which people could not get Screen2Auto to run.
[Android Auto General] mapobean:
Hopefully this helps somebody but today I noticed that if my dimmer was all the way down in my truck it would put my radio would change to night mode and I had no way to access screen2Auto or anything in there bottom
[Android Auto General] mik101:
Mine just disappeared too when I got in the car a few minutes ago. So I went back into android autos list configuration on the phone, and sure enough it doesn't show up in the list again after working fine for days. :mad: Edit: Cleared data on AA and repatched and it returns. I wish Google would realize they're not the ones liable if we're playing with our phones while driving...
[Android Auto General] SOFO888:
Did you check if there was an auto update of Android Auto or Google Play Services?
[Android Auto General] mik101:
Play services hasn't updated since December, and the AA build is still AA V7.2.620124-release-72620124_minAPI23(arm64-v8a). The latter is detached from playstore and won't update automatically. I'll try it again on the car in the morning. If it keeps acting up I'll just go back to 6.9/7.0. I was just hoping 7.2 would work reliably since my new PocoF3 will be getting MIUI 13/Android 12 once the bootloader countdown finishes in a couple days. In the meantime I'm still using my Redmi Note 5 Pro (Whyred) running Lineage 18.1/Android 11. Also still waiting for my Carsifi adapter to ship. I wish they would just ship them without the USB cables that their contracted factory messed up.
[Android Auto General] SOFO888:
Did you try to reinstall Android Auto 7.2.6?
[Android Auto General] mik101:
Yeah it worked fine today after clearing cache and repatching with AIO patcher 5.0.1. I'm not sure what the problem yesterday was about.

Edit: Typo
[Android Auto General] wyt18:
Is there a 5.0.2? Latest on github is 5.0.1
[Android Auto General] mik101:
Typo 5.0.1
[Android Auto General] SOFO888:
As Android Auto 7.3 is already available...did someone test this version?
[Android Auto General] Tomasz_RS:
Yes, everything works fine for me. Screen2auto, Carstream, Fermata Auto
[Android Auto General] robi101012981:
So basically I can just upgrade it from the December version and it'll work, no?
[Android Auto General] perindet:
in andorid 12 or 11?
[Android Auto General] robi101012981:
a12. solved it by just upgrading the android auto app, thanks :)
[Android Auto General] reini1982:
Screen2Auto is still working great for me!

a) installed Screen2Auto with Kinginstaller

b) patched Android Auto and Screen2Auto with AOI Tweaker 5.01

Setup:

rooted Xiaomi Redmi 10 (Miui 12.5.9, Android 11)

Magisk 24.1

Screen2Auto 3.62

Android Auto 7.2.620124

using Screen2Auto in my Skoda Octavia (Bolero Radio)
[Android Auto General] Holzi224:
I got another new problem here:

My Android auto somehow updated even though it's detached from the Playstore and now I have that new multi-screen.

1st problem is: every way of installing s2a again didn't work for me and if it works for a few minutes s2a only shows up on the left side of the multiscreen, not on the entire one.

I can't even deactivate the multi-screen with the AA AIO Tweaker, did anybody have similar problems?

Might just change back to one of the older working versions I guess
[Android Auto General] dead4ngel:
Hi. Are you able to use Amazon prime video and Netflix and do they display properly or do you just have a black screen?
[Android Auto General] aringler:
For me it's the same. But still having a black screen while playing Netflix.
[Android Auto General] SOFO888:
Due to DRM reasons it is not possible any more to use Netflix.
[Android Auto General] gullzway:
It is. You need to download Netflix apk

version 7.99.0 build 14 35427

from April 2021

Works for me. I'm on Android 10, not sure if that matters.
[Android Auto General] drnightshadow:
Why no one is using firewalls and block all googleCr@pware to access net? 🤔 No access to net no update, problem solved... I'm still on AA 6.9 and all fine no update is forced to me. 😎

Simple solution even for non-rooted devices. You could use app like netguard - it's using VPN. For update I'm using AuroraStore.