Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I played with the settings for almost hours myself last night](*,). and still no dice. It looks like for sprint there is something missing that I cann't find. I also read alot of the MMS Fix threads. and it seems like its the same problem as before.
Just outta curiosity i would love to know what u VZW users' setting are? But Im gonna give up, but also keep an eye in it.
Thanks for your imput!:headbang:

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

To the best of my knowledge, Verizon could send and receive on earlier 1.5 versions. Sprint could only receive. I can only confirm with 1.8, Sprint can still be configured to receive-only, but sending doesn't work.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Ok. Thanks for the input. Hopefully it can be resovled somehow.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Yes, I could send & receive in full on 1.5 using the server settings below. I'm using them now: I can send (and see the attachment) AND receive (but not download the attatchment).

Server Name: Whatever
IP Address: Blank
Port Number: 80
Server Address: http://mms.vtext.com/servlets/MMS?X-VZW-MDN=YourPhone#
Connect via: Verizon Wireless (other options are "My Work Network", "My ISP", and "Work")
Send Limit: 1024 KB
WAP version: None

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I'm in the same boat as you. This really sucks. I can't figure out how to get the MMS to download for the life of me! Are you still on Mighty ROM? I am trying on Energy.RHODCDMA.21905.Sense2.5.GTX.Themed.Jun.12. Anyone had any success with it? TIA

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

oi... this one is literally giving me a headache... im using the same server settings as posted above for VZW. same thing. can send and see attachment. can receive, but cant see attachment. i tried installing arcsoft over top of this and i can see my pics that way. but not in htc messaging... gotta go thru the back door in start menu to get to wm messaging... does anyone know where arcsoft AND htc messaging save mms attachments?

EDIT*i had it working on a previous mightyROM... does anyone remember what it was? was it Impact? if so i may still have that ROM...maybe ill flash it and dig thru the registry...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I am on sprint, but i am did have it working w/ arcsoft in impact and full force.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

so is this ONLY for sense 2.5? On stock Verizon wm6.5 rom with sense 2.1 but would love the speedier HTC Messaging client.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

yes this is 2.5 only.

EDIT* just saw youre on verizon... theres a new MR2 upgrade (official stock ROM) available as of today. im trying to find out which Sense build it has (2.1 or 2.5)

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I'm on Vin's Plutonium (06/14) right now. The last MightyRom it worked on for me was FullForce back in March I believe.

**EDIT** I'm trippin! LOL! I just checked old posts. It was MightyROM Impact_3 12/23 and Arcsoft 5.0.90.127 wayyyy back in December!

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

thanks and thanked! i think i have a copy of Impact, so im gonna flash it and look in the registry for any clues...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I hate to flop on ya again. But, I may have type 12/23 in that old post & meant to type 12/28! I can't find a 12/23 Impact release in my archives. I DO have Impact 12/28, Impact 12/28_2, & War 12/28_3 . . . So, I think that's it. Let me know if you need it.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

PM'd you...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

ok... im about tapped on figuring this one out... closest ive been abl to get is with arcsoft receiving the mms instead of htc... if i can get ahold of a copy of the old IMPACT ROM, i may be able to find the differences in the registry and get it working.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Check you PM . . .

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Thank you!!! Impact registry here i come...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Good luck!

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I got bad news... I fjust flashed to the IMPACT ROM that has the htc messaging cooked in. The server settings that worked before, don't work anymore... Im getting the same issue: Can send, but cant receive...

Snaps...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I'm going to chime in on this, because this hs been a personal project for me with HTC Messaging. And let me explain a little about secure box and the issue with MMS. First about secure box, I originally found how to activate secure box and posted the release before G-ThGraf did. I have activated Secure Box on every version on the TP2 based from the HD2 1.72 rom. There is ONLY 2 registry entries needed to make it work. http://forum.xda-developers.com/show...ght=Angeldeath

