yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] bmeek:
A somewhat off-topic question for you mastamoon: does your rom have a modified cmupdater app that pulls updates from your nightlies, or does it still aim at the official cm distribution?

Thanks!
[Verizon Samsung Galaxy S III] mastamoon:
No I haven't touched the cm updater. I use romdashboard to notify of updates. Works pretty well.
[Verizon Samsung Galaxy S III] Aquila76:
I'm getting this issue on stock, too. I'll have full bars, but data fails to connect and I get drops. Wonder if there's still some latent issues with the MF1 modem or maybe VZs network is getting over saturated.
[Verizon Samsung Galaxy S III] rockingondrums:
It could be an increase in the subscriber base. I got on LTE pretty early and enjoyed 20-30/15-20 speeds for awhile, but now it's like 7-10 or 15 at the right hours. I'm also using more data so they may be throttling me at times. OTOH, I tried out my boss's AT&T LTE the day the iPhone 5 came out, and it was still slower than vzw. I'm thankful for that because I'm never going to AT&T again because of a horrendous customer service incident I had.
[Verizon Samsung Galaxy S III] airmaxx23:
Is the cell signal fix in the 7/22 nightly?
[Verizon Samsung Galaxy S III] Chris123NT:
yeah it is :good:
[Verizon Samsung Galaxy S III] bmeek:
Is this a kernel-level fix? IOW, will custom kernels need to be updated to include or support this cell signal fix?
[Verizon Samsung Galaxy S III] mastamoon:
Framework/rom fix.
[Verizon Samsung Galaxy S III] zachf714:
Is MMS broken ?
[Verizon Samsung Galaxy S III] MG386:
not here, works fine.
[Verizon Samsung Galaxy S III] jasoncallahan:
running 7/22 nightly. just confirmed MMS is working.
[Verizon Samsung Galaxy S III] zachf714:
It was just my house when I left I could send one :) thank you
[Verizon Samsung Galaxy S III] rhplusa10:
I've kinda figured out the problem of ffc (front facing camera) of 3rd app like instagram, facebook, or cerberus.

I rolled back to MB1 firmware, and flash old kernels before 5/17 released.

Camera works fine!

5/17 KT kernel, 5/19 BMS kernel or something like that.

but I faced another issue of streaming video with that combination.

