Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

CM11 for A/S8 (in-progress)

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

    #31
    Sorry for the wait guys. I had bunch of schoolwork plus I thought the thing got bricked lol PhoenixSuit saves my butt again lol.

    Comment


      #32
      Lol tell me about it. I think I've bricked at least 6 times now and reflashing saves e butt

      Sent from my SPH-L710 using Tapatalk

      Comment


        #33
        I don't know anything about programming, and I really wish I did, in fact, I want to study it. Anyways, I just want to say that you guys are awesome!!!!! I find it fantastic that you guys take time to help out strangers whose as/8 has been a big disappointment, I thank you all for your hard work!

        Comment


          #34
          So I compiled a Cubieboard2 3.3 kernel instead of a 3.4 because of too many drivers to install. I'll test it out when I get a chance.

          Comment


            #35
            Made progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.

            Comment


              #36
              Any updates on this. Would love to run CM11.

              Comment


                #37
                Originally posted by AManofFewWords View Post
                Made progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.
                awesome job! just out of curiosity where did u get your cm11 from? I might wanna try to get it on the previous gen pmid devices
                https://public.bay.livefilestore.com...ion.png?psid=1

                Comment


                  #38
                  Originally posted by AManofFewWords View Post
                  Made progress on the Cubieboard2 kernel. It actually goes past the Polaroid logo and is met with a grey screen. It's most likely a missing LCD module (a CB2 is a board without a touchscreen) I have the CB2's source code and it includes a "Cubieboard2-LCD" option upon lunching. Will look into this.
                  bro,

                  you need to compile the hardware drivers with the kernel source... you have two options for the maili drivers.. you either use the proprietary drivers which are currently closed source (as far as i know) or you can use the open source mali drivers (still a work in progress) for an almost as-good alternative. you can get the open source alternative from malideveloper.arm.com (or something like that)..

                  btw, great work..

                  Comment


                    #39
                    The problem is that the ramdisk contains kernel modules as well, actually, the basic modules to use the tablet (lcd.ko, hdmi.ko, disp.ko, touch.ko) The other modules the tablet needs can already be preinstalled inside the kernel during compilation.

                    Comment


                      #40
                      Originally posted by AManofFewWords View Post
                      The problem is that the ramdisk contains kernel modules as well, actually, the basic modules to use the tablet (lcd.ko, hdmi.ko, disp.ko, touch.ko) The other modules the tablet needs can already be preinstalled inside the kernel during compilation.

                      I wouldn't advise compiling all the drivers inside the kernel.. It will make your kernel bloated (bigger) and slower to boot.. Depending on which kernel you are building - (if kernel 3.3)there is a chance of using existing modules from the device. You will see the modules inside the vendor folder on the system partition.

                      The modules that are contained inside the ramdisk is used to start the initial support for device operations. During the init.${hardware}.rc init process (which is imported by init.rc) the other modules are activated when called upon.

                      The time saved by the kernel not having to outsource for modules have been overcome by speeds of current architectures. You may be able to completely strip the kernel of all things not needed and run only basic devices to improve speeds in that manner. However, it is not a common practice at this time. Things have changed since the old days.

                      Also, you may find some device drivers that will only compile as modules.

                      Comment


                        #41
                        I'm gonna take another strike at this and recompile the ramdisk modules, I mean, it won't hurt, the device already runs 3.3 anyway :P that system/vendor/modules directory helps A LOT, I mean who would want to compile over 60 modules for one folder? :P

                        Comment


                          #42
                          Any updates on the progress of this rom?

                          Comment


                            #43
                            I was about to ask the same thing, any updates of the progress of this rom so far?

                            Comment


                              #44
                              Refiring the compilation now, updated repos etc. new device tree (will upload to github). New compiled kernel (nearly the same size as stock only .2 MB off (features))

                              Comment


                                #45
                                Github

                                Where is the github you uploaded it to?

                                Comment

                                Working...
                                X