This was a quick release to fix a long standing issue since 3.0 that I finally got a handle on, as I was getting several reports of the Current Location not working, which just didn't make sense. If the phone returns a set of GPS coordinates, then the weather providers should always return data for the nearest weather station, but this was failing, even though the coordinates had been obtained.
With the help of one user, we narrowed it down to World Weather Online, and to when running under Czech language, at which point I could replicate and fix it.
It turns out that many languages use the comma character ',' to indicate a decimal point, instead of the period character '.' which is used in the UK, US etc. When the phone was running under such a language, it was returning the GPS coordinates using a comma, so -13.48123 became -13,48123. Open Weather Map is able to handle both commas and periods for decimal points, but World Weather Online was always expecting a period, so it was failing and returning error messages.
This is now fixed, and v3.4 should now have the Current Location working fine under all different locales and languages for all Weather Providers.
Showing posts with label bug fixes. Show all posts
Showing posts with label bug fixes. Show all posts
Thursday, June 11, 2015
Tuesday, June 2, 2015
CliMate Animated Weather Widget version 3.3 released!
The new version 3.3 of cliMate is now available!
Featuring:
Featuring:
- New Stonehenge Theme!
- All forecast dates now correctly localized
- Added moon rise and moon set in Main Screen night conditions
- Added option to hide contrails
- Added option to hide Date
- Added choice of windspeed units
- Improved layouts when widget resized to extreme widths
- Bug fixes for rare crashes
- Bug fix for countries that have multiple cities with the same name
So what's next? Already started on a Chinese Ink Painting style theme which looks promising, then I think its about time for a City theme.
Also I'm toying with the idea of an alternate forecast view on the main screen, perhaps for the next 12 hours, arranged in a clock style circle, and animated of course. You could then swipe between that detailed forecast for today, and the general forecast for the next 5 days.
Tuesday, May 26, 2015
Version 3.3 nearing release..
So I have been hard at work on the next version of cliMate, with a lot of minor bug fixes but several notable improvements.
First off, a brand new Stonehenge theme for the widget, which looks really dramatic and striking:
First off, a brand new Stonehenge theme for the widget, which looks really dramatic and striking:
Then a new Moonset and Moonrise animation and time indicator on the main screen, which is shown instead of the sunrise and sunset animation during night time scenes:
Then a whole bunch of small fixes for things:
- Ensuring the dates on the forecast are shown using the correct local settings, e.g. 5/26 in the US versus 26/5 in Europe
- Fixing the layouts when the widget is stretched extremely wide
- A range of crash fixes
- Fixes for forecasts where the Chance of Storm condition was used instead of Thunderstorm
- Improved animation on Thunderstorm forecast animation
- Added the ability to hide today's date
- Added the ability to hide the jet contrails on the Clear and Partly Cloudy conditions
I had the occasional report that the clock shown on the widget is not syncing up with the phone's actual time, but until now I have not been quite sure how to deal with it. So also trialing a new method of determining when the screen is switched on and hence when to update the clock.
A lot of testing to go, and then should aim to release maybe next week.
Wednesday, April 15, 2015
Quick cliMate 3.2 Bug fix
Well, that was annoying.
No sooner had I published cliMate 3.0 then I discovered 2 annoying bugs.
For World Weather Online I was retrieving the Moon Rise and Moon Set data, in preparation for the next release when I will use them to add a moon animation.
However, I had assumed that data would always be available, and so when this morning it produced a "No Moonset" condition instead of a time for a particular location, it failed, making it impossible to update the weather or add a new widget for that location.
Also discovered that when searching for a city name, it was ignoring the country code on the returned results. This was found due to a user in Rome, with a widget with the city name of "Roma". When updating, it was bringing back data for the first Roma it found, which was in Australia, rather than Roma, Italy. So the user was seeing an Australian time-zone and Australian weather.
Now the country code is being appended to the retrieval, and the correct city and time-zone is being returned.
A new version 3.2 has these fixed.
No sooner had I published cliMate 3.0 then I discovered 2 annoying bugs.
For World Weather Online I was retrieving the Moon Rise and Moon Set data, in preparation for the next release when I will use them to add a moon animation.
However, I had assumed that data would always be available, and so when this morning it produced a "No Moonset" condition instead of a time for a particular location, it failed, making it impossible to update the weather or add a new widget for that location.
Also discovered that when searching for a city name, it was ignoring the country code on the returned results. This was found due to a user in Rome, with a widget with the city name of "Roma". When updating, it was bringing back data for the first Roma it found, which was in Australia, rather than Roma, Italy. So the user was seeing an Australian time-zone and Australian weather.
Now the country code is being appended to the retrieval, and the correct city and time-zone is being returned.
A new version 3.2 has these fixed.
Monday, April 8, 2013
More bounce to the ounce..
So, finally fixed the issue with motion detection on Galaxy Note 2 phones.
The shake to refresh and bouncing cube didnt work at all.
Turns out it is abug in Samsungs Firmware, the shake events were all being tagged as unreliable, so were being discarded.
I fixed it to ignore the unreliable tag, so they are now being let through and the Note 2 has its bounce back!
Version 3.2 on the Google Play store now..
The shake to refresh and bouncing cube didnt work at all.
Turns out it is abug in Samsungs Firmware, the shake events were all being tagged as unreliable, so were being discarded.
I fixed it to ignore the unreliable tag, so they are now being let through and the Note 2 has its bounce back!
Version 3.2 on the Google Play store now..
Saturday, June 9, 2012
Bug Fix Version 2.6
Almost finished the Motion Detection stuff, but had to release a quick bug fix version, too many Force Close issues popping up which I needed to sort out first.
Version 2.6 is on the Market/Play Store right now. It should fix all the Force Close problems that a few people have reported.
Then on to the end of Motion Detection!
Version 2.6 is on the Market/Play Store right now. It should fix all the Force Close problems that a few people have reported.
Then on to the end of Motion Detection!
Thursday, January 12, 2012
Photo Cube Improved Image Quality
So, on to the Photo Cube enhancements. The first requirement was made more obvious when using the larger screen of my tablet, simply put the photos and backgrounds don't look as good as they should.
The reason for this is that a while back, I had to change to a new method of cropping a photo, so that it worked on all devices. The method I used, whilst working far more reliably than the old method, resulted in a cropped image that was not of the highest quality, because the scaling method was not so good. This was particuarly noticeable when using an image smaller than the crop size, which is more likely on backgrounds.
In addition, I was using the same method when scaling the images so that they fit inside the photo frame the user has chosen, leading to obvious artifacts and what appears like crosshatching on same frames.
Had time to look at this now, and figured out a better scaling method which is a little slower, but results in a much higher quality image. The performance hit is only noticeable when changing photos, so the Cube still spins a fluidly as ever, but now the images look far better.
Compare before on the left and the improved version on the right. See the difference in the background quality, and compare the edges of the face of the photo:
And here when a frame is used, again the old on the left and the new on the right, see how the face within the frame had a funny checkered effect on the left image which has now vanished from the improved version on the right:
This means that Photo Cube gets higher quality images with no extra memory used. This will be released next week along with a minor bug fix after I have done a lot of testing to ensure it will work on all devices.
Finally, the Samsung Tab really shows off the quality of some of the frames, for example, I didn't realise how nice the Antique frame style was until I saw it in all its glory on the tablet... love it!
The reason for this is that a while back, I had to change to a new method of cropping a photo, so that it worked on all devices. The method I used, whilst working far more reliably than the old method, resulted in a cropped image that was not of the highest quality, because the scaling method was not so good. This was particuarly noticeable when using an image smaller than the crop size, which is more likely on backgrounds.
In addition, I was using the same method when scaling the images so that they fit inside the photo frame the user has chosen, leading to obvious artifacts and what appears like crosshatching on same frames.
Had time to look at this now, and figured out a better scaling method which is a little slower, but results in a much higher quality image. The performance hit is only noticeable when changing photos, so the Cube still spins a fluidly as ever, but now the images look far better.
Compare before on the left and the improved version on the right. See the difference in the background quality, and compare the edges of the face of the photo:
And here when a frame is used, again the old on the left and the new on the right, see how the face within the frame had a funny checkered effect on the left image which has now vanished from the improved version on the right:
This means that Photo Cube gets higher quality images with no extra memory used. This will be released next week along with a minor bug fix after I have done a lot of testing to ensure it will work on all devices.
Finally, the Samsung Tab really shows off the quality of some of the frames, for example, I didn't realise how nice the Antique frame style was until I saw it in all its glory on the tablet... love it!
Tuesday, January 10, 2012
Photo Cube now supports Honeycomb and ICS!
Well, I'm very happy to announce this maintenance release of Photo Cube version 1.22, which now fully supports Android 3.x and 4.0, Honeycomb and Ice Cream Sandwich respectively.
The main issues were that the Settings with icons were not appearing correctly under these latest versions of Android, turns out that the custom Setting preferences were being hidden by default, so a very simple switch turned them back on.
There was also a few annoying issues where the settings were not being updated correctly when returning from choosing a new image for a cube side. All sorted now.
And voila! Under 3.2, on my Galaxy Tab 7 Plus:
So all good now, Version 1.22 is on the Market as I write this.
On to the long awaited enhancements now!
The main issues were that the Settings with icons were not appearing correctly under these latest versions of Android, turns out that the custom Setting preferences were being hidden by default, so a very simple switch turned them back on.
There was also a few annoying issues where the settings were not being updated correctly when returning from choosing a new image for a cube side. All sorted now.
And voila! Under 3.2, on my Galaxy Tab 7 Plus:
So all good now, Version 1.22 is on the Market as I write this.
On to the long awaited enhancements now!
Thursday, December 29, 2011
Spinning madly, out of control...
Well, it has been a while. So busy with my other project, but in testing that out on other phones discovered that Photo Cube still behaves strangely on with regard to the spinning when you swipe left and right.
On the Go Home Launcher and on the Galaxy S2 Touchwiz launcher, things are not quite right when you pan over the far left or far right of the available home screens, it results in the cube still going into a constant spin. On the Desire HD latest update, the cube doesn't do any extra spin at all when you pan left or right.
Turns out this is due to the way different phones interpret the wallpaper offsets and what they end up sending to the Android WallpaperEngine "onOffsetsChanged". In short, I can no longer rely on the scroll position of the current home screen to work out how much extra to spin the cube when panning left and right. HTC latest Sense 3.0 uses a carousel idea which completely ignores that, so you can't pan your wallpaper at all, you are left with a fixed background. That is frankly, stupid, but it is what it is.
So I have changed the extra horizontal spinning of the cube to be completely controlled by the user touch commands. This gives me great control, and has completely done away with occaisonal situations where the cube suddenly freaks out due to odd numbers being sent to "onOffsetsChanged", and has allowed me to control how much it spins and even give it a nice deceleration. I might even turn it into a Setting.
Other upsides, you can now definitely see the "Back" picture a lot more often, this used to be pretty hard to get to appear, because the extra rotation was linked to the home screen. Now it is controlled by the user, so the appearance of the pictures are a lot more random.
Will just do a bit more testing on my friend's S2 to make sure all is well there, then will be off to the Market!
On the Go Home Launcher and on the Galaxy S2 Touchwiz launcher, things are not quite right when you pan over the far left or far right of the available home screens, it results in the cube still going into a constant spin. On the Desire HD latest update, the cube doesn't do any extra spin at all when you pan left or right.
Turns out this is due to the way different phones interpret the wallpaper offsets and what they end up sending to the Android WallpaperEngine "onOffsetsChanged". In short, I can no longer rely on the scroll position of the current home screen to work out how much extra to spin the cube when panning left and right. HTC latest Sense 3.0 uses a carousel idea which completely ignores that, so you can't pan your wallpaper at all, you are left with a fixed background. That is frankly, stupid, but it is what it is.
So I have changed the extra horizontal spinning of the cube to be completely controlled by the user touch commands. This gives me great control, and has completely done away with occaisonal situations where the cube suddenly freaks out due to odd numbers being sent to "onOffsetsChanged", and has allowed me to control how much it spins and even give it a nice deceleration. I might even turn it into a Setting.
Other upsides, you can now definitely see the "Back" picture a lot more often, this used to be pretty hard to get to appear, because the extra rotation was linked to the home screen. Now it is controlled by the user, so the appearance of the pictures are a lot more random.
Will just do a bit more testing on my friend's S2 to make sure all is well there, then will be off to the Market!
Monday, November 21, 2011
New Version 1.20
New version 1.20 is live on the Android Market now.
Just two things new in this version, a fix for a very rare bug when choosing a background colour, and a fix for a more common issue on some 3rd party Home Screen launchers, such as the Go Launcher, where changing device orientation would on occasion cause the cube to "freak out", as one user delightfully put it, spinning madly fast until you swiped the screen to stop it.
After some investigation I really cant see why Go Launcher is causing it to freak out to start with, but at least I can treat the symptom and simply stop the mad spin as soon as it is about to start, before the user will notice anything untoward.
In other news, working hard on my next project, it is coming on so well I really wanted to get that out by the end of the year then I can concentrate back on Photo Cube and finally get to all the new features I have been planning. The new Widget really is a thing of beauty... and the top secret killer feature works wonderfully...
Just two things new in this version, a fix for a very rare bug when choosing a background colour, and a fix for a more common issue on some 3rd party Home Screen launchers, such as the Go Launcher, where changing device orientation would on occasion cause the cube to "freak out", as one user delightfully put it, spinning madly fast until you swiped the screen to stop it.
After some investigation I really cant see why Go Launcher is causing it to freak out to start with, but at least I can treat the symptom and simply stop the mad spin as soon as it is about to start, before the user will notice anything untoward.
In other news, working hard on my next project, it is coming on so well I really wanted to get that out by the end of the year then I can concentrate back on Photo Cube and finally get to all the new features I have been planning. The new Widget really is a thing of beauty... and the top secret killer feature works wonderfully...
Thursday, October 27, 2011
Photo Cube Version 1.19 Released
Due to the usual Market incompetency, I had to skip some version numbers. Anyway, version 1.19 is on the Market now. It fixes a couple of minor yet annoying issues, and paves the way for some forthcoming goodness.
Firstly, there was an annoying situation where when you double tap on the Wallpaper to launch the Quick Size and Position screen, it would instead bring up the main Photo Cube Settings screen. That is now fixed, it always brings up the Quick Size and Position.
I added a bit of animation to that screen also, the top and bottom control bars now slide in nicely.
More importantly, there had been a number of reports of users who couldnt get the Background Colour Picker to work because they didnt see how to select the final colour. In some cases that was because it was just a bad design, it uses two coloured rectangles showing the old and new colours, which you had to tap on, which was not obvious. In other cases, it was because in Landscape more, those rectangles didnt appear at all, they were hidden off screen.
So now I changed it to use proper OK and Cancel buttons, and made sure they are visible in both Portrait and Landscape mode:
Firstly, there was an annoying situation where when you double tap on the Wallpaper to launch the Quick Size and Position screen, it would instead bring up the main Photo Cube Settings screen. That is now fixed, it always brings up the Quick Size and Position.
I added a bit of animation to that screen also, the top and bottom control bars now slide in nicely.
More importantly, there had been a number of reports of users who couldnt get the Background Colour Picker to work because they didnt see how to select the final colour. In some cases that was because it was just a bad design, it uses two coloured rectangles showing the old and new colours, which you had to tap on, which was not obvious. In other cases, it was because in Landscape more, those rectangles didnt appear at all, they were hidden off screen.
So now I changed it to use proper OK and Cancel buttons, and made sure they are visible in both Portrait and Landscape mode:
So what is in Development?
I had a nice request for a screenshot capability and being able to upload the image to Facebook. This is now working, it can capture and share the image to Facebook, WhatsApp, Email, MMS, in fact anything on your phone which handles an image. But I need a better interface to be able to launch the capture, so I want to add more features to the Quick Settings, instead of just having Size and Position I want to add options for Screenshot, Frames, Effects and Rotation, all shown as an overlay above the wallpaper so you can see the changes in real time. Working on that at the moment.
After that:
- Maybe a new rotation mode, perhaps something more random.
- Then the long awaited Presets enhancement.
- Finally the Album mode, where you choose an album and it will automatically show pictures from that directory with no further action required from the user. A bit of clever cropping and maybe face detection will be required for that.
- The ability to browse a picture in your Gallery or anywhere and then automatically add it to a Photocube side, via a Send To long press command. Very slick..
And of course I am still doing work on the Weather Widget, which is coming on well.. maybe early next year for an initial release.
Friday, September 23, 2011
Photo Cube 1.16 Released
New version finally released. Just a few bug fixes, there was a very annoying issue for some users when the pictures selected didnt cover the entire face of the cubes, just sat in the corner.
I changed the method of selecting and cropping the pictures to that used by the Background Image selector, which is less pretty but a lot more reliable. That seems to have fixed the issue for the users reporting the issue.
I also changed the boring default abstract background to a nice natural scene, a bit more restful on the eyes.
Then need to do some promo images for launching Photo Cube on the Vodafone App Shop in Europe.
I'm still working hard on the Weather Widget which will be totally unique, literally like nothing else on the market. Watch this space..
I changed the method of selecting and cropping the pictures to that used by the Background Image selector, which is less pretty but a lot more reliable. That seems to have fixed the issue for the users reporting the issue.
I also changed the boring default abstract background to a nice natural scene, a bit more restful on the eyes.
Then need to do some promo images for launching Photo Cube on the Vodafone App Shop in Europe.
I'm still working hard on the Weather Widget which will be totally unique, literally like nothing else on the market. Watch this space..
Monday, July 18, 2011
New Version 1.14
Thanks to a kind customer who emailed me I was able to fix a very annoying yet rare bug, and uploaded version 1.14 last night.
When running Photokube the code draws the background with the OpenGL command glDrawTexiOES, then draws the cube and panels. However on the Android emulator on my pc, the background has always been displayed in front, obscuring the cube and the floating panels, despite me asking it to be drawn behind the kube.
Since it has always appeared correctly on all the phones I have tested, I assumed that it was some sort of bug with the emulator and Open GL. As no one mentioned the problem in the market, and after searching for similar issues on Google I found a few similar complaints about the emulator I came to the conclusion that it was the emulator at fault.
However, Tim emailed me to let me know he had been having the same issue on his phone, so I was forced to revisit it. Thinking about it again, it was really pretty unlikely that if it was an emulator issue, I would only have found a few references to it, it would have been a known issue.
Anyway, more Googling of glDrawTexiOES and z-order depth brought up quite a few people having issues in general, so I was able to narrow it down to Depth Testing in OpenGL, specifically the GL_DEPTH_TEST.
Previously I had depth testing enabled all the time, which seemed sensible, but what seems to fix the issue on the emulator and also work on phones is disabling Depth Testing when drawing the background, then immediately enabling it again before I draw the cube and panels. This doesn't seem logical to me to be honest, I can see why it is needed for drawing the cube, so the panels appear behind the cube, but I don't see why leaving it enabled also doesn't work for the background. Still, now it works for Tim and hopefully any others who had similar issues.
I don't really have the time at the moment but if I get the chance I will research it in more detail so I can really understand why it behaves this way.
Anyway, hope that solves the issue for anyone else. New version on the Market now.
When running Photokube the code draws the background with the OpenGL command glDrawTexiOES, then draws the cube and panels. However on the Android emulator on my pc, the background has always been displayed in front, obscuring the cube and the floating panels, despite me asking it to be drawn behind the kube.
Since it has always appeared correctly on all the phones I have tested, I assumed that it was some sort of bug with the emulator and Open GL. As no one mentioned the problem in the market, and after searching for similar issues on Google I found a few similar complaints about the emulator I came to the conclusion that it was the emulator at fault.
However, Tim emailed me to let me know he had been having the same issue on his phone, so I was forced to revisit it. Thinking about it again, it was really pretty unlikely that if it was an emulator issue, I would only have found a few references to it, it would have been a known issue.
Anyway, more Googling of glDrawTexiOES and z-order depth brought up quite a few people having issues in general, so I was able to narrow it down to Depth Testing in OpenGL, specifically the GL_DEPTH_TEST.
Previously I had depth testing enabled all the time, which seemed sensible, but what seems to fix the issue on the emulator and also work on phones is disabling Depth Testing when drawing the background, then immediately enabling it again before I draw the cube and panels. This doesn't seem logical to me to be honest, I can see why it is needed for drawing the cube, so the panels appear behind the cube, but I don't see why leaving it enabled also doesn't work for the background. Still, now it works for Tim and hopefully any others who had similar issues.
I don't really have the time at the moment but if I get the chance I will research it in more detail so I can really understand why it behaves this way.
Anyway, hope that solves the issue for anyone else. New version on the Market now.
Monday, July 11, 2011
Back from Blighty...
So finished my holiday.. had a nice time in England.
While I was away I released 1.10 and 1.11, to fix some issues with the quick Size and Position screen. Also optimised the memory of the textures used to take advantage of the fact that the Background image is now stored in its own texture, usefully saving 512k memory at runtime.
Just discovered another bug, if you triple tap on the wallpaper then you get the Size and Position screen correctly but the Loading message doesnt get removed, need to fix that. Triple tapping is not that common in general, but if you are playing around with the floating panels, tapping them to make them disappear, it can come up pretty regularly. So will fix that soon, then concentrate a little on another project before starting work on the Album mode and Presets.
While I was away I released 1.10 and 1.11, to fix some issues with the quick Size and Position screen. Also optimised the memory of the textures used to take advantage of the fact that the Background image is now stored in its own texture, usefully saving 512k memory at runtime.
Just discovered another bug, if you triple tap on the wallpaper then you get the Size and Position screen correctly but the Loading message doesnt get removed, need to fix that. Triple tapping is not that common in general, but if you are playing around with the floating panels, tapping them to make them disappear, it can come up pretty regularly. So will fix that soon, then concentrate a little on another project before starting work on the Album mode and Presets.
Monday, July 4, 2011
Bug fix release 1.10
Discovered several annoying bugs regarding the quick Size and Position screen.
Firstly if you haven't loaded that quick settings screen for a while, it sometimes can take a few seconds to come up after you have double tapped the screen. Hence added a "Loading..." splash screen, to indicate that it has registered your double tap and is on the way. This disappears once the screen is loaded. This should help confusion whether your double tap was effective or not, if you see the loading screen, it was effective.
Secondly, quite a few bugs surrounding the double tap event itself. If you tap and slide the screen multiple times to change home screen, that could be interpreted as a double tap, which of course we don't want. Also, if your second tap happens to be upon an icon, this will launch that app, so I have to ensure that the second tap doesn't also launch the translucent settings app on top of that newly launched app. I think I got most of them, but there may be another lurking there.
I wanted to get a new version out though to fix the most annoying sliding screen bug, so 1.10 is on the market as I write this.
Firstly if you haven't loaded that quick settings screen for a while, it sometimes can take a few seconds to come up after you have double tapped the screen. Hence added a "Loading..." splash screen, to indicate that it has registered your double tap and is on the way. This disappears once the screen is loaded. This should help confusion whether your double tap was effective or not, if you see the loading screen, it was effective.
Secondly, quite a few bugs surrounding the double tap event itself. If you tap and slide the screen multiple times to change home screen, that could be interpreted as a double tap, which of course we don't want. Also, if your second tap happens to be upon an icon, this will launch that app, so I have to ensure that the second tap doesn't also launch the translucent settings app on top of that newly launched app. I think I got most of them, but there may be another lurking there.
I wanted to get a new version out though to fix the most annoying sliding screen bug, so 1.10 is on the market as I write this.
Subscribe to:
Posts (Atom)