youtube does not work at all. :(

mobile youtube web does not work either.

I wish this camera problem is resolved soon.
[Verizon Samsung Galaxy S III] ayush20m:
ATT use CS fallback. Although it should not be responsible for call drop, that's the only link I can think between your 4G tower upgrade and your voice call drop.
[Verizon Samsung Galaxy S III] SilverFox66:
You only have so much power available at a rural tower, to drive the antennas, right? So, they add 4G/LTE antenna, wouldnt it be feasible to rob power from 2G/3G to power the 4G/LTE.... killing the distance/strength of the signal?

whatever it was, they knew they did it, but wouldnt admit it.. because they knew they lose too many customers. Like I said, they strung me along for 2 months of that crap.
[Verizon Samsung Galaxy S III] WhammyDroid:
With the new voice+ functionality, I am noticing Google Plus is not issuing notifications. I actually have to go into the app to see if I have any text/voicemail messages.
[Verizon Samsung Galaxy S III] JohnnyTToxic:
You should be getting your text notifications through the default SMS application if you've enabled your voice account in Voice+ and you will not get any further notifications from google voice. That appears to be by design, otherwise you'd get two notifications for each text, one from google voice and one from your messaging app.

Did you disable the default messaging app or anything?

I did notice that it took a while for the messages to migrate properly into the SMS default app.
[Verizon Samsung Galaxy S III] :
I'm not able to send/receive messages at all... Maybe I'm missing something? I did verify it is the voice+ app, after enabling my Google account it breaks MMS/SMS but when I disable it, I am able to send messages again. Is there something I should be doing after I enable my account?
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Maybe reboot and when it comes back, send a text message through the default SMS application. No need to ever open google voice app again, you just need to leave it installed.

Since this is the dev forum, you should move this over to http://xdaforums.com/showthread.php?t=2071252&page=190 which is probably more appropriate for this type of question.
[Verizon Samsung Galaxy S III] :
Yea I tried that before posting... Nothing changed though, although I got a notification saying to activate voice, even though it already was.

Aside from that, the only reason I posted in this thread was because someone reported MMS being broken and another person was also having problems with voice+. Since they posted here and I was having the same issues I was hoping they might have found a resolution...
[Verizon Samsung Galaxy S III] Srambo217:
Any tricks to get this ROM to stream audio via Bluetooth to my HMDX Jam Wireless Speaker? I cn stream audio to other Bluetooth devices but not this one for some reason.

Edit: it's working now. Very odd. Hopefully it stays this way!
[Verizon Samsung Galaxy S III] airmaxx23:
I've had an issue on the last few builds where the Play Store is gone once I'm done installing and reboot. I have to flash GAPPS to get it back,is anyone else experiencing this?
[Verizon Samsung Galaxy S III] Chris123NT:
Anybody else seeing an issue where incoming calls don't have any audio until you toggle speaker phone? Outgoing calls work fine.
[Verizon Samsung Galaxy S III] Phush:
I'm HBG too! Well, 5 minutes outside of the city. :good:
[Verizon Samsung Galaxy S III] goldsmitht:
Airplane mode works fine for me both thru the power menu and the Quick Toggle in the pulldown[/QUOTE]

i can go through the power menu, and system menu and toggle it on and off, however, when i toggle using wigit in pull down -- and i may be getting them backwards, the little widget - it isn't on big widget page -- it doesn't do anything.

:confused:
[Verizon Samsung Galaxy S III] NeoMagus:
Have you tried re-adding the airplane mode toggle by going Settings>System>Quick Settings panel>Tiles and Layout and then deleting and re-adding the airplane mode toggle is that the one youre talking about that might help

Same here no way Id live in the city (esp with the shootout in Hall Manor just what yesterday LOL)
[Verizon Samsung Galaxy S III] ming3r:
Where did you get the 12-19? I'm seeing only a 12-18 here: http://goo.im/devs/aeroevan/cm10.1/
[Verizon Samsung Galaxy S III] Polymira:
Likely IRC.
[Verizon Samsung Galaxy S III] Rixanu:
This is probably gonna sound stupid, but is anyone having issues with gmail notifications causing vibration? I have vibrate unchecked in gmail, but new emails still cause my phone to vibrate. This started happening right after I updated to the unofficial 12/19 with the 12/12 gapps.
[Verizon Samsung Galaxy S III] invisiblek:
This is what I love about xda

Here in the DEVELOPER thread, 23 pages of mindless chit-chat about things that are obviously not working

Go to general, this thread is pointless

Its the same "oh, data doesn't work, anyone have a fix?"

YES, IF YOU READ THE OTHER 22 PAGES OF MINDLESS CHIT CHAT YOU'D KNOW THAT

Now when someone comes along and wants to flash CM10.1 (after it gets to a better state) they'll have to sift through at MINIMUM 23 pages of mindless bull**** to find out anything worthwhile.

This rom should never have been posted, as it was not ready and an accident that it was built in the first place.

Stick to unofficials

Mods, please delete this thread or move it or something, its 100% pointless

Also - we are going to be off the official nightly circulation soon for 10.1, at least until we have data merged properly
[Verizon Samsung Galaxy S III] M Diddy:
Thank you!

Unbelievable, all the mindless drivel in this thread. My head actually hurts reading it. :(
[Verizon Samsung Galaxy S III] airmaxx23:
...says the person cluttering up the thread even more....which I have now done also. :silly:
[Verizon Samsung Galaxy S III] will.bates94:
Have you not seen the offical 10.0 thread? its HUNDREDS of pages long, lots of it containing the same amount of material.
[Verizon Samsung Galaxy S III] Phush:
Why would they have to sift through anything? The OP has all the info they need about the official build.
[Verizon Samsung Galaxy S III] M Diddy:
And yet no one reads it and the same questions get asked over and over. :rolleyes:

You guys do realize that Invisiblek is one of the main devs on the CM team for the d2vzw, right? He knows what's he's talking about.
[Verizon Samsung Galaxy S III] NeoMagus:
Exactly some of these guys must not know who ek is. The point I agree with it is the same questions over and over that if some just took the time to actually read the OP, much less the thread it wouldn't be bigger than it needs to be. Just my 2 cents
[Verizon Samsung Galaxy S III] will.bates94:
yes we do. And thats their fault if they dont read the OP, therefore leads us to tell them to go back and read...
[Verizon Samsung Galaxy S III] Phush:
I'm sure he does, but will deleting the thread and starting a new one teach people to read?
[Verizon Samsung Galaxy S III] dpaine88:
I really dont find this much different than any other ROM thread I've been apart of. Kinda just comes with the territory that there will be a lot of stupid people.
[Verizon Samsung Galaxy S III] illyfilly:
How do you do that?
[Verizon Samsung Galaxy S III] Restola:
I sent a PM to invisiblek asking what he'd like me to do with this thread. As I said in the OP this isn't my ROM! But since the last CM thread was created by a member I figured I'd toss it up and do my best to keep the OP up to date as people ran into so many problems with the 12/18 nightly.

Waiting to hear back from invisiblek and then I'll work with the xda mods to delete or move this thread. I really feel like it's not my decision what to do here. Hopefully someone associated with the project can manage a new thread!

Thanks and hope I didn't step on anyone's toes!!

/edit The thread is staying. I'll do my best to keep the op up to date!
[Verizon Samsung Galaxy S III] motempo:
Yea, volume is definitely louder on all notifications. Distorts the sound when it is turned all the way up as well.
[Verizon Samsung Galaxy S III] peaceofpi:
ugh - anyone else getting the SMS limit popup?
[Verizon Samsung Galaxy S III] airmaxx23:
Mine is working fine on the newest nightly. I just can't figure out why I've been losing the Play Store when flashing the last few nightlies.
[Verizon Samsung Galaxy S III] NegativeOne:
Is anyone experiencing broken gps/location on the last few builds? My 7/11 worked, but 7/22 and 7/23 put me somewhere near San Francisco / Oakland. (I live in Boston)
[Verizon Samsung Galaxy S III] airmaxx23:
I'm on the 7/24 and the GPS is working properly for me.
[Verizon Samsung Galaxy S III] NegativeOne:
Weird. If I flash back to 7/11, it works again, but the newer builds screw it up. Anyone have any suggestions for trying to reset it in some way?
[Verizon Samsung Galaxy S III] WestOkid:
Happened to me too but that was when I was running latest stable version. I am not running CM right now so can't speak on nightly.
[Verizon Samsung Galaxy S III] soohyunk83:
I have a similar issue with my GPS.

It seems to take a lot longer to find my location through GPS.

I'm on 7/23 as well.

Have you tried 7/24?
[Verizon Samsung Galaxy S III] NegativeOne:
I haven't. Don't like flashing untested builds during the day while I'm at work. Today's changelog didn't indicate that anything should have changed in this respect. I do not think it is related to GPS really, but to the network location provider, which assists GPS, or can prevent it from locking.

I'm guessing if network location says you're in CA, but GPS is trying to lock on Boston, GPS will fail to lock (by the sound of it). The network based location that Google Now uses is busted too, so..

Let me know if you do try today's build and whether it works. The question is going to be how far back this thing broke, and why it's not broken for everyone.
[Verizon Samsung Galaxy S III] MG386:
I don't have that, but on incoming calls with BT headset on, BT disconnects. Outgoing calls are fine though.
[Verizon Samsung Galaxy S III] Jackdog89:
I'm seeing the same thing. GPS and WIFI location work fine for me, but mobile network location is way off. I'm getting weather from San Marcos, TX but I'm in Phoenix, AZ (not connected to WiFi here at work).

I know the 7/18 build worked fine. And it may be broken for others, however, you won't notice it unless your GPS is turned off and you're not connected to Wifi.
[Verizon Samsung Galaxy S III] airmaxx23:
I just asked for the weather forecast with Google Now with the GPS and WiFi off and my location was correct, I'm on the 7/24 build.
[Verizon Samsung Galaxy S III] NegativeOne:
Was it broken on 7/23 and lower?
[Verizon Samsung Galaxy S III] Jackdog89:
For me it worked fine after I turned off my Wifi and GPS, until I moved from that location. On my way to work google maps and weather bug had me all over the place until I turned my GPS back on.
[Verizon Samsung Galaxy S III] NegativeOne:
[MENTION=2488766]Jackdog89[/MENTION] - on 7/24?
[Verizon Samsung Galaxy S III] Droid0351:
What baseband do I need to be to flash this for the camera to work?
[Verizon Samsung Galaxy S III] Jackdog89:
On 7/23, I'm checking 7/24 now.

Edit. I have the same issue on 7/24 too.
[Verizon Samsung Galaxy S III] airmaxx23:
MF1.
[Verizon Samsung Galaxy S III] Droid0351:
Ok, thanks
[Verizon Samsung Galaxy S III] NegativeOne:
I heard MF1 kind of sucks though.
[Verizon Samsung Galaxy S III] Droid0351:
What baseband for cm10?
[Verizon Samsung Galaxy S III] sanjsrik:
I'm not even using a bluetooth headset and the latest 7/24 nightly I'm having calls NOT answering on my side. People call, I can hear absolutely nothing on my side. I have to call them back. I'm rolling back to 7/22 nightly. I'm wondering if it's being rerouted to google+ even if I told it not to as I never opted in to use it?
[Verizon Samsung Galaxy S III] NegativeOne:
Guess we gotta figure out what the latest working build is and file a Jira bug.
[Verizon Samsung Galaxy S III] mastamoon:
Should be fixed in tonight's nightly. Fixed in my unofficial right now if you want it.
[Verizon Samsung Galaxy S III] Jackdog89:
Yeah, I was trying to figure it out at work but had an audit today. I had the same problem on as far back as 7/18, but haven't had a chance to check 7/17. Now, it looks like the 7/19 nightlies and older have been removed.

Edit; Strange, I just tried 7/18 & 7/24 at home and can't reproduce the problem again.
[Verizon Samsung Galaxy S III] NegativeOne:
might be this: http://review.cyanogenmod.org/#/c/45565/

mastamoon found that.
[Verizon Samsung Galaxy S III] Srambo217:
I certainly hope it's the cloudy weather and not this ROM, but my signal has been abysmal. I can't even preview images in Falcon Pro or Gmail.

http://www.imgur.com/7BK6L2f.png

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] FrankyFiggz27:
Yea I've been having this issue badly too. Been the same on every aosp ROM for this phone. I tried beans ROM last night and the signal became really strong with lte in the exact same spots where I get 1 bar and not even 3g on aosp. Just hard to leave the aosp look behind... But I had this phone running literally right next to my vzw note 2 with carbon and my phone had perfect reception and lte while this phone had barely a signal on cm and liquid and carbon. Even upgraded to mf1. Is this a known issue? Anyone have an idea how to fix? I'd really hate to leave this phone on boring old tw.
[Verizon Samsung Galaxy S III] buschbarber:
My mobile network type switches between lte13 and ehrpd14. I am not sure what that means or whether it has anything to do with the continuing dropped calls that ocurr in my home.
[Verizon Samsung Galaxy S III] Srambo217:
I didn't know we could run this with MF1 now and not have camera issues. Maybe I'll give that a try when I'm at work (when my signal is at it's worse).
[Verizon Samsung Galaxy S III] NegativeOne:
I think MF1 was pulled by Verizon. PEople are saying it's worse.
[Verizon Samsung Galaxy S III] zachf714:
No that was MD3 .. MF1 is as good as MB1
[Verizon Samsung Galaxy S III] kenbrownstone:
My phone is the same way. Asop ROMs are almost useless.I have to use TW just to get good signal. Glad that someone else is that way so I no I'm not crazy or screwing something up. But I too have thought about finding another phone.. It sucks cause there are a lot of asop roms
[Verizon Samsung Galaxy S III] Srambo217:
Flashed MF1 modem and I'm definitely getting a better signal opposed to yesterday. It's still only 2 bars but at least I can perform basic tasks.

