https://forum.pine64.org/ Fri, 14 Aug 2026 09:50:34 +0000 MyBB https://forum.pine64.org/showthread.php?tid=20344 Wed, 05 Aug 2026 01:29:46 +0000 arw]]> https://forum.pine64.org/showthread.php?tid=20344
PBP is scratched on the bottom but otherwise fine. PineTab-V and PineNote are in flawless condition.]]>
PBP is scratched on the bottom but otherwise fine. PineTab-V and PineNote are in flawless condition.]]> https://forum.pine64.org/showthread.php?tid=20340 Mon, 03 Aug 2026 13:45:59 +0000 waitingpio]]> https://forum.pine64.org/showthread.php?tid=20340 PineBuds Pro: Teardown and Battery Replacement

#repair #battery #electronics #Piner



My PineBuds Pro were new old stock. Never used, just sat in a box. When I finally charged them they ran about an hour at low volume with ANC off, which is well under spec.



These buds are repairable and the cells are cheap. The problem is that there's almost no teardown information for them anywhere online, so I wrote this up.



One thing to know before you start: if the buds are old, the cell inside has probably swollen. Mine had. Better to find that out now than halfway through prying the shell apart.



Disclaimer



This is a record of a repair I did on my own PineBuds Pro. I have an electronics background and years of hands-on soldering experience, and this write-up assumes a similar level of skill. It isn't a beginner guide, and it isn't a recommendation that anyone else attempt it.



Lithium cells can vent, catch fire, or explode if punctured, crushed, shorted, or overheated. Opening the buds is irreversible and voids any warranty.



If you try this, you do so entirely at your own risk. I accept no responsibility for any damage, injury, or loss that results.



⚠️ Lithium cells can catch fire if punctured or shorted. Don't pry near the cell, don't let metal touch both terminals, and stop if it gets hot. At your own risk.



Step 1: Open the earbud





[pic: squeezing the earbud shell]



There are no screws. The shell is held by internal clips with a little adhesive. The way in is to flex it.



The plastic is soft and has some give. Squeezing the shell deforms it just enough to strain the joint from inside, and the clips release and the glue tears before the plastic takes any damage.



Squeeze firmly near the seam and hold. The seam starts to separate, and you may even see the LED indicator through the gap. Keep the pressure on, work a plastic pry tool into the opening, then run it around the edge to release the remaining clips.



Squeeze in short bursts rather than one long press. Repeated flexing works the clips loose bit by bit, and you get much better control than with steady heavy force.



Step 2: A note on debris and tools



You'll see crumbs or dust as the shell opens. That's the old adhesive breaking up, not the plastic cracking. Nothing to worry about.



Use a plastic pry tool or spudger. Never a metal blade or screwdriver. The shell plastic is good quality and flexes well, but it's soft enough that metal will gouge it.



Use a wide tool too, not a pointed one. A narrow tip puts all the force on one spot, which dents the plastic and can crack the clip underneath. A broad edge spreads that force along the seam so the shell flexes as a whole. A guitar pick works well. Avoid anything sharp.



Step 3: Inside the earbud





[pic: shell apart, PCB visible, small black rubber cover loose in the shell]



With the shell apart you can see the PCB. It isn't screwed down. It's held by heat-staked plastic posts, where moulded pins have been pushed through the board and their tips melted flat.



How the touch controls work. The inside of the outer cover is lined with aluminium foil. Once assembled, that foil rests against two pogo pins on the PCB, and those pins run to the capacitive sensing pin on the chip. When you touch the outside of the shell (the side facing away from your ear), the capacitance changes and the chip reads it through those pins. That's the whole touch input path for volume, ANC and everything else.



The other four contacts sit on the opposite face, the side against your ear, next to the speaker. Those are the charging and flashing contacts, covered in Step 4.



Don't lose the mic gasket. There's a small black rubber cover sitting in the shell. It belongs over the microphone on the PCB, it isn't attached to anything, and it falls out very easily. Put it somewhere safe as soon as you see it.



Step 4: Remove the PCB





[pic: PCB removed, showing main chip, battery and wiring]



Cut or shave off the melted heads of the plastic posts, then lift the board out. The battery is underneath, hidden by the PCB.



The main chip is a BES2300 (Bestechnic), running from an external 26.000 MHz crystal. A solid, well-supported part.



Six very fine heat-resistant wires run under the board:

