| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,473
» Latest member: Samliams
» Forum threads: 16,196
» Forum posts: 116,875
Full Statistics
|
|
|
Wake up from charging problem |
|
Posted by: j4n3z - 02-18-2021, 02:23 AM - Forum: Mobian on PinePhone
- Replies (11)
|
 |
Hello,
I am running latest Mobian on PinePhone Mobian edition.
In the evening (cca 22:00) I put phone with battery level at around 10-20% on 5V/2A charger. In the morning (cca 6:00) the phone is charged but not responding. Screen is black and device does not react to power button or display tap (the screen does not even light-up, just stays off).
To get the phone up and running I have to perform hard reset (PWR button press for 8s to turn off and then 2s to turn on again).
My guess is Mobian enters something like "deep sleep" mode, not sure if caused by system or Phosh.
I have auto sleep set only for battery and turned off for charger.
According to my observation this happens only when battery hits 100%. I tried to wake up phone during charging several times and last wake up was at about 96% battery charge and then few minutes later the phone did not wake up.
Do you have any idea what could cause the issue?
Can I prevent this? I did not try offline charging yet.
Thanks
|
|
|
|
Pinebook Pro dead after dd |
|
Posted by: crmcalls - 02-18-2021, 12:17 AM - Forum: General Discussion on Pinebook Pro
- Replies (2)
|
|
I booted my Pinebook Pro with a microSD card running Mankato and used it to download an image to flash to my EMMC, after doing so I shut it down and noticed the charging LED would turn off after about a 30 seconds I tried turning it on and was met with nothing, no power led on the top of the keyboard and no light from the barrel connector. I opened the back and hit the reset button but to no avail, I unplugged the battery, removed and disabled EMMC, tried using usb c to charge but still nothing. Any help would be greatly appreciated
Edit: Got it to boot from microSD however I’m greeted with “give root password for maintenance or press control D to skip, pressing control D reads cannot read /dev/tty1 and it hangs. Any advice?
|
|
|
|
| PinePhone Cross Compiler Install |
|
Posted by: dgdimick - 02-17-2021, 11:44 AM - Forum: General Discussion on PinePhone
- Replies (2)
|
|
I'm trying to install a GCC cross compiler so I can write so really bad code for when my PhinePhone gets here; a 5th grader is probably a better coder then I am.
Anyway, I'm using these instructions, and it work just fine untill I try to install glibc
https://preshing.com/20141119/how-to-bui...-compiler/
Code: make -j4 csu/subdir_lib
make[2]: *** [/home/dgdimick/PinePhone/CrossCompiler/build-glibc/sysd-rules:9: / home/dgdimick/PinePhone/CrossCompiler/build-glibc/csu/libc-start.o] Error 1
make[2]: *** Waiting for unfinished jobs....
check_fds.c: Assembler messages:
check_fds.c:81: Error: no such instruction: `brk '
make[2]: *** [../o-iterator.mk:9: /home/dgdimick/PinePhone/CrossCompiler/build-g libc/csu/check_fds.o] Error 1
In file included from ../include/errno.h:25,
from ../csu/libc-tls.c:20,
from ../sysdeps/aarch64/libc-tls.c:19:
../sysdeps/aarch64/libc-tls.c: In function ‘__tls_get_addr’:
../sysdeps/aarch64/nptl/tls.h:91:19: error: ‘__builtin_thread_pointer’ is not su pported on this target
91 | (((tcbhead_t *) __builtin_thread_pointer ())->dtv)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
../sysdeps/aarch64/libc-tls.c:30:16: note: in expansion of macro ‘THREAD_DTV’
30 | dtv_t *dtv = THREAD_DTV ();
| ^~~~~~~~~~
make[2]: *** [/home/dgdimick/PinePhone/CrossCompiler/build-glibc/sysd-rules:485: /home/dgdimick/PinePhone/CrossCompiler/build-glibc/csu/libc-tls.o] Error 1
make[2]: Leaving directory '/home/dgdimick/PinePhone/CrossCompiler/glibc-2.29/cs u'
make[1]: *** [Makefile:258: csu/subdir_lib] Error 2
make[1]: Leaving directory '/home/dgdimick/PinePhone/CrossCompiler/glibc-2.29'
make: *** [Makefile:9: csu/subdir_lib] Error 2
dgdimick@Samba:~/PinePhone/CrossCompiler/build-glibc $
Any ideas? Or am I just doing this wrong, like there's already as package to install?
I'm running on an old laptop that has Ubuntu installed.
|
|
|
|
| weird sms issue specific to particular sender |
|
Posted by: moodroid - 02-17-2021, 10:39 AM - Forum: PinePhone Software
- Replies (3)
|
|
Hi,
This was with Mobian but could apply to ther OS's...
Didn't get an SMS from my work vpn. Did 'sudo mmcli -m 0 --messaging-list-sms' and there was a message stuck in the 'receiving' state. So, deleted with 'sudo mmcli -m 0 --messaging-delete-sms=1'. Still couldn't receive SMS's from my work vpn, although I could receive them from other senders. Had to put my SIM in another phone to get my work vpn SMS. So it seems as if something specific to that sender is 'locked'.
Any suggestions on what I could have/can do?
Thanks
|
|
|
|
| Videostreaming with VDR. |
|
Posted by: Gribouille - 02-17-2021, 03:38 AM - Forum: Mobian on PinePhone
- No Replies
|
|
Hello,
I know that is not the main usage of the Pinephone, but now I have only my Pinephone available to have access to my private network with the USB-C dock and the Ethernet connexion.
On a desktop computer, Debian Buster, I have a VDR service. The URL of my VDR service is 'http://<my computer>:3000'. On the Pinephone I get the URL of a TNT channel or a records, for this I use a webrowser like elinks, Fireforx, etc.
The video is jerky. There is a big delay between the video and the sound. If I plug a monitor on the USB-C dock, it's worth.
I have no troubles with the streaming with an other desktop computer, even if this is a Windows computer ... So, the VDR service is working as expected.
After, I must use a tool to see the video stream, 'mpv' and 'vlc' can do that. VLC consume more resources than 'mpv'. With 'mpv' I have a message that say :
Code: [vo/gpu/wayland] GNOME's wayland compositor is known to have many serious issues with mpv. Switch to GNOME's xorg session for the best experience.
I've try 'mpv' with many configurations like :
Code: $> mpv http://<my computer>:3000/65030:52559969.rec.ts
$> mpv http://<my computer>:3000/65030:52559969.rec.ts --cache-secs=8
$> mpv http://<my computer>:3000/65030:52559969.rec.ts --cache=yes --demuxer-readahead-secs=30 --demuxer-thread=yes --demuxer-rawvideo-w=640
'mpv' could be not the good application to use in this case. I have not found how to use a streaming URL with Totem.
How to have a fluent video and audio streaming on the Pinephone with Mobian ?
Best regards.
Gribouille.
|
|
|
|
| Carte PCIe bloquant le démarrage du Noyau / PCIe card blocking Kernel boot |
|
Posted by: dml-pc - 02-17-2021, 02:22 AM - Forum: RockPro64 Hardware and Accessories
- Replies (4)
|
 |
Bonjour ...
Je rencontre in problème avec un carte PCIe qui bloque mon RockPro64 dès le lancement du noyau.
Voici ce que la console m'affiche :
Code: U-Boot 2020.10-armbian (Feb 04 2021 - 02:11:12 +0100)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 RockPro64 v2.1
Net: eth0: ethernet@fe300000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 5 ms (622.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
213 bytes read in 4 ms (51.8 KiB/s)
13102297 bytes read in 558 ms (22.4 MiB/s)
28582400 bytes read in 1214 ms (22.5 MiB/s)
75846 bytes read in 13 ms (5.6 MiB/s)
267 bytes read in 8 ms (32.2 KiB/s)
Applying kernel provided DT overlay rockchip-pcie-gen2.dtbo
2698 bytes read in 9 ms (292 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 13102233 Bytes = 12.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f1291000, end f1f0fc99 ... OK
Loading Device Tree to 00000000f1216000, end 00000000f1290fff ... OK
Starting kernel ...
J'ai attendu plusieurs minutes mais rien de plus.
J'ai aussi testé un «ping» durant ce temps, au cas où ce ne soit qu'un problème de console :
Code: ...
From xxx.xxx.xxx.xxx icmp_seq=3493 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3494 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3495 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3496 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3500 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3503 Destination Host Unreachable
...
La carte qui bloque le noyau au démarrage est celle-ci :
Lorsque cette carte pcie n'est pas connectée, le noyau démarre sans aucun problème.
J'utilise maintenant le noyau ArmBian «5.10.16»,car avec le noyau «4.4.x», le problème était le même (voir pire).
Ayant aussi une carte «PCIE-EUX1-04 Ver.002» et ayant lu qu'elle était supportée par la carte RockPro64 :
... j'ai aussi testé cette carte mais cela ne fonctionne pas chez moi. Le résultat est le même.
Si quelqu'un aurait une piste ou une solution, je serai heureux qu'il me la transmette.
D'avance, Merci pour vos réponses.
Cordialement.
Hello ...
I run into a problem with a PCIe card that blocks my RockPro64 when the kernel is launched.
Here is what the console shows me :
Code: U-Boot 2020.10-armbian (Feb 04 2021 - 02:11:12 +0100)
SoC: Rockchip rk3399
Reset cause: POR
Model: Pine64 RockPro64 v2.1
DRAM: 3.9 GiB
PMIC: RK808
MMC: mmc@fe310000: 2, mmc@fe320000: 1, sdhci@fe330000: 0
Loading Environment from SPIFlash... SF: Detected gd25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
In: serial
Out: serial
Err: serial
Model: Pine64 RockPro64 v2.1
Net: eth0: ethernet@fe300000
Hit any key to stop autoboot: 0
switch to partitions #0, OK
mmc1 is current device
Scanning mmc 1:1...
Found U-Boot script /boot/boot.scr
3185 bytes read in 5 ms (622.1 KiB/s)
## Executing script at 00500000
Boot script loaded from mmc 1
213 bytes read in 4 ms (51.8 KiB/s)
13102297 bytes read in 558 ms (22.4 MiB/s)
28582400 bytes read in 1214 ms (22.5 MiB/s)
75846 bytes read in 13 ms (5.6 MiB/s)
267 bytes read in 8 ms (32.2 KiB/s)
Applying kernel provided DT overlay rockchip-pcie-gen2.dtbo
2698 bytes read in 9 ms (292 KiB/s)
Applying kernel provided DT fixup script (rockchip-fixup.scr)
## Executing script at 09000000
Moving Image from 0x2080000 to 0x2200000, end=3de0000
## Loading init Ramdisk from Legacy Image at 06000000 ...
Image Name: uInitrd
Image Type: AArch64 Linux RAMDisk Image (gzip compressed)
Data Size: 13102233 Bytes = 12.5 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 01f00000
Booting using the fdt blob at 0x1f00000
Loading Ramdisk to f1291000, end f1f0fc99 ... OK
Loading Device Tree to 00000000f1216000, end 00000000f1290fff ... OK
Starting kernel ...
I waited several minutes but nothing more.
I also tested a «ping» during this time, in case it is only a console problem :
Code: ...
From xxx.xxx.xxx.xxx icmp_seq=3493 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3494 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3495 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3496 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3500 Destination Host Unreachable
From xxx.xxx.xxx.xxx icmp_seq=3503 Destination Host Unreachable
...
The board that blocks the kernel at boot time is:
When this pcie card is not connected, the kernel starts without any problems.
I now use the ArmBian kernel «5.10.16», because with the kernel «4.4.x», the problem was the same (see worse).
Having also a card «PCIE-EUX1-04 Ver.002» and having read that it was supported by the RockPro64 card :
... i also tested this card but it does not work for me. The result is the same.
If someone has a lead or a solution, I would be happy to hear from them.
In advance, thank you for your answers.
Best Regards.
|
|
|
|
| eg25manager always turns on GPS when waking up from sleep |
|
Posted by: dcinoz - 02-16-2021, 11:49 PM - Forum: Mobian on PinePhone
- Replies (5)
|
|
Hi,
I've just realised eg25manager always turns GPS on using the command:
AT+QGPS=1
when resuming from sleep.
You can check via:
Code: mmcli -m any --command="AT+QGPS?"
1 is on, 0 off.
To turn off use the command:
Code: mmcli -m any --command="AT+QGPSEND"
I've spotted this bug report:
https://gitlab.com/mobian1/devices/eg25-...-/issues/2
I don't understand the "GPS management is now disabled by default with 79974bc9 and can be activated with the -g command line option.
Leaving this issue open as it's just a workaround, I'll have to come up with a better solution later on."
That would suggest GPS should be OFF, no?
I tried to use systemd system-sleep by adding a shell script to send the OFF command to the modem but eg25manager always runs after system-sleep. Adding sleep 5 or 10 or 20 seconds just delays eg25manager running so modem is not found and the OFF command fails. eg25manager would turn it on anyway.
Note that Privacy -> Location Services is switched OFF. I assumed that meant the GPS was OFF too....
It doesn't help battery life, has this just changed explaining the larger battery drain noticed recently? Or is that something else?
How can I prevent eg25manager from sending the GPS ON command (other than running a script manually every time I wake up the Pinephone)?
Command to see eg25manager log from systemd:
Code: sudo journalctl -b | grep eg25
Just did a few IMS tests.
Reboot phone, IMS is on, check via command:
Code: mmcli -m any --command='AT+QCFG="IMS"'
If you disable it via:
Code: mmcli -m any --command='AT+QCFG="IMS",0'
No idea why eg25manager would enable IMS by default. Guess phone still works with a non-IMS enable operator (no VoLTE).
Here is systemd log from boot showing the IMS on part:
Feb 17 16:34:56 mobian eg25manager[362]: Response: [+QCFG: "ims",0,0
Feb 17 16:34:56 mobian eg25manager[362]: Got a different result than expected, changing value...
Feb 17 16:34:56 mobian eg25manager[362]: (null)
Feb 17 16:34:56 mobian eg25manager[362]: Sending command: AT+QCFG="ims",1
Feb 17 16:34:56 mobian eg25manager[362]: Response: [OK]
Further look at eg25manager logs, at least the GPS is turned OFF when it suspends:
eg25manager[362]: system is about to suspend
eg25manager[362]: Sending command: AT+QGPSEND
eg25manager[362]: Response: [OK]
|
|
|
|
| Any trick to fix terrible audio? |
|
Posted by: daniel - 02-16-2021, 10:05 PM - Forum: Mobian on PinePhone
- Replies (2)
|
|
When I use the phone to call or answer another call the audio is terrible. By terrible I mean is low and broken making it difficult to understand anything. I could not find other posts complaining about this basic function, so I am not sure is not just my phone.
Do you get good audio? is there anything I can do? I do not think it is a hardware problem since other sources of audio have no problem.
I am using Ubuntu edition phone, with Mobian, I apt update/upgrade weekly.
|
|
|
|
|
