Reply
Thread Tools
Posts: 79 | Thanked: 64 times | Joined on Jan 2012 @ Pordenone
#41
Originally Posted by qspb View Post
To solve this problem for me I added
Code:
export PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin"
to .config file in /home/user directory and re-entered the terminal.
but where u added this piece of script???
.config is a directory and in this directory are others directory...
in which file i must write it in??
 
qspb's Avatar
Posts: 44 | Thanked: 80 times | Joined on Oct 2012 @ Saint Petersburg
#42
Originally Posted by KTy View Post
Any updates or findings ?
I started a topic about wl1273 capabilities in TI's e2e forum: http://e2e.ti.com/support/low_power_.../t/226064.aspx . There is one reply there.

Originally Posted by michdeskunk View Post
but where u added this piece of script???
.config is a directory and in this directory are others directory...
in which file i must write it in??
I apologize for telling incorrect filename. I added this string at the end of .profile file.
 
Posts: 19 | Thanked: 6 times | Joined on Dec 2012
#43
Hi,
As i write in this post i've send back my n9 to vendor 'cause I think 802.11n problem is due to hardware. so, I only write here for your information ...

As many N9 users I know that I'll have to "bidouille"/hack it to have the best phone ever, but, if something like wifi donesn't work properly ...

It was very difficult to manage my email account, update mail box (only headers), read mail and get SIP account working over wifi ...

I didn't read anything about any link between screen lock and wifi but, in my test to make it work i used ping (ping -t rm696) rm696 is default dns name of n9 on my local network.

ping lost many packets, until my n9 get in "spleep mode" (screen locked after few seconds) and suddenly all pings came back ! I Unlocked phone and again, ping get lost, I locked screen and ping came back !

Of course, as I was running these experiments, all my mails were downloaded, my SIP account connected and so on ! but of course, unable to download mail content when screen is on and SIP get in netwok search mode

Of course, in connection manager, wifi appear to be connected with good signal strength.

I use 300mb/s 802.11n network with wmm active on a netgear wnap320

I really think it's a hardware problem due to screen.
 
Posts: 591 | Thanked: 1,165 times | Joined on Jul 2012
#44
Originally Posted by nemric View Post
Hi,
As i write in this post i've send back my n9 to vendor 'cause I think 802.11n problem is due to hardware. so, I only write here for your information ...

As many N9 users I know that I'll have to "bidouille"/hack it to have the best phone ever, but, if something like wifi donesn't work properly ...

It was very difficult to manage my email account, update mail box (only headers), read mail and get SIP account working over wifi ...

I didn't read anything about any link between screen lock and wifi but, in my test to make it work i used ping (ping -t rm696) rm696 is default dns name of n9 on my local network.

ping lost many packets, until my n9 get in "spleep mode" (screen locked after few seconds) and suddenly all pings came back ! I Unlocked phone and again, ping get lost, I locked screen and ping came back !

Of course, as I was running these experiments, all my mails were downloaded, my SIP account connected and so on ! but of course, unable to download mail content when screen is on and SIP get in netwok search mode

Of course, in connection manager, wifi appear to be connected with good signal strength.

I use 300mb/s 802.11n network with wmm active on a netgear wnap320

I really think it's a hardware problem due to screen.
Hmmm...
Smells like screen taking up too much CPU and network dropping in lower CPU usage priortiy...
As if it would be hardware, locking the screen would not necessarily fix the issue...

But interesting topic!! I have had problems with Wifi too (apart of the usual bugs). It would be *great* to improve this!
Please don't give up!
__________________
BWizz - best N9 bookmark editing tool! Check it out ->BWizz for Harmattan

LINKer - transform your N9's home view in a Desktop, give it the freedom it deserves! -> LINKer for Harmattan

QuickBar - Can't find the app you used yesterday in your overcrowded Home Screen? Want access to the QuickLaunch bar even in the home screen? QuickBar for Harmattan

If you like our work, and would like to support via PayPal : users.giulietta@gmail.com
 
qspb's Avatar
Posts: 44 | Thanked: 80 times | Joined on Oct 2012 @ Saint Petersburg
#45
I tested Wi-Fi ping. Results:
When screen is on:
Code:
ping AAA.BBB.CCC.DDD
PING AAA.BBB.CCC.DDD (AAA.BBB.CCC.DDD) 56(84) bytes of data.
64 bytes from AAA.BBB.CCC.DDD: icmp_req=1 ttl=64 time=143 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=2 ttl=64 time=173 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=3 ttl=64 time=196 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=4 ttl=64 time=220 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=5 ttl=64 time=243 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=6 ttl=64 time=58.7 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=7 ttl=64 time=85.4 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=8 ttl=64 time=105 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=9 ttl=64 time=128 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=10 ttl=64 time=147 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=11 ttl=64 time=176 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=12 ttl=64 time=198 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=13 ttl=64 time=222 ms
^C
--- AAA.BBB.CCC.DDD ping statistics ---
13 packets transmitted, 13 received, 0% packet loss, time 12010ms
rtt min/avg/max/mdev = 58.732/161.616/243.933/54.083 ms
When screen is off:
Code:
ping AAA.BBB.CCC.DDD
PING AAA.BBB.CCC.DDD (AAA.BBB.CCC.DDD) 56(84) bytes of data.
64 bytes from AAA.BBB.CCC.DDD: icmp_req=1 ttl=64 time=82.4 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=2 ttl=64 time=200 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=3 ttl=64 time=119 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=4 ttl=64 time=350 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=5 ttl=64 time=164 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=6 ttl=64 time=192 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=7 ttl=64 time=210 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=8 ttl=64 time=238 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=9 ttl=64 time=255 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=10 ttl=64 time=75.0 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=11 ttl=64 time=100 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=12 ttl=64 time=120 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=13 ttl=64 time=145 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=14 ttl=64 time=167 ms
64 bytes from AAA.BBB.CCC.DDD: icmp_req=15 ttl=64 time=189 ms
^C
--- AAA.BBB.CCC.DDD ping statistics ---
15 packets transmitted, 15 received, 0% packet loss, time 14020ms
rtt min/avg/max/mdev = 75.001/174.317/350.956/70.758 ms
I see no difference.
 
Posts: 19 | Thanked: 6 times | Joined on Dec 2012
#46
ok, but do you have problem with 802.11n wifi.
I successfully get my n9 work on 802.11g access point but once at home, with 300mb/s 802.11n, like many users on this post, connection was unusable...
what is your wifi class ?

[edit] sorry, I didn't see you are author of post ... your N9 seems to work better than mine on 11n wifi.

Last edited by nemric; 2012-12-28 at 08:55.
 
Posts: 230 | Thanked: 302 times | Joined on Oct 2009 @ Helsinki, Suomi (Finland)
#47
Originally Posted by qspb View Post
But I know that some other N9 users said they had no problems with their 802.11n routers.. maybe in neighbour topics on this forum. Can somebody evaluate actual Wi-Fi N speed in a similar way and post the results here so that we can compare different users' experience?

P.S. "M/s" means "Megabytes per a second" - it's not a bitrate, it's a real file transfer speed.
A while ago I tested download speeds of different devices in my network downloading a same file 3 times in a row from the internet. The internet connection isn't a bottleneck here for wifi (not sure about raspberry pi's 100 Mbit ethernet.). Router is a Netgear wndr3800 running openwrt.

Not a good wifi benchmark per se, but it gives some idea about the relative performance. N9's 802.11n peaks at about 4.3 MB/s. The wifi signal isn't the best possible (router next room, behind a wall) and seems to affect n9's wifi performance more compared to a laptop using g standard wifi, which is slower but gives more consistent readings.



[edit]

Pinging my router from N9 (device active):
Code:
~ $ ping openwrt
PING openwrt (192.168.0.254): 56 data bytes
64 bytes from 192.168.0.254: seq=0 ttl=64 time=2.350 ms
64 bytes from 192.168.0.254: seq=1 ttl=64 time=3.174 ms
64 bytes from 192.168.0.254: seq=2 ttl=64 time=10.223 ms
64 bytes from 192.168.0.254: seq=3 ttl=64 time=8.728 ms
64 bytes from 192.168.0.254: seq=4 ttl=64 time=9.796 ms
64 bytes from 192.168.0.254: seq=5 ttl=64 time=10.315 ms
64 bytes from 192.168.0.254: seq=6 ttl=64 time=10.345 ms
64 bytes from 192.168.0.254: seq=7 ttl=64 time=10.406 ms
64 bytes from 192.168.0.254: seq=8 ttl=64 time=10.407 ms
64 bytes from 192.168.0.254: seq=9 ttl=64 time=10.224 ms
64 bytes from 192.168.0.254: seq=10 ttl=64 time=10.315 ms
64 bytes from 192.168.0.254: seq=11 ttl=64 time=10.284 ms
64 bytes from 192.168.0.254: seq=12 ttl=64 time=10.253 ms
64 bytes from 192.168.0.254: seq=13 ttl=64 time=9.003 ms
64 bytes from 192.168.0.254: seq=14 ttl=64 time=10.376 ms
64 bytes from 192.168.0.254: seq=15 ttl=64 time=10.254 ms
64 bytes from 192.168.0.254: seq=16 ttl=64 time=10.254 ms
64 bytes from 192.168.0.254: seq=17 ttl=64 time=10.437 ms
64 bytes from 192.168.0.254: seq=18 ttl=64 time=10.529 ms
64 bytes from 192.168.0.254: seq=19 ttl=64 time=8.819 ms
64 bytes from 192.168.0.254: seq=20 ttl=64 time=10.223 ms
64 bytes from 192.168.0.254: seq=21 ttl=64 time=8.759 ms
^C
--- openwrt ping statistics ---
22 packets transmitted, 22 packets received, 0% packet loss
round-trip min/avg/max = 2.350/9.339/10.529 ms
Pinging my router from N9 (device idle, LPM screen):
Code:
~ $ ping openwrt
PING openwrt (192.168.0.254): 56 data bytes
64 bytes from 192.168.0.254: seq=0 ttl=64 time=183.289 ms
64 bytes from 192.168.0.254: seq=1 ttl=64 time=185.638 ms
64 bytes from 192.168.0.254: seq=2 ttl=64 time=201.447 ms
64 bytes from 192.168.0.254: seq=3 ttl=64 time=209.808 ms
64 bytes from 192.168.0.254: seq=4 ttl=64 time=220.704 ms
64 bytes from 192.168.0.254: seq=5 ttl=64 time=11.292 ms
64 bytes from 192.168.0.254: seq=6 ttl=64 time=19.958 ms
64 bytes from 192.168.0.254: seq=7 ttl=64 time=43.305 ms
64 bytes from 192.168.0.254: seq=8 ttl=64 time=52.582 ms
64 bytes from 192.168.0.254: seq=9 ttl=64 time=62.317 ms
64 bytes from 192.168.0.254: seq=10 ttl=64 time=72.266 ms
64 bytes from 192.168.0.254: seq=11 ttl=64 time=80.841 ms
64 bytes from 192.168.0.254: seq=12 ttl=64 time=91.584 ms
64 bytes from 192.168.0.254: seq=13 ttl=64 time=101.318 ms
64 bytes from 192.168.0.254: seq=14 ttl=64 time=111.236 ms
64 bytes from 192.168.0.254: seq=15 ttl=64 time=120.880 ms
64 bytes from 192.168.0.254: seq=16 ttl=64 time=130.829 ms
64 bytes from 192.168.0.254: seq=17 ttl=64 time=140.533 ms
^C
--- openwrt ping statistics ---
18 packets transmitted, 18 packets received, 0% packet loss
round-trip min/avg/max = 11.292/113.323/220.704 ms

Last edited by ladoga; 2013-02-20 at 14:10.
 

The Following User Says Thank You to ladoga For This Useful Post:
Posts: 47 | Thanked: 16 times | Joined on Jul 2012
#48
Originally Posted by qspb View Post
Some good news.

Before trying to recompile wireless driver or going to NITdroid forum I decided to reflash my Nokia N9. You see, many errors and misconfiguration problems are possible due to updating the phone over the air several times, so it's certainly better to make a "clean install" of phone firmware. So I followed these instructions to zeroize and reflash my N9: http://talk.maemo.org/showpost.php?p...16&postcount=1 .

Then I turned on my phone, installed developer-mode, networking utilities (including wget), and redone all my measurments.
First I set up AP configuration with QoS disabled; here is a part of my hostapd config:
Code:
hw_mode=g
ieee80211n=1
ht_capab=[HT20+][SHORT-GI-20]
channel=6
I tried to download a large file and the average speed was ~ 2.6 M/s (according to wget output). It seemed to be usual 802.11g speed.
Then I edited hostapd config and enabled QoS:
Code:
ieee80211n=1
wmm_enabled=1
ht_capab=[HT20+][SHORT-GI-20]
channel=6
The result was exciting. Enabling QoS improved the speed, not reduced it. The average speed was ~ 2.9 M/s. Sometimes it jumped up to 3.1 M/s (!). Such a result is unreachable with 802.11g-only mode.
Okay, then I made hostapd use [HT40+] instead of [HT20+]. The speed reduced. It was ~ 1 M/s again. With QoS disabled it raised up to stable 2.6 M/s . And such a result isn't surprising, because according to iw output, N9's wireless module supports only HT20 and SHORT-GI-20 capabilities, so using QoS with HT40 results in reducing speed. I think it's quite normal.

But at least I've managed to get my 802.11n work properly with HT20 and QoS enabled. The speed is 2.9 - 3.1 M/s now (it's definetely higher than usual 802.11g speed), the connection is stable, so I'm able to use Internet, ssh and http file transfer without any problems. I'm very glad.

But I know that some other N9 users said they had no problems with their 802.11n routers.. maybe in neighbour topics on this forum. Can somebody evaluate actual Wi-Fi N speed in a similar way and post the results here so that we can compare different users' experience?

P.S. "M/s" means "Megabytes per a second" - it's not a bitrate, it's a real file transfer speed.
can u give more details, step by step? tks
 
Posts: 198 | Thanked: 130 times | Joined on Sep 2012 @ Pakistan
#49
any updates on WiFi Driver qspb?
__________________
N9 - 16 GB Black Reborn

Tutorial - OpenVPN for N9
 
Moderator | Posts: 5,320 | Thanked: 4,464 times | Joined on Oct 2009
#50
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 08:33.