• 2 to the battery, B+ and B−
  
• 4 to the external contact pads: V+ and V− for charging, TX and RX for firmware flashing
  

An FPC ribbon cable connects to the speaker.



Step 5: The battery





[pic: battery lifted out]





[pic: peeling back the foam tape to reveal the label]



The battery lifts out once the PCB is clear. It's wrapped in single-sided vibration-damping foam tape. Peel this back to find the label.



Cell: YD 501012, 40 mAh

Measured: 12.8 × 9.6 × 5.5 mm



The part number is the nominal cell size. 501012 means 5.0 mm thick, 10 mm, 12 mm. That's a useful starting point for searching, but it only describes the bare cell. The protection board and the wire joint add to the real dimensions, and different sellers measure differently — some quote the cell alone, some quote the whole assembly. Check the actual measurements in the listing, and where the protection board sits, before you order.



Note the measured thickness is 5.5 mm against a nominal 5.0 mm. You can see in the photo in step 6 that this cell has already swollen a little. That's normal after years in storage and it's almost certainly why the runtime was so bad.



There's no spare room in the shell, so a physically larger cell won't go in. Match these dimensions when you source a replacement.



⚠️ A swollen cell needs care. Don't press it, bend it or puncture it. Lift it out flat, keep it away from anything flammable, and take it to a battery recycling point soon rather than leaving it on the bench.



Step 6: Fitting the new battery





[pic: disconnecting one lead at a time, new cell ready]



Disconnect one lead at a time, and insulate each one as soon as it's free. If you cut both leads together with metal cutters you short the cell, because the tool bridges the terminals.



I cut the positive lead first, kept it away from anything metal, taped the end, and only then did the negative.



Choosing a replacement



The cell I used came from a source I trust. It has a protection board built in and a recent manufacturing date. Both of those matter more than the brand name. A cheap unprotected cell sealed inside an earbud isn't worth the risk.



The best match I could find was a 301012, 30 mAh:



Original  vs.  Replacement

Part: YD 501012 vs. 301012

Capacity: 40 mAh vs. 30 mAh



Nominal size: 5.0 × 10 × 12 mm vs. 3.0 × 10 × 12 mm



Same footprint, 2 mm thinner, 25% less capacity. Less runtime than a factory-fresh bud, but still better than a swollen cell.



The thinner cell leaves about 2 mm of slack in the pocket. I wrapped it with high-temperature-resistant tape until it was a snug fit, which stops it moving around and also insulates it against any short.



Step 7: Soldering





[pic: new battery soldered to the back side of the PCB]



This is the part that needs real soldering skill. The bud and its PCB are small and won't stay put on their own, so I'd strongly suggest a soldering fixture or helping hands. In practice it isn't really optional.



The glue is the main obstacle. The wires and PCB are held with adhesive, which works well against vibration, but under the iron it softens, flows, and covers the pad you're working on. There are also several connectors and wires close by, so there's very little clean space.



What I did instead: I removed the old battery wires from the front of the PCB and soldered the new ones to the back. The joints are through-hole, so the same pads are reachable from behind, and that side is clean and open with no risk of bridging to a neighbouring connector.



Test before you close up. Once the battery is connected the LED should light. The bud doesn't power on by itself, though. The pogo pins go straight to the chip's capacitive sensing pin, so it's your hand on the pins that triggers it. Either way, the LED tells you the joints are good. Check now, not after reassembly.



One thing Pine64 got right: the original wire is ultra-fine, heat-resistant and break-resistant, noticeably better than what came with my replacement cell. Ordinary insulation shrinks back or melts if the iron sits on it a moment too long.



Which gives an option worth considering. You could keep the original wire. Cut the old cell's leads a few millimetres from the battery, cut the new cell's leads short, and splice the two with heat-shrink. The PCB joints never get touched, and the delicate work happens in open air with no glue nearby.



Step 8: Reassembly





[pic: glue applied over the battery terminals]



Before closing anything, check that the battery is seated properly, the wires are clear of any pinch points, and there's nothing that could short.



I put glue over the battery terminals to protect them, and used it to hold the PCB down since the heat-staked posts were cut off in Step 4.



Then, in order:

    1. Seat the rubber gasket back onto the microphone. Easy to forget, and a missing gasket means a muffled mic.

    2. Check the aluminium foil inside the cover is intact and will sit flat against the pogo pins.

    3. Apply glue around the inner edge of the shell.

    4. Press the cover back on.



