yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
10.1? Current nightly is 10.2....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
He wanted 10.1 so that's what I gave him a link for.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
No no no. This is no where near the last CM10.1 nightly. This was an experimental build that borked a few things. Do not flash this. The last CM10.1 nightly was 08/13. That's the one you want but it's no longer on get.cm. I'll upload it to Dropbox.

Just don't flash the one that he gave the link for. It's a junk build.

---------- Post added at 07:18 PM ---------- Previous post was at 07:03 PM ----------

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

Woo-hoo!!!! Looks like a working Focal on the next nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sakiwinkie:
I was in recovery and was about to flash it when I noticed the date and it was older. I decided not too. I am glad I did not. Thanks for the help.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
No problem. I'll PM you the Dropbox link for the last 10.1 nightly that was generated when it's done uploading. It's the latest and best you are going to get until they release 10.1.3 or another nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jmatt78:
Sorry
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
I read somewhere that this fixes the low speakerphone volume and low video record volume. Is that true? :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
http://mobile.10.1.cmxlog.com/?device=d2att

A commit is in the queue for the next nightly. If 10.1.3 includes these changes than yes. Sometimes stable releases don't always incorporate all changes. Depending on when the baseline is set before the stable release is built.

Perhaps you can sweet talk someone here who has a build environment set up to build an unofficial CM nightly that includes the newest commits.

---------- Post added at 07:48 PM ---------- Previous post was at 07:40 PM ----------

PM sent with the link for the last 10.1 nightly built.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
For what is worth, MsgtSimon has made a very nice repository of older d2att CM10.1 roms, as well as gapps and kt747 kernels.

https://www.dropbox.com/sh/q746bgbhn583jc2/W46PuPSNee
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
It will indeed. That's how I found out about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
d2att only:

CM10.2: https://www.dropbox.com/sh/i73ml8i6624xlsk/Bd4lvXE01o

CM10.1: https://www.dropbox.com/sh/q746bgbhn583jc2/W46PuPSNee

KT747: https://www.dropbox.com/sh/5cipia9hxdkqtji/ueQJx7n07O

Also, the current official releases of KT747 (SGS3, SGS4, nexus10) can be found on my webserver: http://goo.gl/S2O0I9

See the KT747 thread for confirmation if you like.

Any device:

GApps: https://www.dropbox.com/sh/v4pi85s3gqvuz4q/VgHIjUrOuN

When [MENTION=4325945]ktoonsez[/MENTION] starting keeping kernels on my webserver, the monthly bandwidth went from 1gb/mo to almost 600gb last month. Some impressive sh*t.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haha dang that's insane.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
Excellant! :D

Also the nightly's are labeled 10.2, are they actually CM 10.2 "android 4.3" or are they still based on 4.2?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
They're based on 4.3. CM releases DO follow Android numbering somewhat.

CM6 -> Froyo 2.2

CM7 -> Gingerbread 2.3

CM9 -> ICS 4.0

CM10 -> Jellybean 4.1

CM10.1 -> Jellybean 4.2

CM10.2 -> Jellybean 4.3

Guess where CM8 disappeared? ;D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
CM 10.2 is based off of Android 4.3

(10.1 was 4.2, 10 was 4.1, 9.x was 4.x)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
Honeycomb?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
The version that must not be named! lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
10.1.3 will have all the changes merged into cm-10.1 up to the date it will be built on. No special separate branch or anything like that this time, it'll be just like a nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No nightly today, two days.. What is going on?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Very recent commit to the CM10.2 official GitHub
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
8/23 nightly:

http://jenkins.cyanogenmod.org/job/android/39053/artifact/archive/cm-10.2-20130823-NIGHTLY-d2att.zip

Strange this is not available on get.cm
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
First picture taken with focal crashed it. Looks like the fixes didn't work for us. Either way that's too bad. Was looking forward to it.

Edit: I cleared app data for focal and tried again. It seemed better but I was able to crash it again by taking a couple of pictures quickly back to back. It still requires a reboot for the camera to work again but there was supposed to be a fix for that too but it doesn't seem to work.

---------- Post added at 06:47 AM ---------- Previous post was at 06:44 AM ----------

