hamclock_running_on_an_o2_joggler
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| hamclock_running_on_an_o2_joggler [2021/04/20 21:37] – 2e0lxq | hamclock_running_on_an_o2_joggler [2021/04/21 07:25] – 2e0lxq | ||
|---|---|---|---|
| Line 31: | Line 31: | ||
| sudo apt install curl make g++ xorg-dev | sudo apt install curl make g++ xorg-dev | ||
| - | 5. Install the following apps as well: | + | 5. Install the Hamclock app, following the guide on the Hamclock site. |
| + | |||
| + | 6. Install the following apps as well: | ||
| | | ||
| - | 6. Enable lightdm: | + | 7. Enable lightdm: |
| sudo dpkg-reconfigure lightdm | sudo dpkg-reconfigure lightdm | ||
| - | 7. Install the greeter | + | 8. Install the greeter |
| sudo apt-get install -y lightdm-gtk-greeter | sudo apt-get install -y lightdm-gtk-greeter | ||
| - | 8. If all goes to plan, when you reboot the system, the two lines of Ubuntu code should now be replaced a simple graphic box, asking you to provide the password for the ' | + | 9. If all goes to plan, when you reboot the system, the two lines of Ubuntu code should now be replaced a simple graphic box, asking you to provide the password for the ' |
| - | 9. From your Terminal or PuTTy app, start the Hamclock app. You should see the Hamclock setup screen appear very shortly on your Joggler. Using the user guide, enter the items you want to change (callsign, location etc.), then let the app start. | + | 10. From your Terminal or PuTTy app, start the Hamclock app. You should see the Hamclock setup screen appear very shortly on your Joggler. Using the user guide, enter the items you want to change (callsign, location etc.), then let the app start. |
| - | 10. The app will continue to run, but to disconnect your terminal window, use an instruction like nohup to keep the app running, otherwise shutting it down will also stop the Hamclock app. You can also disconnect your external keyboard. | + | 11. The app will continue to run, but to disconnect your terminal window, use an instruction like nohup to keep the app running, otherwise shutting it down will also stop the Hamclock app. You can also disconnect your external keyboard. |
| That should work. As I said, I am no coder, so there may be steps here that are not needed, duplicate things done previously or are just plain dumb, but this is the way I got my Hamclock to work, and I have built this on two separate sticks now to test it out. | That should work. As I said, I am no coder, so there may be steps here that are not needed, duplicate things done previously or are just plain dumb, but this is the way I got my Hamclock to work, and I have built this on two separate sticks now to test it out. | ||
| Please do get in touch with tips or improvements - Hamclock looks great on the Joggler, runs really well, and even auto-updates. And it's a great way to give a new lease of life to old tech, rather than just binning it. | Please do get in touch with tips or improvements - Hamclock looks great on the Joggler, runs really well, and even auto-updates. And it's a great way to give a new lease of life to old tech, rather than just binning it. | ||
| + | |||
| + | **Things I would like to fix in subsequent versions:** | ||
| + | |||
| + | 1. Can I change the screen timeout delay? It's annoying to have the screen go blank, but quite good power saving. Could this time be adjusted | ||
| + | ? | ||
| + | |||
| + | 2. Can I do away with the keyboard log-in step? | ||
| + | |||
| + | 3. Could the internal memory be flashed with the complete package? Internal memory is only 512K, so it suggests to me that it might not. | ||
| 73 de 2E0LXQ | 73 de 2E0LXQ | ||