On Sat, Aug 21, 2010 at 12:48 AM, mot12 <[email protected]> wrote:
> - why does the log not show the alarm intent being FIRED? > The stock platform does not log anything when an alarm is broadcast. > - why does the stock alarm suffer from the same problem? > I know that early releases of Android had some problems with the alarm clock due to user space not doing the right things with wake locks... but this is not an issue I am aware of in the current platform, specifically on Droid. > Here's an example one of my users sent me: > The alarm is set for 08:45. > The user stopped using the device at 02:15. > There are some log entries until 02:54, then NOTHING until 11:46 when > the screen is turned on. > The log entry of the alarm intent being received happens at > 11:46:45.319. This is is the first line in my OnReceive. > What are these things in the log? 03-03 02:32:48.530 I/usbd ( 1078): process_usb_uevent_message(): buffer = change@/devices/platform/wl127x-rfkill.0/rfkill/rfkill0 03-03 02:32:48.530 I/usbd ( 1078): main(): call select(...) That is not something printed by the stock platform, certainly not on Droid running 2.2 (I just checked). If these people are using a Droid (I don't recall at this point who said their users were running what), then I would start to suspect that they have installed a custom build that is broken. If this is some other device that isn't running stock Android, they would perhaps be better off reporting the bug to the hardware manufacturer since it appears to be a bug in the device (and impacts features built in to the device). Also I don't know if this is your app, but somebody is using the old Service.setForeground() API that no longer does anything and they thus could get killed: 03-03 02:33:57.647 W/Service ( 2404): setForeground: ignoring old API call on com.wsandroid.Core.BaseService Anyway, at this point someone needs to show this problem happening on the stock platform. If it is not a bug in the stock platform, there is not much I can do to help. And honestly, if your users have a device where the alarm clock built into it doesn't work... and your alarm clock app doesn't work in the same way... how can they expect yours to work any better? It is an issue with their device. -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
