yashsingh1/xdaforums huggingface dataset:
[Nexus 5 Original Android Development] mmo.xda:
It seems that toybox is work in progress.

There are several commits related to ToyBox from yesterday so I think movement is not finished yet or there has not been time to adapt CM File Manager.

On the other hand, Root Explorer developer team was not aware of this "movement".

I've sent several diagnostics and test cases in order to help them to update app.

Regards
[Nexus 5 Original Android Development] da_toffy:
Thanks! I was directed here from the MultiROM thread.

As I see it, your modified script just skips the checksum verification. Do you have any idea why this check fails? Is that a MultiROM problem?
[Nexus 5 Original Android Development] Sly_67:
[MENTION=4152171]myfluxi[/MENTION] I'm on cm13 20151115 CAF build. It's working very well no FC at all. Only why I can't use supersu instead of CM root access in developer options. Must we wait for newer version of supersu to fix this problem in CM 13? Is it related with busybox? Now I'll dirty flash 20151117 CAF !

Sent from my Nexus 5 CAF
[Nexus 5 Original Android Development] fleischbanane:
Flashed cm-13.0-20151117-UNOFFICIAL-hammerheadcaf.zip today with open-gapps and everything works as expected... the litte problems were mentioned bevor and are not rom-related. Hope Ad-Away will be fixed soon to work with CM again. ;)

Thanks for your hard work keepin our beloved Nexus 5 up to date! :highfive:
[Nexus 5 Original Android Development] nashy10:
clock app is not showing weather after multiple reboots and setting location manually, also pictures not showing up in twitter. Latest build. Other than that, very smooth!also the Tapatalk app is not showing text field as I type this message
[Nexus 5 Original Android Development] JulianXhokaxhiu:
Mobile data: cannot change date range

[MENTION=4152171]myfluxi[/MENTION] I found another small bug on the Android UI ( I know it is because another friend of mine has an opo with CM13 and his case it works fine ).

As you see in the screeshot I cannot change the starting date for my mobile plan, but I'm having this weirdo dropdown with dates from today to 1971. I guess it's a bug? The voice to change the date is not there. Thank you in advance :)

//EDIT: I found also that maybe this patch is related to the issues we have at least with AdAWay. Is it possible to know if it's merged on 17th November build?
[Nexus 5 Original Android Development] mmo.xda:
[UNOFFICIAL] [ROM] [6.0] [MARSHMALLOW] CyanogenMod 13 for Nexus 5 [CAF]

Wrong [emoji853][emoji853][emoji853]
[Nexus 5 Original Android Development] ziggynlp:
AdAway still isn't working in 20151117 build.
[Nexus 5 Original Android Development] banciii:
That weird vibration when I see gradient colors (like on the login screen of Instagram) is a known issue? Or is it an intentional Instagram effect? (I doubt it cause I maybe remember something similar color vibration from some weeks ago.) I just saw it on build 1117.
[Nexus 5 Original Android Development] fleischbanane:
I have a short question: Is it not possible to update the kernel to 3.4.110 or are there no advantages for us? :confused:
[Nexus 5 Original Android Development] Stefano187:
Hello,

If you want, you can flash a custom kernel updated to 3.4.110 [emoji106]

Regards

Stefano
[Nexus 5 Original Android Development] sachin123:
Is anyone else also having heavy battery drain from WiFi and Miscellaneous?

If so, how did you get rid of it?

Also, has anyone tried Xposed for Marshmallow yet?
[Nexus 5 Original Android Development] fleischbanane:
I think there are no custom kernels for these CAF builds but my question is mainly if there are benefits from the update or if it's useless for mobiles unlike desktop distributions.
[Nexus 5 Original Android Development] EnginEAR:
http://xdaforums.com/google-nexus-5/development/kernel-racer-v8-0-cm-4-4-3-mrom-fx-sd-t2726080

This is a CAF custom kernel and it works great with unofficial CM13 CAF...
[Nexus 5 Original Android Development] banciii:
Yes, I also have 59% misc, while wifi 41% and screen is only at 27%. And I donno how to, maybe it will be fixed later.

Yes, I am using Xposed for M because of Greenify. That's the only module I use and I have no problem with it.

My bigger problem is the late of my clock. This attached screenshot has been made at 17:04. But I already had 20, 30 minutes late earlier. Did anyone noticed similar?
[Nexus 5 Original Android Development] amir7777:
I'm pretty sure the clock bug is a known MM thing, I don't think it has anything to do with the ROM. Someone correct me if I'm wrong
[Nexus 5 Original Android Development] KentuckyGuy447:
Is USB-OTG enabled by default or is that feature available in these builds? Can't seem to get the system to notice my USB flash drive like I could in CM12.1 CAF. I know these are just test builds but just curious.

