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. 

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.

How to get a bug fixed...

I've been meaning to do a post like this for a little while and with the last update, this seems to be a good time.

If something happens inside the app that causes it to crash, you'll probably see a window like this:

The important thing to do is hit that "Report" button.  I think that a lot of users don't even consider that as think it probably goes off to Google and into a list of a million other reports never to be read.  That certainly is the case for the Microsoft windows version of this screen.  However with Android, these reports come to developer and can be seen in the development console:

The 4 that I have outstanding are minor and happen infrequently, I've left them as "New" so I don't forget about them.  Each of the reports contain a stack trace (what functions were called before the application crashed).  For example, the bug that was fixed for Monday here's part of the stack trace:

Even if you don't understand everything (I don't always either), the important pieces are:

• The app version
• When it happened
• How often it happens
• What happens (a null exception in this case)
• Where it happens (class name, file and most importantly line number)

The other bit of information that comes along is provided by the user.  When you tap the Report button you're given a chance to include a note of what you were doing (you could also include beer suggestions or your thoughts on Hockey or Soccer teams).  These notes are optional and not nessacary, but the user who sent in this report also sent a good note on what they were doing.

attempted long press set action on second dock of 4th icon to Music App

This defiantly helps me re-create the bug, but wasn't as important in this case.  Looking at the code I realized what had happened on line 512.  I had a check to make sure that I wasn't going to go out of bounds on my list of buttons and if something caused the buttons to go out of bounds, I cleared everything, displayed a toast message and reloaded the list of buttons.  As far as I can tell that's what happened to this user and instead of exiting when the reload was called it continued on (I missed an exit call).  Which then caused the null error.  The fix for this was very simply to add the exit call.

Hopefully this gives a little insight on how things work behind the curtain.

Hello IT...

While I do prefer that user's email me with issues, I do keep an eye on the comments for bugs and feature requests.  About two weeks ago this was posted:

Not working getting error "Update Location…"

I really didn't think too much about it as there wasn't much to think about (due to the lack of information) other than the XML string issue.  Although later that week I got another similar comment:

No longer works "Updating location" then won't open :( ... Droid Bionic

This started to raise some red flags.  I even got an email from a user who had helped with with issues previously asking about known issues.  I checked the error logs and  there was nothing... I couldn't think of what I would have changed that would cause any kind of problem like this.  Then on Saturday I understood exactly what both of these users were talking about.  I plugged my phone it to the wall outlet and turned on Desk Clock Plus manually.  After touching the icon, nothing happened and then I got the toast message "Updating location..." and then Forced Closed.  I tried it again and still nothing... I pulled a magnet off the fridge and found the magnetic dock switch (which worked).  I tried to think of what was wrong and what I could do and I thought rolling back to version 18.  After some WTF moments, I drew on my years of IT support and all of my learning from my advanced technical degrees.  I turned the phone off and on again...

Yes, that did resolve the problem.  What burns me though, is that it did fix it.  I was under the impression that things like this shouldn't happen in the *NIX environment (Android is based on the Linux kernel and keep in mind I'm not a Linux/UNIX guy).  The only thing I can think of is that the SD card was in some odd state or something as I know that other users have had issues with the themes not working.

마스터 (Eighteen)

It's nice when people help out... much like Johannes did for German,  Jonathan volunteered to review the Korean strings.  Hopefully that will help him and the other 45 people that are using my app in Korean.  


Besides that, a minor fix to the night clock that might have been causing it to force close when dimming.  Also, Martina from Munich requested a one minute update on the background image.  I think that it's a little short, but as it was a very simple change I added it in.


I'm also hoping that this update might fix Don and Scott's docking issue (even though there was no change).  


I'm still looking into the alarm issues and I have at least one more thing to look at for omniwolf (Sorry to leave you hanging mate!)

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...

Next Batch

Version 1.0.0.4 is now in the market.

Once again just a couple of fixes and enhancements

