Hello,
A few years ago, I developed a free server monitor (bMonitor) that has
ping, port, and http(s) monitor capabilities. It has required very
little maintenance to keep up with the rapidly evolving Android OS.
However, in the last several months I have noticed more and more users
are complaini
Im holding out for the Notion Ink Adam. There is an anouncement coming
on 12/9. Hopefully either the release date or pre-order.
I was waiting for the Archos 101, but there a quite a few unhappy
people right now on archosfan.com forum concerning the latest firmware
upgrade to the 7 and 101.
On Dec
Dianne and Mark,
I just wanted to thank the both of you for your help on this. Your
suggestions worked beautifully. My application has been running
several hours on two different phones and it has not missed a
scheduled event yet.
Just in case the two of you don't hear this enough, I for one, tr
e.
> > Do you use AlarmManager.RTC_WAKEUP?
>
> > On Fri, Mar 27, 2009 at 5:45 PM, Mark Murphy wrote:
>
> >> clarkbriancarl wrote:
> >> > THanks for the reply. I use your book as a reference from time to
> >> > time. I would recommend it to anyone reading this.
&
are doing different. I just want to make
sure this is an issue and not a mistake on my part.
I am willing to post some code if it is needed.
On Mar 27, 10:18 am, Mark Murphy wrote:
> clarkbriancarl wrote:
> > The best I can get in a 24 our period for an
> > alarm scheduled eve
I have an observation concerning how Android handles scheduled events
and would like any suggestions, comments, or feedback on how other
developers have handled this behavior in Android.
I have noticed that there does not appear to be anyway to schedule an
event to happen at "regularly" scheduled
I understand that Android uses an applicaiton ID for File I/O when
using openFileInput and openFileOutput.
My question is if I create an instance of a class in the Activity
onCreate like the following and do some file IO from the new class,
why does it fail? If I make the MyClass an inner class o
t;
> void barRight() {
> try {
> wakelock.acquire();
> doSomeWork();
> } catch (SomeException e) {
> Log.w(...);
> } finally {
> wakelock.release();
> }
>
> }
>
> On Sat, Feb 7, 2009 at 11:19 PM, clarkbriancarl
>
>
Thanks for the reply. I've been reading and tweaking for over a week
trying to figure this out. Thats a good idea to use the Alarm Manager.
I think I will give that a try. I would still like to hear from a more
experienced devloper or a google engineer if this is the way an
Android service is supp
The android.content.Context api exposes two methods for starting a
service. startService and bindService. The api docs state that when a
service is started with Context.startService, that requires the
service to remain running until stopService(Intent) is called,
regardless of whether any clients
10 matches
Mail list logo
