The Armbian build system has added support for building images for Quartz64. Test images are available via links.


Quartz64 A

https://disk.yandex.ru/d/xMVoaZXFFcWuog

https://users.armbian.com/balbes150/quartz64/



SOQuartz + SOQuartz Model-A Baseboard.

https://disk.yandex.ru/d/Oq5yvBkuIK4R3A

https://users.armbian.com/balbes150/soquartz/


Quartz64 B

https://disk.yandex.ru/d/u0ioJbqtXqvJ6w




The Armbian build system allows anyone who does not even have special skills to work with complex compilation and assembly procedures. independently (for example, not mediocre on the Quartz64 device itself) to build your own kernel version (change the configuration and get your own version of the kernel) or completely your own version of the image with different DE or package composition. To do this, it is enough to follow very simple steps.

Can anybody tell me what exactly
Does this sentence mean?

booti  ${kernel_addr_r}  - ${fdt_addr_r};

We already have almost everything we need here.
I want to get Bluetooth hotspot working on my Mobian/Pinephone, Bluetooth tethering a laptop or tablet while on the train, hotel, during a power outage, or at coffee is a basic daily driver phone requirement in my opinion.
I am sure the modern kernel has the required modules but I don't know what the interface name for bluetooth network interface for the pinephones bt driver; bnep0 is the interface used on this old N900 script.
I think this is an easy edit to the other network interfaces like USB already in the wiki unless iptables has changed much since the 2010s.

BT PAN tethering is by far the best and easiest way to tether to your phone's internet connection vs WiFi which wastes far more electricity per Mb transmitted for little benefit other than maybe easier sharing a wifi password with friends vs them having to pair with you on BT.  The security is provided by the bluetooth pairing process.

Below is the scripting to get full service, including DHCP, automatic Bluetooth PAN hotspot running on the Nokia N900, how much will work as is?.  

Hello all,

I have bought a Pine Phone Pro and I am stuck from the beginning. 

I updated the delivered manjaro to the latest version and played a bit and I am quite happy. 

No w I was trying to install mobian to one of my SD cards but the only thing I get are read errors from the SD Cards slot as well as I/O Errors.

Okay, I spoke to the developers, go thre remark mayto change to two boots firmware. 

Trying that getting everything ready on two different SD cards, Samsung and San Disk it also Failed to start with the RE button pressed as described. 


Even booting into the working majaro gives me error when I try to write to the SD cards. 



I have no further ideas anymore. Do you have any suggestion ?

I'm late to the party on the PinePhone keyboard's top row (number row) actuation issue, but I found 2 solutions to this problem that are simpler than making tiny washer-shaped spacers.



For anyone who has been living under a rock, here are the symptoms:

When pressing a key on the top row of the PinePhone keyboard, the key stroke does not register at the tactile bump. One has to keep pressing the key beyond the tactile bump for the key to register. That last bit of travel is very squishy, and this is the observation that eventually allowed me to understand the root cause of the issue.


The solutions:

1. Add a tiny strip or 2 of tape on the inner face of the key cap on the hinge side.
   (no need for a shim going all the way around).
   
   With a pair of good scissors and some tweezers, this is a very easy and fast solution. On my keyboard, a single strip of masking tape made a huge difference, and adding a second one seemed to make it feel a little better.
   In my mind, the cons are durability and adhesive compatibility. I imagine the strips eventually shifting around or falling out of place.
   
   
    --- or ---
   
   
2. Remove some material from the hinge-side rim of the keycap.
   
   This solution was the most effective and resolves the root cause of the problem with no compromises.
   
   
   
   
   

1. Adding a shim so the hinge side of the keycap makes that side not travel as far, creating room for the displaced membrane under the rim. It has a slightly squishy feel, but the key actuates reliably at the tactile bump.
   
   
2. Removing the portion of keycap that interferes with the displaced membrane allows the keycap to travel all the way down as intended.
   I say this solution is no compromises because the modification is completely hidden from view, it solves the root cause of the problem, and they key does not feel squishy at all. It feels absolutely great.
   
   (Pictured is the proof of concept test. The final modification removed a bit more material than you see here.)
   

Hi,

i traced my intermittent issues with crashes to inappropriate cooling of the cpu. 

Right now, to tp2 pads and a 2€ct. piece work ok for normal work loads.

What would be the measurements of the original thermal pad? I am planning to replace that with a chip of copper. 

Tia.

Hello 
I received my pinephone pro in February 2022.

I installed postmarket os and it works pretty well, except for one thing:
I can't connect to the internet without wifi. In other words, as soon as I leave my house, I no longer have access to the Internet.
I looked in the settings and there, I checked "Mobile Data" and "Data Roaming".
In the advanced settings > Access Point Names, I chose the one that seems to me to be the one that corresponds to my provider… nothing helps.

Any ideas?

Thanks

I have started the process of getting OpenWRT working on the Rock64.

I have a working image alongside a custom repo for packages which can be found here, download links for the SD Card images are front and centre: https://openwrt.cdnbcn.net/

When installing the SD Card image, you will have to manually configure /etc/opkg/distfeeds.conf with my custom repo, however I'll fix this in a later build.

The main issues currently are as follows:
    - USB3 port isn't working
    - Onboard Ethernet doesn't reset correctly 100% of the time

The source code can be found at https://github.com/CanadianBaconBoi/openwrt/tree/rock64.
It is based on the work of lucize however it has been updated for a modern version of OpenWRT.

There is a thread with some fixes for the aforementioned issues below, however I have been short on time recently and haven't been able to get around to implementing them yet.
https://forum.pine64.org/showthread.php?tid=11012

Any help would be greatly appreciated in pulling these in, I'll continue to host the package repo for free until this is pulled into upstream.

Hello all.

As of about two weeks ago, my SMS messages have stopped coming in on my PPP. MMS messages, including multimedia and plaintext multiperson messages work fine, as do outgoing SMS messages, but incoming messages seem to go into a void. mmcli shows no pending messages, so it is not just the front end GUI application. Has anyone else seen this?

For the record, I am using a PPP loaded with the latest Danctnix/Arch, running Phosh, and am on a Verizon contract.

Thanks for any ideas or insight

-tch

My phone will just go dead for days at a time, and it will not update. I think that my software is corrupted. How can I safely reflash the emmc?