Posts by RayW

Quote from DannyMinh

I tried to access storage/.config by File manager tool in LibreElec but could not access this folder. The keymap add-on is also not effective for me. Will try ssh method. But most of my PC/laptop are Windows so need more learning to get it done. However, I accidently found that my TVs (Sharp and LG) remotes can control Kodi with navigation buttons, play/stop and turn off. So the CEC control do the magic here. Not all functions but somehow fit my need before fixing the correct remote.conf one!

Make sure in KODI settings (somewhere that I cannot remember right now) you enable the features to be able to view hidden and system files and also the other option to enable you to edit and delete files too. Then you will see the storage area no problem. using file manager.

Quote from dobbs2010

Please help, have been trying for 3 weeks to get this remote working. It came with a Hamswan OTT TV Box (MXQ S805), it's slightly different to the one that comes with most other MXQ boxes and I can't find a remote.conf that works.

Try this one remote.zip?dl=1 It was made last year for the MXQ M12 S805 box and worked fine so good luck and hope it works well for you too.

Quote from kodiuser1

Hi Ray, here is the inside of a Beelink Mini MXIII II. As you can see the reset button is far away from anything.

Hey thanks a lot Ed. I really did not want to open my box unless I really had to so this is a great relief to see a metal needle is safe to use for the reset button. Nice lot of heat sink paste they use it seems from your photo so this is clearly one of the numerous reasons why many here seem to praise this box, and it does run a lot cooler (10C less) than my MXQ M12CX S905X box. I am very happy with it I have to say but wish they would use an external WiFi antenna and a brighter front power on indicator led. Other than that I see no point in buying any other boxes as the 2G/16G package price is very good for what you get with this box. And has no problems at all with the latest 8.0.1b either. I will be using this box now and recommending it to my KODI box user contacts.

Quote from kodiuser1

Sounds good Ray thanks.

Okay matey I have compiled a new remote.conf to include teh numerical remote buttons. Will email it to you for testing as obviously I am unable to test it out here not having that different Beelink remote that you have. Clearly it has the same Factory code else it would nto work withthe remote.conf I posted wihtout the number keys included.

Let me know that it works okay and let me know if there are other redundant buttons on that remtoe that could be tied to other functions like Page Down and Page Up say as I have done with the MXQ M12CX box supplied remote. Once ti is oaky I can then post the edited remote,conf file to replace the earlier one as then it will be compatibel to both Beelink remote types as supplied with their Mini MXIII II S905X box.

BTW on a different note the WiFi sensitivity at least on the standard 2.4 Ghz band is far worse than the MXQ M12CX and Enybox X1 box as both those have an external antenna. I managed to test my box today at a neighbours house working back to my home WiFi and strangley only my old MyGica ATV1200 dual core box running EmbER 4 managed to actually work there as had a much better reception. The Beelink relies on an internal antenna and I have never known those to be very good as to sensitivity and it did not even see my WiFi at all, whereas at least the MXQ and Enybox both saw a low signal from my home WiFi but was too low to be useable. I now use a WiFi repeater suitably located about half way between our two houses and this is workign fine on the old MyGica ATV1200 but need to test to the 3 different S905X boxes I have. Cannot test the 5Ghz band as my main router does not have a dual band WiFi.

Quote from kodiuser1

Thanks for the remote file. Works good with my Beelink remote, only mine is a newer remote with numbers, which don't work now. I don't use them anyway.

I was unaware there was a newer remote for the Beelink S905X (I assume it is the S905X version Ed). Not a problem I can easily update my Beelink remote conf file to include all the number keys as theyh are standard on the Beelink remote, Cannto test it of course as do nto have your remote but I will send it to you for testing first. I personally prefer to use the buttons as labeled if possible and only remap those buttons that are really redundant in LE.

Just need time but if all okay then it can be used with the non number keys Beelink remtoes too of course. Should be this week. Important thing is to either disable the remote mouse button or remap it to something useful like Play/Pause, as it causes problems as I mentioned earlier if it is left as is.

Quote from Pelican

Prometheus Universal Remote Setup (For any Amlogic board with IR) - FreakTab.com

Many many thanks for that Pelican. This is excellent reading and so informative. Need to read it carefully though I knew soem of it of course a hell of a lot I clearly did not and give the answers to my questions which I raise as I am keen to learn.

RayW

Quote from Vette

remote: Wrong custom code is 0xae517f80

