yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] FrozenCow:
I've submitted that patch on CyanogenMod. The patch is still relevant.

I tried to implement support for Motorola's CD-rom options. Another user (who does have a Motorola device) has tested it. It became clear what the flaws are of their implementation.

Motorola's CD-rom option is write-only. That means applications like DriveDroid cannot see what the current status is. This makes it hard to accurately show the user what mode USB is running on and gives a confusing experience.

Additionally, Motorola's CD-rom option covers only the first LUN (all mass storage devices that are exposed towards a PC over USB). That means when you enable the CD-rom option, only the first mass storage device will become a CD-rom device. This is somewhat confusing, because options like read-only (/ro) and removable (/removable) are available per LUN, just like my patch enables.

Lastly, if you look at the code from Motorola: https://github.com/CyanogenMod/andr...ob/cm-12.0/drivers/usb/gadget/android.c#L2445

You'll see they just set the cdrom option. In my patch, I do the same, but I make sure the option is not changed while the device is in use. Changing the option while it is in use causes problems on the PC side, which first identifies a device as a removable disk, but later is talking to a CD-rom device without the OS knowing this. You can see that in my patch this situation cannot happen: https://github.com/CyanogenMod/andr...847#diff-1b32f50b7c18aecf9b536820ba407b63R769

It seems to be compatible with Motorola's changes, but since I cannot test this on a real device, I do not know for sure.

I do see that, because there is overlap between the two, it is not ideal to accept the patch. However, at the moment Motorola's implementation is less complete and unintuitive. The patch would be very much appreciated as it saves me from explaining over email the unintuitive behavior for every user that hits this issue in DriveDroid.

I'll update the change on review.cyanogenmod.com, so the conversation can continue there.
[Nexus 6  Original Android Development] Milamber:
I'm on rooted stock and was keen to try this ROM.

Will I loose encryption if I install the ROM via TWRP as a fresh install/clean?
[Nexus 6  Original Android Development] armaki:
No
[Nexus 6  Original Android Development] dbrickg:
Haha! I really *do* wish you'd curb your loquaciousness :)
[Nexus 6  Original Android Development] OptimaPrime:
I guess we do have a maintainer I saw the next nightly change log and we are being updated to the new build fingerprint
[Nexus 6  Original Android Development] :
What does that mean? I saw the change but don't know what it will bring us

Nexus 6 64gb - CyanogenMod 12.1 (Android 5.1.1) [MENTION=3705640]520[/MENTION] dpi

LG G watch R
[Nexus 6  Original Android Development] fahadali2315:
I think what it means is it is updated to the latest sources for shamu i.e from 48M. Also some of the Mms fixes too. :) Hope its good.
[Nexus 6  Original Android Development] Milamber:
Please can someone tell me how to remove this Google search propaganda bar?
[Nexus 6  Original Android Development] Elbob10s:
Anyone figured out how to get Android Pay to work? I updated my Google Play Services and disabled SuperSU, no luck yet.
[Nexus 6  Original Android Development] tembares:
For me I long press on the home screen en choose settings. There I can disable it.

