yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] dlbarron:
Forgive me if I am out of touch, but has anyone stepped up to be the maintainer for the N6? I understood the lack was why we had not gotten Gello and some other new features.
[Nexus 6 Android Development] Elektroschmock:
No there is no new maintainer, but people like razorloves, ciwrl, dcd an me are keeping it alive.
[Nexus 6 Android Development] dlbarron:
Thank God. I've only had my N6 for a year, I'm not ready to move to another new phone.
[Nexus 6 Android Development] :
What're the new features other devices have other than Gello?
[Nexus 6 Android Development] julesism:
Looking forward to a working snapshot. Hopefully it will be stable enough to stick around. I started on CM back in the day on my Nexus One and pretty much stayed on it over the years/devices until a few months ago. Wish the N6 got more CM love :/
[Nexus 6 Android Development] dlbarron:
The new camera app, I believe it's Snap.
[Nexus 6 Android Development] dbrickg:
The 8/18 nightly is fixed! No more bootloops!
[Nexus 6 Android Development] :
why we on shamu dont have gello browser ??
[Nexus 6 Android Development] bigchrizzieboy:
There's also a new snapshot (8/18)

cm-13.0-20160818-SNAPSHOT-ZNH5YAO0HC-shamu.zip (448.22 MB)

cm-13.0-20160818-NIGHTLY-shamu.zip (458.39 MB)

https://download.cyanogenmod.org/?device=shamu
[Nexus 6 Android Development] Elektroschmock:
Gello will be included in the next nightly.

http://review.cyanogenmod.org/#/c/156830/
[Nexus 6 Android Development] :
thats great
[Nexus 6 Android Development] dbrickg:
Just installed the 8/19 nightly, and in Settings / Apps / Browser, it now says "Browser: version 42.0.2311.1185 (747cb06) org.cyanogenmod.gello browser"
[Nexus 6 Android Development] smithinsundar:
How is running ?
[Nexus 6 Android Development] dbrickg:
I haven't had a chance to use it much. But it started up just fine :)
[Nexus 6 Android Development] usuppue:
someone has the iusse of black screen while using the app?
[Nexus 6 Android Development] Dead-neM:
Good so far. No big problem noticed except some weird animation glitch
[Nexus 6 Android Development] LS1_01:
Looks like an 8/20 snapshot was just posted.
[Nexus 6 Android Development] :
i would like to flash the snapshot but i dont how will be the update process anyone have idea

---------- Post added at 09:18 PM ---------- Previous post was at 08:35 PM ----------

i already flashed it with stock gapps and everything looks good
[Nexus 6 Android Development] LS1_01:
Working well for me as well now after I flashed it on top of the 8/18 snapshot.
[Nexus 6 Android Development] :
is there any news how the update will be like weekly or monthly beacause last snapshot was in april lol
[Nexus 6 Android Development] LS1_01:
Your guess is as good as mine but I wouldn't hold my breath...it will probably be at least another 2+ months if I had to guess!
[Nexus 6 Android Development] duttyend:
That's awesome, thanks a lot, it's working great!!!

Could you also enable SnapCamera compiling for shamu?
[Nexus 6 Android Development] razorloves:
see comments http://review.cyanogenmod.org/127251
[Nexus 6 Android Development] Igotsanevo4g:
8/21 nightly running great. Installed on a fresh wipe + Franco kernel. Loving it no issues so far.

Gello browser is FAST
[Nexus 6 Android Development] homer667:
You can extract the apk from other build like the Nexus 7 (2013) like I did.

It works exept for the panorama function.

And as a replacement for gello I'm using the tugabrowser.

https://www.androidfilehost.com/?w=search&s=Tugabrowser

The best browser so far in my eyes.
[Nexus 6 Android Development] dbrickg:
Running great for me, too! Just did a dirty install, using the stock kernel. And yes, haven't spent much time on Gello, but it seems pretty fast
[Nexus 6 Android Development] R1skNt:
I'm still on 22/5 nightly and stock kernel and it's working perfectly with no issue, does the latest has new feature or anything i should consider? or it's better to stay on what i have
[Nexus 6 Android Development] Dead-neM:
Latest? If you mean the nightly... They're build everyday so yes it can have new feature sometimes like the snap camera which will come soon or bug fix but it can also be worse so if you're good with 22/08 build stay with it, check log and flash a new one when you see something interesting in it
[Nexus 6 Android Development] dbrickg:
As Dead-neM said, if you're happy with your current version, you should probably just stick with it. The nightlies will have new features, but also new bugs. The only thing I might add is that there have undoubtedly been security fixes, so you'll want, eventually, to upgrade to a newer version. And, as always, make a backup before you upgrade, then, after you upgrade, you can always revert to the older version.
[Nexus 6 Android Development] Dead-neM:
Snap camera is coming!!!
[Nexus 6 Android Development] dbrickg:
Yay!!!
[Nexus 6 Android Development] idroid2324:
Anyone tried the latest nightly 31/08? Is snap camera working?
[Nexus 6 Android Development] dbrickg:
Yes... to both questions :)
[Nexus 6 Android Development] brianr549:
So here goes,

