Develop Bugs

Need help from an expert

So my phones earpiece began to cut in and out, which I found to be a chafed and broken flex cable. No biggie, I ordered a replacement piece and waited for it to show. As I waited the phone began to get worse, I lost the earpiece entirely, the leds stopped working as well as the sleep button. The screen, now only able to be woken by sliding, would not come on when slid out, but only once it returned..also the screen would shut off when I would slide it out again.
I have seen disassembled the phone again and installed the new cable and all is well, with one exception. The slide function of the screen no longer works, period. It will not wake, it will not rotate, and the keyboard doesnt illuminate unless I press a key. I have been through this phone 4 more times now and I simply cannot pin down exactly what tells the phone that it has been slid. I have heard talk of magnets, but found no sensor or magnet, I saw small contacts..that are all functioning properly. There is no cable or connection to the screen portion that connects to any sort of switch that I can see.
Does anyone know what triggers the slide?!

Sorry mate, im not an expert but I thought this may help.
https://fjallfoss.fcc.gov/oetcf/eas...e=N&application_id=259614&fcc_id='NM8RHOD300'
The link is to the FCC website showing links to internal photos of the phone, SAR values, micellaneous stuff, etc.
Maybe a different perspective of the phone might help.
Hope this helps you

[Q] Desire HD very sick - need repair help

Hiya,
my Desire HD got wet in the front pocket of my fleece, not drowned just some droplets of water that got inside the Otterbox case and into the phone. I did try and turn it on before I realised it had got wet, it wouldn't power up.
I removed the phone from the Otterbox and dried everything and tried to turn it on again as there was only very slight traces of moisture apparent. There was condensation and a couple of little drops of water inside. I discovered there must have been enough moisture to short out the battery as there was a little residue mark above the contacts on the inside of the casing. I then noticed the liquid indicators had turned red.
I removed the battery cover and dried the phone gently using an electric room heater for hours, I also put the phone in a bag of rice for a couple of days.
I tried to power it up again after a few days in the rice and it wouldn't start up. I measured across the battery contacts with a multi meter and found the battery was open circuit, so I know it must have shorted. Hoping that this was the only damage I bought a new replacement battery. When I fitted the new battery nearly a week later and switched on the phone, everything seemed to be fine but the display seemed to flash, and as I had a Leedroid rom installed I heard R2D2 chirping and could see the device start to boot up as normal on the screen. Then the display went dark and hasn't worked since. I stripped the phone and cleaned a couple of patches of residue, one of which was right in the lcd connector.
Now when I try and start the phone there is no display, the phone vibrates once when I hold in the power button. Approximately 40 or 50 seconds later I can hear R2D2 making his tweeting noises which always happens on boot up. I didn't think it took so long to hear R2D2 but maybe the phone is checking the file system or something now, and I just can't see it.
It may be that I just need a new screen & digitizer to repair the phone, but I can't tell what might be on the display - maybe it's the phone unlock screen asking for my pin number etc. I can't see any image on the screen, that you would normally see when the baclight is faulty, I have tried to view it with a desk lamp, but it's just black. The capacitive buttons at the bottom don't seem to have any effect, perhaps they are not enabled if it's sitting at the password screen, if it is at that screen.
The l.e.d's don't light up at the top when I turn it on or plug in the charger.
I might have also damaged the volume key switch/ribbon slightly.
What would you do with this phone, any advice on how I could proceed ?
Would it be working just with no display, as R2D2 is squeaking(Leedroid rom has this when the device boots and has an animation of a pc booting up with the post screen) ?
No l.e.d's is a bit worrying and it doesn't seem to know when on charge etc. but perhaps they only work once the phone has booted, I can't remember DOH!
I just thought I would ask, as there are a lot of knowledgeable people on here and it might be possible to save my droid.
Grateful for any help or advice
kind regards
Barry

[Q] Weird touchscreen behaviour (only works when keyboard is flipped out?)

