Posts by _bhf_

Quote from Leo'sSire

I'm having a random issue in defining my A95x S905x unit.

On Amlogics own website every reference to a S905x has 2gb of ram. Mine has 1gb.

The rest appears to be the same re:hardware. It looks like I have a P212 but with less RAM.

Has anyone else found this anomaly yet? It doesn't make sense to me.

Cheers,

I have a Nexbox A95x-B7N (there is a small Sticker on the bottom of the box) with 1 Gig RAM and 8Gig eMMC. It works flawlessly with kszaq's builds (now discontinued) ie 8.2.3.1 and the gxl_p212_1G device tree.

Quote from cptchezza

I have a x96 and tried to use your files, but it didn't work.

Did you activate the keymaps?

ir-keytable -a /storage/.config/rc_maps.cfg -s rc0

Quote from jopereira

I had 8.0.1l, installed internally, almost for a year.

Recently updated directly to 8.90.6, with correct dtb file. Worked like a charm. No problems at all, but the remote keys.

But them, trying to solve a colateral issue, I updated with same .tar file and now it won't boot (AMLogic boot logo only). I used UPDATE folder method.

Since booting from SD works just fine, I tried to restore dtb file (bellow), but it still doesn't boot.

My question:

Can I use this version and do an installtointernal procedure (since it already worked fine with my box)? Will it work fine, or should I be concerned about bicking the box?

Please, sugestions ...

Display More

Not with 8.90.6. In this version the script was removed. You can however boot from SD-Card, update with the CoreElec Devel, test extensively and then installtointernal.

Anyway, this is the wrong thread. This one is about kaszaq's Builds. You want to read AdamG's pinned topic about 8.90.6. And yes, it starts with post #1 and ends with the last one. There you'll find all informations you need.

Oh shoot, too late.

Half Gigabit, because USB2 ist limited to 480 MBit.

1st Post. Build 8.2.3.1.

Denman try this one. Same Remote, same supplier. It's from a WeChip Z69.

Post #120

NTFS works fine with all my boxes.

Yes, sure. First Post, Button older builds. Download the tar file and push it in the update directory. Then reboot the box.

Quote from kszaq

Announcement: Krypton builds are now discontinued.

Okay, great.

What happens to Autoupdate? More precisely, will Autoupdate suspended, till Leia has reached at least beta stage, or should it set to manual update?

When does the update notification pop-up? When the file is physically downloaded into the update directory already? Or prior to that, when update detects a newer version?

Because I got the notification, rebooted the box and got an error of corrupted file. The box booted into the current version. A couple of minutes later, I got another notification and this time, I checked update directory and the file was there.

Reboot installed the update and Settings/LibreElec was dead, no reaction whatsoever. Another reboot and Settings/LibreElec responded again. BTW. Update Channel and Available Versions are both empty.

I guess I deactivate automatic update for the foreseeable future.

Well, a WD 3TB Elements with a single USB cable connected to a Nexbox A95X-A1 does work flawlessly ootb.

Quote from doggyofone

Thanks for that. I will give it a try. The bigger issue is why the remote works with no remote.conf found on the box.

Maybe your search string should have been remote* or *remote*. On my box the remote.conf is found in /etc, like Tim_Taylor said. But even that is no guarantee that this original android remote.conf will work in LibreElec.

There is a repository of remote.conf files, working in LibreElec. Read this a couple of posts down and try the linked remote.conf. If that doesn't work, look for boxes with the same remote, they are usually interoperable.