yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Original Android Development] likonvampire:
Sorry [MENTION=4684315]flar2[/MENTION] to report : I did get my LTE coverage back after wiping the cache in TWRP. After the boot up i decided to do another reboot just to check and now i was back again to H/3G . I flashed the stock boot.img using fastboot and back on LTE again. I will have to flash SuperSU 2.61 again as I have lost root now.
[Nexus 6P Original Android Development] flar2:
I have 3G in my basement and LTE upstairs. It depends on reception.
[Nexus 6P Original Android Development] infamous84:
does the paid app make the vibration stonger? or is it just for turning it down?
[Nexus 6P Original Android Development] NovaSlim:
You can increase it or decrease it.
[Nexus 6P Original Android Development] joqsan:
I love this kernel but I recently switched to a Rom with it's own custom kernel. Do you guys think it will effect anything if flash this kernel over it. I just miss the color options and sound options for this kernel
[Nexus 6P Original Android Development] likonvampire:
I am in an LTE area all the time , i will see if it changes when i go home ..

Thanks for your prompt reply and awesome support as always
[Nexus 6P Original Android Development] flar2:
It should be fine, just match up the Android version (6.0 vs 6.0.1)
[Nexus 6P Original Android Development] Harry Pothead:
Stock setting for the vibration intensity in the App using ElementalX is 51%, so you can do both depending on your needs.
[Nexus 6P Original Android Development] steveo17:
question:

It seems that dt2w does not work 100% of the time. It seems that when the phone is sitting idle for a while dt2w does not work. Perhaps doze is enabled and at that point it is blocking the dt2w?
[Nexus 6P Original Android Development] thuggn16315:
Hey I know on other processors they set a53 cores at 2ghz would it be possible on this and set the a57 cores a bit higher and make a elemental x supercharged version lol
[Nexus 6P Original Android Development] elreydenj:
Unfortunately i can confirm the same. Decided to reboot once again and booted up to 3G. I am going to leave it on 3G and see if it changes as I move out of my office. I always have LTE in my office though. Toggling data fixes it but very curious as to what is up.

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

Its strange it is actually every other reboot. First boot after cache wipe is LTE and second boot is 3G. Third boot was LTE and fourth boot was 3G. Craziness!
[Nexus 6P Original Android Development] oscillik:
followed your exact steps, to the letter, on a Nexus 6P and a Nexus 5X, both running Android 6.0.1 and their appropriate ElementalX version for their hardware.

having Xposed installed, along with ElementalX 1.00 on Android 6.0.1 causes repeat "Unfortunately Nfc Service has stopped." messages.

have wasted the past 3 hours on this, trying different combinations, trying to set Selinux to Enforcing, setting to Permissive, etc etc. doesn't work.
[Nexus 6P Original Android Development] zgroten:
Was having LTE issues, all it took was leaving the house and it found a tower, then LTE was fine. Band 12 connected, even though its super slow compared to band 4.

Only problem I'm having is that Wi-Fi calling doesn't work. It's enabled in settings, but it just doesn't work.
[Nexus 6P Original Android Development] schnob:
I haven't had any service issues of any sort on Verizon, running stock 6.0.1. Flashed everything from the factory image, then SuperSU, then the kernel.
[Nexus 6P Original Android Development] steveo17:
Same here
[Nexus 6P Original Android Development] jc monkeyballs:
Make sure you've got an E-911 address listed on the T-Mobile website.
[Nexus 6P Original Android Development] kashk5:
I had the same issue with the stock kernel. It would just stay stuck on H/H+ in places where I've always gotten LTE. Then about 10-15 minutes later it just randomly connected to LTE and it's been working great ever since. However, I had no such issues when I flashed the latest radio on 6.0 yesterday.

I honestly think it has something to do with 6.0.1 and not this kernel or the radio.
[Nexus 6P Original Android Development] flar2:
The LTE thing absolutely has nothing to do with the kernel. First of all, no code that affects LTE was changed. Secondly, I rebooted like 20 times today with stock and EX and it started up with LTE almost every time. There was no correlation with the kernel I was using. Any findings that people have comparing stock vs EX are completely coincidental.
[Nexus 6P Original Android Development] zgroten:
Yes I checked it. But it was working just fine before the update, why would the e911 on T-Mobile site be it?
[Nexus 6P Original Android Development] rebretz000:
I know I'm late to the party but today I was having the LTE issue on stock kernel also. I'm not sure if perhaps it has to do with the way systemless root is or not but I've had the issue with jus the stock kernel.

