yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] gharrrrrr:
Known bug between Franco kernel and superuser. If you want to use any ROM with superuser baked in and Franco then you will have to flash SuperSu instead.
[Nexus 4 Android Development] derEremit:
Ok, thanks for the hint.

Is there any chance this might go away. Should this ultimately be fixed in franco kernel or on the rom part?
[Nexus 4 Android Development] gharrrrrr:
Hard to say. I know Franco was looking into a fix a release or two back. It didn't work. So, not sure if that is still work in progress or if he is waiting for fix with SuperUser built into many Roms. The SuperSu fix works fine though until one or the other is fixed.
[Nexus 4 Android Development] derEremit:
do you mean this:

http://download.chainfire.eu/351/

that didn't work for me
[Nexus 4 Android Development] gharrrrrr:
Try this instead. http://download.chainfire.eu/372/SuperSU/UPDATE-SuperSU-v1.86.zip
[Nexus 4 Android Development] kelvin99:
[MENTION=814142]dIRE[/MENTION]remit been using franco kernel for a long time..yes i've lost root...you can flash the supersu 1.69 ..because i think the latest supersu will have same problem..no su binary installed..you better try the old version..and update it..sorry i cant give you the link im in a mobile right now
[Nexus 4 Android Development] gharrrrrr:
SuperSu works just fine with Franco. Never had a problem with it. Only with SuperUser. To completely different things. SuperSu 1.86 works perfectly fine with Franco.
[Nexus 4 Android Development] derEremit:
thanks, the version you linked to worked.
[Nexus 4 Android Development] UltraBoykj:
Been a fan of the sabermod lines since 4.2.2. Thank you for the work. Whether its in my head or not, most ROMs feel smoother once I install this.

Puritized with SaberMod
[Nexus 4 Android Development] hughfollett:
Does this kernel have the incoming call wake delay? Also, can I use fku to change settings?

Thanks in advance!

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] gharrrrrr:
Yes you can use FKU
[Nexus 4 Android Development] Luigiesin:
r200 is out guys! Lots of new stuff! Hopefully this notification bar lag in my phone disappears for once and for all! :)
[Nexus 4 Android Development] hrishi420:
waiting for your new update
[Nexus 4 Android Development] gharrrrrr:
Really? You too!? #sarcasm. Devs do what devs do. Patience is a virtue.
[Nexus 4 Android Development] xcstacy:
Sorry guys I don't have my laptop with me now. Will only be able to build on 3/1 so use Franco's till then ;)
[Nexus 4 Android Development] stonebear:
We can wait. :)
[Nexus 4 Android Development] krjadejesus:
Sir. We are excited, where is the new build it is already 3/1??? :)
[Nexus 4 Android Development] ernestnwanu:
It's coming, just be patient
[Nexus 4 Android Development] xcstacy:
Hey guys, as promised here's franco sabermod r200!!

Changelog

Stock:

Updated to franco r200

Edit: I forgot to include latest fauxsound in stock :P Will do that in the next build, sorry!!

Download: Link

Test:

Updated to franco r200

Linux 3.4.75

Latest fauxsound patches

Qseecom patches from caf

mm patches from labodj hammerhead git

Random patches from 3.13-rc4 (Thanks mirage)

Disabled frandom (latest random backport should eliminate all entropy issues)

Misc topology tweaks from Synthetic.Nightmare git

Download: Link

Apologies for the delay everyone. Happy new year! :)

PS: Still trying to figure out the prima issue. May upload a new test with the latest prima ;p
[Nexus 4 Android Development] desiromeo719:
Yesss!!! Thank you! :) Happy New Year!
[Nexus 4 Android Development] Luigiesin:
Thanks brother... Test version still has Prima right?
[Nexus 4 Android Development] xcstacy:
Yup prima driver is present in all stock and test versions.
[Nexus 4 Android Development] xcstacy:
I need someone to be CM tester. Any volunteers?

