search

openDsh / dash

Join us on Slack! https://join.slack.com/t/opendsh/shared_invite/zt-la398uly-a6eMH5ttEQhbtE6asVKx4Q
GNU General Public License v3.0
259 stars 80 forks source link

[SOLVED MAYBE...] Strange issue on RPi4 and Android 10 #17

Open speleolontra opened 4 years ago

speleolontra commented 4 years ago

Hi, I have a RPi4 + official 7 inch screen. I have cloned the repo with "git clone https://github.com/openDsh/dash.git" and installed with "./install.sh". "./ia" command starts correctly, but when i connect via USB C my Motorola One with Android 10, nothing change (with a redmi 8 it run and starts Android Auto). The strange thing is that after a few minutes (phone usb connected) when RPi screen turns off in sleep mode, starts AA on phone and if I touch the screen i see maps from AA. someone has the same behavior? Is there a log file? thanks Lontra

rsjudka commented 4 years ago

If you run ia from the command line you should be able to see the log output.

Hmm so it works with one phone and not the other? Do you have the same version of AA installed on both?

And after you wake the screen back up, are you able to to use AA, or you just see the maps screen?

Just to verify what you're seeing... Do you see the "connect device to start AA" or does it turn into a white screen after you've connected your phone?

speleolontra commented 4 years ago

If you run ia from the command line you should be able to see the log output.

Nice, i will try...

Hmm so it works with one phone and not the other? Do you have the same version of AA installed on both?

There are my tryes: Xiaomi Android 7: phone is recognized and all is ok but for 2 time without a reason RPi reboot. Not important is my neighbor phone, only for testing. Xiaomi Android 9: my wife, it all ok. My Motorola One Android 10: connect only after screen sleep.

And after you wake the screen back up, are you able to to use AA, or you just see the maps screen?

Yes, I'm able to use AA and IA, not yet in car...

Just to verify what you're seeing... Do you see the "connect device to start AA" or does it turn into a white screen after you've connected your phone?

I see "connect device to start AA". Thanks

speleolontra commented 4 years ago

HI, this is the output LOG from command line...

qt5ct: using qt5ct plugin qt5ct: palette support is disabled qt5ct: custom style sheet is disabled [2020-09-18 13:36:15.281344] [0xb0d56010] [info] [OpenAuto] [GSTVideoOutput] RPI Build, running with v4l2h264dec [2020-09-18 13:36:15.385215] [0xb0d56010] [info] [OpenAuto] [AndroidBluetoothServer] listening. [2020-09-18 13:36:15.416008] [0xb0d56010] [info] [OpenAuto] [btservice] Listening for connections, address: DC:A6:32:C6:C5:98, port: 22 [2020-09-18 13:36:15.422091] [0xb0d56010] [info] [OpenAuto] [btservice] Service registered, port: 22 [2020-09-18 13:36:15.750822] [0xb0d56010] [info] [OpenAuto] [App] Waiting for USB device... [2020-09-18 13:36:15.756974] [0xb0d56010] [info] [OpenAuto] [App] Waiting for Wireless device... [2020-09-18 13:36:15.972174] [0x923fa2f0] [info] [OpenAuto] [App] Devices enumeration result: false org.kde.bluez: PendingCall Error: "Host is down" [2020-09-18 13:36:23.799357] [0xb0d56010] [info] [OpenAuto] [GSTVideoOutput] Got resize request to 744x432 [2020-09-18 13:36:44.337684] [0xb0d56010] [info] [OpenAuto] [GSTVideoOutput] Got resize request to 744x432

any suggestion?

robert5974 commented 4 years ago

On the phone having issues, have you checked in developer settings of the phone, what your default usb connection behavior is? Should be file transfer, MTP, Android auto...or whatever your phone says.

speleolontra commented 4 years ago

Bye, the developer options were disabled and I enabled them. now the default behavior in developer options is set to "file transfer" (no reference to AA), however in the USB Preferences I cannot change them and it is still set to "no file transfer".

rsjudka commented 4 years ago

So in your log, the Devices enumeration result is just for the initial scan when the app launches (if you have your phone plugged in before starting dash, that would point to your device not being recognized, which is going to be an issue with your setup)

You can ignore that second bolded part, I'm assuming you're not attempting to connect wirelessly?

Can you try unplugging and plugging back in your phone to see if that changes anything?

speleolontra commented 4 years ago

HI, maybe Isolved the problem. I did not understand how and whi, but I do 2 things:

With these adjustments the phone is recognized by RPi. Now AA starts correctly. I wrote "maybe" beacause I do last attempts at 2 AM last night... I hope everything is still okay today, I haven't tried in the car yet. Thanks for all suggestions! Lontra

rsjudka commented 4 years ago

well glad you got it work :) but still a bit confused because you said this worked with different phones correct (and you didn't change anything with your setup)?

Im more inclined to think bullet one fixed the issue, because it could have been possible that the pi just wasn't getting enough power to drive the display and also connect to your phone, but that's just speculation. I would guess tho that if you enabled USB debug mode, it should work as well.

speleolontra commented 4 years ago

Yes, I confirm, with other phones it was ok. in fact I did not understand why, but maybe what I do can be useful for other users. Thanks, now next step for me is:

By Lontra