yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] anthonyly:
In the op

---------- Post added at 10:38 AM ---------- Previous post was at 10:37 AM ----------

Only stock camera doesn't work, how do I delete stock?
[Nexus 5 Original Android Development] flar2:
doubletap2sleep has to be implemented in a rom or app. It has to know the context of where you are tapping (eg: a blank spot on your wallpaper rather than in your web browser), otherwise the screen would constantly be going off and on.
[Nexus 5 Original Android Development] notbrodie:
yes and no.

it will lock your min frequency to 1267mhz, because it reads from the wrong source.

other than that, it works fine

Sent from my Nexus 5
[Nexus 5 Original Android Development] NovaSlim:
delete the offending app(snapchat) in this case and reinstall it should help.
[Nexus 5 Original Android Development] anthonyly:
Offending app? All camera app works besides the stock one :c is the problem.
[Nexus 5 Original Android Development] zymphad:
Best settings to use with ElementalX?
[Nexus 5 Original Android Development] NovaSlim:
The problem is typically that other apps takes over the camera and don't let the stock camera app use it, hence why I suggested you delete and reinstall the other camera using apps to see if that helps.

You don't have to try if you don't want to.

If you can't decide, use stock. Tweak voltage/scheduler/read-ahead cache to see what works for you, the same setting could act very differently on different phones due to difference in chip silicon(same UV setting could be fine on one phone and bootloop on another).
[Nexus 5 Original Android Development] FuMMoD:
Stock ones that are already chosen in the aroma installer or express one.
[Nexus 5 Original Android Development] Jaani:
Plz check PM ;) Sorry for OT
[Nexus 5 Original Android Development] nickporwal:
Getting amazing battery life...... Thnk you for such a hard work
[Nexus 5 Original Android Development] AhmedFaiz:
Nice to be back here.. V 0.34 beta running all well in default settings...:) was missing this for a while!

Nexus5/PA4.2 Beta1/Elementals v 0.34 Beta
[Nexus 5 Original Android Development] Chochiwpg:
I am still on v0.33 haven't updated yet, but something odd happened twice today. I was just wondering if anyone else has experienced this:

My phone is off, sitting on my desk and then briefly flashing on (as if I pushed the power button) and then off again right away. No notifications or anything, I don't have active display so it shouldn't do that. I was just curious if anyone else has ever came across something like this?

I am running v0.33 with stock settings and on the factory image rooted. Thanks.
[Nexus 5 Original Android Development] letmedanz:
That's how the toggle has been set for disabling dt2w feature.

If you check, the flicker of the screen will happen at the time that been set in aroma (maybe 15 mins?)

flar had stated that this is how the toggle off of dt2w function would need to work.

so nothing to worry.. it's the same for all of us
[Nexus 5 Original Android Development] LiquidSolstice:
If I may make a a suggestion; instead of pushing for double-tap anywhere to sleep, I strongly suggest you change the primary (directly up) Navigation Ring Target to screen-off using your favorite ROM.

It's a very natural gesture, and all it takes to turn your screen off is a quick flick up from the home button. It's a lot nicer (in my opinion) than Sweep2Sleep, and when combined with D2TW, it means you never have to touch your power button.

Just food for thought...
[Nexus 5 Original Android Development] Chochiwpg:
This is what should happen if dt2w feature is enabled. But I never enable that feature, I leave the default values from Aroma installer and don't install any of the extra features of the kernel. Just flash and leave as is. Is it still supposed to do that?
[Nexus 5 Original Android Development] flar2:
No it's supposed to be disabled if you didn't select doubletap2wake or sweep2wake. I'll double check the installer later tonight.
[Nexus 5 Original Android Development] Chochiwpg:
Thanks [MENTION=4684315]flar2[/MENTION] I'm also on v0.33 haven't had a chance to update to v0.34 yet. So maybe after the update it won't happen. Only happened twice so far which was strange. Thanks for the fast response. :good:
[Nexus 5 Original Android Development] francescobabbaro:
Awesome kernel! Thanks for your job, but I am a doubt. If I select cooler colors of screen, I may break it? Thanks again.

Sorry for my bad English.
[Nexus 5 Original Android Development] anthonyly:
okay ill try later
[Nexus 5 Original Android Development] ali262883:
This kernel is just awesome.. I'd tried it 3 times before but ditched it in just a day due to less battery life but had to come back because of the smoothness it offers.. Finally the 0.34 is super smooth and gives very good battery life.. Thanks..
[Nexus 5 Original Android Development] shaker2k:
Hrmm I might consider it again. No doubt it is smooth and responsive, but as you the previous versions weren't quite as good on battery as Franco.
[Nexus 5 Original Android Development] evo_like:
Hi all: I have a nexus 5, and am on Liquidsmooth ROM. I just flashed the elemental X .34 beta express. I am noticiing that the min CPU frequency keeps on going to 1267mhz, despite me setting it at 422. I take it that this will cause more battery drain than what I want it to. Can somebody please tell me what I am missing here, and why my CPU Min settings are not catching?

TIA.
[Nexus 5 Original Android Development] aashgaur:
U can't change that. Simple. Wherever u set it. It'll jump back to the 1267mhz.
[Nexus 5 Original Android Development] evo_like:
Ok. So this is normal behavior then? Will this not hAve a negative impact on battery life ?
[Nexus 5 Original Android Development] Tylog:
You can disable mpdecision , then you can lower your settings , but no need for it, let's touch boost work how it work, needs no more battery .

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] shaker2k:
That is touch boost. If you look at Cpu spy it will spent most of its idle time at what you set it at. Not including deep sleep that is, when your phone is off.
[Nexus 5 Original Android Development] evo_like:
Aah, thank you for the info. I will just run it as is for a while and see how the battery life is. Then maybe will disable mpdecision. What does it do btw, if I may pick your brain?
[Nexus 5 Original Android Development] Tylog:
shaker2k gave you the correct answer one post before yours :)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] evo_like:
Lol I just saw that. I must have posted right after he posted :)

Thanks everybody!
[Nexus 5 Original Android Development] Tylog:
:) you can read this if you want http://www.3c71.com/android/?q=node/1479

Tapatalk Team SlimRoms Nexus 5
[Nexus 5 Original Android Development] evo_like:
Thanks for the link tylog
[Nexus 5 Original Android Development] JmPTaz09:
I just wanted to say after some further testing... Wow, this kernel is just leaps and bounds above all others in terms of battery usage while maintaining smoothness for my usage (medium to light). It just does the tasks you need it to then goes to sleep, like a good little kernel, lol.
[Nexus 5 Original Android Development] ak4d4:
Lmbo

Sent from my Nexus 5
[Nexus 5 Original Android Development] PetritH:
Hell yeah, finally someone didn't say "Sleeps like a baby" I like sleeps like a good little kernel lol
[Nexus 5 Original Android Development] FuMMoD:
Sleeps like a drunken panda. Lol better?
[Nexus 5 Original Android Development] railed:
Getting bootloop when upgrading from .26 to .34 beta. What info do you need from me? Setting are the same as my .26 config; re-installing .26 allowed me to boot again.
[Nexus 5 Original Android Development] FuMMoD:
Don't undervolt. For future reference if you undervolt and you can't boot, that's the first thing to check.
[Nexus 5 Original Android Development] Gipjoe:
what rom? Worst case Ontario just delete your elemental x config, wipe dalvik and cache then reflash
[Nexus 5 Original Android Development] sempot:
Ontario Canada? :P
[Nexus 5 Original Android Development] danarama:
Ha!
[Nexus 5 Original Android Development] letmedanz:
This can also happen if you use trickstermod and select 'set on boot'

Trickster overwrites the min
[Nexus 5 Original Android Development] t1.8matt:
This is most likely MPdecision causing this. If you check your info in Trickstermod, you will see it actually goes down to 300MHz when the phone is idling.
[Nexus 5 Original Android Development] letmedanz:
You can also achieve this with LMT

That's how I've set it..

Swipe up from the bottom of the screen and it locks

Profit!
[Nexus 5 Original Android Development] Gipjoe:
Sorry just made a really Canadian joke too much trailer park boys for me.
[Nexus 5 Original Android Development] LiquidSolstice:
I'm sure that would work great too. I haven't used LMT in the longest time because I haven't felt like I needed to.
[Nexus 5 Original Android Development] letmedanz:
Maybe you should give it a go again..

i have the bottom left for back, centre for lock & right for menu/settings

no dock, no navigation keys, the screen is now the size of a football field :D
[Nexus 5 Original Android Development] flar2:
Worst case Ontario...thought it was a typo for second, then I heard it in Ricky's voice and you had me laughing.

Don't watch this if you're offended by language, the guy is unable to speak without swearing.

[YOUTUBE]2MrlEvYtl44[/YOUTUBE]

Anyways, enough distraculating

Give 0.34 a try, I installed it without dt2w/s2w and the timeout is definitely disabled.
[Nexus 5 Original Android Development] FuMMoD:
I started cracking up when he got permission to smoke and the guys with the oxygen masks are right behind him. These guys are going to die from second hand smoke lmao. Slick move on the mistrial thing too on his part haha.
[Nexus 5 Original Android Development] kepapas:
First time actually trying this kernel loving the speed on art.
[Nexus 5 Original Android Development] kepapas:
Noooooo never!!!! I still rock Trinity its my reliable girl, fkernel is my battery saver slut and this is my my skanky whore!!!! Lol jk nice kernel BTW really digging performance so far.
[Nexus 5 Original Android Development] UgoBoss:
I'm on beanstalk and just flashed 0.34 but in Play Music my sound is at max volume, seems like volume keys doesn't work and nothing work, it is just at max volume.. I've searched but it was fixed by flashing the aosp version of this kernel but beanstalk is cm based so I must flash cm version.. Does someone noticed this? [MENTION=1632145]FuMMoD[/MENTION] I think you are on beanstalk too can you see if you have this problem please?

Thanks! :)

Nexus 5 tapatalked
[Nexus 5 Original Android Development] thereal_bigjake:
I used the CM version on BeanStalk and everything works fine...
[Nexus 5 Original Android Development] UgoBoss:
Thank's for reply! This only appear with Google Music not other apps make sure you tried with play music. If you do, I'm not lucky then..

Nexus 5 tapatalked
[Nexus 5 Original Android Development] thereal_bigjake:
Google Play Music works fine for me but I did delete the Dsp Manager and installed V4A.
[Nexus 5 Original Android Development] dh3lix:
fav i/o

Hi all ... just wondering and want to gather some feedback on your fav setting on i/o sheduler and read ahead .. i'm currently playing around with SIO and ROW with 512k ... used SIO/512 for 2 days ... pretty awrsome most "microlag free" feeling since ages - now going for row/512 for some days ...

yes .... surly it's allways a matter of your personal "feeling" but just want to have a better view on what the Flar2 kernel lova's do prefer for best smooth experience ... let me know if you are willing to share and if it's not to hard hitting the thread.

tia marcO
[Nexus 5 Original Android Development] jlevy73:
I use Flar's stock settings in aroma which are row/128.
[Nexus 5 Original Android Development] bosna110:
Would anyone like to share their rendition on your style used with flars kernel. I've got the .39 cm beta playing around trying to see if I can get a setting that eliminates lag or very close to no lag with above superb battery life
[Nexus 5 Original Android Development] xmlnoob:
Simply can't thanks Flar enough for this wonderful kernel. Flashed .34 on stock rom with latest gravity box, running custom uv700, no L2 bus OC & gboost (i'm no mobile gaming guy :p ), still running as smooth as silk!

Battery life is awesome with dt2w; before .34 30mins mp3 playing with 2G on will consume 6% battery, now consume 5% at most.

and most important, constant stock cam crash seems eliminated now ( which i still cannot confirm its cased by kernel or gravity box, nvm now because no more crash for 2 days so far).

I love this kernel! :good::good::good::good::good:
[Nexus 5 Original Android Development] InterFace86:
After 8hours @ night. 9% lost. How u ppl manage to get 0 or 1 with that time?
[Nexus 5 Original Android Development] sheshuvadrevu:
+1
[Nexus 5 Original Android Development] kraven001:
With everything off maybe you can get a very low consumption. My average is around ~4%/h with 4G on and mostly stand by. I get around 24 hours (according to GSam Battery Monitor) of usage out of a cycle.
[Nexus 5 Original Android Development] FuMMoD:
+1

I do not experience this issue because I always install viper4android on my roms. I noticed flashing the aosp version a few updates ago would decrease my volume and the caf cm version fixed my volume. Maybe Scott changed something around with the caf patches regarding volume now?
[Nexus 5 Original Android Development] Konsumhaus:
That consumption seems to be normal to me with wifi on and good mobile-signal.

