yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] numerouknow:
francokernel r10 + vomertweaks dynamic.

at this rate my phone should last around 40hrs with 6hrs sot on a single charge despite poor signals at my place.
[Nexus 6  Original Android Development] zige:
My phone has been idle 1h31min and still not even 1% has go... So if i don't need to use my phone, battery will stick at least 6 days... :p
[Nexus 6  Original Android Development] big_adventure:
Any chance of sharing a log during the problem and without the problem, optimally with a video showing both as well?
[Nexus 6  Original Android Development] GregNexus:
Sharing a log would be no problem, how do i share one? Maybe Franco would take a look into it.

Making a video... dont know if the effort is worth it. You only will see stutters on r10 and r8 is running fine:D

It has to do something with the changes that were made in r10...

still love this kernel <3 (r8 :D)
[Nexus 6  Original Android Development] big_adventure:
There are a few ways to take a log: connect a cable to the computer, then use adb log and send the output to a file. Or download an app like CatLog from the Play Store, start it, start recording, then switch back to Home and demo the issue.

In both cases, do the same things at the same pace in the two separate logs. Once you've done so, post the logs on pastie.org, and post the link here.
[Nexus 6  Original Android Development] pantmunu:
Man I live around Brooklyn and my service is s*** .
[Nexus 6  Original Android Development] franciscofranco:
There are no changes on r10 that affect deep sleep in any way. For the 1000th time, deep sleep is just a state where the device components are gated. If there's a wakelock the device won't be on that low sleep state. I have never, ever, ever messed with the Wakelock API on the Kernel. There are two possible scenarios: some app decided to keep a lock, or sensor_ind lock is being held (this happens fairly regularly, only a reboot fixes it). Chances are your reboot to flash an older Kernel fixed it, not the new Kernel per-se.
[Nexus 6  Original Android Development] suku_patel_22:
With no change in usage pattern or apps, my SOT has dropped from 5+ to 3.5. My idle drain gas gone down.

Will switch to interactive tomorrow and will see how it goes.
[Nexus 6  Original Android Development] franciscofranco:
That won't do anything. Read my previous post...
[Nexus 6  Original Android Development] suku_patel_22:
No sensor_ind here. But will continue to monitor some more.
[Nexus 6  Original Android Development] oscillik:
I know it's a bit off topic, but IDGAF.

It's pretty hilarious reading comments on the internet from people complaining that they have to pay $5 for the app, for example, "just to turn off the charging LED" and other ridiculous statements of a similar nature.
[Nexus 6  Original Android Development] oak:
I bought the app and have also donated more than once, not for some feature, but to say thanks for a great product. Also, and more importantly (to my own self interest) , to keep the dev developing.
[Nexus 6  Original Android Development] oscillik:
when this concept is explained to these people, the common response is either that of indignation or ignorance.
[Nexus 6  Original Android Development] GregNexus:
Thanks for your awnser franco! That should be clear now.

"Chances are your reboot to flash an older Kernel fixed it, not the new Kernel per-se"

what do you mean?

Do you have a solution why r10 makes the phone for some people stuttering? A flashback to r9 solves the problem for some people.. (i use r8 - smooth animations as ****).

& Thank you for your awesome support! You´ll get a donation for a nice meal, pizza, pasta or a burger?:fingers-crossed::good:
[Nexus 6  Original Android Development] pr0cl1v1ty:
I bought the app for day 1, hard genius work from a awesome man... Deserves a beer.
[Nexus 6  Original Android Development] big_adventure:
Given that most of us aren't having this issue, and nobody who IS seeing it has provided logs of the situation both with and without the effect (so, with an unaffected version of the kernel), it seems unlikely that he has a solution. Just using logic here.

Has anyone who had this issue (there seem to be 2 or 3 people max) tried deleting their first downloaded r10 and re-downloading it? It shouldn't be that, but yanevano.
[Nexus 6  Original Android Development] slekkas:
These devs work hard for us to have a great experience with our phones. The least we can do is buy their apps that cost practically nothing just to show our appreciation.
[Nexus 6  Original Android Development] 6-speed:
The only time I had issues with a couple releases is when I used the auto flash. If I flash it manually through TWRP I don't have any issues....as of yet. I always manually flash now.
[Nexus 6  Original Android Development] franciscofranco:
Absolutely no correlation, flashing manually or auto-flashing is exactly the same thing, writing to a block.
[Nexus 6  Original Android Development] Tzfardaya:
But doesn't one use print and the other cursive writing?
[Nexus 6  Original Android Development] aviz1911:
Hmmm, while auto flashing some versions fku used *'s too :p

[MENTION=3292224]franciscofranco[/MENTION] Can we ****(alpha) test your game application?

Will it work on my play station 4?
[Nexus 6  Original Android Development] big_adventure:
One is actually Times New Roman, the other is Comic Sans. You can guess which works less well.
[Nexus 6  Original Android Development] michmeister:
I think some people just tend to blame every issue they have with phone on the kernel. I found every version of this kernel to be amazingly smooth with absolutely no issues no lag no stuttering. People need to look elsewhere other then a kernel that works perfectly fine for 99.9 % of people using it.
[Nexus 6  Original Android Development] big_adventure:
Supporting Franco's reply, I've autoflashed at least 100 times between the N5 and the N6, and never had a single issue. I did have bad signal once or twice (flashing in an EDGE area), and had the autodownload fail, but that's the only autoflash that's ever failed for me.
[Nexus 6  Original Android Development] 6-speed:
I figured it was the same either way it is flashed, thank you for your work. A kernel this good makes me want to root my N7 just so I can run your kernel there too!

Thanks guys, there absolutely could have been a signal issue. Also now that I'm thinking about it more, wasn't a bad r7 uploaded mistakenly? I'm betting that's what I was thinking of.
[Nexus 6  Original Android Development] big_adventure:
Not necessarily - it is entirely possible that there is a bug that only impacts certain people in certain situations. But to find it, we generally need logs or a more precise description of the problem than "some interpreted level of stuttering swiping through homescreens." That doesn't mean that it doesn't exist, just that it's really hard to troubleshoot things blind. Since I, personally, have seen issues (with phones, computers, network equipment, security equipment, mission-critical applications, etc.) that didn't affect more than a tiny number users, and, despite my general history of competence and of helping people having issues (as well as being a respected IT pro in the real world), was lambasted as an IDIOTNEWBPROBLEMCANTEXISTCAUSEIDONTSEEIT****YOU, so I never dismiss out of hand when someone says they have a problem. Finding the cause can be harder, and it's nearly impossible without more than "A couple of people see some undefined level of stutter."

tl;dr:

Need logs, need videos, need configuration details, need stuff to work with, but don't be a **** to people you don't know who claim a problem you don't have.

---------- Post added at 06:47 PM ---------- Previous post was at 06:46 PM ----------

Yup, that happened, and true to his habits in such situations, Franco fixed the thing in minutes, not hours or days. He's one of the most responsive devs I've ever seen (or heard of, for that matter).
[Nexus 6  Original Android Development] michmeister:
Whose being a **** to people? Hope you weren't referring to me just for complimenting this kernel.
[Nexus 6  Original Android Development] frost_nz:
To be fair, I imagine you'd probably be sharing the issue if you were seeing it too so there's no need to get wound up about it.

As I've stated, I'm also seeing the stutters in R10. And I will post logs and and any a video when I get time.
[Nexus 6  Original Android Development] aviz1911:
Why start an essay writing competition in a kernel thread?
[Nexus 6  Original Android Development] Tzfardaya:
Because we can.
[Nexus 6  Original Android Development] zige:
It's always kernel or rom, not ever example bad app or something. "It's you fault, not mine. This rom suck. This kernel suck. F*ck you".
[Nexus 6  Original Android Development] big_adventure:
Heh, no, I might have used your quote as a starting point - but you DID start throwing the blame game and applying it in your post.

---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------

Because I win essay-writing competitions? ;)

---------- Post added at 07:56 PM ---------- Previous post was at 07:40 PM ----------

I don't think I saw anyone saying that. They said directly that "r9 = no problem, r10 = problem, flashing back to r9 = no problem." That doesn't mean that it IS a kernel (or FKU) issue, but it just as much doesn't rule it out. My point there was that you can't logically dismiss out of hand a claim from someone without a ton more information, yet despite that, people sure seem to want to, and do so while issuing mildly denigrating statements.

Of note, and as stated, I have no such issues. Also of note: this is Franco we're talking about - if someone comes in with good evidence of a specific issue, he'll address it. He may have to drop a few **** bombs on the way, but he will read logs that he doesn't think will apply, and he'll double-check code that needs double-checking. If he'll do that, why does anyone else feel the need to get either passive-aggressive or outright aggressive with people bringing an issue?

That said, people who bring issues without giving precise information don't merit anything more than "get more information and come back next time!" as a reply. Lots of people in this thread are totally willing to help where they can, but "I see dead people...er...stuttering" isn't enough to go on in general.
[Nexus 6  Original Android Development] aviz1911:
Is your keyboard OK ??
[Nexus 6  Original Android Development] big_adventure:
Not usually - it complains a lot. You should see how hard it is to feed a keyboard Zoloft.
[Nexus 6  Original Android Development] zige:
Yea i know that. I just said regarding my experience what usually people do on here XDA and other forums. They always think that it's rom, kernel or phone issue when it can be app issue and when people have said that issue isn't here, issue is caused by some app they answer "no, it's phone issue, not app". You understand what i mean by this?
[Nexus 6  Original Android Development] sn0warmy:
Ugh... my stuttering came back and I started to get a few instances where, when turning on the screen, only half the screen would turn on and become responsive. I had to turn the screen off and on a few times to get it to work correctly again.

This was on stock rooted/decrypted. I experienced these issues with both the stock Franco settings and again with 4 cores set to run full time. I tried using the different governors as well but none of them seemed to resolve it. Back to stock kernel I go...
[Nexus 6  Original Android Development] Krunk83:
Stock seems to be the only kernel that is a smooth experience throughout. Really disappointing.

Nexus 6
[Nexus 6  Original Android Development] Tzfardaya:
Are you undervolting? That sounds like either an undervolt or hardware issue... (may need an rma)
[Nexus 6  Original Android Development] michmeister:
I didn't blame anyone what the hell are you talking about. All I said is I found the kernel to be great and I think people tend to auto complain about the kernel when they have issue. I think you have issues because in no way was I insulting to anyone.
[Nexus 6  Original Android Development] enzoevo:
These stuttering issues I believe are caused by app/system crash reports being written to the sdcard. I had the same issue on another device and after diagnosing the issue for weeks was able to find the problem. Turns out writing a 30MB dump file every time the crash occurred caused significant stuttering. I found it by carefully inspecting my logcat and finding the dump file. Analysing the dump file showed the cause. Fixed the issue and all stuttering/lag/hesitation disappeared.
[Nexus 6  Original Android Development] simms22:
all those with stuttering or that think that the only smooth experience is on the stock kernel.. learn to set up the cpu according to how you personally use your phone. just because francisco franco sets up his kernel one way, does not mean that you cant change the way your cpu is set up. he can not predict how everyone uses their phone. he can only set it up how he feels comfortable with. chances are that the way you use your phone it will need a different set up. i have no stutters on my device.
[Nexus 6  Original Android Development] big_adventure:
Here is EXACTLY what you said then:

"People need to look elsewhere other than the kernel" isn't fair when you don't know what their issue is and haven't experienced it. All that has been reported is a couple of people having very unspecific stuttering on r10, after not having it on r9, and that returning to r9 fixes the issue. Now, I don't know, any more than you do, what the problem is, but you are implying that you are absolutely sure that there is not a kernel problem, and doing it in such a way as to imply that the people suggesting it could be the kernel are not only wrong but are, probably, just complainers looking to blame the kernel for their issue.

That said, you managed to turn this new post into a directed personal insult, so please, cease and desist on that **** straight away.
[Nexus 6  Original Android Development] frost_nz:
Take a breather dude, you're trying "not to be insulting" but you're saying people have issues :p Your first post sounded to everyone like you were dismissing their input and presuming that didn't know what they were talking about (whether you meant it to come across that was or not).

Cheers for the heads up - I'll see if I can track down any similar issues! :)
[Nexus 6  Original Android Development] franciscofranco:
I'll say again, that half screen **** is a bug on the Nexus 6, it happens on 100% stock too.

No, that's bull****.

This x10000;
[Nexus 6  Original Android Development] frost_nz:
I agree. I'm slowly working my way though all the settings and seeing how they work together and the differences they can make. The Gingerbread Man's FAQ thread is very informative. Learning a lot from there: http://xdaforums.com/showthread.php?t=2532422
[Nexus 6  Original Android Development] sn0warmy:
For me, the stuttering and half the screen not turning on, occurs after simply turning the screen on and unlocking the phone. It happens even after a fresh reboot and wiping caches. This shouldn't be happening, especially with stock settings, no matter what your phone usage is like.

And I don't have either of these issues with the stock kernel.

How can I tell if I'm undervolting?
[Nexus 6  Original Android Development] murdok83:
If you cant tell you are not undervolting :)
[Nexus 6  Original Android Development] franciscofranco:
That FAQ is linked in the OP. Unfortunately I'm sure a lot haven't read it :)
[Nexus 6  Original Android Development] simms22:
then set up the kernel like the stock kernel. "stock" franco kernel isnt the same as the default for the stock kernel, its how francisco franco chooses to set up his kernel. it might or might nor be good for you, its not good for me. but when i chose to set it up according to how i use the device, its perfect(for me and my device).
[Nexus 6  Original Android Development] frost_nz:
Yeah, that's where I found it when I first visited this thread. Sorry, should have mentioned that in my other post!

Cheers for all your hard work - Proud user of the full app and will flick you though a donation once pay-day rolls round (finally). :highfive:
[Nexus 6  Original Android Development] anthonyg45157:
I haven't had any noticeable or predictable stuttering. Very seldom will something seem to lag or stutter. I'm on pure shamu on Franco's r10. I even have vomer tweaks on dual core mode and no higher than 1.3ghz. I have only noticed HDR takes a little long to process when under clocked.

Just my 2 pennies

Thanks Franco, don't listen to others(people who aren't actually trying to resolve issue just complaints), this kernel is smoother than stock even under clocked by 50%!!!!

Sent from my Nexus 6
[Nexus 6  Original Android Development] pr0cl1v1ty:
Buy the Vomertweak app and push the 1 button. ALL Stutters were gone and battery perfect.
[Nexus 6  Original Android Development] frost_nz:
Wow - Totally just read the "pennies" part as.... something different lol :laugh:
[Nexus 6  Original Android Development] rignfool:
Pervert

Sent from my Nexus 6
[Nexus 6  Original Android Development] sn0warmy:
Don't tell me what to do. :silly:

Kidding. I'll keep working at it.
[Nexus 6  Original Android Development] simms22:
stock is 2649mhz/1728mhz with mpdecision being active, with the interactive governor. try that out :)
[Nexus 6  Original Android Development] franciscofranco:
Stock is not 1728MHz as min. It's 300MHz.
[Nexus 6  Original Android Development] sn0warmy:
I purchased the Vomertweak app to use alongside Franco's paid app. Not sure what you mean by pushing the "1 button" though. I'm not seeing anything of that sort.

However, I do like that the app allows you to force enable 4 cores with just 1 button push.
[Nexus 6  Original Android Development] michmeister:
I'll state my opinion when i want thank you. And I don't need to use vulgarities.

---------- Post added at 04:22 PM ---------- Previous post was at 04:22 PM ----------

And I stand by what i said. I know people have issues and understand that but it's not always the kernel.
[Nexus 6  Original Android Development] big_adventure:
It only takes 4-5 in FKU... (From the CPU Manager tab, tap Hotplug control, tap load threshold, type 0, hit enter, you are done)
[Nexus 6  Original Android Development] simms22:
maybe so. every time i set up the stock kernel, its at a 1728mhz for a low. of course its mpdecision messing around with my eyes. but thats what i always see before i change it, 2649/1728.
[Nexus 6  Original Android Development] franciscofranco:
It's mpdecision + thread migration boost + touch boost = they all increase min frequency for small periods of time (20ms and 40ms). It goes back to 300MHz after wards.
[Nexus 6  Original Android Development] sn0warmy:
Roger that.

EDIT: you've shown me how to disable/enable mpdecision. Is there a way to do it without having to do it every reboot?
[Nexus 6  Original Android Development] big_adventure:
You have spectacularly failed to understand my point.

You said in your post that I have issues. Here is you, replying to me:

That makes it a, as I stated, personal insult to me, if, admittedly, a very slight one. Still, there is no real place for that. In addition, it's just not true - you, in your first post on the topic, berate people for complaining about issues that you, personally, don't have. And that's not a way to help.

If you want to go back and actually read everything I wrote, and not just the joking "tl;dr"-tagged summation, you'll see that I was referring to "people" making generalized dismissive statements not being the best way to deal with other people trying to report issues. I never called you, personally, anything. Sure, the entire first post was based on a quote from you, but I never single you out. Evidently, you took something in there personally. That's on you.
[Nexus 6  Original Android Development] simms22:
so its more than just mpdecision thats playing with my eyes..
[Nexus 6  Original Android Development] SmokeyMon:
What is your pixel density set to? Custom value? For example if I set my DPI to 493. I am able to reproduce the screen going half black in chrome, only when rotating the phone clockwise. But if I use 460 or the default value I cannot repro. I suspect the kernel or how many cores are lit at any given time are not a contributing on a bug like that. That assertion could be wrong but more to the point, there are often a lot of variables at play. If your screen is constantly mis behaving when reorienting to landscape and it is pervasive throughout many apps, I would flash stock and try duplicate as to attempt to rule out the hardware and original software.
[Nexus 6  Original Android Development] simms22:
not that i know of. unless the kernel is made to have it that way.
[Nexus 6  Original Android Development] wrongway213:
Has anyone investigated if Imoseyon's no-freq-mpdecision zip from Lean Kernel would work for other kernels? It disables mpdecision on LK until another ROM or kernel is flashed, just flash with every update. I don't know if it works on other kernels or not but its an idea.
[Nexus 6  Original Android Development] simms22:
i think that in this case, we are enabling mpdecision, not disabling :)
[Nexus 6  Original Android Development] samdroid24:
Franco's Kernel is a thing of beauty, a delicate art. Muchos Gracias.

Sent from my Whale.
[Nexus 6  Original Android Development] wrongway213:
Pretty sure it's disabling it based on this post http://xdaforums.com/showpost.php?p=58135730&postcount=1474 if not, I am very much misinterpreting that post and would greatly appreciate if you could fill in the blanks for me.
[Nexus 6  Original Android Development] simms22:
he is complaining about "stutters", and said that the stock android kernel he doesnt get stutters. so i told him to set up franco kernel like the stock kernel is set up, mpdecision and all.
[Nexus 6  Original Android Development] sn0warmy:
Dammit wrongway213, pay attention...

:laugh:

Back on topic...

I changed governor to interactive and set my min frequency to 1728 and left everything else stock. So far it's acting like the stock kernel and is flawless for me. It will take some more usage to confirm. But now I'm starting to think that having the min freq set to 300 with this kernel (and others) may have been what has been causing the initial stuttering for me the whole time.

I may go back to conservative governor with min at 1728 to see how it handles.
[Nexus 6  Original Android Development] simms22:
lol. and hes the one paying most the attention here! i think we just confused him because what we are talking about is the opposite of what i always talk about :)

---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------

it very well could be
[Nexus 6  Original Android Development] franciscofranco:
mpdecision is disabled on the ramdisk, please don't mess with it or you'll have problems because I run my own core management driver.

Don't do that, you'll have massive power drainage during usage.
[Nexus 6  Original Android Development] sn0warmy:
Thanks for the heads up. I'll stick with interactive and see how it does.
[Nexus 6  Original Android Development] simms22:
massive, i dont know about. but with mpdecision disabled, he will get a little extra battery drain for sure.
[Nexus 6  Original Android Development] franciscofranco:
It's still running my Hotplug driver, so I'm doing the work for Mpdecision minus all the cpu frequencies management crap that they do with the binary.
[Nexus 6  Original Android Development] simms22:
oh, not fun there!
[Nexus 6  Original Android Development] Krunk83:
It's not bull**** when several people are reporting it. Even with vomer app with performance and 4 cores running at all times the animations of switching apps and unlocking the phone is stuttery as hell. Going back to the stock kernel is smooth. I can say though that it happens on all custom kernels, not just Franco.

Nexus 6
[Nexus 6  Original Android Development] dipstik:
I think he's referring to the 1.7ghz min frequency.
[Nexus 6  Original Android Development] simms22:
he was, i know :)