yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] djsubtronic:
Not with #20. Kept auto rotate activated and rebooted, after a few mins the sensor stopped working as it did before.
[Nexus 5 Original Android Development] rockknee:
It's not just camera. It's everything that rotates. Menus, apps, camera apps (google, aosp...you name it). At least I have experienced it like the whole system doesn't recognize orientation sensor anymore. Logcat spamming has something to do with that for sure, but it's really weird how some users including myfluxi don't have this problem. Caf17 works fine for me so some change between caf17 and caf18 made the rotation broke.
[Nexus 5 Original Android Development] djsubtronic:
Yeah this it it. The entire system fails to recognize/activate the accelerometer a few minutes after booting up.
[Nexus 5 Original Android Development] RTNDO128:
Can another thread be started for these CAF builds? I appreciate myfluxi and all his hard work, but it's a hassle to sift through this thread and read about bugs pertaining to the official CM nightlies with all the CAF posts here.
[Nexus 5 Original Android Development] topgeardave:
Nightlies have minimal issues in my experience. Not had a problem since the weird play store wakelock drain two months ago
[Nexus 5 Original Android Development] kong:
It will become official nightly soon.
[Nexus 5 Original Android Development] boxcar8028:
+1
[Nexus 5 Original Android Development] RTNDO128:
I had no idea, haven't heard anything about it. That's good then, assuming it doesn't cause any issues. I think I've seen posts mentioning that if you're going to flash the CAF builds myfluxi has been posting, you need to do a clean wipe. Is that also going apply when these "unofficial" CAF builds become official nightlies?
[Nexus 5 Original Android Development] one7dchevy:
Is that right? I don't remember this coming from myfluxi..
[Nexus 5 Original Android Development] myfluxi:
New kernel from scratch that will do away with all the crap that started in January. CAF will maybe remain a (n awesome) personal project, it' too time consuming for official. Sorry for abusing this thread, I really underestimated the pitfalls.

Please read this carefully:

* This kernel image is made for NIGHTLIES and M RELEASES, not CAF

* It was put together in one night so please don't bother me with **** like "bootanim is choppy" or "omg, dis si not smooth, plz fix asap"

* Some stuff is missing, like color calibration, gamma tweaking works though

* This baby will fly once some basic tweaking takes place, so pls stay away with Antutu crap

* I am only interested if graphics are fine

* I am only interested if things like camera or BT don't work as expected

Download: 141026_kernel_NIGHTLIES_and_M.zip

This will be official within a few days, I guarantee that. And we will be prepared for L better than everyone else.

Edit: Even the source is there so rapage can start *now*.
[Nexus 5 Original Android Development] bjoswald:
Bummer that CAF won't be official. Oh well. A joy to use for now.
[Nexus 5 Original Android Development] procitysam:
Will this also bring a fix to the SoD's?
[Nexus 5 Original Android Development] myfluxi:
This will fix all kinds of SODs, horrific graphic glitches, BT, kernel panics and the latest bugs with audio in certain games and other occasions. Basically everything that was caused by mixing and matching code. It will not however fix bad userspace commits, such as the the flip thingie and other abuse of sensor code.

To give you an impression about the insanity of all this: one single HAL commit from January, the one the that made AOSP basically incompatible takes onefrigginhundredandthirty kernel commits for compatibility.

I wanna wake up and be sure nothing is broken because of new incompatible patches everywhere. Thank god, our old codebase will probably be left alone.
[Nexus 5 Original Android Development] bjoswald:
Are you sure you can't find the extra time? You seem more engaged than ever.
[Nexus 5 Original Android Development] procitysam:
Sounds amazing man, keep up the good work :good:

The fix will work on M11 right? Or by M does it mean future M releases?
[Nexus 5 Original Android Development] Corintio:
Would love to try this new kernel. Is it ok if I dirty flash the latest nightly over CAF19 in order to do so?
[Nexus 5 Original Android Development] aldyu:
Yes, you can.
[Nexus 5 Original Android Development] procitysam:
Has anyone found any problems in the new kernel?

EDIT: Works awesome on the nightly from the 23rd :D no SoD since I flashed about am hour ago

EDIT 2: Even more good news, AnTuTu was even better than the original score. It went from 34000 to 37000 on ART. Awesome work!
[Nexus 5 Original Android Development] mbellot:
Nice to see you back. :good:

Just dl'ed and installed 102614 + your kernel, dirty flashed over 101614 stock (CM11/kernel + a few apps).

First problem I ran across is wireless charging. Stock CM11 lights the LED orange when charging, I get a momentary blip (green maybe) and then the LED shuts off.

No graphics issues, but I don't do a lot of video streaming. Will test BT in the car tomorrow morning.

Thanks for all your effort.
[Nexus 5 Original Android Development] alevbozzi:
to me happens that wireless charging while phone is off doesn't work, the screen remain on with the battery icon
[Nexus 5 Original Android Development] djsubtronic:
[MENTION=4152171]myfluxi[/MENTION], would you recommend migrating from CAF builds to official nightlies using your new kernel? Or will the CAF builds continue as well?
[Nexus 5 Original Android Development] procitysam:
I got the same charging light problem. I changed my charging light color to a blue-ish color and it did the same thing.

Also the default notification light color, which is set to white, is my charging color now, which is weird. I checked settings and it's still white but it flashes the charging color.
[Nexus 5 Original Android Development] Gregorypac:
Question?

Hi to all

I'm having trouble with my CM11 doubt is when I install the CM11 nexus 5 when the load is plugged minutes after screen not lock?
[Nexus 5 Original Android Development] mbellot:
Charged (green) was not lit up this morning.

My notification light (blue) seems to be OK.

BT seems unchanged, my car works for everything but MAP functions (text messages) which it should work for, but never has on CM11.
[Nexus 5 Original Android Development] dannyella:
Probably dumb question...will the new kernel fix incompatibility with AOSP kernels?
[Nexus 5 Original Android Development] procitysam:
Yeah my notification light works but the charging light doesn't work right.
[Nexus 5 Original Android Development] bjoswald:
I just fell in love with the CAF builds and now there's a new kernel?! Choices...
[Nexus 5 Original Android Development] andrei1015:
I just saw an experimental build. Is it the build with the new kernel?
[Nexus 5 Original Android Development] vamshi2007:
Noob Question

i switched from purity rom to cyanogenmod and i feel a slight lag in the general UI

while switching homepages or opening apps

is it just the animations or is it like that itself or is it just me :confused:
[Nexus 5 Original Android Development] procitysam:
Did you dirty flash it or clean flash?
[Nexus 5 Original Android Development] comscier:
Update to the newest version of CM.

Then, turn off some of the "Google features".

(Do not disable them or you may end up in boot loop, just turn them off in Google Settings > Turn off location reporting and history and Location Settings> Device Only)

If you use all google services, expect to have to charge your phone twice a day.
[Nexus 5 Original Android Development] Chris123NT:
Do you have a bad signal where you normally are? That could be it. Either way, post some BBS stats when you have enough information to give a decent sample of what's going on.

Remember to enable root features in BBS and install as a system app so you can see everything, including partial wakelocks.
[Nexus 5 Original Android Development] kellybrf:
Am I just missing it, or can you not set a separate lock screen wallpaper?
[Nexus 5 Original Android Development] detdett:
You're just missing it
[Nexus 5 Original Android Development] kellybrf:
Super helpful
[Nexus 5 Original Android Development] detdett:
Thank you
[Nexus 5 Original Android Development] kong:
I'm on the latest nightly and don't see any option to set the lock screen wallpaper :/
[Nexus 5 Original Android Development] Jsparta26:
I was wondering if cm will eventually offer full theme support for themed battery icons. I sure miss the batt icon for subzero theme. I spoke with the dev and what he told me its coded in there its a cm and kit kat thing. I'm just asking of its in the works for the future. Would love to see it happen. :)
[Nexus 5 Original Android Development] marcusva79:
I thought it was already added
[Nexus 5 Original Android Development] Jsparta26:
They added the color theme code. I'm talking about having a completely different batt icon when the theme is applyed.
[Nexus 5 Original Android Development] juancaperez2000:
Hello im about to flash CM 11 M2 and this going to be my first cm flash on my new N5 and want to check how stable is that version, asking this trying to be avoid of flashalholic lol thanks for your help
[Nexus 5 Original Android Development] detdett:
Very stable
[Nexus 5 Original Android Development] juancaperez2000:
Thanks, ill flash it now
[Nexus 5 Original Android Development] marcusva79:
Just give the newest nightly a try. No issues on my side. Kernel works a lot better. Also I know someone wanted to CM wallpapers. Which one in particular?
[Nexus 5 Original Android Development] kong:
I'd say flash the latest Nightly (20140119) instead of the M2. There are so many fixes since the M2, especially with the kernel :highfive:
[Nexus 5 Original Android Development] juancaperez2000:
Thanks, kernel is not a big deal im planning to flash custom one thanks for your response
[Nexus 5 Original Android Development] LamboBull:
trust me, flash nightly. No huge difference, and it is really stable.
[Nexus 5 Original Android Development] anton79ru:
As was said b4, the 19 nightly is totally stable. What I did a few nightlies ago is install MultiROM and flash CM alongside with the stock ROM to see the difference, tell CM bugs from global bugs, and revert to stock in case something went wrong. I would encourage you to do the same also because it's fun.

