yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Formhault:
Lol, okay. Thank you!

PS : Tapatalk still screws up quotes, huh? What the hell :confused:
[Nexus 6  Original Android Development] :
I didn't think DST changed until next weekend...
[Nexus 6  Original Android Development] Formhault:
For me it did...
[Nexus 6  Original Android Development] magnamentis:
As promised as per your request, HBM widget ON/OFF via tasker working like a charm, thanks again.:good:
[Nexus 6  Original Android Development] Polv89:
i flash it on aosip rom...

#1

flashed kernel

bootloop on bootanimation

#2

flashed permissive zip

flashed kernel

bootloop on bootanimation

what can i do?
[Nexus 6  Original Android Development] shawnten:
I sure hope you support the 6p. And I really hope your high brightness widget works. Nexus 6 has been my favorite device because I can get the screen so bright when I want to not just in sunlight
[Nexus 6  Original Android Development] flar2:
Also flash the modified boot.img from Chainfire
[Nexus 6  Original Android Development] Polv89:
it failed for me...

should i flash it first ?

1. flash modified boot.img

2.flash permissive

3.flash ex kernel?

i've tried, but modifiet img give me "FAILED"
[Nexus 6  Original Android Development] flar2:
It's not a flashable zip, unzip and use Flashify to flash it
[Nexus 6  Original Android Development] flar2:
Neither device has swap or zram, so it doesn't matter.

You definitely don't want to use sdcard as RAM, it would be very slow. Some devices, including he Nexus 9 and 5X, use zram, which treats some of the RAM as compressed swap. But that's not necessary on this device.
[Nexus 6  Original Android Development] isaakmg:
I don't know why with ex kernel 3.05 I have reboots in diferents Roms, stock, cataclysm etc... Any solution?

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] flar2:
Clean install

This kernel is very close to stock, you shouldn't have reboots. Mine is rock solid on stock ROM.
[Nexus 6  Original Android Development] Polv89:
good !!!!!

flashed boot.img on flashify, flash more (selected ex kernel (without flash permissive zip) and then reboot to recovery)

Now it works ;)

Do you think is better wipe cache and dalvik?
[Nexus 6  Original Android Development] isaakmg:
Yes, clean install ever. Random reboots with stock and cataclysm.....With other kernels nothing happen.....

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] flar2:
Sorry, but there is nothing that I've done to the kernel to make it unstable. This is like stock kernel. Try using interactive governor. If you are using wake gestures app, disable pocket detection.

This hardware is the flakiest I've ever seen, so sometimes random reboots occur that have nothing to do with he kernel.
[Nexus 6  Original Android Development] Alxoom33:
EX 3.05 working flawlessly on latest Cataclysm rom, worked great on JDX 4.1. Bootloops no matter what I try on Xtrasmooth. Go figure!
[Nexus 6  Original Android Development] mbl1979:
I have your kernel on my nexus 6 running cataclysm ROM, fast smooth and stable. Not to mention better battery life. In a week I have had zero reboots.
[Nexus 6  Original Android Development] isaakmg:
Again, clean installed cataclysm + ex kernel 3.05 without wake gesture app. Will see that happen with random reboot.

Thanks for you answer.

Enviado desde mi Nexus 6 mediante Tapatalk
[Nexus 6  Original Android Development] tealio:
I had random reboots on an older version kernel and stock rom when using wake gestures app. [MENTION=4684315]flar2[/MENTION] tried helping, but I ended up chalking it up to my particular device...

Removing wake gestures app and disabling gestures in kernel solved my reboots.
[Nexus 6  Original Android Development] flar2:
You could still use the wake gestures. It's the wake gestures app that causes problems on this device, more specifically, pocket detection. The proximity sensor seems to make the watchdog trigger a reboot.
[Nexus 6  Original Android Development] tealio:
Agreed. Perhaps I was being too concise.

The choice came down to random reboots vs random unlocks, which led to random calls, random YouTube videos playing, random... Well... Anything a modern phone can do... And without pocket detection, I found wake gestures to be a feature I couldn't use.

This is no reflection on [MENTION=4684315]flar2[/MENTION] of course. Love the kernel, love the other apps... Wake gestures app just doesn't work well on this hardware, particularly my specific device. Others may have had success, and good for them. I mainly wanted to share my experience with the app and point out that this kernel is not responsible for the reboots... And the wake gestures app probably isn't directly responsible either. This device's hardware is to blame. That said, I still love my phone...
[Nexus 6  Original Android Development] PhilDX:
I don't use the wake gesture app, I use tasker to enable only the sweep2wake gesture. and I limit it to only the sweep from left to right. it works great and I never have accidental wake ups in my pocket. love this kernel.

syntax: echo 1 > /sys/android_touch/sweep2wake
[Nexus 6  Original Android Development] Formhault:
Does sweep2wake consume more battery than DT2W? I find it to work extremely well, it's very precise :eek:
[Nexus 6  Original Android Development] isaakmg:
In
[Nexus 6  Original Android Development] kraehetest:
random reboot

[MENTION=4684315]flar2[/MENTION]

Hi, I have also random reboots. I’ll give you some informations, maybe this will help you.

I have done a clean OS installation + TWRP + SuperSU 2.52 + your kernel 3.01. Everything is fine, no bootloops etc.

A have the random reboots ONLY with kernel version 3.02, 3.03 and 3.04. I haven’t tested kernel version 3.05, because kernel version 3.01 run stock stable at the moment.

Until now, I've been watching the reboot only under the following situations. Phone is on charger, it’s dark in the room and it happens only when I play the game “Family Guy”. The phone freezes and reboots about 5 seconds later.

What are the changes between kernel 3.01 and 3.02?

I will help you, which log files you need and in which folders are these files?

With best regards

Kraehe
[Nexus 6  Original Android Development] magnamentis:
using the opportunity to bring up an issue i have for months now only on N6 but not on N5 with same setup.

whenever i try to trigger wake gestures ( built in ) with a tasker intent in the way that i wanted gestures off the moment i disconnected any power source with: echo 0 > sys/android_touch/sweep2wake or echo 0 > sys/andoid_doubletap2wake, it the N6 goes into a random reboot within 1-3 minutes but not immediately and the task was executed flawlessly, hence it was working and did the job but a short time later a had an RR.

this was so consistent that i think it should be reproducable. this happened on a variety of LP roms as well as with newest cataclysm for marshmallow. this make me strongly believe that it's device specific, albeit i cannot yet figure the relation between an already successfully executed shell command and an RR, but it is a 100%er and hence has to be considered a fact.

further i tried to increase voltages by 10-15mA globally as well as to set a input boost higher than stock and the likes, no difference.

further i do not have the issue when executing the disable of gestures manually through the EX app, even though i'm sure that it's the

identical command. again i want to point out that this does not happen on the N5 which was my main reason to make that tasker task,

to have gestures off while not charging to avoid the 2%/h drain that comes with it.

should you be interested to narrow this down i'm ready to deliver anything you need, a log for example while in that case i would appreciate if you would let me know what kind of log i would need for that. i have the script stored, hence can simply copy paste it back into the profile and go from there. as it works on the N5 where i really want it no big issue if you think it better not to follow up, just thought it might be interesting for you as well.

---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------

no. while the power consumption on this device is negligible, it remains the same no matter which of the gesture you have in use.
[Nexus 6  Original Android Development] mattmtx:
Hello [MENTION=4684315]flar2[/MENTION], how are you?

I have one question, before, with LP we had support for init.id (I usually use it). Now, with Marshmallow, I don't see that. Thats correct? or it's my error? I did a clean installation yesterday, first rom, then the kernel, I went to system/etc/ and there isn't the folder init.id, also I installed Universal Init.id and executed the test, and the message was "Your Kernel Does Not Have init.id Support".

So, is not supported, right? :(
[Nexus 6  Original Android Development] flar2:
You should be using /system/su.d

Init.d hasn't worked reliably for a long time, I stopped using it about a year ago
[Nexus 6  Original Android Development] flar2:
The only change between 3.01 and 3.02 was a small update to kcal drivers, I think.

However, I don't think that was the cause of your reboot. This device has some kind of electrical problem. People get reboots on the stock kernel and other kernels too.

Anyways, all this talk of reboots and I'm going to get a bad reputation again and nobody will use this kernel. I have no reboots, ever. This is the phone I use all the time, its closer to stock than any other kernel. Almost all the logs I've received either end abruptly or have watchdog bites. There's not much I can do about that.
[Nexus 6  Original Android Development] PhilDX:
I never carefully compared the two options, but with sweep2wake enabled, my battery drain overnight is 0.4%/hr.
[Nexus 6  Original Android Development] :
I know it's outside of the scope of this thread, I didn't find anything easily when googling...

Init.d used a loop in the init script to run parts everything in the init.d script (so it was never REALLY init.d). How does su.d run? Is it programmatically as a feature of supersu?

Also, as to the talk of reboots, I've never gotten reboots running flar2's kernel. Though I have in others.

This phone has oddities, and even though it's a nexus device a lot of features still require workarounds. In doing so, they'll sometimes cause issues. That's not the fault of the kernel necessarily. It's possible that you can get reboots on one kennel but not another, which would lead you to think that is the kernel. Sadly though, that's not always the case. You could flash the stock boot.img on this phone with no issues. Flash the same image a second time and start getting reboots... Its effing weird.
[Nexus 6  Original Android Development] mgostom:
I have to ask this. I tried searching, but I can't find anything specific to this example. The rom I'm running is Lightrom which the selinux is permissive. I'm using kernel EX 3.05, which I'm pretty sure is enforcing. However, when I checked the se status, it shows Permissive. I had to flash Chainfire's boot.img before I could flash the kernel. Having the same setup with a different rom, it was in enforcing mode. Why is it showing Permissive in this case? Anyone has the same experience? Perhaps it's a question for the rom dev, but I figured I'd start here.
[Nexus 6  Original Android Development] Formhault:
[MENTION=4684315]flar2[/MENTION]

I'm on Cataclysm ROM, with EX 3.05. I've enabled DT2W and proximity sensor check in the Wake Gestures app, but...

Some times I gotta tap the screen 4 times in order for DT2W to work. Oh and if I enable proximity sensor check in the Wake Gestures app, the screen turns on slower (I guess it takes time to check for the proximity sensor, with this kind of implementation).

I even had the screen not turning on two times today... DT2W, power button... nothing... had to wait ~5 seconds for it to come on :eek:
[Nexus 6  Original Android Development] flar2:
dt2w without s2w is Google's implementation, which is very unreliable.

dt2w with s2w enabled in at least one direction is my implementation, and will work more reliably, however, the best way to use wake gestures is s2w up, all other directions disabled, and dt2w disabled.

The problem with dt2w in general is that accidental wake occur more easily than with s2w. Personally, I don't like dt2w.

I also don't recommend the wake gestures app for this device. If you only enable s2w up, you don't even need pocket detection. It's more reliable and faster too.
[Nexus 6  Original Android Development] flar2:
EX is enforcing.

I'm not familiar with that ROM, but it may be setting selinux permissive with a script or setting.
[Nexus 6  Original Android Development] flar2:
init.d depends on busybox runparts, but something changed in lollipop that made it not work reliably. I used to run EX init scripts with init.d, but it wasn't always working so I switched to a solution completely in the ramdisk.

Chainfire turned me on to /system/su.d, which is a feature of SuperSU. It works reliably and occurs early during boot up.
[Nexus 6  Original Android Development] Formhault:
DT2W without S2W (swipe to wake)? You're saying that DT2W = different code than for S2W? I thought it's the same code... but then again it's swipe as opposed to double tap so yeah, makes perfect sense.

OKAY, THIS IS AWESOME. Makes so much sense. I did think about this today, during an extremely boring class, but entirely forgot about it, then went ahead to annoy the living bonkers out of me with DT2W not working correctly throughout the entire day. :laugh:

How about double tapping one corner of the nav bar to sleep? Would that be easy for you to implement? Or double tap on status bar...

The swipe to sleep is... well... very likely to set off the phone into a neverending spinning motion :silly: along the fact that it's not very precise :confused:
[Nexus 6  Original Android Development] :
Yeah, I had seen where he explained that su.d ran reliably after se Linux contexts. Just didn't see for sure that it was a function of the supersu service/binary.

I think the problem with lp+ was just where it tried to run it. I've noticed that d scripscripts will sometimes run before drivers even finish making all their sysfs entries (some of the oddness with UKM that people get, unless they've changed recently to use su.d and I just missed it). Just wasn't sure why that was.

