yashsingh1/xdaforums huggingface dataset:
[Verizon Samsung Galaxy S III] M Diddy:
Not sure if anyone noticed or not, but it looks like a fix for the 3G data drops was merged last night.

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

Was curious if anyone can report back if it's better or not.
[Verizon Samsung Galaxy S III] kimsj756:
I think it is for d2spr according to the link you gave us...

Maybe I'm wrong. But I did get a drop on 3g today.

Anyone successful with their 3g?
[Verizon Samsung Galaxy S III] M Diddy:
No, it's actually d2 accross the board. If you look at the comments, Dan (invisiblek) even commented how his d2vzw is handing off much better now.
[Verizon Samsung Galaxy S III] khaoskosmos:
I've been running CM10 for a while now and just noticed it's impossible to send a video mms. You can attach a video file to a mms, but the camcorder doesn't have a resolution lower than 480p and the MMS app doesn't have an increased size limit.

My old palm pre had these capabilities, this kinda sucks even though I don't use it often.
[Verizon Samsung Galaxy S III] M Diddy:
I'm not sure why that is.

When I ran CM10 on my GNex, I never had the problems you see on the GS3 with this ROM. I could:

- Pics taken in portrait would be added to the MMS app in portrait and sent that way.

- There wasn't the drastic degredation in quality of pictures sent via MMS you see on the GS3.

- I could send video, as long as it was taken in MMS quality, with no problems as well.

These things all worked fine on my GNex but not so much on the GS3. :confused:
[Verizon Samsung Galaxy S III] Incredible510:
SD Card issues

Hey guys,

I'm still running the stable 11/13 build and all of a sudden after a reboot of my phone it says the external sd card has been removed.

I've tried rebooting, taking the sd card out, etc, multiple times with no luck.

Anyone else having this issue?

Any suggestions?

Thanks.
[Verizon Samsung Galaxy S III] TechSavvy2:
That's cuz the GNex runs aosp stock, hence why all aosp ROMs run flawless on it. Gs3 doesn't, which is why you have to force it to work....and still not fully there yet.. Its so far off in comparison that I don't understand why it'd even be questioned
[Verizon Samsung Galaxy S III] ddggttff3:
is it just me or is IPv6 completely gone with this update from the 12/6 build?

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

I am no longer pulling a ipv6 address over 4G, and I can no longer access 4g websites (ex ipv6.google.com)

can anyone else confirm this?
[Verizon Samsung Galaxy S III] Argent36:
ipv6.google.com doesn't seem to be a valid address

its ipv6test.google.com and no I'm still getting an ipv4 addy

another would be ipv6chicken.com
[Verizon Samsung Galaxy S III] ddggttff3:
do a NSLOOKUP of ipv6.google.com on your desktop, its googles ipv6 only testing site.
[Verizon Samsung Galaxy S III] funnyperson1:
If you look at the link posted for the 3g handoff fix posted above it looks like the fix changed all apns to use IPV4 like the stock ROM does.
[Verizon Samsung Galaxy S III] nmh5001:
I'm seeing huge drops in LTE speeds lately. Tried the old tricks of fixing permissions and wiping the caches to no avail. I'm currently running at low 3G speeds. On the stock JB leak I was getting mid 30s.

What's up? Tried every modem/rpm combo I could think of with no change.

Edit: This was a local network error. 4G was down for a few days.
[Verizon Samsung Galaxy S III] ddggttff3:
true, but stock still pulls a ipv6 address and can resolve IPv6 domain lookups.
[Verizon Samsung Galaxy S III] htim95:
Is there any way to add the 2 apps on one screen ability from stock onto this? Or is CM planning on adding that to the ROM at all?
[Verizon Samsung Galaxy S III] funnyperson1:
I wouldn't count on it, the Multi-Window stuff is a touchwiz feature and will likely only work with the touchwiz framework. CM might implement something like that but probably not for a long time, I think Google would need to implement it first in AOSP.
[Verizon Samsung Galaxy S III] Version_3:
Whatever it is, holy crap. As an Ingress player, I notice data drops every time because I can't do anything in the game unless I have data. I went out this afternoon, and through areas where I'd normally get 3G and data drops, my phone never once left 4G and I never lost data. I am also using the newest modem leak (and RPM, no matter how unimportant it may be).

However, the BT no-bass issue still persists. I'm thinking of trying to use tasker to automate a quick call when my phone pairs with BT as a short term but automatic solution.
[Verizon Samsung Galaxy S III] funnyperson1:
It seems like the bluetooth fix is waiting on Qualcomm if you look at the bug tracker. So who knows how long that could take. Here's hoping that 4.2 doesn't have that problem.
[Verizon Samsung Galaxy S III] AlexDeGruven:
A good rule of thumb:

If you saw it on a Samsung commercial, it's very unlikely to be in AOSP/CM/AOKP. Sometimes the functionality is already in place with the OS (Now vs S-Voice, S-Beam vs Beam, etc), and that will work, but new features like multi-window and such won't be there.
[Verizon Samsung Galaxy S III] DriveEuro:
I'm with you. The data drop fix is amazing! Getting very few data drops at work now. Loving this. This was my biggest complaint about CM10 based ROMs.
[Verizon Samsung Galaxy S III] sullivan1985:
With the 12/06 nightly, so far I still notice data drops on 3G. This could be because I'm in a shaky area but I'm keeping a close eye. I have noticed that the 4G connection is last much longer into areas it used to drop, but once it flips to 3G its the same old story.

-Sully
[Verizon Samsung Galaxy S III] iofthestorm:
I think CM will likely not do anything like this until Google does, because when they expressed interest in Cornerstone a Google engineer basically said if they did that Google might start taking action to prevent them from having play store access. At the time their reasoning was that it makes it hard for app developers to know how their app will be displayed but I think with Samsung pushing forward anyway Google might realize that especially with huge phones and tablets its a very useful feature.
[Verizon Samsung Galaxy S III] toddley:
Google has actually taken steps to alleviate the developer issue with the new fragment APIs and emphasis on their use in the dev guide. So it's safe to say they are on board with such things at this point
[Verizon Samsung Galaxy S III] Defragger51:
No 4G and very little 3g

This started Monday I have No 4g signal and very little 3G signal so little its useless. I have tried every modem from HE up to the new K3 and still No 4G. I have also tried a variety of roms all the way back to a stock rooted ICS up to the latest 12/06 and still No 4G.I even has a talk with Verizon and they say there is no problem in my area and 4G is working. I know someone else with a rooted SGS3 and they are having the same problem and they are on the cm10 stable build with the HE modem, and I know someone with a SGS3 the is not rooted and all stock and they have 4G service and they live 2 miles from me. Is Verizon blocking 4G service on rooted phones or is there another issues. trying to get back to stock now to test my theory . Anyone with the same problem ? Any idea's? :confused:
[Verizon Samsung Galaxy S III] SymbioticGenius:
currently on 12-7 build. I've tested almost all recent complaints. Only issues I've experienced is the low bass Bluetooth and swyping the browser doesn't auto space or auto caps. that's minor to me. great job devs and testers.
[Verizon Samsung Galaxy S III] iofthestorm:
Yeah I was going to mention that, but I don't think it's completely clear that they're excited about it. Fragments certainly help with a more fluid UI but it's not always going to resize perfectly. I have a feeling that there's some element of them giving Samsung more leeway because they're the top android OEM but at least now if they do something and Google brings up compatibility issues they can point to Samsung and say they did it first. However my opinion was based on a post from a CM developer for the Galaxy Note 10.1 that made it seem like it was completely off the table.
[Verizon Samsung Galaxy S III] sivarticus85:
What about the camcorder recording volume? Is that still low?
[Verizon Samsung Galaxy S III] SymbioticGenius:
I'm not the best person to ask, I never had that issue to begin with, and I don't have it now. I honestly don't remember what it sounded like stock,(wasn't stock long enough to do much) but when I compare videos on CM10 GS3 to vids Ive taken on my DX and DX2 they sound similar. Thats both stock and with CM7 on them also.

One thing I will say is that the signal has greatly improved with the latest nightly.
[Verizon Samsung Galaxy S III] sivarticus85:
I see. I'll have to flash it again and see for myself then. I really like this ROM but I use my camera a lot around my sister's kids and quality is important to me.
[Verizon Samsung Galaxy S III] SymbioticGenius:
I'd wait and see if someone who has experienced it has it fixed. Some people are saying thats its using the wrong mic, some people said its the same mic the TW rom uses. I really don't know, and I have been incredibly lucky reading some of the issues these 600+ pages entail and only experiencing less than a handful of them. I'm sure someone will chime in when it is fixed.
[Verizon Samsung Galaxy S III] Defragger51:
I have gone back to complete un rooted stock and I still have no 4G signal and a very weak 3G signal. I am on my way to the Verizon store now to get a new sim because Verizon says that maybe the issues, if this solves my problem No more CM10 for me, I'll stick to the rooted stock roms. Its unbelievable that I have gotten no useful response about my problem sense I posted last night
[Verizon Samsung Galaxy S III] ajrty33:
Your problem, as you said, isn't related to cm10. Try asking for solutions to your problems in Q&A.
[Verizon Samsung Galaxy S III] Restola:
I posted this earlier, the issue still there as of 12-2.

VZW Galaxy S3 via Tapatalk
[Verizon Samsung Galaxy S III] neyenlives:
No, it's not unbelievable. The fact that you feel entitled to an answer at all is what's unbelievable. Go back to stock and deal with Verizon directly and do not come back to this thread asking about it again. You are the type that is better off staying stock and using what Verizon gives you. That way you can get all crappy with them when you don't get a response.

We have no answer for you which is why you got no response. Good riddance.
[Verizon Samsung Galaxy S III] sivarticus85:
I completely missed this post. Thanks for pointing it out.

---------- Post added at 03:10 PM ---------- Previous post was at 03:03 PM ----------

Dude cmon man.... No need to be like that. Everyone here is still trying to figure all this stuff out. I'll bet you once official JB drops and we get a hold of the source these issues will get squashed. This is an experimental ROM, on a phone it wasn't originally built for. If you want fully functioning AOSP, trade your GS3 for a Nexus.
[Verizon Samsung Galaxy S III] iofthestorm:
FWIW the guy who said it's using the same mic as stock is one of the devs for d2spr and I'm pretty sure he knows what he's talking about so it might be something else. He also said that somehow only d2vzw has this issue which is a little odd.
[Verizon Samsung Galaxy S III] buggerritt:
It's possible you lost your IMEI. Have you checked out this thread on how to fix it or this one for how to back it up, in case you lose it again? "Running away, crying like a little girl, worked out really well for me" said nobody ever.
[Verizon Samsung Galaxy S III] softwarestealer0:
Anyone having issue with gps lock on. Not agps just standard gps. I ask because I have a geochaching app as well as ingress. Both are not really work too well on 12/8
[Verizon Samsung Galaxy S III] mike216:
+1 what's up with people, why do some feel that others here work for them and should be obligated to do all there research for them. I completely agree with you, though I do feel bad for anyone who has bad experiences. This isn't for everyone
[Verizon Samsung Galaxy S III] Defragger51:
Thanks for the usable response. Yes I do still have imei , I still had service just no 4g and a very weak 3g. Thanks again for the concern, as for running away and crying like a little girl sorry to inform you but I have been rooting and roming phones all the way back to the original Droid and never ever have I complained or been impatient but I read the forms most everyday and i see some of the little stuff that goes on and on . Just to let everyone know Verizon gave me a new sim card and I now have 4g service again. Once again I repeat I did nothing to cause the problem I was already running the 11-23 nightly with everything working except NFC and I was ok with that and holding out until something with substantial fixes came along, when for no reason my 4g just stopped working. I will continue to read the forms but will not post for fear of being ignored and then getting my head bet off when I question why no one answered ..Thanks again to all those that have been helpful in the past
[Verizon Samsung Galaxy S III] neyenlives:
You didn't simply ask why it hadn't been answered. You said it was, and I quote "unbelievable that I have gotten no useful response". That carries a tone of entitlement that doesn't go over very well in a community composed of people who do everything for free. So just try to pick your words more carefully bro. :)
[Verizon Samsung Galaxy S III] SymbioticGenius:
Not sure if I came across wrong, my bad. I completely agree its using the right mic, or at least a Mic that works because I have no issues with it.

I'm gonna do more testing after work, but having used this as a Daily Driver since I test drove CM9 in August, this is probably the best its been. No random resets, no more 3 call maximum before I have to reset phone. No more lack of GPS and NFC... which come to think of it, I'm gonna put my stock battery in and test tonight.

My only wish is that they had gotten further with CM9 so all the complainers could STFU, bbut the latest version I could find was from late august early sept.
[Verizon Samsung Galaxy S III] grin0048:
From what I can see (both experimental and from looking at the code/driver), we are not using the same mic as stock. Stock records audio from both mics whereas we are only recording from the top mic (and with a hpf applied as mentioned by that dev). Specifically, we are recording from the "sub mic" device, while stock is using the "handset dmic stereo" device--if you modify the driver so that the "sub mic" has the same configuration as the other, you'll get sound input from both mics. I tried that just as a test though, it's not a fix or even a legit hack--it's just breaking one thing to fix another.
[Verizon Samsung Galaxy S III] iofthestorm:
Yeah I wasn't disagreeing, just providing more context. I personally never use the video feature so I don't know what the situation is.

Interesting thing I noticed from a few days ago, they seem to have made the progress spinner way smoother which makes everything that loads stuff look a bit better. Nice!
[Verizon Samsung Galaxy S III] sivarticus85:
Which nightly are you currently running?
[Verizon Samsung Galaxy S III] SymbioticGenius:
10-20121207 Nightly d2vzw

and not to start this whole thing again, but I dirty flashed the whole way.
[Verizon Samsung Galaxy S III] sivarticus85:
Let us know how this works for you. This is the only thing holding me back from running this as a daily.

Edit: Oh never mind I misread your post. Nothing to see here... :)
[Verizon Samsung Galaxy S III] coldhardtruth:
Anyone know why I would suddenly lose the ability to charge play store purchases to my Verizon account?
[Verizon Samsung Galaxy S III] shinjielric:
I just checked my playstore and I also don't have the option to charge to my account. I think this is Verzion's doing and not the ROM.

I say this because I haven't flashed a new nightly in about a week and a half.
[Verizon Samsung Galaxy S III] softwarestealer0:
I've been using the 12/8 pretty heavy. I don't think I've had a single data drop. It truly is an amazing thing :)

Thanks to all
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Still there for me..

Sent from my Galaxy SIII
[Verizon Samsung Galaxy S III] sullivan1985:
K3 Modem with 12/07 nightly

My 3G is working better than it ever has before! I'm holding it way longer then ever before. Before I got this, I would loose 3G signals all the time at work in the Sussex County, NJ area. Now that I've installed this, it has become a much more reliable connection. It did drop out a few times, but I'm not prepared to put all the blame on the software. service is spotty out that way and always has been.
[Verizon Samsung Galaxy S III] cgulliver:
Anyone else try "Use dark theme" in the built in Messaging app? I don't see any difference in the default one.
[Verizon Samsung Galaxy S III] odub303:
I believe that only applies to the quick message pop up

Sent from my SCH-I535
[Verizon Samsung Galaxy S III] Chris123NT:
Yeah it's only for the quick message popup. Would be cool if they could add an option for the messaging app itself, but I'm really not all that worried about it.
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Download ParanoidAndroid 2.54 and extract the MMS.apk under system/app and push to your phone. You'll have your black mms.

If you don't want to I have it already extracted on my computer I can upload to dropbox when I get home after work in a couple hrs and hit you with a link.

Sent from my Galaxy SIII
[Verizon Samsung Galaxy S III] Chris123NT:
If you could post up a link that would be awesome, thank you.
[Verizon Samsung Galaxy S III] mike216:
+ 1 I would try it also
[Verizon Samsung Galaxy S III] ekklesiaillusion:
15 mins I'll have one posted, im leaving work now.

