yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
This is because of the different aspect ratio of the screen (16:9) and the aspect ratio of the pictures it takes (4:3). If the screen displayed exactly what the picture would be, it would either have to introduce black bars at the sides, or squash it a little bit which some people won't like (search for warp-o-vision in the thread).

Nothing you can do, other than perhaps put in a request for an option either showing black bars, or warp-o-vision. Personally, I don't think this is a big deal. You can always crop out the extra bits if you want 16:9 aspect ratio pictures.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
Works for me. Lol thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
Is anyone else experiencing a lot of stutter when opening and closing apps with the new kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Yes, they haven't optimized 3.4 yet. Give it time. I have this issue as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ozzman54:
Hi guys, can you help me reproduce this bug with the camera. Just making sure it's a CM bug, and not a problem only with my phone. Found it on the March 8th nightly, and still having it on March 21st nightly.

******Warning, you'll probably have to reboot after this.

-Open the messenger app like you're going to text someone. In the text, press the attach button and hit "Capture picture". Use the default Camera app. Take a picture of something and then hit the middle circular arrow button. The camera should freeze and lock up. Eventually it will stop responding and you can force close it. Now try to open the camera app. You should get a Camera error: "Can't connect to the camera." Only way to get it working again is to reboot the phone.

Anyone else getting this?

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12th Planet:
Haha, oh that old thing? What gapps did you flash?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I never understood why they made the transition to the 3.4 kernel. The old one was flawless and had a great battery life. Now we have to start all over with optimization with this new kernel. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
Get used to it. It is all part of running custom OSs on your phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cozmo1:
To whomever was looking for the 03/13 nightly, here it is: cm-10.1-20130313-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You don't have to do anything considering you propably aren't submitting commits to contribute to the new kernel. Not sure why you would be mad over it. This is just part of the process in moving foward. If things like this didnt happen then we would all still be on the first version of android. There are older releases with the kernel that you think is perfect. Why not just use that if its what you prefer? Especially if it works good for you. There's no reason for everyone to be on the latest releases if it's something that conflicts will their day to day usage. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Flashed ktoon's kernel and it's all good. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
Is the M2 release from early March a 4.2.1 build or a 4.2.2 build?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
it's 4.2.2, with the 3.0 kernel. It's a very solid and stable release, but the one around 3/17 just before the 3.4 kernel is better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Yeah, he is right. I'm using the one before they updated to 3.4 and getting around 5hrs screen time. It's awesome. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cowhow:
Same here. Tried installing Wallet and that didn't go so well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
So is that the 3/17 nightly?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Yes. 3/17 used the 3.0 kernel and all the newer nightlies use the 3.4 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wizshaw:
Im not sure which nightly you guys are referring too... it goes from march 4th to march 18th... with a jump of 3 megs... I dont see a nightly for march 17th.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
On 0317 now... will test for a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cre4per:
http://www.goo.im/devs/cm/d2att/nightly/cm-10.1-20130317-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
This file is only 168 bytes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
Go to the T-Mobile Development thread, don't ask for it in an AT&T version.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
This silence is killing me

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
Anyone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Question and answer section.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
Running ADW EX v1.3.3.56; On the home screen and the others, the widgets get either small or really big. Locking or unlocking the desktop will usually make it right. Could be a app compatibility issue, but I thought I'd at least mention it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JibbsIsMe:
Try out Nova or Apex, to see if it is an app problem. ADW is a really old app.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] meccanikal:
ADW EX hasn't been updated since december of last year. Think about it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigdbag:
Hm, I'm using it as well. Can't say I'm having the same issue as you so I'm assuming it's your apps' widget problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Themes and apps section come on guys.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
Im not having this prob, everything is pretty loud for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
Try turning off auto briteness and it should work. I like when the lights are off cus i hate the ugly yellow color but when i activate the auto briteness, the lights turn back on, so i have to uncheck the auto briteness and restart to turn off the lights.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Raul77:
Canadian Users : LTE will "NOT" work on this or AOKP JB ROMS.

my guess is we need a Network Mode settings, everytime i flash ICS AOKP the network mode is on GSM and i have to change to LTE/GSM, CM 10 / AOKP JB does NOT have this setting and i am guessing its stuck at GSM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] projeqht:
In reply to this:

I'm running AOKP JB on my S3 I747M (Canadian Rogers S3) and I have LTE working. Check out my post in the General Section for further discussion. Thanks and good luck.

http://xdaforums.com/showthread.php?t=1796330
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
Bluetooth quality?

Can anyone attest to bluetooth call quality and/or music streaming quality? Does AVRCP function correctly in this early build? How about apt-x?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alirulzz:
where's our boy cyanogen??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Vacation
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cyanogen:
I'm back. Partying on the beach is hard work :cool:

New build is up. The correct camera firmware is included, some new CM features are in, and various issues are fixed. We're still working on fixing the rest of the audio/video bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] schwalbach:
I haven't really had any audio and video bugs, I would normally post this in q&a but since I'm replying to you, what bugs are you guys finding in a&v?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
Please invite me next time!

What are the other audio/video bugs? I havent been on CM10 but it sounds like I might make the jump since the camera is fixed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ManOnTheMoon:
As soon as I flashed ktoonez build last night in desperation this releases. Lol. Either great job!

Sent from my GALAXYSIII running Jelly Bean.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Goo seems to be defunct here for a while. I can't get it either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cozmo1:
And for those looking for the 03/17 nightly here it is: cm-10.1-20130317-NIGHTLY-d2att.zip (This is complete)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] runbuh:
Sadly - I think those folks are still looking. For me, your link redirects to http://mirror.netcologne.de/cyanogenmod/jenkins/22680/cm-10.1-20130317-NIGHTLY-d2att.zip, which yields a 404 Not Found.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Got that error first try but tried again and it worked fine. Direct download from link. Doesn't redirect your browser

anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rescue9:
I'm also getting a 404 error when trying to d/l the 03/17 nightly. It gets redireted here: "http://mirror.symnds.com/software/cm/jenkins/22680/cm-10.1-20130317-NIGHTLY-d2att.zip". However, there isn't a folder 22680, and when looking in the jenkins directory, there isn't a folder for 03/17 that contains a d2att nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
I keep an archive of all nightlies for all my devices of about 2 months. Here is the one for d2att. Take what you need, don't go crazy ;).

https://www.dropbox.com/sh/q746bgbhn583jc2/W46PuPSNee
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Man oh man, I had forgotten how fast the last few nightlies before the 3.4 kernel were. Apologies to the newer kernel, but until it's optimized quite a bit more, there's no comparison between it and the 3.0 kernel in the 3/17 nightly for smooth performance, no lockups/BSODs, and long, LONG battery life.

3/17 should be a milestone! ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
I have been flashing every nightly to see if they have the lock ups fixed, but I have kept falling back to the 17th. It absolutely is the best nightly I have flashed since the beginning of CM for this phone. But here's to hoping the new kernel gets worked out.. I'll keep flashing each nightly until I get one that works... As long as I have the 17th on my SDCard ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Wow, look at the change log for next nightly. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
I'm not sure if this is rom related, but on 3.4 the display and buttons randomly become unresponsive. I've read this thread every day but has anyone had a similar experience?

I'm using ktoonz new kernel.

Edit: sorry, ignore. I found other posts ITT referring to the same thing. For now, 3/17 works great.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] skim7x:
Yeah, that link doesn't work either... I'm just getting file that is 169 bytes... right-clicked and downloaded link, too.

---------- Post added at 12:54 AM ---------- Previous post was at 12:52 AM ----------

Same with this link...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
I am getting about an hour battery life on the last couple of nightlies! Looking forward to some optimization!

Can I dirty install an older (i.e. 0317) nightly over top of the 0324 nightly?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thelakeshow:
This guy has it:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cozmo1:
The link I found is working right now, though I do see that periodically throughout the day it goes offline. There is a link for someones archive of CM files in a previous post. Here's a link to it as well from my DropBox account: cm-10.1-20130317-NIGHTLY-d2att.zip

If you would like a DropBox account of your own click here

.

---------- Post added at 01:35 AM ---------- Previous post was at 01:34 AM ----------

Sure you can. You'll have to download it and install it via CWM recovery, but there's not much to it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Wipe /system and your caches and don't forget to install your Gapps after. I did it and works fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zelendel:
And you wonder why your getting only an hour of battery. Might be time to full wipe and clean flash
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Huge changelog. No clue what they will achieve. lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Looks like kernel optimization. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] huladaddy:
Thanks. I wasn't sure you could downgrade nightlies the same way you upgrade them.

---------- Post added at 01:10 AM ---------- Previous post was at 01:07 AM ----------

Do you need to reflash Gapps after a downgrade? I don't after an upgrade.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Please remember to not report issues when using a modified setup. If you're experiencing issues using a custom kernel and not the one built in, please report issues in that thread.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Not if its the same version of android. IE, if you are on the 3/1 gapps, you should be fine up/downgrading to 3/17 cm10.1 (or any 10.1) edit: that is to say, more specifically, same rules apply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
For all cm lovers, exciting update. Steve has left Samsung after small stint of 2 years. He maybe back with a big bang. Sit tight

He now bring the required insights from Samsung
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Not sure that this is good news. Android is where it is thanks to Samsung, and burning bridges between Samsung and CM can only be detrimental to CM. (Yes, I know, Android != CM, but still...) At least having a "mole" like Steve within Samsung's ranks could help with the already shaky communication b/w CM and Samsung. Without that, Samsung will continue to disregard the open source crowd with a vengeance.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I can understand the notion you have towards his departure, but the statement from him does not have anything negative about his leaving the company, actually he praises the S4 and talks about S3 as his primary phone. I thought the same idea "mole" two years ago would improve the comms with him there, but CM has thrived despite the closed source for certain functions and features and processors...

If there was anything that would've improved the Galaxy phone series and CM, It would've happened already, considering he joined them when the S2 was out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
But the good news you can slow cook an egg on it!

---------- Post added at 05:59 PM ---------- Previous post was at 05:56 PM ----------

I've been wanting to move forward. I just flashed back to 0317. Dirty, and it's running fine. no battery issues.

Is anyone claiming that in the last weeks nightlies that there is a stable, non-freezing, non-bsod, high batterly life build, superior than 0317, as long as a clean flash is done?

Sometimes I think dirty-flashing gets a bad name. :) It must be the name itself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Add to reject list

Stock AT&T phone has "Add to reject list" in the call log as a feature.

How do I get this on CM10.1?

I'm desperate. These bleepholes have called me 5 times today for a home security service. 1-702-441-0585

---

I got this on #teamhacksung

in the people app, open the contact and then hit the menu button and there is a "send all calls to voicemail"

I was hoping for something more powerful. Like a full block, full ignore. But I'll take it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I always have to reinstall the Gapps since I always wipe /system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
Steve worked on CM while at samsung, we also have him to thank for a bunch of advancements with actually getting CM on the S3.

So I wouldn't say its a good thing he has left
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I had no idea that we had test codes working on CM10? Just surprises me that haven't seen folks talk about it. Or has this been just introduced?

Upcoming Nightly:

Fix FC when trying to adjust radio band via *#*#4636#*#* dialer code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] phositadc:
How else can you disable lte if not this way?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
No need! The CM install script actually backs up gapps, then formats system, then installs the ROM, then restores gapps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Just checked out the installer script. I had no idea. However, I also install a custom kernel (with different modules) and the 4.2 camera with photosphere so I'd rather do a wipe of /system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cre4per:
Here's 0317 http://db.tt/BpDBbrD8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Hmm, there is no daily today. I wonder if that's a bad thing or a good thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
Just means the build failed. Doesn't mean anything else.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Everyone needs to see this: http://review.cyanogenmod.org/#/c/34026/. Pie Controls are coming!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russiandivxclub:
Hi guys, I am sure this is something CM Team is working on right now but it seems that weeks passed without any improvement in antenna reading, I am always showing 1 out 5 bars on antenna in places where I always had 5 bars. But strangely enough at my work inside building when I had 4 bars I still have 4 bars. I kinda not following this so I returned to stock and indeed 5 bars home ...flashed back to CM 1 bar, so I do know this is CM. Is it common thing with reception or something is wrong with my device here. All calls are coming true it's just representation of reception is not correct...again in only some places. I am on 3.15 build I heard bad things on few current builds so I stay away.

