What exactly is Quadrant?Support


Last Updated:

  1. poland626

    poland626 Well-Known Member This Topic's Starter

    Joined:
    May 23, 2010
    Messages:
    169
    Likes Received:
    13
    I got the app. I see when I was at 2.1 I got in the 500's but now with 2.2 I am getting 1,242, better than the droid x.

    BUT WHAT DOES IT MEAN?!

    It is seriously like a double rainbow to me. (in all joking aside, I really am wondering what this means)
     

    Advertisement
  2. sabrewings

    sabrewings Well-Known Member

    Joined:
    May 26, 2010
    Messages:
    895
    Likes Received:
    104
    It's a benchmark. It measures all different aspects of your device's performance. CPU processing power, I/O, 3D, 2D, etc. The big change for updating to 2.2 is the CPU's processing power with the new JIT compiler.
     
  3. poland626

    poland626 Well-Known Member This Topic's Starter

    Joined:
    May 23, 2010
    Messages:
    169
    Likes Received:
    13
    So through a digital update, they were able to more than double it's power?! Holy crap
     
  4. Berry2Droid

    Berry2Droid Well-Known Member

    Joined:
    Nov 17, 2009
    Messages:
    402
    Likes Received:
    45
    Just remember, with great power comes great responsibility.

    Have fun Peter
     
  5. Medion

    Medion Well-Known Member

    Joined:
    Aug 14, 2010
    Messages:
    1,855
    Likes Received:
    958
    Well, they didn't do anything to the physical power of the CPU. What happens is that programs have to go through several translation layers before they get to the hardware. As an example, you and I are talking, but you're speaking English, and I'm speaking French. To facilitate this, we try to get a translator. I found one that speaks French and Italian, while you've found one that speaks English and Spanish. So now we go find one that speaks Italian and Spanish, so we've using 3 translators as middle men, and hope to God that they don't lose anything in translation, or that will really slow us down.

    With 2.2, using the JIT compiler, Google simply sped up the communication between layers. In this case, we're both speaking English/French respectively, but this time, we got one translator who speaks both languages, so the process is faster, but still not natural.

    Hopefully 3.0 puts us on the same language, so we don't need translators (and that's an issue more with the development kit now than the OS, as the developers of Core Player can attest). So expect more speed gains with 3.0, just not as dramatic as 2.1 --> 2.2.
     
    Musky likes this.
  6. yojoe600

    yojoe600 Well-Known Member

    Joined:
    Apr 14, 2010
    Messages:
    2,188
    Likes Received:
    207
    you know thats not a bad way of putting it lol
     
  7. poland626

    poland626 Well-Known Member This Topic's Starter

    Joined:
    May 23, 2010
    Messages:
    169
    Likes Received:
    13
    That makes sense! Wow
     
  8. eddieb1983

    eddieb1983 Well-Known Member

    Joined:
    Aug 16, 2010
    Messages:
    48
    Likes Received:
    0
    So 3.0 is in the works? I wonder what they'll do next. They are already KILLING the iPhone!!!!!!
     
  9. Medion

    Medion Well-Known Member

    Joined:
    Aug 14, 2010
    Messages:
    1,855
    Likes Received:
    958
    3.0 is supposedly focused on the user experience, so mainly interface changes and hopefully some uniformity. Also, I'm hopeful that they will finally enable hardware acceleration for UI elements, to include scrolling, pinch to zoom, and accelerometer turns. It's farily quick now, but has two drawbacks. First, it's not as fluid as an iPhone or Zune HD. Second, when you do these actions, it makes the CPU usage soar for the duration. No really, get a long website (like Facebook), and just flick scroll up and down. You'll burn out the battery quick due to high CPU usage. Hardware acceleration not only makes this more fluid, but conserves battery life.

    Also, there's going to be native support for video calling for developers to hook into. I know, the EVO supports it right now, but that's using QIQ with some custom code. That means writing an app several times to make it compatible with multiple phones. By giving Android a native way to do it in 3.0, it means you can write once, and it should work on all 3.0 enabled phones.
     

Share This Page

Loading...