The glue is optional. The internal clips hold the shell closed on their own, so skip it if you'd rather keep the bud easy to open again. When the cover seats properly you'll hear a clear click, and that means it's home.



! Keep glue away from the pogo pins, the aluminium foil, and the clear plastic LED light guide inside the cover. Adhesive on the pins or foil insulates the contact and kills the touch controls. Glue on the light guide clouds it and dims the LED.



Step 9: Clamping and curing





[pic: earbud clamped shut with a clip]



Clamp the bud shut with a folded paper towel between the clip and the shell, so the pressure is spread out and the plastic doesn't mark. Leave it clamped while the adhesive cures.



I used T7000, the black cellphone repair glue for resealing phone housings after a screen replacement.



Set time 3–6 minutes

Full cure 24–48 hours

Temperature range −35 °C to +90 °C



It's sold as waterproof, flexible, vibration-damping and low-odour once cured.



Don't rush the cure. It's tempting to test after a few minutes, but the bond won't reach full strength for a day or two, and this is the joint holding a lithium cell inside a sealed shell.



Two tips for using it on earbuds. Use it sparingly, because squeeze-out inside the shell is very hard to clean up. And let the buds air out before wearing them, since the solvent smell takes a while to leave a small enclosed space that sits in your ear.



Results







[pic: PineBuds with new battery, working]


Tested at low volume with ANC off, playing continuously until the earbud announced shutdown.

The original cell managed about 1 hour before I started.

First full charge after the repair: 2 hours 11 minutes
Second full charge: 2 hours 48 minutes

The jump between the two surprised me. A new cell usually needs a few charge cycles before it settles at its real capacity, so I'd expect the third and fourth runs to land somewhere near the second. Worth knowing if you do this yourself: don't judge the result from the first charge alone.

ANC still works, along with the touch controls and the microphone. This one matters, because Pine64's own store page warns that dismantling the buds can affect performance and ANC especially. It survived on my pair.

Going from 40 mAh to 30 mAh does cost some capacity on paper. But the runtime nearly tripled, which tells you how far gone the original cell was, and the swollen one is out of the earbud, which I wanted to do anyway.


A few notes



These are nice to work on.

The shell opens without breaking anything, the wire quality is good, and the board is tidy inside.

Better than I expected, honestly.



small things that would make life easier for the next person:



The heat-staked posts are the only step you can't undo. Everything else comes apart and goes back together fine.

A clip or a single small screw would make these properly repairable

as long as whatever replaces the staking still lets the shell give a little, so a swelling cell can push the case open rather than building pressure inside it.]]> PineBuds Pro: Teardown and Battery Replacement

#repair #battery #electronics #Piner



My PineBuds Pro were new old stock. Never used, just sat in a box. When I finally charged them they ran about an hour at low volume with ANC off, which is well under spec.



These buds are repairable and the cells are cheap. The problem is that there's almost no teardown information for them anywhere online, so I wrote this up.



One thing to know before you start: if the buds are old, the cell inside has probably swollen. Mine had. Better to find that out now than halfway through prying the shell apart.



Disclaimer



This is a record of a repair I did on my own PineBuds Pro. I have an electronics background and years of hands-on soldering experience, and this write-up assumes a similar level of skill. It isn't a beginner guide, and it isn't a recommendation that anyone else attempt it.



Lithium cells can vent, catch fire, or explode if punctured, crushed, shorted, or overheated. Opening the buds is irreversible and voids any warranty.



If you try this, you do so entirely at your own risk. I accept no responsibility for any damage, injury, or loss that results.



⚠️ Lithium cells can catch fire if punctured or shorted. Don't pry near the cell, don't let metal touch both terminals, and stop if it gets hot. At your own risk.



Step 1: Open the earbud





[pic: squeezing the earbud shell]



There are no screws. The shell is held by internal clips with a little adhesive. The way in is to flex it.



The plastic is soft and has some give. Squeezing the shell deforms it just enough to strain the joint from inside, and the clips release and the glue tears before the plastic takes any damage.



Squeeze firmly near the seam and hold. The seam starts to separate, and you may even see the LED indicator through the gap. Keep the pressure on, work a plastic pry tool into the opening, then run it around the edge to release the remaining clips.



Squeeze in short bursts rather than one long press. Repeated flexing works the clips loose bit by bit, and you get much better control than with steady heavy force.



