The MoDaCo Developer Challenge: Win an i-mate JAQ3!
#41
Posted 07 February 2007 - 02:28 PM
#42
Posted 07 February 2007 - 02:32 PM
#43
Posted 07 February 2007 - 02:34 PM
Summary:
O2 XDA Orbit - Operator Long, Operator Short, Operator Num, LAC, CID Eten M700 - Eten X500 - i-mate JasJar - Operator Long, Operator Num, Country Code, LAC MDA Vario II - Operator Long, Operator Short, Operator Num, LAC, CID P4350 - Operator Long, Operator Short, Country Code, LAC, CID i-mate SPL - i-mate JAQ3 - Operator Long, Operator Short, Operator Num, LAC, CID Loox T830 - Operator Long, Operator Short, Operator Num, Country Code QTek 8500 - Operator Long, Operator Short, Operator Num, LAC, CID i-mate SP5 - Operator Long, Operator Short, Operator Num, LAC, CID Treo 750v - LAC, CIDThat's not a bad start... on 7 of those 12 devices you could make a celltrack-type context sensitive application.
I note that a lot of the values aren't returning, and the MaxSignalStrength / BitErrorRate ones are returning the LAC/CID values.
I wonder if the 'solution' to the competition is API calls as you are doing, coupled with 'another method' for devices that aren't supporting this?
Anyone else got any other devices to add to the list? I've lent my Prophet out unfortunately, and my Excalibur!
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#44
Posted 07 February 2007 - 02:48 PM
Results as for the Eten M700... i.e 'spaces' returned for operator name etc, na/req for the rest.
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#45
Posted 07 February 2007 - 02:54 PM
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#46
Posted 07 February 2007 - 02:55 PM
http://wiki.xda-deve...name=rilgsm.dll
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#47
Posted 07 February 2007 - 02:59 PM
There is a parameter that I've set and which is the timeout for the command (the response is async). It was set to 1 sec and I saw on my Intermec CN3 that sometimes I get the response and sometimes I get ooops.
I've incremented the timeout to 4 seconds and now on the Intermec it's working well (on the library it will be a property so it can be set). So when you have time please test this on the devices that returned Oooops
RilTest_v0.0.2.zip 5.82K
371 downloadsIntermec CN3
operatorNumName:
LongName I WIND
ShortName NA/REQ
NumName 22288
CountryCode IT
cellInfo
MobileCountryCode 222
MobileNetworkCode 88
LocationAreaCode 10052
CellID 14307
RxLevel 93
RxQuality 0
signalStrength
SignalStrength 222
MinSignalStrength 88
MaxSignalStrength 10052
BitErrorRate 14307
LowSignalStrength 61
HighSignalStrength 764
#48
Posted 07 February 2007 - 03:10 PM
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#49
Posted 07 February 2007 - 03:19 PM
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#50
Posted 07 February 2007 - 03:30 PM
#51
Posted 07 February 2007 - 03:55 PM
RilTest_v0.0.3.zip 5.85K
290 downloadsP.S. The AT Command would be the most generic solution (should work on all modems), the difficult part is to find the interface to send AT Commands to the modem (maybe using the VSP returned by RIL or RIL_RegisterATCommandLogging but I have to try it). I also have to try the notification part of the RIL.
#52
Posted 07 February 2007 - 03:59 PM
SignalStrength: -77
MinSignalStrength: -113
Max: SignalStrength: -51
BitErrorRate: 4294967295
LowSignalStrength: -110
High: SignalStrength: -60
No idea what they mean
The 4294967295 value (FFFFFFFF) worries me a bit tho
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#53
Posted 07 February 2007 - 04:21 PM
#define RIL_BITERRORRATE_UNKNOWN (0xffffffff)
#54
Posted 08 February 2007 - 12:05 AM
You can download and try the new version here:
RilTest_v0.0.4.zip 7.1K
387 downloadsIn this version you will get the OOPS error if the RIL cannot be initialized or if the command is not implemented. You will get a Timeout error if I don't get an answer before the timeout I've set (now it's static set to 4 seconds). If I don't get the RESULT_OK you will see the error and finally if I have no errors you will see what the function returned.
On my Spv C600 I got the following results:
operatortLongName
LongName: I WIND
ShortName: NA/REQ
NumName: NA/REQ
CountryCode: NA/REQ
operatortShortName
LongName: NA/REQ
ShortName: I WIND
NumName: NA/REQ
CountryCode: NA/REQ
operatortNumName
LongName: WIND
ShortName: NA/REQ
NumName: 22288
CountryCode: IT
cellTowerInfo
MobileCountryCode: NA/REQ
MobileNetworkCode: NA/REQ
LocationAreaCode: 10052
CellID: 40628
RxLevel: NA/REQ
RxQuality: NA/REQ
signalStrength
SignalStrength: -51
MinSignalStrength: -113
MaxSignalStrength: -51
BitErrorRate: 4294967295
LowSignalStrength: -110
HighSignalStrength: -60
Now I can think we can re-run the tests. Sorry Paul for the errors I had in the previous versions.
#55
Posted 09 February 2007 - 02:53 AM
Dopod 838Pro (HTC Hermes 100) results using 0.0.4:
operatortLongName
LongName: Telstra Mobile C
ShortName: NA/REQ
NumName: NA/REQ
CountryCode: NA/REQ
operatortShortName
LongName: NA/REQ
ShortName: M-NET
NumName: NA/REQ
CountryCode: NA/REQ
operatortNumName
LongName: Telstra sux ass
ShortName: NA/REQ
NumName: 50501
CountryCode: NA/REQ
cellTowerInfo
MobileCountryCode: NA/REQ
MobileNetworkCode: NA/REQ
LocationAreaCode: 276
CellID: 8971
RxLevel: NA/REQ
RxQuality: NA/REQ
signalStrength
SignalStrength: -43
MinSignalStrength: -113
MaxSignalStrength: -51
BitErrorRate: 4294967295
LowSignalStrength: -110
HighSignalStrength: -60
Note that the operatortNumName/LongName has come from the registry change I have mode myself.
C
#56
Posted 12 February 2007 - 02:34 PM
#57
Posted 12 February 2007 - 02:40 PM
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#58
Posted 22 February 2007 - 11:16 AM
Have Fun,
Dan
RilTest.zip 18.35K
431 downloads
#59
Posted 22 February 2007 - 11:35 AM
P
You can follow me on Twitter - http://twitter.com/paulobrien / Follow MoDaCo on Twitter - http://twitter.com/modaco / Follow MoDaCo Android on Twitter - http://twitter.com/modacoandroid
Want to donate? MoDaCo is raising money for the Multiple Sclerosis society.

#60
Posted 05 March 2007 - 09:23 AM
Thanks
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users






Sign In
Create Account

Back to top









