I'm not sure if this is normal behavior or not but ill have my max and min values set and when I leave the app and come back to, the value sliders will still be set but it will display the min as 384.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't recall it doing this before, unless I just never noticed. But I did a restore and also reflashed the kernal and it has not solved it!
I also tried Cpu Tuner and it did the same thing! What would be causing this?
"Edit - I forgot to add I'm on juggernaut 4.1 with bullet kernel"
Tap-A-Talkin it ... Galaxy S ii
Try un-installing set cpu. Boot into recovery and wiping data cache and dalvik. Then fix permissions. Reboot and re-install set cpu.
Thanks for the reply!
I just tried the method stated above and it Is still doing the same thing! I'm stumped! I really hope its not a hardware failure!
When adjusting clock speed with setcpu does this change the frequency for both processors? I'm wondering if the second processor is causing this issue.
While looking at the info tab in setcpu it lists processor 0, and processor 1 every once in awhile processor 1 dissappears from the screen. I'm assuming that's normal behavior though since both cpus aren't being used at all times and I guess its going into standby.
Try faux clock instead of setcpu.
Alright I wiped cache and dalvik once again fixed permissions amd than installed faux clock and still the same thing.
I'm really starting to think my SGS2 has a bad cpu.
I set the values to this, exited the app, reloaded the app and minimum was back down to 384
Sent from my SGH-T989 using Tapatalk
I remember I had an issue something like this. I had to do a wipe data/factory reset in recovery to fix it. You could back up your apps and try that. I know its a pain tho.
I still have not figured out what's going on, I have tried everything I can think of. I've even odin back to stock, updated latest firmware from kies, reflashed juggs... nothing has changed this behavior.
Even using fauxclock, if I set both min and max frequencies to the same setting when I exit the app and re open the app, the max frequency is where I set it to. but the min frequency goes back to 384. Anyone elses do this?
This is my first time owning a dual core phone and I'm beginning to think its normal! Might be panicked for no reason!
Tap-a-Talkin it.... Galaxy S !!
Is there a reason you want your minimum frequency so high? 384 is normal.
Sent from my SGH-T989 using xda premium
No reason, I just found it strange and was thinking there was a problem with the hardware, but I actually did a few test on it tonight and it's working, So I can rest easy!
Tap-a-Talkin it.... Galaxy S !!
Related
I apologize if this has been answered before. And yes, I can assure you I've read the instructions on how to go about installing SnapTurbo and I know all the warnings. Nothing is wrong with my Evo, however I'm curious as to whether or not Turbo is actually running.
What happened was I first installed CM 6.1, played around, wiped both caches, then installed Snap 7.6 (CFS). Then I activated SnapTurbo. On reboot, the phone wouldn't load past the white Evo 4G screen. So I just reflashed the Snap 7.6 kernel. Everything works fine now and the SnapTurbo app says it is activated. However, I'm not sure whether or not I can trust it since I'm not sure how Turbo works its magic. I ran a Quadrant benchmark and around 2040, so I'm guessing it is. Just wanted to make sure.
Bump. Anyone?
2040 doesn't sound like Turbo's been activated.
Do a full wipe of you data+cache, flash a sense ROM, then flash CM6.1-RC1, followed by snap, then do the failsafe Turbo method.
Also, give it plenty of time on the whitescreen, and if you're worried, plugin and look at adb logcat. If you see the same messages repeating or logcat sits there saying "waiting for device" for ten minutes, then yeah, it's looping.
Finally, keep in mind that in 6.1, all of the current versions of Snap are going to have issues due to the differences in kernel versions. For example, Snap 7.6 will not have working bluetooth.
I had the same problem I just pulled the battery and put it back in and it loaded just fine, every time I tried booting from recovery it would get stuck, this probably isn't an exact science but I hope it works
Sent from my PC36100 using XDA App
Thanks guys. Ill give it a try when I get home. Late for my sociology class! I dont wanna use up then battery wiping and flashing right now.
Sent from my PC36100 using XDA App
Alright so instead of going back to my Stock rooted backup, I cleared all caches and restored my original CM 6.1 backup (without Snap kernel). Then I reflashed Snap kernel and activated SnapTurbo and I THINK it's working now. The scores in Quadrant vary; the highest I got now was 2227, but it's gone as low as 1985. I think it's because SetCPU is set to Interactive (998 max, 245 min):
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Put SetCPU on Performance and overclock as high as you can, then run Quadrant three times. You should see 2300+, sometimes all the way up to 2800+.
When I do that, Quadrant first force closes on startup, then it freezes my phone when it gets to the first 3D benchmark (the one with the staircase) and my phone reboots. I'm pretty sure that I did an uninstall and reinstall of it already but I'll do it again.
EDIT: Alright so I ran it with the 3rd-to-highest overclock 3 times. First I had 2187, then 2383, and now 2476. I think it's running. Thanks guys!
PS: What governor would you recommend as the best combination of speed and low power consumption without any noticeable lag? I know this kernel has HAVs, so I don't have profiles enabled. But should I stick with Interactive or go with Conservative? I don't game on this thing, plus I'm using LauncherPro so I don't notice much lag already.
I don't fully understand what wakelock is, I know it has to do with CPU at minimal usage while screen is off, but that's it.
Alongside that I know some kernels can reach 128MHz, but I've found they only scale to 245Mhz by default.
Could we discuss wakelock issues and scaling, maybe get a better understanding for all?
I'm still looking for feedback, my phone has has 100% awake time lately.
Using spare parts, the numbers just don't compute...partial locks are far less than the system uptime.
You can read a fair amount about wakelocks here: http://geekfor.me/news/facebook-1-3-wakelock/
I'm not saying that facebook is your issue but that's an article I wrote a few months ago when the new facebook update wasn't releasing a wakelock. That has been fixed since then though.
This chart should answer a few of your questions:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
There are also several screen shots at the bottom that show the commands you can run from ddms (dalvik debug monitor... it's part of the android sdk) to see any current wake locks that are in place on the phone.
FYI your phone will not sleep when it's plugged in, so you can't compare awake and sleep time when you have it plugged in. It also will not sleep after very first boot until you wake it up and then put it to sleep again. If you are having wake time issues then you should start uninstalling applications until it starts sleeping. Or the faster way would be to just do a data wipe and start over and slowly re-install your applications, paying attention to when it stops sleeping.
I know this is brief but I just wanted to give you a place to start looking.
As for 128mhz vs 245mhz... 245 is the lowest the phone can go by default. I honestly don't keep up with the kernel stuff a whole lot but if there is a kernel that is capable of going down to 128mhz then you would need to use an app such as setcpu to allow it to scale that low. In my experience in the past I have had issues on my phone when going below 245mhz. The phone would automatically drop to 19mhz and basically come to a hault. However like I said I haven't done anything dealing with custom kernels in months so I'm sure I'm behind on new changes.
Extremely helpful, thank you so much.
As much as I have many more questions, you've set me in the right direction.
So far I've found after wimax is shut off I get a connection error sourcing from wimax repeatedly.
Still looking into this.
I tried searching but didn't find a question similar to mine.
I flashed slickmod 3.4, 3.6. When I go to SetCpu (or Fauxclock or etc.) it shows both the min and max frequencies at 1.782ghz then 2 seconds later the min frequency jumps down to 384mhz. Every time I open SetCpu (or any similar app) it does this. My question is:
1. Is the min frequency really at 1.782ghz and when I go to SetCpu it goes down for the first time as to trick me?
Also in other roms I experienced this (not min freq being 1.782 though) but the min freq would be on a certain amount and 2 seconds later it would jump to down to a different certain amount right after I open SetCpu or Faux or any other app like this.
Here's the scenario right after I open Fauxclock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
And here's 2 seconds later
h1a8 said:
I tried searching but didn't find a question similar to mine.
I flashed slickmod 3.4, 3.6. When I go to SetCpu (or Fauxclock or etc.) it shows both the min and max frequencies at 1.782ghz then 2 seconds later the min frequency jumps down to 384mhz. Every time I open SetCpu (or any similar app) it does this. My question is:
1. Is the min frequency really at 1.782ghz and when I go to SetCpu it goes down for the first time as to trick me?
Also in other roms I experienced this (not min freq being 1.782 though) but the min freq would be on a certain amount and 2 seconds later it would jump to down to a different certain amount right after I open SetCpu or Faux or any other app like this.
Here's the scenario right after I open Fauxclock.
And here's 2 seconds later
Click to expand...
Click to collapse
Yeah that's a bug with pretty much all CPU apps on our phone, happens with system tuner as well. Its just a graphical bug, your min frequency is still what it should be at at all times. To confirm that you can use CPU spy which will show your phone using the correct min frequency
Thanks,
Also how do I fix a governer to stick?
Sometimes I change it to another governer, but when I come back to fauxclock
it changes back to the default governer.
Set on boot, or use a script
h1a8 said:
Thanks,
Also how do I fix a governer to stick?
Sometimes I change it to another governer, but when I come back to fauxclock
it changes back to the default governer.
Click to expand...
Click to collapse
I've never had issues with a governor not sticking. I don't use faux clock though, maybe you should try system tuner. If you're not rebooting the governor change should stick but if you need it to change on boot (like if you reboot your phone a lot) you'll have to have the app set it on boot or modify your post boot script like the poster above me said.
Thats right, ever since AOKP and CM9 have updated to 4.0.4 i lost the ability to overclock, well Tegrak OC is now fully functional (at least on AOKP b37)
Any brave souls willing to test on cm9a5?.. if it doesnt work it wont brick the phone will it? Lol
Sent from my SPH-D710 using XDA
It works fine. I've used tegrak for ever. As soon as it updated and started working I tried it on my ROM, CM9, and AOKP. Shouldn't have many issues. Just don't under volt too far
Anyone post the apk? Keep getting a error when download
edit:got it to download and works great!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my awesomely EPIC Phone
what settings you all usin?
Ya works for those who have tested this? Need a good starting point
Sent from my SPH-D710 using XDA
dpaschall said:
Ya works for those who have tested this? Need a good starting point
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
Generally people undervolt -50 or -75 mV from the stock values. Some go -100 mV but that could get you bootlooped. Make sure that your phone is stable after undervolting before setting it on startup. As for OC, I'd say max should be like 1500 Mhz
Sent from my SPH-4710 using XDA
Tegrak has a great feature. No matter what your settings are when you reboot you have to apply the settings after the phone boots. So if you make a change that locks up the phone you can reboot and undo it by hitting cancel at the tegrak screen. When I undervolt I normally go -50mv on each step including GPU. This seems to work the best for me on ICS ROMs. On GB I could go to -75mv and even -100mv on some steps. But -50mv seems to give you a little more battery life and still good performance. Just my input.
OK I'm working on the cttmod for mm and I'm having trouble getting different temperature readings from the different apps I'm using to test so I have a two part question
1 - Does anyone know of an app that accurately measure the temp ?
2- How can I tell what method or what directory mm stock and stock kernels get there temperature information and an temperature app that will allow me to point it in the same direction.
Right now I've got the mod working but the 5°c+ difference in temperature is a big difference when allowing the CPU's temp to be higher before it throttles and for how long it stays there.
Hey.
You can see all thermal zones here:
/sys/class/thermal/
If I'm not wrong, thermal_zone0 is for the cpu package(not only core0), so you can use this to see the temp.
I'm using cooltool from Google play and custom label with this for path:
/sys/class/thermal/thermal_zone0/temp
You can change refresh rate and some other things in the app. You can also watch on what mhz cpu work, so you can see when it throttle
Hope this will help you
P.s.- This is the most accurate temp reading, because you read it directly from the kernel.
Sent from my LG-D855 using Tapatalk
siankatabg said:
Hey.
You can see all thermal zones here:
/sys/class/thermal/
If I'm not wrong, thermal_zone0 is for the cpu package(not only core0), so you can use this to see the temp.
I'm using cooltool from Google play and custom label with this for path:
/sys/class/thermal/thermal_zone0/temp
You can change refresh rate and some other things in the app. You can also watch on what mhz cpu work, so you can see when it throttle
Hope this will help you
P.s.- This is the most accurate temp reading, because you read it directly from the kernel.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Thanks I'll give it a try and see
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can see it runing in statusbar and this is the custom label configurations I'm using for cpu temp.
Sent from my LG-D855 using Tapatalk
siankatabg said:
You can see it runing in statusbar and this is the custom label configurations I'm using for cpu temp.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
Thanks and that just confirmed it. Kernel auditor is the one that's off out the five that I tried only kernel auditor was a consistent 5+ ° c lower than the other four which all stayed without 1 to 2° of each other. That's the reason my mod wasn't working the way I thought it was . Now time to start over
Again thanks I just needed some additional confirmation and that did it