I've never had great reception at work, streaming video is nearly impossible, but as long as I can use Falcon Pro and G+ I'm happy.

Galaxy SIII

My Podcast*-*http://bit.ly/WWSXbz

Twitter - http://bit.ly/VVAdb8
[Verizon Samsung Galaxy S III] DiGi91:
Also had the same issues, on TW no problems. Back on M.O.A.R after trying multiple AOSP ROMs.. I just kinda gave up on it.. Seems that whenever I need my phone to "just work" is when AOSP shows it's ugly little quirks
[Verizon Samsung Galaxy S III] jimmypop13:
I am on the June 29th build of cm10.1 and mb1 radio and am scared to leave it bc it's so stable. I haven't had a single issue. No reboots our freezes or signal problems or GPS problems. I love my phone so much more now. No screen flicker either. I've found as long as I leave the kernel alone, aosp roms work perfect on my phone. Are you formatting system when you go to aosp roms? That's all I can think of that could cause you a problem. Also I've found mb1 works better for me than mf1. Mf1 drops to 3g a lot but mb1 never does unless I'm inside certain buildings
[Verizon Samsung Galaxy S III] DiGi91:
I'm still on MB1 and of course I am formatting when switching to AOSP. I am in a very populated area (Boston) so can't blame it on spotty service or anything like that. TW has been the way to go. I have pretty much tried every AOSP ROM. I was on SlimBean before switching back to M.O.A.R due to BT issues. Like I said there always seems to be a quirk or two that makes me go back to TW.

