>
New Topic
>
Reply<
Esato Forum Index
>
Sony Ericsson / Sony >
Symbian phones
> P1i fails on m.youtube.com
Bookmark topic
lol. ..no, I haven't tested the phone too much, but you can get somewhere around 10mbit in good conditions. So it's not some sort of limitation problem like that.
I think it would be about the same power- drain as well, if the transfer was better.. The node broadcasts at the exact same frequency and power every, say, 100ms anyway. So if it worked as advertised, there would be about the same power- drain per Mb. In theory, anyway.
--
Posted: 2007-10-22 16:18:01
Edit :
Quote
@Nipsen
Only at the wifi transmit stage though, i'm betting its the extra cpu cycles needed to deal with the incoming data stream that would eat the battery... for the p1 with its 200mhz anything over the 11mbs mark might be too much for its poor old cpu to cope with anyway.
Not sure what excuse the n91 would have though
--
Posted: 2007-10-22 16:34:13
Edit :
Quote
.. yes, well.. if we look at this loogically - we could say that on a b- network the target would be 11Mbit, and the "optimum" throughput would be somewhere around half that, say 4-5Mbit. Since half would be overhead and packet loss, which would be necessary to get that much useful junk across the gap. And in theory, then, if we would have 2Mbit as a target, there would still be the same amount of frames generated. In other words, the same amount of overhead for useful packages as well, and the same amount of power per Mb. It would just be spread out thinner.
So there's no reason (except maybe heat or hardware weakness) to set it lower as a default. So what's probably happening is something like this: the AP receives a request - it sends it on, the p1 goes into wait, and checks every 100ms when the frame is ready. At some point the frame is ready, the AP signals the phone, and the p1 tries to retrieve it. At that point one frame - which is tiny - will either get through, or not get through (or it might be fragmented, and so on). And I think that it's here things start to be difficult. Since the module is not programmed very effectively, or something of that sort, and the AP starts to have synch- problems. It would then try to rescue the connection by setting the frequency for transporting frames slower, and the negotiation would continue, and the overhead would just pile on. And there would be (on APs with less quick response) overhead in addition to pauses, and so the throughput would reach bursts on about 200kb/s and over, and then average on around 60 or so (half of lowest rate, at best) very quickly.
And that /could/, at least, explain the bad wifi- connections most people get (and this goes for loads of other units, not just the p1 or symbian..). I guess that would be the same even if the tx was set to target 5.5Mbit in the first place, though.
--
Posted: 2007-10-22 21:36:08
Edit :
Quote
I'm not so sure, if that was the case you would see the signal speed improve. I'm not seeing that at all. I connect my p1 to my netgear and immediately ALL packets are broadcast at 1mbps, packets being transmitted at higher speeds simply stop.
Not withstanding that this could just be the router being rubbish, I still think the p1 negotiates a 1mbps connection from the get-go, at least with my setup. As an alternative to power saving, it may well be that it does this to get maximum range from the wlan.
This is not to say that the implementation is still bad, those graphs from SYMSMB were very interesting indeed, the massive drops with a 32k packet were especially interesting, and hint at a poorly written driver OR poorly written network layer.
[EDIT] Okay. Now I give up too. I tried (and failed) to get the p1 and my netgear router to talk at wifi g - they don't - and then set the netgear to "auto 108mbs" and suddenly i'm getting a nearly full speed download from my laptop WHILE streaming audio from BBC with the p1. Something it just did not want to do before. ARG!
[EDIT AGAIN] AND now I have a full strength 54mbs connection from my laptop. Don't you just hate wlan?
[ This Message was edited by: pnf1973 on 2007-10-22 21:04 ]
--
Posted: 2007-10-22 21:51:56
Edit :
Quote
*nods*. Nice when it works, though. I mean, I live in the belief it might've happened sometime.
..and this negotiation synch would happen before the first ip- packet comes to your phone. It's almost instant, so.. But I think you're right there's something set in the software or something that f**ks things up, specially with the "budget" APs (read: $499 and downwards).
--
Posted: 2007-10-22 22:58:59
Edit :
Quote
Yes, absolutely. You have to admit, given the range of devices available, its a blooming miracle that these things work at all
I think that the SE and Nokia wlan implementations suffer from similar problems - a large number of people get connection issues with the power save polling for example.
I guess we are just stuck waiting for SE to fix this - which isn't looking too hopeful IMHO. As much as i like my p1 and find using it a positive experience I really think that SE are struggling with uiq3 - i think they have tried to do too much too quickly and we are now paying the price.
--
Posted: 2007-10-23 00:37:43
Edit :
Quote
People with htc and other devices have similar problems, though. The synch- problems are pretty common, on laptops for instance. Or just when there are two different modems on a network, etc. But if it's a synch- problem like that, then it's very likely that a fix on just the timing settings for the p1 will improve things a lot.
--
Posted: 2007-10-23 12:07:54
Edit :
Quote
I found a solution!
You need to configure your router to handle RTSP protocol properly.
RTSP is a Real Time Streaming Protocol.
It's used to control a video stream over RTP (Real-time Transport Protocol).
RTSP uses port 554 for both UDP and TCP transports.
RTP have no standards assigned and generally configured to use 16384-32767 UDP ports.
But, for example, QuickTime uses RTP via 6970-6999 ports range.
So, I, having a D-Link DI-624+ wireless router, configured it via Special Applications section (or how it named?).
I already had a default QuickTime profile that I changed a little.
The trigger port remained unchanged and defaults to 554.
I changed only data ports to 1024-65525 (defaults to 6970-6999) to cover all the port range and applied the rules.
Guess what?
It works now!
Enjoy.
[ This Message was edited by: 1m.dm on 2007-10-24 15:15 ]
[ This Message was edited by: 1m.dm on 2007-10-24 15:15 ]
--
Posted: 2007-10-24 16:14:12
Edit :
Quote
I believe I already said that earlier on in the thread
Its not all of the solution anyway, there is a definite issue with wlan and symbian - its not restricted to SE and p1 but it appears that nokia also suffer with wlan probs.
--
Posted: 2007-10-24 16:20:49
Edit :
Quote
Maybe. But I described the solution for D-Link wireless routers with help of which I got streaming video to work on my P1i.
--
Posted: 2007-10-24 16:51:18
Edit :
Quote
New Topic
Reply
