+- 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: Announcing the Mobian project (/showthread.php?tid=9850)
RE: Announcing the Mobian project - ryo - 01-05-2021
2 days ago I started to understanding the importance of the "Software" app.
I received 3 "system updates" in a row, and a reboot was needed each time.
Now I notice my phone became suddenly much smoother than what it was before these updates.
And I didn't notice any double tap problems since then too.
On top of that, it seems to be surviving a bit longer without a charger now, I had it off-charger all morning and on idle, and it's still on 85% battery.
Before that, it'd be dead by now.
However, it seems to suddenly restart the UI after pressing the power button once, and then it'll go into the endless login loop.
RE: Announcing the Mobian project - someGermanGuy - 01-09-2021
my phone's LED is blinking blue about every second. The screen does not turn off, i see the clock and some symbols (wifi, bluetooth etc.) - is it supposed how it is? how should the battery last 12h+ with that?
RE: Announcing the Mobian project - dcinoz - 01-12-2021
Latest kernel / software updates has huge problems - blue blinking light appears for no reason after a while, unable to unlock screen / frozen screen, forced to do hard reset (press on button).
Alternatively, after being turned on with modem on (not sure if this makes a difference but it is supposed to be a phone), after screen locks, several minutes later the unlock screen doesn't even appear, nothing can be done, forced to hard reset.
Linux mobian 5.10-sunxi64 #1 SMP PREEMPT Mon Jan 11 19:19:49 UTC 2021 aarch64 GNU/Linux
/etc/apt/sources/list:
deb http://deb.debian.org/debian bullseye main
sudo apt update only has 2 hits:
Hit:1 http://deb.debian.org/debian bullseye InRelease
Hit:2 http://repo.mobian-project.org mobian InRelease
Reading package lists... Done
Building dependency tree
Reading state information... Done
All packages are up to date.
Anyone else having this issue?! I would say do not update at this stage.
Following tests run:
On battery (5 min auto suspend):
mobile on only - automatic suspend: can't unlock / screen unresponsive when press on button(stays black / blank) - hard reset needed (can lock / unlock screen ok before suspend)
nothing on - automatic suspend: as above, screen stays black/blank, pressing on button or touching screen does nothing, forced to hard reset
wifi on only - automatic suspend: as above, as soon as screen goes blank, phone appears to be 'dead' (can't access through ssh as wifi suspends too)
mobile and wifi on - as above
I don't know how to try and debug.
I'll try while on power next.
RE: Announcing the Mobian project - dcinoz - 01-12-2021
On power (5 min auto suspend):
mobile on only - automatic suspend: screen goes black, press on and unlock screen appears but can't unlock as screen doesn't respond (pressing off button doesn't turn screen off) so hard reset needed (mobile indicator doesn't turn on)
nothing on - automatic suspend: screen goes black, same behaviour as on battery
wifi on only - automatic suspend: screen goes black, same behaviour as on battery, pressing on button does nothing, screen stays black, forced to hard reset, ssh connection lost
mobile and wifi on - automatic suspend: screen goes black, press on and unlock screen appears but can't unlock as screen doesn't respond (pressing off button doesn't turn screen off) so hard reset needed (neither wifi nor mobile indicators turn on either)
RE: Announcing the Mobian project - dcinoz - 01-12-2021
Apparently auto suspend is invoked by the following command:
systemctl suspend
This reproduces the behaviour when auto suspend timeout is reached.
I tried creating /usr/lib/pm-utils/pm-functions containing "export PM_DEBUG=true" (as per https://wiki.debian.org/Suspend) but that didn't work.
There is no /var/log/pm-suspend.log file.
Disabling auto suspend prevents the problem - phone has been on with mobile on for a few hours without a problem, though presumably battery drain is larger?
RE: Announcing the Mobian project - fdlamotte - 01-13-2021
I had the same issue yesterday in the morning. It has been solved by noon with a new kernel
current kernel is 5.10.6+sunxi64-2
RE: Announcing the Mobian project - dcinoz - 01-13-2021
(01-13-2021, 12:25 AM)fdlamotte Wrote: I had the same issue yesterday in the morning. It has been solved by noon with a new kernel
current kernel is 5.10.6+sunxi64-2
@fdlamotte
Ok, great. How come I'm still 'stuck' on 5.10-sunxi64?
I've done sudo apt update & sudo apt upgrade and am supposedly up-to-date ?!
Thanks for any help.
RE: Announcing the Mobian project - fdlamotte - 01-13-2021
(01-13-2021, 12:35 AM)dcinoz Wrote: Ok, great. How come I'm still 'stuck' on 5.10-sunxi64?
I've done sudo apt update & sudo apt upgrade and am supposedly up-to-date ?!
I have sid enabled, maybe the difference is here ?
RE: Announcing the Mobian project - fdlamotte - 01-13-2021
The package is here :
http://repo.mobian-project.org/pool/main/l/linux-5.10-sunxi64/
Maybe you can install it with dpkg
RE: Announcing the Mobian project - dcinoz - 01-13-2021
(01-13-2021, 01:41 AM)!fdlamotte Wrote:@fdlamotte(01-13-2021, 12:35 AM)dcinoz Wrote: Ok, great. How come I'm still 'stuck' on 5.10-sunxi64?
I've done sudo apt update & sudo apt upgrade and am supposedly up-to-date ?!
I have sid enabled, maybe the difference is here ?
This is what I have:
Code:
$ uname -r
5.10-sunxi64
$ apt list linux-image*-sunxi64
linux-image-5.10-sunxi64/unstable,now 5.10.6+sunxi64-1 arm64 [installed]
linux-image-5.9-sunxi64/unstable,now 5.9.13+sunxi64-1 arm64 [installed,automatic]I'm not sure why uname -r doesn't include the .6 but from apt list I understand I'm actually running 5.10.6, right?
And yet command: systemctl suspend
still does the same thing.
There were additional updates but that hasn't changed anything.
Presumably sid / testing has more up-to-date versions that have fixed the problem.
I look forward to the fixes for the stable branch!