yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] maorgit:
[/COLOR]

So looks like your using correct version , I'd say your going have to wait for more users to confirm a issue or flar2 to check it out . I'm on stock version so I'm going be no help :P[/QUOTE]

flashed 31 and still no success!! trying 26
[Nexus 5 Original Android Development] notbrodie:
26 definitely won't work, that's an AOSP build. try 29.
[Nexus 5 Original Android Development] maorgit:
OK this is weird same problem on 29... returning to stock kernel :crying:
[Nexus 5 Original Android Development] notbrodie:
and this is why CM's stupid CAF fragmentation was a bad idea
[Nexus 5 Original Android Development] GavinMazey:
I'm seeing graphical glitches here and there on 32 non caf running purity.
[Nexus 5 Original Android Development] drawde40599:
Dont do that its probably something simple , What other mods do u have installed ?
[Nexus 5 Original Android Development] maorgit:
thanks for the help :) no mods! i just flashed beanstalk 255 and full PA gapps (with photosphere)
[Nexus 5 Original Android Development] FuMMoD:
I'm running beanstalk 255 with 0.32cm and have no issues at all.
[Nexus 5 Original Android Development] maorgit:
do i need to wipe anything when flashing the kernel? i didn't i just flashed the aroma zip

BTW did you check my problem? (can't turn down volume of music with headphones)
[Nexus 5 Original Android Development] FuMMoD:
Didn't wipe just did aroma. Yes I tested your problem with spotify, Di fm radio, google music, poweramp and Musicmatch. Volume works fine the only problem is that cm caf decreases volume so I boosted it with Viper4android, that's all. I listen to music everyday with poweramp so I would catch that bug if it happened.
[Nexus 5 Original Android Development] drawde40599:
Well I no for a fact 29cm works flawless with cyanogen I used it for a week before I went stock . have u looked around beanstock thread for others with similar issues ? But if I was u I would dirty flash your ROM and gapps let it boot , then go back and install 29cm make sure u choose current ramdisk ( I don't think u have option not to but if u do ... And see what happens , if still broken , backup your ROM and do a FULL wipe ( everything but SD card ) install ROM gapps let boot then go back and install 29 cm if its still broken I would post whats going on in there thread (Beanstalk) because if it works on CM it should work on every Cm based ROM including beanstock
[Nexus 5 Original Android Development] maorgit:
Thanks! tried again and still same problem!! i returned to stock kernel and no problem so its kernel related for sure!!

this is what i chose in aroma:

Set each CPU core separatly: NO

Min CPU Freq: stock 2266 MHz

CPU optimization level: elementalx

Auto UV: 750 min

thermal throttling: Default

IO :ROW

s2w s2s dt2w fullscreen power toggle s2w dt2w

usb fastcharge, enable exfat, max screen off freq, backlight dimmer

Still volume bug :confused:

---------- Post added at 11:27 AM ---------- Previous post was at 11:22 AM ----------

Thanks for your advice I tried wiping: system, cache and dalvik flashed ROM and gapps booted ( no bug) returned to recovery flashed kernel (I just wrote everything I chose) and bug is back... Full wipe will have to wait because I am at work but thanks
[Nexus 5 Original Android Development] ralpheboyo:
.....32 express...some serious power under the hood...can't wait for a few cycles to be completed....nice one!!!

Tapatalk: Nexus 5 Powered by SlimKat & FKU
[Nexus 5 Original Android Development] chris6278:
Does anyone have a mirror for .32 cm? The one posted by flar just says please wait an wont give me a link
[Nexus 5 Original Android Development] netinetinet:
I am on CM11M3 with 0.32 and everything work right...
[Nexus 5 Original Android Development] bamboosensei:
I have the same problem on Beanstalk .255 as well with both ElementalX .31 and .32 cm but I came from a full wipe since I was on stock ROM beforehand. I've also tried a dirty flash to see if it was just something on my end. Haven't checked if stock kernel was fine but if you have tested that then yeah I guess it might be something to do with CAF audio libs?

Note that, I can change the volume for everything but music apps (i.e. I can change media volume for YouTube but not say Beat, which is my preferred music app). Maybe Flar has better suggestions but otherwise, great kernel! Thanks for all your development efforts.
[Nexus 5 Original Android Development] EarlZ:
I experienced a soft reboot just now with 0.32, i dont have any uc/uv options enabled.
[Nexus 5 Original Android Development] maorgit:
FIXED!!!! as recommended i installed viper4android and in setting sound changed music effects to V4A and walla it works!!!! thanks for all the help guys of course i installed the driver and rebooted first (chose battery saver driver)
[Nexus 5 Original Android Development] shhbz:
Remove dsp manger from inbuilt system app remover or titanium and reboot so it does not conflict anytime later and you can chose the best sound mod as it does not drain battery as u are expecting it to be and njoy the thumping sound with very least drainage

And install viper as system app placing it under system/private-app and setting permission or can share a zip which will directly do that and viper will rock without any hickups
[Nexus 5 Original Android Development] flar2:
Thanks! Much appreciated
[Nexus 5 Original Android Development] flar2:
perhaps beanstalk is somewhere between CAF and standard AOSP

there are so many patches out there, every kernel seems to have a different combination

Kernel usually causes a hard reboot
[Nexus 5 Original Android Development] The-Droidster:
What kinda graphical glitches? Please elaborate.
[Nexus 5 Original Android Development] ak4d4:
Oops... I'm on beanstalk and didn't flash caf cause I had volume issues. No problems here on the regular one..

Sent from my Nexus 5
[Nexus 5 Original Android Development] tlf55:
Had some hard reboot with the same settings that I had on 31 .. (Same uc and UV )

"Envoyé depuis mon Nexus 5 avec Tapatalk"
[Nexus 5 Original Android Development] Savant:
What ROM are you using ? I've been using slim 3.4 with the latest elemental kernel and everything works like it should and no bugs.
[Nexus 5 Original Android Development] flar2:
version 0.32 has a lot of changes to regulators and drivers, it might not be able to handle undervolting as much.

/proc/last_kmsg if it happens again.

I'm not seeing this on mine, running 0.32 with Cataclysm. Version 0.31 is same as 0.26 except I changed the backlight dimmer steps and a small fix to the power button toggle. I don't think the backight dimmer would cause this, but do you have it enabled? Otherwise, there shouldn't be any difference between 0.31 and 0.26 for something like this. Maybe wipe your caches and use stock voltage.
[Nexus 5 Original Android Development] bobby janow:
Very nice, it feels good too. And to your post, you have embarrassed me somewhat. I am so excited about this kernel and its performance that I totally forgot to donate. Since been corrected. <smack> Thanks I needed that.
[Nexus 5 Original Android Development] flar2:
Something like that's not going to show up in a log. I don't think there's anything I can do about it. It doesn't happen on my phone, and I didn't make big changes to graphics (even on 0.32). The kernel is essentially stock when it comes to graphics. All I can suggest is wiping and trying a clean install.
[Nexus 5 Original Android Development] letmedanz:
Confirmed working as advertised on Beanstalk latest (.255) version.

No volume or graphic issues
[Nexus 5 Original Android Development] flar2:
Back up your important apps, contacts and texts, factory reset, clean install. Then when you've got it reinstalled perfectly clean, apps updated, etc, do a nandroid backup so you'll always be able to get back to a clean state.
[Nexus 5 Original Android Development] letmedanz:
Maybe you could try without the Adreno drivers?

that could be causing some compatibility issues?
[Nexus 5 Original Android Development] flar2:
I've been running Cataclysm for long time.
[Nexus 5 Original Android Development] FuMMoD:
Beanstalk 255 with 0.32 with stock settings and row with 512 read ahead. This thing idles like a beast.
[Nexus 5 Original Android Development] flar2:
I had 0.1% per hour drain last night, that's the best I've had ever on any phone.
[Nexus 5 Original Android Development] hilltruange:
Have been running .32 for a while, seems a lot more smooth than. 30.
[Nexus 5 Original Android Development] adio201:
.32 caf not working with pacman lates nightly
[Nexus 5 Original Android Development] ak4d4:
Maybe bad download?

Sent from my Nexus 5
[Nexus 5 Original Android Development] flar2:
What's the problem?
[Nexus 5 Original Android Development] drawde40599:
Only with this kernel u said ?
[Nexus 5 Original Android Development] drawde40599:
If it's doing with or without the kernel and different Roms its time for some diag , and since full wipe isn't working , u should probably flash back to Google IMG get your phone back to factory status if still happening its time to use that warranty ;) good luck
[Nexus 5 Original Android Development] bobby_sucker:
really excited about the 32nd version

btw, if i wipe cache/dalvik, would it be sufficient to flash the kernel? Or there is a necessity to reflash the current ROM as well?

Thx in advance!
[Nexus 5 Original Android Development] adio201:
Get stuck in Google logo bootloop
[Nexus 5 Original Android Development] rickyx32:
Have you tried flashing Google's factory image yet? There's a sticky in the Nexus 5 General forum.
[Nexus 5 Original Android Development] flar2:
Unless you've flashed a different kernel, you can just install it.

I don't know anything about pacman, whether you need the CAF or AOSP version. Make sure you choose stock frequencies and voltages.

Is anyone else using pacman? Maybe someone could confirm if it works or not, and which version of the kernel is needed.
[Nexus 5 Original Android Development] flar2:
Oh sh*t, I was going to add f2fs support, but I totally forgot.
[Nexus 5 Original Android Development] Schemerlamp:
Doubletap2wake doesn't work during phonecall
[Nexus 5 Original Android Development] kmar22:
Running really smooth so far on latest beta. Well done as always.
[Nexus 5 Original Android Development] walpurgisnacht30:
Finally tried this kernel on my Hammerhead. Loving the swipe2wake ability, not really care with the battery life since I still can get 8 hours in one charge only :D

Anyway, when I tried to enable fast charge function from 0 to 1 and reboot once I checked the script, it reverted back to 0 again, is it normal?
[Nexus 5 Original Android Development] Chochiwpg:
Make sure you make the change in the /etc/elementalX.conf file.

There is another file with the same name in a different location that will get over written with each reboot. If you change the settings in the file location specified above, they will stick on reboot.

http://xdaforums.com/showpost.php?p=50567503&postcount=4046
[Nexus 5 Original Android Development] JmPTaz09:
Anytime there is a "hack" involved, it may be a prime culprit...
[Nexus 5 Original Android Development] letmedanz:
Lol.. so that only means "people watch out for v0.33 in 4...3...2...1...."

:P
[Nexus 5 Original Android Development] walpurgisnacht30:
Yes, I change in the /etc/elementalX.conf file. But, twice tried to change it, still reverted back.
[Nexus 5 Original Android Development] Chochiwpg:
What app/program are you using to make the change?

I use ES File Explorer. Make sure you have Mount Read/Write enabled for / and /system. Then you should be able to save changes in the conf file.
[Nexus 5 Original Android Development] DarkFantasy6:
Where to download beta releases? :D

Gesendet von meinem Nexus 5 mit Tapatalk

---------- Post added at 06:48 PM ---------- Previous post was at 06:47 PM ----------

And are they working on aosp or is it caf? :)

Gesendet von meinem Nexus 5 mit Tapatalk
[Nexus 5 Original Android Development] Tylog:
http://xdaforums.com/showthread.php?p=50827608

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] walpurgisnacht30:
I'm also using ES File Explorer, I think it's already enabled since I can change the swipe2wake settings from 0 to 1 and also change the power key toggle settings.

Not sure why the fast charge settings always reverted back :eek:
[Nexus 5 Original Android Development] DarkFantasy6:
Thank you very much! :)
[Nexus 5 Original Android Development] shhbz:
Flash your recovery once again and then try a clean wipe maybe try another recovery from the one u using now . i tried .31cm on beanstalk and mahdi and both works fine even i flashed .31 aosp kernel on mahdi by mistake and all was good still.

So its working on both roms wanted to try .32 or maybe .33 but just loving the battery backup and smoothness of .31
[Nexus 5 Original Android Development] shhbz:
But u said it was working fine earlier if it still shows that sign after a fresh and changed recovery then definitely a hardware issue
[Nexus 5 Original Android Development] GavinMazey:
I had similar issues when I flashed the kernel on purity last night. I was getting scrambled colors in the top 8th of the screen when backing out of apps. Flashed back to 31 last night before bed and then decided to flash 32 again this morning and I haven't seen the glitches again. Only thing different flashing the second time was to undervolt 300mhz at 750 instead of 725 which has worked fine up till now. I'll report back later today if I see the glitches again. If not I'll undervolt again tonight to 725 and see if I can reproduce. Thanks for the best nexus kernel flar.

