Your app will most either kill battery life or spend most of it's time suspended, making it either unpopular or very slow.
Most battery powered devices (such as the G1) try to increase battery life by reducing processing load, so when you whack up the lock the battery suffers. Al. ThemePark wrote: > I've been reading through a bit of the Android documentation, and this > seems to be perfect for developing one of my projects. But in order to > make sure, I need to get some things straight. > > Android has processes (background processes being especially > interesting), life cycles, and as far as I can tell, the ability to > connect to networks. So as far as I can tell, I should be able to > build a distributed system, by having a server with my program and > some data, and then any number of G1 phones, that have downloaded and > installed another program for downloading some of the data, running > calculations on it, and uploading it back to the server. > > Am I right about being able to do that, and how should I go about with > it? What things should I be careful of/look out for? > > > > -- Al Sutton W: www.alsutton.com B: alsutton.wordpress.com T: twitter.com/alsutton --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
