Has anyone android working with andy-tracking?

Andy Green andy at openmoko.com
Sat Feb 7 20:56:33 CET 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Somebody in the thread at some point said:
| Hi,
|
| Radek Polak wrote:
|> Hi,
|> with current andy-tracking i am unable to get android working.
|>
|> I have problem with broken display, touchscreen does not work
|> and keys dont work too.
| I'm very surprising, maybe the problem is my bad english. I follow the
| kernel update,
| and I have a running android version each time. I try to having a stable
| android platform,

Yes I see other people are running fine with it too.

| and personally I give the possibily to use the android with a lot of
| feature, but there is
| no open discussion on this. The uImage-v11.bin and uImage-v11-strip.bin
| and uImage-v10 are
| based on the latest kernel with a revert of one commit on display
| (pan_problem) and a keyboard
| patch. I send a lot of patches to rebase the current freerunner-android
| git of koolu over the new kernel.
| The new android framework on the kernel is readable.
| I think that can be done a lot of improvement, in different direction. I
| send email for an open discussion
| about wake lock, but I start to think that nothing know what is a wake
| lock.

Well we enabled the wake locks on our config to start with, but it
causes resume to go straight back to suspend on non-Android rootfs.
You're right, I don't know where the wake lock code came from or what it
really is for either, so we disabled it in config to work around it.

- -Andy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iEYEARECAAYFAkmN53EACgkQOjLpvpq7dMpe0wCeNRW4e/uTQUGBcZxWKF+on/B6
IZsAn3Z2piTvUJM23zvGutS5Zn/7ipH1
=99br
-----END PGP SIGNATURE-----



More information about the openmoko-kernel mailing list