Closed GoogleCodeExporter closed 8 years ago
I use NPR (as do many other users) over wifi much of the time. In fact the
majority of our issues involve switching from WiFi to 3G. Also, the app should
generally show an error message if it can't connect — it shouldn't hang. I'd
like to get more information, but short of getting your log files at the time
of the hang, the only other thing would be to see if you have this problem at
other wifi access points.
Original comment by jeremy.w...@gmail.com
on 5 Jan 2011 at 12:54
Your comment about logs helped me figure it out. Evidently the app uses an
outgoing TCP port 8080 to connect to the media stream. Strict firewall
rules stop those connections, so I had to implement a rule to enable that.
That would have been a great little tip/documentation note on the faq page.
:-)
Thanks for the fast response to the query and support.
Original comment by sean.j....@gmail.com
on 5 Jan 2011 at 4:12
Sean:
Marking that for the person who maintains the FAQ.
Thanks a ton!
Kate
Original comment by kate.my...@gmail.com
on 5 Jan 2011 at 1:36
Hmm... that's a good point. RTMP servers can often run on ports other than port
80, often because they are co-hosted on the same server as a web server. While
we can't know every port that every stream could use (we could do an inventory
but then someone has to track that), I think that the app could do a better job
of detecting that problem and responding to it, perhaps with a useful
suggestion like "Is your firewall configured to allow traffic over port XXXX?"
Sean - if you happen to have the log files, would you mind attaching a stack
dump that could help me know where to put that detection?
Original comment by jeremy.w...@gmail.com
on 5 Jan 2011 at 7:08
I don'thave an issue with sending a stack dump, but I need to research how
to collect that info and get it off the phone. :-) Stay tuned.
Comment #4 on issue 55 by jeremy.w...@gmail.com: App won't play local
station streams over wifi
http://code.google.com/p/npr-android-app/issues/detail?id=55
Hmm... that's a good point. RTMP servers can often run on ports other than
port 80, often because they are co-hosted on the same server as a web
server. While we can't know every port that every stream could use (we could
do an inventory but then someone has to track that), I think that the app
could do a better job of detecting that problem and responding to it,
perhaps with a useful suggestion like "Is your firewall configured to allow
traffic over port XXXX?"
Sean - if you happen to have the log files, would you mind attaching a stack
dump that could help me know where to put that detection?
Original comment by sean.j....@gmail.com
on 6 Jan 2011 at 12:36
Jeremy - I wasn't able to find anything meaningful on collecting a stack
dump. Do you have instructions?
Thanks.
Original comment by sean.j....@gmail.com
on 6 Jan 2011 at 4:21
Actually, having looked at this, I don't think the log files are going to
provide us any further details. We can re-create this in a test and figure out
how to capture it there.
You mentioned the logs, so I assumed you had looked at them. It's not totally
straightforward to get them.
However, if you are interested, here's info on how to do it. :)
If you have the development tools installed you can hook your phone to your
computer and use 'adb -d logcat' as documented here:
http://developer.android.com/guide/developing/tools/adb.html#logcat.
If you don't have the dev tools installed somewhere, it's not necessary to do
so. There are a couple apps in the marketplace to pull the log, including
aLogcat
(http://www.appstorehq.com/alogcat-logcatapplication-android-175640/app).
Logs files are combined logs of all applications, so you need to pull the
segment of the file from the time that the error is happening to provide the
best content.
Original comment by jeremy.w...@gmail.com
on 6 Jan 2011 at 6:31
Sorry I wasn't clear..... I looled at my firewall logs and saw what was
being blocked there. I wasn't looking at the phone logs.
Sorry I couldn't be more helpful here.
Sean
Updates:
Owner: jeremy.wadsack
Original comment by sean.j....@gmail.com
on 7 Jan 2011 at 8:17
Can we add a note to the FAQ that streaming problems over wifi could be related
to firewall settings blocking access to external streaming servers?
Then I think we can close this issue.
Original comment by jeremy.w...@gmail.com
on 24 Mar 2011 at 6:06
That would work for me.
As a side note, for me to listen to my local NPR station, I had to create a
firewall rule to allow outbound TCP port 8080. Other stations may use other
TCP/UDP ports, so a user would have to review their firewall logs to determine
the correct ports and protocols to allow though their firewalls.
BTW, most home firewalls default to allow all outbound connections through
their firewalls. Mine is a little more restrictive. :-)
Original comment by sean.j....@gmail.com
on 25 Mar 2011 at 7:08
Documentation should be added to the FAQ page about this possibility. NPR will
follow up.
Original comment by jpenn...@gmail.com
on 19 May 2011 at 7:36
Original comment by jpenn...@gmail.com
on 19 Feb 2013 at 7:50
Original issue reported on code.google.com by
sean.j....@gmail.com
on 5 Jan 2011 at 12:04