yashsingh1/xdaforums huggingface dataset:
[ONE Android Development] miragez:
Wow its seems like CM developers are on the fire rage, striking so many fixes. Thanks in advanced Daleski75, I was like freaking happy today morning when I see several new fixes in gerrit, but never expect a 20 over changes and still going on.

I have a question for the pros,

build: Allow devices to specify a RIL variant (android_build) <--- does this resolve the RILJ issues which keeps waking up the phone during deep sleep or does it means CM are trying to isolate and resolve certain RIL variant ?
[ONE Android Development] daleski75:
Gah the filesystem on my ubuntu VM is screwed hopefully I have a working backup....

Running off USB for the meantime so at least I can continue doing builds just more slowly.
[ONE Android Development] daleski75:
Did not see them commits will try doing another build now and if I can get it working I will let you know right away.
[ONE Android Development] giaur:
Many fixes but nothing related to audio distortion and buttons lights...
[ONE Android Development] daleski75:
Still bootlooping guys so not sure if there will be a build today.
[ONE Android Development] Norapapa:
OT: Can you recommend me an app to screen record?
[ONE Android Development] SrZNlu32:
IS the rom includes all the customizable options like cm11 44s.. and stock cameranext app without any lag as it lags in lollipop build.. voice wake up?

i am looking for stock feel with more customizable options ... i want to flash it right now .. so please hepl???
[ONE Android Development] chikiro:
Thanks sir.. Waitng for the update..
[ONE Android Development] hidea:
I like this app called Rec.

https://play.google.com/store/apps/details?id=com.spectrl.rec
[ONE Android Development] NuLLV01D:
Yep.. Everything You Want is All Inside. So Get Going!
[ONE Android Development] SrZNlu32:
Thank you :) i'm not getting the links.. can you please tell me where are the latest version links? and which Gapps should i use.??
[ONE Android Development] daleski75:
Voice wakeup though has never existed officially.
[ONE Android Development] NuLLV01D:
Oh Sorry... I Didn't Read that part. Yep, That Doesn't and didn't exist.
[ONE Android Development] tiny4579:
What I'd like to do if I were at home today would be to build for a different device to see if the broken part is related to Bacon only or one of those many telephony commits.
[ONE Android Development] daleski75:
Seen a commit for a NPE could this help? And this telephony commit as well

http://review.cyanogenmod.org/#/c/83030/

http://review.cyanogenmod.org/#/c/83029/
[ONE Android Development] tiny4579:
That npe wouldn't be causing a bootloop like that. More likely it causes force closes under certain conditions.
[ONE Android Development] SrZNlu32:
Download links not getting ?? And gapps?
[ONE Android Development] daleski75:
Do you mean download links for today 28/12?
[ONE Android Development] SrZNlu32:
Yeah..
[ONE Android Development] daleski75:
Erm did you read the last few pages or the first post?
[ONE Android Development] Nburnes:
The part where he mentions it bootloops and as such will probably be no build today, might have something to do with no link existing.
[ONE Android Development] SrZNlu32:
Sorry.. Just now checked the last pages so i'll download the 27/12 one..

---------- Post added at 02:41 PM ---------- Previous post was at 02:39 PM ----------

So which is the recommended gapps ..???
[ONE Android Development] daleski75:
Also on the first post.
[ONE Android Development] Nburnes:
First link in the very first post of the thread: http://xdaforums.com/paranoid-android/general/gapps-official-to-date-pa-google-apps-t2943900
[ONE Android Development] SrZNlu32:
Thanks i'll download it right now..
[ONE Android Development] fards:
Is it getting far enough along to get logs?

All this fun is making me want to get back into building, had niggling in the back of my brain to start on a pure aosp but not had time to think about it.

Have week off at mo so could do, but no broadband due to bt cocking up installing my infinity line.
[ONE Android Development] daleski75:
Not sure when it's plugged in and doing it's bootloop thing if I run any adb commands it says device not found and almost finished another fresh clean build... 3rd time lucky??
[ONE Android Development] fards:
Try a build with the vector flags back back in

http://review.cyanogenmod.org/#/c/82992/1/BoardConfigCommon.mk
[ONE Android Development] daleski75:
Just flashed and it's booting now, if it doesn't reboot once it's got past the Android is Upgrading part then that's a good sign.
[ONE Android Development] tiny4579:
If you clean flash the device won't be authorized. You won't be able to do adb logcat on a clean install prior to authorizing the device, so the two options are to dirty flash from a working build or disable the adb security via default.prop in the ramdisk.
[ONE Android Development] daleski75:
This is a dirty flash from last night's which has the device authorised still and weirdly enough it seems to be working with adb logcat so far.

