yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] namtombout:
fifo_batch

This determines the number of reads or writes to issue in a single batch. The default is 16. Setting this to a higher value may result in better throughput, but will also increase latency.

front_merges

You can set this tunable to 0 if you know your workload will never generate front merges. Unless you have measured the overhead of this check, it is advisable to leave it at its default setting (1).

read_expire

This tunable allows you to set the number of milliseconds in which a read request should be serviced. By default, this is set to 500 ms (half a second).

write_expire

This tunable allows you to set the number of milliseconds in which a write request should be serviced. By default, this is set to 5000 ms (five seconds).

writes_starved

This tunable controls how many read batches can be processed before processing a single write batch. The higher this is set, the more preference is given to reads.
[Samsung Galaxy Nexus] Antob125:
Any way to keep these after boot through fku?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Get a copy of osmosis's script from his SIG and your golden :D:thumbup:
[Samsung Galaxy Nexus] nikodr:
Well it is incredible....thats why i love 4.1.2 . Four dqys and still on:)
[Samsung Galaxy Nexus] harris360:
How much display time?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] Bl4ck3urn:
Big thanks to you!

I've found a nice documentation about these tunables which I would like to share.

https://www.kernel.org/doc/Documentation/block/deadline-iosched.txt
[Samsung Galaxy Nexus] wtr_dhd:
Looking at the little screentime % it means you had your phone on standby for almost 4 days without using it. Quite obvious then that you can get 3-4 days out of your battery like that..
[Samsung Galaxy Nexus] pen²:
Since 376 I'm getting sync drops with franco kernel (ie: sync is on but even when I'm on wifi, when i switch off the screen and unlock the device 4 minutes later, the wifi icon is grey. Some seconds later it turns blue again and I start receiving emails).

First I blamed it on the voltages, so I upped them by 50mV. Did not help. Wiped cache, dalvik cache and franco kernel app-data.

No problems like this with lean kernel except I don't want to use it ;) franco has offered better performance and battery life for me.

This is with cm 10.1 rc1.

Any hints?
[Samsung Galaxy Nexus] bat0nas:
The new version of the updater is so advanced now!! It checks every hour by default for a new kernel when.. new kernel versions are released just once a month.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] K.D.M.:
Same problem here
[Samsung Galaxy Nexus] osm0sis:
f.K uses the stock wifi drivers. This is more a ROM issue of it forgetting your settings somehow despite displaying correctly. We discussed it 5 pages back and the solution I mentioned has worked for most if not all others experiencing the issue.

http://xdaforums.com/showthread.php?p=41201322#post41201322
[Samsung Galaxy Nexus] knightmedz:
Hi, can anyone please tell me the color settings of the stock 4.2.2 kernel? I want to keep f.K but I always prefer the look of the stock kernel on my device. Thanks!
[Samsung Galaxy Nexus] mono28aug:
Choose between the color presets in trickster app...
[Samsung Galaxy Nexus] Raijin:
RGB 200 200 200, Gamma 0 0 0.
[Samsung Galaxy Nexus] Wynnded:
Change the setting. And remember that this is for more than just one device.

Sent from my Galaxy
[Samsung Galaxy Nexus] The Gingerbread Man:
Just so your aware all the blue icon WiFi / data icon means is if your connected to googles services / servers. WiFi and data can still function when they are grey it just means things like gmail / play store / Google talk wont work. A couple of work around I heard are remove your Google account reboot and add it back or sign out and back in of Google talk. Voltages and cache and dalvik are completely unrelated to this so if you want to blame anyone blame anyone it should be Google.

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] ChazzMatt:
Grey bars = no data

:rolleyes:

NOT always. In fact, I would posit not most of the time?

With my device, when I have grey bars I have NO data, period. With my wife's Nexus also. For us, and probably many others...

Grey bars = no internet connection whatsover.

No webpages in browser, no emails (not just gmail but all other accounts), no music streaming, etc.

Searching on Google I see tons of the myth "Grey bars just means you aren't connected to Google services". :rolleyes: And the reason you aren't connected to Google services is because you have no freakin internet connection.
[Samsung Galaxy Nexus] pen²:
Hi,

it is definitely kernel (or wifi driver) related, as all of these problems do not occur with lean kernel (while google stays the same when I change the kernel ;))

What I learned from other threads for other kernels and what helped me so far:

- Flash CM-stock-kernel before switching to franco from another kernel. (Simple solution: *Download* franco kernel (don't auto-flash), go to recovery, dirty-flash CyanogenMod, flash franco, flash gapps, wipe cache, wipe dalvik, reboot)

- go to wifi settings and disable wifi optimization if enabled and set wifi-sleep policy to "never sleep"

- go to franco app and enable WI-FI PM_FAST

So far no wifi-sync "drops" for 18hrs...
[Samsung Galaxy Nexus] The Gingerbread Man:
Well if it works for you then great. From what I've seen here the last three guys trying to report bugs all were using cyanogen roms, a guy said Bluetooth froze his phone, another WiFi tether broke and you with data drops. I have none of these issues on stock rom, what does that say about cyanogenmod?

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] sconrad308:
That's what I was thinking too. I've not experienced any of those problems and I'm running stock with Franco Kernel. I think the common link seems to be the ROM. I have thought about switching to AOKP but I've been pretty happy with stock. I see no reason to change.
[Samsung Galaxy Nexus] lippol94:
Franco.Kernel r378 - lippol94 | more priority to SystemUI

Here's a new toy for you to play with ;)

Recently boype added a really cool feature to his Fancy Kernel to elevate systemUI process priority in order to have a smoother UI.

It doesn't drain your battery more than usual. Simply, SystemUI, responsable of transitions and animations, gets higher priority over other processes, so CPU will provide "more power to it" while other processes are running at the same time. (let's accept this expression to be easily understandable from everyone).

I found it cool, tested and liked it. So I ported it on Franco Kernel!

Check sources here

I didn't do anything special. Just unpacked ramdisk, added boype's code, repacked. That's it :)

Go and flood boype and osm0sis of thanks ;)

Download Link:

http://d-h.st/PuP

Credits:

Boype - http://xdaforums.com/showthread.php?t=2115590

Osm0sis for his Android Image Kitchen :* - http://xdaforums.com/showthread.php?t=2073775

Lemme know how it works :)

See ya guys :)
[Samsung Galaxy Nexus] ExodusC:
If this actually works, I'd love to see Franco add this to franco.Kernel Updater!
[Samsung Galaxy Nexus] Efrenjr15:
Going to have to give it a try, anything special we need to do after the flash?
[Samsung Galaxy Nexus] lippol94:
Actually is really working. I'm not the only one to say so. :) go and read last pages on fancy kernel thread

Nope. Wipe cache and dalvik as usual when flashing a new kernel. That's it. :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Spoderman:
Is it only me, or this kernel with CM 10.1 gets really sluggish sometimes.

After restart it's fine for a day or two again.

Also, on games, there's a lot of stuttering, not lag, only stuttering, which is annoying :/

I'll try to go back to AOSP R11...
[Samsung Galaxy Nexus] osm0sis:
Great idea! Looking into implementing it my own way for inclusion here.
[Samsung Galaxy Nexus] Sparx639:
Nope, when I'm using my schools WiFi, Google services are blocked but I can still use the internet even if my data is turned off. So the myths ARE true :p
[Samsung Galaxy Nexus] ChazzMatt:
I have 2 Galaxy Nexus vs your 1 Galaxy Nexus. I win. :)

I have NO data connection at all with grey bars.
[Samsung Galaxy Nexus] lippol94:
It doesn't matter. That's a 4.2.2 bug.

We have to wait for google to fix it. Let's hope in a marvellous 4.3 ;)

Yeah, saw the same while reading his ramdisk. That's bad :/

I'll ask him to add them :)

Anyway, glad you like it. I think it's a nice +1 and would be awsome if Franco would add it by default.

I'm sorry... I do :P Sometimes I can perfectly browse web pages and do everything even if signal bars are not blue.
[Samsung Galaxy Nexus] Sparx639:
Who says I only have one nexus? And that's because you can't connect to Google services without a connection to them :rolleyes:
[Samsung Galaxy Nexus] ChazzMatt:
Dude, if YOU CAN READ, I plainly said it was NO internet connection -- no websites, no email (not just gmail, all email accounts). With grey bars (wifi or mobile signal) there's no internet connection, period.

At least on my two Galaxy Nexus. And I dare you to prove you have more than 1 Galaxy Nexus. Like show me an XDA post from from a year ago, not some photoshopped receipt. Because I can.
[Samsung Galaxy Nexus] Sparx639:
Yeah, and I was saying that grey bars mean that you aren't connected to Google services, and I was right. Obviously I know that in your situation it was caused by lack of connection, but, gray bars = no connection to Google services.
[Samsung Galaxy Nexus] ChazzMatt:
I'm not connected to Google services because there's no internet connection.

If you are agreeing with me, fine.

I notice the issue more with mobile signal grey bars, but also happens sometimes with wi-fi grey bars. Very frustrating when it happens. I SEE there's a signal but it's not "active", I can't connect. No data with grey bars. :(
[Samsung Galaxy Nexus] Sparx639:
I was agreeing, just saying that the gray bars mean no Google services connection
[Samsung Galaxy Nexus] jcmm11:
I suspect you're both right. If you have grey bars without a 3g/4g etc indicator above them you have no connection. If they're grey with the indicator you have a connection but no Google services. I'm not sure of the no services limitations though since you can still get to things like the play store.
[Samsung Galaxy Nexus] osm0sis:
Meh. Not overly worried. It's only the queue tweaks (and older versions of them) like I said. Don't bother.

Here's a much cleaner version I just whipped up:

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

We could pretty much stick that in our ramdisk before the lmk whitelist script and we're all set. Could maybe even remove the sleep for the lmk whitelist since the launcher should be starting at pretty much the same time. I'll experiment. Of course this will also work just fine in an init.d script so no need to hack around if people want to try it out. Or just run the last command from Terminal Emulator to try it for on-the-fly comparison. ;)

Edit: Yup. We can reduce the lmk sleep to 10 with that above it. :good:

Edit 2: Apparently -17 may be better than -20 according to BoyPeterson (Fancy Kernel), where the original idea came from.

Exactly. But I've had times where my bars were grey and I could still do basic web browsing, but the Play Store, Google Apps Sync etc. wouldn't work. Grey DO

only

indicate that you aren't connected to Google Services, however, the majority of the time, that WILL also mean your internet connection in general isn't working.

Chazz, I like you buddy, but you need to stop escalating when you think you know you're right. :rolleyes:
[Samsung Galaxy Nexus] The Gingerbread Man:
That would be highly appreciated if you could have a word, it is basic common courtesy to credit. I don't mind the values being used by everyone, but a lot of time has been put into those settings and not just me and osmosis but a whole group of us have been working on stuff for months and just basic gratitude or recognition would be nice.
[Samsung Galaxy Nexus] osm0sis:
They're the old versions where nomerges = 1, I say **** it and let them suffer. :p
[Samsung Galaxy Nexus] Sik-1:
Where can I find the latest io tuneables you guys are using, even tho I know its always being changed and worked on
[Samsung Galaxy Nexus] lippol94:
Last update has been released on April 24 if I'm right.

Look for it following "odd scripts etc" link in osm0sis signature :)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Sik-1:
Cool thanks a bunch lippol
[Samsung Galaxy Nexus] EnricoTFYKD:
About the grey bars: I'm pretty sure they just mean that Google push service is not working. In fact, when I'm connected to my university wifi, bars are grey and I do not receive notifications for Gmail, Facebook, etc because incoming connections are blocked, yet I can access Internet with no problems.
[Samsung Galaxy Nexus] lippol94:
You're welcome man ;)

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] demlv:
Running Osmosis' script for the tunables. Never messed around with init.d before. Phone running nice and smooth, but is there a way to truly verify the script is working?
[Samsung Galaxy Nexus] thegtfusion:
Hehehehe lippolmod r378 running awesome :D

Sent from my Nexus Prime
[Samsung Galaxy Nexus] akash3656:
I know how you feel. Same exact situation for me in my college too.
[Samsung Galaxy Nexus] maverick_hunter:
It's improvements like this that keep me from pulling the trigger on a Nexus 4.
[Samsung Galaxy Nexus] marcusva79:
Does anyone get lag with carbon ROM? Works good for a while then stutters like a mug. Any suggestions? Wonder if it's a toroplus thing?
[Samsung Galaxy Nexus] Efrenjr15:
heard its like a systemui leak?
[Samsung Galaxy Nexus] marcusva79:
I know it's not the kernel so I'll shut it and get on topic. Just wanted some suggestions. :banghead:
[Samsung Galaxy Nexus] jcmm11:
Try the 5/13 nightly. Big improvement for me on Toro, so far at least.

Although I have switched to Tiny kernel for the moment. Ingress heated my phone like crazy. Don't know if it was Rom or kernel, but my initial guess it's that the gpu was running at high freq the whole time and even with uv it just got too hot. But that's only a preliminary guess.
[Samsung Galaxy Nexus] kalintka:
+1, confirm that lag.

Nexus tapatalk
[Samsung Galaxy Nexus] lippol94:
That's cool! Are you sure it will work without using busybox?

As written many times, that's a known 4.2.2 bug.

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

https://code.google.com/p/android/issues/detail?id=51254
[Samsung Galaxy Nexus] lippol94:
Woot! New io settings update is online :)

Thanks Franco Team <3

http://d-h.st/c3T
[Samsung Galaxy Nexus] arhung:
The link seems not working:confused:
[Samsung Galaxy Nexus] lippol94:
http://www.downforeveryoneorjustme.com/http://d-h.st/c3T

Doesn't seem so :)
[Samsung Galaxy Nexus] osm0sis:
;)

No real changes for us, just added a couple extra tunables that row has on the N4+N10.

Oh definitely, they're all built in commands. Busybox is completely unnecessary for this. That's why I used pidof instead of pgrep; native is better.

Edit: Here's a simple way I just worked out to check the actual current priority (also known as "niceness") on Android:

cut -d\ -f19 /proc/`pidof com.android.systemui`/stat

Note the extra space after -d\, that's important. The output should be -20 like we set with the init.d/ramdisk script. That's the lowest number (and highest priority) a process can be.
[Samsung Galaxy Nexus] bigbear6708:
Is that zip a whole kernel or do I fish on top of Franco kernel?? Have been absent for a while.. Sorry if I missed the conversation on it
[Samsung Galaxy Nexus] osm0sis:
Like it says, "init.d script installer" - flash it on top. Only really useful on f.K tuna now if you want to use our tweaked deadline on boot. All the other schedulers are already hardcoded. And presumably it won't be necessary at all beginning with M7. :good:
[Samsung Galaxy Nexus] :
Just download the CWM installer and flash it after installing Franco, it will add the script at the init.d folder :)
[Samsung Galaxy Nexus] Blackcrx:
M7? Wow, haven't seen a milestone since the 4.1 days. This is exciting news
[Samsung Galaxy Nexus] coolshan:
PGM

PGM is not working with 278. when i enable it reboots the device. any way to fix this>?? i cant live without PGM:confused:
[Samsung Galaxy Nexus] ExodusC:
Does the Galaxy Nexus with franco.Kernel not support dynamic hotplug on the CPU?

It doesn't seem to ever offline one of the cores, even when the device is idle.

Doesn't franco.Kernel on the Nexus 4 do this? Does the Galaxy Nexus not support it due to a hardware limitation or something?

Edit: Nevermind, the Galaxy Nexus and franco.Kernel seem to support it as I can do it through an external app. I'm curious what behavior franco.Kernel has for offlining the second core?
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Little confused by the recent app update. The fsync option used to be a check box to turn fsync on and it was checked by default. Now the option says to turn fsync off and it is checked by default.
[Samsung Galaxy Nexus] Sik-1:
The galaxy nexus wasn't made to offline cores the way the n4 does, completely different beasts lol
[Samsung Galaxy Nexus] xFuGiToiDx:
Just flashed lippols r378 so far so good and seems to be faster than original. :)

Hopefully I'll be able to achieve 4 hours on screen time, almost reached it with fancy r24 ;P
[Samsung Galaxy Nexus] ChazzMatt:
PGM not working is usually PGM developer issue. :rolleyes: Usually.

Over in another kernel thread, every time the kernel is updated PGM "breaks" until the PGM developer updates the software. So, over there questions about PGM have almost been banned. It's NOT the kernel's fault, it's the PGM developer's fault. Assume that first, go ask the PGM developer. THEN, come ask the kernel developer. ;)
[Samsung Galaxy Nexus] stevensoaj:
So if I wanted to adjust the niceness of systemui via an init.d script, what value would I echo (I assume -20 for highest priority) and to where? Or, would I echo a value at all?
[Samsung Galaxy Nexus] osm0sis:
lippol quoted my post with it a page back. :)
[Samsung Galaxy Nexus] stevensoaj:
I looked and looked. Don't know how I didn't see it. Thanks!
[Samsung Galaxy Nexus] shreddintyres:
im on 378 and its working just fine, you need to uninstall pgm, reboot, reinstall from market, reload modules and go from there, all this info is listed on the play store page for PGM, any time you change kernel or update the app, if it doesnt work the above is the prescribed method to get it working again.
[Samsung Galaxy Nexus] akash3656:
Works perfectly for me on 378. Heck the only kernel I tried and PGM caused the phone to reboot was Glados kernel. AK Trinity and Franco kernel work fine with PGM.
[Samsung Galaxy Nexus] lightingcloud:
I had a few reboot and a freeze in the last few days, then noticed that the phone switched to deadline on his own... O_o
[Samsung Galaxy Nexus] xFuGiToiDx:
Flashed lippols modded version of franco r378 and so far its the only kernel that im able to get 4 hrs on screen time! Great job for u hard work..
[Samsung Galaxy Nexus] lippol94:
Yeah, no, please :D

Don't thank me at all.

I really didn't do anything. I just took the already outstanding release from Franco and applied a few lines to elevate systemUI process priority. That's it :) It wasn't even an idea of mine. Credits go to boype.

Btw, I'll push a new version today with cleaner code by Osm0sis and process priority set to 18/17 (we don't need 20 as it's too high for systemUI process. Only very important ones require it.)
[Samsung Galaxy Nexus] xFuGiToiDx:
I will flash the new fancy r25 and see if i get the same results.
[Samsung Galaxy Nexus] chickentuna:
Please do and report back. Im curious as I am switching between franco and fancy and can't really see any noticeable improvements, well except that systemUI is more snappy and fluid with fancy and lippol modded franco.
[Samsung Galaxy Nexus] ro_explorer:
Those tests have a current interval. If you look at the video you will see that the amperage draw is not constant and is more like bouncing between two limits, with the most frequent value that I saw being written in the current (mA) field. But those absolute values are prone to error ... I would say that there is a little (visible) difference between 350 and 700 while playing mp3 ... but It can be ignored.

Anyway, I'm one of the stubborn guys and I'll just set the minimum to 350 :).
[Samsung Galaxy Nexus] Nebucatnetzer:
I tried to run the "Scaling Test" in the Stability Test app to test if #14 is stable. It wasn't even able to performe on successful run. I tried it twice. Same result decided to flash back to #13.1

I'm trying again with #13.1 to check if it's something with my setup but it doesn't look like. I already passed 2 runs.

Note: I'm running at stock settings no profiles nor undervolting.
[Samsung Galaxy Nexus] franciscofranco:
Yes, it was probably my ****. Try download and flash again, I re-uploaded it.
[Samsung Galaxy Nexus] 1Speed:
Installing #14 puts my Galaxy Nexus in a boot loop cycle that will not even get to the animation. I tried removing the battery and putting it back in and the boot loop continues. I reverted to 13.1 and everything is fine now.

Not sure what is going on with #14 with my GSM Nexus.
[Samsung Galaxy Nexus] darrendm:
Reupload does not work for me still.

Freezes during boot animation and restarts.
[Samsung Galaxy Nexus] ro_explorer:
Same for me :(
[Samsung Galaxy Nexus] franciscofranco:
Wtf... Try again, just reverted something else.
[Samsung Galaxy Nexus] Nebucatnetzer:
actually the reupload seams to work for me. Passed 3 runs in Stablility test with scaling.
[Samsung Galaxy Nexus] darrendm:
Restoring nanbackup and will try new upload once it's done.

Off topic but; Dani Alves' goal was so sweet!!!
[Samsung Galaxy Nexus] Bisazz:
I had this same issue going from 13 - 13.1. Whenever I had it setting UV on boot it would freeze during the boot animation.
[Samsung Galaxy Nexus] ellesshoo:
Can these have some sort of versioning? I don't know which "#14" I'm on now or what things were reverted.
[Samsung Galaxy Nexus] ro_explorer:
So I deleted all #14 from internal memory and downloaded again ... 2 minutes ago

Stuck at Google logo .. not even going into boot animation.

---------- Post added at 12:01 AM ---------- Previous post was at 12:00 AM ----------

Franco, if you ask me, I think you should skip #14 and start indexing. There are already 2 or 3 versions of #14 ... people (including me) are getting confused.
[Samsung Galaxy Nexus] dwang:
I'm also experiencing the 3g data drop off when the screen is off on build #14. Same thing that was reported on morfics thread with his kernel.

when the screen is off, mobile data goes away.

when the screen is on, mobile data comes back.

I'm using bigxie's rom which doesn't have the power saver feature. so 3g shouldn't go off when the screen is off.
[Samsung Galaxy Nexus] Nebucatnetzer:
I let it pass 5 test successfully. Now I switched the phone off and rebooted.

Worked without a problem.

I'm using the second upload (the first reupload).
[Samsung Galaxy Nexus] Pego71:
does not work, it crashes google logo ....
[Samsung Galaxy Nexus] yohimbe35:
It did the same for me. I went back to 13.
[Samsung Galaxy Nexus] ctbear:
Something to consider: it could be that the GPU OC is causing problems? I remember flashing an GPU-OC'ed kernel and had the exact same issue (not getting to boot animation)
[Samsung Galaxy Nexus] danielvc:
I stand corrected: i'm having problems as well. didn't start and now my rom is corrupted or something. restoring a previous version of my rom+kernel. grmblz. Is there a way to download 13.1 again?
[Samsung Galaxy Nexus] nic85:
Lol?

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] akalias1981:
+1

Having the exact same issue. Glad its not just me.
[Samsung Galaxy Nexus] Efrenjr15:
I'll be waiting lol :p