Edit: Nvm tested it myself. :)
[Nexus 4 Android Development] xcstacy:
Yup it sort of works. No reboots so far. Only problem is that some parameters are not tunable.
[Nexus 4 Android Development] hulicow:
franco Kernel 201 is out..
[Nexus 4 Android Development] stonebear:
I am just a a "user" and don't know noffink but just wanted to report still issues with this kernel. :cowboy:

Battery life doesn't seem quite as amazing as when I was on stock rom and version 197 Prima but still good.

That could be because I am using a mod rom now with xposed too?
[Nexus 4 Android Development] xcstacy:
Thanks for the feedback. My battery life with r200 Test is horrible too so I am trying to solve the issue. r201 will be pushed probably tomorrow or day after.
[Nexus 4 Android Development] Luigiesin:
That's interesting... My battery with r200 has been amazing! The best so far. This is with test version.
[Nexus 4 Android Development] stonebear:
Nice one. :)
[Nexus 4 Android Development] stonebear:
I was reporting on the stock one, will flash the test now.
[Nexus 4 Android Development] xcstacy:
Here's an update! :good:

Changelog:

Stock

- franco r201

- updated fauxsound to v3.2

- upstream to Linux 3.4.75

- neon-vfpv4 instead of neon

LINK: http://d-h.st/VGn

Test

- franco r201

- prima driver v3.2.3.196

- futex patches from labodj hammerhead git

- fastcharge driver from faux

- neon-vfpv4 instead of neon

LINK: http://d-h.st/8oh

Guys, I will have to stop building the kernel for awhile due to my forthcoming exams. Will resume building after 19/1/2014. Till then, reply here or drop me PM if you encounter any issues with r201. :D
[Nexus 4 Android Development] stonebear:
OK mate and thanks for all your work. :)
[Nexus 4 Android Development] ernestnwanu:
Thanks for the update. Is the test version also updated with the latest fauxsound?
[Nexus 4 Android Development] xcstacy:
Its already been updated to the latest fauxsound in r200 test. ;)
[Nexus 4 Android Development] hulicow:
Does touch control by bponury works now? and also does it have stratosk brightness driver? Thanks sir.
[Nexus 4 Android Development] Luigiesin:
201 is a monster! Loving the fact that you included faux supercharger... Thanks brother!
[Nexus 4 Android Development] xcstacy:
Touch control still doesn't work. Bponury said he will not support non stock toolchain so we are on our own here. Stratosk brightness driver was taken out from previous build due to poor reception.
[Nexus 4 Android Development] boeder9:
what CM version did you use? 10.2? how is the stability thus far?
[Nexus 4 Android Development] xcstacy:
I tested it with CM 11 and a couple more custom CM 11 ROMs out there. It doesn't cause FC and reboots so far. The only issue is the heat caused by not configurable kernel parameters.
[Nexus 4 Android Development] Luigiesin:
I feel r200 had much better idle drain that r201... But 201 doesn't have supercharger from Faux..
[Nexus 4 Android Development] xcstacy:
Yup the issue is present in Franco r201.
[Nexus 4 Android Development] jokkir:
Can someone tell me or link me to an explanation of what the Prima drivers are instead of a simple "updated WiFi drivers". I want to know the advantages and disadvantages of using it and possibly where it originated from.

Google didn't really help me find the answer for this.
[Nexus 4 Android Development] xcstacy:
http://xdaforums.com/showthread.php?p=48112307
[Nexus 4 Android Development] krjadejesus:
Nope. 201 has better battery compared to 200.
[Nexus 4 Android Development] Luigiesin:
Went back to r200... This version is the best so far. Baftery/performance... Don't think I'm moving from this one for a while ;)
[Nexus 4 Android Development] stonebear:
197 seemed the best battery for me, but it is hard to tell without doing proper tests. I am using Gnome ROM atm so I am using his kernel but I will be trying this again. :)
[Nexus 4 Android Development] xcstacy:
Franco sabermod r201a Test.

I would love some feedback about the battery life with this version.