adb logcat -v long > Desktop/bootloop.txt
[ONE Android Development] tiny4579:
They shouldn't prevent the device from booting. On m7 I did a dirty build after vectorimpl_symbols was reverted to test some camera drivers and the only issue was camera was broken since the build wasn't fully compiled without the vector flags in. No bootloops.
[ONE Android Development] daleski75:
Here is the output from the adb logcat.

https://www.androidfilehost.com/?fid=95864024717071306
[ONE Android Development] tiny4579:
Just realized something after looking at the log. There were a lot of qc-qmi errors. Steve updated a lot of ril/radio blobs, but the switch to the new ril didn't happen until later. Its possible it might boot just fine now after syncing and building, even an installclean might work.
[ONE Android Development] daleski75:
Did a clean build with all the ril commits and still get a bootloop will try doing a clean install as well to see if that gets to the setup wizard.
[ONE Android Development] Gwanatu:
What in the world is this Eleven I keep seeing in the commits?
[ONE Android Development] daleski75:
Replaces Apollo the music player.
[ONE Android Development] tiny4579:
Useless trivia but this is possibly the source of the name of the eleven music app.

http://en.m.wikipedia.org/wiki/Up_to_eleven
[ONE Android Development] daleski75:
I shall call today bootloop day.
[ONE Android Development] hapee:
So no new build today?
[ONE Android Development] daleski75:
Nope not unless CM fix the bootloop.
[ONE Android Development] giaur:
Do you mean app called "Music"?

---------- Post added at 03:58 PM ---------- Previous post was at 03:55 PM ----------

Let's wait for fix... I will also test other (automated) build tommorow and see if it works
[ONE Android Development] daleski75:
[MENTION=3500210]tiny4579[/MENTION] Not sure I have spotted the bootloop issue (still learning this stuff)

The msm8974: Use CAF RIL variant commit depends on this commit which is still under review would this still be downloaded when doing a repo sync even though it is under review and not merged into the git repository?

http://review.cyanogenmod.org/#/c/83022/ depends on http://review.cyanogenmod.org/#/c/81003/
[ONE Android Development] _Man0waR_:
I understand it's the way around. The first commit is NEEDED for the second commit. Am I wrong ?
[ONE Android Development] Nburnes:
Correct. He has it backwards.
[ONE Android Development] daleski75:
Cheers guys.
[ONE Android Development] Borsutkar:
Hats of...to your dedication and efforts you guys are putting...

Thanks again
[ONE Android Development] tiny4579:
Gerrit dependencies are a frame of reference as far as commit order. I think its to avoid people merging or cherry picking in the wrong order. There are no missing dependencies for ril or izat.
[ONE Android Development] daleski75:
Cheers man much appreciated going to sit back and chill and wait for CM to fix the bootloop issue.
[ONE Android Development] fards:
In your log vm is being shut down from fatal in systemui related to wallpaper

Nuplayer is having issues with audioeq and a few others

Those are pretty early on through and system server does restart later on.

They are all being tombstoned so can pull the logs in from data/tombstones in recovery.
[ONE Android Development] tiny4579:
If they get it fixed and I'm still up but it's too late for you do you mind if I post a build here? I don't want an XDA thread for an unofficial build for now nor take over yours so I thought I'd check first. Mainly because of the potential goodies awaiting us today.
[ONE Android Development] daleski75:
I really appreciate the help and it's bugging me knowing that there are a lot of good commits today but it won't boot.
[ONE Android Development] daleski75:
Also a bit OT but my thread is getting a lot of views.
[ONE Android Development] Yammertime:
450K and rising. It goes to show how many people are eager to try out new builds. And thanks to you, they can. Keep up the good work!
[ONE Android Development] tiny4579:
We may not be missing too much in the camera. The updated drivers didn't remove the need for the camera hack so I guess 4k recording still wouldn't work.

