yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] nikodr:
Is it somehow possible to create a script that would change kernel parameters of battery when battery decreases? for example when battery range is 100% to 60% i would want to have interactive governor with some specific options,when it gets to 59% i would want it to automatically switch to other options is that possible?Sorry if this is offtopic to the kernel thread,but i want to automate the process of battery handling like this,i know that when i am travelling and i don't have a charger with me it would be useful if kernel options of battery changed automatically when i am let's say 59% of battery.That way i could save more juice automatically.
[Samsung Galaxy Nexus] Edward Stanbury:
you can do this by using SetCPU app but it may conflict with other kernel setting apps/rom controls.
[Samsung Galaxy Nexus] Kurre:
with Tasker this could be done and you would have full power over it. It just takes some time to get it right..meaning that you would want it to set those parameters only once (making sure that it doesn't echo values over and over again, etc.) and then restoring those after being charged. But it's doable no doubt :)
[Samsung Galaxy Nexus] Langduscher:
Tried some of the other kernels out there, but franco.Kernel is still the best in terms of battery life & smoothness :good:
[Samsung Galaxy Nexus] nikodr:
I believe a mod like this would be very useful,i sense that the governors that give best battery life are handy when the phone is low on battery.No sense to use ithem when it is 90%.

I have in mind what i want to do,i don't mind under clocking the phone when battery is only 25%.Unde-rclocking and maybe switching off the second core,and maybe changing the voltage too,would help conserve more battery.

I know what i want to do,but is is not practical to load the application just to do that,i know of the profiles i can create if i want ,but i want to make it as automatically as possible.

So how about a request for new feature of the kernel app,to auto switch profiles automatically based upon the user programing of profiles and the usage of battery?
[Samsung Galaxy Nexus] CyanoBacteryMod:
I am using BeastlyBattery mode but .. can i get a setup to increase the battery life even more?

Thanks:good:
[Samsung Galaxy Nexus] nemotheblue:
[MENTION=3292224]franciscofranco[/MENTION]

Ever since I clean flashed MiNCO v7, using your 4.2.2 nightlies, the Lightflow app hasn't worked at all. I was emailing the developer last week and he suggested the problem might be caused by something you changed post-r364. Lightflow tries to run the command "ls -R /sys/devices" on startup, but for some reason it just hangs when your kernel is installed. I tested the command via "adb shell" and confirmed this behaviour.

The dev offered me a beta version that might ignore the error, but I thought you'd want to know in case this could affect other apps/commands
[Samsung Galaxy Nexus] creeve4:
I am currently using Light Flow with AOKP and r376. I have no issues with the app.
[Samsung Galaxy Nexus] ak:
Light flow have problem with ak kernel also ... I think the developer have to investigate where is the problem. :thumbup:
[Samsung Galaxy Nexus] Gafanhotz:
Or maybe it's something in my Nexus' hardware. But I'll forget it, since I rarely use bluetooth.
[Samsung Galaxy Nexus] The Gingerbread Man:
As much as I'd like to reproduce your problem I simply couldn't with my phone connected to the car using Bluetooth at the same time I was using Google maps navigation to get me to my destination near south coast and as you can see its quite a journey. Same as WiFi tethering, I got to actually use it for a decent amount of time as the hotel had no WiFi so I had to use my gnex as a hot spot, all works perfectly.
[Samsung Galaxy Nexus] Gafanhotz:
Yep, I understand. But nevermind, I'll stick with stock ASAP the next Android comes up. Hopefully, Franco will support it.
[Samsung Galaxy Nexus] EnricoTFYKD:
Try this workaround: after starting the wifi tethering, open a non-cached Web page either in the stock browser or Chrome. I also experience "limited connection" when I first connect the PC to the mobile hotspot, but after opening a Web page on the phone the hotspot starts behaving well.

I don't know if it's just placebo or what, but it works for me. Last Cm nightly and franco 376
[Samsung Galaxy Nexus] osm0sis:
Finally hunted down the commit; it's been in for ages. Samsung never actually fixed it just worked around it by keeping the affected chip fw revisions from using the command (secure erase) that triggers the brick.

https://github.com/franciscofranco/Tuna_JB_pre1/commit/3c57a612f12b069bbc863ec0c74a26850d76a9e8

So yes, should be perfectly safe to enable discard for any kernel with the above patch. Still not sure why ordered data would be required though.. I was digging around in the AK ramdisk last night and they've got both writeback and discard in the fstab with apparently no problem. :confused:
[Samsung Galaxy Nexus] The Gingerbread Man:
It would be nice to have but last time we talked about it Franco ended up in boot loops for some reason but he was majotly busy at the time http://xdaforums.com/showthread.php?p=39533348&highlight=discard#post39533348 Perhaps its worth another shot
[Samsung Galaxy Nexus] Kurre:
Yeah I also forgot this issue completely :p

But true, it should be safe to enable discard option via fstab. Dunno what caused that bootloop issue (logcat was dumped full of some ****..can't remember precisely anymore..). Maybe there's some commit what's causing this..or some other difference in ramdisk, hard to say without thorough testing. And everything works just fine if applied after booting..it's funny.. :p

And to be honest, I'm nowadays using stock slimbean (with leankernel), so I ain't even using fK now..nor have time to play with it. Maybe I could try same fstab mod with LK and see if it behaves in the same way. That could give you guys some clues if it's affecting only fK (sound little absurd, but who knows). :D

Edit: Just looked a bit of AK's ramdisk..it seems that they are using the following:

/system, discard, writeback
/cache, writeback
/data, discard

So they are using discard+writeback combo only for /system..maybe using that combo with /data caused the issue?

That could be one thing to try..but still I can't see why it shouldn't work with discard+writeback combo for /data also? But I'm no kernel pro ..maybe that's why I can't see it :D
[Samsung Galaxy Nexus] ak:
I have done a lot of test with fstab, and i have saw sometimes, not always, bootloop with "discard+writeback" applied to /data partition.

No "discard" for /cache because sometimes i have found little lags during wake up of the phone.

https://github.com/anarkia1976/AK-ramdisk/blob/jb-initram-4.2.2-mainline/ramdisk-4.2/fstab.tuna
[Samsung Galaxy Nexus] whitedragonz83:
Gingerbread,

I've been on CFQ since you replied to this thread about the IO schedulers a day or two ago. This feels much closer to the response I want and am very happy thus far with CFQ. Hopefully I'll get a better feel when I finally get to about the 1 week mark without rebooting.

Thanks for your help!
[Samsung Galaxy Nexus] myvijay:
Notifications for FKU

I was looking for an option to enable notifications when a new nightly is available for the device. I suppose its not there so this is more of a feature request. Guess it would save time for all those obsessed with checking for updates (which of course includes me). Keep up the great work
[Samsung Galaxy Nexus] tsabasid:
Hey guys. I have the latest r376.I hear about those Osmosis settings regarding row scheduler. Is it necessary for me to tweak something or is it already done? If not could someone please post the values? Thanks a lot.
[Samsung Galaxy Nexus] Ronaldo Forenucci:
I forget what is currently hard coded, but the numbers from osm0sis' latest (25 April) iosettings file are:

"deadline"

echo 250 > /sys/block/mmcblk0/queue/iosched/read_expire;

echo 2500 > /sys/block/mmcblk0/queue/iosched/write_expire;

echo 1 > /sys/block/mmcblk0/queue/iosched/writes_starved;

echo 1 > /sys/block/mmcblk0/queue/iosched/front_merges;

echo 8 > /sys/block/mmcblk0/queue/iosched/fifo_batch;

"row"

echo 100 > /sys/block/mmcblk0/queue/iosched/hp_read_quantum;

echo 75 > /sys/block/mmcblk0/queue/iosched/rp_read_quantum;

echo 5 > /sys/block/mmcblk0/queue/iosched/hp_swrite_quantum;

echo 4 > /sys/block/mmcblk0/queue/iosched/rp_swrite_quantum;

echo 4 > /sys/block/mmcblk0/queue/iosched/rp_write_quantum;

echo 3 > /sys/block/mmcblk0/queue/iosched/lp_read_quantum;

echo 12 > /sys/block/mmcblk0/queue/iosched/lp_swrite_quantum;

echo 10 > /sys/block/mmcblk0/queue/iosched/read_idle;

echo 25 > /sys/block/mmcblk0/queue/iosched/read_idle_freq;

"cfq"

echo 4 > /sys/block/mmcblk0/queue/iosched/quantum;

echo 80 > /sys/block/mmcblk0/queue/iosched/fifo_expire_sync;

echo 330 > /sys/block/mmcblk0/queue/iosched/fifo_expire_async;

echo 12582912 > /sys/block/mmcblk0/queue/iosched/back_seek_max;

echo 1 > /sys/block/mmcblk0/queue/iosched/back_seek_penalty;

echo 60 > /sys/block/mmcblk0/queue/iosched/slice_sync;

echo 50 > /sys/block/mmcblk0/queue/iosched/slice_async;

echo 2 > /sys/block/mmcblk0/queue/iosched/slice_async_rq;

echo 0 > /sys/block/mmcblk0/queue/iosched/slice_idle;

echo 0 > /sys/block/mmcblk0/queue/iosched/group_idle;

echo 1 > /sys/block/mmcblk0/queue/iosched/low_latency;

RF
[Samsung Galaxy Nexus] sspunkky:
Has someone tried this kernel on MIUI v5 3.5.3 ?

Has someone tried this kernel on MIUI v5 3.5.3 ?
[Samsung Galaxy Nexus] tsabasid:
Thanks a lot, they were a bit different.
[Samsung Galaxy Nexus] The Gingerbread Man:
You can open the franco app and allow it to check for you in the 'update' section. I think i saw franco was reluctant towards notifications as that requires stuff running in the back ground using up battery life.

Everything you need is already all hard coded in so you don't need to worry about it

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] osm0sis:
/system ro,noatime,discard,noauto_da_alloc,barrier=0,data=writeback
/cache noatime,discard,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0,data=writeback
/data noatime,discard,nosuid,nodev,nomblk_io_submit,errors=panic,noauto_da_alloc,barrier=0

