Skip to content
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.

Sign up for GitHub

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

Jump to bottom

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

Closed
kristurek opened this issue Jan 14, 2019 · 159 comments
Closed

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

kristurek opened this issue Jan 14, 2019 · 159 comments

Comments

@kristurek
Copy link

kristurek commented Jan 14, 2019 •
edited
Loading

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
Copy link
Contributor

rinoshs commented Jan 23, 2019

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

@ZHAJOR
Copy link

ZHAJOR commented Feb 1, 2019

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
Copy link

humiboy commented Feb 12, 2019

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

@rinoshs rinoshs mentioned this issue Feb 13, 2019
Closed
@rinoshs
Copy link
Contributor

rinoshs commented Feb 13, 2019

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

@iandarbey
Copy link

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

@humiboy
Copy link

humiboy commented Feb 13, 2019 •
edited
Loading

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
Copy link

humiboy commented Feb 21, 2019

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

@jacotec
Copy link

jacotec commented Feb 24, 2019

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
Copy link

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

@humiboy
Copy link

humiboy commented Feb 24, 2019

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
Copy link

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

@humiboy
Copy link

humiboy commented Feb 24, 2019

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
Copy link

when comes the fix out?????

@rinoshs
Copy link
Contributor

rinoshs commented Feb 25, 2019

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
Copy link

humiboy commented Feb 25, 2019

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
Copy link

iandarbey commented Feb 25, 2019 •
edited
Loading

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
Copy link

humiboy commented Feb 25, 2019

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

https://youtu.be/zYwLW86i1yo

@iandarbey
Copy link

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

@humiboy
Copy link

humiboy commented Feb 27, 2019

@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
Copy link

@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
Copy link

humiboy commented Mar 1, 2019

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

In amazon to review the product no developer read this.

@humiboy
Copy link

humiboy commented Mar 6, 2019

@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
Copy link
Contributor

rinoshs commented Mar 7, 2019

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
Copy link

humiboy commented Mar 8, 2019

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
Copy link

@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
Copy link

jacotec commented Mar 8, 2019

@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
Copy link

humiboy commented Mar 8, 2019 •
edited
Loading

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
Copy link

humiboy commented Mar 18, 2019

@rinoshs

any news from the chipset vendor?

@humiboy
Copy link

humiboy commented Mar 30, 2019

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?

@flokic
Copy link

flokic commented Jun 23, 2019

For me, somehow, lately, 4k stick started to work lil better, until 6.2.6.4 update came with only one system components after it, so i'm with NS6264/ 1995 and now is a lot worse then before for smart IPTV and also huge problems started when watching movies on Prime, where deinterlace problems also appears, wich is unacceptable and never did it before! Still waiting the second system components update, maybe this'll be fixed. So, YES, i think we are a lot more those for whom the 4k stick is not working!

The issue you had with deinterlacing in Prime, I've had yesterday as well, for the first time ever, on my 2015 samsung smart tv prime video app! Nothing to do with this update but hey let's blame this update for everything plus the bad weather.

@Arcitec
Copy link

Arcitec commented Jun 24, 2019 •
edited
Loading

Found this file, didn't work before, works now, perfectly:
https://drive.google.com/open?id=1VxL4EtUDfourOqDudo5glVzGbzpukKBw
My gramps is happy now! I'm happy for him!

Okay my celebrations are over...

@rinoshs

Here is a video showing that deinterlacing still crashes in the new OS update:

https://vimeo.com/344003267

The update improved the situation for a lot of channels, solving many of them completely, and has now made the image nicely deinterlaced. But there are SOME channels (certain bad video data) that can still crash the player. Most likely there's some problematic/buggy/corrupt video streams in these channels, which confuses the decoder and crashes it...

Here I am playing the "https://drive.google.com/open?id=1VxL4EtUDfourOqDudo5glVzGbzpukKBw" test file, and after a while the whole hardware decoder crashes and the hardware becomes unusable (cannot play videos) until rebooted.

Please submit the linked file (from google drive) to the team. Use the download-link from the hidden top-bar (hover over it) on the Google Drive page, and get the raw TS file. When they've played the file for about 40 seconds (to the end of the linked video), the hardware decoder crashes.

I described my OS update history in my previous posts above. But here it is again:

Fire OS 6.2.6.4 (NS6264/1995)
Fire TV Home Version 6.1.6.0-727

PS: My FireTV 4K unit was bought in June 2019 so is presumably the latest hardware revision.

@Arcitec
Copy link

Arcitec commented Jun 24, 2019 •
edited
Loading

