yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] nn1coH:
I am running PA 3.15 at the moment, do you recommend me to wipe before flashing the kernel?
[Nexus 4 Original Android Development] republitarian:
No need to wipe just flash and your good To go. It is recommended to clear cache and delvik in recovery.
[Nexus 4 Original Android Development] gee2012:
Nope, no wipe needed when flashing a kernel.
[Nexus 4 Original Android Development] tlf55:
Do disabling the logger really improve battery ?
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
What is the intended behaviour of the hot plugging driver for touching the screen? More than one core? 2? 3? 4?
[Nexus 4 Original Android Development] xanthrax:
Not that much but if you're not a "log provider" disable it

sent from my Darkside of Nexus 4
[Nexus 4 Original Android Development] Net.silb:
It's planned to be user configurable, but it ultimately depends on how Franco will implement it.

If he does make it configurable, you will be able to decide for which type of touch event (if at all) you want the hotplugging to happen - none, swipe or touch. You will also be able to decide the minimum amount of cores that should be online when the touch event happens.
[Nexus 4 Original Android Development] Ok_Kaleidoscope5109:
I see. I'm curious about Franco's preferred default. I'd like to know what's a good balance between smoothness and battery life.
[Nexus 4 Original Android Development] franciscofranco:
Yeah it will be configurable as you designed. I cant provide diff of the code today, Im on my way out of the city to watch a festival and I wont make it back until tomorrow.
[Nexus 4 Original Android Development] brian88:
excuse me, where could I download r666? Is that a test version, right?
[Nexus 4 Original Android Development] Luigiesin:
Right here... Put it on the folder "Kernel_Backups". And update from the app

http://db.tt/gaZIdWnb

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco 666/May1

T-Mobile
[Nexus 4 Original Android Development] borsa1994:
Franciscofranco, could you implement the possibility to reduce the microphone gain?

Inviato dal mio Nexus⁴
[Nexus 4 Original Android Development] republitarian:
Use the search or go four pages back

http://xdaforums.com/showthread.php?p=41052557
[Nexus 4 Original Android Development] Luigiesin:
He mentioned before... But it would be great!

Sent from my Rock & Roll Nexus 4 \m/

ROM: PA 3.15

Kernel: Franco 666/May1

T-Mobile
[Nexus 4 Original Android Development] brian88:
thanks, guys :good:
[Nexus 4 Original Android Development] Net.silb:
Thanks again! Enjoy the festival! It's ok to have a life outside of kernel development once in a while! :p (jokes...)
[Nexus 4 Original Android Development] Arstoien:
If I may make a suggestion for increasing battery life: currently the governor enters this high performance mode decreasing the timer to 10k as soon as 4 cores kick in, even if it's not really needed. I think it would make more sense to enter this state either after certain amount of load is met when on 4 cores or after the 4 cores have been online for predefined amount of time.

Thoughts?

I'm testing the new 666 now.

Sent from my Nexus 4
[Nexus 4 Original Android Development] kelah:
I had this with system monitor about week ago. Try clear play store data.

Maybe new play store is little buggy.
[Nexus 4 Original Android Development] Arstoien:
Edit: Ignore this post – something got messed up and it behaved weird. It's fine after I reflashed.

Regarding the new hotplugging:

I've had some occasional stutters on swiping between home screens (with just one calendar widget) but just a couple of times after very quick interactions with the screen.

Generally it looks good but I think it needs some polishing to get the right values. Currently it's offlining too easily, it seems. I cleared franco's app's data after the flash.

After a reboot, not doing anything, I sit and watch the cores and it's a series of 4 cores -> 1 -> 4 -> 1. I don't remember this behaviour with the previous 666.

Also in games it's generally fluctuating between cores, not quite efficiently. With the previous hotplug it would stay on 4 cores all the time in Real Racing 3 and GTA VC, keeping smooth fps. Currently in RR3 it's often staying at 3 cores and about 3–4 times a race it would jump down directly to 1 core. Overall fps is not affected that much thought, but drops are felt when it goes down to 1 core during a race.

In GTA there's something interesting. When the game starts, it stays at 3 cores for about half a minute regardless of what I do and the fps is very bad. Then after that it would jump to 4 cores and stay there stable. Until I hit the pause button which drops to two cores. After I reenter the game from the pause menu it's again staying at 3 cores, causing lag and for the first 20–30 seconds I just can't cause it to increase the number of cores.

