yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] xda890:
Any way to only start the timeout for d2tw when not charging (and then have d2tw active all the time when charging)?
[Nexus 5 Original Android Development] :
Hello ElementalX kernel is compatible with CM12?:)
[Nexus 5 Original Android Development] maortrol:
Yes...

http://xdaforums.com/showpost.php?p=58328837&postcount=15558
[Nexus 5 Original Android Development] magnamentis:
this is not the answer but a possible workaround, the question has been asked and i think it's possible with tasker.

however this is how i solved this for me, a very simple way however:

1. set the dt2w to be disabled by pressing the power button

2. set the screen to come on when connecting and/or disconnecting to/from charger

3. press power button to switch off display after disconnecting form charger and dt2w is off, just that you won't forget it that way

4. use the swipe to screen off feature to put display to sleep on charger, so dt2w will stay on while on charger, of course you can use that

....feature while on battery, but with a risk that you forget that dt2w is still on so you'll have a drain of 2%/h approximately, furhter there are more ways to

....switch the display off, there are launcher gestures like in nova launcher etc. and there are rom specific features like double tap status bar like in cm based roms.

while you could still set a time out to prevent dt2w staying active for x hours, i don't like that because my criteria like yours is to have dt2w on while on charger, full stop.

as mentioned above you can make a tasker script, i think somebody posted it in this thread not too far back (relative haha.. ) but for me the above does it.
[Nexus 5 Original Android Development] xda890:
Only "problem" with this is that I need to remember to use the power off button..... But maybe I'll try this and see how it goes.... :)
[Nexus 5 Original Android Development] magnamentis:
no then you did not fully understand, using my setup, the moment you disconnect from power source, the screen coms on into lockscreen and from there you simply have to press power button to have it off again and you're done, there is really nothing to forget that way, considering that we're talking a configuration where one is using dt2w on charger only.

go back to my 1st post on topic, i made the part bold now, because that's the point, to have a reminder to use that power button :)
[Nexus 5 Original Android Development] xda890:
Yes, I understood but I was talking about when the phone is not on the charger... :)

I am not used to switch off the screen, I always let the screen switch off by itself....
[Nexus 5 Original Android Development] BlueBliss:
Settings not saved after reboot?

Hey guys,

Emailed the dev, and was directed to ask in this thread!

Been using ElementalX and have changed settings through the app. Problem is, it seems like the settings are not being saved upon reboot. Is this a known bug? For example, I woke up this morning to my Max CPU Frequency reset to ~1500MHz, and the power button next to it disabled. Also, the voltages were all reset and the "Apply on Boot" box was unchecked.

Thanks!
[Nexus 5 Original Android Development] walpurgisnacht30:
Check your busybox first.
[Nexus 5 Original Android Development] Spinergy02:
So..the kernel that the app is listing as compatible with CM/CAF is not compatible with the full CAF version of CM12. Just wanted to put that out there before anyone else softbricks their phone like I did :)
[Nexus 5 Original Android Development] flar2:
If ypu want to use EX, then why not just use the regular version of cm? If you're using the caf version, then the main reason for choosing it would be for the caf kernel.
[Nexus 5 Original Android Development] Spinergy02:
EX gives the user more control over kernel operations that simply isn't offered with the default caf kernel on CM12. I've also found myfluxi's CM builds to be more stable overall, and your kernel as always been the icing on the cake. I meant no offense, just wanted to mention that the app is stating that the kernel was CAF compatible when it is not.
[Nexus 5 Original Android Development] magnamentis:
obviously you did not fully understand that the main difference between regular cm12 and caf cm12 is the kernel, so if you use another kernel than the one which comes with the caf cm12 rom you loose the difference to the regular cm12 which makes the use of that rom obsolete thus you can decide to use regualar cm12 + custom kernel or full caf without custom kernel. everything else does not make any sense and thus is not worth even one more post on the matter.

EDIT: sometimes one can simply not have both/all in this case you have to choose between customization or caf whereas the benefits of the caf stuff is a) not yet proven and b) reducing your choices and c) making a difference in fields where our high powered modern devices perform great without it. this is of course a subjective judgement. not claiming that this is valid for everyone, albeit certainly for most users.
[Nexus 5 Original Android Development] Spinergy02:
Myfluxi's builds are not simply base cm12 with a caf kernel.