Ah you're right, I was mistaken. It's only there for system. I think your hypothesis is probably correct, especially since data=ordered is the default. Great work here! :) Come back to us some time. ;)

Very good info! Thanks anarkia. :D You have discard for cache in Rubik right now at least from what I see though. Do you still run your trim script on cache to make up the difference?

Almost! We're missing deadline here still, but I think all the other devices have them now. :good:
[Samsung Galaxy Nexus] Ryandroid86:
Im new to the GN scene. I am currently running Paranoid 3.5 with Rubik 30.

how does this Kernel compare? I like how smooth rubik is... but I hate the contrast and gamma changed in the display as a default. Im always changing it back after each reboot.

Id love to hear opinions between the two.
[Samsung Galaxy Nexus] ak:
i think you are into the wrong thread ... This is franco and not rubik ... please leave discussions into the right place.
[Samsung Galaxy Nexus] osm0sis:
Both are good. Try them yourself and make up your own mind. ;) It's all about what works best for your usage and ROM combo, though kernel devs do try to iron out differences as best they can to make it work equally well across all ROMs.

---------- Post added at 01:21 PM ---------- Previous post was at 01:20 PM ----------

:p

[MENTION=3685904]anarkia1976[/MENTION] So now that you've removed discard from cache, do you still run your trim script on cache to make up the difference?
[Samsung Galaxy Nexus] Ryandroid86:
Clearly I can read... which is why I stated "how does this kernel compare?"

Im interested in moving to this kernel if its comparable.

No need to jump down my back. Im not a noob. ;)
[Samsung Galaxy Nexus] Sik-1:
You have to be a noob if after a reboot you always have to change your settings back to how you like , they have apps with the feature to apply on boot you know
[Samsung Galaxy Nexus] osm0sis:
Alright keep it civil guys.

We discourage direct comparisons to be respectful to all the excellent devs doing great work. Like I said, no harm in trying and seeing which you like better. Of course there is Trickster or f.Ku or init.d to set colors and other settings on boot, let's leave it at that.
[Samsung Galaxy Nexus] timbck2:
I've encountered a problem with the Lightflow application where it hangs at startup (and doesn't do LED notifications like it's designed to). I thought it was an issue with my ROM (XenonHD) so I reported it in that forum but I also sent an email to the developer of Lightflow. He says it's a bug in some custom kernels that causes "ls -lR /sys/devices" (which Lightflow does at startup) to hang. I just wanted to report it here, even though it strikes me as finger-pointing since he also told me that command isn't even necessary on the Galaxy Nexus and he's working on a workaround.

Sent from my toro or grouper
[Samsung Galaxy Nexus] Ryandroid86:
sorry to disturb the force around here. Sheesh :rolleyes:

Ill give it a try regardless.
[Samsung Galaxy Nexus] Sik-1:
Its cool the force is still strong and since you flash so much how about using an init.d color script to always have it how you like until you change roms, so that the kernel shouldn't matter :D:thumbup:
[Samsung Galaxy Nexus] Ryandroid86:
Which I intended to do one of these days. Just haven't found the time. Im using trickster in the mean time. But thanks.
[Samsung Galaxy Nexus] Sik-1:
Cool no doubt
[Samsung Galaxy Nexus] ExodusC:
Hey everyone, I just picked up a Verizon Galaxy Nexus as an interim phone until my contract with Verizon is up, then I'll switch over to a GSM carrier with whatever the latest Nexus phone is at the time.

Anyways, from what I can tell, franco.kernel runs on the Verizon Galaxy Nexus, but I was wondering if it plays well with CyanogenMod. Specifically, the nightlies. I know Franco has a Nexus 4 right now so I assume it is his primary phone, but does the Galaxy Nexus franco.Kernel still get semi-regular updates?

Sorry for being out of touch, but I've been off Nexus devices for a long while and am just getting back to them. Thanks in advance!
[Samsung Galaxy Nexus] jcmm11:
The kernel is pretty mature at this point and doesn't really need regular updates. If there's a problem it will get fixed. He is planning on releasing an official 'stable' as soon as the finals are finalized (pretty much done for row and cfq) but the latest nightly is super stable as is.

Should work fine with cm nightlies. I'm running carbon (sweet Rom) nightlies (cm based) and it's fine.
[Samsung Galaxy Nexus] sspunkky:
I am going to reply to my own question.

Finally I took the risk and flashed Milestone6 on my phone running MIUI v5 3.5.3 and so far it's working like a charm.
[Samsung Galaxy Nexus] ExodusC:
Good to hear. I hope that when the next version of Android hits (since presumably the Galaxy Nexus will get it officially- I hope) Franco will be able to still build his kernel for us for it.
[Samsung Galaxy Nexus] nikodr:
I am on 4.1.2 stock and with this kernel r300 I have been using the phone for 2 days 48 minutes and I have 57% of battery still left .Though I didnt use much wifi ,for vacation or when you are somewhere with no access to power supply or charger ,it is awesome :)
[Samsung Galaxy Nexus] Sharks8:
Cheater, the real challenge is to get a good battery life with 4.2.2 :p
[Samsung Galaxy Nexus] brenopapito:
Translate franco.Kernel updater was very difficult, but I think it looks good!

:D
[Samsung Galaxy Nexus] wtr_dhd:
I can't seem to find it back.. maybe somebody wanna help me.

What is the stock GPU frequency and which one is used in the r376 franco nightly ? And I don't think it is possible to alter the GPU frequency yourself (i.e. with Trickster mod) ?
[Samsung Galaxy Nexus] mono28aug:
384 :) yes its possible if the kernel has this option tuneable... I mean this freq is hard coded... Afait
[Samsung Galaxy Nexus] Godra:
Stock GPU freq is 307 MHz and GPU in franco kernel is OCed to 512 MHz
[Samsung Galaxy Nexus] wasdf:
Hi... it's me.....again :p

Just want to ask something off-topic but related to GN (All member in this thread are GN users right?)

Is there any one having wifi disconnect problem in sleep mode?

I have serach about many keyboards with google like "4.2 wifi sleep disconnect" but I can't find any actually fix...

I am having the same issue like the below link

http://code.google.com/p/android/issues/detail?id=40792

wifi only get disconnect WHEN phone in sleep mode (For sure, I have already tried to set wifi sleep to NEVER and untick wifi optimization but no hope )

finally I serach "galaxy nexus wifi sleep disconnect"

and the first result come out this thread

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

There is a temporary solution about downloading an app call Wifi Fixer and it will run as a service with some additional battery cost *sigh* so wifi will not disconnect in sleep mode.

I dont know if it is 4.2.2 or GN well known problem... is there any natively fix?
[Samsung Galaxy Nexus] osm0sis:
I was worried I had this last week. The "fix" that I've seen work for many (and worked for me) has always been setting the Wifi settings to something else and then setting them back to the defaults so that the way they are stored is definitely the same as what it looks like.

They should be:

Keep Wi-Fi on during sleep: Always

Avoid poor connections: disabled (unchecked)

Wi-Fi optimization: enabled (checked)

so set those to something else (Never, enabled, disabled). Reboot. Set them back to the defaults (above), and then reboot again. See how that goes.

Gotta wonder how that "Wifi fixer" affects deep sleep..
[Samsung Galaxy Nexus] mono28aug:
Thanks for correcting me :)
[Samsung Galaxy Nexus] alfiemenace:
Seems to be working for me. Thank you sir!
[Samsung Galaxy Nexus] wasdf:
Sounds interesting and seems working, thanks a lot :good:
[Samsung Galaxy Nexus] wtr_dhd:
Are you sure about this though ?

Just checked in advanced options and look at the GPU clock speed..
[Samsung Galaxy Nexus] Khrushy:
Yes. We're sure. Franco has been clocked at 512 GPU for quite some time now.
[Samsung Galaxy Nexus] wtr_dhd:
Then where does it get the 307MHz info from in Advanced Settings ?

The rom is CM 10.1
[Samsung Galaxy Nexus] mpokwsths:
:eek:

OMG!

Even a baby can understand that the "307" value is grayed out...
[Samsung Galaxy Nexus] wtr_dhd:
Has nothing to do with it.

It simply means you can't adjust it, hence the GPU frequency is hardcoded as stated a few posts before.

Go back to sleep or stop being a smartass :)
[Samsung Galaxy Nexus] whitedragonz83:
Franco's GPU will ramp from 153 to 307 to 384 to 512

http://xdaforums.com/showpost.php?p=39557045&postcount=40473
[Samsung Galaxy Nexus] lightingcloud:
Maybe (just maybe, I don't really get what app are you using) since EVERYTHING is grayed out, the app isn't compatible at all with franco kernel and can't read the correct values?

EDIT: didn't read the last answer, which makes a lot more sense :P
[Samsung Galaxy Nexus] mono28aug:
Bammmmmmm :D

Well bro just use trickster and see if u have the option to change it o not! M on ak and it has
[Samsung Galaxy Nexus] mpokwsths:
Can't adjust it.

So it will not show up in Trickster.

Franco chose not to include the specific interface.

307 "info" is not read from anywhere. It is just grayed out.
[Samsung Galaxy Nexus] The Gingerbread Man:
That right there is your problem :p
[Samsung Galaxy Nexus] shreddintyres:
The GPU is not constantly runing at 512 it is variable and goes anywhere from 153 to 512 depending on the load on the gpu. just like your cpu isnt always set to max neither is the GPU

Edit whoops someone already mentioned this :X
[Samsung Galaxy Nexus] franciscofranco:
r378:

* Revert back to BFQv5, v6 was giving problems to some users so before trying to find out the cause lets revert it for Milestone preparation

* Merge 3.0.75, .76 and .77

* Merge a patch to deadline to make I/O reads a bit faster

* Make deadline I/O the default again, its still my favorite
[Samsung Galaxy Nexus] Wynnded:
La Machine
[Samsung Galaxy Nexus] osm0sis:
Hey does this 3.0.75 soc crash fix also apply to us?

https://github.com/anarkia1976/AK-tuna/commit/723869dfd20365b7efbc3400ecc5fc11f61a14c3

Also still need those deadline and fixed cfq finalized tunables for the milestone at least. :)

Edit: Ah I see you did fix that one cfq tunable that was still a tad off, thanks! Don't see that commit on your github so I just assumed it wasn't. :silly:
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
What's the battery service that the app runs?
[Samsung Galaxy Nexus] neo-X:
Battery stats. You can turn it off in Franco's app under system monitor settings > app

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] Godra:
I'm 100% sure. Flash AK kernel, it will show 307 MHz again, even it's clocked @ 384 MHz.
[Samsung Galaxy Nexus] neo-X:
I thought that screen gets greyed out because you are no longer running stock CM kernel. That's why it doesn't display correctly.
[Samsung Galaxy Nexus] parkson:
378 is dope. Thanks for the fix
[Samsung Galaxy Nexus] Syfer_Fever:
hmm BFQ reverted to v5... i was using BFQ v6 on ARHD ROM and it's very stable, phone uptime was 5 days

but i think it is a good decision, thanks! gonna test your kernel as soon as i get home
[Samsung Galaxy Nexus] Godra:
Yes. Actually, it's because kerenel doesn't use CMs GPU OC and colour profile implementation
[Samsung Galaxy Nexus] wasdf:
Many member here are experiencing random reboot when using BFQ, I seldom use BFQ but for test purpose, I tried to use BFQ and I had random reboot too.......
[Samsung Galaxy Nexus] Efrenjr15:
378 is running smooth with Liquids nightly greats job team
[Samsung Galaxy Nexus] whitedragonz83:
Franco, really happy with the Deadline changes. I haven't even bothered going back to CFQ, which I liked a little over ROW. I'll get a better feel in a few days, but thus far, thanks for the Deadline changes!
[Samsung Galaxy Nexus] osm0sis:
Try it with our winning tunables:

250/2500/1/1/8

:D
[Samsung Galaxy Nexus] Astug:
Thanks, was looking for these. I'll report back how they feel.
[Samsung Galaxy Nexus] Khrushy:
Trust me when I say these are sexy sexy numbers.

Like your lady-friend's chest measurements, but with more I/O speed and less boobs.
[Samsung Galaxy Nexus] emd2009:
nice thanks for this
[Samsung Galaxy Nexus] Empty Hand:
Looks like it's back to the IO scheduler script...until the milestone.
[Samsung Galaxy Nexus] ExodusC:
Anyone else having an issue where their wifi doesn't seem to stay on when the screen is off, regardless of the settings? I don't think it did this before franco.Kernel, but I can't be entirely sure.
[Samsung Galaxy Nexus] Angelakaro:
Already answered, read a couple of pages ago.

Inviato dal mio Galaxy Nexus
[Samsung Galaxy Nexus] parkson:
Can this be done in trixstermod? Have FKU but don't see this options
[Samsung Galaxy Nexus] The Gingerbread Man:
In fku go into custom kernel settings then io scheduler tuning

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bigknowz:
Deadline

New tweak looks really good, thanks guys. Much better than 350 / 2750 / 2 / 1 / 16.
[Samsung Galaxy Nexus] Dark7star:
Can you only do that in the app?
[Samsung Galaxy Nexus] pitchdarkice:
are these settings for deadline io scheduler?
[Samsung Galaxy Nexus] Midomad:
Yes :)

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] bigknowz:
You can use fku, trickster or a script.

Yes.
[Samsung Galaxy Nexus] xFuGiToiDx:
r378 running great with purity 5.4.1.. Thanks Franco. Best kernel for my nexus so far, I've tried ak kernels but I always end up coming back to Franco kernels for its stability and performance. :)
[Samsung Galaxy Nexus] scadilla:
Just for my feeble brain are the settings read_expire = 250, write_expire=2500, Writes_starved=1, Front_merges=1, and fifo_batch=8?
[Samsung Galaxy Nexus] AndyGnex:
Enter the values according to the order that they appear in F.K.U
[Samsung Galaxy Nexus] Blackcrx:
Yup