yashsingh1/xdaforums huggingface dataset:
[Touch Pro2, Tilt 2 Windows Mobile General] iboj007:
There were many complaints of this on the MyPhone forums and last I checked, Microsoft said that this was a known issue based on when the device was inserting a given message into the message store.

They said that they were working on it.
[Touch Pro2, Tilt 2 Windows Mobile General] cincy1020:
Hi:

Thanks so much for your replies :)

So, after restoring with Jeyo, can I then turn threading back on? I can't live without threaded messages lol.

Thanks again!
[Touch Pro2, Tilt 2 Windows Mobile General] das-man:
Oh I am sorry I forgot to mention that. After you backup your messages without the threading, you should hard reset your phone. Then just follow the steps like I mentioned. So yes, your threading should be enabled again by default so you don't have to worry about that on your part.

BTW, please don't forget to keep copies of your old backups (any backup files you had before I made my suggestions).
[Touch Pro2, Tilt 2 Windows Mobile General] cincy1020:
Hi:

Well when I disabled threaded messaging for some reason it caused my phone to become unresponsive. SMS tab was no longer loading in TF3D, and all of TF3D was basically unusable.

I had to hard reset, and restore with Sprite.

So, now I am back to the messed up SMSes.
[Touch Pro2, Tilt 2 Windows Mobile General] das-man:
Sorry to hear that. Yeah I was lucky enough to still have my old phone to mess around with so I am not sure how get your SMS in order. If you still feel like messing around I still have a few ideas in mind lol.

Forget trying to disable the threaded SMS all together. This time try backing up your SMS on your Tilt 2 using Jeyo. Once it's backed up, look in Jeyo and see how it is arranged. If you see all your received SMS in "Inbox" and sent SMS in "Sent" I guess that is a good sign. Then perform a hard reset on your phone and try restoring your SMS from Jeyo's backup file.

If after the first restore from Jeyo, your message is still out of order, don't panic. Like I mentioned earlier, delete all your SMS's(Not Hard Reset!) and perform the restore a second time. (I don't know the reasoning behind that, but hey it worked for me.)
[Touch Pro2, Tilt 2 Windows Mobile General] hopelovebeauty:
Das-Man,

I have the HTC Touch Pro 2 with Verizon as my carrier and I tried your method.

I downloaded all my messages back onto my phone via My Phone. They were all out of order. So, I then downloaded Total Companion and edited the registry value as you said, so that they became unthreaded. Went to Jeyo's website, downloaded the program, backed them up.

I deleted all messages in my folders, deleted the registry values, made sure my mms was closed, etc. Then restored my messages. They went back on but they are still unthreaded in my windows sms windows.

I already had my contacts, etc backed up. So, I decided to reflash my rom thinking that it would definitely get rid of my threading edits. That went smoothly, and I tried again.

In the windows txt app they're still unthreaded, but in order. In HTC's texting window, all texts are now separated by author. IE. All of mine are at the top, with all of my correspondents at the bottom. Though they are in the correct order, this still isn't very helpful.

You have any more ideas of what I could do or where I might have gone wrong?
[Touch Pro2, Tilt 2 Windows Mobile General] das-man:
First of all, the HTC's texting Window is a mystery I have not solved yet. Yes, mine also has the same nonsense with the the messages I sent on top while the messages I received on the bottom. I am still researching into it, and if i find a solution, I'll definitely let you know.

Now for your Windows txt app; after you reflashed the rom you said your msgs are still unthreaded after you transferred them. I am not sure if I had the same problem but I remember something was wrong the first time I transferred. That is why I deleted all the text messages and did the transfer process a 2nd time w/o reflashing the rom. In other words, the first transfer usually doesn't work for some odd reason but the 2nd time it does. If you see messages being sorted, then you are good to go, and don't touch it til you are certain it is done. I hope I didn't confuse you lol. BTW is it WM 6.5?
[Touch Pro2, Tilt 2 Windows Mobile General] hopelovebeauty:
Ugh, this is the most frustrating thing ever.

After reading your post, I reflashed my rom again. Put the txts on once, it was a no go. No sorting happened. I deleted all of them, reconnected to Jeyo, and went to restore again.

Jeyo got through all the inbox and about 1/2 the sent box. Then it errored and closed out, not completing the restore. I went into my inbox to delete this incomplete transfer, and lo and behold what was there began to sort. I left it alone to make sure and everything rethreaded. It was fantastic. But as I said, 1/2 my sent messages were misssing and thus did not get rethreaded in. So, I deleted all my messages again. Repeated process, jeyo didn't error this time.

But of course, now they refuse to rethread. I have deleted/re downloaded probably about 10 times now and not once did it begin to resort my txts. I even reflashed the rom, hoping that it only would work the 2nd time, still no cigar.

I just don't understand what makes the windows messaging app want to rethread or not. Are there special options I should select in the restore? Am I supposed to be checking that overwrite box?

And yes, this is WM 6.5.
[Touch Pro2, Tilt 2 Windows Mobile General] das-man:
When I was doing the transfer, I did not have the overwrite option checked off. The best thing i could suggest, is reflash your Rom. Make sure in task manager that messaging is not in there. Use Jaya to transfer all your SMS to the phone. If it did not thread, make sure you delete all your text messages. Don't use Jaya to delete the SMS's but use the phone. Make sure you delete your sent box, inbox and even drafts. If you have a lot of messages, it can take quite a while to delete so don't panick. When you see everything is clearn try the transfer process again and hopefully it threads. I'm sorry if I'm repeating exactly what you did, but that is the best I can think of.
[Touch Pro2, Tilt 2 Windows Mobile General] hopelovebeauty:
I got it to work. I had to turn of the threading option when I transferred the texts over. Once they were one, i went and renabled threading. All threaded perfectly. =)
[Touch Pro2, Tilt 2 Windows Mobile General] leepriestenator:
I don't seem to have the problem you are all facing. I tested many different scenarios without turning off Threaded Messaging. First synced all the messages, then archived only a few that were part of a threaded message. they obviously got deleted from the phone. Later I restored the same messages from the archive and voila, they were all back perfectly.

I'm not sure, but many of you might not be aware that there is a new version of MyPhone available. The one that came with my ROM wouldn't work unless I upgraded it, which I did.
[Touch Pro2, Tilt 2 Windows Mobile General] das-man:
Good to hear. BTW, were you able to get the HTC Messaging to thread properly?
[General Questions and Answers] Archer:
Hi.

I don't think this is an easy one, but I'll ask anyway.

When you use "Pictures & Videos" to select an image to use as your Today background, you are given the option of "Transparency Level". I just wondered if there's a way to select what colour is 'behind' the image when you do this. At the moment, it's white (or close enough), so the image gets lighter with more transparency. I would like it black, so that the image gets darker with more transparency. Realistically, you should be able to assign any colour, so you can almost colourize an image by altering its transparency.

Anyone got any ideas?

Thanks.
[General Questions and Answers] denco7:
It is not a " white colored " background. It is a " lack of color " background, no image.

You cannot overlap two today background images.
[General Questions and Answers] Archer:
I don't want to "overlap" two today background images. If you read the question, you'll see that I've explained the background colour is white, which it is.

Set the background image to 100% transparent and you'll see white. A background with a "lack of colour" would actually be black (see transparency, 0 value colour etc. for both windows & web development.)

Something, somewhere, defines that white is used as the background colour (it may actually be an overlay for the image, with inverse transparency, as opposed to a transparent image over a solid colour.) This may be a registry entry, but it's just as likely hard-coded into the OS. Either way, that is my question.

Thanks for trying to help.
[Touch Diamond2, Pure General] caro23:
Hi all,

I want to install the original HTC ROM on my MDA Compact (T-Mobile version of TD2).

Has anyone tried this before? As far as I can see, this should be working with a HardSPL.

However, I've tried to download the ROM from the HTC webpage. The page asks for the serial number and it doesn't accept the serial from my MDA Compact.

Can anyone give me the serial of a TD2 (german version)?

Thanks in advance,

Caroline
[Touch Diamond2, Pure General] Mike Austin:
Same here - but I did download it from http://htcpedia.com/news/official-topaz-wm6_5-rom-upgrades.html.

However, following the various reports on this forum, I prefer to remain with 6.1 at the moment.
[Touch Diamond2, Pure General] caro23:
Thanks, I've found a working serial: ht965l100038

What do you mean exactly ? Are there any compatibility issues when using the original ROM on the MDA Compact?
[Touch Diamond2, Pure General] Mike Austin:
I mean WM6.5 in general. There are too many people reporting problems with it and too few people reporting improvements.
[Touch Diamond2, Pure General] caro23:
That's interesting. I've read many threads about this new ROM and I now have the opposite impression. Most of the people say that the new ROM is quite better than the old one.
[Touch Diamond2, Pure General] Mike Austin:
Good! I look forward to hearing how you get on with it!
[Touch Diamond2, Pure General] djbrookes:
Can't install on T-mobile COMPACT V uk

Hi,

I've tried the steps mentioned in this thread to get wm6.5 onto my T-mobile MDA COMPACT V but it wont work.

It starts to install and then says "verfity you want to update the ROM version" From "Images version 1.40.110.1" To "Image Version 2.16.405.4".

I click on 'Next' to complete the update but the PC then reports "ERROR 294: INVALID VENDOR ID".

I then have no option other than to click 'Exit' which cancels the install.

PLEASE PLEASE PLEASE HELP :-)

I really want to update this phone to 6.5

Thanks

Josh
[Touch Diamond2, Pure General] caro23:
As I mentioned before, you have to install HardSPL.
[Touch Diamond2, Pure General] pa49:
The difference is that HTC's ROM upgrade process detects the model being upgraded and does not allow a compact V to be flashed with TD2 official ROM by this method. They are separate models.

You have to change the vendor ID and fool it into seeing a TD2 or CID unlock to allow cooked ROMs to be flashed.

Try one of Aman's cooked ROMs (TESS version 3.9 is the latest). They are very good, stable and fast. Flash hard spl first (olipro 1.83) and you should have no problems.
[Touch Diamond2, Pure General] :
This is incorrect - where did you get this information from? A T-Mobile Compact V is a TD2 internally, model no. T5353. With HardSPL 1.83 installed it can be flashed to any ROM, including any HTC stock ROM. That's how I flashed my Compact V with the new HTC stock WWE 6.5 ROM this week.
[Touch Diamond2, Pure General] pa49:
It's not incorrect!

You unlocked the ID specific to the T-mobile product by flashing HSPL. This has been the case ever since they began branding HTC phones. It's also done by many other manufacturers as a means of network providers locking in users to their branded OSs and is used by them to determine warranty liability in the case of recalls and service work. Nokia is another manufacturer that does this extensively with T-mobile.

The whole point of HSPL flashing is so that you can bypass this lock mechanism and flash what you like. As you found out.

Otherwise there would be no need to remove it, reflash with a stock ROM and "relock" should a return through your network operater be required.

This was also the reason why there was an initial wait for SPL/HSPL when the TD2 was launched as flashing cooked ROMs to a branded phone was not possible.

If you look at the earliest threds on this forum you will see that.

The Compact V and the generic TD2 may run the same internal hardware (and I would even question that as common sense would dictate improvements along the way should they be required) but the HTC website upgrade system detects a difference between the "stock" models when presented for a flash.
[Touch Diamond2, Pure General] :
Regardless of what you meant to say, you quoted a previous post which (correctly) suggested that HardSPL 1.83 was what was needed, and which you then directly contradicted by saying "HTC's ROM upgrade process... does not allow a compact V to be flashed with TD2 official ROM by this method." The only method mentioned in the quoted post was HardSPL 1.83, and it looked like you were saying that wouldn't work. That's what I said was incorrect.

You then said "They are separate models", which is incorrect because under the covers they are the same (Topaz T5353) - maybe you meant "different brands", but that's not what you said. You went on to say that you have to "fool it into seeing a TD2", which is not correct; the process of installing HardSPL doesn't fool anything into seeing a different model, it just removes the CID lock.

To me, what your post said was that a stock HTC ROM couldn't be flashed onto a Compact V by the usual process of installing HardSPL, because it was not actually a TD2 and therefore you needed to "fool" the HTC upgrade process (how, you didn't specify). (Presumably though, an Orange TD2 would be OK because that really is a proper TD2, so no "fooling" required.)

That may not be what you meant, but that's how I read it. Read your post back and maybe you can see my point. This would be very confusing to a newcomer, which is why I decided to point out the errors.
[Touch Diamond2, Pure General] pa49:
I meant to say everything I did say.

The post quoted didn't suggest anything. It stated "HardSPL v1.83!" without any qualification and then asserted that "There's no difference between TD2 and MDA V except cover-design." which is untrue!

I ignored the former and pointed out the incorrectness of the later.

Whatever you thought it looked like I said is less important than what I actually did say and it would seem that as I ignored the HSPL reference as being a point taken for granted you construed my statement that there was a difference between the TD2 and the Compact V as a comment on the relevance of the use of HSPL to the upgrade process via the HTC site.

So in order to clarify and run the risk of being pedantic at the same time allow me to elucidate-

If a stock Compact V is presented to the HTC site for upgrade by way of their online system it will be rejected as an inappropriate model.

The Compact V is designated as a TOPA200 model by HTC, extensively designed and branded for T-mobile and therefore is not recognised as a TD2, a Topaz, a T5353 or any combination thereof. The model information is held in a HARD flashed portion of memory that is addressed by HSPL at a programming level not normally accessible to end users. There are other parameters that are embedded in the same way as well as other requirements that are specified by T-mobile (and other carriers on model variants) that are included in the stock carriers ROM. Certain functions are disabled and branding applied by way of bespoke software and programming.

Flashing HSPL allows it to be "seen" as the correct model for upgrade by this method. It does not turn it into another model.

I trust that clears up any confusion and puts my comments into perspective.

If anyone read my post(s) and took it (them) any other way then I hope that clears it up and rectifies any "errors" that may have been misinterpreted.
[Touch Diamond2, Pure General] Wayfarer56:
MDA Compact V

Hi After some "fun" today my MDA compact V now thinks its a TD2, flashed it with SPL 1.83 and then put the HTC Topaz flash on, as per above, all appears to work very well - now on O2

Thanks for all your hard work never would have got there without it
[myTouch 3G, Magic Android Development] andreo1964:
Hello all,

Here is my situation.

I was happily using a Hero rom on my HTC branded Magic 32A.

I thought that the new update from HTC would have the Sense interface so I updated, hopping that Bluetooth would finally work. And it does.

But, now I can't root and I can't downgrade to the previous update.

Anyone with a similar problem?

Thanks in advance.

Andre

Releas date 2009-10-27

Firmware 1.5

Build No 2.20.401.2

Baseband 62.575.20.23U_3-22-23-18

Kernel 2.6.27.3d7dcf2e
[myTouch 3G, Magic Android Development] Narreto:
Norwegian ROM update

Same problem here ! :(

I've tried searching EVERYWHERE for some answers, but I can't find any help.

Please, say if you find out ! :)
[myTouch 3G, Magic Android Development] rps13:
I also have a swiss magic and i also updated to the new official firmware. Since there are now new sense roms with working bluetooth (such as Hofo 3.0.3) just flash to one of those if you installed a recovery (either amon ra's or cyanogen's) and if you don't have a recovery use flashrec which can flash a recovery rom even with a perfect spl which comes with this update.
[myTouch 3G, Magic Android Development] Narreto:
can't flash or anything, just get's errors ...

it seems like the recovery is still there, but it's no use, and I can't get a new recovery img. Nothing works :S can't unroot or root a new rom :S
[myTouch 3G, Magic Android Development] andreo1964:
I've tried as well, no good. Why did HTC bother with an update without the new Sense UI . . . I'm starting to wonder how incompetent they are :mad:
[myTouch 3G, Magic Android Development] Epedemic:
What spl do you have now?
[myTouch 3G, Magic Android Development] andreo1964:
Hboot-1.33.0014
[myTouch 3G, Magic Android Development] Epedemic:
Good. Make a goldcard and flash a engineering SPL or 1.33.0009. I can confirm that it will work!
[myTouch 3G, Magic Android Development] andreo1964:
Thanks! That DID work! Good to have you all around . . . . !

Cheers.
[myTouch 3G, Magic Android Development] Howler62:
the update in canada a couple months ago gave us the perfect spl 1.33.0010 from 1.33.0009 so what i do now is go to unlockr.com and use the 1 click root method for htc magic then i add my hero roms
[myTouch 3G, Magic Android Development] charles29:
Can you please tell us what SDCard you are using?

I tried already 10+ cards, but after writing the goldcard image to offset 000 - 170 on the SDCard, Windows (as well as the phone) does not recognize the card anymore.

I think the cid is unique by the card, not by the phone. Correct?

--> Could I use a goldcard that was created by someone else?
[myTouch 3G, Magic Android Development] Eskibo:
No you couldnt, the CID is taken from your phone and plotted into the card. You need to create one for YOUR phone.

When creating the card, are you sure you are saving to physical drives and not logical?
[myTouch 3G, Magic Android Development] andreo1964:
I have tried with many SanDisk but the only one that worked is a Kensington 4GB. Also, and i'm not sure if that did do anything, but while downgrading, press the action key ( the track ball ). Good luck.
[myTouch 3G, Magic Android Development] themaskfly:
no, you are wrong, it's the cid for the sd card not from the phone, u can read the cid code de sd card by any linux os. and the goldcard can be used for any htc magic. i have two magic, one from TIM another from Singapore, and they are all flashed into the official taiwan sense rom by the same glodcard. :D
[myTouch 3G, Magic Android Development] thihaz:
which image do you put into your goldcard?

Which image did you put into your goldcard?

Where did u get it?

Can you tell me a little bit more what you did after you have created a Goldcard?

Because most of the people stuck with the perfected SPL after upgrading from HTC.

Thanks.

thihaz
[myTouch 3G, Magic Android Development] charles29:
Ahhhhhhhh! #%&$# !

Thank you Eskibo - I was always opening the cards as logical drives!

I just tried again as physical drive and already the first card worked fine. :-)
[HD2 General] mightymn:
Now this has always been a concern for HTC devices. Some of them have cold/blue screens, others warm screens and even some screens are kind of blurry compared to other ones. Can someone clear this thing a bit? What regions get what screens? Isn't there a way to fix the bad ones through software? etc...

I ask this coz I've seen a lot of Leos in these videos witch have blue screens and I really fear I may get one of them
[HD2 General] cobnut:
Links to these vids?
[HD2 General] DaveLeh:
That depends on the video camrea those videos were recorded. Bad video camera = HD2 screen seems blue and blurry.
[HD2 General] KowboyBebop:
Wel iam sure thats not the point. I have TP and my friend have HD. And in comparison, his screen really feel blue. You know, the color are just more blueish (oO,). Its kinda disturbing if you ask me. But my friend dont mind. SO any1 know if its just us or there is something with screens?
[HD2 General] mightymn:
In videos were there's only one phone you could say the white balance or some other setting is problematic in the camera. As for HD2 I've seen a video where there are both a Touch Pro 2 and a Hero next to it so it can't be the camera. Link to that video:

http://www.youtube.com/watch?v=dFtqsrbsHzY&feature=player_embedded

Aside from HD2, I've seen it myself on old blue angels (even from the same manufacturer- imate) and also the new Touch HD.

Even now, some diamond 2s have warmer screens than others which makes the whites a bit yellow
[Touch Cruise 2 General] tatagsm:
my problem it's .

the phone allways give me ( emergency call only ) with or without sim card.

so what i need fix sim card problem or unlock my phone .

br

tata
[General Questions and Answers] bendecko:
Hi

I'm developing an app that outputs phone numbers and postcodes on the mobile device screen.

It is likely that the user will want to call these numbers or use the postcodes in the built-in satnav.

How can i <markup>the phone number</markup> so that the device allows click to call or send to savnav app.

Having the user write down the number and then call it seems pretty backwards!

Ben
[8125, K-JAM, P4300, MDA Vario General] MaXmeOliver:
My power-button don't work, so I was wondering if anyone could help me to fix this. Maybye someone have a power-button i can buy, or there's a software fix I could use, like i open a program and press lock screen and something like that, because i can't lock the screen and tha makes my battery time very bad.
[Touch GSM General] riahc3:
Hey

My friend has a problem with her HTC Touch that it cannot turn on or charge. Sometimes (randomly) the amber light turns on for a second (when we plug it in to charge) but turns off. She changed the battery with a new one which fixed the problem for about a day and afterwards same issue. She also tried with another charger and same issue as well. What could be the problem or how can we fix it?
[Touch GSM General] prats:
i had same prob luckily it was in warranty they changed the main board
[Touch GSM General] AirBagas Fail:
hi, im a complete rookie on this, i have 2 elf in the same condition, what can i do?. plz someone point me in the right direction!. thanks

ps. ill keep reading
[Touch GSM General] ivanmatz:
If it’s under warranty get your motherboard replaced or if you are fortunate you can even get a fresh device but if it’s not under warranty get ready to play a whooping 14K for a new motherboard.

I have got my MB replaced