Edit: I'm sorry for assuming that what was marked as the ElementalX CAF Kernel in the app was, in fact, NOT a CAF kernel.
[Nexus 5 Original Android Development] magnamentis:
you're not reading carefully. i wrote and [MENTION=4684315]flar2[/MENTION] wrote that " the main difference " is what we said. this excludes the term only. so nobody said only, just mainly. so further explanations would ask for a few words which i just gave up using here. make your choice, the choice is yours but then when we make choices we have to live with the downsides. why should he make a kernel for one subrom that is used by a few people only. then it would make more sense to ad a popular device to the kernel family. but as i said, just my 2cents others may see things differently.
[Nexus 5 Original Android Development] Spinergy02:
You have completely missed the point twice now. I'm trying not to be a jerk, but something marked as CAF compatible should be CAF compatible. I'm not going to participate in your circlejerk any further.
[Nexus 5 Original Android Development] gravedigger76:
Check OP. Clearly states that CAF version is for 4.4 and not LP.

Seems pretty clear.
[Nexus 5 Original Android Development] Spinergy02:
Because everybody with the EX app is going to check the XDA thread to verify what the app is saying.

Edit: the main reason I purchased the app was to keep from having to check this thread for updates.
[Nexus 5 Original Android Development] flar2:
I'm going to pull it from the app to avoid confusion.

To clarify for others: the standard EX kernel is compatible with official cyanogenmod.

It is NOT compatible with the special CAF builds of cyanogenmod.
[Nexus 5 Original Android Development] Spinergy02:
Sorry for blowing your thread up with all of this. I just wanted to point out the issue I had after receiving the app notification to possibly save other users some frustration. I've always enjoyed your kernel and appreciate the hard work you put into it.
[Nexus 5 Original Android Development] gravedigger76:
Of course its up to you and all, just IMHO checking the thread, reading And knowing what you flashing would have prevented you from 1-soft bricking, 2- bugging And showing attitude when people are trying to explain to you where you've gone wrong.

Again just IMHO.
[Nexus 5 Original Android Development] adibayer_:
just install this kernel with terminus with step like this:

1. Terminus

2. GApps

3. SuperSU.

4. ElementalX

but DT2W didn't work at all. Am I missing something?
[Nexus 5 Original Android Development] Spinergy02:
I did wrongly catch some attitude with you. I was a bit worked up after having another user try to tell me that the main difference between the official AOSP CM12 builds and myfluxi's CAF CM12 builds was the kernel when that is far from true. I do usually read the OP and I wrongly trusted the app.

I understand why he marked it as CAF due to the number of people posting in this thread that don't understand that official CM12 is currently AOSP and not CAF. My apologies for the harsh reaction to your comment. I definitely could have worded my response differently.
[Nexus 5 Original Android Development] luckana:
Can someone explain me why people use functions such as dt2w, s2w ? :D Seriously, why would one spare more battery just to touch the screen twice and turn the display on? What, is it too hard to press the power button I really do not understand. Is it only because it's cool ?
[Nexus 5 Original Android Development] californicated:
Some people don't want to wear the phone's power button ;)
[Nexus 5 Original Android Development] nappent:
Very useful when running in treadmill. Or phone is in a car mount. Basically any situation where you can't easily press the power button... Just use your imagination ?
[Nexus 5 Original Android Development] luckana:
Oh, that's a point right there. Never thought about it this way :D
[Nexus 5 Original Android Development] Jax Teller:
[MENTION=4684315]flar2[/MENTION] I wanted to inform you that when I have SuperSU 2.45 installed the installation with Aroma Installer is not going very well.

A lot of the selected settings are not applied, like readahead size, backlight dimmer etc and also the backup file is not getting created in sdcard.

In addition to these, the kernel itself doesn't react the same, loading, boosting etc.

Going again back to SuperSU 2.40 and installing kernel again solves all the problems and everything is normal again.

Also ukm & synapse doesn't work with SuperSU 2.45, only SuperSU 2.40.

Your app is working fine.
[Nexus 5 Original Android Development] luckana:
UKM works like a charm with 2.45, something went wrong with your setup
[Nexus 5 Original Android Development] Jax Teller:
I'll check ukm again but the installation of the kernel with 2.45 has been checked twice with two different roms.
[Nexus 5 Original Android Development] adibayer_:
can anyone help me with this problem?

