yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] magnamentis:
i sent you pm but think it's worth to post my find here as well for anyone who might be interested :)

i went through the process and flashed the stock kernel and measured the vibration level of stock google as well as default EX and they were both identical, at least as far as it's measurable with a non-laboratory level measurement tool :) hence: stock google = EX default, whatever the percentage is calles or set to.
[Nexus 6  Original Android Development] rignfool:
Interesting...

I would love for [MENTION=4684315]flar2[/MENTION] to weigh in on this
[Nexus 6  Original Android Development] magnamentis:
me too to be honest :) i remember that i once have been reading about 75% as the upper threshold above which a vibration engine would take damage in the long run, hence i was a bit suspicious that an OEM would set 100% as default but then again, let's see what flar2 has to say, i think that will settle the matter for a long time :) one way or the other LOL, thanks however for the contribution which will help to ultimately find the truth. :good:
[Nexus 6  Original Android Development] chrisram88:
So I just had a random hard reboot. I tried to save the logs from within the app but it said logs were not available. After reboot this is what happened to my battery. Any ideas why? Was at roughly 50 something percent. Running PN with stock EX settings. Only have 40% vibrate override.
[Nexus 6  Original Android Development] TransportedMan:
Will lowering the highest clock rate of the cores improve battery life? Or rather, in aroma setup if I lower the CPU highest speed will battery life see a difference? I was thinking about taking it down to 2572mhz but the difference between that and 2726mhz seem negligible and I would be just taking away performance for almost no increase in battery life.
[Nexus 6  Original Android Development] nathanchance:
I've tried underclocking and it really does not make much of a difference unless you do it significantly but then as you say you are hampering performance.
[Nexus 6  Original Android Development] Djfrost:
Not much you can really do about battery life on the Nexus 6. It's already great with this kernel. Under clocking just destroys the performance and marshmallow experience... IMO just have to manage you usage
[Nexus 6  Original Android Development] suku_patel_22:
Underclock? I've over clocked it to 2803. [emoji2]

There is hardly any impact on battery life.
[Nexus 6  Original Android Development] blanco2701:
What about the impact on performance? is it worth it to overclock?
[Nexus 6  Original Android Development] rignfool:
Over clocking on elementalx or interactive governor has almost no impact on performance or battery...

It rarely uses frequencies over 2 ghz...

However... If you run on demand... You'll notice a difference in both battery and performance
[Nexus 6  Original Android Development] Droidphilev:
Regarding OC'ing: i never got it to work with ElementalX. If i enable a higher speed in the aroma installer my device freezes at boot. Other kernels/apps set the OC speed a bit after boot while EX uses this speed right when booting. Would love to find a way set speed when booting is done.
[Nexus 6  Original Android Development] apophis9283:
Whats your bin. The higher the bin the crappier the chip. Your device may not handle that on boot. Why awhile back we made it so it would boot with stock frequencies
[Nexus 6  Original Android Development] flar2:
If it can't boot at the oc frequency, then you shouldn't be overclocking, as it is clearly not stable.
[Nexus 6  Original Android Development] Alxoom33:
Use the EX Kernel Manager or Tweakeakerz App.
[Nexus 6  Original Android Development] rignfool:
[MENTION=4684315]flar2[/MENTION]

I was wondering if you could be talked into adding a light sensor toggle to either your widget or to EX Kernel Manager...

With a user adjustable threshold
[Nexus 6  Original Android Development] flar2:
For High Brightness Mode?

The HBM Widget beta has this, but the threshold is not adjustable

https://play.google.com/apps/testing/flar2.hbmwidget
[Nexus 6  Original Android Development] DroidIt!:
Hey flar. Yep been running elementalx gov on .7 for about a day or so now uc to 1.9 and UV by 25 and no problems at all so far. Installed through Aroma if that makes a difference with SlimLP. [emoji106]
[Nexus 6  Original Android Development] mk262:
When I updated to .08 I lost cellular data.
[Nexus 6  Original Android Development] flar2:
That's not due to the kernel.
[Nexus 6  Original Android Development] mk262:
I recognize it sounds weird but it's the sole change I made.
[Nexus 6  Original Android Development] letmedanz:
wifi & cellular signal is controlled by the radio.
[Nexus 6  Original Android Development] paychex:
Reboot usually fixes that on any phone. Happens occasionally when you flash a kernel. Happens sometimes on every phone I've used
[Nexus 6  Original Android Development] DroidIt!:
What carrier? I'd go double check APN's. I had some really strange behavior and didn't realize even though I'm on the same carrier as on my N5, I still needed to use a different APN on T-Mobile.
[Nexus 6  Original Android Development] Krunk83:
Got another random reboot today on .08. Stock settings.

