yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] mastamoon:
It wasn't merged so it isn't fixed officially. You can test his fix by editing your build.prop as specified by the commit and see if it helps.

If a few people do this that had issues previously, I and others can comment on the change and see if it can get merged. Also in the meantime we can make a flashable zip or something that will allow you to keep using cm13 till it gets merged.
[Nexus 6 Android Development] pirasalbe:
Can anyone activate battery saver mode???
[Nexus 6 Android Development] mastamoon:
Ive attached a flashable zip that will allow those with LTE issues to test http://review.cyanogenmod.org/#/c/126248/ "fix".

As you can see in the comments on this patch, even DCD says it doesnt work everytime. But maybe it will work more often than not.

You will need to flash this zip after every nightly update. Build.prop doesnt tend to change all that often so it should be ok for a while.
[Nexus 6 Android Development] pillzbury:
Thanks, I will try the zip next time I flash a nightly (hopefully today) and report back.

One observation I've made - I dunno if it's useful or not - is that I've noticed LTE often drops around the same physical locations. For example, LTE always fails to kick back in after I come above ground in NJ after taking the PATH train from NY. But I don't have this same problem when I come above ground in other locations. Also, yesterday, I put my phone in airplane mode before going underground to the PATH, and LTE did come back when I took my phone off airplane mode when I came back above ground.

Toggling airplane mode (other than the instance I just mentioned) never works to bring back LTE. The only thing that does is restoring the last nandroid on which I had LTE.

Thanks again for the fix - let's hope it works.
[Nexus 6 Android Development] jl33:
What kernels work well with this build? I got a funky error when installing HC that I couldnt catch, just some red error text and a quick reboot back to recovery
[Nexus 6 Android Development] the_rooter:
Hc permissive installed fine
[Nexus 6 Android Development] Jaspreet84:
Yes, on my mobile it's working with CM13 nightly.
[Nexus 6 Android Development] DarkRazorr7:
Is someone trying today's nightly? Is it fixed problems with mobile network, random reboots and battery consumption?
[Nexus 6 Android Development] dbrickg:
2016-01-07 nightly

Just installed the 01/07 nightly: root-explorer kept crashing for me, and screen casting still doesn't work (just casts a black screen and the phone display itself goes black every second or two). Didn't take time to test much of anything else.

PS: noticed when it was booting, that the little white screen said "optimizing app 12 of 29", instead of my usual "12 of 59". Those numbers are approximate. I don't remember the exact ones. And I use the Opengapps pico version, so your numbers may vary. But I was struck by the fact that they appeared to be about half of what they used to be. Not sure if that's significant or not. Just wanted to note that here, in case anybody else tries it and notices something similar. Or, in case anybody has any ideas about why that might be.
[Nexus 6 Android Development] Khizar:
Root Explorer is fine for me, I dirty flashed on top of the 4th Jan night.
[Nexus 6 Android Development] dbrickg:
Hmm, thanks. Guess I'll try again. I dirty flashed over the 1/4 nightly, too, but there were some rather strange symptoms, which made me think I'd messed up somehow. So, I'll install again and let you know how it goes for me this time.....

Well, still no better. And this time the "optimizing apps" screen said "3 of 20" and it only took a few seconds ... so that makes me think maybe the gapps package was bad, even though I downloaded it a second time, just to be sure. Guess I'll try restoring the 1/4 backup and reflashing the 1/7 nightly, but without flashing opengapps...

Nope, even without opengapps: Root Explorer still "stops unexpectedly," and I still got the "3 of 20", only this time I noticed that it started at "14 of 20" or something like, and it still took just a few seconds, instead of the usual 5 minutes or so that it takes to optimize. And I checked screen casting again, and that still didn't work. So, seems like I've messed something up. Maybe it's time to do another clean install. I'd done maybe 3 dirty installs to get to the 1/4 nightly ... sigh.
[Nexus 6 Android Development] preshit10:
I have the same problem with screen cast.
[Nexus 6 Android Development] the_rooter:
Why are u dirty flashing gapps all you need to flash is the rom.
[Nexus 6 Android Development] dbrickg:
Yeah, I hadn't seen anything in the git commits that made me think that would be fixed... but I keep hoping :(

I dunno... just old habit, I guess. I've always done that, for years now, and never had any problems with it. I thought I'd read some place that that's what you were supposed to do: flash rom and gapps, clean cache and dalvik, reboot. But several people on this thread have pointed out that, when dirty flashing, I don't need to flash gapps, just the rom. Guess it's time to change my old ways :) Thanks for pointing it out again
[Nexus 6 Android Development] Khizar:
Don't dirty flash gapps along with rom on roms that have gapps backup script, that causes a lot of issues. Change the habit, before things were simpler, not much caused issues but now almost doing anything out of the ordinary will cause issues.. LOL
[Nexus 6 Android Development] dbrickg:
Thanks. And should I skip the clear cache and dalvik, too? Or do I keep doing that?
[Nexus 6 Android Development] ilatimer1:
Just a FYI, I flashed the latest CM13 Nightly and noticed that LTE was working with out me cycling Airplane mode on and off :).
[Nexus 6 Android Development] dbrickg:
Just did a clean install of 01/07, and still got "Root Explorer stopped unexpectedly" every time I tried to use it :(
[Nexus 6 Android Development] pirasalbe:
It deosn't work for me from setting and tile :( :confused:

Edit: Also H indicator is still not working
[Nexus 6 Android Development] jmartin72:
http://review.cyanogenmod.org/#/c/127244/

Why would Shamu need this if it doesn't have a fingerprint sensor?
[Nexus 6 Android Development] DarthDestroyeis:
That has nothing to do with a fingerprint scanner. It deals with the stock Android version for the device and updating some items to the latest and greatest.
[Nexus 6 Android Development] jmartin72:
I see, thank you
[Nexus 6 Android Development] dbrickg:
01/08 nightly!

Screen casting works on 01/08!!!

And it looks like Root Explorer was crashing because of some newness... the Pro version doesn't like the key. I uninstalled everything and reinstalled, and now it seems to work. At least somewhat. It's now called "Explorer" with no "Root" in front. And when I tried to move a file, I got the dreaded "Unfortunately Explorer has stopped" message. I'll keep playing around with it and get back to the group in a bit....

Well, I don't know. I can't seem to make Root Explorer happy whatever I do. Guess I'll just leave it for the moment.

Very happy that screen casting is working!
[Nexus 6 Android Development] mastamoon:
http://review.cyanogenmod.org/#/c/127242/ and http://review.cyanogenmod.org/#/c/127243/ reverted some changes that killed Screen Casting around December 20th or so.. does that sound right?

Explorer is the non Root version of Root Explorer I believe. I have moved away from Root Explorer and am not using Solid Explorer. Hasnt let me down yet and is all materialized n stuff.
[Nexus 6 Android Development] dbrickg:
Thanks, mastamoon, for the info on the screen casting changes. December 20th does, indeed, sound about right. I think the 12/18 nightly was the last one where it worked for me. And thanks too for the recommendation of Solid Explorer. It looks pretty nice. I went ahead and purchased the permanent version.

So, I'm back to using cm13 as my regular rom. Hurray!
[Nexus 6 Android Development] chromatica86:
Why no just use the built in CM file manager? It has root access. Always been my go to.
[Nexus 6 Android Development] Khizar:
You cursed me mate... LOL.. It was working perfectly for me on yesterday's nightly and now after 5 years of perfect use, with no issues, root Explorer started crashing on me in today's nightly. I've been recommended ES and solid, gonna switch to one of them after some testing. Using the built-in CM file Explorer temporarily but it isn't DD material.

Simply put, it isn't as efficient IMHO.
[Nexus 6 Android Development] dbrickg:
Yeah, I really liked Root Explorer, too, damn! But Solid does look pretty good. I'll play with that for awhile. And maybe Root Explorer will get a fix so we can go back to it.
[Nexus 6 Android Development] adm1jtg:
The issue seems cm specific. I have run root explorer on other roms both aosp and stock 6.01 without any issues. Ver 3.3.7
[Nexus 6 Android Development] dbrickg:
Yes, and, not only cm specific, but specific to the last couple of nightlies. It could well be that on the next nightly root explorer will work perfectly.
[Nexus 6 Android Development] oak:
Installing busybox brought Root Explorer back for me.
[Nexus 6 Android Development] mrkhigh:
***Oak hugs oak.... If that makes no sense to you ignore it.

Lte still broken?
[Nexus 6 Android Development] datagubben:
Not sticking after reboot.
[Nexus 6 Android Development] oak:
I guess I'll ignore it..... :laugh:
[Nexus 6 Android Development] mrkhigh:
Used to know a guy named oak years ago... He would type that from time to time.
[Nexus 6 Android Development] olus:
lots of changes with snapdragon camera. anyone tested newest nightly? can we record slow motiom or high speed videos now?
[Nexus 6 Android Development] Khizar:
Looks like nav bleed is finally fixed by CM and the fix has been merged.

http://review.cyanogenmod.org/126981

Update - Confirmed it's fixed. Been using today's nightly for a couple of hrs now and no bleed.
[Nexus 6 Android Development] the_rooter:
What's the nav bleed?
[Nexus 6 Android Development] Khizar:
Look at navigation bar.
[Nexus 6 Android Development] the_rooter:
Thanks never noticed that. I am currently not on cm until the lte issue and the stock launcher issue is fixed
[Nexus 6 Android Development] Harry44:
LTE Issue? I am literally sitting in first boot. Do I need to flash something else lol.
[Nexus 6 Android Development] the_rooter:
I heard different people posting that lte is fixed for att and tmobile users and others say it's not. After u reboot it doesn't survive u have to toggle airplane mode to work.
[Nexus 6 Android Development] oak:
LTE is working for me. I'm on ATT.
[Nexus 6 Android Development] mobitote:
For those using root explorer...

Seems like as of 0108 nightly, from the changelog; seems cm is using toybox instead of busybox(deprecated). Therein lies the issue.

I think once the root explorer dev updates his app to find toybox things should go back to normal. In the mean time .. The in built file manager pretty has the same functionality.
[Nexus 6 Android Development] the_rooter:
Just cleaned install the newest nightly and LTE still doesn't survive even with the zip. Att here and the only way to get it back i had to toggle airplane mode. Another thing that happened is when i turned on GPS for maps the system ui crashed. Hasn't happened since after.

Update: Found another bug on the latest nightly cleaned flash that when changing ringtone or notification sounds settings crash. I use Zedge to get different sounds.
[Nexus 6 Android Development] Khizar:
Yes root Explorer needs to be updated. I personally switched to solid Explorer and it's growing on me, probably won't switch back to root Explorer even after its updated.

No crash for me.

Only FC's I have on CM13 atm are when I unlink notifications/ringtones volume and when I enter then exit other sounds.
[Nexus 6 Android Development] PeteSeiler2010:
What carriers are having the LTE issue? I flashed a build that a buddy of mine compiled and LTE is working fine on that and I am on Sprint.

I will gladly flash it back to my phone and answer any questions you guys have, I am no developer so nothing too technical, lol.
[Nexus 6 Android Development] tembares:
Increasing ringtone doesn't work for me. First ring is low, the second is loud already.
[Nexus 6 Android Development] the_rooter:
its only gsm networks...att and tmobile
[Nexus 6 Android Development] the_rooter:
This doesn't work with the latest build. Question though has dcd thought about reverting back to the lollipop APN settings.
[Nexus 6 Android Development] dbrickg:
deleting my cm12.1 backup

Well, cm13 nightlies have been solid enough for long enough that I backed up my cm12.1 backup to my computer and deleted it from my phone.... Hope I'm not jinxing myself :)

I'm on Verizon and have never had the LTE issue with cm13. Screen casting seems to be working quite reliably now. Hopefully Root Explorer will get fixed soon, but till then Solid Explorer is usable. It think there were a couple of other issues, but I can't remember now what they were.
[Nexus 6 Android Development] the_rooter:
I left the cyanogenmod 13 for a few days and i wanna come back, is there a known way to get supersu to work on the rom? I tried flashing 2.52 and i just get a bootloop. Thanks guys/gals.
[Nexus 6 Android Development] HueyT:
It has 2.52 built in so just flash the rom, gapps, and enable root in Dev. Options for "apps and adb" and you should be good to go :good:
[Nexus 6 Android Development] the_rooter:
That's not what I asked. U understand root is built in, but I wanna use supersu so I don't have that annoying icon on the status bar
[Nexus 6 Android Development] cuberio1:
You'll probably find what you're looking for here (I personally use 2.65 without any trouble, did not try 2.66 yet)
[Nexus 6 Android Development] datagubben:
Any fix yet for the 4g/lte issue?
[Nexus 6 Android Development] the_rooter:
Nope still there
[Nexus 6 Android Development] NOSTALGIA:
cant seem to make viper work
[Nexus 6 Android Development] tembares:
Most of the posts in this thread are about the 4G/LTE issue.

Does other devices have this issue, too?

If it is specifically this device, will there be a solution at all? As far as I know there is no maintainer for this device. As far as I understood from posts before, if there is no maintainer, then there will be no specific solutions for our device.

I hope I don't burst any bubbles :eek:
[Nexus 6 Android Development] dbrickg:
mastamoon says there's a developer, DCD, actively working on the LTE problem:

http://xdaforums.com/showpost.php?p=64637580&postcount=843

but if you follow the link in that post you'll see that DCD says it's not a real fix, and the commit has been "abandoned." I don't know enough about the internals of cyanogenmod development to have any idea what all that means. Maybe somebody more knowledgeable than me can chime in here
[Nexus 6 Android Development] EvilDobe:
Means it didn't work & they abandoned it. Much as one would abandon a child.. same definition.
[Nexus 6 Android Development] dbrickg:
Thanks for the clarification :)

