yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] xFuGiToiDx:
Finished testing all 4 osmod versions.

1. fstab_sysfs_sdcard

2. Fstab_sysfs

3. Fstab_only

4. Fstab_sdcard

All versions were good. Not sure why I had bad battery drain with fstab_sdcard compared to the rest.
[Samsung Galaxy Nexus] osm0sis:
None of the 4 stood out as better for you?
[Samsung Galaxy Nexus] xFuGiToiDx:
The fstab_sysfs_sdcard is the best one out of the 4.. Its the most responsive and still able to keep a good battery life..
[Samsung Galaxy Nexus] AndyGnex:
I tried the fstab_sysfs_sdcard version, and since it was so smooth, i didnt even bothered to test the other three.... :angel:

Sorry to ruin your test Os... :crying: :D
[Samsung Galaxy Nexus] The Gingerbread Man:
I think the fstab sysfs sdcard probably feels the best but again its marginal difference between them all.
[Samsung Galaxy Nexus] thegtfusion:
Hey os,

What are the tweaked deadline values?

Thess are the default ones from franco.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] AndyGnex:
I guess this is what you're looking for?

In order of -->read ex, write ex, write starve, front merge, fifo batch
[Samsung Galaxy Nexus] thegtfusion:
Hehehehehehe thanks friend! :D :D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Son of a ****! Trickster added the general queue tweaks we selected as important?! I know they based it on our work since add random and rotational are in there. :rolleyes:
[Samsung Galaxy Nexus] dmourao:
Just testing the default one, now going for Sysfs_sdcard and the others.

Gonna post my results later.
[Samsung Galaxy Nexus] thegtfusion:
That sucks!

Anyways, the winning values are definitely winning. I have never seen my gnex so fast! Purity 5.4.3 + lippol-378+ winning values = jizz in your pants!

Thanks os, you are a legend :D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] whitedragonz83:
60+ hours of uptime. Deadline tweaked values with osmod sysfs. Sdcard. Fstab 378.

This is the first time I can remember in awhile I haven't felt the need for a reboot after a day or two. I only even checked the uptime for this post.
[Samsung Galaxy Nexus] Khrushy:
It's nice to be loved and credited . . . . err . . . well . . . at least we know people like it! :p
[Samsung Galaxy Nexus] osm0sis:
Haha exactly.. :p

The funny thing is those 2 really aren't very important, and most ROMs/kernels already have both of them set to 0 (off) by default, I just threw them in as a "let's make sure" kind of thing.. Pretty obvious they took their cues from us. ;) I'm just kind of bummed that they beat us to the punch, since that was on the list for f.Ku.
[Samsung Galaxy Nexus] SahilC:
Hey osmosis are your tunables stock for all franco kernels?
[Samsung Galaxy Nexus] lippol94:
I know your feeling guys... This is awful.

Unfortunately, as in everything else, there are positive and negative aspects of open source.

And not even get credits for your hard work is pitiful.

I suggest to compile them into a non-opensource module that gets loaded at boot and sets your winning values :P

Screw them.

Just kidding of course, but sometimes people make you think this way.

Let's take PGM's author.

When he developed the module on his former phone it was open source. And he simply published a paid app on the store to set it.

But other people took his code and made other apps with the same purpose but

1) completely free

2) available for less money.

And he didn't get what he deserved.

Hence, no more open source from him due to lame money grabbers.

That's sad.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] SahilC:
Sad. :(

Could the same be said for PA's PIE and (upcoming) Halo?
[Samsung Galaxy Nexus] :
Exactly.
[Samsung Galaxy Nexus] namtombout:
Idk. Everyone knows pie and halo are PA's. Similar to everyone knowing aokp toggles and navbar. plus no one is making money or taking money away from pa. Not to mention what the acronym aosp stands for.

But yeah it is sad

You my bro, you my kin, fck the color of your skin
[Samsung Galaxy Nexus] :
That's the consequences of open source, you create something awesome and at the long run someone will get that from you and advertise it a lot and all you get is a tap at the back for being the one that you discovered. And then the people who made it more apealling will have all the credits. ;)

Isn't it a bummer eh?
[Samsung Galaxy Nexus] Kurre:
hmm..AFAIK, those io tunables have been known & tweaked long before even fK/winning io values existed etc..of course you guys have made really hard work tweaking those values all together..But it's not like those tunables magically appeared when work to find winning values started.

I don't try to rant you guys or anything (I always try to be nice to people ;) ).

You guys combined the tweaking of scheduler tunables and common io tunables and everyone should be grateful for making that huge job and bringing those up to the bigger audience..but still those tunables have been there for a long time (and others have also tweaked those for a long time..?). It's like chicken or egg dilemma :p

point is that I don't understand what's the issue (offering an option to tweak these values easily?) or I'm totally missing the point (wouldn't be the first time) :D

edit: and if user asks dev to add some tunables to app, how could he know who "invented the ability to tune these values". Most probably those have been picked up from yours io script and therefore could be credited..dunno :)

Sent from my slimbeaned GNex :)
[Samsung Galaxy Nexus] SahilC:
True, and sorry for the OT, but I guess the way I see it is that even if people use other 'open' ideas, most people remember the original source of the idea. I mean, even though other ROMs have a variation of PIE, people still thing of PA as the original innovator. And I guess you could pull back PIE to the original stock browser too.

Same thing with Halo. PA made it better, but the original idea was from Facebook, right?
[Samsung Galaxy Nexus] :
You have that right man, that's how open source works. You have something and then someone gets interested and then poof, you're out of the picture. :)
[Samsung Galaxy Nexus] chickentuna:
same here mate. I've set it with the winning tunables, overclocked to 1305mhz. Never bothered to test the other 3. Im on slim bean and didn't notice any lag or stutters within the past 50+ hrs. Battery life I would say is about roughly the same as r378
[Samsung Galaxy Nexus] abalam:
+1
[Samsung Galaxy Nexus] EdForce1:
Where can i find this test kernel? I've looked for it, no go..
[Samsung Galaxy Nexus] :
20 posts back.
[Samsung Galaxy Nexus] GrijzeGeest:
Are the tunables still necessary or are they in this kernel already?

(Sorry if I missed that somewhere)
[Samsung Galaxy Nexus] osm0sis:
Oh hell, I'm not claiming we "invented" tuning those specific ones, just that it's obvious they took their selection of the many many (many) more queue tweaks available, from us, because they included add_random and rotational even though there's no point to them being there... other than we said so. :p

Yeah you guys missed the point of me putting up 4 completely. What if fstab_only turned out the fastest? :rolleyes:

Anyway it was pretty clear fstab_sysfs_sdcard >= fstab_sysfs > fstab_sdcard >= fstab_only by everyone's feedback, and that matches my personal assessment as well. Thanks to those that took their time to help test. :D

I've left the winner up as r378-osmod and brought the tweaks over to the N7 as well. :good:
[Samsung Galaxy Nexus] Khrushy:
You still need to script the deadline tuneables (250/2500/1/1/8) or bfq (slice idle = 0, back seek penalty = 1) if you use them but RoW and cfq are hard coded.
[Samsung Galaxy Nexus] 5pace:
Anyone having problems of this kind in mildly-graphic-intensive games?

I am on stock Android 4.2.2 (takju) build and kernel version is 378.
[Samsung Galaxy Nexus] osm0sis:
The fact that you could screenshot it indicates hardware pre-render.

On second thought I guess software pre-render could do the same.. Hmm.
[Samsung Galaxy Nexus] 5pace:
That was my first reaction; 'how could I screencap something that happened on lower hardware level?!'.

And in addition, after closing the game I could see some of graphic artifacts on my wallpaper and not anywhere else.
[Samsung Galaxy Nexus] Langduscher:
Thanks for your efforts to making a great kernel an even better kernel :good:

