yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] bunnahabhain:
Same here. Amazing. Simply amazing.

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] kinfolk248:
sourcery sourceress
[Samsung Galaxy Nexus] phishn:
Pre 34-01 a noticeable improvement for me regarding snapiness and smoothness.
[Samsung Galaxy Nexus] bigknowz:
Min stays the same

Min stays at 192, governor stays the same, not sure why you thought I wasn't answering the question properly. Only change is the way the governor reacts to a spike in load. I have done a ton of messing around to get music stutter free since January.
[Samsung Galaxy Nexus] jesssiii:
I'm on that with no reboots. Your phone hardware may need higher voltages. Or maybe try setting the power saver thing from 2 to 0, may help.

Toro GNex
[Samsung Galaxy Nexus] creeve4:
What have you done?
[Samsung Galaxy Nexus] kinfolk248:
okay im gonna give it a few because i wiped 5x and reinstalled everything, if that doesnt work i'll try the power saver first...
[Samsung Galaxy Nexus] MartianCeo:
Is the wake locks improved with the recent test version? Takes forever to get into deep sleep and I had to use greenify to put most of my apps to sleep.
[Samsung Galaxy Nexus] Seraz007:
yes idle drain,i believe, has been limited to the minimum

Sent from my Katana
[Samsung Galaxy Nexus] namtombout:
Have you tried experimenting with io schedulers and/or tuning them. Not sure if it will work or has anything to do with your issue

U.O.E.N.O
[Samsung Galaxy Nexus] creeve4:
I have not yet, currently I'm using BFQ.
[Samsung Galaxy Nexus] Nemed:
Maybe it's too soon to give a feedback, but i haven't noticed any lag episodes nor deepsleep issues
[Samsung Galaxy Nexus] Seraz007:
+1

Sent from my Katana
[Samsung Galaxy Nexus] TheMysteriousOne:
Amazing results with r33.

Moving on to pre-r34 now.
[Samsung Galaxy Nexus] splus:
I posted yesterday that after a ROM and kernel reflash GPS started working OK. But then today it again takes long time, 1-2 min to get a lock, without changing anything in my phone.

I wiped cache and dalvik and flashed pre34 and GPS got a lock in 10 sec. I'll update tomorrow if it stays OK or goes slow again.

Btw, pre34 is flying. It's really fast and apps launch instantly, faster than ever before with any other kernel I tried.

Trying interactive with default max freq but hifreq set at 729 MHz, and BFQ scheduler with RAB 512, Fsync disabled and GPU 512 MHz. Everything is super smooth and responsive. Wow!
[Samsung Galaxy Nexus] d0ge01:
r34

Tested r34, back to r33 due high battery drain, i don't know if it's mine problem or kernel problem, but really high battery drain ( like 15%/hours with little/mid usage )
[Samsung Galaxy Nexus] TheMan0790:
Sounds like a specific issue on your end.
[Samsung Galaxy Nexus] jjjameson:
Everything is default. 1024
[Samsung Galaxy Nexus] parthipanramesh:
The default on Fancy Kernel is 256. Maybe a init.d script overrides the default setting.

Sent from my Paranoid Nexus running Fancy Kernel
[Samsung Galaxy Nexus] sajty:
Lower it to 512 or 256.
[Samsung Galaxy Nexus] KeithLing1115:
These voltages are running great on my phone. I've been skimming this thread and I see some different settings scattered here and there and I've Googled quite a bit but can a few people share their undervolt settings?

One more thing, has the battery saver changed? When I had my t-bolt using leankernel you would set the saver to like 95, it would charge to 100 then it would stop and discharge to the setting of 95 then charge back up to 100. Now it just charges to 95.
[Samsung Galaxy Nexus] evilssj4:
I just flashed pre34-01 and its the first time flashing Fancy kernel on my galaxy nexus (toro), what are the best settings for great battery life and performance? any help will be appreciated thanks! :good:
[Samsung Galaxy Nexus] chikimonke:
The only thing I typically change is the IO to BFQ and the Max to 1344000. I've played with other settings, but this seems to give me the best performance:battery ratio. Super smooth, lasts the whole day with regular usage, can't ask for much more.
[Samsung Galaxy Nexus] evilssj4:
thanks, for the governor do you leave it at ondemandplus? I've read others here use interactive as well.
[Samsung Galaxy Nexus] chikimonke:
Yup, I keep ondemandplus. It's a melding of ondemand and interactive. There's a link to a description and it's tuneables in the OP.

Oh, I forgot, I also raise the RAB to 512 instead of the stock 256.
[Samsung Galaxy Nexus] evilssj4:
Thanks, I changed it to BFQ now and yeah I had changed the RAB to 512. Hopefully I can get better battery life and I will look at the link you mentioned :good:
[Samsung Galaxy Nexus] Godra:
Flashing over franco kernel with wiping cache and dalvik cache is OK? No need to do anything else?
[Samsung Galaxy Nexus] chikimonke:
Shouldn't be, but if you want to give yourself a better chance of everything working as advertised, but don't want to clean flash, you can always wipe system too and then flash your ROM, gapps, Fancy and whatever else you normally flash. Gives you a cleaner install without having to set everything back up like after a clean wipe and reinstall.
[Samsung Galaxy Nexus] Godra:
I will definitely do it in few days because I dont have enough time at the moment. I had some battery drain with franco and I have read few last pages of this kernel thread and it seems like its really good and smooth.
[Samsung Galaxy Nexus] HiM@L:
What's RAB? How do you change that. Coming from another phone..so new in gnex community.
[Samsung Galaxy Nexus] apophis9283:
Rab is read ahead buffer
[Samsung Galaxy Nexus] chikimonke:
Check out Trickster in the play store. It will let you make any and all of the tweaks that you read about in here. It has unofficially become the standard for Kernel tweaking apps.
[Samsung Galaxy Nexus] openlatedotorg:
r33 felt ok but slightly off with battery and responsiveness.

Pre 34 is great so far!
[Samsung Galaxy Nexus] 7175:
I will definitely update soon and check out r6. ;) I've been trying to narrow down this 3-5% battery drain increase per hour in screen-on use since updating trickster but no solid conclusions yet. Just got back to my phone after being away for a week, so I need to go through everything that was changed from then including updates to a few other apps like gmail. I backed up all apks and made a couple nandroid backups a week ago after running continuously great results with r4, so I'll probably flash back to one to double check some things and make sure phone hardware is still consistent.

I read about the issue with the "task-grouping" toggle in trickster which was the main reason I went back to an older trickster and cleared out its data and boot values. One big thing I've noticed is more battery drain with using 192 min_SO opposed to 384 min_SO. I will check if 384MHz was the lowest freq my nandroid backup was running. This might just be my phone or maybe the average cpu load has increased. I will see if this comes up after flashing r6 too. Hope I can narrow things down a bit more soon. Need that holy grail battery life!!
[Samsung Galaxy Nexus] jzero88:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Dope kernel bro. Running smooooooooth, snappy, and bomb battery life. :sweetness:
[Samsung Galaxy Nexus] imam.krismanto:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Can i flash this kernel over stock rom?
[Samsung Galaxy Nexus] namtombout:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Yes. Worst case scenario restore your backup
[Samsung Galaxy Nexus] bolanrox:
boype, would it ever be a possibility down the road to add a update/flash script like imoseyon has with Lean Kernel? Just wondering!
[Samsung Galaxy Nexus] bigknowz:
Dirty Flash Fail

I tried a dirty flash yesterday and I couldn't get past the Google unlock screen. Wipe cache / dalvik got me back on track. Is that because of

optimized ext4 mounting via RAMDISK

?

I was running tiny kernel. Also, wrote a simple script for multi-core scheduling is anyone cares, got tired of going into terminal. I call it grouptask

#!/system/bin/sh

# chmod -R 755 /storage/emulated/o/grouptask

echo 2 > /sys/devices/system/cpu/sched_mc_power_savings
[Samsung Galaxy Nexus] lost_:
Trickster MOD does this. It would set the value to 2 if "Try to group tasks into the least core possible" is selected, and zero not selected.
[Samsung Galaxy Nexus] bigknowz:
Trickster

Yesterday, set to 1 on my phone.
[Samsung Galaxy Nexus] lost_:
I checked before I posted the above. Set to 2 to on mine with latest Trickster

u0_a65@android:/ $ cat /sys/devices/system/cpu/sched_mc_power_savings
2
[Samsung Galaxy Nexus] boype:
The "2" is set via RAMDISK by default on every boot (which is part of my kernel), so no need for any scripts. Trickster sets this to 1 when first disabling and then re-enabling this in the current version, so don't use that option there.
[Samsung Galaxy Nexus] bigknowz:
Ramdisk

Do you have a thought on my Ramdisk question?

I tried a dirty flash yesterday and I couldn't get past the Google unlock screen. Wipe cache / dalvik got me back on track. Is that because of:

optimized ext4 mounting via RAMDISK?

I was running tiny kernel.
[Samsung Galaxy Nexus] lost_:
I stand corrected. I'm glad we went over this. Off topic, I sent a bug report to Trickster author though it's probably already reported. I reckon 2 may have a slight performance hit on rare instances, but at least an option for 1 or 2 should be provided .
[Samsung Galaxy Nexus] harisazmi88:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Could anybody plz give a link for guide to using PGM on GNex.I tried it on purity Rom 4.4 with AK purity.021 kernel but had to pull out the battery to get the device working.
[Samsung Galaxy Nexus] gwindlord:
Actually just install and activate PGM, nothing else. At least it works for me with fancy :)
[Samsung Galaxy Nexus] harisazmi88:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

But even on fancy kernel,the phone just reboots and the PGM app is gone....:(
[Samsung Galaxy Nexus] gwindlord:
Well... maybe the reason is your particular PGM version or its compatibility with some other installed applications... for me it's fine on all versions of fancy.
[Samsung Galaxy Nexus] jaredkzr:
Hey first of all, amazing job on this kernel. I have had very few problems (a few crashes) but amazing battery life.

For some reason I can't get r6 to boot on my Galaxy Nexus. I am running JDX 13.0 which is 4.2.2 and I 'm trying to flash the 4.2.2 kernel version but it hangs on the Google Logo. I have wiped cache repeatedly but the problem persists. Any ideas?
[Samsung Galaxy Nexus] t1.8matt:
with the multi core scheduling, when creating an init.d script, what should the permissions look like? rwxr-xr-x?
[Samsung Galaxy Nexus] namtombout:
Re: [KERNEL][4.2.1][4.2.2] Fancy Kernel (r6) (FEB-13-2013)

Try 4.2.1 then

Sent from my thumbs to your eyes
[Samsung Galaxy Nexus] gwindlord:
Yeah, set 755 there.
[Samsung Galaxy Nexus] pcphobic:
Cool! Thanks for testing. Will flash it tonight.
[Samsung Galaxy Nexus] Charmacas:
I am sorry to say that after a day of usage the slowdowns came back. This morning on my way to work it was really hard sometimes. Apps startet in 5 sec and more and my keyboard strokes were also delayed. Just to let you know boype! :)
[Samsung Galaxy Nexus] splus:
Maybe it's a ROM?

The only ROM around that doesn't have sysui slowdown problem is Cataclysm, AFAIK. Can run it for weeks without reboot, not a bit of slow down. It's stock based, so smooth and bug free, but maguro only, though.

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

With this ROM I haven't had any slow down with ANY kernel I tried.
[Samsung Galaxy Nexus] Charmacas:
Don't think so but maybe. Carbon ROM normally gives me also no slowdowns! :)
[Samsung Galaxy Nexus] bunnahabhain:
Sure that it hasn't sth to do with those carbon nightlys? They're pretty quirky every now and then...
[Samsung Galaxy Nexus] agritux:
i am happy with latest cm nightly and r33

but i dont know gps working or not

i dont use it
[Samsung Galaxy Nexus] Charmacas:
As I said above. That could maybe be the cause. :)
[Samsung Galaxy Nexus] bunnahabhain:
Yeah sorry, just waited to long to hit the reply button finally :o
[Samsung Galaxy Nexus] mpokwsths:
r34 pre here running for a day without any problems. Fast ans smooth!
[Samsung Galaxy Nexus] pcphobic:
How's battery life?
[Samsung Galaxy Nexus] BOY_:
Boype, been running pre-r34 and performance is good but on screen battery life seems to be suffering. I'm actually off work today so I can continue to test. Screen off idle seems as good as r33.
[Samsung Galaxy Nexus] Quarmzz:
It is recommended to wipe cache and dalvik ....

Should I wipe before or after flashing the kernel?
[Samsung Galaxy Nexus] angourakis:
I wipe before and after =P never had a single problem! Also, when flashing a new ROM, I fix the permissions too =)
[Samsung Galaxy Nexus] Quarmzz:
Alright. I'm gonna try just that :fingers-crossed:
[Samsung Galaxy Nexus] flatflo:
I'm wiping only before and i never had problems.

Gesendet von meinem Galaxy Nexus
[Samsung Galaxy Nexus] mrm43:
I am sorry to hear that. I am at 2 days and 7 hours without reboot and it is still smooth for me. Using PA and fancy r33. All stock settings. I am very satisfied with r33. Thanks to Boype.
[Samsung Galaxy Nexus] Riekr:
[MENTION=4615478]boype[/MENTION] is adb in USB debug not working anymore? Tested on 2 PCs and running cm10.1 final and r34 pre

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] Charmacas:
It seems like deactivating USB Debugging made my device lag. Is that possible?

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] Riekr:
Nevermind maybe it's a rom problem. Now it is working even if i don't know why.

I've never noticed it but it could be sine some more service is stared when in debug mode (adb and logging AFAIK)

Inviato dal mio Galaxy Nexus con Tapatalk 2
[Samsung Galaxy Nexus] mrdunn:
My wife's toro gnex is having bluetooth problems with the stock kernel. Pairs fine with Kenwood car radio, but after a few days doesn't work anymore and need to do a factory reset on the radio and repair to make it work again. My gnex doesn't have that problem (Sourcery with r33 or with any custom kernel). Is this a problem with the kernel, the rom or the radio? If kernel, does r33 have different bluetooth code? This has been a problem with her phone/radio since the 4.2.2 OTA update.
[Samsung Galaxy Nexus] The Gingerbread Man:
The only thing you need to wipe when flashing kernels is your arse
[Samsung Galaxy Nexus] TheMan0790:
YES! I laughed so much at this
[Samsung Galaxy Nexus] stevensoaj:
Just wanted to report on r33. Been running great now for 3 days without a reboot. Most of the time I start seeing lags on kernels after about a day, but not on r33.

All default settings except the following:

Read Ahead Buffer: 256 (default?)

Multicore Power Savings: 1

GPU: 512MHz

MPU Voltages: -100mV across the board.

I'm reluctant to test pre 34 because I like r33 so much. The battery life has been great thanks to the timer slack feature. Great job boype! :thumbup:
[Samsung Galaxy Nexus] aHecticLife:
LOLOLOLOL I'm dying here.

& you're welcome for your 2000th thanks ;)
[Samsung Galaxy Nexus] Charmacas:
Now that my ROM runs great again I have to tell you that you miss something great if you don't try pre34. You can always go back to r33. ;)

So what I said above... I am now sure that the slowdowns came from my ROM somewhat. But the nightly for maguro from today is great. I tell you... Great! :)

Sent from my Galaxy Nexus with Tapatalk
[Samsung Galaxy Nexus] bunnahabhain:
Besides the fact that it is an old joke that originated from Trinity himself, i find it doubtful that wiping isn't necessary. As stated in Francos thread numerous times there are leftovers here and there, especially if you come from AK kernel (scripts in data folder). What i am not aware of is wheather it is possible to get rid of the junk via wiping cashe/dalvik cahe. But what i am aware of is that you don't have to wipe anything if you want to flash a kernel after Fancy kernel. Boype stated this a couple of pages back. He designs the kernel the way that everything is handled via ramdisk to get a clean base.
[Samsung Galaxy Nexus] Hexo07:
R33 is running on my purity Rom since few days really smooth and fast.

Can a gnex be better?

Gesendet von meinem Galaxy Nexus mit Tapatalk 2
[Samsung Galaxy Nexus] ReMuSeR:
Purity latest and fancy are fast,smooth,battery good and stable

Thanks dev for this amazing kernel and i really hope to see even better improvmments
[Samsung Galaxy Nexus] x3m.zone:
Running pre-r34 for 24hrs and i must say: wow!

Performance is just awesome: 9074 in Antantu, and battery life is comparable to r33.

Very nice work, dev! Keep up the good work.
[Samsung Galaxy Nexus] sym_m:
what rom you'r using

iGet 8011 on cm10.1 stable
[Samsung Galaxy Nexus] Doublewise:
Sorry I was wrong about process name of 360 launcher. Melvinchng, the translator, told me it's name is com.qihoo360.launcher

Hope you add this in white list for next update. Thanks
[Samsung Galaxy Nexus] jeffcavicchi:
Interesting - on pre R34 I had issues streaming music over bluetooth tonight - a lot of stuttering, which was not present when hardwired into the speakers. Could have been my crappy ISP - I'll test tomorrow and see if I can reproduce. Using Google music on Atom ROM.
[Samsung Galaxy Nexus] motorazrv3:
Yes it can. Give pre r34 a try an you won't regret it.

Gesendet von meinem Galaxy Nexus mit Tapatalk 4 Beta
[Samsung Galaxy Nexus] aHecticLife:
why was I tagged in the post?
[Samsung Galaxy Nexus] x3m.zone:
CM10.1 stable

Cpu:1420/Gpu:512/bfq/RAB:512
[Samsung Galaxy Nexus] bunnahabhain:
Don't have a clue

Galaxy Nexus / Tapatalk
[Samsung Galaxy Nexus] boype:
pre34-02 (test)

Hi,

I have just uploaded pre34-02 for you to test. Changes:

memory optimizations (aiming for long-term smoothness and performance)

small block tweak (making it yet a little snappier?)

The changes from pre34-01 are of course also included:

http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-pre34-02-ext.zip

Best regards
[Samsung Galaxy Nexus] bunnahabhain:
Nice dude - sounds promising! Herzlichen Dank!
[Samsung Galaxy Nexus] Rufufu:
For those who undervolt :

-Can UV increase lag? Or the only consequence of too agressive UV is unstability?

-Do you leave Smart reflex enabled?
[Samsung Galaxy Nexus] stuffynet:
Apps load and process allot faster. Battery drain very good on both pre releases. :good:
[Samsung Galaxy Nexus] sajty:
1) with some hardcore UV,yes (but it more likely cause freeze)

2) yes
[Samsung Galaxy Nexus] Rufufu:
Thank you. I'm at -75mV on each step, seems stable, will see what happen during a few days. Hope my phone will be less hot!
[Samsung Galaxy Nexus] sajty:
I am at -75mV for all too.Only 384MHz and 729MHz step i have lowered by 100mV.Stable for weeks.
[Samsung Galaxy Nexus] pcphobic:
Wow. That's fast... LOL. OK will try 02 instead of 01.
[Samsung Galaxy Nexus] bunnahabhain:
Beware of this nonproductive post:

This kernel is crazy!
[Samsung Galaxy Nexus] L-ViZ:
lulz, got my phone running [MENTION=4773854]720[/MENTION]mhz max :D still smooth, very slight undervolting :)
[Samsung Galaxy Nexus] Quarmzz:
I quoted a part of the OP I wasn't clear about. I wanted to know whether I should wipe those before flashing the kernel or after flashing because it was a little vague.

Thanks for your helpful answer.
[Samsung Galaxy Nexus] sajty:
Wiping anything before/after flashing kernel is useless.But i agree with you,that answer from The Gingerbread Man was a little bit...stupid.
[Samsung Galaxy Nexus] Seraz007:
not stupid, just funny as hell xD