Hi everyone,
I've had my Desire Z for little over 2 years now and two months ago (was running CM7.2 at the time) I started getting a weird issue where my touchscreen would only be responsive when the keyboard was slid out (so the opposite problem of what quite a few other people have reported where the touchscreen becomes unresponsive when the keyboard is out). The status LED would also stay off whenever the keyboard was closed, and the keyboard backlight didn't come on anymore at all. Also, I had to make sure that the keyboard was slid out during boot, if the phone booted without the keyboard out the screen would not become responsive at all until after another reboot. My earpiece speaker stopped working around the same time so I was wondering whether it was just an issue with the flex cable becoming a bit loose, but the touchscreen would consistently start working again when I flipped the keyboard out, and also the physical scroll button on the top bit would always work, so I was still hoping it would be some weird software issue.
I then upgraded to Flinny's (amazing) Andromadus ROM (build 22, complete data+dalvik wipe) after which the keyboard backlight started working again, but the rest remained pretty much the same. Since then the touchscreen issues have been getting worse, so that I sometimes have to flip the keyboard in and out again a few times, or turn the screen on or off with the power button several times before it becomes responsive again, but then it tends to work fine until I lock the screen again, with no noticeable dead spots anywhere on the screen. I've had days where it worked all day without problems (except having to flip out the keyboard, that's been a constant for the past two months), and then today I haven't been able to get the screen to do anything at all even after dozens of reboots.
I've already bought a new digitizer and am all ready to put it in (I'll have to replace the broken earpiece anyway), but was wondering whether anyone has any thoughts on whether it could still be a software issue after all, or if anyone has experienced anything similar? The thing with having to flip the keyboard out to get not only the touchscreen but also the status LED to work is just so weird and makes me doubt that it's a pure broken digitizer or lose flex cable issue, so I'm wondering whether it would be better to first try reverting to a stock ROM before taking on the messy sticky glue stuff (I should be fine but still, never done it before)?
Many thanks!

From what you describe my best guess would be the main flex cable is what needs to be replaced. Flash a touch based recovery and see if you have the issue there as well, if so its very unlikely that its anything but a hardware fault
Sent from my Nexus 4 using Tapatalk 2

Thanks for the heads-up, I've been playing around a bit more with software and I do manage to get the screen working again occasionally, typically after the second boot into a newly flashed ROM or restoring a backup, and only until one or two reboots later when it becomes completely unresponsive again. I've tried CM 7.2.0 as well as Flinny's Andromadus 10, and it is only complete flashing that does the trick, cache wipe or factory reset alone does nothing. The two occasions where the touchscreen worked were still limited to when the keyboard was flipped out, and it also had to be flipped out during boot, otherwise nothing would work. I've learned to navigate my way around the phone by just using the hardware navigation button, but I'll have a close look at the flex cable when I take it apart to replace the earpiece speaker tonight...

Hello,
so I took my dear phone apart yesterday to replace the broken earpiece - everything went fine but after reassembly the replacement earpiece isn't working either, which leads me to think that all those little broken bits might actually be related to some contacts being a bit lose, all in the same region. Should've thought about that earlier really since the earpiece and the LED (only works when keyboard flipped out) are both in that top region that the digitiser data presumable also has to run through before passing through the flex cable.
In any case, I also took a picture of the flex cable which is slightly bent but doesn't seem straightforwardly damaged (see attachment, that thing on the right is *not* a rip). Think it's worth trying to replace it anyway?
What was truly bizarre is that after the first boot following reassembly the touchscreen worked quite consistently for the entire evening - I thought I might've fixed a lose contact by un- and replugging the digitiser cable, but then the screen went nonreactive again at some point. I wonder if the working screen was again actually related to some software reset caused by the battery being taken out for so long? In the meantime the actual screen and trackball are still working away perfectly. Bizarre.

Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)

