<![CDATA[PINE64 - Pinebook Pro Hardware and Accessories]]>

<![CDATA[PINE64 - Pinebook Pro Hardware and Accessories]]> https://forum.pine64.org/ Sat, 09 May 2026 19:46:11 +0000 MyBB <![CDATA[Fitting new case]]> https://forum.pine64.org/showthread.php?tid=20186 Fri, 06 Feb 2026 13:09:20 +0000 RicTor]]> https://forum.pine64.org/showthread.php?tid=20186
Now to do a transplant. Has anyone else done this - are there any instructions? The order in which to do this is not obvious - hidden screws etc.

Yes I've read (most of) the page https://pine64.org/documentation/Pineboo...eassembly/
and seen the advice there about stiff hinges...

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main bo

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).

stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).]]>
Now to do a transplant. Has anyone else done this - are there any instructions? The order in which to do this is not obvious - hidden screws etc.

Yes I've read (most of) the page https://pine64.org/documentation/Pineboo...eassembly/
and seen the advice there about stiff hinges...

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main bo

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).

stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).

Many units come with the hinges too stiff from the factory. You can tell if it affects your device by carefully observing if operating the lid on a fully assembled notebook flexes the case. This repeated flexing can lead to plastic and metal fatigue and eventually broken parts. Consider carefully using a flat screwdriver or similar object to unbend the hinges a bit by wedging it into the slot (requires the display part to be fully detached from the main body).]]> <![CDATA[Any recommended brands/models?]]> https://forum.pine64.org/showthread.php?tid=19812 Wed, 23 Apr 2025 03:10:59 +0000 Kinces]]> https://forum.pine64.org/showthread.php?tid=19812 <![CDATA[pinebook pro dixplays vertical stripes]]> https://forum.pine64.org/showthread.php?tid=19748 Sun, 23 Mar 2025 01:47:48 +0000 WEF]]> https://forum.pine64.org/showthread.php?tid=19748 Now when i power it on, green light on the keyboard comes on for maybe 10 seconds then goes out, the screen remains black. Anyone dealt with this? I hate to take it apart to blindly start seating cables or whatever since i understand this thing is easy to break and i am somewhat of a klutz. But i would like to get it working again, any suggestion is appreciated.]]> Now when i power it on, green light on the keyboard comes on for maybe 10 seconds then goes out, the screen remains black. Anyone dealt with this? I hate to take it apart to blindly start seating cables or whatever since i understand this thing is easy to break and i am somewhat of a klutz. But i would like to get it working again, any suggestion is appreciated.]]> <![CDATA[best way to get a stuck sd card out?]]> https://forum.pine64.org/showthread.php?tid=19737 Thu, 13 Mar 2025 20:41:36 +0000 elix]]> https://forum.pine64.org/showthread.php?tid=19737 the micro sd card is now stuck and i wanna switch distros.
i tried the old knife method, etc. but ended up screwing up the outer part of the card.
is my next bet to the case off and get it out that way?
not sure its even safe to use the card at this point.

thanks]]> the micro sd card is now stuck and i wanna switch distros.
i tried the old knife method, etc. but ended up screwing up the outer part of the card.
is my next bet to the case off and get it out that way?
not sure its even safe to use the card at this point.

