Hi,
i have an Italian version of i9000 with jf5 firmware.
I have upgraded whit samsung kies my firmware.
now i have
pda xwjm3
phone xxjm2
csc itvjm1
now sometime my phone goes off
anyone have the same problem?
i read that this is a bug......
You read its a bug? Of course it's a bug.
It's either a bug with the firmware or with an application. I had the same problem when using SetCPU.
Sent from my GT-I9000
i have setcpu me too.
so the problem is this app?
just uninstall it?
I experienced it (no response completely unless I reinsert the battery) when with lag fix and GPS on, regardless eclair or froyo ROM.
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
I have a feeling that the problem was due to GPS or due to the 0513 pit, but I'm not sure - so far it's been okay so I bother not to break it for tests.
SetCPU shuts my device down... out of nothing...
i uninstalled setcpu and never happened again
mystaka said:
then I reflashed and turned GPS off for most of the time on my 2.1 lag-fixed ROM, the problem seemed not to trouble me any more. I have also underclocked my CPU with "Overclock Widget" to 800/400 MHz on screen, and 400/400 MHz offscreen.
Click to expand...
Click to collapse
Slightly off-topic but... That'd actually be an overclock if I'm reading those numbers correctly. The default frequency is 1000/100mhz with a conservative setting, meaning it'll try to be as low as possible more or less. What you've done is set min-frequency to 400mhz, which in my book is an overclock from the stock 100mhz.
Back to semi on topic... SetCPU is known to cause problems on Galaxy S, and likely other devices aswell. Most problems has been more specifically caused by using ondemand setting when setting up profiles - for some reason the phone doesn't handle this setting well when it wakes from sleep.
I'm pretty sure I managed to get it working more or less flawlessly with an screen off profile at 400/100 with Conservative setting, though I reflashed shortly after those settings so never got to test it properly. Regardless, they might work if you want to mess about with it.
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
gettons said:
I had a similar problem with JM5 and SetCPU.
Removed and it didn't happen again.
Click to expand...
Click to collapse
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
insty said:
The way to have SetCPU working is to do the following:
Scaling: conservating
Freq Step: 100
Click to expand...
Click to collapse
Great!This work
Thank you
I don't use setcpu but I have this problem in my two SGS. Using m5 and m6..
Related
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
You might be right. Not every CPU is created equal and since the phone is only supposed to run 800Mhz you can't exactly complain that it "only" does ~1.1ghz
On the other hand a little more juice can make a reluctant CPU run a little faster. I'm not sure how the voltage tables work out for different Kernels but you might want to look in to that. The higher the voltage, the better the chance your OC will work, typically.
That's true, every cpu is unique. But for now, since the kernels are still going through development, I would assume it's perfectly fine that overclocked speeds are still quite unstable
Thanks for the replys i am not really complaining i just wanna make sure that i havnt messed up somewhere i thought the crashing might be happening because i messed something up or maybe it happend to others and its a common problem or there is a fix for it .
Also i would appreciate it if someone could put me in the right direction in regard to changing the voltage.
Sent from my HTC Vision using XDA App
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
The current overclock kernel that Flippy has over in Development (1.4) causes my phone to freeze when I'm trying to play Angry Birds. CyanogenMod's kernel runs it at 1.4Ghz, and I'm using an older, more stable version of Flippy's kernel.
bahmanxda said:
just wipe my original stock sense rom and flashed it with virtuous-vision_froyo_rom-v0.8.0 and applied all the patches but still the same problem
my phone freezes instantly as soon as i change it to just over 1100 mhz
its so strange its very very stable at 1094 mhz hasnt crashed even once.
any ideas?
Click to expand...
Click to collapse
It could be simply that your CPU isn't capable of over-clocking that high. Its hard to say as the kernels are still being developed but the ability to overclock a processor can vary greatly from unit to unit...
I have CM 6.1 and the last few days I have been running my phone at 1017 to compare the performance difference against the 1497 and thus far, I haven't really seen a drastic difference... That may change as the Gingerbread based ROMS start to trickle out but for now 1ghz seems like plenty of power.
You could always try a different kernel and see if it yields different results.
bahmanxda said:
Hi
I have permroot and s/off my phone using gfree method and i flashed a kernal
that i downloaded (Cyanogen Kernel v1.3) the kernal allows overclocking upto over 1400 mhz ,at 1094 mhz everything is fine and my phone is stable but as soon as i set the frequency over that using setCPU my phone freezes ,i dont know what i am doing wrong this is the first time i tried overclocking a phone ,i hope i am wrong but i am thinking since every cpu is unique maybe thats the max mine can handle ??? i apprentice any tips, advise , help ,suggestions
Thanks.
i have also tried EZDZ_Godspeed_update03 but using this kernal my phone doesnt even boot up it crashes immediately when i turn my phone on.
Click to expand...
Click to collapse
you should check/edit the overclock scripts..
I found wrong configuration script (650 Mhz using Androidiani OR)
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Only thing anyone can probably suggest is turning up your min clock speed. What are your profiles set to?
My screen off is 245/368 just to give it that bit extra to guarantee no wakeup issues, not that I had any to begin with, better safe than wanting to throw her up the wall (I get annoyed easy).
bahmanxda said:
So i just swiched from virtouos ROM (sense) to CM6.1 and i am having a problem.
when i first flashed virtouos, sometimes my phone screen wouldnt turn on with
first attempt but after setting profiles on setCPU it was fixed and didnt happen anymore now with CM6.1 i am having a slightly different problem the screen doesnt turn on when i am receiving a call (it rings though) and i have to press the power button couple of times to get the screen on. i have already set some profiles on setCPU ,i am just wondering if there is any fix for it ?
Thanks
Click to expand...
Click to collapse
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Possible explination posted here by rmk40:
http://forum.xda-developers.com/showthread.php?t=884237
dhkr123 said:
Doesn't sound normal... did you make ANY customizations at all? Or did you install CM straight up and just use it like that? Any adjustment to "performance settings" or CPU clocking? What SPL and radio do you have installed?
Click to expand...
Click to collapse
Thanks
no i didnt make any customization its just CM6.1 although my max clock speed is at 1497 mhz
setCPU
Screen off max 368
min 245
and profiles for temp and battery as well
the wierd thing is it doesnt happen at all when im just waking the phone up it only happens when its ringing i am thinking its my CPU issue ,i dont think it handles overclocking well ,i couldnt go over 1.1ghz (it would freeze instantly) with virouos that was the main reason i switched im gonna play with with cpu profiles for a while and see if i can get it fixed.
btw i have never flashed any radio so im guessing its the stock one
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
bahmanxda said:
wow this is very intreasting its actually fine without any setCPU profiles
i had something totally different in my mind.
Click to expand...
Click to collapse
With my experience I've noticed the phone runs better, and lasts longer on a single charge WITHOUT setCPU profiles. Just my opinion
bahmanxda said:
although my max clock speed is at 1497 mhz
setCPU
Click to expand...
Click to collapse
And there you have it. Overclocking can do weird things.
dhkr123 said:
And there you have it. Overclocking can do weird things.
Click to expand...
Click to collapse
Fair enough
Sent from my HTC Vision using XDA App
I have a rooted myTouch 3g slide and am using the CyanogenMod 6.1.1 ROM. I have been trying to overclock the CPU using setCPU but for some reason every time I change the max speed past 600 mhz the phone just reboots. Am I doing something wrong or do I just have a phone that can't be overclocked beyond that speed?
Thanks for any insight into this problem!
I don't know how far past 600 MHz you're trying to go, but I have been successful at overclocking to 806 MHz. Anything over that, and I start getting lockups, reboots, etc.
Hope that helps a bit!
Lol i'm jealous now.. At this point I'd like to even just be able to overclock it to 768 or 787 mhz. Anything over 600 mhz really would be a step in the right direction.
It seems as though as soon as i change the max cpu speed in setCPU the phone hangs up for a second and then immediately reboots. I have to quickly change it when i get back into setCPU after the reboot otherwise it reboots again.
Do I not have the necessary tools or applications on the phone to do this? I thought CM 6.1.1 had the overclock kernel and everything...
arjuna_ said:
Lol i'm jealous now.. At this point I'd like to even just be able to overclock it to 768 or 787 mhz. Anything over 600 mhz really would be a step in the right direction.
It seems as though as soon as i change the max cpu speed in setCPU the phone hangs up for a second and then immediately reboots. I have to quickly change it when i get back into setCPU after the reboot otherwise it reboots again.
Do I not have the necessary tools or applications on the phone to do this? I thought CM 6.1.1 had the overclock kernel and everything...
Click to expand...
Click to collapse
it does, but the problem is that your phone's cpu is not able to handle it. Some people can do 900+(unfortunately im not that lucky) some cant touch 800 even. Even though we all have the same phone they all arent exactly the same. Like on a computer some can OC higher than others even if setup is the same...
So what your saying is that my phone just can't be overclocked beyond 600 mhz? Is there a way to manually adjust it to like 650 mhz or something else that I set? Or is that dangerous and stupid to do?
Sorry i'm a total noob at this...
arjuna_ said:
So what your saying is that my phone just can't be overclocked beyond 600 mhz? Is there a way to manually adjust it to like 650 mhz or something else that I set? Or is that dangerous and stupid to do?
Sorry i'm a total noob at this...
Click to expand...
Click to collapse
That can't be done because the cpu won't actually clock to anything in between certain multiples, I forget what the multiple is but it can't do in between unfortunately. I have stably clocked to 844 mhz. Every once and awhile, normally less than once a month it will freeze but not enough for me to go down to 825 or 806.
But to me, this doesn't sound like the processor not being able to handle it. It sounds like something software related, since at least in my experience, if the CPU can't handle it, the phone simply freezes and you have to pull the battery. It doesn't reboot, it just freezes, stops processing entirely.
If you don't have the android sdk, download it and install it (just google it), and then open a command prompt when your phone is plugged in and type adb logcat and press enter.
You also need the HTC sync drivers which can be obtained from HTC's site.
Then, while running the logcat, change your frequency up one step, and after your phone is back at the boot splash screen, press CTRL + C in the command prompt window and paste the entire logcat into a reply here in this thread
Code:
with code brackets like this
. You might even do a paste2: http://paste2.org/new-paste to make it easier to read
It sure sounds like it's a system crash, not a processor locking up from too high of speeds.
Maybe its the version of SetCPU that your using. Try re-installing it first, and if that doesn't help, Google up SetCPU 2.02 or something and see if that works.
I think the latest version of setcpu is 2.10
Sent from my T-Mobile myTouch 3G Slide using Tapatalk
What rom are you using?
Maybe the kernel is not Over Clocked.
I've made it to overclock up to 844 pretty well on 3rdSense Rom...
Tzatlacael said:
What rom are you using?
Maybe the kernel is not Over Clocked.
I've made it to overclock up to 844 pretty well on 3rdSense Rom...
Click to expand...
Click to collapse
arjuna_ said:
I have a rooted myTouch 3g slide and am using the CyanogenMod 6.1.1 ROM. I have been trying to overclock the CPU using setCPU but for some reason every time I change the max speed past 600 mhz the phone just reboots. Am I doing something wrong or do I just have a phone that can't be overclocked beyond that speed?
Thanks for any insight into this problem!
Click to expand...
Click to collapse
CM 6.1.1 Should have the kernel included.
When i first started over clocking I recall being told not to use the perflock disabler on SetCpu or it would mess things up. Perhaps you are using it and should not be or vice versa? That was using DumFuq's (sp) kernels of course, I do not know if Cyanogen still uses the same overclock kernel.
Balem said:
When i first started over clocking I recall being told not to use the perflock disabler on SetCpu or it would mess things up. Perhaps you are using it and should not be or vice versa? That was using DumFuq's (sp) kernels of course, I do not know if Cyanogen still uses the same overclock kernel.
Click to expand...
Click to collapse
You only needed to use perflock on stock kernel that was used on stock rom. Dumfuq's kernel lets you yse setcpu w/o that setting being needed. but once i got soff it would save settings even after rebooting.
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
I did not start using SetCPU on my phone yet because it's not rooted, but first I would check if SetCPU doesn't require some kernel support? and if that's implemented in the custom ROM you're using? (if it's needed, I'm not sure).
Or maybe SetCPU needs an update to properly support our phones?
That Temp > 44.5 Profile, wouldn't that interfere with gaming? I have never used Temp profiles before (is it really needed?), only the other ones, like battery and screen-off and charging.
my one x has unlocked bootloader, recovery and root. I was running into some serious intermittent lagging issues, the phone in any app would just stall for 5+ seconds. after hours restoring after failure , it came down to the problem that using ANY cpu controll app, messed my phone up... BADLY! it seems at the moment (im assuming) apps like setcpu and cpu master are not quad core ready...
thanks for the responses guys.
I guess ill just wait until one of the devs can confirm this as working...
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
skywalker1970 said:
The reason is simple. We don't have rooted kernels yet. Until then stay away from messing with CPU speeds or under volting. Etc.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
+1
DO NOT mess with your CPU speeds yet. Undervoltage is causing reboots!
the software is not up to the hardware capability, i dont think the cpu control apps can handle quad core yet. and there is a lot of apps (esp. games) that lag a lot, and amazingly the cores are too lazy to work... im hoping for a better kernel that will address this issues.
If you want to at least see what's going on with the cores, I can confirm that Tablet CPU Usage Monitor works on HTC One X
It shows 2 icons in notification bar, each icon showing usage of 2 cores. Not sure how accurate it is, but so far had no problems with it and it seems to be reporting correctly. Developer is working on single icon with all 4cores in it, to save space.
I had the same problem, but if you delete your profiles you won't get reboots.
I'm just running default profile Max: 1500, Min: 760 Ondemand gov. and it has been a straight line for 6 hours when I was sleeping and no reboots.
jakejay said:
Hi All,
After being a long time iPhone user i recently purchased htc one x, as a result my android skills are almost non-existent; so please bear with me.
I managed to flash clockworkmod recovery and rooted with SuperSU with no issues.
Purchased setCPU after reading the reviews and enabled. However the phone would reboot randomly a few times a day. Ususally when the screen was off.
After disabling setCPU there was no rebooting issue.
Has anyone got this app to work on the OneX, and if so which settings did you use?
Also has it been confirmed to work with all 4 cores?
FYI I had the following profiles setup.
Screen Off
Freq:640Mhz-51Mhz
Gov: conservative
Temp > 44.5
Freq:880Mhz-51Mhz
Gov: conservative
Battery < 30%
Freq:1000Mhz-51Mhz
Gov: powersave
Charging Any
Freq:1500Mhz-51Mhz
Gov: ondemand
Please note these profiles are based on no evidence, just on what I estimated to be about right...
Cheers
Click to expand...
Click to collapse
I was having that problem too... In my opinion, I don't think that the phone can handle the Conservative governor setting. I set my governor to Interactive (On Demand works too)
Right now, I have my profile set to 1000mhz max and 475mhz min, with screen off profiles set to 475mhz max and min. I have not had any problems with the phone rebooting at all since setting those freqs. (And I don't want to quite go any lower yet). And I have it Set on Boot.
im now using rooted HTC One X(HOX) and installed RD-MIUI ROM quite sometimes. my kernel is still in stock. Im using setcpu and NO random reboot happen like what you have said. Yet, i am still confuse whether setcpu is good for my phone. based on my review, in the leading rom developer thread they not mention setcpu for their choice. they play alot with kernels to govern their hox cpu-s. could anyone do some comment.
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Did you try wiping everything on the phone and starting fresh. Go in the Android Revolution thread and run the superwipe script and wipe again then reinstall everything see if that helps.
I didn't look at the logcats, too tedious.
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
clarkey1269 said:
basically just recently i have noticed my Nexus not waking up.
will simply go sleep perfectly fine but sometimes will not wake and sort of reboots in away.
tried all sort of ROMS, kernels, radios with no effect. even switched back to ICS but still get the same results.
Galaxy nexus
Android 4.1.1
XXLF1
Rom: Latest CM10 Nightly
Kenel: Stock (even tried Francos)
Logcats:
http://pastebin.com/tpeuQYqx
Any ideas guys?
Click to expand...
Click to collapse
Does this happen on stock. This logcat is using franco's kernel, are you UV'ing? OC'ing? Smartreflex? I don't know if actually Francisco is using official stock voltages today, or is already uv'ing a little from source.
And I just finished going through your log, there's nothing useful there; you should be getting it while it happens, or better yet would be /proc/last_kmsg immediately after the reboot; Grab it like this, for example:
Code:
adb shell cat /proc/last_kmsg > last_kmsg_on_my_pc
Also, what you're experiencing is called Sleep of Death.
chopper the dog said:
See here. http://forum.xda-developers.com/showthread.php?p=29839968
good day.
Click to expand...
Click to collapse
also happens on ICS not just JB
full wipe is taken out with every flash or nightly update without fail.
even did a fresh start with locking and relocking the bootloader with no effect i still get the annoying wake
Are you using any app to control your min CPU voltage? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU voltage is too low...
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
bk201doesntexist said:
Why? It's more likely that it's the voltages that are causing it, they're probably too low for his chip. What you're saying is that "it doesnt have enough power", so you're kind of contradicting yourself. And CPU ramps you know? So, if it meets a intensive task (if you call waking up the screen and bringing up UI an intensive task), it will ramp UP to the next step, until it reaches the defined workload percentage for max cpu speed defined in the governor.
Click to expand...
Click to collapse
Sorry I meant to say voltage
cayte2 said:
Are you using any app to control your min CPU frequency? the problem might be that your phone doesn't have enough power to come back from sleep or just takes really long if the CPU frequency is too low...
Click to expand...
Click to collapse
cayte2 said:
Sorry I meant to say voltage
Click to expand...
Click to collapse
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
bk201doesntexist said:
It seems you didn't understand where you're contradicting yourself.
min cpu frequency is not equal to min cpu frequency voltage. If you set min cpu freq to 700mhz step, but lower the voltage to a value where that same cpu step it's not stable, it will still have issues.
Another thing I recalled: OP, are you limiting your MAX cpu freq, WHEN screen is off? Like with cpu profilers and such apps?
Click to expand...
Click to collapse
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
clarkey1269 said:
when using Francos kernel i have being using his app.
haven't messed with any frequency's and is set to what ever the kernel is standard. with no effect.
no fancy profiles set in his app either.
really starting to bug me now
Click to expand...
Click to collapse
Does it happen when using google's factory image?
Do you have Eugene cpu sleeper installed? I was having that happen to mine and I just uninstalled, wiped caches, fixed permissions and I haven't had a problem since.
Sent from my Galaxy Nexus using xda premium
bk201doesntexist said:
Does it happen when using google's factory image?
Click to expand...
Click to collapse
fresh instal of googles stock image and il report back