| Welcome, Guest |
You have to register before you can post on our site.
|
| Forum Statistics |
» Members: 29,789
» Latest member: Andydor1
» Forum threads: 16,287
» Forum posts: 117,309
Full Statistics
|
| Latest Threads |
Problems With Extensions ...
Forum: PineNote Software
Last Post: Notebook823
1 hour ago
» Replies: 0
» Views: 5
|
Quill OS for the PineNote
Forum: PineNote Software
Last Post: tux-linux
7 hours ago
» Replies: 2
» Views: 447
|
60fps display updates pos...
Forum: General Discussion on PinePhone
Last Post: WhiteHexagon
Yesterday, 12:46 PM
» Replies: 2
» Views: 452
|
wifi password wont save
Forum: General Discussion on PineTab
Last Post: WEF
12-29-2025, 03:54 PM
» Replies: 0
» Views: 56
|
curious iPhone user here
Forum: General Discussion of PinePhone Pro
Last Post: Mary_Davis
12-29-2025, 03:57 AM
» Replies: 10
» Views: 8,507
|
Pinephone + Keyboard for ...
Forum: PinePhone Hardware
Last Post: PinePhoneProUser
12-28-2025, 02:13 PM
» Replies: 12
» Views: 6,376
|
Booting Issues
Forum: PineNote Software
Last Post: d2minik
12-26-2025, 12:44 PM
» Replies: 22
» Views: 16,285
|
Window Maker Live for Pin...
Forum: Linux on Pinebook Pro
Last Post: vajak
12-24-2025, 06:00 AM
» Replies: 2
» Views: 434
|
Rrkisp issue with CSI cam...
Forum: Linux on Quartz64
Last Post: lystar
12-24-2025, 02:34 AM
» Replies: 1
» Views: 3,848
|
bookworm vs trixie discus...
Forum: Mobian on PinePhone
Last Post: Kevin Kofler
12-24-2025, 12:11 AM
» Replies: 80
» Views: 45,848
|
|
|
| To live and die on LTE (with a Pinephone) |
|
Posted by: robthebold - 07-08-2022, 09:46 AM - Forum: General Discussion on PinePhone
- Replies (2)
|
 |
Well, that sounds dramatic, but here in the US 2g and 3g service is all but gone with T-Mo dropping the last (maybe . . . mostly . . .) of theirs last week and ATT's going offline last February. As far as the rest of the world, YMMV, but if GSM and 3g are set to be phased out where you communicate this might be interesting.
I've been spending a lot of time trying to figure out why (and when) my pinephone stops receiving calls. I found this thread which provides an interesting "watchdog" work-around for the pinephone modem falling into a coma and never waking up again. User @kebab (thanks, kebab!) describes using the modem manager to reset the modem and bring it back to life. Unfortunately, that never worked for me . . . but it can sometimes fix two other issues that will knock the pinephone offline on my all-LTE network.
kebab's service checks the results of mmcli -m any for the phrase "No modems were found" and calls for an eg25-manager restart (using the appropriate system service manager for your OS. This problem -- the modem not waking up -- will definitely interrupt your service regardless of location, technology or network provider. However, I found my device not working at other times too, and I started logging the output of mmcli
Code: mmcli -m any >> log.txt
I found at least 2 other problems that can break LTE silently resulting in a phone that won't be receiving calls or texts without the user even knowing it. In both cases, the problem can be detected in the output of mmcli. I'll quote the relevant sections as I describe the issues I've found.
Problem 1: Status
Code: Status | lock: sim-pin2
| unlock retries: sim-pin (3), sim-puk (10), sim-pin2 (3), sim-puk2 (10)
| state: [32mconnected[0m
| power state: on
| access tech: lte
| signal quality: 59% (cached)
When everything's OK, the line containing "access tech: lte" is present. If grepping for this term in the output of "mmcli -m any" fails, the device cannot make or receive calls or texts. This problem sometimes gets better on its own. But sometimes it doesn't either. Using the appropriate service manager to restart eg25-manager usually fixes the problem. BTW, the modem will come back with a new index number. When it gets better either due to eg25-manager restart, a phone reset or just on its own, the "access tech: lte" line reappears in the mmcli output.
Problem 2: Modes
When things are working (and problem 1 has been ruled out) I check the Modes section. I see this when things are working properly.
Code: Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: 4g; preferred: none
It took me forever to find it, but when I got a call on another phone to tell me I wasn't answering, I quickly logged the mmcli output:
Code: Modes | supported: allowed: 2g; preferred: none
| allowed: 3g; preferred: none
| allowed: 4g; preferred: none
| allowed: 2g, 3g; preferred: 3g
| allowed: 2g, 3g; preferred: 2g
| allowed: 2g, 4g; preferred: 4g
| allowed: 2g, 4g; preferred: 2g
| allowed: 3g, 4g; preferred: 4g
| allowed: 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 4g
| allowed: 2g, 3g, 4g; preferred: 3g
| allowed: 2g, 3g, 4g; preferred: 2g
| current: allowed: 2g, 3g, 4g; preferred: 4g
There it is the the "current:" line of the "Modes" section. LTE working ok and calls going thru I see "current: allowed: 4g; preferred: none".
OTOH, when calls and texts aren't working (even if the "access" issue above is fine) I see "current: allowed: 2g, 3g, 4g; preferred: 4g". The same status can be seen in the GUI "System|Mobile Network"
Doing an eg25-manager restart did restore service, but the current Mode setting remained "current: allowed: 2g, 3g, 4g;" until I went in and manually changed the setting in the GUI. I haven't tried changing the setting with mmcli, and don't know if I can or not.
Anyway, if anyone has any extra insights on this issue, I'd love to hear about it.
|
|
|
|
| Keyboard drawing only 0.1A from charger |
|
Posted by: qwazix - 07-08-2022, 12:09 AM - Forum: PinePhone Accessories
- Replies (7)
|
 |
As the title says, the keyboard is only drawing tiny amounts of power, regardless if it has a phone in it, if it's on, and of the constant current sysfs setting.
I did plug the phone in while docked before I read the warning, did I fry the charging chip?
|
|
|
|
| error when try to build infinitime 1.10 |
|
Posted by: gy145 - 07-07-2022, 08:45 PM - Forum: Development Discussion on PineTime
- Replies (2)
|
 |
Got stuck on building infinitime on my own computer. The following procedure worked well for version 1.9 but not 1.10
I used a win10 64bit computer. I installed Microsoft visual studio code and docker on my computer.
Here is what I have tried:
1. use github desktop app to make a clone of the infinitime code.
2. under github app choose the master branch tagged 1.10
3. then use the visual studio code to open the infinitime folder.
4. wait for visual studio code to run docker container, then opened an terminal
5. with root account
apt-get install npm
npm install lv_font_conv
6. runs the create_build_open_ocd.sh
/workspaces/InfiniTime$ cmake -G 'Unix Makefiles' -DCMAKE_BUILD_TYPE=Release -DUSE_OPENOCD=1 -DARM_NONE_EABI_TOOLCHAIN_PATH=/opt/gcc-arm-none-eabi-9-2020-q2-update -DNRF5_SDK_PATH=/opt/nRF5_SDK_15.3.0_59ac345 -S . -Bbuild
7. cd build
8 make -j pinetime-app
Then it gives error:
[ 42%] Built target lvgl
[ 63%] Built target nimble
(Stripping trailing CRs from patch; use --binary to disable.)
patching file jetbrains_mono_bold_20.c
patching file jetbrains_mono_bold_20.c
patch: **** malformed patch at line 3:
Traceback (most recent call last):
File "/workspaces/InfiniTime/src/displayapp/fonts/generate.py", line 75, in <module>
main()
File "/workspaces/InfiniTime/src/displayapp/fonts/generate.py", line 70, in main
subprocess.check_call(['/usr/bin/env', 'patch', name+'.c', patch])
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['/usr/bin/env', 'patch', 'jetbrains_mono_bold_20.c', 'jetbrains_mono_bold_20.c_M.patch']' returned non-zero exit status 2.
make[3]: *** [src/displayapp/fonts/CMakeFiles/infinitime_fonts_jetbrains_mono_bold_20.dir/build.make:73: src/displayapp/fonts/jetbrains_mono_bold_20.c] Error 1
make[3]: *** Deleting file 'src/displayapp/fonts/jetbrains_mono_bold_20.c'
make[2]: *** [CMakeFiles/Makefile2:590: src/displayapp/fonts/CMakeFiles/infinitime_fonts_jetbrains_mono_bold_20.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:286: src/CMakeFiles/pinetime-app.dir/rule] Error 2
make: *** [Makefile:189: pinetime-app] Error 2
|
|
|
|
| Dedicated Chat and Phone. |
|
Posted by: Chief - 07-07-2022, 12:14 PM - Forum: General Discussion on PinePhone
- Replies (2)
|
 |
Greetings folks,
After reading plenty of issues related to sound and phone I thought I might suggest a possible solution for Pine64 staff to consider. Since Android devices work excellent as phones but not so great as data devices whereas PinePhone works excellent with data but not so great as a phone ... why not marry the two together? Is it possible to have a PinePhone flashed from the factory with a dedicated Chat/Phone system separate from any o.s.? Further to this a system that can boot from the dedicated phone app with no other o.s. on the eMMC card? In doing so people can flash whatever o.s. they wish BUT the phone/chat system are already there preinstalled by factory and unaffected by any o.s. except where an address book is created in any Linux o.s. This way the phone will always work regardless and the sound system also dedicated to phone/chat. On the PPP we can flash tow boot to the SPI chip which I have done so I am suggesting something similar to that. So instead of a rolling update that destroys (potentially sometimes) the usability of the device a dedicated system unaffected by any update except where a flash update is released to the phone if required.
Just a suggestion to consider.
|
|
|
|
| No display on early boot after Manjaro update |
|
Posted by: robocone - 07-07-2022, 05:47 AM - Forum: PinePhone Pro Software
- No Replies
|
 |
After a recent update (Manjaro plasma), the display has stopped working on early boot, for example during initramfs.
My boot.txt has not changed.
It comes back on during the normal bootup.
Does anyone know how to get it working again? It's causing me major headaches, typing into nothing and hoping things will work.
Edit: I'm not sure what exactly fixed this but I'm getting the display on the current version
|
|
|
|
| Emmc |
|
Posted by: yvan - 07-07-2022, 01:47 AM - Forum: PinePhone Hardware
- Replies (1)
|
 |
Hello everyone, I have a small problem I wanted to change os on my Pinephone but Emmc na is displayed more when I use BalenaEtcher or Gparted and the phone does not want to start anymore someone would have a solution please
|
|
|
|
| Low Disk Space on Filesystem root |
|
Posted by: ichbins - 07-06-2022, 12:27 PM - Forum: Mobian on PinePhone
- Replies (9)
|
 |
Hello everybody,
I am trying to make a fresh install on my Pinephone, but it results in a device that is not booting anymore. I am flashing mobian-installer-pinephone-phosh-20220621.img to eMMC and the installation works as usual. After the installation I run apt update and apt upgrade and get this message in the status bar:
Low Disk Space on "Filesystem root"
The volume "Filesystem root" has only
166.3 MB disk space remaining.
The update process shows a littlebit later: No more disk space available.
Code: cp: Fehler beim Schreiben von '/var/tmp/mkinitramfs_sbR54T//usr/lib/aarch64-linux-gnu/libharfbuzz.so.0.20704.0':
Auf dem Gerät ist kein Speicherplatz mehr verfügbar
ERROR: Couldn't copy /bin/osk-sdl
E: /usr/share/initramfs-tools/hooks/osk-sdl failed with return 1.
update-initramfs: failed for /boot/initrd.img-5.15-sunxi64 with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
I: u-boot-menu: syncing /usr/lib/linux-image-5.15-sunxi64 to /boot/dtb-5.15-sunxi64
P: Checking for EXTLINUX directory... found.
P: Writing config for vmlinuz-5.15-sunxi64...
dpkg: Fehler beim Bearbeiten des Paketes linux-image-5.15-sunxi64 (--configure):
»installiertes post-installation-Skript des Paketes linux-image-5.15-sunxi64«-Unterprozess gab den Fehlerwert 1
zurück
I never had this disk space problem before, when I made a fresh installation. How should I make the installation and update to get a working system?
|
|
|
|
| PinephonePro camera calibration conundrum |
|
Posted by: orbital - 07-06-2022, 09:09 AM - Forum: General Discussion on PinePhone
- No Replies
|
 |
Hi,
I noticed that Megi (i.e. Ondřej Jirman at https://xnux.eu/log/#069) has recently been working on calibrating the IMX258 sensor.
But is it Pine's plan to have people calibrate at home like he is doing, instead of calibrating at the factory?
There's a reason why companies like Foxconn calibrate every sensor at the factory: It's because every single sensor is slightly different.
Without special equipment, there is no reliable way to calibrate a color Bayer sensor at home.
Now, if Pine had used a grayscale (B&W) sensor then maybe calibration would be possible, but they didn't.
So what then is the actual plan once Megi is done?
Will his code be used at the factory?
If yes, will each person who buys a PinephonePro receive a file containing calibration info for the phone?
Megi points out that unlike other phones, the Pinephones don't include an EEPROM to store calibration parameters, so it will have to be in a file somewhere.
And how will people who have already bought the phone get theirs calibrated?
|
|
|
|
|