Register Hello & Welcome to AndroidTablets.net, is this your first visit?

Results 1 to 8 of 8
  1. #1
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777

    Is your device fully Google Android Compatible?

    You can test if your device is fully "Google Android Compatible" by checking if it passes Google's Compatibility Test Suite (CTS):

    http://source.android.com/compatibility/downloads.html

    Caveat: You might need some Android development experience to run the CTS.
    Most manufacturers would have already run it, and maybe not publish the complete results for dubious reasons.
    If your device came pre-installed with Google Play, chances are that it passes Google's CTS.

    Now that I know this, I (personally) will never buy a tablet that fails the CTS. And I don't think I should have to hack a device to make it CTS-compatible; that is the device manufacturer's job.

    Posting this here for your information.
    Last edited by Natey2; 06-25-2012 at 07:39 AM.

  2. # ADS
    Ads
    Circuit advertisement
    Join Date
    Always
    Location
    Advertising world
    Posts
    Many

  3. #2
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777
    Google has a nice chart on how to run the tests and collect the results: http://source.android.com/compatibility/cts-intro.html

  4. #3
    Developer
    Points: 24,375, Level: 95
    Level completed: 3%, Points required for next Level: 975
    Overall activity: 41.0%
    Achievements:
    Recommendation Second Class 10,000 Experience Points 5,000 Experience Points 1 year registered 1,000 Experience Points

    Member #
    61306
    Join Date
    Nov 2011
    Location
    Huntington WV
    Posts
    3,709
    Thanked
    1386 times
    Points
    24,375
    Level
    95
    Device
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    I have read over these tests, as a user I have no need for it, perhaps a company or an app creator could use it. The best test for a user is to setup their build.prop to allow the best access then search and install the apps they want from play store.

  5. #4
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777
    I think the tests will predict if you will have problems with hdmi/video, etc routines using somebody's port of Android to your device.
    Is it no wonder that so many people have problems with unofficial ICS builds running on their devices?

    JUnit tests are standard things software developers run when building a product to ensure things that once worked continue to work when changes are made.

    It is great that Google has made this publicly available, so be especially cautious of "ICS" versions out there that fail these tests.

  6. #5
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777
    YES!!! I finally got it installed and working!

    I am using v2.3 of the CTS to test the Android 2.3.4 variant running on my Motorola DroidX.
    I will do the ICS test against my generic ICS 4.0.3 tablet later.
    (The Android 4.0 CTS r2 release contains approximately 17,000 tests that you can execute on your device)

    My sample sesion:

    $ bash
    /android-cts/tools[2]$ ./startcts
    java -Xmx512M -cp c;C:\android-cts\tools\cts.jar;c;C:\android-cts\tools\ddmlib-prebuilt.jar;c;C:\android-cts\tools\junit.jar;c;C:\android-cts\tools\hosttestlib.jar com.android.cts.TestHost C:\android-cts\repository\host_config.xml
    Android CTS version 2.3_r13
    Device(XXXXXXXXXXXXXXXX) connected
    cts_host > cts_host > help
    Usage: command options
    Avaiable commands and options:
    Host:
    help: show this message
    exit: exit cts command line
    Plan:
    ls --plan: list available plans
    ls --plan plan_name: list contents of the plan with specified name
    add --plan plan_name: add a new plan with specified name
    add --derivedplan plan_name -s/--session session_id -r/--result result_type: derive a plan from the given session
    rm --plan plan_name/all: remove a plan or all plans from repository
    start --plan test_plan_name: run a test plan
    start --plan test_plan_name -d/--device device_ID: run a test plan using the specified device
    start --plan test_plan_name -t/--test test_name: run a specific test
    start --plan test_plan_name -p/--package java_package_name: run a specific java package
    start --plan test_plan_name -t/--test test_name -d/--device device_ID: run a specific test using the specified device
    start --plan test_plan_name -p/--package java_package_name -d/--device device_ID: run a specific java package using the specified device
    Package:
    ls -p/--package: list available packages
    ls -p/--package package_name: list contents of the package with specified name
    add -p/--package root: add packages from root to repository
    rm -p/--package package_name/all: remove a package or all packages from repository
    Result:
    ls -r/--result: list all result of sessions
    ls -r/--result -s/--session session_id: list detail case result of a specified session
    ls -r/--result [pass/fail/notExecuted/timeout] -s/--session session_id: list detail cases of a specified session by the specified result.
    History:
    history/h: list all commands in command history
    history/h count: list the latest count records in command history
    history/h -e num: run the command designated by 'num' in command history
    Device:
    ls -d/--device: list available devices
    cts_host > ls --plan
    List of plans (7 in total):
    Android
    AppSecurity
    CTS
    Java
    RefApp
    Signature
    VM

    Running a specific test:

    cts_host > start --plan CTS -t android.text.cts.ClipboardManagerTest#testAccessTe xt
    start test android.text.cts.ClipboardManagerTest#testAccessTe xt
    ================================================== ============
    Test package: android.text
    android.text.cts.ClipboardManagerTest#testAccessTe xt...(pass)
    ================================================== ============
    Time: 65.454s

    Many more packages with tests available:

    cts_host > ls -p
    Available packages (44 in total):
    android.openglperf
    android.accessibilityservice
    android.core.vm-tests
    android.core.tests.luni.io
    android.database
    android.util
    android.location
    android.admin
    android.example
    android.permission2
    android.core.tests.luni.lang
    android.jni
    android.provider
    android.app
    android.accounts
    android.gesture
    android.webkit
    android.security
    android.core.tests.luni.util
    android.core.tests.luni.net
    android.view
    android.hardware
    android.widget
    android.tests.sigtest
    android.text
    android.sax
    android.bluetooth
    android.dpi
    android.tests.appsecurity
    android.dpi2
    android.core.tests.xml
    android.net
    android.ndef
    android.media
    android.core.tests.dom
    android.speech
    android.permission
    android.os
    android.mediastress
    android.telephony
    android.apidemos.cts
    android.content
    android.preference
    android.graphics
    cts_host >


    Sent from my unrooted DroidX using Tapatalk

  7. #6
    Developer
    Points: 24,375, Level: 95
    Level completed: 3%, Points required for next Level: 975
    Overall activity: 41.0%
    Achievements:
    Recommendation Second Class 10,000 Experience Points 5,000 Experience Points 1 year registered 1,000 Experience Points

    Member #
    61306
    Join Date
    Nov 2011
    Location
    Huntington WV
    Posts
    3,709
    Thanked
    1386 times
    Points
    24,375
    Level
    95
    Device
    Leagoo Lead 1 ZTE OPEN C, Coby 7065, Coby 8042, Coby 9740
    ok and what did any of that prove? I know you like this tests but I don't think you understand it. you need two tablets to really understand it, one tablet must fail while the other passes this test, then you go to the market and try to install the same apps on both, unless you find apps that only work on the tablet that the test says passed the test it's self is unimportant.

  8. #7
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777
    Quote Originally Posted by vampirefo. View Post
    ok and what did any of that prove? I know you like this tests but I don't think you understand it. you need two tablets to really understand it, one tablet must fail while the other passes this test, then you go to the market and try to install the same apps on both, unless you find apps that only work on the tablet that the test says passed the test it's self is unimportant.
    These tests are not dependent on Market apps. The purpose of the JUnit tests is to see if something fundamental has deviated from the way Google expects it to work.

    The single sample test I ran above indicates my DroidX passes the test Google designed to verify accessing text from the Clipboard (via their standard API). If a manufacturer had hacked the OS and broken this part of the system, this test would have failed.

    It'll take a while to run all of the tests, but it'll provide information about which part of the system deviated from Google's standard.
    Google should prevent manufacturers from using names like "Ice Cream Sandwich", "Honeycomb", "Gingerbread", etc. if too many of these tests fail on a particular manufacturers device.
    And some manufacturers' tablets will pass more of these tests than others. That's the manufacturer's tablet I want to buy.
    If these test results were published publicly, it'll make the purchasing decision much easier.
    Last edited by Natey2; 07-07-2012 at 02:54 PM.

  9. #8
    Senior Member
    Points: 16,591, Level: 82
    Level completed: 49%, Points required for next Level: 259
    Overall activity: 0%
    Achievements:
    10,000 Experience Points 1 year registered 5,000 Experience Points 3 months registered 1,000 Experience Points

    Member #
    117131
    Join Date
    May 2012
    Location
    California
    Posts
    477
    Thanked
    43 times
    Points
    16,591
    Level
    82
    Device
    Nexus 7, iDeaUSA CT702/YG A777
    I got Google's CTS installed and working under linux to test my Android 4.0.3 tablet (iDeaUSA CT702 / YG A777).
    Is your Media not working properly after an "upgrade" from some strange source?
    Mine works fine. Sample session to test media routines on my YG A777:

    $ ./cts-tradefed
    Android CTS 4.0.3_r3
    cts-tf > 07-10 14:17:03 I/DeviceManager: Detected new device 0123456789ABCDEF
    cts-tf > help
    CTS-tradefed host version 4.0.3_r3

    CTS-tradefed is the test harness for running the Android Compatibility Suite, built on top of the tradefed framework.

    Available commands and options
    Host:
    help: show this message
    help all: show the complete tradefed help
    exit: gracefully exit the cts console, waiting till all invocations are complete
    Run:
    run cts --plan test_plan_name: run a test plan
    run cts --package/-p : run a CTS test package
    run cts --class/-c [--method/-m] : run a specific test class and/ormethod
    run cts --continue-session session_ID: run all not executed tests from a previous CTS session
    run cts [options] --serial/s device_ID: run CTS on specified device
    run cts [options] --shards number_of_shards: shard a CTS run into given number of independent chunks, to run on multiple devices inparallel
    run cts --help/--help-all: get more help on running CTS
    List:
    l/list d/devices: list connected devices and their state
    l/list packages: list CTS test packages
    l/list p/plans: list CTS test plans
    l/list i/invocations: list invocations aka CTS test runs currentlyin progress
    l/list c/commands: list commands: aka CTS test run commands currently in the queue waiting to be allocated devices
    l/list r/results: list CTS results currently present in the repository
    Add:
    add derivedplan --plan plane_name --session/-s session_id -r [pass/fail/notExecuted/timeout]: derive a plan from the given session
    Dump:
    d/dump l/logs: dump the tradefed logs for all running invocations

    cts-tf > list devices
    Serial State Product Variant Build Battery
    0123456789ABCDEF Available m805_892x m805_892x A777 76
    cts-tf > list plans
    RefApp
    CTS
    Signature
    CTS-TF
    VM-TF
    Java
    AppSecurity
    Android
    cts-tf > list packages
    android.acceleration
    android.accessibilityservice
    android.accounts
    android.admin
    android.animation
    android.apidemos.cts
    android.app
    android.bluetooth
    android.content
    android.core.tests.libcore.package.com
    android.core.tests.libcore.package.dalvik
    android.core.tests.libcore.package.libcore
    android.core.tests.libcore.package.org
    android.core.tests.libcore.package.sun
    android.core.tests.libcore.package.tests
    android.core.vm-tests
    android.core.vm-tests-tf
    android.database
    android.dpi
    android.dpi2
    android.drm
    android.example
    android.gesture
    android.graphics
    android.graphics2
    android.hardware
    android.holo
    android.jni
    android.location
    android.media
    android.mediastress
    android.nativemedia
    android.ndef
    android.net
    android.openglperf
    android.os
    android.permission
    android.permission2
    android.preference
    android.preference2
    android.provider
    android.renderscript
    android.sax
    android.security
    android.speech
    android.telephony
    android.tests.appsecurity
    android.tests.sigtest
    android.text
    android.textureview
    android.util
    android.view
    android.webkit
    android.widget

    cts-tf > run cts -p android.nativemedia
    07-10 14:30:14 I/TestInvocation: Starting invocation for 'cts' on build '4.0.3_r3' on device 0123456789ABCDEF
    07-10 14:30:14 I/0123456789ABCDEF: Created result dir 2012.07.10_14.30.14
    cts-tf > 07-10 14:30:45 I/0123456789ABCDEF: Collecting device info
    07-10 14:30:47 I/0123456789ABCDEF: -----------------------------------------
    07-10 14:30:47 I/0123456789ABCDEF: Test package android.nativemedia started
    07-10 14:30:47 I/0123456789ABCDEF: -----------------------------------------
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testEngin eCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testOutpu tMixCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromUriCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromFdCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromPcmBqCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromTsAbqCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromUriToPcmBqCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromFdToPcmBqCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia.SLObjectCreationTest#testAudio PlayerFromAdtsAbqToPcmBqCreation PASS
    07-10 14:30:48 I/0123456789ABCDEF: Saved log device_logcat_9118328628809773285.zip
    07-10 14:30:48 I/0123456789ABCDEF: Saved log host_log_1640505787766876170.zip
    07-10 14:30:48 I/0123456789ABCDEF: android.nativemedia package complete: Passed 9, Failed 0, Not Executed 0
    07-10 14:30:48 I/0123456789ABCDEF: Created xml report file at file:///usr/local/work/android_work/CTS403/android-cts/tools/./../../android-cts/repository/results/2012.07.10_14.30.14/testResult.xml
    07-10 14:30:48 I/0123456789ABCDEF: XML test result file generated at 2012.07.10_14.30.14. Passed 9, Failed 0, Not Executed 0
    07-10 14:30:48 I/0123456789ABCDEF: Time: 33s

    cts-tf > run cts -p android.mediastress
    07-10 15:19:46 I/TestInvocation: Starting invocation for 'cts' on build '4.0.3_r3' on device 0123456789ABCDEF
    07-10 15:19:46 I/0123456789ABCDEF: Created result dir 2012.07.10_15.19.46
    cts-tf > 07-10 15:20:29 I/0123456789ABCDEF: Collecting device info
    07-10 15:20:33 I/0123456789ABCDEF: -----------------------------------------
    07-10 15:20:33 I/0123456789ABCDEF: Test package android.mediastress started
    07-10 15:20:33 I/0123456789ABCDEF: -----------------------------------------
    07-10 15:30:46 I/0123456789ABCDEF: android.mediastress.cts.H263QcifLongPlayerTest#tes tPlay00 PASS
    07-10 15:31:08 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay00 PASS
    07-10 15:31:31 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay01 PASS
    07-10 15:31:53 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay02 PASS
    07-10 15:32:16 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay03 PASS
    07-10 15:32:38 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay04 PASS
    07-10 15:33:01 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay05 PASS
    07-10 15:33:23 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay06 PASS
    07-10 15:33:45 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay07 PASS
    07-10 15:34:08 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay08 PASS
    07-10 15:34:30 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay09 PASS
    07-10 15:34:52 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay10 PASS
    07-10 15:35:15 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay11 PASS
    07-10 15:35:37 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay12 PASS
    07-10 15:35:59 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay13 PASS
    07-10 15:36:22 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay14 PASS
    07-10 15:36:44 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay15 PASS
    07-10 15:37:06 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay16 PASS
    07-10 15:37:28 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay17 PASS
    07-10 15:37:51 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay18 PASS
    07-10 15:38:13 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay19 PASS
    07-10 15:38:35 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay20 PASS
    07-10 15:38:57 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay21 PASS
    07-10 15:39:20 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay22 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H263QcifShortPlayerTest#te stPlay23 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R1080pAacLongPlayerTes t#testPlay00 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R1080pAacShortPlayerTe st#testPlay00 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R1080pAacShortPlayerTe st#testPlay01 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R1080pAacShortPlayerTe st#testPlay02 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacLongPlayerTest #testPlay00 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay00 PASS
    07-10 15:39:42 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay01 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay02 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay03 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay04 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay05 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay06 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay07 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay08 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay09 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay10 PASS
    07-10 15:39:43 I/0123456789ABCDEF: android.mediastress.cts.H264R480pAacShortPlayerTes t#testPlay11 PASS
    07-10 15:40:05 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay00 PASS
    07-10 15:40:27 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay01 PASS
    07-10 15:40:50 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay02 PASS
    07-10 15:41:12 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay03 PASS
    07-10 15:41:34 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay04 PASS
    07-10 15:41:56 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay05 PASS
    07-10 15:42:19 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay06 PASS
    07-10 15:42:41 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay07 PASS
    07-10 15:43:03 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay08 PASS
    07-10 15:43:25 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay09 PASS
    07-10 15:43:48 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay10 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R480x360AacShortPlayer Test#testPlay11 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacLongPlayerTest #testPlay00 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacLongPlayerTest #testPlay01 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay00 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay01 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay02 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay03 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay04 PASS
    07-10 15:44:10 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay05 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay06 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay07 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay08 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay09 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay10 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay11 PASS
    07-10 15:44:11 I/0123456789ABCDEF: android.mediastress.cts.H264R720pAacShortPlayerTes t#testPlay12 PASS
    07-10 15:48:22 I/0123456789ABCDEF: android.mediastress.cts.MediaRecorderStressTest#te stStressCamera PASS
    07-10 15:54:25 I/0123456789ABCDEF: android.mediastress.cts.MediaRecorderStressTest#te stStressCameraSwitchRecorder PASS
    07-10 15:59:39 I/0123456789ABCDEF: android.mediastress.cts.MediaRecorderStressTest#te stStressRecordVideoAndPlayback PASS
    07-10 16:03:51 I/0123456789ABCDEF: android.mediastress.cts.MediaRecorderStressTest#te stStressRecorder PASS
    07-10 16:13:57 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360LongPlayerTest# testPlay00 PASS
    07-10 16:14:20 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay00 PASS
    07-10 16:14:43 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay01 PASS
    07-10 16:15:05 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay02 PASS
    07-10 16:15:28 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay03 PASS
    07-10 16:15:51 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay04 PASS
    07-10 16:16:13 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay05 PASS
    07-10 16:16:36 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay06 PASS
    07-10 16:16:59 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay07 PASS
    07-10 16:17:22 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay08 PASS
    07-10 16:17:44 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay09 PASS
    07-10 16:18:07 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay10 PASS
    07-10 16:18:29 I/0123456789ABCDEF: android.mediastress.cts.Vp8R480x360ShortPlayerTest #testPlay11 PASS
    07-10 16:18:45 I/0123456789ABCDEF: Saved log device_logcat_5895987144373648159.zip
    07-10 16:18:45 I/0123456789ABCDEF: Saved log host_log_913050346659382334.zip
    07-10 16:18:45 I/0123456789ABCDEF: android.mediastress package complete: Passed 86, Failed 0, Not Executed 0
    07-10 16:18:45 I/0123456789ABCDEF: Created xml report file at file:///usr/local/work/android_work/CTS403/android-cts/tools/./../../android-cts/repository/results/2012.07.10_15.19.46/testResult.xml
    07-10 16:18:45 I/0123456789ABCDEF: XML test result file generated at 2012.07.10_15.19.46. Passed 86, Failed 0, Not Executed 0
    07-10 16:18:45 I/0123456789ABCDEF: Time: 58m 58s

    cts-tf > list results
    Session Pass Fail Not Executed Start time Plan name Device serial(s)
    0 9 0 0 2012.07.10_14.30.14 NA unknown
    1 86 0 0 2012.07.10_15.19.46 NA unknown

    cts-tf > exit
    Signalling command scheduler for shutdown.
    TF will exit without warning when remaining invocations complete.
    cts-tf > 07-10 16:34:46 I/CommandScheduler: All done
    Saved log to /tmp/tradefed_global_log_2151627119574242570.txt


    Sent from my unrooted DroidX using Tapatalk


 

Ads:

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Similar Threads

  1. Application not compatible with device
    By 5star in forum Android Tablet Apps
    Replies: 4
    Last Post: 03-28-2012, 04:39 AM
  2. This app is not compatible with your device??? G tab help
    By mgr52 in forum Viewsonic gTablet
    Replies: 6
    Last Post: 12-15-2011, 08:22 AM
  3. Can't install AppBrain - device is not compatible...
    By Zhopa in forum Nook Color Technical
    Replies: 3
    Last Post: 12-05-2011, 07:41 AM

Search tags for this page

android cts 4.1 testing
,
android cts run historical session
,
android cts tablets wiki
,
android cts test case example
,
android+cts telephony
,

android.mediastress.cts.h263qciflongplayertest

,
compatibility+test+package: android.textureview
,
h263qcifshortplayertest
,
ho wto test cts mediastress
,
nexus 7 cts result
,

tf will exit without warning when remaining invocations complete

,

your device is not compatible with this version

Click on a term to search our sites for related topics.
Powered by vBulletin® Version 4.1.11
Copyright © 2014 vBulletin Solutions, Inc. All rights reserved.
Android Tablets.net is not affiliated or associated with Google, Android Project or any of the device manufacturers listed on this site.
We are simply an enthusiast site.
All times are GMT -5. The time now is 04:52 AM.