Develop Bugs

[Q] GPS use forces reboots. Help?

I have been having a nagging problem w/ my DInc ever since I was stock w/ 2.1.
When I use the GPS w/ Google maps, my phone will randomly reboot.
I've tried various kernels, various 2.2 ROMS, tried underclocking / managing temperatures and continue to be plagued w/ this issue.
My current setup is:
Rooted, S-Off, Virtous ROM 2.6, Adrynalyne's Virtuous Custom Kernel, 2.15.00.07.28 radio
It is rock solid with GPS off. As soon as I enable GPS and start navigating somewhere, it's only a matter of time before it reboots. Sometimes it reboots after 1 minute - other times 20 minutes. No rhyme or reason to the length of time before reboot.
I've been hoping that the latest kernels, radio, etc would alleviate this problem, but I'm about at my wits end and ready to just un-root, go back to stock, and try my luck w/ a replacement from VZW.
Anybody have any troubleshooting tips that I can try before I go the replacement route?
UPDATE: Took phone into VZW while it was doing a reboot. They immediately put in a refurb order for me. Replacement phone has been absolutely rock solid for a few days now. Thanks for your help in convincing me it was a hardware issue.

Idea
margelef said:
Anybody have any troubleshooting tips that I can try before I go the replacement route?
Click to expand...
Click to collapse
What's the temperature of your phone at the point it reboots (or comes out of its reboot).

jdmba said:
What's the temperature of your phone at the point it reboots (or comes out of its reboot).
Click to expand...
Click to collapse
Good question, I've never actually recorded the temperature after the reboot (I obviously can't know what the temp was *before* the reboot)
I have, however, used SetCPU with a profile that should underclock (and throw an event notification) if the phone gets above around 43 degrees celsius. I've never actually gotten that notification, though. So either the phone isn't actually getting that hot, or it's rebooting before SetCPU can kick in and pop up the notification.
I'll GPS on the way home tonight and after the inevitable reboot, I'll take a look at what the temperature reading is.

