You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like the Kindle Fire supports its own set of video specifications and sizes. Perhaps the code should check to see if the video specification is supported on the device prior to starting the stream?
I have had a problem with the Tower/Solo app video decoding on MTK based tablets for a long time.
The observed behaviour is that Tower can control the Solo properly, but the video is never displayed.
The Solo app may decode 1 frame of video before resetting the connection. Then this repeats.
I hooked up USB debugging and captured the resulting logcat for both the Solo app and Tower. Although the versions of each I used are fairly old (last March for Solo and July for Tower) the problem remains to this day.
Hope the logcat output helps someone. I don't think this is a Tower issue but may be related to dronekit-android or the GLES android drivers for the MTK gpu. (Mali400)
BTW the Solo app did the same thing both before and after 3DR moved away from 3DRServices. video_problem.txt video_problem_tower.txt
Activity
jasonhamilton commentedon Dec 1, 2016
It looks like the Kindle Fire supports its own set of video specifications and sizes. Perhaps the code should check to see if the video specification is supported on the device prior to starting the stream?
https://developer.amazon.com/public/solutions/devices/fire-tablets/specifications/02-video-specifications
GPSFan commentedon Dec 5, 2016
I have had a problem with the Tower/Solo app video decoding on MTK based tablets for a long time.
The observed behaviour is that Tower can control the Solo properly, but the video is never displayed.
The Solo app may decode 1 frame of video before resetting the connection. Then this repeats.
I hooked up USB debugging and captured the resulting logcat for both the Solo app and Tower. Although the versions of each I used are fairly old (last March for Solo and July for Tower) the problem remains to this day.
Hope the logcat output helps someone. I don't think this is a Tower issue but may be related to dronekit-android or the GLES android drivers for the MTK gpu. (Mali400)
BTW the Solo app did the same thing both before and after 3DR moved away from 3DRServices.
video_problem.txt
video_problem_tower.txt