yashsingh1/xdaforums huggingface dataset:
[Nexus 6  Original Android Development] Tylog:
http://xdaforums.com/showthread.php?t=3034811

V75 arm is the one you need
[Nexus 6  Original Android Development] roton:
Does this have the 2 newest stagefright vulns patched?

CVE-2015-3876

CVE-2015-6602
[Nexus 6  Original Android Development] Shano56:
View attachment 3503464
[Nexus 6  Original Android Development] knirirr:
I've since tried a full wipe and clean install of Cyanogenmod and Exodus ROMs; they're fine on first install but once I start restoring apps with Titanium Backup then the settings crash recurs. Unfortunately I have rather a lot of apps and it's not clear which one is responsible, assuming that that is indeed the cause.
[Nexus 6  Original Android Development] dbrickg:
Hmm, you do realize, don't you, that this is a forum for the cyanogenmod 12.1 rom? Exodus has a forum here:

http://xdaforums.com/oneplus-one/orig-development/official-vaniraosp-t2890749

There are probably other forums for exodus, but this is the first one I found on xda
[Nexus 6  Original Android Development] knirirr:
Yes. I'm running the CM 12.1 nightly (12th Oct), having also briefly tried another ROM to see if the same problem occurred there, which it does.
[Nexus 6  Original Android Development] dbrickg:
Hmm, sorry, I see I misunderstood your post. Anyway, I'm not sure what to say. I remember reading somewhere that restoring via Titanium can cause problems. As I understand it, you might as well not do a clean install, if you're then going to restore via Titanium. It will reintroduce the same underlying structure that was there before you did the clean wipe. I don't have much experience with it, though, and might well be mistaken. I think that to do a really clean install, you need to reinstall each app from scratch. A huge pain in the butt, but that's the only way I can see to get rid of your problem crashes. Or you could use Titanium to restore apps one at a time, testing each, and see which one is causing the problem, then uninstalling that app and reinstalling just that one.
[Nexus 6  Original Android Development] knirirr:
I think you're right in that I'll have to avoid that part of the restore.

The main reason I use Titanium Backup is to back up all the app data. I think that what I'll have to do instead is a clean install, followed by allowing the setup process to re-download the apps I had installed, and then use TB only for those cases where I need to recover some of an app's data. It's been a bit of a nuisance when restoring and sometimes hangs on some apps. If settings crashes occur after allowing the Play Store to restore then it might indicate a dodgy app, but if not then it would be TB which would be to blame.

I would be interested in finding an alternative to TB, which can restore the Android ID and app data, but haven't yet found anything I'd dare risk.
[Nexus 6  Original Android Development] RanceJustice:
Thank you for bringing an official CyanogenMod 12.1 (and beyond!) thread to the forums! I have a couple of questions as I'd like to make use of CM12.1 based ROMs and I've gotten some conflicting reports on various features and issues.

1. VoLTE on T-Mobile - I am glad to hear you say that VoLTE is now supported on CM12.1. Before installing any custom 5.1.x ROMs , I flashed a modified stock LMY47M image in order to ensure I got the radio and whatnot from that build. I can see that I have LTE data in my calling area (though, I am often on WiFi , which of course shows its icon instead of LTE's when activated. You can still make VoLTE calls when you're using WiFi for data?) Is there any way I can confirm it is working for me?

2. HD Audio codec - Does CM12.1 support the usage of the HD Audio codec? I'm to understand that either via VoLTE (which as of 5.1 we're supposed to have) and WiFi Calling (which we don't have yet), allows the use of the HD Audio codec for better audio quality. I hear there is supposed to be a "HD" icon during a call provided both sides have HD Audio codec compliant phones, but I've never seen one to date. I've made calls between my Nexus 6 and someone with a Galaxy S6, both of which should have HD Audio capability, but I remember reading somewhere (unconfirmed) rumors that HD Audio only works between compliant mobiles on the same network? Maybe this is an issue as I am using T-Mobile, yet the Galaxy S6 I've called is on Sprint. Likewise, I've called landline users with Verizon FIOS (and thus VOIP, so possibly better voice quality supporting as well) but to no avail. It would be nice to have the additional audio quality of the HD codec and maybe I'm just not in its use cases, but is CM12.1 supporting it at least would be nice.

3. Does CM12.1 have a built in Tethering Checking Disabled (for T-Mobile )? I've seen a handful of ROMs that claim to offer this feature, both AOSP and CM based, but I was wondering if it was included in the CM codebase. I have an unlimited T-Mobile data plan and I'd like to be able to use WiFi hotspot creation (as well as USB tethering/bluetooth) to share it without worry that one kind of data or another is somehow biased, and have to go around setting user agents and other workarounds. It would be great if CM just had this feature built in and thus I could use any CM12.1 based ROM without worry!

4. Does CM come with a kernel notably different from the stock one and/or depend on any particular kernel behavior? That is to say, is there reason to believe that there would be incompatibilities using Vindicator, Zen, CodeBlue, ElementalX or any of the other kernels discussed here, or any requirements to make it easier for these kernels to work with CM?

Thanks again for all your hard work.

Oh, and check this out - http://phandroid.com/2015/05/21/nexus-6-wifi-calling-update-memorial-weekend/ - Maybe built in, pure AOSP WiFi calling will be coming to Nexus 6 this weekend?! If this is the case, I look forward to seeing it integrated into CyanogenMod as soon as possible!
[Nexus 6  Original Android Development] scoobaspeaz:
You are welcome :D Now on to the questions haha

1. VoLTE, according to [MENTION=4112553]dhacker29[/MENTION] , is not working yet. I personally cannot test anything other than making a call and seeing if my data is still on. I can do that tomorrow but the developer says its not working yet so I'm not expecting it to. He does plan to work on it but he is one guy supporting many devices.

2. Let me reach out to dhacker and get a response on that. I personally don't know the answer regarding if its using the HD audio or not. As for how VoLTE HD Calling works you are sadly correct. I too read that, at least on Verizon, you had to be calling from Verizon to Verizon for HD VoLTE calling to work. Also the video portion of the call does not work yet either for the Nexus 6 on Verizon. I am not sure if the same is true for T-Mobile.

3. tethering should be enabled. There should not be a reason for it not to be enabled.

4. the kernel is the stock kernel pretty much. Its not based on much of anything other than the aosp kernel. there are custom kernels you can use out there with this rom though. I personally just use the stock kernel that comes with CM.
[Nexus 6  Original Android Development] scoobaspeaz:
HD Audio codec is included but since VoLTE is not working currently you wont be able to use it. But its there for when it is working :)
[Nexus 6  Original Android Development] RanceJustice:
Thank you kindly for all those replies! I really hope that VoLTE and HDVoice will be working soon. The other fellow in this thread who claims to have VoLTE working, I wonder if this is because of a difference in carriers? For instance, I remember that as of CM12 and whenever there was something written about VoLTE being broken ,it was noted that this was either on Verizon or Sprint, the CDMA carriers. However, as T-Mobile (as well as ATT, and all the MVNOs using both networks) is based on GSM. Is it possible this could explain the difference in reports, or is VoLTE/HD Voice simply not working across the board?

Oh and with regards to tethering, I wasn't speaking simply of tethering being enabled, but rather if Tethering Checking was disabled. That is say, if tethering data appears/is recorded any different than device-based data. Many carriers seem to have some sort of system in place to try and discover if you're tethering and then (depending on the carrier) treat you data use differently. Sometimes, even those with "unlimited" plans are really "unlimited if we think you're just using your phone, but if we think you're tethering then we have a data cap", which makes little sense especially with today's LTE data speeds and advanced phone features leading to major data use on-device if you're so inclined.. I've read threads that claim it can be as simple as using a user agent switcher on a tethered device (ie if you're using a desktop browser user agent, they assume you're tethering and count it against you), but it would be nice if there was some way to disable tether checking all together. However, this may again be something that varies between carriers. ROMs like BenzoRom (built on CM12.1) for instance specifically notes that it Disables Tether Checking somehow, as does EuphoriaOS (AOSP, I think), so I am guessing there is some ROM-side fix that can be applied, if it doesn't already exist in CyanogenMod!

Thanks@!
[Nexus 6  Original Android Development] info[]box1:
The normal Zen kernel zip works fine for me, on CM 12.1 based ROM. Didn't have a need to use any kernel zip. Just a heads up. #courtesy
[Nexus 6  Original Android Development] npjohnson:
1. Woohoo! I picked up a call the other day and realized this!

2. Couldn't tell you

3. Uses a different tethering check, so yes, the T-Mobile popup won't get in your way.

4. Not a different t kernel persay, but a modified ramdisk. This prevents many of the kernels from Working on CM12.1. Just a couple commits need to be merged to fix it.
[Nexus 6  Original Android Development] coldconfession13:
So since people want to make long post I'm posting this again but I'm still getting this issue. Anybody else getting this?
[Nexus 6  Original Android Development] githyanki:
This morning after my alarm went off and I swiped it to sleep for 10 min, a game that I was playing right before I went to bed came on. I couldn't get menu/navigation bars to come in by swiping from the sides. I turned screen off and went back to sleep for my 10 extra minutes. Of course it was 5 AM, and I wasn't fully awake yet...
[Nexus 6  Original Android Development] scoobaspeaz:
There have been significant changes in the base code over the past week. I have not seen this happen on my device at all. It runs really great on it.

Some questions for you though. Did you move to this rom from the unofficial one? If so did you do a fresh install or dirty flash to this? Also when was the last time you did a fresh install regardless of your path to this rom? I ask because I had to fresh install a few days ago so some things would work properly. One of the fun things about using nightlies is you are at risk for having to go full fresh install from time to time.
[Nexus 6  Original Android Development] coldconfession13:
I've been installing from cyangenmod since its been official. But I did a factory reset and fresh install on 5/13.
[Nexus 6  Original Android Development] scoobaspeaz:
Try doing another one for this latest one. If you notice they merged a lot from R1 to R2 then from R2 to R3. I really do not have any of these issues you are having so I am hoping this does help you.
[Nexus 6  Original Android Development] seangeezy12:
If only voLTE worked *sigh*
[Nexus 6  Original Android Development] RanceJustice:
Rejoice, for WiFi Calling has arrived and its name is "5.1.1 LYZ28E"! https://support.t-mobile.com/docs/DOC-18109 ! Hope to see the CM devs start building on it ASAP! For those of us who have been waiting for VoLTE, WiFi Calling, and HD Voice codec, this is a major win! Now if I could only know for sure that CM disables tether checking/detection hehe! I'm sure it will take a little while to propagate, but enjoy when the new build arrives!
[Nexus 6  Original Android Development] coldconfession13:
Volte does work u just have to toggle the setting upon reboot.
[Nexus 6  Original Android Development] coldconfession13:
Still getting the screen issue on todays nightly. Seems to do it at times not all the time when the screen should shut off but gets stuck but thinks its off.

*edit*

As I'm eating breakfast I have my phone in front of me and I'm seeing my screen for third time turn itself on. I'm sure it's going to keep doing that. And now a fourth.
[Nexus 6  Original Android Development] RanceJustice:
Here's the link to the newest OTA for the WiFi Calling update! The T-Mobile version has been uploaded - http://xdaforums.com/nexus-6/general/ref-nexus-6-stock-ota-urls-t2906493 - the one for everyone else will be coming soon, I expect.

Oh, with regards to VoLTE. In order to check if VoLTE is working (on Stock, AOSP, or CM), you need to see the "LTE" label stay on during calls, is that correct? If the thing drops down to "H" instead, when you had LTE prior to callings, then you're not using VoLTE? Its strange. I flashed back to stock 5.1 (LMY47M) and made a call, noting that as soon as I did so it dropped down to H from LTE.. So maybe soemthing else is going on?
[Nexus 6  Original Android Development] dean_fx:
Just got my N6 yesterday. Any major bugs in the N6 CM12 builds I should be aware of?
[Nexus 6  Original Android Development] xtzz:
Sort of, but are slowly getting resolved.

This has been a particularly disturbing one (for me at least) - no notifications for new emails with the e-mail app. Hopefully it is getting fixed soon:
[Nexus 6  Original Android Development] dean_fx:
Gotcha. Thanks for the reply.
[Nexus 6  Original Android Development] ibraheeemz:
any idea if CM will add Gestures anywhere? or any other ROM having it? New to Nexus 6, did some searching, can't find much useful info, thanks for helping guys,
[Nexus 6  Original Android Development] AlxMAX:
I have a question. I'm building the firmware and I see lots of target thumb C++ messages. Why is it compiling in thumb mode? Why not arm mode? Or even armv7? Nexus 6 has a SoC which is near cortex A15 after all.
[Nexus 6  Original Android Development] knirirr:
I've since tried a factory reset and flash without using Titanium Backup and the crash still occurs after letting the Play Store restore apps, so it's not TB.
[Nexus 6  Original Android Development] dbrickg:
Wow! How weird! The only thing I can think of then, is that one of the apps (or some combination of apps) must be causing the crash. I suppose there's some remote chance that it could just be a hardware problem. But, if it's some app, what a pain. You'll have to reinstall apps, one at a time, and then test after each one... argh... Totally messy! Anyway, best of luck with it. Let us all know how it's going
[Nexus 6  Original Android Development] dbrickg:
MMS and cell data again?

