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

[tosonny]

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.

 

[gullzway]

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.

 

[tosonny]

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.

 

[gullzway]

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]

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]

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]

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]

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.

 

[falciatrice10]

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]

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.

 

[Sjhingan]

FYI, I just updated to Android Auto version 8.1.626474-release, via Playstore. Started getting a pop-up about update required soon.

Screen2Auto still working, didn't have to do anything. Pixel 6 Pro unrooted.

what about 8.2.62? Have you tried it yet?

 

[tosonny]

what about 8.2.62? Have you tried it yet?

Works ....S2A shown ...but that´s not my problem for months. It will disappear.

 

[gullzway]

what about 8.2.62? Have you tried it yet?

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.

 

[tosonny]

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]

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?!

 

[Jinkue]

what about 8.2.62? Have you tried it yet?

I have updated AA to 8.2.62 version and it s2a is still present and working on unrooted samsung note 9.

 

[tiho5]

So Titanium Backup might be better for this reason?!

TB wipes data and then restores it. So it does both things in one click.

Swift backup doesn't wipe data before the restore, but you can wipe it manually and then restore it.
The dev of swift backup likes it like that.

You can use either one.

 

[zgfg]

So Titanium Backup might be better for this reason?!

There is Clear Data in Swift Backup - screenshot attached

Besides, you can Wipe Data for a given app from Settings, Apps, Manage apps, navigate to an app

 

[tosonny]

There is Clear Data in Swift Backup - screenshot attached

Besides, you can Wipe Data for a given app from Settings, Apps, Manage apps, navigate to an app

So if I restore AA with TB I have also to clear data in AA? I thought TB does it automatically.

 

[zgfg]

So if I restore AA with TB I have also to clear data in AA? I thought TB does it automatically.

I don't use TB. I wrote that you can Clear Data for an app from the Swift Backup - take More and scroll to the right

Btw, you can even manage Battery optimization from the Swift Backup (I was not aware but found it while taking you the screenshot)