Read that post and it will explain it to you. Now just so everyone knows This will most likely not work with arcsoft messaging installed. Also the likely hood of this working on a customized cooked rom is 50/50 mainly the reason why is there are too many settings that are being altered. The HTCMessaging_Client_1_8_20152127_00 version secure box works on GSM (Dont know about CDMA) on a stock 2.07 TP2 rom / Build 21887 Min. The Messaging client believe it or not will only work with some roms and not others, what those are I dont know, I do know that it seems the newest HTCMessaging_Client_1_8_20161228_00 will not work correctly with the OS build 21887, so it leads me to believe its Build dependent.

As for the MMS send and recieve, the settings are based by another package aside from the htc messaging client.

Also there seems to be a bug in the TP2 which I dont know if it applies to anyone, or if anyone knows about it, but if you have WIFI on, and in the advanced connection setting you have the first one set to anything other then media net, mms will fail to send and possibly recieve. This bug did not exist in the Fuze nor the Tilt phones, but does exist in the TP2.

If anyone who hasnt gotten Secure box to work, can try mine. But make sure your os build is 21887. Also my version only has Secure Box activated and nothing fancy added. Also, mine is actually one version below the 1.8, the reason is there is a secure box bug I found, but still dont know if its OS related since I am having trouble updating my MSXIPKernel :(

Any questions feel free.

Also here a bonus for those who dont know it, here is the registry setting to activate MMS preview auto rotate screen settings:

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging]
"PlayerType"=dword:00000001
"PlayerFlags"=dword:00000001
"PlayerOrientation"=dword:00000002 (This Entry Doesnt seem to exist in current versions so add it)

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Thanks and thanked. I do remember seeing something about yours before this new G-thgraf's. I have a question for you. with your 2 reg edits can I get the secure box to work? I am running Might Rom Full Force? I like the idea of the secure box. and would love to get this added into my set up now.
Thanks for all you hard work!=D>

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

bdurst08,

Unfortunately being unfamilar with Might Roms, I would be wrong to tell you that it would, there are alot of factors that play into this, such as:

1) What OS Build is in your phone?
2) What HTC Messaging Client Version/Build are you looking at?
3) CDMA or GSM version of the phone.
4) Is Arcsoft/HTC Messaging 2.1 (Older software) installed?
5) What has been altered in the registry?

My best answer to you is, make a backup of your phone or the one file your replacing the MUI and make the changes copy the MUI file, reset the phone and see.

And aestivalisakito just confirmed my thoughts and previous statement without even knowing it! HTC Messaging Client is OS dependent to a point. Quote:

"Latest Tp2 EXT Packages! Updated 6/15/10 - Also this has been adjusted to work with 21XXX winmo, if you have com 3 goto manila core app.reg and change "isCom3Project" and "Roamingicon" to DWORD:00000001. Remember to configure for your provider!

Link: forum.xda-developers.com/showthread.php?t=700798

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

txting worked fine for me and so did the secure box, but sending pics didnt at all. My phone also got jacked up with verizon data connections, meaning NO data connections going in or out aside from simple txt msgs. this was tested on 2012 sense. Going to try newer sense & see if this is different.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Just flashed it to a refurb unit and its Sense 2.5 (213227).

Only way i will try this is if I can send and receive MMS.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

You might be waiting a while than :(

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

thanks and thanked for your hard work and sharing it! i think the biggest reason ppl here are trying to use the 1.8 client (me included) is for 2 reasons:

1) eliminate lag in sms client
2) have MMS working properly in htc messaging

the secure box likely takes 3rd place to those items. the Full Force ROM that we're trying to use this on is a 6.5.X build (dont have the exact build number), so im not sure if thats affecting the MMS or not. whats really throwing me off, is that i flashed back to a 6.5.x ROM with an older build of htc messaging (1.5 i think). i used this ROM for a few months in january/february, and i had MMS working perfectly WITHOUT arcsoft... now when i flashed back to it, MMS doesnt work, even with the exact same server settings i used before...

so idk if verizons settings have changed (unlikely) or if when i flashed, something got stuck in the OS from my previous ROM. i might try again and run a task29 first...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

1) 5.2.23563(23565.5.5.0)
2) i think my HTC messaging client is 1.5
3) CDMA
4) yeah I do have arcsoft installed
5) I am not sure excatly what has been altered in the registry. I dont manually make reg edit. But I am pretty sure that there are some cabs that have made reg edits.

Thanks for your help!!=D>

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

1) Not sure it will work, I am fixing my build issues with my kitchen (GSM). Once I figure it out I'll try the build.
2)1.5 what the rest? Build what?
3) Completely Unfamilar with CDMA
4) Might cause you an issue.
5) Specifically to HTC messaging, arcsoft, and Jataayu.

Anyone who has MMS working (Doesnt matter HTC or arcsoft) send and recieve, if you would be so kind to dump your registry (I use CDRegEdtior) and up it to this post, I can maybe help find a solution. 90% of everything is in the registry.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

did that you install the messaging client yourself or was it already made in that rom

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Here you go!

Arcsoft.reg
Jataayu.reg

The Jataayu.reg file is a copy of my Jataayu key with it working to SEND mms only. When an MMS comes, in, I get a "Downloading" icon, then a "New Message" notification. I then go into the conversation in HTC messaging. The preview is not shown. I select the message, and it opens the message details, where I then have the option to "Download" the attachment. I attempt to download it, only to get a notification stating "Unable to download message from <SENDER>"

Pleae note that there are two string values within the Jataayu key (under Profiles, "MMSCURL"), which contains the server address (http://mms.vtext.com/srevlets/mms?X-VZW-MDN=1234567890) for Verizon MMS. The last 10 digits of the string are the users phone number, so I edited them to "124567890".

The Arcsoft.reg file is a copy of the Arcsoft key with it being able to SEND AND RECEIVE MMS. The server address in the Arcsoft settings is set to http://mms.vtext.com/servlets/mms. If i remember correctly, the HTC server setting has the additional characters asthe HTC messenging client would not supply all of the infomation (user phone number) unless it was part of the server string.

Hopefully you can help us get the MMS receving properly in HTC messaging! Thank you for your efforts and let me know if I can help further!!!

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I'd like to jump in and offer my support for getting MMS to recieve as well! I've got a VZW TP2 running the latest NRGZ Dinik Cookie ROM "Energy.RHODCDMA.23569.Sense2.5.Cookie.DinikGlass. Jun.23" I gave up on HTC Messages when it stopped working back Febuaryish? Usually everytime I've seen a new version of HTC Messages comes out I've popped it on to see if it works to no avail. Currently I can send MMS's and get notified that I have one to be downloaded but not download. I can happily provide registry key details or try new edits if anyone has ideas, reflashing my phone if I mess up is not a problem. I've been trying to find an NRGZ rom from earlier this year when he still cooked in HTC Messages and it worked, so Januaryish? If anyone has one that would be good to inspect.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

def appreciate your willingness to help! in regards to flashing to the old EnergyROM, i doubt it will work. i did that with an old MightyROM. it has htc messaging cooked in and i used to have it working for MMS send ANE receive. but now it wont receive, even with the same server settings i used before. (januaryish also). im now leaning towards something in verizons server thats changed to be a little more sensitive... even the new mr2 update is having mms problems...

ive got a couple ideas but im pretty swamped right now. maybe next week ill be able to get back into this...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

yes it works for me on mightyROM FF but ill have to say that its not worth it if you have a lot of text messages because not only is the lag worse but it also seemed to have broke the threaded messaging in the standard wm texting and it also freezes on restoring message. how do i uninstall this without having to do a hard reset? i have another block of work days coming up tomorrow so i won't have time to restore from a hard reset

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

SPB backup FTW......... thats all I got to say about that.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

do you have MMS working WITHOUT Arcsoft?

and you should be able to just uninstall it via "Remove Programs"

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

i tried that already and it said that it couldn't be removed,i had sense disabled at the time

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I am on Sprint and would love to know what to do to get mms working do i need arcsoft cooked in or leave it out.

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

I posted what you need in the reg in MM thread....but mms is a fail every time...I gave up...I cannnot remember where I posted it but it was at least a week ago...so you will have to search..sorry....I will also take a quick gander...

here I found it....

http://forum.ppcgeeks.com/showpost.p...postcount=8523

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Hey boys wanted to chime in. I doug deep on this and it is pretty much a no go. I can provide the following reg settings but I think the issue has to do with the phone being CDMA.

REGEDIT4

[HKEY_LOCAL_MACHINE\SOFTWARE\Jataayu\Messaging]
"MessageServiceComponents"=dword:000005FE
"sms"=hex:00, 00
"LogBuffer"=dword:00000000
"DisableSMSSuccess"=dword:00000001
"MaxRecipients"=dword:00000064
"MaxMMSRecipients"=dword:0000000A
"MaxQuickText"=dword:0000001E
"LogLevel"=dword:00000000
"ImageFolder"="\\windows\\"
"LogTime"=dword:00000000
"Max7BitText"=dword:000008F7
"MaxUnicodeText"=dword:000003ED
"HTCContactPicker"=dword:00000001
"VideoMode"=dword:00000001
"TrashFolderSupported"=dword:00000001
"GSensor"=dword:00000001
"DownloadLimitFlag"=dword:00000001
"DraftsSupported"=dword:00000001
"EnableContactBtn"=dword:00000001
"MaxMediaSize"=dword:0000012C
"EnableOmaCP"=dword:00000001
"CheckUnreadCountAtStartup"=dword:00000003
"PlayerType"=dword:00000001
"MSFTUnreadCountFlag"=dword:00000003
"PlayerFlags"=dword:00000001
"DeleteMessagePermanently"=dword:00000000
"PlayerOrientation"=dword:00000002
"StaticVideo"=dword:00000001
"SkipNumberPrefixCheck2"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging]
"HTCDevice"=dword:00000001
"EmailClassName"="IPM.Note"
"MMSClassName"="IPM.MMS"
"SMSClassName"="IPM.SMStext"
"VoiceMailClassName"="IPM.VoiceMail"
"ComposeFlag"=dword:00000000
"CameraThreshold"=dword:0000001E
"PhotoThreshold"=dword:00000005
"EnableKeyEvt"=dword:00000001
"DisableCacheWhenLengthierMessage"=dword:00000 001

[HKEY_CLASSES_ROOT\CLSID\{B7D01B9D-ACD8-48bf-AD4C-597521CB4221}\InprocServer32]
@="messagingnotification.dll"

[HKEY_CLASSES_ROOT\CLSID\{A9879FBF-5FA9-48dd-94EC-3AE3D1F2D8F9}\InprocServer32]
@="messagingnotification.dll"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByCTAndAppId\application/vnd.wap.mms-message;]
@="0068C573279EC901"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByGenericId\0068C573279EC901]
"QueueId"=dword:00000001
"Trust"=dword:00000002
"RefCount"=dword:00000001
"Params"="mms"
"Path"="\\Windows\\PushClient.exe"
"AppId"=""
"ContentTypes"="application/vnd.wap.mms-message"
"GenId"="0068C573279EC901"

[HKEY_LOCAL_MACHINE\Services\MSG]
"Dll"="MessagingService.dll"
"Keep"=dword:00000001
"Index"=dword:00000000
"Order"=dword:00000009
"FriendlyName"="Message Service"
"Prefix"="MSG"
"MaxPhoneLength"=dword:00000014

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\DlgH elper]
"DlgHelperExe"="\\windows\\DlgHelper.exe"

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MsgF lags]
"CDMA"=" - CDMA"
"CDMASIM"=" - UIM"
"GSM"=" - GSM"
"GSMSIM"=" - SIM"
"DefaultLine"="GSM"

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Imag eResizer]
"CameraCapturedRresolution"=dword:00000002
"PhotoResolution"=dword:00000007

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Netw ork]
"SMSPreferredNetwork"=dword:00000002
"MMSPreferredNetwork"=dword:00000002

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MMS]
"Duration1"=dword:00000001
"Duration2"=dword:00000003
"Duration3"=dword:00000005
"Duration4"=dword:00000007
"Duration5"=dword:0000000A
"EnableHTCPicturePicker"=dword:00000001
"RecvTimeFlag"=dword:00000001
"DeliveryReport"=dword:00000000
"AllowDeliveryReport"=dword:00000000
"ValidityPeriod"=dword:00000000
"SendRetryInterval"="5 60 60 60"
"Priority"=dword:00000001
"MaxSlides"=dword:00000014
"SubjectMaxCharacters"=dword:00000028
"StorageMinMemory"=dword:00000400
"SaveListWhiteList"="VOLUMECONTROL"
"DefaultSlideDuration"=dword:00000005
"DisablePowerMgr"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Rich Edit]
"TextSelSearchArea"=dword:00000096

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM\AudioV ideoAmbiguousExtensions\.3g2]
"AudioMimeType"="audio/3gp"
"VideoMimeType"="video/3g2"

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM\AudioV ideoAmbiguousExtensions\.3gp]
"AudioMimeType"="audio/3gp"
"VideoMimeType"="video/3gpp"

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM\AudioV ideoAmbiguousExtensions\.mp4]
"AudioMimeType"="audio/mp4"
"VideoMimeType"="video/mp4"

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM\Conten t-Types]
".3gp"="video/3gpp"
".3g2"="video/3gpp2"
".vcs"="text/x-vcalendar"
".dcf"="application/vnd.oma.drm.content"
".wbmp"="image/vnd.wap.wbmp"
".m4a"="audio/m4a"
".qcp"="audio/qcp"
".wav"="audio/wav"
".midi"="audio/midi"
".wma"="audio/wma"
".aac"="audio/aac"
".awb"="audio/amr-wb"
".gif"="image/gif"
".png"="image/png"
".jpg"="image/jpeg"

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM\File Extensions\audio/mpeg]
"DRMExtension"=".mp3d"

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MMS\ OEM]
"SendPacketBufSize"=dword:00002000

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MMS\ Profile\GSM]
"MMSCURL"="http://mms.emome.net:8002"
"IPAddress"="10.1.1.1"
"ConnectionType"=dword:00000002
"Port"=dword:00001F90
"GUID"="{BFF8E209-7DDA-4BD6-995E-E44CE5462DB3}"
"SendLimit"=dword:0000012C
"Lock"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MsgC ount]
@=""

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Noti fications]
"Path"="\\Windows\\"
"NotificationRemoverInfo"="{A877D65B-239C-47a7-9304-0D347F580408}|256;{3EDF3B32-EC31-44ba-BD5E-1C2495E42E07}|256"

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\SMS]
"DeliveryReport"=dword:00000000
"ValidityPeriod"=dword:00000000
"RilSendWaitTimeout"=dword:0000012C
"SendRetryInterval"="5 60 60 60"
"Priority"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\WAPP ush]
"SLInvokeBrowser"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\JSR]
"Enable"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\SP]
"LogBuffer"=dword:00000000
"Logging"=dword:00000000
"RRPreferredClass"=dword:00000001
"UAProfile"="http://www.htcmms.com.tw/gen/Qilin-1.0.xml"
"UserAgent"="dopodT8388/1.0 WindowsMobile/6.5 CEOS/5.2 release/5.0 IE/6.0 WAP2.0 Profile/MIDP2.0 Configuration/CLDC1.1"
"MMSRetrievalRetryCount"=dword:00000003

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\TextS election]
"EnableTextSelection"=dword:00000001
"TextSel_ScrollBoundary"=dword:00000038
"DebounceCount"=dword:00000001
"TextSel_ScrollElapseTime"=dword:00000064
"TextSel_HideAnchor"=dword:0000003C

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Menu]
"SecureMode"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Fonts]
"DrawWidth1"=dword:00000176
"DrawWidth2"=dword:000002B6
"DrawWidthCounts"=dword:00000002
"DrawFontCounts"=dword:00000005
"FontScale"=dword:00000002

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Misce llaneous]
"TextSize"=dword:00000002

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Harve y]
"ShowMaxDeletedItem"=dword:000003E8
"FromMessageClient"=dword:00000000
"Sender"=""

[HKEY_LOCAL_MACHINE\Software\HTC\HTCPhotoPicker\HTC Messaging_Client\Setting]
"virtual_content_count"=dword:00000002
"Enable_DRM"=dword:00000001
"DRM_Filter"=dword:00000100
"Enable_GSensor_Rotate"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCPhotoPicker\HTC Messaging_Client\Setting\VirtualContent_1]
"ResolutionWidth"=dword:000001E0
"ResolutionHeight"=dword:00000280
"StillQuality"=dword:00000000
"Mode"=dword:00000000
"Type"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCPhotoPicker\HTC Messaging_Client\Setting\VirtualContent_2]
"ResolutionWidth"=dword:000000B0
"ResolutionHeight"=dword:00000090
"StillQuality"=dword:00000000
"Mode"=dword:00000002
"Type"=dword:00000001
"VideoTypes"=dword:00000002

[HKEY_CURRENT_USER\Software\HTC\NOTIFICATIONMANAGER \{A877D65B-239C-47a7-9304-0D347F580408}]
"ProcessPath"="\\Windows\\Messaging_Client.exe "
"Cmd"="1001 999"
"Dismissable"=dword:00000001
"Img"="\\windows\\notifications_icon_Messages. png"

[HKEY_CURRENT_USER\Software\HTC\NOTIFICATIONMANAGER \{3EDF3B32-EC31-44ba-BD5E-1C2495E42E07}]
"ProcessPath"="\\Windows\\Messaging_Client.exe "
"Cmd"="1001 999"
"Dismissable"=dword:00000001
"Img"="\\windows\\notifications_icon_Messages. png"

[HKEY_CURRENT_USER\Software\HTC\NOTIFICATIONMANAGER \{B7D01B9D-ACD8-48bf-AD4C-597521CB4221}]
"ProcessPath"=""
"Cmd"=""
"Dismissable"=dword:00000001
"Img"="\\windows\\notifications_icon_Messages. png"

[HKEY_CURRENT_USER\Software\HTC\NOTIFICATIONMANAGER \{B7D01B9D-ACD8-48bf-AD4C-597521CB4220}]
"ProcessPath"=""
"Cmd"=""
"Dismissable"=dword:00000001
"Img"="\\windows\\notifications_icon_Messages. png"

[HKEY_CURRENT_USER\Software\HTC\NOTIFICATIONMANAGER \{D95268B4-67F7-4cb1-8DD5-B2217B73F9F9}]
"ProcessPath"=""
"Cmd"=""
"Dismissable"=dword:00000001
"Img"="\\windows\\notifications_icon_Messages. png"

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\OEM]
"RetryAttempts"=dword:00000004
"IsDataDisconnect"=dword:00000001
"DataConnPriority"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\USER]
"AnonymousMessage"=dword:00000000
"OutgoingMessageSize"=dword:0004B000
"ReadReportOptions"=dword:00000003
"VideoFileRatio"=dword:00000050
"CreationMode"=dword:00000003
"HideSender"=dword:00000000
"IncomingMessageSize"=dword:0004B000
"OutgoingMessageClass"=dword:00000001
"DeferredTime"=dword:00000000
"ReadReport"=dword:00000000
"Advertisement"=dword:00000000
"Deny_All"=dword:00000000
"MessageClass"=dword:0000000F
"Retrieval"=dword:00000003
"RoamingReception"=dword:00000002
"HomeReception"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Setti ng]
"UI_IncomingMessageSize"="100 KB;100;200 KB;200;300 KB;300;600 KB;600"
"SendRetryIntervalTemp"="5 60 60 60 60 60 60 60 60 60"
"SignatureMaxSize"=dword:00000032
"SignaturePreInsertLine"=dword:00000003
"EnableSignature"=dword:00000001
"EnableAllowDeliveryReport"=dword:00000001
"EnableHtcRichEdit"=dword:00000001
"EnableAutoUppercast"=dword:00000001
"EnableVTCallMenuOption"=dword:00000001
"ValidityPeriodList_SMS"="MAX;h:1;h:12;d:1;d:2 "
"ValidityPeriodList_MMS"="MAX;h:1;h:12;d:1;d:2 "
"MessageSizeList"="KB:100;KB:200;KB:300;KB:600;KB: 1024"
"ShowSMSForwordTypeUI"=dword:00000001
"ShowMMSForwordTypeUI"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Sett ing]
"SMSForwardStringType"=dword:00000000
"MMSForwardStringType"=dword:00000000

[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\Profiles]
"ActiveProfileCDMA"="Sprint"
"ActiveProfileGSM"="Sprint"
"DefaultNetwork"=dword:00000000
"DefaultSendSize"=dword:00000400
"EnablePortNumAutoSwitch"=dword:00000001
"DefaultWAP1XPort"=dword:000023F1
"DefaultWAP20Port"=dword:00000050
[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MMS\ Profile\CDMA]
"Name"="Sprint"
"SendLimit"=dword:00000400
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\MMS\ Profile\GSM]
"Name"="Sprint"
"SendLimit"=dword:00000400
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\Profiles\S print]
"Name"="Sprint"
"SendLimit"=dword:00000400
"GUID"="{F079757F-9357-4000-8305-9CA6B9B6CAEC}"
"IPAddress"=""
"MMSCURL"="http://mms.sprintpcs.com/servlets/mms"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\Profiles\T elus]
"Name"="Telus"
"SendLimit"=dword:00000400
"GUID"="{18AD9FBD-F716-ACB6-FD8A-1965DB95B814}"
"IPAddress"="216.198.139.113"
"MMSCURL"="http://mmsfeplb01.int.eng.telusmobility.com:8088/mms"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\Profiles\U S Cellular]
"Name"="US Cellular"
"SendLimit"=dword:00000400
"GUID"="{ADB0B001-10B5-3F39-27C6-9742E785FCD4}"
"IPAddress"=""
"MMSCURL"="http://mmsc1.uscc.net/mmsc/MMS"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\MMS\Profiles\V erizon]
"Name"="Verizon"
"SendLimit"=dword:00000400
"GUID"="{0DAEA92E-2917-4c6c-9E23-F2BCAA13DA07}"
"IPAddress"=""
"MMSCURL"="http://mms.vtext.com/servlets/mms"
"ConnectionType"=dword:00000000
"Port"=dword:00000050
"Lock"=dword:00000000
[HKEY_LOCAL_MACHINE\Software\Jataayu\Messaging\Pred efinedPort]
"Sprint MMS"=dword:00000050
"Telus MMS"=dword:00000050
"US Cellular MMS"=dword:00000050
"Verizon MMS"=dword:00000050

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Custo mization]
"TouchRange"=dword:0000003A
"ClearNotifyinAllMessage"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\Compo se]
"ExecPathName"="\\windows\\Messaging_Client.ex e"

[HKEY_CLASSES_ROOT\CLSID\{1037DBE3-7EEC-4b70-B5F4-5D89F1D625E4}]
"SBPassword"=hex:79, 7B

[HKEY_CLASSES_ROOT\CLSID\{820D9EA2-11EC-4eb0-A71B-49F50DB4F28E}]
@="HtcMailAccount"

[HKEY_CLASSES_ROOT\CLSID\{820D9EA2-11EC-4eb0-A71B-49F50DB4F28E}\InprocServer32]
@="HtcMailAccount.dll"

[HKEY_LOCAL_MACHINE\Software\HTC\Camera\Video]
"EnableMMS"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\HTCMessaging\EditI temParameter]
"ToolBarMode"=dword:00000001
"HandWriting"=dword:00000001

[HKEY_CLASSES_ROOT\CLSID\{D9A9C70F-A8A9-4b26-B972-C3A514BBB815}]
@="HthMmsContactMenuInfo"

[HKEY_CLASSES_ROOT\CLSID\{D9A9C70F-A8A9-4b26-B972-C3A514BBB815}\InprocServer32]
@="GetHtcMmsLimitDll.dll"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Contacts\Main_Menu\{D9A9C70F-A8A9-4b26-B972-C3A514BBB815}]
@="Send contact info"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Contacts\Main_ContextMenu\{D9A9C 70F-A8A9-4b26-B972-C3A514BBB815}]
@="Send contact info"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Contacts\Summary_Tools\{D9A9C70F-A8A9-4b26-B972-C3A514BBB815}]
@="Send contact info"

[HKEY_CLASSES_ROOT\CLSID\{EF375CB5-8A6C-4a90-91EB-D9502EABD6F5}]
@="HthMmsCalendarMenuInfo"

[HKEY_CLASSES_ROOT\CLSID\{EF375CB5-8A6C-4a90-91EB-D9502EABD6F5}\InprocServer32]
@="GetHtcMmsLimitDll.dll"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Calendar\Main_Menu\{EF375CB5-8A6C-4a90-91EB-D9502EABD6F5}]
@="Send calendar info"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Calendar\Main_ContextMenu\{EF375 CB5-8A6C-4a90-91EB-D9502EABD6F5}]
@="Send calendar info"

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Extens ions\ContextMenus\Calendar\Summary_Tools\{EF375CB5-8A6C-4a90-91EB-D9502EABD6F5}]
@="Send calendar info"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByCTAndAppId\application/vnd.wap.sic;]
@="00CD6EA703E9C901"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByCTAndAppId\application/vnd.wap.slc;]
@="0027D1A903E9C901"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByCTAndAppId\text/vnd.wap.si;]
@="809038A903E9C901"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByCTAndAppId\text/vnd.wap.sl;]
@="005402AB03E9C901"

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByGenericId\0027D1A903E9C901]
"AppId"=""
"ContentTypes"="application/vnd.wap.slc"
"GenId"="0027D1A903E9C901"
"Params"="sl"
"Path"="\\Windows\\PushClient.exe"
"QueueId"=dword:00000005
"RefCount"=dword:00000001
"Trust"=dword:00000002

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByGenericId\005402AB03E9C901]
"AppId"=""
"ContentTypes"="text/vnd.wap.sl"
"GenId"="005402AB03E9C901"
"Params"="sltext"
"Path"="\\Windows\\PushClient.exe"
"QueueId"=dword:00000004
"RefCount"=dword:00000001
"Trust"=dword:00000002

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByGenericId\00CD6EA703E9C901]
"AppId"=""
"ContentTypes"="application/vnd.wap.sic"
"GenId"="00CD6EA703E9C901"
"Params"="si"
"Path"="\\Windows\\PushClient.exe"
"QueueId"=dword:00000003
"RefCount"=dword:00000001
"Trust"=dword:00000002

[HKEY_LOCAL_MACHINE\Security\PushRouter\Registratio ns\ByGenericId\809038A903E9C901]
"AppId"=""
"ContentTypes"="text/vnd.wap.si"
"GenId"="809038A903E9C901"
"Params"="sitext"
"Path"="\\Windows\\PushClient.exe"
"QueueId"=dword:00000002
"RefCount"=dword:00000001
"Trust"=dword:00000002

[HKEY_LOCAL_MACHINE\Software\Microsoft\Shell\Event\ Network\WDP\9204\pushclient]
"9204"=dword:00000000
"Class"=""
"Command"="pushclient.exe wap 9204"

[HKEY_LOCAL_MACHINE\Software\HTC\VolumeOverlay\Inho useAPClass\HTCMessaging_Client]
"ClassName"="MESSAGING_CLIENT"

[HKEY_LOCAL_MACHINE\Software\HTC\VolumeOverlay\Inho useEnable2ndUI\MESSAGING_CLIENT]
"Enable2ndOverlay"=dword:00000000
"OwnerWindowEnable"=dword:00000001

[HKEY_LOCAL_MACHINE\Software\HTC\VolumeOverlay\Inho useEnable2ndUI\Manila]
"OwnerWindowEnable"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\MASD]
"HTCMessaging_Client"="1_8_20152127_00"

[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\Build_Order]
"HTCMessaging_Client"="2"

[HKEY_LOCAL_MACHINE\SOFTWARE\OEM\PKG]
"shadow"="1"

Re: Will The New HTC Messenging Client v1.8 Work On TP2?
 

Holy wow... And I thought I had spent a lot of time in the registry trying to figure this out...

Re: Will The New HTC Messenging Client v1.8 Work On TP2?