Here the button code is 0x51.
(use "remotecfg /storage/.config/remote.conf" to apply a new config without rebooting")

All working now Vette as I finally derived the correct remote code from a partially working remote config file by a process of elimination. See my last post in the remote repository thread. What threw me was I was looking for the normal 116 KODI shutdown command code but it was shown as 704 in that other odd file ????? As I thought the command codes were a single byte of data then decimal values over 255 surely would not be recognised?? Though strangely or coincidentally 74 Hex is indeed 116 decimal but not teh stated 704 Hex of course ??

The correct code as it turns out was 0x51=116 and same remote code as in your example. Many thanks Vette for your input but how could you know to specifically use the 3rd and 4th hex characters from that Wrong custom code result ???

Cheers
RayW

I do not know your box mrtr32 but yes it should be perfectly possible by changing the value in the remote.conf file for whichever button you want to remap, to value of 164. I use the mouse button on my Beelink remote as it is redundant anyway with Linux (and crap in Android too) and I simply change it's value to 164 and bingo.

Copy your amended remote.config file (edited using a plain non formatting text editor like Notepad and save as a *.* not a .txt file) to a USB or SD card and then with your KODI box transfer it into the .storage/config folder using the easiest of ways with the KODI File Manager and reboot.

Also found with Kodiuser1's Beelink remote.conf file when in use not only as expected do all the navigation keys cease to work if you hit the mouse key by mistake, but hitting the mouse key again to restore them to use will disable the repeat function of all the remote buttons. This of course can no longer happen with a remapped remote mouse key set to the Play/Pause function.

Now cracked this power button problem by a process of elimination with kodiuser1's earlier remote.conf. The line I needed was 0X51 704 but cannot understand that 704 value as not on my list of KODI command codes as way out of the range. Changed that to 116 and all working perfectly now.

Here is the link which I hope works for you as Dropbox have recently made some changes to their public folder but this is the only way I know how to make it available to all. Dropbox - BEELINK Remote.zip

Quote from kostaman

Hey Ray and others please see screenshot of how to reply and only quote RELEVANT part of the subject you are replying to.
It is getting way out of control with members quoting the whole posting and then re quoting again and again.
Pages are increasing with the same full quotes everywhere.

Yes indeed my bad I do usually do that so my apologies as get a few senior moments when I forget to do just that. My bad hmm !!!

Anyway found the answer I need by a process of elimination using a rather messy and flawed Beelink remote.conf file and teh answer was a line 0x51 704 . Odd as 704 to me should not be a valid figure AFAIK ??? Changed that line to 0x51 116 and it now all works. Thought I had tried 0x51 before but must have made an error loading it when I did try that. So now all is workign and will post it in the remote repository for all those with the Beelingk MXIII II S905X box.

Cheers
RayW
[hr]

Quote from libredark

Does suspend/sleep work on Beelink MiniMXIII?

Yes it does for me on my MiniMXIII II S905X version of that box, by simply going into System|Settings|System|Power Saving and changing the Shutdown Function from the default Shutdown to Suspend. Should work if you have the S905 version too, so try it.

Well firstly I really much prefer not to have to install a terminal app in Android as I quickly want to clear Android out of my new boxes as I really detest Android bloatware and want as littel to do with it as possible whereas I love Linux based LE. So will persevere much easier with the small reset hole and find a thin enough plastic needle for the job. Thanks for the input though.

As to remote conf files well yes I know about the remote repository here but the remote.conf file that my friend Kodiuser1 posted for the Beelink leaves a lot to be desired and it is a mess with muliple edits leaving several different mappings settings mostly wrong or unneeded and all still active. Only the last set of mapping in the end actually counts and this does work. It has some bad limitations too like the repeat function does not work at all and the mouse key is still active meaning an accidental press leaves your remote navigation keys not working until you press remote again. That is why I decided to write a new suitable remote.conf file from scratch and which I promise you will like a lot once I can get this Remote: Press ircode for the power button to map the 116 shutdown code to it. This new remote.conf I am trying to complete as I said enables properly the repeat function and maps the redundant mouse button to an easy and useful single press KODI Play/Pause command.

Cheers
RayW

Now I have my new Beeling MXIII II S905X box I have to say that after intiial tests with it, and now running LE7 withthe 012j version I am impressed with the performance. So I do like the Beeling S905X box it runs very fast and seems impressive.

A couple of things I do not like though that is IMHO not as good as on the other box I have the MXQ M12CX S905X. Firstly and a minor gripe is that the reset hole in the base is way too small as it won't accomodate even a normal wooden toothpick and that means I have to use a metal pin or needle and I hate poking any metal objects into the box as you never know whether it will short and damage the box without knowing the layout inside. Secondly and more importantly, I do not like that it does not have an external WiFi antenna as internal antennas are usually far less receptive and can and do often lower the WiFi sensitivity considerably. Have not put this to the test yet though, as my box is only a small single room away from the Router so is not a decent test on that score with such a strong signal there. My bedroom TV is broken at the moment waiting for the Samsung repair team to come and fit a new 40" screen to it hopefully on Monday, and then I can test this box's WiFi to this more distant point and compare performance to my MXQ M12CX S905x box with it's external antenna.

Trying to finish off a really useful remote.conf file whch I have built from scratch for this Beelink box and it works excelletnly on testing and has the redundant mouse button very usefully mapped for single press Play/Pause function. All woirks except for the power button for which I cannot get the scancode as the box of course switches off before I can run the "dmesg -c" SSH command and read it off. So if anyone knows the scancode, or more precisely with this box the "Remote: Press ircode" , then I cannot map that to the 116 KODI shutdown command. Once I have this missing Press ircode value than I will have a great simple minimalistic remote.conf file which I will post in the remote repository here. My tests with it shows it functions flawlessly with full repeat function too, that is all except this simple bloody power button mapping !!!!! Anyone can help with this it will be much appreicated..

Cheers
RayW

Hi Subzero79 and welcoem to this forum. Thanks for your input but alas the key codes generated are dependent on the remote itself and the standard Beeling MXIII II S905X box remote which of course has no number pad at all.

Ed thanks for that idea I never thought about configuring KODI to somethign else when it gets a shutdown command form the remote, was not sure you could but will take a look when I get a moment. Another problem withthe remote conf file you posted is that the repoat function does not work and I can see why. My new conf file works 100% on all scores other than the red power button as I said before.

As an aside, so far I like the Beeling S905X box it runs very fast and seems impressive. A couple of things I do not like though. One the reset hole in tehbase is way too small as it won't accomodate even a normal wooden toothpick and that means I have to use a metal pin or needle and I hate poking any metal objects into the box as you never know whether it will short and damage the box withut knowing the layout inside. Second thing that I do not like is that is does not have an external WiFi antenna as internal antennas are usually far less receptive and lower the WiFi sensitivity usually. Have not put this to the test yet though as my box is only a small single room away from the Router so is not a decent test on that score with such a strong signal there. My bedroom TV is broken at the moment waiting for the Samsung repair team to come and fit a new 40" screen to it hopefully on Monday and then I can test this box's WiFi to this more distant pointand compare performance to my MXQ M12CX S905x box with an external antenna.

Quote from kodiuser1

Ray , can't you just use the scan code from the Beelink remote file I posted??

The mouse does work, not that it's used by anyone.

Second thoughts I can't see the power in there either.

My remote file seems to work fine though.

Hi Ed.

No it is not ideal at all as one major problem is the mouse button if accidentally clicked it stops all the navigatign controls workign without clicking it again. Still thanks a lot for posting it and indeed am having to use that for now until my new conf file is completed. I have eliminated this with my far smaller remote.conf file and used the mouse button for a Play/Pause button which is an excellent reassignment of an otherwise redundant button. Also your remote.conf has loads of complete and conflicting or redundant rubbish in there, and thus also why over 4KB whereas my new remote.conf file only deals with the buttons on the Beelink remote and removes all the conflicting redundant bloat. So all I need is the remote code for the red power button and cannto get it. Why it is missing in you remote.conf heavens only knows ???? Your remote.conf is obviously edited from other existing and much previously edited files whereas mine is written from scratch and is only about 460 Bytes in all too.

Some KODI codes in your file are totally strange and oddball, like a value of 704 here in this line "0x51 704" well if you look in the KODI codes document you will understandably see that such a code does not exist as way too high a value and 0x51 is not a Press ircode form my remote either though the 51 value is shown in the scancode but htis does not work with Beelink as it is mapped somehow it seems to the PRess ircode or Release ircode value whcih I need and cannto get for the power button???

So please can someone, somehow get me the Press (and Release) ircode for the red power button on the Beelink remote and I will give you a first class efficient remote.conf file for use with LibreELEC 7 or 8 on these wonderful littel Beelink boxes. Just this one Power option line I still need to write into my new conf file.

Cheers
RayW

Can someone help me here please. I am writing a functional remote.conf file for the Beelink MXIII II S905X and I have it all neat and tidy and fully functioning EXCEPT I cannot get the key code for the Power button, as of course when I push it then Putty no longer has access to the Beeling box as it understandably has now turned off !!! With the new conf file then the remote Power button does nothing and I get the message in SSH command dmesg-c "remote: scancode is 0x0051,invalid key is 0x0000." but I know that this scancode is not what I want as i need the remote:press ircode in the format of something like 0x53 (that in fact is the code for the Home key). I have tried putting 0x51=116 in there but that is no good as I know from experience now that the scancode does not seem to correlate in any way with the press ircode as the example two lines below shows for the Home key press

remote: press ircode = 0x53,
remote: scancode = 0x00ac,maptable = 0,code:0xac537f80

BTW my new remote.conf file for the Beeling MXIII II maps the redundant mouse key to play/pause which is probably the most useful function as now it takes just a single key operation to pause and then later play a movie you are watching when you get interrupted. The relevant line in the remote.conf file for this mopuse key play/pause function is 0X52 164 Now my remote mouse key is very useful and is used a lot. Just now need the remote: press ircode for the red power key and my new remote.conf file is complete and I will make it available in this thread.

Does anybody here know if the new MyGica ATV495 is supported. This is a s905 box with a gigabut ehternet port and 2G/16G memory. Looks very nice though not that cheap by todays standards. All depends of course whether thsi box is compatible with any of the available s905 device trees ?? Also has a very nice USB dongle driven remote with one side normal remote buttons and the other a full querty keyboard with other function keys too.

I have only just tried out LibreELEC 8 with my new sample Enybox X1 1gb/8GB which was runnign from internal LibreELEC 7.0.3.012j with a full suite of add-ons etc. Originally I tried just the update path putting the V8 file in the .update folder in the usual way and indeed put the latest gxl 1GB device tree file in there too, and then rebooted. Yes it did the update BUT would not run up at all.

So I tried a clean install of LibreELEC 8 build (version d) with a new SD card and this worked fine and booted into the convoluted not so nice KODI 17 homescreen. Thsi was fine until I restored, using the LibreELEC restore feature, my KODI 16.1 earlier backup of all my add-ons and settings, then same result it would not boot up into KODI adn after tgeh LibreELEC boot up screen was left with a balnk black screen. So had to assume that it is not possible to restore your settings and add-ons from an old KODI 16.1 LibreELEC 7 setup ???

Tried it again with fresh made up SD card with LE8 but this time I painstakingly manually reinstalled my respositories and add-ons and it now works fine. Flashed to NAND with installtointernal command too and with no problems. Sorry if this has been mentioned before but lookign through over 100 pages in this thread is going to take way too long to find, so can anyone help here or point me to any relevant posting(s) here.

I would love simply to be able to update with all the add-ons and settings a LibreELEC 7.0.3.012x box to LibreELEC 8 if this is possible. Anyone ?

Have to say so far I am NOT a lover of the new KODI 17 default skin at all. Need to play around with it and remove all those Library links that I do not use to make it less cluttered and long winded to navigate. Much prefer the old Confluence skin (can that be installed on KODI 17?), but then again it is early days and the old problem of familiarity with Confluence and not with the new skin (Estuary ??) of course. Sure I will persevere with KODI 17 and climb the much needed new learning curve. :s

Cheers
RayW

Quote from kodiuser1

Hi RayW,
You can't go wrong with the Beelink MXIII II That's what I have and it is the best box I've ever had.
Remember to pick the correct device tree you need one for S905X. There is only 2 to choose.
[hr]

You can get the remote.conf file from the remote repository thread.
Also one you have basic LE up and running you can use Samba to just drop the remote.conf file into the Configs folder. On restart your remote will work and when you flash to internal the remote will work also.
You may have to run install to internal twice otherwise you will get an boot error.

Display More

Hi Ed. Thanks for the confidence booster for my getting a Beelink S905X box in to try. And yes I am well up and running with the device tree options, and yes am aware that for this Beelink box I have on order I will need the S905X one for 2GB boxes.

I will try the remote for the Beelink from the remote repository here and if needed can remap it to what I prefer. My MXQ box now has for example the @ button mapped for direct play/pause, the Home button does as it should and I have the other two redundant buttons on bottom left and right for PageDown and PageUp. Must upload that in the remote repository for the MXQ M12CX box and many others that seem to use this same remote from the numerous Shinningworth produced boxes like the Enybox X1 I now have on test.

Cheers
RayW
[hr]

Just a note to say the Enybox X1 1GB/8GB S905X box works perfectly with the latest 12j version of LE7.

There are though two small but annoying problems relating to the front panel on the Enybox. One is that the blue light stays blue all the time, even when shut down or in suspend mode, which is unlike the MXQ M12CX which changes to Red. Secondly there is a front panel clock display on this box, which as I expected only works in Android (which I really detest and won't use) and not in LE7.

The build quality of this Enybox X1 box IMHO looks and feels a little inferior to the MXQ M12CX box, though likely that the mainboard will be the same Shinningworth produced board in both boxes as indeed the remote is also identical. So overall this makes the MXQ M12CX still my current box of choice as now it has absolutely no problems and runs mega fast, smooth, and truly like a dream with the latest LE7. Pity it is so difficult to source still as a great value for money box that really works.

Also the new Enybox X1 has the same temporary loss of OSD controls as the MXQ M12CX box when running up a video stream if the Vertical sync is enabled. Of course easily fixed by staying with the default setting for the Vertical Sync option of "Let The Driver Decide"

Cheers
RayW