Touch Screen stopped working after Google Play Service updated #352
Comments
|
I have a raspberry pi3 b+ and the official touchscreen 7" display which worked flawlessly until the point where touchscreen works only in the chrankshaft menu but not in Android Auto like it did until this point. Everything worked fine until Google Play Services updated. I have run into a Catch-22. I removed the Google Play Service updates successfully. Android Auto won't work unless Google Play Services is updated. Updated Google Play Services makes my touch screen not work in Android Auto. Phone: Umidigi Z2 Pro Android Version: 8.1.0 Build Number: UMIDIGI_Z2_PRO_V1.020180823 Raspberry Pi 3+ with 7" Touch Screen CrankShaft: Crankshaft OpenCarOS NG Alpha-5 2019-06-08 |
|
Same identical issue on my Galaxy Note 8 EU version. Android version: 9.0 Build number: PPR1.180610.011.hadesRom_OneUI_v7.0 Raspberry Pi 3+ with 7" Touch Screen CrankShaft: Crankshaft OpenCarOS NG Alpha-5 2019-06-08 |
|
Same issue on my OnePlus 5T Android version: 9.0 Raspberry Pi 3+ with generic 7" screen and digitiser ("USB_TouchController (eGalax TouchScreen)") X11: True CrankShaft: Crankshaft OpenCarOS NG Alpha-5 2019-06-08 EDIT: I've attached the debug.zip |
|
I got the same issue on my Asus X00QD Android version: 9.0 Raspberry Pi 3+ with 7" Touch Screen SKU:Z-0017 Crankshaft OpenCarOS NG Alpha-4 2019-03-03 Crankshaft : both not working. I was using the Alpha-4 wich worked using touchscreen on Android Auto and crankshaft . I updated to Alpha-5 and this has had no changes. |
|
needs some debug what was changed by play services.... |
|
the f1xpl/aasdk repository had an issue report a few days ago stating the sdk would no longer work with android auto due to a protocol buffer incompatibility. Something about AA using proto2 and aasdk using proto3 and play services starting to be more strict about the data it receives. Issue reports have been disabled on f1xpl/aasdk for some reason and the debug for that issue is no longer visible. Hopefully that helps a little. |
|
I tryed to do debug files I uninstalled Play Services updates on my phone and i catch some apk from apkmirror.com I first installed Google Play Services 17.4.55 (100400-248795830) version, i plug my phone to my rpi and Android Auto started and touch screen was working , i then using touchscreen returning to crankshaft-ng menu and do debug file using the button debug while usb still plug Then installed Google Play Services 17.5.28 (100400-252519129) version, i plug my phone to my rpi and Android Auto started and touch screen was working , i then using touchscreen returning to crankshaft-ng menu and do debug file using the button debug while usb still plug Then installed Google Play Services 17.7.84 (100400-252519124) version, i plug my phone to my rpi and Android Auto started but touch screen was not working anymore in AA so i cannot reach crankshaft-ng menu with my touchscreen so i unplugged my phone , launched a debug and pluged my phone right after , AA started and debug was still in progress . debug_working_17.4.55.zip |
|
Same identical issue on my Galaxy S8 Qualcomm Android version: 9.0 Raspberry Pi 3 B+ with Other 7" touchscreen CrankShaft: Crankshaft OpenCarOS NG Alpha-5 2019-06-08 |
|
Same identical issue on my Galaxy S7 Android version: 7.0 Raspberry Pi 3 B with 7" touchscreen CrankShaft: 2019-03-03-crankshaft-ng-299C16C.zip Touchscreen + mouse is working fine in the crankshaft menu's. but both stops working when connecting Phone. |
|
Same issue with my Nokia 7 Plus Android version: 9 RPi 3 A+ with official 7" touchscreen CrankShaft latest |
|
Same issue with my Xiaomi Mi6 Android version: 8.0 RPi 3 B+ with official 7" touchscreen CrankShaft latest |
|
Same issue with Huawei mate 20 pro RPi 3 B+ with 10.1" Waveshare touchscreen CrankShaft latest Touchscreen is working in the crankshaft menu's. And stops working when connecting Phone. |
|
Same Issue |
|
downgraded google play services to 17.1.22 and touchscreen went crazy random touches all over the android auto app works fine in crankshaft |
|
Same issue. CrankShaft: 2019-03-03-crankshaft-ng-299C16C.zip 7" screen + USB touch panel |
|
I am experiencing the same issue. Phone: Oneplus 6T Crankshaft: May 2018 |
|
A workaround is to open the application settings for Google Play Services and uninstalling all updates. Maybe a newer apk could be sideloaded, but the factory version is all that I tested. |
|
Same here on samsung A3 2017
Cant un install google play services
Op vr 28 jun. 2019 01:07 schreef Karthik Karyamapudi <
[email protected]>:
… A workaround is to open the application settings for Google Play Services
and uninstalling all updates. Maybe a newer apk could be sideloaded, but
the factory version is all that I tested.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#352?email_source=notifications&email_token=AB3IBWDIL4YJZI7AFOJ3RZTP4VB3NA5CNFSM4H2JVZ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYYTSKQ#issuecomment-506542378>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB3IBWDVQTLWTOZJIQJ4HG3P4VB3NANCNFSM4H2JVZ6Q>
.
|
|
I'll pull a debug later tonight, but I just got the update on my Google pixel 3 and same is happening to me. |
|
Same. Work around is to use "OK Google" and tell AA to play the music you want. now to reflash crankshaft as I figured my sd was corrupt. Thanks for the info everyone- I'll wait for someone smarter to post the fix...hopefully. |
|
Same here, Pixel XL after google play services update touch screen stopped working . |
|
Same issue: Phone - Samsung S9 Plus on Android 9.0 Definitively a problem with google play services update it seems. I will downgrade and report results. |
|
Im having issues downgrading my play services, with out formatting the phone its basically not going to happen so cant test this temporary fix. |
You have to disable "locate my phone" and google pay in the device administrator apps. Then you can remove the app updates but, even I disabled automatic updates and offline data for the app, it updates again after some hours. It is a very temporary fix. |
|
I got this working for the time, so I figured I'd share. First you'll need to download the google play services APK version for your phone, here's the guide I used (pay attention to the sub version numbers): I tried
At this point your phone will likely be freaking out with tons of notifications. I'd disable all sounds before you start, it gets really annoying with it buzzing every 2 seconds. Enable the app again, and install the APK you downloaded. If disable worked, it should install fine. Go to Google Store (before or after install) and disable auto update. I think side loading an APK might prevent auto update anyways. You'll need to re-enable all location services, but just open the Android Auto app and let it do it's thing. This works for me so far, we'll see if it tries to update itself anyways. I got this working on the 7" touchscreen, Raspberry Pi 3 B, standard release SD image, and a Moto Z2 Force phone. |
|
Just as a warning, rolling back google play services may break other apps or stop them from working correctly. |
|
Hey @modemlamer |
|
Cheers, mate! |
|
I have the greatest respect for the devs who develop open source projects and crankshaft in particular. Still this bug has been around for 5 weeks now and makes the software unusable, also a fix is around for those who are willing to dig deeper.. |
|
@miro279 I agree withyou. |
|
I'm sure he said that already in another thread. This project isn't dead. Just wait and be patient. There are guides and files to get it running. And yes, u have to digg into it. |
|
Don"t get me wrong but I think the lack of information about crankshafts future development is one if the reason why many people switch to the paid openauto pro version. |
|
@Maju3 @miro279 problem is, this is a currently a very small group of developers that cannot be too active. @htruong said himself in one of the open pull requests, he cannot handle it. It would be great to open this project to a more broad dev community with the ability to contribute. |
|
Sure. |
|
I really hate to say this but it seems to me that if you want quick bug fixes you need to have linux skills or you need to pay for openauto pro. |
|
Come'on it's summertime, he's maybe on Holiday, or maybe moving elsewhere... |
|
Android and raspbian are based in Linux, so yes u have to have decent Linux skills... Otherwise you better pay for a caraudio that has this Feature built in... |
|
Or maybe he lost interrest in this and thats it. |
|
@modemlamer |
|
@Maju3 is bring up some good points. As someone who's been following this project in mostly a passive manner, I know not to expect devs to get every bug squashed immidiately, thats not realistic and it's not fair to them. |
|
@gcharlie |
|
From what I've heard @htruong and @hawkeyexp are both somewhat busy with life. I've signed on to help maintain this project. Still waiting on write access to the repos, but hopefully we'll have a official build out soon. |
|
@abraha2d You now have access to the repos :) Thank you for offering help! |
|
Ok everyone, thanks for being patient. OTA updates are now available with the latest fixes! If your Raspberry Pi running Crankshaft-NG is connected to the internet, you should see "Update available!" in the top-right corner of the screen. Press it, and then press "Update OpenAuto" to get the fixes. (Also, fyi Crankshaft-NG still works with the new Android Auto interface, which is good!) |
|
Kevin,
That is great news, now will this be the only way to update in the future?
Or will there still be the file to download to flash to sdcard option?
Thanks,
Stargazzer77
…On Wed, Aug 7, 2019 at 7:32 PM Kevin Abraham ***@***.***> wrote:
Ok everyone, thanks for being patient. OTA updates are now available with
the latest fixes!
If your Raspberry Pi running Crankshaft-NG is connected to the internet,
you should see "Update available!" in the top-right corner of the screen.
Press it, and then press "Update OpenAuto" to get the fixes.
(Also, fyi Crankshaft-NG still works with the new Android Auto interface,
which is good!)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#352?email_source=notifications&email_token=AJ72UPYE4Y3YOSR2BCNQ6TDQDOATNA5CNFSM4H2JVZ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD32HWEA#issuecomment-519338768>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AJ72UP4AVMSTC6TQ35WXOVTQDOATNANCNFSM4H2JVZ6Q>
.
|
Kevis is also preparing a release: https://github.com/opencardev/crankshaft/releases/tag/csng-alpha5.1 |
|
@Stargazzer The plan is to release Alpha5.1 with the updates baked in. It's out here: https://github.com/opencardev/crankshaft/releases/tag/csng-alpha5.1 I haven't had the time to flash it to an sdcard and test it yet, though. In theory it should work, but it's my first time dealing with the crankshaft build system, and I'm not sure whether I've messed anything up. |
|
I'll test it today. I damaged something with a test to run to instances of
camoverlay in x11. Crankshaft doesn't run in x11 anymore since camoverlay
crashed... Very weird.
Op vr 9 aug. 2019 18:34 schreef Kevin Abraham <[email protected]>:
… @Stargazzer <https://github.com/Stargazzer> The plan is to release
Alpha5.1 with the updates baked in. It's out here:
https://github.com/opencardev/crankshaft/releases/tag/csng-alpha5.1
I haven't had the time to flash it to an sdcard and test it yet, though.
In theory it should work.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#352?email_source=notifications&email_token=AHGXD75A76ZCSPA7ZYQUSM3QDWMCFA5CNFSM4H2JVZ62YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD37FFMY#issuecomment-519983795>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHGXD74GDM53SIKH6FS2HMTQDWMCFANCNFSM4H2JVZ6Q>
.
|
|
I will test, give me around an hour |
|
Can confirm, the update fixed the touchscreen in open auto for me. Essential PH1 |
|
Personally tested Alpha 5.1, and it seems to be working fine (at least USB mode, hardware incompatibility prevents me from testing WiFi mode). For those of you having issues with openauto crashing in X11 mode, see #366. Specifically this comment. |
This seemed to work for me. |
and others
If you need support: Please post on https://www.reddit.com/r/crankshaft/ as this is a bug tracker, not a support forum.
Note: Reporting issues not based on official published builds will be closed without any comment.
What phone do you have?
What OS version?
What crankshaft version?
Steps to reproduce the bug, if you're planning to report a bug. Please indicate whether the bug is always repoducible.
Please provide any further information that you might find helpful if available.
Starting with pre4: Boot into dev mode (can be selected in settings).
Reproduce the possible bug. Create the debug logs by pushing the grey button on bottom of screen.
Add the created file (/boot/debug.zip) to the issue.
Warning: if you have configured wifi passwords they will be blanked by script during creation.
We can't make absolutly sure you passwords are removed so do a personal check of the files inside the zip.
The text was updated successfully, but these errors were encountered: