yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] rickyx32:
Yeah, I use Xposed and GravityBox too and they've been updated recently, but the problem occurred before I installed them so I ruled them out. Again, I know that 0.36 has been out for like two weeks and I've only noticed this issue the past two days or so. Besides the sound issue which affects all of the OS, the other weird function/connectivity issues have been bound only to Google apps, and not facebook etc. So I can't tell if it's a recent update causing the issue, the 0.36 kernel, or both.

Edit: Well I switched to 0.34 and it happened after I installed Adaway and let it reboot. Are you using it?
[Nexus 5 Original Android Development] C3C076:
My info if it helps. Running stock with GB and 0.36 since it came out and I have never experienced this issue.
[Nexus 5 Original Android Development] dakore:
I can confirm this, and I experienced this today for the first time.

I'm running Cataclysm (since last year) + Elemental 0.36 (since release date April 5) and always using the same setup since ElementalX 0.26. I've never seen screen flickering before... This morning I accidentaly saw your post and skipped it. This afternoon I saw flickering while I was playing Ingress. I came home, put my phone on charger and flickering appears every 5 seconds so I managed to capture it with camera.

Here is the video and dmesg taken within 1 minute since flickering occured.

https://dl.dropboxusercontent.com/u/12007684/MOV_0003.mp4

https://dl.dropboxusercontent.com/u/12007684/dmesg.txt

I must say:

- the phone was NOT hot!

- I play Ingress every day - this is the first time I saw flickering

- screen brightness was on auto (it probably ramped up to max because outside was sunny)

- I haven't touch the system or kernel in any way since last week at least. Same setup and apps like for the last 4-5 days for sure

- I don't use S2W or any kind of touch to wake features
[Nexus 5 Original Android Development] Android_Sheriff:
Yes, I do use Adaway. I flashed .34 just to check and I got the boot sound, but there's still no sound from the volume sliders or while changing sound profiles.
[Nexus 5 Original Android Development] aceian:
OT

Check out "Google Edu Device Setup" - https://play.google.com/store/apps/details?id=com.google.android.apps.edu.nfcprogrammer

Read the what's new section..

END OT..

**sorry **
[Nexus 5 Original Android Development] rickyx32:
Well I never had the issue the whole time 0.34 was the main version, so it's strange that it is occurring now. It may not be the kernel after all, I guess I will have to got pure stock for a while then root try Adaway and wait some more.

Anyway a few more things I notice is that I am able to do a type search in Google Now, but when I click the microphone button to do a voice search it says "Can't reach Google at the moment." The mic icon is hollow instead of white or red. With YouTube, again the screen will have the play and pause buttons alternate for a bit with the black background and will then display "There was a problem while playing" "Touch to retry". Besides that there is no sound while unlocking, using the volume rocker, using the dialer, no sound at all from the device it seems. Out of curiosity I checked to see if the Google account was syncing and the only one that failed to do so initially was "Sound Search for Google Play", though it did sync when I did it manually. The sound only came back after I rebooted. I rebooted several times to see if it would come up again, and it's pretty much happens at random...

Edit: Sheriff, can you confirm that you are having the same exact problem? If it's a bug from a recent Google app update then I would think that more people would be having this issue, the other thing we have in common is Adaway, maybe a recent update to the hosts files is doing it, but I never thought it was possible, I'll go pure stock for now so i can continue to rule out more suspects.
[Nexus 5 Original Android Development] :
Voice commands working fine for me on aosp 0.36. ;)

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Nexus 5 Original Android Development] magnamentis:
are you bored ?

- there is no need to update this kernel just for the sake of an update for flashoholics, because it's already good as it is

- there is no need to update because it's better than googles and they update every 2-3 months

- you are bored flash something else, but try not to impose pressure on the dev, willingly or accidental, if he likes he never ever has to update anything, specially not his working kernel

- look at the very fequently updated kernels, sooner or later something brakes, some famous devs had to go back to the drawing board LOL

- when google updates what, is not kernel related, thus OT

- your post is to no-ones benefit but is spreading a certain kind of energy for those with the appropriate antennas :)

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11, AGNI Kernel 2.7.5_r3, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] MBQ_:
Yep

This will always be my fallback kernel

Played around with other kernels and honestly, this has consistently been the best for me.
[Nexus 5 Original Android Development] Tylog:
As if (apart from CM ) great changes to other kernels would have happened including in the last week's ( maybe here and there a few small changes and fixes but nothing more. 4.4.3 comes and maybe the Game starts from zero.

The Fact is , ElementalX is one of the Top 3 Nexus 5 Kernel , and there is no reason every day to make any changes to the senseless only create problems and then fall away again.

Keep up your great and always friendly work flar2.

Best regards.

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] MrCatalyst:
If it's not broken, don't fix it. No point making unnecessary tweaks, especially with 4.4.3 just around the corner. Let flar2 rest instead, until new Android is out, so he can release v0.37 for it.
[Nexus 5 Original Android Development] Boonyard:
I don't want to slag off other devs, but other kernels regularly get updated and updated and often get worse and worse. There's one popular one which was great about 20 releases ago, and is mostly rubbish now. Too much fiddling for fiddlings sake.
[Nexus 5 Original Android Development] FuMMoD:
Can we stop with the off topic talk and just ignore the stupid remarks made by some members. Remember there's a report button for a reason. The mods can't monitor every single thread so help them spot the trolls.
[Nexus 5 Original Android Development] tracerit:
loving this kernel. i get <4% battery drain over 8 hours overnight. with franco , it was 2-3%/hr.
[Nexus 5 Original Android Development] fcisco13:
I get <1% over night 8 hrs.

Whatchu talking bout willis!
[Nexus 5 Original Android Development] Elluel:
Any custom kernel can do that as long as you manage wake locks. I've gotten 1% loss over 15 hours using Trinity B10.

Sent from my Nexus 5
[Nexus 5 Original Android Development] szucsgf:
Depends on your settings guys. No sense comparing overnight drain unless you have the same setup. Conversely, it only makes sense to compare overnight drain if you also post the details of your setup.

For example, I lose about 4% overnight too. I keep wi-fi and data connected, location history and reporting on, high accuracy location, and everything synced overnight. I think I'm entitled to being happy with 4%.
[Nexus 5 Original Android Development] hikarugo:
My bluetooth has never been on for even one second but my battery stats is weird
[Nexus 5 Original Android Development] magnamentis:
do you think that this kernel has something to do with it ?

- not sure about your intention, do you think it's the kernel doing this, i'm as sure as one can be that not

- is nfc on, because nfc is somehow related to bluetooth, no real idea just a thought :)

otherwise specify your intention in a more detailed manner [or should we just say thanks for the info :) ]

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11, AGNI Kernel 2.7.5_r3, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] letmedanz:
Have you tried a restart?
[Nexus 5 Original Android Development] BATZ DA LOCC:
Hey can I run this on aicp
[Nexus 5 Original Android Development] PetritH:
yeah, make sure to use CM one
[Nexus 5 Original Android Development] BATZ DA LOCC:
I used cm expresso
[Nexus 5 Original Android Development] PetritH:
You are good.
[Nexus 5 Original Android Development] BATZ DA LOCC:
I can't get my settings to stikc
[Nexus 5 Original Android Development] PetritH:
then use aroma version, and set it to you liking
[Nexus 5 Original Android Development] BATZ DA LOCC:
Which one is aroma going bakc to uber
[Nexus 5 Original Android Development] PetritH:
Look in OP dude, there are 2 versions CM express and the other one is with aroma installer...
[Nexus 5 Original Android Development] BATZ DA LOCC:
U late bakc on uber
[Nexus 5 Original Android Development] PetritH:
Lol, k kiddo
[Nexus 5 Original Android Development] magnamentis:
time to read :)

now it's time that you go and read the first page of this thread, all your questions are answered there.

further if you say that your settings don't stick it would be the minimum to let us know which settings,

because without setting max cpu clock speed in aroma for example you cannot change clockspeed to

higher than set upon installation and express comes with default clock speed. just one example beside others.

but still go and read, it's well explained and it does not make much sense to fill pages with the same Q&A, but in increments.

enjoy

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] rolear8:
So I red last pages, seems .34 still better than .36?
[Nexus 5 Original Android Development] magnamentis:
consider the following :)

you always have to put into account that 95% of users who are totally happy with

their config, could i.e. be 0.36, will not post anything here, while many of those with a

problem or an observation which appears strange or not so good would show up here.

this means, that most probably .36 is running perfect for the vast majority of users

and since it's younger, also most probably contains a few improvements.

so i would say that your conclusion is probably not correct. my reason to stay with

0.34 is that i always flash the latest milestone if not in the mood to try interesting new features

that were announced.

have fun

Current Devices:

I9100, PAC-ROM 4.3.1 ( Formerly Omni, PA, Dorimanx, etc. )

N7000, 4.1.2 TouchWizz All Stock ( very motivating to continue flashing custom roms further haha.... )

N7100, Cyanogenmod 11, Xposed Framework ( Formerly AOSNP, PAC, Omni, PA, Devil, Thor, AGNI up to 2.7.6, etc. )

Nexus 4, Cataclysm 4.4.2, Franco Kernel r203, Dalvik & Bionic Patched, Xposed Framework ( Formerly PAC, PA, Cataclysm, Faux, etc. )

Nexus 5, Cyanogenmod 11, ElementalX Kernel 0.34, Xposed, ( Formerly Cataclysm, Franco & FKU Color Control, Dalvik & Bionic, Faux, Bricked, etc. )
[Nexus 5 Original Android Development] BATZ DA LOCC:
I was using trickster trying to uc
[Nexus 5 Original Android Development] Venomous Viper 119:
I think people need to stop bragging about the drain they get when the phone is ideal. Every phone has different apps installed, a different setup & usage criterion. And some people don't even bother about wake locks at all while on the other hand, the people that do have a different knowledge & understanding of wake locks & hence they handle them in a different way. In any case, the results vary. What ultimately matters is that you should be happy with what you get. That's all. If you're really happy, drop by & thank him with your kind words & donations. If you find any issues, help him to identify & resolve them. Besides, you flash a custom kernel to get more juice & performance from your device. Not to let it on the couch for hours & watch it drain & brag about it (except while you're asleep). There's a separate battery thread to brag about your results & experiences, take your posts there.
[Nexus 5 Original Android Development] RJQXCV:
If you read the OP, you'd know using Trickster would cause problems, wouldn't you?
[Nexus 5 Original Android Development] jumparound246:
Nope, it's not ok to flash stock kernel only if you want to use another kernel after running elementalx. You need to dirty flash your rom.
[Nexus 5 Original Android Development] flar2:
Working on an update (minor)

Can I just get a quick recap of issues and requests?

Obviously I will update F2FS, but was there anything else?

What about the latest CyanogenMod? I haven't used it lately, is there a problem?
[Nexus 5 Original Android Development] gpvecchi:
Nope, all OK with Cm...
[Nexus 5 Original Android Development] drawde40599:
There's a few that have mentioned screen artifacts/glitches , I haven't experienced it but might be a real issue
[Nexus 5 Original Android Development] notbrodie:
not really sure what you're planning on fixing, lol

this kernel is an immovable force of stability

Sent from my Nexus 5
[Nexus 5 Original Android Development] ShoeVan:
I had this too, a reflash seemed to fix the problem but would be worth looking in to. Also I'm not sure if this is a problem with my loud speaker or not, but there's some popping and crackling sometimes when watching YouTube videos. If anyone else notices this, might be a kernel issue(?).
[Nexus 5 Original Android Development] paychex:
Getting some random reboots. Tried out the Chaos nightly, no reboots.

Here's a last_kmsg if you wanna look at it
[Nexus 5 Original Android Development] flar2:
I haven't experienced this, and don't think it's kernel related, as I haven't changed anything major in a long time. could be certain ROMs, as there is now a huge variety of ROMs with minor differences.

What ROM and could you describe how to reproduce this? I assume you aren't undervolting or anything that could cause random problems.
[Nexus 5 Original Android Development] paychex:
CM. Thought it might be undervolting. Changed to stock voltages, same thing. It would happen when I turned the phone on and it would hang for a second and restart. Sometimes when opening an app same thing.
[Nexus 5 Original Android Development] maidenboston:
sames been happening for me...

using cm11 and noticed this a few builds back (maybe a week ago)

i think sometime after the 14th april build is when i've been having "hang for a second and restart"

i just assumed it was something with cm11 nightlies...
[Nexus 5 Original Android Development] tomak1n:
so far so good with .36 + latest daily Slimkat rom
[Nexus 5 Original Android Development] pcphobic:
I have experienced the same thing twice on 0.36.

I am on LiquidSmooth 6th April version ROM.
[Nexus 5 Original Android Development] flar2:
I'm using CM latest nightly now, so far so good with 0.36. I don't see any recent changes to the CM kernel that should be causing a problem.

Are any of you using gamma control/color profiles/RGB settings?

Can you try using version 0.34? It's almost identical to 0.36 except it doesn't have the RGB color control, which is my suspicion right now.
[Nexus 5 Original Android Development] flar2:
Minor update for Stock/AOSP version. The only change is updated F2FS support, so you don't need to install if you don't use F2FS.

I don't use F2FS, so let me know if this is working.

I will release the CM/CAF version after I test it more to make sure it's stable.

Download:

ElementalX-N5-0.37

ElementalX-N5-0.37-express

Changes:

-update F2FS support
[Nexus 5 Original Android Development] bamboosensei:
Flar, is there any chance you could add the Zen IO Scheduler to your kernel? IMO, it's better than Row and Sio for performance and I normally use it on other kernels if they have it. Just a small request, thanks!
[Nexus 5 Original Android Development] pagratios:
I am trying to set sound control settings but the setting for speaker return all the time to 0.
[Nexus 5 Original Android Development] Onismurai:
Do you guy think 3 hours screen on time is good enough? Always got this SOT when came to ElementalX. I heard someone said in this thread that turn off gboost manually will get a better battery life. Is that true? I started to play Clash of Clan and since then my battery never last long after 10 hours.
[Nexus 5 Original Android Development] szucsgf:
Depends on lots of factors. Please post screenshots of your battery stats, wakelocks, and cpu frequency usage.
[Nexus 5 Original Android Development] nadiros:
Hey flar2 thanks for the new release. I know you only updated f2fs but for interest sake I'm going to test it for s2s as 0.36 is unusable for me because of poor sensitivity and it takes several tries to get it to function. 0.34 however consistently runs like a dream.
[Nexus 5 Original Android Development] :
If your playing games...have location services active, talk on the phone a bit, play music...etc...etc.....then 3 hours is a fair average.

As others said, it all depends on your usage.

Without screen shots from gsam, or something other than the stock battery usage screens.....we're all just guessing. ;)

Sent from my N5, N7, Moto X, G Tab 3 or S2.....
[Nexus 5 Original Android Development] wewewi999:
Nice dough

Hi there! Just took the plunge over your kernel;

I installed it for its ability to toggle the Double Tap 2 Wake function with the Power Key. Clever.

Thing is; It seems to be tricked by the DinamicNotifications app.. You might know about it..

--- Even when you press the toggle, it'll still wake up on double tap if you get a notification.

1) Any way you could make the toggle work with the Power Key only?

