When I was looking at the included dock in the convergence package I noticed that it might not be ideal for convergence. Let me explain why.

The use case: 
 - You have the dock permanently on your desk connected to the monitor, power, keyboard, mouse, etc. And when you get to your desk you connect your pinephone with 1 cable to the dock and start working as if it where a desktop.

The problem: 
 - Now you are working while docked and you get a phone call.

The current options:
 - hold the phone to your ear with all the cables still attached (very awkward and clunky if at all possible as the lead of the dock is very short).
 - disconnect the pinephone from the dock to answer the call (you can't keep working in convergence while answering a call).
 - have a headset and answer the call using it (now you have to plug 2 cables to the pinephone as the dock does not have a jack).

Possible Solutions:
 - Replacing the lead of the dock with a connector so you can have a cable with the length you want.
 - Making the lead longer.
 - Having a headset or headphone and mic jack on the dock so you can have a headset always connected at your desk.

I know these solutions sound way easier than they are, as almost all if not all docks on the market have the current design (which is perfect for laptops but not for phones). So take these as just recommendations for the future :)


TL;DR: The lead of the dock included is too short for convergence use.

I was extremely happy to read the news that the Early Adopter editions would be coming soon. I've been holding the buttons on my Pebble 2 in place with tape for a while, and hoping that I could order a sealed PineTime with a bootloader and half-functional software before it finally quit. Alas, that was not meant to be.

I didn't want to order a dev kit because I have more projects than time already and really wouldn't be able to contribute much to the development effort, especially in these early days. Not that that's even an option right now, as the website shows they're out of stock.

I'm not here to complain about the website stock or the development, production, or release timelines. I'm not even here to beg for an update on the release schedule. The things'll be ready when they're ready.

Not being able to receive notifications on my wrist has left me feeling kind of naked, to say nothing of having to pull my phone out of its holster to find out what time it was. It's gotten to the point where I've started getting anxious.

If the dev kits were still in stock late last week, I probably would have bought one and tried to find a way around the fact that they weren't water-resistant. (at least to the "able to wash dishes or take a shower with it on" level)

If you were me, what would you do?

Either buy another Pebble or a low-end Wear-OS watch to tide me over?
Or just suck it up and wait until the Early Adopter PineTimes are available?

The Pinephone is a real computer in your pocket, and could eventually replace a notebook computer. But to be used as a mobile computer, one usb-c connector is too little. It is possible to add for instance a connector like this for mobile use:



https://de.aliexpress.com/item/330321893...gQRpH&mp=1




but this setup is not so stable. Integration of such an adapter by default in the Pinephone would make out of the Pinephone a real mobile computer, which could replace a notebook.

Please start by reading this blog post.
In this thread you are welcome to discuss and submit your PinePhone keyboard designs. I am well aware that myBB (the software running this forum) isn't particularly permissive of hosting various document types (e.g. it will not permit you to upload a .stl), so some portion of your idea(s) and design(s) will have to uploaded externally. You are also welcome to use our Wiki for the purpose of uploading project-related files.

Looking forward to seeing what you come up with!

Hi
Is there a way to suppress the trackpad when typing?
Sometimes my palm accidentally touches the pad when I'm in the middle of typing something, and in the worst case selects a block of text already written, and them my next key stroke overwrites it.
What I would really like is a feature that for n seconds or microseconds after the last key press that the trackpad just doesn't do anything.
If I don't press a key for n period of time then the trackpad would automatically start working again.
I'm on KDE on Manjaro and I'm new to both.
thanks DNJ

Calls are now stable but it seems there is only one volume. When i use the volume buttons i see it change on the screen, but the actual in call volume remains constant on the medium-low side.

I lost USB ssh access after a recent update (including kernel as I remember) into my UBPorts edition. Can't see the phone by lsusb, ip a, or dmesg. The situation is the same independent of OS (including postmarketOS without UI), either running from eMMC or SD card. Inspecting the initramfs via the debug-shell would not work. PostmarketOS troubleshoot suggests adjusting kernel configuration parameters referencing: CONFIG_USB_ETH CONFIG_USB_ETH_RNDIS CONFIG_USB_G_ANDROID.  Anybody know the appropriate parameters I should be looking for?

So I saw this tweet: https://twitter.com/LukaszErecinsk1/stat...3589531650

I tried to enable WebRender on my Firefox but it seems to fail to start up. I could make it past the start up if I overrode OpenGL version to 3.3 but Firefox becomes a huge graphical mess, so not really any better. I'm on Wayland, default Manjaro install, mesa-git driver.

in aboutupport I see this:

unavailable by runtime: WebRender initialization failed
(#0) Error Failed GL context creation for WebRender: 0

Anyone get it successfully working? Is it worth pursuing for the performance increase?

Not sure if anybody is curious or interested, but MS Powershell 7.0.3 works great out of the box on Manjaro KDE and PBP. (I have to use it for work now and again)

https://github.com/PowerShell/powershell/releases

Download

...linux-arm64...

or follow the linux binary instructions:

https://docs.microsoft.com/en-us/powersh...y-archives

I've come across a few posts about there being possible corruption of the firmware on the Pinephone modems. Are the only affected ones the one from the Braveheart Editions or does it occur on the UBports editions as well? Im not sure whats the deal with my UBports edition phone. It was not working when using UBports and even when it was updated I still had no cellular working. Then I tried Mobian and still it was not working. I ran the hardware test from a Postmarket OS image and it shows the modem status as ok.

Factorytest v0.49.0
Status: OK
Registration: not registered
IMEI: XXXXXXXXXXXXXXXX   (it shows but Im not posting it)
Firmware: EG25GGBR07A08M2G
Network: FDD LTE, 311480, LTE BAND 13
Signal: -81dBm

Sim Status
Status: Connected
IMSI: XXXXXXXXXXXXXXXX

Call Status
Status: Ready for call
Technology: ...
Number: ...

Im not sure what to make of it, with Mobian and UBports not working with my sim. I have thought if the results from the modem are faulty results.

(Edit 1) My cellular service is from T-mobile and I used a T-mobile sim card.
Edit 2:  Sim card size is micro

Update:
https://www.t-mobile.com/support/coverag...le-network  a link to T-mobile network bands.

https://www.quectel.com/UploadFile/Produ...n_V1.1.pdf   The Quectel modem pdf

Does anyone know if it might have something to do with the Network bands T-mobile uses in the Los Angeles Area?

Update: I installed and used LTE Discovery on a working android phone and it shows in my area that it connects mostly to band 2 and sometimes 66. Band 66 is not supported by the EG-25G modem.

Anyone know how to keep the modem to refuse or stop trying to connect to band 66?