Database Develop

T-Mobile New ROM info

Hi yawll,
Just a heads up for all those who are wanting info on TMobiles plans for the Vario, I am havign emails with tech support atm who are saying there is a new update planned for the end of June that will include the extras we are seeing in the recent Qtek and Imate rom releases...
Dunno why there taking so long? I mean to release an update then pull it takes the mick, but to wait three months longer than other carriers to release an update makes me :evil:
Cheerio,
Veef13

Thx
Thx for the update though fella

I applied the i-Mate upgrade to my T-Mobile UK Vario and selected the T-Mobile UK operator option when applying the customisation.
It still didn't setup the GPRS APN stuff - which I expected it to do. Before I was using the T-Mobile shipped ROM.
Is this normal or is there something missing from the customisation?
I also tried the separate t-mobileUK.cab and that didn't set up the GPRS either.
Thanks

cliffai said:
I applied the i-Mate upgrade to my T-Mobile UK Vario and selected the T-Mobile UK operator option when applying the customisation.
It still didn't setup the GPRS APN stuff - which I expected it to do. Before I was using the T-Mobile shipped ROM.
Is this normal or is there something missing from the customisation?
I also tried the separate t-mobileUK.cab and that didn't set up the GPRS either.
Thanks
Click to expand...
Click to collapse
as far as i'm aware thats normal.. the tmobile cab files have never setup mms gprs etc for me

Re: Thx
Big D said:
Thx for the update though fella
Click to expand...
Click to collapse
no worries... wish they'd pull their finger out tho!

Would any kind person be able to generate a new UK T-Mobile.cab that did configure the GPRS & MMS settings as well and perhaps add back in the defaults favorites/homepage url.
I'm sure this would get a lot of use now we have this new generic i-Mate firmware available
Thanks
Cliff

cliffai said:
Would any kind person be able to generate a new UK T-Mobile.cab that did configure the GPRS & MMS settings as well and perhaps add back in the defaults favorites/homepage url.
I'm sure this would get a lot of use now we have this new generic i-Mate firmware available
Thanks
Cliff
Click to expand...
Click to collapse
Easiest way is grab hold of the Tmobile Extended Rom from the FTP and use the two connection configuration files in there, job done!
but at the same time a working cab would be spot on!

I read an interesting conspiracy theory the other day that theorised the reasons why T mobile are going to be late with an upgraded ROM.
“There are devices running on the AKU2 out there, HTC devices even. Could it be that it is not the new ROM that is causing problems, but the T-Mobile Exchange platform offering push e-mail that T-mobile has announced? With push email in the new ROM but a Exchange platform that is not ready yet, users can easily go to some other service provider to get working push e-mail their. Without the ability to use push e-mail on their SIM locked devices however, MDA Vario users have no other option but to wait for the ROM that does support push e-mail to be released by T-Mobile”
Not my words I must stress, but there's generally no smoke without fire....

Can you confim which are the connection files in the extROM is it
CAB-Customization-Connection-TMUK-Wizard-Aug08
&
CAB-Customization-WapPush-TMO-Wizard-Sep02-1
?
Thanks

hi,
you really only need the first one you highlighted... If you install the second one without the 2nd part of the wap push profile you'll get "cannot find elateservice message ever reboot" you may also want the file called CAB-Customization-TMUK-Wizard-01-04-03Oct05
Cheerio...
Veef13

Cingular 8125 users: 2 custom RUU upgraders available on ftp

