suddenly "Lock" #680
Comments
|
Same problem here. |
|
Facing the same problem (with both wired and wireless connection), when I used crankshaft today after a couple of weeks. Also phone screen showed a message, something like installed app in Android auto does not work with wired connection... |
|
Same! Pi 4, Galaxy Flip 6, AA-Wireless (but also doesn't work with a direct USB connection to the phone). Tried a clean install of crankshaft-ng without any additional changes with the same result. I'll try to see some logs as soon as I can find the time to take my pi within range of my home wifi to run some diagnostics over ssh. Note: the Edit2: I've bumped my Android Auto app version to |
|
Same with Samsung Galaxy S24 Ultra/ RPi3B+. |
I hadn't even thought to try that, but audio comes through for me, too. In fact, if I play a Youtube video on my phone, the audio from that comes through to the Crankshaft device. Somewhere in my travels (but which I have now lost track of), I saw a reference to turning on "allow videos while driving". If I ever find that again, I'll try it since the AA projection is just some sort of video stream (I think). |
I'm was also on Android Auto app version to 12.9.143734-release.daily, but just now I took an upgrade to 12.9.143804-release.daily. No change for this problem. Have you tried downgrading yet?
|
|
The logcat on my phone when trying to connect to Crankshaft includes this line: I don't know what it means or what to do about it, but it seems like it's probably significant. FWIW: |
|
I have disabled the Android Auto app on my phone and then deinstalled all updates. At the same time I also completely reinstalled crankshaft on the Pi. |
|
That encouraging! I wonder how you got to that version instead of one of the 12.9.* versions that I have. I was in the beta program for AA, but leaving the beta program still left me with the 12.9.* version I reported earlier. If I remove all updates for the AA app, it leaves me with something that identifies itself as a "stub" that can't connect to anything until you follow its prompt to update it. I figured that's something that Google changed when they made AA a hidden app a while back. My phone is a Google Pixel 6a. What's yours? |
|
Ho ho! I guess normal app activity is that it wouldn't update to an earlier version just because I left the beta program. I uninstalled updates to AA and then applied fresh updates, leaving me at For others who had the same problem, what AA versions were you using? |
|
FWIW, I reported this in the AA community help forum, but I don't know if that will get any attention. |
|
I uninstalled the Android Auto updates and it is working again too. I'm back to 12.6.643244 on Android Auto and so far so good. |
|
@dcolecpa Were you on the app beta before you uninstalled the AA updates? |
|
No. I was on "2022-09-11-crankshaft-ng-66525ef-pi2.img". |
|
@dcolecpa I meant the beta channel of the AA app on your phone, not Crankshaft. |
|
Sorry, I misunderstood. No I wasn't on beta for the Android Auto. |
|
I had the same issue since about a week. Out of the blue, didn't change a thing that might have caused issues. After removing the updates of the Android Auto app I'm also back on 12.6.643244 and now all is working fine again. It looks like something changed in the 12.9 version that crankshaft didn't like? |
|
Same for me, running crankshaft for years and it broke this week. Let's see if we can fix this somehow |
|
Same here. Many-year user. Just broke recently. My AA version that broke it was 12.7.643414. At the time my girl still had 12.6.643254, and her phone still worked consistently. Her phone has since updated to 12.8.643614 and no longer works either. |
|
Pressing "uninstall" in the play Store removed updates and that made it work again for now. Quick solution for now, but not for the long term |
|
The folks at Bluewave Stuidos (OpenAuto Pro) also seem to have this issue, as they stopped selling it and locked down the forum. |
|
I figured that was the reason. I was actually considering purchasing a license if their forks of openauto/aasdk would have been more up to date than the public ones. But alas that was not the case. I tried building opendsh to see if that would work for me. So far no luck (but this has to do with my unfamiliarity with the project as well as my lack of time since I became a dad). For now I'm driving without only audio nav over bluetooth, but I hope I can retry opendsh and get a working build to try this time... |
|
Add me to the list of "latest AA not working for me". Multiple phones: Found it wasn't working for my pixels; crankshaft would say it's connected but wouldn't go into android auto. Motorola wasn't up to date at the time so it worked, then I updated AA on it and then had the same issues. Uninstalled updates and wanted to do the first time setup. Uninstalled updates on my pixel 7A (this is my main phone) and it started working again like it's a new car, then said something about updates which I did and has been working since. App details |
|
My phone updated to 12.7.643414-release, and now Crankshaft is broken in this way again. Things still work with my factory AA headunit (via an AAwireless dongle). @DJFliX You mentioned opendsh. I built and tried that. Same symptoms as for Crankshaft, which is not surprising since it uses the same openauto substrate AFAICT. |
|
I'm going to chime in and say I have the same issue. I had to downgrade to Android Auto 12.4.6. I'm running Android 11 on a Sony Xperia 5 II. I'm willing to provide any logs and test any configurations. I loved this project for years and want to keep using it! |
|
Good to know! I am still surprised by the lack of reports of AA being
broken for Opendsh users on their Slack. But I suspect AA is a secondary
feature for most Opendsh users whereas for Crankshaft close to 100% of
users AA is the only thing they use crankshaft for.
I have downgraded to 12.6 but am experiencing frequent disconnects. Since I'm using AAWireless the reconencts do happen automatically but this does mean 20 second interruptions of music and nav which isnt great. I had never experienced this before...
…On Tue, 24 Sept 2024, 21:08 WJCarpenter, ***@***.***> wrote:
My phone updated to 12.7.643414-release, and now Crankshaft is broken in
this way again. Things still work with my factory AA headunit (via an
AAwireless dongle).
@DJFliX <https://github.com/DJFliX> You mentioned opendsh. I built and
tried that. Same symptoms as for Crankshaft, which is not surprising since
it uses the same openauto substrate AFAICT.
—
Reply to this email directly, view it on GitHub
<#680 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABJ6DNJ2O7N6U54EUIP2HQLZYG2D3AVCNFSM6AAAAABOKJIW4KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZSGEYDSNZWGQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
It seems odd to me, too. I suspect there may be more to it than just the AA app version, like maybe some other dependent library or something that varies from phone to phone. For the last couple months (not sure how long) my factory AA headunit, which I also use with AAwireless, occasionally stalls with some message about losing bluetooth connectivity. It resumes after a few seconds. It's been rare enough that I just put up with it. (Before I learned more about how AA works, I blamed a lot of things on the firmware inside my head unit. Now that I know about AA projection, it seems like almost every glitch has to be in the AA app on the phone.) |
|
I make a point to disable auto updates as much as possible. I also haven't changed any crankshaft settings in months. So there's only two things that could have changed on my phone to break things.
I only noticed crankshaft broke when I manually updated AA but it's possible changes in Google services play a role in the incompatibility. |
|
I also have same issue I used wireless Android auto using CS few months ago. And I tried to connect again yesterday, it didn't works. |
Well before I found OpenAuto, I had KODI on my Raspberry Pi and had written a number of Python scripts to interact. I had two raspberry pi's, one had a canbus hat listening to the data and sending it upstream to my main car pc. This collected CanBus information and uploaded telemetry into the cloud where I had a companion app to show me details. My goal is to recreate a similar ecosystem tacked on to OpenAuto, hopefully with the advantage of using Vendor Extension channels so the companion app can simply upload everything itself from the phone rather than needing a WiFi router in the car as well! I then hooked it into the Google Assistant so you could ask questions about your car. |
@Geekyadz Sorry for the late reply. But yes, I do still have the issue. I've in the meantime had an android update and AA update, but that did not solve the issue. I also have an AA Wireless, and you mentioned it only happened to you with it. Unfortunately mine doesn't work either directly via the USB cable. (Doesn't work as in YTMusic and GMaps don't work, I've not tried other apps) |
|
@TobiasDeBruijn I had that issue when connecting via USB, I had forgot to disconnect from the Crankshaft hotspot. |
|
That doesn't seem to be the issue for me. I'll give @sjdean's new works a shot once they're released. Hopefully that can fix it 🙏 |
|
I've got my code checked in on my repositories - updates to AAP 1.6, rework of bluetooth handling, physical screen geometry calculations and more. Please do check my repositories and I'll look to get some binaries on there over the weekend. More than welcome to merge my code into Crankshaft-NG |
|
@sjdean: can you elaborate on the rework of Bluetooth handling? I'm very excited for your update and to have a working Crankshaft again. |
|
@sjdean submit a pr and we'll review and merge |
|
@matt2005: Is there a reason why posting to the Crankshaft subreddit is restricted? Would you mind opening it for posts again? |
|
Thing got worse as now AA forces an update, meaning it's not possible to use the older version of AA to bypass the issue... |
So why not use the image that @SonOfGib has made instead of using this version which has been known to be broken since September? |
To be honest I'm new to github and it's been really hard to find any information on how to handle the problem and any possible solutions. I've head something got fixed but wireless AA didn't work. Is that the case with @SonOfGib? |
As far as I'm aware their one is working: https://github.com/SonOfGib/crankshaft/releases/tag/v2024.10.30.1 Personally I don't use wireless Android Auto but with all due respect there's only one way you are going to find out and that is to try it. Obtain another memory card if you don't want to overwrite your existing memory card. But I am using that image and it works for usb for me |
|
Well, 😿, I've had to throw in the towel on trying to get this project working. There still seems be a lot of interest, so I hope everything is eventually resolved. When I opened this issue way back in September, it was because i was working toward retrofitting Android Auto into my wife's car. As time wore on, my goal was to get it going in time to be a Christmas present for her. Obviously, that time is upon us. During the November sales, I bought a 3rd party aftermarket Android Auto display gadget. Now, I could have waited and found a different Christmas gift, but I kind of doubt this project will ever have a high enough WAF. I would lose serious marital cred. It would be OK for a tinkerer like me, but my car has Android Auto built in by the factory. In case anyone is wondering, the aftermarket display I bought is this one: https://www.amazon.com/dp/B0CGQTQDVD I was reluctant to go for one of these company-I-never-heard-of gadgets since they don't have a great review reputation. But, I took a chance. I believe my gamble paid off. I unboxed it and used it for a few minutes to see how it went. The physical construction is nice, the screen responsiveness is comparable to my built-in Android Auto, and the setup for wireless was very simple (bluetooth pairing, ba-da-boom, ba-da-bing). Of course, I'm using the latest AA app version. In other words, WAF should be pretty high. I know fellow followers want this project to work for multiple reasons. Some can't or don't want to gamble a hundred bucks on a no-name device. Some just like tinkering and the rewards that brings. I empathize with all of that, and I hope those who continue down this project's trail will get satisfaction. I'll be following it mostly from intellectual curiosity. |
Hmm, although my Amazon order page took me to the 9 inch model, I actually bought the 7 inch model from the same company. I think it's this one: https://www.amazon.com/dp/B0DDL21SMM. Must be some database glitch over in Seattle. |
Don't throw in the towel. I've got everything working from my end, using Bluetooth/WiFi Projection on my Google Pixel 8 (so Android 15 and latest Android Auto etc). Been using for a few weeks. There's some artefacts in audio due to I think either CPU in processing WiFi data on the inbuilt raspberry pi wifi, or because it's running in WiFi 2.4Ghz mode instead of 5Ghz. As I've said previously, I've completely overhauled the ProtoBuf files and tidied everything up a lot. If anyone wants any builds let me know. Code is available for building from my repo. I'm working on a re-brand as I don't want to tread on the toes of Crankshaft, so the next elements I;m working on: Upgrade to Qt6 (this removes a lot of the Qt Bluetooth handling and we'll need to step back to using DBus integration for monitoring Bluetooth Connectivity) |
|
@sjdean this sounds really promising and I'd love to try this. Can you perhaps provide binaries for Pi3, or otherwise some instructions on how to compile? Thanks in advance. |
The thing that I'm afraid of (for WAF) is that something on the Google side will break it again, leading to a possibly months-long reverse engineering voyage of discovery to get things back on the air. That would be sort of OK for me, but not for Mrs. Me. |
|
@wjcarpenter I hear you, although I had over 2 years without updating before this bloody lock issue! Which is reasonable (possibly not for waf but she might have got a new car in that time😂) @sjdean keen as mustard to check out your build, I'm on a pi4 how can I get the good stuff? ( Not built it myself yet but I'll look at this, if you have any bins I'm keen) @SonOfGib 's pie3 bin worked for me on a pi4 but I suffer reasonably frequent lock ups and Google maps not working (I use Waze so not so bad) so still looking for something longer term. My wife's 6 year old golf has AA, I can't work out how it gets away with never being updated given the Phone app updates constantly.... |
For a while, I though that maybe the reported protocol version was the key, with the app side having backward looking behavior. However, IIRC, I did an experiment of setting that to 1.1 or something and it made no difference. My next thought was that maybe the car manufacturer and model info triggers some kind of lookup. For official partners, Google could know their capabilities and react accordingly. I tried faking that info, but I don't know what any official partner strings might be, so I was just guessing. Finally, since 98% of the logic on the head unit side is in the protobuf handshaking stuff, and the other 2% is just rendering whatever the app sends over, and since (I think) Google provides the official partners with a library for the 98%, the app could in theory update the head unit with a new version of that library. Or, it's something completely different. 😄 |
|
Hi excuse my bad english I use the translator. |
I wasn't able to get AAWirelsess (gen 1) to work. |
You're running this on what exactly? |
Raspberry Pi 2 Model B |
With a USB WiFi adapter, right? |
Using it with this one . Just plug it in and It handles wireless AA. |
|
Hello everyone Impressive how you managed to locate the issue origin and all the work done.. Like everybody else, I had the lock issue with my one plus 8t (android 14). For a weeks weeks, it worked nicely when Android auto was downgraded to 12.6.633244 I've just tried the SonOfGib release on my pi4.. No luck so far. I also have an older one plus 5t, android 10 : android auto 13.3.644654 is able to connect ! Any suggestion ? Does the SonOfGib release works for you guys on android 14 ? Thanks |
Android 14 is what I tested on. I haven't tested it lately as I've been working on updating Crankshaft to bookworm. But when I did that original testing I used AA 13.1 and android 14. |
Google Pixel 7a Android 15 here and using a raspberry pi 3b and all working with latest updates of android auto |
|
Maybe an oldest version of AA like 13.1.xx ? |
|
Tried some AA 13.1 and 13.2 Don't want to switch to one of these chinese headunit ; I just (this summer) bought a new touchscreen LCD and 3d-print a good looking adapter for my car... That's so frustrating ! |
and others
Discussed in #678
Originally posted by wjcarpenter September 1, 2024
I started tinkering with CS about a month or so back. I fired it up and used my mouse to operate it while displaying over HDMI. Everything looked pretty cool and stable. I got a nice touchscreen, bolted my RPi 3B+ to it and repeated the experiment. It worked great, and the touchscreen stuff worked just dandy. I plugged in my phone (Pixel 6a) and up came AA. It behaved the way I expected.
Time went by while I was waiting for additional mail order parts, 3D printing a case, and doing unrelated things. With everything in hand a couple days ago, I repeated my experiments, including plugging in my phone for the first time in a few weeks. CS reacted by throwing up the word "Lock" in the upper left corner and ignoring touches or mouse clicks on the screen. When I unplug my phone, CS goes back to its normal responsive self.
Thinking I might have tweaked something the wrong way, I started over with a freshly downloaded image file. Same "Lock" symptoms. I also locally built the image and got the same "Lock" symptoms. I know the generic advice is to check my USB cable. I've tried about a half dozen different cables between my phone and CS, but I don't really think that's the problem.
I'm just starting my spelunking in the source code, but I wonder if someone has already been down this path and figured it out. (I'm not providing any logs at the moment because I don't want to bother someone into spending time on this unless it's something they already have ideas about. I can provide them if desired.) My hypothesis at the moment is something changed in an Android monthly update, and now the handshaking between my phone and CS is getting something confused. Things definitely get as far as CS recording my phone info into the /tmp/android_device file.
The text was updated successfully, but these errors were encountered: