Fixed!

So, I found the problem with the in app purchasing not verifying (the payload)... and it turns out that:

string1 == string2

would return false (even though they were the same string) but,

string1.equals(string2) == true

would work as expected.  Now, this is something very small and trivial and something that I potentially should have realized a lot faster.  The problem is that (for right now) I don't do java development and that's just how things work in java.  My 9-5 job is slowly (and I do mean SLOWLY) starting to move into the world of web development using angular and java script and at that point comparing two string values using .equals will become trivial, but for now the .NET developer that I am expects the == to work the same way.

As usual, when I end one of these posts, I'll mention what the future holds for Desk Clock Plus.  As usual, I'll say that I'm not sure.  It is one of those things that I want to get back to and do a proper re-write.  However, over the past two years or so, I've started working more with a non-profit museum that I've belonged to for most of my life.  I'll be starting on a fairly large project that will need to be completed by October(ish).  While that seems like a long time, remember that I'll be working on it less than an hour a day.  After that, who knows...

But the one thing I do want to do is thank everyone who has downloaded Desk Clock Plus and a big thank you to the people who threw a dollar at me for the extension.  I never though that it would ever have been downloaded over 50,000 times and still have 9-10,000 installs.

Bob

Does this still work...

...Why yes, it seems that it does! The updates here are few and far between (last post April 2013?!?!?) and the last update to the app was August 27, 2013?!?!!?  G+ posts have only been slightly better with the last one back in February.  I honestly should do another "State of the App" type post, but my time for today is limited.  So the short version of what happened goes like this (Starting in February):

• Re-write started using Android Studio
• Problems with Android studio kept development to a snail's pace
• Something Super Crazy AWESOME happened
• 100% of my time got devoted to that super crazy awesome thing
• The super crazy awesome thing didn't pan out
• Little bit of depression
• The World Cup
• Re-re-write started in eclipse and I've been addressing GUI changes

That brings us to Monday when I got an email about the app selector not working for the MP3 button.  This feature has been a pain in my butt since day one and I've gone though many different methods for picking a music app and I'm hoping that I've got one that works...

Also, Galaxy S5 users don't have a menu button any more, so they couldn't access the menu (there's a back door method), but I figured I should also add an on screen button.  That's what the colon in the upper right side is for.

I have been working on Desk Clock Plus V2 and hopefully I be able to share a rough screen shot shortly.

Thanks for your support and patience. 

I am HERE!

Yesterday afternoon, I posted the "second half" to the hot fix that was caused by the deprecation of the Yahoo Geo coder.  The static location picker should now be working again.  When you enter your location, if there's more than one returned you'll get prompted with the first 20 results.  If you're location isn't there you may need to provide more information (state for example).  In some ways, I'm a little happier with how this works, but in other ways, I preferred the old method as I was able to pre-filter the results by your location (ie US, UK, AUS, etc).

My goal for tomorrow is to write (or at least write most of) a post regarding the state of Desk Clock Plus.

Previously on Desk Clock Plus...

It's been a month and a half since the last post.  Work and life in general has had me running like crazy with little time (or motivation) to work on the clock program let alone update the blog.  Since the last post on July 2, here's what's changed:

• A number of smallish bug fixes that came up from any number of reporting methods (see: How to get a bug fixed.)
• A quick hot fix because one of things I tried didn't work... 
• Two new features:
• Orientation Lock
• Static background color
• Caught a potential NULL value
• Fixed a display bug for 100+ degree days

That brings us up to today's minor update which is just adding 1 minute to the screen saver time out.  I promised this to a user back in December, but I forgot about it.  Sorry!

I have been working on Desk Clock Plus when I can since the last post, but I haven't gotten anywhere really.  The game plan is to break the application up from one big project into a number of smaller libraries and one execution project.  This will then allow me to swap parts of the application out on a version by version basis. The real push for this is the Alarm code which is still based off the 2.2.  I had to maintain that version of code as it pretty much worked for all the different versions of Android.  Google made a major improvement for 2.3 which I'm not using.  The goal is to build a legacy version of the alarm and then other versions for 3.x versions and for 4.x versions.  Libraries are key to keeping all that code manageable by re-using all the common code among 3 different versions.  The problem is the code is so interlaced that can't quite get the code split up correct to avoid circular references (ie two libraries that reference each other, which leads to the chicken vs the egg problem). 

Earlier this week, I came to the conclusion that the on-the-fly design method really wasn't working (there's a big surprise) and I'm going to have to sit down with some design tools and figure out how I can break up the application that works for now and should work for future enchantments.