I need this to minimalize in using power button, because some of my friends who have Nexus 5 got problem because they always use their power button to wake it.

their problem is the power button sticking with some component inside, so it always in pressed state even though they not pressed it. That is why I use DT2W, to minimalize using power button or volume rocker to wake mine.

Wish someone could fix this :D

Edit: Problem Fixed
[Nexus 5 Original Android Development] kong:
I would recommend using Gravity Screen for a more natural way to automatically turn off / turn on the screen :good:
[Nexus 5 Original Android Development] ciano865:
Does gravity drain less battery than dt2w in your experience ?
[Nexus 5 Original Android Development] californicated:
Yes. The drain is really minimal

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] t0mas_:
could you please state what settings did you choose to wake up the screen in the app? my experience from a while ago using kk are quite different...
[Nexus 5 Original Android Development] californicated:
Disable every settings that wakes the phone using motion/gravity sensors. Should be only one option if you didn't change the settings yet.

So you make the screen turn off when put top down in the pocket or face down on the table, and wake up when moving over the proximity sensor.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] magnamentis:
show me where it's marked as caf compatible in the op it isn't and as i know [MENTION=4684315]flar2[/MENTION] he would never mark something as caf compatible if it isn't, and if he wold more mean the official cm12 caf stuff than the special out of the ordinary stuff. so if it should be marked as caf compatible somewhere it would be better to guide us there to see instead of getting *****y. and then you begin to drift off with your wording, means put to ignore list and bye bye.
[Nexus 5 Original Android Development] Spinergy02:
I never once stated that it was marked CAF compatible in the OP. I clearly stated that it was marked as CAF compatible in the app. The issue had already been addressed by [MENTION=4684315]flar2[/MENTION]. Please add me to your ignore list ASAP.
[Nexus 5 Original Android Development] R3Lax1:
Can confirm, aroma flashes like express with 2.45.
[Nexus 5 Original Android Development] nednednerb:
SuperSU 2.45 is marked as stable in the xda thread, but no play store update from 2.40 indicates 2.45 may be marked as the 5th beta in a row soon, given this kind of bug.
[Nexus 5 Original Android Development] walpurgisnacht30:
2.45 is still in RC stage.
[Nexus 5 Original Android Development] nednednerb:
Yes, like I mentioned. It was yesterday it said "stable," but it sure doesn't seem to be!

Still buggy obviously, and no play store update being pushed. Definitely only a candidate.
[Nexus 5 Original Android Development] mayurh:
Guys I'm on stock lp 5.0.1 with root and Franco, I want to try this kernel , I see talks about flashing boot.img then this kernel

Can I restore the backup of the stock kernel that I made with fku app before flashing his kernel? Or does it have to be stock boot.img? Tks in advance
[Nexus 5 Original Android Development] AtEExll:
It's the same, you can restore the backup from your stock kernel.

Best Regards.
[Nexus 5 Original Android Development] till22:
Is there some setting except for "USB fastcharge" to be able to charge the phone quicker? My phone always needs ~3h to charge to 100%, even with a 2,1A charger.
[Nexus 5 Original Android Development] magnamentis:
wanna be sure you have to measure the real throughput, best with an Volt/Amperemeter. once when i had such kind of issues it was showing that the cables were the culprit and not that just one was bad, but only 2 of ten were perfect while 6 were average and 2 ( new ones ) were useless. before i found out i bought about 10 different chargers in vain.

so easy way without buying the hardware (amperementer) try different cables and just sayi'n, original cables from oems are by no means the best one can get. i have 4 identical original samsung usb cables and each of them provides a different throughput, one even very bad, of course measured on same device, same charger, same source and same consumers and setup.
[Nexus 5 Original Android Development] till22:
I'm sure I have one lying around somwhere, Let's see what the result is.. And I'll make sure to check every cable in the house ;)
[Nexus 5 Original Android Development] magnamentis:
my findings were so unexpected and unequivocally that i marked all my cables with a color, green for good, yellow for average ok and red for only use if must be LOL
[Nexus 5 Original Android Development] till22:
It's going to be a tough job measuring:

Just need to figure out what to set on the DMM and I'll see what I'll get :)
[Nexus 5 Original Android Development] magnamentis:
but you know that you need a consumer running thus you have to measure between charger and consumer (device) LOL OK i see you have the equipment so you probably know that, just to make sure that nothing spoils the fun. so the device has to be on and the more power it sucks the better, thus should not be at 99% or something, better below 90% and navi, lte, etc etc. on with full brightness. that will make it suck power. that's where benchmarking would have a real benefit for once or directly after booting to use the media scanner running, that really sucks (power) :)
[Nexus 5 Original Android Development] till22:
Can't find anything to put inbetween to measure correctly. Any ideas, easy DIY? Or else I'll just have to use the boring method and try all cables through :)

This would come in really handy, but I don't feel like buying the stuff I miss to build it myself: http://www.tolaris.com/blog/wp-content/uploads/2013/02/usb_tap_1.jpg
[Nexus 5 Original Android Development] sempot:
Cables are to blame . My nexus 5 cable is kaput now. The charge was so slow and i was about to buy the new charger in the playstore. However, i tried some other cables laying around in my house, and guess what? The charge speed is fast and good now. [emoji16]
[Nexus 5 Original Android Development] DroidIt!:
Oopse :)
[Nexus 5 Original Android Development] theesotericone:
psssst. Droidit. (whispers)You're in the EX thread.:laugh::cool:

EDIT: Damn it you ninjad me before I got that post quoted. It was classic.
[Nexus 5 Original Android Development] DroidIt!:
Nice try...muwahaha but I am faster! [emoji12] ...well, sometimes [emoji4]
[Nexus 5 Original Android Development] gpvecchi:
I would like to enable the missing LTE bands on my phone, I know the kernel must have a particular requisite... Is EX compatible?
[Nexus 5 Original Android Development] openlatedotorg:
By default, on elementalx gov the sampling rate is 30000, by even making it 31000 ui is noticeably different.
[Nexus 5 Original Android Development] flar2:
The lag is because you flashed Franco before. Reflash your ROM to get your system back in order, Franco deletes some stuff that this kernel needs.
[Nexus 5 Original Android Development] flar2:
Just a note:

If there is any lag at all, there is something wrong with your system. You shouldn't have any lag on elementax governor either.
[Nexus 5 Original Android Development] Syk69:
I agree. Using elemental governor with your stock settings and don't see any lag at all. Most likely if anyone notices lag I would check to see if there is any app running in the background taking up resources excessively.
[Nexus 5 Original Android Development] onecrzyasian:
Crap. I was using purity rom with Franco and just switched to your rom. Does this mean I have to clean wipe and then start new with rom and then only flash your kernel?
[Nexus 5 Original Android Development] Syk69:
You can just flash purity again, boot to rom, and then reboot to recovery and flash elemental kernel. No need to clean wipe.
[Nexus 5 Original Android Development] cpom1:
The latest kernel update made me have WiFi issues for some reason... Not sure if anyone else experienced that.
[Nexus 5 Original Android Development] Syk69:
Nope no WiFi issues here. Flar2 didn't change anything for WiFi. Reboot router perhaps?
[Nexus 5 Original Android Development] edangel:
Ok my results with elementalx 18..all stock gboost enabled!no s2w dt2w etc..

24 hours with 4+ SOT with data enabled 24 hours and wifi when i am home..!mostly used fb chrome youtube about 40 minutes watching fails compilations lol ..classic viber conversation and 30 minutes of call today and about 300 sms text..!took about 12 pictures blah blah and other things that i dont remember..

The funny thing is that battery stat is showing that i charged my phone..what the heck?i only rebooted my phone once just to apply some adblock hosts files...

Maybe rebooting the phone charges magicaly?

If yes then flar2 you did a great magic trick hahaha...just kidding..!

No problems so far and kernel kicks a$$..buttery smooth..!big thanks
[Nexus 5 Original Android Development] cpom1:
Nope. Because my gf phone was working. And so was my Xbox and my computer. Not sure what happened.
[Nexus 5 Original Android Development] flar2:
It's definitely not the kernel. The WiFi drivers are stock and haven't changed at all since the 4.4.1 update. Try rebooting your phone and the router.
[Nexus 5 Original Android Development] biggofer:
thermal

Hello , I've looked threw the thread and can't find answer , I see while install there's option to lower thermal thresholds but what about raising it ? I've tried to use a few kernel control apps but none of them show the option to raise it for some reason , I was looking at the sys/module/msm_thermal file but I'm clueless on what to change .