Not that recent. I posted about the commit on here 8 hours before you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MicroChip:
So I have a weird question. when i was on 10.1, I did the manual upgrade to the 4.3 camera (gallery2.apk) and had all the problems that went along with it, like having to touch the screen for manual focus before shooting or else the camrea would lock up until a reboot. I also enjoyed the benefits like kinda working photosphere.

Anyway I've upgraded to 10.2 and the latest gapps, and pretty much everything works fine, but I still have the same issues with the camera, and I also have to touch the screen for focus before taking a pic with Focal or it does the same thing, locks up until a reboot.

So did upgrading to 10.2 and latest gapps upgrade me to the camera I was already using, and we're all having these issues (I know there are plenty of other camera issues people are having) or is there a way I could get the 4.3 gallery apk that I put on off and let the nightlies put the latest one on?

Thanks!

MC
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Morning nightly are up on get.cm. lol morning
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reluttr:
This is gonna sound stupid... but I assume 10.1.3 will be compatible with the newest boot loader, or should I stay on DLK3?

Or does it really matter what bootloader I use as long as its compatible? XD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It will be compatible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Anyone else try Focal after the fixes last night? I've had no luck today. Nothing seems to have improved for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
It's hosed for sure. Needs reboot after to release the camera
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Yeah there was supposed to be a massive fix that addressed many issues with focal including releasing the camera after a crash which was never supposed to happen anymore due to other fixes included. Haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
LOL, that is awesome :D. Thanks for hosting man, you are a life saver :good: :highfive: :D :victory:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Update superuser?

I just upgraded from cm 10.1 to 10.2 and now I'm getting a message that I have to update the superuser binary. But the only choices are "Cancel" and "Update in Recovery". I tap the latter, end up in TWRP but can't find any file to flash. Any hints on how to do this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
Search
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
Oops. My bad. I should have done this first.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Looks like they're finally going to have the MMS size fixed: http://review.cyanogenmod.org/#/c/48986/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Guess somebody finally realized. My fix is obsoleted soon. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
Latest release fixed my focal crash.

Wish it supported SD storage like the AOSP camera now does. Oh well, making progress
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I think you are the only one then. Try taking a bunch photos really fast or clicking around the screen to focus a bunch of places really fast. You should be able to get it to crash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] A.VOID:
Right. It didn't crash initially now, buy of you play with the app it will crash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Would anyone know how to enable config_stopPreviewBetweenShots for Focal?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
Easiest way to do it would be to add an overlay in the d2-common source tree and build Focal from source afterwards.

Built the APK just now, with the said config enabled: http://www.mediafire.com/?eua9tr3yda4zfa3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Do you think we can expect a CM10.1.3 build eventually or is this all fantasy? :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks.

I've installed it but it still shows the picture preview after taking a shot even though enabling that line was supposed to stop it. Still crashes just the same. Thanks for building this for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
How stable is this come the 8/26 nightly? At this point I'm unsure if I should stick with Quantum or hop on board the official nightly train. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWheezy:
So maybe I'm just not searching the right thing, but is anyone having issues with background data not attaching? My data icons (both wifi and cell) stay gray all the time and none of my apps sync in the background. I checked background data and it is not disabled? I'm downloading GAPPS to reflash next, it happened when I updated the modem to the latest one and updated to CM10.2 for the first time. I've put a couple nightlies on since, upgraded the bootloader to match the modem etc. My next step is a full wipe but I'd rather avoid that if possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you haven't updated your gapps, that's expected.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Which nightly are you running? Which modem are you running? Any custom kernel?

I'm running the 8-24 nightly with the I747UCDMG2 modem, the 8-23 KT747 kernel, and the 8-13 gapps. I had no issues with data. I did have to go set my cell data type back to include LTE at some point recently, but I doubt that's what it is for you.

I'm updating the to the 8-26 nightly (all else is the same). If I have issues with data, I'll post back.

