yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Android Development] zaclimon:
Unless your device is the nexus 6, nope.
[Nexus 4 Android Development] nellorocca:
I don't have ambient display but I've turned off dt2w and my problem seems solved.
[Nexus 4 Android Development] nick2503:
So CM 12 on Nexus 4 does have ambient display or not?

Because I cannot find the option of ambient display in the settings hence I have not enabled it.

My DT2W feature is on & also sometimes the screen doesn't respond & all what I can do is reboot!
[Nexus 4 Android Development] TheDarkDefender:
Ok. Cool. I read somewhere around here that might be related to ambient display. Also, I don't use d2w so I don't know.
[Nexus 4 Android Development] MtG92:
1. No, it does not.

2. It may just be a bug with the dt2w in this particular implementation, but [MENTION=4217103]zaclimon[/MENTION] might know better than me...
[Nexus 4 Android Development] zaclimon:
Looks like it is a bug in this particular implementation. The thing is, I'm always surprised at how you're the first to have those problems.

Have you reverted to stock and tried again to see if it was working?

Envoyé de mon Nexus 4 en utilisant Tapatalk
[Nexus 4 Android Development] dragos281993:
I see that others had this dt2w issue too. I'm on CM12 + this kernel right here (215.2 CM), and even if I have dt2w on, the screen is unresponsive sometimes. The CPU+GPU are not OClocked or UClocked, and I also left the voltages untouched, so I'm using the kernel as is. The only tweak is the screen profile, which is Obsanity-Amoled, but I don't believe this has anything to do with the touchscreen. Is there anything to do about the dt2w feature? I mean, to change something or do anything to make it work all the time?
[Nexus 4 Android Development] g33k0 b3lk0w:
Hello, can you just write down your settings for kernel and which app did you use for controling the kernel to get that much SoT, I'm also looking for best battery life,currently I'm using nash kernel with euphoria rom
[Nexus 4 Android Development] GorfDroid:
Sure.

I am on Resurrection Remix ROM.

I use both trickster mod and synapse.

Trickster mod for the main settings and synapse for gamma, sound profiles, exponential back light and selinux settings. I underclocked my CPU and GPU as well with no noticeable difference in performance.

Trickster mod:

TCP: Westwood

I/O: deadline @ 512

CPU: min: 192k, max: 1242k

GOVERNOR: interactive, with these settings:

above_highspeed_delay - 20000 702000:60000 1026000:150000

boost - 0

boostpulse_duration - 80000

go_highspeed_load - 99

hispeed_freq - 384000

io_is_busy - 0

min_sample_time - 40000

target_loads - 98 384000:40 702000:80 1026000:95

timer_rate - 30000

timer_slack - 80000

Fsync off.

GPU: ondemand @ 320

Synapse:

Gamma profile: obsanity_amoled

Linear/exponential: unchecked

Headset profile: quality

Fast charge: enable @ 1500 mA

Selinux: permissive.

I am also using RAM Manager with minfrees set to "hard multitasking".

I am using ES task manager to disable some programs from starting up and Greenify as well.

Hope this helps.

---------- Post added at 03:24 PM ---------- Previous post was at 03:20 PM ----------

Woops I made I mistake with those Governor settings.

Set high_speed_freq to 192k and set input_boost_freq to 918k.
[Nexus 4 Android Development] insigma28:
I can't get synapse on this kernel any idea Guy's?
[Nexus 4 Android Development] dragos281993:
After you flash the kernel, flash UKM and do a cache+dalvik wipe. Try this, it's made by [MENTION=4914494]aviz1911[/MENTION]
[Nexus 4 Android Development] yochananmarqos:
For those who might like more info before flashing a random file, it's a modified version of the Universal Kernel Manager with dt2w tunables. Wiping cache & dalvik is not necessary.
[Nexus 4 Android Development] dragos281993:
It is necessary. If you flash the kernel then the UKM right after.

Edit: apparently it's not necessary but I do it anyway just to make sure I don't get any problems (like FCs, which I had).
[Nexus 4 Android Development] aviz1911:
Nope, no need to wipe anything.
[Nexus 4 Android Development] dragos281993:
Well, I've had a few FCs of the system ui (or something like that) and also "Crossy road" was having the same issue and I couldn't play it, so I had to wipe the cache partitions which stopped the FCs. I assume the wipe stopped the FCs unless I did something else without knowing it, and I thought the wipe was the one that did the trick.

Anyways, every time I flash a new kernel, I wipe the cache partitions just in case.
[Nexus 4 Android Development] Dor-b:
Hi,

Never flashed a kernel before, do i just flash the zip?

No need for wipe cache and dalvik?

Thanks
[Nexus 4 Android Development] TheDarkDefender:
No wipe needed. Flash and forget.

Cheers,

D
[Nexus 4 Android Development] ObihoernchenDE:
There will be an update today. Probably r216 [emoji106]

https://plus.google.com/106873500108976028532/posts/RrwbEGK9jCo
[Nexus 4 Android Development] coffeecore:
That is insane!

sent with my Nexus 4.
[Nexus 4 Android Development] zaclimon:
Don't worry, I'll be here to update it. :p

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] TheDarkDefender:
Don't worry, I'll be nagging [MENTION=4217103]zaclimon[/MENTION] on hangouts until he updates [emoji14] lol
[Nexus 4 Android Development] kol1124:
There is new test version! ;)
[Nexus 4 Android Development] MtG92:
Where?
[Nexus 4 Android Development] kol1124:
Here ;)

http://192.241.177.15/Nexus4/5.0/tests/
[Nexus 4 Android Development] zaclimon:
Official version is real go get it :p

http://xdaforums.com/showpost.php?p=58895368&postcount=58058

As for myself, I should get to work on it either Wednesday or Thursday. (Hard work week is coming full burst at me -.- )
[Nexus 4 Android Development] MtG92:
Hi [MENTION=4914494]aviz1911[/MENTION], I don't know if it's a very time consuming thing, but do you think you modify UKM 3.7 (new update) with the dt2w tunables? Thanks :)
[Nexus 4 Android Development] zaclimon:
Little sketch :p

SM-Franco: r216 calling for report.

Mako: What's the report?

SM-Franco: Here's what I've brought so far:

- Synced myself from the latest Franco's source (Conservative governor stuff, optimizations, msm_hsic_host...)

- Linux 3.4.106

- Updated my F2FS driver so I can be faster and more stable while you're using it.

- Auto-Compiled from the latest SM 4.9 toolchain

- Because there has been some changes in the ramdisk, it might be better for you to return back to your original rom's kernel before flashing me sir.

Mako: Alright let's do it, where can I find you?

SM-Franco: I'm already available on BasketBuild. I also called my cousin from CM and he's also ready.

Mako: Alright let's do this!!

Enjoy!! :)
[Nexus 4 Android Development] pompidoi:
Thanks for the update! Getting it now.
[Nexus 4 Android Development] haplo39:
buggy

just installed R216,

SDCARD dismounted and could not access it..

too many Force close on google play services even after reboot.

reflashed the previous kernel again..

ther is something wrong with this build!!!
[Nexus 4 Android Development] wong.izzat:
Yes. Me too. Coming from Litchi 14 Feb
[Nexus 4 Android Development] gharrrrrr:
Grab a log! Provide more info! Did you dirty flash ROM first or revert to stock kernel? What ROM? Log or gtfo!

PS: just installed AOSP version of this kernel after installing new simpleAOSP build and everything is working beautifully. Great work [MENTION=4217103]zaclimon[/MENTION]. Thanks for sharing these builds.
[Nexus 4 Android Development] jer_ying_fd:
Just curious but why is f2fs adopted by so few kernels? And there's only so little info regarding it on xda... (or I am just bad at searching)
[Nexus 4 Android Development] quentin2260:
Flash stock kernel then flash this kernel then wipe cache and dalvik. Always flash stock kernel if you have another custom kernel.
[Nexus 4 Android Development] dragos281993:
Any idea where to get the stock kernel from?
[Nexus 4 Android Development] TheDarkDefender:
Your rom.
[Nexus 4 Android Development] quentin2260:
Download official stock rom in zip format then flash boot.img that you can find in ZIP. Or wait i can upload boot.img in next hour
[Nexus 4 Android Development] yochananmarqos:
Nevermind
[Nexus 4 Android Development] dragos281993:
[MENTION=4778194]TheDarkDefender[/MENTION] , [MENTION=3337700]quentin2260[/MENTION] Nevermind. I flashed CM12 again, then this kernel right after, did I cache/dalvik cache wipe and everything works fine. But thanks anyway.
[Nexus 4 Android Development] gharrrrrr:
You can also use flashify app from play store to download and install stock kernels.
[Nexus 4 Android Development] coffeecore:
Just flash Google's latest firmware, then it all is fresh as****. Root it, flash ROM with gapps, reboot, let it settle, play with it, debloat it ;) and reboot after deleting system apps and after that reboot and flash kernel and maybe a mod, check out L Speed on xda. Thanks for this kernel, you rock!

sent with my Nexus 4.
[Nexus 4 Android Development] zaclimon:
Ahh true I forgot to tell, if you're using a custom rom, it may be better to flash the rom's kernel instead. The way I use to flash isn't "conventional" you did have issues when you flashed from stock kernel.

If you want to go technical, well anykernel installs the necessary modifications on top of the already existing ramdisk instead of overwriting it. Because CM's ramdisk is different than stock, if you try to flash SM-Franco while having a stock ramdisk, it will be normal that you'll get errors upon flashing SM-Franco.

There's a thread over here:

http://xdaforums.com/nexus-4/general/index-f2fs-roms-kernels-13-6-2014-t2728201

It contains outdated information but if you ever want to convert to f2fs, download the Multirom twrp, then format your /data partition to f2fs. It did the trick for me. :p

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] jer_ying_fd:
Tyvm m8!
[Nexus 4 Android Development] haplo39:
it worked. thanks. finally dt2w is working with full screen
[Nexus 4 Android Development] Maibol:
[MENTION=4217103]zaclimon[/MENTION] can i troll and ask for a feature ?

i gon troll [MENTION=1229225]aviz[/MENTION] kernel thread to be aware [MENTION=1229225]aviz[/MENTION] lol :p
[Nexus 4 Android Development] aviz1911:
**** you :p
[Nexus 4 Android Development] zaclimon:
Go ahead but I won't even reply. :p
[Nexus 4 Android Development] Maibol:
lol :D

can you add gpu oc :D lol i jump from both of you guys kernels from time to time and I'm hooked with your kernels that's the only i miss but don't worry guys is only a dumb request :p
[Nexus 4 Android Development] yochananmarqos:
Oops, nevermind. Thought he said CPU instead of GPU. Derp.
[Nexus 4 Android Development] jer_ying_fd:
Umm... The maximum gpu frequency is 400mhz which is the same as stock
[Nexus 4 Android Development] yochananmarqos:
Oh shoot, I'm sorry. You said GPU, not CPU. :silly:
[Nexus 4 Android Development] mdaamir1989:
Guys two quick questions,

1. I'm quite confused by the usage of the word stock here , To flash this kernel on top of a different(semaphore) kernel running Euphoria Rom , is it ok if i dirty flash the rom and flash this kernel ?

2. After flashing this kernel If the ROM(Euphoria) has an option to enable DT2W , hope i don't have to configure anything myself to get DT2W working as mentioned in the third post of the OP.

EDIT : Flashed the rom and the kernel ,everything works as expected.
[Nexus 4 Android Development] zaclimon:
1. In this case, I mean that the stock kernel is the pre-bundled kernel that comes with the rom. I understand that it may get confused with the official stock 5.0 and I'll modify my post to avoid any further confusion.

2. You can enable dt2w if the rom support a setting to enable it. That said, the methods on the 3rd post are for versatility because you can modify some of the options (for example the dt2w zone, disable it when you press the home button to sleep, etc)

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] emanuele1986:
Conservative is the default governor? I still having interactive ad default after the flash
[Nexus 4 Android Development] MtG92:
Nevermind
[Nexus 4 Android Development] zaclimon:
Please check the changelog post regarding this.
[Nexus 4 Android Development] mdaamir1989:
Nevermind
[Nexus 4 Android Development] coffeecore:
Installed UKM on latest build but when I install Synapse from Play Store and laugh the app there stands ERROR. I am not able to use Synapse, anyone who also use Synapse and can confirm this?
[Nexus 4 Android Development] xshallowgrave:
Does this kernel have the Faux gamma controls? I didn't see it listed under "Features".
[Nexus 4 Android Development] zaclimon:
No this feature isn't included. This is a kernel based off franco which is why it doesn't have the faux gamma control*.
[Nexus 4 Android Development] xshallowgrave:
Thank you! Do you know if this kernel is 4.4.4 compatible? I tried flashing it on my purity ROM but was unfortunately caught in a bootloop.
[Nexus 4 Android Development] yochananmarqos:
You'll need to use r213 for Kit Kat.
[Nexus 4 Android Development] xshallowgrave:
Ah okay, thank you kindly!
[Nexus 4 Android Development] mdaamir1989:
Is there anyway the 192 mhz frequency of deep sleep can be changed to be 384 Mhz ? When the phone is in deep sleep it doesn't wake up with DT2W , takes about 4-5 double taps on the screen to wake it up , and sometimes it doesn't even wake up.
[Nexus 4 Android Development] copong:
You can use the Franco kernel app to do that
[Nexus 4 Android Development] zaclimon:
Nope unless you make the modifications in the source. :P

Now that you speak about it, is there somebody that wants to have 384 MHZ instead of 192MHZ for deep sleep? (for the mentionned reason above) if there's a demand, I'll revert it to 384 so there won't be problems with DT2W anymore. I initially wanted to keep it this way because the device uses even less battery and using 384 MHZ while having 192 UC results in SOD's but looks like if some people really wants it, I'll get it back.
[Nexus 4 Android Development] CalculatedRisk:
I flashed this kernel and lost root, and fixed it by flashing the stock 4.4.4 boot.img and then reflashing this kernel and the latest SuperSU. Just wanted to say this in case anyone ever encounters the same issue in the future.
[Nexus 4 Android Development] ObihoernchenDE:
I vote for 384 MHz
[Nexus 4 Android Development] yochananmarqos:
If I remember somewhat correctly, one must flash SuperSU again after franco.Kernel due to Franco's ramdisk modifications. I might be completely off, I just remember there was something. I made it a habit now to flash one after the other to avoid issues.
[Nexus 4 Android Development] CalculatedRisk:
Hmm, I don't recall having to flash supersu after installing the original Franco, and I never faced any issues with root. However, when I installed this Kernel, I lost root and flashing supersu on top didn't fix it, I could only fix it by flashing the stock kernel, then installing this kernel followed by reinstalling supersu. It works great now and I look forward to testing it out :)
[Nexus 4 Android Development] gharrrrrr:
192mhz preferred here. Don't use dt2w (prefer the battery savings).
[Nexus 4 Android Development] dragos281993:
That would be a great idea. I mean, it's very annoying to have the DT2W feature activated, and still to have to use the power button cause the screen doesn't turn on even with 100 taps. My power button is a bit faulty, so when I press it to turn the screen on, sometimes the screen turns back off right away, so the DT2W is pretty indispensable for me. But probably not many people would want you to change the deep sleep frequency from 192 MHz to 384 MHz, so you could make a second version of your kernel so we can all be happy, if you wanted, obviously.
[Nexus 4 Android Development] WiwiPouPou:
No difference between 192 and 384 MHz over here, so keep it stock !
[Nexus 4 Android Development] dragos281993:
What do you mean "no difference"? Could you be more specific?
[Nexus 4 Android Development] WiwiPouPou:
Never seen any sensitive difference in battery usage over time, with any kernel. See for yourself, one of the best kernel batterywise is semaphore, which is closer to stock, with just UV options.

Really guys, in over a year, stock freqs have always been good, apps have a lot more to do with battery usage..
[Nexus 4 Android Development] dragos281993:
The whole "change the 192MHz to 384" thing was specifically to fix the DT2W bug, which consists of the screen being unresponsive due to a way to "deep sleep" mode of the device. Now you've still been very vague about the frequency you want to be kept, the 192 or 384 so I don't really know how to respond to this. You could refer to the 192MHz option as stock, if you're talking about the SaberMod Kernel, or you could refer to the 384 MHz step as stock, if you're talking about the original Lollipop kernel. I hope you support the 384 MHz frequency step.
[Nexus 4 Android Development] MtG92:
That is a very good point! I vote for the 384MHz step if it fixes the dt2w bug.
[Nexus 4 Android Development] WiwiPouPou:
384 MHz FTW !:good:
[Nexus 4 Android Development] zaclimon:
I heard ya everyone, I pushed r216.2 which restores the deep sleep frequency to 384 MHZ. I leave r216 here as well if somebody wants to keep the 192 MHZ deep sleep frequency but 384 MHZ will now be the default in future releases. It do helps a lot with DT2W but when it's deep sleeping hard, you may need 2-6 taps to get the screen to wake up. At this stage, I won't really complain about it lool.

Both versions are up.

Enjoy! :)
[Nexus 4 Android Development] jer_ying_fd:
Can I dirty flash this over the last build? Thx.
[Nexus 4 Android Development] zaclimon:
Yeah, nothing ramdisk wise has been changed. :)

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] quentin2260:
Fantastic kernel ! Thanks !

Only one question. Is it possible to add line in kernel settings for enable/disable DT2W in FKU ? it bothers me to have to use Trickster to enable this setting.
[Nexus 4 Android Development] mdaamir1989:
Im afraid it cant be added. Trickster is your best bet ... or you can create the config file as mentioned in OP and keep changing doubletap_to_wake=Y or doubletap_to_wake=N as and when required.
[Nexus 4 Android Development] zaclimon:
FKU doesn't act like synapse. It is an app that is coded solely by franco and only him can decide whether to add a line for it or not. (which in this case, I doubt he will add the option)

You can check the 3rd post, there are solutions in order to get DT2W enabled without using a 3rd party app.
[Nexus 4 Android Development] dragos281993:
Hey [MENTION=4217103]zaclimon[/MENTION] . I flashed the 216.2 build and I noticed that the frequencies are unchangeable. I mean, when I'm trying to set the minimum frequency to 384 MHz instead of 192, in Synapse, then tap "apply" and exit to make sure that everything applied correctly, the minimum freq is set to 192 MHz back again, when I restart the app. I found out about this when I had seen that my screen was still unresponsive, just like it was before with a previous build, so I assumed that the device was still going into that annoying SOD state again, which is caused by a lower frequency than 384 MHz, apparently, meaning that the CPU was still going under 384 MHZ

I hope you take a look into that,if you have time.

PS: I did a full wipe of my device to make sure the bug was truly there, and it was, unfortunately.
[Nexus 4 Android Development] zaclimon:
Hmm that's definitely strange, as for the frequencies not changing, I can't tell anything really. Have you flashed back to stock before flashing r216? Also I'm using FKU and my frequency is fine as far as I can see. Though you're the first person to tell me that you have an SOD related to the frequency. what's your cpu bin? Perhaps the frequency isn't stable for your device.
[Nexus 4 Android Development] dragos281993:
Just installed FKU. It seems that the minimum frequency stays at 384 MHz, just like I set it. Maybe it was an app related bug, and I'm referring to Synapse. Well, I'll use FKU for now. It also looks awesome. Thanks for replying so quick.
[Nexus 4 Android Development] coffeecore:
Use 384, you won't notice the difference in battery life, only the performance.