thanks]]> <![CDATA[I'm going to be waist-deep in keyboards]]> https://forum.pine64.org/showthread.php?tid=19668 Wed, 05 Feb 2025 02:14:16 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=19668
So a month or two ago, I replaced the palm case. Today I found out this one is broken already. The hinges don't seem tighter than any of the other PBPs I have.
But I guess I'll loosen the hinges and replace the palm case again.]]>
So a month or two ago, I replaced the palm case. Today I found out this one is broken already. The hinges don't seem tighter than any of the other PBPs I have.
But I guess I'll loosen the hinges and replace the palm case again.]]> <![CDATA[compra]]> https://forum.pine64.org/showthread.php?tid=19628 Fri, 17 Jan 2025 02:17:12 +0000 eules]]> https://forum.pine64.org/showthread.php?tid=19628 <![CDATA[Hardkernel 256GB eMMC with lvm2 on PBP]]> https://forum.pine64.org/showthread.php?tid=19572 Wed, 18 Dec 2024 04:39:57 +0000 Dendrocalamus64]]> https://forum.pine64.org/showthread.php?tid=19572
The Hardkernel 256GB emmc has some sort of an orange bump on the bottom, opposite the socket, that the Pine64 64GB emmc which it replaced did not.

There was a sticky pad on the PBP mainboard underneath the emmc to help keep it in place while it's being bumped around; I had to scrape it off with a spudger to get the 256 installed. The new emmc still doesn't sit quite level, it angles up slightly due to the bump; I hope it isn't going to come loose.

Using the Pine-branded emmc-to-USB adapter which I got from the Pine store several years ago, the 256 GB emmc consistently gave read errors whenever it was being accessed raw, which greatly slowed down operations like mounting & partitioning. It's not doing that in the emmc slot, and the 64 isn't doing that on the adapter. For example, this sort of command would trigger a read error if it wasn't read from cache, but reading from a filesystem would not:
$ sudo dd if=/dev/sda count=20480 | md5sum
The errors were recoverable and only showed up in dmesg & syslog, but made it slow.

I wanted to partition the new storage myself and rsync over my files, instead of reinstalling. Things I learned in the process:
- gpt's partition table & backup partition table occupy the first 64 and last 64 sectors of the main address space of the medium; thats why the skip=64 when writing bootloaders.
- The emmc boot partitions (mmcblk2boot0 and mmcblk2boot1) are NOT being used. The convention is to leave the first 30 MiB in the main address space unallocated so there's space for bootloaders and start the first partition at 62500 sectors; with alignment to 2048 sectors as parted recommends, the first partition starts at 32*2048 = 65536 sectors.
- Stock uboot can only boot from FAT filesystems. Using ext4 for your /boot partition makes the medium unbootable. I only tested that FAT16 works.
- If you want the root partition on lvm, as I did, you need to rebuild the initramfs with the lvm2 hook included (instructions) and specify the root fs as e.g. root=/dev/VG1/LV1. u-boot doesn't understand lvm by itself; the tools in the initramfs are needed to mount it.
- Boot order is supposed to be USB > SD > eMMC but with the particular boot loader versions I was using, the USB wouldn't boot at all without the internal emmc disabled. Failure to boot off the USB adapter doesn't necessarily mean it won't boot when slotted.
- The last revision of tow-boot before the maintainer bailed doesn't work on my PBP so it's u-boot only.

In principle, lvm should be a great fit for an all-solid state system like the PBP. Logically contiguous blocks on the medium aren't physically contiguous, so a partition table designed for rotating disks that forces you to keep partitions completely contiguous rather than just reasonably unfragmented, as allocation in extents is intended to do, doesn't make sense.

But what about in practice? I had a hard time finding any performance numbers for lvm other than "works for me", some synthetic benchmarks, and an ancient study using lvm1 which found that performance with small files was terrible.

Life on arm means compiling a lot. I don't want it to slow down big builds.

I've been benchmarking by building haveno's git repository, which is a convenient size. It goes from 260M to 5.1G over the course of a build, and takes about 7-10 minutes to do it. 98% Java code, build managed with Gradle.

Testing `make skip-tests` starting with all dependencies resolved & cached on disk, a gradle daemon running, parallel builds enabled & build caching off, and the linux disk cache freshly flushed, it took about 7m 20s to build on the old emmc without lvm, and 7m 3s on the new emmc with lvm2. Still to test is building on the new emmc in the non-lvm partition I left for comparison, and building from heavily fragmented logical volumes.]]>
The Hardkernel 256GB emmc has some sort of an orange bump on the bottom, opposite the socket, that the Pine64 64GB emmc which it replaced did not.

