yashsingh1/xdaforums huggingface dataset:
[Android Auto General] BostonDan:
I'm sorry, but as Google monitors this message board, while I do want to share, I do not wish to have Google patch this so that this is disabled on my own phone. For this reason I am declining to share my solution.

I'm sad that Google will not permit the .01% of us who are interested in modifying our phones to maintain such hacks.

I hope you can respect this. I will say that the solution is not difficult. Other than that, I'm afraid I must leave it to other individuals to identify how to solve this.

Cheers,

B.d.
[Android Auto General] virol:
HELLO,

I have installed aaease 6.2 on my rooted android 12 phone.

When using aaease to install S2A you see downloading the app and then it shows "installing" and the arrows keepng spinning forever.

What do I do wrong, do I miss some permissions ?
[Android Auto General] gullzway:
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.
[Android Auto General] 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.
[Android Auto General] gullzway:
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.
[Android Auto General] tosonny:
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.
[Android Auto General] gullzway:
Interesting. I'm on an unrooted Google Pixel 6 Pro and have no issues.

Go figure.
[Android Auto General] tosonny:
@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.
[Android Auto General] tosonny:
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.
[Android Auto General] 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.
[Android Auto General] 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.
[Android Auto General] 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 !!!
[Android Auto General] tiho5:
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.
[Android Auto General] Sjhingan:
what about 8.2.62? Have you tried it yet?
[Android Auto General] tosonny:
Works ....S2A shown ...but that´s not my problem for months. It will disappear.
[Android Auto General] gullzway:
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.
[Android Auto General] tosonny:
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.
[Android Auto General] tosonny:
So Titanium Backup might be better for this reason?!
[Android Auto General] Jinkue:
I have updated AA to 8.2.62 version and it s2a is still present and working on unrooted samsung note 9.
[Android Auto General] tiho5:
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.
[Android Auto General] zgfg:
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
[Android Auto General] tosonny:
So if I restore AA with TB I have also to clear data in AA? I thought TB does it automatically.
[Android Auto General] zgfg:
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)
[Android Auto General] tosonny:
I could thus create a schedule in TB in which AA is restored every 6 hours, for example. That would sort of settle the matter.

Edit: Ui, unfortunately TB can only save automatically, but not manufacture. Gone stupid.
[Android Auto General] tosonny:
So, I had to try it right now because S2A dissappeared. Restoring with TB and that's it. Not the best but at least a good way to get it back before entering my car.
[Android Auto General] zgfg:
Btw, for me Fermata and S2A disappeared over night but Swift Backup Clear Data followed by Restore for AA got them back

Btw, seems that AA does not care much about CarTube (playing YT only when car is stopped), it did not clear CarTube from AA (like Fermata and S2A)
[Android Auto General] logman9:
Great job..just hope you made a video on YouTube, correct correct setting of the appl

Great job..just hope you made a video on YouTube, correct correct setting of the application, and the benefit would be maximum
[Android Auto General] yuri76:
I don't know if the touch of the machine works anymore

Inviato dal mio SM-G975F utilizzando Tapatalk
[Android Auto General] farbara:
+1

SM-G988B cihazımdan Tapatalk kullanılarak gönderildi
[Android Auto General] pierluigi85:
Hi,

I use sreen2auto since a week and is a really Great job!

I use vlc, youtube, netflix and nowtv without problems!

Just a question: when i use "prime video" app, i see video only on the phone (samsung galaxy A10): in Android auto (mercedes w246), instead, I only listen audio but with black screen.

It is a problem of prime video app?

Someone in my situation?

Thanks everybody and a coffee is coming for the creator!
[Android Auto General] yuri76:
To me on s10 plus it worked until 2.5 I put the 2.6 and 2.7 and it no longer works. I went back to 2.4 and the touch after screen2aa launcher does not work

Inviato dal mio SM-G975F utilizzando Tapatalk
[Android Auto General] magicko:
Good job

:cowboy:
[Android Auto General] tosonny:
My questions (am on 2.7):

- Sometimes it happens that AA screen stays black if I open an app. No idea why. Next time it shows everything.

- How do I get these widgets on the screen. It shows only the time/date.

- If I start for example Mi Video app to watch a video it is shown very small (phone format, not rotated).
[Android Auto General] cri.cri:
Great job [MENTION=4263401]Uksus17[/MENTION], the coofee is on the way to you.

Everything works fine here, i have an Xperia X running lineage OS 16 and just got back to the 2.4 version now cause it seems for me the best till now.
[MENTION=1510680]pierluigi85[/MENTION]

i've got the same problem, but then I installed a Prime Video apk from march and now it works fine. Now i have the same problem with netflix and an older apk (2017) doesn't help.
[Android Auto General] Uksus17:
1. It depends on how the root works. Also from the smartphone settings (permissions, ect). Xiaomi or with Miui the most problematic device.

2. Swipe HU screen left

3. I recommend using any other third-party video player (for example, MX). And even better to use for video Fermata Media Player (really cool application) - https://xdaforums.com/android-auto/...mata-media-player-audio-video-player-t4079519
[Android Auto General] tosonny:
"HU" means what :confused:
[Android Auto General] ivandena:
Head Unit (in a few words your car radio)

Inviato dal mio SM-G955F utilizzando Tapatalk
[Android Auto General] Mokka X18:
Great work

Hello, really great work. I was using A A mirror but I tried S2A V 2.6 in rooted A 320 Oreo and so far working great with all audio and video apps. But with V 2.7 there is 2 issues

1st the file for adding a few more background wallpaper can not be able to found when I connect the phone to the PC like I did with V 2.6, even when I added the background wallpaper to the file through Root prowser, the additional wallpapers can not be found in the background section of the application.

2- How to add widget in the same place with the Clock ( mini ).

Once again thanks for your great work.
[Android Auto General] dejan-:
I also tested v2.7 briefly (just the connection) and it seems to work. At least phone screen was mirrored to HU of a car [emoji846] like with AA mirror.

Actual functionality I didn't have time to test.

Poslano z mojega SM-G930F z uporabo Tapatalk
[Android Auto General] raho78:
Unknown sources is active. Wiping data from google play services fixed it for me.

No, not a beta tester. But wiping data from google play services fixed the problem.

Thanks, B.D. This did the trick. It's working again.
[Android Auto General] ippoglosso:
Hi, I put this photo in the background folder, in the app you can't see it and I can't select it, how come?

Inviato dal mio HTC U11 utilizzando Tapatalk
[Android Auto General] nostraslo:
Same here. In version 2.7 own background images can not be used. Bug ?
[Android Auto General] Uksus17:
No. For some devices, you need to set the file permissions - 600 (rw- --- ---), instead of 644.
[Android Auto General] Uksus17:
1- See previous post.

2- Activate mini clock in Launcher menu and then scroll through the swipe or click on the car radio screen edges.
[Android Auto General] Uksus17:
Some useful pictures

Dear colleagues.

Sometimes on some devices after a long work, s2a touch stops responding. This is not an application issue. This is the problem of providing root access from Magisk side. Unfortunately, ensuring the stable operation of the root is becoming increasingly difficult (Google has taken de-rooting path). As a solution - s2a quick reboot by clicking the widget button.
[Android Auto General] tosonny:
this almost one click restoring stuff with TB saves my life.
[Android Auto General] tiho5:
Now that you've made it work with TB or swift backup restore (manually wiping data first bofore the restore if using swift backup), I can give you another advise. It might work or not. Try the following:

1. Restore data of a working AA. Wipe data first if using swift backup to restore it.

2. Do not start AA after the restore.

3. Use a terminal to change permission for AA shared_prefs folder, which is under: /data/data/com.google.android.projection.gearhead (use root shell)

Type "su"

Hit enter

Then type "chmod -R 551 /data/data/com.google.android.projection.gearhead/shared_prefs"

Hit enter

You can also use a root explorer to do this.

Making "/data/data/com.google.android.projection.gearhead/shared_prefs" readonly prevents AA from creating the following files:

/data/data/com.google.android.projection.gearhead/files/phenotype/shared/gh.phenotype.pb

/data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.gms.clearcut_client#com.google.android.projection.gearhead.pb

/data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.gms.maps#com.google.android.projection.gearhead.pb

/data/data/com.google.android.projection.gearhead/files/phenotype/shared/com.google.android.libraries.surveys#com.google.android.projection.gearhead.pb

They (or one of them) are the culprit. But they will not get created now any more.

This works for me.

For you it may work or not (different Android versions and etc), like I said. So if it doesn't work, remember what were the original permissions for /data/data/com.google.android.projection.gearhead/shared_prefs and restore them.

Now test and report here.
[Android Auto General] tosonny:
Is this enough?

Type "su"

Hit enter

Then type "chmod -R 551 /data/data/com.google.android.projection.gearhead/shared_prefs"

Hit enter

And the other ones are alternatives or do I have to make both?

Edit: forget it ...haven´t read properly.
[Android Auto General] tiho5:
Only the one you quoted. Read carefully, please.
[Android Auto General] tosonny:
And if there should any problems occur an Android Update (or new installation) should be enough to revert these changes?
[Android Auto General] tiho5:
Yes. This doesn't have anything to do with android updates. It affects only AA.

Or you can always uninstall and install AA again. You are only making a folder in the AA data folder readonly.

And if it works for you, it will also make it work forever even after you update AA.
[Android Auto General] tosonny:
Here we go. Will test end report.
[Android Auto General] tosonny:
Assume and hope this is the solution (this damn secret): easy to implement, literally only one function.
[Android Auto General] tosonny:
Thanks for the tip. So far things are looking good. If S2A is also shown tomorrow, then we have a solution.

And I wish all secret bearers that the S2A developers - my Russian friends ;-) - build something into S2A that you have to pay € 100. You definitely like doing that for free apps that are unconditionally and gladly shared with everyone and where the solutions (changed package name) are also delivered and gladly shared with everyone.
[Android Auto General] gullzway:
Is this a Rooted phone only issue?

Or possibly Android 13 issue? I'm still on Android 12 and plan to stay there.

I do not have the issue as I said on my non-rooted Pixel 6 pro. If I did I would probably have to root it cuz I can't change permissions on that folder.

I guess I should break out my Moto Ace 5G(Android 10) or Z3 Play that are rooted and see if they have this issue.
[Android Auto General] tosonny:
No idea. Don´t think it´s an rooted phone issue. I am on Android 12.
[Android Auto General] tosonny:
Peng, THIS DOESN'T WORK EITHER.

S2A disappeared over night.
[Android Auto General] zgfg:
For me S2A and Fermata also disappeared from AA yesterday evening but then, by reading which four files AA would tend to create (@tiho5 , post #2585), I additionally did

chmod -R 551 /data/data/com.google.android.projection.gearhead/files/phenotype

Btw, they more often/quick disappeared for me when I did several times connect the phone to AA in the car, disconnect, reconnect, etc

Then, after few times, AA would ve ' cleansed' by itself

Sometime today, after that chmod-ing 551 the other directory, I will test again more in the car again
[Android Auto General] tosonny:
Maybe some other files need also to be changed to "only read". Ich have several of this cache files for example in this folder.
[Android Auto General] tosonny:
I just uninstalled AA updates, deleted dates and cache again, installed updates to start again concerning this folder setup (read only). I deactivated (reverted) in AA Tweaker first...but obviously with no effect. Either depatching S2A in Tweaker or Patching has no effect because S2A is shown...without patching AA with AA Tweaker.
[Android Auto General] zgfg:
Did you test as with my post #2596
[Android Auto General] tosonny:
not yet, but will change permission for this file too now.

this file not folder by the way:

com.google.android.libraries.consentverifier#com.google.android.projection.gearhead.pb
[Android Auto General] zgfg:
For the whole folder:

/data/data/com.google.android.projection.gearhead/files/phenotype
[Android Auto General] tosonny:
this would not effect the files that are in the folder, would it? if you check the permissions you will see that the files in a folder still have the rights "write". I think what you do if you set a folder to read only is that I is not allowed to create a new file in the folder. but you can still change (write) the files that already exists. maybe I am wrong.
[Android Auto General] zgfg:
Its recursive chmode (-R) preventing creating and updating any file in the folder and subfolders
[Android Auto General] tosonny:
but root explorer shows still writing rights in the files?
[Android Auto General] zgfg:
If using root explorer, you had to checkmark Recursive (on your earlier screenshot you didn't)
[Android Auto General] tosonny:
Ah ok.

I just went to my car and tried a connection - after all these tries and changes in the settings - with my car. Had weird behaviour. Car didn´t connect anymore, then - after it has connected - S2A was suddenly gone. Restoring with TB didn´t bring in back ...was all very confusing. I have to try one step after the other again including the connecting to the car (not only on the phone). takes all a lot of time .... damn google.
[Android Auto General] zgfg:
Today I drove back and forth the whole day, I restarted the car and AA dozen times, but Fermata and S2A as I set them up yesterday evening, still continued to work in AA, they did not dissapear in AA screen)

(Previously I needed to reconnect AA two or three times, and S2A and Fermata would dissapear. Or they would dissapear over the six-ten hours even without using AA)

Hence, to prevent AA to remove S2A and Fermata (both were installed by EEAase), it was needed for me to set chmod 551 recursively to the folders:

/data/data/com.google.android.projection.gearhead/shared_prefs

and to: /data/data/com.google.android.projection.gearhead/files/phenotype

Btw, AA still created another folder (with four files in there):

/data/data/com.google.android.projection.gearhead/databases

but it did not affect S2A and Fermata

(That third folder can not be chmod-ed to 551 - when I tried, it caused AA to crash on start)

---

Also, as mentioned earlier, I used Swift Backup. Made a backup of AA, S2A and Fermata when I originally set everything, them (before preventing by chmod 511) when AA removed S2A and Fermata - I simply made Wipe Data for AA, followed by Restore
[Android Auto General] zagl81:
Hi everyone, with the last two updates of AA I get a black screen when I start S2A.

It is very strange that not even Waze works anymore, even this black screen of ours. Could it be that Google is also blocking all of its apps on rooted phones?

Are there any solutions? I'm using a stock Galaxy S7 Edge.
[Android Auto General] xls654:
try this commands run as root, then connect usb to car:

sed -i -e 's/inceptive/inceptxxx/g' /data/data/com.google.android.projection.gearhead/files/phenotype/shared/*.pb

am force-stop com.google.android.projection.gearhead

You can use tasker to run these commands after car bluetooth is connected when no usb is connected
[Android Auto General] tosonny:
Thanks, I will check how the behaviour will be next time and if I need this command. Hope not.
[Android Auto General] tiho5:
Glad you've made it. And I hope it sticks.

Now don't forget to make another backup after the changes of making those folders readonly.

Thanks for reporting.

Btw what is your android version?
[Android Auto General] zgfg:
Of course, I already updated the Swift backup

Xiaomi, MIUI 13, A12
[Android Auto General] tiho5:
Thaught so, but decided to anyway point that out for others to be aware. Thanks again. 👍🏻
[Android Auto General] tiho5:
@zgfg

Please, let me know your phone model and android version.
[Android Auto General] zgfg:
Xiaomi MI 5G NE

Android ver was commented above, so:

MIUI 13, Android 12

Actually, not the stock ROM, but Xiaomi.eu ROM (well known 'debloated' official Xiaomi ROMs)