Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Amlogic remote POWER ON scancode hardcoded somewhere in the kernel? (EDIT: actually it's in the bootloader)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Amlogic remote POWER ON scancode hardcoded somewhere in the kernel? (EDIT: actually it's in the bootloader)

    Hello, I have an amlogic S805 box, but I guess all amlogic boes have the same remote scancdes. I tryed to use some random IR remote, I edited the remote.conf with apropriate scancode and apropriate factory code.All is working. I can navigate/play/pause even POWER OFF the device.

    But the problem comes when tyring to POWER ON the device. Only the stock remote works. I guess the remote daemon which is running and handles the remote.conf is not working while the box in in sleep mode and the POWER ON scancode is somehwere hardcoded in the kernel. It will be very bad if it's hardcoded in the IR transmitter itself. Anyone was searching for this? Any clues? But even if it's in the kernel, where do I get the s805 kernel sources to recompile? If it matter the box is Minix Neo X6.

    #2
    It seems that POWER ON scancode in hardcoded in the bootloader. (see https://github.com/kszaq/u-boot/comm...c45c6fbff414L4 )
    Code:
     #define IR_POWER_KEY    0xbf40fe01
     #define IR_POWER_KEY_MASK 0xffffffff
     unsigned int kk[] = { 0xbf40fe01, 0xeb14ff00 };
    I'm not really sure what this gives to me. It seems I need to find somehwere the X6 bootlaoder sources. I don't really want to use some random found sources.

    Comment


      #3
      HEX editor won't work for changing the scancode. I was trying to use a HEX editor to view the bootloader.img It's totally unreadable I reall think there should be some way to unpack the .img file. There should be something in it. It's just an archieve as I udnerstand

      Comment


        #4
        Anyne here knows if its a good idea to flash the bootloader from another s805 box? would I be able to reflash original back?

        Comment


          #5
          Lol?I find this discovery to be very interesting. Since it should at least be possible to unpack the *.img File to eventually 'see' the Files inside of it, and possibly edit it. This could be a better fix for the Remote. AFAIK though the only tool I know of that could do this however is Android Kitchen. Problem there is it fell outta support like three years ago now.

          I don't know what Remote you have... I have a Logitech Harmony One. My work around for that was to just Clone the Power On Button from the Stock Remote. And, set the Power Off (remote.conf) to 703* IIRC which is the command for Shutdown / Suspend.

          *I have an S802 MXIII though these Remote Codes are likely generic, your mileage may vary.

          Edit - I would be cautious when it comes to the bootloader, as the permabrick risk is fairly large if you somehow got it wrong. Though as I understand it, it should be possible to run a bootable recovery off a MicroSD Card in the event of such a brick. Unfortunately through that it seems is not always a silver bullet though.

          Comment


            #6
            Originally posted by Ichijoe View Post
            I don't know what Remote you have... I have a Logitech Harmony One. My work around for that was to just Clone the Power On Button from the Stock Remote. And, set the Power Off (remote.conf) to 703* IIRC which is the command for Shutdown / Suspend.
            I just took a random remote I had from an old TV. I just like how it looks and feels. It's not programable, so I can't assign default power scancode to remote's power button. This is why I was searching for a way to teach the box to understand remotes power code. Do you know if it safe to write new bootloader to sdcard and try to boot with it? Or it will overrride my default bootlaoder and make a brick if something goes wrong?

            Comment


              #7
              I would say that "safe" was as relitve to your programming skills, and the tools as such at your disposal to get the job done. For me it would be a no, go. As I have no experience in reading such code. Nor assuming that such code once repacked back into a *.img File would still be valid.

              The only thing I know, or think I know (more likely), is that you 'mess' with the Bootloader at your own peril. Cause if you manage to break that, you'll have essentially a hard brick on your hands. While recovery Might still be possible. Under such conditions, it will neither be as simple (which it already isn't), nor as straight forward either. And will likely require you to hack up some JTAG Programmer to the Device to replace said Bootloader.

              My advice to you would be to have a look on Fle**** for a slightly older Logitech Harmony One Remote. They seem to be going for 40~60€'s there. I think I might have blown closer to 200€ for mine back in 2007. So I don't know it that's still to pricy for you. But, you'll never need another IR Remote again. And as a long time user I will say it was worth the cost of it.

              Comment

              Working...
              X