yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] zoomy942:
I will flash that r25 test and put that into terminal and report back.

---------- Post added at 02:01 PM ---------- Previous post was at 01:40 PM ----------

Done !
[Samsung Galaxy Nexus] sym_m:
my nova launcher is laging on scroll on r25 ?? how can fix?
[Samsung Galaxy Nexus] zoomy942:
Whatever you were into with r24. It's way smoother than 25 in my limited testing

EDIT - just to be more clear.

r24 has been great. I flashed r25 which includes SIOPLUS and seemed okay. Didnt test it long as I started using the r25test. That was much less smooth.

Right now I'm on r25 NONTEST standard with the renice to 20. And using SIOPLUS
[Samsung Galaxy Nexus] CCaaNN:
Hello Boype, can you add whatsapp to this lowmemory killer whitelist? Or is it necessary? I got lots of disconnects while using wifi in whatsapp. But i dont know if it is connected with it.

Galaxy Nexus cihazımdan Tapatalk 2 ile gönderildi
[Samsung Galaxy Nexus] scadilla:
Is all the discussion around systemui priority etc. For people that are having systemui issues at boot up? I had no luck with r23 and r24, both kept giving me systemui stopped responding errors, had to revert to nandroid. Not sure if makes a difference but I was flashing over top of Franco's kernel. Any advice would be appreciated.
[Samsung Galaxy Nexus] Argasil:
All fine here with r25 test, don't know for smoothness( seems to ne the same but maybe faster). No sod, freeze with ondemandplus and sioplus!:) will see for battery life anyway another good job boype, congratulations :good:
[Samsung Galaxy Nexus] dmillerzx:
Correct me if I'm wrong... Is there any possible reason why a Fancy Kernel update might cause data drops on my cell radios. When wifi is on or off, I've noticed my cell signal completely dropping out or greying out. From my understand though the kernel shouldn't have any effect on radios... However, I can't say I've seen this problem since updating to R25. Any suggestions, GNEX Toro here.
[Samsung Galaxy Nexus] Argasil:
I think that is not the kernel..the baseband si another thing,but it si strange.. I always flash theese kernel with a new updeted ROM,so i always do a cLean installation: wipe data wipe cache wipe dalvick cache format system, try only to wipe cache if it's not working try a cLean installation..and if it isn't working yet try to flash a baseband,i rally don't think the problemi si the kernel..
[Samsung Galaxy Nexus] Pelide:
I'm pretty sure that the kernel controls the wifi, while the baseband controls the mobile data

Have you tried to contact your mobile provider and ask if they are aware of some problems on the line in your city/zone?
[Samsung Galaxy Nexus] Charmacas:
Thank you [MENTION=4615478]boype[/MENTION] for the discussion and helpful links. I also see some in the OT. Thanks!

I really have to say that r24 for me personally is much much better in terms of performance than r25. Do you have any idea why that happens?

I also have the problem as another user already reported. While typing with r25 it comes to lags often with SwiftKey.

Could I help you tracking this performance problem?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] Pelide:
Here all ok with SwiftKey, typing or sliding (all stock except than min 192 screen on, uv mpu - 50, with slimbean 5 andare fancy r25test)

If you or boype need other infos I'm here

Tapatalkeggiato
[Samsung Galaxy Nexus] dmillerzx:
I don't think it is either just want to eliminate it as a possibility at all. No issues with Verizon 4G/3G as far as I know, and I've tried reflashing the radios. Guess I'll keep and eye on it and see.
[Samsung Galaxy Nexus] Invicta:
Cm10.1 and r24
[Samsung Galaxy Nexus] parkson:
This happened to me yesterday. Posted about it a couple pages back - got no response. Sucks you have the same problem but its assuring knowing im not alone here.

I've been a user long enough to know there aren't any other variables that cause this for me, other than flashing r25. Doesn't happen on r24 or previous versions, nor other developers' kernels
[Samsung Galaxy Nexus] gwindlord:
Have no issues on slim bean and r25. Synthetic tests show little decrease, but I guess it could be not too relevant. Though 3D shows even increase. Thanks, boype :)
[Samsung Galaxy Nexus] bolanrox:
it felt like i had slower than usual switches with data, but i wasn't on it long enough at home to really see. (work is always bad signal wise post sandy..) no other changes to anything, and reverting back to 24 fixed everything. are you guys on VZW too?
[Samsung Galaxy Nexus] zoomy942:
The main difference I see is 24 has SIO and 25 has SIOPLUS
[Samsung Galaxy Nexus] parkson:
Yes we are Toro users. After data drops kept occurring I reflashed cm for the kernel and got no data drops. Flash ak kernel... No drops. Another dirty ROM flash + r24... no drops... Flash r25(test vers.) and data drops return.
[Samsung Galaxy Nexus] bolanrox:
Guess it is only fair - had none of the issues people were having with was it version 23? So strange that a kernel would be messing with non wifi radios though.
[Samsung Galaxy Nexus] dmourao:
Heard quite a lot about your kernel lately. Gonna try it out now! Thanks!
[Samsung Galaxy Nexus] osm0sis:
Correct. Thanks. ;)

[MENTION=4615478]boype[/MENTION] Lots of great ideas and tweaks coming out of this thread lately. Great job and keep up the good work! Couple other corrections to your changelog though, for proper credit purposes:

- moved "powerHAL fix" from zip package to ramdisk (thanks to osm0sis)

- queue "block tweaks" (thanks to Franco's Dev Team)

- added lowmemorykiller launcher whitelist (makes the launcher 'unkillable'; thanks to osm0sis)

- ramdisk "init.d support" dir creation (thanks to osm0sis)

I realize the powerhal fix and init.d creation are pretty trivial, but looking at the script it's pretty much cut+paste from franco.Kernel's ramdisk which I wrote it for to provide stock ROM with a backup for OTA assert purposes, so it'd just be courteous to credit it as such. :)

I also come bearing gifts though. :p Got a couple fixes for your current setup if you're interested:

- nomerges at anything other than 0 feels faster, but cripples write speeds, so we had to put it back to 0 after trialing it at 2 and then 1 for awhile. This is also a big contributor to "Play Store lag" for downloads/installs.

- made a slightly more concise version of your systemui renice script:

# wait for systemui and increase its priority
while sleep 1; do
if [ `$bb pidof com.android.systemui` ]; then
renice -18 `$bb pidof com.android.systemui`;
exit;
fi;
done&

No need to use busybox if we don't have to. Putting that near the end of the init.d scripts, before the lmkwhitelist is a good spot since it won't hold anything else up and cuts down the time required for the lmk sleep to 10. I'm also toying with making systemui "unkillable", and increasing the niceness of the launcher by adding that to the lmk whitelist script. I'd appreciate your thoughts on those. And I recently fixed the lmk script up a bit: only real change is " if [ $pid ]; then" so that the output is clean (I see you've already done something similar with pgrep, but again, why use busybox if you don't have to? ;)). Oh and if the RD application doesn't work out again I can probably swing RC for you, just let me know. Cheers! :D

Edit: Huh just realized pidof is also busybox. Ah well, guess we can't go full native.

Edit 2: Updated with a while sleep loop so that it doesn't hold up the rest of the init.d script.
[Samsung Galaxy Nexus] johno86:
I also had radio problems. It would barely have any data. Running speedtest.net would give me around 50 - 700 kbps. Very random. Performance wise it was great. Called my provider to ensure there was no tower outage which there was not. Not entirely sure if it was this specific kernel but I have since changed to ak and my 4G data is back.

Sent from my Nexus 10
[Samsung Galaxy Nexus] dmillerzx:
It is very strange indeed. However all indicators are pointing to the Kernel currently as I've never had this issue prior to using R25.... I am a toro / VZW user and have always favored this kernel.

From my understanding the kernel should only effect wifi. However, it appears that when wifi is transitioning to a cellular connection the problem then appears. So perhaps the way wifi is now disconnecting is the culprit? Not sure, but something strange is going on. I'd be willing to bet there aren't more reports of this as most people using this kernel probably aren't using a toro / VZW... Hopefully boype can provide some insight.

Also [MENTION=4615478]boype[/MENTION] are you still continuing your work on the wifi fix to resolve the dreaded data stalls during sleep? I saw in your change logs that you had attempted some sort of fix. I ask because depending on your usage behavior everyone running 4.2 will eventually run into the wifi bug... I hate having data stalls or grey bars await me after I wake my phone from sleep. A unbelievable oversight by Google which was NOT present in 4.1....

Some insight from past research into this:

The problem with WiFi in 4.2 appears to be related to the botched "Keep Wi-Fi on during sleep" settings under advanced in WiFi.

If anyone is interested here is a work around that proves that this is where the problem exist.

For what's it's worth Buckmarble of Project Elite [MENTION=5250612]droidf[/MENTION]orums found somewhat of a work-a-round.

"I have read through that link before (https://code.google.com/p/android/issues/detail?id=40065). I was trying something at the kernel level to see if I could find a solution but it was a dead end. I have discovered a 'work around' that does fix it but has to be done every time WiFi is toggled. It seems related to the sleep policy not being saved or reinstated every time WiFi is toggled on and off. What you need to do is change the sleep policy to something different, reboot, change it back, and reboot again and WiFi will stay on during deep sleep."