Sent from my Katana
[Samsung Galaxy Nexus] TheMan0790:
It was meant to be nothing more than a joke...although yes, he could have given the answer a little more clearly.
[Samsung Galaxy Nexus] sajty:
So,i didnt get it,that its joke ;).Someone needs help and he gets answer like "you only need to wipe your ass".But everyone has different sense of humor :).
[Samsung Galaxy Nexus] TheMan0790:
I wholeheartedly agree it wasn't the best way to answer someone who needed a hand
[Samsung Galaxy Nexus] Quarmzz:
Alright. Now I know. Very much appreciated.
[Samsung Galaxy Nexus] Gil Smash:
Undervolting and leaving smart reflex on means that smart reflex is going the voltage. If you want the kernel to use your undervolted values turn smart reflex off.
[Samsung Galaxy Nexus] Rufufu:
But why when a leave SR on and I UV too much, the phone freeze?
[Samsung Galaxy Nexus] Gil Smash:
Some of then slots are not governed by smart reflex. I could. Be wrong on the this but that is what I've always heard.
[Samsung Galaxy Nexus] sajty:
I think,that its not true.

1) undervolt

2) turn on SR

3) look at first page of trickster mod

4) what current voltages you see for each steps at the bottom of the screen?

I see voltages,that i set manually,even when SR on.
[Samsung Galaxy Nexus] Gil Smash:
That's true. That's also weird haha. I've heard many times to keep smart reflex off when setting UV values. Anyone with some more knowledge want to weigh in?
[Samsung Galaxy Nexus] The Gingerbread Man:
Man xda is loosing its fun, you don't find that funny, mods on my case about my signature. Jes
[Samsung Galaxy Nexus] sajty:
I think,its really working even with SR on.I remember,that i undervolted Lean kernel with SR on and i immediately got freeze (i undervolted too much).So the value had to be applied.
[Samsung Galaxy Nexus] jesssiii:
Back when faux1234 was active here, he said turn it off. He even had separate kernels with it on and off.

I'm also wondering which sets (or all) of those values to undervolte? Not sure what the differences are. Using trickster.

Toro GNex
[Samsung Galaxy Nexus] Rufufu:
Anddo you change Core voltages and IVA voltages?
[Samsung Galaxy Nexus] sajty:
Never.
[Samsung Galaxy Nexus] The Gingerbread Man:
To effectively under volt smart reflex should be off, otherwise smart reflex with continue to calculate voltages you are just changing the maximum possible value other wise
[Samsung Galaxy Nexus] sajty:
Example.I set 800mV for 384MHz step and left SR on.If i understood you well,800mV will be max voltage,that phone can use for that step.Right?
[Samsung Galaxy Nexus] kinfolk248:
still getting the reboots, boot ani then to lock screen. So idk if that means rom (sourcery sourceress) or a kernel (r33) problem. I tried the set power save to 0, it seemed to reduce occurance but it still happened just less often.

if it helps the last one was a SOD then boot ani and lock screen.

any help pleaselll ;-(
[Samsung Galaxy Nexus] The Gingerbread Man:
OK I'll try to explain to the best of my ability for you guys. So think of the smart reflex system as an automatic under volter, it calculates values for your CPU speeds as you use them allowing everyone's phone to run at their comfortable voltage (what ever the hardware runs with being stable) as everyone's silicone isn't equal some chips use more juice than others. Smart relex sees the maximum amount of electricity it can use and works to stay under what ever is the maximum limit. With me so far?

So keeping smart reflex on, the system is still trying to draw less power than the maximum value allowed, hence where instabilities come from. So when you undervolt with SR off you are setting more strict rules to the juice allowed to each speed without your hardware trying to draw less than you have said is maximum.
[Samsung Galaxy Nexus] Charmacas:
Explanation from boype! :good:

But you all should be more focused on Fancy kernel. :) It's better to open another thread to talk about undervolting.
[Samsung Galaxy Nexus] ReMuSeR:
Coool only small bugs fixes and changes needed on kernel and boommmmmm masterpiece
[Samsung Galaxy Nexus] Charmacas:
You fixed bugs? :confused: Which?