Peli, Sorry I have taken a while to reply.
I see that you are planning to do this after the code submission date. Please do contact me if necessary to share ideas. I am not able devote enough time to Android to actually help you in the coding. The benefits of something like this are 1. The user experience is MUCH better. He doesnt have to make similar settings in many apps. It is centralised. If he finds that polling once in 10 min is causing his battery to drain too fast, or his battery is low and he wants to conserve it for emergencies he can easily change the setting in one place rather than going to many applications to change this setting. Android has many excellent ideas, exciting for developers. But I peronally see many issues with its usability. Google has managed excellent usability in their search engine, mail, calendar etc. But their approach in Android seem flawed for creating a device with good usability. This is one example. 2. Restoring from a hibernation and going back to sleep will be needing current from the battery. I expect that waking up once in 15 min from hibernation instead of thrice in 15 min will definetely drain the battery less. 3. If the polling is just a request a response from server with not much data interchange, establishing a connection to server and disconection should occupy a large percentage of time and if same connection can be shared, the time will reduce and hence battery drain will be less. gk On 3/26/08, Peli <[EMAIL PROTECTED]> wrote: > > > Your idea sounds very useful. Indeed, it could be an idea that would > fit well into our project "OpenIntents". I already suggested it as an > idea in our project group: > > http://groups.google.com/group/openintents/browse_frm/thread/7f34fe99bd23c25 > linking back to this discussion here, so feel free to add any > additional information there as well. > > As of the real savings, I'm not so sure. Google seems to promote > "always-on-networking", so the connection cost should not matter as it > would be a flatrate. > > As for saving battery, one still has to transmit a certain amount of > data, so whether I transmit 3 minutes out of 15 minutes in a row, or 3 > times 1 minute within 15 minutes does not obviously seem to make a > large difference in battery savings. > > I imagine, there could be some savings if all services polled exactly > at the same time in parallel (to fill waiting gaps for individual > services) that could reduce the time say from 3 minutes for 3 services > to 1 1/2 minutes for 3 services, so the phone could sleep for 13 1/2 > minutes which would make sense. > > Peli > > On Mar 25, 4:55 pm, "Krishna(GK)" <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Connecting to internet continously or polling is likely to cause drain > on > > battery. ( > http://groups.google.com/group/android-developers/search?group=androi... > > ). > > > > Lots of people are going to write apps that poll server. Each one will > need > > configuration on how often to poll. And user will have to configure in > each > > app. If he configures every 15 min in 3 different apps and each start > poll > > at a different point in time he will be connecting to the internet > thrice > > every 15 min. Not nice. > > > > Suggestion > > > > 1. Set up a Internet polling mechanism for polling the internet > defaulting > > to every fifteen minutes. User can change this setting in one place. > Allow > > services / apps to subscribe to this service. IPM(Internet polling > > mechanism) wakes up one service at a time. service polls internet does > > whatever it wants and goes back to sleep. > > > > Now each app has to initiate a connection and close it, which from my > very > > basic understanding will slowdown the whole process and again drain > battery. > > Instead IPM opens a socket and hands socket to each service round robin > > fashion. Service only indicates done. When all subscribers done IPM > closes > > down connection. > > > > Question > > Does this make sense, I am no TCP stack or Mobile phone expert. Will > > somebody with more knowledge pitch in please. > > > > gk > > > --~--~---------~--~----~------------~-------~--~----~ 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] Announcing the new M5 SDK! http://android-developers.blogspot.com/2008/02/android-sdk-m5-rc14-now-available.html For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
