yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] integrate01:
I'm on 9/17 build with clean flash. i keep getting browser force closes after a while. Anyone else?
[Verizon Samsung Galaxy S III] syde1020:
Anyway to adjust in call volume???
[Verizon Samsung Galaxy S III] TechSavvy2:
Press volume rocker up/down as needed, lol.
[Verizon Samsung Galaxy S III] MG386:
Adjust in call volume by

1. Press volume rocker to bring up volume slider on screen

2. Use finger on screen, not rocker, and slide all the way up then down.
[Verizon Samsung Galaxy S III] kls629:
^ This should be added to original thread

As should alarm volume be moved in sounds in order to get noise from device when alarm is set. If not no noise comes out until volume is moved up or down
[Verizon Samsung Galaxy S III] Best01:
Anyone having issues with mms being sent upside down.
[Verizon Samsung Galaxy S III] goldsmitht:
No, but was getting warning that phone was sending a lot if text messages (was chatting with my wife) and asked for permission to send each text. Went on for about 10 texts or so, then just stopped
[Verizon Samsung Galaxy S III] salas2324:
That's not a bug. Its a feature.

Sent from my Verizon Galaxy S III
[Verizon Samsung Galaxy S III] beaups:
Its a bug when it asks you over and over and over every time you send a text.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Android beam doesn't seem to work. Any one else get it to work?
[Verizon Samsung Galaxy S III] syde1020:
Doesn't work for me. Sound is really loud almost like its on speaker phone.
[Verizon Samsung Galaxy S III] NeoMagus:
Works fine for me between S3 and Nexus 7 just beamed a picture no issue
[Verizon Samsung Galaxy S III] cgulliver:
Anyone tried the 2nd 9.18 build?
[Verizon Samsung Galaxy S III] alee:
Can't say I can tell the difference between the 2, but the 2nd one works as good as the 1st one.

Looks like Jenkins is building early tonight for whatever reason.
[Verizon Samsung Galaxy S III] Best01:
It's driving me nuts that whenever I send a mms its upside down. Not surewhy iit's doing it. I flashed clean on 9/17 and it did it and than I dirty flashed 9/18 and still doing it.
[Verizon Samsung Galaxy S III] ercDROID:
I am getting a ton of wakes with screen off. I tried 2 days on stock kernel and one my first day on latest lean kernel. Anyone else seeing this? 1 hour of screen time and 12 hours off charger and at 44% which isn't terrible but I have seen much better on earlier builds. I lose 3-4% and hour with screen off where I used to see 1-2% before. This is on 9/17 and new modem.
[Verizon Samsung Galaxy S III] jdubau55:
I see. It's not a huge deal really. Just a little odd. Don't think it really effects anything.
[Verizon Samsung Galaxy S III] mikaeldalc:
What is the most stable version so far... I mainly use video player, YouTube, music player, web browser. I never switch to 3g manually and use bluetooth BEATS earphones. As long as 4g works fine, I can make phone calls, chat via text messages and use these features just fine then I'm on. And nightly date recommendations?
[Verizon Samsung Galaxy S III] Durthquake:
anyone else have issues with the resolution on mms in/out being low? I am able to send higher quality is i use go sms, but does not help the incoming. any fix's? never had this issue with stock. :eek:
[Verizon Samsung Galaxy S III] chetqwerty:
Tried? I'm on the latest Nightly 18 take 2 and i still don't have control of my keypad during voicemail retrieval. Did i miss an instruction to enable the fix? I see it's in the changelog but still no work-y.
[Verizon Samsung Galaxy S III] quattr0:
Audio in video record still low :( 9/18
[Verizon Samsung Galaxy S III] rgrossie:
IMHO it's been pretty stable since M1. I haven't had any major issues since then- the rare data drop (easily repaired with a reboot or airplane mode on/off), and I had one SOD today on 9/15. I'm now on 9/18 part 2, so far so good. Audio on the video recorder is still a problem, but is virtually meaningless to me.
[Verizon Samsung Galaxy S III] juancaperez2000:
i just did a full clean installation in my phone ussing N18, this is some issue that i have geolocation work but GPS no, it is some fix around here, thanks
[Verizon Samsung Galaxy S III] neyenlives:
whats a voicemail?
[Verizon Samsung Galaxy S III] sullivan1985:
I ditched Verizon Voicemail a long time ago. Been using Google Voice since it came out. Way better if you ask me.
[Verizon Samsung Galaxy S III] Nightwind Hawk:
Just finished my first full day of having 9-17 (first time CM for me) and wow! Battery life is certainly amazing... Granted, I didn't use it much today but 70% after 12 hours being unplugged. Idle 4G/phone radio would go down like crazy on touchwiz...

Keypad works fine for me during calls but there is a horrible echo which others don't seem to have a problem with?? (Not talking about speakerphone)
[Verizon Samsung Galaxy S III] Zacharybinx34:
Are you referring to the feature where you place both phones together and knock on the side to send a photo? That's what i am referring to. How are you doing it?
[Verizon Samsung Galaxy S III] jackpot08:
im looking for a daily driver. would you guys suggest the M1 release?
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
I would like to know what the difference is on m1?

I flashed it but never saw or noticed anything
[Verizon Samsung Galaxy S III] alee:
I suggest always downloading the latest release as your first one. There is no point in older releases short of the M experimental releases. Even then, the list of bug fixes since M1 has been substantial.

CM10 only improves if people stay with the latest releases. Don't be "that guy" who is still wondering why something is broken in an August release and refuses to upgrade. CWM is your friend. Go get the latest and greatest and see for yourself.

---------- Post added at 11:37 PM ---------- Previous post was at 11:34 PM ----------

It's just a monthly stable milestone.

http://www.cyanogenmod.com/blog/cyanogenmod-10-m1
[Verizon Samsung Galaxy S III] NeoMagus:
Yes all you do is open gallery the picture you want and when you touch them together it says touch to beam, touch the screen and it beams it over on the other device it'll say image beamed and shows up in a folder named beam no issues at all with it here on 9-18 its been working for a while
[Verizon Samsung Galaxy S III] Zalithian:
I'd go with M1 if you want CM. AOKP JB build 2 is solid, minus the custom ringtone for contacts thing. Even though the new CM's do have new fixes, they still introduce new ones since they're always adding new stuff. You never know what will break one day to the next.
[Verizon Samsung Galaxy S III] sullivan1985:
Did a full clean flash (format /data, /system, /cache and wipe Dalvik) of 09/18A and so far...

The good!

-I have no echoes that some have reported in the 9/18 builds.

-No screen flickering of any kind.

-The CRT animation has returned!

-GPS is getting a solid lock in seconds.

-4G is very fast and reliable (noticed it in places I was only getting 3G on previous builds with clean flashes).

-Battery life is good with heavy use and audio streaming.

The bad!

-Still getting random 3G drops (but not as often).

-Volume buttons still don't control in-call volume (but on-screen slider does).

-Video recorder volume is low.

I am very satisfied with the 9/18A build. I'm not even going to bother with 9/18B or even the 9/19 build unless it has some kind of significant addition to it.

-Sully
[Verizon Samsung Galaxy S III] THISisTIG:
I would highly recommend the M1 release as a daily driver. I flashed the nightly builds until it came out. If you don't plan to report bugs and are just looking for a solid ROM to run then this is probably for you.
[Verizon Samsung Galaxy S III] InsaneScientist:
Disclaimer: This is my first foray back to CM10 since the bootloader unlock was found, so I may have missed something. I've mostly kept up with the thread, though, and I don't think I've missed anything in the last hundred pages or so...

Here's an interesting oddity on the most recent nightly (9/18 v2) with the most recent baseband (I535VRLG7). When I first boot up my phone, it won't connect to my WiFi, despite it showing the WiFi as being active and it showing my home network as being saved. I have to toggle the WiFi off and back on, but after I do that, it comes right up. Anyone else seeing behavior like this?

Since I'm on a fresh install with nothing to lose, I wiped everything and installed the M1 build to see if it was something with my phone. That build doesn't seem to have the issue (though it does have others). Reinstalled 9/18v2 and the problem came back.

If other people aren't seeing the same behavior, what baseband do you have? When I have a chance, I'll see if flashing back to an older radio makes a difference.
[Verizon Samsung Galaxy S III] rfmodeler:
I'm on the first 9/18 and have only minor issues like call volume. Never had any data drops on LTE, I stream music from Google Music to my phone and then via bluetooth to my car stereo and it works great. I've found that the LF2 radio is better than the G7 (as far as download speed goes), but I haven't tried any others. I'd say go for it. If you don't like it just restore your TouchWiz backup.

It's now working for me. Make sure you wiped both caches, formatted /system and fixed permissions.

---------- Post added at 01:00 AM ---------- Previous post was at 12:58 AM ----------

No. Go with one of the 9/18 builds. If you read backwards in the forum to the M1 release you will see many improvements.

---------- Post added at 01:02 AM ---------- Previous post was at 01:00 AM ----------

Well, that's the safe, don't do any real research, type of answer.

---------- Post added at 01:05 AM ---------- Previous post was at 01:02 AM ----------

See my previous response.

---------- Post added at 01:19 AM ---------- Previous post was at 01:05 AM ----------

I would suggest the VRLF2 radio/modem/baseband (these seem to be used interchangeably in the Android world). I am getting much better download speeds. Do your own research though since you are probably connecting to different towers than I am. The speed test app is sufficient. Just make sure you aren't holding the phone for the test and your environment isn't changing (put the phone in the same location when you do the speed tests for radio comparisons) and you should be able to see which is better. Holding the phone will not give you repeatable results. Make sure your dog, cat, sibling, spouse, etc aren't nearby when you run the tests. Sit in the same position, blah blah blah. Basically, make the test repeatable and control for as many factors as possible. The only things you want to change are the software and a small amount of time.

I'm a phased array antenna designer so I have first hand knowledge of this type of stuff. Multipath, Fresnel zones, propagation loss, gain patterns, far fields, and much much more.
[Verizon Samsung Galaxy S III] cgulliver:
Make sure you set the wifi region code.
[Verizon Samsung Galaxy S III] THISisTIG:
It was just a suggestion, man. Don't get bent up about it. Nightly releases are for those who like flashing "nightly", want to be on the cutting edge and enjoy reporting bugs, or need fixes for a previously flashed nightly. Everyone is out for something different so if you want a more STABLE release to use as a DD the "M" releases are the way to go. This was already stated by the guys from XDA in the beginning of the thread. I realize they have ironed out a few bugs since its release but more will likely be reported as the new releases get used by nightly flashers. To sum up, RELAX!
[Verizon Samsung Galaxy S III] gdawga4:
I flashed 9/18a yesterday, coming from stock unlocked rooted. Here's what I've found with my first CM10 experience:

What works:

GPS works, turn by turn

Wifi connects immediately (have tested in multiple locations that have saved profiles)

Video recording audio seems to be fine (same levels as ICS)

4G works, no drops

3G works, no drops

Keypad works in-call

No screen flicker

Volume adjustment works in-call

What doesn't work:

NFC (possibly)

I see the NFC menu option and I'm able to enabled/disable as I please but I can't beam to my N7 and vice versa. I installed Google Wallet so I'll have to try making a purchase and see if NFC is working.

Overall, I haven't found anything wrong with the 9/18a build. It's been stable for me in the 16 hours it's been running and I've been able to use it just like before I flashed CM10.
[Verizon Samsung Galaxy S III] Version_3:
To further mention NFC, I had no problems with it when others did. Now I do, with the same symptoms others had, when others have no issues. Clean flashing does nothing.

Which leads me to a thought I had.

To me, it seems as if some of these hardware settings stay with the phone, as if wiping the phone clean does nothing. Those who have radio drops keep the radio drops through any kind of flashing. Same to those with NFC issues. Restoring back to stock seems to help, but maybe only because a stock flash resets those settings - something a custom ROM isn't able to do.

I do see that there is an nv area as it's what is backed up for the IMEI. Has anyone looked at this to see if settings like these persist in the nv area between flashes?
[Verizon Samsung Galaxy S III] peaceofpi:
Good news. Did a clean flash of 9/15 over 9/7. Today Google Wallet would not open until I updated. So I bit the bullet. I have the unsupported device error on the top. But went to DR and bam paid with it no issue.

---------- Post added at 10:33 AM ---------- Previous post was at 10:32 AM ----------

Still on 9/15 here. Let me know how wallet works out. It's my only reasoning I have been avoiding the latest releases.
[Verizon Samsung Galaxy S III] gdawga4:
I'll try to use it tonight and let you know.
[Verizon Samsung Galaxy S III] killerT721:
On build 9/19 now. No problems with data or wifi connecting. Battery still seems good
[Verizon Samsung Galaxy S III] Argent36:
totally forgot that my Nexus 7 has NFC - I'll have to test it with my GSIII tonight
[Verizon Samsung Galaxy S III] alee:
Yes. Has happened to me before. Seems to be only after the first boot post-flash, but afterwards it seems to connect reliably. Check your Wi-Fi region code as well under Wi-Fi settings.
[Verizon Samsung Galaxy S III] PerCompLLC:
It appears that the screen flicker is finally gone with the latest nightly (9/19)! At least it seems to be for me... It was still present for me with the 9/18 nightly.
[Verizon Samsung Galaxy S III] jdommer:
I've been running M1 since it came out. I'm not looking to report bugs, I suppose I'm just leeching off the community. I'm certainly not doing any development. I just wanted to get away from TouchWiz.

M1 does that very well. The nightlies fix some bugs, but add others.

The only bugs I've had with it are: Data has dropped one time requiring a full reboot of the phone - airplane mode would not fix it. GPS is slower to lock on than stock, but does lock on. Screen flickers occasionally, but it's not an unusable flicker - just noticable.

I don't use NFC often, but I use bluetooth, wifi, data, calls, gps a lot with no issues except noted above.

If none of those issues are a dealbreaker for you, M1 will work well.

jd
[Verizon Samsung Galaxy S III] killerT721:
Battery seems to be really good on 9/19 but of course will take a couple of charge cycles to confirm.
[Verizon Samsung Galaxy S III] jdubau55:
Dirty flash of 9/19. I feel like data is definitely improving. Can actually get some connection while in the bathroom at work now. It's 3G, but it is there and working. A few builds back was still pretty bad. I test in the bathroom at work because it's always been tough to get a 3G signal in there. Previously it was pretty much a given that there would be no connection.
[Verizon Samsung Galaxy S III] C0ntr0lfr33k:
Everything seems to work well except for bluetooth. I can't get phone or music to stream through my bluetooth enabled car stereo or bluetooth headset. This is a showstopper for me. This is a clean install of 9/19 build. Anyone have a fix or the same issue?

Wipe x3

Format System

Format sdcard
[Verizon Samsung Galaxy S III] xkookooman:
My bluetooth works fine. Have you cleared all bluetooth settings from any previous install on your phone? Also make sure to clear the settings on the device that's receiving the media from your phone as well. I have to do that with my car headunit everytime I install a new ROM.
[Verizon Samsung Galaxy S III] evandena:
I've had bad 3g drops on every nightly, and no AOKP-J2. Jellywiz 3g is working fine (but the ROM sucks).

I'm going to load up AOKP-J2 when I'm traveling out west. Then we'll know if the data drops follow the phone, or if they are regional. I still think it has something to do with our isolated 1900 mghz network here in Southern Wisconsin.
[Verizon Samsung Galaxy S III] quattr0:
Odd. I'm on 9/18 and no screen flicker. I do know what it means as ive seen it b4
[Verizon Samsung Galaxy S III] chadamir:
Is anyone else here experiencing crashes when using chrome? I have a log which basically suggests it's an EGL issue but since no one else is complaining, I wonder if it's something particular to my phone (need to clear cache or fix permissions etc). I've tried clearing cache and uninstalling chrome itself but it doesn't fix on reinstall. Basically when I try to go to a webpage it simply closes. Sometimes it works.

Edit: Fix permissions seems to have done it.

Edit2: never mind it's not working still.
[Verizon Samsung Galaxy S III] btonetbone:
Hi all -

I am experiencing an odd quirk with bluetooth. I know that this was mentioned by a few people a while back, but it seems like it was fixed or most people. Am I the only one with this problem? It is an ongoing issue since I switched to CM10 in August, regardless of the specific date and whether I have clean or dirty flashed. I am currently on 9/19 from a dirty flash over 9/18b (which was a clean flash).

I have a Parrot bluetooth in my car that only works as a phone profile (not A2DP). Sometimes, my phone and it will work perfectly; when I turn my car on, it and my phone recognize each other and pair. Other times, I will need to manually pair the two devices and enter the PIN number on my phone. It appears to be random as far as when it works and when it fails.

Is anyone else experiencing this or anything similar?

Thanks

Ivan
[Verizon Samsung Galaxy S III] psycho_asylum:
Everything seems to be working well for me today except in-call volume. It worked a few nightlies ago, I don't think I received any calls for the past couple of days so I don't know when it started.
[Verizon Samsung Galaxy S III] kennyho35:
Has there been any ril fixes lately I have tried nightlies up till 9.17 and have had 3g data drops badly with all roms
[Verizon Samsung Galaxy S III] codyvance:
Having car Bluetooth issues as well.. thought it was fixed but it is not.. phone will disconnect from car randomly, have to manually reconnect or restart phone
[Verizon Samsung Galaxy S III] jdhas:
I can't express how much I love that your standard Android ROM testing location is the work bathroom. That's some serious dedication! :good: :highfive:
[Verizon Samsung Galaxy S III] jdubau55:
Hahaha. Well it's the only place that doesn't change. 4G doesn't reach inside yet. Wifi doesn't penetrate. So it's up to 3G and 1X. It's always been pretty low signal since my OG Droid, but was at least solid. That way I know if I get 3G in there now something must be improving.
[Verizon Samsung Galaxy S III] tycoonheart:
Same here.
[Verizon Samsung Galaxy S III] antiseen:
The last one I tried was 9/15 and I was told there was a horrible echo on the other end. I wish that was gone because everything else seemed golden.
[Verizon Samsung Galaxy S III] beaups:
Try turning off wifi, see if that helps. This will rule out a BT/WLAN coexistence issue.

BTW is there a maintainer for CM10 for our devices? Does he/she post here ever? I also own an ATT HOX and H8RIFT is the maintainer over there and is very active with replying about bugs, feature requests, etc.

Over here I feel like we are all just talking to ourselves.
[Verizon Samsung Galaxy S III] cgulliver:
That's what I would call a dirty flash.
[Verizon Samsung Galaxy S III] ugachris:
I'm on a clean flash of 9/19 and this isn't an issue. During the first call, I hit the physical volume rocker, then when the dialog comes up on the screen, drag it to the highest then the lowest volume, then wherever you want it. This worked for me, and only had to do it once.

Otherwise, 9/19 is looking good so far.
[Verizon Samsung Galaxy S III] cgulliver:
Looks like BBQ log has latest merges rather than AppSpot... http://changelog.bbqdroid.org/#d2vzw/cm10/next
[Verizon Samsung Galaxy S III] WhammyDroid:
I am noticing issues as well. Posted a logcat a few posts back.
[Verizon Samsung Galaxy S III] ddggttff3:
post it on the unofficial bug tracker, might get noticed there.
[Verizon Samsung Galaxy S III] Zacharybinx34:
When using speaker call i can't change the volume any where.
[Verizon Samsung Galaxy S III] Ryphez:
I've been having problems getting Wifi Tethering programs working, the 2 apps I have tried are FoxFi and WifiTether. Anyone else running into this issue?
[Verizon Samsung Galaxy S III] rgrossie:
Why not use the native one? Settings--Wireless&network---More... It's right there. I haven't had any problems with it.
[Verizon Samsung Galaxy S III] Durthquake:
I also use the native tether. it works well. I have a widget that turns it on, saves a couple of keystrokes.
[Verizon Samsung Galaxy S III] awmobjects:
I have SuperTooth HD in my car and I have no issues pairing or with anything all!
[Verizon Samsung Galaxy S III] s197:
cvpcs is our maintainer. I don't recall seeing him respond here but then again I don't check this thread religiously. However, whether he's here or not he is a VERY good dev and we're lucky to have him. Ask anyone who has used the GEM series ROMs, which he used to produce prior to joining Cyanogen.
[Verizon Samsung Galaxy S III] toddley:
He's Austen dicken on Google+ for anyone who wants to follow him. he occasionally mentions the GS3 and CM10 but not very often
[Verizon Samsung Galaxy S III] goldsmitht:
I've been having issues with WIFI as well. Read somewhere that if you click on wifi region (settings>wifi>menu>advanced>wifi region code and set it to United States, it helps. Problem, is it wont stick after reboot and then have to go back in. Any way to get this to stick? Would help my wifi connection without having to go back in a set it each boot.
[Verizon Samsung Galaxy S III] XTRoRDiNAiRE:
Will there ever be work on the speaker phone audio? I can't even listen to anything on speaker cause it sounds so bad
[Verizon Samsung Galaxy S III] WhammyDroid:
Does the "unofficial" bug tracker even get noticed the developers?
[Verizon Samsung Galaxy S III] ddggttff3:
Ive seen logs get deleted and moved, so I think so. Better than here in a 300+ page thread.
[Verizon Samsung Galaxy S III] codyvance:
Yeah I checked this and still have issue..
[Verizon Samsung Galaxy S III] alee:
Probably. But let's remember you are on a NIGHTLY build and CM9 took almost a year to be considered final. CM10 is about a month old. It could be fixed tomorrow. It could be fixed in 6 months. If it's a legitimate bug, it definitely will be fixed eventually.
[Verizon Samsung Galaxy S III] the_gonz79:
Is anyone else having issues with Google servers? Im on 18v2 (clean install) and it was working great all day, but in the last hour or so it seems to have lost connection to Google. The bars are still blue, I can check email and calendar, but when I try to use Google Now or Cards, it says theres a sign-in problem. Doesn't seem like a CM10 problem but just wanted to check...