2) Would be nice if Double Tap 2 wake would be automatically disabled via proximity sensor (To make sure it doesnt wake up when it's my pockets, for example)

Keep up the good work!
[Nexus 5 Original Android Development] notbrodie:
I've been using it with CrDroid b21 (based in CM11-0419) with the Piereligio trueRGB and the lux RGB plug in without issues.

Sent from my Nexus 5
[Nexus 5 Original Android Development] kong:
Somehow 0.34 seems to be smoother than 0.36 for me on CM11.
[Nexus 5 Original Android Development] drawde40599:
For #2 the Kernel dosent control the proximity sensor on the N5

---------- Post added at 07:15 PM ---------- Previous post was at 07:11 PM ----------

What setting r u changing ? And how r u doing it ?
[Nexus 5 Original Android Development] marcusva79:
Flar do you think the glitches came from the new theme engine cm put out? I remember some kernels weren't working well with it. Just a thought.

I agree with Kong. I was getting slight stutters with .36. .34 has been working better in my phone.

Running carbonrom latest with .34
[Nexus 5 Original Android Development] wewewi999:
Restored stock kernel.

Battery drain was so important the battery actually DEPLETED even when AC plugged in on my 1.35A Nexus 7 charger.
[Nexus 5 Original Android Development] Venomous Viper 119:
I'm sure it is not the kernel problem. Something to do with your ROM. Do a clean flash again & your good to go. This kernel rocks!!
[Nexus 5 Original Android Development] dead0:
I'm using viper in combination with the beats libs. Found it to be a better enhancement ;)
[Nexus 5 Original Android Development] parkson:
Where to find alternative audio libs?
[Nexus 5 Original Android Development] dead0:
I'm still testing but I'll post them here once I know its definitely working

ps my bbs with 0.10 2hrs SOT with 60% remaining. data was on most of the time screen was on whilst browsing and facebooking, the odd call and sms, a few benchies with antutu and quadrant
[Nexus 5 Original Android Development] alchimia:
How to do it?

Inviato dal mio Nexus 5 con Tapatalk 2
[Nexus 5 Original Android Development] dead0:
i'll post when confirmed. wanna make sure it works. i'll post a how-to on the weekend for other testers
[Nexus 5 Original Android Development] mercuriox85:
The best kernel! I love it!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] Batfink33:
I used Viper before I found Neutron player ,dont need Viper now!
[Nexus 5 Original Android Development] mrruin:
Does anyone use CM11 with this kernel and can test if USB Audio works with this kernel installed? Thanks!
[Nexus 5 Original Android Development] ValoXis:
My settings: UC from 2.3GHz to 1.9GHz, UV -25 for all frequencies, governor interactive, scheduler sio, max freq screen off 960MHz.

For now (this is the first time with this kernel), this is my battery life with 0.10:

Spoiler content hidden.

Nexus 5 with Tapatalk Pro
[Nexus 5 Original Android Development] Moose0704:
Awesome Kernel!

Loving this kernel! Thank you very much for your time and work on this!! ;)
[Nexus 5 Original Android Development] rootuser11:
EX 0.10 + Stock Frequency + EX Bus + 725mv + ART

EDIT: Battery life has improved about 10-15% since ART was enabled.
[Nexus 5 Original Android Development] frarredo:
If I flash this is there a way I can reflash the stock kernel?

Or if I restore from a previous back up will it overwrite the kernel?
[Nexus 5 Original Android Development] frarredo:
How can i edit the elementalx.conf ?
[Nexus 5 Original Android Development] ColdCircuitCash:
Has anyone's phone fried yet using ART? Or am I just being paranoid about running it. Can anyone give me some encouraging words and reassure me? :)
[Nexus 5 Original Android Development] dbolot1:
Running ART with the latest beta, all is well...the initial boot took a very long time.
[Nexus 5 Original Android Development] ColdCircuitCash:
On a separate note, flashing a kernel over another should overwrite everything. If you're concerned wipe the cache but I've never had to. Editing instructions are in OP. Or use the included setup.
[Nexus 5 Original Android Development] parkson:
Only problem flashing kernels over one another is that some kernels remove MPDecision for a substitute and that can cause problems for new kernels flashed. Recommended to dirty flash ROM before new kernel
[Nexus 5 Original Android Development] ColdCircuitCash:
What noticeable problems does removing MPdecision cause?
[Nexus 5 Original Android Development] jarjar124:
Turns all four cores on and you won't have any hotplug for the kernel to run on.
[Nexus 5 Original Android Development] Tom540:
Depends on the ramdisk the kernel uses, but it doesn't affect cache - dirty flashing the ROM is all you need
[Nexus 5 Original Android Development] wewewi999:
Besides this kernel, I was running 100% stock.

Funny to see you blaming the ROM though.
[Nexus 5 Original Android Development] Venomous Viper 119:
Did you come from some other kernel or were you on stock kernel before?
[Nexus 5 Original Android Development] wewewi999:
Came from stock. Was my first take on custom kernels for my Nexus 5.
[Nexus 5 Original Android Development] Venomous Viper 119:
Weird. What settings did you choose in the aroma installer?