yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] :
It wouldn't in and of itself. That's why I was thinking that maybe it's xposed related.

IE: Google play services crashes without a hard reboot. However, a crash that is caused by an xposed module and being unhandled, could cause a hard reboot due to the way that it's hooking the system at a low level.

It could just be coincidence as well though.

*Edit*

[MENTION=4684315]flar2[/MENTION], here's my reboot logs:

Annotate-ramoops

Console-Ramoops

Of course, I'm on Euphoria-OS with xposed and all sorts of stuff going on. So it's likely nothing kernel related specifically. Just figured I'd share. This was while plugged into the stock charger with a 10' cable.

Also, I'm just kinda curious. Is there a reason/benefit that you made you go with faux's sound driver over franco's? I've always found that faux's driver is a bit iffy sometimes, while franco's seems a bit cleaner/more direct. I was trying to manually boost the speaker volume by editing /sys/kernel/sound_control_3/gpl_speaker_gain which *should* work, except that faux's driver is kinda weird sometimes. It should be included in the driver you have committed, but I can't for the life of me get it to work. I seem to recall his driver needing some sort of magic number to take it though.

I reverted Faux's soundcontrol and tried adding Franco's here and modifying it to control the speaker boost here. However, it doesn't seem to be doing anything either (neither did faux's seem to).

His path is /sys/devices/virtual/misc/soundcontrol

Obviously, this would break compatibility with your tuning app. I'm just trying to figure out what's up with speaker volume boosting. :s

*edit* actually, your kernel app finds those paths for that driver as well... Nice.
[Nexus 6  Original Android Development] ArcMage:
Yeah, if something kicks the system hard enough all kinds of stuff dies.

I had a totally intractable hard crash that presented only a null pointer exception in an irrelevant line, due to ContextWrapper.bindService() puking it up the chain improperly. That one actually traced back to asking TeslaUnread to provide counts for IMAP addresses.

Traced by blindly wiping, reinstalling, and enabling/disabling apps. I'm not really good at this.

~thank your devs~
[Nexus 6  Original Android Development] jk8260:
I can confirm tmo wifi-calling is working with EX v2.03 on PureNexus. Get wifi-calling working on the pure nexus stock first then flash EX 2.03 works like a dream. Please note that I have found that some themes break wifi-calling for dialer. Just change delete that single dialer theme file and profit. Thanks for the best kernel out for our N6 !!!

If you try any other kernel you must reflash the ROM before flashing EX2.03 or no joy.
[Nexus 6  Original Android Development] TransportedMan:
Anyone have any links or pictures with the type of battery life and screen on time you get with this kernel? I feel like its a more performance based than anything especially with all cores online all the time.
[Nexus 6  Original Android Development] :
You just unset that option, and it hotplugs like normal. I don't take battery screenshots personally because there are too many variables that affect them. So its basically like looking at a picture of a car and being like "I bet that car gets great gas mileage". There's no real reference, and depending on the driver it can vary greatly.
[Nexus 6  Original Android Development] TransportedMan:
There's not hotplug option for the kernel in Kernel Auditor. All cores are just always online.
[Nexus 6  Original Android Development] :
Not sure then. There's a toggle for it in ex kernel manager.... I don't know what it's changing in sysfs though.
[Nexus 6  Original Android Development] Lancez:
Which version of pure are you using
[Nexus 6  Original Android Development] jk8260:
9/17
[Nexus 6  Original Android Development] danarama:
It's not about the speaker top volume. It's about after lower battery %, top volume is reduced, but not constant. It fades in and out and is very annoying when using speakers.

I thought I included a link to my thread but it seems I did not.

http://xdaforums.com/nexus-6/general/curious-speaker-volume-lowering-issue-t3136759
[Nexus 6  Original Android Development] magnamentis:
confirmed. this happens as well over bluetooth even on charger. i first thought something i set-up badly in viper4android. it comes and goes like some kind of volume throttle one would expect from a badly set clipping prevention.
[Nexus 6  Original Android Development] danarama:
Yeah it's like some really dodgy normalisation
[Nexus 6  Original Android Development] :
I don't know if you're into development, but you could always try to replace the normal drivers with caf drivers and see if they fix it. But then you're heading toward a hybrid kernel.
[Nexus 6  Original Android Development] flar2:
Does it do this on stock? Maybe the fauxsound driver is messing something up?
[Nexus 6  Original Android Development] magnamentis:
[MENTION=4684315]flar2[/MENTION]

