2nd core clock speed - Xoom Q&A, Help & Troubleshooting

Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.

ggrammer said:
Is there any particular reason the second core always drops down to 216mhz? This happens with any custom kernel I run, currently running moray with electra kernel at 1.5Ghz using pimp my cpy to OC.
Click to expand...
Click to collapse
when it's needed, it goes to the required frequency...

sounds reasonable but I will notice some lag and stuttering while I am using the xoom, i will open os monitor and the second core is sitting at 216, i move it manually to 1.5Ghz and the tablet is more responsive...
Edit
Sorry I should have been more specific about the situation. When I say the 2nd core drops to 216 I mean the max frequency drops to 216 so the 2nd core does not clock up any higher unless I manually intervene.

same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.

okay i see wat u mean...i just checked and i'm getting the same results... it sits on the min freq, all laggy, then when i manually set the frequency, it's super responsive like it shud.... i'm over-clocking to 1.6 btw

burgi400 said:
same on my xoom with tiamat 2.2.2 and setcpu. i have two profles , screen off with 216-456mhz and other with 216-1200mhz. only the first score is over clocked after switched on, the second stucks at 216-456mhz. i contacted the developer of setcpu someting around 2 weeks a go, but no solution till now.
Click to expand...
Click to collapse
I don't think that it strictly a SetCPU problem. I also have an Advent Vega and have used SetCPU to overclock it. Had almost the same problem, except both cores were stuck at 216Mhz.
Tried multiple overclocking apps and have had the same problem with all of them. Device fine until it goes into sleep mode, CPU stuck at 216Mhz when brought out of sleep. Even setting the minimum setting to 456Mhz still resulted in the CPU being stuck at 216Mhz on wakeup.

so i guess the big question is whether it is the kernels (I've tried a few) or in the way these apps OC a dualcore processor...It makes me wonder about the OC apps though, they were all built for single core originally and in each of them you only set 1 max and 1 min speed. OS monitor is the only app that displays both cores, at least that I have used, but it doesn't set an OC value at boot. Maybe if one of the smart devs on here could comment maybe even just to shed some light on this

Is there no solution to this issue yet?
Is it a tegra fault/problem?
Is it a Kernel issue?
Would flashing back to a stock kernel fix it? (if that is even possible...)

Related

[Q] Ondemand 800-1300Mhz Shorten Phone's Life?

I placed my SetCpu main profile(when screen is on) to ondemand from 800mhz to 1300mhz. I really like the performance boost for when playing flash or websites that have flash. I'm kinda worried though... do you think my phone will last at least a year with this kind of overclocking?
Should be fine...people are clocking much higher..plus I notice the cpu seems to settle into the overclocks...I could never get it to boot on 1.3 or 1.4 and after about two weeks on 1.2 I could get to 1.4 and stay on it....

[Q] My device keeps powering off when the I put the screen to sleep.

For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
supadupadoug said:
For some reason since this morning after a full night of charging everytime my screen goes to sleep or I pus the power button to put the screen to sleep the device completely powers off. Last night I did flash infusion to oc/uv but had several issues and just kept the the device clocked at 12k and did slight uv. Im using setcpu and have a profile setup for screen off but I disabled in hopes to remedy the total poweroff. Any suggestions? How can infusion be removed?
Click to expand...
Click to collapse
Flash community kernel your getting sod or try removing your Oc UV settings
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Ok thanks. What is sod by the way???
supadupadoug said:
Ok thanks. What is sod by the way???
Click to expand...
Click to collapse
Sleep of death
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
oh lol im learning slowly but fa showly.
supadupadoug said:
oh lol im learning slowly but fa showly.
Click to expand...
Click to collapse
All good
Infusion kernel is great kernel but your settings are going to be trial an error play around with.UV that's usually the probably with sod
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Question about uv. is less best ie -25? and what does disabling the various clock speeds do?
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Thanks I will give that a try. to oc really isn't my goal just to improve battery life. Right now seems to be working ok @12k with frequency uv @75-50
jdbeitz said:
Try using setcpu to throttle your frequencies. If you're having sod that usually means your phone isn't getting the required voltage for your CPU and you're choking your phone.. See if you can set it at 1200mhz and 800mhz on performance mode and see where that leads you.
Click to expand...
Click to collapse
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
supadupadoug said:
You guys are great everyday i just read and read and im amazed by the information and knowledge passed on. I learn something new every few pages. As for my oc/uv prob i've stuck to minimal uv with no oc and screen off profile and everything is working aok i did switch to the b version of infusion so so far so good. Ive read 28 pages today on the new infusion v2b2 for gb and that will be my next conquest. To all thanks a bunch and continue to the good work and especially helping out the new guys like me. And believe it or not im an electrical engineer lol. Again thanks and much appreciation
Click to expand...
Click to collapse
No prob. Buddy glad to have ya
Sent from my SAMSUNG-SGH-I997R using XDA Premium App
Entropy512 said:
SoD actually usually happens at lower frequencies - after all the phone tends to stay down there when the screen is off.
Typically SoD results from too much UV from 100-400. I never was able to go more than -50 mV undervolt, others hit -100.
netarchy's Gingerbread OC config is a bit different, instead of setting modifiers from stock you set absolute voltages. (No binaries have been released of his kernel until more testing is done - but the source is out there!)
Click to expand...
Click to collapse
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Dani897 said:
sounds a bit like unhelpfuls kernel from the eclair captivate days. he had absolute voltage values and other freatures. will the gpu clock be configurable? that would be awesome. under clocking the gpu and agressive uv and ucing the cpu could add hours to the battery life. with 2.3.3 you could set the phone to 800mhz and the gpu to 182 or 166mhz could probably give little negative performance in every day use with exceptional battery life.
to the op:
sod can be a problem especially if you overclock. it seems the cpu doesnt like rapid voltage changes. i can uv -200 acriss the board if i dont overclock. if i do im at -150. the 200mhz clock is almost never used but i find if i disable it im more prone to sod presumably because the voltage and frequency jump to 400mhz is too great. it can help if the 100mhz-200mhz clocks have less uv than 400. if you loose stability on 1200 at -100 then maybe set all clocks to -75 cept 100-200mhz which you may set to -50.
this isnt a rule though. you might be able to uv 400-1000 settings quite a bit more than the 1200 setting just if you have sleep of death you generally dont want agressive settings on the 100-200mhz.
Click to expand...
Click to collapse
Not a clue - I only know what netarchy has done, not what he plans on doing.
The architecture of voltage/CPU frequency control is significantly different in GB kernels than Froyo. In general it's cleaner, so a lot of the issues with rapid frequency changes might go away in GB. For example, there's some code in the base kernel that's supposed to facilitate rapid voltage changes (not exactly sure how... the only documentation people outside of Samsung have for the MAX8998 is kernel source code.)
Well guys I have some news. I continued use with set cpu no oc just uv on freq above 624 @ -75 and I kept my screen off profile set to 644 max powersave scaling, and my battery life has been outstanding i check emails frequently been texting all morning and playing wwf and im @ 70% after 4 hrs of use. I know I read % doesn't mean much compared to some volts ratio but I think this is worth mentioning. And for my purposes the goal has been achieved in extending battery life and still having exceptional performance.
Oh and I wanted to add that my phone recharges much faster especially with the screen off with these setting. Maybe nothing new to you but def a plus for a(us) neewb's reading.

should I use f4 phantom or f15c eagle?

To overclock. Which one iis better?
SENT FROM MY DINC2 RUNNING CM7 overclocked to 1.6ghz
Ok. I don't know if it was the kernel or what but f4 phantom bricked my touchpad. The screen was blue and I couldn't restart it. It scared me so bad. But it just now began working again and the first thing I did was remove f4.
SENT FROM MY DINC2 RUNNING CM7 overclocked to 1.6ghz
Haven't had issues with F4, actually runs both cores full time which is an advantage compared to Warthog. I've never gotten F15 to work correctly.
Running f15 at 1.8 no issues at all..
Matt V said:
Haven't had issues with F4, actually runs both cores full time which is an advantage compared to Warthog. I've never gotten F15 to work correctly.
Click to expand...
Click to collapse
isn't that going to eat up your battery?
Not really because it's on demand. At idle both cores run at 400MHz.
Matt V said:
Not really because it's on demand. At idle both cores run at 400MHz.
Click to expand...
Click to collapse
Then what does the Warthog kernel do?
Wearespacepeople said:
Then what does the Warthog kernel do?
Click to expand...
Click to collapse
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
JohnnyChuttz said:
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
Click to expand...
Click to collapse
Warthog activates core 2 when necessary I believe, I've seen it jump to 1.7ghz
JohnnyChuttz said:
Warthog idles core 1 at 292 or so and cuts off core 2 until needed. I originally used F15c Eagle to OC and recently switched to Wathog to try it out. Both Oc'd to 1.728Ghz. I have never gotten either of them to activate core 2, even with polling set to 1 sec.
Click to expand...
Click to collapse
polling frequency is not too important. just have to do something like watch a hd video. then go back and check. the number will be back down again. but what u have to do is to click on the graph, and u'll see it peaks to 1.7 when needed.
i've used f15c, and it froze a few times. been using Warthog for a day now, so far no freeze.
havent tried F4 yet. i'm happy with the performance and stability now, so i might not change it unless there's a big difference.
Use f15c ... it works awesome , if you dont see the second core do anything is because the second core is not being used! you can test it openning lets say 3 youtube videos at the same time then go to govnah and you will see second core working! after you install the kernel if second core says n/a just unnistall the kernel reboot and try phantom after you install restar again.. I guess using phantom running both cores at the same time will drecrease battery a little bit.
had problems getting f15 to oc above 1.5, would give me errors if I tried to up it. Switched to warthog and my TP has been 100%. I'm very happy with it. I have not tried F4.
bug splat said:
had problems getting f15 to oc above 1.5, would give me errors if I tried to up it. Switched to warthog and my TP has been 100%. I'm very happy with it. I have not tried F4.
Click to expand...
Click to collapse
I tried f4 but I believe since both cores run at full speed all the time battery will decrease faster not sure how much faster , I have tried movies, games, 4 youtube videos at the same time some of multitasking and with 1.7 is more than enough everything runs perfect with f15 .. I would say you are covered with warthog
Here's a test showing that F4 performs the best out of any of the kernels.
http://forums.precentral.net/hp-tou...k-benchmarking-kernel-fastest-comparison.html
bafare said:
I tried f4 but I believe since both cores run at full speed all the time battery will decrease faster not sure how much faster , I have tried movies, games, 4 youtube videos at the same time some of multitasking and with 1.7 is more than enough everything runs perfect with f15 .. I would say you are covered with warthog
Click to expand...
Click to collapse
The only way both cores are at full speed all the time is if you set the governor to performance. I believe it defaults to on demand so it should only only use higher frequencies when necessary.
I prefer F4 Phantom at the moment.
used F4 at 1.8 for few hours now and it works smooth. Difference between F15c and F4 is quite noticeable .
I have updated from uberkernel to f4 @ 1.72 , seems very stable.
Battery life on the f4 kernal is amazing even with performance mode on. I can get about a day and a half with consistant usage (I mainly use it as a pdf viewer for my textbooks, sprinkled in with heavy web usage here and there when I zone out). I can only imagine the battery life with eagle and warthog if I stuck with it longer... 6000mAh battery ftw.
Sent from my T-Mobile myTouch 3G Slide using XDA Premium App
I agree, the battery life, screen, and processor, are the strong features of this tablet. Even with webOS it's a nice, handy tablet.

[Q] Overclocking cm7 to 1600 Mhz

So overclocking cm7 to 1600 doesnt work and causes boot loops, i have been trying to get a kernel that would do it and i cant find one.
anyone know any kernels that work?
Only kernal for cm7 is the one that is with it no other kernals are compatible as for 1600 some phones run fine at 1600 others don't just depends on your CPU in your phone
Sent from my SGH-I997 using xda premium
^^^ what he said ^^^
my cappy was maginally stable @ 1300 within a very narrow voltage range. my infuse runs 100% @ 1664 with a ton of uv untill i turn on gps and everything starts to get warm. every cpu is different.
most infuses seem to be a higher test cpu than galaxy s phones though. you may be able to run at 1500 or better if you take a lot of time and figure out what the cpu likes and doesnt like. remember heat, uv and rapid voltage change can all cause instability so too much uv can cause problems as well as too little! to get maximum speed you may want keep the top few freq's at the same voltage (not the same uv but the same actual voltage) and have zero uv on the low freq's. it can be a pain to figure it all out but when you see the benchmarks you may think it was worth it.
ok well i kinda messed around with the overclocking built in and was messing with the type of governors and userspace seems to support over clocking on 1600.
really weird but my phone hasnt done the boot loop yet.
but thanks for your guy's help.
I set mine at 1600 last night via SetCPU. After 5 min it got hot and started boot looping. Its running good at 1200 now. I'm gonna bump it up little by little.
Good info, nice to know its "normal".
Honestly, the performance of CM7 outperforms all the other ROMS even running at 1.2GHz (IMO). I really don't see much of a performance increase by stepping up the clock speed, just a decrease in battery life, so it's not worth it to me.
ive talked to many people about this and most can only run at 1.4ghz even though 1.6ghz was stable in froyo. alot of people repeat "it depends on your specific chipset" but i dont buy that cop out. i think theres something wrong with the 1.6ghz setting in cm7.

[Q] - Overclocked kernels - What's the point ?

I see a lot of overclocked kernel editions, and I am wonder could someone explane me, except extensive battery draining, instabillity and overheating of device, what is and is there any crucial positive point of overclocked kernels ?
Overclocked kernels are simply kernels whose speed limit had been raised above the stock speed.
That increases perrormans dramatically as is visible by different benchmarks utilities.
You are correct to assume that higher clock would require some extra voltage and that the phone will get hotter. But it is not always noticeable and is mostly depentant on the configuration.
The cpu clock is not always at the highest possible. Different governors define what speed should the cpu be at any time. If there's a lot of work the cpuspeed would increase and if it idles a lot it would decrease.
I love 3 oc kernels, Sebastian's, bricked and faux. They all have different philosophies but all are excelent, do not overheat and save gather.compared to stock though they allow higher cpu freqs.
I suggest you create a nandroid backup and try some of.there kernels. Give it atleast two days.before you make up your mind about it, and try another if you wish, till you find the one that is right for you.
Sent from my HTC Sensation using xda premium
I agree. I never see the point of over clocking. I always limit my processor to 1.18 or even 1.13 and never have any problems with overheating or poor battery life!
I used overclock kernels for a long time on my gs2. Its nearly the same like with a desktop CPU. Every CPU had it's own work range, many CPUs a
are even able to work with higher frequency but lower voltage than standard. This causes in higher speed with lower power consumption!
all you need is a kernel which allows individual voltage settings for each speed which you can set with setcpu.
BUT my opinion is that even the gs2 with 1,2 GHz dual core was faster than any Android app had needed, so the gs3 at all!
ATM I've setted the max frequency in setcpu to 600 mhz and I can't see any lags or missing speed...
So I guess many people are more looking for benchmarking than real practical advantage..
but undervolting is a real great thing for power hungry smartphones!
Gesendet von meinem GT-I9300 mit Tapatalk 2
You all right guys. That is why I asked myself that question because there is hard to find modded kernels with default speeds and all new goodies, because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value, even in settings they were limited, and that impact widespread device causes instabillity ( and corrensponding unpleasent situations of forced battery pulling).
Last good kernel what I find for my CM7 ( I don't like ICS) is Bricked_XE-1.6.beta7 and with this release of CM7 it seems that kernel edition further development stops.It runs on 1526 Mhz and I allways wonder why shouldn't it run "out of the box" on default speed...
Does anyone have suggestion link, (because I couldn't find it )for any CM7 modded kernel with all new goodies, but running on default Sensation XE Mhz speed ?
i have been using overclocked Kernels for a while now and rarely have any problems, the phone is quick, very quick and the battery drain is really not that different and that is running it at 1.72 with both cores permanently on
tin2404 said:
[...] because I have noticed even I "limit" overclocked kernel in my Hypersensation CM7 Cyanogen Settings, it happens that some kernels from time to time speeds up to overclocked value
Click to expand...
Click to collapse
This really should not happen. The maximum frequency for a governor is set through /sys pseudo-fs and (assuming the governor is not buggy) strictly followed. Maybe you have some leftover scripts somewhere messing with /sys?
tin2404 said:
( and corrensponding unpleasent situations of forced battery pulling).
Click to expand...
Click to collapse
And this should -- like already pointed out -- only be the case under heavy load. Normally, a sensible governor will only set frequencies necessary to satisfy the current load.

Categories

Resources