I am having similar issues with Droid. G1 and Emulator seem to work
fine.
Is this related?
http://community.developer.motorola.com/t5/Android-App-Development-for/AlarmManager-ELAPSED-REALTIME-WAKEUP-amp-RTC-WAKEUP-won-t-wake/td-p/4987
On Apr 29, 12:17 pm, nikhil wrote:
> Just to update this topi
Just to update this topic, it seems that even HTC Hero is facing the
same issue.
Does anyone know if there are any plans to provide push notifications?
On Mar 22, 2:46 pm, Derek wrote:
> Mark,
>
> It doesn't seem to consume battery. I've tried several solutions and
> only yours is really working
Mark,
It doesn't seem to consume battery. I've tried several solutions and
only yours is really working.
Before I used a regular service with a AlarmManager.set(...) to
schedule service run every minute.
It worked fine on emulator (even when killing the service) but on real
devices it failed often
Derek wrote:
> Refresh is every minute.
:: blink, blink ::
Every *minute*?
That's not really a good idea.
If you have a short-term need for an every-minute bit of work, you may
as well use a regular Service and a Timer/TimerTask. This would, by
definition, eliminate your classloading problem,
Refresh is every minute. We didn't get crash report from 2.x users
yet.
Here is the WakefulIntentService I'm using:
public abstract class WakefulIntentService extends IntentService
{
public static final String LOCK_NAME_STATIC =
"my.app.Service.Static";
private static PowerManager.
Derek wrote:
> I've implemented it and I got the crash report from the end user. See
> details below.
> The error report is VerifyError when the broadcastReceiver tries to
> start the WakefulIntentService.
> It happens on Cupcake/Samsumg. I've tested under emulator with 1.5
> (minSDK=3) and it work
Hi Mark,
I've implemented it and I got the crash report from the end user. See
details below.
The error report is VerifyError when the broadcastReceiver tries to
start the WakefulIntentService.
It happens on Cupcake/Samsumg. I've tested under emulator with 1.5
(minSDK=3) and it works perfect.
It s
Derek wrote:
> I'm also using your WakefulIntentService sample. It works fine in
> emulator (all releases of Android). It seems to work fine on many
> devices (HTC Magic, Nexus One ...). However, I get "Force Close"
> complains from some users everytime the Alarm goes off. Some are under
> 1.5 and
Hi Mark,
I'm also using your WakefulIntentService sample. It works fine in
emulator (all releases of Android). It seems to work fine on many
devices (HTC Magic, Nexus One ...). However, I get "Force Close"
complains from some users everytime the Alarm goes off. Some are under
1.5 and other are und
hi,
We have set the alarm on Droid (after 4 minutes). Switched off the
phone.
But the phone didn't wake up or didn't show the alarm for the preset
time.
Is this a normal behavior?
And why?
Sachin
On Mar 14, 1:14 am, mot12 wrote:
> I misspoke: I meant to turn off user applications running in the
I misspoke: I meant to turn off user applications running in the
background.
Many people use the flightmode at night as they use their phones as a
bedside alarm clock. Many alarm clocks offer this functionality and I
would consider this a typical use of the device.
>From some 6000 active users I
I misspoke: I meant to turn off user applications running in the
background.
Many people use the flightmode at night as they use their phones as a
bedside alarm clock. Many alarm clocks offer this functionality and I
would consider this a typical use of the device.
>From some 6000 active users I
mot12 wrote:
> No customer could give me a definitive guide to reproduce the problem.
> But doing the following should give you good chance to make it happen
> on your device:
> - turn on airplane mode to cancel much of the background activity
> - turn off any services, apps running in the backgrou
Mark, it is quite possible that Nikhil and I are talking about
different problems. However, the problem my customers are observing
will not be verified by your project since you fire alarms every 5
minutes. My users report that if the phone goes into a "deep sleep
mode", alarms may not fire. Deep s
I ran this project overnight on a DROID:
http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices/Alarm/
Every alarm fired, as expected. The device sat idle, unplugged, for over
12 hours.
I'll be checking it again every 12 hours or so for a while, to see if it
fails. After all, it m
Maybe it is something else then :(. I would suggest a quick test to
establish that we are talking about the same thing:
Test 1)
Set the stock alarm to ring right after your alarm should go off. For
several devices I have users that passed this test, i.e. both alarms
don't go off. (And make sure th
Thanks for your reply martin. By any chance, do you have a list of
phones facing this problem?
In our case, the phone stops receiving notifications immediately after
it is put in the sleep mode. Once it is out of sleep mode it works
well. Also, the user has indicated that in sleep mode it works on
I am the developer of Gentle Alarm and I can confirm that several
phones have issues with the sleep mode and non-firing alarms.
Unfortunately, there is no sure-fire way to reproduce this so I can't
tell you do A, then B, and the alarm won't ring. It typically happens
though if the device has been i
Okay Mark, just joined the group. I will contact you there and till
then will try to think of different possibilities..
On Mar 10, 4:06 pm, Mark Murphy wrote:
> nikhil wrote:
> > Yes Mark, I refered to your wakeful intent article and then
> > implemented the wakelocks, alarmmanagers etc...It wor
nikhil wrote:
> Yes Mark, I refered to your wakeful intent article and then
> implemented the wakelocks, alarmmanagers etc...It works really well
> for Nexus One and even G1.
>
> The problem that our droid customers are facing is that the app works
> well whenever the phone is on like not in slee
Yes Mark, I refered to your wakeful intent article and then
implemented the wakelocks, alarmmanagers etc...It works really well
for Nexus One and even G1.
The problem that our droid customers are facing is that the app works
well whenever the phone is on like not in sleep mode (shows status bar
n
21 matches
Mail list logo
