Pretty much what it says in the title; 5.8 has lots of bug fixes and the ANX7688 driver. Latest update from the dev channel is still on 5.6 .

Spyder (spyder) 4.1.5-1 freezes on "Synchronizing package databases..."

spyder3-git 5.0.0.a1.r2.g36ff0882c-1 freezes on "Cloning python-pympler build files..."

Both require Pamac to be hard closed.

Any ideas?

I am new and just followed the get started. I went to login on the third time and it takes me to a strange login page. It has my user name in all CAPS and within an icon and when I enter password it does nothing. The enter key does not work only a refresh type icon at the top of page right side and a banner that says US and American Flag. What now?

I just had a 300MB or so update with my Manjaro build on PBP...

It looks like there were a lot of KDE packages and QT stuff, a wayland and some plasma stuff.... at any rate, I wonder if we got any good updates that help with functionality or issues that we had pointed out over the last week or so.

I'm gonna dig into system settings and see if any of those graphical 'glitches' got updated. I reported them to the Manjaro forums, but man that was just 4-5 days ago; made me go hmmmmmmm, tho.

Did you notice of find anything new? I'll poke around today. Cheers team Pine.

As per discussion in another thread, I'd like the community's input on whether we should remove users ability to up/down "reputation".
It appears that this system has been abused recently.

Hi,

I ordered a Pinebook Pro (ANSI) on september 11 2020, the order number is 149679, payment done with PayPal.

As I read on "Shipping", Pinebook Pro was scheduled to start shipping on september 21st and I would like to know if my order is shipped on this batch because I haven't received a shipment number so far.

Thank you!

I have been trying to get @megous  p-boot bootloader to work, for fun and also to try benefit from the safety fixes he has put in p-boot.

But so far I have no success. In short I have re-worked his example directory to try be my working config to be able to boot mobian from an SDcard and pmOS from the eMMC. I have got p-boot installed on the SDcard and at initial boot I get the p-boot menu screen with my 2 options, but selecting either of them I get the red LED temporarily then it goes out and neither OS ever loads sufficiently to show on the screen.

So obviously my boot.conf is duff but I am not sure why.

My boot.conf:

@Luke

Is there any way to permanently block someone? Due to my, and many others, responses to a certain forum individual they have been on a down vote/negative rating crusade and have sought out every post I have basically made in order to negatively rate them.

I have ignored that person via the control panel, but that has no effect judging by the 10 negative reputations in basically 2 days.

I mean I know reputation is fake internet points, but this is getting harassing.

Thanks in advance for any help!

I just recently received this Pinephone, here in Australia. Phone cannot make/receive calls & SMS, as it does not detect the telco's network - in fact, it clearly says "NO NETWORK". This was the case with the preinstalled version of Ubuntu Touch, and did not improve just now after I tried an updated version of UT I downloaded from UBports on 2nd Sept (#76, I think), and I followed UBPorts' directions for flashing the SD card.

Other things I've tried / checked:
Turning phone on / off
re-seating SIM card
SIM card works fine in another handset
DIP switches on the back of the phone are all in the 'up' position (I haven't touched them at all)

Any ideas?

Thanks,
Ken.
***

It all started with figuring out audio quality issues in the Mobian room over on the Matrix server.

Long story short, I messed around with gain settings but couldn't make it sound as expected. So I started digging around in the schematics and datasheets to see if there was a hardware issue. Turns out I was right; there are hardware issues.

Let's start in the middle with the centerpiece of the discussion, Broadchip BCT4717ETB-TR. This is an analog switch and in the PinePhone it's wired up to switch between headphone audio and debug serial. In the PinePhone v1.2 schematic on page 8 you can see it's connected to HPOUT_L/HPOUT_R on the A64 through inductors, to PB8-DEBUG-RX/PB8-DEBUG-TX on the A64 and to HP_L/HP_R on the headphone jack.

The issue here stems from the BCT4717ETB-TR being an analog switch. The way it is connected on the schematic implies it's being used as a non-inverting audio OpAmp even though it's meant for signaling. It lacks the linear properties of an audio OpAmp and the datasheet gain graphs don't even go below 1 MHz. The graphs cover 1 MHz to 1 GHz and 300 MHz is the point where it reaches -3 dB attenuation at 1.65 V_CC which matches up well with its rated bandwidth of 300 MHz. The graph isn't exactly flat in between which leads me to believe it's unlikely to be flat for lower frequencies as well, but that's still not the main issue.

The main issue is both the analog switch range and the output impedance. The analog signal range is specified as 0 to V+, which in our case should mean 0-3.3 V. That is sort of fine since we're using a virtual ground (connected to HP-FB on the A64) but it's a point of concern. The output impedance isn't explicitly defined but the output resistance is specified as 4 Ohm typical and 8.5 Ohm maximum. Together with the inductance that becomes a low pass filter, I haven't been able to find accurate data for our components in the audible range but the shape of the curve is inverse logarithmic. This could explain why the amplifier is so incredibly bass heavy. Furthermore even if we apply a constant impedance at 4 Ohms that's still way too high for most headphones you'd connect to a phone, which are somewhere in the ballpark of 8 to 40 Ohms at 1 kHz. This could lead to strange harmonics, especially at the lower end of that range.

Then there's yet another issue I discovered while trying to measure the DC offset which turned out to be in the mV range and too small to accurately measure with my old analog scope and a twitchy cable. After about 10 seconds of pausing the music the DC offset rose to a whopping 200 mV! This is not really a good thing if you leave headphones plugged in overnight as they typically don't like DC at all, let alone 200 mV.

This is about as far as I can go tonight, it's way past bedtime and I'm super tired but I wanted to get this written down somewhere before I forget the details. My conclusion for now is that someone needs to validate my results, if the 200 mV idle offset is reproducible on other units then we might need to issue a PSA about not leaving headphones plugged in when they're not in use. Furthermore I'd really encourage the hardware people to either use a proper headphone amplifier or separate out the debug serial port from the headphone jack.

I'll see if I can figure out a way of getting frequency response curves.