PS: The homescreens lag is actually caused by me lowering the suspend_frequency to 486. On default 702 there's no lag. I'm pointing that out though because before I hadn't had such problems even with 384. Only the screen-on would be slightly slower, so I was running it on 486.

Sent from my Nexus 4
[Nexus 4 Original Android Development] LMR1200:
I am losing all Franco settings after a reboot, fi colour and governor settings. Any idea?
[Nexus 4 Original Android Development] franciscofranco:
Try high threshold to 80.
[Nexus 4 Original Android Development] Arstoien:
It is 80. I cleared the app's data and restarted after the flash, so I assume that's the default value?

Sent from my Nexus 4
[Nexus 4 Original Android Development] Etihad:
Francisco, there is one thing missing that needs to be translated in German.

On the main page, line #4:

"Click here to open the menu" --> "Hier klicken, um das Menü zu öffnen".

Thank you.
[Nexus 4 Original Android Development] PetritH:
We are talking about latest r666 which was uploaded last night and it has 90 not 80
[Nexus 4 Original Android Development] Arstoien:
Yeah, I'm talking about the latest too, but it seems I've got wrong values even after clearing the app's data. I'll reflash.

PS: Reflashed and I've got the correct values and everything behaves as it should with the defaults now. None of the mumbo-jumbo I talked about in my previous post.

It's only slightly weird that CPU 2 is the first one to get offlined, then CPU 3, then CPU 4 (from System Monitor's screen). Never seen that before but…

Sent from my Nexus 4
[Nexus 4 Original Android Development] nachordez:
Too soon to talk about battery, but for smoothness, in normal use (I mean, not gaming), last 666 seems EXTREMELY smooth... I'm with stock values, and its the first time I have absolutely 0 lag when fast scrolling between widgets screens, for example.

I could say that even xda app is smoother, but perhaps that's placebo. But widgets screen is a fact. I think this new routine is a good idea.

Thanks, Francisco, and thanks, guys who proposed that (sorry, forgot names).

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] Arstoien:
Yes smoothness hasn't been that good in a while. Facebook lagis noticeably less, and I can now use the vertical app drawer style in Nova launcher without the lag I'm used to see. That's the reason I was using horizontal scrolling instead of vertical.

Sent from my Nexus 4
[Nexus 4 Original Android Development] nachordez:
Yea, same for me with nova!

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] Vangelis13:
I've n e v e r had lag on nova; try setting these two on faster than light.
[Nexus 4 Original Android Development] Arstoien:
The lag is there only if the app drawer scrolling is set to Vertical and you go quickly between different app groups (left/right). It's a combination of lag and touch unresponsiveness (only in vertical scrolling) but the touch thing is something the Nova devs have to work on.

The animation speed has nothing to do with the problem ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] Vangelis13:
Scroll speed then, set that to faster than light.

I've never heard of scrolling lag in the drawer on nova on the n4. :confused:
[Nexus 4 Original Android Development] Arstoien:
It's the transition between the pages that's laggy, not the scrolling itself. I think it's an app problem that needs fixing – it can't be just too much for the s4 pro to handle…

But anyway that's way off topic, and it's mostly gone on the latest 666 ;)

Sent from my Nexus 4
[Nexus 4 Original Android Development] eainyow:
Try setting the drawer style to vertical and scroll through groups in the app drawer you'll see the lag
[Nexus 4 Original Android Development] nachordez:
No. Scroll is a different question in this settings. It's the change between screens, not real scroll through the vertical drawer (which speed depends on the impulse you give with your finger sweep, of course).

And faster than light gives responsiveness... But nearly takes out the effect, which is nice also. :)

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] copi:
but on latest 666 is more drain battery,, do u guys notice too?
[Nexus 4 Original Android Development] nachordez:
Not for me by now, it seems very nice... but it's Sunday, not exactly the usual use, so it's not objective, let's see Monday...

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] copi:
hmm,, or is it bcoz I'm switching rom to jdq39e slimrom,, from jdq39 eos. is jdq39e is more drain than jdq39 u think? if not from kernel wise the drain is..
[Nexus 4 Original Android Development] nachordez:
Who knows? Wait till we see kernel working next days... Or revert to previous 666 to see if ROM has influence on that (easier to change ROM than kernel, ain't it? :p)

nexus4 / stock / last Franco.kernel nightly

gt-p5110 / CM 10.1 / Dhollmen kernel
[Nexus 4 Original Android Development] copi:
already go to m2 hehe.. thank u for this conversation :highfive:
[Nexus 4 Original Android Development] Net.silb:
Guys, the new hotplugging logic has just been implemented and not even fully. There are going to be many changes and improvements to it just like the old hotplugging logic. Just sit back, be patient and keep the feedback coming! :)

If anyone has any suggestions (and I'm sure I can say this in Franco's name), they are very welcome!
[Nexus 4 Original Android Development] malukiz:
Hi,

I've problem with wifi when the screen is off. It's seems that he is totally disabled (music pause and Google play update pause too)

Kernel 134

Rom pa 16/04
[Nexus 4 Original Android Development] franciscofranco:
Sigh...
[Nexus 4 Original Android Development] combatdeity:
[MENTION=3292224]franciscofranco[/MENTION]

Perhaps you could update the OP with common known issues with stock android, would hopefully reduce the number of complaints against the kernel that aren't applicable.

Oh and you could mention Touch Control is not supported and link to the thread.

Maybe all of this in big red text. :p
[Nexus 4 Original Android Development] TonySkate:
Sane issue here, I updated from milestone 1 to r134, when the screen is off in every receive notifications... I back to milestone 1 and everything works fine

Enviado desde mi Nexus 4 usando Tapatalk 2
[Nexus 4 Original Android Development] ceejay83:
Doesn't make sense when Franco hasn't touched anything regarding Wi-Fi or data.
[Nexus 4 Original Android Development] fozzie:
Just to say that I'm getting great battery & performance on Franco's r.666 from 2nd May (the one before the reworked hot plugging).

It's been fairly light usage today & mainly WiFi, but after 10hrs, my battery monitor predicts still a whole day of usage left. As somebody else days previously, this kernel really does sleep like a baby :)
[Nexus 4 Original Android Development] franciscofranco:
No one reads the OP :p
[Nexus 4 Original Android Development] zephiK:
You should make people take a multiple choice quiz based off your op faq before they can download your kernel :p
[Nexus 4 Original Android Development] bradm23:
I gotta say that the newest r666 has been awesome! Getting great smoothness and performance and battery life is best to date. So far I have had 45 min screen on time on WiFi in 3 hours and only down to 90%. I usually am down 10% after 30 min!
[Nexus 4 Original Android Development] Shano56:
Wuts a op ;o
[Nexus 4 Original Android Development] ceejay83:
Think Franco should edit the op so the download links are below the faq. That'll force people to actually read it :p
[Nexus 4 Original Android Development] mundixx:
Guys, sorry if this has been asked before. Can

anyone share their values for accuracy filter?

Tapatalked from my AOSPA Nexus 4
[Nexus 4 Original Android Development] Karlo666:
I get same that on the lowest brightness and i get 30 minutes on 50% brightness.

Test on 3G then we talk.
[Nexus 4 Original Android Development] fozzie:
Values? Accuracy filter? Franco kernel?
[Nexus 4 Original Android Development] zephiK:
Or make them decipher the URL link in bits throughout the FAQ. Just have the URL links in a color so the user would have to copy paste bit-by-bit haha.. okay that was a little bit too harsh :p but on topic, pretty satisfied with r666. Can't really find anything to complain about, great battery life while withstanding great performance. I'm personally not on the OCing type so I can't comment on OCing.
[Nexus 4 Original Android Development] razor 116:
1 Day 16 Hrs 25m battery life with 22% remaining and 4Hrs 33m 47s screen on time, I'll take it lol. Nominal CPU with 125mv undervolt at all frequencies.
[Nexus 4 Original Android Development] Beremus:
Battery on r666 (Franco's one) seems really good. LTE enabled, I was able to squeeze 4h SOT with 10% left, playing games, facebook, xda, etc.

The experience is good. The phone is a lot more fluid. I've got the status bar bug again, few times in fact. But it's not annoying.
[Nexus 4 Original Android Development] Krunk83:
I never see these numbers but then again I am a power user.
[Nexus 4 Original Android Development] LibiSC:
[MENTION=3292224]franciscofranco[/MENTION] could you upload your .Config file... I'm having a mod post error when compiling... I think is that
[Nexus 4 Original Android Development] Cuzz1369:
Getting a lot of the notification drop down lately on M2. Never used to be that bad. Once a week or so before, now many times a day.

Carbonized and francofied N4
[Nexus 4 Original Android Development] razor 116:
I've never experienced the status bar bug at all. I would guess there were specific ROM, Kernel combinations would create the status bar bug.
[Nexus 4 Original Android Development] aventu:
can you already modify the mentioned parameters manually?
[Nexus 4 Original Android Development] Net.silb:
I don't know about that but I can tell you that the parameters that regard touch aren't there yet because the hot plugging on touch events is not implemented yet.
[Nexus 4 Original Android Development] Underground_XI:
The status bar thing im starting to think is hardware flaw because i got two nexus 4 both same exact setup, one has that issue, the other does not which is weird....
[Nexus 4 Original Android Development] dhurk:
Mine is stock and i have the issue
[Nexus 4 Original Android Development] pkelly517:
In terminal, try

zcat /proc/configure > 'where you want the text file'

---------- Post added at 12:46 PM ---------- Previous post was at 12:45 PM ----------

Man, Tapatalk and auto correct suck at times.
[Nexus 4 Original Android Development] LibiSC:
I can't believe I forgot that... It's been a while since I compile stuff thanks
[Nexus 4 Original Android Development] pkelly517:
Tapatalk still sucks.
[Nexus 4 Original Android Development] Shano56:
Franco have you considered (if possible) to disable touch input on pixel 1,1 for a couple seconds after screen on? I think that should squash the drop down bug. I know its a workaround and not an actuall solution, but it might work.
[Nexus 4 Original Android Development] Testraindrop:
Well nothing franco can do about that, are the tapatalk devs on XDA?

Would be good to tell them how laggy it is and that sometimes it posts multiple times the same message -.-
[Nexus 4 Original Android Development] kelah:
I have never had it on stock kernel. On motley kernel too. About other kernels - don't know, but it is software thing.
[Nexus 4 Original Android Development] LibiSC:
I

Still the modpost error so wasn't the config

WARNING: vmlinux.o(.text+0xadec): Section mismatch in reference from the function first_level_work_check() to the function .cpuinit.text:cpu_up()
The function first_level_work_check() references
the function __cpuinit cpu_up().
This is often because first_level_work_check lacks a __cpuinit
annotation or the annotation of cpu_up is wrong.

WARNING: vmlinux.o(.text+0xb180): Section mismatch in reference from the function decide_hotplug_func() to the function .cpuinit.text:cpu_up()
The function decide_hotplug_func() references
the function __cpuinit cpu_up().
This is often because decide_hotplug_func lacks a __cpuinit
annotation or the annotation of cpu_up is wrong.

To build the kernel despite the mismatches, build with:
'make CONFIG_NO_ERROR_ON_MISMATCH=y'
(NOTE: This is not recommended)
make[1]: *** [vmlinux.o] Error 1
make: *** [vmlinux.o] Error 2

Edit: well adding __cpuinit to some of the mako hotplug functions solved the problem
[Nexus 4 Original Android Development] drawde40599:
134

Used both of last 666 builds and im back to 134 now with high set to 70 rest stock and now OC, while new 666 is definitely lil faster 134 is right up there in speed and smoothness to were nit really noticeable, battery life is always abiut the same with me i always get 4 hours SOT and by then im plugging in charger so cant really say what build will pull more than that, but reason i keep going back to 134 is it just seems "smarter" and runs cooler, i dont no if "smarter" makes any sense to anyone but it's only word I can think of.

Thanks for your time franco
[Nexus 4 Original Android Development] nexusmaniac:
One thing I've noticed with the second iteration of r666 is that my device gets pretty toasty with even basic things like using xda and watching YouTube just thought I'd mention that :)

N4/N7 - CM 10.1 Nightly, Franco Kernel
[Nexus 4 Original Android Development] Arstoien:
I haven't noticed increased heat. With UV -125 it's getting warm only in games and I can still play on USB charger with the temperature reaching about 60°C.
[Nexus 4 Original Android Development] franciscofranco:
r134 is awesome indeed! But need to keep trying new things, thats the joy of it :) thanks for the feedback!
[Nexus 4 Original Android Development] malukiz:
I have updated to the 04/05 PA rom and now the problem is gone. (maybe it's related to the rom, flash cache, dalvik, kernel have solves the problem)

I'm sorry for had made you sigh :angel:
[Nexus 4 Original Android Development] drawde40599:
Something ive been doing is i have a backup of a full 100% rooted stock rom its the rom and what came with it out the box + superuser and busybox, any time i have a strange issue i restore my backup and install whatever it is im having issue with, whether is a kernel or app or mod or whatever im doing to try rule out.......... Just something thats come in handy for me ;)
[Nexus 4 Original Android Development] quiquegabriel:
Running #r666 and for my personal usage its the best one. Really really smooth and battery is doing pretty well so far. I think some changes still have to be done. Looking forward to them. But i really like the secong test version of 666.:good::good:
[Nexus 4 Original Android Development] dbellonate:
Red Light of Death

