yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] calbruc:
Ah, these are great points and I admittedly never really thought about it before. I was just going on a purely anecdotal scenario: I flashed a new ROM and kernel, plugged the phone into my laptop, then watched some Netflix while tethered. It had been my experience that I could gain a decent charge by doing this. Last night I moved a percent or two in an hour. Maybe because it was a clean flash and the phone was building caches and whatnot, or maybe I was messing with it more than I realized, it being a new flash. Could be a few things, I guess, L vs M, new radio, what have you.

But I guess I'm curious now. What is USB fastcharge actually doing, if your output is limited by the port?
[Nexus 6  Original Android Development] magnamentis:
first a big smile because you're lucky if your device goes up 1 point or two, here it a happens that it goes down a few point on heavy load like for example while fastbooting something and later let it on usb charging during set up and app install.

however what usb-fastcharge is doing as i already hinted in that other post, is to let you charge at around 900mA if your computer port provides that much output while without usb-fastcharge you would be limited to charge with 450-500mA only, no matter how much output your computer's usb port could provide. in other words, the 500mA cap is a device specific software based limitation which usp-fastcharge will cancel.
[Nexus 6  Original Android Development] nathanchance:
You can just enable the wake gestures during the Aroma installer and not have to use an app to tweak them. But the ElementalX Kernel Manager is great for tweaking the kernel settings if you want to support the developer (best purchase I have made in a while). But I believe Kernel Adiutor will work just fine. Just remember that to get flar2's dt2w implementation, you have to enable sweep2wake in one direction; otherwise, you will have Google's implementation which can be unreliable at times. Just enabling sweep2wake is the best because it is reliable and doesn't wake up in your pocket accidentally.
[Nexus 6  Original Android Development] magnamentis:
even though i did not narrow it down like you did i think it might help others when i confirm quickly that there is a relation between the governors in use and random reboots. i had them, changed gov and they're gone. i'm now on elementalX governor and have no RRs. only difference from your case ( similar setup ) is that i had extremely good sound today, better than before, so much better that i recognized it immediately but then my sound sliders are on 1, 3 and 4 ( top to bottom ) and locked for what it's worth. thanks for the hint, didn't even consider that before, was just starting to play with settings after getting those RRs till it stopped. ( so spoiled with this kernel that i somehow blamed the device's electric :rolleyes: )
[Nexus 6  Original Android Development] mepo12:
i dont mind supporting the Dev, I will def purchase the EX Kernel Manager. I'm flashing xtrasmooth now on my N6 and it comes iwth EX kernel so I'll download that app now.

Once I download it, is it straight forward to setup dt2w and sweep2wake?

thanks
[Nexus 6  Original Android Development] nathanchance:
Yes, when you flash EX, you will have the options to set those up in the Aroma installer. If they don't stick, within the app there is a section called Gestures where you can set them up!
[Nexus 6  Original Android Development] mepo12:
When I flash the rom, I believe that EX is baked in already, so can I just install th EX Kernel manager and it'll be good to go?
[Nexus 6  Original Android Development] nathanchance:
Yes, you should be! You can check and see if there is an EX update from within the app and customize all aspects of it.
[Nexus 6  Original Android Development] :
I don't know for sure what's up with sound registers for us. I tried both fauxs and francos sound drivers. But ended up abandoning both, because for some reason it you add a printk showing the values after being modified... Positive values appeared to modify the values correctly (though with no detectable increase in sound), but negative values wouldn't shift as expected. Basically, 0 + 2 ended up being 2 but 0 + -2 ended up as like 254.

Maybe it was something I was doing wrong. Have you noticed the same?

Unfortunately, the standard printks don't show the actual register value, just what you're setting it to.

Sorry for the ot, it's not necessarily related specially to your kernel.
[Nexus 6  Original Android Development] aoleg:
With "elementalx" selected as the governor, cores #3 and #4 get stuck at full frequency after a while. Switching to another governor then back to "elementalx" solves this for a while. This happens irregularly, but it does happen. Today it happened twice, so I had to choose a different governor altogether ("conservative" seems to work without issues).

My system: latest "mra58r" stock (flashed boot.img and the rest of the system, then SuperSU and ElementalX), rooted with SuperSU v.2.52, ElementalX 3.06 with default settings. No O/C and no tweaking anywhere of anything.
[Nexus 6  Original Android Development] Brotuck:
Sometimes the phone gets really hot, after inspection one core is locked in full speed. It happens once a week.

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] nathanchance:
If you are using the ElementalX governor, I'd recommend switching to Interactive. I haven't had a stuck core since and performance/battery life has been very solid.
[Nexus 6  Original Android Development] magnamentis:
search the app, perhaps you know the term "cherchez la femme" lol in this context it's an app that keeps your device busy. best is to take a catlog, it will most probably show the culprit
[Nexus 6  Original Android Development] Brotuck:
Yes using the ElementalX governor, i will switch to interactive for a while to see if it helps
[Nexus 6  Original Android Development] bond32:
Decided to do some basic tests with the TCP Congestion Algorithms... I ran (on WiFi, Comcast) 2 tests for each, all were pretty close to each other. Highspeed seemed to have a good combination of low latency and good down/up speeds so I think I will try it for a while. Might test on Verizon's LTE as well. Anyone else have similar results?

I also tested governors, not scientific I know. Just ran GeekBench, found similar results between ElementalX and Interactive although ElementalX had slightly better multicore performance and Interactive had better single core. But I say better, they were small differences.
[Nexus 6  Original Android Development] Brotuck:
Already tried that, no app is using lots of CPU time. It is hard to see that after keeping the phone on and not rebooted for at least a week.
[Nexus 6  Original Android Development] nathanchance:
Yeah I noticed that one or two cores sticking was a result of the ElementalX governor, not a result of a run away app. This phone's hardware can get a little haywire at times but Interactive has been super smooth so just see if that works.
[Nexus 6  Original Android Development] magnamentis:
understand, yes it's difficult to find stuff if it's that kind of intermittent, no clue then, sorry that i could not help more :) :angel:
[Nexus 6  Original Android Development] bond32:
Regarding the Packet Schedulers - is the "pfifo_fast" the only one in this kernel? Any thoughts on others?
[Nexus 6  Original Android Development] magnamentis:
if that would be true it would happen to everyone which it does not. hence it's a combo of user space and kernel setup. still it's clearly not a kernel issue but a specific kernel setup reacts more sensitive with that other part which is yet unknown. if changing gov solves it for you that's all what counts for your setup but is not really a solution, more of a workaround. i'm on elementalX governor for 2 years now and never had such issues, not even tiny bit and then i'm using xposed and all kinds of mods one can imagine. i know it's apps that cause this but cannot prove it unfortunately. only way to find out would be to start from scratch and install apps in increments for proper troubleshooting but then if it happens once a week like for the user above that is simply not a reasonable effort. hence i would probably take the same approch like you and tweak until it stops. had a similar issue with random reboots on nexus 6 and still don't know what it was, changed governors and overvolted a bit and they're gone :)
[Nexus 6  Original Android Development] aoleg:
I opted for ondemand governor after all. Interactive not smooth enough I done apps. Would love to get back to elementalx governor of the issue with stuck cores it's fixed.
[Nexus 6  Original Android Development] magnamentis:
what do you expect, that the dev fixes something that is not broken. you can choose, either you use the gov which works for you or you find the reason for the issue. read the post above and previous posts. if eleX gov would be the problem 90% of all users of this kernel would have the same issue bit after all it's only hand full, 1% perhaps. what does that tell you? you have to fix it yourself if you want use eleX gov. BTW, ondemand caused randrom reboots for at least 3 reputable forum member with this devcice. just mentiioning it in case that you would encounter RRs.

ondemand AFIK is stock gov and indeed RRs are an issue across all forums i've been reading in, hence have an eye on it.

if interactive is not smooth that as well hints to a user space issue because interactive is very smooth normally but obviously handles the underlaying problem in another way while EX gov keeps one core running high.
[Nexus 6  Original Android Development] :
The real issue here is that people are reprint a bug with the governor... A big which only presents itself supposedly after a week of uptime. Yet... The isn't a single dmesg or logcat of the issue as it happens.

So people really expect that something can be replicated and troubleshot when it only happens to a handful of people with the only information being "after about a week of uptime". Based on that, it could literally take years to reproduce, troubleshoot, patch and test for one person.... Especially if he doesn't get the same thing.

Seriously, submit logs with you bug reports. It's pretty important... Actually, I think it's even a sticky somewhere... Like the top of every forum or something.
[Nexus 6  Original Android Development] aoleg:
Hmm, that's not how it works in the real world :) But thanks for the tip on the "ondemand" governor; I'll watch for random reboots when using it. I tried "conservative", and it's not smooth enough in some games. Tried "interactive", and then there are stutters in my favorite launcher. "ondemand" looks like it's well balanced. I really liked the "elementalx" governor, but it does get the two cores stuck every once in a while. I'll certainly try exporting logcat if the next time the cores are stuck I happen to be at home with a PC accessible. Unfortunately, this mostly happens on the go where I just need the thing to "work".
[Nexus 6  Original Android Development] magnamentis:
what does that mean, that's exactly how it works if one is not too lazy to troubleshoot. games are something very special and cannot serve as references but then i recommend to switch to performance governor for gaming, you can do that with a tasker script to switch upon opening certain apps/games. i really have difficulties to digest that sentence about the real world, i mean you want things to work on top of the scale (games) and have an issue and ask for help and in addition ask the dev to go to work and fix a governor which works flawlessly and which is not built with gaming in mind and then you blatantly refuse to do a proper troubleshooting. that's not so rare of an attitude on XDA but saying it openly is.

i wish you luck however and perhaps someone else has too much time left and the nerve to deal with advice resistant users, sorry but i don't.
[Nexus 6  Original Android Development] aoleg:
Offtopic: OK, the real world example. You rent a vacation home and a coffee maker breaks. "It worked for 99 guests before you, so it's you who'll be fixing it!" says the owner. Now, don't get me wrong; I truly appreciate the work done by flar2, and I supported the developer by purchasing the kernel management app. I don't feel like anyone owes me anything; far from it. However, if something breaks down, hearing "you have to fix it yourself" and "too lazy to troubleshoot" in return for a bug report does sound dangerously close to an insult.
[Nexus 6  Original Android Development] magnamentis:
i hear you and take it as your personal opinion which i don't share because i had 68 years of time to learn how to solve problems LOL but no, insulting is not the purpose, more to shake the foundations a bit as a wake up call but then i have no issues to conclude this with the following:

"Let's agree that we disagree" LOL i hope for you that i'm totally wrong and someone will solve the problem for you, i obviously can't, sorry.
[Nexus 6  Original Android Development] :
Just install the app syslog

It literally takes all the logs at once for you, puts them in a time/date folder in your sdcard and even zips them for uploading. The nice thing is, if you don't want to let it stay stuck for long you can take the logs, reboot, then retrieve them from that folder.

Sorry, but with the number of log taking apps available... not having a PC available is a poor excuse for not having logs (short of times where your phone becomes completely unresponsive). Not trying to be offensive or insulting... I just see that as an excuse ALOT on these forums.
[Nexus 6  Original Android Development] aoleg:
Thanks! Will try the syslog app tomorrow. Hope I can nail that but down.
[Nexus 6  Original Android Development] tkalli:
OT, I have 12 more years of learning on you. Been at this since before the heyday of Moto. Never ending experience, but it keeps my old brain working.

:o
[Nexus 6  Original Android Development] rignfool:
This... Is BCL throttling...

When it un-throttlea... Cores 2 and 3 come back with performance governor...

Flar is aware

---------- Post added at 01:51 AM ---------- Previous post was at 01:45 AM ----------

It is not a governor issue... It's a throttle issue...

You will notice it happens after going to recovery a lot...

When you boot recovery... Your battery reports true... When you boot back to the OS... Your battery reports much lower... Thanks to that battery learning commit...

Your phone then throttles cuz it thinks your phone is going to die during a reboot... Which would corrupt your data...

The workaround I found... Is to use a kernel tuner to set elementalx governor on boot... I'm usually out of the throttle by then...

It does make for SUPER long app optimizing time... 2 cores... 2ghz speed... Ugh
[Nexus 6  Original Android Development] aoleg:
rignfool, the two kernels are not throttled or disabled (put offline). They are stuck at full speed with the "elemental" governor. So far it did not happen with the "ondemand" government I've been using. I'm still waiting for the bug to occur to make a log snapshot.
[Nexus 6  Original Android Development] magnamentis:
good morning my friend, nice finds, thanks, one more day adding to the learning curve, i have come across some similar information about the volume fluctuation below 80% battery while it was additionally mentioned that the device's electric system may be "flawed" a bit. fortunately i'm 95% of all times on charger, no matter where :) even have an outlet on my motorbike :) contribution very much appreciated as always :good:
[Nexus 6  Original Android Development] rignfool:
Yes... And if you read what I wrote... You would see I said when it returns from throttle...

It happens on any of the kernels that do not disable BCL throttling...

blu_spark is the oddball since he still uses a hotplug
[Nexus 6  Original Android Development] aoleg:
rignfool,

I re-read your previous posting and still could not understand the connection between the two cores being throttled (and/or disabled) and the two cores being stuck at full frequency. I also assure you that this behavior (of the two cores being stuck at max freq) is specific to ElementalX kernel with "elementalx" governor *only*. (During the last 6 months or so, I used Franko, Lean and ElementalX, the latter with "elementalx", "conservative", "interactive" and "ondemand" governors). Finally, you mentioned the boot sequence and, specifically, the bootloader. The behavior I described has nothing to do with any of that; instead, the two cores get stuck randomly during normal use (and never after a reboot - that would be too easy to reproduce!)
[Nexus 6  Original Android Development] ArcMage:
I've got another one.

https://drive.google.com/file/d/0B5s7dn0NW5g8aGg5QkNFZk9EdjA/view?usp=docslist_api

Crash while switching tracks in Pandora. A bunch of tainted kernel threads in the end there.
[Nexus 6  Original Android Development] rignfool:
I assure you... Francokernel does it as well... You just prolly didn't notice...

Now... When BCL kicks in... It takes you to 2 cores at 2ghz...

When it normalizes... It returns cores 2 and 3 to online... Unfortunately... It does not listen to your original governor choice and defaults to performance...

You don't have to believe me...

It's just the way it is
[Nexus 6  Original Android Development] flar2:
It can happen on any governor and it happens on other kernels, including the stock kernel.
[Nexus 6  Original Android Development] flar2:
I've pared this kernel down to be virtually the same as stock in every way that matters. I still use this phone as my daily driver and have had no reboots ever since Marshmallow.

I think they are caused by things in user space or it's the flaky hardware.
[Nexus 6  Original Android Development] ArcMage:
Do you have any theories on what hardware or userland problems could lead to tainted kernel threads and page faults in very specifically the kernel, without generating any app-level errors or gross device effects, or should I shut up?
[Nexus 6  Original Android Development] :
68 + 12 = 80...? You're truly 80?? Wow, now this is what I call a real senior member! :) congrats mate!

Nexus 6 64gb - CyanogenMod 12.1 (Android 5.1.1) [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] flar2:
Could be anything. Like I said, this kernel is pretty much stock if you leave default options. If there is a problem, it's not due to anything I've done. Also, I work this phone super hard and never get reboots.
[Nexus 6  Original Android Development] tkalli:
OT

Yes, I'll be 80 in a month. Don't let age influence what you do.

:o
[Nexus 6  Original Android Development] Lancez:
Hats off to you, Sir
[Nexus 6  Original Android Development] golfgtiedition30:
First time flashing EX here. Looking forward to testing over the weekend to see how it settles. Cheers :)
[Nexus 6  Original Android Development] :
You've been missing out. ;)
[Nexus 6  Original Android Development] arifqur:
Wishing you many more healthy and productive years
[Nexus 6  Original Android Development] FriendWithin:
I've been eyeing this kernel for a long time. Is it worth switching to from Hellscore? I'm still unsure whether I should.
[Nexus 6  Original Android Development] Lancez:
I can't say whether it's worth to switch or not. But EX kernel is the only one I've been using on all my current devices (Nexus 5, Nexus 7 and Nexus 6). Give it a shot and see for yourself, after all you are using an android device not iPhone :)
[Nexus 6  Original Android Development] harkirat01:
Experts need some help.

My phone's just a month old and under warranty of course. So I am a little worried about the whole warranty thing, if I root and then install the ElementalX kernel. But I've seen people post insane SOT with the nexus and that's really tempting me to go ahead with it.

Would it be possible to return to pure stock if required at a later stage?
[Nexus 6  Original Android Development] DroidIt!:
Heya [MENTION=4684315]flar2[/MENTION]. :) I know you're pretty security oriented and thought you might find this xdaforums.com/nexus-6/general/root-t3231211 kind of interesting. It was posted by somebody in the slim builder thread and made me think of some things I hadn't thought about before with SuperSU. :)
[Nexus 6  Original Android Development] nathanchance:
Yes, you would just need to flash the factory images from Google to return to stock if you need to RMA, very easy process.
[Nexus 6  Original Android Development] harkirat01:
That simple? Really? Great then. I read a couple of articles saying that it's still possible for the service centre guys to understand whether the phone was rooted or not and all that stuff, but I mean what's the use of buying a Google device, if you can't play around and customize it as you like?!

I flashed the latest 6.0 manually so at the moment I have the bootloader unlocked on my device. My PC has all the drivers installed along with the adb debugger. So I just need to download the utility from elementalX website and then flash it on my device, right?

What's the feedback on their app - EX Kernel Manager?

My main purpose of installing a custom ROM is to improve my battery life, more than anything else. Should I take the plunge or stick to my stock version? Currently I get around 3 hours of SOT over a day and half usage.

Thanks in advance
[Nexus 6  Original Android Development] DroidIt!:
It is pretty easy no matter what ROM/kernel you have on your phone you just download the latest google image and either use a tool to to restore to factory or unzip the zip :) and fastboot flash each part. I've RMA'd an N6 myself and I've noticed that the tech center guys don't necessarily look at that stuff. ;) Now, I'm not saying that one might not catch it, there is an off chance, but I just flashed stock and relocked the bootloader and I was all good. It's ultimately up to you though. The only real advice I'd have is just read a lot so you know how to get out of any sticky situations you might run into and before you know it your device protection will be up anyways. :)
[Nexus 6  Original Android Development] wuvio:
Hey, would you like to share with me where to find miscellaneous setting in the phone, I can't seemed to find it any where inside the setting
[Nexus 6  Original Android Development] nathanchance:
In that post, I'm referring to the miscellaneous settings of the ElementalX Aroma installer, which is the last screen before the install EX/abort installation screen. That post isn't relevant anymore if you are on Chroma 11/22/15 since it allows you to have SELinux in Enforcing. If you are on a different ROM, check to see if they have the necessary patches to allow it.
[Nexus 6  Original Android Development] rignfool:
*cough* in the aroma installer...
[Nexus 6  Original Android Development] Alxoom33:
It's in the EX Settings App, you can download it from the Playstore. Excellent app.
[Nexus 6  Original Android Development] xhamadeex:
Is it possible to control vibration intensity in this kernel?

Because the option does not exist in kernel auditor!
[Nexus 6  Original Android Development] suku_patel_22:
Guys do checkout the updated Chromium for snapdragon devices. Its fast!!.

Sunspider scores on my N6 are

Chrome stable : 1131

Snappy Chromium : 607

http://xdaforums.com/general/general/guide-building-chromium-snapdragon-t3255475
[Nexus 6  Original Android Development] flar2:
Yes, in EX Kernel Manager