---------- Post added at 11:27 AM ---------- Previous post was at 10:51 AM ----------

From what I see there, the removal of transparency on the bottom half is to avoid an earlier and more serious bug until that one is fixed. Is this understanding correct?
[Nexus 5 Original Android Development] koelspy:
Same here (2014-01-19 nightly), you can trigger this problem by pressing POWER + VOLUME UP + VOLUME DOWN.
[Nexus 5 Original Android Development] LamboBull:
To fix the superuser problem, go to Settings>Superuser>Settings>Notification>None.

Sent from my Nexus 5
[Nexus 5 Original Android Development] hanschke:
cm-11-20141027-EXPERIMENTAL-hammerhead.zip

anyone knows why :confused:
[Nexus 5 Original Android Development] procitysam:
[MENTION=4152171]myfluxi[/MENTION] not sure if this is a ROM bug or a kernel bug, but when I click the camera widget button on the lockscreen, it seems like systemui crashes. It resets my background to the default CM background as well. I'm on the nightly from the 23rd and using your SoD kernel fix.
[Nexus 5 Original Android Development] bray424:
Wondering that as well, or even just a link to wherever the cm team usually announces this sort of thing, as its not on the changelog site.
[Nexus 5 Original Android Development] telep:
I tried several times to use cyanogen but i can not stand laggy and stuttery UI.
[Nexus 5 Original Android Development] vamshi2007:
I clean flashed it

---------- Post added at 12:12 AM ---------- Previous post was at 12:09 AM ----------

Same here my friend :)
[Nexus 5 Original Android Development] swat4samp:
Use elementalx kernel, no offence to myfluxi but your new kernel too lagged :(, tried changing various parameters, but still no good. Custom caf kernels like elemental and code blue runs smooth.
[Nexus 5 Original Android Development] ssauger:
i take some time to tweak it. cool down
[Nexus 5 Original Android Development] lolobarjo:
After a half day of test it work good for me

It work very well with the last nightly. Graphics seems buggy at the start but after few minutes all run pretty smooth. I don't see graphical glitch when I play movies or video games. For the Bluetooth I test during almost 2 hours (music and calls) and I haven't encountered bug.

Good job man ???

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] topgeardave:
Anyone know why cm have refused the [MENTION=4152171]myfluxi[/MENTION]s caf builds? I had no issues when I tested the latest build.

Also will the audio offload processing be available in the new kernel when Google open source the blobs? :)
[Nexus 5 Original Android Development] Sultanxda:
CM didn't refuse, it's just that we ran into some roadblocks that couldn't be easily fixed while using CM's official repositories. For example, the newer display HAL from CM, display-caf-new, has a lot of inconsistencies and graphical glitches that can't be easily fixed. There are three known nasty graphical glitches with display-caf-new, and I'm sure there are other minor bugs as well due to mixing and matching code from different CAF branches.

By switching back to our old HALs we can avoid new upstream regressions (and headaches) that the CAF HALs experience on a regular basis (as our old HALs are rarely touched).
[Nexus 5 Original Android Development] procitysam:
Never mind [MENTION=4152171]myfluxi[/MENTION] the camera bug was on that nightly. I went back to M11 and flashed your fixed kernel and all is good again. :D
[Nexus 5 Original Android Development] caliban2:
So whatever they were trying with the experimental build today - screen rotation is broken. Apart from that it seems fine. :rolleyes:
[Nexus 5 Original Android Development] bjoswald:
Agreed. I have a been using a backup copy of M11 + ElementalX and it feels just as smooth.

Why bother coming back here every few hours, hoping for a new build, when I can just flash an upgrade from within CM, drop in a new kernel, and be done with it? If CAF becomes official, well, that's another story...
[Nexus 5 Original Android Development] claudeman:
Anytime I use the kernel on the CM nightlies or the when I used the CAF rom I got random reboots where my phone suddenly freezes and reboot.s When I use elemental, this doesn't occur even when I do the exact same thing as when it rebooted with the CM or CAF kernels.

Is there a reason why this is happening to me? I didn't seem to find that this issue is happening to anyone else so should I just do a clean install?
[Nexus 5 Original Android Development] topgeardave:
Could you try and capture a kmsg next time you're next to a pc?

Or download Andy log, wait for a hard reboot to happen then open app and dump the last_kmsg and upload here.
[Nexus 5 Original Android Development] claudeman:
Okay I'll be sure to try and get one.
[Nexus 5 Original Android Development] claudeman:
okay, here it is.
[Nexus 5 Original Android Development] vamshi2007:
I did try using it with elementalx and also code blue , but i still find no difference
[Nexus 5 Original Android Development] lolobarjo:
Nop

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] andrei1015:
Is rotation broken or is it just me? Tried on both CM normal kernel and [MENTION=4152171]myfluxi[/MENTION]'s new kernel..
[Nexus 5 Original Android Development] myfluxi:
some people can't even read the basic instructions. I have to ask myself, why. [MENTION=1591612]TopGear[/MENTION]: I wasn't refused or rejected, nobody even bothered... ;)

This file hacks around the useless HAL changes from January, the stuff that a) makes us incompatible with AOSP and b) indirectly introduced the higher mem usage, known as "cam stutter bug". It should be almost feature complete, the goal is still to have a full (the best!) CM with the least amount of changes from AOSP as possible. L, here we come, Kim and friends are doing amazing minimal work again. Consider me founder and president of the first Devin Kim Fan Club.

Download: 141028_kernel_NIGHTLIES_and_M.zip
[Nexus 5 Original Android Development] kong:
Since you removed the link to CAF builds in your signature, can we imply that there won’t be future releases and we should stay with official Nightly?
[Nexus 5 Original Android Development] myfluxi:
Like talking to a wall.

But hey, pain is temporary, glory is forever.
[Nexus 5 Original Android Development] :
adrogantia
[Nexus 5 Original Android Development] kong:
So I guess this means you’ll STOP releasing CAF builds? Maybe my English is too bad lol :silly:
[Nexus 5 Original Android Development] neobuddy89:
Yes. Something like this perhaps..

and all fans are like

Just cheering up the mood.. :P
[Nexus 5 Original Android Development] procitysam:
Flashed the new kernel. Is there much difference between the first fix and this one?
[Nexus 5 Original Android Development] myfluxi:
No seriously, it's all good. CAF is now a personal thing, maybe with some potential. I learned so much in the process, not just about the software, also about how to handle things and how not to handle things. And about what to expect and not expect.

Keep your fingers crossed that everything is smooth with the new approach. The kernel is really the most unimportant thing in the chain, as long as it works and supports userspace functions. Learning from LGE is learning from the best.

Yes. And if you don't notice it, it worked :)
[Nexus 5 Original Android Development] topgeardave:
Thanks for the reply mate :) Is the experimental build from cm contain your latest kernel?
[Nexus 5 Original Android Development] myfluxi:
I have no idea what it is.
[Nexus 5 Original Android Development] topgeardave:
Kinda coincidental how it released on the first day you released your kernel, kinda gives the impression it's your kernel haha. It's pretty weird how no sources from cm have been updated to coincide with the experimental release so nobody knows what it is
[Nexus 5 Original Android Development] procitysam:
The only differences I've noticed is it's a more laggy after boot and it takes a little longer for the screen to turn back on.
[Nexus 5 Original Android Development] nictki:
Does anybody notice on latest nightly (27-10), that some sensors are "missing" (light, proximty)

??
[Nexus 5 Original Android Development] myfluxi:
This will be taken care of, as it affects CM as a whole. I got hit by that as well but it was almost 3am again and I wasn't able to think clearly any more. ;)
[Nexus 5 Original Android Development] AndroidBR:
Way OT... Sorry...

Is it just me or Google Play Services are a little unreliable today? I can't keep my Chromecast videos playing and most of my Hangouts calls are dropping... Anyone experiencing this as well?
[Nexus 5 Original Android Development] mmo.xda:
I think is being addressed by Steve:

core: Correct the sensors UID

:rolleyes: :rolleyes: :rolleyes: :rolleyes:

Regards
[Nexus 5 Original Android Development] aldyu:
[MENTION=4152171]myfluxi[/MENTION], nice new signature ;)
[Nexus 5 Original Android Development] Isidorosis:
[MENTION=4152171]myfluxi[/MENTION] Will we get a last CAF build with the sensors working (when that's fixed) ?

Cause the ROM for me works perfectly fine (except the sensors bug :P ) and i would like to wait with caf until L comes

Thanks for your work !
[Nexus 5 Original Android Development] provolinoo:
Hi guys,

I just realized that is no more possible to disable some system app as Gallery and File manager in latest builds, the disable button is greyed out

why that? I remember it worked previously

how to fix?

Thanks a lot
[Nexus 5 Original Android Development] andrei1015:
Another mysterious experimental build emerges from the dark :eek:
[Nexus 5 Original Android Development] topgeardave:
Found out what they are now. Taken from official cm forum:

"Experimentals are part of the milestone releases. These releases are tested a bit before they are released and are the first releases that CM allows to be used for official bug reports onhttps://jira.cyanogenmod.org

They should be more stable than nightlies."
[Nexus 5 Original Android Development] bray424:
Just delete them in recovery. If you're worried about needing them later, just change the .apk extension to .ap.
[Nexus 5 Original Android Development] provolinoo:
sadly this is not a working solution :(

I know how to delete app using a file manager but if I did that those apps would be back on every new rom flash (I flash nightlies every a few days) and I would do that every time

this is why I prefer to disable apps, since disabled status is kept even after a rom update
[Nexus 5 Original Android Development] :
Freeze them in titanium backup and it will stick
[Nexus 5 Original Android Development] mbellot:
Just delete them from the ZIP.

I do it with a handful of apps like Term (prefer ConnectBot) and WhisperPush.

Ten seconds of effort, no muss, no fuss.
[Nexus 5 Original Android Development] aldyu:
Create a flashable zip that will delete those apps, flash it after every rom update.

Sent from my Nexus 5
[Nexus 5 Original Android Development] andrei1015:
Rotation still doesn't seem to work. General problem or only me?
[Nexus 5 Original Android Development] razorloves:
Yeah, just flashed 29th nightly. Sensors still broken.
[Nexus 5 Original Android Development] lolobarjo:
Works good on 26th nightly with latest myfluxi kernel

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] mainicia:
yep. back to 26th for now and wait for fix in the next day
[Nexus 5 Original Android Development] AndroidBR:
Here's what I sometimes get when going through the menus in Recovery when flashing a nightly... :(
[Nexus 5 Original Android Development] dannyella:
Is proximity sensor working with [MENTION=4152171]myfluxi[/MENTION]'s kernel?
[Nexus 5 Original Android Development] topgeardave:
Recovery problem mate as it uses its own kernel. Ask Cwm or twrp threads about how you can debug it
[Nexus 5 Original Android Development] myfluxi:
The problem is on a higher level and affects many CM devices, even the OnePlus One, so this must and will be fixed for everybody. When? Dunno. We could hack this but won't... In the meantime use the last known good 20141026 nightly.

Fyi, I requested test/nightly builds with the updated kernel that fixes all the things. Plase don't ask for ETAs.
[Nexus 5 Original Android Development] mmo.xda:
Thanks for your effort. You're awesome :)

Regards
[Nexus 5 Original Android Development] procitysam:
Yeah the sensors on my brother's G2 stopped as well.
[Nexus 5 Original Android Development] mainicia:
I think it came from

[system: core: Add Sensors group]

on 20141027

hope they can fix soon ;)
[Nexus 5 Original Android Development] myfluxi:
I was talking out of my butt ;)

http://review.cyanogenmod.org/#/c/75774/
[Nexus 5 Original Android Development] provolinoo:
app freezing worked like a charm, thanks for the suggestion!

btw, I found out the disable works if I disable the app directly from terminal emulator even if the disable button is greyed out
[Nexus 5 Original Android Development] procitysam:
Not sure if anyone else is having this sort of issue, I'm assuming you do because my brother's G2 has the same problem. When you unlock the phone, the navigation bar does not have the gradient that its supposed to have so that the buttons maintain visibility. Tapping the status bar or the navigation buttons will bring this gradient back, but seeing it like that is annoying for someone who likes their stuff fancy looking lol. The only time I've noticed that the gradient is there after an unlock is after the very first unlock after a reboot.
[Nexus 5 Original Android Development] nictki:
thx ;)