Develop Bugs

[Q] Desire Z crashes after overclocking

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)

Data Disconnects after sleep?

I have an issue with any custom ROM's I've tried, when the phone sleeps my cell radio turns off and I cant receive phone calls, sms's and the like.. The service comes back after a minute of having the screen on, but its a real hassle. I dont have this issue with either of the stock roms, both 4.0.1 and 4.0.2 but anything custom causes me issues.. I wipe data, cache and dalvik and take care not to install any apps and the issue still arises.. I noticed there are a few other people having similar issues, but unlike them I do not have to reboot to get my cell radio working and its not just data, I have also tried the gamut of radio's but I am hesitant to flash radios constantly since my understanding is flashing them has a greater risk to brick your phone should something happen. Does anyone know anything I could try? I dont understand how custom roms all do this but a stock one wont..

set minimum CPU frequency to 700 mhz.
also try other radios (UGLA4 works very well)... flashing a radio won't brick your phone as long as its for your phone.. which in this case, just dont flash I515 radios (verizon)
what rom? kernel?

yannisthegreek has a thread about this; not uncommon by the sounds of it.
Purely conjecture on my part, but I think it's a power issue, i.e. your phone isn't supplying the radio with enough power to kick start it from sleep. Basing this on the fact that a particular kernel (Fugo IIRC?) or upping your min freq to 700 seems to fix the issue. I've yet to experience this however.

I'm going to try setting it to 700mhz right now, I've flashed CM9, Modaco, Codename Android, Revolution, used the Kernel that was provided with those ROMS and Franco's and Trinity, I have also tried every radio as well with the same results.. it does make sense the way mudferret explained it and also explains why it will start up after my phones out of sleep mode and running faster, the weird thing is that this just happened one day, my phone was fine running a custom rom and Franco's kernel and then one day I notice that I had calls going right to voice mail..

So glad I found this thread. I've been dealing with the same issue. People tell me when they try to call they get a fast busy signal. If I wake my phone for about a minute everything works again. I am going to try Fugo IIRC? kernel and see what that does.

Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..

flindil said:
Looks like setting my kernel to 700mhz did the trick.. using Franco Kernel and Modaco custom rom, this was driving me nuts.. I'm a happy camper now, thanks for the help guys..
Click to expand...
Click to collapse
Glad to see it up and running. I never had this problem but I always had my minimum frequency set to 700 MHz because I think I heard franco say something about it helps battery blah blah blah... it was a while back but I don't remember the full details

Yeah, I read that he said the difference on battery use was negligible.. that could have been why custom ROMS and kernels were working for me previously.
Sent from my Galaxy Nexus using xda premium

I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...

bk201doesntexist said:
I don't believe that setting min freq to 700mhz solves anything that relates to ril.
If you were talking about voltages, that would be another story...
Click to expand...
Click to collapse
What's the voltage differential between the 350 and 700 slots, if any?
Edit: I ask because I can't see my voltages on my current kernel

Have same problem post 4.0.4 update
I started seeing this too after a manual 4.0.4 update to my GSM Nexus. The phone is still stock (and was prior to the flash) with ClockWorkMod the only thing added. Still troubleshooting.
----------------------------------------------------
UPDATE: Noticed that this does not happen while phone is being charged. I've tried playing around with a CPU speed program, but I haven't yet figured out if the settings are taking properly.

Random reboot. Help appreciated!

Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz

kyokeun1234 said:
Ok I have gsm Gnex with AOKP jelly bean build 1 with Franco kernel overclocked to 1.4 GHz and I am experiencing a random reboot problem starting today around 1 am.
I do have cpu undervolted, but it was undervolted for some time now, but just to make sure, I increased the voltage just in case. No luck.
Next thing I though that might have been a problem is the fact that I dirty flashes the AOKP build 1 from the nightly of AOKP, but I flashed it for a time now and never had that problem until today.
Another thing I changed is that I changed the boot animation from AOKP one to cyanogenmod 10 one. That, I flashed yesterday.
One thing I do like to mention is that I think there might be something to do with SetCPU profiles, because I set the profiles so it underclocks when phone screen is off or if the phone cpu or battery heats up, and one reboot was when I was unlocking the screen and another one was when I was watching youtube, and the third one was when I was playing a game, which heats up my phone. The thing is though, I have set those profiles since day 1 and never have encountered any reboots until today
Can anyone help me? Is it something that I should care about, or something that is temporary? Any recommended actions? I hate factory wiping, so that is the last thing I wanna do. Thanks in advance!
Swyped on my Galaxy Nexus running AOKP with Franco Kernel, overclocked to 1.4GHz
Click to expand...
Click to collapse
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.

Petrovski80 said:
Tough one. Myself I'd start off by disabling all OC/undervolt settings & disable SetCPU profiles. If that doesn't resolve the issue, temporarily flash back stock kernel.
Click to expand...
Click to collapse
For some reason, when I cleared the cache and dalvik, It doesn't seem to reboot anymore. But if it ever happens again, I'll do what you told me
Thanks!

Hi, this happened again today, but I noticed that it isn't a full reboot. (no Google splash screen)
Any ideas?
Sent from my ASUS Transformer Pad TF300T using xda app-developers app

[Q] Phone getting hot after few minutes of use

Been noticing this since last week. Every time I use my phone for like 1 or 2 minutes, the phone starts getting hot. Usually, it gets hot after an hour of use (Facebook, Messaging, Browser, Twitter, Play Store). Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
This hasn't happened to me before. Not sure if this is normal, but I just want to make sure.

My recent heat and battery drain was coming from an app. I didn't check the CPU.
I checked the battery area of the settings and found a locale add-on that was draining more juice than my screen.
sent from a secret underground bunker

It will happen if your signal is real bad or 3G is down in your area.

I don't think it's my signal. I get 2 or 3 bars almost all of the time at home with the FC09 modem.
Besides opening and/or using an app, it seems that the CPU clock will go max speed if I do something, such as scrolling. Battery is also draining quickly before this was happening to me.
Sent from my SPH-D700 using Tapatalk 2

InsaneHien said:
Went to Performance settings in Settings, then Processor, and notice the Current CPU frequency is always at 1000 MHz, then goes down to 200 or 100 MHz when idle for a few seconds. Switched between conservative and ondemand governor, no OC. Was on PA 2.54 when this happened, but I'm on CM10 Stable now, and it's still getting hot after using it for a few minutes.
Click to expand...
Click to collapse
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP

AndyYan said:
I think that's a Jellybean-specific CPU behavior (to keep system flowing like "silk", JB put CPU at max the instant you have your finger on screen... At least that's what I heard). Try ICS/GB ROMs and see if problem persists.
Sent from HTC Incredible S @ AOKP
Click to expand...
Click to collapse
Yeah, you're right. I even looked it up. It's part of Jelly Bean.
I'm going back to CM9 or The People's ROM.

You could try a different kernel, or lower voltage. Sorry not sure what phone this topic is for lol but that's some options. It takes a lot to get my phone hot, and I'm on jelly bean
Sent from my Galaxy Nexus using Tapatalk 2

I don't have this problem on nitest kernel with the ns4g modem
Sent from my SPH-D700 using Tapatalk 2

You likely have an issue with your settings.
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.

Ruedii said:
If it's not an app, you probably have an issue with your performance settings.
Try turning off some of the eye-candy features in the settings. This will likely include the Cyanogenmod specific setting area as well.
That should at least help.
Click to expand...
Click to collapse
It didn't help unfortunately.
I flashed CM9 earlier and the issue still exists. I'm now back on CM10 (11/22 nightly).
It's okay if this can't be resolved. I am probably gonna go back to a GB ROM.
EDIT: Issue still persists in GB. I'm guessing it could be a hardware issue? I have no idea. Back to JB. I'm still willing to try anything to resolve this. Thanks to those who posted some solutions.
Sent from my SPH-D700 using Tapatalk 2

cpu speed

