debian+phosh running on PinePhone

[wibble]

I recently saw that battery life on Ubuntu touch has been increased a lot with the addition of CRUST. Is there any plans to incorporate it in the Debian image ?

As previously mentioned, work in this direction will be part of the next release. Please note, however, that it has its drawbacks, such as incoming calls not waking up the phone atm (even in UT, no OS has it figured out yet), so it's really experimental and not fit for using the phone as a daily driver.

I thought not waking from suspend on call or text was down to hardware:
https://wiki.pine64.org/index.php/PinePh..._connected
https://wiki.pine64.org/index.php/PinePh...nts_wakeup
I can imagine how CRUST might be able to change which pins can receive interrupts in suspend, but a pin that's not connected is another matter entirely. Have I misunderstood the nature of the problem, or does 'figured it out' mean 'found an undocumented behaviour we can use as a workaround'?

[a-wai]

I thought not waking from suspend on call or text was down to hardware:
https://wiki.pine64.org/index.php/PinePh..._connected
https://wiki.pine64.org/index.php/PinePh...nts_wakeup
I can imagine how CRUST might be able to change which pins can receive interrupts in suspend, but a pin that's not connected  is another matter entirely. Have I misunderstood the nature of the problem, or does 'figured it out' mean 'found an undocumented behaviour we can use as a workaround'?

That surely complicates things, but testing s2idle shows that we can do without AP_READY, although more work is needed to make wakeup from RI reliable.
It should also be possible to hack the crust firmware and linux kernel to keep GPIO port B powered on and able to process interrupts during suspend, which would allow wakeup from modem. Admittedly we're still a long way from there, and I may be wrong about that, but I really believe it should be possible.

[wibble]

I thought not waking from suspend on call or text was down to hardware:
https://wiki.pine64.org/index.php/PinePh..._connected
https://wiki.pine64.org/index.php/PinePh...nts_wakeup
I can imagine how CRUST might be able to change which pins can receive interrupts in suspend, but a pin that's not connected  is another matter entirely. Have I misunderstood the nature of the problem, or does 'figured it out' mean 'found an undocumented behaviour we can use as a workaround'?

That surely complicates things, but testing s2idle shows that we can do without AP_READY, although more work is needed to make wakeup from RI reliable.
It should also be possible to hack the crust firmware and linux kernel to keep GPIO port B powered on and able to process interrupts during suspend, which would allow wakeup from modem. Admittedly we're still a long way from there, and I may be wrong about that, but I really believe it should be possible.

Thanks for the details - that's a little more positive than I was expecting. I won't be complaining if it doesn't happen though - something like this was one of the anticipated risks buying the initial hardware release.

[a-wai]

New week, new release !

The major features this week are, as previously mentioned, the move to a 5.6 kernel and integration of the crust power management firmware.
Other topics include a few software upgrades, but I mostly worked towards getting phosh-related packages accepted into Debian (which is progressing well so far), so nothing really important to mention here.

Unless you're an experienced developer, I strongly suggest you start with a fresh image instead of upgrading using apt this time. For those wanting to use apt anyway, the following steps are fairly simple, but keep in mind bad things will happen if something goes wrong:

Code:

# First, upgrade the whole system
sudo apt update
sudo apt upgrade
# Install the new bootloader (and crust firmware)
sudo u-boot-install-sunxi64 /dev/mmcblkX # X being 0 for the SD card, 2 for the eMMC
# Install the new kernel and remove the old one
sudo apt install linux-image-5.6-pinephone
sudo apt remove linux-image-5.5-pinephone

Now, regarding power management:

• auto-suspend is disabled by default: this is still experimental, and shouldn't be enabled if you use your phone as a daily driver
  
• s2idle auto-suspend can be enabled through Settings -> Power; the modem will wake up the phone on an incoming phone call or SMS, but answering the call can fail and leave the modem in a "reboot-required" state
  
• crust suspend (aka "deep sleep") can only be triggered through sysfs for now, and it might require a reboot to recover network connectivity after resuming
  

Given the experimental status, please don't report issues regarding this feature (unless you can provide really helpful logs, in which case please file an issue on gitlab)

[dukla2000]

New week, new release !

  More strength to your bow, Sir!

...
s2idle auto-suspend can be enabled through Settings -> Power;
...

As far as I car see this must be by enabling "Automatic Suspend", is that correct?

[jfloren]

Apologies if this has been asked elsewhere in the thread, but on a freshly-flashed image is there a way to enable SSH without using the serial console? I've got a serial cable but it's a little bit of a hassle if I'm re-flashing often.

[pjsf]

Apologies if this has been asked elsewhere in the thread, but on a freshly-flashed image is there a way to enable SSH without using the serial console? I've got a serial cable but it's a little bit of a hassle if I'm re-flashing often.

maybe:
sudo apt install openssh-server

[l_gyuri]

Apologies if this has been asked elsewhere in the thread, but on a freshly-flashed image is there a way to enable SSH without using the serial console? I've got a serial cable but it's a little bit of a hassle if I'm re-flashing often.

You can get a console using the terminal application on the phone.

[a-wai]

As far as I car see this must be by enabling "Automatic Suspend", is that correct?

Yep

[Zweitaktmotor]

A few observations about the image posted yesterday (20 April):

1.
Someting I have noticed in other distros as well is that the time setting for my time zone is initially 1 hour behind, irrespective of whether we are in summer time or not (I noticed this back in March before we turned the clocks). For instance, it is now 9.44am in the UK, but on first boot my Pinephone shows 8.44am. To correct this, I need to select another time zone and then go back to London, UK. This will load the time correctly. - Not a high priority, but perhaps it should be put on a "bug list" to be dealt with later.

2.
Under "Language & Region", I can select a UK keyboard layout, but the only entries in "Language" and "Formats" refer to the United States, they cannot be changed. I don't mind a different spelling occasionally, but would prefer the UK date format.

3.
The Geary e-mail client does not let me set up my account correctly. This may be because I own my domain name which is hosted on a provider's server with a different name. Example (not my real e-mail): myself@myname.co.uk can be found at mail.provider.net. But Geary rejects this server.

4.
As an alternative, I tried to install Claws Mail, but when I try to set it up, I am running into a strange keyboard glitch: The keys are mapped differently. Pressing Backspace produces "=" signs, for instance. Switching between "English UK" and "Terminal" keyboard layouts does not make a difference.


Apart from that, I am pleased that many apps now use the screen dimensions correctly, although I am not a big fan of Phosh itself because the running apps display takes up half the screen which IMO is not necessary. But this is is not your fault. It's the same in each Phosh distro.


Manyy thanks for the good work!