I guess what I was asking is what that means in terms of the LTE problem that's plaguing this phone. Has DCD abandoned the quest? Is anybody else working on it? Is the Nexus 6 an abandoned child? That sort of thing....
[Nexus 6 Android Development] mastamoon:
I think the fix shamu needs is like http://review.cyanogenmod.org/#/c/127013/

I was gonna try and roll a build with this, but there is a bunch of other things that need to be done along with it since we dont ship our own RIL. Not sure if anybody else here is building and would want to give it a go. I havent had time to work on it.
[Nexus 6 Android Development] dbrickg:
Wow, yes, that looks really promising! Seems that somebody has actually tracked down the problem and come up with a fix. Hopefully the same thing can be applied to shamu!

PS: This commit log (referenced in the one posted by mastamoon above) has a longer explanation:

http://review.cyanogenmod.org/#/c/126770/
[Nexus 6 Android Development] akanealw:
I wanted to do the same thing, so I did some testing last night.

1.) Do a factory reset, wiping all partitions except internal storage. Flash CM13 nightly, flash gapps, flash SuperSu 2.66, and reboot.

2.) Run through setup, then use the CM File Manager and created a file called .supersu in /data and enter "SYSTEMLESS=false" (no quotes) in it.

3.) Reboot into recovery and reflash just SuperSu 2.66 and reboot. Check the supersu app after booting up and it should say it is installed in /system.