sent with my Google Nexus 4.
[Nexus 4 Android Development] dragos281993:
You didn't read the last few comments, it appears.

---------- Post added at 01:41 PM ---------- Previous post was at 01:26 PM ----------

@zaclimon , sorry to bother you again. Well I tried Trickster Mod not long ago, and it seems it has the same problem as Synapse, which means the minimum freq is stuck at 192 MHz. So the kernel is the problem, it appears cause the r216 build doesn't have this problem.

Why did I come to this "aspect" again ? Well, I've been using FKU for the fast few hours and the only thing it doesn't have, is a DT2W option. And I haven't found an alternative. I know I can simply navigate to .../lge_touch_core/parameters/" and manually activate it, but it's a pain in the *** to do it at every restart. I tried to create an init.d script to do my job for me, but no luck. Any suggestions?

Edit: the frequency is stuck on 192 MHz on every single kernel manager I try, so it's a kernel related bug. Is it possible that you delete the 192 MHz step from build r216.2?
[Nexus 4 Android Development] zaclimon:
I can confirm the issue using kernel auditor. Something in the ramdisk permissions that franco added to lock the permissions (Maybe it's due to the max freq always changing without any reason). Actually you can fix this issue in trickstermod. Go in the general section and disable the frequency block toggle. Your frequencies should work now.
[Nexus 4 Android Development] dragos281993:
Apparently, after disabling the freq locker, I noticed from the "Time in state" section (from "Info") that the 192 MHz step was still being used (counting the time in use). So, with the "Frequency lock" disabled, I chose 384 MHz as minimum frequency, then reactivated it again and it looks like it finally stays the way I like.

Thank you very much for wasting your time with me, buddy !!! You're the best.
[Nexus 4 Android Development] quentin2260:
Hello :)

Someone can explain me how to add init.d support with this kernel ?

Thank you

EDIT : init.d support added with term.init v3 method
[Nexus 4 Android Development] quentin2260:
Lastest Light Flow (paid) doesn't work with this kernel :crying:

It works with stock kernel.
[Nexus 4 Android Development] 350Rocket:
Light manager free works fine if that helps (most of the time anyways). Occasionally the stock colors show up instead of what you selected.

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

Okay haven't updated from r216 yet but mine seems to work fine set at 192 min and 1.7ghz Max. Does 192 actually not help battery life at all? My usage is too inconsistent to be able to notice if it helped or not but any improvement is helpful.

I notice a big difference in smoothness between stock max freq and using the highest 1.7ghz I think. No stability issues on my phone.
[Nexus 4 Android Development] AndyYan:
Seems my post had been deleted?

DT2W doesn't work here. R216.2+CM12 nightly, tried init.dt2w.sh (the only one that worked for me in r215.2), init.d and dt2w.conf, none works.

Sent from Google Nexus 4 @ CM12

[WARNING: XDA Premium 4.0.13+ lacks Signature function - do not update]
[Nexus 4 Android Development] Persechini:
My phone wasn't awakening from messages with 216-cm, but works fine with 216.2-cm

Enviado do meu Nexus 4
[Nexus 4 Android Development] zaclimon:
Have you flashed back from stock before flashing r216? I suppose using an app like trickster would make it work but since you don't want an app to control it, I may have to try it for myself.

Hmm looks like the 192mhz frequency isn't doing any good. Looks like I might have to drop it off it doesn't have any benefits for anybody.

Envoyé de mon Nexus 7 en utilisant Tapatalk
[Nexus 4 Android Development] 350Rocket:
Mine is awakening fine on r216 also version, set to 192mhz min with trickster. I don't know whether its saving battery or not but I know its using the frequency a lot.