nexus 6
[Nexus 6  Original Android Development] mk262:
tmo. apn looked correct
[Nexus 6  Original Android Development] DroidIt!:
I was seeing 3 different APN's for T-Mobile. I was using the first for my N5 but needed to switch to the .fast T-Mobile one for the N6.
[Nexus 6  Original Android Development] adio201:
Beem uaing elementalx kernel since i got my N5 and never had any roobts or problems. Now that i got my N6 i using this kernel again and it has heen good no reboots only thing is tap to wake is not working other than that all is well:D
[Nexus 6  Original Android Development] mk262:
It was on fast.
[Nexus 6  Original Android Development] slickie88:
I've been using dt2w constantly on every version released and it's always worked as expected.
[Nexus 6  Original Android Development] flar2:
It's extremely important that I get kernel logs.
[Nexus 6  Original Android Development] flar2:
If you don't have sweep2wake enabled, it uses the stock doubletap gesture, which is less reliable. That's probably why its disabled by google. The tradeoff is that sweep2wake will add 0.6% per hour drain while idle.
[Nexus 6  Original Android Development] adio201:
Any way to disable stock tap to wake and use flar kernel for tap to wake?
[Nexus 6  Original Android Development] paychex:
The options are in his app
[Nexus 6  Original Android Development] adio201:
Im using trickstermod wouldnt that option be om there also?
[Nexus 6  Original Android Development] bogus83:
flar2, is there any chance we could get an option to associate a voltage modifier with the performance and powersave modes (in the ElementalX App)? Overclocking doesn't work so well when the device is undervolted, and the battery saver mode is less efficient when the device is overvolted.
[Nexus 6  Original Android Development] celyko:
Off topic, but is there a stock unencrypted ROM file I can flash? I lost my backup of complete stock :/ . I can't seem to find it anywhere
[Nexus 6  Original Android Development] suku_patel_22:
Does it have auto on and off?
[Nexus 6  Original Android Development] nathanchance:
Oh I thought that only worked on the 6P! Sweet, I just installed it, I'll test it out on campus tomorrow.

Yes, you can toggle between manual and automatic mode by double tapping on the icon. It will show you which mode it is in (screenshots attached).
[Nexus 6  Original Android Development] Droidphilev:
Hi all,

Thanks for the answers!

Hmm, i don't even know what this "bin" is. :(
[Nexus 6  Original Android Development] nathanchance:
Probably gonna butcher this explanation a bit. Type cat /proc/cpu/msm_acpu_pvs﻿ into a terminal emulator from the Play Store. The number it returns corresponds to your bin number, which allows you to tell the stock voltages of your chip. See this list to see your stock frequencies and their corresponding voltages (the bin number is the number after the pvs).
[Nexus 6  Original Android Development] Droidphilev:
Thanks! Well... the "bin" seems to be 4. I guess it's high and therefor crap?
[Nexus 6  Original Android Development] apophis9283:
Actually bud, youre good to go. It should hang in there for oc. Its what i have and i run 35mhz to 3.09
[Nexus 6  Original Android Development] Droidphilev:
With ElementalX? I don't have the problems with other kernels either.
[Nexus 6  Original Android Development] lazer77:
I expected it to say something more than just "4" lol. I was curious and also did dmesg |grep PVS, which confirmed the "4". Thanks for the info. :highfive:
[Nexus 6  Original Android Development] Formhault:
Damage as in... rattling sound? Mine was like that from day one. I mean it is kinda loud. I've seen this across the board...

---------- Post added at 05:49 PM ---------- Previous post was at 05:46 PM ----------

