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. |
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 ! |
|
@SonOfGib Also I've noticed that when i uncheck the music so it comes from the phone, every couple of restarts it puts the ticks back in the checkboxes. |
|
I never had working wireless AA. I commented earlier (somewhere, don't remember where) that I was under the impression that the only form of wireless AA with crankshaft was to use the headunit server stuff mentioned in the wiki. If you had it working some other way then that was not a feature I was aware of (unless you are talking about openauto pro, which was a separate project from crankshaft.) I am not currently looking into the wireless stuff, and I don't have much time (or skill tbh) to devote to this stuff, so I work at a snail's pace :) |
I really appreciate you efforts 🙏 To get Wireless I just plugged this thing in one of the USBs of the Pi and It just worked. |
|
Ok, yeah I don't know why there would be any issues with one of those dongles, but I don't have one to mess with sorry. |
|
Good news. I had an idea about open source aawireless and I came across someone who already thought of this. Repository: https://github.com/nisargjhaveri/WirelessAndroidAutoDongle. |
|
I'm the one on that Issue. And I can confirm I have a working setup where the dongle is running on the same pi as OpenAuto-Pro. I'm finalizing my details and will post everything I needed to make it work. :) |
I struggeled with the AA Wireless (Generation 1). I could get AA to work, but it semes there was no 'network'. Google maps would get stuck on loading a route and YouTube Music wouldn't player anything. What firmware version of the AAW are you using? |
Just double checking ... Your phone was on mobile data, right? AAwiteless is talking to your phone over a private Wi-Fi hotspot. |
|
Yes! Before AA did their update it worked amazing. Something in between the new AA version and crankshaft broke something. |
|
@KreAch3R add new important commits (thanks). i try burn a https://github.com/SonOfGib/crankshaft/releases/tag/v2024.10.30.1 in my sd card @SonOfGib (thanks). and I will follow the steps described in the new readme. https://github.com/KreAch3R/aa-proxy-oap |
Yes guys, I have updated my repo. I installed my test sdcard into my car and it works. Check the screenshots and the photos on the repo. The only thing missing is to follow my own guide with the former sdcard and check if I miss something, which I will do in the next days. FYI, my method specifically targets the closed-sourced OpenAuto-Pro installation. For the opensource Crankshaft here, someone should really implement the necessary wireless changes into the crankshaft code itself, it's a shame that the code exists but it's not mainlined yet. |
Good to see you here since the OpenAuto Pro forums went down. My truck has been off the road for the past two months with a blown engine, I finally got it back yesterday only to find that the old version of Android Auto that had been working was now forcing an update. Your AA-Proxy-OAP project looks promising, going to give it a try. Thank you for all of your work! Russ. |
@KreAch3R I've tried to apply the two patches included with your aa-proxy-oap project with both: patch -p0 < ../0001-Backport-and-apply-patches-for-Android-Accessory-mod.patch ...and... patch -n -p0 < ../0001-Backport-and-apply-patches-for-Android-Accessory-mod.patch but I always get: patch: **** Only garbage was found in the patch input. I've also tried "git apply" but that gives "unrecognized input". Any thoughts on what I'm missing? Thanks! |
|
Sure I'll work on getting prs up to the repos. Looks there are a few issues people have been experiencing which is why I didn't initially. I wonder if the changes I made for the wifi service interfere with the aa wireless dongles (as reported above.) I could pretty easily add a config option to disable the bluetooth and wifi services in openauto. |
|
@SonOfGib I've pr'ed a few recent changes and added you to the dev team. |
Happy New Year guys. I uploaded new commits to the repo that should adress your patching issue. I am also working on somehow bundle it all in release package to be easier to adopt. |
|
Just for anyone listening here about my Check the new instructions in the repo: https://github.com/KreAch3R/aa-proxy-oap I tried to find a way to bundle the kernel into a .deb file but the raspberrypi-kernel situation is a bit hacky and all over the place because of the fat32 boot partition, so there is no simple solution to bundle the files. So manual install it is. Let me know if you run into issues. And please, backup first! |
|
I saw the new release for 20250104 and I was wondering which binaries we should be using for different Pi boards? |
Which other board are you using? Raspberry Pi 3/3+? I can try to build those as well. |
I have 3B+. Thanks! What board are the 20250104 releases for? |
|
try 20250105 use the armv7 for pi2, armhf for everything else Matt |
I'm not sure now if you were talking about Crankshaft or my modification/hack, because we have almost same date releases. In order to not confuse the users that follow this mailing list, I'll just say that I have built the rpi3 kernel blindly and I uploaded to my repo with instructions. If someone from here wants to use it, please come over to that repo and post an issue there, to keep the threads separate. |
Sorry for the confusion, I was talking about the Crankshaft release. |
|
This is expected to be resolved in 20250111 |
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: