| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,422
» Latest member: fnosai
» Forum threads: 16,178
» Forum posts: 116,806
Full Statistics
|
|
|
| Size of the phone |
|
Posted by: PierreB - 05-30-2021, 06:32 AM - Forum: General Discussion on PinePhone
- Replies (1)
|
 |
Question: What are the community intentions about the size of the Pine64.
Question: Will it change size periodicaly (design crazyness), are remain stable over time.
Question: Will I be abble to keep the device for at least 5 years.
I dont fill like interested anymore being force to change device every two years (800$) because of design changes that brings up size modifications in the physical stack (sandards or what ever).
Thank you!
|
|
|
|
| Screen recording on PlaMo |
|
Posted by: ryo - 05-29-2021, 07:52 PM - Forum: Manjaro on PinePhone
- Replies (5)
|
 |
After receiving my 2nd Pinephone recently, I noticed that while wf-recorder works flawlessly on Phosh, it doesn't work on PlaMo.
On PlaMo I'm getting:
Code: compositor doesn't support wlr-screencopy-unstable-v1
OBS gives me:
Code: 5月 30 10:51:01 plasma-mobile systemd[4002]: Started OBS Studio - Streaming/Recording Software.
5月 30 10:51:03 plasma-mobile obs[4976]: QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_clicked()
5月 30 10:51:03 plasma-mobile obs[4976]: QMetaObject::connectSlotsByName: No matching signal for on_advAudioProps_destroyed()
5月 30 10:51:03 plasma-mobile obs[4976]: QMetaObject::connectSlotsByName: No matching signal for on_actionGridMode_triggered()
5月 30 10:51:03 plasma-mobile obs[4976]: QMetaObject::connectSlotsByName: No matching signal for on_program_customContextMenuRequested(QPoint)
5月 30 10:51:03 plasma-mobile obs[4976]: QMetaObject::connectSlotsByName: No matching signal for on_transitionRemove_clicked()
5月 30 10:51:04 plasma-mobile systemd[1]: Started Process Core Dump (PID 4988/UID 0).
5月 30 10:51:08 plasma-mobile systemd-coredump[4989]: [?] Process 4976 (obs) of user 1002 dumped core.
Stack trace of thread 4976:
#0 0x0000ffff9998d5d0 n/a (n/a + 0x0)
#1 0x0000ffff9b70d5e0 gl_platform_create (libobs-opengl.so.0 + 0x65e0)
#2 0x0000ffffbc2c3d60 n/a (libobs.so.0 + 0x4ed60)
5月 30 10:51:08 plasma-mobile systemd[1]: systemd-coredump@2-4988-0.service: Deactivated successfully.
5月 30 10:51:09 plasma-mobile systemd[1]: systemd-coredump@2-4988-0.service: Consumed 2.820s CPU time.
5月 30 10:51:09 plasma-mobile systemd[4002]: app-com.obsproject.Studio-366aeb3398934904a71d5ce492e25f60.scope: Deactivated successfully.
5月 30 10:51:09 plasma-mobile systemd[4002]: app-com.obsproject.Studio-366aeb3398934904a71d5ce492e25f60.scope: Consumed 3.505s CPU time.
And Green Recorder despite being advertised by the Arch Wiki as supported by Wayland seems to require X.org in order to function.
|
|
|
|
| apk abort, util-linux-2.36-r0 |
|
Posted by: spartacus - 05-29-2021, 08:15 AM - Forum: PostmarketOS on PinePhone
- Replies (1)
|
|
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?
|
|
|
|
| Convergence beta edition for sale - UK |
|
Posted by: AndroidMancave - 05-29-2021, 04:31 AM - Forum: General Discussion on PinePhone
- Replies (2)
|
|
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.
|
|
|
|
Hardware video acceleration in Chromium on Manjaro |
|
Posted by: siemsenit - 05-29-2021, 04:02 AM - Forum: Linux on Pinebook Pro
- Replies (3)
|
|
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.
|
|
|
|
| The state of mainline hardware decoding |
|
Posted by: CounterPillow - 05-28-2021, 03:39 PM - Forum: Linux on Rock64
- Replies (17)
|
|
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:
Code: $ gst-launch-1.0 filesrc location=/home/fratti/ocean.webm ! matroskademux ! v4l2slvp8dec ! fakesink
Setting pipeline to PAUSED ...
Pipeline is PREROLLING ...
ERROR: from element /GstPipeline:pipeline0/v4l2slvp8dec:v4l2slvp8dec0: Driver does not support the selected stream.
Additional debug info:
../gst-plugins-bad/sys/v4l2codecs/gstv4l2codecvp8dec.c(172): gst_v4l2_codec_vp8_dec_negotiate (): /GstPipeline:pipeline0/v4l2slvp8dec:v4l2slvp8dec0
ERROR: pipeline doesn't want to preroll.
Setting pipeline to NULL ...
Freeing pipeline ...
It took me forever to find out how to build this simple gst-launch pipeline because their docs are more about API usage, so this will serve as reference for anyone who does a web search for this. Hello web searcher! Yes this is v4l2codecs related! That's the plugin, it's in gst-plugins-bad, fittingly enough.
What else is there?
There's a patchset for ffmpeg that implements the v4l2-requests API. This patchset no longer works, as it relies on the API as it was on older kernels. Since the API was and still is (as of 5.13) in staging, it's still in flux, though recently there have been talks of moving it to mainline proper. It does not look like the collabora person who posted the patchset is interested in upstreaming it any further at this moment, either because their contract stopped at that point or because it doesn't make sense to include it in ffmpeg while the API is still in staging.
The best you'll get if you do hack the patchset into at least building is some errors while decoding:
Code: [vp8 @ 0xaaaada6f4ec0] v4l2_request_queue_decode: set controls failed for request 29, Invalid argument (22)
[vp8 @ 0xaaaada6ff6e0] Discarding interframe without a prior keyframe!
[vp8 @ 0xaaaada702490] Discarding interframe without a prior keyframe!
[vp8 @ 0xaaaada705240] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Operation not permitted
[vp8 @ 0xaaaada707ff0] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Invalid data found when processing input
[vp8 @ 0xaaaada6f4ec0] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Invalid data found when processing input
[vp8 @ 0xaaaada6ff6e0] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Invalid data found when processing input
[vp8 @ 0xaaaada702490] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Invalid data found when processing input
[vp8 @ 0xaaaada705240] Discarding interframe without a prior keyframe!
Error while decoding stream #0:0: Invalid data found when processing input
This is marvellous, but it's no video.
This post is basically here to let everyone else know that trying right now is a pointless exercise. What appears to need to be done is:
- 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?!)
- mainline the v4l2-requests api
- write a mergeable patchset against the mainline API for ffmpeg
- you now get hwdec in mpv for free, thanks to ffmpeg
Alternative path to the goal:
- 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
- never get it merged anywhere because they'll just point to the broken pile of v4l2-requests bits and tell you to use those
- 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.
What I'd appreciate is the following info:
- 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
|
|
|
|
| Daily alarms? |
|
Posted by: atleastitried - 05-28-2021, 12:52 PM - Forum: General Discussion on PineTime
- Replies (1)
|
|
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.
|
|
|
|
|
) welcome.
