yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
With phone off, hold home and volume up. Press power button, when screen flashes let go of power while still holding the other two buttons
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Confirmed. No way to focus the camera.

When I get a moment I'm goingg to flash the old camera fix to see if that solves the focus issue. I will report back in an hour or two.

EDIT: Flashing the old camera fix on the 7/25 build does not fix the cameras inability to focus. I tried all four focusing styles (Auto, Infinity, Macro, Fixed).

EDIT2: The external speaker sounds perfectly fine! Until you get or make a call... then the sound is noticeably distorted for all everything coming out of the speaker (music, notifications, ringtones, etc). A reboot fixes the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] snotyak:
It doesn't.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
I'd really like to see the first one fixed, but my captivate on cm9 did the same thing. Something about how the Samsung camera encodes the orientation data is different from the "standard" which cards the mms app to not rotate the picture.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I can verify this too. The camera will take the photo, but won't focus. I can confirm that Camera Zoom FX does seem to focus properly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jason123420:
Anyone also have the problem of it saying phone number unknown?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] americasteam:
It's actually home + volume up to enter recovery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
LTE confirmed working on Rogers too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
Sound through the speaker is not distorted on this build, until you make or receive a phone call. After that all sounds coming out of the speaker are distorted at the highest three volume settings. The sounds are not "louder" on these three volume levels after a call, which would explain the distortion. The sounds are just garbled.

A reboot fixes the issue until you get or make a call.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
Oops
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Why would it? All that would be there are settings for options that no longer exist. The OS would ignore and most likely purge those.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
U sir... Are wrong as can be theres no purging and sometimes those left over data fragments are the culprit for the issue... Ask any respectable dev what the first solution to any bug is... Wipe data... And the os doesnt always differentiate... Sometimes the options do exist just slightly changed... Wiping isnt always needed but sometimes it is. Its better to pass on safe practice than careless practice

Btw im a rom dev... So i do really know what im talking about... Just throwing that out there:P

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
This is correct. :good:

---------- Post added at 01:45 AM ---------- Previous post was at 01:44 AM ----------

This is not. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] *KiD CuDi*:
I've been running M3 all day and its flawless just in case anyone was wondering.

I only have one issue, is there any way to disable CRT animation? I've tried searching but I cant find anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I to am finding M3 to be one of the best builds released in the last two or three weeks. Kudos to the CM team for all their hard work getting the new kernel to work right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I can't say whether or not doing a full wipe would have improved M3 for me, but I can say without a doubt that dirty flashing back to M2 reinstated the smooth performance that I had been used to before. That being said, I think that the difference in performance may be the result of the new kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ag4vr:
It's not resolved for me on M3.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Unless you are doing a FULL WIPE, your statements regarding anything about performance or bugs are meaningless. This subject was explained just a few posts above by howtomen
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Can a mod please clean this thread?

Why don't the 2 (or more) of you take this discussion private? I'd rather hear about the ROM and not ramblings about the "proper" way to flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
It's over now. In future, might I suggest ignoring and scrolling through it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Well id rather see real bugs and post with log cats instead of i didnt wipe and now i have this and that ;) but hey anyways im running on latest just fine

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
the M3 has been running awesomely for the most part, but I'm still getting the weird page flipping occasionally with certain apps and the pull down menu from the home screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Speaking of, how does one get Logcat to work and actually report stuff? It's been awhile since I've uploaded a Logcat but recently when I try, it seems Logcat doesn't actually do or log anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TeflonMyk:
So far, so good running 10.1 Milestone 3

---------- Post added at 01:39 PM ---------- Previous post was at 01:34 PM ----------

Out of curiousity: What camera apk are you all using for M3???

I didn't have a camera app with this flash. I can't remember if I had one with M2 or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
I normally use adb and pastebin my logcats... But u can do the text method

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
What I mean is Logcat doesn't actually appear to be logging anything. It's always blank when I pull up the app, no matter what I do on the device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sephk:
it needs root, I think its a 4.2 thing. Use catlog, it asks for root on first start
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
These last few posts are more like, thank you for returning to topic!