I second [MENTION=4311957]polobunny[/MENTION]'s suggestion: upgrade to the latest gapps: http://goo.im/gapps/gapps-jb-20130813-signed.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BWheezy:
I updated from 8/24 to 8/26 nightly and installed the 8-13 GAPPS and it appears to be fixed (going blue, haven't actually checked the data but I assume if the icon went blue the data will work). I was running KT747 8/21, i just downloaded 8/23 to install instead. Also using the UCDMG2 bootloader/modem. Getting some FCs but hopefully updating the apps will take care of that... Thanks for the quick responses.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
if you are having "weird" problem, I would stay away from any third party kernel for now...

CM 10.2 is moving fast... so there is some chance that kernels that are not exactly up to date compared to the latest nightly might cause some problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I always have quirky problems as well. I'm on d2att CM10.1 7/21 nightly still (clean flash, stock kernel, normal gapps as of that build), because it's been stable and offers me a solid 4+hrs screen time per day.

With that said, I noticed a problem when going back to school last week that I also experienced last year at school. I have wifi always on, as most do, and my university allows any device to connect to the guest wireless accounts all over campus without any type of authentication.

That's all fine, except that it will connect to the wifi fine when I get to my office, but if I go from my office to the library (or anywhere else, basically any other building), the wifi & cell reception icons go gray and I will not have any data connection until I either cycle wifi off & on, or cycle airplane mode. I can still receive texts/calls during this time, but nothing that requires a data connection.

As I mentioned, this has happened for a long time on various builds of CM, dating back to last summer when I got the phone. (This also sometimes happens when driving cross-country and the phone can't seem to connect to different towers while on Edge, but that's just cellular network, nothing to do with wifi.) I went back to stock to get the new bootloader and unlock my phone earlier this summer, then ran Dandroid 3.x for a week (until I couldn't deal with stock any longer), and it didn't have this issue with handoffs from one building to the next on campus.

Any idea what could be causing this, and what might fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Icons going grey doesn't mean you don't have a data connection. It means you aren't connected to Google 's servers which is fine. You only should turn blue and connect when you are trying to sync something like email from them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I'm sorry. I tried to make it clear that I don't have data connection when this happens. It's not just a cosmetic issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AmazingSpanoMan:
This was an issue brought up fairly early I'd say the first couple of pages. I do not believe playing music over bluetooth has been fixed yet. I can confirm that I can make and take phone calls as well as use voice dialer.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
The below quote is directly from the OP. The bold red is for your issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nismax:
Full wipe before install?

1! Hint...advanced>sensors.

Answer for rest of you Q's is patience.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markysd:
thanks guys still learning.....

yes full wipe.. will try akop :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
Running smooth just wanted to mention MUTE doesn't work while calling...thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nismax:
That sucks.... I hope they didn't hear words they not suppose to hear...;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
You can get the live wallpaper of the ripple effect here:

http://xdaforums.com/showthread.php?t=1788749
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notoriouspk:
I swear man this s*** is scary :) but since its a development theard now me I am on MUTE :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
Well, I see lots of reports of tethering not working, but I see no logs to help with that.. so..

Logcat: http://pastebin.com/utkaawaC

(MAC Address and SSID sanitized.)

dmesg: http://pastebin.com/LebMSDHc

Both cleared immediately before turning wifi tethering on.

Client device (windows 7) tried to connect a few seconds later (I see no activity in either log at that point, but I might be missing something), and after it fails out with no useful message on the client, I turned wifi tethering off, and dumped both logs.

I did have WPA2-PSK enabled, so I hope this helps.

On a different topic: Anyone using pattern lock + "Show widgets before unlock"?

This worked on cm9, and oddly, it works on another device of mine in CM10, but doesn't seem to work on this device?

Both the wifi tethering and the pattern unlock question are with cm-10-20120729-UNOFFICIAL-d2att.

Both bluetooth and USB tethering work, and USB tethering works with decent speed, so this isn't going to force me back to cm9. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Bug Report:

After I make a phone call, I cannot make another phone call till I reboot the phone. I can dial the number and all I get is silence.

I have not tested this with incoming calls, only with outgoing calls.

LanceM

7/29 ver

Upgraded from the 7/27 ver, wiping only davik cache
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
The same thing happened to me yesterday. After it happened, I wiped everything and reflashed, and the same thing happened once more. After that though, I restored an earlier backup (7-27 build I think) and then flashed the 7-29 build over it, and the problem seems to have gone away

Also, after reflashing from scratch, I was getting a Sim Unlock message on bootup. This also has gone away since flashing over my earlier backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
I'm on the 7/29 build and not seeing this problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Did you full wipe or just cache and dalvik wipe?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Latty:
I encountered this yesterday as well
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] aznkenshin:
Same here. It usually ends up them calling me just moments after. So maybe it actually dials them?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
just cache and dalvik
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] majingrim:
It definitely dials them, I called someone 3 times in a row, and they texted me asking what was going on with my phone. Then after a restart I could get one call through and it would stop working again after that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
None of this matters without logcats. Please test and pull the logcat so it could be reviewed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] electech13:
Any chance a future build will have network state modifier for us 747m users who haveLTE? cuz its hard going from 40-55mbps to Leeds then 7.. gonna try this rom though now and looking forward to it but saw that late not working...yet ..so had to ask
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Come on man there's already a fix. SEARCH!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] azncookiecutter:
Anyone run into issues where after a reboot, CM 10.2 freezes while booting up at the Samsung Galaxy SIII screen and when you go into recovery, the internal sdcard isn't found and cannot be mounted? Happened with both TWRP and CWM recoveries, latest versions. The initial boot after install is fine, this occurs after the first reboot. Only way to fix it is to format the data partition fully. Happens with both a dirty flash and clean flash, with the latest 8-26 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] johnhazelwood:
I just tried this without an issue. I installed 8/26 build, booted into OS, rebooted (no issues), rebooted into TWRP and am currently performing a backup.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
So my phone decided to dial 911 this morning all on it's own. It was on my nightstand beside me and I heard the operator talking and woke up, I told her it must have been a bug with my phone and convinced her it was an accident then went back to sleep. I thought I might have been dreaming so I called AT&T just now and confirmed the call was placed, to make this even more bizarre the call DID NOT show up in my call log.

I only have some basic applications from the Google play store so i'm going to assume it has something to do with this ROM (10.2) or if anyone else has any ideas as to how that happened please do share. My phone has actually done this before on the stock ROM about 6 months ago while I was just sitting at my desk.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
Do you have a look screen? Could you have hit the emergency call button somehow?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I do yes, I tried clicking it earlier but you'd have to dial the number then hit call. So I don't think it's that..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] djjuice:
So no freezing on the 26th build. But I don't have the quick power options for GPS, WiFi, Bluetooth, WTC from the pull down notification menu. I couldn't find a spot if this is a feature to enable or disable. Anyone else with this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] representingcochran:
It's in settings, interface, quick settings, then I think it's the fourth one day to add tiles....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
This is Off topic a bit guys but how do I flash back to the original ROM again? I'm with Bell.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polsonov:
Get a sledgehammer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Go read one of the multitude of stickies in this forum. If it's off topic and you know it is, don't post it anyway.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Ribbons >> quick tiles. Damn, I love cm 10.2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] webosguru:
I had an issue somewhat similar to what you're describing back in the GB days (2.3) and I found that setting my IP as static in the advanced settings in WiFi Connections would solve the data issue. It might be worth a shot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moporoco:
Happened to me using twrp and the cmupdater. Been fine last few nightlies using cwm and manual flashing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
How do you get access to the ribbons?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Settings -> Interface -> Notification Drawer
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
I'm on the latest 10.2 nightly. Anyone else getting a ton of battery drain due to cell standby? The same thing happened with a 10.1 nightly from around 2 weeks ago which I was on before I upgraded to 10.2

I've been on battery for around 90 minutes now and it has already dropped 7%. Says Cell Standy ate up around 45% of battery use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] berryman13:
Oh, duh! So enable this and disable the quick settings dropdown menu? I kind of like the quick settings UI more, but if it's going to be taken out of the CM code I'd better get used to these ribbons.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I didn'to see any commits in the last day or two that would explain this but I can't seem to break Focal today. Running the latest nightly and leankernel8.0.

Anyone else try it out today?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] friedsonjm:
Anyone have a recommendation for a kernel with fastcharge support that works well with these nightlies?

EDIT: ktoonsez kt747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I glanced and I agree with you no direct commits to focal. There's quite a few commits though so I might have overlooked something, but there's one about removing dithering from performance options which I always knew as being a cause of trouble back in cm10/10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therebel88:
Just tried it. Still causing reboot using the front-facing camera :( Running 8/28 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
That's expected as that fault is part of a bigger issue that all 3rd party apps will cause reboot when using front facing camera.