Error code 1,-105 while attempting to stream WZAI-FM

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Open NPR app
2. Search -> Callsign -> Wzai
3. Select WZAI
4. Select "Listen Online"
5. Error.
6. 30s after leaving the program, I get a "Force Close" message about it

What is the expected output? What do you see instead?

I expect to listen to the freaking radio. Instead I'm getting an error mesage 
1, -105

What version of the product are you using? On what operating system?

1.4.108 code: 9 on Android 2.2.1
It worked fine when I was on 2.1.

Please provide any additional information below.

Original issue reported on code.google.com by delugeof...@gmail.com on 3 Jan 2011 at 1:19

• Merged into: #56

[GoogleCodeExporter]

This doesn't happen for me on my N1 (running Android 2.3.1, which could be the 
difference). No problem on my G1 either (running Android 1.6, which should be 
similar media player to 2.2.1).

In both cases I'm using the latest update of the NPR News app, 1.4.117. Can you 
try updating from the marketplace and see if you still have an issue?

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 1:05

[GoogleCodeExporter]

It updated in the market today and still has the same error. I can get 
prerecorded streams like the hourly news brief but nothing live.

Original comment by delugeof...@gmail.com on 5 Jan 2011 at 1:15

[GoogleCodeExporter]

Ugh. Ok, thanks for doing that. We'll dig deeper into this and let you know if 
there's more information we need.

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 1:20

[GoogleCodeExporter]

-105 seems to suggest that we're choking media player on a read-only parameter. 
I don't know wtf that means to your app but I have the tools to provide a 
logcat if you think it will help.

Original comment by delugeof...@gmail.com on 5 Jan 2011 at 2:59

[GoogleCodeExporter]

The wzai streams (all 4 in the API) are fine, so this is not a data problem. 

Original comment by kate.my...@gmail.com on 5 Jan 2011 at 3:32

[GoogleCodeExporter]

A logcat would be very helpful. Perhaps we can figure out from the context what 
a "read-only parameter" means. :)

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 7:10

[GoogleCodeExporter]

Okay, so I'm really inexpert at this and just typed adb logcat > C:\logcat.txt 
and trimmed down the monster file I got to what I thought would be relevant. If 
you want to give me logcat parameters I might do better, but I think I have a 
good portion of what's going on when I try to listen.

Original comment by delugeof...@gmail.com on 5 Jan 2011 at 8:21

[GoogleCodeExporter]

Wow, windows notepad totally mangled that file. Fixed.

Original comment by delugeof...@gmail.com on 5 Jan 2011 at 8:26

Attachments:

• npr-logcat.txt

[GoogleCodeExporter]

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 9:50

[GoogleCodeExporter]

Sean - can you point me to where the error -105 is defined? I assume you came 
across this somewhere. The error codes for media player are spread out across 
so many files that I can't always find them.

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 10:42

[GoogleCodeExporter]

Sean?
I had googled it at some point and followed a series of links to 
android.git.kernel.org/?p=platform/external/opencore.git;a=blob;f=pvmi/pvmf/incl
ude/pvmf_return_codes.h;h=ed5a2539ca85ae60425229be41646b6bd7d9389c;hb=HEAD

Hope I didn't get the wrong set of codes LOL like I said, inexpert

Original comment by delugeof...@gmail.com on 5 Jan 2011 at 11:46

[GoogleCodeExporter]

Well your Googling is better than mine. I even looked through that file and 
missed it.

For the record, this appears to be a value captured from the stream in response 
to a request. It's a return error code from the source (i.e. HTTP Response Code 
458). See section 11.3.9 in http://tools.ietf.org/html/rfc2326#page-43.

This implies to me that there's actually a problem with the media player 
connecting to that stream. Let me check i it repros in the simulator. It could 
also be something in the proxy that we build for pre 2.3 OS, but I think that 
just passes status codes through.

Original comment by jeremy.w...@gmail.com on 5 Jan 2011 at 11:58

[GoogleCodeExporter]

Ah, line 63.

I'm sorry, I've sent you on a wild goose chase. Apparently a huge chunk of my 
media player is missing, including the OpenCore API that this app depends on. 
It's totally on my end and I'm sorry that I wasted your time.

Original comment by delugeof...@gmail.com on 6 Jan 2011 at 4:34

[GoogleCodeExporter]

Well, that could certainly cause some problems. :) Although I wonder why it 
popped up a RTMP server message for that. 

I think we can close this then.

Oh, and for the record, my Nexus 1 runs 2.2.1, not 2.3.1 (I don't think there 
is a 2.3.1 at this time). Also, the proxy in the app addresses OS pre-2.2 and 
is not used in 2.2 or later (where Shoutcast streams are directly supported by 
the media player).

Original comment by jeremy.w...@gmail.com on 6 Jan 2011 at 6:34

[GoogleCodeExporter]

That's right (although there actually is a 2.3.1 on the Nexus S).

Original comment by mfreder...@google.com on 6 Jan 2011 at 6:52

[GoogleCodeExporter]

Original comment by jpenn...@gmail.com on 6 Jan 2011 at 7:51

• Changed state: Invalid

[GoogleCodeExporter]

So, this needs to be reopened.

I had originally thought it was something I had done to the phone running 
non-stock firmware, but now I'm convinced it actually is your problem, lol. I'm 
running stock firmware from Samsung right now, and I'm still getting the same 
error. It doesn't make much sense to me, but here's a logcat from when I 
started the NPR app to the end of error handling. I appreciate the effort 
you've already put into this. I really want to be able to stream NPR, 
considering I'm a member.

Early on in the Logcat it complains that the OpenCore Hardware Module isn't 
found... wtf does that mean? ;)

I can still stream pre-recorded stories, I just can't stream the live radio.

Original comment by delugeof...@gmail.com on 13 Jan 2011 at 7:17

[GoogleCodeExporter]

Just grabbed version 1.3 off the "Downloads" section here and it streams what 
I'm telling it to. If THAT points to the problem at all, you're welcome. In the 
mean time, I'm happy using the old version of the app. If you want another 
logcat please tell me, I'll be happy to show you the working log.

Also, I really hope that comments on closed issues aren't going to /dev/null 
because I don't much enjoy talking to myself. Hope you're getting this ;)

Original comment by delugeof...@gmail.com on 13 Jan 2011 at 7:39

[GoogleCodeExporter]

I think the problem has something to do with this:
V/PlayerDriver( 2889): Send player code: 6
V/PlayerDriver( 2889): release string is 2.2 len 3
V/PlayerDriver( 2889): HandleInformationalEvent: 26
V/PlayerDriver( 2889): HandleInformationalEvent: type=26 UNHANDLED

This is the same response I see when using my Samsung Galaxy Tablet to connect 
to an RTSP stream carrying h.264.  I get this event "26" about one out of every 
four attempts to connect.

delugeof: what kind of android device are you using?

Chris

Original comment by chrissta...@gmail.com on 24 Jan 2011 at 2:55

[GoogleCodeExporter]

Go figure, Samsung GALAXY S CAPTIVATE. 

Original comment by delugeof...@gmail.com on 26 Jan 2011 at 3:05

[GoogleCodeExporter]

Per suggestion, I'm reopening this issue. I will merge it into another, as we 
can't nail down specifics on this front yet. Until we do, it makes more sense 
to me to keep these all together.

Original comment by jpenn...@gmail.com on 31 Jan 2011 at 7:12

• Changed state: Duplicate