yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
I even said that it was caused by using the camera in snapchat. I didn't mention front cam, happens with both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DRFTsil40:
The low audio on recorded video had been like that for awhile.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
It's probably a different problem since it happens with the front cam only with the d2att...

And I do not have any other reboot problem...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Open phone app, menu, settings. It's weird phone settings aren't in the main settings, took my awhile to find it the first time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Alright well I checked that out as well. but it already has it set to vibrate when ringing. The calls vibrate with sound on, but not when it is set to vibrate. In vibrate mode the notifications/texts still vibrate, just not calls. Really weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SgtSausage21:
Ah i see. Yeah I've noticed weird stuff as well. Sometimes I think to much gets merged and too many setting conflicting.

Even worse for me cause I use PAC man, normally alright though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] stedean:
I'm on RC5. Verified front camera issue with Camera Zoom FX. Luckily, I never use my front camera, so I probably wouldn't have noticed it if it hadn't been posted here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I just posted about this problem a few days ago. Here's the link to my post, where there's a link to the JIRA report about this issue. The issue still hasn't been fixed. Follow the link and go vote it up! This is a terribly annoying issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
A workaround is to use another kernel that supports fauxsound drivers. Works just fine with that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
What kernel is that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Well anyone have any idea how to fix the calls not vibrating on this rom? I guess a factory reset might be in order?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
KT for one, there are others
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] humblehyper:
So just install KT and I should have a higher volume recording? No other app needed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
You need to buy faux app from playstore. Kernel just supports it but the app is what makes it work
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MikalCarbine:
Tried searching the thread with no luck. 99% of the time when I get an MMS it comes as a slideshow. No biggie but more than half of the time I can't even open it to see the image so I need to save the attachment and open it that way. It's driving nuts, anyone experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It's the sender's fault. That person has an iPhone I bet. Tell them to only send 1 picture at the time and add it to the conversation instead of going though their gallery to send it or vice versa. Then it won't make a slideshow.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] elijahblake:
+1, on it being a sender.. but my wife has a stock galaxy S3 and her's will do the same thing we she tries to send multiple pics at the same time. God is it annoying...

I've finally got her to stop..

---------- Post added at 12:07 PM ---------- Previous post was at 12:05 PM ----------

would this allow me to record my conversations? I think this was a feature that use to be in CM but isn't any longer.. I'm going through some legal stuff with a brand new car I bought and it would be VERY helpful.

I've tried apps from the market but they don't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yup, it's annoying as heck, it's like a video that plays that you can't skip to any part.

No it wouldn't help you record your conversations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gravedigger76:
No, this will not allow you to record phone conversations.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
I recommend Google voice. Ask the people you are dealing with to call you if they aren't already.

http://goo.gl/f40Fx
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheCynick:
Stability/random reboots

I updated to RC5 the last week and had a run of 5 solid days without a random reboot, and that included leaving the phone on overnight. In the past that's been an impossibility, as a reboot was almost guaranteed to happen then.

Of course once I started bragging about it I had two in relatively quick succession yesterday. The last_kmsg seems to clearly indicate a problem with the modem as the reason for the reboot.

There is a JIRA open for this, but is there anywhere else that i should post the last_kmsg for review?

Also, can anyone else comment on stability since moving to the latest RC?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
+1 on this. There has to be some kind of workaround for it though because it's just ridiculous.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Yes, ask the sender to send them as separate instead of slideshow. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
Of course you could do that. I often get a single picture in a slideshow from iPhone folks, where the first slide is their message, and the second slide is the attached picture. It's frustrating.

I'm curious, though - do their iPhones display these as a slideshow or as individual pictures? I think the latter is the functionality that people would rather have. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It shows it as individual pictures. I don't remember exactly, but my brother used to text me pictures and depending on the order of the picture & text and if from his gallery or from the messaging app they would appear as single pictures or slideshow.

This isn't a CM issue though, it happens even with stock roms, a quick google search will net lots and lots of frustrated users about this, even though the issue is on Apple's side.

Even worse, sometimes iPhones will try to send iMessages instead of normal

