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

Search This thread

tosonny

Senior Member
Jan 27, 2011
540
74
I've been trying all sorts of variations over the past few days, trying to follow BostonDan's advice: "You need to know why S2A is being removed" and "Ultimately, it's a feature that's critical and not really difficult to implement".

I have tried different settings in the developer settings and disabled many permissions in the app (because Google might read them) in both AA and S2A. I've tried pretty much everything I have access to and nothing has helped.

So much for saying "not difficult to implement". Apps like S2A only exist because people are innovative and kind enough to develop and share them. I donated to it because I can't contribute otherwise. If I had something to contribute, I would share it, because that's the only way apps like this and the solution to problems with them (in the fight against Google) will continue to exist in the future. Keeping secrets to yourself - with all understanding for the worries that justify it - is just the wrong way.

Whereby I add that - if I hadn't found the solution myself and was entrusted with a secret - I would stand by the helper's word and would not reveal it. He would have to do that himself.

I hope that for S2A and any other apps they use to be able to use S2A, those who don't tell your secret how to get around the problem also sent money to the developers.

If anyone has an idea or if those in the know would like to help us, I would be very happy.

Edit 1: the last thing I have tried now (after contact with the devs in their Telegram group) is to freeze Google Services Framework. If this will help or cause problems with other Google services ...I have no idea yet.
Edit 2: didn´t help. Sometimes Googles frequency is pretty high. S2A was deleted very quickly this time.
 
Last edited:

gullzway

Senior Member
Nov 17, 2007
342
55
I've been trying all sorts of variations over the past few days, trying to follow BostonDan's advice: "You need to know why S2A is being removed" and "Ultimately, it's a feature that's critical and not really difficult to implement".

I have tried different settings in the developer settings and disabled many permissions in the app (because Google might read them) in both AA and S2A. I've tried pretty much everything I have access to and nothing has helped.

So much for saying "not difficult to implement". Apps like S2A only exist because people are innovative and kind enough to develop and share them. I donated to it because I can't contribute otherwise. If I had something to contribute, I would share it, because that's the only way apps like this and the solution to problems with them (in the fight against Google) will continue to exist in the future. Keeping secrets to yourself - with all understanding for the worries that justify it - is just the wrong way.

Whereby I add that - if I hadn't found the solution myself and was entrusted with a secret - I would stand by the helper's word and would not reveal it. He would have to do that himself.

I hope that for S2A and any other apps they use to be able to use S2A, those who don't tell your secret how to get around the problem also sent money to the developers.

If anyone has an idea or if those in the know would like to help us, I would be very happy.

Edit: the last thing I have tried now (after contact with the devs in their Telegram group) is to freeze Google Services Framework. If this will help or cause problems with other Google services ...I have no idea yet.
I haven't read your post history to see what you've tried already, but from what I have read Google disables the app when it detects it in the android/data folder.
That's the main point of installing with AAEASE, it renames the program so Google doesn't recognize it.
I'm going on well over a year with no issues after using AAEASE to install S2A.

What is your S2A program folder named in /storage/emulated/0/Android/data when checked using File Explorer app? https://www.apkmirror.com/apk/speed-software/explorer/explorer-3-9-1-release/

Look what mine is named 2nd from the bottom. If yours is named ru.inceptive.screentwoauto, then that is why it keeps disappearing. If it is not, then I'm not sure what is happening.
 

Attachments

  • Screenshot_20221019-134921.png
    Screenshot_20221019-134921.png
    364.7 KB · Views: 72

tosonny

Senior Member
Jan 27, 2011
540
74
I haven't read your post history to see what you've tried already, but from what I have read Google disables the app when it detects it in the android/data folder.
That's the main point of installing with AAEASE, it renames the program so Google doesn't recognize it.
I'm going on well over a year with no issues after using AAEASE to install S2A.

What is your S2A program folder named in /storage/emulated/0/Android/data when checked using File Explorer app? https://www.apkmirror.com/apk/speed-software/explorer/explorer-3-9-1-release/

