yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] metalspring:
Isn't that the stock 4.3 or 4.2 kernel setting for hispeed_freq? The only issue I could see with it being set to 729 would be it might cause higher max frequencies to have lower performance than expected. Personally I usually have my max frequency at around 1500 with the hispeed_freq at 729 with no issues

Btw, looking forward to being able to use this kernel again and not having root issues with supersu. For some reason Franco is the only kernel I don't get a few random lockups and reboots on most roms
[Samsung Galaxy Nexus] osm0sis:
Have you tried my latest fixed yet? All reported root works perfectly on it vs. "original recipe."

http://d-h.st/users/osm0sis/jb4_3/tuna/
[Samsung Galaxy Nexus] metalspring:
Just installed and rebooted a couple tines and it seems to work now

Btw, what's the best read ahead buffer size value? I always heard it was 2048 but I'm not sure if it varies by kernel or I/O scheduler or anything
[Samsung Galaxy Nexus] osm0sis:
It varies by scheduler but we found the best middle ground for all was 512 and that's the default for f.K.
[Samsung Galaxy Nexus] SahilC:
Hey everyone!

I'm new to PA, and apparently they teamed up with franco.

Would you recommend the original franco, PA franco, os's mod, or the 'fix' posted on page 4339?

Thanks!

Nexus Prime, powered by CyanogenMod and LeanKernel.
[Samsung Galaxy Nexus] osm0sis:
Last I'd heard PA franco is very basic by comparison to his mainline kernel work. There is no osmod until we get some basics squared away again with the new rebase (ie. nothing extra to test), so definitely use my fixed version until Francisco can put out a new version with the fixes integrated. :good:
[Samsung Galaxy Nexus] Phazmos:
Fwiw - I set to 729 and never had any issues. I also usually set high speed delay to 60000, no problems
[Samsung Galaxy Nexus] metalspring:
Having some weird permissions errors with the latest fixed kernel and supersu

Root explorer not gaining root permissions on /system (can't mount RW/r, can't change permissions), plus another app (viper4android) can't write to /system either with root permissions

Switched to fancy kernel and everything works just fine
[Samsung Galaxy Nexus] JiroPrinz8:
Sorry for the noob question, is there an app to use to control the kernel?
[Samsung Galaxy Nexus] nickcct:
Franco kernel updater or trickster mod will do.
[Samsung Galaxy Nexus] JiroPrinz8:
Yep figured that out on the screenshots of the users.

Anyway, using r391 fixed, and do not have the su issues, running AOKP 9/28 official nightly.

Haven't had the chance to use this kernel for a whule so no feedback yet.

But as of now, I've already played with CPU frequencies and governors anf all that good stuff, and no issues as yet. Will report back if i see any.
[Samsung Galaxy Nexus] parkson:
Latest fixed 391 working great for me. No problems booting phone without being tossed back into recovery!
[Samsung Galaxy Nexus] osm0sis:
Here's the list we've compiled for [MENTION=3292224]franciscofranco[/MENTION] of what's missing in r391 vs. pre-rebase:

f.K tuna: hf 729 not 1228; cfq fea 335 not 328; bfq+quick tune; ?wifi pm fast; ?high perf sound; cpu temp+freq, gpu freq display;

Also, f.Ku: Volume boost still 0-3; some options don't work with other kernels (looking for internal bb?); hide color profile on front page if none selected; option to hide lean menu item;
[Samsung Galaxy Nexus] The Horak:
Hey guys, I'm so sorry if this is a stupid question. Does the latest r391 work on the Toro/CDMA Galaxy Nexus, or is this specific to the GSM?
[Samsung Galaxy Nexus] greyhd:
Works on toro/CDMA.
[Samsung Galaxy Nexus] ashclepdia:
no kernel is specific to ANY of the Galaxy Nexus variants.(should work perfectly fine on any toro/toroplus/maguro) no matter which forum here you find it in, if it's a kernel, ot should be just fine on any variant.(afaik)

that is why i come to this forum more often for kernel development vs toro forum, it's more active here.
[Samsung Galaxy Nexus] Khrushy:
Ok, I finally stopped being quite so preoccupied with that "real world" place and made the jump to 4.3. Anything else other than what's listed above that we're on the lookout for?
[Samsung Galaxy Nexus] ChazzMatt:
new 4.4 KitKat kernel for older devices?

Screenshots of KitKat running on Nexus 4 for testing purposes. Yes, ALL Nexus devices are designed to get the latest Android OS automatically, thus Google needs to test on their older devices -- but here's one interesting nugget of information (if true):

This is one of the most important points in the article, and is based on speculation 4.4 KitKat will be released with Linux 3.8 kernel. Has anyone heard any more about this?

______________

Even though I own two gen3 Galaxy Nexus currently running with 4.3 JellyBean (actually SlimBean 4.3), the KERNEL is still older version than the gen4 Nexus 4. While Google makes the newest OS available for Nexus devices, they never released a newer kernel for the processors on older Nexus devices like ours. Sure, we are running Franco custom version of that kernel, with increased performance and battery saving tweaks, but it's still based on the original kernel (3.3) of our gen3 Galaxy Nexus. Gen4 Nexus 4 got a whole new kernel (3.4), which is not compatible with our processors.

(Yes, I'm aware of nascent developer efforts to make the Linux Android 3.4 gen4 kernel work with our Galaxy Nexus -- but it's been a year already, so we aren't going to discuss that.)

A NEW 3.8 kernel compatible with our gen3 Galaxy Nexus would that complaint moot. I am upgrading to the Nexus 5 when it is released, but my wife still likes her Galaxy Nexus. Would be nice to have BOTH Nexus 5 and Nexus 3 running 4.4 KitKat with new kernel.

I know Franco tends to drop development on Nexus devices more than one generation past (keeping dedicated support for the newest and "part time" support for 2nd newest) -- but many other developers just move on to new devices, totally abandoning developer efforts for any devices except the newest. So Franco is more generous. But if it's the SAME BASE KERNEL that situation might change, and older devices could be supported longer. New life for older devices...

Gen3 Galaxy Nexus could get a whole new kernel next month? Again, this is not confirmed -- it would depend on Google using 3.8 kernel in 4.4 KitKat... but I hope it's not ignorant speculation.

Of all the leaked 4.4 KitKat (code name keylimepie) screenshots, have any been with a 3.8 kernel? or just same 3.4? :confused:

Still this article is interesting for what 4.4 KitKat will bring:

_______________

http://au.ibtimes.com/articles/511621/20131005/android-4-running-lg-nexus-10-new.htm#.UlAd5VCkrzM
[Samsung Galaxy Nexus] osm0sis:
The fact that there's a lime in there makes me doubt that article overall.

Anyway there were rumors that new Bluetooth LE (or whatever it's called) for 4.3 would necessitate a bump in the kernel for the GN to 3.6 I think, from the 3.0 we're actually on (for comparison the N7 '12 is 3.1), but this never happened.

I have a feeling the GN won't see KitKat at all officially so I wouldn't get my hopes up.
[Samsung Galaxy Nexus] The Gingerbread Man:
Be optimistic ;)
[Samsung Galaxy Nexus] ChazzMatt:
I thought we were on kernel 3.3. GNex is on kernel 3.0? You know more than me on this subject.

As for keylimepie references, Google called it that internally for the past year to even fool employees. So it's baked into the testing software.

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] Sik-1:
No we have been on 3.0 for the longest, hence y all the latest kernels are now on 3.0.98 , we haven't reach the nexus7 '12 edition of the 3.1 kernel
[Samsung Galaxy Nexus] Fenvarien:
3.0.99 was released today, but the 3.0.X kernels will be EOL within a few weeks. https://plus.google.com/app/basic/stream/z12gxfjjqyzrjl45c04cg5lwhweuhxjjtno0k

Gesendet von meinem Nexus 4 mit Tapatalk 4
[Samsung Galaxy Nexus] dpaine88:
I just wanted to post and say 14.1 is running FINE for me. No issues at all.

I am running the kernel with 100% STOCK VALUES. No gov/freq/UV changes.

I am using the CDMA ROM by Lou called Redemption ROM.
[Samsung Galaxy Nexus] jhericurls:
Let's hope he has a nandroid back-up, you will be surprised the number of people who haven't.

I think kernel #14 needs to be removed or have some kind of warning, as it's too easy to boot loop and without a back-up you are in trouble.
[Samsung Galaxy Nexus] damigor:
tHE SAME PROBLEM

Hi guys!

I have already flash this kernel .

Results :

- Bootloop

-No SD Card Mount

-doesnt see SD Card

I am not able to connect my phone to the computer.

ADB Push doesn't work !

Hou I can restore an old version ??

Regards!
[Samsung Galaxy Nexus] Nebucatnetzer:
We already found out that it doesn't depend on your settings, frequencies, voltages, rom, radio etc. the issues are coming from the kernel.
[Samsung Galaxy Nexus] Elganja:
who is we? all i see is people complaining but not posting what UV, Overclock/Underclock they have.

I also see people who haven't messed with any of that, and have no issues. I'll go back through the posts again to see if I can find a person who is 100% stock kernel settings to see if they had the bootloop problems.

edit:

I'm not saying there isn't an issue with the kernel, but we can help find what makes it unstable for some, and stable for others. The UV, OC/UC, etc... are all variables that can cause issues IMHO
[Samsung Galaxy Nexus] kecinzer:
Well, I think there is something wrong with version 14.x related to comments.
[Samsung Galaxy Nexus] PapaWangsta:
Hey guys, the hotplug is enabled, and still shows 0? How do I get 1? :confused:
[Samsung Galaxy Nexus] tumman:
Phone signal drop randomly after upgrading to 14.1 XXKK6 with Open Gang Project build 20 now I'm back to 13.1 no issue.
[Samsung Galaxy Nexus] davidbb:
running 14.1 with stock values here. no bootloops. in fact i tried all the 14.x releases and they all booted fine.
[Samsung Galaxy Nexus] Elganja:
People should post at a minimum the following when reporting a problem..

ROM:

Kernel:

Clock Settings:

Voltage Settings:

Governor:

Radio:

GSM/CDMA:

Bootloader:

Hotplug:

And for further help franco, the logs he requested may also be useful for him.

e.g. (mine)

ROM: Codename Android 1.2

Kernel: Franco #14.1

Clock Settings: Stock, 1200Mhz-700Mhz

Voltage Settings: 1125mv, 1000mv, 900mv

Governor: Stock, conservative

Radio: EK06/EK04 (CDMA/LTE)

GSM/CDMA: CDMA

Bootloader: PRIMEKL01

Hotplug: Enabled
[Samsung Galaxy Nexus] dcoy82:
Running CDMA Gnex with CND 1.2.0 ROM with Franco 14.1 Kernel. Running Kernel at 350/1200 Conservative governor with hotplug enabled. No UV being used as when I tried UV on #13 I got a terrible boot loop and haven't tried UV ever since!

Phone is running faster/snappier than ever before with any other ROM/Kernel I've tried in the past but I have noticed a little reduction in battery life than prior kernel releases. In all honesty, I'll take the performance over battery life on this release as it's snappy as hell. I'm just wondering if the extra battery drain is caused from the 350/1200 Mhz jump and low usage of 700/920 MHz?

Either way, keep up the good hard work Franco out of all the many kernel's I have tried yours seems to be most stable and best performance overall.
[Samsung Galaxy Nexus] rickh925:
Don't loose any sleep over it. Anyone flashing bleeding edge kernels should know stuff happens and how to fix it. Keep up the good work.
[Samsung Galaxy Nexus] VoicesX:
I have problem with #14.1:

I change UV setting (the same that i had with #13.1) and i get inmediatly reboot.

Go back to #13.1.

PD: SetCPU use.
[Samsung Galaxy Nexus] franciscofranco:
Just released #14.2, hope it cuts it for the people with stability issues.
[Samsung Galaxy Nexus] Elganja:
thanks franco!
[Samsung Galaxy Nexus] AzzaD:
as always, cheers man - gonna throw some money your way tomorrow!
[Samsung Galaxy Nexus] energie:
Il keep 14.1 no problems for me
[Samsung Galaxy Nexus] Puzzlegirl:
No problems here on 14.1 after signal drops on 14. All settings as per Franco, running latest Manhattan ROM. Battery life appears to be better than 13.1 so far. Thanks Franco, hope you aren't disillusioned with everyone's problems.
[Samsung Galaxy Nexus] saywhat4118:
No problems here. Im on 14.1 running AOKP 20 baseband kk6. Underclocked as well and here are my voltage values. Mind you I have been using this setting over night now with no issues and used the same setting on 13.1.
[Samsung Galaxy Nexus] dyndragon:
For everyone's information, and please try to replicate, but it appears that the latest CM9 kang from this morning (update-cm-9.0.0-RC0-GN-KANG-signed.01262012-0810.zip) (euroskank CM9 kangs) does not work with Franco's kernel. I'm just stuck at the boot animation.

Probably due to this recent change?

Tuna: Update kernel to 3.0.17
[Samsung Galaxy Nexus] The Gingerbread Man:
So if we do get official kit kat it should mean a bump to at least 3.1 :thumbup:
[Samsung Galaxy Nexus] thegtfusion:
the chance that wwe will get kitkat is very small... so i started to save for n5 :D
[Samsung Galaxy Nexus] The Gingerbread Man:
You say that but the nexus s did make it up to official jelly bean 4.1.2 from 2.0 / 2.1 I think. I don't know if they got kernel update but if someone were to check back on that it might give an indication if Google did update nexus s kernel it might possibly had plans for updating ours. If they didn't we may not see a brand new one but perhaps some kind of patched one
[Samsung Galaxy Nexus] Godra:
Only one problem. Nexus S started with 2.3
[Samsung Galaxy Nexus] cmstlist:
Nexus S was released around December 2010, and the first OS update that it failed to receive (4.2) launched with the Nexus 4 in November 2012. Hence the support cycle ended in just under two years, same as with the Nexus One.

If the GNex gets 4.4 it would break this pattern, but I have a feeling it won't. Frankly I'm ready to junk this phone anyway, but it's still kinda sad if no Nexus device can ever expect more than two years of official support.
[Samsung Galaxy Nexus] bigknowz:
Google is trying to lessen fragmentation with 4.4, so my bet is kit Kat for Gnex. Meanwhile, thumbs up to osm0sis, newest 391 is amazing.
[Samsung Galaxy Nexus] okanb3:
Newest ? Can you please give a link?
[Samsung Galaxy Nexus] creeve4:
http://d-h.st/users/osm0sis/?fld_id=23509#files
[Samsung Galaxy Nexus] okanb3:
Ah i'm using this also, too. I tought osmosis released a new version

Galaxy Nexus cihazımdan Tapatalk 4 ile gönderildi
[Samsung Galaxy Nexus] h1ghland3r:
One question, I'm with Franco r391 and I've changed some configurations (like colors) in Franco Kernel App. If I install the osm0sis r391 by CWM, I'll keep my configurations in Franco Kernel App?
[Samsung Galaxy Nexus] creeve4:
One more request for f.Ku: read ahead buffer size adjustment.
[Samsung Galaxy Nexus] The Gingerbread Man:
Well thats my memory deteriorating then lol

I see, thanks, I haven't spent a great deal of time looking over update patterns. Anyway even if we don't get it there is always roms. You should see me on the n5 forums anyway as I plan to get one at some point anyway

This is some good news that may help persuade others to join the xposed framework, this post is from the dev of a module called gravity box. This is useful for instance to lock apex in memory to reduce redraws or those who like noozoxcide but don't like the constant ongoing notifications with these apps

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

:thumbup: :)
[Samsung Galaxy Nexus] Fenvarien:
My feeling is that the GNex will receive some tasty KitKat as a final update! :good: :)
[Samsung Galaxy Nexus] osm0sis:
I likely did. ;) Update to make sure.

---------- Post added at 06:33 PM ---------- Previous post was at 06:32 PM ----------

But if they give us KitKat then they also have to support all the dot releases down the chain... I'm thinking this is more than they want to commit to for a 2 year old device.
[Samsung Galaxy Nexus] ChazzMatt:
It's just very ironic that 4.4 is touted as being ideal for older devices (even running on 512MB RAM) and Google then won't support their older devices -- which could receive it automatically. :)

_________

Sent from my Galaxy Nexus i9250
[Samsung Galaxy Nexus] The Gingerbread Man:
True as nexus s was left at 4.1.2 while not too long after we all went to 4.3 and still labeled as jellybean. Now a high percentage of modern devices is on 'jellybean' Google is ready to roll out of station with a new os. It could swing 50/50 here tbh.

On an unrelated note *excuse the pun* I think I talked my gf out of getting a note 10.1 and into getting a nexus 10 for her b day in couple of months. After me telling her that basicly every single bit is better and also its like near enough £100 cheaper she started listening lol
[Samsung Galaxy Nexus] osm0sis:
Haha talked my mother and father into a new Nexus 7 2013 to replace their aging Kobo. And they both use iPhone 4's but are now thinking they'll go Android for their next ones. :D

Already looking forward to going home at Christmas to visit and messing with the N7'13.
[Samsung Galaxy Nexus] -Jesco-:
cant wait to see osm0sis-ed franco over at N7 2013 thread :P
[Samsung Galaxy Nexus] osm0sis:
Haha not likely since I won't have it full time. The Franco's Dev Team init.d scripts still apply though. :good:
[Samsung Galaxy Nexus] DoesntPostAThing:
I'm looking forward to getting a Nexus 5 as well. The only reason I kinda left Franco kernel was because 4.2 was just atrocious, and I had to stay on as stock as possible for the best results. I loved Franco on 4.1, looking forward to that again on 4.4 with a Nexus 5! As for now, how's Franco with AOSPA? I'm looking to go back to my old 4.1 combo that absolutely rocked. Right now running the PA kernel (based on Franco, I think?) and it's quite awesome.
[Samsung Galaxy Nexus] osm0sis:
The N7'13 LTE (deb) just got a 4.3.1 OTA. I'm thinking the GN (maguro) will get this too around the time KitKat launches, and that'll be the swan song OTA much like JZO54K 4.1.2 was for the Nexus S (crespo)'s official support.

Also just learned the N5 is going to be hammerhead (catching up on my rumor mill reading :p). Glad they're sticking with the amusing fish names still; flo/deb had me worried. ;)
[Samsung Galaxy Nexus] The Gingerbread Man:
Someone posted this which I think nearly all but officially confirms rumours https://www.digitec.ch/Startseite.aspx?param=details&wert=283007 4.96 1080p screen, 2.3 snapdragon 800, LTE , 8 MP camera
[Samsung Galaxy Nexus] Khrushy:
If the stats are accurate, and I'd be surprised if they're not, then I am definitely making the jump to one of these.
[Samsung Galaxy Nexus] The Gingerbread Man:
http://www.phonearena.com/news/Nexu...t-on-a-phone-Lytro-like-functionality_id47900 is another juicly one. Mems camera, focuses much faster and uses less power
[Samsung Galaxy Nexus] DoesntPostAThing:
I doubt it's going to have the MEMS camera. Leaks have disproved that and instead points towards 8 MP OIS camera, which wouldn't be too bad.
[Samsung Galaxy Nexus] franciscofranco:
r392:

* Fix SU problems. If your SU was broken before flashing r392 you gotta re-install it regardless. Should work fine with superuser and SuperSu (tested SuperSu and works fine). Let me know if it is otherwise