is this information which tells you something:

<2>[ 1921.914787] kernel BUG at drivers/base/power/main.c:411!
<0>[ 1921.914791] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP ARM

if i reboot and the device reaches a booted state with lockscreen ready to unlock there are two procedures:

a) i unlock the device and everything is running perfectly well

b) i let the display fade out and wait, device is dead (SOD) does not reboot. just not possible to wake it up or it's off which at that moment looks the same

further, intermittently this would happen overnight, means the device was running all day without trouble but in the morning it's off or SOD'ed.

never happens on charger, only on battery and on reboot from flashing rom & kernel new. should you need more input or the entire log, no problem

it's on the my MacBook Pro's desktob ready, just thought to send the most relevant lines forst to see if this is something you want to look into or not.
[Nexus 6  Original Android Development] danarama:
I haven't tested stock M but yes it happens on Lollipop stock on multiple devices. I think it affects everyone but some just aren't noticing.. But the issue seems to kick in earlier on lollipop with an M kernel.

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

It's maybe worth a try but I do think this is affecting everyone.
[Nexus 6  Original Android Development] :
[MENTION=4684315]flar2[/MENTION], using 1.10 with pure nexus, I'm getting flooded in my logcat with powerhal touch boost no such directory errors.

I'm sure that this isn't a kernel issue... But its there an easy way to disable touch boost? Or maybe modify the ramdisk to create the directories.
[Nexus 6  Original Android Development] slyguy2000:
I don't get these errors with stock kernel 3.10.40-gc16a3c6, only with EX 1.10

...if that helps
[Nexus 6  Original Android Development] flar2:
That's because mpdecision is disabled. They messages are annoying but harmless

logcat | grep -v touch_boost
[Nexus 6  Original Android Development] :
Yeah, I just wasn't sure if there was a simple fix to stop it. Like just creating a dummy file in the unit for it to write to so that it would stop spamming.

I know the rom source can be modded to just remove the log entries, but that's a bit more involved.
[Nexus 6  Original Android Development] ivanov13:
Slight overclock on 1.10 does magic;) best performance with this kernel out of all I've tried. Thank you [MENTION=4684315]flar2[/MENTION] for sharing this masterpiece!
[Nexus 6  Original Android Development] Beakhole:
[Tasker Intents]

So I've posted about this before but wasn't able to get it to work till last night:

I've discovered that for some reason I can't use the AutoShare Tasker plugin to send the intents below to control the Powersave and Performance Modes.

Powersave:

flar2.exkernelmanager.powersaver.ENABLE_POWERSAVE

flar2.exkernelmanager.powersaver.DISABLE_POWERSAVE

———————————————————

Performance:

flar2.exkernelmanager.performance.ENABLE_PERFORMANCE

flar2.exkernelmanager.performance.DISABLE_PERFORMANCE

So instead, in order to get the intent broadcasts to work, I had to use the built-in Tasker task of System > Send Intent. Then for "Action" I use one of the above Broadcasts, for "Package" I use flar2.exkernelmanager and then for "Target" I selected Broadcast Receiver. And they work perfectly!
[Nexus 6  Original Android Development] pittrich:
Express setup

Hi,

can you make a flashable express setup?

Regard
[Nexus 6  Original Android Development] magnamentis:
if you download from within the app it gives you the choice between express and aroma version
[Nexus 6  Original Android Development] pkgnex:
I had an odd occurrence on 1.10 that I want to report.

I switched on USB fast charge in the EX app (first time I've ever done that), and my battery life went to crap (3-4% idle drain per hour).

I traced the drain to the SMB135X wakelock (it basically was keeping the device awake 100% of the time).

Even after turning USB fast charge off and rebooting, the same thing was happening - same wakelock wouldn't ever let the device sleep. I had to re-flash the kernel without ever turning on USB fast charge to keep the wakelock from popping up and have decent battery life.

I know this is somewhat anecdotal as I didn't get any logs or anything, but this is the only time I've had crappy batter life with EX, and also the only time I ever tried turning on USB fast charge in the app. For me, setting that flag in the app definitely seems to make that SMB135X wakelock rear it's ugly head for some reason.
[Nexus 6  Original Android Development] magnamentis:
must be a coincidence because i have fast charge on for 2 years on nexus 5 and from day one on nexus 6 and never encountered this issue.

further you can be assured that if this would be more than a coincidence there would be lot's of related feedback here and honestly speaking, it's

the first time i hear that (does not mean it is the first time of course and does not mean it did not happen LOL ) however perhaps someone

more tech-savvy knows the wakelock and can tell more, because i've never seen that one albeit i'm checking them every morning with 3 apps:

amplify, wakelockdetector and C3's batterymonitorwidget .
[Nexus 6  Original Android Development] pkgnex:
Definitely could be a coincidence, just didn't seem likely. I used this on the old Galaxy Nexus for years and never had an issue either, but I've come to learn that each device can be different in terms if what works and doesn't.

I don't know how many people actually use USB fast charge on this device. The quick-charge is so fast, and the battery life gets you through at least a day, but I suppose you're right that if it were a significant problem, someone else would probably have reported it.

I'm surprised you've never heard of that wakelock, though - it's one of the 3 or 4 wake locks that Franco, Imoseyon, and others provide disabling toggles in their kernels to block because it was so bad before 5.1. I think this particular one has something to do with wireless charging (waking the device to ensure it is charging, or checking if it's near the wireless charger), so that also made sense to me that it only ever occurred when flipping a charging toggle in the EX app.

I guess it's not an issue unless someone else chimes in to confirm, though.
[Nexus 6  Original Android Development] magnamentis:
it have an idea as to that wakelock (why i'm not aware of it)

a) i was on 5.0.x for 1 or 2 weeks only, late LP adopter ( final switch while mutlirom testing for longer ) and then i check wakelocks only after pure battery usage, i even set all my battery and wakelock testing apps to only show "on battery" or with the help of tasker to reset stats (amplify) hence i just don't have any wakelock connected to charging high up in my stats after 8-10 hours daily stats check.

and yes, it's even worse than from device to device. it's ridiculous sometimes how things can go havoc on the SAME devcie without making changes from one day to anothe, but i must say that i have stable battery 0.3-0.4%/h in idle on all 7 devices in the mean time, just made it happen for the OP2 last night for the first time :) after dealing with 1%/h before on that new device-os-kernel-compo
[Nexus 6  Original Android Development] dynamo147:
Hey all, I love the wake gestures but wanted to try my battery without them and so I turned then off, but occasionally they work, especially the double tap and I can even feel the wake gesture vibration so I know its not just me happening to wake up the phone when it does the notification peek. I went into root browser and all the values for the gestures at set at 0, and even with the kernel manager everything is set to disabled and to keep the setting that way after reboot, any ideas?

Most up to date kernel, 5.1.1 Android, 5.1 Paranoid, Rooted Nexus 6.
[Nexus 6  Original Android Development] :
Does the rom have its own double tap to wake?
[Nexus 6  Original Android Development] dynamo147:
No I believe it does not, fairly certain like 99.9 unless it's baked in and does not have an off feature!
[Nexus 6  Original Android Development] Alxoom33:
Yes, it does.

It is set when you first start the Aroma installer.
[Nexus 6  Original Android Development] :
Kinda figured that's what it was.
[Nexus 6  Original Android Development] dynamo147:
It does? Hey learned something new then. So to turn it off I should run aroma again? Or is there a setting somewhere in Paranoid Android that I have to toggle, or is it both?
[Nexus 6  Original Android Development] Woody:
Kernel: Go into root/etc/elemental.conf and open in text editor. There you can change whatever parameter was set in the aroma install. Don't forget to hit Save.

PA Settings: Not sure. I don't run that one.
[Nexus 6  Original Android Development] dynamo147:
I remember that file path from my N5...BUT now looking on my N6 my root folder is empty...0.o? I did fine the values in the sys/Android touch folder though and wake gestures, dtw, and stw are all on 0. I do have sts on however, that being 3. Is something wrong with my root folder which is causing the problem?
[Nexus 6  Original Android Development] DroidIt!:
Um, noticed the N5 slim thread was closed. The link the mod supplied, at least in tapa says invalid thread id. Any ideas?
[Nexus 6  Original Android Development] Woody:
Might be a wonky Tapa error, cause we never get those right? Lol. I checked and am getting the same error. Something about "Invalid thread ID #5". Not sure, but I checked both links and they both are the same AND correct.

In any case, it is Yank's new thread in OD. I'll post the link here in full and not embedded.

This is for the Nexus 5 section, so anyone in the Nexus 6 section reading this, I'm just trying to help a brotha out.

