Android TV - V9 Pie - Link constantly cycling between DOWN and UP, in SLEEP mode

Wistuplu

Regular Contributor
Hello,

My television has a "feature" that will probably go unnoticed to most people.
When the television is in "sleep" mode, the network constantly goes UP and DOWN, in approximately 30 seconds cycles, being mostly UP. It is cabled with CAT5E to an AC86U, that has IPV6 disabled. The network card inside the TV is 100 mbps, and the Wifi on the TV is disabled.

I think it started after the upgrade to Android TV 9 Pie, a few weeks ago. The TV previously ran Android 7. The TV model is Sony XE-9005 from 2017 (probably known as X900E in some parts of the world).

By the way, it was also doing DHCP dance every 30 seconds, which I got rid of by defining the IP inside the TV network settings (FYI, I assigned the TV IP 192.168.17.133. The 192.168.17.x is used for all my devices.)

I wish I didn't care, but it kind of bugs me.
Is there anything I could do, besides mindfulness and breathing exercises ? I guess a "solution"/change (if any) might only come from the TV settings or Sony firmware. But someone might know some hidden Android TV option, app or whatever...

Sorry for spamming here, but I'm convinced there are more people with an Android TV and networking interest in this forum, than networking enthusiast in the Sony forums.

Thank you for reading
Take care
Best regards
W.

See below, the 33 or 34 seconds UP/DOWN cycle ((when the network inside the TV is setup to have a static IP) .
Code:
Jul 28 17:07:07 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Jul 28 17:07:07 kernel: br0: port 1(eth1) entered disabled state
Jul 28 17:07:10 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
Jul 28 17:07:10 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 17:07:10 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 17:07:43 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Jul 28 17:07:43 kernel: br0: port 1(eth1) entered disabled state
Jul 28 17:07:46 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
Jul 28 17:07:46 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 17:07:46 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 17:08:20 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.



See below the cycle with the DHCP dance when the TV is setup to use DHCP (with a static IP defined in the router). (BTW, in this log, the router has "Spanning-Tree Protocol" enabled) :

Code:
Jul 28 02:32:46 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Jul 28 02:32:46 kernel: br0: port 1(eth1) entered disabled state
Jul 28 02:32:49 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
Jul 28 02:32:49 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:32:49 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:32:51 kernel: br0: port 1(eth1) entered learning state
Jul 28 02:32:53 kernel: br0: topology change detected, propagating
Jul 28 02:32:53 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 02:32:54 dnsmasq-dhcp[1227]: DHCPDISCOVER(br0) 04:5d:4b:e8:ad:2a
Jul 28 02:32:54 dnsmasq-dhcp[1227]: DHCPOFFER(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:32:54 dnsmasq-dhcp[1227]: DHCPREQUEST(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:32:54 dnsmasq-dhcp[1227]: DHCPACK(br0) 192.168.17.133 04:5d:4b:e8:ad:2a PF-TV-Eth
Jul 28 02:33:26 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Jul 28 02:33:26 kernel: br0: port 1(eth1) entered disabled state
Jul 28 02:33:29 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
Jul 28 02:33:29 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:33:29 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:33:31 kernel: br0: port 1(eth1) entered learning state
Jul 28 02:33:33 kernel: br0: topology change detected, propagating
Jul 28 02:33:33 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 02:33:35 dnsmasq-dhcp[1227]: DHCPDISCOVER(br0) 04:5d:4b:e8:ad:2a
Jul 28 02:33:35 dnsmasq-dhcp[1227]: DHCPOFFER(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:33:35 dnsmasq-dhcp[1227]: DHCPREQUEST(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:33:35 dnsmasq-dhcp[1227]: DHCPACK(br0) 192.168.17.133 04:5d:4b:e8:ad:2a PF-TV-Eth
Jul 28 02:34:07 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
Jul 28 02:34:07 kernel: br0: port 1(eth1) entered disabled state
Jul 28 02:34:10 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link UP 100 mbps full duplex
Jul 28 02:34:10 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:34:10 kernel: br0: port 1(eth1) entered listening state
Jul 28 02:34:12 kernel: br0: port 1(eth1) entered learning state
Jul 28 02:34:14 kernel: br0: topology change detected, propagating
Jul 28 02:34:14 kernel: br0: port 1(eth1) entered forwarding state
Jul 28 02:34:15 dnsmasq-dhcp[1227]: DHCPDISCOVER(br0) 04:5d:4b:e8:ad:2a
Jul 28 02:34:15 dnsmasq-dhcp[1227]: DHCPOFFER(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:34:15 dnsmasq-dhcp[1227]: DHCPREQUEST(br0) 192.168.17.133 04:5d:4b:e8:ad:2a
Jul 28 02:34:15 dnsmasq-dhcp[1227]: DHCPACK(br0) 192.168.17.133 04:5d:4b:e8:ad:2a PF-TV-Eth
Jul 28 02:34:46 kernel: eth1 (Ext switch port: 0) (Logical Port: 8) Link DOWN.
 

Wistuplu

Regular Contributor
Hello,

Thank you for the pointer. I didn't know about "green ports". And it's difficult for me to assess if I have some, and/or how I could use this knowledge to modify the behavior, even though I just looked at some Cisco doc and Wikipedia. That Cisco doc. says "Energy-Detect Mode—On an inactive link, the port moves into inactive mode, saving power while keeping the Administrative status of the port Up. (...) This mode is disabled by default."
If I understand correctly, it would not explain the "Down" administrative status (or is it a different kind of status that's reported in the log).

On the router, AC86U with Merlin 386.3, on the LAN / Switch Control page, one can only configure "Jumbo Frame" and "Spanning-tree Protocol". Nothing about "green ports".

On the TV, the reference document only mentions "LAN; 10BASE-T/100BASE-TX connector (Depending on the operating environment of the network, connection speed may differ. 10BASE-T/100BASE-TX communication rate and communication quality are not guaranteed for this TV.)". So, nothing about green ports.

Thank you again for your interest
Best regards
 

sfx2000

Part of the Furniture
Try rebooting Android on the TV - port might be in a bad state...

Next thing would be to do a reset of Android, and start over...

After that - might consider using a third party box and not use the internal Android - with "Smart" TV's, I avoid using the internal apps, mostly due to privacy concerns - too many of the vendors are monetizing the telemetry info for viewing habits.
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top