There was a sticky pad on the PBP mainboard underneath the emmc to help keep it in place while it's being bumped around; I had to scrape it off with a spudger to get the 256 installed. The new emmc still doesn't sit quite level, it angles up slightly due to the bump; I hope it isn't going to come loose.

Using the Pine-branded emmc-to-USB adapter which I got from the Pine store several years ago, the 256 GB emmc consistently gave read errors whenever it was being accessed raw, which greatly slowed down operations like mounting & partitioning. It's not doing that in the emmc slot, and the 64 isn't doing that on the adapter. For example, this sort of command would trigger a read error if it wasn't read from cache, but reading from a filesystem would not:
$ sudo dd if=/dev/sda count=20480 | md5sum
The errors were recoverable and only showed up in dmesg & syslog, but made it slow.

I wanted to partition the new storage myself and rsync over my files, instead of reinstalling. Things I learned in the process:
- gpt's partition table & backup partition table occupy the first 64 and last 64 sectors of the main address space of the medium; thats why the skip=64 when writing bootloaders.
- The emmc boot partitions (mmcblk2boot0 and mmcblk2boot1) are NOT being used. The convention is to leave the first 30 MiB in the main address space unallocated so there's space for bootloaders and start the first partition at 62500 sectors; with alignment to 2048 sectors as parted recommends, the first partition starts at 32*2048 = 65536 sectors.
- Stock uboot can only boot from FAT filesystems. Using ext4 for your /boot partition makes the medium unbootable. I only tested that FAT16 works.
- If you want the root partition on lvm, as I did, you need to rebuild the initramfs with the lvm2 hook included (instructions) and specify the root fs as e.g. root=/dev/VG1/LV1. u-boot doesn't understand lvm by itself; the tools in the initramfs are needed to mount it.
- Boot order is supposed to be USB > SD > eMMC but with the particular boot loader versions I was using, the USB wouldn't boot at all without the internal emmc disabled. Failure to boot off the USB adapter doesn't necessarily mean it won't boot when slotted.
- The last revision of tow-boot before the maintainer bailed doesn't work on my PBP so it's u-boot only.

In principle, lvm should be a great fit for an all-solid state system like the PBP. Logically contiguous blocks on the medium aren't physically contiguous, so a partition table designed for rotating disks that forces you to keep partitions completely contiguous rather than just reasonably unfragmented, as allocation in extents is intended to do, doesn't make sense.

But what about in practice? I had a hard time finding any performance numbers for lvm other than "works for me", some synthetic benchmarks, and an ancient study using lvm1 which found that performance with small files was terrible.

Life on arm means compiling a lot. I don't want it to slow down big builds.

I've been benchmarking by building haveno's git repository, which is a convenient size. It goes from 260M to 5.1G over the course of a build, and takes about 7-10 minutes to do it. 98% Java code, build managed with Gradle.

Testing `make skip-tests` starting with all dependencies resolved & cached on disk, a gradle daemon running, parallel builds enabled & build caching off, and the linux disk cache freshly flushed, it took about 7m 20s to build on the old emmc without lvm, and 7m 3s on the new emmc with lvm2. Still to test is building on the new emmc in the non-lvm partition I left for comparison, and building from heavily fragmented logical volumes.]]> <![CDATA[NVMe]]> https://forum.pine64.org/showthread.php?tid=19520 Mon, 18 Nov 2024 15:00:23 +0000 reukiodo]]> https://forum.pine64.org/showthread.php?tid=19520 NVMe compatibility matrix and TechPowerup's SSD database has much more info, I am still finding it difficult to find an optimal low-power large (2TB+) SSD.

From what I can determine so far from the SSD database, there are really 2 choices for low-power:

