Develop Bugs

phone heats up and restart with all custom kernels

has anyone else experienced this? i have this happen to me quite a few times using bullet/synergy kernal
basically what happens is that my phone will always heat up and crash then it restarts itself..even when it's idle
i've used faux clock to keep my phone from ocing but this still seems to happen..

Try Fauxs kernels.. always stable....check your OC setting and UV settings...flash it and use at it's out of the box setting
Sent from my SGS2

Vinsane said:
Try Fauxs kernels.. always stable....check your OC setting and UV settings...flash it and use at it's out of the box setting
Sent from my SGS2
Click to expand...
Click to collapse
oc settings is set to keep the clocks at stock
i tried undervolting it by 12mv and my phone was ok, then i went a bit lower and my phone crashed again, not quite sure if i should try another custom kernel, i feel like im on the brink of bricking my phone

Yeah..not all chips are created equal...so keep it to where it's stable and you should be good. Flash Fauxs.. leave all the settings as it came and see how it does for you
Sent from my SGS2

Vinsane said:
Yeah..not all chips are created equal...so keep it to where it's stable and you should be good. Flash Fauxs.. leave all the settings as it came and see how it does for you
Sent from my SGS2
Click to expand...
Click to collapse
i dont think its actually a chip issue
my settings were
1.512ghz max 384mhz min
and
at screen off
540max
384 min
my phone heated up and crashed when i turned the screen offf..so it seems more like a software bug rather than hardware imo..
i think you misunderstood me lul. so here's the entire story
i flashed synergy a couple weeks back and had this issue, so i thought o well and went back to eaglesblood(which is pretty much stock everything)
then i decided to try jugs+bullet, it seemed fined until i went to sleep and wokeup with a phone that has its battery drained and is hot to the touch
now the settings were set to not overclock, so it doesnt seem like my chip is causing the issue

If your chip heats up enough to cause it to crash and reboot...that's not a good sign man..especially if you've tried different kernels and don't have crazy settings.
One more flash won't hurt right?
Maybe try a new combo... different rom and kernel?
Sent from my SGS2

Vinsane said:
If your chip heats up enough to cause it to crash and reboot...that's not a good sign man..especially if you've tried different kernels and don't have crazy settings.
One more flash won't hurt right?
Maybe try a new combo... different rom and kernel?
Sent from my SGS2
Click to expand...
Click to collapse
im on faux right now
it does sound bad, but its been fine when im on eaglesblood(stock kernel)
so im a bit confused all around

thing is, im playing gta 3 right now and its barely heated up, so it confuses me why it would heat up and crash/restart when its friggen idle..

Like some are saying try faux's kernal. I used to have the same problem when ocing my sgs and g2x everyone's phones are different but so far faux kernal is very stable
Sent from my SGH-T989 using xda premium

BowLow said:
Like some are saying try faux's kernal. I used to have the same problem when ocing my sgs and g2x everyone's phones are different but so far faux kernal is very stable
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
read up lul, im using it and it's been good so far

ya the faux kernel is doing really really well
on synergy/bullet i used to get under 4500 antutu score..
now im getting 6458 and im not even overclocking..

I unerstand this isn't what was asked, but I've never had heat issues, using the stock roms cleaned-up by myself after root. The new 2.3.6 is solid as well.

heinrich said:
I unerstand this isn't what was asked, but I've never had heat issues, using the stock roms cleaned-up by myself after root. The new 2.3.6 is solid as well.
Click to expand...
Click to collapse
i wasnt talking about the stock kernel, i was talking about synergy and bullet

Cool. Glad it worked out for you man
Hint - find his. 06 version with gpu Turbo.... freaking awesome
Sent from my SGS2

Vinsane said:
Cool. Glad it worked out for you man
Hint - find his. 06 version with gpu Turbo.... freaking awesome
Sent from my SGS2
Click to expand...
Click to collapse
This things plenty fast without overclocking, I'm in no overcompensation contest to get my benchmark scores higher lull

Kernels don't seem to do anything.

Ever since i flashed francos kernel for the first time i failed to see any difference whatsoever in batterylife or performance. 4 versions of franco kernel later and still no change. Even bought his app and tried undervolting. I accidentaly uv'd by 100 in the 700 category and none of the side effects were happening so i tried undervolting all by 200 and even setting on boot. Nothing happened. I then flashed jame bond kernel and nothing happened. When i tried flashing glados kernel it just froze on boot. I experimented with all of them for at least a day and except glados which didn't work they all showed no difference than stock regarding battery life or performance. What could be the cause of this?
Sent from my Galaxy Nexus using Tapatalk

Kernels don't have the profound effect you might think on this phone. Not nearly as much as devices I have had in the past.

I'm aware of that, but still. No difference whatsoever? Even when i intentionally try and break it by undervolting by 200?
Sent from my Galaxy Nexus using Tapatalk

What did you undervolt by 200? Some speed steps can get away with that.

What ROM are you using?
Sent from my Galaxy Nexus using xda premium

adrynalyne said:
Kernels don't have the profound effect you might think on this phone. Not nearly as much as devices I have had in the past.
Click to expand...
Click to collapse
Adrynalyne! Its good to see you here!
Yeah, on the Fascinate, Kernels had much more of a profound effect. I can't say the same for this phone. But the OP said that he purposely tried to Bork his phone to see if it worked and it didn't even touch it. That's really strange. I can purposely try to Bork mine and do a pretty damn good job of it.
Sent from my Galaxy Nexus using xda premium

Some kernels had broken UV interfaces that wouldn't undervolt the kernel and would allow you to undervolt by absurd amounts. (though it wasn't actually doing anything)

joshnichols189 said:
Some kernels had broken UV interfaces that wouldn't undervolt the kernel and would allow you to undervolt by absurd amounts. (though it wasn't actually doing anything)
Click to expand...
Click to collapse
Well, are all the most popular kernels broken? Franco, glados, jame bond? I'm more inclined to think the problem is localized (either me or my phone).
And i'm running aokp 20, btw. Had 19 and milestone2 before those, which were all installed after full wipes (before anyone suggests that).
Sent from my Galaxy Nexus using Tapatalk

Your not the only one with this problem as I too have seen no change in battery performance on my gnex. I'm also using aokp 20 and Franco's (14.4). What I don't get however is that my buddy seems to see significant improvement in his phone while running the same rom/kernel combo

I've had some friends do some tests for me and run stock kernels for a while.
The differences in performance and battery life were menial between custom and stock.

What about all those people that claim seeing improved battery life? Not to mention those impresive screenshots of battery stats that show numbers i have yet to even come close to.
Sent from my Galaxy Nexus using Tapatalk

Many of those screenshots are sleep time.
Also, never underestimate the power of placebo.

adrynalyne said:
Many of those screenshots are sleep time.
Click to expand...
Click to collapse
naturally. also, data calls are a huge battery drainer, even with excellent reception, when actually using the phone. the same with wifi.
to give the op an example, this last night i forgot wifi on. connected to my home network. the phone slept well (something woke it up in the middle but for a very short period of time, probably gmail), and i only lost 3%. i normally loose 1% in 7hrs approx., so it wasnt so bad.
on the other hand, if screenOn is true, it will obviously drain faster..

adrynalyne said:
Many of those screenshots are sleep time.
Also, never underestimate the power of placebo.
Click to expand...
Click to collapse
+1 on that.
Btw adryn, what kernel/rom do you use in your gnex?
Sent from my Galaxy Nexus using xda premium

Tried a lot of combinations, but at the time of writing the original post i had been using aokp 20 with franco 14.4 for a while. I am currently trying aokp20 with trinity 384mhz gpu.
Also i lost about 2%/hour with franco in standby. I had mobile data connected and autosync only for google account + yahoo mail, all set to sync each hour.
Waiting on trinity now. Curious if i notice any difference besides the lack of franco's blueish tint.
Sent from my Galaxy Nexus using Tapatalk

adrynalyne said:
Many of those screenshots are sleep time.
Also, never underestimate the power of placebo.
Click to expand...
Click to collapse
This.
However, the GPU overclock is noticeable on games like Shadow and GTA.

yondercomesthetrain said:
+1 on that.
Btw adryn, what kernel/rom do you use in your gnex?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
My own or stock. I experiment a lot. Currently I am running a custom with a tweaked deadline scheduler, and a slightly different oc method for gpu and cpu than everyone is using to 1.35ghz. Stock voltages, tweaked ramdisk for filesystem mounts. Stock sleep profile of 350/700 on Interactive. Not using Setcpu to overclock at all. I set the power profile in fw-res to include the extra speed step.
So far so good, but its too early to tell. I went to bed and work up 9 hours off battery with 99% remaining. So its definitely deep sleeping fine I won't know for a couple days on whether it sucks battery dry or not.

ericc191 said:
This.
However, the GPU overclock is noticeable on games like Shadow and GTA.
Click to expand...
Click to collapse
I don't play a lot of games but 307mhz to 384, nets me 3fps in Nenamark2. Not exactly mind blowing.

adrynalyne said:
Many of those screenshots are sleep time.
Also, never underestimate the power of placebo.
Click to expand...
Click to collapse
exactly. I used to go crazy doing this and that, disabling this and that to try to get 20+ hours that people were getting on stock battery. Then I came to realize that the screenshots are probably mostly sleep time. Me being a very social person (text, IM, Facebook, and Tweet a lot) there is no way I was ever gonna get anywhere near 20 hours on stock. So I bought a couple of spare batteries, turned stuff back on, turn the screen back on brightly and enjoyed the phone and its great screen without worrying about battery life
Sent from my Galaxy Nexus using Tapatalk

Ill be as honest as I can. I just had two nexus and installed two different roms and and two different kernels....I believe they don't do anything as well..And I thinks its placebo effect when people are saying there battery's are better or the screen is smoother....I see not much of a difference even in stock...yes the benchmark may go up but that's means nothing really....
Sent from my Galaxy Nexus using XDA App

Galaxy Nexus Unusable

Here's my problem: no matter what app is used to control my CPU, no matter what ROM I use, or Kernel I run, my phone cycles over and over down to 350mhz. I've even changed the voltages and governor to no avail. At this point I want to throw this thing against the wall and go ballistic.
Does anybody else have this problem? Or know how to fix it.
~Jasecloud4
Sent from the Nexus of another Galaxy.

Does this problem occur when you are running stock?

Stock root yes. Never had the problem while unrooted.
Sent from the Nexus of another Galaxy.

So...what is the problem?
The phone spends most of its time at 350mhz on any kernel.

That's weird, even with full wipes in between your ROM flashes it still cycles down to 350? You've also selected run on boot in your kernel settings and verified that the init.d file was written? Do you keep restoring with Titanium Backup or something after all your ROM flashes or do you actually start fresh?

adrynalyne said:
So...what is the problem?
The phone spends most of its time at 350mhz on any kernel.
Click to expand...
Click to collapse
The problem? Have you used this phone at 350mhz? It's worse than a G1 on Eclair...I didn't buy the latest phone to run at 1/4 of the max. Not trying to troll, but the lag between key strokes as the processor cycles down and up over and over is ridiculous. It makes the phone a terror to use.
opensourcefan said:
That's weird, even with full wipes in between your ROM flashes it still cycles down to 350? You've also selected run on boot in your kernel settings and verified that the init.d file was written? Do you keep restoring with Titanium Backup or something after all your ROM flashes or do you actually start fresh?
Click to expand...
Click to collapse
Yes, I wipe repeatedly just to make sure. No Titanium for me. Yes, run on boot is good.
Sent from the Nexus of another Galaxy.

Your explanation was confusing. I thought you meant it was spending most of its time at 350mhz, not stuck with 350mhz as a cap.
Have you returned to stock? Because rooting alone won't do this.

adrynalyne said:
Your explanation was confusing. I thought you meant it was spending most of its time at 350mhz, not stuck with 350mhz as a cap.
Have you returned to stock? Because rooting alone won't do this.
Click to expand...
Click to collapse
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Sent from the Nexus of another Galaxy.

Have you run CPU Spy through a course of a day to see what is actually happening?

jasecloud4 said:
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Sent from the Nexus of another Galaxy.
Click to expand...
Click to collapse
As a test, use something like setcpu and cap yourself at 1.2ghz and see if it stays there. You might have a bad cpu.

I had this same problem using setcpu on my old htc sensation.
I can't remember exactly what I did to fix it. I think I just got rid of setcpu and stopped messing with the clock speeds.
Sent from my Galaxy Nexus using xda premium

adrynalyne said:
As a test, use something like setcpu and cap yourself at 1.2ghz and see if it stays there. You might have a bad cpu.
Click to expand...
Click to collapse
Blah. I hope it's not bad. Dealing with insurance blows. I've done that already but I'll try again.
Maybe I should just rewrite the kernel so that 1.2ghz and 1.35ghz are the only options.
Sent from the Nexus of another Galaxy.

jasecloud4 said:
Maybe I should just rewrite the kernel so that 1.2ghz and 1.35ghz are the only options.
Click to expand...
Click to collapse
what? Its so hard to understand you. I am still not 100% sure what is the problem or what you've done because they are rather conflicting.
Not even any close to his suggestions either. Do yourself a favour and follow his instructions.
Rewriting kernel?? Er what??

Try removing all CPU control apps and see if it becomes usable
Sent from my ADR6425LVW using XDA App

s2d4 said:
what? Its so hard to understand you. I am still not 100% sure what is the problem or what you've done because they are rather conflicting.
Not even any close to his suggestions either. Do yourself a favour and listen to him.
Click to expand...
Click to collapse
No joke rofl. Having a very hard time understanding whats actually going on here lol.

I think I just put it all together. He claims 350mhz to be "1/4" of the max. So he's trying to oc to 1.4ghz and his cpu, like most, can't handle it and the system clocks down to minimum on its own.
Could be wrong but his case sounds like exactly what happened to me when trying out 1.42ghz. Even on performance gov. It just isn't stable on all cpus. Voltage tweaking may or may not help.
Sent from my Galaxy Nexus using Tapatalk

jasecloud4 said:
I apologize I wasn't clearer. The phone will switch to a high frequency and then drop all the way down to 350mhz and stay there.
No matter how much I try and change it, the phone will switch frequencies for roughly twenty seconds and drop down to 350mhz, regardless of settings.
After 3 or 4 times of doing this, the phone will stick to 350mhz and not change at all, until I reboot the phone.
Click to expand...
Click to collapse
No, I it's what he said above. His phone isn't using all the available cpu frequencies, his cpu gets stuck at 350mhz and doesn't change.
Sent from my Galaxy Nexus using xda premium

opensourcefan said:
No, I it's what he said above. His phone isn't using all the available cpu frequencies, his cpu gets stuck at 350mhz and doesn't change.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Your exactly right.
Sent from the Nexus of another Galaxy.

I'm having this same issue, was anyone able to figure out what causes it?

Black Screen of Death: ROM or Kernel Issue?

I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?

Amphibliam said:
I just had my first Black Screen of Death requiring a battery pull. I don't know if it's a ROM or Kernel problem. I just flashed Liquid Smooth 1.5RC1 and the latest trinity. Not undervolted. I did a search, didn't find anything. Any ideas?
Click to expand...
Click to collapse
Does this rom come stock with trinity kernel? If it does not and you flash it.. then it is normal, you are supposed to let the kernel sit and reboot after the phone is settled. Im not entirely sure what it is but i have to do it everytime otherwise i get what we called it back in my epic fourms "the dead hooker syndrome" where the lights would come on but the phone would be unresponsive.

No I flashed Trinity separately and ran it after several reboots and s**t for like 3 hours then this happened. I ran trinity before and never had this issue. My guess is that it's Liquid. For now, I shall observe and see if it happens again.

