[ROM] Android TV (7.1.2) Beelink GT1 (Multi 6255 & 9377 Standard+Ultimate)

[tillaz87]

Nope..

Seemed to flash OK, but still had the E: [] Unknown Command error at the end
Rebooted but stuck on the Google animation. Pulled power and tried again, but still sticking at animation
At least it booted this time.

Nothing more I can do about this everything has failed. no idea why 706D hardware defaults to 2GB as the other 3GB devices are fine.
maybe it is fake 3GB who knows, beelink are bad AX12 have faulty GPU as well

[Andrewdroid]

Nothing more I can do about this everything has failed. no idea why 706D hardware defaults to 2GB as the other 3GB devices are fine.
maybe it is fake 3GB who knows, beelink are bad AX12 have faulty GPU as well

I disagree.
I have 3/32 ultimate with AX12 serial number and all (icl 3d games and benchmarks) work fine.

[Winno]

Nothing more I can do about this everything has failed. no idea why 706D hardware defaults to 2GB as the other 3GB devices are fine.
maybe it is fake 3GB who knows, beelink are bad AX12 have faulty GPU as well

Thanks for trying.

[tillaz87]

I disagree.
I have 3/32 ultimate with AX12 serial number and all (icl 3d games and benchmarks) work fine.

Lots of people have reported broken 3D with AX12 on here, and beelink forums. Its a well known thing. Just because yours is not effected does not mean there is no problem. in fact your the first I've seen say otherwise vs the 30+ complaints on beelink's forum.

Now the fact that you say you don't have any problem with 3D on AX12 just further proves its nothing to do with firmware.. so must be bad hardware batch

[tillaz87]

Beelink have more hardware configs for the GT1 than actual products

[mperreir]

Hello tillaz87 . Small question : where is the xpad.ko kernel module in this new version (v10) of your rom ? Is it built in in the kernel ? In previous versions it was in /system/lib and could be easily replaced (I have some Thrustmaster XID xbox 360 gamepads that are not listed in the defautl xpad.ko, I had to binary patch the module to add my vendor and device ID). Now I can't find it in /system/lib but when I try to insmod my module dmesg tells me that the module is already loaded... (still it does not show up in lsmod).
Now my gamepads are not working anymore and my kids are not really happy ;-)

[tillaz87]

Hello tillaz87 . Small question : where is the xpad.ko kernel module in this new version (v10) of your rom ? Is it built in in the kernel ? In previous versions it was in /system/lib and could be easily replaced (I have some Thrustmaster XID xbox 360 gamepads that are not listed in the defautl xpad.ko, I had to binary patch the module to add my vendor and device ID). Now I can't find it in /system/lib but when I try to insmod my module dmesg tells me that the module is already loaded... (still it does not show up in lsmod).
Now my gamepads are not working anymore and my kids are not really happy ;-)

Tell me the vendor and device ID for your gamepads and I will look into something when back on I'm away for a bit now

[mperreir]

Tell me the vendor and device ID for your gamepads and I will look into something when back on I'm away for a bit now

Here is the excerpt from xpad.c of latest linux kernel : { 0x044f, 0xb326, "Thrustmaster Gamepad GP XID", 0, XTYPE_XBOX360 }

So vendor ID is 0x044f and device ID 0xb326

Thanks !

[OCit]

Lots of people have reported broken 3D with AX12 on here, and beelink forums. Its a well known thing. Just because yours is not effected does not mean there is no problem. in fact your the first I've seen say otherwise vs the 30+ complaints on beelink's forum.

Now the fact that you say you don't have any problem with 3D on AX12 just further proves its nothing to do with firmware.. so must be bad hardware batch

I also have an ax12 box, after testing I have found that it appears at least with my box that it runs all OpenGL 3.x benchmarks flawless without issue. The issues appear to be with any of the older OpenGL 2.x benchmarks. Could this not lend itself to reason that with problematic hardware one would think to see more problems running a more intensive benchmark and instructions? The OpenGL 2.x ones always fault at exactly the same place and don't seem related to more taxing graphical processes. Thank you for all your hard work, time and breathing life into questionable devices.

[tillaz87]

Here is the excerpt from xpad.c of latest linux kernel : { 0x044f, 0xb326, "Thrustmaster Gamepad GP XID", 0, XTYPE_XBOX360 }

So vendor ID is 0x044f and device ID 0xb326

Thanks !

Ah so it's a wired controller and not BT?

When the gamepad is plugged in can you do this from terminal and tell me if you see your device

cat /proc/bus/input/devices

If its detected a .kl might be enough.

Otherwise we won't be to update the module as we don't have the kernel source for this rom and xpad.ko is built into kernel on this firmware.

If you rename your xpad.ko to xpad2.ko can you insmod?

[tillaz87]

I also have an ax12 box, after testing I have found that it appears at least with my box that it runs all OpenGL 3.x benchmarks flawless without issue. The issues appear to be with any of the older OpenGL 2.x benchmarks. Could this not lend itself to reason that with problematic hardware one would think to see more problems running a more intensive benchmark and instructions? The OpenGL 2.x ones always fault at exactly the same place and don't seem related to more taxing graphical processes. Thank you for all your hard work, time and breathing life into questionable devices.

