yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Smallsmx3:
[MENTION=4684315]flar2[/MENTION] just bought your app... Just came back to trying your kernel. Going to use elementalx gov to see if I have any reboots. Is there any way to add manual input for color calibration? The sliders are nice but can be difficult to get exact numbers... At least it is for me
[Nexus 6  Original Android Development] colinmcg71:
2h43m SOT, 75% remaining, .16 consumed only half the battery lollipop expected. http://i40.photobucket.com/albums/e...creenshot_2015-01-04-19-11-43_zpsk1wkeawg.png
[Nexus 6  Original Android Development] cobyman7035:
What app is that

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] paychex:
The battery menu in settings
[Nexus 6  Original Android Development] colinmcg71:
It's not an app, it's just the total expected battery consumption versus actual consumption since I unplugged from the charger.
[Nexus 6  Original Android Development] DroidIt!:
[emoji53] And I just spent 3 hours the other day researching light flow and how to get it to work properly...and it didn't. This is MUCH better, thanks a million flar [emoji16]
[Nexus 6  Original Android Development] TheEmpyre:
Just purchased the elemental app, glad to support your kernel been using it since HTC One X! Wanted to ask which specifically will trigger the LED for messages? I have been using Light-Flow and it no longer works after I switched from the stock kernel :(
[Nexus 6  Original Android Development] Circaflex:
Light flow works with elemental uninstall and reinstall light flow
[Nexus 6  Original Android Development] michmeister:
Don't have to uninstall. Just clear light flow cache in settings. Then set up light flow. Works perfect with this kernel.
[Nexus 6  Original Android Development] carlz28:
What are you tapping to get that page? Can't find that menu anywhere.
[Nexus 6  Original Android Development] colinmcg71:
It was at the bottom of the list under the battery graph. It's gone now though. I hadn't seen it since the developer preview days, took a screenshot for that reason.
[Nexus 6  Original Android Development] TheEmpyre:
Thanks for this! Thought it was broken after switching kernel. Phew!
[Nexus 6  Original Android Development] DroidIt!:
Light flow worked for me kind of. Started fresh with it and followed a couple of thread's tutorials and whenever I tried mixer, my light would never light up. Only when I had mixer unchecked.

---------- Post added at 05:38 PM ---------- Previous post was at 05:34 PM ----------

Actually a question. The rest are kind of self explanatory, but under led controls what are rfkill and mmc?
[Nexus 6  Original Android Development] D-m-x:
I asked myself the same thing, I'm guessing WiFi, Bluetooth and LTE http://linux.die.net/man/1/rfkill

mmc, maybe if something is written on the SD Card, like on your PC the HD LED.

Other than that i have no clue what and when max170xx_battery-online or Backlight does/works.
[Nexus 6  Original Android Development] enzoevo:
Just installed the kernel for the first time. Bought the app as well.

Does this kernel do hotplugging or something similar with mpdecision disabled?

What is cpu boost, should I enable it, and are default settings sufficient?

Sorry for all the questions, but I've heard good things and want to make the most of this kernel.

Thanks.

Via my CleanROM Nexus 6
[Nexus 6  Original Android Development] flar2:
I have no idea what those things do either, they are just the available options. The mmc one definitely acts like the disk light on a desktop system. The main ones of interest are the charging ones. You'll still need lightflow or something if you want to set up notifications, as this is beyond the scope of the app. And yes, that setting doesn't stick on boot, will have to fix it.

Stick with the default CPU and GPU settings for now. You can experiment after you get a feel for things. Some of the settings, such as the color, sound or wake options, are totally safe to play with.
[Nexus 6  Original Android Development] dsmitty166:
What are you thoughts on adding color option as well to the led
[Nexus 6  Original Android Development] flar2:
Possibly. I don't really know how it works. I would have to look at the code.
[Nexus 6  Original Android Development] dsmitty166:
Sweet thanks man love the app.

I know trickster let's me set colors. I like a blue charging, but it doesn't stick on reboot
[Nexus 6  Original Android Development] cobyman7035:
I cudnt get light flow to work on elementalx… tried uninstall wipe cache app.. Went with trickster mod

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] suku_patel_22:
Withe every new kernel, you need to setup lightflow again. Clear its data, and setup from scratch. Restoring titanium backup or other backup wont work.
[Nexus 6  Original Android Development] pr0cl1v1ty:
The only other thing possible I would love from this is the LED control for notifications and such... as I have so many issues with the other applications like lightflow.
[Nexus 6  Original Android Development] flar2:
I don't want the EX app to get that deeply into the system. Best to use a dedicated app for that.
[Nexus 6  Original Android Development] Drefsab:
just out of interest from the way I understand it if an app can turn the light on and off it it not possible to have an optional kernel module that hooks to the normal notification call's and then redirects them to method for turning the LEDs on and off? I'm not asking for this to be done but just trying to understand the difference to an app turning it on and off and it being baked in at a lower level?
[Nexus 6  Original Android Development] drawde40599:
Those are all "issues" of the app not the kernel , led dose 3 colors with 2 LED's , when you start messing with them things get weird , its best just to set it up like that Dev said and leave it alone . Light flow works on 100 different devices of all brands going back 4-5 years , those settings are for a different phone .
[Nexus 6  Original Android Development] flyinj54:
In regards to my previous post regarding having an issue with my device having a screen of death using this kernel this has nothing to do with this kernel whatsoever. The device had actually shut itself off and while using the completely stock 5.0.1 Rom I had the same exact occurrence. Doing more research I have found that this is a common problem with Nexus 6 devices and found a google thread regarding this problem. Google has also commented that they are looking into these occurrences. I hope this is not a hardware issue. Here is the thread. With that being it seems that people are having success running aosp 5.0.2 Roms with custom kernels and having the problem go away. So I'm not sure it has something to do with stock 5.0.1 at the rom level or kernel level. Something in newer code has fixed the issue apparently that you find in 5.0.2 aosp roms or possibly updates on the kernel. I'm going to continue to experiment and see if aosp 5.0.2 with stock kernel has the same occurrence.

