| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,927
» Latest member: 1services
» Forum threads: 16,330
» Forum posts: 117,424
Full Statistics
|
| Latest Threads |
A/V output enable
Forum: Linux on Rock64
Last Post: 8lall0
6 hours ago
» Replies: 0
» Views: 13
|
If your USB-C port is fla...
Forum: PinePhone Pro Hardware
Last Post: Zebulon Walton
8 hours ago
» Replies: 0
» Views: 28
|
Pinebook problem
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-18-2026, 08:58 AM
» Replies: 2
» Views: 4,618
|
Pine a64+ power supply
Forum: General Discussion on PINE A64(+)
Last Post: davidspencer
03-18-2026, 01:02 AM
» Replies: 0
» Views: 137
|
Private / self-hosted "Cl...
Forum: General Discussion on PinePhone
Last Post: cyberb123
03-17-2026, 11:57 AM
» Replies: 8
» Views: 7,166
|
Automatic screen rotation
Forum: PineTab Software
Last Post: Raik
03-17-2026, 01:49 AM
» Replies: 32
» Views: 29,842
|
Prohibit Pinecil from goi...
Forum: Pinecil Software
Last Post: snorkel
03-13-2026, 01:56 AM
» Replies: 2
» Views: 217
|
dead Pinebook - help plea...
Forum: General Discussion on Pinebook Pro
Last Post: RicTor
03-12-2026, 04:49 AM
» Replies: 2
» Views: 613
|
Looking for PineTime user...
Forum: General
Last Post: Mitrax
03-11-2026, 02:50 PM
» Replies: 2
» Views: 395
|
reset wifi hardware/drive...
Forum: Mobian on PinePhone
Last Post: baptx
03-10-2026, 04:43 PM
» Replies: 5
» Views: 5,073
|
|
|
| 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 ...
... et l'affichage s'arrête là.
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 ...
... and the signage stops there.
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'
then the setting is kept when the phone wakes from sleep.
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.
|
|
|
|
Tutorial: (Internal SDR) Adding External Threaded Antenna Port |
|
Posted by: RTP - 02-16-2021, 06:21 PM - Forum: PineTab Hardware
- Replies (2)
|
 |
Howto: Create Threaded Antenna Port For Internal SDR (Pinetab)
My video with tips/instructions for safely opening your Pinetab + This Tutorial: https://odysee.com/@RTP:9/howto-open-pinetab-cover-safely-adding:4
This can be done for any device with internal SDR. In this case, the Pinetab. Pinebooks and any other device can add this in same fashion. Just be careful where you choose to drill your holes (so finished product does not to put too much pressure against fragile piece internally, and so antennas/cords do not get in the way of leaning your device). Here we installed it to fit small antennas inside the keyboard case itself (when leaning upright). Also measuring antenna wire is important so as not to stretch/damage it internally. Leave a slight extra bit of slack.
Adds a way to change out different antennas without having to opening your Pinetab (greatly enhances the usability/options for SDR).
The Pinetab optionally carries internal SDR (Software Defined Radio). You can also be added later. This is what I have. I love using the Pinetab for SDR controls after this small mod. Works as well as my external and makes for a very thin/compact total SDR kit (might try adding transmitter later) 
Backstory:
Tried a few internal options but signal was very weak with internal (tried a couple, didn't expect much). I wasn't able to use it for what I needed (multiple antenna types). Still might explore more there but like this options.
Decided it was time to try a modification using parts I had laying around. I not only wanted to be able to change out factory antenna, I wanted an easy way to do this without opening the Pinetab case each time, via a threaded exit port end coming out of the case (for screwing on different types of antennas/cables).
I checked my tools/parts inventory. I noted an antenna I had laying around with a pigtail clip for a LoRa mcu. A matching pigtail was fastening the factory included antenna. The LoRa antenna end itself was unscrewable (see it laying at top right), allowing easy changing out of different antennas. This would be it.
![[Image: 2c8990e073884f3d8831912bbdf18e59.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/2c8990e073884f3d8831912bbdf18e59.jpg)
In the picture below we see the sdr on the small black board, attached by blue/white ribbon cable:
![[Image: 5c2816830e5a37d789615f6ef40b81dd.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/5c2816830e5a37d789615f6ef40b81dd.jpg)
Getting Started:
Open your Pinetab case (see link to my video on doing this safely at top of this tutorial) also here: https://odysee.com/@RTP:9/howto-open-pin...y-adding:4
Measure the length of antenna wire to create an idea where to place the hole. Use a marker to plan it.
Carefully drill the hole in back cover (be safe- take off the cover first).
Unclip the factory antenna wire (see above picture: originally antenna still inside the case, lightly tucked under a ribbon cable; new antenna wire shown attached.
I grabbed plyers to bend the thin (maybe 1/2 inch long) small/straight metal piece on the opposite side of the threaded end to make it fit inside the case as neatly as possible (with case completely closed) without too much trouble. I didn't want to risk damaging screen from the inside.
Get a 90 degree bend antenna wire -> SMA (shown in video at top- this was changed as seen in video for better results/less stress to wire).
Grind off a few mm with a dremel or other grinding tool, being careful to ensure it will fit with case closed.
I then used electrical tape to add an extra layer of padding to the hard metal tube opposite the threaded end (the side inside the case).
Would the other end fit inside when I attempt to close the case?
I then set the threaded end straight up, pulling this threaded end through the top of the Pinetab cover, exiting out the back/outside the Pinetab (see picture above/below).
I fastened the small thin bolt + washers over the threaded piece to hold it snug without wear & tear.
As the picture shows, the threaded end exits the back of the tablet allowing you to change/screw on all different types of antennas.
Some antennas for LoRa. Other antenna setups perfect for receiving live satellite images of the earth.
See below:
![[Image: e9ab931a6d26492d1909e015da0c2f7d.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/e9ab931a6d26492d1909e015da0c2f7d.jpg)
Take the newly modified back cover and place over the Pinetab. Then carefully snap each edge shut, leaving the side closest to the threaded end for last (to be sure it fits without adding pressure).
I was sure not to put too much pressure on that side, as I didn't want to chance breaking either my screen. This is a big reason I wrapped the harder metal parts (opposite the threading, inside the case) in electrical tape- to cushion any possible pressure put on inside of my screen.
Another antenna shown as an example (LoRa fits inside the keyboard stand discreetly while in use):
![[Image: cace1cd0ee4627f8b812f0944405668b.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/cace1cd0ee4627f8b812f0944405668b.jpg)
One nice thing is small antennas like LoRa, along with antenna cord hooked to larger ones, fit nicely inside the keyboard case without any pressure:
![[Image: a6aa9e5fd857a16053828bbbb2447ae0.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/a6aa9e5fd857a16053828bbbb2447ae0.jpg)
I ran a couple tests to be sure the bending with plyers didn't harm anything. Before doing the mod, I took pictures of the signal strengths/waterfall, attempted to pick up various bands for comparison. This way I could see if there were issues with the bend made in antenna wire metal piece (opposite the threading directly inside the case). The modification made a huge difference- being able to use external antennas increased clarity and distance by probably 40+ x. Worth it.
One of my before/after mod tests was simple FM radio. Only read a weak signal with internal/built in antennas.
![[Image: 73e510c23af2b16490d8db45eb46c53f.jpg]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/73e510c23af2b16490d8db45eb46c53f.jpg)
My other main test was another stable radio goto: keyless entry car keys. I used this and took photos before, and after the modification. See for yourself:
![[Image: d3a0f92011af76c5beaadc9fd4720a27.png]](https://cdn.buymeacoffee.com/uploads/project_updates/2021/02/d3a0f92011af76c5beaadc9fd4720a27.png)
Everything is working beautifully. Each antenna showing their unique strengths (as they should).
This was fun.
Hope someone finds useful. Really makes for a totally awesome/ideal small SDR kit you can carry (with small antennas discreetly inside keyboard stand).
Cheers!
See this video (as linked above) that corrects a part in the pictures: https://odysee.com/@RTP:9/howto-open-pinetab-cover-safely-adding:4
|
|
|
|
| Plasma mobile email client |
|
Posted by: Athansor - 02-16-2021, 05:00 PM - Forum: Manjaro on PinePhone
- Replies (9)
|
 |
So I recently wandered over to Manjaro Plasma Mobile from Mobian Phosh, and Plasma seems to be working quite well. All the basics are there -- except, unless I'm missing something -- an email client.
Mobian has Geary; is there anything that someone can recommend for my Plasma pleasure?
Thanks in advance!
|
|
|
|
| Adding GPS |
|
Posted by: kessel - 02-16-2021, 12:11 PM - Forum: PineTime Hardware and Accessories
- Replies (5)
|
 |
Please add GPS to the PineTime!
For millions of runners, bikers and other athletes, there's no privacy respecting (open source) GPS-enabled fitness watch to handle the fitness data (e.g. gps tracks). PineTime could be the first.
To my knowledge, every major GPS-enabled fitness watch manufacturer (Garmin, Suunto, Polar etc.) requires a propriatary mobile app for data transfer (over bluetooth). They are also forcing users into their closed and hackable cloud services to store the sensitive fitness/location data. I store my fitness data locally. This is why I still use old USB devices, but these get harder and harder to use due to abandoned usb drivers. I'm also on Linux which is unsupported (Currently I'm using a Windows 7 virtual machine to transfer my data, not exaclty a practical or future proof solution).
Since runners don't want to carry a heavy smartphone, adding a GPS to the PineTime would bring a privacy respecting alternative.
I've read the hardware is unlikely to change, but I just wanted to mention the importance of this.
|
|
|
|
|