Sometimes when I set my phone down - regardless of battery level - my epic shuts itself down - anyone seen this issue - boots right up when I notice it is off but no shut down sound or any other warning - any ideas? his has happened on multiple roms, stock, SRF, a couple of others - thanks
Are you under clocking and/or undervolting your phone at all? Mine was doing this like 3-4 times a week. I was underclocked to 200 on Twilight 1.1.1 using conservative setting.
I haven't experienced a shutdown since I reverted back to stock lowest speed of 400. You may want to try that or jump to a different kernel.
Related
Is anyone using SetCPU with gingerbread?
I'm using GingerVillain 1.5 but I can't seem to find the right profiles with SetCPU.
Oc'd @ 1,2 Ghz without profiles.
Because when I use the screen off profile, my screen sometimes won't turn on.
Screen off - min 245 max 1200
Can someone help me finding the right profiles?
Share your user experience.
In my experience and many others too, the profiles are not needed. The only profile you should ever need is a temperature profile and that's only if you really have it cranked up.
Having a screen off profile is always bad since switching to another profile doesn't happen instantly - there are polling intervals involved and until the next cycle runs your phone will still be using the screen off profile. That makes the phone slow which causes SetCPU to take longer in switching profiles, bogs down the cpu and it becomes a vicious cycle for a few seconds (sometimes a couple minutes). All the while it's draing your battery because the cpu has to work harder. Even regular profiles eat the battery due to the constant querying of the systems status and processing power used for that - which is the main reason you'll hear people whining about their battery life (some aren't effected as much).
Profiles are just not a good idea except for a temp profile for those that oc to the higher GHz (probably 1.4+).
You could try using cpu tuner instead. Gives you way more options.
CM 7
You have a lot of options with cpu tuner.
What triggers and/or profiles do you use?
My screen on/off has been working fine with CM7 nightlies before and after the RC1. I've been using SetCPU with a normal profile of 1017max/245min and a screen off profile of 365max/245min.
I think your issue is with overclocking. Idk about Gingervillain but as far as CM7 goes lots of people are having issues with the on/off animations and wakelock issues when overclocked over 1ghz. Try using your profiles and clocking at or under 1ghz and see how things change.
Not sure why anyone would really need a higher clock than 1ghz but what do I know. I dont see any slowdowns at 1017mhz and I feel that anything faster than that would lead to heat or battery issues?
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
thanks bro, i OC'd to 1017 and there are no issues
ibemad1 said:
Yes, screen off profiles work. But they drain your battery faster than if you have no profiles.
Sent from my T-Mobile G2 running Cyanogenmod.
Click to expand...
Click to collapse
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
martonikaj said:
I'm not so sure about this. Have you tested this at all? Starting using screen off profiles of 365max/245min have really increased my battery life, especially when my phone sits idle for a decent amount of time. I don't think you could see more battery life by leaving the clock at 1ghz while the screen is off.
Click to expand...
Click to collapse
Every kernel that I know of out there drops down the clock cycle when the screen times out. The reason not having the screen off profile saves the battery is because SetCPU isn't constantly sending requests about the phones state and then checking that against your profiles to see if it meets the parameters set in them.
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
KCRic said:
Now it could be a bit different for you. You might have a different set up or different apps that make having a screen off profile useful (ones that constantly update or run in some way). You just have to watch your phone for a few days and get an app that keeps track of that stuff so you know which route to take.
Click to expand...
Click to collapse
This is very true. It is definitely hard to make a blanket statement because no two people have the exact same setup. All I was saying is what I've been doin with the screen off animation and I've been having pretty solid battery numbers.
ok so im running the STOCK GB but im rooted and have been running gingertiny 9/29 ran into rebooting issues.. phone constently reboots after 20 mins of use. usually when this happened before like on stock kernels the battery temp would rise up to 104 but i kept eyes on the temp and it never goes over 78.4 F
not overclocking cpu im actually running at about 625 mhz but issue still occurs
SO with that being said i need help finding either a better kernal or trying to find solutions with this one.
i went back to complete stock and rooted to see if i still have this issue
any help will do thanks!
These questions belong in the Q/A section. This has zero relevance to development.
Now:
1) pull the battery then place it back into your phone.
2) Charge it awhile to make sure you haven't dropped a considerable charge during the bootloops.
3) Turn your phone on and move your clock speed towards 998400 (stock clock speed) via setcpu or however you underclocked.
This bootloop is likely due to you being underclocked so low. If you want, flash Tiny's latest kernel from 9/29/2011 to bring yourself up to date.
Was your min clock speed underclocked below the stock 245000? I had random reboot issues when I underclocked my min to 128000.
Having your max_freq set at 628 or whatever it was shouldn't cause reboot issues. You're phone should be rock-solid stable at a speed like that. I'd suggest taking a look at your voltages.
I've never run that kernel so I'm not familiar with what the voltage table looks like, but it might very well be that your voltage is too low. If your max_freq were higher, the transition through that clock freq would probably be too brief to cause an issue. I don't know if that kernel has sysfs enabled, but if it does, upping the voltage at that step .25 volts should cure it.
Min speed was at 628 even switching back to stock kernel still having issues I'm not sure what can be the issue I only last few mins playing any games or watching anything all speeds are stock
Sent from my ADR6300 using XDA App
Sounds like it's time to start wiping stuff.
I've got the E4GT. My phone will no longer turn on, show any sort of notification light, no sounds are made, etc. I'm pretty sure it was caused by underclocking the CPU to 800mHz but I've done this in the past with no issues. I set it with RomToolkit (and have had success going from 500mHz - 1600mHz) with the PowerSave on 500mHz min -> 800mHz max. I had my phone reboot to save the changes, and now it doesn't even seem like it's attempting to turn on. It is fully charged (at least 90% when I had it reboot).
I've just got this phone recently (so exchanging it might be an option). I'm running the LoStKernel 1.0.0.8 experimental kernel with StarBurst 1.9.8r and the ICS animations mod.
A mate of mine suggested using a jig but I don't think it will do much as the phone won't even boot to download mode.
Thanks
--
FIXED:
I took out the battery, held the power button for 10 seconds, put the battery back in and turned it on like normal. Mentioning so someone else can find it quick in the search.
I have heard that if u completely drain the battery to nothing, remove the SD card and plug it in and turn it on that it boots
Sent from my SPH-D710 using xda premium
Just rooted my phone a week ago and installed setcpu and a new kernel (made for 4.0.2 - and I quadruple checked that 1) I am definitely on 4.0.2 and 2) the kernel is definitely made for 4.0.2 (it's Faux's 4.0.2 kernel).
With that out of the way, here's my issue: with SetCPU installed, my phone is a slow, laggy mess. When I uninstall the application, my phone is fast, zippy, and all is well. It doesn't make sense given the context. More details below.
Specific things that lag especially bad are the following: 1) very slow screen wake/unlock (without any screen-off profile set/enabled and with the phone at stock min/max CPU frequency and ondemand and interactive governors, and also when underclocked and overclocked and in any combination you can think of); 2) homescreen performance; 3) typing; 4) switching between apps; 5) answering phone calls
I have tried using Setcpu with and without screen off profiles set and enabled, I have tried using the phone at stock clock, overclocked to 1.35ghz, and underclocked to 920mhz, and in all situations and combinations, the phone is slow, jerky, and a bit laggy. I also played with different scaling governors (interactive and ondemand mostly), and had the issue regardless of the governor used. I have not messed with voltage or anything else.
This issue has persisted over three days now, it happens regardless of how many times I've rebooted the phone and uninstalled/reinstalled the SetCPU application, etc. In short, there seems to be nothing I'm doing wrong on my end (or so I think) to explain this issue. And every single time I uninstall SetCPU, my phone is a speed demon again.
I have never had this issue on any previously rooted phone using Setcpu. Also, yes, I wiped cache AND dalvik cache before flashing Faux's kernel. I am not new to Android, cell phones, rooting, flashing kernels, etc. I can even use ADB without problems.
So, hopefully I covered all my bases. Anyone have any thoughts on why I might have been experiencing this issue?
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
T.J. Bender said:
Having some major headaches with my Note 2 right now. I'd previously had System Tuner set to cap screen-off frequency at 800MHz, with the pegasusq governor still selected. That was causing heavy drain (1-2% per hour) while idle, so I tried yesterday evening to scale it down to 200MHz with the powersave governor for screen off. It worked in the sense that my battery stayed flat at 67% overnight, but the phone took forever to come out of sleep so I could turn off my alarm clock, and then it started some type of fresh torment where it would freeze at the lockscreen and need a battery pull to reboot.
I switched the frequency to 500MHz this morning, but it's still locking up. Struggling to boot, too. I'd really rather not go back to 800MHz and pegasusq, but will if I need to. How do you guys have your screen-off behavior set in System Tuner, and has it caused you any problems? I'm on stock rooted, by the way, debloated by myself a while back.
Click to expand...
Click to collapse
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
P1 Wookie said:
I don't use system tuner, but in setcpu my screen off profile is set for 200-500 with pegasusq/cfq. I use almost no battery when my screen is off, and the wake up time is no slower than stock.
Click to expand...
Click to collapse
Thanks for that. I had to restore (luckily I'd done a Nandroid yesterday!) because the system wouldn't boot past the Samsung splash. I've been anti-Juice Defender for a while here, but it seems like a decent chunk of the problem with my battery has been wlan_rx_wake, most likely caused by network traffic. That's what I get for letting my wife share my phone's wifi router instead of leaving her on the house.
Much as I hate to do so, I've put JD Ultimate back on my phone in hopes that its control over wifi and data will prevent those wifi and data wakelocks from happening. Hoping that 500 max with pegasusq (I'd put it back at 600 after restoring) will alleviate things.