yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Original Android Development] Bobtehblob:
CM aren't even building off AOSP sources any more. They're using qualcomms CAF branch now which is the reason for incompatibilities between AOSP based kernels like Franco's .

---------- Post added at 03:43 AM ---------- Previous post was at 03:38 AM ----------

Also Franco if this is true is there anything that you/us have to look forward to from it? Or just the standard performance improvements. I know absolutely nothing about Linux kernels :D

http://www.androidpolice.com/2013/1...id-will-be-updated-to-the-v3-10-linux-kernel/

---------- Post added at 03:45 AM ---------- Previous post was at 03:43 AM ----------

Also Franco if this is true is there anything that you/us have to look forward to from it? Or just the standard performance improvements. I know absolutely nothing about Linux kernels :D

http://www.androidpolice.com/2013/1...id-will-be-updated-to-the-v3-10-linux-kernel/
[Nexus 4 Original Android Development] franciscofranco:
I hear you should fix it.

Seriously, because CM commits will brake stock. Stock > everything else.
[Nexus 4 Original Android Development] franciscofranco:
You can read my post: https://plus.google.com/106873500108976028532/posts/1AivLpAjWqS that I wrote yesterday.
[Nexus 4 Original Android Development] SeemannBootlegs:
Hi Franco

I was using your kernel with MarcLandi's AOKP 2013-10-22 nightly and everything was smooth an nice. I really like have color and double tap features but since I update to 2013-10-25 nightly this fc don't stop to appear.

Do you know if this is a ROM related or an incompatibility with your kernel?

Thanks in advance!

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] ziddey:
Ramdisk issue. There's an addition to BOOTCLASSPATH in init.rc

Sent from my phone. Please forgive typos and brevity.
[Nexus 4 Original Android Development] franciscofranco:
Rom added CM stuff then it breaks because there is a .jar file that is not on my ramdisk path.

Is there any rom out there that does anything original without copying CM? I know PA does.
[Nexus 4 Original Android Development] LimitsX:
I'm on r28 now with MinCo v6 rom. Did a full clean wipe and installed new r28.

One issue i noticed is that my wifi signal bar doesn't go above 2 bars. It its just stuck there, and its been an hour of usage on it. No random fluctuation though compared to r27.

Battery seem great. Other than the two wifi bar, everything looks great! Maybe I should do something else?

I have location access off, NFC off.
[Nexus 4 Original Android Development] benrees21:
Oh yeah!! Love it.

A Nexus b!tch called Ben (Work that one out :P) AOSPA!!!
[Nexus 4 Original Android Development] joshnichols189:
That's your phone reacting to something with NFC.
[Nexus 4 Original Android Development] scream4cheese:
So far so good! I was running this on r27 last night and then flashed r28 early this morning. I love idle/sleep time on this kernel! It's a major improvement from all the rest. I decided to just use franco's default setting btw.
[Nexus 4 Original Android Development] jark99:
Off topic a bit, but what are people using to tweak kernel settings? I remember on the Nexus a, I used nstools to tweak voltages and frequencies, right now running everything stock and it's soo smooth! Good to see you back franco

Sent from Nexus 4
[Nexus 4 Original Android Development] ceejay83:
Franco's app
[Nexus 4 Original Android Development] resynx:
Franco's app
[Nexus 4 Original Android Development] nellisere:
Can anyone help me with these wake locks? Its stopping my phone going into deep sleep

(Using r28 and CyanogenMod 10.1 latest nightly)
[Nexus 4 Original Android Development] iGoogleNexus:
O.o why does your notification look faded?

#Team MiNCO

**G1→N1→NS→GN→N⁴**
[Nexus 4 Original Android Development] jarjar124:
Paranoid android is like that apparently
[Nexus 4 Original Android Development] mobilehavoc:
Let me if you figure this out. I have no clue either and its bothering me.
[Nexus 4 Original Android Development] franciscofranco:
Try to reproduce those wakelocks in stock rom.
[Nexus 4 Original Android Development] CMNein:
Same set up here but I don't have those wake locks. Do you have a texting widget or alike?
[Nexus 4 Original Android Development] nellisere:
Nope, the only texting widget is that one that comes stock with CM, I wonder if that is causing it?
[Nexus 4 Original Android Development] franciscofranco:
Maybe maybe not. Try to reproduce the wakelocks with stock rom and you'll know whats the culprit.
[Nexus 4 Original Android Development] nellisere:
Probably won't be able to reflash due to internet woes until Tuesday, it's not really causing a massive drain, still get's me through the day without a problem so I should be fine till then.
[Nexus 4 Original Android Development] daviiiiiid:
My first full day with my N4 with the settings in sig!

