leduycuong86 / openbmap

Automatically exported from code.google.com/p/openbmap
Other
0 stars 0 forks source link

Show full cell identification data while logging #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Start logging.
2. Stay on the first tab and observe cell information.

What is the expected output? What do you see instead?
I would expect to get full cell ID, i.e. MCC, MNC, LAC and Cell ID.
Instead, I get something like "F SFR 1337353" (MCC+MNC resolved to a friendly 
name, followed by cell ID). Under some circumstances (such as using the cell 
without a SIM inserted – it will report a serving cell even though it can't 
authenticate to it) I just get "1337353" with no network info at all.

What version of the product are you using? On what operating system?
0.8.4 (from F-Droid) on Cyanogenmod 11 M11.

Please provide any additional information below.
Resolving the MCC/MNC tuple to a legible name is OK, but if the display name is 
not available, the raw MCC/MNC should be displayed as a fallback, rather than 
omitting that information altogether. (Bells and whistles: add a configuration 
option to choose between "pretty" network names and raw MCC/MNC.) Also, since 
the LAC (Location Area Code) on 2G/3G, or TAC (Tracking Area Code) on 4G, is 
part of the cell identification, it should be displayed as well. Feel free to 
borrow from the radio network tab in SatStat :-)

Original issue reported on code.google.com by mich...@vonglasow.com on 28 Mar 2015 at 9:16

GoogleCodeExporter commented 9 years ago
Sorry for the late reply..

Conducted further tests: i fear, the actual behaviour seems is ROM/device 
dependent

Nexus 4 @ ParanoidAndroid without SIM doesn't report MCC, MNC, LAC and Cell ID

>add a configuration option to choose between "pretty" network names and raw 
MCC/MNC.)
> Also, since the LAC (Location Area Code) on 2G/3G, or TAC (Tracking Area 
Code) on
> 4G, is part of the cell identification, it should be displayed as well

Makes sense..

Original comment by wish7code on 15 Apr 2015 at 9:07

GoogleCodeExporter commented 9 years ago
> i fear, the actual behaviour seems is ROM/device dependent

You mean logging without a SIM? That indeed seems to depend on the device, 
probably radio firmware and drivers, the latter of which are frequently the 
same across different ROMs. It works for me on a Nexus S (while my old 
Geeksphone One doesn't seem to report any cells with no SIM). However, logging 
without a SIM isn't necessarily a requirement – you could also try logging 
with a SIM that has been disabled (you might need to be within the network on 
which the SIM was issued) or disabling all data connectivity while logging.

If all of these fail to reproduce the issue I'm experiencing, you can always go 
for the bells and whistles and make pretty network names configurable, and/or 
fall back to MCC/MNC in case the function to look up the pretty name returns 
NULL or an empty string.

Original comment by mich...@vonglasow.com on 15 Apr 2015 at 11:37

GoogleCodeExporter commented 9 years ago
Update on logging without SIM: the Nexus S does that with no issues. Today I 
was having issues with the OnePlus One no longer recognizing the SIM. 
Radiobeacon logged all the wifis around but none of the cells. Oddly, SatStat 
gave me complete cell data – you might want to check SatStat output on the 
Nexus 4 with no SIM.

Original comment by mich...@vonglasow.com on 20 Apr 2015 at 8:40

GoogleCodeExporter commented 9 years ago
Another update: see also issue #77, which may be related. If Radiobeacon won't 
log on the Nexus 4 without the SIM but SatStat displays cell data, you might be 
experiencing a variation of issue #77.

Original comment by mich...@vonglasow.com on 21 Apr 2015 at 8:32