Sent from my Lean and Paranoid Galaxy SIII
[Verizon Samsung Galaxy S III] ekklesiaillusion:
Heres your dark MMS. It is taken out of ParanoidAndroid 2.54 which is CM10 based so it SHOULD work. I have not tried it. In the zip the dark one is labeled and I included the stock cm10 one just incase something doesn't work.
[Verizon Samsung Galaxy S III] Chris123NT:
Thanks! Seems to be working fine so far, I will run a few more tests to make sure but so far so good :good:
[Verizon Samsung Galaxy S III] sensui123:
Coming from a TW rom now that I see the data issue being resolved....been itchin to go to CM10.....what nice progress indeed, everything is smooth and quick compared to the TW rom I was running and battery life so far has been great. No problems with GPS or Data (After I flashed the latest JB radio leak K3....I had the original radio and I had that dreaded data loss when going into low reception areas and wouldn't come back). Great work devs and thanks to those maintaining this thread.

Quick question though, wifi tether seems to work without flashing that file @ on the original post. Is that file still necessary for some purpose?
[Verizon Samsung Galaxy S III] Flowah:
So, I've encountered this problem twice now. I've been running CM10 on my phone for a long time. I have an MHL cable that works. I know it works with the SGS3 because I've watched stuff with that set up.

I went to go put a file on the SGS3 and hooked it up to my computer. Then, back to the same TV, cable, everything as before. I changed nothing. The only difference was that I had added a video to the SD card.

Now my TV says "no signal" when put to the HDMI where my phone is hooked up to. I've changed no settings at all. I've tried restarting. The first time this happened, I just gave up. Then a few days ago I flashed a new CM10 build and tried it again and it worked again. I'm not going to reflash every time I want it to work though...

This has happened with the M2, and a more recently nightly. Anyone got any ideas?
[Verizon Samsung Galaxy S III] MG386:
not needed.
[Verizon Samsung Galaxy S III] Zacharybinx34:
Skype doesn't work and Google video chat over heats the phone.
[Verizon Samsung Galaxy S III] sensui123:
Excellent. Appreciate that confirmation. Skype seems to work fine for me btw to the previous post above me.....on the 12/7 nightly.
[Verizon Samsung Galaxy S III] antiseen:
Is bluetooth still broken?
[Verizon Samsung Galaxy S III] kench33:
When I used the 12/8 build it was working fine for me. No crackling or anything
[Verizon Samsung Galaxy S III] mybook4:
Have you tried playing music using blue tooth audio?
[Verizon Samsung Galaxy S III] kimsj756:
Sorry, I'm not the guy you asked the question to, but I tested it and the bt audio has no bass.
[Verizon Samsung Galaxy S III] antiseen:
Thanks. Been running touchwiz for a week and miss cm10. Bt isn't a deal breaker
[Verizon Samsung Galaxy S III] RED ZMAN:
Agreed, did this for the first time yesterday and the music and navigation sounded pretty horrible over Bluetooth. Has this actually been reported anywhere officially ? We have to make sure this s*** is being reported or it is never gonna get fixed.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] funnyperson1:
Not sure about the navigation but the no bass issue is on the bug tracker and has like 120 people confirming it across all d2 devices.

One of the devs commented that they're waiting on a fix from Qualcomm.
[Verizon Samsung Galaxy S III] RED ZMAN:
Thank you.

Blasted from my Samsung Galaxy SIII (CM10).
[Verizon Samsung Galaxy S III] d1ez3:
Have the issues with SOD's been resolved? I left CM a while ago due to the phone's screen turning off with the soft keys remaining on and I had to pull the battery (happed 2-3 times a day).

thanks
[Verizon Samsung Galaxy S III] mcp2009:
I still get this a lot when unlocking the phone so I would have to say it is still present and I am on the newest nightly
[Verizon Samsung Galaxy S III] JohnnyTToxic:
Yea, same here. I mash power button a bunch and it comes on, but it's always at the worst time. Although, I've never once had to pull a battery on it.
[Verizon Samsung Galaxy S III] WildBidoof:
Will Bluetooth ever work correctly?

Bluetooth drops constantly with CM10 nightly. Some times i must turn on/off bluetooth for my BTd's to see the phone. Bass is non existent.
[Verizon Samsung Galaxy S III] mybook4:
Imoseyon (kernel dev) has commented that the stock TW kernel forces the voltage for the lowest frequencies to be 1150mv. I've personally run into issues when the lowest frequencies are set below 1000mv (which is what i keep my device at). From my fascinate days, i know that setting the voltage of the lowest frequencies too low can cause the SOD.

I wonder what the stock voltage of the CM10 kernel is at the lowest frequencies. That might be the issue (and why not everyone is experiencing it, as voltage tolerance is very dependent on your specific S4 chip).

I would test by doing the following:

1) flash a kernel with voltage control (like Imoseyon's LeakKernel. Leave at stock voltage (925mv at lowest frequency of 384mhz). Observe over a few days.

2) If you still run into the same issues using LeanKernel, use voltage control to increase the voltage of all low frequencies such that no voltage level is below 1150mv. Observe over a few days to see if the issue is gone. If it is, try lower values to balance stability and battery life (1000mv works for me).

3) Reporting findings back here would prove useful for others
[Verizon Samsung Galaxy S III] jafterdark:
I have a bug to report can't use voice dialing with my bluetooth it acts like the mic can't hear me
[Verizon Samsung Galaxy S III] WhammyDroid:
I've already reported this.
[Verizon Samsung Galaxy S III] cgulliver:
Also reported. It is an issue with the voice dialer which appears to be the same one from Froyo days. Also is routing mic incorrectly. There is a supposed mod that you can convert voice search to a user app and it will prompt you which app to use on bt press.
[Verizon Samsung Galaxy S III] Chris123NT:
Does anyone else have the home button randomly not waking the device issue? It's rather annoying and AFAIK it's been a problem for a little while now.