yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thank you for your input and support on this issue. I appreciate your thoroughness in your testing.

As for forcing your phone to not use LTE. I'm not sure why you need to go through the extensive steps that you do to turn LTE off. I use the "LTE" toggle in the Quick Settings Pull Down Menu and have no issues what-so-ever turning on or off LTE and this always remains through a reboot.

My phone is set up to automatically choose the network operator. I have my APN set to the one for LTE. When LTE is on in the quick panel settings, the phone is set to LTE/GSM/WCDMA. When I toggle LTE to off, it switches the phone over to WCDMA preferred which prevents the phone from using LTE. The APN stays the same but that doesn't matter because your network mode is set to one that doesn't use LTE.

I'm not sure why you are seeing what you see but I'm sure it is an isolated case and does not affect everyone. I manually toggle LTE on and Off daily depending on where I am with no issues what so ever. Try turning LTE on using the dialer code *#*#4636#*#* and go in and set your phone to LTE/GSM. Then reboot. See what happens then when you change your network mode via the CM menus. Does it still revert back to the wrong one? Should be LTE/GSM/WCDMA in the CM menus. Also try restoring your APNs back to default. Maybe something is borked in one of them causing the phone to not switch over. You can do this easily via the APN settings page menu. No need to do it manually.

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

I've looked into this but gave up on the whole idea. The only way to toggle 4G/LTE with Tasker is to use the Secure Settings Add-on found in the market. I had trouble with this however working as it usually didn't recognize my phone as having the right requirements to allow for this toggle to work. In any case, I usually run with LTE off at home or work and toggle LTE on if I know I'm going to be out and about around town.

It's not ideal but it works for the time being.

I was unable to locate any other ways of automating this through any other tasker type app either. I've looked high and low with no luck.

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

I have been asked to test a patch that is currently under review in the CM Code Review Process but I have no idea how to do such a thing.

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

Do I need a full blown build environment set up to do this? If I do, I unfortunately don't have the time or resources right now to get this up and running. If someone is already set up would it be possible to build CM with the patch shown above to post it for me to try out?

If it is something much simpler, would someone be able to teach me how to do it?

I have found this information online in regards to testing a patch http://wiki.cyanogenmod.org/w/Doc:_using_gerrit but it says to go ahead and build which is why I believe it's a bigger more difficult process than I am capable of on such short notice.

Any help or direction would be greatly appreciated.

Cheers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Under "manage apps", click on your app of interest, and you should see an option for "enable privacy guard".

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

No, it is not included in CM10.1.1, only in the nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Latest nightly mms shows constant sending of text
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
I'm running into this issue as well. The SMS does get sent but gets stuck at "Sending" status. Must've been some of the middleware patches that broke it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
20130712 one?

There was a new event added to make things simpler and the last bit of the patch is coming tomorrow, but that shouldn't affect in any way sending of SMS/MMS I believe.

Otherwise localization for Polish language on the 9th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes went back to previous nightly and the problem was not there. Went to 7/12 it returned again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Guess they broke something. Kinda happy I didn't flash the nightly yesterday night. Would have ended up with a broken phone for the day. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I went to the stable 10.1.2 from yesterday
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bentonhall:
I have this exact same issue. Always have on all versions of CM including the stable 10.1 which is what I am running now. The LTE toggle will show its off in the Quick Settings Panel for 30 seconds or so and automatically go back to enabled. When it shows off, the signal bar still shows 4G and never changes to H+. I also am not able to change the network mode, if I select either LTE/WCDMA or GSM/WCDMA Preferred, it reverts right back to LTE/GSM/WCDMA. The only way I've been able to successfully disable LTE is to switch to the old wap.cingular access point. Can anyone not having this issue on AT&T post what modem you are using to see if that makes a difference? I'm using I747UCDLK3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Yeah I thought that too based on cmxlog but according to CyanDelta those middleware changes made it in last night.

Screenshot: http://db.tt/GgcI9g1E
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ahhh what the hell. That might explain why... guess I'm staying clear of the nightlies for the weekend. Drink beer by the pool anyway, it's gonna be hot out. 8-)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Once again this isn't normal. The LTE button in quick settings works 100% for me all the time and has from day 1. Not sure what the problem is for you guys. I'm on Rogers so my settings won't help you out if you are on ATT. Your problem does sound familiar and I'm sure there are threads about not retaining network mode settings out there. Do a quick search and you'll likely find some other folks with the same problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
anyone know what changed in the latest Stable build?

it's sad that it's hard to find stable changelog... =\
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
From what I read, it's just security patches.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
See my response below. I'm on the same modem as you and got it to work with a complete wipe, factory reset, and clean install of the 7/11 nightly.

This wasn't working for me on the 7/5 nightly. However, thanks to your original post responding to me yesterday, I went back and did a complete wipe and clean install of the 7/11 nightly. Now the LTE button works, and does exactly what it's supposed to, just as you described. This was such a PITA for so long, I wonder why it finally works for me?

Thanks so much for the helpful encouragement, though!

P.S. I'm not sure what the purpose of LTE is except when you're tethered. I get 12mbit/2mbit on HSPA+ (27mbit/6mbit on LTE with full bars here), and that's more than fast enough for every possible thing I could do on my phone. Ping times are no different on LTE, either... I'm just curious how LTE is beneficial to other people - is it that vastly different in performance in some areas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
I'm in the same boat as bentonhall. Exactly the same. My LTE switch does nothing and changing the preferred network changes it right back .... shrug. I'm AT&T with the 11th nightly on a clean install, but it's been like this forever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bentonhall:
Anyone notice the "Experimental Signal Strength" build for the d2att that posted in get.cm earlier today?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Would a "test" build be more or less stable than nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That was a test build for me to try out some signal strength stuff related to the incorrect reporting of the 4G signal strength.

DO NOT FLASH IT!

It was a one time build to test some things out and I can confirm it did not work as intended.

Always stick to the nightlies, M or stable builds. Most if not all experimental builds are for the simple purpose of one or two people generating a build to test it out to see if a commit works and what else if anything it borks. They are potentially highly unstable and not intended for mass installation. The include code that hasn't been tested or verified even to the level of being included in the nightlies. Unfortunately it shows up in the get.cm list and can cause confusion. Anyway just ignore it. Once the code is sorted out the commit will eventually show up in the nightlies. I'll keep you guys posted.

---------- Post added at 06:41 PM ---------- Previous post was at 06:40 PM ----------

See above.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
tested the experimental build no signals at all... back to stable now... with stable I get 2 bars at the same spot n as soon as I dial a number signal bars jump to 4. I haven't dropped any calls yet.. cuz of signal strength.

it's common sense to stay with stable now :p

nightlies hmmmm not for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
As I mentioned above the Experimental build was not intended for anyone but me.

As for why your signal strength jumps when you make a call, you phone is most likely on a 4G network connection and when you place the call it reverts to 3G which in your location is a strong cell signal. This is normal as all phones will revert to 3G for an incoming or outgoing call.

If you have WIFI turned on, turn it off to be able to see what your phone is actually doing. It's impossible to truly understand the "bars" in the status bar when WIFI is on because it won't show you what you are actually connected too. When WIFI is off you can see E, H, 3G or 4G. When WIFI is active you can't see any of that. (Another way to see is in the phone status area of the settings).

Furthermore, this "Experimental" build shouldn't be considered a nightly because it's not and the nightlies are quite stable at this point in time. I don't want anyone to think the nightlies are compromised because of this experimental release.

---------- Post added at 07:03 PM ---------- Previous post was at 06:57 PM ----------

A good LTE speed for me can easily be double or more what I get with HSPA+. Sure you may not notice a difference on daily browsing but when streaming an HD video or downloading large files the speed difference can make all the difference. So yeah, your speeds seem in line with most but it does have its benefits. In the end it all depends on how you use your phone on a daily basis.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
In West Houston, I've hit speeds of 68Mbps down, so yeah LTE is crazy fast compared to H+
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Are the security patches from 10.1.1 and 10.1.2 in the last couple days worth of nightlies?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
Anyone on the latest nightly and have their messages stuck on 'sendin' but they are still going through? I can receive messages also.

Is there something i can do if I'm the only one experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DanD911Phx:
https://github.com/CyanogenMod/andr...mmit/cd143d037ce689622e45bf26a8f5b6dfbb0a0935

Introduced in 7/12 nightly. Fixed already and will be in the next nightly. Its in the experimental but do NOT flash that ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
What is the background of 10.1.2? I know 10.1.1 include the security fix, what does the latest 10.1.2 includes? No updates on the CM Blog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
The word from Koush is that he knew the first patch would break things until the second patch was finished. He expects the second patch to be in the next nightly.

https://plus.google.com/110558071969009568835/posts/6BpFRfqMvw7

~L.T.

Sent from my Galaxy S3 [AT&T][CM10.1]

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
7/13 has the SMS fix
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Will there eventually be "stable" builds of whatever is coming out in the new nightlies? Or after the current stable, does it stay in nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
I am having the same problem with the SMS sending message. It just say sending for ever.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] montrealcityboy:
So i take it 7/13 hasn't fixed the text message stuck on 'sending' bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drping11:
Agreed, the newest nightly didn't fix the SMS sending issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Yes it did....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
Yes it did fix the sending issue.

You might have to erase those thread that already have errors before the upgrade to make sure it's working fine...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Thank you. Downloading now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
The guy looking into the 0dBm/99asu bug has given up. According to him it's unfixable on the CM side of things. So I guess that's that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
MMS and SMS both working fine for me on 7/13 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Looks like my fears are true, that this won't be fixed until AT&T releases the official 4.2.2 ROM/modem...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Where is there any info on this bug? I've never heard of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ipilcher:
What makes you think they will ever do that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Can someone enlighten me as to what this bug is exactly? I'm hoping to God this isn't the random reboot issue related to the modem...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Guys you really need to read. That flexfulton guy has been posting regularly about this for months. It's about lte band switching in low signal situations.

~L.T.

Sent from my Galaxy S3 [AT&T][CM10.1]

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ratdog07067:
The MMS thing is weird. I took a picture of a car at a lot at 11:30 this morning and texted it to my wife - went through no problem. An hour later I took another one, same phone, no changes in any settings, tried texting it and it hung up on Sending. I tried rebooting the phone and re-sending and same thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
If mms is stuck on "sending...", try long-pressing the pic while stuck, select "edit", then hit send again.

Found this in another thread. Worked for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
The problem is with AT&T version of the S3. There is a way to make it stick. Just do a search.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
d2can and d2att are virtually identical minus radio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aybarrap1:
Then the radio is the issue if this is the case. On d2att, the stock rom does not allow for network selection and it stick. In fact the only way to access network preferences is by dialing *#*#4636#*#*. For CM it does not readily stick either for the AT&T variant. The way around this is System settings/More.../Mobile networks/Network operators. You will have to wait at least a minute or two for it to search. Once it populates, choose the network. In my case I am on AT&T and sometimes three of them pop up. I just choose the top one labeled with my carrier. Once it says registered on network, the network preferences option will stick. You will also be able to utilize 2G only. Until you register the network, 2G will gray out if you select it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pkimkpop:
nfc file sharing between s4 and s3

A friend of mine who has the S4 stock unrooted tried to send a file to me on my S3 running The latest cm10.1 and when we touch phone backs together my phone goes straight to Google play store and says error. Can someone help me . we both had NFC enabled
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
It is due to the size of the image. The edit workaround seems to compress it again to a small enough size to work.

On ATT if the image the MMS app tries to send is over 1MB it fails. You can click and hold on the image and check details.

Unfortunately the MMS app doesn't seem to be resizing the images below 1MB reliably.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JayDream:
Thanks. after the latest stables and nightlies broke subway surfers, this is exactly what I've been looking for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
getting low volume for the mic in different apps like skype n viber
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
thanks I thought no one noticed even the stable version cant play subway surfers!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] te_quiero_forever_girl:
Does anyone realize that the screen on/off animation has been changed in the latest nightly ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
It'll be back in the next nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I hope not as I hate the CRT animation. Bright flashes of light strains my eyes, especially when it's dark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
You can turn it off in display settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
Yea I know that. I've always had it turned off. But now I can turn it on again and enjoy the fade out animation.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mhdsanto85:
I really like this simple fade animation. Crt is kind of old....

If the Sony wt19 screen off animation could be ported, it would be nice!..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I feel as if I should know this but I have not used Cyanogen in a while. Does CM have Halo or any kind of floating window mod?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No.

---------- Post added at 05:50 PM ---------- Previous post was at 05:42 PM ----------

Agree with you, CRT is getting meh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Does anyone else have very lazy hand-up back to 4G after calls? I tend to get impatient and go airplane mode or go to *#*#4636#*#* to get it to re-handshake and get 4g back.

Also, has anyone else had very odd behavior on 10.1.2? My phone was freezing up (sorta) a lot on 10.1.2.. it was most noticeable in car mode - it seemed like the car home app would always go not responding, but I also had apex launcher and poweramp go not responding often as well. I reverted to 10.1.0 with no issue, and I'm currently on 10.1.1 and don't have the issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
I switched carriers from AT&T to T-Mobile, but kept my i747 device and d2att CM10.1 nightly (7/10). Since switching I have had many random reboots, which I did not experience prior to switching. Also since switching, I have had issues with my data signal dropping out of nowhere, even though immediately before dropping I had a connection. The data signal fluctuates wildly. Does anyone have any insight as to whether switching carriers but keeping my i747 device and 7/10 i747 nightly can cause any of these issues? I should continue flashing the AT&T ROMs and the T-Mobile ones now, right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You shouldn't flash the d2tmo nightlies if your phone is d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
Thanks. That's what I thought. Can switching carriers still cause issues, though?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It could give issues with connectivity and getting 4G service or similar depending on the bands your operator uses, but reboots would be far fetched. I would look into something else.

If you tried to flash a d2tmo rom prior then went back to a d2att one it might be a good idea to backup your apps using something such as Titanium Backup then wipe everything clean and start fresh.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stone_phalanges:
Has there been any word on HDMI out? is it gone for good? I haven't heard word of it since May 21st.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Correct me if I'm wrong, but isn't it a proprietary driver issue regarding this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
HDMI out has been broken and fixed twice in the last year. We're just on the longest broken streak now, for whatever non-proprietary reason.

---------- Post added at 02:07 PM ---------- Previous post was at 02:00 PM ----------

[/COLOR]

I switched from AT&T to T-Mobile last month as well, keeping my unlocked att s3, and sticking with the d2att cm Rom.

FWIW, the random reboot (in)frequency was about the same before and after switching, but the signal fluctuation is all over the map like you described, even in the NYC area where I get 4 4G bars. It's either a ROM problem (test with touchjizz), an AT&T radio on tmob problem, or just a network problem (find somebody with a t-mobile s3 running the same Rom, in the same vicinity, and compare)

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Broken steak isn't too good. :p

Thanks for the heads up though. Not a function I use, can't comment, but still curious.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Hi. Does anyone know why the pixel density of our device is set to 320 and not 306 (the actual pixel density of our screen)? I find that having the pixel density at 320 affects some alignment in some apps, after changing it to 306 in build.prop everything aligns better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I saw reports on MMS getting stuck on sending but has anyone had issues with receiving MMS? I'll often not receive all of the MMS' that are sent to me until I respond to the group message. For example this AM I'm on a group message with me and 2 others. 1 person sends 3 messages at 8AM I only receive 2 of them until 10AM when I respond I receive the 3rd message. This is a pretty difficult issue to replicate and to even realize is occurring.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
I thought the default DPI was 320. 306 is the PPI.

I read that PPI is pixels per inch, which is hardware and you can never change that. DPI is dots per inch and is OS level and can be easily modified by changing your build.prop to some other number
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://review.cyanogenmod.org/#/c/45653/

Looks like have a fix now for the 99asu/0dBm issue. Interested to see how much of my issues this will actually fix.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Testers wanted:

https://plus.google.com/106725270254855943082/posts/RAnRojXmKes

Sent from my Nexus 7 [CM10.1]

Samsung Galaxy S3 [AT&T] [CM10.1]

Galaxy S Captivate [CM10.1]

OUYA
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
This is 4 or 5 days old... Not sure if it's still good / needed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That was the original patch he was using to attempt to get it to work. All the stuff is 4 days old and it never worked as planned.

New fix has been apparently confirmed working and should be in the next nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] noobnl:
the 0/99 asu bug is fixed. http://review.cyanogenmod.org/#/c/45653/