Suggest you isolate the issue into two piece. 1. Testing a normal serial
connection with emulator and make sure it can work. 2. Replace the host
interface with your /dev/ttyUSB0. You can refer to the below book for the
emulator internal.
The Android file system can be corrupted. However, in a properly
configured system, the bootloader, kernel, and system are read-only,
and thus, should never be corrupted. The writable system partitions
(data/ and cache/) are susceptible to corruption. But, usually,
devices can be booted into a
Rockchip never updated Android for the RK2808 beyond 1.6. The RK2808
is ARM9-based and slower in performance than the Qualcomm chip in the
G1, the 1st Android phone. I have Android 2.2 (Cyanogenmod) running
on a G1 and this is barely usable even with overclocking of the CPU.
So it's no surprise
From the different CTS releases, you can see that the releases are for
specific versions of the code. This failure means you are running a
CTS release meant for a later version of Android (like 2.3.3). You
need to try a previous CTS release like 2.3_r1.
On Jun 21, 11:46 am, James P
I'd like to get an official response to this as well as I'm having
the same problem. However, according the compatibility doc, when you
are missing hardware, you need to make whatever code changes to the
system code so that values returned by the API are correct according
to the SDK. In this
I would recommend getting the official test suites which you can get
at
http://source.android.com/compatibility/downloads.html
Unzip the file and you will get
android-cts/
docs/
repository/
tools/
You also need to have the Android SDK installed (get it from
The CDD doesn't restrict you in anyway. For example, look at the
Android 2.2 CDD
and compare against the tablets out now running on 2.2 (such as the
Nook Color).
In theory, you need to comply to the CDD and the pass CTS before
Google will
consider you for licensing of their apps. But that's
