Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Tutorial: Enable RK3368 True Octa-Core Processor - Part 1 of 2

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

    #46
    Originally posted by Shomari View Post
    ... also - change your cpu mem alignment in init.rc from the default '4' to 1 or 0. That'll help with the segfaults causing reboots during some benchmarks.
    write /proc/cpu/alignment 0

    Also I am using the geekbox sources. Android 6.0.1 AOSP you can find it on the geekbox forums or github.

    Also what reboot bug are you talking about? Mine seems to run fine for over a day of being on.

    Comment


      #47
      ... yeah my boxes are rock solid stable, it's just if you try to reboot or power off it doesn't. It just freezes right there. That's the only minor bug left in my code that I haven't solved.

      Comment


        #48
        Originally posted by Shomari View Post
        ... yeah my boxes are rock solid stable, it's just if you try to reboot or power off it doesn't. It just freezes right there. That's the only minor bug left in my code that I haven't solved.
        Mine will reboot if I tell it to. adb reboot or in terminal emulator reboot.

        Comment


          #49
          Originally posted by l33tlinuxh4x0r View Post

          That line doesn't even exist in my init.rc! I guess that means it is already off

          EDIT: found it in another init file.

          Also I am changing cpu mem alignment to 0.
          it'll be in init.rc in 5.x, but I see you found it. It'll never be off by default, that's for sure

          Comment


            #50
            Originally posted by l33tlinuxh4x0r View Post

            Mine will reboot if I tell it to. adb reboot or in terminal emulator reboot.
            Upload your resource.img, if you don't mind. Something in my resource is messing with the power regulator

            Comment


              #51
              Originally posted by Shomari View Post

              Upload your resource.img, if you don't mind. Something in my resource is messing with the power regulator
              I'll upload it in a minute... I think that I broke bluetooth
              Attached Files

              Comment


                #52
                Originally posted by l33tlinuxh4x0r View Post

                I'll upload it in a minute... I think that I broke bluetooth
                ... judging from what I've seen so far, I'm sure you'll figure it out. I'll help however I can

                Comment


                  #53
                  Originally posted by Shomari View Post

                  ... judging from what I've seen so far, I'm sure you'll figure it out. I'll help however I can
                  I have an even bigger problem. It has been bugging me for days. I cannot do a clean flash of my firmware that I built. I have to flash stock firmware first and then flash mine on top of it otherwise not all of the partitions will be created and/or mounted Any ideas on why that might be?

                  Comment


                    #54
                    Originally posted by l33tlinuxh4x0r View Post

                    I have an even bigger problem. It has been bugging me for days. I cannot do a clean flash of my firmware that I built. I have to flash stock firmware first and then flash mine on top of it otherwise not all of the partitions will be created and/or mounted Any ideas on why that might be?
                    ...hmmm. That sounds vaguely familiar. What other steps were different in your build process other than your kernel/resource changes? Something must be up with either your parameter file or you misc.img, most likely

                    Comment


                      #55
                      Couple things; your resource still has 'safe frequency' parameters set in the cpufreq node - you don't want those if you're after peak performance. I've removed them and have yet to find issue.

                      Also, your cpu-map has two clusters, cluster 0 and cluster 1, but all your cpus were migrated into cluster0 for the cpu hack. Cluster1 is empty, so I'd remove it from the node.

                      Comment


                        #56
                        Interestingly enough - I bet if you take out that empty cluster1 from the node it'll cause the reboot bug to show. Because when I did that months ago, is when the bug came back..

                        Comment


                          #57
                          Originally posted by Shomari View Post
                          Couple things; your resource still has 'safe frequency' parameters set in the cpufreq node - you don't want those if you're after peak performance. I've removed them and have yet to find issue.

                          Also, your cpu-map has two clusters, cluster 0 and cluster 1, but all your cpus were migrated into cluster0 for the cpu hack. Cluster1 is empty, so I'd remove it from the node.
                          yeah I left cluster1 in there empty of course because otherwise it complains.

                          Comment


                            #58
                            Originally posted by Shomari View Post

                            ...hmmm. That sounds vaguely familiar. What other steps were different in your build process other than your kernel/resource changes? Something must be up with either your parameter file or you misc.img, most likely
                            what is the misc.img used for anyway? How do I edit it?

                            Comment


                              #59
                              As far as Bluetooth, your kernel build targets 8723bs ... that might be the problem?

                              Comment


                                #60
                                Originally posted by l33tlinuxh4x0r View Post

                                what is the misc.img used for anyway? How do I edit it?
                                Nice thread. Good work. misc.img tells the box what to do on next boot. http://www.mediafire.com/file/a9mvg4sk4hb9y74/misc.zip here are some i have collected. Cant remember what the one i labeled clear does. Maybe that is why when you flash yours it doesnt boot. Try using the wipe all one. Second though maybe better take misc from the stock one and bring into yours. I bet it boots after that.
                                Prahjister ****MK808(nonB)****MK808B V5****MK808B Plus****UBOX R89**** CX919****MK808B Pro****Nexbox N9****Eny Em95****Matricon Q2****Tanix TX5 Pro****

                                Comment

                                Working...
                                X