Only the Kingston is listed in the compatibility matrix, with comments are large battery drain. The compatibility matrix shows many other SSD options using less power, such as WD SN520 and Kioxia BG4.

Does the Power State X actually correlate to battery drain? And can it be forced to always disable all the high-powered states?

Something like SK Hynix Gold P31 2TB shows 6.3W (PS0) in the compatibility matrix, but only 3.3W max in the SSD database.
https://www.techpowerup.com/ssd-specs/sk...-2-tb.d443

Which one is accurate? Or are they both accurate and there are old versions which use more power?]]> NVMe compatibility matrix and TechPowerup's SSD database has much more info, I am still finding it difficult to find an optimal low-power large (2TB+) SSD.

From what I can determine so far from the SSD database, there are really 2 choices for low-power:

Only the Kingston is listed in the compatibility matrix, with comments are large battery drain. The compatibility matrix shows many other SSD options using less power, such as WD SN520 and Kioxia BG4.

Does the Power State X actually correlate to battery drain? And can it be forced to always disable all the high-powered states?

Something like SK Hynix Gold P31 2TB shows 6.3W (PS0) in the compatibility matrix, but only 3.3W max in the SSD database.
https://www.techpowerup.com/ssd-specs/sk...-2-tb.d443

Which one is accurate? Or are they both accurate and there are old versions which use more power?]]> <![CDATA[Replacement touch pads]]> https://forum.pine64.org/showthread.php?tid=19510 Fri, 15 Nov 2024 04:05:52 +0000 Sb2024]]> https://forum.pine64.org/showthread.php?tid=19510 <![CDATA[PinebookPro Bottom Case]]> https://forum.pine64.org/showthread.php?tid=19501 Sat, 09 Nov 2024 16:42:12 +0000 KC9UDX]]> https://forum.pine64.org/showthread.php?tid=19501
I have two Pinebooks Pro on which the left hinge has broken free. I assume that the Bottom Case is all I'll need to fix these. Or is it just the magnesium cover? (I don't need that)
Maybe the palm case is what I need. Is it possible to get two? I see there is a limit of one.]]>
I have two Pinebooks Pro on which the left hinge has broken free. I assume that the Bottom Case is all I'll need to fix these. Or is it just the magnesium cover? (I don't need that)
Maybe the palm case is what I need. Is it possible to get two? I see there is a limit of one.]]> <![CDATA["PowerButton pressed" randomly]]> https://forum.pine64.org/showthread.php?tid=19458 Sat, 12 Oct 2024 15:47:03 +0000 CosmicRay]]> https://forum.pine64.org/showthread.php?tid=19458 Been a quiet PBP user since july 2021, really love my pinebook and enjoy it (using manjaro).

Lately I have an issue with the power button.

Symptoms:
It seemed that it won't boot properly, despite no recent OS/FW updates and topped-up battery.
It would boot into a certain state where the LCD is lit up and a flashing '_' is flashing at top left corner, as expected.
Then, the flashing is halted, then continues until shutdown. The PBP reboots, ad infinitum.
From time to time it did load GUI to show the mouse pointer before resetting, rarely loading the login screen.
Another thing is that shutting down resulted in reboot. Long press on power button did shut it down for good though.
Lately otherwise it ususally make it into login without turning off.

Making a long story short, in the rare cases I managed to log in I got constant power-off dialogs popping at me.
That's a typical journal log I get on the machine (reverse order):

Code:
Oct 12 18:08:27 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:44 PinebookPro root[4904]: PowerButton pressed

Oct 12 18:07:44 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:28 PinebookPro root[4902]: PowerButton pressed

Oct 12 18:07:28 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:17 PinebookPro root[4897]: PowerButton pressed

Oct 12 18:07:17 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:06:44 PinebookPro root[4892]: PowerButton pressed

Oct 12 18:06:44 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:05:58 PinebookPro root[4879]: PowerButton pressed