---------- Post added at 06:09 AM ---------- Previous post was at 05:51 AM ----------

Go to Location in settings and click the ... In the upper right-hand corner and click scanning. Turn off always scanning for Wifi and turn of the Bluetooth scanning too. It solved the WiFi problem for me. I think the millcellaneous battery drain is due to account syncing in the background. Since there is no quick tiles ATM idk if there is anyway to turn off account sycing or I would test this.

EDIT: I found a way to turn off account syncingin background but millcellaneous still has a high drain so maybe something else is also contributing. For anyone interested is turning off background sycing go to Accounts, click the ... In the upper right hand corner, and uncheck auto-sync data. Please note you have to manullay sync data if you decide to do this but you can renable it at anytime. Hope this helps somewhat!
[Nexus 5 Original Android Development] JGoldz75:
Has anyone tested this?
[Nexus 5 Original Android Development] Alx31:
[MENTION=4145479]experience7[/MENTION]

can we please know wich sources been used for these builds? is it official cm13 repos? in this case i guess u need to link them in first post anyways...
[Nexus 5 Original Android Development] :
[MENTION=5265704]Alx31[/MENTION]: To be honest, I don't even know. I'm just maintaining the thread for myfluxi so he doesn't have to take care of that :) (Long ago he said that he doesn't want to do it himself - so I asked wether I'm allowed to create one)

Maybe he can answer that question :)
[Nexus 5 Original Android Development] Alx31:
Well its in xda rules to link sources...at least kernel one

Tapatalked from Z3
[Nexus 5 Original Android Development] ziggynlp:
Here you have sources: https://github.com/CyanogenMod/android_kernel_lge_hammerhead/tree/cm-13.0-caf
[Nexus 5 Original Android Development] Alx31:
dude if i asked to op wich sources he used, its because i wanna know wich one he used, i exactly know where to find cm kernel im not dumb, its written unofficial, so then i kindly asked wich ones are used, and link to his device trees would be kool too...thats what open sources means....and if he used official stuff, just need to be mentioned...

cheerz
[Nexus 5 Original Android Development] q1t1:
He is using these sources !

Myfluxi is the CM maintainer for hammerhead / hammerheadcaf ; his builds are unofficial because CM13 hasn't started yet...
[Nexus 5 Original Android Development] Alx31:
ok thx
[Nexus 5 Original Android Development] komawoyo:
Read OP Please
[Nexus 5 Original Android Development] Alx31:
i did, was just wondering if the sources used to make the builds provided here use the official sources repos or personnal repos wich contains maybe extra commits....because

it is not stated

in the op ( q1t1 said yes but he's not the one who built) , if yes please show me cuz apparently im blind.

Also leave it, nvm; im out sorry for the inconvenience, i will ask to myfluxi cuz its polluting the thread for nothing, the op didn't compiled rom himself too.
[Nexus 5 Original Android Development] komawoyo:
Yeah my bad, I see that you have trouble finding the correct information on the OP. I honestly thought it was obvious that he was sharing information regarding the unofficial CM 13 builds given post #3 and #4 to share some of the insights (I'm sure we all dont read the posts in the thread) :
[Nexus 5 Original Android Development] Alx31:
well its because im having some errors as this one....using cm official repos

hammerheadcaf/obj/SHARED_LIBRARIES/power.msm8974_intermediates/power.o] Error 1

but indeed could avoid messing thread if i was 100% sure these builds here using official repos; just by looking at the commits...then diff with the stuff i use, it will tell me if im missing something or if its from somewhere else than device trees.....
[Nexus 5 Original Android Development] kenshin33:
builds just fine over here !
[Nexus 5 Original Android Development] Alx31:
ok thanks for the info bro...

(j'ai jamais dit que je compilais cyanogen hein :laugh: mais j'utilise juste leur repo caf)
[Nexus 5 Original Android Development] andrei1015:
http://review.cyanogenmod.org/#/c/120142/
[Nexus 5 Original Android Development] rachanta:
CM official Kernel source: https://github.com/CyanogenMod/android_kernel_lge_hammerhead/commits/cm-13.0-caf

This is behind myfluxi's personal github branch for cm 13 caf:

https://github.com/myfluxi/android_kernel_lge_hammerhead/commits/cm-13.0-caf-151121?page=2

