Dear all,

I would like to have a PinePhoneMax with a 8-9" screen.

In my opinion a 13" tablet (with sim-card slot) seems to be interesting,too.

What do you think about my suggestions?


Jürgen

Offering my Pinephone Pro Explorer Edition + Soft TPU Protective Case + USB-C Docking Bar + Extra Tempered Glass Screen Protector, Pinephone Braveheart Edition w/VCONN mod + Soft TPU Protective Case, and Pinebook Pro + Barrel Plug Charger.

Reason for sale - I bought this hardware years ago and I have barely used it since.
Ships from - Mexico.
Condition - Pinebook Pro is like new, Pinephones are lightly used.

Minimum asking prices (shipping not included):

PinePhone Pro + Accessories = $250 (SOLD!)
PinePhone + Accessories = $50
Pinebook Pro = $120

Items can be sold separately. If I receive multiple offers, I will go with the best offer.

Reply or DM for more info.

Howdy!

I just got my pinetab2 in the mail today and I can't seem to get it to charge.
It powers on just fine and I've got wifi working and upgraded the OS, but I can't get it to charge.
I'm at 60% and dropping.

I'm using the included cable and I've tried various chargers, but nothing works.
I've tried several that say they run at 5V and 3A, but nothing has worked so far.

Is it DoA?
Has anybody else had this issue?
I searched, but couldn't find anything.

Thanks!

Hi friends,
I decided to install manjaro xfce on my Pinebook,and after a quick review of websites and wiki pages,I have realized that the device boots surely from a SD,maybe 
there are different procedures,but the straightforward one is the SD...But how can I write the image to MMC? I tried to write the image from an USB drive to MMC using dd from a live OS brought through the SD...Something has gone wrong and my device can't power on...I love this device and the underlying idea,can someone please give me an hint?...

Yesterday I unboxed a new PinePhone Pro bought recently. Here are some things I noticed that were problematic (posting here as feedback to Pine64):

- The battery was completely dead, as in 0 volts at the terminal. There was a plastic protector over the terminals, so that wasn't the issue. At first I thought maybe internal low voltage protector had kicked in. I charged it for a bit then checked the voltage and it was at around 2V.  It really is a dud battery. I managed to charged up to full (constantly checking temperature and whether it's expanding or not). As expected, capacity seems to be way down (voltage drops rapidly when using it), I'll probably have to toss it. Ordered a Samsung J7 replacement. Pine64, please test the batteries before shipping!

