OK, updated switched power button mode to suspend and seems alright so far.
What did it do before switching to suspend ?
OK, updated switched power button mode to suspend and seems alright so far.
What did it do before switching to suspend ?
The development version has an option to configure Power button behaviour in Kodi menu (Settings -> System -> Power saving). You probably want to set it to "Suspend" as some boxes have trouble waking up by remote control from "Power off".
Just to confirm that this Particular Box "Powers Off" via remote.
Using the .005 version it "Wakes Up" after power off.
Using Power Menu and choosing Suspend , The box Powers Off not Suspend. (.005)
Using the Development Build I tried the suspend option from my "Power Menu" and it Powered Off.
Doesn't seem to have Suspend.
@all I would like to publish one more update for S805 before switching to Krypton development.
LibreELEC-S805.HD18Q.arm-7.0-devel-201610120705..>
Updated to above version and lost "Turn On" box via remote.
Went back to .005 and "Turn On" via remote worked.
All Black MXQ (This particular box always worked on the HD18Q Versions as opposed to another All Black MXQ which works with the MXQ Arm versions.)
On the other hand, I still recommend using SD card first and I'm wondering whether I should drop NAND installation ZIP completely.
I'm a fan of that idea.
Working SD Card Install is mandatory for me on any box. Followed by SSH installtointernal has worked 100% on 4 different s905's
I have a Vigica 100S witch is the same as a Venz K1 and tried all S805 images without success
You might want to elaborate what "without success means" ?
Did your box explode or maybe catch fire ?
I am putting humour into this as i think you must understand we cannot read between lines.
I don't like your chances of the tuner working in LE but a little more info would be good.
At the moment I could not get the IR remote control to work. Not a big problem but it would be useful. It doens't respond. Perhaps it's a known problem...I will read if there's something about it.
Well done.
We don't give up that easy at LE.
Try the remote.conf file attached.
SMB and copy it to config directory.
Unzip it first.
remote.conf.zip
[hr]
Hi,
remote control does't work on my Beelink MiniMX 1/8Gb, please support.
(used gxbb_p200_1G_1Gbit.dtb)
Beelink might be different but look at picture.
Why did I do a clean install?
Good to hear from you again PatrickJB
I did the clean Android Install and Clean LE because of the Blue Light "ON" all the time.
I now have Suspend with remote. Blue Light Comes On.
Turn back on from Suspend . Red Light Comes On.
Suits me.
I couldn't remember what the hell I had on this box as far as Boot Loader and U-Boot .
Flashed so many roms on this box.
Anyway , Good to get this out as i'm sure it is going to come up again.
I found that LE does not recognize my MCE remote. It has its own IR receiver and it works "out f the box" with OE.
I believe you must have a USB port not working that the ir receiver is plugged into.
Swap it around and see what happens. I'm not sure what MCE remote is but the remotes with receivers usually
learn when plugged into a WORKING usb port.
Sorry that is all i can help with at this stage.
Hi Fellow s805 Flashers.
I am just posting an issue that may or may not be known as i haven't had to do a fresh install NAND on my
MXQ.arm 7.0.2.5 from Nand on All Alack MXQ, board number: 'AM_MXQ_A 20150825 for a long while.
I Downloaded zip file from NAND release folder.
Unpacked downloaded file to a FAT32-formatted SD card - there were 3 files as a result:
aml_autoscript, factory_update_param.aml and a zip file with an update.
Tried to Install ROM using "toothpick" method. FAILED to boot into LE. It booted to Android.
Tried 4 times with same result. I tried the Update App in Android but same thing.
I then took out the SD Card and tried to boot into recovery but no go. Just booted into Android.
I then added the factory recovery image to the LE sd card files to make it 4 files and Toothpicked.
The Android Robot appeared and started installing. The box rebooted with a fresh NAND LE .
Just putting it out there as this never was the case with this box previously way back.
Hi andreaf, what version of MX Plus you have?
This is his first post above when i tried to help him. It looks like it is definitely the same box.
I wonder if the .006 version you flashed first worked and the .007 he is trying to flash first time is causing the issue?
I hope he hasn't given up
i'm having some issues with my remote of the T95-max. This is the remote:
azido can i ask if you have this t95 Max 2gb 32gb working ?
I have been given one of these to put LE on SD card
But i have never seen one of these boxes before.
Device tree used / Version of LE is my query and that remote is not one I've seen either.
Thanks.
The box I was going with was a VONTAR T95. Is this known to work well?
No idea. I don't have this box.
I know the LED Display will give you issues in LE. I don't believe it will work.
The OTG Port may or may not work as the device trees currently available are 1 gigabit ethernet.
I don't know if recovery booting from SD card LE will give problems depending on the Android firmware.
This metal case is used in many of these Chinese boxes but what's inside is a lottery.
Display More
I know this is in the wrong thread but I was wanting some advice on a new box?
Will LibreELEC run on this ?SPECIFICATIONS
HARDWARE
Processor: Quad-Core Cortex A53 S905 Processor
GPU: Penta Core Mali-450 GPU
Memory: 2GB DDR3
Flash Memory: 8GB
The Hardware you quote is known to work.
But these boxes are not all the same as far as boards, internal memory, heat sinks, etc and Android software.
You will find some of these branded boxes have issues trying to flash LE so take what you want from that.
See the ones with branding names that other members have successfully run LE and you are good to go.
Signature shows my box fits into the specs you're after but there are others.
I have tried replacing the dtb too but get the same result
Are you referring to the below device trees ?
And you tried firstly without replacing device tree because you have an S905X soc ?
Any other ideas?Perhaps I need an hw modification like this ?
Try an 8gb sd card first to eliminate the possibility of 32gb not compatible with LE Booting.
I have seen this issue before. It is worth the try.
In case you need info later Your Box has P200 Board and Realtek WiFi Chip RTL8723.
Read this as well ; Modifying u-boot. Inphic Spot i7 - Running Linux From An SD Card, USB Card Reader Or Flash Drive, Using Balbes150's Method And Files. - FreakTab.com
This member is credited for the above. balbes150LibreELEC
Another possibility is to load Factory Android Firmware with U-Boot from a similar s905 Box.
This will only get you an Android version with not all working functions for your box.
It will then allow you to load LE on SD Card . Then you can test device trees to get a WORKING LE
After that you can SSH installtointernal command to run LE From internal memory.
I have done this before but it is not really advised.
I'm a risk taker with boxes that give me troubles like this.
Never used Rufus before...it seems it has correctly burned the SD even if I did not unpack the .gz
After Rufus had finished I saw several file on the SD.
I just quickly looked at Rufus info and it looks like you did it right.
You mentioned the files are visible after burning so it is correct.
You may have to choose the update zip which is one of the files you are seeing whilst in recovery but please wait as i am not sure
about this. Do so at your own risk. If you don't have factory Android Files to get back if something goes wrong.
I dont think anything will go wrong but i dont know what U-Boot this box has and i am wary about some of these boxes and suspect Firmware.
This box has a Dubious and not very friendly community version of Kodi with license violations.
[hr]
You need to unzip the .gz before using rufus. It will look like it's burning correctly - but it is not. You need to burn the .img file.
If you are correct ?
Someone has to fix the link Installation - LibreELEC
1) formatted as FAT32 a 32GB Kingston class 10 microSD card. Done under Windows
2) downloaded LibreELEC-S905.aarch64-7.0.2.007.img.gz and then drag-and-dropped it in Rufus, without unpacking it before
Someone has to help you with Windows and Rufus. I am a Mac User and use Apple Pi Baker. I have to Unpack .gz and Apple Pi Baker sees the .img
It prompts me to choose the unpacked LE Image for burning and sees my SD card to choose as the SD card to burn it to.
Get confirmation from Windows members as i am a total Windows No Idea kind of guy.
Second issue is the 32GB sd Card. Can your box read 32gb ?
Get the burning right first and beware of the sd card size issues. i know people have had issues with LE on sd cards larger than 16gb.
Now the problem is that
1) when I try to boot using the toothpick method the box boots Android in safe mode
2) using the recovery method the box restores the factory Android installation
From your post i think you are just booting into ANDROID recovery ?
I don't believe you have created a Bootable SD Card.
Please tell us how you burnt the .img onto the sd card.
EG: You unpacked the LibreELEC-S905.aarch64-7.0.2.007.img.gz and you used WHAT program to burn the image you unpacked from the
LibreELEC-S905.aarch64-7.0.2.007.img.gz.
You also S905 only: Downloaded a device tree gxbb_p200_1G_1Gbit.dtb, renamed it to dtb.img and copied it to main folder of SD card replacing the one that's already there.
Check the steps and confirm your steps.
I am pretty sure the burning image to sd card has not been executed correctly.