You can check for device ( ROM) as well after you get to the links and explore a bit.
[Nexus 5 Original Android Development] Alx31:
yeah thats ok thanks i checked/found dat kernel yesterday and he prolly built from there and not from cm sources....not only that but his vendors too are in font of TheMuppets ones, and device seems to be moreless even...

So by seeing his repos he obviously built these test builds from there and not from official cm sources, else it makes no sense...i guess once well tested he will push to gerrit...

cheerz
[Nexus 5 Original Android Development] kenshin33:
no problem !

(ah mais c'est une histoire alors)

---------- Post added at 10:42 AM ---------- Previous post was at 10:41 AM ----------

you guessed right!
[Nexus 5 Original Android Development] :
I'm currently building my own CM-13.0 CAF :) There've been a lot of changes since the last update from myfluxi and if everything works fine on my side, I'll try to upload the build :)

Anyways, my connection is damn slow - so the 20151122 build will most likely arrive tomorrow - if at all :P

[MENTION=5265704]Alx31[/MENTION]: Yeah, it's best to ask myfluxi which sources he used. Like said before - these are his unofficial sources. His builts always used 'official' and 'pure' CM sources - so I guess the same applies for his latest CM13 builds, too. But you have to ask the man himself to be 100% sure.

By the way: My build will use official sources, too. And it's built on a virtual machine running Ubuntu :)
[Nexus 5 Original Android Development] Sly_67:
Why we can't use Supersu for root? I'm using CM root for now, but I'll be very happy if I cann use Supersu instead.

Sent from Nexus 5 CM13 CAF
[Nexus 5 Original Android Development] fagyi:
android phone crashes every 20 sec if you upgrade your device from before version, this is a bug on upstream two days ago. They updated the provider which brake my N5 phone :(

Hope they fix it soon. But maybe working with clean install, but i dont remember i tested it with clean setup or no.

System remount to RW its a toybox issue on upstream. So not device related. Steve says fixing it later time.
[Nexus 5 Original Android Development] kenshin33:
phone somthing crashing on startup and the phone is sluggish and hot???

look in logcat and see if it is complaining about a locked sqlite database, if it is the case :

"rm /data/user/0/com.android.providers.telephony/databases/telephony.db*" and reboot
[Nexus 5 Original Android Development] :
[MENTION=4453138]fagyi[/MENTION]: Maybe a commit broke something - but I can't imagine that they left it in this state for about 2 days :) I'm not sure but as soon as my build is done, I'll do a backup and try to update from 11/11 build :)

PS: First build didn't finish because it stopped with an memory related error. I adressed some more memory to my virtual machine. Hopefully this fixes the issue :) Currently building...
[Nexus 5 Original Android Development] Balino:
Is it possible to have a different topic for your builds?

Bugs reporting etc would be difficult .

Just a suggestion, I don't use cm at all.
[Nexus 5 Original Android Development] fagyi:
Yes, I looked this on the review, but it doesnt help for me. ( I removed the com.android.providers.telephony dir from my data not just the db file, but nothing. ) After I reverted some related commits, but it looks like need more, because the issue still there.

Actually on newest build for me not recognize my SIM card, and Phone crashing every 5-20 sec. So its not ready for the users, for upgrade from before version. Soon testing via clean install.

Im on the non caf version, let me know how its work on caf, but i think the issue still there, because another device got this problem.

EDIT:

Working with clean install without FC's!

EDIT2:

We need remove data for upgrade from before version :

data/data/com.android.providers.telephony/*

&

data/user/0/ com.android.providers.telephony/*

We dont have data/0 folder. We have data/user/0/
[Nexus 5 Original Android Development] myfluxi:
All sources are always on either CM's official or my personal git. Not just kernel but also devicetree and props.

Updating to kernel.org mainline is not just useless but most of the time the ultimate sin. QCOM merges relevant stuff for us and I pick stuff on top (not a lot, though). QCOM 3.10 branches have much more bleeding edge stuff for us. There is no way, the kernel can be improved. This does not include functionality that is not tolerated in CM such as dt2w without proper firmware support, undervolting or dual boot, obviously.

It might be nessecary to remove: /data/data/com.android.providers.telephony (as mentioned above). Presently, I'm only interested in hard kernel reboots (block/fs) or watchdog resets.

cm-13.0-20151123-UNOFFICIAL-hammerheadcaf.zip

Edit: Reupload, missed a commit for pick-up. Only difference is two lines in build.prop.
[Nexus 5 Original Android Development] :
First off all, thanks for the build! I had some trouble with mine yesterday (first run: too less RAM; second run: too less hard-drive capacity). Using a virtual machine here - but I guess everyone makes mistakes in the first place :D

Sorry to quote you again, but this is exactly what I want to hightlight:

Hopefully everyone reads this since a lot of people unfortunately still think you're our maid-of-all-work :D
[Nexus 5 Original Android Development] myfluxi:
I even got another new shiny N5 device lately (because everything else including and especially bullhead/N5X is so disappointing). Maybe Snapdragon 820 will be a game changer.
[Nexus 5 Original Android Development] mmo.xda:
From 11/11 CM13 hammerheadcaf build.

- Deleted in TWRP folfer: /data/data/com.android.providers.telephony

- It is not possible to remove anything from /data/user/0 'cause link is not accesible.

- Install 23/11 build.

- Reboot System

Everything seems to be working fine.

Thanks again for your awesome effort.

Regards
[Nexus 5 Original Android Development] Alx31:
if i just can suggest....imho if u don't have a proper setup to build on vm; u should make a dual boot with whatever distro...vm is taking lot of ram, especially android building, i have 16gb and if i do something else than just building ( during the 16/17 minutes it takes :p ) it goes easily over 7/8gb ram soon as u have few tabs open in chrome/chromium...just sayin (just pm me if u need help to setup the dual boot)
[Nexus 5 Original Android Development] :
no daul boot for me cuz wanna haz my windooze in foregruond
[Nexus 5 Original Android Development] Alx31:
aw ok then ...:good:
[Nexus 5 Original Android Development] :
[MENTION=4152171]myfluxi[/MENTION]: Can you give me a helping hand for a second?

I downloaded the CM source code and did "breakfast hammerheadcaf". As far as I understand, this creates a local manifest (which is called roomservice.xml by default). If I build with these sources I use official CM sources. Am I right so far with this assumption? Because this one worked for me and I got the appropriate files in the output dir. Haven't flashed anything yet but naming/size/file structure and everything else looks good.

Now if I would like to build using your sources -> Can I do so with another local manifest? I tried to create a second one which lists your sources - but as soon as I 'repo sync' it throws out errors. Something like 'duplicate path' and stuff. I guess that's because the other local manifest file uses these paths as well. I'm a bit lost here.

I'd appreciate if you / anyone else could help me to find a decent solution :)

...hope this all makes some sense :D

Thanks in advance!

EDIT: I'm still learning stuff and... I just found an article which describes that we can also remove projects using a local manifest. So my thought: Is it possible to replace CM projects/repositories by removing them in the first place and then re-syncing them from myfluxis github? Any help is greatly appreciated :)
[Nexus 5 Original Android Development] vikashhero:
Is superSU's recovery install causing anyone else to bootloop?
[Nexus 5 Original Android Development] Ajfink:
You can add his repositories in your manifest. Just remove the CM ones and maintain the same structure to setting up the way the manifest lists them. Run a repo sync and you should be good, then a brunch hammerheadcaf.
[Nexus 5 Original Android Development] jugoslavpetrovic:
This ROM did not asked me which apps to restore from google account. Any solution?

Also, I prefer CF SuperSU, which one and how to ?
[Nexus 5 Original Android Development] scrack26:
Did you install gapps aswell? or just this ROM? also use the SuperSU Beta, but not sure if it is working on CM13, I am not using it atm. currently stock everything on CM13-caf
[Nexus 5 Original Android Development] jugoslavpetrovic:
Yes, flashed recommended open gapps 6.0 for MM, flashed also superSU 2.56. System is working, google is working but I got used to to be asked on initial start from which device to restore apps connected with the same google account. Im coming from BlissPop which development got a bit delayed for MM, its still on LP release. I would like better battery life so thats why I decided to try MM but so far already having issues with this one, and also with other roms which every single one recommends different gapps. Its still a mess as I see.
[Nexus 5 Original Android Development] kenshin33:
not clean but you can edit directly roomservice.xml and change the relevant parts. As for your setup you better have a lot of RAM --minmum of 8-- and a lot of space!
[Nexus 5 Original Android Development] banciii:
With the latest build I can't make photos with any camera app (cm/google/snap). :( Are there anybody who has the same issue?

Tapatalk-kal küldve az én Nexus 5 CAF-el
[Nexus 5 Original Android Development] mmo.xda:
Same issue here.

No photos are taken.

Regards
[Nexus 5 Original Android Development] myfluxi:
Cam is fine everywhere.

Regarding building hhcaf: presently I maintain branches by day so best advice is to add my repos as remote branches and then checkout to the latest (or whichever seems appropriate). E.g. for kernel:

cd kernel/lge/hammerhead
git remote add fluxi https://github.com/myfluxi/android_kernel_lge_hammerhead
git fetch fluxi
git checkout fluxi/cm-13.0-caf-yymmdd

Then build.
[Nexus 5 Original Android Development] fleischbanane:
No problems here with Google Camera. HDR is also working fine.
[Nexus 5 Original Android Development] mmo.xda:
In my hammerheadcaf Camera FV-5 is not working.

It seems like photo is taken, but no file is written to DCIM folfer.

Instagram cam also fails. It freezes the app when taking a photo.

So samething has changes since last build (not saying a hammerheadcaf error, maybe upstream one).

Here is a sample with Camera FV-5 error (link).

Maybe someone could bring us light about it.

Update: The error seems to be here:

Regards
[Nexus 5 Original Android Development] simplicio11:
CM 13 official nighlty! http://www.cyanogenmod.org/blog/a-marshmallowy-cm

p.s. not for our N5 CAF yet :crying:
[Nexus 5 Original Android Development] banciii:
Then I don't understand it. I even made a full clean install, wiped internal storage too and still no success. DCIM directory has been made but no photos in it. :( Should I attach any logcat or something or mmo's report is enought for now. :o
[Nexus 5 Original Android Development] mmo.xda:
Probably is outside MyFluxi's duties.

Maybe it is a general CM13 stream problem and we need to wait until it is fixed like storage mount.

Regards
[Nexus 5 Original Android Development] myfluxi:
That's a proper bug report and you have the possible solution as well in the log. We need new blobs that are only available on Google's internal repos.

Revert: https://github.com/myfluxi/android_...mmit/4afde7bcb9ba540647f76622b5035160a053c47c

And also, we inherit a bad sepolicy from CM's qcom/sepolicy, we're better off doing it correctly ourselves.
[Nexus 5 Original Android Development] reesedizan:
Using Sprint. Cannot get service/data to work. Anyone have this this issue or know a workaround? Seems prevalent with caf. Thank you for your help.

---------- Post added at 04:55 PM ---------- Previous post was at 04:50 PM ----------

Never mind. Think I found a fix. Keep you posted.
[Nexus 5 Original Android Development] swapnildixit3:
Can't wait more...[emoji19] [MENTION=4152171]myfluxi[/MENTION] - any idea? Or ETA?
[Nexus 5 Original Android Development] Ajfink:
The first rule of CyanogenMod....
[Nexus 5 Original Android Development] joshuas_79:
"The first rule of Cyanogenmod is: you do not talk about Cyanogenmod."

Sorry , I had to :D
[Nexus 5 Original Android Development] andrei1015:
Dem last few days waiting for that commit about your device getting the newest update. Awesome! Thanks [MENTION=4152171]myfluxi[/MENTION]!
[Nexus 5 Original Android Development] :
Same here! Unofficial builds are incredibly stable already though :eek:

Just dropped him a few cents again for his tireless work! :)
[Nexus 5 Original Android Development] myfluxi:
cm-13.0-20151124-UNOFFICIAL-hammerheadcaf.zip

You would not like nightlies as audio/video during recording is terribly out of sync there. Sultan posted a fix but - yet again - this crucial patch is being ignored. And the sweet new stuff in device/kernel will take a while until I merge it into the nightlies.
[Nexus 5 Original Android Development] jugoslavpetrovic:
Figured out that if I remove CM setup wizard from Open Gapps, afterwards when system starts for the first time, I am getting to choose apps to restore.

After I flashed CF SuperSU, my favorite I cant get root access. What can I do?
[Nexus 5 Original Android Development] amnher:
if I want to use c-apps.

I only need to flash rom+c-apps? or rom+gapps(mini)+c-apps?
[Nexus 5 Original Android Development] madsurgeon:
23rd build is just brilliant! Very stable and phenomenal battery. Haven't had this great a battery life in ages.

Thank you! [MENTION=4152171]myfluxi[/MENTION]
[Nexus 5 Original Android Development] madsurgeon:
Doesn't matter, as long as the boot.img is enforcing, its not going to allow /system to mount as rw. CM's built in root is more than adequate for the rest of it. 2.56 doesnt allow /system to mount as rw either. Tried flashing SELinux capable superuser too, it works well, just wont allow the /system mount. Personally, I'm good with CM's root coz flashing another kernel would detract from the whole experience imo.
[Nexus 5 Original Android Development] mmo.xda:
Awesome work, as usual from Myfluxi.

Camera FV-5 is working again.

Many thanks!!!

Regards