Good luck
[Nexus 6 Android Development] mobitote:
Quick question I have noticed with cm13, on the notification with regard to tethering or hotspot; it only shows that one device connected unlike the way it used to be in cm12, where it would show the total number of devices connected. I know tethering and hotspot is working for all devices connected via hotspot.

I was wondering if this is prevalent on cm13 on n6 or its just occurring in my 2 n6s.

The reason I am asking is because after say six or so devices on cm12 things kinder got slow and such and I'd spread the load around. For the curious I am on VZW grandfathered plan and gotta justify paying an arm and a leg for unlimited internet. Plus hate to admit its faster and better where I live compared to the other options around.
[Nexus 6 Android Development] wessiide:
I'm still on lollipop, an old paranoid Android rom and want to update. Do I need to do anything special to install cm13 or just wipe data and cache then flash rom and gapps? I am also encrypted if it matters. I appreciate any help I have fallen so out of touch with the rom community.
[Nexus 6 Android Development] PainToad:
What's the appeal of CM13 when there's other roms with more features and less bugs?

Not trolling, genuinely interested.

---------- Post added at 03:09 AM ---------- Previous post was at 03:01 AM ----------

Would be a good idea to update bootloader and radio. But remember once you upgrade to bootloader over 5.1, you can't downgrade without bricking. I'm sure someone can explain this better.
[Nexus 6 Android Development] NOSTALGIA:
for me the cmte is so appealing rather than rro
[Nexus 6 Android Development] the_rooter:
Hey just an idea. Could the LTE issue for some gsm networks be a result of the radio? Has anyone tried another radio?
[Nexus 6 Android Development] adm1jtg:
Mind you I tested modems BEFORE cm13 hit official nightlies but back then I tried 3 different modems and had the same issue with all of them, The same issue we are STILL experiencing now
[Nexus 6 Android Development] wessiide:
Just one of the old guard that I'm familiar with. I mostly used paranoid Android for the longest time across 3 different devices but they seem to be MIA. What roms would you recommend?
[Nexus 6 Android Development] dbrickg:
Was checking the cyanogenmod nexus 6 forums. Looks like the LTE issue is bugging everyone there, too:

http://forum.cyanogenmod.org/forum/1150-google-nexus-6-development/

Luckily for me, it doesn't appear to be affecting Verizon (knock on wood): my LTE is better now than it has been in ages. But it must be really irritating (to say the least) to everyone on carriers where LTE is broken :(
[Nexus 6 Android Development] evilbobvu:
I am on Verizon but the signal is pretty weak on few ROMs that I've tried.

