From Newsgroup: comp.mobile.android
In comp.mobile.android, on Thu, 06 Aug 2026 17:43:31 -0400, micky <
NONONOmisc07@fmguy.com> wrote:
I was using a steak knife to pry the battery out, and at one point it >>sparked, but when it was out I could not find any metal showing except
at the end of the ribbon cable, and that was not where the spark was.
I used the phone for about 15 minutes 24 hours ago, and just now pickes
ir up. Sometimes the screen is right but most of the time there are >>vertical bars of varying transparency going from the top to the bottom
of the screen.
I'll take it apart in an hour but I'm 98% sure I made good connections
with the battern ribbon and the other ribbon, and I'm sure the ribbon I >>didn't connect is not doing this, because the back is off now and I'm
still getting the vertical bars. (Yes, I should have put some tape
between the two halves of the unconnected connector, but I don't think
they touched.)
Could a bad battery be doing this?
Goodle says, and if it's not the *new* battery, I could have predicted
that it's the snap-on connector, and indeed when I took the internal
cove off, the cable came with it, instead staying stuck It is hard to
connect those those things. So I tried again, and still no good.
Do you think I can be dmageing anythign by trying to run it with the
main, non-battery ribbon ccnnector from the bottom of the phone to the
top, misconnected?
ASI says "Yes, you can permanently damage an Android phone by assembling
it with a ribbon connector out of place.
Potential Risks
Bent or Crushed Pins: Forcing the phone together can crush the tiny
metal pins inside the connector.
Electrical Short Circuits: Misaligned pins can route power to the
wrong data lines, instantly frying components on the motherboard.
Torn Cable Ribbons: Putting pressure on a twisted or improperly
seated cable can easily tear its delicate copper traces."
And I think I did that, except the phone worked fine for at least 20
minutes last night. I did lots of things with it. I took pictures with
the flash in automatic, off, and on, and I looked at the pictures, and
they looked okay. . I looked at my gmail and at my Fastmail, I
downloaded more fastmail, and it was okay.. I used google lens, which
also uses the camera, to look at some little device I found in my
drawer, that plugged into the audio jack on iirc a cell phone, and I
read what Google Lens had to say and looked at one of the links. I put
the rubber case on,
I did all that last night, and may have used it this morning too. I
didn't bounce the phone around. I worked on the fence this morning and
the phone stayed on the kitchen table.
I didn't charge it because one set of instructinos said to run it down
and fully charge a new battery twice -- but other instructions didn't
say that and I was going to ask here.
There is a plastic cover for the "logic board" that is held on by 10
screws. When removed, you can see it has at least 4 rubber pads, two of
which are over the ribbon connectors from the battery and from the
bottom of the phone, the one that was loose when I took it apart the
second time Yhe pads are clearly designed to keep the connectors in
place. Maybe I should have tighten the screws another turn? The sceews
are 8 threads in an eighth of an inch. Could 1/64th or even 1/32 of an
inch not tightened be enough for the connector to move? None of the 10
screws were tight when I first unscrewed them. I tried to make them the
same tightness.
Of course I was happy to save 4 or 500 dollars but the bigger problem is
not the money I won'd save. It's the defeat. It's the failure to win.
I bought the phone 6 years ago. For a lot of you, that's plenty, but I
wanted to prove I could make it last much longer. But that's not the
defeat that's really bothering me. Its the failure to be able to
replace the battery, the failure to fix it. It's almost worse because
I seemed to have fixed it. And it *is* worse because I'm too stupid to
know what went wrong, after it was fixed.
--- Synchronet 3.22a-Linux NewsLink 1.2