| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,862
» Latest member: Billy7698
» Forum threads: 16,313
» Forum posts: 117,377
Full Statistics
|
| Latest Threads |
Questions about filming v...
Forum: PinePhone Hardware
Last Post: georgegohl888
Yesterday, 07:46 AM
» Replies: 11
» Views: 16,420
|
Pinebook Pro in EU for Sa...
Forum: General Discussion on Pinebook Pro
Last Post: Anthona
02-09-2026, 12:50 AM
» Replies: 5
» Views: 7,368
|
New Pinetab- error when a...
Forum: PineTab Software
Last Post: authorjaw
02-08-2026, 08:19 PM
» Replies: 0
» Views: 64
|
What about a Pine digital...
Forum: General
Last Post: gwennelsonuk
02-08-2026, 08:11 PM
» Replies: 8
» Views: 8,057
|
Proposal: an open mp3/med...
Forum: General
Last Post: gwennelsonuk
02-08-2026, 08:08 PM
» Replies: 1
» Views: 74
|
Pinephone (Pro) Keyboard ...
Forum: PinePhone Accessories
Last Post: Ondy
02-08-2026, 07:41 PM
» Replies: 7
» Views: 14,847
|
Ethernet does not work
Forum: Ethernet Port
Last Post: zetabeta
02-06-2026, 11:58 PM
» Replies: 1
» Views: 92
|
Fitting new case
Forum: Pinebook Pro Hardware and Accessories
Last Post: RicTor
02-06-2026, 07:09 AM
» Replies: 0
» Views: 90
|
Rockchip gets DMCA'ed on ...
Forum: General Discussion on PinePhone
Last Post: hanmira
02-04-2026, 08:43 PM
» Replies: 3
» Views: 734
|
Advice on PineNote
Forum: General Discussion on PineNote
Last Post: LogicalAtomist
02-04-2026, 06:51 PM
» Replies: 0
» Views: 135
|
|
|
How to set the Power Off key binding in i3wm for the Pinebook |
|
Posted by: MarkHaysHarris777 - 09-16-2017, 10:21 PM - Forum: Linux on Pinebook
- Replies (4)
|
 |
Greetings,
The purpose of this blog post is to detail the steps necessary to set the Power Off key-binding for the Pinebook in i3 window manager. We don't want the Pinebook to come crashing down if we accidentally touch the poweroff button -- so we'll set a key-binding that makes sense requiring at least two other keys , for instance the $mod key and the Shift key. The following key-binding should bring the system down cleanly ( and power off properly ) without prompting for a password:
$mod+Shift+XF86_PowerOff
The key-binding will be placed in the i3 config; but I'm getting ahead of myself. The first step is to build the poweroff script in /usr/local/sbin/
Pb_poweroff.sh
The simple script above should be placed in /usr/local/sbin/ and should be made active with the following commands:
sudo chown root:root Pb_poweroff.sh
sudo chmod 0754 Pb_poweroff.sh
The next step is to place a rule file in /etc/sudoers.d/ so that the command trigger will not prompt for the sudo password when the key-binding is pressed. Creat the following rule file in /etc/sudoers.d/ :
Pb_power_rule
Code: # Pb power rule
Cmnd_Alias PBPOWEROFF=/usr/local/sbin/Pb_poweroff.sh
ALL ALL=NOPASSWD: PBPOWEROFF
Place the above rule file in the /etc/sudoers.d/ directory and activate with the following commands :
sudo chown root:root Pb_power_rule
sudo chmod 0440 Pb_power_rule
The last step is to place the following bindsym entry in the i3 configuration ~/.config/i3/config , in your home directory:
bindsym $mod+Shift+XF86_PowerOff exec sudo /usr/local/sbin/Pb_poweroff.sh
Place the above bindsym entry somewhere near the end of your i3 config after the "resize" and before the "bar". The configuration file is ~/.config/i3/config
Activate the key-binding by either pressing $mod+Shift+c to re-read the config, or $mod+Shift+r to restart i3wm.
Theory
Pressing the Pinebook power button returns scancode 124; key-sym XF86_PowerOff. This by default does nothing in i3wm; unlike other OS window manager | desktops , which typically pulls up the shutdown dialogue.
With our keybinding in effect the Pb_poweroff.sh script will be called with sudo, and because the Pb_power_rule file exists in /etc/sudoers.d/ the command trigger will not prompt for the password, but the poweroff command will simply take effect: while holding down the mod key, and the Shift key together, press the power button and the i3 window manager will exit and the system will cleanly shutdown and power off.
|
|
|
|
| Octoprint |
|
Posted by: Cellarboy - 09-16-2017, 10:04 AM - Forum: General Discussion on ROCK64
- Replies (3)
|
 |
