yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] joelteixeira:
Francisco,

Since we got many user reports about lag on Zenonia 4 could you please investigate this? I really want to keep using your kernel since everything seems great and your app have many features.

I don't want to use other kernel just because of a game and don't want to quit the game too. :-)

I can't send you a logcat right now but I send you ASAP if it helps you.
[Samsung Galaxy Nexus] rafi300:
How can the 1200 MHz voltage go down to 600mv ? That has to be a typo. :)
[Samsung Galaxy Nexus] erdi06:
This is one of the better Kernels from your last works. This is very stable for me on 1.65 with even some undervoltage and minor tweaks from your tool, i get a good battery life. I am on aosp 4.0.3 and this thing is flying. Thanks for your great work, keep on!
[Samsung Galaxy Nexus] Shetlander:
I was wondering if 1650Mhz didnt have enough voltage as when I run Linpack i get a lot of "inconsistant results". Like with a PC CPU I assume this is down to voltage although I also wondered if this was as a result of thermal throttling making the cpu produce an error.

Anyone any thoughts/results?
[Samsung Galaxy Nexus] bendirkss:
Same. I don't like it
[Samsung Galaxy Nexus] franciscofranco:
Ok I will take a look later on.
[Samsung Galaxy Nexus] franciscofranco:
Set it to 0 0 0 and it will be stock.
[Samsung Galaxy Nexus] bendirkss:
Dunno how. I can't download your app
[Samsung Galaxy Nexus] SpOuK-3-:
Just tried 3 games... No lag.... Running at 350/1500
[Samsung Galaxy Nexus] joelteixeira:
Indeed, I have no complaints about other games. I feel the lag only on Zenonia 4.
[Samsung Galaxy Nexus] slayp00n:
apparently 1.65ghz likes me...
[Samsung Galaxy Nexus] sotoskawasaki:
I am using gummynex 0.7.0 with franco Kernel 18.1 underclocked (700MHz-1GHz, hotplug mod enabled) and I haven't noticed any lag or performance hit anywhere (menu or games). If anything, there might be a slightly performance gain. Maybe its a placebo, but certainly its not worse! Now as battery life, I have to come back for that. One other thing that I noticed, is that it gets to deep sleep faster.
[Samsung Galaxy Nexus] jenicekk:
Again BOOTLOOP, i try version 17.2, 18, 18.2, all version will finish durign the boot. All version from 1 to 16.2 are working properly except 17.2, 18, 18.2.

Im trying to install kernel in to the celan AOKP 23 and Milestone 3 ROM.

are the any posible solutions??
[Samsung Galaxy Nexus] refaa:
Ok i got it..thanks mate
[Samsung Galaxy Nexus] drawde40599:
Happened to me few times only when installing rom from factory reset and kernel right after, if I install rom first let boot up, then back to.recovery and then install kernel works fine . try it hopefully it works fo try it hopefully it works for you
[Samsung Galaxy Nexus] refaa:
Will they be back? And do u rekomend uv ???
[Samsung Galaxy Nexus] iamdata:
I had SOD so no alarm for work this morning. Was after I updated to 18.2 auto flash. Had full battery though. I was expecting it to be dead. I've cleaned cache. Hopefully will resolve. Anyone else had this?
[Samsung Galaxy Nexus] kimboinatl:
Running 18 now, seems smooth so far. Battery drain seems a little high, but I'm guessing it'll settle down soon.

I just noticed that this has a setting for 1.65?? Has anyone run this and remained stable?
[Samsung Galaxy Nexus] refaa:
Freaking lag hihi how is it going?
[Samsung Galaxy Nexus] Gahh Its Lee:
Yes a bunch of us have.
[Samsung Galaxy Nexus] clepsy:
In benchmarks it seems very fast but in real life there are some lag spike, I try also with a 720p mkv video format and for some reason it's lags very bad, the same as in games (gta3), a few seconds of lag.

And a question, how can I get access to gpu voltage? it's possible or?

Thanks,
[Samsung Galaxy Nexus] GchildT:
Benchmark Junkies.... FK18.2 @ 1600MHz
[Samsung Galaxy Nexus] mjchung:
First ever SOD with 18.2 after plugging in with 13% battery. 350/1200 ondemand.

