Some days ago I noticed I cannot play videos anymore using mpv as it have become choppy even with low resolution videos (Firefox isn't affected). Downgrading Mesa to 22.2 fixed the problem. https://alaa.ad24.cz/packages/m/mesa/mes...pkg.tar.xz


Edit: After another Manjaro update, KDE Plasma regressed to software rendering so I had to update Mesa to 22.3. The solution was to put "vd-lavc-dr=no" to ~/.config/mpv/mpv.conf as described here: https://forum.manjaro.org/t/video-playba...k/130967/6

I cannot boot the PineTab from (happy) new (year) images with kernel version 6.1.

I tried:

 mobian

 postmarketos



On mobian I could install the 5.15 kernel.

I took this one: https://gitlab.com/mobian1/devices/sunxi...pe=archive



Maybe there are workarounds for the other operation systems too. Please let me/us know. Don't let the early PineTab die.



another thread for mobian: https://forum.pine64.org/showthread.php?tid=17772

Hello, gonna front-load this with an apology for my utter newbness, and probably a whole slew of subsequent dumb questions.

I have a thought and I would like to ask if this is something that is possible. I was thinking about how one could go about getting access to, or expanding, the GPIO resources for the Pinebook Pro. In my searching around for existing info, I found the following: 

https://forum.pine64.org/showthread.php?tid=4785

I'm not so enthusiastic about doing everything through the SD card slot like that, but I def appreciate that that user was able to really probe the system for that functionality like that. 

I had another thought: is it possible to create some kind of add-on board/card using the PCIe x4 connection, some kind of bridge chip, and possibly some kind of MCU or other supporting ICs, that one could install through the M.2 connection, and then create a port physically somewhere on the case (I'm actually thinking of somehow machining the aluminum bottom case somehow to do this but whole other can of worms)? A whole "GPIO board" mounted on that connection using that bus? 

Is that dumb? Crazy amount of work? I'm not even sure where to start, mostly just wanted a lot more GPIO/physical computing ability for this platform.

I have a Pinephone pro running mobian phosh. (Note this happened on other distros too) where i cant connect to my bluetooth devices but it can pair. What should i do to be able to connect to my devices? or am i screwed?

Hi everyone,

I've been reading sites and trying fixes for a while and I've been able to get Disney+ and Netflix running in chromium-docker on Manjaro. So far, I haven't figured out how to get Amazon Prime or Paramount+ working. Has anyone had any success with these? 

Thanks,
Tessa

I have a sealed PineTime, and today the screen stopped working properly, see the pictures below (quality isnt the best but it basically looks the same IRL).

Touch etc. still seems to work though, so i can go through the menus just fine. I run InfiniTime 1.11 and didn't bunk into something exceptionally hard with it nor do i swim/shower with it (except for the occasional hand washing where it might get splashed a bit). I already tried rebooting it which didn't help. Is there a way to fix this or should i just get a new PineTime?

The menu when swiping left:


The flashlight, activated:

I got a pinephone from someone turned it on and it has a pass code trying to flash it with a os but can't help please

I saw the Roshambo case on the Pine64 store. Trying to understand components and assembly.

I see that a power supply and board are required - RockPro64 is recommended. It says that the ssd "cartridge" is optional. I see that the board comes with 2 or 4GB RAM, but doesn't seem to have storage.
From the site - "There is also an optional eMMC module (up to 128GB) and microSD slot for booting." If the ssd is optional and the eMMC is optional, how is the R-Cade system installed/stored?

Other than the case, board, power supply, and a couple of controllers, is there anything else I would need?

Thanks

I was playing with picroft on my old RPI3 + AIY Voicehat and it was just too slow for some functions, so considering the difficulty obtaining an RPI4 w/o selling limbs, I wanted to try getting it up and running on the RockPro.

One of the reasons I grabbed the RockPro was the "PI-2" gpio connector that is, more or less, compatible with the Rpi 40 pin.  I was hoping to reuse the Voicehat (which provides a nice mic array and amplified speaker output).

Installing the Mycroft software was easy enough but I soon discovered that the driver that was written for the "googlevoicehat-soundcard" was, for some inane reason, held in the sound/soc/bcm area of the kernel and it's dts claimed it needed the RPI BCM processor (it's a dac/adc/amp combo it shouldn't be tied to a specific processor.

The driver is in Raspi but I don't think it was ever in mainline kernel, or if it was, it was dropped before Linux 5.

So, not being a kernel hacker, I've walked away from that idea.

I have ordered an inexpensive USB Speakerphone and will see how that works and update here.

I've been mostly-happily using the PinePhone with Mobian for a long while (years), with MMS working pretty smoothly for a long time. Recently (last 5 days or so), MMS sending has completely stopped working.

  - It didn't happen after making any big software change (apt upgrade, settings change, things like that).
  - Group message sending and 1-on-1 media sending no longer works
  - Group and media receiving still works totally fine
  - Back when MMS sending was working, I noticed that after hitting "send" on an MMS message, the screen brightness would always change for a moment (something to do with power draw to the antenna?). Now when I try to send MMS that doesn't happen.

Any idea what the problem could be?