Howdy yall,
I've created 2 executable ROM upgraders for Cingular 8125 users.
The first is a RUU package that will restore an 8125 to it's 100% stock shipping state.
This file is on the ftp at:
ftp://xda:[email protected]/Wizard/Roms/Cingular/Cingular_RUU_1.8.11.1.WWE.ship.exe
The second file is a customized version of the latest Qtek AKU2 ROM. It requires that your device be CID unlocked to install. It includes the Qtek OS, Radio, IPL, and SPL ROM parts untouched. The extended ROM has been customized as follows:
-all Cingular customization cabs included EXCEPT "Singed_gprsstall_1228.sa.cab" which breaks wifi.
-cab created by ammar to allow enabling wireless Today screen item.
-SPCS cab to allow install of unsigned cabs
-PPCContactsMgr cab created by ammar to allow for selecting/deleting multiple contacts
-P_removeBTicon cab to remove the battery indicator in the tray
-P_DisconnectButton3s cab to allow for gprs disconnect when holding end key 3 seconds
SPLASH screen display order is set to Cingular, Cingular, Windows Mobile (same as stock)
I left the "Get Express mail" and Goodlink stuff despite wanting to blow it away.. =)
This file is on the ftp at:
ftp://xda:[email protected]/Wizard/Roms/Cingular/Cingular_RUU_WIZARD_217_AKU2_WWE.exe
Hopefully this is useful to Cingular folks who want to either go back to stock easily or go to the latest AKU2 ROM while maintaining Cingular customizations.
I take no responsibility for what happens to your device or the price of tea in China if you decide to use these RUU upgraders. I have swapped between the two versions several times today without problem.

your gonna make a lot of people happy with this easy process.
does this turn everything back to OEM spec ? including IPL etc ?

FarSeide said:
your gonna make a lot of people happy with this easy process.
does this turn everything back to OEM spec ? including IPL etc ?
Click to expand...
Click to collapse
It does indeed. The IPL/SPL is returned to 1.08. I know there's probably a lot of folks who didn't want to try the new AKU ROM for fear of not being able to return to a 100% stock version....you can now do that easily.

Dude your awesome! I always put the newest rom on my device anyway, but its nice to know (in case device breaks) I can bring it back with no worries.

Absolutely awesome summiter! Just like the wayback machine that Mr. Peabody and Sherman would use in the old cartoon! Worked like a charm. (Forgot how slow that original ROM is...) Looking forward to installing your Cingular 2.17.
Thanks again dude, you're definitely gonna make a lot of people happy.
Steven

This is even better than what I was looking for originally. I wanted everything to be exactly like the 8125 on my Qtek 9100 because I'm on Cingular (I just like how the 9100 looks compared to the 8125). Now this came along as something even better - the newest Qtek 9100 ROM with the best combination of Cingular settings! I can't thank you enough!
EDIT: Hmm, everything works beautifully except one main thing: when I tried adding my GMail account to Outlook, I got to the point where it asks if it's a POP3 or IMAP4 account. I select POP3 and name it GMail, but when I click Next at the bottom, nothing happens. It's as if the button does absolutely nothing. Because of this, I can't add my email account because I can't proceed to the final step. Is anybody else having this problem?

I found it on Hofo posted by JediCorrado.
yanathin try this and let us know if it works.
Incoming Mail: pop.gmail.com:995
Outgoing Mail: smtp.gmail.com:465
under Options check "Require SSL Connection" "Outgoing mail requires authentication" "Use separate settings"
Click Outgoing Settings
Enter your username, password, check "Require SSL for outgoing mail"

The problem is that I can't even GET to the point where I enter my incoming/outgoing server... The "Next" button leading to that screen won't do anything. I had GMail working before the new ROM update just fine. (sorry for the slightly off-topic posts)

Sorry yanathin, was just trying to help.
I keep looking and post if I find anything.

biggie ups to you, summiter
so i'm a pansy, and i dinna have the brass ones required to futz with my stock cingular 8125... until this came along. just finished popping on the official qtek rom, and things appear to be running swimmingly. will mess around more later because i want a2dp so i can stop carrying my logitech dongle around, but thas neither here nor there.
excellent, EXCELLENT post. thanks much, chief.
EDIT: i got mine all set up, and i have to reflash, but i don't even care, because you're awesome in the first place for getting this up, and awesome again for fixing it on-the-spot-like. biggie ups again. downloading again now =)

awesome, im gonna give this a shot soon