...
Great. Of course, my question was one of experience and not randomness. I am expecting to hear something back from you along the lines of 43c+. If you are at 47c or 48c then its a no brainer.
Bad radios (not the 2.15.xxx software; the physical hardware) are a documented issue with early early early DINC's. They are faulty and they start trying REAL HARD to get their signal, at which point the DINC overheats and reboots.
I returned my first DINC (I am on #3) as it would superheat to 43c (without being in actual use ... temp would just climb and climb) and then enter a reboot loop.

jdmba said:
Bad radios (not the 2.15.xxx software; the physical hardware) are a documented issue with early early early DINC's. They are faulty and they start trying REAL HARD to get their signal, at which point the DINC overheats and reboots.
I returned my first DINC (I am on #3) as it would superheat to 43c (without being in actual use ... temp would just climb and climb) and then enter a reboot loop.
Click to expand...
Click to collapse
Other than having SetCPU do an "Audible Alert" if it hits a certain temperature, is there any sort of diagnostic logging that I can do to help monitor the temperature?
I have used System Panel to show CPU/usage history, but I have not noticed a spike in the CPU right before the reboots in the history view.
This is a release-day unit, so it would have been in the first batch of DIncs. You reference a documented issue on the early batch of phones...do you have a link to something that I can reference if I take this to VZW for a replacement?

Not any more
At the time when this was big news you could find postings, but no admissions from VZW if that's what you want. I think you overestimate the amount of difficulty VZW is going to give you. Sure, a level 1 tech may get very very very annoying by asking you if you pulled the battery and if you are running "advanced task killer" (I guarantee the latter actually), but you should just come up with the answer you know they want, until they agree to pass you up the chain. At the second level, they don't ask those questions (case in point: when I went to return DINC # 2 because it was shipped to me with a pre-blown speaker; the tier 1 rep actually asked me if I pulled the battery and did a reboot. Tier 2 rep apologized when I told him that).
Anyway, if you have one of these bad initial batch phones (as I did), I doubt any software solution is going to help you. In fact, it will hurt. If your phone has a faulty radio or is overheating after a few minutes of GPS, you probably want to know that, rather than mask it.
Turn off your protections, run the GPS, and see if you are hitting 43c+ (I believe 48c is the absolute highest level the Incredible will actually go before shutting down to save itself). If you are getting that hot, you simply have a bad phone.
EDIT: Whoops - missed your question. I use BATTERY INDICATOR (Free) from the market to show my battery strength as a number. It also shows the temperature when you slide down the top menu bar:
http://www.appbrain.com/app/com.darshancomputing.BatteryIndicator

Well, took all of 5 minutes of gps'ing before my phone started rebooting. It rebooted, I opened System Panel and the temperature was 35.7. Then it rebooted again. I shut off gps, went into System Panel and temp was 36.1. With the gps now off, the reboots stopped.

Hmmmm
Honestly, I have to turn the reigns over to someone else. I am still thinking bad radio (search out Incredible random reboot) as the source regardless of heat, but heat would have been the easier answer. My first DINC would also reboot randomly at the office (where it is sufficiently cool all the time).

It's assuredly hardware failure.
In my case, it wasn't related to temperature. Anything that taxed the radio or cpu triggered a reboot and/or boot loop. Even batch operations in Titanium Backup would render the phone unusable.

najaboy said:
It's assuredly hardware failure.
Click to expand...
Click to collapse
You are probably correct.
I reverted back to unrooted stock 2.1 last night. Did not install ANY applications whatsoever. This morning, used Google Navigation on my way to work and the phone rebooted about 3 minutes into my drive.
What's interesting now is that my phone is telling me that it's up to date and there are no updates available. I wonder if VZW has pulled the 2.2 OTA because of the battery drain issues. It'll be interesting to see when I go into VZW for a replacement phone if they make me go through the 2.2 upgrade or if they'll just swap out the phone.

[Q] overclocking damages hardware but what if i only overclocked when needed

Weather it was ondemond or just putting clockspeed up when needed will it still damage hardware?

It could yes. With oc you just never know.

Really it doesn't matter. You're not going to mess up your phone overclocking it. While it's technically possible, your phone will kp and restart before it causes any permanent harm to itself. If your phone isn't boot looping over and over, you're at a frequency that's probably safe to run at for the long term.
Sent from my R800x using XDA App

You're not going to mess up your phone overclocking it.
Click to expand...
Click to collapse
Unexperienced people still can mess it up !
It's quite easy if you do not only raise the clock, as also the voltage !
Condensers and such parts aren't long living parts.
Though that you rly need to want it, till you can mess it up...
But first of all, read, read and again read.
Still it's like the Tegra promotes itself, naturally the CPU needs to have such a function, programming APPs will be quite hard...

[Q] Kernel - phone problem ?

Hy guys I have seen on a noob guide that I can see my phone cpu "stats".
This tells me is my phone a powerfull machine or a bad brick.
So I have installed the faux kernel and with root explorer I came to this t3_variant
/sys/kernel/debug/t3_variant
If your cpu_process_id=
"0"- Sorry, but your in for a world of hurt. I'd recommend only trying out his mainline edition, nothing else.
"1"- Well, you''ll do just fine, but it still sorta shaky. Don't think about overclocking though, unless you're on a beta or VF version
"2"- Knock yourself Out! ;p
"3"- Lock that phone in Fort Knox and, if you see faux lurking around your house, then just run . Jokes aside, your phone can do ANYTHING.
Click to expand...
Click to collapse
This is a quote from a Noob Guide - here.
Mine cpu_process_id=0. Does this mean I bought 4500kn (597.32€ - Yes that's the price of HOX in Croatia) brick?
I have problems with battery he shuts down sometimes more like often, is he really that bad and I am angry right now cause I think I bought bad and expensive phone?!

If you need more info I will be glad to post just someone help me please.

LOL, those cpu variants are to be ignored. They are for hard core overclockers.
It has nothing to do with battery life and you do not own a phone shaped brick. I paid the same amount for my HOX.

Well can you tell me why does he act strange all the time. He just shuts down but he doesn't do that when he is on charger. I think I have some serious power issue. I'will give you all logs you ask and all screenshots just help please.

You might want to try another kernel and do a clean reflash of rom.
Give me the kernel reboot log from /proc/last_kmsg.

No need I think I solved the problem. I have now just moved the governor to interactive witch was default "ondemand". He didn't went off for like 6 hours witch is a record and battery is still 50% can't believe. I know I am noob sry for that

You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.

faiz02 said:
You might wanna try sense roms as well. You wouldnt be facing any random reboots issue.
Click to expand...
Click to collapse
All those random reboots were on stock jb xD

Oh OK,
Case closed.

[Q] Galaxy S3 no warning crash, not SDS?

Hi Guys,
My galaxy S3 , SGH-I747M (d2can) is crashing regularly with no warning. I'll give you the symptoms as best I can.
My phone dies only when I'm using it, not when it's in sleep mode. it doesn't have to be a very power-hungry task, though the frequency of the crashes increases when I multitask. There is no lag on the task I'm performing when it crashes, it just looks like the screen has timed out. When I go to restart it right away, I usually only get to the samsung logo, about 6-10 seconds after it boots up. The likelihood that it will stay on after a crash increases the longer I wait with it off after the crash, 30 minutes is usually enough, though pulling the battery seems to help it boot up as well. The battery is not hot when I feel it, it's not even warmer than room temperature which I thought was unusual.
This tends to happen once every two days now
I tried eMMC check and it came back clear.
My phone was rooted shortly after I got it, though the crashes happened even before I rooted it. Just not as frequently, but I also had no apps installed at the time. limiting the background processes does nothing.
Any thoughts? I'm kind of stumped.

This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.

audit13 said:
This forum is for the d2lte, d2att, and d2can. What is the model for the s3 d2vl? Let us know and we'll try to help.
Click to expand...
Click to collapse
It's the S3 SGH-I747M, which I believe is d2can.

Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?

audit13 said:
Okay. Your original post mentioned the d2vl.
Are you running a custom ROM? Does it do this on a stock ROM?
Click to expand...
Click to collapse
it's all stock. I just did cf autoroot and twrp. This problem started even before I rooted it.

Sounds like a hardware problem since the issue has always been present.

Definitely seems like a hardware issue. If you still have a warranty, you'll want to get it replaced ASAP (usually the warranty is a year or longer, and some carriers don't care if you've flashed your phone or not). No amount of tweaking will be able to get that thing running properly, most likely.

Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.

jdezwaan91 said:
Sadly it's not under warranty. It doesn't sound like I have any other options than to scrap it. Is it possible to quarantine the bad sector so I can keep using it?
Thanks for all your help btw.
Click to expand...
Click to collapse
Not unless it was definitely a RAM issue and you had some sort of memory dump that shows exactly when it crashes, and even then, you'd have to manually add things to the kernel to stop it from ever accessing that sector.
It's incredibly hard to do on Linux even, never mind on Android.
You could try undervolting + running different I/O Schedulers and Governors, but I don't know how far that'll get you, honestly.

nexus 5x bootloop and random down solution

Hi.
Finally I have found that solution.
It is to do aging cpu and gpu and wifi ap.
Through using stress test app, you can save your nexus 5x device in easy as if I had.
Of course I recommend you not root and update 2017 March update.
I have attached my device's running time capture image.

I thought the bootloop issues were found to be due to a manufacturing defect on the boards. Soldering specifically​, with about 10% of devices
Sent from my Nexus 5X using Tapatalk

You can think soldering for the reason of bootloop. But in manufacturing soldering problem does not happen to many devices. If such issue occurs, it will be rare case. And its not wrong development.
Voltage down is easily happened to old device not only mobile but also pc.
Many korean users also think soldering problem. It is sad.
I would like to say to a lot users like this. Study or search voltage down and device or pc shutdown or reboot. And aging makes high stability especially about high clock related to lower voltage or flat voltage degree.

The reason is good stress test with youtube on than gaming or watching video or web surfing is the stress test does not stop aging cpu,gpu and wifi ap.
So trust me. Unfornatedly i have reboot today. I will attach screenshot for running time of device periodly.
Just do try my solution. It is broadly spread way at pc. It works about mobile.

choijuho78 said:
Hi.
Finally I have found that solution.
It is to do aging cpu and gpu and wifi ap.
Through using stress test app, you can save your nexus 5x device in easy as if I had.
Of course I recommend you not root and update 2017 March update.
I have attached my device's running time capture image.
Click to expand...
Click to collapse
How to use any stress test app IF my device never go after the google logo anymore??

Put finger on fingerprint sensor unit when you try boot. When you keep that even if boot fails many times, you will succeed to make dead device boot.

And added screenshot for running time of my nexus 5x after aging

It's there anyone who can make sense of this post?
The OP is​ extremely difficult to understand. I still don't understand what the solution exactly is even after reading about ten times.
Can you at least describe what you did?
Maybe tell us the steps you took to achieve the result so people can try for them selves.

Aging cpu and gpu and ap, it is to make chip bear heat for lower voltage because our nexus 5x are old and old things.
You might use dryer to back of phone in order to make device very warmer for the reason that soldering problem.
It looks like your solution. But as if a lot users used hand dryer who had experience, it is happening too.
Basically we must know aging mcu(cpu) makes cpu bear heat very well in condition of lower voltage because time passed for long time like one year or more than one year.
So how to make device aging or aged?
At pc, after overclock users always use prime 95 or such programs can make cpu aging.
So I had recommended users will uses stress test app to make their device aging.
At least a few hours aging needed. I recommend a couple of days for aging.
Voltage regulater exist, but it became to work in correct after a few years. I have tried that experiment for my device. Ot was successful.
If you believe my saying after thid explanation, just do run stress test for long time or periodly repeatidly.

peltus said:
It's there anyone who can make sense of this post?
The OP is​ extremely difficult to understand. I still don't understand what the solution exactly is even after reading about ten times.
Can you at least describe what you did?
Maybe tell us the steps you took to achieve the result so people can try for them selves.
Click to expand...
Click to collapse
If I understand correctly, OP tries to show a method, which purpose is to check whether CPU soldering is going to become loose and lead the phone to endless bootloop.
He/she describes that stress testing the CPU worns it out a lot faster than everyday usage and then explains that people, who overclock their CPUs in PCs, are checking if the CPU can run on such core clock in a time trial, so we can also do such test (just without overclocking).
So:
If you want to check whether your phone is going to die soon, run a stress test. If the device doesn't restart during that test, you're good to go, else brace yourself.
But I think this is not a good method, beacuse if the SoC temperature will rise up to 105 Celsius degrees, the device will cut current flowing to the CPU to prevent damage (that's what thermal throttling is for).
To my mind, it is not a solution, this is rather a test for checking devices' long-term durability and reliability.

No. It is solution if expired warranty period.
You have to run stress test again even though device go shutdown during stress test.
At least a few days needed running stress test app.
Then your device will come back healthy.

przemcio510 said:
If I understand correctly, OP tries to show a method, which purpose is to check whether CPU soldering is going to become loose and lead the phone to endless bootloop.
He/she describes that stress testing the CPU worns it out a lot faster than everyday usage and then explains that people, who overclock their CPUs in PCs, are checking if the CPU can run on such core clock in a time trial, so we can also do such test (just without overclocking).
So:
If you want to check whether your phone is going to die soon, run a stress test. If the device doesn't restart during that test, you're good to go, else brace yourself.
But I think this is not a good method, beacuse if the SoC temperature will rise up to 105 Celsius degrees, the device will cut current flowing to the CPU to prevent damage (that's what thermal throttling is for).
To my mind, it is not a solution, this is rather a test for checking devices' long-term durability and reliability.
Click to expand...
Click to collapse
"If you want to check whether your phone is going to die soon, run a stress test. If the device doesn't restart during that test, you're good to go, else brace yourself." he trying to say that to fix hardware bootloop (maybe caused by soldering issue), often you have to stress test your cpu, so it won't go in hardware bootlooop issue.

choijuho78 said:
Hi.
Finally I have found that solution.
It is to do aging cpu and gpu and wifi ap.
Through using stress test app, you can save your nexus 5x device in easy as if I had.
Of course I recommend you not root and update 2017 March update.
I have attached my device's running time capture image.
Click to expand...
Click to collapse
OMG MAN. YOU ARE A LIFE SAVER. I JUST TRIED AND FIXED MY BROTHER'S 5X. THANK YOU MAN. I LOVE YOU.
My brother's phone went into bootloop today and I managed to get it to boot. Some days back I read your post and remembered this, so I quickly downloaded the stress test app and ran it. It has been 30 minutes since the device has been turned on. It hasn't frozen and did not reboot and go into bootloop again. I hope I can permanently fix this. Thank you sir you are a life saver. More people should see this thread and try this method.

choijuho78 said:
No. It is solution if expired warranty period.
You have to run stress test again even though device go shutdown during stress test.
At least a few days needed running stress test app.
Then your device will come back healthy.
Click to expand...
Click to collapse
Can you tell me which app did you use for the stress test?
Sent from my Nexus 5X using Tapatalk

But how to run stress test if we're in hardware bootloop? @choijuho78

Read replies

InterrtuptoR said:
Can you tell me which app did you use for the stress test?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
same question here...
which app ?

This thread is bull**** and should be closed.

Hi, @choijuho78! Nexus 5X bootloops are really a nightmare! I don't mean to offend you, but some users are interested in your method. So, if you want, I can help you re-write your first post so that it is clearer for everyone. Maybe, some links to important programs, apps or procedures could be included to make it clearer. If you think I can help you somehow, feel free to answer this post or PM me. Thanks!

I used StabilityTest app.
And have run stress test in the app. You can repost for other users.