Database Users

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.

activesync slowing down/freezing device | replog eating cpu

While syncing my phone via USB (using either USB settings) my phone slows to the point where most calls don't even have a chance to ring on the phone before going to VM.
The only thing i'm syncing now is Exchange (2003 SP2) Contacts/Calendar/E-mail
replog.exe seems to be the one eating all the CPU.
It seems to be the worst when saying "Looking for changes", but even when it says synchronized and appears idle, it can still run the PDA into the ground.
I've experienced this problem with Black Dymond and now a flavour of LVSW.
I'm missing at least 5 calls/day (that I know of) because of this! HELP!

I have seen this with all versions of WM6 that I have tried. At first I thought it was something to do with the fact the earlier WM6 ROMs were beta versions and therefore there was probably debug code in them, but not any more. I'd be interested in a solution for this as well.
John

johnburn said:
I have seen this with all versions of WM6 that I have tried. At first I thought it was something to do with the fact the earlier WM6 ROMs were beta versions and therefore there was probably debug code in them, but not any more. I'd be interested in a solution for this as well.
John
Click to expand...
Click to collapse
aww.. CRAP!
Just to confirm, does WM5 have this problem? I'd like Exchange 07 and Office 2007 support, but not at this price.

Oo that's useful to know - I've been mooting a WM6 upgrade for my handset for a while now, but I'll definitely steer clear because I sync daily!

christopherwoods said:
Oo that's useful to know - I've been mooting a WM6 upgrade for my handset for a while now, but I'll definitely steer clear because I sync daily!
Click to expand...
Click to collapse
If you're syncing OTA, it works fine. But I have a couple things that don't sync OTA so I'd like to keep it docked while at the office.

j0dan said:
aww.. CRAP!
Just to confirm, does WM5 have this problem? I'd like Exchange 07 and Office 2007 support, but not at this price.
Click to expand...
Click to collapse
I can't remember! Brain's not what it used to be. I don't believe so...
John

johnburn said:
I can't remember! Brain's not what it used to be. I don't believe so...
John
Click to expand...
Click to collapse
i swear it's getting worse. is anyone else having this problem?
John: do you use Pocket Informant and PlanPlus by any chance?

j0dan said:
i swear it's getting worse. is anyone else having this problem?
John: do you use Pocket Informant and PlanPlus by any chance?
Click to expand...
Click to collapse
Yes for Pocket Informant, no for PlanPlus.
John

This has to be fixable. I just had the problem go away for about 2 days. That's not to say it synced properly, but it didn't kill the phone!

I also have the same problem with sync. I am using ACT Link for Pocket PC though and thought it could be that. I removed it and tried but the same problem, is slows down and sometimes just locks up. The only way I make it work is to SR before I sync and just wait it out.
Using Shadow currently but it appears in all ROMs I have tried so far.

Problem solved in latest ROMs???
This weekend I upgraded my TyTN to Sleuth255's 5.2.1238_17913.0.3.0_v1.0 ROM and guess what? The problem has gone away! So either something The Amazing Sleuth did in his ROM fixed it, or the problem has been fixed by M$ in the latest ROMs.
John

Maybe not...
OK, I might have spoken too soon. The slowness did return a couple of times this afternoon, but it definitely still seems to be happening less with this new build.
John

johnburn said:
OK, I might have spoken too soon. The slowness did return a couple of times this afternoon, but it definitely still seems to be happening less with this new build.
John
Click to expand...
Click to collapse
Lol. My ActiveSync woes have gone away for the last 2 days. I disabled PlanPlus for activesync, but I'm still missing plenty of calls because my device takes 2 full rings to turn on and start ringing itself.

WM6 Password issue

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

[Q] g sensor android nand

hi, ive used android on my hd2 pretty much since day one,
ive never been able to get the g-sensor to work in android. i dont get freezes or anything at all it just simply doesnt work, ive tried all sorts i was hoping nand would fix it for me but it doesnt can anyone be kind enough to offer me any solutions?
it works fine in windows mobile so its definatly related to android
ive tried loads of builds and most kernals still nothing, ive tried scripts to disable and re enable and nothing im totally mythed :/

Sorry for bump
Sent from my HTC HD2 using Tapatalk

Are you still using SD?, if so try calibrating with it upside down, screen facing down.

I'm running NAND, when I go to caliberate the bubbles don't move at all, until I press caliberate then the just move left and right and it says complete.
....
Sent from my HTC HD2 using Tapatalk

Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.

oddly I got it to calibrate with the phone on its side, facing sideways. IT rotated ok afterwards but then got stuck. Best thing to do here is not to calibrate at all as it seems to work fine without any calibration - too late once you have done it though?

pvdw50 said:
Hi, I allready posted this problem a while ago. I hoped this was a problem with windows mobile occupying the G-sensor, while running android from SD. I was happy to see that we finally could boot to android and skip WM, but still no G-sensor in android. Is there someone who knows the commands (in Gscript) for starting the G-sensor? I allready tried renaming the akmd file but this is only a solution for someone who has a working G-sensor and wants it disabled temporarily.
Please help a handfull of us G-sensorless android users.
Thanks.
Click to expand...
Click to collapse
I can't find the script but all it does is renames the akmd file to stop and start. Your the only person I've found with the same problem we need to figure this out man
Sent from my HTC HD2 using Tapatalk

