Develop Bugs

Phone turns off about once a week

The subject heading pretty much says it all. I think about once a week I'm coming to my phone, pressing the power button to wake up the screen, and I'm finding that the phone was totally off.
Just the other day it happened twice. Never happened before, and it may be a one off.
But am I just accidentally taping power off (which I'm pretty sure I am) or am I going towards making sure my backups are current and getting a replacement (no doubt referbished) Desire?

Perhaps it's a 3rd party application causing the issue?
I'd suggest you do a hard reset and see if the problem comes back.
It's pretty difficult to accidentally power off your device. You still have to go through 2 screen taps to power off after you long-press the stand-by key.
Get it exchanged if you've ruled out any 3rd party applications.

This happened to me for the first time yesterday. Left my phone in the glove box of my car, came back and it was turned off. It would turn back on either, I tried for ages in a mild panic!
When I got home I removed the battery for a bit and then it suddenly worked.
All been OK since.

ohyeahar said:
Perhaps it's a 3rd party application causing the issue?
I'd suggest you do a hard reset and see if the problem comes back.
It's pretty difficult to accidentally power off your device. You still have to go through 2 screen taps to power off after you long-press the stand-by key.
Get it exchanged if you've ruled out any 3rd party applications.
Click to expand...
Click to collapse
I was thinking about 3rd party applications, but haven't started investigating. Probably because of the frequency it occurs and the amount of apps I have. Though I think I only have pretty popular apps.
I did a post a while ago that I had dropped the phone in a very minor way that would not have broken a Jacobs Cream Cracker (if you don't live in UK, they are very fragile, brittle, biscuit type things). But on each of the two times, one of them being a very cushioned landing, when I picked up the phone, it was off. I was thinking that this must have been what happened. But I'm now thinking it was either a separate issue or coincidence because I don't drop the phone and it still is sometimes off. And I think this occured before even the minor falls.
Hmmmm.....

I just did a test and dropped it from exactly 3cm flat onto my desk and it was instant off. I should add that I have a silicone/gel tight case on my Desire.
Like I said before I don't think this is the main problem, I think this is a secondary issue. And as I've said before, I think the phone going off from this sort of a drop/shock is too sensitive and delicate. Maybe sometime is not quite as tight as it could be in other people's phones.

Perhaps the body of your device is a bit warped such that the battery is a bit loose. That would explain why your device would power off from shock. The battery contacts may have shifted.
Try this. Take off your battery cover. The battery contacts should be on the left (the side without the volume rocker). Try to leverage the right side (the side with the volume rocker) of the battery so that the battery remains in contact with the device. I would try to slip thin strips of paper on the right so that it pushes the battery to the left.
Then try your 3cm drop test again. See if it improves.
If it improves, you can choose to continue using this method (despite how ghetto it is). Or you can see if you can get it replaced under warranty. Don't mention that you dropped the device, of course!

Other issues (like the glovebox fellow) could be related to heat, too. If it's too warm, I wouldn't be surprised if it turns off and doesn't turn back on until it's cooled down.

The phone has never yet failed to turn on the instance I've pressed the power button.
Looking into said ghetto method....
Nope. Contacts on the phone are all sprunt and sticking out nicely to meet the contacts on the battery, which will then compress the sprung contacs. So I doubt pushing any of the contact out further will help.

Is there any sound meant to come from the phone when you shake it? I don't mean furiously shake it, but just a milding shaking by your ear.
I have always heard a small movement but had assumed it was the vibrating mechanism.

Cleargrey said:
Is there any sound meant to come from the phone when you shake it? I don't mean furiously shake it, but just a milding shaking by your ear.
I have always heard a small movement but had assumed it was the vibrating mechanism.
Click to expand...
Click to collapse
Its the camera lens (internal focus part). Its like this on all HTC devices due to the lens they use.

[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

Strange issues after water damage

Yesterday morning my girlfriend knocked over a cup of water off of my bedstand and after wiping up the mess we went back to sleep. I woke up and realized my phone was drenched as a result of this happening, as it was charging in a spot I usually don't put it. I fumble around with it and realize it's messed up pretty bad, though not black screen.
Fast forward to doing the rice treatment and using an un-harmed battery without the pink water damage indicator, all seems good. Phone turns on, runs full speed, plays sound, camera works, data works, etc. This is running task's AOKP.
I use it throughout the next day and then I notice my mobile connection drop completely. This isn't like 1 bar, it's like the triangle logo empty as in no service. Flipping between airplane mode doesn't seem to help like it normally does. Sporadically I'd get a bar with 3G or something.
Then, I flashed the new version of AOKP and upon reboot my phone's data is still not working and the network connection is always dead as well. But, there is also noticeable lag. Pressing the app drawer takes 3 seconds to load and I see the animation in very slow motion. Using a countdown app, it is literally noticeable that seconds are taking substantially longer than they should.
ODIN to complete stock and the lag is still there. Data is in and out. Also if I let the phone sleep, it sometimes either turns off or freezes, I need to take the battery out to boot it again. Basically, something is up - and it's making no sense. My phone is working in slow motion with no mobile data/network after drying out water damage, and flashing new ROM's or ODIN to stock didn't fix anything. I checked APN's, I checked kernel speeds (when it was still on AOKP, right now stock), I checked mobile data on and off, nothing is working. On the off chance I do get lucky and have data + network, I try to make a call and both of them vanish.
I don't think I'll get any help bringing this to ATT cause the indicator on the phone itself is pink, so does anybody here have any ideas on what the heck to do? Being that the issues persist whether I'm rooted or not, custom rom or stock, I believe it's a hardware issue - right?

Yep. Most likely. A trip to repair will most likely be required.
The most common error is trying the phone out after it gets wet.
Best to do is immediately take out the battery, and use the rice, desiccant, blow dryer, whatever method right then.
After a few days of sitting in the rice or silica gel packs (in a sealed bag) THEN try powering it up.
Those first seconds of powered up state with the moisture present are the most damaging.

The best thing to do when a phone gets wet is to immediately disassemble it and clean everything with a high grade isopropyl alcohol. That will get all the moisture out and remobe any corrosion on the boards. I would still take it apart if I were you and let it dry completely for about a day. It may bring it back to life. There may be some water hanging in the antenna wire plug or in the radio itself. Watch some youtube videos on the the disassembly and go slow.

[SOLVED] Black Screen Issue

Hi. I am not sure this is the BSOD problem that others have had.
I bought a second hand i747. It came with 4.3. It will work fine for a few minutes when first turned on, then the screen will go dark. The menu and back buttons stay lit, and the touchscreen still works, the LCD just cuts off.
If I hit the power button, it sleeps the phone. When I hit again, the screen will come on, but only for about 5 seconds, then it's black again. Everything works, just black screen.
Is it possible for it to overheat or something? It doesn't feel hot at all, but if I turn it off and leave it for awhile, it will again work for about 2-3 minutes, then only about 5 seconds at a time again.
I swapped batteries, and it's the same. The battery had pink on it. I opened it up, and none of the other stickers showed water exposure, and the board itself was clean.
It has stock 4.3, and is not rooted.
I did go to phone settings and turned off the "darken screen during calls" checkbox.
I am wondering if the proximity sensor heats up and shuts the screen off. Grasping at straws I suppose.
Any idea of how to fix this?
Thanks

Perhaps a bad capacitor in the digitizer/lcd assembly? My TV had an issue with a bad capacitor that would cause the screen to blank out after a few minutes???
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

I'll try swapping boards in it later, and maybe at least narrow down if it's the board or the screen assembly. I have an extra proximity sensor I could swap, but it doesn't seem like it's that to me.
thanks, will post more after the board swap

Update: I switched boards (different carriers), and I could not replicate the problem in either phone. I had hoped that would show that either the board or the LCD assembly was bad, but I didn't learn anything useful either way.
I put the boards back in their respective bodies. It still happens now, but not as often. It also appears to be totally random. I did switch batteries in the problem phone, and it doesn't seem as bad. I will try another battery switch and see if that helps it more.
When the screen goes dark, the menu and back buttons are lit. When it went out last night, I could see that there was still some faint background light that I can't see in the day. I pulled up Youtube and did a video, and when the screen went dark, I could still see movement, but couldn't make anything out. So, the phone is still going in the background.
If I push the power button, it sleeps, then push it again, and it wakes up just fine. Sometimes I have to do that 4 or 5 times for the screen to stay on. Sometimes it goes dark after 10 minutes of use, sometimes a half hour, sometimes just a few.
Any help is appreciated.

Well, right before throwing the phone into the wall, I noticed a partially removed liquid exposure indicator. I pulled the phone apart to check the motherboard.
In the process of taking it apart, I forgot to take out the SD card. In so doing, it pulled the sim/sd card module off the motherboard. Low and behold, there was a very light corrosive glaze in a few spots under the module.
So, I got out the 99% IPA, and a toothbrush, and cleaned the whole entire board. Since then, it seems to be working fine.
I don't know exactly what part getting cleaned fixed it, because I just cleaned the whole board.
Anyways, maybe that'll help someone with inexplicable issues downstream.

Thanks for following up with how you fixed the problem. In retrospect, water damage makes sense.
I dropped a Captivate into an ice chest full of melted water last year. I immediately pulled it out and the phone was mostly okay for a while but then the microphone didn't seem to work so well and occasionally the right third of the screen wouldn't respond to touch until I cycled the screen on and off. The water damage sticker and phone interior showed no signs of water.
I will probably sell the old captivate but with full diclosure about the history. Would have been nice if the seller had done the same for you.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app

Thanks, I should have thought of it sooner, but it didn't seem to have any signs of water damage otherwise.
I ordered the 99% IPA online, because I couldn't find any locally. It works wonders with previously wet boards. You might be able to bring it back.

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.