yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] ChazzMatt:
Yes, Franco's big mem adds 50MB to the default 694MB. Also, beside allowing 1080p video, you can use all the barcode scanners (many of which were broken with Fancy big mem).

However, if you don't need full functionality, then the current Fancy is fine for you. I've used many kernels -- Franco, AK, Lean, Fancy. I'm not trashing Fancy, byope is a very good, respected developer. It just seems he got caught away with more important stuff (real life is more important than our cell phone hobby), and when he comes back he will probably update the kernel to include the Franco fix. byope may make it even better. All the devs go back and forth, using the others' work to make improvements and create their own.
[Samsung Galaxy Nexus] lightingcloud:
Actually, I loved Franco's kernel until he moved to N4 and gave his gnex to his wife. Now the Franco kernel has some rare updates, which are pretty much bugged if it weren't for osm0sis work to fix them with his releases. At least we know that boype may be busy right now, but will come back and provide us updates for our (and his) phone.
[Samsung Galaxy Nexus] ChazzMatt:
You must be thinking of someone else? Franco is not married.

But you are correct in that once Franco moved to the Nexus 4, his attention was on that. He is also supporting the current Nexus tablets.

He warned the Galaxy Nexus users of that a year ago. He was quite honest that the Nexus 4 would be his primary focus, since it was the current Nexus phone. But he said he would give occasional updates for the gen 3 Nexus for this year -- same way in the previous year he gave occasional updates to the gen 2 Nexus S when the Galaxy Nexus became his his primary device. Then he stopped the Nexus S updates when he got the gen 4 Nexus 4.

I think that's quite fair. One year devoted support to the current Nexus device, then one year of periodic support for the previous generation of Nexus devices. After two years, sorry. :)

And Franco has kept his word. There was another popular dev (not Franco, not byope) who got another newer Nexus phone and promised to continue support for the Galaxy Nexus -- then was never heard from again, abandoning his supporters. :rolleyes:

______

We are coming up on two years for the Galaxy Nexus. I am jumping to the Nexus 5, but my wife still likes her Galaxy Nexus (I bought two July 2012). My point is I know Franco support will soon end for the Galaxy Nexus. byope hasn't been around recently either, but he may come back. IF so, then I may put new versions of Fancy on my wife's phone, when Franco goes away from the Galaxy Nexus. It's just right now, at this moment, Franco's GNex kernel is a little more updated due to functionality.

And yes, I am thankful osm0sis has continued as the flame-keeper for Franco between his sporadic visits.
[Samsung Galaxy Nexus] TheMan0790:
I think you are thinking of Anarkia. His kernel was amazing, but then he moved to a Nexus 4 and the thread isn't active anymore.
[Samsung Galaxy Nexus] nmlssit:
Is this only some kind of speculation, right?

Last time i checked the thread i've read boype was busy because he moved away, is it so or do we have new informations?
[Samsung Galaxy Nexus] motorazrv3:
Boype got married than he got a new job and searched for a new home because he had to move.

He never said his won't be active any more and I personally think that he will inform us when he will stop building new kernels for our gsm.
[Samsung Galaxy Nexus] mixtapes08:
Try this one.

http://xdaforums.com/showthread.php?p=46748007

Sent from my Nexus⁴
[Samsung Galaxy Nexus] lippol94:
Guys, this entire discussion is sick.

Before asking whether this project is dead or not, why don't you ask yourself: "what do I miss?"

I mean, where does this kernel fail? It's perfect. Period. It pushes our Galaxy Nexus to its best.

And I'm sure Boype will update it as 4.4 comes out. He's, before being a developer, a user! I have no doubts he will share his piece of work to improve kitkat experience again!

About 1080p, do you really need it? It's not a matter of pixels. With our camera you'll hardly spot the difference (in terms of video quality) between a 720p or 1080p.

If numbers are so important to you, go on. Switch kernel. But please, keep this thread clean. And if you have any kind of question, Q&A forum is there for you!

Cheers!

Inviato dal mio Galaxy Nexus utilizzando Tapatalk
[Samsung Galaxy Nexus] Taomyn:
Well it fails on every CM10.2 nightly since 21/10.
[Samsung Galaxy Nexus] -Jesco-:
Well it's CM that's moving away from AOSP, first they moved Mako and Flo/Deb from AOSP library to CAF, causing much headaches to kernel devs or any devs in general. next they're changing ram disks all across. wanna blame a kernel? if the kernel is working great on all other true AOSP Roms, then blame CM :)
[Samsung Galaxy Nexus] ChazzMatt:
Many, many people have complained about the1080p break. Other kernels have implemented big mem and kept 1080p. It's a flaw byope has not fixed yet.

But talking about it is valid -- and people will continue to talk about it until it's fixed. Email him, tell him to look at Fanco's kernel and copy that fix. Easy to do.

__________

That was what was originally said a few days ago about the Franco kernel. Tell CM users they are no longer welcome. But then osm0sis fixed it. Now Franco kernel works with pure AOSP and CM.

And that was what was originally said in the AK thread months ago. I didn't want to mention his name, but yeah you guessed it. At first, everyone was saying "Oh, his kernel is still great. We don't need anything else!".

That's true if you keep the same ROM and don't flash any newer ones. Same kernel/same ROM will last as long as you want -- look at people who don't root and keep their pathetic contract phones for 2 years. :rolleyes: They miss out on all the great features of custom kernels and custom ROMs.

But you know it as well as I do, that as custom ROMs continue development, custom kernels have to keep up. byope may come back. But if he doesn't come back, here's two signs this kernel is already getting a little behind current development? :confused:

Use it as long as you like -- but the discussion is valid and is part of the development thread, when the kernel (for whatever reason) is no longer being developed.
[Samsung Galaxy Nexus] aamadorj:
I don't think 1080p absence in latest Fancy kernels is a flaw. I considered it just a choice: more RAM available or 1080p available. In my case, as mentioned before, I prefer the former, so I'll be happy if boype decide to build one version of his kernel with more RAM but no 1080p.
[Samsung Galaxy Nexus] osm0sis:
Just to clear things up, it wasn't franciscofranco "fixing" boype. It was BigBrother1984 with mpokwsths's idea and boype's general implementation.

Please make sure you read the commit next time to make sure you've got your facts straight:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/a5200bf56b02453da6d8d33e83baf2e51f014845

Also folks, I'm not compiling anything, ramdisk fixes are a simple repack procedure which can be done with my Android Image Kitchen on Windows (and many have posted scripts/tutorials for Linux). I highly encourage someone to make the basic changes required for compatibility to Fancy Kernel so everyone can stop *****ing. ;)

Edit: Fixed the Kitchen link, had the changes link in there by mistake. It's dead easy: unpack, edit files, repack. :good:
[Samsung Galaxy Nexus] iluvamk:
osm0sis - Do you have a tutorial on how the do this using your Android Image Kitchen? Would love to know how but not really sure where to start.
[Samsung Galaxy Nexus] Astug:
interactive/deadline, no other changes
[Samsung Galaxy Nexus] Jar3112:
Did you even try googling it?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] shawnaye:
quite the off topic, but could i get the name of that font?
[Samsung Galaxy Nexus] Astug:
http://aajohan.deviantart.com/art/Comfortaa-font-105395949
[Samsung Galaxy Nexus] cujo6801:
What is this "Google" you speak of?

It's witchcraft I tell you...

Witchcraft !!!!

sent from the DOG pound
[Samsung Galaxy Nexus] t1.8matt:
I tried following Osmosis' directions, even tried different kitchen tools. I just can't figure out how to make the changes to the kernel. Just seems like it's above my head until someone shows me or simplifies the directions. In not skiing someone to do that though, I'll just keep trying to figure it out.
[Samsung Galaxy Nexus] t1.8matt:
So let me get this straight, all I had to do was add /system/framework/framework-pac.jar and /system/framework/telephony-msim.jar to the bootclasspath in the init file of the ramdisk, repack it and viola, fixed kernel? That was easier than i thought, even though i never would have gotten that if someone didn't supply the info as to what needed changed.

---------- Post added at 10:25 PM ---------- Previous post was at 09:58 PM ----------

ah, i see. all i had to add was system/framework/telephony-msim.jar. but adding /framework-pac.jar also didn't hurt anything.
[Samsung Galaxy Nexus] t1.8matt:
Sorry if I'm getting off topic but maybe someone here can answer this. When I open the init file directly from the ramdisk folder into notepad, its a bunch of jumbled symbols. But when I do a search in the folder for bootclasspath it brings up the init file and when I open it, everything is legible. Just a curious question.
[Samsung Galaxy Nexus] csolanol:
The file is init.rc not init.
[Samsung Galaxy Nexus] ChazzMatt:
I just knew Franco gave credit to boype for the big mem, but did it better -- with full functionality for 1080p and ability to use all barcode scanners. I've used many kernels on my two GNexus, including byope's big mem.

byope is a respected developer, but his kernel is going to start drifting backwards like AK's did unless either he or someone else steps up to keep up development. When 4.3 came out, you couldn't use AK kernel any more.

When 4.4 KitKat is released, maybe byope will come back?
[Samsung Galaxy Nexus] osm0sis:
If you ask me, for all the brilliant, in-depth, and innovative tweaking he's done on a device this late in its life-cycle, boype deserves at least a month off.

And by the way, you could make a JB4.3 compatible hybrid ramdisk for AK like I did for f.K r384, but you wouldn't get any of the new JB4.3 kernel features. Jus' sayin', if you wanted to go die-hard AK, you could. ;)
[Samsung Galaxy Nexus] t1.8matt:
gotcha, i wasn't paying attention when i was looking through the ramdisk. gives yourself a nice feeling of satisfaction knowing you were able to fix something yourself, even with help from others. thanks for straightening that up for me.
[Samsung Galaxy Nexus] wai10691:
Fixed Fancy Kernel (com.android.phone force close issue on recent ROM)

Hey guys, I have been bugging by the force close issue of com.android.phone app because of the latest changes from CM side for some custom ROM. And because of that it has limited me from flashing recent ROM update from several devs, like Vanir.

So today I was having a little bit of time and go through some post on XDA and found the solution to fix this. There were some tutorial on fixing the kernel but I didn't find any fixed kernel of Fancy so I decided to write this post.

If you want to use Fancy kernel on recent ROMs, you can get the file here: fancy_kernel-tuna-4.3-r42-big - fixed

I only fixed r42-big because that's the best version I found and that's the one I used. If you want other version of Fancy to be fixed, you can follow this tutorial (Credit to [MENTION=4544860]osm0sis[/MENTION]):

And that's all, you're done. :)

Hit thanks if it helps.
[Samsung Galaxy Nexus] Lancez:
[MENTION=1534227]wait[/MENTION]10691, can u make an r42 ext.? Thanks in advance

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] t1.8matt:
Thanks. For some reason I've been doing exactly how your supposed to and I could not get Big-Fancy to work. I was able to fix Mpokang v10, but Fancy was still giving me problems. I'll have to unpack yours and try to see what I did wrong, even though its a really simple fix and I don't know what I could have done.
[Samsung Galaxy Nexus] wai10691:
Here's the fix for r42 ext. I didn't try. But it should work.

Link : http://d-h.st/vRA
[Samsung Galaxy Nexus] Lancez:
It works, appreciate d

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
That'll fix CM but not PAC: see the other change (in red) that needs to be added:

http://xdaforums.com/showthread.php?p=46748007

Great work! :good:
[Samsung Galaxy Nexus] iluvamk:
Here is a fixed pre44-3big file if you want it. All credit goes to Boype for the kernel and to osm0sis for his tutorial and his Android Image Kitchen. As it's a dropbox link and I don't know what the limit for downloads is please reupload if you can.

https://www.dropbox.com/s/apvzyiux40ftyoi/fancypre44_3fix.zip
[Samsung Galaxy Nexus] rjshrjndrn:
Mirror https://mega.co.nz/#!vkQFWJjI!YNxW7_Dto1E7-Ku_MnNgcBbKQ4jh-73FLAoUaY7FAuk
[Samsung Galaxy Nexus] osm0sis:
.... ;):p
[Samsung Galaxy Nexus] RaZi3L_:
com.buzzpia.aqua.launcher please :)
[Samsung Galaxy Nexus] pikso:
any chances to build beta kernel for slimkat 4.4? :D :good:

IIx0 :eek:
[Samsung Galaxy Nexus] paarthdesai:
pheww.. thank god you asked this question mate :)

i was soo getting restless that after 48+hrs since the release of kitkat.. y didn't any of the fancy user asked this question..

you're the one my friend.. thanks for it, ! and ty for making me stern on my belief that no matter what.. somewhere, someone will always be the there to ask eta's

sent from my seXy NeXy ;)
[Samsung Galaxy Nexus] Pumpino:
I just noticed that kernel 3.0.101 is now end of life. It's almost poetic that it's occurred at the same time that Google has stopped supporting our phones. If Boype does any more work on the kernel, it would be great to have it updated to the last ever 3.0 kernel, and maybe even a build for any decent KitKat ROMs that come along.
[Samsung Galaxy Nexus] sago62:
r43 with carbon build nigltly today tells me: the process com.android.phone has stopped ... why? I riflash everything at least 5 times ...
[Samsung Galaxy Nexus] Lancez:
Did u not read posts in the last couple of pages?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] TnK8iD:
did you try to fix permission?
[Samsung Galaxy Nexus] sago62:
Yes i have... But not works... Works with kernel modify...
[Samsung Galaxy Nexus] Lancez:
Have you tried 2 fixed kernels on page 712?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sago62:
This

http://xdaforums.com/showthread.php?p=46970382
[Samsung Galaxy Nexus] hawkstorm:
Hi,

I'm new to kernels and am running CM10.2. I flashed the Fancy-ext version of the kernel and the speed and performance is amazing! But I have a question, how do I control the settings etc?
[Samsung Galaxy Nexus] wai10691:
You can control the setting with TricksterMod

Link https://play.google.com/store/apps/details?id=com.bigeyes0x0.trickstermod
[Samsung Galaxy Nexus] CavacoIT:
Which kernel I have To flash on 4.1.2 ROM's?
[Samsung Galaxy Nexus] Syfer_Fever:
this kernel dosen't support 4.1.2, only 4.2.x (EOL) and 4.3.x
[Samsung Galaxy Nexus] d0ge01:
I need some fancy love in my 4.4 kitkat, so i done zip of fancy-kernel-r43-std that's compatible with 4.4 ( and 4.2.2 , i only removed ramdisk )

Download:

GDrive: https://drive.google.com/file/d/0ByJZo5VJY6SOVlZ4b0FoVTdyZFk/edit?usp=sharing

Mega : https://mega.co.nz/#!oVI2lS6a!IaZbjXMdCXO0VbbfDbVWHlciC4YC8kHyhDbFNEpDQWI

md5

247793b779a0d1e23a4320d3f2f628b1
[Samsung Galaxy Nexus] paarthdesai:
i love you... :D. ( not in a gay way obviously :p)

can u re-upload to dev host or media fire?

for some reasons link isn't working for me..

sent from my seXy NeXy ;)
[Samsung Galaxy Nexus] d0ge01:
Sure

I have not mediafire or devhost, anyway there's Mega mirror, hope this will work

https://mega.co.nz/#!oVI2lS6a!IaZbjXMdCXO0VbbfDbVWHlciC4YC8kHyhDbFNEpDQWI

md5

247793b779a0d1e23a4320d3f2f628b1
[Samsung Galaxy Nexus] paarthdesai:
oh noo mega please... asking for a decryption key.. :( :@

upload to your Dropbox if possible then..

sent from my seXy NeXy ;)
[Samsung Galaxy Nexus] felystar:
Has anyone tried r43 on stock 4.3?

Enviado desde mi Galaxy Nexus usando Tapatalk
[Samsung Galaxy Nexus] d0ge01:
I can't register to box or mediafire ( i have too many accounts on cloud :D ) anyway there's attachment
[Samsung Galaxy Nexus] Bubble-be:
Care to share your method ? I'd like the ext on 4.4 myself so I can see if Touch Control can work.
[Samsung Galaxy Nexus] t1.8matt:
i think all you need to do is use android image kitchen and take the boot image, unpack it, remove the ramdisk, repack the split folder, and use the new boot image. i could be wrong, i don't know if ext. uses a ramdisk or not. and i'm only going by how he made the 4.4 big kernel saying he only removed the ramdisk.
[Samsung Galaxy Nexus] t1.8matt:
Like this that i have attached, all i did was remove the ramdisk, which might cause you to lose some features, and like i said i may be wrong so have a backup handy if you attempt to flash this. someone please correct me if i'm way off.

edit: yeah, i removed it, i'm pretty sure i was wrong. i don't think you're supposed to have a boot.img in there at all if you remove the ramdisk, so don't listen to me. sorry.
[Samsung Galaxy Nexus] rjshrjndrn:
Do you think there will be a 4.4 fancy.
[Samsung Galaxy Nexus] n2rjt:
Yes. Better question: who is working on it and what help do you need?

I did kernel development for a different phone a couple of years ago. I never did anything innovative but was able to use scripts and toolkits built by others to build code mostly written by others. I plan to try building fancy for 4.3 then 4.4 but it might take me a few weeks. If I hear someone else succeeding or if Boype gets time to work on this, I'll happily give up. And heck I might just give up anyway.
[Samsung Galaxy Nexus] d0ge01:
Man, with this minor releases, kernel is not released with ROM itself, you can use any kernel in 4.4, i tested AK 256 ( Summer 2013 kernel ), fancy kernel r44-big and r43-std and alot of them.

The main different is ramdisk, the problem will born with old devices that using 2.6.x branch of linux, where's there no compatible SELinux enviroment or driver , etc...

http://xdaforums.com/showpost.php?p=47113330&postcount=7136

There's my working fancy kernel r43 std compatible with 4.4 AOSP, i'm using it without any issue :)

anyway everyone is waiting boype when he's some free time and can release r44 :D
[Samsung Galaxy Nexus] Bubble-be:
How did you get rid of the ramdisk?
[Samsung Galaxy Nexus] seriousia:
Not working with PAC-man 4.3 build 1 :(
[Samsung Galaxy Nexus] d0ge01:
Can you try my version ( some post over ) ?

There's will be no problem, so use the same ramdisk of rom

( Pacman and some other rom *coff* *coff* Cyanogenmod *coff* *coff* used to change system and require special ramdisk

with stock kernel there's no problem, but with custom yes, use kernel with same ramdisk will fix 99% this issue )
[Samsung Galaxy Nexus] milojoseph:
does this suport zRam which do you prefer swap or zRam
[Samsung Galaxy Nexus] payas0:
I used your fancy on older versions of Grarak's 4.4. But on Grarak's latest update, your kernel leads to boot loops. I wonder why. Can you confirm this or is it just me?
[Samsung Galaxy Nexus] seriousia:
its because of ramdisk i guess, i had the same problem with PAC-Man 4.3 build.

you need to change the ramdisk.

---------- Post added at 12:33 PM ---------- Previous post was at 12:29 PM ----------

i did that my self, changed the ramdisk, now kernel is working but phone is crashing and rebooting every 3-4 min after boot maybe its a kernel problem or ramdisk which i used?????? :eek: :confused:

so now im using franco kernel.
[Samsung Galaxy Nexus] vinymaster:
error

"Unfortunately, the process com.android.phone has stopped." is spamming after reboot. How to stop this?

i using AOKP nightly (jb-mr2)2013-10-31,any solution?
[Samsung Galaxy Nexus] standa75:
This usually happens when installed not compatible kernel vs ROM.You can try install only ROM and see whether problem is solved.:fingers-crossed:
[Samsung Galaxy Nexus] paarthdesai:
if u searched in the thread u wld have got your answer..

use another kernel that has been updated with new cm changes like mopokang.. u have to search there too coz it's posted somewhere in the thread.. not op

sent from my seXy NeXy ;)
[Samsung Galaxy Nexus] vinymaster:
thanks, i try franco kernel and works fine!

(y)
[Samsung Galaxy Nexus] iSadic:
Here is the fixed r43-ext version:

https://mega.co.nz/#!QRxQlbbD!OpRmBlMd9gQ-6eTQATCYRiE1V68Z_-WISTVapxckLJU

tested on latest AOKP nightly (2013-10-31)
[Samsung Galaxy Nexus] vitokes:
so just curious but im here because of FML 4.4 and it talked about using fancy kernel. will this work with that? im just not sure. maybe this is the wrong place to ask this if it is just delete. im not hating. but i still would love to know.
[Samsung Galaxy Nexus] d0ge01:
You have done this:

1: flash ROM

2: flash kernel

?

It's strange cuz it will work in every ROM due it using same rom ramdisk

Phone problem is caused by a CM commit that break compatibility with different kernel than stock

Use stock kernel or fixed kernel

Inviato dal mio Nexus 7 utilizzando Tapatalk
[Samsung Galaxy Nexus] CommanderDuplex:
any news from Boype ??
[Samsung Galaxy Nexus] Charmacas:
No!

But I sent him a message. Hopefully he returns soon. There is a lot to do here and we need people like him. :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] nec_d:
i've tried many kernels lately, but this one ROCKS! stable, speedy and battery life is superb!!! :good::good::good:
[Samsung Galaxy Nexus] milojoseph:
per app gpu/cpu settings will be nice
[Samsung Galaxy Nexus] hhwong:
Cant run on cm10.2 nightly oct 13 version.

"Unfortunately, the process com.android.phone has stopped."

In fact, i cant run it for quite a while, ever since around september.

I tried flashing the kernel, tried flashing rom dirty, tried flashing rom clean, heck i even tried to go back to stock and and did a clean install cm, still doesnt work.......

Since cm is such a popular rom i was hoping someone else would know whats wrong :(
[Samsung Galaxy Nexus] marpipro:
You must flash fix rel of fancy or franco cause new stuff of ramdisk in cm is incompatible with all previous kernel. There are tons of similar issue in many kernels thread for many roms users. Search for fancy.pre44.3.fix. few pages ago. If il find my file I'll post for you.
[Samsung Galaxy Nexus] hhwong:
i fixed it using r43 big, thanks for the info though :)

i am glad some genius made the fix for normal users like me, otherwise i would be forced to use other kernels which is far from optimal imo!

/cheers
[Samsung Galaxy Nexus] abhishek93:
guys why after a day my ram decrease? like after boot its 400mb free after half of the day its 315 and after a full day it will be like 280 something.. nd my apps restarts when i check running apps.

anyone who can help me?
[Samsung Galaxy Nexus] RajatPatel:
You seem to have OCD about free RAM, lol ;)

This behaviour is normal :D
[Samsung Galaxy Nexus] abhishek93:
i was thinking the same but it goes worse.. after few days, 2 or more.. apps dnt start.. nd all i can see is that apps are restarting..

like swiftkey it take atleast 10 seconds to open up so i can type..
[Samsung Galaxy Nexus] dirtygoldfish:
Sounds like a ROM issue tbh.
[Samsung Galaxy Nexus] vojkan22:
^ yup, leaky rom
[Samsung Galaxy Nexus] Doublewise:
What Rom are you on?
[Samsung Galaxy Nexus] RajatPatel:
Oh i see, sounds serious now!!

did you tried reflashing the ROM?

You can use Greenify app to hibernate the unnecessary background apps. It saves lots of RAM tbh :good:
[Samsung Galaxy Nexus] abhishek93:
Yea flashed stock rom today.. Nd yup I use greenify..

Right now no problem with stock.. :)
[Samsung Galaxy Nexus] jameshmiller:
To check for leaks, download Android System Info, goto the tasks tab and sort by memory usage. I think a lot of 4.3 ROMs based on CM have a System UI leak. If your phone starts to run really slow, as was described, I bet System UI will be at the top of the list, and it will be close to 200 MB.
[Samsung Galaxy Nexus] vojkan22:
^ this, and even more often, android system leak