ThemePark wrote: > With that in mind, wouldn't it be possible for me to run it as a > background process, possibly only running when the phone is not being > used (if at all possible), and that way not use a whole lot of battery > time and not making it slow either? Think of the way SETI works.
[EMAIL PROTECTED] is usually used on machines plugged into AC power. Mobile devices are infrequently plugged into AC power. On a mobile device, every executed instruction eats a tiny bit of battery power. What you're suggesting is to execute a whole lot of instructions while users are thinking their phone is asleep and therefore is not using (much) power. If Android starts getting used for devices more frequently connected to power, using it for a distributed computation cloud might make sense. -- Mark Murphy (a Commons Guy) http://commonsware.com Android Training on the Ranch! -- Mar 16-20, 2009 http://www.bignerdranch.com/schedule.shtml --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