Hold on tight...

The updates might be a little fast and frequent for the next week.  I figured that I would spend some time reviewing the stack traces that have been sent in (I was up to about 15 issues).  Some of them were odd little things that only happened once, but still required some extra checks to make sure it didn't happen again.  I did however make a couple minor fixes to the stuff I released last week that caused some users to get an index out of bounds error.

I still have about 10 issues that need to be looked at, but as long as nothing critical comes in overnight, I'll probably hold off as long as I can before pushing the next set of bug fixes out.

Long time coming...

The last post to this blog was made on April 10th and the last update to the app was probably around that time as well.  That's almost three months... and you would think that after that amount of time I would have some crazy new enhancement ready to roll out.  Sadly, I don't.  After the last update, I started into looking at a weather extension and I think I have a plan for that, but then my 9-5 job got real crazy and home life got crazy.  I also got an email from a user who couldn't configure the docks, so I started into a redesign of the save / load mechanism for the custom docks.  The problem was that I lost motivation to work on this during my lunch break, so things started moving very slowly.

That started to change a couple weeks ago... with Verizon's move from the unlimited data plans.  My wife and I replaced our 2 1/2 year old OG Droids were replaced by shiny new Samsung Nexus' (Nexi?).  That kind of got me moving again as developing on the new phone is a dream compared to the OG Droid.  Then as it seems almost always happens I got a couple emails about the dock configuration issue.  What was nice was that one of the user's said that the problem started after his Razr was updated to Ice Cream Sandwich.  Quick emails to the other users and it seems that they were all on version 3.2 or higher.    I was able to confirm the issue on my new phone as well.  Fortunately, I was about 75% done with a rewrite of the dock extension and I was able to finish it up and send out a Beta to the users who has emailed me.

I made some other minor adjustments and that brings me up to where we are now.  Version 1.0.0.28 was just pushed out the market a little while ago with a better way for me to handle saving the dock configuration (that also works for ICS) and a small tweak to how I try to get the music apps, based off this article from Android ER.

I do feel a little motivated to work on Desk Clock Plus more after diving back into get this last bug fixed, so hopefully I'll be able continue to be motivated and get going on the other extensions that I've been thinking about since I started on the Desk Clock Plus project about a year and half ago.

Thank you all for your support and patience between updates.

A cause for alarm

