08-24-2020, 07:25 AM
(This post was last modified: 08-24-2020, 07:50 AM by hackerfantastic.)
I ordered a Pinebook Pro in August 2019 and my unit arrived sometime in December. I had a US ANSI keyboard model. However over the last few weeks I started noticed weird power behaviour, the laptop would be left on overnight on charge but in the morning I would find the battery completely depleted or the device had randomly powered itself off for no valid reason. I have not taken the device out of my house, and just move it between a few rooms - so I put it down to linux being linux. I would unplug and replug it, power cycle and notice the battery seemed to be getting a charge but that there did appear to be some kind of power related issue but did not think much of it. Until it died.
Now, the pinebook pro will not even charge on the barrel jack. The pbp died completely 3 days ago, when I connect two different PSU's (which I tested at giving 5V out each with a multimeter) on the barrel jack, I got absolutely no red light indicating power, the laptop was completely dead. I left it charging via USB-C which did give me a charge indicator, it took several hours to get enough charge to power on the laptop. Once I booted the laptop I noticed that the battery indicator stated "discharging 0%" and after a few minutes with the device powered via USB-C, it would just switch off anyway (after a good 12 hour charge).
I opened the case, disconnected the battery, connected the bypass wires and then powered from barrel jack - nothing, the barrel jack is completely dead, however the USB-C power input would work but was not able to give it enough power to complete booting from the NVMe. The pbp is hosed, so I looked to see what the fault could be.
I have identified that one of the transistors besides where the "bypass" cables are wired appears to have let out the magic smoke, additionally I am disappointed at the state of the soldering job on those wires - they are basically soldered on in such a way that undoubtedly these bypass cables have moved around over time introducing a short - the metal contacts of the wires runs right across the flex cable battery connector, this I believe is what has caused the transistor to blow and break the charging circuit. The cables are half exposed when connected to the PCB and are soldered on in a blob method right across the battery contacts and alongside where the blown transistor appears. Picture below.
I have ordered a new replacement pinebook pro mainboard as unfortunately I was using this thing for actual coding work at night time and aside from the exploding transistor of death it's been a rather decent little machine! in the interim I will try to swap out the blown transistor - does anyone know what component that is on the board above, its the middle transistor that has clearly cracked open? One thing I would definitely do on my new unit when it arrives is remove those bypass cables unless I actually intend to power it without a battery direct from DC, as undoubtedly I believe they are the reason the board short circuited on the power circuit at some point (at least that is my best guess right now). Oddly, those are both soldered with VCC + GND connected to the same pads, they should be removed if not required. Is anyone else noticing the poor connectivity of these wires? Is this a known fault? Have others experienced it?
The machine was powered on most days, didn't have anything plugged into it aside from USB controllers and an RTL-SDR so nothing else can seemingly explain the transistor of death.
Now, the pinebook pro will not even charge on the barrel jack. The pbp died completely 3 days ago, when I connect two different PSU's (which I tested at giving 5V out each with a multimeter) on the barrel jack, I got absolutely no red light indicating power, the laptop was completely dead. I left it charging via USB-C which did give me a charge indicator, it took several hours to get enough charge to power on the laptop. Once I booted the laptop I noticed that the battery indicator stated "discharging 0%" and after a few minutes with the device powered via USB-C, it would just switch off anyway (after a good 12 hour charge).
I opened the case, disconnected the battery, connected the bypass wires and then powered from barrel jack - nothing, the barrel jack is completely dead, however the USB-C power input would work but was not able to give it enough power to complete booting from the NVMe. The pbp is hosed, so I looked to see what the fault could be.
I have identified that one of the transistors besides where the "bypass" cables are wired appears to have let out the magic smoke, additionally I am disappointed at the state of the soldering job on those wires - they are basically soldered on in such a way that undoubtedly these bypass cables have moved around over time introducing a short - the metal contacts of the wires runs right across the flex cable battery connector, this I believe is what has caused the transistor to blow and break the charging circuit. The cables are half exposed when connected to the PCB and are soldered on in a blob method right across the battery contacts and alongside where the blown transistor appears. Picture below.
I have ordered a new replacement pinebook pro mainboard as unfortunately I was using this thing for actual coding work at night time and aside from the exploding transistor of death it's been a rather decent little machine! in the interim I will try to swap out the blown transistor - does anyone know what component that is on the board above, its the middle transistor that has clearly cracked open? One thing I would definitely do on my new unit when it arrives is remove those bypass cables unless I actually intend to power it without a battery direct from DC, as undoubtedly I believe they are the reason the board short circuited on the power circuit at some point (at least that is my best guess right now). Oddly, those are both soldered with VCC + GND connected to the same pads, they should be removed if not required. Is anyone else noticing the poor connectivity of these wires? Is this a known fault? Have others experienced it?
The machine was powered on most days, didn't have anything plugged into it aside from USB controllers and an RTL-SDR so nothing else can seemingly explain the transistor of death.