Amazing community!
[Samsung Galaxy Nexus] ToMeRv32:
I suggest to add ~850Mhz option.
[Samsung Galaxy Nexus] osm0sis:
Nah, we found more steps makes interactive perform worse.
[Samsung Galaxy Nexus] SahilC:
Hey everyone thank you so much. Literally just tested my phone against my dad's n4,and damn, I was right up there with it, if not faster. And amazing battery life too.

:D :good::good::good:
[Samsung Galaxy Nexus] odin13:
Hi guys...just a quick question...

I just flashed Franco kernel 378 and in trickster mod it shows smart reflex is turned off for mpu, core and iva. Thing is the setting doesn't stick when i turn it on. I already cleared trickster cache + data

Anyone has the same problem?

Thnx in advance

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] osm0sis:
SR is hardcoded disabled lately until Franco can find time to improve it.
[Samsung Galaxy Nexus] ToMeRv32:
And what about vibrator strength?

And can I use trickster for this kernel?
[Samsung Galaxy Nexus] droid_legacy:
You can use Trickster for sure! But for supporting the dev you could buy his app.

This is the only thing I'm really missing in this kernel. I know that franco did say that he won't implement it, but maybe someone with the knowledge could compile a kernel with the virbarto strenght control from ak (with the 127 scale not the one which goes up to 1470 (or something like thaht) ; hope it becomes clear). :D :rolleyes::laugh:
[Samsung Galaxy Nexus] odin13:
Thnx for quick reply :)

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] Kurre:
Heh, yeah and I didn't meant to claim that either (sorry for that, as english isn't my native language etc ;) ). But anyway..I think it's slightly nitpicking, since I think that your (and I mean all of you guys..not anyone specifically) work with the values is the one to be praised..a lot..(and thankfully almost everyone is giving the credit to you guys).

But that's just my "opinion", please don't take any offense on what I say :fingers-crossed: You can feel what ever you like and I'll respect that :)
[Samsung Galaxy Nexus] odin13:
Do you use standard values for core and iva or do i need to undervolt them?

Verstuurd van mijn Galaxy Nexus met Tapatalk
[Samsung Galaxy Nexus] droid_legacy:
So is there is newer version then one of those 4?

Means is there a way to download your: "r378-osmod "

Thanks for your hard work.
[Samsung Galaxy Nexus] osm0sis:
Can't remember if I made any changes since the 16th or not; my local build was an hour newer than what I had uploaded, and if there are any changes they'd be cosmetic only, but here's a fresh one just to make sure everyone's on the latest: http://d-h.st/users/osm0sis/osmod :cowboy:

P.S. I also just redid all the links in my sig with custom shortener URLs. Pretty nerd-fun. :p

For instance, now http://v.ht/fKGN points to the OP of this thread, http://v.ht/fKN7 to the OP of the N7 thread, etc.

http://v.ht/osm0 points to my Odds and Ends thread. :D

---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------

Like I said: Not upset in the least; jus' sayin'. ;)

---------- Post added at 03:07 PM ---------- Previous post was at 03:03 PM ----------

They're harder to gauge when you've UV'd too far than MPU is, so I've always just left them alone.
[Samsung Galaxy Nexus] marcusva79:
Os no zip for your tweaked 378 correct? At work and can't do the IMG. Was curious just use fast boot right?
[Samsung Galaxy Nexus] bombadier:
Use fastboot or copy the .IMG to the franco kernel backup folder /SDCARD/kernel_updates and use Kernel restore from within the app
[Samsung Galaxy Nexus] DoesntPostAThing:
Finally someone else that believes me when I say that the GNex can be faster than a N4! I was telling the people over at the CM thread that with a custom kernel (AK 243 at the time) our phones can be faster, but they refused to believe me and stuck with the CM Kernel. Have to say, Osmod 378 matches the performance of AK 243, sans overheating.
[Samsung Galaxy Nexus] droid_legacy:
Hey guys.