SMS to Android phones, then will fail (for obvious reasons). Then the iPhone user has to retry and it will work...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
Anyone else on 06/15 getting an alarm clock bug type thing? I have my alarm set to repeat for weekdays, but after I turn it off for the day, it doesn't default to being set to the next day. I have to keep disabling and re enabling it.

This is after a clean wipe/flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I can't say, I'm on 06/18 and all is good here. :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rocket Nine:
We have had quite a few nightlies since RC5. Is there any news from the devs on a RC6/stable release? Is anyone flashing these nightlies as a daily driver without too many hiccups?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Domoo:
I've been staying up to date and am currently on 6/19. So far it seems just as stable as rc5. The battery life has improved as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I will agree with that. I've been on each successive nightly since RC5 and 6/18 has amazing battery life. About to flash 6/19; hope I didn't just jinx myself...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I flashed 6/17 and lost the ability to send pictures in texts. Restored back to rc5 and it worked fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I usually upgrade my nightly setup every 1-2 days, sometimes up to a week between updates and I don't have any specific issue as of 06/18.

Release Candidates are nothing but nightlies far enough in development... You could pretty much title any nightlies, aside from show stopping bugs "RC".

Slicetwo - I just sent a MMS on 06/18 and it worked. Can't say for 06/17, I jumped over this one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
How's the volume on these part nighties? Rc5 volume when playing music is pretty low and that's the only downside...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
From speaker or headphones?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
speaker
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MissingBonobo:
This is relevant.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I've updated nighlties through CyanDelta daily and have had no issues at all with any of them. I have run the stock kernel, Lean, KT, and BMS, whichever is newest, and all have run flawlessly. I would think that it is time to label one as, "Stable". :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gcamp0730:
I was on RC5 for a while and liked it, except I couldn't send MMS pics. I updated to 6/19 today and I can send MMS again. I could always receive MMS, just not send. It was very strange. I've had no issues running 6/19 today.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I just updated to 6/19 and can't send mms at all. Anyone know of any fixes?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
No problems here. Just verified by sending an MMS (photo) to myself via the stock messenger app. Are you using stock or a 3rd party app?

I know they have been adding commits that have added some new settings/features to the system settings/more (under wireless & networks)/mobile networks sections of the menus. Double check all your APNs are still present that and that your preferred network mode is set correctly.

Nothing has affected me yet but I know their have been some recent RIL changes and some stuff being added to those menus. Perhaps your phone didn't play nicely with one of the updates and something was set incorrectly by default.

Also if you are normally on WIFI and can't see what network type you are connected too, double check you are connected to 3G, H, H+ or 4g. If you aren't on either of those, MMS won't come through.

Just my debugging ideas as I really haven't had any problems. I know you have been around a while and likely checked all these things but thought I'd throw this out there anywhere.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Ya. It seems that I can send small pictures but nothing bigger then a mb, even though I could before. All my settings are still good.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
Stupid question. Does my 4g-lte still work? I am on at&t.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Might be your service provider though that has changed something. I can send MMS just fine, small or big. :S
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
You are right; stupid question. Mine's been working fine. You must be doing it wrong.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
Should be. It is for me. Are you sure you have LTE near you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
I meant to say how can I tell if it on lte or not.... Will it say lte is the real question.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
It will say 4G
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
Thanks. So far everything is running fast and smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reinaldistic:
I can't install these nightlyies, the stables nor the release candidates cwm shows a message getprop =d2att. I'm doing this on an att phone i747 so I don't understand why it doesn't work. twrp shows a get prop i747 error...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Is your recovery for d2att or did you inadvertently install one for d2spr, d2can, d2tmo or else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reinaldistic:
you are right the cwm I installed might have been sprint but the twrp I had before was att for sure thats how I had installed cm10 before but its not working now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Just flash either CWM or TWRP via odin for the d2att.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Check to see if you have the newest bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] C2Q:
So I just flashed the latest nightly, this was happening back in 06/15 as well. The alarm clock tile that is supposed to be there then your alarm clock is set just randomly disappears after a while of the phone being asleep. The alarm clock icon on the top bar also goes away. The alarm still says it's on, but I'm not sure if it's actually going to ring when this happens. Anyone else getting this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] reinaldistic:
I'm sorry I didn't know boot loaders updated... I am in the latest modem, kernel, and twrp/cwm how do I update boot loader?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
About 2 to 3 weeks ago (maybe a month?) or so it was all that was talked about. Search the thread. It is done through Odin.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
My alarms stick, try clearing the data for your alarm clock app. You will need to redo your alarm after that but that usually solves most problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] indymx:
As of the 6/19 nightly media volume is either full on or off. Can anyone else confirm? This is thru headphones or speaker, haven't tested Bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
You might not have to update the bootloader at all. Download an app such as Android Info and verify if you have the latest or not. LK3 for ATT users, LK4 for Canadian users.

