-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Device support (add your device here) #12
Comments
Goggles: V1 When starting the app for the first time when plugging in the usb cable it freezes, after pressing the "back" button and opening the app again it works. Edit: did some more testing, the stream starts lagging behind so the latency increases, it catches up eventually and gets behind again. |
Device: Samsung Galaxy S20 25mbit shows one frame then freezes. Waiting 20s or so does not solve the issue. |
Goggles: V2 |
Goggles: V1 |
Goggles used (v1/v2): v1 |
Goggles: V1 |
Goggles: V2 |
V1 Goggles |
Goggles used (v1/v2) : v1 Picture is sent and shown in app, but then app freezes. |
Goggles: V2 |
Goggles used (v1/v2) : v1 |
Goggles used (v1/v2): v1 |
Goggles: V1 |
Goggles used (v1/v2): V1 A higher end Anker cable that I use for my display port external touch screen did NOT work. Both said "Unsupported USB Device". |
Google V1 |
Goggles: V1 |
Goggles used = V2 Goggles used = V2 Tried a USB-A to micro USB cable to the phone and USB-A to USB-C to the Goggles but it didnt work. |
Google V1 |
Goggles: V1 + normal Airunit |
Goggles: V1 received_2311501135661030.mp4 |
Goggles: V1 |
Goggles; v1 |
Goggles used: V1 My workflow:
Repeat steps 4 and 5 after disconnecting the phone if any issue occurs and the issue resolves itself. NOTE: I have not tested real world flying conditions. |
V1 |
Goggles: V2 Works with and without temp control. |
Goggles: V2 Used cable: 25 mbit: Works takes a while and sometimes freezes |
Goggles: V1 Used Cable: USB-C to USB-C Temperature control deactivated, No recording, MicroSd inserted. |
Goggles used (v1/v2) = v2 The image froze on a few occasions but would resume after changing app focus (i.e. switch away from app, then switch back). |
Goggles v2 |
Goggles used (v1/v2): v2 |
Device brand/type: Oneplus 9 Pro Tried with OTG and didn't work with any of the cables I have, also didn't work with the usb-c charging cable for my Macbook Pro. |
Goggles: V1 & V2 Digiview tried : |
Notes:
|
Try setting buffer to legacy, seemed to do the trick for me ;) |
Goggles V1 Samsung Galaxy S7 Nvidia Shield K1 Tablet App version 1.0.0 beta Used cable: USB 3.0 (USB C to USB A male) with Micro USB + USB C to USB 2.0 Female Adapter Cable https://www.amazon.com/gp/product/B01N1RHJC0/ref=ppx_yo_dt_b_asin_title_o01_s00?ie=UTF8&psc=1 25mbit working: Yes 50mbit working: Yes latency: approx 0.5 seconds Video Preset: Legacy (on both Galaxy and Sheild) Temperature control activated (I prefer to keep it activated always). This did not impact my ability to get video out. I record on Air Unit SD card while using the app without issue. Side note: I was able to use the HDMI out on the Nvidia Shield K1 Tablet successfully. This has allowed me to output video to my older FPV goggles that have HDMI in as well as large viewing screens/projectors. This was my goal with using this app and am very pleased! |
Goggles used (v1/v2) |
Goggles: V1 |
Goggles used (v2) |
Goggles used (v2) |
Goggles used (v2) |
Goggles: V1 + / Vista approx 150ms? No stuttering |
Goggles: V1 + / Vista lagging, not usable / recommended. CPU/GPU too slow |
Goggles V2, dji air unit it worked after enabling usb debugging on developer options (developer mode activated) |
DJI FPV Goggles V2, Caddx Vista unit |
|
Goggles: V1
|
Goggles: V2 |
Goggles: V2 |
Goggles: V2 |
Goggles used (v2) |
I want to update Nokia C3-00 keypad mobile s40. |
Add your experience with specific devices here so people can see if it works or not. Add the following information:
*How to measure latency? Use an online stopwatch and point the FPV cam at the screen. take a picture of the phone with the image of the stopwatch and calculate the difference.
The text was updated successfully, but these errors were encountered: