yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] heaiser:
Gotcha. Yeah that's what I'm being told too running the latest update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
stable releases for sprint & verizon

http://download.cyanogenmod.com/?type=stable. You know something is wrong when sprint and verizon both get a stable before att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ceredics:
:beer: here's to hoping ours gets uploaded next so I can do a ota today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
ATT build failed so lets see if it gets another try a little later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Whoa. Even my old sgs1 captivate got a stable CM10.0.0 this morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ceredics:
Thanks for the info bud
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Yeah, this has been a thorn in my side for the last three weeks solidly, through multiple full wipes and the latest builds. Why, oh why? :)

Thanks for the workaround, even if it is a hassle. Much appreciated! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Has anyone else seen lockups under very specific situations? I'm still running through some different scenarios but I can get the phone to lock up 100% of the time under the following circumstances:

Any of the cm10 nightly builds 11/8 or newer

Stock kernel

4.2 Gapps (Was running them before the issue started)

Streaming audio from 8tracks over Bluetooth audio (never a problem until this week)

Now I'll have the clock on, in night mode, while streaming music from 8tracks, and generally within about 20-30 mins, the phone freezes.

I got a logcat of it, and it appears to be as a result of an out of memory error starting at line 146 right before surfaceflinger blows up into pieces :)

http://pastebin.com/d4TQxUyh

I'm out of ideas at this point, although I might try going back as early as M2 to see if that alleviates it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ceredics:
Hold out until we get the stable, if its not out today then probably tomorrow. Then run your test again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
Ok everyone whenever 4.2 is on our device it will be CM 10.1 https://plus.google.com/+CyanogenMod/posts/1FLFe2RzYZ7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rcook55:
Interesting, thanks for the information. What I've now found is that this is only occuring some of the time. I can have my phone and desktop client open, delete an email on the phone and sometimes it deletes the email on server and that is reflected on the desktop client other times the email does not delete. I don't recall this ever happening w/ stock TW or my iPhone/iPad. Now the Exchange 'admin' if you want to use that term has less than a clue as to what he's doing so it's entirely possible that the server is configured wrong. I think that when the M3/Stable build drops I'll do a complete wipe of the phone and reset everything as I shouldn't be upgrading a bunch more at this point. Hopefully that will correct the issue or at least remove any possibility that it's on my end.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Stable doesn't necessarily reflect a huge difference in code over the existing nightlies, it's just a milestone that says the rom is "generally" stable and no major changes are on the horizon. This bug could easily still be present in the stable based on the current changelogs and what I'm seeing on Gerrit.

Interestingly enough, I think it may have had to do with the 8tracks widget, which isn't necessarily related to the rom, still needs more testing which I will have to do later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
ATT build is in queue to compile next.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] javadahutch:
"Extra gain in voice calls" setting does not stick after leaving advanced screen.

Cm10 11/11

kt747 kernel 10/31

Wipe cache...format cache...wipe dalvik... wipe system&data
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Senor Forum:
That's amazing news, man! Looking forward to it.

:)

The hard work is always appreciated.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dx9:
Get it while its Hot guys

http://jenkins.cyanogenmod.com/job/android/12630/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Senor Forum:
*trips over own feet*

:victory::victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
4.2 Gapps? This is not 4.2. Run the older Gapps and try again. It is supported according to Task where as 4.2 is not. It could easily be the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nklenchik:
Is this based on 4.2? Very anxious
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Nope. Sorry. 4.2 will be CM10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
No that code hasn't been released to AOSP yet. If it had, it would be tough to get it as a stable since there hasn't been any builds released yet at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
stable is out. http://get.cm/?device=&type=stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abbz123:
will this show up on cyandelta?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djthread:
USB Digital Audio Out

Hello CMers!

Has anyone heard anything regarding progress towards bringing digital USB audio output to CM10 like Samsung's TouchWiz roms seem to have?

It seems like a simple enough enhancement that would make a ton of aurally-inclined folks happy... I think the right people just aren't involved. :)

I would gladly send a compatible device to a dev willing to work on it, help test, or anything else that would further this cause.

Surprisingly, this is even the 5th most starred issue on the AOSP project! http://code.google.com/p/android/issues/detail?id=24614

More links:

http://xdaforums.com/showthread.php?t=1820411

http://www.head-fi.org/t/595071/android-phones-and-usb-dacs/

<3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
Thanks man...I've installed it and restoring apps as it type this:)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
504 Gateway Time-out

nginx/1.0.5
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
I'm aware that it is unsupported, but I was performing the identical procedure I outlined on a build I did on 1105 with the identical 4.2 gapps package, without the lockup issue. Enough people are running 4.2 gapps without having this particular issue reported, and I'm sure it's quite an isolated incident.

Also, if you read my latest post, I may have narrowed it down to an errant widget.

If it wasn't clear from the nature of my post I was not looking for broad, sweeping and condescending answers. I was looking to see if anyone else had experienced a similar issue, not random guesses about what it *might* be. There's a reason why I provided a logcat.

I'm sure I'll get flamed for this. :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Download directly off Jenkins, there's a link further up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I think I am gonna stay on this stable build for a while instead of flashing the new nightlies like I have been for the past few months. I may flash a nightly if I see something that I just got to have.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
+1 that server is much faster!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
4.2 is on the servers so we may see cm 10.1 within a few days. http://www.androidcentral.com/android-42-code-hits-aosp?utm_source=ac&utm_medium=twitter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
USB Audio works in CM, the problem is now Bluetooth Streaming doesnt (no bass)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Was on the 11/11 nightly before upgrading to the stable. My usual method for upgrading the nightlies was to wipe cache/wipe dalvik/format system and then install update and Gapps. I know I'm not *supposed* to base performance on Quadrant scores, but the stable has dropped my scores from 4600's on the nightlies to 3600's. Anyone else see this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
Same here, though phone seems pretty snappy so I'm not worried to much about the benchmark.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
How's the stable version for the ones that loaded it already? Any problems with bluetooth and call echoing?

Any negatives thing to say about it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
4.2 finally went aosp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Odd, same procedure on the HOX didn't affect scores.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
I can't speak for echo'ing yet.

I installed stable over 11/8 with a dalvik and cache wipe about an hour ago. My phone has gotten the sleep of death twice since then. The menu and back buttons light up, but the screen never turns on. I have to hold power and home in order to make the phone reboot. Anyone else with this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
Figured out the default governor is interactive... changing it to on demand helps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JMP1147:
I had that on the last nightly, havnt experience d anything like that on 10.0.0 but you probably need to let the battery drain all the way then charge it. Worked for me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
yes, ive found hitting the power button about 5 times then waiting 5-10 seconds will activate the display.

odd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Changed it and just got 3336 as a result. Perhaps a wipe and restore is in order?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] doctorspeed1:
FYI A2DP bass is working on stable build. I am using power amp.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
Did you reboot?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
To those experience sleep of death or anything related to display shutting down, I find that LeanKernel helps a lot with it.

I've been running it with the nighltys and am right now with the latest CM and it seems like a great combo
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ladd76:
Echo

If by call echoing you mean the person on other line hearing echo when u enable speakerphone, yes it's still there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Yes, and I made the settings stick via checking set on boot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vw671:
That's werid...I get at least 4,500-4,700 after changing mine to interactive without overclocking.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etiin:
is wechat push to talk working for anyone?

nm gotta turn off low-bitrate recording and use top mic :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] brownsmell:
OpenVPN

Hi Guys,

Surprisingly in 600+ pages nobody mentioned OpenVPN.

I have:

S3 i747 Rogers (AT&T d2att) running latest nightly 11-11.

I want:

OpenVPN working over wifi and ** also over data **.

OpenVPN is preinstalled in CM10 so all one needs is the OpenVPN Settings app. I installed busybox just in case it wasnt preinstalled.

The Problem:

VPN traffic works using OpenVPN Settings over wifi but it does not work over data. It seems to be a routing issue because OpenVPN Settings successfully connects to the VPN server, but

no traffic is routed over the VPN Connection.

The traffic goes straight through my data connection, bypassing the VPN.

The data connection requires going through an http proxy (Speakout/PetroCanada) on port 80 before it connects to the server I hope this is not a problem new in CM10. I have verified that the server, client files, and routing all worked on my p500h with cm9 so this problem is related to JellyBean or the S3. Other roms I tried that didnt work with OpenVPN over data: Liquid, Ariel, Stock Rogers