Yesterday I did not. All last night and this morning I used ElementalX with no issues then I tried to flash Cataclysm but ran into issues. That's when my issues started. Not sure if it's connected to that either.
[Nexus 6P Original Android Development] infamous84:
those on verizon is Volte working for you?
[Nexus 6P Original Android Development] elreydenj:
Yes.
[Nexus 6P Original Android Development] cshuwing:
Just updated to 6.0.1, I'm yet to try 1.00 but I can definitely say LTE issue is also present in stock kernel (non rooted or rooted with supersu 2.6.1).

It seems to me the new radio is the culprit and it tends to stick with hspa instead of lte in my area (Hong Kong).
[Nexus 6P Original Android Development] c_86:
hmmm anyone using this with Cm13, the latest nightly (aka tonights)...

I just flashed this with the latest and the camera doesnt work... i did flash the 1.0 version of this kernel... thoughts?
[Nexus 6P Original Android Development] nathanchance:
Is that nightly based on 6.0 or 6.0.1? If 6.0, you need 0.11, not 1.0.
[Nexus 6P Original Android Development] c_86:
No. It's based of 6.0.1

update/edit:

it seemed to have been an issue with my device...

I just updated the vendor image, the bootloader and radio and the camera is now working fine with this kernel

didnt know about the vendor image so im guessing that did it
[Nexus 6P Original Android Development] drawde40599:
The LTE issue on 6.01 happens on 100% stock system , its been reported by many members on G+ .

---------- Post added at 08:56 PM ---------- Previous post was at 08:50 PM ----------

Android Pay works fine (paying ) with BBox installed as long as you have system-less Root 2.6*
[Nexus 6P Original Android Development] :
Can we still use supersu 2.52 with version 1.0? Half of my root apps don't work with systemless root.
[Nexus 6P Original Android Development] drothenberger:
If you manually create /system/bin/su and/or /system/xbin/su, SuperSU 2.61 will update the files with the latest binary, which should fix those apps.
[Nexus 6P Original Android Development] :
Out of thanks at the moment, but thank you.

What exactly do i need to do? Just create these files in file manager? And then what? Do I need to reflash 2.61 or how does it work?
[Nexus 6P Original Android Development] mobileman88:
What about the stock kernel? I have boot.img from Google's image. Can I just reflash this to revert to stock kernel?
[Nexus 6P Original Android Development] Wintersdark:
I haven't installed ElementalX since updating, and wanted to confirm to put people's mind at ease: I've had LTE issues since the 6.0.1 update on the stock kernel. It's a 6.0.1 problem. I'd held off installing EX again until I got it worked out.
[Nexus 6P Original Android Development] :
Been using with cm 13 batter life is amazing
[Nexus 6P Original Android Development] saturated:
Would it be possible to have an option for double tapping the display to not only unlock device but also launch camera? Thanks for this kernel.
[Nexus 6P Original Android Development] sherlock5545:
You can use flar2's Wake Gesture app to do that. You'll find the link on his signature.
[Nexus 6P Original Android Development] saturated:
thanks tried it out. I was hoping to be able to double tap to launch camera the same way double clicking the power button does. Keep phone and gallery locked but quickly snap shots.
[Nexus 6P Original Android Development] mobileman88:
Any reason you don't use your fingerprint to unlock then tap on the camera? That's the other option from double tapping power
[Nexus 6P Original Android Development] saturated:
Yah I suppose that isn't much of a complication. Just like the idea of taking advantage of the locked camera on the go, simpler, more secure if others want to use my phone for a picture, and more geared to gripping the phone in landscape out of your pocket. Without adding wear and tear to the power button too.
[Nexus 6P Original Android Development] jc monkeyballs:
If you don't have a E-911 address set, T-Mobile won't let you on their WiFi calling.

However, I checked and my WiFi calling wasn't working either. I flashed the stock boot.img and it works, but doesn't work on ElementalX 1.0 on 6.0.1.

EDIT: Just checked WiFi calling with stock boot.img and SuperSU 2.61 and WiFi calling does not work. It seems like the new experimental SuperSU breaks it.
[Nexus 6P Original Android Development] drothenberger:
I just created an empty file with Root Explorer, set its permissions to rwxr-xr-x and then rebooted. After the reboot, the file was replaced with the real su binary.