obstacle3 said:
Just to let people know the solution to the mystery: the increasingly odd behaviour was actually caused by an initially small rip in the flex ribbon cable that got bigger and bigger - it's actually half-visible in the picture I uploaded above, only that the rip is where the cable comes out from underneath the case, and not where it's wrinkled!
Just in case it could be useful for anyone, here's the (top half of phone) components in the order in which they failed on me, which I guess corresponds to the order of the respective data lines in the ribbon cable (from the top of the phone towards the center):
environment brightness sensor (I thought that the sensor had been broken for almost a year, but as soon as I rebooted with the new flex cable I noticed how my phone stopped shining into my face at full brightness - if your brightness sensor gets stuck reporting the same (low) value this means your flex cable is on its way out!)
earpiece speaker
status led
touchscreen
screen (non-alignment with edge of screen, visual artefacts)
screen (fade to black/power interrupt)
Click to expand...
Click to collapse
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone

fireball0093 said:
I'll for sure keep that in mind. Mine is still going strong for the time being, but it's good to know some warning signs if I need to replace parts or if it's time to get a new phone
Click to expand...
Click to collapse
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]

obstacle3 said:
Replacement parts all the way, the repair was 15$ and it feels as good as new! Well, it could do with a new battery but that's just another 5..
Just realised that the proximity sensor should actually be added to the very top of the list - just noticed that faint red light when taking a phone call, don't remember seeing that in almost a year :]
Click to expand...
Click to collapse
That's not a bad cost at all. I know I'm going to have to replace my keyboard in probably 2 months or so (maybe sooner) because some buttons are starting to not work. Other than that fact my phone is currently still going strong for being going on a 3 and a half year old phone

[Q] LG G3 display not working

Upon power up flashes green then blue, no LG logo or anything else. If i plug USB connection to the PC the PC recognizes the phone any suggestions? By the way this happened after the phone was dropped, no visible signs of the screen being cracked.

Try holding power button for like 30 seconds. Or pull battery

Was this ever resolved? My friends phone did the exact same thing the other night, you can still feel it vibrate across the unlock pads and it makes noise and everything when receiving texts, can even answer calls if you know exactly where to push accept call.
It's the strangest thing.

Looks like a broken mainboard from the drop. Or perhaps cracked screen near the connection to the mainboard.

Not Resolved
VeeDaub said:
Was this ever resolved? My friends phone did the exact same thing the other night, you can still feel it vibrate across the unlock pads and it makes noise and everything when receiving texts, can even answer calls if you know exactly where to push accept call.
It's the strangest thing.
Click to expand...
Click to collapse
Replaced the bazel/Screen/LCD, still same issue.

As I said: broken mainboard....

Same friend I was talking about earlier, exact same issue, he had his old phone he was using and just recently we found the issue, it had mild water damage from snow getting in his pocket right around the display connector inside, so we cleaned it up with alcohol, made some colors at the bottom but then would go black again, we took the logic board out, reflowed it in stages on each side so everything was good, tried it again, exactly half the screen (right side) worked perfect, so finally, brought it in, they said the display was faulty and replaced the phone under warranty.
So, conclusion, we didn't touch the display, Bell said the display was broken and just replaced his phone.
We only touched the logicboard and we got it half working, if we knew a better method of reflowing a mobile logic board (chips on both sides so you can't reflow the same way as laptop motherboard) so it was a lot harder but we probably could have fixed it if we kept at it and knew more about what size of the logic board needed the reflow the most
We used a bunch of clay if anyone is wondering, worked it in out hands till it was very plyable, make a pile slightly bigger then logic board, push board flat I to clay so it holds the underside chips pressed and in place, reflow top, repeat once cooled, it got half the screen working from a phone that had physical water damage and corrosion on the display connector so, this will probably work for you.

Got an interesting problem.

Hey there. I'm a bit new to this side of XDA. Honestly with how long I've been AWOL from this site nothing is familiar anymore. How time flies. Well my first post back in years couldnt be more unfortunate phone wise, I've had my Z2 for a couple of months now and as a mechanic it's been treated like all my others phones prior, rough. I've been locally recognized as the guy who has a new phone every couple of months because he can't not shatter a phone. An expensive hobby of breaking phones. Well luckily I didn't shatter my Z2. I just water logged it. Gotta change things up right? So here's where the interesting problem comes in, I let the phone sit in rice for 30 hours, switching the rice out half way through. It acted up like you would expect in the first couple of hours but then stopped. When I pulled the phone out I scraped the rice out of all the books and crannies and tried to power it on, to no avail. Dead battery I assume, so I plug it in. Charge icon pops up, a sign of life! How glorious. So I let it sit for a minute as I assume the battery probably dropped below minimum voltage when the LEDs were freaking out. Went back to the phone, held the power button and no screen, but "Hello, Moto!" So at this point I'm convinced the screen is dead, so I force it off with the volume down method and pry off the screen. To find what? More water. Good Lord. This phone is incredibly water resistant just in reverse. So I do the only thing that makes sense at this point, I remove the ribbion connector from the board for the display and put the phone back in new rice as 2 separate pieces. I then leave it in there for another 30 hours switching the rice halfway. Bringing us to now. I took the phone out, cleaned all the rice out of the 2 pieces and off the remaining adhesive and connected the ribbion back to the board. Plug the charger in, and again, charging logo. But then I hold the power button and the TMobile splash screen pops up! Then the screen goes dead and once again, "Hello, Moto!". But whats different is now when the boot sequence is finished I can interact with the phone and it works, shake for flashlight, enter my passcode (just by feel cause I'm good like that, ladies hmu), and the button responds with vibration. The phone is working but no screen. So at this point I'm sure, the display driver is done. I murdered it in cold daylight. So I shut it off and start looking around for new screens, in the midst of this I knock the phone and accidentally hit the power button, and it starts to boot up. T-Mobile spash screen, screen death, "Hello, Moto!", and nothing. Now that seems weird. Why would it work twice on the TMobile splash? So I decide I'll try putting it in fastboot for S&G's. Restart, put it in fastboot and the screen stays on. Beautiful and clear as day, all buttons work, everything reads fine, but, if I go to boot it or do anyother action than "retart bootloader", the cycle continues. T-Mobile, death, hello Moto, nothingness. Now at this point I'm okay with the phone being dead, it's fine, but I'm intrigued now. What would cause the screen to work just fine when in the bootloader and the TMobile splash screen, but die when it boots? The phone is very clearly working in the background. I logged in, used Google assistant, used the flashlight, pressed buttons on the dialer, all without the screen but with haptic feedback and audio. Could the graphical side of the main partition just be corrupt, or maybe the display driver is dead but the main board interacts with it differently during fastboot? I'm far from being knowledgeable on the hardware side of these things but I'm really genuinely interested in getting feedback here from anyone with an idea of what is going on. I'll post a video here in a half an hour or so when I finish up with dinner.

AFAinHD said:
...snip...
Click to expand...
Click to collapse
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.

Uzephi said:
Well... It sounds like there is a short between the screen and the main board. It could have happened when you plugged it into power while parts were still wet causing a short to ground and frying a chip that controls display but not touch on the screen.
Best way I can describe it for you is if an ECU on a car got wet and shorted out. Everything works but you get an engine code for TPS sensor failure due to said short. (The ECU can't read TPS due to a short). That is what seems like what happened.
Click to expand...
Click to collapse
Well see I would think that as well but the screen does work. Just only in fastboot, and the boot logo.
I got the video here.

Fastboot is a pretty low level and most likely uses basic hardware. I mean really what is there to see but a simple background with some text. Once you load the OS then all the hardware and it's drivers into play. Have you tried booting into safemode? Ultimately you'll probably have to repair or replace, but there could be a slim chance that there's still a little moisture in there and it still has a short somewhere.