https://drive.google.com/uc?id=0B-q9LvlYB2cndVEyTnV1N0l6d00&export=download

Note: This is highly experimental. Use it at your own risk.
[Nexus 4 Android Development] desiromeo719:
Can you tell us what changes you made or are you trying to keep it a secret?! Looking forward to try it either way.
[Nexus 4 Android Development] xcstacy:
I am trying to see if the commits are placebo or it really helps with battery life. So yea I'm not going to reveal the patches until later.

Go ahead and give it a go! Its basically r201 test plus additional battery patches.
[Nexus 4 Android Development] desiromeo719:
Gotcha...I was one of those that had worse battery life on 201 and then read a bunch of other people having problems and reverted back to r200. Now im wondering if it was really becuase of r201 or some other problem that randomly caused the battery problem....

I just turned on smart radio on cataclysm rom to see if it would help the msm hsic wakelock that was killing my battery...so ill have to wait till tonight to flash to 201a test to compare with 200 test...
[Nexus 4 Android Development] jmtjr278:
Just flashed this improved 201 today and now 202 is out.
[Nexus 4 Android Development] nachordez:
Seems Franco 202 is having deepsleep problems. So, don't hurry up OP to build. Better to wait and see...

from gt-p5110
[Nexus 4 Android Development] desiromeo719:
Hmm ok so here goes....

I installed r201a test yesterday...charged up and ran it today. At first it seemed like it was sipping on battery and would be better. But with pretty much the same usage as any other day I am pretty much at the same battery life. Yesterday on r200 test I got about 14 hour runtime with 3 hour SOT(Im always on 3g). Today on r201a I got better runtime(about 17 hours) with about the same SOT(maybe less). SO it seems like r201a uses more battery with screen on but less with screen off(this could simply be because of the changes between 200 and 201)...This is all just what im seeing. There is a blizzard going on today which wasnt yesterday so dunno if the weather conditions are messing with cell signal at all....I am also getting music stuttering on r201a test which I didnt have in any of the previous versions. This was all compared to r200 test and not regular r201 test. This is all just my observation from unscientific testing...Seems like the battery patches didnt do much?
[Nexus 4 Android Development] attaint:
Screenshots of your battery stats would make this post much more reliable and we could take more from it. Try raising voltage to stock to try and fix the music stuttering, but it could also be your ROM.
[Nexus 4 Android Development] amarb70:
Is there any zip to use when wanting to reset the prima drivers? I have attempted the stock 4.4.2 kernel and ak's deprimer; both didn't reset the kernel and remove the drivers.

Yes I know you can dirty flash your rom but I don't have the zip downloaded and was curious to see if there's any other way.

Thank you.

...sent from space
[Nexus 4 Android Development] jmtjr278:
Seems 203 has been released.
[Nexus 4 Android Development] Luigiesin:
Still navigating with r200... Still the best out of the latest ones... Let's see how 203 goes :)
[Nexus 4 Android Development] Luigiesin:
Seems that battery bugs are pretty much fixed on 203!
[Nexus 4 Android Development] nachordez:
Seems so.... :)

from gt-p5110
[Nexus 4 Android Development] jayRokk:
Yup can't wait until this gets updated to 203. I run this kernel with every ROM I flash and it never fails!
[Nexus 4 Android Development] desiromeo719:
I pretty much got identical battery life on stock Franco 203 and Franco sabermod 201...

I did disable nfc and animations too on 203...but that probably doesn't make much difference anyway...

Performance on 203 is amazing tho
[Nexus 4 Android Development] gharrrrrr:
Hate to be "one of them" but I love your kernel. Really looking forward to a SM Franco Test for us N4 users! Thanks again guy for ur work. :D
[Nexus 4 Android Development] ernestnwanu:
Interesting, mine doesn't like anything under -50 anymore. But only recently. Used to set it to -150 without delayed notifications on wifi.
[Nexus 4 Android Development] ernestnwanu:
Ehh I hope this hasn't been abandoned..
[Nexus 4 Android Development] desiromeo719:
I was about to say first Atlantis from cataclysm and now xcstacy from here...where are all my devs going...
[Nexus 4 Android Development] gharrrrrr:
Aliens
[Nexus 4 Android Development] Luigiesin:
LOL!
[Nexus 4 Android Development] jayRokk:
Its not abandoned ;)
[Nexus 4 Android Development] xcstacy:
No guys I haven't abandoned the project. I just haven't got the time to work on the kernel.

R203 is partially ready with latest sched-dl from mainline so please look forward to it. :)
[Nexus 4 Android Development] deltatux:
I've been on regular franco with -125mV no problem.

deltatux
[Nexus 4 Android Development] UltraBoykj:
Is-50 to -125 the accepted attempts that are working? I've only recently started with undervolting and a tad timid - but what I've tried has improved batt life. Would like to push this as far as I can.

As a side note, the 29/01 version of this rom is the first that doesn't auto cap my 'i' into 'I' while swype typing ( except when it begins a sentence ). I know there used to be a setting for it, but it seems to be missing now.

---------- Post added at 05:35 AM ---------- Previous post was at 05:27 AM ----------

Sigh sorry. I was reading two threads and crossed my streams. Ignore the 2nd part of the above msg.
[Nexus 4 Android Development] mystx2112:
From my understanding how much one is able to undervolt depends on the bin of the processor. I've got a fast binned cpu. -125 has worked well for me, with no stability issues. -150 would cause the occasional reboot. You can determine what bin your processor is by using this terminal command: su

dmesg | grep PVS
[Nexus 4 Android Development] nachordez:
Sorry to say no.

The binning of the processor just means about what is it's default voltage (it differs on binning), but how much your CPU admits UV depends on individual processors. Two fast binned ones can support different UV. Mine is also fast and can't go further than -75, other are slow and resist even -150 or more. You have to try. Being careful!

from Nexus 4
[Nexus 4 Android Development] C.T.Richter:
I can confirm this, I have a slow bin and I can go as low as -150 while still stable. And I used to think those "lucky fastest bin" could easily go to -200 doing a little research.

I just don't know if the processor binning means anything to overclocking, if fastest bin is more stable than slow bin at higher frequencies.
[Nexus 4 Android Development] Luigiesin:
Man I so miss your kernel! :)
[Nexus 4 Android Development] hrishi420:
Waiting...... Waiting...... Waiting...
[Nexus 4 Android Development] jayRokk:
Why wait?

I'm still running 201 with PA and get the best battery life and performance. 202 and 203 have some severe bugs that need to be ironed out. So wait until Franco releases 204 with fixes.
[Nexus 4 Android Development] xda_emanuel:
Any chance to put the new prima driver into this kernel? https://www.codeaurora.org/cgit/external/wlan/prima/log/ . Recently they has fixed alot stuff.
[Nexus 4 Android Development] MAXGEN:
I"m trying to compile the Franco kernel. I download the git and tried doing a make but no success. I get an error. I have had success compiling AOSP kernel but just trying to compile this custom franco kernel. I haven't tired it with Sabermod or Linaro toolkit, that will be next. Thanks for any help.
[Nexus 4 Android Development] poondog:
Ok so what's the error?
[Nexus 4 Android Development] MAXGEN:
Yeah there was this error midway.

Franco respond in another post

Originally Posted by franciscofranco View Post

Yes, its my bad, I haven't fixed that code in Ondemand because I don't use the governor (I'll push the fix tomorrow regardless). You have to implement something like this on Ondemand: https://github.com/franciscofranco/h...55f970a50c9fbb disregard all the thread_migration code, focus on the get_cpu_idle_time part. Basically I've added to cpufreq.c the generic get_cpu_idle_time function so you'll just use that instead of using the implemented get_cpu_idle_time on Ondemand.

Can I do something to the git so I can build a earlier release...maybe r32?
[Nexus 4 Android Development] poondog:
hmm I do not see the link. That code is fixed in francos main repo? Maybe easiest thing to do now is to copy/paste cpufreq_ondemand.c from the latest franco kernel in his repo, and hope it compiles on your machine. Or, you can in the defconfig or .config remove the ondemand governor (# CONFIG_CPUFREQ_ONDEMAND is not set) or whatever it says :P

Basically the reason is this

instead of defining the thread migration code in both interactive and ondemand, it can be used in cpufreq only once. So he has moved it all to cpufreq, but you still have it in ondemand. The compiler doesn't like the fact that its there twice
[Nexus 4 Android Development] MAXGEN:
Its his nexus 5 hammerhead. I want to eventually use Sabermod but at the moment I can't compile is with AOSP tool kit.

https://github.com/franciscofranco/hammerhead/commit/05a63750c0edfd4090512d9b7f55f970a50c9fbb
[Nexus 4 Android Development] poondog:
The AOSP toolchain is nowhere near as strict as sabermod/linaro/christopher83

You need to fix this code in order for it to compile on any toolchain

The thread migration code needs to be removed from ondemand like it has been removed on interactive, or if you disable the ondemaand gov it will not have the error

edit: I just looked in xcstacy github and in the defconfig ondemand gov is disabled like on franco kernel was

https://github.com/xcstacy/mako-lin...ca8ab5/arch/arm/configs/franco_defconfig#L706
[Nexus 4 Android Development] philosophics:
Pretty sure I know the answer but it doesn't hurt asking.

Can you build this same kernel but make it compatible with CM/CAF?

PAC 4.4 was releases and I'm sure there will be plenty of people asking, wanting, needing.

Just wondering...
[Nexus 4 Android Development] XenderX666:
Work with PAC rom on 4.3 ?:eek:
[Nexus 4 Android Development] philosophics:
No, hints the question
[Nexus 4 Android Development] ernestnwanu:
204 is coming this weekend, I hope this isn't dead yet..
[Nexus 4 Android Development] krjadejesus:
What has happened with this thread?
[Nexus 4 Android Development] Luigiesin:
No idea... Hopefully the developer would be back when 204 is out... I really like this kernel version of Franco.
[Nexus 4 Android Development] Crostantin:
Dev is waiting that franco solves the problems on the 203...201 is much more better

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] gharrrrrr:
I sure hope so. This kernel is by far my favorite for my N4. Franco did announce on G+ a 204 release for N4 soon.

Sent from my Hammerhead using my TARDIS.
[Nexus 4 Android Development] philosophics:
Let the compiling BEGIN!

So excited for this release!
[Nexus 4 Android Development] Luigiesin:
1+
[Nexus 4 Android Development] xcstacy:
Working on it
[Nexus 4 Android Development] desiromeo719:
Awesome! Thought this thread had died for a sec.. Can't wait :)
[Nexus 4 Android Development] Luigiesin:
Great! Thanks man!
[Nexus 4 Android Development] xcstacy:
I'm testing it now. :)
[Nexus 4 Android Development] Crostantin:
c mon!!!!! waiting for it!!!!
[Nexus 4 Android Development] desiromeo719:
lol

people are gonna start turning on xstacy like they did on franco if you take too long to supply our needs! :)
[Nexus 4 Android Development] Luigiesin:
Hahahahaha! Can't blame them! This version of Franco rocks!
[Nexus 4 Android Development] philosophics:
Haha. Let's not do that again, please.

As we all know, these things take time. Sometimes, it takes longer.

