Hello, I have a HK1 RBOX X4, I followed all the steps, but the display does not work. Can someone help me? Thanks.
Same problem, lan worked, but link Down/Up every 300 sec, usually twice
MAC 02:00:00:00:00:00
I spent now almost a whole week about this JL2xx1 ethernet PHY.
I think already it will be never working 100% for everybody.
So I just can repeat myself: do not buy such cheap no-name hardware!
It’s even worse than the other X… devices on market!
Maybe we go to ignore any request about this chip in future without sources from the vendor how to implement this part of hardware.
There are now about 5 different hardware variations out there about this HK1. So solution will be: donate all of them to the dev team so we can disassemble and fully implement this device.
3 Likes
I confirm functionality X96 X4
Help!!
If I play a video with DTS-MA audio and then try to play a music file, it plays at around 18x speed (no sound, just the progress bar moving very quickly).
If I then play a video with non-HD audio (DTS, MP3 , AAC) and play the same music file, it plays fast at around 1.2x speed. I have to reboot to get back to normal speed music.
Does anyone else have this problem or a fix for it?
HK1RBox S905X4, 2G/16G, 100M, 19.5 nightly.
@emveepee @Dreringer please update your Android firmware. The device I have under test do have set a mac in bootloader environment. Yours not.
So search a firmware until in CE console: fw_printenv mac return a valid result.
Right now I am setting it in autostart.sh to match the Android MAC that gets detected, so it isn’t a major problem, plus with only one device I could live with the one it defaults to for everyone. I am running the current latest firmware 2022.06.20 ota but I will maybe try slimbox since I have read Vontar ah218 version works. If CoreElec had LibreELEC.tv/ethmactool-config at master · LibreELEC/LibreELEC.tv · GitHub from LE I could use the serial number
fw_printenv mac or ethaddr ?
CoreELEC:~ # fw_printenv mac
Error: “mac” not defined
CoreELEC:~ # fw_printenv ethaddr
ethaddr=02:ad:32:01:d0:51
CoreELEC:~ # ifconfig eth0
eth0 Link encap:Ethernet HWaddr 02:00:00:00:00:00
inet addr:192.168.100.19 Bcast:192.168.100.255 Mask:255.255.255.0
Android/Network settings, mac: 02:ad:32:01:d0:51
So wrong firmware, it must be mac.
So a few different hw revisions including multiple different firmwares will cause this chaos.
When you all find the correct firmware I am sure mac is working and eth0 as well.
Hk1x4 and clones/knock offs
ah 212= Hk1x4 1000m
ah 214= TranSpeed x4 1000M
ah 218= Vontar x4 1000M
ah 224=TranSpeed x4s 100m
Ott Tv Box s905x4
*Tv Box s905x4
*Mxiii Pro x4 s905x4
*Magcubic s905x4
Boxes released 2021 most/ all had
8211f
After that well is the Jl2xx
All boxes look the same that rectangle soapdish
Look.
- Unknown Firmware/Hardware
Happy Testing
What firmware are we referring to here? The android firmware?
Yes Android 11 on various boxes
Have tested Vontar and Transpeed on Hk1x4
They are cross compatible
I have 8211f so not affected by jl2xx1
Working 1gbit
Currently i have Vontar img from 08 03 2022 on
Hk1x4
About the clones no idea about ethernet chipset
Firmware can be found 4pda
Happy Testing
This seems to work on my X96_X4 too, the device mentioned above, with stable 1GBit/s connection.
It is hardware rev. 1.3
I just got the Mxiii Pro x4. It is ah232 and I didn’t open it but I assume it is jl2xxx too because the mac is 02:00… in CE to and the Android mac is 02:ad:32
12-31 19:00:06.117 0 0 I : [ 1.934636@1] meson8b-dwmac fdc00000.ethernet: device MAC address 02:ad:32:01:70:2a
To use the Android mac this autostart.sh is working for me with both my jl2xxx devices
ethmac=$(fw_printenv -n ethaddr)
ip link set eth0 down
ip link set dev eth0 address $ethmac
ip link set eth0 up
This is not related to the eth phy. Only to the bootloader environment. I need to check why it’s different to the others as they have mac defined.
I checked different android firmware, official HK1, Vontar x4, x96 x4, and custom Android TV, slimBox. All of them have working stable 1Gb link on Android, but no one have “mac” in the enviroment. Some do not have a MAC address at all in the environment, some have MAC in “ethaddr”.
@emveepee, autostart.sh is working for me too, stable 1Gb link, tnx
@emveepee @Dreringer please try this image without your mac script.
You can confirm now with dmesg | grep mac-addr if the mac is set from uboot environment or not like:
CoreELEC:~ # dmesg |grep mac-addr
[ 0.000000@0] uboot setup mac mac-addr: 90:0e:b3:fc:be:8b
So it’s set here by the var mac, yours should be than like uboot setup ethaddr mac-addr: ....
CoreELEC-Amlogic-ne.arm-20.0-Nexus_devel_20221003093146-Generic.img.gz
Hint: the VFD display should work as well now with this image.
Good news and bad the openvfd service is now installed and working but it still gets the bogus mac. http://ix.io/4caL
@Portisch when I bought the second one I figured if it had the jl2xxxx chip, I could mail one to you or the most relevant developer if you wanted to PM me an address.
Would be option, yes.
[ 0.000000@0] Kernel command line: init=/init console=ttyS0,921600 no_console_suspend earlycon=aml-uart,0xfe07a000 ramoops.pstore_en=1 ramoops.record_size=0x8000 ramoops.console_size=0x4000 loop.max_part=4 loglevel=7 otg_device=0 logo=osd0,loaded,0x00300000 vout=1080p60hz,enable panel_type=lcd_1 hdmitx=,422,12bit
hdmimode=1080p60hz hdmichecksum=0xbc710000 dolby_vision_on=0 hdr_policy=1 hdr_priority= frac_rate_policy=1 hdmi_read_edid=1 cvbsmode=576cvbs osd_reverse=0 video_reverse=0 irq_check_en=0 androidboot.selinux=permissive androidboot.firstboot=0 jtag=disable androidboot.bootloader=01.01.220620.224252 androidboot.hardware=amlogic androidboot.serialno=ah21280566015c1a11b0e androidboot.wificountrycode=US androidboot.rpmb_state=1x1 androidboot.slot_suffix=_b BOOT_IMAGE=kernel.img boot=LABEL=COREELEC disk=LABEL=STORAGE console=tty0 no_console_suspend keymap=us vout=1080p60hz,dis logo=osd0,loaded,0x00300000 frac_rate_policy=0 hdmitx=, hdr_policy=1 quiet androidboot.vbmeta.device=/dev/block/vbmeta androidboot.vbmeta.avb_version=1.1 androidboot.vbmeta.device_state=locked androidboot.vbmeta.hash_alg=sha256 androidboot.vbmeta.size=6912 androidboot.vbmeta.digest=918696b10612ff2e5d2b99ef9840a63d4e1e003204c0fb61cb800d28722086fb androidboot.vbmeta.invalidate_on_error=yes androidboot.veritymode=enforcing androidboot.verifiedbootstate=green
There is no mac or ethaddr in boot parameters defined. The box I have SSH access do read this mac from memory. But in CE kernel it’s not possible anymore since SC2 because of security.
It just read 0x00. But I checked the other HK1 box and might got just an idea. Let me check if it’s somehow possible.
@emveepee please make me a log of your complete bootloader environment with:
fw_printenv | paste