Dear Pine64 Community,

I really really love PBP. But, it's dead, unable to boot up.
I'm not sure what I did that caused PBP dead.

I have done all Wiki and steps to reset, bypass the power and reset again. None of this worked.
Please kindly advise. Thanks.

I don't know who thought it was a "great idea" to move Firefox's address bar to the bottom of the screen but I find it really annoying and confusing. How can I move it back to the top where it belongs?

So far the only thing I've found is this suggestion from Mozilla support  from nearly 2 years ago saying to go to Settings, then Customize:

https://support.mozilla.org/en-US/questions/1296961

However I don't see "Customize" in the settings and searching doesn't find it either.

Like the title says. This worked fine for quite a while.

Today I flashed tow-boot to emmc and reinstalled mobian.
Now, Portfolio doesn't extract zip files any more ("Could not open <filename>.zip").

Unzipping in the terminal works.

I wanted to uninstall and reinstall but unfortunately, uninstalling Portfolio isn't possible  in "Software" ("Unable to remove Portfolio: no packages to remove"). I also can't find a target for apt remove.

Does someone have an idea how I could fix the zip function or how I could uninstall Portfolio? Maybe the flathub version works better...?

Portfolio was quite usable on the Pinephone and fulfilled all my needs. I just want it to work like it did before the reinstallation.

Thanks in advance

Has anyone been able to activate a Tracfone or US Mobile SIM on the Pinephone and be able to make calls?  I have activated cards from both on my Pinephone and it seemed to go well but I can not make usable connections (calls usually do not connect at all) and the phone will not stay registered.

Do I have to get another SIM and activate it on a different phone?  That seems to be what most do.

I couldn't find out, what this big white 6 pin socket on the board is used for. Someone has a clue?
The other question is: there is this jellow jumper which selects the clock signal. In the schematics drawing one can see, that pin 1 selects the board's clock. Now I wonder which pin is pin 1.
regards,
Hans-Peter

I received my Pinephone Pro about a month ago, played with it a little bit and haven't used it until yesterday. I booted it once and powered it off again as I wanted to try another os.

After that I was unable to boot it. The battery and charging seems to work fine (checked it with a voltmeter). I was also unable to boot to sd following all instructions in the wiki.

Android 11 ATV build

gapps not fully working googleplay wont work yet apps can be added through uptodown app or usb etc

inspired by the builds of mo123 for other devices i am trying to make a ATV build for the Quartz64-a

only from google login issue it is working nice on my device 
4K,HDR, wifi etc

some cooling is advised

gpt image wich you can flash on sd or emmc

dts used :
https://github.com/Shaggy013/diesel/blob...tz64-a.dts

android 11 source with rockchip sdk  (just google )
added gapps https://github.com/opengapps/aosp_build

android box configs:
https://github.com/Shaggy013/diesel/blob...dConfig.mk
https://github.com/Shaggy013/diesel/blob...56x_box.mk

gpt image

https://drive.google.com/file/d/1tGIoHn4...sp=sharing


       

I have found over the years that when working with open source navigation and mapping most involving OSM it can be difficult to import and export locations especially when using a non-Roman alphabet.
When possible I like to be able to input and export WGS84 latitude and longitude so say I was referring to Bern Switzerland I would input 46°56′53″N 7°26′51″E into the map app.
IN LineageOS with microG even a google maps link with coordinates will give the option to open with OSMand mapping app.
I have tried dumping raw lat/lon into both the Gneom Maps and PureMaps apps and neither can read the raw decimal or deg,min,sec not even n46, e7 or 46n, 7e is received as useful input. Perhaps the app can be launched with coordinates via CLI?

There are commands to get coordinates directly via terminal

I am probably going to be wiping my PP soon and reinstalling mobian to rule out any kludged hand-hacking I did to the system especially bridging as I am trying to get us a working implementation of Bluetooth PAN wireless access point to share mobile internet to your gadgets without the massive power waste that WiFi is.

https://forum.pine64.org/showthread.php?...#pid109129



so to backup:

For me I only really care about my SMS and messaging so saving my .purple chat history which handles all of the IM and SMS stuff

cp ~/.purple/chatty/db/chatty-history.db /meda/mobian/yoursdcardname/

copy that to the SD card, then the same for contacts

cp ~/.local/share/evolution/addressbook /meda/mobian/yoursdcardname/

dump these directories back where they go in the new install


I could also save installed files to speed up restoring my system

apt list --installed | /meda/mobian/yoursdcardname/installedaptpackages.txt

which would give me a list of installed files dumped into a new file installedaptpackages


flatpak list | /meda/mobian/yoursdcardname/flatpakinstalls.txt
to have a list of installed flatpaks

Really I could copy all or selected parts of the whole user(mobian) /home directory to get all of the settings identical but I want a clean install free the previous months of attempted hacks and scripts.



I like that maemo for the N900 had a nice app to save messaging settings, calendar, and installed apps, it could even be a script to make a backup.

Hey all. The PinePhone Pro was released in what I see as a fully-disclosed early adopter state.



In spite of that openness, I see posts here which claim that it's not possible to make the device work correctly. I, at least, have everything I need working fine, so I figured I'd share how you too can get to that state. By posting this I hope to accomplish three things:



1. Making users who claim it's impossible to make such-and-such feature work or "the device isn't ready for daily driving!!!" go away

2. Help very technically proficient users get their own devices into a better state

3. Show maintainers what they should make happen out-of-the-box to provide a superior user experience for the PPP



That said, there is a major caveat here: I don't present these steps as "easy" or "simple". This is just a summary of exactly what you have to do to go from a fresh PPP to a working daily driver, right now.



Inventory of what works after following this guide:

- Arch Linux ARM base (community support), with several patches to important components like the kernel

- Encrypted root (for me, this is a requirement for a daily driver) with graphical unlock working with both touchscreen and hardware keyboard

- SXMO desktop environment

- Phone calls

- SMS

- Suspend/Crust, reliably, including receiving calls while suspended

- PinePhone hardware keyboard case, inc. charging

- Bluetooth, inc. audio

- fwupdmgr and pacman updates like a normal computer



What does not work even if you follow all these steps:

- Either camera (kernel support exists, but userland isn't finished yet)

- After resume from Crust, on some but not all occasions non-call audio is sped up by a factor of exactly 3x, with the corresponding increase in pitch. I have seen developers comment on this before so I believe it's a known issue. You can see that's what's happening because using mpv to play the audio at 0.33 speed (disabling auto pitch correction) results in normal audio. I have not yet devised a reliable way to poke the phone out of this state.

- Booting the phone if you entirely deplete the battery. Don't entirely deplete the battery. If someone tells you there's something that doesn't work right, please stop posting thread after thread pointing out that the thing they said doesn't work... doesn't work.

- SXMO doesn't have a proper lock screen. Very disappointing. The hardware keyboard keys will still work through "lock" and also there is no PIN screen. I'm exploring putting swaylock or similar on the phone, which should work fine.

- SXMO doesn't let you use the phone normally while in a call. Also just a software problem.

- You need to disable charging the phone with the hardware keyboard to be able to use the phone USB port for ANYTHING, including something basic like a Yubikey. Not just charging! If the keyboard is powering the phone, you can't use USB. This is a hardware problem.

- uBlock origin in Firefox has a rather broken UI



What is untested by me but might be important:

- Android app support w/Waydroid (reported to work...)



Credits: a huge number of talented developers wrote the parts I'm stitching together here. You should thank them for their work. All I've written is packaging scripts and configuration...



Revision Notes:

1.1 Removed step compiling a new kernel, as the kernel in danctnix's repo is now sufficiently up to date to work and can just be installed.

1.2 Removed custom build of Arch base, as Dreemurs distribution is now sufficiently up to date
1.3 Removed keyboard and SXMO customization, as Dreemurs distribution has those



All right, let's get into making our phone work!