yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] franciscofranco:
It won't work for the majority of the users. What I'm trying to do is to find a sweetspot for at least 90% of the users, thats why I've been experimenting a little bit with the OC values in the #18.y nightlies.

This is simple:

To allow such big OC values I had to disable Smartreflex 1.5 and use the MPU register override that Ezekeel found. This allowed us to overclock to high values, but SR 1.5 disabled caused SoD's for around 20% of the users, and heat problems for another 20%. Then I added back Smartreflex, which fixed the SoD's but greatly reduced the ability of overclocking so high. Then I released 18.3 with SR1.5 enabled but I left >1,5ghz frequencies on the table, so if users had set on boot with those higher frequencies it would result in an endless bootloop, which I don't understand because I explicitly said in the changelog the problems coming from having >1,5ghz. Then I released 18.4 that has SR1.5 enabled, the MPU register override enabled and 1200,1300,1400 and 1500 frequencies ready for use. As I said before overclocking is a dangerous action, and I don't give any support if users have problems while overclocking. If one overclocks you're on your own, I only provide the means to overclock, nothing more.

And more, users are flashing kernels while flashing beta roms...I never change my roms, maybe thats why I never have issues?
[Samsung Galaxy Nexus] yyz71:
1.5 seems to work for me :)
[Samsung Galaxy Nexus] dmmarck:
Amen to that.

Thanks for the incite; I'll stay at 1200 while I'm in my flashing frenzy. It was addicting, though ;).
[Samsung Galaxy Nexus] drawde40599:
K makes sense, I have a question though? Once u get a " stable " ( i think 18.4 is it ) will u be playing with the higher overclocking (ezekeel) method agn to make them " stable "?
[Samsung Galaxy Nexus] franciscofranco:
The MPU register override is still enabled... But I don't know what I'm doing next, I just want to make this stable and 100% problem free to make it a milestone, then I can play around again.
[Samsung Galaxy Nexus] SpOuK-3-:
1.5ghz issue

**** just saw your previous post **** Sorry for the "already answered question" ! :)

Hey Franco,

Since #18.4 I can't use 1.5ghz ... I select 1.5ghz from your apps and then ... Reboot...

When on #18.2 was running great without any issue...
[Samsung Galaxy Nexus] franciscofranco:
I explained that 3 posts ago..................
[Samsung Galaxy Nexus] SpOuK-3-:
Sorry ... Just edited my post :) hehe
[Samsung Galaxy Nexus] pearse:
Does anyone have a copy of 18.3?
[Samsung Galaxy Nexus] drawde40599:
Ya no I understand 1000% has to be frustrating with works for some not for others?? ... Some feed back --- 18.3 and 18.4 been running since u released, I'm currently at stock settings its running seriously flawless, my battery is more right now than it should be and I've been on phone just as much as normal for me, phone running a lot cooler with current build on and off charger . No hot plug completely stock how it installs . Thanks

Got 3.8 hours screen on time out of full charge . With these ^^^^^^ settings data on, screen brightness 80% ohhhh yaaaa:)
[Samsung Galaxy Nexus] neverhappy:
18.4 700-1500, on demand, hotPplug. Running flawless on CDMA right now. 7.5hrs in and still at 79% with lite use. Other than my "Duh" (left 1.65Ghz set) when migrating from 18.3, both kernels work fine. Thinking back from the first kernel, things are really smoothing out nice from my experience. Thanks
[Samsung Galaxy Nexus] brian_o'fish:
Where can I find that kernel's .config ?

Hello Francisco,

I'm trying to recompile your kernel from the source you put on bitbucket.

However, I'm missing which .config you are using exactly. Can you put that online somewhere, please?

I started with the bitbucket sources of today, and tuna_defconfig.

The first problem I ran into, is your code is missing the cfq-iosched.c

change of this patch:

http://lkml.indiana.edu/hypermail/linux/kernel/1106.0/00548.html

(and probably you don't build CFQ at all?)

The second problem I cannot resolve. Started by complaints about missing profile_pc(), which led me to a '#define ****' instead of '#define CONFIG_SMP' in vanilla kernels, and changing that back led me down a road of funny "arm unwind" ABI stuff that does frighten me a bit...

Now, on the other hand, I run your kernel happily, so you must have resolved these problems, and the only thing I'm missing is probably something your config does different than tuna_defconfig. Thus my request.

BTW, I want to recompile the kernel myself, because one of your recent modifications makes me too nervous: the do_fsync() shortcutting. I don't want that on my phone!
[Samsung Galaxy Nexus] M3drvr:
Running at 1.5 is all good here. Little to no heat too. Much better and smoother than 18.2
[Samsung Galaxy Nexus] slayp00n:
So contrary to everyone else:

18.2 was rock solid stable for me, 18.3 or 18.4 keeps randomly rebooting and the speaker makes a popping noise.

I will stick with 18.2
[Samsung Galaxy Nexus] drawde40599:
Its not the kernel, sounds like u need a good wipe to me, similar thing happened while back and a wipe fixed it .. bet that reset kernel would fix also
[Samsung Galaxy Nexus] woolbeo:
So I copied checkv from Imoseyon's leankernel, modified to use the busybox on my rom, and ran it...

leanKernel Voltage Checker
--------------------------
Nominal Voltage - This is the voltage we choose as the starting point.
Calibrated Voltage - Best voltage chosen by SmartReflex.

Make sure that your screen is turned on...

350000: nominal 1025000, calibrated 850000
700000: nominal 1203000, calibrated 1090000
1000000: nominal 1317000, calibrated 1150000
1200000: nominal 1380000, calibrated 1280000
1300000: nominal 1380000, calibrated 1280000
1400000: nominal 1380000, calibrated 1280000
1500000: nominal 1400000, calibrated 1270000

Is smartreflex using one slot for 1200, 1300, and 1400; or is the script just not written to work correctly with this kernel and the extra slots? Also I find it interesting that 1500 has a lower calibrated voltage than 1400...

BTW I loving your kernel and app. Thank you for all of your hard work.

*Edit forgot to post Stats. CDMA Gnex hw v10 "made in China" AOKP b25, 350-1500 interactive, no UV.
[Samsung Galaxy Nexus] Ezekeel:
I would be angry with myself too. You should punch yourself in the face as a punishment.
[Samsung Galaxy Nexus] lurchie85:
It´s seems like i´m a lucky man with a good Phone ;)

no problems with V18.2 @ 1,65 Ghz overclocking.

No SOD´s, no overheating, everything works fine for me.do a strestest for 30 minutes and everythink works fine.

for me V18.2 will be my daily driver.I only change when a newer Kernel from you got the 1,65 Ghz step back.

Maybe you can pull out 2 Versions of your Kernel.

1 for persons with problems over 1.3 Ghz

and 1 for people who have no problems?
[Samsung Galaxy Nexus] franciscofranco:
Its going to happen as soon as I can call one version as 100% stable.

I wonder why I still come to clubs, this is boring as **** :(
[Samsung Galaxy Nexus] sishgupta:
drink more bro...that's the only way it gets good.
[Samsung Galaxy Nexus] mazubo:
Now that you mention it, I wonder the same thing! Friends, Family, and Franco Kernel :):):)

_______________________________

frAncO Kernel ;-P
[Samsung Galaxy Nexus] drawde40599:
Download unsuccessful

Download unsuccessful!!!!

Download unsuccessful!!!!

Download unsuccessful!!!!

Gooooooogle!!!!!
[Samsung Galaxy Nexus] Terry-Miracle:
the franco's kernel seems good

I'll try it~
[Samsung Galaxy Nexus] SrTapir:
After 3 days of use of 18.x I only can say this kernel is incredibly fast and amazing!

If it helps to anyone, battery drain on standby is minimum, actually quite less than with the stock.

I´m using this values of OC and UV:

Max CPU 1400, Min 700 (as recommended), governor Conservative.

