yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Money, it's a crime

Share it fairly

But don't take a slice of my pie...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] khunfused:
in the downloads what does rc stand for and how stable is the final release of 10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
RC stands for "release candidate". 10.1.3 RC2 was excellent for me before finally moving on to the 10.2 nightlies. I suggest you try it for yourself since every device can handle it a little differently.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
10.1.3 RC2 has been solid for me... . very good for daily use I use it everyday with kt747 kernel :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TKG26:
Any ideas why i get error/Fail when i attempt to flash nightly?

TWRP 2.6.3.0

usual full wipe

error when i flash rom:

no md5 file found

assert failed: getprop ("ro product device")=="

e: error executing updater binary in zip.................

error flashing zip/ external sdcard.............

fail

---------- Post added at 02:25 AM ---------- Previous post was at 02:18 AM ----------

uhh? Rolled back TWRP to 2.4xxx and it flashes.... loading now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Noticed the recent nightly 09/21 has file size 176.28MB. I did not flash it nor wanna take the risk.

You're warned!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
The only time I have ever seen that error was when I had the d2can recovery installed instead of d2att. I747M phones can run the d2att recovery and is the easiest way to flash without editing the updater script. The other workaround of course is to go in to the updater script and the line for the device check can be either removed or edited to check for d2can. Pretty sure it's the first line in the file should you decide to use that method.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
They removed Focal. Maybe that's why.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Flashed 9/21 already. It's fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
Signal Strength

Thought I would share my signal strength on the Sep19th Nightly. I am on Tmobile in the South East. After dirty flashing the the19th Nightly I had trouble acquiring good signal even in the areas where it was full. It stayed that way for hours till I decided to use a free app call Signal Booster (I think it resets the radio plus reconnects to a better tower). It has been fine since then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Been noticing the same on 09/21
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klef25:
I was wondering if you found any more info about usb dock audio. I just updated from CM10.0 to CM10.2 nightlies and seem to have lost the usb dock audio. I can't find it in the settings, so I assume that means that they removed it. It makes docking the phone in my car a little more of a hassle (I loved snapping and sliding and not messing with any cables). Does anyone know of any workarounds to get it working again?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Monkeymannnn:
I sincerely doubt focal is 20 MBs and CM has been about 180-190 for a long time now. Something important got left out or they're gutting it even further now that they're officially going commercial.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sgp77:
Focal from the app store is 16.69MB. I've been running the last few nightlies without problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Try my Quantum rom. I fixed the dock audio and it's basically cm with tweaks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Did a full clean install of 1.65 this morning.

accelhandler error still showing up in logs...

CM has a bug in the Rotate Display code.

ACDB AFE = -8 still occurring

Audio Calibration Database

Completely in love with the Quantum boot screen - probably only need "Pwncakes" displayed on one of the 2 boot screens for tidiness sake.

Now all I'm missing is dual boot and usb->hdmi convertor so I can run linux on the S3 in terminal mode on a nice big monitor so I can be a unix geek.

---------- Post added at 02:36 PM ---------- Previous post was at 02:34 PM ----------

... on a slightly related note... Is there a build environment VM floating around? It would be nice to hack in dual boot if no one else is going to take it on for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
so I dont know if its just me, but when I go off wi-fi, I see my network is off till I enable it. then all of a sudden I see the text's and such I didnt receive. anyone else notice this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I'm pretty sure then it is broken for the last two nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klef25:
Is this based off CM 10.1 or CM 10.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
10.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vegasdiceshooter:
Google wallet supposedly is now available for all phones and all roms I have it on beanstalk from play store
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
10.1.3 stable is out, go get it.. Final release for 4.2.2 based on cm with latest update code...

Hit thanks button if this helped..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rvash:
Does the front facing camera work on 3rd party apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Yes it does work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
10.1.3

1.) Do all games (subway surfers etc) work fine on 10.1.3 stable?

2.) Does the front facing camera work fine with the 3rd party apps like cerberus on 10.1.3 stable? it crashed previously

could someone tell me? tried the previous stable and had these 2 issues, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
No these issues are not fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
The issues I mentioned?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You have to take what matrixzone says with a grain of salt.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry, what issues we are talking about please.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
1.) Do all games (subway surfers etc) work fine on 10.1.3 stable?