And before anyone starts with the "devs do this for free" speech. I am grateful for all of the devs and great ROMs out there and the hard work they put into them but I will be sticking with TW until I either switch phones or hear of a 100% stable AOSP ROM.
[Verizon Samsung Galaxy S III] FrankyFiggz27:
Exactly. Same here. It'll seem like everything is fine... But then an MMS won't send. Or I'll find out i missed a bunch of SMS and MMS messages..and signal will fade and not give me any data until after a reboot. Very random stuff that simply doesn't happen on most phones with aosp ROMs. Damn shame. There's nothing else wrong with this phone. Moar is pretty good in the meantime tho. Thanks for letting me know its not just me.
[Verizon Samsung Galaxy S III] jimmypop13:
Hmm. I haven't had any problems like that. I have the 32gb model, I wonder if that could make a difference. I'm just sorry to hear your phone doesn't like aosp bc that's gotta suck that you have to use touchwiz and are stuck on 4.1.2 at the moment.
[Verizon Samsung Galaxy S III] mastamoon:
You guys complaining about "signal" should flash my unofficial. I've tweaked the perceived signal strength by messing with what bars are displayed when. More matches Touchwiz. Only in lte mode though.

Give it a shot and see it helps.
[Verizon Samsung Galaxy S III] arh2o:
Would you say the actual signal is comparable to TW on your unofficials? Obviously visual tweaks to signal strength mean absolutely nothing.
[Verizon Samsung Galaxy S III] mastamoon:
No way for me to really compare but I would say it's more placebo but as you know, placebo sometimes works wonders! :)
[Verizon Samsung Galaxy S III] buschbarber:
What do I need to do prior to flashing your ROM over my current ROM from this thread?
[Verizon Samsung Galaxy S III] MG386:
Yes the actual signal in dBm is same cm10.1/touchwiz. Like masta said, people see less bars and think signal is bad, its not really.
[Verizon Samsung Galaxy S III] mastamoon:
Nothing really. I suggest wiping caches and system, then flash rom and gapps to get the cleanest install without messing up anything else.
[Verizon Samsung Galaxy S III] buschbarber:
I don't worry about the number of bars or even the value of the signal strength. It is the constant dropped calls, in my home, that is frustrating.
[Verizon Samsung Galaxy S III] arh2o:
Well I just installed your unofficial and the bar signal strength is definitely higher. Getting maybe 3-4 bars where i would be getting 0-1 on the official. Data speed and actual loading web pages wise it seems to be about the same if not a bit better. GOTTA LOVE THE PLACEBO EFFECT! :highfive:
[Verizon Samsung Galaxy S III] Restola:
I installed the unofficial and it cured my hemorrhoids too!
[Verizon Samsung Galaxy S III] airmaxx23:
I accidentally hit the airplane mode toggle and since turning it back off I'm unable to get my cell signal to not be grey. I've cleared dalvik/cache, tried toggling airplane mode and nothing is bringing it back to normal so I can't connect to Google. Suggestions?

