yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] osm0sis:
If it happens on every kernel then you should be complaining to Google to fix their sh*t, not in every custom kernel thread. ;)

It's MPU Watchdog. Nobody knows why it happens.

That IRQ error is a damn mess though. That isn't happening here so it must be your ROM. Clean flash.

---------- Post added at 07:58 AM ---------- Previous post was at 07:55 AM ----------

P.S. Can someone recommend a good Stock-like KK ROM for maguro? I'd love to use something like Shiny or FML but sadly they're toro only.
[Samsung Galaxy Nexus] Culex316:
MPU watchdog means that something is locking up the CPU and the watchdog (which checks to see if the CPU is running normally and) resets the CPU if it doesn't get a "response" within a certain amount of time.

http://en.m.wikipedia.org/wiki/Watchdog_timer
[Samsung Galaxy Nexus] akash3656:
osm0sis, wait up a little longer looks like nasty 4.4 glitches/reboots may be finally fixed. Once its confirmed to be fixed, Omni or Slim should be nice and clean to use.

This works for me when flashing older builds of Shiny on my maguro :)

http://xdaforums.com/showthread.php?t=2362644

Everything worked fine other than HSPA being constantly shown as 3G and not H. If you can't connect to data, go to the APN settings in Android and use the built in reset APN option.
[Samsung Galaxy Nexus] McDuffSmith:
you could try Paranoid Android 4.0 beta. i've heard good things about it. its nearly stock too.
[Samsung Galaxy Nexus] joelmonty:
I've used the cm11 ROM it's still not as smooth as stock jelly bean, it's stable though I didn't have any reboots or glitches works fine, only things I had noticed was done delays in music playback.
[Samsung Galaxy Nexus] namelesske:
Its not rom problem its will be a hardware issue, its happens with Google Factory image too. :eek:

CM11 20140103 Nightly is really good and smooth with mpokang1080 kernel and with playfulgod's 1222Gapps_ps
[Samsung Galaxy Nexus] metalspring:
You could always try cm... I know it's not really close to stock but it's one of the few roms that doesn't have reboot issues

Also FML still has reboot issues (only a few roms have them fixed and they don't even know what fixed them lol)

---------- Post added at 09:08 AM ---------- Previous post was at 09:05 AM ----------

Not sure about stock jellybean but most of the KitKat roms I've tried blow any jellybean roms away in terms of speed and smoothness
[Samsung Galaxy Nexus] joelmonty:
I'm using fireb33 latest build, I used the cm11 for about 4 days and switched to jelly bean , the speed difference was there, I'm used it with stock kernel though.
[Samsung Galaxy Nexus] HellsFury:
Sorry for the noob question...I flashed r394 on to my Galaxy Nexus running CM 10.2 stable. Is there any way to set the kernel settings (governor for example) other than using the Franco.Kernel Updater app?
[Samsung Galaxy Nexus] erghetto:
trickster mod

you can download it from playstore
[Samsung Galaxy Nexus] hotrodwinston:
Read a few pages back and am a little confused - are there any versions of this kernel that work with shinyrom 4.4.2? If so which one?
[Samsung Galaxy Nexus] Edward Stanbury:
this will :P

http://d-h.st/LZO
[Samsung Galaxy Nexus] hotrodwinston:
Actually I had read about boot loops with the any kernel version - which made me have questions - flashed the fixed kk version no problem
[Samsung Galaxy Nexus] Edward Stanbury:
All good both will work fine from personal experience :P as long as we can all enjoy fancos goodness :D
[Samsung Galaxy Nexus] matdestr:
I have an xperia p with carbon rom (4.3) , will this kernel work ? Because I realy want to have the doubletap2wake function...
[Samsung Galaxy Nexus] Edward Stanbury:
ill simply say no. unless ya wanna soft brick ya phone ;) wrong thread buddy sorry there must be some other amazing devs in your neck of the woods ?
[Samsung Galaxy Nexus] The Gingerbread Man:
Look for stuff by fxp, doomlord and some call zdzihu (I think) they were best on x10. Be sure to use stuff for your specific device though as stuff from other devices won't work and will make it not boot up
[Samsung Galaxy Nexus] hotrodwinston:
Double tap to wake? That's not on Franco for gnex is it?
[Samsung Galaxy Nexus] The Gingerbread Man:
Not by default, there's an app for it I think. Search play store for key words
[Samsung Galaxy Nexus] lonnyrs:
Edward, maybe you or someone else can explain why I'm bootlooping after flashing this Franco kernel (r394)? It IS for 4.4.2, correct? I am running shinyROM, and it just loops. I've been out of the flashing game for several months, so maybe I have missed something along the way. Technology for these devices is advancing WAY faster than I can attempt to keep up.

