Hello everybody,
I'm trying to build an application to connect and Android phone via Bluetooth
through an RFCOMM serial channel.
Unfortunately I'm hitting a really nasty bug which make development
impossibile.
I tried starting with the examples provided that explain how to open an RFCOMM
conn
Hi,
I'm porting Android 1.6 Donut to a Freescale i.MX233 EVK board and I'm having a
problem when recording audio. Let me introduce my problem.
What works:
- playing audio with alsa_aplay;
- recording audio with alsa_aplay -C;
- playing audio inside Android (e.g. with Music player).
What doesn't
Hello,
I'm porting Android on a platform that doesn't support suspend-to-ram (echo
mem >/sys/power/state) but just standby (echo standby >/sys/power/state). I
ended up hacking my kernel so that every call to suspend-to-ram becomes a
standby request, but I'm wondering how the thing is managed on
Hello!
I've built my own Android distribution, but I'm not able to figure out how
devices (with respect to adb) are named.
My device is always "emulator-5554", no matter what I put in
/system/build.prop in "ro.product.device=" (tried also the other values, but
no luck).
$ adb devices
List of
Hello everybody!
I've grabbed the following patch for tslib integration:
http://gitorious.org/0xdroid/frameworks_base/commit/851dde5d74893b3a6e9b9bda43b8bd936f4a7e5d
and integrated it successfully in a Froyo build.
To make it work I had to force the send boolean variable to true after
"preproce
Il giorno mercoledì 16 marzo 2011 03:49:35 Hamilton Vera ha scritto:
> Hi Diego, maybe you can find more reference/code about that in LTIB.
>
> You can download LTIB for imx28 at freescale.com
>
Thanks you for the hint, but it's not what I need.
We found out that declaring «struct tsdev *mTS;»
#include "tslib-private.h"» and the
pointer declaration «struct tsdev *mTS;» in EventHub.h makes Android fail to
launch SurfaceFlinger most of the times.
Does anybody know what could be causing the problem? Could we be missing
something (we've noticed we're missin
