Related
Hi, I am experiancing the same problem with many WM6 ROM's, no matter which WM6 ROM i flashed on my p3600 or on any other p3600 of my friends the same problem occure.
Flashing the ROM is fine, but without any reason, suddenly i am getting the message that the pin code i am entering is wrong (even if its my actual correct pin code)
It happened to me many time on diffrent devices and with different ROM's, all with WM6.
Any one of you experts have experiaced this also and found a WORKING Solution to prevent this from happening?
Is it a WM6 problem ?
How come it does NOT happened in the P3600i WM6 ROM?
itzik-g said:
Hi, I am experiancing the same problem with many WM6 ROM's, no matter which WM6 ROM i flashed on my p3600 or on any other p3600 of my friends the same problem occure.
Flashing the ROM is fine, but without any reason, suddenly i am getting the message that the pin code i am entering is wrong (even if its my actual correct pin code)
It happened to me many time on diffrent devices and with different ROM's, all with WM6.
Any one of you experts have experiaced this also and found a WORKING Solution to prevent this from happening?
Is it a WM6 problem ?
How come it does NOT happened in the P3600i WM6 ROM?
Click to expand...
Click to collapse
Smile For prevent password dissapearing
[!] For prevent password dissapearing u should (you should make this procedure immediatly after first soft reset ):
1. Set up your connection settings (gprs, edge or wifi)
2. Open IExplorer / Set up Ineternet connection / Open some internet page
3. Click Disconnect button to close internet connection
4. Hold power button and turn off your phone
5. Power on your phone.
After that procedure your password wont dissapear. I think that you should repeat the same for mail account (set up mail account / try to send or recieve your mail / hold disconnect button / turn off your phone)
There is another problem: if you change your Owner information and you got a PIN active, the next soft reset the PIN isn't recognized making impossible to enter into the system.
My advice is to not use PIN under WM6 (until microsoft solves these problems).
I've had this problem for a long time.
If I set a pin and do a soft reset, and type in the pin, I get a wrong password error message even though I'm 100% I typed out the right PIN.
Then the only thing left to do is a hard reset.
Read from another thread, and they suggested after you set your PIN for the first time, hold on to the ON/OFF button for about 10 seconds to save your PIN properly.
I've done that for half a day now and resetted a few times already, still OK.
Fingers crossed.
joymike123 said:
I've had this problem for a long time.
If I set a pin and do a soft reset, and type in the pin, I get a wrong password error message even though I'm 100% I typed out the right PIN.
Then the only thing left to do is a hard reset.
Read from another thread, and they suggested after you set your PIN for the first time, hold on to the ON/OFF button for about 10 seconds to save your PIN properly.
I've done that for half a day now and resetted a few times already, still OK.
Fingers crossed.
Click to expand...
Click to collapse
You're quite right joymike123.
Glad you got it sorted.
Just one question: you found this thread that was last updated three months ago (so a dead issue kind of) and resurrected it by replying. Just a friendly suggestion: try to avoid this as it keeps ancient issues towards the top of the forum - making pressing current issues more difficult to find.
Other than that: good, helpful post, thanks.
why do you need to use pin? why not just turn it of? the way i see it, if my phone gets stolen or you misplace it its probably still turned on anyway. just call it up and if nobody answers just call you`re serviceprovider and ask them to kill the sim.
timmey78 said:
why do you need to use pin? why not just turn it of? the way i see it, if my phone gets stolen or you misplace it its probably still turned on anyway. just call it up and if nobody answers just call you`re serviceprovider and ask them to kill the sim.
Click to expand...
Click to collapse
it's not a thief protection. It's for unauthorized use protection. if you're in a workplace where your things are accessible by many, it can't be used by anyone else.
ok. so what we are talking about here is really the screen unlock code and not the sim pin.
joymike123 said:
I've had this problem for a long time.
Read from another thread, and they suggested after you set your PIN for the first time, hold on to the ON/OFF button for about 10 seconds to save your PIN properly.
I've done that for half a day now and resetted a few times already, still OK.
Fingers crossed.
Click to expand...
Click to collapse
i had this happened to me a couple of times, i had to do a reset and lost all my data. i have a Mac and i can't seem to sync my P3600 with Mac. now i just don't bother with the PIN until this bug has been resolved once and for all.
holding down the on/off button is a work around no doubt, but people who owns the phone don't usually assume setting a PIN would cause this headset (i.e. hard reset to re-gain access to the phone). what a pain, indeed!
Hello,
I have a strange problem with my HTC Artemis (O2 XDA branded, bought in Germany, no lock)
It behaves unstable and indeterministic.
Unstable means that it crashes/stucks or turns off.
Indeterministic means that it happens when i plugg it to charger, when i'm syncing, when a phone rings, when using applications/tomtom or just i arrive to work and i find the device off.
When it crashes or i find it off, the biggest problem is to boot the device. It takes me typically 10mins, when i'm always trying to press the power button, push the reset button or unplugg the battery for a while in random order until i bring it to work.
After first crach, the device also often crashes or stucks again during the boot process.
Once, the device was so dead, that it took me two days to bring it into bootloader mode and then i could at least flash the ROM.
All these was happening with ARTEMIS TOUCH 4.01 WWE - LITE NO CUBE.
Yesterday, i switched to ARTEMIS TOUCH 4.02 WWE - LITE NO CUBE (burned FW twice) without installing any other applications and the problems are still here
My personal feeling is that it is getting every week worser.
When i bought the device (eBay), there was original FW with Win Mobile 5 on it, i immediately flashed to ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device. So i flashed to 4.01 and this issue was away, but approx 2months ago, the above described behaviour has started and nowdays i'm fighting with it 2-3x a day.
so, can anybody help?
GiZMo
Similar here
I have a similar problem, what's really strange to me is, that as far as i can recall it started happening 2 months ago or so also!! weird huh...
my device simply reboots from time to time! even while i'm making a call.
the weird thing about these reboots is that when it comes back to live i do not have to enter my pin to enable the phone! everytime i perform a manual reboot (by software, using the pin or remove battery) i have to insert my pin to able to make a call...
i have upgraded from 3.01 full touch to 4.02 full touch about the time it started, i have now 4.02 vanilla touch but problem still occurs from time to time.
any ideas?
Im another one to join this boat!
Bought an MDA C 3, two days ago, bought of someone from gumtree.com.
Worked fine for the first hour, and then locked up - nothing on the screen, no LED. Only way to get it going was to remove battery and then press power button.
I upgraded the ROM from the original t-mob UK WM5 to mechles fine release: http://forum.xda-developers.com/showthread.php?t=371182
The lock-ups / crashes have now become rarer, on average every 4 hours (before was every 1 hour).
There is no pattern to them either, although I have saw the screen trun all corrupted just before it happens. The last one was caused when I pressed the 'start' button.
I'm on a T-Mob contract, and lost my Kaiser, got ripped of when I tryed to replace it by a tosser on here for $375 Thief on the loose thread, and was hoping my luck had changed when I bought this one!!
It is T-mob branded and I wonder if there isn't a fix on here, would T-Mob repair it under warranty??
same "issue" with no entering of PIN after reboot. But not always
GiZMoSK said:
ARTEMIS TOUCH 3.01(?) WWE - FULL WITH CUBE, i can only remember that that time I had a problem with gsm radio - from time to time i found it stucked/off - to bring it to work i had to reset the device.
Click to expand...
Click to collapse
here i found a good description of that issue:
"
Originally Posted by lasertony
I've got the same problem as !Novy, but nobody seems to have noticed his question. Are there any other guys out there with this strange problem ? I have been using this rom for a while and sometimes, without any visual warning the phone freezes up. This is particularly ennoying because there is no way to check wether it is working or not. Every other function or software keeps working ! The phone is just not receiving any calls or sms. So you can miss an entire day of calls and sms without knowing... Only when trying to call somebody the dialer says 'Dialing...' and nothing happens. No connection.
A soft reset is needed to get the phone working again.
"
btw, now i'm again trying to turn the device on, it's again stuck. grrr
Hello,
i had a few weeks ago a similar strange behaviour.
After changing the sd-card I had problems to turn the device on. After a hard reset it began to boot but hang.
The I flashed back to original O2 ROM. Then I had a unpredictable behaviour. Somtimes no sound. Sometimes I cound not be called. Sometimes Error message "no sim card". After every reset i had an other error.
Hard reset and flashing was no solution. Removing battery for less than 4 hours has no effect.
Then I wanted to send it back for repair. I took of the battery. The next day I wanted to try a last time and surprise: The device works fine without an error. Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
regards
Andre
It is Happening to my device too!!
It stucks every 2-3 hours!Tried many of the cooked ROMs but nothing.Also tried all the radio roms for 1-2 days.still the same!
It stucks with no particular reason.SOmetimes in s2u2 sometimes when am receiving a call.... etc.
Had the pin problem too for 3-4 times!
I will try your sugestion ANDRE and we will see!
Also i will try flashing the original rom,cid unlock and then flash the cood rom twice!
Fingers crosed....
Andre1210 said:
Its hard to believe, but the removal of the battery for more than 8 hours was the solution.
Now I use it for 5 weeks without a problem.
Click to expand...
Click to collapse
didn't help
happy u
now, i will try to flash back original german o2 rom
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
bricked or not?
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Vinnie1 said:
I think mine is sorted now, thanks to a new battery.
Installed it on Wednesday and hasn't died/crashed once since then.
I did notice before that the battery was getting warm, and I stuck the handset on the vent of my AC in the car, and this seemed to make the phone more stable.
Got one from Deal Extreme or try the XDA shop.
It worked for me!!
Click to expand...
Click to collapse
I thought it was a battery problem too, but I've 2 batteries and both are died in the same time? I think it's too strange...
My P3300 have this problem from when it is returned from assistence and with original firmware (without other applications).
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
GiZMoSK said:
did my device get bricked?
last friday i wanted to change firmware and during step1-cid unlocking (device should never been cid locked) pda got stucked. So i unplugged it and since then i cannot turn it on or get it into bootloader mode.
the only proof of life is when I take away battery and plugg it to power supply, then the red diod turns on and off for 1/2sec.
any idea what to do?
Click to expand...
Click to collapse
jahrami said:
dude i think u bricked ur device i am sorry to convey such a message!
now its time for CPR go to xda wiki and try the SD flashing get ur device back to life man
http://wiki.xda-developers.com/index.php?pagename=Artemis_SD_Card_Flashing
Click to expand...
Click to collapse
but i cannot get into bootloader mode so no flashing from SD card or PC
bricked device
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
GiZMoSK said:
so my device ist still dead
is there any possibility to hard flash bootloader (when corrupt)? or the only way is to change the mainboard?
Click to expand...
Click to collapse
the good sign are the leds that means you have a very good chance...the guy made the piont...check the wiki
random crashes are often caused by hardware malfunction...sometimes the connection on the motherboard stuck,get broken or make a short-circuit...so check the hardware
I was out shopping in sunny MK and something weird happened to my phone. I took it out of my pocket to check something and the screen was on the emergency pin screen, like i had tried 5 attempts to unlock the phone and failed. I entered my pin as normal, and did what i needed to, but the next time i unlocked the phone, the complete knock code/security had vanished off the phone and the it was set to swipe unlock?
Ive put the knock code security back on, but is this something that has happened to anyone before? is it something i should be worried about.
cheers
Ray
It happens anytime you try 5 times and fail. Once you put your security code in you have to reset it.
sent from my rooted lg g3 locked to tmobile
Anyone else having issues with the Pixel not waking up from sleep. This happens to me seemingly randomly, at least I have not been able to pinpoint what is causing it. I have to use the power button and volume rocker to hard reboot it. This is my second unit that has done this, and Google just wants to replace it again.
I made a quick video of it:
https://www.youtube.com/watch?v=97iho4sHAlc
I have exactly the same problem ...
to boot, I press 10 seconds repeatedly on the power button.
I already had the problem of keyboard update ...
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Ves said:
I thought this was solved but sadly it's still around. Suffered from it a few days ago after doing a factory reset about a week ago.
Click to expand...
Click to collapse
Same here, I finally received the Feb update on my replacement Pixel and thought it was solved... nope.
I bought the Pixel for quick work trips so I did not have to bring my laptop. I take allot of flights in the morning and return that afternoon/evening. The Pixel was going to be used for Presentations, and notes. It is super frustrating when I have the tablet all setup to present and I have to mess with it to get it to turn back on. This thing has way to many problems for a premium tab, and seems like Google has not dedicated the appropriate resources to supporting it (support/dev).
Ah the old "Sleep of Death" it seems to have plagued (mostly) tablets for years. I've had it happen on my Asus Transformer T101 years ago and it also happened on my Samsung Galaxy Tab S 10.5". I haven't had it happen yet in the months I've owned the Pixel, but I have had some odd issues where I press the power button to turn it on and it shows the unlocked boot warning for literally a second and then turns off/reboots, when it does that I have to hold the power button for like 10 seconds to force a reboot and then it boots up fine.
Sent from my Pixel C using Tapatalk
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
buurmas said:
I use the pattern to unlock my device. For years on my Asus TF201 (which had occasional severe performance problems), I would occasionally turn it on, get nothing for several seconds, and then get the pattern unlock screen for a fraction of a second, and then it would sleep. Sometimes if I drew the pattern really fast it would unlock it. Othertimes, I think I just rebooted it.
With the Google Pixel C, I (perhaps foolishly) continued the pattern unlock approach. It usually works fine. But occasionally, I will get the pattern unlock screen soon enough, enter the pattern, and it will do nothing for several seconds (just frozen on the pattern screen with my drawn pattern) and then go to sleep. If I try this repeatedly, sometimes once it will actually let me in. Otherwise I reboot and try again.
Click to expand...
Click to collapse
I do not use the pattern lock, I do secure it with a passcode though. My issue does not seem to be related to the security though as it does it at random times and never display the login prompt.
still having both random reboots and screen blackouts. This is a shame google will not acknowledge the problem and say they're fixing it. It only makes me believe that they know about it yet CANT fix it. Like its a hardware issue more than a software one. At least if they would say "we are aware of the issue and working on a fix" or "we were working on a fix but now working just a big OS update instead" Id feel like I wasnt ripped off by them. I mean I have EVERY nexus device box still displayed in my hobby room at my house. Im a huge fan but this is really bad.
Joined beta N program, hopefully this issue is resolved on the Pixel C.
Hi,
I have a problem with my Mi Mix 2. A couple of times I entered the wrong lock screen PIN on my phone, and every time I got a locked phone after 1 wrong try. First time it was 30 seconds, and it gradually got longer to 119 minutes last time (two weeks ago).
This evening I entered a wrong PIN again (I was too quick) and now it locked my phone for 1190 minutes!!
I know there is no way of unlocking it before this time, but is there any solution to this in the future?
I want to have as many tries as I want, or at least not lock my phone for hours...
Anyone else have this problem?
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
I hope this helps
e-merge said:
Hi,
I have a problem with my Mi Mix 2. A couple of times I entered the wrong lock screen PIN on my phone, and every time I got a locked phone after 1 wrong try. First time it was 30 seconds, and it gradually got longer to 119 minutes last time (two weeks ago).
This evening I entered a wrong PIN again (I was too quick) and now it locked my phone for 1190 minutes!!
I know there is no way of unlocking it before this time, but is there any solution to this in the future?
I want to have as many tries as I want, or at least not lock my phone for hours...
Anyone else have this problem?
Click to expand...
Click to collapse
I don't have a solution but I'm curious why you aren't using the fingerprint scanner?
nouse1981 said:
https://forum.xda-developers.com/android/software-hacking/remove-lockscreen-recovery-t3530008
I hope this helps
Click to expand...
Click to collapse
Unfortunately I haven't istalled TWRP yet.
I just want to prevent my phone from locking again after 1 wrong attempt...
Twotems said:
I don't have a solution but I'm curious why you aren't using the fingerprint scanner?
Click to expand...
Click to collapse
I usually do, but my phone was in a car holder so I used the PIN...