• Dark Clock (Screen Saver) - I got an email from a user saying that the night clock no longer dimmed, but it did dim, just so very little  you couldn't tell.  When I incorporated the better dimming for the "Smoke" level on the main screen I changed it to take an integer (ie 30%) while the Dark Clock's dim was expecting a decimal (ie .30).  Yes it was very Micheal Bolton of me to misplace the decimal...
• Dark Clock - I added an option to keep the screen on when in the Screen Saver mode.  Some people want it on, others want it off, so now there's an option.
• Strings - I've had an on going error log pop up that I haven't been able to put my finger on.  It turns out (or so I believe) that when I did the string translation the substitution strings (minutes %s until alarm) got messed up and I think were causing issues with setting alarms.  I've fixed all of those and I'm hoping that goes away.
• Translation - Sergio from Chile contacted me awhile back saying that my Spanish translations were off and that some did not make sense (this has happened before).  He offered to fix things up and those are now in place (there are some new strings that haven't been reviewed yet).  I wanted to tell Sergio 'Gracias' for his help!  This prompted me to put a link to this page asking for translating for other languages.

This leaves me with one other big bug left with the purchasing service, which someone left a note in the report that "wasn't even doing anything with it." which might mean that something is just not being set or caught correctly...

After knocking that issue out I've got these two enhancements for the dock extension:

• Launch a specific app when removed from the dock.
• Tablet Dock Mode by this I mean stretch the dock the entire width of the device and use a gallery for the icons.

Quick Fixes

Version 1.0.0.3 is in the market.  Just a couple of things fixed:

• Picasa - This probably didn't effect too many people, but it was a bug when you had Picasa images chosen for the background, but didn't choose any Albums
• Weather and Location - I'm now holding on to the weather and location information so I don't have to look it up all the time.  This should make rotation and weather update refreshes faster.

Fixin' Bugs

I've kept a close eye on the Android Application Error logs to figure out where the problems are and fix everything as quickly as possible.  As I eluded to on Monday when I first released version 1.0 there was a lot of code churn and as I stated on the Market page:

There were a large number of changes for this release.  If you have problems please help me by emailing me so I can help you!

I've been working with a number of users to identify the bugs and Johannes in Austria I was able to identify a pretty nasty force close bug and get an update to the market later that day.  He was also helpful in tracking down another issue with updating the number of docks from the preference screen.  I was also happy to get comments (cause that means that someone is actually reading this) from two users in Monday's release post (and my reply is in there as well).  There's those two ways of contacting me and I'm probably going to break down and setup a Twitter account and start using Google+ when things settle down.   Leaving a comment like... Oh I don't know... something like "Update sux Update is full of bugs" (Ahem Lacy*) that doesn't do any good and makes me go all ranty.   Bob S thank you for driving home the idea that if leave me a comment things get fixed!

Here's the list of thing that I have fixed in version 1.0.0.2

• Force Close on start / orientation change - This was actually fixed late Monday in version 1.0.0.1 and it must have done the trick as all the force close reports that have come in and are still coming in are from version 1.0  This was basically a Layout redraw issue, it was trying to set the dock buttons, but due to a layout reload the button was there.
• Force Close when changing dock count - This one was caused by me doing VB for work and then Java at lunch...slight differences in the languages and how they work.
• 24 Hour AM/PM - Regardless of the setting the AM/PM was always being set to visible.
• Plugged-in Indicator - Same as above the indicator was always on
• Heartbeat transition - This got lost in the GUI redesign and now fades in and out like before.
• Disable Heartbeat - Ummm... yea didn't put the code in to do this... I found it when I was looking at the transition.  
•  Weather Issues - I've had a couple emails about the weather not working.  From what it sounds like it's having a problem getting the location to find the weather.  I looked at the code and it's exactly the same as the previous version.  However, there were some differences with the permissions which might have been the problem.  If that's the problem I must be trapping the lack of permissions correctly, but not finding the location (which sounds right).  I'm hoping that this fixes things, but I haven't had any problems with the weather loading... Did this get fixed?

Known issues that are still out there (from what Google tells me):

• Null Pointer in the get Picasa images - not sure if this is the featured or your images.
• Null Pointer in the billing service - this is google code for the extension purchase (which pisses me off).  If you get a force close when purchasing the extension, put your name in the log and email me.  

I'm sure there's more, but I don't have the time to list them now.  

*If it's this Lacy then it might be ok...

Update Bomb

I've been rather busy with all three of my projects lately... I was finally able to get everything done and taken care of and I just got done pushing updates to all of them.  But first a little rant...

I personally am very happy with my version of the Desk Clock.  It works very well for me on my original Droid.  It works well, on the Droid 2 and on the HTC incredible (according to my cousin and sister).  I've also have a co-worker using it on his Droid X.  However there are some people who are still having issues with it force closing on start.  That sucks.  I want my software to work for everyone.  The problem is the phones that they say that it doesn't work for... I don't have access to.  Beyond that, I can't say if this is some specific to the phone or the user or a combo of the two.  Additionally, If you going to bitch about it not working, HELP ME, HELP YOU!.  Fill out the Force Close Report!!!  I'll get a stack trace that should help me figure out what the problem is.  I guarantee that it will take less time than going back to the market and complaining there...

I feel a little better... sorry about that.

Desk Clock Pro: I changed how I get the "default background" and I suspect that was the cause of some of the problems or at least I can guess cause nobody fills out the Force Close Report (sorry about that)... The added bonus is that now the Live Wall papers will show through which is pretty cool.  It turns out that I was doing too much work and in most cases if your doing too much work then your doing it wrong.

I still don't know what the problem is with some people and the music button.  It tries to find the default first and then if it can't it should display a list to choose from.  I'm planning on putting an option in the settings for the user to choose which one they want to use.  I'm hoping that speeds things up a little and reduces some of the problems (or at least helps me find the source of the problem.

Launch Bar Pro:  I've learned a lot since I started programming for the Android OS six months ago.  Some of that has been slowly working it's way into the Launch Bar.  I was able to reduce the amount of work it was doing and therefore made the loading and scrolling features a lot faster.

Launch Bar:  The big thing that I'm excited about is that you can now unlock the Pro version from the basic version buy purchasing it though PayPal for $1 USD.  What's nice is that if you are running both versions, you can unlock the free version and basically be running two different Pro widgets!

I don't think I'm going to get rich off of any of my applications, but any extra scratch helps at the end of the month!

Looking forward, I 'm probably going to change out the weather icons for the Clock in the near future.  I talked about a menu option of the musing and I think I'm going to get picasa support for the slide show / backgrounds.

Until then...

Coming Attractions

Just a quick update...

I've been working on a semi radical change to the Launch Bar for a couple weeks now. I have the basic version completed and am working on a similar update for the Pro version. However, I'm hitting a little bit of a learning curve when it comes to some more advanced GUI elements. I'm hoping to be able to publish the updates early next week.

This update will include:

• A new GUI for the configuration screens
  
• Removed the icon size slider (for now)
  
• A major speed increase when launching the configuration screen
• A major speed increase when changing the orientation of the device

Also, I've seen a couple of comments regarding the basic Launch Bar not working or missing icons (specifically messaging) on certain phones. Typically these have been HTC devices with the Hero, Desire and EVO being the ones I know being problematic. I have good idea of what the problem is, but with out a phone to test on I can't verify it or write a fix. I've been trying to build the HTC source code so I can use it in the emulator, but haven't had time to really work on that. If you are running the basic version and have seen the missing button issue please send me an email. I have a debug program that I'll send you that should help me out. I can be reached at rmueser (at) gmail (dot) com