yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I haven't seen GPS issues since M2 or earlier. There were some reports about flakey GPS last month when everything was messed up trying to bugfix around the old bootloaders. We were forced to update to new bootloaders and those troublesome bug fixes were reverted.

Bluetooth had been better since...idk, RC2? I flashed 5/30 the other day and just noticed this morning that I wasn't connecting to my car w/o toggling. I'm not doing a clean flash to confirm though.

Here's something I read about in the nexus 7 thread that I've experienced consistently but have not seen here. Sometimes if you turn Wi-Fi on (or locale does in my case) it won't connect. If you open the Wi-Fi settings it will. I mean you don't have to tell it to connect, just open the Wi-Fi settings and it does what it was supposed to do in the first place. This has been a small annoyance for a long time but that's about the only thing still bothering me.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Bluetooth has been working great for me since at least as early as 5/17. I have that exact same issue with WiFi, although it seems to only happen when I have very little cell signal. At work, there is barely a bar of 2G, so WiFi is a requirement to get through the day, but it refuses to connect when Tasked turns WiFi on when I get there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cy-rock:
I' m on RC2 and wanted to flash RC4

After reading this:

Flash problem

I have an d2att (rogers) device so i flashed this:

I747MVLDLK4: modem_CWM_I747MVLDLK4.zip

But im running into the same installation problems (assert..)

Any clue ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
DLK4 is for the Canadian version of the phone. DLK3 is what you want.

Also you need the bootloader, not the modem.

~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] cy-rock:
I guess its ok im canadian :)

Sorry i didnt mention it ...

But i was looking for the bootloader page ...dunno if theres any !

---------- Post added at 02:32 PM ---------- Previous post was at 02:28 PM ----------

Here it is Bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cy-rock:
all good :cool:

Its flashing properly now !!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
Anybody having earphone issues?

To be more specific, when ever I try to do a Skype or WebEx call the audio switches to "speaker phone" and I can't figure out how to get it back. I was on a call yesterday and it started out fine with audio coming over the headset then about 10sec on it just switched to the external speaker.

I don't have this issue with phone calls though. Actually whenever I have this issue with WebEx I switch the audio to phone call from VoIP and it works perfectly but this is not always an option.

I know I will get flamed for not searching or reading the forums but I have been search for this for the past week and I have found nothing. If it is there my search terms must be off. So if it was discussed before just reply with a link or something like that and will go do my homework. Again I apologize if this was already discussed and I missed it.

BTW.

CYANOGENMOD ROCKS! I have been around the block, tried a few others but I always come back here. Keep up the great work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
There was a commit in last night or today's nightly to fix VOIP calls (specifically hangouts) but may work for you as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
Thanks, I was trying to avoid the nightlies but for this, but it is definitely worth a try.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
For those of you with data usage reporting issue:

https://plus.google.com/117962666888533781522/posts/jE4Abeoc1Yi
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
Is anyone else having an issue with the last few nightlies where the touchscreen becomes unresponsive? In the app drawer or browser?

I flashed back to 30 and it's working perfectly. But definitely RC4, last night's, and possibly 31 if I remember correctly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
On RC4, don't seem to have the issue you described.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] newmind02:
Really digging the improvements made to the burst shot on the camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I flashed rc4 and it acted really odd. First, the power menu didn't have the advance reboot. I toggled it on and off, didn't work. Toggled developer mode, didn't work. Pressed the home button to close it and the screen turned off and locked.

Anyone else experience this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
There's a new unified Qualcomm ril in 6/1 and enhancements going in 6/2 based on it.

I plan to flash 6/2 when it's built. I'm wondering if anybody here is on 6/1 today...have you noticed any changes in radio performance or battery usage?

~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] villovil:
It seems as if this has nothing to do with the ROM. I flashed many versions and even tried going back to Rogers stock. Nothing.....

Only option I can think of is to try using some other basebands, etc
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Have you tried submitting a bug report to Google? If the S3 isn't working with their app they probably know already but you might get some answers by trying.

~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] theROMinator:
Has anyone noticed the stretched image when the front facing camera is set to 1.9mp?

Of course this can be temporarily remedied by selecting 1.3mp, but I'd like to know if it's a widespread issue.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I see it too.

Front cam

Stretched at 1.9MP

Normal at 1.3MP

Good catch, Romy!

~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] RJQXCV:
Also suffering from this. That and the 720p video aspect bug.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
720p video problems AND 1.3MP camera problems? Now I'm going to have to throw this phone away and get an iPhone. Those have cameras right?

~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] RJQXCV:
I'm not sure they have that. They have Siri though! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
Discovered that it's my charger and the screen becomes unresponsive when I use it. Weird. Don't buy random Chinese knockoffs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Anybody else having problems with camera aspect ratio when changing the resolution?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Read the posts before yours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Read the post after yours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Read the post in between both of yours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshMcMadMac:
I know I am a bit behind the curve, but hopefully I can still get some help here. I finally had a little time to update, from an older (October) build to 0317. The update went fine, and I put the 0301 GAPPS on as well. Now several of the google apps are "stopping" like sound search, google play music, and gmail. I have tried everything I can find, and have searched for everything I can think of. It is as if they are not syncing properly. Things like maps, calendar, play, etc. work. I seem to recall having this issue on a previous update, but for the life of me cannot remember the solution. Help is greatly appreciated!

EDIT: I found the 20121212 Gapps, and that fixed at least GMail. Play Music is still botched, though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] uplift777:
Try reinstalling the apps...:) works for me sometimes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Really you should be running the newer ROMS. A ROM from almost 3 months (wow!) ago is quite immature by today's standard, and totally unsupported to boot (see what I did there). Of course your going to run into problems. There have been hundreds upon hundreds of commits and reverts and tons of debugging done... Why not run the 6.02 ROM? What are you afraid of... being up to date and running smoothly? It all works now. Everything is good. Stop messing with the old stuff... and worst case scenario.. I'm wrong and you nandroid back to your old standby.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
He did update. From an older ROM. Reread his post.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshMcMadMac:
Switching to the 121212 Gapps helped. Then it was just clearing the clock data and uninstalling/reinstalling Play Music. Thanks for the suggestion!

If you have been following this thread you would know that 0317 was the last ROM before 3.4, and that there are things like battery usage that are worse because of it. I do not need bleeding-edge; rather I want the most stable and consistent build I can get. In this case, 0317 is where I want to be. :rolleyes:

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Have you tried a ROM with a 3.4 Kernel? It's super stable and there are no battery issues. Not sure where you are getting your information. I'd recommend you try a 3.4 ROM before you start saying "things like battery usage that are worse because of it". I can't seem to find any recent information in this thread that mention 3/17 being the best CM ROM or even that battery life is affected on ROMs released after that.

Furthermore, a release candidate, RC4 for example is the most stable and consistent build that you can get. That's why they release RCs.

It's time for people to live in the now. Stop saying that Linux 3.4 is awful because you really have no idea. Especially if you haven't tried it for yourself yet. If you want a stable consistant ROM, try the released that CM say are the most stable and consistant ROMs and that's their latest RC.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
This is completely inaccurate. Battery life in 3.4 and with latest builds now surpasses any 4.2.2 release with the 3.0 kernel. Wakelock is minimal and things have really never been more stable.

Ask the CM d2 device maintainers yourself if you don't believe me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JoshMcMadMac:
That certainly is promising. Many posts over the last few months referenced the "lesser" battery life with the new kernel. It makes since, especially when it first merged and there was not adequate core support. It is great to hear that they have improved upon it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LiquidZero:
I have 4G service with CM10.1 RC2 and have no issues with data or connectivity.. H+ networks give me around 16 mbps with a variable ping of around 40-80ms. I can call and watch video at the same time without error.

Hate to say it, but perhaps it's a tower, carrier, or location issue. Perhaps not.

My baseband is T999UVDLJA. D2tmo, T-Mobile, 4.2.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jayharper08:
Thread has been cleaned. Please keep the bickering and arguing out of a development thread. Shouldn't be that hard to give the developer that much respect to not have the childish arguments in his thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks but it's not a tower/carrier/location issue and I have 4G with data no problem. Read through the JIRA report I've created, you will understand better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I read it and I'm experiencing just that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] corno1979:
I updated from rc2 to rc4 (didn't flash rc3) but I have the data reporting bug: it thinks I used about 300MB in a day. Anyone else seeing this on rc4 or later nightlies?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't know for you guys, but Jellybean data calculations were never right for me. It totally differs from what my carrier says and also differs from my 3rd party app with widget that I use to monitor. Would anyone have an idea? I'm not using RC3 too, for that matters.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] comdei:
Anyone have odin flashable recoveries?

I am having trouble after flashing stock...

Can't get a recovery to work...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
It's not because I am crazy why I am replying to my own post. I am just posting here for anyone who might come search for a fix for the same thing in the future.

So, I tried many things as you can see from my previous posts above. I was just about to call may carrier, act stupid and get a replacement under warranty. But instead I reinstalled CM10.1.0-RC4 and decided to use LeanKernel 6.2(Jun-01) instead of KT, BMS or CM default which I tested before. I don't know if this combination of ROM and kernel is the "magic formula" but this what I am using now and I can make calls with all the various VoIP apps that weren't working over the headsets before. (Knock-on-wood :fingers-crossed:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
I want to know more about this before I leave RC4.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
Dude......are you quoting yourself???
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
The last few nightlies I have had full radio loss for 30 seconds at a time and bad radio signal.....also poor battery life. Anyone else seeing the same?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I believe it's fixed on 6/3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
I've only experienced it on 6/2-3 and I'm on 6/3 currently...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
I only experienced it from 6/1 for a few weeks before that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I just installed RC4 and I can't seem to access my sdcard from Windows 7 anymore. I'm trying to paste gapps onto my sdcard and it is giving me an error cannot copy item - the device has either stopped responding or has be disconnected. I tried sending airdroid to my device but it hasn't arrived yet and switching usb modes doesn't help. I tried searching the thread and came up with nothing, any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The LPT:
Try powering off the device. Then booting it back up. A simple restart doesn't help. This is what I used to do when that has happened to me in the past on earlier versions.

Sent from my SGH-I747M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
I tried rebooting, even cleared cache/data and reflashed. I was able to copy the file by putting it in a folder and copying the folder but I don't think this is acceptable for day to day use. I'm going to try to odin back to stock and reflash the latest nightly

Edit: Flashing to the latest nightly fixed it!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VegUnited:
6/3 is the best signal-3g lte edge handoff this device has had since stock. Best battery life since 3/17 as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
The 1st sign of insanity. Lol...

The quote was just for context. Imagine if I just started to respond to I comment at was 3 pages back?

Anyways, I seem to have called it too early. I am back to square one. The issue is still here :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I'm having a strange time on 0603. It seems to be broken but I'm getting amazing battery life. The bluetooth won't connect to my car at all and I can't get any sounds to show except the stock ones. When /sdcard/media didn't work I tried dropping them in /system/media with the stock notifications with no result. I've rebooted 4 times and cleared media twice. At this point my only option is to restore and try again. There is that little matter of battery life though...

1.5hrs screen time

~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] justin860:
Sounds like you need to fully wipe and try again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Great summary of your issue. I believe I was able to see this around 2 days ago when walking outside and visiting and old clock tower. I looked at my battery stats because my battery percentage seemed lower than what it should have been and saw phone standby was taking an unusually high percentage compared to other, similar usage times.

Looking at the graph, there was no red whatsoever meaning I never lost signal. However, checking the phone standby details I saw something like 30ish minutes without signal. Which strangely coincide with more or less the time it took me to climb the clock tower...

I'm glad it doesn't affect me very much, but I could see this very a big battery drain if you were on a "fringe area" like you, whereas in a building or just physically far from a cell tower.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Mphill46:
You just stated when you reverted back to the stock jelly bean rom that you no longer had the problem of losing the signal and not switching over when you are inside the building.

It definitely looks like a radio refresh update ratio problem. I would suggest to flash only the radio and see if that helps.. Are you running a different kernel??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
He meant that the stock 4.1 works properly, as does cm10 - same aosp version. When he updates to 4.2, the handoff is not working as expected, leading to the conclusion that a) the updated android source is having an issue with some bit of cm code or b) the latest radio released so far is not designed with the latest jb updates in mind (most likely imo). He has tried all the available radios, and different methods to update the radio settings - the revert to stock was to check that it was working properly and set a baseline for his tests, as well as rule out a possible glitch regarding funky radio behavior that a revert to stock was consistently fixing for many.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You've got it! I also think that most likely it's an issue with modems from our carriers that are based on 4.1 or even ICS not playing well with a 4.2.2 based ROM. Both have different ideas on network handoff and they aren't working very well together.

