| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,557
» Latest member: tadonic
» Forum threads: 16,212
» Forum posts: 116,975
Full Statistics
|
| Latest Threads |
Why projects like PinePho...
Forum: General Discussion on PinePhone
Last Post: Gary2003
4 hours ago
» Replies: 13
» Views: 8,132
|
Cannot flash the modem fi...
Forum: Mobian on PinePhone
Last Post: anonymous
4 hours ago
» Replies: 7
» Views: 1,567
|
Star64 Irradium (based on...
Forum: Getting Started
Last Post: mara
5 hours ago
» Replies: 8
» Views: 4,847
|
the self built bl602_boot...
Forum: Getting Started
Last Post: pinecheng
7 hours ago
» Replies: 0
» Views: 210
|
Pinecil V2 - Getting “No ...
Forum: General
Last Post: powerscrews
Today, 02:07 AM
» Replies: 0
» Views: 383
|
Mobian MMS/SMS text probl...
Forum: Mobian on PinePhone
Last Post: georgegohl888
Yesterday, 02:42 AM
» Replies: 16
» Views: 20,431
|
Default password for KDE ...
Forum: General Discussion on PinePhone
Last Post: Toni
09-14-2025, 06:35 PM
» Replies: 0
» Views: 1,199
|
My Phone stopped making a...
Forum: PinePhone Hardware
Last Post: tracyanne
09-14-2025, 03:30 PM
» Replies: 0
» Views: 1,415
|
StarPro64 Irradium (based...
Forum: Getting Started
Last Post: mara
09-14-2025, 01:56 PM
» Replies: 9
» Views: 4,014
|
Can use PlayStation on Pi...
Forum: General Discussion on PinePhone
Last Post: ChaiLetters
09-13-2025, 12:30 AM
» Replies: 7
» Views: 8,154
|
|
|
| glmark2 benchmark on wayland |
|
Posted by: Henry - 05-18-2021, 10:23 AM - Forum: Linux on Pinebook Pro
- No Replies
|
 |
I ran the `glmark2-es2` and `glmark2-es2-wayland` benchmarks (on Manjaro with Plasma Wayland and mesa 21.1.0). Surprisingly, I got radically different results:
Code: ❯ glmark2-es2 --fullscreen
=======================================================
glmark2 2021.02
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali T860 (Panfrost)
GL_VERSION: OpenGL ES 3.0 Mesa 21.1.0
=======================================================
[build] use-vbo=false: FPS: 418 FrameTime: 2.392 ms
[build] use-vbo=true: FPS: 443 FrameTime: 2.257 ms
[texture] texture-filter=nearest: FPS: 456 FrameTime: 2.193 ms
[texture] texture-filter=linear: FPS: 460 FrameTime: 2.174 ms
[texture] texture-filter=mipmap: FPS: 454 FrameTime: 2.203 ms
[shading] shading=gouraud: FPS: 365 FrameTime: 2.740 ms
[shading] shading=blinn-phong-inf: FPS: 353 FrameTime: 2.833 ms
[shading] shading=phong: FPS: 283 FrameTime: 3.534 ms
[shading] shading=cel: FPS: 278 FrameTime: 3.597 ms
[bump] bump-render=high-poly: FPS: 254 FrameTime: 3.937 ms
[bump] bump-render=normals: FPS: 444 FrameTime: 2.252 ms
[bump] bump-render=height: FPS: 440 FrameTime: 2.273 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 221 FrameTime: 4.525 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 76 FrameTime: 13.158 ms
[pulsar] light=false:quads=5:texture=false: FPS: 462 FrameTime: 2.165 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 71 FrameTime: 14.085 ms
[desktop] effect=shadow:windows=4: FPS: 368 FrameTime: 2.717 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 88 FrameTime: 11.364 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 96 FrameTime: 10.417 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 174 FrameTime: 5.747 ms
[ideas] speed=duration: FPS: 82 FrameTime: 12.195 ms
[jellyfish] <default>: FPS: 195 FrameTime: 5.128 ms
[terrain] <default>: FPS: 13 FrameTime: 76.923 ms
[shadow] <default>: FPS: 144 FrameTime: 6.944 ms
[refract] <default>: FPS: 43 FrameTime: 23.256 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 421 FrameTime: 2.375 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 243 FrameTime: 4.115 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 421 FrameTime: 2.375 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 323 FrameTime: 3.096 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 218 FrameTime: 4.587 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 318 FrameTime: 3.145 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 324 FrameTime: 3.086 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 226 FrameTime: 4.425 ms
=======================================================
glmark2 Score: 278
=======================================================
and
Code: ❯ glmark2-es2-wayland --fullscreen
=======================================================
glmark2 2021.02
=======================================================
OpenGL Information
GL_VENDOR: Panfrost
GL_RENDERER: Mali T860 (Panfrost)
GL_VERSION: OpenGL ES 3.0 Mesa 21.1.0
=======================================================
[build] use-vbo=false: FPS: 117 FrameTime: 8.547 ms
[build] use-vbo=true: FPS: 141 FrameTime: 7.092 ms
[texture] texture-filter=nearest: FPS: 156 FrameTime: 6.410 ms
[texture] texture-filter=linear: FPS: 144 FrameTime: 6.944 ms
[texture] texture-filter=mipmap: FPS: 147 FrameTime: 6.803 ms
[shading] shading=gouraud: FPS: 108 FrameTime: 9.259 ms
[shading] shading=blinn-phong-inf: FPS: 119 FrameTime: 8.403 ms
[shading] shading=phong: FPS: 100 FrameTime: 10.000 ms
[shading] shading=cel: FPS: 97 FrameTime: 10.309 ms
[bump] bump-render=high-poly: FPS: 124 FrameTime: 8.065 ms
[bump] bump-render=normals: FPS: 130 FrameTime: 7.692 ms
[bump] bump-render=height: FPS: 124 FrameTime: 8.065 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 105 FrameTime: 9.524 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 67 FrameTime: 14.925 ms
[pulsar] light=false:quads=5:texture=false: FPS: 128 FrameTime: 7.812 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 49 FrameTime: 20.408 ms
[desktop] effect=shadow:windows=4: FPS: 117 FrameTime: 8.547 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 58 FrameTime: 17.241 ms
[buffer] columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata: FPS: 70 FrameTime: 14.286 ms
[buffer] columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map: FPS: 82 FrameTime: 12.195 ms
[ideas] speed=duration: FPS: 66 FrameTime: 15.152 ms
[jellyfish] <default>: FPS: 88 FrameTime: 11.364 ms
[terrain] <default>: FPS: 12 FrameTime: 83.333 ms
[shadow] <default>: FPS: 66 FrameTime: 15.152 ms
[refract] <default>: FPS: 42 FrameTime: 23.810 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 126 FrameTime: 7.937 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 97 FrameTime: 10.309 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 161 FrameTime: 6.211 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 124 FrameTime: 8.065 ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 103 FrameTime: 9.709 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 114 FrameTime: 8.772 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 100 FrameTime: 10.000 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 97 FrameTime: 10.309 ms
=======================================================
glmark2 Score: 102
=======================================================
Is the discrepancy to be expected, or is something amiss in my configuration?
|
|
|
|
| Vertical Grey Bars on PBP Reboot |
|
Posted by: MickTheGeek - 05-18-2021, 09:41 AM - Forum: General Discussion on Pinebook Pro
- Replies (5)
|
|
Hello all. I'm still having problems when I reboot my PBP. When I do, I get a screen with grey vertical bars and it just stays in that state until I shut it off with the power button. I posted back in October of 2020 when I first started having this problem, but the only solution available at the time was to just do a shutdown and power back on the machine to restart it, and a kernel update or fix would come it the future. Is there a fix for this issue, and if so how do you fix it. I have a PBP ANSI running up to date Manjaro. Any help/info is appreciated. Thanks.
/Mike
|
|
|
|
| chats not working |
|
Posted by: rvh - 05-18-2021, 07:48 AM - Forum: Mobian on PinePhone
- No Replies
|
|
the last time this happened the only way to fix this i could figure out was to reinstall the OS. thats kind of a nuclear option. Is there any other way to get it working?
|
|
|
|
| no 911 |
|
Posted by: rvh - 05-18-2021, 07:42 AM - Forum: Mobian on PinePhone
- Replies (6)
|
|
i had to call 911 and to my surprise, the call wouldnt go through. Is there a way to fix this?
|
|
|
|
| PWM whine near earpiece in low signal phone call and loud sound sent to the other end |
|
Posted by: vortex - 05-17-2021, 05:47 PM - Forum: PinePhone Hardware
- Replies (29)
|
|
For reference, my phone is a Beta Edition Convergence PhonePhone (1.2b hardware). I am running Mobian with the following modifications:
- Running 5.11 kernel
- Flashed the anx7688 with the latest firmware
- Installed crust-firmware package
In all of this, I was calling a land line.
Today, I had my first chance to see the PinePhone in action with phone calls in a location with very poor reception. Many places there have no reception. Many other places a phone has to drop to 2G. 4G in a few places, though it is marginal. This was the pattern with my old phone (Nexus 5), and is the pattern with my new PinePhone. At first glance, it looks like my PinePhone is doing a bit better reception wise than my Nexus 5.
Yesterday, I called the landline from a location with good reception and there were no problems. I also did the same earlier tonight at the same location to check, and had no problems.
But in the location today with bad reception, there were major problems that were strongly correlated with the reception.
On my end, there was a loud sound coming from inside the PinePhone case near the earpiece. The sound seemed like PWM whine. So I think it is a switching power supply and a capacitor combination. It quite bad in one location. I moved to another location with better reception and it decreased some. I ended the call and tried again in a location outside with slightly better and the sound was a lot quieter, and I could make it slightly quieter by rotating myself so it would aim in certain directions. My Nexus 5 makes a similar sound but much quieter even in poor reception, and has a similar pattern.
On the other person's end was much worse. They said a very loud sound was coming through on their end which made it even harder to understand me than the sound on my end made it hard to understand them, though my voice was coming through better than on my old Nexus 5 except for the added loud sound. The intensity of the sound decreased as the signal quality improved. From how they described the sound later, it seems like it might have been RF pickup in the microphone line or the sound connection line to the modem. Tomorrow, we are going to attempt to record the sound on their end so I can listen to it and try to figure out more.
Based on the pattern, I think that the sound on my end and the pickup causing loud sound to be transmitted to the other end are due to the increased transmission power as the signal quality decreases. In the worst reception area, the modem is operating at maximum and the problem is at its worst.
For the PWM whine on my end, I am doubtful there is a software solution. Only possibility would be if the PWM frequency is controllable from software. But the PWM whine on my end isn't too terrible (it is tolerable). For the noise transmitted to the other end, it is possible that the settings of the modem, CPU, and sound hardware may have some tangible effect; but I don't know. There is more likely to be a solution, though than for my end.
Hardware wise, assuming I am not the only one with this problem and that the electronics causing it are not inside the modem itself, it might be possible to reduce by finding the particularly switching supply and changing it to a different one as well as changing the capacitor to one that will make less noise (hopefully the capacitor is easy to get to because then it would be possible for the brave to desolder it and solder a new one on). That by itself my reduce the problem to no longer be an issue. The RF pickup can probably also be reduced in other ways.
Anyone have any ideas on this and/or have experienced it?
|
|
|
|
| Fraud Warning on purchase attempt? |
|
Posted by: kriscj - 05-17-2021, 10:28 AM - Forum: General
- No Replies
|
|
Hello, Pine community.
I attempted to buy a pinephone this weekend (mid-May, 2021) using my credit card and was declined, and knowing my finances are OK, asked the bank the reason for the decline. They stated that the purchase was blocked because the vendor has a history of fraud reports against them.
Now I'm not sure what to do... I could probably go through PayPal, but SHOULD I? I love the idea of the pine universe of devices and am an IT guy, so I'm a good early adopter, but this fraud warning has me really worried.
Interested to hear your experiences and opinions on the matter, please?
|
|
|
|
| OpenBSD 6.9 install |
|
Posted by: StickyPine - 05-17-2021, 02:30 AM - Forum: BSD on Pinebook Pro
- Replies (18)
|
|
Hello,
I attempted to install OpenBSD 6.9 on the PineBookPro. I essentially followed those steps https://github.com/ndhwyd/roc-rk3399-pc_openbsd and changed rk3399-roc-pc.dtb with rk3399-pinebook-pro.dtb.
When starting the machine, the booting process halts with the following message:
Code: bwfm0: failed loadfirmware of file brcmfmac43456-sdio.rockchip,rk3399-evb.bin
(I have the same issue when using rk3399-roc-pc.dtb)
Has anyone experienced something similar or would know how to solve this ?
|
|
|
|
| PINE A64 AUDIO DAC POT BOARD On A64 LTS w/ Armbian FOCAL |
|
Posted by: A64mediaplayer - 05-16-2021, 11:43 AM - Forum: SOEdge Hardware
- No Replies
|
|
Hi Folks!
Setup an A64 LTS board with Armbian focal and trying to get the Pine DAC POT running. Any insight into the method to make this work?
Is it via dt-overlay like in raspian ... or something else? I am assuming this is possible since the Volumio image claims to work ...
Thanks!
|
|
|
|
|
