Announcement

Collapse
No announcement yet.

Announcement

Collapse
No announcement yet.

PiPo UpU1 ROM Speed Test Comparison

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

    PiPo UpU1 ROM Speed Test Comparison

    I just got another PiPo UpU1 (for my sister) and thought it would be interesting to run Speedtest.net to compare the current PiPo factory unit against my RileyROM unit. Both tablets have Kernel 308+ and both units are Build 4.1.1-20121031. Both units were tested through the same server WIFI connection, using the same wireless network.

    PiPo UpU1-1 (Factory ROM)
    Average of three test runs: Download = 2450kbps Upload = 829kbps Ping = 42ms

    PiPo UpU1-2 (Riley ROM)
    Average of three test runs: Download = 1028kbps Upload = 834kbps Ping = 44ms

    As you can see, the Factory ROM unit is much faster in the download test.

    Any ideas as to why such a big difference?

    #2
    PiPo UpU1 ROM Speed Test Comparison

    I don't know. I kept the same factory settings for wifi. They haven't updated the firmware since January.

    It would be cool to have a ROM dump of that stock version to see if they have updated something, and never posted it.


    Randy
    Randy
    Freaktab Developer, Product Reviewer, Moderator and "Flashaholic".
    Read my BIO Here
    Be sure to donate to support Freaktab.com. If any of my development work makes a positive difference for you, please make a donation to support future RileyROM's.
    Donate here

    Comment


      #3
      Being a semi-retired database software developer; I have now developed this new interest in the Android world. I am learning quickly, but I am not yet fully versed in droid terminology.

      Is a "Rom Dump" something I could provide you from the new PiPo UpU1 I received this last week? Or, from archived Firmware .img files that I have been keeping on my PC.

      I am happy to assist.

      Comment


        #4
        I'm at work, so I don't have time to look for it, but there is a thread here on Freaktab...somewhere...that takes you through dumping the ROM that is installed on the device. We use this technique to make ROM's for people who don't have access to the original firmware, or the factory web page doesn't have the firmware posted.

        In this case, I'm wondering if Pipo has done a firmware update for their more recent runs...and just forgot or failed to post the update on the web site. I find that from time to time with Pipo. I have had to resort to doing ROMs from firmware that was sort of back doored from someone. It isn't the best scenario, and I really don't like to do it.

        So I try to either use official factory firmware, or the next best thing, a dump of a ROM that is very recently shipped from the factory. With a ROM dump, I can compare dates on files and see if they've made changes. If there is that much improvement, I would love to release a new ROM. The files I need are:

        kernel.img
        misc.img
        boot.img
        recovery.img
        system.img (which is the largest file)
        parameter

        Most of the changes will occur in the kernel or the system images. While I can change everything in the system.img...the kernel is binary and must be edited with a hex editor...or compiled from the original sources...which Pipo doesn't release.
        Randy
        Freaktab Developer, Product Reviewer, Moderator and "Flashaholic".
        Read my BIO Here
        Be sure to donate to support Freaktab.com. If any of my development work makes a positive difference for you, please make a donation to support future RileyROM's.
        Donate here

        Comment


          #5
          Is this the thread you were recommending, http://www.freaktab.com/showthread.p...ht=dumping+rom

          If so, I will try and get the PiPo U1 image files for you.

          Geoffery

          Comment


            #6
            PiPo UpU1 ROM Speed Test Comparison

            Yes. That's it.

            Thanks.


            Randy
            Randy
            Freaktab Developer, Product Reviewer, Moderator and "Flashaholic".
            Read my BIO Here
            Be sure to donate to support Freaktab.com. If any of my development work makes a positive difference for you, please make a donation to support future RileyROM's.
            Donate here

            Comment


              #7
              Originally posted by rrileypm View Post
              Yes. That's it.

              Thanks.


              Randy
              Better yet, I have the current complete factory update img (update_DS778_PIPO_U1_20121031-Support PIP Zoom.img), but it is to large (459.37MB) for me to upload. As .zip it is 302MB. Do you have ftp for uploading? It appears to be the same as the build of the new PiPo U1 I just got.

              Kernel version: 3.0.8+
              Build number: RK30_ANDROID4.1.1-SDK-v1.00.00 WXGA-eng 4.1.1 JR003H 20121031.175301 release-keys


              GeofferyH

              Comment


                #8
                Pipo U1 Pro

                Just checked and my tabby has build RK_30 android 4.1.1 -SDK-V1.00.00 and I just wondered if it was the latest as starting to lag a little lately. cheers

                Comment


                  #9
                  Originally posted by John Dough View Post
                  Just checked and my tabby has build RK_30 android 4.1.1 -SDK-V1.00.00 and I just wondered if it was the latest as starting to lag a little lately. cheers
                  The remaining portion of the build number is what is most important to determine the ROM installed.

                  It looks something like this: 2012xxxx-xxxxxx

                  Comment


                    #10
                    Re build

                    Subject: RE: Reply to thread 'PiPo UpU1 ROM Speed Test Comparison'

                    No more numbers after or before build but kernel is dated Nov 8 2012.
                    Cheers
                    For info: Speedtest : wi-fi 18147kbps down 8147upload from Manx server.
                    Last edited by John Dough; 20 September 2013, 15:25.

                    Comment

                    Working...
                    X