Months ago I asked about this here, and no one seemed to know how to get the cellular radio info (cell ID, dB strength, etc.). After more searching around the net, I finally found it.
On some WM phones there is a utility called FieldTest.exe in the /Windows folder. I didn't see it on my Athena, so I searched the net. You can get it here, after registering with that board:
http://discuss.treocentral.com/attachment.php?attachmentid=16140&d=1200066698
Note, there are two versions available on the net, the newest one shows "CellID" at the bottom of the "WCDMA" screen. Older versions don't, so if you look for it yourself, make sure you see "CellID". Once you get the file, place it in the /Windows folder.
You can also find a manual that explains some of what the various screens mean. :
http://forum.xda-developers.com/showthread.php?p=1079220
1. Once you get the file, place it in the /Windows folder.
2. Reboot.
3. Either run the file directly, or go into the phone and dial *#*#364#*#* (don't press send); within a few seconds the app will run.
4. You may need to add the following keys to \HKLM\Software\HTC\EngineerMode and then reboot before it will work:
- BuildInEngineeringModeApp with a value of 1 (try this by itself before trying the next key)
- LaunchEngineerModeAppDialStr with a value of *#*#364#*#* (or whatever you want)
Quirks I've noticed:
- not all fields are populated, even when they should be
- I can only get most of the fields populated after a reboot (or restarting the phone radio), the first time I run fieldtest.exe; after re-running it most fields are bad and I have to reboot; I've also found that it seems to stop updating some fields within seconds of running
- even when I get the fields to populate, some don't appear to update in real-time like the Nokia screens do even when I set the program to update every second
- "RSSI 1" should show the dB signal level, but is one of the fields that isn't reliable
- "RSSI" is a reliable signal strength, but doesn't show dB; values appear to be between 0 and 40, with 40 around -50 db (excellent) and 1 over -100 dB (horrible); I get 2 "bars" in the teens and 4 "bars in the 30's; my old Nokia at home has the Net Monitor active and I'll compare dB values tonight.
- some things that I'm used to seeing on the Nokia's net monitor isn't here, like Frame Error Rate, which is a dropped bit (noise) measurement of the current and neighboring cells
I mostly wanted this functionality because receiver dB is far more accurate than "bars". It seems I can get get close to this via "RSSI". Irritating that the proper dB reading should be shown in "RSSI 1" but often isn't. So, please update me on your experiences. If you find a version of fieldtest.exe that appears to be more accurate, PLEASE post it here. Thanks.
Did more testing last night. Turns out FieldTest was pre-installed on my wife's Tilt, and works properly on her stock WM6 ROM. I wonder if AP4 is giving me trouble, or if others find the same problems on the Athena.
Since the application was working correctly on her ROM, I spent some time getting various RSSI & RSSI 1 readings, and made a conversion table. Useful if you are only getting the internal RSSI value, and not the converted (to dB) RSSI 1 value like I am. From 4 years of always tracking my dB readings on my old Nokia, I added my own interpretation of good vs. bad signal, although the receiver seems to be more sensitive on the Athena so we will probably get better results than what I indicated from my Nokia. I may adjust this later. Note that I found the dB reading could be +/- 2, I just recorded the value I saw most often.
RSSI / RSSI 1 (dB) / my interpretation
------------------------------------
10 -109
11 -107
12 -105
13 -103
14 -101 unusable ^
15 -99
16 -97
17 -95
18 -93
19 -91 possibly useable for voice ^
20 -88
21 -86
22 -84
23 -82
24 -80 good signal ^
25 -78
26 -76
27 -74
28 -72
29 -71
30 -69 excellent signal ^ (continuing to -50 db)
I couldn't get readings better than -69 or worse than -109, if I see these values in the future I'll update. However, in the real world anything worse than -100 is unusable anyway, and anything better than -75 is perfect so extending the chart wouldn't be very useful.
This might prove very useful. I have serious connection problems at home and therefor must buy an external GSM antenna..the DB strength indicator could help me a bit in finding an optimal antenna. Thanks for the info.
will_990 said:
This might prove very useful. I have serious connection problems at home and therefor must buy an external GSM antenna..the DB strength indicator could help me a bit in finding an optimal antenna. Thanks for the info.
Click to expand...
Click to collapse
That is exactly what first got me interested in Nokia's Net Monitor (and a long standing interest in ham radio). Using it I could verify that an external antenna I bought for my Nokia boosted the signal by -12 dB. Far more accurate than saying "I think I got one extra bar." I bought a new adapter for that antenna for my Athena, but I've found the Athena has such a sensitive receiver I don't use the antenna with it.
Hi! Some of you might recognize me from the WinMo/WinPho world. I just picked up a Captivate and i'm having the same GPS issues we all are. I noticed there's a distinct lack of raw, verifiable data regarding the issue. Nearly everything is anecdotal observations.
Please do NOT post any observational data here (example: I changed xxx and yyy setting, and now my GPS works great! Tracking is spot on!) - these posts, if not based on provided raw data, will be deleted.
Please DO post raw data (lbstestmode readings, NMEA strings, sensor output, adb logcat output, My Tracks, comparisons vs. other GPS with raw data, etc.) - also, feel free to post observations based on this raw data.
[size=+2]Apps i'm using to gather this data:[/size]
[size=+1]Android Apps[/size]
LbsTestMode: Comes with just about any ROM. Use "Any Cut" from the market to make a shortcut to it, make sure your settings match those below (unless intentionally testing others) and press "Get Position Test". If you are going to post satellite signal values, it's easiest to take a photo and type the values in from the photo, as the signal strengths vary from moment to moment.
My Tracks: This google app records a track of your GPS location, updating every 1s (unless you haven't moved beyond a small threshhold) - You can then upload this data to google maps and link it as I did in post 2. Unfortunately this method does not record any NMEA data (so we can't see signal strength, etc.) But serves will to see how accurately the tracking is.
Bluetooth GPS Provider: Used along with the "Allow Mock Locations" setting in Settings - Applications - Development to allow the phone to pull location data from a tethered bluetooth GPS such as the BT338. Note that this program will show satellite signal strengths as a bar, without actual dB readings. The program listed below provides more data, but performs a bit worse over time.
Bluetooth GPS: This program provides the same functionality as the app above. However, it provides much more diagnostic data such as signal strength readings, Satellite Constellation View, and raw NMEA output.
[size=+1]PC Apps[/size]
SirfDemo: Used along with a bluetooth module to connect to my BT338 GPS on the laptop. You can see a screenshot of this app in the photo below. It also displays raw NMEA data and allows logging.
[size=+2]GPS Settings[/size]
These are the settings that i'm using for testing. If your settings vary, please post along with the data so we can have a complete picture. The ROM/Radio/Kernel you're using is important too Also note any tweaks you may have made to gps configurations (using lbstestmode, jupiter.xml, et al.)
IMPORTANT: Use the "Delete GPS Data" button in LbsTestMode immediately prior to conducting any tests, and ensure to use standalone/cold start. This will remove all cached assistance data and ensure the GPS isn't affected by external effects.
Da_G said:
Application Settings
Session Type: Tracking
Test Mode (S/W or H/W): S/W Test
Operation Mode: Standalone
Start Mode: Cold Start
GPS Plus: ON
Dynamic Accuracy: ON
Accuracy: 50
GPS Logging: (optional)
SUPL/CP Settings
Server FQDN Type: AUTO Config
Server: (greyed out, default)
Server Port: (greyed out, default)
SUPL Secure Socket: ON
AGPS Mode: SUPL
Click to expand...
Click to collapse
I'll go first!
This is my test setup for the data in this post. You can see most of the output there on the screen. (I'll type it up for readability too) - There's about a 110 degree clear sky view, overcast. There is probably some minor multipath from the 2 story buildings nearby.
Phone setup is my own custom ROM (based on the recent Vibrant Froyo leak, with Cappy JH7 bits tacked on to address the various incompatibilities), JK3 baseband, Setiron 1.4.3 1200mhz kernel.
Format below is:
PRN of Satellite : Signal Strength : Used in Fix?
BT338 Standalone GPS (Tethered to laptop)
SV 5 : C/No 00
SV 6 : C/No 00
SV 15 : C/No 21 *
SV 16 : C/No 21 *
SV 18 : C/No 33 *
SV 21 : C/No 34 *
SV 22 : C/No 18 *
SV 25 : C/No 00
SV 26 : C/No 32 *
SV 29 : C/No 30 *
SV 30 : C/No 16 *
Captivate1 (Standalone internal GPS, to the left of BT GPS in photo)
SV 6 : C/No 13
SV 15 : C/No 23 *
SV 16 : C/No 19 *
SV 18 : C/No 32 *
SV 21 : C/No 12
SV 22 : C/No 19 *
SV 26 : C/No 21 *
SV 29 : C/No 33 *
SV 30 : C/No 11
Captivate2 (Standalone internal GPS, to the left of BT GPS in photo)
SV 6 : C/No 14
SV 15 : C/No 26 *
SV 16 : C/No 16 *
SV 18 : C/No 33 *
SV 21 : C/No 32 *
SV 22 : C/No 20 *
SV 26 : C/No 29 *
SV 29 : C/No 33 *
SV 30 : C/No 11
Some notes and observations:
I took 4 photos a few seconds apart from this angle to look at the signal fluctuations. You might notice Captivate1 SV 21 is an anomaly (12dB). The signal shows majorly degraded from the BT GPS and the Captivate2. Appx. 4 seconds before, the phone was getting 23dB on that satellite. The BT GPS and Captivate2 both remained at the same level (34dB, 32dB) - that might indicate some antenna issue after all, perhaps a marginal connection in some units. I'll do some more extensive comparison between these 2 units while I have them (2 or 3 days)
Here are 3 different MyTracks I took yesterday while driving: both GPS units on the dash.
AT&T Captivate Track:
http://maps.google.com/maps/ms?hl=e...26965825393652.000496745b69eeef7de5f&t=h&z=14
BT338 GPS Tethered to Captivate Track:
http://maps.google.com/maps/ms?hl=e...26965825393652.00049673fd50c60e8d690&t=h&z=14
Both Tracks overlaid (anyone know how to get one track as a different color for better visibility? I know you can in g earth..)
http://maps.google.com/maps/ms?hl=e...09,-117.346945&spn=0.053451,0.065746&t=h&z=14
[size=+2][Edit: Forgot to add, here is some data on fix times.][/size]
GPS in Standalone operation - Cold start
BT GPS - 59s
Cappy1 - 19s
Cappy2 - 16s
GPS in Standalone operation - Warm Start
BT GPS - 32s
Cappy1 - 12s
Cappy2 - 9s
GPS in AGPS operation - Hot Start
BT GPS (no AGPS, hot start only) - 3s
Cappy1 - 7s
Cappy2 - 5s
Interesting to note is that the 2 Captivates running the same software, used in the same position/enviornment, and trying to get a fix at the same time, Cappy2 consistently performs better than Cappy1. This again may point to some design-time issues with the GPS Antenna.
What software are you using to collect this data?
I'll post it in the first post, as i'm sure others will want to know too Look there shortly.
If we all post as replies to this thread that could get really cumbersome and hard to track.
Might I suggest another submission method?
Lol don't have time to do it but if you really wanted to get this done right you could code an algorithim that calculates average distance away from a street in my tracks... use that to generate a gps performance score... and use those gps performance scores to generate an average with standard deviations/ 95% confidence intervals.
That, would be so cool!
Sent from my SAMSUNG-SGH-I897 using XDA App
It would be great if there was so much data to be had that it was hard to track. Right now the situation is exactly opposite of that Bring it on! We can worry about managing the flood of data later, when there is a flood of data.
The problem with calculating an average distance like that is that it won't factor in enviornmental factors. The GPS might perform great with a 110 degree sky view and minimal multipath, with a 110 degree sky view and a mountain nearby, it might go bonkers. Due to the frequency range and transmission type, GPS signals are very prone to enviornmental factors. (These same weaknesses are also their strength in being so accurate in the right enviornment)
Updated first post with info about the apps I used.
This may count as anecdotal, but...
You asked for My Tracks data... something I have noticed is that, for me at least, My Tracks wil be pretty damb accurate if running in the background, while navigation or maps can't track well I the foreground at all. In fact, even My Tracks won't do well in the foreground. Not sure what this means, but liking forward to any developments on this front.
Sent from my SAMSUNG-SGH-I897 using XDA App
Dam Da_G great to see you. Long time since I have worked with wm but always enjoyed making roms from your leaked builds. I will work on collecting gps data. I do onsite IT work so I will log gps all day and post back when I get a few days of data.
Good to see you too shep Re: WM, The King is dead! Long live the King
Updated post 2 with some more interesting data regarding lock times. Re: My Tracks and performance in foreground/background, i'll slate that test for tomorrow. I think you're wondering if the CPU usage may have something to do with accuracy? It's certainly possible but if most of the calculations are handled in the baseband like I think, not likely. Either way, tomorrow's test will answer that
i'm not sure if this is the data you want but i matched all lbstestmode settings as yours, and did 3 position tests, took screen shots right after sat locked.
hope this useful...
here's my cappy's setup.
Rom : Perception Build 5
Kernel : SetiroN's v1.4.3 1350 Mhz OC'd
and here's the results
First Test
SV 22 : C/No 35 *
SV 06 : C/No 35 *
SV 03 : C/No 35 *
SV 09 : C/No 33 *
SV 19 : C/No 32 *
SV 14 : C/No 29 *
SV 21 : C/No 28
SV 27 : C/No 13
Second Test
SV 06 : C/No 37 *
SV 03 : C/No 36 *
SV 22 : C/No 35 *
SV 14 : C/No 33 *
SV 19 : C/No 32 *
SV 21 : C/No 30
SV 09 : C/No 28
SV 18 : C/No 11
Third Test
SV 03 : C/No 34 *
SV 22 : C/No 32 *
SV 06 : C/No 32 *
SV 19 : C/No 31 *
SV 09 : C/No 30
SV 14 : C/No 28 *
SV 21 : C/No 23
SV 18 : C/No 13
Screen Shots
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Perception Build 6 w/ JM9 gps files
Indoors - Currently clear skies
SV 18 : C/No 33 *
SV 12 : C/No 32 *
SV 22 : C/No 31 *
SV 25 : C/No 30 *
SV 09 : C/No 30 *
SV 14 : C/No 26 *
SV 21 : C/No 23 *
SV 27 : C/No 22 *
SV 15 : C/No 20 *
SV 31 : C/No 18 *
born_fisherman said:
Perception Build 6 w/ JM9 gps files
Seeing how well this works with xda app:
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
can't enlarge the image...
Great post, drancid. What was the enviornment like at the time? How far apart were the fix attempts? All on the same device?
I'm guessing it was indoors or with a partially blocked view of the sky?
@born_fisherman:
Looks like it was just a thumbnail that uploaded. No link to a larger photo, and the text is too small to read
Da_G said:
Great post, drancid. What was the enviornment like at the time? How far apart were the fix attempts? All on the same device?
I'm guessing it was indoors or with a partially blocked view of the sky?
Click to expand...
Click to collapse
thx.
yes, results from my cappy. just have one device.
about 2 minutes interval.
tested in my back yard. big tree and two story houses were near me but cappy was facing clear sky.
updated my post - The JM9 files work wonders. Oh, I also have SUPL Secure Socket ON
Ok, I'm indoors. Waited 5 minutes between tests. One device.
ROM - di11igaf's UGJK3, MODEM - JK3, KERNEL - SetiroN 1280 1.4.3
Gps Fixes - Jupiter V006 + JM9 Files
TEST 1
PRN: 25 CNo: 35
PRN: 31 CNo: 34
PRN: 22 CNo: 34
PRN: 18 CNo: 29
PRN: 14 CNo: 20
PRN: 30 CNo: 19
TEST 2
PRN: 25 CNo: 32
PRN: 22 CNo: 31
PRN: 31 CNo: 28
PRN: 30 CNo: 28
PRN: 24 CNo: 23
PRN: 18 CNo: 22
PRN: 14 CNo: 18
majinzen said:
Ok, I'm indoors.
ROM - di11igaf's UGJK3, MODEM - JK3, KERNEL - SetiroN 1280 1.4.3
Gps Fixes - Jupiter V006 + JM9 Files
TEST 1 TEST 2
PRN: 25 CNo: 35 PRN: 25 CNo: 32
PRN: 31 CNo: 34 PRN: 22 CNo: 31
PRN: 22 CNo: 34 PRN: 31 CNo: 28
PRN: 18 CNo: 29 PRN: 30 CNo: 28
PRN: 14 CNo: 20 PRN: 24 CNo: 23
PRN: 30 CNo: 19 PRN: 18 CNo: 22
PRN: 14 CNo: 18
Click to expand...
Click to collapse
Since you are using the JM9 files, use Supl.google.com / 7276 to get better results
I've tried both and I get better or equal results with this config. Sometimes supl.google.com takes forever to lock on for me.
See, that is really what I would like to find out more about the GPS - why it's different for others and why it isn't consistent!
Assonance 2.0 (stock = supl.google.com 7276, secure socket off, standalone, hot start, http://forum.xda-developers.com/showthread.php?t=856877)
#1007
sitting near a window with a clear view of the sky
TTFF 15s
Accuracy: 25.0 m
PRN 31 = 28*
PRN 23 = 22*
PRN 32 = 21*
PRN 24 = 21*
PRN 20 = 21*
PRN 11 = 21*
PRN 14 = 18*
PRN 30 = 17*
5 min later:
TTFF 15s
Accuracy 15.0 m
PRN 32 = 30*
PRN 20 = 29*
PRN 31 = 25*
PRN 24 = 25*
PRN 11 = 24*
PRN 30 = 20*
PRN 23 = 14
PRN 14 = 13
FWIW, this setup tracks very well on some car trips, less well on others.
What clues can you get from seeing our signal strengths, besides that it's erratic..?
Choosing the best Wifi Channel
I've searched through the forums, but don't think this subject has been previously raised.
So, just to simplify this problem, let me demonstrate with a specific example.
Let's say in my vicinity there are four Wifi APs.
Two running Channel 1, and the other two Channel 6.
Now, common sense will tell you to choose Channels 2, 3, 4, or 5, to prevent conflict with other APs.
But, this is where the problem starts.
Though Channels 2/3/4/5 are running on different channels, their actual frequency ranges overlap with each other, including with 1 and 6 (note that Channels 1 and 6 themselves don't overlap each other). Thus, this means that if I choose Channels 2/3/4/5 I'll have all four of my neighbouring APs overlapping with mine.
Wouldn't this be worse than choosing either 1 or 6, since if I choose either of these, I'll only have two APs conflicting with mine.
You are very much correct. Using the 2.4GHz ISM band, only use channels 1, 6 and 11.
Read more at http://www.cisco.com/en/US/docs/wireless/technology/channel/deployment/guide/Channel.html
Basically the channels bleed over 4 channels worth (I think) of frequency. 1, 6, and 11 are far enough apart to avoid this bleedover. So if someone has a channel 2 wireless signal it will affect channel 1. If someone has a channel 5 signal, it will affect channel 1 (I'm pretty sure, it's been a few years since my Wi-Fi college class).
Slow wifi on cm10 on GT 7 p1000
I have searched to death, but cant find a solution or actual discussion on this.
MY p1 is on;-
Baseband ver. P1000XXJPZ
kernel ver. 2.6.35.13-go6bec8e
[email protected],,,,mod#1
Wed Sep 2604:17:41 PDT 2012
Build nr. cm_p1-userdebug 4.1.1 eng..20120926.040310 test-keys
performance settings are default- Too scared to touch!
The problem is that wifi is slow, i.e. speedtest.net app shows normal speed, yet ACTUAL performance is very slow. For instance, connecting to the same network and going to the same site, such as Cm 10 nightly downloads, takes about twice as long on my tab as on HTC Desire S or laptop. This goes for most sites and apps including BBC News, Pulse, Bloomberg etc . Even though I'm a newbie, dummy on tech, especially according to my children, I have run cm9 and have flashed every cm10 nightly since they started. Yes, I use it as a daily driver and whilst I got close to going back to cm9, I'm NOT.
So far the wait has been great. I love cm10 and everything I need now works, apart from WiFi tethering. (Does USB tethering work?) It's just this slow wifi that bothers me, if there's any help out there.
3G/HSDPA works fine, fast and smooth. Thanks to everyone for all the great work(cdesai, jenkins, many others)! Even us older, non-tech guys like bloat-free smooth OS'.
In a series of two blog posts, the Google Project Zero team showcases how a popular WiFi SoC, Broadcom BCM4339, broadens the attack surface. Such SoCs generally garner little scrutiny.
This chip, found in Nexus 5 and also in Zenfone 2, also processes BlueTooth and FM Radio communications. GPZ also says it is applicable to other chips from this product line.
One of the vulnerabilities, registered as "Google Android CVE-2017-0561 Remote Code Execution Vulnerability" and tracked as Android bug ID A-34199105, allows remote code execution (RCE) on the Cortex-M4 based processor (32-bit Thumb2 ISA).
This particular exploit requires the victim having WiFi turned on, and knowing their MAC address (which is not particularly hard to do).
Specially-crafted "TDLS" packets trigger a heap overflow, further allowing code execution. Attacker does not need to join access point AFAICT.
Nexus 5's 6.37.34.40 is vulnerable according to exploit-db (and possibly won't receive a fix)
Here are a couple of version strings found in /system/etc/firmware/fw_bcmdhd.bin on zen2:
4.21.40.134: 4339a0-roml/sdio-ag-pool-p2p-pno-pktfilter-keepalive-aoe-sr-mchan-proptxstatus-lpc-tdls-autoabn-txbf-rcc-wepso-okc-ndoe-wls-mfp-wl11u Version: 6.37.34.22 CRC: 159e79c5 Date: Fri 2015-04-10 00:43:19 PDT Ucode Ver: 855.1041 FWID: 01-41260e22
4.21.40.223: *unknown*/sdio-ag-pool-p2p-pno-pktfilter-keepalive-aoe-sr-mchan-proptxstatus-*unknown*-*unknown*-*unknown*-medioctl-dhdcs-ve-(null)-... Version: 6.37.45.0 CRC: c2000704 Date: Wed 2016-01-06 15:44:26 CST
Fixed in:
Android Security Bulletin—April 2017 "This issue is rated as Critical due to the possibility of remote code execution in the context of the Wi-Fi SoC."
References:
Part 1 - https://googleprojectzero.blogspot.com/2017/04/over-air-exploiting-broadcoms-wi-fi_4.html
Part 2 - t.b.a. "In the next blog post, we’ll see how we can use our assumed control of the Wi-Fi SoC in order to further escalate our privileges into the application processor, taking over the host’s operating system!"
Bug opened in January 2017 - https://bugs.chromium.org/p/project-zero/issues/detail?id=1046
http://www.securityfocus.com/bid/97054/discuss (another vuln briefly mentioned in the blog post)
I'm sure will get a security update soon, because the Zenfone 2 is still in the window for "Two years of scheduled automatic monthly Android M security and software updates." (and also this thread).
Oh no, wait Asus deleted that commitment from their post.