Also, I'm getting a millisecond green flash on my screen upon screen on.

Otherwise, great work as always Franco-
[Samsung Galaxy Nexus] dyndragon:
Do you have hotplug enabled?
[Samsung Galaxy Nexus] _Opiate_:
If you guys don't mind me asking. What's the most accurate/battery friendly CPU temp monitor?
[Samsung Galaxy Nexus] marc.tulley:
Running 1.65 VERY well lol how'd you manage this Franco ? Good job. Although thermal throttling makes it nonexistent during long loads like gaming
[Samsung Galaxy Nexus] danibravo:
not sure if anyone posted this. but here are all the previous nightlies

http://www.world-of-nexus.com/download-section/category/4-franco-kernel
[Samsung Galaxy Nexus] Tanith:
I'm amazed at how stable 1650Mhz is. Awesome work Franco. :)
[Samsung Galaxy Nexus] franciscofranco:
No problem, glad you like it. If you know how to do it better you can email me a patch.
[Samsung Galaxy Nexus] Gahh Its Lee:
I've played every game on my phone... No lag. Ive tried them on 1200 1350 1500 1600 and 1650 can't get any lag
[Samsung Galaxy Nexus] hosmsdos:
Did you play GTA
[Samsung Galaxy Nexus] AzzaD:
so no one else has this issue? doesn't matter what I change it to it always obeys the max CPU but not the minimum, it will always start at 350MHz, I've tried wiping davlik and cache and reflashing, should I try a full data wipe next?
[Samsung Galaxy Nexus] slayp00n:
Can we have a 1.7 and 1.8ghz step?

thanks,
[Samsung Galaxy Nexus] kevyli85:
Does anyone have the custom gamma values from 18.2 changelog?
[Samsung Galaxy Nexus] darrendm:
Jesus, give the phone a chance to realise that you have 700MHz set on boot.

That's such a tiny issue, I cannot believe you are asking for a solution for such a thing. I don't think 13 seconds of 350MHz will damage your phone.

Not sure if serious...
[Samsung Galaxy Nexus] slayp00n:
Changelog:

#18.2

* Added <#18 screen gamma values by default

I dont get what this means.

---------- Post added at 10:01 PM ---------- Previous post was at 10:00 PM ----------

Dead serious. 1.65 is no biggy for my phone.
[Samsung Galaxy Nexus] kevyli85:
They should be init.d scripts that change the gamma to the values before build 18. I have the paid app and my app settings overwrote whatever was in place for 18.2.
[Samsung Galaxy Nexus] nory82688:
Lol I was thinking the same thing, but I don't know its it possible?
[Samsung Galaxy Nexus] slayp00n:
I know their are init.d scripts for it.

I just dont get what he is trying to say with the <18 gamma value.

Also I STOPPED CRANKING UP MY GAMMA VALUE there is a real burn in issues. be careful.
[Samsung Galaxy Nexus] darrendm:
I'm unbelievably shocked how well my phone runs at 1.65GHz.

From when 1.5GHz was introduced, I had an instant lockup and thought I had an unlucky chip but I just flashed #18.2 to test this and it worked perfectly. No crashes, lock ups or SoDs just yet.

Very impressed! Franco did it again!
[Samsung Galaxy Nexus] chardd23:
Is it normal for the gnex to reach 49c while charging and screen on??
[Samsung Galaxy Nexus] qwer23:
Francisco what the hell did you do to my phone? You killed all my precious lag! 1.65 ghz with your tweaked ondemand is running perfect! 18.2 has by far the best performance i experienced by now. Have to test stability and battery life though, but thank you for your time and efforts!
[Samsung Galaxy Nexus] Gahh Its Lee:
I'm sure he could get it to work if its doable however our phones would heat up so quick we wouldnt really get to use it.
[Samsung Galaxy Nexus] marc.tulley:
Lol I can see it now. 'Omgz it booted at 1,8 gigaher*POP*....OMGZ Franco broke my nexus!'
[Samsung Galaxy Nexus] franciscofranco:
Gamma values are -8 0 10 by default.
[Samsung Galaxy Nexus] AzzaD:
Sorry I didn't mean to point out that it was a major issue for me, was just wondering if others got the same result - if noone else does get this I just figured maybe I needed to start off fresh to fix it