Is anybody else having particularly bad cellular data and/or MMS problems? It's hard to tell, since it seems to be pretty bad even at the best of times, but I think the last 2 or 3 nightly's have been worse than usual.
[Nexus 6  Original Android Development] tembares:
Data is not an issue. For me the battery drains faster than before. But maybe it is WhatsApp that I have installed a few days ago.
[Nexus 6  Original Android Development] whojabacod:
cm-13-20151022.095132-JBL-shamu.zip
[Nexus 6  Original Android Development] criminalzen:
well how is it? I could never get marshmallow to build..
[Nexus 6  Original Android Development] whojabacod:
actually really fluid, its void of boot ani and theme manager however its much more fluid to the touch and the ui much less yellow tinged dark look to it ...

Tmo WiFi calling works
[Nexus 6  Original Android Development] :
Any link and additional info please? Sounds good!

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

LG G watch R
[Nexus 6  Original Android Development] Khizar:
http://xdaforums.com/nexus-6/development/rom-cyanogenmod-13-0-android-6-0-t3231497
[Nexus 6  Original Android Development] AlxMAX:
It's not clear from the albinoman messages that one needs to flash the radio, hboot and all the other stuff that Google provided in the factory images of Android 6. Have you flashed them?
[Nexus 6  Original Android Development] dbrickg:
I assume you're asking about the cm13 rom? There's some discussion of that in the cm13 thread. I asked the same question there and got mixed responses.
[Nexus 6  Original Android Development] dbrickg:
all quiet on the western front

not much happening here lately. guess that's a good sign
[Nexus 6  Original Android Development] k1l:
tested a cm13 (which didnt work out). then had some issues with reverting to my recovery backup.

after installing the latest cm12.1 from 20151110/11 i dont had a keyboard, trebuchet or camera. is that a known issue on the cm repo?
[Nexus 6  Original Android Development] dbrickg:
Hmm, no, I've not heard anything about issues like you describe with cm12.1. I've installed the alpha cm13 rom (from 11/10, which actually works pretty well; see my post in that forum), and then restored to my cm12 backup, which was, I think, the 2015-11-06 (or thereabouts) nightly, then flashed yesterday's (11/11) nightly, and all's working well. Which cm13 rom did you flash?
[Nexus 6  Original Android Development] :
Any advice against trying the alpha? Some bugs / issue / shortcomings that might prevent me from doing so? :) I read that thread and apart some setup issues it seems it's missing many features of cm 12.1 of course,but i didn't exactly catch what's there and what is not!

Also, do you think that the future official nightlies will be dirty flashable over this? I'm thinking about upgrading, but hell!, setting the phone up from scratch once is way more than enough for me! I really hate doing it, so boring and time consuming (and a little anxiety - inducing too: "did I forget something?").

Thank you for your help!

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

LG G watch R
[Nexus 6  Original Android Development] k1l:
just had a friend telling me the same from recent 12.1 on another device.

on get.cm there are a lot 404 errors now for the builds.
[Nexus 6  Original Android Development] dbrickg:
Probably best to discuss the alpha cm13 rom in its own thread. But no, I didn't find any huge problems with it. I'd have kept it as my daily driver, except for a couple of minor problems (chromecast would crash the phone, for instance).

And, assuming you mean, can cm12.1 roms be dirty flashed over cm13, I'd guess that you can't. There are some pretty significant differences. I always keep a backup of my most recent cm12.1 and one of cm13, so I can restore to whichever cm version I'm interested in, and then flash new roms from there.

PS: just realized another interpretation of your "future official nightlies will be dirty flashable over this" might be "future official cm13.0 nightlies". If that's the case, I have no idea. Especially since it looks like it'll be awhile before any official cm13 nightlies start coming out. We'll just have to wait and see. But in general, I always try first to dirty flash, and if that doesn't work, then do a clean flash. And, yes, I agree, restoring everything after a clean flash is a pain in the butt

---------- Post added at 08:07 AM ---------- Previous post was at 08:00 AM ----------

Hmm, do you mean 404 web errors? Do you mean that you can't download the recent 12.1 nightlies? Or that once you install the nightly you get a lot of 404 errors with the browser on that nightly?

