A software engineer living in Vancouver, Canada - http://www.antonypranata.com/
antonypr | 24 April, 2007 05:30
Recently I had a strange problem with my Nokia E61 device. The device needs to be charged every day. I was quite sure that the battery was still okay. The device was relatively new, about 1 month old. Before it happened, I could use my device for 3 - 4 days without charging.
I thought it must be from one of the applications that I have installed recently. I suspected one of the applications that I have just installed. Then, I decided to uninstall it (I am not going to disclose the name of the application). What happened after that? The problem with my battery was solved. I can use my device normally.
Why did it happen? Apparently, the application installed a server that runs in the background. I am not sure what the server is doing, but it empties the battery very fast.
As a mobile developer, how can we avoid this? Forum Nokia has a good paper, S60 Platform Effective Power and Resource Management. I won't repeat everything here; just highlight some of the important points:
Please, always remember that mobile device has limited battery power. It is not the same as desktop world where the power is "unlimited".
antonypr | 24/04/2007, 18:20
That is a good point.luis-junior | 25/04/2007, 06:14
Great topic!stichbury | 24/04/2007, 20:13
antonypr | 25/04/2007, 07:49
Jo, you are right that there might be a server still running even though we can close the application. I believe this was the case in my problem too. I didn't see application running in the task list. I'll try to contact the developer and see what their comment.
A software engineer living in Vancouver, Canada - http://www.antonypranata.com/
RDF Facets:
qfnZtopicQUqfnTopicZcppQ
qfnZtypeQUqfnTypeZBlogContentQ
qfnZtypeQUqfnTypeZBlogE45ntryQ
qfnZtypeQUqfnTypeZCommunityContentQ
qfnZtypeQUqfnTypeZWebpageQ
qmarsZlanguageQUxhttpE3aE2fE2fswE2enokiaE2ecomE2flanguageE2d1E2fenX
Re: Always Remember that Mobile Device has Limited Battery Power
mgroeber9110 | 24/04/2007, 11:02
My favourite example are audio streams - if you open a CMdaAudioOutputStream, play some buffers, and then just let the queue underflow (i.e. you supply no more audio data), but do not call Stop() on the stream, the audio hardware stays open, and drains the battery in about half a day.
This behaviour was introduced only with the 6620 and later phones, but to my knowledge has never been explicitly documented anywhere.
So even for developers, the only way to learn about this may be through user feedback, and collecting feedback from the field.