Notices


Reply
Thread Tools
Posts: 76 | Thanked: 35 times | Joined on Nov 2007 @ Seattle
#21
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
 
Posts: 397 | Thanked: 99 times | Joined on Jun 2008 @ Toronto, Ontario
#22
I also had a failed install, and got the "Rescuing Software Update". Is there any option of what to do during a installation that seems to hang? I left it sit for a while with nothing happening, is the best course of action to just wait it out?

I was able to uninstall with no problems though.
 
Posts: 397 | Thanked: 99 times | Joined on Jun 2008 @ Toronto, Ontario
#23
I also had a failed install, and got the "Rescuing Software Update". Is there any option of what to do during a installation that seems to hang? I left it sit for a while with nothing happening, is the best course of action to just wait it out?

I was able to uninstall with no problems though.
 
YoDude's Avatar
Posts: 2,869 | Thanked: 1,784 times | Joined on Feb 2007 @ Po' Bo'. PA
#24
Mine installed without a hitch on an N800 Diablo and works as advertised.
However, it does add the "extras-development" repository to the catalog during the install process. After installation your tablet may show that certain upgrades for other apps are available. -DO NOT UPGRADE THESE APPS- (unless you know why.)

Instead, disable the "extras-development" repository and these upgrade notices will go away.
 
jmjanzen's Avatar
Posts: 192 | Thanked: 60 times | Joined on Sep 2008 @ Wichita, KS
#25
Originally Posted by Nelson L. Squeeko View Post
Basically it would be nice to go blank screen, clock, blank screen. I'm mostly wanting this to avoid any unnecessary battery loss.
Of course, the "blank screen" really should be an "off" screen, not just a black image. Showing a black image wouldn't save any energy if the backlight is still being powered for normal brightness. (it would on a CRT--see blackle--but not with LCD.) you might as well display the desktop if the screen is going to wake up to full brightness before showing the clock. and in that case,
you might as well just show the built-in system clock on your desktop or install statusbar clock (as others have suggested) and save the processor the cycle or 2 that it takes to show a clock on a black background like emjayes' app does.

The most power-efficient solution, of course, would be to flash the clock on the screen for only 1-2 seconds and then immediately shut the screen off afterwards. AND/OR show the clock at a diminished brightness level AND/OR show the desktop at diminished/zero brightness. (perhaps this is what you were suggesting already....)

i'm curious. @emjayes: are you making this for power-saving purposes too? or just for functional/accessibility purposes?
 
Rassilon7's Avatar
Posts: 220 | Thanked: 41 times | Joined on Oct 2008
#26
Well I found that 'Locked' clock was an apt name. It installed fine but then like a psycho ex girlfriend it refused to leave. The application manager hung on the uninstall for twenty minutes. I forced quit and tried this:

~ $ sudo gainroot
Root shell enabled


BusyBox v1.6.1 (2008-05-22 10:32:35 EEST) Built-in shell (ash)
Enter 'help' for a list of built-in commands.

/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:
initfs-flasher libgnokii3 kernel-diablo-flasher
libepeg0 flash-and-reboot libimlib2
Use 'apt-get autoremove' to remove them.
The following packages will be REMOVED
lockedclock
0 upgraded, 0 newly installed, 1 to remove and 2 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]? n
Abort.
/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:
initfs-flasher libgnokii3 kernel-diablo-flasher
libepeg0 flash-and-reboot libimlib2
The following packages will be REMOVED
flash-and-reboot initfs-flasher
kernel-diablo-flasher libepeg0 libgnokii3
libimlib2 lockedclock
0 upgraded, 0 newly installed, 7 to remove and 2 not upgraded.
1 not fully installed or removed.
Need to get 0B of archives.
After unpacking 6271kB disk space will be freed.
Do you want to continue [Y/n]? y
(Reading database ... 21584 files and directories currently installed.)
Removing lockedclock ...
Stopping Lockedclock daemon: /usr/lib/lockedclock/lockedclock.py:3: RuntimeWarning: import cdrom: No module named cdrom
import pygame
/usr/lib/lockedclock/lockedclock.py:3: RuntimeWarning: import joystick: No module named joystick
import pygame
Could not stop, pid file '/tmp/lockedclock.pid' missing.
invoke-rc.d: initscript lockedclock, action "stop" failed.
dpkg: error processing lockedclock (--remove):
subprocess pre-removal script returned error exit status 1
System startup links for /etc/init.d/lockedclock already exist.
Starting Lockedclock daemon: /usr/lib/lockedclock/lockedclock.py:3: RuntimeWarning: import cdrom: No module named cdrom
import pygame
/usr/lib/lockedclock/lockedclock.py:3: RuntimeWarning: import joystick: No module named joystick
import pygame

started with pid 1727
Lockedclock.
Removing kernel-diablo-flasher ...
Removing initfs-flasher ...
Removing flash-and-reboot ...
Removing libepeg0 ...
Removing libgnokii3 ...
Removing libimlib2 ...
Errors were encountered while processing:
lockedclock
E: Sub-process /usr/bin/dpkg returned an error code (1)
/home/user #


My question, did I do any damage?

Thanks in advance.

Steve
 
Reply

Tags
clock, screen lock

Thread Tools

 
Forum Jump


All times are GMT. The time now is 12:26.