http://xdaforums.com/google-nexus-5/orig-development/hammerhead-slimlp-5-1-1-beta-0-8-t3214745

Sorry for the OT and Hey [MENTION=4684315]flar2[/MENTION]. Picked up my N6 during the fire-sale 2 weeks ago and been running ElX since day one.

************************
[MENTION=5371470]dynamo147[/MENTION] That is weird since the /sys folder is in the /root section. Maybe look to see if you have any radios checked that might be hiding root or something like that. What file explorer are you using. I use Root Explorer and have for years now. Other have come and gone, but it's hard to beat the king.
[Nexus 6  Original Android Development] :
It's /etc/elemental.conf or /system/etc/elemental.conf

Same folder/file, /etc is just a symlink to /system/etc
[Nexus 6  Original Android Development] flar2:
/sys/android_touch/ is the path

If s2w and dt2w are 0, then the gestures are disabled. There is no grey area here, they're on or off.

The stock dt2w is located at /sys/bus/i2c/devices/1-004a/tsp and should say OFF

The other possibility is there is some other mod that turns on the screen, such as ambient display or gravity screen
[Nexus 6  Original Android Development] :
flar2, you are a bad a#$! Your M kernel is awesome along with your app on stock rooted preview. Been onboard 2 days now and staying put until other M roms drop once they bring it official. :cool:
[Nexus 6  Original Android Development] Psych0t1c20:
I just have a request; could you add vibration control?
[Nexus 6  Original Android Development] :
It's included, controlled in ex kernel manager.

For both, vibration and gesture haptic feedback.

Not really sure what you're requesting.
[Nexus 6  Original Android Development] lexus91:
I also experience the same thing, and using kernel Adiutor for the kernel manager. So this might explains the situation?
[Nexus 6  Original Android Development] flar2:
I added vibration control already:

/sys/drv2605/rtp_strength

There is a slider to control it easily in EX Kernel Manager
[Nexus 6  Original Android Development] Psych0t1c20:
Oh I'm using kernel auditor and didn't see it.
[Nexus 6  Original Android Development] Alxoom33:
Use the Ex Kernel Manager, awesome app and support [MENTION=4684315]flar2[/MENTION] awesome developer. Look in OP for links.

Probably not in kernel auditor.
[Nexus 6  Original Android Development] dynamo147:
Using me the es file explorer! I find its interface much more friendly lol but I use root browser as well in case I feel one is hiding the other, and mmm do you mean radios like the actual phone radios that you can flash?
[Nexus 6  Original Android Development] danarama:
Who are you talking to? If this is in response to someone, please use quote functions.
[Nexus 6  Original Android Development] dynamo147:
I was thinking it was ambient display too.....until I set my gestures vibration to 100 so that I could feel if the dt2w was happening and it sure was since ambient display leading to the screen waking and or unlocking doesn't cause any vibration, curiously enough my tsp file says 'Auto' figure I should go ahead and put in 'OFF' right?

BTW flar, used the kernel since N5 and I love it and went ahead and bought that kernel manager too
[Nexus 6  Original Android Development] flar2:
Yes, AUTO means that stock doubletap is enabled.
[Nexus 6  Original Android Development] dynamo147:
Now this is interesting! Okay so FYI I changed the text in that file and it indeed worked!

But let me get a couple things straight in my head first....so the N6 had some type of stock dt2w function that was presumably turned on by Paranoid Android which is found under sys/bus/ correct?

Now the main reason I wanted to disable dt2w was because I wanted to see if it would affect my battery by any large amount, from what I've dug up it seems that the kernel's dt2w shouldn't have any affect on battery life yes? Is that the same for the stock dt2w? Is there a recommend setting when a phone has both stock and kernel dt2w such as one being off and the other on or does it not matter?
[Nexus 6  Original Android Development] :
It doesn't matter at all.

The only battery savings that youre going to see from turning any of the wake gestures stuff off is negligible. Basically, whether the digitizer stays on or not. Which, it doesn't draw much power so there's not much savings there. That's assuming the code even turns the power off to the digitizer while the screen is off when dt2w is disabled... It probably doesn't.

What can save you battery is disabling it if you're not using anything for Pocket detection... The screen uses to much power to light the inside of your pocket. Luckily flar2's wake gestures app includes this.
[Nexus 6  Original Android Development] Brotuck:
This Kernel rocks ! And is rock solid on M !