I don't know if setting the permissions was necessary.
[Nexus 6P Original Android Development] mobileman88:
Yep. That's what I am doing now. Still fairly easy. Grip phone and tap on camera icon once unlocked
[Nexus 6P Original Android Development] xyge:
Amazing performance!

Stock kernel settings with fsync off.... And debloated stock rom
[Nexus 6P Original Android Development] jc monkeyballs:
Will this still allow Android Pay to work?
[Nexus 6P Original Android Development] Badger50:
Did you just name the file Su??
[Nexus 6P Original Android Development] drothenberger:
Yes. I created /system/xbin/su as an empty file and rebooted.

---------- Post added at 06:58 AM ---------- Previous post was at 06:57 AM ----------

I doubt it. My understanding is Android Pay will not work if you've made any changes to /system.
[Nexus 6P Original Android Development] slayp00n:
Hi Flair, several people including me notice the acceleromter in the 6p is calibrated poorly / too sensitive causing the phone to goto portrait when sitting flat on a desk, very very annoying.

I tested my accelerometer and noticed when level it reports 2 - 3 degrees of role to the left.

I am wondering if at a kernal level you could:

allow us to calibrate it OR even better... allow us to set the 'goto to landscape role rate', i would love to be able to say.. if less then 25 degree role stay portrait..
[Nexus 6P Original Android Development] flar2:
Unfortunately I don't see anything in the kernel to control the sensors. The sensors seem to be handled by some system libraries.
[Nexus 6P Original Android Development] slayp00n:
That sucks, it clearly is a bug according to the response im getting on reddit. And all 3 6ps in my office experience it
[Nexus 6P Original Android Development] mobileman88:
No. Once you modify or add any files in /system it will break android pay
[Nexus 6P Original Android Development] Bwyan Benton:
I can definitely confirm this. It's annoying as hell to.
[Nexus 6P Original Android Development] slayp00n:
I made a reddit post for visibility, maybe someone can get it created on the google issue tracker

https://www.reddit.com/r/Nexus6P/comments/3w2tps/recal_the_accellerometer/
[Nexus 6P Original Android Development] flar2:
Probably have to get Google to fix it, I think those sensor libraries are closed binaries and other parts of the implementation are proabably in the firmware.
[Nexus 6P Original Android Development] zgroten:
Yes it looks that way. I've seen this happening on other devices with a modified boot.img, trying to figure out what will fix it.

I don't care about Android Pay working vs Wi-Fi calling. Can I flash the stock boot.img and the original SuperSU 2.52 Beta that was the first root method for 6.0? That isn't systemless.
[Nexus 6P Original Android Development] joho5:
Can I flash the kernel in twrp if I am not rooted, and then flash just the 2.52 supersu in twrp?

I just plan on updating my stock rom without wiping data by flashing the new radio, bootloader, and system.

that will take away my current root, which is fine, but the original post says something about having to use 2.61 or higher, which I cant even find.

I will not be pre-rooted, but will want to end up rooted after I update images.
[Nexus 6P Original Android Development] nathanchance:
Process would be: flash images with fastboot, boot into TWRP, flash SuperSU 2.61 from here,then flash EX 2.61. Make sure not to hit the install SuperSU button in TWRP when rebooting.
[Nexus 6P Original Android Development] joho5:
thanks for the response.

If i use elementalx kernel manager to bump up headphone volume or something on the system partition after this process, then I lose the ability to use android pay due to system being altered right?

Not a big deal to me, just curious.
[Nexus 6P Original Android Development] nathanchance:
I don't think so, I don't think Safety Net cares about that but I don't have a 6P so I couldn't test.
[Nexus 6P Original Android Development] flar2:
No, those settings are in /sys not /system

/sys is a virtual filesystem where all the kernel settings are
[Nexus 6P Original Android Development] zgroten:
I'm unable to create any files in /system/xbin or /system/bin

How did you do it?
[Nexus 6P Original Android Development] 3ddfknmontana:
The 1.00 only for 6.0.1?
[Nexus 6P Original Android Development] joho5:
ok...thanks.

I was under the impression that volume increases were altered under system/etc/mixer_paths.xml

