yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] TurboLed:
Which build (date)? With the one from yesterday (20131205), I get boot loops as soon as I install Franco r394... Even with wiping.
[Samsung Galaxy Nexus] osm0sis:
That's because it doesn't have a KitKat ramdisk. It's been mentioned many times. Read please. Someone posted an AnyKernel version shortly after Francisco pushed r394, but of course you lose some of the tweaks we've made to our ramdisk to have things extra smooth. That'll have to wait for r395 whenever Francisco has the time.
[Samsung Galaxy Nexus] creeve4:
I am really looking forward to r395, it is awesome of Franco to toss us a bone now and then.
[Samsung Galaxy Nexus] SahilC:
Hey Os, I'm really sorry for the OT, but I was wondering : I know you love pure stock ROMs. Are you planning on waiting for an AOSP one, or going for CM11 Kit Kat?
[Samsung Galaxy Nexus] :
I think he's waiting for a proper, stable KK ROM.
[Samsung Galaxy Nexus] electro`:
oops lel
[Samsung Galaxy Nexus] Vekhez:
That has basically come with CM11 for the Toro, Toroplus and Maguro. Basically, we just need Franco to get the update to us, be we are probably last on the priority list, since the N7 (2012/13), N10, N4, N5 all have KitKat officially.
[Samsung Galaxy Nexus] luckana:
well i flashed the version that said android 4.4, are you flashing the 4.3 one ?
[Samsung Galaxy Nexus] Myster:
According to a reply from TouchControl Dev here lastest version of franco kernel 394 doesn't support modules again...
[Samsung Galaxy Nexus] osm0sis:
That makes no sense.. :confused:

Lines 20-24:

https://github.com/franciscofranco/Tuna_JB_pre1/blob/nightlies-4.3/arch/arm/configs/tuna_defconfig
[Samsung Galaxy Nexus] hhwong:
so......in short r394 does NOT run on cm11......right? I tried and i got into a boot loop.....

Is there a working version for CM11 atm? or just any working kernel for cm11? i am on the official nightly btw.
[Samsung Galaxy Nexus] Vekhez:
There is no the R392 FK that works, but Faux, ASKP, Golden Kernel, basically any kernel, if you download it, then open it, and if you see boot.img it won't if you see a kernel folder it will.
[Samsung Galaxy Nexus] hhwong:
while that is good to know, do you know which kernel has the extra memory like Fancy Kernel does? I personally find that to be the best feature ever on gnex XD. That with zram makes the phone so snappy, ive tried a lot of different kernels previously and if it doesnt have the extra memory, the phone always pop me out of zram and requires to relaunch the app........kinda annoying.
[Samsung Galaxy Nexus] Vekhez:
Mpokang SuperRAM 4.4 (if you go to the MPOKANG kernel thread and then on the side the like thing (right side) there is one with 7 likes. That's got the SuperRAM 4.4 kernel. It has almost 800mb's
[Samsung Galaxy Nexus] osm0sis:
KOT49E apks, including a new Google Home (GEL) launcher stub and the actual launcher, Velvet (Google Now/Search). Email and Exchange also got a notable update fixing the wakelock/battery drain with Exchange finally. Google Play Store apk removed (still 4.4.22) since 4.5.10 has started rolling out; Wallet also removed since a newer version has been available for a couple weeks now.

http://d-h.st/users/osm0sis/kot49e-kk4_4_1-apk/
[Samsung Galaxy Nexus] sd3993:
any whats been change in the launcher stub and the new google search?
[Samsung Galaxy Nexus] osm0sis:
Harder, better, faster, stronger? ;)

Seems a little less buggy, and a little quicker to me.
[Samsung Galaxy Nexus] sd3993:
You still talking about the launcher rite? lol :D

Sorry jk...thnx :)
[Samsung Galaxy Nexus] swedkg:
Thank you for that!! Is com.google.android.GoogleCamera-2.0.002-926649-30.apk supposed to work on our devices?
[Samsung Galaxy Nexus] osm0sis:
Yeah, it works fine. The only problem is with the KK version of Gallery FCing when you try to edit.
[Samsung Galaxy Nexus] swedkg:
Well, after installing the new gallery, I don't have a camera anymore..

...which is now back on that I uninstalled the new gallery.
[Samsung Galaxy Nexus] osm0sis:
Haha that's because you also need to install Camera. ;)

They're not fused anymore, they are 2 separate apks. Gallery and Camera.
[Samsung Galaxy Nexus] swedkg:
Yeah!! Needed a couple of seconds to realize that, since i missed the "swipe from lockscreen to open camera" thing and the icon from the launcher. :D:D
[Samsung Galaxy Nexus] TurboLed:
Should we install these APK or put them in /system/app or /data/app ?

Are we gonna see these integrated into Gapps eventually?
[Samsung Galaxy Nexus] osm0sis:
They install just fine the normal way. GEL and such have been integrated into GApps already, I'm sure someone will update theirs with the KOT49E apks soon.
[Samsung Galaxy Nexus] PCWright86:
When I click your link, it shows the downloadable files but upon clicking a file to download. It say ERROR something has went wrong..

Edit: Tried a few hours later and all worked fine. Thanks for the apks and your hard work with this kernel.
[Samsung Galaxy Nexus] ahmadairfan:
Hey os, sorry for OT, but did you install your KOT49E apks on 4.3 rom?

I did install GEL and it says like "placeholder text google search not found" or something like that:confused:
[Samsung Galaxy Nexus] osm0sis:
Yes. Works great. Do you not have the latest Google Search also installed?

Edit: I do see that the newest hammerhead Google Search seems to require that different recognizer lib again though; could be best to just use the one on the Play Store and wait for that to update for a universal new version like last time. Up to you though. ;)
[Samsung Galaxy Nexus] ahmadairfan:
This! thank you sir :victory:

Can we change the icons (on GEL)? Or at least hide some icons for the sake of aesthetic :good:
[Samsung Galaxy Nexus] niamul:
I went into a boot loop with the 394 kernel on 4.4/cm11

How do I fix it?
[Samsung Galaxy Nexus] BladeRider:
Try flash the previous version kernel, R392-fixed by Osmosis

If it still doesn't work, you might have to reflash the ROM and stick to stock kernel or opt for another kernel. Otherwise, just patiently wait for Franco to update the kernel
[Samsung Galaxy Nexus] Vekhez:
Not really to do with the kernel but more with FKU.

The Colour Control toggle doesn't do anything. You can change colours with it off and it works fine.
[Samsung Galaxy Nexus] redj12:
Hi,

I am looking for the 392 fixed version by [MENTION=4544860]osm0sis[/MENTION]. I am on the last AOKP and I must stay on the stock kernel because there is many FC com.androoid.process if I flash another one. With the fixed version by osmo it was OK.

There is nothing about this kernel on d-h osm0sis profil.

Thx :good:
[Samsung Galaxy Nexus] osm0sis:
Fixed is gone. [MENTION=3292224]franciscofranco[/MENTION] needs to push r395 because it (with the KK and JB ramdisks) should have all the fixes we need.
[Samsung Galaxy Nexus] mangusZen:
Why remove ? Its still one of the best kernel out there on kk for maguro, im using it right now...and I hold it tight :D
[Samsung Galaxy Nexus] redj12:
Oh, sir, can you share your zip please ?

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Because it was supposed to be obsolete with r394, and should totally be with r395, which [MENTION=3292224]franciscofranco[/MENTION] just needs to check to make sure modules and ASRAM work, build with both ramdisks I sent him, then release.
[Samsung Galaxy Nexus] creeve4:
Please [MENTION=3292224]franciscofranco[/MENTION]
[Samsung Galaxy Nexus] rajputrajat:
Has anyone noticed, there is a pull request on github...

https://github.com/franciscofranco/Tuna_JB_pre1/pull/1
[Samsung Galaxy Nexus] osm0sis:
Yeah that was actually discussed awhile back by the author and he posted a test kernel which unfortunately was pretty unstable with the patch.
[Samsung Galaxy Nexus] rajputrajat:
Hmm, somehow I missed that..

Thanks.. :)
[Samsung Galaxy Nexus] axlrvx:
That is the r395?

http://192.241.177.15/GalaxyNexus/4.4/zips/ this address send me to a zip with the r394 kernel, ir works with KitKat?

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] mixtapes08:
Os what's your current setup right now?

Sent from my Nexus⁴
[Samsung Galaxy Nexus] The Gingerbread Man:
Osmosis and other 'seasoned members' who know what they are doing, you may want to check http://xdaforums.com/showthread.php?t=2546120 you may benefit from the bionic zip, probably not the dalvik one. To anyone else who fancies a test be sure to run a nandroid before. I won't provide support for it and its not my work but just curious to see if this works on the galaxy nexus
[Samsung Galaxy Nexus] Vekhez:
4.4_qc-optimized_dalvik.zip works on omni-4.4.2-20131212-maguro-HOMEMADE.zip just fine :D

Not trying the Bionic one because it says in the OP that it's already built into CM/OMNI :D
[Samsung Galaxy Nexus] sd3993:
Works but no performance improvements....i feel stock dalvik is faster for gnex....
[Samsung Galaxy Nexus] AndyYan:
It makes no sense trying QUALCOMM-OPTIMIZED libs on a TI OMAP device...
[Samsung Galaxy Nexus] Vekhez:
Dunno what you are talking about, I flashed it and Mpokang, and I definetaly felt a performance boost... I found that I opened apps (especially games) 1-4 seconds quicker.. not crazy, but better.
[Samsung Galaxy Nexus] The Gingerbread Man:
That's why I said people who know what they are doing, to recover if it soft bricks. This is meant to be faster than art, in arts present state. I was only curious ☺
[Samsung Galaxy Nexus] AndyYan:
Yeah but newbies tend to do whatever they can to "improve performance" brainlessly without thinking of consequences. In that Qualcomm patch thread, some non-Krait examples got bootloops already. Just to avoid noobs firing complaints all over the place :)

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] metalspring:
I did test it myself... any performance gains on dalvik was minimal and may just be due to tests not being 100% accurate and ART runtime blew both away lol

antutu UX test (test dalvik performance and multitask performance, the numbers below are just for dalvik)-

normal dalvik- 1250-1300

patched dalvik- 1275-1340

ART- 1525-1575

So basically that patch for dalvik may cause a slight increase in performance when using dalvik runtime, so its probably not worth the risk of breaking anything using files not intended for our phones, and ART runtime is still the fastest without question
[Samsung Galaxy Nexus] The Gingerbread Man:
[MENTION=4328678]metalspring[/MENTION] did you try the bionic one also? There's 2 files, one for dalvik and one for bionic

[MENTION=4467696]AndyYan[/MENTION], I still don't think you understood how I originally worded my original post. Anyway what ever, I'd of tried myself if my gnex was working still.
[Samsung Galaxy Nexus] metalspring:
I think most custom roms already include bionic patches for performance that work on all devices and are even better optimized than the ones that patch installs

Also there are tons of even more optimized bionic patches out there (like linaro's bionic patches for example)

Someone on a straight aosp 4.4 build would need to try the bionic patch
[Samsung Galaxy Nexus] The Gingerbread Man:
Yeah that's the general twist I got from the thread also. I didn't know what your current set up was :)
[Samsung Galaxy Nexus] redj12:
Noop for me. I can't explain why because it's a random choice :)

Envoyé de mon Galaxy Nexus
[Samsung Galaxy Nexus] Charmacas:
I recently noticed that this thread is more about quality discussion neither than the franco kernel itself. I like that. ;)

And now you guys brought up the IO scheduler topic. I also have the feeling that it's more of a miracle what to use there but on the other hand it really makes a difference which scheduler and RAB you're using. So strange situation at all on this topic.

So I decided to make some testing on that topic and here's my first result on SIOplus vs. BFQ: http://goo.gl/hYJiaY

I am bringing it in here to hear some thoughts from you guys. If you could answer me the following questions and maybe bring in your own thoughts it would be great. If the feedback is good for this I will consider to open a thread for it and make more tests with other schedulers.

In your opinion: Is it a miracle that the results for the right scheduler and RAB varies from device to device? Of course the same device is meant. I know that tests are always showing something else but in the average it should be nearly constantly, should it?

What do you think could be optimized in my test? Except more test data of course. ;)

Do you think I should put more effort on this? If yes: Which schedulers would you like to see?

The schedulers also have tunables which could be configured. How should we handle this? I mean that would make thousands of thousands variations... -.-
[Samsung Galaxy Nexus] Sik-1:
Similar test have already been done, that's how the fellas here came up with the winning tunables, do a search and its plenty good reading
[Samsung Galaxy Nexus] ashclepdia:
for sure, those are great starting points also if someone wanted to optimize their settings for their own custom usage, since everyones usage varies by little or even major significance. i do not doubt though the work that went into finding the best tunables for schedulers. but if someone wanted to do even further testing and changing of things i feel it would be better suited in its own thread in place of taking more space in here since it could be applied to many other kernels as well. :)

i am not well versed in all the different things those tunables actually do and how they work, but im sure that different things can be changed to optimize even further but only really for specific instances and uses(aka- trying to optimize it specifically for certain uses, preferring speed in one area of it, etc...) ya'll went bonkers on those tunables with [MENTION=1143630]osmosis[/MENTION] lol, so i know ya'll got it pretty damn down pat.

(apologies..just realized i was rambling again... /AshRambles ... blame beer)
[Samsung Galaxy Nexus] The Gingerbread Man:
Really extensive testing went into optimising the io schedulars and a few other bits and bobs but I believe I can can speak for all involved feel free to see if can pick up from where we stopped https://groups.google.com/forum/m/#!forum/francosdevteam
[Samsung Galaxy Nexus] Charmacas:
Okay guys. Thanks for the answers! :)

If anyone got further feedback for me please write a PM.
[Samsung Galaxy Nexus] Schneewitzchen:
Hey guys,

i think franco has an error in r394 with the init.d support.

I stumbled on it because every time i set my screen colors with an init.d script, my screen is flickering every now an then. So i edited the multiplier file of the color control to set strange colors. After saving the multiplier file, a few seconds later the colors defined in my init.d script where set.

Don't get me wrong, but my understanding of init.d is to run scripts one single time on boot.

So i looked in the init.rc in r394 and compared it to the one in r392. The difference between both is: in r392 is an option called oneshot defined to the runparts of the init.d folder! In init.rc of r394 this option is missing.

Is this error work as designed or is this really a little error?
[Samsung Galaxy Nexus] osm0sis:
You sir are good! I just noticed this this morning myself while updating all the fkbootscripts with what we were talking about over in my thread. Fixed it already. :)

P.S. And about the renice fix, oddly enough just adding the pipe to head in the if statement seems to be enough, even though it doesn't necessarily make sense. :good:
[Samsung Galaxy Nexus] axlrvx:
I have flashed every kernel in xda for the gnex and the best kernel I ever flashed is the franco kernel. There's no support for KK yet, and that's why I don't use it for now.

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] osm0sis:
F**k it. Merry Christmas!

http://d-h.st/users/osm0sis/fixed/
[Samsung Galaxy Nexus] thesebastian:
You're right. I'm using KitKat for daily now.

I discovered that the problem was the CM11 kernel (and a lot of Roms uses CM11 tuna kernel).

[MENTION=4544860]osm0sis[/MENTION], i highly recommend you to try CM11 latest nightly with A.S.K.P kernel. For now I think its better than Google 4.3

Thx! Gonna try it today ;)

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
Maybe soon.. ;) But right now I'm still having fun/not totally done breaking Stock ROM now that I don't care about OTAs anymore. :D
[Samsung Galaxy Nexus] aR_ChRiS:
But...but...I was waiting for r395 to release :D

Jokes aside, is the ASKP as good as fK though?
[Samsung Galaxy Nexus] pkgnex:
Thanks, Osm0sis!

We're still awaiting a Franco-built "r395" to get the fixes incorporated into the mainline kernel, and add ASRAM back in, correct?
[Samsung Galaxy Nexus] thesebastian:
I don't know. I quoted ASKP as an example. You can also try Mpokang 1080p adapted for 4.4 by [MENTION=4328678]metalspring[/MENTION]

Just evade the CM kernel it has a lot of delays.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] axlrvx:
The battery life is not very good in superRam and askp with only facebook, twitter, whatsapp and tapatalk installed, I only have 7 or 8 hours of duration.

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] thesebastian:
Well i didnt tried superram kernel but with ASKP and 1080p mpokang I have great battery life.

A little better than Google Stock 4.3 ROM.

I'm going to try Franco today.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
thanks for the early gift, everything smooth as hell so far, o and I'm on 1.7 for ****s and giggles but I barely make it to that speed often bcuz its so slippery
[Samsung Galaxy Nexus] osm0sis:
Correctimundo! I emailed him the images so he can just extract the ramdisks to fix mainline with. I'm pretty sure I've got ASRAM enabled already again in the source, it just needs him to compile it and test to be sure about that and module support working before he releases it.
[Samsung Galaxy Nexus] redj12:
Yep, but I can't download my gift. Error. Will wait and try later. :D

EDIT: Bull****, it's Ok now.
[Samsung Galaxy Nexus] pirigu:
hello guys by any chance there is a zip dell'r349 KitKat flashabile through recovery? Thanks
[Samsung Galaxy Nexus] Sik-1:
No need for zip, download flashify on the market and flash boot IMG, simple and fast

---------- Post added at 02:48 PM ---------- Previous post was at 02:47 PM ----------

Sorry and I do see where the zip is needed also for convenience
[Samsung Galaxy Nexus] redj12:
http://192.241.177.15/GalaxyNexus/4.3/zips/

Edit: You want KK kernel...Bad link, sorry.
[Samsung Galaxy Nexus] osm0sis:
If you desperately need a zip, it's easy enough to just rename to boot.img and put it in the mainline r394 zip. :good:

Otherwise Flashify and f.Ku easily allow you to directly flash .img files.
[Samsung Galaxy Nexus] pirigu:
thank you so much now I do it now!:o
[Samsung Galaxy Nexus] Schneewitzchen:
Thanks and no problem for the hint at the renice fix!

Thanks to you and your work! Without you and the guys at the dev Team back in the days, this kernel wouldn't be this big and great!
[Samsung Galaxy Nexus] axlrvx:
I flashed the .img with nexus root toolkit and it works very well, I have never flashed a boot.img but google and youtube are the best teachers :D

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] pkgnex:
r394_os-fixed kitkat version is running well on Shiny 4.4.2.

Man, I do miss ASRAM already, though... and the old f.ku app, for that matter!
[Samsung Galaxy Nexus] sd3993:
[MENTION=4544860]osm0sis[/MENTION] the fixed version for kitkat seems to break battery stats on cm11 latest nightly 16/12. Battery jusy shows 100% all the time
[Samsung Galaxy Nexus] osm0sis:
That's pretty weird... Can anyone confirm? I might have to just rebase it off a newer nightly's ramdisk.
[Samsung Galaxy Nexus] metalspring:
Cm builds after dec 15 have an updated healthd binary, which needs switched out for the old one to fix that issue (as I found out modifying the mpokang kernel's ramdisk)
[Samsung Galaxy Nexus] osm0sis:
****! It's such a headache keeping up with CM. :mad:

I suppose the new healthd binary breaks AOSP ROMs and everything that came before too? :rolleyes:;)
[Samsung Galaxy Nexus] sd3993:
i swear! i suppose it's their dock battery support thingy.

And nothing else seems to be broken for now. Even r394 with the AnyKernel method is working fine. It's just kernels which have their own ramdisks that give problems :/

Can't wait for PA to release....will switch immediately!
[Samsung Galaxy Nexus] metalspring:
I assume since its all because of one commit...

http://review.cyanogenmod.org/#/c/55029/
[Samsung Galaxy Nexus] The Gingerbread Man:
Cm are indeed playing funky chickens lol Someone in n5 had battery % of 4325 something lol
[Samsung Galaxy Nexus] shatteringlass:
Had this exact issue on my gnex with latest cm11 nightly. Negative battery voltage, 0.6° battery temperature and a scale of ~4000, charging but not connected. Back to stock kernel.
[Samsung Galaxy Nexus] Vekhez:
Cyanogen Mod.. they have the right thing in mind, but they forget that not many people (in the Nexus community anyway) flash CM and that's it's like, CM+FK/Golden/AKSP/Mpokang and doing all this stuff is great and all, but they sorta need to tell people, or find a way to implement it without breaking everything else.
[Samsung Galaxy Nexus] akash3656:
Guys just flash an anykernel type of kernel and you will be fine with cm 11.

The whole CAF issue (nexus 4, 5) is what amazes me and the main reason I don't like cm. But on this Galaxy Nexus, cm11 seems like the most stable 4.4 ROM so I'm being a hypocrite and run cm11.

But seriously couldn't cm like use dome fallback option or something when a older ramdisk was used? It's insane to see those battery percentages lol.
[Samsung Galaxy Nexus] TurboLed:
Battery issues are fixed with mpokang: http://xdaforums.com/showthread.php?p=48557359#post48557359
[Samsung Galaxy Nexus] axlrvx:
I will not upgrade from the 20131214 Nightly, I think is the best nightly and the franco kernel la working without issues.

Enviado desde mi Galaxy Nexus mediante Tapatalk
[Samsung Galaxy Nexus] muntain:
20131214? are you talking about franco kernel version? because in the repository (http://192.241.177.15/GalaxyNexus/4.3/zips/) I think the latest is 2013-11-28
[Samsung Galaxy Nexus] hdoraemonk:
20131214 is CM's nightly :p
[Samsung Galaxy Nexus] osm0sis:
Great.. And from what I've read, using the newer CM healthd will break anything older. So what the f**k, make 3 ramdisks now? Bullsh*t.

I'm looking into writing an epic AnyKernel script to place all the f.K tweaks in whatever ramdisk you have.
[Samsung Galaxy Nexus] Fenvarien:
One script to rule them all! That sounds very promising :D
[Samsung Galaxy Nexus] memaro_maro:
please... im tired running so many scripts n build prop editing since 4.4.2 launched.

still waiting f.k injection.. then, perfect

galaxy nexus i9250
[Samsung Galaxy Nexus] szale9001:
Ok, that sounds awesome and not to discourage what sounds like the coolest script ever, but just FYI, this commit was just posted yesterday and might fix the messed up battery stats in the latest nightly. I haven't had time to look into/test it.

https://github.com/CyanogenMod/andr...mmit/b0fde04f862349e2a2166a48d534035b52ea3fdf

Last comment on the dock support commit basically restates the above

http://review.cyanogenmod.org/#/c/55029/
[Samsung Galaxy Nexus] Edward Stanbury:
hey bro: http://xdaforums.com/showpost.php?p=48613949&postcount=31

good news yes ? ;)

so in theory guys the previously fixed version should work on the latest 4.4.2 cm roms !
[Samsung Galaxy Nexus] osm0sis:
Yup, sounds like it's fixed again. :)

That's good since Francisco hates AnyKernel. ;)

I'll still look into the AnyKernel idea when I have time though, mostly I'll just be moving most things back into fkbootscript from the .rc files, and then sed merging a couple important changes to the .rc files to ensure we have root, init.d, fkbootscript, and custom fstab stuff working.

Right now I'm making an odex script for my own evil uses still trying to break my 4.3 Stock ROM. :p