yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] trailblazerz11:
Stock is fine, rechecked r21 too.

Though I can't seem to get it to crash on my tcp reverted img. How many/Which commits did you revert?

My git log with 10 total reverted.

[juston@asus-m51ac Shamu]$ git log --pretty=short
commit c66548eab39e4b79c8bbe41a38822078787906db
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv4: ip_check_defrag should correctly check return value of skb_copy_bits"

commit 792934b2405a4455c96a9d1722a4fb0faaeea13c
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv4: ip_check_defrag should not assume that skb_network_offset is zero"

commit 9a7038441a376f36d766a3be5da12f222e35d68d
Author: Juston Li <juston.h.li@gmail.com>

Revert "tcp: fix tcp fin memory accounting"

commit 448e855337dc18478470280383bf409e68cf24b4
Author: Juston Li <juston.h.li@gmail.com>

Revert "tcp: make connect() mem charging friendly"

commit 42d9616e82c10bd82727ede0726d70e2b608bb22
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv6: stop sending PTB packets for MTU < 1280"

commit c8fcfe24484359e7c83753aee014086eb6d22326
Author: Juston Li <juston.h.li@gmail.com>

Revert "ping: Fix race in free in receive path"

commit 0981e982d40e0c3a21f6588e6b7ec14c27e02ec1
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv6: replacing a rt6_info needs to purge possible propagated rt6_infos too"

commit 95ff9bda6453944f79cc3031a286083f009b4865
Author: Juston Li <juston.h.li@gmail.com>

Revert "tcp: ipv4: initialize unicast_sock sk_pacing_rate"

commit c2bfe0ade89066bdb1eac716213da17dda5c79d6
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv4: dst_entry leak in ip_send_unicast_reply()"

commit 04be0deb6211b601f31a17858d6e3759b1d6c43d
Author: Juston Li <juston.h.li@gmail.com>

Revert "ipv4: tcp: get rid of ugly unicast_sock"
[Nexus 6  Original Android Development] lngwca:
You mind sharing settings. Im barely hiting 32k
[Nexus 6  Original Android Development] dadsterflip:
Any reason this kernel runs hot while others are not? Well while charging i should . Default setups. Tested a few kernels. Running chroma. Do I need to change any settings on the app? Would love to keep running this kernel
[Nexus 6  Original Android Development] shwise:
Thanks, I did have some weird settings, and now I'm back where I was with stock. What are your settings?
[Nexus 6  Original Android Development] JRJ442:
[MENTION=3134933]lngwca[/MENTION] & [MENTION=5615053]shwise[/MENTION] My settings aren't really anything crazy.

Max 2649

Min 1036

Interactive

Noop
[Nexus 6  Original Android Development] lngwca:
Have you ever used vomer tweaks?
[Nexus 6  Original Android Development] JRJ442:
No, not sure what that is.
[Nexus 6  Original Android Development] lngwca:
What is noop?

Here's mine
[Nexus 6  Original Android Development] kifac:
Is it just me or are non of the settings since the update sticking?

After updating the app and flashing R22, my profile magically switched to power saving. Went back to balanced, closed app...went back in and it was back to power saving. Switched back to balance and it has been fine since. Another thing i have noticed is MAX CPU FREQ is also not sticking. Everytime i go back into that same section of the app..theres always a different value. It either goes up or it goes down.

Ill be doing a few things to figure out what could be causing it.

Flashed R21...went back to balanced and set freq to 2649. Seems to be holding!

Will flash R22 now.

EDIT: Flashed R22. The CPU settings stuck on boot.

Went to profile and again..magically it was on power saving :/

Switched back to balance and CPU freq stayed the same as i set.

EDIT 2:

So i ran a benchmark before flashing R22. I got 48K

flashed R22 got 34K

realized what the problem was, thought i fixed it and i still only got 37K

No idea what it is but i cant replicate the performance on R22 tht R21 had.
[Nexus 6  Original Android Development] lainemac:
Benchmarks aren't indicative of actual performance. Is your phone actually not running as well as with R21? Or are you strictly referring to the benchmarks?
[Nexus 6  Original Android Development] kifac:
I was able to quickly switch between multiple apps at a time with no lag on R21.

With R22 i do get lag when switching between whatsapp and messaging app.

I have ran 3 benchmarks and neither of them come close to what R21 was.

rebooted my device, and for some reason it keeps reverting to "Power saving" under profiles.
[Nexus 6  Original Android Development] dtroup64:
Dial Pad

Can't find anyone else having this issue on r22. I reflashed everything after you re-uploaded the kernel, and for some reason my dial pad, when IN a call, isn't working. I hadn't pre-set my Voicemail password and was trying to enter it, and it wouldn't work. It makes sounds as if it's working, and the voicemail registers that something is being entered, but it's entered wrong every time.

I then tried some other things, such as calling technical support to change my password (I thought I had perhaps changed it without remembering) and I couldn't enter the numbers to get to technical support.

I reflashed 21 and all was good with the world again.
[Nexus 6  Original Android Development] Popo001:
I've been using your kernel since the N4 and I'm so disappointed your cat is not improving in the r22 release.

I'm gonna use another kernel now.
[Nexus 6  Original Android Development] crawlingcity:
hey [MENTION=3292224]franciscofranco[/MENTION]

Have you noticed that when you call "adb reboot" , or use your reboot application, the custom screen values won't stick ?

I know you fixed saving values after a reboot, but that's a normal reboot -> power button -> reboot -> they stick

using your reboot application (or any other calling reboot directly?) -> they won't stick.

Do you need logs of this? if so, which ones ?

Let me know if you need more info on this, but I thing you can reproduce it.

PS: just updated to r22 using your paid app, on reboot I lost my custom screen values.
[Nexus 6  Original Android Development] nexusmaniac:
Hi,

I noticed that it defaults to "Power Saving" mode by default. However, if you open the System Monitor you'll notice that all 4 cores are still active (Only 2 are supposed to be active with Power Saving mode) Your CPU clock speed will still hit your current Max. Freq.

So although it seems to be selected I can confirm it's not actually in the Power Saving mode :)
[Nexus 6  Original Android Development] eluspo:
Seeing the same in the performance profile, it is in power saving but all cores onlines. Also experience first boot after flashing r22 the all apps tried to optimize. Anyone felt or experience any adverse effect in disabling the wlan wakelocks?
[Nexus 6  Original Android Development] iainaaldrich:
I'm not a conplainer, this kernel and app are fantastic and supported an incredible amount. I am, however getting random freezes/reboots on r22. I have not changed any kernel settings or changed my ROM since updating from r21. Sometimes I won't even be using my phone then I'll pick it up and notice it's frozen at the google logo. I am using stock rooted 5.1 on sprint (D build) with 95r radio.
[Nexus 6  Original Android Development] stevessvt:
Jesus,...so go back to r21, quite your whining, and wait for Franco to sort it out.
[Nexus 6  Original Android Development] sway40:
I'm thinking he's joking, calm down.

tappin from my Nexus 6
[Nexus 6  Original Android Development] stevessvt:
There's been a lot of people complaining about 22 so the assumption was he was too. If not I apologize.
[Nexus 6  Original Android Development] nexusmaniac:
Hmm, I didn't have any of my apps trying to optimise after flashing r22?

Because the WiFi networks you connect to are going to be completely different from a WiFi network that say I would connect to. Your results will vary, best way to find out for sure is to either leave them alone ;) Or just have a play with them, figure out what works and what doesn't. As with many Kernel things, it's very specific to the user, there isn't an answer per se :)
[Nexus 6  Original Android Development] 6-speed:
I'm noticing my dial pad is acting up with inputs as well. Calling my voicemail and entering any numbers I have to do it slowly. If I do it too fast it doesn't recognize the password or number inputs. Other than that everything else seems to be working fine.
[Nexus 6  Original Android Development] dtroup64:
I think you'll find the reference to Franco's cat is the giveaway. I could be wrong. I often am. This kernel has done nothing to improve my own cat, so there's that...
[Nexus 6  Original Android Development] stevessvt:
Ha, maybe ....I myself am having f/c of chrome and camera on 22, so I threw 21 back in and all is right again.
[Nexus 6  Original Android Development] madAdam6LOVE:
Loving R22 with Chroma.

What are the preferred high quality audio options? Is there a good alternative to forcing permissive and running V4A?
[Nexus 6  Original Android Development] franciscofranco:
Yes, that's been happening since Lollipop hit. I don't know why.
[Nexus 6  Original Android Development] franciscofranco:
Just got rid of those patches as well. Dunno why or how upstream net/ patches could be causing that crash. Thanks.
[Nexus 6  Original Android Development] franciscofranco:
Please download r23, I reverted a couple of upstream patches that might be causing some havoc.
[Nexus 6  Original Android Development] 6-speed:
The dialer inputs work correctly and I got the theme update for the app! I just donated for the theme and a meal for you and your cat. Thanks Franco!
[Nexus 6  Original Android Development] Popo001:
Well, I was ! Furthermore, have a look at your agenda and the date ! ;)
[Nexus 6  Original Android Development] rkwhyte2:
Dark Theme

So I had an update to the paid app yesterday and was expecting to see the dark theme but if it's there I don't see it. What am I missing? Also is anybody having issues with the way the website is displaying sidebars? I'm at work and only have IE which may be the problem.
[Nexus 6  Original Android Development] Prack:
Theme is top choice in settings. Working great for me.
[Nexus 6  Original Android Development] TR2N:
Hi Franco,

what is the deal with defaulting the kernel settings to power saving inside Performance Profiles?
[Nexus 6  Original Android Development] Fauert:
I don't know why my N6 with r22 just works :D .... Happy Easter for ALL ;) :thumbup: :beer:
[Nexus 6  Original Android Development] stas333:
Franco,

Thanks for updating the app, my CPU presets stick after reboot no matter what profile I'm on.
[Nexus 6  Original Android Development] rkwhyte2:
Well now I feel stupid I was looking under color profiles.
[Nexus 6  Original Android Development] ShredCreature:
I was going to ask the same thing... Perhaps thinking balanced would be the right default, though?...

But yeah, why is power saving default?
[Nexus 6  Original Android Development] stas333:
I'm noticing that r23 runs so much smoother and faster then r21 without any changes to the setup between the 2.
[Nexus 6  Original Android Development] trailblazerz11:
Yeah, I just glanced through the Hurr Durr Archives and LKML for these patches and nothing seems wrong.

Still, I'm gonna bisect and try and narrow it down.
[Nexus 6  Original Android Development] nexusmaniac:
I find it strange that it only seems to have affected a few users (That I know of ^^)

I know that for me at least, everything worked perfectly (After r22 was re-uploaded of course ;) )

Good luck with that then, hopefully you'll find something interesting! :)
[Nexus 6  Original Android Development] kifac:
Franco! I have no idea what you did but whatever it is...you have out done yourself! R23 Is running much better than R21 and R22!

Profiles are still auto switching to power saving upon reboot but im sure oyu will get get that worked out!

Thank you again!!
[Nexus 6  Original Android Development] trailblazerz11:
Yeah, thought it was weird as well. Only thing that might be unique is that I'm running TMO build LMY47M.

I mean they might have screwed around with radios and/or net for VoLTE and Wi-Fi Calling but what are the odds that it conflicts with the added net patches =/
[Nexus 6  Original Android Development] Nocturnal86:
FKU has stopped setting my color profile at boot and I have to do it manually after boot. Does anyone else have that issue?

I can also confirm that after reboot FKU has power saving profile ticked, however it doesn't seem like its really activated because it still shows the 2.7Ghz max freq.
[Nexus 6  Original Android Development] TR2N:
So maybe power profiles got broken?
[Nexus 6  Original Android Development] trailblazerz11:
[MENTION=3292224]franciscofranco[/MENTION]

So, I've finally isolated the crash to be triggered by Chrome Beta. Opening it will always crash for me when connected to network. (Explains why Comm: Chrome_IOThread in logs)

It will likely crash if Wi-Fi is on at boot since Chrome Beta autostarts and starts making network syscalls, which explains why I had crashes after flashing kernel or rebooting.

I figured out the patch responsible,

Enabled verbose debugging and it pointed to "kernel BUG at net/ipv4/tcp_output.c:852!" which is BUG_ON(!skb || !tcp_skb_pcount(skb));

Only 2 patches affected that file.

Bisect confirmed that the patch that causes trouble is: tcp: make connect() mem charging friendly

I can't be entirely sure but I think that the crash is due to missing this patch http://goo.gl/mZguKj, which was in the same patch set and also affects tcp_output.c

Too lazy ^^ to confirm it'll fix since it's a fairly large patch affecting a number of files and doesn't merge cleanly with shamu kernel source.

I'm testing a build with just that commit reverted, stable for the past hour. The 9 other net patches are probably safe to re-apply.
[Nexus 6  Original Android Development] TheySaidWhat?!:
Same for me after updating to r23 too, but I noticed my max. frequency was 2.265 Ghz.

But the phone still runs smooth like butter!?
[Nexus 6  Original Android Development] info[]box1:
Running Vomer's Cleancore ROM + Franco r²².. Reporting all is good. Just saw seen update, that was pretty fast for Franco
[Nexus 6  Original Android Development] hdtechk:
It screen protector issue with 5.1 even good glass ones I had to remove mine

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

Screen goes black when you make a call on 5.1, try this.
[Nexus 6  Original Android Development] dtroup64:
Nope. I don't think you actually read my post. I do appreciate you trying to help though.

I've been on 5.1 since the day it came out. I have no issues with a screen protector. My screen does not go black. My calls go through. I have no issues whatsoever with calls.

My dial pad actually was dialing the wrong numbers when IN a call. The dial pad.

Anyway, r21 is Perfect! and i'll try r23 when I get back from class tonight. :)
[Nexus 6  Original Android Development] manup456:
Having the same issue with color sticking after reboot r23 with Chroma.
[Nexus 6  Original Android Development] Johnny424:
I have been dealing with it sense 22 was released. I have tried everything that I can think of but I'm just not quite sure what the issue is. issue persisted for me over to 23. after every reboot the colors switch back to stock and fku does not load the profile, so I do it manually each boot.

and boy oh boy do the stock colors really make you wanna throw up after using vomers deep rich for a few weeks lol
[Nexus 6  Original Android Development] franciscofranco:
There were a new color commits on r23, one of them prevents new color values to be pushed when the display is off. Maybe that's what you experienced. I'll do a couple more tests about it and revert that patch if deem necessary.
[Nexus 6  Original Android Development] franciscofranco:
Just found out why Power-saving is highlighted on the newest FKUpdater update. It's just a cosmetic buga. Programming is really ****ed up some times. I fixed a weird-ass FC in a method that I use to parse STDOUT, and if STDOUT is null or empty I just return "0" (I should know better anyway, at least return -1 since it's an error). So when you don't have a specific Perf Profile set the getprop command that I use returns an empty string, so that parse will always return 0 and on my callback if it returns 0 then it means the user is using Power-saving. Took me a while to figure this one out. I'll push a bug fix release soon.
[Nexus 6  Original Android Development] paychex:
so.... you changed your cat food brand?
[Nexus 6  Original Android Development] franciscofranco:
Neps, she's needs to eat some special food to maintain the right weight to perfect testing conditions.
[Nexus 6  Original Android Development] franciscofranco:
Just confirmed color values do not apply during screen off. I'm gonna revert that Kernel patch for r24. In the mean time, don't turn your display off for about a minute after boot. It's a Kernel thing, not app, so don't ****ing go down rate the app.
[Nexus 6  Original Android Development] suku_patel_22:
Let's push some 1 stars guys [emoji12]

Sent from the sixth dimension.
[Nexus 6  Original Android Development] Stigga:
Apologies in advance but question about the wakelock options in the app. I know the new update added new one's that franco said don't mess with if you are not an advanced user but does that apply to all wakelock options or are some of them a no Brainer to toggle to save battery life? Thanks!
[Nexus 6  Original Android Development] info[]box1:
Vomer's Cleancore (stock 5.1) ROM + Franco r23 = $$$Euros
[Nexus 6  Original Android Development] franciscofranco:
Same for every wakelock toggle.
[Nexus 6  Original Android Development] jodvova:
Franco, why does screen brightness decreases when I click on selecting the color profile?
[Nexus 6  Original Android Development] franciscofranco:
How should I know?
[Nexus 6  Original Android Development] rkwhyte2:
My money is on it decreasing because when you are doing this it is an overlay.
[Nexus 6  Original Android Development] jodvova:
It used to work fine in early release of FKU when color profiles were just added. But then after a certain release it decreases the brightness.

Kinda pointless to lower the brightness and show the photo when selecting the profile. How would I be able to assess color accuracy?
[Nexus 6  Original Android Development] Chahk:
Take a look at Amplify module for Xposed. I know Xposed doesn't work on 5.1 yet, but the developer of that module spent quite a bit of time testing the effects of limiting various wakelocks. TL;DR version - some are safer than others.
[Nexus 6  Original Android Development] Stigga:
Awesome, thanks! I will check that out when Xposed is updated to 5.1.
[Nexus 6  Original Android Development] franciscofranco:
But I'm not doing anything, do you think I care about screen brightness when using my app? Lol
[Nexus 6  Original Android Development] trickster2369:
I think the point was for you to do some research by reading that thread to learn more about which wakelocks do what, so you can better understand the ramifications of disabling them.

Sent from my SinLess Shamu
[Nexus 6  Original Android Development] DutchDogg54:
While we're on the subject of wakelocks, any chance you'd be willing to include the ability to disable the BlueSleep wakelock, [MENTION=3292224]franciscofranco[/MENTION]?
[Nexus 6  Original Android Development] taranfx:
[MENTION=3292224]franciscofranco[/MENTION] Good work with r23. Totally got rid of bad wifi wakes. My Nexus now sleeps well :) Thank you!

When i switched from 5.0.x to 5.1 I noticed my moto 360 BT's range has reduced by 5-10feet. Did they reduce the BT LE Transmit power? Any chance we can raise it back via kernel?
[Nexus 6  Original Android Development] franciscofranco:
Nope, then you'll complain that BT stops receiving/transmiting during screen off.
[Nexus 6  Original Android Development] franciscofranco:
There were no BT commits on the Kernel space.

Glad the wakelocka toggles helped you greatly!
[Nexus 6  Original Android Development] nexusmaniac:
Why are you so far away from your Moto 360 ;) Jk ^^

I don't think so though, I can still be a good 10M from my 360 without the connection cutting out.

Are you still in LOS? Or going through walls, etc?
[Nexus 6  Original Android Development] taranfx:
When at home I trust my watch to deliver notifications rather than carrying Nexus everywhere. [emoji2] it used to work across two rooms (non LOS) now it doesn't work in second room.
[Nexus 6  Original Android Development] Tqpolo:
Is there any way you can make haptic feedback strength adjustment separate from vibrate strength adjustment? I would really like my haptic to be weak while keep my vibration strong.
[Nexus 6  Original Android Development] taranfx:
Cheers for incorporating that.

BT range difference is definitely there. Even a2dp speakers range has lowered by good number. If its not in the kernel, its somewhere in the ROM. Sigh they lowered it, I used to love extended Bluetooth range with nexus 6.
[Nexus 6  Original Android Development] franciscofranco:
Nop.

:(
[Nexus 6  Original Android Development] scandalousk:
Would love for someone to make this happen.
[Nexus 6  Original Android Development] LeonDX82:
Once in a blue moon I get a split vertical screen. It scrolls independently and only lasts a few seconds. I have balanced,interactive, and 422 min CPU set in the fku app. On 5.1 e.

Should I increase the min CPU? Thanks for kernel support!
[Nexus 6  Original Android Development] micdawg12:
Hey man, not quite on topic, but I just wanted to express my sincere gratitude for your kernels. You are part of the top tier community that make this development scene what it is. I have run your kernels on several of my phones, and I've been disappointed if you don't make 1 for a phone I have. I haven't had any issues with any of them, and if there are issues found by others, you fix it very promptly, and it's because of this, that all my friends with Nexus 6's have bought your app and use your kernel ( only 6 so far, but it's something ).

Thank you for your kernel and the support you give the community!
[Nexus 6  Original Android Development] mgear356:
2nd that.. there was a void when i was using s4, g2. knew franco from Galaxy Nexus and followed to nexus 4 and now back to n6.

its always less heat, better battery life.

Never felt better.. i also asked all my friends to support franco app for his awesome work.
[Nexus 6  Original Android Development] jeromechrome1:
Seriously though what is google going to call the next nexus phone my head hurts really bad r24 running great also
[Nexus 6  Original Android Development] szale9001:
Hey [MENTION=3292224]franciscofranco[/MENTION] , last day or so I have been getting an odd couple of random reboots. Until recently I was unable to get the ramoops because the phone would start hanging at the bootloader after the reboot and I would have to hold the Pwr button shut it off. Honestly, I wish I could tell you exactly how I reproduced it but it doesn't happen consistently. It usually happens when I am multitasking between apps and most often around 50% battery (though that could be coincidence). Anyways, I "lucked out" and got it to crash twice. Here are the logs. Hope they help.

Crash #1: only dmesg oops

http://pastebin.com/3RzEyyFk

Crash #2: both console and dmesg oops files

http://pastebin.com/pJeyBu62 (console oops)

http://pastebin.com/jnFu4P3K (dmesg oops)
[Nexus 6  Original Android Development] paychex:
Where's the pun?
[Nexus 6  Original Android Development] szale9001:
Ugh, I'm tired. I was referring to the fact (or attempting to) that while trying to reproduce the reboots it wasn't happening consistently and was, in fact, occurring randomly.

Yea... I'll just go ahead and edit that lol
[Nexus 6  Original Android Development] franciscofranco:
Nice crashes!!

That's not good :)
[Nexus 6  Original Android Development] szale9001:
Haha. So, I am always trying to learn more about this stuff. My guess was that the slimbus errors might be related to the recent throughput patches you merged? That said, I don't know what the deal is with kmalloc errors is. Would you mind explaining?