First, a little note about the update from Friday.  There was a small fix on the preference screen where I was trying update the GUI from a background thread (that's a no-no).  The other fix was that I sat down last week and wrote my own translation app using a combination of .NET, LINQ and Microsoft Translation.  Much like Desk Clock Plus, it was me writing up something to fill my need, so hopefully this will keep all the strings in sync with all the different languages.

Next, Scott left the following comment:

Worked great before the last update Doesn't open automatically when docked anymore. Have to manually open it now. Also, the alarm turns off after every update.

Thankfully he (or someone else named Scott) followed up with an email.  I think his docking issue is something at his end as nothing with that has changed with that ever.  (Update) I got another email from someone else who said that there was an update for the same device (Galaxy S) and after that he was having docking issues.

The reason point of this post is the side bit of information that Scott tossed in about the the alarm turns off after every update.  This was actually a really big thing to me... I had had another user in the comments state:

Dont rely on alsrm The clock is nice BUT DONT RELY ON THE ALARM. It only goes off about a quarter of the time.

That comment was made right around the time that version 1.0.0.7 came out and there was a signification amount of code churn and updates being pushed.  If something is happening with the set alarms after every update then this comment makes a lot of sense.  I don't use the alarm feature of my application very often as I use it at my desk at work (hence the name Desk Clock Plus).  So, I've never set a recurring alarm and therefore never had a recurring alarm set when the application is updated.  As I said when Version 1.0 was released, the Alarm code was taken straight from the Google Source and honestly, I never took the time to review it / understand it.  I think my other two scrolling dock enhancements will have to wait until after this gets taken care of...

I'm waiting to hear back...

The last update fixes two issues, the first I realized there was a problem yesterday and I mentioned it on the g+ page.  There were a handful of Application Not Responding reports coming in and after a quick look yesterday, I realized that I committed a programming foul.  Typically, anything that's going to take a long time or anytime you're going out of the device to get something (picture, info, etc) you want to put it in a thread.  This way the thread can do it's thing and the main part application can continue doing it's thing.  I had done this in the past in a number of places (getting the image and weather just to name two).  However, I didn't think about doing this for all the new Yahoo! PlaceFinder web service calls that I mentioned in my Round up.  Depending on the device, the connection or traffic Yahoo! is receiving the reply from the web service might take too long and the OS displays that lovely "Something took too long" do you want to Force Close, Wait or Report dialog.  Most of the time, hitting wait will be good enough.  This is one of those things as a programmer that burns me as I know better, but since I don't deal with it often (or not at all for my 9-5 job) I just didn't think about it.

The other thing in this update should hopefully resolve the any future problems that Stu experienced.  Those problems frustrated him enough to leave this review.  Long story short, I found Stu's email from the purchase order and dropped him a line.  It seems (and I'm waiting for confirmation from Stu) that after the purchase of the dock extension is made 1) there's a lag between the purchase and the acknowledgement of the purchase 2) After the acknowledgement is received I'm not forcing a reload of the dock or any of the other stuff that needs to happen.  The simple fix for him should have been a Reboot or a Force Close of the app.

I believe that in the time between the purchase and the review, the app wasn't restarted and therefore the extension was never fully 'activated'.  The code change was relatively simple and hopefully other people who purchase the extension (and future extensions) will not have the same problems that Stu experienced.  My apologies to Stu and any other users who experienced the same kinds of issues.

Update Round-up

I've been neglecting the blog lately although I've been rolling out updates in a steady stream.  After the last post, I started digging into the static location feature.  Most of the people who sent email asked "can I just enter a zip code".  Well, that would work for the 70% of people that are in the US, but having received emails from all over the world (Chile, Australia, UK, Austria and Poland just to name a few), I didn't want a solution that would only work in the states (I try not to be a narrow minded American).   Recently, I discovered Yahoo! PlaceFinder.  In the same web service fashion as the weather, you generate a HTTP request with the information and it returns an XML file of location information. Some other additional nice things that go with it, is that if you provide it a common city name (Newcastle for example has 8 locations in the states, at least 3 in the UK and one in Australia).  It will return you a list of XML nodes that I used for a dialog.  You can also add in a locale which will only return the relevant locations for that locale.

I was more than halfway though adding the static location feature in when I noticed that I started getting a steady stream of force close reports.  It seems that I wasn't checking for a NULL value when getting the location which caused the app to crash.  Fixing the error was pretty simple, but I had already made a number of changes that would need to be rolled back to release just the bug fix.  I decided to just plow though the finishing static location as I thought that would be faster.  All said,  I ended up getting about 45 reports in week from the last update until I got the error fixed.

Not sure when version 1.0.0.12 was released, but it fixed the NULL force close issue and added in the static location which can be used Never, Always or when your location can't be found (back up).

Version 1.0.0.13 was pretty much a maintenance release.  Just a number of little bugs (again from Force Close Reports) and other odds and ends that just needed to be cleaned up.

Version 1.0.0.14 (the latest) big change was fixing a bug with the location loop up.  Emailing back and forth with Christopher D, I ended up discovering that my my location look up hierarchy wasn't working as expected.  The idea was to try to use this list (if enabled) to get the location :

1. Static Location
2. Location Based on IP Address
3. Get current location 
4. Get a cached location
5. Get back-up location
6. Location can't be found (give up)

The his phone had a problem was with getting the current location so it continued on to the cached location.  That was where I started to find all kinds of problems.  I ended up making a lot of changed to how the cached location works and what to do with it when it finds it.  All in all it was pretty much a product of the rushing to get the static location out to the market.

The other thing I wanted to note was that I did set up a Google+ page for the Desk Clock Plus.  I don't use Google+ on a personal level (or any other social media for that matter), so I'm really not sure how it's all going to work yet.  I figure, quick updates, support and I guess it is another way to get in touch with me.  It's an experiment so we'll see what happens with it.  

Location

I just quite didn't have time to post about yesterday's update and there's a bit of an overlap with the changes for today.  Yesterday's changes were some bugs reported by users.

The first one had to do with setting the Music button.  Apparently the ROM he's using has two different versions of Google Music installed.  It didn't matter which one he picked from the list, it always launched the older one.  I just had to adjust how I was finding and saving the intent.  While I'm thinking about the music button, over the life of Desk Clock Plus, there have a been a number of people who have emailed and said that music play {insert app here} doesn't show up in the list.  This has more to do with the other app than mine.  I'm trying to figure out what apps are registered to handle .MP3 files.


final String MP3_FILE = "/sdcard/media_api/music/SHORTMP3.mp3";
        Intent viewIntent = new Intent(Intent.ACTION_VIEW);
        Uri uri = Uri.fromParts("file", MP3_FILE, null);
        viewIntent.setDataAndType(uri, "audio/mp3");     
        Intent pickIntent = new Intent(Intent.ACTION_PICK_ACTIVITY);
        pickIntent.putExtra(Intent.EXTRA_INTENT, viewIntent);    
        startActivityForResult(pickIntent, MUSICPICKER);  


If the app isn't registered with the system to "view" a mp3, it doesn't show up in the list.  If anyone has a better way of doing this please let me know.

The other one which once again was reported by a pair of users with HP Touchpads saying that the display was way off.  Basically, the font sizes needed to be shrunk down the size of the font and weather icon to make everything fit.  Part of the major redesign when version 1.0 was released, all of the sizes, heights and widths were moved into one XML file.  This allowed me to very easily change everything to fit on to the Thouchpad.  Unfortunately, I didn't shrink the weather enough and the High/Low temp degree mark was pushed off the edge.  That was fixed in today's update...

So, the big thing for today's update is major improvement to finding your location.  Previously, I was relying on the last known location.  If I loop though everything and nothing knows where you're at then I'm forcing the device to update it's location.  I'm not 100% I'm happy with how all this works and it will probably be reexamined in the future.  Also, as it turns out the feature to use the IP address for the location wasn't working anymore (the web service I was using went away).  Fortunately, Yahoo had a replacement that I was able to use instead.

Finally, I also updated the "Immediate" time out to be more immediate.  As pointed out by Omniwolf in the comments, it was a little confusing / misleading.

Unless something comes up, I'm going to start on the static location tomorrow... Given the the changes I've made yesterday, I don't think that it's going to take me very long.

'Hide and Seek' or 'I'm not touching you'

I just pushed out version 1.0.0.8 to the market this afternoon.  The big new feature is for Scrolling Dock users, you can now swipe up or down on the dock area to show or hide the dock giving you a little more clear space to enjoy your background.  There are also settings for the dock to "auto-hide" after a time period which also includes immediately (well, 15 second delay).

