Posts by kostaman

Quote from trogggy

Gotcha. But in this case he did say ' I have Beelink Mini MXIII ...'
If someone says that I'm going to assume they have a Beelink Mini MXIII - if not it's their problem

I have to tell you on at least 20 posts in the past , members have named their Black UN BRANDED box
Beelink MiniMx because the sellers sold it to them with that name.
Google beelink minimx s905 and see my point.
Asking the question Un Branded confirmed they had the Broadcom Chip Un Branded Box.
Because it is Manufactured by Beelink , there's nothing wrong with that.
Again it is Chinese Branding mixing up names with numerous boxes with different specs.

Quote from trogggy

Identifying a minimxiii should be pretty straightforward

My point is that a Member asking for help with MiniMx as their Box to seek help is what causes confusion for me.
I never know which of the 2 boxes a member has when they post MiniMx as their Box.
Both boxes are made by Beelink with Nexteon Boards but have minor differences in Hardware (wifi chip) AND DIFFERENT
Firmware.

Quote from trogggy

For comparison my minimxiii (ie branded) returned this:

I have had this issue with identifying a MiniMx during the last 12 months with members not being specific as to
what MiniMx they have.
I never use Beelink MiniMx when posting and always use Un Branded MiniMx S905 along with the ram and memory size to make it clear.
Looks like the Branded Box uses Realtek.

Quote from libredark

Are you shure?
I think my box have Broadcom wifi chip.

I have never used Realtek device trees for my MiniMx S905 2g/16g non branded on casing.

Please SSH into your box and run

udevadm info /sys/bus/sdio/devices/sdio*

This is my result below. Broadcom Wifi.

LibreELEC (community) Version: 7.0.3.012j
LibreELEC:~ # udevadm info /sys/bus/sdio/devices/sdio*
P: /devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DEVPATH=/devices/d0070000.sdio/mmc_host/sdio/sdio:0001/sdio:0001:1
E: DRIVER=bcmsdh_sdmmc
E: MODALIAS=sdio:c00v02D0d4330
E: SDIO_CLASS=00
E: SDIO_ID=02D0:4330
E: SUBSYSTEM=sdio
E: SYSTEMD_WANTS=brcmfmac_sdio-firmware-aml.service
E: TAGS=:systemd:
E: USEC_INITIALIZED=7555091

Quote from ojerez

Hello I have a Beelink Mini MX III and I can not get the ethernet connection LibreElec 8. On the router itself does not turn on the light of the connected ethernet port. I restarted several times and nothing. Other times, after a few reboots, I get it to detect it, but this time there is no way. What I can do?
Thank you

Whilst the box is on pull the ethernet cable out and plug back in until you see it detected by router.
It may take a few in and out with cable.
When detected you have to reboot box.
It only happens when power is un plugged from box.
I am on [7.0.3.012j] and it never happens anymore.
It used to happen on previous early versions.
Maybe the ethernet module loading problem for this box has re surfaced.

Quote from CanBert

I assume a new wireless chip inside....anyone know what app that is that shows the hardware info?

Try ssh issue below and see results.

udevadm info /sys/bus/sdio/devices/sdio*

Also try

mkdir -p /tmp/system
mount /dev/system /tmp/system
find /tmp/system -name *.ko

I just copied the remote.conf
from sd card after flashing LE sd card install.
I have a working remote except the volume button Volume UP does nothing and Volume DOWN takes me back to the beginning of a movie file during playback.
This volume button seems to navigate through my skin back and forward using volume up and down .

I used Keymap Editor to assign the volume up and down presses and it worked whilst i was using the GUI.
During playback it failed with above mentioned result.

So i can only use volume up and down before i start a movie. When i start a movie the volume up and down assigned using Keymap Editor fail to stick.

Someone help me out on this one greatly appreciated.

EDIT: Just tried Keymap Editor Fullscreen Video Menu and found Audio in there.
Assigned and it works during Playback.

