thous who allredy did or going to go from ATT WM6 (leacked) TO oficial Vodafone WM6 whot are the Advanteges and Disadvanteges ??
Couple of positives:
- Seems a bit quicker
- Doesn't have the AT&T junkware clogging it up
I am having a problem with Activesync however. I can only connect as Guest. It does not prompt me to set up a relationship. Unfortunately, I cannot synchronize. Anyone know how to resolve this?
Guest Only key
You need to change the key for GuestOnly in registry on your PC. It's located at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services". Find the key for Guest Only, and either delete the key entirely, or change the value to "0".
I think this is more of a side effect of the hard reset than anything else. I tried the official vodafone ROM against the leaked ATT rom, there was no difference except for the absence of ATT software. When I flashed back to the leaked ATT rom, it was just as fast. The only other difference seems to be that the vodafone firmware version is 1.47.02 whereas the leaked ATT is 1.47.25.
FreshJiveX said:
You need to change the key for GuestOnly in registry on your PC. It's located at "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services". Find the key for Guest Only, and either delete the key entirely, or change the value to "0".
Click to expand...
Click to collapse
Thanks a bunch. That did the trick!!!
how about voice quality?
When I had the Vodafone ROM people complained that they can't hear me well and with the ATT everybody could hear me crystal clear.
can someone confirm they had the same problem
Vanilla Voda Rom?
Hi all. Just wondering. What do I need to do to make this Rom a vanilla one.
There are alot of folders and stuff when you look into the extended rom. I just do not want to delet something that is important for the normal functions of my phone.
Thanks
jeo100 said:
how about voice quality?
When I had the Vodafone ROM people complained that they can't hear me well and with the ATT everybody could hear me crystal clear.
can someone confirm they had the same problem
Click to expand...
Click to collapse
My 750, with WM5 (from factory) had problems when I would use the speakerphone. People would complain of not being able to hear well.
With the ATT leaked ROM (WM6), that problem still remained.
I am glad to report that with the latest, official Palm UK ROM (VFU) I am able to use the speakerphone at lengths with no complaints from folks on the other side. This is a great benefit for me as I use the speakerfone frequently.
As for the voice quality while holding up to my ear or over a BT headset, it's always been acceptable.
Related
There is a file pda2K_2k5.rar on FTP that contains the WM5 ROM for BlueAngel. Origin of the file is unknown, flashing it to my device showed that it is really a WM5 ROM that is working. The OS version is 5.1.1700 build 14343, it has MS bluetooth stack and no camera. The camera drivers are present, so I think it would be possible to extract app from Himalaya ROM.
It has no MMS application and no SIM toolkit.
I've repartitioned DOC, so now I have 61Mb storage area and 128Mb RAM that are fully accessible.
All hardware buttons are working, and the keyboard is working fine, though there is no control panel applet that allows you to turn off its backlight.
Making hardreset is tricky - you have to press camera, record, power and reset buttons simultaneously. There you'll have a choice to use debugger (something about KITL), reset registry and format built-in storage. Navigation in menu is done with camera and record buttons, exit - "mail" button.
Thanks download now .
great it working thanks
So glad I worked late tonight...
Unbelievable! :shock:
Awesome etc.
I think the simplest thing to say is: THANK YOU!
That will not stop me from buying a native WM5 PDAphone like the Universal or the Wizard, but still I'm really happy this happened. If only that could force O2, I-Mate, Qtek etc. to sell an official upgrade, that would be nice...
Until now, I had to put my BA in reserve and used my XDAII for everyday for a single problem: BT!!! Maybe the MS stack here will do as good as the one in my XDAII 1.72. Just need my GPS and headset to work properly. The rest is luxury at this point.
BTW, Mamaich, is the procedure similar as the one for Himalaya WM5? Any difference?
Cheers,
Hal
Mamaich, it's time to make tweaking for the camera and especially the O/S speed.. :?
Did someone take down that RAR file? I can't seems to find it anywhere under BA section on the FTP site.
file
uploads/Blueangel
Sweet!! Thank you!!
maybe we can get the mms application from the universal?
sx66
so...i hawe sx66 from cingular (not locked) rom version 1.33.10 wwe can i upgrade with pda2K_2k5.rar ROM or not...and what i get with that i meen with pocket2005 ? can someone tell me...im new here and i will be gracefull to answer me...
10x
ps. blueangel rulz
Silly Question Really
Buzz Do you think you will be able to get this Rom 2005 Rom to work with Alpine (XDA 2i)
Re: Silly Question Really
Studulike said:
Buzz Do you think you will be able to get this Rom 2005 Rom to work with Alpine (XDA 2i)
Click to expand...
Click to collapse
It would not work on any device other than BA.
maybe we can get the mms application from the universal?
Click to expand...
Click to collapse
At first we need a ROM image rom Universal or better an official ROM update.
unbelievable brother mamaich...but its true... :lol:
Erm...
This is not the same file as on Buzzdev.net is it?
The version is different.
Think I'd have better luck with this one?
Hi Mamaich,
I installed WM5.0 on my PDA2k but unlike you, i only got 49MB storage space. How is it that you got 61MB while i got only 49MB. What did i do wrong?
Also, why am i not able to synchronise with outlook after the rom upgrade?
Thirdly, i can pair my BT headset with my PDA2k but it does not transfer any calls to the headset. I tried using a BT GPS and that works perfectly fine. What do u suppose the problem is?
Would appreciate your comments.
UD.
Has anyone here yet or not weather or not this will work with Sprint or Verizon CDMA phones yet?
Wherez the ROM on the FTP, i searched but i couldnt find it. Its not under BA. Where is it? Is it different from the one that Buzz had on his site?
UD.
wesley762 said:
Has anyone here yet or not weather or not this will work with Sprint or Verizon CDMA phones yet?
Click to expand...
Click to collapse
Still no luck with VZW CDMA, and I haven't heard of a successful case yet.
Yes, the file is the same as the one on Buzz's site.
ftp://xda-developers.com/Uploads/Blueangel/
Hi all
I´ve searched the registry with no luck at all... Is there anyway to lower the backlight brightness? Cause like this it drains the battery really fast! Rudra was right :?
Hey btw i´ve tried my Bt headset and it works better than before!! at least i can go like 5 - 6 meters from my phone and still hear the caller
Just checked the o2 site and it seems this upgrade is now available, not tried it yet but will tonight
hi, which site are you downloading from?
www.my-xda.com
Any news on whether it is worth upgrading to the .171 ROM? Seems as though the radio is back to 1.00?
bobster007 said:
Just checked the o2 site and it seems this upgrade is now available, not tried it yet but will tonight
Click to expand...
Click to collapse
We are waiting for more info about the new rom!
Might be an anomoly but I tried the 171 ROM modified and my device has hard reset twice, with the original ROM the phone stopped working and needed a hard reset to sort it out, twice.
Think I'll keep to my 162 ROM. How's everyone else found it?
http://www.my-xda.com/xda2i_soft3.html
here's the direct link for 1.11.171 - just downloading and will let you know how I get on after discovering that 1.11.170 (blackberry)didn't work with radio version as supplied.
Hi!
When I have install it. It apeared the radio 1.100
So still old radio, not v1.104
phuong said:
Hi!
When I have install it. It apeared the radio 1.100
So still old radio, not v1.104
Click to expand...
Click to collapse
that is correct. Radio 1.104 is not compatible with the Blackberry system. This is the main reason that ROM 1.11.170 was removed from the o2 website as it had upgraded the Radio version from 1.100 to 1.104.
Hi! I've just bought an O2XDAIIi. I just wonder which ROM version I should use to upgrade my XDA. Could anyone give me an advice?
MrSandman said:
Hi! I've just bought an O2XDAIIi. I just wonder which ROM version I should use to upgrade my XDA. Could anyone give me an advice?
Click to expand...
Click to collapse
I'm using Blackberry and have upgraded to the latest o2 ROM - 1.11.171. If you aren't using Blackberry, try using Pugs cooked version of 1.11.169.
Is there any change to Blackberry functionality on 71 over 69?
Won't be changing if there isn't.
I belive that if your using the o2email open and not the BES version you won;t lose your Calendar options.
We use BES so no need to change then - thanks
Well ROM version 1.11.171 seems to be as stable as 1.11.169 and I don't have to use the workaround to sync Outlook Calendar.
I wonder if o2 are going to release more XDA phones that can use Blackberry - I quiet fancy the o2 Atom but it doesn't list BB which is a shame.
171 ROM is the BT reliability resolved
Symbasean,
Stating that the 171 ROM is as stable as the 169 ROM is a little bit of a two edged sword for me.
When I applied the O2 ROM last October / November it trashed my bluetooth functionality, effectively making my Jabra 250V a large black ear ring and the XDA 11i an electronic chocolate tea pot, for use in a car.
Can you sense my frustration with O2, who offered me £10 off my next bill as compensation and then didn't give it to me.
I switched to one of PUG's home cooked ROMs and this has been 80% successful, but randomly fails to deliver the sound.
His version has been a saviour, but would the 171 be an improvement for the BT stability and reliability?
Sorry for the incredibly rambling first post. :?: :roll:
I upgraded to the new software last night and have noticed one small annoyance. I used to be able to to deactivate GPRS by clicking the connectivity icon in the title bar and tapping disconnect. Now the disconnect option isn't there for GPRS. Eventually I discovered that I could turn off GPRS by holding the end call button.
Re: 171 ROM is the BT reliability resolved
dgt1963 said:
Symbasean,
Stating that the 171 ROM is as stable as the 169 ROM is a little bit of a two edged sword for me.
When I applied the O2 ROM last October / November it trashed my bluetooth functionality, effectively making my Jabra 250V a large black ear ring and the XDA 11i an electronic chocolate tea pot, for use in a car.
Can you sense my frustration with O2, who offered me £10 off my next bill as compensation and then didn't give it to me.
I switched to one of PUG's home cooked ROMs and this has been 80% successful, but randomly fails to deliver the sound.
His version has been a saviour, but would the 171 be an improvement for the BT stability and reliability?
Sorry for the incredibly rambling first post. :?: :roll:
Click to expand...
Click to collapse
two points:-
1. please spell my name correctly.
2. "Well ROM version 1.11.171 seems" - note also the word, "Seems". I make no direct comparison on stablity, only that mine has not crashed - caveat empore......
Apologies
Symbaseian
Sorry for the mistake.
I shall try the ROM and see.
I have to agree caveat emptor is an appropriate warning with this particular device.
If it worked as well as it is should, straoight out of the box, it would be excellent.
But it does have some way to go, and without the likes of these forums, it would not happen.
Dave
Re: Apologies
dgt1963 said:
Symbaseian
Sorry for the mistake.
I shall try the ROM and see.
I have to agree caveat emptor is an appropriate warning with this particular device.
If it worked as well as it is should, straoight out of the box, it would be excellent.
But it does have some way to go, and without the likes of these forums, it would not happen.
Dave
Click to expand...
Click to collapse
I totally agree. When I first got one of these I couldn't use TT3 let alone TT5 without it locking up all the time if I used anything other than my old 128mb Compaq SD card, but having listened and learned on this forum and also on pocketgpsworld I now have a stable XDAIIi with blackberry.
It's taken a long time to get to where I'm fully happy with the device (except camera performance - but I very rarely use that anyway) often involving Tomtom tech support, o2 tech support and these forums. If you feel happy using Pugs ROM version without blackberry please go ahead, but for me that's not an option.
It's just a shame that we have had to co-develope to get a product that is finally starting to show everything that it first promised.....
Sorry guys to bug you but i need your help.How can i revert back to
Qtek_9100 old rom 1.6.7.1 after upgrading to 2.8.7.102?I downloaded a new 1.6.7.1 ROM, tried that several times and it kept on telling me that I'm using a newer ROM therefore an upgrade is not possible.Could you outline to me or point me to a detailed info for downgrading cause the new ROM is not stable on my device(Qtek 9100).It keeps on rebooting even during a call and when i'm running other applications.
I'd appreciate your kind help.Thanks a mil.
I have a similar problem. Except I need to go back to my original tmobile MDA ROM. A2DP works fine, but nothing else is working for me. How can I go back?
davidbessler said:
I have a similar problem. Except I need to go back to my original tmobile MDA ROM. A2DP works fine, but nothing else is working for me. How can I go back?
Click to expand...
Click to collapse
Did you backup your original rom? Also is aWizard not letting you go back to your previous rom? I have posted the production T-Mobile USA ROM in a different post on the board if you don't have your old ROM.
I am also curious what the issues are you are having as I have been wondering about trying the test ROM on a USA unit for T-Mobile going from 1.x to 2.x as you did.
I could use a link to the TMO USA MDA ROM just in case I need to exchange the machine. That said, I am having absolutely NO problems with the QTEK TEST ROM. However, I did lvlolvlo's trick and after I had flashed the new ROM, when it said that in 3 seconds it would install the extended ROM, I quickly soft-reset, and then installed the extended ROM stuff from TMobile. This automatically set up my internet, and made the email triggers a snap. I can now use my Motorola STEREO bluetooth headset (even has a mic for the phone). As an added bonus, with the TMO ROM, I was unable to have both MortButtons and MS VoiceCommand installed simultaneously (something about the startup folder), but with the QTEK ROM they both work.
You know, I came from the 6315, and this machine is FLAWLESS ... really a top-notch device, with the QTEK ROM, it is even better.
If you would like me to test out any functionality with this configuration, let me know, I'd be happy to test it out.
Can you get me that link to the original TMO ROM just in case?
I posted this not too long ago. It has the main rom and a link to the extended rom.
http://forum.xda-developers.com/viewtopic.php?t=42130&start=0&postdays=0&postorder=asc&highlight=
The reason I ask about your functionality is that you said your bluetooth stereo profile was working now but nothing else was? I am tempted to switch to the newer rom but not without some assurance it works semi decently. I am mainly interested in the Radio rom upgrade as mine seems to take a while to re-obtain a signal once it is lost and it ocassionally appears to not accept calls (going to voicemail) even though it has signal strength.
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Downloaded it from HTc.cOM
Installation instructions
Follow the instructions below to download and install the hot fix on your device:
Make sure you have Microsoft ActiveSync® installed on your Windows XP PC or Windows Mobile Device Center on your Windows Vista® PC. You can find Microsoft ActiveSync from this link or Windows Mobile Device Center from this link.
Connect and synchronize your device with your PC via Microsoft ActiveSync® or Windows Mobile Device Center using the USB cable.
To download thehot fix, first select the check box below. Next, select thehot fix and the desired FTP site then click Download.
Copy the hot fix, which is a cab file, to your device.
To install the hot fix, tap the cab file and follow the on-screen instructions.
Here is the file:
http://rapidshare.com/files/77588898/TyTNII_BT_Hotfix.zip
Enjoy,
Nadavi
for tytnII, but how about att tilt? is it rom specific?
Hope this will work. Thanks for the tip.
private69 said:
Hello,
HTC have publied a HOT FIX FOR BLUETOOH
"/12/2007
Bluetooth Hot Fix (for HTC TyTN II)
Dropped calls sometimes occur when Bluetooth is on. If you encountered the same problem, please download this Bluetooth Hot Fix and install it on your device.
Go to htc club an enjoy.
Click to expand...
Click to collapse
This does not show up on the updates for my TyTynII (downloads are serial number specific) only in the generic downloads.
I think its best if you only apply this IF you suffer with any Bluetooth problem.
The old adage, 'If it ain't broke, don't fix it!'
Re: does this work on AT&T Tilt?
In the HTC 1.56 ROM, this file is a replacement for \Windows\TIInit_4_2_38.bts a.k.a. (OEM\OEMDrivers\TIInit_4_2_38.bts for chefs). There is nothing else in that cab (see upgrading forums thread for better description)
Edit: I was wondering if I kept quiet, how many people would have experienced a placebo effect and said that it works great and makes bluetooth 10x better on AT&T...
Summary
If you happen to be an AT&T Tilt user that has flashed to an HTC ROM, this fix will work for you. If you're running an AT&T ROM, or you have no idea what a ROM is, but you know your phone says AT&T on it, it does nothing.
Does this fix the issue were bluetooth is dropped after finishing a call ?
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
I have install the update listed above on a Tilt running the RUU_Kaiser_HTC_WWE_1.56.405.5_radio_sign_22.45.88.07_1.27.12.11_Ship Rom and the Bluetooth quality has jumped 100%. My Bluetooth stereo headphones sound great.
Thanks for starting this thread.
Awesome, thanks! I was going to ask if anyone had drop call problems as it happened to me twice last night and I happened to have my BT headset on
sirooga said:
Thanks for letting us ATT users know that it doesn't do anything. Guess we don't have this issue But on a serious note does this actually fix anything besides a supposed call dropping? I don't have that issue but of course we all have tons of issues with BT quality.
Click to expand...
Click to collapse
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
kaluzu said:
I have a lot of crackling background on my BT headset. Did not have that on the 8525. Also, there seems to be less functionality supported in the Tilt implementations, regarding the BT, vs the 8525 (I was running a cooked ROM though on my 8525). What i mean by that, is that I was able to use the BT buton to activate the voice dial using the MS VM. In addition, hitting the BT button twice was getting me a redial. Not anymore. I wonder is this has to do with the AT&T ROM or not? Is this a genuine HTC issue?
Click to expand...
Click to collapse
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
_Alex_ said:
This file does not exist in the AT&T Tilt ROM, so it's doubtful it will harm or help to install this.
Click to expand...
Click to collapse
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Is rapidshare the only place to get this? I am behind a firewall.
jgermuga said:
Is rapidshare the only place to get this? I am behind a firewall.
Click to expand...
Click to collapse
Cab fix attached.
akadonny said:
I checked the AT&T's 1.60.502.3 rom and it does exist. I didn't check the stock AT&T rom so I don't know if it wasn't there. I did a file comparison with ExamDiff between HTC's fix (22,490 bytes), AT&T's 1.60.502.3 version (22,490 bytes) and HTC's 1.56.405.5 version (23,899 bytes). It appears AT&T's newest rom already has the fix so anyone using the following roms should not have to apply the fix:
AT&T stock 1.60.502.3
Kyphur's XDA Live
Dutty's AT&T Variants
Custel's Series
_Alex_'s 1.60
any of DK's roms (shameless plug)
Click to expand...
Click to collapse
Just realized this while doing some diffs and was going to repost. (Microsoft file find sux ) Original post edited...
mfrazzz said:
Before I switched to Dutty's ROMs, I was running the stock Tilt Rom for a few days, and then the newer Tilt ROM for a week. Both of those AT&T Tilt Stock roms gave me no issues like you mentioned. I heavily use my BT headset (Jawbone), and use Microsoft Voice Command (I very seldom use the dialer as its easier to just speak and have the phone dial for me). Pressing once on my headset would always bring up MS VC so I could issue it commands, and pressing twice on my headset always did a redial.
Now that I'm on Dutty's 7b, I have the same behaviors there too. Not sure what to tell you (other than some BT headsets don't work well with WM6, but if you were using the same headset on your 8525 then thats probably not the case).
As always... YMMV
Click to expand...
Click to collapse
Give this a read. I have MS VC 1.6 working just fine on my Jabra BT250 after following the instructions.
you can ignore the first part about removeing the cybertron dialer or whatever.
http://forum.xda-developers.com/showpost.php?p=998205&postcount=9
I'll try it. Thx for the tip. I am not sure if this only works for 8525/TyTn (I do have the TyTn II/Kaiser)
Edit:
Tried. Sorry, did not work. Oh well. will see, but for now I wil stick with the AT&T ROM.
Hi,
there is something weird about that fix:
when the cab is on the kaiser, you tap on the file to install it.
you believe it's installed but in program files , you may find
a "kai6492_hotfix" shortcut, you tap on it and the choices are install or exit
it's seems there an identity check to be sure it's on a kaiser
"module id is kais(required kais)"
then if "equal" "ok" then install
and soft reset needed
why two install required ?
the kai6492_hotfix is still in program files after that
and last VC1.6 was working on my bt headset(but the voice recognition succeded about only 10%,i think because of audio quality when i am speaking) but i could ear vc1.6 replies ou questions)
now it is not working anymore.
when i click on the button(headset) before it was launching voice command as the harware button (assigned to it) could do it
now the same button launches the phone dialer(as i was tapping on "call"(green phone)).
ps; since that hotfix, i haven't been able, any more, to install btIO-0.6-wm5 cab
Deleted cause not worth it....
Hello! I've been lurking around these forums for a while. Off and on I would come and check out some stuff. Well I have a problem.
When I upgraded to the official AT&T rom from HTC's site, I noticed something strange. The network icon that tells you if you are in EDGE territory or 3G or GPRS or whatever...it shows basically I'm not connected to anything. It's a slight annoyance because I know the 6.0 rom showed I was in EDGE with an E. You guys know what I'm talking about? Any fixes? If someone already asked this question then I am sorry (hides). I couldn't think of what to search for.
*Flash Kick Bump*
Add the following Registry Key:
Code:
HKLM\Software\Microsoft\Shell\Taskbar\LegacyEdgeNotification
as a DWORD with the value (1).
Ta
Dave
Ty Dave! I shall download the appropriate regedit software for 6.1 and get it on!
Dave...that didn't work. I applied the key, soft reset the phone, nothing. anything else i could try?
Turbo Mach 5 said:
Dave...that didn't work. I applied the key, soft reset the phone, nothing. anything else i could try?
Click to expand...
Click to collapse
That should work for Edge. Try LegacyGprsNotification as a Dword and Value 1 forr the GPRS Icon instead.
Ta
Dave
Nope I wonder if PHM Registry Editor isn't really applying the key. It should...Let me try another reg edit.
Unfortunately that didn't work either )CeRegistryEditor(
AT&T couldn't have locked this down on their official 6.1...could they?
Hmm Daddy Might have to go ask a chef if we can't find a solution. Now I know that the network couldn't have screwed up on that particular day because my mother's Blackberry (yah I know, different) shows GPRS and I KNOW my phone should show EDGE/Gprs...
It can't be because I am using the same sim card as I had before (and not using the one that is branded AT&T 3G). Just trying to throw out some ideas
Turbo Mach 5 said:
Unfortunately that didn't work either )CeRegistryEditor(
AT&T couldn't have locked this down on their official 6.1...could they?
Hmm Daddy Might have to go ask a chef if we can't find a solution. Now I know that the network couldn't have screwed up on that particular day because my mother's Blackberry (yah I know, different) shows GPRS and I KNOW my phone should show EDGE/Gprs...
It can't be because I am using the same sim card as I had before (and not using the one that is branded AT&T 3G). Just trying to throw out some ideas
Click to expand...
Click to collapse
I've cooked several ROMs based off of the Official AT&T 6.1 ROM, and I can verify that it does correctly display G, E, 3G, and H icons. What other software have you installed?
The only other software added:
Garmin Mobile XT
M:Metrics Mobile Panel
Opera 9.5 Beta
PHM RegEdit
mfrazzz Transformer Sliding Sound
DK no Ringtone limit
Customization Tools and Customization Customize_Tool
and the Cingular crud
think it could be one of those? I have verified it not even showing if I do a hard reset. Maybe my Tilt hates me hehhe like I siad I could live without it but it is annoying not being able to see if I'm in EDGE or GPRS (or 3G if and when I enter a 3G area)
Ok I tried Advanced Configuration Tool (or whatever it's called ) and while it does apply the registry setting, the rom won't take it still. Now I just thought about this:
When the official rom came out, I did download it that day (September think it was). Could they have slightly changed the binary since and I just never knew about it?
Another thing, you think reflashing it would at least allow me to edit the registry properly?