Any ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Senor Forum:
So I've done a full wipe twice now, and the stable is giving me a lot of display issues.

My screen will just randomly go black, and holding my power button down for a while to reboot it is the only thing that seems to work with fixing it.

Just a heads up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bostonirishguy13:
Ok, just got a 4743. So all is good. No other issues at all so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CZ Eddie:
He was asking about Digital USB Audio though. Not Analog.

The Analog USB Audio is working now with OEM Samsung docks.

But digital USB Audio is different and afaik, still not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Wasn't this fixed for a short time? Or am I just remembering back when we first got the CM10 builds in July when the bug wasn't present?

Also, I confirmed that when you get the sleep of death, hitting the home key 5-10 times will usually wake the phone up. Hitting the power key multiple times definitely does not. This has made my phone work up properly the last two times I've gotten the Sleep of Death, which raises my total to 4 sleep of deaths in about 4 hours...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cellgeek:
Call quality on CM10.0

Just updated to CM10.0 using baseband I747UCLH9 radio on my S3. Traveling on business in California; San Mateo to be exact. Call quality is terrible. Keeps jumping from 3G -> H+ ->4G and eventually drops the call. Has happened on my last 5 calls. Down-link quality is really quite bad as call is consistently garbled.

When I go back to ICS UCLH9 semi stock call quality is fine and reliable. The M2 build works reasonably well also.

Also noticed that while in Settings->Display when you disable the auto rotation the display freezes until you re-enable the auto rotation.

Sigh.......

------------------CM10.0 Reinstall with full wipe

After reinstalling with a full wipe, the Settings->Display lockup went away. Call quality and caller echo are still really bad. Since this is a work phone most of the time, I'm back on UCLH9 until the echo problem gets fixed. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Whew, glad I'm not the only one experiencing things like this.

I've ruled out a couple of possibilities, it's happened to me with or without bluetooth, with or without wifi.

Each time I've had the app "8tracks" streaming music while having the 4.2 GApps night mode activated, and the phone has been plugged in.

Have you been able to reproduce the SoD's with a specific set of actions? if so, I suggest opening a terminal, do "su" then "cd /sdcard/" then "logcat > logcat.txt" and let it run in the background. It should catch something and it would be nice to compare your logcat to mine to see if the underlying cause is the same.

Please have a look at my original post for my logcat.

http://xdaforums.com/showpost.php?p=34060950&postcount=6610
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smashcz:
No bass over Bluetooth is still there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
Thank you for correcting me, just wondering what is the difference? apart from the obvious one being analog and other Digital. is there a huge quality improvement?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
Think we will see 4.2 merged tonight?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
doubt it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
very seriously doubt it. All the devs I umm "stalk" Follow on twitter says they will be too busy playing black Ops 2 and it takes a while to synch and all that so will be a few days.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joe772:
Any special instructions for flashing CM10 stable? Do we need to wipe anything different?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] joker96:
hi

i was just wondering if this cm10 build has Vsync working with project butter. the reason i ask is i am looking for a replacement of my current phone and i want something that has JB fully running. thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastergrillo:
Same here but i did a dirty install did u try a clean install?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Nothing special, no, but milestones should really get an honorary clean wipe. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djthread:
Proper USB DAC support is entirely different from what has been just merged in. It would allow you to connect the device to one of many different outboard DACs and drive them just like a computer can. With a high quality DAC and amp...

This would allow you to get "serious" audiophile type of performance... as good as anything, in theory, since it's the pure bits coming out.

