Database Users

HTC TyTN (HTC Hermes 300) very slow and sluggish

Hi there,
I'm new to this forum - and new to the whole Windows Mobile idea as I'm normally an avid Apple fan but I do make an exception when it comes to the phone as the iPhone (as of yet) is quite 'useless' when it comes functionality and flexibility compared to a Windows Mobile device.
In either case, I've recently flashed my MDA Vario II and, after having used Black Satin for a day or two, put on Schap's 3.60a WM6 ROM. The only reason i did not like Satin was that it combined the inbox/outbox for MMS and SMS messages (knowing my luck I'm sure there would have been an easy way around that).
Right, ever since I put on the WM6 ROM and installed a few other applications, such as Spb's Mobile Shell, Spb Weather, etc etc the phone seems to be incredibly sluggish and slow. I did a full re-set and then installed one application at a time to see if it has something to do with a particular bit of software. But I don't think that's the case as the phone acts pretty slow even with nothing installed after the hard re-set. But now, after a few days, it takes, for example, around 15seconds to show the Windows directory using either File Explorer or Resco's explorer. The start-up progress, especially the transition from the Splash Screen to the standard Home Screen is incredibly slow and happens in stages. It then takes about another 30 seconds for the keypad to come up, asking for my PIN.
I've been running all sorts of utilities such as MemMaid, PocketMechanic and SKTools to make sure that the device is in 'mint' condition but, if at all, this made little change to the overall speed.
I expected the phone to run slightly slower under WM6 compared to WM5 as, strictly speaking, the TyTN, as I understand it, was not designed with WM6 in mind - which may be the reason why a lot of providers here in the UK do not offer a WM6 upgrade. However, the phone has become uncomfortably slow and sluggish so is there any way to speed it up or is this a known issue with WM6 on the TyTN?
Also, not sure this is the right forum for this but I also tried to set up Direct Push and it works fine - only problem I have is that it does not seem to support WiFi (it does when I check manually but as soon as I utilise the Direct Push function, the phone insists to connect to the 3G network). Now this is not necessarily a big problem as I've got an unlimited data plan but when at home I am using WiFi and there is little point in having both switched on, WiFi and the Data Connection as that does drain the battery. Again, any ideas to solve this would be appreciated
Thank you guys

Hello mate,
Not sure why you are having the problems you are having. Anyway I run Schaps on my Tytn (see my sig), together with SPB products without any problems at all. The whole lot is rock solid.
My suggestion would be that you re-flash your device with the combination of ROM and Radio that I use, given I have confirmed no issues. If that works then you have at least proved your device is ok. If it doesn't work then your problem lies elsewhere, probably with the device.
Strong advice - make absolutely sure you have done all the things and taken all the precautions outlined in Mr Vanx's excellent guides (see here http://www.mrvanx.org/cms/)
I will track this thread to see how you get on.
Cheers
WB

Hello there...
How was your device under Satin? I am running Satin on an 8525, and it runs ok. Black Satin is also a WM6 rom. I am running HTC home, pocket breeze and iLauncher. SPB tends to let it slower, but not that slow for sure.
I suggest you read through the specific thread of Schaps 3.60. I am not sure, but i once read a few posts, and if i recall correctly, there were some problems with the version. Either that or 3.57... don't know for sure.
I also suggest re-flashing with a different rom. Or, read through the Satin thread here at XDA-devs or at 4winmobile, and there might be a fix for the mms/sms thingy. Then go back to Satin. There is also the Black X going on, but I think it is still beta...
Just don't forget to follow Mr. Vanx precautions, specially installing HardSPL v7, if you don't want a bricked device.
Let us know how it goes

Hey there,
Thanx for replying. I have been thinking about re-flashing the ROM but to see if that helps. I have been playing with the phone a lot so I may have somehow done something which I shouldn't have - whatever that may be :S
Can I ask ... in your sig you state that the 1.50 Radio is very buggy - what are the issues with it, cos I am using that one and was wondering if that could possibly be related to it?

Thanx for the replies guys. I've decided to re-flash the ROM and, it seems to be working fine again. I actually think the phone works slightly faster now as it did under the T-Mobile WM5 ROM. I haven't updated the Radio and stuck to 1.50 as I've read somewhere that it's working fine for the UK (lemme know if I'm wrong - they say there would be a noticable improvement in 3G reception, but I haven't seen that, but I dont seem to have any major issues with 1.50)
So, fingers crossed the phone won't slow down again - which I guess it shouldn't and I'll be careful what I install on it, making sure I have the latest versions of everything.
Thanx again for all your suggestions

Flipside,
Radio 1.50 caused me loads of problems; dropped calls, not being able to make a call for no reason, people not being able to reach me even though the phone was on and in an excellent signal area, having to reboot to get the radio to switch on, etc, etc.
Have not looked back since i went to 1.47. The lesson learnt for me was not to jump at the latest radio rom, just because its the latest. Latest does not necessarily mean best for ones particular circumstances.
Cheers
WB

Qtek Newest official ROM bug? Icons white out, app won't run, after 10 hrs running.

Hardware: Dopod 818Pro
ROM: Qtek S200, 2.20.7.34 World Wide English, Date:7/10/06, Radio: 02.47.21, ExtROM:2.20.7.114
Software Installed: E-Sword 3.01 (Bible Software), Mapking 2007, Select-Radio, MobiPocket
How's the problem happened:
After Hard Reset, simply install above software, and start the 10 hrs test by launching E-Sword, Mapking and Select Radio, keep the radio playing, by sharing Internet connection through USB to PC.
10 hrs later, or around, you will possibly find either,
a. some icons "white out", not able to run by clicking on them, if you do click, they will give you a program is not certificated, or something like that being mentioned at other threads.
b. Today Screen lost some lines.
c. System may hang later.
IMHO,
1. It looks rather like the GDI resource running out in win98 system.
2. The originally seemed random error now can be repeated by above procedure, time related, always around 10 hrs.
3. Not to specific software, any above software can cause the same problem, just choose SelectRadio as example, since it also test the network connection.
Anybody experience the same problem and any suggestion? It's not a big one, however, annoying when you need to keep running something.
It would be very grateful if somebody can offer me a suggestion on the cause or how to debug it.

J install this rom
J Have problem with:
Today Screen lost icon
Keyboard don't work etc...
The best rom WM5 for Prophet is : JAMin_WWE_213923_2139123_022021 ( ftp://ftp.clubimate.com/JAMin_WWE_213923_2139123_022021_ship.zip )

leszekcce said:
J install this rom
J Have problem with:
Today Screen lost icon
Keyboard don't work etc...
The best rom WM5 for Prophet is : JAMin_WWE_213923_2139123_022021 ( ftp://ftp.clubimate.com/JAMin_WWE_213923_2139123_022021_ship.zip )
Click to expand...
Click to collapse
Bro, with all my grateful heart, i would like to ask you for one favor. Could you pls be more specific on your PDA phone hardware (Dopod, or Qtek) and how long after your phone on did that happen? A clean installation?
I had pinned down the problem to my Home Screen Plugin from HTC, due to possible memory leak or heap corruption.
Now i upgrade to Korand's WM6 ROM without problem.
May still want to know the cause of problem to avoid it in the future.
Anyway, i will still download your suggested ROM for dissection...to see the difference. Thanks.

[RELEASE]HTC-BlueAngel 6.5 5.2.21176WWE2CX3.1 by sun_dream

Seems sun_dream found yet another build, hes saying is pretty fast, i cant wait till he releases it, heres the link to his blog post
edit:heres a mirror thx to homam_france

He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!

I hope the shell won't distort the OK and X Buttons anymore

egzthunder1 said:
He has sent me a beta, which I will be testing sometime between today and tomorrow. I will post some feedback on this. Stay tuned!
Click to expand...
Click to collapse
Great, I just installed Xplode's R3. But i want to try it too.
egzthunder1 can i test it too?

i better get my BA fix up ASAP, the hardware buttons are not so responsive, it seems I am going to be busy flashing

Well,
Day 1 after flashing sun_dream's latest. So far, very fast and stable. Here are the main points (in my opinion anyways)
*Titanium seems a lot more responsive than before (I still don't like it though )
*The removal of windows and menus animations make the device respond faster overall.
*Unbelievably responsive kinetic scrolling.
*The honeycomb is actually usable now!!
*Settings were put back into categories (Personal, System, Communications).
*Battery life seems good, no major drainage.
*"OK and X" bug fixed and working fine!!
*Wifi nice and steady (still need to test PIE8 and Iris Browser).
*Transparent Top bar looks awfully nice! (too bad the programs replace it with the Black bar)
Things I did notice were as follows:
*The Wifi icon seems to be getting cut off from the bottom down. In other words, you can only see half of the icon.
*Power in the Power Settings doesn't show a percentage anymore.
I still need to do some further testing (e-mail setup, etc), but overall this rom is superb!
Will report back later.
Good Job Sun!!!!!

he sent me a beta too but got a big problem...my cradle ain't working anymore!

red_hanks said:
he sent me a beta too but got a big problem...my cradle ain't working anymore!
Click to expand...
Click to collapse
You can always use mtty and flash via SD.

hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....

red_hanks said:
hey Egz...I'd like to try that but I need my cradle so I need to go to a local phone store first thing tomorrow. I tried to fix the cradle myself but ended ruining it more so how is the 2117x build vs xplode's r3? 21169 x2 is so buggy so I flashed my BA back to wm6.1....
Click to expand...
Click to collapse
I havent' had a chance to test xplode's R3, but sun's is a very nice rom (so far anyways). I still have to test BT (headset and GPS).
One thing I did notice also, is that it seems that data transfer via AS is a lot faster than in previous builds... I guess M$ finally did something right
You can read the rest of my review in my previoius post. Good luck with your craddle situation

A little further testing...
*I purposely soft reset the device and it took approximately 1 minute to wake up completely and loading PointUI Home 2. So, it has a very fast wake up time!!
*I set up my g-mail account with no problem.
*I don't use SMS, so I cannot test that.
*Lock application seems a bit faster and more responsive than in older builds.
*PIE is a bit faster, but I still have other browsers that I like to use. I will test YouTube later (with both PIE and Iris).
Left to do...
*Test BT connection with headset, and GPS (Pharos BT receiver).
*Test IR/BT data transfer... (I have to find another BT and another IR enabled device to do this)
*Must finish going through the settings to ensure that they all work.
Will do more later...

ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...

red_hanks said:
ok seems like 2117x is a lot stable vs the older wm6.5 builds..waiting for your BT test result...
Click to expand...
Click to collapse
BT = Bluetooth?
if so, it's always a trouble-maker

i found strange issue with lockscreen, when you have locked your device and pressed power (entered standby) and recieve a call the answer lockscreen part does not show upon device resume, this bug does not happen when device is locked and not on standby - you may try the scenario yourself, i think that this bug is present in 21169 too (no matter sun or my roms)
tested various rom configurations, rebuilded about 20 times this rom, but this nasty bug stays

as of now I am very contented with wm6.1 v3.02 by sun_dream. I need to use my BA so I think I will just wait for a more stable build of wm6.5

Well, I tested (tried to pair really), my GPS receiver, but no dice... For some reason, the device either looses connection or just flat out does not recognize the pass-code. The BT headset, on the other hand hasn't given me too much trouble. It paired up nicely...
@xplode,
I'll give it a shot, but I don't normally use my BA as a phone (unless I am traveling)... which I will do on Monday, so I'll let you know then.
Still stable and no SR so far, except for one time when I was using wifi and my device went into power saving mode (turned off the screen) and afterwards, it would only have a black screen... had to SR there. I tried to recreate the situation on a few occasions with no luck... I guess it was a one time thing.
More reports to come..

well i had the same thing today, blackscreen - only fixed with hard reset
soft reset gets me back to the black screen

This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.

if we just talk about it, Microhell can't do something about it... now if we link to it here DIRECTLY, then xda-developers is in Trouble.

April 1 said:
This appears to be a secret and private talks thread
Why are others kept in dark about the build 2117x? Once its disclosed that such a build exists, every one gets interested in trying it. If there is a reason for keeping it hidden from others for the time being, better use private messages. Just my two cents.
Click to expand...
Click to collapse
@April 1,
The reason is rather simple. If you release something that has bugs and things (something you would consider a pre-release), you will have an enormous amount of people asking the same questions over and over and over and over.... and over again (kinda like it is right now but worse).
It is a lot easier to develop something when the beta testers are finding all the minor things and not hitting themselves on the face with major bugs that might require hard resets and stuff.
We are not trying to keep anyone in the dark (that is why we are reviewing this build), but sun_dream will release it when he deems it is ready for public use. So far, he has not made mistakes (at least not many) in his ability to judge when a rom is suitable for release.
Just be patient... this should be out soon

Upgrade to Cooked ROM or wait for Official ROM??

Hi all,
Just after some advice. I bought a HTC HD2 when they were first launched. I upgraded the phone to 1.66 via a goldcard method (? the turkish release that came out). Since then the phone has not been upgraded. My wife is the main user and is still expriencing intemittent problems with the phone. Main ones being--
1- The Proximity sensor doesn't work that well. When on calls she sends random DTMF or hangs up on the caller. Seems to be her cheek on the keypad. I tried a screen lock app (name?)- but that caused other problems with the unlock intermitently not working.
2- If I enable HDSPA high speed comms it sometimes locks her SMS outbox
3- When composing SMS, it sometime locks so you can't compose. You have to wait quite a few seconds before trying again.
4- Other minor niggles.
When the phones works ok- it's very good. When the bugs kick in she wants to launch it thru the window. It's mostly used for business hence the need for reliable operation.
Anyway is it worth waiting for HTC to come out with official Ver 2.x software, whenever that might be. Or should in pick a ROM from the Development page and load that and hope??
Please advise!

Hi there,
Entirely up to you whether you upgrade, but I upgraded from 1.61 to a 2.01 Rom (Miri's) and the phone has performed faster, is more stable & includes additional features.
It was the first time I ever installed a cooked ROM, and I'd do the same again!
Regards,
Dan.

Critical reboots bug while using A2DP [play/pause bug]

Hello! I would like to draw your attention to very annoying bug for all users, who uses Stereo Bluetooth Headsets (A2DP BT Headphones) with Mango and later versions of WP7.
The bug appears if your headset is connected & you are using zune to listen music via A2DP. You need to start track, listen sometime and then pause (never mind which way you use to pause - hardware buttons on headset or tap the pause button in zune or lock screen.
If you wait some time (minute or two) and then resume playback, the phone will freeze and after 5-6 secs reboots. This bug does not appear if you don't use A2DP/Bluetooth headset for listening. So it is Zune or bluetooth stack/radio combination bug, but it is very-very annoying.
Today I flashed about 20 different ROMs and discovered, when the bug appeared.
I flashed oldest ROMs since NODO. This bug appeared after first Mango ROM out. In NODO and PRE-MANGO (Green Mango) ROMs everything works properly. (Tried DFTs NODO & Green Mango ROMs (7392 and 7592 builds).
The radio version for 7392 and 7592, which works properly (without this bug) is: 5.51.09.29_22.32.50.10U (A.102.0.D4)
I hope this info will help ROM developers and DFT Team to fix this distressing bug.
Thank you very much!!!
Added some summary stats about Windows Phone builds:
BUG EXISTS:
7740 [Ultrafruit Based, almost all ROMs at the moment], 8107
A2DP WORKS PROPERLY (BUG DOESN'T APPEAR):
8779 [POST-TANGO by ansar] - BUG FIXED
7720/7740 [which based on Green Mango drivers, NOT Ultrafruit, I found only HD2O_WP7_1.25_LEO71_7740 from HD2Owner]
7592 [Green Mango from DFT]
7390 [NoDo]

It will be interesting to test this bug on first Mango ROMs, which were based on NON-Ultrafruit contents (builds 7720 for example, HD2O`s earlier ROM or any else).
This is ROM is not based on Ultrafruit and there is some probability that A2DP works OK there. I am downloading and flashing it right now and I`ll post the testing results here later.
UPD: my estimates about the problem is connected to Ultrafruit base have been confirmed! I've found a mango rom without this bug (I flashed HD2O_WP7_1.25_LEO71_7740 ROM, that is last version of HD2O Mango ROM NOT BASED ON ULTRAFRUIT)

Very nice of you to bring to the attention of the devs to this critical bug. A lot of us use bluetooth devices and this bug renders the device useless.
How about Ansar's rom? Have you tried it? The first versions i tried were ok bluetooth-wise and it is 8107 i reckon. It suffers from various other problems though and v6 i tried had reboot problems due to Cottula's touch drivers propably. Ansar states he has implemented most drivers from htc titan.
Good luck to all of us that want a fully working phone

[/COLOR]UPD: my estimates about the problem is connected to Ultrafruit base have been confirmed! I've found a mango rom without this bug (I flashed HD2O_WP7_1.25_LEO71_7740 ROM, that is last version of HD2O Mango ROM NOT BASED ON ULTRAFRUIT)[/QUOTE]
Was 1.26 based on ultrafruit??????

Yuki-xbmod rom works without an issue also, with all updates up to 8107 and SP1 drivers too. I test it for 2 weeks and you can use Bluetooth as you will and it will never freeze or reboot.But it has no fullunlock so is quite limited for testing purposes
It's a pity xbmod has abandon this beautiful rom, lots of work wasted. I don't think HD2O's project is similar to any ways.... so sad

indeed, yuki xbox rom has worked fine, this all started when ultrafruit came about and people started using it as a base.
whats slightly more frustrating is that when ever this gets brought up in the approperate threads for each rom it gets ignored.
I was just about to do a new thread similar to this so thank you for doing this.
fair enough if the developers do not use BT for this and thus dont have the problem but perhaps a prudent course of action would be to communicate with us to see if we can narrow down what is going wrong... say the word an ill bend over backwards to help!

alyn99 said:
Was 1.26 based on ultrafruit??????
Click to expand...
Click to collapse
My mistake, 1.26 is also not based on ultrafruit, but the next version and later versions are already based on Ultrafruit. Today Cotulla answered in his twitter, that the next ultrafruit ROM will be based on Schubert drivers and this bug seems to be fixed.

dark.angel said:
My mistake, 1.26 is also not based on ultrafruit, but the next version and later versions are already based on Ultrafruit. Today Cotulla answered in his twitter, that the next ultrafruit ROM will be based on Schubert drivers and this bug seems to be fixed.
Click to expand...
Click to collapse
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. This Bt and low incall issue has frustrated me so much that I bought an HTC Titan today and will just be using the WP7 as a backup until things get sorted.

alyn99 said:
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. This Bt and low incall issue has frustrated me so much that I bought an HTC Titan today and will just be using the WP7 as a backup until things get sorted.
Click to expand...
Click to collapse
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
The Titan is also a nice device...but please don't backslide ;-)

alyn99 said:
Thanks for clarifying. I guess we'll have to wait for a working rom and use the old ones until then. T
Click to expand...
Click to collapse
TitusO said:
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
Click to expand...
Click to collapse
Yes, I think this bug will be fixed soon. The most important thing is that we know where it appears and the developers (firstly Cotulla) confirmed that they are working on it now
Let's hope and say thanks to developers! I think the WP7 rom will be fully usable and perfect in the nearest time.

TitusO said:
I really appreciate, that you've tested the almost every ROM for the BT-Bug and reported this. I'm with you and for me this funktion ist also necessary. I'd say a little more patience and the new WP7 ROMs will be good.
The Titan is also a nice device...but please don't backslide ;-)
Click to expand...
Click to collapse
Actually, the Titan is a bit of a problem for me now as I realized on Tmobile US it won't do 3G, otherwise I like the phone. So I am bouncing back and forth between HD20's V1.26 on the HD2 and the Titan. In so many ways I like the HD2 better - ability to run 32gb memory, etc. Just curious as this is first time I tried V1.26 - so far it is AMAZING rom - bluetooth rock solid, sound perfect, incall volume perfect - what is wrong with the V1.26 rom and why did all the devs feel the need to "upgrade" the newer roms and thereby disable bluetooth functionality and incall volume?? I just don't get it. Newer is not always better.
HD20s V1.26 gives me 8107 Mango and I can't see any feature difference between it and all the newer roms, what am I missing?????
Edit: Only bummer so far on V1.26 is that I can't do a backup - certs missing error message.

At least the bug has been fixed in Post-Mango builds, don't know about earlier ROM's (I was using Android ICS) but I confirm, that ansar`s Post-Mango ROM works with Bluetooth A2DP perfectly!