There's 2 more topics on this for a while now, but there's no luck on a solution. The biggest problem we all have is likely the fact that anyone reading a G-sensor thread is having the same problems. The one with the solution isnt looking for our threads.

solution - working for me
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem

Spartn said:
it works properly without any calibration, but if you already did it, here is the solution:
calibrate it with upside down - screen facing down, it will resolve your problem
Click to expand...
Click to collapse
Did it already, it seems there maintains a hardware differences in every HD2, some of can work properly, some of like us can not. Hope that the dev. who also has this problems can work this out.

i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~

有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论

朋友,你也是重力出了问题吗?

Just keep subscribed to this post and we'll find something eventually

i hope so~~~~~~~~~

hen_43 said:
i got this problem too!!!
and i already try many different way try to fix it out
but it still does not working!!!!
i guess the problem is the device of our gsensor hareware different form the others!
sorry for my poor english
if someone can read it,i want to say!!!!!
help me~~~~~~~~~~~~~~
Click to expand...
Click to collapse
It looks like so, but it works in WM, so it may be HARDWARE DIFFERENCE let the drivers cause issues? I must talk about, I have never calibrated g-sensor after flashing NAND ROM.
hen_43 said:
有中国人是同样的问题吗?我是Tmo版的~~~有的加我QQ385334026讨论
Click to expand...
Click to collapse
hen_43 said:
朋友,你也是重力出了问题吗?
Click to expand...
Click to collapse
Please use English on this forum, thank you.
whynot66 said:
Just keep subscribed to this post and we'll find something eventually
Click to expand...
Click to collapse
Hope that we can eventually find something useful.

ye~~i try but my english is poor
BTW,,i hope we'll find something eventuallye,too

seem like no one can solve this problemT_T

honestly this solution didn't help me - first time, i calibrate my HD2 facing down about 3 times, and finally 3rd shot was done successfully

So your g works?
Me and others in this thread have no g at all baby caliberate as the g sensor doesn't work at all :-/ please can some one help

[HELP] DHD wakes up by itself

Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!

I've a similar problem a bunch of months ago, my phone turn on automatically, without no logic. I've resolved the problem pulling out the battery for a night, after that the problem disappeared.
I hope that will help you to resolve your problem,
Rodomar705

Thanks, I will try that out tonight and report!

Ok, I tried it out last night, but it did not work
Does anybody have a different idea?

Dabarr said:
Ok, I tried it out last night, but it did not work
Does anybody have a different idea?
Click to expand...
Click to collapse
Did you check the date and time once you'd insert battery inside DHD? I think to solve the problem that way, you should leave DHD without battery until the internal battery will be totally discharged. It takes approx. 12-14 hours, and you can be sure only if turning on DHD you'll find time and date set to 12:00am, 1st jan 1980 (or something like that).

Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^

Dabarr said:
Hey,
I have a major problem for a couple of weeks now. My phone just keeps waking up randomly and turns the screen on by itself. I have root and s-off and tried out a few roms. Sense Roms as well as MIUI roms... It does not make a difference at all, so I guess it can't be rom related. I have read a few more posts on the web of users having a similar problem but there was no solution given anywhere.
Also, my speaker automatically turns on when I receive or make a call. These two problems seem interconnected since there is at least one person on xda having exactly the same two issues...
Does anybody have an idea or a solution for this? I would be thankful for any kind of help! Thank you in advance!!!
Click to expand...
Click to collapse
same here, i have the MIUI ROM, will try with another version.

Dabarr said:
Yeah, it definately worked though, time was resetted as well. I turned it in today, hope to be able to pick it up next week. Before, I ran the Ruu to set it back to shipping condition... It still had the same error, so it is definately not rom related...
It is a huge drag without it... Already feeling uncomfortable ^^
Click to expand...
Click to collapse
Sorry mate!! Just wait for a week, ist not so long time, and you'll get back your phone as new as when you bought first time!! Hope this makes you feel a little bit of joy!!

Ok, I have gotten my phone back on thursday (after one week)...
SO far so good, everything worked again, they even set the proximity sensor right again... Then I rerooted it and put another MIUI on it...
On friday then, I put Vipermod back in and undervolted it by 50 mA... BOOM, the issue came back, I couldn't remove it, so I took the battery out and waited for 12 hours, as you suggested... and it worked... Issue was gone... Then I ran vipermod again and BOOM the issue was there again... It didn't even help to set the mA values back to normal, I had to reset it again by taking out the battery for 12 hours.
So my conclusion is that this issue is directly related to the actual USE (not just the installation) of vipermod... Can anyone confirm? Don't want to put out false information in the vipermod thread without having others to confirm...

need help also

Stinger696 said:
need help also
Click to expand...
Click to collapse
have you tried pulling out the battery already?

xlxl said:
same here, i have the MIUI ROM, will try with another version.
Click to expand...
Click to collapse
As I have stated before: Rom change haven't helped me.. Did it work for you ???

Dabarr said:
As I have stated before: Rom change haven't helped me.. Did it work for you ???
Click to expand...
Click to collapse
If changing the ROM didn't help then it is an app issue. One of your apps is causing it. Time to look deeper

I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).

freakshock said:
I have exactly the same issue! Also with the speaker sometimes. Really annoying. If an app is causing it, how can we find out which one? I'm using ARHD 6.1.0, but I've had the issue with older versions of the ROM too (with the same apps installed).
Click to expand...
Click to collapse
Only way to find out is to test them one by one by reinstalling them one at a time