PVS bin? Mine's 2. Doubt it's good, since my battery is crap :) (still haven't pinned that down, yeah)
[Nexus 6  Original Android Development] DroidIt!:
Really? My N6 has always been quiet as a mouse since day one. I have always felt it and not heard it at all. The 5x though I thought was going to knock stuff off the walls and the 6p is about halfway between my 6 and the 5x.
[Nexus 6  Original Android Development] timosuomi:
The loudness of my N6 is the one thing I hate about it. The vibration is SO loud. Changing the vibration level seems to just change the pitch, but doesn't make it any quieter. It drives me crazy! I've never had a phone vibrate this loud. Of course, it's a fairly minor complaint.
[Nexus 6  Original Android Development] magnamentis:
no, i meant damage as in "dead" LOL and mine is very intense at 45% currently :) i had to reduce it more and more to not get "rattled" haha... but seriously i'm fine with my vibes, better strong and able to reduce than the other way around and i have no rattling except if something on the table would rattle. so we agree as to very loud but i don't consider mine rattling while i believe that this is due to subjectively different registration and most probably is the same :)

just remove all your millions in coins from the desk and see if it still rattles for you ( just kidding ) ;):cool:
[Nexus 6  Original Android Development] Formhault:
No, I don't mean that kind of rattle. Compared to a Samsung device, for example, the Nexus 6 is very... audible, while the Samsung is just feely (so to say, you feel it better than hear). You know...
[Nexus 6  Original Android Development] DroidIt!:
Must be one of those cases of when it was manufactured. I got my N6 probably 4 months or so after release. Maybe Motorola did better after the first batch?
[Nexus 6  Original Android Development] :
I know flar2 posted about the option being in the beta, but not adjustable.

What I do is have tasker toggle the widget based on light value. Assuming that you use tasker, this is what you would need.

State:

Condition %LIGHT > 1500

Enter task:

Send intent flar2.hbmwidget.HBM_ON

Exit task:

Send intent flar2.hbmwidget.HBM_OFF

The 1500 seemed to be a good value for me as it only seems to trigger with my phone in direct sunlight.
[Nexus 6  Original Android Development] magnamentis:
that's the right approach IMO, just in case that someone who is less experienced with tasker, instead of using variables the light sensor is built into tasker as a state to choose in profiles, both things will have the same outcome while to use the built in sensor profile is a bit easier for less experienced users and the values go from 0 to 100% which is a bit more intuitieve. that's a yes but, the other way works great of course, hope it's welcome :angel:

EDIT: this is how i manage screen brightness dependent on light level and battery percentage, that way i can stay full bright withing certain levels :)
[Nexus 6  Original Android Development] :
The reason that i went with the variable approach over the light level state is because the variable holds the current sensor value while the light level state is a percentage of the min/max values that tasker has ever seen from the light sensor. When I originally setup the profile I apparently didn't have enough history built up for light state. I'd set a percentage that would work then an hour later it wouldn't. That value/percent for the state can also get horribly messed up if your light sensor ever glitches and spits out a max value like 99999 or something.

For me, I found the variable comparison to be a much more stable/reliable method.

Basically, the % seems like it would be more intuitive but in my testing it was anything but. The other issue with it is that the sensor doesn't seem very linear. For me, a reading of less than like 10 lux is a dim to dark room. A well lit room could get anywhere from 100-1000 or so (as read by tasker) while outside would be anywhere from 1500-2000 for direct sunlight. When you look at the way that percent works out would be the percentage from 0-2000. And since anything over 1500 was bright, it would end up being like 10% or so.... If course some people's light sensors may operate a little different.

The way I got my value s by making a scene with that variable as a text item. I think I had to have a button to update it or something though which was annoying. Then I walked around to different lighted areas to get a value that worked.

But, if it works better for you it might for other people as well. It's always nice to have options.
[Nexus 6  Original Android Development] magnamentis:
i agree with every bit of your reasons, ease of set up was my only point while all your points are more than valid when it comes to reliability and precision, appropriate skills provided. hope that did not come over in a different way, that would mean i'd have to reconsider my semantic skills LOL.

thanks for the in depth explanations, now all that matters lays on the table and everyone can choose according to his priorities. :good:
[Nexus 6  Original Android Development] athraugh:
HI,

1. I hope to flash ElementalX-N6-3.08.

2. I don't want to encryption function .

3. I am on rom of shamu-mmb29s-factory-fc7b590e.tgz now.

4. I want to stay on the stock rom and don't want flash the custom rom like chroma or pure nexus project.

