Its not a big deal, to prevent android auto update. During the begin of fw installation process, unplug the box. The system will think the update corrupt, and will not install again automatically .
I made this in other box.
Of course just own risk…
I totally understand you, but this one is different now, the device needs to be connected to the Internet and will never proceed to the next point. Playing with system apps settings is totally hit and miss and I had to reset the device twice and gone through the same process> I got headache more than any OS I ever tried and spent like two days to debloat the crappy G software that’s installed on this device. And for you this thing might look easier from your perspective than regular Android ATV users
And away from ATV and G software nightmares. Here is 3 modified G1 remote files BT, IR and fully customized gen keymaps to use with the device on CoreElec
G1 remote files
locations of files
*IR file- copy (remote.conf) to main (root coreelec partition) folder of boot media.
*BT file- copy (G1.hwdb) to Storage/.config/hwdb.d/
*keymaps file- copy (gen.xml) to Storage/.kodi/userdata/keymaps
finally restart CoreElec.
2 Likes
have you tried
someone with G1 has and the script did what it was supposed to do but they didn’t really notice any speedup, though no speed down either, would be great for more testers.
Nothing, it just works. So someone need to compare the driver in Linux and find the reason.
1 Like
This is not new, it was always like this, but this mandatory update that initially needs logging to your Google account and is only for updating new ATV Interface/Launcher. It does NOT update Android OS. I have setup two G1 boxes, one last week, and on both it worked like this; after logging to Google account and updating ATV Interface, the first thing I did is disabling the OTA updater app, installed “X-Plore” and Reboot to “Coreelec 5.0” apps needed to install CoreElec.
Now the update includes small change for OTA updater, so the app needs to be restored to its factory rest and disabled, I saw the big OS update multiple times with 695MB size, whenever your device is ready to set up for the first time as a new device or after the process of factory reset of the box
OK, one important thing I forgot to mention, after first boot to Android and setting up successfully Google account, and got to GUI, I immediately disconnected internet connection. Then the next things I did is disabled all apps that could be disabled, among them was OTA updater.
Then preceded with Google apps updating, and installing my two apps. When G1 rebooted to install new ATV UI I noticed that OTA updater cannot be disabled any more, only stopped.
1 Like
Im lucky I didnt even open the Google account needed to turn on into Android. I went to CE 1st 
Last week when I was setting new G1, I was curious if it still comes with original, not blocked, firmware; and it did. So they still have old stock, and if it came with new blocked firmware it would be immediately returned.
2 Likes
I see wired network issues with all NG-CE including the latest nightly version (2024-10-03)
A few times the wire network works OK, but mostly it doesn’t work properly. Especially with every power cycle and restart.
IP address is not obtained correctly, and it doesn’t show online state for network. (ready or failure)
dmesg | paste
paste.coreelec.org/WhiningClinical
CoreELEC:~ # dmesg | grep eth0
[ 8.952464@3]- meson6-dwmac fdc00000.ethernet eth0: fail to init PTP.
[ 8.964676@3]- IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 13.028701@3]d meson6-dwmac fdc00000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
[ 13.028726@3]- IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 890.476062@2]- meson6-dwmac fdc00000.ethernet eth0: fail to init PTP.
[ 893.527982@2]d meson6-dwmac fdc00000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
CoreELEC:~ # ifconfig
eth0 Link encap:Ethernet HWaddr B0:B3:69:10:65:58
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1151 errors:0 dropped:294 overruns:0 frame:0
TX packets:901 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:177430 (173.2 KiB) TX bytes:152816 (149.2 KiB)
Interrupt:16
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:478 errors:0 dropped:0 overruns:0 frame:0
TX packets:478 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:57140 (55.8 KiB) TX bytes:57140 (55.8 KiB)
wlan0 Link encap:Ethernet HWaddr 70:4A:0E:45:8C:32
inet addr:192.168.0.150 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:701 errors:0 dropped:0 overruns:0 frame:0
TX packets:461 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:103459 (101.0 KiB) TX bytes:328735 (321.0 KiB)
CoreELEC:~ # ^C
CoreELEC:~ # ethtool eth0
Settings for eth0:
Supported ports: [ TP MII ]
Supported link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Supported pause frame use: Symmetric Receive-only
Supports auto-negotiation: Yes
Supported FEC modes: Not reported
Advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Half 1000baseT/Full
Advertised pause frame use: Symmetric Receive-only
Advertised auto-negotiation: Yes
Advertised FEC modes: Not reported
Link partner advertised link modes: 10baseT/Half 10baseT/Full
100baseT/Half 100baseT/Full
1000baseT/Full
Link partner advertised pause frame use: Symmetric
Link partner advertised auto-negotiation: Yes
Link partner advertised FEC modes: Not reported
Speed: 1000Mb/s
Duplex: Full
Port: MII
PHYAD: 6
Transceiver: external
Auto-negotiation: on
Supports Wake-on: ug
Wake-on: d
Current message level: 0x0000003f (63)
drv probe link timer ifdown ifup
Link detected: yes
I took pictures that shows the Ethernet adapter state on CE
DHCP (failure connection state with network input/output error message
https://i.ibb.co/sgjwhBt/IMG20241005035027.jpg
Manual IP (ready connection state)
https://i.ibb.co/FhgTn8j/IMG20241005034805.jpg
AUTO (ready connection state with abnormal IP starts with 169.254)
https://i.ibb.co/kq9CrBP/IMG20241005033544.jpg
https://i.ibb.co/2v6DCxh/IMG20241001133440.jpg
Thanks CE team, I really appreciate every bit of your time and efforts to help solve some tech issues.