Has anyone else experienced this issue with latest r666? I decided to benchmark it for fun (turned out to be no fun at all!) and whilst testing CPU intergers the phone turned off and now I have the red light of death. I have charged it all night and then managed to get it into download mode this morning and flashed stock google image but it still wont turn on (if it does it gets to the 'Google' screen for maybe 2sec and then it turns off).

Any suggestions? I have tried every option that I could find except pulling the phone apart.
[Nexus 4 Original Android Development] llevo3:
[MENTION=3292224]franciscofranco[/MENTION] thanx for AndroidPIT update!
[Nexus 4 Original Android Development] republitarian:
http://xdaforums.com/showthread.php?t=2177787
[Nexus 4 Original Android Development] drawde40599:
There's a whole thread on this issue, dont have link but ive seen it its general section if i remember right
[Nexus 4 Original Android Development] republitarian:
I just posted it above your post
[Nexus 4 Original Android Development] thebryceee:
Did you run antutu at 1.7ghz?
[Nexus 4 Original Android Development] kyokeun1234:
If I were you, I would've just RMA'd I think this isn't the problem with the kernel but the phone itself
[Nexus 4 Original Android Development] thebryceee:
Been playing with those settings. Relaxed feels tons more fluid. I like it.
[Nexus 4 Original Android Development] LibiSC:
Just to say i managed to compile it... a little different procedure to repack it from my days in galaxy ace... now i will play a little for personal use.

Edit:

[MENTION=3292224]franciscofranco[/MENTION] now i only have screen color tuning in the app.... do the options depend on the build or the app doesnt recognize my build as your kernel?

Edit #2: well your app checks the build number so i had to change KBUILD_BUILD_VERSION. It solved it.
[Nexus 4 Original Android Development] Haomuch:
Used r666 for two days and it does feel smoother than 134. But the battery life also recorded a hit to at most 4 SOT. I think even the M2 is smooth enough but it has much better battery life.
[Nexus 4 Original Android Development] bvx89:
I did the exact same thing, and had the exact same problem. Solution: Open up your phone and disconnect the battery connector. That's all it took for me at least to get it back up.
[Nexus 4 Original Android Development] DeZire17:
Can you add UV Profiles to your app? It would be great.

Im stable at -130 UV but I don't want to set it on boot, so instead of UVing manually every time, I can save profile at -130 UV and load it every time.

* I know that I can UV -125 in 5 clicks, but I need to UV -5 manually every time to get -130UV.

Or just add (not replace) -10 UV button... It will solve it too.

Thanks!
[Nexus 4 Original Android Development] AshtonTS:
What's the best gamma settings? I've tried all the included profiles and none of them are just right, I'm trying to get them to match my iPad.
[Nexus 4 Original Android Development] DeZire17:
Franco. Kernel updaters's Recommend Settings...
[Nexus 4 Original Android Development] Arstoien:
Different hardware, different user preferences... There's no definite answer. Try more and more till you find ones you like. Look through the colour spreadsheet in the thread here at XDA, you'll find a lot of presets there.
[Nexus 4 Original Android Development] Underground_XI:
Make your own then:)
[Nexus 4 Original Android Development] drawde40599:
Thats not possible, but if u do a search in this thread u can find a drive page with settings that people have made and there sposed b close to what u want
[Nexus 4 Original Android Development] hern1989:
The high speed load under governor control doesnt stay when i set it. It goea back to 99… im on r134 and FKU 9.3.3. Is this a bug?
[Nexus 4 Original Android Development] rxmxsh:
I had that issue. I had to RMA my phone. Disconnecting the battery didn't help.
[Nexus 4 Original Android Development] dbellonate:
Thanks heaps I will try out the suggestions that i found here that I did not find elsewhere :)
[Nexus 4 Original Android Development] AshtonTS:
Why wouldn't it be possible to get it to look like the iPad? Apple did it with their screens, so why can't we do it with our screens.

Sent from my Nexus 4
[Nexus 4 Original Android Development] Underground_XI:
Different hardware involved but since you like apple screen so much get an apple product then.