yashsingh1/xdaforums huggingface dataset:
[Touch HD Windows Mobile ROM Development] bokiv:
WM 6,5 color v 11 HTC works exellent to me, nice colored

Also using 2a graphic driver, rom is not faster but looking clear, and havent circular black- graycolor on tabs in manila, sugest to all install 2a driver and sugest PhamQuangt to include s 2 a in next realise
[Touch HD Windows Mobile ROM Development] voileuxcool:
When new udapte soon ?
[Touch HD Windows Mobile ROM Development] chriss66:
Hey, THX.

Was just about to eddit my post to say I figurd it out.

Thought I'd check 2 see if somone ansewrd, wouldn't be roud, u know...;)

But thx 4 u'r replay:)
[Touch HD Windows Mobile ROM Development] ZekeWolf:
I have the same issue.
[Touch HD Windows Mobile ROM Development] schiwa:
Flashing Pham Quang

Hello Buddy ClydeB1

Please assist flashing the new Pham Quang ram?
[Touch HD Windows Mobile ROM Development] RonGRossi:
That is just what I am doing. I will let the forum know.
[Touch HD Windows Mobile ROM Development] reidar.ostrem:
Dont know if its been answered but untick the repeat checkbox in sounds/notifications..
[Touch HD Windows Mobile ROM Development] schiwa:
My current version of ROM is Dutty's LeoR4, There were minor problems here an there, but the major problem is the scroll bar, other than that its a nice ROM and Dutt's given his hardmanship to develop a stable ROM.

NOW, I want to flash Phan Quang, any tutorial or assistance, plz.

So far ClydeB1 assisted me in several issues, kind of hoping that he will do the same here.

Thx

Edit : I'm using Blackstone Touch HD
[Touch HD Windows Mobile ROM Development] brojectiot:
What theme is this? It looks awesome.
[Touch HD Windows Mobile ROM Development] makbil:
Not the right place but installing Dusk theme fixes the scroll bar issue, there is also a registry fix for it.

I briefly tried v64 but like most other M2.5 ROMs (excluding Dutty's Leo R4) it will not run a program I absolutely must use. The culprit is most likely one of the new Manila files but until that issue is solved, I can't install these on a long term basis.

If anyone would like to work on it, the program that can install but crashes on launch is called DiabetesPilot
[Touch HD Windows Mobile ROM Development] RAP5:
I am not installing any programs and having the hard reset issue, and yes multiple times a day. It's getting irritating. Im using V63. It was real stable for about 5 days then it just went south...
[Touch HD Windows Mobile ROM Development] makbil:
This seems to happen randomly with WM6.5 ROMs. It was reported on some threads that first flashing to a stock ROM then flashing the ROM of your choice fixes this issue.
[Touch HD Windows Mobile ROM Development] ZekeWolf:
Have you tried to install "SDKCERTS"? (to route/avoid the signed issue)
[Touch HD Windows Mobile ROM Development] dogbreath:
On t-mobile in uk, this rom doesnt seem to have the right connection settings for mms to work, anyone else in the same boat and can post the settings?

Yer, ive tried a few settings around and about but no joy

on v63 me
[Touch HD Windows Mobile ROM Development] ClydeB1:
I'm here now, but now you're off line. Sorry, went out to dinner and the movies with my wife. I have to pay upfront to allow me to have some time online :D

If you've flashed Dutty R4, you just need to follow the same process to flash to this rom. If you used uspl before you will need to rerun it and then flash, or if on hspl you can just flash.
[Touch HD Windows Mobile ROM Development] RAP5:
Since I have a couple of stocks roms, I will try this later and post results. I really liked ver 63 and it was about perfect as stated earlier for about 5 days. Thanks for the tip
[Touch HD Windows Mobile ROM Development] henv:
Just be sure you flash a rom with version 1.56. Maybe the best is to dl the latest version from htc.com
[Touch HD Windows Mobile ROM Development] puri1:
Page Pool

Guys just need help here with V64 Page pool. What number you guy recommend i should change it to. I use multi Applications and use Manila at the same time. So to get both of them balance what number i should go with. I think 18 would do but i will appreciate opinion. Thanks.
[Touch HD Windows Mobile ROM Development] ClydeB1:
I think the consensus has been either 20 or 24. I've been using 24 for a while now and it serves my needs well.
[Touch HD Windows Mobile ROM Development] puri1:
Thanks bro then ill go with 20. But before i flash any new on the newer version like V65 ???
[Touch HD Windows Mobile ROM Development] BigE:
Have you hard reset intitially?

Just curious.. When you flashed V64, have you tried hard resetting BEFORE installing anything? Here is how non volatile memories work- You actually have the flashed code written to a NVRAM at two different locations. One is a serial EEPROM and the other is NVRAM. for unknown reason, this dual write session isn't perfect with touch HD. Almost every chef recommnds to hard reset the phone right after flashing.

I suspect the reason is to make sure the NVRAM is loaded correctly from the EEPROM , not directly from the dual write while flashing, as there are few more elements (USB, PC) involved in this write session, and there is a good chance the NVRAM has a glitch.

So just let me know, if right after flashing the phone, have you hard reset it yourself (VolUp+Voldn+pwr buttons) . If you did not, it MAY BE the reason.

From personal experiance- I had the phone crash on me few times with different codes (Miri, NRG and PHAMQUANG's) until I started hard resetting the phone as soon as I flashed. Since I do so, I did not crash.. statistics show it is working..
[Touch HD Windows Mobile ROM Development] forelli:
Have you set the new mms server you added as default? It's on the screen where you see add new server, if you click on the right soft key (menu i guess), set as default and it should work

To both of you guys, try this if you want, maybe it will help: First, sync your data, then Hard reset BEFORE and AFTER flashing a new rom. This is what I'm used to do with my Omnia, and as it's working great, I do the same with my formerly sim-locked Blackstone and it works a threat. I have hspl thanks Clyde 81 and his useful flashing guide for dummies. I've never tried uspl and won't anyway. I have install on V63 as well as on V64 the following programs with excellent stability and good responsiveness: spbtime 2.1, resco explorer, skTools, core player, mortscript 4.2, ACR 1.2.2, Showaco cHome editor beta 1.6.

Themes: Dusk Theme, Dusk Manila 2.5 Evolution v1.2 NMSI.

Titanium plugins: cAnalog clock, Titanium weather 4.2 (and the script fix)+Beyond Invisible icons+Stardock icons+settings for default wm 6.5, Ccomm manager 0.32, cOffice, AT fave people, CFacebook 0.5.

Hope this is useful to you.

forelli

edit: pagepool is not modified and Taskmanager is working as it's supposed to, by tapping on the clock, and I haven't recalibrated my screen.
[Touch HD Windows Mobile ROM Development] RAP5:
That is the exact ROM I used even though I have a T8285.

BlackStone_HTC_Europe_1.56.401.0_Radio_52.62.25.34_1.13.25.24_Ship
[Touch HD Windows Mobile ROM Development] ClydeB1:
I wish I could take credit for the Dummies Guide, but this is all Digital Outcast's work. ;)
[Touch HD Windows Mobile ROM Development] forelli:
Thanks to Digital Outcast, and to you to having put it in a thread:)
[Touch HD Windows Mobile ROM Development] makbil:
There's nothing wrong with using USPL to flash a ROM, I've used it until recently and never had a problem. The advantage of using HSPL is that you can skip the additional step of installing USPL each time you want to flash a new ROM.

Thanks to BigE for the best explanation put on paper that I've read regarding the merits or reasons for a hard reset after a flash. With your permission, I will refer others to your post when the discussion comes up.
[Touch HD Windows Mobile ROM Development] RAP5:
I agree Makibil great post by BigE. Also I use USPL and it's no big thing at all. Just remember to uncheck your Active Sync USB and the USPL GUI does it all.
[Touch HD Windows Mobile ROM Development] RAP5:
OK I followed your suggestion,

Just flashed OEM HTC EU ROM, then let it setup, reset, then reloaded Ver 63. I am keepin my fingers crossed!
[Touch HD Windows Mobile ROM Development] Pandemoniumone:
This would just promote laziness, we already have plenty of that. Perhaps simply ignoring such posts is the answer, either way this is an issue that will never cease to exist in forums so we may as well get used to it ;)

I was having the same issue and by default in windows sound settings, "repeat" was unchecked. I found when I press on the icon and activate the full screen notification, if you press on the actual message and not "Dismiss" or "Snooze", the sound will not repeat itself. If I just press "Dismiss", the sound will continue to repeat itself.
[Touch HD Windows Mobile ROM Development] henv:
I used the dutch version of that when i had the problem that mine phone freezed. Flash original rom. Run the calibration etc wait till phone reboot and asked for pin. Then did a hard reset. Same steps again. After that flash the custom rom. Dont forget after the original flash that your radio is 1.13 again
[Touch HD Windows Mobile ROM Development] Sean3:
Thank you both Cortez and Pandemoniumone...They are the same number, except, of course, for the +1 in front of the voicemail number in phone settings. So just for the heck of it I deleted the +1, and it worked! Great job, thank you!
[Touch HD Windows Mobile ROM Development] gohyc:
As a rule of thumb, I ALWAYS perform hard reset immediately after flashing new rom, so this can be ruled out as a cause.

I have been on PDAViet since the 1st version of its Manila 2.5 appeared here (v56? Too many versions, can't recall), and had been installing the same software for all the ROMs, but this resetting issue only surfaced starting from v63, so for now it is v63 and v64 (both incidentally is with WM Build 23053). I have been following this thread closely since the beginning, and it is clear that this auto hard-resetting issue only started appearing for those who had flashed v63 or v64 (although it doesn't happen to everybody yet, but like Rap5, it only happened to him after 5 days).

Another point to note is, I have exactly same WM and Manila Build on my X1, with even more software installed (didn't get too far installing apps on HD as it crashes before I can do much), my faithful rom in X1 is keeping me satisfied until I get my Touch HD back from service centre).

I think people should start realizing that there is indeed a very serious issue with v63 and v64. If you haven't got this issue yet, you are lucky, but some of us aren't that fortunate!!

Ultimately, the decision is still up to the individual to flash. I will stay away from v63 and v64 until the next version (and hopefully this issue is being looked into). The problem is author of PDAViet isn't "present" in this thread to listen to issues reported here (correct me if I am wrong), so they can be addressed accordingly. I assume the moderator of this thread isn't the author for PDAViet ROMs.
[Touch HD Windows Mobile ROM Development] gohyc:
I am sure a new version will be out very soon as there is already an updated version of Manila 2.6 with Twitter tab added. I am using it on my X1. :)

Check it out from this the link below:

http://htcpedia.com/touch_it_leo_v__798bf171b4fa2dd31/soft/sony-x1-rom.html
[Touch HD Windows Mobile ROM Development] leslie222:
Any news of V65??????? I just enjoy this whole flashing business......
[Touch HD Windows Mobile ROM Development] chainbolt:
The next one is V66, (V65 to be skipped) :D
[Touch HD Windows Mobile ROM Development] MrRalphMan:
Thanks Dude, I'll see if I can get it up and working.. ;)
[Touch HD Windows Mobile ROM Development] BigE:
it is only an educated guess..

Sure, it's OK by me, as long as you understand I do not have the circuit design of the phone. I just have the understanding of how a loader works (where the code is stored in two separate locations) so when we perform 'hard reset' we practically take the code from a serial EEPROM and re-write the NVRAM. That is what any hardware designer will do to make sure there is a way to 'fix' the phones without going to a lab..

Since we are all PC junkies, I bet we all tend to browse the forums while we flash the phone, listen to music, play video, and use the PC so the flashing is time sharing the PC resources... add to that a cheapo USB cable/cradle and some magnetic interference around it, and you have a good recipe for a bit error in a flash session. Normally the EEPROM is immune because it is serial write, and because it has a check-sum (some sanity check). Having the same write session load the NVRAM (and I believe this is what is does) is , at best, more sensitive than just loading the EEPROM.

I have to admit all the text I am writing here has no connection to any HTC design, and specifically not to the HD.. it is just fundamental digital design any engineer will do... I don't have access to their schematics (I wish i had..)

Be my guest, and quote/amend/re-phrase the previous email and this one, and put it anywhere you want, as long as it is taken as what it is- an educated guess...
[Touch HD Windows Mobile ROM Development] leslie222:
Thanks Chainbolt..........any reason for the skipping???? Just curious. And is there a new wm 6.5 build already available???
[Touch HD Windows Mobile ROM Development] BigE:
You may be right..

I was thinking about a reason why there are more issues with V63/64 and I have to admit you have a point. I have seen before cases where the code itself was the cause of the hang-up. After all we need to remember 23053 is new code, and I have my doubts if M$ is validating the code on our devices. So in the basic essence of it, there is always a possibility there is a software-hardware flaw by design that afloat in V63/64. Probably nothing the chef has to do with, and since 23053 like all other WM6.5 codes around are beta after all, we take the chance it does behave funny on us. Regardless- keep hard reset after flashing, and avoid using the computer while flashing for any CPU hungry process, letting the flashing the right of way..

I think you have a good advice to stay away from V63/64 IF it already crashed on you. I was not lucky with V63 and it crashed on me, but I am sure it is because I did not hard reset.. well, not 100% positive but more than 50% :)

But if not V64 then what else? V61/62? I tried today Miri's 23053 and hated it. I tried Dutty's R4 and ended up with no access to setting of the phone (it bounce to Manila setting) and I could not put my personal ID in, and could not register to SKTOOLS... I tried NRG roms, and they are nice but 23016 based and the battery life seems to be an issue... I will try V65 as soon as it shows up, just because I am a junkie... :cool:
[Touch HD Windows Mobile ROM Development] ClydeB1:
My pleasure, hope it works for you and saves you a hard reset ;)

I think he's just pulling your leg :p. AFAIK there is not a new wm6.5 build yet, but there is an updated manila version (1919) with a Twitter tab.
[Touch HD Windows Mobile ROM Development] James62370:
Hi BigE, I purchased my Touch HD because of your recommendation :) I had my trinity for along time, I still have it - I have now handed it down to my gf...

I'm loving my new HD, and there are so many ROM's to try... I have flashed all that you have below, and ended up with Topix 3.0 - It's still on Windows 6.1 with Manila 2.1 (but has the color Leo Icons) - for me it seems stable and as fast as the stock ROM. I actually didn't mind the stock ROM, except it came with too much Bloatware from Telstra. I dislike icons that don't do anything. However, I was impressed with it's speed and stability...

I feel that there are still too many issues with the new releases of 6.5 and new versions of Manila. However, I do enjoy testing all of the new builds... I can barely keep up with all of these threads...

Anyway, just thought I'd give my 2 cents, and thanks again BigE for letting me know about the Australian T8285 release where I can make use of AT&T's 3G network in the U.S.
[Touch HD Windows Mobile ROM Development] pg2005:
I think i solved the Alarm bug with no snooze and dismiss buttons.

After I installed the V64, I installed WVD and checked if it´s working. I couldn´t stop the program, so I was going for showcase 1.10 and the registry entries etc. Showcase worked but really slow.

than I tried later at night my alarm. I installed some fixes and patches from this forum. It broke my Manila direction totaly.

I went on the whole day yesterday to find my problem. Later on in the evening, I have had enough of mucking around and used the PIM BACKUP, which u can find in applications, to keep my contacts etc on the storage

and I did like a Hardreset in

Start/Settings/System/Clear storage and confirmed with 1234

This solved the Alarm Problem with snooze and dismiss button

After it was done I did the Provider settings

- than Start/settings/system/regional settings to germany (or ur country)

- than Start/settings/Clock & Alarm to Germany Berlin settings (or ur city)

- than I turned my Wlan on and went to my location weather

- than I did set up my first alarm in Start/Alarms

- I went after to Start / Settings / sound and notifications

-- here u should Enable sounds for Programs and Notifications (alarms,reminders)

-- goto Sounds on the right and than reminders and set Display message on screen

voila Alarm is working now with notification in lock screen and without!! Nice sleep guys

Taskmanager to end programs like wvd without a X (end) button

- here we have a no fingefriendly thing as describet in this thread already.

You have to use the stylus to click right behind the .png clock letters at the top right of your screen. It really works.

I have only installed

- Resco explorer

- WVD

- Nitrogen

- Coreplayer

- mToolbox

- Moisis Vafiadis Shake and Save (screenshot app)

- and a shortcut to IGO 8.x.10

I dont need anything else, maybe facebook and twitter

I did not install any alarm patch or something like that

Request: How do I change my background in START?

- it worked twice than i couldn´t change it anymore.
[Touch HD Windows Mobile ROM Development] avicoh12:
I went after to Start / Settings / sound and notifications

-- here u should Enable sounds for Programs and Notifications (alarms,reminders)

-- goto Sounds on the right and than reminders and set Display message on screen

it worked !!! tnx

fixed my alarm issue
[Touch HD Windows Mobile ROM Development] onesolo:
Wow I tried updating my location, via wifi, and worked awsome!!! This rom rocks, very little problems I have...
[Touch HD Windows Mobile ROM Development] leslie222:
wow..Mine NEVER does. I wonder if it is because I live in a small town...or as I suspect because I use a proxy server. ven the email tab never works over the wifi though all else does.
[Touch HD Windows Mobile ROM Development] ClydeB1:
Neo Driverpack Updated

Version 3 is now available.
[Touch HD Windows Mobile ROM Development] K_Hismoom:
Great, I just connected my phone via USB and killed it. A reboot after that lead to the Windows Mobile bootscreen, where it stuck forever.

Had to hard-reset, again...
[Touch HD Windows Mobile ROM Development] RAP5:
Will check out the radio today. THanks for the tip
[Touch HD Windows Mobile ROM Development] avicoh12:
and it works great tnx
[Touch HD Windows Mobile ROM Development] luckyluke168:
Oh thanks I wanna ask can be used at HTC Touch Diamond 2..I cant hardly wait to test the ROM...Thanks
[Touch HD Windows Mobile ROM Development] jyod24:
i cannot receive sms when my phone is in sleep mode. You actuall hav to awake the phone for sms to come .I only got this prob when i flashed v64. But now after i flash back v63, the prob is still there. Any solution, other than turn wake on sms receive using HD Tweak. I hope to get back like the past when sms just come in
[Touch HD Windows Mobile ROM Development] bokiv:
A hope too, sms on time are important, but before that working fine with Hd Tweak
[Touch HD Windows Mobile ROM Development] makbil:
Thanks. It's the way you put the idea on paper that is important and easy to understand. I had more or less the same understanding but you explained it quite clearly.

You just took me back some 20 years or so when I had to leave some EPROMs (those are the ROMs where you could see the actual chip through a transparent window on top) under direct sunlight to have them erased, I had a programmer but not an eraser :)
[Touch HD Windows Mobile ROM Development] makbil:
No, obviously, unless you want to brick your phone.

You should look at some TD2 specific ROMs.
[Touch HD Windows Mobile ROM Development] henv:
A few people had the problem that the phone was freezing and after a reset the telephone would hang in the bootscreen. Only a hard reset want usefull by me, after a few hours till a few days the problem was there again. I solved it to first flash the latest rom from htc. Run the configuration after the flash. When i did did two times I flashed a custom rom, no problems since
[Touch HD Windows Mobile ROM Development] oluwaponmile:
Is there any noticeable difference in video acceleration or performance?
[Touch HD Windows Mobile ROM Development] khurr:
My mobile isnt using 3G, only E(dge) is displayed on top.

Im using v64.

Help?
[Touch HD Windows Mobile ROM Development] avicoh12:
turn 3G on it helped me
[Touch HD Windows Mobile ROM Development] gohyc:
I have warned a few times about v63 and v64 causing the Touch HD to hard reset or hang at boot up (had to hard reset), but people doesn't seem to take it too seriously. I would avoid it at all cause until a new release is available for test. I believe v63/v64 ROM isn't cooked properly, and not because of WM Build 23053 as I am using this build on my X1 and so far I did not encounter this hard reset problem, only on the Touch HD.

I am unlucky to be the one of the first to report this issue, and thought there is something wrong with my Touch HD and sent it for repair.

Still, the choice is yours. I only help to warn people who can't afford to keep loosing data or afford any time for a hard reset.
[Touch HD Windows Mobile ROM Development] gohyc:
Thanks for the info Clyde!! :) Did you notice any improvement from Version 2/2a?
[Touch HD Windows Mobile ROM Development] K_Hismoom:
I did flash the latest stock rom, but still have that problem. Gonna try that again, flash the latest stock rom, hard reset, flash custom rom, hard reset and see if it works then.

I remember having this problem before on V61, but not V62.
[Touch HD Windows Mobile ROM Development] K_Hismoom:
Thanks for trying to help.

I still hope, I can narrow the problem down somehow.
[Touch HD Windows Mobile ROM Development] ClydeB1:
I haven't noticed any significant difference. If anything Coreplayer seems to be a little worse. Going to go back to 2a to check it out again.

The photo album and music player seem to rotate slightly faster, but as I say, no huge difference noticed so far.
[Touch HD Windows Mobile ROM Development] gohyc:
Hi pg2005, not sure what you mean by this. Did this resolve the snooze option where you can select the different times to snooze, or you mean you resolve the issue with snooze and dismiss button missing?

In the first place, I never encounter issue where snooze and dismiss buttons are missing. I thought you were complaining that the snooze options (different snooze time selection) were missing. Perhaps there is some misunderstanding.

Anyway, the snooze options (able to select different snooze time) is definitely missing in WM6.5 Build 23053. Builds before this have this option and can be fixed using cab to disable the HTC Notification Pop-up that has this option missing. It is HTC LAZY way of implementing the Notification Pop-up replacement.
[Touch HD Windows Mobile ROM Development] avicoh12:
he means snooze and dismiss buttons are missing and it happened to many users when the phone was locked , his advise actually fixed that prob , at least for me
[Touch HD Windows Mobile ROM Development] pg2005:
New Graphicsdriver

http://xdaforums.com/showpost.php?p=3507221&postcount=1

how and what did u install? Any performance?