I'm hoping that perhaps there are some chunks of code that can be reverted somewhere back to 4.1 that might eliminate this issue. It's going to take a smarter man than I to figure it out.

As for my kernel, this is all on stock kernel but I have tried KT747 and Lean to see if they made a difference and they did not.

I love how there has been 130+ views of my screen captures but not one look at my log cat files.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Does anyone else have this issue?

When playing an intensive game (GTA III in my case) or even just navigating (using google maps nav), the image just freezes, and there is no touch input. Volume button input still works (volume works perfectly). Home button does nothing.

It seems to correct itself after about 5 minutes of being frozen. This bug appeared sometime after a clean install around two week ago. I was updating nightlies over that install since.

Logcat: http://pastebin.com/mFL9pF6K
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I've had that on a racing game (Real Racing 3 I think it's called). I've stuck on 20130520 which doesn't exhibit this issue.

Too lazy to report to JIRA.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I'm willing to bet this issue won't be resolved until the official Samsung 4.2.2 modem comes out for the SGH-I747. Maybe something can be gleamed from the recent I9300 4.2.2 leak but I doubt it...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 2new2care:
Same exact issue here...sucks to miss calls all the time and other data related app issues. But I enjoy so many of the other functions of cm10.1 that I deal with it. Great summary...I hope to see some movement on this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I'm sorry but we don't have the same issue.

I don't miss calls nor do I have app issues related to my data connection.

Guess I wasn't clear in my summary but I'm pretty sure I never said anything about experiencing those two things.

Thank you for your support however.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
I work in a veritable dead zone. As of now, my cell standby is reporting 45% without signal. However my mobile network signal graph on the battery page shows only yellow. No red. But status is showing 0 dBM and a disconnected mobile network state. Strange.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Disconnected mobile state might be because you have an active WIFI connection. Aside from that, it's exactly as I am experiencing though I never have the disconnected mobile state unless I'm on WIFI.

Thanks so I'm not crazy nor am I the only one.

I'm assuming you are running CM10.1? What's your carrier? I should also as if that when it was showing 0dBm did it show you were connected to 4G in your status bar or LTE in your phone status?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
Someone posted a day ago about great battery life. For months I've been getting mediocre battery life with nightlies. After 1 h of display time I was near 15% yesterday. I have auto brightness on. My battery is about 10 mo old. Somewhere along the line (maybe the switch to 10.1) battery life suddenly decreased, it seemed.

Unrelated problem: I have a weird directory structure on the SD card with multiple nested "0" folders and several "emulated" and "legacy" folders which seem to contain the same files. My card is almost full but I can't copy my photos because DCIM and most of the other folders don't show up in Windows when I connect the phone. With MTP I see only a few random folders and with camera device mode I see no folders. Permissions appear fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
Yup, running 10.1, June 4th nightly. Carrier is AT&T. And it does show connected to 4g when the signal is at 0dBm.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Excellent, someone on a completely different carrier and a different varient of the phone. This once again goes to show that it's not a hardware or carrier problem.

And the Disconnected Network State? Is that because you were on wifi?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
Yup, was on Wifi. After reading your posts and some of those external links you provided, I'm really leaning to this being an issue with the modem not being optimized for 4.2.2. Not sure what can be done until we see the official updates roll out from the carriers, then pilfer the updated modem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Your nested 0 folders are there probably because you went back to cm10 at least once. Every time you upgrade to cm10.1, the file structure is reorganized for multi user support. There is a zip floating around to fix a nested level.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
is anyone still seeing the data usage error? i know there was the google+ posting about how it was fixed, but I just got a notice that I had used 2+gb in 2 days. haha.