Related
Does anybody have any idea what would cause my Epic to shutdown several times a day and won't power back on without pulling the battery. I have tried doing data factory resets, Odin back to stock, different Roms and it keeps doing it. I've purchased a new battery and it still happens with the new battery. Anybody have any ideas or words of advice to help me fix this problem? Thanks in advance.
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
downyours said:
Are you rooted and running a overclock or underclock? If you have it set to 100mhz with the screen off some phones have trouble waking up from that. Also, if you are rooted, try going in to your CWM and wiping battery stats. Its under advanced. Make sure you do this when its fully charged.
Click to expand...
Click to collapse
Yes its rooted. I have never messed with clock speeds, so it shouldnt be an issue with that I hope. Ive also tried wiping the battery stats as well in CWM. It first started when I flashed Syndicate Rom Frozen a few weeks ago. So I have tried several other roms since then and I still have the same problem. I even purchased a new battery and still have the same issue. Im lost in this one. Im not blaming the problem on Syndicate either, I was just letting you know when I first noticed the problem.
Sent from my SPH-D700 using Tapatalk
What happens when you open the keyboard? Does anything light up? Or does it just continue to stay off?
It stays completely off and blacked out when I open the keyboard. I have to pull the battery in and out to get anything.
Sent from my SPH-D700 using Tapatalk
And youve gone completely back to stock without root. No difference?
Also, the kernels that you have run, are they overclock kernels? What about the one your running now? If so, I think they are overclocked from the get go and possibly set for 100mhz on the low end. You might want to try and find SetCPU on the website here, (there is a free one) and set it to raise the speed on the low end. Also add a profile for screen off that changes to 200-400. It would be free and relatively easy to try.
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
dazednconfused1144 said:
Yeah I have used Odin to go back to stock. Then flashed new roms. I will try that program out and let you know. I'm using the new Viperrom Synergy now and its still happening. Ill try the SetCPU and let you know if it works. Thanks for all of your help.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
I might be wrong, but I think the newest ViperRom is set by default at 200-1000. To reach the 1200 mark, you have to use SetCPU. Same for going under 200 (which is known to cause problems for some folks when the screen turns off).
I just wanted to say thanks for the help. I wanted to update you and let you know I finally found the problem. For some reason it had something to do with restoring my apps and data through Mybackup Pro and Titanium. I finally just started taking out different steps of what I was doing and finally just downloaded all of my apparently directly from the market and the problem went away. No more blackouts. I don't know why that would cause that problem, but it did. Thanks again for all of your replies and help.
Sent from my SPH-D700 using XDA Premium App
My defy is having one problem. Its actually random. Sometimes when a call comes, i am not able to pick it up. The touch simply wont work. Then i have to cut the call using the power button and call them back.
Sent from my MB525 using XDA App
Are you using SetVSel? If yes then what settings are you using?
Im getting rid of mine because of the same issue. It seems to randomly break during some incoming calls. Sometimes the touch sensors stop working, sometimes it fails to to bring up the answer/reject lock screen and just brings up the normal one. Other times it goes into a frenzy of randomly pressing the buttons and touch screen all by itself while ignoring anything I do to try and prevent it. Its a great device, but as a phone its been crap for me.
I dont use setvsel because it caused issues with the graphics on my defy, even at 850 it caused corruption and freezing on anything 3d. I had the call answering issues before rooting and unstalling setvsel btw
Sent from my MB525 using XDA App
LetoKynes said:
Are you using SetVSel? If yes then what settings are you using?
Click to expand...
Click to collapse
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App
obscurant1st said:
Yes i am usi.g setvsel. So u r saying it could be the problem? Nywy by settings what you meant? Is it the voltage levels and frequency?
[email protected]
[email protected]
[email protected]
Sent from my MB525 using XDA App
Click to expand...
Click to collapse
Yeap that's what I meant.
Well I'm not entirely sure, but I remember someone mentioning he had trouble picking up calls because his frequency was too low but yours seem fine.
Have you tried disabling SetVSel to see if it works OK without it?
XDA app? where did you get it?
Sometimes i cant able to lift the call
even i am not able to lift the call sometimes the touch is not working at the time by clicking the power button then the call is ending.
Yeah, i got it from the market.
Sent from my MB525 using XDA App
But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?
obscurant1st said:
But its not happening always, till now it has happened for me like 5 times in 3 months! so i dont think i will b able to check it after switching the setvsel off. I will have to stop it like 1 month or some to confirm it! any other option?
Click to expand...
Click to collapse
happens here too, no root, no overclocking tools. plain stock defy but happens
with launcher ex as well. mostly when on the charger or been not in use for a
few hours.
oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/
obscurant1st said:
oh ok, so its not the problem of overclocking/undervolting! So I'm happy. I thought like I will have to remove the root and all!
But still, why is this even happening??
Will it get fixed on the froyo update?? :/
Click to expand...
Click to collapse
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.
philofax said:
in the german android community it's only listed as an eclair problem so hopefully it is solved n froyo. i am still waiting for the update.
Click to expand...
Click to collapse
Wow, thats a real relief. Thanks man.
Sent from my MB525 using XDA App
I have this problem with mine. Totally stock and it didn't happen until AFTER I updated to Froyo. It has happened about 5 times now.
You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|
vikrambharadwaj said:
You sure it will be fixed in froyo? Yesterday my boss was calling me to discuss something imp and I could not pick up the call because of this damn issue, I had to disconnect the call with the power button and called him back :-|
Click to expand...
Click to collapse
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?
someAZdude said:
Did you miss my post? I never had this problem until AFTER I updated to froyo. Now, I am experiencing it on occasion. This would lead me to believe that something else is amiss.
Are you guys using a screen protector?
Click to expand...
Click to collapse
, then it could be something else.
And well, I am not using or will ever use a screen protector! I simply don't like them. idk why!
I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk
D3rR0fl3r said:
I think its just a problem with motoblur, since i'm using custom roms i never had that issue
Sent from my MB525 using Tapatalk
Click to expand...
Click to collapse
But tbh i don't think Indian defy has motoblur installed in it! At-least I haven't seen it yet on my phone!
i have indian rom , but i have faced this issue...and i dont know why it happend....faced 2 to 3 times now...hoping to get an solution.....one solution is just lock and unlock it again by press and release pow button i think it solves the issue of random screen freeze
I have I really annoying problem, when I use sense roms (only sense, not AOSP) my phone freezes almost instantly when going to sleep.
This results in the phone not ringing when people call me, and first receiving texts after i reboot the phone.
And the only way to reboot it, is to remove the battery.
If anyone knows what is causing this, please let me know how to fix it, this problem have made me miss many really important calls.
Thanks in advance
i had the same problem with official 2.2 sense rom (don't know with 2.3, i switched yesterday) , but only when i was on a place with bad network.. In big town like Paris no problem, but when i moved to smallest town with bad network i experienced same freeze...
When you hit a button only the button backlight turn on?
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
KasperHermansen said:
Exactly, only the button backlight comes on.
But I have fine reception at my location
Thanks for the reply
Click to expand...
Click to collapse
Did you use setcpu?
Usually it happen when you use setcpu and you make screen off profile 128 mhz.
Sent from my HTC Desire using XDA Premium App
Not anymore, because I had the same idea that that could be the problem, but it still freezes
Thanks for the reply
Today it has frozen 4 times.
And every time with massive battery drains, about 15% in a short period of time.
I have slide that random reboots like once a day for no apperant reason . Beed doing it since cm6.1.1 and now I'm on cm7.1 so would like to know what mightt be wrong... info : rom- cm7.1 / hotboot- 0.52 / latest radio / s-on .. if anyone can help I'm open ears
Sent from my T-Mobile G2 using XDA App
Any one with info on this your insight will be very helpful
Sent from my T-Mobile G2 using XDA App
can you give us some more info? like whether your phone's overclocked? to what frequency? what apps were running? etc...
Well I had setcpu on the cm 6:1:1 and clocked 768 I beleave it would run right then it would reboot like 2 times a day so I took of the oc and set cpu and the reboots were now random like once a day or one at all .. so jumped to cm 7:1 everything is good so I set the built in oc to 768 and it was fine till like with in a few hours it would reboot again reboots are random but like once or twice a day so removed oc and back to the stock and only once a day on none at all ... apps that I use the most and leave runinf facebook, voice, talk , sd-booster at bootup set at 1024, music most of the time, also advanced task manager by rechild, ... if more specific info is needed I'm be glad to give to help me get closer to solve the problem .. thanx
Sent from my T-Mobile G2 using XDA App
how about battery temperature? how hot does it get when you're using/not using the phone? also, by randomly reboot, does it reboot when you're using the phone or just whenever it wants?
Battery doesn't heat up at all so normal temp ... by randomly I mean when it wants.. it in the pocket and u just feel the buzz of the reboot .. again no oc and just like 3 apps running at most also have cache clener ng runing at 12hour intervolts ... also ran permistion fix threw rom manager but not sure if the fix will stick since its s-on
Edit : forgot to say wifi alway on even when sleep since the phone does not have a data plane
Sent from my T-Mobile G2 using XDA App
hm... idk but perhaps it's the wifi that's causing those reboots. then again, if you don't have data plan, not using wifi will just turn your phone into paper weight.
Would having it s-on be a issue in any way?
Sent from my T-Mobile G2 using XDA App
Not at all, I have S-ON and only have reboot problem occasionally when I use wifi, battery gets too hot, or something.
Oh ok ... so would their be a fix for the wifi cuz this is getting annoying I have reflashed like 5 times in hopes it was a bad flash.. and don't really see a big library of roms that ain't sense roms ...
Sent from my T-Mobile G2 using XDA App
I have had this issue with CM7 as well. Some nightlies are better than others.
To reproduce just keep toggling your wifi. Eventually the phone will reboot. I use to see "kernel panic" messages in the logcat file but the last time I captured logcat for this issue I did not see any message about a kernel panic.
Where would we post a bug for this?
ovar said:
I have had this issue with CM7 as well. Some nightlies are better than others.
To reproduce just keep toggling your wifi. Eventually the phone will reboot. I use to see "kernel panic" messages in the logcat file but the last time I captured logcat for this issue I did not see any message about a kernel panic.
Where would we post a bug for this?
Click to expand...
Click to collapse
Oh ok so wat u are suggesting it might be cm rom related issue ... would the wifi fix flooting around here help with the issue or have u tried the wifi fix ?
Sent from my T-Mobile G2 using XDA App
I have not tried the WIFI fix. I would be curious if other can get the reboot to happen by toggling WIFI repeatedly.
Hi,
Sometimes when i click Home button Middle-Bottom of the screen.
physical buttons's Backlight turning on but screen doesn't come up.
I have to try at least 5-6 more times for screen to show up.
What is wrong with my phone ?
It's just sometimes really annoying..
Thank you for reading.
Best Regards.
UP
Using the latest FW ?
From my sexy LT15i
Do you use any custom Rom/kernel?
Sent from my Xperia Arc using XDA
Seems like extreme lag to me. The next time it happens check with a program (like OS monitor) the cpu usage. The situation that you described happened to me once, the MtpApp process was using 100% cpu and i couldn't use my phone properly until i rebooted it.
I faced a similar issue on a Xperia Ray
Its hardware i guess, flashing stock didnt work for me
What i say is you should flash stock FW
Thank you for all those answers !
I'm using DoomKernel 2.32.9 ( I Guess it's 19v )
2.3.7 Modded GB Deluxe Edition ( http://forum.xda-developers.com/showthread.php?t=1533332 )
It was happening more before i started using Modded GB Deluxe Edition.
But it is still happening, and still a lot annoying..
Thank you for reading.
Best Regards.
If your using a program like SetCPU or no-frills cpu control make sure that the minimum clock frequency is not set to 122MHz. Try set it to atleast 245MHz. I tried setting the "screen off" CPU to the minimum on SetCPU before in the hope to get more battery life, but whenever I wanted to wake the phone there would be a 2-3 second lag before the screen showed up. I hope this helps.
I guess this will work.
remove your SD card, connect it to a PC & format it, Insert it back.
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
oojjii said:
@adielee
I wasn't using anything like SetCPU back than. So it can't be the problem.
Thank you for your answer.
@Kajendran
Okay, will try it. Sounds like a good idea.
But why is this hapening ?
Click to expand...
Click to collapse
Maybe you can try flashing the stock kernel to test? i tried flashing a non-stock kernel a few times before and results were mixed and never perfect for me (don't really know why). Sometimes it would randomly glitch and the screen would turn black for about 1/2 a second or something. Wifi would sometimes be intermittent despite flashing the modules for some as well.
I'm not experienced enough to fully understand but I'm thinking that it could be a regional thing? I mean, how signals differ between regions?
So.......
Did it work........