Maybe I will give this a shot to see any improvement.
[Nexus 6 Android Development] dbrickg:
If you do, let us know how it goes. I'll be interested to hear if there's any correlation between signal strength and LTE. Good luck with it!
[Nexus 6 Android Development] bmakk2055:
Have you guys tried these apn for t-mo ?

Name:*T-Mobile US LTE

APN:*fast.t-mobile.com

Proxy:*Not set

Port:*Not set

Username:*Not set

Password:*Not set

Server:*Not set

MMSC:*http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS proxy:*Not set

MMS port:*Not set

MCC:*310

MNC:*260

Authentication type:*Not set

APN type:*default,supl,mms,hipri,dun

APN protocol:*IPv4/IPv6

APN roaming protocol:*IPv4

APN enable/disable:*APN enabled

Bearer:*Unspecified

MVNO type:*None

MVNO value:*Not set
[Nexus 6 Android Development] the_rooter:
For the lte issue
[Nexus 6 Android Development] mastamoon:
You guys with the LTE issue, are you sure its not actually connected but just not showing any indication that it is? LIke do you still really have service/data when your phone is "broke"?

I only ask because this commit http://review.cyanogenmod.org/#/c/128480/ looks like it fixes this condition and I thought a few of you had said something similar.
[Nexus 6 Android Development] pillzbury:
Nope, there's no connection - I've tried.
[Nexus 6 Android Development] mastamoon:
OK =\
[Nexus 6 Android Development] adm1jtg:
You and I had tested this very scenario earlier as well as the apn settings. The logcats I sent also didnt show you anything of value.
[Nexus 6 Android Development] Xenosis:
It's as easy as toggling airplane mode to get it connected though. Makes me think it's either a timing issue or the routine is flawed that starts it.
[Nexus 6 Android Development] dbrickg:
Hmm, I'm not sure that's strictly true. It seems to me that I remember reading that for some people (or for some carriers, or... ) it *is* as simple as toggling airplane mode. But for other's it's not. I'd love to hear that I'm wrong about that :)
[Nexus 6 Android Development] HeavyYeti:
Running the 1/14 nightly and last night I ran into the LTE issue, as well. A simple Airplane Mode toggle quickly fixed it.

While we wait for an official fix, this might relieve some stress.

Running on T-Mobile, by the way.:cool:
[Nexus 6 Android Development] adm1jtg:
The major issue I had was, YES its as easy as toggling airplane mode but lets says you travelling or driving and your signal drops for just a split second but you don't realize it.... you data will not recover until you look, realize the issue, and toggle airplane mode.
[Nexus 6 Android Development] dbrickg:
Yes! I used to have a phone that did something like that. I used a gps tracking program while riding my bike, and sometimes it would lose its network and I'd lose whole sections of my route. It was especially prevalent when switching from wifi to cellular data, so it got to the point where I knew I had to stop my bike, shortly after visiting a coffee shop (for instance) to make sure cellular data hadn't dropped.

PS: this one, for instance. note the big straight section at the bottom of the map, that doesn't follow any road, where the mapping program lost contact so it just drew a straight line between the last known point and the point where I rebooted the phone; there's another, near the top, where the track goes absolutely straight north-south, cross country for 10 miles or so:

https://www.strava.com/activities/274975596
[Nexus 6 Android Development] slogar25:
Guys I think this is an android issue in general with the MM 6.0.1 update. I have read in another forum hear on xda and several articles on Google itself. I believe Google is aware of this though and is working on it for the next update. So...not sure these are actually ROM specific issues rather an android across the board issue.
[Nexus 6 Android Development] direwolf1:
Don't know if my experience is helpful, but I'm an AT&T user. I had the LTE connection bug on CM13, but as several users have described, toggling airplane mode after reboot was sufficient to fix it. I've since tried two AOSP (non-CM) ROMS--Dirty Unicorns and AOSiP--and neither of them have this problem.
[Nexus 6 Android Development] slogar25:
Yes very weird. I also have been lingering on all forums like you said DU and AOSIP and have heard that the GSM networks(att and tmo) are the ones affected. It's been hit or miss. But it was actually AOSIP were I got clued in on the total bug in android
[Nexus 6 Android Development] mastamoon:
That's because those rom teams don't **** with the telephony stack like cm does for the most part. They generally don't pull in CAF stuff that tends to break a lot of things also.

Im currently on Pure Nexus and haven't had any of the cm issues... Aosp based roms with cm like tweaks are pretty win. Or stock with xposed. CM is awesome for non nexus phones after they have been abandoned by the manufacturer, mostly because you have no other choice.