since i cant post this in the dev for cm10 i have to post this here. i installed it last night on my phone and everything has been running pretty good. i understand its still a wip so im not complaining. what has come to my attention is the fact that my phone now likes to run at 1026 no matter how low i set it at. if its sitting there itll change to 384. when i was on stock rom rooted and unlocked, it would never change speed on powersave. now if i go into antutu or just performance under settings minimum will always change to 1026. i havent had a chance to really test if its affecting my battery life but i can let someone know. im bringing it up so maybe the devs can have their way with it. if theres any way i can help, just let me know.

0328 update
with the latest update the speed issue is still there and the camera has been improved although i havent tried video yet. but on 0327 it has like a staircase set up on the upper lefthand side of the screen. did a wipe and fresh 0328 so ill see how that goes. keep up the great work and as always let me know if there is anything i can do to help.
update:recorded video still has issue but nexus7 camera apps work perfectly to get to camera here. flash or the camera worked once and hasnt worked since. still a great rom.

It looks like you're not using the latest cm10 builds, you need to hit the "next" thing on the top right of the download page.
I recommend taking a spin with the houcha kernel. It's pretty much fixed the cpu stuff, and intellidemand governor is amazing; Turns off 3 cores when nothing is taxing and idles at correct minimums.
They are always up to date with the cm10 kernel commits as well.
I get amazing battery life.
Sent from my LG-LS970 using xda app-developers app

0429 update
yeah. its running pretty good. the video recording is fixed so that helps me out at work. with all the phones and tablets i have, i havent installed another kernal so thats the only thing im a little sketchy on doing. but since you recommend it i think i have to give it a look. if theres anything i should know about it, just let me know.
I was on the latest update but I just fat fingered my posts and wasn't double checking it. Just had to install a keyboard that better suites me.
update-flash on the camera work only when i use touch to focus. does that kernal help with that?

clean install of 5/5
Did a clean install last night with standard 4.2.2 gapps. Camera icon has has appeared without the need to install a 3rd party app to access it. Battery life is about the same as before with installing a different kernel. As my daily driver I would recommend it all the way. Follow the forums specific to the ROM and you can't go wrong. I'll keep updating about the progress until I can post on there.

powersave for cm10.1
If you want to get powersave to work correctly; 1.set both speeds to the same number 2.must be below 1026.
If you set them both to 1026, they will stay at that speed. If you set them to two different numbers the minimum and maximum will default to 1026 and1350, respectively, when the system feels it needs the power above 384 and will stay there. Hopefully this will help someone out.

The reason the cpu speed gets raised to 1026 is due to mpdecision. It boosts the cpu speed on touch to increase the interactivity and decrease the lag. mpdecision is a qcom blob and since we are trying to stay as close to mako as possible these is nothing I can do about that blob.

Then I guess my question is why on stock I can run at 384 min with max at 1512 on powersave and it'll actually run at 384 but this cant?

fine for me
I have not really had this problem at all weird

harrybear25 said:
I have not really had this problem at all weird
Click to expand...
Click to collapse
So what min and max speeds is your phone set at? What speed does it end up at after using it for 5 mins on the net?

5/14
my powersave settings with the max at 1512 and min at 384 seemed to stick longer than normal with this rom. im going to backup everything, revert back to zvb and then do a clean install of the latest and see how that fairs.

Did a full restore of my phone back to zvb. Did all the GPS stuff I needed to, rooted and unlocked. Proceeded to do a full wipe and install of 5/27 ROM. Speed issue still there but as noted before I found a small workaround and randomly today I got a message that maps had stopped working.
I did play around with the ROM before install gapps and found some interesting things. None really stuck out except Bluetooth not working at all.
After installing gapps, everything seems to work perfectly. Downloading 5/28 right now and dont expect much to change. Some updates hold my speed settings and some dont. Not really an issue.

6/1 build
powersave function was working correctly with the max at 1512 and the min at 384 right after initial update. using antutu the temp and battery level would be displayed incorrectly. after the first reboot though, everything went back to "normal." but on the brightside if you set the max to 918 and the min at 384 on powersave, it appears to now stay that way. no more having to set them both at the same speed. i will continue to play with the speed settings and see if anything else comes up.