2.) Does the front facing camera work fine with the 3rd party apps like cerberus on 10.1.3 stable? it crashed previously

could someone tell me? tried the previous stable and had these 2 issues, thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Hey disregard my other post, I was 100% sure you were talking about RC2. I didn't notice stable was out, neither that you mentioned it. I haven't tried it yet, so I can't comment.

Don't post before your coffee!

Also thanks flex for your watchful eye. x_x
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spotdog14:
How are the most recent nightly's running? I'm currently on the CM-10.2-20139014 and have had some reboots and memory leaks if I don't restart every few days but overall its been good. I have heard that with the most recent nightly's there is a problem with data switching between wifi and mobile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
Thanks

I have installed 10.1.3 , the issues were not fixed- subway surfers stops at blank screen, and using cerberus causes phone to freeze and reboot, like in the previous stable versions..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I second you. Just tested, front facing camera still causes a reboot. No surprise there.

Edit: No surprise since there were no commits regarding this. Just to make things clear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you please pull logcat and open bug in CM Jira, if possible?

---------- Post added at 02:46 PM ---------- Previous post was at 02:45 PM ----------

URL for CM JIRA:

https://jira.cyanogenmod.org
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
You're funny.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Can you share the logcat please

---------- Post added at 02:54 PM ---------- Previous post was at 02:51 PM ----------

I will call that helpful
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, a logcat of a reboot...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I don't understand how they can release 10.1.3 as a stable release if the front facing camera doesnt work with 3rd party apps. Seems half-assed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Still crashing when using instagram for both video recording.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
I'm going to switch carriers from AT&T to T-Mobile. What is the best way to convert a d2att to a d2tmo? Phone is unlocked (though I'll check with the new SIM before I flash).

I'm running 10.2 d2att nightlies. Is it really risky to dirty-flash d2tmo 10.2 over d2att 10.2? I would imagine the ROM differences are few since the phone is identical. When I get my new SIM card, should I exchange it before/after/during the flash? Thanks for any help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Those who compile roms don't necessarily own the devices. Can't blame them.

But hey, I come from the Nexus S world, and back when CM7 was the thing, the stable wasn't even stable either. At least the d2att CM10.1 stable IS stable as far as I can see, minus a few glitches (HW overlay + front facing camera in third party apps)

---------- Post added at 01:10 PM ---------- Previous post was at 01:08 PM ----------

Whoa whoa whoa, don't do that! Don't flash d2tmo on a d2att.

Plus, you're gonna run in a few issues. Such as 3G being troublesome to have.

See here:

http://xdaforums.com/showthread.php?t=1771021
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
If you're already unlocked, just put in the T-Mobile sim. Done. Continue flashing d2att ROMs, as that is and will always be the device itself.

Source: I switched from AT&T to T-Mobile myself on this device.

