yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] Raijin:
Days ago I made a post saying that my GN had the eMMC brickbug (I am suspicious of my bad use ofLagFix). Tomorrow it will come and will be for my brother.

Now I have a Nexus 4 and I am very happy with it. Miss the AMOLED deep blacks a lot, but love the design, smoothness, powerful hardware, touch sensitivity, light colors in screen, camera...

Osm0sis, what scripts of your Dev-Host can be used in N4? I think iosettings yes, but VM tweaks, lowmemorykiller and others are GN specific. But I will wait for your response. And please, update them to the new tweaks included in Osmod. :)

I don't want to go without thank the help you guys gave me. Specially Osm0sis. ;)

There was a lot of time reading GN Franco topic. I will maintain it in Subscribed topics. Will miss you all.

Regards!
[Samsung Galaxy Nexus] osm0sis:
r384-osmod now up with the newer, slimmer busybox binary (for whatever that's worth), westwood TCP CAA by default (since Franco recently did this over on grouper), and the changes to the vm tunables Franco's Dev Team has in the final rounds of testing (basically just reverts them to their Android defaults except for a couple differences).

http://d-h.st/users/osm0sis/osmod/

If you're running any Franco's Dev Team init.d scripts you can/should remove them if you're running the above, since it's pretty much all included. We are also in the final rounds of testing lmk tweaks (in 925vm), but I left those out since we're a little less sure about them.

When in doubt, use my Kernel Emergency Settings Reset Zip to make sure you're running clean from control app and init.d interference.

---

Please test this vs. "original recipe" r384 and let us know which feels better. :good:
[Samsung Galaxy Nexus] njiki11:
How do you use osmod?
[Samsung Galaxy Nexus] osm0sis:
Hey! Thanks for the kind words, and sorry to hear about your GN. All those scripts are actually intended for any device you want to try them on, but especially Nexus devices. [MENTION=4828198]malaroth[/MENTION] just dropped by the other day to say they work great on his new S4. Give them a try on the N4 and let us know how it goes! :D

Oh and it goes the other way around: scripts first, then osmod from those scripts once the tweaks are tried and true. So they're all matching, except for the stuff which may need a bit more work that I already mentioned. :) :good:

Yeah as far as all-in-one score benches go AnTuTu is fine. 3dmark is a definite stress test, and even Nenamark2 has its value.

It's a kernel image. So you flash it. There are many ways: fastboot flash boot. f.Ku backup+restore (via /sdcard/kernel_backups/). rename to boot.img and put it in the official r384 zip then flash in recovery. Flash Image GUI is an older app option, or Christian Göllner's new app Flashify looks fantastic. Gotta love Christian's work, plus he's a good friend of Francisco's from back in Portugal. :)
[Samsung Galaxy Nexus] Raijin:
Thank you Osm0sis one more time. :)

Regards!
[Samsung Galaxy Nexus] njiki11:
Thanks man, appreciated that!
[Samsung Galaxy Nexus] designori:
It works great. Very smooth and responsible!! thx, osm0sis!

Anyway what is your recommendation for scheduler? and your bfq tweak still works?
[Samsung Galaxy Nexus] misterk267:
Oh yeah. 384 osmod is incredible with Purity 5.7. The speed is just ridiculous. :D
[Samsung Galaxy Nexus] kaluoshi:
My wake up present. Thanks guys :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] Syfer_Fever:
using r384-osmod on MIUI 3.7.5 it feels a slightly improves performance speed, but still not smooth as AOSP based but i'm pretty happy, thanks to all :)
[Samsung Galaxy Nexus] mpokwsths:
These improved RAM timings have done their job.

Franco's kernel faster than ever!
[Samsung Galaxy Nexus] d4nteps:
Is there any possibility to control the vibration strength? :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Godra:
No
[Samsung Galaxy Nexus] creeve4:
Do the newer kernel versions have trimming enabled for system, data, and cache?
[Samsung Galaxy Nexus] UlbaWan-:
I've installed your version after used your "Cleaning scrpit" and in some days i'm gonna test the original version and tell wich I prefer :) But just to be sure about the difference, your version include all the configuration that you've done on the original kernel ? No need to use franco's app to configure the frequencies, gamma colour, governor,... ?

Because if I test the two one, I need to test with the same configuration :p
[Samsung Galaxy Nexus] vlc_marcos:
so still regarding his question. is not needed to activate nothing more after install the kernel. no script nothing? sorry if is a stupid question
[Samsung Galaxy Nexus] Coolgoly:
You don't have to do nothing after flashing kernel.
[Samsung Galaxy Nexus] ChazzMatt:
BFQ?

Do either of these R384 kernels have the winning tunables for BFQ yet? Before this the I/O schedulers tweaked were just Deadline and CFQ. Any of the others had to be done by scripts, but

BFQ was very promising

-- just had not been hardcoded yet.
[Samsung Galaxy Nexus] AndyGnex:
I still had to enter my BFQ settings manually, ( hate scripts :p ) so i guess they haven't hardcoded it yet. But yeah, BFQ is great :D
[Samsung Galaxy Nexus] osm0sis:
bfq has been hardcoded. Tested it myself. And yeah same settings are default except for Westwood. Thanks for testing guys. :good:
[Samsung Galaxy Nexus] AndyGnex:
The hardcoded settings are same values as tested with exception of the last variable is it? the one with 7000 value?

If so, then it must have been because i didnt run the reset script/clear app data.
[Samsung Galaxy Nexus] jpin321:
I'm out kernel shopping. I feel dumb, how do I flash this? Do I download a nightly image and fastboot it?
[Samsung Galaxy Nexus] bigknowz:
Flash

Yes, but make sure its the proper version as the OP states

r384 -> 4.2.2 | r364 -> 4.2 | r300 -> 4.1
[Samsung Galaxy Nexus] jpin321:
Ok, does anyone zip these up so they can be flashed without my computer? I'd like to flash this before I get home.
[Samsung Galaxy Nexus] Coolgoly:
Download zip version instead img.
[Samsung Galaxy Nexus] jpin321:
My apologies I didn't see the zip directory at the bottom. Thanks for the help.
[Samsung Galaxy Nexus] odavans:
ZIP

http://minooch.com/franciscofranco/Galaxy%20Nexus/JB/JB-4.2.2/zips/
[Samsung Galaxy Nexus] blueren:
Fallen back on my gnex since I successfully bricked my n4.. again.

Anyway, could someone point me to better tuning values that flatten out the slight micro stutters that lingering around?

Also, where can I go looking for user defined color presets.. Any pointers will be very helpful :)

Sent from a Nexus
[Samsung Galaxy Nexus] Bl4ck3urn:
The search button is your best friend.

Anyway http://xdaforums.com/showthread.php?t=1790325
[Samsung Galaxy Nexus] osm0sis:
Yeah that last one didn't work for everyone (felt worse than default to some) so it was left out of the final quick tune values.
[Samsung Galaxy Nexus] diSke:
Some questions regarding this kernel,

- Is it best to turn on smart reflexes? Because I've read something in the changelogs

that some Frequencies didn't calibrate properly with smart reflex on.

- I've used Fancy for a little while and it had multicore power savings. Didn't find this setting

in trickster mod. what value is it default? Off, normal or aggressive?

Thank you!
[Samsung Galaxy Nexus] NutellaBanane:
if you changed any voltages you should turn smart reflex off, so that they're actually used

and i think mps is set to off on default

Send from a piece of wood
[Samsung Galaxy Nexus] Edward Stanbury:
Smart reflex is hard coded disabled atm until it can be improved and multi core power saving is not enabled in this kernel :)
[Samsung Galaxy Nexus] diSke:
Thank you both very much for the information :)
[Samsung Galaxy Nexus] osm0sis:
Whoops just noticed I totally linked the Franco's Dev Team forum incorrectly in my osmod posts. Here it is properly:

https://groups.google.com/forum/#!forum/francosdevteam

LOTS of good reading for any interested in the long process of research and subjective testing of all these fine tunables. :)

Edit: Also w00t! Filled in another block on my Thanks Meter. Thank YOU all! Only 3000 and then another 2000 to go. :laugh:
[Samsung Galaxy Nexus] franciscofranco:
Multi core power saving? Another buzzword? Sched MC is completely broken im the 3.0 branch, its just another buzzword that others use to help them "shine".

Smartreflex is disabled since forever. Its a bit broken as well. I hardcoded the voltages long ago thats why this is probably the only Kernel for the GN that every user can have a stable device running the GPU at 512MHz and stable when overclocking the CPU.

Yeah you guys are awesome, I would pay a few beers each if we'd met in real life.
[Samsung Galaxy Nexus] kaluoshi:
-your kernel doesn't need more stuff like that as you're doing for the app dude :)

-what a great guy that give and deserve respect! :thumbup:

that's the awesome franco team, people not virtual ghosts :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] designori:
appreciate, boss!!!
[Samsung Galaxy Nexus] sci05:
Latest update is blazing fast but I noticed my phone got really hot while playing games (47F) where as the previous build did not.

Anyone else experience this? I've gone back to the previous for now.

In running stock 4.2.2

Edit: sorry. Kernel works fine reflashed without clearing cache and now it seems fine. Odd.
[Samsung Galaxy Nexus] thisguy23:
So how do you feel about regulator voltages? Let me clarify. VAux_6030 runs at 3.1v and with other kernels we can turn this down to 2.5v, if our device can handle it.

Since the screen uses the most power in the phone and since this phone doesn't get the greatest battery anyway, would this be beneficial to add as a feature?

Thanks for your input. This is something I've been wondering for a while.
[Samsung Galaxy Nexus] nikodr:
I was on 382 version on Paranoid android 3.65 on samsung galaxy nexus maguro,all was ok,but after updating to 384 version of kernel,device was not put on deep sleep mode correctly,i used franco's utility to have beastly battery settings,but if on 384 then deep sleep was not used on the cpu spy,i was getting lots of usage on 1036 mhz,i reverted back to stock kernel from franco utility,(a backup i made) and then went to recovery and flashed 382.All is ok now.And battery issues are gone.

Did i do something wrong?

In order to flash a custom kernel,the best option would be to go back to the rom stock and then flash anything above it?
[Samsung Galaxy Nexus] kaluoshi:
no problem here on 384, try as you said a clean install of everything :thumbup:

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] Edward Stanbury:
ditto its running like a champ :D
[Samsung Galaxy Nexus] diSke:
Probably another buzzword idd. That cleared it up for me. Thank you!

I have to admit, probably one of the best kernels out there. Keep up the good work :good:
[Samsung Galaxy Nexus] Mike318:
Sorry for a noobish question... but since there are a number of available governors and CPU must scale up to meet demand, is the voltage we set stable at the highest frequency (since the stability test punishes it) or are we setting a frequency for each available clock?
[Samsung Galaxy Nexus] bigknowz:
Wifi Optimization

Is there a noticeable difference in battery drain with Wi-Fi optimization off?
[Samsung Galaxy Nexus] Sik-1:
Honestly not that I have noticed ever
[Samsung Galaxy Nexus] osm0sis:
And that weird Wi-Fi drop while asleep even when not set only occurs when optimization is disabled.
[Samsung Galaxy Nexus] Syfer_Fever:
i thought the WiFi turn-off when asleep is a known issue in Android 4.2.x?
[Samsung Galaxy Nexus] bigknowz:
Wifi Optimization

If I recall correctly, you also suggest having optimization off. My issue - when arriving home / work, phone does not connect to wifi until I wake it, currently optimization is on.
[Samsung Galaxy Nexus] gpzbc:
Now I am confused. Should wifi optimization be enabled or disabled? And should "keep wifi on during sleep" be set to always?

Thanks!
[Samsung Galaxy Nexus] ChazzMatt:
These color values work very well for my Galaxy Nexus....

Using the Color Control settings in the Franco kernel app:

COLOR MULTIPLES

RED 290

GREEN 300

BLUE 320

RGB GAMMA

RED 0

GREEN 0

BLUE -5

OMAP GAMMA INTERFACE

1.2
[Samsung Galaxy Nexus] osm0sis:
Nope actually I've always said to "set them to something other than what they currently are, and then set them to the defaults" to fix the issue, with most, if not all reporting success. The issue seems to be that what it's telling you is set either isn't actually set, or isn't being followed. Setting it again and sticking to the defaults seems to resolve it.

Defaults are "Keep Wi-Fi on during sleep" set to Always, "Avoid poor connections" disabled, and "Wi-Fi optimization" enabled. These are what I use with no issue.
[Samsung Galaxy Nexus] x3m.zone:
Simply the best kernel for GNex. Thank you dev.
[Samsung Galaxy Nexus] osm0sis:
So. Has anyone had the chance to formulate an opinion on r384-osmod vs. r384 "original recipe" ? I'd love to hear how the vm settings are affecting feel for the population-at-large, since they're the only real change. :)
[Samsung Galaxy Nexus] bigbear6708:
Saw the op updated so I DL the original.. No problems yet, on slim. I'll look back for osmod and give it a try to compare
[Samsung Galaxy Nexus] Efrenjr15:
both are smooth and fast as F*** ? lol :p
[Samsung Galaxy Nexus] AutomaticFailure27:
One thing I have noticed is my battery seems to drain a bit fast on r384. I've checked for running apps and things of that sort, nothing stands out of the ordinary. It does seem to drain faster when on wifi (which I had this issue before, but was all fixed earlier)

I am running osmod r384, cleared out my init.d, along with some other files AK kernel left behind in the /data/ak folder. Seems everything is pretty much stable on r382.
[Samsung Galaxy Nexus] njiki11:
Same here!!
[Samsung Galaxy Nexus] wavedashdoc:
On normal 384. Best Battery I've gotten with Franco. Vzw PA 3.65
[Samsung Galaxy Nexus] osm0sis:
I'll check idle drain tomorrow. Seems about the same to me though. If anything would do that it'd likely be the cgroup commit. Ignoring that, I want to hear a comparison of smoothness. Short term and longer uptimes.
[Samsung Galaxy Nexus] darko.baruh:
Hi, I am new to flashing kernels on gnex. I did buy the franco kernel updater and when I downloaded the latest nightly kernel r384 and when the phone went to recovery it didnt flash it, saying that clockwork recovery didnt find the path. So I did it manyaly from there and have my pphone stuck on animation screen. The same thing hapened with the latest stable lean kernel. So in order the phone to boot I had to restore boot. Can someone explain me what I am doing wrong.

P.S. I am on miui v5 with the kernel that comes with it.
[Samsung Galaxy Nexus] lippol94:
As I reported when you published VM tweaks, it runs great for a few hours, then it starts lagging a lot. This ain't happening on original franco, neither on fancy kernel (just to make a comparison)

I really love governor and scheduler tunables, but those VM tweaks didn't work on my phone.

But hey, your mileage may vary :)
[Samsung Galaxy Nexus] adambala:
my friend miui needs modify kernels to work....try to find the kernel yo want from miui threat....
[Samsung Galaxy Nexus] darko.baruh:
Thank you
[Samsung Galaxy Nexus] Khrushy:
Haven't rebooted since I flashed it and it's very smooth so far. I can't compare to #384 because I never flashed it :p

VM settings seem really good - did you include the lmk stuff?
[Samsung Galaxy Nexus] The Gingerbread Man:
I had only had original 384 flashed for a short while before trying the osmod version. It was running mostly smooth but had a few screen off animation lags, a couple of scrolling lags and keyboard recacting slowly to input. Trying original 384 again to get a better comparison
[Samsung Galaxy Nexus] AutomaticFailure27:
Going to check out the "original recipe" today (and maybe a few more)

Letcha know what I find out... soon.
[Samsung Galaxy Nexus] AndyGnex:
I'll be honest here. I'm a big FrancoKernel fan. The only kernel that ran without hiccups on my phone is Franco's.

But since yesterday, i reverted to stock cm10.1 kernel....because it was the only way i could get Minion Rush to run smoothly :(

I know this isnt the kernel's fault, since i also play CSRracing and it ran fine on any kernel..its just the silly way how the game determines how intense graphically it should be rendered..

So, in conclusion, i'll have to be traitor, at least until i get bored of the minions. :D

Sent from my bathroom throne.
[Samsung Galaxy Nexus] kaluoshi:
why not using per-app settings for games? that's a super feature for issues like this :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] AndyGnex:
How do i do that? :beer:

Sent from my bathroom throne.
[Samsung Galaxy Nexus] kaluoshi:
maybe franco app? :) subscribe to beta testers for the latest beta too if you wanna :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] AndyGnex:
I'll have a look, though i dont think it will help since its the game that is to blame.. :D

Sent from my bathroom throne.
[Samsung Galaxy Nexus] kaluoshi:
You can bypass it with the app forcing to use performance gov, but only on game launch, that's the great thing. I'm very thankful to francisco for that feature. Pure innovation on kernel control imo :)

Paranoid ... wait for it ... Android
[Samsung Galaxy Nexus] Fenvarien:
384-osmod is running perfectly well here, no idle drain issues. Compared to vanilla 384 it seems to start lagging a bit after very long uptimes.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] Edward Stanbury:
I've gotta say purity 5.7.1 + osmod 384 is the fastest my phone has ever been omg this is amazing ! Thank you everyone :)
[Samsung Galaxy Nexus] osm0sis:
Hmm okay.

All we changed was the following:

echo 500 > /proc/sys/vm/dirty_writeback_centisecs;

This is the Android default. Francisco had it at 0 to disable the writeback daemon, I found both options very good but in the end thought 500 was a little better.

echo 2884 > /proc/sys/vm/min_free_kbytes;

This is double the GN default of 1442. AK has it at 3022, and many others jack it up to 2048, 3072 or even 4096. I found this helped in the longer uptimes but also made things feel a bit faster. I liked 2884 over all the other options. 2884 even seems to work nicely on the N7 where it's only a modest increase over its default.

echo 100 > /proc/sys/vm/vfs_cache_pressure;

This is the Android default, where Francisco has set it to 1. We found this improves the feel.

Can you both try getting the latest 925vm from my Dev-Host and edit writeback to 0 to see if that helps your perceived lag with longer uptimes?

lmk was the only thing I left out since I felt it was less finalized. Could you and The Gingerbread Man try pkgnex's latest suggestion on the Group forum and maybe then we can hammer these out?
[Samsung Galaxy Nexus] thegtfusion:
I mean... What do I need to say? :D

Perfect!

Purity 5.7.1+r384(stock)

-interactive 1228/384, hispeed @729

-deadline

-stock battery

-sync always on

-wifi on all time

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
New Maps that's been rolling out ditched Latitude. This is great news for battery life since the maps location wakelocks are some of the worst! :D
[Samsung Galaxy Nexus] whitedragonz83:
Yes, I noticed a MASSIVE drop in wakelocks. Basically it eliminated Google Maps as a wakelock and relies on the internal Android system / Google Play Services, I assume. Much more efficient and smart for location tracking.

This might bring me from 2hr SOT over 18hrs (mix WiFi/3G) back to 3hr+ SOT over 24hrs. (Yes, I do not restrict syncing, location settings, etc.. at all).

Oh, a side benefit that I can't be sure about for another day or two, is no more Google Maps in my running apps list (3 x 10-15 mb each they were). Sometimes when I would be 'low' on RAM 1 or 2 of these Google Maps apps would just constantly 'restart' causing severe lag making me reboot the Nexus to clear things.
[Samsung Galaxy Nexus] osm0sis:
Nice! I wonder if Hangouts improves the old GTalk wakelocks.

Idle drain seems to be 0.5%/hr for me which is pretty much the same as always. :good:
[Samsung Galaxy Nexus] bigbear6708:
My phone seems to prefer original recipe. I ran both stock for 24 hrs with no reboots. As stated before... LTE idle drain seems higher on 384 as well.
[Samsung Galaxy Nexus] Mevordel:
Hopefully it will. C2DM (Google talk service - implemented in GoogleServicesFramework.apk) has been deprecated in favor of GCM (announced at I/O and implemented in GMSCore). Once everyone starts using the new push service, hopefully they can remove that ancient 2.x technology. From everything else they're doing, it looks like they're trying to reduce the number of preinstalled apps/libraries by having a self-bootstrapping store and everything else downloadable from there.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Khrushy:
On it today - it's the settings in "Finalized" right? (I think I followed the post chain correctly).
[Samsung Galaxy Nexus] Coolgoly:
Sorry for the ot but my gnex won't charge more than 70%,till some days ago it reached 80%.It happens with various charger and batteries.

BLE is setted to 100 on FK.

I have to return to stock and send the phone to the RMA?

Thanks.
[Samsung Galaxy Nexus] osm0sis:
Thanks bro! You bet. I put them there tentatively since pkgnex and I were in agreement about them. I wouldn't copy/paste though, you should grab the actual scripts from my Dev-Host: http://v.ht/osm0sis / http://d-h.st/users/osm0sis :D

Unfortunately it sounds like your battery is starting to eat sh*t. :(

RMA to Samsung if you've owned it under a year, or you could always try and buy a replacement OEM battery on eBay.
[Samsung Galaxy Nexus] Coolgoly:
As I wrote I've already tried another battery.It's the phone.
[Samsung Galaxy Nexus] Fenvarien:
I installed the latest 925vm and switched writeback to 0. The lag was the same, so I searched deeper on my phone and discovered some memory hogging apps, that were updated lately. Most probably my perceived lag is nothing more than some app worries...

Thanks for helping to investigate, Osm0sis :)

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] jerrycycle:
This might be a another option to try . [APP][2.3+][ROOT] App Control - 0.40 http://xdaforums.com/showthread.php?t=2355148
[Samsung Galaxy Nexus] SahilC:
Hey [MENTION=4544860]osm0sis[/MENTION] - I'm not that interested (and frankly don't have the time) to be at the cutting edge of the kernel, but I'm very thankful of the work you put into franco's already amazing kernel. I just wanted to know: if franco sees that you have improved some part of the kernel, does he implement that in an official release?
[Samsung Galaxy Nexus] The Gingerbread Man:
Having cleared my cache and running lag fix over all partitions osmod 384 is running much nicer, I think there was some **** somewhere which could have been app related making it run not so well. I'm not certain the timer slack is working too great though, both versions of 384 I'm sure have increased battery usage. Osmosis, I can try to test these other numbers you mentioned you wanted testing, I have been so busy with personal life lately but if I get a chance I will try but can't promise.
[Samsung Galaxy Nexus] markjankovic:
My phone is like BMW now :)

Sent with my fingers
[Samsung Galaxy Nexus] creeve4:
Why is it not supported?
[Samsung Galaxy Nexus] Kurre:
could it be due discard mount option used for those partitions?

Sent from my SlimBeaned GNex
[Samsung Galaxy Nexus] Ci@cKi:
Have you tried to clean the app's data and cache? This helped for me!
[Samsung Galaxy Nexus] creeve4:
That is my guess. I have asked several times, but have not received a response.

This is the first time that I have ever installed the app.
[Samsung Galaxy Nexus] The Gingerbread Man:
It must be something with your set up as it works for me, on stock rom. I'm sure I read some time ago clearing app data and reboot fixed it.
[Samsung Galaxy Nexus] vlc_marcos:
can we use the kernel on miui rom?

thanks