Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Setting 1360x760 resolution

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

    Setting 1360x760 resolution

    Hi,
    I am up and running with my new Beelink r89 , I have sucessfully upgrade the f/w to Leolas 0.95, however I have run into a problem in that the resolution of my LCD TV is 1360x760 which is not a selectable option within settings > display > hdmi mode, has anyone got any suggestions on how I set the resolutions.
    Thanks.

    #2
    Originally posted by manc View Post
    Hi,
    I am up and running with my new Beelink r89 , I have sucessfully upgrade the f/w to Leolas 0.95, however I have run into a problem in that the resolution of my LCD TV is 1360x760 which is not a selectable option within settings > display > hdmi mode, has anyone got any suggestions on how I set the resolutions.
    Thanks.
    HDMI resolution differ with LCD resolution,those are independent..

    And there is no such resolution in HDMI
    Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

    Comment


      #3
      Cheers for the reply Oman.

      My 32" LG LCD is a good number of years old but it is still working well, I guess this odd resolution is not supported natively in Android but I dont have the luxury of going out and buying a new 1080p LCD, do I assume I have to put up with the scaled & fussy output I am seeing in Android until some kind sole brings out a firmware that supports 1360x760? If so do you have any suggestions? I feel a little disappointed after spending so much on a nice new media player to find I cannot run the native resolution of my LG TV, hope you can help, its worth pointing out my raspberry pi had no issues at this resolution.

      Thanks.
      Last edited by manc; 14 November 2014, 10:11.

      Comment


        #4
        Originally posted by manc View Post
        Cheers for the reply Oman.

        My 32" LG LCD is a good number of years old but it is still working well, I guess this odd resolution is not supported natively in Android but I dont have the luxury of going out and buying a new 1080p LCD, do I assume I have to put up with the scaled & fussy output I am seeing in Android until some kind sole brings out a firmware that supports 1360x760? If so do you have any suggestions? I feel a little disappointed after spending so much on a nice new media player to find I cannot run the native resolution of my LG TV, hope you can help, its worth pointing out my raspberry pi had no issues at this resolution.

        Thanks.
        I guess it could be fixed by modifying the FB size..

        \kernel\arch\arm\boot\dts\lcd-box.dtsi

        hactive = <1280>;
        vactive = <720>;

        ==>

        hactive = <1360>;
        vactive = <760>;
        Easy way to catch LOG -> Search 'Syslog' in Google Play,then install it and catch log

        Comment


          #5
          Originally posted by oman View Post
          I guess it could be fixed by modifying the FB size..

          \kernel\arch\arm\boot\dts\lcd-box.dtsi

          hactive = <1280>;
          vactive = <720>;

          ==>

          hactive = <1360>;
          vactive = <760>;
          Hmm OK, will give this a go this evening and report back the results.

          Comment


            #6
            Originally posted by oman View Post
            I guess it could be fixed by modifying the FB size..

            \kernel\arch\arm\boot\dts\lcd-box.dtsi

            hactive = <1280>;
            vactive = <720>;

            ==>

            hactive = <1360>;
            vactive = <760>;
            Your going to have to expand up on these instructions, "find / -name lcd" within a terminal windows comes back with nothing?

            Comment


              #7
              Originally posted by manc View Post
              Your going to have to expand up on these instructions, "find / -name lcd" within a terminal windows comes back with nothing?
              It's an information for dev's because he talk about a part at the kernel source...
              So I think it doesn't help you to find a solution
              RK3288 Devices
              - Overview BOX (LINK !)
              - Overview STICK (Dongle) (LINK !)

              MINIX NEO: Z64 W/A - (Intel Z3735F); X8-H Plus - (Amlogic S812H); A2 Lite (sponsored by minix.com.hk)
              UGOOS UT3S (4/32GB with fan) - FW 2.0.6 - (RK3288) (sponsored by GearBest.com)
              Tronsmart Draco AW80 Meta (2/16GB) - FW v2.0rc3 - (Allwinner A80) (sponsored by GeekBuying.com)
              Beelink / UBOX R89 - FW 111k4110_1219 - (RK3288) (sponsored by Netxeon (Beelink))

              RK3188: pcb => "CH001 1332 TN-BX09_V2.1" (K-R42 / CS918...) => wasser KK 1.0.3 (old rev)
              Fly Mouse Mini Wireless Keyboard with 2 mode learning IR remote 'iPazzPort KP-810-16'

              Comment


                #8
                Originally posted by no_spam_for_me View Post
                It's an information for dev's because he talk about a part at the kernel source...
                So I think it doesn't help you to find a solution
                Wish he would of said that, had me running around trying to find these files

                Comment

                Working...
                X