yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] chowy993:
The reason I am asking about alternative methods is because using the terminal method doesn't seem to list where ssLauncher is hiding.

No matter though, this kernel is so smooth and efficient that ssLauncher hasn't been killed on me yet (^.^).

Keep up the good work on Fancy Kernel!
[Samsung Galaxy Nexus] albsat:
[MENTION=4615478]boype[/MENTION]

Just curious. What Rom is on your phone?
[Samsung Galaxy Nexus] Tex99:
hi guys, this kernel has the OTG support ??
[Samsung Galaxy Nexus] Pelide:
Yes :) vai tranquillo, funziona senza problemi

Tapatalkeggiato - Improve SwiftKey http://goo.gl/xKYfc
[Samsung Galaxy Nexus] n2rjt:
Yes, works well for me.
[Samsung Galaxy Nexus] :
[MENTION=4615478]boype[/MENTION]
[Samsung Galaxy Nexus] Inpain:
I flashed r31 and the problem is gone, so i guess the wifi fix caused the drops for me ?
[Samsung Galaxy Nexus] JonBsbB:
How do you get the OTA?
[Samsung Galaxy Nexus] quickstang:


---------- Post added at 11:03 PM ---------- Previous post was at 10:42 PM ----------

Speaking of batteries, I realized just how bad this phone sucks when it comes to battery life.

I installed a battery monitor on my wifes DNA last night & at around 10:25p tonight I was looking at the phone & it said 66% left. I asked her if this was from the time she unplugged it & she was like... Yeah at like 6:30a this morning.

20min shy of 19hrs with 66% left. And no it didn't sit all day either. Pinterest, facebook, Pandora, etc.

I wish my phone did that. The next Nexus better not suck battery wise or I'll be going with a totally different phone. Pretty disappointing when I see stats like that. I'm also running a little larger than stock battery as well.
[Samsung Galaxy Nexus] MizzouBrent:
Agreed. This is worse than my old evo which at the time was the gold standard for horrific battery
[Samsung Galaxy Nexus] Lancez:
which app are you using to do that
[Samsung Galaxy Nexus] tzyn:
That is the "Android Terminal Emulator". You can get it in the PlayStore. For CM10.1 it's preinstalled.
[Samsung Galaxy Nexus] quickstang:
Yep, or Rom toolbox. Built in there, so I deleted the standalone terminal app.
[Samsung Galaxy Nexus] Rufufu:
I noticed that USB OTG with ntfs does not support accentuation. For exemple, a file named "présentation.ppt" will be represented with a chinese symbol instead of "é", and it will be impossible to open the file with any file manager. This does not happen with fat32 drives.

Is it a known issue? Maybe it is ROM related? I'm on cm10.1.
[Samsung Galaxy Nexus] phishn:
I just experienced wifi drops for the first time on r31 ext, no tinkering with the wifi options besides wifi high performance toggle.
[Samsung Galaxy Nexus] boype:
Must be coincidental, as nothing was changed with WiFi. Drops appear on stock kernels as well and devs share the opinion that they are not kernel related. The WiFi fix is something that only happens when you manually execute it. There is no changed code for WiFi in either r30 or r31
[Samsung Galaxy Nexus] phishn:
I can tell you that I had a sent mms message delivery fail last night prior noticing the wifi issues. That might be coincidental too.
[Samsung Galaxy Nexus] berliozz:
Guys, can you say me, what voltage used by default on our phone.

Today I find, that my GN use 4V, in past time it 3,5-3,8V.

Can you explain how to do it?
[Samsung Galaxy Nexus] jeffcavicchi:
Not trying to be a jerk, but in my experience wifi drops were ROM related. On some ROMs they happened constantly, on others not at all, with the same kernel and Android version.

Make a nandroid and try a different ROM and see what happens.
[Samsung Galaxy Nexus] billouetaudrey:
In french yes ...

Settings / Apps / All / " Service Google Play "

And Disable it and Enable it

Or

TitaniumBackup

Remove " Service google play "

And reinstall it with Google Play Store

https://www.joemobile.fr/invitation?membre=Billouetaudrey
[Samsung Galaxy Nexus] JonBsbB:
Does the new r31 not allow you to adjust the voltages? And does the r31 not come in extended yet? I'm running on a toro.
[Samsung Galaxy Nexus] quickstang:
Use trickster

Click extended link in first post & download.
[Samsung Galaxy Nexus] natezire71:
I'm having an issue. I don't even know if it's kernel related. My settings aren't sticking after boot. I've changed the Read Ahead Buffer Size and the governor, they never stick. However, my color settings and misc stuff like Battery Life Extender, Content Adaptive Brightness, etc... All stick after a reboot. I'm using Trickster Mod Pro and it is set to apply after boot.
[Samsung Galaxy Nexus] Cnhamm532:
I've had this same issue on xylon and commotio with AK, butter and fancy. I would think it's ROM and not kernel, but I'm no dev. :confused:
[Samsung Galaxy Nexus] jeff5347:
I noticed on UKG while screen was on and using XDA, g+ or whatever my WiFi would drop. I'm on apophis's AOKP and not one drop. Have used fancy since 26 and have come to the conclusion these drops are ROM related. Also I'm using a toro
[Samsung Galaxy Nexus] natezire71:
I've never had this issue until now. I've been running Vanir for months now.
[Samsung Galaxy Nexus] Cnhamm532:
I found it. Check init.d folder for scripts. That's what was doing mine.
[Samsung Galaxy Nexus] natezire71:
I don't have any int.d scripts that change stuff.
[Samsung Galaxy Nexus] Cnhamm532:
Oh, well i had three. No problems now for me
[Samsung Galaxy Nexus] jeffcavicchi:
Ask Osmosis for a link to his kernel cleaner script. I don't have it handy, but flashing it has often solved similar problems for me.
[Samsung Galaxy Nexus] Cnhamm532:
Try deleting the 02dhokernel script.
[Samsung Galaxy Nexus] natezire71:
I don't have that. :P
[Samsung Galaxy Nexus] Cnhamm532:
Well crap! I tried. Lol:screwy:
[Samsung Galaxy Nexus] natezire71:
Well, I did find something that was messing it up: "vanir.cfg" on the root of the SD card. It's never affected any other kernel until now. However, the only thing that isn't sticking on reboots is the "read ahead buffer speed". Can't find anything else that is changing my kernel settings.
[Samsung Galaxy Nexus] phishn:
I'm just reporting findings and unusual things that might lead to them Rom or kernel issues. I have never had wifi data issues before, on any Rom, nor have I had mms fail either before while using wifi. I do know something goes on with wifi / cell network when sending mms while wifi is on. Just an observation.
[Samsung Galaxy Nexus] Cnhamm532:
I'm on raped ape and it has three that affect it. I'll keep looking.
[Samsung Galaxy Nexus] the cronic dude:
I have not had the issue on my phone but my girlfriend has the exact same phone as me GNex toro, running the same rom and kernel and also has MMS issues every once in a while while her WiFi is on as well, if its toggeled on and off sometimes the message will go through other times a full reboot is required. Kernel fancy r31 and AOKP
[Samsung Galaxy Nexus] natezire71:
Don't worry about it. It's not your problem. :P I appreciate your help though! I'm gonna flash Osmosis' kernel reset then flash fancy again. I flashed this kernel with a clean ROM--this is the only kernel to have existed on this ROM. I have no clue why it's doing this.

---------- Post added at 02:58 PM ---------- Previous post was at 02:05 PM ----------

I seem to have found the issue. One of my init.d scripts has a line in it that changes the Read Ahead Buffer Size. However, I am unable to change it because of an error. I'm using Solid explorer. Every time I go to change that line and save it, it says it can't because it's a "Read only file zone". No clue what to do.
[Samsung Galaxy Nexus] motorazrv3:
You must change your operating permission. Mist file explorer mount with read only permission. Change to read and write permission and you can save your changes.

I am using root explorer. On top you can change the permission from read only to read and write.

