My Pinephone is currently running Mobian and I have been playing with docking to my Nexdock lapdock. Using a usb-c connection from the booted phone to the usb-c connection on the lapdock does connect. The dock icon on the phone shows connection and I see the Debian background screen on the Nexdock. When the phone is in portrait mode the touchpad (pointer) can be moved over to the phone and used to click on apps and navigate around the screen. When an app is launched (ie Terminal) the keyboard on the Nexdock can be used to type on the phone. 
If the phone is turned to landscape mode the screen image on the phone then becomes the screen image on the Nexdock and it is like working with a 14" screen for the Pinephone. It is interesting to note that in this mode the cursor image stops at the edge of the Nexdock and will not move to the Pinephone as it did in portrait mode. I am in the process of increasing my Linux skills (noobie) so being able to work the Pinephone with a keyboard and mouse (touchpad) is fun.
An additional plus is the Nexdock charges the Pinephone. Since I have ordered the new keyboard from Pine64 I look forward to increasing the battery life of the Pinephone.

Hi,
I tried a TS-100 tip in my Pinecill today as I'd read they were compatible but it didn't seem to work correctly, it started to heat up but the tip temp. was reading over 300 Degrees C when it was probably only around 70 or so and the wattage was really low as if it had stopped heating because it had reached temperature ... but it hadn't.

I checked the resistance of the tip between the two connection rings and it was just under 10 ohms, when I tested the continuity between the top ring, nearest the tip, and the tip body it was a short circuit on the TS-100 tip but open circuit on the Pinecil original tip.

Anyone have any ideas what the issue is, should it be connected to the tip body?

Cheers

I would like to know what will be the future of Mobian, some sort of "stable sid" or will it be like Debian on the desktop in terms of development? Maybe something in the middle of unstable, testing and stable?

Since I have a PinePhone on the way, I decided to order the necessary accessories. Several people have advised buying additional batteries to compensate for the relatively shorter battery life compared to the average conventional smart phone.

The Pine64 store indicates that replacement batteries are "Out of stock". Does the Pine team plan to obtain more stock? If so, what is the estimated time that the stock will be available for purchase?

Thanks.

My carrier must define a single APN for the web, sms and mms, which is why I have to configure my APN directly without going through "settings" etc

With arch phosh, where are the APN configuration files to directly edit the file for a new or delete the old APN

Anyone know yet if the "jumpdrive" process works on pinephone pro as it did on pinephone.  I am also wondering if it is known whether "balenaetcher" works on pinephone pro.

thanks,     tom kosvic

Hi Everyone

Today I got the keyboard delivered, but I cannot make it to work.

1. I see in many places to press the button on the keyboard (dis-attached from the phone), to turn it on/off, does it have any indicator light to show its status?
2. How to test if keyboard unit is working on it's own?

And I do not know if this is relevant, I'm an owner of a ubports CE version, but I installed PostmarketOS on it.

I am having some problems with bluetooth on my Pinephone running phosh. The bluetooth icon shows that bluetooth is on, and bluetoothctl seems to indicate that bluetooth is working fine - list shows the adapter and devices shows a list of the known devices. However if I select bluetooth from the Settings menu it will either show:
1. that bluetooth is turned off and changing the top right switch has no effect.
2. that bluetooth is on but the devices list is never shown.
3. the devices list is shown, connecting a device shows the device connected and then .... nothing. The device is not connected and often we go back to item 1.

I am not sure what bluetooth manager the Settings menu uses, but it would seem that it may need re-installing.

Does anyone have the slightest idea what is going on?

Thanks

Hi,

Although I've managed to boot a custom kernel and recovery image using a combination of rkdeveloptool and fastboot, I noticed that on the 'stock' android firmware adb has been configured in 'production mode' and won't let you run 'adb root' to gain root access to android - this is an accident, right?  The dev documentation seems to expect the device to not be in production mode and for 'adb root' to work.

Can we get an 'update' to the stock image that turns off 'production mode' so we can tinker with that environment?

Thanks

Edit: Never mind I managed to get the stock android rooted using magisk - after realizing my boot.img I fed it initially was incomplete, leading me to think magisk was to blame for making android unbootable. All good now

On the wiki ( https://wiki.pine64.org/wiki/Quartz64 ) it mentions installing Debian testing userland.

Is it possible to do this without touching an existing 4.19 based boot partition (so keep the existing working kernel and dtb file)?

How do I actually do it?