Hi there. I have finally received my Pinebook Pro recently, so i started playing around with it. However, i have encountered extremely frustrating bug with its keyboard and touchpad firmware: for some reason, from time to time it starts thinking that shift is pressed. Sometimes pressing right shift sets it back to normal behavior, but not for long. I am pretty sure it's not a physical defect: external keyboard acts in a similar way. I have tried to update my firmware with pinebook-pro-keyboard-updater, but that killed my touchpad. Any ideas how to fix that?

At least until the end of the year

https://community.e.foundation/t/e-os-po...ne/9710/40

Greeting,

I wanted to install PmOS with sxmo as described here
https://git.sr.ht/~mil/sxmo-docs/tree/ma...LLGUIDE.md
in order to eventually, make some modifications to the installation I want. Sadly, I failed in step 0 of this plan.

The phone does not show up under lsusb, even if I try the telnet debug solution from
https://wiki.postmarketos.org/wiki/Inspe..._initramfs
I assume I did something wrong in the pmbootstrap, but I would not know what. I have had not problems with the telnet by jumpdrive.

I did not give up here, and I tried to install sxmo-ui before flashing, by using pmbootstrap chroot -r and following the instruction there. This works within chroot, if you follow the instructions from the sxmo website, but pmbootstrap install fails afterwards with
Could not find dependency 'sxmo-dmenu' in any aports folder or APKINDEX.
despite the fact that cache folder now contains the sxmo*.apk files.

I would be grateful if anyone can provide some insight as to what might be causing these problems.


cheers
IV

I did the cc fix (removed two switches on the motherboard) on my PP BH in order to enable USB OTG and hdmi output. Booting the recent factory image flashed new firmware and ran tests just fine indicating I did not destroy anything in the process. I hooked up my cheap USB C hub and mouse and keyboards works fine. Oh how lovely it is to use the terminal with a physical keyboard! The hub even charges the PP while connected. 

Hdmi output did not "just work" and I need help with it. I got Mobian on emmc which requires (according to the mobian wiki) the internal screen to be disabled in order to get hdmi out working. My goal is to extend the desktop like on Martijn´s convergence video. So I booted Danct12´s Arch (Thank you @Danct12 for your hard work!) from sd card and installed wlr-randr. With the monitor attached it gives this output:


  wlr-randr_1.jpeg (Size: 125.01 KB / Downloads: 1179)

The monitor (HDMI-A-1 Asus VG249) is recognized and is enabled (I can move the mouse to the right as if I´m moving it over to the Asus monitor) but the monitor says No signal. I have tried a few different refresh rates and resolutions that is supported according to wlr-randr but still no sight of life on the Asus monitor. It does however wake up when I attach the hdmi cable so there is some connection. Disabling the internal (DSI-1) display have worked for some people but since I don´t have ssh I argue that I need the display on the PP. 

If someone have had success making both internal and external displays working like in Martijn´s video, please share how you did it. And if someone has any questions for me, please ask!

EDIT: I tried with my TV as well, but its the same thing. TV is enabled but shows No signal.


  wlr-randr_2.jpeg (Size: 125.01 KB / Downloads: 926)

EDIT2: Success! Setting 1280x720@50Hz enabled the external monitor! The result seems very random though because trying again with the same settings did not work. Reboot, fiddle, then it worked again. Until the phone froze that is. Non the less, this is a success and proof that it actually works! I have a video but cant upload it to the forum.


  wlr-randr_3.jpeg (Size: 87.31 KB / Downloads: 923)

Video showing internal and external screens enabled:
https://youtu.be/x9klL7PyvS0

I've definitely seen some messages on here that seem to be from members of the UBports team, but its been looking somewhat sparse over the last few days. This is where most users and community members seem to exchange info, bugs, ideas, requests, fixes etc. Im sure some UB ports members are here but it would be great to see more active involvement addressing individual threads where they may have insight, learn, or find ideas of how to improve. Perhaps they already are but sometimes saying "don't worry, we're on it" or "great idea, we'll explore it" would be super!

A bulletin of changes for each update or what's in the works and expected release dates would be a cool alternative too

Good day
is there any way I can switch off the led light on the phone, the blue one
regards

Not sure if this has been discussed, or if this is "too political" or not PC to talk about around these parts, but has there been any?

More and more, I'm starting to look for items made and produced outside of mainland China.  I understand that certain components would be hard--if not impossible to source--but it's nice to a see a "Made in the UK" stamp on a RPi box/board or "Made in Korea" on HardKernel's products, for example.  Yeah, I love how open source everything w/ Pine64 it still bugs me.  Yeah, I realize it's a complicated topic wrt cost, logistics, etc.

Sorry, if this has been posted before.

Not sure why but data only seems to work if you only have one set of APN settings. This means for now if you try setting up both mms and data APN settings, neither will work. Even if you turn one off, it's existence will block the other. Im guessing most will prioritize data these days so if you have put mms settings in, for now you'll need to delete them completely, not just turn them off. Then restart and enter your carriers data APN settings and you should be good to go.

At some point this bug should be addressed so we can have multiple APN settings.

Btw, im curious. If we manually enter APN settings rather than auto, how does that affect our connection when travelling/roaming outside our network?

Hi everyone!
Okay so very pleased now. Over the last couple weeks with some tinkering and a few OTA updates much of my Pinephone is working and almost ready to be my daily driver.

The following now work:
Calls
Text
Data
Bluetooth incl. Audio
Gps (although not stable - must be manually initialized through terminal each time, can UBports include this in next update?)

Most of the other glitches i encountered appear to be ironed out.

Looks like camera is the one outstanding thing most people will care for.

What else do i need?
Im sure as a community we will find more things we are missing/need or want, but for where we are and whence we've come, this is pretty great!

2 little things that would be really nice are in-call volume control, although not too critical since i can hear the other party anyway. And if screen brightness could be made to go dimmer too. I find the pinephone screen incredibly bright, even on it's lowest setting. Makes me feel like im going to go blind once the sun sets... A night mode/ blue light filter would be nice too!

Hello,

I've been poking around PineBook Pro for some time, and one of the issues is the battery charging current, which is way too low at slightly under 3 A at 5 V.  It even gets ridiculous, e.g. the battery pretty much never charges back to 100% once you try to recharge it from an empty state while still using the PBP.  Not to mention that the battery discharges when running higher CPU loads, which is both ridiculous and very bad for the battery life.

So, I took some time to investigate the PBP's wiring diagrams, trying to isolate the culprit.  In a few words, the good news is that everything points into that increasing the max. battery charge current should be a relatively easy mod.  It could even be incorporated into the next revision of the main PCB.  The bad news is that a mod like that must be discussed first.

The PBP's battery can easily take up around 5A during the constant-current part of the charge cycle, which is according to its data sheet.  The PBP's battery charger IC is configured to think that the system current is always zero, which means that only the max. charge current needs to be tweaked; again, this is according to its data sheet, page 17 in particular.  The PBP wiring diagram, page 11 in particular, shows the way the BQ24171 IC is configured, as already described.

In a few words, increasing the battery charging current to 4A would be pretty simple; all that's required is to replace the R44, R45, R47 and R48 SMD resistors, so their values configure the BQ24171 IC to take 4A from the charger (IACSET) and output 4A (ISET) as the battery fast-charge current.  Of course, any chargers providing less than 3A could not be used any more, which would render the factory-provided barrel-type charger useless; however, I don't think anyone would complain.

I cannot see anything that would prevent this mod from being successful.  The PCB traces designed for 3A can easily handle 4A, which isn't a huge increase of the current.  Maybe the F1 fuse would also need to be replaced, but I don't know that for sure because its max. current isn't available from the wiring diagram.

Thoughts?