As for the assert error you got, it has nothing to do with the bootloader and everything to do with what version of Open Script Recovery (TWRP or CWM) you have. It needs to be d2att even if you have a d2can. Flashing the latest nightlies won't work with a custom recovery labelled as anything else. So just download the recovery flashable version of TWRP or CWM for d2att and flash it and you will be good to go.

Don't get all hung up on bootloaders before you either get the assert that says it's wrong or you have verified that you actually do have the wrong bootloader.

Tip: Bootloader is different than baseband (modem, radio). Don't assume that because your baseband is one version number that your bootloader is the same.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Checked my video subscriptions last night on YouTube with volume at 2 while I was in bed, it was just fine (as per usual). Updated this morning to 6/21 without a hitch. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RJQXCV:
Same problem here. Only happens in Apollo.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Ah! Probably why I didn't notice. I don't listen to music much anymore, and when I do I use Play Music.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So here's an interesting one. I know some people have been having issues with the front facing camera, but this is related to the rear camera. Instagram added the ability to take video today to their app. I tried it out and filmed a video no problem. When I decided to redo the video, the camera was blacked out. I closed the app, tried to open the stock camera, and got the "could not connect to camera" error message. I reopened instagram and my phone froze and rebooted.

I'm assuming this is an instagram problem with their video code, but you never know.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mustangtyson:
Has anyone noticed any changes resulting from this checkin?

d2: Add stereo mic device
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
6/21 when you call or receive call from someone, call timer always stay at 0:00

can anyone confirm if it's a bug?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
Haven't noticed, but once I go back to see the calls I made today they show the correct duration. Do you see 0:00 there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
I didn't mean that, I meant as

during the call

sorry for not making it clear earlier

call history indeed shows the correct duration, but please check when you're talking to someone on phone

edit: After some tests, it seems during calls, the duration goes by minute, not second so one minute = 0:01
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
Late to the party as usual. Working my way backwards through this thread...

on an i747 with Rogers. Been running the Nightlies for a couple of days. My connectivity is ****. Mostly Edge and sometimes not even that. Is it me or the nightlies?

My imei is correct.

My apn is ltemobile.net

My preferred network mode is LTE/GSM/WCDMA.

Current build is Jun 19.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
It's not the Nightlies. They've been great. 4G speed all the way.

This ROM is set up for ATT. Make sure that you make the changes necessary to use it elsewhere. Rogers has guite a bit about setting it up to work on their network; search around. :good:

Oh, and update to the newest. It is really solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
This d2att CM ROM isn't *only* set up for ATT. If your phone is unlocked (using an unlock hack or a legit code) and you swap out your SIM for another GSM SIM, it should work just fine, and even auto-switch the APN settings for you (for TXT and MMS) because cyanogenmod rocks that way.

I know this for sure, because I switched from AT&T to T-Mobile only about 24 hours ago and it worked without a hiccup (4G: check; TXT&MMS: check; calls: check). T-Mobile's bring-your-own-device + $30/mo prepaid plan rocks! I'm now paying less than half of what I was on AT&T (~$71/mo), and am getting much much more data: 5GB of 4G followed by unlimited 3G, unlimited TXTs, and "only" 100min talk. Should've switched sooner. Only downside to t-mobile's prepaid is that conditional call forwarding is disabled, soo... can't use Google Voice for VoiceMail. I can live with that.

