hi just a question - Droid Incredible Q&A, Help & Troubleshooting

what would cause my droid incredible to shut down on its own

ICEMANN42 said:
what would cause my droid incredible to shut down on its own
Click to expand...
Click to collapse
Many different things, actually. Unfortunately, it's impossible to provide a specific answer to such a vague question.

well its was just random shutdowns..........but all is well now re-flashed and seems to be fine now.

Best thing is to download a log recorder from the market and send the system log (right after it crashes and reboots) to either someone here or the developer of the rom. They can sometimes help you better with that kind of info.

Mithos der Held said:
Best thing is to download a log recorder from the market and send the system log (right after it crashes and reboots) to either someone here or the developer of the rom. They can sometimes help you better with that kind of info.
Click to expand...
Click to collapse
Thanks for the info!

I know that it's probably too late now but were you overclocking? My phone gets unstable above 1100 MHz and it reboots a lot. I leave it at 1100 maximum.

Related

[Q] reboot random

Hello,
I had random reboot before with my leedroid 2.3b, and I had one also 30 minutes ago with AuraxTSense, so I'm asking if the cause is the rom or not.
When he reboot, he's not hot, I see it reboot sometimes and the phone was at normal temperature (approximately with my hands lol). it reboots max 1 time per day.
So I'm tellng myself that's it could be due to:
- radio
- S-OFF
- one app
For radio, I try tu update from 32.48.00.32U_5.11.05.14 to 32.47.00.32U_5.10.05.23, and I'll see.
For apps, the problem is that I would have not to restore all my apps, to see if one app cause it.
What do you think of it?
Thanks
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
Or as fnotsje said, could be hardware related
fnotsje said:
My question to you is: what are you doing with your phone at the time it reboots?
Playing a game, navigating or browsing the web etc?
I just got my Desire back from htc with a new motherboard, it used to reboot randomly also. Now it doesn't anymore
Click to expand...
Click to collapse
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
eden2812 said:
Are you using SetCPU?
Could be an issue with the kernel, or how one of the SetCPU profiles handle the kernel during screen off (interactive I think?)
It's installed but not configured in smatass mode, you advise me to uninstall it and to test?
Or as fnotsje said, could be hardware related
Click to expand...
Click to collapse
What is surprising, that if it's that, i t should reboot many more times than one time per day no?
Thanks
thierry_b said:
Sometimes I do nothing...maybe it's due to an app services?
But with your old motherboard, it reboots several times per day, or like me?
Click to expand...
Click to collapse
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
fnotsje said:
It depended on the usage, if I used it alot, it'd reboot more than if I used it less frequent.
But I'm not sure it is the motherboard issue, because you're mentioning the phone is not hot when it reboots..
Click to expand...
Click to collapse
Yes and always only one time per day, just one time maybe 2.
I desinstalled SetCPU, it changes nothing.
What do you advise me to do?
Wipe and install minimum apps, and see if I've that, and little by lttile, reinstall one new app...test few days again...?, it will be long :-(
Thanks.
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
GoogleJelly said:
Your phone shouldn't be rebooting randomly really. It's happened to me when I overclocked my CPU and played a game. It didn't like it at all. It sounds like something has buggered up somewhere down the line. If I was you, I would try quite a few more roms other than what you've tried. If it's still rebooting then it would need to get looked at by HTC or by going through you carrier (if they do it). That's what I would do.
Click to expand...
Click to collapse
With the minimum of apps, for example to see if it reboot or not?
Because if t's an hardware problem due to the radio, it censed to reboot even with few apps no?
For carrier as I'm at Orange like you, I think, they could change fastly my phone maybe. I will try that if anything works. You think that if I do that, I've to find an orange rom? I'm asking myself if they accept an HTC even restored with RUU.
Thanks
I have the same issue and ITS DRIVING ME MAD!!!!!!!!!!!!
I never experienced this with my stock ROM... so I firstly tried a gingerbread ROM... when it started... i then moved to a Sense Rom and still reboots occured... I'm now on my 2nd cooked sense ROM and still having reboots!!
WTF? is there a quick sollution?
thank you!
SO MANY follks seem to be having problems with [email protected]! Is there seriously no sollution to this or a common cause..?
had the same problem & is with HTC getting fixed
there are a few posts about it if you search - the only fix seems to be to send it to HTC for a new motherboard as some presume that it's overheating.
11 march still waiting on return of my Desire
I can relate to your issues. Mine kept rebooting when I tried to use the GPS. Like you I had mine rooted, S-off and was using a custom ROM.
After many tests, I downloaded a stock RUU, installed a different navigation app and once again, it rebooted.
Bottom Line: take it back. Its probably defective. Just make sure you're running a stock ROM. Download an RUU.

4.2 is making me angry

So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
its called sod, sleep of death. its a common problem with 4.2.1 kernel source. just about everyone has experienced them, some a lot more than others, root and not rooted, custom rom/kernel and stock. google needs to fix it in its source. there are some anecdotal fixes, some claim work, others say dont work.
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
063_XOBX said:
I'm running a 4.2 ROM (Beta at that) and am amazed at how much better my device is working. Everything is smoother and I haven't had a single issue. I honestly don't see how everyone is having so many problems with it.
Click to expand...
Click to collapse
im loving 4.2.1, cant say that i have any real issues with it. but, i do get sod occasionally, about once every ten days or so. if you around the forums, just about everyone has experienced them. some get them several times an hour, some several times a day, some several times a week, some just have had sod once or twice total. every device is different, they will have differing experiences.
dakota.breeden said:
So yeah all the 4.2 Roms are making me very angry because I'll turn my screen off and it doesn't want to turn back on. Is anyone else having this issue? Does anyone know how to fix it?
Click to expand...
Click to collapse
just go back to 4.1.2 if you are having issues.. 4.2.1 is a hit or miss IMO, some ppl get issues while for others it works great
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
bk201doesntexist said:
Just a thought, how many of you had bt on when sod occurs?
Sent from my i9250
Click to expand...
Click to collapse
Interesting idea. I never use it and have never had any issues.
i never use bluetooth, but have had sod.
Same here.
063_XOBX said:
Interesting idea. I never use it and have never had any issues.
Click to expand...
Click to collapse
I've had issues with BT on 4.2.1 (OTA), turned it off after a) sending first file OK b) second file fail, and it stuck on " turning off".
Read below.
simms22 said:
i never use bluetooth, but have had sod.
Click to expand...
Click to collapse
dakota.breeden said:
Same here.
Click to expand...
Click to collapse
I've experienced a "black screen" on 4.2.1 (OTA), due to what i think was a crash from XDA app, probably from using it with an ad blocker, at least from what i could see. I could adb shell to the device, remount system, no problem. I've removed the ad blocker from the system, while still on 4.2.1 (OTA), and have not experienced the "black screen of death" again.
I have not experienced a "sleep of death" yet on this device. Note: definition of sod from my galaxy s days: device is in a state (after going into deep sleep) in which the only way to get it back is pulling the battery out. System is unresponsive.
I've flashed JOP40D through stock images, and haven't seen black screen/sod scenarios, recreating the same system, more or less.
As i rarely use BT, i haven't tested it again, but we shall see.
Op, what apps do you have installed? Do you use SR/AVS? If not, please raise voltages by 50mv at each step, or at least the lowest and highest step, for mpu, core and iva.
While the device is in this state, no communication is possible? Can you logcat? dmesg? Can you receive calls?
Sent from my i9250
I have not had that issue or any SOD and I am running CM10.1 with LeanKernel, my wife runs the same setup and she also has not had any issues.
I've seen SoD's on Jellybro CM10.1 with ZenSERIES kernel v14.1, but only when using the ZenX governor. If I change to Pegasusq, the SoD's stop. I guess ADA is still working out some of the kinks in ZenX. Ooo, and it looks like v15 was released a few days ago. Something new to flash.