https://productforums.google.com/fo...c/nexus/other-discussions/nexus-6/9aVUBrwdUZU
[Nexus 6  Original Android Development] Lancez:
I've had similar problem running stock with EX, but it was 0.13. anyway, I've been running pure shamu b.3.9.2 with EX 0.16 since it's out, no reboots or SOD.
[Nexus 6  Original Android Development] pr0cl1v1ty:
Same, Never ran into any issues with both of these.
[Nexus 6  Original Android Development] flyinj54:
Yea I'm thinking it is possibly the memory leak Google has spoke about in 5.0.1? Not sure exactly but if it's on the software side that's great news. Not real interested in dealing with Motorola on warranty for phone unless I absolutely have too. I don't see a lot of people mentioning this issue though so I'm surprised a lot of others running stock rom aren't experiencing this. Don't get me wrong when you search XDA you do see a thread of two on it but you would think it would be everyone. That's what concerned me about thinking hardware.
[Nexus 6  Original Android Development] n80k:
As a side note, the reboot I reported a couple days ago keeps happening to my wife. I gave her my old 32gb N6 phone and it keeps rebooting--most notably within seconds of unlocking the phone. My 64gb N6 I got last week has been running perfectly and both phones are on the same settings. I had several reboots on the 32gb when I had it but figured it might have had something to do with my settings but before I gave it back to her I set everything to stock (with exception of root and elementalx stock settings kernel) and she's still having issues. With my new 64gb I haven't had a single reboot and that's with trying out all sorts of exotic settings. Just throwing it out there
[Nexus 6  Original Android Development] flyinj54:
Well that makes me think its hardware again lol.
[Nexus 6  Original Android Development] erraggy:
My favorite part of your post: "my old 32gb N6"

[emoji1]
[Nexus 6  Original Android Development] n80k:
Lol.. I dont know what to think. I just flashed the stock kernel a few mins ago to rule that out. We'll see what happens. Only things left to rule out is root and an unlocked bootloader. Im just trying to eliminate one thing at a time to see if by some crazy chance reverting any one of those things fixes it.

It definitely felt weird to say that lol
[Nexus 6  Original Android Development] flyinj54:
Ok are you running stock rom as well 5.0.1? Please continue to run this for a few days and keep me updated on the status. I need to know if I should RMA this phone and request a replacement. I don't want to be stuck with something with bad hardware. I am running the white 32 gigabyte version.
[Nexus 6  Original Android Development] n80k:
Midnight blue Stock ROM 5.0.1. Here's my hardware info fwiw
[Nexus 6  Original Android Development] flyinj54:
Okay so this is the device that had the reboot issues? Mine is actually sandisk first and then Samsung
[Nexus 6  Original Android Development] n80k:
Yep that's the one
[Nexus 6  Original Android Development] flyinj54:
Ok keep me updated on your device with stock rom and stock kernel. My specific problem was trying to unlock the device the device would be off and I would have to hold the power button to start the device. I never had any restarts just the device with power down. I haven't had any problems today but I am running a 5.0.2 pure ROM and elemental x kernel. I was running the elementalx kernel but I was running stock rom with these issues. Also I was running stock rom with stock kernel with the same issue as well. I'm still questioning if its a stock 5.0.1 ROM problem as a few others had stated after running a custom AOSP 5.0.2 ROM they haven't had the problem since. Now i didn't ask them about exactly what version of phone (memory) and hardware they had
[Nexus 6  Original Android Development] jtwlbz:
I highly doubt that your reboot is related to mfr of the memory...
[Nexus 6  Original Android Development] n80k:
I had a couple of SODs but im pretty sure i was experimenting with overclocking at the time. I'll report back if theres another issue
[Nexus 6  Original Android Development] flyinj54:
Sounds good I'll keep an eye out for your updates on this. Like I said only running stock ROM and flar or stock kernel is all I tried with stock both with same shutting down phone result.
[Nexus 6  Original Android Development] Simer03:
Great kernel! Thanks!
[Nexus 6  Original Android Development] flar2:
Update!!!

More experimentation, trying to smooth things out a bit by ensuring cpu boost is enabled and adding some CAF updates to interactive. Also increased the cache freq and bandwidth for touchboost freq. More tuning to come, I'm still getting used to interactive. This one is built with Linaro (for real).

Download:

ElementalX-N6-0.17 (beta)

Changes:

-various tweaks and optimizations (mostly CAF)

-interactive update and tuneup

-ensure cpu-boost is enabled

-increase cache freq and bandwidth for boost freq

-built with linaro 4.9.1 toolchain
[Nexus 6  Original Android Development] crashercarlton:
I must not use battery stats right, i can't ever seem to get it working to show anything so i switched to GSAM with root companion installed.
[Nexus 6  Original Android Development] BRKotucs:
Awesome!! I appreciate the hard work..
[Nexus 6  Original Android Development] slickie88:
Are you recommending interactive or elementalX governor? I know you switched focus to interactive a build or two back, but can't recall if there was a specific reason to move away from X.
[Nexus 6  Original Android Development] flar2:
Interactive is default and recommended. Although some people get very good results with elementalx, I can't recommend it because of the risk of SOD.
[Nexus 6  Original Android Development] Damon13:
Thanks flare, Do I need to wipe cache before installing yours? I am currently on FK. Will your app provide updates to your new Kernels?
[Nexus 6  Original Android Development] elite_gamer04:
Wonderful news :D.

Out of interest have you had a chance to remove the need to have S2W for your custom DT2W or can we just use DT2W and have it replace stock?
[Nexus 6  Original Android Development] Damon13:
Oh I forgot, Can i just install and let it be? i prefer not to mess around
[Nexus 6  Original Android Development] Lancez:
no and yes

---------- Post added at 10:20 PM ---------- Previous post was at 10:20 PM ----------

yes
[Nexus 6  Original Android Development] paychex:
Try the beta one. Its updated for lollipop
[Nexus 6  Original Android Development] D-m-x:
I meant to ask this too, the Custom DT2W is way better.
[Nexus 6  Original Android Development] IcipherPT:
Voltage is locked? I can't set above 1200mv
[Nexus 6  Original Android Development] cobyman7035:
Might want to black out ur serial number ?

Via my NeXus™ 7FHD on XDA Premium app

---------- Post added at 07:38 AM ---------- Previous post was at 07:37 AM ----------

Try using the xda version of bbs app… google link

Via my NeXus™ 7FHD on XDA Premium app
[Nexus 6  Original Android Development] pinoyflayv:
DT2W and SW2S Battery usage?

If I were to enable them through your kernel settings, do they eat a lot of battery usage? What's the difference between your DT2W and the PlayStore APP?
[Nexus 6  Original Android Development] DroidIt!:
1200? My top end is 915. Somebody you don't like and you're trying to electrocute them? [emoji14]
[Nexus 6  Original Android Development] IcipherPT:
Somebody would be 3033Mhz of my 805 snapdragon :silly:
[Nexus 6  Original Android Development] jtwlbz:
just a quick update. I've never experienced my phone died during charging with .16 and .17. Everything looks good so far.
[Nexus 6  Original Android Development] TyroneLT:
SOD issues aside (since I haven't had any SOD issues with ElementalX) would you say on average the ElementalX governor is better on battery than Interactive?
[Nexus 6  Original Android Development] flar2:
No, I left it because some people want the stock dt2w. If you want to use custom dt2w, just enable s2w. You could just enable it in one direction.

Personally I always use swipe up to turn on the phone. Dt2w is way too much effort, having to lift my finger all the way off the screen ;)

I should raise it to 1225, as that is the voltage I gave to 3033 on PVS 0. But I wouldn't recommend setting it that high. The highest voltage on the worst PVS in stock is 1150. There is really not much headroom for overclocking on this chip.

I reimplemented dt2w in order to have it at the same time as s2w. It's more sensitive. The battery consumption is about 0.1% to 0.2% per hour while the screen is off (essentially negligible)
[Nexus 6  Original Android Development] IcipherPT:
Maybe i'm doing something wrong...I'm trying 3033@max_voltage but with ondemand governor. maybe thats my problem (btw, i have a qcom,speed2-pvs12-bin-v1)
[Nexus 6  Original Android Development] pinoyflayv:
Loving this infos and updates!

Again, thanks Aaron! You are a Rockstar! Love this new update!
[Nexus 6  Original Android Development] flar2:
Not many can run at 3033 no matter how much voltage you give it. If you really want to do this for benchmarking or something, put it in a ziplock baggie and then into the freezer.
[Nexus 6  Original Android Development] IcipherPT:
Yes, is only for benchmark, don't need it for 24/7! i did that but my shamu reboot at 33% of antutu :p

What app do you advice to read temps?
[Nexus 6  Original Android Development] Skripka:
Further odds are high that running 3033 will wear down the chip a great deal faster. Over in Sensei kernel's thread one guy reported that after running an overclocked kernel for a month his CPU quit wanting to run the OC'd frequencies.
[Nexus 6  Original Android Development] n80k:
Just did. Why does that matter?

---------- Post added at 01:12 PM ---------- Previous post was at 01:02 PM ----------

So confused... I thought PVS 0 was the lowest number and the "worst" PVS capable of the least overclocking (at least at boot)?
[Nexus 6  Original Android Development] old_fart:
For me, I've had this problem also. . And again, for me, it was some data corruption or ***** of a glitch that will stay there until you : factory reset / wipe data, system, cache / reload from internal storage : rom, gApps, kernel, supersu . . . . TiB is my best'est friend !

Um - Its happened three times and I have had to do the fix three times . . . I'm guessing it is tied to DIRTY updates, but I can't be sure.
[Nexus 6  Original Android Development] D-m-x:
I'm not sure but I have the feeling 0.17 actually is a little bit cooler during charging with the Turbo Charger. ElementalX App says about 34 - 35 °C while previous Versions had 38 - 40°C for me.
[Nexus 6  Original Android Development] jpd_:
Thank you for the great Kernel. I purchased the app to support development. :good:
[Nexus 6  Original Android Development] flyinj54:
There's no doubt about it this kernel is absolutely solid. Highly recommended. Great job flar thanks for the device support
[Nexus 6  Original Android Development] Nucleonic:
[MENTION=298610]Flar[/MENTION]

Great work on this kernel. Your choice of beverage on me!!
[Nexus 6  Original Android Development] TEW999:
I have a question about my stock voltage table and my PVS bin. Basically looking in my kmesg I find that my CPU has a speed bin of 2, a PVS bin of 4 and an SVS PVS of 13. Now what's weird are my actual stock voltages. At 300mhz it sits at 680mv which suggests I'm running a PVS 13 table however the higher frequencies from 1267mhz upwards relate to a PVS table of 4. At 2647mhz I'm pulling 1110mv so I'm not sure what PVS my phone is and what voltages are right. As the stock non modified voltage table my nexus has falls into 2 different voltage tables looking at the source code. There isn't a voltage table for the voltages I'm getting as stock. I'm running stock rooted with the latest elementalx kernel
[Nexus 6  Original Android Development] flar2:
Update!!!

Only one small change: added vibration strength control

/sys/drv2605/rtp_strength

Takes values from 0 to 100

I will update the app to adjust it soon.

Download:

ElementalX-N6-0.18 (beta)

Changes:

-add vibration strength control
[Nexus 6  Original Android Development] eeliah:
Is people running with this in cm nigthlys already? Or is this even compatible with CM? :) Tried to search but no go.
[Nexus 6  Original Android Development] jtwlbz:
Hmm weird that the strength is set to 127 on liquid rom
[Nexus 6  Original Android Development] flyinj54:
I am working fine
[Nexus 6  Original Android Development] flar2:
Update!!!

