Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

[ROM] QBOX 2GB/16GB Superceleron v1.0

Collapse
This is a sticky topic.
X
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #16
    Originally posted by superceleron View Post
    [*]Removed the default launcher it have a lot of stability problems, so you will lose the led color change since its the launcher that controls it!

    you the man! will definitely try this. will you be able to do something about the led lights being controlled outside the original SunvellWin8Launcher? in case you decide to look into this, maybe this would help:

    - as you well said it, leds only work while in home screen on original sunvellwin8launcher

    - dmesg in terminal emulator gives the below for the led button on the remote:
    <1>[ 328.006310@1] QBled: cmd:0
    <1>[ 328.006333@1] QBled: arg:3remote: press ircode = 0x42, (204) (info)
    <6>[ 329.341866@0] remote: scancode = 0x00cc,maptable = 0,code:0xbd42fd88

    also this (note the bold red that i highlighted)
    <1>[ 790.572888@2] QBled: arg:0type=1400 audit(1420071193.720:20): avc: denied { getattr } for pid=4788 comm="ll.win8launcher" path="/dev/qbled_dev" dev="tmpfs" ino=11295 scontext=u:r:untrusted_app:s0 tcontext=ubject_r:device:s0 tclass=chr_file permissive=1

    - the ir code "0x42" is mapped as linux keycode "204" as seen in /system/etc/remote.conf

    - the linux keycode 204 is mapped as android keycode "info" as seen in /system/usr/keylayout/Vendor_0001_Product_0001.kl

    that's all i've got and that's as far as my knowledge took me. maybe you can uncover more in order to have this led lights controlled independently, should you decide to do so.

    thanks for your efforts anyway!
    Last edited by carianis; 07 July 2016, 06:44.

    Comment


      #17
      Im running the newest version of the qbox firmware firmware and it it really works great however I have a USB Camera with Mic hooked up It works on SKype and voice recorder but when i open google voice search or web search through google its always cant open mic Do you know how to fix this or at the very least does it work on your firmware I started with the newest updated firmware and created my own rom but would switch to yours if this would just work i have also had this problem on every china box running 5.0 but all 4.4 voice always works

      Comment


        #18
        Hi superceleron
        Thanks for your hard work.
        I've got a beelink minimx mxiii s905 2/16 Gb, should this rom work ? I've successfully used your 1.0 with only wifi broken.
        Any comments on the dts shuttering, Is it still present ?

        And finally, would you share on a private bitbucket your sources so I could help. I was building and cooking a lot on various device. Of course, no rom released without your approval and references, check my profile on xda
        Best

        Comment


          #19
          Originally posted by carianis View Post


          you the man! will definitely try this. will you be able to do something about the led lights being controlled outside the original SunvellWin8Launcher? in case you decide to look into this, maybe this would help:

          - as you well said it, leds only work while in home screen on original sunvellwin8launcher

          - dmesg in terminal emulator gives the below for the led button on the remote:
          <1>[ 328.006310@1] QBled: cmd:0
          <1>[ 328.006333@1] QBled: arg:3remote: press ircode = 0x42, (204) (info)
          <6>[ 329.341866@0] remote: scancode = 0x00cc,maptable = 0,code:0xbd42fd88

          .................
          When i have sometime i will check that!
          Nice find

          Originally posted by Abysstech View Post
          Im running the newest version of the qbox firmware firmware and it it really works great however I have a USB Camera with Mic hooked up It works on SKype and voice recorder but when i open google voice search or web search through google its always cant open mic Do you know how to fix this or at the very least does it work on your firmware I started with the newest updated firmware and created my own rom but would switch to yours if this would just work i have also had this problem on every china box running 5.0 but all 4.4 voice always works
          Dunno, don't have a camera with mic to try it!

          Originally posted by BENETNATH View Post
          Hi superceleron
          Thanks for your hard work.
          I've got a beelink minimx mxiii s905 2/16 Gb, should this rom work ? I've successfully used your 1.0 with only wifi broken.
          Any comments on the dts shuttering, Is it still present ?

          And finally, would you share on a private bitbucket your sources so I could help. I was building and cooking a lot on various device. Of course, no rom released without your approval and references, check my profile on xda
          Best
          No don,t try it, i don't feel safe that the bootloader are the same and you can hardbrick the box.
          About the source, sorry i cant help you on that, amlogic are very strict on that thing(well i don't care about that... but i do care because of the person who gave it to me asked not to share and i,m not going to do it)
          Sorry!
          But i can tell you that beelink M18 was made with the same sdk....!

          Comment


            #20
            gasp..that's frustrating ^^
            any way to discard the bootloader part and get a s905 generic rom ??

            Edit : As you can see, your previous rom works well : http://freaktab.com/forum/tv-player-...nk-mini-mx-iii

            Comment


              #21
              Yes i know
              And yes u can, and is pretty simple to do it!
              You need it from the original rom, and transplant it to this one!

              Comment


                #22
                Hi Superceleron!

                Thank you a LOT for your rom. It is great that someone is bringing a little love to our 905 devices! You are correct that the firmware by the box-"builders" is mostly just a quick and dirty publish so that they can sell their boxes. They don't spend much time on details and polish.

                I don't know if you have read my thread


                It seems that DTS passthrough is broken (it has audio-drops every 5-7 seconds) on all 905 boxes in Kodi because Andoid API21 does not support DTS passthrough (only AC3) and Kodi/SPMC do the passthrough by various hacks (ie. sending IEC frames over PCM) and that does not seem to work out very good in all cases. Android API23(Version 6.x) will support DTS and they say that it will work then.

                NVidia shield went another way and backported API23 to Android 5.1 so in the shield DTS passthrough works even though they are on Android 5.1.

                I will test with your rom and see if it has he same DTS passthrough problems as the stock roms.

                Thanks again and I will buy you a beer or two if things work! :-)

                Comment


                  #23
                  well dunno about this one but i think you have to wait for the 6 to came out for the final fix for it!
                  I dint test this one on DTS since i dont have DTS decoder but i almost bet it wont work! that is a general problem like you said of the s905 SDK!

                  Comment


                    #24
                    I aren't able to restore a backup of this rom via TWRP.

                    I ]get the error message 'extractTarFork() process ended with ERROR: 255' during the restore of the system partitition. After this I can't reboot the system and have to reboot into recovery and choose a backup of the original rom and then reboot into the system. I'm obliged to reflash this rom via the USB flashing tool.

                    Anyone have any idea what's wrong ?

                    Comment


                      #25
                      Hmm need to talk with abdul_pt to see where is the problem with the TWRP!

                      Comment


                        #26
                        Hmmmm seems to be not what rom was built for and Louis being hellful but guy who ported to this device missing in action?
                        Many devices now mk902ii/Shield/Mk68 /Ugoos/neox5/minix5 (yes they still work lol) mk80 no it doesnt work lol.

                        Comment


                          #27
                          so, for those of you who want to control the leds from an airmouse instead of the original remote, it is doable by remapping a button of your choice from your airmouse. i won't describe the whole process, as there are plenty how to guides outhere. all you need to know is that you have to give that button the android keycode "INFO". so, find the scancode of the button you choose with keytest app and write/overwrite to the right of the key number INFO in Vendor_xxxx_Product_xxxx.kl in /system/user/keylayout. vendor and product details you'll find by typing this in terminal emulator cat /proc/bus/input/devices attached is my kl file, note key 155, this was keycoded ENVELOPE and i changed it to INFO (i can't seem to upload this 9kb file now). remember, this will only work while in homescreen on the stock sunvellwin8launcher.
                          i wasn't sure if i should post this here, but i did because i wanted superceleron to see it in case it helps with getting these lights to work outside the stock launcher.

                          Comment


                            #28
                            hmm well... like i said i check that, but not now the box are the daily usage of me kids(you know school vacations) so i cant touch it now util i get another to put in is place!
                            So you guys have to wait or if someone want to try fixing it... go for it

                            Comment


                              #29
                              Originally posted by Twosheds
                              I aren't able to restore a backup of this rom via TWRP.

                              I ]get the error message 'extractTarFork() process ended with ERROR: 255' during the restore of the system partitition. After this I can't reboot the system and have to reboot into recovery and choose a backup of the original rom and then reboot into the system. I'm obliged to reflash this rom via the USB flashing tool.

                              Anyone have any idea what's wrong ?
                              Recovery log please.



                              Tapatalked

                              if [ $up.post.type = $type.two.lazy.to_use_google ] || [ $up.post.type = $type.silly_question ];
                              then mv $user.contact.up.post /.trash; set response($response.type = ignore);
                              $user.up.post.ignore_in_future = true; fi;

                              Comment


                                #30
                                Kodi can not HD DTS it? It is better to be able to transplant and rk3368, zidoo 905 decoding is still good, and hope to have someone to transplant!

                                Comment

                                Working...
                                X