GNex lagging really bad after using it for a few weeks.

I had this problem before a few weeks ago, but a full boot.img stock reversion fixed things and I unrooted (then re-rooted) and installed the PACman ROM with the AK Kernel. Everything was fine until a few weeks later it started to lag really bad again. I'm talking the screen would hang for 5-10 seconds or just freeze completely. Earlier today I had to pull my battery about 3 times because of the freezes. I tried to install a new kernel a week ago, but that made it worse.
Why does it keep doing thing. I love the custom ROMs and the kernel tweaks, but I won't be able to use them if I go to stock...
Same thing here on complete stock 4.2.2
Been doing factory reset once a month since I got the phone in September.
Sent from my Galaxy Nexus using xda app-developers app
brad416 said:
Same thing here on complete stock 4.2.2
Been doing factory reset once a month since I got the phone in September.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
What are we doing wrong? :crying:
Had d same prob
Just use lagfix(fstrim) from google play
Sent from my Galaxy Nexus using xda premium
seriousia said:
Had d same prob
Just use lagfix(fstrim) from google play
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
sounds too good to be true tbh.
gonna try
RedDeadDorito said:
What are we doing wrong? :crying:
Click to expand...
Click to collapse
Not giving any information other than your own "diagnosis" for one.
063_XOBX said:
Not giving any information other than your own "diagnosis" for one.
Click to expand...
Click to collapse
i didn't give a diagnosis. I gave symptoms.
RedDeadDorito said:
i didn't give a diagnosis. I gave symptoms.
Click to expand...
Click to collapse
You interpreted the symptoms yourself rather than just report the issue and what software combination is resulting in the issue. Its lagging but why is it lagging? "Lag" isn't a symptom its a result of something else going on deeper down.
063_XOBX said:
You interpreted the symptoms yourself rather than just report the issue and what software combination is resulting in the issue. Its lagging but why is it lagging? "Lag" isn't a symptom its a result of something else going on deeper down.
Click to expand...
Click to collapse
I'm sorry, man. I didn't realize I had to report the issues exactly as I know them. I totally wouldn't resolve the problem myself if I knew what it was.
I guess you missed the part where I asked what software combination might be causing it.
Diagnosing problems you don't understand is exactly the kind of thing that makes it impossible to help someone. The phone may be right in front of you and you may know what you did but so far all you've done is tell us that:
1. Your phone lags
2. You tried a different kernel
3. You've pulled the battery
Not much to work with is it?
What CPU settings are you using?
What superuser apps?
Etc.
How much free space is on your phone? How about ram usage?
063_XOBX said:
I guess you missed the part where I asked what software combination is causing it.
Click to expand...
Click to collapse
I don't know. Turning the phone on takes about 3 seconds, same with turning it off. After unlocking, it hangs for about 4 seconds. Opening Chrome takes 5-10 seconds. Pressing the home button while on any app takes 5 seconds before it gives a response.
Don't say those are regular waiting times either, before I had these problems, things would appear at the touch of a button.
I also forgot to mention that a fresh ROM install doesn't help.
bodh said:
How much free space is on your phone? How about ram usage?
Click to expand...
Click to collapse
1.1GB
550-600mb+ being used at any given time.
RedDeadDorito said:
I don't know. Turning the phone on takes about 3 seconds, same with turning it off. After unlocking, it hangs for about 4 seconds. Opening Chrome takes 5-10 seconds. Pressing the home button while on any app takes 5 seconds before it gives a response.
Don't say those are regular waiting times either, before I had these problems, things would appear at the touch of a button.
I also forgot to mention that a fresh ROM install doesn't help.
Click to expand...
Click to collapse
"Fresh ROM install" as in you're just wiping cache and data then reinstalling?
Move on to the next step which is flashing a factory image.
063_XOBX said:
I guess you missed the part where I asked what software combination might be causing it.
Diagnosing problems you don't understand is exactly the kind of thing that makes it impossible to help someone. The phone may be right in front of you and you may know what you did but so far all you've done is tell us that:
1. Your phone lags
2. You tried a different kernel
3. You've pulled the battery
Not much to work with is it?
What CPU settings are you using?
What superuser apps?
Etc.
Click to expand...
Click to collapse
.180ghz min
1.4ghz max
interactivex
headphone boost 1
everything else is unchanged.
using SuperSU.
063_XOBX said:
"Fresh ROM install" as in you're just wiping cache and data then reinstalling?
Move on to the next step which is flashing a factory image.
Click to expand...
Click to collapse
factory reset
formatting system
then wiping cache
then installing
I think that space is an issue. I've read that once you get below 3 or 4 gigs free, the lag begins. Supposedly, on any disk, you should keep about 20% free, which for a 16gb gnex is 3.2gig.
Edit: isn't 180ghz min pretty low? I've seen 384 as a min suggested if lagging is an issue. And i think you mean mhz.
bodh said:
I think that space is an issue. I've read that once you get below 3 or 4 gigs free, the lag begins. Supposedly, on any disk, you should keep about 20% free, which for a 16gb gnex is 3.2gig.
Edit: isn't 180ghz min pretty low? I've seen 384 as a min suggested if lagging is an issue. And i think you mean mhz.
Click to expand...
Click to collapse
really? but I like my music :crying:
This is why they shouldn't have gotten rid of SD cards...
I'll see if clearing out my HDD space does anything. I've had it that full for quite some time though...
I'll see if putting 384 as min fizes it.
Your device also might not be able to handle 1.4 GHz oc. While its originally a 1.5ghz processor mild imperfections in the manufacturing process result in it being sold as a (guaranteed safe at) 1.2ghz processor.
What that means is that not every phone will handle the same speeds, voltages etc. You should try running at stock speeds for testing purposes.
I have this same issue, I've tried a number of different ROMs and kernals. They all start out great, then after about a month my phone starts to get random lag, then as time goes on it gets worse and worse until I bite the bullet and start over again

