yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] AndyYan:
Might not be the cause of the problem, but did you exclude CMSetupWizard when installing OpenGAPPS?

Sent from Google Nexus 6P @ CM13

[WARNING: XDA One have not implemented "mark forum as read" - do not use]
[Nexus 6P General] andyc2d:
OK I'll give that a try, thank you.

Edit: The permissions were set correctly but it wasn't set as the default dialer. I fixed that and it works perfectly, thank you!

No I just installed it as usual, I don't know how to do that. Is that something you can do with the aroma installer?

Edit: I figured it out, just need to create the config file for Open GApps. Turns out I didn't need to though, thanks for the input anyway.
[Nexus 6P General] mamv:
[MENTION=1890382]sam3000[/MENTION] Still having 3 or 4 random reboots per day. Are you still having the same problem?
[Nexus 6P General] kogone:
decided to not restore apps from titanium and reinstall fresh. random reboots have gone away for me on 0519
[Nexus 6P General] kogone:
been building cm from source with dex2oat and JustArchi's ArchiDroid Optimizations: link.

posting my builds here: https://goo.gl/8vQHDP
[Nexus 6P General] sam3000:
Yes.

Potential fixes here:

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

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

http://review.cyanogenmod.org/#/c/146681/
[Nexus 6P General] winxuser:
Gello browser for me fc on the new build that just came out
[Nexus 6P General] razorloves:
HEADS UP: The backuptool script in cm that does the backup & restore of gapps for each flash, is broken in 25 may nightly, so you should avoid it.

https://jira.cyanogenmod.org/browse/NIGHTLIES-3030

EDIT: a fix is already in work http://review.cyanogenmod.org/#/c/146714/
[Nexus 6P General] winxuser:
Yeah I noticed that when it booted I had no google apps, don't dirty flash gapps again fc everywhere. Just another heads up
[Nexus 6P General] sam3000:
Did you flash the latest gapps or the same version as you installed when you first flashed cm in the first place ? I would think that reflashing the original version should be okay.
[Nexus 6P General] winxuser:
Reflashed the same one.
[Nexus 6P General] sam3000:
I'm sure too late now but also:

https://wiki.cyanogenmod.org/w/User:PsychoI3oy#Fixing_CyanogenMod_13.0_gapps_crashes
[Nexus 6P General] razorloves:
bug report for gello app crashing https://jira.cyanogenmod.org/browse/NIGHTLIES-3034

EDIT: Gello app is fixed in 28 may nightly
[Nexus 6P General] turbo1781:
Is the dt2w feature in the Rom included, or only with Costum Kernel?
[Nexus 6P General] razorloves:
Included
[Nexus 6P General] mrjoeyloke:
Can anyone confirm that the Bluetooth is working on these nightlies? I know it's not on the latest snapshot.
[Nexus 6P General] ce_rob:
anyone else have issues with slow data when downloading anything or when using certain apps? though speedtest has always shown decent speeds, i've always noticed that downloading files or using apps like instagram or snapchat seem to take awhile to upload/download media. i ran an experiment this morning and have absolutely no idea wtf is going on.

speedtest results:

right before i ran the speedtest above, here's my download speed for a video - a MERE 178 KB/s:

and here's me having connected to wifi as soon as i got into the office, showing it's not a server issue where the above file is hosted:

should i enable/disable something? i've had to mess with disabling optimizing certain apps for battery consumption or whatever for random issues (notifications, not sync'ing, etc.) - could down-speeds be similarly affected with a random setting? FYI my 'bars'/reception show as full, on LTE, and speedtest results are quite high. i'm absolutely dumbfounded and because i'm currently taking an uber to/from the office (30mi each way), it's extremely frustrating as i'm on my phone the entire time.
[Nexus 6P General] redbullman:
Bluetooth is still broken sadly in 2 June nightly. Seems like it will never be fixed :( Its been broken like forever!!
[Nexus 6P General] kogone:
the thing that affects a download speed the most is the server that is serving the data requested.. you proved that the issue is not your wifi chip by running speedtest. there are so many other things that could be affecting those speeds. good luck!

this could be beneficial bluetooth fix
[Nexus 6P General] ce_rob:
the speedtest was run OFF of wifi, it was run on my data/LTE and i got those high speeds - but i was still downloading at 178 KB/s. i then proved that it WASN'T the server itself because the down-speeds increased when i DID enable wifi.

that says either speedtest is reporting VERY inaccurate speeds or there's a setting/config that's preventing certain processes or apps from utilizing the full data speed.
[Nexus 6P General] kogone:
!!! i thought you successfully ran speedtest on the wifi! oh well
[Nexus 6P General] turbo1781:
How the Bluetooth connection works? Are there interruptions or distortions
[Nexus 6P General] Smallsmx3:
BT will get fixed when it gets fixed. By then Android N will drop and will break again and all of the development will start over and all the features that you need you'll be waiting for. All the while with broken features. The problem with CM, by the time builds are stable enough to use as daily drivers I've either moved to my next device. Which is yearly. Or a new version has dropped and all development starts over. You have a Nexus. There are tons of AOSP Roms with all the same features all completely stable with working BT
[Nexus 6P General] snakecharmer23:
Sadly, this is true. CM has never been something for the average consumer but great for the people who enjoy development and a perfect fix for the hardcore flashers. In the past I was a dedicated user because of the built-in support to limit permissions in apps. Built-in root was good too. I always put up with the minor annoyances and lack of decent bluetooth support. Now, with the 6P, I find bare bones stock more than adequate. The permissions support built into Marshmallow isn't as good as what CM offered but it gets the job done. I still come to this thread and monitor changelogs out of habit, hoping one day to see that a truly stable build will someday be released.
[Nexus 6P General] Smallsmx3:
Well CM is good to get an aosp like experience on a device that had no hope for an aosp ROM. I too was a dedicated user. I still like to flash custom ROMs and you would think that since all the binaries are available for Nexus phones CM would be a flawless experience it's quite the opposite. It's generally the buggiest for our devices. Its sad really, I feel like their implementation of features and the layout of the ROM is nothing but of high quality
[Nexus 6P General] seangeezy12:
How is this ROM? I am a fan of CM! Everything works I presume?
[Nexus 6P General] farfromovin:
My only previous Nexus was the Galaxy Nexus and that device was STELLAR with CM. I think I ran nightlies for 6 months straight without a single hiccup. It was great!
[Nexus 6P General] Smallsmx3:
That's when CM was still pure AOSP.... It's a CAF ROM now.... ever since the Nexus 4 it's been rough
[Nexus 6P General] State.of.mind:
Faster install

Is there a way to flash Nightlies without having to re flash SU and Xposed?
[Nexus 6P General] redbullman:
Any ideas why the latest nightlies state mob30m when the nexus 6p should be MTC19V? mob30m is for all nexus devices except the 5x and 6p. I wondered why flashing the latest vendor doesn't fix the error on boot up (there is a problem with your device) as the nightlife state the wrong build number!
[Nexus 6P General] redbullman:
Anyone know if there is being fixed as its a fairly basic error!
[Nexus 6P General] razorloves:
Nothing needs to be fixed.

Cm keeps its code base up to date with newest aosp. Which currently is	android-6.0.1_r46 MOB30M.

Device trees are separate and often at different levels.

You can see here https://source.android.com/source/build-numbers.html#source-code-tags-and-builds

So, in cm you see the code base is currently at MOB30M.

Reflected here: https://github.com/CyanogenMod/android_build/blob/cm-13.0/core/build_id.mk#L21

But for the nexus 6p device, you see it's at MTC19T.

Reflected here: https://github.com/CyanogenMod/android_device_huawei_angler/blob/cm-13.0/cm.mk#L25

Google just released MTC19V for the nexus 6p a couple days ago, so cm will be updating to it soon, as usual.

Changes are currently under review.

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

and

https://github.com/TheMuppets/proprietary_vendor_huawei/pull/31
[Nexus 6P General] redbullman:
Ok that makes sense thanks for explaining. Seems to be longer than normal this month.
[Nexus 6P General] razorloves:
Heads-up: All the MTC19V updates for the nexus 6p have been merged into cm. So, starting with the Jun 10th nightly you will need the new vendor.img from the MTC19V factory image. I have extracted the vendor.img from the factory image and put a link below if you want it:

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

I've also hash checked the radio and bootloader in this new factory image (MTC19V) and they're the same as the ones in the last few updates, so no need to update them. (bootloader v3.51 / baseband v3.61).

Side note: Some changes to have the weather on the lockscreen have just been merged, so that will be in the Jun 10th nightly also. :good:
[Nexus 6P General] LiquidSolstice:
Anyone know if the BT stuttering has been resolved on the latest?
[Nexus 6P General] ccblox:
Just flashed. Still getting terrible stutter for about 5-6 seconds after waking the screen.

francoKernel r21 is my only modification.

Edit: I had also made sure to flash the latest vendor file, MTC19V, from a few posts back.
[Nexus 6P General] XZQ't:
I'm too a die hard CM user since Nexus One. Just bought 6P and flash CM few days ago, I also frustrated by the lack of stable ROM. If bluetooth on CM of Samsung device is broken I would understand, but this is NEXUS.

At the moment I'm back on stock. And not sure if I will ever wanted to give CM a try again.
[Nexus 6P General] hi2u2:
Bunch of BT commits got merged for June 11 nightly. Can't tell if they address, or start to address the stuttering issue though. Anybody with more expertise know?

https://www.cmxlog.com/13/angler/
[Nexus 6P General] ccblox:
I flashed 20160611, and have noticed no improvement. Still 5-6 seconds of stutter after unlocking.
[Nexus 6P General] Ok_Kaleidoscope5109:
Is this a documented issue in JIRA? If not I would suggest doing so.
[Nexus 6P General] Ulver:
I can't believe there are still Bluetooth issues with CM on this phone.
[Nexus 6P General] Jammol:
There's still bluetooth issues on CM Note 4. I really hope the 6P gets sorted out. I would really like to just use CM dualboot with stock and call it good.
[Nexus 6P General] Mroid:
How is the camera in CM13? Does it at least have all the features of a stock 6P (120/240fps, 4k, HDR etc.?)
[Nexus 6P General] AndyYan:
You need Google Camera for those.

Sent from Google Nexus 6P @ CM13
[Nexus 6P General] locolbd:
Yep. CM Team is on this like white on rice.
[Nexus 6P General] c_86:
guys i need help

big time

not sure what to do... im not new to this at all

i just got a n6p and unlocked bootloader, etc etc, flash the latest cm13 and refuses to boot... i am unable to get USB debugging on as i cannot boot it so I cannot flash a stock factory image...

how the hell can I fix this?
[Nexus 6P General] kenbrownstone:
Go into recovery....You flashed twrp right?
[Nexus 6P General] c_86:
yes i can get into recovery fine... i have tried flashing a factory rom (zip) stuck on google logo

i was stupid and didnt do a back up
[Nexus 6P General] kenbrownstone:
What other zips do you have ?

---------- Post added at 11:10 PM ---------- Previous post was at 11:10 PM ----------

Hold on
[Nexus 6P General] c_86:
i have the latest CM, gapps, the 08M vendor zip and a factory image zip...
[Nexus 6P General] kenbrownstone:
Go find wugs tool...its easy ..Check in nexus 6 forum...Just select 6p in menu ...or hook up to computer and flash with adb in bootloader mode...wugs is the best way

---------- Post added at 11:15 PM ---------- Previous post was at 11:13 PM ----------

Wugs is in the np forum now sorry
[Nexus 6P General] c_86:
ok, but how can i access adb is debugging isnt selected? thats my whole issue... adb isnt detecting the device when in bootloader... i have tried doing to the flash all etc with the direct google image
[Nexus 6P General] kenbrownstone:
http://xdaforums.com/nexus-6p/development/toolkit-wugs-nexus-root-toolkit-v2-1-0-t3258493?nocache=1

---------- Post added at 11:18 PM ---------- Previous post was at 11:17 PM ----------

Ask in the help thread..There is away somehow...You might can even transfer another zip from your computer to your phone

---------- Post added at 11:19 PM ---------- Previous post was at 11:18 PM ----------

By the way I couldnt get any cm13 build to flash either
[Nexus 6P General] tdamocles:
Fastboot flash works in bootloader, not adb. Fastboot devices......Like brownstone said, find wugs and use it. When you sort it out reflash with the latest stock build(m build). Then flash cm13 and do not flash the m vendor zip. It will bootloop you. Sounds like you flashed the vendor zip after flashing cm13. A nandroid backup probably would have failed also-happened to me. Just use wugs, it'll get you back quickly.
[Nexus 6P General] c_86:
ok, so do i do that to flash a factory image?

whenever i use the flash all that comes with the google image it never works....
[Nexus 6P General] kenbrownstone:
Hold on I will try to find the directions for you...Sorry I worded it wrong but that's what I meant was fastboot mode in the bootloader.
[Nexus 6P General] c_86:
Thanks. I would love to get cm running but at this point I just want a phone I can use lol
[Nexus 6P General] kenbrownstone:
Try wugs tool kit...it will work..just select bootloop in the options and it will download the right files for you ..just follow step by step .

---------- Post added at 11:41 PM ---------- Previous post was at 11:40 PM ----------

It will even reroot after it restores stock..Just don't lock the bootloader

---------- Post added at 11:41 PM ---------- Previous post was at 11:41 PM ----------

It installs twrp also
[Nexus 6P General] c_86:
I tried wugs and it wouldn't go. Said I needed to enable USB debugging
[Nexus 6P General] kenbrownstone:
Dam...sorry dude ..fastboot mode is the way to go...ask around for smarter people I don't want to mess u up..But I know it works and your phone isn't fcked ..Just find the right person or thread to show you...
[Nexus 6P General] tdamocles:
Sounds like you're trying wugs in twrp. Put it in bootloader mode by holding power and volume down at the same time and when the screen turns on it should be in the bootloader. Then use wugs.
[Nexus 6P General] kenbrownstone:
I thought something was wrong cause its supposed to work in boot loop
[Nexus 6P General] tdamocles:
Easier from bootloader.
[Nexus 6P General] aznriceballman:
Has anyone noticed when you first boot your phone on 1128, there's this random static sound the speakers make? Also, systemui still crashes when you try to set up a pin/fingerprint during setup?
[Nexus 6P General] koupa:
I confirm the BT problem with the latest version. I have a Sony SBH 52 and it's impossible to listen music. The problem is there since January when i first flashed the ROM. Of course on N preview everything is fine.
[Nexus 6P General] Smallsmx3:
It's fine on everything other than cm
[Nexus 6P General] hi2u2:
https://jira.cyanogenmod.org/browse/CYAN-7569

Been reported a while ago, but doesn't look like there's any progress. There's logs already attached and the issue should be easy to reproduce.
[Nexus 6P General] Smallsmx3:
I saw a post somewhere that CM knows where the problem lies and what's causing it. I think they said it would be fixed but there's no timetable. I really wish the strategy would be to keep the functions of devices working properly. Or at least fix it within a build or two. The BT issues are more of a CAF problem than an Android one according to the slim team which bases there ROM on Caf now. I know that's a difficult feat considering the amount of devices maintained. I've owned almost all nexuses and ever since CM went Caf I'm pretty sure BT has been borked

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

On another note does Google hotword work with the screen off? I know it was being worked on and I think merged but I don't really see any chatter about CM for the 6p
[Nexus 6P General] hi2u2:
Yes it works.
[Nexus 6P General] Smallsmx3:
Hey thanks! That's good to hear. Any idea if the BT bug is fixed yet. Been searching but I don't see anything recent.
[Nexus 6P General] hi2u2:
No idea.

What you told us earlier about CAF and CM being aware of the cause of the BT issue was news to me so you probably know just as much as most of us.
[Nexus 6P General] Smallsmx3:
I read it in a CM thread I think. Maybe on G+. I don't even remember if the guy who said it was part of the CM team. So who knows how valid that is. But one of the Slim devs said it was ACaf problem because slim suffers the same issue
[Nexus 6P General] Ok_Kaleidoscope5109:
Anyone have issues with phone calls? Occasionally I'll get a call I can't pick up (it just keeps ringing) or if I make a call sometimes it gets stuck at Dialing. I need to reboot.

I'm on the 27-JUN nightly but I've seen this for a few weeks now. Using latest Open Gapps as well and Google Dialer.
[Nexus 6P General] fhek:
I've also had this issue. It was only occurring for one number.

I couldn't receive a call from A. I would swipe to answer and it would not pickup, I could keep swiping and nothing. I couldn't call A, it would sit at dialing.

I tried calling B and it worked fine. B called me fine.

A and B had different area codes(idk if correlation)

I got no logs sorry, 5min after fresh install and late at night.

If it happens again I'll upload a catlog
[Nexus 6P General] magn3to3:
Hi Guys, sorry, just wanted to ask....is it okay if I dirty flash the Nightly Build as when i'm on Snapshot build of CM 13 on Nexus 6P??
[Nexus 6P General] hi2u2:
Warning: 7/3 nightly breaks mobile data, on AT&T at least.

On a positive note though, this may be the one BT users have been waiting for. I've only tested very briefly but it seems the stuttering upon screen on while playing music over BT may finally be fixed! Wasn't able to test more since I flashed back to previous due to mobile data not working.
[Nexus 6P General] razorloves:
I'm having data issues on att too, on 3 jul nightly. When i leave wifi area and phone auto switches to cellular data, it doesn't connect sometimes. I have to toggle airplane mode to get it to connect. But once it's connected it works good, like normal. Probably from all the telephony commits steve merged yesterday.

But bluetooth still stutters on me for a few seconds when screen is turned on
[Nexus 6P General] Smallsmx3:
I used slim gapps because it was recommended and didn't cause this issue.
[Nexus 6P General] :
Anyone on latest build? What are the bugs if any? BT stuttering issues? anything else to be aware of?
[Nexus 6P General] be_vigilant:
I am on the 5th and BT still stutters in my car. I do not even need to turn the screen on. Random stutters ever minute or so.
[Nexus 6P General] redbullman:
Just installed latest nightly 8/7/15 and noticed Wi-Fi doesn't work. It was ok on yesterday's nightly.
[Nexus 6P General] razorloves:
same here. looks like it's from the kernel update we got in this nightly.

https://github.com/CyanogenMod/andr...mmit/43023fa2770d7856a48f70af36bce62a3f92478a

EDIT: Figured out the fix. Flash the new vendor.img from the MTC19X update that came out 2 days ago. You can get it from the factory image or use the one that i already extracted from it, here.

Like usual, you can flash it using fastboot or using twrp.
[Nexus 6P General] redbullman:
As stated in the other cm 6p thread, if you flash the July vendor image it fixes wifi.
[Nexus 6P General] razorloves:
Ok, cm has finished updating the 6p to MTC19X today, so you will need the MTC19X vendor.img starting with next nightly (9 July).

You can extract it from the factory image or use the one that I already extracted here.

You can flash it using twrp or fastboot.

The MTC19X update from google has a new bootloader, but same radio. You can extract them from the factory image or use the ones I already extracted:

bootloader 03.52

radio 03.61

Those cannot be flashed with twrp. Only with fastboot.
[Nexus 6P General] turbo1781:
Any news about the stability of the nightly builds ? How work for example Bluetooth, random reboots ? CM was always my favorite ROM because everything gives me what I need .
[Nexus 6P General] hi2u2:
Bluetooth issues and random reboots are still both present in the latest nightly.
[Nexus 6P General] H00pyFr00d:
I really don't understand why you lot are using CM and putting up with these bugs. Is it worth it for a device that runs like a dream out of the box and works really well with Xposed and Layers?
[Nexus 6P General] turbo1781:
What layers do you use? With stock rom, but I don't like xposed.
[Nexus 6P General] Smallsmx3:
I'm wondering the same thing. Years ago I used CM and it was great. CM7 has to be my all time favorite ROM but it's never stable now. I just wish CM would go away from the CAF base and back to the pure AOSP. I used CM on my 6p a couple of days ago and the ROM and it's features are amazing and very sleek looking. The performance was sub par at best. Made me feel like i was using a galaxy S with ask the lag and choppiness.
[Nexus 6P General] suspended.brooklyn:
Searching for WiFi

I installed the latest CM13 nightly along with the recommended GAPPS package on my Nexus 6p as per the given instructions.

All went well until the phone booted. Phone constantly searching for Wifi with 0 results even though. My other phones are connected to my home wifi with no problems. Cannot even add Wifi manually.

I even did a clean install 2 more times (with no luck) hoping the issue will resolve itself. Still keeps searching for Wifi
[Nexus 6P General] razorloves:
u need the newest vendor.img.

http://xdaforums.com/showpost.php?p=67663036&postcount=806
[Nexus 6P General] suspended.brooklyn:
It worked. Thanks a million :)
[Nexus 6P General] Mroid:
Okay so I updated from an early June build to the 12th July build and the Wifi doesn't work, so I assume doing the above will fix this...