Wow! already a new update.

I had to change one small thing in the vibration control, so it would show 0-100 instead of 27-127

Download:

ElementalX-N6-0.19 (beta)

Changes:

-adjust vibration strength control
[Nexus 6  Original Android Development] flar2:
I shouldn't rush to do things before bed. fixed in 0.19
[Nexus 6  Original Android Development] stumpy352:
For some reason, I cannot find where to adjust vibration in the app. I enabled it in aroma. What am I missing?
[Nexus 6  Original Android Development] Lancez:
U DA MAN!!!
[Nexus 6  Original Android Development] flar2:
Wait for the next app update, it's not there yet. It will be on the Miscellaneous page. I just pushed the app update, it'll hit the Play Store servers within the next few hours.

The existing vibration setting in aroma is for s2w and dt2w haptic feedback.
[Nexus 6  Original Android Development] DroidIt!:
Flashed .19 and all working good here on EleX gov w/gestures disabled on Slim .91/5.0.2 ROM. So the vibration strength control will come in your next app update then?
[Nexus 6  Original Android Development] flar2:
I still have to fix one more thing in the vibration code. I thought the lowest setting disabled vibration completely, but it doesn't. It's not a huge deal so I'll just wait until the next kernel update.
[Nexus 6  Original Android Development] flar2:
Yes, I've already pushed it to the play store, but it takes at least an hour to show up. You can adjust manually for now

For example:

echo 50 > /sys/drv2605/rtp_strength
[Nexus 6  Original Android Development] DroidIt!:
What! You mean you don't want to push a .20 update tonight? Slacker [emoji14] Really thanks for everything there flar, everything running great so far [emoji106]
[Nexus 6  Original Android Development] chipstien:
Can someone tell me which setting to change to shorten the duration of the touch boost? Running 19 with all stock except dt2w and sweep up enabled and fiops and 1024 read ahead. Have max CPU set at 1297 and when ever I touch the screen it pins 2 cores at 1297 for quite some time. (I have CPU boost disabled). Thanks.
[Nexus 6  Original Android Development] binqker:
Bought the app for my bday present! yeee.
[Nexus 6  Original Android Development] kornklown69:
[MENTION=4684315]flar2[/MENTION] think u can add in whatever it is cm12 requires for the built in root? built in root just looks better to me than using supersu and unless you are using the new stock kernel you lose it when you flash ElementalX
[Nexus 6  Original Android Development] paychex:
SuperSu is the universally preferred root tool
[Nexus 6  Original Android Development] monkboy24:
Flar I'm loving your app bro. Its incredible!!!
[Nexus 6  Original Android Development] kossiewossie:
Brilliant kernel, loving the app for the kernel too! great work! thanks
[Nexus 6  Original Android Development] Megaflop666:
Still having the same issue on Resurrection Remix build with this kernel. I ran a logcat during boot, i'll PM you link as it's to big to upload to here.

It gets through "Android is upgrading" apps and then goes into a boot loop.
[Nexus 6  Original Android Development] JasonJoel:
'Universal' except all CM12 builds moving forward... Which means it isn't universal, and thus the request.

No need to dump on others requests.
[Nexus 6  Original Android Development] flar2:
Not sure what the problem is

I may have to start using the existing ramdisk again

Thanks and Happy birthday!

It's either on or off. I recommend leaving it for now.

Remove the powerhal file or disable mpdecision to remove it.
[Nexus 6  Original Android Development] chipstien:
OK I was wondering if if was coded into mpdecision. Speaking of which on your Nexus 5 kernel, I can't remember if you had modified mpdecision or swapped it for another hot plugging software altogether, but did you have plans to tinker with mpdecision at all in the upcoming future? Really enjoying your kernel and app.... Thanks.

PS... If I decide to remove the Powerhal file, where is it located?
[Nexus 6  Original Android Development] flar2:
/system/lib/hw/power.shamu.so

Not 100% sure what happens when you remove it. So just rename it in case you want to revert.

I'm still not sure what the kernel will look like in the end.
[Nexus 6  Original Android Development] franciscofranco:
It's not a good idea to remove the Hal. It has some power hints for encoding, decoding etc.
[Nexus 6  Original Android Development] Megaflop666:
Did you get the log I pulled? I started an adb logcat after the boot loop started and let it run for a minute.
[Nexus 6  Original Android Development] chipstien:
OK. I'll leave well enough alone then. As it is I have 60% battery after streaming Spotify all day. Thanks.