I can confirm wifi will function correctly until it's toggled on/off (or your device reboots).

Sleep Policy = Keep Wi-Fi on during sleep. (Settings -> Wi-Fi -> Advanced)

People like me who are trying to manage wifi to save battery life (https://play.google.com/store/apps/details?id=com.sebouh00.smartwifitoggler&hl=en) resulting in multiple toggles in-between reboots will always notice this problem more than someone who simply leaves wifi toggled on 24/7

Thoughts? :D and thanks for making one of the best Kernel's out there for the GNex!! Keep up the amazing work.
[Samsung Galaxy Nexus] Charmacas:
Nice osmosis!

Also I downloaded the Carbon Nightly from the 16th, installed Fancy Test r25 and changed nomerges to 0. Now I have a good performance. Time will tell about the long term performance. :)

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] dmillerzx:
[MENTION=4615478]boype[/MENTION] I hope you'll consider everything osm0sis has stated. Him and the Franco guys along with the AK team continue to push the GNex to new horizons. Hopefully you can incorporate all of their latest advancements into Fancy; of course giving credit where due.

Everyone making advancements on the kernel front is simply amazing. Now if the wifi issues I posted above can be fixed. Everything for the perfect user experience will be in place ;)
[Samsung Galaxy Nexus] Fabur87:
After a few days of usage I also have the feeling that r25 is not the smoothest version of Fancy I have had.

And I also experienced a new problem that I never had with this kernel before:

when I was using xiia live to listen to internet radio and my screen turned off the music playback suddenly started to lag as hell until I turned the screen on.

This happened only twice and not every time the screen went off.

There was no update for the app or ROM, so the only thing that changed was the kernel (at least it is the only thing that comes to my mind that could affect playback).

Any idea why that might have happened?
[Samsung Galaxy Nexus] stevensoaj:
This happened to me as well while listening to music on the new Play Music app with my bluetooth headset. Never had a problem with this before. Min Freq was at 384, so should be plenty.
[Samsung Galaxy Nexus] BOY_:
Just wanted to report that I too am having cell signal drops. My battery has been hammered today with time without signal. I've asked around and no other Verizon subscribers in my office are experiencing signal drops. Only change has been r25. Rolling back to r24.
[Samsung Galaxy Nexus] parkson:
Would love to help get to the bottom of this issue regarding cell signal drops for VZW users. Not able to post one now, but I'm reading up on how to use logcat - would that help this matter? If neccessary, I'll clean flash cm and r25 later, then post a log later tonight (EST).
[Samsung Galaxy Nexus] Lancez:
clean installed latest AOKP nightly with r25 and been running it without any problems ever since. Maguro on T-Mobile USA
[Samsung Galaxy Nexus] dmillerzx:
Toro users stay at r24!!

Just wanted to report the kernel is in fact the reason for the cellular radio issues related to r25. I flashed the latest AK kernel, resulting in the radio problems being resolved. Looks like r25 is a no go for Toro users.
[Samsung Galaxy Nexus] Fabur87:
Looks like it doesn't affect German users? I didn't notice anything out of the ordinary.
[Samsung Galaxy Nexus] parkson:
*edited for sake of neatnes*

3-16 CM 10.1

r25 exp test

signal drops for Toro

warnings...errors...logcats!

http://db.tt/14nLLVpj

http://db.tt/5gjwm4up

http://db.tt/mLMsyMhK
[Samsung Galaxy Nexus] boype:
Hi all,

... wow. Pretty much going on in this thread! It is getting hard to follow everything ;)

Of course, I see that r25 is not the greatest release, and I share this opinion. Therefore, r26 will continue where r24 ended, dropping the 'bad' changes of r25.

A word to dynamic fsync, as several people have been asking for it: There is fsync toggle already included in the ext version. My point is that dynamic fsync has no real advantages over the fsync toggle. In comparison to the 'normal' fsync toggle, all it does is switch fsync on again when the screen goes off. So if the kernel/ROM is not exactly known for SODs, I don't see any gain in it, really... Having said this, I'd like to add that im my personal opinion dynamic fsync is one of those 'innovations' that nobody really needs.

Best regards

[EDIT] Meanwhile, there's a freshly compiled test version available: http://boypetersen.de/fancykernel/tst/fancy_kernel-tuna-4.2-tst-ext.zip
[Samsung Galaxy Nexus] Rufufu:
Thanks!

And what do you think about Osmosis ideas?
[Samsung Galaxy Nexus] Charmacas:
Thanks for the update [MENTION=4615478]boype[/MENTION] !

I absolutely agree with your opinion about the Dynamic FSYNC. It's not bad to integrate but it's not needed.

Also I saw you did not set nomerges to 0 as Osmosis suggested. Why?

I tuned the test version. I use 1420 MHz and set the nomerges value. And I also set the MCPS to 1. So far it's running really nice! Should we test something specific?

Sent from my Galaxy Nexus with Tapatalk 2
[Samsung Galaxy Nexus] boype:
r26

Hi all,

r26 is uploaded. Change log is as follows:

removed async read starvation feature from sioplus (debugging showed it is not necessary)

reverted several changes that caused worse performance than r24 (e.g., systemui priority is back to -20, sched_mc_power_saving is back to 2, readahead is back to 256)

increased CPU transition latency to 30000 (was 20000, this aims to fix CPU stangenesses as SODs and jerky 1.4 GHz)

nomerges back to 0 (thanks 0smosis)

This should make things better again that were introduced for the worse in r25. Also the 0smosis thing included (thanks mate). Also, I have corrected the credits for several things in the change log - I'm ashamed I didn't give proper credit to the authors :(

Best regards
[Samsung Galaxy Nexus] stevensoaj:
While I agree r25 was not the greatest, I'm glad it was released. Its hard to release a better kernel without doing some experimenting! I love your work so far and I hope you keep it up. Time to flash r26. :p
[Samsung Galaxy Nexus] jjhrrsn:
Awesome thanks. As far as credit goes it was an honest mistake, you were trying to give credit, not like you said it was you. Keep up the great work!
[Samsung Galaxy Nexus] 1haumann1:
Want to share my kernel settings with r26

Now testing.... :D

swyped from my maguro
[Samsung Galaxy Nexus] Invicta:
Flashed, so far all good
[Samsung Galaxy Nexus] scadilla:
Tried installing r25 over top of the stock kernel JDQ39 kernel and had the same results. Kept getting System UI stopped responding errors. The only way to correct was to restore via nandroid. Nobody has had any install issues like this? I'd love to try this kernel but seems that since r23 I have had no luck installing. Any help / advice is always appreciated.
[Samsung Galaxy Nexus] motorazrv3:
no problems here with r25 ext on purity 5.4.2.

I just flashed r26 exp changed gpu clock back to 307 mhz and max. CPU to 1ghz.

So far no issues, phone performing fast and smooth. For my feelings better than r25.
[Samsung Galaxy Nexus] bolanrox:
Been running r26 since you posted it. No issues yet. data is normal, will see if I get any drop offs (I am at work, so wifi has been off since i flashed it)
[Samsung Galaxy Nexus] openlatedotorg:
Just flashed over slim5 and can already tell a slight difference in performance over r25. Stock settings
[Samsung Galaxy Nexus] dmillerzx:
That's because this is only reported to be affecting Toro users (VZW users in the states). I haven't tested r26 yet, can anyone confirm that the data issues were resolved for Toro users? No mentioned of this issues in the change log.
[Samsung Galaxy Nexus] parkson:
Just loaded it up and data signal dropped within first 5 minutes. Bars remained blue but data arrows didnt show activity; connection frozen. Then bars disappear (-1 dbm reading), all without messing with wifi :(

Going to do another clean flash and try again :banghead:
[Samsung Galaxy Nexus] thebogy:
just flashed r26 over r25 on purity 5.4.2

it seems better than r25, with default settings. :) thx boype
[Samsung Galaxy Nexus] bolanrox:
So far my bars are low, but that is normal for work - still getting email and other notifications though - deep sleep is fine. Will really need to look later when i get home and actually have a normal signal strength
[Samsung Galaxy Nexus] shawnaye:
I just wanted to say thanks for all your hard work Boype.

It's development like this that's keep me from purchasing a N4 that i'll regret because i'm holding out for a N5.
[Samsung Galaxy Nexus] dmillerzx:
[MENTION=4615478]boype[/MENTION] can you provide any insight for Toro users who are noticing signal issues from their cellular radios since r25? Looks like r26 still is causing the same symptoms... Seems to be effecting everyone on Toro/VZW service.
[Samsung Galaxy Nexus] Kewyang:
Hi may i know does this kernel run perfectly with PA?
[Samsung Galaxy Nexus] mitchmao:
I noted that r26 is missing "Sound Control" capabilities (high performance sound, volume boost). is this just me?

I checked with Trickster MOD. I'm using Paranoid Android 3.5 may14 on a gnex.

thanks
[Samsung Galaxy Nexus] TheMysteriousOne:
You must have downloaded the standard version instead of the extended one.
[Samsung Galaxy Nexus] mangusZen:
just saying, I just transferred some big files in my phone on my wireless lan and reached 2,45 Mb/s with r26.

Best speed ever! great work :good:
[Samsung Galaxy Nexus] mitchmao:
...

sorry, I'm dumb, really. -.-

getting the EXT now.

apart from that, r26 seems stable and better than r25 up to now.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION] Thank you sir! :)

What about these (edited)?

I'm also toying with making systemui "unkillable", and increasing the niceness of the launcher by adding that to the lmk whitelist script.

But I'm also worried that the -20 on systemui could exacerbate the memory leak custom ROM users are seeing since JB4.2.2.

I'd appreciate your thoughts. :)

---------- Post added at 01:13 PM ---------- Previous post was at 12:56 PM ----------

P.S. Created a getprio script last night for use in /system/xbin as a runnable script to check the niceness of a process. Makes up for Android not having "getpriority", and not displaying the niceness in "top" or "ps" like it would on mainstream Linux. More info on usage in my most recent post in my Odds and Ends thread. ;)

http://xdaforums.com/showthread.php?p=40409361#post40409361
[Samsung Galaxy Nexus] omid900:
Yes, I have test it with last official release and unofficial linaro build, it work just great :)

Also I have none of the problems with data/wifi , maguro here! So it must be a issue that only affect Toro users!

R26 feels really good, and a I am testing some serious undervolt values, so far so good :)

Thank you boype
[Samsung Galaxy Nexus] boype:
In fact, I do not have the slightest idea what's wrong. If I'm looking at the changes from r24 >> r25, the only thing that comes to my mind is the linux 3.0.78 update. But then again, AK kernel also has the update and is working fine. There's only one remaining option, but I cannot imagine that the thing I have in mind is responsible. Anyway, I'll put up a test version soon.

[edit] Turns out I was too lazy to read the logcats that were provided. The issue has to do with the priorization of the systemui process:

05-17 01:05:50.718 W/PackageManager(940): Unknown permission android.permission.ACCESS_4G_STATE in package com.android.systemui

I'm looking into this.

Will add the script change to the next release, I just didn't feel the urge to add it right away because it basically does the same job.

By the way, 'ps -p' shows the niceness, also in Android :) But of course it shows all processes instead of one.
[Samsung Galaxy Nexus] Fabur87:
Doh. I always forget that there are multiple version of this phone.

[MENTION=4337538]Kewyang[/MENTION]: I am still running PA from 05. May and it is running great so far. I had some problems with the PA version before that though.

Don't know about the more recent ones, but I guess they should run fine too.

Also nice seeing you devs working together.
[Samsung Galaxy Nexus] osm0sis:
[MENTION=4615478]boype[/MENTION] Ah great thanks! Hadn't tried -p since everywhere I looked said it should display already. :good:

And what do you think about also making launcher nicer, or the possibility that increasing systemui's prio could exacerbate the memory leak?

My feeling about making systemui unkillable is that lmk should never kill it anyway so it might be redundant. I'm trying it right now anyway to see what happens though.
[Samsung Galaxy Nexus] dmillerzx:
Thanks Boype! Hopefully us Toro users can come back to Fancy soon. Keep up the great work bro.
[Samsung Galaxy Nexus] momomok:
I have read all these process priority stuffs on the last few pages

but I can't stop thinking one question: aren't all android apps running under dalvik vm? how can kernel control the priority? aren't they running in a single process?

(sorry if it is a nooby question... just want to get my concepts corrected :D)
[Samsung Galaxy Nexus] angourakis:
As a sugestion for the next release, and quoting an answer boype gave me:

Why not set the default GPU speed to 307Mhz and make it ajustable accordingly to the demand? It would be a nice feature to save energy plus giving us the best possible performance.

AK have implement this in one of the kernels (and if we choose "conservative", the GPU will be stucked at 307Mhz, the same for "performance" and 512Mhz, "ondemand" has the behavior above) and Franco uses this way.

Best Regards,

Rafael
[Samsung Galaxy Nexus] TheMysteriousOne:
There already are 3 GPU governors and up to 512 GPU OC.
[Samsung Galaxy Nexus] droid_legacy:
frandom

Hey guys.

Is it possible to run the frandom init.d script of AK.Kernel with this Kernel or needs there something to be changed in the kernel?

thx in advance
[Samsung Galaxy Nexus] Blackcrx:
Question for ppl that had data drops with r25. What color was your signal/reception bar in the battery status? red? black?
[Samsung Galaxy Nexus] dmourao:
I had massive wifi drops in r25, but my reception signal was mostly ok (TIM Brazil), 3G worked when I needed. :)