yanathin said:
The problem is that I can't even GET to the point where I enter my incoming/outgoing server... The "Next" button leading to that screen won't do anything. I had GMail working before the new ROM update just fine. (sorry for the slightly off-topic posts)
Click to expand...
Click to collapse
I think I know what the problem is - gimme a few minutes to check things out and I'll upload a fixed installer.

Thanks soo much for the new rom package
I just finished loading my apps back on the cingular 8125, and it all works great, and much faster than the stock cingular rom. Exellent Work!

summiter said:
I think I know what the problem is - gimme a few minutes to check things out and I'll upload a fixed installer.
Click to expand...
Click to collapse
That would be wonderful if you could fix it... Aside from the ugly pasted Cingular logo on the Phone screen and Incoming Call pop-up box (I love it when Cingular just "pastes" their logo on things, no matter how it looks :x), this ROM is darn near perfect!

yanathin said:
summiter said:
I think I know what the problem is - gimme a few minutes to check things out and I'll upload a fixed installer.
Click to expand...
Click to collapse
That would be wonderful if you could fix it... Aside from the ugly pasted Cingular logo on the Phone screen and Incoming Call pop-up box (I love it when Cingular just "pastes" their logo on things, no matter how it looks :x), this ROM is darn near perfect!
Click to expand...
Click to collapse
Is this a definate confirmed bug with the current installer? If it is I figure I should wait because I use my mail on the road everyday. If anyone has more info - please let us know. Thanks for creating this ROM and for looking at it again---as someone who has been afraid of updating but really anxious, this is really exciting.

JMD0116 said:
yanathin said:
summiter said:
I think I know what the problem is - gimme a few minutes to check things out and I'll upload a fixed installer.
Click to expand...
Click to collapse
That would be wonderful if you could fix it... Aside from the ugly pasted Cingular logo on the Phone screen and Incoming Call pop-up box (I love it when Cingular just "pastes" their logo on things, no matter how it looks :x), this ROM is darn near perfect!
Click to expand...
Click to collapse
Is this a definate confirmed bug with the current installer? If it is I figure I should wait because I use my mail on the road everyday. If anyone has more info - please let us know. Thanks for creating this ROM and for looking at it again---as someone who has been afraid of updating but really anxious, this is really exciting.
Click to expand...
Click to collapse
It was one of the Cingular cab files. Apparently there was some issue with MMS and Cingular had a cab file that applied some sort of hotfix. Well this hotfix isn't needed with the AKU2 ROM and all it did was break mail. I've removed that portion of the offending cab file, repacked, and I'll upload the fixed installer afer I finish one more round of double checking. I've deleted the old one off the ftp, so when you see the 2.17 installer back up it will be the fixed version.

summiter said:
JMD0116 said:
yanathin said:
summiter said:
I think I know what the problem is - gimme a few minutes to check things out and I'll upload a fixed installer.
Click to expand...
Click to collapse
That would be wonderful if you could fix it... Aside from the ugly pasted Cingular logo on the Phone screen and Incoming Call pop-up box (I love it when Cingular just "pastes" their logo on things, no matter how it looks :x), this ROM is darn near perfect!
Click to expand...
Click to collapse
Is this a definate confirmed bug with the current installer? If it is I figure I should wait because I use my mail on the road everyday. If anyone has more info - please let us know. Thanks for creating this ROM and for looking at it again---as someone who has been afraid of updating but really anxious, this is really exciting.
Click to expand...
Click to collapse
It was one of the Cingular cab files. Apparently there was some issue with MMS and Cingular had a cab file that applied some sort of hotfix. Well this hotfix isn't needed with the AKU2 ROM and all it did was break mail. I've removed that portion of the offending cab file, repacked, and I'll upload the fixed installer afer I finish one more round of double checking. I've deleted the old one off the ftp, so when you see the 2.17 installer back up it will be the fixed version.
Click to expand...
Click to collapse
Oh you rock! Thanks

The fixed installer has been uploaded. Use the original link in the first message of this thread to grab it.
My appologies to those folks who got their devices all set up and have to reflash.. :?

