FYI, I have hacked up a quick&dirty Plasma Mobile quick settings drawer button for VPNs:
https://invent.kde.org/kkofler/plasma-mo...ttings/vpn

You do not need to compile anything for it, you can just drop the contents of the linked folder into a new folder called ~/.local/share/plasma/quicksettings/org.kde.plasma.quicksetting.vpn (where ~ is your home directory) on the device (PinePhone, PinePhone Pro, or any other Plasma Mobile device).

The set up still requires the desktop kcm_networkmanagement, so you need to scroll around a bit in that dialog to configure the VPN. If you have no VPN set up yet, the quick settings button just brings up the dialog for you. Otherwise, it takes the first VPN it finds (there is no selection yet for the case where there is more than one) and toggles it, i.e., disables it if it was enabled, enables it otherwise. Depending on the VPN type, you will most likely be prompted for secrets with yet another desktop dialog, but it allows you to connect.

I doubt the code can be included upstream as is because the code architecture is just ugly (scraping a string to check the status and invoking a shell script to do the toggling using nmcli), but if you want a convenient way to use a VPN under Plasma Mobile as long as upstream does not support it officially, there you go.

Our Discord community has surpassed 1000 Discord members, which is beyond our expectations, and we are incredibly grateful for everyone who has participated and helped improve our community experience!

We are excited to announce that our continuous integration system is slowly getting back into action. We have nailed down the critical bugs and sorted out versioning. Our beta.armbian.com repository is now back with kernel semi-automated updates. We are also working on building framework documentation, and before we put it to the final destination, docs.armbian.com, we invite you to get involved in fast bootstrapping.

If you'd like to get involved in armbian, meet us at 6 PM CET every Wednesday for weekly developer meetings! 

We have also enabled Github sponsorships, so you can easily sponsor the project. This is a great way of supporting us and the future of armbian.

We were also busy planning for Armbian 23.05 release, and besides finding various agreements on tasks, the primary goal of the meeting was to clean the list of supported boards.

Also, we have enabled Google login on our forums, which became a hit overnight!  

Lastly, you are always welcome to join us at our general meetings every Friday, which take place at 11 PM CET every Friday!

I have several boards that I've tried to run R-Cade on that freak out when trying to run anything not encoded with x265 (and one board that works fine with all media). I was wondering if there was a diagnostics mode or image that could be booted that would run a full diag on the board that could be monitored over serial to see if there are any failures on the boards as having 3 that choke on specific things and one board that handles everything fine is a bit funky.

Hi there,

I want BLE-MIDI on the PineTime, overall preferred running in InfiniTime, because it seems the only still active OS. And I really like that OS.
I tried a library from Adafruit, with no success. Then I found this: https://novelbits.io/bluetooth-gatt-serv...teristics/ which explains very detailed how everything works, and I can compile it with Segger development tools (almost: There is a known bug in creating the binary, but that's ok, I don't want to stay on Segger anyway). But I can't find out how I could integrate it into InfiniTime. There are so many dependencies. How can one do something like port a new library?


Best regards,
Luno

Signal for Pinefon can be found at...

https://gitlab.com/undef1/signal-desktop...s/13612537

I got one of the Nexdock things that Purism is selling and I really like it.  I no longer need to tether the phone to a laptop for certain mobile uses - I can simply use the relevant apps and data directly on the phone now.  One odd behavior I am seeing is the screen going black for a couple seconds 2-4 times per minute.  I don't see this behavior when the Nexdock is connected to my Juno tablet (with mobian) so it's apparently not endemic to the dock.

Does anyone else have experience with a Nexdock and Pinephone?  I'd sure like to get some clues to the source of this issue.

Will the PineTav-V use the same chip as the Star64 or a different chip?

Mike

Hi everyone,

(I hope I'm posting in the right place. If not, please let me know.)

I have been using PineTime since 2021 and I really like it. I'm absolutely a FOSS-guy who welcomes any open/community-based projects, such as PineTime which is a fully open (hardware and software) and long overdue product in the smartwatch market.

I'm studying Computer Engineering at university. Many of us design a high-level application (Java, Python etc.) or a webpage or something AI related stuff. However, I'm rather a hardware (IoT/embedded systems) -oriented person, and that's why many people think i'm crazy when I say: "I loved my Assembly programming course"

To be honest, when I bought my first PineTime, I ordered a twin pack (sealed and devkit), because I knew that I would like to modify/hack/develop my watch in the future. And now it seems like a good idea to deal with PineTime because it perfectly fits my studies and who knows... maybe that could be even a great theme for my thesis. Moreover, it would be a great adventure (doing it for fun).

I'm planning to create a new (very basic) firmware from scratch. I mean that would be an independent and separate project from InfiniTime / Wasp-OS or other relevant PineTime related firmwares, although it would rely on some third party libraries (such as LVGL or FreeRTOS) and it would use existing projects (mostly InfiniTime) as a reference.


Initial (essential) objectives:

• display time without any smart capabilities (e.g. Bluetooth synchronization)
  

• Bluetooth implementation
  
• Heart rate measuring
  
• Step counting
  
• Built-in apps
  
• ...
  

Just bought a board (in India), have tried various images on pine site and different power supplies and SD cards the board always gets stuck on

U-Boot SPL 2022.04 (Mar 01 2023 - 00:14:33 +00000)
DRAM:

it never goes past DRAM:

the date after SPL changes with different images but it's stuck on DRAM:

once in a while it give this message once , restarts and gets stuck on DRAM again:

DRAM: This DRAM setup is currently not supported.

From looking at the specification, it seems the StarFive JH7110 is weaker than the Rockchip RK3399 but has more L2 cache. In performance I imagine the star64 will be slightly stronger than a RK3399 based device with its a72 cores disabled, in the case of pine64 hardware, only better because of the 8gb of ram?

Comparing GPUs, weaker but support for newer standards?

Do you agree? Difficult to benchmark, perhaps need the 4gb star and 4gb rock to go head to head.