yashsingh1/xdaforums huggingface dataset:
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
I would love to beleive that this ROM is bug free,

but as always Im sure that even a stock ROM has its issues. I can't promise you it will be bug free, what works for one person may not work for others. In my flash, my device has performed like the shipped ROM with the edition of WM6.1, I have not had any issues and I have been running it for 5 days now in a realistic enviroment (work). Its not alot of time to compare but the majority of problems should have risen by now. Battery consumption seems to be comparable to what I originaly had, Exchange Server works on schedule with no hang-ups, ect..

I call it V1.0 because I beleive it is stable enough to release as a full version with proper flashing,

I had tested all features of the phone before giving this consideration. V1.X will be for incremental updates if fixes can be made. V2.x will be reserved if the device ever gets another ROM upgrade from HTC, you never know.

I haven' had any freezing problems yet,

but I have not loaded any other applications to the device. I am trying to test the stability of the stock rom with out influence from other programs. Third party applications or other ROM's cabs may cause the phone to lock up if it has an incompatible driver. Please let me know if you loaded any customizations or apps that seem to be the cause. For example, I am staying away from Opera 9.5 until an official release has been put out because it always locked my shipped ROM, even if it did operate fine for a few minutes.

Thanks for your feedback guys, It really helps me gauge concerns.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] disflipissofresh:
niki100 with 1.58.21.23
[Touch Dual, MDA Touch Plus ROM Development] disflipissofresh:
thanks Jcostanza4. i appreciate this good feedback :D

i think the installing 1 too many app may have cause freezes.

so once again thanks for replying back
[Touch Dual, MDA Touch Plus ROM Development] mactron:
Try one of the modded kaisers Roms!
[Touch Dual, MDA Touch Plus ROM Development] disflipissofresh:
okay i'll try the modded kaiser 1.64.08.21. be back with the result later on today.
[Touch Dual, MDA Touch Plus ROM Development] rodi1981:
One Q

What is diffrent betwine V1.0 and V1.0 + S600 Touch.dll

And what is S600 Touch.dll???
[Touch Dual, MDA Touch Plus ROM Development] randomelements:
Anyone care to whip up a version for a Niki200 with 16 keys?
[Touch Dual, MDA Touch Plus ROM Development] badaas:
you mean radio? ;)
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
I would but I have no 16 key device to test my results on. Anyone willing to try the ROM to see what problems may come up? I imagine that you would get the reverse effect of what happens when I flash a device ROM designed with a 16 key Keyboard to my device. (Numbered keys perform like 16 key version while other keys operate normally.) But I don't know for sure.

The s600 is a device that had a better Touch.dll which is a driver that had helps in 2D graphics performance. The most common of fixes is a performance improvement when scrolling with your finger in certain applications like Internet Explorer. Though this driver is an improvement it is not a complete fix, like the 3D accelerator built into the Touch Diamond.

The original version of this ROM does not have this updated driver, mactron had created another version containing the update. I dont know what the adverse affects are yet but the graphics performance is noticably better in these applications.

Hope this was explains what you were looking for.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
Confirmed - it works fine on the 16 key version!
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Thanks mskovrinskie, I have updated the first post with your findings and given you credit in the process.

I was wrong on my prediction of the keyboard, my errors must have been related to the XIP I was using from the NEON300. Thanks again for testing.

Thanks as always,

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] Xyse:
Yep been using it on my 16 keys too for the pass few days. IMHO, this is the best rom so far.

Haven't found a bug yet.
[Touch Dual, MDA Touch Plus ROM Development] rodi1981:
Yes

Yes it was Thanks so much
[Touch Dual, MDA Touch Plus ROM Development] rling:
Succesful change to WM6.1

Newbie. Followed instructions:USPL,HardSPL, followed by the ROM. Painless procedure lasting 15 minutes. Finally breathing again and able to wipe all the cold sweat off.

20 key keyboard working well, as is every program reinstalled, including iGo8.

Phone: Niki100 20key unlocked phone from US
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
I have tested the V1.0 + s600 ROM for about 5 days now in a working Environment

So far there have been no errors or bugs over my initial release. Battery consumption seems normal, no lock ups yet either. Touch Flo performance for scrolling works great when loading is finished; a bug the s600 driver fixed. I still wish PIE would let you scroll smoothly while its loading but Im sure this is not a graphics issue, more of a load on the processor and/or memory.

The only bug I still get comes from the original shipped ROM

and I have seen this on other custom ROMs too. Its where the call history application sometimes looses the Top Tray Icons with the Start Button and displays a white bar running accross instead. It doesnt bother me much so I leave it. I soft reset to fix.

I am glad to see the 16 Key Niki100 works with no problems.

Thanks Xyse for the praise, I really appreciate it.

I am looking for experienced Niki200 and Niki300 users to test this ROM.

This would be at your own risk, but if you are experienced then you would know how fix or unbrick your device if you get stuck. If you test, please list what Keypad version and any problems you may get. Neon Users: I know Neon users will have problems with this ROM so I would not advise them to test.

Thanks for the feedback guys.

I now have a poll running on the front page, check out this ROMs overall performance, and vote if you haven't yet.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] klotuer:
I would like to think of Tmobile MDA Touch Plus with the new WM 6.1. Can you tell me whether there was already there, so in German? PS: I'm sorry, the text is translated from google.
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
This ROM was working fine on my 16 key for a while but now I've run into a bad, repeatable issue with a black screen of death. The only solution is to pull the battery. After boot and PIN unlock, if I let the device go into standby, it will not wake up. I cannot receive calls. The bluetooth indicator continues to blink. The power button does not turn the screen back on.

Has anyone else seen this?
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
I am experiencing the exact thing with the Mary ROM. It's very annoying! In fact, there are a few other flakey things about this ROM that I'm discovering as I'm using it. Could it be WM6.1?
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Hmmm, I am not expereince this problem yet.

I have a couple questions to help troubleshoot.

Are you running any applications that open on wake up?

Like S2U2 or SPB mobile Shell? It could possibly be a customization or a skin change that may not agree with your device.

Have you hard reset yet and see if the problem comes back?

Could another application that was installed be causing this?

If the problem happened on a Mary ROM and on this one, I would beleive it was related to a loaded application that you guys both use. Are there any CAB files from other ROMs you may have intalled over existing applications? i.e. an Updated HTC Home, HTC Diamond apps, or any other applications you may have installed.

eyecrispy: What other "flakey things" do you notice?

Is this on Mary's ROM or on the US NIKI ROM?

Thanks guys for the information, any information helps.

Can you guys list what applications and customizations you have loaded and maybe there is a common one between the two of you causing this?

It is real hard to trouble shoot, especially if this problem hapens on another ROM that uses a completely different OS build. If you want to help troubleshoot and test, I recomend not loading applications and try either ROM for a couple days to see if problems return. If not load one app at a time and see if it causes problems before moving on to the next.

I love to help people, but I would hate to spend hours troubleshooting if it was an application outsided of the ROM that was causing this.

Thanks

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
The issues I'm seeing is on the Mary ROM. I just wanted to share that it's not just on your ROM, but another WM6.1 ROM as well. But to answer your questions, yes, I am using S2U2.

Yes, I do install my applications one at a time and test after each install.

Everything worked just fine when I was using Tom's Niki Project ROM. These started appearing after I flashed the Mary ROM.

I do plan to reflash tonight and your ROM is currently my top choice. If I still see this issue, I will go back to Tom's v1.
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Thanks eyecrispy for the info.

Tom's V1 ROM is also a WM6.1 ROM, so I don't think it would be the ROM version.

I did see that S2U2 just got another version upgrade on June 4th to v1.03. could it be from a recent release or a registry change within that application. Maybe the Tom's v1 rom used an older release of S2U2.

Hope we figure it out. thanks for the help.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
Nope. I had S2U2 v1.00 installed when I got this the first time. I then installed v1.03 (and hard reset) and things were fine for a few days ... then I got it again this morning and have been fighting it all day. Very irritating.

Yea, I'm aware that Tom's v1 ROM is also WM6.1, but it was an older build .... who knows though ...
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
In which ROM of Mary's did this happen to you?

My ROM is from a NEON300, I dont know where Tom's V1 ROM originated from, and Mary's v0.3.2 currently uses a Kaiser ROM.

Also lets see if mskovrinskie would be willing to fill us in on what apps he has loaded, and we could go from there and see if you have any simularities.

-Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
I'm running Mary v0.3.2 right now.

Midget just reported over in the Mary thread that he thinks this issue is caused by Tom's XIP, which I don't believe you're using since yours is a ported stock ROM.
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Correct, I am not using Tom's XIP,

My ROM comes from only the stock US Touch Dual ROM (NEON300) and the stock ROM "HTC P5520 WWE-ME 1.31.456.09 1.58.16.27 Shipped" provided by HTC. No other files are used from other ROM's or builds, with the exception of the s600 Touch.dll which is available in a seperate ROM. You could try testing without the s600 driver and see if that could be causing the problem, Mary's ROM uses this too.
[Touch Dual, MDA Touch Plus ROM Development] Midget_1990:
did you port the XIP? thanks.
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Yes, I ported the XIP from the NEON300
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
@mskovrinskie, did you flash this ROM with or without the S600 dll????
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
alrighty, i've flashed this ROM with the S600 patch. the funny thing is that i've still got the Mary splash screen when the device starts up.

i'll test and let you know if i get the same issue. if you want me to do anything in particular, let me know since i haven't installed anything yet.

Update: I got an error "cannot execute Tskschedule.exe" while I was setting up the device.
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
Got Black Screen of Death

Ok, I barely got started and have already gotten the Black Screen of Death twice on this ROM. The ONLY things I've done are as follows:

1. initial setup (align screen, set time, etc)

2. Use auto config to setup my data connection

3. Edit my proxy info

4. Setup my Exchange sync

5. Sync my contacts and appts via exchange

Every time my phone goes to sleep, it won't wake again without a soft reset.

I'm going to try the version without the S600 driver and see if it's any different.

UPDATE: I flashed the version of your ROM without the S600 drivers and it appeared to be working fine for the first few hours. I was installing things one at a time and testing after each install. The last thing I installed was PhoneAlarm and then left it to do something else for half an hour or so. When I came back, it was the black screen of death. So now I'm going back to the Niki Project v1 ROM so I don't have to babysit my phone all day tomorrow. I'm always happy to help test any potential fixes.
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
The ROM used was the one w/ the s600 DLL. It had been working for several days with no issues. I only installed a few apps (MobiPocket, Opera Mini, Battery Status, and synced w/ my Exchange Server which requires PIN unlock).

2 nights ago, I removed battery status and also added the following:

- SPB Pocket Plus

- SPB Mobile Shell

- SPB Phone Suite

After that, I started seing the BSOD. I did not have Mobile Shell set to start on resume from standby. I removed each SPB app, one by one, and the problem did not go away.

I still have the phone in this state if anyone wants me to check anything.
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
I also recall that I had installed Slide Actions 1.8 - http://puna.net.nz/wm6/ just prior to these issues happening, and then uninstalled it because the phone locked up on answering an incoming call.

I also noticed that the empty notification issue is back for me (right after boot and before BSOD). I had that problem with HTC builds but thought that was gone in this ROM.
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Thanks mskovrinkskie for the update,

The only common application that you guys share is batterystatus, but I don't think thats it. I thought it was the direct draw problem on S2U2 but it doesn't seem to be that either. eyecrusty says he also had this problem before coming to this ROM with Mary's too. He flashed this ROM (s600) and said he got the BSOD before doing any customization or application installs. There difference between you guys is he has a 20 Key NIKI100 and you have a 16 Key.

I will keep looking my friend.THX

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
Is Exchange ActiveSync with PIN lock a common config?
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
Yes, most corporations that allow Exchange sync will enforce a policy that requires PIN lock.
[Touch Dual, MDA Touch Plus ROM Development] Dracula72:
MMS

there is no mms setting in this rom is there any fix ?
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
To clarify, by common config, I meant is Exchange ActiveSync + PINLock common across the devices with the BSOD?
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
MMS is in the stock ROM,

its powered by ArcSoft MMS Composer 4.031.36 and if you click on Start -> Messenging, you should see the Select an Account option with SMS\MMS as one of them.

If you by passed the automatic customization when the ROM first loaded it may not have installed. Let me know if you see it there.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] badaas:
go: Start -> Settings -> Connections -> Connection Setup

and choose your provider, it will the auto dl and install
[Touch Dual, MDA Touch Plus ROM Development] darrenstone:
Hi there folks,

I flashed my Touch Dual with this ROM the day before yesterday and it's brilliant.

The previous time I did it (I think it was an earlier release) the keypad wouldn't write text, I could only use it for number entry. This time it works fine.

Just noticed one little problem with it though. Every time I press the red end call button after finishing a phone call, or after viewing my recent outgoing calls, the phone freezes up for a moment or so, then the screen goes almost completely white.

When I say almost completely, I have all the icons at the bottom of the screen for received calls, dialled calls, missed calls, etc... I don't have the "OK" button in the top corner to exit it, and the rest of the screen is blank white - even the menu bar at the bottom.

If I touch one of the other call icons, it changes to the relevant call view which will work fine. If I then press the outgoing button again, it goes back to normal and the outgoing call list is back to how it should be with the calls listed. Scrolling will work fine and the OK button comes back.

Anyone else noticed this, or is it just me???

It's not a major problem because I'm used to it now, just highlighting it as a possible bug.

Another thing I've noticed is that the video call doesn't seem to work. I called a work colleague who was set next to me to test it out, and selecting the "video call" option from the menu didn't make a blind bit of difference. We both had good 3G coverage at the time. He's using a TyTN II but don't nkow which ROM. I am unsure whether this is a bug with the ROM I'm using or the one he's using.

I haven't had chance to try and video call anyone else yet to rule out the possibility of it being my ROM, because believe it or not I don't know anyone else with a phone that is capable of video calling!

I must say again though, this ROM is probably the best I've tried up to yet. It's slow to start up, but when the phone has got its act together (after about 2 minutes of waiting) it's very fast and very responsive.

I think the s600 DLL has made a big improvement.

Keep up the good work!
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
The call history problem you are having with missing icons and the white bars has come from the Original ROM for the NIKI,

I expereinced this prior to porting this ROM. Since this ROM is a strait port, the original ROM bugs will more than likely carry over too. I still expereince this problem, I don't know how to simply fix this issue without creating a Frankenstein ROM from multiple builds and devices and potentially causing more bugs. I usually soft reset if it bothers me and it should work normal for awhile. I don't know what actions trigger it, and I am trying to find a simple solution without jepardising the integrity of the ROM.

HTC has a cab that may fix this,

I do remember seeing this on HTC e-Club downloads. I haven't tested yet. It may already be included in my build or it may not help, but I have attached it anyways if anybody wants to test it, HTC's description below. I will give it a shot too.

2/27/2008

Hot fix for abnormal Nike TouchFLO screen display and keyboard output problems

"If the TouchFLO screen display is abnormal (for example, the icons disappear, the words overlap, and so on) and the keyboard output characters are incorrect (pressing a key doesn’t result in the desired character), please download and install this fix to solve the problem."

Note: this is from the US HTC e-Club, it may effect other country's keyboard layouts. Please use at your own risk.

​

On the video calling,

I unfortunately do not have 3G in my area. I would be interested to know if it works and how well. Possibly between two devices that have my ROM to rule out another variable.

The slow boot up is the pagepool taking effect.

I don't know what the page pool is set to, but I did not change the pagepool in the port. I don't know if mactron changed it when he did his s600 version of this ROM. But you are right it does take a few minutes and then its super responsive. I hope other flashers relize this before giving up on this ROM.

Thanks for the feedback,

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] :
Hi Guys,

You guys rock! amazing!

im a real noob at this... so i got 3 quick questions...

1, is there a cab file which will install the S600 Touch.dll? ( flashing sounds reeeal hard )

2, Is the WM 6.1 comming to our touch dual or will HTC just give us the finger again?

3, is xvid movies standard resulotion running smooth?

thanks again,

Charlie
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Q.1, is there a cab file which will install the S600 Touch.dll? ( flashing sounds reeeal hard )

A1. Unfortunately not yet,

maybe in the future, but currently you have to dump your ROM and go through a process to replace it. Here is the thread if you want to do it yourself.

http://xdaforums.com/showthread.php?t=393387

Or just download a ROM that includes the s600 touch.dll and flash it. Flashing is easy, its updating your Hard SPL that allows you to flash that you need to be carefull with. Just read, understand, and follow. We all started out as noobs, and it was hard at first.

Q2, Is the WM 6.1 comming to our touch dual or will HTC just give us the finger again?

A2. There are rumors, but I wouldn't hold your breath.

There are some Touch Dual devices that HTC released that have WM6.1 but I believe all of these are NEON devices. The majority of users have NIKI devices, which are not compatible with NEON ROMs. The NIKI ROM in this thread uses the NEON ROM to acheive WM6.1

Q3, is xvid movies standard resulotion running smooth?

A3, There are alot of variables in that question.

No one has really set a standard for mobile devices, its more of range codecs balance for performance. If you want smooth it really depends on resolution, frame rate, clip length and bit rate. Though I have not tested XVID I do run WMV at 320X240 @ 30FPS at 400-600kbps at 1-2 hour clip lengths pretty smooth. every once in a while I get a studder but I don't know what to blame it on. This is also while running HTC Audio Booster.

I hope these are the answers you were looking for.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] Xyse:
Yeah, this is the only bug I encounter on this room thus far. Very good indeed. End of the day, we are back to oem roms for stablity.
[Touch Dual, MDA Touch Plus ROM Development] soldier4u:
Has anyone with the BSOD problem tried disableing the today screen timeout. I know the original touch had the same wake-up issue that can be solved that way.

The only issue Im having with this ROM is the long startup time, and Ive noticed the battery indicater is no longer on the today plugin when you touch the area of the signal strength. I have to go into settings to check my status now.

Device: NIKI100 20 Key
[Touch Dual, MDA Touch Plus ROM Development] eyecrispy:
No, I haven't tried disabling the today screen timeout. That's curious.

I am no longer running this ROM. I'm beta testing Tom's v2.1 for him.
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Startup time is related to the pagepool, once loaded it will be responsive. The battery indicator is shown when you press the time in the top bar. A bubble will pop up and the status is on the left.

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] mskovrinskie:
I actually disabled Today screen timeout last night and just started getting the BSOD this morning. Bummer...
[Touch Dual, MDA Touch Plus ROM Development] eelco_akker:
If anyone has BSOD, try this http://xdaforums.com/showthread.php?t=403779
[Touch Dual, MDA Touch Plus ROM Development] eelco_akker:
Videocall works fine, tested it with calling to a Nokia N95
[Touch Dual, MDA Touch Plus ROM Development] jcostanza4:
Thanks eelco_akker,

You seem to have a bundle of good news for me today. Even though the BSOD does not effect my personal device, I am still concerned and very glad you addressed this as a possible fix. Always looking for improvement and fixes.

Again thanks,

Jcostanza4
[Touch Dual, MDA Touch Plus ROM Development] eelco_akker:
Glad I could help.

Device works like a charm right now.

* Push Mail Exchange Server

* Dutch Xt9 (self installed)

* Pop3 account

* Bluetooth ActiveSync

All working like they should

Thanx for the great rom

Eelco
[Touch Dual, MDA Touch Plus ROM Development] i486:
Great ROM, so far 5*

So far everything works, no hangs, no errors, recomended!

Thanks for your excellent work...

;)