Elfin/Touch Slowdown? - Touch GSM General

After working fine for several months with a TMO UK WM6.1 image my Elfin started malfunctioning a few days ago.
This manifests itself in an excruciating slowdown in starting new programs or switching from one program to another.
Has anyone come across something like this before and can advise me what solutions to pursue?
Regards,
Wolf

Related

My Magician freezes

Hello all,
last week I got my new HTC Magician, here in Austria so called "T-Mobile MDA Compact". Unfortunately I have the problem, that my device freezes from time to time (at least 1 time a day). This happens most of the time when using the T-Mobile IntelliDialer, but sometimes it happens even when I do not use the device at all.
When the problem occurs, I am not able to make or receive a call, the upper status LED is gone as well (no signal, no blinking).
When I got the device I had ROM 1.13 installed, but after I heard that maybe this could cause the problems, I installed version 1.12 from T-Mobile site, but still have the same problems.
Now I am really out of ideas, don't know what to do. It seems I am not the only one with this problem, so I am afraid it hase no sense to switch the device with a new one @ a T-Mobile shop. Or do you guys have a "good", normal running Magician w/o this bug?
Thanks in advance for your help!
Greetings, Matthias
Helle again,
As you've got the same problems on rom 1.12 & 1.13 and you got it just for a week I'd say go back and get another one. There are people with simular issues and I guess there are much more users without it, like myself.
So my advice use your warrenty, make a backup of your contacts etc. first with sprite (trial version is available) or AS or whatever, saves you a lot of times. I won't restore the apps just reinstall, maybe it is some combination of a faulty program & with a backup you get that back as well. And it gives you the chance to determine, if possible, what's causing the freeze.
Good luck, M
ok, then thanks again
Today I made a ROM update @ T-Mobile. If that did not the trick (I will look for errors the next days), then I will use my warranty and change the device itself. I hope they don't send it to technical support somewhere, but give me another one instead...
Greetings and thanks for your infos, Matthias
haimat said:
Hello all,
last week I got my new HTC Magician, here in Austria so called "T-Mobile MDA Compact". Unfortunately I have the problem, that my device freezes from time to time (at least 1 time a day). This happens most of the time when using the T-Mobile IntelliDialer, but sometimes it happens even when I do not use the device at all.
When the problem occurs, I am not able to make or receive a call, the upper status LED is gone as well (no signal, no blinking).
When I got the device I had ROM 1.13 installed, but after I heard that maybe this could cause the problems, I installed version 1.12 from T-Mobile site, but still have the same problems.
Now I am really out of ideas, don't know what to do. It seems I am not the only one with this problem, so I am afraid it hase no sense to switch the device with a new one @ a T-Mobile shop. Or do you guys have a "good", normal running Magician w/o this bug?
Thanks in advance for your help!
Greetings, Matthias
Click to expand...
Click to collapse
Hi,
I have been using my Magician for almost 8-9 months .. moving from ROM version 1.11 to 1.13 WWE BigStorage (radio 1.11 to 1.13 as well).Recently (last 1mth or so) I start to notice that I have a strange problem similiar to you, my 'radio' would 'hang' where I cannot receive or make calls, can't even receive or send SMS. However, my signal (the top bar signal strengh) will still work. This is really fustrating .. because the PDA still works, I won't know when my Magician 'hangs' ... (at least until I try to send SMS or make a call).
I've downgraded to Radio 1.11 & ROM 1.11 ... I'm still facing this problem, but not as often (sometime once in 2 days). The strange thing is that my wife who is using a Magician as well, is facing the same problem (symptom arrise almost the same time together). Both our phone used to be fine.
So far, no luck trying to locate the source of the problem, and I don't think both our magician's hardware got screwed at the same time ... I have a feeling, it has something to do with GPRS ... gut feel ... but cannot confirm.
Anyone face this problem and managed to solve it, I would appreciate any pointers ... Many thanks!
Note : I don't install additional ROM software such as CallerID, etc ... I only use intellidialer.
Hello, you could be right with your GPRS feeling, I have it as well...
Is the LED of your device blinking, when you have one of these freezes?
Hi guys,
Don't know if this gets you on the right track, but a few months ago I had major memory problems with my magician. Thought it was a virus, probably was one or two today plug-ins that consumed all of my memory very rapidly. Think of plug-ins like OO journalbar. Didn't look at the led blinking I just soft-reseted to solved the prob. for a few minutes. Very inconvenience when you're navigating in a car.
Since I ditched these plug-ins eveything is fine, tried them afterwards of course & noticed the memory leaks.
When you're not using anything like those apps. it must be something else. Maybe there's something on the forum.
Cheers, M
I thought about some apps or plugins as problem source too, so I refreshed my device without installing any additional app to it -- no success. So I still have these hangups, even if I have no tool installed...
Sounds like really s..tty problem.
Does the use of gprs or phone functionalities make any difference? what happens when you skip the ext-rom installation (hard-reset & soft-reset just before the customization kicks in) & go for basic WM2003, without all the TMO apps&branding?
M
... tried this allready, but without any difference, device freezes serveral times a day. I would say it's a hardware fault, can't think of another problem source.
Yesterday I spoke with a T-Mobile tech @ T-Mobile support. He told me, he is not aware of this problem and he always had "good" devices. And he updated my ROM to latest version...
Since I still have the problem, I will change my device now and see if this makes any difference!
haimat,
I think exchanging your magician is the best option, the techi might be right in saying he only encountered good ones. Haven't found much error reports like yours, so the rest must be good (look at the bright side). Hope you can trade it directly without any hassle & enjoy your magician for the rest of it's lifetime.
Found some people with a universal with simular probs. didn't read all posts though there were so many. So can't tell you how it ended, it's about a JasJas that hangs and hangs and ...
In the meantime good luck with the change of your device.
Cheers, M

Universal is perfect, third-party apps cause the problems

At this forum and at others I have been told the following by Universal users:
- The Universal is the most stable WM device to date
- All the faults reported are caused by poor WM5 third-party apps
I must say having used many many Palm OS and Symbian devices I have never seen third-party apps cause as many problems as those posted here.
What do you think? Should WM protect the main OS functions from faulty third-party apps?
Some of you might get annoyed that I am grinding over the same problem over and over again i.e. the SMS freezing problem.
However after I had sold my 1st Jasjar due to the SMS freezing problem and got a second brand new unit, I was specially sensitive to this issue and so thoroughly tested it right out of the box without installing any 3rd party software. And there it was !!! It froze again. This was followed by several hard resets and even changing the ROM to that of the XDA but to no avail.
I am wondering if various issues being reported with the Universal are really related to 3rd party software or is it a problem of WM5. Maybe some are but others definitely not.
Kind Regards
@srmz,
I had the same problem with my JJ and I replaced it with an XDA Exec, which was okay until I re-intalled the ROM!
I am annoyed that many people here believe we don't have problems or we are so incompetent that we must be causing the problems to occur. My issue is that if we don't accept there are problems and report them they will never get fixed!
srmz said:
Some of you might get annoyed that I am grinding over the same problem over and over again i.e. the SMS freezing problem.
However after I had sold my 1st Jasjar due to the SMS freezing problem and got a second brand new unit, I was specially sensitive to this issue and so thoroughly tested it right out of the box without installing any 3rd party software. And there it was !!! It froze again. This was followed by several hard resets and even changing the ROM to that of the XDA but to no avail.
I am wondering if various issues being reported with the Universal are really related to 3rd party software or is it a problem of WM5. Maybe some are but others definitely not.
Kind Regards
Click to expand...
Click to collapse
:idea:
I’ve been reading about this SMS freezing on various forums and luckily I don’t have that kind of problem, but here is a hint: what about the SIM card of your operator? Did you try changing that one? Since you have done all possible things to resolve the problem I don’t think that it will be a problem for you to try another SIM, no? At least I would have done that…
Please let me know if this was of any help…
Thanks Zormic for your concern and suggestion.
I have already tried SIM from two operators than the one I normally use. I therefore believe this is not operator related.
Thanks and Kind Regards
srmz said:
Thanks Zormic for your concern and suggestion.
I have already tried SIM from two operators than the one I normally use. I therefore believe this is not operator related.
Thanks and Kind Regards
Click to expand...
Click to collapse
I don't think anyone has said that WM5 is COMPLETELY bug-free? Surely no-one would be bold enough to make such a statement!?!
However, certainly in my experience this is the most stable PPC I've ever owned. I sympathise with your SMS problem, but as I and many others have never experienced this, I'm afraid that a) I'm completely stumped for a fix, as you've already tried what I would suggest, and b) I doubt if this is an inherant WM5 problem, it's possibly due to some ExtROM add-in?
(Of course, it may actually be a bug in WM5 that only occurs in certain circumstances....useless, aren't I!? )
@sub69
no has said that WM5 is bug free, but lots of posters here and elsewhere claim that the problems users are reporting are to do with third-party apps. My point is this cannot be the case for all faults and we should look elsewhere for the source of problems. For example, as I have said before my Exec was stable (let me repeat, stable) until I was foolish enough to use the O2 ROM. So my Exec was less stable because I stopped using the factory shipped ROM. This should start to give us a hint - for example.
Also many users have reoported poor quality of the camera unit (dead pixels), well my camera app caused my unit to overheat if I left it running. A pattern emerges...the cheap camera hardware perhaps?
try this...
sorry for my por english...
i had the same sms freezing probleme on my qtek V1640 (SFR's version of the 9000)
then i read this post and i try...
http://forum.xda-developers.com/viewtopic.php?p=193215#193215
i don't know exactly why, but it works fine now, since i install spb and is plug in today... no more freeze!
about the third party apps, i think that the operators's plug in today is not optimize for this machine... the 9000 is perfect, WM5 is not so bad, but the pluging is bad...
@dojparis
but old JJ was SIM free and it did freeze on SMS receipt so can't be an operator plug-in
And thanks for the tip
and the other possibility is that its not WM5 and its a universal hardware problem ....
This is due to 3 party software, in case you don't know, your Exec or Jasjar is using a highly customized version of rom which is not original or as clean as dopod900. Thats explain why dopod900 is way more stable than Exec/Jasjar. O2/I-mate might have messed up the rom.
In fact, my friend's Dopod900 and my running perfectly well without any problem that you all mentioned here.

Number buttons only do numbers during a phone call

Whenever I'm on a call I can't take notes because the the buttons that have numbers on them only do numbers during a call, no matter what application I am in. I've tried it with numlock on and I still can't type letters. Does anyone know a way around this? I'm using a black rom, does it do this on the official one? I would really like to be able to take notes during a call.
Noticed this on WM6
Which version of WM are you using? The keyboard on my Cingular 8525 with WM5 functioned normally, even during a phone calls. But the problem you described surfaced when I upgraded my 8525 to the leaked WM6 ROM on this website.
I'm hoping that when AT&T releases their official 8525 WM6 ROM upgrade that this problem is corrected.
I'm using Black Satin
I've got the same deal going on here with my WM6 Cingular USA official version...reg edit in the works?
Hey just to confirm on this issue, I have the exact same problem with when I recently upgraded to WM5 to Schaps_WM6Pro_WWE_3.57a_Full.
I also hope there is a fix for it, cause WM6 looks pretty good. Unfortunately I probably won't see WM6 from Rogers any time soon.
got the same problem with my softbank X01HTC w/ WM6.
Don't have this problem with Imate Jasjam using WM6 Black 2.5 rom
same problem here ... can anyone point me in the right direction? How about a reg dump from a working ROM? I'll do the diff if someone provides the data
There are a number of threads on this topic already. No one has yet to find a solution and some of the brightest minds are working on it. I am not one of those minds, however, I compared the registry dumps from during a call and not during a call and saw nothing that would make a difference. I would suggest "subscribing" to this thread (and the other ones to be safe) so that when someone posts an answer you will get an email. Unfourtunatly, you will also get an email when someone post "Me Too!", or even when someone is just being grumpy about the "Me Too"s.
Me too!
T-Mo 3.60 ROM has the same issue on my 8525... anyone find differently?
This has been the standard since Windows Mobile 2003. so people have been complaining about this since the Blue Angel days. The phone application that comes with WM takes control of the keyboard when there is an active call.
Using a different phone application is likely the only fix. Since most of you hate the phone application that comes with Windows, this shouldn't be heartcrushing for too many people. Which phone applications don't force this behavior? I have no idea, but I'm sure someone can let us know.
Of course, you can still use the onscreen keyboard when on a call which doesn't have this issue. I know this is painful for those of you who are morally opposed to using the stylus, though. To me, having the keyboard extended while on a call is awkward at best.
I'm not sure why this became such an active issue all of a sudden when the problem (or feature) has been around ever since the very first WM phone with a keyboard on it first appeared, although I think this is a nice indication that these devices are finally starting to catch on with new people.
You must be a very slow typer. It's a huge issue. I've ROM'ed my HTC Wizard & Hermes many times and have only had this problem with the WM6 image ... while i'm with you on it not being specific to the image or WM6, i don't agree that it's not important.
If you're saying a new phone app will fix it, i'm all about it but don't downplay the issue because it doesn't bother you.
Doom Tints said:
This has been the standard since Windows Mobile 2003. so people have been complaining about this since the Blue Angel days. The phone application that comes with WM takes control of the keyboard when there is an active call.
...
I'm not sure why this became such an active issue all of a sudden when the problem (or feature) has been around ever since the very first WM phone with a keyboard on it first appeared, although I think this is a nice indication that these devices are finally starting to catch on with new people.
Click to expand...
Click to collapse
It is a huge issue because with WM5 on my 8125 and on my 8525 this was NOT a problem. The letters worked as they were supposed to even during a call. It only began when I switched to to WM6. So WM6 broke something.
I didn't say this is a non-issue. But what I am saying is that this problem has been around for years.
It's possible that something from WM2003 was changed in WM2005, but made its way back into WM2006. I don't recall the problem on WM2005 on the Hermes, but I do recall it from earlier phones. But I also wasn't looking for the problem, either, and I don't generally text or do other typing when on phone calls.
Right on, has anyone found any more information about this problem?
Best I can tell it came in with all of the latest WM6 builds. Anything I've tried that's been labeled "official" or that is based on same has had the issue. I can say with certainty AT&T's WM5 didn't, nor did vp3G 2.0 (which was based on a pre-"official" build).
Beyond that, no clue.
eventually it'll get fixed.. what im really having issues now is overeating.. last night i had my phone plugged into the wall and was talking via bluetooth for about an hour and a half and my phone was extremely hot and had stopped charging.. i wish there was a fix for that and really am hoping i didn't buy a lemon 8525
ericc191 said:
eventually it'll get fixed..
Click to expand...
Click to collapse
Well, with the official TyTN ROMs having been released that way I'm beginning to have my doubts.
Does this work with the official AT&T WM6 rom? Anyone? Bueller?

How many soft resets/day do I have to accept?

I'm using a t-mobile MDA Vario II for two weeks now.
- Serial HT640...
- ROM Version 3.60.111.4
- Radio Version 1.50.00.00
(official German t-mobile WM6 update, no individual software so far)
I had to soft reset 3-5 times a day. Frozen display in different situations, during a call, when working with WM6 apps and even if the MDA was in standby. Therefore I had t-mobile replace the unit. They sent me an already updated replacement (serial HT638...) with the same ROM. I'm using this one two days now but the situation hasn't improved at all.
I just can't imagine that this is the way it should be. Are there any similar experiences? Will a cooked ROM improve the reliability? Do I have to use another Radio version?
Thanks for your help and greetings from Germany,
Andre
I soft reset roughly once every four or five days maybe? Usually cos I have installed something or uninstalled it.
My Vario 2 locks up when using TomTom6. Initially I did a soft reset to get it going again but I then found that pressing the OK button (on the side) took me back to the Today screen, I could then tap the TomTom symbol and hey-presto it's back working again. Have you tried this?
Dave
I used to have to reset my Vario 2 about 4 times a day with the original T-Mobile WM5 ROM on it as it kept freezing. That was one of the main reasons why I tried the WM6 ROMs when they came out on here. Since I started installing the ROMS from here, I'm down to maybe one every couple of months. I haven't tried the official WM6 ROMs, as I'm perfectly happy with the custom ones.
My advice, spend a couple of days playing with Matt_K's Pandora kitchen. It's ridiculously stable, and you can set it up exactly as you like it without any of the stuff you never use!
Thanks, gonna try this. Andre
Andre_K said:
I'm using a t-mobile MDA Vario II for two weeks now.
- Serial HT640...
- ROM Version 3.60.111.4
- Radio Version 1.50.00.00
(official German t-mobile WM6 update, no individual software so far)
I had to soft reset 3-5 times a day. Frozen display in different situations, during a call, when working with WM6 apps and even if the MDA was in standby. Therefore I had t-mobile replace the unit. They sent me an already updated replacement (serial HT638...) with the same ROM. I'm using this one two days now but the situation hasn't improved at all.
I just can't imagine that this is the way it should be. Are there any similar experiences? Will a cooked ROM improve the reliability? Do I have to use another Radio version?
Thanks for your help and greetings from Germany,
Andre
Click to expand...
Click to collapse
Also if you are running WM5 and in some WM6 situations see here:
http://forum.xda-developers.com/showpost.php?p=1078848&postcount=2
Mike

Samsung Saga 6.5??

No love for the Saga??
I love it... and check for news about once every two weeks. Haven't heard anything.
hello fellow IL person... im hoping for a 6.5 cooked rom
note... I posted a message over on PDAPhoneHome.com and everythingwm.com and then found this thread... since it is similar in nature to my questions, I thought I would reply to this one instead of starting a new thread.
Greetings fellow frustrated Saga owners!
Wish I hadn't updated…
I, like many of you, now wish that I had not installed the update on my Saga.
It worked great before!... But now I am experiencing many of the same bugs that have already been mentioned on this forum.
I am pretty tolerant of bugs in general and I don't mind trying to find workarounds for them. Often, the workarounds add more functionality then would normally be there anyway… Plus I enjoy learning how things work.
Biggest problem…
The one thing that I can't stand is the loss of signal strength I have seen since updating! My data connection dies several times per day and I have to soft reset to get it back. Sometimes it is hours before I realize this has happened so I am not always getting my email right away. (Who has time to check their phone every few minutes to see if it has stopped synching or not?)
Other times it seems like it just stops synching for no reason. I use both an exchange server (MailStreet) and Windows Live and they both have this problem. Sometimes I check my phone when I go on break at Noon and I will notice that it hasn't synched since 9:30 AM or sometimes longer than that, yet there is no error message (like it tried to synch and couldn't) and I open the browser and can get on the internet. It is like it doesn't even try to synch. I have both of them set to synch every 15 minutes (greatly increases battery life btw) 24 hours a day. Then there are other times, it synchs more often than every 15 minutes… so I don't know what is going on!
Getting worse?…
Is it just me or do the signal issues seem to be getting worse? Or maybe it is just in my area? This past week I have actually started getting errors saying that it couldn't connect (whereas before, it just wouldn't connect... no errors)... and it seems to be happening more frequently.
Finally… my question…
What I would like to know is if anyone is working on a "cooked" ROM for the Saga. Either 6.1 or 6.5 would work for me. I have heard some good things about 6.5 (like dramatically increased performance), but I haven't heard about anyone working on this for the Saga. Waiting for Verizon to come out with another update is just a lesson in frustration and honestly I am not sure I would trust it if they did release one.
I consider myself to be a pretty tech savvy person and even enjoy some light programming on occasion (the .net framework is awesome… Something Microsoft got right!!), yet I am reasonably certain that cooking up my own ROM is beyond my skills (though I am willing to give it a shot if someone can point me to a clear guide)
Follow-up question…
If no one is working on this and no helpful guide is available, then I am wondering if a ROM from a similar phone can be used (maybe with a few modifications required?). For instance, is the Epix similar enough that we could use a ROM designed for it on the Saga? (There is a 6.5 ROM for the Epix that can be found here) Or does the fact that its hardware is GSM only make it out of the question?
More questions…
If using a ROM from a similar phone is possible is there a way to backup the current ROM so that it could be restored if the other ROM doesn't work? If so then I would probably be willing to use my phone as a guinea pig. Yes, I understand that there is a possibility that it could brick my phone and I am willing to accept the risk if there is a good chance that it will work. I have an old blackberry that I can use if something goes really wrong.
So I guess the real question is… How similar do the phones have to be? Or does it have to be identical hardware?
Any insight would be appreciated...
Steven
Id like to know the same answers! The Omnia, which came out at the same time will be upgradable to 6.5, so why did samsung release a phone that wont be at the same time as one that could?
i wonder if an omnia rom could be altered for the samsung?
Lets see some love for the Saga with 6.5, also any news on the Sags 2?
Revisiting old thread
I've still got a brand new Saga that I'd love to use if I could get a stable build of 6.1 or 6.5. The "update" from Verizon made the Saga useless with its instability and constant lock-ups.
I would really appreciate some of the experts here building a clean ROM for the Saga.
Thanks.

Categories

Resources