yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Nexus] astraelraen:
With the 8/18 CM 10.2 nightly my Gnex goes to sleep or the screen turns off and the power button won't turn it back on. I have to do a battery pull to fix the issue. Does anyone else have this issue? Seems kinda random. It will sleep/turn off just fine 95% of the time.

I have had this issue with CM before in other nightly builds. I did a dirty flash, I'm wondering if that is part of the problem.
[Samsung Galaxy Nexus] TurboD:
Mine starting doing that, I also dirty flashed.
[Samsung Galaxy Nexus] bisbers:
27 Aug Nightly is out - MMS is still broken and still can't get My Phone Number. Looks like 18th is where it's at for now.

(Dirty flashed in case it might matter).
[Samsung Galaxy Nexus] JeeperDon:
See, this is why the CM dev team can sometimes suck. Do we ants on a hill here in toroland have any idea that the CM devs even know we have an issue, and we've even helped them by figuring out what it is, and it hasn't been fixed in the week since they broke it? :mad:
[Samsung Galaxy Nexus] RaiderX29:
I spoke with our maintainer late yesterday and he's looking into it. These are nightlies, you have to expect things not to work at times. We're fortunate that our maintainer is more responsive than some others I've seen in the past.
[Samsung Galaxy Nexus] RaiderX29:
Just a quick update. It's definitely an issue with telephony and it looks like its related to this commit: http://review.cyanogenmod.org/#/c/48680/

I also noticed d2vzw is experiencing data switching issues which have been reported on toro as well. They're asking for a revert of the above commit here: http://review.cyanogenmod.org/#/c/48873/

I passed all this along to our maintainer. He's going to confirm that this fixes all the issues and then push a revert or fix, whichever is most appropriate.
[Samsung Galaxy Nexus] johnhimm:
Just because bugs aren't ironed out in a few days does not mean the CM Dev team sucks. Can you do better? These people are doing this in their spare time for the love of it. If the current ROM doesn't meet your needs go back to 10.1.2
[Samsung Galaxy Nexus] bisbers:
Completely agree. I've been running nightlies almost consistently since cm6? (whatever was first available for D-Inc, 3+ years ago). In that time, I've only had a small handful of issues that have impacted functionality. This issue has taken longer to fix than most, but at least we have a recent build to go back to. It's a risk you take when you run a nightly build.
[Samsung Galaxy Nexus] greyhd:
I also agree. There is a reason why they are called nightlies and some things should be expected to be broken. I went back to 0819 and MMS works, but I will update the ROM as soon as the MMS issue is fixed. There are other ROMs you can use and run as a DD.
[Samsung Galaxy Nexus] mark manning:
I don't post in here often but this seemed to warrant a response

That sounds awfully entitled. You seem to forget people do this for fun and out of the kindness of their hearts. As the others have said remember you are using a nightly build. Basically an ROM that is built automatically. Things will be broke especially this early in the build stage of a ROM. Lots and lots of work is being done behinds the scenes to bring and add new ideas, take away old ideas, and further develop existing ideas.

https://plus.google.com/100275307499530023476/posts/ABDA7xSdZcx

Be glade you have a nexus and that the nightlies are as stable as they are. If you want a stable ROM go download the stable version and quit using the daily alpha/beta ROM. I remember a few years ago it was a comment very similar to this that made Steve close the cm5 thread and leave XDA....
[Samsung Galaxy Nexus] bill.allrobots.org:
Obviously a new feature to encourage sharing more pictures... just add a picture to every text. ;)

Honestly though that's a weird problem. I thought if SMS was broken, it would take MMS with it. I rarely use either, so I was mainly shooting for reliable data, but a test SMS failed for me too. Obviously this is not a good long-term solution. ;)
[Samsung Galaxy Nexus] mouf32:
Strange... I dirty flashed the 27th and my SMS works.... So far.
[Samsung Galaxy Nexus] johnhimm:
The 08/27 nightly build has worked the best for me so far tho I am not sure on MMS, since I do not use that.
[Samsung Galaxy Nexus] JeeperDon:
Ok, so I agree I was probably a bit harsh. Between the lines on my post was that the communication with the CM team does not appear to be two way. There are quite a few popular forums, and each one with a huge quantity of specific phone foruii. Thats a huge number of 'Official CM Nightly' threads, way too many for the actual coders to watch. So, I meant does anyone there even know the 'no phone number' problem exists on a toro? Having 'a guy here who knows someone' isn't a valid path for information, in my opinion.

I've been with CM a long time and do appreciate the work and effort. Notice my original comment that hit the fan here did say 'can sometimes suck', and the rest of the post was only related to the communication path, not the work. Sorry if I ruffled feathers, just not used to CM nightlies having anything broken at all, let alone for a week.
[Samsung Galaxy Nexus] RaiderX29:
CyanogenMod is very clear on who the maintainer is for every device, if you have an issue, you can, as I did, contact them directly through many different channels. The maintainers for each device cannot monitor every single post on each of the forums out there for their build and device.

As for the current issue, our maintainer is bisecting the issue with telephony and will hopefully push a fix soon. If I hear when that is, I'll certainly pass it along.
[Samsung Galaxy Nexus] silfa718:
who is our maintainer?
[Samsung Galaxy Nexus] greyhd:
0828 is up and the change log states telephony fix with mms
[Samsung Galaxy Nexus] Diablohtr:
I am on 8/28 - SMS working, MMS broken. I did a dirty flash though.
[Samsung Galaxy Nexus] ashclepdia:
i thought CM has an "official bugreporting" site?

and if someone finds a way to fix it in source, cant they push that to be reviewed and added in?
[Samsung Galaxy Nexus] johnhimm:
I am not seeing an 8/28 build yet for toro, only an 8/27.
[Samsung Galaxy Nexus] jaredsleboeuf:
Same.
[Samsung Galaxy Nexus] Diablohtr:
Oops I am on the Euroskank version - sorry guys.
[Samsung Galaxy Nexus] atrophis:
How did you find that? I didn't see it get built on jenkins and its not listed on get.cm.
[Samsung Galaxy Nexus] greyhd:
Fitsnugly of cm has 828 build up
[Samsung Galaxy Nexus] bisbers:
In fact Jenkins looks stuck, had a few failures today and seems like he gave up.

http://jenkins.cyanogenmod.com/job/android/
[Samsung Galaxy Nexus] greyhd:
Here is euroskank's website

http://fitsnugly.euroskank.com/?rom=cm10&device=toro
[Samsung Galaxy Nexus] bill.allrobots.org:
Does not seem to have fixed the "Unknown phone number, PRL, etc" problem (or therefore presumably the MMS problem).
[Samsung Galaxy Nexus] greyhd:
I haven't flashed the latest since I am at work, but I was going to at home. I guess I will stay on 0819 since MMS is still broken.
[Samsung Galaxy Nexus] atrophis:
OK. That's a "cherry pick" build and not the official CM nightly. Thanks.
[Samsung Galaxy Nexus] rmgibbs1861:
Cyanogenmod-10-1-3-rc1

FYI : http://www.cyanogenmod.org/blog/cyanogenmod-10-1-3-rc1

:)

Rick
[Samsung Galaxy Nexus] aeidian:
Does 8-19 have mms working?
[Samsung Galaxy Nexus] bill.allrobots.org:
There was no official 20130819, but 20130818 worked and 20130821 (the next build) was the first to have the commits that broke MMS etc. It looks like fitsnugly 08-19 was built before the commits in question, so it should work like official 20130818 (i.e., it should work).
[Samsung Galaxy Nexus] greyhd:
Yes. It's a cherry pick from euroskank's rom
[Samsung Galaxy Nexus] ExodusC:
I don't even care about MMS functionality, honestly.

I'm hoping that we don't have to wait for the (possibly never coming) official 4.3 OTA to fix the random data drops.
[Samsung Galaxy Nexus] Enter The Nexus:
apps + adb...

---------- Post added at 09:09 PM ---------- Previous post was at 09:09 PM ----------

We might get it! Binaries were released yesterday...
[Samsung Galaxy Nexus] aeidian:
get.cm only lists 10.2 nightlies starting with 0821. I'm not sure what 0818 you're referring to.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
If you have the goo manager app you can look it up on there

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] bill.allrobots.org:
Just because it's no longer there doesn't mean it didn't exist. CM didn't come into existence on 2013 Aug 21.

You can find old builds here: http://goo.im/devs/cm/toro/nightly/
[Samsung Galaxy Nexus] JohnKuczek:
MMS Issues

I had been having the MMS not sending or receiving issue and moved to PA3.99, and it followed me there. Started looking for other causes, and I think I found my issue. While I haven't come back to CM10.2 yet, it may be worth a try for those of you with the issue to uninstall any 3rd party texting apps that work with your VZW number...

I had been using Verizon Messages and uninstalled it late yesterday... as soon as I did that I could send and receive MMS again. For the moment, I'm going to assume that something in that app is not playing well with 4.3 ROMs.
[Samsung Galaxy Nexus] jaredsleboeuf:
Would you mind sharing where you're getting the info on new binaries? (I'm not seeing anything about a new date, so I'm just curious).
[Samsung Galaxy Nexus] gpzbc:
Weird. I am currently on PA 3.99, waiting for the bugs to be ironed out of CM 10.2, and MMS is working for me. By the way, I am using Chomp.
[Samsung Galaxy Nexus] sheeksta:
euroskank vs cm10

i was using jellybro from euroskank until yesterday and just switched to cm10 nightly 9-4-2012 and notice the clock's stopwatch and timer features are not included. is it not a CM feature?
[Samsung Galaxy Nexus] swyecso:
You have to download the Verizon Login App and connect to that over mobile data first (disable wifi)

http://goo.gl/kPvDB
[Samsung Galaxy Nexus] jimlange:
That's one of Euroskank's cherry picks that hasn't been merged yet. I'm also running jellybro and have experienced some bugs with the countdown timer, so I think it's not quite ready for release.
[Samsung Galaxy Nexus] BrotherG:
Anyone having their notification alert cut off short when using the pop up messaging option?
[Samsung Galaxy Nexus] johnhimm:
Anyone running the 9/4 build with any comments on the battery over the last couple of builds? And what Kernel are you running?
[Samsung Galaxy Nexus] bikeboy:
yes, the tone is down-cut for some reason
[Samsung Galaxy Nexus] Kennnny1:
Interesting that some of you are reporting poor battery life - I'm getting the best life I've had since having the phone. About 4 hours screen on time on 4g.

Also, no random reboots here.
[Samsung Galaxy Nexus] anotherdroid:
we ignore the claims of bad battery life ;)
[Samsung Galaxy Nexus] thefatalepic:
Lol, funny because I've come to learn to ignore the claims of good battery life!

EDIT: Now that I think of it, I ignore all claims of battery life.
[Samsung Galaxy Nexus] Lw00d:
i was wondering the same thing. i check the change log website everyday hoping they post it.. do you think they will even post something like that??
[Samsung Galaxy Nexus] myriad46:
JRO03L is what the build info says.
[Samsung Galaxy Nexus] k_nivesout:
JRO03L is the latest AOSP source. You can't build JRO03O as of yet, the roms that are JRO03O are made from the VZW/Google leaked test build.
[Samsung Galaxy Nexus] norm12:
Not to be "that guy" but I've been running the first CM10 nightly 8-18 with no issues, stellar battery life, and no reboots. Yes, I use my phone and yes the 4g is lovely. This thread is making me happy I've stayed on that version----any noticeable improvements since it was released?

Sent by Logo the turtle
[Samsung Galaxy Nexus] thefatalepic:
The early builds were great for me, too. I know Torch was added. And battery life isn't bad (although I always flash leankernel). I think it is a little more responsive now than it was before.
[Samsung Galaxy Nexus] gabbar21:
Galary Sync

Does anyone know how to make the Galary app sync with Picasa online web albums? The sync is simply not working after installing the latest Gapps (7.26.2012).
[Samsung Galaxy Nexus] NookMonkey:
Try flashing formula84's gapps-jb-20120831-JRO03O-Formula84-PicSync:

http://rootzwiki.com/topic/31532-gapps-411-424425-jro03o-gapps-package-831/
[Samsung Galaxy Nexus] NickSaul:
Quick question.

Do I need to reset wallet every time I flash a new nightly build?

I wipe cache & dalvik.

Then flash rom and gapps.

Thanks.
[Samsung Galaxy Nexus] thefatalepic:
No. Before there was some issue with bricking the "secure element" but I've flashed over and over again and have had no issues. I've wiped and reinstalled the Wallet app and it just re-registers my cards when I click on them.
[Samsung Galaxy Nexus] NickSaul:
Thank you!
[Samsung Galaxy Nexus] bikeboy:
Manage Wallet devices online: https://wallet.google.com/manage/#devices:

( I had two.)
[Samsung Galaxy Nexus] bill.allrobots.org:
https://developers.google.com/android/nexus/drivers#torojwr66v
[Samsung Galaxy Nexus] jlvlawrence:
I also switched over to PA. No mms issues on that rom. I'm gonna do a clean flash of the Euroskank build when I get home and see if the mms problem exits. Supposedly those builds have the mms fix cherry picked.
[Samsung Galaxy Nexus] greyhd:
I did a clean install on 828 and mms is still broken.
[Samsung Galaxy Nexus] modernbummer:
Team Vanir seems to have figured out an MMS fix:

http://rootzwiki.com/index.php?/topic/38860-[ROM]-VANIR-(v4.2.2.1-[JB-4.2.2][3/19])-(Yeah,-it's-got-a-HEMI)#entry1415882

I can confirm that it's working.
[Samsung Galaxy Nexus] greyhd:
Isn't that a 4.2 Rom?
[Samsung Galaxy Nexus] modernbummer:
No. They were on 4.3 before most.
[Samsung Galaxy Nexus] j0hnnyth3f0x:
They need to update their title then... 3/19 date and JB 4.2.2....

Sent from my Galaxy Nexus
[Samsung Galaxy Nexus] greyhd:
Their downloads are all 4.2 in the titles.
[Samsung Galaxy Nexus] jaredsleboeuf:
They appear to have a download section for 4.3 as well, but I haven't gone through every page in that thread to find where, if anywhere, it's posted:

http://www.emccann.net/nuclearmistake/VanirAOSPNightlies/toro/
[Samsung Galaxy Nexus] modernbummer:
Didn't mean to highjack this thread. Just wanted to point out a potential fix.
[Samsung Galaxy Nexus] greyhd:
Thanks for the suggestion, I will give it a try tonight.
[Samsung Galaxy Nexus] bill.allrobots.org:
Someone mentioned that they have something in the changelog related to MMS, but it's not THE fix (i.e., it's not the one we're waiting for---MMS is still broken there, too).

Another poster pointed this out before me, but I think the problem pretty well "figured out" at this point, as evidenced by the waiting commit here to revert the change that broke it (this one). It's causing issues on d2vzw, etc, as well. I think it's not a matter of figuring out what broke it, but rather how to fix it again without regressing on the original problem the commit was made to solve. I'm not a CM dev, but this is how it seems to me.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Textra seems to handle MMS just fine. Guess I'll use that until the stock app is fixed.
[Samsung Galaxy Nexus] bill.allrobots.org:
FYI: 20130829 is up. As those watching the logs probably know, the network issues persist.
[Samsung Galaxy Nexus] Terrell1433:
Textra doesn't work for me
[Samsung Galaxy Nexus] Royal2000H:
I was looking to upgrade my old AOKP (jb-mr1-build-5) either to a new AOKP or CM.

Is 10.2 too unstable right now? I see people are having issues with MMS... any other issues?
[Samsung Galaxy Nexus] JeeperDon:
You can also read that the 8/18 version is fine, everything works.

Actually, to all here, CM 'just works' out the door at pretty much any nightly release. In all my time on CM, I never saw a real need to go to the next nightly other than just "because it's there". Has anyone stepping through the nightlies now, those that don't care about the 8/21+ Phn#/MMS issues really notice actual improvements day to day? I'm happy to stay on my completely functional 8/18 until the first Stable comes out, though I'll probably be teased by the M release.
[Samsung Galaxy Nexus] bill.allrobots.org:
Network can be really flaky in general... if you're not prepared to pull logs and help debug, my opinion is it's not the time to jump on 10.2 nightlies, at least until these issues are ironed out. Obviously I don't know your background, but if you haven't upgraded in that long, I'm going to guess you're not the type of user that rides the bleeding edge and can debug issues.

That said, cm 10.1.3 RC 1 was just released, and it's quite happy and stable, from what I saw of it.

Edit:

As noted here, the 20130818 build did not have the current issues, so you might be alright with that.
[Samsung Galaxy Nexus] Royal2000H:
Thanks for both of your replies. While I have the technical ability to try to debug issues, I've become very busy lately and don't have the time or patience to (hence my months old rom). So I am trying to go stable rather than bleeding edge, but since 4.3 is out, it seems silly to put on a 4.2.2 ROM since I'll have to / want to upgrade soon anyway.

20130818 isn't on get.cm, do you know where I can get it? I understand the MMS issues aren't there but are the data drops/network issues there?
[Samsung Galaxy Nexus] jaredsleboeuf:
Seconded. I jump between a few ROMs for testing, issue-tracking, the fun of it, etc., but cm 10.1.3 RC 1 is now my daily driver and seems to be a natural follow-up for either 10.1.2 nightlies or stable. Though it did just drop, I have been using it since and haven't had a single issue pop up yet.
[Samsung Galaxy Nexus] bisbers:
http://goo.im/devs/cm/toro/nightly/
[Samsung Galaxy Nexus] bill.allrobots.org:
Update: it looks like the other commits might not be the cause of network issues after all. This just appeared:

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

Seems reasonable, based on the logs I gathered. After the "break," the IccCardProxy is clearly being set to UMTS. This was not the case in the "before" log.
[Samsung Galaxy Nexus] mouf32:
Royal, I have yet to have any data issues on my Gnex. I have been dirty flashing since I did the first intial clean install of 4.3

I do have the MMS issues though, but I just unchecked auto download so I can atleast see who is sending them now.
[Samsung Galaxy Nexus] markcyst:
Never had any data issues here either, only been dirty flashing.
[Samsung Galaxy Nexus] underwaterjr:
Have you tried to cherry pick it and build to see if this commit fixes the problem?
[Samsung Galaxy Nexus] RaiderX29:
Sorry forgot to update. What caused the problem was this commit: http://review.cyanogenmod.org/#/c/48620/ The revert of the revert of the revert.

Instead of piling on and reverting once more on the qualcomm radio patch, they submitted a fix that will address the toro issue separately which is the commit you listed: http://review.cyanogenmod.org/#/c/49342/

Hopefully a merge is not too far off now.
[Samsung Galaxy Nexus] demlv:
As of today I'm on 10.1.3 RC1. I expect I will soon take the plunge and move to 10.2. But before I do, I'm interested in knowing how things went for anyone who dirty flashed CM 10.2 on top of a working CM 10.1 rom.

Any successes?

Any nightmares?
[Samsung Galaxy Nexus] carpenter311:
Don't flash anything after 8/18/13 if you want working MMS. Other than that all is good.

Sent from my bathroom downstairs.
[Samsung Galaxy Nexus] bill.allrobots.org:
Just be sure to backup first---you can't downgrade in place without breaking things.
[Samsung Galaxy Nexus] RaiderX29:
Here's the commit for the MMS fix for toro. Cross your fingers that it gets rebased and merged soon. Once you see this in the nightly everything should be gravy.

http://review.cyanogenmod.org/#/c/49346/
[Samsung Galaxy Nexus] atrophis:
Does 10.1.3 RC1 have the WiFi connect/disconnect support for profiles merged? I know 10.1.2 does not, but what hoping 10.1.3 will have it.
[Samsung Galaxy Nexus] JeeperDon:
I just did a dirty flash of 8/30 over my 8/18. The first thing I checked was the Settings/About/Status phone number. Nope, still says unknown. My 8/18 is restoring as I type.
[Samsung Galaxy Nexus] markcyst:
see:
[Samsung Galaxy Nexus] blackhand1001:
Not related to the MMS issue but adding wifi.supplicant_scan_interval=30

To my build.prop fixed the WiFi not auto connecting issue. I noticed this line was on my nexus 7 and added it to my galaxy nexus's build.prop. in think googles default is 15 but I think 30 is the best compromise.

Edit: nevermind. After deep sleep it seems to be back to not auto connecting. Will try it again with 15.
[Samsung Galaxy Nexus] mouf32:
Mine was a train wreck.... I had it for about an hour when I tried to dirty flash from 10.1 to 10.2... I restored a back up and did a full wipe/clean install of 10.2 later in the day and haven't had any issues. Make sure you get the correct GAPPS.
[Samsung Galaxy Nexus] greyhd:
Did the mms get fixed on 0830?
[Samsung Galaxy Nexus] jlvlawrence:
The newest Euroskank build has working mms and phone status.
[Samsung Galaxy Nexus] Whompy:
The fix was just merged and will be included in tomorrow's nightly.
[Samsung Galaxy Nexus] PDR447:
any way to pull the file from the euroskank build and "self patch" the 8/30 nightly? anyone care to point me in a direction of where the patch is in the compiled builds? I don't mind being a guinea pig.
[Samsung Galaxy Nexus] johnhimm:
Don't kill me, just asking-

What's the fuss on MMS? I think I have sent 3 in 3 years. Everyone has a smartphone nowadays so emailing a photo works just as well, without carrier fees.
[Samsung Galaxy Nexus] ExodusC:
Hopefully this next nightly will not only fix MMS, but the data drops some of us are experiencing. Maybe they're the same issue. I think it has to do with tower switching, as I only really get it when I'm traveling.

Not to mention 3G data has not worked even once since I've been on 10.2, I have to use LTE or I don't get an actual data connection.
[Samsung Galaxy Nexus] bisbers:
A few pages ago someone tried to do that and it caused a few other issues (IIRC, you'll need to pull /system/app/TelephonyProvider.apk and /system/app/Telephony-provider.jar).

The merge missed today's build by a few hrs, but it's already waiting for the next one. I don't think there's any way to request a re-compile for today. http://changelog.bbqdroid.org/#/toro/next
[Samsung Galaxy Nexus] PDR447:
NP for asking. my motivation is that I have friends that use it. Group MMS is one example. it's not only pictures. and just guessing, most people are unlimited mms/sms plans these days. so charges are moot.

hmm, I'll give it a shot. that's what backups are for right?
[Samsung Galaxy Nexus] bisbers:
Group messaging. It seems like some of these guys have friends and many people use group messaging, which is just a repurposing of MMS. I don't fall into this category, but some people think it's related to signal issues, a few (incl myself) had Messaging eating the battery, and lastly, it bothers me knowing that it's broken.
[Samsung Galaxy Nexus] PDR447:
ya, for better or worse the iphone is popular... can't deny that. And many iphone users(at least that I know) have become accustom to group messaging(uses the MMS system). Don't get me wrong, I find it annoying sometimes getting everyones responses when I have no interest in the conversation. But on the other side, sometimes I need to be a part of those conversations as they can pertain to work.
[Samsung Galaxy Nexus] bisbers:
Yup. The patch suggests you might only need /system/framework/telephony-common.jar, perhaps put them on one at a time to see if one makes the difference.
[Samsung Galaxy Nexus] xI mEzMeRiZe Ix:
Different strokes for different folks. Some people just don't use email for conversing with friends.
[Samsung Galaxy Nexus] bisbers:
If I had friends, I'd mms them. I want this fixed, just in case the opportunity comes up.
[Samsung Galaxy Nexus] PDR447:
woohoo! replaced both the jar and the apk and SMS and MMS are fully functional. Was too impatient to try one at a time... Phone number is present in about phone.

Now to see about the LTE/EVDO hand offs.