thanks
[Nexus 6P Original Android Development] drothenberger:
I used Root Explorer after remounting /system as R/W (there's a button in Root Explorer to do that). Alternatively, you can run these commands from a terminal or adb:

su
mount -o remount,rw /system
touch /system/sbin/su /system/sbin/su
mount -o remount,to /system

---------- Post added at 09:24 AM ---------- Previous post was at 09:23 AM ----------

Yes.
[Nexus 6P Original Android Development] fchowd0696:
can you link me to the vendor image?
[Nexus 6P Original Android Development] flar2:
Google "Nexus factory images"

The latest are always available in a zip file, that's why we buy Nexus devices.

Just for everyone's info, if you update to 6.0.1, you should flash bootloader, vendor and radio images. If you are using stock ROM, then also flash system and boot (this is what is normally flashed with custom ROMs). The userdata and cache images aren't necessary (and the former will wipe your sdcard).
[Nexus 6P Original Android Development] c_86:
see there
[Nexus 6P Original Android Development] zgroten:
After flashing, should be reboot to recovery and flash SuperSU 2.61 or let the device reboot into Android?

Will the latter method encrypt the file system?
[Nexus 6P Original Android Development] flar2:
If you let it reboot to Android with stock kernel, it will encrypt your data. Flashing SuperSU (or EX) will prevent data from being encrypted.
[Nexus 6P Original Android Development] zgroten:
Gotcha. SuperSU OR Ex?

Meaning I don't need to flash SuperSU? Will I still have root?

I rebooted into recovery, flashed SuperSU 2.60, then went into Android. Everything seems fine except WiFi calling does not want to work. Also the phone seems to only want to connect to HSPA
[Nexus 6P Original Android Development] flar2:
You will not have root with just EX.

I don't know anything about wifi calling, but the mobile connection issue is present on stock as well.
[Nexus 6P Original Android Development] bagarwa:
I learnt that the hard way. It had totally slipped my mind and I thought the device is bootlooping when the boot animation had ran for 8+ minutes. I did a hard reboot and got the "encryption is corrupted. Must factory reset now" screen. ;'( :'( Lost everything, including sdcard content.

SuperSu roots your device. Ex is the kernel ElementalX. That also supposedly disables encryption. But I don't know whether that gives you root or not.
[Nexus 6P Original Android Development] zgroten:
Gotcha. Just trying to get WiFi calling to work. Right now I'm stock kernel with SuperSU 2.61 and it won't connect to WiFi calling. SIM status says IWAN which is WiFi calling, but the phone and notifications do not.

Is there a system file, directory, or build.prop edit that could be the cause?
[Nexus 6P Original Android Development] flar2:
I don't know much about wifi calling, other than it's extremely finicky. It probably just doesn't work with root or something like that.

What happens if you install EX on completely stock system (no SuperSU)?
[Nexus 6P Original Android Development] troymz1:
Use Tasker to create a profile so it stays in portrait mode until you launch certain apps like YouTube or any other video playing apps. Works great for me. Games that require portrait automatically turn no need to add them to profile.
[Nexus 6P Original Android Development] zgroten:
Was working before just fine same setup on 6.0.

It worked with stock boot.img

Not sure about just EX. How can I remove SuperSU and switch to just EX?
[Nexus 6P Original Android Development] flar2:
Flash the stock boot.img and then flash EX.
[Nexus 6P Original Android Development] slayp00n:
i can do that but, its ridiculous that such an obvious usability issue exists.,
[Nexus 6P Original Android Development] kodabmx:
CIFS

Any chance of adding CIFS support so I can mount a samba share?
[Nexus 6P Original Android Development] GollyJer:
This kernel is working great for me in conjunction with PureNexus. Just paid for the app in the play store to show my appreciation.

Thanks for the awesome work!
[Nexus 6P Original Android Development] flar2:
This is a neat idea, I'm going to do something along those lines. Wake gestures app won't be necessary
[Nexus 6P Original Android Development] Shockz:
I know this might not be possible but what about building on top of that and adding knock patterns and you can set certain patterns to do certain things? Just an idea, some oem phone had this but I forget which one it was.
[Nexus 6P Original Android Development] freemini:
I know this is a bit of a far stretched request, but I might as well ask. If I understand correctly, headphones with apple in-line controls use different signals for vol up/down (perhaps different voltages? I'm not sure) than ones made for android. I recall reading some android phone working fine with both, is it possible to change this in the kernel somehow? The reason I think it could be kernel-related is because of the vol up fix you implemented a while ago which was also based on reading the wrong voltages from controls IIRC.
[Nexus 6P Original Android Development] mobileman88:
[MENTION=4684315]flar2[/MENTION]

Thansk for this great kernel and EX Manager. I just changed from the stock kernel to EX 1.0 . Noticed something a little different. The only thing I enabled in EX Manager app is S2S. When my phone is plugged to the charger, it seems to wake up for around 5 seconds every minute or so. This was not happening before. I will reflash the stock kernel to confirm this. Anyone know what feature I might have turned on by default or accidentally turned on for this to happen?
[Nexus 6P Original Android Development] flar2:
I don't know of anything in the kernel that would do that.
[Nexus 6P Original Android Development] flar2:
That's complicated because it's tied to lockscreen security.
[Nexus 6P Original Android Development] mobileman88:
Thanks. Shall investigate this event
[Nexus 6P Original Android Development] grayskul:
Which log do I upload. I'm only having random reboots listening to music through Bluetooth in my car.
[Nexus 6P Original Android Development] micmars:
WiFi calling on TMO and version 1.0 of your kernel works perfectly on 6.01.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] aamitabh28:
I hated the stock colors

So here is a cool profile from me. Try out and lemme know

RGB = 225 230 256

Saturation 30

Value 135

Contrast 132
[Nexus 6P Original Android Development] zgroten:
After a clean install?

Are you rooted?
[Nexus 6P Original Android Development] micmars:
Yes rooted, system root, clean install.

Also works perfectly on PureNexus.

Sent from my Nexus 6P, #WhiteUIsMustDie, #EndDarkAppOppression
[Nexus 6P Original Android Development] fairyshacker:
how to change to permissive mode?

Cataclysm 6.0.1

Ex 1.00
[Nexus 6P Original Android Development] nathanchance:
Uncheck the SELinux Enforcing option in the Aroma installer.
[Nexus 6P Original Android Development] tech_head:
Anyone else notice that their phone will not rapid charge after 6.01 and Elemental?

I don't know which one it is.
[Nexus 6P Original Android Development] fairyshacker:
so can i flash the kernel again?

if yes, should i flash supersu 2.61 before that?

thanks!
[Nexus 6P Original Android Development] nathanchance:
Reflash Cataclysm (full zip or mod), flash SuperSU 2.61, then flash ElementalX with the Enforcing box unchecked.
[Nexus 6P Original Android Development] fairyshacker:
thanks a lot bro..
[Nexus 6P Original Android Development] TiGuy82:
I am really happy with the app and Kernel. thank you so much.

I would like to ask if is it possible to add Gain option for Bluetooth?
[Nexus 6P Original Android Development] inffy:
Doesn't Cataclysm support enforcing kernels now
[Nexus 6P Original Android Development] xflowy:
jep. works for me in that combi.
[Nexus 6P Original Android Development] adrman:
Rapid Charge working here.
[Nexus 6P Original Android Development] :
[MENTION=4684315]flar2[/MENTION]

Supposedly franco put some battery tweaks into his kernel, would you take a look at them and maybe incorporate them into elementalx?

https://github.com/franciscofranco/angler
[Nexus 6P Original Android Development] flar2:
Neither, it works

It's not a good idea to mess with Bluetooth

I've experimented with many things, and I think you'll find that battery life is very similar on all the kernels. Seven hours plus SOT is possible on stock. But if you wish, you can apply the same tweaks in my app by disabling touchboost and tweaking interactive and cpuboost. I won't add most of those commmits because I like to stay close to stock, and they make negligible difference.
[Nexus 6P Original Android Development] aamitabh28:
Mate every kernel developer goes around development in their usual standard styles. What one dev uses may not be the best for someone else. That gives us the freedom to choose from a plethora of awesome. Ones each with its own unique ability.

I am sure flar2 is aware of franco's git. He might or might not choose to put his tweaks into his kernel
[Nexus 6P Original Android Development] sean222:
Awesome. Glad to hear you're keeping to your style/close to stock. That's what I like about this kernel. :D
[Nexus 6P Original Android Development] aamitabh28:
Cheers!
[Nexus 6P Original Android Development] steveo17:
not to harp too much on battery talk, but for me battery life has been pretty dissappointing. granted i spend 90% of my day on Verizon LTE, the reception is not always the greatest (in a tall office building), but I have been getting about 2.5 hours of SOT over the a 12 ish hour period at which point my phone is dead. No idea how anyone would get anywhere near to 7 hours of SOT
[Nexus 6P Original Android Development] grayskul:
Which log do I upload. I'm only having random reboots listening to music through Bluetooth in my car. <br />

<br />
[Nexus 6P Original Android Development] flar2:
That seems really bad. I'm also in an office tower with hit and miss reception, where LTE increase drain to around 1% per hour, which is higher than when I'm outside, but still pretty good.