SET CPU problems with root? - Vibrant General

Aside from being able to Wirelessly Tether my 3G connection from my Vibrant, I wanted to also control my CPU speeds. But with SET CPU, I tend to come across a particular problem. I would underclock to 100000 (min&max) with the screen off, but as a result, the screen won't turn back on and I would have to take the battery off and restart my phone. Clocking it to 400000 (both min and max) screen off leads to the same problem. Is anyone else going through the same situation? If not, what are you setting your CPU to, in regards to both screen on and off?

I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.

lqaddict said:
I have it set to 400MHz max/100MHz min for screen off, and it wakes up just fine so far.
What is your Governor setting? I was told to put it in "Conservative" for Vibrant.
Click to expand...
Click to collapse
Yeah I have all my profiles set to conservative. Do you guys think it has to do with the priorities, cause I have all of them set to 100.

It could, since there is no telling how to prioritize the settings, hardware/software might get confused.

you know I just noticed I got the same issue, sort of.
I have multiple profiles setup, and one is for charging via USB 800max/100min.
If the screen is off (400max/100min), and I connect the USB cable, guess what happens, three finger salute gets it back, hmmm.

OK I got it working for those who are having the same problem as I. All I did was I made my screen off frequency 200max/100min. For both charging and battery use, I have my cpu set at 1000max/800 min. It works flawlessly and I am noticing an increaSe in battery life...
Sent from my SGH-T959 using XDA App

OverClock?
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.

Halieus said:
I used SET CPU on my G1 and really loved the new life it gave my old hardware. I would like to open it up and see what my Sammy Vibe can really do. Is there a way to get some real OVER clocking?
Battery life is really not an issue for me so far.
Click to expand...
Click to collapse
we need a kernel that will enable it. its apparently not possible on the stock kernel...

I have been having the exact same freezing issue when the screen times out, I'm unable to revive the phone without pulling the battery. I have tried many different setting in Setcpu including those posted here. I finally just uninstalled it and everythings right again. Best to avoid this app for now.

Hey man i did that and i still did not work any other way to set it up.

Vibrant wont come out of Blank Screen
I used Set CPU and put it to the max 1000 and then the max on the other readings it forced closed and after the tmobile and Galaxy animations it goes to a blank screen.

Yeah, I uninstalled it after a week because it was just too unstable. I was getting freezes several times a day, which is unacceptable. Other people might have better luck, but my phone did not like it at all.

So far the only way I can get the program to work 100% is to not have any screen off profile. If I just set it to 1200 max - 200 min / conservative it works fine. Yet once I use profiles and screen off at 100, 200 or 400 it won't turn back on. Every morning it's the same thing, battery pull.

I have similar problem. As long as I am not using "Profiles" at all it is fine. Playing with profiles setting for a while, but not being able to make them 100% stable.
Another thing, if your screen does not come on, you don't have to pull the battery out. Just keep holding on/off button for 5-7 seconds, it'll reboot. It's not a complete freeze, I believe only display system (whatever it is) fails.

Stuck at Recovery Mode
Guyz,
I have firetrap sugar on Spice Mi300. Installed Set CPU.
Tried entering the recovery mode, the phone gets stuck at 1st screen with a line "Enter recovery Mode" displayed on top.
Please help.

Related

nueDynamicClock experiences? (Over-/Underclocking)

I've found this neat tool: http://www.nuerom.com/BlogEngine/page/nueDynamicClock.aspx
Has anyone used this on their X1 and did you notice any changes? I don't think you can use it for overclocking an X1. But I'm thinking about setting clock frequency to 19 MHz on Suspend, to get more out of my battery.
I've got this tool, not sure if it made much of a diff when I overclocked it to 528
( or just set it to the base clock speed since they have it underclocked @ 400 mhz ), wanna try the lower speeds, but not sure whether it will have a negative effect.
I uninstalled it..
found that any apps (such as gps cycle computer, audiomanager etc) that played with the screen on didn't work very well when the speed was lowered. Also had quite a lot of instances when the screen was corrupted after coming out of suspend..
I use it since yesterday, so i can't say anything about changed battery lifetime. But i got it working only after setting min-clock to 384MHz. With lower settings the phone got frozen in standby mode after a while. I'll try it for a few days for testing a (hopefully) enhanced standby time...
PS: i use 384MHz in suspend mode and after idle time of 5s, didn't change max clock or voltage settings (all to "auto"). Maybe setting idle time to 2s would care more battery life, but i don't know how the cpu will stand changing the clock so much often...
Been using it since v1.0. Seems to have some battery gain (10% over 8 hours better) - set to default 528MHz, down to 256MHz idle and 122.98MHz on suspend and screen off. Needed 123MHz for clean audio playback in standby.
Only screen corruption (inversion) issues I had was when set too low (19MHz) at standby. Now using these settings for a few days and no issues so recommended for use with TFlo3D2.
Unless you're running WM6.5 with WM7 titanium - makes it very slow to respond out of standby.
And it doesn't overclock - 528MHz is default clock speed.
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Mark A Cilenti said:
I wanted to try this but my X1 says no, here is the screen shot, due to security, I press yes and my X1 does a soft reset, then I try the program again and get the same thing.
View attachment 180763
Has anyone with a standard Official Rom 2 got this to work, and how ?
Click to expand...
Click to collapse
I have a standard R2A ROM and it works for me. Can't tell you what's the problem with your installation, though.
Anyway, I found since I installed the tool my device is worse than before. It sometimes interrupts audio playback when display is off (ALthough frequency in that case is still at 3xx MHz!) and sometimes it takes very long (5 secs +) to suspend and to wake up again. So I think I'm gonna remove it.
I only turned down the voltage to 1.1 instead of 1.325 running on 528MHz.

Vibrant turns off in sleep mode

Hey evweryone,
Found a VERY strange issue, that seems to be affecting Captivate users as well. This is my second phone that has had this issue, so its not isolated.
The phone works fine when using it, but when it goes to sleep, occasionally (more and more frequently it seems) it will actually turns off. Meaning, when I pull the phone out of my pocket, its off. Has occurred 3 times today, and I'm SURE i didn't accidentally hold the power key.
First, I thought it was the OC kernel, so I reverted to JAC's non-OC kernel, still turns off. Reverted to stock kernel, still happens. I have a slight hunch maybe SetCPU may be causing it to sleep incorrectly, so I un-installed that.
Anyone else run into this issue? Its a PITA when your phone randomly turns off, cant rely on it at all. Thanks!
EDIT: Phone was ON while sitting on my desk while I was writing this, tried to wake it up....it was off
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Puushiki said:
It happened to me too, and I believe it was because of Set CPU, I had it set low when it went into sleep mode and it would shut down, and i would need to remove battery and start it up again. So I just deleted the profile and it seems fine now.
Click to expand...
Click to collapse
I will try that and see. Anyone else have this issue on any Galaxy S based device (Captivate, Vibrant or Generic Galaxy-S)?
Oh btw, I have the Samsung Vibrant
Puushiki said:
Oh btw, I have the Samsung Vibrant
Click to expand...
Click to collapse
Okay, confirmed by one user. There is a large number of captivate users having this same issue, and a discussion about it in a SetCPU forum (Link ).
No problems here, stock ROM + RyanZA using SetCPU since day one.
Two profiles: conversative
Battery <100%: 400 min; 1000 max
screen off: 400min; 400 max
Are you guys using SetCPU for OC'ing, or for scheduling?
I was having the same issue, wasn't sure what it was and was going to return my Vibrant, and with that in mind had wiped the phone and gone back to stock. Due to a delay in getting to the store, I did re-install things (hey, I do need my phone) and found that the issue had stopped. I did have SetCPU on originally and have not re-installed it, but it's difficult to recall if I had SetCPU on before or after the issue started. I suspected it could have been SetCPU and since I didn't really feel the need to use it, I just didn't bother to install and and wanted to see what would happen.
It did happen again yesterday, but the phone seemed to just lock up on me while I was using it (was as I was using Navigate, got to my destination, locked up, then shut off, more or less), so it might have just been another fluke due to overheating or something.
Anyway, the problem that I had was that I couldn't get the phone to come back on without having to remove and replace the battery. But fortunately, other than yesterday, the issue has not happened since the past Friday (where it happened 4 times that morning vs once per day the 3-4 days prior). The inability to turn it back on might just be an issue with my phone (and it only happens after this force shut down).
ytj87 said:
Are you guys using SetCPU for OC'ing, or for scheduling?
Click to expand...
Click to collapse
Mainly for stress testing, as the OC kernel doesnt need to be configured to OC, its already running at 100/1200. Mainly for scheduling and stress testing. Occasionally for detailed info about CPU (temp, current speed, etc). Hopefully this issue\bug can get worked out, cause SetCPU is a GREAT app.
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
hockeyrcks9901 said:
I can almost guaruntee that it is SetCPU causing the issue. Make sure it is set to "Conservative" mode and try not to use the "Screen Off" profile.
Click to expand...
Click to collapse
Had NO issues today, seems SetCPU was the culprit. Thanks!
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Puushiki said:
Well I have SetCPU for Screen Off Conservative at 400, and haven't had a problem yet, so I'm not sure
Click to expand...
Click to collapse
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
I have had the same problem and am using SetCPU. I love it, but this shutting down in sleep mode thing is driving me crazy. Gonna try to turn off notifications and move to conservative and will report what happens.
I use SetCPU regularly on my Captivate and only see issues if I change the governor or polling interval, or if I use profiles.
Sent from my SAMSUNG-SGH-I897 using XDA App
hockeyrcks9901 said:
I think it's kind of hit or miss. Some people have no issues with it and others do. My first phone would not wake from sleep if I was using the "Screen Off" profile. I haven't tried with my second phone as I've noticed it seems to be really good at lowering **** speed on it's own.
Click to expand...
Click to collapse
**** speed aye?
Don't use setcpu!!!!
Sent from my SGH-T959 using XDA App
xaisomboun said:
**** speed aye?
Click to expand...
Click to collapse
lol. That's swype for ya...
Typos and other gibberish courtesy of Swype
I have this problem several times a week. The phone is NOT rooted. What are my options for curing this problem besides rooting?
Thanks for the help.
Samsung Vibrant, Android 2.1, T-Mobile
I read somewhere that Galaxy S users should NOT use conservative and use on demand instead for this reason... not sure though.

Rom'd HTC Hero randomly reboots

Hey guys,
A few weeks back I rom'd my HTC hero with VillainRom 12 and it was working great for awhile. Now however it crashes all the time, or just freezes up and I have to remove the battery.
I have the phone over clocked to about 650mHz. The battery temps seem fine.
Has anyone else experienced this problem before? Any way I can do a debug on my phone to find out what's crashing?
It's really starting to annoy me considering that I use my phone for my business and it's not good when a customer calls and my phone dies and reboots when I go to answer a call.
try overclocking to a lower extent
it might be because your phone cannot handle ur clock speed
(my MAX clock speed is 672... it simply crashes with 691 or higher)
You were absolutely right. It was clocked too high.
I turned it down and now it works great.
Thanks for the tip.
652 seems to be my max.
710 is my max, I can't go below 192 either or the phone starts to have a fit, I wanted to use a lower clock speed in "screen off" mode, but I'll have to stick with 192

[Q] SC 2.2 NV => 2.4 V & same problem

If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
jbjarko said:
If I lock my phone, sometimes it won't unlock. It essentially just shuts down. I've reinstalled 2.2 once, and just went to 2.4 last night. When this happens, I have to pull the batter and restart. And yes, it does this with both versions. I wiped cache, etc upon installing the ROM as well.
Click to expand...
Click to collapse
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
jenisiz said:
When you say it won't unlock...is haptic feed buggy and it seems unresponsive and sporadic?
Click to expand...
Click to collapse
Not really, seems normal to me. Should I try turning it off, and see if that fixes it?
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
kdaz said:
By any chance, would you happen to be using setcpu? I ask because I have noticed this happening on any rom I use, but changing my setcpu values for when the screen is off has pretty much solved it.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Ok, downloaded setcpu, what specs should I put it at?
jenisiz said:
I've been using setcpu with every setup on this device and haven't ran into any problems. Only problem I would see with this, is if you set the levels way to low...that will induce locking up the system.
Click to expand...
Click to collapse
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
kdaz said:
well thats basically why i was asking..if i set mine to 200 max and 100 min when screen is off, it sometimes doesnt come back on. i currently have it set to 400 max and 100 min when screen is off and havent noticed any problems.
Click to expand...
Click to collapse
IMHO...that's really low.
Where do I set it for screen off? All I have are two sliders?
jbjarko said:
Where do I set it for screen off? All I have are two sliders?
Click to expand...
Click to collapse
you have to go under the profiles tab and enable then you can set different profiles.
Still doing the same deal. SetCPU is at 400-800 during screen off. Haptic feedback is off.
Any ideas?
I'm not even running SetCPU and I get this happening.
Anyone have any more suggestions? It's not a huge deal, but it sucks watching my battery drop 10% every time I have to pull the battery and reboot.

A simplest solution for battery issue

Hi there,
I was very unhappy and was about to go back to 2.2.2 because the battery life was horrible after OTA upgrade to 2.3.4. Here is how I resolved the battery issue on my Atrix 4G. This was the simplest way for me and works great.
Pre-Condition:
-You must not a heavy user because this method is going to slow down your phone's performance.
-Rooted phone.
1. Download CPU tuner (free) from the market and install it
2. Under Settings (this will option will pop up when you run the app for the first time)
-Set "User Interface > Experience Level" to Power User
-Do not check "Enable CPU tuner"
3. Set Frequencies under Current tab to
Min: 216 MHz
Max: 312 MHz (you can increase this if you wish but it will consume more battery)
4. That's all
Although the performance is really slow, I still get calls, email and text.
When I need to do something, I just open up the app and increase the Max. frequency to 1000. And then, change it back to 312 MHz when I am done.
I do battery calibration once in a while with a free app from the market.
*** My battery is still at 80% after 12 hours of use. ***
Set your max to 216, it will last even more!
Actually to get the best battery life, I recommend turning off the phone. It will increase the battery life even more.
I paid for juicedefender a while back and didn't really use it until recently but it works great. Shuts off wifi when not in use, and turns off data when the screen is off. I still get texts and calls with no issues. I tried setting my max to 216 and it took like 10 seconds for the screen toturn on when getting a call....and a couple of times the calls went right to voicemail.
Phoneguy589 said:
I paid for juicedefender a while back and didn't really use it until recently but it works great. Shuts off wifi when not in use, and turns off data when the screen is off. I still get texts and calls with no issues. I tried setting my max to 216 and it took like 10 seconds for the screen toturn on when getting a call....and a couple of times the calls went right to voicemail.
Click to expand...
Click to collapse
I do all those things manually.
Sent from my MB860 using XDA App
I was too but I thought being it was automatically done whne the phone times out...it works great if you forget or don't have time to do. Just thought I share it...my battery is hit or miss with different ROMs but this seems to help without scaraficing time or functionality.
This is probably why I won't go GB on the Atrix. I had enough run with it on my SGS. Battery life is way too important to me...
Sent from my MB860 using xda premium
Try to disable/uninstall the CPU control software such as SetCPU and let the system to control the CPU. You may find the solution.
Sent from my MB860 using XDA App
Thank you for all the comments guys! It works for me at no cost so I just wanted to share the tip with others.
Yes, and turning off my engine and coasting down hills saves me gas.
Sorry, I just can't see crippling performance as a solution.
I use Temp + CPU Pro to monitor my CPU and most of the time it stays at 216, it switches up to 312, 456, then to 1 ghz occasionally but most of the time is at 216.
Over all I would have to give the 'lil fella credit for managing CPU speed automagically pretty well.
PS: Carlharsch I was visiting a vendor in China, and on the interstate the driver would cut the car off on hills, and I leaned forward to look at the limo gas meter and it was on E! I asked the interpreter WTF are we out of gas? Why the H*ll did you pick me up with an empty tank! She lied and said "oh no, the gauge is broken, haha". Of course I laid into the management at the company and at the end of the week the car was full when we left.
Talk about a nightmare being stranded on the interstate in deepest Guangdong.

Categories

Resources