Thanks !
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Maybe CM is showing accurate signal whereas stock shows you less accurate...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
I would say this is a huge possibility, companies want people to think they have amazing service everywhere they go, so just add an extra bar or two no matter your signal strength. One company definitely got caught for this.. *cough Apple cough*.....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acme anvil:
Have you compared the actual signal strength?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Oddly, my phone will, for example, show 4 bars, yet calls will cut out and drop.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Consider updating your modem firmware.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
What are pie controls?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Check out ParanoidAndroid to see what they are.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Which Nightly has a great battery life before 03-17? I don't want to jump in to the latest one due to its kernel not being optimized yet. And the 03-17 Nightly is not giving me a good battery life..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
My take on all of this and I have no hard proof aside from what I've been observing on my own phone is that in locations where the signal would usually fall back to full bars 3G is hanging onto 1 bar 4G thus always looking like such poor signal. I'd rather it go back to full 3G than try and hang onto 4G but it's not a deal breaker for me.

Just my take on it.

And if you are trying to determine your signal strength while you have a WIFI connection, turn it off because you can't see what type of network you are connected too and you may have the same thing as me. 1 bar 4G where you used to get full bar 3G. Or you can go into phone status to check it out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
You try using goo with twrp? You can queue up your zips and order them. I use it for nightlies + soft nav mod. Works great, haven't had an issue yet. I'm sure you haven't either, but I think it's a bit faster this way.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Cyandelta also allows for the same and you are only downloading 10meg files instead of full zips.

Never had a problem and flash every nightly as it comes out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
No nightlies for 2 straight days. :thumbdown:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Makoers:
New nightly should be soon with pie
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Indeed, I forgot about cyandelta... But in my defense, I got my toes wet and have been building cm myself. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jorgeszabo:
Headphone Issue

Has anyone else noticed that when the headphones (regular wired) and charger are plugged in, there is a background buzzing noise coming from the headphones? The noise goes away if you start to use an application that has an audio stream. For example if you open up Apollo and listen to a song and then pause (no sound playing) the noise is not there but comes back a few seconds after closing the program.

If you unplug the power cable the buzzing sound is never there.

I don't remember trying this before the upgrade to the 3.4 kernel so not sure if this was a consequence of the upgrade that team will try to address in the future or is this something specific to my device.

Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] carbon12:
That is a side effect of turning off the audio amplifier when it is not in use. The ground is most likely disconnected to save power but that in turn causes the ouputs to then float, with no battery ground. This causes a ground loop which then generates the buzzing/humming noise. That's why you don't hear it for a few moments after an audio event. This happens in most electronic audio equipment when grounds are not directly tied together.

In this case, when you plug in your charger, there is a switching voltage regulator that is fairly noisy, RF wise, and in very close proximity.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jorgeszabo:
Thanks for the info! Is there anything I can do on my end to prevent this? Or is this something worth filing a bug report to the CM team for a software fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
This is purely a hardware setup issue. I only experienced the buzzing noise when charging from cigarette lighter adapter in my car and playing music through aux-in at the same time. After sbddude suggested earlier in this thread, I bought a ground loop isolator from here http://www.amazon.com/gp/product/B001EAQTRI/ and it worked pretty well. Now there is only buzzing noise in the empty silence in between the audio plays.

EDIT: read your issue more carefully and see that you want to stop the buzzing noise in between plays. so ignore my comment, but leaving it here for future users with car charging + audio issue.