Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

Pipo M6 Pro RileyROM 1.5

Collapse
X
Collapse
 
  • Page of 18
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 6 7 8 9 10 11 12 14 18 template Next
    #46
    Originally posted by Satbeginner View Post
    Hello all,

    on this quiet Sundaymorning I did some testing with my M6Pro and the Giouncino kernels.
    Here are the results:

    AnTuTu @ 17980 with Rileyrom 1.5 kernel

    AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_1325mV_gpu600h STOCK_ddr720_Claro.zip
    Boot, but hangs in AnTuTu CPU float performance (@21%)


    AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_gpu600_ddr720_target_2.1
    Does not boot at all


    AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_gpu600h_ddr720_VERY_LOW_voltag es
    Does not boot at all

    When I was using the Riley 1.3a my M6 Pro allowed for a patched kernel, but with the Riley 1.5 only the default Riley kernel works good.
    I think it has to do with my M6, maybe others will have better results.

    Un saludo.

    Hi! I have the exact same problem.. (althou it boots with _target_2.1)..
    I still use the Claro and it works good... but cant do stability or test in antutu (hangs on 21%)

    Cheers

    Comment

      #47
      Patched kernels in Riley 1.5

      Originally posted by giouncino View Post
      Strange...
      I have used exaclty the same scripts of the previous release...
      Which version of my kernel did you use on previous ROM?
      In the 1.3a Riley-rom I used the patched kernel that came with that rom.
      It was not one of yours, I am sorry.

      Because of the differences between the 1.3 stock and the 12052013 pipo version I do not want to try the 'old' 1.3a patched kernel with the present 1.5 riley rom.

      Un saludo.
      Last edited by Satbeginner; 15 December 2013, 23:13. Reason: typos

      Comment

        #48
        TITANIUM BACKUP...

        Apologies if out of place, but this subject is relevant here as it is part of the flashing process, so, here goes.

        Installed RR v.1.5 (so far so good, THX), had been using v.1.3a since several days after it was released, but unfortunately Titanium Backup Pro (I bought it based on recommendation here) wil not restore ANY of the multiple backups I did, it can't find them, and it's a REAL PITA...
        Try to change the backup folder to the folder with my backups, and it will not let me change the folder whatsoever, nor does the auto-detect feature work.

        I had finally settled in my new Pipo since Randy FIXED Pipo's chronic lockup issue (?feature?) while Pipo did nothing in regard to it that I experienced.

        The configuration I did took me a good bit of time as I'm sure all know that routine, and it is now in limbo awaiting Titanium support, and I will not spend any more time at this point trying to even mess with it, so my tablet is pretty much down pending Titanium Backup Support.

        No support forums at Titanium either, but a lot of instructions, FAQ, troubleshooting, etc., but try to get support if you need it, and I think you'll find it is quite ghostly and an until they are ready type of deal.


        I guess a "browse to select backup" is an idea Titanium never considered.
        Never had to do a restore before, and now that I need it, TB isn't getting it done, so be made aware.

        Comment

          #49
          Titanium backup?

          Originally posted by si3Dp7NXwLfb View Post
          Apologies if out of place, but this subject is relevant here as it is part of the flashing process, so, here goes.

          Installed RR v.1.5 (so far so good, THX), had been using v.1.3a since several days after it was released, but unfortunately Titanium Backup Pro (I bought it based on recommendation here) wil not restore ANY of the multiple backups I did, it can't find them, and it's a REAL PITA...
          Try to change the backup folder to the folder with my backups, and it will not let me change the folder whatsoever, nor does the auto-detect feature work.

          I had finally settled in my new Pipo since Randy FIXED Pipo's chronic lockup issue (?feature?) while Pipo did nothing in regard to it that I experienced.

          The configuration I did took me a good bit of time as I'm sure all know that routine, and it is now in limbo awaiting Titanium support, and I will not spend any more time at this point trying to even mess with it, so my tablet is pretty much down pending Titanium Backup Support.

          No support forums at Titanium either, but a lot of instructions, FAQ, troubleshooting, etc., but try to get support if you need it, and I think you'll find it is quite ghostly and an until they are ready type of deal.


          I guess a "browse to select backup" is an idea Titanium never considered.
          Never had to do a restore before, and now that I need it, TB isn't getting it done, so be made aware.
          I went through the same process, but I found the backup on the internal sdcard after I made it.
          So before flashing everything (thus erasing) I copied the backup directory via usb to my PC.
          Than I did the flash, and after a the first reboot of the tablet I copied the backup-dir back to the pipo.
          Reinstalled titanium and did the restore.

          If you fully flashed without securing the backup it probably is lost...:-(
          If so, I am sorry.

          Comment

            #50
            I copied the backup folder on a micro-sd card.
            after flashing, i install Titanium backup and make an autodetect of backup, TB find it on micro SD then set it as default location for EVERY future backup/restore.
            In my opinion this is the best you can do!
            if you appreciate my efforts this is the link for any donation:
            https://www.paypal.com/cgi-bin/websc...NonHostedGuest

            Comment

              #51
              Originally posted by Satbeginner View Post
              In the 1.3a Riley-rom I used the patched kernel that came with that rom.
              It was not one of yours, I am sorry.

              Because of the differences between the 1.3 stock and the 12052013 pipo version I do not want to try the 'old' 1.3a patched kernel with the present 1.5 riley rom.

              Un saludo.
              Ok, your CPU is probably not lucky. The mod kernel with the firmware you used has only ram overclocked and nothing else.
              if you appreciate my efforts this is the link for any donation:
              https://www.paypal.com/cgi-bin/websc...NonHostedGuest

              Comment

                #52
                Originally posted by Satbeginner View Post
                If you fully flashed without securing the backup it probably is lost...:-(
                If so, I am sorry.
                LOL, a bit of bluntness and sincerity in the world to bring me to the realization that I !@#$ ^... THX

                Oh gosh...Imma feeling like a 1-legged duck that just realized a rather large cat is intensely staring at me

                Comment

                  #53
                  RAM only?

                  Originally posted by giouncino View Post
                  Ok, your CPU is probably not lucky. The mod kernel with the firmware you used has only ram overclocked and nothing else.
                  Hello, would it be possible /difficult to create a kernel based on the 1.5 riley rom with just the ram overclocked?
                  Or give me some directions how to do this myself?

                  I am new to this, but I am a good reader, I think...

                  Un saludo desde Espana

                  Comment

                    #54
                    Too late to run

                    Originally posted by si3Dp7NXwLfb View Post
                    LOL, a bit of bluntness and sincerity in the world to bring me to the realization that I !@#$ ^... THX

                    Oh gosh...Imma feeling like a 1-legged duck that just realized a rather large cat is intensely staring at me

                    Comment

                      #55
                      cameras cannot be initialized

                      Hello.
                      Can someone help me with my trouble?
                      Yesterday I've received my "Pipo M6pro 3G". I found that both cameras does not working.
                      On stock firmware any try to open camera results in tablet reboot.
                      I've flashed RileysROM 1.4.2 - now I have no reboots, but the cameras still not working - all applications trying to use camera stopping with error or hanging.
                      I found, that the kernel cannot initialize cameras:
                      Code:
                      ------ KERNEL LOG (dmesg) ------
<3>[    6.305325] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 2...
<3>[    6.305490] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 1...
<3>[    6.305649] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 0...
<3>[    6.305674]  ov5640 write reg(0x3008, val:0x80) failed, try to write again!
<3>[    6.305842] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 2...
<3>[    6.306002] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 1...
<3>[    6.306162] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 0...
<3>[    6.306185]  ov5640 write reg(0x3008, val:0x80) failed, try to write again!
<3>[    6.306352] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 2...
<3>[    6.306513] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 1...
<3>[    6.306671] i2c i2c-3: No ack, Maybe slave(addr: 0x3c) not exist or abnormal power-on, retry 0...
<3>[    6.306693]  ov5640 write reg(0x3008, val:0x80) failed, try to write again!
<3>[    6.306723] soft reset ov5640 failed
<3>[    6.319048] camera 33-0-ov5640_back: Probe ov5640_back failed
<3>[    6.335459] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 2...
<3>[    6.335616] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 1...
<3>[    6.335771] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 0...
<3>[    6.335792]  ov2659 write reg(0x103, val:0x1) failed, try to write again!
<3>[    6.335956] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 2...
<3>[    6.336111] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 1...
<3>[    6.336265] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 0...
<3>[    6.336286]  ov2659 write reg(0x103, val:0x1) failed, try to write again!
<3>[    6.336448] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 2...
<3>[    6.336603] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 1...
<3>[    6.336758] i2c i2c-3: No ack, Maybe slave(addr: 0x30) not exist or abnormal power-on, retry 0...
<3>[    6.336779]  ov2659 write reg(0x103, val:0x1) failed, try to write again!
<3>[    6.336805] soft reset ov2659 failed
<3>[    6.349059] camera 33-1-ov2659_front: Probe ov2659_front failed

                      so applications trying to open camera have an exception:

                      Code:
                      ------ SYSTEM LOG (logcat -v threadtime -d *:v) ------
12-16 12:08:48.681  5876  5892 V CameraHolder: open camera 0
12-16 12:08:48.691   110   450 E CameraService: CameraService::connect X (pid 5876) rejected (invalid cameraId 0).
12-16 12:08:48.701  5876  5892 E CameraHolder: fail to connect Camera
12-16 12:08:48.701  5876  5892 E CameraHolder: java.lang.RuntimeException: Fail to connect to camera service
12-16 12:08:48.701  5876  5892 E CameraHolder:     at android.hardware.Camera.native_setup(Native Method)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at android.hardware.Camera.<init>(Camera.java:340)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at android.hardware.Camera.open(Camera.java:302)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at com.android.camera.CameraHolder.open(CameraHolder.java:210)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at com.android.camera.Util.openCamera(Util.java:315)
12-16 12:08:48.701  5876  5892 E CameraHolder:     at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:319)
12-16 12:08:48.701  5876  5892 W dalvikvm: threadid=13: thread exiting with uncaught exception (group=0x4103c930)
12-16 12:08:48.701  5876  5892 E AndroidRuntime: FATAL EXCEPTION: Thread-402
12-16 12:08:48.701  5876  5892 E AndroidRuntime: java.lang.RuntimeException: openCamera failed
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.Util.openCamera(Util.java:320)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.PhotoModule$CameraStartUpThread.run(PhotoModule.java:319)
12-16 12:08:48.701  5876  5892 E AndroidRuntime: Caused by: com.android.camera.CameraHardwareException: java.lang.RuntimeException: Fail to connect to camera service
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.CameraHolder.open(CameraHolder.java:219)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.Util.openCamera(Util.java:315)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     ... 1 more
12-16 12:08:48.701  5876  5892 E AndroidRuntime: Caused by: java.lang.RuntimeException: Fail to connect to camera service
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at android.hardware.Camera.native_setup(Native Method)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at android.hardware.Camera.<init>(Camera.java:340)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at android.hardware.Camera.open(Camera.java:302)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.CameraManager.cameraOpen(CameraManager.java:283)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     at com.android.camera.CameraHolder.open(CameraHolder.java:210)
12-16 12:08:48.701  5876  5892 E AndroidRuntime:     ... 2 more

                      I'm asking all who can know something about this: What is this? Can it be software problem or it's a hardware fail of cameras?


                      (full adb bugreport is here)

                      Comment

                        #56
                        Originally posted by Satbeginner View Post
                        Hello all,

                        on this quiet Sundaymorning I did some testing with my M6Pro and the Giouncino kernels.
                        Here are the results:

                        AnTuTu @ 17980 with Rileyrom 1.5 kernel

                        AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_1325mV_gpu600h STOCK_ddr720_Claro.zip
                        Boot, but hangs in AnTuTu CPU float performance (@21%)


                        AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_gpu600_ddr720_target_2.1
                        Does not boot at all


                        AnTuTu @ No Score, with Giouncino kernel_1.5_cpu1704h_gpu600h_ddr720_VERY_LOW_voltag es
                        Does not boot at all

                        When I was using the Riley 1.3a my M6 Pro allowed for a patched kernel, but with the Riley 1.5 only the default Riley kernel works good.
                        I think it has to do with my M6, maybe others will have better results.

                        Un saludo.
                        Interesting. This sounds *very* familiar!!!

                        Does anybody have an M6 Pro flashed at 1.5 and stable using anything other than the stock kernel? If so which kernel are you using?

                        Comment

                          #57
                          Originally posted by ArCh View Post
                          ...

                          I'm asking all who can know something about this: What is this? Can it be software problem or it's a hardware fail of cameras?


                          (full adb bugreport is here)
                          May be problem with camera-connector?
                          You must check 4pda-forum, some people had same problem.

                          Comment

                            #58
                            Kernel with only RAM overclocked, based on Riley 1.5

                            Originally posted by Satbeginner View Post
                            Hello, would it be possible /difficult to create a kernel based on the 1.5 riley rom with just the ram overclocked?
                            Or give me some directions how to do this myself?

                            I am new to this, but I am a good reader, I think...

                            Un saludo desde Espana
                            I did my part of reading, and now I 'patched' my first kernel.
                            It is all based on the PERL script made by phjanderson and the information on frequencies and voltages by giouncino.

                            It turns out MY sample of the M6Pro seems to work ONLY with higher memory speeds.
                            Any tweak on the CPU or GPU will cause freezes.
                            I was able to push my M6Pro to a memory clock of 760Mz, and it appears to run stable. (for now)

                            Here is the kernel I run at the moment, it gave me an AnTuTu score of 19100.
                            I don't have any info on battery usage yet.

                            Please some feedback when using this one.

                            Un saludo.
                            Attached Files

                            Comment

                              #59
                              Choice among normal and HD screen

                              In any case I would like to keep possibility of switch among screens.
                              Normal screen for some applications is enough and interface of HD screen still a bit laggy.

                              Is it possible to change smth (settings) in current ROM - 1.5 to have both options as it was before?

                              Comment

                                #60
                                Sleep of Death

                                Have anyone SoD on riley's 1.5 firmware, except me.
                                My stats: 5 SoD in 2 days

                                Comment

                                Previous 1 2 3 4 5 6 7 8 9 10 11 12 14 18 template Next

                                What's Going On

                                Collapse

                                There are currently 2312 users online. 0 members and 2312 guests.

                                Most users ever online was 63,956 at 18:56 on 20 March 2025.

                                Working...
                                X

                                We process personal data about users of our site, through the use of cookies and other technologies, to deliver our services, personalize advertising, and to analyze site activity. We may share certain information about our users with our advertising and analytics partners. For additional details, refer to our Privacy Policy.

                                By clicking "I AGREE" below, you agree to our Privacy Policy and our personal data processing and cookie practices as described therein. You also acknowledge that this forum may be hosted outside your country and you consent to the collection, storage, and processing of your data in the country where this forum is hosted.

                                I Agree