yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] dEris:
Awesome

[DEVICE:NEXUS⁴]❌[ROM:BEERGANG]❌[KERNEL:AK]​
[Nexus 4 Android Development] Kocai:
Subscribed! Thank you for continuing the m_plus kernel [MENTION=4303511]thracemerin[/MENTION]
[Nexus 4 Android Development] azrash:
Feels like home again. Thanks thracemerin!
[Nexus 4 Android Development] saibz:
I'm using this right now, on KRT16O build. No problems with WiFi so far. :good:
[Nexus 4 Android Development] thracemerin:
Good to know, thanks!
[Nexus 4 Android Development] Ace42:
Long time no see! :)

Sent with Virtue
[Nexus 4 Android Development] karanrajpal14:
Finally! Was waiting for this :D thanks!
[Nexus 4 Android Development] azrash:
Nice to see familiar names here. Loyal user base here :P
[Nexus 4 Android Development] Spec-Chum:
Awesome, was using your kernel on 4.3, now on psx 4.4 so looking forward to trying this on that :)
[Nexus 4 Android Development] ciprianruse88:
One of the best kernels!Keep up the good work!:thumbup:
[Nexus 4 Android Development] thracemerin:
Keeping in mind the design principles of the previous m_plus versions (4.2.x and 4.3), what features would you guys like to see for 4.4?
[Nexus 4 Android Development] SkyBeam2048:
Undervolting (down to 600mV)

Dynamic fsync

Hotplug (control max. online CPUs)

Not sure if this is a feature which can be implemented in kernel. But I hate the Android default brightness control. You have to decide whether you use auto-brightness or manual one. I would like to see some control over auto-brightness as well. For example in many light conditions I would like to use a lower brightness than what is provided by auto-brightness. But when I go for manual brightness then I cannot even find the brightness control when I step out into the sunlight. So actually I would prefer to have auto-brightness but control the lower and upper limits and adjust the brightness adjustment sensitivity. Of course this would require also a change on the ROM since the ROM controls will disable brightness control when auto-brightness is active. But perhaps tuning the algorithm variables could be done via kernel variables or by very simple app then.

I just migrated to KRT16S factory image and looking forward to test this kernel.

These are just the features I would love most to see. Keep up the great work! Many thanks to you and also all the other kernel hackers allowing us to fine-tune where the Google default stops.
[Nexus 4 Android Development] thracemerin:
The 3 things you listed are things that make my list too.

As far as the auto-brightness, this is mostly handled by the OS, though I have noticed that stratosk did some tweaks to the kernel side driver that could result in better auto-brightness, I'll look into that one.
[Nexus 4 Android Development] ciprianruse88:
Don't forget gamma hack(faux's) and fauxsound and keep it ass minimal as possible just like on 4.3 :thumbup:
[Nexus 4 Android Development] zorginho:
Uh OK dunno that mpdecision is linked to stock thermal, so ur kernel is already perfect as is :)

Inviato dal mio Nexus 4 utilizzando Tapatalk
[Nexus 4 Android Development] ihancioglu:
Hi, [MENTION=4303511]thracemerin[/MENTION]

I would like to change governor to interactive to save a bit more battery. Is it possible to do with mpdecision? There are some configs about interactive /sys/devices/system/cpu/cpufreq/interactive. Are that changes affect the performance with mpdecision?

Thanks,
[Nexus 4 Android Development] thracemerin:
There should be no problem switching to interactive or changing the interactive tunables while running mpdecision.
[Nexus 4 Android Development] ihancioglu:
What is the best method to change it for you? I tried to change with script on init.d folder. Some of the cores does not change. I think they were not online at that moment. I think I will change on init.mako.rc file. What do you suggest?
[Nexus 4 Android Development] thracemerin:
I don't think you can use the init.mako.rc file because it is stored in the ramdisk and will be overwritten by the one inside the ramdisk on boot, I'm not certain what the best method is to set those parameters for offline cores, especially since they will likely lose those settings when they go offline again, probably trickster or another system tuning app would be able to handle this best since it remains in memory and can set the settings when a core goes online.
[Nexus 4 Android Development] azrash:
Thrace, just out of curiosity, what ROM is your current daily driver now? For the N4
[Nexus 4 Android Development] thracemerin:
Stock, I make all my mods using Xposed now.
[Nexus 4 Android Development] zorginho:
hey [MENTION=4303511]thracemerin[/MENTION]

what means rd in that kernel?

m_plus-0.1.1_rd.zip
[Nexus 4 Android Development] thracemerin:
It includes the entire modified stock ramdisk for those with pure stock that want init.d support.
[Nexus 4 Android Development] thracemerin:
New Version! :D

0.1.2 Release:

Changes:

GPU Governor default back to ondemand (simple is still available, see post 2 for how to switch with scripts)

Sweep2Wake, Doubletap2wake, Sweep2sleep only

kexec hardboot for multiROM support

Happy flashing! :victory:

Anykernel version available now, if you need init.d support flash the 0.1.1 rd version then this.

CM version shortly.
[Nexus 4 Android Development] thracemerin:
Shortly meaning now :victory:
[Nexus 4 Android Development] themike10452:
hit me

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Android Development] thracemerin:
Downloads section :D
[Nexus 4 Android Development] themike10452:
oh yess DT2W

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Android Development] ihancioglu:
Thanks for the update,

Are you planning to implement below function?

- eco mode option s2s/s2w/dt2w

with this feature you can enable an option for save battery.

/sys/module/input_core/parameters/pwrkey_suspend pwrkey_suspend = Y or N

if yes when screen goes off without touch anything 2w is enabled otherwise if you use power button is disabled.

You can save your battery with this option on.

Then will work like touchwake alternative.

EDIT: Most of the time dt2w is not working on first double tab. Then works on second double tab. Do you experience this issue? Known bug?
[Nexus 4 Android Development] snak3ater:
Double tap problem is blessing in a way lol.. it'll prevent your phone screen turning on inside pocket :D

---------- Post added at 02:07 PM ---------- Previous post was at 02:05 PM ----------

Going to try this kernel for the first time.. Fingers crossed :thumbup:
[Nexus 4 Android Development] apatal:
Does the cm version also have mpdecision plus all of the features of the AOSP one? :)
[Nexus 4 Android Development] thracemerin:
Yup, they are identical except for the cm color correction patches.
[Nexus 4 Android Development] mjehan:
Changing GPU governor to ondemand reduces the lag but it is still there and very noticeable. Just try and play Tempel run 2 and you will See it.
[Nexus 4 Android Development] thracemerin:
Hmm....I would assume this means it lags on stock as well since I didn't do anything that would have reduced the performance vs stock.
[Nexus 4 Android Development] thracemerin:
I used showp1984's new sw2/dt2w from hammerhead, I don't believe the eco mode is implemented in that version, but the code was rewritten and shouldn't have a tremendous impact on battery life.

I noticed occasionally dt2w doesn't work on the first try, but I assumed that it was because it tapped too slowly or too quickly for it to register.
[Nexus 4 Android Development] thracemerin:
Upon further testing, it works much better if you tap the center than it does if you tap the edges, I think this is intentional.
[Nexus 4 Android Development] thracemerin:
It also appears that [MENTION=3750240]stratosk[/MENTION] wrote a different version of dt2w that works a little better, but I don't think its compatible with s2w so I'd have to get rid of s2w and s2s to add that, I'm not sure it's worth it.
[Nexus 4 Android Development] themike10452:
i think no one uses s2w and dt2w at the same time. i like dt2w more than s2w personally. maybe u should make a poll for that.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by Piasek v7 CM Linux 3.4.75 kernel.
[Nexus 4 Android Development] thracemerin:
People are welcome to weigh in on the issue :D
[Nexus 4 Android Development] DontPushButtons:
If dt2w works well enough, I assume battery drain is equal to s2w/s2s anyway. With most roms offering ways to sleep without using the power button (quick settings, Nav ring, long press Nav buttons, etc..) s2s really isn't necessary.

I don't really use either of them, but if I had my pick, double tap is the winner. I do miss it since returning my gpad. Just finally got out of the habit of tapping on my n4 to no avail, though ;)
[Nexus 4 Android Development] thracemerin:
Ok, let me put it this way, assuming the version of dt2w that stratosk implemented works better than the current one that I have implemented (showp's version) would there be anyone who would desperately miss s2w or s2s?
[Nexus 4 Android Development] themike10452:
Go for strarosk's new implementation :D

one question, is it normal that all 4 cores are online at all times? o.O There's no custom hotplug or MP-decision.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by m_plus 0.1.2_CM Linux 3.4.0 kernel.
[Nexus 4 Android Development] thracemerin:
Nope, if you flashed the anykernel version or cm version coming from a kernel that has mpdecision disabled in the ramdisk will cause that problem, dirty flash your ROM first to get mpdecision back, then flash the kernel again should fix it right up.
[Nexus 4 Android Development] themike10452:
oh okay thanks for clearing it up.

Sent using my nexus⁴ running crDroid Simple 4.4.2 (Dalvik) powered by m_plus 0.1.2_CM Linux 3.4.0 kernel.
[Nexus 4 Android Development] :
is this compatible with cm11 M2?
[Nexus 4 Android Development] thracemerin:
the _cm version should be, I tested it on last nights nightly and it was working fine.
[Nexus 4 Android Development] ak:
Because this feature isnt present into showp1984 original code ... But from flar2 kernel

ak
[Nexus 4 Android Development] azrash:
I am too used to s2s. Already used the nav ring on cm for app dialer and another app. One plus of the s2s is the position of it, at the nav bar, makes it easier for the thumb to reach.

I'll give dt2w a try and maybe update to the latest CM that has dt2s and see how that combo goes.
[Nexus 4 Android Development] cmajetic:
d2ts in statusbar is a great feature and already included in most ROMs so I vote for stratosk d2tw.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] thracemerin:
I thought about it a bit and read some of the discussion in stratosk's thread and I think I will let him work on his implementation a little more, people are saying the drain is massive and reporting some other minor problems that I'm not seeing with the current one. People are still welcome to comment with their opinion but I'm going to put this particular option on hold for the time being to see how it progresses a bit more.
[Nexus 4 Android Development] ihancioglu:
I was tested stratosk dt2w last night. Battery drain was %6. I just installed your kernel and activate the dt2w. Exactly the same setup. I will let you know how the drain on your kernel.
[Nexus 4 Android Development] flash5000:
Thanks for adding kexec patches, I really appreciate that! :)
[Nexus 4 Android Development] ihancioglu:
Hi,

Battery drain over the night with DT2W is %4 on your krnel. So this is a bit battery friendly over the semaphore's DT2W.
[Nexus 4 Android Development] thracemerin:
I'm getting about 1.3% idle drain per hour with dt2w on and about 1% idle drain with it off which is pretty consistent with what I expected.
[Nexus 4 Android Development] azrash:
Thrace, to enable s2s only, s2w need to be enabled as per the documentation you placed in first page.

However on my end, I can still use s2w.

My userinit.d script

#s2w

echo 1 > /sys/android_touch/sweep2wake

#dt2w

echo 1 > /sys/android_touch/doubletap2wake

#s2s only (s2w must be enabled)

echo 1 > /sys/android_touch/s2w_s2sonly
[Nexus 4 Android Development] thracemerin:
Does s2s only work without s2w enabled? I was just following the instructions I read on this.
[Nexus 4 Android Development] azrash:
I tried enabling s2s only, leaving s2w to off but s2s doesn't work.

Not a big issue but I find dt2w + s2s works great, so s2w is not being used on my end.

I still use s2s since dt2s only works when the screen is unlocked. For CM at least.
[Nexus 4 Android Development] thracemerin:
I'll check into it.
[Nexus 4 Android Development] snak3ater:
I just tested it...Enabled s2s only and dt2w in k-control..this combination works..

Tried doing the same thing in Trickster but the app reverts my settings..It's an issue with trickster Mod app
[Nexus 4 Android Development] azrash:
And s2w wont activate the screen?

Thing is, I am not using trickster to set it up.

I made the settings via userinit.d script as per the documentation.

Do you mind enabling s2s only and dt2w in K control again, and check the values of the files in /sys/android_touch, which ones are 1 and which ones are 0.

Thanks
[Nexus 4 Android Development] snak3ater:
Yes...S2w does not wake up the screen...

Values are like this:

s2w_s2sonly 1

sweep2wake 1

Set both the values as 1 and you will get your desired result ie s2s feature only..

Opps:As soon as i turned on dt2w..now s2w is working as well :p

s2s alone works fine but when dt2w is turned on,s2w starts working by itself
[Nexus 4 Android Development] thracemerin:
Yeah, seems to be a glitch with the dt2w code that causes s2w to be activated automatically, I'll contact [MENTION=4195844]show-p1984[/MENTION] about it and see if he has a solution.
[Nexus 4 Android Development] show-p1984:
Nope.

Cherry-pick: https://github.com/showp1984/bricked-hammerhead/commit/43087424a5ace389e5419ae17565d4ea0a6e971c

Should apply cleanly.
[Nexus 4 Android Development] thracemerin:
Thanks!
[Nexus 4 Android Development] thracemerin:
New Version 0.1.3 released!

Changes

Fix for s2w being active with s2sonly and dt2w (thanks to show-p1984)

Happy Flashing! :victory:
[Nexus 4 Android Development] Serial Kazama:
Best Kernel so far. Thx U very much.

Greetings from Germany.
[Nexus 4 Android Development] zorginho:
hey thrace maybe u alreadu know but stratosk has coded a new dt2w, and now he is testing it on a test build, but seems to work very good, better than others :)
[Nexus 4 Android Development] thracemerin:
Yeah, I follow his thread fairly regularly especially now that he's working on dt2w. I'm not sure that I would say it's better than others yet since people are still reporting some of the same issues that have been present in most of the s2w/dt2w implementations that exist, but I am keeping a close eye on developments to see how it comes along.
[Nexus 4 Android Development] Lazy Rich:
I'll just leave this here... simply amazing battery.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] IndDoc:
Is this on 3G?
[Nexus 4 Android Development] Lazy Rich:
4 hours 3G, rest was on wifi.

Gesendet von meinem Nexus 4 mit Tapatalk
[Nexus 4 Android Development] kridster:
Hey tracemerin,

I'm using CM on my Nexus 4 and followed the according threads here on XDA passively but regularly. You were always very polite and gave reasonable answers for sometimes even stupid questions ;).

I wanted to test the dt2w feature and seeing that you are in the kernel development business too, I thought I'll try yours!

I flashed the current version yesterday on top of the CM nightly from Jan 26th. Today I experience a weird issue, I never had before and only a reboot could solve:

Opening menus by swiping from the right or left border of the screen into the middle didn't work anymore. For instance, I'm was using the AOSP browser with the fast control feature and suddenly, I couldn't open the menu anymore. The same thing happened with every app, where the menu can be triggered from the edge of the screen, like Play Store or Trickster Mod..

The only settings I altered were the d2tw feature, some but not too heavy uv (use these settings in the past) and different colour settings.

This never happened to me before and seems totally weird, but maybe there were some technical complications.

Thanks!
[Nexus 4 Android Development] themike10452:
This is a known bug in touch wake driver (Screen edges unresponsive). The solution is to disable any DT2W/S2W, turn off the screen, then re-enable it. It seems Mr. Stratos - the dev of Semaphore kernel - came out with a solution to this problem, and I guess all devs will adopt his solution as soon as it's reported working by all users (Reset touch drivers on wake).

Cheers.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.4 Linux 3.4.77 kernel.
[Nexus 4 Android Development] kridster:
That was it. It happens to me quite often, guess I'm not the only one. Hopefully this feature will be polished :)

Besides from that it's a great battery friendly kernel!
[Nexus 4 Android Development] themike10452:
Yep, the problem is solved, Semaphore 2.0.5 is running great with no touch problems at all, wake from first double tap always, and screen doesn't freeze on boot if you don't unlock the screen, no screen edge unresponsiveness. Just great. I think it's time for all devs to adopt his masterpiece of code.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Android Development] thracemerin:
People are still reporting unresponsive screen in stratosk's implementation, so I'm still waiting to see how this plays out.

In other news, I have some other updates I'm going to push this weekend.
[Nexus 4 Android Development] themike10452:
Personally I am absolutely satisfied with stratosk's work on his latest kernel, no problems whatsoever, nor touch nor performance issues.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) powered by Semaphore 2.0.5 Linux 3.4.78 kernel.
[Nexus 4 Android Development] thracemerin:
Seems isolated, might be other mods that are causing it.
[Nexus 4 Android Development] kridster:
Running CM11, I'm having problems frome time to time. One time I could unlock the screen but touchscreen didn't response after that. Sometimes d2tw doesn't work so I have to wake up the device the old fashioned way.

All in all it's an improvement from before, but not the perfect solution, at least for my setup.

How is your development evolving thracemerin? :D
[Nexus 4 Android Development] thracemerin:
I added a bunch of compile time improvements and caused a nasty bootloop issue, I'm trying to track it now, but the release is delayed a couple of days as a result.
[Nexus 4 Android Development] mjehan:
how is the development coming along ?
[Nexus 4 Android Development] thracemerin:
I've been extremely busy, but I tracked down the issues I was having and I'm going to add the camera crash patch that was talked about in the Semaphore thread, just need to do a little final testing on the local version and I'll get it out ASAP. Sorry for the delay, real life is kicking my butt at the moment.
[Nexus 4 Android Development] ak:
I want to break a lance for shop1984 s2w implemented into my kernel:

- double tap dont work always = yes true but sweep2wake work always good

- screen freeze on boot = the situation is created by app used for control kernel and features at boot, if you use initd script the problem doesn't exist

- screen edge unresponsiveness = this is resolved long time ago

Some code of Semaphore 2w is taken from showp implementation, so in my opinion both are great.

Let's avoid spreading incorrect information.

thanks
[Nexus 4 Android Development] themike10452:
It was just an opinion, I am still using showp's t2w with no problems, only the edge unresponsiveness problem comes rarely. And I'm only getting 0.5%/h total drain with screen off, which is awesome.

Sent using my nexus⁴ running Purity 4.4.2 (Dalvik) + T.A.R.D.I.S powered by HellsDoctor R17 Linux 3.4.79 kernel.
[Nexus 4 Android Development] mjehan:
any update ?
[Nexus 4 Android Development] mjehan:
Please include the new GPU drivers in the next version.

Source : http://xdaforums.com/nexus-4/general/qualcomm-adreno-gpu-binaries-t2667759
[Nexus 4 Android Development] azrash:
Hey thracemerin

Will 0.1.3 works fine with CM M4?

From the release note in the CM blog, there is this

Performance – Speed up booting on multi-core devices

Is this kernel side or ROM side?

Thanks
[Nexus 4 Android Development] thracemerin:
I'm not sure, I will look into it, I would assume its on the ROM side, they rarely make kernel changes.
[Nexus 4 Android Development] snak3ater:
This is rom related

Sent from someone else's Nexus 4
[Nexus 4 Android Development] mjehan:
is the kernel developement dead ?
[Nexus 4 Android Development] DontPushButtons:
Actually haven't seen [MENTION=4303511]thracemerin[/MENTION] post anywhere as of late. Maybe moved on to a new device? Hope the Motley curse didn't get him :(
[Nexus 4 Android Development] azrash:
Hi guys, I am getting some random reboots with CM M6. Anyone facing the same issue? Been off xda for a while now. Not sure whether there are kernel related changes that happened recently.
[Nexus 4 Android Development] thracemerin:
I think I'll just add the _motley interface which is built upon the faux interface so both should work, I don't think I'll add other interfaces.
[Nexus 4 Android Development] ciprianruse88:
Cool :thumbup: Waiting for update :cool:
[Nexus 4 Android Development] azrash:
Is it possible to add the s2w and s2s that you implemented before? From my experience it works better than using touch control that tends to freeze the phone a lot. I'll get a freeze maybe once or twice a month with your previous kernel but that is much much better than using TC.

Oh and I forgot to report this, with the previous 4.2 kernel, I had a what I assumed was data corruption that happened twice in a few months. Had to do a factory reset otherwise it stuck at bootloop.

Turned the dynamic f sync off, and it never happened again, well so far at least. So perhaps it is best to set dynamic fsync off, by default? And maintain the stock fsync setting by default.

Thanks again, really enjoyed using this kernel. Lean and fast.
[Nexus 4 Android Development] thracemerin:
I was thinking of adding double tap to wake, similar to the LG G2's knock on, but s2w/s2s is also possible.

Using anything other than the stock fsync settings adds a slight risk of data corruption in exchange for a little speed, I've never personally had anything bad happen, but the main risk for this occurs when your device crashes or freezes during file read/write operations. Problems should be extremely rare, but if you're worried about it you can always disable dynamic fsync to avoid the risk.
[Nexus 4 Android Development] apatal:
Been waiting for this too. Thanks for sharing. As for feature request, I can live with it as close to stock as possible, but if you can throw in every optimization you can think of in there, I would be happy with that. In fact, just put in optimizations from faux (not the crazy intelli-stuffs). :)
[Nexus 4 Android Development] thracemerin:
Test 2 is live (staying with boot.img format only until we go beta)

Added Undervolt Support

Added _motley and faux123 gamma interfaces

Happy Flashing! :victory:

Note: since these are packed with the stock boot.img including ramdisk they may be incompatible with ROMs with modified ramdisks, I will be going beta once a few more features get back in and at that point I will return to using anykernel format.
[Nexus 4 Android Development] snak3ater:
double tap to wake or s2w/s2s..Any one of these is fine..I hope this feature gets added soon :fingers-crossed:

PS:Testing your kernel now :)