Look what mine is named 2nd from the bottom. If yours is named ru.inceptive.screentwoauto, then that is why it keeps disappearing. If it is not, then I'm not sure what is happening.

Ha ...sorry that´s unfortunately not the point. We are far beyond this package name thing. We all use AAEase or Lucky Patcher to hide the package. Google has found another way ...but the strange thing is, that a lot but not everbody has this problem, that S2A disappears after some hours or at least a day.
 
Last edited:

gullzway

Senior Member
Nov 17, 2007
342
55
Ha ...sorry that´s unfortunately not the point. We are far after this package name thing. We all use AAEase or Lucky Patcher to hide the package. Google has found another way ...but the strange thing is, that a lot but not everbody has this problem, that S2A disappears after some hours or at least a day.
Interesting. I'm on an unrooted Google Pixel 6 Pro and have no issues.
Go figure.
 

tosonny

Senior Member
Jan 27, 2011
540
74
Interesting. I'm on an unrooted Google Pixel 6 Pro and have no issues.
Go figure.
@BostonDan: you see there are a lot of users that don´t have our problem. This means that Google isn't campaigning against anyone and everyone and isn't reading this. Because otherwise it would no longer run on a non-rooted pixel. Why some of us have this strange problem remains a mystery. But disclosing your solution would by no means harm you - that's obvious - and help many others. I hope you understand and help those affected. Gladly via PM, because everyone obviously does not need this solution anyway.
 

tosonny

Senior Member
Jan 27, 2011
540
74
I haven't read your post history to see what you've tried already, but from what I have read Google disables the app when it detects it in the android/data folder.
That's the main point of installing with AAEASE, it renames the program so Google doesn't recognize it.
I'm going on well over a year with no issues after using AAEASE to install S2A.

What is your S2A program folder named in /storage/emulated/0/Android/data when checked using File Explorer app? https://www.apkmirror.com/apk/speed-software/explorer/explorer-3-9-1-release/

Look what mine is named 2nd from the bottom. If yours is named ru.inceptive.screentwoauto, then that is why it keeps disappearing. If it is not, then I'm not sure what is happening.
FYI: we - that have this f...ing problem - see S2A in AA Launcher. But after some hours or at least a day it disappears and we have to reset AA to see it again. And this is boring and BostonDan has found a solution for that.
 

tosonny

Senior Member
Jan 27, 2011
540
74
Guys, I'll summarize the clues for the scavenger hunt here. If anyone has an idea of what to do, please do so.

We all love to hear ideas about what "hack the process..." and "only one function" might mean. Unfortunately, I don't get the slightest hint from @BostonDan, even just vaguely asking whether one needs to use third-party apps to remove certain rights, whether it's more likely to be done in AA or in the individual apps that are affected (S2A etc.) would have to do (which could also be the case, because he writes that he always had to carry out this "hacked process" after patching new apps in the tweaker. This means that you either have to do it again after each patch or that you have to do it for each individual app that needs to be shown. So I thought that because Google looks for suspicious apps based on these criteria, maybe the apps need to be stripped of some rights. I was unsuccessful. So I don't even know if it's a firewall issue , a blocking issue, a rights issue in AA, in the apps, or whatever. But according to BostonDan, it's very simple.

I could puke....
  • Yes, vanced music fully works with AA. I use AA AIO tweaker to patch GMS to whitelist it. But again, I had to hack the process so that it didn't revert back to being blacklisted, which is what current Android Auto does.
  • I enabled it with AA AIO tweaker and used the same hacked process above.
  • The only thing I will state is that the hack I had to perform to get everything working is literally one function, so it is not hard to implement.
 

tosonny

Senior Member
Jan 27, 2011
540
74
I've now found a shortened workaround so that after wiping the data and cache I don't have to a) set everything up again in AA launcher and b) not have to set up AA again when connecting to the car.

I clear data and cache then restore AA using Swift Backup. That makes things a lot easier.

By the way, just restoring AA is not enough. Google leaves something in the data that even the restore doesn't remove.
 
  • Like
