Related
Just started happening today.When charging my phone it will turn on. Does anybody know of a fix or what the cause is?
grayhair98270 said:
Just started happening today.When charging my phone it will turn on. Does anybody know of a fix or what the cause is?
Click to expand...
Click to collapse
Do you mean randomly some time after plugging in the charger, but not the 100% notification?
Screen turns on when a charger is plugged in, and also at 100%. A custom ROM can fix the 100% notification.
randomly, comes on about 1-2 minutes after plugging in
i don't have the answer, but i think we're talking about powering the phone off then charging. it's supposed to just show a battery pic but is powering back on. it might be the kernel you're using. that's what people said it was when i tried Sprint's version. mine didn't power back on with this model, but i haven't tried it lately.
using Zedomax stock kernal,phone is off ,plug in to charge normall battery pic will appear after a minute or so it will boot up on it's own
Ghost in the Shell...
Can't help but sure sounds strange... Have you tried to reflash and see if the problem persists?
Don
reflashed still there
re: power-up issues
grayhair98270 said:
randomly, comes on about 1-2 minutes after plugging in
Click to expand...
Click to collapse
Make sure that the rom you are using is one which is designed for the SGS i777 phone.
It might even be a good idea to re-download the rom just incase the first download
some how got corrupted during downloading.
Do a clean fresh "wipe data/factory reset" and re-flash the rom but don't flash any custom
kernels and don't install any apps at all until you have had enough time to see if the
problem still persists.
Flashing roms like any of the i9100 rom or any other rom which was not
intended for our phones can cause unexpected and random issues.
Good Luck!
I have the same problem. I turned off the phone to charge up, a min later, the phone automatically turns on by itself. I rooted it with Zedomax kernel (SGH-I777-ATTGalaxyS2RootStockZedomaxKernel) before. Could this be the cause? Any other users have the same problem?
Misterjunky said:
Make sure that the rom you are using is one which is designed for the SGS i777 phone.
It might even be a good idea to re-download the rom just incase the first download
some how got corrupted during downloading.
Do a clean fresh "wipe data/factory reset" and re-flash the rom but don't flash any custom
kernels and don't install any apps at all until you have had enough time to see if the
problem still persists.
Flashing roms like any of the i9100 rom or any other rom which was not
intended for our phones can cause unexpected and random issues.
Good Luck!
Click to expand...
Click to collapse
Not true. There are minor differences between i777 ROMs and GT9100 ROMs. The main differences are the radio, kernel, and button mapping; which have all been fixed with Hellraiser and HapticFix.
Sent from my Samsung SGH-i777 using XDA Premium.
grayhair98270 said:
Just started happening today.When charging my phone it will turn on. Does anybody know of a fix or what the cause is?
Click to expand...
Click to collapse
My phone does the same thing. I don't consider it to be a problem because my phone is rarely ever turned off. I wouldn't be too concerned about it. If it bothers you enough, you could always do a warranty exchange. Personally, I'd rather live with a minor annoyance, than have AT&T send me a refurbished replacement.
Sent from my Samsung SGH-i777 using XDA Premium.
You can try out nomoarpowah app. It replaces the battery charging 'off' screen with one that has reboot controls and shows the time.
It might be able to stop the phone from booting itself. Not to mention it's really cool and will only work on Samsung phones.
Sent from my páhhōniē
wrenchmonkey26 said:
Not true. There are minor differences between i777 ROMs and GT9100 ROMs. The main differences are the radio, kernel, and button mapping; which have all been fixed with Hellraiser and HapticFix.
Sent from my Samsung SGH-i777 using XDA Premium.
Click to expand...
Click to collapse
MJ wrote that before Hellraiser existed. Look at the posting date.
Gr8hairy1, I tried the app. Got it installed and when I run it the phone still shuts down, the battery screen appears and then the phone boots up. Booo:-(
Sorry I meant to quote you.
Sent from my SGH-I777 using XDA App
grayhair98270 said:
using Zedomax stock kernal,phone is off ,plug in to charge normall battery pic will appear after a minute or so it will boot up on it's own
Click to expand...
Click to collapse
Try Entrophy's kernel to see if it does the same. Screen off charging is controlled by the kernel from what I'm told. When I was running MIUI it use to do that until they added the function in the kernel.
EDIT:
I just decided to try it since I never charge that way....lol and mine did it as well.
ah well.... I think this may be an issue.
jpstiehl said:
Gr8hairy1, I tried the app. Got it installed and when I run it the phone still shuts down, the battery screen appears and then the phone boots up. Booo:-(
Sorry I meant to quote you.
Sent from my SGH-I777 using XDA App
Click to expand...
Click to collapse
Well if it's any consolation my phone is doing it too. I guess I never left it off long enough. Starts right up after a minute or so.
But once this issue gets figured out I'm sure you'll really like the app. It's good to turn off the phone every once and awhile. And with it you can set it to boot the phone when it's done charging or at a specific time.
Running unnamed 1.3 with dd11232011 kernel
Sent from my páhhōniē
I'm also having this problem. Is it hardware? I have the latest unnamed rom. Phone won't stay off no matter what...I've tried pulling the battery and everything.
I don't have this issue on miui if it helps...
IIRC, I also didn't have the issue with UnNamed, but its been a while since I ran that.
Sent from my Galaxy S II (i777)
i am having the same issue, using a zedomax kernel, if anyone has a solution i would like to hear it, i like to be able to shut the phone off when charging it some times, it seems to charge faster when its off
This is a known issue with my kernel's 11/23 release, and ONLY that release for my kernel, it was a result of adding support for the Interactive governor.
I have no clue what the results might be for Zedo's kernel - he released one kernel, lots of people had problems with it, then he disappeared. He probably enabled Interactive governor too.
It could also affect CM7, I know for a while CM7 builds had issues with not supporting LPM at all - CM7 devices would go to the bootanimation and stay there.
I wanted to see if I can post something without getting ridiculed. Seriously doubt that now cause I accidentally posted this in the general Q&A first and did not know how to move it or delete it so i am posing again here. Hopefully a moderator can just take care of that stray posting I made in the general area.
I am on my second ATT SGS2. First one had a GPS issue. Tried everything and finally convinced ATT warranty services that the problem was hardware. They said they would advance replace the handset. So I got it back to stock in every way except the flash counter,this was in December so long before I was aware of mobile odin. Flash counter was at about 12 when I was done trying different ROMs,mostly just try to get the GPS to work. It was in perfect shape, bone stock except for the counter. I cannot imagine I will have an issue, but has anyone ever heard of someone getting charged on a return to stock phone that had a flash counter above stock? Ill update once I know for sure the outcome.
My real question, does everyones SGH-I777 crash on occasion? If so how often? I so happy with the current code that is running on the phone with the exception that it sometimes sleeps and wont wake up, and sometimes it just plain crashes hard, locks up and has to be hard rebooted. Usually this happens about twice a day one or the other. I wiped before installing current kernel. The only reason I am not stock is cause I wanted the CKK6, 2.3.6 update to work and to keep root privaledges, but also needed my wifi cause ATT is throttling me down to dial up speeds when I reach 2GB. So wrong!!! Anyway thats another thread.
I loaded shostock with siyah kernel 2.6.35.14. after wiping everything including both caches. The GPS is solid now, phone is fast, battery is egh, I keep a charger with me... but it crashes hard from one to three times a day. Locks up playing tunes, or wont wake up with out being plugged in or hard booted. Do I have another defective handset or should I just go back to 2.3.4 and UKH7 or should I just deal with it and consider the crashes, "excellent opportunities to reboot."?
Thanks for the all the hours of fun, u know who you are.
I honestly don't remember my phone crashing at all. If it's crashing, it aint stable. Did it crash when it was stock?
yeah I mean duh right? The new handset was updated, rooted, downreved and flashed with the custom rom before it was put under any load, so I do not know if it would have crashed before. I have wiped, re downloaded, checked with hashtab and re flashed my current kernel, so it seems like it has to be hardware, again... ugh. Especially since no one else is having issues with shostock and siyah. I wonder how hard it is going to be to get warranty services to replace the second phone in 3weeks!? Lol.
Try going back to stock and run it for a couple hours to see if it still crashes. If it still crashes then more than likely hardware issues.
Sent from my SAMSUNG-SGH-I777 using xda premium
If it's crashing on stock without SetCPU to set a screen-off profile, you have a hardware problem.
I haven't had a crash, freeze, or spontaneous reboot in ages - despite running kernels that a few others have reported stability problems with (and I have effectively halted my kernel until I can get to the bottom of those reports...)
Too often is when it happens regularly, period.
I'm running CyanogenMod 9 and have almost no crashes, despite it being experimental.
Sent from my GT-I9100 using XDA App
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
silashj said:
I reverted to stock last night shortly after posting this. Ran fine until re loaded SHOstock v1.9.2-UCKK6. It is not "crashing" but it will go to sleep and not want to wake up again. I can sometimes plug in the charger and that will wake it up but other times I have to hard reboot. So no more crashing, but will not wake from sleep about 10% of the time. Not a huge deal, but its a bit weird because I know that the code I am running is ok, and it seems the hw is ok, so... not sure why this is happening. Anyway thanks all for your suggestions etc.
Click to expand...
Click to collapse
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
I had the same problem using the latest siyah kernel, but never with entropy's. I would suggest flashing a new kernel.
Sent from my GT-I9100 using Tapatalk
1. To answer the OP question, I have experienced ONCE that was when I tried to run the Andy's TI-83 emulator on my virgin stock ROM. The result is either my fault or the application isn't compatible with the running OS.
2. With bone stock, it shouldn't crash at all. If it does, RMA.
3. If the owner(s) have "some fun" around it such rip it off, hack it up, install different kernels, different ROMs, ...... then please DO NOT complain the device is suck.
I've seen a lot of knuckleheads who tried to mod their devices, screw them up then claim "they're suck".
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
Thanks this sounds like a plan. I have to do something things have gotten worse. About 3 out of ten times I go to put the phone to sleep now, instead of blinking out the phone takes a screen shot. My fingers are no where near any of the other buttons and it takes a screen shot over and over when I press the power button. I have to move around from screen to screen, hit the home button and then hit the power button to put it to sleep. Weird stuff, could be worse though. Did I say that I thought the phone sucks? I thought I read in one of the replies up there something like that. Aside from the GPS issue that was hardware related, and problems I have brought on myself because stock wasnt good enough, this is hands down the most awesome piece of electronics I have ever owned. iPhone smyphone. I just need to find the perfect turbo charged, rooted but as stock as possible configuration that is stable and I will be set. I really like where I am, hopefully the kernel you suggested does not change much but fixes the problems. Thanks again all.
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
dandrumheller said:
This sounds like SoD (sleep of death) to me. I would recommend reading through Entropy's kernel thread (yes, it is a LOT of reading) but it might give you some insight into possible causes and/or solutions, and you'll get a great feel for where development on this device has come from, from the beginning...
Click to expand...
Click to collapse
axis01 said:
Grab one of Entropy's DD Kernels and flash it with CWM. I'd suggest getting one from Jan or earlier. His latest ones are trying to track down a issue.
Click to expand...
Click to collapse
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
silashj said:
Ok the noob is going to shine through here... but you say to flash with CWM. With my current config, when I enter recovery mode I am taken to the siyah kernel recovery console. Are we talking the same difference here, and when I go to flash as you mentioned can I do so with Siyah recovery or shall I flash with something that will give me back cwm first and then flash the config that you mentioned in your reply?
Click to expand...
Click to collapse
That recovery will work. After installing the DD kernel, CWM will change.
Sent from my Galaxy SII
I get a crash here and there everyday...
Sent from my SGH-I777 using xda premium
Have only ever crashed while messing with voltages or clock speeds. if it's crashing something is wrong.
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Mine crashes a few times a day if I'm cycling through a lot of apps or installing things. (Stock+root) the other day my phone would crash anytime I tried, to watch a video in web browser. (Either mxplayer or phone)
Sent from my SAMSUNG-SGH-I777 using XDA App
T90 said:
A few people's phones just do not play well with Siya kernal. Most of those people flash Entropy's DD and the sleep deaths go away... give it a try, I bet it will help!
Click to expand...
Click to collapse
With Siyah I crashed more often than I do know with DD...
Sent from my SGH-I777 using xda premium
Ok flashed the DD from 01-30-2012
Thanks for all the help. I will post again when I know if things are better.
I have two galaxy s2s. one is i9100 and the other one is i777 on at&t.
SoD happened once on each phone. The i777 was running stock gingerbread and the i9100 was running resurrection remix 1.9.1 with the siyan kernal I believe.
The screen just wouldn't turn on so I just pulled the battery out (is it safe for the phone?)
This doesn't happen often,well just once each on each phone as stated before, but it does bug me as it makes me think there's something wrong with my phones, and pulling the battery out doesn't seem like it's good for the phone.
I searched around the forum a bit and saw other people are having this issue as well. And not just the galaxy s2, but other phones too.
only sleep of death in almost 10 months of use is when i tried xwlp9.
so no its not common
It's fairly common yes, a lot of people running non-stock ROMs get this. I had this ~25 times on numerous Resurrection Remix ROMs, but since v1.9 I haven't had this issue fortunately. If it's causing you a big problem, try fixing permissions from CWM recovery, that seemed to make a big difference when I was having the problem.
SOD usually occurs when the kernel UV the CPU or GPU a little to much. Not every device is the same and not handle same kernels, UV values etc
Sent from my GT-P6810 using XDA Premium HD app
From the sound of it, it seems to be a software problem.
I got it on the i777 which wasn't running a custom rom. But I think it could be caused by that battery management app that I installed.
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
It's normally a firmware issue, or a conflict between an app & the firmware. You'd find it's pretty rare for an 'untouched' (I.E not modded) phone running stock firmware to have SOD's. And obviously if you're flashing custom firmware that's constantly evolving/changing, then sometimes you're going to get SOD's, tho with most well crafted firmware these are fairly rare.
I reckon I've probably had <10 in the 8 mths I've had my phone & I've been running non-stock firmware the whole time save for the week I got my phone, which is nothing when stacked up against all the mucking around I've with my phone.
Edit to add - One way you can test to see if SOD's you're having are possibly hardware related is to do a completely clean install of stock firmware & see if they still happen. If they don't, then it's obviously whatever firmware you were running. If they do, then it might be hardware-related. Re: your question about pulling the battery after a SOD, normally this shouldn't cause you any problems (it's sometimes the only way you can successfully reboot the phone).
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
victorator said:
The only known SOD issues on I9100 are the old 2.3.3 (don't remember which one) and the XWLP9 kernel.
Custom roms... well. No need to elaborate I guess.
Most of them have undervolted settings as default.
Click to expand...
Click to collapse
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Ray_Grey said:
Im pretty sure i rooted my phone on the we with LP9 kernel. Since Sunday, I've had about 10 sods and never had one before... no doubt here as to what's causing it. I plan to change the kernel on the we and hopefully no more sod.
Click to expand...
Click to collapse
Or just flash the newer build. No SOD there.
wanewon said:
anyway, my main concern is that if there's anything wrong physically with the hardware. ( having the SoD caused by software problem is much easier to swallow as to it being caused by hardware problem, as I can just reflash the kernal, roms, factory reset, etc. )
and did removing the battery while in SoD mode damage the phone?
Click to expand...
Click to collapse
How about this?
I answered your question. Read the edit I made to my post.
wanewon said:
How about this?
Click to expand...
Click to collapse
MistahBungle said:
I answered your question. Read the edit I made to my post.
Click to expand...
Click to collapse
Thank you for the answer.
Since it's kinda hard to recreate the SOD. I'll reflash the rom and kernal and do a wipe and see if the SOD still happen
victorator said:
Or just flash the newer build. No SOD there.
Click to expand...
Click to collapse
Victorator, forgive my ignorance, but are you saying i should just flash the latest build, XWLPD, onto my fone rather than re-rooting it using a different kernel (i.e. CF-Root-SGS2_DX_SIN_LP9-v5.4-CWM5.zip) in order to stop the SOD?
Never faced such issues ever.
Sleep of death
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
MX 007 said:
Hi all, the SLEEP OF DEATH on android phones has even become worse; somebody said this issue is resolved in ICS 4.0.3; thats not true. As of now; i have a galaxy S2 i900, 1 month and 2 weeks old, running ICS 4.0.4 and I have been experiencing this problem lately and took back my phone for repairs last week, got back the phone yesterday and this morning the sleep of death happened 3 times in 1 hour. I took the phone for repairs again later this evening and i made it clear to them that problem still hangs around and i told them that if it comes back with the same problem, they got to give me a new one because it happens on some devices only and im dead serious because SAMSUNG knows about this issue very well and they do nothing. NOW CHECK THIS OUT: the new SAMSUNG GALAXY S3 features this disease too; i was in the queue with two S3 clients reporting this problem. Android is really bad at times; im moving to APPLE
Will keep you Updated
MALCOM
Click to expand...
Click to collapse
bah bye
SOD
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
?
darkm1st87 said:
im having the same trouble with stock android 4.0.3 and know with
super nexus rom, the only way to solve it, is to use a program that
prevent phone lock, at the costo of more batery use
Click to expand...
Click to collapse
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
tkrokod said:
Could u please test something for me...because i am trying to solve this problem since a long time..
Could u put your phone while open screen on refrigerator for 30' .There is no fear of destroy the phone.I have test already 2 phones with sod and both are doing it with low temp.I want to see if it is sw or hd problem
Click to expand...
Click to collapse
Hi,
I'm also trying to solve this problem, since weeks.
My observations:
SOD happens most on higher battery status (e.g. more SOD's at 80% battery then at 20%
The Phone gets hot after SOD and also before the SOD comes.
While loading the Phone SOD's happen more often
The battery status drains rapidly while SOD (cause of the resulting heat)
My SOD's are independent of kernel, rom, firmware or what ever.
I think it's a hardware problem, but I've no warranty and what to solve the problem without changing the mainboard. It couldn't be a really defective of an important part, cause the phone works apart of this SOD-problem.
Maybe we could find out together howto solve these anoying sod's
Hey. Im trying to solve the SOD problem myself cause its been happening every day and its really annyoing since the phone isnt even a month old.
I got the newest cyanogen mod running.
The phones model is GT-i9100
Android is 4,2,1
I still have warranty on it, do you think I should go back to stock, go exchange my phone where I got it and see if the new one has SOD too or should I just try fixing it first.
Also apps I use constantly : go launcher and dragonvale
I have a 8 gb micro SD inside as well, dunno if that could cause this.
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Seems like your system files might be corrupted. Wipe system partition from fastboot or cwm then reflash your rom. Any time I had weird stuff happen on a rom, I wipe the system then it goes away. Hope this helps you get rid of this issue. Good luck!
Sent from my MB860 on CM7.2.0 Stable
Doesn't work, just wiped system, cache and dalvik, then flashed rom and sod's still happen.
I have also tried flashing several radios, all with sod's. Any suggestions?
wakelock
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
affiatic said:
I had this problem on stock and every rom I tried (this was actually the reason I unlocked) I installed wakelock app from the market. I set it on partial wakelock. I think it keeps phone from going into deep sleep. It worked for me. I think it may make battery life a bit worse but having to pull battery sucks. Since I also have the issue on stock I am prob sending it in on warranty
Click to expand...
Click to collapse
So you've had SODs since you got the phone? Wakelock seems to work, but kills the battery.
For anyone who does NOT have SODs what modem/radio are you using?
Yes had them since I got the phone. Wakelok fixed it for me. Battery life is not horrible. It still last me like 14 hrs moderate use. I have tried radios and everything else I could thing of. Think mine is hardware related. That is why I am sending it in. I was surprised to find out it was still under warranty
I've just noticed that when mine shuts down, it gives a green notification first, then when I try turning the screen it, it reboots.
Unfortunately, my phone is out of warranty, I bought it used
SODs still happen in airplane mode.
Try wakelock and post if that fixes it.
Call Motorola directly. I bought two used. Had the same problem. They replaced them both with new units.
Motorola Android Department
1-800-734-5870
Just don't say anything about buying it used.
Good luck.
As posted above, wake lock works but uses battery.
I live in Canada and am out of warranty, would I still be able to call?
It's worth a try. You have nothing to lose.
Sent from my MB860 using xda premium
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
javinavas said:
I had the same problems.. but mine happens when phone gets above 35°C.. So I activate wakelock at this time until i see temp is lower than that.. after that I disable wake lock.. it's a pain in the ass.. but it is better than pull the battery out once every 15 min..
Click to expand...
Click to collapse
Is there something specific about 35C, and are you sure it is exactly that?
I have installed 2.3.6 Bell and I still get reboots, anyone have a link to stock 2.2.1 Bell SBF that I can try?
sometime 35 sometime 36.. but above that temp.. sod kills me.. under that temp phone runs smooth..
I'm a system enginner but I haven't program in years.. I'm thinking seriously in create just a services to read temp and launch a wake lock when temp reache some level..
I'm pretty sure I will help lot of people but aint sure when i can start doing some work
dancom96 said:
Whenever my phone goes to sleep, and I try and turn on the screen again, it simply reboots. This occurs in airplane mode with nothing enabled as well
Unlocked, CM7. I flashed different roms and they all had this, I don't think it happened on stock.
Any fixes? All the threads I've seen have no real info
Click to expand...
Click to collapse
my phone would not actually reboot but in went into SOD (sleep of death) so every time this has happened to me i installed a new kernel or reinstalled the one i had.........always rectified the issue.
Same issue
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
jediknightbrodie said:
I had the same problem when I flashed CM9 and then when I downgraded back down to CM7, I tweaked the kernels I used and changed my UV settings and it hasn't happened since. Perhaps flash a different kernel and see if that works?
Click to expand...
Click to collapse
Tried several of them, this seems to happen on stock 2.3.6 as well.
I flashed a stock sbf to return to stock. Still had the sleep of death. Reboots after and during phone calls, and touch screen problems. I believe it is hardware related.
Hey fellas, my phone will not stop rebooting and i was wondering if anyone was having the same issues? My phone is S-off and i have tried several kernals and different roms. ive wiped the battery stats, drained down the battery and fully charged it while the phone is off. Im getting to the point of grabbing a hammer and breaking this and either buy a Galaxy S3 or wait to see what apple does with the Iphone 5. Any suggestions? Should i buy a new battery or is it just my phone?
Did you flash a ROM without wiping? Are you flashing kernels on roms that you shouldn't be? A little more information might help
Sent from my HTC_Amaze_4G using xda premium
Flash the stock RUU and run for 24hrs to see if the reboots still happen.
Another issue could be the battery. I've also heard that SIM cards could cause some reboots. It's just a process of elemination.
Spastic909 said:
Did you flash a ROM without wiping? Are you flashing kernels on roms that you shouldn't be? A little more information might help
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I always do a full wipe on the phone, including the cache and davlik. And for the kernels ive only used faux's kernel and the stock kernels.
Double0EK said:
Flash the stock RUU and run for 24hrs to see if the reboots still happen.
Another issue could be the battery. I've also heard that SIM cards could cause some reboots. It's just a process of elemination.
Click to expand...
Click to collapse
Ive thought about doing this as well, i will try flashing the stock RUU. Never thought about the sim card but its worth a shot. Im starting to believe that it might be the battery. Thanks for the advice, i dont really want to move to another phone but this is becoming a lil too much :fingers-crossed:
tonym2015 said:
I always do a full wipe on the phone, including the cache and davlik. And for the kernels ive only used faux's kernel and the stock kernels.
Ive thought about doing this as well, i will try flashing the stock RUU. Never thought about the sim card but its worth a shot. Im starting to believe that it might be the battery. Thanks for the advice, i dont really want to move to another phone but this is becoming a lil too much :fingers-crossed:
Click to expand...
Click to collapse
I think the majority of the users in the Amaze forum had their batteries go bad. Just get a new battery. Either call HTC and request for a replacement battery per HTC's warranty or buy an Anker battery.
My stock battery is going bad. It'll only last about 6hrs now. It used to last 10-16hrs depending on use. But I can let it sit, without using it, for 4hrs and my battery will he about 30%..I've never had the random reboots with it yet.
Just as an update, i installed the official RUU and still encountering the reboot issue :crying:
tonym2015 said:
Just as an update, i installed the official RUU and still encountering the reboot issue :crying:
Click to expand...
Click to collapse
Now that double points it out. It could be a sim as well although I don't recall as I got a new battery and sim and flashed stock ruu before inserting them. Then they disappeared.
Sent from my HTC_Amaze_4G using xda premium
This is from the Sensation forum, but a similar fix can be applied for Amaze as well:
[FIX] Random reboots/shutdowns. Pictures added!
You can see the fix highlighted in this image if the fix isn't clear enough: http://forum.xda-developers.com/showpost.php?p=29891426&postcount=5870
kgs1992 said:
This is from the Sensation forum, but a similar fix can be applied for Amaze as well:
[FIX] Random reboots/shutdowns. Pictures added!
You can see the fix highlighted in this image if the fix isn't clear enough: http://forum.xda-developers.com/showpost.php?p=29891426&postcount=5870
Click to expand...
Click to collapse
I should try that. But it doesn't appear to be a contact issue though. Many Amaze users, including myself, had that issue. The only thing that fixed it was a new battery.
The pins seem to be spring loaded (or something like it) because when I insert the battery, the pins go back like 1/3 to 1/2 way. There is absolutely no room for movement whatsoever. It's not like the battery was loose. But that's just me, and the mileage may vary for others.
kgs1992 said:
This is from the Sensation forum, but a similar fix can be applied for Amaze as well:
[FIX] Random reboots/shutdowns. Pictures added!
You can see the fix highlighted in this image if the fix isn't clear enough: http://forum.xda-developers.com/showpost.php?p=29891426&postcount=5870
Click to expand...
Click to collapse
This is interesting and i will definitely try it, thanks for the advice.
:good::good::good::good::good:
kgs1992 said:
This is from the Sensation forum, but a similar fix can be applied for Amaze as well:
[FIX] Random reboots/shutdowns. Pictures added!
You can see the fix highlighted in this image if the fix isn't clear enough: http://forum.xda-developers.com/showpost.php?p=29891426&postcount=5870
Click to expand...
Click to collapse
Ok so i tried this yesterday around this very time and im happy to say that as off right now ive have had one single random reboot. Heres to hoping that this is a permanent fix! Thanks again!!! :laugh: