Hello,

I have been testing and enjoying my new Pinebook Pro. I 've noticed however that 5Ghz Wifi is performing poor. I have activated both 2.4 Ghz and 5Ghz wifi on my home router. Things I 've noticed:

• There are times when 5Ghz wifi is not working at all - as if there's no wifi signal available. Devices next to the pinebook, such as a smartphone, work fine with 5Ghz wifi so I know the signal is good but PBP can't interface with it.
  
• I 've tested wifi speeds when both 2.4Ghz and 5Ghz are working in the Pinebook. The 2.4Ghz connection easily gets 4+Mbytes/sec while the 5Ghz oscillates between 500Kbytes/sec to 1.2Mbytes/sec.
  The network connection is 150Mbps.
  

I've created a fork of Mobian for testing purposes. I've built my own personal images with this for a few days now and I thought I might as well share it for anyone who's interested. I'm not supplying binary images for two reasons;

• This is not meant to replace regular Mobian for end users
  
• I'm stuck on a slow and metered connection
  

There are now PineTab chats available (all bridged of course):

IRC
Discord
Matrix
Telegram

Hi everyone,

So I have been in the possession of a braveheart edition pinephone some time now, With the recent developments now that the ubports community edition has come out, I have spent more time with it. It feels much more snappy than it did the last time I tried it and I am very impressed by all the hard work that has been done.

Recently, the devs got crust working, which promises to make my pinephone an actual usable device. For me, the extended battery life could mean that it can now become my daily driver. Yesterday I found a Reddit post saying that switching to the dev channel for OTA updates would enable me to use crust. So I did, and installed version 47. I noticed that there are multiple Development channels, but I'm sure I picked the one described in the post. Everything seemed to work fine. My battery life was not much better than it was before, though, but there were some people saying that crust was not yet enabled in version 47.

So I waited a day, and was eager to install version 48, hoping it would be the solution to my problems. I did experience even snappier UI, but the screen resolution was kind of messed up. It's a dev channel, so I know thinngs like that can be expected.

What does make me kind of sad though is that my phone will no longer boot. All it does when I insert the charging cable is give me the notification LED rainbow show like it normally does on boot and turn on the screen backlight for a second or so. Then it just shuts down and starts over.

Has anyone experienced the same problem? How do I fix it?

Hi all,

It's been quite some time since I last updated you on Mobian's status, and just over a month since the first Mobian release, so it's time for a short summary of what happened during that time 

The latest nightly build has been promoted to a reference release, as it brings quite a few improvements:

• Wake up on incoming call now also works on the CE
  
• GPS is automatically activated on boot
  
• /boot is now on a separate partition (this will be helpful if and when we decide to implement disk encryption)
  
• lots of packaged software have been upgraded to the latest available versions
  
• the image now includes a couple more useful software, as these have been improved for use on mobile phones:
  • Eye of Gnome (image viewer)
    
  • GNOME Authenticator (2FA)
    
  • GNOME Sound recorder
    
  • GNOME Todo (still WIP, UX is not perfect, but it's mostly usable, and can sync with Nextcloud)
    

I received a PBP a couple of weeks back, and generally I really like it. (Though I wish the code for the keyboard/clickpad controller was opensourced!  The trackpad lag makes the PBP “feel” a lot slower than it really is!)

I’ve been doing some larger software package builds (with make -j 6) with the PBP and have noticed that when I have heavy constant load on the CPUs, the internal battery begins to drain even when the unit is externally powered via the the 5V 3A barrel connector.  Is this normal or do I need to try and track down some other issue here?  

I apologize if this has already been covered; I did a couple of searches and didn’t find any information that really matched what I’m interested in.  I’ve seen some comments on this type of behavior when powering external USB devices, but not with CPU load.

If this is normal, I’m interested in tweaking some of the charger circuit setpoints and seeing if it improves things. (With a new power adapter of course!)  Looking at the schematic I see some potential spots that may be of interest.  However, without layout art and a complete BOM, it’s hard to say how much margin there is to increase the draw without risking CCA damage.

Is the screen expected to work with active stylii, or is it limited to passive?

For some reason, probably 'operator error' on my part, the main log-in password got changed and now I am not able to fully start my Pinebook Pro. Is there any way, outside of a full reinstall, to reset the main log-in password?
Thank you,
James Good

The wiki says [1] there are "USB-C CC pin issues" in Pinephone CE. Can anyone explain in plain text what this means and which problems I should expect due to that? I have no idea what the words in the subject mean. Should I cancel my order?

[1] https://wiki.pine64.org/index.php?title=PinePhone_v1.2

What is the maximum storage configuration for the PineBook Pro? How many internal drive ports does it have? Can Linux be booted from any of them or only one? Can boot operating systems from USB?

I don't think that information is available on the Wiki. Please add it.