Reactions: zgfg

falciatrice10

Senior Member
Feb 19, 2013
494
37
42
TUNISIA
Hi
It worked on my car with my Samsung galaxy S9+, but only once, in the second time, screen2auto disappeared from Android auto screen !!!
 

tiho5

Senior Member
Jun 21, 2010
2,662
1,009
Bulgaria
I've now found a shortened workaround so that after wiping the data and cache I don't have to a) set everything up again in AA launcher and b) not have to set up AA again when connecting to the car.

I clear data and cache then restore AA using Swift Backup. That makes things a lot easier.

By the way, just restoring AA is not enough. Google leaves something in the data that even the restore doesn't remove.
Swift backup doesn't wipe data for the app before restore unlike titanium backup.

Wipe data and then restore and it will work.

But first make sure you have a working (as you like it) AA and then back it up.

Let me know if this helped. If it did, I'll try to guve you one more idea how to get the rest to work from then on.
 

tosonny

Senior Member
Jan 27, 2011
540
74
No, it looks like that just came out four days ago. I'll stick with the one I'm on until it forces another update.
I have 8.2.623924 ...and the behavior is like always: S2A shown, disappears, shown after deleting data & cache, disappears and so on. So there is absolutely no difference to the former version.
 

tosonny

Senior Member
Jan 27, 2011
540
74
Swift backup doesn't wipe data for the app before restore unlike titanium backup.

Wipe data and then restore and it will work.

But first make sure you have a working (as you like it) AA and then back it up.

Let me know if this helped. If it did, I'll try to guve you one more idea how to get the rest to work from then on.
So Titanium Backup might be better for this reason?!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    You have to turn off Autororate with Tasker after changing rotation. This did the trick for me.
    You need:
    1.Force rotation
    2.Wait time of 500ms
    3.Autorotate off
    I use tasker profile to rotate 90 deg when auto android is engaged (enter criteria), and then an exit task to turn off fixed rotation once Android Auto is disengaged (exit criteria).

    No wait time for my solution.

    Also will definitely give thumbs up for the new AAAIO Tweaker (Shmykelsa)! Works great!

    Cheers,
    B.D.
    1
    me to,I make my s7edge work on car screen for 4years.but,tendays ago,use aaese install s2auto,ok,show on android auto list,when i press s2auto button on my car,just black,and phone not change,it looks s2auto try to work,but,no work.
    For everyone who's getting the black screen, I might have a solution. Use to have the same issue.

    Before pressing the s2a icon on the car screen, you must first open the app on your phone and stay on it.
    Once it done you can can press the s2a icon on the screen car and enjoy.

    I hope it work for you but that has been my solution for the past 2 years.
    Sorry for my English!
    1
    screen2auto works on Android 10 with root at 1000 percent, the problem will always be on Android 11,12,13
    You will need it
    screen2auto v 3.5.6 apk
    AA-AIO-TWEAKER-5.0.2-release apk
    Magisk 23.0 zip
    SU_Connector zip

    P.S Magisk 23.0 install SU_Connector zip and reboot your phone
    1
    screen2auto works on Android 10 with root at 1000 percent, the problem will always be on Android 11,12,13
    You will need it
    screen2auto v 3.5.6 apk
    AA-AIO-TWEAKER-5.0.2-release apk
    Magisk 23.0 zip
    SU_Connector zip

    P.S Magisk 23.0 install SU_Connector zip and reboot your phone
    Maybe using all that is working for you, but that does not necessarily mean that you need all of that to make it work, at least for some phones anyways.
    For example: Pixel 7 Pro (ships Android 13) All you need is AAEase, install Screen2Auto using AAEase and you have a working setup, no fussing with AA version or anything.
    1
    If the S2A opens for you, but you have a black screen when you start any application, this may help
    S2A: -> Screen settings -> Screen size -> Manual resolution
    Set the exact value:
    - screen widht
    - screen height
    - screen DPI
    to the resolution that the phone has
    reboot
  • 117
    Smartphone screen on Anddroid Auto HU car screen
    For root devices only!

    a65be9f97d8097a3eeccdacfbe7ac48d.png

    b8add53a049c33be76f7e3778db2551c.png



    c1b9abbde2a1f4e7a6920f3b7bd1ffe2.png



    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...
    1d1ca5ad04e260cb8dfa7360d36cee00.png

    Installation and setup:
    1. Download and Install Screen2Auto
    6760829d5c83bfb472ea0a96d8b0efde.png
    2. Enable developper settings in Android Auto and enable Unkown sources in developper settings.
    1. Launch on the Android Auto mobile device
    2. Open the menu, tap the tab "About Android Auto"
    3. In the menu that opens, tap on the gear (settings). Then we crawl to the very bottom of the menu that opens: "Version 4.5. *** - release".
    4. 10 times tap on the display of the version of Android Auto, a window will appear where we must agree with what we are doing. Click "Yes."
    5. Go to the menu (tap "three points") and select the tab "For Developers" that appears in the menu
    6. In the last line, put a checkmark "Unknown sources" or use other settings of the developer's menu.
    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.
    1ae13868aa9142dd0ea19722b818d9a7.jpg
    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.
    3e5e464d111050be0db4f57505492313.png
    0222f487a017f62a6242d37d27e82b3a.png

    Don't forget to use the button (if you want course):
    cb294618ab788427637345c9f1030b77.png


    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 new

    v3.5.2beta
    • Bug fixes

    v3.5beta
    • Adapted for Non Root devices
    • Notification when pause (for automation).
    • Bug fixes
    • Languages update

    v3.4.6
    • Added persistent quick launch bar
    • Added a pause S2A. If need to use the phone (so as not to disconnect)
    • Fixed bug with floating button
    • Fixed bug with choosing launcher button and background
    • Minor fixes

    v3.4.5
    • Added the ability to change the icon of the floating button
    • Added autostart mapcam.info
    • Added starting Tasker task after completion
    • Minor fixes

    v3.4
    • Fixed jambs
    • Added Support for Screen2Echo*
    • *Screen2Echo - application idesigned to link two phones. An application for those who do not want to get root on their main phone, and the second one is always in the car . Screen2Auto and S2Echo communicate via WiFi Hotspot.
    • Added Function to enable Hotspot at phone startup

    v3.3
    • Bug fixes
    • Switch "Do not restore" in the settings
    • Fixes for some jambs version 3.2

    v3.1
    • Bug fixes
    • Fix launch on Android 5&6
    • Fix Netflix (be sure to enable accessibility)
    • Adjustment of language packs
    • Added new translations

    v3.0
    • Application optimization
    • Made initial setting (Wizard settings)
    • Updated language files. (Thanks for the translations)
    • Added driving safety warning

    32a6ff91f00801a90056ed0b6dc27241.png

    837e9dacbe128637ed1dcd820e3b0a00.png
    Preview

    29f8f3095dcb6e0f7c50945273cd8846.jpg

    74a842327d62fc08ff4094db75c5cf05.jpg

    d3ca794b3557868d6b0c5d0f1cb47726.jpg

    f12617d47c0d7ba10b38071596beea04.jpg

    2e7d1fd6cfc6285f47cb63c875f37344.jpg

    b3b5fbe231fd9037188cc9995ea7cea3.jpg

    e6cb6d066052a58c27c5fa40755c4a7b.jpg

    472ed615393e079d2cf3b0180ceb8bc5.jpg

    5798b314178fd956947295e55eac32c1.jpg

    Well, as usual, I will be glad your coffee
    8ba7613826381811e8ab595c18c11459.jpg
    Download: ↓↓↓
    10
    A new version 3.4.6 has been released

    • Added persistent quick launch bar
    • Added a pause S2A. If need to use the phone (so as not to disconnect)
    • Fixed bug with floating button
    • Fixed bug with choosing launcher button and background
    • Minor fixes
    9
    Screen2Auto 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
    9
    The 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
    hello how do you rename the apk with lucky patcher ... i'm interested thank you
    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 **):