WM6 Password issue - Shift General

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

Related

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?

Dropping signal registry fix??

Hey there, I was going through the old posts and saw a reference to a registry fix for the wizard dropping signal and taking forever to reaquire it even in places that the signal is excellent. The person left a link to the fix but when I go the site is down. Is there anyone here that knows what this registry fix is, and how I can go about implementing it? This would be my first experience with playing with the registry on my phone, but I"m pretty versed in messing with the registry on the desktop. This has been something that has bothered me since the day I got the phone and T-mobile doesn't even recognize it as a problem. Thanks for your help, here is the original thread that I read about the tweak from: http://forum.xda-developers.com/showthread.php?t=375864
Specifically this person's response: While my first instinct is to convince you to sell me your otherwise functioning phone on the cheap, I must resort to being the good guy (or else get spanked by the mods...)
There is a registry fix for the kind of signal dropping you're describing. I'm surprised you went for so long without experiencing the problem. I did almost right away when I got mine last year. You should try it first, if you haven't already...
I think this is the one I used:
http://www.pocketpctweaks.com/pocket...fix_drop_calls
Reply With Quote
I thought that writing looked familiar.
Try this: http://www.netmotionwireless.com/support/technotes/2208.aspx
It may not be addressing the exact problem you're having, but then again, it might...
Obviously, if you've upgraded your phone to WM 6.x, you need to take this problem up with the one who created that ROM, and hope they feel like supporting you. That's the fun of using home-cooked ROMs.
[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\RIL]
“GPRSStallWorkaround”=dword:0
Try this, FIRST!

Touch display serious problem!

Ho all,
I am having a serious problem with touch display alligning. It happened two times, on resuming it from stand by, touch screen lost its configuration. So that display becomes unusable becouse finger touch doesn't have a correct corrispondance. I had to restart device to have it working again.
Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/
kozm0naut said:
Have you installed any custom ROMs? If not...
You'll want to contact HTC as this sounds like it may be a hardware issue. http://www.htc.com/www/support/nexusone/
Click to expand...
Click to collapse
No, I still haven't rooted it. It's with stock rom. HW problem? I wish in a SW issue..
I've seen this issue crop up on my rooted N1 as well. A reboot fixes it, as does waiting it out. For some reason I seem to notice it happening when I'm in the browser. There's a thread here about it (which evidently I can't link to since I'm new). Check the second page of the general section, the subject is "touch screen issues".
Seems like a software issue to me, but who knows.
The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.
uansari1 said:
The first thing to do if you have these types of obvious software issues is a hard reset (Settings>Privacy>Factory Reset). If that doesn't work, then it's time to call HTC.
Click to expand...
Click to collapse
Thank you all! I found the post where this is being discussed.
This is an issue many people are experiencing on google support forums, in fact it is the second longest thread after the 3g issues. It has also finally been pinned. Here is the link: http://www.google.com/support/forum/p/android/thread?tid=04134c63c784258e&hl=en#all
Anyone experiencing the same problem please post in that thread, the more people that post the more chance for google to acknowledge this and remedy.
BTW I also experince issues with the touch screen which happen quite randomly and can normally be cleared with a power on/off. When the screen goes bad the touch is no longer registered in the correct spot on the screen.

Problems with my hd2 - Help Please

