Not crucial to daily, but annoying to an otherwise perfect transition to 6.0. Same behaviour on WMXL and LVSW editions of 6.0, so probably something to hack in registry (???). When opening PIE, a message box opens reporting [This Address is not valid....], also, no matter which URL is set as homepage, after exiting and then re-entering PIE, it doesn't default to it asexpected.
Apologies if already discussed, but after conducting search, couldn't find an answer yet.
Thx.
=========
Saar
Is this while the device is plugged via USB?
If it is, have you tried unplugging and trying again?
If you are setting a correct address manually, say www.google.com and you get that error then it is a connectivity issue and not PIE.
agovinoveritas said:
Is this while the device is plugged via USB?
If it is, have you tried unplugging and trying again?
If you are setting a correct address manually, say www.google.com and you get that error then it is a connectivity issue and not PIE.
Click to expand...
Click to collapse
Hmmm....thank you agovinoveritas, but of course it's not a connectivity issue...... and I should have definitely mentioned, more specifically, that otherwise than this annoying message box, PIE 6.0 works impecably with no problems via both radio (HSDPA) and USB.
This must be a registry issue, but unfortunately I don't have another Hermes on originally released ROM and AKU to compare to, nor do I know if a simple 1:1 comparison is in order in this case.
Anybody..pls. advice.
=======
Saar
SaarAvigour said:
Hmmm....thank you agovinoveritas, but of course it's not a connectivity issue...... and I should have definitely mentioned, more specifically, that otherwise than this annoying message box, PIE 6.0 works impecably with no problems via both radio (HSDPA) and USB.
This must be a registry issue, but unfortunately I don't have another Hermes on originally released ROM and AKU to compare to, nor do I know if a simple 1:1 comparison is in order in this case.
Anybody..pls. advice.
=======
Saar
Click to expand...
Click to collapse
Have you done changes to your PPC? Installed new software?
Since I have had both WMXL and LVSW --including the newer version as well-- and I have no issue whatsoever and I have played around the registry as well. Any more info? That is kinda of the point. The error you have is vague. Not your fault but any more info would be helpful.
SAAR!
It's a known bug in eyron hebrew.
check the "FREAK" site.
it's a month old bug.
agovinoveritas said:
Have you done changes to your PPC? Installed new software?
Since I have had both WMXL and LVSW --including the newer version as well-- and I have no issue whatsoever and I have played around the registry as well. Any more info? That is kinda of the point. The error you have is vague. Not your fault but any more info would be helpful.
Click to expand...
Click to collapse
agovinoveritas thx again. Maybe I should ask you what is the default home page you see first when you just enter your PIE 6.0. BTW I'm searching the net and I've seen that there are a few others with same problem, but no solution yet.
Otherwise nothing special to detail:
1. When entering PIE 6.0 I get an empty home page instead of the expected WM6.0 default home page, unlike as expected
2. In a sec after the empty home page fires up, I get a message box reading: [The Address is not valid. Check the address and try again]. This corelates with digging deeper at [menu/tools/options] to find the home page URL empty
3. Now expected UEx would be to be able to click the [Use Current] button, to set a(ny) new URL address as home page (providing one is up), but this does not work either. Once clicked and approved [OK], it does not stick
4. Otherwise PIE 6.0 browses well both by Radio or USB, so of course it has nothing to do with connectivity
5. Surprisingly, very few report this, but since I've installed both an HTC TyTN, and an iMate JasJam with both WMXL and LVSW with different apps to same results, it must be something in the registry redirecting the default page to errored Address.
Hope I''m clearer now, as there's nothing more detailed to say.
=====
Saar
elivne said:
SAAR!
It's a known bug in eyron hebrew.
check the "FREAK" site.
it's a month old bug.
Click to expand...
Click to collapse
Hi elivne, I confirm that it is an Eyron bug. Following your comment I've suspended Eyron Localization temporarily and checked PIE 6.0 - OK. Thank you for your advice.
=====
Saar
where can i find the bug? what is the eyron?
thanks!
bump bump bump
still bump!
Related
Aaahhhhhhhhhhh
Can anyone help please?
I am running a PDA2K with i-mate 1.4 roms and radio 1.13.
Sometimes after a telephone call my GPRS fails to connect.
As I have Smartner push email on my phone this is a REAL pain and means I need to reset my device in order to re-establish GPRS and hence email.
THIS HAPPNES 4-8 TIMES A DAY!!!!!!!!!!!!!!!!!
Any ideas for a fix out there please?
Cheers.
Robin
I've got this problem too. But i don't know how to make it work correctly!
Every time i need to reconnect the GPRS.
And i realy doesn't like it!!! :evil:
Try this chaps. I have applied the registry tweak and now I keep GPRS on all the time.
HKEY_LOCAL_MACHINE\Comm\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\(GPRS connection name)\AlwaysOn
Just change it from 0 to 1.
(GPRS connection name) is, of course, the name of your GPRS connection, and I'm not sure if that GUID is the same on
every machine or not, but I only had about 5 GUIDs under Providers, so it shouldn't be too hard to find.
Fatzzz
_________________
This kinda sounds familiar to when I was last using my PDA2K about 6 months ago.
Okay.
HOW do I make this change please?
I have no idea how to do it?
Cheers.
Robin
Dude you need a PPC registry editor. I use EdReg.
Very similar to a normal windows registry editor.
Fatzzz
I have found something like that there: HKCU\Software\Microsoft\ConnMgr\Providers\{7C4B7A38-5FF7-4bc1-80F6-5DA7870BB1AA}\Connections\Providers\(GPRS Connevtion name)
But there is no key named "Always on"!!...
Well you have got further than I have.
I download PHM Registry Edit.
I opened KKEY_LOCAL_MACHINE then Comm and the only 2 options that start with a C under there are:-
Cellular Line and CXPort?????????
Is it something I am doing wrong????
Robin
Robster said:
Well you have got further than I have.
I download PHM Registry Edit.
I opened KKEY_LOCAL_MACHINE then Comm and the only 2 options that start with a C under there are:-
Cellular Line and CXPort?????????
Is it something I am doing wrong????
Robin
Click to expand...
Click to collapse
Try to use "Find"
I did a search on Providers.
NOTHING FOUND?????????
Robin
Robster said:
I did a search on Providers.
NOTHING FOUND?????????
Robin
Click to expand...
Click to collapse
Try ConnMgr!
NOPE.
Nothing.
Now I am getting really worried.
Either I am doing something very wrong or some of my setup is shot to peices.
And yet apart from this disconnect issue the phone is working fine!!!!!!
Robin
Okay.
It DOES help to check one of the check boxes asking for the kind of data I am looking for............. Dohhhhh
Well I found it under Microsoft.
I Have the following:-
Vodafone Internet
Vodafone MMS
Vodafone WAP and
Vodafone WAP CSD
NOTHING that says GPRS?
Any more ideas?
Cheers.
Robin
Robster said:
NOTHING that says GPRS?
Click to expand...
Click to collapse
so did i!
Hi
So no-one can help with this problem?
Looks like I am not the only one suffering and I am not the only one who cannot find the appropriate setting that needs to be changed?
Cheers.
Robin
GPRS problem
From another post someone indicated that in the new rom build its a problem with the caller ID program, and that downgrading this will help the issue:
Here is a step by step instruction:
1. Download the older version of caller-id from:
ftp://xda:[email protected]/BlueAngel/CAB_Files/Caller ID/IA_CallerID_1.20_WWE.CAB
and transfer it over to your device. Any directory is OK. I used ActiveSync to put it into the My Documents folder.
2. Remove the file IA_CD-Startup.exe from \Windows\Startup on your device.
3. Rename iacontacts.dll to something else (e.g. old-iacontacts.dll). This file is in the \Windows directory of your device but is hidden. However you can rename it using your PC. Open Windows explorer, and navigate to Mobile Device>My PocketPC>Windows.
4. Rename displayCID.dll to something else (e.g. old-displayCID.dll). Access it via your PC the same as for the previous step.
5. Soft reset
6. Run the CAB file on the device - just tap on it.
7. Soft reset.
That should do it.
Hope that helps someone, I have downgraded to the 1.22 rom which does not have this issue, but I am considering trying to upgrade to 1.40 and try this as a workaround to the gprs not able to reconnect issue, except after a soft reset or flight mode on/off cycle...
Many thanks.
I am off on holiday tomorrow so don't want to do anything that I cannot repare very quickly in case I have no phone while I am away.
I will give this a try on my return.
If anyone else tries this and is succesful please let us know.
Cheers.
Robin
GPRS Problems and caller Display
I too have been having problems with GPRS connecting once and then not again until a soft-reset or turning the phone off - on top of which caller display was slow and would often hang. (This is on an Alpine) I have succesfully downgraded the caller-id app and the GPRS problems have completely disappeared - on top of which, the app responds quicker, does not hang at all, and responds quicker on an incoming call. All in all, a result!
One note of caution - I had a password on my machine, and after renaming the files and doing a soft reset (as per instructions above) my Alpine would not restart. I had to to a hard reset! if you have a password on yr machine, disable it before you do the downgrade. The GPRS issue was really my only problem with my XDA, and now I'm a happy bunny. :lol:
Im just had to install this. Will see if it will be ok. I'll let you know.
I installed yesterday.
Seems to be working a treat.
EXCELLENT.
Many thanks for all the help.
Robin
Robster said:
I installed yesterday.
Seems to be working a treat.
EXCELLENT.
Many thanks for all the help.
Robin
Click to expand...
Click to collapse
Hi Robin - Glad to hear all is ok.. I notice that you're running the i-mate 1.40 ROM.. Any thoughts of updating to the 1.42..?
Cheers!
As the title asks really.
Since moving onto AKU3.x ROM images, I have also moved to radio 1.13, and I am forever getting connection problems with push mail, and WL Messenger.
It says it is connected with the little G, but no data seems to go through. If I soft reset, it works again for a while.
I have used in the last few weeks ROMs from everyone that's posted here, and today Indra's 3.3, but I seem to get similar problems on them all.
Any idea what's going on?
AlanJC said:
As the title asks really.
Since moving onto AKU3.x ROM images, I have also moved to radio 1.13, and I am forever getting connection problems with push mail, and WL Messenger.
It says it is connected with the little G, but no data seems to go through. If I soft reset, it works again for a while.
I have used in the last few weeks ROMs from everyone that's posted here, and today Indra's 3.3, but I seem to get similar problems on them all.
Any idea what's going on?
Click to expand...
Click to collapse
Question: do you also lose phone connectivity?
This is a problem in AKU. In AKU 2 MS have changed the RILGSM interfaces, while HTC have not fixed that in their code. So you'll get problems connecting to APNs that require passwords and your device cannot connect to them from the first attempt.
I have the same problem. There are solutions -
1. Flash AKU1 ROM (no push email support, only OUTD)
2. Use APN that does not require login/password
3. Wait when Crossbow ROM would become public. I think that that bug would be fixed there.
4. Just live with that bug.
I think option 4, then 3 will do for me thanks hehe.
BlackBerry
mamaich said:
This is a problem in AKU. In AKU 2 MS have changed the RILGSM interfaces, while HTC have not fixed that in their code. So you'll get problems connecting to APNs that require passwords and your device cannot connect to them from the first attempt.
I have the same problem. There are solutions -
1. Flash AKU1 ROM (no push email support, only OUTD)
2. Use APN that does not require login/password
3. Wait when Crossbow ROM would become public. I think that that bug would be fixed there.
4. Just live with that bug.
Click to expand...
Click to collapse
I think is the some problem happening with BBconnect, that produce times works the pushmail and times not. I was thinking could be related to the new "Internet Sharing" program.
Strange, my AKU2 works fine with Radio 1.13.00 (Jwritesmcps's version extracted from his AKU3.2).
My AKU2 with Radio 1.11.00 was also ok and least memory leak, except of some missed calls & clarity which prompts me to change to Radio 1.13.00.
Helmi_c AKU3.3 works fine with Radio 1.14.10.
Password or no password, pushmail, pop3, internet, etc.
But in AKU3.3, I do have a problem with additional apps (vcard) that jams up my sms/mms. uninstall it and it is ok.
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,
Just upgraded my rom, and for some reason, when i go the the orangeworld site in pie, it only displays a text version. No graphics or anything.
Any ideas?
all these fantastic genius's here, and no ideas?
I have noticed this too, and it must be something to do with what PIE reports itself as for User Agent.
The sites work fine with Opera, but cant see if that reports as Mozilla for whatever.
We need someone with WM5 to look....
philg2000 said:
I have noticed this too, and it must be something to do with what PIE reports itself as for User Agent.
The sites work fine with Opera, but cant see if that reports as Mozilla for whatever.
We need someone with WM5 to look....
Click to expand...
Click to collapse
I use PIE+ and tried all the user agents, but no change. Also noticed gprs/3g connection is real unstable! I'm in london, so definately a good coverage!
Erm....?
Any ideas?
What is the URL? Assume you have "show pictures" set etc ? I have black 3.1 on T mobile (well, virgin) and connection seems stable. This is on a m3100
Yeah I noticed this before too... I've only installed Black up to 3.0, so it the problem existed in at least version, maybe earlier.
http://wap.orange.co.uk for orange world. WEorks in opera fine. in PIE every other site i look at displays correctly, only orange so far is appearing as plain text.
As for the connection, i'm using the latest radio upgrade. to be honest, the connection was pants when i had the standard os installed, but then upgraded the radio, which improved it. But now i upgraded the os, the connection is worse than ever.
Also, Skype refuses to log in!
I'm pretty much ready to the sell piece of $h1t on ebay and get something else!!
So nobody able to help me?????
I don't use Orangeworld. Sorry. Have not had this issue. What apn are you using, the orangewap one or the orangeinternet one?
crazyC said:
I don't use Orangeworld. Sorry. Have not had this issue. What apn are you using, the orangewap one or the orangeinternet one?
Click to expand...
Click to collapse
orangeinternet
crazyC said:
I don't use Orangeworld. Sorry. Have not had this issue. What apn are you using, the orangewap one or the orangeinternet one?
Click to expand...
Click to collapse
I dont think its down to that in any case, coz it works fine with Opera.
yeah I know, just grasping at straws. I seem to remember that some of the orange sites only worked via the orangewap apn. never use them so dunno really.
Hi, sorry am unable to help as I have same on orangeworld, but would just recommend that before you sell, you try reverting the radio version to 1.38.0.10 or .01.
Makes it a whole different phone, no dropped signals, better battery.
gibster said:
Hi,
Just upgraded my rom, and for some reason, when i go the the orangeworld site in pie, it only displays a text version. No graphics or anything.
Any ideas?
Click to expand...
Click to collapse
Yeah, no problems - orangeworld works fine in PIE for me WITH graphics (after I fixed it of course!!)
First I would recommend the latest Orange Radio ROM which is 1.38.00.01 - works best for Orange UK (this is not necessary for my fix to work though.)
See my cab file which installs the Orange UK MMS and internet settings as well as fixing the voicemail icon issue and the orangeworld graphics issue
If anyone needs it, I suppose I could create a cab file containing just the fix for orangeworld on PIE
Ok, here is the cab to just fix the Orangeworld site on Orange UK - it also fixes the voicemail icon since this is kinda essential
This should work on all WM6 ROMs on Orange UK
ps. you DO NOT need this file if you are using the cab file in the post above
Thanks alot Rabdo!!! I'll try the radio downgrade when i get home!!! Orange now works a treat!!!
Thanks!!
Just a quick question. What was the problem? It almost looked like it didn't pick up the css or something, but the strange thing was the fact every other site i looked at was fine. Would be nice to know exactly what was up with it.
rabdo! my wife can have your babies if you like!
radio fix and settings cab have sorted me right out!
keep getting the "H" symbol. did a quick test and was close to 500kbs! not sure how reliable that is, but just browsing now is a dream, and no connection dropped!
thanks a lot!
gibster said:
Just a quick question. What was the problem? It almost looked like it didn't pick up the css or something, but the strange thing was the fact every other site i looked at was fine. Would be nice to know exactly what was up with it.
Click to expand...
Click to collapse
I have a similar problem on 3 UK in that none of the icons on Planet 3 show up - is this cab something generic that might fix my problem? My phone is working nice and smoothly and the moment so don't want to install it just in case.....
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!