Observer

Constant buffering issues

I have found, for the most part, that the app is unusable. I have this on my PC (which is connected via ethernet directly to the modem), using Chrome, Microsoft Edge and Firefox.  It makes no difference.  Every few seconds, the picture is buffering.  

 

Before it is suggested..  I have updated Flash Player, cleared cookies, enabled hardware acceleration in Flash, then disabled hardware acceleration in Flash.  

 

I have also accessed the app via Roku and my iPad with same results.

 

So, is there a troubleshooting item I may have missed?  I love the idea of using this app, but I want to be able to actually use it.

16 REPLIES
Community Manager

Re: Constant buffering issues

@MCD73

 

What speed is your current service and when was the modem last restarted?  

 

James M.
Social Media Customer Care
Community Forums Moderator

 

Observer

Re: Constant buffering issues

I have the 60/5 (sppedtest actually shows 70 dl) and I did restart my modem to clear its cache.  

Community Manager

Re: Constant buffering issues

Thanks.  

 

Please forward us your account information using this private message link at Forums_Help so we can investigate further.  

 

James 

Observer

Re: Constant buffering issues

Sent

Highlighted
Expert

Re: Constant buffering issues

copy and paste the modems signal level and error log pages . DO NOT RESET IT, WE NEED TO SEE REAL HISTORY.... There is no Cache in a modem to be reset and virtually none in a router either.

 

Boz
Sharer

Re: Constant buffering issues

For whatever reason, the TWCTV/SpectrumTV app needs a better/more stable internet connection to work well than other apps/services.  For example, Netflix might work perfectly from you device/internet connection, but the TWCTV/SpectrumTV app might not.

 

I use the TWCTV/SpectrumTV app successfully every day, and my internet speed is only 30/5, but I did have TWC come out last November to get everything working as well as possible with my internet connection.

 

So, I suggest that you do as MsRaye requests to see what might need to be done to improve your internet connection.

Expert

Re: Constant buffering issues

need to verify the coaxial side is good... 1 channel with ingress can cut your speed to nothing when bytes are corrupted.

 

Observer

Re: Constant buffering issues

TimePriorityDescription
2017-1-26, 00:36:17Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:17Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:18Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:21Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:22Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:25Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:28Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:29Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:31Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:32Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:34Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:35Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:43Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:44Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:45Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:46Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:50Critical (3)SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:36:59Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
2017-1-26, 00:37:36Critical (3)DHCP FAILED - Discover sent, no offer received;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
2017-1-25, 23:38:24Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
2017-1-25, 23:38:29Critical (3)No Ranging Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
2017-2-1, 19:47:49Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-2-9, 16:36:32Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-2-26, 14:03:59Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-8, 15:38:15Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-14, 13:32:41Critical (3)Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-14, 13:33:13Critical (3)Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-14, 06:33:49Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:39Critical (3)SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
1970-1-1, 00:00:42Notice (6)WiFi Interface [wl0] set to Channel 3 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:42Notice (6)WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:N/A) - Reason:INIT
1970-1-1, 00:00:47Notice (6)Honoring MDD; IP provisioning mode = IPv4
1970-1-1, 00:00:49Warning (5)DHCP WARNING - Non-critical field invalid in response ;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.0;CM-VER=3.0;
2017-3-17, 09:32:56Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-17, 09:32:56Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-17, 09:33:07Notice (6)Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
2017-3-17, 10:33:20Error (4)Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
2017-3-17, 10:33:20Error (4)Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=10:da:43:9d:0f:69;CMTS-MAC=00:17:10:8b:8c:8d;CM-QOS=1.1;CM-VER=3.0;
Observer

Re: Constant buffering issues

Show Statistics
 
System Up Time       00:42:15
PortStatusTxPktsRxPktsCollisionsTx B/sRx B/sUp Time
WANLink Up56591315966063288664400:40:54
LAN11G/Full189176132599084246800700:41:38
LAN21G/Full00:41:38
LAN3Link Down--
LAN4Link Down--
WLAN/2.4G289M72847911041859300:42:15
WLAN/5G1.3G67157604057355900:42:15