But the number of telephony commits is more than I care to go through. I saw one mentioning volte tho. I'd love to be able to do a volte call some day.
[ONE Android Development] daleski75:
I saw Steve's message on the abandoned hack that video recording is still broken even with the new camera drivers and in the UK we only have one network which is doing VoLTE testing and if I am on 4G it reverts to 3G for calls.
[ONE Android Development] fmc000:
Yup, count me in since Yesterday. Kudos to Dale.
[ONE Android Development] m4f1050:
Is it my OPO or does flash pictures get like a line (half is darker on one side)?
[ONE Android Development] Nucleonic:
Not just you. Haven't seen that recently on my OPO but I had seen that on my N6 running SlimLP Alpha. Would be watching Netflix and all of a sudden a line would appear longitudinally. The line doesn't show up on screenshots.
[ONE Android Development] tiny4579:
Issue with flash and Google camera. Try camera next. I've been able to reproduce this several times when setting flash to on (not auto) and taking a picture with Google camera.
[ONE Android Development] tiny4579:
Try reverting this for the bootloop issue:

http://review.cyanogenmod.org/#/c/82990/

I can't test for about 4 hours.
[ONE Android Development] daleski75:
Just spotted that in the comments on gerrit will try reverting that commit and see how it goes.
[ONE Android Development] inffy:
My build from hour ago booted just fine
[ONE Android Development] daleski75:
False alarm.

Ben Edmunds	7:59 PM

Patch Set 1:

flashed wrong kernel sorry this commit seems fine
[ONE Android Development] giaur:
But somebody said that commit is ok and bootlop is caused by wrong kernel.
[ONE Android Development] tiny4579:
Darn. I guess we keep waiting.
[ONE Android Development] joebonrichie:
when did you last repo sync?
[ONE Android Development] AcmE85:
I can confirm this, no issues.
[ONE Android Development] daleski75:
Weird I still get a bootloop and literally done a repo sync and built it about 30 mins ago.
[ONE Android Development] daleski75:
The bootloop happens with the stock kernel.
[ONE Android Development] giaur:
What about custom kernel?

---------- Post added at 10:05 PM ---------- Previous post was at 10:04 PM ----------

Stock kernel?
[ONE Android Development] daleski75:
They flashed the wrong kernel which caused them to think that the commit http://review.cyanogenmod.org/#/c/82990/ was the cause of the bootloop when it wasn't.
[ONE Android Development] giaur:
But AcmE85 and others said that it boots ok
[ONE Android Development] daleski75:
Waiting to hear when inffy done the last repo sync.
[ONE Android Development] fragargon:
I made a repo this morning around 10 a build and boot nice.... Was reading the thread and look to gerrit... Made a repo again and build but bootloop.... Same error as your build daleski. So this is certainly a faulty commit. There are too much commit. I still don't know which one is the culprit!

Edit; saw that the muppets was update by commit!

sent from my one+1 XDA Mobil app
[ONE Android Development] daleski75:
There are a ton of commits today and any of them could be the culprit or even worse a combination of commits.
[ONE Android Development] inffy:
I did repo sync about 7.40pm (Finnish time)
[ONE Android Development] daleski75:
Did you do a dirty flash?
[ONE Android Development] inffy:
My friend did yes. And it was a totally clean build
[ONE Android Development] daleski75:
Very odd the second mine finishes doing the "Android is upgrading..." it reboots and then that's it and it never gets out of the bootloop then.
[ONE Android Development] inffy:
That is odd yeah
[ONE Android Development] daleski75:
Looks like its now fixed or soon going to be fixed http://review.cyanogenmod.org/#/c/82993/
[ONE Android Development] joebonrichie:
Just did a make clean and fresh synced build. Still a bootloop.
[ONE Android Development] tobitege:
[MENTION=1095206]daleski75[/MENTION]: is the missing library "libalarmservice_jni.so" a separate merge/build? Just wondering.
[ONE Android Development] fards:
Are you using muppets?
[ONE Android Development] fards:
https://github.com/TheOldUnas/Bacon-Lollipop/blob/master/mango/system/.fr-68jhBK/system/vendor/lib/libalarmservice_jni.so

That one?
[ONE Android Development] m4f1050:
Ok, will give Camera Next a try.... Does it have all the nice features the one that it came with has? :D
[ONE Android Development] PresidentMcCain:
Don't bother, the repo is just completely shot right now:

"reverting com.qualcomm.location.apk to the previous version makes the rom boots again, but no iZat. at least this option doesn't appear in the location mode."

- Even if you do this, you'll find out that other stuff are broken as well... such as the camera. No apps can connect to the camera.
[ONE Android Development] asafba:
Camera Next 2.00.04 download

