Help: hardware issues with my phone. - Verizon Galaxy Note 4 Q&A, Help & Troubleshooting

So, my phone only boots when it's been in the freezer for about 20 minutes. It will work until it warms up, then freezes.
I tried many batteries. No change. It's almost like if a video card had bad thermal paste/faulty fan. Any ideas?

Boot to recovery and set a timer, if it doesn't freeze then try a new kernel

Related

[Q] Troubleshoot reboots

Hi,
My Desire has a rebooting problem...
If I play a cpu-intensive game like Angry Birds, it will always reboot after a while (gets hot and then reboots). Usually goes into a boot loop and I have to pull the battery.
I've noticed that if I do somewhat intensive tasks while the phone is charging, it also reboots - again this appears heat-related. again, boot loop, and battery pull.
I can put up with these reboots - b/c I can predict when they're going to happen. however,if anyone has ideas about how to prevent apps from overheating the cpu, please let me know...
However, sometimes it's just sitting on the desk in front of me and it reboots. this is much more of a pain. I have a LogCat reader installed but how do I pinpoint the apps causing the reboot in the log? Alternatively, I'm wondering if I leave it plugged into ADB, can that record the reason for a reboot?
Any advice is much appreciated.
I'm on AuraxTSense with an ext2 partition, in case that helps

My G2 will shut itself off - any suggestions?

I'm looking for any ideas for the problem I'm having on my G2. I'm afraid it's a hardware problem and not much I can do about it.
I started having problems after upgrading from CM 7.1 to 7.2, but I don't think it was related to the upgrade. I started having battery draining problems, the phone took forever to get fully charged, and car mode would automatically start sometimes when plugging up or unplugging the charger. I cleaned the usb port with alcohol (with battery removed), let dry, and restarted. Now I don't have the car mode problem and the battery problem is somewhat better.
My problem now is that the phone will just die when I'm using it. Usually when I'm using the browser. I'll be scrolling on a page and the phone will just turn itself off. Like the battery died. I can turn the phone back on and it will start up, get all the way started back up, but while it is still loading the home screen widgets, it will go off again. I can repeat this several times. The only way to recover is to plug in the charger. I don't have to hit the power button again, just plugging in the charger will start up recovery mode automatically, I'll choose reboot and the phone will start normally then and stay on.
The phone never dies when I'm not using it. I'll carry it all day, making phone calls on and off, and it'll stay on with no problem. Mostly, I only have the problem when using the browser. Also had the problem while using my newsreader. Once during playing a game. But if I start up browsing the internet, it doesn't take long before it will turn itself off. A matter of a couple of minutes. I don't have the problem with reading emails with K9. Don't have a problem in downloading from the internet such as podcasts. Don't have a problem in sending text messages. Don't recall it shutting down while using the Facebook app. After putting up with this for a week, some troubleshooting and observations.
I never have this problem if the charger is plugged in. Only when it is running fully from the battery.
I've tried swapping to a different battery.
Turned down the overclocking with no difference.
I've changed to other recoveries, CM 7.2, CM 7.1, a CM 7.1 that I was running in May. No difference.
I've swapped memory cards.
I've reset battery stats.
No difference if running on wifi or just data.
Clearing caches made no difference.
So, I start thinking it must be a hardware problem, but then why does it only crop up when internet browsing. Must be power related since plugging in the charger makes it go away, but why does it not have a problem with using the phone in other ways?
Any suggestions on what I could try?
You could try to see if there is too much voltage drop when you start something power-hungry. Use a battery voltage logger and post the results. Start logging, let the phoneidle for a minute and then start browsing. Even if the phone shut off, the log should still be there after rebooting.
Thanks for the idea. I can't locate a logger that looks like it would work. It would have to capture a quick drop in voltage that is momentary. This problem happens even on a full battery and when the phone come back on (either momentarily or after a recovery reboot) the battery level is unchanged.
You might try as well an other way: first idle, then gradually step up to a more power hungry app to see when the problem actually happens. I have no other ideas...
Make sure that you dont have any contact with the battery and the door.
Normally batteries are covered with an aluminum wrap, and can cause short-cuts with the phone itself.
I searched it for a while with the galilio batteries.
You can try to put some saranhwrap around the battery.
I have the same problem with two different batteries. But I'm ready to try that too.
Battery graph
So here's a graph of my battery status. Long time to charge to 100%. Discharges pretty rapidly. Each downturn ends in the phone turning itself off. Notice that at 7:30 today, it turned itself off, I did a recovery reboot, then noticed it wasn't charging very well (green line turns to blue but doesn't increase), then I did a manual reboot and when the phone restarted, it showed the battery was at 100% charge (from about 60% before the reboot).
What do you think - hardware or software?
oVeRdOsE. said:
Make sure that you dont have any contact with the battery and the door.
Normally batteries are covered with an aluminum wrap, and can cause short-cuts with the phone itself.
I searched it for a while with the galilio batteries.
You can try to put some saranhwrap around the battery.
Click to expand...
Click to collapse
Well, I just took the cover off for awhile and tried it. Played crosswords (Shortz) for awhile with no problems. Started my newsreader (Newsrob) and it shut itself off in about 15 seconds. So, no short to the battery cover.
Same thing is happening to me. I use poweramp or the browser and the G2 just shuts off. Then I restart it and it tells me that the battery is low. Once I shut it down and reboot in recovery and wipe the battery cache it's back to it's normal battery level. I disabled data and set my phone for 2G networks only and it didn't shut off after. I'm assuming this is a wireless issue? I'm running mimicry 1.3.0 on my G2.
Had the same problem. Swapped out batteries and problem gone.
Sent from my HTC Vision using xda app-developers app
Did you swap the battery and immediately have no further problems? I tried swapping my battery already and still have the same problem.

Random Reboots (Unable to receive call, after reboot loop at boot loader) SOLVED

After having headache with this problem for last one month and lost hours of testing, i finally found a problem so lets explain symptoms, maybe it will help someone.
I am using CM since first version and as all nightly version have some bugs i had them as well. So i had random reboot from time to time and i thought it's just CM bugs.
For last 1 month reboots happen most often and always when i receive or make a call.
Phone just reboot and loop at boot loader. After removing battery for few seconds phone can normally boot.
3 days ago phone started to reboot even with some heavier app's but never if i disable network. Reboots start to happen even if phone is in my pocked and i exit elevator (drop network and get again).
I tried clean installation of CM12.1, Clean installation of CM13, Wiping internal storage, Clean installation of Cloudy ROM, Removing SIM card, removing SD card i even moved back to stock ROM.
Installed more then 30 app's for monitoring everything and noting show any error, problem etc. While doing all this, i realized that this problems never happen when phone is at charger. Again, installation of 20 apps for battery calibration, voltage monitoring, logs etc. and non of them showed any problem.
Battery was regullary fully charged but noticed that it happen only with heavier usage (have call, copy bigger file, start game).
After doing that tests for entire day, phone refused to pass boot loader with battery but boot normally with charger.
So i purshesed new battery last night, phone booted normally, there is no reboots or any issue at all. Now i can compare that new battery is better since it lost only 1% of battery over the night but old battery didnt show up any problems at all. It's normally to not be that good after 1 year of usage but I didnt had any drainings, it was regularry charged etc.
So if you have similiar problem, to go to some service where you can try with new battery before buying one.
I have the exact same problem .
It driving me crazy! I will try to get new one, and reply as soon as possible ! I hope it will work.
the phone just showed me that The battery that I was using it for one year is fake -_-
Yep, same issues, phone was rebooting sometimes (at the begin, only a few reboots, only during the launch of "big" activities like GPS, or photos) then a few weeks later
I needed to connect it to the charger otherwise, after a few seconds, the phone used to reboot in loop... Until it dies...
Buying a new battery resolved all the issues, no more reboots at all

Overheating issues with fulmics 5.3: phone reboots

I have been using fulmics for a long time now. I live somewhere where the temperature is always something around 17-25 degrees on summer and never had an overheating problem. Now, I'm on holiday somewhere hotter (canary islands) and the 30-ish temperatures are causing my phone to reboot if i take a couple of pictures or if I open apps like pokemon go. I think this has something g to do with heat because back at the hotel, I don't have these issues at all. Even when i perform the same tasks at night, the phone does not reboot.
Now, I can't remember if I chose the stock or the the thermal throttle values upon installation but I'd like to ask, which would be the best option to avoid this issue and also, any other advice you could give in order to mitigate this issue. I asked on the fulmics thread over at xda but the mods locked it because some asshole didn't stop asking the dev for Etas. Screw that guy.
Any help would be welcome! Thanks!
Hi, there will probably be an update to fulmics 6.0 which should solve overheating problems. I'd recommend for you to move to Cloudy G3 2.5 or XenonHD with aCC kernel just for now.
I also have problems with heating. When the phone is at direct sunlight for some time it become irresponsible. I mean it don't reboot but message pop up "system ui stopped ....." and screen lock. I wonder if fulmics ROM is the reason for that. As far as I remember upon installation I choose stock settings, kernel.
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
My G2 acted like this when the battery died. Its a sure sign
GFXi0N said:
Update! : This morning, I went out and the phone got literally unusable. Constant bootloops. Sometimes getting to see the wallpaper but after a couple of seconds, before the whole system boots, rebooting again. The temperature today is quite lower than the previous days and the phone sure didn't feel that hot on the back (power button is my thermometer). Back at the hotel, I tried to backup in order to wipe data and see if it's a data corruption issue. I had to try a couple of times to backup because the phone would reboot half way. I finally made it to the point where I reinstall the rom, before wiping, and the phone would reboot while fulmics was getting installed. I then remembered reading somewhere about the possibility of being a fubar battery, so I plugged the thing to the wall: instant fix. No more reboots. I even restored the backup without any reboots. Booted the rom perfectly. Let it load. Open pokemon go, see it works. Unplug from the wall and in less than twenty seconds: reboot.
Now, I'm on twrp without performing any task and saw my phone lose 30% of the battery in 45 minutes just sitting still. So yes, my bet is on a broken battery.
Whaddayathink?
Click to expand...
Click to collapse

SM-G920P Random reboots

Hello everyone. I have a problem with one of my phones. This galaxy S6 started to reboot randomly. You can see how it reboots in the video below. The CPU temps are ok, i tested it in heavy load (usually stays at 60-80C in benchmarks, and below 60C under normal use, idle temps are 30-25). It doesn't crash specifically in heavy load, it can happen even in idle. I have tried different stock roms, full wipe of internal sd card, custom roms and nothing helped. Usually in custom ROMs the phone random reboots not so often. This phone is not water damaged and has not been dropped. Is that a battery failure or what it can be ??
Any help will be appreciated.
Video 1
I forgot to mention, reboots happen more often when battery is under 40%.
I have this problem too, I'm not sure if this will bump the thread, but if you ever solved this problem, I would love to hear how! I got mine used to idk the history. I rooted it as soon as I got it and the problem didn't start til a month or so later. I have tried two different roms and both seem to have the problem. It started with just the occasional crash when memory was loaded. Then one day it started crashing every couple minutes so I tried to restore from TWRP backup. The restore failed and it could no longer boot into the OS. I then flashed a new rom and it is currently trying to configure it (the flash worked) but it is still crashing randomly. It seems to happen every time the screen times out as well as randomly.

Categories

Resources