Hope this works for you, too. I don't know which launcher you use.
[Nexus 6  Original Android Development] tembares:
My Bluetooth force closes and I cannot turn it on anymore. A reboot is needed. Someone else has this issue?
[Nexus 6  Original Android Development] OptimaPrime:
Trebuchet has an option to disable it in settings
[Nexus 6  Original Android Development] Milamber:
It won't disable by long pressing, I'm using default launcher.
[Nexus 6  Original Android Development] OptimaPrime:
Long press swipe up search bar off
[Nexus 6  Original Android Development] BMXKing119:
Then why are you posting in this thread at all? You should start posting your hate posts in a separate "General" or "Q&A" thread for CM haters. You love CM so much that you are in this exact thread posting comments but hate CM so much that you "don't think CyanogenMod will ever be on my phone as a daily until those guys push out something stable". Nice logic
[Nexus 6  Original Android Development] AlxMAX:
It may also mean the binary blobs have been updated to a version like LMY48M, LYZ28K or LVY48F (I'm not sure which one) and that we have to update the radio firmware and all the other stuff from the Nexus factory image site. Look for the releases after LMY48M and choose whatever version fits your phone.

Since I brought to the discussion the subject of the binary blobs, I am interested to know which ones are used by the CyanogenMod firmware. I have seen that Google lets us download those binaries according to the region of the phone we own. For instance, one can download the LYZ28K set of binaries for the phones intended to work in the T-Mobile network or the LVY48F set for the phones intended to work with Project Fi or LMY48M for all the others.
[Nexus 6  Original Android Development] 3bs11:
Thanks for sharing. I was gonna ask how this runs for a daily driver but I remembered I should go a few pages back to see the comments and saw yours.

I just got my Nexus 6 today and I was going to try to stay on stock but there are just some annoyances that I can't believe Google hasn't addressed even now towards the phones end of cycle, like ringer volume changing from lock screen and being able to turn off the phone off from the lock screen so easily.

---------- Post added at 07:25 PM ---------- Previous post was at 07:22 PM ----------

Not on Verizon and rarely use mms so thanks for sharing. Gonna flash in a bit.

---------- Post added at 07:47 PM ---------- Previous post was at 07:25 PM ----------

Which gapps do I use? gapps-5.1-arm-2015-07-17-13-29.zip? https://github.com/cgapps/vendor_google/tree/builds/arm

---------- Post added at 08:10 PM ---------- Previous post was at 07:47 PM ----------

I screwed up somehow. Maybe things changed since I last messed around with Android phones. I went into twrp and did a factory reset then installed latest nightly and the gapps I posted. Now phone won't boot or go into recovery mode so can't go back to my stock nandroid. I'll try going back to stock using wugys toolkit :/

Edit: I used the toolkit to flash stock + unroot option without wiping data but it finished too fast somehow and the options in bootloader were fixed. I booted up phone and now CM booting up. What did I do wrong and how did I fix it? I'm really confused and would appreciate some help.
[Nexus 6  Original Android Development] jmartin72:
I used to really Like CM, and wouldn't buy a phone that I couldn't immediately root, and install CM on. I am now changing my mind, with their intention of integrating Cortana into Cyanogen OS. I liked them when they were a little group of guys that put out ROM's you could flash that let you run close to stock AOSP. They are getting way too far out there for me. Sorry, I'm out. Glad I have a Nexus, and can run stock and will get Marshmallow when it comes out on the 29th. Just my 2 cents.
[Nexus 6  Original Android Development] MizzouBrent:
Cyanogen OS is different than this rom.
[Nexus 6  Original Android Development] jmartin72:
Yes, I am aware of that, but when they integrate Cortana, do you not think it will be in this ROM too? I'm betting it will.
[Nexus 6  Original Android Development] OptimaPrime:
I'll try out some cortana love
[Nexus 6  Original Android Development] tembares:
I understand what you mean. It is not only about Cortana. It is about where does guys began with and now that they grew so fast, they start doing things and let their principles go.

In my opinion CM's principles are to build Android ROMs without any grap on it.
[Nexus 6  Original Android Development] scoobaspeaz:
Im going to be honest...dhacker is the only maintainer and he isnt really working on this right now that I know of. I think he is waiting on Marshmellow to come for WiFi support to be integrated.

How is MMS btw? Is it having any issues with receiving pictures that are very low quality compared to what you get on stock?
[Nexus 6  Original Android Development] scoobaspeaz:
Have you tried disabling VoLTE and trying the call? I have this issue sometimes with the stock rom.
[Nexus 6  Original Android Development] :
I'm on T-Mobile and the sound goes good for a few seconds if I switch to speaker than starts cracking then I go back to handset and a couple seconds it starts cracking. It was very annoying. Haven't tried anything cause I've gone to a different ROM until it is sorted out
[Nexus 6  Original Android Development] scoobaspeaz:
I am looking back through this thread a bit and noticing people have been asking about where the hell I have been and pointing out i havent posted since June. For that I'm sorry. To be honest I had things come up lately and have not really been on XDA at all. Not really bad things just some life changing great events. Also with device development kinda not being as active on the Nexus 6 concerning CM I kinda also lost some interest.

Dhacker is a great guy and smart at what he does. He doesnt post on XDA much anymore. I think you might be able to find him in his Nexus Player thread he made here on XDA. I am not sure how active he is there but I know he wont enjoy answering Nexus 6 questions there ;) Right now, like i said above, he was wanting WiFi calling merged in and was told CM is waiting for marshmallow for that to happen. That kinda got him to focus on other devices until its merged.

As with all things though the code is there for us all to grab and develop if we have the skill set. I am hoping someone else will jump in and take a look at some things.