Can someone capture a 3 minute TS file from channels that crash their fully updated FireTV?

Look at your M3U playlist in a text editor and find one of the crashy channels. Then run this command on a computer (with ffmpeg installed):

ffmpeg -i "the video url" -codec copy -t 00:03:00 test.ts

Share it with us and let’s all test the bad channels!

@rinoshs rinoshs closed this as completed Jun 24, 2019
@rinoshs
Copy link
Contributor

rinoshs commented Jun 24, 2019

@VideoPlayerCode
Could you a open a new ticket with the specific content that is not playing?

@leone007
Copy link

leone007 commented Jun 24, 2019 •
edited
Loading

@VideoPlayerCode

Here and here for the cause.

Fire OS 6.2.6.4 (NS6264/1995)
Fire TV Home Version 6.1.6.0-727

@y2000j

some of the processor cores are nearly on full capacity

Exactly, one of the cores jumps to 100%. And I can confirm that y2000j's sample freezes my FTS4K.

@y2000j
Copy link

y2000j commented Jun 24, 2019

@VideoPlayerCode @leone007
For me for example that stream isnt working.
Here

I use Fire OS 6.2.6.4 (NS6264/1995)

After the picture freezes, i cant watch anything until i restart the 4k stick. When is start the problematic stream, some of the processor cores are nearly on full capacity.

I have only a handful of streams who force that problem. But if the problem happens, you cant watch anything until restart.

Till now, 2 days after the 1st component update, i did not receive the 2nd component update. So i think we have to wait until it is fixed finally.

Maybe we should open a new ticket, cause the ticket here is closed.

@gb160
Copy link

gb160 commented Jun 24, 2019 •
edited
Loading

I really don't understand why this has been closed.

It gives the impression that the problem has been solved by this fix when it clearly hasn't.

It would also be good to hear from someone at Amazon why some people are updated to 6.2.6.4 (NS6264/1996), yet some are still on 6.2.6.4 (NS6264/1995), and clear this up once and for all.

@y2000j
Copy link

y2000j commented Jun 24, 2019

@gb160
I dont even know too, why it is closed. For me it is interesting too if the problem lasts with version 6.2.6.4 (NS6264/1996).

@dougie175
Copy link

Only thing I can think is the Fire Stick I have on 1996 when the rest are on 1995 is slightly older stick so possibly to do with different hardware?

I can confirm neither 1996 or 1995 work and better for me though

I also don't really understand why it has been closed, I understand some of the issues have been fixed as per VideoPlayerCode's post but it is far from fixed overall.

@iandarbey
Copy link

Shouldn’t have been closed till a majority were on /1996 with no more component updates available..... i.e. all on the same page and with the same things working or not.

@gb160
Copy link

gb160 commented Jun 24, 2019 •
edited
Loading

@leone007
I compared the mediainfo for your files that cause the issue mate, and they are IDENTICAL to my files/streams that cause the freezing issue my end.

@dougie175
Copy link

I too can confirm the same with cores hitting almost max when freeze happens.

Please everyone don't get your hopes up thinking 1996 is the saviour as I honestly think you will be disappointed unfortunately. I don't believe 1996 fixes anything 1995 didn't

@leone007
Copy link

leone007 commented Jun 24, 2019 •
edited
Loading

@dougie175

Only thing I can think is the Fire Stick I have on 1996 when the rest are on 1995 is slightly older stick so possibly to do with different hardware?

Mine was ordered last Friday man :) and I'm on 1995.

@gb160

I compared the mediainfo for your files that cause the issue mate, and they are IDENTICAL to my files/streams that cause the freezing issue my end.

No way man. My 2 samples are different.

Eurosport HD

Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Top Field First
Bits/(Pixel*Frame)                       : 0.152

Eurosport 2 HD

Scan type                                : MBAFF
Scan type, store method                  : Interleaved fields
Scan order                               : Top Field First
Bits/(Pixel*Frame)                       : 0.171

And for the record, @y2000j 's sample

Scan type                                : Interlaced
Scan type, store method                  : Separated fields
Scan order                               : Bottom Field First
Bits/(Pixel*Frame)                       : 0.117

@gb160
Copy link

gb160 commented Jun 24, 2019 •
edited
Loading

@leone007 Ahhh, I only checked the Eurosport2 one, I presumed they would be the same.

@iandarbey can you make a test clip and upload it somewhere mate?
ffmpeg -i "the video url" -codec copy -t 00:03:00 test.ts
I think your streams will have different media info but would like to check.
Would also be interesting to see if you can play the problematic files posted by @leone007 and report your findings.

@dougie175
Copy link

