CommMgrPro (Communication Manager Pro) na X500 - Cell ID problem
Nakolko som si u predchadzajuceho WindowsMobile zariadenia (bol to T-Mobile SDA Smartphone) zvykol na moznost automatickej zmeny profilu, resp. dalsich nastaveni na zaklade lokality v ktorej sa nachadzam (identifikacia podla Cell ID), hladal som nejake riesenie tejto poziadavky aj na mojej novej "tehlicke".
A nasiel som, nieco co ponuka komplexne riesenie pre moje potreby:
CommMgrPro (www.commmgrpro.com)
Sluboval som si od toho vela (skutocne toho vela aj ponuka) a tak som sa podujal stiahnut si trial verziu.
Zial po chvilke "hrania" sa, sa dostavilo zklamanie. Cell ID informacia je nepouzitelna. Zobrazuje sa stale Cell ID 14 a LAC - 51... bez ohladu na lokalitu, alebo operatora (testovane so SIM roznych operatorov). :(
Pre uplnu informaciu dodavam, ze som to instaloval na cistej WM6 ROM... po zisteni problemu som nasledne testoval na aktualnej WM5 ROM... s rovnakym vysledkom...
Mate niekto podobne skusenosti? Pripadne viete poradit iny software, ktory by vedel reagovat na zmenu Cell ID a umoznoval na zaklade tejto zmeny prisposobovat chovanie?
Doteraz som takuto moznost vyuzival hlavne na prechod zariadenia do ticheho rezimu v miestach kde je zvoniaci telefon neziaduci (banky,zdravotnicke zariadenia) a nasledny navrat do normalneho modu, po opusteni tychto miest....
A nasiel som, nieco co ponuka komplexne riesenie pre moje potreby:
CommMgrPro (www.commmgrpro.com)
Sluboval som si od toho vela (skutocne toho vela aj ponuka) a tak som sa podujal stiahnut si trial verziu.
Zial po chvilke "hrania" sa, sa dostavilo zklamanie. Cell ID informacia je nepouzitelna. Zobrazuje sa stale Cell ID 14 a LAC - 51... bez ohladu na lokalitu, alebo operatora (testovane so SIM roznych operatorov). :(
Pre uplnu informaciu dodavam, ze som to instaloval na cistej WM6 ROM... po zisteni problemu som nasledne testoval na aktualnej WM5 ROM... s rovnakym vysledkom...
Mate niekto podobne skusenosti? Pripadne viete poradit iny software, ktory by vedel reagovat na zmenu Cell ID a umoznoval na zaklade tejto zmeny prisposobovat chovanie?
Doteraz som takuto moznost vyuzival hlavne na prechod zariadenia do ticheho rezimu v miestach kde je zvoniaci telefon neziaduci (banky,zdravotnicke zariadenia) a nasledny navrat do normalneho modu, po opusteni tychto miest....
Kedze mi tato otazka nedala spavat, pokracoval som v patrani aj napriek nulovej odozve k tejto teme... Preliezol som aplikacne forum a tam som nasiel vyjadrenie autora k danej problematike:
Hi.
There are two ways to get cell id.
1) Using official WM5/WM6 api. This system should be implemented by every OEM but only a few ones have implemented it currently (HTC, HP). Others hasnt implemented it in his latest RIL version. For example, toshiba hasnt implemented it in his new device pertege G900 (I could test it days ago). When cmp calls this api simple get NOT_IMPLEMENTED. Same happens with ETEN. Hope they fix it soon because this api is Official and should be implemented. It doesnt work in wm2003
2) tweaking. Its is used by programs that works in wm2003 too (phone alarm and others) This system is oem dependent. Basically is to spy some memory positions in ril driver space. It works in wm2003, wm5 and wm6 but developer must do special code for each device and so version. Even code is different for same device, so but different rom version. So five devices need 15 different fragments of code or more. I could do it but I didnt want to start a endless road. I ve read many forums of phonealarm users saying that program didnt get correctly in their devices. I prefer to wait for RIL developers do their job.
Dani
Takze vyzera to tak, ze nas vyrobca neposkytuje podporu pre standardne Windows API... Je nejaka nadej, ze to v dohladnej dobe napravi? Alebo je potreba uzivatelov v tomto smere tak nezaujimava, ze sa to pre neho neoplati (coho sa tak trochu obavam, vzhladom na nulovu odozvu k tejto teme :? )
Hi.
There are two ways to get cell id.
1) Using official WM5/WM6 api. This system should be implemented by every OEM but only a few ones have implemented it currently (HTC, HP). Others hasnt implemented it in his latest RIL version. For example, toshiba hasnt implemented it in his new device pertege G900 (I could test it days ago). When cmp calls this api simple get NOT_IMPLEMENTED. Same happens with ETEN. Hope they fix it soon because this api is Official and should be implemented. It doesnt work in wm2003
2) tweaking. Its is used by programs that works in wm2003 too (phone alarm and others) This system is oem dependent. Basically is to spy some memory positions in ril driver space. It works in wm2003, wm5 and wm6 but developer must do special code for each device and so version. Even code is different for same device, so but different rom version. So five devices need 15 different fragments of code or more. I could do it but I didnt want to start a endless road. I ve read many forums of phonealarm users saying that program didnt get correctly in their devices. I prefer to wait for RIL developers do their job.
Dani
Takze vyzera to tak, ze nas vyrobca neposkytuje podporu pre standardne Windows API... Je nejaka nadej, ze to v dohladnej dobe napravi? Alebo je potreba uzivatelov v tomto smere tak nezaujimava, ze sa to pre neho neoplati (coho sa tak trochu obavam, vzhladom na nulovu odozvu k tejto teme :? )
Zkus phoneAlarm nebo PocketZenPhone.
