Related
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.
Have just sent my 3rd Vario back to T-Mobile with this fault, and think I will be getting another brand new handset back in the post, but not convinced it is fixing the fault.
When I use the phone for texting or making calls or any function, the screen appears to crash as while lines appear on one side of the screen, and slowly spread over the screen making it not respond to the touch - even if I could see what was there.
A click of the power button bring the screen back OK sometimes, but often have to do this many times or pull the battery out.
Have I just had duff handsets??
are you overclocking? when did it start? what rom, software, programs are you running? etc
bbobeckyj said:
are you overclocking? when did it start? what rom, software, programs are you running? etc
Click to expand...
Click to collapse
Alas I can only answer a few of the questions as the pone is away being repaired / swapped out, but I am not overclocking, the ROM is what it came with 3 weeks ago from T Mobile, I had installed the Skype s/ware but have not run in more than once, and it certainly was not running when this fault occurs.
The fault appears 5 or so times a day, in differing forms of severity.
I don't use skype myself, so I don't know how it runs in the background. but I think you need to overclock to get it to work well, or use the newer made-for-slow-devices version. other than that, i find sometimes i try out a new app and this problem occurs (even if others use it with no problems). I don't know if it's possible to have a combination of progs/apps which will cause this? but the fact that this is your third occurrence definitely suggests a user created fault of some sort, what other software do you use?
I use Messenger a lot on it, but apart from Skype have not installed any other software - it is all as it comes out the box.
does this happen before you install skype? try the version for ppc with slow processors
Yes it did happen before Skype, and am using the version you mentioned.
i'm only aware of this happening with extreme overclocking, and bad software. so, sorry but i'm out of ideas. when you get it back hard reset and don't install the extended rom, see if that helps, if you've not added much to it it may be a problem with the hardware (assuming they keep sending you the same unit).
I don't think many people run a stock setting and use this site, but hopefully someone else will have had a similar problem and help...
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?
Hi All
I have searched on the forums for a bit of advice on this issue, and it seems to be a WM6 problem (some comments on other xda-dev device-specific forums but none i could find on the shift).
Every so often, my shift decides not to recognise my password, and therefore i need a hard reset. Not good after i spent all the time liberating it! This has happened twice now.
On xda-dev forums for other devices, they suggest you hold the 'on-off button' for 10 seconds after setting the p/w the first time, which will work around the problem. Unfortunately, the shift doesn't have such a button for the snapvue bit.
This seems to be a WM6 issue, which is made worse for the shift given the above issues (losing liberation, no on-off workaround).
Does anyone encounter this on their shift as well? I am surprised not to see it on the forum, so i hope i didn't miss anything. By the way, the solution 'don't use password' is no good for me, since to sync with my work server i must use one - and it comes on every 15 mins maximum without use!
I am intrigued also because i have a new HTC touch dual, and this p/w problem does not happen at all?
Odd. Any thoughts? Thanks all,
Nick
Anyone there
Hi all
sorry to bump this up, but I am just wondering whether the lack of replies since I posted this the night before I went on a job for a week is because of:
a) i am the only one who experiences this and thus noone knows how to fix it
b) anyone who does know has already posted to another thread i cant find?
Sorry to bug, just wondering.
Cheers, Nick
Never had this issue in any wm6 device.
pof said:
Never had this issue in any wm6 device.
Click to expand...
Click to collapse
Same here..
Just an odd thought, are you using a long password? WinMo really only likes a 4 digit numerical PIN for password as it is a system originally designed for PDA's and enhanced for mobile phone use. Hence unlock via keypad.
Thanks
Hi guys
thanks for that, no i am using a 4 digit password.
Interesting, it seems to have stopped since i wrote the first post, have taken it away on 2 major work trips and it's all good. However, i have not liberated it again yet. I think i am going to re-liberate it and see whether the issue happens again.
There are definitely postings on some of the other forums here on xda-dev, so it is a known issue, but maybe i am just unlucky....
N
Stock Rom and 6.1.
For as long as I can remember My Sprint Touch had intermittent issues with responsiveness. After boot up everything would be great, but over time the screen would require more and more pressure to execute commands. Eventually it wouldn't even respond to tremendous pressure from the stylus. At this point I'd reboot and everything would again be normal .
A similar misbehavior afflicted my D-Pad when scrolling. After boot up everything would be great but over time D-Pad scrolling became intermittent and then stopped altogether. At this point I'd resort to the stylus. If I rebooted everything was normal again.
After much googling of different search terms I found this thread - http://ppcgeeks.com/forum.ppcgeeks/showthread.php?t=34132&page=5
My symptoms seemed similar to theirs'. I even had the occasional "startkey.exe" error upon bootup. The thread suggested a potential connection between my push email client and these problems.
I was using the Sprint "Mobile Email" app found in "programs" on my device. I understand it is an earlier version of the "SEVEN beta" client now available online.
With this in mind I uninstalled the Sprint "Mobile Email" app and am happy to report that my screen and d-pad are functioning error free and have been for a week.
I apologize if this issue has been discussed here before. If it was I couldn't find it. With this in mind I thought I'd share my experience so others might benefit.
I've learned alot here and hope this is helpful to someone.
With this problem behind me I only have one issue left to resolve...
Bluetooth Volume .