Courtesy of KonstaKANG

  • @aluminium
    link
    English
    21 year ago

    Yeah, Android when it comes to “smoothness” is an enigma to me. For games it makes sense since the GPU is weak. But for browsing and stuff it should be plenty fast.

    You could also try to AOT compile apps with these adb commands to maybe get better performance:

    adb shell pm compile -a -f --check-prof false -m everything

    adb shell pm compile -a -f --check-prof false --compile-layouts

    adb shell pm bg-dexopt-job

    • @furyOP
      link
      English
      11 year ago

      The first and third commands made things load up a bit quicker. Thanks! Second command seems to have been removed. I wish I could figure out what’s limiting the system to 30 fps on this display…it OUGHT to be able to handle 60 fps at this resolution

    • @[email protected]M
      link
      fedilink
      English
      11 year ago

      adb shell pm compile -a -f --check-prof false -m everything

      adb shell pm compile -a -f --check-prof false --compile-layouts

      adb shell pm bg-dexopt-job

      What do these commands do? From 1st to last.

      • @aluminium
        link
        English
        11 year ago

        in short : Android apps contain dex bytecode, which through these commands get compiled into native machine code.

        • @[email protected]M
          link
          fedilink
          English
          11 year ago

          I know that. I was just asking what the actual adb commands do like the compile-layouts parameter, the last bgdexopt job. Why are all 3 necessary. Samsung has a galaxy app booster that appears to do something similar.

          • @aluminium
            link
            English
            21 year ago

            Ah, unfortunately I don’t know it either. I always saw these 3 mentioned when talking about the topic. My guess with the --compile-layouts flag would be that it maybe precalculates layout xml files to your exact screen size and resolution.