If people do generally get this, then I'll stop whining about it :D
[Samsung Galaxy Nexus] franciscofranco:
I'm going to stay in #18.y branch for a while until I can say it's 100% ready to be called a milestone, like many have suggested it would be nice to have 1 absolutely stable kernel and another one with experiments.
[Samsung Galaxy Nexus] diesel2k:
SOD on 18.2. I am back to 16.w

Sendt fra min Galaxy Nexus med Tapatalk
[Samsung Galaxy Nexus] franciscofranco:
Don't use hotplug = no sod.
[Samsung Galaxy Nexus] GchildT:
I too got SOD on 18.2 350 - 1350. 1600Mhz was easy not problems. Hotplug was not enabled. Back on 15.2 for stability.
[Samsung Galaxy Nexus] nic85:
i return to leankernel untill fix these SOD.
[Samsung Galaxy Nexus] AzzaD:
yep discovered that too, I thought it was 1650Mhz making it sod but it they've disappeared since disabling hotplug - maybe you should place a warning message under the option or when it is checked in your app?
[Samsung Galaxy Nexus] darrendm:
Ha sorry for coming across rude.

Just sounded a bit excessive to ask something like that. I'm not sure what it is myself but I assume it takes a bit of time to read the script saying to set that frequency on boot or whatever. I seriously doubt it will have any negative impact on your device or usability. Mine has been in 350MHz for 48 seconds today (it says) and I have my min freq. set to 700MHz (on boot) but I think something like that is so negligible to either bother attempting a fix by wiping.:o

Just had my first freeze at 1.65GHz. Occurred when typing a long message with stock keyboard. I've noticed that typing on the keyboard gives the CPU a higher workload than most benchmark tests. It's probably the predictive stuff working hard at guessing my next move :D
[Samsung Galaxy Nexus] lukasb9000:
Well, I'm using 18.2 350 - 1200 UVed and with Hotplug enabled and didn't get any SOD yet; everything running very smooth. Only problem is that battery life is not so good anymore
[Samsung Galaxy Nexus] dlotters:
@franco

I've also gotten the odd SOD (3 in total since flashing 18.2).

Hotplug was not enabled at any time

The Max Freq was 1200, Min was 700 and scaling gov was OnDemand

I'm not sure if it's relevant but each time I've experienced SOD it was when the phone was either on charge or very recently came off charge (< 10 minutes).

Last night I had the phone with it's screen off for hours and the charge cable wasn't plugged in and it remained fine. I always charge with a wall outlet (AC charge, not USB charge).

The SOD issue is pretty much the only thing I've noticed aside from how brilliant this kernel is... The battery life is incredible, the performance is amazing. Thanks so very much.

Edit: Not sure if it makes any difference, but using AOKP b24 atm and prior to flashing your latest 18.2 kernel I was running Trinity's standard one (1350/384)
[Samsung Galaxy Nexus] minooch:
1.7 & 1.8 are not going to appear, because even if they are added to the frequency list, you can't actually select them.

In fact, issues are starting to appear with 1.6 & 1.65, so they will probably be removed from the next version - There is a very important omap option that needs to enabled (smartreflex - like on a stock kernel) - Without it, I believe that throttling is constantly happening. & personally I would rather have a stable 1500 than a so so 1600
[Samsung Galaxy Nexus] AzzaD:
ah right yeah as long as I'm not the only one I'm happy, and it was pretty much my only issue (albeit minor) with the kernel - which says a lot! :D
[Samsung Galaxy Nexus] drawde40599:
Only only issue I had with the 18.2 was got extremely hot and laggy to.were unusable while on charger . Normal??? No I don't think so my phone will sometimes get up to 115 on charger 18.2 took it to 127 before I shut it down
[Samsung Galaxy Nexus] darrendm:
Same issue here. I don't think its a problem but it does seem a bit warm. Reached a peak of 49C while charging with is higher than normal for sure.
[Samsung Galaxy Nexus] stagejuan:
on 18.2... awesome kernel so far...

newbie questions, just to make sure.. where do i go to check if the hotplug is enabled/disabled?
[Samsung Galaxy Nexus] rahan95:
Hello,

3 sod's since flashing 18.2 as well, even without any OC yet
[Samsung Galaxy Nexus] minipaolo:
I've been using franco's kernels since #13, but I had the worst feeling ever with #18.

It's probably me, but as I cannot fix this i need to switch back to 17.2 for now.

Having sods, hot phone (never happened before) and horrible battery life.

Aokp, 18.2, no hotplug, no uv, ondemand 700-1200

Looking forward to future updates! :-)

Inviato dal mio Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] pstevep:
Thread cleaned. Please don't feed the trolls just report them.

And please don't respond to devs in ignorant "everything broke, u frix nao".. Post your issue in the appropriate way without being a douche..

Thanks again and have a nice day.
[Samsung Galaxy Nexus] Gahh Its Lee:
Thank you. On a new note I've been running this fine minus one incident my phone rebooted in my pocket today. Wasn't doing anything since it was in my pocket (I know because my up time is under 15 hours)
[Samsung Galaxy Nexus] Jrbourque:
I've had one sod no oc ,UV, or hot plug on 18.2 so far
[Samsung Galaxy Nexus] heo_con184:
IMO, #17.2 gave me more battery life than #18. I'm no involved in UV, hotplug, etc.
[Samsung Galaxy Nexus] oilerseberle14:
cant use on aokp b25..... causes reboots when open power menu... please fix
[Samsung Galaxy Nexus] tvnaderwal:
Updated to 18.2 when it hit, have had a few sod's...seems to happen soon after unplugging power...plus woke up to dead phone this morning. Also noticed the phone getting a bit toasty too.. Running AOKP b25, plus no hotplug, OC (700/1200 ondemand) and no UV. Never had sod with 18.1....however, I did flash the ICS-4.0.3-reset kernel, rebooted, flashed AOKP rebooted, then flashed 18.2, used CWR for whole process.
[Samsung Galaxy Nexus] sotoskawasaki:
I am using 18.1, UV, UC (700MHz-1GHz) hotplug mod enabled, default governor and I did not experienced any issues (reboots or sod). Performance is great and so is battery life. I am very curious as to whats causing other users problems.
[Samsung Galaxy Nexus] Jimmy Flip:
I also think this it's a good idea to wipe /cache from within the CWM package. I've just done some experimenting to find out if this is practical because I haven't seen it in any updater-scripts for the GN so far. It turns out that formatting /cache in updater-script doesn't really work correctly and causes a number of issues - probably because CWM already has /cache mounted and is using files in /cache/recovery - but adding this one line to updater-script gave good results in my testing:

delete_recursive("/cache");

It even rebuilds the /cache/recovery folder and creates the log correctly (/cache/recovery/last_log) when you hit '+++++Go Back+++++' in CWM before rebooting. No need to mount/unmount /cache in the script either, and in fact it will cause problems if you do.

I'm interested if this works for others too.
[Samsung Galaxy Nexus] Simer03:
Holy crap Franco....I been using Trinity and just flashed ur kernel cuz I flashed ur kernel on my girlfriends nexus and I just used my girls nexus for a bit and it was so smooth I had to flash for myself....trying your new 18.2 and don't understand the commotion...this is smooth, fast and stable for me!

Is it just me, or does flashing your kernel make the blue colors more bluer?? Its sexy lol

sent from my Nexus Prime
[Samsung Galaxy Nexus] slayp00n:
That's not how cpus work. Also 1.65 is a 10% over clock... very reasonable... 1.8 is 20% still reasonable
[Samsung Galaxy Nexus] Zealotki11er:
18.2 is really working for me. Just tested some benchmarks and CPU score is downhill. Where can i download older version?
[Samsung Galaxy Nexus] bendirkss:
I really don't like the new colors. Is there any way to change them besides Franco's app?
[Samsung Galaxy Nexus] franciscofranco:
Yes, read the OP.

New franco.Kernel updater app update:

#3.2

* Added testing version of Color Multipliers interface - pretty similar to Voodoo Color

* Another try to fix "set on boot" CPU frequencies

* Added preventive toasts when trying to do tasks that require internet connection and no connection is found
[Samsung Galaxy Nexus] bendirkss:
I must be blind. I dont see anything in the OP on how to change the colors:S
[Samsung Galaxy Nexus] LuffyPSP:
Got 2 sleep of death with default settings with 18.1 and 18.2. Otherwise, loving this!
[Samsung Galaxy Nexus] slayp00n:
Since 18.2 my CPU settings and voltage don't stick on boot?
[Samsung Galaxy Nexus] sishgupta:
I'm pretty sure zenonia 4 issues are due to thermal throttling.

I live in Canada and when I went for a walk it was fine. When I am inside and my phone warms up the issue appears.

I'm running 1200 with stock volt.
[Samsung Galaxy Nexus] franciscofranco:
Indeed, but they are now ;)
[Samsung Galaxy Nexus] EsPeHil:
Could it be some new addition in ROMs that causes these. I reverted back to AOKP #24. No lag no sod no problems at all.

Well I didn't have sods in the first place. I have sync always on. Does that prevent the sleep of death?
[Samsung Galaxy Nexus] bendirkss:
Are you saying with your app? Cause I'm looking for a way to do it without your app.
[Samsung Galaxy Nexus] franciscofranco:
Its on the OP.
[Samsung Galaxy Nexus] clefster:
Just had first SOD on 18.2 (No OC/UV but with hotplug enabled).. will try now with hotplug disabled.

No last_kmsg was available to provide (why is this? depends on the type of failure?)
[Samsung Galaxy Nexus] bendirkss:
Well I don't see anything. I guess I'm blind. I'll just wait a few days till I can buy your app
[Samsung Galaxy Nexus] bendirkss:
Anyone undervolting, does it really save much battery? Is it worth it?
[Samsung Galaxy Nexus] asianboy9:
SOD may not be entirely hotplug-related.

I've been crack-flashing just about every one of your nightlies, with hotplug enabled for the past few weeks, and never got an SOD... until version 18.1

Even after then disabling hotplug, with no OC, no UV - still got SOD.

I've now unfortunately had to revert to a previous version, which has always worked for me.
[Samsung Galaxy Nexus] tvnaderwal:
reverted back to 17.2, all good so far..
[Samsung Galaxy Nexus] minooch:
God knows who you're quoting.

But the stock frequency is 1200mhz not 1500mhz

That means 1650 is a 37.5% OC & 1800 is a 50% OC

Oh & Franco, I know I don't say it publicly often, so here goes:

Still Loving This Awesome Kernel!

There we go :)
[Samsung Galaxy Nexus] ChongoDroid:
My colors were still the old ones so I tried the new values manually thru the app and it looks WAYYY better. No more purple! Thank you Franco!

R:-8 G:0 B:8

Let's be honest green just goes crazy if you adjust it lol
[Samsung Galaxy Nexus] qwer23:
Dude battery graph looks very nice and linear with 18.2 and hotplug enabled. Just like with your older 15.1 kernel which gave awesome battery life. Let's see how long my phone will last :)
[Samsung Galaxy Nexus] mike2518:
No ****ting, i'm still on 15.1 and it's awesome.
[Samsung Galaxy Nexus] AfroCreame:
Hey francisco, just sent a little donation as a way to say thank you for all the hard work! Thanks again!

8GK42916M9088202Y
[Samsung Galaxy Nexus] EchoVelocity:
Here's a screenshot for all you benchmark junkies out there.

1.65GHz with onDemand
[Samsung Galaxy Nexus] jenicekk:
Are the multiplier value 196 / 168 / 206 safe for the screen?

White looks great with this setup on my GNEX..
[Samsung Galaxy Nexus] qwer23:
I know :) But try out 18.2, it's great! Even on 1,65 ghz max & 350 mhz min I get amazing battery graph (actual battery LIFE being tested at the moment). If you experience sod/random reboots, just turn off hotplug and kernel is rock stable.
[Samsung Galaxy Nexus] montysweden:
Still no MD5 checksum?

I can't get GTA3 to work. Anyone else with the same problem? I switch back to the stock kernel that comes with AOKP for now.
[Samsung Galaxy Nexus] maisi:
Got a SoD last night, without UV/OC or hotplug :/
[Samsung Galaxy Nexus] qwer23:
Donated a little something via your rootzwiki donate link, I really appreciate your latest kernel.

But I'm still a little concerned if I damaged my hardware at some point, as I get incredibly low scores on Antutu and other benchmarks no matter what kernel or governor I use (linpack multithread: 75, quadrant on performance governor @1650mhz: 3200, Antutu: ram ~700 and cpu ~1000 with completely cool phone). I don't really care about ZOMFG benchmarks but this conerns me :/ Any advice Francisco? Some way to test it besides benchmarks?
[Samsung Galaxy Nexus] rafi300:
Damn! The color tweaks using the new kernel app is awesome! True 8000K color whites using recommended settings . I can't get true GPS lock however internet assisted lock is quick but off by nearly 200 meters. Any solution or workaround for this Franco?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Elganja:
had another SOD last night. 100% stock settings... 2nd one on 18.x first on 18.2

never had them in the past
[Samsung Galaxy Nexus] Elganja:
I feel like everything has a blue hint using the suggested settings
[Samsung Galaxy Nexus] CaspaTheGhost:
I can report another SOD overnight... This time on 18.2, 700/1200, default gov, no hotplug and no UV... Didn't get a log as was then kinda in a rush this morning!

Interestingly, all of my SOD's on 18.x have been whilst the phone is on charge via the mains...
[Samsung Galaxy Nexus] minipaolo:
me too. I changed gamma to -4 0 5 and it looks nicer to me.
[Samsung Galaxy Nexus] Gahh Its Lee:
I've been using -8 0 0. If I go any higher everything goes blue for me
[Samsung Galaxy Nexus] frantic912:
can someone share voltage setting...seem like my volt setting still crash,random reboot...
[Samsung Galaxy Nexus] Gahh Its Lee:
Its honestly not worth it the biggest battery savings you'll see are 2%. One reboot uses more than that but I dropped all mine by 100 awhile back it ran fine but I've since stopped setting it. No difference in battery.
[Samsung Galaxy Nexus] JcMalta:
Why so many problems?

I have been using Franco's kernel since its very first releases and I follow this thread quite closely.

I have NEVER had any issues with bootloops or SODs or overheat etc. - my phone is fantastic.

For a while I was running Paul's excellent MoDaCo ROM ... but the "extras" he provides started to become a little too much and "baking from the kitchen" became too much of a pain for me.

I then settled on Bigxie's Apex 1.0.2 ROM and then nearly every iteration of Franco's kernel. No problems at all.

Maybe I have a "lucky phone" ... but I have never played with OC or UV - I believe that is best left to the experts.

Looking through the thread it seems to be people who **** around with UV, use AOKP (I am not pointing any fingers! - a ROM doesn't get so popular by being ****) and those that piss around with OC to chase meaningless benchmarks suffer problems .....

Just my 2 EuroCents.
[Samsung Galaxy Nexus] Vangelis13:
^^

With you on the ov/oc-ing, however there's nothing wrong with aokp.
[Samsung Galaxy Nexus] JcMalta:
I am sure there isn't! It is a highly popular and highly respected ROM - but I have never run it myself.

It just seems (because of its vast popularity) many people who complain about Franco's Kernel are running that ROM.
[Samsung Galaxy Nexus] StuMcBill:
Hi Franco.

Had a SOD this morning with hotplug enabled, disabled hotplug and just got another one. No undervolting or overclocking.

I emailed logs for the first SOD but never managed to get for the second one!

Cheers

Stewart

Sent from my Amiga 500 using Workbench
[Samsung Galaxy Nexus] AuxXxilium:
3d benchmark with this points? why have i max 1000 points in 3d? what's wrong?
[Samsung Galaxy Nexus] ChongoDroid:
So far this is the latest test... this is great for my usage.
[Samsung Galaxy Nexus] minipaolo:
Franco himself is on AOKP as long as I know. :)
[Samsung Galaxy Nexus] frantic912:
i change it to default setting....:p
[Samsung Galaxy Nexus] ChongoDroid:
Aokp and this kernel go hand in hand.
[Samsung Galaxy Nexus] rafi300:
Umm I don't know , it may be personal preference regarding the blue hue , but this is how mine looks. Its like super white , 8000K h.i.d white style. Check it out and comment.

Regarding the gps , I'm on modacorom ir11b 4.0.4 . Gps worked perfect alone but now with this kernel I get problems obtaining a lock alone without internet assistance.