ThemePark wrote: > Point taken. I didn't think it would use up a lot of battery power, > but you're right, a lot of little bits certain would.
It would be entirely possible to have the app only run when the device is charging; given that most people with smartphones leave them on charge overnight, this would still get you reasonable run time. There's an ACTION_BATTERY_CHANGED intent that you can register for to get notified when the AC power status changes, but I don't know offhand how you'd poll for the current status. > I've been reading about using stuff like messages > and threads in general, but I am unsure of what I should use > specifically in Android. You probably want to read up on this: http://code.google.com/android/reference/aidl.html Note that you only really need to do this for IPC between different apps on the same device. The most common use for this is to allow one app to communicate with a library that's actually part of another app --- ContentProviders, for example. For a distributed processing app, the most likely scenario is to have the actual calculator running as a background service, with a separate app communicating with it via IPC to show the results to the user, that only runs when the user actually wants to watch things happening. -- ┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ───── │ │ ⍎'⎕',∊N⍴⊂S←'←⎕←(3=T)⋎M⋏2=T←⊃+/(V⌽"⊂M),(V⊝"M),(V,⌽V)⌽"(V,V←1⎺1)⊝"⊂M)' │ --- Conway's Game Of Life, in one line of APL
signature.asc
Description: OpenPGP digital signature