I would assume this would also explain why I'm getting 'Android System - Internal Device Problem' (or similar ) message at startup, by not updating vendor.img?
[Nexus 6P General] razorloves:
Yep. Every month google releases a new update for all nexus devices. So, you have to flash the new vendor.img from that update (assuming you're wanting to update cm rom).

Also, in that update from google, is the bootloader and radio. Those don't change every month like the vendor.img, so you just have to flash those whenever they update to a new version.
[Nexus 6P General] Mroid:
Excellent, just downloaded the factory image from Google and got the vendor/radio/bootloader files and flashed/installed myself as required. Warning message is gone and Wifi working now.

Would be good if this was mentioned in the OP...
[Nexus 6P General] Ok_Kaleidoscope5109:
I don't think CM is any more buggy than stock. The problem is when you start combining rooted apps and Xposed addons, it becomes more unstable.

I've personally noted that I have issues with lockups and soft reboots and inability to call sometimes with GravityBox. I turned it off for a week and those problems went away. Turned it back on this past Monday and I couldn't make a call yesterday.
[Nexus 6P General] MaxNXS:
Really?? Those are pretty bold and, IMHO, inaccurate statements. You clearly are not using BT audio on CM13, since it has been completely broken for months and it doesn't look like it's getting fixed. Xposed and GB are pretty mature and well proven by now and they work perfectly fine with no major bugs. FYI GB, as mentioned by the author is not meant to be used with CM or any custom rom:
[Nexus 6P General] :
when was the last time you checked BT audio?