[android-porting] errors while compiling android ginger bread

2011-04-26 Thread dev
linux for compiling Gingerbread. Regards, dev -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

[android-porting] UBUNTU linux 64-bit

2011-04-27 Thread dev
? Thanks & Regards, dev -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting

[android-porting] RTC_WAKEUP

2009-09-14 Thread /dev/null
I thought that the intention for the RTC_WAKEUP alarm was to wake up a sleeping or powered off device. I was a bit surprised to find out that it was not only the Alarm Clock application that registered RTC_WAKEUP alarms, but also the Calendar does this to drive its synchronization. I assume the GM

[android-porting] Re: RTC_WAKEUP

2009-09-15 Thread /dev/null
leep (that is when no wake > > locks are held), not to turn it on when it is off. > > > If you want to allow the device to turn on while off, a new kind of wakeup > > alarm will need to be defined.  This is not currently feature that is > > supported by the platform. > &

[android-porting] "The 0x18d1 vendor id belongs to Google"

2010-01-09 Thread /dev/null
This may be somewhat off-topic but in this message http://groups.google.com/group/android-porting/msg/a04c96a77f1a2e81 posted in this forum it is claimed that the USB vendor id 0x18d1 belongs to Google. I have no problem with that, but after taking a look at the current official list of vendor IDs

[android-porting] Re: "The 0x18d1 vendor id belongs to Google"

2010-01-11 Thread /dev/null
-id list there. Then at least the Nexus One will show up as a Google device when you run "lsusb" on a future release of a Linux distribution. On 9 Jan, 11:49, "/dev/null" wrote: > This may be somewhat off-topic but in this > messagehttp://groups.google.com