yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
Figured it out guys, Francisco must have enabled ASRAM manually on compile for r392 because it's not enabled in the config files by default on the git. I'm making the changes now and I'll get him to push a new build. :good:
[Samsung Galaxy Nexus] sd3993:
Hopefully the new build will work with cm11 too? :)
[Samsung Galaxy Nexus] osm0sis:
It's a JB kernel, so no. But, as I already said, I will join it with a working KitKat ramdisk as I have already done for r392.
[Samsung Galaxy Nexus] sd3993:
Yes that is what i meant actually. Will u be releasing them together or seperately? not asking for ETAs lol :p
[Samsung Galaxy Nexus] metalspring:
May I suggest using a cm ramdisk? Other ramdisks seem to cause issues with cm, but cm ramdisks still seem to work just fine on other roms
[Samsung Galaxy Nexus] osm0sis:
I was using SlimKat's which was based on both AOSP's and CM's, but yup, for the new one I'll be grabbing the latest CM11, then comparing to SlimKat and merging anything necessary, then adding the f.K optimizations.

Bad news though, franco DID enable ASRAM under his franco_defconfig, so there's no reason it shouldn't be working after all. So I'm stumped again and I've got to email him about it. I went ahead and made row the default iosched for the next build too.

I was going to fix the KK ramdisk up tonight, but we'll see, I'm getting tired.
[Samsung Galaxy Nexus] sd3993:
No hurry mate. Take your time! :)
[Samsung Galaxy Nexus] osm0sis:
Cheers, yeah I just worked my second 12h day shift in a row at the hospital (I'm a RN), so I think I'll put the ramdisk off until tomorrow afternoon before I head in for my first of two 12h night shifts this weekend. ;)

I'm emailing Francisco about the bugs right now so that's the important stuff out of the way. :good:

Edit: Oh man, clearly I AM tired. When I said franco had enabled it, I was looking at the file from after me enabling it, so hopefully my fixes do the trick. :p
[Samsung Galaxy Nexus] sd3993:
Oh lol :P

Yes you do need some rest :P

One lust bug. I was unable to change the value of the target_load to 85 in the 'interactive' governor. Everytime i changed it's value it would just revert back to zero :P
[Samsung Galaxy Nexus] osm0sis:
Works fine here on r394. 85 is the default and I had no problem setting it to 75, verified using a file explorer. Maybe an issue in CM11's ramdisk that you're using... ;)

Oh and by the way, the logcat warning spam I'm seeing was in r392 as well, but I've still asked Francisco to look into it when he can.
[Samsung Galaxy Nexus] sd3993:
Yeah it is an issue in CM11's ramdisk not franco's. But you said you would be merging changes from franco's ramdisk to cm11's...so i thought i should make you aware of this issue since I don't really know how things work in the ramdisk porting world :P
[Samsung Galaxy Nexus] mangusZen:
OT for [MENTION=1143630]osmosis[/MENTION].. What is a RN? I work in hospital too, Im a radiotherapy technician
[Samsung Galaxy Nexus] Edward Stanbury:
registered nurse ?
[Samsung Galaxy Nexus] mangusZen:
yes, I didn't get what 'R' stand for :D
[Samsung Galaxy Nexus] Edward Stanbury:
Haha all good :)
[Samsung Galaxy Nexus] thegtfusion:
i am back here for a week i think, my n5 had a bad cpu XD, they put a cpu revision 1 in my phone, which caused sod and reboots on stock! (unrooted, locked bootloader)

time to flash r394 :D
[Samsung Galaxy Nexus] pkgnex:
Thanks for everything you do to keep franco.kernel running and relevant for us lowly G-Nexers, Os!

I'll be looking forward to an os-fixed r395 (?) with ASRAM back and a ramdisk that is compatible with 4.4!

On a separate note, I see the F.Ku app was updated again today. I didn't take the last update because core and IVA voltage editing (or somethng similar) was left out... can anyone confirm that the 11/29 update version has all the old functionality back?
[Samsung Galaxy Nexus] Mr Black'd:
I have Rom XenonHD and I had successfully installed v392 when I decided to test v394 which gave me bootloops.

I decided to flash again v392 but bootloops still exist. Any ideas?
[Samsung Galaxy Nexus] dracon6ai:
Dirty flash XenonHD again followed by v392. Should be good to go afterwards. Your Ram Disk just got screwy.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] Mr Black'd:
thanks for the advice I ll keep in mind, I currently restored to a few days older cwm backup since I have little time to waste and the device is operating again. however I think that at some point I dirty flashed the rom and gapps but the bootloop still existed...
[Samsung Galaxy Nexus] luckana:
Guys this is my first encounter with gnex kernels and rooting etc. (i had another android device before) I did everything and installed franco kernel but when i set the max freq of the processor to 1.8ghz I am experiencing random shutdowns. It's because of the high freq right ? It doesn't occur on lower ones
[Samsung Galaxy Nexus] agayabag:
there you go, you have answered your own question. for me, i don't really need no OC because 1.2 or even 1.0 ghz is enough for me. you feel me, bro?
[Samsung Galaxy Nexus] Ashtrix:
The overclocking requires a bit of hardware knowledge prior to that all SoC's aren't made equal, mine runs at a 1.5Ghz full stable and i can OC upto 1.8 but that would only drain my phone plus make sure to read

this

for all Nexus Prime's SR and OC/UV capabilities ;) !!
[Samsung Galaxy Nexus] thegtfusion:
[MENTION=4544860]osm0sis[/MENTION], do you use 4.4?so yes, which rom? thanks :D
[Samsung Galaxy Nexus] osm0sis:
Nah, not in the mood for instability at the moment, so I'm still rocking 4.3, but with KitKat APKs, launcher, sounds and bootanimation, plus GravityBox to make up the difference and have it look roughly like 4.4. :cool:
[Samsung Galaxy Nexus] thegtfusion:
ahaa nice :)

its been a day since my n5 has been sent back, hard to live with gnex now :P, but r394 speeded my gnex up a little :)
[Samsung Galaxy Nexus] wisefreakz:
Kitkang is pretty much stable... I still have my 3 hours screen on.... No lags... Worth a try.
[Samsung Galaxy Nexus] inihccor:
Can I use r394 with cm10.2?

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] McDuffSmith:
Franco Kernel r394 4.4 version on CM11 unofficial gets me in a bootloop.

any fixes?

is this kernel or ROM side?

Franco's change log said it would work with CM now.

kind of a bummer :(
[Samsung Galaxy Nexus] wisefreakz:
Kernel... Incompatible ramdisk. Its about to be fixed by Osmosis/Franco
[Samsung Galaxy Nexus] bchaney16:
r394 works with PAC ROM 12/1 nightly. Thanks!
[Samsung Galaxy Nexus] PCWright86:
Is the PAC 12/1 nightly 4.3 or 4.4. I run nothing but Franco and don't want to drop back to 4.3. Spoiled by KitKat I guess
[Samsung Galaxy Nexus] metalspring:
Pac is all still 4.3
[Samsung Galaxy Nexus] Flammable:
r394 bootlooping on slimkat 1.6
[Samsung Galaxy Nexus] sd3993:
I think what he meant was that the r392 build wasn't compatible with CM/PAC's custom frameworks. But r394 is. Although not on KitKat.
[Samsung Galaxy Nexus] thegtfusion:
In the OP is written : 4.3/4.4 so it should work on 4.4. But the people say different, weird
[Samsung Galaxy Nexus] Madsunable:
I'm on the latest franco r394. And when I select the bfq sheduler my device crashed into a reboot.

Gesendet von meinem Galaxy Nexus mit Tapatalk
[Samsung Galaxy Nexus] vitalero:
How stable is this r394 for a 4.3 ROM ?

as of 12pages i read that some stuff missing including some extra RAM ?
[Samsung Galaxy Nexus] Vekhez:
Really good. Battery life could be better but it could be on all kernels really. I totally recommend FK or ASKP.
[Samsung Galaxy Nexus] vitalero:
Yes i am using franco already but just wanted to make sure for this latest version update as i notice 10 pages + talking about issues with it
[Samsung Galaxy Nexus] osm0sis:
ASRAM (an extra 50mb of RAM above what stock kernel has) was left disabled somehow but I think I have already fixed it for the next build and Francisco has said he will have it working in the case that I haven't. Francisco was mistaken in saying r394 works in KK4.4 - that would require a different ramdisk - but I have sent him my updated KK4.4 ramdisk with all the f.K optimizations and he has said that he will be putting up images of both versions officially for the next build. To answer your question though, it is completely stable for me and still really fast, even without ASRAM. :) :good:

Been running various versions (testing and final) of r394 for the last 3 days with bfq set on boot and zero issues. :confused:
[Samsung Galaxy Nexus] sd3993:
Alright i know...no ETAs.....but i can't hold it in this time :p

Any idea on when he's gonna upload them? And if you have test versions could you PM them to me for testing. The more the better :D

I promise not to leak them ;)
[Samsung Galaxy Nexus] Firnagzen:
Hmm... Just idle curiosity here.

Who's actually developing Franco kernel, anyway?

As I understand it, Francisco started it, but it seems like osm0sis is doing the optimization, and now, continuing the development? And Francisco said he's more or less finished with the kernel, but there's still little problems here and there (such as the current RAMdisk issue)?
[Samsung Galaxy Nexus] metalspring:
They both do their part... Franco is busy with newer devices so he doesnt have a lot of time for us gnex users now, so osm0sis helps out so we can keep getting updates :)
[Samsung Galaxy Nexus] osm0sis:
The only test versions were: a) r394 but 3.0.91 and with the old broken ramdisk. b) r394 but 3.0.91 with the fixed ramdisk. c) release version of r394 on 3.0.101 like an hour earlier than everyone else to give it another once-over. :p

None really worth playing with at this point - none had ASRAM working. Clearly my once-over shouldn't have been in the middle of a 12 hour nightshift, at work. ;)

I've been fixing the ramdisk lately and supplied a couple of cherry-picks and minor patch commits but Francisco remains the developer and only genius at work on franco.Kernel. The GN kernel will still be updated with fixes/interesting picks from other repos for awhile longer, when possible or required.
[Samsung Galaxy Nexus] thesebastian:
Well after 2 weeks with CM11 and dhacker's kernel i decided to go back to stock 4.3 (with Google experience launcher apk manually installed)...

In my opinion at the moment 4.3 is smoother than 4.4.

CM11 is 100% stable, excellent performance but isn't really smooth for a Nexus device...(Specially when pressing HOME / RECENT APPS and sometimes when scrolling really hard, is fast, but not smooth).

I really like 4.4 AOSP apps, but i'm going to wait a little more before upgrade again.
[Samsung Galaxy Nexus] osm0sis:
You can grab Clock and Email from my Dev-Host:

http://v.ht/osm0sis -- http://d-h.st/users/osm0sis/krt16s-kk4_4-apk/ :D

Plus bootanimation and sounds. :p
[Samsung Galaxy Nexus] TiagoRigueto:
have a osmosis mod??

my usb tethering work but....very bad... 1min ok, 10min not work, 1min work, 10 min not work... =/
[Samsung Galaxy Nexus] metalspring:
If I may make a suggestion, you might want to give my build a quick try and see then, you might see the full smoothness of kitkat in full action ;)

not to mention cm is starting to bring all the fun custom settings back, plus lots of bug fixes, etc.
[Samsung Galaxy Nexus] sd3993:
lol :P

Oh and i was asking for a r394 with ASRAM and 4.4 Ramdisk with the f.K optimizations as a test build as i incorrectly thought that you might already have them for testing before Franco releases them to the public :P

Anyways if you're looking for people to test them once those are made, count me in ;)
[Samsung Galaxy Nexus] osm0sis:
Whoa, just saw this! That's awesome buddy! The legendary [MENTION=2961824]joaquinf[/MENTION] from f.K tuna/Franco's Dev Team glory days works in a hospital too, though I think he was more on the biotech side. Health care professionals unite! :D
[Samsung Galaxy Nexus] bigknowz:
Reboot on 394

Started some updates in the Play Store and phone rebooted. Running Shiny ROM 10/11 build (4.3.1), bfq, interactive, 192, 1305. Here is the link for last_kmsg (don't know why its 113 pages). Also, has anyone else noticed a screen flicker a couple of seconds after wake?
[Samsung Galaxy Nexus] osm0sis:
Crap. I take that back.. Got my first reboot while running bfq. The last_kmsg is pretty clear.. Guess BFQv6 is still bugged.

Honestly guys I think bfq should just go altogether. It's hardly worth the hassle since v5 is stable but not smooth and v6 is smooth but not stable. Francisco said about the same the other night. We both agree that our tweaked row is far superior.
[Samsung Galaxy Nexus] maritimesbob:
Please delete!
[Samsung Galaxy Nexus] Sik-1:
It works on 4.4 jus fine, it is meant for aosp ROMs which Franco and several of us only use, cm and the kangers change ramdisk stuff alot so its a ROM thing,
[Samsung Galaxy Nexus] osm0sis:
I already explained this. The image does NOT work on 4.4 because it's got a Jelly Bean 4.3 ramdisk. Francisco will be releasing a version for KitKat soon.
[Samsung Galaxy Nexus] creeve4:
Any idea if the 4.4 version work with CM?
[Samsung Galaxy Nexus] TiagoRigueto:
my usb tethering work but very bad with this kernel...

you know why? very unstable...
[Samsung Galaxy Nexus] Sik-1:
You quoted his answer to tour question lmfao
[Samsung Galaxy Nexus] inihccor:
I saw that touch control is supported... how can I enable it?

BTW 394 is awesome!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] osm0sis:
Yes the KK ramdisk (when released) is based off of the latest CM and SlimKat both.

No idea. Can anyone else confirm? It's not a feature I use.

By installing it? r394 has module support enabled and everything. If you have any issues the onus is on the module dev so please take your support questions to their thread.
[Samsung Galaxy Nexus] gummie:
Hey Guys, just a quick one here. Correct me if I'm wrong. This regards to the Extra RAM feature. Did Os fix this or someone did? If not, is it already ditched or something? It made part of our daily driver to have that feature specially my Gnex has Facebook and Messenger on background.
[Samsung Galaxy Nexus] osm0sis:
Read back 2 pages please. :mad:
[Samsung Galaxy Nexus] h1ghland3r:
Someone can give me the link of r392-fixed?
[Samsung Galaxy Nexus] osm0sis:
It's gone. Fixed has been folded back into mainline. Use r394 for now until r395 is released. :good:
[Samsung Galaxy Nexus] h1ghland3r:
Thanks osm0sis.

Oh god, r394 doesn't work with touch control. If someone still has r392-fixed, can please upload me?
[Samsung Galaxy Nexus] osm0sis:
Tell the developers of Touch Control. I imagine they need to fix their sh*t, as always was the case with PGM.

Likely due to the 3.0.101 Linux kernel revision bump.
[Samsung Galaxy Nexus] h1ghland3r:
The same the nothing tell them. I tried in the past and they don't answer to me, even I had purchased the paid version. The r392-fixed is a fast solution.
[Samsung Galaxy Nexus] AutomaticFailure27:
Keep calm dude. [MENTION=2538253]bponury[/MENTION]'s main focus is on the Nexus 4. He keeps a statistic chart of all the kernels/devices and makes them based on popularity. Just give it some time.
[Samsung Galaxy Nexus] dracon6ai:
Plus he even stated to me multiple times that he never planned or promised to support the app or our devices forever. Between work, real life, and newer devices I highly doubt he will spend much time on the Gnex anymore. At least that's the impression I got through our emails.

***Laziness is nothing more than the habit of resting before one gets tired.***
[Samsung Galaxy Nexus] osm0sis:
Silly that something like updating the Linux kernel to the EOL .101 revision would break it. He should at least support that.
[Samsung Galaxy Nexus] arshum:
it is a bad news to me. I enjoy using Touch Control too...
[Samsung Galaxy Nexus] h1ghland3r:
As you have r392 fixed installed, can you provide us a link for download? Because bponury said that we need to ask for CM Team support the his module. >.>...
[Samsung Galaxy Nexus] yungboss22:
Franco, i dont like your conservative tweak because my phone spends all its time on 1200mhz and i have a poor battery with it.Your governor look like the interactive or performance governor lol. can u review this governor please ? It will be appreciated:)
[Samsung Galaxy Nexus] ctbear:
Have you check your background apps? Because it should switch to max frequency only when the cpu load is quite high (80%).

In my case, it spends ~80% in deep sleep, 10% in min and 10% in max frequency.
[Samsung Galaxy Nexus] ratson:
nothing!

10chars
[Samsung Galaxy Nexus] minipaolo:
It doesn't happen with me.

I normally get about 75% deep sleep, 10% max and 15% min
[Samsung Galaxy Nexus] Nebucatnetzer:
You don't have to wipe anything since the kernel doesn't affect one of those.
[Samsung Galaxy Nexus] yungboss22:
@Minipaolo

I have about 74% deep sleep but when my screen is on, my cpu spends all this time on 1200mhz with 15-20% cpu usage and a lil bit on 350mhz :(
[Samsung Galaxy Nexus] minipaolo:
you should prob set min to 700.

franco said it is probably the best setting because it tends to go idle earlier.
[Samsung Galaxy Nexus] Elganja:
try a 700 min... it will make a difference. with the new kernel on conservative governor it switches between the min and max only (see Franco's change log)
[Samsung Galaxy Nexus] rolear8:
Damn i never knew this neither!!!! i just did that and the FPS went super high! thanks a lot, i think we will need to do this everytime we flash AOKP????
[Samsung Galaxy Nexus] versd:
will running 700 min have any effect on battery life? i would think the answer is yes, but i might be missing something?
[Samsung Galaxy Nexus] franciscofranco:
That's obvious! 350mhz isn't enough to run the tasks you're performing, so, as it only ramps up to max freq it will stay there almost forever. Setting it at 700min it will stay there 70-80% of the time while max freq will be used the other 20%. That's why I've took some days testing this setup, in my opinion it's the best, that's why it's default ;)
[Samsung Galaxy Nexus] mustafaluigi:
using betterbatterystats app, i am seeing an almost constant wake lock with modem_usb_suspend_block under kernal wakelocks. anybody have any idea to stop this? i get about 8 hours of battery life while the phone sits unused. usb tethering is turned off.
[Samsung Galaxy Nexus] :
Hi,

I just tested a few minutes with Conservative governor (350Mhz-1.2Ghz) and my cpu does not spend (all) his time at 1.2Ghz (or the max cpu freq you choose).

I reset my settings to test (before 350Mhz-1.35Ghz/Conservative) to 350Mhz-1.2Ghz.Ok,I have not tested the defaut settings we are 700Mhz-1.2Ghz,but as you can see my cpu does not spend (all) his time at 1.2Ghz...He spends most his time from the selected minimum frequency (350MHz):

In any case,for me,i see no problem with Conservative governor...
[Samsung Galaxy Nexus] sishgupta:
I don't have this one at all in my kernel wakelocks. Are you sure your tethering is disabled? Try enabling and disabling maybe there is a glitch in the UI. I would toggle wifi tether too.
[Samsung Galaxy Nexus] Elganja:
I decided to remove my UV ... the phone feels better... less random laggyness ... I guess Franco was on to something with his default voltages ;)
[Samsung Galaxy Nexus] MSgtSimon:
Just bringing it to your attention in case it was an issue. Love your work.
[Samsung Galaxy Nexus] MFD00M:
Franco....great job on 14.1 I'm very impressed.

AOKP 20 (toro) with Franco 14.1 350min 1200 Max conservative governor, hot plug disabled. Stock kernel voltages.

7 of those hours was overnight idle while I slept. Only lost 3% on wifi in that time
[Samsung Galaxy Nexus] Caanon:
What app is that? Looks useful
[Samsung Galaxy Nexus] Heppieboeddah:
System Tuner [Pro]
[Samsung Galaxy Nexus] taney:
FYI, upgrade to latest radio and replaced with stock CM9 kernel. problem was gone.
[Samsung Galaxy Nexus] AutomaticFailure27:
Not 100% if this will work but here is a link for r392 fixed
[Samsung Galaxy Nexus] h1ghland3r:
It works like a charm, thank you! Finally my GNexus is ready to go to my sister.
[Samsung Galaxy Nexus] joaquinf:
Hi there!! nice to hear from the good old franco's team :cyclops: Thanks for quoting me on that one, yes I work in a hospital as a quality and project management engineer. Health care professionals unite! :highfive:

How's everything going? planning on keep the gnex for too long or already have something in mind? we could really use your help on the ONE forum :D
[Samsung Galaxy Nexus] The Gingerbread Man:
Ah man you should have went for the nexus 5... Nice to see you :)
[Samsung Galaxy Nexus] joaquinf:
The gingerbread man is in the house! hi buddy, nah I bought the ONE far before the N5 was launched and it's been an awesome device so far, no regrets. How are things going for you with your new toy? got some franco's love?
[Samsung Galaxy Nexus] pirigu:
hello guys you give me the link to the CM11 4.4? do not know what is compatible ... Thanks in advance:)
[Samsung Galaxy Nexus] The Gingerbread Man:
The display might be a little better one your one it has slightly higher ppi. In glad to hear your enjoying it though. Yup Franco is over on the n5 and things are going well with that development is getting better and the battery life is really good. Over all I'm really happy and couldn't recommend the n5 enough :)

I cm11 to my knowledge doesn't support any other kernels other than its own.
[Samsung Galaxy Nexus] McDuffSmith:
he meant the 4.4 Franco kernel for the GNex.

the last one had a broken ram disk and thus had bootloops.

he (and I) are looking for the fixed ram disk r394.
[Samsung Galaxy Nexus] metalspring:
There isn't one yet...
[Samsung Galaxy Nexus] McDuffSmith:
*I* know that. the other guy didn't.

its taking forever to get here by the way.

franco released an N5 kernel since the discovery of the broken ram disk.

witch is beyond me as this should be fixed first IMO
[Samsung Galaxy Nexus] metalspring:
He gives priority to the other nexus devices over the gnex (they are newer and probably have more users now?)

and it looks like the needed changes are in source to fix the other issues the r394 had, so all he has to do is compile it, then package it with his ramdisk (probably for 4.3), then osm0sis can make a 4,4 version
[Samsung Galaxy Nexus] McDuffSmith:
exactly: all he has to to is compile it.
[Samsung Galaxy Nexus] osm0sis:
Yup and I sent him the KK4.4 ramdisk too and he said he'd be compiling with each now. He emailed me while I was at work earlier today and mentioned he'd try to get to it tomorrow. :fingers-crossed:
[Samsung Galaxy Nexus] hshaikh:
Hi guys

I am using CM 10.2 stable on the Gnex. I looking at the franco kernel updater app and it says there is no stable version for my setup only nightly r392. Is there in fact no stable version out? is one coming? how is the nightly with CM 10.2 stable?
[Samsung Galaxy Nexus] wisefreakz:
Consider all nightlies as stable!!
[Samsung Galaxy Nexus] hshaikh:
ok i will try it. how do your guys think it compared with stock CM kernel for those on CM 10.2, wrt speed and battery?
[Samsung Galaxy Nexus] wisefreakz:
For the 4.3 ROM... Franco FTW!
[Samsung Galaxy Nexus] akash3656:
I find most kernels to have about the same battery life. But performance wise, almost every (but not all) kernels on XDA run circles above the stock CM kernel and also stock AOSP kernel.
[Samsung Galaxy Nexus] skizofrenic:
Is per-app mode correctly working?

Couse i tried set min-max 500-729mhz for a game....

It goes correctly to wanted freq during game

But it keeps this frequency also out of game (like now,writing )

The game is not in background

( edit 1: i LL try to set on boot min max freq 192 - 1200)

(Edit 2: confrirmed: per app mode overwrite min max freq, also when the related app is turned off. In my case was game Heroes of DA. So now , app is off and i m still at max freq 729....)
[Samsung Galaxy Nexus] kostheback:
Does it work on miui rom?
[Samsung Galaxy Nexus] Tommy_FIN:
So, what 4.4 roms are compatible with Franco r394? Gonna update later today so any info would be appreciated :)
[Samsung Galaxy Nexus] luckana:
I used it on CM11