yashsingh1/xdaforums huggingface dataset:
[Nexus 6 Android Development] the_rooter:
Please do I will be one of the first there

---------- Post added at 10:44 PM ---------- Previous post was at 10:37 PM ----------

How so? Because the guy that said that to u is obviously blind of the issue. Very disrespectful.
[Nexus 6 Android Development] admiralspeedy:
Just doing some testing with APN settings. I'll let you know in a bit.
[Nexus 6 Android Development] the_rooter:
I am looking at my apn settings now. I am on straight talk. What me attach a picture to compare? This rom lte works great
[Nexus 6 Android Development] admiralspeedy:
To anybody that has the LTE issue, I've been testing things all night and I found something that seemingly works, but I need more people to test it.

After doing a clean installation of the latest nightly my phone sits with a full signal bar but no 3G/HSPA/LTE indicator. After several minutes it eventually connects to 3G. What I did was I dialed *#*#4636#*#* in the dialer, tapped "Phone Information" and scrolled down and changed the preferred network to LTE Only, but my phone then just sat without signal. So, I rebooted the phone and this time it connected to HSPA immediately but not LTE. I went back to the dialer and did the same thing and it immediately jumped to LTE. I then changed the preferred network back to the default LTE/GSM/CDMA at which point my phone stayed on LTE and LTE now survives reboots and and full power off/on cycles.

I'm gonna test this for a few days and see if it works permanently(I don't see why it shouldn't since it has survived dozens of reboots and power cycles now) and if anyone else could try doing this to confirm, we might be able to located the root of the issue.

EDIT: I'm starting to think this issue is truly carrier based because after doing this LTE works totally fine, even if I disable data and re-enable it or switch between WiFi and data. Mastamoon's build doesn't work 100% for me and toggling airplane more almost never worked for me or only got me HSPA but never LTE. I think it may have something to do with information being sent to the carrier being wrong or incorrect when connecting or something. Obviously it should be fixable because it's not an issue in other ROMs but I don't know how and I don't think a modem reset is all that's required.
[Nexus 6 Android Development] bmargm:
I tried sending it over to LTE only, but I jumped up to a LTE (no bars) connection without having to reboot. After a reboot it booted to HSPA, my setting had reset back to the default LTE/GSM/CDMA. Set it back to LTE only, LTE connects immediately. Switched back to LTE/GSM/CDMA, connection to LTE maintains. Rebooted, but connects to HSPA. This very well could be due to my location (a basement) and just not having a strong LTE signal. I will monitor my connection as I go about my day tomorrow. If it helps, I'm on AT&T via StraightTalk. I can post my APN settings if relevant.
[Nexus 6 Android Development] admiralspeedy:
That setting is supposed to reset.
[Nexus 6 Android Development] bmargm:
Ahh, okay. I'll make a post tomorrow with my results. Hopefully this works. Or the CM guys get over their dumbass attack.
[Nexus 6 Android Development] tangiers:
Just in case it helps you work out your bug, I have never had the LTE bug on the nightlies but I am on Telstra which is an Australian carrier.
[Nexus 6 Android Development] tembares:
VoIP works great on WiFi, HSDPA and LTE. Add your SIP provider and calls can be made (data only).
[Nexus 6 Android Development] mastamoon:
So what needs to happen going foward.. until the bug is found in CM, is we need to setup our own custom ril, that puts this fix in place without altering the main ril that the rest of CM uses.

Im still trying to wrap my head around that, if anybody else has the skill to do so, please by all means put something together. Even if you cant submit it yourself to gerrit, send me the patch and ill upload it.

My patch wont get merged, period. It was mostly a proof of concept to make sure this method of a workaround would work for us. And it seems by the vast majority of users, it does.
[Nexus 6 Android Development] admiralspeedy:
The problem is, is that restarting the modem doesn't fix the issue. I would say maybe once every dozen boots your builds actually connect to LTE for me and toggling airplane mode has never worked for me.

The issue is even bigger because during the initial setup after a clean flash, half the time it doesn't even see my SIM card in the device or I get no service for several minutes.
[Nexus 6 Android Development] mastamoon:
From all the feedback I have gotten, in this thread and others that are using the same fix goes against your findings.
[Nexus 6 Android Development] admiralspeedy:
Can you run a new build for me with the fix (I don't need the buggy Snap camera) so I can continue my testing? I flashed your 28th build four times last night and that other one from another poster and only once did yours actually connect to LTE for me.

Also, if you could PM instructions on how to setup my Linux VM to build my own copies, that would be cool.
[Nexus 6 Android Development] ieatacid:
I haven't tried mastamoon's builds but on my own builds, using his patch, LTE works every time.
[Nexus 6 Android Development] admiralspeedy:
Care to upload one of your builds?
[Nexus 6 Android Development] ieatacid:
https://basketbuild.com/devs/ieatacid/shamu

That build was synced with CM source last night.
[Nexus 6 Android Development] admiralspeedy:
Oh, that's the one I downloaded last night. I'll try it again today when I'm done my class.

So, it should connect to LTE after the initial setup on first boot?
[Nexus 6 Android Development] ieatacid:
I dirty-flash unless it can't be avoided so I can't say for sure, but I don't see why it wouldn't. It works on first boot after flashing and 'upgrading apps', and it works on every reboot after.
[Nexus 6 Android Development] admiralspeedy:
Ok, I will continue my testing.
[Nexus 6 Android Development] ieatacid:
I spent some time this weekend trying different things like the apn patch Matt Mower suggested (on mastamoon's gerrit change comments), and how to implement a device specific ril overlay. But that's as far as I got before having to retire for the night, and I can't do much more from work.

---------- Post added at 10:50 AM ---------- Previous post was at 10:40 AM ----------

I included the radio debugging flag in build.prop but it's disabled by default. To enable just find 'persist.radio.adb_log_on=0' and set to 1.

Edit:

adb logcat -b radio > radio.log
[Nexus 6 Android Development] admiralspeedy:
I will enable it.

---------- Post added at 05:52 PM ---------- Previous post was at 04:58 PM ----------

So I think I might actually be experiencing something totally different with this whole LTE thing. I have tried the official build, your build and Mastamoon's build now and they all do the same thing.

Basically after booting for the very first time the phone eventually connects to 3G and stays there. Now, if I reboot it immediately connects to HSPA and then if I wait a few minutes it connects to LTE and then LTE seems to survive power cycles and reboots just fine.

That probably explains why I didn't have issues on older nightlies because I was dirty flashing over one that was already connected to LTE but now I'm doing a clean flash.

Still doesn't explain why it first connects to 3G though or why the patch doesn't work for me.
[Nexus 6 Android Development] mastamoon:
It connecting to 3G first isnt what the patch is attempting to fix, nor is it the "LTE issue" people are having. This patch fixes the issue where upon a reboot on some GSM carriers, LTE would not connect until you toggled airplane mode.
[Nexus 6 Android Development] admiralspeedy:
I would assume being stuck on HSPA or 3G is the definition of not connecting to LTE.
[Nexus 6 Android Development] mastamoon:
as far as I know, thats not the issue.. the "lte issue" is not getting LTE (or any network afaik) upon reboot until airplane mode. I might be wrong, but Im pretty sure people were not seeing 3G either.
[Nexus 6 Android Development] admiralspeedy:
Then why say "No LTE" and not "No Network". Specifying LTE kind of leads people to believe that you are able to connect to a slower network like HSPA/3G.
[Nexus 6 Android Development] mastamoon:
Because Im guessing 99.9% of people are within LTE areas and thus have LTE on boot always? AFAIK, the phone boots up with signal but no connection... no LTE/3G

Im on Verizon so Ive never had the problem when using CM13.

Somebody else with the issue my patch fixes can further elaborate if you need more info.
[Nexus 6 Android Development] ieatacid:
There's no data connection at all. On the QS tile for network settings it shows T-mobile but nothing you typically need data for works. Web pages won't open, no push notifications, etc.

So, indeed, "no network" or "no data connection" would be more accurate.
[Nexus 6 Android Development] dwardo:
I'm getting phone shutoffs sometimes when I hang up from a call... Haven't found a pattern though...
[Nexus 6 Android Development] mastamoon:
People with the "LTE issue" will want to give tonight's official a go. These look like they might help.

http://review.cyanogenmod.org/131093 & http://review.cyanogenmod.org/131094

---------- Post added at 10:43 AM ---------- Previous post was at 09:59 AM ----------

I'm running a build now, I'm too impatient.
[Nexus 6 Android Development] dbrickg:
Aha! I just installed the latest nightly and was going to say that, as usual for me, it at least doesn't break LTE. Then I reread your post, and I'm betting by "tonight's official", you mean the next nightly, not the current one. Anyway, I'm glad someone has found something that might address the "LTE issue". It seems like that's been going on for far too long. Looking forward to your impatient build :)
[Nexus 6 Android Development] mastamoon:
LOL.. yeah I consider the latest official nightly at this point to be "last nights".

I really hope this fixes it because the modem reboot method would likely not fly in any form for a Nexus device on CM.
[Nexus 6 Android Development] dbrickg:
Yes, and, it seems that the modem reboot doesn't fix some peoples' problem. Their problem seems to be carrier-dependent. Hopefully these commits will fix both problems. It'd be really nice to get that dealt with ... and move on to some other issues :)
[Nexus 6 Android Development] mastamoon:
Ok, here is the build. This one doesnt include my 'lte fix'. Please give it a try.

https://www.androidfilehost.com/?fid=24399994186367480
[Nexus 6 Android Development] dbrickg:
Downloaded, backing up the previous one, will install this one and get back to the group once it's rebooted....

OK, it installed just fine and appears to be working quite well. I've never had the "LTE issue", so I can't say if this build fixed it, but, at least, I can say it didn't break it. I've still got good cellular data and the cell signal icon shows an "LTE" next to it. And the new Snap camera is there and appears to be functioning just fine.
[Nexus 6 Android Development] CCJ22:
Has ANYONE gotten ok google anywhere to work on ANY CM13 rom? or nightly? No matter what rom I try, OK google anywhere doesn't work. Only works from the app. Sadly
[Nexus 6 Android Development] admiralspeedy:
Has never worked in CM13 and I believe it's something to do with a bug in an included Motorla Always on Voice app(called triggerenroll). If you use the Google launcher it works from the homescreen or the app, but nowhere else.

You can train it to your voice now, which you couldn't before so some progress is being made.
[Nexus 6 Android Development] jlvlawrence:
It doesn't work on my nexus 9 with CM 13 either.
[Nexus 6 Android Development] mastamoon:
You guys are killing me!! Nobody but [MENTION=4490141]dbrickg[/MENTION] tried my build? And he doesnt even have the "lte issue".
[Nexus 6 Android Development] adm1jtg:
Not a very cooperative bunch huh.... I would have helped but my lte issue is also if i loose connectivity and then gain service back it leaves the phone in limbo shows all signal bars but no LTE or 3g or whatever and is not actually connected at all. I only have the main phone and thus cannot take the chance of loosing service and not knowing it. Please dont get discouraged and keep up all the good work.
[Nexus 6 Android Development] laosguy:
All good here runs great thanks no lte issues here on t-mobile
[Nexus 6 Android Development] mastamoon:
I know, I'm must messing around. I was excited to see a fix from CM merged that might have fixed it and thought when I posted a build before the official tonight a few would have given it a go.

This fix might help you also [MENTION=2781850]adm1jtg[/MENTION], never know. It's not the same fix I had put up.

---------- Post added at 08:18 PM ---------- Previous post was at 08:16 PM ----------

So you had the no lte on reboot issue previously and now do not with the build I posted this morning?
[Nexus 6 Android Development] MortaLPortaL:
I have MetroPCS. Will try this in a few and update if anything.

okay it seems to work fine. LTE is connected. too bad my favorite game doesn't work on it(puzzle and dragons lol).
[Nexus 6 Android Development] mastamoon:
Did you previously have the issue with no lte on reboots until toggling airplane mode?
[Nexus 6 Android Development] MortaLPortaL:
yeah. before your build I would get no LTE. Airplane mode fixed it but temporarily.
[Nexus 6 Android Development] DragonHunt3r:
How can I replace the default home launcher with Google's Now Launcher ?

When installing the now launcher it doesn't let me change the home launcher, there's no option other then trebutched
[Nexus 6 Android Development] mastamoon:
Anybody flash the official nightly yet? How goes your LTE on reboot?
[Nexus 6 Android Development] Irisservice:
New nightly does not fix LTE on T-mobile NYC :(
[Nexus 6 Android Development] mastamoon:
Hmm... It should be the same as the build I posted yesterday and a few have said it worked.... :confused::confused:

(╯°□°）╯︵ ┻━┻

(╯°□°）╯︵ ┻━┻
[Nexus 6 Android Development] raresoul77:
I'll check it out right now. Will report back in a few mins.
[Nexus 6 Android Development] Irisservice:
Just tried yesterdays that you posted...does the same..
[Nexus 6 Android Development] mastamoon:
And this is simply doing a reboot and having no LTE/Data until you airplane mode, correct?
[Nexus 6 Android Development] Irisservice:
Im trying the one you posted on the 01/31

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

simply doing reboot...did not try airplane mode... airplane mode did not last for me in previous officials...only thing that gave me usable results was change preferred network to 3G..no LTE

---------- Post added at 09:52 AM ---------- Previous post was at 09:49 AM ----------
[Nexus 6 Android Development] raresoul77:
5 reboots , toggled airplane 3x and LTE is sticking .....for now ! (SPRINT)
[Nexus 6 Android Development] dbrickg:
So, wait... you still had to toggle airplane to get LTE (or any cellular data)? I thought the whole point of these updates was that you'd get LTE (cellular data) without having to toggle airplane mode. At least that's what mastamoon's unofficial updates were supposed to do. But, as far as I understand it, his unofficial builds would do a sort of under-the-covers airplane mode toggle by restarting the modem. Then yesterday there were a couple of commits that looked like they *might* do a better kind of fix. So mastamoon built a new unofficial release, without the under-the-covers airplane mode toggle, to see if the new commits would help. A couple of people in this forum appeared to think that the new release fixed the "LTE issue". But maybe not.... It's all way too confusing for me.

At any rate, I installed the 20160203 nightly, and LTE continues to work for me (just like it always has). No Snap camera. Everything else looks just fine....
[Nexus 6 Android Development] mastamoon:
Issue is it seems like there is 2 different issues.. im guessing they kinda have to do with eachother, but manifiests itself slightly differently for each carrier affected. Im just dumbfounded that Verizon is the odd man out with 100% working RIL. Usually VZW is the bastard child.
[Nexus 6 Android Development] raresoul77:
I just toggled airplane for the hell of it to see what happened. It's still working!
[Nexus 6 Android Development] adm1jtg:
not getting any warm fuzzies from this forum about the issue really being fixed for all users. Will keep watching though.
[Nexus 6 Android Development] ilatimer1:
For me the new nightly did not fix my LTE issue. If I reboot my phone it does not get a data connection. I need to toggle Airplane mode to get it back. I did do a dirty flash. I might to a clean flash and test that.
[Nexus 6 Android Development] mastamoon:
I wouldn't bother clean flashing. Sounds like the merged fixes are a bust. :(
[Nexus 6 Android Development] lostwhat83:
Feb 02 nightly official fixes the LTE issue with me. Straight talk using ATT towers.

Dirty flashed.

First boot LTE worked without airplane toggle.

I haven't restarted my phone since the flash, and LTE continues to work.

OK now I'm confused!

I just restarted after this post. I had to toggle airplane mode to get LTE (data) to work. The reason I am confused is my data worked during first boot after Feb 02 nightly without airplane toggle.

I am going to dirty flash Feb 02 right now and see if LTE works after first boot without airplane toggle again. I'll post my results.

LTE works without airplane toggle during first boot with dirty flash. LTE does not survive a reboot. Mind blown! Haha
[Nexus 6 Android Development] ilatimer1:
I experienced same results. Boot after dirty flash and LTE works fine. Reboot after that and no data connection.
[Nexus 6 Android Development] ieatacid:
No data for me as well (until airplane mode toggle), built from source. I posted a radio log on the "LTE fix" gerrit page the other day but I don't know if anyone looked or if it's even enough info to help.
[Nexus 6 Android Development] mastamoon:
I thought the log you posted is what led to the patches that were merged lol. Put another one up there on the latest nightly.
[Nexus 6 Android Development] tembares:
For everyone who has data problems.

After flash is the prop.build or any other configuration file the same? Maybe a modification of a configuration file takes place after first reboot.
[Nexus 6 Android Development] ieatacid:
build.prop doesn't get altered after reboot. Also, after first boot, you can "fix" data by toggling airplane mode on/off.

---------- Post added at 08:53 PM ---------- Previous post was at 08:48 PM ----------

Yeah, I don't know. If that's the case, I wish someone would've replied, and I would've done it last night. Now it's too late to do before I go to bed.
[Nexus 6 Android Development] blitzerking1:
So far LTE on sprint is working for me on 2/3 nightly. I have not had any connectivity issues yet...
[Nexus 6 Android Development] Herk718:
Can someone kinda upload a copy of the Music Player apk located in this ROM... Thx!
[Nexus 6 Android Development] tembares:
That's why I added 'or any other configuration file'. My knowledge isn't technically. If after one reboot the trouble starts again, then something must have changed in between. I guess :rolleyes:
[Nexus 6 Android Development] tattedupboy:
Is the app locking feature behaving strangely for anyone else?
[Nexus 6 Android Development] blitzerking1:
Yes. I don't think it is working right for me. When I put a lock on an app and try to start the app a notification pops up. I click on the notification and it opens the wrong app. Until this is fixed you can use cm security antivirus applock that does the same thing.
[Nexus 6 Android Development] mastamoon:
New build... LTE Fix + Snap Camera ----- https://www.androidfilehost.com/?fid=24399994186368719
[Nexus 6 Android Development] l337lasers:
My nexus 6 has always had LTE issues no matter what ROM I install. I'm on Project Fi and even after swapping Sim cards and too many emails with Project Fi support, T-Mobile has never worked on my device.

I recently installed CM13 again and I was dropping my connection nearly every minute. I found that I have much better luck when I flash the stock developer radios from developers.google.

I almost never have LTE issues after flashing the radios.

---------- Post added at 11:20 PM ---------- Previous post was at 11:01 PM ----------

Each nightly download I have installed since my re-installation back to CM13 a few days ago continues to pop up with the error "Unfortunately, CyanogenStats has stopped" during each boot.

I just can't seem to figure out why...
[Nexus 6 Android Development] dbrickg:
Geez... I *almost* wish I had the LTE problem so I could test this properly. I did download and install it, and it works just fine for me: my LTE/cellular data *still* isn't broken. But it looks like anybody who had the LTE problem has been so discouraged by CM's lack of attention to it, that they've all gone elsewhere :(

PS: just noticed that mastamoon's last post has seven thanks. So, I guess it's not so much that people aren't using the builds, just that they don't post about it, since it's all already been said over and over again.
[Nexus 6 Android Development] dgk823:
Thank you mastamoon. Its very humble and selfless of you to give hours of your time every day to help people, and you don't even own the Nexus 6. I hope more people will recognize your selfless efforts. Your builds with LTE fix have helped me on T-Mobile USA LTE band. It reboots the modem, and LTE shows on my status bar within 3 seconds. Thank you.
[Nexus 6 Android Development] vercety974:
Is CM13 enough stable to use it as daily driver ?

Envoyé de mon Nexus 6 en utilisant Tapatalk
[Nexus 6 Android Development] mastamoon:
host says 11 downloads lol

I do own a Nexus 6.. I just dont use CM on it. I did at some point but the radio issues have turned me off to it. Currently running Pure Nexus, which has most of the CM type features, but is built on AOSP and thus doesnt have the radio issues that plague CM.

Glad you like the build. Ill put one up every now and then for you guys until CM fixes their ****. I would **lightly** suggest moving on to a different, non cm based rom if you want **** to work lol
[Nexus 6 Android Development] stebomurkn420:
Sweet.. I too was experiencing the LTE issue on T-Mobile, as described by other users of cm13. I will clean install latest nightly to see if the fix at hand truly cures my issue. Thanks again devs... I will update this post with my findings...
[Nexus 6 Android Development] adm1jtg:
Same here no offence to all the great devs but cm13 simply isn't worth it at its current state. It is currently the ONLY rom out there that doesn't have even a stable base. There are no features unique to cm anymore not that there are cmte builds of dirty unicorns and pure nexus, so unfortunately I am just like ... why bother. I also moved to pure nexus and while I still check here hoping the issues will get resolved I really have lost hope and likely wont jump roms anytime soon.
[Nexus 6 Android Development] razrlover:
Confirmed LTE and volte working Nexus 6 T-Mobile,

With mastetmoons build from afh and opengapps

Appreciate you're work
[Nexus 6 Android Development] raresoul77:
Awesome nightly! 2\5
[Nexus 6 Android Development] zoome9:
Been using build 02/04 since release. Haven't come across any issues yet.
[Nexus 6 Android Development] stebomurkn420:
I too can confirm that LTE has been fixed :) I dirty flashed mastetmoons build on top of official cm13... Had LTE on first boot and after toggling WiFi. Two thumbs up.
[Nexus 6 Android Development] stebomurkn420:
Is everyone sticking with the stock kernel??? I would have to disagree with other users and say that cm13 is definitely a DD. I am getting some stuttering though, when installing an app, the phone freezes for like 3-4 seconds. Lol. Gonna play around with kernels today...
[Nexus 6 Android Development] Stroky:
I'm using Hells Core and its working perfect!

So todays Build is stable?
[Nexus 6 Android Development] XxCyberHackerxX:
Is this MultiRom compatible?