Also scrolling in tapatalk with version 32 is super smooth but Swype seems to be lagging a bit but not sure i can say it's kernel related cause happened before on different kernels
[Nexus 5 Original Android Development] DarkFantasy6:
what is the difference between express and normal version? :D
[Nexus 5 Original Android Development] A_Button117:
Whether or not it uses the aroma installer in recovery

Studying Computer Science and Forensic Science @ UCO

Using XDA Premium 4
[Nexus 5 Original Android Development] cc16177:
My understanding is that express is just a zip flash with default setting and "normal" version allows you options in aroma installer.
[Nexus 5 Original Android Development] Koersten:
You're absolutely right:)
[Nexus 5 Original Android Development] DarkFantasy6:
Thank you very much guys!!! :)
[Nexus 5 Original Android Development] adio201:
I been using this kernel since I got my hands on pacman ROM and has always work previous build .31 works fine but I try the new update I get stuck in Google logo bootloop and I even try the previous version of pacman that I knew elemental kernel work and same thing bootloop but only with lates kernel build
[Nexus 5 Original Android Development] mbwsutherland:
So I'm ready to give it a go lol. Should this work fine with stock rooted N5? It just keeped rebooting Google boot screen I'm I missing something or should I try some different setting through aroma? Just curious on some feed back

Thabks
[Nexus 5 Original Android Development] tsubus:
using 0.7. Is MTP broken? can't seem to connect phone to PC after switching kernel (tried both with FC enabled and disabled)

edit: adb also not working, worked fine previously and still works fine in recovery
[Nexus 5 Original Android Development] davidbar93:
Did you flashed it in CWM? Try to flash it with TWRP 2.6.3.2 ,for me it works like charm.
[Nexus 5 Original Android Development] mbwsutherland:
Yeah of course lol I'll re try of course thanks
[Nexus 5 Original Android Development] kamaliqwan:
everything is crashes on DroidKang V5

system ui just disappeared..
[Nexus 5 Original Android Development] Lancez:
Flash stock kernel boot phone, then flash 0.7

Sent from my Nexus 5
[Nexus 5 Original Android Development] flar2:
I have busy day today, so a couple quick answers and I will read through the last few pages tonight.

Screen on notifications will reenable s2w if you are using the power button toggle.

I might switch back to reusing existing ramdisk, but some people were having trouble with that too.

More later...
[Nexus 5 Original Android Development] kamaliqwan:
do u have flashable zip for the stock kernel?

just found the boot.img.
[Nexus 5 Original Android Development] Lancez:
http://xdaforums.com/showthread.php?t=2518816

Sent from my Nexus 5
[Nexus 5 Original Android Development] kamaliqwan:
thanks a lot man..but still no go...:(

kinda weird..i got the same error when im on ElementalX..

maybe something is different on DroidKang rom..
[Nexus 5 Original Android Development] Batfink33:
I thought droidkang was Cm based and only compatible with bricked?
[Nexus 5 Original Android Development] kamaliqwan:
yes droidkang is cm..
[Nexus 5 Original Android Development] staymunch:
0.7 is causing bootloops on PsX rom, even after full wipe. 0.5 was running great tho.
[Nexus 5 Original Android Development] Alfonso87:
Guys can you post some battery screen shots pls? How much SoT can you get with 0.7? I would link to know the use of the phone also, if you are on wifi or 3g or LTE, ect.
[Nexus 5 Original Android Development] flar2:
Should be no difference. The only change was the screen wake stuff.

It looks like I'll have to go back to using the ramdisk though
[Nexus 5 Original Android Development] tsubus:
Can anyone confirm or deny this? I still cannot connect to my phone neither from ADB nor from MTP after switching to this kernel.
[Nexus 5 Original Android Development] GSLEON3:
Nope. Works fine here. I've noticed on 4.4 driver reinstalls are commonly needed, even with stock kernel. It will not recognize & then you need a restart or to manually change the driver in device manager.

Try switching to ptp then back to mtp, or switch ports.
[Nexus 5 Original Android Development] tsubus:
I'll try that when I get back home. Weird thing is that it works just fine from recovery, and before it also worked with stock kernel and faux kernel. I'll try your suggestion tonight and leave feedback.
[Nexus 5 Original Android Development] MrFishiz:
I flashed 0.7 and I am using Psx, working flawlessly.
[Nexus 5 Original Android Development] Alfonso87:
[MENTION=4684315]flar2[/MENTION] Your switch off for dt2w and s2s seems great. I'm tring to test it, to see if the battery gain some more lifetime :D From now it seems to work perfectly, more battery saved when you "switch off" your phone with the power button. The dt2w feature is still perfectly working and useful, for example while browsing. You are smart man :D
[Nexus 5 Original Android Development] FuMMoD:
So you tried flashing the cm version of elemental before posting right? I would try the cm version first and then the regular version.
[Nexus 5 Original Android Development] flushell:
Say what? Maybe you should read what you just wrote before submitting.
[Nexus 5 Original Android Development] notbrodie:
that's not a bug, it's a feature. lot's of people were having issues with phantom touches during phone call, solution was to disable touch2wake features during that tiem
[Nexus 5 Original Android Development] GavinMazey:
Probably not what you want to hear but sounds like a hardware issue as others have mentioned.

I'm thinking that pacman might need the stock/aosp kernel because it's labeled aosp in the title the pacman thread. Good luck.

Edit... If you read the pac thread it seems most people are having issues with custom kernels.
[Nexus 5 Original Android Development] drawde40599:
R u undervolting first step during install ?
[Nexus 5 Original Android Development] hooliganx:
Oi!

Im very interested in this kernel. since I see some comments about in [MENTION=3685904]ak[/MENTION] mako thread ;)

But try flash with Slim and simple don't boot.

I try 0.31 (or 0.32,don’t remember right nowl.

should I try another version?

I bought N5 yesterday. root, flash twrp, flash slim, boot, setting, reboot in recovery, flash Elementalx, bootloop.

:what:

thanks for help.

N5*SlimKat.b3.4*Faux.10m*ART*TWRP.2.6.3.4*0.23
[Nexus 5 Original Android Development] GoldElocks:
I believe Mahdi is AOSP based with CM features integrated - no CAF, therefore the AOSP version should be the proper one to flash. Somebody correct me if I am wrong.
[Nexus 5 Original Android Development] gippy2:
Have you flashed the right version aosp? I'm on slim and both 31 and 32 work fine.....
[Nexus 5 Original Android Development] Scallywag1:
Correct
[Nexus 5 Original Android Development] r0cky0790:
Flashed 32 and out the gate phone is perfectly responsive with Row and Elementalx governor. Running CM.
[Nexus 5 Original Android Development] aamitabh28:
Came across a weird problem.

The ram bar on beanstalk shows a different value than that in settings menu or monitored through system monitor

---------- Post added at 01:30 AM ---------- Previous post was at 01:29 AM ----------

Same can be observed with the ram circle on bottom left
[Nexus 5 Original Android Development] shhbz:
Thanks for the info as me to considered it aosp based but mu friend argued it to be cm and due to lack of time from work cant check out as even in op its stated about franco kernel and stuff and same info.

Thanks for sharing n rectifying

Edited: flashed .32 now and yes can really feel it more snappy now lets see how it reacts with rom and stuff
[Nexus 5 Original Android Development] AquilaDroid:
I'm on 32 with Slim 3.4 weekly, everything is great. Maybe when Flar reads all these posts he'll think again about trying to keep up with CM based roms...

From my Nexus 5
[Nexus 5 Original Android Development] bobby_sucker:
Guys, ElementalX governor is more battery friendly than Ondemand?
[Nexus 5 Original Android Development] shhbz:
ElementalX provides the best combo of battery and performance for sure.
[Nexus 5 Original Android Development] nadiros:
That is correct :thumbup:
[Nexus 5 Original Android Development] JmPTaz09:
Man, .32 is running in beast mode on Illusion ROM! Fast and smooth in all areas and sipping battery like none other. Screen at 20% brightness (could obviously get even better stats but like the vibrant screen at 20):
[Nexus 5 Original Android Development] rhamej:
CAF or Stock with Slimkat?

I have been on Purity for a while and wanted to try something different. So I flashed the latest stable of SlimKat. On Purity, I would flash the non-CAF kernel. Doing a little research I read that I should flash the CAF one. I did and no problems. But then after reading the SlimKat thread some more, I found out I was supposed to flash the non-CAF one. So I did. And again, no problems. This was done both with the latest, 32. So which is it? CAF or non-CAF? And why is it neither one of them threw me into a bootloop? :confused:
[Nexus 5 Original Android Development] JmPTaz09:
Oops, second pic didn't come through:
[Nexus 5 Original Android Development] Tylog:
Correct , our base is aosp so you need the non caf :)

Tapatalk Team SlimRoms
[Nexus 5 Original Android Development] Munkee915:
Flashed this today but NTFS support seems to be read only. Is there something else I need to do to get write? I'm using stickmount and tested through ES Explorer, Total Commander and Root Browser.
[Nexus 5 Original Android Development] flar2:
I think it's selinux preventing you from writing. Try typing setenforce 0 in the terminal as root.
[Nexus 5 Original Android Development] Munkee915:
That worked. Is this going to stick or will I have to do this whenever i reboot my phone?
[Nexus 5 Original Android Development] kidrobot52:
OK I'm still on .26 since I got Nova Prime. And I must say amazing now if I wasn't to update to. 32 can I just flash it?

Also not to get off topic but any one see less of a battery drain without using gravity box? I turned it off and my stats doubled. Maybe a placebo

sent from Nova Prime
[Nexus 5 Original Android Development] kidrobot52:
Regular usage (Facebook, XDA, motocross, Google now enabled, location battery saving) hopefully updating will double this for me.
[Nexus 5 Original Android Development] PetritH:
I didn't understand your question at all, every xposed module drains battery more than w/o it.
[Nexus 5 Original Android Development] FuMMoD:
False. I got 5 hours idle with not even 1% drain and I have around 12 modules and on LTE.