Read this post.
Note that suspend is not supported and might cause your device to crash. But on some boxes it works fine.
Read this post.
Note that suspend is not supported and might cause your device to crash. But on some boxes it works fine.
Add "ssh" to CMDLINE in kernel config.
wistoha Only if Amlogic adds it to a publicly available driver.
Yes. /dev/SYSTEM is a LibreELEC system image copy in RAM.
wistoha Most probably you have an unsupported NAND. Unfortunately support cannot be added for that chip as driver is closed-source and we rely on Amlogic for updates.
You don't need to extract it, simply delete dtb.img from SD card and it will use device tree from internal memory. But it's highly probable it won't boot.
Sorry, S905W is not supported in my build.
Hi guys,
Anyone has manged to install lepotato image in the emmc? I've tried it but it doesnt boot. Is it possible? It is working without problem in a sdcard though.
The image is not compatible with eMMC as it's currently not possible to have an image compatible with both SD and eMMC for gxl targets.
gadido30 I wouldn't say "missing" because it doesn't exist in 3.14 kernel tree: kernel/git/stable/linux-stable.git - Linux kernel stable tree
But thank you for pointing this out, it's definitely worth testing.
LuRcH Any updates on your side?
Yet,
an S905 box with a "wrong" dtb behaves just like that.
Once the dtb is replaced with a "proper" one - power on from remote works again...
Please give some more details: type of box, working dtb, not working dtb, run from SD/internal and maybe we can figure something out.
p.s. I still can not fix the damn power off/on, so annoying but I have to live with that. Wonder if we cannot extract the dtb.img from the crappy original Android firmware that comes with those boxes. For H96+ pro there is a stock 7.1 Android. Anybody let me know if I can do something.
This has been said 100s times: powering on is a matter of proper bootloader implementation, not dtb!
Sirius Amlogic TV Boxes use u-boot as a bootloader.
Installing LE to Android TV Box means replacing kernel, and system image with LE. This process does not modify bootloader as is is impossible to provide single (or even a few) bootloader images that would fit all the boxes, mainly because of slight hardware differences, different DDR speed etc.
The only targets we provide bootloader are SBCs - for the moment Odroid-C2 and LePotato, possibly Khadas VIM in near future.
I'm sorry, I have no more ideas.
neel Re remote.conf with all buttons mapped: solution in this post
Re resolutions not detected: solution in this post
Please let us know regardless the result.
FYI: This is a modified bootloader that changes DDR frequency from 912MHz to 792MHz. CAS latency lowered from 13 to 11 at the same time.
mega-samu There will be no new 8.2 builds.
kszaq wrote: No, not essential. You can also do this yourself in every previous version, e.g. to scale GPU down to 500MHz:
Code
- echo 2 > /sys/class/mpgpu/cur_freq
Kszaq is this code like:
or just the code you posted... and is this the only thing i have to do, ones?
And is there a way to scale down CPU? for betther temp/ overheat?
Code
- echo 2 > /sys/class/mpgpu/cur_freq=500?
I don't understand the question. You don't have to do anything, box should work with OK temps with the latest build.