So yes, with the right equipment, the sound would be hella-better than the S3's built-in DAC circuitry. See head-fi.org for other crazies like me :] Check out Ray's Intruder (fully balanced DAC/amp) for a slice of aural paradise. (disclaimer: I'm close with Ray.)

How is this the #5 most starred issue on AOSP and still no love!?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Thanks!

So according to the last few posts here, this last stables version doesnt seem that stable with the echoing and bluetooth problems still there... Really wondering if I revert back to M2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Andrew149:
I'm not having any issues at all of course I don't use Bluetooth as for the echoing idk I use voxer to talk to everyone

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MildSe7en:
clean install of the stable version.

instagram still doesn't work, after taking a picture you cant see the previews

and the camera still freezes if you take a picture in auto mode (prefocusing works as before)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djHandy:
Excuse my ignorance, but what's the benefit of this? How would you use it? In a car dock?

My only complaint about the S3 is that the USB is on one side and audio on the other. Messy when set up in my car.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Yea, I use bluetooth pretty much every odd day and well the echoing I just dont want it! So I'll wait till there's a good solid "stable" rom out there before making the switch!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
The stable build from today also has no bass over bluetooth for me, same as the last nightly. 11/8 works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wired_In:
A workaround for Bluetooth quality issue:

1) Start streaming music over bluetooth.

2) Make a phone call over bluetooth (611 is fine).

3) When you hang up music should be streaming with full quality now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjohnnyblaze:
I think this has been brought up in the past but Voicemal Notifications do not work. I dont know if this is service provider specific or not. Yes I have entered a valid voicemail number and checked all my service settings. I can call my voicemail and check the messages fine but I cannot automatically receive missed voicemail notifications. Missed call notifications work however. I have tried many different recent nightlies as well as the newest stable release from today and it still does not work.

Running:

Samsung S3 I747 (d2att)

CM10.0.0 (d2att)

stock CM10 kernel

no other modifications

Service provider is Bell.

Any help on this matter would be greatly appreciated as this is the only thing i am currently having trouble with (everything else works great)

Thanks in advance.

EDIT: apparently there used to be a patch/fix for this issue. Is this still being implemented in current builds? http://review.cyanogenmod.org/#/c/13322/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Randomacts:
so yeah.. in call echo is still here

I'll update the offical bug report in a bit.. I'll get another logcat..

Edit: I updated it

Everyone if you have a bug PLEASE report to the official bug tracker as this is a stable rom now we can report.

https://code.google.com/p/cyanogenm...work+Owner+Summary+Stars+Priority&cells=tiles
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jproy12:
Here's my same exact question...

http://xdaforums.com/showthread.php?t=1948055
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
I'm on the Bell version, running the stable CM10 from today, and just confirmed that my OpenVPN setup is routing everything through the VPN while on H+ Connection. I'm pretty sure it was working for at least the last week or so of nightlies, but can't say 100%. Not sure what might be different between our setups. I'm on Bell, but I don't imagine that would make a difference unless Rogers has your VPN server blocked for some reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djthread:
It's purely for the sake of sound quality and the ability to interwork with USB DACs. There are *many* such devices on the market that are compatible with a generic usb audio driver in the linux kernel. Check this post for a list of some.

There is a group of people who want to use their phones as a source for high quality listening, connected to a really nice pair of headphones or speakers. And Samsung's work for the S3/Note2 TW roms seem to be the only method.

It seems the only work needed is a way to route audio from the Android system layer (apps) to the already recognized device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
so now that 4.2 has been added to aosp, will this be part of CM10? or part of CM11?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jebise101:
it will be CM 10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
When i made a phone call over the dock while my audio was routed through my stereo today on the stable build, the echo was there for the person i was talking to. So, although dock audio is working great for music, getting a phone call will result in echo until that is fixed again. I'm just happy i can listen to my Google music now in my dock again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zerojay:
Using tonight's new stable build, I am *not* experiencing the camera crash people have mentioned before focusing. In fact, I haven't had that on the nightly builds either for a little while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mtl171:
Works like a charm. Only issue is how the people(contacts) app constantly crashes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
I submitted a bug report for the lack of bass using bluetooth audio. Please go view/add useful information not already in my report/star (best way to get things prioritized) to assist the developers in working on this: Bug report
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] davis9491:
New stable release is great. The nightlies were great to. Only one build had camera issues that was corrected on next build. Everything is working great (except voice dialer vis Bluetooth which is JB issue I think).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phzi:
Like many others have posted here, after I flashed the stable build i was having an extremely difficult time waking the phone from sleep (10+ presses sometimes necessary to wake the phone). For now I am back on 11/9, which is bug free for how I use the phone.

At the moment, I would strongly advise against flashing the "stable", or 11/11 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
Same here, i experienced this with CM10 and AOKP.