You would think that because developers make applications for Android, that the ecosystem would be standardized enough so that if I cast a seqeunce of Characters into a String, and it doesn't throw an error in plain Java that Android will be fine too. And it is. Except when you're device implementation of casting from CharSequences to Strings sometimes crosses through an Android SpannableString interface. In which case you can't cast that to a String. So you get bugs, and crashes. And one poor soul on a Galaxy S3 build who has this problem who just can't for the life of hi/her open the Radio interface to set settings. Because Android bugs out in an area that it works fine for almost everyone else. Why Android.
Hopefully the bug has been fixed up so that the interface I've designed can be used by the people suffering from a casting error on my part. Hopefully Android will slowly but surely become more standardized so that a SDK distributed to all developers will be expected to work on one, and work on all devices. Also a null ointer has been addressed in the overlay which should hopefully fix the problems for those people encountering bugs in there.
Hope. Just a fool's hope.
Keep following pyamsoft for updates and announcements about the newest applications!
==
Like what I do?
Send me an email at: pyam.soft@gmail.com
Or find me online at: http://pyamsoft-official.blogspot.com/