#*********************************************************************************************************
#this file is configuration for each factory remote device
#     work_mode      0 :software mode  1 :hardware mode 
#    repeat_enable      0 :disable repeat 1 :enable repeat    
#
#    factory_code      each device has it's unique factory code. 
#              pattern:custom_code(16bit)+index_code(16bit)
#              examble: 0xff000001 = 0xff00(custom cod)  0001 (index)
#
#    release_delay      unit:ms.release will report from kernel to user layer after this period of time
#              from press or repeat triggered. 
#
#    debug_enable      0 :debug disable  1 :debug disable
#
# SW MODE:
#    bit_count      how many bits in each frame      
#    tw_leader_act      time window for leader active 
#    tw_bit0          time window for bit0 time.
#    tw_bit1          time window for bit1 time
#    tw_repeat_leader  time window for repeat leader
# REG
#    reg_base_gen      set value for PREG_IR_DEC_BASE_GEN    
#    reg_control      set value for PREG_IR_DEC_CONTROL
#    reg_leader_act      set value for PREG_IR_DEC_LEADER_ACTIVE
#    reg_leader_idle      set value for PREG_IR_DEC_LEADER_IDLE
#    reg_repeat_leader set value for PREG_IR_DEC_REPEAT_IDLE
#    reg_bit0_time      set value for PREG_IR_DEC_BIT0_TIME
#************************************************************************************************************* 
#amlogic NEC remote
factory_code    = 0xfe010001 
work_mode          = 0
repeat_enable = 1
repeat_delay = 40
repeat_peroid = 39
release_delay    =    121
debug_enable     = 1


fn_key_scancode    = 0x00
left_key_scancode  = 0x51
right_key_scancode = 0x50
up_key_scancode    = 0x16
down_key_scancode  = 0x1a
ok_key_scancode    = 0x13
pageup_key_scancode = 0x55
pagedown_key_scancode = 0x54


mouse_begin
        0 0x51
        1 0x50
        2 0x16
        3 0x1a
mouse_end


key_begin
        0x01 11
        0x4e 2
        0x0d 3
        0x0c 4
        0x4a 5
        0x09 6
        0x08 7
        0x46 8
        0x05 9
        0x04 10
        0x13 97
        0x19 15
        0x42 14
        0x16 103
        0x1a 108
        0x51 105
        0x50 106
        0x18 104 
        0x11 102 
        0x4c 125 
        0x10 109 
        0x5a 119
        0x59 122
        0x52 128
        0x58 123
        0x54 120
        0x55 121
        0x40 116
        0x41 113
        0x45 467 ;# SET_DISPLAY 130  G5_F2_NONE  display setup
        0x49 20 ;# T 134
        0x0a 31 ;# S 133
        0x48 38 ;# L 138
        0x4d 466 ;#new add UI_MOVIE ;old explorer 70  G5_F7_FILE
        0x0e 48  ;# B 136
        0x0f 44 ; # Z 142 ;# apps    
        0x43 469 ;# SETTINGS          G5_F4_SETUP
        0x03 468 ;# SET_ADVANCED 127  G5_F3_NONE    more setting
        0x06 70 ;# EXPLORER 139
        0x44 50 ;# M 140
        0x00 63
key_end
repeat_key_begin
        0x01 11
        0x4e 2
        0x0d 3
        0x0c 4
        0x4a 5
        0x09 6
        0x08 7
        0x46 8
        0x05 9
        0x04 10
        0x13 97
        0x19 15
        0x42 14
        0x16 103
        0x1a 108
        0x51 105
        0x50 106
        0x18 104
        0x11 102
        0x4c 125
        0x10 109
        0x5a 119
        0x59 122
        0x52 128
        0x58 123
        0x54 120
        0x55 121
        0x40 116
        0x41 113
        0x45 467 ;# SET_DISPLAY 130  G5_F2_NONE  display setup
        0x49 20 ;# T 134
        0x0a 31 ;# S 133
        0x48 38 ;# L 138
        0x4d 466 ;#new add UI_MOVIE ;old explorer 70  G5_F7_FILE
        0x0e 48  ;# B 136
        0x0f 44 ; # Z 142 ;# apps    
        0x43 469 ;# SETTINGS          G5_F4_SETUP
        0x03 468 ;# SET_ADVANCED 127  G5_F3_NONE    more setting
        0x06 70 ;# EXPLORER 139
        0x44 50 ;#  M 140
        0x00 63


repeat_key_end

Updated today from .007
S805 - MXQ.arm 7.0.3.3c Internal Install
All Black MXQ, Board number:'AM_MXQ_A 20150825

