Hi Brill,
is your question about the BuzzBox SDK?
It's a complete (but simple) solution if you want to add notifications
to your App.
The scheduler is the core. Then you can use the UI activity if you
want to let your users to schedule the task. It depends of the use
case.
For example, if you
Why is the analytics library mixed up with a UI library like that?
Sounds like a maintenance nightmare.
- Brill Pappin
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to android-developers@googlegroups.com
Finally, My alarm is working with notifications. :)
Thanks all and special thanks to Kostya Vasilyev
On Sat, Mar 12, 2011 at 1:42 ,AM, Kostya Vasilyev kmans...@gmail.comwrote:
11.03.2011 23:10, Marcin Orlowski пишет:
- Connect to your phone/emulator with adb shell, use dumpsys power to
How should I implement WakeLock in my above mentioned code?
2011/3/11 Jonathan Foley jonefo...@gmail.com
Is the device going to sleep? If so you'll need to acquire a WakeLock
otherwise it will wake up for the alarm and may fall back asleep
before the notification ever gets fired.
Before you look into using a WakeLock (which might not be necessary,
since Android keeps a wake lock for the duration of your onReceive)...
There are a few things in your code that look rather strange to me:
1 - Your broadcast receiver is called Notification (bad name, btw, as it
clashes with
Moreover, if i set reminder to current time using
alarms.setRepeating(AlarmManager.ELAPSED_REALTIME,
SystemClock.elapsedRealtime(),
30 * 1000, alarmIntent);
then it is notifying perfectly.
2011/3/11 Brad Stintson geek.bin...@gmail.com
2011/3/11 Kostya Vasilyev
Sounds like your Calendar-based time calculation is wrong (for the
original, non-repeating case).
-- Kostya
11.03.2011 20:31, Brad Stintson пишет:
Moreover, if i set reminder to current time using
alarms.setRepeating(AlarmManager.ELAPSED_REALTIME,
SystemClock.elapsedRealtime(),
2011/3/11 Kostya Vasilyev kmans...@gmail.com
Before you look into using a WakeLock (which might not be necessary, since
Android keeps a wake lock for the duration of your onReceive)...
There are a few things in your code that look rather strange to me:
1 - Your broadcast receiver is called
For calendar values, i tried all possible values in UTC time as well as
emulator time. Still it is not showing the notification. Is it related to
WakeLock? If yes, then how to implement it?
2011/3/11 Kostya Vasilyev kmans...@gmail.com
Sounds like your Calendar-based time calculation is wrong
All possible values in UTC time - there are (2 63) - 1 of those,
which is almost 10 ^ 19, so I don't see how you could have tried them
all so fast :)
Even without a wake lock, your receiver's onReceive should still be
called (you do log that, right?).
RTC_WAKEUP uses wall clock time in the
- Connect to your phone/emulator with adb shell, use dumpsys power to
check your alarm after it's been set.
You probably meant dumpsys alarm?
--
Regards,
Marcin Orlowski
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this
11.03.2011 23:10, Marcin Orlowski пишет:
- Connect to your phone/emulator with adb shell, use dumpsys power to
check your alarm after it's been set.
You probably meant dumpsys alarm?
Yes, I did. Thanks.
--
Kostya Vasilyev -- http://kmansoft.wordpress.com
--
You received this message
How to get time from database n trigger notification on that time?
On Thu, Mar 10, 2011 at 4:45 AM, roberto roberto.fo...@gmail.com wrote:
On Mar 9, 11:41 am, Marcin Orlowski webnet.andr...@gmail.com wrote:
On 9 March 2011 19:59, roberto roberto.fo...@gmail.com wrote:
From a database? Same as anything else, by using a query. Probably easiest
to keep date/time values as a long integer (standard Unix representation).
Once you have the time value, use AlarmManager and NotificationManager
classes in Android.
10.03.2011 16:47 пользователь Brad Stintson
*My application is not triggering notification at specified alarm time.
Please see below classes and tell me how to do that.*
*
*
*
*
*This is my notification class.*
public class Notificaition extends BroadcastReceiver {
@Override
public void onReceive(Context context, Intent intent)
Is the device going to sleep? If so you'll need to acquire a WakeLock
otherwise it will wake up for the alarm and may fall back asleep
before the notification ever gets fired.
Jonathan
On Mar 10, 10:06 pm, Brad Stintson geek.bin...@gmail.com wrote:
*My application is not triggering
Hi Brad,
you might want to consider using the BuzzBox SDK to do schedule a Task
very quickly.
You can use a cron string to schedule your task, in your case it would
be:
SchedulerManager.getInstance()
.saveTask(this, 0 10 * * 1,2,3,4,5,6,7, YourTask.class);
The BuzzBox SDK takes care of
On 9 March 2011 19:59, roberto roberto.fo...@gmail.com wrote:
http://hub.buzzbox.com/android-sdk/
Looks interesting but I personally am not happy with it being closed
source (which I could stand) but integration with their analics. Who
knows what it analites when your app got internet
On Mar 9, 11:41 am, Marcin Orlowski webnet.andr...@gmail.com wrote:
On 9 March 2011 19:59, roberto roberto.fo...@gmail.com wrote:
http://hub.buzzbox.com/android-sdk/
Looks interesting but I personally am not happy with it being closed
source (which I could stand) but integration with their
No. Android is currently not intended to work on a non-touch device.
Please don't add menu items for the notifications on the off-chance that you
will run on a non-touch device; if someone builds such a device (or the
platform is updated to support them), then access to the status bar will be
Ok. Thanks for the clarification.
On Tue, Oct 6, 2009 at 11:41 AM, Dianne Hackborn hack...@android.comwrote:
No. Android is currently not intended to work on a non-touch device.
Please don't add menu items for the notifications on the off-chance that you
will run on a non-touch device; if
Android currently requires a touch screen. If someone makes a phone without
a touch screen, they can come up with whatever way they want to get at the
notifications. Either way, you can always get to them by going home and
selecting notifications from the menu, though obviously this is less than
It's possible to access the notifications without a touch screen
though. Home Menu Notifications.
On Mon, Oct 5, 2009 at 10:08 AM, Dianne Hackborn hack...@android.com wrote:
Android currently requires a touch screen. If someone makes a phone without
a touch screen, they can come up with
All right. Thanks for the replies. It would be nice if this is documented
somewhere.
Instead of navigating to Home --Menu and then notifications, is it not
possible to click on the Menu button in the current activity and then
navigate to Notifications directly from the currently displayed activity
24 matches
Mail list logo