8 hours with 1% consumption is for me normal too....but only in Airplane-Mode with everything off:cool:
[Nexus 5 Original Android Development] Jaza78:
Great kernel....
[Nexus 5 Original Android Development] xmlnoob:
Booo, just crashed :(

logcat attached....
[Nexus 5 Original Android Development] flar2:
I need kernel logs to know if it has to do with the kernel (dmesg).

However, I haven't changed the camera from stock, and it works fine for me (and I presume others) so I'm thinking it has something to do with your mods.

Any specific steps to reproduce the camera crash?
[Nexus 5 Original Android Development] xmlnoob:
its randomly crash when i wake up the screen and go for the camera, then it FC, and mm-qcamera-daemon keep taking up cpu and ofc burn the battery until i reboot the phone ( killall -9 mm-qcamera-daemon can't do the job)

do the dmesg stuffs keep after reboot? i'll try to dig'em out here.

Thank you.
[Nexus 5 Original Android Development] flar2:
No, dmesg just shows the recent logs.

But /proc/last_kmsg will show the kernel log from your previous boot, so you could attach that.
[Nexus 5 Original Android Development] absoluterebirth:
does the cooler color option damage the screen?
[Nexus 5 Original Android Development] flar2:
Just a note:

I recieved a PM from a user of this kernel who was still having a problem with busybox. If you remember, a while back there was a version of busybox that was broken and didn't run init.d scripts.

If you have any problems with settings being applied, check to see if the init.d script is running. If it is running, you should see a log file at /data/local/tmp/elementalx.log that will show the last settings that were applied.

If it appears that the init.d script is not running at boot, the solution is to update to the latest busybox by opening the busybox app and choosing update busybox.

I don't think so, many people have been using it for months. But it's preferred to find a good colour profile and do it that way.
[Nexus 5 Original Android Development] JmPTaz09:
No problems here on slimkat... Just running nice and smooth. Only 2 days on this combo but no hiccups yet. I don't run any kernel control apps, etc. So that might help.
[Nexus 5 Original Android Development] xmlnoob:
Thank you, last_kmsg attached.
[Nexus 5 Original Android Development] ralpheboyo:
...can someone pls help and point me in the right direction...just need some verification...installed trickster app and simply don't touch it as I do all my tweaks in the etc folder...one issue I am having and probably isn't kernel related I used the sound booster on trickster and save my profile...however my sound profile does not stick...after a couple of minutes it reverts back to the default volume (don't even reboot)....have posted on forum over at trickster just hoping some one could might know & provide assistance....

Latest Busy box pro installed ....Thxs....

Tapatalk: Nexus 5 (Art): SlimKat: ElementalX
[Nexus 5 Original Android Development] Leviatano:
What versione is better forma battery life? 0.26 or 0.34?:)
[Nexus 5 Original Android Development] D@nge1:
Kernel version 0.34 is very energy efficient.

Отправлено с моего Nexus 5 через Tapatalk
[Nexus 5 Original Android Development] danmaman:
Hi

both versions are brilliant and awesome

but i would suggest you try .34

cheers
[Nexus 5 Original Android Development] dskies:
I confirm 0.34 is more JUICY....
[Nexus 5 Original Android Development] drawde40599:
34 , but give it few cycles /days . that seems to work best .
[Nexus 5 Original Android Development] AhmedFaiz:
. 34 super performance and as mentioned above battery is too good with this kernel now. As it was always good.

Why this beta tag for this kernel! Does it really needed! ;)

Nexus5/PA4.2 Beta1/Elementals v 0.34 Beta
[Nexus 5 Original Android Development] Leviatano:
0.26 version
[Nexus 5 Original Android Development] danmaman:
yes i agree:good:

since 0.26 there are too much betas;):p

and 0.34 is it worth to get the stable status:good::good::good:

thanx

cheers
[Nexus 5 Original Android Development] Traxex_:
I've got flickering screen problems with 0.34.

Am I the only one facing that issue?

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] FuMMoD:
So far you are the only one.
[Nexus 5 Original Android Development] magnamentis:
not the kernel but the people :)

no it's not the kernel that needs a beta tag, it's usually the users who try it out

only some of them of course but if you wanna know what i mean spend

a few days in franco's thread and you'll know :)

the quality of the thread is as important as the kernel in the long run

and this is the most pleasant, albeit success attracts more public which is good

but unfortunately asks for far more tolerance with some posters haha....

Current Devices:

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

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

N7100, Cyanogenmod 11 4.4.2, AGNI Kernel 2.7.3, 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, Stock Vanilla 4.4.2, ElementalX Kernel 0.32, Franco's FKU Color Control, Dalvik & Bionic, Xposed, ( Formerly Cataclysm, Franco, Faux, Bricked, etc. )

_________________________________________________________________________________________________________________________________________
[Nexus 5 Original Android Development] sirovai:
Tried others kernel this day. At this time elementalx is definitely the best one. Lot of features and awesome smoothness, without going crazy with settings!

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Nexus 5 Original Android Development] dskies:
What ROM?

What kernel version? for Stock or CM?

Any patch or optimization?
[Nexus 5 Original Android Development] railed:
That fixed it. Thanks for the idea. Strange I could undervolt in .26 just fine to 700 no bootloop on restart.
[Nexus 5 Original Android Development] Traxex_:
Cataclysm Rom and, as I said version 0.34.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] FuMMoD:
Check your apps and whatever you have flashed. Been running cataclysm since November and the Dane with elemental and never had a screen flicker. Think of what you have modified to the rom.
[Nexus 5 Original Android Development] kmar22:
Latest running nicely minus the camera crash. On third party camera apps no crash just stock camera. Stock rom
[Nexus 5 Original Android Development] Traxex_:
I'm using Cataclysm with ElementalX for several months too and never ever had a single problem. Gotta try to do a clean flash then.

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] -Maverick-:
Hello everyone, quick question.

Does this kernel auto mount usb-otg?

I only ask because, while I'm currently on franco.Kernel I have to use an app to mount and un-mount my usb-otg. I'd like to avoid using an app if I can and simply have the kernel do it for me.
[Nexus 5 Original Android Development] Michealtbh:
I think this is rom dependant as well as kernel. Storage auto mounts with Cyanogenmod and this kernel but it didn't when I tried Omni
[Nexus 5 Original Android Development] FuMMoD:
Make sure you flash the aosp version.
[Nexus 5 Original Android Development] FredC94:
Hello people, just a quick question as I'm reading some different comments: is this kernel compatible with Vanir or CM ROMs ?

Thank you
[Nexus 5 Original Android Development] Tylog:
Use the caf one, it's for CM and CM based roms.

Tapatalk Team SlimRoms Nexus 5
[Nexus 5 Original Android Development] FredC94:
Thank you. However what does mean CAF ?
[Nexus 5 Original Android Development] Tylog:
Read there http://www.reddit.com/r/Android/comments/1rt9md/eli5_what_is_caf_why_is_cm_going_caf_affects_the/

In the op you found one kernel for aosp , one for cm.

http://xdaforums.com/showthread.php?p=47286518

Tapatalk Team SlimRoms Nexus 5
[Nexus 5 Original Android Development] danarama:
Its sort of rom dependent (in a round about way) with elementalx but not with all kernels. For example before Chaos became CAF only, it would automount even on stock - although not show in storage menu.

On slimkat, rom automounts (or rather rom allows otg in storage menu) but if you flash elementalx and choose the stock ramdisk option (replacing the slim ramdisk) automount doesn't work - however if you chose to keep the existing ramdisk (from slim) then it worked. This is academic now as elementalx always keeps existing ramdisk now. I think OP states you need stickmount with elementalx, but if you're flashing on a rom / ramdisk with automount, you'll retain the automount function
[Nexus 5 Original Android Development] nadiros:
Tapatalk/Settings/Load Preferences, and uncheck "Photos" and enjoy a smoother user experience.

BONUS! - Never, EVER have to gaze upon endless screenshots of battery stats again!
[Nexus 5 Original Android Development] le_prof:
I have been using ElementalX kernel for a couple of weeks now and I wanted to revert back to the stock kernel to make a few test and compare battery life (I am using stock rom without any other modification). So I flashed back to stock kernel using a zip file I already had (one which used to work very well). However, not everything seems to go back to stock. When I check my infos in Trickster, my min frequency is still at 1267200, but unlike when on ElementalX kernel (which in reality, goes back down to 300000), it really sticks at a 1267200 and the phone get very hot and the battery drains rapidly.

Why is that ? Doesn't flashing back to stock kernel (through a zip file) supposed to be enough ? Is there something else I need to do ? Must I flash the boot partition through the bootloader, or any other partition if need be ?

I knew there was issues between Trickster and this kernel, but I didn't think this would prevent me to go back to the stock kernel, if needed. BTW, I did reset my Trickster settings to stock too (cleared data), but this doesn't change anything. The min frequency still sticks somehow.

Thanks !
[Nexus 5 Original Android Development] El Nino1977:
Fastboot flash the latest google factory system.img and boot.img. That should clear out any system configs etc and give you a clean slate. Other than that the stock kernel mpdecision does touch boost to 1267ghz but like flars it is only a boost.