![]() |
2011-12-16
, 19:42
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#32
|
3) There is no any small length limit for security code, so it can be qwertyuiopasdfghjklzxcvbnm... Twice or triple. Even 200 characters are ok.
5) Devicelock 'Numpad' view is a standard feature available on any N9, just enter lock code which contains numbers (0123456789) only (locked device will look similar to PIN query, for example).
It is not possible to switch to full VKB qwerty mode as it is not needed here.
![]() |
2011-12-16
, 21:31
|
|
Posts: 301 |
Thanked: 227 times |
Joined on Nov 2009
@ Turkey
|
#33
|
![]() |
2011-12-17
, 04:18
|
Posts: 12 |
Thanked: 13 times |
Joined on Nov 2011
@ Tampere Finland
|
#34
|
Once alphanumeric and once numeric. The device lock requires the input of security code.
![]() |
2011-12-17
, 04:47
|
Posts: 12 |
Thanked: 13 times |
Joined on Nov 2011
@ Tampere Finland
|
#35
|
The Following User Says Thank You to mdn For This Useful Post: | ||
![]() |
2011-12-17
, 15:46
|
|
Posts: 4,118 |
Thanked: 8,901 times |
Joined on Aug 2010
@ Ruhrgebiet, Germany
|
#36
|
Devicelock on N9 has 2 different UIs:
1) with own 'Numpad' like PIN query
2) with VKB.
It is not possible to switch between them when device is locked.
![]() |
2011-12-17
, 15:58
|
Posts: 57 |
Thanked: 31 times |
Joined on Dec 2009
@ Denmark
|
#37
|
Hi mdn,
I do not own a N9 (and probably never will). So pls excuse me for asking such "dumb" question again.
You have two different UIs, thats understood. But:
one is alphanumeric VKB (when you enter/confirm the security code)
and the other is numeric-only numpad (when you have to unlock).
This is quite confusing/annoying/buggy...
![]() |
2011-12-17
, 16:05
|
Posts: 57 |
Thanked: 31 times |
Joined on Dec 2009
@ Denmark
|
#38
|
Well I can't understand why this issue is such a blocker for N9 users. It happened to me once on my N950, but on N9 you can easily get your security code back, by using Nemesis Service Suite. (Section 308 Key 5) It somehow doesn't work for N950, but I can confirm it myself it works on N9.
Then you can set your device "non provisionable" on MfE and disable devicelock timeout.
![]() |
2011-12-20
, 11:51
|
Posts: 12 |
Thanked: 13 times |
Joined on Nov 2011
@ Tampere Finland
|
#39
|
But:
one is alphanumeric VKB (when you enter/confirm the security code)
and the other is numeric-only numpad (when you have to unlock).
This is quite confusing/annoying/buggy...
The Following User Says Thank You to mdn For This Useful Post: | ||
![]() |
2011-12-20
, 11:54
|
Posts: 12 |
Thanked: 13 times |
Joined on Nov 2011
@ Tampere Finland
|
#40
|
but on N9 you can easily get your security code back, by using Nemesis Service Suite. (Section 308 Key 5) It somehow doesn't work for N950, but I can confirm it myself it works on N9.
The Following User Says Thank You to mdn For This Useful Post: | ||
I did set up a T&P account some months ago, and I did remember the pin - there was no question about it, because I used it to login to T&P's site online. I tried that code on the phone, - but with no luck either.
I can tell you that I also tried the T&P locate, lock (not wipe!) from their site - and although I know the service sent my phone an sms with the commands (I know because I tried it with my SIM-card in another phone) there was no reaction on that by the N9 either.
My idea was that if I could lock it from T&P's homepage, I might also be able to unlock it - but no such luck.
Btw I had PR 1.1 installed...
I think the problem has actually got something to do with the Mail for Exchange, since it happened right after I changed my MfE server. Therefore I posted in this thread, http://talk.maemo.org/showthread.php...91#post1138391 to make Sergey aware of the problem, as suggested by Jalyst a little further up...