But nevertheless, this blog entry sounds good…
http://blogs.caradisiac.com/l-autre-blog-de-zig-zag/android-tempolimit-speed-1181901.html
But nevertheless, this blog entry sounds good…
http://blogs.caradisiac.com/l-autre-blog-de-zig-zag/android-tempolimit-speed-1181901.html
I just released Version 1.1 of Read it loud! Premium, my SMS reading app available on Android Market. You can now use profile managers like Llama and others that are able to communicate with other apps via Android intent system to activate and deactivate it automatically.
How to? Just configure your profile manager to send the intent
de.exesmobile.messagereaderpremium.ACTIVATE
to activate it. Or send
de.exesmobile.messagereaderpremium.DEACTIVATE
to – well I think you can guess
Thanks to Joe Kurut who sent me an email with the idea for that feature!
Well – how big the part that software development plays in my live may be, there is something more. No, not my wife (whose part is actually a tiny fraction bigger) – I am talking about music. I play the base guitar in a band called “Sky Pilot” and we have now released our first EP called “Live from Livingroom”. It is available on iTunes, so if you like, take a listen…
A few minutes ago I released Tempolimit Speed HUD Version 5.9. New features are long requested optimizations for the apps HUD mode like a full screen view of the driven speed (YES, without the speed sign and the title bar) and a high contrast mode.
Wonder if we will hit 50.000 downloads solely on Android Market by the end of the year (right now it is roughly 39.000 and counting). If you already use the app, just update, if you don’t and want to give it a try:
https://market.android.com/details?id=net.thomasmanthey.speedwarner
Let me know what features you would like for future releases…
As one can read here, Apple lawyers state that the Samsung Galaxy Tab 10.1 will attract iPad customers so much that Apples iPad business would be ruined in a very short time. Interesting thought – is the “copy” so much better than the original? Guess I need one, then…
Today I noticed a change in ratings of my application “Read it loud! SMS Reader Basic” – one 5 star rating had gone while a 2 star rating had appeared. Obviously a user had changed his mind after a bad experience with the app. Then I saw a accompanying comment – let me quote:
Worked great with my Evo 4G and my Evo 3D…and worked for a day on my Motorola Photon…but it stopped for some reason…love the app otherwise
I really would love to offer help, to find out what the error was and to correct it – but I can’t.
What most users do not keep in mind is that we developers cannot reply to comments and ratings, we cannot even contact the one who wrote that comment. So what can YOU as a user do instead of just writing negative comments and ratings? Well, if you like the app in general but had some negative experience – may it be an error or a function not working as expected or even a feature wish – then give us developers a chance to give you support and improve our apps. Just contact us – a suitable mail address can be found on every app’s market page. And then tell us what happened. Did you change something on your phone? Was there a software update? Did you notice anything when it stopped working?
We do lots of testing before publishing apps and invest lots of effort to produce quality software – so if you get an error or a problem then there is a good chance that we can fix it in a short time. Which means no bad ratings for us and our apps and better apps for you to use.
Agreed? Thank you!
You know Androids TextToSpeech-Service? It enables you to enhance your Android apps with voice output in a very convenient way. What I like most is that it runs completely in the background, so that calling myTTSService.speak("Some very long text indeed..."); does not stop your main thread from continuing which is one reason less to get an “Application not responding”-error.
So far so good, but sometimes you just need to know when the TTS-Service has finished speaking a sentence. Well, the API documentation suggests the following: Just make your calling class implement OnUtteranceCompletedListener, register it with the TTS-Service and get notified whenever a sentence is finished. Let source code speak:
After compiling and running this code one would expect (at least I did on first try) that the TTS-Engine would
(a) be initialized
(b) would speak “Hello world”
(c) call my method onUtteranceCompleted with “FIRSTSENTENCE” as parameter.
Well, (a) and (b) happened perfectly. Not so much (c), where not so much means not at all. What happened? After trying I lot i found out that the API documentation does not mention on thing: The call myTTS.setOnUtteranceCompletedListener(this); MUST be used AFTER onInit has been called by the TTS -Service.
So changing two methods helps:
Nice to know…
Tempolimit Speed HUD has now 20’000 downloads. Greetings to Mario whose parallel developed iPhone-project has some less…
With round about 36h gone Read it loud! SMS Reader has 176 Downloads, and 122 active installs. And is rated with an average of 3.5 stars out of five. Not bad, but is more possible?
The first version of Read it loud! SMS Reader Basic has just been released. This basic edition will be freely available, an enhanced and paid Premium edition will be released later…