Verstuurd vanaf mijn Nexus 6 met Tapatalk
[Nexus 6  Original Android Development] dynamo147:
Thanks for the info was really helpful and I appreciate it!
[Nexus 6  Original Android Development] jeebuspwnz:
I can confirm that the M Preview 3 kernel boots and allows for root access on 6.0 Final. No clue if it's optimized or ideal, but it does boot and allows me to restore all my stuff in Titanium.
[Nexus 6  Original Android Development] flar2:
Thanks!

I doubt there are many changes from developer preview 3 to the final version.
[Nexus 6  Original Android Development] LittleJakub:
that is great news! however I also wonder, if it needs to be more optimized. also, what root would you suggest?

cheers!
[Nexus 6  Original Android Development] djkinetic:
On dev 3 i was able to make changes to /system within android, it seems the final factory image makes /system write protected. any chance you can update your kernel to disable this =)
[Nexus 6  Original Android Development] danarama:
Austen changes on dev preview 3 needed a special kernel I believe.
[Nexus 6  Original Android Development] djkinetic:
when i was on JDX and Elemental 2.06 there were no problems with /system write access, on final M release with Elemental 2.06 no /system write access but root does work.
[Nexus 6  Original Android Development] danarama:
Ok, well not sure how that worked. Myself and many others in the flashable preview thread all had issues with /system r/w and I believe it was by flashing despair kernel, was the only way to get system r/w on preview 3.

You're the only person I know of who had system r/w without despair kernel.
[Nexus 6  Original Android Development] flar2:
Update

For Android 6.0 Marshmallow

Download:

ElementalX-N6-3.00

Changes:

-update for Android 6.0
[Nexus 6  Original Android Development] metaphz:
Is /system R/W available on this update? Having a terrible time getting AdAway to work. I forgot how awful the Internet is with millions of advertisements.
[Nexus 6  Original Android Development] Flying_Hellfish:
It doesn't appear to. But there's a symlink zip you can flash HERE then you just set AdAway to write the host file to /data/data/hosts and it works like a champ.
[Nexus 6  Original Android Development] flar2:
I don't know, I haven't really used it yet, just updating my devices and kernels tonight. I will look into it later this week.
[Nexus 6  Original Android Development] ohad129:
How to root new 6?
[Nexus 6  Original Android Development] Brotuck:
Please take a look at this post, the kernel needs permissive for RW capabilities.

http://xdaforums.com/showpost.php?p=63152945&postcount=145
[Nexus 6  Original Android Development] flar2:
EX is permissive, and has been for the all the M previews. There are several issues that need to be looked at on Marshmallow. But I was up til 3am last night updating my devices and kernels, and now I'm at work so I haven't had a chance yet.
[Nexus 6  Original Android Development] El Nino1977:
I can R/W system on M, I changed my build.prop lcd_density to 500dpi on flars 2.03 kernel. Also changed the target hosts preference to data/data/hosts in Adaway and all was fine.
[Nexus 6  Original Android Development] jtwebfusion:
I had to flash back to Despair's R20.6 kernel.
[Nexus 6  Original Android Development] flar2:
Okay, I just checked the system rw thing, and all you need is an insecure boot.img

I'll push an update tonight

Note that it will be OPTIONAL, as I prefer to ship the kernel in as secure a state as possible.
[Nexus 6  Original Android Development] WhammyDroid:
[MENTION=4684315]flar2[/MENTION], do you know if updates to the system partition can be made through TWRP if you have a secure kernel?
[Nexus 6  Original Android Development] flar2:
I haven't checked specifically, but generally recovery lets you do almost whatever you want.
[Nexus 6  Original Android Development] stumpy352:
Thanks in advance [MENTION=4684315]flar2[/MENTION] for the next update. Not being able to put my ringtones in /system/media is driving me crazy.
[Nexus 6  Original Android Development] WhammyDroid:
You should be able to put ringtones in the /sdcard/ringtones folder. Android will see it and add it to the list to use. You do not see to put them in the system partition.
[Nexus 6  Original Android Development] danarama:
Recovery has its own kernel. It.doesn't use the kernel you have in your rom.
[Nexus 6  Original Android Development] hlxanthus:
. . . or use /oem like I do. Do it once and done forever on any rom you ever flash.

http://xdaforums.com/showpost.php?p=62892696&postcount=17
[Nexus 6  Original Android Development] LGtMgG2t:
That's such a great tip for us serial crack flashers! :laugh:

Thanks for the heads up on this, going to try it out a little later.