Also as per a suggestion from a user, there is now an option to dim the dark clock immediately as well.  Once again it's really a 15 second initial delay...  I figured you needed a short delay just to show the transition from non-dimmed to dimmed.  The other thing that is new for the dark clock is that the proximity sensor is now being monitored.  Typically the proximity sensors is located by the speaker at the top of the phone.  If the clock is dimmed and you wave your hand close by the sensor, the screen will un-dim for 15 seconds.  I figured that would be good for someone who wakes up in the middle of the night and wants to check the time.  This way the screen is only lit up for a short time instead of the five minutes (or more) for when the screen is touched.

I also linked the proximity sensor the the hidden dock as well.  If the dock is hidden and you trip the proximity sensor it will open the dock for 15 seconds.  This feature is a little more of a novelty, but the code was all there for the dark clock to do it and this program is a learning tool for me, so why not put it in?

The next thing up is the much requested "static" location for the weather... now that I know how to handle this for international locations.

Sieben

The biggest update to the newest version is improved German strings.  Thanks to Johannes of Austria for reviewing and updating the XML files for me so they make a little more sense.  I've actually had a fair amount of purchases from Austria and Germany so hopefully this leads to more sales in that region... look at me using real fancy business lingo there!  

Speaking of Europe, the following comment was left in the market:

FAJNY, ALE Zawsze pokazuje temperature w st F bez wzgledu na ustawienia (GALAXY TAB)

Google Translate tells me that he said:

Cool, but always shows the temperature in F st regardless of settings (GALAXY TAB)

Which isn't 100% true, it was holding onto the last weather it knew (as per this update).  Since the first update was in Fahrenheit it stuck after the unit was changed.  Now when the weather unit is changed it will force a refresh to get the correct units.

I also fixed a minor run time error (causing a force close) that would happen sometimes where there were no images to be added to the pool. 

I'm working on a new feature for Scrolling Dock users that I'm hoping that I can get pushed out before Christmas, but I'm not sure that's going to happen...

Desk Clock Plus Version 1.0 Released

I am very happy to announce that I have published the changes for Desk Clock Plus that I've been working on for the past 6 months or so (remember, I'm only a lunch time developer so things take time).  So what's new?  That's a very big question....

The big thing is the addition of 'Application Extensions'.  The basic features of Desk Clock Plus (ie the features from the versions prior to this and what the 'Stock' clock app does) will always remain free.  I don't feel it's right for me (or legal) to charge for that*.  However I understand that there are some users who what more from this application that others don't need.  I think the dock configuration is a good example of that.  Some users have asked for this and I would image that others wouldn't care if they could do that or not.  So for one US dollar (or your approximate equivalent) you can purchase this extension for your devices.  As I said before, I don't see myself getting rich off of this application, but with the holidays coming up and more importantly the office holiday beer exchange I could use a couple extra bucks.

One more thing to note about this... I am a little sketchy about how the code for this works.  I'm pretty sure that I have it implemented correctly (the Pay-Pal system was much easier to work with and debug).  If you have a problem please contact me (or leave a comment) I don't want to leave someone who has paid for this (or is trying to pay) high and dry.  There are a couple of bonuses with this.

1. When you purchase this extension, it should work across all your devices that are connected to your account.
2. If you get a new phone or second device, you should just need to go in to the 'Purchase Extensions' screen for things to be reset internally, so you will not have to 'repurchase' this extension.

Now, on to the changes for this version:

• Scrolling Dock Button Extension - More documentation to follow, but the quick over view is that you can go into the settings --> Scrolling Dock Configuration to set the number of docks and to configure the docks.  Swipe the dock left and right to change docks.  Additionally you can long press a button change a button's:
• Action - internal to Desk Clock Plus
• Application - Launch a 3rd party app
• Clear - Clear action or application
• Add Dock -  Add a new empty Dock.
• Delete Dock - Delete the current Dock.
• Scrolling time / Weather - As a bonus for anyone who purchases an extension I also enable the feature of swiping the time or weather to change it to Digital Time, Analog Time or Weather (I'll add more 'windows' as I add more paid extensions.

• Reorganized Settings Screen - I grouped everything into sub-properties instead of the sub groups, this way you have smaller pieces to deal with at one time.  Everything is still grouped the same way, just organized a little different.
• Redesigned GUI - This should be pretty much be transparent to everyone, however some people should notice that fixes issues with 3 digit temperatures and long city state names.
• Translation - I changed how I translate this application into other languages.  I originally sang the praises of Androlate.  There was some problems with it.  First, it was pretty slow.  Second, it didn't handle multiple string files very well.  Third, it doesn't work anymore (it was only a beta anyhow).  For this go around, I used a Chrome Extension Android Multilingual translation tool.  I was very happy with it as it fixed the 3 issues above, however it doesn't handle string arrays, so those are still in English for the time being.  I also don't know if translations are any better (I'm going to check with other users)
• Background Images - I made a major change to how background images are handled that should drastically reduce the memory that I'm using and should reduce if not eliminate the out of memory issues you would get when loading images.  This has also worked its way into the slide show.
• Performance Boost - I think this comes from the changes for the background images, but the application seems to be running much faster which is always good!

Some other things to note, I updated everything on the Android Market page added a new featured graphic, new screen shots and re-wrote all the text.

Stats wise, I'm very happy with what Google is telling me (22k downloads, 5k installed and an average review of 3.7)

As always, what's next?  Probably over the next week or two it's going to be a number of updates for bug fixes as people start using the new version.  I might have some language updates depending on how well the chrome extension did.  I have a couple more ideas for the dock configuration extension that I want to implement.  I have a security issue that I need to resolve and then hopefully some more extensions.

As always, I'm very happy that 5,000 people are using this application, so if you experience any issues or have a suggestion, please email me!

*I am happy to note that everything except for the alarm & alarm screen was written by me.  The alarm code was taken from the Google source.

Major Release on the horizon...

Since May 23rd, updates for Desk Clock plus have been few and far apart (about 4 or 5 in those 5 months).  In that time, I've been working on a pretty major redesign of the main screen.  I haven't changed the look of the application all that much, but the underlying layout has changed a lot which will allow me to add new features quickly and easily.  It's also allowed me to shrink the size of the APK file by 300K or more.

The big feature is the ability to configure the dock (the five icons on the bottom of the screen).  You will soon be able to add more docks (swiping left and right) and add your own applications.  This however will will be an in-app-purchase to enable this new feature.  The in-app-purchase code was truly what had delayed the release of this version.  However, now that's been worked out, I should be able to add more in-app-purchases easily.

I'm happy with the in-app-purchase system that Google has provided (now that it's working).  I feel that it allows me to provide a free basic application for anyone to use and provide additional features for those people willing to pay for them.  I'm not looking to get rich and retire to the beach, but a little extra cash for beer money would be nice.

I also have a list of stack traces that I need to look at (force close and application not responding reports).  I'm not getting a ton of these, but I'm about 2-4 per week, so they need to be addressed.  For the most part it's better error catching for image loading (out of memory, image memory already cleared, etc).

As of 10-3-11 there are 19 Stack traces to look into...

If you happen to notice any other oddities or bugs, leave a comment!

Dark Clock Options

After adding the new feature of dimming the dark clock I had a couple of people email regarding it being too dark or that they didn't want it to dim at all.  I knew when I published that last update about a week ago that I probably should have just waited and added these two options.  So, just a little while ago, I pushed version 0.98.5.11 out to the market with these two new features:

• Dim Time Out -- Allows you to configure when if ever the Dark Clock will dim down.  Choices are Off, 5, 10, 15 or 30 minutes.
• Dim Level -- Allows you to configure how much the Dark Clock will dim out.  Choices are 20%, 30%, 40%, 50%, 60%, 70% or 80%.  The previous (and stock default) was 80%.  

Also, I'm happy to note that I've had a pretty decent bump in active installs over the past month (and specifically in the last week).  

It's crazy to me that I've got over one thousand new Active (installed on a device) users in about a week.

I'm close to having the last piece of the next major release done, so hopefully in the next week or two I'll have a  big release to write about.

Minor New Feature

I have been working on some major new enhancements to the Desk Clock over the past two months.  Primary development is about 75% done or so, and I've been pretty happy with the results.  I'm hoping to have it to my beta testers later this week.  In the mean time, I do have one new minor feature that was requested via the comments (although I would prefer to take suggestions via email).  There's now an option to turn on / off the "heartbeat" (blinking colon in the time).  Since this was a pretty simple request, I figured I would take some time and put that in.  The two new text strings are being translated and once that's done I'll publish it to the market.

I'm also on the verge of another milestone, 100 ratings.  All in all, I'm very happy and surprised with the usage.  Google tells me that I've had ~15k downloads and ~3.5k active installs.  It's running in countries all over the world (UK, Germany, India, Korea, Japan, Australia).  Now if I could only get more people to use that donate button...

This is not the update you're looking for...

Just a minor code rearrange to avoid a threading bug.

Last one... I swear... until the next one

I found two little bugs one dealing with the display on a larger phone (IE the new Droid X2) that was just setting the dock to center.  The other one was little more odd, I noticed that the slide show would sometimes display the local images when it wasn't supposed to.  This turned out to be an invalid default value, so I need to add a little more brains to making the choice to show local images or not for the slide show.

Seriously, going to start on the extensions... not fixing anything else... until I find something else that's broken.

EDIT: I almost forgot to mention the new 'Vintage Flag' them available for download from the theme browser.  I tried something different with the icons and I'm not 100% sold on them. 

Opinions welcome!

Milestone

Over the weekend at some point Desk Clock Plus reached the next plateau in the Android Market, over 10,000 downloads since I first released it mid December.  Obviously, that's not 'Angry Birds' type numbers, but it still it averages out to be about 55 downloads a day or about 1600 per month.  It's still kind of crazy to me that many people have tried out my app and 2000+ have it installed on their device. 

Just some quick notes about the last couple of updates:

• Re-sized the "night clock" for tablet devices, the font size should be the same as when it's in landscape mode.
• Apparently the colon color wasn't being set either... 
• Updated PayPal API after it caused a Force Close.
• After I re-localized the strings, I introduced a string bug that caused force closes on non-English devices (Désolé pour ça!)
• I'm also now doing some more work to verify that I have the correct intent when the music application is set, this came to light with the Google Music 3.0 launch.
• Andrew C. sent me screen shot of Desk Clock Plus on his Galaxy Tab and there was some screen layout issues.  The portrait view I know is fixed, I made some other changes to the landscape view, but I haven't been able to verify them, so please email me if your display is messed up for a 'large' tablet device.
• Gary M. requested that the weather not show NA when no weather info can be found.  This is an issue for him as he said: "I'm on holiday with no internet access".  The first thing I thought of was "a holiday with no internet access... that sounds really good right now!"
• Finally, there's an extra permission request for the Fine location (GPS).  I did this to increase the chance that I could find your location for the weather without having to resort to the IP address which is rather in accurate.

I don't think there's going to be very many if any updates for a while.  I'm going to be working on some in-app paid extensions, but more about that at a later time.

Thanks again to everyone who has downloaded and uses Desk Clock Plus!

Curse you PayPal!

I looked at the Developer Console this afternoon and I noticed I had a new Force Close report... Something inside of the PayPal API ran out of memory.  So, the last update have some error trapping around the PayPal stuff and I updated the PayPal code to the the latest 1.1.1 version.

I was also informed that I didn't re-size the night clock for the tablet screens.  That's also been fixed in the latest update.