Perhaps try starting with a fresh CE?
I just finished setting it all up, adding movies and all …
However, now on the 15 and 16 nightlies, this is suddenly broken. No more remote power-on. Upon updating the BL301 is still recognized and if I try to do it in the menu it states that it is not needed.
works fine for me on 20200115 and now 20200116 - I can power-on / power-off / power-on through the ir-remote successfully. maybe try to flash the original bootloader (it got saved to /flash/ during the first injection) to undo the BL301 injection, and then retry?
Heldchen,
will give that a try.
I ran the ssh command from the bl301 thread - did not help.
I guess I have to look for a X96 firmware file and burn that …
You can use the Reboot to Libreelec app on android instead of pressing the recovery button. I’ve setup 3 now and always do this instead, never used the button.
https://m.apkpure.com/reboot-to-libreelec/me.thomastv.rebootupdate
I fine the Krypton type remote much more responsive / smother than meson-ir
I created two files, easy to test and easy to revert back if you don’t like
Example 1 - works the same as the meson-ir in the initial post
Example 2 - only some small changes
# "0x47 18 # @ " changed from 18 to 46 - "TVGuide" to "Codec info"
# "0x4c 50 # MENU" changed from 50 to 46 - "Menu" (sidebar menu on the default skin) to "Contextual menu" as all the remote's I've used had this
I’ve re-wrriten the file to make it easy to modify e.g. the STAR button is currently mapped to info (23)… you can change this to what you like e.g 18 for TVguide
0x43 23 # STAR (examples 15 tab, 23 info, 24 codec info, 113 mute, 354 favourites, 18 TVguide, print screen 210 etc)
To install rename the file to remote.conf and
Krypton remote.zip (2.5 KB)
1 Like
FYI
I never check what version of X96Air_x I had, it was purchased from same place as someone who got a P2
However its X96Air_P3 and the guide works for this Box as well 
(the only different I can tell is that bluetooth chip has changed & does not work)
Thanks.
I’ll update topic soon
Can anyone confirm which USB port should be used for the Amlogic USB burning tool?
Rear USB 2.0
Side USB 2.0
Side USB 3.0
Also, should I be booted into the Android recovery screen to be able to start the process?
Odd, nothing at all getting recognised on USB on any ports on Win10 or Ubuntu whilst in Android recovery mode
Same for my S905 too though to be honest
I think you can include also P3 version of X96 Air 4/32 to the title/description, I just unpacked one and all your summary is spot on. Thank you for it 
1 Like
A little off topic but I’ve not been able to use Amlogic Burning tool on my Vim3’s.
I don’t know if it’s a cable issue but most people are using it on Khadas Forum.
I ordered one of these cables.
Still don’t have it.
Amlogic USB Burning Tool 2.1.7.3 is the latest version btw, make sure you are using that in case that is the problem.
Topic updated!
2 Likes
Why you enable this?
debug_enable = 1
Updated… my previous commnet was incorrect
1 is actually debug disabled
Do you know where’s remote.conf on Android system?
I try \android\etc but didn’t find.
Do you original file from android?
I used the meson-ir as a starting point as the button assignments are as you visually scan the remote downwards i.e in order.
Then converted to Krypton and used the key assignments from revolution6 e.g 0x40 116 # POWER - changed couple of names
I don’t know where the android file is
However I found some info
# debug_enable 0 :debug disable 1 :debug disable
I found files with it enabled / disable… I’ll correct my previous post & delete the file - original files are correct
1 Like
Added a 4" fan running off the 5v jack to the bottom of my P2 and I have steady 45C.
A bit noisier than I would like but will probably upgrade the fan to a more silent model.
Shoog
1 Like
Picture please to see your final work