i have to limit util-linux to version 2.36-r0 (apk add util-linux=2.36-r0) to prevent apk from aborting upgrade.  Otherwise it tries to upgrade to util-linux-2.36.2-r2, which results in a conflict.  I had several similar upgrade issues which I was able to correct by removing obsolete programs; however, I have failed to locate the program requiring util-linux-2.36-r0.  Has anyone else had or solved this conflict?

Basically unused. 1 month old. Running Mobian. All working as well as expected and battery takes full charge.
Hoped I could use it as daily phone but it's not to my liking.
I supported the project by buying and now it seems like an expensive ornament so looking to sell in the hope someone can make better use and actually contribute to the project.
I've installed the OS, connected to wifi, checked out some apps and updated the OS. That's all I've done with it. As I said, basically unused.
Happy to post in UK. £165 inc tracked postage. All customs duties already paid on initial purchase. Available now.
All original items - box, lead, hub connector, leaflets etc. As new.
DM me if interested.

PineTalk is a PINE64 Community Podcast you may have heard of (and hopefully listened to).


Every two weeks, Ezra and I sit down to discuss PINE64 hardware, software developments and open source in general.

This thread is meant to offer another way to send in your questions and feedback. We will answer them during the show … when we get to it

Earlier today, when i was bored, I turned on "Hardware-accelerated video decode" and "GPU rasterization" in Chromium browser ( chrome://flags ). To my surprise, it actually worked well, bringing CPU load to 80% when playing plain H.264, compared to 160% before.

I am currently Manjaro 21.05 with GNOME 40 on my Pinebook Pro.

I wonder if it works "just for me", so you guys might give it a try.

Current situation: stuff just works! As long as things implement the v4l2-requests API. See https://wiki.pine64.org/wiki/Mainline_Hardware_Decoding

Original post (no longer applicable)

Or "everything is forever terrible"

First off: I'm not talking about rkmpp. Do not reply to this thread about anything regarding rkmpp, or non-mainline images using rkmpp.

Basically, a sunk a few afternoons of investigating, tinkering and tearing my hair out into getting any hardware decoding working on this using the mainline kernel. My conclusion is that it doesn't work, and won't ever work unless someone puts some effort into making all the moving bits and pieces align.

Here's the farthest one can get, which is upstream gstreamer telling you that despite advertising vp8 decoding, it can't actually decode a vp8 file:

1. fix the kernel side for rk3328 so that they actually work(?) (I'm so unsure I don't even know if it's broken! Also why does it not say it can decode H.264 in gstreamer?!)
   
2. mainline the v4l2-requests api
   
3. write a mergeable patchset against the mainline API for ffmpeg
   
4. you now get hwdec in mpv for free, thanks to ffmpeg
   

1. passive-aggressively write a vaapi implementation for the hantro VPU, with no v4l2-requests bits at all because why introduce yet another userspace API for something like this that several other things already do
   
2. never get it merged anywhere because they'll just point to the broken pile of v4l2-requests bits and tell you to use those
   
3. this will also work on DRM, i.e. a terminal with no display server running, at least my AMD vaapi implementation can do this with mpv.
   

• ways to tell v4l2 to list all supported codecs/formats. Somehow, v4l2-dbg just does nothing or straight up ruins my terminal by writing binary to it. Good tool. All I want is "vainfo" but for v4l2-requests
  
• information regarding the v4l2-requests design, or where to find such information
  
• anecdotes of using v4l2-requests on any rk3328 on some upstream kernel
  
• information regarding what part of vaapi lives in the kernel, if any, and where one would get started writing a vaapi implementation for hantro without wrapping around v4l2-requests
  

As far as I can see there is no function for daily alarms, yet, is that correct?

Will there be a daily alarm function? Is it already in development?

I would like to see a daily alarm function that can handle an unlimited number of daily alarms (in contrast to conventional watches) and that doesn't need permanent BT connection to a smartphone or whatever.

I also think about that the PineTime could store calendary events on it's own so that it can remind the user of upcoming events. The event's would have to be synchronized with a companion device so that the PineTime can remind of events without beeing permanently connected via BT. I write this in this "daily alarms" thread because both functions may have intersections and could possibly be developed together.

Can a PineTime user manage apps (adding / installing, removing, updating / upgrading)? Maybe to how package management works on Linux?

Or do we have to flash a new image via OTA to get newapps or their latest versions?

And how does app management differ on the different PineTime OSs?

Thank in advance. Please continue the great work.

Hello 
I have a problem that  i think is software related  and not hardware related becuse  i dident notice this problem when i run Ubuntu touch.
Okej im going to try to explane, about 30-40% of the time when i lock the screen or when it lock itself when om going to wake it up again (pushing the home button) then its like the phone is dead but its starts direkt with the green led light and im back to enter the encryption key again and i when i have entered the encryption key the screen turns al black again and after 3-4 minuts i have to push the home button again and then its back to the lock screen where i just enter my pinkode(not the encryption key) and im in my phone again. And it seems like it reboot itself but it does not comes up Any  mobian logo or anything else like it usually do when i turn my phone on after i turn it off. And like i Said this happens pretty often so it little anoying to check something and try to open the lock screen and i have to wait for the phone to ”reboot” . This Does not  happenings everytime normaly i just wake it up and comes tho the lockscreen like a normal phone.Anyone else who has this issue? I run mobian Posh with full disk encryption and its the uppdatera version 3.38.5
Im sorry for bad english but i couldnt find anyting about this problem when i Google search. Om verry greatefull for answers thank u so much for this forum.

Hello, after trying manjaro-arm phosh, I decided to install mobian linux 11 bullseye and noted that the audio quality was pretty awful - lots of crackling noise and feedback!? The phosh worked best so far but the speaker volume was extremely low. Plasma-mobile was extremely echo-y and unusable.

I would like to know if this can be fixed and how to troubleshoot phone quality issues in general. In mobian when making a call, I got a pop-up with some options, mute, speaker, and one more. Will any of these settings help to get a decent sound quality on the phone. Lots of info on the mobian wiki page and quite organized so I would like to stick to this distro if possible. Thanks.

Source based Linux distribution CRUX-ARM adhering to ideology keep it simple, has its own package system, also supports the port system.

the image building system now supports slaсkwarearm, slarm64, crux-arm

crux-arm-3.6-aarch64-core-rock64-5.12.6-build-20210527.img.zst
crux-arm-3.6-aarch64-core-rock64-5.12.6-build-20210527.img.zst.sha256