On a clean wipe of system/dalvik/cache and flash of CM nightly 8/31 and 9/1 gapps, my first run setup would constantly loop not allowing me to complete the first run so I could not get into the OS. So i decided to wipe and fresh install CM, go through setup, then reboot and install gapps through recovery . Reboot and first run everything is fine, so I rebooted to flashed gapps in recovery. I was immediately greeted with multiple windows of "Google Play Store has stopped" and "Unfortunately, google play services has stopped" issue as others have described in this thread. So as I am reading the threads someone mentions giving permission through settings/apps and checking box on each permissions for "Google Play services" "Google Play Store" and "Google Services Framework". Doing this was a SLOW process because I am having to dismiss the error messages and quickly navigating before the next error messages popped up a half a second later. However, completing this did fix all but one error message "Unfortunately, google play services has stopped" and it was now only popping up every 10 seconds or so, so this was a huge improvement. After taking a look at this last error (by clicking "report" on the error pop) and doing a bit of researching (google'ing) , I found that it was still a permission issue. I had checked all the buttons through settings/apps so I was not sure why still a permission issue. I did find where someone had a similar issue and issued the permission commands through ADB. This FIXED my issues and I wanted to share the commands here in hopes of helping someone else.

In CM 13 developer options make sure root access is set to "ADB only" or "Apps and ADB" depending on your preference.

From adb issue the following two commands.

adb shell pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

adb shell pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE

or if you want to run from inside CM13 from a terminal with root access you could run the following. (I did not try this but should work in theory)

pm grant com.google.android.gms android.permission.ACCESS_FINE_LOCATION

pm grant com.google.android.setupwizard android.permission.READ_PHONE_STATE
[Nexus 6 Android Development] dbrickg:
Wow! That's a LOT. Thanks for sharing your experience and the commands to fix the problem. Has anyone else had those problems? I haven't done a clean install for months, but when I did, I didn't have any problems like you're describing.... or any other problems for that matter. It all went pretty much flawlessly. Did you actually do the initial install in the order you mentioned? I think, though I'm not really sure, you're supposed to wipe dalvik after installing the nightly and gapps. Anyway, sorry it was such a problem for you. And thanks, again for sharing the solution you found.
[Nexus 6 Android Development] Dead-neM:
If you flash a nightly to an other new one you don't need to wipe cache/art and system partition. Doesn't need at all especially if you're not modify them before. Next time just flash the rom without wiping anything.

DO NOT FLASH GAPPS EVERYTIME it's also useless as a /system/addon.d script is placed to keep your gapps on a rom flash.

Also do not flash rom then boot in os without flashing gapps if you want them.

Google play service and Google play store update automatically and so they're both on system and data i think because you flash your rom and gapps after wiping system the apk part in data were messed up with the new gapps. If you flashed gapps without wiping system, gapps zip clean the apk on data and system if necessary and your phone will boot normally.

That's for the flash process you messed up thing by doing that.

Now the permissions trick is skipable by flashing rom and gapps on twrp then boot the device

If you're on a fresh install or on a not fresh install (i mean wiping /data or not) always flash gapps after Tom and then you can reboot.

I think the way you flash rom and gapps are wrong. No offence here. Just a warn. I try to explain why and if you have question or anything I'll try to explain it in a better English ^^.
[Nexus 6 Android Development] brianr549:
Thanks for your reply, your English is pretty good. I need to stress that is was a clean install. That is the reason for wiping everything. I do not flash gapps every time.
[Nexus 6 Android Development] brianr549:
If you flash a nightly to an other new one you don't need to wipe cache/art and system partition. Doesn't need at all especially if you're not modify them before. Next time just flash the rom without wiping anything. This was a clean install starting from scratch, so I wiped everything.

DO NOT FLASH GAPPS EVERYTIME it's also useless as a /system/addon.d script is placed to keep your gapps on a rom flash. I do not flash gapps everytime, see first comment

Also do not flash rom then boot in os without flashing gapps if you want them. I just did flash gapps after installing and booting CM and explained how to fix issues after doing so. It was my only choice.

Google play service and Google play store update automatically and so they're both on system and data i think because you flash your rom and gapps after wiping system the apk part in data were messed up with the new gapps. If you flashed gapps without wiping system, gapps zip clean the apk on data and system if necessary and your phone will boot normally. In an update CM situation, you would be correct. My situation was a fresh install, so if the gapps break my first run and I can't get into OS, then I only have option to install gapps after Install of CM .

That's for the flash process you messed up thing by doing that. No mistakes made, I fixed an odd situation and shared how to resolve. There are a few others that have ran into this on N6 and other devices with CM 13, that's why the recommendation of flashing in recovery with CM so permission are right. I was not able to do that because of first run loop.

Now the permissions trick is skipable by flashing rom and gapps on twrp then boot the device Not really, as i said 1st , flashing roms and gapps caused my first run setup to loop and I could not complete first run and get into os.

If you're on a fresh install or on a not fresh install (i mean wiping /data or not) always flash gapps after Tom and then you can reboot. Repeating myself, but flashing roms and gapps caused my first run setup to loop and I could not complete first run and get into os.

I think the way you flash rom and gapps are wrong. No offence here. Just a warn. I try to explain why and if you have question or anything I'll try to explain it in a better English ^^. No offence taken, I have been installing CM on devices since CM 9. I have been around the block and realize what needs to be wiped/flashed. This was the first time I have encountered such an odd issue, and this is why I have posted my results. CM has been very solid for me through the years.
[Nexus 6 Android Development] Dead-neM:
I've understand this with your post above but thanks for the more complete answer ;)

I think

" So i decided to wipe and fresh install CM, go through setup, then reboot and install gapps through recovery . Reboot and first run everything is fine, so I rebooted to flashed gapps in recovery. "

I misunderstood that and though you were installing rom then boot into cm without gapps and then reboot into recovery and flash gapps. So i was talking about something not for your situation.

When I've flash cm12.1 on my n6 I've faced a similar problem with fc messages etc... But by wiping data and system completely except /data/media/0 and /data/.layout_version // then flash rom and gapps wipe cache, it booted without error this time.

Your solution is welcome and will surely help people in your case.
[Nexus 6 Android Development] brianr549:
That's my fault for not being very clear. I am not great at typing explanations. I was installing rom then boot into cm without gapps and then reboot into recovery and flash gapps. I had to do so because if I flashed cm and gapps at same time (and is recommended, and most always works) this caused first run setup to start over before complete and repeated indefinitely. I have received so much awesome information through the years from XDA that I am eager to give info back.
[Nexus 6 Android Development] mobitote:
On clean install its best to copy/save data/media data then wipe everything including data/media/. After that reload via adb or if on computer just copy everything back to phone. Then flash ROM, wipe dalvik& cache. Flash gapps then wipe dalvik & cache. The reboot. Its how I do it. Never had a problem ever since the tbolt days. Plus for good measure I wipe everything like three times just to make sure nothing is left. This is something I carried over from early days of twrp/cm recovery. Never had any issues at all.
[Nexus 6 Android Development] _AnAkIn_:
Apparently no one is applying security updates to the Nexus 6 kernel that CyanogenMod uses, it is pretty behind compared to what Google provides. Even though the settings say that the security patch level is recent, it simply is not true for this device.
[Nexus 6 Android Development] Dead-neM:
Source are in OP. Take a look...

Please no more post like this without proof info or a little bit of knowledge
[Nexus 6 Android Development] _AnAkIn_:
Maybe I did take a look already, which is exactly why I posted that.

https://source.android.com/security/bulletin/2016-08-01.html

Let's take CVE-2016-2544 which has been fixed with https://git.kernel.org/cgit/linux/k.../?id=3567eb6af614dac436c4b16a8d426f9faed639b3 and affect all Nexus devices according to the page.

I would be happy to see where you can find this patch being applied against the cm-13.0 branch on the CM sources.
[Nexus 6 Android Development] Elektroschmock:
Its neither in Google's upstream kernel. So it's not CM's fault.

https://android.googlesource.com/kernel/msm/+log/android-6.0.1_r0.120/sound/core/seq/seq_queue.c
[Nexus 6 Android Development] _AnAkIn_:
Any idea why? It's in their 3.10.y branch though:

https://android.googlesource.com/kernel/common/+/android-3.10.y/sound/core/seq/seq_queue.c

What does that mean for official Google builds then, would they be built from a different branch than the one CM pulls from?
[Nexus 6 Android Development] Elektroschmock:
I don't think that any device's kernel is released from the kernel_common repository.

You can ask here https://groups.google.com/forum/#!forum/android-security-updates why the patch you mentioned isn't included.
[Nexus 6 Android Development] gothy.gothy:
Who wants some Nougat?

https://www.cmxlog.com/14/
[Nexus 6 Android Development] Dead-neM:
I wonder if they'll discontinue cm13 for shamu when 14 comes out
[Nexus 6 Android Development] gothy.gothy:
Don't think so! I think they will be developed both, in parallel.
[Nexus 6 Android Development] Dead-neM:
Mmm I'm in doubt cause they have stop cm12.1 when 13 have been released. I'm talking about shamu i know that old device have still cm12 dev on it
[Nexus 6 Android Development] Elektroschmock:
CM13.0 will be maintained untill CM14.0 is feature complete and stable.
[Nexus 6 Android Development] nazfalas:
I guess it will be limited to snapshot releases, though. At least that's how it's been for ages now when new nightlies start.
[Nexus 6 Android Development] dbrickg:
Let's hope it's not ages till the new nightlies start :) Anybody hear any rumors about when the first cm14 might appear?

PS: just did a little searching on google, and found some estimates saying cm14 might come out in mid-October. But those estimates were based on how long it took for cm13 to be released after android 6 came out. So, my guess is that anybody's guess is as good as we're gonna get for the moment
[Nexus 6 Android Development] dbrickg:
Let's hope it's not ages till somebody posts something on this forum :(

Or maybe it's just one of those "no news is good news" situations....
[Nexus 6 Android Development] Dead-neM:
Devs are fully working on cm14. This is why nightly doesn't have lots of commits.

This thread is quiet most of time but user have always find a solution to their problem. On old thread and on new thread.

Feel free to post anything you want man
[Nexus 6 Android Development] dbrickg:
Yay! That's wonderful. Thanks for the news. Have you heard any rumors about when cm14 might be ready for the first nightlies? Or how the development is coming along in general?
[Nexus 6 Android Development] Dead-neM:
https://www.cmxlog.com/14

To follow commits

I don't know when it will be ready. But I'm sure it will.

Patience is a virtue ;)

Awesome dev neobuddy made a unofficial cm14

https://xdaforums.com/nexus-6/development/cyanogenmod-14-unofficial-sept-18-t3463784
[Nexus 6 Android Development] EricSB:
Please let me know what I am doing wrong... Here is what I keep running into.

