It's my understanding that the Google Calendar API is yet
undocumented, although it's pretty obvious how to get at them if you
use the correct query string. When I query content://calendar/events
I get access to a ton of Calendars, but I noticed that the Calendar
I've synched from my MS Outlook
It's my understanding that the Android NDK is just a way to achieve
increased performance in an application. In .NET development, the word
native often means unmanaged which tends to provide a more
granular level of control relative to the standard managed APIs.
Does the Android NDK also provide
I'm interested in writing an application that extends the
functionality of the Android clipboard. Basically, when the user tries
to perform a copy (as in copy-paste) I want my application or
Service to perform a function on the copied text.
Is this possible?
--
You received this message because
if the Alarm is registered on BOOT_RECEIVED.
On Mar 29, 9:22 am, AuxOne tyler.thack...@gmail.com wrote:
I've done extensive tests and realized that the Alarm works perfectly
when I install it to my device via Eclipse (then unplug the cable),
but when I upload it to Android market the Alarm won't
I'm starting the AlarmManager from a BOOT_RECEIVED broadcast and it
works like a charm. I've noticed, however, that it requires a restart
to take effect because it's triggered from a broadcast. In light of
this I also start the AlarmManager from the onCreate() of my activity
so that the user
It just occurred to me that if I create it from a static context it
shouldn't really die with the Activity. That's what I used to be
doing, but later I switched it to an instantiated class. I'll see what
happens.
On Mar 27, 9:12 am, AuxOne tyler.thack...@gmail.com wrote:
I'm starting
Then maybe it's the Service that is dependent? All I know is it works
after reboot, but not after immediately installing (and starting Alarm
from Activity). It's a 1 hour+ timer.
On Mar 27, 9:18 am, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
It just occurred to me that if I
I have a Dev 1 Phone which I was able to update from Android 1.0 to
1.6 via an OS Image found online. I did not see an OS Image to update
to 2.X.
Does that exists?
Does the hardware of the Dev 1 even support it?
Thanks
--
You received this message because you are subscribed to the Google
So perhaps it would suffice to just Thread.sleep() for 30 seconds
after WakeLock is set, to wait for the Wifi. I'll experiment with that.
--
You received this message because you are subscribed to the Google
Groups Android Developers group.
To post to this group, send email to
I have a Service/AlarmManager set to go off ever hour; as seen at:
http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices/Alarm/
The Alarm triggers a Socket connection to communicate with a Web
Server. I'm logging the interaction to a file so I can see it later.
When I leave the
/com/commonsware/android/syssvc/alarm/WakefulIntentService.java
Thanks again.
On Mar 24, 5:12 pm, nikhil nik...@gmail.com wrote:
You need a partial wakelock and internet permission.
On Mar 24, 3:56 pm, AuxOne tyler.thack...@gmail.com wrote:
I have a Service/AlarmManager set to go off ever
the lock
into my Thread and release it from there?
Your KungFu is the best!
On Mar 24, 5:21 pm, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
I have a Service/AlarmManager set to go off ever hour; as seen at:
http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices
=
(PowerManager)context.getSystemService(Context.WIFI_SERVICE);
lockWifi = mgr.newWakeLock(PowerManager.PARTIAL_WAKE_LOCK,
LOCK_NAME_WIFI);
lockWifi.setReferenceCounted(true);
Thanks
On Mar 24, 5:59 pm, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
The wi-fi lock sounds interesting
If this is something that's supposed to be going on 24x7, since keeping
the WiFi radio on all that time will drain the battery pretty good, I
think you're more going to need to just hang tight in your
doWakefulWork() until WiFi connectivity is restored.
It is indeed 24x7. What do you mean by
Just to let you know, I experimented with FULL_WAKE_LOCK. Not only did
it not turn on the screen as it said it would, which is a good thing I
guess, but it also doesn't seem to lock as effectively as the
PARTIAL_WAKE_LOCK. Both seem to go into a deep sleep around 15-20 min
of use and then WiFi
The filepath used for the File class has to include a special prefix.
getFilesDir() or Environment.getExternalStorageDirectory() should get
it.
It's usually data/data/your package name/files/ for the phone
memory and sdcard/ for the SDcard.
--
You received this message because you are subscribed
I've successfully implemented a BootReceiver, AlarmManager, and
Service per the code here:
http://github.com/commonsguy/cw-advandroid/tree/master/SystemServices/Alarm
Inside the doWakefulWork method of the Service I am instantiating a
few classes, but some of them require my Activity to be
On the whole, that's not a good idea. Popping up an Activity in the
middle of whatever the user is doing will not be popular. There are
certain circumstances where this is appropriate -- incoming VOIP calls,
etc. -- but should not be done in general. Users will attack you with
sharp pointy
Sorry if I seem confused...
Call getContentResolver() in your Service.
I'm also doing things like .sendBroadcast() to refresh the photo
gallery, .openFileInput() from the Activity. So doesn't that mean
GetContentResolver() won't work for me?
Your example code has the Alarm scheduled from
Is there any advantages / disadvantages to having the Service start
the AlarmManager, as opposed to the AlarmManager starting the Service?
I though Services were more robust.
On Mar 19, 10:50 am, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
Like, what If the phone
boots up
I have a single Activity application, within it I have a service which
creates an AlarmManager and sends a broadcast to a broadcast Receiver.
If the activity which starts the services dies, (ie. divide by zero),
the broadcast receiver stops the old service which created the
AlarmManager.
It works
.
E.g
while ((len = is.read(buffer)) != -1){
os.write(buffer, 0, len);
os.flush();
}
I haven't looked at the underlying implementation of org.apache.http
package in Android. But perhaps it is worth investigating if you
continue to have problems.
Makas
On Mar 13, 8:17 am, AuxOne
.
E.g
while ((len = is.read(buffer)) != -1){
os.write(buffer, 0, len);
os.flush();
}
I haven't looked at the underlying implementation of org.apache.http
package in Android. But perhaps it is worth investigating if you
continue to have problems.
Makas
On Mar 13, 8:17 am, AuxOne
Sorry for the double post. I reloaded the page
--
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
To unsubscribe from this group, send email to
I have an application with a single Activity implemented as a
singleton (in the AndroidManifest). It implements a Listener I wrote.
When the application is first run the Listener works fine. When I use
the home button to minimize it, then open it again it's still fine.
But when I press the back
Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
When the application is first run the Listener works fine. When I use
the home button to minimize it, then open it again it's still fine.
But when I press the back button then run it again from the
application icon, the Listener doesn't work
,
however the problem remains.
Thanks!
On Mar 13, 1:37 pm, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
Shouldn't it suffice to just re-register the listener onCreate()?
If you are talking about registering some listener with Android
(LocationListener, etc.), then no. Please unregister
with.
Thanks
On Mar 13, 2:13 pm, Mark Murphy mmur...@commonsware.com wrote:
AuxOne wrote:
I've chosen singletonInstance in hopes of avoiding the problem I have
now. It just seems to me from a memory perspective it could be better
to have less instances of the application in memory
My application loads/saves contacts, but I am having some confusion
regarding the difference between unsynched contacts and those
associate with a Google account.
In the emulator when I create a contact manually the account it uses
is Phone-only (unsynched). When I read the contacts via
I have some Android code that can send files to my webserver using an
HttpsUrlConnection, but when it tries to send larger files I get an
OutOfMemory exception when opening the OutputStream. Can anyone offer
some assistance?
It looks something like this:
httpConn = (HttpsURLConnection) new
My app runs on a 1 hour timer. I'd like it to run even if it's not in
the foreground, and even if the phone is asleep, preferably even if
the app isn't even running.
I tried to accomplish this via AlarmManager and Services. The
AlarmManager just seems to queue the process because nothing happens
When I create a contact on the emulator manually it says Phone-only
in the top because it's creating it locally. When I check the contacts
via my application, I see it there.
When I create a contact via my application, the only method I've found
is via a RawContact which requires an Account name
32 matches
Mail list logo