Greetings everyone, just got a used Pinephone Pro (and a pinephone but haven't used that yet) and am trying to dredge up years-old pre-brain surgery Linux knowledge to make this thing work as a palmtop full time. Currently I am running Mobian with XFCE and I am working on getting the keyboard and the screen rotation working correctly. With regards to the screen, I have two lines in /etc/lightdm/lightdm.conf (which may be the wrong place but one tutorial mentioned it so I'm using it for now)

[Seat Defaults]
display-setup-script = xinput set-prop "pointer:Goodix Capacitive TouchScreen" --type=float "Coordinate Transformation Matrix" 0 1 0 -1 0 1 0 0 1
display-setup-script = xrandr --output DP-1 --off --output DSI-1 --primary --mode 720x1440 --pos 0x0 --rotate right

The first line fixes the touchscreen so I can use it in landscape mode from within the OS. The second makes the greeter landscape, but now the touchscreen is equally broken (swipe to the right, cursor going up) in both the greeter and the OS itself because the first line is "cancelled out." If I comment out the second line, the first works.

I've barely managed to scrape these solutions together from tutorials and I have no idea why one would mess with the other and I'm completely lost. Any ideas? Ask me anything and I'll answer what I can.

(Also I'm doing my best to follow the rules but my reading comprehension is not the best so please if I am breaking any I swear it's an accident and will correct it asap)

Hello all, 

I was wondering if anyone had a fix to the following problem I ran into when setting up WIFI and Bluetooth functionality on the PineTab. I got through the WIFI setup without issue and it works great, but when running the following to setup Bluetooth:

Hello,



I have been using and loving my PineTime for almost 2 years, and it has suddenly developed a hardware issue. The touchscreen will not respond to touch, and the battery drain has gone from 16 days on a single charge to 2 days. I have rebooted the PineTime twice, flashed it from 1.13 to 1.14, allowed it to drain completely to shut it off, and nothing has helped. I'm not sure what could have caused this, I didn't drop or hit or soak it, from the battery drain it looks like it started at 5am when I was sleeping. Is there a way to repair it? All the other functions such as the step counter, bluetooth pairing, the physical button, notifications display etc all work.



Video:

https://imgur.com/Y7MA8Xq



Gadgetbridge showing it started at about 5am:

https://i.imgur.com/evRUXXr.jpeg

There are at least eight threads in the PINE64 forum discussing security of the OS used on the PinePhone... :

id=13214 - "Firejail: Sandbox Pinephone/Pinetab Apps"
id=16110 - "Most secure option for phinephone"
id=13179 - "PinePhone Security"
id=14709 - "Security/Musl Question"
id=12457 - "Secure Mobile OS"
id=12303 - "Securing / Hardening The PinePhone"
id=12210 - "Can internal PinePhone firmware be compromised?"
id=11430 - "Security Based OS ?"

...but none of them mention Kicksecure.

According to three threads on the whonix forums:
https://forums.whonix.org/t/whonix-for-a...pi/723/209
https://forums.whonix.org/t/cross-buildi...md64/11607
https://forums.whonix.org/t/whonix-on-ma...g/11310/40
it is possible to use Kicksecure on ARM, including Raspberry Pis and Apple Silicon.

I can't find the Github link right now but I did see that SkewedZeppelin is already using at least one Kicksecure component in DivestOS, so it's not unprecedented that Kicksecure might be applied to a #MobileLinux ARM device.

So my question is, what would the PINE64 community think of converting a Mobian install to Mobian-Kicksecure ("Sneakernic"*, anyone?) on the PinePhone?
*nod to Sonic the Hedgehog

Pinetab is an excellent product.

I'm working on getting the Bluetooth connected. The page Wifi and Bluetooth on PineTab 2 mentions the command

I had Armbian running from a MicroSD card for a while and it worked pretty well. I did an "apt dist-upgrade" the other day and now it won't boot into a graphical desktop. And it doesn't come up on the network because I can't ping it.

I installed the latest Armbian onto another MicroSD and it doesn't work either.

So their image for the Pinebook became broken probably in the last few months.

I tried an earlier image from 2023 and did an "apt dist-upgrade" on it and it broke too.

Sucks. That is a nice OS.

A year to 2 years ago, I was heavily involved in trying to get PPP usable through software tests and mods.  I provided about 150 comments to the forum in this effort.  I tried so many SD card, SIM card changes during this testing that I physically broke the SIM card holder in the PPP phone making it not functional as a cell phone.  I never received the free replacement SIM card holder that was promised by Pinephone even after providing all of their required data.  For more than a year, my PPP (and the earlier PP) has been shelved and I have dropped out of PPP efforts.

