Related
Hi all.. This is my first post so obviously this is a newbie question! My XDA 2s is not able to recognize the name of my mobile operator here in India, and it shows up as "40468". Is there any tweak by which I can manually feed in the name of the operator so it shows up on the Phone screen?
Just to explain the issue clearly - the number on the top right is where the name of the mobile service provider should show up. Why does it show up as a number (40468) and not as a name, as it did on my Sonyericsson P910i, or indeed other phones? Grateful for any help in this matter.
It's because basically each mobile phone operator is allocated a number (in your case 40468) and inside each phone is a tiny database of operator names/numbers.
I used to think that the operator "sent" the name, but a few years ago now a UK operator changed it's name from "Cellnet" to "BT Cellnet" and then to "O2", however phones wouldn't change. But if you had a newer version of firmware on your phone it would change (so that supports my theory that the database is in the firmware).
I think this also make sense because the operator isn't going to know how many characters are available for showing the name/abbreviating as necessary and so it makes sense for the mobile phone providers to keep their database in sync with the "main" one for who is allocated what as it'll make sure the information is displayed correctly as they can abbreviate as needed for each device.
At least that's how I understand it. So in your case it sounds like your phone doesn't know your provider. Perhaps a newer upgrade might help (1.33 or 1.40?), but I'd just ask your provider. If they sold you the phone it's pretty weird it doesn't support their own network. It might just be a faulty handset :-(
Perhaps post the name of your operator and we can see if anyone else is using them and it works for them
Neil -- many thanks for your reply. When I bought this phone (unlocked) from Kuala Lumpur, it wasn't as yet available in India. Now it is, though. Maybe thats why it doesn't show up all of India's mobile service providers. Anyway, my mobile provider is MTNL in Delhi.
Upgrading ROM to 1.40 may solve the problem, provided its and "Asia" ROM. Is that available yet? Is it possilbe to "cook" the rom to add service providers?
Many thanks for your help Neil.
Well you're using PH20B which is same as my phone is here in the UK and I'm running the 1.40 ROM so technically you shouldn't any problems. I'd wait for someone else to just verify either that A) What I've said about being stored in the phone is correct or B) Some one using MNTL in Delhi to confirm they have/haven't got this problem.
Because if it's a case of it's fine for them and ROM's are same etc it might be a faulty unit (can't really see how!) and a ROM upgrade might not help and since technically these ROM upgrades aren't always official (1.40 probably isn't) you'd probably have to put it back/find previous ROM before you could take it back.
Upgrading to 1.40 isn't really a pain, see the WIKI (top left) it's daunting at first, but it's actually very easy to do, but do it when you have enough time to reinstall everything because doing any sort of ROM upgrade does a hard reset as well (wipes everything in main memory - \Storage and \Storage Card are safe).
I can't guarentee that this would fix your problem, i.e. your provider is in that ROM, but not sure what else to suggest + 1.40 does come with Media Player 10 which is a bit of an added bonus! You can backup your existing ROM, although it's probably already on the FTP, might be handy to have it in advance if you want to go back.
Hope that was some help!
P.S. If you decide to go down the upgrade route, probably worth upgrading your radio at the same time. I'm all the way to 1.12 and it's fine for me, but some people seem to have stayed with 1.10 because they've had some issues - search forum on this)
Neil -- two quick comments.
One, from using cell phones for the last many years, I feel that the code to decipher the cell provider's number is in the phone. This has happened to me before, when I bought phones which were not available in India, and it's happened again! It seems to me it's a ROM issue, as its logical for cell providers to be consistent (i.e. broadcast their identification numbers) and let the phones decipher them.
Two, is there any major danger that I'll lose the phone itself with a ROM upgrade? I know this has been answered in some other threads of this forum, but it'll be a first for me on this newly acquired beauty!
Cheers and many thanks....
example:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
"45404"="3-DUALBAND-"
Hehe, big mamaich spoke... :lol:
Yup, those are PPC's: many things can be done by software... :wink:
This is odd...
Since I upgraded my MDA2 to 2.06.00WWE Radio: 1.14.00 I've seen this problem where the carrier name was changed to a number (in my case 334020).
On my previous ROM version I had no problem at all. And this device does not even exsist in Mexico and it displayed the carrier name (Telcel) without a problem.
I think the carrier name is taken from the network itself and fed to the registry but this particular ROM has problems taking this particular carrier numbers.
If I do a network search I can see the other carrier in my area (Movistar as a number also) and two other United States Carriers (Cingular and AT&T) but this time with their names (I live close to the United States).
To "fix" this I created a GIF file named carrierlogo.gif and place it on the Pocket PC Windows directory and now it shows a nice Telcel logo instead!...
@ Rayan
that looks good! Could you please explain how you did it? The first step obviously was to place it on the Pocket PC Windows directory, but what were the other fixes? Did you tweak the registry? Newbie question... I've been a XDA 2s user only for a few weeks Rayan!!
mamaich said:
example:
Code:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
"45404"="3-DUALBAND-"
Click to expand...
Click to collapse
Mamaich speaks loud and clear! Yup, adding that additional string did the trick! I created a string for my carrier ("40468"="MTNL"), did a soft reset and Voila! It worked! Thank you Mamaich, thank you forum!!
Hi Dilip,
I tried the trick on my PDA2k, but not worked..can u pls elaborate how u hv added the string....or made a new key value in the registry?
hdubli said:
Hi Dilip,
I tried the trick on my PDA2k, but not worked..can u pls elaborate how u hv added the string....or made a new key value in the registry?
Click to expand...
Click to collapse
it works and thanks to mamaich (he is the greatest) i tried it on my imate jam and worked like a charm.... all u have to do is navigate to
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\RIL\OperatorNames]
using any registry editor like resco..... once u reach OperatorNames create a STRING VALUE
in the Name box write the number that shows in ur dialing pad and in the String box write the name of the operator or any name u want ..... look at the pic ... and u can write it in any lang u want
As shown by PapaDocta above, I added a string to my registery and this is how my phone looks now:
Hi!!!
Thaks, now it worked...I was trying to make a new key value and what not.....but never knew that it was so simple.
Thanks a ton..This helps very much during roaming...
hey guyz..
the scene is set, dont want to tell anyone where it happened by whom and ofcourse who got robbed but here's the story.
User had an o2 Xda II, customized rom, with IIWPO Theft Control installed in the rom, so that means hard reset wont wipe IIWPO out of the pda.
Robber comes puts a knife on the user's throat takes away cash and the pda, user gives it happily thinking she will get a msg on the other number with all the info of sim changed.
4 days pass by no info come's and the pda is sold or forwarded to someone else or whatever. END OF STORY.
now how did the user not get a msg of the new sim info.
1. SIM WAS NOT CHANGED.
2.SIM CHANGED BUT NO CREDIT IN NEW SIM.
3.BATTERY TAKEN OUT PDA TOTALLY DEAD TILL NEW CUSTOMER GETS IT. ETC ETC.
WHAT CAN BE DONE.
ok guyz this is the part where i would like allll the geeks & gurus to put in some effort, i know it will be tough but i have a feeling its not impossible.
CAN UR,LL UPDATE IIWPO IN SUCH A WAY THAT WHEN WE ARE FEEDING OUR NAME AND OTHER INFO IT WILL ALSO ASK FOR A SECURITY PASS TO BE PUT IN, SO THAT WHEN ROBBER CHANGES SIM THE IIWPO RECOGNIZES THE SIM CHANGE AND LOCK'S THE PDA AND ASKS FOR THE PASS, AND WONT UNLOCK TILL PASS PROVIDED, REBOOT WONT HELP.
Now ofcourse the robber can be anyone, so the robber plans to hard reset and still the device would recognize the sim change and ask for pass now so annoyed he plans to flash the device and what happens after that all of us know.
To prevent this THE GEEKS & GURUS can just build a small security patch that can wont allow flashing of device till pass given, it would work like this, we flash our device for the first time install IIWPO and the NEW SECURITY PATCH (with passwords) device is robbed, robber changes the sim gets pass error he gets pissed and tries to flash the device and that clever software would not flash the device till pass provided, this would prove that all the efforts the robber made to steal the device are gone to waste.
And ofcourse someday someone might put in a sim with credit and we would get the info.
NOT FORGETTING CHARLES WARNER FOR THE GREAT WORK HE'S PUT IN FOR ALL xda-developers.com USERS and also giving the IIWPO to us for free, REALLY APPRECIATE YOUR WORK SIR !! THANKS ALOT.
no one interested in being secured ?
I think the IIWPO idea can definitely be improved, BUT: It will never protect you from being robbed.
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device. In the end: someone will put in his/her sim and then its just bing!
All other enhancements will just make sure noone else gets to use the device. Sure an improvement, but less important to me: I just want my device back and get the thief nailed!
Interesting...
But I think you have misunderstood how IIWPO works.
IIWPO does not detect if someone changes the SIM card. It ONLY acts when the someone changes the Owner Information (Start/Settings/Owner Information), so no matter what SIM card there is, as long as it has credit it will send an SMS to the recipient's phone number. That's the beauty of it, that it silently sends the SMS with the 'new' users data so there is a slight chance of knowing who's the 'new' owner.
But! This is by no means fool proof. It's what they call 'protection by obscurity', so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO.
That's one of the cool new features of WM5.0, that we can at least know for sure that our data is SAFE by wiping the info remotely if necessary.
Just a thought.
Rayan
edsub said:
The true advantage of IIWPO in its currect form is to be able to get track of the 'new' owner of a nicked device.I just want my device back and get the thief nailed!
Click to expand...
Click to collapse
Rayan said:
so if a savvy robber knows how to reflash the device it will get away with it no matter what features we can integrate to IIWPO
Click to expand...
Click to collapse
ofcourse this is why we all love IIWPO cause it sends use a msg, and ofcourse even if someone was to modify IIWPO iam sure that this feature would'nt wipe out.god forbid you get robbed u get a msg frm the cell but you for some reason cant track the person or some other c#@p...and the pda is gone....WHY caz it only sends sms it does not block the screen....if you were to have a feature which would jam or freeze the pda on change of the name then the pda would be useless to the robber nothing much he could do....unless he knows how to flash it...now comes a part where we can do something about not flashin the device with out a pass....this would totally make the pda useless to the robber and would also keep sendin us msgs and secondly the robber maybe maybe next time might think twice before robbing a pda and might go for something else
How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,
cruisin-thru said:
How about a device that would be installed internally to the xda and if it is stolen and a different sim/different user info is entered and the person makes a call it fires a large captive bolt which nails the phone to the head of the user, it then adjusts itself to full volume with all lights flashing and announcing "This is a stolen phone...call an ambulance...or hearse".,
Click to expand...
Click to collapse
tht would be great..... are u goood enough to build something like tht ?
Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve
edsub said:
Rayan said:
But I think you have misunderstood how IIWPO works.
Click to expand...
Click to collapse
I perfectly understands the IIWPO functionality. It was me who put together IIWPO for other devices than Wallaby.
Let me explain how my earlier post should be interpreted: Sure it is triggered by the change of owner info, but most thieves (or buyer from a stolen device) will put in another SIM (simply because they dont have the pin of the stolen sim or because the stolen sim is blocked by the network). Thus: As soon as the 'new' owner puts in a SIM AND he/she has changed the owner info (and every one does that!) the sms is sent.
Also: Eventually a thief might flash a device, but ost certain a thief (or buyer) starts it up to test whether its working or not.
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve
Click to expand...
Click to collapse
Sorry edsub, I should have specified to whom I was refering to (zairyaab) when I wrote that comment.
Best regards,
Rayan
np m8
edsub said:
It was me who put together IIWPO for other devices than Wallaby.
Click to expand...
Click to collapse
Can you explain what should I change in the cab to make it work on other devices (Like ETen M500/Torq P100)?
edsub said:
Imho IIWPO can be improved, but practically chances of getting a device back will not significantly improve.
Click to expand...
Click to collapse
Yeah, but still I would feel somewhat better if I can at least call the thief/buyer and shout some expletives if he/she refuses to cooperate!!! :twisted: :lol:
Best regards,
Rayan
i have my girlfriend's number as my report number.. what if were together and we got robbed both our phones are taken away.. a multiple report number would be a good addition to IIWPO
The changes I'd like to see done to IIWPO include:
a) not using "IIWPO" or 'xda-developer' in the registry (user customisable registry key)
b) user customisable executable file name (IIWPO_startup is like a dead giveaway)
c) not storing owner name & number 'in the clear' (a simple XOR to hide it would be just as effective)
d) a hash of the entire owner info page (not just the last name) so unit will resend an SMS if any info changes
e) a new sms is resent after a preset time (eg: every 24/48/120 hours for example), regardless if owner info has changed or not.
I also like the idea of multiple number reporting.
a,b,c) Considering the concept of IIWPO is 'security by obscurity'; it will help if one could hide it more effectively. (no one is going to bother too much about bluetooth.exe or msn_update.exe in the startup folder for example...)
d) Most people get their name right; then meddle with the other bits of information as time goes on - it'd be good to get 'updated' info as and when it happens.
e) Consider it a 'keep alive' thing, so we'll know the unit is still in use, and can continue to keep in touch with the new owner =) I've no moral issues burning up the credit of someone who refuses to give me back my property either. =P
If nothing else, we'd be able to know when the unit gets reflashed, and can quiety say goodbye to our unit after not hearing from it for a while... =(
Is IIWPO still being maintained by the author, or anyone on xda-developers? If not, is the source available? I might be interested in following up on it (time permitting...)
Edited to add: A really vicious version of the IIWPO would possibly send out:
a) phone numbers stored in the SIM card
b) phone numbers stored in the addres book
c) recently dialed/received phone numbers
d) recently sent/received SMS phone numbers
Not all in one go; but in bits and pieces (eg: every 20 startups; send phone numbers of last 5 SMSs sent/received + last 5 phone calls dialed/received).
That would allow us get in touch with his friends and would possibly aid in getting the unit returned (use your imagination... probably easier to get them tell you who/where he is, rather than to get them convince him to return it...)
Probably this would add too much bloat to IIWPO; but hey, could be useful... =P
WOW, ok.
First of all - I registered 2 this forum less than a week ago,
and great job for doing these kind of things.
second - where can i d/l the prog?
and last another idea: when some1 steals ur pda he's usually gonna sell it over. meaning he made his money.
HOWEVER - if even after a HR after changing sims (maybe even without) there will be a picture message saying:
"You cannot use this phone"
"This phone can only be used by me - *name*"
"However, Im willing to buy this phone back from you. call +......"
there wont be a place on the screen to enter the code.
however - the phones' user knows he can type his password and unlock the phone. you might even integrate a handwriting recognition programm for signature or somthing but that will be super hard, i know.
another option is that when seeing this message user has to touch 4 corners of the screen with the stylus in a specific order, then he'll have a please enter password screen.
any comment?
is it do-able?
http://wiki.xda-developers.com/index.php?pagename=IIWPO
Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Why would this happen with these latest wm6 roms not previous wm6 roms.
My main worry is if this happens randomly with every new rom, and Im guessing this may not be isolated to this batch of roms.
Similar thread which may give a clue but thought this was more suited to the wm6 forum after I posted :/ lol
http://forum.xda-developers.com/showthread.php?t=284147
Thanks in advance
Start > Settings > System > About > Device ID
CUSTEL;1247299 said:
Start > Settings > System > About > Device ID
Click to expand...
Click to collapse
I'm pretty sure that isn't what he is referring to.
It's a unique string that identifies your device.
For example;
With AEButtons and WM5, I had a Device ID that started with D1 C3.... and then moving to WM6 it changed to something like C6 A2...
I was able to activate AEB just fine, it just shows that I have activated 2 devices at AEB's website activation page.
Karzi said:
Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Why would this happen with these latest wm6 roms not previous wm6 roms.
My main worry is if this happens randomly with every new rom, and Im guessing this may not be isolated to this batch of roms.
Similar thread which may give a clue but thought this was more suited to the wm6 forum after I posted :/ lol
http://forum.xda-developers.com/showthread.php?t=284147
Thanks in advance
Click to expand...
Click to collapse
I opened a call at Tomtom for that. I have the same problem. I asked to have a solution of a code based on the hardware and not on the operating system.
The answer: impossible. I must indicate the link of new the ROM and they correct the code.… I did not test yet…
I've run into the same situation with TomTom. It's a bit of a pain. Still working through the issues with them.
Timothy
I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed. Prior to upgrading WM6 (LVSW 20070423), Opera Browser would read the IMEI (device ID) correctly. After upgrading, it now reads a completely different number (not even remotely close, for one thing, it is two digits shorter). However, when I look at the IMEI shown in "Device Information", or #*06# from the phone dialpad, it is correct.
In both my cases (TomTom and Opera), I was quickly able to get new license keys from each, but it is still a pain.
WTF, M$ & HTC???
John
Same happened to me with the Hebrew add on. Strange.
Had the same wit Hebrew as well...
Yup, same problem here, I'm with Berdinkerdickle, there is a hex code that you can see with AEB Plus's registration screen that comes from the OS I guess. It changed from stock WM5 to Black 2.0 and now again with 2.5
Slingbox Mobile seems to use it internally to lock it to an individual device. The prog actually logs onto the sling site each time you use it and checks this number against the issued key code, this is independant of user inputted ID name like most progs. If there is a mismatch the program tells you that you have 30 days remaining and counts down till you enter a new code provided by Sling, which means an email conversation with them each time to get a new code.
AEB Plus as noted, shows you the internal code string and has you enter that string into their website to get an activation code. (I'm on my 3rd web re-activation and wondering if AEB has a max cut off number?)
I looked over the thread referenced on the first post and it mentions super CID, I've not done that to mine yet.
The device code is a hex string listed as 7 pairs of numbers in AEB Plus (xx xx xx xx xx xx xx) is this the CID code?? and if it is, is it linked to the OS, uniquely by device?? That doesn't make sense to me.
Same problem for me, with SlingPlayer and a few other applications. Ugh. Every time I put a new ROM on there, the device ID or whatever they're using changes. They must think I'm trying to equip an army with Slingplayer licenses.
jmat said:
Same problem for me, with SlingPlayer and a few other applications. Ugh. Every time I put a new ROM on there, the device ID or whatever they're using changes. They must think I'm trying to equip an army with Slingplayer licenses.
Click to expand...
Click to collapse
I had it with a few apps as well. With Slingbox they indicated that it's not a problem at all since once they issue a new code, the old one is invalidated. They don't really care.
never mind...
johnburn said:
I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed. Prior to upgrading WM6 (LVSW 20070423), Opera Browser would read the IMEI (device ID) correctly. After upgrading, it now reads a completely different number (not even remotely close, for one thing, it is two digits shorter). However, when I look at the IMEI shown in "Device Information", or #*06# from the phone dialpad, it is correct.
In both my cases (TomTom and Opera), I was quickly able to get new license keys from each, but it is still a pain.
WTF, M$ & HTC???
John
Click to expand...
Click to collapse
The API isnt broken... works fine in Black 2.0, 2.5 and 3.0, as well as all of LSVW ROMS...
Skyscape
Same problem with
Skyscape applications (medical references)
http://www.skyscape.com
johnburn said:
I think the API to get the device's IMEI got broken in the latest WM6 builds. I too have the TomTom license problem, and Opera Browser for Mobile is also complaining that the device ID has changed.
Click to expand...
Click to collapse
The irony is that people who didn't pay for these applications have zero problems..
Copy protection doesn't hurt anyone but the legitimate people..
The worst part is, I can't even suggest that you (the legitimate purchaser) use the keygen floating around give yourself access to your product.. because that would cut you off from your online services..
icemantwilight said:
The irony is that people who didn't pay for these applications have zero problems..
Copy protection doesn't hurt anyone but the legitimate people..
Couldn't agree more!!
Click to expand...
Click to collapse
mrvanx;1248020 said:
never mind...
Click to expand...
Click to collapse
Sure, No Problem.
Yea, I wish we could delete our posts rather than
only being able to edit them.
Karzi said:
Any one figured this out yet?
Basically the tomtom calculates the device code (I thought this was via imei)
Well since installing black 2 I can not longer use tomtom plus services (speed cams traffic e.t.c)
I can change the device code on there website once every 6 months BUT if the same thing happens with black 3 then It wont work, there is a similar thread I have replied to on the upgrades forum which may be a clue as they had the problem with CID unlocking, my device has had all that dont about 6 months ago many roms and "device names" later (one actual device) it now has it thinking its a new device.
I am guessing this is going to happen with a few other bits of software from what I have read in the searches (opera and a few other similar bits of software).
Click to expand...
Click to collapse
Same problem with my TomTom, does the new Black 3.0.1 solve this issue?
Black 3.0.1 goes back to the same hardware ID that was around in Black 1.0 and Black 2.0. So.. I guess it's fixed? It seems like there was a build of WM6 out there that really screwed with things -- because all of the other ROM's had the same problem.
jmat said:
Black 3.0.1 goes back to the same hardware ID that was around in Black 1.0 and Black 2.0. So.. I guess it's fixed? It seems like there was a build of WM6 out there that really screwed with things -- because all of the other ROM's had the same problem.
Click to expand...
Click to collapse
I didn't check Black 1 or Black 2, was the ID the same as WM5 with these versions of WM6? It was only a fault in roms v2.5?
Hi Guys,
I am wondering where the Device ID is hardcoded and if it can be overridden by any software or bootloader hack.
I have a corporate mail windows desktop software that checks for the reported device ID. It was configured to look out for a Cingular 8525 (HTC Wizard) which has a device ID of [WIZA200] however after I upgraded to a a HTC Trinity [TRIN100] it refuses to sync with a an error message of pointing to the invalid device id.
any advice/help appreicated how I can make my Trinity ID look like a Wizard ID to sync again.
cheers,
Ollie.
Probably a stupid question, but wouldn't it be simpler if you go to the administrator (or who ever is in charge of the tech staff at you company) and have your account changed for the new device?
What you want can theoretically be done by editing the ROM image (I know this ID is something PB sets) but I don't think anyone ever tried it (at least on this forum).
One more thing: why is your software checking device model? This would be fairly useless as a security feature. Are you certain it is not locked on your phone IMEI or UUID - in which case my first suggestion is the only way to go.
I'm with levenum on this. Checking if the phone is a WIZA or TRIN is rather an extra effort that does not provide much security or identification purpose. E.g. there are like millions of WIZA out there that is able to by pass this 'security' or be identified as.. you?
IMEI on the other hand, is unique to each device, for security and identification purpose, thats most likely what it is doing. ELSE, if it were to be like a login name, you can try changing the one at 'Start'->'Settings'->'System'->'About'->'Device Id'
Thank you for the suggestion guys. I have tried...
The reason they are checking for ID is, that they would like to ensure that only "standardized devices" are used.
However, you probably can appreciate that I'd prefer to use my Trinity rather than a Wizard.
The are not checking for the "soft" device ID that is user configurable as the access security is done on application level with a login password.
The other problem is, talking to a IT organisation which supports 40,000 people. Not exactly easy to get a one off change done ;-)
levenum, what do you mean with PB ?
BTW the application is CREDANT password manager.
Pretty sure, its locked to Device ID based on the extract from Log of credant connecting via Active Sync:
DevOS=PocketPC
Device=TRIN100
Cert=M2M
SyncOS=ActiveSync
SyncVersion=4.5.5096.0
ProcessorClass=2577
05-15-2007 15:54:10 [W] PPC device is unknown: [TRIN100]
cheers,
Oliver.
P.B. stands for Platform Builder, it is an MS tool that creates ROM images (thats what OEMs use).
I understand your frustration about dealing with IT but trust me - it is a lot easier than actually changing the device ID (if it is at all possible).
Plus if your company has 40000 employees I am sure you are not the only one using Trinity or at least something other than Wizard. Maybe group pressure can help expedite the proceedings.
I run a couple of bits of software on my phone which the licence is registered to the device id. When I change the rom on my phone the device id changes. Is there anyway I can stop the id changing? I have to contact my software provider each time to explain I have changed phones and can they supply a new licence on the new device id, I dont think they're going to keep doing this for free
Thanks.
A very good question!!