yashsingh1/xdaforums huggingface dataset:
[Android Auto General] lukccp:
Hi.

First of all thanks guys for all this...

I read last 10 pages, but I'm still not able to get S2A in my AA.

First of all, I'm still not sure if all this should work on non-rooted devices?

If not, than all my other questions are non-sense. :)

I'm using Pixel 7Pro, A14, AA version 10.7.634234, as I said, no root.

If root isn't mandatory, than I have few questions, after I tried to follow all 5 steps.

1. Dev mode + unknown sources ->OK

2. KingInstaller installed, but I don't know what means "Apps need to be "installed as Google Play"

Do I just select .apk and hit "Install as king"?

3. Apps need to be "whitelisted in phenotype.db"

This step shuld be done inside AA-AIO-Tweaker app? Or do I just need to install this app?

Because when I installed AA-AIO and open it I get "Root access denied"

So this is the end for me, because I'm not rooted?

------- If only installed AA-AIO is needed I start with next step-------

4. As I see, before installing Android-Auto-XLauncher-Unlocked I have to do this:

Install Magisk

Magisk => Settings => Magisk => Check Zygisk

Install LSPosed (Zygisk) + Shamiko

Install the Android-Auto-XLauncher-Unlocked app with KingInstaller

LSPosed => Modules => Check Enable module + Check Android Auto

Reboot

I installed Magisk and I get this screen:

Screenshot-20231115-215451 hosted at ImgBB

Image Screenshot-20231115-215451 hosted in ImgBB

ibb.co

What should I do to get to 2nd step->Magisk => Settings => Magisk => Check Zygisk

I don't see this option at all.

I already downloaded LSposed + Shamiko so If I can get to this point with your help, I'm not sure how do I install these two modules since they're .zip. From Magisk?

Enough for now. :)

Thanks for your help!
[Android Auto General] gullzway:
At this point, I think Step 5 is the most important. If you don't change the package name, Google blocks it.

I have it working on my non rooted Pixel 6Pro(Android 13,) and Oneplus 9 also Android 13.

5. Apps (for now only Screen2Auto to my knowledge) need their internal package name changed to something different,

you can use MT Manager for this: https://mt2.cn/download/

I'm reading a lot of people having problems with this and AAAD on Android 14. Ones I've seen with it working, already had it working on Android 13 before updating.

Issues · shmykelsa/AAAD

Contribute to shmykelsa/AAAD development by creating an account on GitHub.

github.com
[Android Auto General] lukccp:
Ok, I understand that. But as you see, I already failed at step 3 and 4...
[Android Auto General] Toastking:
Thanks, but installing via MT Manager doesn't work either (in MT Manager, clicking on the APK and then selecting "install" instead of "view").

I'm afraid there is just no way of getting any of this to run on a Android 14 device (in my case, a rooted Pixel 8) that has not been updated from Android 13, but already been shipped with 14.

I have activated Dev Mode + Unknown Sources in Android Auto, have rooted the phone + Magisk installed, Lsposed module + Shamiko, installed AA Xlauncher with KingInstaller and activated its Xposed module, changed the package name of S2A with MT Manager to something generic, and used the button "Select Apps" (localized to my language, it's the left button in the second row) in AA AIO to select Screen2Auto with my changed package name.

Still, S2A doesn't show up in AA.

Does the "Patch user-defined apps" button (second row, right button) in AA AIO need to work? Because when I click it, it's doing something for some time and then says the process has failed.
[Android Auto General] gullzway:
I didn't do steps 3 or 4. And I didn't install with MTmanager.

I opened MTmanager. Select s2a apk, View, click s2a apk, click AndroidManifest file, string pool, scroll down to the first ru.inceptive.screentwoauto and change the name of screentwoauto. Click top right 3 dots and save.

Then installed S2A apk with KingInstaller. Select file, Install as King, when it pops up it tells you to select the Package Installer, not the King one.

Also forgot, my Pixel 6Pro is on Android 14, but already had s2a working.
[Android Auto General] lukccp:
I followed all your steps.

Maybe just about renaming, should it be done like:

ru.inceptive.screentwoauto -> ru.inceptive.screentwoauto123?

When I open KingInstaller I get message: "Google package installer is used on your device..."

Than I select file and I have no message about selecting installer:

After that I choose "Install anyway":

As I understand from your "when it pops up it tells you to select the Package Installer, not the King one." it's somehow different as I have?

Anyway, I've completed the installation, I'll report the result when I get in the car. :)
[Android Auto General] gullzway:
Looks like I get that because I checked "Enable if you use Oppo,Realme, or OnePlus phone"