I am still a believer in linux phone technology, particularly for privacy reasons, after I see reports of the newest gimmicks by the major phone manufacturers. I am also a 20 year exclusively linux user on my PCs. 

I am trying to get an assessment of where PPP stands as to functionality currently to be a "daily driver" cell phone.  I am retired, i.e., heavyweight business needs are over; my needs are moderate. I would put money into repairing my PPP if things currently look better. 

Here is what I would need in order to justify an investment into getting my PPP repaired.
     At least 12 hour battery life w/o charger
     Functional recharging capability
     Reliable/repeatable boots
     Good capability to send and receive phone calls where one could hear and be heard by a connecting party
     Ability to reliably send SMS messages over cell network.  I use Consumer Cellular which did allow calls on PPP with it's SIM card on some OS              a while ago.
     Ability to send MMS messages (attachments)
     Some auxiliary app functions, i.e., navigation, cameras would be nice if progress has been made on that.

Would appreciate any info on your success in meeting these needs. Include OS and desktop name and versions.  Also any mods made to the phone to achieve.

thanks all.    tom kosvic

Does anyone know of a large 3d printable case for a Quartz64 Model A that could fit a Pcie card and approximately one 3.5in hdd in addition to the board? I'm not actually putting in a drive, I just need about this much space.

I'd use the PinePro 64 metal case as it is ideal size, but I'm not a fan of the construction that puts one of thewalls offsett from another internal wall, then there is a huge square hole... It signifficantly lowers the usability of that case for me.

Alternatively if someone has a dimensioned drawing of the mounting pattern for Quartz64 Model A please share. I can make my own.

I'm having some difficulty after updating to the latest plasma 6 version of the operating system
Installed Calibre e-book viewer via Discover Software Center hoping to find an DRM plug-in in order to use my Pinetab2  to view epubs downloaded via Libby.
Calibre installed, but fails to open after processing initial setup. I decided to re-install the OS using the latest factory image from the releases site.
After updating, (sudo pacman -Syu) Angelfish began behaving as Calibre did, (starts to launch then stops with no message. Removed, (sudo pacman -R Angelfish) and re-installed, (sudo pacman -S angelfish) - same result.
Error when running from command line:
angelfish: symbol lookup error: angelfish: undefined symbol: close, version Qt_6

Also, today's attempt to update via "sudo pacman -Syu" resulted in error:
:: Starting full system upgrade...
resolving dependencies...
looking for conflicting packages...
 
Packages (7) bluez-5.76-1  bluez-libs-5.76-1  composefs-1.0.3-1  glibc-locales-2.39+r52+gf8e4623421-1  mkinitcpio-39.1-1  ostree-2024.6-1  xorg-xwayland-24.
1.0-1
 
Total Installed Size:  228.53 MiB
Net Upgrade Size:       30.49 MiB
 
:: Proceed with installation? [Y/n] checking keyring...
checking package integrity...
loading package files...
checking for file conflicts... 
error: failed to commit transaction (conflicting files)

Then, about 40 pages of:

glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_ADDRESS exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_COLLATE exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_CTYPE exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_IDENTIFICATION exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_MEASUREMENT exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_MESSAGES/SYS_LC_MESSAGES exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_MONETARY exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_NAME exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_NUMERIC exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_PAPER exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_TELEPHONE exists in filesystem
glibc-locales: /usr/lib/locale/aa_DJ.utf8/LC_TIME exists in filesystem
glibc-locales: /usr/lib/locale/af_ZA.utf8/LC_ADDRESS exists in filesystem
glibc-locales: /usr/lib/locale/af_ZA.utf8/LC_COLLATE exists in filesystem
glibc-locales: /usr/lib/locale/af_ZA.utf8/LC_CTYPE exists in filesystem
glibc-locales: /usr/lib/locale/af_ZA.utf8/LC_IDENTIFICATION exists in filesystem
...
Sorry for the lengthy post, if any further info required I would be happy to provide it.
Any Help appreciated

Early versions of wireplumber had a bug that prevented switching the audio output from the earpiece back to the speaker after a call, meaning the next call would ring through the earpiece. This was issue #156 and is fixed in v0.5.2, available now in Trixie.

That fix unmasks 2 other related issues which I suspect have been around for awhile.

1) When I disconnect a call that had been on speaker, the output sometimes gets switched to the earpiece instead of being left on the speaker. The next call then rings through the earpiece. The currently-selected ports can be queried with: