I'm trying to find simple instructions for how to compile and implement fbkeyboard so it's running at TTY when it asks for login/password on PostmarketOS.

Repo: https://github.com/julianwi/fbkeyboard
Example of it running at tty login on a Pinephone: https://youtu.be/npKwMWr1F_0?t=1099

I've searched around a while but can't seem to find much. The repo's readme is somewhat helpful but i'm not used to Alpine's musl compiler or how to auto-start a program so it's runs at the TTY prompt.

Much thanks for any suggestions and if I find the answer i'll post it here.

Like the title says, I did an apt dist-upgrade and now I can install gnome-contacts and loose chatty(SMS and some IM) or install chatty and loose installed gnome-contacts.  No matter what gnome-contacts is broken or gone so I choose installing a working chatty and use the phone app for contacts short term.
More of an FYI as I expect it to be fixed in a few days unless anyone has a slick fix.

I have successfully installed Arch Linux on my Pinebook Pro using the following wiki article:

https://wiki.pine64.org/wiki/Installing_...nebook_Pro

However, I had to use the Pinephone dock to enable networking because the wifi adapter does not work out of the box.

dmesh output shows:

brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43456-sdio for chip BCM4345/9
brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.pine64,pinebook-pro.bin failed with error -2
brcmfmac mmc0:0001:1: Direct firmware load for brcm/brcmfmac43456-sdio.bin failed with error -2


I tried some suggestions from the friendly people on the Pine64 Telegram channel but until now I cannot get it to work.

Here is what I tried:

https://forums.raspberrypi.com/viewtopic...7&t=291688

This is a thread on the Raspberry Pi 4 which seemingly uses the same hardware? I tried copying the suggested file but that did not solve the problem. Note that the file was not there in the first place so renaming failed.

Copied the files found here:

https://gitlab.manjaro.org/manjaro-arm/p...6-firmware

Also this did not solve the problem.

Another suggestion is to see whether the alarm repos have a firmware package for this but I'm a bit at a loss as to how to do this.

A usb wifi dongle works without any problem so I have a workaround but I would be happy if the on board wifi would work.

Any help/pointers are appreciated.

I know that some people have it working so it is just me not having found the solution yet.

Back in the N900 days we had an app which used rendezvous auto discovery IM protocol to bridge the phone's SMS to LAN instant messenger.
While HeySMS could probably be ported or cloned with recent libs https://talk.maemo.org/showthread.php?t=84705 I think that there is probably a quick ready to get a basic SMS send.

Is there an easy way to send a command line trigger or AT command followed by the text to at least write a SMS and then send it over SSH.

According to Megi's 6/23 blogpost, the PinePhone Pro is missing camera calibration data.

Any chance PINE64 has the equipment to get professional camera calibration for the hardware they ship?

I am an everyday driver pinephone 3-32gb w/mobian user.
The reboots and modem cutouts during the day are survivable, but the battery life is difficult at best.
If I rent a car and the poser or USB port is dead it means only satellite navigation at the end of a trip.  No video or surfing on the train unless there is a USB port or mains jack.  Even listening to an audio book can easily knock me to below 50% after two-three hours and will continue to until the hardware audio acceleration and buffer is improved.  Even 10 minutes checking webmail can easily burn 15%.
Most often the answer is Megi's kernel, but as this is an everyday driver phone I want something at least as stable as I already have.
If Megi's kernel is better why is it not adopted by Mobian or other distros?
What is the downside aside form being outside the normal software upgrades?
Back in the Nokia/Maemo days the testing repos for Maemo5 had the power kernel with all of the extra community tweaks to turbocharge the distro and it included missing hardware optimizations, all just an apt-get install away from a reliable alternate to the Nokia kernel.

To those already running Megi's kernel and other tweaks what is your difference in battery life as well as system performance, what about system reliability?

https://xnux.eu/howtos/build-pinephone-kernel.html

https://github.com/megous/linux/tree/orange-pi-5.16

Eu professor me presenteou com um pine64LTS, e sou noob com essas coisas.


É possível instalar algo semelhante ao "Retropie"? Instalei o Armbian e executei o . mas o que fazer com este pinho 64lts ?

SO,
I have a pinePhone Pro Explorer and the keyboard phone holder.
Firstly. Is there an easy or "recommended" method of removing the Phone from the the keyboard holder??? I was forced to use tweezers and twist them and try and wriggle them behind the phone and in front of the screen bit just to get the phone out. It wasn't easy, and the phone now has scratches on it.

Real Newbie question.
What do I do now??
I REALLY wanted this pine phone so I could seamlessly integrate the phone with my desktop. Abilities to sync emails, copy of phone calls, Voice recordings of VoIP calls, copy of sms & mms, and files.
I don't use social media full stop, and have no intention of ever using it. ScoialMedia just sucks the life out of privacy!


How do I go about Testing things? I am half a point higher than a noob with linux to begin with, but I can search and figure things out. I do like a good problem to solve, as long as I know it's a problem.

SO FYI. Ask me to work out how to change something setting on the phone. My Autistic brain will thank you for it.

Will I ever learn. I did a dist-upgrade this evening, immediately lost access to the internet via wifi. So I restarted the PPP and it came back up but still no internet via wifi. 

I tried shutting down and booting instead of just a restart. Now I cannot boot from the SD card with mobian on it at all. Or at least not in the same way I started it up til now. Double press and short hold on the power button normally did the trick but now nothing. 

I just checked to see if it was a coincidental hardware failure but the PPP boots OK from Manjaro/Plasma which came installed on the eMMC.

Anyone else experiencing anything similar?

I have been trying to get the any of the BSP images to boot on the SOEDGE. I made some discoveries along the way I thought I would share. I did not see these posted anywhere else so hopefully this will help someone else.

I could not use rkflashtool on linux. It would not detect the SOEDGE while in maskrom mode. I did not troubleshoot this very far, but I think it's because it USB PID is not what rkflashtool expects. Maybe there are some udev rules that could fix this.

I tried several combinations of drivers and software on Windows 10. I eventually got the BSP image to work with the usb A to A cable.

The Rockchip tools download links in the wiki no longer work at the time I tried them. I did find a version of AndroidTool (RKDevTool) elsewhere that works. The exact version was labeled AndroidTool_Release_v2.71.zip. I used the drivers from DriverAssistant v4.5. I used the links from the Firefly Core-1808-JD4 download page.

With this combination, Androidtool was able to detect the board and flash it with the BSP images in the wiki. If you flash the Factory Test Build by Gamiee and have the touchscreen attached to the baseboard, it will boot up with a splash screen and then load a simple touch interface.

Also, like other have stated, I was not able to get the serial console working. However, adb will work. If you keep AndroidTool open and leave the usb A to A cable plugged in. It will change the detected board status from maskrom to adb after the board boots up. I used the adb_tools.zip for Radxa. With a adb start-server and adb shell, I was greeted with a prompt that was clearly the SOEDGE running.

After reading about the SOEDGE on the forum, I consider this a win as I never thought I would see this thing run code.