yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] mm360x:
Charging through wall very slow.

So ever since I flashed the newest version of ElementalX on my Nexus 6 i.e. version 3.09 I have been getting very slow charge speeds when charging through the original nexus 6 turbo charger. I used to get around 1750mA /hr before and now after flashing this update I am only getting around 700mA /hr. This charges my device very slowly. I have Chroma rom running with the latest update and ever since I flashed the version 3.09 I have been getting very slow charges through the wall with the original turbo charger.

Is this a kernel bug or do I need to check/change any settings. Are any of y'all facing this problem and if you know the solution to this it would be a great help because I love this kernel for battery life and performance. Thanks.
[Nexus 6  Original Android Development] flar2:
Nothing has changed. The battery or thermal driver is probably limiting charge speeds at the moment. It will go back to normal.
[Nexus 6  Original Android Development] mm360x:
This problem has been occurring from the last 2 days because like whenever I try to charge even in cold conditions (battery temperature is always below 20°C when charging) it still is just below 700mA all the time.
[Nexus 6  Original Android Development] flar2:
This is nothing that I changed in the kernel, it must be something else.
[Nexus 6  Original Android Development] Lancez:
Dose 3.09 work on the new MMS29Q? :)
[Nexus 6  Original Android Development] flar2:
Probably, but you might as well just hang on til I update.
[Nexus 6  Original Android Development] Lancez:
10-4
[Nexus 6  Original Android Development] biglilsteve:
Not seeing that on my end. Running the latest 1-29 build of pure nexus and all is well. Just a few hours ago I used Ampere to measure charge @ 5% and it was at 2350mA. With the turbo charger.

My Tylt Vu produces 700mA through my case, so that is wild that you only get 700 from the wall charger.

What kernel were you running prior to flashing this?
[Nexus 6  Original Android Development] nixie2121:
[MENTION=4684315]flar2[/MENTION] just wanted to say I love your work. I jumped around a lot, but have been using your kernel for a few months now. the addition of the color profiles in aroma is just awesome (which do you prefer?) you answer questions nicely and quickly. just a class act all around... THANK YOU VERY MUCH !
[Nexus 6  Original Android Development] Alxoom33:
Works on MMB29Q for me.
[Nexus 6  Original Android Development] pankozin:
Hello. Can I flash this kernel over ShamuM which comes with hells core?
[Nexus 6  Original Android Development] flar2:
Reflash the rom, then flash ElementalX
[Nexus 6  Original Android Development] pankozin:
Thanks, but

Hells core is there by default, if I reflash it would be still there

Or is there another point to reflash?
[Nexus 6  Original Android Development] nathanchance:
If you are on the kernel that comes with your ROM, you are free to flash EX.
[Nexus 6  Original Android Development] Alxoom33:
It works!
[Nexus 6  Original Android Development] jon.s.nelson:
Sorry for re-posting, but can anyone explain how to adjust global vibration strength? I can't seem to find this setting...(using kernel audiator)
[Nexus 6  Original Android Development] adm1jtg:
Ok I guess I am just an idiot but I cannot find what the speedometer and leaf icons do in the ex kernel manager. The leaf icon appears to shut off 2 cores not sure about the speedometer one. Can someone point me to docs or tell me specifically what these icons are used for please?
[Nexus 6  Original Android Development] nathanchance:
Speedometer is performance mode (ramps up quicker) and leaf is battery saver mode (shuts off two cores and limits the frequency).
[Nexus 6  Original Android Development] adm1jtg:
and how can i tell whats enabled and what isnt. Aka if I hit the speedometer how can I tell later that i had enabled performance mode. I dont see any indicator.

For example when trying to figure out what they did I hit each a number of times so no longer know what mode i am in.
[Nexus 6  Original Android Development] nathanchance:
It appears vibration is not exposed in Kernel Adiutor. May need to contact the developer but I would recommend picking up the ElementalX Kernel Manager if you want a fully compatible, high quality app (linked in my signature).

Go into the apps settings and look under the power and performance sections for the notifications.
[Nexus 6  Original Android Development] adm1jtg:
Perfect. I enabled both notifications and now all is good.
[Nexus 6  Original Android Development] jon.s.nelson:
Thanks. Do you happen to know if vibration settings are exposed in that Kernel Manager app?
[Nexus 6  Original Android Development] no.one.writeme:
Hi [MENTION=4684315]flar2[/MENTION],

Any kernel change between MMB29S and MMB29Q?

I am eager to apply the February update but without an update to EX it's no go for me.

Thanks,

Best regards.
[Nexus 6  Original Android Development] modernbummer:
Another user previously stated that it's working.
[Nexus 6  Original Android Development] nathanchance:
Absolutely, I am using reduced vibration myself.
[Nexus 6  Original Android Development] flar2:
I don't think there were any updates on the kernel front
[Nexus 6  Original Android Development] no.one.writeme:
Thank you [MENTION=4684315]flar2[/MENTION]
[Nexus 6  Original Android Development] SanJoseCA:
Screen goes dark on 3.09

Has anyone faced an issue about screen going dark and not turning on, for 3.09 build?

I have all gestures enabled. I let the screen timeout, and then try turning it on. I get heptic feedback of recognizing the gesture, but the screen stays dark. :confused:

Reboot is the only option
[Nexus 6  Original Android Development] nathanchance:
I haven't had any problems with sweep to wake. What ROM?
[Nexus 6  Original Android Development] adm1jtg:
happened to me with dt2w but so far stw working perfectly
[Nexus 6  Original Android Development] eddloschi:
Hi [MENTION=4684315]flar2[/MENTION]

I have both sweep2sleep right and left. Successfully used them since I flashed elementalx. But I ran into a problem now. After trying to use sweep2sleep left the screen froze for several seconds, then the phone rebooted. I've attached logs. Also attached aroma logs. Thanks.
[Nexus 6  Original Android Development] SanJoseCA:
Sorry.. missed that. I'm on stock 6.0.1 MMB29S. No major tweaks either.
[Nexus 6  Original Android Development] nathanchance:
When the phone rebooted, do you remember if it went to the white Google logo with the lock or the boot loading animation? Any mods like Xposed?

Hmmm I haven't had any issues with this on stock or a variety of ROMs, you may want to try a clean install but I'll let flar2 chime in.
[Nexus 6  Original Android Development] eddloschi:
Google logo. Not a soft reboot. I'm on stock mmb29s (january release). No mods. I've systemless supersu 2.67, busybox and removed some apps that I don't need from system.
[Nexus 6  Original Android Development] jee'sgalaxy:
so, just to clarify, there no way to have dt2w and sweep2sleep without root?
[Nexus 6  Original Android Development] nathanchance:
Yes.
[Nexus 6  Original Android Development] flar2:
You will have sweep2wake up without root, since ib enabled it by default in the latest version.
[Nexus 6  Original Android Development] pankozin:
Hi

Is there opportunity to add gpu governor tuning in ex app? I feel screen rotating and some other things got a bit lagish lately. If even set to performance, gpu clock isn't sticking to max speed, only sticks to it on screen event and then goes down. I feel it wasn't like this last time a checked it out, when I set to performance clock was always 600 and newer down, and ui thus was super smooth. I'm on stock rom.
[Nexus 6  Original Android Development] Woody:
Hey [MENTION=4684315]flar2[/MENTION] Forgive me if this is in the wrong thread, but I run your kernel on my N6, my whole family's N7's (4) and my wife's N5, so I have to make sure that I am reading all 3 threads. In one of them you had mentioned that you were thinking about removing Faux Sound from ElX. Do you still have plans to do this?

There are quite a few people who run your kernel in parallel with various sound mods. There have been reports of popping and cracking in the Interactive and ElementalX governors and with a switch to On-Demand they are gone. I had asked you about this a long time ago (if there was any tweaks you did to ramping up the audio portion of the kernel in Interactive) and you said that you didn't do anything to cause this. After some testing of other kernels for a bit (sorry, won't happen again :p), I think that the popping and cracking comes from Faux Sound implementation.

So when I read it in one of these 3 threads that you were thinking about removing it, I was eager to test my theory out. I also remember that you said that you don't run any sound mods on your phone, but I would suggest that you give [MENTION=4445176]guitardedhero[/MENTION]'s amalgamated sound mod ViPER|Audio || ViPER|Atmos || ViPER|DD+ 5.1 * Driver * Stock * Sony * Beats * a shot. If you want to get at me with some questions or advice on setting it up, just hit me on PM or Hangouts. I[ve been using a variant of Viper for 3-4 years now and consider myself well schooled in it's intricacies.
[Nexus 6  Original Android Development] magnamentis:
good day sir :)

if i'm not totally wrong he changed it for franco's already, let's see what he says, could well be that it's done only for some devices yet
[Nexus 6  Original Android Development] rignfool:
No faux sound on the N6
[Nexus 6  Original Android Development] magnamentis:
ok, thanks for the insight, having all those devices with same kernel easily let's one mix things up, can you tell me what he's using on the "6" ?

PS: i've sent you pm about that TiBu / root topic :)
[Nexus 6  Original Android Development] fuzz_33594:
Been using this since, I think, Note 2. Really appreciate your work. Just bought you a coke to thank you.
[Nexus 6  Original Android Development] flar2:
I changed to franco's sound mod on the Nexus 5, but it also has problems, and didn't solve the crackling problem.

I don't think the crackling problem has to do with the sound mods, because if you don't change the sound settings, it's the same as it would be with stock. I really don't know what the problem is, but I've always suspected it's either overdrive of the sound hardware or glitches due to the extra processing done by Viper. I installed viper and don't have any crackling sound.

Can you provide your exact settings that you use on Viper and the situation where the popping and cracking happens?
[Nexus 6  Original Android Development] Woody:
Absolutely. I'll zip up a package that you can test on your device and send it to you via PM. The main thing is that I only get cracking in Interactive and ElementalX governors (schedulers are negligible). Once I change it to On-Demand, the are immediately gone. Happened on Cataclysm and currently happens on DU and Pure Nexus on both my N6 and N7 (I'll ask the Mrs about her N5 tonight). Got some Mod things I am into right now, but I'll send you something this afternoon, if that's ok.
[Nexus 6  Original Android Development] flar2:
You don't need to send me the package, I managed to reproduce this on my Nexus 5. It has nothing to do with fauxsound or franco sound, it is a performance problem.

On Nexus 5, turning off mpdecision and using custom hotplugging causes it. No issue at all when mpdecision is enabled. It's probably the same thing on the Nexus 6, where I have mpdecsion disabled.

Have you tried with version 3.09? I changed it so that four cores are online during suspend by default (make sure you haven't changed that in the app or something, it used to be 2)
[Nexus 6  Original Android Development] adm1jtg:
just had a hard reboot. I want to pull kernel logs but dont remember the location of the files. I tried searching but just not finding it. can you refresh my memort on where they are? I used to pull last_kmsg but thats changed now.
[Nexus 6  Original Android Development] flar2:
/sys/fs/pstore/

Not much I can do though, I've stripped this down to be almost the same as stock. This phone seems to get a lot of watchdog bites, I think the battery current is a bit wonky because there's never kernel errors, just sudden reboots.
[Nexus 6  Original Android Development] l337lasers:
This kernel has been the absolute best on my N6's battery life! Love it
[Nexus 6  Original Android Development] adm1jtg:
logs zipped and posted. I see lots of denied errors but no idea if they are even relevant. Had just switched to ondemand as a test and io was bfq with max read ahead. Used a color profile but no other changes.

http://bit.ly/1PXKfGG

Let me know if u see anything

thanks
[Nexus 6  Original Android Development] flar2:
[MENTION=3200478]Woody[/MENTION]

I got to the bottom of the v4a issue and will fix it next release.
[Nexus 6  Original Android Development] Woody:
Thanks man. I got real busy at the end of the day yesterday and then took this morning off to spend some time at my kids' school. Appreciate your efforts.
[Nexus 6  Original Android Development] nixie2121:
Sorry, What is the issue? I have it running perfectly?

Thanks
[Nexus 6  Original Android Development] magnamentis:
just follow back the thread by clicking the arrow in the quotes and you'll come to the original post. forther the info is good enough to find everything by searching.
[Nexus 6  Original Android Development] djcsurf:
Is it possible to consider adding a choice of gestures to select from to wake the phone to camera. Its a great idea but I find when taking the phone out my pocket at times its woke to the camera already. As an example another kernel has the gesture as a circle so its unlikely you'd accidentally wake it.
[Nexus 6  Original Android Development] rignfool:
[MENTION=6842057]nathanchance[/MENTION] [MENTION=5372360]magnamentis[/MENTION]

I have an experiment for you guys to try...

And actually anyone else...

I have noticed a vast improvement in battery life on this kernel using CPU Boost...

I was wondering if either of you 2 used it or were interested in trying it out...

I'm currently using elementalx governor with input Boost at 960 for 1500 milliseconds...

The big improvement I noticed is in the fact that most touch tasks get done within the allotted boost time... And the CPU does not scale up wildly like it does without boost enabled
[Nexus 6  Original Android Development] flar2:
I was able to reproduce the distortion very easily on my Nexus 5, but I can't reproduce on the Nexus 6. Is there some specific scenario where this happens?

I have pretty much every effect in V4A enabled and it's been playing smooth with no glitches for over an hour.
[Nexus 6  Original Android Development] magnamentis:
great you bring it up, below (shot) find my setup. since i'm already getting more than 8h SOT on wifi and 2G (via tasker wifi=2G) playing klondike and emailing a bit receiving eventual messages and calls, hence nothing extreme but still, full brightness and 5 Gmail and 3 IMAP accounts full sync. it will be hard to test the difference between my 1497MHz/1200ms and your 960MHz/1500ms setup. if you think it's worth it, ill still take the path but have to wait till monday when i'll visit the specific place where i usually perform those tests, would prefer to use same spot, same wifi and all.
[Nexus 6  Original Android Development] pankozin:
Hello. Can someone clear me what is "boost milliseconds" in kernel manager and why changing it doesn't affect nothing compared to "input boost milliseconds")
[Nexus 6  Original Android Development] biglilsteve:
I had an extremely tough time trying to replicate Cat smart radio using tasker but it seems like you have figured it out? Might you be able to share how you did it? Its one of the main things I miss about that ROM.
[Nexus 6  Original Android Development] pankozin:
And what does "boost milliseconds" do? Coz i feel it changes nothing... (
[Nexus 6  Original Android Development] blanco2701:
A couple of questions...

1 - What governor?

2 - This are the only tweaks you do In the kernel manager? I barely get to 4hrs sot sometimes, most of the day connected to Wifi. I know usage varies a lot perhaps but the difference is too much.

Thanks!
[Nexus 6  Original Android Development] magnamentis:
1 - elementalX governor _ deadline scheduler _ 2048 readahead buffer _ 10mA overvolt _ GPU governor = performance ( those matter if at all )

2 - kernel impact is 10% max while with this setup certainly less _ check per app usage with minimum 2 complementary monitoring apps

.....and probably most important, check your radio settings, LTE with bad signal uses doulbe than 2G with good signal. if you have bad cell

.....coverage use tasker to auto switch, dependent on use case

3 - use a dark theme on amoled devices ( blackest possible ) because that makes a huge difference whether you power 10% of pixels or 90% with white themes

there is more to it but try that first and let's go from there later after some improvement (hopefully)
[Nexus 6  Original Android Development] blanco2701:
Sorry to keep asking, but what's the gain of the overvolt and keeping the GPU governor on performance... My logic tells me that it goes against the SOT. Where am I wrong?
[Nexus 6  Original Android Development] magnamentis:
the gain is that i have no more random reboots now while they were due to special tasks on plug/unplug and have nothing to do with normal usage.

i set tasker to do a few things for me which i want (my choice) and the device obviously needed a bit more juice to perform without hickups.

further if voltage is set very tight in relation to you PSV/ASV level ( CPU ) it's possible that one can get certain tasks done a bit quicker and ramp up less, hence as counter intuitive it may sound, in special cases one might save battery like that.

all this is why it's so difficult to compare SOT, what you can and should compare is idle drain in airplane mode that's how one can easily map out misbehaving apps and components and troubleshoot them. SOT is prone to too many variables while i agree that around 4h on this device is

not acceptable. but even then it would probably be easier to find the culpit by performing idle test (no usage) and see what drains (if anything)

because if you have good idle drain and bad SOT (which i doubt) there only remain radios and display, always considering that you don't play the most heavy games and then complain about 4h because in that case it would be normal or even good LOL
[Nexus 6  Original Android Development] derdjango:
I'm gonna play around this weekend with my settings, because I'm one of those who rarely see a SOT of over 4:15 hours and a pretty high idle drain. Ran BBS last night for 10 hours and lost 20% although being in deep sleep for 98.3%. I did see a good performance boost by trying out your input boost settings.
[Nexus 6  Original Android Development] magnamentis:
those stats look in generel quite well, hence check your wifi network before next test, (forget network and re-add it)

further check interfering networks, change channels or even better bands, especially if you're on 5GHz in another room than the router

only thing is see (but others can read text logs better, i only use visual LOL) is that sensors, if it's the dt2w sensor it would be ok but dunno which, hence question mark without jumping to conclusions.

EDIT: @ derdjango further i recommend WLD app in combination with greenify. from within that app you can directly greenify top consumers (apps only) but be careful with greenify, some features are not recommended with marshmallow, use the minimum only and go from there once all goes well.
[Nexus 6  Original Android Development] derdjango:
Thanks for your suggestions. I live in a student dorm at the time and the wifi ist quite fast but I obviously don't have control over it. I did a speed test and found out that switching the settings to using 2.4GHz only is a little faster. Might be more battery friendly, too. I'll find out this night.

I was also aware of the sensors, I have sweep2wake enabled in all direction + the camera gesture. No double2towake Don't think that it has much impact on the battery.

I'll check out the WLD app, thanks. I use greenify with auto-hibernation and shallow hibernation, no aggressive doze.
[Nexus 6  Original Android Development] magnamentis:
there are sensors which have to be on and i assume it's only those, only thing is i dunno, hence mentioned it. certainly you need the

touch sensors and the sensors that sense movements for doze to work. just narrow things downs as you already are in the process.

if the wifi does not produce positive results, try airplane mode just for one night, because there are indeed a few roms that have issues

with a wifi wakelock, not saying that this one has, at least i don't and test every night.
[Nexus 6  Original Android Development] rignfool:
Are you on a public router... With lots of other users on at the same time in your dorm?

If so... You're probably getting removed from the network while you are idle... And then jumping back on... Would explain a lot of screen off drain...

Try this...

Settings... WiFi... Menu... Advanced... Keep WiFi on...

Set it to 'Only while plugged in'
[Nexus 6  Original Android Development] derdjango:
Yes, there are a lot of other users but each floor has two routers and I don't think that I get kicked out of the wifi at least I never saw it when turning on the screen. I'm not sure if I'd want my wifi off when not charging since I have to keep an eye on my data consumption but I'll try it. Good to have a weekend of to test everything, I just need to be comfortable leaving the house in the morning without worrying about my battery. Thanks!
[Nexus 6  Original Android Development] rignfool:
You must be using WhatsApp or viber or something.... Because if you are using a lot of data with the screen off... That would be your issue...

If the messages aren't super important... You can restrict background data?
[Nexus 6  Original Android Development] Circaflex:
What recovery are you using? TWRP can flash .IMG files natively, or you can use a free program from market called Flashify that can flash boot.img files for you
[Nexus 6  Original Android Development] paychex:
http://xdaforums.com/nexus-6/development/disable-forced-encryption-gain-root-t2946715
[Nexus 6  Original Android Development] feedhead:
I'm familar with that thread . If ElementalX remains set to forceencrypt how would that thread help? Set to encryptable and you desired encryption it could be easily done in sysyem security after boot. A win win for all.

I am a fan of flar2's awesome kernel and will love to use it but thus far I find unencrypted to perform better and I do not feel the need for this layer of security.
[Nexus 6  Original Android Development] flar2:
I started adding some features, lots more to come. Let's test these out for now.

forceencrypt is gone, you can safely flash whether you are encrypted or not.

I will add full compatibility with the ElementalX app next update. For now, you will have to manually enable things.

All the gestures are disabled by default.

Sweep2wake:

disable = 0

sweep right = 1

sweep left = 2

sweep up = 4

sweep down = 8

Add them together. For example, to enable sweep2wake in every direction:

echo 15 > /sys/android_touch/sweep2wake

Sweep2sleep:

disable = 0

sweep right = 1

sweep left = 2

sweep left or right = 3

eg: enable sweep2sleep left

echo 2 > /sys/android_touch/sweep2sleep

Doubletap2wake:

enable = 1

disable = 0

eg: enable doubletap2wake:

echo 1 > /sys/android_touch/doubletap2wake

Still no installer, reboot to bootloader and flash with fastboot.

Download:

ElementalX-N6-0.02 alpha

Changes:

-do not force encryption

-add sweep2sleep

-add sweep2wake

-make doubletap2wake compatible with standard apps

-overclock CPU to 2.9GHz

-user voltage control

-NTFS r/w support

-exFAT support
[Nexus 6  Original Android Development] flar2:
Just noticed I broke my sweep2sleep code trying to clean it up. It's supposed to be restricted to the area of the navigation buttons, but works all over the screen. If you enable it, you'll be turning your screen off accidentally a lot!