Guest DaWhite Posted May 31, 2011 Report Share Posted May 31, 2011 Ok, Apologies in advance I did try a search and found a few responses to this but nothing conclusive. I've got Corvus on at the moment and it's fantastic. I also got setCPU and when it's working, it's also extremely good. However, every now and then setCPU gets "stuck" at 216mhz until I reboot after which it's back to it's normal self again. Previous searches suggest setting up profiles (which I haven't tried yet, at work) and using the specific .txt file corvus provides which I already have but the slowdown still occurs. Has anybody conclusively fixed the problem for themselves? If so please could you outline what you did, it'd be a great help for me :D Thanks! Great work BTW on this forum, it's made the Vega a real bargain. Again, sorry for what might be a question already answered. Link to comment Share on other sites More sharing options...
Guest CoWPlagued Posted May 31, 2011 Report Share Posted May 31, 2011 It has been covered in lots of different posts, but I've yet to see anyone point to an actual cause. For a lot of people SetCpu works fine with no issues, but I found that I was getting a lot of 216 lockups in both Corvus5 and vegaComb and since moving to CPU Tuner I've not had any. Give it a go. Link to comment Share on other sites More sharing options...
Guest DaWhite Posted May 31, 2011 Report Share Posted May 31, 2011 Thanks CoWPlagued, I will try CPU Tuner tonight and report back if it resolves the issue! Link to comment Share on other sites More sharing options...
Guest dibbles Posted May 31, 2011 Report Share Posted May 31, 2011 When You write that the speed gets stuck at its minimum do you go the the Set CPU tab and try the short and long benchmark and then note if the CPU speed in Mhz actually increases...? I use the Fuji Vega ROM... http://android.modaco.com/content/advent-v...ghz-25-04-2011/ ...with SetCPU and, as yet, it has not happened for me. If it does continue maybe you could set the minimum a little higher than 216mhz, although I would not know if that would work..? Link to comment Share on other sites More sharing options...
Guest DaWhite Posted May 31, 2011 Report Share Posted May 31, 2011 @ Dibbles, I have set the minimum higher than 216 in the past and this doesn't help. I haven't tried however running a benchmark, I will try this thanks. The way I "notice" that the CPU is so low is that the whole tablet becomes very sluggish, usable, but no where near as slick and smooth as normal and even webpage rendering takes 4 to 5 seconds. I used to use FujiVega too, It's pretty good, I didn't have setCPU at the time so cannot say for sure if Corvus has caused the issue or not, consensus seems to be that it's certain users of setCPU rather than the ROM they are using. Link to comment Share on other sites More sharing options...
Guest CoWPlagued Posted May 31, 2011 Report Share Posted May 31, 2011 Benchmark performs as expected at 216mhz .. slowly. I've tried a few different things, including setting profiles to try and keep things fast. No matter what you try it ignores any effort to force it out of 216mhz until a reboot. I have had another vega lock at 216Mhz without any cpu apps installed, so the cause isn't SetCpu, but for some people it seems to aggravate the issue. The only thing I found from all my messing, was that it never happens when the tablet is in use, only when the screen's off, so it's probably related to the fact we don't have the correct code to put the Tegra chip to sleep properly and in some cases it's not responding to the wake up command. Link to comment Share on other sites More sharing options...
Guest unclebob31 Posted May 31, 2011 Report Share Posted May 31, 2011 For me it was because I had more than one CPU setting app on the Vega. Removed them all, reinstalled one, no more problems. Hope this helps UB31 Link to comment Share on other sites More sharing options...
Guest WWEpsp Posted May 31, 2011 Report Share Posted May 31, 2011 i have the same problem, and i've looked for it a lot just a few days and give up, now im just rebooting the tablet. Interested in a solution too... :D Link to comment Share on other sites More sharing options...
Guest vulpy Posted May 31, 2011 Report Share Posted May 31, 2011 Had the same issue, unistalled SetCPU and issue is gone... Link to comment Share on other sites More sharing options...
Guest DaWhite Posted May 31, 2011 Report Share Posted May 31, 2011 Ok, got home from work and pput cputuner on, removed setcpu. I've spent the evening doing other things and waking the vega intermittantly, so far so good. Plus cputuner actually seems better that setcpu anyway. I will post back in a few days either way with results for others needing a solution. Link to comment Share on other sites More sharing options...
Guest WWEpsp Posted May 31, 2011 Report Share Posted May 31, 2011 Had the same issue, unistalled SetCPU and issue is gone... the first thing i tried but no solution. Maybe tomorrow gonna try CPUtuner... Link to comment Share on other sites More sharing options...
Guest dibbles Posted May 31, 2011 Report Share Posted May 31, 2011 (edited) @DaWhite Not sure if it might help you but you might want to check out the SP 1 upgrade that has been made for the Corvus ROM as there are some changes which have been made that could be of benefit to those using that ROM. The reason that I posted what I did is that when you do use SetCPU there is a tab that you can use to do the benchmarks I noted and thus note to see if the 216mhz clock is indeed stuck at that speed or if there is something else hogging the CPU. As you do the benchmarks you can read the speed of the CPU in mhz. If you run a task manager type of application which shows what is running and what is consuming the CPU it might also offer some information. However since your last post, and your initial response to mine, it does seem to suggest that the issue is more to do with SetCPU and some users. Thinking about what you wrote in your first post I had noticed a sluggishness when I used the Corvus ROM (on an odd occasion) and, as I had always used SetCPU with my San Fran phone, I had it installed from the start of using Corvus. I just used to reboot the tablet not thinking of a possible relationship with the Vega and SetCPU. As I was not aware of the possibility of the CPU being stuck at 216mhz I never checked that out to see if it was or not. I have not, as yet, seen it happen with the Fuji ROM, albeit this ROM has only been installed for a day. I am also using the latest version of the VTL launcher (1.6.5) rather than the Launcher Pro I was using with the Corvus ROM. The VTL launcher I have found is particularly good. Edited May 31, 2011 by dibbles Link to comment Share on other sites More sharing options...
Guest xzyk Posted May 31, 2011 Report Share Posted May 31, 2011 (edited) ditto on the 216MHz stick. I have removed all cpu apps but behaviour is still as described; i.e. it occassionally just stick after coming out of sleep. I will try cpu tuner, although i have a suspicion it won't be so siimple ! EDIT: I have now tried all the available cpu apps, still getting the 216 lock. One interesting point, i have tested with cpu tuner,Menu>setup>system>check compatability, and that is telling me there are no working governors in this rom. It lists the 3 non-working ones as Ondemand, Performance and Powersave, funnily enough also suggests that the rom does not support them and i should load CM7. Now i'm even more confused. I think the ultimate test is going to be a fresh install of some other rom that supports OC. Edited June 1, 2011 by xzyk Link to comment Share on other sites More sharing options...
Guest DaWhite Posted June 6, 2011 Report Share Posted June 6, 2011 Ok, sorry for the lack of response but I've been checking carefully that CPUTuner has worked. Over the past week of normal use, even letting the tablet sleep on and off, even overnight, I've not had the 216 sticking. So my finger is pointed at SetCPU. Reading other responses I'm sorry to see that removing SetCPU hasn't worked for others 100% :D What I did exactly was to remove setCPU from the system, deleting data on the way, I manually removed the setcpu.txt file, rebooted, downloaded CPUTuner and fired it up, set a 400mhz min and 1.2ghz max and it's been hunky dory ever since. I'm running Corvus 5 for now until flash is working in VegaComb. Hope this helps, my issue is resolved now so I'm a happy bunny, I'll stick around this thread though in case I can help others. Link to comment Share on other sites More sharing options...
Guest MaxiP Posted June 7, 2011 Report Share Posted June 7, 2011 As a slight aside, I've been running SetCPU on my Wildfire for a while but recently noticed that (a) system would run very slowly / freeze and would need to be reset and (:D battery was draining in 6 hours instead of 24+ So I removed SetCPU and Viola! that has seemed to do the trick. I've installed CPU Master(Free) to check when I need to and so far, it's like having my old phone back (albeit overclocked). Link to comment Share on other sites More sharing options...
Guest Dave Marchant Posted June 7, 2011 Report Share Posted June 7, 2011 As a slight aside, I've been running SetCPU on my Wildfire for a while but recently noticed that (a) system would run very slowly / freeze and would need to be reset and (:D battery was draining in 6 hours instead of 24+ So I removed SetCPU and Viola! that has seemed to do the trick. I've installed CPU Master(Free) to check when I need to and so far, it's like having my old phone back (albeit overclocked). I have replaced SetCPU with CPU Master on my Vega (Corvus 5 sp1) and that also seems to have stopped the drop to 216MHz. Link to comment Share on other sites More sharing options...
Guest DaWhite Posted June 7, 2011 Report Share Posted June 7, 2011 Consensus seems to be that setCPU is maybe a bad recommendation, maybe it can be removed from the CorvusROM page (Which is why I bought it) ok, it's only like 2 quid, but it was a wasted 2 quid :/ Link to comment Share on other sites More sharing options...
Guest newbe5 Posted June 7, 2011 Report Share Posted June 7, 2011 Consensus seems to be that setCPU is maybe a bad recommendation, maybe it can be removed from the CorvusROM page (Which is why I bought it) ok, it's only like 2 quid, but it was a wasted 2 quid :/ SetCPU is free if you are a member of the XDA forums :/ Link to comment Share on other sites More sharing options...
Guest DaWhite Posted June 7, 2011 Report Share Posted June 7, 2011 Oh Bottom. My bad. Link to comment Share on other sites More sharing options...
Guest MaxiP Posted June 7, 2011 Report Share Posted June 7, 2011 Oh Bottom. My bad. Nobody is saying that SetCPU is bad or doesn't work, just causes some issues on some HW. I have SetCPU running quite nicely on the Vega but it fails on my Wildfire. Link to comment Share on other sites More sharing options...
Guest Tucnak Posted June 15, 2011 Report Share Posted June 15, 2011 Nobody is saying that SetCPU is bad or doesn't work, just causes some issues on some HW. I have SetCPU running quite nicely on the Vega but it fails on my Wildfire. I have Ganbarou 1.0 ROM and 216MHz issue (Point of View, Tegra, 3G+GPS version) :-( Always after suspend is CPU set to 216MHz, then is there big problem with waekup device ;) - SetCPU uninstalled - setcpu.txt deleted - reboot - no others CPU apps - ok, CPU is 1000 MHz - after suspend and wakeup device - still have 216 MHz issue :-( - installed CPU Master Free (set 1000/1200) - no others CPU apps - reboot - after suspend and wakeup device - still have 216 MHz issue :-( Any solution ? thanks Link to comment Share on other sites More sharing options...
Guest Splinter82 Posted June 15, 2011 Report Share Posted June 15, 2011 All I can suggest is try wiping and re-flashing your ROM, then starting afresh just using CPU Master. That's what I had to do; full wipe of everything (dalvik, cache, etc) then just using CPU Master seemed to do the trick. Link to comment Share on other sites More sharing options...
Guest mahousaru Posted June 15, 2011 Report Share Posted June 15, 2011 Personally I found I get the sticky CPU with both Corvus5 and Paul's at least once a day coming out of suspend. I tried both SetCPU and CPU Tuner and still suffer from it. I even tried no CPU clocking program. I didn't notice it when I was trying VegaComb, but I only had that on for half a day. Been trying out stock 1.10 with Ganjaman's market mod and I haven't had the problem for over 3 days without a reboot. Link to comment Share on other sites More sharing options...
Guest buyadroid Posted June 15, 2011 Report Share Posted June 15, 2011 I have the same issue with my Shuttle P10an01 unit. Worked fine before vegacomb, thou. Link to comment Share on other sites More sharing options...
Guest premieral Posted June 15, 2011 Report Share Posted June 15, 2011 i had the problem when using setcpu so moved to cpumaster, on another thread on this topic somebody suggested they only got the sticky when in host mode so i tested this and low and behold within 12 hrs stuck at 216, however for over a week now in slave mode no sticks at all. i am still running vegacomb and have changed nothing so maybe that was a cause? also why does it stick at 216 when my minimum speed was set to 412?? it obviously ignores the cpu controller and looks at a some controller a little deeper embedded? Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now