yashsingh1/xdaforums huggingface dataset:
[Sprint Samsung Galaxy S III] haynesr07:
Anyone had camera trouble? Randomly quit on me one day required reboot kind of annoying.
[Sprint Samsung Galaxy S III] Logix:
International ? I use Justin bean gapps pack good idea try it out report back

In my house in a certain area I have no service and I can't get it to happen
[Sprint Samsung Galaxy S III] haynesr07:
Yeah I flashed 10.1 again and I'm still having some serious problems with my network. 1 to zero bars max for 3g and 4g, but stock and other roms are fine....what's going on with that?
[Sprint Samsung Galaxy S III] vestaviajag:
I see the international roaming under settings/more.../mobile networks

Is there some other place that has roaming settings?

I'm not sure it's a gapps thing as much as it is a data connectivity thing. Reason I say that is I just deleted my google account from the phone, and it still got random wakes.

I will try Justin bean gapps and report back.

Thanks!
[Sprint Samsung Galaxy S III] haynesr07:
Well I guess it was just the version of 10.1 I had. Network issues resolved by not using that version. Dl'd a few weeks ago
[Sprint Samsung Galaxy S III] Logix:
Thought so
[Sprint Samsung Galaxy S III] Logix:
Can you post a log cat

You have the same setup as me. I don't have the issue what's your governor
[Sprint Samsung Galaxy S III] Plinkett:
Often after updating, I have to reinstall some apps. This most recent flash to nightly 2013-01-07, I had to uninstall and reinstall YouTube, Prey and Facebook because they would constantly force close at boot, even though I wasn't running them and have no widgets for them.

Before that, the included installation of Terminal Emulator would force close when it ran. This happened both on my GS3 and on my Galaxy Tab 2. I ended up having to manually remove it with the file manager and reinstall it from the store, which solved the problems for all of those apps.

The more annoying thing right now is the recent changes to the lockscreen, which make it so your widgets are nigh useless if you have a security method set up. Is there a way to bring back the old method where you had a widget on the screen and an unlock button on the bottom, which you would slide to bring up whatever unlock method you chose (pin/password/pattern)?
[Sprint Samsung Galaxy S III] EndlessDissent:
Stock doesn't show the bars for 3G or 4G. The bars are always for 1x signal, even if the connection says 3G or 4G next to the bars. CM10 does show the actual 3G and 4G signal in the bars. 3G and 4G will always be lower than 1x, especially if your market has had 800MHz activated in the PRL.
[Sprint Samsung Galaxy S III] Logix:
the lockscreen is still wip
[Sprint Samsung Galaxy S III] Logix:
Thanks! yeah i remember seeing this why is it lower with the 800? i thought it was higher . 800= more coverage cuz the larger wave length? i saw some maps and 800 gave something like 2.5x coverage and if they are lower how is it lower than 100 db 1x? whats the cutoff for lte? 100and change? also is there a app that appropriately shows me lte db
[Sprint Samsung Galaxy S III] Neonfire:
I get the app switch bug sometimes, I usually just reboot. luckily this beast boots fast.
[Sprint Samsung Galaxy S III] Plinkett:
Ah, okay. If I press menu/power, the screen comes up and immediately asks for my pin number. If I swipe screens to the left and then back to the right, it brings up the screen how it should be (Clock widget with weather and calendar). If I disable the lock screen security, it just goes right to the phone. It's just weird how it actually was working pretty well before.

The left part is when turning the phone on, the right is after swiping to a different script and back again.
[Sprint Samsung Galaxy S III] EndlessDissent:
Only 1x is being rolled out in the 800MHz spectrum. Therefore, the 1x signal will be much better compared to 3G and 4G signals in the markets with 800MHz activated. If you reread what you quoted, this is what I was saying, perhaps not clearly.

The cutoff is 120 dBm RSRP.

CDMA Field Test is your best bet.
[Sprint Samsung Galaxy S III] haynesr07:
Any idea when this will be official?
[Sprint Samsung Galaxy S III] Logix:
that why we see so much bigger coverage from single lte towers on sensorly than 3g?

does that not cause signal degradation with 1rru setup? how good can a signal really hold at -120.

sorry for all the random questions you seem informed
[Sprint Samsung Galaxy S III] Logix:
cm? its already offical

my thread... never it sucks. its ment as a temporary help ill eventually move aokp source built and wont support it.and bugtracker will be out for cm (unfortunately few know how to use it but ill make a tutorial which probably wont help still . xda is a black hole of mass epic proportions but i love it.
[Sprint Samsung Galaxy S III] haynesr07:
Well 10 is stable. But I mean a stable release and not nightlies.
[Sprint Samsung Galaxy S III] Logix:
Oh stable official 2 different things stable is when the nights get that way
[Sprint Samsung Galaxy S III] EndlessDissent:
That's most likely a downtilt issue because when a single tower in an area is upgraded, its downtilt is set to cover the largest possible area. As nearby towers are completed, the downtilt is adjusted to decrease overlap and interference. When Network Vision is complete, assuming people remap the areas in Sensorly, the coverage per tower will even out between LTE and 3G. Since they share the same frequency (1900MHz), coverage should be about the same, but LTE will have slightly less coverage because it's a more fragile signal (this isn't a problem with LTE; it's just what happens when you try to cram more data in the same frequency; it happens with every new wireless technology, which is why the companies want the lower, father-reaching spectrum so badly).

You should probably check out the website s4gru.com. There are a ton of experts in the wireless technology field that hang out on the forums there that can answer your questions better. It's also a good place to keep up with Network Vision progress.
[Sprint Samsung Galaxy S III] Logix:
I'm. A member no one was as direct n clear as you
[Sprint Samsung Galaxy S III] haynesr07:
I haven't really been tracking these nightlies for a couple weeks, bugs going well?
[Sprint Samsung Galaxy S III] zkz90:
http://review.cyanogenmod.org/#/c/29870/

a ton of audio commits incoming! hopefully we can get in-call volume fixed at least :D
[Sprint Samsung Galaxy S III] jordanabc:
Headset volume seems much louder as of 1/09 nightly.
[Sprint Samsung Galaxy S III] zkz90:
+1

ad2p worked for like 30s
[Sprint Samsung Galaxy S III] jordanabc:
Same here. Bluetooth audio is still messed up.
[Sprint Samsung Galaxy S III] Wilkesin:
Fix appears to be coming according to the next nightly changelog. Nice!
[Sprint Samsung Galaxy S III] Bielinsk:
Only thing preventing my from running it as a daily is that it's bluetooth stack doesn't provide MAP.

That is required to send texts to and from my Toyota.

Stock has this setting.

There are other things as well for bluetooth. Like contact pictures are not sent etc.

I can't seem to find a place listing what is added each night to search for MAP.
[Sprint Samsung Galaxy S III] Wilkesin:
Here for our phone:

http://changelog.bbqdroid.org/#d2spr/cm10.1/next

and here for CM common:

http://review.cyanogenmod.org/#/q/status:merged,n,z
[Sprint Samsung Galaxy S III] Logix:
anyone notice mad screen flicker when trying to pulll down the status bar in a call?
[Sprint Samsung Galaxy S III] zkz90:
nope
[Sprint Samsung Galaxy S III] Logix:
New kernel fixes
[Sprint Samsung Galaxy S III] FlakMagnet:
Do you have link to google play for that? Maybe a how-to write up?
[Sprint Samsung Galaxy S III] Logix:
Turns out its not for GS 3.

I read that boost gain under galaxy s3 device settings may work. I don't have the issue soo can't try to fix it
[Sprint Samsung Galaxy S III] vcast009:
Not too sure if this is a bug, but the global vibrate setting overrides specific app setting for notifications. For example, I set the Gmail notification to never vibrate, but then it does when I set ringer to vibrate. In 10.0 app settings remained the same regardless of the global setting. Any insight would be helpful!
[Sprint Samsung Galaxy S III] akm987654:
Anyone else with this problem? If I open the camera and the lock screen comes on the whole phone freezes and I have to reboot. I've tried clearing camera cache and data to no avail. Has happened on all nighlies I flash.
[Sprint Samsung Galaxy S III] Logix:
anyone have tethering issues?
[Sprint Samsung Galaxy S III] CNexus:
Are you use the TreveMod wifi tether app? That one is modded specifically for this device

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

Whats your flashing process? Do you clear EVERYTHING before flashing? (Data, system, cache, dalvik-cache)
[Sprint Samsung Galaxy S III] busyychild:
lack of MHL support.
[Sprint Samsung Galaxy S III] Logix:
I'm on AOKP that's tw only

And yeah clear everything
[Sprint Samsung Galaxy S III] akm987654:
Figured it out! In developer settings I had the Window, transition and animation scales set to zero. I changed them all to. 5 and it works now. Such a simple fix... I never dirty flash, no glove no love. Always flash with protection!
[Sprint Samsung Galaxy S III] blueeyedbassist:
bahh camera!

I absolutely hate that the cam freezes
[Sprint Samsung Galaxy S III] Logix:
Anyone know asop WiFi tethering works for then or have a work around
[Sprint Samsung Galaxy S III] tank1916:
I've noticed this for every build, up to 1/21/2013 and it is a very annoying first world problem. I have 2 google calendar apps so I am getting two alerts for everything, even after complete wipes. I know I can uninstall the one I downloaded from the play store, but why is a different calendar still being included in the gapps/rom?
[Sprint Samsung Galaxy S III] pitcherj:
I noticed this too.

I just set the "old" calendar app to have no notification sound.

I was going to disable it but I'm not sure what that would do to calendar sync so never really bothered with it.

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] pitcherj:
For those who are flashing to 12/26, you might try the latest nightly plus the flashable zip from user madmack linked in the following forum post that reverts the Bluetooth to the 12/26 build (supposed to fix a2dp).

http://xdaforums.com/showthread.php?p=37058211

I tried this in hopes that it would fix Bluetooth voice dial, but alas, my hopes were dashed.

Sent from my SPH-L710
[Sprint Samsung Galaxy S III] CarlT:
On the GS3, the "Dark Theme" on the messages app does not work?
[Sprint Samsung Galaxy S III] DerIdiot:
Anyone else getting the loud BEEP for ending a call coming out of the speakerphone instead of the ear piece?

Edit: This has been confirmed to affect multiple people for the last 3-4 nightlies.
[Sprint Samsung Galaxy S III] fishking2:
Car Bluetooth Audio

A problem I have found in all of the nightly builds is that I can't play music through the bluetooth radio in my car. Connects, but mumbled and scratchy quality (stops and goes on and off alot too)
[Sprint Samsung Galaxy S III] CNexus:
I saw someone post that it worked in one of the nightlies...but then it didn't in the next.

Sent from my PG06100
[Sprint Samsung Galaxy S III] Logix:
it works on aokp for me :) and clean bean
[Sprint Samsung Galaxy S III] GiantJay:
Flash 1/31 nightly it should be working
[Sprint Samsung Galaxy S III] captStevo:
Keypad not working

Anyone else have Google Voice that occasionally can't "press 1" to answer? This bug seems to strike randomly... The keypad in the phone app will not send tones so I can't pick up a call.
[Sprint Samsung Galaxy S III] Trueno22:
no but I am unable to swap from using my number to the voice number without a fc.
[Sprint Samsung Galaxy S III] GiantJay:
Found a bug. When listening to audio with a audio jack plugged in, if you have the screen off and pull out the jack while the audio is playing then turn on the screen, the screen flickers bad. I'm on the 1/31 nightly with a completely clean install. This happened with the TuneIn Radio Pro app. I heard someone else with a different device have the same thing happen using Play Music.
[Sprint Samsung Galaxy S III] jdogg836:
Pretty sure it's a google issue not a phone issue. Whenever it strikes, none of my phones will do it regardless of ROM, maker, and such. Check the bug reports from google, lots of reports.
[Sprint Samsung Galaxy S III] captStevo:
uldoing upon

