Spotted in the wild: x88 King x922

[greenstone]

Porkie You can turn on developer options in most of these builds and mess with the USB but you need a way to control the box if your mouse/controller is usb connected I think you cant do anything - not sure if I have a controller that will work so I haven't done the firmware again.

[Porkie]

Has anybody tried the app 'USB Host Controler' to see if they can mount devices? Or has anybody tried to switch the USB mode? There are apps that will let you switch USB modes like MPT mode etc.

[Juasser]

greenstone I also feel disappointed with the software but I think it is a good hardware. I want it for more things than multimedia, such as home automation bridge and the features fit what I need. Also the price is very good. I have installed the rom that I put up and the original of the king pro and without problem, except the USB that I keep trying to make them work and remote. If you flash do not check the bootloader option. To use the infrared I use the application of my xiaomi A2 and look for the remote control of the minix, Then I already set up a bluetooth controller to move through the menus

[greenstone]

Juasser I wouldn't mind seeing the gt-king install, I tried and my box got stuck at the bootloader I probably grabbed the wrong rom. I keep looking at what ugoos has done for its box and more and more I am thinking about sending the x88 king back as the vendor gave me the ability to do so.

[Porkie]

I was trying [ROM] Beelink GT-King ALVATECH Standard Android (9.0 Pie) S922X and seems that the only thing that dont works are the usb. I'd tried and Lan, wifi, bt, Ir... and all works, storage show 128Gb too. Would be wonderful if someone can make a patch to make usb works. I downladed an app from play store to see usb devices and seems that both are reconogised but no input or storage devices work. I post the log.


Device Info
Device Path: /sys/bus/usb/devices/usb1/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0002
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 2.00
Speed: 480
Protocol: 01
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

---------------------------------------------------
Device Info
Device Path: /sys/bus/usb/devices/usb2/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0003
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 3.00
Speed: 5000
Protocol: 03
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

Thanks in advance

Did you try going into Developer settngs and turning USB Debug on and off and checking the USB ports? I have had USB not work before, and that solved the problem.

[raruba]

raruba, would be possible patch boot.img from original x88 to ALVATECH rom, or this is a crazy idea?

Its a great ROM, I'm using it on my Beelink GT-King....works great.

[raruba]

raruba, would be possible patch boot.img from original x88 to ALVATECH rom, or this is a crazy idea?

Yeah it shouldn't be that hard, if the only thing that don't work is USB's....should be fairly easy, for him that is....lol

[Juasser]

raruba, would be possible patch boot.img from original x88 to ALVATECH rom, or this is a crazy idea?

[Juasser]

Porkie Thanks for the tip about the keyboard that worked. I renamed the old file in that area to bad-generic and copied over the new file with the proper permissions.


Juasser Was wondering if you can get me the build.props from that rom want to see if we can edit our build.props and "spoof" our box so its recognized as a gtbox for playstore. From what I remember reading on the thread about the gt-king rom there were two roms they made depending on the serial number of the board. I am wondering if we should get that info from our boxes for them.

# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.version.incremental=20191017
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Thu Oct 17 17:20:09 CST 2019
ro.build.date.utc=1571304009
ro.build.type=userdebug
ro.build.user=alvatech
ro.build.host=AT
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=GTKing_AT
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Xiaomi
ro.product.locale=en-US
ro.wifi.channels=13
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191017:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145
ro.expect.recovery_id=0x3b30004511e5d6ee48ed6d9c0a 8d29245154b555000000000000000000000000

[raruba]

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

Hmm replaced these values, cleared the app store cache/storage (including framework and so forth...)

No luck so far.

Greenstone: nice try....keep up the good work, it would be great if the beelink GT-KING firmware would work on the X88 King.

[greenstone]

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

Hmm replaced these values, cleared the app store cache/storage (including framework and so forth...)

No luck so far.

[greenstone]

Juasser Was able to get a build.prop from alvatech rom:


# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.version.incremental=20191017
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Thu Oct 17 15:41:30 CST 2019
ro.build.date.utc=1571298090
ro.build.type=userdebug
ro.build.user=alvatech
ro.build.host=AT
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=GTKing_AT
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei
# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Xiaomi
ro.product.locale=en-US
ro.wifi.channels=13
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191017 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191017:userdebug/test-keys
ro.build.characteristics=tablet
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145
ro.expect.recovery_id=0x3bcc839a9ee7293976ba33f666 4930d935f56c02000000000000000000000000


Here is the build.prop from our boxes:


# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=PPR1.180610.011
ro.build.display.id=galilei-userdebug 9 PPR1.180610.011 20191207 test-keys
ro.build.version.incremental=20191207
ro.build.version.sdk=28
ro.build.version.preview_sdk=0
ro.build.version.codename=REL
ro.build.version.all_codenames=REL
ro.build.version.release=9
ro.build.version.security_patch=2018-08-05
ro.build.version.base_os=
ro.build.version.min_supported_target_sdk=17
ro.build.date=Sat Dec 7 09:43:48 CST 2019
ro.build.date.utc=1575683028
ro.build.type=userdebug
ro.build.user=foxluo
ro.build.host=hugsun
ro.build.tags=test-keys
ro.build.flavor=galilei-userdebug
ro.build.system_root_image=true
ro.product.model=X88King
ro.product.brand=Amlogic
ro.product.name=galilei
ro.product.device=galilei


# ro.product.cpu.abi and ro.product.cpu.abi2 are obsolete,
# use ro.product.cpu.abilist instead.
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.cpu.abilist=armeabi-v7a,armeabi
ro.product.cpu.abilist32=armeabi-v7a,armeabi
ro.product.cpu.abilist64=
ro.product.manufacturer=Amlogic
ro.product.locale=en-US
ro.wifi.channels=
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galilei
# Do not try to parse description, fingerprint, or thumbprint
ro.build.description=galilei-userdebug 9 PPR1.180610.011 20191207 test-keys
ro.build.fingerprint=Amlogic/galilei/galilei:9/PPR1.180610.011/20191207:userdebug/test-keys
ro.build.characteristics=mbx,nosdcard
# end build properties

#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.bionic.ld.warning=1
ro.art.hiddenapi.warning=1
ro.treble.enabled=true
persist.sys.dalvik.vm.lib.2=libart.so
dalvik.vm.isa.arm.variant=cortex-a9
dalvik.vm.isa.arm.features=default
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
dalvik.vm.stack-trace-dir=/data/anr
ro.build.expect.bootloader=01.01.180822.152145

# begin fota properties
ro.fota.platform=S922X
ro.fota.type=box
ro.fota.oem=x88king
ro.fota.device=x88king
ro.fota.version=X88King_20191207-1003
# end fota properties
ro.expect.recovery_id=0x811716e3d7287246acbcf21694 143e8212a9c5e0000000000000000000000000


Here are few areas that are different:

ro.product.model=GTKing_AT ---vs--- ro.product.model=X88King
ro.product.manufacturer=Xiaomi ---vs--- ro.product.manufacturer=Amlogic
ro.wifi.channels=13 ---vs--- ro.wifi.channels=
ro.build.characteristics=tablet ---vs--- ro.build.characteristics=mbx,nosdcard

[greenstone]

Porkie Thanks for the tip about the keyboard that worked. I renamed the old file in that area to bad-generic and copied over the new file with the proper permissions.


Juasser Was wondering if you can get me the build.props from that rom want to see if we can edit our build.props and "spoof" our box so its recognized as a gtbox for playstore. From what I remember reading on the thread about the gt-king rom there were two roms they made depending on the serial number of the board. I am wondering if we should get that info from our boxes for them.

[Juasser]

I was trying [ROM] Beelink GT-King ALVATECH Standard Android (9.0 Pie) S922X and seems that the only thing that dont works are the usb. I'd tried and Lan, wifi, bt, Ir... and all works, storage show 128Gb too. Would be wonderful if someone can make a patch to make usb works. I downladed an app from play store to see usb devices and seems that both are reconogised but no input or storage devices work. I post the log.


Device Info
Device Path: /sys/bus/usb/devices/usb1/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0002
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 2.00
Speed: 480
Protocol: 01
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

---------------------------------------------------
Device Info
Device Path: /sys/bus/usb/devices/usb2/
Device Class: USB Hub (0x9)
Vendor ID: 1d6b
Vendor Name (reported): Linux 4.9.113 xhci-hcd
Vendor Name (from DB): Linux Foundation
Product ID: 0003
Product Name (reported): xHCI Host Controller
Product Name (from DB): not found

Additional Info
USB Version: 3.00
Speed: 5000
Protocol: 03
Maximum Power: 0mA
Serial Number: xhci-hcd.0.auto

Thanks in advance

[Porkie]

Just noticed a weird issue I was having with the box basically the Q and ENTER keys on my minikeyboard arent working right - had to actually change the keyboard input with something someone had on the playstore. Another issue I noticed is that the audio on the box with some movie apps fails unless you turn off and turn the audio back on. Disney+, HBO go and Showtime go seem to have that problem. The CW app doesn't run properly and neither does the CW seed or whatever its called. More time I spend with the box the more I see the issues with it. I have yet to find a game that wow's me, but I dont have a decent android game controller anyway.

For the keyboard the fix is super easy, go to Vendor/usr/keylayout and delete generic.kl. Then go to system/usr/keylayout and copy generic.kl to vendor/usr/keylayout, set permissions and reboot