Develop Bugs

Mobile operator shows up as number

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...

PIE 6 defaults to "This Address is not valid"

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!

Has your TomTom Device ID changed?

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!

New XDA Zest firmware

There's a new Zest firmware available for download from http://www.my-xda.com/. The filename is Xda_Zest Firmware Update_V7.7.0S.WWE20.00_M4.6.5.P7_V2.1.4 GBR20, which seems to be updates to most of the roms inside the zest. It's installing at the moment, and the upgrade interface on the phone is displaying "GalaxyMini5 Eboot (3.33.0). Since this appears to be a codename for the P565, I guess this is more evidence that the XDA Zest is simply an underclocked P565 and more evidence that P565 firmware may well work on it.

Warning, this firmware does not appear to contain the O2 menu software, or the free GPS software that comes with the phone (although maybe the latter can be re-installed from the SD card). Shame - I rather liked the O2 menu interface.

what improvements does it have? Is it actually worth upgrading?
Thanks.

The only things I can see that I don't remember seeing before are a couple of new or updated control panel entries. Video calling is probably the really important one.
You seem to lose the RSS reader, the O2 auto settings, the O2 menu and the GPS s/w (although the latter was only a demo). I have no idea if using the SD card that came with the Zest will restore these, as I don't have it. (If the software is all on there somewhere, and someone could bung me a copy, I'd be really grateful.)
It does make me wonder how the P565 firmware compares. I understand it has a nice touch interface on it.

It seems odd that the new firmware would remove all the o2 specific bits. Great if you want to use it on another network I suppose, but I quite like the mobile shell or o2 menu.
The satnav software isn't on the sd card - only the maps.
The instructions say:
Please note that if you already have CoPilot satellite navigation software on your Xda, refer to the Xda Zest user manual before upgrading your device software.
Click to expand...
Click to collapse
I couldn't see anything of significance in the user manual.

Interesting. I actually have Tomtom for GPS on a different SD card, which is related to the reason I don't have the original SD card. Tomtom autoinstalls from the SD card, so I thought it might be that the O2 software installed itself from the SD card provided by O2. I guess that if it's only maps on the SD card then that's not the case, and the new firmware does strip out all the O2 extras, which seems like a peculiar decision to say the least.
Still, it did get me to try the new SPB mobile shell 3, which is what the O2 menu is based on, but nicer. I'm trying to decide whether it's worth the $35 for just a flashy finger driven interface. The weird thing is, it actually might be.

I'm actually going to upgrade my firmware to new one which is currently available in O2 site. What I want to know is if upgrade mine to the latest what would be the changes I may seen... Is it worth upgrading by loosing all the software?

So far I've seen nothing to write home about. The only reason might be if you can't already make video calls and want to do so. (I never make them, so I have no idea whether or not they're supported in the original firmware.)

I just upgraded mine to new firm ware. It worked fine for me. I didn't lose any O2 extras inc O2 menu. It was Oki but haven't tried yet to make video calls.. I will install iGO8 and will uninstall the co-pilot.
SPB Mobile shell 3.0 Rocks working smoothly with my Omnia and Xda Zest

I've just updated, and I didn't lose any O2 extras either (including Copilot). I backed up the Program Files\Copilot folder on the device to my PC before updating, and copied it back over after the update and voila, I've still got my fully activated version of Copilot. It did still prompt for allowing it to connect to the net during the 14-day trial the first time I ran it, but the license screen confirms it's the full version.
aDe

I have a working theory that the autorun on my Tomtom SD card might have run in preference to some autorun that might otherwise have run the first time the OS booted. I could test this by re-installing the firmware, but it's kind of a pain to have to put all the data on again.
Having played around some more and browsed the Extended ROM on my device, this does appear to be what happened, as all the CAB files are present. Fortunately this is a bonus for me, since I'm not on O2, and most of these files are useless to me, and I can therefore just pick and choose the apps I'd like to install.
This might be useful to other Zest users - the hack to make the Extended ROM visible:
Use your favourite Registry Editor to make HKLM\System\StorageManager\Profiles\ONDisk2\FATFS\MountHidden set to 0 (default is 1)
You can then browse to \ASUS_ROM\ in Total Commander to view your Extended ROM partition. The ROM does not appear to be write protected, so you can now put all the packages *you* want re-installed on a hard reset in there. Neat.

I contacted O2 support about this issue, and they replied saying that:
On occasions the O2 menu can drop off after a ROM upgrade, but this would usually be resolve by either hard resetting or running the upgrade again. The o2 menu is still installed on the new ROM.
Click to expand...
Click to collapse
I have now done this upgrade and have retained the 02 menu. The radio reception seems a bit better as I now get HSDPA at home, which I didn't previously, so the radio upgrade seems to be worth it.

ringer
ive got the zest and am happy with it so far apart from the last 2 days i cannot hear it when i get a call everything else works ie.system sounds,core player etc but the actual phone wont ring it just vibrates ive reset it a million times and checked system settings etc but nothing so if anyone has any ideas i would be very grateful, also how do you know if you are getting hdspa or not is there a setting for it or something, cheers guys.

The connectivity icon at the top right of the screen shows what communication protocol is being used by showing a symbol (usually just a single letter) in a solid square. The letters I have seen so far are:
G - GPRS (2G)
E - EDGE
3G - 3G (this is the odd one out with the two letters squashed together)
H - HSDPA
It's worth mentioning that on my train ride home I see all four protocols at different points, and the hand-off between them is very smooth.

thanks for quick reply i will keep an eye on it, still no joy with my ringer though its very strange. never had a problem like it on my orbit. i will keep investigating ,also do you know if anyone will be coming up with a rom for zest as i miss manila 2d although mobile shell v3 is good.

Have you checked:
Start->Settings->Sounds & Notifications
On the Notifications tab you can select the "Ring type", one possible choice of which is "Vibrate", which will make the phone only vibrate on incoming calls. Just guessing.

yes ive tried all that it might be affected by software ive installed recently i will try unistalling them one by one and see if that helps, failing that il do a hard reset i guess, anyone know how to hard reset the zest? thanks for your help.

There is a contortional key sequence for this, but you can also reset it by going to:
Start->Settings->System Tab->Default Settings

cheers managed to sort it , i installed mini lyrics software and ticked all in associating files which for some reason stopped the phone from ringing
thanks for your help.

Failure of firmware upgrade
Ive just had a power failure whilst upgrading the firmware on my new xda Zest and all it it shows when turning on is "OS Update failed! Please update again". Is there anything i can about this or will it need to be returned to O2. Any suggestions. thanx

Blackberry Connect

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