that worked out great! my 8125 was acting all retarded and not picking up any signal at all for about 8 hours and after i installed the upgrade package, it worked like a charm. anybody else have any problems with the 8125 dropping connectivity completely?

dormido said:
that worked out great! my 8125 was acting all retarded and not picking up any signal at all for about 8 hours and after i installed the upgrade package, it worked like a charm. anybody else have any problems with the 8125 dropping connectivity completely?
Click to expand...
Click to collapse
Were you using the original stock ROM when you had these issues?
I have 4 Wizards, and 3 of them had problems locking up and losing signal with the original Cingular ROM. Cingular blames the problem on bad SIMs. After flashing to AKU 2 I've had no problems with any of the devices, so the update is either handling flaky SIMs better or Cingular was taking the easy way out of the problem. haha

Palm Threading App on keiser

I installed the Palm thread app ripped from WM6 device board and everything works except sending MMS I keep getting out of memory errors. I made sure that the pic is under 300k but as soon as I hit Send I get the message. I'm with cingular/at&t. I have searched regarding this but I noticed that for some people it works fine and other not so its hit or miss. But I wanted to know if anyone else has tried to use this on there kaiser.
Thanks

i tried it and no, you cant send any MMS's (I tried some of the other varients found elsewhere on this forum but none work better). In fact I found that this app had knock on problems all over my TYTN II and slowed down the machine considerably. Since this isnt an app you can just remove I had to do a hard reset.

Thanks for the reply hopefully someone figures out a fix for the slowness and mms not working on the tytn II

No one else has tried Palm threading app on there Keiser yet? and has mms working with AT&T??

I too tried it on my Kaiser and could not get the mms to work no matter what size file I tried, it would give me the memory error. I was able to uninstall it through the add/remove programs though and not have to do a hard reset.

jhernand1102 said:
I too tried it on my Kaiser and could not get the mms to work no matter what size file I tried, it would give me the memory error. I was able to uninstall it through the add/remove programs though and not have to do a hard reset.
Click to expand...
Click to collapse
I am experiencing the same. Luckily I don't use MMS very much so if I absolutely need it I can Uninstall Threaded SMS and fetch the incoming MMS then re-install threaded sms. I had same issue with Cingular 8525..Too bad, this is the best threaded sms app out there to me. I can't understand why they haven't built a threaded sms app that comes pre-installed. So basic. Everyone uses SMS. What are they thinking?

any updates on this one yet? I miss my threaded SMS/MMS

**** it doesnt work for me either
****ing BS...please shogun mark, HELP!!!

i wanna stress how important this app is to me.....i was sooo ****ing excited to go from 8525 to kaiser. this actually almost makes me wanna go back.... even though the kaiser is soooooo much sweeter. im beggiing someone to please please work on a fix for this!! please

has anyonetried setting up theconnection settings by hand in the Palm app? I always did myself and it works great

austinsnyc said:
has anyonetried setting up theconnection settings by hand in the Palm app? I always did myself and it works great
Click to expand...
Click to collapse
Which version of Palm threading app are you using?? I have tried to setup the correct settings for the ATT mms part and still as soon as I try to send a mms i get the "out of memory error"

if anyone gets it to work they are brilliant...i have the shogunmark version from windows mobile 6

ttttttttttttt

It is a known bug in the app. Just be thankful we have what we have. To better understand, go here:
http://forum.ppcgeeks.com/showthread.php?t=621

Works for me. The Shogun version thats circulated around doesnt work. You need the full version. Do a search and you might find it. THe problems are the same on most WM6 devices, and not just the Kaiser.
P.S. Some f-in patience might make people actually want to help you. 6 posts, half dropping F bombs doesn't endear you to the community.

Temporary Fix
Well this is what I do to have palm threading and MMS working on my Tilt witch is something I have asked before but haven't gotten an answer but this is my crazy hack or whatever you want to call it.
My theory was well since the MMS portion for Palm threading is out of the question regarding a fix from what I have been reading about. I asked before If after you install palm threading is there away to enable again the default MMS application that came with the phone like that giving you the option to use palm threading for Txt's and sending MMS' to be sent by the default application witch i like better.
I have the files but I dont know where to upload them too but if someone can post them up I will send it to them.
Basically I managed to get me the cab installation of Arcsoft MMS composer ver 4.0.21.28 .. I noticed that tilt has a new version 4.0.3.?? anyways so basically this is what I did..
1) install Palm threading application - reboot device
2) Install Arcsoft MMS application - reboot Device
3) Install EnableMMS.cab - Reboot
4) Re-apply ATT MMS cab configuration so that MMS gets configured
Now when I press on the email key I get the option to compose a MMS and I can receive them fine..
Like i said this is something I just tried for the heck of it and it worked but I dont guaranteed it will work for everyone. I have tried this on the Tytn II and now I just received my Tilt and it works good.
If there was a way to just re-enable the MMS portion I think there wouldnt need to install the slightly older version of arcsoft composer viewer but I havent able to figure it out..
PS. I tried uploading the zip files but it keeps telling upload of file failed..

Can you e-mail me those files, please.

Hi, is someone able to upload these files somewhere?......thanks in advance

ok here they are.. Let me know if they work for you
http://rapidshare.com/files/61245824/MMSsetup.zip

Thanks doug0365, i will have to do a full backup first on my kaiser before i install the files......its missing the threadersms.cab though....but thats ok i found the file in the kaiser forum.......will report back later today of the outcome.....thanks again.

EnergyROM can't add a MMS server?

hey everyone. I flash EnergyROM two days ago, and I'm facing a rather important bug that trouble me, I can't add a MMS server from Messages - All Messages - menu - Settings - Options - MMS server, when I click "new" to add a new MMS server, there is not any response, nothing happens. I wonder if some other guy who flash the same ROM is facing the same problem and how can I fix it? THX very very much!
Here is my machine's information, SE X1 with EnergyROM KOVSKY 20090914 StandardM2.5.

Shouldn't you ask this in the EnergyROM thread rather than start a new thread?

ipporek said:
Shouldn't you ask this in the EnergyROM thread rather than start a new thread?
Click to expand...
Click to collapse
I'm sorry but There are too many replies in EnergyROM thread..

i m having the same problem, but a little bit different, i can set up the mms server, but it does not work in any way, i was searching in registry and found many entries with HTCs servers, cingular servers, but i m brazil, and cant put the mms to work, even changing tre registry entries, but as i dont know very well how to manipulate the registry its still not working, both ways sending and receiving

MMS Issue with Energy ROM
Yeah.. I totally love this particular rom of all the ones out there and picture messaging hasn't worked for me either.. I'm U.S.-ATT
I've actually been sending via email as a work around because I like the rom that much.. Hope this does get resolved...

That problem is due to the leo message app? I have never really got mms working properly when using different roms with it cooked in. Try setting up the connection manually.

Well, i had already tested the jack4.x rom, MultimediaOS from KidDc(i think) and this perfect and bealtiful energy rom, and the only one that was able to send mms was the multimediaOS, but the ROM is ugly and still imature, no good for me...
Im using the operator TIM here in brazil...
if anyone has the solution...
I dont know too, if the energyROM already comes with arcsoft, or it attempts to send via other software(because in system/remove programs, it does not show nothing)
PS: in the multimediaOS the arcsoft version was 5.0.43.98, but neither google could find it...

here is the only solution :-
http://forum.xda-developers.com/showthread.php?t=556614
Regards

newstar said:
here is the only solution :-
http://forum.xda-developers.com/showthread.php?t=556614
Regards
Click to expand...
Click to collapse
THANKS. It really works. but with a pity that can't use HTC message, I love the beautiful looks.

recieving very small mms! PLEASE HELP

Hey there,
I have a touch diamond 2 with official ROM and i live in armenia i use MTS armenia sim card i went to costumer support they said its my phone problem and my phone is scaling the picture down but i dont belive in that.i read the other posts i tested the registry tweak but it didnt work someone please help me.

Yeah the phone has a higher res screen and the picture was sent from a phone with a small screen and sorry camera or screen size. That is why your picture is small. Try saving it and viewing it with the HTC album and Zoom-in. That should work.

no that is not the problem becuz the pictures recieved are max 3kb. so its a thumb.

Glad you asked this question as I have the same problem on o2 in uk. I tried the reg tweak from here: http://forum.xda-developers.com/showthread.php?t=359584 but it didn't help.
I'm hoping somebody has been able to solve it and can post.

I just want to add a +1 to this. Im currently using Duttys WM6.5 ROM R5 going to use R6 now, could it be a setting that is wrong?

im using the topaz essential 3.7 rom and this solved my "tiny" mms problems that i had with the other roms. hope this helps!

sounds like post#2 had it right. While you CAN change the max send/receive limit on MMS messages... typically they are 300k by default; usually the receive limit is 600kb. Here is my edited MMS Settings I cook with. I increase my limits up to 600k send and 1Mb receive. SampleMMSC is just the name I used, it could be anything.
You can check this:
Code:
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\MMSCSetting\[b]SampleMMSC[/b]]
"waptype"=dword:00000001
"GatewayPort"=dword:00000050
"MmscURI"="http://mmsc.cingular.com"
"Gateway"="wireless.cingular.com"
"Name"="AT&T MMS"
[b]"WAP1RecvDefaultSize"=dword:000FA000
"WAP2RecvDefaultSize"=dword:000FA000[/b]
"SendDefault"=dword:00096000
"ConnectionVia"="{B2AD7D1D-2C4B-494B-B324-42EEC882B71B}"
[b]"WAP1SendDefaultSize"=dword:00096000
"WAP2SendDefaultSize"=dword:00096000[/b]
"ISP"="SampleMMSC"
Looking at this code, WAP1RecvDefaultSize = FA000 (1024kb or 1mb)
WAP1SendDefaultSize = 96000 (600kb)
But I think the reasoning is that most phones don't have a high resolution. So full screen on my wife's phone is 240x320... plus most phones compress the image down for sending via MMS to usually 120x160... which as you can imagine would look tiny on our 480x800 screens. Just depends on the phone.

my registry entry is correct:
"WAP1RecvDefaultSize"=dword:000FA000
"WAP2RecvDefaultSize"=dword:000FA000
The problem for me is definitely with my carrier - o2.
As my TD2 is not from o2 and they don't actually sell this phone, they don't recognise the user-agent in WspHeader. Because they don't recognise it, they then compress the mms image right down to between 3 and 6k. I can send full size mms and they are received by others fine but anything I receive is compressed. I have sent myself mms - it leaves at around 250k but arrives at 6k.
I have found posts about changing the user-agent and profile in WspHeader to a device that o2 recognises but none of these changes have worked for me.
I'd be interested to see what anyone else on o2 (uk) that can receive mms of 300k, has for their user-agent and profile in the registry:
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader\User-Agent]
and
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader\Profile]

cokeyblokey said:
The problem for me is definitely with my carrier - o2.
As my TD2 is not from o2 and they don't actually sell this phone, they don't recognise the user-agent in WspHeader. Because they don't recognise it, they then compress the mms image right down to between 3 and 6k. I can send full size mms and they are received by others fine but anything I receive is compressed. I have sent myself mms - it leaves at around 250k but arrives at 6k.
I have found posts about changing the user-agent and profile in WspHeader to a device that o2 recognises but none of these changes have worked for me.
I'd be interested to see what anyone else on o2 (uk) that can receive mms of 300k, has for their user-agent and profile in the registry:
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader\User-Agent]
and
[HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA\Config\mm1\WspHeader\Profile]
Click to expand...
Click to collapse
Has been driving me nuts for weeks as well However I was sure that when I first got the phone (pre flashing cooked ROMS) that I received MMS @ full size.
So today, in desperation I flashed the official Topaz 6.5 ROM. Sent a test MMS to myself and hey presto it came back full size YAY.
Looking at the registry for Arcsoft/Arcsoft MMS UA/Config there are a hell of a lot more subkeys and values than was in the cooked ROM, so next step is to copy everything down reflash the cooked ROM and add all the subkeys and values. I may be some time LOL

I have exactly the same problem, flashed mine with 'Duttys Topaz WM6.5 Leo R7 WWE' rom, now I recieve tiny MMS pictures. Also on O2 (UK) with non branded phone.
Druboo please can you post what changes you have to make to correct this problem, I know it may take a while to sort but it will help all of here.
Thanks

Can now receive full size MMS on Duttys ROM
First things first, I use CERegEditor as a pc based regedit for my TD2 - So not sure if it will work with other regeditors. However, if Druboo's using it, it must have been free
With the stock 6.5 ROM still on the phone I made a backup of the Registry saved as Stock ROM.
Re-flashed Dutty's ROM and made a backup of it's Registry Saved as Dutty's ROM.
Then did a compare between Stock ROM and Dutty's ROM just for HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA which resulted in 12 subkeys and 199 values extra in the Stock Rom. Saved the differences as Differences.
Imported Differences onto Dutty's ROM. Test MMS and hot to trot
Hope it works for you too
ATB

Druboo said:
Can now receive full size MMS on Duttys ROM
First things first, I use CERegEditor as a pc based regedit for my TD2 - So not sure if it will work with other regeditors. However, if Druboo's using it, it must have been free
With the stock 6.5 ROM still on the phone I made a backup of the Registry saved as Stock ROM.
Re-flashed Dutty's ROM and made a backup of it's Registry Saved as Dutty's ROM.
Then did a compare between Stock ROM and Dutty's ROM just for HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA which resulted in 12 subkeys and 199 values extra in the Stock Rom. Saved the differences as Differences.
Imported Differences onto Dutty's ROM. Test MMS and hot to trot
Hope it works for you too
ATB
Click to expand...
Click to collapse
excellent work, if i have (alot of) time i will add the reg entries seperatly in an attempt to find the one responsible for the problem

Thank you, I will give it a try.

Druboo said:
Can now receive full size MMS on Duttys ROM
First things first, I use CERegEditor as a pc based regedit for my TD2 - So not sure if it will work with other regeditors. However, if Druboo's using it, it must have been free
With the stock 6.5 ROM still on the phone I made a backup of the Registry saved as Stock ROM.
Re-flashed Dutty's ROM and made a backup of it's Registry Saved as Dutty's ROM.
Then did a compare between Stock ROM and Dutty's ROM just for HKEY_LOCAL_MACHINE\Software\Arcsoft\ArcSoft MMS UA which resulted in 12 subkeys and 199 values extra in the Stock Rom. Saved the differences as Differences.
Imported Differences onto Dutty's ROM. Test MMS and hot to trot
Hope it works for you too
ATB
Click to expand...
Click to collapse
Is this cabbed up somewhere? I have no idea how to implement it but I am having this problem.

New Place to Edit
Well my previous fix no longer works on Sense 2.5 ROMS
It appears that the mms servers are now given the phone information from a different location. The good news for us poor belligered O2 UK users is that the Topaz is finally recognised in the Server database.
Point your reg editors to HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\SP
Make UAProfile="http://www.htcmms.com.tw/gen/HTC_Touch_Diamond2_T5353-1.0.xml"
& UserAgent="HTC_Touch_Diamond2_T5353/arcsoft-mmsua-5.2.0.xx" and you should be back in business.

Druboo said:
Well my previous fix no longer works on Sense 2.5 ROMS
It appears that the mms servers are now given the phone information from a different location. The good news for us poor belligered O2 UK users is that the Topaz is finally recognised in the Server database.
Point your reg editors to HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\SP
Make UAProfile="http://www.htcmms.com.tw/gen/HTC_Touch_Diamond2_T5353-1.0.xml"
& UserAgent="HTC_Touch_Diamond2_T5353/arcsoft-mmsua-5.2.0.xx" and you should be back in business.
Click to expand...
Click to collapse
Thanks, just found this thread and this worked for me