Can you tell me how can I do?
[Nexus 6  Original Android Development] RandomPooka:
Yeah, do this...
[Nexus 6  Original Android Development] nathanchance:
Yeah, flash EX in TWRP and you are done. EX won't change your encryption status so if you are not currently decrypted you will need to do but if you are, you are fine.
[Nexus 6  Original Android Development] RandomPooka:
Seriously. It's one step, and it's in the OP under "Installation"
[Nexus 6  Original Android Development] athraugh:
1. I am in encryption mode now.

2. Can I flash "shamu-mmb29s-factory-fc7b590e.tgz(factory image)" by TWRP?

I need to fully wipe and decryption my device .

Can you tell me how to fully wipe on stock bootloader?

thank Nathanchance, RandomPooka reply.
[Nexus 6  Original Android Development] RandomPooka:
Start HERE at the Nexus 6 Lounge Forum. Read a lot. There are forums on XDA specifically for what you're trying to do, with links to apps like the Nexus Root Toolkit. You really do want to read as much as you can about what will happen, so you can take any precautionary steps to save your data, pictures, apps and so on before taking any action on your phone.

Being well educated on the thing you're about to do is very much worth the time it takes to do the research. There's nothing like losing the first pics of your newborn or the last pictures of a relative that passed away because you didn't back up everything first.

---------- Post added at 07:30 AM ---------- Previous post was at 07:27 AM ----------

I'm almost positive that the stock bootloader has an option to completely wipe your phone and factory reset it.

You can NOT flash a custom kernel from the stock bootloader .It has to be unlocked with 'fastboot oem unlock' and you have to flash a custom recovery like TWRP to flash a custom kernel.

^^ THAT will wipe your phone in itself, but I can not remember if it wipes the internal SDcard. I want to say it does. It probably does not decrypt your device. Can't remember.

Is there a specific reason that you need your device to be decrypted?
[Nexus 6  Original Android Development] magnamentis:
yes read the first post of this thread, it's all there. and then read the first and the last 10 pages and search if you have a specific question.

---------- Post added at 03:09 PM ---------- Previous post was at 03:04 PM ----------

to decrypt your phone it's not enough to clean flash, you will have to format you entire phone including internal strorage (sdcard) you will loose all your data, not only app data but all photos files, music, flashable zips simply everything.

it's not worth it, the later stock variants deal so good with encryption that you won't see the huge difference in performance like under 5.0.x if any at all. so leave it as it is if you ask me directly ( which you didn't ) LOL

further you have to get used to use google search and xda-search. post if you don't find the answer after reading and if you get in trouble with log and maximum information so we can help you out, but better read again and again before to avoid that of course.
[Nexus 6  Original Android Development] nathanchance:
[MENTION=4684315]flar2[/MENTION] the auto HMB with the beta widget is really nice, works well so far! Activates very quickly and in the right lighting conditions. However, as I walk around campus, there are some areas where trees intermittently block out the sun, which causes the screen to shift pretty rapidly between normal and high brightness. Not sure how easy/practical it would but it would be nice if the sensor waited a few seconds before initiating a shift to see if the threshold would be reached again within that time frame (maybe even making this customizable?). Thanks for the hard work!
[Nexus 6  Original Android Development] The Funky Pear:
Hello,im one step behind flashing this kernel.

My problem is,that,you say in OP dont flash it on top of other custom kernels..

I have a custom kernel right now,and i dont have the stock kernel.

How can i find the stock kernel?? I have not made a backup.

Also,i bought this phone yesterday.

And for last,how can i check if my device has enabled or disabled encrypt??
[Nexus 6  Original Android Development] tkalli:
Check Security in Settings.

It was say encrypted if it is.
[Nexus 6  Original Android Development] magnamentis:
dirty flash the rom you have now and the kernel thereafter while don't forget to re-root, root before installing EX else you could end with the last kernel installed. however the answer to your question is to reflash the current rom and if that is stock you can extract the boot.img from the factory image and "fastboot flash boot boot.img" or you can use twrp's included image flash tool or flashify or rashr.
[Nexus 6  Original Android Development] suku_patel_22:
Has anyone tried out https://play.google.com/store/apps/details?id=de.srlabs.snoopsnitch
[Nexus 6  Original Android Development] rignfool:
[MENTION=4684315]flar2[/MENTION]

Could you please make sample_rate_min a user tunable node in the next release...

I am experimenting with polling and trying to slow frequency switching and see if that has a positive impact on battery for me...

Thanks
[Nexus 6  Original Android Development] flar2:
Sampling rate min doesn't matter, only sampling_rate is important
[Nexus 6  Original Android Development] modernbummer:
Pretty quiet in this forum. Probably because your kernel is stable as hell ?
[Nexus 6  Original Android Development] nathanchance:
That is the unfortunate part of something working so well lol.
[Nexus 6  Original Android Development] jpeckinp:
Not sure if this is kernel related or my charger.

Since 3.08 was released my wireless charger hasn't been charging my phone properly. The light will come on on the base and not charge or sometimes the light is on but the notification light on the phone will flash.

Just wanted to see if anybody else has noticed this.

Phone - N6

Charger - http://www.amazon.com/gp/product/B00JA7HNZO?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00

ROM - Chroma
[Nexus 6  Original Android Development] nathanchance:
I'm not having an issue with wireless charging on 3.08. Have you tried another device? Does it happen on the default kernel?
[Nexus 6  Original Android Development] flar2:
There is a bug, which I figured out today and will fix tonight or tomorrow.
[Nexus 6  Original Android Development] jpeckinp:
I do have another charger that is the same for my wifes phone, I should give that one a try first then I'll try stock kernel.
[Nexus 6  Original Android Development] Lancez:
F5'ing..... :p
[Nexus 6  Original Android Development] flar2:
Hang on, I'm not sure if I'll get to it tonight.
[Nexus 6  Original Android Development] MarkGbe:
pfft, whatever, i'll believe a bug when i see it.
[Nexus 6  Original Android Development] ren0.1:
Sorry for the n00b question: is 3.08 the ElementalX version or the underlying kernel version? The elementalx.org site doesn't make this clear, either.

Is there a changelog for the 3.x series?

Thanks!
[Nexus 6  Original Android Development] nathanchance:
3.08 is the EX version, the Linux kernel version is 3.10.40.

There is a changelog in the EX Kernel Manager when you download and flar2 posts every time there is an update but I can't locate a full 3.x one.
[Nexus 6  Original Android Development] ren0.1:
Very helpful. Thanks!
[Nexus 6  Original Android Development] suku_patel_22:
You forgot to add colors to aroma last time around. Just a gentle reminder [emoji2]
[Nexus 6  Original Android Development] Gedablo666:
Sweep2sleep (left right) not working. Its only works when you sweep to left but never to the right.
[Nexus 6  Original Android Development] xe0r:
Working fine on my side.
[Nexus 6  Original Android Development] Alxoom33:
Try reinstalling the kernel.
[Nexus 6  Original Android Development] magnamentis:
settings > apps > elementalX > storage > clear data
[Nexus 6  Original Android Development] flar2:
Check /sys/android_touch/sweep2sleep

if it says 1, then sweep right is active, 2 means sweep left, and 3 means sweep left or right.

There are launcher, app or ROM mods that can interfere with sweep2sleep. This feature can be implemented many different ways.

That shouldn't really ever be necessary. No preference is stored unless you set it on boot. The setting in the app always shows the current state of the setting, regardless of any preference that is saved.
[Nexus 6  Original Android Development] Alxoom33:
I use the EX Kernel Manager to set or change gestures.
[Nexus 6  Original Android Development] Gedablo666:
Just checked sweep2sleep I see 3, but its not working to the left. I turned off in rom settings double tap to sleep on navigation bar. Tried to turn on only sweep to right but its still not working. Works only sweep to left.
[Nexus 6  Original Android Development] JonesL:
Same problem here, with regards to sweep to sleep.
[Nexus 6  Original Android Development] flar2:
Look guys, it 100% works. I know this. Something in your setup is interfering or you are not sweeping correctly.
[Nexus 6  Original Android Development] Khizar:
I can confirm gestures works perfectly. However I did have this issue once where none of the gestures worked on a clean flash, what I did was reflash kernel and enabled the gestures, that made them work.

Edit - This was on a stock rom, so no conflicting mods.
[Nexus 6  Original Android Development] flar2:
There is a good chance that it doesn't work due to something built into the rom, an xposed module, a launcher, or some other app the does a similar thing.