So, here's how I see it.

They all use S912 SOC with mail-t820 GPU so the graphics implementation on the software side is the same across the board.

This problem is only reported on the AX12 batch of hardware.

Very few people say 3D is ok on AX12. but most say its broke, that alone suggests people with faulty hardware.
maybe the RAM is failing for some when under load?

706D batch came quicky after AX12 this batch must of had hardware changes as it needs its own firmware release, even though it uses ap6255

This makes me think it must of been a change with the RAM as 706D has its own problem
where its only detecting 2GB rather than 3GB RAM when it's stock firmware is not used.

And lastly look at all the complaints about AX12 3D problem below, why won't beelink acknowledge it?
https://www.google.co.uk/search?q=AX...hrome&ie=UTF-8

For me some hardware is faulty with a lot of AX12 my guess would be ram going off what we know.


I wont be looking any further into this as there is literary nothing I can do about it, other than advise you tell the people you bought the box off that its faulty and will open a paypal dispute if its not exchanged as you have loads of proof with the link above how widespred the 3D problem is with the the AX12 batch.

if you didn't use paypal make sure you do in future, if you can.



EDIT:

I also have an ax12 box, after testing I have found that it appears at least with my box that it runs all OpenGL 3.x benchmarks flawless without issue.

This video shows it failing on GL3.0

https://youtu.be/Bs-1U25ilhs

[cbm]

tillaz87 I had updated to the V10 beta already. Is there an ota zip file to flash the mouse cursor size fixes etc in the new V10 ?

[tillaz87]

tillaz87 I had updated to the V10 beta already. Is there an ota zip file to flash the mouse cursor size fixes etc in the new V10 ?

No, the latest update 10.1 is probably final update

[OCit]

[QUOTE=tillaz87;n708483]




EDIT:



This video shows it failing on GL3.0

Thank you immensely for you work and quick and lengthy response it was completely unexpected and I feel bad that you took that much time out of your day, lol I was only hoping to offer some constructive input for the AX12 issues . I'm not in need of Gaming/3d and I only purchased the box for TV viewing upon knowing of your ATV build which runs flawless. I posted prior to this only having learned of the AX12 problems and then loaded the benchmarking software to see if I was experiencing the same problems myself. I also was unable to run 3.x tests on the stock newest Beelink firmware and varying results on an older version I had saved. There are videos of people reviewing and benchmarking on Utube when the 3/32 version was initially released and it suffered none of the same issues but it was on older Beelink firmware and a different version of Antutu.( I watched them prior to purchase). I would think it would also have to be noted how people are coming to their conclusions about the problems they are experiencing, Are they solely trusting Antutu or Unity related apps to reach any sort of conclusion, as Ive seen others experiencing similar problems with the new iterations of Antutu on various Chinese chipsets. Years ago on here in a different forum Rockchip/RileyRom I remember similar problems that were only remedied with underclocked kernels on the memory side of things and those devices ran great after. As for the reason Beelink abandoned the AX12 my guess would be virtual memory is a lot cheaper than physical memory. :-P Again thank you so much for your time and incredible firmware my intention was nothing more than to possibly offer some congruence to the AX12 story.

[tillaz87]

[QUOTE=OCit;n708531]

EDIT:



This video shows it failing on GL3.0

Thank you immensely for you work and quick and lengthy response it was completely unexpected and I feel bad that you took that much time out of your day, lol I was only hoping to offer some constructive input for the AX12 issues . I'm not in need of Gaming/3d and I only purchased the box for TV viewing upon knowing of your ATV build which runs flawless. I posted prior to this only having learned of the AX12 problems and then loaded the benchmarking software to see if I was experiencing the same problems myself. I also was unable to run 3.x tests on the stock newest Beelink firmware and varying results on an older version I had saved. There are videos of people reviewing and benchmarking on Utube when the 3/32 version was initially released and it suffered none of the same issues but it was on older Beelink firmware and a different version of Antutu.( I watched them prior to purchase). I would think it would also have to be noted how people are coming to their conclusions about the problems they are experiencing, Are they solely trusting Antutu or Unity related apps to reach any sort of conclusion, as Ive seen others experiencing similar problems with the new iterations of Antutu on various Chinese chipsets. Years ago on here in a different forum Rockchip/RileyRom I remember similar problems that were only remedied with underclocked kernels on the memory side of things and those devices ran great after. As for the reason Beelink abandoned the AX12 my guess would be virtual memory is a lot cheaper than physical memory. :-P Again thank you so much for your time and incredible firmware my intention was nothing more than to possibly offer some congruence to the AX12 story.

Its just stuff I already said in other posts so don't feel bad it took seconds. but knowing what I know about android and how it works
I will let other people waste time trying to fix a 3D problem on AX12 that the OEM won't even acknowledge or comment on

Beelink's stance on it is enough to not interest me. I would also avoid this OEM in future as they are poorly ran IMO.


I'm ether going back to a Shield TV or will give a rk3399 a whirl out of curiosity how they compare to amlogic (circus)