Developing an AppWidget – Part 4

Keep On Running… Some may have noticed that I updated my previous post with a footnote describing an issue with my battery widget not resuming it’s updates after the phone went into (and came out of) deep sleep. I got to the bottom of that and can now happily report that my widget seems 100% reliable and the solution is not contributing to any additional battery drain. This is what I did…

To init() or Not to Init(), That is the Correction

The short answer is: Yes, init() In a previous post I lamented the fact [cough – Ed] that some Java class imports appeared to support the underlying Java constructors via an init() method, where others did not. This wasn’t a “fact” at all. It was a misunderstanding based on an incomplete grasp of the machinations of the Java class import mechanism in the AndroidAPI units.

Getting the Battery Level on Android With Delphi

Over the past few days I posted a two part series showing how to obtain the current battery level as part of the implementation of an Android AppWidget using Oxygene. As far as I can tell AppWidgets simply aren’t possible using Delphi but reading the battery is quite straightforward Android SDK work, and I thought a comparison of the Oxygene and Delphi equivalents might be interesting.