| 2011-03-16 04:00:01 |
Jorge Silva |
bug |
|
|
added bug |
| 2011-03-16 04:00:32 |
Jorge Silva |
summary |
Fullscreen and always on keyboard do not automatically start after rebooting |
Fullscreen switch and always-on modes do not automatically start after rebooting |
|
| 2011-03-16 04:01:12 |
Jorge Silva |
description |
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go without doing anything else, hoewever, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem |
Platform: Android 2.1
Handset: Motorola Milestone
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go without doing anything else, hoewever, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem |
|
| 2011-04-19 20:32:12 |
Jorge Silva |
nominated for series |
|
meadl/android |
|
| 2011-04-19 20:32:12 |
Jorge Silva |
bug task added |
|
meadl/android |
|
| 2011-06-05 02:55:39 |
Jorge Silva |
description |
Platform: Android 2.1
Handset: Motorola Milestone
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go without doing anything else, hoewever, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem |
Platform: Android 2.1 and 2.2.1
Handset: Motorola Milestone
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go, however, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem |
|
| 2011-06-05 02:58:24 |
Jorge Silva |
description |
Platform: Android 2.1 and 2.2.1
Handset: Motorola Milestone
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go, however, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem |
Platform: Android 2.1 and 2.2.1
Handset: Motorola Milestone
When a Tekla Shield is connected and the handset is rebooted (power off-on sequence), the shield connects automatically, the screen is unlocked, and the user is good to go, however, that is not the case with the fullscreen switch and always-on modes since the user has to unlock the phone manually before these modes kick-in.
It is very likely that the Shield is able to unlock the screen and start right away because it emulates a user input and pokes the user activity timer, so adding such method to the other modes may solve the problem
Also force-closing on startup on Android 2.2.1 |
|
| 2011-06-12 17:51:01 |
Jorge Silva |
marked as duplicate |
|
792997 |
|
| 2011-06-19 03:07:46 |
Jorge Silva |
meadl/android: milestone |
|
0.4.3-alpha |
|