* Add the memory reclaim feature from mpokwsthsand boype (reclaims 50Mb from the YUV Tiler)

* Add a proper touch boost implementation 100% on the Kernel side. It boosts the CPU to 1GHz on touch for at least 250ms = 0.25s. The PowerHal is disabled since this implementation works only from the Kernel side. Interacting with the device should be smoother. I merged this from my work on the Nexus 4, only adapted to work in this Kernel touch driver
[Samsung Galaxy Nexus] nuchdog:
Not sure why this doesn't happen anymore, but Francisco, you get a gold star for the day!

Maybe, I'm just getting old...

This post was sent through the tubes for your enjoyment! now Free
[Samsung Galaxy Nexus] osm0sis:
Looks like you fixed SuperSU by just putting the install-recovery.sh service back into init.rc? The combined init.superuser.rc fixes it too, SuperSU just needed to be first. :good:

The script you changed to fkbaks from fkbak will result in a second backup file of the wrong powerhal on devices that already used f.K. ;)

Also you forgot to add back in init.d support and timer slack when you reverted init.rc. :eek: :)
[Samsung Galaxy Nexus] abalam:
OsmOsis gonne fix this hehe...:cool:
[Samsung Galaxy Nexus] osm0sis:
[MENTION=3292224]franciscofranco[/MENTION] Don't think this got seen either. :good: :)

---------- Post added at 04:13 AM ---------- Previous post was at 03:58 AM ----------

Yip yip. :p

http://d-h.st/users/osm0sis/jb4_3/tuna/ One second, just noticed the powerhal wasn't actually getting disabled. Fixyfixing. Okay we're a go again. :D

There's weird stuff going on with the interactive tunables in f.Ku, like them populating with an old entered value when you go to edit (or nothing at all if you've never changed them before).

And it seems like interactive is missing io_is_busy now, though all the other schedulers seem to have it and you still have it in init.tuna.rc... [MENTION=3292224]franciscofranco[/MENTION] Is this intentional? Also please let us edit voltages to a specific value as well. The 990 +/- 25 for IVA is funky when I know that I can take mine down to 825mV safely.
[Samsung Galaxy Nexus] abalam:
Jiphaaaa ... he does it again hehehe...:D:D
[Samsung Galaxy Nexus] bvt-1:
r391 was as fast as a flash :good: hope r392 ist fast, too ;)

One stupid question, because my english isnt good its hard for me to read much posts and didnt find it in OP ...

On which MHz is GPU with r391/r392? 307 or 384MHz ... TricksterMod doesnt show me an option ...:confused:
[Samsung Galaxy Nexus] TunedFish:
384
[Samsung Galaxy Nexus] osm0sis:
GPU/CORE are just like CPU/MPU in that the frequency changes to meet demand. In stock Google kernel the

max

is 307MHz, in f.K it is 512MHz since Francisco cleverly figured out how to make it stable on all devices. :good: :)
[Samsung Galaxy Nexus] Schneewitzchen:
@ Os

Could you check the

--> vm settings

min_free_kbytes is set to 1442 instead of 2884

swapiness is set to 60 instead of 0

--> fs tweaks

lease-break-time is set to 45 instead of 10

--> entropy tweaks

read_wakeup_threshold is set to 64 instead of 128

write_wakeup_threshold is set to 128 instead of 256

correct me if the tunables weren't the last one you published as winning.
[Samsung Galaxy Nexus] osm0sis:
Franco never implemented the 2884, and the other 4, which he did, are fixed in my fixed version. :p
[Samsung Galaxy Nexus] Schneewitzchen:
That was strange. Before i controlled the values i flashed your fixed version through fk app.

Seems that the fk app hasn't flashed the kernel properly.

Now i flashed your version through cwm and all values work properly.

Thx for your quick response & keep up your great work!
[Samsung Galaxy Nexus] GamaX320:
why touch control cant find modula on latest franco???
[Samsung Galaxy Nexus] odavans:
Ask in TC thread
[Samsung Galaxy Nexus] pkgnex:
No more 1080p

I know "big-mem" is flavor of the day, and I personally don't mind the trade-off, but it's probably worth noting in the OP that this kernel no longer allows 1080p video recording due to the RAM reclamation code...
[Samsung Galaxy Nexus] -Jesco-:
i believe 1080p works here , maybe im wrong but this is how pa reclaims mem too , no broken 1080 on pa kernel
[Samsung Galaxy Nexus] DoesntPostAThing:
Just tested 1080p recording on r392, works just fine.
[Samsung Galaxy Nexus] Bl4ck3urn:
Yeah 1080p recording works more than fine.
[Samsung Galaxy Nexus] siddardha21:
Fantastic kernel. Thumbs up for franco and osmosis for uploading fixed version. The amount of free ram without breaking full HD or anything is just amazing. Thank you so so so so much franco!!! And osmosis too. :thumbup:

Edit: battery life looks good too nd with all the apps like fb, gapps, whatsapp etc running theres 250+mb free ram. Which is very impressive.

I'd like the kernel this way without disabling anything that's actually meant to function. Like 1080p etc. Cheers!!