PinePhone Developer edition

[MartijnBraam]

malvcr: The default password for the demo user for plasma images is 147147, this is labelled on the page where you download that image. (http://images.postmarketos.org/pinephone/)

Those images are only for testing, I recommend building an image with pmbootstrap for any production use.

The battery should trickle charge when the phone has power and the battery is inserted, the AXP803 has a charging mode for that.

[malvcr]

malvcr: The default password for the demo user for plasma images is 147147, this is labelled on the page where you download that image. (http://images.postmarketos.org/pinephone/)

Those images are only for testing, I recommend building an image with pmbootstrap for any production use.

The battery should trickle charge when the phone has power and the battery is inserted, the AXP803 has a charging mode for that.

Thank you ... to be sincere, I really don't remember where I downloaded the image, as it is really confusing to arrive to any download page from Pine64 place.  And in that moment I didn't pay attention to any "password" or similar.  Later, when I was checking information, the pointers sent me to wherever but that download page, that I see it is very important.

Maybe in Pine64 somebody must track where are things going with all known distributions, and to keep some updated page for easy browsing.  Some type of "index" or "quick access" page ... for not to travel through a lot of independent forum threads that offer many different options (they are for discussion and in the discussions are real and fake things mixed).

By now I have been trying to understand the "phone" and to think on possibilities with it (I have several on mind by now).  I will try the pmbootstrap as I see is an important part on all this process.

And thanks for the good work :-)

About the battery, there is something I must check with more care.  For a lot of time the recharging phase never arrived to 100% (just 99%).  But yesterday I let the phone connected for several hours and it was really hot at 97%.  That is a sensitive detail in any mobile device.

[malvcr]

Just some extra information that could be useful for people testing the phone using postmarketOS.

The modem name is "quectelqmi_1"

Commands of this type can interact with the modem using DBus:

dbus-send --print-reply --system --dest=org.ofono /quectelqmi_1 org.ofono.Modem.GetProperties


When using the testing image it is useful to install qdbusviewer:

sudo apk add qt5-qdbusviewer

And, to execute it from a graphical terminal with X11 forwarding (the pinephone screen without the auto rotation is useless in this case).


In my case, I want to use the "ofono" interface directly without the included phone software.  I am not a fan of DBus but if there is no other way, is ok (by now).  Later I will embed some extra-secure software to protect the communication channels :-) ...

[MartijnBraam]

If you want to mess with the modem over dbus then you can install ofonoctl through pip3

[dukla2000]

Maybe in Pine64 somebody must track where are things going with all known distributions, and to keep some updated page for easy browsing.  Some type of "index" or "quick access" page ... for not to travel through a lot of independent forum threads that offer many different options (they are for discussion and in the discussions are real and fake things mixed).

AFAIK Pine64 do not have any software staff - that is the responsibility of the community. There is a skeleton wiki page here in anticipation of folks updating it as they receive their phones - please add your experiences.

[malvcr]

Maybe in Pine64 somebody must track where are things going with all known distributions, and to keep some updated page for easy browsing.  Some type of "index" or "quick access" page ... for not to travel through a lot of independent forum threads that offer many different options (they are for discussion and in the discussions are real and fake things mixed).

AFAIK Pine64 do not have any software staff - that is the responsibility of the community. There is a skeleton wiki page here in anticipation of folks updating it as they receive their phones - please add your experiences.

OK ... I am taking your word.

First correction: the password for the demo user in postmarketOS is not "demo" but "147147".   First I will order my notes and then to modify such page for not to create a nightmare to the other readers.

[malvcr]

I really have been trying to make the ofono part to work, with ofonoctl and other dbus based tools, but the phone seems to ignore a SIM card I am using on it ... it simple says me that there is no SIM card installed.

It is an old SIM I found around that never was used (I suppose the available is gone by now), but as a physical device it is in pristine conditions. At least the phone must find that there is a SIM card there, but no way. And the same card works well in an Alcatel phone with FirefoxOS.

As a reference, I first poweron the Quactel with "ofonoctl poweron" ... and the SIM manager appear ... but no SIM ... and later "ofonoctl online" as trying to do something else, but no SIM available.

Could be a phone physical problem? Does somebody else have been trying to make the telephony part to work having more success than me?

[malvcr]

I was worried about the SIM, so I had a new one from a different telephone company ... and it works.  ( I still don't know why the previous one failed ... maybe the ofono layer is not managing well the corresponding error code).

With the ofonoctl I can send messages, although I have no idea where to receive them.

And the phone application in postmarketOS can make and receive calls, but with no audio involved (something is not yet connected).



There is something important with the phone.  It eats the battery very quickly and becomes really hot while recharging (I need to keep it connected when performing tests).  I suppose there is something running on the Linux that is not a good idea to keep working in a phone, or some working parameters are wrong.


At least there is a path to continue :-) ...

[malvcr]

Just in case ... something is missing in the kernel configuration for testing kernel:

pine64-pinephone:/sys/devices/virtual/thermal/thermal_zone1$ cat temp
cat: read error: Invalid argument

[malvcr]

A question.

There is a fix for the USB-C port ... this is the "stupid" version (https://www.youtube.com/watch?v=j3jc7Mvn9Eo&t=1742s) ... however, I don't know if the Developer Edition has the same problem.

My phone has these parts, and the board is clean and sound ... just USB-C never worked as expected.

Could somebody corroborate if that fix can be done with this phone version?



Thank you