Guess that shouldn't matter if your on a Pixel. For renaming, I just scrambled the letters.

Mine looks like this.
[Android Auto General] lukccp:
Aaa ok, I got it.

Yes, I think this should have no effect. I'll report.
[Android Auto General] gullzway:
You may have to clear data in Android Auto in settings as well.
[Android Auto General] lukccp:
Done.

Thank you for now!
[Android Auto General] gullzway:
You can check to see if S2A will appear in Android AUTO by going to Apps/Android Auto/additional settings in the app. Click on Customize Launcher and look for S2A.
[Android Auto General] lukccp:
Oh yes, of course...

But, it's not there. :(
[Android Auto General] lukccp:
Anyone else can help me with my questions :)?

Tnx.
[Android Auto General] Toastking:
Right now it's not even possible to get it working on Android 14 with root (see my experiments above), on your phone without root it will be even harder. We have to wait until someone figures out what Google has implemented as new protection mechanism in Android 14.

It's amazing that this custom Android Auto community is rather small, I would imagine there's quite a lot of people using AA today since almost every new car has been equipped with it for the last few years.
[Android Auto General] lukccp:
Thanks for info! Then I won't deal with it any further.

Different forums have different information, and we also have different phones, so it's all quite confusing.

I'm quite surprised myself, because now I'm using AA for the first time in my car and I was sure that there are a bunch of mods for this platform and I didn't even doubt that it's not possible to do screen mirroring. Obviously I'll have to use WebLink and switch back to cable when there'll be need. :)
[Android Auto General] gullzway:
It DOES work on my unrooted Pixel 6 Pro on Android 14. I already had it working on Android 13 before updating to 14, but you would think it would work on a fresh install on Android 14?

I'm not in that situation so I haven't tried.

Edit: Looked back and saw you mentioned devices that were working already on Android 13. Still, strange that would matter.
[Android Auto General] lukccp:
Yes, but I followed all your steps and doesn't work for me. :(
[Android Auto General] gullzway:
I may try getting it to work on my kids Pixel 6a that is on Android 14 already if I get a chance.

My Oneplus9 is still on A13, and my Pixel 6Pro already had it installed.

Strange times when a jailbroken iphone has a MUCH better experience with Carbridge tweak than Android can get. Though iphone jailbreaks have slowed almost to a halt on anything newer than iOS 15.4. With my 13 Mini, I can use almost any app, video streaming, etc. all while leaving the phone free to use as needed.
[Android Auto General] lukccp:
That would be great... I will be really grateful to you for your time!
[Android Auto General] :
I'm Japanese so English is broken

My phone

Android14 AA 10.7.634234

you need rooted device

1st use rooted android13（12,11）device（anything ok）

→update AA to new version

→install s2a as google apps

→setup all setting include connect car

→this method is Already published

then use titanium backup→backup Android auto

next on your rooted Android14 phone→install same s2a apk

last restore titanium backuped Android auto on your rooted Android14 phone

for me it's good

try
[Android Auto General] lukccp:
Hi.

Thank you, but I don't want to root my phone... :)
[Android Auto General] :
ごめん

I don't know how to none rooted device
[Android Auto General] Jinkue:
S2a working on non rooted Android 14 Samsung 23 ultra . Couldn't install s2a with Kingstaller but was able install with AAAD and works well on wireless android auto set up. I have used s2a on non root Samsung note 8 and 9 for a couple of years.
[Android Auto General] lukccp:
Can you please describe all the steps?

So as I see over the whole Google in last 2 days there is no confrimation that S2A works with Pixel and A14, with S2A installed AFTER phone was updated to A14.
[Android Auto General] Toastking:
Was your S23 ultra upgraded to Android 14, i.e. shipped with version 13 or below?

The reason I'm asking is that even in the AAAD threads / on their github, people are reporting that nothing is working right now on fresh, rooted Android 14 installations. Basically exactly what we're seeing with the other method described in this thread.

Edit: Just tried installing S2A on my rooted Pixel8 with Android 14, of course the installation works, but it's not showing up in Android Auto.

@yutax is describing a process to basically emulate a phone that has been shipped with pre-14, equipped with custom AA apps and then upgraded to 14. Since I don't have a rooted Android 13 phone laying around, this won't work for me.

Someone has to be able to figure out what's going on here... :confused: It really is a shame that the AA community seems to be so small.

Edit2: The same thing seems to apply to Fermata on Android 14. Fermata Control is still showing up in the AA menu, but Fermata itself doesn't (even with active Lsposed hook).
[Android Auto General] :
I agree. I couldn't do it with Android14 using the previously mentioned method, so I was able to do it after restoring a backup of another model.

google translate
[Android Auto General] lukccp:
Yes I can install as well from different sources, but s2a never shows in AA.
[Android Auto General] Jinkue:
S23 ultra was android 13 but updated to android 14. I installed the s2a app before it updated to android 14 and successful install was just a fluke and trial and error as I don't have any expertise in this matter.

On my non rooted samsung note 8/9 I was able to successfully able to install s2a 3.6.2 version app by enabling download from unknown sources in AA and using AA Ease. (all information from this thread). s2a stilll works on both phones. On S23 ultra, android 13, I had to upgrade AA before I could access the setting and enable download from unknown sources button. I attempted AA Ease install of s2a but the install was aborted/blocked. So i tried using AAAD pro version and it installed s2a 3.7 immediately. Had to enable some permissions such as accessibilty, allow change system settings.
[Android Auto General] Jinkue:
It was shipped as android 13.
[Android Auto General] Toastking:
Well that explains why it worked for you. S2A is known to be working on Android 13 (as well as Fermata etc.), even when upgrading to Android 14 AFTER installation.

What we are discussing here - and what is NOT working for anyone for some reason only Google knows - is installing unofficial Android Auto Apps like S2A on Android 14.
[Android Auto General] gullzway:
No luck here testing out one of our Pixels(6a) on Android 14 that never had Screen2Auto.

S2A not showing in AA after installing MTmanager modded S2Aapk.

I'm wondering if something else needs changed in the AndroidManifest, or if it's something else entirely.

Hopefully someone can figure this out. Fortunately, My 6Pro was already working and my Oneplus9 is still on Android 13.

Edit: Anyone try removing Android Auto and installing an Old version. Installing S2A, then updating AA?

Edit2: Can't uninstall AA, at least on a non rooted Android 14 phone.

Maybe I should go buy that Oneplus 11 I looked at today for $410, didn't check to see if it was still on Android 13.
[Android Auto General] lukccp:
But probably you can disable AA and install old one?

Btw, what about S2A developers? Are the quit with their job about S2A?
[Android Auto General] gullzway:
Don't know, nothing posted on their website in over 1.5 years, other than the 3.7 S2A apk.

INCEPTIVE.RU - Полезные статьи для программистов

INCEPTIVE.RU - Полезные статьи для программистов

inceptive.ru
[Android Auto General] lukccp:
Yes, I saw that and GitHub as well.

Probably they already work for Google. 😁
[Android Auto General] gullzway:
Maybe, all the iphone jailbreak devs get hired by Apple.

I messaged the OP of this thread, but they haven't posted in here in 2.5 years.

I guess keep an older Android phone handy for use in vehicle. I had been mainly using a jailbroken iphone 13 mini with Carbridge tweak lately, but since installing Fermata Auto, I've been using my Android phone.
[Android Auto General] :
My point is that you can restore any rooted smartphone up to Android 13 to another new Android 14 rooted smartphone. For example, Xiaomi (Android13) → Galaxy (Android14).

google translate
[Android Auto General] Toastking:
Sure, but technically speaking, at least with full (root) access to the system and Lsposed's ability to hook into any function call, we should easily be able to make the Android Auto app behave exactly like we want it to. Here's to hoping that someone with the necessary technical expertise will look into that.

Maybe we should just ditch the Android Auto app entirely and hook into whatever functionality is actually streaming the rendered screen to the car's head unit :D
[Android Auto General] gullzway:
So you need to install modded S2A app on Android 14 phone, then install the backed up Android Auto app with Titanium backup on Android 14 phone?

I've saved it on my Moto Ace 5g(Android 10) in case I need it in the future.
[Android Auto General] :
S2A、Android 11、12、13、14に対応している機種ならどれでも大丈夫だと思います。私の場合、Galaxy（Android 11）から復元したAAを別の機種（Android 14）で使用しています。

グーグル翻訳

Sorry,I'm new commer

#3167 was Japanese??&I can't delete that comment.

I wrote

I think any model that can be used S2A, Android 11, 12, 13, 14 will be OK. In my case, I am using AA restored from Galaxy (Android 11) on another model (Android 14)
[Android Auto General] lukccp:
That's what I'm using now.I use Autolink mirroring which is supported from my Pioneer radio and it works great.