Any help from anyone would be awesome! Or if anyone can recommend a kernel that works, I'm all ears.. Thanks guys..
[Samsung Galaxy Nexus] Edward Stanbury:
Hey bro some people have said the anykernel format doesn't like some ROMs for some odd reason, http://d-h.st/Wq4 this version is with the fixed ram disk give that a go many people say it still works as it should :) and its all good man were all here to help

And yep these are for 4.4.2
[Samsung Galaxy Nexus] ahmadairfan:
Yeah I experienced the same thing, sometimes it just bootlooping.

But thats a reasonable one, since [MENTION=4544860]osm0sis[/MENTION] tried to make a different method for Anykernel for r394, right?
[Samsung Galaxy Nexus] RandyRhoads1821:
where's the osmosis version? is it possible to put the link on the first page of this thread?
[Samsung Galaxy Nexus] abalam:
Just click on his profile and you see al the info

Sent from my Nexus⁴ machine
[Samsung Galaxy Nexus] osm0sis:
Really you just need to go to my Dev Host, http://d-h.st/users/osm0sis/

Or if that's too hard to remember, http://v.ht/osm0sis
[Samsung Galaxy Nexus] -totonio-:
Hi to all, I need to restore the phone to a friend, I've Installed 4.4 CM, but if i flash this kernel I got bootloop, my question is, is this kernel compatible with CM11 or I need to switch to another rom? Thanks ! :D
[Samsung Galaxy Nexus] NetBender:
No, this kernel is not compatible with 4.4 then you have to reflash the boot.img (extracted from the rom zip) via fastboot (fastboot flash boot boot.img).
[Samsung Galaxy Nexus] -totonio-:
Already did ;) anyway I misunderstood thank you!
[Samsung Galaxy Nexus] osm0sis:
Poor reading all around. :(
[Samsung Galaxy Nexus] vitalero:
Didnt we accept that both AnyKernal and osm0sis kk fix works with 4.4?

and he dont have to reflash via fastboot anything just easier to flash the 4.4 rom again with its default kernel then pick a kernel of his choice much more user friendly i think
[Samsung Galaxy Nexus] pkgnex:
I love this kernel and the Mpokang kernel for different reasons. If Franco, or anyone, could turn ASRAM back on in this kernel and do whatever the Mpo-dev did to speed up the RAM by 50% (RAM over-clock?), I'd never need another kernel update!
[Samsung Galaxy Nexus] NetBender:
I started to follow this thread a few days ago then i didn't know that AnyKernel and osm0sis works. Thank You.
[Samsung Galaxy Nexus] Schneewitzchen:
[MENTION=4544860]osm0sis[/MENTION]

I found an error while investigating catlog for another problem!

I've looked in init.rc, but there, no permissions are given to screen_off_max_freq. Also the right ownership isn't set!

I set this up manually to the file and no more errors in catlog. BTW i'm using your fixed KK Version.
[Samsung Galaxy Nexus] bigknowz:
Update coming?

Might be of interest, franco commented on other devices

http://xdaforums.com/showpost.php?p=49440955&postcount=12786
[Samsung Galaxy Nexus] Schneewitzchen:
THX nice to know
[Samsung Galaxy Nexus] Vekhez:
Cmon guys 10 more pages till 4460 :D our chipset :P
[Samsung Galaxy Nexus] osm0sis:
Nice catch! I must have missed that one when I was merging all the changes over to the kitkat ramdisk. :good: :)

---------- Post added at 08:28 PM ---------- Previous post was at 07:56 PM ----------

-kk is updated with that fix added to init.rc, a fix to tuna.fstab that might help with remounting system rw being finicky at times since selinux became enforcing (had to make a similar change on grouper awhile back), and updated busybox to 1.22 for whatever little that's worth.

http://d-h.st/users/osm0sis/fixed/
[Samsung Galaxy Nexus] The Gingerbread Man:
Franco's display app has been updated to work with gnex now http://xdaforums.com/showthread.php?t=2424467
[Samsung Galaxy Nexus] AndyYan:
To other users: looks like the flashable zip isn't updated yet, manually flash the boot.img if you want it.

Sent from Google Nexus 4 @ crSimple
[Samsung Galaxy Nexus] raymond1688:
Who is osm0sis?

Pardon me for my ignorance, who is osm0sis? (not in a rude way)

The reason I'm asking is because I had bad experience with CM and Franco of battery drain (this was just last month), so I moved to Cataclysm with leankernel. Now I think leankernel is creating problems with my WiFi, so I want to re-try Franco again this time with Cataclysm.

I see a lot of people here mentioning osm0sis' fix to the franco kernel, so I'm kind of confused.

Does osm0sis work along side Franco?

And how would I go about applying osm0sis' fix? I clicked into the webpage and it's a .img?

Sorry I tried searching through the thread by seeing when osm0sis joined this thread, but there was just too many pages I don't know where to find the information.
[Samsung Galaxy Nexus] Vekhez:
osm0sis is the maintainer of FK for the GNex now. When someone finds a problem with the kernel he's the one to fix it. Fransisco pushes the official release and he works his magic on the release to make a "fixed" version.

Basically he and Fransisco work together Franco pushes releases with osm0sis help.

[MENTION=4544860]osm0sis[/MENTION] any Jellybean love with that fixed kernel of yours. Have you got off the stock ROM..?!
[Samsung Galaxy Nexus] pkgnex:
I'm having even more problems with mounting rw with this version... Not sure why, but I can not edit/save any scripts in /etc/init.d. I tried a couple different utilities, and even though the folder shows as mounted rw, nothing will save.

Update: I'm fairly certain this issue is kernel or ramdisk specific. Using the same utilities, same busybox install, and either stock (Shiny rom) kernel or mpokang kernel that doesn't have a ramdisk does not exhibit the rw mounting issues.

Hope this helps narrow it down for you, osm0sis.
[Samsung Galaxy Nexus] Juice3250:
Where can I find the Franco kernel for 4.2.2? I'm on i515(CDMA) Verizon.
[Samsung Galaxy Nexus] raymond1688:
Thanks, that makes it clear.

I just have a couple more question.

1. What is osm0sis' fix? Is it a kernel that I flash like normal or is it a patch? I clicked into his file hosting site and saw .IMG files, but I'm not sure what they are, that's why I'm not sure if I'm suppose to replace it as a kernel or there are special procedures.

2. If the fix is a kernel, I install it with fastboot right? Seeing that are no .zip versions of it.

3. Are osm0sis' fix mandatory, meaning if I'm not comfortable with flashing via fastboot, would I run into major problems if I just use franco kernel?

Once again, really appreciate the community in helping noobs like me. Thanks.
[Samsung Galaxy Nexus] akash3656:
IMGs can be flashed using Flashify instead of fastboot. Its a nice app, i use it to also update the recovery installed on my phone. Kernels go to the /boot partition

I wish I could answer your other questions but unfortunately I'm not running Franco kernel at the moment so I am unable to help you.
[Samsung Galaxy Nexus] vitalero:
here is a nice guide

http://xdaforums.com/showthread.php?t=1956984

and also there is the Any-Kernel version which is a zip i am not sure what is the difference but ive seen people with 4.4.x using them so it looks legit[get your ROM backup on your memory anyway[ALWAYS]]

EDIT: and i found this one also

http://xdaforums.com/showthread.php?t=1508585
[Samsung Galaxy Nexus] raymond1688:
I've flash custom ROM and kernel before. What I'm not sure is whether osm0sis is a complete kernel, or an update patch that I'm suppose to add on top of Franco kernel
[Samsung Galaxy Nexus] Sik-1:
Lol its the same kernel, he only patched up what franco missed
[Samsung Galaxy Nexus] tylerdurden83:
Flashing this http://192.241.177.15/GalaxyNexus/4.4/ r394 boot img with flashify on top of cm 11 gets my phone stuck on boot logo

Pulled out the battery, turned the phone on in recovery, flashed the previous kernel that I was using (mopkang 1080p), but now it gets stuck on boot logo with that too...
[Samsung Galaxy Nexus] NetBender:
Flash the osm0sis' fixed kernel via fastboot: http://d-h.st/H8B
[Samsung Galaxy Nexus] tylerdurden83:
Cheers, working well now!
[Samsung Galaxy Nexus] Juice3250:
Is Franco kernel available on 4.2.2?
[Samsung Galaxy Nexus] NetBender:
Sure: http://192.241.177.15/GalaxyNexus/4.2/
[Samsung Galaxy Nexus] movelbit:
There are some paid users here waiting for the promissed update

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] sajty:
Ou.I guess,that you will be denounced by some users very soon :D
[Samsung Galaxy Nexus] movelbit:
Yeah. I know :)

Someone had to say it. Lol

Enviado do meu Galaxy Nexus através de Tapatalk
[Samsung Galaxy Nexus] sajty:
I understand.But posts like that are pointless,will have no effect.The only one can be,as i wrote,some more sensitive users will punish you ;).
[Samsung Galaxy Nexus] Vekhez:
really odd question, but does someone have all the franco.Kernel's that there has been?

Specifically the final R196 and the Final Jellybean 4.1.2 kernel :D
[Samsung Galaxy Nexus] osm0sis:
I can't seem to reproduce the issue anymore with SuperSU v1.91 - what about you? Maybe it was more of a root bug all along..

Between the link in the OP and http://minooch.com/franciscofranco/ that should be all of them.

Edit: Hmm, actually I take that back. Looks like Francisco cleaned up the server and everything before 4.2 support is gone.. I wonder if anyone mirrored them?

---------- Post added at 01:38 AM ---------- Previous post was at 01:01 AM ----------

Ah ****, I take that back, I can repro the rw issue again. It's so random though..
[Samsung Galaxy Nexus] Vekhez:
Yeah, they are all cleaned up, I did like 2 hours of searching, there are no mirrors.. So I guess Franco's the only one with em.
[Samsung Galaxy Nexus] AutomaticFailure27:
I had the same type of issue using Root Explorer. What I found (which not 100% sure if it is what fixed it but it worked after that) was I was able to mount everything to r/w but still not able to change it. I then backed all the way to root "/" and noticed that was still at r/o. After switching that, I was able to do pretty much everything again.
[Samsung Galaxy Nexus] Edward Stanbury:
after exploring the kernel worlds im back home again on FK (: only thing i miss is being able to mess with the voltage regulators i almost managed to double my battery life in comparison to what i get here :| ah well nothing compared in speed though! :D
[Samsung Galaxy Nexus] Vekhez:
Yeah, I never found FK to improve battery life, just speed.
[Samsung Galaxy Nexus] pkgnex:
Os,

Yeah, the r/w issue seems to be gone on my device at the moment - and the only thing I did was update SU to 1.91.

One odd thing, though... when rebooting out of recovery, I still get the "Root access possibly lost. Fix?" prompt in cwm. The affirmative response (which I never choose) points to "Yes - Fix root (/system/xbin/su)".

This has been happening for a while on your (recent) Franco kernels, but not on stock or other ram-disk free kernels, so I wonder if there is any relation, or if this helps you pin down any other issue.

BTW - Answering "NO" to the CWM prompt I listed above does not cause me to loose root.

Also, mounting the top level root directory r/w did not fix the issue for me when it was occurring, unlike what another user said. Root explorer would copy/save files in non-root directories, but not in anything normally mounted r/o.
[Samsung Galaxy Nexus] sd3993:
Could you post those settings please? :P
[Samsung Galaxy Nexus] namelesske:
Franco kernel for Galaxy Nexus is discontinued? Not so much updates since November 2013.
[Samsung Galaxy Nexus] pkgnex:
Not discontinued, just development has slowed. You'll see the same in every other G-Nex kernel forum because:

1. The Developer community has wrung just about everything possible out of the G-Nex kernel.

2. The 3.0 kernel hit end-of-life a month or two back (3.0.101)

3. The device is over 2 years old, and the Dev's have been putting more effort toward two generations of newer hardware that still have more room for improvement kernel-wise.

Franco has promised at least one more version, and I am confident it will come in the not-too-distant future. At this point, the various kernels out there are all quite similar and very good / mature. We should all relax and just be happy that we have the current crop of kernels to use rather than the 2-year old stock kernel the G-Nex shipped with!
[Samsung Galaxy Nexus] namelesske:
Hmm maybe "ignorance is bliss" the best way to handle when a device is end of its life :) That was sad moment when 3.x kernel EOL-ed and later Google Denied KitKat :(
[Samsung Galaxy Nexus] pkgnex:
Agreed - especially the Google KK denial for a device that still wasn't quite 2 years old. It sounds like 18 months is all the longer they plan to support devices now.

My plan from here out is to buy only "close-to-stock-android" devices with high sales volumes... in order to take advantage of wide-spread developer support and hope that I am able to keep the device still feeling usable for 6 - 12 months after the official OEM/Google support dies off at 18 months.

I have too many other things I want to spend my money on to justify buying a new phone / tablet for everyone in the family every 18-20 months!
[Samsung Galaxy Nexus] namelesske:
My device is just one year old. Cyanogen mod is the only rom witch has a good community based translator team so there is no foreign language menu points in menus and settings so it feels like more stock than others. I decided to use only stable builds, so I'm still on 10.2 :)
[Samsung Galaxy Nexus] omvir:
Off topic: osmosis, I read a while ago that you are an RN. Are you located in the states? If so, I have a question regarding Canadian RNs and what the process would be to work in the states? Do you know anyone who has gone through the process? I've searched this online but there are a mix of answers. Maybe you know more? Thanks.
[Samsung Galaxy Nexus] osm0sis:
Canadian working in Eastern Canada currently. I know a couple of people from my class that moved to The States to work. They need to write a transfer exam as far as I know, basically another licensure exam. I've heard it's easier than ours. :p
[Samsung Galaxy Nexus] hotrodwinston:
Hey [MENTION=1143630]osmosis[/MENTION] - shiny port for maguro http://xdaforums.com/showthread.php?p=49793715
[Samsung Galaxy Nexus] osm0sis:
Whaaaat that's definitely my next ROM! Thanks buddy!
[Samsung Galaxy Nexus] metalspring:
If codefirex does any builds soon they might be the best choice. I did a build for toro awhile ago and it was basically a highly optimized, super fast aosp since they haven't added many features back yet (and they usually keep things slimmed down anyway)
[Samsung Galaxy Nexus] Karlo666:
[MENTION=3292224]franciscofranco[/MENTION]

Does this kernel work whit OmniROM nightlies for GNex?
[Samsung Galaxy Nexus] Vekhez:
The official Franco one doesn't but the [MENTION=4544860]osm0sis[/MENTION] modded one works just fine.
[Samsung Galaxy Nexus] garuhhh:
thanks for the headsup [MENTION=1937895]hotrodwinston[/MENTION]! Running shiny now, no issues so far. I was from stock.

[MENTION=4544860]osm0sis[/MENTION], r394 working fine for shinyROM? i'm testing out the stock kernel's battery life before moving on to Franco just to have a point of comparison.
[Samsung Galaxy Nexus] vitalero:
the fixed osmosis version works awesome on 4.4.x

BTW how good is the Shine Rom ? using AOKP and its great is there really something better?
[Samsung Galaxy Nexus] garuhhh:
Yeah, I looked at the available fixed kernels from osmosis, then saw one that is for KK, I tried it, and so far so good.

Although, yesterday I was not able to get a GPS fix. Not sure if kernel or ROM issue. I was not able to test stock kernel with GPS.

I just wanted a ROM that is as close as possible to stock, and Shiny ROM promises that. How's AOKP?
[Samsung Galaxy Nexus] akash3656:
It's probably more on the ROM/phone side. After 2 years owning this device, I'll tell you one thing the GPS on this phone is quite playful with the user. Sometimes it will lock fine, then loose accuracy and loose a lock, sometimes it never locks even after 15 mins (outdoors, data on), and hardly it works fine. When it does work fine though, at very certain places while driving it will loose a lock or tell me I'm at a street far away from the current street. A nexus 4 and htc butterfly s do not have this issue though (tested them in the car together with my GNex).
[Samsung Galaxy Nexus] AndyYan:
Never had lost GPS lock before, of course I'm on Franco r394. When a loss of lock happens, try force stopping the app that's using the GPS and start it again, mostly works on my Photon Q.

And happy Chinese New Year to all, if that matters to you :)

