Hello, i've been working on a dashboard to remotely control and monitor raspberry pi. i have called it piBoard.
Its based on nodejs so you will need to install nodejs on your raspberry pi.
Here is the full information about the project which you can also find at : https://github.com/piBoard/piBoard
piBoard
Plugable embedded boards dashboard
What is it ?
piBoard is a plugable HTML-based dashboard for embedded boards.It provides a plugin architecture for creating plugins that will help with managing your embedded board. piBoard will give you the abillity to connect to all embedded boards (Raspberry Pi, beaglebone...etc) that are connected to your local network
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
How to Use
Using piBoard is straight forward, piBoard have two parts:
Server: which will be installed on the device that you want to manage lets say (Raspberry Pi)
Client: which will run on you computer to give you the ability to connect to the device and manage it
you only need to install piBoard-server on your embedded board (ex: Raspberry Pi) then run the piBoard-client on your computer. Which will automatically search and list all running piBoard-server inside your local network.
Version
0.0.1
Features
Plugins system: you can write your own plugin using javascript, html and nodejs
Auto scan to detect any running piBoard-server in the local network
Password protection to prevent insecure access to the board
Core plugins that comes out of the box when you install the piBoard:
1. Mouse & keyboard plugin: this plugin will let you control your device mouse and keyboard form your laptop, without hooking a real mouse and keyboard to your rasperrypi.
2. System plugin: this plugin will give you realtime updates on your system resources (memoury/cpu)
3. More plugins to come with futuer version releases
Installation
First you need to install the latest version of nodejs on the embedded device.
For Raspberry Pi and debian based embedded devices use the following command to install nodejs:
Code:
wget http://node-arm.herokuapp.com/node_latest_armhf.deb
sudo dpkg -i node_latest_armhf.deb
After installing nodejs you can proceed with piBoard-server installation, to do that download the latest piBoard-server version form
Code:
wget https://github.com/piBoard/piBoard/archive/master.zip
unzip master.zip
Now you will have a new folder called piBoard-master, cd to this folder:
Code:
cd piBoard-master
Now run the install script which will take care for installing all the dependencies and setting up the piBoard-server to run on startup, also it will setup the core plugins
to do that run this command
Code:
chmod 755 ./install.sh && ./install.sh
Installation my take couple of minutes so be patient please, also the command might ask you for your sudo password, this is because it will try to apt-get install some applications that are needed by the plugins to run.
Configuration
After finishing the installation you can edit the package.json file to edit your piBoard name and password.
Code:
vim package.json
and change the password and name fields, leaving the password field blank will allow piBoard-client to access your board without authentication
Code:
{
"piBoard": {
"name": "piBoard",
"password": "1234567"
}
}
Client
Get the latest release from piBoard Client form the Client repo, under releases.
https://github.com/piBoard/piBoard-client/releases
License
MIT
Free Software, Hell Yeah!
interesting. should work on full-blown pi4 as well as "embedded" pi which has fewer sockets like for USB-3
Related
This is non androd, non based on android ROM
This OS based on Meego.
I promised to publish a small guide how to boot Nemo Mobile on your phone instead of the default android. Here is a small guide how to do so. The process it self is quite simple and should be relatively safe as well, as you do not need to flash anything to try it out.
In this guide it is assumed that one has android tools, such as adb and fastboot installed, also Linux is assumed but it should work also on windows with minor modifications.
The phone used was unlocked/rooted before I tried this, so that might also be required for following these instructions.
First thing is to download all the needed files:
Downloads:
rootfs image: - http://sage.kapsi.fi/sagestechblog/gt-i9250/2012-04-26.1/nemo-handset-armv7l-gt-i9250.img.bz2
Kernel: - http://d-h.st/Ffw (also with this kernel you can boot arm linux)
Instruction:
Push the rootfs image to the /sdcard
# Uncompress
adb shell bzip2 -d /sdcard/nemo-handset-armv7l-gt-i9250.img.bz2
adb shell mv /sdcard/nemo-handset-armv7l-gt-i9250.img /sdcard/image.img
2. Download and flash kernel.elf
fastboot flash boot kernel.elf
fastboot reboot
Or with Flash Tools
3. Connect mouse via OTG
After this, the device should boot to the MTF based UX home screen.
What works:
USB OTG
USB Mouse/Keyboard
Display
Backlight
What no works:
Xorg starts with standard fbdev (no 3D acceleration)
Applications do not start as the software flag isn't forwarded properly
No window manager/application switcher (requires 3D)
No 3D acceleration
Touch screen
Sensors (Especially disabled)
No USB networking
No WLAN
No Bluetooth
No Sound
Touch keys
Hardware keys
...
Kernel sources:
https://github.com/XperiaNext/kernel_sony_msm8x60/tree/msm-3.0.67-fb
Changelog:
Alpha
- Added in kernel framebuffer support for booting this OS
Small preview:
Video:
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WOW，looks very powerful, but not for daily use.
Wow nice :good: keep going
waiting for better version with working touch . wifi etc....
I intend to port to WP7 device fully fledged WEC7 OS (USB Host/OTG, Flash animations in the fully featured Internet Explorer, XP-like explorer design, Multiple formats media player etc.) with preservation of WP7 applications in the near future. Many WEC / WCE applications work unchanged, the problem is only with the addition of the core (especially missing UI API) and fixing some drivers. If you want someone to play, for example, there is a kernel tracker listing. Place the attached exe and dll files in the \Windows directory, you can start logging by WP7 console command:
\> CeLogFlush.exe
Logging will finished by device power switching off or by W.I.N.C.O wPhoManager Process Kill function.
Registry needed (in my device are rest probably from the Dynamics ROM authors):
[HKEY_LOCAL_MACHINE\System\CeLog]
"FileName"="celog.clg"
"Transport"="LocalFile"
You can open logged file by Visual Studio 2008 Remote Tools / Kernel Tracker.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Very powerful WEC7 shell works on WP7 device too
Deploy shell.exe to \Windows directory. Now you can work from WP7 Console. Try for example:
\> shell -c gi proc
or
\> shell -c mi kernel
-c means "output to console"
2013 (similar WEC7) target controlling help is here.
Full Internet explorer for WP7
There is first version. After one working second it stays in "Failed to create swap chain" state. This is something from DirectX subsystem probably. Also "Too many favorites" mistake occures. If we solve it, we can use fully working IE on WP7 devices (grouped favorites, working flash and other plugins etc.).
Utilities big update
New Console7 version can offer to you many usable utilities, as cgacutil, etcha, ipconfig, ipconfig6, ipv6, kbdtest, msmqadm, ndisconfig, net, netlogctl, netstat, ping, rnaapp, route, services, shell, tracert, upnpreg and wlantool. With simply user interface you can write commands (or batch or Mort scripts) with big possibilities as on desktop Windows.
Might be you need a "32-bit Windows 8.x / 7 Rescue Disk (WinPE)" at some point. If you won't create such a WinPE by yourself, you might use the one I created by means of phantastic WinBuilder - a script engine that will run a project developed by you, which produces a very efficient boot disk . Note, that this WinPE boots in legacy mode and only comes with legacy apps.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
• Requirements:
1. At least 1 GB RAM; the WinPE completely is copied to RAM and runs from therein.
2. A storage device with at least 1 GB; the WinPE currently is ~225 MB of size.
3. A VESA-compatible display device. Note, that screen resolution will be set to 1024x768 and colordepth to 32-bit.
• Network:
Wireless networking is not supported in WinPE, this WinPE uses TCP/IP and/or NetBIOS over TCP/IP to provide network access and support for standard network drivers. Hence connect the PC to a router using an ethernet cable before booting.
• How To:
» You burn the .ISO on CD/DVD/BD or USB-stick (use 2x speed).
» You direct your Windows 8.x / 7 32-bit computer to boot from the storage device you burnt the .ISO onto.
» You power off the PC.
» You insert the CD/DVD/BD or plugin the USB-stick.
» You restart your Windows 8.x / 7 32-bit computer.
If WinPE has successfully booted, you right click anywhere in the desktop to get the WinPE's MENU shown. You wiil not find a pretty GUI with buttons and nice graphs!
• Disclaimer:
This WinPE only was tested in VMWare Player. It comes with no warranty or official support - I will try to help with any bugs or issues that people report when I get chance but this is not in any way guaranteed. No guarantee of final success or absence of undesirable side effects is being given hereby. Any liability of any kind will be rejected. I cannot be held accountable for any loss of data that occurs as a result of using this WinPE, you use the programs included AT YOUR OWN RISK. Be aware in WinPE environment you are "nt authority/system", which is the highest level on a local system, above Administrator.
TO GET AN IDEA, WHAT A PROGRAM INCLUDED IS FOR, PLEASE VISIT ITS RESPECTIVE WEB-SITE.
This WinPE comes with no programs' documentation! Might be with next version of this WinPE.
• License, Use, Copying, and Distribution:
Because this WinPE compilation only is based on free softwares, it is licensed as Freeware and free to download and for personal and commercial usage.
• Trade-Marks and Proprietary Notices:
Parts of this WinPE contents might be protected by copyrights, trademarks, trade secrets, or other proprietary rights, and if so, these rights are valid and belong to the authors of the softwares injected in the WinPE. "Microsoft Windows PE 5.0" which this WinPE is built on, is copyrighted by Microsoft.
• Credits:
Misty, who provided an excellent basic WinBuilder-project ready to start with
grischka, who developped bbLean, a Windows Shell Replacement that appears spartan and minimalistic compared to a normal Windows interface and is therefore resource saving.
• Version History:
v1 2014-05-01
Download: WinPE-32bit-en-US-v1.iso
MD5 Checksum: 4c7bcc301463dd04b8ed69865aa9b82a
Hi all,
On Android 13, Google enabled KVM support for Tensor Chips model(Pixel 6 / 6pro / 6a). So we can run a Virtual machine at full speed, but there is no APP to utilize this feature.
I modified the Limbo Emulator (QEMU), so it can enable the KVM on Pixel 6 Phones. Due to the limitation of the kernel, the APP needs ROOT permission to access the KVM service(/dev/kvm)
Currently, only VNC is working on this APP, and you can only boot directly using the Linux kernel. UEFI did not work on KVM.
Network functions worked, but you may need to set the DNS inside the Guest OS.
Arch Linux for arm64 runs pretty well on Limbo. It runs even faster than Raspi 4. You can download it from ArchLinuxARM-aarch64-latest.tar.gz
Other Linux can also run on the Limbo, but you may need to recompile the kernel to enable virto-related functions.
Download link:
Releases · wasdwasd0105/limbo_tensor
Limbo for Tensor is a QEMU-based Hypervisor for Tensor-based Google Pixel devices such as Pixel 6 & 7 series. - wasdwasd0105/limbo_tensor
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Interesting concept. If I get some time I'll give it a whirl.
Thanks for this
Gives me a "package appears to be invalid" when trying to install. Assuming this could be a signature issue? not sure....
im having same issue
edit: you need to install the debug apk with adb
Code:
adb install -t <name-of-apk>
it would be awesome if this app had a terminal emulator function so you dont have to exclusively use the vnc viewer.
Can confirm this^ works. Would love to install w11 with this. Looks good
Is anyone else having issues with being able to bring CPUs online since the v0.2.1 update? It seems that each boot a random amount of allocated CPUs will online (it seems to mostly be just one), and attempting to online the ones that failed results in:
ryaniskira said:
Is anyone else having issues with being able to bring CPUs online since the v0.2.1 update? It seems that each boot a random amount of allocated CPUs will online (it seems to mostly be just one), and attempting to online the ones that failed results in:
View attachment 5741675
Click to expand...
Click to collapse
Try 0.22
Unfortunately the issue still exists.
I've attached a log on Pastebin though I can't see anything obviously wrong other than Java not being able to find a file.
ryaniskira said:
Unfortunately the issue still exists.
View attachment 5743195
I've attached a log on Pastebin though I can't see anything obviously wrong other than Java not being able to find a file.
Click to expand...
Click to collapse
can you try using uefi mode？
uefi mode results in nothing.
UEFI + Debian works just fine. One issue i have is that ssh port forwarding just doesn't work, but telnet does (but it forgets i set it every time i launch the app).
Is there a telegram group for this project?
Can you please share how you created the EFI pflash image, specifically the part where the memory write issue is resolved. I have an idea on how to fix Windows, but I've not ever seen the memory write issue.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Droidian is a GNU/Linux distribution based on top of Mobian, a Debian-based distribution for mobile devices. The goal of Droidian is to be able to run Mobian on Android phones. This is accomplished by using well-known technologies such as libhybris and Halium.Requirements
Android 9 firmware for your device (PQ3B.190801.002):
Pixel 3a sargo: LINK
Files
Download the latest fastbootable image: droidian-UNOFFICIAL-phosh-phone-google_sargo-api28-arm64-nightly_XXXXXXXX.zip
Installation:
Extract the archive
run the flash_all script
Boot to fastboot and let the script flash everything.
UBports Installer
Alternatively the UBports installer can also be used to install Droidian.
NotesDefault passwordThe default password is 1234.
List of working things can be found at https://github.com/droidian-sargo/device-page
APNMobile data needs an APN to be set up from Settings -> Mobile Network -> Access Point Names.
Broken mobile data after callsData connection might break after receiving and making calls. Switch it off and on from Settings -> Mobile Network to fix it. Be careful to not turn off the mobile modem or a device restart might be required.
Out of storageBy default when flashing Droidian it allocates 8GB of storage to the system. This might not be enough and luckily you can allocate more storage with ADB by running (while in recovery): adb shell e2fsck -fy /data/rootfs.img and adb shell resize2fs -f /data/rootfs.img xG where x is the amount of GB to allocate (eg: 50G for 50 GB).
SSH accessconnect your phone to your computer and type ssh [email protected], the password is 1234 (on Windows, you may need PuTTY)
ApplicationsYou can find a list of mobile-friendly Linux applications at LinuxPhoneApps
What Works
Manual brightness, Notification LED, Torchlight, Vibration, Carrier info, Data connection, Calls, Pin unlock, SMS, Audio routing, Voice calls, Volume control, Battery percentage, Online charging, RTC time, SDcard, Shutdown, Reboot, Bluetooth, Flight mode, Hotspot, WIFI, Auto brightness, Proximity, Rotation, Touch screen, Earphones, Loud speaker, Microphone, Waydroid
What partially works
Camera works fine in Waydroid but in system itself it requires manual download and compilation of a software
What doesn't work
GPS, Fingerprint, Offline charging, Dual SIM, Encryption
Don't enable encryption it make it will soft brick the device.
WaydroidWaydroid is an Android container which lets Android apps run on Linux phones with GPU acceleration with full speed.
Waydroid works fine on bonito.
Final Notes
I'm not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
Support
Droidian telegram group: @DroidianLinux.
Thanks to the Droidian team and fredldotme for all helping out to make this happen.
All the sources are available at
https://github.com/droidian-sargo/
Attached images are from different devices but the interface looks and acts the same.
Hi,
i just got a pixel 3a and installed ubuntu touch. can i flash droidian using ubports installer from this or do i have to go back to android9 before?
screenshots look really good
jazzzy_de said:
Hi,
i just got a pixel 3a and installed ubuntu touch. can i flash droidian using ubports installer from this or do i have to go back to android9 before?
screenshots look really good
Click to expand...
Click to collapse
yes you can
FakeShell said:
yes you can
Click to expand...
Click to collapse
Thanks a lot. It worked. Now I can play around with it and try to solve upcoming problems