djtech

joined 1 year ago
[–] djtech@lemmy.world 3 points 9 months ago

The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

[–] djtech@lemmy.world 6 points 9 months ago (1 children)

Thanks for your reply; i won't work with firmware-level aspects of the stack, as my plan is to write the userspace daemon, while keeping the kernel-levels modules identical and to communicate to them via HCI sockets, as they are implemented by Linux and with them I can talk directly to the bluetooth controllers.

I'll check out Android's project and double-check for security vulnerabilities in older version of the protocols tho, so thank you again for replying.

79
submitted 9 months ago* (last edited 9 months ago) by djtech@lemmy.world to c/linux@lemmy.ml
 

Hi everybody,

i'm a long time Debian user and, while i've always loved the Linux experience, the bluetooth side of things was always a little bit... painful.

Lately, i've been digging on how bluetooth on Linux works (i knew about BlueZ, but i didn't know about HCI sockets, standard protocols for bluetooth controllers, ...). Seeing how Android manages to work fine with bluetooth (yes, i know, money and company support, blah blah blah), i was thinking about re-writing the bluetooth daemon, in order to be modern, modular, safe (written in Rust), stable and retro-compatible (exposes the same D-Bus APIs as BlueZ) I already found some documents about HCI socket in Linux, HCI communication with bluetooth controllers, HID standards for Bluetooth, etc...

My questions are:

  • is this a good idea?
  • does somebody want to collaborate?

Thanks for reading.

EDIT: The repository is https://github.com/djtech-dev/reblued but at the moment is pretty much empty, just the project's skeleton, license, README and disussions for collaborators.

[–] djtech@lemmy.world 13 points 10 months ago (1 children)

Fork the feature one, get the diff of the commit that patches the bug and apply the diff to your fork.

Now compile and test.

[–] djtech@lemmy.world 1 points 10 months ago
[–] djtech@lemmy.world 2 points 10 months ago

A quick research tells me that there aren't patches for other emulators, but the protocol seems well described, so making those patches is possible. I could also take a look at Alacritty source code and deicide if I could make this project work.

[–] djtech@lemmy.world 9 points 10 months ago (6 children)

For rendering high quality images in the terminal, check out the Kitty graphical protocol. I don't know if they are any python libraries to use, but I think that they are. P.S. This seems to work well https://stackoverflow.com/questions/58138638/how-to-display-graphical-images-in-kitty-terminal-using-python

[–] djtech@lemmy.world 6 points 11 months ago

So... emacs?

[–] djtech@lemmy.world 45 points 11 months ago* (last edited 11 months ago)

mhhhhhhhhhh

The project is trolling fs

[–] djtech@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

What do you mean by AppImage permissions? A sandboxing feature like "access only those directories, those /dev devices, ..."

EDIT: obviously this isn't just for AppImage, but I tested it with AppImage and it work well. Another tip: if you want a package manager for managing AppImage installations try zap (https://github.com/srevinsaju/zap)

In that case, take a look at bubblejail. (https://github.com/igo95862/bubblejail)

[–] djtech@lemmy.world 3 points 11 months ago

Before the "systemctl" command: try removing the GPU and booting it up without the GPU If it works, you can skip the "systemctl" commands

[–] djtech@lemmy.world 3 points 11 months ago (10 children)

Run "journalctl --lines 200" and send photos of output.

NOTE: This is all of the logging of the computer, and it's long (that command select the last 200 entries), so you might have to scroll down using the PageDown key (or arrow down) in order make the photos of everything

[–] djtech@lemmy.world 3 points 11 months ago (13 children)

The Shell where you typed "systemctl reboot" and "exit".

If you are running KDE neon, try "apt update" and "apt upgrade". If It doesn't work do "sudo apt update" and "sudo apt upgrade"

view more: next ›