You dont need any injection. Just use remote.conf file in CE. Works good.
Should I remove the Injection? How?
Before that I had the same problem - I canāt shutdown or reboot properly. The screen turns black but the box stays with the green leds and never really turns off or reboots.
What remote.conf should I use?
Thank you. Itās exactly the same as another one Iāve found here.
Iāve tried it before with no success.
I have two problems:
1 - The box doesnāt shutdown or reboot properly. The screen turns black and disconnects but the box stays with the green leds and never really turns off or reboots.
2 - The remote doesnāt activate the shutdown on kodi.
However if I suspend the box then the leds go red and the remote works to wake it. I donāt know if it also works from a shutdown state because I canāt put the box on such state.
Logs (before the remote.conf but it didnāt change the behaviour):
From Kodi: http://ix.io/24mK
From ssh dmesg | paste : http://ix.io/24mL
I have Stock android rom from beelink, no any bl injection, CE on usb pendrive. With this, the box working good, totally power off, no led light.
From your logs it looks like clean startā¦
What Android firmware does your box have?
Try to comment decode_type, remotewakeupmask, wol values. They are the same as default one
So you can change only remotewakeup code. Is it correct? Does power button works for shutdown?
I have firmware 906P0.
SN: B922HQā¦
I installed CE rev A on SD card because it didnāt boot with rev B.
Before I had the original config.ini with no changes but then I tried everything Iāve read trying to solve the problem.
The power button on remote doesnāt work for shutdown. It only works to resume from the suspend state.
Iām not even trying to solve the remote problem now - first I would like to be able to shutdown/reboot the box properly.
If not Iāll have to educate myself to just suspend the box.
If it doesnāt work for power off then it looks like you have wrong codeā¦
Or use instruction to find correct key How to configure IR remote control
Or
Enable debug mode, press power button, disable debug mode and collect log
With the following keymap file now the power button shutdowns Kodi
# table gtkingboxkeymap, type: NEC
0x8051 KEY_POWER
However the behavior is the same as if I select the option on the UI: The box turns off the screen and the network but the leds are still on (green) and the only way to restart is to turn off the power and then turn on again.
PS: I discovered that if I unmount the emmc file system before shutdown (Iām mounting on startup doing something like this: How to run CoreElec on internal memory eMMC on NG boxes (S905X2, S922X) having full operating Android system too) then when I shutdown the box goes to sleep - I say it goes to sleep and not turns off because the led lights are dark red, not completely off, but perhaps thatās just how it works.
Problem is that with the key map the remote does not wake it.
Resume:
- I can use the remote to turn off Kodi (using the keymap) or to wake the box (using config.ini), but not both.
- Box does not shutdown if a mount to emmc exists (I have to automate the umount on shutdown.sh).
- The box never completely turns the leds light off - theyāre red on shutdown? / suspend.
You are using a tool that wasnāt provided by Team CE. Please test your device running from SD or at least use the official tool ceemmc. This isnāt supported on the king but I can guarantee that itās fully functional.
Sorry but I donāt understand. Which tool am I using that I shouldnāt?
- Is it possible to shutdown and also wake the box from the remote?
- When the box shut downs how should the leds be? (The eyes on the skull). Dark red or completely off?
Than you.
If you followed what is discussed in that topic youāre on your own. My eyes stay red.
Oh no, thatās not it, perhaps thereās a misunderstanding - Iām running CE from the SD card isolated from the Android system.
The only thing I picked from that topic is a couple lines of .sh about how to mount the emmc file system so that I could use the storage space. Thatās all.
If you also have the āred eyesā then it means it is the expected behavior. Good.
The only thing Iām missing now is how to use the power button on the remote to perform both on and off functions.
ā With the keymap if turns off but doesnāt turn on.
ā With config.ini it turns on but doesnāt turn off.
ā With remote.conf if does nothing.
ā Which is your configuration?
I also installed the BL301 but it seems unnecessary.
Thanks!
Ok, sorry. I use BL301 injection but my remote is not the original (it stopped working). Now I use the Khadas vtv remote and just changed the wakeup code on config.ini.
1 Like
Wellā¦ it seems that if I have both config.ini and the keymap I can use the power button to turn on and also to turn off the box!!!
I have to test it better tomorrow.
Thanks.
Hi to all, Iām new to the forum but Iām using coreelec on my gtking from a few month .
I started in the nightly channel and all was good until the last update received with the new kernel .
My system goes in bootloop with both 20191213/14 nightly . I have already tried a clean install of coreelec and Android OS in order to avoid plugin issues . If I revert back to old nightly /9.2.1 stable build all is fine .
Firmware 906p0
Coreelec on SD card
Sn 922x
Does anybody faced the same problem ?
I tested a fresh install if the nightly and it worked on my GT-King.
I know that the following will be some dumb questions but ,on which firmware is your gt king ? Are you booting from as card ? If yes did you used the toothpick method the first time ?
I have tried again but after beelink logo Iām getting a black screen and then the beelink logo again in loop. If I revert to the old nighlies everything is working
I didnāt need to use toothpick method but if youāre having problems you should use it. My android version is 906P0 as yours.
I have the same issue. My only working version of nightly is 20191204. Even I get the full image of 20191214 and make fresh install to spare CF or USB storage the CoreELEC wonāt boot - bootloop.
This continue after I revert the SYSTEM.img and kernel.img. I have to make a fresh install of 20191204 and bytecopy the partition of COREELEC. After this the CF card is already bootable.