View Single Post
Posts: 875 | Thanked: 918 times | Joined on Sep 2010
#169
asui failed to start after installation
Known problem, ASUI does start/restart after installation/upgrade but then appman stops it for some reason. You can see this by enabling the start_visible setting. It however works fine when installed or upgraded from the console.

Locking the device only locks the screen. Hardware qwerty-keyboard still works, power button still opens asui, long press of back button still closes active application.
I was only able to reproduce with the screen locked but still on, it only happens when its on right? If so, I will look into fixing it.

Power button to 'unlock' is a feature!

SSH widget doesn't recognise dropbear as SSH server.
What is the name of the init.d file that starts dropbear, what is the full path to the server binary and what is the full name of a client process (do they start with "sshd: ")?

IMO locking the device through UI should hide asui.
This is already on the list, I'll bump it up.