Guest dan.ardelean Posted January 22, 2007 Report Posted January 22, 2007 What is the deadline for the contest?
Guest dan.ardelean Posted February 7, 2007 Report Posted February 7, 2007 Since I saw the contest I had the obsession that one of the solutions will be to invoke the ril.dll. I've been working for a couple of days to develop an interface to the ril in compact framework 2. The solution is far from being finished, but I am sending, attached, a test program. I am really interested of the results you will get. The exe program works also on smartphone (it only uses a menu and messageboxes). If you get the "ooops" error it is probable that on your device the program needs a certification to run. You can change those settings using the Device Security Manager from Microsoft which can be downloaded from this link: http://www.microsoft.com/downloads/details...;DisplayLang=en. After you test the program you can go back to your old settings (you have to save the settings before provisioning the No security setting). You will also need compact framework 2.0 installed on the device. I've tested on a SPV C600 and Qtek S100. On the fields you get NA/REQ means Not available or requested. Let me know the results, Dan RilTest.zip
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 XDA Orbit: operatorLongName: T-Mobile operatorShortName: TMO UK NumName: 23430 LocationAreaCode: 256 CellID: 21012 SignalStrength: NA/REQ MinSignalStrength: NA/REQ BitErrorRate: 21012 LowSignalStrength: NA/REQ HighSignalStrenth: NA/REQ Looks promising... running it now on every device I can lay my hands on (that's quite a few!) P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Eten M700: operatorLongName: operatorShortName: NumName: All other fields: NA/REQ I guess this is a symptom of the Eten RIL rather than the HTC RIL... P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 i-mate JASJAR ("special build"): operatorLongName: T-Mobile operatorShortName: NA/REQ NumName: 23430 CountryCode: GB LocationAreaCode: 256 Ooooops error (CellTowerInfo) Ooooops error (signalQuality) Device IS fully app unlocked. P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 MDA Vario II: operatorLongName: T-Mobile Person operatorShortName: TMOUK NumName: 23430 CountryCode: -- LocationAreaCode: 256 CellID: 21012 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 256 BitErrorRate: 21012 LowSignalStrength: NA/REQ HighSignalStrenth: NA/REQ
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 HTC P4350: operatorLongName: T-Mobile operatorShortName: TMOUK NumName: 23430 CountryCode: GB LocationAreaCode: 256 CellID: 21012 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 256 BitErrorRate: 21012 LowSignalStrength: NA/REQ HighSignalStrength: NA/REQ HighSignalStrenth: NA/REQ
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 i-mate SPL 'Ooooops' error on everything, so i'm guessing it's not fully unlocked properly, despite my best efforts... :) P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 i-mate JAQ3 operatorLongName: T-Mobile operatorShortName: TMOUK NumName: 23430 CountryCode: NA/REQ LocationAreaCode: 66 CellID: 36893 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 66 BitErrorRate: 36893 LowSignalStrength: NA/REQ HighSignalStrength: NA/REQ HighSignalStrenth: NA/REQ Gotta say, this one surprised me... didn't expect it to work! :) P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Fujitsu Siemens Loox T830 operatorLongName: T-Mobile 2G operatorShortName: TMOUK NumName: 23430 CountryCode: GB Ooooops error (CellTowerInfo) Ooooops error (signalQuality) Started off so well! :) P
Guest johncody Posted February 7, 2007 Report Posted February 7, 2007 (edited) ... to develop an interface to the ril in compact framework 2. Curious, is there any technical reason why you used the CF2 and not CF1? I'm only asking because with CF2, it requires the end user to install a huge 5MB CF2 runtime, and using CF2 prevents this solution from running on 2003 devices. Edited February 7, 2007 by johncody
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Qtek 8500 operatorLongName: T-Mobile operatorShortName: TMOUK NumName: 23430 CountryCode: NA/REQ LocationAreaCode: 256 CellID: 21012 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 256 BitErrorRate: 21012 LowSignalStrength: NA/REQ HighSignalStrength: NA/REQ
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 i-mate SP5 operatorLongName: T-Mobile operatorShortName: TMOUK NumName: 23430 CountryCode: NA/REQ LocationAreaCode: 256 CellID: 21012 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 256 BitErrorRate: 21012 LowSignalStrength: NA/REQ HighSignalStrength: NA/REQ
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Palm Treo 750v (with Vodafone SIM) operatorLongName: NA/REQ operatorShortName: NA/REQ NumName: NA/REQ CountryCode: NA/REQ LocationAreaCode: 193 CellID: 17683 RxLevel: NA/REQ RxQuality: NA/REQ SignalStrength: NA/REQ MinSignalStrength: NA/REQ MaxSignalStrength: 193 BitErrorRate: 17683 LowSignalStrength: NA/REQ HighSignalStrength: NA/REQ
Guest dan.ardelean Posted February 7, 2007 Report Posted February 7, 2007 I used CF2 because I needed callback functions which are not implemented in CF1. Anyway it works fine on WM 2003.
Guest johncody Posted February 7, 2007 Report Posted February 7, 2007 I used CF2 because I needed callback functions which are not implemented in CF1. Anyway it works fine on WM 2003. Do you have a 2003 PPC or a 2003 SP?
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 That's enough messing around with devices I think :) 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, CID[/code] That'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! :D P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Eten X500: Results as for the Eten M700... i.e 'spaces' returned for operator name etc, na/req for the rest. P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 I'm talking to Eten about the T-Mobile GPRS problem atm, so i'll ask them why RIL_GetCellTowerInfo and RIL_GetCurrentOperator don't work too :) P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Here's an interesting page... wonder if the functions work on the Eten etc. via AT commands? http://wiki.xda-developers.com/index.php?pagename=rilgsm.dll P
Guest dan.ardelean Posted February 7, 2007 Report Posted February 7, 2007 Ooops Ooops 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 Intermec 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
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 For test purposes, could you add an option where you hit the menu button, and it dumps all that stuff to a text file? :) P
Guest Paul (MVP) Posted February 7, 2007 Report Posted February 7, 2007 Still rather odd results for signal strength etc... on my MDA Vario II the SignalStrength returns 234 (first part of network ID), MinSignalStrength the other MaxSignalStrength returns the LAC, BitErrorRate the CID. :) P
Guest dan.ardelean Posted February 7, 2007 Report Posted February 7, 2007 Mea culpa again. Looks like I am sleeping :) I have to modify the exe. Cannot blaim (I was programming at 2 o'clock in the morning). Modify right away
Recommended Posts