At what seems to be very random times with CM 13 Nightly my cellular data stops working. Once this happens it never again functions regardless of what I do.

Here are things that I have tried:

1) Used 8/20 snap shot. Problem still crops up eventually.

2) Used nightly.

a) I have done quite a bit of searching and I have tried flashing a radio and boot loader and data still refuses to work.

I really love CM and really want to keep it, but am considering going back to Pure Nexus 6 as I don't have these issues.

Does anyone else with a Nexus 6 have this issue and more importantly any suggestions on how to fix this would be very appreciated.

Thank you in advance,

Eric
[Nexus 6 Android Development] Dead-neM:
1/Which Mobile brand do you use ?

2/Did you dirty flash snapshot over a nightly ???

3/does this happen when screen is on??
[Nexus 6 Android Development] EricSB:
Very good questions, thanks! I am using Sprint. And I have tried flashing from a complete wipe using sideload to upload CM snapshot and nightly. And to be honest, it may very well be the case that this happens when the screen is off.

UPDATE: No, it doesn't happen only when the screen is off... it seems to happen when I lose LTE and my Nexus 6 drops to 3G and from there I see "Sprint 3100" and after that there is no getting data back. Not even after airplane mode, reboot, or even turning the phone completely off and back on. Data never returns and I wind up stuck without data until I re-flash. It's a very frustrating problem.
[Nexus 6 Android Development] EricSB:
I'm still having the LTE issues with CM 13 and Sprint. Can you provide a link to this radio? I've tried searching for it and there is a lot to look through and the last thing I want to do is make the problem worse by flashing the wrong radio.

Thanks for your help and I REALLY hope this resolves my issue!
[Nexus 6 Android Development] julesism:
Hello. Links to the radios are in the first post and here:

http://xdaforums.com/nexus-6/development/fxz-nexus-6-recovery-flashable-fastboot-t3066052

My guess is the 27R is this one:

http://batakang.com/ftp/devs/mhous33/shamu/6.0/shamu_baseband_D4.01-9625-05.27+FSG-9625-02.104.zip

Hopefully that helps.
[Nexus 6 Android Development] Dead-neM:
13/nov/2016 broke xposed for me. No way to boot with 13/nov but i can with 6/nov.

LiveBoot display many problems with compiler and zygote. I can't see the commit that break this...

Anybody else?
[Nexus 6 Android Development] razorloves:
cm doesn't work with xposed anymore.

see post #4637 and #4638 here:

http://xdaforums.com/xposed/discussion-xposed-marshmallow-t3249095/post69607383#post69607383
[Nexus 6 Android Development] Elektroschmock:
Soon :D

First CM-14.1 nightly build for shamu is coming soon.

http://review.cyanogenmod.org/#/c/171238/
[Nexus 6 Android Development] :
finallyyyyyyyyyyy :d:d:d:d:d:d
[Nexus 6 Android Development] k1l:
did cm somehow push their own recovery? i even tried to flash twrp again in fastboot but it didnt work. i still only see the cm recovery.
[Nexus 6 Android Development] christianpeso:
They were having this Xposed problem in [MENTION=4203241]Neo[/MENTION] unofficial Resurrection ROM builds, which is CM based. Apparently it was fixed by the SlimRoms team. This commit reverted the problem:

https://github.com/HealthyMarshmall...mmit/0b5f4e5f762d4d8a85cab1a3085bf4296a97c4e5

Little more convo on it over on that thread:

http://xdaforums.com/nexus-6/development/rom-resurrection-remix-5-6-9-t3396453/page192
[Nexus 6 Android Development] Dead-neM:
Yes so it's what i though... I'm afraid that cm14 start and cm13 is let xposed unusable. Thanks Christian for the share. If cm13 last nightly still not work I'll compile a last romzip with the revert.
[Nexus 6 Android Development] Dead-neM:
Go to developers option and untick the "update cyanogen recovery"
[Nexus 6 Android Development] Elektroschmock:
Altough I wouldn't use CM-13.0 as we haven't merged the November security fixes.

CM-14.1 is up to date regarding security fixes.
[Nexus 6 Android Development] k1l:
yes thanks. That was checked and i unchecked it. I dont think that was checked before. But it works now.
[Nexus 6 Android Development] Dead-neM:
November security patch for shamu on kernel side is for mr1 so nothing to merge.

But there's some code for rom. https://review.cyanogenmod.org/#/c/169592

Is the patch merged right?

Anyway, I know that's not device specific but last android code to zygote that break xposed.

As you're a dev for cm do you know if this problem is in discuss? If the commit above could be merge? Before cm13 nightly insight?
[Nexus 6 Android Development] Elektroschmock:
The kernel commits from google went to the mr1 branch, but I think mr2 needs them too. The Nougat branch got the same commits.

The commit you mentioned has been merged, but it's not very important.

I don't have any knowledge if the xposed break is under discussion, as I'm just a regular guy who took over shamu, as nobody was maintaining it.

BTW:

https://drive.google.com/open?id=0By-BiXxmxKpkb21GQVBYWHBIQVE

use newest bootloader and radio

flash Gapps for 7.1
[Nexus 6 Android Development] adm1jtg:
Nov patches broke xposed on almost all roms, there is a single commit that cm would have to revert for it to work or they will need to whitelist resources for xposed
[Nexus 6 Android Development] :
first nightly is up , but its bad uploaded , can someone help us

link here : https://www.cmxlog.com/13/shamu/
[Nexus 6 Android Development] Dead-neM:
https://www.cmxlog.com/14.1/shamu/

First cm14.1 nightly here.

No more cm13. I've download 06/11 and 14/11 which are respectiveley the last one with xposed working and the last cm13 nightly one. I'll mirror them this night.

Now i think it's time to add cm14.1 to the thread name.
[Nexus 6 Android Development] coremania:
Anyone got a working dl for CM 14.1 nightly?
[Nexus 6 Android Development] Dead-neM:
Try the link in electro post.

The first of this page
[Nexus 6 Android Development] noenoen:
what you mean? i cant dl too

edit: i know what you means. thank
[Nexus 6 Android Development] coremania:
Thanks, but it says unofficial 11.16

Official 11.17 is what I want ;)