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:

I don't know whether it's just my unit, or Tow-Boot and Arch Linux ARM, but it tends to happen that I plug in my PPP to charge over USB and it won't charge until I re-insert the battery.

Yes, I suspended in the meantime, and I was made aware in the #pinephone Matrix that it causes the battery level to be incorrect.

Is this a known issue? Does it indicate a hardware fault?

Hi!
I have bought a Rock64 for running Netbsd and downloaded pre-built, bootable 10.0 image from https://nycdn.netbsd.org/pub/arm/ for this board.
Then I verify, gunzip and dd the .img file to sd/emmc, insert card and power on. I get a green power light a red st.by and a white pwr light and that's it. Ive done this the exact same on pinebook pro and rpi3b many times with no issues. Just works. I also tried the "daily" but no noticable difference.

I have successfully booted an image from armbian just to verify the hw is working.

Even tried the 9.4 image so now i'm running out of ideas. Btw also tried the dd u-boot to sd but it should not be necessary with these images as far as I know...

Anyone using these images who could help me out here?

I have a pinebook pro with a rather old version of u-boot on it (it says U-Boot 2017.09-04094-g969502b-dirty), and I was thinking it would probably be a good idea to update it.

What version/versions are known to work, and are there binary releases available to download, or should I compile it myself?

Hello,

I am evaluating if PineTime would be a good idea for my 7 year old son. He might have some light ASD.

• He gets reassured by knowing the current time (24h format or analog, not AM/PM)  
  
•  I'd like him to receive a notification for specific moments in time when he should be doing something, repeating for day of week.  
  
•  An agenda view and some notes would also be good, he really needs some knowledge over his own life.
  
•  If I could attach small pictures or specific noises to the notifications and agenda, that would be great.
  
• I want only the minimum of distractions, no games, etc..  
  
• He also tends to freeze/daydream and forget where he is.  I wonder if the step detector could detect this and make a noice to pull him back to reality
  
• I'd like this in Dutch/Flemish
  

My second battery went poofed.  That is two batteries in 16 months.  The original battery lasted
11 months.  No PP for 1 month.  The second "Samsung clone" battery lasted 4 months. 

The second battery acted up a month ago.  I tried moved (recharging PP) from old power strip to
a surge protector and thought that solved the problem.  Now battery is dying.

The first battery, I did USB charging for awhile.  Thought it was too slow and moved to the old
power strip.  Battery lasted longer, but still died.

-----

Can you share your experience in recharging PP?  Does surge protector helps?  Or slow USB charging
is best?  Or what?  Any tip on recharging PP so that battery lasts longer?

Burning a battery every 1/2 year is not pleasant.

Thank in advanced for your story.

Sheng-Chieh

I find it odd that there are essentially *zero* good and affordable solutions for push-to-talk systems.  Everyone just accepts crappy FRS quality since there's not really anything better available.

It would be amazing to have a simple dedicated device with a speaker, mic, 3.5mm port, a tiny display and menu button, and a push-to-talk key.

It could come out of the box preprogrammed with a few ESP-NOW based channels, and then allow you to add RTP multicast paging on a proper WiFi network(Which seems to be what the expensive SIP phones use).

The ESP32 can handle Opus compression, so there should be enough bandwidth for a few repeater hops.

If it was 18650 powered it should be able to last all day, so you could just leave a few around as repeaters, one hop is probably enough for 90% of things FRS is actually good for.


The same hardware could also connect to a smart voice assistant server, act as a wireless media streaming target, or be a wireless doorbell beeper for home assistant.


I've seen a bunch of projects like this, but nothing available as a mass produced, ready to use device.