Trying to use the Pinetab2 as my daily tablet, but the pop up keyboard does not contain all the characters i would like such as Home, End, L Tab, R Tab, F5, would be nice to be able to have these basic functions available from the virtual keypad. Anyone know is there some conf file or something that can be edited to add/change keys to the virtual keyboard? I am running the shipped Arch linux.

Thanks for your suggestions.

Hi all. Is anyone using the Pcie connector on the back of the Quartz64b ? I am revisiting this board after some considerable time. Lets say it has been in storage. Anyway I would like to make use of it again. Which brings me to the Pcie part, Is this used with a flat cable? or is a M.2 card able to be plugged directly into this ? I cannot find much information about it. Has anyone seen a compatible hat that may be used with this connector ? Your comments/experience may point me in the right direction to making use of the Quartz64b once again.

My goal is to compile android for a64+ with the usb simcom76xx drivers included, but I can't even get it to compile stock.  I have tried several guides, several ubuntu versions as host os, various things.  and the 8.1 sdk seems to be missing files (such as .dts) at first glance, on top of no compile instructions.  How do?

The last few updates I have seen hu.org.cameractrls show an update.
Are we close to getting working cameras on our Danctnix Pinetab2s?

Hi,

  I was successfully running Armbian on my Pine A64+ board, using the 7" touch screen from 2016, first using the Longsleep kernel, with mainline kernels from 2021.

See https://forum.pine64.org/showthread.php?tid=3482 thread for more details.

Regular Armbian upgrades were fine until around the beginning of this year - Armbian kernel 6.1.104 (02/02/2025).

But a kernel version somewhere beween that and the next currently available Armbian kernel 6.6.750 (03/02/25) has broken the output to the touchscreen.

I haven't been able top source intermediate kernels and device trees, so can't say exactly where the change happened that broke the output.

Rolling back to 6.1.104 fixes the display with no other changes.

I don't see any changes in logging boutput related to mipi-dsi or display and don't have access to a serial connection to view the early boot process, so am stuck.

Does anyone else still use this board with the 7" touchsceen and have they been able to run it with a kernel later than 6.1.x?

I'd be very interested to know what changed and how to fix it without freezing the kernel.

I'm trying to build a U-Boot loader for PineTab2 (don't ask me why, I have no answer to this question).

Just received a gifted Pinebook Pro. Donor said "look in the forums" when I asked for the login & password.
May I please ask what are the default username and password?
TY.

UPDATE: rock/rock
--
73 & best regards de K7AAY CN85oj @503bartley.pdx.social @503bartley.bsky.social

Purchased an Alpha One, took it out of the box, plugged in the Ethernet cord, inserted a blank SD Card, and plugged in the provided power cable. Noticed from the start, only one of the two ethernet port lights were lit, which indicates a faulty port. I created a brand new Cat6 Ethernet cable with shielded RJ45s, and tested it, to make sure the cable was not the issue. I then checked to see if the alpha one had acquired an IP Address, it indicated it did, but attempts to connect failed due to timing out. So then an ARP scan was performed to see if the board would respond to ARP, but it did not. I performed a ping test for redundancy, which timed out, then the Alpha One disappeared entirely from the network.

Repeated attempts to try to configure the network proved unsuccessful, until the decision to reflash the entire board with the official image was reached. This was performed to the letter as instructed by RockOS, here[url=https://docs.rockos.dev/en/docs/installation/][/url]. The result of which was fewer errors generated in syslog, but overall no change. Neither could the board obtain connectivity, nor could anything connect to it. 

Current efforts are invested towards discovering whether the EMMC is defective, before moving on to other parts of the board itself. In my sixteen years of experience, I have yet to encounter a system I have been unable to get up and running, I do not plan for the AlphaOne to be the first, but there is little I can do when it appears the hardware itself arrives broken.

Why has a section for StarPro64 not been created yet? 
Why is there no "Catch all for problems" thread either?  

Hi,
I'm writing a custom pyqt6 app on my pinephone but I cannot access the camera.
In dmesg, I see

Quote:ov5640 0-004C: ov5640_write_reg: error: reg=3008, val=42