Sent from Google Nexus 4 @ CM11
[Samsung Galaxy Nexus] akash3656:
Might be my phone derping. It has a lot of other derps too....

Happy Chinese New Year to you!
[Samsung Galaxy Nexus] skizofrenic:
I m tryin it right now it s simply awesome

Only thing is i had to use osm0sis 394fixed couse i was stucked in bootanimation with 394 downloaded directly from FKU
[Samsung Galaxy Nexus] duffymm:
Sorry for the Laziness ..... I'm on 4.3 google Stock rom and actually using official r394 franco kernel

Is there something more updated to use with the 4.3 stock ?

Is hard to follow the thread because of the CM11 / 4.4 versions mixed with the 4.3 ones.....

Thanks a Lot
[Samsung Galaxy Nexus] osm0sis:
I still have a fixed for JB up as well.
[Samsung Galaxy Nexus] duffymm:
Is this one ? http://d-h.st/wuZ ?

cwm-franco.Kernel-tuna-nightly-r394-JB.zip ?

Thanks Osmosis
[Samsung Galaxy Nexus] 47th_Ronin:
[MENTION=4544860]osm0sis[/MENTION]

Just wondering if the init.d scripts are as beneficial for kk as for jb. With all of the changes in code etc. I've been using the latest io script off and on but wanted to run the fkdt script set.

Thanks
[Samsung Galaxy Nexus] osm0sis:
Absolutely no need, actually. Everything important from the FDT work has long been added to f.K either via the ramdisk or hardcoded in the source. Some of the 975experimental and some of the 925vmsettings you could run if you like, since those were the only ones that remained too experimental to incorporate.

The FDT init.d script pack is a bit of a misnomer. It's not FOR franco.Kernel, but rather BY franco.Kernel and meant to bring the f.K experience to every other device/kernel. :)
[Samsung Galaxy Nexus] franciscofranco:
Pushed r395:

* Enabled ASRAM

* Enabled modules

* Ramdisk changes thanks to osm0sis

* Merged custom patches from my other devices

* Now it properly works on 4.4 custom roms

Happy flashings :)
[Samsung Galaxy Nexus] memaro_maro:
wow!!! first one!! waiting for a long time
[Samsung Galaxy Nexus] osm0sis:
Hell yes sir! Also bfq removed and row made default as mentioned I changed in the source way back here:

http://xdaforums.com/showpost.php?p=48062053&postcount=44215

Finally we're back on track from r392. :D

I'll try to get my AnyKernel version going in the next week or so, depending on how the broken leg is treating me.
[Samsung Galaxy Nexus] Vekhez:
Awesome!

I don't know if this has been said before, but would it be possible to have regulator voltages added in (or just UV the screen yourself) :D

Anyway, Thanks a ton for the new release!