Nothing happens when connecting phone / RPi connected to HDMI screen #1
Comments
|
Please provide with the Qt version you're trying to compile aasdk/openauto with, so we can debug this problem further. Openauto's author requested you to get the Qt lib from apt and try to compile it against the official blessed way. If it only happens with this distro but not Open Auto, I'm happy to investigate. Otherwise, you should consult with openauto project. |
|
I'm at work now, but I'll check when I get home. But the first i tried was the crankshaft image downloaded on 2018-02-25. RPi 3B, using a plain HDMI screen (I've ordered the official 7" touch screen, so will also test as soon as I get it) OxygenOS 5.0.1 edit: I'll file a bug with the openauto project, since it seems to be more related to that. |
|
Actually, I just did a fresh install and compile of openauto etc, and it works. So it seems to be something in the crankshaft image... |
|
Thanks for reporting back @vb4life - I will figure out how to get an android phone that exhibits the problem and correct it in the next version. |
|
Let me know if you need any logs, or if you want me to test anything...
Den 26 feb. 2018 20:22 skrev "Huan Truong" <[email protected]>:
Thanks for reporting back @vb4life <https://github.com/vb4life> - I will
figure out how to get an android phone that exhibits the problem and
correct it in the next version.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AHbcH5rzgTrJAyLp5ekM4kWMzAgvRFJcks5tYwQxgaJpZM4SScBn>
.
|
|
I just recieved the 7" display and case, and after trying again with Crankshaft (same image), the phone connects just fine. So it might be an issue when using an external screen? My first test was with a HDMI -> DVI cable, so it might fail on the audio connection. So you can probably close this issue, or modify it.. |
|
Oh - that's right. I know it is doing something funky with the HDMI connection. HDMI doesn't work yet. So that mystery is solved. :) |
htruong
changed the title
|
Wait, you are connecting the PHONE via HDMI? Or do you mean the Pi is outputting HDMI and the phone is connected to the Pi via USB? |
|
vb4life used the HDMI touchscreen instead of the official DSI one. Bad title on my end. |
|
Oh, weird that would cause an issue. I wonder if forcing an X11 build would work for the HDMI screen (for the time being) |
htruong
changed the title
|
I connected the PI to a normal (non-touch) screen. The screen also only had DVI connectors, so I used a HDMI -> DVI cable. But using the official 7" screen works perfect, though.. :) |
htruong
added
the
custom-hardware
|
For anyone having difficulties with custom HDMI screens, please try Starting Crankshaft in X11 compatibility mode on image 2018-03-05 or later. |
|
As of now with the introduction of the X11 compatibility mode, I think this should be resolved. Plus vb4life got their screen to work, so I'm closing this ticket down. Please feel free to comment and request to open a ticket if you feel this thread should continue. |
This is an awesome idea, but it doesn't seem to work for me.
I've flashed the image and can boot the RPi 3 with no problem. The screen comes up, waiting for a device to be connected. However, when I connect my phone (OnePlus 3), Android Auto starts on the phone, but nothing happens with the UI on the PI.
The log shows some errors, but nothing that tells me anything useful:
Any idea on what might be the issue?
I also tried compiling aasdk and openauto from source, but it is the same error..
The text was updated successfully, but these errors were encountered: