search

amzn / exoplayer-amazon-port

Official port of ExoPlayer for Amazon devices
Apache License 2.0
171 stars 80 forks source link

4K Fire Stick - video stream stuck after few seconds, but audio stream go forward. #81

Closed kristurek closed 5 years ago

kristurek commented 5 years ago

Issue description

Hi, I have a problem with some streams IPTV only in high resolutions on Fire TV Stick 4K. After few seconds video stream stuck but audio go forward. Then any replay/forward action causes crash app. When I testing on old FireStick, everything works correctly, low and high resolution.

01-14 12:22:22.685 21882 28884 E MtkOmxVdecEx: ## [ERROR] HandleStateSet() line: 7036 LOCK timeout...
01-14 12:22:29.986 21882 21897 E OMXNodeInstance: !!! Observer died. Quickly, do something, ... anything... \
01-14 12:22:30.987 21882 21913 D MtkOmxVdecEx: [0xb30c9000] MtkOmxVdec::GetState (mState=OMX_StateExecuting) \
01-14 12:22:30.988 21882 21913 W OMXNodeInstance: [557a0015:MTK.DECODER.AVC] failed to enter Idle state (now Executing(3), aborting.\
01-14 12:22:30.988 21882 21913 D MtkOmxCore: Mtk_OMX_FreeHandle\
01-14 12:22:30.988 21882 21913 D MtkOmxVdecEx: [0xb30c9000] +MtkOmxVdec::ComponentDeInit
01-14 12:22:30.988 21882 21913 E MtkOmxVdecEx: [0xb30c9000] Warning!! ComponentDeInit before DeInitVideoDecodeHW! De-Init video driver..
01-14 12:22:30.998 21882 21913 I BWC     : get_bwc_mm_property success
01-14 12:22:30.998 21882 21913 E BWC     : fail to open ddr_type_file driver file
01-14 12:22:30.998 21882 21913 I BWC     : DDR Type = -1
--------- beginning of crash
01-14 12:22:30.998 21882 28885 F libc    : Fatal signal 11 (SIGSEGV), code 1, fault addr 0xb3eb30ec in tid 28885 (MtkOmxVdecDecod)
01-14 12:22:30.998 21882 21913 I BWC     : smi_bw_ctrl_set: scen 3, turn off
01-14 12:22:30.998 21882 21913 I BWC     : emi_string is CON_SCE_VP
01-14 12:22:30.999   198   198 W         : debuggerd: handling request: pid=21882 uid=1046 gid=1013 tid=28885
01-14 12:22:30.999 21882 21913 I BWC     : emi_bw_ctrl_set: CON_SCE_VP OFF
01-14 12:22:30.999 21882 21913 I BWC     : set_bwc_mm_property: propterty_id=0, value1=0, value2=0 
01-14 12:22:30.999 21882 21913 I BWC     : gpu_bw_ultra_set: 1, enable
01-14 12:22:30.999 21882 21913 I BWC     : Profile_Change:[BWCPT_VIDEO_PLAYBACK]:OFF,current concurrency is 0x0
01-14 12:22:30.999 21882 21913 I VDO_LOG : eVDecDrvRelease rhandleMem 0xb3f3e000
01-14 12:22:30.999 21882 21913 D MtkOmxVdecEx: [0xb30c9000] signal mInPortAllocDoneSem (1)
01-14 12:22:30.999 21882 28887 D MtkOmxVdecEx: [0xb30c9000] MtkOmxVdecConvertThread terminated
01-14 12:22:30.999 21882 28886 D MtkOmxVdecEx: [0xb30c9000] MtkOmxVdecPostDispThread terminated
01-14 12:22:30.999 21882 21913 D MtkOmxVdecEx: [0xb30c9000] signal mOutPortAllocDoneSem (1)

Reproduction steps

Add to media.exolist.json downloaded sample and run demo. After about 14s video stream will be stuck but audio stream go forward. Next try replay/restart sample, demo application will be crashed.

Link to test content

Sample stream https://www.dropbox.com/s/2urho8ayeuhchta/hd.ts?dl=0

Version of ExoPlayer being used

Software version Fire OS 6.2.5.8 (NS6258/1604) ExoPlayer 2.9.2 or ExoPlayer Amazon Port 2.9.0

A full bug report captured from the device

Bugreport https://www.dropbox.com/s/s77imyg3oyja6z3/bugreport-NS6258-2019-01-14-12-23-50.zip?dl=0 Log file https://www.dropbox.com/s/7t3fasnkogk0buw/log.txt?dl=0

Thanks for any help,

Regards

rinoshs commented 5 years ago

We are able to reproduce the issue and we are working on it.

ZHAJOR commented 5 years ago

Hi,

I have a similar issue but in my case the audio and the video are stuck. When I do a rewind/forward it's playing again! This bug happens on both the FireTV stick and 4K.

02-01 14:10:35.921 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6593
02-01 14:10:39.213 17714 17782 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:10:39.214 17714 17782 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:10:39.215 17714 17782 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:10:39.226 17714 17782 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-pairable._tcp.local. op=Remove #listeners=0
02-01 14:10:39.226 17714 17782 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Apple TV typeSubType=_sleep-proxy._udp.local. op=Remove #listeners=0
02-01 14:10:39.691 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 130
02-01 14:10:40.999 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6563
02-01 14:10:42.239   298 18465 I         : sem_wait nWaitMilliSec : 100
02-01 14:10:44.748 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 130
02-01 14:10:46.036 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 7233
02-01 14:10:49.214 17714 17782 I JmDNSImpl: updateRecord() name=f8:38:80:de:6e:e8@fe80::fa38:80ff:fede:6ee8 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:10:49.216 17714 17782 I JmDNSImpl: updateRecord() name=f8:38:80:de:6e:e8@fe80::fa38:80ff:fede:6ee8 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:10:49.785 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 130
02-01 14:10:51.070 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6462
02-01 14:10:52.706 17714 17781 I JmDNSImpl: updateRecord() name=f8:38:80:de:6e:e8@fe80::fa38:80ff:fede:6ee8 typeSubType=_apple-mobdev2._tcp.local. op=Add #listeners=0
02-01 14:10:52.706 17714 17781 I JmDNSImpl: updateRecord() name=f8:38:80:de:6e:e8@fe80::fa38:80ff:fede:6ee8 typeSubType=_apple-mobdev2._tcp.local. op=Add #listeners=0
02-01 14:10:54.841 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 129
02-01 14:10:56.117 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6653
02-01 14:10:58.588   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12481909)
02-01 14:10:58.621   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12481773)
02-01 14:10:58.654   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12464127)
02-01 14:10:58.688   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12459371)
02-01 14:10:58.721   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12460105)
02-01 14:10:58.754   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12469690)
02-01 14:10:58.788   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12482093)
02-01 14:10:58.821   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12486879)
02-01 14:10:58.854   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12462206)
02-01 14:10:58.888   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12459839)
02-01 14:10:58.921   243   243 D FrameRateEnforcer: FRC INTENTIONAL EARLY BUFFER
02-01 14:10:58.921   243   243 D FrameRateEnforcer: FRC BROKEN current=1 last=2 offset=12457241 fract=12457241
02-01 14:10:58.955   243   243 D FrameRateEnforcer: FRC BROKEN current=2 last=1 offset=12473367 fract=12473367
02-01 14:10:59.854 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 124
02-01 14:11:00.104   655   668 W IMGMemtrackHAL: hal_get_memory: memtrack cache rebuild was required
02-01 14:11:00.139   243   243 D FrameRateEnforcer: FRC BROKEN current=3 last=2 offset=12466384 fract=12466384
02-01 14:11:00.172   243   243 D FrameRateEnforcer: FRC BROKEN current=2 last=3 offset=12474299 fract=12474299
02-01 14:11:00.623   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12475960)
02-01 14:11:00.656   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12481147)
02-01 14:11:00.690   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12464433)
02-01 14:11:00.723   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12464347)
02-01 14:11:00.756   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12482202)
02-01 14:11:00.790   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12488642)
02-01 14:11:00.823   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12493942)
02-01 14:11:00.856   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12476980)
02-01 14:11:00.890   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12482285)
02-01 14:11:00.923   243   243 D FrameRateEnforcer: FRC averting 1:2 (offset=12482405)
02-01 14:11:00.956   243   243 D FrameRateEnforcer: FRC INTENTIONAL EARLY BUFFER
02-01 14:11:00.956   243   243 D FrameRateEnforcer: FRC BROKEN current=1 last=2 offset=12466371 fract=12466371
02-01 14:11:00.990   243   243 D FrameRateEnforcer: FRC BROKEN current=2 last=1 offset=12462724 fract=12462724
02-01 14:11:01.148 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6507
02-01 14:11:02.124   298 18465 I         : sem_wait nWaitMilliSec : 100
02-01 14:11:02.188   298 18473 I VDO_LOG : [LAT]sem_wait nWaitMilliSec : 100
02-01 14:11:02.525   298 18465 I         : sem_wait nWaitMilliSec : 100
02-01 14:11:02.525   298 18473 I VDO_LOG : [LAT]sem_wait nWaitMilliSec : 100
02-01 14:11:02.825   655   881 I WifiDiagsUtil: event=RUN_TEST_CONTINUOUSLY
02-01 14:11:02.825   655   881 I WifiDiagsUtil: loggingPacketStats
02-01 14:11:02.840   655   881 I WifiManager: Wifi getConfiguredNetworks called by system
02-01 14:11:02.854   655   881 I WifiDiagsUtil: pinging ... localhost
02-01 14:11:02.860   655   881 I WifiDiagsUtil: event=pingsComplete, IP=xxx.xxx.xxx..., packetsSent=5, numFailed=0, packetLoss=0.0%, AvgTimeMs=0.56
02-01 14:11:02.860   655   881 I WifiDiagsUtil: pinging ... gateway
02-01 14:11:02.889   655   881 I WifiDiagsUtil: event=pingsComplete, IP=xxx.xxx.xxx..., packetsSent=5, numFailed=0, packetLoss=0.0%, AvgTimeMs=5.46
02-01 14:11:02.889   655   881 I WifiDiagsUtil: pinging ... dns1
02-01 14:11:02.918   655   881 I WifiDiagsUtil: event=pingsComplete, IP=xxx.xxx.xxx..., packetsSent=5, numFailed=0, packetLoss=0.0%, AvgTimeMs=5.40
02-01 14:11:02.918   655   881 I WifiDiagsUtil: event=preConfiguredDNSDetected, action=skipPingTest, nameserver=xxx.xxx.xxx...
02-01 14:11:02.918   655   881 I WifiDiagsUtil: event=noEntryFoundFor: net.dns3, action=skippingPingTest
02-01 14:11:02.918   655   881 I WifiDiagsUtil: event=runHttpConnTestAttempt, host=http://spectrum.s3.amazonaws.com/kindle-wifi/wifistub.html
02-01 14:11:03.130   655   881 I WifiDiagsUtil: event=runHttpConnTestSuccess, host=http://spectrum.s3.amazonaws.com/kindle-wifi/wifistub.html, latency=208
02-01 14:11:03.130   655   881 I WifiDiagsUtil: event=GOOD_CONNECTION
02-01 14:11:03.131   655   881 I WifiDiagsUtil: event=evaluatingCaptivePortal
02-01 14:11:03.207 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc Dropping frame
02-01 14:11:03.209 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc Dropping frame
02-01 14:11:03.210 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc Dropping frame
02-01 14:11:03.212 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc Dropping frame
02-01 14:11:03.226   243   243 D FrameRateEnforcer: FRC BROKEN current=58 last=2 offset=12457170 fract=12457170
02-01 14:11:03.259   243   243 D FrameRateEnforcer: FRC BROKEN current=2 last=58 offset=12455750 fract=12455750
02-01 14:11:03.339   655   881 I WifiDiagsUtil: Ping HOST=http://spectrum.s3.amazonaws.com/kindle-wifi/wifistub.html, result=Yes (1)
02-01 14:11:03.339   655   881 I WifiDiagsUtil: same network status
02-01 14:11:03.959   243   243 D FrameRateEnforcer: FRC BROKEN current=14 last=2 offset=12481852 fract=12481852
02-01 14:11:03.993   243   243 D FrameRateEnforcer: FRC BROKEN current=2 last=14 offset=12438794 fract=12438794
02-01 14:11:04.896 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 101
02-01 14:11:05.089  5667 21995 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:05.089  5667 21995 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:06.200 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 5487
02-01 14:11:07.352 17714 17781 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Apple TV typeSubType=_sleep-proxy._udp.local. op=Add #listeners=0
02-01 14:11:07.559 17714 17781 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Add #listeners=0
02-01 14:11:07.560 17714 17781 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Add #listeners=0
02-01 14:11:07.561 17714 17781 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-mobdev2._tcp.local. op=Add #listeners=0
02-01 14:11:07.562 17714 17781 I JmDNSImpl: updateRecord() name=40:cb:c0:c4:9e:83@fe80::42cb:c0ff:fec4:9e83 typeSubType=_apple-pairable._tcp.local. op=Add #listeners=0
02-01 14:11:09.217 17714 17782 I JmDNSImpl: updateRecord() name=2llh1v3xc8rrs typeSubType=_tw-multipeer._tcp.local. op=Remove #listeners=0
02-01 14:11:09.220 17714 17782 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Bedroom typeSubType=_sleep-proxy._udp.local. op=Remove #listeners=0
02-01 14:11:09.221 17714 17782 I JmDNSImpl: updateRecord() name=70-35-60-63.1 TVOS-11.2 DONT UPGRADE typeSubType=_sleep-proxy._udp.local. op=Remove #listeners=0
02-01 14:11:09.597  1119  1119 I wpa_supplicant: TDLS: Invalid frame - payloadtype=1 category=240 action=10
02-01 14:11:09.901 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 124
02-01 14:11:10.331  1119  1119 I wpa_supplicant: TDLS: Invalid frame - payloadtype=1 category=240 action=10
02-01 14:11:11.147 17714 17781 I JmDNSImpl: updateRecord() name=70-35-60-63.1 TVOS-11.2 DONT UPGRADE typeSubType=_sleep-proxy._udp.local. op=Add #listeners=0
02-01 14:11:11.244 17714 17781 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Bedroom typeSubType=_sleep-proxy._udp.local. op=Add #listeners=0
02-01 14:11:11.280 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6747
02-01 14:11:14.950 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 125
02-01 14:11:15.446  5667 21997 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:15.446  5667 21997 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:16.316 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6862
02-01 14:11:16.798  5667 21998 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:16.798  5667 21998 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:17.584  5667 21999 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:17.584  5667 21999 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:19.075 21483 22000 W AmazonAppstore.DummyAndroidAccountAccessor: Could not retrieve any account from the Account Cache, regardless of index.
02-01 14:11:19.077 21483 22000 I AmazonAppstore.AvailabilityService: analyzing ad3-meta submission policies
02-01 14:11:19.083 21483 22000 I AmazonAppstore.AvailabilityService: looking for ad3-meta measurements to submit...
02-01 14:11:19.086 21483 22000 I AmazonAppstore.AvailabilityService: analyzing zeroes submission policies
02-01 14:11:19.088 21483 22000 I AmazonAppstore.AvailabilityService: looking for zeroes measurements to submit...
02-01 14:11:19.090 21483 22000 I AmazonAppstore.AvailabilityService: analyzing venezia-metrics submission policies
02-01 14:11:19.093 21483 22000 I AmazonAppstore.AvailabilityService: looking for venezia-metrics measurements to submit...
02-01 14:11:19.096 21483 22000 W AmazonAppstore.AvailabilityService: File is less than minimum size (1024 < 5000). skip submitting measurement.
02-01 14:11:19.098 21483 22000 I AmazonAppstore.AvailabilityService: analyzing ad3.report.venezia submission policies
02-01 14:11:19.099  5667 22001 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:19.100  5667 22001 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:19.104 21483 22000 I AmazonAppstore.AvailabilityService: looking for ad3.report.venezia measurements to submit...
02-01 14:11:19.105 21483 22000 I AmazonAppstore.AvailabilityService: analyzing engagement submission policies
02-01 14:11:19.108 21483 22000 I AmazonAppstore.AvailabilityService: looking for engagement measurements to submit...
02-01 14:11:19.110 21483 22000 W AmazonAppstore.AvailabilityService: File is less than minimum size (3328 < 5000). skip submitting measurement.
02-01 14:11:19.111 21483 22000 I AmazonAppstore.AvailabilityService: analyzing venezia submission policies
02-01 14:11:19.113 21483 22000 I AmazonAppstore.AvailabilityService: looking for venezia measurements to submit...
02-01 14:11:19.117 21483 22000 I AmazonAppstore.AvailabilityService: Synced successfully
02-01 14:11:19.120  1119  1119 I wpa_supplicant: TDLS: Invalid frame - payloadtype=1 category=240 action=10
02-01 14:11:19.216 17714 17782 I JmDNSImpl: updateRecord() name=38:71:de:83:74:61@fe80::3a71:deff:fe83:7461 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:11:19.217 17714 17782 I JmDNSImpl: updateRecord() name=38:71:de:83:74:61@fe80::3a71:deff:fe83:7461 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:11:19.218 17714 17782 I JmDNSImpl: updateRecord() name=38:71:de:83:74:61@fe80::3a71:deff:fe83:7461 typeSubType=_apple-mobdev2._tcp.local. op=Remove #listeners=0
02-01 14:11:19.220 17714 17782 I JmDNSImpl: updateRecord() name=70-35-60-63.1 TVOS-11.2 DONT UPGRADE typeSubType=_sleep-proxy._udp.local. op=Remove #listeners=0
02-01 14:11:19.220 17714 17782 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Bedroom typeSubType=_sleep-proxy._udp.local. op=Remove #listeners=0
02-01 14:11:19.984 17539 18470 I MediaCodecLogger: com.kanopy.tvapp.SW.audio.mp4a.bitrateInKbps = 125
02-01 14:11:21.348 17539 18461 I MediaCodecLogger: com.kanopy.tvapp.4K.HW.video.avc.bitrateInKbps = 6943
02-01 14:11:22.959   298 18465 I         : sem_wait nWaitMilliSec : 100
02-01 14:11:23.024   298 18473 I VDO_LOG : [LAT]sem_wait nWaitMilliSec : 100
02-01 14:11:23.640 17714 17781 I JmDNSImpl: updateRecord() name=70-35-60-63.1 TVOS-11.2 DONT UPGRADE typeSubType=_sleep-proxy._udp.local. op=Add #listeners=0
02-01 14:11:23.736 17714 17781 I JmDNSImpl: updateRecord() name=70-35-60-63.1 Bedroom typeSubType=_sleep-proxy._udp.local. op=Add #listeners=0
02-01 14:11:23.945 17714 17781 I JmDNSImpl: updateRecord() name=ChaseMenakerMacBookAir.local. typeSubType=_tcp.ip6.arpa. op=Add #listeners=0
02-01 14:11:23.946 17714 17781 I JmDNSImpl: updateRecord() name=ChaseMenakerMacBookAir.local. typeSubType=_tcp.in-addr.arpa. op=Add #listeners=0
02-01 14:11:23.951 17714 17781 I JmDNSImpl: updateRecord() name=Chromecast-a602a225b05b2ed37f4f2893077c1d29 typeSubType=_37f83649._sub._googlecast._tcp.local. op=Add #listeners=0
02-01 14:11:23.954 17714 17781 I JmDNSImpl: updateRecord() name=Chromecast-a602a225b05b2ed37f4f2893077c1d29 typeSubType=_d2ca5178._sub._googlecast._tcp.local. op=Add #listeners=0
02-01 14:11:23.964 17714 17781 I JmDNSImpl: updateRecord() name=E50-E3-56e22584432e797850c3624aa9fdc5e9 typeSubType=_d2ca5178._sub._googlecast._tcp.local. op=Add #listeners=0
02-01 14:11:25.572  1119  1119 I wpa_supplicant: TDLS: Invalid frame - payloadtype=1 category=240 action=10
02-01 14:11:26.116   409   486 I DolbyAudioStreamOut: standby()
02-01 14:11:26.151   655  5698 I AmazonPowerManagerVendorCallback: Wakelock released UID:1041 PID:0 Tag:AudioMix
02-01 14:11:27.245  5667 22003 I DiscoveryService: SsdpNanoHTTPD - Method:GET;
02-01 14:11:27.245  5667 22003 I DiscoveryService: SsdpDialRestService - serve: Method: GET URI = /apps/com.spotify.Spotify.TVv2;
02-01 14:11:28.360   298 18465 E         : sem_wait_timeout timeout
02-01 14:11:28.360   298 18465 E MtkOmxVdecEx: ## [ERROR] MtkOmxVdecDecodeThread() line: 1393 WAIT timeout...

Do you think it can be related?

humiboy commented 5 years ago

When come new Update? I have the same issues on my 3 FireTV 4K Sticks.

rinoshs commented 5 years ago

This is a H264 deinterlacing issue. We are working our vendor partners for a fix.

iandarbey commented 5 years ago

Any timeframe for fix? 3 weeks since confirmed reproduction and working on it. Has cause been identified?

humiboy commented 5 years ago

Anyone use IPTV for example with Smart IPTV App an FireTV Stick 4K?

Everytime after a few changes the Channels the App is blocked black screen nothing more works.

It is possible to fix this mega big issue?

All other FireTV devices have no issue. It is a firmware bug or hardware issues?

Must i send my 3 FireTV 4K Sticks retoure or not?

humiboy commented 5 years ago

It is possible to fix this big issue with IPTV Channels or not?

jacotec commented 5 years ago

That did cost me 3 hours on the weekend, I was about so send my new 4k stick right back to Amazon because of this major issue. Will keep it and wait for a hopefully fast fix.

iandarbey commented 5 years ago

Hopefully the fix is faster than the replies / updates.....

humiboy commented 5 years ago

Where is the Amazon Support?

The 4K Stick is available since 4 month+ an the market and this big bugs is still not fixed????

That is not akzeptable.

iandarbey commented 5 years ago

They’ll need to fix it to launch the recast in uk / Europe.....

humiboy commented 5 years ago

Amazon is so big and release an the market a FireTV Stick 4K Stick with many big bugs. Have Amazon not testet there product before release?

And why we must waitung so long for a fix?

gregor-hh commented 5 years ago

when comes the fix out?????

rinoshs commented 5 years ago

We are working on it. Unfortunately, the issue is in the chipset firmware for which only the chipset vendor has the source code. The vendor is still in development phase trying to identify a fix. Once the vendor has identified a fix, we will provide an eta.

humiboy commented 5 years ago

This fix you are work solved the problem with Smart IPTV App too? After a few zapping the App crashes and no more works only Buffering. Other IPTV Apps crashes too for example.

Only the 4K Stick have this big problem other FireTVs have no problem.

iandarbey commented 5 years ago

The problem is the interlaced content (which your IPTV app asks the stick to decode). There is a bug with the deinterlacing decoding.

Hopefully it’s not a significant bug as for me at least the decoding appears to be visually good until the freeze and crash of the underlying driver.

Most UK and European broadcast tv is interlaced so I’d imagine Amazon will want this fixed so they can launch their new DVR in the UK.

humiboy commented 5 years ago

What is this Shit with the Amazon FireTV 4K and Smart IPTV App????

https://youtu.be/zYwLW86i1yo

iandarbey commented 5 years ago

It’s an issue with interlaced content..... although for most people the content is legally obtained live tv.....

humiboy commented 5 years ago

@rinoshs

And why the chipset vendor not can fix this big problem since 1-2 month?

He can not fix, because it is a hardware issues and not software issues?

NedScott commented 5 years ago

@humiboy this isn't the place to bitch and moan or look for someone to blame. If you are unsatisfied with the product, leave a review on Amazon. This is a technical discussion, and your messages are spamming everyone trying to follow the issue.

humiboy commented 5 years ago

This is here a technical discussion and we are waiting for a fix.

In amazon to review the product no developer read this.

humiboy commented 5 years ago

@rinoshs

any news from chipset vendor to to fix this big problem? Or it is a hardware issue and not software issu in the chipset driver and the FireStick 4K is not possible to fix?

The problem is since release from the FireStick 4K this problem is not fixed. Why over 4 month and still not fixed?

rinoshs commented 5 years ago

It is a vendor software issue. Vendor fix development is an iterative process. The vendor fixes have to go through a full regression cycle, which usually catches regressions which might not be related to the original fix. The vendor then goes and refines the fix to account for regressions. This iterative process is what takes time.

humiboy commented 5 years ago

And why Amazon have not testet this before Release the Fire Stick 4K in the Market??????

And now we have buy an bug product and must live with this all bugs and must play the beta tester for Amazon?

gregor-hh commented 5 years ago

@humiboy Why you flame here so much?... we are all waiting here for a fix... and how rinoshs wrote, the vendor is working on it.... it make no sense with your repeated questions.

jacotec commented 5 years ago

@humiboy GitHub is not the place for this kind of discussions. If you have something to contribute technically concerning the issue, please feel free to post. Bugs are happening, discussions why Amazon did not see it won't help fixing neither are containing infos which helps with the progress. Please have this kind of discussions with the Amazon Customer Support!

humiboy commented 5 years ago

Okey sorry guys no problem. We all waiting i know but it is too long since release.

This is not a little bug it is a very big bug.

humiboy commented 5 years ago

@rinoshs

any news from the chipset vendor?

humiboy commented 5 years ago

I see the bugs can not fixed from chipset vendor. It is perhaps a Hardware failure isses and not a software driver issues.

Many thousends of Firestick 4K have Amazon sell to the customers...

We all have buy a bug product from Amazon.

Can the Developers from Amazon read this thread here or not?

Can anyone send me a link to contact with Amazon Developer Support?

y2000j commented 5 years ago

I see the bugs can not fixed from chipset vendor. It is perhaps a Hardware failure isses and not a software driver issues.