Thanks for the info, as always you're awesome.
[Nexus 6  Original Android Development] 93fuelslut:
Subscribed
[Nexus 6  Original Android Development] flar2:
I have sweep2sleep, but I stay away from things like doubletapping status bar to sleep. This is better to implement as an app, because the kernel has no idea about the status bar or anything else showing on the screen.
[Nexus 6  Original Android Development] Mercado_Negro:
FWIW, dt2w and s2s has been working flawlessly here using Wake Gestures. I'd say I'm actually impressed by how accurate and reliable it is. My device is new (and it was actually manufactured on August) if that means something.
[Nexus 6  Original Android Development] Formhault:
[MENTION=4684315]flar2[/MENTION]

Last night, before going to bed, I rebooted my phone. ~3 minutes later, I come back and see the Google splash logo... which means it rebooted itself again (which is something that used to happen on LP, with Pure Nexus + Elite combo) almost one out of every 3-4 reboots.

I grabbed the pstore folder and a last_kmsg log. They're attached to this post. Hope you can find something :eek:

EDIT : It just happened again. I just flashed the latest Cataclysm update + EX 3.05. Changed DPI with Texdroider and rebooted. 5 minutes later, I wanted to use the phone. Woke it up with the power button and the touchscreen didn't register anything. Turned the screen back off, thinking it's a random hiccup... then it stayed black for ~10 seconds, before rebooting again. A secondary set of logs has been attached.
[Nexus 6  Original Android Development] magnamentis:
For what it's worth i confirm that this can happen from time to time for no obvious reasons. it simply boots twice and after second boot works flawlessly like before. could have to do something with all the tasks performed after boot, especially starting root apps. i'm very curious as to what the logs will tell to those who have deeper understanding. thanks for brining this up.
[Nexus 6  Original Android Development] :
Both functions are provide in the wake gestures driver. However, I believe that a large number of roms out there include their own dt2w function within the rom itself, not necessarily dependent on the kernel.

If that's the case... Maybe that's some of what's causing people issues if they have both enabled.

As for some of the dt2w not working issues kernel side, that might just be people fat_fingering it. The code is locked to a 150 radius for both taps within half a second. Maybe your taps are too far apart?
[Nexus 6  Original Android Development] Formhault:
My fingers are pretty slim, and I do know how dt2w is supposed to work. I had owned an OnePlus One for almost 5 months (which does have native dt2w, which worked absolutely perfect).

It is the same as with s2w. Some times, you just have to do it twice :) not sure why... But perhaps if Google had finished their damned work and finalized the code for dt2w, things would work the way they should (perhaps there is more to it than just pure software, I dunno).

---------- Post added at 01:06 PM ---------- Previous post was at 01:05 PM ----------

@magnamentis Thanks for confirming.

This has been happening with Elite kernel, as well. Both in conjunction with Pure Nexus (LP) and Cataclysm (M).
[Nexus 6  Original Android Development] italia0101:
Quick question for the developers here ;

I don't suppose there's any way to actually measure doze time is there ?

I found that with " $ adb shell dumpsys deviceidle step" you can actually advance the steps of Doze
[Nexus 6  Original Android Development] flar2:
Did you get rid of the wake gestures app?

It could be that the wake gestures are not stable with your phone for some reason.

Both logs had no kernel errors, but did report pwr key presses near the end.

Is there a lot of static electricity in your environment?
[Nexus 6  Original Android Development] Formhault:
I no longer use the Wake Gestures app. Only set s2w via EX Kernel Manager.

Static electricity...? I don't know, maybe? I'm rocking an UAG case on my Nexus 6, with a tempered glass on it. So I'd say the potential static doesn't discharge via phone... Besides, shouldn't the phone be able to withstand those pulses?
[Nexus 6  Original Android Development] flar2:
I'm just trying to think of what might be interfering with the gestures. Maybe it's the tempered glass. I have tempered glass on my HTC m8 and it seems to increase the touch sensitivity a lot (as in ghost touches), not sure if that's a typical effect or not.
[Nexus 6  Original Android Development] :
It might not be feasible, but wouldn't rewriting the driver to check for say 5 or so gestures in a line sequentially before registering it as a swipe?

I think for now it only checks for like 2 in a direction.

