Openmoko Bug #2043: GTA02 WiFi signal reception too weak

Openmoko Public Trac bugs at docs.openmoko.org
Tue Sep 30 13:15:12 CEST 2008


#2043: GTA02 WiFi signal reception too weak
---------------------+------------------------------------------------------
 Reporter:  vnevoa   |          Owner:  openmoko-devel
     Type:  defect   |         Status:  new           
 Priority:  normal   |      Milestone:                
Component:  unknown  |        Version:  Om2008.8      
 Severity:  normal   |       Keywords:                
Blockedby:           |   Reproducible:  always        
 Blocking:           |  
---------------------+------------------------------------------------------
 Software: OM2008.9 with "testing" feeds. Updated and rebooted today.

 Comparing the Neo FR's wifi signal strength to other portable systems
 apparently indicates that the FR's wifi system has very bad signal
 reception. This may be at the root of many of the other numerous wifi
 tickets.

 Use case: placed the FR and a Eee901 side-by-side, and scanned for
 wireless networks on both. (I had to switch off the Eee901 before scanning
 with the FR, or the interference would kill the signal on the FR).
 Here the output of both scans:

 ===========Eee901=========
 vasco at van-eee:~$ iwlist scan
 ra0       Scan completed :
           Cell 01 - Address: 00:11:88:A4:6B:62
                     ESSID:"INTERNET"
                     Mode:Managed
                     Channel:6
                     Quality:20/100  Signal level:-82 dBm  Noise level:-97
 dBm
                     Encryption key:off
                     Bit Rates:36 Mb/s
           Cell 02 - Address: 00:21:29:8A:C5:EE
                     ESSID:"linksys"
                     Mode:Managed
                     Channel:5
                     Quality:34/100  Signal level:-76 dBm  Noise level:-97
 dBm
                     Encryption key:off
                     Bit Rates:36 Mb/s
           Cell 03 - Address: 00:11:88:A4:6B:60
                     ESSID:""
                     Mode:Managed
                     Channel:6
                     Quality:15/100  Signal level:-84 dBm  Noise level:-97
 dBm
                     Encryption key:off
                     Bit Rates:36 Mb/s
           Cell 04 - Address: 00:14:BF:65:86:2A
                     ESSID:"INS"
                     Mode:Managed
                     Channel:7
                     Quality:20/100  Signal level:-82 dBm  Noise level:-97
 dBm
                     Encryption key:on
                     Bit Rates:11 Mb/s
           Cell 05 - Address: 00:14:7C:B1:D8:B2
                     ESSID:""
                     Mode:Managed
                     Channel:11
                     Quality:15/100  Signal level:-84 dBm  Noise level:-97
 dBm
                     Encryption key:on
                     Bit Rates:22 Mb/s

 =========Neo FR==========
 root at om-gta02:~# iwlist scan
 eth0      Scan completed :
           Cell 01 - Address: 00:21:29:8A:C5:EE
                     ESSID:"linksys"
                     Mode:Master
                     Frequency:2.432 GHz (Channel 5)
                     Quality=4/94  Signal level=-91 dBm  Noise level=-95
 dBm
                     Encryption key:off
                     Extra:bcn_int=100
           Cell 02 - Address: 00:11:88:A4:6B:60
                     ESSID:""
                     Mode:Master
                     Frequency:2.437 GHz (Channel 6)
                     Quality=4/94  Signal level=-91 dBm  Noise level=-95
 dBm
                     Encryption key:off
                     Extra:bcn_int=100

 So, the FR "sees" only 2 networks instead of 5.

 And for the strongest network, it shows Signal/Noise of -91dBm/-95dBm when
 the Eee901 shows -76dBm/-97dBm.

 I think its ok that the FR has 2dBm more noise level (smaller device, more
 compact electronics, more EMI), but it worries me that the signal level is
 15dBm lower!...

 Desired behavior: FR should identify all present networks and be able to
 connect to those that have an acceptable signal power, just like other
 mobile devices.

-- 
Ticket URL: <https://docs.openmoko.org/trac/ticket/2043>
docs.openmoko.org <http://docs.openmoko.org/trac/>
openmoko trac


More information about the buglog mailing list