(github should have a srcfile(s) somewhere showing all the supported APNs. If any are incomplete or outofdate, file a bug report, so you don't have to enter it manually. Found it - that's a LOT of APNs: https://github.com/CyanogenMod/android_vendor_cm/blob/cm-10.1/prebuilt/common/etc/apns-conf.xml?source=cc)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobertFontaine:
I'm experimenting with different modems in hopes that this may be my problem. Something is definitely wonky on my system. Both data and voice are completely flakey on my S3 on Rogers at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] swtnix:
anyone having issues with bluetooth audio? I get no left channel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Psychosi42:
For those that have been having trouble sending MMS, the issue appears to be the built in messaging app is trying to send a file larger than your carrier allows. I had to lower the megapixels on the camera app to allow it to send.

https://jira.cyanogenmod.org/browse/CYAN-1312?focusedCommentId=14431&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theROMinator:
That makes sense because the stock TW app reduces the image size before sending. Thanks.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chirantan.f:
Hello, I'm on RC5 and everything was ok till yesterday but suddenly I'm getting stuck wakelocks, it's Google services that's keeping my phone awake, does anybody know if there's anything that I can do to solve this?

Thank you
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Disable location and Google maps..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheIgster:
Think I'm having the same type of issue in another ROM. But what if you want Google Maps? ;) Not sure disabling an app is a great solution. Especially one you use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
Get greenify from thr play store and greenify maps. Also disable location reporting and location history in maps settings. Google now usually enables these features.

lalala boom
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
On 6/21 I am getting neither text message notifications nor gmail notifications when my phone is plugged in to the charger. No sound and no led light indication. Anyone else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
No.... But I am on 23 now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Wtf was with 6/23? Why did my phone force reboot twice right before the boot animation after install? It did this twice. Thank God too, especially cause it caused me to install ALLL my apps one by one. The battery life must be worth it. Holy Christ.

---------- Post added at 10:54 PM ---------- Previous post was at 10:49 PM ----------
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AlbertoM:
Mine too. I thought that it was stuck on a loop for a moment. Kernel change? I don't know, but I didn't have to reinstall any apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
All nightlies after 6/23 require kernel update. So ensure the kernel you are using was updated 6/23 or later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
I did not update kernel on 6/23. It loaded fine just like every other nightly build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
I'm running Ktoonsez's 6/08 kernel on 6/23 right now with no issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
You are lucky
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Rocket Nine:
Running 6/23 with the above mentioned KT kernel and have encountered one issue so far. When installing a new app from APK, the Next button changes to Install once I have scrolled through the permissions, but is not clickable. Even if I change orientation. The cancel button works. So be warned there may be other issues. This could be strictly CM. Could someone clarify if this works on pure CM?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
If you have installed some kind of screen dimmer or screen color changer than android will prevent you from installing apps untill it is disabled. i had this problem before.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
So has anyone else run into the Instagram video bug yet? I posted about it a few days ago. Basically, the video doesn't always work, and if it does, it then disables your camera after you've take the video. I wonder if it's an Instagram bug or something with CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
Is anyone else's homescreen widgets and dock shortcuts getting hosed on the 6/24 build? I can set them all back up, but they disappear on the next launcher reload (reboot, or if you hide drawer apps)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Calendar and Google play music widgets are working great for me. My home screen is working normally. Updated this morning, haven't noticed any issues yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Running 6/24 updated thru CyanDelta (and have been doing so like for a month now). Everything is perfect. It is hard to decide to use this or Task's ROM, which is always a cut above... and wins due to the Underwear Kernel, which gives better performance and battery over the stock CM kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thelakeshow:
Anyone flash the stable build yet?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
I have. I was trying to record myself with the front facing camera and all of a sudden it just freezes and crash then restarts. This is the only reason I'm going back to TW because the camera is so good on there. It could be an Instagram bug, maybe wait for the next update and try video recording again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] The LPT:
The front camera glitch shows up on camera zoom fx as well. I'm surprised this wasn't fixed before they classed it as "Stable"

Otherwise it's running pretty smooth

Sent from my SAMSUNG-SGH-I747