I'm guessing that random touches from static wouldn't meet that criteria, so that could help filter that out some.
[Nexus 6  Original Android Development] flar2:
It already has to pass several thresholds to register a gesture. At this point, I think they work very well, at least for the majority of people.
[Nexus 6  Original Android Development] enzippo:
I currently disabled dt2w 'cause during a call the phone vibrate like dt2w is activated by itself or with touch of my face. When the calling is finished, i need to rewake the screen by double tap...
[Nexus 6  Original Android Development] mattmtx:
I need some advice here.

I use:

ElementalX governor.

1 core during suspend.

Gboost disabled.

Up_threshold 90.

Custom Hotplugging.
[Nexus 6  Original Android Development] magnamentis:
you can reduce your idle drain while you SOT seams not that bad depending on what you're doing then.

download greenify beta with extended doze mode to reduce the time until doze gets activated to zero, that will most probably reduce your idle drain to half or even below 1%/h. i get between 0.85 and 0.95%/h while cell signal and wifi signal still have their impact as well as the number of apps and mail accounts you sync on your device. further you can go to build.prop and reduce wifi-scanning by setting something higher than 60 seconds, impact will be small and for SOT mostly since wifi scanning is dozed in idle.

EDIT: sorry that i was unclear, it's 0.85-0.95%/h awake not battery drain, battery drain is 1-2% in 10h overnight and around 0.2-0.3/h all on during daytime.
[Nexus 6  Original Android Development] Formhault:
Yeah, I think it's enough... you have to drag your finger across ~40% of the screen (about 5 centimeters) for it to register a "swipe to wake" gesture.
[Nexus 6  Original Android Development] flar2:
Something kept your phone awake for two hours. Get Better Battery STats and try to figure out what it is.

I would not go down to one core on suspend. It will keep the phone awake longer, just leave it on the default.

Your screen on battery usage is very good.
[Nexus 6  Original Android Development] Formhault:
Why, would that be a factor? I gave up on Wake Gestures, now relying in totality on EX Kernel Manager (which does provide control over S2W functionality, so...).

---------- Post added at 08:05 PM ---------- Previous post was at 08:04 PM ----------

That is exactly why s2w is superior to dt2w. The chances of you waking the screen by mistake are drastically reduced.

---------- Post added at 08:09 PM ---------- Previous post was at 08:05 PM ----------

Could be. There are times when, with the phone laying flat on the table, if I try to wake it up (by gestures / power button) and check a message real quick, the touchscreen would act funky (say... impossible to slide up the lockscreen in order to unlock it, lol) But that's extremely rare. So yeah... there could be something in the touchscreen itself that is funky or I dunno. Anyway, the current state that s2w is in is a huuuuuuuuge step, especially for me... I've relied on the power button for the last 4 months, so... :silly:

To be clear, are you inferring that the potential sudden static electricity discharges could affect the s2w functionality... or provoke the random secondary reboot?
[Nexus 6  Original Android Development] flar2:
The wake gestures app has just never worked that great on this phone.

On my other phones, it wakes up instantly, pocket detection works great, it's awesome. But on this phone, there is a delay for the screen to come on, sometimes it doesn't register, and the pocket detection causes watchdog bites, no idea why.
[Nexus 6  Original Android Development] Formhault:
Ah, I see. I thought there's additional functionality that the Wake Gestures app adds (something underneath the surface... but that'd be nonsense, the kernel itself already does that :silly: ).

Yeah, I've noticed that pocket detection => delay.

Watchdog bites? What exactly do you mean by that? I've seen this term being used before, so I'm curious.

Also, check out my previous post... again. It's longer now :silly:

Oh and thank you for chiming in, always nice to hear back from a dev :)
[Nexus 6  Original Android Development] mattmtx:
This in usage:

And this in wakelocks:
[Nexus 6  Original Android Development] flar2:
The app does add functionality, it allows you to customize what happens for each gesture. Without the app, the gestures simply turn on the screen.

I'm not sure how to read that app, but I see stuff like google accounts, some kind of media player, and one of the motion sensors. Were you playing music? That would explain it. Also, ambient display might be a factor if you're using that. Were you on mobile data at all? Mine can drain quickly on mobile, depending on the signal.

In any case, your stats aren't that bad, I wouldn't worry too much, especially if you were playing music, or on mobile data.
[Nexus 6  Original Android Development] Formhault:
Oh, right. No, I meant besides that... so nevermind :silly: