hey guys, im having this issue with random reboots. been rooting since the eris, then dinc, now thunderbolt. now with the tbolt, i bought it around the beginning of the year and now its becoming more and more frequent these random reboots. it happens with every rom ive tried (XDABolt, killasense, thundershed's cm7, now GBR 3.3).
i thought it might of been the base i was using, but now i dont think it was cuz it seems to have happened again on the newest one (.19). the only thing that seems to be constant is this happens while the phone is in my pocket, and USUALLY when im moving around a lot, lots of heat/leg sweat. i actually hope that this is just a heating issue cuz then i at least know that its my own user fault, but i dont know for sure.
i dunno if a last_kmsg will help seeing if this is the case, but i was hoping someone more knowledgeable on these logs could help out?
http://db.tt/DtPruALc
also im currently running GBR 3.3 w/ stock kernel.
EDIT: O also i am currently using the oem extended from verizon, but this also happens w/ stock battery as well
Related
I know there are several posting about Vibrants shutting down on its own even when it is fully charged, but, most of the posting are about rooted phones. I am experiencing the same problem but with a stock Vibrant upgraded to 2.2 Froyo. Is there a fix for this problem? I just experienced this problem twice today already and I'm hoping stock Vibrant owners might have a solution.
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
cashmundy said:
I have also had spontaneous shutdowns and reboots using CM. I tried two different ICS builds for a while (Onecosmic's and CM9 Kang) and it didn't happen with either of them, so maybe something about ICS fixes this. I'm waiting for CM permissions management to appear in an ICS build, then switching over for good.
Click to expand...
Click to collapse
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
dustinkh said:
I'm pretty sure in the OP the guy is looking for help from people on a stock vibrant, unrooted on 2.2...
As far as the random shutdowns go, I would try to factory reset the phone and let the phone sit for about 5-10 minutes after doing so before reinstalling apps and whatnot.
Sent from my T959 using XDA App
Click to expand...
Click to collapse
I have put my phone back to JFD via Odin quite a few times, let alone resets, so I wouldn't expect much from that. There will apparently never be a stock ICS for the Vibrant. If the underlying problem is indeed fixed in ICS, the OP may want to make the leap to a good rom at some point.
My GF's phone was on stock 2.2 Froyo and shutdown incidentally, it actually just cut power, black screen suddently. Tried two battery and did the same, reflash to VJI6 and JFD and didn't help at all, but after flashing to Bionix 1.3.1 somehow the problem is gone, weird though
Spontaneous halts and reboots indicate a bug in the kernel or drivers. I don't know what bionic uses. ICS kernels are from the 3.x series of Linux, and are incompatible with older roms. Changing ketnel amd/or radio driver might be a way of attacking the problem short of changing roms. I've changed radios with CM7 but still get the halt/reboots.
A spontaneous shutdowm could also be cause by the battery making bad contact.. try smacking or dropping the phone and see if it happens
sent from the xda app on my android smartphone.
Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
mforminio7 said:
Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
Click to expand...
Click to collapse
Is it an actual freeze or is Sense crashing? I saw that a lot when I still had a ROM with Sense. If you're hitting home but not going anywhere then that's probably the case. No real cure for it other than to try unlocking and tossing another ROM on. You could also have something wrong with your SD. Pull that out for a while and see if the freezing/crashing still occurs.
You said no apps loaded so I assume you didn't restore any data from another phone either?
I've been running Ineffabilis for a month now without that issue so it shouldn't be the ROM. What happens after the freeze? Do you have to reboot or does it go away? (I don't know why I'm asking that cuz I don't know how to fix it no matter what your answer! But I like pondering and the more info the better for when someone more knowledgeable comes by.)
You could also try flashing a different kernel and see if that helps. I just put on AnthraX and it's running nice and smooth.
MrSmith (that feels so formal after all these months, I might have to call you Smitty now ), or anyone else... would there be an error log generated somewhere that could be looked at?
mforminio7 said:
Hi everyone, I've been having serious problems and if anyone can help me I'd love you forever. I got a rezound a week ago and loved it. I decided to root and rom it and afterwards my screenwould randomly freeze. I tried every GB rom and no matter which rom I was on it would freeze
I thought maybe my phone was defective so I returned my phone and got a brand.new.resound. once I installed.inef on my new phone it started freezing again. No apps loaded just stock inef. Could it be my sim card? Any help would be greatly appreciated.
Click to expand...
Click to collapse
I think the problem is in the kernel and not the rom. I had issues with gingerbread rom/kernel combinations. What are you using to control your CPU? Just making sure you aren't using more than one app, but since you didn't mention that you may not be adjusting clock speed at all.
I would recommend flashing an ICS leak and Sebastians modified kernel and seeing how that does. It's not as stable as an OTA but I don't see problems with random reboots and freezes on ICS even when overclocked to 1.7.
Hi guys thanks for the replys. Its not the kernel or rom because I've tried every gb kernel and every gb rom and my problem still persists. And I've swapped out dif SD.cards as well so I'm really scratching my head lol. Could it be the sim card? I think it needs to be hardware related but my last resound had the same issue but the sim is the same. And when it freezes I mean the screen just stops updating. You can press the buttons but the screen will stay frozen until a battery pull. Thanks!
maybe go get a new phone if u say u have tried all those things?
mforminio7 said:
Hi guys thanks for the replys. Its not the kernel or rom because I've tried every gb kernel and every gb rom and my problem still persists. And I've swapped out dif SD.cards as well so I'm really scratching my head lol. Could it be the sim card? I think it needs to be hardware related but my last resound had the same issue but the sim is the same. And when it freezes I mean the screen just stops updating. You can press the buttons but the screen will stay frozen until a battery pull. Thanks!
Click to expand...
Click to collapse
Yeah, see about getting a new SIM from Verizon then and see if that works since that's the only constant.
Just got a brand new rezound yesterday.. returned my last rezound for the same issue but they used my old sim. Idk what could be causing it
Make them give you a new SIM.
feralicious said:
Make them give you a new SIM.
Click to expand...
Click to collapse
Yea Ill pick one up tonight and update the thread. Hopefully that's the problem. Thanks for the suggestions fera
Didn't solve my problem.. I'm really out of ideas at this point and its so frustrating BC the phone is sick
I would try running the RUU and bring it back to stock and see what happens.
Yes I would also recommend relocking and installing the latest RUU and see what it does. If it persists you will be stock unrooted and should be able to have them replace it under warranty.
Sent from my ADR6425LVW using Tapatalk
I actually think the cause of my lockups were due to some buil.prop edits. Does anyone have the debug.sf.hw=1 gpu tweak in their rom? And if so are you experiencing any lockups? I ahve used the RUU and everything was fine but all these roms look to yummy to stay away from lol
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Chakker3D said:
Ive used CWM to install different roms over a couple months since I have gotten my GS2. Ive never had a problem with Bluetooth connecting and playing music at all. But I find that since I started running the latest ICS XXLPH roms its been an issue.
Or can switching many roms over a course of time damage the antenna? or hardware? Any suggestions?
I am going to revert back to my stock roms after I send this message. The only reason I am sending this before I try it is because nobody else really seems to be running in to this problem after searching the GS2 thread.
Ive tried a couple ICS roms and all cause my phone to randomly reboot when using BT paired with my stereo either on a call or streaming music.
When it reboots enough times it starts to corrupt the ROM/install. Because after a while it will start to just randomly freeze on its own forcing me to reset the phone.
Ive searched all over I havent pin pointed anyone having the exact problem as me so that is why I wonder if its possible to damage the BT device after multiple custom rom installs.
Thanks in advance.
Click to expand...
Click to collapse
You are using a leak or *beta* rom which is far from stable
And no installing many roms can not damage any hardware
Sent from my GT-I9100 using xda premium
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Chakker3D said:
Thanks for your response.
I am just concerned because like I said, from what I can tell, nobody else is running in to this problem.
Ive tried /format system along with full data/cache wipes. I wiped dalvik cache.
Im waiting for my phone to fully charge to put stock rom back on so I can test this completely.
But a bit nervous, because I need my phones BT as I am on the road often.
Click to expand...
Click to collapse
Having a similar, if not identical issue on latest Westcrip ROM. Near as I can tell, seems to be related to memory management: while on BT, RAM space drops almost 200Mb. While changing songs, or surfing the tracklist/phonebook, it can cause the RAM to reach a critical level. This causes the OS to crash and the phone to reboot (my case a soft reboot from the animation only) in order to create space. I would chalk this up to inefficient memory management by a beta ICS rom. Look for this to be sorted out in the future with official releases and custom kernels/roms.
Thanks for your response.
Yeah when I installed resurrection, I also ran in to that problem. I had no idea how to diagnose it. But it makes sense, bottling up the ram to the brink of reboot.
Thats what initially was happening to me, soft boot, took a few seconds and was back in. But extended crashes seemed to cause corruption.
Yeah so the XXLPH seems to have an issue. Because I also tried foxhound and got the same result.
I just got back in from testing my BT on my car stereo using my stock rom of KG2 and it played for 20 minutes and i chatted for 19 without any problems.
So I am glad it wasnt anything seriosu. But only reason I was concerned is I found nobody else to have the problem and I felt a bit isolated
But im reading the official ICS rom is out in Europe so im sure we will see some new roms out in the next little while.
Okay so this is my first post on XDA and I hope it's in the right section. Anyways I bought an HTC Incredible off a collegue of mine about two weeks ago. I got the phone and immediately rooted and installed a custom rom (MIUIv4 to be exact) I noticed after a lil while that the touch screen would randomly go berserk clicking things, calling people, etc (usually right after turning screen on) When the screen starts doing it I'd turn it off and back on and it would be completely fine. I thought to myself "maybe it's just a problem with MIUI and installed PONS CM7. I still had the same issue. Now whats strange about all of this is if I'm running an RUU or Stock based rom the screen NEVER acts up. I've read on several forums that this is a hardware issue but most people still experience it on stock roms, this is not the case with me. I won't deny that it could be a hardware issue, but it's an issue that can be solved with kerenl/dirvers/software. I'm wondering if I can use the drivers and software from a stock based rom to combat the issue and make custom roms run like they are supposed to. In all of my research I found this link which seems to be pretty promising but I don't know where to begin with it. Unfortuneately I can't post a link until I've posted 8 times, uuugh.
Edit: It seems the longer I run a custom rom the more frequently the issue happens.
If anybody is intrested in helping it would be greatly appreciated. I've been racking my head for over a week on this one. You can look up the blog I read on google. It looks like it could solve my problem.
Unresponsive touchscreen of Nexus S solved by tuning kernel
Like the title states, my phone started rebooting multiple times today, I just flashed Eclipse2.0 the other day. I havnt had any issues at all until now. any help would be appreciated. If more info is needed let me know exactly what/ how to get that for you!! thanks in advanced!!!!
p.s. Ive searched forums for a solution, none seem to be relevant to what I am experiencing.
I get random reboots on all JB ROMs. I think its a fact of life until an official kernel is released. Please correct me if I'm wrong about the kernal.
Sent from Novena A3..... it's on fire!
I actually had it a while back too, I was on Black star. I was still under warrenty and had other issues, got a new one and no problem until now.