Notices

Again something that won't work if you have a non-hacked 770.

Won't work on an iMac either.

BTW: Karel, did you get your N800 fixed?

Har har har. How full of wit.
Who knows? It's in Nokia's hands now and consequently I don't expect it back for another six months at least.

Thankls very much for this. Maybe Alpha but it works for me. If you get time,can I ask for two possible options
!. Full Time Display?
Full time Display only when on AC Charging Option
That would be great
Take Care and Thanks again

emjayes,

I installed it as well, and it's so close to perfect already. I am truly astonished that a simple little request turned into reality in 24 hrs. The members of this forum are truly amazing, including yourself.

I have my display to turn off automatically after two minutes, and dim after 30 seconds. When I push the power button, it shows the clock and date for five seconds, then goes to home screen until the pre-defined display time turns it off. This works great for me, but a perfect app in my mind as well would be as quoted above if you decide to continue work on this.

Thanks again for the hard work, and lightning fast results. I can't wait for more iterations of this app!

joe

I've noticed that an update (0.1.1-alpha) has left my IT frozen at an 'installing' prompt. I had to reset it. FYI

oh oh. Now during the reboot it stopped at 'rescuing software update'. Never saw that before. But it seemed to reboot again on it's own & come up ok. lockedclock still shows 0.1-alpha installed. wew! won't be trying that again soon.

I got the same thing with 0.1.1 alpha. It hung during installation, so I aborted the process and reset the tablet. I too got the rescue software message, and now the application 0.1-alpha is showing corrupt, and it is uninstallable! How do I remove this broken app from my tablet now? Anyone? Thanks,

joe

I gained root access, and tried to manually remove the program, here is what I got:

/home/user # apt-get remove lockedclock
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
python2.5-pyinotify libfribidi0
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED:
lockedclock
0 upgraded, 0 newly installed, 1 to remove and 23 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 1049kB disk space will be freed.
Do you want to continue [Y/n]? y
dpkg: error processing lockedclock (--remove):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
Errors were encountered while processing:
lockedclock
E: Sub-process /usr/bin/dpkg returned an error code (1)

So then I did this:

/home/user # apt-get autoremove lockedclock
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
python2.5-pyinotify libfribidi0
The following packages will be REMOVED:
libfribidi0 lockedclock
python2.5-pyinotify
0 upgraded, 0 newly installed, 3 to remove and 23 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 1266kB disk space will be freed.
Do you want to continue [Y/n]? y
dpkg: error processing lockedclock (--remove):
Package is in a very bad inconsistent state - you should
reinstall it before attempting a removal.
(Reading database ... 18343 files and directories currently installed.)
Removing libfribidi0 ...
Removing python2.5-pyinotify ...
Errors were encountered while processing:
lockedclock
E: Sub-process /usr/bin/dpkg returned an error code (1)

I have quickly reached the threshold of my very limited root and code expertise, meanin non-existant. Some help would be appreciated

OK, scratch the above two request...I figured it out. I had to actually install from root, then uninstall in root to get the application off the device. Here's a tip for the books, don't interrupt either installing or uninstalling apps. Bad things can happen. Still doesn't make any sense why the 0.1.1-alpha release hung up like that though.

Joe