But S2A looks great for me (I never used it, because AA is new thing for me) is that you can use it inside AA.

Actually before starting to use AA, I was 100% sure there are a lot of "hacks" how to use whatever you want app inside AA. :)
[Android Auto General] gullzway:
There "are" multiple tweaks for Android Auto third party apps.

They have Not worked on phones shipped with or upgraded to Android 14(unless already installed) for a couple months now apparently. Hopefully someone finds a fix.

https://www.reddit.com/r/AndroidAuto/comments/16weokt
[Android Auto General] lukccp:
AAAD, AAEase, AAStore... Anything else :) ?
[Android Auto General] Toastking:
Hi all,

I've finally managed to get Screen2Auto as well as Fermata running on my Pixel 8 with Android 14. Honestly, it wasn't so hard after all.

1. Uninstall all Android Auto updates via Play Store, uncheck "automatic updates" (three dots).

2. Manually install an older version of Android Auto, I have used 9.0.630814-release from apkmirror, clear data / reset the app.

3. Enable Developer options in the Android Auto App and check unknown sources.

4. Install Fermata using King Installer and install S2A with a changed packaged name, also using King Installer. I have also added S2A via AA AIO Tweaker and have the LSPosed Module of AA Xlauncher installed, I don't know if that's actually necessary or not.

5. If you look at the App List in Android Auto's settings now, Fermata and S2A will show up like they're supposed to. However, you probably won't be able to connect the device to your car. At least I wasn't, I think Play Services is preventing the usage of old Android Auto versions somehow.

6. Using the Play Store, just update the Android Auto app to the newest version. Clear data / reset the app.

=> Android Auto will now work, in the newest version, on a Android 14 shipped phone, WITH S2A and Fermata working perfectly fine ;)
[Android Auto General] lukccp:
I followed all your steps and actually I've done this before:

I have the same AA version right now, I used KingIns, and Fermata version is 1.9.5.

No luck... :(

But, you have rooted phone? Maybe there's a catch?

And another difference is that I'm using Pixel 7Pro and it was updated to A14. But on 13 there was never S2A or Fermata installed.
[Android Auto General] gullzway:
I just tried as well on our unrooted Pixel 6A. No luck.

S2a doesn't show in the Android Auto app after step 4.

May have to have a rooted phone to use the AIO tweaker app.
[Android Auto General] Toastking:
Yes, my phone is rooted. But I don't think it needs to be for Fermata to work, only for S2A.

If you go into Android's app information dialog of the Fermata app (the one for permission management, uninstallation etc.), does it at the very bottom say that Fermata was installed by Google Play?
[Android Auto General] lukccp:
Yes AIO tweaker needs root. I get message "Please allow root access.".

But I installed Fermata/S2A directly from KingInstaller.
[Android Auto General] gullzway:
Mine doesn't show that on my Oneplus 9.
[Android Auto General] lukccp:
App installed from KingInstaller.

So this should be ok.

Should I use any moded Fermata? I actually don't know where I downloaded it...
[Android Auto General] gullzway:
Yes, I uninstalled all updates to AA and installed the older linked one. Installed modded S2A with Kinginstaller and S2A doesn't show in AA settings under Customize Launcher or on car screen.

I did Not try using AAstore, but this post is Old, and I believe the package name Has to be changed now.

https://www.reddit.com/r/AndroidAuto/comments/qtcqb9
[Android Auto General] lukccp:
I think for S2A you should be rooted as @Toastking said.

First try with Fermata.
[Android Auto General] Toastking:
Agreed. Fermata should show up just by installing it with King Installer (and using the old AA version described above). I wouldn't try to get S2A running without root access honestly.

@gullzway This is the correct menu, the information missing there has to be something OnePlus specific. Maybe try to research a different way to show the installation source for an app in Android.
[Android Auto General] lukccp:
Some good news:

Google Pixel 8, carstream showing but, no new messages on this drive, also no Fermata auto, it does not show up on android auto. Any help highly appreciated. · Issue #269 · shmykelsa/AAAD

Contribute to shmykelsa/AAAD development by creating an account on GitHub.

github.com
[Android Auto General] Jinkue:
So I had s2a working on new S23 Ultra Android 14 (bought as android 13) but had play protect s2a warning and black screen on s2a. I lost s2a from AA when i was fiddling with settings and was trying to reinstall s2a on AA. Carstream also started showing no messages on drive after reinstalling the carstream from AAAD.

I was stuck with no working apps so I decided to downgrade my S23 Ultra to android 13 UI 5.14 with Odin.(firmware from samfw but links on xda thread). Turned off play protect and reinstalled both apps and have updated software back to android 14 UI 6. Enabled all relevant permissions on s2a and it is working well. Carstream is also working.

Downgrading to stock android 13 and upgrading back to 14 may be an option.

Edit: S2A has dropped off app list
[Android Auto General] yuri76:
Of course. On those versions they no longer update security patches

Inviato dal mio SM-G975F utilizzando Tapatalk
[Android Auto General] raho78:
I installed previous version of Android Auto and now it starts up again ?
[Android Auto General] gandamaluko:
How to configure the Touch button to go back to the launcher? I tried all options, but it goes to the mais Screen of Android.
[Android Auto General] aragon88:
Hi, this app is great! good job! However, I am having an issue right now. The app seems fine, was able to load and run. Even got into the home screen when I launch the app but whenever I launch any app, the screen went black. But the touch function is still working. I was still able to control my phone through the HU. But it just seems that it wasn't mirroring my phone display on it. Anyone having a similar issue? any help would be really appreciated. I am using MIUI 11.0. Android 9. Screen2Auto 2.7. AA Version 5.4. Thanks.
[Android Auto General] anto1208:
done but the icon does not appear on the navigator of my KIA car.

:(
[Android Auto General] Asselnik:
Hello,

i have a very crazy problem.

It took me several days to find the error :)

When the option "Reset on Lost Focus" is activated, then the TASKER Notification Trigger does not work anymore.

I have a tasker trigger to trigger the notifications of my incoming emails and then the email is reading. So this trigger does not working when the option in s2a is set.

Or it works only after a few minutes. Total crazy, but i have test it a few times.

The problem persists even when s2a is not running.

And the problem is only when Android Auto is running.

Do i disconnect the phone from the car, the notification trigger is ok.

Can anyone explain that? :)

