Related
Hi people,
I have a question, I've been reading these forums a lot but now I have a problem that I don't really understand:
My HTC Trinity that has served me well does not want to boot at normal temeratures 21C - 70F. The akward thing is that if I put it in the freezer for 10 mins, it starts working , doesn't get hot. As it reaches 20+C it freezez or doesn't want to wake up from sleep anymore.
Any ideas as to why this happens it's clearly a hardware fail but what part of it ?
any help would be greatly appreciated.
Maybe it's the battery......did you tried it with other batteries....?
It maybe that you have a poor connection within the phone being affected by thermal expansion. Might also be moisture condensation in your phone (made worse if repeatedly placed in and out of a freezer) that requires drying out.
hfzarx said:
Maybe it's the battery......did you tried it with other batteries....?
Click to expand...
Click to collapse
I'm guessing it's not the battery as when I put it in the freezer I take the battery out. Also, while the phone is off the battery charges normally, without heating up or anything.
The theory of a faulty contact makes more sense but then which one ? I do now have a star shaped screw driver with me (I'm travelling for the moment) but I'll try and open the phone once I get back to a more tinkering friendly environment.
I have put it since in a drawer and it has been waiting for me quietly. In the mean time I bought a Sony Xperia X1 which is an excellent phone. I would still try to fix my trinity, I'd use it exclusively as a GPS if it works.
Any other theories as to why this might happen or what should I do to fix it?
Thanks guys for the useful replies !
When issue occurs will it power up plugged into charger?
As BundyR stated there is a poor connection somewhere. Also known as a "cold solder joint". The trick will be having device apart but still being able to power it up at the same time and start poking around with a toothpick and a magnifying glass starting with the battery contacts and moving on from there.
good day.
Random shut down solution! At least for me.
My phone shuts down pretty much 2-5 times a day since i got it. No matter what I do to it. But I tried the app, load monitor and enabled WAKE LOCK and my phone hasnt rebooted in 4 days!
Anyone else had similar experience.
Sent from my SAMSUNG-SGH-I897 using XDA App
Umm, not meant in an asshat way at all man, but your real solution is to take that sucker back. I wouldn't put up with that at all. Bad phone. Just my opinion.
From a phone on an app
I have to agree with the post above mine. I believe it's a hardware issue and that you should return it for another one. I have two captivates and neither I've of them have ever had the random shutdown issue.
Truth is, the phone is bad. Ask for a warranty replacement. I went through 2 phones until I got a good one with no issues. A perfectly good working phone should never randomly shut off as mine were doing before (4-10 times a day) Even setting Set-CPU to 1000mhz 100% of the time didn't fix the other phones I had. Hell, even leaving the screen on the entire time one of them still shut off once.
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Did you have set cpu installed? That's what happened to me after installing set cpu. Sometimes it would lock up after the screen went off & sometimes it would just reboot randomly. I got around this by setting the min clock speed to 200mhz. I think set cpu sometimes undervolts the cpu when scaling especially at 100mhz & at 1000mhz when the screen is off. If it did that stock then I would definitely return that pos! Wake lock will kill your battery life.
Sent from my SAMSUNG-SGH-I897 using XDA App
Well we will see. I was in the process of a rma and just got the phone last night.
I see if the new one has any issues. By the way this will be my 4 th phone(3 through the first month, this one through rma). So the get another phone idea kind of sucks.
Just a curser glance at the back of the rma phone and I can see its different. So maybe I'll get lucky on it.
Sent from my SAMSUNG-SGH-I897 using XDA App
. .
Same here, I'm in Australia, I bought the phone from the US, It used to shutdown 3 - 5 times a day, especially when it's fully charged. Wiped the phone (Internal and external) and now it's solid stable. no special apps or settings or whatsoever. It's a little bit weird though.
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
I leave mine plugged in all the time overnight and it has Never booted off
Sent from my SAMSUNG-SGH-I897 using Tapatalk
galaxyjeff said:
I think the problem may be from the phones overcharging. Mine was brand new and I left it on the charger overnight then took it off the charger in the morning and when I came home from work it was powered off. It may be a safety feature built into the phone and not a defect. I had it happen to me twice when I didn't take it to work with me after charging it all night the night before.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
I thought the same, but last night I forgot it on the charger with no problems at all, No shutdowns... Strange...
It happens to my Samsung S Vibrant and I *think* I can reliably reproduce the issue, at least on my phone.
Steps:
1. Go to a spot where you know it has failed, for me this is my office because it has bad reception and it seems to only shutdown for me when there is bad reception.
2. Make sure 3G is turned on and open an application that uses data.
3. Wait for the phone to sleep, do not hit the power button or anything to make it sleep (not sure if this step matters)
4. Wait ~30 mins without touching the phone (You can play music with it while this is happening if you want, the music will stop to let you know it's failed)
5. Try to wake up your phone, it is now dead.
I'm not sure this will work for everyone but last night I could reproduce 3 shutdowns in an hour and a half. And reproduced about 7 shutdowns yesterday when my phone only usually shuts down ~2 times a day.
I'm testing out all kinds of software permutations (disabling stuff, installing things like Captivate Keep Alive). Nothing has worked so far, my guess right now is that the problem lies in the Pattern Unlock feature so I have disabled it, I read that on a forum somewhere.
My guess is that if you have too much running in the background it might take up too much cpu or ram so that when the phone tries to come out of sleep it can't get enough CPU power to come out of sleep and therefore gets stuck in a kind of limbo. This theory could then be releated to the SetCPU problem when you set the CPU too low when it sleeps the issue occurs.
Moral of the storey is I have no idea what's going on, but please post if this works or doesn't work. Maybe it will shed some light on the issue, or you can tell me I'm wrong so I can give up. Let me know if you have Pattern Unlock enabled...
Luckily I'm not past the 30 day mark and I'm exchanging for a new Vibrant tonight. Wish me luck!
UPDATE: It's not the fault of Pattern Unlock, just reproduced the issue with it turned off.
UPDATE #2: Got my second Vibrant, just reproduced the issue within 30 mins of getting into work in the morning.
My Captivate used to shut off once every 2 weeks. Now it's doing it 4 times a day. However, I just found this app:
http://uk.androlib.com/android.application.org-bluesteel-cka-qxnim.aspx
Looks promising. I hope this works.
My wife's stock Captivate has been doing this for a week or two (our phones are about 6 weeks old). My rooted Captivate has -not- been doing it. We both have the same "plug it in all night" charging pattern. Hers will be going back shortly.
Jack45 said:
Others have found that the "wake lock fix" has not worked (although it initially seemed promising). If your shutdowns recur, exchange the unit. That's been the only remedy to date.
Click to expand...
Click to collapse
Tha'ts not true.
My phone was working fine. Then I rooted it. Then I started sideloading bunch of apps. Randon shutdown started to happen. I started tracing back and deleted apps one by one. Didn't work. Replacing the phone was out of the question because I live in Canada and bought the AT&T phone cash off a seller.
SOLUTION:
if you have had SetCPU (or overclock app) and had it to anything to your phone, this is what you got to do.
Run the SetCPu again, and make sure that you do Max 200mhz and Min 200mhz.
Reboot the phone.
Then go into SetCPU, disable autodetect. Then uninstall app.
No more random shutdowns.
It is NOT a hardware issue.
I can confirm that the App stops my phone from shutting down.. unfortunately I have to set it to 65% charge for it to work (whereas others can leave it on default 80%).
Found my issue, it was happening when my phone was jumping between the 850 mhz band and the 1900 mhz band. It would freeze and only happen in areas of bad signal. Locked it on to the 850 mhz band and havent had a freeze since.
100 hours of uptime and counting
http://forum.xda-developers.com/showpost.php?p=8612667&postcount=386
I have also heard that some phones experience the issue when fully charged and that putting a wake lock on your phone with captivate keep alive will solve the problem. These are two independant issues.
i'm not really that knowledgeable about how the phone interacts with different bands, but i'm trying to fix this problem as well and i'll try anything. are there any side/adverse affects to locking it onto a single band?
Has anyone tried removing the sim? to see if it still turns off?
The problem im having is when its near full and goes to sleep i need to turn it back on (like it shuts off) but i tried removing the sim and has not had this problem
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
The de-casing was fun, and yet there isn't an obviously damaged component. It was pronounced dead at 6:20 yesterday evening.
R.I.p.
Sent from my SGH-T699 using XDA Premium 4 mobile app
tylik said:
So, there I was, eating dinner while my phone read me a book.* And suddenly, it stopped. Because my phone crashed. And the amount of a boot cycle it can get through before crashing has been decreasing ever since. A complicating factor: when I still thought it was possibly a software issue, I booted into recovery, and attempted to re-flash the OS (currently it's on 10.2.1). It crashed partway through the process.
On the off chance this was a humidity issue (and not having a lot of time to mess with it) I opened up the phone, removed battery, sim, sd and the small screws in the main body of the phone, and left it in a dry well ventillated place. Now it will get as far as the initial "samsung" splash screen the first time I've reinserted the battery, and won't boot at all beside that. (It's possible that the power button was behaving weirdly, but the phone's behavior was generally so erratic that I can't say that with confidence.) Also, sniffing at the keyboard there is ever so faint a smell of burnt electronics... maybe. Maybe just platicizers. (I've noticed a bit of
This is the same phone that had screen issues (assumed to be related to a small amount of water** though subsequent evidence suggested a loose connector as an alternative hypothesis) around the beginning of February. It's been fine ever since, discounting the occasional weird usb connectivity issues that seem to be common with this phone.
I'm pretty happy to take the phone apart, but other than a general decase everything and look for loose connectors or other obvious trouble, I'm not even sure where to begin. (Also, I have about twelve hours to put in an order if I want Amazon to send by a new phone by tomorrow. Which is kind of silly, but this is swiftly and impressively dead. And otherwise it'd be no phone until Tuesday, which wouldn't kill me, but which would annoy me mightily.)
Any thought regarding common problem areas for this phone? I'm hoping to be able to leave the lab early today, which should give me some hours of working time. Well set up for tools, always happy to have things to take apart.
* Text to speech is awesome, once you get used to the robo-voice.
** Really, not a lot - none of the moisure stickers showed anything, and I don't think it got into the main body of the phone.
Click to expand...
Click to collapse
Get a new battery for it....had this issue before and placing new battery in it fixed my bootlooping and not being able to flash or get past samsung screen...the samsung batteries have an overcharge feature which has been known for causing errors such as this...
This was an apparent issue on s7 based on Google search.
I am getting this error message on a s8+ that has never seen water. It's been like this for about a week.
Kinda strange for a phone touted as waterproof.
Correct me if wrong but samsung warranty is voided on water damage?
Anyway to reset this?
Anyone with thoughts?
Sent from my SM-G955U using Tapatalk
I don't think it implies you have water damage. The warning is to prevent you from trying to charge if the port is wet after being exposed to water. You may just have a faulty port.
My first s7 did this and eventually would not charge anymore , and had to get a replacement
Sent from my SM-G955U using Tapatalk
It will wireless charge still.
Normally shows up fire a bit after the phone gets wet. Once it does it will go away.
I've gotten my phone wet all works great.
If you truly haven't gotten the phone wet or take it back because it might have an issue.
If the phone has nevee been wet then there is a problem.
Now if you live In the area where the humidity is high.
The that can trigger it also.
OMG the same thing is happening to my phone I've only had it for about 30 to 40 days-and like yours never seen water and it's giving me that moisture warning it has to be something wrong with these phones they need to give us our money back or replace them
Same thing just popped up on mine. I've had this phone for a week. Granted it's a really humid and rainy day here but this phone hasn't seen a drop of moisture.
Sent from my SM-G955U1 using XDA Free mobile app
Try giving the connector/port a wipe with some isopropyl/rubbing alcohol. This should clear the error.
so I have had this issue for about 2 weeks. the first time....it wouldn't charge. so I waited 3 hours and it still wouldn't charge. I turned my phone off and turned it back on and it worked fine. couple of days later it did the same thing....and then again. then yesterday....it restarted my phone at least 10 times and it was still saying moisture detected. MY PHONE HAS NEVER GOTTEN WET!! I googled and ever since the last mandatory update....alot of ppl are having this issue. so today....again...I can't charge my phone. i called tmobile and they are replacing my phone. i checked the little card inside the SIM card slot and it does NOT show water damage so it is a SYSTEM ISSUE!!! come on samsung!!! first the NOTE 7 issue....now this?! so tomorrow I'm getting a brand new phone being sent to the store and lets see what happens with this cause now I can only use my wireless charger which takes HOURS to fully charge my phone!!!!
Samsung has a hard rule, no repairs for water damage ever. I had to jump through hoops to get a brand new note fixed even after they agreed to fix it, the repair facility tried to not do it, more time in the phone with customer service. Samsung will go out of their way to deny warranty work and make you tell every higher person in the customer service chain your entire story over and over again. Terrible customer service unless you have a lot of patience and a lot of time to sit on hold.
mandyed66 said:
so I have had this issue for about 2 weeks. the first time....it wouldn't charge. so I waited 3 hours and it still wouldn't charge. I turned my phone off and turned it back on and it worked fine. couple of days later it did the same thing....and then again. then yesterday....it restarted my phone at least 10 times and it was still saying moisture detected. MY PHONE HAS NEVER GOTTEN WET!! I googled and ever since the last mandatory update....alot of ppl are having this issue. so today....again...I can't charge my phone. i called tmobile and they are replacing my phone. i checked the little card inside the SIM card slot and it does NOT show water damage so it is a SYSTEM ISSUE!!! come on samsung!!! first the NOTE 7 issue....now this?! so tomorrow I'm getting a brand new phone being sent to the store and lets see what happens with this cause now I can only use my wireless charger which takes HOURS to fully charge my phone!!!!
Click to expand...
Click to collapse
I've had issue with this as well but it's disappeared for the last few weeks not sure why......
Is there any chance that sand could cause the moisture alert? I had the same issue for an entire day, the phone did not get wet, but I live in a very sandy area and figured a grain of sand had triggered the alert. Just curious..
All you need ti do to fix this is plug in the cable then quickly restart phone without taking the charger out and when it comes back on seeconds later its fine
I've also had this problem for the past couple of days. Have had the alert before (phone has never been wet, but I used to live in a humid environment and mostly happened when my finger had been sitting over the connector). Then yesterday it stopped charging - very convenient not having a working phone while moving house and starting a new job /s.
I don't think hacks like rebooting while plugged in are an OK solution; I've never been unable to charge any phone during regular use before!
Reading around the net, Samsung has obviously pushed an update that has either increased the sensitivity of the cut-off, or just has a bug. Perhaps in response to issues with wet phones shorting and causing damage, and want to push warranty claims as user error or damage.
I've had an S3, S4, S6 and now S8; between this and Bixby hijacking my phone and constantly pushing updates to itself my next handset might be a Pixel.
Stifler87 said:
All you need ti do to fix this is plug in the cable then quickly restart phone without taking the charger out and when it comes back on seeconds later its fine
Click to expand...
Click to collapse
This worked for me. Thanks! Going to call T-Mo tomorrow though to get it replaced.
I'm having this issue with my Note 8 that is less than 2 months in use, Samsung is collecting it for repair on Friday and it will 7 to 10 days, phone have Not been exposed to moisture and won't work in the DeX station either, there is clearly a problem with charging ports on several different Samsung devices, fingers crossed it will come back fixed up OK with no more hassle
j_hansen said:
I'm having this issue with my Note 8 that is less than 2 months in use, Samsung is collecting it for repair on Friday and it will 7 to 10 days, phone have Not been exposed to moisture and won't work in the DeX station either, there is clearly a problem with charging ports on several different Samsung devices, fingers crossed it will come back fixed up OK with no more hassle
Click to expand...
Click to collapse
Could be an app causing it or multiple other things as mine just suddenly stopped doing it after an update a long while back.
Another thing was I have it a good rinse and then let it dry my phone on a stand so any water would move down and out.
I've been down all avenues including deleting apps and booting into safe mode that disables 3rd party apps, couple of factory resets and few hard resets from recovery and also have a problem with phone not detecting my brand new DeX, this digs deeper than I want to deal with now so Samsung can fix it since I did nothing wrong, I look after my phones really well, this is my first note to have a problem so I'll give Samsung the chance to put it right without me having a husdyr fit
Hello together,
I have a Z5 (6653) that didn't start anymore and got extremely hot while charging. To be more clear: after connecting the phone to the charger the red LED turned on, then after about 10 seconds later it turned off again. From this moment on the phone's back started to get extremely hot. The source of the heat is about 1cm right and 1 cm down to the back camera (so you can say 1cm diagonal from the camera to the phone middle). Because of this I doubt it has to do with the battery as it should heat the lower two-third and not the upper third of the phone. Maybe the processor is at this place?
I tried to connect the phone in flash mode with the PC and it connected, but disconnected after a few seconds, probably because battery was empty. I repeated this procedure (connecting to charger, disconnecting, reconnecting, connecting to PC) a few days and suddenly the red LED kept on and the phone didn't get hot anymore.
So I charged the phone fully and wanted to start it, but the screen won't turn on anymore. Connecting it to the PC and the Phone drive (MTP) is displayed but empty, because you need to unlock screen. Also I hear the connecting sound of the phone and touch feedback sounds.
I tried the following things:
Xperia Companion Repair
Flashtool flashing newest ROM
Flashtool downgrading to 32.0.A.6.152_R5B (LP ROM)
Nothing helped. Well, the idea it is an hardware issue might be at hand, but maybe there is something else I can try first?
And if it is an Hardware issue, what is the cause? The Display itself? Then why was a single point at the phone back the source of heat and not a large area on the phone front?
A short summary:
Phone gets hot while connected to charger
Battery won't charge (LED indicator turns off after few seconds)
Source of heat is 1cm to the right and down to the back camera; after 2 minutes whole phone is hot and you can't recognize the source
After days of repeating the action (connect to charger, disconnect, connect to PC, connect to charger) it suddenly charged the battery and didn't get hot anymore
Display won't start anymore; still responsive
Tried Xperia Companion Software repair
flashed latest Stock ROM
flashed Lollipop Stock ROM
Phone has locked bootloader and is/was not rooted. I'm grateful for all help!
I guess its a dead screen maybe u droped it and the pins of the screens got ejected from the motherboard.. Ignoring the fact that it was empty of charge and you charged it.
From what i understand that the phone is working but there is no screen.
The best thing u can do is to check a hardware store that is capable of diagnosing the issue.
Im not helping here i know but wanted to share my thoughts..
Gd luck with that.
Thanks for this anyway. But phone didn't drop.
The fact that the phone wasn't charging and got hot instead at the beginning is very irritating. Especially that it wasn't the front but a point at the back near the camera. Is there a way to check if it's a Display issue and not a Mainboard/Processor/other Chip issue?
At least in Germany are a lot of stores that aren't too competent at all. But nobody would tell you, so its very helpful to know as much as possible before going to a store.
I think it might have something to do with the gpu inside the soc? The heat might have burned something inside the mainboard (how hot was it btw, like running intensive apps or even hotter than that?) Another thing that might have happened is the display cable is loose.
I've seen some Z5's screens and they're not that easy to die.
The best thing I can suggest is that you repair it in a trusted shop that lets you observe the repair procedure directly (open the phone, take the parts out, identify the problem).
Good luck with your phone.
colorado48 said:
I think it might have something to do with the gpu inside the soc? The heat might have burned something inside the mainboard (how hot was it btw, like running intensive apps or even hotter than that?) Another thing that might have happened is the display cable is loose.
I've seen some Z5's screens and they're not that easy to die.
The best thing I can suggest is that you repair it in a trusted shop that lets you observe the repair procedure directly (open the phone, take the parts out, identify the problem).
Good luck with your phone.
Click to expand...
Click to collapse
I never played any game so it is hard to compare, but I never had a phone in my hands that got this hot before. You didn't get instantly burned touching the phone but it was already inconvenient hot for your fingers/hand.
There might be some trust able stores to find, but I doubt somebody will let you observe it, not even Apple store does. If you see the trick of how to repair it easy and fast, you might do it yourself next time. And it is also a question of the price. If I can buy a used but totally unharmed Z5 for the same price, why should I let it repair?
As far as I could see in Germany repairing Display starts at 99€ for the Z5. Buying display with adhesive would start at 49€. But if they change the Display and it's still broken you have to pay for the Display and also for the mainboard i.e.