I'm still seeing some random flipping around too when scrolling on pages on 4/12 nightly.

Lock screen also acted strange earlier; Spotify widget on lockscreen caused the camera to try and open and they were kind of stuck.

I hit the power button once and then waited a second, hit it again and then was able to unlock.

Can't seem to get it to do again, so maybe just a one time weird thing...

Liking the progress so far though, 4/12 nightly seems to be very smooth and so far no random bsod lockup/reboot.

Just have the page scrolling issue and bluetooth still hangs up when turning off sometimes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Or u can stop using apps and use terminal emulator or the android sdk on ur computer... And u can see the actual logcat;)

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Did a clean flash of M3 and was still getting the odd page flipping bug. Tends to start happening when you leave the screen on the same page for a little while. Went back to 03/17 for now until hopefully this is resolved.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Is it worth coming from 3/17 build to the latest build? I see that some people are still reporting some issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I think its very much worth it. There's always going to be issues as this is mod isn't finalized. M3 runs a lot better than the dailies before it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I stayed on 317 until 408 then switched to the m3 build. 317 has much more SODs and freezes (during phone calls). I have experienced one reboot and no freezes on M3.I haven't noticed a difference in battery life between the two (M3 might be slightly better). I developed a wakelock on 317 prior to flashing 408 and M3, which fixed the issue. Performance is smoother on the new kernel, but I develop some lag that can be resolved by rebooting.

Overall, I think the new kernel is much more refined than when it came out on 318. I think it's worth it to upgrade and you can flash back if you don't like it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
So I decided to do both a dirty flash from M2 to M3 and then a fresh install of M3 afterward to see if there was any difference. There wasn't. M3 has really choppy open/close animations compared to M2 no matter how I flash it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Didn't someone a few pages back say that 3/17 was one of the more stable nightlies? I'll use it for a while and see how it goes. The page flipping bug is a deal breaker for me to use M3 right now. I read a lot of documents/books and having it randomly change pages is way too annoying.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
The audio skip when touching screen elements bug is still present in M3, it just doesn't show up right away. It only seems to appear when the uptime on the phone is up near 6+ hours or more.

I'll be happy to grab a log but I'm not exactly sure if this issue will even appear in a log since it's not really a crash or anything.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Welp i run a different kernel and its smoooothhh

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
Which kernel are you using?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
3/17 was the last nightly before the move to the new kernel version... It was also the most stable & bug free for the past few months. Or so I hear, haven't made the jump off of it yet myself as the new kernel sounds like it's doing a little teething still.

Not dissing the devs at all, but they made the jump from a very mature code base to a newer less mature one. It will take a bit to reach the same maturity as the older kernel version. It's the temporary cost of progress.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Bms im one of the testers haha so im running one synced used this weeks release should be great

sgh-i747(d2att)(sgs3) on latest cm10.1 or ultimatum
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Pardon my ignorance, but is the newer "code base" that you speak of mainly referring to the changes made to the kernel between M2 and M3?

I honestly can't imagine how anyone using the stock CM kernel in M3 or beyond is getting good performance. After I went back to M2 the difference was even more clear than before. M2 is silky smooth with the stock kernel, and M3 is sluggish as hell when it comes to animations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] calvin35:
If you want to fix the app animations go into developer options and disable hardware overlays and force GPU rendering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
I'm on 20130412. I'm getting random reboots, at least once an hour. I've recorded some logs and they're packed with accelHandler messages. That doesn't worry me by itself but the last line before a reboot is always from Sensors.

Is this a bug related to the recent sensor updates or just me?

Sent from my Galaxy S3 [AT&T][CM10.1]

EDIT: Flashed 20130413. I had to fix permissions but it seems to have improved the rebooting issue. Looking at the logcat I'm seeing loads of errors and warnings though. I'm hoping they are from benign bugs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
Came to 4/12 straight from 3/17 and zero issues on KT kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
How's the 4/13 build guys? It seems like there was quite a few kernel improvements.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
Disable auto rotate and the accelHandler errors should go away. I doubt they are related to the reboots.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
That was the first thing I tried and it made no difference. I believe it simply tells the ux/ui to ignore the data but not to stop processing it or to shut down the sensors.

Sent from my Galaxy S3 [AT&T][CM10.1]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Why don't you try it out yourself? Every morning you are here asking how it is. If it's any better blah blah. Stop being so lazy and try it out yourself. You clearly aren't adding anything to this development because you aren't even man enough to test the nightlies. And don't say you don't have time or anything like that cause you clearly have time to troll the forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I've only been running it for an hour now, but 4/13 is very smooth. Haven't seen the weird page flipping thing yet either. It did change my WiFi region to Europe for some reason, but that's an easy fix. Nice work devs!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Looks like the next nightly will have a ton of kernel improvements. :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Well that was interesting.

I'm on the 04/09 nightly with the KT kernel and this morning I went to share a picture from facebook. Upon doing so, handcent crashed. I thought ok, no big deal, I'll just check if the message sent. I open handcent and I have no messages at all. I open messaging, also totally empty. Ok, weird. So I reboot and it's still empty, and my contacts are also gone. I start to restore the messages from Titan Backup, and after a while it makes my phone reboot. After that it kept rebooting a few seconds after the boot screen disappeared. I pulled the battery out and left the phone to cool for a bit since it was getting pretty warm. Was able to boot up ok after cooling down for 5 minutes or so. I manage to resync my contacts (google sync) but still no messages.

I happened to get a text from a friend but it didn't say his name, just the number. So I send him a text back from the main screen (having to pick his name) and the conversation showed his name at the top, but going back to the main screen it didn't update to show the name, just the number. So I reboot again, and it starts doing the reboot thing again.

Seems like somehow something got corrupt? I'm restoring from a nandroid right now which I did just before I installed the 09 nightly. I'm hoping that fixes whatever might be corrupt.

EDIT: Nandroid fixed it. Lost 4 days worth of texts but oh well, not much I can do about that now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarphoun:
After a full day on M3 I realize battery life was awful vs what I been getting with m2. I dirty flashed M3 over m2.

Fully charged last night and it down to 38 without me barely using it.

Back to m2 for now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Great. You can try it out and report back how it works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
It just did it again. It did it as soon as I was listening to music and went to reply to a text. Handcent crashed and then no messages. I'm going to nandroid again, restore from titanium backup since I JUST backed up and then update to the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I have to agree 10.1 M2 is fantastic. I'll probably be sticking with it until key lime pie or if a possible M4 gets better reviews.

Wonder if we'll get a stable before key lime pie?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Just flashed 04/13. The page flipping bug hasn't popped up yet, so hopefully it's gone. Also I'm not sure what's up with the battery on this build. Either the battery life is amazing or the battery stats are bonkered. I've been on battery for a bit over an hour now and it's still showing 100%. Normally I would at least discharge a bit.

Can anyone else running 4/13 confirm?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Anyone else having issues with their phone ringer not ringing?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] samvillian:
yeah, but its moreso that nobody ever calls me :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I'm going to agree with excellent battery life on 4/13 and have had no page flipping issues either.

---------- Post added at 04:13 PM ---------- Previous post was at 04:12 PM ----------

Please remember to post issues with your modded setup in the appropriate forum.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You didn't accidently or forget that you set quiet hours did you? I've seen people before complain about stuff like that then realize quiet hours were set or set wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
going to 04/13 now due to positive reports! here's hoping!

any chance of swapping out bluetooth drivers from 4.1 to 4.2.2 so we can use wii remotes again? not asking if anyone will do it, just if its theoretically possible.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Is sending an SMS handled by the kernel?

Additonally I just noticed that it makes all my accounts under settings disappear. Only Whatsapp is still there out of the 8 or so that were before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
4/14/13 preview