I tried dirty flashing the build I'm currently on and still nothing, I did end up having to flash GAPPS again because the Play Store was gone, again.
[Verizon Samsung Galaxy S III] mastamoon:
Check your mobile network settings.
[Verizon Samsung Galaxy S III] brockkk:
This happened to me too. I turned on airplane while on a plane and when I turned it back on I was stuck at roaming I have to go to mobile networks and change system select to home only (phone doesn't work when you do that) then connect to WiFi for a little then switch back to auto then change system select back to automatic and it works until I reboot. Then all over again.
[Verizon Samsung Galaxy S III] airmaxx23:
I always have mine set to "home only" and the phone always works, I've been doing it for years. I work about a mile from the Canadian border and it keeps me from getting notified about their towers. I got tired of messing with it and just restored a backup, I wanted to mess with my Chromecast instead.
[Verizon Samsung Galaxy S III] brockkk:
weird... it wont let me make calls when im in home only.
[Verizon Samsung Galaxy S III] Droid0351:
Does this have the center clock mod?
[Verizon Samsung Galaxy S III] sivarticus85:
No.
[Verizon Samsung Galaxy S III] Droid0351:
OK, thanks. I'm still on twz 4.1.2. It looks like I'm going to be flashing avatar.
[Verizon Samsung Galaxy S III] rhcreed:
Anyone using latest nightly? Any issues?
[Verizon Samsung Galaxy S III] ddggttff3:
As a nightly updater, last nights update has no issues for me.
[Verizon Samsung Galaxy S III] Hans5849:
I'm having problems with gps location. I'm near Chicago and it's telling me I'm by Pittsburgh.
[Verizon Samsung Galaxy S III] Aquila76:
I'm in Lowell, MA, and occasionally mine will toss me on a San Francisco Airport utility road. Honestly, it's been doing that since I started using CM 10.1 a few days ago (7/23 nightly). Toggling WiFi on/off or rebooting seems to fix it though.
[Verizon Samsung Galaxy S III] titanshadow:
Last time that happened to me, I had to go down the road 65 miles an hour on the freeway before it realized that I was right I actually was.
[Verizon Samsung Galaxy S III] Hans5849:
Oh, I was going about the same and that was no help. I'm on mastamoons 7/19 build now.
[Verizon Samsung Galaxy S III] russell5:
Im in Boston MA and same thing with me. Makes playing ingress a pain.

7/19 seems to be the last on that works correctly for me.
[Verizon Samsung Galaxy S III] Aquila76:
Cool, I'll have to try that out if something gets hung gps-wise.
[Verizon Samsung Galaxy S III] toddrosenberger:
All of a sudden on the latest nightly my phone has no sound and will not play any videos, tried flashing back to 10.1.2 and still problem. Maybe I need to do a full wipe..anyone else experienced this?
[Verizon Samsung Galaxy S III] NegativeOne:
Have you guys tried 7/20? Is 7/20 the first broken one, or is it 7/23? If we can identify which build caused it, we can isolate the commits that were the problem.