Perhaps the "focus on lost" option is triggerin anything and stops the tasker trigger?
[Android Auto General] Fishcat7:
My phone is Samsung Note 8. Stereo car is Pioneer AVH Z7100DAB.

Screen2auto is visible only on the android auto emulator for Windows, when I connect the phone to the car this app is not available in android auto.

I tried to unlock with the inbuilt unlock and with phenotype patcher, but the result is the same.

This problem is with all third party apps...

I already tried to uninstall and reinstall all android apps...

What could be the problem?
[Android Auto General] Mokka X18:
Hi Anton, check that it ( S2A ) unlock, go to your Super US and open it and click Apps and find if S2A in there and if you are using Magisk go to log and find S2A there.

If you found S2A in there ( Super SU or Magisk so the application is unlocked and must be in Android Auto .

It will be nice if you have a look through the all threat from page 1 to 30 , I did that before installing the S2A
[Android Auto General] globs7:
For all with s2a not appearing in Android Auto:

Clear the data of the Google-Play Services (com.google.android.GMS).

Then start the installation right from the beginning.

Worked for me!
[Android Auto General] Jooctarj:
Netflix

Hello, has anyone managed to run Netflix on Screen2Auto? I had a procedure in AAMirror, but with the arrival of Android 9, it stopped working, and Screen2Auto doesn't work.
[Android Auto General] BostonDan:
Jooctarj,

Check out the thread "Mirror Screen on Android Auto" page 181. The post by Datrix describes this.

It's because of DLP Data Protection that it sees Screen2Auto as another HDMI output and prevents the video feed from showing.

One thing I had to do, since /system is read only is i did everything on my sdcard and then created a symbolic links to the programs in the /system/bin directory.

Let me know if you have any trouble, but I can attest that the method works brilliantly.

Cheers,

B.D.

P.S. I will include the links to the post later, as I am travelling and do not have my laptop with me to copy the links to the post properly right now.
[Android Auto General] Jooctarj:
Netflix

I'm a bit of a layman on the subject, could you explain it better to do it on mine?
[Android Auto General] Medicina200401:
Hi. The split screen function using google maps and any other application does not work.

When you choose google map and any other app, the screen is not divided and google maps is seen in full screen.

Hopefully it can be solved

Thank you
[Android Auto General] annexhack:
Hey. I can give advice. Yesterday, I posted on my website an article on how to disable standard applications in AA (in s2a, a link in the about section). When you disconnect it in AA, you can launch it as an application on the phone without opening it in AA.