Fullscreen switch and always-on modes do not automatically start after rebooting

Bug #735901 reported by Jorge Silva
This bug report is a duplicate of:  Bug #792997: Tekla force-closes on reboot. Edit Remove
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Tecla Access
Status tracked in Android
Android
New
Low
Jorge Silva

Bug 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

Also force-closing on startup on Android 2.2.1

summary: - Fullscreen and always on keyboard do not automatically start after
+ Fullscreen switch and always-on modes do not automatically start after
rebooting
description: updated
description: updated
description: updated
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.