I've got the cm-12.1-20151111-NIGHTLY-shamu.zip installed on my Verizon Nexus 6, with the open_gapps-arm-5.1-nano-20151111.zip, and I'm not experiencing any problems. I also flashed the shamu-mra58k-bootloader.zip and shamu-mra58k-radio.zip when I was experimenting with the cm-13.0 alpha, and it's my understanding that those are independent of and persist across cm versions, but I don't think that should make any difference to the kind of errors your friend is talking about
[Nexus 6  Original Android Development] k1l:
with 404 i meant the get.cm links to the shamu builds.

and after reflashing a clean cm12.1 and then reflashing my data i didnt had trebuchet, aosp keyboard. and since my friend said the same from the other device i was curious what is wrong with the cm12.1 builds. i mean having the google-now launcher and having to use voice-search on chrome to get a trebuchet download. never had to do that.

i now flashed the cm12.1 20151111 with the cmupdater in the system settings and it still got no aosp keyboard.
[Nexus 6  Original Android Development] dbrickg:
Hmm, weird. I've got that same cm12.1, 2015-11-11, and I'm not having any problems. It downloaded just fine, using chrome. But I got it from download.cyanogenmod.org. And my keyboard and launcher are working just fine. But I use Hackers Keyboard and Nova launcher, so that may explain why I'm not having any problems. Is anyone else who's using recent cm12.1 nightlies having problems with the stock keyboard and launcher?
[Nexus 6  Original Android Development] akanealw:
I use CM Downloader for all of my nightly updates along with OpenGapps and have had no issues with the keyboard. Even when dirty flashing I usually nandroid backup, wipe system, dalvik, cache, then flash cm and gapps. I've had very few issues in the 6+ months I've used this method. Also the CM Downloader app does an md5 check when the download is done. I can't recommend it enough.

https://play.google.com/store/apps/details?id=com.paolinoalessandro.cmromdownloader
[Nexus 6  Original Android Development] NOSTALGIA:
no issues with keyboard as well on the latest nightly

downloaded my builds through

cmxlog
[Nexus 6  Original Android Development] bmakk2055:
Are these build still stable? It's been a while since I flashed .
[Nexus 6  Original Android Development] dbrickg:
Yes, they're very stable
[Nexus 6  Original Android Development] bmakk2055:
Any new features?
[Nexus 6  Original Android Development] dbrickg:
I guess that depends on what you're comparing it to.
[Nexus 6  Original Android Development] NOSTALGIA:
cm12.1 nightlies all the way..super customized. with hydra kernel.loving it
[Nexus 6  Original Android Development] metallbloodxox:
Since shamu did not get the 11/17/15 cm12.1 snapshot, is it safe to flash the ones after that date like the 11/21 nightly??? or can anybody recommend any latest nightly that has no issues/mayor bugs. I need this phone a daily driver.

Q? Is it planned a last realise (snapshot cm12.1) for shamu?

Note. I have flashed the latest snapshot on my g2 d801 and its running like a champ very smooth and battery awesome and I would like to see the same in my moto nexus 6 abyy response or advice will be very appreciated. Thank in advance.
[Nexus 6  Original Android Development] boog:
I just loaded the 11/21 on mine and it appears to be solid! Haven't seen any issues as of yet.
[Nexus 6  Original Android Development] NOSTALGIA:
nice.. im still on the 11/14 nigthlies. and im still loving this build paired with hydra kernel. getting most of the time 3-5 hours sot on a 24 hour usage. with moxed data and wifi.. amazing. and sleep is also amazing.. no issue. also with some more murdered customizations with xposed
[Nexus 6  Original Android Development] dbrickg:
cm13.0 nightlies!!!

in case anyone hasn't already found it, there's a new cm13.0 nightly thread:

http://xdaforums.com/nexus-6/development/rom-cyanogenmod-13-0-nightlies-t3254987

it's still pretty early stages, but it's making fast progress...
[Nexus 6  Original Android Development] antmunny:
whoa...hammerhead is now getting official cm13 nightlies. hope shamu is next
[Nexus 6  Original Android Development] marshall_634:
Question. How can I get rid of the pics in the contact and have the stock letters.

Sent from my Nexus 6
[Nexus 6  Original Android Development] antmunny:
looks like Official CM13 starts tomorrow!!
[Nexus 6  Original Android Development] NOSTALGIA:
its already listed on cmxlog
[Nexus 6  Original Android Development] dlbarron:
Got it, flashed it, looking good.