Many thousends of Firestick 4K have Amazon sell to the customers...

We all have buy a bug product from Amazon.

Can the Developers from Amazon read this thread here or not?

Can anyone send me a link to contact with Amazon Developer Support?

@humiboy Hi! from where did you get the information that it can't be fixed from chipset Vendor? It would be a pity if it is a hardware failure. But i never heared about that? Do you have a source of your information?

I really hope that the problem can be fixed. I bought four of the fire 4k TV sticks and was very happy about there performance until i found out about the bug.

humiboy commented 5 years ago

For me myself no source after 5-6 month not can fixed from chipset vendor is a Hardware Failure and can not fixed.

When it is a Software driver bug it have fixed for a long time ago but it is still not fixed after 5-6 month. Why? It is a iterative process... and take still 1-2 years for fix?

humiboy commented 5 years ago

The 4K Stick have become an Update to 6.2.6.3 and the big bug is still not fixed?

leone007 commented 5 years ago

Any chance for an ETA?

humiboy commented 5 years ago

very very bad support from Amazon Developers Team.

No Update, no new statement, nothing.

We users are only the beta testers.

badbob001 commented 5 years ago

Is this bug specific to interlaced video? I encountered stuttered and slow playback with h264 non-interlaced video when it is recorded at 60fps. Same video plays smoothly and at correct speed on my firetv 3-class devices.

rinoshs commented 5 years ago

Yes, the issue is specific to H264 interlaced video. This issue is fixed. The system ota is scheduled for mid Q2.

leone007 commented 5 years ago

Great, does this mean that we’ll get H264 HW Deinterlace? Or it means that we’ll be able to play H264 interlaced content (which isn’t really a solution for EU customers)

leone007 commented 5 years ago

Also IF there is going to be HW H264 deinterlace support, is it going to be full framerate deinterlacing? Which methods will be supported? @rinoshs please elaborate if you are in the possession of this kind of information :)

humiboy commented 5 years ago

When this issue is fixed why update for mid Q2???

Why so long waiting after 5 month?

humiboy commented 5 years ago

Any news from Amazon support to fix the problem with iptv streams after 6 month?

Why Amazon need so long time to release a fix?

Gertbucket commented 5 years ago

The sync issues are driving me nuts. What's happening here?

humiboy commented 5 years ago

When come the big update to fix the problem

watsond2002 commented 5 years ago

Can someone from Amazon please give us an update on the expected time to deliver the new firmware to fix this bug. Feels like it's going on forever and Amazon have gone very quiet!

humiboy commented 5 years ago

The Amazon Support ist not available or exist. Only sell products but no support

jacotec commented 5 years ago

Unfortunately I need to agree, that's taking much too long!

Going on a business trip next Friday, I have tons of TV recordings I want to put on memory card of my GL-AR750S to have something to watch independent from hotel WiFi speed (in case I lack of proper speed to my Emby server). I need to deinterlace all files first, meanwhile I've set up a dedicated VM on my servers for that.

humiboy commented 5 years ago

@rinoshs

any news for updates????

badbob001 commented 5 years ago

Setting the FireOS audio output setting from auto to something specific like 'stereo' helped with sync issues in hdhomerun. So see if setting making audio options in the os and player fixed would help.

rinoshs commented 5 years ago

This fix is planned for end of Q2. The update should start going out to devices by the end of June.

humiboy commented 5 years ago

And why end oft june and not now release the fix???

Where is the problem after 8 month with no fix?

And this ultimate fix, fixed all streaming problems with the 4K Stick?

justme-justus commented 5 years ago

Dude, i get for every nonsense question of you an E-Mail. Please stop this spamming.

On Mon, 3 Jun 2019, 22:43 humiboy, notifications@github.com wrote:

And why end oft june and not now release the fix???

Where is the problem after 8 month with no fix?

And this ultimate fix, fixed all streaming problems with the 4K Stick?