The actual 204 as is, amazing. Play with that one until this one comes out, none will be disappointed. The only thing I'm missing atm is faux sound but I'm sure I'll be reminded of other goodies once I'm able to flash the saber release...
[Nexus 4 Android Development] Luigiesin:
I'm missing Faux and supercharger... The only reason why I haven't used the regular build ;)
[Nexus 4 Android Development] philosophics:
Supercharger?
[Nexus 4 Android Development] Luigiesin:
Yes... This kernel brings supercharger... Which allows the battery to charge twice as fast!
[Nexus 4 Android Development] philosophics:
Oh, that supercharger. I thought you were referring to the supercharger script you run in terminal that changes your OOM to vrOOM and Makes your launcher die hard.
[Nexus 4 Android Development] desiromeo719:
I just need faux sound to fix the camcorder mic gain issue with our phones. All else is just a plus. Think I will try out regular 204 till this gets released.
[Nexus 4 Android Development] xcstacy:
Alright guys, here's r204.

AOSP | CM

I started all over again from scratch and implemented most of the previous patches. New notable patches include:

- Prima 3.2.7.47 from CAF

- F2FS support

- Latest sched-dl from Linux mainline

Enjoy! :)

Edit: Oh yes, one more thing. Please remember to flash ak_uninstaller_mako.zip made by [MENTION=3685904]ak[/MENTION] before flashing another kernel or else your wifi will not work.
[Nexus 4 Android Development] philosophics:
So far, this kernel is working great! No problems at all yet. Device is more responsive over Franco standard, and that's saying something considering how fast the device was already...
[Nexus 4 Android Development] TheDarkDefender:
[MENTION=4888112]xcstacy[/MENTION] the cm version is working great with Liquid smooth. Thanks a lot for this.
[Nexus 4 Android Development] mixtapes08:
Anyone tried this on touch control?

Sent from my Nexus⁴
[Nexus 4 Android Development] xcstacy:
If you're referring to bponury touch control, then I'm very sorry to tell you that it won't work. The author himself said that he will not support custom toolchains.
[Nexus 4 Android Development] mixtapes08:
Oh it's ok dude... Thanks and morepower to you. :)

Sent from my Nexus⁴
[Nexus 4 Android Development] desiromeo719:
Anybody else having severe problems with link speed and download speeds with the prima drivers? My throughput has gone down from 150mbps to 65mbps. Download speed has gone down from 50-60mbps to 10mbps. Is there any way to make the kernel without the prima drivers?!
[Nexus 4 Android Development] Luigiesin:
Hey guys... Isn't 204 supposed to run on 3 cores by default? That's how regular Franco is running... But not this version.
[Nexus 4 Android Development] philosophics:
I don't know, my settings rolled over from the standard version so I'm still running 4 cores at all time
[Nexus 4 Android Development] xcstacy:
Need more inputs to confirm this. My internet speed has been horribly slow ever since I came to Sweden so I can't really tell if the speed has gone down.
[Nexus 4 Android Development] xcstacy:
I thought its always been the standard 2 cores screen on?
[Nexus 4 Android Development] philosophics:
I have noticed it as well. At first, I thought it was because of my defective router but that has been fixed. My phone is still slow. Transitioning back to standard Franco, speeds did increase from this kernel. I am using the latest hybrid radio so to have LTE but that doesn't seem to be the issue...

---------- Post added at 12:21 AM ---------- Previous post was at 12:19 AM ----------

When I say roll over, I neglected to mention the settings I speak of are the custom settings provided by ginger and Stormtrooper
[Nexus 4 Android Development] Luigiesin:
Franco made 3 cores default this time... Just confirmed with a few more users... It's working fine though... How can we make it go 3 cores online?
[Nexus 4 Android Development] xcstacy:
That's odd. I haven't experienced any severe drop in my internet speed (but then again its too slow to begin with). Maybe I can try building the kernel with older Prima drivers when I'm free and see if there's any difference in speed.

Yup got it. I was actually referring to [MENTION=2750179]Luigiesin[/MENTION] post.
[Nexus 4 Android Development] desiromeo719:
That's would be great! I think there isn't much need for prima drivers anymore since the wifi drivers have been fixed for a while now on our phones and with stock Franco I get full throughout and download speeds.

---------- Post added at 04:23 PM ---------- Previous post was at 04:21 PM ----------

That's interesting I haven't heard of this. It didn't say anything about 3 cores in the change log...