| |
Sasq
Registered: Apr 2004
Posts: 156 |
Android SID/MOD/etc player
I am working on a SID/MOD player for Android called Droidsound and need some beta testing...
* Music goes into MODS/ on sdcard
* Requires Android 1.6
* Uses sidplay2 (and modplug + GME)
* Indexes zip-files (like C64Music.zip)
* Title search
* CSDB metadata browsing
(To try out CSDB browsing, put "csdb.dump" in your MODS dir)
The player (and csdb.dump) can be found here:
http://swimmer.se/droidsound/files/
|
|
... 22 posts hidden. Click here to view all posts....
|
| |
Perff
Administrator
Posts: 1679 |
All media buttons on my HTC headset now works perfectly with beta6c. :)
Great work!
However, it still takes forever to update the database (C64Music.zip especially) on my phone. It takes at least 5 minutes. Not so big a problem, but I remember it as being faster at some point. Perhaps before upgrading to 2.2!? :)
What are your experience? |
| |
Sasq
Registered: Apr 2004
Posts: 156 |
Quote: All media buttons on my HTC headset now works perfectly with beta6c. :)
Great work!
However, it still takes forever to update the database (C64Music.zip especially) on my phone. It takes at least 5 minutes. Not so big a problem, but I remember it as being faster at some point. Perhaps before upgrading to 2.2!? :)
What are your experience?
Actually that sounds slow - I think its under 2 minutes on my Galaxy... I'll time it to make sure.
It really shouldn't have to do with 2.2 - can you think of anything else that is different with your phone? |
| |
Sasq
Registered: Apr 2004
Posts: 156 |
Quoting SteinI just installed beta6c and my headset buttons still don't work :(
!
What kind of headset did you have?
If you can run logcat, look for lines starting with MEDIA BUTTON from the class PlayerService, that shows which key events are broadcasted...
|
| |
Sasq
Registered: Apr 2004
Posts: 156 |
Wishful thinking on my part - it takes 03:15 to index C64Music.zip on my Samsung Galaxy S
|
| |
Stone
Registered: Oct 2006
Posts: 172 |
Quoting Sasq
What kind of headset did you have?
If you can run logcat, look for lines starting with MEDIA BUTTON from the class PlayerService, that shows which key events are broadcasted...
I have the Google Nexus One headset, which I think is exactly the same as the one that comes with the HTC Desire. I got a replacement HTC headset that works exactly the same as the Google one.
I don't have the sdk, but I downloaded aLogcat and tried filtering on PlayerService but no key events showed up. I tried the same with the Spotify app and then I get a log like this:
D/SpotifyJava(13367): PHONE STATE - IDLE
D/SpotifyJava(13367): Received broadcast: android.intent.action.HEADSET_PLUG
D/SpotifyJava(13367): Not logged in. Ignoring intent.
D/SpotifyJava(13367): Received broadcast: android.intent.action.MEDIA_BUTTON
D/SpotifyJava(13367): Received broadcast: android.intent.action.MEDIA_BUTTON
D/SpotifyJava(13367): Received broadcast: android.intent.action.MEDIA_BUTTON
|
| |
Sasq
Registered: Apr 2004
Posts: 156 |
PlayerService logs lots of things, you're looking for lines like this;
V/PlayerService( 4108): MEDIA BUTTON android.intent.action.MEDIA_BUTTON
V/PlayerService( 4108): MEDIA BUTTON KEY KeyEvent{action=0 code=79 repeat=0 meta=0 scancode=248 mFlags=8}
V/PlayerService( 4108): MEDIA BUTTON android.intent.action.MEDIA_BUTTON
V/PlayerService( 4108): MEDIA BUTTON KEY KeyEvent{action=1 code=79 repeat=0 meta=0 scancode=248 mFlags=8}
|
| |
Stone
Registered: Oct 2006
Posts: 172 |
I only see the following (from PlayerService):
V/PlayerServiceConnection(12977): binding
V/PlayerService(12977): Silence detection off
V/PlayerService(12977): Service started
V/PlayerService(12977): Intent null / null
V/PlayerServiceConnection(12977): Service Connected
V/PlayerService(12977): Adding com.ssb.droidsound.PlayerServiceConnection$1@44a23520
V/PlayerServiceConnection(12977): Unbinding
V/PlayerService(12977): Removing com.ssb.droidsound.PlayerServiceConnection$1@44a23520
V/PlayerServiceConnection(12977): binding
V/PlayerService(12977): Silence detection off
V/PlayerService(12977): Service started
V/PlayerService(12977): Intent null / null
V/PlayerServiceConnection(12977): Service Connected
V/PlayerService(12977): Adding com.ssb.droidsound.PlayerServiceConnection$1@44a23520
V/PlayerServiceConnection(12977): Unbinding
V/PlayerService(12977): Removing com.ssb.droidsound.PlayerServiceConnection$1@44a23520
I feel like an idiot suggesting things to you since I've never even looked at the Android sdk myself, but did you try raising the priority of the IntentFilter thingie as suggested in an earlier post? |
| |
SIDWAVE
Account closed
Registered: Apr 2002
Posts: 2238 |
My handset, MH801 for Sony X10 mini - it operates on the phone's music player, when droindsound is running, and not on droidsound :) |
| |
Sasq
Registered: Apr 2004
Posts: 156 |
Quoting Stein
I feel like an idiot suggesting things to you since I've never even looked at the Android sdk myself, but did you try raising the priority of the IntentFilter thingie as suggested in an earlier post?
Yep it's the highest priority ATM.
If that log is when you actually pressed the MEDIA_BUTTON then I can only guess one of two things;
1. You are running some evil program that lies before Droidsound in the queue, also runs on highest priority and steals the broadcast.
2. You are actually running the old beta5 from swimmer.se and not the new beta6c from swimsuitboys.com
|
| |
Sasq
Registered: Apr 2004
Posts: 156 |
Quote: My handset, MH801 for Sony X10 mini - it operates on the phone's music player, when droindsound is running, and not on droidsound :)
If Droidsound is not either playing or paused, it will ignore the broadcast in favor of other programs... maybe that's whats happening?
|
| Previous - 1 | 2 | 3 | 4 - Next |