Edit: read about any radio issues you may encounter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VQ30DE:
K thanks--my other question was whether I even needed to re-flash. It looks like the AT&T lacks the radio equipment to use the T-mobile LTE band, but not vice versa. :( Damn

---------- Post added at 12:40 PM ---------- Previous post was at 12:31 PM ----------

Thanks! So what is your data like? I haven't read the whole thread polobunny linked to yet, but it appears there is a hack to make HSPA and/or LTE work on T-Mobile with the i747, but it may not work with custom ROMs. Are you getting 3G/HSPA/LTE on the T-Mobile network?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Sorry if this sounds rude, can someone please share the logcat who are facing the reboot on using 3rd party camera app

Edit: We don't have any bug opened in CM Jira for this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
logcat gets cleared at every boot, you know. Hence why you're not seeing any logcat.

Can't be arsed adb'ing to my phone at work and dumping it live.

The issue happens to anyone using CM10.1/CM10.2, so if you're using one or the other you should be able to collect what you want/need.

Oh and have fun at the JIRA with their silly requirements. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So, has anyone noticed any performance improvements coming from 10.1 to 10.2? Just wondering, as that is the one thing that would make me wanna switch over to the nightlies from my rock-solid 10.1 build.

TRIM support making a difference, maybe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sprke:
I had the audio bug as well...flashed back to 7-27 hopefully the next build clears it up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
Just out of curiosity is there anything wrong with the 7/30 build? I just downloaded it and see it's been pulled..

edit: I'm dumb, ignore.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Never saw/heard anything about it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
Just flashed 7/29 build running smooth for me. No issues so far. Thank u CM team.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
How'd u DL a 7/30 build? The OP hasn't been updated since around 5am the 29th. So the "last edited" tag says atleast.

Sure you downloaded this ROM? I accidentily downloaded CM 9 nightlies thinking they were CM10 preview updates a few times myself. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
we're having similar issues w/ aokp

heres someone elses post on the aokp qa thread, anyone on cm10 try this?

corythug: Got call sound working but only with dial tone and touch tones on... Its worked every time with those 2 on. Now what bothers me more... System sounds or speaker phone toggle... Lol. Edit; no need for dial tone, but touch tones must be on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Directory indexes are enabled for http://android.chemlab.org/previews/, so that's probably how. Not a smart idea to download before the OP is updated, though.

Yep, I had left dialpad touch tones enabled (default enabled), but turned Touch sounds off (default enabled) because I hate hearing the little click every time I touch any button. When I re-enabled "Touch sounds", call-audio for each outgoing call was fine again. The touch sound button presses are probably just resetting the audio system in between calls as a happy side effect. Still, I hate touch sounds so much that I'm keeping it disabled, and am using the speakerphone toggle workaround instead. :)

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ghstudent:
have you tried this? http://xdaforums.com/showthread.php?t=1801997
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
As soon as I saw what had happened, I got rid of it ASAP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ghstudent:
you got rid of your phone or the issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bbgt2:
I may be just to damn blind or are the NFC settings just not on this build?

Did the GW fix but can't seem to find where to enable NFC settings.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
I've got it. Look under settings > more. If you still don't see it you might have flashed something such as a kernel or theme that made it disappear.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] outz:
I'm with you. I'm running the first jb aokp which doesn't have this call bug... no way I can deal with touch sounds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
The phone. At the time there was no solution.

AOKP jellybean by TGFY
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xnerdx:
Getting getting an error on every recovery out touch and non touch, has to do with symlinks status 7. Cm9 nightly works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bud951:
What file explorer are you guys using? Im using ES Explorer but its FC'ng alot. Great rom so far. I use this as my daily. Remarkably stable with only a few issues. Thanks CM team! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Go and buy root explorer it is the best and definitely worth it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] amgpower63:
+1

I'd definitely recommend it if you're into modding your phone
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] msgnyc:
I agree with Moh_Jay.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I use File Manager(Free)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Try Quantum based on 10.2, rock solid and stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I tried it early on, not as of late to be honest and there's jack $#!+ difference. CM10.2 seemed even a bit slower.

Take everything with a grain of salt since I didn't try the latest nightlies, but that's that.

That's why I'm sticking to 10.1 for as long as I can, don't feel like dealing with new bugs for the sake of it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Okay, thanks for the input. I had the same experience with going from 10.0 to 10.1. The performance just wasn't there until the later milestone builds.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I did exactly the same. I used to be interested by the latest stuff available, but I feel like the nightlies, RCs and stables have been getting progressively less polished over time since the earlier CM days. Guess that's what happens when a ROM gets thrown on a few dozen devices instead of a select few.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Can anyone tell me what the x in a circle icon is in the top left corner of the stock cm camera? Been wondering for ages.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Saving location details in photo EXIF data. Change it in the camera settings, it's like the third option. Yours is enabled. =)

Edit: Don't put your shoes on the couch yo. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I put ma shoes where I want!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
First, it works fine with the stock camera.

Second, it works fine with Snap Camera HDR which is a third party app. If you check out his app changelog he even has an entry about fixing the front facing camera on the S3. This to me sounds like it's not a CM problem but something with the way 3rd party apps are accessing it. Might be something to do with the way CM is compiled but in the end, the app devs can fix the problem and CM's stock camera works so let's stop blaming them and saying their stuff doesn't work.

Don't believe me, download the free trial of snap camera HDR and see for yourself. It works. http://xdaforums.com/showthread.php?t=2055140
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
But because of a CM change, ALL apps would be forced to change their code. That seems a bit backwards, no?

