Osplay 1.0.6… Er… 1.0.7

I released Osplay 1.0.6 1.0.7 today. 1.0.6 had a problem on some systems with upgrading the database which was fixed by 1.0.7. This most notably can accept the VIEW Intent, so audiobooks/podcasts can be opened from other applications in Osplay. I threw in album art as well as a bunch of miscellaneous bugfixes. Still $5 on the Android Market.

10 Responses to “Osplay 1.0.6… Er… 1.0.7”

  1. Allan says:

    Osplay sounds like just what I’ve been looking for. Is there any way to get it if you live in a country that only have access to free apps on Android Market?

  2. admin says:

    It’s getting there. For now, there’s a Trial version on the Android Market only for the countries where apps are sold to avoid taunting people. I’m thinking about opening that up. I did put in code that would support locking to a single device/subscriber, but I haven’t created a web interface for buying Osplay. If you send me an e-mail we can come to some arrangement. The only serious issue is I haven’t _automated_ taking payment or building the APK.

  3. Allan says:

    Thanks for the offer but Google finally announced that they will be opening up Android Market in my country within the coming weeks! I hope Osplay is available in all locations that are on the Android Market?

  4. admin says:

    Yes, and I’ve updated the Trial to be available in all such locations as well. Thanks for buying!

  5. Allan says:

    I’m sorry to say this but I had to cancel my purchase of Osplay after trying it out. The variable speed worked flawlessly but I have massive problems with the app hanging and Android telling me that Osplay is not responding.

  6. admin says:

    At what phase? Which version were you using? Were you loading from the Select Media Activity or by doing “Open With..?” The more details you can provide, the more likely I can find the source of the problem and fix it.

  7. Allan says:

    I was using version 1.0.13. The problems started already the first time I started Osplay. I just got a black screen and the “not responding” message from Android. After waiting for a minute or two it finally started. The problems continued and often when I switched back to the main screen it just froze with a black screen for minute before anything happened. I had problems when searching for media as well but at those operations could be cancelled.

  8. admin says:

    Hi, Allan,

    Thanks for pointing this out. The issue was the licensing code that only runs for the full version. (The licensing code only works for released versions, and by definition anything new I’m working on isn’t in a released version.) I was able to refactor it to happen in the background, and that should go out in 1.0.14.

  9. Allan says:

    Thanks for the quick response. I’ll give it a new try when 1.0.14 is released.

  10. admin says:

    Hi, Allan,

    Were you seeing long startup times every time, or only on first successful load (or before the first completed load)?

Leave a Reply