And same with fsync I want to turn it off but don't no location and those apps don't show option to turn off . any help would be appreciated . thank you .
[Nexus 5 Original Android Development] TheSpaceManatee:
Hey guys, any idea why my minimum CPU frequency is stuck to 1.2 GHz and I cannot set it lower?
[Nexus 5 Original Android Development] flar2:
I think I know what you're talking about, a very subtle effect. This is where a lower sampling rate might help.

The thermal is not configurable through apps, you would have to edit /etc/thermal-engine.conf to raise thresholds. If you want to temporarily disable it for benchmarks or something, you could open a terminal and type (as root): stop thermal-engine-hh

Granted it's very cold middle of winter for me right now, but I haven't noticed thermal throttling while gaming or anything.

It's not stuck, that's the frequency it uses when you touch the screen. You have to touch the screen to open CPU apps, so that's what they mistakenly report.

There is no need to worry about frequencies with this kernel. If you don't touch anything, it will work as intended.
[Nexus 5 Original Android Development] letmedanz:
When dt2w is toggled off using the power button, for one hour I had 0 drop in battery!

I think that's what you had intended flar2, working great.

The next hour with the screen locked normally but not used, there was a drop of 2 pcnt for the hour.

Must say this has definitely been the best version of this great kernel so far
[Nexus 5 Original Android Development] wklie:
I also noticed that the UI is less smooth with 0.18 (gboost enabled, cooler thermal throttle not enabled) compared to 0.17 elementalx governor, and got lower scores with Antutu (yes, I know it does not reflect real world usage). I thought I was doing something wrong and went back to reflash stock kernel before flashing the 0.18 again, and even uinstalled Trickster app.

After chargnig my phone I'll try to adjust the sampling rate and see if it helps.
[Nexus 5 Original Android Development] thereal_bigjake:
I flashed .18 on a secondary CM11 rom and it booted a ran normally. Later when I rebooted to recovery I was asked to input a password and I don't use any encryption. Also multirom seemed to be uninstalled at this point says twrp. So I rebooted again and went straight to the internal rom confirming multirom is gone.

Reinstalled multirom and all is fine so far.

Been using multirom on my Nexus 7 for a year now and never seen an error similar to this so I thought I'd mention it here.

No problems at all with .17
[Nexus 5 Original Android Development] dsmpampis:
Does it work with ART? Or I have to go to Dalvik?

Thanks in advance!

Tapatalked with my Nexus5(AKA The Hammerhead)
[Nexus 5 Original Android Development] estate:
0.17 was better battery save forma me

During the night in flightmode 0.17 alfter around 9h lose 0%

0.18 sane condition but lode 3% boost features enable (tonight try without and report)

In general feeling 0.18 have more battery drain.

Performance with 0.18 is fantastic so so smooth!

But maybe go back to 0.17... See tomorrow.

Anyway, goooood job!!!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] aquavalanche:
Hi! I've been sticking to this rom on several builds, I wonder what is elemental x base governor? Is it based on on demand or interactive? Thanks
[Nexus 5 Original Android Development] ciano865:
CM12 Official Nightly 01/24

Kernel works fine.

Flashed CM12+SuperSU 2.40 and after reboot 2.05 kernel... no problems :)
[Nexus 5 Original Android Development] armaki:
the only thing that does not work for me is the Sandisk USB-OTG 64Gb. Tried both exFAT and NTFS.
[Nexus 5 Original Android Development] abovebeyondgal:
Hello,

Im on stock with ElementalX 2.05 kernel

my wifi sometimes freeze and i need to reboot the phone .

the network disconnected and i cant turn off or scan for network

what can i do ?:confused:
[Nexus 5 Original Android Development] rhamej:
Correct me if I'm wrong flar2, but the kernel has nothing to do with the WiFi. If the phone is freezing, the only thing I can think of that could be kernel related is if you under volted. But it would happen in places other than WiFi too.
[Nexus 5 Original Android Development] abovebeyondgal:
the phone doesnt freeze , just the WIFI .

its enter a state that i cannot turn it off or on.

im not undervolt or underclock. made regular installation.
[Nexus 5 Original Android Development] rhamej:
If that is correct, I stand corrected :)