Runs as good as any S905 box i own.

Great work kszaq

Quote from kszaq

I'm sorry but I will not change anything related to audio/video playback in 7.0 builds.

Thank God for that. I just Update through the Alphabet Versions waiting for something Bad to happen. I don't seem to have a lot of these issues reported by some. I just update to see what happens.

My only issue is all my S905 Chip boxes DONT freeze anymore using temperature sensor ENABLED. HA!

Quote from kwapa

It works for me. Have you changed the name of gxbb_p200_2G_1Gbit.dtb file?

To be more clear.
Download a device tree as instructed and rename it to dtb.img. Copy the renamed file to main folder of SD card/USB drive - replace the one that's already there.
#1

I had 2 TX5Pro s905x boxes brick.
#807

I've sent them back to supplier for testing hardware.
I will report back with response.

Quote from relatek

Please, kszaq, kostaman... Can you help me?

I don't have this box. I only asked if it worked.

Quote from beeasy79

so what i got then is LibreELEC-S905.arm-8.0-8.0.0c.img and gxbb_p200_1G_mxq_pro_4k.dtb and for tools to use i have Win32DiskImager-0.9.5-install or LibreELEC.USB-SD.Creator.Win32 or rufus and i also found this tutorial

Sorry i use a Mac OS so i will let others help you with this.

Quote from charlie

whats the advantage with the temp disabled version?

Used only if box freezes when powering on.
Mainly occurs with S905 Chip Boxes but seems to have disappeared on a lot of those boxes after 7.0.012g version.
Read #1

Quote from mmpp

Conclusion: If you are interested in cpu-bound applications on your device, like software decoded video, emulation and games, pick the S905 over the S905X.

Thanks.
I only purchased one s905x and am a little more critical than you.
I will not purchase one of these again.
"4K VP9 hardware decoding"? I couldn't be less interested.

Quote from Pelican

There are very shitty boxes with S905 even with fake RAM chips

My TX5Pro's that SH#T themselves have Samsung RAM. Qualcomm wifi Blah Blah.
I'm just making a point on the Board.
The Board looks like recycled Dogsh#t .
2 sided circuit board.
Enough! Start a new thread if you want to take this further.

Quote from Poida

Have you tried shorting the nand pins to erase / reset it?

2 sided circuit board i cant see any numbers or know of schematic diagram.
Supplier asked for me to send them back to "Shenzhen Sally" who will get her Engineer "Hong Kong Harry"
to tell me what happened? I will report back.

Read This as well #1
mmpp thanks.

Quote from kostaman

Strange thing just happened to my
TX5 Pro s905x 2gb/16gb with Qualcomm QCA9377
LE Internal 7.0.3.012h

Red light on but not turning on via remote or un plugging power supply and re plugging to power.

Red light comes on and stays on when power is connected.

Tried Android SD Card firmware using toothpick recovery method with no results except red standby light.

My first Bricked box. I've never bricked a box in years of testing , not even an all black MXQ S805.

Second Tx5Pro S905x chip box just Sh#t itself with the same issue.

I'm DONE with the the S905X Chip Boxes.

I've researched a bit more on why these S905X Boxes are cheaper than S905 Chip Boxes and discovered the Circuit Boards are the first
crap shortcut in Quality and that is a Major no no for me.
Link #149
I'm not going to go on Just Google s905x circuit boards and read on.
[hr]

Quote from kszaq

Sure. Added as requested. I will keep them in a separate folder though because the same device trees are for 8.0 builds.

Thanks.

Quote from kwapa

I have checked the LIBREelec 7.0.3.12i with the device tree gxbb_p200_2G_1Gbit.dtb installed on a clean SD card for testing (as per kszaq's suggestion) in my KIII device. I am confirming as follows:
1. That device tree is correct & works with KIII.

Quote from kwapa

LIBREelec 7.0.3.12i works without problems.

I have had 2 TX5Pro S905X boxes Sh#t themselves in the last 2 weeks and upon opening them the first thing i noticed is what Crap Circuit Boards are used with these new chips. Seriously bad sandwich boards with a Murky Resin Finish.
I am done with these S905X Chips Boxes and now know why they are cheaper than the s905 Chip Boxes.

Sorry had to get that out.

Question is , is this KIII Sorted for you ?