Anyone have a download link for camera next 2.00.04?

Thanks
[ONE Android Development] PresidentMcCain:
http://www.apkmirror.com/apk/cyanogenmod/cyanogen-camera/camera-2-0-004-5fa8c79c0b-30-apk/
[ONE Android Development] tiny4579:
Cam should work but I'm building now to confirm. Did you do a clean build when testing today?
[ONE Android Development] joebonrichie:
I just did another(!) clean build moving com.qualcomm.location.apk to it's previous location (/app), still no boot.

Oh well, I'll wait for it to be fixed upstream.
[ONE Android Development] AcmE85:
Freshly merged

http://review.cyanogenmod.org/#/c/83066/

This should probably fix the bootloop.
[ONE Android Development] PresidentMcCain:
You need to revert com.qualcomm.location.apk to the previous commit. The file location is still at the original /system/priv-app/com.qualcomm.location

But judging from what [MENTION=4447339]AcmE85[/MENTION] found out, you probably don't even need to do that anymore.
[ONE Android Development] Sh0X31:
Hey guys,

I build my owne stock build, but it don't boot. It's always at the 1+1 Screen.
[ONE Android Development] Galactus:
You need to read some pages back..................
[ONE Android Development] PresidentMcCain:
I can confirm that this change (http://review.cyanogenmod.org/#/c/83066/) solved the bootloop issue. However, camera is still broken.

Camera crash stack trace:

12-28 21:22:15.713: A/libc(1983): Fatal signal 11 (SIGSEGV), code 1, fault addr 0x1 in tid 2209 (Binder_2)
12-28 21:22:15.814: I/DEBUG(241): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
12-28 21:22:15.814: I/DEBUG(241): Build fingerprint: 'oneplus/bacon/A0001:4.4.2/KVT49L/XNPH25R:user/release-keys'
12-28 21:22:15.814: I/DEBUG(241): Revision: '0'
12-28 21:22:15.815: I/DEBUG(241): ABI: 'arm'
12-28 21:22:15.815: I/DEBUG(241): pid: 1983, tid: 2209, name: Binder_2 >>> /system/bin/mediaserver <<<
12-28 21:22:15.815: I/DEBUG(241): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x1
12-28 21:22:15.818: W/NativeCrashListener(831): Couldn't find ProcessRecord for pid 1983
12-28 21:22:15.820: I/DEBUG(241): r0 af6b688c r1 af60e5f0 r2 af7ff660 r3 b4380131
12-28 21:22:15.820: E/DEBUG(241): AM write failure (32 / Broken pipe)
12-28 21:22:15.820: I/DEBUG(241): r4 00000000 r5 00000000 r6 af6b688c r7 00000000
12-28 21:22:15.820: I/DEBUG(241): r8 00000000 r9 af7ff660 sl af60e5f0 fp 00000008
12-28 21:22:15.820: I/DEBUG(241): ip b45f0c98 sp af7ff620 lr b6e4b8a3 pc b4380136 cpsr 400d0030
12-28 21:22:15.820: I/DEBUG(241): backtrace:
12-28 21:22:15.820: I/DEBUG(241): #00 pc 003d7136 /system/lib/hw/camera.msm8974.so
12-28 21:22:16.261: I/DEBUG(241): Tombstone written to: /data/tombstones/tombstone_00
12-28 21:22:16.262: I/BootReceiver(831): Copying /data/tombstones/tombstone_00 to DropBox (SYSTEM_TOMBSTONE)
12-28 21:22:16.263: E/SharedPreferencesImpl(831): Couldn't create directory for SharedPreferences file shared_prefs/log_files.xml
12-28 21:22:16.272: I/ServiceManager(219): service 'media.audio_flinger' died
12-28 21:22:16.272: I/ServiceManager(219): service 'media.player' died
12-28 21:22:16.272: I/ServiceManager(219): service 'media.camera' died
12-28 21:22:16.272: I/ServiceManager(219): service 'media.audio_policy' died
12-28 21:22:16.272: I/ServiceManager(219): service 'media.sound_trigger_hw' died
[ONE Android Development] tiny4579:
Camera works fine. Did you clean build as I asked earlier?

It's absolutely essential if you want a working camera due to this commit:

http://review.cyanogenmod.org/#/c/82992/
[ONE Android Development] TeChNoC4AzY:
Is this rom recommended sense it is updated daily?
[ONE Android Development] omvir:
Do you post your builds anywhere? Or are they for yourself only?
[ONE Android Development] tiny4579:
I haven't really wanted to keep up with an xda thread and maintain a changelog which is a bit for running daily builds, and my builds are basically like [MENTION=1095206]daleski75[/MENTION] but just built at a different time but I don't build every day. Sometimes I do cherry picks, but not usually.

I can post my build here to wet your appetites for OP's next daily but I don't want to steal thunder from the OP.
[ONE Android Development] omvir:
Ah, okay. Would it be possible if you could put a link in your signature whenever daleski misses a build And if you happen to build that day?

Yes, please. Wet my appetite [emoji14]
[ONE Android Development] tiny4579:
For now I'll post tonight's build since the builds were failing to boot this morning.

https://www.androidfilehost.com/?fid=95864024717071585

If I get around to it, I may create a thread later.
[ONE Android Development] omvir:
I flashed the latest build and I noticed that the app drawer animation is choppy. Everything else seems to be fine tho. Anyone else with a similar observation?
[ONE Android Development] jamesst20:
Is that a build you just compiled? If so, thanks you ! :) Was it a fresh build?
[ONE Android Development] CptAwesomeTT:
Just dirty flashed build for 29th dec and no such issue. App drawer animation is normal.
[ONE Android Development] PresidentMcCain:
make clobber build now allows camera apps to launch without crashing... but the camera can't focus at all. Any attempt to tap-to-focus will just result in an unfocused image in any app.

#EDIT: logcat:

12-29 00:02:37.687: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.687: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.727: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.727: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.767: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.767: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.807: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.807: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.847: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.847: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.887: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.888: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.928: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.928: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:37.968: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:37.968: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.008: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:38.008: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.058: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:38.058: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.108: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:38.108: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.158: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:38.158: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.209: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!
12-29 00:02:38.209: E/mm-camera-CORE(266): af_process: Error processing AF stats!
12-29 00:02:38.269: E/mm-camera-CORE(266): af_process_parse_stats: Invalid FV data!

And also, 4K UHD recording is still broken in Google Camera in addition to these new issues.
[ONE Android Development] omvir:
Okay. Do you think I might've had a bad flash? Can that even happen lol? Anyways I'll try reflashing.
[ONE Android Development] daleski75:
http://review.cyanogenmod.org/#/c/83066/

Doing a build now and many thanks to [MENTION=3500210]tiny4579[/MENTION] for providing a build in the meantime :D
[ONE Android Development] giaur:
Not sure if it's even worth, with broken camera
[ONE Android Development] DrearierJester1:
How do u change the dpi of the nav bar of this rom
[ONE Android Development] daleski75:
You can't
[ONE Android Development] daleski75:
There are updated blobs I take it [MENTION=3500210]tiny4579[/MENTION] build included them for it to boot properly?
[ONE Android Development] daleski75:
Yup cannot connect to the camera everytime I try and launch it.
[ONE Android Development] galza:
tried 2 different 22th build and as soon as i open facebook app the phone reboots...is it only me have this issue?
[ONE Android Development] luv4greenleaves:
Wow, people still Facebook?
[ONE Android Development] 6Seven:
Same thing happens with me
[ONE Android Development] azsl1326:
Any video clips in Instagram will cause a reboot for me.
[ONE Android Development] daleski75:
If you guys haven't already turn off nu player under dev settings then reboot and see if that fixes the facebook issue.
[ONE Android Development] leximu5:
So far, this ROM has been rock solid, great battery and very stable overall. The only thing that's bugging me right now is the Clock app which crashes on boot and everytime I try to launch it. Anyone having the same issue?
[ONE Android Development] hassan_1000:
Disable NU player in developer settings! On FB if you have auto video play this is probably the cause of the bootloop
[ONE Android Development] fards:
clear app data for the clock.. been posted several times.
[ONE Android Development] azsl1326:
Nu Player was disabled in Developer Options and I still get the reboot with Instagram video clips.
[ONE Android Development] Nburnes:
AwesomePlayer should be the default already in recent builds. http://review.cyanogenmod.org/#/c/78618/
[ONE Android Development] fards:
nah steve reverted that later on this morning.

http://review.cyanogenmod.org/#/c/78826/

Back to nuplayer by default, looks like the new blobs are causing issues.