[KERNEL] [GPL] [GN] franco.Kernel r398

ratson said:

my phone could run 1.5 with #17 but in antutu it produced way lower scores (~4500) than on 1.35 (~6500). how does this thermal throttling actually work? if cpu reaches a given temperature it is throttled back to what? and what is this temperature?

my question is if it is any worth to run on 1.5 if it cannot stand it for long. in everyday use both 1.35 and 1.5 seem to be smooth but 'faster' is something always worth to experiment for

Click to expand...

Click to collapse

I only run 1.35 and I have been for quite a while now but after 20-40 seconds of heavy use (benchmarking for instance) it starts throttling until temperature drops under some threshold, and it'll keep dropping the speed all the way down to min if temp doesn't recover quickly, then when it's below it'll push itself back up to max and then throttle down again. Rinse and repeat. What the threshold is I do not know, nor do I know if it's the same temp sensor as we can use using a monitor app or StabilityTest. The reason I say that is because the temp shown in StabilityTest (and other apps) is (in my eyes) too low for throttling to happen and it's not consistent which temp it throttles at. Sometimes I can see 40 degrees C without throttling and sometimes I can't hit 33C without throttling. It feels like it's some other temp sensor that determines when to throttle.

// Stefan

---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------

marc.tulley said:

That's not very helpful Franco lol! Not using 1.5 is avoiding the problem.

Click to expand...

Click to collapse

It's not really though.

The phone is specced to run at 1.2GHz and anything above is gravy.

The CPU is already overclocked from factory.

I know, many of you are thinking "what is this guy smoking and can I have some?!" but it's true.

The CPU is specced to run at 1.5GHz yes, but that's with DCC enabled. Tech sheet says you have to use DCC above 1.0GHz. Our phones are run without DCC due to a hardware bug in the CPU. (I think it was the CPU).

The bug manifests itself in several ways :

Some CPUs don't run with DCC at all.
Some CPUs crash when switching between DCC and non-DCC.

And the same sheet says that you cannot use DCC below a certain frequency for the same reason.

What's this DCC thing I'm talking about:

There is a clock generator in the phone. I'm not totally sure but I think it's specced at 2.4GHz. Without DCC the frequency is halved (2.4 => 1.2GHz). With DCC the frequency is run natively.

The spec sheet says that at speeds up to 1.0GHz you run with DCC off (2.0GHz => 1.0GHz) and then turn it on and slow the speed down, say for example 1.2GHz for 1.2GHz operation and 1.5GHz for 1.5GHz operation. This keeps us within spec of the clock generator.

This is what our phones (some of the phones anyway) cannot do. Either it crashes enabling DCC or it crashes flipping DCC on/off.

// Stefan

I was using morfics kernel at 1.5ghz with only a minor bump up in voltage. With franco17.2 I'm still unstable at 1.5ghz even at a much higher voltage (I don't wanna go past 1500mv)

Sent from my Galaxy Nexus using xda premium

ChongoDroid said:

I was using morfics kernel at 1.5ghz with only a minor bump up in voltage. With franco17.2 I'm still unstable at 1.5ghz even at a much higher voltage (I don't wanna go past 1500mv)

Sent from my Galaxy Nexus using xda premium

Click to expand...

Click to collapse

Your phone obviously cant handle 1.5...
Im running v17.2 slightly undervolted, and have had no issues at all.. Im set at gazelle 350-1500

I pushed 17.2 right after wiping and restoring my phone (thought it was bricked for a little bit due to a bug with the power button not working lol, but I figured it out). All seems smooth now, and 1.5 does work. However, there are occasional moments of lag and my AnPooPoo scores are pretty low, hovering around the low-high 4000's range.

Stefan said:

It's not really though.

The phone is specced to run at 1.2GHz and anything above is gravy.

The CPU is already overclocked from factory.

I know, many of you are thinking "what is this guy smoking and can I have some?!" but it's true.

The CPU is specced to run at 1.5GHz yes, but that's with DCC enabled. Tech sheet says you have to use DCC above 1.0GHz. Our phones are run without DCC due to a hardware bug in the CPU. (I think it was the CPU).

The bug manifests itself in several ways :

Some CPUs don't run with DCC at all.
Some CPUs crash when switching between DCC and non-DCC.

And the same sheet says that you cannot use DCC below a certain frequency for the same reason.

What's this DCC thing I'm talking about:

There is a clock generator in the phone. I'm not totally sure but I think it's specced at 2.4GHz. Without DCC the frequency is halved (2.4 => 1.2GHz). With DCC the frequency is run natively.

The spec sheet says that at speeds up to 1.0GHz you run with DCC off (2.0GHz => 1.0GHz) and then turn it on and slow the speed down, say for example 1.2GHz for 1.2GHz operation and 1.5GHz for 1.5GHz operation. This keeps us within spec of the clock generator.

This is what our phones (some of the phones anyway) cannot do. Either it crashes enabling DCC or it crashes flipping DCC on/off.

// Stefan

Click to expand...

Click to collapse

You dont have to be smoking anything to realise the stock speed is 1.2Ghz...

And I agree, above this is gravy but if I can go from Tesco Value Beef Gravy Garanules Gravy to Proper Beek fatty Juices Gravy then I'm happier still!

If you read my entire post you may understand that I just want to achieve the highest clock comfortabley possible. With or without DCC, I honestly dont mind as long as its stable. I understand the DCC definition but its irrelevant if some guys are fully happy and stable with or without it active.

So whether its with a few more kernel tweaks, some user voltage tweaks or a slight clock reduction I'd appreciate it as the OC junkie that I am.

What is throttling I see its a on going issue

Sent from my Galaxy Nexus using xda premium

Antob125 said:

What exactly is SQlite? What exactly is this device IO that it's speeding up? I'm not sure of the terminology. I usually have francoturtle with hotplug on to give me the best battery life. Will this improve it also? What about turn logger off? What does that do? I checked it because it said it could save battery.

Sent from my Galaxy Nexus using Tapatalk

Click to expand...

Click to collapse

anyone figure out the answer to this? I just enabled it along with disabling logs.... hope it doesn't mess anything up!

on another note... 17.2 has been working well for me. No random reboots after an hour of random usage (17 would have crashed within 5min).



---------- Post added at 08:24 AM ---------- Previous post was at 07:58 AM ----------

Franco answered on google plus:

Francisco Franco - It's just to defrag the Sqlite files within Android.
me - so it can't, or shouldn't, hurt anything then right?
Francisco Franco - Yes, it won't do harm at all.

just wanted to pass the message along

whiteintegsg316 said:

What is throttling I see its a on going issue

Sent from my Galaxy Nexus using xda premium

Click to expand...

Click to collapse

Example:

You tell your phone to run 1.35GHz minimum and 1.35GHz maximum.

That way your phone shouldn't ever run at anything but 1.35GHz.

But you notice that that CPU clock goes below 1.35GHz at times. That is throttling.

Some/many phones run too hot under load, even sometimes at stock 1.2GHz speed.

They then lower the speed until the temps go down to a more reasonable temperature. When it lowers the phone increases the speed up back to whatever it's told to run at.

This is an abnormal condition, ie it does it to save itself from burning up.

Lowering the speed because the load is lower is a normal condition and not what we discuss here.

// Stefan

I am sure the temp which is reported comes from the battery, cpus are usually fine till 70-80C.

stesmi said:

I only run 1.35 and I have been for quite a while now but after 20-40 seconds of heavy use (benchmarking for instance) it starts throttling until temperature drops under some threshold, and it'll keep dropping the speed all the way down to min if temp doesn't recover quickly, then when it's below it'll push itself back up to max and then throttle down again. Rinse and repeat. What the threshold is I do not know, nor do I know if it's the same temp sensor as we can use using a monitor app or StabilityTest. The reason I say that is because the temp shown in StabilityTest (and other apps) is (in my eyes) too low for throttling to happen and it's not consistent which temp it throttles at. Sometimes I can see 40 degrees C without throttling and sometimes I can't hit 33C without throttling. It feels like it's some other temp sensor that determines when to throttle.

// Stefan

---------- Post added at 12:27 PM ---------- Previous post was at 12:16 PM ----------



It's not really though.

The phone is specced to run at 1.2GHz and anything above is gravy.

The CPU is already overclocked from factory.

I know, many of you are thinking "what is this guy smoking and can I have some?!" but it's true.

The CPU is specced to run at 1.5GHz yes, but that's with DCC enabled. Tech sheet says you have to use DCC above 1.0GHz. Our phones are run without DCC due to a hardware bug in the CPU. (I think it was the CPU).

The bug manifests itself in several ways :

Some CPUs don't run with DCC at all.
Some CPUs crash when switching between DCC and non-DCC.

And the same sheet says that you cannot use DCC below a certain frequency for the same reason.

What's this DCC thing I'm talking about:

There is a clock generator in the phone. I'm not totally sure but I think it's specced at 2.4GHz. Without DCC the frequency is halved (2.4 => 1.2GHz). With DCC the frequency is run natively.

The spec sheet says that at speeds up to 1.0GHz you run with DCC off (2.0GHz => 1.0GHz) and then turn it on and slow the speed down, say for example 1.2GHz for 1.2GHz operation and 1.5GHz for 1.5GHz operation. This keeps us within spec of the clock generator.

This is what our phones (some of the phones anyway) cannot do. Either it crashes enabling DCC or it crashes flipping DCC on/off.

// Stefan

Click to expand...

Click to collapse

Which is better turtle or gazelle????

Sent from my Galaxy Nexus using Tapatalk

hnx6310 said:

Which is better turtle or gazelle????

Click to expand...

Click to collapse

Depends. They do different things. I'd love for somebody to fill me in on the specifics, but turtle is more battery conservative, where as gazelle still aims for performance with battery improvements.

Sent from my Galaxy Nexus using XDA App

ratson said:

I am sure the temp which is reported comes from the battery, cpus are usually fine till 70-80C.

Click to expand...

Click to collapse

That makes perfect sense.

// Stefan

The Best Kernel

FFS ... why do all these complaints come from people that want to over-clock or under-volt?

Franco's kernel at stock IS THE BEST .. my phone runs so smooth with no ****ing around with OC/UV ... WHY do you people think they can do better than the recommendations from a true expert? --- then come whining here when it doesn't work?

BTW ... my phone is **** at 1.5 too .... but do I actually care? I still have the best phone experience ever -- even on Turtle.

My Phone was working fine with 1.5Ghz using #17, but it's unstable using #17.2. I'll go back to #17 so I can use 200/1500 which was perfect and noticeably faster the 400/1350. Haven't had any stability issues with #17.

I'm still on #17 and overnight, this is the first time I've been able to get 1% drain per hour. I'm on Gazelle 400/1200 and haven't changed the UV settings. My personal recap of 17 is that this is the only way I can run over 1.35ghz without it slowing down and I can get good battery life. Win.

So I've been using #17 without issue since around 4PM yesterday. Clocks are 700/1500, francoGazelle @ stock voltage. Absolutely no isssue, in fact, my phone has never been snappier. Battery life doesn't appear to have suffered, it's about on par with what it's been for the past few revisions.

I'm not sure what you did, franco -- but keep it up! I'll be avoiding any future releases with DCC re-enabled until you have a forked branch or toggle.

* Edit: I've attached #17 to this post, as a few people have asked me for it via PM.

.....:thumbdown::banghead:
Sent from my Galaxy Nexus using Tapatalk

magn2o said:

So I've been using #17 without issue since around 4PM yesterday. Clocks are 700/1500, francoGazelle @ stock voltage. Absolutely no isssue, in fact, my phone has never been snappier. Battery life doesn't appear to have suffered, it's about on par with what it's been for the past few revisions.

I'm not sure what you did, franco -- but keep it up! I'll be avoiding any future releases with DCC re-enabled until you have a forked branch or toggle.

* Edit: I've attached #17 to this post, as a few people have asked me for it via PM.

Click to expand...

Click to collapse

what do u mean by 700/1500???

Mine is 350 mhz 1500??



Sent from my Galaxy Nexus using xda premium

hnx6310 said:

.....:thumbdown::banghead:
Sent from my Galaxy Nexus using Tapatalk

Click to expand...

Click to collapse

If you have a fever, can you go out and play a full hour of sport?? Same goes with our phones, cpu temperature goes up, cpu speeds get dropped, regardless of our setting, so that we dont fry our devices.

If people want to avoid temperature throttling, run your benchmaks with the phone in the freezer... lol