+- PINE64 (https://forum.pine64.org)
+-- Forum: PinePhone (https://forum.pine64.org/forumdisplay.php?fid=120)
+--- Forum: PinePhone Software (https://forum.pine64.org/forumdisplay.php?fid=121)
+---- Forum: Mobian on PinePhone (https://forum.pine64.org/forumdisplay.php?fid=139)
+---- Thread: debian+phosh running on PinePhone (/showthread.php?tid=9016)
RE: debian+phosh running on PinePhone - rico - 05-09-2020
On my own build this morning :
Using shutdown button on top bar.
It asked me for a password because an application was running.
Are you sure you really shut it down ?
RE: shutdown - dukla2000 - 05-09-2020
(05-09-2020, 01:51 AM)Juergen Wrote: Another problem occurred the second time to me: I shut down the phone yesterday 23.00, today the battery is totally discharged. (0%)
Can anyone confirm?
Yes, the modem doesn't power off correctly so unless you remove the battery you still have 1 ARM core (A53?) running.
RE: debian+phosh running on PinePhone - heng - 05-09-2020
Also does USB tethering work so that my Debian computer can use the internet connection(4g/lte) of the Pinephone?
RE: debian+phosh running on PinePhone - l_gyuri - 05-09-2020
(05-09-2020, 05:23 AM)heng Wrote: Also does USB tethering work so that my Debian computer can use the internet connection(4g/lte) of the Pinephone?
Yes, you should read about rico's post #470.
RE: debian+phosh running on PinePhone - rico - 05-09-2020
Or in the the tips wiki page :
https://gitlab.com/mobian1/wiki/-/wikis/Tweaks
Tell us if something goes wrong.
RE: debian+phosh running on PinePhone - heng - 05-09-2020
(05-09-2020, 11:39 AM)rico Wrote: Or in the the tips wiki page :
https://gitlab.com/mobian1/wiki/-/wikis/Tweaks
Tell us if something goes wrong.
Thanks!
RE: debian+phosh running on PinePhone - a-wai - 05-14-2020
Finally, a new release is there with a pretty big announcement! Head over there for more details
RE: shutdown - Juergen - 05-19-2020
(05-09-2020, 03:18 AM)dukla2000 Wrote:(05-09-2020, 01:51 AM)Juergen Wrote: Another problem occurred the second time to me: I shut down the phone yesterday 23.00, today the battery is totally discharged. (0%)
Can anyone confirm?
Yes, the modem doesn't power off correctly so unless you remove the battery you still have 1 ARM core (A53?) running.
I remembered that my old notebook "Siemens Amilo Pi2530" had the same problem within the first 6 months, the battery discharged within a week. After a bios-update, the problem was solved. Perhaps our problem could be found within the bootloader.
RE: Pass code / login screen - dukla2000 - 05-31-2020
(05-04-2020, 10:59 PM)Juergen Wrote: After pressing the power button the login screen appears to type in the passcode.
Sometimes this does not work. (one time within two days)
a) The login screen does not appear, only the backlight switches on.
or b) After typing in the passcode the login screen appears again and again ...
Can anyone confirm this problem?
Yup after deep sleep phosh is not waking up. I could ssh and get the journal below, starting with the suspend at 11:50 and ending at my successful ssh login. Note all kinds of fails around 12:13:58 and 12:13:59 related to user 1000 :
Code:
May 31 11:50:56 DuklaPP systemd[1]: Starting Suspend...
May 31 11:50:56 DuklaPP systemd-sleep[2721]: Suspending system...
May 31 11:50:56 DuklaPP kernel: PM: suspend entry (s2idle)
May 31 11:50:56 DuklaPP kernel: Filesystems sync: 0.148 seconds
May 31 12:13:58 DuklaPP kernel: OOM killer disabled.
May 31 12:13:58 DuklaPP kernel: Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
May 31 12:13:58 DuklaPP kernel: sunxi-rsb 1f03400.rsb: RSB running at 3000000 Hz
May 31 12:13:58 DuklaPP kernel: OOM killer enabled.
May 31 12:13:58 DuklaPP kernel: Restarting tasks ... done.
May 31 12:13:58 DuklaPP systemd[1]: systemd-journald.service: Main process exited, code=killed, status=6/ABRT
May 31 12:13:58 DuklaPP kernel: PM: suspend exit
May 31 12:13:58 DuklaPP systemd[1]: systemd-journald.service: Failed with result 'watchdog'.
May 31 12:13:58 DuklaPP systemd[1]: systemd-udevd.service: Main process exited, code=killed, status=6/ABRT
May 31 12:13:58 DuklaPP systemd[1]: systemd-udevd.service: Killing process 2725 (systemd-udevd) with signal SIGKILL.
May 31 12:13:58 DuklaPP systemd[1]: systemd-udevd.service: Failed with result 'watchdog'.
May 31 12:13:58 DuklaPP systemd[1]: systemd-timesyncd.service: Main process exited, code=killed, status=6/ABRT
May 31 12:13:58 DuklaPP systemd[1]: systemd-timesyncd.service: Failed with result 'watchdog'.
May 31 12:13:58 DuklaPP systemd[1]: systemd-logind.service: Main process exited, code=killed, status=6/ABRT
May 31 12:13:58 DuklaPP systemd[1]: systemd-logind.service: Failed with result 'watchdog'.
May 31 12:13:58 DuklaPP systemd[1]: systemd-suspend.service: Succeeded.
May 31 12:13:58 DuklaPP systemd[1]: Finished Suspend.
May 31 12:13:58 DuklaPP systemd[1]: systemd-journald.service: Scheduled restart job, restart counter is at 1.
May 31 12:13:58 DuklaPP systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1.
May 31 12:13:58 DuklaPP systemd[1]: systemd-timesyncd.service: Scheduled restart job, restart counter is at 1.
May 31 12:13:58 DuklaPP systemd[1]: systemd-logind.service: Scheduled restart job, restart counter is at 1.
May 31 12:13:58 DuklaPP systemd[1]: Stopped target Sleep.
May 31 12:13:58 DuklaPP systemd[1]: Reached target Suspend.
May 31 12:13:58 DuklaPP systemd[1]: Stopping Flush Journal to Persistent Storage...
May 31 12:13:58 DuklaPP systemd[1]: Stopped Login Service.
May 31 12:13:58 DuklaPP systemd[1]: Condition check resulted in Load Kernel Module drm being skipped.
May 31 12:13:58 DuklaPP systemd[1]: Starting Login Service...
May 31 12:13:58 DuklaPP systemd[1]: Stopped Network Time Synchronization.
May 31 12:13:58 DuklaPP systemd[1]: Starting Network Time Synchronization...
May 31 12:13:58 DuklaPP systemd[1]: Stopped udev Kernel Device Manager.
May 31 12:13:58 DuklaPP systemd[1]: Starting udev Kernel Device Manager...
May 31 12:13:58 DuklaPP systemd[1]: systemd-journal-flush.service: Succeeded.
May 31 12:13:58 DuklaPP systemd[1]: Stopped Flush Journal to Persistent Storage.
May 31 12:13:58 DuklaPP systemd[1]: Stopped target Suspend.
May 31 12:13:58 DuklaPP systemd[1]: Stopped Journal Service.
May 31 12:13:58 DuklaPP systemd[1]: Starting Journal Service...
May 31 12:13:58 DuklaPP systemd[1]: Started udev Kernel Device Manager.
May 31 12:13:58 DuklaPP systemd-journald[2770]: Journal started
May 31 12:13:58 DuklaPP systemd-journald[2770]: System Journal (/var/log/journal/c10263f9e3794ddbb4599843d5699302) is 1.3G, max 1.4G, 97.4M free.
May 31 12:13:57 DuklaPP systemd[1]: systemd-timesyncd.service: Watchdog timeout (limit 3min)!
May 31 12:13:57 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-DISCONNECTED bssid=f8:d1:11:24:17:dc reason=0 locally_generated=1
May 31 12:13:57 DuklaPP systemd[1]: systemd-timesyncd.service: Killing process 1455 (systemd-timesyn) with signal SIGABRT.
May 31 12:13:57 DuklaPP wpa_supplicant[1525]: dbus: wpa_dbus_property_changed: no property SessionLength in object /fi/w1/wpa_supplicant1/Interfaces/0
May 31 12:13:57 DuklaPP systemd[1]: systemd-udevd.service: Watchdog timeout (limit 3min)!
May 31 12:13:57 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=CORE type=WORLD
May 31 12:13:57 DuklaPP systemd[1]: systemd-udevd.service: Killing process 1426 (systemd-udevd) with signal SIGABRT.
May 31 12:13:57 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=USER type=COUNTRY alpha2=GB
May 31 12:13:57 DuklaPP systemd[1]: systemd-logind.service: Watchdog timeout (limit 3min)!
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0xd aborted, but message is not abortable
May 31 12:13:57 DuklaPP systemd[1]: systemd-logind.service: Killing process 1516 (systemd-logind) with signal SIGABRT.
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0xe aborted, but message is not abortable
May 31 12:13:57 DuklaPP systemd[1]: systemd-journald.service: Watchdog timeout (limit 3min)!
May 31 12:13:58 DuklaPP systemd[1]: Started Journal Service.
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0xf aborted, but message is not abortable
May 31 12:13:57 DuklaPP systemd[1]: systemd-journald.service: Killing process 1412 (systemd-journal) with signal SIGABRT.
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0x10 aborted, but message is not abortable
May 31 12:13:57 DuklaPP phoc[1573]: [backend/session/logind.c:119] Failed to release device '31': Connection timed out
May 31 12:13:58 DuklaPP systemd-journald[2770]: System Journal (/var/log/journal/c10263f9e3794ddbb4599843d5699302) is 1.3G, max 1.4G, 89.4M free.
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0x11 aborted, but message is not abortable
May 31 12:13:57 DuklaPP systemd-sleep[2721]: System resumed.
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0x12 aborted, but message is not abortable
May 31 12:13:57 DuklaPP NetworkManager[1507]: <info> [1590923637.4982] device (wlan0): supplicant interface state: completed -> disconnected
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0x13 aborted, but message is not abortable
May 31 12:13:57 DuklaPP NetworkManager[1507]: <info> [1590923637.5616] device (wlan0): supplicant interface state: disconnected -> scanning
May 31 12:13:57 DuklaPP ModemManager[1556]: transaction 0x14 aborted, but message is not abortable
May 31 12:13:58 DuklaPP systemd-logind[2767]: New seat seat0.
May 31 12:13:57 DuklaPP dbus-daemon[1506]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus-org.freedesktop.login1.service' requested by ':1.20' (uid=1000 pid=1573 comm="/usr/bin/phoc -C >
May 31 12:13:58 DuklaPP systemd-logind[2767]: Failed to add user by file name 1000, ignoring: Invalid argument
May 31 12:13:58 DuklaPP dbus-daemon[1506]: [system] Successfully activated service 'org.freedesktop.login1'
May 31 12:13:58 DuklaPP systemd-logind[2767]: User enumeration failed: Invalid argument
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: Trying to associate with f8:d1:11:24:17:dc (SSID='Eighteen' freq=2462 MHz)
May 31 12:13:58 DuklaPP systemd-logind[2767]: User of session 1 not known.
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: Associated with f8:d1:11:24:17:dc
May 31 12:13:58 DuklaPP systemd-logind[2767]: Got fd for missing session device [226:1] in session 1
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
May 31 12:13:58 DuklaPP systemd-logind[2767]: Session enumeration failed: No such file or directory
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: WPA: Key negotiation completed with f8:d1:11:24:17:dc [PTK=CCMP GTK=CCMP]
May 31 12:13:58 DuklaPP systemd-logind[2767]: Watching system buttons on /dev/input/event0 (axp20x-pek)
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-CONNECTED - Connection to f8:d1:11:24:17:dc completed [id=0 id_str=]
May 31 12:13:58 DuklaPP systemd[1]: Starting Flush Journal to Persistent Storage...
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: bgscan simple: Failed to enable signal strength monitoring
May 31 12:13:58 DuklaPP phoc[1573]: [backend/session/logind.c:119] Failed to release device '32': Unknown object '/org/freedesktop/login1/session/_31'.
May 31 12:13:59 DuklaPP wpa_supplicant[1525]: wlan0: CTRL-EVENT-REGDOM-CHANGE init=COUNTRY_IE type=COUNTRY alpha2=GB
May 31 12:13:58 DuklaPP systemd[1]: Started Login Service.
May 31 12:13:58 DuklaPP systemd[1]: Started Network Time Synchronization.
May 31 12:13:58 DuklaPP phoc[1573]: [backend/session/logind.c:119] Failed to release device '33': Unknown object '/org/freedesktop/login1/session/_31'.
May 31 12:13:58 DuklaPP phoc[1573]: [backend/session/logind.c:119] Failed to release device '34': Unknown object '/org/freedesktop/login1/session/_31'.
May 31 12:13:58 DuklaPP phoc[1573]: [backend/session/logind.c:119] Failed to release device '35': Unknown object '/org/freedesktop/login1/session/_31'.
May 31 12:13:59 DuklaPP NetworkManager[1507]: <info> [1590923639.0665] device (wlan0): supplicant interface state: scanning -> associating
May 31 12:13:59 DuklaPP NetworkManager[1507]: <info> [1590923639.1131] device (wlan0): supplicant interface state: associating -> associated
May 31 12:13:59 DuklaPP NetworkManager[1507]: <info> [1590923639.1201] device (wlan0): supplicant interface state: associated -> 4way_handshake
May 31 12:13:59 DuklaPP NetworkManager[1507]: <info> [1590923639.1339] device (wlan0): supplicant interface state: 4way_handshake -> completed
May 31 12:13:59 DuklaPP systemd-timesyncd[2768]: Initial synchronization to time server 185.121.25.166:123 (0.debian.pool.ntp.org).
May 31 12:13:59 DuklaPP systemd[1]: Finished Flush Journal to Persistent Storage.
May 31 12:14:05 DuklaPP systemd-logind[2767]: Power key pressed.
May 31 12:14:48 DuklaPP systemd-logind[2767]: Power key pressed.
May 31 12:16:14 DuklaPP sshd[2785]: Accepted password for chris from 192.168.1.154 port 56974 ssh2
May 31 12:16:14 DuklaPP sshd[2785]: pam_unix(sshd:session): session opened for user chris by (uid=0)And a
Code:
sudo systemctl restart phoshI am rapidly starting to hate phosh
RE: debian+phosh running on PinePhone - cefre00 - 06-05-2020
Hi All!
I see that the app grid changed quite a bit and the Settings menu too. But interestingly some of the applications are not present in the app grid, though I can start them from Software app, like Contacts. Is it time to re-flash?
Maybe I am just missing something, but still this is the thread to read new release info?