yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] boype:
He's right, I have to take the blame. I apologize. Credits changed at OP, r30 post and github.
[Samsung Galaxy Nexus] AbhishekS:
Is Fast Charge supported by a ROM or Kernel?

RasbeanJelly has no direct option for fast charge. Can I use Fast Charge if I flash Fancy on RasbeanJelly and if yes, then how?
[Samsung Galaxy Nexus] boype:
The kernel has fast charge.

You can activate it with

1) a kernel control app, like Trickster mod (free in the Play Store)

2) with a terminal command: 'echo 1 > /sys/kernel/fast_charge/force_fast_charge'

3) with this init.d script (this way it will always be turned on on boot)

#!/system/bin/sh

echo 1 > /sys/kernel/fast_charge/force_fast_charge
[Samsung Galaxy Nexus] sajty:
Again,i didnt care about credits.But you are saying something,thats not truth and i will not sit back only because you are the osm0sis.And you are wrong again,i tested those values before i noticed boype.So please,stop attacking me.

boype,please change OP,maybe after that he will stop saying those lies.
[Samsung Galaxy Nexus] osm0sis:
sajty, by "fair enough" I meant "point conceded" which basically means "you're right".

I'm not sitting here trying to pull rank on you. I already agreed with you, and boype confirmed you're not at fault. Let's drop it. I'm good if you're good. Thanks boype once again for the speedy response time. :)
[Samsung Galaxy Nexus] sajty:
OK.Sorry,but if i am "under attack" and i am convinced,that without justification,i will defend myself to the last breath :highfive:

And i dont think,its boype's fault.I wrote only "franco thread",but not particular name.
[Samsung Galaxy Nexus] boype:
Alrighty then, case closed :highfive:
[Samsung Galaxy Nexus] sajty:
Btw.,now testing CFQ tunables from franco thread (dont know,who is author,maybe osm0sis will know),but so far it looks,that with Fancy is playing better with tuned BFQ than CFQ.
[Samsung Galaxy Nexus] osm0sis:
Yeah bfq is a bit faster than cfq, even after we fine tuned them both. All scheduler and governor tunables from f.K are the work of the Franco's Dev Team tuning collective. :)

Best just to point boype to the actual commit on Franco's github. I had to accommodate the weird stepwise counting for those tunables to come up with the actual values to hardcode:

https://github.com/franciscofranco/Tuna_JB_pre1/commit/87f65eccb3a23143f9d6c380fb89e6c23b8131d1

It all depends on what HZ is at though. As long as it's still the default 128 then that commit should work. If it's 100 like it is on AK from anarkia bringing stuff down from 3.4 then it'll probably have to be the commit from Franco's N7 git (or N4 if you pulled the 3.4 cfq as well).
[Samsung Galaxy Nexus] sajty:
Its interesting,that you were able to tune BFQ so good with only few changes made and CFQ seems to be slower even with so much tuning.

Btw.,maybe you will know the answer or have some idea.All schedulers are working good with Fancy,but deadline has extremly low read speeds.Do you have any idea,what can cause that?Read speed is around 6-10 MB/s,which is terrible (should be around 25MB/s).
[Samsung Galaxy Nexus] osm0sis:
Yeah it is interesting. bfq is just the better of the two overall, and it shows. pkgnex did ANOVA statistical DOE analysis of 6 people's testing results using highs and lows for each to find the relationships between the cfq tunables and identify the sweet spot, so it's better than default cfq but even then bfq still feels a bit better because it slices things differently.

Not sure what's up with deadline. There was a 0 latency patch to it recently on f.K that might help, don't think Fancy has that yet. Cheers. :)
[Samsung Galaxy Nexus] The Gingerbread Man:
When you get as far as deadline you can throw a high five over to me ;)
[Samsung Galaxy Nexus] Charmacas:
BFQ or CFQ... I use SIOplus! ;) Runs just great!

And credits... yeah they are going out to [MENTION=4615478]boype[/MENTION]! :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] sajty:
SIOplus has the best write speed over all schedulers (around 15MB/s),boype has done fantastic work.However,BFQ is still absolute winner for me :).
[Samsung Galaxy Nexus] agritux:
İs anyone faces this problem? İ am using latest cm nightly with latest fancy ext kernel. While i am surfing on the web with stock browser, it closes sometimes without any error. İ asked it in cm topic but they said no problem here. İ flashed rom with clean install (reflashed) problem is still there. :( i am using stock fancy kernel settings. Not changed anything. İs it releated with kernel?
[Samsung Galaxy Nexus] creeve4:
What tunable values do you use for BFQ?
[Samsung Galaxy Nexus] sajty:
back_seek_penalty = 1

raising_max_time = 0

slice_idle = 0

But those values are already hardcoded.raising_max_time tunable is dynamicly changing,so dont panic,when you will se there different number ;).
[Samsung Galaxy Nexus] Droiddude24:
Did you get that fix? I'm having the same pronelm
[Samsung Galaxy Nexus] Rufufu:
I'm using 14th nightly and chrome, and it is working well.
[Samsung Galaxy Nexus] wictor1992:
Great Kernel, very smooth and nice Performance! I had laggs with Franco and AK, buth this one runs smooth as butter with PA 3.60. Good work!
[Samsung Galaxy Nexus] Charmacas:
[MENTION=4615478]boype[/MENTION] : Look what Franco wrote about one of your commits. Worth a look.

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

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] sajty:
Hm,i must say,that from the great one's hand it looks suspicious.Whats going on in this commit?
[Samsung Galaxy Nexus] boype:
In my personal opinion, it is not as dramatic as he describes it.

I replied to him here, you can read what's going on in this one:

http://xdaforums.com/showpost.php?p=42656874&postcount=6945
[Samsung Galaxy Nexus] okanb3:
I read it too but i dislike Franco's comment. Because this is an custom kernel, not a stock kernel. I think none of common viruses gonna say, "hey there is a way for to make me unkillable, let's do that!"

Also as far as i know you need SuperUser permissions to edit that file.
[Samsung Galaxy Nexus] boype:
My thinking exactly, but I cannot deny franco has a point, even though the 'problem' is not as much of a problem as he describes it. As a developer, security should be the most important factor.

Still, I know what to do to fix the slight security risk.
[Samsung Galaxy Nexus] okanb3:
And that makes you a great developer. Thanks for sharing it with us.
[Samsung Galaxy Nexus] boype:
Can you please check whether you have a folder named 'module' in /system/lib/ ? This would help with identifying the problem.

I suppose the ',odule' part of the error message is just a typo.
[Samsung Galaxy Nexus] Seraz007:
hmm this kernel saved my day :p:D

battery percentage was droppin overnight......switched to this and its gone :good: :):cool:
[Samsung Galaxy Nexus] Inpain:
My issue is now fixed, i created the folder and it worked :D

Thanks boype :highfive:
[Samsung Galaxy Nexus] boype:
Thank you for your input. I was not aware there were ROMs without this folder. Now that I know it, I can implement automatic creation of the folder.
[Samsung Galaxy Nexus] boype:
r31 available

Hi again,

r31 is ready for download. Here's the change log:

updated to Linux 3.0.82

ondemandplus governor: fix adaptive timer_rate (the adaptive timer rate was never applied due to a coding-mistake)

prevent Android OS to change the oom_score_adj value if it has been set to -1000 by the user (launchers are 100% bullet proof now. period.)

block: disable iostats

fixed issues for some users where the WiFi fix could not be executed

few other minor things

Best regards and sorry for double post.

[EDIT] I have updated the knowledge base article of the ondemandplus governor with additional information about the dynamic timer_rate.
[Samsung Galaxy Nexus] agritux:
speedy gonzales :) thanks!
[Samsung Galaxy Nexus] pcphobic:
Cool! Flashing now!
[Samsung Galaxy Nexus] boype:
Knowledge base: WiFi DTIM skipping override

Another post to be linked to the OP. It explains a feature I added a few releases back, but did not mention it so far because I wanted to give a detailed explanation first.

If you are lazy, look at the bottom of the post for a summary.

What is DTIM (skipping)?

DTIM stands for "delivery traffic indication message". A DTIM is sent to your phone by the wireless access point, when there is data the access point wants to transmit. For example, when there's a Whatsapp message incoming, it is reaching the wireless access point, which then notifies your phone that there's something incoming and it has to get ready to receive it. This notification is handled by DTIMs.

More information on DTIM can be found here: http://en.wikipedia.org/wiki/Delivery_traffic_indication_message

Now what's the big deal with DTIMs? The Broadcom WiFi driver in the kernel is set to not receive each DTIM when the phone's screen is off. This is obviously done in order to save some battery, so that the phone doesn't have to get out of idle so often. This behavior is called DTIM skipping. A negative effect of DTIM skipping, however, might be that messages (like Whatsapp messages) are received with some delay.

So what is DTIM skip override good for?

DTIM skip override lets you choose if and how many DTIM requests are ignored when the phone's screen is off.

Just to give an example, I have set mine to skip no DTIMs whatsoever to get quicker notifications.

I have not made any specific tests by how much faster stuff arrives. I just feel like it does ;)

What is the actual impact on battery life?

That depends on the wireless network you're in. If you're signed-in to a network with many clients and a lot of traffic, disabling DTIM skipping will probably affect your battery life some more. When you're in a private wireless network (like the one in your home), disabling DTIM skipping is most likely not affecting your battery life at all.

Personally, I cannot see any negative effects on my apartment's wireless.

How to enable the DTIM skip override

This is possible via the following sysfs path: /sys/module/bcmdhd/parameters/dtim_skip_override

A value of 1 disables DTIM skipping. A value of 0 simply uses the stock behavior. Any value above 1 sets the value, which nth DTIM request should be processed by your phone. E.g., if you set it to 3, each third request will be processed.

The default value is 0, which makes it behave the way you always used to know it (and makes your phone skip DTIMs).

You can activate it via terminal, e.g.:

su
echo 1 > /sys/module/bcmdhd/parameters/dtim_skip_override

To make it apply on each boot, use the following init.d script:

#!/system/bin/sh

echo 1 > /sys/module/bcmdhd/parameters/dtim_skip_override

Long story short

'echo 1 > /sys/module/bcmdhd/parameters/dtim_skip_override' disables DTIM skipping when the screen is off and may provide you faster message delivery (probably at the cost of increased battery drain).

The default value is 0, which reflects the behavior you always used to know.
[Samsung Galaxy Nexus] phishn:
Ran into an issue on r30, 30 hours uptime, where the phone would only use 537 mhz, which was my highest screen off setting, when the phone was not in deep sleep. Based on the sleep percentage it looks like it was sleeping at 192 mhz. Normally I'd see a majority of cpu states percentage as deep sleep and 192 mhz when woken. This is with ondemand plus governor.
[Samsung Galaxy Nexus] quickstang:
Can someone post a screen of what this looks like in terminal when activating it? When I type it in I get a not found message.

I know I'm doing something wrong.
[Samsung Galaxy Nexus] zoomy942:
I went reading through it and didn't see the default setting?
[Samsung Galaxy Nexus] CCaaNN:
Default is 0

I was looking for this kind a code for wifi over a year. I can not thank you enough boype :beer:

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] iferlive:
[MENTION=4615478]boype[/MENTION] As a polite request could you add the temperature limit settings like in lean kernel? My phone usually gets too hot but when using lean kernel with this temp control is significant cooler.
[Samsung Galaxy Nexus] boype:
Did you type 'su' before? Because you need to :) I'll add it to the knowledge base post.

I'll definitly check it out!

What he said :) I will add this to the knowledge base post too.
[Samsung Galaxy Nexus] quickstang:
[MENTION=4615478]boype[/MENTION] or anyone, here is my screen shot. What did I forget or screw up?
[Samsung Galaxy Nexus] boype:
Looking good! There's no confirmation message like 'successfully applied' or anything.

To check if it was applied, type this:

cat /sys/module/bcmdhd/parameters/dtim_skip_override

If it returns the value you were trying to set, all is good.
[Samsung Galaxy Nexus] chikimonke:
Hey boype, great work. Have you had a chance to check out Frandom yet? Here is a link to information regarding it if you are still interested and curious. Thanks
[Samsung Galaxy Nexus] bigknowz:
Echo

echo 0 > /sys/module/bcmdhd/parameters/dtim_skip_override

This sets the value to 0. Replace 0 with another value if you want.
[Samsung Galaxy Nexus] quickstang:
What are most of you testing for the value?
[Samsung Galaxy Nexus] boype:
I use / recommend '1' (= no DTIM skipping).

If you notice any weird battery drain change it back to 0 (stock / default).
[Samsung Galaxy Nexus] bigknowz:
Wifi Fix

[MENTION=4615478]boype[/MENTION], is the wifi drop still an issue, or fixed in r31?
[Samsung Galaxy Nexus] sajty:
Good point.
[Samsung Galaxy Nexus] boype:
It's still an issue and it is not kernel related. I have created a workaround though (see OP).
[Samsung Galaxy Nexus] Charmacas:
I have to report that I definitely notice a good improvement of battery in r31. I think it's the new idle algorithm but maybe you also did some other stuff which you stated as minor. ;)

Great job! As usual! :)

Here are some screenshots:

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] sajty:
boype,maybe another feature,that could be added,if you think,that it will be useful.You have already implemented possibility to turn on/off SR for MPU,IVA and core too.What about addind possibility to change also min calibrated voltages for MPU,IVA and core?Again can be found in Lean or AK for example.At least for ext version it could be interesting (i used this feature with every kernel,that was offering this).
[Samsung Galaxy Nexus] stevensoaj:
Haha, I asked for this exact feature earlier today via PM. Funny how that works.
[Samsung Galaxy Nexus] sajty:
Always good,when new feature is requested by more users.That could reason boype to implement this :).
[Samsung Galaxy Nexus] giorgis91:
How is this kernel compared to air kernel? I'm interested mostly about battery life

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] apophis9283:
I suppose it depends on settings in the end, but ive abandoned hope for all other kernels, for this one. Havent even thought about flashing another kernel.
[Samsung Galaxy Nexus] aHecticLife:
It depends on your phone but I've switched to Fancy because of stability, performance and battery

All three are excellent for me
[Samsung Galaxy Nexus] bigknowz:
System UI has Stopped

Getting system ui has stopped after I flashed fancy kernel. I reinstalled my ROM, still getting the error. Thought reinstalling ROM fixes system ui. Any and all thoughts appreciated.
[Samsung Galaxy Nexus] namtombout:
Never heard of a kernel causing system ui error, but what do I know. You wipe davlik and cache or flash any mods?

I'd backup sdcard using adb then wipe device completely if you haven't done it lately and have the time

U.O.E.N.O
[Samsung Galaxy Nexus] Efrenjr15:
Liquid 2.6.5 with this Kernel are by far the best.

i think i can stop looking for a better kernel now cause ive found it :p
[Samsung Galaxy Nexus] zoomy942:
This is the only kernel I've seen that prevents the 4.2.2 lag and studder
[Samsung Galaxy Nexus] klobkelosh:
Correct me if I am wrong, but this is the only gnex kernel under active development. Loving it by the way. Thank you boype for keeping my device relevant for a little longer.
[Samsung Galaxy Nexus] Droid-21:
Liquid 2.6.5? does not exist.

LiquidSmooth v2.5 - maguro - 05|27|13

http://xdaforums.com/showthread.php?t=2232615&page=58

just that.
[Samsung Galaxy Nexus] pcphobic:
Maybe he is a special test user testing some unreleased version that is being developed? LOL
[Samsung Galaxy Nexus] boype:
... and I'm not going to go over to Nexus 4 or anything else within the next year or so. I'm perfectly happy with my Galaxy Nexus, which I only possess for half a year now. This phone has everything I need.

And I don't have the money for any other phone ;)
[Samsung Galaxy Nexus] Charmacas:
But if you're going to move to another phone. Please tell us! :) I am personally following the news of the Moto X.

Is it somehow possible to tell the system to not kill the actually opened app when locking it?

I ask because I am going to work by subway and so I have to switch trains often. I am playing a game, then have to lock it for train switch and sometimes the game got killed in the background. This is annoying especially when you played a level near the end. ^^
[Samsung Galaxy Nexus] agritux:
i am very lucky

because this is my second phone same as with boype :)

i am using his kernel and his rom about 1 or 1.5 year :)

thanks boype
[Samsung Galaxy Nexus] quickstang:
As of now, the Moto X seems to be a disappointment spec wise. If the specs hold true, all it'll be is a mid range phone. If so, it may be doomed.
[Samsung Galaxy Nexus] sajty:
I love youuuuuuuuu! (no homo :))
[Samsung Galaxy Nexus] pcphobic:
Yup, the GNEX is still good.
[Samsung Galaxy Nexus] Inpain:
[MENTION=4615478]boype[/MENTION]

My WiFi keeps dropping w/e the phone goes into Deep Sleep now, using r30 ext , and i have the wifi fix too. I checked my WiFi settings and it's set to ALWAYS be on, and using TricksterMod i have the WiFi signal boost set to ON for when it goes into sleep.

Any idea why it keeps going Off ?
[Samsung Galaxy Nexus] ReMuSeR:
I have money for nex 4 but developers and supprt and everyday fresh relasses are keeping me on this phone and im not moving untill updates for roms and kernels stop coz so far im in love with my phone no laggs no buggs amazing but only this wifi drop is getting me crazy sometimes hope someone comes with a fix
[Samsung Galaxy Nexus] berliozz:
Has anyone encountered such problems:

- on r30 release my phone goes to deep sleep, I can't swith on it after removing a battery. First time i switch it on only after several hours with battery and sim remove, second time I can ON it after reload battery and sim;

- on r31 release my battery drain to quickly, after 8 hours was last 61%. On r29 version battery drain on day was 35-40% per 12 hours and total time was 26-27 hours by one charge.

No new software on this period, now new firmware only kernel change from r29 -> r30 -> r31

With every update i do Clear Dalvik Cache and Chache partition.

Does any idea how to fix it?
[Samsung Galaxy Nexus] Charmacas:
I have no problem at all with all the kernels you mentioned and you're the first talk about such.

What ROM are you using?

Did you try a clean install?

Do you run any scripts?

Do you undervolt?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] berliozz:
Paranoid Android 3.60

Yes, ROM was installed on fully wiped system, with format all data portitions.

No, clean install without any tweak and mods.

No, stock voltage.

Power tutor app https://play.google.com/store/apps/details?id=edu.umich.PowerTutor on R29 and R30 kernel show average power usage – 383mW. On R31 I see 830mW.

I can attach dmesg if it will help.
[Samsung Galaxy Nexus] albsat:
If this phone had a 3000 mah battery like that of note, I would keep it happily for another one or two years.
[Samsung Galaxy Nexus] Lancez:
R31 with latest AOKP nightly :D
[Samsung Galaxy Nexus] Echo5Kilo:
That was the longest run-on sentence I've ever read. Well done, sir.
[Samsung Galaxy Nexus] sajty:
Probably broken dot key.
[Samsung Galaxy Nexus] billouetaudrey:
Hi, try to uninstall google play service and reinstall it

My phone don't go to deep sleep and after uninstall/reinstall, work fine...

Sorry for my bad english...

Envoyé depuis mon Galaxy Nexus avec Tapatalk
[Samsung Galaxy Nexus] quickstang:
I'm out of breath, hold on...
[Samsung Galaxy Nexus] chowy993:
Can you add ssLauncher to the launcher whitelist? Sorry if this has already been suggested/implemented. (Package name is com.ss.launcher)

P.S. To find package name, its a lot easier to use Titanium Backup... (See attached :D)
[Samsung Galaxy Nexus] n2rjt:
Thanks to boype (and the host of others whose patches and suggestions have made it into Fancy) GNEX is still good. Before I found Fancy, I was actively shopping. My charging hardware is somehow messed up to where the phone usually thinks it is charging even when it isn't connected to anything. That goes well with the solar panel prank apps but otherwise sucks. With this kernel I still get 10 hours with typical use, which is less than most of you report but much better than the 3-4 I was getting before.
[Samsung Galaxy Nexus] chikimonke:
Your charging issue usually means one of the pins on your usb connector is bent and making contact where it shouldn't. This can make the phone think it's charging when it is not.

Also, when comparing battery stats I think we really need to start the trend of stating Toro vs Maguro. Toro has the LTE radio which is an absolute hog for battery, and tends to skew battery results quite a bit. Now I'm not certain, but I believe the standard GSM radio is also more friendly than the CDMA radio found in the Toro as well.
[Samsung Galaxy Nexus] boype:
The package name is not necessarily equal to the process name! That's important.

ssLauncher is not yet om the list, but I'll add it if you can give me the process name.
[Samsung Galaxy Nexus] GamaX320:
running r31 with lastest night Vanir very nice and fantastic batter life
[Samsung Galaxy Nexus] giorgis91:
Hi guys I'm installing the latest ext version. Is it normal that it is taking up to 10 minute to boot? Seems I'm stuck at the X logo
[Samsung Galaxy Nexus] Seraz007:
yea which rom are u on?

Couldnt get the kernel too boot on a rom as well (forgot which one)

R31
[Samsung Galaxy Nexus] cmoG530:
What x logo? And if you came from another kernel, then you may want to flash the ROM again. Then flash kernel.
[Samsung Galaxy Nexus] giorgis91:
I'm on latest AOKP nightly
[Samsung Galaxy Nexus] Seraz007:
hmm havent tried aokp but like yours, couldnt get the r31 kernel to boot on another rom as well :confused::(
[Samsung Galaxy Nexus] giorgis91:
Sorry, for "X logo" I mean the nexus boot logo. And yes, I reflashed first the rom and then the kernel.
[Samsung Galaxy Nexus] sajty:
10 minutes definitely is not normal.
[Samsung Galaxy Nexus] zoomy942:
Which ROM did you have trouble with?
[Samsung Galaxy Nexus] Seraz007:
cant remember sorry :( :o
[Samsung Galaxy Nexus] boype:
First boot can take up to 20 minutes. 2 - 5 minutes is normal though.
[Samsung Galaxy Nexus] chowy993:
I didn't know that, thanks. (I'm relatively new to this world ^.^)

What about using the 'Show CPU Usage' option under Developer Options?
[Samsung Galaxy Nexus] sajty:
I really dont think,that boot can take so much time.Never had longer booting time than 3 minutes,common boot is shorter than 1 minute.20 minutes is insane :D.
[Samsung Galaxy Nexus] pcphobic:
The first time boot normally takes around 5 minutes.
[Samsung Galaxy Nexus] :
10 min seems long :3 anything 10 or longer I would say make sure you have done a full wipe (via fastboot) and make sure your battery isn't going because a bad battery can cause all kinds of problems

Edit: it will Also depend on how much data you have on the device, without a full wipe and install of you have lots of apps and such it will take longer because of trimming
[Samsung Galaxy Nexus] n2rjt:
My first boot sits on the X logo for about ten minutes since this kernel trims the filesystems at that time. Be patient, allow 20 minutes before giving up. The long first boot is worth the wait!
[Samsung Galaxy Nexus] boype:
I don't know if that one displays package or process name...

Just use the method I described here.