Muito Obrigado Francisco, you´re kernel makes the GN a true rocket.
[Samsung Galaxy Nexus] Gabriel Audemard:
Starting to like 18.4 a lot. No problems.

At first I thought it was a bit heavy on battery, from looking at amps drawn. But now Ive gone 18h45min with 2h45 screen on, and I have 39% left. This is on the first charge. Not bad at all.

This could very much be my personal milestone kernel.

Rom: aokp m3

Thank you.
[Samsung Galaxy Nexus] drawde40599:
What r ur settings? Data on or off? Screen brightness? U have screen shot? Just wondering with almost 3 hours screen on and 18 hours on battery how u did this?
[Samsung Galaxy Nexus] ChongoDroid:
Same, my battery was quick to drop from 100 to 80 but it's crawling now. Might even make 4 hours screen on tonight
[Samsung Galaxy Nexus] Gabriel Audemard:
Well, nothing out of the ordinary. I use the unit as its ment to. Brightness set on ca 40%. Started out with oc 1,5 then 700/1000 conservative. Hot plug enabled. Wifi, sync, data on.

Have screenshots, but I have never attached pictures on here before and I have two kids in/out of my laps. Hard to consentrate on lerning new things.

/Gabriel
[Samsung Galaxy Nexus] drawde40599:
Sounds good thanks, just post pics when u can
[Samsung Galaxy Nexus] MontAlbert:
camera working perfectly on 13 test kernel.. thanks.
[Samsung Galaxy Nexus] anoraknophobia:
Same issue with OC kernel.
[Samsung Galaxy Nexus] The Gingerbread Man:
Provide log cats with reports for Fc, log cat is free app. Wheb error happens open log cat app and press save then upload the log to here with your report with drop box or something.

Edit

Quoted wrong guy silly me :p
[Samsung Galaxy Nexus] EddyOS:
Must've missed that, was looking at the changelog :D
[Samsung Galaxy Nexus] The Gingerbread Man:
All camera features seem to be working fine on franco.Kernel-13122011-GN-OC-TEST-JRCU.zip
[Samsung Galaxy Nexus] bdcdxw:
Hi, i try many version of this kernal . The same problem is wake up lag after a long time deep sleep. In stock kernal, there is no wake up lag.
[Samsung Galaxy Nexus] EddyOS:
13th Dec all working fine, or appear to be. Using the non-OC version
[Samsung Galaxy Nexus] The Gingerbread Man:
The latest OC one still appears to use OC even if I tell it not to. Everything else seems great. No graphic glitches
[Samsung Galaxy Nexus] dwang:
As others have mentioned, the test version solves the camera fc issue.

Also notice that the UI seems to be more responsive and less laggy than before. Of course that may be due to the reboot.

Great job.
[Samsung Galaxy Nexus] franciscofranco:
Its expected as this jRCU is pretty cool!
[Samsung Galaxy Nexus] Sim-1:
Guys if I wanted to revert to stock kernel, how can I do that?

BTW I haven't had any fc with camera app on v.1212... :)
[Samsung Galaxy Nexus] EddyOS:
Try changing to camcorder once you've opened the stills camera ;)
[Samsung Galaxy Nexus] yyz71:
Yep everything's working again thank you :)
[Samsung Galaxy Nexus] sluflyer06:
Have had no problems testing Dec12 version overnight, although I'm seeing alarm_rtc casusing about 2,000 wakelock counts. I don't know what this wakelock is but even with no alarms set it is still causing a wakelock

Drain overnight was ~20% which is a improvement from the past but still pretty high. What should we be looking for testing JRCU, anything in particular?
[Samsung Galaxy Nexus] DJTaurus:
While i was talking to the phone i got a graphical issue poping at the screen....i am with the standard kernel version.
[Samsung Galaxy Nexus] franciscofranco:
Read here about the alarm_rtc and mmc wakelocks from this 3.0 kernel: http://comments.gmane.org/gmane.linux.linaro.devel/5566

Increase your voltages a little and report back. Try the testing build too.
[Samsung Galaxy Nexus] netchip:
Hey, where I can get the source for jRCU?

Sent from my GT-I9100
[Samsung Galaxy Nexus] sluflyer06:
@Franco I did see that doing some google searches however if theres anything useful in there it's above my head as I am not a developer but they do seem to not be addressing the alarm_rtc other than mentioning it in the OP but then again as I said I dont' understand really what they're talking about.

I manage software and hardware configuration tools/processes for US Navy flight simulators but I don't have much interest in actual coding.
[Samsung Galaxy Nexus] beekay201:
Last night i was testing 800mv on 350mhz, all good on stress test, but after a while, my sim was out of service. Bumped it up again to 825mv, no issues since yesterday. :)

Will try test version later.

Edit: I also agree that voltages too low could cause some **** to go haywire.
[Samsung Galaxy Nexus] franciscofranco:
Joe Korty is still polishing it up based on what information I give him. I'm not sure I'm allowed to share it until he officially releases it. Best thing you can do is email him and ask.
[Samsung Galaxy Nexus] lukasb9000:
Why is 700Mhz the recommended min. frequency? Shouldn't it be way more battery draining than 350Mhz?

And another question I've uved my stats and 350Mhz is running with 725mV, is it too low? I think I read something about not to uv too much because it's not good for the cpu. Is it true? 725 runs perfectly no stability issues.
[Samsung Galaxy Nexus] Gabriel Audemard:
Tapatalk app thinks that screen shots have incorrect file extension. They are png and I tried to change them to jpg but no go.

Howe should it be done?

Btw, 22h41, 3h43 screen on, 11%. Time to plug in.

Aokp m3, franco18.4, 700/1000, conservative, hot plug.
[Samsung Galaxy Nexus] kyota:
Sorry, Where can I get old version ? (18.2 & 18.3)

Or some one can share these 2 files for me ? Thank you..
[Samsung Galaxy Nexus] Vangelis13:
http://www.world-of-nexus.com/download-section
[Samsung Galaxy Nexus] nikosrs4:
This and the other post explaining why someone should use 700mhz instead of 350mhz, should be in the 1st post :)
[Samsung Galaxy Nexus] cgollner:
I agree! Never had anything more stable and smooth.
[Samsung Galaxy Nexus] blackdub370:
now yes, now can play whitout lag ! NICE FRANCO!
[Samsung Galaxy Nexus] Jayrod1980:
You know, not to be a downer but 18 hours on time and only a tick under an hour of on screen time at 50 percent is not exceptional battery performance. If you are draining at 1% per hour and the phone gets 4 hours screen on time then 25% plus 18% would put you at 43% lost and you are showing 50%.

I'm not mocking your performance but it seems this kernel and others are losing battery performance and not gaining anything but benchmark scores.
[Samsung Galaxy Nexus] atsavlis:
His battery is on 60% so he is showing 60% which brings him closer to your original 43%.....

Don't know what kernel you are running, or which ones you have tested, but this kernel manages to give our phones great performance and descent battery life. As far as benchmark scores, I get the lowest scores using this kernel, but in using the phone, its clear that it is FAST... as for battery life, I manage 27 hours with about 3 hours of on screen time, wifi on and sync on....
[Samsung Galaxy Nexus] nklenchik:
Alright guys, lets agree to disagree here. This is the smoothest kernel I've been on in my android experience (18.4), and if I get 12-16 hours...which is a whole day for me, school, work, and gym...I'm set.

Yesterday I got 16 with constant texts and music on for for about 4 solid hours.
[Samsung Galaxy Nexus] sluflyer06:
@Franco

Thoughts on adding USB audio support for use with a DAC? There are MANY people who would be eternally grateful.
[Samsung Galaxy Nexus] Laynee1:
Stupido question :

Do i have to wipe anything after flashing new kernel 18.4 from 17.2 which i currently have.. ? :)
[Samsung Galaxy Nexus] bendirkss:
Kind of annoyed at how my battery went down overnight. And does anyone know why my phone might be waking up so many times View attachment 919263

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] Laynee1:
Any one? And my question about wiping ? :)
[Samsung Galaxy Nexus] bendirkss:
FAQ

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] DarkGruf:
No.

Wipe cache and dalvik cache if you want.
[Samsung Galaxy Nexus] ratson:
Exactly the same for me.
[Samsung Galaxy Nexus] DarkGruf:
Search the thread this has been explained by Francisco.

From what i remember/understand it has something to do with going faster in deep sleep if you use 700 and the difference of drain between 350 and 700 not so big. So all together makes 700 less draining than 350 in most of cases.
[Samsung Galaxy Nexus] Tubes6al4v:
Something was waking up your phone throughout the night. What did it say for power consumption by app? You can use system tuner to track cpu usage as well if you want to dig in a bit further.

Sent from my AOKP Gnex

When starting at 350, it requires more time with the cpu and presumably the screen on to perform the same task. So that uses more power. It is akin to how wifi saves power by staying in transmit mode for less time.
[Samsung Galaxy Nexus] franciscofranco:
Yes Im waiting for a DAC and an headphones that FiiO is kindly sending me to try that. In the mean time theres nothing I can do.
[Samsung Galaxy Nexus] franciscofranco:
No signal = bye bye battery.
[Samsung Galaxy Nexus] franciscofranco:
Which frequency are you using to get the reboots?
[Samsung Galaxy Nexus] bendirkss:
I had full wifi though. You still think it was my signal? And what about all those wake ups

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] sluflyer06:
Awesome! Ive got a DAC Destroyer from hotaudio runnin that with a Little Dot mkiii tube amp as far as source stuff and it would be great to use it.with the nexus at work :)
[Samsung Galaxy Nexus] franciscofranco:
Yes. Low signal makes the device to spend a lot of resources to try and find the signal which then makes your battery go kaboom. Wakeups come from a rogue app like facebook or google maps that are constantly using your wifi connection waking your device like there was no tomorrow.
[Samsung Galaxy Nexus] bendirkss:
So maybe turn off my Facebook sync and watch my battery life go up? What can I do about maps?

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] ratson:
Tried with 1.5 and 1.4 , both failed.

#18.2 runs perfectly on 1.65.

#17 run great on 1.5.
[Samsung Galaxy Nexus] franciscofranco:
Maybe your device cant handle those frequencies without hacks. Wait until I start an experimental branch which will have the ability to OC that much.
[Samsung Galaxy Nexus] franciscofranco:
Yes.

About maps well you can either uninstall it or freeze it until you need it.
[Samsung Galaxy Nexus] bendirkss:
I just force stopped it, if thats what you meant by freeze

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] chadouming:
I think he is more speaking of freezing with an app like titanium backup
[Samsung Galaxy Nexus] ratson:
Fine enough will report back how it is doing with newer versions.
[Samsung Galaxy Nexus] bendirkss:
Ya your right. I need to buy the app in order to do so. I turned all my syncs off except for whatsapp and Google. I'll see how that goes today

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] GrandMstrBud:
Just bought the app from the market and it's pretty sweet. You developers are all awesome and I am loving my Galaxy Nexus. First it was the Nexus One, then Nexus S, and now my new baby. I love the boot animation and would love how to make my own but that's way over my head.
[Samsung Galaxy Nexus] Jayrod1980:
My bad! Thought it said 50 percent. Hard to read that battery meter. I use Franco and Trinity almost exclusively. My complaint isn't a knock against the devs work. They are much better than stock. I would just like to see a kernel with over 5 hours on screen time. I have the GSM with extended battery and was getter better battery results with earlier kernels. I would revert but in the process of wiping etc I've deleted them. I saw someone say they got 6 hours with screen on, but I'd like to know if they have push notification, data, etc off.
[Samsung Galaxy Nexus] Vangelis13:
http://www.world-of-nexus.com/download-section. All the old versions of pretty much everything..
[Samsung Galaxy Nexus] atsavlis:
Im guessing the 6 hours are coming from users who use their phones the way that mobiles where used back in the days ie- calls, sms and a occasional picture and at night flight mode. The rest of us are running a mini pc on a tiny battery :p
[Samsung Galaxy Nexus] bendirkss:
Well turning off all my syncs didn't fix my wakes. Seems like my battery is dying quicker even. View attachment 919581

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] heo_con184:
I don't know but I got much battery life with #16.2 than the newer ones.

I could easily get 4h on screen time with #16.2 but have not achieved the same result with #18.x.
[Samsung Galaxy Nexus] Stretlow:
I don't know how many are downloading francos kernels, probably a 1000 or so and you only get a small few with issues.

I think is was generalised there was "some" issues from 13 up however i'll put a good word down for 18.4.

Practically no drain with screen off and am looking to get between 3 and 3 and a half hours of screen time on 50% brightness.

On screen time hasn't been beat yet with the setup I use but the screen off on this one is the best. Oh coupled with absolutely no performance issues.

Keep up the good work Franco
[Samsung Galaxy Nexus] Vangelis13:
Do you have BetterBatteryStats? Try that, maybe you find what's killing the battery.
[Samsung Galaxy Nexus] renaud:
Try other basebands first. Your signal really sucks.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] loudaccord:
That red under mobile network = battery blood. your phone is bleeding. Look into radios, make sure you aren't under volting. For your wake-ups, get Better Battery Stats and check to see what is waking your phone up. Worst case, wipe everything, flash your rom, flash kernel. Do not restore apps with data.

Your battery drain is not due to kernel.
[Samsung Galaxy Nexus] bendirkss:
Ya I've been looking at it a lot for a week and can't see what it is

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] bendirkss:
That's just cause of the area I live I think

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] bendirkss:
Why no UV?

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] drawde40599:
color

Any1 share Franco app color settings . I'm looking for the whitest whites and blackest blacks, I tried messing with settings but I.have no patience and getting frustrated:) ( yes I no personal issue: ):):):):) )

I run my screen brightness 100%
[Samsung Galaxy Nexus] KingDavid63:
Excited about this app and kernel. Just bought it from market, if all goes well I'll be frequenting these thread

Sent from my AOKP loaded Galaxy Nexus
[Samsung Galaxy Nexus] cgollner:
Yes, the kernel is great and the app has lots of exciting stuff :)
[Samsung Galaxy Nexus] loudaccord:
If you UV too much, it might not freeze your phone but it could effect other things. That is one way to rule out the issue you're having.
[Samsung Galaxy Nexus] bendirkss:
I UV -100

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] loudaccord:
I uv 0 and have 0 problems :)
[Samsung Galaxy Nexus] radekg7:
Is this kernel work on latest cm9??
[Samsung Galaxy Nexus] dmmarck:
Yes on toro nightly from 2 25 12 with no problems at all.
[Samsung Galaxy Nexus] drawde40599:
UV

Just putting something out there

I got 45min more screen on time with 100% stock settings than with slight UV settings
[Samsung Galaxy Nexus] Laynee1:
I have used these UV and OC advice.. Can they do any harm ? Im seeing only good battery life for now, but im using it for 4 hours only... And without any heavy use...

Thanks in advance
[Samsung Galaxy Nexus] drawde40599:
For not really being on ur phone, that's a really ****ty battery life . IMO!
[Samsung Galaxy Nexus] bendirkss:
Do you think whatsapp would be whats waking my phone all the time?

Sent from my AOKP Gnex
[Samsung Galaxy Nexus] drawde40599:
What better battery stats say? No one going be able tell u what's keeping ur phone awake . If that's what u think it is freeze or uninstall that app see if issue go away . What radio do.u have?
[Samsung Galaxy Nexus] Laynee1:
Ok i have read the franko wiki and i understand that stock voltage values are best.. So can any one tell me the stock voltages cause i have already undervolted ?

Thanks in advance