My Temperatur with latest kernel is during slight usage always At around 50°C. Is this normal. My phone seems to be getting really hot in the top right corner.

Thanks in advance.
[Samsung Galaxy Nexus] bunnahabhain:
Osmosis i just saved my "fancy kernel test 2" as boot image via fkU pro and i wnat to give your osmod a try... Do i have to reflash ROM and then install your kernel or is a cashe/dalvik-cashe wipe sufficient?

I wanna switch between these two kernels every now and then and reinstalling the ROM would be more work :D
[Samsung Galaxy Nexus] chickentuna:
No need to reflash anything, just flash the kernel and enjoy
[Samsung Galaxy Nexus] bunnahabhain:
Thanks [MENTION=4492200]chickentuna[/MENTION],

was just asking because AK-based kernels got a compressed ramdisk and require a rom-reflash. Didn't know how about Fancy/Franco :D

cheers...
[Samsung Galaxy Nexus] sotoskawasaki:
Strange thing happened. I put the boot-tuna-r378-osmod.img in kernel_backup folder and restored in fku. My phone stuck at google logo..

EDIT: I fixed it by using fastboot. Something must have gone wrong in fku.
[Samsung Galaxy Nexus] The Gingerbread Man:
I'd say it was probably a bad download, md5 mismatch or files missing. These things happen occasionally. Try with a fresh download over WiFi.
[Samsung Galaxy Nexus] Khizar:
But if it was one of those things it wouldnt have flashed via fastboot either, right? He edited hia post and said it flashed fine using fastboot...

Sent From My iphone Killing Galaxy Nexus Running AK Kernel And Whatever Rom I Feel Like. For The Love Of Everyone On The Forums READ BEFORE YOU POST!
[Samsung Galaxy Nexus] The Gingerbread Man:
True but he didn't specify if it was the same file he downloaded presumably to his mobile or another he downloaded to the PC over wifi
[Samsung Galaxy Nexus] droid_legacy:
:bumb: because I'm not sure if this could damage my phone. Purity 5.4.3
[Samsung Galaxy Nexus] sotoskawasaki:
I did compare the md5sum and it was the same. So it was not the file's problem. I used the same file in fastboot (after checking the md5sum first.) My bet is something went wrong in fku. Not that I am blaming it of course. S**t happens! :) Anyway thanks for the reply.
[Samsung Galaxy Nexus] bigknowz:
rq_affinity
[Samsung Galaxy Nexus] osm0sis:
Yeah 50°C isn't anything to worry about but that is weird.. Nice and cool at 34°C here. Uninstall any conflicting kernel management apps if you have more than one (SetCPU, Trickster, f.Ku), empty out your /system/etc/init.d directory, then wipe data+cache on the kernel management app you still have and reboot.

Actually you don't need to wipe for any of those either, at least not because of the ramdisk, as long as you're installing another kernel with a ramdisk (like f.K). At most, for a kernel that doesn't include its own ramdisk, you'd only have to flash stock kernel first then flash another. Only thing you need to watch out for, especially with AK (not sure about Fancy) are all the scripts it installs. Take a look in the AK installer zip (in the /system and /data subfolders) and you'll see what I mean. So if you're coming back from AK you should go through your ROM and weed out that stuff to make sure you're running clean.

Those are our finalized deadline tunables, so if you had to set them manually then you must be running an old version of the script. The script isn't required anymore unless you're using deadline, and only until Francisco hardcodes deadline on the GN as well. And yeah, that's correct; rq_affinity resolves to 1 here because the GN doesn't support 2.
[Samsung Galaxy Nexus] bunnahabhain:
great os... thanks! Running your osmod now... Thanks for your explanation. Will safe me a lot of time :D
[Samsung Galaxy Nexus] osm0sis:
Oh yeah! And I got 4h screen on time and 1d of uptime yesterday. First time since JB4.1.2. :D

Biggest difference is I uninstalled Facebook and FB Messenger. They were okay again for awhile there once you turned off push notifications, etc., but now that Messenger added the "Chat Heads" the wakelocks and counts are more ridiculous than ever, even if you disable that feature.

http://imgur.com/a/wWqUj
[Samsung Galaxy Nexus] droid_legacy:
Uninstalled Trickster and did what you told me to do and... tada.. seems to have fixed my temperatur problem. There where no init.d scripts so this couldn't have been the problem. Purchased f.KU. Tweaked my setting. Temperature idle is around ~35°C and after playing a few minutes Templerun2 my max temperature was at about ~50°C.

Thanks mate! That really fixed it. Now fully enjoying the kernel :) :thumbsup:
[Samsung Galaxy Nexus] wavedashdoc:
Also had an issue that was fixed by uninstalling trickster. Now Franco flies.

I came from AK which is a great kernel as well but lacked the stability even in its stable channel that Franco has always had.
[Samsung Galaxy Nexus] akash3656:
Fb app was never decent xD I use flipster free. Gets the job done nicely for a quick glance on the timeline. But no substitute for fb messenger yet :/
[Samsung Galaxy Nexus] osm0sis:
Nah but if you don't care about getting chat notifications immediately you can try MB Notifications. It's an app by Mike Bannion, who if I'm not mistaken is an old xda legend. It can do anything from 1min to 2h checks.

Between setting that to poll every 2h, and using Tinfoil and Haxsync, everything's pretty well taken care of.

Edit: Yeah, I was mistaken. I was thinking of Mike Channon, xda legend. ;)
[Samsung Galaxy Nexus] thegtfusion:
Hey os, i stalked your devhost, and i sae there is only one r378 now, is that "the chosen" one out of the 4?

I can just fastboot flash it? Fastboot flash boot francoblablabla.img?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Yup.
[Samsung Galaxy Nexus] thegtfusion:
Just for making sure, is my fastboot command good? :):o

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Yeah that's how you fastboot a kernel. :)

You could put it in /sdcard/kernel_backups and flash it through f.Ku's Backup/Restore function too. That's how I always do it.
[Samsung Galaxy Nexus] thegtfusion:
It worked ;)

The fifo batch tunable is 16 now? (Instead of 8?) Is that the new experiment?

Sent from my Nexus Prime
[Samsung Galaxy Nexus] osm0sis:
Nope, all scheduler tunables are finalized now. I'd say you're running an old version as well. Read my response to bigknowz a page back.
[Samsung Galaxy Nexus] thegtfusion:
Got it, thanks. Ps, check your pm.

Sent from my Nexus Prime
[Samsung Galaxy Nexus] bigknowz:
init.d

You were correct. For some reason, my init.d backup folder had the correct settings, but the actual init.d had old settings. Fixed, thanks.
[Samsung Galaxy Nexus] thephenom696:
Derp.
[Samsung Galaxy Nexus] stevensoaj:
[MENTION=4544860]osm0sis[/MENTION], I got a question for you. Could you explain why the systemui priority part of my init.d script causes certain kernels(lean and trinity) to bootloop (the don't get past the Google boot logo)? It works fine on every other kernel (Franco, fancy, AK, kubo). I'm using this version of it.

# wait for systemui and increase its priority
until [ `pidof com.android.systemui` != "" ]; do
sleep 1;
done;
renice -18 `pidof com.android.systemui`;
[Samsung Galaxy Nexus] DoesntPostAThing:
What about CM's built-in one?
[Samsung Galaxy Nexus] gpzbc:
I have tried Franco on my Galaxy Nexus quite a few times over the past year and have never been happy with it. Battery life sucked and it got really laggy to the point that I had to reboot and eventually install a different kernel.

So anyways I installed Franco kernel 378 with the osmod tweaks yesterday and have had nothing but good results. It is smooth as butter and my battery life is longer than it has been in a really long time. I guess I just never had the right settings on my previous attempts at Franco Kernel.

Thanks osmOsis (and Franco)!
[Samsung Galaxy Nexus] nikulogical:
Is the 378 in the op the one with osmosis tweaks or is there a separate download for that?
[Samsung Galaxy Nexus] bigknowz:
osmod

Here's the osmod 378.
[Samsung Galaxy Nexus] osm0sis:
That should be:

# wait for systemui and increase its priority
until [ `busybox pidof com.android.systemui` ]; do
sleep 1;
done;
renice -18 `busybox pidof com.android.systemui`;

And be careful with your LFs.

They have their own ramdisk.
[Samsung Galaxy Nexus] stevensoaj:
It didn't work for me without the != "". I just wanted to know what was causing this to boot loop on lean and trinity but not other kernels.

Edit: Never mind I'm dumb.

Edit2:

Nope. Still doesn't work even with those changes. I thought that part would be universal for every kernel, but I guess not.
[Samsung Galaxy Nexus] DoesntPostAThing:
I meant the build-in performance settings stuff. Overclocking, etc. Do those interfere with Trickster?
[Samsung Galaxy Nexus] zoomy942:
So if I buy the Franco app, I can control the colors and get away from the dim blue hue?
[Samsung Galaxy Nexus] musashihatred:
you can also use trickstermod to do that thing for free.

besides, Using Franco App (buying) is a way of saying thanks to him :)
[Samsung Galaxy Nexus] osm0sis:
Yeah that's really weird. Both that you can't get it to work and that it gives you bootloops on other kernels. Oh well, works here and that's the important thing. :confused: :)

Well yeah. ;)
[Samsung Galaxy Nexus] DoesntPostAThing:
I see. What if they're not set on boot then? Because I get that annoying overheating issue. I'm quite confused here, as to what interferes with what. I like the amount of options Trickster offers, and is convenient since I switch ROMs/kernels quite often. Jumping between Franco and AK, and Vanir and CM.
[Samsung Galaxy Nexus] osm0sis:
CM/AOKP/PA extra performance options shouldn't really be a problem if you don't set them on boot. Follow my advice a few pages back and clear data +cache on Trickster and make sure your init.d folders are clean.
[Samsung Galaxy Nexus] DoesntPostAThing:
Ok, thanks. What about the ones the ROM puts in there though?
[Samsung Galaxy Nexus] osm0sis:
Up to you bro. Personally I don't think any scripts are required if your ROM is doing its job. I don't like any ROM or kernel that's loaded up with sh*t.
[Samsung Galaxy Nexus] DoesntPostAThing:
Well, currently on Commotio. Has some speed scripts to make stuff super fast (it shows). Just flashed though, so I'll let it rest overnight and see how it goes tomorrow.
[Samsung Galaxy Nexus] alfiemenace:
Just want to ask, if I flash the latest Osmod, do I still need the 950iosettings in init.d?
[Samsung Galaxy Nexus] Jerommeke:
Stuck at the Google-logo here too, does anyone have a download link for the 13.1 kernel? I would like to go back, 'cause that one worked just fine for me :)
[Samsung Galaxy Nexus] darrendm:
Simply reverting to 13.1 did not work for me, I had to restore a backup.
[Samsung Galaxy Nexus] sluflyer06:
Running great here :). AOKP 20 and #14.
[Samsung Galaxy Nexus] aron7awol:
Maybe flashing faux's reset kernel zip before flashing Franco kernel will help the people having issues?

http://goo-inside.me/kernels/faux123/ICS-4.0.3-Reset-Kernel (1).zip

I can't UV on 14 like I could on 13.1 but otherwise, it's working fine.
[Samsung Galaxy Nexus] franciscofranco:
Well, I'm so sorry everyone. I sent this kernel to 5 testers and haven't got a single problem reported, I don't understand what happened here.
[Samsung Galaxy Nexus] aleve1983:
Work fine for me, aokp 20. Work first and second update

Inviato dal mio Galaxy Nexus usando Tapatalk