Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

RK3399 and HDMI CEC

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

    RK3399 and HDMI CEC

    Hi,

    I have Qintaix Q39 TV box. It's great hardware, but I'm really upset that there is no HDMI CEC support, and I have to use second pilot for controlling STB.

    I've checked kernel drivers for RK3399 and it looks like it support CEC.
    Also in some RK3399 box specifications CEC function appear ( for example in H69 Max http://www.gearbest.com/tv-box-mini-pc/pp_627166.html )

    Can owners of different RK3399 TV box can report if they have CEC support?

    #2
    Hi melgurth ,

    it is supported , but i think it is not fixed maybe a Software Bug ???

    greetings

    gefattern

    Comment


      #3
      OK - I have following question:

      Is it possible to flash other device firmware to another one?

      My Qintaix Q39 is based on HTC-T077-V2 (2017-03-02) board and have AP6255 WiFi chipset so it is the same PCB as in CSA96 and R-TV BOX K99.
      Can I safely flash it with other box firmware? I'm really interested in testing firmware from thread : "Firmware Android 7.1.2 Stock AlfaWise H96 MAX (Rk3399) 4Gb/32G" is there a chance that it will work?

      If so, it will be good to have some compatibility chart of cross-device firmwares.

      Comment


        #4
        Yes possible also possible brick. That why it good to wait see how unbrick goes and must have original firmware.
        Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

        Comment


          #5
          ... so I broke and flashed some firmwares to check if Q39 firmware is bugged.

          I can report that any of following firmwares can be flashed and in case of Boot fail it can be easily recoverable.
          Firmware name flashing / booting CEC working
          CSA96 CSA96RK3399_6255_6.0_ota_20170303.img OK/OK NO
          H96 Max rk3399_H96_4+32G_max_170526.img OK/Boot fail N/A
          H96 Max rk3399_7.1_hcy_stb_ap6255_170721.img OK/Boot fail N/A
          R-TV K99 R-TV BOX K99_RK3399_wifi6255_6.0_20170302.img OK/OK NO
          VORKE Z3 VORKE Z3 Android7.1 RK3399 382994 20170914.img OK/OK NO Remote controller not working
          Yundoo Y8 yundoo_y8_6.0.1_ap6356_4g32g_170605.img OK/OK NO Remote controller not working
          Q39 Q39_6.0_root_20170614.img (native device) OK/OK NO
          So... no matter which firmware was used HDMI-CEC did not worked. Probably hardware issue ?

          I must check CEC comptibility with other TVs, maybe this device supports CEC but it somehow doesn't work with my TV.

          Comment


            #6
            Originally posted by melgurth View Post
            ... so I broke and flashed some firmwares to check if Q39 firmware is bugged.

            I can report that any of following firmwares can be flashed and in case of Boot fail it can be easily recoverable.
            Firmware name flashing / booting CEC working
            CSA96 CSA96RK3399_6255_6.0_ota_20170303.img OK/OK NO
            H96 Max rk3399_H96_4+32G_max_170526.img OK/Boot fail N/A
            H96 Max rk3399_7.1_hcy_stb_ap6255_170721.img OK/Boot fail N/A
            R-TV K99 R-TV BOX K99_RK3399_wifi6255_6.0_20170302.img OK/OK NO
            VORKE Z3 VORKE Z3 Android7.1 RK3399 382994 20170914.img OK/OK NO Remote controller not working
            Yundoo Y8 yundoo_y8_6.0.1_ap6356_4g32g_170605.img OK/OK NO Remote controller not working
            Q39 Q39_6.0_root_20170614.img (native device) OK/OK NO
            So... no matter which firmware was used HDMI-CEC did not worked. Probably hardware issue ?

            I must check CEC comptibility with other TVs, maybe this device supports CEC but it somehow doesn't work with my TV.
            Hi ,

            if all this FWs support it , it is for sure not good coded in the FW , i am sure they use all the same .

            good luck / gefattern

            Comment


              #7
              Originally posted by melgurth View Post
              ... so I broke and flashed some firmwares to check if Q39 firmware is bugged.

              I can report that any of following firmwares can be flashed and in case of Boot fail it can be easily recoverable.
              Firmware name flashing / booting CEC working
              CSA96 CSA96RK3399_6255_6.0_ota_20170303.img OK/OK NO
              H96 Max rk3399_H96_4+32G_max_170526.img OK/Boot fail N/A
              H96 Max rk3399_7.1_hcy_stb_ap6255_170721.img OK/Boot fail N/A
              R-TV K99 R-TV BOX K99_RK3399_wifi6255_6.0_20170302.img OK/OK NO
              VORKE Z3 VORKE Z3 Android7.1 RK3399 382994 20170914.img OK/OK NO Remote controller not working
              Yundoo Y8 yundoo_y8_6.0.1_ap6356_4g32g_170605.img OK/OK NO Remote controller not working
              Q39 Q39_6.0_root_20170614.img (native device) OK/OK NO
              So... no matter which firmware was used HDMI-CEC did not worked. Probably hardware issue ?

              I must check CEC comptibility with other TVs, maybe this device supports CEC but it somehow doesn't work with my TV.
              You need to enable cec in the kernel dts or add it if it's missing(probably the case in all the above bug-filled firmwares).

              Comment


                #8
                No further questions
                You may only view thumbnails in this gallery. This gallery has 1 photos.

                Comment


                  #9
                  Originally posted by melgurth View Post
                  No further questions
                  At least they are honest that they have no clue about their own products and are not interested to fix it.

                  Comment


                    #10
                    melgurth, not that it seemed to work for me but I found hdmi CEC settings with vorke z3 firmware (probably there on all Rk3399 's). download activity launcher from play store & click all activity, scroll down to settings & open then scroll down to com.android.tv.settings.system.InputsActivity
                    Was a while back, you probably sorted it by now

                    Comment

                    Working...
                    X