Someone can help me with this? I can't find anything online.
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
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
try doing ./adb devices and see what the output shows. Remove everything
listed and type, ./adb connect IP-address:. If this works, you can check
out other adb commands
--
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting
On Apr 28, 10:46 am, Diego Rondini wrote:
> To make it work I had to force the send boolean variable to true after
> "preprocessEvent" in KeyInputQueue.java. I was getting true only for the SYN
> event...
>
> Now I'm investigating why I get false from preprocessEvent for every ABS
> event, but is
Hi all!
I've ported Android 2.3.3 to my Freescale iMX-based board, and for
some reason I cannot change the date or time. (This problem occurred
on IMX's R10 and R10.1 releases.)
Changing the value in settings has no effect. Moreover, the time in
the top-right notification area does not refresh
Attempting to change the date from the shell reveals a little more
information:
$ adb shell date $(date +%s)
time 1303997425 -> 1303997425.0
settimeofday failed Bad file number
$
I'm trying to find information on the settimeofday failed error, but
so far no luck.
On Apr 28, 8:54 am, Jim D wrote
On Apr 28, 12:59 pm, Diego wrote:
> Uncommenting some log messages in preprocessEvent in
> WindowManagerService.java I found out that the culprit was this line:
>
> boolean screenIsOff = !mPowerManager.isScreenOn();
>
> screenIsOff is true (yes, mPowerManager.isScreenOn() returns false
> even if m
Diego,
This is something I need to track down as well..but for now, you can
set "setprop hw.nopm true" in your init.rc file and that will get your
touch events and keypresses working..
-- Ashwin
On Thu, Apr 28, 2011 at 10:12 AM, Diego wrote:
> On Apr 28, 12:59 pm, Diego wrote:
>> Uncommentin
Hi all ,
i am able to boot android froyo on DM368 board from NAND flash ,but
its very slow .I am ignoring the first time booting time .Its taking
15 min approximately to boot from the next time onwards.
i am using initramfs as android rootfs filessytem. the android kernel
boots and mounts the sys
On Apr 28, 8:58 am, Mali Laurent wrote:
> They have removed it as the information was old. They are working on an up
> to date version and will be back online soon.
>
While I found it odd to remove old but not totally outdated
informations before publishing the new version, people can find a copy
Hi,
Building Android 2.3.3 for first time for Nexus one is giving
following error
system/media/opensles/tests/automated/BufferQueue_test.cpp:34:29:
error: SLES/OpenSLESUT.h: No such file or directory
Has anyone faced similliar error ?
Regards,
Pradeep
--
unsubscribe: android-porting+unsubscr.
It will be pretty hard. You have to get the internal info of that device
(CPU, NAND type and size, etc) and create a total workaround for that.
Also, interfaces of GPS, etc.
If the CPU isn't ARMv6 or v7, it is possible to do but most apps won't work.
--
unsubscribe: android-porting+unsubscr...@
12 matches
Mail list logo