Xperia S screen becomes dimmer on one side randomly

Hello,my phone's screen becomes dimmer on one side randomly even when I'm not using it.The only thing that helps is if I leave in the fridge for a couple of minutes or when it's turned off for 15 minutes.If anyone had a similar problem please help me.
It must be overheating.
Try SetCPU
I have underclocked it to 1.1 Ghz but the problem is still there.
Wait for a while/days to stabilize.
AlinTheron said:
Wait for a while/days to stabilize.
Click to expand...
Click to collapse
I doubt it will help but I'll report back in a couple of days.
Ok, I think It will work,let's hope so.
AlinTheron said:
Ok, I think It will work,let's hope so.
Click to expand...
Click to collapse
Well the problem is still there. :/
I don't know what to do now.
mihael1995 said:
Well the problem is still there. :/
I don't know what to do now.
Click to expand...
Click to collapse
Download THIS and go to the screen section, among other tweaks, and hope that one of them will solve the display problem.
Still not working.Guess I need to get it repaired...

[Q] Galaxy Nexus Sleep of Death

Problem: Cannot turn on the screen by pressing the power button sometimes. The screen is black or very dim, I cannot tell. One can see nothing on the screen, and it doesn’t accept any touch input, either. The phone still rings if there’s an incoming call. If this happens, the following several presses (about 10 - 20) on the power button will probably lead to a reboot. The “screen auto-rotate” and the proximity sensor may fail after the reboot, but will recover after a manual reboot.
Frequency: Fewer with higher Rom version. About once per day for 4.3.
Other description:
 The problem frequently happens when I just take the phone outside my house/office, and seldom happens when the phone just stays somewhere.
 The problem seems to be irrelevant to the remaining battery capacity or the uptime, but it never happens when charging.
 The problem seems to be irrelevant to the Apps installed.
 The problem seldom happens in the first 3-4 days after flashing a Rom, but happens more and more frequently as time goes by. My guess is some cache is stuffed by some trash, which causes the problem. The phone may be fine as long as the trash can be cleaned up on a regular basis.
 I manually reboot my phone at most every two days.