The ROM doesnt control the CPU .. the kernel does.. my guess is its a bad download or something is keeping it from coming out of deep sleep..

What is your minimum speed of the CPU? Anything below stock can cause issues.
Sent from my Galaxy Nexus using XDA

I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.

Amphibliam said:
I'm running 307. I run 180 on IMO and Franco with zero issues, which is what I had used for a month.
Click to expand...
Click to collapse
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.

ÜBER™ said:
It could be the fact that your phone just doesnt like Trinity... although we all have the same chipset... they arent all built to withstand the same conditions. Some handle more than others.
Click to expand...
Click to collapse
What he said. Having your lowest frequency set at ~100, 300 regardless if it works on one particular kernel. Your phone might not like that kernel and cause it to not wake back up.
Best way to workaround it is just to simply boost your lowest frequency.... or just flash another kernel.

I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.

Amphibliam said:
I would except Franco (m4/nightlies), IMO overheats my phone, PBJT fails at performance and battery, Popcorn is good, but I haven't tried the latest.
Click to expand...
Click to collapse
I think kernels for sprint work for Verizon try samurai kernel in our forums. Its what I use or you could just flash faux kernel his is based on that.
Sent from my Galaxy Nexus using xda premium

Screen gets HOT

I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?

How long has it been since you installed these AOSP roms. In my experience, it takes one or two days for everything to settle down after installation, during which the phone might overheat and battery life takes a hit. My advice would be to give it some time, but if you're really worried, try fixing permissions or even going back to a touchwiz ROM.

jebise101 said:
I know for a fact the phone gets hot when playing some games like Asphalt 7 and that is understandable but it never used to get hot while in regular use such as browsing the web or text messaging on stock and i could have the screen on for an hour. Ever since i installed CM10 and now on AOKP by task650 I have noticed the bottom half of the phone gets very warm even when doing simple things. I have the brightness set to auto at all times and within 15 minutes or so it starts to get hot.
Does this happen to anyone else or its just me? Also maybe there is a tweak for the screen in the ROM?
Click to expand...
Click to collapse
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.

Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
RobbieL811 said:
I am having the same problem with CM10. I have tried multiple nightlies with the stock CM10 kernel and my phone just seems to run warmer. I can't figure it out. When I flash back to the stock ROM it doesn't do it unless like you said, I am playing Asphalt or some other games.
Click to expand...
Click to collapse
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.

The bottom of mine gets real hot after about 15 minutes of browsing on LTE. It did it right out of the box, and I'm on stock.
Stock ICS on my S3

I disabled LTE yet its still gets hot.

jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.

jebise101 said:
Nah not worried because i have extended warranty on my phone. Its just i like my electronics to function the way they should and when they don't i HAVE to fix them or i will loose my mind, plus its kinda annoying when hold it.
I know it needs a few charge cycles and installed CM earlier this week so its been at least 3 days, but still noticed the phone heating up. I installed AOKP today and will try cycling the battery a few times.
Pardon my ignorance but why would fixing permissions have anything to do with this? Also there is no negative effects to doing this? I don't see any as it wil just mark everything rwx-r--r-- or whatever the default is, but just want to confirm.
I was thinking it maybe the CM kernel, would you mind flashing Kooz kernel? If you have CM for a few days. I still testing AOKP so might be a while before i can flash.
Click to expand...
Click to collapse
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium

RobbieL811 said:
That's what I was thinking it might be and no, I don't mind flashing the other kernel. As a matter of fact, I was wanting to try that myself but I couldn't figure out wich download I needed off the link that you just posted. Wich one should I download and flash with CM10? He's got several flashable kernels posted under the "Downloads" section. I just need to know wich one I need to use with CM10.
Click to expand...
Click to collapse
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
IUH1991 said:
Fixing permissions tends to remedy certain glitches on my end. I don't nearly have enough knowledge to tell you why though. However, there are certain aspects of this phone that will lead to heat production no matter what you do: lte chip; powerful dual core CPU, etc. Furthermore, aosp ROMs are not stable nor are they fully optimized for the phone at this point, this will also lead to more resources being spent, which ultimately results in faster heat production. If it really bothers you, stick to what works and flash a stock ROM.
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:

jebise101 said:
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Yeah, to my understanding, chipsets are designed to withstand a heat threshold of about 60 degrees Celsius. It is extremely hard to get it to that temp at stock speeds, so I wouldn't worry too much about something going awry with your phone.
Sent from my SGH-I747 using xda premium

jebise101 said:
You need to flash one of the AOSP JB kernels since you are on CM10. I can't tell you which one because that depends on which nightly you have installed. I guess there was major code changes after the 14th.
Yeah but it never did that with stock and its not a deal breaker i love AOKP no way am i flashing back to touchwiz. You know the ROM has been so stable that I expected everything to work but your right its not stable yet and some things are probably not optimized and that is the cause for the phone to heat up more then usual or kernel. Guess it can't hurt to make a nandroid and then fix permissions and if it goes south i have a backup:victory:
Click to expand...
Click to collapse
Ok. Thanks. I'll figure it out.

Can a mod please delete this unintended post?

RobbieL811 said:
Ok. Thanks. I'll figure it out.
Click to expand...
Click to collapse
hehe keep me posted. I fixed permissions, we will see how it goes.

jebise101 said:
hehe keep me posted. I fixed permissions, we will see how it goes.
Click to expand...
Click to collapse
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?

RobbieL811 said:
I've clean flashed the new nightly and task's kernel. My phone still seems to be running warm! I'll run it for about 24 hours or so and see how it does. IDK what the hell it could be. Is there other people running CM10 that are having this same problem? And by the way...Do you know of a fix for the MMS? My pictures that were taken vertically show up in an MMS horizontally and visa versa. Is there no way to fix that?
Click to expand...
Click to collapse
It seemed a bit better today, but then i been out all day and its been wet and cold so might not have noticed. Its not Task's kernel but rather Kooz but they do work together. Can you also keep an eye on battery life? his kernel is suppose to have amazing battery life and CM/AOKP for me have very bad battery life. Also make sure to cycle the battery at least 3 time.
NOTE: Battery cycling mean charging it to 100% and letting it die to 0% and repeating, this will calibrate the battery and maybe will help.
Just a recommendation for you to give AOKP a try. I always used CM, but CM had some bugs when i tried so i thought might as well give AOKP a try and its actually been solid and has more features then CM. Best part is the build in LED configuration for apps/notifications.
These devs make it so hard to choose, both are very good ROMS.

Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App

RobbieL811 said:
Yeah. That's a problem I have too. I can't decide which one I want. The KT 747 kernel has seemed to take care of my heat problems. I was cycling the battery anyways. Where can I get the AOKP ROM? Is it posted under original development? The 747 kernel also gave me some much better benchmark scores!
Edit - I see in ktweaker where you can change some voltages but I have NO clue about any of that! Any advice? I think there is a thread on here somewhere about it. I'll have to find it & read it I guess.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium

thatsupnow said:
go into the ktweaker voltages then hit menu and you have an option to add or subtract 5-25 mv. Take away a bit and do a stress test if its good then try some more etc etc. You get the picture
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App

RobbieL811 said:
Yeah. But the lower I set my voltages, will that affect the speeds that my phone runs at? Idk how to word my question. I guess what I'm saying is, if I lower the voltage on my 1.5GHz setting will it make my benchmark lower?
Sent from my SAMSUNG-SGH-I747 using XDA Premium App
Click to expand...
Click to collapse
Pfft! You should know at this point in the game that benchmarks mean nothing, its all about real world performance. Basically I'd just start playing around its the only way to learn what works and what doesn't on your device! Cause afterall every device is different no 2 chips are the same, what works on one device might not work on another
Sent from my SGH-I747M using xda premium

Yeah. I know. I guess I didn't necessarily mean my benchmark. I guess I meant speed.
Sent from my SAMSUNG-SGH-I747 using XDA Premium App