Oct 12 18:05:58 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:05:26 PinebookPro root[4876]: PowerButton pressed

Oct 12 18:05:26 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:04:36 PinebookPro root[4873]: PowerButton pressed

Oct 12 18:04:36 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:03:28 PinebookPro root[4862]: PowerButton pressed

Oct 12 18:03:28 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:03:10 PinebookPro root[4859]: PowerButton pressed

Oct 12 18:03:10 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:56 PinebookPro root[4857]: PowerButton pressed

Oct 12 18:02:56 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:31 PinebookPro root[4855]: PowerButton pressed

Oct 12 18:02:31 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:07 PinebookPro root[4851]: PowerButton pressed

Oct 12 18:02:06 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:01:35 PinebookPro root[4844]: PowerButton pressed

Oct 12 18:01:35 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:00:57 PinebookPro root[4831]: PowerButton pressed

Oct 12 18:00:57 PinebookPro systemd-logind[520]: Power key pressed short.

Well you get the idea. That's really annoying.
I could probably remap the power button? But I do fear that the underlying condition will kill the power button altogether one day, and I wont be able to properly power the device on.

I took a look at the schematics. I guess that something is pulling the CPU power line, but not the PMIC one? Or is the PMIC less sensitive to that signal?
If it's the first issue that it's not a keyboard issue, and I have no clue what issue it is.
I might be able to sense the proper test points later, but I'd rather ask here first if anyone had such an issue or have any insight into this issue (I couldn't find such thing in the forum or elsewhere).

Kudos]]> Been a quiet PBP user since july 2021, really love my pinebook and enjoy it (using manjaro).

Lately I have an issue with the power button.

Symptoms:
It seemed that it won't boot properly, despite no recent OS/FW updates and topped-up battery.
It would boot into a certain state where the LCD is lit up and a flashing '_' is flashing at top left corner, as expected.
Then, the flashing is halted, then continues until shutdown. The PBP reboots, ad infinitum.
From time to time it did load GUI to show the mouse pointer before resetting, rarely loading the login screen.
Another thing is that shutting down resulted in reboot. Long press on power button did shut it down for good though.
Lately otherwise it ususally make it into login without turning off.

Making a long story short, in the rare cases I managed to log in I got constant power-off dialogs popping at me.
That's a typical journal log I get on the machine (reverse order):

Code:
Oct 12 18:08:27 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:44 PinebookPro root[4904]: PowerButton pressed

Oct 12 18:07:44 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:28 PinebookPro root[4902]: PowerButton pressed

Oct 12 18:07:28 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:07:17 PinebookPro root[4897]: PowerButton pressed

Oct 12 18:07:17 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:06:44 PinebookPro root[4892]: PowerButton pressed

Oct 12 18:06:44 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:05:58 PinebookPro root[4879]: PowerButton pressed

Oct 12 18:05:58 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:05:26 PinebookPro root[4876]: PowerButton pressed

Oct 12 18:05:26 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:04:36 PinebookPro root[4873]: PowerButton pressed

Oct 12 18:04:36 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:03:28 PinebookPro root[4862]: PowerButton pressed

Oct 12 18:03:28 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:03:10 PinebookPro root[4859]: PowerButton pressed

Oct 12 18:03:10 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:56 PinebookPro root[4857]: PowerButton pressed

Oct 12 18:02:56 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:31 PinebookPro root[4855]: PowerButton pressed

Oct 12 18:02:31 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:02:07 PinebookPro root[4851]: PowerButton pressed

Oct 12 18:02:06 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:01:35 PinebookPro root[4844]: PowerButton pressed

Oct 12 18:01:35 PinebookPro systemd-logind[520]: Power key pressed short.

Oct 12 18:00:57 PinebookPro root[4831]: PowerButton pressed

Oct 12 18:00:57 PinebookPro systemd-logind[520]: Power key pressed short.