Step 2: A note on debris and tools



You'll see crumbs or dust as the shell opens. That's the old adhesive breaking up, not the plastic cracking. Nothing to worry about.



Use a plastic pry tool or spudger. Never a metal blade or screwdriver. The shell plastic is good quality and flexes well, but it's soft enough that metal will gouge it.



Use a wide tool too, not a pointed one. A narrow tip puts all the force on one spot, which dents the plastic and can crack the clip underneath. A broad edge spreads that force along the seam so the shell flexes as a whole. A guitar pick works well. Avoid anything sharp.



Step 3: Inside the earbud





[pic: shell apart, PCB visible, small black rubber cover loose in the shell]



With the shell apart you can see the PCB. It isn't screwed down. It's held by heat-staked plastic posts, where moulded pins have been pushed through the board and their tips melted flat.



How the touch controls work. The inside of the outer cover is lined with aluminium foil. Once assembled, that foil rests against two pogo pins on the PCB, and those pins run to the capacitive sensing pin on the chip. When you touch the outside of the shell (the side facing away from your ear), the capacitance changes and the chip reads it through those pins. That's the whole touch input path for volume, ANC and everything else.



The other four contacts sit on the opposite face, the side against your ear, next to the speaker. Those are the charging and flashing contacts, covered in Step 4.



Don't lose the mic gasket. There's a small black rubber cover sitting in the shell. It belongs over the microphone on the PCB, it isn't attached to anything, and it falls out very easily. Put it somewhere safe as soon as you see it.



Step 4: Remove the PCB





[pic: PCB removed, showing main chip, battery and wiring]



Cut or shave off the melted heads of the plastic posts, then lift the board out. The battery is underneath, hidden by the PCB.



The main chip is a BES2300 (Bestechnic), running from an external 26.000 MHz crystal. A solid, well-supported part.



Six very fine heat-resistant wires run under the board:

• 2 to the battery, B+ and B−
  
• 4 to the external contact pads: V+ and V− for charging, TX and RX for firmware flashing
  

An FPC ribbon cable connects to the speaker.



Step 5: The battery





[pic: battery lifted out]





[pic: peeling back the foam tape to reveal the label]



The battery lifts out once the PCB is clear. It's wrapped in single-sided vibration-damping foam tape. Peel this back to find the label.



Cell: YD 501012, 40 mAh

Measured: 12.8 × 9.6 × 5.5 mm



The part number is the nominal cell size. 501012 means 5.0 mm thick, 10 mm, 12 mm. That's a useful starting point for searching, but it only describes the bare cell. The protection board and the wire joint add to the real dimensions, and different sellers measure differently — some quote the cell alone, some quote the whole assembly. Check the actual measurements in the listing, and where the protection board sits, before you order.



Note the measured thickness is 5.5 mm against a nominal 5.0 mm. You can see in the photo in step 6 that this cell has already swollen a little. That's normal after years in storage and it's almost certainly why the runtime was so bad.



There's no spare room in the shell, so a physically larger cell won't go in. Match these dimensions when you source a replacement.



⚠️ A swollen cell needs care. Don't press it, bend it or puncture it. Lift it out flat, keep it away from anything flammable, and take it to a battery recycling point soon rather than leaving it on the bench.



Step 6: Fitting the new battery





[pic: disconnecting one lead at a time, new cell ready]



Disconnect one lead at a time, and insulate each one as soon as it's free. If you cut both leads together with metal cutters you short the cell, because the tool bridges the terminals.



I cut the positive lead first, kept it away from anything metal, taped the end, and only then did the negative.



Choosing a replacement



The cell I used came from a source I trust. It has a protection board built in and a recent manufacturing date. Both of those matter more than the brand name. A cheap unprotected cell sealed inside an earbud isn't worth the risk.



The best match I could find was a 301012, 30 mAh:



Original  vs.  Replacement

Part: YD 501012 vs. 301012

Capacity: 40 mAh vs. 30 mAh



Nominal size: 5.0 × 10 × 12 mm vs. 3.0 × 10 × 12 mm



Same footprint, 2 mm thinner, 25% less capacity. Less runtime than a factory-fresh bud, but still better than a swollen cell.



The thinner cell leaves about 2 mm of slack in the pocket. I wrapped it with high-temperature-resistant tape until it was a snug fit, which stops it moving around and also insulates it against any short.



Step 7: Soldering





[pic: new battery soldered to the back side of the PCB]



This is the part that needs real soldering skill. The bud and its PCB are small and won't stay put on their own, so I'd strongly suggest a soldering fixture or helping hands. In practice it isn't really optional.



The glue is the main obstacle. The wires and PCB are held with adhesive, which works well against vibration, but under the iron it softens, flows, and covers the pad you're working on. There are also several connectors and wires close by, so there's very little clean space.



What I did instead: I removed the old battery wires from the front of the PCB and soldered the new ones to the back. The joints are through-hole, so the same pads are reachable from behind, and that side is clean and open with no risk of bridging to a neighbouring connector.



Test before you close up. Once the battery is connected the LED should light. The bud doesn't power on by itself, though. The pogo pins go straight to the chip's capacitive sensing pin, so it's your hand on the pins that triggers it. Either way, the LED tells you the joints are good. Check now, not after reassembly.



One thing Pine64 got right: the original wire is ultra-fine, heat-resistant and break-resistant, noticeably better than what came with my replacement cell. Ordinary insulation shrinks back or melts if the iron sits on it a moment too long.



Which gives an option worth considering. You could keep the original wire. Cut the old cell's leads a few millimetres from the battery, cut the new cell's leads short, and splice the two with heat-shrink. The PCB joints never get touched, and the delicate work happens in open air with no glue nearby.



Step 8: Reassembly





[pic: glue applied over the battery terminals]



Before closing anything, check that the battery is seated properly, the wires are clear of any pinch points, and there's nothing that could short.



I put glue over the battery terminals to protect them, and used it to hold the PCB down since the heat-staked posts were cut off in Step 4.



Then, in order:

    1. Seat the rubber gasket back onto the microphone. Easy to forget, and a missing gasket means a muffled mic.

    2. Check the aluminium foil inside the cover is intact and will sit flat against the pogo pins.

    3. Apply glue around the inner edge of the shell.

    4. Press the cover back on.



The glue is optional. The internal clips hold the shell closed on their own, so skip it if you'd rather keep the bud easy to open again. When the cover seats properly you'll hear a clear click, and that means it's home.



! Keep glue away from the pogo pins, the aluminium foil, and the clear plastic LED light guide inside the cover. Adhesive on the pins or foil insulates the contact and kills the touch controls. Glue on the light guide clouds it and dims the LED.



Step 9: Clamping and curing





[pic: earbud clamped shut with a clip]



Clamp the bud shut with a folded paper towel between the clip and the shell, so the pressure is spread out and the plastic doesn't mark. Leave it clamped while the adhesive cures.



I used T7000, the black cellphone repair glue for resealing phone housings after a screen replacement.



Set time 3–6 minutes

Full cure 24–48 hours

Temperature range −35 °C to +90 °C



It's sold as waterproof, flexible, vibration-damping and low-odour once cured.



Don't rush the cure. It's tempting to test after a few minutes, but the bond won't reach full strength for a day or two, and this is the joint holding a lithium cell inside a sealed shell.



Two tips for using it on earbuds. Use it sparingly, because squeeze-out inside the shell is very hard to clean up. And let the buds air out before wearing them, since the solvent smell takes a while to leave a small enclosed space that sits in your ear.



Results







[pic: PineBuds with new battery, working]


Tested at low volume with ANC off, playing continuously until the earbud announced shutdown.

The original cell managed about 1 hour before I started.

First full charge after the repair: 2 hours 11 minutes
Second full charge: 2 hours 48 minutes

The jump between the two surprised me. A new cell usually needs a few charge cycles before it settles at its real capacity, so I'd expect the third and fourth runs to land somewhere near the second. Worth knowing if you do this yourself: don't judge the result from the first charge alone.

ANC still works, along with the touch controls and the microphone. This one matters, because Pine64's own store page warns that dismantling the buds can affect performance and ANC especially. It survived on my pair.

Going from 40 mAh to 30 mAh does cost some capacity on paper. But the runtime nearly tripled, which tells you how far gone the original cell was, and the swollen one is out of the earbud, which I wanted to do anyway.


A few notes



These are nice to work on.

The shell opens without breaking anything, the wire quality is good, and the board is tidy inside.

Better than I expected, honestly.



small things that would make life easier for the next person:



The heat-staked posts are the only step you can't undo. Everything else comes apart and goes back together fine.

A clip or a single small screw would make these properly repairable

as long as whatever replaces the staking still lets the shell give a little, so a swelling cell can push the case open rather than building pressure inside it.]]> https://forum.pine64.org/showthread.php?tid=20333 Tue, 28 Jul 2026 20:40:36 +0000 MaSk]]> https://forum.pine64.org/showthread.php?tid=20333
I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/]]>
I think it's time to challenge that. That belief led me to write a hacker phone manifesto — an attempt to revisit the values behind devices like the N900, and sketch what a phone that's open and hardware-expandable could actually look like.

I'd love to hear whether people think this is technically viable today, or whether the market killed that idea for good reasons. And if this is off-topic here, I apologize in advance, you can point me some place better.

https://beyondframe.ink/hacker-phone-the...-hardware/]]> https://forum.pine64.org/showthread.php?tid=20332 Tue, 28 Jul 2026 20:07:38 +0000 NonPlayableCharacter22]]> https://forum.pine64.org/showthread.php?tid=20332
Worst of all, after all this, when I finally hit pay, I get this wonderful error: "Field Billing address 1 should have only English letters, digits, spaces and , / @ . ( ) - characters."

Great, ascii is the only character set in the world. For Once I decided to spend more money on a company with values I respect, I am barred from buying. It is like you do not want anyone in Europe to buy from you. 

I corrected the address and the error still exists. Only after two tries I realised it is talking about the main billing and shipping address not the billing address it asks AGAIN after entering card details.

I don't need any resolution for this until you fix this terrible website. Even AI can make a better payment experience than Pine64. I still have not placed the large order I wanted and am now considering going back to buying cheaper ones from other sources. Thank you very much guys.]]>
Worst of all, after all this, when I finally hit pay, I get this wonderful error: "Field Billing address 1 should have only English letters, digits, spaces and , / @ . ( ) - characters."

Great, ascii is the only character set in the world. For Once I decided to spend more money on a company with values I respect, I am barred from buying. It is like you do not want anyone in Europe to buy from you. 

I corrected the address and the error still exists. Only after two tries I realised it is talking about the main billing and shipping address not the billing address it asks AGAIN after entering card details.

I don't need any resolution for this until you fix this terrible website. Even AI can make a better payment experience than Pine64. I still have not placed the large order I wanted and am now considering going back to buying cheaper ones from other sources. Thank you very much guys.]]> https://forum.pine64.org/showthread.php?tid=20308 Sun, 28 Jun 2026 16:45:42 +0000 tantamount]]> https://forum.pine64.org/showthread.php?tid=20308
https://threat-modeling.com/arch-linux-a...june-2026/]]>
https://threat-modeling.com/arch-linux-a...june-2026/]]> https://forum.pine64.org/showthread.php?tid=20281 Mon, 01 Jun 2026 13:16:01 +0000 sam_uk]]> https://forum.pine64.org/showthread.php?tid=20281 https://pine64.com/product/yuzuki-avaota...-4gb-32gb/

Trying to get mainline on it: https://github.com/Agroecology-Lab/build

Running into issues with it https://github.com/Agroecology-Lab/build/issues/1

If anyone wants to play along or help that would be great]]> https://pine64.com/product/yuzuki-avaota...-4gb-32gb/

Trying to get mainline on it: https://github.com/Agroecology-Lab/build

Running into issues with it https://github.com/Agroecology-Lab/build/issues/1

If anyone wants to play along or help that would be great]]> https://forum.pine64.org/showthread.php?tid=20279 Sat, 30 May 2026 16:28:09 +0000 A Mnesia]]> https://forum.pine64.org/showthread.php?tid=20279
Is there any way to totally and completely disable this auto-boot behavior?

Thank you very much in advance.]]>
Is there any way to totally and completely disable this auto-boot behavior?

Thank you very much in advance.]]> https://forum.pine64.org/showthread.php?tid=20215 Wed, 11 Mar 2026 17:42:20 +0000 Mitrax]]> https://forum.pine64.org/showthread.php?tid=20215
I'm currently developing a small Android app called Dormivox.

The Bluetooth feature was mainly designed with the Pine watch in mind – mostly because I like the project.

Current features:
• Live noise level detection
• Alarm to interrupt snoring
• Night statistics and history
• Playback of recorded audio segments
• Optional Bluetooth heart rate input (BLE)

I'm particularly interested in testing Bluetooth heart rate devices with open BLE support (for example PineTime or other BLE HR monitors).

If anyone here would like to try it and give some feedback, that would be very helpful.

You can find the app on the Play Store by searching for: Dormivox

Thanks!
Mitrax


  dormivox_audio_graph_600.jpg (Size: 66.49 KB / Downloads: 233) ]]>
I'm currently developing a small Android app called Dormivox.

The Bluetooth feature was mainly designed with the Pine watch in mind – mostly because I like the project.

Current features:
• Live noise level detection
• Alarm to interrupt snoring
• Night statistics and history
• Playback of recorded audio segments
• Optional Bluetooth heart rate input (BLE)

I'm particularly interested in testing Bluetooth heart rate devices with open BLE support (for example PineTime or other BLE HR monitors).

If anyone here would like to try it and give some feedback, that would be very helpful.

You can find the app on the Play Store by searching for: Dormivox

Thanks!
Mitrax


  dormivox_audio_graph_600.jpg (Size: 66.49 KB / Downloads: 233) ]]> https://forum.pine64.org/showthread.php?tid=20209 Mon, 09 Mar 2026 15:46:33 +0000 recursivenomad]]> https://forum.pine64.org/showthread.php?tid=20209
I see that making a purchase to the US is still charging the full $25 shipping, noting coverage for tariffs, and the amount has not changed since the US Supreme Court decision to suspend specific tariffs in February.  I just wanted to ask if there are any plans to update this cost to reflect the new tariff situation, or if this cost is expected to remain the same?

Thank you for developing and selling awesome open-source hardware ]]>
I see that making a purchase to the US is still charging the full $25 shipping, noting coverage for tariffs, and the amount has not changed since the US Supreme Court decision to suspend specific tariffs in February.  I just wanted to ask if there are any plans to update this cost to reflect the new tariff situation, or if this cost is expected to remain the same?

Thank you for developing and selling awesome open-source hardware ]]> https://forum.pine64.org/showthread.php?tid=20208 Sat, 07 Mar 2026 07:17:44 +0000 kulala]]> https://forum.pine64.org/showthread.php?tid=20208 ]]> ]]> https://forum.pine64.org/showthread.php?tid=20188 Mon, 09 Feb 2026 01:52:50 +0000 gwennelsonuk]]> https://forum.pine64.org/showthread.php?tid=20188 A small, audio-first handheld released as an open dev platform, derived from PinePhone hardware, designed to be capable of a Rockbox port. Physical controls, great battery life, optional PineBuds + external display support. I would buy one immediately and actively work on the Rockbox port — I’ve been wanting an open hardware Rockbox target like this for a long time.
I wanted to float an idea that feels very aligned with Pine64’s strengths: reuse existing work, document it well, and let the community do interesting things with it.

Concept:
A single-purpose handheld primarily intended as a media player, but released explicitly as an open development platform, not a polished consumer product.

Think: “PinePhone without the phone.”

High-level hardware direction:

• Start from the PinePhone hardware lineage (SoC, audio path, power, USB-C)
  
• Remove phone-specific components (modem, cameras, etc.)
  
• Reduce overall size
  
• Add a small, low-power screen
  
• Physical controls (rocker / select / hold)
  
• Headphone jack, microSD
  
• Focus on battery life
  

Rather than shipping with Rockbox, the goal would be to release a platform deliberately capable of supporting a Rockbox port, alongside other lightweight or experimental software.

Why this seems like a good Pine64 fit:

• Rockbox already solves the hard problems for this class of device (audio quality, codecs, physical controls, power efficiency).
  
• Pine64 already excels at open ARM hardware where the value is documentation, reuse, and community ports
  
• There’s growing interest in calm, offline, single-purpose devices (especially for music) that don’t try to compete with phones.
  

Personal note:
I would immediately buy this device and actively work on the Rockbox port. I’ve been wanting a modern, openly documented hardware platform suitable for Rockbox for some time, and this would be an ideal target.

Natural extensions (without diluting the focus):

• PineBuds support for local playback and experimentation
  
• Modest mic + compute for on-device translation / transcription experiments (not positioned as an “AI gadget”)
  
• Optional external display support over USB-C for docking or experimentation, while remaining clearly a handheld media player first
  

The intent wouldn’t be another general-purpose Linux handheld, but:
an audio-first device released as a documented, hackable platform with a clear “this could run Rockbox” target many people already understand and want.

This feels like one of those rare ideas where most of the hard engineering is already solved, and the main challenge is restraint — choosing what not to include.

Curious what others think]]> A small, audio-first handheld released as an open dev platform, derived from PinePhone hardware, designed to be capable of a Rockbox port. Physical controls, great battery life, optional PineBuds + external display support. I would buy one immediately and actively work on the Rockbox port — I’ve been wanting an open hardware Rockbox target like this for a long time.
I wanted to float an idea that feels very aligned with Pine64’s strengths: reuse existing work, document it well, and let the community do interesting things with it.

Concept:
A single-purpose handheld primarily intended as a media player, but released explicitly as an open development platform, not a polished consumer product.

Think: “PinePhone without the phone.”

High-level hardware direction:

• Start from the PinePhone hardware lineage (SoC, audio path, power, USB-C)
  
• Remove phone-specific components (modem, cameras, etc.)
  
• Reduce overall size
  
• Add a small, low-power screen
  
• Physical controls (rocker / select / hold)
  
• Headphone jack, microSD
  
• Focus on battery life
  

Rather than shipping with Rockbox, the goal would be to release a platform deliberately capable of supporting a Rockbox port, alongside other lightweight or experimental software.

Why this seems like a good Pine64 fit:

• Rockbox already solves the hard problems for this class of device (audio quality, codecs, physical controls, power efficiency).
  
• Pine64 already excels at open ARM hardware where the value is documentation, reuse, and community ports
  
• There’s growing interest in calm, offline, single-purpose devices (especially for music) that don’t try to compete with phones.
  

Personal note:
I would immediately buy this device and actively work on the Rockbox port. I’ve been wanting a modern, openly documented hardware platform suitable for Rockbox for some time, and this would be an ideal target.

Natural extensions (without diluting the focus):

• PineBuds support for local playback and experimentation
  
• Modest mic + compute for on-device translation / transcription experiments (not positioned as an “AI gadget”)
  
• Optional external display support over USB-C for docking or experimentation, while remaining clearly a handheld media player first
  

The intent wouldn’t be another general-purpose Linux handheld, but:
an audio-first device released as a documented, hackable platform with a clear “this could run Rockbox” target many people already understand and want.

This feels like one of those rare ideas where most of the hard engineering is already solved, and the main challenge is restraint — choosing what not to include.

Curious what others think]]> https://forum.pine64.org/showthread.php?tid=20181 Sun, 01 Feb 2026 22:30:37 +0000 Mitrax]]> https://forum.pine64.org/showthread.php?tid=20181
Using PineWatch and reading Open BLE was very easy to implement to my App.
Just with Built in OS.
So far, im using HeartRate in my App, no Gatebridge needed, just simple as can be. 

Thanks for that.

Greets]]>
Using PineWatch and reading Open BLE was very easy to implement to my App.
Just with Built in OS.
So far, im using HeartRate in my App, no Gatebridge needed, just simple as can be. 

Thanks for that.

Greets]]> https://forum.pine64.org/showthread.php?tid=20179 Sun, 01 Feb 2026 18:30:49 +0000 dustfinger]]> https://forum.pine64.org/showthread.php?tid=20179
I re-registered my nick yesterday on IRC because I have been inactive for a while. I have not received a confirmation email and I just wanted to let you know incase my registeration got missed somehow. My IRC nick is dustfinger, just like my forum username.

Thanks,

dustfinger.]]>
I re-registered my nick yesterday on IRC because I have been inactive for a while. I have not received a confirmation email and I just wanted to let you know incase my registeration got missed somehow. My IRC nick is dustfinger, just like my forum username.

Thanks,

dustfinger.]]> https://forum.pine64.org/showthread.php?tid=20177 Sat, 24 Jan 2026 18:31:18 +0000 heocb]]> https://forum.pine64.org/showthread.php?tid=20177 on free software except from a ram training blob. Thank you.]]> on free software except from a ram training blob. Thank you.]]> https://forum.pine64.org/showthread.php?tid=20129 Fri, 19 Dec 2025 11:31:47 +0000 Sergiu]]> https://forum.pine64.org/showthread.php?tid=20129
Does anyone have a clear answer to this? Has anyone ordered recently and paid or not paid anything extra?]]>
Does anyone have a clear answer to this? Has anyone ordered recently and paid or not paid anything extra?]]>