dougie175 commented Jun 24, 2019 •
edited
Loading

@dougie175

Only thing I can think is the Fire Stick I have on 1996 when the rest are on 1995 is slightly older stick so possibly to do with different hardware?

Mine was ordered last Friday man :) and I'm on 1995.

@leone007 That's my point mate I am thinking the older sticks may need another update i.e 1996 where as the newer sticks like your's and most of mine 1995 had everything required?

@leone007
Copy link

@dougie175 sry man, my bad, read too fast 🤣 I have a FTS4K ordered in 2019 February, that is 1995 too.

@dougie175
Copy link

@leone007 I would imagine mine on 1996 was bought around then. Either way I honestly think the 1996 bit is irrelevant as it crashes exactly the same as the rest of my stick do and always have lol

@gb160
Copy link

gb160 commented Jun 24, 2019

Oh well lads, on the positive side, only another 5 months 29 days to wait until we're likely to see another attempted fix by Amazon.

@leone007
Copy link

leone007 commented Jun 24, 2019 •
edited
Loading

@gb160 As I said

by the time we come out with a fix - or at least something that reminds of a fix - the product life cycle will reach its end, so we can release something new.

@dougie175
Copy link

@gb160 I really hope not my wife will castrate me if it doesn't start working soon I've been promising her the fix is coming soon so she can watch TV without massive frame skips due to software decoding!

I took the bold step to put TV's all around the new house without a traditional TV aerial's so the only way you can watch live TV in my house is through the HDHomeRun via the Fire Stick's I did this because the fix was "coming by the end of Q2"

@leone007
Copy link

And as I said:

Basically we use this device with a TV right? TVs have built-in high quality de-interlacing, if they detect 1080i signal. The best thing would be to be able to switch to 1080i with the FTS4K, and let the TV's superior hardware deal with the de-interlacing.

1080i as available resolution for FTS4K would solve this whole hassle.

@y2000j
Copy link

y2000j commented Jun 24, 2019

I ordered my fire tv 4k stick on November 2018 and the version is (NS6264/1995)

@leone007
Copy link

leone007 commented Jun 24, 2019 •
edited
Loading

@dougie175 if you wanna keep your balls, buy some cheap S905 or S912 sticks/boxes, install CoreElec, set the GUI to 1080i, and there you go, your TVs will do the de-interlacing (and in better quality than FTS4K could ever do). Also install HDHomerun kodi add-on, or whatever PVR add-on you need.

Amazon Prime Video, and Netflix will be 720p unfortunately as this can be only SW decoded under linux and these cheap SoCs dont have the horsepower to SW decode 1080p.

OR

Buy a PC with nVidia 1660 Ti, install linux, build a tvheadend with latest NVENC API and transcode your HDHomerun streams to H265 1080p 50 fps. This way you can keep and use your FTS4Ks. :)

@dougie175
Copy link

@y2000j Ok that blows any age related theories out the water I would say as the one I have running 1996 is definitely newer than that. I am not sure what is the deciding factor for the upgrade to 1996 then.

@dougie175
Copy link

dougie175 commented Jun 24, 2019 •
edited
Loading

@dougie175 if you wanna keep your balls, buy some cheap S905 or S912 sticks/boxes, install CoreElec, set the GUI to 1080i, and there you go, your TVs will do the de-interlacing (and in better quality than FTS4K could ever do). Also install HDHomerun kodi add-on, or whatever PVR add-on you need.

Hi Mate

Thanks for the suggestion, the problem is I also need the following apps installed and working which I don't think is possible with a normal Anroid / Linux box's in the UK: BBC iPlayer, ITV Hub, ALL 4 and MY5 as I don't actually have a DVR as such she relies on catch-up services.

@leone007
Copy link

@dougie175 I edited my comment with a different option :) I'm going to go down on the second road. Also please read this. All the services you mentioned has a kodi add-on AFAIK.

@dougie175
Copy link

Buy a PC with nVidia 1660 Ti, install linux, build a tvheadend with latest NVENC API and transcode your HDHomerun streams to H265 1080p 50 fps. This way you can keep and use your FTS4Ks. :)

This I can kind of already do via my plex media server it transcodes the HDHomeRun, but the navigation of the guide is awful the whole thing becomes so slow to use, this is what made me switch from Roku's with Plex to Fire Sticks with Channels app as the guide and channel switching was fantastic, as close to a traditional TV as possible

@leone007
Copy link

@dougie175 OK, just to save them ballz, buy an Apple TV 4K for the wife.

@amzn amzn locked as off-topic and limited conversation to collaborators Jun 24, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests