SetCPU 216mhz Issue

[Guest dibbles]

Changing over to CM 7 and I have not had a "sticky" on my Vega since, and it has been on for a couple of weeks now. My wife is also using CM7 and with its built in overclocking it has been working a treat for us both.

[Guest ® Andy]

Must admit this one has been driving me mad for a couple of weeks now since I got my Vega. Haven't the foggiest if the problem occurs with the stock ROM since I'd wiped that within 5 minutes of getting the Vega home and put on Corvus5 instead. It took me a few days to realize that there was a regular problem since 1st off I'd put it down to the system "settling in" where I'd dumped a load of stuff on it. Then spent a while looking for CPU hogs when the go-slow happened, but of course couldn't see any. I wasn't running SetCPU, but did have JuiceDefender on with overclocking set on. Main reason for JuiceDefender is/was to control the wifi when the screen is off under Corvus5 since my Vega spends quite a lot of the day sat on the table off power.

Did jump to CM7 a few days ago to see if that had the problem, but must admit I wasn't immediately smitten and possibly saw the problem there, and so came back to Corvus5 by way of Paul's ROM (which was too much like stock for me ... sorry!). Thought I had everything singing along but the 216Mhz problem has been getting more regular. Had it with SetCPU and also with CPU Tuner. Just been running CPU Master because of the widget to show current speed, and just had that get stuck too :P.

I only finally noticed this thread ;) after searching to see why Corvus5 wasn't showing up any governors at all on the CPU apps. Still not seen a clear answer to that one? Does the Corvus kernel not containing any?

Think I might spend another hour or two jumping to try CM7 again tonight and stick with it longer!? Always painful since Titanium Backup never seems to want to do what it promises with Market relinking (not helped by the problem on CM7 with the My Apps going blank).

Edited June 15, 2011 by ® Andy

[Guest premieral]

Must admit this one has been driving me mad for a couple of weeks now since I got my Vega. Haven't the foggiest if the problem occurs with the stock ROM since I'd wiped that within 5 minutes of getting the Vega home and put on Corvus5 instead. It took me a few days to realize that there was a regular problem since 1st off I'd put it down to the system "settling in" where I'd dumped a load of stuff on it. Then spent a while looking for CPU hogs when the go-slow happened, but of course couldn't see any. I wasn't running SetCPU, but did have JuiceDefender on with overclocking set on. Main reason for JuiceDefender is/was to control the wifi when the screen is off under Corvus5 since my Vega spends quite a lot of the day sat on the table off power.

Did jump to CM7 a few days ago to see if that had the problem, but must admit I wasn't immediately smitten and possibly saw the problem there, and so came back to Corvus5 by way of Paul's ROM (which was too much like stock for me ... sorry!). Thought I had everything singing along but the 216Mhz problem has been getting more regular. Had it with SetCPU and also with CPU Tuner. Just been running CPU Master because of the widget to show current speed, and just had that get stuck too :P.

I only finally noticed this thread ;) after searching to see why Corvus5 wasn't showing up any governors at all on the CPU apps. Still not seen a clear answer to that one? Does the Corvus kernel not containing any?

Think I might spend another hour or two jumping to try CM7 again tonight and stick with it longer!? Always painful since Titanium Backup never seems to want to do what it promises with Market relinking (not helped by the problem on CM7 with the My Apps going blank).

There is a script fix for the market losing apps in cm7

[Guest dibbles]

market app fix for CM7 (saves the searching)....

http://forum.xda-developers.com/showpost.p...p;postcount=707

[Guest]

No frills CPU seems to be working okay for me on Corvus5

[Guest ® Andy]

market app fix for CM7 (saves the searching)....

http://forum.xda-developers.com/showpost.p...p;postcount=707

Thanks ... had seen that when I had CM7 on last week but was without root file manager with necessary built in text editor. Have since invested in excellent Root Explorer, and so when I put on CM7 tonight did the necessary change, cleared the market data, and all is working fine now.

Sadly tho' I just got a 216Mhz lock under CM7 too ;). I had just put SetCPU on there as a way of showing the current CPU frequency (any other suggestions of something that displays current CPU speed without actually tinkering with settings?), and so in the hope it was that which did it I'm now just running CM7 using it's own CPU control (set 216-1400 with performance governor) and we'll see how we get on!

[Guest Panayioti]

Thanks ... had seen that when I had CM7 on last week but was without root file manager with necessary built in text editor. Have since invested in excellent Root Explorer, and so when I put on CM7 tonight did the necessary change, cleared the market data, and all is working fine now.

Sadly tho' I just got a 216Mhz lock under CM7 too ;). I had just put SetCPU on there as a way of showing the current CPU frequency (any other suggestions of something that displays current CPU speed without actually tinkering with settings?), and so in the hope it was that which did it I'm now just running CM7 using it's own CPU control (set 216-1400 with performance governor) and we'll see how we get on!

I have found that using setcpu is the problem so my recommendation is to use cpu master from the market which is free and since i have used it has never had the '216mhz' problem. (Using Vegacomb)

[Guest premieral]

I have found that using setcpu is the problem so my recommendation is to use cpu master from the market which is free and since i have used it has never had the '216mhz' problem. (Using Vegacomb)

i too thought it was setcpu but it also happens with other cpu controllers so it cant be that simple, however it does do it everytime i switch to usb mode and use the usb??

[Guest ® Andy]

For 1st time ever I'm actually running stock 1.10 ROM. Been running CM7 for last few days but not convinced I didn't see slow down on that :-( Defo had some go slows forcing reboots but couldn't tell you if it was stuck at 216 since didn't have SetCPU installed to check with.

Borrowed a Windows machine & restored to stock quickly followed by Market etc..

Happy to give up on overclocking for reliability at mo & hope that a resolution is discovered in support of Vegacomb some time!

[Guest Katsunami]

We're between a rock and a hard place now.

Corvus5 is the best ROM available IMHO (if only because it does not show an x for your phone connection because of the removed phone apk's :)), but it has a bug in it's kernel; the tablet becomes slower than should be when run at stock speed. (Newbe5 explained that to me in another thread.) Using SetCPU or others to put the tablet at 216 MHz causes lockups.

I don't mind ditching CPU controllers and running on stock speed, but is there any fix for the kernel problem forthcoming?

[Guest]

We're between a rock and a hard place now.

Corvus5 is the best ROM available IMHO (if only because it does not show an x for your phone connection because of the removed phone apk's :)), but it has a bug in it's kernel; the tablet becomes slower than should be when run at stock speed. (Newbe5 explained that to me in another thread.) Using SetCPU or others to put the tablet at 216 MHz causes lockups.

I don't mind ditching CPU controllers and running on stock speed, but is there any fix for the kernel problem forthcoming?

The very few times I have had the 216 lock it has been when the Vega has been in standby for around 8 Hours. A reboot always sorts it. For me I can live with this no problem...

[Guest ® Andy]

We're between a rock and a hard place now.

Corvus5 is the best ROM available IMHO (if only because it does not show an x for your phone connection because of the removed phone apk's :)), but it has a bug in it's kernel; the tablet becomes slower than should be when run at stock speed. (Newbe5 explained that to me in another thread.) Using SetCPU or others to put the tablet at 216 MHz causes lockups.

I don't mind ditching CPU controllers and running on stock speed, but is there any fix for the kernel problem forthcoming?

Ironically after a couple of weeks running the stock ROM, I went back to Corvus5 yesterday. Basically got bored of the pedestrian stock ROM, had a fleeting dance with latest CM7 nightly which wasn't stable and so after 20 minutes before I'd fully restored things I put Corvus5 on. I've purposefully not got anything capable of overclocking on it, and will see whether I get any 216 Mhz slow downs.

I had seen newbe5's comment about benchmarks and a problem at 1Ghz and how bumping to 1.2Ghz was recommended, but TBH even at 1Ghz Corvus5 flies along compared with stock and CM7 and so I'm happy to live with it as is in the hope that I'll avoid the slow downs.

I'd also be interested to understand plans for solving the kernel problem!? Isn't the same kernel (or derivative of) used on VegaComb?

[Guest Katsunami]

Andy: I almost can't believe that stock Corvus is faster than other ROMs, provided other ROMs don't have a huge amount of background tasks. The timing problem slows it down considerably. The stock ROM, and Modaco R8 get a SmartBench 2011 value of 2895-2940, where Corvus only reaches 1771. So, Corvus only reaches 60% of the speed of the original ROM. After bumping the CPU to 1.2 GHz, the score almost reaches 3100. The speed bump of 20% on top of the stock speed would make me believe that Corvus would need to reach at least 2940 x 1.2 = >3500, however. (Don't know if thinking like that is OK; I'm not a tablet overclock guru.)

For what it's worth, I have switched to the free version of CPU-master.

It basically is a "set your lowest and highest speed" utility without any fancy profiles. (That is only available in the paid version, for €1.39.) I have not yet had any slowdowns. When I launch the utility, it dutifully states "1200 MHz". (The cpu speeds up for launching this, of course.) Then after a few seconds, it switches back to 456 Mhz. So far so good, for about half a day. Could it be that profile switching, or trying to do that, causes the problem?

Still, I would very much like to see a Corvus5 SP2 or patch that fixes the kernel bug. Then I'll return to stock speed, and be happy :)

(I did buy a subscription for the forum to get the R8 costumized ROM though, but in the end. I regret that a bit, becuase I went for Corvus5 in the end. I liked it better for several reasons... and I have learned how to take out stuff I don't need. I hope Nebwe5 and Corvus will benefit from the subscription too, or I might donate a bit to them too.)

Edited July 5, 2011 by Katsunami

[Guest DaWhite]

I'm not long off putting Vegacomb on, I do actually still get this 216 issue and a reboot sorts the problem out for me pretty much all the time.

[Guest Katsunami]

Most probably it will have the same issue, as Vegacomb and Corvus are both running the same kernel.

(Please note that this is just a guess on my part. I don't know that much about the internals of the Android kernel.)

[Guest Tucnak]

Still no solution for 216 MHz issue ? :-(

I have POV mobii 3G & GPS and problem with 216MHz with all roms (Ganbaro 1.0, VegaComb 1.6, ... ) :blink:

[Guest dibbles]

Have you thought of using the nightly CM 7 builds...? I have never had a "stuck" situation when using CM 7. Maybe it is because you can use the built in overclocking utility of the ROM without needed a 3rd party app..? It, for me, just works.

[Guest Katsunami]

I have POV mobii 3G & GPS :blink:

Swiftly in between... does 3G work with the Corvus5 ROM?

If it does, I may put the Huawei EM770 3G card (which POV claims to be using) into my POV Mobii.

[Guest arnookie]

I suggest everyone try No frills cpu from the market.

I have had no problems since using that. :O)

If a bunch of you try it and it works for you then we have found our fix. ;O)

[Guest Katsunami]

Two days ago I started using setcpu again because I had an idea. I created two profiles. One runs between 456 and 1200 Mhz for normal use. The other explicitly sets the cpu to 216 Mhz when the screen goes off. I did not have a sticky for two days. I have a hunch that the kernel sets 216 Mhz, making setcpu get stuck. Having setcpu set all speeds by itself, explicitly, may have solved the problem.

Please note that I cannot prove this. It's just a hunch. I might just have had good luck. Ymmv.

[Guest pjjames55]

I suggest everyone try No frills cpu from the market.

I have had no problems since using that. :blink:)

If a bunch of you try it and it works for you then we have found our fix. ;O)

I too have been plagued by the 216mhz issue, this generally happened a few times a day after waking my vega. This happened while using both setcpu and cpumaster, with or without profiles. I installed No Frills CPU three days ago and since then i have not had a single 216mhz lockup. So touch wood the problem hopefully has been solved, for me anyway.

Edited July 10, 2011 by pjjames55

[Guest simonta]

Learned something today.

The 216mhz thing is a safety setting and it makes sense.

If you overclock your device, select "set on boot" and the device can't handle the clock speed, you may experience freezes. If you power off your Vega without using the power off menu option, then setcpu assumes that your device froze and sets the CPU to 216mhz on boot to ensure that you can get back into it to lower the max clock and try again.

Possibly options:

1. Use another tool (although having thought about this, I reckon setcpu has the right approach).

2. Always shutdown properly.

3. If you are experiencing freezes, or other reasons to power off your Vega, lower the overclock.

Hope it helps..

Cheers

[Guest wasps]

This may not be good news, but I should share anyway.

A while ago I installed vegacomb1.7.

This was on top.of the modded Rom v1.

At that point I had no CPU software installed.

After playing with the vega for a while, I left it on charge all day.

That evening it was very slow.

I installed cpumaster and found that it was running at 216.

Therefore I don't think the CPU software causes the problem, however it does make sense for it to be a safety feature in the tablet if it think it has hung