-
Notifications
You must be signed in to change notification settings - Fork 9
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
No Video on MediaTek Device (Samsung Galaxy A15)? #6
Comments
This is a common issue with MediaTek SoCs as the third party encoder used the this app primarily supports snapdragon processors. Logs would be useful for debugging this issue For obtaining logs, once #3 is merged there will be a share button. But for now the only way to obtain logs is using logcat on a PC |
Could you upload an .apk build of #3 while we wait? |
Built by GitHub, not tested myself and not endorsed by openipc |
pixelpilot_log_20240920_202831.txt |
Nothing jumps out straight away, another useful bit of information for debbuging would be the details of the HEVC decoder from https://play.google.com/store/apps/details?id=com.parseus.codecinfo |
Ok: c2.android.hevc.decoder
Hardware acceleration: false c2.mtk.hevc.decoder
Hardware acceleration: true c2.mtk.hevc.decoder.secure
Hardware acceleration: true |
What is the "third party encoder" used? May I open an issue in their github to get this fixed? |
Hi,
I just tried out the WifiLink by RunCam. Using the FPV4Win Windows App I receive the video just fine. However, using the same External Wifi Module (the one that comes with the WifiLink-G version), the PixelPilot app does not display any stream.
I did use the correct gs.key, generated by the WifiLink board. I also tried switching to h264. I am on the correct channel 173 with both devices. The PixelPilot App just says "Starting wfb-ng on channel 173 ..." - but never displays anything.
I am using a Samsung Galaxy A15 (not 5G version), which is a pretty new phone (2024) with the latest Android version. It has a Mediatek Helio G99 processor, which seems to be capable of both h264 and h265 - so it should be capable of handling this use-case just fine.
Any ideas what may be going on here? Is there any possibility to get a logfile from the PixelPilot App?
The text was updated successfully, but these errors were encountered: