guys,
when I moved from WM5 to WM6 (both official ROMs), my device ID appeared to change (assumption by virtue of the fact it changed in TomTom 6).
Can anyone else confirm they have seen this? I'm still waiting for HTC UK support to contact me. ABout a week now.
I thought it might be helpful to see who has seen this (regardless of ROM details).
Hi,
Yes, all time you Flash your PPC with new Rom, Your Device ID change, and Tomtom need to be change too (Trafic, SN, etc...)
If you have Tomtom Trafic option, go to tomtom site to change your device id, it's work fine.
As far as I know, it is only the DOPOD, and DOPOD based ROMs that have this problem, and it is a bug in the firmware. The very latest DOPOD release has apparently fixed it- so Mun's Indigo Full which uses the latest ROM is OK, but Lite shows the problem.
Device ID's are a complex matter. Some are based on the IMEI, some derived from the ROM version and some by other means. TomTom and Mobipocket both use 'other means' to derive the Device Code, and it is only with the 'faulty' ROMs that the Device Code changes.
I've taken my Trinity through about 7 ROM updates, and the TomTom Device Code remained the same except in the DOPOD WM6 ROMs; reverting to another ROM resulted in the Device Code going back to what it should be.
This is a real problem for TomTom users because they are currently refusing to relink the new Device Code to the Traffic and Weather account, even if you succeed in obtaining a new activation code. So you have a situation where the software is working fine, but you can't access your TomTom Home subscriptions. Customer Support are now asking for 'proof of purchase' of the WM6 ROM upgrade, which of course can't be provided as there is no 'proof of purchase' for most ROMs.
We have had quite a long topic on this on 4Winmobile, and the latest situation is that it could be a case for Trading Standards to investigate, as TomTom are effectively blocking users from accessing services they have paid for.
hi Neil,
that's most interesting feedback, thanks.
I too have installed at least 6 ROMs on my Trinity. From the OEM Orange UK WM5 (the phone came with) through to mUns TE and others the device code remained static.
Then when I went to the officical Dopod WM6 ROM it changed. I believe I also used the latest official of their ROMS the other week, which was rumoured to fix this issue, but it has not. I think people are confusing the other issue of changing with each hard reset- which I do not have the problem of.
I'm very frustrated with TomTom- it's a month now with no Traffic- and I use it for my work driving the length of the country.
I've suggested that it shouldn't be my problem- after all I have paid the subscription, and it's an official ROM. OK it costs them time to make a change- but it costs them more to keep sending emails to-and-fro asking me for proof etc etc. I've wasted hours on this chasing, HTC (Dopod), Microsoft and TomTom, plus investigating on the web. It's clearly an issue, but no-one will hold their hands up.
If someone could post a link to the latest Dopod ROM which definitively does not change the ID I'd be eternally grateful. And by definitive, I'd prefer first hand experience ;-)
folks,
tonight I bit the bullet and installed mUn's Indigo Full. Very quick to install, nice looking ROM but the Device ID has still changed :-(
So every Dopod official ROM and now the full Indigo changes the device ID from the original WM5 ROM and every other WM6 ROM.
I've tried 3 ROM in 7 days now. This is getting silly!
I think I will not be renewing my TomTom Traffic. Oh and I forgot to say, HTC Europe sent me a fob- off email tonight.
"Contact your phone supplier......" Thanks. They seem to be deliberately avoiding this- I gave them the chance to just say "yes" we know there is an issue. That would be enough for TomTom.....
TomTom and license key
I have heard that TomTom only allows the use of the license key twice. Has anyone found this to be true? Because, if so, a lot of people who have installed WM6 on their Trinity and have been asked to activate Navigator again (myself included) will have to think twice before switching ROMs again.
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
sickboy555 said:
Hmm I'm not sure if this is correct- if the map is activated, and you change the device ROM, TomTom does not need the map to be reactivated normally.
This ONLY happens if you change the device ID- i.e. you then need to reactivate with the licence.
If Device ID's change again then yes there is a problem.
Please lets not confuse the issue here- the problem is for Traffic subscriptions- you can only change your device in the TomTom account online once in 6 months.
After this you must go through TomTom support.
It's not got customer service to be waiting 1 month with no resolution.
Click to expand...
Click to collapse
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
oh no Pietrucci, that's bad news. And very odd if they changed the ID, but going back to another ROM with old ID, Traffic works.
So if TomTom update my device ID and Traffic still doesn't work I'm scuppered.
Apparently they never let you go back to an old ID in your account, which means going back to an old ROM may not help either. Maybe there is something wrong with their account system for Traffic, if your old one still works???
pietrucci said:
I also had the "famous" devide-id change after upgrading to the official WM6. But in my case something very strange: I DID send a proove of repair to TomTom (I really had a repair) and then TomTom DID reset my device-id to the correct device-id (when I actually look at the TomTom-site my settings are all correct).
But now I still get an error using traffic (and other Plus-services). I resettet my device on the TomTom site many times but no effect.
The situation now is that I have alle the correct codes, can use TomTom (6) but still can't use traffic!
When I go back to an unofficial ROM (p.e. Sleuth 3.2) with another device-id everything's ok.
Frustrating... don't know what to do anymore, TomTom did their job.
Click to expand...
Click to collapse
I have exactly the same problem. Online my plus services shows that the TomTom Device ID is correct, BUT traffic still doesn't work.
Going back to the older version of WM6 with the older device code and it works. So TT Plus servers must still have the old device code associated with my PLUS account even though PLUS online is showing the new code.
I've told TT that it's not working but no fix so far.
MAJOR UPDATE: New build of WM6 fixes the device ID change issue. The device ID is the same as in WM5 - the first cooked ROM to include the fixed build is Schap's 3.60a.
Best get onto TT and have that code reverted back sharpish!
hi eaglerest can you post a link to the specific new build of WM6 you are referring to please (the OEM ROm, not the cooked one).
The 8th of August DOPOD rom DOES NOT fix the device ID bug.
i.e. this one RUU_Trinity_DOPODASIA_WWE_3.00.707.18_6275_1.46.30.11_108_Ship
hi,
sorry it's a hermes build.....
http://forum.xda-developers.com/showthread.php?t=322905
ah, so it's not just confined to the Trinity then.
thanks for the info eaglerest.
right, I've given up with this ridiculous Device ID business!
I told TomTom to leave the ID alone (after 6 weeks with no Traffic) and have gone back to mUn's TE, which preserves the old Device ID.
Not what I really wanted but I think I'll be an old man before it gets resolved.
HTC In Asia and Europe fobbed me off and wouldn't even acknowledge this as an "event" let alone a bug.
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
moondevil said:
Hi all, am I missing something? I thought that the latest release of code i.e. OS 5.2.1620 Build 18125.0.4.2 was going to fix this? Or have I mis-read the posts. I ask because I tried the latest Bepe build, and my device ID still changed. Does anybody know excatly why the ID is changing?
Click to expand...
Click to collapse
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
TomTom will only change the registered device if I can provide proof from HTC or someone else that this is a bug. Guess what- they've been no help at all. Neither have Microsoft or Orange.
sickboy555 said:
Not really sure what you think you have misread. perhaps you are thinking of a bug whereby the Device ID apparently changed on EACH hard reset? I personally have not seen this.
My problem is that WM5 = DEVICE ID A (My Traffic is registered to this.
mUns TE WM6= DEVICE ID A
Official DOPOD WM6 ROm, Indigo FULL = DEVICE ID B. Now my Traffic will not work.
Click to expand...
Click to collapse
OK, just so I'm clear on this because I'm (nervously) about to go down the path of updating for the first time. I'm coming from WM5, having never flashed before, will upgrading with Bepe's latest of .74 change my Device ID or not?
probably, but I have no idea for sure. Not used that ROM.
If you use TomTom Traffic and it does change, you will not be able to use it anymore. If you have never changed your device ID with TomTom, you can do it yourself- but only once per 6 months via your account on their website.
You will have to re-register all your maps too.
If you saw moondevils post, his ID changed with one of bepe's builds. I imagine that bepe uses the same core OS for all his builds so your ID will likely change.
mUns TE is the only Wm6 ROM I have tried which keeps the ID (and I've tried many many).
sickboy555, thanks for your reply.
I *thought* I'd seen something relating to the newer build not changing the ID, but I was obviously mistaken. Like you, I've tried most of the "post Dopod official" Roms and they all change my device ID. I followed the link to the Hermes build and saw that it was a 18125.0.4.2 build, and thought that maybe this would cure it. But obviously not.
What I find funny is that Bepe is building Tomtom in to his builds, and I'd love to use it, except I just upgraded from my SPV M5000 (1 change) and now tomtom won't let me reregister my maps.
Bugger!
Related
Contacted o2 (UK) requesting a date for an official ROM upgrade to WM2005 and WMP10.. not definitive news, but if you believe their reply then it's on it way:
"A rom upgrade for the XDAIIs is still in test. We are unable to give a
release time or confirm it's contents until it is fully accredited.
As soon as any information is available it will be posted at
www.my-xda.com"
Fingers crossed, I don't fancy trying one of the modded versions just yet - I rely on the phone a bit too much at the mo.
-FM
O2's 2003SE software isnt exactly stable. I did the upgrade yesterday and its fine except the BT keeps turning off
If you want to increase the stabilty of an O2 XDAIIs, I'd do a hard reset. (Hold the power button whilst pressing the reset button). It'll come up saying it's going to install a load of stuff. Thats OK. When it asks if you want an O2 config or a corporate config, select corporate. You will then be prompted for a pin number. The numbre you require is 0506. Enter the numbers. The phone will eventually finish without installing the O2 active stuff. This, in my experience, turned a phone/pda that was always locking up into a very stable thing!
Hard reseting removes everything and returns it to it's out of the box state. You can restore a previously saved backup as this will put O2 active back on! I learnt this the hard way!
mine was still unstable after the corporate reset and removal of the o2 software....
running tomtom5, BT and media player doesnt help though
What are the chances of the NEW UK XDAIIS ROM containing support for i-mode?
I've got a sneaky suspicion it's why they have dragged the release of it out a bit.... It's taken a long time considering Asia has a ROM all done, that needed a few bugs fixed, but surely would not take this long....?
Must be something 'extra' going into it.
O2 i-mode launch is 'imminent'
http://www.theregister.co.uk/2005/09/20/o2_i-mode_autumn/
What is i-mode?
http://www.sourceo2.com/imode.html
from Wikipedia:
"Opposed to the WAP standard which utilizes WML on top of a specific protocol stack for wireless handheld devices, i-mode borrows from fixed Internet protocols such as C-HTML based on HTML, as well as DoCoMo proprietary protocols ALP (HTTP) and TLP (TCP, UDP). "
I may be completely barking up the wrong tree, but it should be manageable through a software update.....
Anyone know if this is a possibility?
Can someone please share their experience.
I am interrested to know how the devices perform in the Corporate install of the O2 and the JasJar.
Having used both I would recommend the o2 Exec ROM, I've ended up reverting back to this due to stability issues with the Imate ROM. Both ROM's will need registry hacks, go with the o2 one running in corporate mode.
The corporate with the code 0506?
Is the pocket MSN there on that configuration?
Which one is the most generic config?
a18041967 said:
Having used both I would recommend the o2 Exec ROM, I've ended up reverting back to this due to stability issues with the Imate ROM. Both ROM's will need registry hacks, go with the o2 one running in corporate mode.
Click to expand...
Click to collapse
Is it possible to flash a Jasjar with the O2 ROM? If so will I lose anything?
skearon said:
a18041967 said:
Having used both I would recommend the o2 Exec ROM, I've ended up reverting back to this due to stability issues with the Imate ROM. Both ROM's will need registry hacks, go with the o2 one running in corporate mode.
Click to expand...
Click to collapse
Is it possible to flash a Jasjar with the O2 ROM? If so will I lose anything?
Click to expand...
Click to collapse
Yes,you can flash any ROM to your Jasjar , you will lose your setting email..etc,others same as new.
I have just loaded my MDA PRO with the O2 ROM, and tryed all the possible installs (basic, Corporate with code 0506 and personal)
Only the Corporate one is really customisation free. I have myself bypassed the extended_ROM so now I have run only one cab the Default_Enable_VT_RTPlugin_0727_2_signed.CAB which is responcible for the video call. Strangely enough I have the same scin in the dialer as I had in the JasJar ROM...
Also as mentioned by... that by O2 ROM the splash screen is not installed it is not true, as right after the upgrade to the O2 ROM and the reset you see the O2 splash screen, which is untill now the nicest looking splash screen.
What I can say after 2 hours of using the O2 ROM is the following:
1. The amount of free program memory after reset is the same as by JasJar ROM.
2. The device is at least twice as fast as with the JasJar ROM.
Conclusion for now I am much happier with the O2 ROM. Much more stable and responsive.
As I am using Jasjar and after your comments I am considering moving to o2 could you tell me how you configured your Jasjar? Specifically, I am using my jasjar without the extended rom except for the video dialler and the bluetooth patch. It is generally running well except for the need to hard reset once in a while. When comparing with the O2 were you also using Jasjar without extenstion?
Thanks, apap
Having used both ROMs, I think they're essentially the same ROM with a few minor branding cosmetic mods... The two ROMs are only dated 2 wks apart and doubt there are any major differences.
To be honest, I couldn't find any performance gain or loose using either one of them and the O2 ROM seem to be slightly smaller in size (maybe due to the additional Imate games/themes etc?) So after going Imate ROM with O2 extended ROM, I went back to all O2 ROM..
I have a Jasjar. Due to the machine freezing occassionally on arrival of a new SMS I would like to give the O2 ROM a try.
I shall be obliged if someone can tell me that when I have installed the O2 ROM and would like to go back to the i-mate ROM would this be possible. What is the procedure to revert from O2 ROM back to the I-mate ROM.
I will appreciate your help
Regards
OK boys and girls...
I have tryed the O2 ROM the whole day yesterday and last night late reverted to JasJar ROM. Reason: maybe I did something wrong but in corporate install of the O2 ROM with the code 0506 but I had no pdf reader which is unfortunately a crucial software for me. I have tried to install it from the cabs of the O2 ROM and from JasJar ROM but it would not work. Of course the solution might be to get a cracked version. But that fact pissed me off so much that I have loudly cursed O2 and reverted to JasJar.
Observations: I have noticed that O2 ROM has more program memory when you reset the device but once you use the thing the amount of program ROM is the same as in JasJar. So the fact that just after the soft reset there is more ROM is actually not interresting. I also found that in the O2 ROM there is a problem with the start menu opening up first time after a soft reset (If you soft reset the device and then for the first time click on start it takes 10-13 seconds to open it up) and this issue was the biggest issue for me to change to O2 ROM. Pocket MSN seemed to work faster and is more responsive on the O2 and maybe overal performance is a little notch better then JasJar. The Bootup Splash screen on the O2 is much nicer then on JasJar it is really sharp and cool
Conclusions: If you like experimenting try out the O2 ROM because you get to see also (if you try out the Personal install) how badly an operator can F*** up the device, it is beyond my understanding but it is hideous their Launch software, the screen looks like a battle field and I get dizzy looking at it, the task manager which it installs is such a crap only due to a fact that once you close all the progs with the task manager the task manager is still running so to close it too you have to go to settings ->system->memory and close it from there. I can understand that the task manager which you can use from your today screen has to be running in order to work but this task manager you have to start by going to programs and starting it manually, It is comepletely beyond me what is the purpose of such a task manger, but hey maybe I am STUPID ???
The battery icon moved next to the start I can understand the handyness of this, but the O2 icon which does not do anything is also comepletely beyond my understanding. Plus when changing the screen orientation the battery and the O2 icons suddenly get a darker background and it looks like it hangs, but it only looks like it the device does not hang, but it is still an ugly sight to see...
If you opt for the Corporate install with the 0506 code I think you are fine the machine performs as it should, and is very stable, no O2 annoyances and no O2 **** to be seen apart from a couple of icons in the Programs. One of them is the O2 install which I beleive supposed to allow you to change your install type, without making a hard reset, but of course it only works in one direction, meaning that if you have a corporate install with the code 0506 and you want to change to standard or to personal it will work but if you are running the standard and want to go back to corporate or if you are runnning the Personal (full featuer O2) and want to change to standard it will not work. After playing around with that I have found that my simmanager and enroller icons dissapeared, but I was able to get it back by running one of the cabs. it was different with the pdf reader, since I need one I have decided to run that O2 install type thingy and chose first standard install which did not bring the pdf back, and then I have chosen the personal install which would mean that I should have now everything on it , the pdf icon was there but alais the pdf did not work I kept on getting an error.
One more thing when you install the CORP version the dialer skin is the same as by the JasJar so I beleive that that is the generic skin, since the O2 Dialer skin is very vague the buttons are beautiful, but have to much light in them so it is difficult to see the letters
SO I am back to JasJar ROM and I beleive will stick to it for a while.
The progs I run :
TT5.1
Resco Explorer
Skype 1.2 beta
Backgammon
Total commander
All installed on the storage card
I hope this not too boring and helps folks here.
srmz said:
I have a Jasjar. Due to the machine freezing occassionally on arrival of a new SMS I would like to give the O2 ROM a try.
I shall be obliged if someone can tell me that when I have installed the O2 ROM and would like to go back to the i-mate ROM would this be possible. What is the procedure to revert from O2 ROM back to the I-mate ROM.
I will appreciate your help
Regards
Click to expand...
Click to collapse
I have done it and reverted back to the JasJasr rom no problems and I have an MDA PRO, so I am even further way from home.
Follow this thread to learn what are the procedures for upgrading:
http://forum.xda-developers.com/viewtopic.php?t=29354&postdays=0&postorder=asc&start=0
Good luck
The Exec ROM (basic and Corporate) do not suffer from a buggy Messaging app on the JJ ROM. The JJ ROM can cause the JJ to freeze on SMS notification and can crash when receiving emails over UMTS.
You mean the imate email app ?? or the bult in functionality. Because I do not have those symptoms. and I have received only today already about 12 sms messages.
About receiving the e-mail overUMTS: I use exchange active sync over UMTS and works like a charm without any problems...Maybe it freezes when using pop mail or imap? What is your configuration ?
And once again by the "buggy messaging app" you mean the imate e-mail??
Can someone confirm the presence of MSN and PDF inthe O2 Corporate mode ????
Thanx
Jasjar or O2?
I have also been wondering whether to try O2. Overall, after many trials I am quite satisfied with Jasjar. I have not installed extended rom except for bluetooth patch and smardialer cabs. I am running: pocketinformant, magicbutton, repligo, netfront 3.3, resco explorer, pocket mechanic, microsoft voice command. I have done a number of recommended register tweaks. I have also updated the radio to 1.04.
Speed is good.
Remaining problems: Once in a while I need to soft reset to overcome freezes. My main problem now is that I cannot install new programs or updates, nor can I remove programs.
It would be useful to find out how others are dealing with these problems and whether thos running O2 corporate are confronting similar problems.
Should I switch to O2 corporate? There seem to be conflicting views on the matter.
thanks, apap
Churchill:
You wrote a few things about Extended ROMs, Code 0506 (for o2 Corp. mode?), and about bypassing the extended ROMs.
Also there was a mention of bluetooth and radio Cabs...
I would be obliged if you could elaborate and explain them to me.
I have the o2 Exec and would like to experiemnt with the corp. mode since I find that in personal mode it freezes up all too often (not enough memory I guess...) but I wouldn't like to loose essential functionality by changing my ROM.
Thanks in advance
Well I am right now updating my MDA PRo from JasJar Rom to O2 ROM, since I still think the O2 ROM was a notch faster in the corporate mode.
I would not advice you to bypass the extended rom install as I found that some things do not work properly like the sim manager and pdf.
You are fine with the Corporate mode since it is the cleanest of all options including the JasJar.
Also Pocket MSN is more responsive in the O2 corporate mode, then with JasJar ROM.
So just go ahead and do a hard reset and choose corporate mode with the code 0506.
By the Way as I have already mentioned earlier the Boot splash screen of O2 is the best till now. Funny is that I was called by T-Mobile representative a couple of days ago and asked what I think about the MDA PRO. I have told him that MDA PRO with t-mobile customization is history by me and I am running JasJar. He warned me that if something happens to my device they can not help me now since there is no t-mobile rom available to flash it with (I do not understand that where is the release rom? did they loose it or something?) but I am still eligible for my 2 year warranty. He also asked why I have switched to JasJar, I have told him that the t-mobile customisation is crap and that the device was slow and unstable. He confirmed that and also saysd that this is exactly the reason why he is contacting me, since they aparently received a threat from one of the major consumer organisations in the netherlands. So he sayd that they are verifying the isue with the users and it does not look good since everybody complains. So hopefully t-mobile will release new rom soon...
Funny is that I have mentioned to him that I hate the hideous colors and boot splash screen of t-mobile rom, his answere was that the boot splash screen they are extremely proud of since it took a long time to come up with the design.... DUDE how long can it take to come up with something so hideous?
Anyhow....
P.S. I let you guys know how is my MDA PRo with O2 ROM
Adobe acrobat reader is available freely from the adobe site, in the same way as their readers always are:
http://www.adobe.com/products/acrobat/readerforppc.html
HTH
The O2 Exec has OS 1.13.48, which has a memory leak bug. Commontime mNotes synchronization cannot free the memory after use, so a 3rd consecutive sync empties out all remaining RAM. This was resolved in OS version 1.13.53, which is on the Jasjar.
Yes, the Exec ROM seems a tad faster, but at least for me the memory leak is decisive for the Jasjar ROM.
Jasjar or O2?
Wiz, have you reverted to Jasjar? Also, I do not quite understand the memory leak problem. Does this mean that there is a danger of losing note information? Finally, any suggestions on how to resolve the inability to add new programs? Does this problem occur only with Jasjar?
Thanks, apap
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?
Hello there,
What I Have: Att 8525 Herm100
Rom: Att's Mobile 6
Everything is stock but the extended life battery
The problem I am having is when ever I try to activate my WiFi the phone doesn't do anything. I am not sure if there is a wifi card or not but that's want I want to know. I have tried everything from activating it in com manager to going into the settings and activating it manually and nothing happens it acts like I didn't even hit the button to activate it. Is there a wifi card in the phone or is it integrated on the motherboard in the phone. Note: I bought this phone off e-bay and the wifi never worked when I received the phone.
I am new here and if there is a post about this already I am sorry.
I hate it when that happens.
To begin, there were two ATT OEM WM6 roms relevant to the 8525 that I noticed deep in the bowels of XGA.
I chose the later file (higher revision numbers) I found it here:
http://wiki.xda-developers.com/index.php?pagename=Available Original Shipped WM6 ROM Versions
From comm manager when I click the tower button on within a second the spinning windoze icon shows something is happening. It then starts "sniffing" for my preset wifi connection (ATT supplied 2wire portal 802.11g).
Now, if yours does not show the spinning windoze working icon when you turn on wifi? There obviously is a problem. This could be software, or hardware related (duh). If there is no error message related to "wifi is not an option, unavailable, or screwed" then my first guess is there is something missing or damaged in the ROM update that was applied to your device. As far as I know all 8525 (herm100) were shipped with wm5. It had been mentioned in the volumes of xda that the first AT&T WM6 rom was a little buggy. Try the later released AT&T WM6 update.
It was a run file so no muss no fuss. Sync the phone run the update from the pc, three minutes later the phone is flashed to ATT WM6 professional.
You could take it to a ATT shop? But, I think that without a doubt they would hand it back and say you need a new phone with a 20 year contract and 3g data plan even Obama would blush at.
Try the hard reset. take a picture of the startup screens so you have the numbers and see if the wifi startup is working after the reset. If not then compare the numbers to the above mentioned roms. If the indications are you have the first issue of WM6 from ATT try flashing the second release. If that still fails then your device could indeed have a hardware problem.
The wifi is indeed built into the system and if that chip on the board is not working it could be a overly expensive problem. Possibly a shop has a working board they would swap out cheap? Otherwise, it is a fun phone you can keep notes on, run gps software if you have a bluetooth gps receiver and software like tomtom.
To be honest the wifi on my 8525 has been convenient when around the house to check the local weather radar when I hear a thunder outside, or browse headlines from the porcelain room or even leave messenger turned on incase a gamer friend is looking for someone to get shot up in a game.
I have used the live search voice thing to amaze the neighbors once. But, the limited range of wifi is a real drawback to how truly wonderful that addition could be.
HELP Please! Wi-Fi not working!!!
Hi to XDA all users !!!
MY Hermes - HTC TyTN [Herm200]
I bought HTC Hermes myself year ago.
there was flashed a WM5.0, I've just downloaded from here HARD SPL & WM6,1 (Custom) Flashed.
Wi-Fi will works on WM5.0.
Well here I am at 6.1 flashed and now is not working Wi-Fi. When i pressed Power ON - loading long and nothing happens.
Other methods are also tried on Commanager and Settings - but did not help.
What do I need to do my dear.
HELP!
Thank you for your attention!
Hi Nurk.
Since the wifi worked on wm5 but failed after the 6.1 flash. I would guess the problem is in the 6.1 components. You might start with contacting the kitchen rom you employed for WM6.1 thread and see if this has happened to others. Next step would be to check the radio rom version. I did see on xda an assortment of Radio roms.
If your not totally in love with the current rom you have flashed? Try another 6.1 or even a 6.5 and see whats poppin.
and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?
utak3r said:
and what you have in HKLM\Software\HTC\CommManager\WLAN\DeviceName?
Click to expand...
Click to collapse
I have get this from registry:
HKLM\Software\HTC\CommManager\WLAN\DeviceName - {98C5250D-C29A-4985-AE5F-AFE5367E5006}\TIACXWLN1
Will Blackberry Connect work on the Touch Pro2?
I have installed version 106 and no luck as yet with t-mobile., stiil pending.
I just put the blackberry service on the phone and they said give it another day to activate the service.
Any help/suggestions would be appreciated.
i have been stuck on this issue for a week... no luck...
wrote to htc and they came back saying that look for updates on its site... now that's a really long shot..
would suggest that you too write to them... lets put some pressure..
this is a business phone according to them... then bberry is as much important!
I havent bought this phone yet, but I would only be able to if bbconnect is working.
Could you try to change the device ID to TouchPRO in settings/system/about and change the registry HLM\System\Versions\Aku to .1.6.0
But you need to change it BEFORE you install BBConnect
Please indicate if this makes any difference, otherwise we'll need to wait for a new bbconnect version
When i had installed the software without the above settings, i had a PIN and IP address - but it would not connect.
Later on i had hard reset the phone...
now i re-installed the software with the settings u mentioned, but i do not have a PIN or IP Address and bbconnect will not register either...
could u please tell me how to un-install it safely too? as i do not want to do another hard-reset now!
(btw, i had done a hard reset on the phone earlier coz after i tried 106 and uninstalled it, i installed a previous version 100 and it hung my phone.... )
peebee01 said:
I havent bought this phone yet, but I would only be able to if bbconnect is working.
Could you try to change the device ID to TouchPRO in settings/system/about and change the registry HLM\System\Versions\Aku to .1.6.0
But you need to change it BEFORE you install BBConnect
Please indicate if this makes any difference, otherwise we'll need to wait for a new bbconnect version
Click to expand...
Click to collapse
Thanks..I just unstalled and tried your settings still no connection or PIN.
am sure htc engineers visit these pages too....
hope u guys understand.. that u r touting the tp2 as a business phone.. and we need blackberry too in a business phone to complete the package....
we cannot connect to exchange alone (that incurs data charges and is not roaming friendly - especially international).. we need bberry coz that keeps us mobile from country to country that we visit...
common guys... its just a few lines of code u hv to modify... am sure...
Hi,
Have you tried this?
See WM65 solution here:
http://forum.xda-developers.com/showthread.php?t=502623
I think you have to play with the version number of your WM...
In case of WM61
I used this:
HKLM\System\Versions\AKU key, change whatever in there (like .0.0.3) to .0.4.2
Br,
Zsocee
I'm an Aussie wanting to purchase a Rhodium...
I'm upgrading from a 7100G blackberry handset. (yup a massive upgrade). Although the most critical part of my phone... (apart from making phone calls) is my blackberry push e-mail...
I can't afford to change over phones until I know that the Blackberry Connect 4.0 works. I know that HTC have a special version of the Blackberry Connect for the Diamond, the Touch Pro ect...
http://www.htc.com/sea/SupportViewNews.aspx?dl_id=497&news_id=61
With Windows 6.5 rumoured to be released within the next month I'm speculating that we won't see Blackberry Connect 4.0 working on the windows mobile 6.1
Zsocee said:
Hi,
Have you tried this?
See WM65 solution here:
http://forum.xda-developers.com/showthread.php?t=502623
I think you have to play with the version number of your WM...
In case of WM61
I used this:
HKLM\System\Versions\AKU key, change whatever in there (like .0.0.3) to .0.4.2
Br,
Zsocee
Click to expand...
Click to collapse
nope... non of these solutions will work.. tried all of them... even faced a few hard-resets trying older versions of bbconnect.
we have to wait for the next release. hmm....
mirage22 said:
nope... non of these solutions will work.. tried all of them... even faced a few hard-resets trying older versions of bbconnect.
we have to wait for the next release. hmm....
Click to expand...
Click to collapse
Me too!! Not working.
Had T-mobile and Rim on the phone together with no luck.
Well I contacted HTC to find out when it would work and this was the reply I received:
Since Windows Mobile is our platform for the HTC handsets, we would push customers to use the Microsoft exchange server.
The device comes with microsoft exchange server support and also supports IMAP and POP3 accounts.
HTC is not going to release any Blackberry connect applications and it would not up to HTC to do this. If Blackberry wants to develop an application and release it to HTC, you may need to check with RIM/BB.
RIM (is the company name)
Blackberry is the platform
Hope this information helps.
Sounds like the person I was contacted by either has no idea or there's no plan for blackberry connect to work on the touch pro 2.... Oh well looks like I'll have to purchase a storm...
Just be patient...
I'm more than sure that we will get BBC to work the same way we did it before. By manipulating the Device-ID string in the ROM (from HTC-Rhodium to whatever) BBC should recognize the device as "allowed" and it _should_ work. So all we have to do is to wait for the HardSPL-guys getting it done so that we can flash custom ROMs. Once this is done, I assume we will have BBC up and running.
Blackberry Connect.
Blackberry Connect does not work on the device, however, it seems to work on the HD.
From Sems.org
Has anyone tried this?
from http://www.sems.org/entry.asp?entry_id=338#IDComment31926819
Paul
Report Reply 1 reply · active 2 weeks ago
0 Vote up Vote down AirwolfUK · 2 weeks ago
make sure your AKU is set to .1.6.3. I have bbc .106 working fine on my touch pro2 with this and the SetModelID solution
Report Reply
I am planning on upgrading from Fuze to Fortress (TP2) and want to see if this works. You need to make sure your account is provisioned for BBConnect service.
Didn't work for me even after switching system ID to identify as Raphael, on T-Mobile US.
It works fine on the Rhodium. Check out the thread entitled "blackberry connect, not yet working" It got working about halway through. I use BBC on mine but I needed to make a couple of tweaks as outlined in that thread.
Dominoid - Rhodium - Blackberry connect
very interested in your asnwer dominoid.....can you send us more specifics as to how / what / where. We are dying to get Rhodium work with BBErry Connect. Which version worked with yours?
Does anyone know the orignal AKU for the ATT Tilt2?
I hate cross posting in threads, but somehow people decided to open different threads on the same topic. (Maybe a mod can merge them into one if he reads this).
Read more for a final solution without using SetModelID and starting and stoping services each time:
http://forum.xda-developers.com/showpost.php?p=4782317&postcount=163
Direct Link to the HowTo: http://www.silentservices.de/HexEdit-ROM-for-BBC.html
BBC
Works excellanty on my TP2 on Vodafone India Delhi n/w
follow steps on this forum
http://forum.xda-developers.com/showthread.php?p=5123157#post5123157:o