Furthermore, this issue isn't present on stock rom for the S3, which only re-enforces putting the blame back on CM team.

I don't think we should be expecting software updates from all providers for such a small subgroup of users (d2xxx using CM?).

Edit: Might be nice contacting dzo directly to see his fix and just provide said fix to CM. Hands-on approach usually works better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Does the hdr work in snap camera on our phones? I was under the impression that no hdr worked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
So was I. Maybe the app / camera applies a filter to make us "believe" that HDR works. As far as I know exposure in our camera is borked so HDR shots just result in blurry pics that sometimes come out sideways.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] WarningSLO:
There has been one open for a while here: https://jira.cyanogenmod.org/browse/CYAN-1504
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Exact. Exposure is broken.

Also I contacted dzo from Snap Camera HDR and he clued me on the fix, which I reported on the JIRA issue. Fingers crossed... maybe.

BUY HIS APP. ITS PRETTY SWEET AND I SUPPORT PEOPLE FIXING THINGS AND MAKING GOOD SOFTWARE.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Do we know WHY exposure is broken? Is it across all devices?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mahler47:
No, not across all devices.

See https://jira.cyanogenmod.org/browse/CYAN-79
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Oh and I meant fix for front facing camera causing a reboot, not the exposure (sadly).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I hate that I'm a flash o holic. Newest 10.2 nightlies suddenly broke Wi-Fi and a whole two of us mentioned it here. Really? Wi-Fi? At this stage? Oh, and battery drain while in use seems about a percent a minute. I'm running a few days ago build and am about to try latest to see if Wi-Fi is working. I need help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gleonard3:
WiFi A-OK for me, latest 10.2, 9/25 Nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tejajuloori:
Thanks I was wondering where I saw the issue on jira

---------- Post added at 12:21 PM ---------- Previous post was at 12:18 PM ----------

sry, went back to stock, also as someone pointed out, this seems the exact issue I was facing on cm 10.1 stable versions, and there seems a solution for this

from https://jira.cyanogenmod.org/browse/CYAN-1504

'dzo, creator of Snap Camera HDR has fixed this in his app.

He was nice enough to cue me onto the solution, so in his words:

"The problem is with the cam_mode parameter, the CM10 HAL sets it to an empty string (or doesn't set it at all I can't quite remember).

It needs to be 0.'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Am I just lucky? I'm running latest 10.2 nightly and face detection works fine, as well asfront-facing camera in Snapchat and Vine. I'm running stock CM kernel. I've never had a problem with the front-facing camera in any apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Wi-Fi on wake is working well for me again in latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
That's my post. :p

Have you took a picture with it, not just seen the preview? Usually reboots right after taking the picture.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] villovil:
Early days but good so far.....

I was able to use the front facing camera with Skype last night running 10.1.3 (stable) on my GS3 from Rogers. The only thing I noticed that was weird on my Google Hangout call, was a green line down the left side of the picture of the other party.

No crashes though..... :fingers-crossed:

NB.: I am running KT Kernel form July18
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
The front-facing camera works fine for me on Snapchat & Skype, but reboots the phone when used for Instagram. CM 10.2 9/07 nightly, stock kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Guess both might have added a fix!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elijahblake:
latest nightly, stock kernel, i was just at 15% battery after only about 2 hrs. Screen time was top and I've barely had my phone on, Google Services was number 2.

I rebooted and I'm recharging, going to see if it was just a fluke.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Battery is almost always bad on a fresh nightly. Posts like this just plug up the thread with useless information.

Run the nightly for a couple days and then decide what your battery is like. I typically barely make it half a day on day 1 of my flash but my battery life doubles or more after a couple days. My best battery life is still stock TW.

Sent from my SAMSUNG-SGH-I747M running CM10.2 nightlies
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elijahblake:
I've been on Nightlies for about 3 years and I've never had a battery drain like this before.. like I said it was at 15% in less than 2 hrs. and it had 12 mins of screen time.

So no, this isn't typical for nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wheemer:
S3 has not even been out that long...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I don't think he mentioned it was on the S3 alone. I've been running CM nightlies for 3 years too, just not on this phone solely... ;)