Open ShawnBSST opened 2 years ago
Did you happen to try disabling RT Audio? It is in the settings of the openauto tab. It should default to QT Audio without it.
What resolution is your 11.9" screen?
Also, what does the console say while dash is running? Does it say something like "end of stream" and/or "no frames to..."?
As noted in #124 I wouldn't be terribly surprised if the whitescreen is back... The core of whitescreen issues (up until this point) has been a combination of https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1056 (colorimetry probing) and https://github.com/raspberrypi/firmware/issues/1673 (resolution change event support in pi firmware).
For a bit, the whitescreen workaround I implemented (remove custom colorimetry from the h264 bytestream) worked fine on my phone, but one day stopped working with no Pi changes - I assume google changed something in Android Auto/Play Services.
For my phone, I was able to work around it by just overriding colorimetry as stated above (which already indicates to me that the whitescreen workaround I implemented is being circumvented by some Google change - probably multiple colorimetry packets or something).
@ShawnBSST
I would expect that this same fix would apply to more than just my phone though - make sure your system is fully up to date - both via rpi-update
and apt-get upgrade
, as the resolution change capture event support was only "recently" added to the pi repos.
I'm away from home right now, but plan to dig more into this when I get a chance. I have good ideas of where to look.
Robert,
Thanks for getting back to me so promptly.
I have a large assignment due and need to have it all completed these next few days.
I'll give your email the attention it deserves, read the links, and get back to you.
Many thanks,
Shawn
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Cole Brinsfield @.> Sent: Wednesday, May 25, 2022 4:38:33 AM To: openDsh/dash @.> Cc: Shawn Thompson @.>; Mention @.> Subject: Re: [openDsh/dash] White Screen (Issue #125)
As noted in #124https://github.com/openDsh/dash/issues/124 I wouldn't be terribly surprised if the whitescreen is back... The core of whitescreen issues (up until this point) has been a combination of https://gitlab.freedesktop.org/gstreamer/gstreamer/-/issues/1056 (colorimetry probing) and raspberrypi/firmware#1673https://github.com/raspberrypi/firmware/issues/1673 (resolution change event support in pi firmware).
For a bit, the whitescreen workaround I implemented (remove custom colorimetry from the h264 bytestream) worked fine on my phone, but one day stopped working with no Pi changes - I assume google changed something in Android Auto/Play Services.
For my phone, I was able to work around it by just overriding colorimetry as stated above (which already indicates to me that the whitescreen workaround I implemented is being circumvented by some Google change - probably multiple colorimetry packets or something).
@ShawnBSSThttps://github.com/ShawnBSST I would expect that this same fix would apply to more than just my phone though - make sure your system is fully up to date - both via rpi-update and apt-get upgrade, as the resolution change capture event support was only "recently" added to the pi repos.
I'm away from home right now, but plan to dig more into this when I get a chance. I have good ideas of where to look.
— Reply to this email directly, view it on GitHubhttps://github.com/openDsh/dash/issues/125#issuecomment-1136305988, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZJZ7WPKWAXG7OBET3GYNZTVLUO2TANCNFSM5WY6M2VQ. You are receiving this because you were mentioned.Message ID: @.***>
Good morning Gents,
Sorry for not getting back sooner, life has a bad habit of getting in the way.
I started digging around GSTVideoOutput.cpp and noticed my #defines for the PI versions were not correct. As I mentioned I'm running a raspberry PI 400 (the one with the PI inside the keyboard). I managed to trace to the CMakeList in openauto where it checks the version of PI and sets the #define. I calculated that mine is version 19 and changed the it to the following and now the openauto app is running.
if(RPI_MODEL EQUAL 19) message("Raspberry Pi 4 Found") add_definitions(-DPI4) endif(RPI_MODEL EQUAL 17)
I noticed you have a similar line in opendsh; I hope to get some time today to modify it as well and rebuild the whole system. I probable should change the line to some like ...
if(RPI_MODEL GREATER_EQUAL 17)
I'm happy for you to close this issue.
Thanks for your help, Shawn
Urgh, of course it's a define issue. I've had a revamp of the install script/cmake on my list for awhile now, because there's a lot that changed with pi firmware and functionality with the release of bullseye. This just increases the priority of that for me. Going to leave this open until we have the update install/cmake in the repo, because it will serve as a good reminder.
Thanks Cole
Get Outlook for Androidhttps://aka.ms/AAb9ysg
From: Cole Brinsfield @.> Sent: Tuesday, June 7, 2022 1:25:44 PM To: openDsh/dash @.> Cc: Shawn Thompson @.>; Mention @.> Subject: Re: [openDsh/dash] White Screen (Issue #125)
Urgh, of course it's a define issue. I've had a revamp of the install script/cmake on my list for awhile now, because there's a lot that changed with pi firmware and functionality with the release of bullseye. This just increases the priority of that for me. Going to leave this open until we have the update install/cmake in the repo, because it will serve as a good reminder.
— Reply to this email directly, view it on GitHubhttps://github.com/openDsh/dash/issues/125#issuecomment-1148152650, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AZJZ7WI34BP6A6UDYNIPO73VN26LRANCNFSM5WY6M2VQ. You are receiving this because you were mentioned.Message ID: @.***>
@icecube45 do you have any update on this issue?
@c0c4i it all should hopefully be worked around once I get openDsh/openauto#29 and #126 merged in, but I'll need probably another week to get that done (I moved mid June and have been dealing with furnishing and all the fun stuff that comes with). If you hop in the slack, I can point you towards instructions as to manually getting it up and running until I get those merged in.
has this been resolved now with icecube's changes?
Issue
Thanks Gents, for what look like a pretty terric product.
I have installed the latest code and built with the latest install.sh This all builds fine and runs with the exception of getting a white screen on the PI (in the Android Tab) when connecting the USB cable to the phone. My phone in the status tells me I'm connected but thats it. If I turn on spotify I can see the output from the terminal window of the song that is playing.
I have read through some of the other issues, added "capssetter caps="video/x-h264,colorimetry=bt709"" to the code as per #124 and rebuilt the code and still the same. No difference.
I have a Google Pixel 5 running the latest Android 12.
I do differ in that my screen is a Waveshare 11.9in touch screen. The full raspbian OS in 32 and 64 bit version runs well with the touch screen. I am also running a PI 400 which I assume is a PI 4 just in a slightly different physical layout ... I chose this because it will work with the screen when it gets assembled.
Is there a check list I need to go through? I'm reading posts about being in developer mode, usb debug on etc ... all of which I have tried to no avail.
I hope I am not wasting your good time with something obvious.
Many thanks, Shawn
Make sure you are running the latest version before reporting an issue.
Hardware
Installation Method: Install.sh or Image
Description of problem:
Problem
Expected Result:
Result
Problem-relevant steps to reproduce:
Traceback (if applicable):
Additional info:
Additional Info