So basically, my hd2 is not running smooth at all. Every time i do a rom update and then restore my contacts/messages/settings it keeps getting frozen and unresponsive. So I have to restart the device, but I don't know why it should be restarted anyway, isn't is kind of super fast?!?! So, now, when I recently updated my ROM, the device is so damn slow, that even after typing my PIN it takes a minute to launch htc sense and everything. When I'm moving through the tabs it's so damn laggy i can't stand it. . Is anyone else experiencing this????
To be honest, and I'm no expert, it sounds like you have some serious phone problems, probably out of your control. Not to sound like a pessimist but given how everyone else seems to be ok with the HD2, could be either a major rom/radio problem or hardware failure??
I've updated my hd2 using the official rom from HTC and, apart from the occasional lag i get from WinMo, my device runs sweet as a a proverbial nut. Especially as I have run the tweaks suggested by the forums here.
Given that you have said that you've upgraded the ROM and it's made no difference, the only thing i could suggest is possibly send it back under warranty?
Obviously, I'd wait and see if someone with more know-how has a better explanation, i'm merely giving you my POV.
Hope you get this sorted ASAP. A properly working HD2 is a marvellous thing.
All the best
To the OP,
There could be so many causes for your problems. I would start as follows:
- Take your SD card out and see if the phone boots and is not laggy with the card out
- If this does not work take a look at the SMS threads on here and see if the solutions there help you
- If no joy then read the Hints @ Tips thread on here, if you have not already done so, and pickup on the cache move tips, using the task manager to close open files, etc
- I that fails look for the thread "HD2 Died - or did it" and implement the solutions in there
- If that does not help and you have been flashing a fair few roms then hop over to the MTTY thread in rom development and see if that helps.
Plenty to be getting on with.
Hope you get it sorted.
WB
My power up to sense loaded time = 55 secs.
Any different?
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
[^IcEmAn^] said:
thanks for this quick reply. I am using Energy Leo ROM, but I don't think this could be the problem, or is it? Because I have performed a hard-reset now and it's running quite smooth again.. But the question is for how long.
Two questions I have now:
-does it happen to anyone, when you try to wake up the phone, screen doesn't wake up, only the keys in the bottom start to glow? It happened to me from time to time
-does anyone else experience missed key taps? When I tap something from time to time it just doesn't get recognized so I have to "retap" it...
Click to expand...
Click to collapse
I have experienced question 1 and 2.. however not alot or not frequent.. I tend to think that this is just a computer and computers do crash depending on whats going on.. The missed screen taps only happens once or twice when its playing up. I do have a screen protector on though so whether the dust, oil or screen protector is causing that is a different story, but isnt a big problem for me to remove the screen protector to find out.
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time). As said before, I'm using energy rom, latest issue (17.2.). Could the problem be, in fact connected with this rom or specifically with sms software?
using cooked roms you can generally expect a few lockups and restarts.
Also, the screen not powering up, just the hard keys backlight is an issue across the board, from custom roms to official roms. Some roms seem to do it, some don't, but one that doesn't do it to me might well do it to you.
[^IcEmAn^] said:
so, the latest problem.. my hd2 had been running for ~16 hours without any problem now, but in last 10 minutes i had to restart it twice, because the screen stopped responding after i wanted to type new sms in a conversation (first time) and after i had a pop-up message about new sms (second time).
Click to expand...
Click to collapse
It has been mentioned before that if you have a large number of texts stored, it will take a while for it to allow you to reply to a text. (It has to go through the database, check for the texts sent by the user, then arrange them alongside the ones sent to them by you, then put them in chronological order, then display them, this takes time)
but i would presume the device should be working anyway (but slower, of course) and not flashing the display and being "frozen" ?
The frozen issue with texts is all in the SMS thread I pointed you to earlier. Solutions to the phone freezing are in the HD2 Died thread, again as I pointed out earlier.
How many of these potential solutions have you tried? Tryy these things first then come back if they don't work rather than make assumptions about your ROM.
WB
after 3 months i still have the issue with missed strokes.. even after the latest energy rom update :\
anyone?

Omnia 7 and Answering

Anyone have any idea how to solve "delay in MIC" after answering? Delay is about 1 second. When I press Answer and say Hello, person on the other side didn't hear what I said, I have to say again... Some first calls I didn't know is it something with my phone or network, or caller...
Regards from Dubrovnik
I have the same problem...
Funnily but that seems to happen to me all the time but I didn't really register it until you posted it on here.
Maybe It's because I rarely use it to make voice calls but I always find myself having to say "Hello, Hello" as they never hear the first hello.
Guys, I'm happy now... I'm not alone
Dejo, hvala
Same problem here ? Do you think its hardware or software related ?
Same thing here.
I find myself waiting a second or two before saying hello or i get exactly as described.
Anyone knows who, MS or Samsung, and where would be best to ask about this problem ?
Noticed the same problem!
S1eepy said:
Anyone knows who, MS or Samsung, and where would be best to ask about this problem ?
Click to expand...
Click to collapse
Samsung. If it's not being reported for other phones, then it's likely not the OS itself.
same problem.
Now I wait 1 second before speak...
Same. Wife explained it to me a while back after I got pissed off at her for not talking after I answered. haha
I was surprised today as I answered the phone and said hello straight away and got a reply - I was actually heard.
I am not sure If this was due to upgrading to the newest rom - including the firmware.
I've noticed this as well (JK1 firmware)
Cool, that's good news Let's hope it'll be included in a subsequent official Zune-distributed release
This happened to me also, but since upgrading to the I8700XXKC1 XXKB2 firmware it seems to have been resolved. (It's also resolved the issue of the notification sounds occasionally 'breaking' - I haven't seen that mentioned anywahere else.
Thanks for the feedback. Sorry I didn't quite follow the upgrade procedure. Is it possible to flash the firmware without erasing all the user data?
Unfortunately not, but almost all data on the phone is cloud based or can by synced via zune anyway. You'll just need to connect to your accounts and reinstall all your apps again (which is the biggest pain about the process).

Categories

Resources