Database Users

Random shutdowns?

Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App

kopykatkiller said:
Anyone else having issues with the phone shutting itself off at random intervals? It is happening on mine and I have to pull the battery in order to power it back on.
So far have rooted, installed su file browser, and system panel. Only other thing I have done is removed Amazon mp3.
Thanks in advanced, just want to know if I need to exchange my phone or not.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
This happen to me yesterday 3 times after the phone's screen was off for more than 10 min
I uninstalled setcpu and it never happened again so far.

Ok maybe it is a setcpu setting that is defaulting wrong. Anyone with setcpu installed that is not experiencing this? If so, what are your settings?
Sent from my SGH-T959 using XDA App

i also had this happen to me w/ setcpu active, i have yet to have it happen w/o setcpu

Happened with setcpu to me to. Removed it no problem since.

Same as everyone else. W/ SetCPU it happens. W/o SetCPU it doesn't.
Just sent the dev a message to let him know of the situation. http://twitter.com/MINUS_Stl/status/18719463969

Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.

Ya know. I did actually change it to ondemand seeing as that's what I always used on my G1. Gonna reinstall and see how we do. Will definitely report back. Thanks.
UPDATE: 1 hour in on 'conservative' and all is good.

I probably have to put a warning or something for Galaxy S for ondemand. It's probably a kernel flaw for that.
For now, it looks like conservative is 100% stable, haven't had reports of crashes on it.

Yeah, I'd say conservative is it. Thanks, bro.

Yes, before the reply about the conservative setting I had messed with it and set to that. Wanted to verify before posting, but as stated that appears that is the key. Thanks guys.
Loving this phone by the way.
Sent from my SGH-T959 using XDA App

coolbho3000 said:
Are you guys changing the scaling governor? From early reports, the Galaxy S phones can't take ondemand, you have to stick it to conservative.
You can "simulate" ondemand by changing freq step in Advanced to 100%.
Click to expand...
Click to collapse
I had SetCPU set to Conservative since I installed it. Yesterday it randomly powered off 6 times. I found this post and deleted SetCPU and am currently using Overclock widget. So far I haven't had it power off.
Has anyone else had this issue while having it set to conservative?

Yes! I changed my charger and it hasn't happened ever since.
Sent from my SGH-T959 using XDA App

i have also noticed that if i set a profile so that the cpu has a max of 400mhz while screen is off it will crash on me randomly. i have to keep it at at least 800mhz. It has just started doing this.
also does anybody know if it is dangerous to run in performance mode at a constant 1000mhz? it makes my phone super fast(obviously) but sounds dangerous making it run at maximum power constantly while the screen is on.

I've never used or installed SetCPU and my phone was shutting down by itself as well and had to do the battery pull to get it back on. I found it to be the "Power saving mode" in the display setting. Ever since I turned it off it has not shut down.

I also experienced this once when I try to install setcpu on my vibrant running bionix-v 1.2. Uninstalled it and it never happend again. =)

Just use the stock kernel.
Sent from my SGH-T959 using XDA App

this used to happen to me all the time so I got a replacement from tmobile but it continued to happen. It finally stopped when i rooted and flashed my phone

This thread is quite old, and while I do appreciate the contributions, it was long ago when this was posted and was dealing with a very early version of the over-clocked kernel. Please let this thread die, so that current ones maintain priority.
Sent from my SGH-T959 using XDA App

at least you guys are getting something. My phone shuts down 1-3 times a day. it is whether its rooted or not, customized rom or not. It just like to go to deep sleep really bad. Hopefully I can exchange it. But i just get my gps fixed, i dont know if i will get a new one with crappy gps.

Overclockable cpu... pro and cons?

hi my wildpuzzle version is 8.0, but i'm waiting a bit before upgrading to one of the latest.
I'm waiting also because i'd like to know a bit more about overclocking the cpu.
On one hand, i'm sure the phone will be smoother and faster, but on the other hand? Are there any problems, or effect i should be aware of?
One more thing, there is a list with 6 different kernels with oc enabled. How do i choose which one to flash? Which is the best?
thanks in advance

pro:
your phone will be faster
battery usage during idle is potentially decreased
cons:
your phone might become unstable as the hardware will be running outside of tested specs
battery usage during active usage is increased
The different kernels all have different levels of overclocking. If you try one and your phone becomes unstable (random Force Closes or restart) try and flash it with a slower kernel (lower maximum frequency).
There is no danger of directly harming the hardware in the phone from overclocking. However if the phone is pushed so far it is becoming unstable data corruption might occur.

ok that's what i was afraid of.
is this (damaging the hardware) a real possibility? Or is it just in theory?
Than is the phone really faster? I mean, is it worth to overclock the cpu (considering the possible damage of the processor and the various improvement)?

Sorry about that...
I missed a "no" in there. I meant to say that your phone will not explode into a ball of fire or otherwise become unusable from overclocking.
If it is pushed to far it will simply hang or crash and need to be rebooted.
I can notice a rather big difference. I mean going from 528Mhz -> 768Mhz. That's almost a 50% speed increase.
If you require a rock solid telephone and do not want to mess with stability then don't over clock. If you on the other hand like experimenting just go ahead and try it.
just remember to make a nandroid backup that you can go back to in case your phone doesn't work properly after installing the new kernel.

if we overlocking the wildfire , can i play divs with rockplayer or auther?

If I have WPR 8.06 installed and the 0050kernel, is it ok to try installing new kernels to test? And if its unstable, just test a new one? (have a previous nanbackup that I done directly after rooting the phon).
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!

The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.

Akerhage said:
* Do I have to wipe everything, installing the wpr everytime, or just update the kernel without having to do anything else? cheers!
Click to expand...
Click to collapse
You can flash kernels back and forth. You don't have to reflash the entire ROM for that. Just make sure you have a working nandroid backup first in case your phone doesn't want to boot.
Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
Yes, in Theory. In practice computer CPUs have temperature monitors that will limit CPU speed to prevent it from rising to high.
In the context of a phone it will be to hot to handle before the temperature becomes high enough to do any critical damage.
Yes, the life time of the electrical circuits will be shortened but a mobile phone will become outdated. Besides the phone is only active for very short periods of time compared to computer.

Skye Menjou said:
The Wildfire temperature will increase greatly in theory.
If the Wildfire hasn't got it in its design to cool that amount then it will damage the phone, same with computers.
Click to expand...
Click to collapse
with a 768mhz speed?.. i dont think it will result to an intense heat that makes the device unusable.. it will make more heat than usual but its tolerable enough..

@OP
Please post in the appropriate sections. This thread belongs in the General Section not Android Development.

[Q] Fascinate Won't Wake from Sleep/Screen Off

My brother and I both got Fascinates this month. Both are rooted, but only mine is upgraded to DJ05. We are both loving the phone except, both of us have a problem where the screen/phone will not wake up from sleep sometimes. It will just show a black screen, it even happened while talking on the phone today, the screen didn't wake when I got off the phone. I've done a few searches and on some other phones people suggested setting SetCP to at least one higher then the minimum when it's in screen off mode, but I just tried that and had the same issue 5 minutes later. With all the development going on, I'm hoping that someone may have found a fix for it. Does anyone else have this problem or know of a solution? I apologize if there is another thread in the fascinate forum about this, I did a few searches, but didn't see anything.
Thanks,
Ryan

You could help yourself by stating what rom version and what specific kernel you are using. And if you are using a task killer and or power managment app.
good day.

Sorry if I wasn't clear enough. We are both rooted, but my brother is otherwise running stock. No task manager, just Setcpu. I upgraded to DJ05 and installed JTs Superclean w/non voodoo and rom. But I wouldn't think that'd be the problem considering he's running stock. Maybe it's setcpu? If so is their another comparable manager for battery life that someone might suggest, I can see if that fixes it?

Setcpu offers no benefit to devices using a stock kernel only good for over clocked kernels. If the problem at hand didn't start until installing setcpu, then you have your answer. I myself do not use any power management apps so I can't speak for them.
good day.

Did you by any chance install something that adjusts the brightness of your screen?

If your running Setcpu and your having problems waking up the phone, are you running a profile for the screen off? You can't run profiles on Sammy phones, they don't like it.

No, no brightness apps.
Yes, I was running a profile for screen off and stuff. That was the whole point of Setcpu, I thought, so you could reduce it when the battery started getting low and the phone wasn't being used. Thanks for the info, I uninstalled it. I guess that's the problem. Only time will tell though. Do you know of any other reputable apps that would be similar to Setcpu?

Why not try geeks last kernel? I believe it was uv and should help battery life if that's what you're going for.

I would, but people have had some issues with them from what I hear, besides he's no longer developing them or supporting them, so sooner or later I'd be changing anyway. Maybe I'll check out juice defender.

You can keep setcpu, just don't use any profiles lol and keep it on conservative
Sent from my SCH-I500 using XDA App

Does it actually do anything for you though to help save battery life without the profiles?

Just because he isn't deving for the sf doesnt mean that his kernels are worse than the stock one...I use adryn's 12/17 test 2 and get amazing battery life..14 hrs at like 60-65% but it's voodoo and you will prob not want that.

setcpu will change the ramp up/ramp down speed...more time at max when you need it more time at min when you dont...i don't think it will help nearly as much as proper kernel

Epic help needed!!

So i have been going crazy! I started with ACS Frozen 1.1.0 and it was suffering from the "not waking up" problem. I assumed it was the overclocking so i went through all the crap with playing with the volts and settings. Well i never got the problem to go away so i switched roms to 1.1.1 (I think) and i got the same thing! So i wend to Bonsai v4.1.1 then to Emerald envy. Now im on SRF 1.2 final. All do the same thing!! The phone will go to sleep and not wake up with out a battery pull. Some roms make it take longer than others but at the most i get like 5-6hours before the lock screen (on 1.1.0). On this 1.2final i am getting almost immediate shut down!!! Non of them work!! I thought because the 1.2 final was pretty much a stock kernel i would not have a problem... i was wrong. The phone other wise runs great! So should i go back to stock? any suggestions??

Does it start doing it right after you flash a rom? Or does happen after you've installed all your favorite apps?
Sent from my SPH-D700 using Tapatalk

Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.

I dont know if it happens before or after.. i always set it up... ill try flashing it now and not setting anything up. But if i cant use my apps then what the point?
I stooped over clocking it about 4 flashes ago. The last few times i did not even let voltage control get root access to see if that was the problem and is still freeze's! Also i read up and tried every configuration i could for overclocking before giving up on it.
Maybe its my apps? Or awd launcher? But that seems doubtful to me.
Anybody point me in the direction for returning it back to complete stock? If running it for some time with non of my apps does not work then i am going back to stock.

This will get you back to stock.
http://forum.xda-developers.com/showthread.php?t=1052813
I would try flashing a rom again without apps then as things look good start installing stuff. For me there was a battery widget that would lock up my nook color and on my Epic I had music stutters.
Sent from my SPH-D700 using Tapatalk

I flashed the 1.2final rom and have been adding 1 app every 4 hours. I have not has any freezing. Hard to believe a app would crash my phone... I will let you guys know what app ends up crashing it.
But now that I know its a app I will try over clocking again... and recommendations for a kernel for this frozen 1.2final rom?
Sent from my SPH-D700 using XDA App

Using setcpu?
Sent from my Epic 4G via Tapatalk

Some phones can't handle certain clock speeds. Sounds like your CPU may be biting the dust, or just got the bad end of the silicon.
Sent from my SPH-D700 using XDA Premium App

Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.

hayzooos said:
Either stop using SetCPU's ondemand setting and switch it to conservative, or just don't use the application at all.
The minimum for your phone seems to be higher than 100mhz, so adjust accordingly. Just remember, the ondemand setting doesn't maintain the minimum you set, so that's why you have to use conservative.
Or switch kernels and that might do it for you as well. Genocide kernel is a popular choice, but even that dev suggests using conservative, not ondemand, even though it does maintain the minimum when you set it on his newest kernel.
Hope that made sense.
Click to expand...
Click to collapse
NissanNick said:
Well the phone has worked all night! I loaded youmail and that seems to be what crashed it. But now i am thinking it was not a app at all... it was my backup. When it crashed after loading youmail i reinstalled the rom and just loaded app.. I did not use Mybackup pro to load my data. The phone seems fine as of right now. I have not overclocked it once yet. I hope it was my backed up data because at this point i just want a phone that does not need to be reloaded every few hours.
Click to expand...
Click to collapse
I wasn't saying don't use any apps, I was saying not to use SetCPU with ondemand. Maybe it was youmail, maybe you just had some corrupt data. Who really knows.
Google doesn't go through the verification/testing process like Apple does, so you'll get some rogue apps out there that just plain suck, and can cause issues with your phone. Maybe that was the case.
Either way, it sounds like you got it pretty much figured out. If I ever restore a backup (not a nandroid), I usually only put data back to games, not any other apps, as there's no real need. Maybe for an email app to keep the settings, but even that's not hard to set back up.

Phone freezing after long charge on Franco Kernel

Apologies if this is covered elsewhere, but I have been struggling to trawl through all 1000 pages on the relevant thread as I can't get the search terms to get the info!
Basically, when I leave the phone overnight charging, in the morning I cannot turn it on unless I press and hold the power button and volume down to reset the device.
Other than this it is great in terms of being able to adjust the colours and the battery life seems better.
I have tried both the nightly and stable versions..

What ROM are you using?
Sent from my Nexus 4 using xda premium

murtezahu said:
What ROM are you using?
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
I am currently using the stock ROM but could change to a custom... (I am learning as I go at the moment...)

Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.

LOL
Sent from my Nexus 4 using xda premium

sounds like a classical case of sod. do you undervolt?

and rolmply
simms22 said:
sounds like a classical case of sod. do you undervolt?
Click to expand...
Click to collapse
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!

vindikleuk said:
Sounds like your phone is having trouble to wake after a deep sleep. I'm guessing it's caused by a (probably: too) low cpu frequency.
Did you use any app to change the cpu frequencies while asleep, or did you undervolt your cpu?
Also, which version of the kernel are you using? I suggest you stick to M1 for more stable results.
And after all, it might be a bug in the kernel. The people in franco's thread are more than willing to help you if you supply as much information as you possibly can. Kernel version, your adjustments to it if any, etc. I haven't seen this problem happen to anyone before in the last days (oh yea, I read every page of that thread...), so don't be afraid to ask for some help. But for now, I suggest you update to M1. If you're already on M1, feel free to ask your question in the thread.
Click to expand...
Click to collapse
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.

goldeneye243 said:
No, I do not undervolt. The only changes I made were to gamma settings. Having said that I did change the power setting but changed it back. I have rebooted the phone so I will see if it happens after the next deep sleep.
Thanks for the help so far, much appreciated!
Click to expand...
Click to collapse
do you use the pgm slide to wake app?

simms22 said:
do you use the pgm slide to wake app?
Click to expand...
Click to collapse
No, I don't - Should I, or is it possibly what is could have caused the problem?

goldeneye243 said:
No, I don't - Should I, or is it possibly what is could have caused the problem?
Click to expand...
Click to collapse
its a possible cause of sod if you had it installed.

goldeneye243 said:
Thanks for the reply.
I am currently using milestone 1.
As far as I am aware I only made changes to the colour as I am still learning the controls as I go. I have restarted the phone to see if it helps.
The only app that I am using that could be to blame is battery guru, so if it persists, I could try disabling that.
Click to expand...
Click to collapse
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:. From my experience, you wouldn't need any battery management apps when you're on franco's M1 anyway - using common sense to save your battery should suffice.

vindikleuk said:
You're using the exact same set-up I am, and I'm haven't had any of the trouble you talk of. Disabling battery guru might be a good idea. As it's an app from Qualcomm itself, I wouldn't be surprised if it's set to mess around with the stock kernel's settings. If that's the case, then your kernel is obviously not the kernel that Battery Guru was programmed to mess with! Uninstalling it to see what happens next would be a good step :highfive:.
Click to expand...
Click to collapse
I will do that if I have not already got it fixed with the reboot. Battery guru is still in learning mode so possibly isn't messing with the kernel yet but is the next thing to try...

Alrighty, let's hope it'll get figured out.

vindikleuk said:
Alrighty, let's hope it'll get figured out.
Click to expand...
Click to collapse
Well, it turned on OK this morning, so hopefully fixed...
I guess I will only know in a few days time when I have got more confidence...

I had another SOD so I have reset all settings (installed nightly version 110) and started again -
The only changes I have made are to the gamma settings and changing the governer to conservative to see if that gives me a longer battery life.
Will see how it goes....

I had some more SODs with 110/111 so I changed to 121 and the battery life did not seem as good.
Takes a while to work out what is going on when it only happens once a day...

I still get occasional SODs with battery guru disabled so i guess it is either the kernel or possibly the ROM... I will try on the support thread....