Sorry if this is a dumb or frequently asked question, but is there a working Octoprint build for the Rock64? I’m weighing up going the easy route and just just getting a Raspberry Pi, but I do like the idea of having a board with a bit more grunt or processing headrooom that the Rock64 seems to offer.
Many thanks in advance.
|
|
|
|
| Shutdown / Restarting Android Rock64 |
|
Posted by: Farley56 - 09-15-2017, 09:15 AM - Forum: Android on Rock64
- Replies (5)
|
 |
Wondered about the recommended method of powering down Rock64 running Android. Found a post in the Pine64 section from 2016. Here's what I experienced.
1. Short press of the power button on Rock64 = blanks the screen. Short press a second time brings up the screen.
2. Long press of the power button on Rock64 = displays power off / restart dialog box. Defaults to power off, press Enter, Rock64 powers off. Arrow down to Restart, then Enter, Rock64 says powering down, and then it restarts.
3. Restarting via the settings menu (Settings - About - Restart) also restarts but I couldn't find anything in settings about shutting down.
4. Pressing the reset button on Rock64 = resets (probably not recommended, doesn't correctly close first, just hard reset like pulling the power?).
5. If off - pressing the power button = powers it up, pressing the reset button = powers it up.
I assume my results are by design. If not, best method for powering down? Don't want to corrupt the eMMC. Thanks.
NOTE: base Android, not Android TV build. Not sure if the results would be the same.
|
|
|
|
| LibreELEC Krypton/Leia/Agile 64bit kernel 32bit libs |
|
Posted by: Raybuntu - 09-14-2017, 01:57 AM - Forum: Linux on Rock64
- Replies (193)
|
 |
Here is my community build. Kernel is build as 64bit with 32bit Userspace. It means you can use 32bit armhf packages. I've been doing these builds for a while now for Odroid C2, WeTek.Hub and WeTek.Play2. The benefit in using 32bit packages with an aarch64 kernel is we can use retroplayer emulators that only compile for armhf and we can use precompiled libwidevine to play DRM protected content with Kodi through inputstream.adaptive.
Special thanks go to @peak3d for implementing the great inputstream plugin that makes DRM work with kodi.
Also special thanks to @Kwiboo, @longchair and @omegamoon for the great Rockchip work. These builds are based on kwiboo's LE tree.
And last but not least thanks to @tllim for providing me a Rock64 developer sample.
DISCLAIMER: This is a community build of LibreELEC. USE AT YOUR OWN RISK!
Tar upgrade from "pure" aarch64 builds might work. Use the following steps:
Code: touch /storage/.update/.nocompat
Code: rm /storage/.kodi/addons/packages
Then you will have to reinstall all addons from my Repo. My Repo (RB-Addons) ist preinstalled and features the same addons as official LibreELEC does. I'm rebuilding all addons from source.
If you are updating from one of my previous builds you just need to put the tar in /storage/.update/
Download on Github: https://github.com/Raybuntu/LibreELEC.tv/releases
Source code on Github: https://github.com/Raybuntu/LibreELEC.tv...Krypton-rk
Addons: https://github.com/Raybuntu/rb-addons
Bugs: https://github.com/Raybuntu/LibreELEC.tv/issues
If you like my build and you want to buy me a beer or whatever.
Bitcoin: 12zLUYC7JzwM7a8cQKekAvZr9kWxjzTfxm
https://github.com/Raybuntu/LibreELEC.tv...-krypton18
That's my first build. Based on kwiboo's build.
-kwiboo's libcec Adapter for feature complete CEC support in Kodi.
-HEVC HW decoding working
-H.264 HW decoding working
-I've tested DAZN with inputstream.adaptive and libwidevine from Chromeos and it's working pretty good.
- VC-1 and mpeg2 are not HW decoded which makes VC-1 basically unusable
- Occasional graphic glitches
Use at your own risk.
Netflix and Amazon VOD Streaming will be working when the first LE9 (rb-leia) build is ready for the Rock64. I'll also start focusing on Leia and I will drop Support for Krypton in the future.
|
|
|
|
|