-
Notifications
You must be signed in to change notification settings - Fork 6
News
For news updates in the future goto Google+ and search for #Pandoroid by yours truly :) I think it's going to turn out to be a much more organic way to share newsy stuff related to Pandoroid. This way, everyone can get involved and have their voices heard!!!
-Dylan Powers
....and then school hit....
My goal was to get an update out over the past month or so, but that obviously hasn't happened. (I'm disappointed too.) I suppose I was too ambitious in my endeavors! Currently there are still two versions: one for Pandora One subscribers, and one for others. It kills me having to do it that way, but so be it. It also kills me having GitHub not letting me freely put things up in the downloads section, but again, so is life. Happy listening!
-Dylan Powers
Now that I'm on break, I've had the time to start gravitating my mind towards this project. For standard Pandora users this bug #21 that breaks the app has been brought to my attention. There's a wad of bugs related to it but if you want a quick and dirty fix contact me dylanPowers by email. As for the general advancement of the app, now that I've learned so much more in the past 6 months, I can apply that new found knowledge and wisdom to fix the bad and improve the uhhh bad. I'm planning for a complete overhaul to the app's backend, finally get media keys working so we can get the ICS and Jelly Bean features that all music apps should have, and should be heading towards a final 1.0 release. If you read this, then well props to you!
-Dylan Powers
Hmmm, it appears Pandora has taken to updating their apps recently. I noticed both on my desktop client, and the Android client (I only have it installed to notice such things LOL). We'll have to see if anything becomes of this.
Oh and also bye bye downloads. I'm going to have to come up with a new way now to distribute the APK I guess. Any ideas for such things outside of Github would be much appreciated!
-Dylan Powers
Hey all, I've been at work trying to fix a bug in Android's MediaPlayer API that hinders the playback experience on Android 4.1 and greater devices. People who have phones running Jelly Bean represent an incredibly small minority of users, but I use Jelly Bean, so it matters!
Anyhow, my fix has been merged into the Android Open Source repositories and the patch should be on your device.....someday....
If you're the adventurous I-build-my-own-ROMs type then you can go ahead and cherry-pick the commit to get Pandoroid working correctly today.
-Dylan Powers
Today marks the release of Android version 4.2 into AOSP. Something that's interested me lately is how little care has been brought to Android's MediaPlayer API. Why have it exist if it's broken and doesn't work as documented? From my experience working on this project, the API seems to have never worked exactly as documented. The bad news is that it seems to be getting worse. Under Android 4.1, mp3 music files (this may be even true for all music files...I haven't tested yet) are no longer downloaded automatically when the prepare() command is sent. Instead they wait to download until the play() command is sent. That is a worthless hunk of garbage of an API. I thought originally these problems were related to CyanogenMod 10 on my phone, but I've booted up the emulator and the problems exist there too. With Android 4.2, the problem still exists. I find this rather unacceptable on Google's part. Hopefully I can possibly get a fix into CyanogenMod's sources, but that of course doesn't help anybody else running stock ROMs. For now we're going to have to live with what we got....
If anyone is curious to know, I've slowed up development on this because of school starting up, and my various other commitments. This app has become my baby so I won't forget about it, and I'll continually do small updates here and there, but don't expect any major code rewrites like I was doing over the summer. As for an official 1.0 release, don't bother holding your breath until at least December when I get my winter break. If you were to wonder why I don't simply call what we got a 1.0 release, that is because in order for me to call it a 1.0 release I need it to be up to my own standards, and the current features need to be implemented to their maximum potential. That means, track skipping needs to be revamped so it isn't so slow, the playback engine needs to be both simplified and efficient, audio resume on network disconnects needs to work every time regardless of how unpredictable and crappy the internal MediaPlayer API is, etc, etc....all those little tiny bugs need fixed.
For now, the preview releases work great, and please share with your friends! It helps to motivate me :)
Holy cow, I think Google finally fixed their flawed AAC decoder in Jelly Bean (Android 4.1)! I'm currently listening to the 64kbps MP4 stream on a recent build of CM10 (for my E4GT), and I'm no longer hearing any audio artifacts. It sure took them long enough! Unfortunately on the CM10 build I'm using, the buffering updates are broken, so the app doesn't work as well as it should :(