All samples I use for testing are from: https://kodi.wiki/view/Samples
ISO-full3D-sample.iso
Portisch⌠sorry for the late reply. was outta town for a bitâŚ
anyways currently its working on both. the sources are still private as the project is not done yet and may be introduced in different manner then CE and LE and till its complete i canât say for sure yet. Currently its working along with some other S912 based devices on a mainline 5.1 kernel that has some proprietary blobs enabling the graphics stack on bot the S922 and S912âs devices being tested. I wonât know till the projects done and discussions with the funders can take place.
in the meantime i noticed you guys finally got a new custom bootloader happening which is good.
I have used a custom loader for along time now and its great because then you can enable most of the hardware prior to linux coming up making things much easier to get going.
Personally i still think the N2 is better built from a board manufacturing point but still the GT King looks not to bad.
My main focus right now tho is on the Dreambox One as they are really nice and my work on it was kinda why i got asked to look at the GT-King to begin with.
Iâve been following and forked most of the current gits reqarding the move to mainline just to stay up to speed were they are but not really interested at this point in helping Amlogic fix problems they should have fixed themselves along time ago. but my feelings may change down the road, who knows.
On another note: Recently i did clone the CE github and have been messing with the 9.2 branch and trying to add in some support for a number of devices including a beelink project i have got going and once i figure out a few more things about the CE build system may look at trying to upload some stuff. The way they keep changing the build system is hard to keep up on without spending more time then i really want. both CE and LE are a lot more complicated these days then when they forked from OE and i use a different build system.
1 Like
@broleke we are working on a trouble free method for users to be able to flash our custom bootloader.
Most things are working but without our custom bootloader then you are left in the same situation as with other older generic Chinese devices with no working CEC/WoL/Sleep/Wakeup etcâŚ
1 Like
thanks for your feedback 
good to know that progress are made.
could you explain why the custom bootloader help with those features ? is it not the kernel job to handle this ?
Bootloader comes before the KERNEL is loaded and initiates various hardware so that the kernel can spot them. Its a bit like a BIOS.
Shoog
thanks, I wasnât aware of this.
Is it safe to already order a Beelink King GT, meaning an easy way to install coreelec is almost guaranteed? Or should I wait until it is done?
Itâs not ready yet.
So I have now created an image that can be flashed to a USB stick or SD-card which will flash the bootloader on the Beelink device with our custom one, itâs completely n00b proof, following this users will be able to burn/run our normal CoreELEC image as usual.
We didnât want to rely on autoscript which is what is used to boot CoreELEC on older devices and instead we wanted to be able to use cfgload on this device which is what we use on SBCâs like the N2.
3 Likes
I am ready to test it!
There is no point in testing it yet as installing the custom bootloader at this point would serve you no purpose as it will not change your Android experience.
Duly noted.
Hi @anon88919003, what does the team think about the chance to get the internal WiFi and BT to work?
At the moment it doesnât work but we do have the drivers so we should be able to in the future, I already tried to spend some time on this and have some ideas, unfortunately everyone is short for time at the moment and we have issues to deal with on other devices also.
Nice what is the chipset? Does it have any kind of mainline support?
I canât remember the exact chip number but no and Iâm not sure on any mainline status.
According to a review found on internet, it should be: AP6356S
If it is correct, then it is a good info because it should already have mainline support
Yes, it is the AP6356S.
Update:
Wifi is working.
We have also got the idle temperature reduced by at least 10 degrees and the GT-King is now idling at 43-44oC.
Framebuffer text is now displayed during initial boot/updates.
There is an issue with our custom bootloader where Android will not boot, 4K H265 also does not play, still no bluetooth (yet).
6 Likes