- Even though rk2aw was installed to SPI, there's no primary or fallback bootloader installed. This caused me massive amounts of pain, because rk2aw needs to boot to a bootloader. When I turned on the phone for the first time, I saw u-boot, so assumed it's installed to SPI. I selected to boot off the first option, but after waiting a bit I just saw a black screen, so assumed maybe no OS is installed. I anyway wanted Mobian, so I flashed it from SD card to eMMC. This wiped the bootloader off the eMMC, and I was thus stuck with a non-booting phone (since my Mobian image doesn't have a bootloader). I couldn't find an image that had a bootloader already installed and writing a bootloader onto the SD card didn't work for me (bootloader loads but hangs on booting up a kernel). The only fix that got me out of this mess was to use tow-boot's installer image to wipe rk2aw off the SPI and put tow-boot there. Pine64, PLEASE put a primary and fallback bootloader into SPI as part of your rk2aw installation, I recommend u-boot (with binary bits for DDR) as primary and maybe tow-boot as secondary fallback? This would avoid so many problems!

Anyway apart from those issues, now that I finally have a working OS installed, it's great

Hey everyone,
I've been experimenting with running Android games on my PinePhone, and I wanted to share some findings while also seeing what others have tried.
Since PinePhone runs Linux-based OSes like Manjaro, Mobian, and PostmarketOS, getting Android apps to work isn’t always straightforward. Here are a few methods I’ve tested:

1. Anbox – This allows you to run Android apps inside a Linux container. It works decently for basic apps, but performance can be hit-or-miss with heavier games.
   
2. Waydroid – A more optimized solution that runs a full Android system inside a container. It provides better performance and supports the Play Store and APK installations natively.
   
3. Emulation (QEMU or Box86/Box64) – Not the best for gaming, but some people have managed to run older Android versions through emulation.
   

• Simple 2D games (puzzle, card, retro) work fine on Waydroid.
  
• More demanding 3D games may struggle without GPU acceleration.
  
• Touchscreen responsiveness depends on the OS and Waydroid’s integration.
  

Hello all,
I have set up my PPP following @mikehenson's  guide. I have everything I need in order to daily drive the phone working. With the exception of mms. Unfortunately I have to have mms working in order to daily drive it. I initially thought the issue might be something I didn't configure correctly, or something in the software side of things. I have since come to the conclusion that it must be a problem on the Tracfone side of things. I am using T-Mobile through Tracfone as my provider. I have data and sms working, I just can't get mms figured out. I started off using T-Mobile's APN and MMSC settings, however though I had sms and data I could not send or receive mms. I then tried Tracfone's recommended settings, and the settings listed here, both with the same results. I've also tried many other combinations of APNs, MMSCs, and Proxies from all over the web. I think part of the problem at least might have to do with the Verizon Migration of Tracfone, and the resulting chaos of the transfer, but I don't know for sure. This brings me to my question: Does anyone here use Tracfone on their ppp, or have any experience with it? If so how/did you get it working, and with what settings? Any insight would be much appreciated. 
Thanks!

Hello Pine64 Team,

I am a big fan of your open-source projects, and I would love to use the Pinecil V2. However, due to customs restrictions in Turkey, I am unable to import it into my country.

To overcome this issue, I would like to manufacture a Pinecil V2 unit for my personal use only. I have found the schematic and PCB placement files, but I need the Gerber files to proceed with PCB fabrication.

Since Pinecil is an open-source project, I was wondering if you could provide the Gerber files for Pinecil V2 or guide me on how to generate them from the available resources.

Thank you for your time and for supporting open-source hardware!

Best regards

I would like to see a PineTime LTE version with eSIM support... if there is even an open-source/free software OS that can support this. From what I understand, Google has not open-sourced WearOS.

Somewhere (not on this forum) there was a pretty detailed article that described how to replace a touch panel of the Pinephone - or perhaps the whole LCD assembly - with a third-party one from AliExpress instead of from Pine64. AliExpress alternative was much cheaper, had more shipping options and didn't have any availability problems (i.e. at the moment a Pine64's Pinephone LCD replacement - is "out of stock" for a pretty long time).

I had this article saved somewhere in my bookmarks, but now I can't find it anywhere - and extensive googling does not help yet. Two things that I remember:

• it turned out that Pine64 changed the pinout of touch to make it more "proprietary" (maybe so that everyone is forced to buy this replacement part from Pine64), two pins were switched - but I don't remember which ones
  
• this article was a couple of years old
  

Quote:Buy a two dollar lighter that uses a piece of quartz as an ignition source... Electrical discharge... Not the type with a piece of flint inside. The main difference and clue you have the right one is, the flint one has the rollers on top you run your thumb across as you press down on the button/trigger to release its gas for ignition. The lighter you want has just one button/ trigger. First vent or empty butane gas... Release valve on bottom. Then remove the quartz igniter from the lighters housing and place on you phones dead screen click/ press it a couple of times..for me three times. Dead zone/dead bar fixed.. no more ghost touches either. Fixed... 2.00 dollars... but keep igniter around in case screen goes dead again but after a couple of clicks screen permanent fix for me. For a detailed youtube video of the process, search keywords screen fix quartz iginiter.... the error is a digitizer fault, often due to your phone overheating for long periods at a time. The quartz igniter generates around 350 to 400 volts to the lcd screen and attached digitizer ..harmless to your phone and you... this electrical discharge that awakens the dead zone like magic. No costly repairs of digitizer and LCD screen