yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Al Asmi:
Kernel is amazing, but can't purchase the app as paid applications are blocked in the middle east :mad::mad::mad:. Tried Market Enabler, no go as the new Market check also the IP address. can see now the paid applications in the market but can't buy them:(:(

Any help regarding the app would be highly appreciated.
[Samsung Galaxy Nexus] lemmy_0:
Didn't you see he was at 1.5GHz?
[Samsung Galaxy Nexus] mgear356:
Dear Franco, able to provide some tips to cool down the phone?

Used modaco's 4.0.4 romwith default kernel seems much more cooler when I play games or surf net.

On your kernel I ran Franco turtle 700/1000 also seems much more warm.

I wonder is it because of android os fixes in 4.0.4? I am using aokp build 23 btw
[Samsung Galaxy Nexus] marc.tulley:
Could someone kindly post a 17.1?

17 was very nearly stable for me but 17.2,with FCC, stutters all over the place!

Really appreciate a go at 17.1 if any 1 can help?
[Samsung Galaxy Nexus] drawde40599:
ur phone can't handle its normal: ()
[Samsung Galaxy Nexus] d3rutat:
Release 17.2 working great here with AOKP #23. Using 700-1200mhz francoturtle stock UV.
[Samsung Galaxy Nexus] lemmy_0:
Is it just me?

When I download from OP and install, shows 16.2 in System info.
[Samsung Galaxy Nexus] mrfenyx:
noob question here: if your phone is in a bootloop, how do you revert to old kernel?
[Samsung Galaxy Nexus] stesmi:
Go into CWM and flash the old kernel or go back to your nandroid backup.

EDIT: To go into CWM, power off your phone, remove the battery, let it sit there for a few seconds, then put battery back in, hold down volume + and - while holding power button. Then go to recovery from there. And no, the battery thing may not be necessary but hey, some people say it does *Shrug*

// Stefan
[Samsung Galaxy Nexus] danielvc:
for noobs: restore your nandroid
[Samsung Galaxy Nexus] qwer23:
How do you get such high RAM and CPU scores? I only get 761 in ram for example, not even mentioning the cpu scores (i know not every phone can handle 1,5ghz). I know every phone is different but this difference seems too big. Are you using any other tweaks? Which setup are you running? I'm on AOKP build 23 with franco.kernel nightly 17.

Sorry, don't wanna freak out about crappy benchmark results, I just think my scores are really bad and I wanna know if I got a faulty unit perhaps.

Besides scores my phone is running quite smooth :)
[Samsung Galaxy Nexus] franciscofranco:
It seems like your device was being throttled for thermal control.
[Samsung Galaxy Nexus] Mrc527:
Man,

i'm the ony that can't see the 200MHz step in setcpu?:D

And at 1,5GHz my phone goes really slooooooooow! I think there is something wrong with this:p

BTW, 1,35GHz is high enough!
[Samsung Galaxy Nexus] superbobup:
i think for 17.2, the trick to make most phones run smoothly at 1.5 ghz (i think it was called DCC) was removed and so some phones may run slowly at this speed
[Samsung Galaxy Nexus] franciscofranco:
This is simply explained. For #17 and #17.1 I used the same trick that morfic did and force enabled DCC for every frequency which makes 1,5ghz usable, but as we could see it ****s up for around 50% of the users even in different frequencies that not 1,5ghz. For #17.2 I disabled DCC again and made the kernel stable for everyone, but the number of devices that will work with 1,5ghz decreases a LOT. Luckily I can run 1,5ghz with DCC or no DCC so I couldn't reproduce any of the bugs reported. What I'm gonna do later today when I'm home is to start mass producing two different kernel branches, one with DCC and another with DCC off because there are devices that can run with 1,5ghz and DCC just fine and I want everyone to have the best experience ever. It will give me a little bit of extra work, but its going to be worth it.
[Samsung Galaxy Nexus] Persianity:
thank you franco for putting forth such great effort into benefiting everyone here, just wanted to say good stuff :)
[Samsung Galaxy Nexus] yeeson:
1500 Very not smooth！Can only choose 1350
[Samsung Galaxy Nexus] mjchung:
Really? With Apex 1.0.2, I'm getting 2700 with 1.00 on turtle. Unfortunately, it doesn't look like my handset can handle 1.5. Extremely stuttery and about 1600 in Quadrant.
[Samsung Galaxy Nexus] mgear356:
Hmm used stock kernel and seems like it'd not as warm as Franco 17.2 or 16.2.. any ideas?
[Samsung Galaxy Nexus] MS.:
Could anyone re-upload 17.1 please? On 17.2 my phone gets really laggy @1.5GHz.
[Samsung Galaxy Nexus] qwer23:
Please tell me that's just a temporary effect and not something that damaged my hardware :(

On the other hand, my phone was not even slightly warm when doing the benchmark. So maybe it's a permanent defect after all?? :/
[Samsung Galaxy Nexus] pattsy:
Soo i updated to 17.2 (turtle 350-1000) and i got a strange thing going on. When wakeing up the phone (with the power button) the screen flashes green for a short moment. Have'nt had this before (16.2)... Any1 got this 2? Other than that it seems to run ok.
[Samsung Galaxy Nexus] ratson:
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 :)
[Samsung Galaxy Nexus] marc.tulley:
I got that score with aokp 23 and Franco 17

Antutu can be funny not sure if its CPU current loading or thermal throttling but if you bench it FIRST thing after getting up in the morning it yields best results.

Static wallpaper and performance governor are said to help but I don't bother

Also still hoping someone can upload 17.1 for me please 17 very occasionally reboots and 17.2 stutters
[Samsung Galaxy Nexus] franciscofranco:
Stutters with 1,5ghz?
[Samsung Galaxy Nexus] ratson:
definitetly, that is what I have too.
[Samsung Galaxy Nexus] CaspaTheGhost:
Think I'm gonna have to give the infamous 13.1 a try! I assume it's "Franco.kernel-nightly13-1-200112.zip" from World Of Nexus
[Samsung Galaxy Nexus] lemmy_0:
can somebody help explain this?

flashing 17.1 and 17.2 does not seem to work.

shows 16.2 in about system.

my download was broken?
[Samsung Galaxy Nexus] marc.tulley:
Yeah its more obvious with sounds on. For example when you press a softbutton that makes a click sound the button will get the click down appearance for about 3 seconds during which the click sound will keep repeating 'click click click...' then the phone will come back to life and perform what ever action you clicked on. But this delay happens with most actions all over the place
[Samsung Galaxy Nexus] franciscofranco:
I know, dont use 1,5 then ;)
[Samsung Galaxy Nexus] definator:
Is this Version Not titled 17.2 in settings Or was my update a fault? #40 called
[Samsung Galaxy Nexus] samizad:
Can this not be a setting in your updater app to turn DCC on and off?
[Samsung Galaxy Nexus] atsavlis:
Luckily for me, 17.2 works with no glitches at all. Missed out on 17.1 as was sleeping, so I moved directly from 17 to 17.2

Whats I do notice is that if I set it to ondemand min 1.5 and max 1.5, clear cpu spy and then play around with the phone, it does not only use 1.5 frequency, but 2-3 frequencies too. Is that normal, I thought with the above setup, it locks the cpu into 1.5mhz?

What programms are you guys using to stress test the different frequencies??

Franco, what governor and frequencies do you reccomend for descent battery and speed?
[Samsung Galaxy Nexus] franciscofranco:
Maybe, I'll see what I can do.
[Samsung Galaxy Nexus] Mukosil:
Just came from gladus Kernel back Tor Francos.

Running on 1000 wir Franco turtle setting.

IT takes so much battery this Kernel on my device...

30 min chatting 11% battery lost.

Maybe someone can tell me whats wrong here.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] marc.tulley:
That's not very helpful Franco lol! Not using 1.5 is avoiding the problem. Would 17.1 help me? 17 only resets after 10-15min of heavy use, its fine idling and short tasks...

Seems there's only a small change to be made somewhere to achieve full stability due to such different responces from different people with the same settings.

Perhaps an intermediate 1.425 or 1.45 step will help those not quite hitting the 1.5 mark get the best out of their phones?
[Samsung Galaxy Nexus] lemmy_0:
can someone upload the zips for 17.1 and 17.2.

I'm not sure why but installing the files I downloaded from the OP shows 16.2 in system info
[Samsung Galaxy Nexus] ro_explorer:
#17.2 is stable for me. No more reboots or freezes. I'll see how it performs in the days to come.
[Samsung Galaxy Nexus] franciscofranco:
Update your cache, the kernel is there http://androtransfer.com/franciscofranco/Galaxy Nexus/
[Samsung Galaxy Nexus] sluflyer06:
Just super wiped then restored phone to google sourced stock image -F then flashed this newest Kernel (with OC since I've never had a issue using it but I don't run above 1.2ghz anyway) and testing currently.
[Samsung Galaxy Nexus] franciscofranco:
http://tinypic.com/view.php?pic=lgp6h&s=5
[Samsung Galaxy Nexus] GchildT:
I don't know why i'm not experiencing the problems some of you guys are having. Interesting...

I keep changing my setup to try to break it, but it still works.
[Samsung Galaxy Nexus] sluflyer06:
New Kernel is doing great so far, SD R/W looks great, no graphical glitches for me on any of these kernels or stock.

Works great at both 1.2 and 1.4ghz. What I'm really looking looking for is battery drain performance which I'll pay attention to the rest of today.
[Samsung Galaxy Nexus] eiabea:
i hope your kernel for the GN will be as legendary as your kernel for the SNS :) but i think you are on a very good way ;)

Is there any chance that the GN also has a deep-idle mode which isn't implemented yet? :)
[Samsung Galaxy Nexus] sluflyer06:
Added to your G.Nex fund :) Thanks for all the hard work!

9JT13623KM432904W
[Samsung Galaxy Nexus] Shetlander:
Just flashed latest OC version now. Will give it a test tonight and see how it behaves in the morning.

What sections of betterbatterystats do you want to see?
[Samsung Galaxy Nexus] drdino:
+1, I haven't had any issues with any of the kernels.

(aside from not being able to get usb host working, that is)
[Samsung Galaxy Nexus] girux1:
Is it safe to flash this over the latest Android Revolution 1.3.2 Rom?
[Samsung Galaxy Nexus] Rey-619:
Recognized something interesting

Will now take a look into spareparts.

[Edit] FC -.-

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] sluflyer06:
Just installed this when you posted. After ~1h30m up time my phone has not used deep sleep...it has also been plugged into my laptop so I dunno if they go to that state but I just unplugged it and I'm about to host a meeting so I'll see if it sleeps during it.
[Samsung Galaxy Nexus] Sim-1:
Just updated to 1212 version.

I noticed you have deleted the line in the 1st thread where you suggested we deleted a line in sys?

BTW thanks for your job, here's my donation!

3RG68923KC127461K

;)
[Samsung Galaxy Nexus] franciscofranco:
When the phone is plugged in it holds a wakelock because its connected to USB ;)
[Samsung Galaxy Nexus] Rey-619:
Thats right, but i tested IT again without plugged in. I know it is a very short time but it realy seems to ignore the deep sleep. This could be the reason for battery drain

Update:

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] DJTaurus:
At last no battery drain for me in todays kernel release without even using setCPU prifiles. Great work franco.... now i hope to cooperate with Revolution HD in your future releases.... best combo for GN ;)
[Samsung Galaxy Nexus] sluflyer06:
Yea..I reset the time in state stats in cpu Spy and it slept the entire time since its been unplugged.
[Samsung Galaxy Nexus] franciscofranco:
Me and mike are talking yes. Most of his inbuilt tweaks are already on my kernel source so not to worry. But we're still discussing :)
[Samsung Galaxy Nexus] Rey-619:
I got the problem...

ragpon wifi keepalive kept my phone on min frequencie...

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] stesmi:
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
[Samsung Galaxy Nexus] ChongoDroid:
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)
[Samsung Galaxy Nexus] atsavlis:
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
[Samsung Galaxy Nexus] poopooface:
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.
[Samsung Galaxy Nexus] marc.tulley:
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.
[Samsung Galaxy Nexus] whiteintegsg316:
What is throttling I see its a on going issue
[Samsung Galaxy Nexus] Elganja:
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
[Samsung Galaxy Nexus] stesmi:
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
[Samsung Galaxy Nexus] ratson:
I am sure the temp which is reported comes from the battery, cpus are usually fine till 70-80C.
[Samsung Galaxy Nexus] franciscofranco:
XDA's spirit is not "install X and Y to get your device over 9000 and doesn't matter how we got there, as long as it works". He gave you a perfect and technical explanation about this scenario so everything has been said.
[Samsung Galaxy Nexus] hnx6310:
Which is better turtle or gazelle????
[Samsung Galaxy Nexus] Niksko:
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.
[Samsung Galaxy Nexus] stesmi:
That makes perfect sense.

// Stefan
[Samsung Galaxy Nexus] JcMalta:
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.
[Samsung Galaxy Nexus] Bram77:
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.
[Samsung Galaxy Nexus] loudaccord:
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.
[Samsung Galaxy Nexus] magn2o:
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.
[Samsung Galaxy Nexus] hnx6310:
.....:thumbdown::banghead:
[Samsung Galaxy Nexus] refaa:
what do u mean by 700/1500???

Mine is 350 mhz 1500??
[Samsung Galaxy Nexus] atsavlis:
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... :p lol
[Samsung Galaxy Nexus] pmicho:
Tried 17.2...neverending bootloop. I use basic settings. I have tried every single version of Franco Kernel since beginning. First time it happens.

Back to 16.1

In any case. Thanks for generous work Franco.
[Samsung Galaxy Nexus] yyz71:
Thank you so much :) I find 17 to be more stable even at 1.5..
[Samsung Galaxy Nexus] drtrmiller:
Since flashing from 16.2, my Verizon 3G (no LTE where I live) disconnects every few minutes, sometimes taking several minutes to reconnect, while the overall signal remains strong. The phone's practically useless for data.

I haven't changed *anything* else on the phone which was working fine before flashing the new nightly.

Is there any way this could be kernel related?

1.5 Ghz was unstable for me as well. The camcorder would not work until I reverted the upper cap back to 1350, and other times apps would stop responding when at the 1.5.
[Samsung Galaxy Nexus] sishgupta:
Suuuuch a quality post. I wish we had this information earlier.

Thank you
[Samsung Galaxy Nexus] nicandris:
yeah my phone could cope with 1.5GHz just fine on #17 but on #17.2 it starts freezing as soon as i select 1.5
[Samsung Galaxy Nexus] marc.tulley:
With all due respect, I did not want a perfect and technical explanation of DCC at all. My problem is with DCC enabled my OC worked less well than with it off, so I was enquiring into the ability to improve stability of 1.5Ghz while keeping DCC off..

I dont think this is an unreasonable question. Just trying to aid in troubleshooting a problem and achieving better results, not just reverting back to when it worked and moving on past a issue. I'm not asking for reckless modifications so am trying to stay inline with XDA's spirit.

If its too bigger problem or you dont want to prioritise this then that is fine. This all only stemmed from my request for an upload of 17.1 as this should be an improvment on 17 which nearly worked for me.....
[Samsung Galaxy Nexus] lillypad_33:
Franco, I just bought your app after using this kernel since the beginning.

Thanks for the hard work.

I am also using a different ROM than most currently ( foxhound )

I'll update to 17.2 and see how she goes.
[Samsung Galaxy Nexus] Elganja:
this was answered already...

http://xdaforums.com/showpost.php?p=22558586&postcount=6386
[Samsung Galaxy Nexus] yyz71:
Ya same here :) this type of info I like...
[Samsung Galaxy Nexus] magn2o:
I set my minimum to 700MHz, and my maximum to 1500MHz in the kernel app.
[Samsung Galaxy Nexus] yeeson:
CM9 overclocked to 1500, the phone is very not fluency!
[Samsung Galaxy Nexus] deezid:
Does GPS work for you? :)

For me it doesn't.

GPS Test doesn't even find any satellite... :eek:
[Samsung Galaxy Nexus] timafey:
Mine is completely broken as well on 17.2. 0/1 birds with GPS test.

What do I use to completely clear my Kernel?
[Samsung Galaxy Nexus] hnx6310:
@atsavlis Scores are very lower at ram...
[Samsung Galaxy Nexus] qwer23:
True, but not the only reason. I can guarantee that my phone was completely cold while benchmarking but I still scored equally low on ram and CPU.
[Samsung Galaxy Nexus] phunghoang24:
i've set CPU at 1.35G:

Antutu benchmark : 5100 -> 5800 points

Linpack : 1:83M, 2:40M, 3:60M, 4:80M (it's not stable)

Quadrant : Sometime :3000 points, usually: 2100 -> 2400, <2000 when it's very hot by wifi and 3G.

:( I want it's stable :(