Looks so far so good with my heavy usage and still a new battery..
[Nexus 4 Original Android Development] scream4cheese:
Ohmygoodness! You got the Nexus 10! :D
[Nexus 4 Original Android Development] mobilehavoc:
I'm on stock unrooted rom with only your kernel. So they happen on stock rom. I believe its app related but can't figure out. My Nexus 7 has exact same apps as N4 and don't ever have these wake locks so something specific to N4 or kernel.
[Nexus 4 Original Android Development] nellisere:
I currently have these apps: BetterBatteryStats, Chrome, Draw Something, Dropbox, Facebook, Gifboom, iFixit, Instagram, Lockscreen Policy, MemoWidget, Facebook Messenger, NatWest, Skype, SongPop, Speedtest, Trainline, TricksterMod, Tumblr, Twitter, Unified Remote Full, WhatsApp, Words with Friends, and XDA. Which ones do you have the same, then maybe we can narrow it down quicker? (If it is an App)
[Nexus 4 Original Android Development] SeemannBootlegs:
Thanks Franco for your answer

I know they added some stuff from CM and recently I know you hate CM hehehe

Thanks buddy.

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] franciscofranco:
I don't hate CM - I hate what they do with the project most of the times - its different.
[Nexus 4 Original Android Development] SeemannBootlegs:
I was joking :P but I understand you Bro that's why I don't use CM anymore but since I cannot make a ROM for myself I just seek which ROM fits my needs

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] ben_pyett:
[MENTION=470754] franciscofranco [/MENTION]

Just to play devils advocate for a second, what are the negative implications of adding the CM path lines that have been recently added, would they adversely effect the performance or function of a stock rom? As an aokp user, as the user above explained, they along with a frightening number of other roms clearly use a significantly large amount of CM in their base and therefore suffer from the current phone FC issue, thankfully AOKP gave their users the right to choose in the recent CAF kernel disaster.

Any chance you add the lines? I reckon between a third and a half of your users would be even more gratefu (a figure I've plucked from thin air). I understand that you shouldn't have to change, but whats the harm to incorporate these additions?

I need a new kernel and Rom to flash in order to distract me from the non event that is Google nexus 5 launch
[Nexus 4 Original Android Development] Mercado_Negro:
SlimBean is CM free for Mako.
[Nexus 4 Original Android Development] pkelly517:
I'd suggest that most of the ROM dev teams track a good portion of CM, just because the smaller dev teams can't devote full time to a lot of the lower level stuff. For a long, long time, it's worked. I'd guess that there will be a lot of second guessing in the coming months.

Since the CM crowd has gone commercial, I suspect that the changes they are doing are geared to break this dependency. They don't want ROMs to track their changes, since it breaks AOSP compatibility. CM or someone else. Then they can go their merry way on the path towards cash. The CM folks are trying to make money. The rest of the world just wants to make cool ROM. And the cool ROM guys aren't paying for the CM tracking. Let's screw them.

It started with the CAF kernel commits. Then there were telephony breakages in AOKP (fixed within a day). Some new stuff makes franco incompatible with the daily build.

It looks like the bottom line is that ROM builders are going to have to track SO much more just keep a ROM that's even half-assed updated.

What I would suspect is that there will be another group that shows up just to track the stuff that CM used to track. I have no idea how much effort that would require, but I would guess that it's do-able between ALL of the ongoing ROM devs.

edit: I got a response from AOKP dev Marc Landis about the latest incompatibility. I will assume that this will be an issue going forward for all non-CM ROMs.

Is this a fix that's easy to make (on a general level), or is it on the JWR/JSS level of crap?

Anyhow, tl;dr

ROMs will likely move away from CM tracking.
[Nexus 4 Original Android Development] AlphaDivxMovies:
Hi, I suppose you are using Franco`s Kernel...duh...those music glitches you mention are probably related to a battery saving / heat reducing feature of the kernel. When the screen goes off the maximum clock speed available to the system gets reduced to around 800 Mhz if I am not mistaken thus making song apps and cpu intensive DSP struggle at such low clock speeds. This is a good feature but since we are listening to music and the screen is off apps get that little cpu power. When using intensive apps like Powerplay or DSP`s like Viper Audio or Eizo it falls short. Even hearing music in a stereo bluetooth sucks because of the intensive cpu needs I reckon. It all depends on what you use or how you use it. Try increasing the value to around 1200Mhz or whatever works. You can do this easily using Franco`s app or the hard way using terminal ( I have no idea so ask around). Or just leave the screen on all the time. I solved my bluetooth woes with DSP with this. Good luck.
[Nexus 4 Original Android Development] corwest:
What are you doing when it stutters? What ROM are you using? What is your CPU state when it stutters? Do you under volt? What app? Common buddy this is ridiculous.
[Nexus 4 Original Android Development] winner00:
PA doesn't need to track CM because they only support Nexus's. Pretty much every other rom that supports more devices than just nexus's needs to track CM stuff. Other roms track CM stuff mainly for all the device stuff such as telephony.
[Nexus 4 Original Android Development] ernani1:
that omni rom is working fine with JSS kernel. Almost 48hs using this and no deadlocks yet since i moved from carbon to omni unnoficial daily builds
[Nexus 4 Original Android Development] Testraindrop:
+1 I just hope they speed up things, I finally want that "official" string in my phone :D

Gesendet von meinem Nexus 4
[Nexus 4 Original Android Development] ernani1:
Better to leave carbon instead of leaving franco kernel...
[Nexus 4 Original Android Development] crawfordmd:
Ez aww added tXZzea za Aww z zzz
[Nexus 4 Original Android Development] jmudrick:
As an occasional user of reborn90's Franco+ kernel I don't think tracking other people's recoding of the kernel needs to be on Franco's priority list, the boy has plenty of other more important things to do like improving his own kernel and app. Try them out if you want, as I do, but I think two official Franco kernels for the N4 is one more than enough.
[Nexus 4 Original Android Development] Viper4713:
On any phone even the Nexus 4, the Official "Stable" CM was so buggy for me, to the point even the Compass wasn't working, as if there was no driver for the compass installed, on Nexus 4 System Settings would not save unless I rebooted phone, I flashed the correct Gapps and full wipe every time, I have tried CM multiple times sense CM7 to CM10.1 and its always been this way, I have tried Carbon Rom, its good and stable but recently I switched to PA, and wow everything works, I don't believe I even found a bug yet.

So for me I do not like CM at all.
[Nexus 4 Original Android Development] jtwlbz:
I bought a franco kernel app and now I can't use it.. cuz I am using cm based rom.
[Nexus 4 Original Android Development] corwest:
Unfortunate indeed.
[Nexus 4 Original Android Development] arlenwoot:
Checkout http://xdaforums.com/showthread.php?p=46817401 might work with your rom. Only thing different between it and regular franco.Kernel is the commits needed to work with CM based roms.
[Nexus 4 Original Android Development] Mercado_Negro:
Gents, there are other ROMs out there without all that CM drama like Cataclysm, SlimBean, etc. I really can't believe you can't find something you're not pleased with. I know, it's a sad situation but sometimes we should be part of the solution, not the problem. I really like AOKP but I can't really put up with all this and I need a working phone with some features that aren't included on stock so I looked around and found something that suited me. I'm pretty sure you can do the same and keep using your favorite kernel. In this case I was lucky because the ROM I chose has a great kernel and also supports other JWR kernels which means no deadlocks.

We're always going to miss something but that doesn't mean we can't get 90% there using a different approach.
[Nexus 4 Original Android Development] theclaytons:
I use stock and xposed framework with gravity box. Has all the features I ever used from CM and I love it.
[Nexus 4 Original Android Development] Mercado_Negro:
There you go, problem solved :thumbup:
[Nexus 4 Original Android Development] sordna:
Umm you misunderstood. All I'm suggesting Franco could do, is add a link: if you want this kernel on CM, go to this thread where some other guys are doing it. I didn't propose for a second that Franco tracks anything or does any ongoing extra work. I want him offloaded from having to even answer questions related to CM !
[Nexus 4 Original Android Development] 777.300:
Good advice.

I use ParanoidAndroid on my Nexus 4 now for a couple of weeks. I totally don't miss CM.

PA is great in combination with the Franco kernel.

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] budapestkave:
Guys, I use CM only because of the customisable power widgets in the notification bar, and I'd line to use Franco's kernel.

Is there a way to download the last compatible CM version, or is there another ROM with similar functionality?
[Nexus 4 Original Android Development] ziddey:
You could check out Widgetsoid
[Nexus 4 Original Android Development] SpasilliumNexus:
CarbonROM
[Nexus 4 Original Android Development] Pipusz:
Power Toggles.
[Nexus 4 Original Android Development] pitjago74:
Me too.....and franco 191jwr and not problem at all

Enviado desde mi Nexus 4 mediante Tapatalk
[Nexus 4 Original Android Development] budapestkave:
I gave a try to this one but after installing Franco's kernel my phone constantly says com.android.phone has stopped. Any ideas on this?
[Nexus 4 Original Android Development] zorginho:
It's because a file missing in Franco's ramdisk, carbon added a commit from cm.

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Original Android Development] Mercado_Negro:
You can't use a kernel with a modified ramdisk on CarbonROM, i.e., the original franco.Kernel won't work, you need a modified version.
[Nexus 4 Original Android Development] rushi1607:
Which Rom is [MENTION=3292224]franciscofranco[/MENTION] using ?
[Nexus 4 Original Android Development] jarjar124:
Stock
[Nexus 4 Original Android Development] Savant:
I'm so sorry that your mad because you're supporting a developer.
[Nexus 4 Original Android Development] zephiK:
You are aware that the latest nightly of Carbon is broken with Franco because of the modified ram disk because they included phone and camera cm commit right? So your suggestion isn't really helping.
[Nexus 4 Original Android Development] cgulliver:
SlimBean has toggles as well. Running great for me with FK. Nothing against CM but not missing it at all. SB has been exceptional.
[Nexus 4 Original Android Development] franciscofranco:
Guess I'll release an update to fix the ramdisk with Carbon and PAC - Google sure taking its time to release 4.4. I'll take care of that later today.
[Nexus 4 Original Android Development] jtwlbz:
Good news
[Nexus 4 Original Android Development] budapestkave:
Which nightly works with franco's kernel?
[Nexus 4 Original Android Development] corwest:
Thank you franco. Hopefully this can save some pages of people complaining about FC's in CM based roms with your kernel. (Ha! Who am I kidding, the posts will still come...)
[Nexus 4 Original Android Development] SpasilliumNexus:
Well I wasn't aware of that since I switched back to PA + FK from Carbon + FK before they made those changes. Thanks for trying to help by actually giving him another suggestion... oh wait... :rolleyes:
[Nexus 4 Original Android Development] ben_pyett:
Apologies [MENTION=3292224]franciscofranco[/MENTION], but to cut down on complaints until you get the chance to rebuild, for the impatient (who are on a CM based ROM, ie CM AOKP, Carbon, PAC etc), there is a link below and in my sig, to a rebuilt version of Franco 191 JWR with the updated init.rc (so no phone FC) which runs fine on latest AOKP no issues. thanks to [MENTION=702102]LaboDJ[/MENTION] [MENTION=1006034]rickroll[/MENTION] and [MENTION=584916]ziddey[/MENTION]

http://xdaforums.com/showpost.php?p=46825530&postcount=10473

Details of commits have come from http://xdaforums.com/showpost.php?p=46748007&postcount=51

[MENTION=3292224]franciscofranco[/MENTION], if you'd like me to remove the link just say...

off topic, whose watching El Classico....?
[Nexus 4 Original Android Development] ziddey:
Perhaps, an extension to the popular "anykernel" approach would be best in the long run in terms of minimizing work and maximizing support. I don't have much time at the moment, but got some of the changes down:

fstab.mako:
s/,barrier=1//g
/persist/!s/ordered/writeback/g

init.mako.rc:
/vibrator/s/70/100/g
/service mpdecision/,+1 s/^/#/g
/service thermald/,+1 s/^/#/g
/dev\/socket\/mpdecision/ s/^/#/g

APPEND:
service fkbootscript /sbin/fkbootscript.sh
class main
oneshot

on property:sys.boot_completed=1
write /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor "interactive"
write /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor "interactive"
write /sys/devices/system/cpu/cpu2/cpufreq/scaling_governor "interactive"
write /sys/devices/system/cpu/cpu3/cpufreq/scaling_governor "interactive"

init.rc:
/sys\/devices/s/0660/0664/g (now also init.cm.rc)
s/\(randomize_va_space \)./\10/g

APPEND:
# Execute files in /system/etc/init.d before booting
service run-parts /sbin/bb/busybox run-parts /system/etc/init.d
class main

It's missing a few parts-- tweaks (dirty_writeback_centisecs/dirty_ratio/swappiness), busybox, fkbootscript.sh, and setting/deleting (initial) power modes.

I'm mostly comparing against an early 10.2 ramdisk and a recent one, but see that there could be issues trying to use a sed substitution universally. So, it may be a better idea to simply append some of the changes instead of replace. That way, whatever was originally set would simply be updated.

One thing I noticed with recent CM ramdisks is that some of the governor related lines are moved from init.mako.rc to init.cm.rc. That and there seems to be some extra/duplicate commands here and there. Messy.
[Nexus 4 Original Android Development] theclaytons:
Just use the quick toggles and add buttons in there. Power widgets is old and when you use quick toggles you will wonder why you liked power widgets.
[Nexus 4 Original Android Development] 777.300:
Your completely right. Quick toggles is the way to go.

Sent from my Nexus 4 with Tapatalk 4
[Nexus 4 Original Android Development] arlenwoot:
Checkout http://xdaforums.com/showthread.php?p=46822695 It's franco.Kernel compiled with the two commits needed to work with CM. Nothing else changed.
[Nexus 4 Original Android Development] ssbnasa:
That is some awesome battery!

And version u using anyways?! :P
[Nexus 4 Original Android Development] franciscofranco:
I don't want to use AnyKernel, I prefer the boot.img approach.
[Nexus 4 Original Android Development] franciscofranco:
Does anyone know which .jar file I need to add on the classpath for Carbon compatibility? Thanks.
[Nexus 4 Original Android Development] ben_pyett:
I believe that the second link in my post above, might have the detail your after, although I'm not 100%
[Nexus 4 Original Android Development] Mercado_Negro:
Here:
[Nexus 4 Original Android Development] namurt:
telephony-msim.jar

source: https://plus.google.com/106513914946845471488/posts/evdxYtAR5Ps (read the second to last comment, which is from daniel mm, a member of the carbon team)

edit: FREAKIN' NINJA'D! :p
[Nexus 4 Original Android Development] UgoBoss:
Thank's Franco for adding the classpath for Carbon Rom compatibility ! Awesome ! :D
[Nexus 4 Original Android Development] sordna:
You mean Power Toggles?
[Nexus 4 Original Android Development] franciscofranco:
Thanks guys.

Can someone on PAC or Carbon test the attached please.

EDIT: removed attachment, I forgot that was for JWR and not JSS.
[Nexus 4 Original Android Development] nexusmaniac:
Will this also work on non PAC or Carbon ROM's?
[Nexus 4 Original Android Development] franciscofranco:
Yes... I just want to know if it boots on those two before I can release.
[Nexus 4 Original Android Development] nexusmaniac:
Thought it would, just checking :)
[Nexus 4 Original Android Development] winner00:
Works fine. Also Carbon is JWR.
[Nexus 4 Original Android Development] franciscofranco:
Ok, great.
[Nexus 4 Original Android Development] ben_pyett:
As is AOKP
[Nexus 4 Original Android Development] franciscofranco:
Good. Just cleaning up some code and I'll push final r193.
[Nexus 4 Original Android Development] franciscofranco:
r193:

* Improve gaming experience by enhancing how the Hotplug driver reacts to sustained high GPU load - tests showed a 2-3 fps increase in the tested games

* Clean code from the Hotplug driver to make it prettieeee

* Compatible with the latest PAC and Carbon rom nightlies

This is the last release to be hosted on the current servers - I got hold of a very powerful VPS machine that will be used in the next FKU and in all downloads through XDA topics and I'm sure there won't be any more bandwidth bottlenecks. Wasn't ready today for deployment so instead of rushing things I decided to still use the current servers one last time. The new machine is a 8 core, 16gb ram, 160gb ssd, 1 gigabit line with Ubuntu 12.04, Kernel 3.11 running Apache2. From my tests that should be more than enough to take care of peak times.
[Nexus 4 Original Android Development] vladm7:
Get rid of Apache in favor of Nginx or similar. Is that all for hosting downloads or something else will be running there?
[Nexus 4 Original Android Development] franciscofranco:
It will have the same use that current servers do. I'll run with Apache2 for a while to see how it goes, I can always delete the Droplet and create a new one in a few minutes without any biggie. What are the advantages with using Nginx?
[Nexus 4 Original Android Development] iGoogleNexus:
O.o my colors look beautiful When flashing 193... Or is it me?

Btw Franco... Thank you for sticking with Nexus... Love this phone even more with your Kernel <3 lol
[Nexus 4 Original Android Development] vladm7:
nginx is event-based threading server capable of handling thousands of simultaneous connections on a modest server. Small memory footprint. Mostly used to serve static content or as a front-end proxy for various web-apps (via fastcgi, *sgi and http proxying).

http://www.wikivs.com/wiki/Apache_vs_nginx
[Nexus 4 Original Android Development] franciscofranco:
Well, should I care with the powerful machine that I have? I mean, how can I starve 16gb of ram and 8 logical cores I think running between 3,5GHz and 4GHz on each core?