Here's my unofficial build synced as of http://review.cyanogenmod.org/35748

http://db.tt/ZZdYqJbU

Flash at your own risk but I've been running it all day. Enjoy fraaaands :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
On 04/13 I got a random reboot while streaming Pandora over BT in car today. Otherwise, fine I think.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
4/13 has been running perfectly for me. No problems at all... But I'm sure gonna flash 14 ASAP!

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

You ought to try 4/13. It is loads better than M2. Faster, smoother, and tastes better too! :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
Just flashed 4/14 from m3. So far, it's good. No trouble flashing or booting up. Another solid nightly after the m3 build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dieselrellim:
On 4/14 for a few hours and no troubles or screen jumping.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
So I've done some searching around, but I can't seem to find anyone else who experiences the issue I am having. So basically random icons do not show and are just a black square. It seems like the icon is not drawing or something, and in place of it is just a black square. This gets annoying at times and has been in every nightly I've built and installed. I just want to know if others are having this problem or its just me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Attached more images:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
None of us have seen that before, but you may want to post in the t-mobile forum. This is the at&t, telus, bell, and rogers galaxy s3 (sgh-i747).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I haven't seen this issue. I assume you've tried clean wiping all of your partitions and starting fresh?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
They are the same ROMs, except for some very minor build.prop changes and a different build fingerprint. But I'll try posting in the T-Mobile forums and see if anyone else experiences the same thing I do.

I've tried everything, including restoring to the default unrooted Samsung ROM and then coming back. It's strange that I am the only one having this problem...it is quite annoying at times.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
At this point, it very well could be a problem with the GPU in your phone. I'm not sure how to go about further testing that theory though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
The thing is that TouchWiz ROMs do not have this issue...the black squares only appear on AOSP ROMs. I'll continue to ask around to see if anyone else has these issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
I seem to have found my solution. I have always been using KT747, and I assumed that the stock CM kernel would be the same. But I decided to give it a try, and with the stock CM kernel the black squares are gone. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
The animations do seem a little sluggish in the latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
You could try the new builds of the BMS kernel, or Tasks Underwear kernel, if you are looking for more control over speed and/or voltage.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bigdbag:
Does anyone know if cm now supports bluetooth 4.0 and/or the apt-x codec?

I have a pebble and would prefer to use the lower power profile of bt4.0. The apt-x is just something I've always wanted on custom roms since it makes bluetooth music actually worth listening to.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Seeing strangely quick battery drain on 4/14 nightly. Phone is getting really hot while actively using it too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
I still having this matter, does anybody encounter same?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] detdett:
Same here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yeahmann:
Lots of random reboots on M3 and 4/14 even with clean install and before doing anything. Back to M2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
Interesting if this only happening to Canadian versions. I had it from a while and tried to clean install and other possible options, but issue is still present
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
4/13 is giving my crazy bad battery life. it's really weird. Phone has been on for 5.5 hours with 5 hours of deep sleep. airplane mode for 5 hours. screen time of 25 minutes. i've lost 16% of my battery. i think im going to just stick with 3/17 until we get the final stable release for this ROM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Use a different modem. LH1 works for me but the others do not. There are a few threads around discussing this. Don't think it's a CM issue. It's more an issue with anything other than running stock by the looks for it.

---------- Post added at 01:41 PM ---------- Previous post was at 01:36 PM ----------

Must be something with your phone because I haven't had a random reboot since the M3 release and I have flashed every nightly since then

It's been super stable for me. Decent battery life, no reboots, FCs or crashes. No deep sleep issues etc. Overall very solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
I read that it is causing battery drains, hows yours? Thnx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
What's causing battery drain? The modem? Weren't you asking about the garbled call display? I've offered you a fix which is the ONLY way to fix it. I'm not going to start discussing battery drain with a certain modem.

Either use LH1 and fix your problem or stop complaining about it.

Battery drain (or so you hear) or fixed call display. Take your pick.