Well you get the idea. That's really annoying.
I could probably remap the power button? But I do fear that the underlying condition will kill the power button altogether one day, and I wont be able to properly power the device on.

I took a look at the schematics. I guess that something is pulling the CPU power line, but not the PMIC one? Or is the PMIC less sensitive to that signal?
If it's the first issue that it's not a keyboard issue, and I have no clue what issue it is.
I might be able to sense the proper test points later, but I'd rather ask here first if anyone had such an issue or have any insight into this issue (I couldn't find such thing in the forum or elsewhere).

Kudos]]> <![CDATA[Keyswitch scissors replacement]]> https://forum.pine64.org/showthread.php?tid=19453 Tue, 08 Oct 2024 08:01:26 +0000 cmj]]> https://forum.pine64.org/showthread.php?tid=19453
The little scissors assembly thing has broken on two of the keys on my PBPro keyboard (ISO / UK version)

One normal-sized one and the backspace key. It feels like the sort of thing that could be replaced, if I can source the assembly. I think in both cases it's the lugs that hold the switch into the keyboard side that have snapped off (so the scissors attaches to the key, just not the keyboard).

Does anyone know if it's possible to obtain them without buying a new keyboard? (the Pine64 store does sell US versions but not the ISO ones).

Thanks!

Chris]]>
The little scissors assembly thing has broken on two of the keys on my PBPro keyboard (ISO / UK version)

One normal-sized one and the backspace key. It feels like the sort of thing that could be replaced, if I can source the assembly. I think in both cases it's the lugs that hold the switch into the keyboard side that have snapped off (so the scissors attaches to the key, just not the keyboard).

Does anyone know if it's possible to obtain them without buying a new keyboard? (the Pine64 store does sell US versions but not the ISO ones).

Thanks!

Chris]]> <![CDATA[Yet another new Pinebook keyboard problem]]> https://forum.pine64.org/showthread.php?tid=19415 Mon, 09 Sep 2024 14:19:36 +0000 MikoBob]]> https://forum.pine64.org/showthread.php?tid=19415
This seems to be a huuuge problem.]]>
This seems to be a huuuge problem.]]> <![CDATA[New Hardware]]> https://forum.pine64.org/showthread.php?tid=19187 Sat, 20 Apr 2024 17:01:44 +0000 names_mark_]]> https://forum.pine64.org/showthread.php?tid=19187
I've been considering getting myself a Pinebook Pro, but I check again every year or so and the hardware hasn't been updated it seems. Are there any plans for 8GB RAM or a newer ARM CPU?

Cheers!]]>
I've been considering getting myself a Pinebook Pro, but I check again every year or so and the hardware hasn't been updated it seems. Are there any plans for 8GB RAM or a newer ARM CPU?

Cheers!]]> <![CDATA[Lithium Battery Connector]]> https://forum.pine64.org/showthread.php?tid=19166 Tue, 02 Apr 2024 07:52:14 +0000 Franestra]]> https://forum.pine64.org/showthread.php?tid=19166
I need to know the 7-pin connector that is used to connect the battery pack to the mainboard on the Pinebook Pro... according to the schematic the boardside connector is JSQ1201WR-7P, however I could not find any more information to this on the internet. What I really am looking for is the cable side connector name, and if I could order it somewhere... I have seen a few posts on this forum asking something similar, but no answer this far...
There are also 2 types of connector, one from an older version and a newer one, as far as I can tell? Does anyone have any information?

Thanks!]]>
I need to know the 7-pin connector that is used to connect the battery pack to the mainboard on the Pinebook Pro... according to the schematic the boardside connector is JSQ1201WR-7P, however I could not find any more information to this on the internet. What I really am looking for is the cable side connector name, and if I could order it somewhere... I have seen a few posts on this forum asking something similar, but no answer this far...
There are also 2 types of connector, one from an older version and a newer one, as far as I can tell? Does anyone have any information?

Thanks!]]>