Solutions tried, but don’t work
 Flashing official ROMs 4.0.4, 4.1.1, 4.1.2, 4.2.2 and 4.3 following the procedure “adb reboot bootloader; fastboot oem unlock; flash-all; fastboot oem lock”, without google wallet, not rooted.
 Turning off the auto-brightness control, as suggested by some post on the Internet.
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Thymo said:
Does it look like it goes to standby normally or does the screen show gibberish and then turns off?
Sent from my Galaxy Nexus using XDA Free mobile app
Click to expand...
Click to collapse
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Bobby_yan said:
Thank you very much.
I think it's standing-by normally even through the screen is black (or very dim, I cannot tell), since it rings if there's an incoming call. I can see nothing from the screen, and I don't think the screen accepts any touch input, either.
Does this answer your question? Thank you.
Click to expand...
Click to collapse
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Thymo said:
Thanks.
Was just asking if you had gibberish yes or no. In that case i've got a different issue than you (Suspecting f*cked GPU).
Have you tried a different ROM/Kernel combination maybe it's related to that.
Click to expand...
Click to collapse
No.
No, I just tried the official ROMs. Any suggestion?
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
eKeith said:
Perhaps it's just busy in the background and running low on RAM. Give LagFix a try. Sorry can't link atm as I am on mobile...
Click to expand...
Click to collapse
Thanks a lot. I'm trying it.
Bobby_yan said:
Thanks a lot. I'm trying it.
Click to expand...
Click to collapse
LagFix does NOT help in my case. Any other suggestions? Thanks.
I've also had this blank screen with calls still ring issue for as long as I can remember, nearly 2.5 yrs.
I've always suspected it's my ROM and so I'd try out another ROM'S, BUT no other ROM works like how I'd like, so I always come back to my ROM.
It doesn't happen every single day, but it does happen very often.
I've tried using apps that auto reboot daily, but eventually this blank screen issue will return.
Unfortunately I can't seem to find any solution, so I just put up with it, it's like the 1 only flaw with my ROM.
&
Not to be at all rude, but I'm really glad op has had this issue from testing other versions of Android, cause then at least I know I don't need to give up my great tablet mode ROM.
LOL
I think I've finally found a work around for this screen of death.
Using Exposed, download/install this module/extension:
Disable Proximity
http://repo.xposed.info/module/com.mrchandler.disableprox
It does exactly what it's name is and ever since then I've not once had to remove my GN battery to work again because the screen went completely dead.
NVM
Screen still goes dead.
Anyone find an actual fix to this?
isajoo,
I had pretty much the same problems with my Galaxy Nexus running CyanogenMod 11 M12.
It got better by doing the following :
Blowing dry air in the earpiece… though the proximity sensor is clearly beside it. Can't do any harm though, I guess.
Settings/Applications/All/menu/Reset applications preferences (or whatever that's called in english) : that seemed to do a lot of good to my phone ! However, it's a very unsatisfactory answer on a technical point of view, as I still don't know WHAT was precisely needed. It's a "magic wand" solution for which I can't give an explanation.
Not specifically related, but greatly helped my phone in the responsiveness area : Trimmer (fstrim) (https://play.google.com/store/apps/details?id=com.fifthelement.trimmer), an updated version of LagFix that you may already know
Hope that helped !
(I wanted to try http://www.androidlegend.com/how-to-perform-proximity-sensor-calibration-on-any-samsung-phone/ as well, but apparently, /sys/class/sensors/proximity_sensor/prox_cal does not exist on my phone…)

Categories

Resources