What settings are you using on your phone and Screen2Auto app, because everything works fine with my Samsung s22 ultra (unrooted) with ford sync aside from the touch screen responsiveness. I cant scroll or tap using the car screen.
I Have the same phone, galaxy s22 ultra on FIAT TIPO and touch is good. You mus enable on phone alternative touch, button number two, and enable scree2auto in accessibily settings on the phone-
My Pixel 6 Pro works great. I also have Ford sync in my Maverick and have no issues with touch screen. I was referring to all the other posts about people having issues.
I had this issue on a particular phone a while back, I don't even remember which phone.
Where do you enable alternative touch? I already have screen2auto accessbility settings turned on
Update: Nevermind I found it in settings. I will see if this works and let you know.
Update 2: I changed alternative touch to button 2 and I still do not have touchscreen responsiveness on the car screen.
What kind of Magic does this? I am a bit scared of downloading and installing this...For those who are having trouble with touch response:
If you're using Magisk, install the Magisk module su_connector (download here: https://www.mediafire.com/file/7dduzlef86y7ppj/SU_Connector.zip/file). Reboot after installing.
You should then turn off alternate touch in S2A. The touch response should work normally in S2A after installing this, and not ultra-sensitive like it is with alternate touch turned on.
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:
and to: /data/data/com.google.android.projection.gearhead/files/phenotype
Btw, AA still created another folder (with four files in there):
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
Today's test: everything works (connection to the car, S2A remains visible).
Set chmod 551 recursively to the folders (just use root explorer and make sure "also include subfolders" is checked):
Thanks to everyone who went on a "scavenger hunt" with me ... which was unfortunately necessary thanks to our secret bearers.
It depends where it shows for you
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).
Lucky Patcher actually calls it "Cloning".