yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] rearden_metal:
Try enabling S2W with DT2W. I think it's S2W that causes the problem. When I enable DT2W alone this is not an issue.

It's a shame because the sensitivity for double tap is noticeably better when S2W is also enabled. DT2W alone gets me about 70% success rate with double tap, but the DT2W/S2W combo gets me something like a 90-95% success rate (i.e. minimal failed attempts to wake the screen).

I'm thinking of just disabling it altogether, these in-call issues are terrible. I'm surprised it's not more of a discussed issue on this thread though.
[Nexus 6  Original Android Development] PhilDX:
did you guys try flar2's app to temporarily disable s2w during calls?

http://xdaforums.com/showthread.php?p=58561610
[Nexus 6  Original Android Development] rearden_metal:
Yes, I did. This is the app that I mentioned in the original post that was buggy. The app does what is advertised, i.e. it disables s2w during phone calls. But it also 50% of the time ends up disabling the screen altogether when it's off. While I'm on a call and the app is doing it's thing, I can't turn the screen back on to do anything (for instance if I want to convert to speakerphone or check something on Chrome, or even end the call).

From what I've learned it's difficult to include this implementation in the kernel, hence the app. I just wondered if I was alone in this problem or if anyone else has encountered it.
[Nexus 6  Original Android Development] semdoc:
Exactly. dt2w and s2w remain disabled after call. Need to be re-enabled.
[Nexus 6  Original Android Development] wrongway213:
+1 to the demand (using your word - obviously this is a request and not a demand) for kexec support for Multi-ROM.. I know you run stock so you don't have any use for it, but I imagine you would find it pretty cool in terms of what it is able to do from the perspective of someone who likes good programming - it's just what it sounds like, you can boot multiple ROMs at once - crackflashers don't have to enter recovery, backup, wipe, restore - we can just switch from ROM to ROM. For me, I am in a legal situation where I require call recording, so I need a stable CM ROM until I find an AOSP module or app to record calls. However, the ROM I run probably 70% of the time is AOSP. If I had a legal call to make I'd just switch ROMs, make the call, record it on CM, and then switch back to AOSP after hanging up. I hope that gives you a bit better idea of what it is and why users may want support for it - I could be wrong and be in the minority here in wanting to give Multi-ROM a go... that would quite surprise me, though :p

Edit: Just realized this made it sound like I just like, swap back into AOSP ROM from a CM one. No, that's where the kexec hardboot comes in. Instead of rebooting to recovery, backing up, booting another rom, etc, you just boot into Multi-ROM and load your other ROM right up. It's not magic as this post made it sound, just very convenient compared to normal TWRP options.
[Nexus 6  Original Android Development] old_fart:
Mr. [MENTION=3357040]Imoseyon[/MENTION] sir, the other genius kernel dev, [MENTION=4684315]flar2[/MENTION] has just expressed a kernel mystery.

http://xdaforums.com/showpost.php?p=59284579&postcount=2433

What are your thoughts ?

---------- Post added at 04:18 PM ---------- Previous post was at 04:07 PM ----------

I recommend this app.

https://play.google.com/store/apps/details?id=com.skvalex.callrecorder&hl=en
[Nexus 6  Original Android Development] wrongway213:
I considered it, but being a college student with a newborn to take care of I simply couldn't rationalize spending $10 on something I know for certain I can do for free if I look in the right place.
[Nexus 6  Original Android Development] buschris:
+1 for kexec support :)
[Nexus 6  Original Android Development] wrongway213:
I never thought I would ever get on XDA app to thank someone when I was over thanks limit for the day for a +1 post.. first time for everything I suppose. :p
[Nexus 6  Original Android Development] anthonyg45157:
Would like to try multirom! +1kexec I'll live without if not :thumbup::D
[Nexus 6  Original Android Development] Imoseyon:
Hmmm ok, I will look into it after 1.17, which should be this weekend.

Well, the problem is that I don't use gestures, so I don't really know what the issues are. Is there a single post that describes the issue - something I can reproduce?
[Nexus 6  Original Android Development] purian23:
I believe flar was mainly referring to his gestures app that he makes not being as friendly with the N6. Not a gesture issue itself within his or this kernel per say.

Basically with the sweep to wake gesture during a phone call it makes the screen either too sensitive and you accidentally hang up, or, it will go off and not wake back up properly. Not all of the time and depends on usage so this helps you none lol.
[Nexus 6  Original Android Development] Imoseyon:
I see so the people are using the gesture app to prevent the touchscreen from being active during calls but the app is unstable?
[Nexus 6  Original Android Development] wrongway213:
Indeed, it is perfect on all other phones but causes issues on the N6.
[Nexus 6  Original Android Development] purian23:
Actually that's the odd part. He makes an app to help with the s2w option that disables the gesture during a call. That app causes some issues at times if you ignore the call. Since it uses root it activates on ring and deactivates after, but if you're quick to dismiss something isn't happening quick enough and it causes issues.

The other app in reference above is a pure gestures app that you can use with the screen on or off and set up custom commands. Like I could set it to where I swipe left while playing music and my screen is off to change the track of my song., or swipe right and it unlocks my display. Then lastly if your display is on, swipe to open apps or put the phone to sleep. It's pretty neat but I believe flar is trying to figure out why it's finicky on the N6.
[Nexus 6  Original Android Development] s2d4:
Yeah, a legal case will cost more than the app 100 folds over.
[Nexus 6  Original Android Development] wrongway213:
Context is key. I see you didn't read my posts on this page and the last.
[Nexus 6  Original Android Development] poczynek:
Latest cm build has 'class path changes' which means that custom kernels aren't working. Any chance of a build with these changes? Thanks again!
[Nexus 6  Original Android Development] s2d4:
I actually did, just a different opinion to yours but that is fine. Feel free to read the dev's context which is in his thread and not here.
[Nexus 6  Original Android Development] purian23:
CM is consistent to say the least. Tailor and change it all for everyone else to have to change lol. They are cool, just headaches for some.
[Nexus 6  Original Android Development] akellar:
How are they not working? I'm using lean right now on a build with all latest commits.
[Nexus 6  Original Android Development] poczynek:
You're the only one!
[Nexus 6  Original Android Development] franciscofranco:
Can you link us the patch with the classpath changes? It would be helpful.
[Nexus 6  Original Android Development] wrongway213:
I believe this is what he was referring to, hope it helps http://review.cyanogenmod.org/#/c/90736/
[Nexus 6  Original Android Development] akellar:
Way to answer the question
[Nexus 6  Original Android Development] Imoseyon:
This may shed some light on progress so far: http://review.cyanogenmod.org/#/c/90732/

Edit: I may delay v1.17 to wait on the outcome of above.
[Nexus 6  Original Android Development] Imoseyon:
in-call s2w issues

Those of you with screen sensitivity issues while in-call with s2w enabled, give v1.16.7 a try?

It's in the test folder here: https://onedrive.live.com/?cid=F1ED4BADFEE3FC02&id=F1ED4BADFEE3FC02!440
[Nexus 6  Original Android Development] purian23:
For sure, thank you!

Edit: [MENTION=3357040]Imoseyon[/MENTION] dude it looks like we might have a fix or at least no issues lol. I tested in length on a call, with the speakerphone on, I turned off my display and dt2w & s2w worked perfectly!

I also tested in the normal mic without the speakerphone and it also worked fine. There seemed to be a slight delay in the proximity sensor but it did indeed wake up every time I took away from my face. Additionally on this test it seemed like there was no accidental button pushes or wakes when it was up to my face!

One small request if you could include s2s in lkconfig too :)

Thanks dude!!!
[Nexus 6  Original Android Development] old_fart:
Are there two kinds of deep sleep ? . . . Early ( just in ) sleep and then Late ( been dark for a while ) sleep . . . I know there is not supposed to be. . . . I'm just trying to make some sense to some inconsistencies ( for me - am not stock, euphoria and banks ) when I am double tapping and swiping . . . . . . . .
[Nexus 6  Original Android Development] wrongway213:
Do you have CPU boost enabled or disabled? Is mp-decision disabled? That inconsistency, the way you described it reminds me of touch boost or mp-decision spiking your freq on touch to make it feel snappier.. if you are repeatedly doing gestures for a battery test I would imagine you'd see wild inconsistency in freqs if CPU boost or mp-decision was enabled... could be wrong but the wording (mainly referring to it as inconsistencies, plural) just made me think of that.. hope it helps.
[Nexus 6  Original Android Development] Imoseyon:
Nice, yeah I put in some kernel code to disable s2w gestures during calls - hopefully this works for most people. As for s2s in lkconfig, I will look into it but won't make it in v1.17. Thanks for testing!
[Nexus 6  Original Android Development] Yank555:
Real call detection or proxy reading ? You caught my attention here :D

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Nexus 6  Original Android Development] poczynek:
Ah yes it's better during calls but I've lost my ability to sweep to wake. Can anyone confirm on this test build if sweep to wake is working for them?
[Nexus 6  Original Android Development] Imoseyon:
I did it via the qcom audio driver which is aware of voice call status. The problem with using proximity sensor, I think, is that it's going to be less reliable, especially since the sensor is so close to the screen that it may prevent legitimate sweep motions. I'm not sure how reliable my method is either though. ;)
[Nexus 6  Original Android Development] Imoseyon:
hmmm, that's concerning. What is the last app that was running when the screen went off? Did you have the dialer still running?
[Nexus 6  Original Android Development] poczynek:
Actually good point. Pretty sure it was working then I took a call and now not working. Yes so the dialer was running.

In data/data/leankernel my sweep2wake options are still there too.
[Nexus 6  Original Android Development] flar2:
Hope it works. I couldn't find a reliable hook in kernel.
[Nexus 6  Original Android Development] smclaughlin3:
what scales the cpu if mp decision is disabled then?

isnt their usually an alternative like hotplug etc....?
[Nexus 6  Original Android Development] Imoseyon:
Damn ok, so I think maybe when the dialer is still running s2w stays disabled. Let me play with this a bit. Those of you with this problem, see if s2w is re-enabled if you exit out of the dialer/phone app before turning the screen off?
[Nexus 6  Original Android Development] wrongway213:
Question may be above my pay grade - I am under the impression values defined in userspace and the InteractiveX governor itself are all that "scale" the cpu, quotes because not sure if that's the right term or if I'm even on the right track - just what I've been thinking this whole time.
[Nexus 6  Original Android Development] purian23:
I'm just gonna reply this is just good testing! Thanks dude. I'm sure it'll help the dev's do what they do best!
[Nexus 6  Original Android Development] rearden_metal:
Thanks bro. I must seem crazy lol. I'm coming from an M8 GPE and am spoiled. Haptic wake gestures on that thing were incredible.
[Nexus 6  Original Android Development] wrongway213:
Not crazy at all - you seem like someone who has either done testing before or someone who actually logically thought through what would be required to perform a successful test.. nothing crazy about doing something that requires a lot of time the right way at all. It's crazy to me to spend hours testing and not be thorough to be honest.. it's a waste of time. Appreciate the thorough testing as I am sure the kernel will get better in part because of it
[Nexus 6  Original Android Development] rearden_metal:
Nope, not a tester. Just someone who has been jailbreaking/rooting/bricking/unbricking phones forever it seems lol. Thinking about these sorts of problems is fun. XDA lurker for years, but only recently started to post. Wish I knew how to code. It amazes me how people know how to build ROMs and kernels and so forth. Keep doing what you guys do!
[Nexus 6  Original Android Development] Imoseyon:
Thanks [MENTION=5442991]rearden_metal[/MENTION] and [MENTION=1481114]purian23[/MENTION]. I'll see if there's something else I can do to make it behave better.
[Nexus 6  Original Android Development] jeromechrome1:
Does latest build have kexec-hardboot patch?

Sent from my Nexus 6
[Nexus 6  Original Android Development] wrongway213:
No, 1.17 won't either but it should hopefully be coming soon - Imoseyon said he will look into it after 1.17, as users expressed that it was a wanted feature.
[Nexus 6  Original Android Development] jeromechrome1:
Thanks for the heads up.

Sent from my Nexus 6
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=5442991]rearden_metal[/MENTION] and [MENTION=1481114]purian23[/MENTION] (and others who were testing s2w disable in-call), please try v1.16.8 in the same test folder?

--

kexec support will come - probably in v1.18. Haven't had a chance yet.
[Nexus 6  Original Android Development] mugendon:
Aaaaaaaand it's done :) Nothing to bother anymore for kerneldevs, the new alpha2 of xposed works with an enforcing kernel!
[Nexus 6  Original Android Development] datajosh:
Looks like 5.1 should be popping up any time now, I don't think the source has been pushed to AOSP yet though.

http://officialandroid.blogspot.com/2015/03/android-51-unwrapping-new-lollipop.html
[Nexus 6  Original Android Development] purian23:
Sorry for the delay IMO, I've had a killer headache today. On this test I think we went slightly backwards. I lost the abilities I had to wake using gestures while manually turning off my display in speakerphone mode.

The other test while not using speakerphone remained the same as before. If I manually turned off my display, no wake or tap gestures worked.

Ending as the same on my end with the prior test, once the call was over I gained my wake options back without needing to reset them for use.
[Nexus 6  Original Android Development] Imoseyon:
[MENTION=5442991]rearden_metal[/MENTION] and [MENTION=1481114]purian23[/MENTION], (and others with s2w iincall issues) how about v1.16.10? :)

I feel like we're probably pretty close by now. One thing to note is that there's maybe about a 2-3 sec delay before the gestures are re-enabled after call ends.

(feel free to reach out directly via imoseyon@gmail.com if you need faster response. thanks!)
[Nexus 6  Original Android Development] old_fart:
I am running the euphoria rom released yesterday with the newest banks gapps. For me, there was no delay after call end. Answer the call, raise it near my ugly mug, screen goes black. . dt2w and s2w both working fine before and after call. I hung up. . .

.

now I'll let the other end hang up and then let it go to sleep....

.

hmmm, sweeped about seven times . . . was thinking 'oh crap !' but then it woke . . .

The improved, hepatic dt2w seems very very solid.

.

removing it from my face, it stays dark for one second. I answered and then tapped power to go to sleep. Again it was seven ( more ! ) sweeps to wake it . . . Hmmm, the call did not end when I tapped power.

.

Again, I answered and then tapped power to go to sleep. Ah, dt2w was stubborn this time ! . . . And again the call did not end when I tapped power. . . YIKES ! . . . couldn't that make for an un-expected, big cell phone bill ? ? ?

.

Discovery ? ! . . . in lkconfig, option 2, I entered '4' for both . . . and then I display and it sez ( for option 2 ) - stock is off, haptic is '1' ( true ) and finally s2w is 15.

.

When it was in stubborn mode, the option 2 changed itself ( ergo needs a reset back, can you read the settings and save and write them back if power is tapped )which give it trouble ?

.

It put stock to 'auto' when stock was 'off' !

.

Also, on the desktop, if you tap power, it'll make a small click-click noise, announcing it's going down . . .

In a phone call, this noise ( state ) is missing . . .
[Nexus 6  Original Android Development] Imoseyon:
v1.17 is up.

Notable changes are automatic disabling of s2w gestures while in-call (still needs to be tested some more), and removal of unused kernel functionality for leaner kernel (and reduced memory footprint).

Full changelog: https://github.com/imoseyon/leanKernel-shamu/wiki/Lollipop-ChangeLog

As for kexec support, it's probably going to go into v2.0, since 5.1 release seems imminent. If you're interested in testing this, shoot me an email at imoseyon@gmail.com or PM me?
[Nexus 6  Original Android Development] Franzie3:
$20 on 5.1 releasing for Shamu tomorrow.thursday and VZW releasing Nexus 6 for retail on Thursday. bet they were waiting on that HD Voice :)
[Nexus 6  Original Android Development] Mervingio:
I got HD Voice on T-Mobile on 5.0.1 on iPv6 in some areas not all.
[Nexus 6  Original Android Development] old_fart:
Installed and then re-charged the batt. and then let it sleep.

But then ( just now ) I noticed it did not sleep. WLD says the SystemUI ( DozeService ) kept it awake. Hmm, a service for dozing that makes it stay awake. the programmers must be laughing the keesters off . . . Just a f.y.i. Troubleshooting now. A couple days ago I had that PlayService keeping it awake . . .
[Nexus 6  Original Android Development] Yank555:
Doze is Ambient display ;)

JP.

Sent from my Nexus 6 running Yank555.lu SlimLP 5.0.2 LRX22G on Yank555.lu v0.7 kernel.
[Nexus 6  Original Android Development] numerouknow:
http://xdaforums.com/showpost.php?p=59349423&postcount=6179

just when i was soaking in (croma+lk 1.16) bliss...i figured there's an update.
[Nexus 6  Original Android Development] TMYINC:
Man I missed your kernels man. Its been since the old thunderbolt days lol. Thanks again for your hard work!!!!!
[Nexus 6  Original Android Development] Mervingio:
[emoji6]
[Nexus 6  Original Android Development] boysetsfire:
Great job on this kernel, I only recently started using it, but have been getting really good performance and awesome battery life from the beginning with zero problems :) thank you [MENTION=3357040]Imoseyon[/MENTION]!

Inviato dal mio Nexus 6 utilizzando Tapatalk
[Nexus 6  Original Android Development] datajosh:
Seems like something is off with the s2w disabling, I was on a call today and the screen would not come on at all and I had to reboot my phone to end it.
[Nexus 6  Original Android Development] Imoseyon:
Yeah I think the jury is still out on this patch. Let me know if you (or others) run into similar issues during calls.
[Nexus 6  Original Android Development] flar2:
I used a different audio related trigger to do this earlier in the development of s2w and had the same problem. It mostly worked, but occasionally didn't. That's why I went the userspace route with an apk, which unfortunately fails in certain scenarios as well.

I just thought of a completely different way of attacking this problem, which I will try tonight when I get home.
[Nexus 6  Original Android Development] Imoseyon:
Yeah let me know what you find out. My patch works perfectly for me, but I think there maybe something about how the audio driver is used by different phones/carriers/dialers. I have a newer patch that's being tested by [MENTION=5442991]rearden_metal[/MENTION], but I'm not sure if that's perfect either.
[Nexus 6  Original Android Development] rub1k:
Haven't tried 1.17 yet (about to flash it now) but wanted to check whether anyone is experiencing issues with the screen not coming on when there's an incoming call?

Starting with updating/flashing 1.16 (encrypted/stock ROM/everything else), it seems to happen for almost every incoming call (I don't get many so it's hard to put a % on it)... phone rings and rings and rings but the screen never comes on so I can't answer it. Pretty damn strange...

Any logs/info I can provide to help troubleshoot?
[Nexus 6  Original Android Development] old_fart:
Same for me. But when I induced an error by "powering off" on a call . . . it stayed broken with bad behavior. . It went back to playing nice when I went into lkconfig, went into option two and set it again . . . Question : the kernel and the apps cannot handle a "power off" because it is a google bug . . . waiting for google to fix ?

.

When I induced an error state, your lkconfig showed a different setting in option two. The error changed the setting. I am certain on that. Repeatable.
[Nexus 6  Original Android Development] flar2:
This patch solves the main problem of accidental touches during phone calls.

https://github.com/flar2/shamu/commit/aa88f4e53e9b7a0e5f8c4821974234347cdfb4e7

While the panel is off, x coordinates are translated far offscreen, so you can't accidentally hit the dial pad or end the call with your chin.

Unfortunately, dt2w and s2w will still work during phone calls. Ideally, these should be disabled too, but at least with this method you should never get into a situation where the screen won't turn on, and you will never have to re-enable the wake gestures.

You can try it if you want, I'm not updating my kernel until the 5.1 source is released.
[Nexus 6  Original Android Development] wrongway213:
Thanks button alone just didn't convey the proper amount of being awesome that went into this post.
[Nexus 6  Original Android Development] Imoseyon:
Nice! I will play around with this patch as well.

Edit: incidentally [MENTION=5442991]rearden_metal[/MENTION] also found that my latest patch in 1.17.2 works for his use case finally. Now the question is which solution solves people's actual problems? I'm not entirely sure since I don't use gestures.

Does [MENTION=4684315]flar2[/MENTION]'s patch work for everyone since theoretically it prevents the call from ending accidentally when screen is off? Is that pretty much what folks want, or do we want to actually disable gestures while in-call? If former, I can revert my patch and add flar's. If latter, I can probably leave mine (and perhaps add flar's as well).
[Nexus 6  Original Android Development] rearden_metal:
The only possible downside to the flar2 patch as an isolated solution is that accidental haptic feedback can get annoying while on a call, even if it doesn't actually result in any significant consequence. This may not matter for those using nonhaptic gestures.

Thanks [MENTION=3357040]Imoseyon[/MENTION] and [MENTION=4684315]flar2[/MENTION] for the hard work!
[Nexus 6  Original Android Development] mugendon:
Never used a custom kernel before, so just one quick question:

Does imo have to start over with the 5.1 update and has to reimplement all the nice things like wakelock control, powersave mode etc.? Or is this "just" merging work?
[Nexus 6  Original Android Development] numerouknow:
though i am not an expert on this matter, i think it depends on what google has changed between 5.0 and 5.1.
[Nexus 6  Original Android Development] hellsgod:
Correct. On hammerhead it was easy to merge 5.1, because there weren't too much changes. Sometimes, if google changes a lot, its easier to start over from scratch.

hells
[Nexus 6  Original Android Development] knitler:
When LK drops for 5.1, then I'll look into re-rooting.

So far I am loving 5.1 though.