yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] andrei1015:
I found that these days the build appears on jenkins only when it's the latest device built. When the next device pops up.. You get the idea.

Flowed from my Nexus 5
[Nexus 5 Original Android Development] kronflux:
@myfluxi, or to anyone else who can answer - I haven't used the official CM nightlies lately, but I had heard somewhere in some post if I recall correctly, that some of the work on the CAF roms has been or is going to be adopted by official CM repos?

I'm just wondering what's been merged as of late, or whether you know. I'm thinking of going back to official nightlies, as I find them more stable. The youtube app, for example, crashes for me anytime I play a video(I could probably fix my issues with a clean install, so I may try that first).

My issue with switching back to official CM is that the audio isn't as loud, even with various custom kernels and rom tweaks. The CAF roms you put out boost my volume quite a bit, and not to the point that it's overly distorted. I like that for my alarms.

So yeah. any info on what's been merged, what will be merged, and the progress of CM official repos vs the CAF roms would be greatly appreciated.
[Nexus 5 Original Android Development] omvir:
Well... The myfluxi CAF builds have been stopped. And deleted. Due to a conflict between myfluxi and neobuddy. None of the code was adopted by CM. Myfluxi had plans for that but obviously no more. I do happen to have a link to his last build if you would like that?
[Nexus 5 Original Android Development] VOLTAGEROCK:
Just flashed 10192014 nightly. No issues so far...

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] tnpapadakos:
I HAVE cm-11-20141009-CAF15-hammerhead if anyone needs it
[Nexus 5 Original Android Development] hanschke:
can anyone confirm a google licence problem with cm:confused:
[Nexus 5 Original Android Development] topgeardave:
Please elaborate?
[Nexus 5 Original Android Development] neobuddy89:
And latest hammerhead lollipop preview's kernel source released... that was pretty quick.
[Nexus 5 Original Android Development] Tylog:
Yes, I also wonder :)
[Nexus 5 Original Android Development] topgeardave:
It's not of much use to us unless we go back to aosp hals in cm 12
[Nexus 5 Original Android Development] VOLTAGEROCK:
Don't have time to search, so can you tell me what caf means. Should I flash that instead of the Oct 19 one in using?

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] fattire:
CAF

CAF = Code Aurora Forum. It's the oem hub for Qualcomm's open source projects. See more about OEMs and how they support open source projects w/platform-specific code here at the CyanogenMod wiki.
[Nexus 5 Original Android Development] koelspy:
Is there any developer here that can continue where [MENTION=4152171]myfluxi[/MENTION] stopped? I really liked the CAF builds!
[Nexus 5 Original Android Development] magnamentis:
IMO you post was longer than typing CAF+android into google search so too lazy would be closer to the truth

Sent from my A0001
[Nexus 5 Original Android Development] VOLTAGEROCK:
Typing into a search and then reading for 15 minutes takes longer than simply asking someone who knows more about this than I do.

I expect nothing more from some of the people here on XDA. Oh yeah, I work too. But really good point. I'm glad you have enough time to try to put people down. Good luck with that in the future.

All the best.

Sent from my wondrous Nexus numeral 5
[Nexus 5 Original Android Development] ^Reloaded^:
Latest nightly 201014 has bug

When I set quick toggles it gives systemui fc
[Nexus 5 Original Android Development] mbellot:
Unlikely. If what I understand happened is correct, myfluxi deleted all his modified code.

A new dev would have to recreate everything from scratch.
[Nexus 5 Original Android Development] warhead1978:
All fine here ... nightly from 21.10

MfG

Edit: OK, if you change the settings in quick panel there is systemui fc...sorry ... didn't tried it yet...
[Nexus 5 Original Android Development] MaxRabbit:
Is there anything that would convince you to come back?
[Nexus 5 Original Android Development] myfluxi:
I got nice feedback. We can do whatever is nessecary as long it does not affect other devices and we were promised full support. This however does not change the actual problems with all those options and pros and cons. On top, everything might change after the L release that brings major changes in sources and build system. It will be painful.
[Nexus 5 Original Android Development] nictki:
looks nice, hopefully will go smoothly
[Nexus 5 Original Android Development] kellybrf:
whichever way you decide to go I just wanted to say thanks for all the time and effort you put in. I've been here long enough to watch this scenario play out over and over and its a shame that a few jealous, insecure mid-level developers continue to drive the truly good ones away. its a selfish act that hurts the community, but either way you shouldn't have to deal with it. I really appreciated your caf work and selfishly hope you continue as I plan to stay with my n5, but I completely understand if you don't want to deal with the hassle of the pricks around here
[Nexus 5 Original Android Development] myfluxi:
Thanks to the L release blobs we have new firmwares and even the fancy esoteric stuff like offloaded post-processing audio effects, something that was an for-OPPO-only feature. The Nexus is moar awesome than ever and it never sounded so good.
[Nexus 5 Original Android Development] aldyu:
Hope you will be back building again and share it with us. :fingers-crossed:
[Nexus 5 Original Android Development] myfluxi:
Update inofficial build #18

Built with CMs audio-caf (again), enable offloaded post processing effects bundle (cpu sleeps even with eq, bass boost etc. enabled), readd AudioFX equalizer app (sometimes takes two attempts to hook into the music stream, this appears to be an issue on bacon as well, will probably be fixed once it's open sourced), music sound is awesome, camcorder stereo sound is nice and with much less static than L's cam

If this works, I will do my best to get our plain CAF HALs and make it a nightly. If you feel like discussing, do whatever you like...
[Nexus 5 Original Android Development] procitysam:
Does this mean you're back?
[Nexus 5 Original Android Development] myfluxi:
I'm a ***** sometimes, sorry for the drama (even if my points remain).
[Nexus 5 Original Android Development] procitysam:
I don't care it's just awesome you're back :D
[Nexus 5 Original Android Development] lolobarjo:
Welcome back ?

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] Tylog:
Sind wir nicht alle ein bisschen Bluna ? :eek:

German insider :) and Wb
[Nexus 5 Original Android Development] leonard.pitzu:
welcome back! and thank for your many efforts. i am a developers myself (although not of the posting type) and know what effort goes into such an undertaking.
[Nexus 5 Original Android Development] topgeardave:
Cheers for the update, on behalf of the community I genuinely can't thank you enough!

Do you think that the kernel and L blobs will change with the final release of L in a couple of weeks?
[Nexus 5 Original Android Development] eosaph:
welcome back!
[Nexus 5 Original Android Development] _MirageX_:
thanks for coming back, really. I could really feel my nexus 5 screaming for a new build of you.
[Nexus 5 Original Android Development] nictki:
sweet, many thanks
[Nexus 5 Original Android Development] Dudebowski:
I'm a poor student, but I'll shamelessly plug myfluxi for donations...

10/22 Unofficial CAF build boots, runs, does what i need it to do (nothing crazy.) Thanks for coming back.

Question: I'm having issues with charging while in normal boot. Charges as expected in recovery/ fastbootloader. Battery Monitor Widget shows a net charge of 0 when plugged into a charger. Tried different chargers, wall sockets, have one of those blackberry 1.8A chargers and I think i either fried the battery or the microUSB but getting it to charge in recovery normally seems strange. This has been happening on both nightlies and CAF builds for a few weeks now. haven't tested stock or anything though.
[Nexus 5 Original Android Development] q1t1:
Welcome back !
[Nexus 5 Original Android Development] mmo.xda:
Sweettttt!! I will try CAF18 as soon as I can :)

On the other hand, there was a little bug in CAF17 (

link

).

Instagram was not working with that build.

I was getting a black picture when I was just about to publish a modified photo from instagram app.

In gallery (sdcard/pictures/instagram) modified Instagram photo was saved right, but in app a black one was shown.

A failed provider was shown in logcat... ("E/ActivityThread(21812): Failed to find provider info for com.facebook.katana.provider.AttributionIdProvider ")

Could someone test on CAF18 if this issue is still there???

Best regards
[Nexus 5 Original Android Development] Viper LABs:
Does back navigation bar button work on CAF18? For me it do nothing. No messages in logcat either.

UPD. Nevermind, my fault. Was related to the new Google Keyboard from L. Everything is working now.
[Nexus 5 Original Android Development] wipian:
Is anyone else's display auto rotation broken with this build?

Edit: I'm an idiot, a reboot fixed it :)

Edit 2: Apparently not...
[Nexus 5 Original Android Development] myfluxi:
Nothing related to rotation has been changed specifically, works for me smoothly as expected. So this is either a holding-it-wrong or genral CM error.

This issue was fixed earlier but reappeared and there was a report of this happening even in the nightlies. Will have to dig deeper but only if we are official, else I would not care as I'd never use Instagram. Probably related to jpeg post-processing and the HALs.

Keep on testing, people.
[Nexus 5 Original Android Development] mmo.xda:
Woow! Thanks for this quick answer.

I will test several builds (official nightlies and CAF) in order to help identify break point date :)

Yes sir!, that is what user should do here :)

Thanks!!
[Nexus 5 Original Android Development] wipian:
Oops, my apologies, a reboot did the trick.

Everything is running great again.

Many thanks :)

Edit: Hmmm, broken again :(
[Nexus 5 Original Android Development] myfluxi:
Glad it's fine.

Could those with certain car charger being detected a peripherical (= not charging) please test again with #18, thx. I tested 3 different car chargers and all of them work (they did before already, tbh...).
[Nexus 5 Original Android Development] Tylog:
[MENTION=4152171]myfluxi[/MENTION], is it possible to include the kexec patch in the kernel? Thx.
[Nexus 5 Original Android Development] myfluxi:
These kind of hacks won't find their way into CM versions. If this goes official or fails, I'm sure somebody will pick it up as all sources will be public. Until then, I kindly ask everybody to use the supplied kernel in order to avoid additional chances for errors.
[Nexus 5 Original Android Development] Tylog:
Ok i understand, thanks.
[Nexus 5 Original Android Development] Corintio:
Instagram keeps showing a black picture on CAF18, as it did on CAF17. The bug is still there. Is there anything I can do to help you/anyone pinpoint it?
[Nexus 5 Original Android Development] Isidorosis:
anyone else having this issue on caf18?
[Nexus 5 Original Android Development] rockknee:
Yes I'm having too some troubles with auto rotation. Now it has been two times stuck, reboot fixed it tho. Maybe just cm bug?
[Nexus 5 Original Android Development] djsubtronic:
Can confirm the rotation issue. Seems like a gyro/accelerometer issue. Wasn't able to get a logcat though.
[Nexus 5 Original Android Development] wipian:
Yes, I spoke too soon.

I've just taken three pictures in landscape and they all appeared in the gallery as if I'd taken them in portrait.

(auto rotate is still working perfectly...)

Strange one.
[Nexus 5 Original Android Development] rockknee:
As I was going to try the same I noticed that even the camera app itself doesn't rotate so it's stuck again. I will try to dig logcats right away when I'm back home...
[Nexus 5 Original Android Development] myfluxi:
There have been a zillion changes in the camera app lately (https://github.com/CyanogenMod/android_packages_apps_Camera2/commits/cm-11.0). Please try with the official nightlies and report back at which date the issue started.
[Nexus 5 Original Android Development] nictki:
here is everything ok...

CAF-18 flashed over last nightly
[Nexus 5 Original Android Development] djsubtronic:
It is happening on all camera apps (I don't use the CM camera). So not likely to be related to the CM camera app.
[Nexus 5 Original Android Development] rockknee:
I took logcat and it seems to repeat this line all over and over again

E/qcom_sensors_hal( 646): hal_process_buffering_resp: Result: 1, Error: 5

E/qcom_sensors_hal( 646): hal_process_buffering_resp: 0 Error: 4 Reason: 16

E/qcom_sensors_hal( 646): hal_acquire_resources: Failed for handle 0 @ samp 15 Hz rpt 0 Hz WuFF 0 batched 0

After lots of spam there comes lines:

D/qdhwcomposer( 219): hwc_blank: Done blanking display: 0

I/qdhwcomposer( 219): handle_blank_event: dpy:0 panel power state: 0

D/SurfaceControl( 646): Excessive delay in blankDisplay() while turning screen off: 290ms

I/QCOM PowerHAL( 646): Got set_interactive hint

W/qcom_sensors_hal( 646): _hal_sensors_activate: Deactivating dirty sensor 0

E/Sensors ( 228): sns_acm_mr.c(348):Transport error -45

I can't get the whole file uploaded atm cause of it's size...

It's not just the camera app that isn't rotating here, it's every app and system.
[Nexus 5 Original Android Development] topgeardave:
Try and pastebin it, it makes life easier for everyone ?
[Nexus 5 Original Android Development] Corintio:
Everything ok here as well. Phone rotates properly, pictures are saved as portrait or landscape accordingly without issue. CAF18 freshly installed after wiping lollipop official preview. Google camera app installed from play store.
[Nexus 5 Original Android Development] warhead1978:
Since nightly from 21.10, I noticed an issue with media control with Bluetooth and car audio head unit. Playing is fine but cannot control (play/pause forward backward) any Media App like Apollo, etc.

MfG
[Nexus 5 Original Android Development] rockknee:
I did some testing with official nightlies (couple of them) and I was not able to reproduce the problem. Rotation worked fine. Now I'm giving another shot for caf18 and investigating wheter I can reproduce the bug or not. I have no idea how it is possible to have randomly broken rotation when clean flashing.. That's what I did the first time when the issue appeared.

Edit: After clean flash everything worked fine 20mins and then Booom. Rotation broken again. Only possible reason aside the ROM itself is Gapps, which I don't believe in. I'm using Pa Gapps. I took a lookat the logcat and it's spammed with E/qcom_sensors_hal..... Lines
[Nexus 5 Original Android Development] wipian:
I used the Google camera from the store for those particular pictures.

Agreed.
[Nexus 5 Original Android Development] myfluxi:
So you have a full log? Why don't you post it, my crystal ball is for repair.
[Nexus 5 Original Android Development] rockknee:
Yes I have and multiple of them! Due to the xda's attachment file size limitation I did not post the full log first but here is another one
[Nexus 5 Original Android Development] nexzor:
hi, i´m on CAF18 since aprox. 10h. no new problems found.

only as a reminder for any dev (exept myfluxi) who passes by:

this bug still exist https://jira.cyanogenmod.org/browse/CYAN-5567

as mentioned before i´m still searching nightlys between 2014/08/27 and 2014/09/11 to identify in which nightly the lockscreen broke.
[Nexus 5 Original Android Development] wipian:
Here's another if it helps :)

The same qcom sensor stuff appears in here too.
[Nexus 5 Original Android Development] procitysam:
[MENTION=4152171]myfluxi[/MENTION] your builds fixed the SoD right? I went from M11 snapshot official to the latest official nightly and I still have the problem.
[Nexus 5 Original Android Development] Robisgnarly:
Having issues with data speeds, on the newest radio below the lollipop radio, on sprint 3 bars of lte and 3 bars of 3g. The issue is the lte data speed that was about 10mbs on lte previously on stock is now only getting about .50mbps now in the same exact spot, also the 3g is pulling faster than the lte with 1.2 mbps.
[Nexus 5 Original Android Development] myfluxi:
Argh. Ms and nightlys are incompatible and mixing and matching will cause major breakage.
[Nexus 5 Original Android Development] procitysam:
No what I'm saying is I was on M11 official, but the SoD became too constant, after every lock I had to hard reboot. So I used CM updater and went to the nightly for yesterday to see if it had a fix yet, and I've gotten one SoD so far. I'm thinking of switching to your unofficial version because I think I remember you getting a fix for it but I can't remember for sure.
[Nexus 5 Original Android Development] cjwaggsrx8:
Might not be your radio. Sprint is doing some major tower work everywhere. You may have received a text about it. I'm in St. Louis and my data speeds were all messed up for about three days. Check this to see if your affected... https://downdetector.com/status/sprint/map
[Nexus 5 Original Android Development] Robisgnarly:
Nope not on the map, also on stock the previous dayspeeds were much better
[Nexus 5 Original Android Development] warhead1978:
No one else?

I saw in the nightly from 16.10 there are many Bluetooth changes and I had updated from a nightly before to nightly from 21.10.

I never had any Bluetooth issues before this changes.

MfG
[Nexus 5 Original Android Development] bjoswald:
I've tried the CAF build, but didn't notice anything different, so I went back to stock. However, I thank you, fluxi, for the continued support.
[Nexus 5 Original Android Development] nexzor:
little update on this:

did a little testing again ( [MENTION=2770410]mbellot[/MENTION] send me some nightlys):

20140831-nightly is ok

20140905-nightly is ok

20140911-nightly not ok

so the problem has to do somthing with patches between 20140905 and 20140911.

so if you have nightlys between this dates pleas test the issue or send me the nightlys.
[Nexus 5 Original Android Development] rockknee:
So are you comparing here CM and stock or cm CAF and CM official builds? If cm and stock I have to ask you; did you even open settings menu to see what cm has to offer? The difference is huge
[Nexus 5 Original Android Development] bjoswald:
I just didn't see a need for it. I have been using stock CM for so long that I can put up with the occasional glitch here and there. But if you like it, more power to you.
[Nexus 5 Original Android Development] rockknee:
Ohh, I thought you were comparing vanilla stock to cm which made me wonder how you can't notice any difference between two of them. The difference between CAF and official cm builds is less noticable but there are some great and usefull "underhood" improvements on CAF builds.
[Nexus 5 Original Android Development] myfluxi:
Good bug report. I cannot spot anything specific on first view, will look at this later.
[Nexus 5 Original Android Development] myfluxi:
Update inofficial build #19, nothing special, just consolidated.

I completely forgot that we diverged from Google in mdss considerably and unnececarily. So even reverting to Google means that we're running glued together stuff. Very, very, very sad and frustrating.
[Nexus 5 Original Android Development] Audioboxer:
Did you change it to only support the old bootloader? I have the new one from L preview, build 18 flashed okay, build 19 errors out due to bootloader.
[Nexus 5 Original Android Development] myfluxi:
I ran into that as well and I think had one line removed in the build, so this is just random and not intended. You can extract the updater-script and remove the assert that checks for the bootloader revision (lines 4 and 5) and then put it back in the ZIP.
[Nexus 5 Original Android Development] unknvvn:
[MENTION=4152171]myfluxi[/MENTION]

It seems i can't flash CAF19 on HHZ12d bootloader (says not supported), CAF18 worked as normal.

Thought i haven't tried latest nightly (24-10).
[Nexus 5 Original Android Development] myfluxi:
Ugh, hidden camera somewhere?

Honestly, #19 behaves "normally", not the other way around. Anyway reading only a few pixels above may be a good idea.
[Nexus 5 Original Android Development] nexzor:
maybe i found something on the bug discribed below!

my problem now is that i need to build without tis patch (http://review.cyanogenmod.org/#/c/72393/).

i never build cm before so i have to learn it step by step, any good tutorial is appreciated!!!!

if someone with more knowledge than me has a build environment set up and is willing to build for me without the mentioned patch pleas send me the build or test the bug.

if no one will do this for me i´ll need some days to learn how to do it, but i´m sure i´ll find the corrupted patch sooner or later.

than i realy need someone with programming skills to solve the problem or it will take some years till i learn how to write code!^^

so any help on this is verry appreciated!

sorry for following german!

ich will die nicht unter druck setzen [MENTION=4152171]myfluxi[/MENTION] , ich weiss nur nicht wo ich diese frage sonst am besten stellen soll. also wirklich nur beachten wenn du zeit hast!
[Nexus 5 Original Android Development] myfluxi:
Yeah, I saw that patch and wanted to investigate later. That's why I said "good bug report", I wish every report was like that.
[Nexus 5 Original Android Development] myfluxi:
Unofficial build #20

If this fixes those sensor/rotation errors (I never got them so far), it would be another nail in the coffin for this little project. Time to pray, we're getting a vanilla display HAL to start from scratch.
[Nexus 5 Original Android Development] wipian:
So far it appears to be fixed :)

A few manual reboots

Same GApps

Same Apps

Same camera app and no rotated images

Many thanks [emoji106]

Edit: I spoke too soon again...
[Nexus 5 Original Android Development] ssauger:
Screen Color

[MENTION=4152171]myfluxi[/MENTION]

First, thanks your back for us .

I noticed under sreen settings -> Screen Color in your CAF20 build. I did a clean install, when i change anything nothing happens. Also the setting isn't there as i tried the latest official cm nightly for that. Is this something like gamma settings for the future in your builds?
[Nexus 5 Original Android Development] djsubtronic:
Sorry [MENTION=4152171]myfluxi[/MENTION], just installed #20 and the rotation bug remains. Is there any way I can help providing a log for this?
[Nexus 5 Original Android Development] Isidorosis:
I am still having this issue on CAF20

is interactive broken ?? it never goes under 1.1ghz for me
[Nexus 5 Original Android Development] bjoswald:
Works fine here...

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

Tried your build again and feels a lot smoother. No idea what I did wrong last time or what's changed in the past three days, but I'm happy. Will continue to use your builds from now on.
[Nexus 5 Original Android Development] topgeardave:
Is this with cm camera or Google?
[Nexus 5 Original Android Development] oliveko:
Rotation bug here as well...and thank you

For your work!!!
[Nexus 5 Original Android Development] djsubtronic:
Google camera, snap camera, and any other app that uses the accelerometer. Download an app called "Accelerometer Monitor" and you can see all the graphs moving as you move the phone. After the sensor fails (within a little while of a fresh boot), it shows no graphs and no app recognises phone movements.
[Nexus 5 Original Android Development] lolobarjo:
With #19 I noticed something with rotation bug. If I boot my device with auto rotate disabled after some minutes the sensors are dead but if I boot my device with auto rotate activate and I let it there is no more bug. I will test with #20 and report with lolcat

Envoyé de mon Nexus 5
[Nexus 5 Original Android Development] wipian:
I spoke too soon again :(