Arch Linux ARM on PinePhone

[dukla2000]

Arch Linux ARM (20201129):

...

Seems pretty snappy and stable to me, thank you . Gonna try it as daily driver for a bit.

Settings/sound seems to have some phosh hangover bits: after each boot I need to play with speakers/earpiece and default/phone for a while until I can get the tests to work on speakers propetly. (At which stage phone call sound more likely to work as well.)

[Lousy Fisherman]

pacman -Syu 2020/12/02 based on 2020-11-12 image.
Phone no longer charges when turned on. It was left overnight, it never went to sleep despite the setting of "sleep after 5 minutes no matter what" and in the morning the charge was only 15%. Reverting to my production image (2020-11-29) allows the phone to charge as before.

HTH
LF

[Danct12]

pacman -Syu 2020/12/02 based on 2020-11-12 image.
Phone no longer charges when turned on. It was left overnight, it never went to sleep despite the setting of "sleep after 5 minutes no matter what" and in the morning the charge was only 15%. Reverting to my production image (2020-11-29) allows the phone to charge as before.

HTH
LF

Hi, can you please let me know how you charge your phone (C-C or A-C?) for A-C I can still charge the phone just fine.

Please keep in mind that if the device is on load while being charged it might not charge fast or can discharge.

---

Arch Linux ARM (20201203):

• Kernel 5.9.11
  
• Now uses F2FS as the default filesystem
  

[Lousy Fisherman]

pacman -Syu 2020/12/02 based on 2020-11-12 image.
Phone no longer charges when turned on. It was left overnight, it never went to sleep despite the setting of "sleep after 5 minutes no matter what" and in the morning the charge was only 15%. Reverting to my production image (2020-11-29) allows the phone to charge as before.

HTH
LF

Hi, can you please let me know how you charge your phone (C-C or A-C?) for A-C I can still charge the phone just fine.

Please keep in mind that if the device is on load while being charged it might not charge fast or can discharge.

---

Hello,
I use a standard wall plugin USB adaptor, 5V, 2A max. I noticed this because it had been left overnight, unused . When I logged in I did not check the processes to see if something unusual was running. I also have not repeated the test. Unfortunately, I am short of time for the rest of the week.

And I've been searching for a way to donate to your hardware fund. I have not been able to figure that out yet :0

Thanks
LF

[dukla2000]

...

---

Arch Linux ARM (20201203):

• Kernel 5.9.11
  
• Now uses F2FS as the default filesystem
  

- thank you

BTW - what is the memory speed in the pre-built images? (I presume that when I flash a new image it also flashes a new bootloader?) After pacman -Syu yesterday I saw the new bootloader comment and went for 492 which has seemed more stable, for me, than previously.

[dukla2000]

...

• Now uses F2FS as the default filesystem
  

I cant get this to install. After boot df shows the filesystem has been expanded (to 31G in my case on eMMC). But lsblk still shows the 3.xG partition. Nothing I can do either on phone itself or via Jumpdrive can recover so reverting to 20201129.

Seems at least f2fs-tools missing from the image - not sure that will help the resize?

[Danct12]

...

• Now uses F2FS as the default filesystem
  

I cant get this to install. After boot df shows the filesystem has been expanded (to 31G in my case on eMMC). But lsblk still shows the 3.xG partition. Nothing I can do either on phone itself or via Jumpdrive can recover so reverting to 20201129.

Seems at least f2fs-tools missing from the image - not sure that will help the resize?

I have released a new image in respond to the issue.

However, if you already have installed the old broken image you can boot to Jumpdrive (or insert the SD card to your computer) and manually "resize.f2fs /dev/mmcblk0p2" (root partition)

[dukla2000]

...
I have released a new image in respond to the issue.
...

Many thanks - downloaded and installed fine (the resize logging does give a 2 minute "commentary" on first boot but no big deal).

...
However, if you already have installed the old broken image you can boot to Jumpdrive (or insert the SD card to your computer) and manually "resize.f2fs /dev/mmcblk0p2" (root partition)

How embarrassing - I could work out I needed f2fs-tools but was too dumb to try anything beyond resize2fs

[Lousy Fisherman]

pacman -Syu 2020/12/05 based on 2020-11-12 image, new uboot image installed. 1 month full daily driver usage.


- incoming calls interrupt deep sleep 100% of the time, gnome-calls is too late 5% of the time

- I could not reproduce my charging problem of above, hallelulah

- automatic sleep and suspend is flaky whether on battery or USB power (5V, 2Am wall adaptor)

- Mobile data works well with manual control. Tested on 3G, 4G and LTE networks. Wake and suspend problems persist

- the phone handles USB changes much better. Connecting a fully loaded dock (USB power, HDMI, usb keyb and mouse) works properly 80-100% of the time, up from 30%

- roaming not tested

- wifi re-connection has become much more inconsistent, 50% of the time after deep sleep I have to kick the wifi connection to get it to work

- power consumption is quite good even with the sleep troubles noted earlier, 24 hours moderate use, 48 hours if just text and messaging



Thanks to all.

LF

[dukla2000]

...
[quote pid='85225' dateline='1607268924']

- wifi re-connection has become much more inconsistent, 50% of the time after deep sleep I have to kick the wifi connection to get it to work
...
[/quote]

I have always found with phosh that you need to wait on the clock/sleep screen, after pushing the power button to wake up, until the wifi and/or mobile data reconnects before swiping up and doing your PIN. Seems to me phosh stops trying to recover a data connection after you enter your PIN.

Recently (?5.9 kernel?) my wifi is sometimes taking 90 seconds or so to reconnect.