Installed now again with AAEASE and it's working! I've denied root on the AAEASE to work and then gave root to S2Auto
thanks!
Screen2Auto - New app for AA smartphone mirroring (only for root devices).
- Thread starter Uksus17
- Start date
thanks!Not sure this helps but I have been using S2A for over a year with non rooted samsung note 9. Installed with AA Ease and works very well on wireless AA setup.Would someone be kind enough to post a draft of a guide, from a to z? SInce starting to use it for a rooted note9 to now, a lot has changed, the aio patcher doesnt work, so i cannot shrink the navbar, also s2a always works and then it doesn't and I would like to have my trusty road companion back with me.
Also, before being told, i saw that here are fragments of information here and there, but that generally end up in intermitent working s2a.
Thank you in advance !
Last edited:
For those like me, until recently, that always used the Launcher screen, noticed that it is not working on Android 13 (non rooted Samsung A52S). Launching an app using an icon on the launcher screen crashes screen2auto (only viber was still working). But if "Open on start" launcher screen is disabled, the screen mirroring, and all apps are functioning properly!
It works on 9.1 and every released version, your phone should be the issue, change it.
I don't know how to answer this question.i install aa 8.6 on android 11 phon,aa aio can't work on it,aaad worked,then update to 9.0,but on my old phone,s7edge,still not work for 3 months.
Updated my Pixel 6 Pro, non rooted, to AA version 9.0.630834-release a few days ago. Screen2Auto still working.
Try reinstall with AAEASE?
I know that this is maybe not the right thread to ask but I wonder if anybody saw the AA Communication error 22 when trying to establish the connection
I have two Xiaomi phones. On one (newer, A12) AA works flowlessly with SA and Fermata
On the other Xiaomi, older (A11, model from 2019), now I cannot even establish the AA connection anymore.
A year+ ago, when this was my main phone AA worked (same MIUI, also with SA and Fermata) but now AA pops that error telling that AA was not pre-installed on the phone
However, on both Xiaomi phones AndroidAuto Stub app was pre-installed as a stock app to /system/product/priv-app/AndroidAutoStub, and I had to use Google Play to install the latest version of AA app
On that newer phone there was no problem but on the older one this error now (a year ago, the older version of AA worked fine on the same phone and ROM was never upgraded or changed in the meantime)
I tried also a couple of older AA versions from APK mirror, like
v8.8.630404-release (same version works just fine on my newer Xiaomi) but on that older Xiaomi I always get the same error
Frankly, it's not crucial for me, I have AA working on the newer phone (with SA and Fermata), and this old phone (without SIM card, hence without Mobile Internet and therefore not really useful for AA) is just for testing...
I have two Xiaomi phones. On one (newer, A12) AA works flowlessly with SA and Fermata
On the other Xiaomi, older (A11, model from 2019), now I cannot even establish the AA connection anymore.
A year+ ago, when this was my main phone AA worked (same MIUI, also with SA and Fermata) but now AA pops that error telling that AA was not pre-installed on the phone
However, on both Xiaomi phones AndroidAuto Stub app was pre-installed as a stock app to /system/product/priv-app/AndroidAutoStub, and I had to use Google Play to install the latest version of AA app
On that newer phone there was no problem but on the older one this error now (a year ago, the older version of AA worked fine on the same phone and ROM was never upgraded or changed in the meantime)
I tried also a couple of older AA versions from APK mirror, like
v8.8.630404-release (same version works just fine on my newer Xiaomi) but on that older Xiaomi I always get the same error
Frankly, it's not crucial for me, I have AA working on the newer phone (with SA and Fermata), and this old phone (without SIM card, hence without Mobile Internet and therefore not really useful for AA) is just for testing...
Attachments
Last edited:
Just a stupid idea. Did you try with SIM inserted? Not much logic here, but one can expect everything from Google these days...
Actually, the yesterday's issue was resolved (now, one step ahead), it was my fault (AA Stub was [partially] debloated)
Now I pass that step but get another Communication error 17 - I think this one is really due to the lack of SIM card (I will no more pursue because I don't want to move the SIM card from one phone to another, I tried with WiFi tethering instead but it did not help)
Attachments
Let us know what happened. It's good to have issues reported here for the general knowledge.
Thanks. By giving the microphone permission to AA (I gave all kind of permissions, to make sure it won't be next time a new error xx), Comm error 17 was fixed and AA finally connected successfully (even without the SIM card and out of reach of the WLAN)
[That's what I wanted, to have AA (with SA and Fermata), like I have other apps and tweaks ready on that spare phone, just in case (once I bricked my main phone and having almost everything ready on the spare phone saved my ass - I was on vacation, I just moved SIM cards to the old/spare phone and in about half an hour I was able to continue with everything that I needed for the private and work use)]
It happened a similar thing to me. After an update S2A disapeared (rooted phone). I tried to install it again via AAAD or AAease and both apps crashed. I solved it using ApkRenamer from github. Follow the instructions and you'll be able to renme the package and then S2A will be shown again in AA.
Similar threads
Top Liked Posts
-
1
for it to show up in AA, direct install (sideloading) is not enough, it needs to be installed with a special flag to make it part of the Google Play Market.
You can use AAEase to do that, just use the install option further down.
There are other tools that can do that too. -
2
It happened a similar thing to me. After an update S2A disapeared (rooted phone). I tried to install it again via AAAD or AAease and both apps crashed. I solved it using ApkRenamer from github. Follow the instructions and you'll be able to renme the package and then S2A will be shown again in AA.2
Installed now again with AAEASE and it's working! I've denied root on the AAEASE to work and then gave root to S2Auto thanks!1
You must install s2a with a changed name. Some use king installer, some use AAAD, some use AAEASE. Google recognizes the app otherwise.11Would someone be kind enough to post a draft of a guide, from a to z? SInce starting to use it for a rooted note9 to now, a lot has changed, the aio patcher doesnt work, so i cannot shrink the navbar, also s2a always works and then it doesn't and I would like to have my trusty road companion back with me .
Also, before being told, i saw that here are fragments of information here and there, but that generally end up in intermitent working s2a.
Thank you in advance ! -
121Smartphone 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 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...
Installation and setup:
1. Download and Install Screen2Auto
2. Enable developper settings in Android Auto and enable Unkown sources in developper settings.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.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.
Don't forget to use the button (if you want course):
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 newPreview
Well, as usual, I will be glad your coffee
Download: ↓↓↓9Screen2Auto 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
9The 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
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 **):
