home.social

#framebufferphone — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #framebufferphone, aggregated by home.social.

  1. Last major issue to fix before releasing fbp 0.6.1 and using as my daily driver: The UI is really slow, unresponsive, and crashes often on any platform other than the original pinephone with pmOS. Likely due to a memory leak

  2. Last major issue to fix before releasing fbp 0.6.1 and using #framebufferphone as my daily driver: The UI is really slow, unresponsive, and crashes often on any platform other than the original pinephone with pmOS. Likely due to a memory leak

  3. Last major issue to fix before releasing fbp 0.6.1 and using #framebufferphone as my daily driver: The UI is really slow, unresponsive, and crashes often on any platform other than the original pinephone with pmOS. Likely due to a memory leak

  4. Last major issue to fix before releasing fbp 0.6.1 and using #framebufferphone as my daily driver: The UI is really slow, unresponsive, and crashes often on any platform other than the original pinephone with pmOS. Likely due to a memory leak

  5. Announcing the release of and 0.6! This marks the first releases in almost 2 years, and I'm so proud of the amount of learning that went into these releases. I'm picking up where Miles Alan left off in order to create the ultimate framebuffer-based UI for . Packaging should be making its way into /#Alpinelinux soon (tm), and I've created a PR to get this UI option merged into Arch ARM.

  6. Announcing the release of #fbp and #f_scripts 0.6! This marks the first #framebufferphone releases in almost 2 years, and I'm so proud of the amount of learning that went into these releases. I'm picking up where Miles Alan left off in order to create the ultimate framebuffer-based UI for #MobileLinux. Packaging should be making its way into #pmOS/#Alpinelinux soon (tm), and I've created a PR to get this UI option merged into #Danctnix Arch ARM.

  7. Announcing the release of #fbp and #f_scripts 0.6! This marks the first #framebufferphone releases in almost 2 years, and I'm so proud of the amount of learning that went into these releases. I'm picking up where Miles Alan left off in order to create the ultimate framebuffer-based UI for #MobileLinux. Packaging should be making its way into #pmOS/#Alpinelinux soon (tm), and I've created a PR to get this UI option merged into #Danctnix Arch ARM.

  8. Announcing the release of #fbp and #f_scripts 0.6! This marks the first #framebufferphone releases in almost 2 years, and I'm so proud of the amount of learning that went into these releases. I'm picking up where Miles Alan left off in order to create the ultimate framebuffer-based UI for #MobileLinux. Packaging should be making its way into #pmOS/#Alpinelinux soon (tm), and I've created a PR to get this UI option merged into #Danctnix Arch ARM.

  9. Announcing the release of #fbp and #f_scripts 0.6! This marks the first #framebufferphone releases in almost 2 years, and I'm so proud of the amount of learning that went into these releases. I'm picking up where Miles Alan left off in order to create the ultimate framebuffer-based UI for #MobileLinux. Packaging should be making its way into #pmOS/#Alpinelinux soon (tm), and I've created a PR to get this UI option merged into #Danctnix Arch ARM.

  10. i'd like to synchronize the releases of and 0.6, but i first need to finish overhauling the f_scripts audio stack in f_audio and f_phone. once those items are done, i think i'll be able to switch to as my daily driver UI!

  11. i'd like to synchronize the releases of #fbp and #f_scripts 0.6, but i first need to finish overhauling the f_scripts audio stack in f_audio and f_phone. once those items are done, i think i'll be able to switch to #framebufferphone as my daily driver UI!

  12. i'd like to synchronize the releases of #fbp and #f_scripts 0.6, but i first need to finish overhauling the f_scripts audio stack in f_audio and f_phone. once those items are done, i think i'll be able to switch to #framebufferphone as my daily driver UI!

  13. i'd like to synchronize the releases of #fbp and #f_scripts 0.6, but i first need to finish overhauling the f_scripts audio stack in f_audio and f_phone. once those items are done, i think i'll be able to switch to #framebufferphone as my daily driver UI!

  14. overhauling the f_audio script is turning out to be quite the challenge. not only am i reworking it to use a pipewire/pamixer stack instead of using alsa directly, but im also making it system-independent by auto detecting available sinks, sources, and ports and basing the ui off of that rather than hard-coding in which audio devices are available. it's coming along nicely, and i'm learning more about pulseaudio and scripting than i ever have before

  15. overhauling the #framebufferphone f_audio script is turning out to be quite the challenge. not only am i reworking it to use a pipewire/pamixer stack instead of using alsa directly, but im also making it system-independent by auto detecting available sinks, sources, and ports and basing the ui off of that rather than hard-coding in which audio devices are available. it's coming along nicely, and i'm learning more about pulseaudio and scripting than i ever have before

  16. overhauling the #framebufferphone f_audio script is turning out to be quite the challenge. not only am i reworking it to use a pipewire/pamixer stack instead of using alsa directly, but im also making it system-independent by auto detecting available sinks, sources, and ports and basing the ui off of that rather than hard-coding in which audio devices are available. it's coming along nicely, and i'm learning more about pulseaudio and scripting than i ever have before

  17. overhauling the #framebufferphone f_audio script is turning out to be quite the challenge. not only am i reworking it to use a pipewire/pamixer stack instead of using alsa directly, but im also making it system-independent by auto detecting available sinks, sources, and ports and basing the ui off of that rather than hard-coding in which audio devices are available. it's coming along nicely, and i'm learning more about pulseaudio and scripting than i ever have before

  18. overhauling the #framebufferphone f_audio script is turning out to be quite the challenge. not only am i reworking it to use a pipewire/pamixer stack instead of using alsa directly, but im also making it system-independent by auto detecting available sinks, sources, and ports and basing the ui off of that rather than hard-coding in which audio devices are available. it's coming along nicely, and i'm learning more about pulseaudio and scripting than i ever have before

  19. i became a real programmer today... i wrote my first segfault

    lol i was working on text rendering in the fbp keyboard, i can't figure out why sdl_truetype is drawing all the fonts in white

    it doesn't help that i'm writing a complex program in zig when i don't really know zig

  20. i became a real programmer today... i wrote my first segfault

    lol i was working on text rendering in the #framebufferphone fbp keyboard, i can't figure out why sdl_truetype is drawing all the fonts in white

    it doesn't help that i'm writing a complex program in zig when i don't really know zig

  21. i became a real programmer today... i wrote my first segfault

    lol i was working on text rendering in the #framebufferphone fbp keyboard, i can't figure out why sdl_truetype is drawing all the fonts in white

    it doesn't help that i'm writing a complex program in zig when i don't really know zig

  22. i became a real programmer today... i wrote my first segfault

    lol i was working on text rendering in the #framebufferphone fbp keyboard, i can't figure out why sdl_truetype is drawing all the fonts in white

    it doesn't help that i'm writing a complex program in zig when i don't really know zig

  23. i became a real programmer today... i wrote my first segfault

    lol i was working on text rendering in the #framebufferphone fbp keyboard, i can't figure out why sdl_truetype is drawing all the fonts in white

    it doesn't help that i'm writing a complex program in zig when i don't really know zig

  24. @jawsh that's pretty much the idea with the UI that i'm working on. just a virtual keyboard, tty, and some scripts to make it usable for calling/texting and other basic smartphone functionality. we'll have to see what the battery life difference is once it's fully daily-drivable

  25. @jawsh that's pretty much the idea with the #framebufferphone #MobileLinux UI that i'm working on. just a virtual keyboard, tty, and some scripts to make it usable for calling/texting and other basic smartphone functionality. we'll have to see what the battery life difference is once it's fully daily-drivable

  26. @jawsh that's pretty much the idea with the #framebufferphone #MobileLinux UI that i'm working on. just a virtual keyboard, tty, and some scripts to make it usable for calling/texting and other basic smartphone functionality. we'll have to see what the battery life difference is once it's fully daily-drivable

  27. @jawsh that's pretty much the idea with the #framebufferphone #MobileLinux UI that i'm working on. just a virtual keyboard, tty, and some scripts to make it usable for calling/texting and other basic smartphone functionality. we'll have to see what the battery life difference is once it's fully daily-drivable

  28. learning is quite the adventure! i'm migrating the f_phone script to use in place of megi's old pinephone-call-audio program (for wider system compatability and future-proofing), but am finding it harder than expected. finding a good way to start callaudiod's dbus connection is proving quite difficult. oh, well, i'll figure it out. up next: migrating f_audio and other scripts that use audio to ! that's sure to be fun.

  29. learning #DBus is quite the adventure! i'm migrating the #framebufferphone f_phone script to use #callaudiod in place of megi's old pinephone-call-audio program (for wider system compatability and future-proofing), but am finding it harder than expected. finding a good way to start callaudiod's dbus connection is proving quite difficult. oh, well, i'll figure it out. up next: migrating f_audio and other scripts that use audio to #pipewire! that's sure to be fun.

  30. learning #DBus is quite the adventure! i'm migrating the #framebufferphone f_phone script to use #callaudiod in place of megi's old pinephone-call-audio program (for wider system compatability and future-proofing), but am finding it harder than expected. finding a good way to start callaudiod's dbus connection is proving quite difficult. oh, well, i'll figure it out. up next: migrating f_audio and other scripts that use audio to #pipewire! that's sure to be fun.

  31. learning #DBus is quite the adventure! i'm migrating the #framebufferphone f_phone script to use #callaudiod in place of megi's old pinephone-call-audio program (for wider system compatability and future-proofing), but am finding it harder than expected. finding a good way to start callaudiod's dbus connection is proving quite difficult. oh, well, i'll figure it out. up next: migrating f_audio and other scripts that use audio to #pipewire! that's sure to be fun.

  32. learning #DBus is quite the adventure! i'm migrating the #framebufferphone f_phone script to use #callaudiod in place of megi's old pinephone-call-audio program (for wider system compatability and future-proofing), but am finding it harder than expected. finding a good way to start callaudiod's dbus connection is proving quite difficult. oh, well, i'll figure it out. up next: migrating f_audio and other scripts that use audio to #pipewire! that's sure to be fun.

  33. happy new year! and right to work i go, testing on both and on the and pro with a patch applied that updates fbp to be built on the Zig 0.11.0 codebase. huge thanks to ~noneofyourbusiness on sourcehut for submitting that patch, i'll have it merged shortly!

  34. happy new year! and right to work i go, testing #framebufferphone on both #pmOS and #ArchLinuxARM on the #pinephone and #pinephone pro with a patch applied that updates fbp to be built on the Zig 0.11.0 codebase. huge thanks to ~noneofyourbusiness on sourcehut for submitting that patch, i'll have it merged shortly!

  35. happy new year! and right to work i go, testing #framebufferphone on both #pmOS and #ArchLinuxARM on the #pinephone and #pinephone pro with a patch applied that updates fbp to be built on the Zig 0.11.0 codebase. huge thanks to ~noneofyourbusiness on sourcehut for submitting that patch, i'll have it merged shortly!

  36. happy new year! and right to work i go, testing #framebufferphone on both #pmOS and #ArchLinuxARM on the #pinephone and #pinephone pro with a patch applied that updates fbp to be built on the Zig 0.11.0 codebase. huge thanks to ~noneofyourbusiness on sourcehut for submitting that patch, i'll have it merged shortly!

  37. happy new year! and right to work i go, testing #framebufferphone on both #pmOS and #ArchLinuxARM on the #pinephone and #pinephone pro with a patch applied that updates fbp to be built on the Zig 0.11.0 codebase. huge thanks to ~noneofyourbusiness on sourcehut for submitting that patch, i'll have it merged shortly!

  38. list of tech goals over winter break:

    [] home server setup (wip)
    [x] back case meshtastic connection
    [] figure out LoRa usb communicator
    [] pinephone fingerprint back case
    [] actually maintain
    [x] read the Pragmatic Programmer
    [x] figure out what's wrong with my (charging circuit :/)
    - and probably more i'm forgetting

    i've got a bit of work to do

  39. list of tech goals over winter break:

    [] home server setup (wip)
    [x] #LoRa #Pinephone back case meshtastic connection
    [] figure out LoRa #PineDio usb communicator
    [] pinephone fingerprint back case
    [] actually maintain #framebufferphone
    [x] read the Pragmatic Programmer
    [x] figure out what's wrong with my #ppkb (charging circuit :/)
    - and probably more i'm forgetting

    i've got a bit of work to do

  40. list of tech goals over winter break:

    [] home server setup (wip)
    [x] #LoRa #Pinephone back case meshtastic connection
    [] figure out LoRa #PineDio usb communicator
    [] pinephone fingerprint back case
    [] actually maintain #framebufferphone
    [x] read the Pragmatic Programmer
    [x] figure out what's wrong with my #ppkb (charging circuit :/)
    - and probably more i'm forgetting

    i've got a bit of work to do

  41. list of tech goals over winter break:

    [] home server setup (wip)
    [x] #LoRa #Pinephone back case meshtastic connection
    [] figure out LoRa #PineDio usb communicator
    [] pinephone fingerprint back case
    [] actually maintain #framebufferphone
    [x] read the Pragmatic Programmer
    [x] figure out what's wrong with my #ppkb (charging circuit :/)
    - and probably more i'm forgetting

    i've got a bit of work to do

  42. another blog post is out, this time a spotlight on the UI available on and soon(tm) arch ARM! i've been working on porting this framebuffer centered unique interface for a while now and am excited for it to become daily driver ready in the future. hamblingreen.com/ or rss.

    edit: let me know what you think about the framebufferphone idea by replying here or emailing me at hamblingreen at hotmail dot com

  43. another blog post is out, this time a spotlight on the #framebufferphone UI available on #pmOS and soon(tm) #danctnix arch ARM! i've been working on porting this framebuffer centered unique interface for a while now and am excited for it to become daily driver ready in the future. hamblingreen.com/ or rss.

    edit: let me know what you think about the framebufferphone idea by replying here or emailing me at hamblingreen at hotmail dot com

  44. another blog post is out, this time a spotlight on the #framebufferphone UI available on #pmOS and soon(tm) #danctnix arch ARM! i've been working on porting this framebuffer centered unique interface for a while now and am excited for it to become daily driver ready in the future. hamblingreen.com/ or rss.

    edit: let me know what you think about the framebufferphone idea by replying here or emailing me at hamblingreen at hotmail dot com

  45. another blog post is out, this time a spotlight on the #framebufferphone UI available on #pmOS and soon(tm) #danctnix arch ARM! i've been working on porting this framebuffer centered unique interface for a while now and am excited for it to become daily driver ready in the future. hamblingreen.com/ or rss.

    edit: let me know what you think about the framebufferphone idea by replying here or emailing me at hamblingreen at hotmail dot com