As for the MMS "Fix" snapshot i made eons ago I didnt merge it cause it didnt fix the problem for me. The images were still too crappy compared to what you find on stock. I was actually surprised I got some positive feedback that it was fixed from one user. I could not duplicate it here on mine. The issue with MMS picture size constraints is that a few months ago a change was merged in that limited the size of the picture to something very low. Verizon i think supports 1.4 mb but this limit that was set was in the kb range. I reverted it in my local repo and rebuilt it...but it didnt fix it for me. So i was planning to look a bit deeper and see what I could find. Never really had the time to do it. I might have some here soon that I could but I am not sure if I have the skill set to fix it.
[Nexus 6  Original Android Development] scoobaspeaz:
Also just wanted to add that posting on behalf of dhacker does not mean I have cookouts and he comes over to them :) I do talk to him on hangouts to ask questions and just to shoot the bull. I asked him a while back if he minded i started up this thread on his behalf so the user base had a place to discuss and help each other out. I hope the expectation isnt that I can discuss the rom issues over a beer with him as I live pretty far away from him.

The power of the CM community is awesome. Everyone has the opportunity to chip in and fix things and you find people will do that. You will find those who find an issue and they download the source in hopes of fixing it. These people will go out and google the hell out of how to do something and try to get it fixed or really fix it. We need more of those people.

There are also those who sit on the fence and wait for others to fix issues. That is fine too as not everyone has the skill set or is able to build a skill set to fix the issues. But to those people please understand that this is a volunteer project and as such you are at the mercy of others fixing something for you. The expectation needs to be set accordingly.
[Nexus 6  Original Android Development] dbrickg:
scoobaspeaz: thanks for the updates. good to hear from you. hope all's well
[Nexus 6  Original Android Development] OptimaPrime:
I'll be honest I wasnt on stock long enough to get an MMS. I have no problems receiving or sending MMS. Other than I can't download the media through messenger; only if I receive it on Hangouts
[Nexus 6  Original Android Development] dbrickg:
I still think the MMS problem is just a byproduct of the larger cellular data problem. Ever since I switched to CM my cellular data keeps dropping. I get a little exclamation point next to my cell bar icon in the notification area. I'm on Verizon, so I don't know if this same problem exists with other carriers. Also, I switched to CM the 2nd day I had the phone, so the problem may have occurred with the original Android OS and I just didn't notice it. At any rate, as I've said before, I can usually fix the problem by a) turning cell data off and then back on b) changing the Settings / Mobile network settings / Access Point Names to something else (after a second it, usually, automatically switches back to the default, Verizon Internet), c) rebooting the phone, or, if all else fails, d) reinstalling the nightly from recovery. Oh, I forgot one other option, sometimes switching Wifi off will make cellular data work. In general, it seems like the problem is some conflict between Wifi and Cell data, as if the phone can't decide which to use, so it disables cell data. But I really don't know. The problem is so intermittent that I haven't been able to narrow it down any more precisely. These are just my general observations from the 6 months or so that I've had the phone. I don't mean this as a criticism of the OS, just hoping that my notes will help somebody figure out what's going on.
[Nexus 6  Original Android Development] OptimaPrime:
Sprint has this problem as well, I believe it is a CDMA issue and not just limited to Verizon. When I was on Verizon and had a VS980 it had the same issue with CM starting with LP builds.
[Nexus 6  Original Android Development] zero100101:
Same with the T-mobile ,but I play around the APN n changed APV lots of time :DD,, it might help for the T mobile ppl
[Nexus 6  Original Android Development] Borderpatrol1987:
I had an issue for a while where I wouldn't get cellular data unless I was connected to WiFi
[Nexus 6  Original Android Development] dbrickg:
Ah, yes! Now that you mention it, I had that, too. I'd forgotten. So, this problem with cellular data seems to be all over the map sometimes it works, sometimes it doesn't work unless WiFi is turned off, sometimes it doesn't work unless WiFi is turned on.... It's most perplexing!
[Nexus 6  Original Android Development] Borderpatrol1987:
Yes and frustrating, part of the reason I switched to M. I like CM, but I need it to work.
[Nexus 6  Original Android Development] dbrickg:
How do you like M?
[Nexus 6  Original Android Development] Borderpatrol1987:
I love it. So far I have issues with tibu restoring apps, but restoring data works, so I download from play store and restore my app data. I also have the universal AP issue, but battery life is better and I have data connection.
[Nexus 6  Original Android Development] scoobaspeaz:
Here is a commit I noticed that someone submitted that should fix the mms hit or miss types of issues:

http://review.cyanogenmod.org/#/c/104801/
[Nexus 6  Original Android Development] dbrickg:
Just saw that, too! Hurray! I'm installing the 9/23 nightly now. Hopefully that fixes the problem.

PS: 5 hours later, too early to tell for sure, especially given the intermittent nature of the problem, but so far so good

PPS: 5 days later, still looking good.
[Nexus 6  Original Android Development] mllora81:
I've seen other roms that have an option to enable 4 tiles per row in quick settings. Anyone know if this is possible this rom?
[Nexus 6  Original Android Development] dbrickg:
I didn't see any option for that... doesn't mean it doesn't exist someplace, but not anyplace where I looked :)
[Nexus 6  Original Android Development] tembares:
I know what you are talking about. I searched it for you, but I think the option is not activated anymore.

Did you know that you can search in the settings? Go into settings and click the search button in the right to corner. Enter tiles and you'll see all tile-options.

Enjoy your day!
[Nexus 6  Original Android Development] dbrickg:
Wow! Cool! No, I didn't know you could search settings. That's great!
[Nexus 6  Original Android Development] MartinX3:
Goodbye dear Galaxy S2 Community :'(

I lost my Galaxy S2 1 week ago, after 6 years of Cyanogenmod-Love <3

Thank you very much, that you gave this holy device the long life which it deserved! <3
[Nexus 6  Original Android Development] DreamFX:
This is the Nexus 6 community but sorry for your loss. Lol.
[Nexus 6  Original Android Development] AlxMAX:
Excuse me for the off topic, but I could not help myself: I feel sorry for your loss, but you could always buy a Nexus 6, install CM 12.1 and (re)join the community for another 6 years of Cyanogenmod-Love. ;)
[Nexus 6  Original Android Development] MartinX3:
Sorry, my Fault xD

Hahahahahahahaha :D

I buied a Nexus 6 and got it last friday, CM12.1 28/09/2015 with XPosed V74 works perfect on it :p

I will use it at least 6 years and enjoy the love of Android, XDA und CM :silly:
[Nexus 6  Original Android Development] maxpower7:
You had a 4-year-old device for 6 years? Impressive.
[Nexus 6  Original Android Development] def1003:
[IMG="help"]http://s21.postimg.org/qvf7n0n3q/tmp_6787_Screenshot_2015_09_30_00_15_48_16465895.jpg[/IMG]

anyone know how i can make the god damn Google search bar go away
[Nexus 6  Original Android Development] auriken:
Hello, when I am on landscape, my soft keys go away and I cannot use them. I am on Sunday's nightly.
[Nexus 6  Original Android Development] bmakk2055:
Try rebooting
[Nexus 6  Original Android Development] dlbarron:
I am seeing that too. The only way to get rid of it is to go into the homescreen settings and turn it off. Long touch on the home screen and you'll get the menu for selection of Wallpapers, Widgets, Settings. Over Widgets there is a small triangle of dots. Touch that to get to the settings for home screen.

Since yesterday's nightly I have been seeing the same thing you are. Normally I keep the search bar turned off all the time, so to get rid of it now I have to turn it on, then turn it back off.

Hopefully this will be corrected soon.
[Nexus 6  Original Android Development] bill3508:
What kernel are you folks using,?
[Nexus 6  Original Android Development] MartinX3:
Oh, you're right, it was my fault. :angel:

4 years is correct, but the time was so wonderful, it felt like 6 years xD :silly:
[Nexus 6  Original Android Development] dknotty:
I've just swapped to a nexus 6. Not enjoying the pure Android experience and thinking about installing cyanogenmod.

Does this work with GoPro cameras? My previous OnePlus (which had cyanogenmod) did not...
[Nexus 6  Original Android Development] sjgore:
If you mean does a Nexus 6 running CM12.1 connect to a GoPro using the official GoPro app, then yes it does. Using it with a Hero3+ here with no issues whatsoever.
[Nexus 6  Original Android Development] 3bs11:
What are you using for your different status bar icons?
[Nexus 6  Original Android Development] Bwyan Benton:
Lmfao

Sent from my Nexus 6
[Nexus 6  Original Android Development] dbrickg:
Probably custom kernel with overclocked CPU. That'd be my guess
[Nexus 6  Original Android Development] mexiken:
Quick question: if you download a nightly, but flash a different kernel that doesn't force encrypt, will you stay unencrypted????
[Nexus 6  Original Android Development] ibraheeemz:
I'm sure it was just an expression of frustration of losing the phone, loll
[Nexus 6  Original Android Development] jmartin72:
Do we have a maintainer yet, or do I stay on stock marshmallow forever?
[Nexus 6  Original Android Development] criminalzen:
forever of course.... you are being sarcastic, right?
[Nexus 6  Original Android Development] jmartin72:
I will be on stock until when and if the N6 get a maintainer, or I get another Nexus whatever comes first.
[Nexus 6  Original Android Development] knirirr:
I've been getting settings app crashes when trying to use privacy guard or look at the details of any app (e..g to clear cache or data). A crash on the 6th Oct. nightly produced this:

java.lang.OutOfMemoryError: Failed to allocate a 112908 byte allocation with 41440 free bytes and 40KB until OOM
at dalvik.system.VMRuntime.newNonMovableArray(Native Method)
at android.graphics.BitmapFactory.nativeDecodeAsset(Native Method)
at android.graphics.BitmapFactory.decodeStream(BitmapFactory.java:608)
at android.graphics.BitmapFactory.decodeResourceStream(BitmapFactory.java:444)
at android.graphics.drawable.Drawable.createFromResourceStream(Drawable.java:988)
at android.content.res.Resources.loadDrawableForCookie(Resources.java:2621)
at android.content.res.Resources.loadDrawable(Resources.java:2528)
at android.content.res.Resources.getDrawable(Resources.java:823)
at android.content.res.Resources.getDrawable(Resources.java:799)
at android.content.res.Resources.getDrawable(Resources.java:774)
at android.app.ApplicationPackageManager.getDrawable(ApplicationPackageManager.java:744)
at android.app.ApplicationPackageManager.loadUnbadgedItemIcon(ApplicationPackageManager.java:1753)
at android.app.ApplicationPackageManager.loadItemIcon(ApplicationPackageManager.java:1733)
at android.content.pm.PackageItemInfo.loadIcon(PackageItemInfo.java:163)
at com.android.settings.applications.ApplicationsState$AppEntry.ensureIconLocked(ApplicationsState.java:143)
at com.android.settings.applications.ApplicationsState$BackgroundHandler.handleMessage(ApplicationsState.java:995)
at android.os.Handler.dispatchMessage(Handler.java:102)
at android.os.Looper.loop(Looper.java:135)
at android.os.HandlerThread.run(HandlerThread.java:61)

Has anyone else seen this, or can anyone suggest any remedy short of a wipe and re-install? I'll probably try the latter after a few days, when there's time, but I'd rather not.
[Nexus 6  Original Android Development] dbrickg:
I just tried clearing cache and data on a couple of apps. Didn't get any crashing. Checked privacy guard on a couple of things, too. No crashes.
[Nexus 6  Original Android Development] knirirr:
Thanks. It's probably a fault with my installation, then.
[Nexus 6  Original Android Development] mexiken:
Anyone????

I'm coming from a non-CM ROM. Unencrypted.

If I:

Wipe

Flash CM

Flash custom kernel that doesn't enforce encryption.

Boot

Will I stay unencrypted or is there some other thing I've gotta do????

Thanks.
[Nexus 6  Original Android Development] DreamFX:
You will stay unencrypted.
[Nexus 6  Original Android Development] dbrickg:
Sorry, I don't know the answer to that. It seems *likely* that you'll stay unencrypted, if you flash a non-enforcing kernel, but I really don't know. I'm still rather miffed that google/android decided to encrypt my phone without asking me about it.
[Nexus 6  Original Android Development] pepez05:
Has I've read in last pages of this topic, CM12.1 seems prety stable and can be used as daily use no ?

Any problem in particular ? Battery is better, worth or same as Android Lollipop Stock ?
[Nexus 6  Original Android Development] AlxMAX:
It seems like the BFQ I/O scheduler has been merged into the kernel. I am curious how this will change the performance. I've found some comparisons where BFQ was shown as winner against CFQ. A while ago I have also found some comparisons of FIOPS against the others and it was the winner.
[Nexus 6  Original Android Development] jmartin72:
Does that mean we have a maintainer, or is Cyanogen submitting the changes?
[Nexus 6  Original Android Development] AlxMAX:
No, there's no new maintainer. The code has been committed by Steve Kondik based on the work of the very developers of BFQ (Paolo Valente and co). Off topic: please stop asking for a maintainer. It's not an easy job. Besides, it's a Nexus device and it has a lot of support from the development teams at Google.
[Nexus 6  Original Android Development] Milamber:
What version of XPOSED Framework should I be using with this ROM?
[Nexus 6  Original Android Development] warfenix:
I would be looking in the xposed thread. Where ever that is.