Look if there is an option at solid explorer.
[Samsung Galaxy Nexus] natezire71:
I don't know why this is an issue with this kernel though. AK always overwrote the init.d scripts. The script that overwrites the read ahead buffer size is a script built into Vanir. Maybe it's an issue with Trickster?
[Samsung Galaxy Nexus] JonBsbB:
I did the update with FUSS in terminal and wouldnt let me get the extended
[Samsung Galaxy Nexus] KeithLing1115:
Is anyone with GPU OC to 512 able to Deep Sleep? I notice when I set my GPU to 512 and reboot just to clear all my Time In State stats and shut the screen off for say 2 hours, no deep sleep. Comes up under Not Used State. 384 GPU works just fine.
[Samsung Galaxy Nexus] clnzx2:
Working fine for me. What gpu governor are you using?
[Samsung Galaxy Nexus] nitsua98:
Do the gpu governors actually work? I tried ondemand and powersave with 307 and they feel and bench the same
[Samsung Galaxy Nexus] KeithLing1115:
I use ondemand. Okay ill play around.

Okay I disabled zram and it's now working. Did you have that enabled?
[Samsung Galaxy Nexus] chikimonke:
I could be wrong, but I believe for the governors to do anything you need to be at least set to 384. There's a link in the OP that describes the governor function more thoroughly.
[Samsung Galaxy Nexus] Milly7:
I am on raped ape as well, and every time I try to over clock I get some very nasty lag and lockups. What do you suggest I edit/delete in init.d?
[Samsung Galaxy Nexus] im the doctor:
Does "trimming for /system, /data and /cache" help with the gnex loss of performance over time (this bug) ?
[Samsung Galaxy Nexus] clnzx2:
This is true
[Samsung Galaxy Nexus] Cnhamm532:
What method are you using to make the changes? It could be that your phone just doesn't like the kernel. Mine does that on any of Franco's kernels.

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

Root Explorer has always been rock solid for me. It will actually change the permission for you now.
[Samsung Galaxy Nexus] quickstang:
Then just download the link from your browser. I'm not sure why you are having issues.

Click link, download, flash, profit. As simple as it gets.
[Samsung Galaxy Nexus] scadilla:
Battery Life on this kernel has been awesome

So I have been on this kernel for about a week and I have to say that my battery life has never been this good, I used to get about 2 hours of screen time I have been getting close to 3. I also consider myself a heavy user as I have about 3 Google accounts syncing and 1 Exchange account (Push) syncing, I receive on average about 300 e-mails a day mostly Exchange. I am running the ondemandplus governor and the SIOPLUS scheduler with MMuzzy FV 4/19, phone is very responsive and excellent battery life. I did clean install and I haven't loaded any SystemUI mods and have not setup Google now. At some point I am going to enable systemui mods (1% circle battery and blue zenyth keys) and setup Google now and see if my battery life it impacted. Thank you for all your hard work Boy and team!!
[Samsung Galaxy Nexus] Syfer_Fever:
delete folder "fuss" on sdcard if you have problem with OTA when typing "su" then "fuss" on terminal, it work for me
[Samsung Galaxy Nexus] im the doctor:
can 1% battery mod and custom softkey drain battery life ?
[Samsung Galaxy Nexus] pageniao:
Re: [KERNEL][4.2.x] Fancy Kernel (Rel. #5) (FEB-10-2013)

hi boype.great kernel.

i play nfs17 very fast :D

i can tune off 'group task' on trickser mod?
[Samsung Galaxy Nexus] boype:
Sure you can, but you will lose some battery savings.
[Samsung Galaxy Nexus] gwindlord:
So is it better to use or not to use group tasks in trickster? :) Or there is just no need, because kernel has its own?
[Samsung Galaxy Nexus] bolanrox:
I am going to leave it on for now i guess?
[Samsung Galaxy Nexus] bigknowz:
Confused as well

seems like there were 2 different answers

and to me:

Don't use the 'group tasks' option in trickster, because the author has implemented it incorrectly. group tasks is set by the kernel on boot on its own already. I think I will contact the trickster author...
[Samsung Galaxy Nexus] abezzilla99:
Has anyone experienced your phone freezing a few seconds after boot? I was using on demand plus running aokp jbmr1 b3. I did not try any other governors so it might have nothing to do with it but I just went back to lean kernel till I can figure out what's going on.
[Samsung Galaxy Nexus] boype:
Let me clarify: You can use trickster mod to turn the feature off. But when you use trickster mod to turn the feature back on, the value for sched_mc_power_savings will be 1 instead of 2, which is wrong. The correct value of 2 is set via the kernel's RAMDISK on every boot.

Freezing when exactly? On the google logo, on the boot animation, on 'enter PIN' dialog, or later? You are the first one to experience/report this.
[Samsung Galaxy Nexus] abezzilla99:
Sometimes at the boot animation and sometimes at the lock screen. On the lock screen I have just enough time to touch touch the unlock button before it freezes and if I have a lwp on sometimes it will stay moving while frozen.
[Samsung Galaxy Nexus] gwindlord:
Thank you for group tasks detailed clarification again :) Set sched_mc_power_savings to 2 manually.
[Samsung Galaxy Nexus] boype:
Short update:

I have contacted the Trickster mod team via email so they can fix the task grouping feature and also asked them to add the missing ondemandplus tunables to their app. Let's see what happens...

[EDIT] Trickster answered:

I'm sorry to tell you that I cannot do anything about that right now, since the problem only occurs on your end and I cannot reproduce it... :/
[Samsung Galaxy Nexus] ux50jp:
I tried to install Fancy#5 to JB4.2.2 but doesn't start up.

I tested with other kernels but the same.

Is there any way to fix this problem?
[Samsung Galaxy Nexus] renaud:
PVR changed (again) between 4.2.1 and 4.2.2, so there are changes needed in the kernels. Currently at least FuguMod and AK work
[Samsung Galaxy Nexus] abezzilla99:
Alright well I'll just try the next release w/ a fresh rom install. I also had a question for you. What kind of battery improvements have you had with both the ondemand+ and pegasusQ governors? I wanted to try them out and thats why I wanted to try your kernal.
[Samsung Galaxy Nexus] boype:
New release soon... With Android 4.2.2 support.

Currently compiling r6. Thanks to renaud I knew where to look in order to make the kernel boot on the new Android 4.2.2. The new release mainly includes updates.

Will upload later tonight or tomorrow morning (it's 07:40 P.M. here at the moment).
[Samsung Galaxy Nexus] gwindlord:
Is r6 with support of 4.2.2 of intended only for 4.2.2? My ROM is not updated yet, and there is no backward compatibility between 4.2.1 and 4.2.2...
[Samsung Galaxy Nexus] SPyxOff:
May I ask you what are your battery life guys? I mean with this kernel in use :laugh:
[Samsung Galaxy Nexus] boype:
I am still using 4.2.1 myself, so no worries. There will be two versions for each release.
[Samsung Galaxy Nexus] bigknowz:
Battery Life

Battery is very good on my phone with Max CPU and Max screen off (interactive gov) @ 1.4GHz. I would estimate it to be 5 - 10% more battery than other kernels I've used (lean, faux, tiny, ak, zen, franco).
[Samsung Galaxy Nexus] bolanrox:
cool thanks! I was worried about that :)
[Samsung Galaxy Nexus] namtombout:
Re: [KERNEL][4.2.1] Fancy Kernel (Rel. #5) (FEB-10-2013)

Shameless bump because I feel more people need to check this kernel out. Thanks boype I finally get great battery life and ost on sourcery.

Also would you enlighten us on the rom you're running and your typical battery life and ost?
[Samsung Galaxy Nexus] natezire71:
Not really, no. I wouldn't worry about that. That's such a small percentage of your battery life it's practically negligible.
[Samsung Galaxy Nexus] Milly7:
I used the built in performance settings, as well as, trying trickster mod. It runs fine as long as i do not try to over clock. I didn't have this problem on Axi0m ROM. Oh well. Love the kernel so may just switch ROMs.
[Samsung Galaxy Nexus] Cnhamm532:
That would be a good idea to figure out what's causing it. Don't forget to delete vanir.cfg
[Samsung Galaxy Nexus] Hoochie_Coochie:
Using latest PacMan and this kernel. I also use lux and occasionally the halo notification will go nuts as lux gets killed and then restarts itself continuously. Anyone else get this? Any solutions?

Thanks
[Samsung Galaxy Nexus] splus:
I tested 512 MHz GPU earlier, and it looks like ondemand GPU governor doesn't work. Graphics benchmarks were in line with 307 or 384 MHz GPU speeds.

Performance GPU governor, on the other hand worked OK, full 512 Mhz speed performance.

[MENTION=4615478]boype[/MENTION] - maybe there's some bug with ondemand GPU governor, at least when GPU speed is set to 512 MHz?

It looks to me that everyone is focusing on CPU performance and CPU governors, but I think for a smooth UI the GPU performance is much more important than CPU performance. Especially in Gnex, whose GPU isn't very good. I'd really love to see GPU governors perform great while being battery efficient.
[Samsung Galaxy Nexus] bolanrox:
i've had those softkeys on every rom i flashed since i rooted and never noticed any kind of drain
[Samsung Galaxy Nexus] creeve4:
I agree.

Using NenaMark2 and testing each group 15 times:

I get an average of 25.6 FPS with 384 MHz and Ondemand.

I get an average of 27.8 FPS with 384 MHz and Performance.

I get an average of 25.4 FPS with 512 MHz and Ondemand.

I get an average of 31.9 FPS with 512 MHz and Performance.
[Samsung Galaxy Nexus] sherincal:
Conclusion: Works
[Samsung Galaxy Nexus] splus:
And I just did Nenamark2 test with old AK Cylon 734 kernel (no GPU governors):

With 512 MHz GPU I get 37.4 FPS.

With 384 MHz GPU I get 32.1 FPS.

With 307 MHz GPU I get 28.1 FPS.

All those speeds are pretty much in line with speeds of other kernels I tested in past.

It looks like that ondemand on Fancy is stuck on 307 MHz GPU no matter what frequency is chosen, whereas performance puts it up to 384 MHz speed ONLY if 512 MHz is selected.

If this is fixed this kernel will suddenly get MUCH smoother! :)

Nope, it doesn't.
[Samsung Galaxy Nexus] creeve4:
Do you not see that FPS is the same for 384 MHz and 512 MHz when using Ondemand?
[Samsung Galaxy Nexus] cuboc:
how do I machetes for this file to run every boot?
[Samsung Galaxy Nexus] aHecticLife:
Just checked and you're right!
[Samsung Galaxy Nexus] splus:
Except that it never even reaches 512 MHz speed.

It reaches maximum 384 MHz with performance gov when set to 512 MHz, and stays on 307 MHz with ondemand no matter what speed is selected.

Since kernel comes with ondemand GPU governor as default, most users have been running GPU on slow 307 MHz...

Fixing this should increase smoothness because it's the GPU that is often the bottleneck in smooth UI, not the CPU.

It's not for no reason that Apple always puts beefed up GPUs in their devices... ;)
[Samsung Galaxy Nexus] mixtapes08:
What if we just remove the gpu governor selection?
[Samsung Galaxy Nexus] splus:
Well, that's up to [MENTION=4615478]boype[/MENTION], if he doesn't mind fiddling with it little more and offering few choices for GPU governors... Same philosophy as CPU governors, just fewer frequencies and I guess they have a different logic.

If one governor works good then probably no need to have more.

Franco kernel has only one default GPU governor, and the max GPU is hard coded to 512 MHz (hence its good performance).

AK kernel is same but with max GPU speed of 384 MHz because he had some users complaining they have artifacts when they choose 512 MHz GPU (so he took out the choice of 512 GPU instead of having to listen to complaints of users who don't know what they're doing).

The thing is that some phones can run 512 MHz without problems and some can't, they have occassional artifacts.