I initially thought so too, but I also randomly run into the problem when calling an 800 number and can't press a number at a prompt. For instance "Press 1 for english" doesn't work sometimes. Maybe it is just a GV problem though. Thanks for the reply.
[Sprint Samsung Galaxy S III] COOKtheKILLA:
I have a couple bugs. One is the beep when hanging up...not even sure if this is a bug or not. Also, when I select attachment in a text, then select capture photo, then take a photo, then attempt to retake the photo it locks up. Then it says gallery is not responding so I select quit. After that if I try to use the camera at all it says "cannot connect to camera." If I restart it fixes the camera but I can recreate this issue every time! I have cleared cache/dalvik/fix permissions. I'm on the 2/3/13 nightly and this bug has been present on at least the last 3 nightly's.

Love me some CM10.1 though. Bad a$$ ROM IMHO
[Sprint Samsung Galaxy S III] hotsauce32:
Sometimes a short press of the home button is being registered as a long press and bringing up the 'recent apps' menu. Happens kinda randomly, rebooting usually fixes it temporarily. Happened to me on the 1/17 nightly and on the 1/31 nightly after a clean flash. I was on 1/17 for maybe a week and a half and the issue only started happening maybe a week ago. Clean flashed to 1/31 thinking it might fix it, but it still happens.
[Sprint Samsung Galaxy S III] pluesama:
I just upgraded to the latest 10.1 nightly from the last CM 10.0 nightly, and now I can't make phone calls. I don't know if I can receive them or not as I haven't had someone try (that I know of). I still have my IMEI and phone number, and I can connect to 3g/4g, but the phone itself doesn't work. Fresh install, stock kernel. I had some issues where my number was missing and I reverted to the stock MA6 and reactivated and updated the PRL but it still won't work. Any ideas?
[Sprint Samsung Galaxy S III] GiantJay:
Use your nandroid to get back to before it was messed up.
[Sprint Samsung Galaxy S III] pluesama:
That's great and all, but it doesn't help me get this rom working properly.
[Sprint Samsung Galaxy S III] cuteyr:
Camera not working

Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false[/QUOTE] Seems to be working as of 1/3

Camera Crashes :

Bluetooth A2DP :

BT A2DP not functioning properly some say to make a call and hang up using bluetooth

GPS shows locked in notification drawer even after being turned off

Camera: * unconfirmed

NO GPS?

flash back to any tw rom get a lock and then flash back to cm/aokp

Memory:

Screen wakes: screen wake only on stock kernel use ktoonsez kernel make sure min mhz is stock * possibly fixed in 1/3?

4g: ehrdp hand off still a bit wonky toggle airplane mode if it has trouble not sure. some reports of it working find others its.*

App switcher bug please confirm?

anything else? submit a reply and ill ad it to the op! your help is appreciated!

Bug fixed? as bugs get squahsed ill remove them again this is ment as a running list cuz theres no bug tracker[/QUOTE]

My camera dont work at all. When i open the camera app it just has a black screen then crashes. Any way to fix that?
[Sprint Samsung Galaxy S III] DerIdiot:
Enabling "AirPlane" mode when Bluetooth is on and in-use causes it to forever be stuck in "Turning off Bluetooth..." status. Only a reboot will fix it.

This is on 2-17-2013 build, cm10.1 kernel.
[Sprint Samsung Galaxy S III] pie_are_squared:
bugs

bug 1: i cant hang up a phone call using the button on my headphones

bag 2: so in the older versions (pre 2/13) if you picked up a phone call while you were listening to music, the music would not turn on after you hung up. at all. on the latest nightly (2/19) the music goes back on, but its blaring loud. then when the song is over, the volume stabilizes.

dunno if this is a bug or a complaint, but what happened to the reboot menu? it used to be that when you pressed reboot after holding down the power button, it would give you the option to reboot in recovery, download, or system. i liked that feature, it just disappeared. where did it go?

complaint/request: if you finish typing a word in stock android then hit space, then you go back and tap on it, word suggestions show up. im not seeing this in CM. if you type a word then hit space, then go back to the word, the word suggestions dont show up

finally: i am not having any success with any wifi tethering in CM. has anyone had this? any solutions? tips? apps? advice?

but after all is said and done im loving it and using it
[Sprint Samsung Galaxy S III] pluesama:
bug 2: This is supposedly fixed in today's build. I haven't had a chance to test it yet, though.

The reboot menu has just been changed by default, but can be changed to the advanced menu through Developer Options -> Advanced Reboot

As for wifi tethering, it should work without encryption. If you need encryption, you'll have to use a custom kernel, as the CM team hasn't fixed it yet.
[Sprint Samsung Galaxy S III] pie_are_squared:
thanks i found the reboot options and changed it.

just flashed the latest nightly. ill let you know how it works with the music issue :)
[Sprint Samsung Galaxy S III] pie_are_squared:
music

confirmed: music bug was fixed on latest nightly :)
[Sprint Samsung Galaxy S III] pluesama:
Good to hear. I had recently upgraded to 10.1 when 4.2.2 came out, and the first day I got 3 texts within 20 minutes while listening to music at work. It was... unpleasant to say the least.
[Sprint Samsung Galaxy S III] pluesama:
Has anyone tried today's build with KT747? I can't seem to get it to boot on a dirty or clean flash. Stock kernel boots fine.
[Sprint Samsung Galaxy S III] bounce8:
Volume wake works intermittently. Tried different nighties, wiped cache, fixed permissions with no luck. Thanks!

Download rom toolbox and open the build.prop editor search for lpa.decode=true and change it to lpa.decode=false[/QUOTE] Seems to be working as of 1/3

Camera Crashes :

Bluetooth A2DP :

BT A2DP not functioning properly some say to make a call and hang up using bluetooth

GPS shows locked in notification drawer even after being turned off

Camera: * unconfirmed

NO GPS?

flash back to any tw rom get a lock and then flash back to cm/aokp

Memory:

Screen wakes: screen wake only on stock kernel use ktoonsez kernel make sure min mhz is stock * possibly fixed in 1/3?

4g: ehrdp hand off still a bit wonky toggle airplane mode if it has trouble not sure. some reports of it working find others its.*

App switcher bug please confirm?

anything else? submit a reply and ill ad it to the op! your help is appreciated!

Bug fixed? as bugs get squahsed ill remove them again this is ment as a running list cuz theres no bug tracker[/QUOTE]
[Sprint Samsung Galaxy S III] Logix:
im in the process of updating the op so please report back with newest nightly bugs and is tethering confirmed not working on stock kernel? thanks guys!
[Sprint Samsung Galaxy S III] Paintguy25:
dialer codes???

i need to change my mmsc and dialer codes wont work since upgraded to cm10.1 can anyone please help??
[Sprint Samsung Galaxy S III] hermeticist:
Did you flash fresh or dirty?

I.e did you wipe data, cache and dalvik before flashing?

That is a necessary step when upgrading from 4.1 to 4.2.
[Sprint Samsung Galaxy S III] guirae:
Although I am currently on SlimBean, I post here because this I left this specific CM10.1 ROM for the following reasons.

Currently on:

ROM: SlimBean Custom RC2 (not the one in the OP but towards the end of the thread because it is a test build Cordell asked people to try out)

Kernel: Already baked into SlimBean on flash but has been modified by Cordell due to the comments Steve Kondik has made.

Flashed: 27 hours ago

GAPPS: latest 20130301

Three bugs that I had on CM 10.1/ AOSP ROMs were and possibly still are the following:

1) Home button bug:

This is a bug that occurs approx. 48 hours after flash. It has something to do the the system freaking out due to a QCOM optimization. The issue pertains to time and leads to a bug that when 'short pressing' the home button, the recent apps feature appears. Other have stated that any touching of the screen registers as "double tapping" or "holding down a capacitive button"

- Steve Kondik of CM has addressed the issue and has stated a theory. He has requested devs to take out a line in the kernel. So far so good. I feel extra optimistic in that the bug would usually occur couple of hours after the AOSP Keyboard Gesture streaks became thinner. The streaks usually go thinner in 7-8 hours after boot. My streaks are still as thick as when I first booted.

2) Camera stutter on focus bug:

1-2 hours after boot, when opening the camera app, you can sense a significant lag. When moving the camera around, the screen lags in that the screen is moving in extremely slow frames. Also, the issue could be easily reproduced when focusing on something. the circle would turn green and the frames would become laggy again.

- Flashed the new 20130301 GAPPS and I have not yet experienced the issue stated above

3) Korean, and potentially other language characters missing

I was not be able to see Korean characters as I went on Facebook, Gmail, or a Korean website. After researching the matter, this is a 4.2 issue. Not a bug, but it has something to do along the lines of building a ROM. If a dev does not take a certain route or integrate a specific base (excuse my subpar development jargon. Please correct me if I am wrong in anything I say) the characters could show up as literally blank spaces.

- Being on SlimBean, this is not an issue. This was not an issue on CM but I thought I'd list it anyways in case other AOSP roamers are looking for a solution.
[Sprint Samsung Galaxy S III] el_mariach:
Screen is not rotating for me. As far as I know all of my options are checked for rotation.
[Sprint Samsung Galaxy S III] pluesama:
Not sure if this is an issue with the ROM or the towers around here, but is anyone experiencing the clock de-syncing? Sometimes I check my phone and it's several hours off.
[Sprint Samsung Galaxy S III] Gguarda23:
So I have been running cm10.1 for a while now (about 3 nightlies in after it came out) and I still get no results from the exposure settings on the camera app. It works on cameraZoom but doors absolutely nothing on the aosp camera app that is included in cm 10.1. Does anyone have a fix for it?
[Sprint Samsung Galaxy S III] Neonfire:
I'm having an issue on recent nightlies where when I lock the screen it won't turn the screen off but will be locked. Any ideas?
[Sprint Samsung Galaxy S III] filmaker:
I have a question, has anyone found a AOSP Rom where the mic volume for video recording is not low?
[Sprint Samsung Galaxy S III] Logix:
carbon seems right on for me its my perma dd but id use the old/non 3/4 kt kern and a 17 build cuz hte recent are kinda bugggy after the power button fix
[Sprint Samsung Galaxy S III] filmaker:
Alright thanks, I'll check it out
[Sprint Samsung Galaxy S III] Logix:
the newest seems like its almost all the way back to dd on carbon
[Sprint Samsung Galaxy S III] bilatunt:
Galaxy Grand Duos familiar design style of the hit Galaxy S III. The relatively large size and not easy to handle with a

----------------
[Sprint Samsung Galaxy S III] smartguy10:
Is there is any workaround for phone freezing in calls
[Sprint Samsung Galaxy S III] deezeejoey:
My phone has been locking up and rebooting a LOT with the past few CM nightlies anyone got a suggestion for a better rom?
[Sprint Samsung Galaxy S III] Ascertion:
Grab an AOSP based ROM that's using the 3.0 kernel. (SlimROM cough cough) :p