I more than confirm what @thivamero says: I started my trials with two smartphones on android 8; none of them succeeded. After having upgraded them to android 9 everything worked nicelyI was able to get S2A to work on my Galaxy A5 2017...
I just had to upgrade it to Android 9 and install S2A with Kinginstaller and MT manager...
With pleasure,I more than confirm what @thivamero says: I started my trials with two smartphones on android 8; none of them succeeded. After having upgraded them to android 9 everything worked nicely
Here as well I second @thivamero : steps 1,2 and 5 are enough for both of my smartphones
It's reaaly a crystal clear intructions. Thanks Man. IT works on my Poco F1 A13 Nasuntara ROM + NGK kernel test buildS2A appears to be the most restricted app.
To my knowledge following levels of restrictions/by-passes exist:
1. Developer mode + unknown sources need to be enabled in the AA app,
you can tap the Version number in the AA app a lot, to unlock the developer settings.
2. Apps need to be "installed as Google Play",
you can use KingInstaller to do so: https://github.com/fcaronte/KingInstaller
3. Apps need to be "whitelisted in phenotype.db",
you can use AA-AIO-Tweaker for this: https://github.com/shmykelsa/AA-Tweaker
4. Apps need Xposed module to spoof an additional "installed as Google Play" check,
you can use Android-Auto-XLauncher-Unlocked for this: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked
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/
Open MT Manager => Open S2A.apk file => View => AndroidManifest.xml => String pool => Triple dot icon => Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online => Ok => Back arrow => Save and exit
=> Save AndroidManifest.xml modification + Auto sign => Ok
Open your package manager => Install modified / renamed S2A.apk
Thanks for these, some of these helped me I'm sure.S2A appears to be the most restricted app.
To my knowledge following levels of restrictions/by-passes exist:
1. Developer mode + unknown sources need to be enabled in the AA app,
you can tap the Version number in the AA app a lot, to unlock the developer settings.
2. Apps need to be "installed as Google Play",
you can use KingInstaller to do so: https://github.com/fcaronte/KingInstaller
3. Apps need to be "whitelisted in phenotype.db",
you can use AA-AIO-Tweaker for this: https://github.com/shmykelsa/AA-Tweaker
4. Apps need Xposed module to spoof an additional "installed as Google Play" check,
you can use Android-Auto-XLauncher-Unlocked for this: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked
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/
Open MT Manager => Open S2A.apk file => View => AndroidManifest.xml => String pool => Triple dot icon => Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online => Ok => Back arrow => Save and exit
=> Save AndroidManifest.xml modification + Auto sign => Ok
Open your package manager => Install modified / renamed S2A.apk
Thanks for the detailed reply. This was the way to get Fermata working again. I tried KingInstaller, AA AIO Tweaker, AAAD, etc, and nothing worked. Fermata was visible in AndroidAuto, but when launching it would freeze AndroidAuto. I am using a Moto Edge+ (2023) with Android 13 (June). Previous phone was Pixel 6 with Android 13, and on that one Fermata worked without any mods on July version of Android13. Appreciate the writup!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/
Open MT Manager => Open S2A.apk file => View => AndroidManifest.xml => String pool => Triple dot icon => Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online => Ok => Back arrow => Save and exit
=> Save AndroidManifest.xml modification + Auto sign => Ok
Enable dev mod + unknown sources plus
5th suggestion is enough for s22 ultra with android 13. Thanks for your suggestion.
I have a custom rom (crDroid 9.7), rooted, Android 13 on a OnePlus 9. S2A works.This is a crazy long way to mirror your screen to my car. Wow. Can this not be automated since basically everyone does it?
Tried it anyway, didn't work, ran into issues.
Followed all the steps, used Magisk and Lsposed magisk module and configured lsposed settings and King Installer and the tweaker and launcher and MT Manager to modify the Android manifest of share2auto... (6-7 apps to make screen mirroring work? lol) also tried patching with tweaker
If I change ru.inceptive.screentwoauto
.. it says package is invalid, but if I change ru.inceptive.screentwoauto.App then it installs but won't open, just flashes and then says stopped responding. The other string didn't exist.
With an unpatched share2auto all of the settings are enabled but nothing different shows on the car screen, just looks like regular Android Auto. No additional app icons even if added under Applications.
Android 13, OnePlus 11
Any ideas?
Worked like a charm here after a little fiddling -- but unlike some folks posting recently, all of the steps were required for my Poco F3 w/Lineage 20 w/Googles "spyware". Note for those with official Google Services, turn off play protect.S2A appears to be the most restricted app.
To my knowledge following levels of restrictions/by-passes exist:
1. Developer mode + unknown sources need to be enabled in the AA app,
you can tap the Version number in the AA app a lot, to unlock the developer settings.
2. Apps need to be "installed as Google Play",
you can use KingInstaller to do so: https://github.com/fcaronte/KingInstaller
3. Apps need to be "whitelisted in phenotype.db",
you can use AA-AIO-Tweaker for this: https://github.com/shmykelsa/AA-Tweaker
4. Apps need Xposed module to spoof an additional "installed as Google Play" check,
you can use Android-Auto-XLauncher-Unlocked for this: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked
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/
Open MT Manager => Open S2A.apk file => View => AndroidManifest.xml => String pool => Triple dot icon => Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online => Ok => Back arrow => Save and exit
=> Save AndroidManifest.xml modification + Auto sign => Ok
Open your package manager => Install modified / renamed S2A.apk
sorry, where can I get the S2A.apk?S2A appears to be the most restricted app.
To my knowledge following levels of restrictions/by-passes exist:
1. Developer mode + unknown sources need to be enabled in the AA app,
you can tap the Version number in the AA app a lot, to unlock the developer settings.
2. Apps need to be "installed as Google Play",
you can use KingInstaller to do so: https://github.com/fcaronte/KingInstaller
3. Apps need to be "whitelisted in phenotype.db",
you can use AA-AIO-Tweaker for this: https://github.com/shmykelsa/AA-Tweaker
4. Apps need Xposed module to spoof an additional "installed as Google Play" check,
you can use Android-Auto-XLauncher-Unlocked for this: https://github.com/Rikj000/Android-Auto-XLauncher-Unlocked
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/
Open MT Manager => Open S2A.apk file => View => AndroidManifest.xml => String pool => Triple dot icon => Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online => Ok => Back arrow => Save and exit
=> Save AndroidManifest.xml modification + Auto sign => Ok
Open your package manager => Install modified / renamed S2A.apk
I just keep the APK that I patched the first time and reinstall that with king installer per the instructions. Only when a new version is released will I have to change the package name and resign it again.By repatching, did you have to do the MT manager process again to rename the package?
You should change only the line that is named exactly "ru.inceptive.screentwoauto", ignore the other lines that are similar, like ru.inceptive.auto.screen, ru.inceptive.auto.config, ru.inceptive.auto.somethingelse, etceteraI need some help with:
"Filter =>
Type the package name of the app (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto") => Ok
=> Select the found package name (likely "ru.cvitnepei.neatruwtosceo" or "ru.inceptive.screentwoauto")
=> Alter it to something unique, don't tell your unique package name online"
When I filter, there come a lot of lines with this package name. Do I have to change it in every line?