Franco for a long time had 2 versions of his kernel, one with GPU 512 MHz and one with GPU 384 MHz for those whose phone couldn't run GPU 512 MHz.

And then he finally figured out how to make all phones work with 512 MHz - the trick was to disable Core SR and slightly increase core (GPU) voltages. With that ALL phones were able to run GPU on 512 MHz.

So that's a brief history of Gnex GPU... :)

I guess when Boype fixes the GPU governor he'll either have to put a clear notice that some phones can't run 512 MHz and will have artifacts if they do, but it can be fixed easily if max GPU frequency is set to 384 MHz (.

Or to turn off Core SR and increase Core voltages so all phones can run 512 MHz GPU...

I'd also suggest to set default max GPU speed to 384 MHz for better performance. Battery difference, as tested in Franco threat over the past year, is negligible.
[Samsung Galaxy Nexus] sajty:
I really hope,that this solution will NOT be selected.I really dont like,when is something hardcoded and i cannot change it (at least for basic things).
[Samsung Galaxy Nexus] splus:
Neither do I. :)

I'd just rather put a red letter note before download link that says if one selects 512 MHz as max GPU frequency in Trickster and has artifacts to just revert back to 384 MHz because their GPU can't run at 512 MHz. Everyone's silicon is different.

And if someone STILL complains about artifacts then tell them to read OP or google "How to learn reading".

On the other hand, I think only 512 MHz slot needs to have higher voltage for weaker silicons, so maybe the solution could be that lower GPU frequencies use SR and 512 MHz slot can be hard coded, SR disabled.

I think higher CPU frequencies above 1400 MHz work that way, they disable SR.

This approach would be easy, hassle free for everyone, and you still have control of all voltages except the 512 MHz one.

It's up to boype to decide.

Who knows, maybe he can think of something new... :)
[Samsung Galaxy Nexus] im the doctor:
Will using GPU at 512MHz damage hw ?
[Samsung Galaxy Nexus] Seraz007:
no m8

but i think it hardly ever reaches that value :confused::)
[Samsung Galaxy Nexus] boype:
GPU governor

Hi all,

I did some debugging with the GPU governor to find what's wrong with it.

The facts first: Even though there was an error in the code by the original author, after fixing this one it still does not work. Only 307 MHz will be used, no matter what you set the ondemand governor's max frequency to. In principle it should work, but it doesn't. Probably the GPU simply does not support switching from 307 to 384/512 MHz. But that's just a theory.

I'll remove the GPU governor, as it is non-functional.

On another note: I am compiling with linaro 4.7 now, NenaMark2 scores are way better. And I think other usage scenarios should profit from this as well.
[Samsung Galaxy Nexus] mangusZen:
This is quite interesting about the topic above..

http://techie-buzz.com/android/why-...exus-clocked-at-308mhz-instead-of-380mhz.html

sent from Vega gnex
[Samsung Galaxy Nexus] splus:
Hm, that's strange. Any chance to check the code in some other kernels that have different approach?

Or to check the performance governor, because when max GPU is set to 512 MHz performance governor will actually boost the GPU up to 384 MHz.

Now that I remember, I think Franco also had difficulties to implement a variable max GPU frequency (selectable in kernel app), so he just went with hard coded MAX GPU frequency without any GPU governors, and it works perfectly, scales from 157 to 512 Mhz...

If automatic GPU frequency scaling is working OK then probably no need for GPU governors... Just as long as we can have high max GPU frequency when its needed, lol.
[Samsung Galaxy Nexus] zoomy942:
We not hard code 384 and make 512 optional?
[Samsung Galaxy Nexus] paarthdesai:
is otg available in this?

sent from my sexy Nexy ;)
[Samsung Galaxy Nexus] boype:
You'll still be able to select the Max frequency, don't worry. There'll be two steps then, like on other kernels. You can choose from 153 - 307, 153-384, 153-512.

Also, I have implemented the temperature control stuff.
[Samsung Galaxy Nexus] creeve4:
Looking forward to r32!