Repository navigation
new feature: receiving udp video strem from cheap toys with wifi cam's #187
Description
Request for new new feature: receiving udp video strem from cheap toys with wifi cam's
Receiving and playing back video streams from cheap toys equipped with Wi‑Fi cameras. The camera up an access point. We connect to it. UDP stream. Now decoder only in Buffering state.
Activity
compot-dev commentedon Oct 15, 2026
Thanks for the request! We looked into it. Toys with a
FLOW-UFO-xxxxxxaccess point (BL60x camera, the KY UFO app) don't send plain RTP or raw UDP video. The drone waits for a probe from the client on192.168.169.1:8800, then sends MJPEG frames cut into 1 KB fragments, and the client has to keep acknowledging them. The decoder never sends that probe, so it stays in Buffering.We'll add this protocol as a new transport (video only, no flight control) and build a test APK from a separate branch. When it's ready I'll post a direct download link here. Could you then:
FLOW-UFO-…or something else) and the model;http://<phone IP>:8085/stats.jsonandhttp://<phone IP>:8085/logfrom a browser on the same network, or long-press → screenshot, so we can see what the toy sends.test: ImageIO by reflection, unit tests compile against android.jar (#…
fix: FLOW-UFO window and client after review (Qodo on #188)
compot-dev commentedon Oct 15, 2026
@CatRovacer a test build is ready:
Direct APK link: https://github.com/OpenIPC/decoder/releases/download/flowufo-187-test1/decoder-flowufo-test1.apk
Release notes with the steps: https://github.com/OpenIPC/decoder/releases/tag/flowufo-187-test1 · code: #188
Short version:
FLOW-UFO-…Wi‑Fi, and stay connected even if Android warns that there is no internet.flowufo://192.168.169.1:8800(or justflowufo://).This is built from a description of the protocol, not from a real toy, so it may not work on the first try. If there's no picture, or it looks wrong, please wait about 30 s, then open
http://127.0.0.1:8085/stats.jsonandhttp://127.0.0.1:8085/login a browser on the same phone and paste both here. Please also tell us the phone model, the Android version, and the toy's Wi‑Fi name and model. Thank you!CatRovacer commentedon Oct 15, 2026
First toy: K200
AccPoint FLY-UFO-1c8414, IP:192.168.1.100
No image, stats.json:
{
"app": "OpenIPC Decoder",
"version": "2.10",
"git": "8aaf666",
"time": "2026-10-15 20:05:05",
"uptime_s": 374709,
"device": "OPPO CPH2725 · QTI SM6115 · board bengal",
"android": "15 (SDK 35)",
"screen": "1604x720",
"addresses": [
"http://192.168.1.100:8085/",
"http://33.91.55.135:8085/",
"http://33.95.96.154:8085/"
],
"server": "listening",
"decoders": [
{
"name": "c2.qti.avc.decoder",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.avc",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "c2.qti.avc.decoder.low_latency",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.avc.low_latency",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "c2.qti.avc.decoder.secure",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.avc.secure",
"type": "video/avc",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "c2.qti.hevc.decoder",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.hevc",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "c2.qti.hevc.decoder.low_latency",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.hevc.low_latency",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 16,
"fps_1080p": 60
},
{
"name": "c2.qti.hevc.decoder.secure",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.hevc.secure",
"type": "video/hevc",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "c2.qti.vp9.decoder",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 6,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.vp9",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 6,
"fps_1080p": 60
},
{
"name": "c2.qti.vp9.decoder.low_latency",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 6,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.vp9.low_latency",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 6,
"fps_1080p": 60
},
{
"name": "c2.qti.vp9.decoder.secure",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "OMX.qcom.video.decoder.vp9.secure",
"type": "video/x-vnd.on2.vp9",
"hardware": true,
"adaptive": true,
"max_instances": 3,
"fps_1080p": 60
},
{
"name": "c2.android.av1-dav1d.decoder",
"type": "video/av01",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "c2.android.avc.decoder",
"type": "video/avc",
"hardware": false,
"adaptive": true,
"max_instances": 32,
"fps_1080p": 60
},
{
"name": "OMX.google.h264.decoder",
"type": "video/avc",
"hardware": false,
"adaptive": true,
"max_instances": 32,
"fps_1080p": 60
},
{
"name": "c2.android.h263.decoder",
"type": "video/3gpp",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "OMX.google.h263.decoder",
"type": "video/3gpp",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "c2.android.hevc.decoder",
"type": "video/hevc",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "OMX.google.hevc.decoder",
"type": "video/hevc",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "c2.android.mpeg4.decoder",
"type": "video/mp4v-es",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "OMX.google.mpeg4.decoder",
"type": "video/mp4v-es",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "c2.android.vp8.decoder",
"type": "video/x-vnd.on2.vp8",
"hardware": false,
"adaptive": true,
"max_instances": 32,
"fps_1080p": 123
},
{
"name": "OMX.google.vp8.decoder",
"type": "video/x-vnd.on2.vp8",
"hardware": false,
"adaptive": true,
"max_instances": 32,
"fps_1080p": 123
},
{
"name": "c2.android.vp9.decoder",
"type": "video/x-vnd.on2.vp9",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "OMX.google.vp9.decoder",
"type": "video/x-vnd.on2.vp9",
"hardware": false,
"adaptive": true,
"max_instances": 32
},
{
"name": "c2.android.av1.decoder",
"type": "video/av01",
"hardware": false,
"adaptive": true,
"max_instances": 32
}
],
"ui_thread": "ok",
"mode": "paused",
"active_slot": 5,
"single": {
"url": "flowufo://192.168.1.100:8800",
"transport": "AUTO",
"transport_mode": "AUTO",
"video": false,
"status": "Waiting for the toy: probing 192.168.1.100:8800",
"codec": "MJPEG",
"audio": "NONE",
"out_fps": 0,
"decode": "full"
},
"slots": [
{
"slot": 1,
"on_screen": false,
"url": "rtsp://@192.168.1.106:554/stream=0",
"transport": "check over TCP",
"transport_mode": "AUTO",
"video": false,
"text": "Waiting for a stream check",
"probe": {
"state": "waiting"
}
},
{
"slot": 2,
"on_screen": false,
"url": "rtsp://@192.168.1.106/stream=2",
"transport": "check over TCP",
"transport_mode": "AUTO",
"video": false,
"text": "Waiting for a stream check",
"probe": {
"state": "waiting"
}
},
{
"slot": 3,
"on_screen": false,
"url": "rtsp://***@192.168.1.237:554/stream=0",
"transport": "check over TCP",
"transport_mode": "AUTO",
"video": false,
"text": "Waiting for a stream check",
"probe": {
"state": "waiting"
}
},
{
"slot": 4,
"on_screen": false,
"url": "udp://192.168.1.101:8800",
"transport": "UDP listen",
"transport_mode": "AUTO",
"video": false,
"text": "UDP listen slot: not checked in single view",
"probe": {
"state": "not checked"
}
},
{
"slot": 5,
"on_screen": true,
"url": "flowufo://192.168.1.100:8800",
"transport": "AUTO",
"transport_mode": "AUTO",
"video": false,
"text": "Waiting for the toy: probing 192.168.1.100:8800"
},
{
"slot": 6,
"on_screen": false,
"url": "flowufo://",
"transport": "FLOW-UFO UDP",
"transport_mode": "AUTO",
"video": false,
"text": "toy drone slot: not checked in single view",
"probe": {
"state": "not checked"
}
},
{
"slot": 7,
"on_screen": false,
"video": false,
"text": "not configured",
"probe": {
"state": "not checked"
}
},
{
"slot": 8,
"on_screen": false,
"video": false,
"text": "not configured",
"probe": {
"state": "not checked"
}
},
{
"slot": "U",
"on_screen": false,
"url": "udp://@:5600",
"transport": "UDP push",
"transport_mode": "UDP",
"video": false,
"text": "U · not checked in single view",
"probe": {
"state": "not checked"
}
}
]
}
2. Model D16, AP: FLOW_251DC0, IP:192.168.169.2
3. Model : Drone YL3, AP: HF_ba47b828, IP:192.168.80.3
2,3 no video and image
compot-dev commentedon Oct 15, 2026
Thank you, this helps a lot! A few things we can already see:
1. K200 (
FLY-UFO-1c8414, phone 192.168.1.100): the slot was set toflowufo://192.168.1.100:8800, but that is your phone's own address. The toy itself is almost certainly192.168.1.1. The 192.168.1.x network suggests an older family of these toys that streams plain RTSP. Could you try these two slots and tell us what each shows?rtsp://192.168.1.1:7070/webcamflowufo://192.168.1.1:88002. D16 (
FLOW_251DC0, phone 192.168.169.2): the toy should be192.168.169.1, so please useflowufo://192.168.169.1:8800. If there's still no picture, please sendhttp://127.0.0.1:8085/stats.jsonandhttp://127.0.0.1:8085/logfrom this toy after about 30 s. Theflowufopart of stats.json and theFLOW-UFOlines in the log show whether the toy answers at all. The D16 may use a different protocol (video on another port), and the log will tell us.3. YL3 (
HF_ba47b828, phone 192.168.80.3): this looks like yet another family. Which app does its manual or box tell you to install (name, or a link to the store page)? The toy is probably192.168.80.1.For each toy, the vendor app's name helps us most, since toys that use the same app usually share a protocol.
feat: FLOW-UFO after turbodrone (both ports, quality bytes, lagging s…
compot-dev commentedon Oct 15, 2026
@CatRovacer an update and a short how-to for the next tests.
What we learned about your three toys
FLY-UFO-…192.168.1.1rtsp://192.168.1.1:7070/webcam, which also expects a small "heartbeat" packet every secondFLOW_…192.168.169.1HF_…192.168.80.1jieli://in the next buildThe next test build will cover all three. I'll post the direct link here with the exact address for each toy.
How to send us what the app sees (no extra tools needed: the decoder has a small built-in web server)
http://127.0.0.1:8085/log: the app's own log (last ~500 lines). It shows what the app sent to the toy and what came back.http://127.0.0.1:8085/stats.json: the current state of the slot.A screenshot (long-press on the picture) helps too if a picture appears but looks wrong (colours, stripes). Thanks a lot for testing!
Merge pull request #198 from OpenIPC/feat/jieli-187
fix: /log keeps the app's lines and only Info and up from system libr…
CatRovacer commentedon Oct 15, 2026
На D16 работает flyufo://192.168.169.1:8800. Ориентации картинки и экрана правильные.
compot-dev commentedon Oct 15, 2026
@CatRovacer great news about the D16, thank you!
flowufo://192.168.169.1:8800works on the very first test build.A quick question about the photo of your three drones (the orange one on the YL3 box, the grey one on the D16 box, and the grey one with black guards): which drone is which? Please label them like this:
For each, please also tell us its Wi‑Fi name (
FLY-UFO-…,FLOW_…,HF_…) and the app from its manual (KY UFO, WIFI UAV, DVRunning 2…). We'll put this table in our docs. May we use your photo there too?The next test build is coming soon:
jieli://192.168.80.1for the YL3, and the K200 picture turned upright.Отличные новости про D16, спасибо!
flowufo://192.168.169.1:8800заработал уже на первой тестовой сборке.Короткий вопрос по фото трёх дронов (оранжевый на коробке YL3, серый на коробке D16, серый с чёрными защитами): подпишите, пожалуйста, какой из них какой:
И для каждого: имя его Wi‑Fi (
FLY-UFO-…,FLOW_…,HF_…) и приложение из инструкции (KY UFO, WIFI UAV, DVRunning 2…). Сведём это в таблицу в документации. Можно ли использовать там ваше фото?Следующая тестовая сборка уже скоро:
jieli://192.168.80.1для YL3 и картинка K200, повёрнутая как надо.docs: photo and table of the toy drones tested in #187
Merge pull request #209 from OpenIPC/docs/toys-photo
19 remaining items
CatRovacer commentedon Oct 16, 2026
YL3: Ориентация картинки как и в случае с К200, вверх ногами, но битая.
Кадры
http://127.0.0.1:8085/jieli-frame.jpg
http://127.0.0.1:8085/jieli-dropped.bin
не снимаются, в браузере сообщения:
Nothing yet (a jieli:// slot in the single view)
Пробовпл дважды, в ом числе и при живом потоке.
report-20261016-180335.txt
fix: YL3 frames put together from each piece's own length (bytes 2-3)…
compot-dev commentedon Oct 16, 2026
@CatRovacer thank you! Your report contained what I needed even without the frames.
Why the lower half was broken: each UDP packet from the YL3 starts with a 20-byte header, and bytes 2–3 of it give the length of the picture piece in that packet. The rest of the packet is left over from earlier frames. The app took the whole packet, so the lower part of every larger frame was made of old data (hence the cuts and flicker). Now it takes only the piece and puts the frame together from several packets.
Orientation: turned 90° instead of 270°, since 270° showed it upside down.
Why the frames could not be saved: opening the browser on the same phone pauses the app and ends the toy session, and the frames went with it. Now they are kept.
Direct APK link: https://github.com/OpenIPC/decoder/releases/download/toys-187-test5/decoder-toys-test5.apk
(release notes: https://github.com/OpenIPC/decoder/releases/tag/toys-187-test5; it installs over test build 4)
Please check the YL3 again: is the picture whole and upright now? K200 and D16 should work as before. If the YL3 is still broken, a report from the app (as you sent) plus
http://127.0.0.1:8085/jieli-frame.jpgand/jieli-dropped.bin(they work now after switching to the browser) would help.@CatRovacer спасибо! В вашем отчёте нашлось всё нужное даже без кадров.
Почему ломалась нижняя половина: каждый UDP-пакет YL3 начинается с 20-байтового заголовка, и байты 2–3 в нём — длина куска картинки в этом пакете. Остальное в пакете — остатки прошлых кадров. Приложение брало пакет целиком, поэтому низ каждого крупного кадра состоял из старых данных (отсюда разрезы и мерцание). Теперь берётся только кусок, а кадр собирается из нескольких пакетов.
Ориентация: поворот 90° вместо 270°, потому что 270° показывал картинку вверх ногами.
Почему кадры не сохранялись: когда на том же телефоне открывается браузер, приложение уходит в паузу и сессия с дроном заканчивается, а кадры пропадали вместе с ней. Теперь они сохраняются.
Прямая ссылка на APK: https://github.com/OpenIPC/decoder/releases/download/toys-187-test5/decoder-toys-test5.apk
(описание: https://github.com/OpenIPC/decoder/releases/tag/toys-187-test5; ставится поверх сборки 4)
Проверьте, пожалуйста, YL3 ещё раз: картинка теперь целая и ровная? K200 и D16 должны работать, как раньше. Если YL3 всё ещё битый, помогут отчёт из приложения (как вы прислали) и
http://127.0.0.1:8085/jieli-frame.jpgс/jieli-dropped.bin— теперь они работают и после перехода в браузер.docs: toy drones are in the release (2.15): FLOW-UFO and KY UFO work,…
Merge pull request #215 from OpenIPC/feat/flowufo-187
compot-dev commentedon Oct 16, 2026
@CatRovacer the drone support is now in the regular release 2.15: D16 (
flowufo://), K200 (rtsp://…:7070/webcam, turned upright) and YL3 (jieli://, still marked experimental). Test build 5 is replaced by the release, which has everything from it plus two more fixes for the YL3 stream (repeated or late packets no longer spoil a frame).APK: https://github.com/OpenIPC/decoder/releases/download/latest/decoder-v2.apk (installs over the test builds and keeps the settings)
This issue stays open until the YL3 picture is confirmed. Is it whole and upright now?
@CatRovacer поддержка дронов вошла в обычный релиз 2.15: D16 (
flowufo://), K200 (rtsp://…:7070/webcam, картинка ровная) и YL3 (jieli://, пока помечен как экспериментальный). Тестовую сборку 5 заменяет релиз: в нём всё то же плюс ещё два исправления потока YL3 (повторные или опоздавшие пакеты больше не портят кадр).APK: https://github.com/OpenIPC/decoder/releases/download/latest/decoder-v2.apk (ставится поверх тестовых сборок, настройки сохраняются)
Issue остаётся открытой, пока не подтвердится картинка YL3. Теперь она целая и ровная?
CatRovacer commentedon Oct 16, 2026
compot-dev
YL3: ориентация картинки теперь правильная., целая, не кусками
Однако:
Скриншоты и прочее прилагаю
Dcdr.this-zip.zip.txt
compot-dev commentedon Oct 16, 2026
@CatRovacer thank you, the archive was exactly what was needed!
What it showed: one UDP packet from the YL3 can carry several pieces of a frame one after another, each with its own 20-byte header (e.g. 3104 bytes = 20 + 2964 + 20 + 100). Release 2.15 read only the first piece, so every frame bigger than 2964 bytes stayed incomplete (in your log 92 of 96 packets were dropped). Only the small ~2 KB frames were shown, and those really are blocky and reddish (the frame you saved looks like that as the toy sent it). Hence the freezing and the poor picture.
Test build 6 reads every piece. On our TV box it plays a simulated YL3 stream built the same way (8 pieces per packet) at 10 fps without a single lost frame.
Direct APK link: https://github.com/OpenIPC/decoder/releases/download/toys-187-test6/decoder-yl3-test6.apk
(version 2.17, installs over 2.15)
Does the YL3 picture now run smoothly with normal colours?
@CatRovacer спасибо, в архиве было ровно то, что нужно!
Что выяснилось: один UDP-пакет YL3 может нести несколько кусков кадра подряд, каждый со своим 20-байтовым заголовком (например, 3104 байта = 20 + 2964 + 20 + 100). Релиз 2.15 читал только первый кусок, поэтому все кадры больше 2964 байт оставались незавершёнными (в вашем логе отброшено 92 пакета из 96). Показывались только маленькие кадры около 2 КБ, а они действительно блочные и красноватые: сохранённый вами кадр так выглядит уже в том виде, в каком его прислал дрон. Отсюда замирание и плохая картинка.
Тестовая сборка 6 читает все куски. На нашей ТВ-приставке она показывает имитацию потока YL3, собранного так же (8 кусков в пакете), с частотой 10 кадров/с без единого потерянного кадра.
Прямая ссылка на APK: https://github.com/OpenIPC/decoder/releases/download/toys-187-test6/decoder-yl3-test6.apk
(версия 2.17, ставится поверх 2.15)
Теперь картинка YL3 идёт плавно и с нормальными цветами?
CatRovacer commentedon Oct 16, 2026
Вот, теперь картинка правильная. Качество зависит от сенсора. Лучшая картинка у K200 )))
Надеюсь, логи не нужны? Но приложу.
Благодарю. Issue можно закрывать, мержить. Ну когда-нибудь дополните раздельными картинками для VR.
report-20261016-212344.txt
chore: version 2.16; docs: Jieli works with a YL3 (#187)
Merge pull request #224 from OpenIPC/fix/jieli-pieces-187
compot-dev commentedon Oct 16, 2026
@CatRovacer thank you for testing all three drones so patiently! The YL3 fix is in the regular release 2.16 (https://github.com/OpenIPC/decoder/releases/download/latest/decoder-v2.apk), so all three now work there: D16, K200 and YL3. Closing this issue.
Separate pictures for VR headsets are planned in #204. We'll mention you there when there is something to try.
@CatRovacer спасибо за терпеливую проверку всех трёх дронов! Исправление для YL3 вошло в обычный релиз 2.16 (https://github.com/OpenIPC/decoder/releases/download/latest/decoder-v2.apk), так что там теперь работают все три: D16, K200 и YL3. Закрываю issue.
Раздельные картинки для VR-шлемов запланированы в #204. Позовём вас туда, когда будет что попробовать.