yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] selw0nk:
Camera Zoom FX was my back up camera app and haven't tried it. Since you tried it that sucks it still does it too.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
Stable release losses the dim lockscreen, other than that seems to be speedy and great
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I only used the back camera for instagram
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Malf8:
I'm having issues with MMS on 6/24 nightly. I can receive but not send. Anyone else experiencing this? I haven't noticed this issue on any previous nightly builds. Not a huge issue but I wanted go see if I was alone in this or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
I'm definitely having issues sending MMS as well. As you stated, I can receive them fine and from multiple individuals as well as over group MMS. However, I can't send a damn thing. It just hangs and says 'sending...' under the time stamp. Tried wiping and clean flashing to no avail.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
Stable running great so far. Fast and smooth.

Sent from my Samsung Galaxy S-BEAST!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Yup quoting myself to add more. So I can send pictures that I've downloaded to my phone with no problems. For instance, I downloaded a pic from theChive (yeah buddy) and sent to several people. Status went from "Sending..." to the time stamp quickly. But when I try to send any pic that I've taken with the galaxy it will always hang on sending. Idk if it's a file extension problem or something else. I can replicate the behavior every time though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Pic is too big. Try resizing to something under a gazillion mega pixels before sending. This was already answered

~L.T.

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

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
I can also confirm it still crashes and reboots on CM10.1 final when using front camera in apps like Cerberus and Photochron, which uses their own camera interface instead of through the gallery apk.

I'm not sure anyone has filed a bug report for this, so maybe the devs don't know about it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] klin1344:
Same here, the CM10.1 stable is running perfectly despite not having all the features that the latest nightly has.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Hey Klin can we have separate kernel update for the stable release? The latest kernel you have released yesterday is for nghtlies and not for stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] minnick:
Thx for the reply sir but I've already tried compressing the file down to 125 ish kb all the way from its 2mb original size. Still no cigar.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pkimkpop:
I am on 6/21 nightly. Can I install cm10.1 stable from update or do I have to update kernel? I always thought it updated kernel auyomatically
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Well it's either something wrong with the message (pic too big), something derped in your apn settings, or a bad flash. If you can't find anything obvious I'd backup with nandroid, factory reset, format the crap outta /system, flash a fresh copy of cm, clear caches for luck, and boot it up for a test drive. If it works then I would compare those apn settings. If they are identical then you've narrowed it down to a bad flash or something like it. If they are different well then that's probably it. Once you figure out the source of your troubles it shouldn't be difficult to devise a method to repair them.

~L.T.

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

Galaxy S Captivate [CM10.1]

Nexus 7 [CM10.1]

OUYA [Stock Rom...for now]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
Is anyone unable to see their photos in the stock gallery app? I know they're there as I checked with file explorer. I've refreshed the rom, wiped cache and dalvik, fixed permissions, and cleared the gallery cache and data. Anyone have any other ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I see them. Make sure you don't have a .nomedia file in your directory. If yes, delete it.

If you don't have one, I would suggest renaming the directory to something different, then creating a new directory with the proper name and simply cutting/pasting your pictures between both directories.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
Yes you can. Kernel is updated mayomatically from 6/21 to 6/24 stable
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
lol I see what you did there. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slicetwo:
I don't ahve any .nomedia files. I actually restored my last nandroid and just flashed the stable over that and everything seems fine (besides the front camera bug, the instagram video issue, and it seems the video is still skewed in the camera app).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Went from 10.1 M2 to 10.1.0 and I have to say everything is pretty comparable even the excellent battery life. Battery maybe a little worse on the new stable but no reason not to upgrade could be a time thing. WiFi hotspot works bluetooth seems reliable though I'm still early testing. Only issue I've had is one random reboot. I'll watch for this if it's going to be an issue I'll go back. I was hoping I would see some of the reports of a more fluid experience with the new kernel but I can't say I noticed much difference.

Overall I'm happy with the stable so far.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VashTS:
I'm very happy too, sometimes when idle for a bit, better battery stats reports as low as 0.8%/hour! that is incredible! im not budging from this version until something crazy comes along to make me change.

normally i see about 3.9-4.2%/hour, sometimes higher if im bored at work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
Takes no time at all through your Gmail account... Export--> Fix the "()" in Excel --> Import back into your Gmail Contacts... Profit

There is always a work-around

---------- Post added at 11:30 AM ---------- Previous post was at 11:29 AM ----------

One might want to use the CM10 JB Gapps if they want to get favorable expected results on a CM10 ROM
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gromet:
How do you take a screen shot on CM10?

..Gromet
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
Not you again. smh. Why would you install cm9 gapps on cm10? Do some reading and take this to q&a.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
Like this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] enzyne:
Yes was having the same problem as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Coolaaron88:
Where is the link to the Kt557 kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BabyHuey:
http://www.mediafire.com/?545c6xdxcq8icua
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
I don't think it is appropriate to post comments about other Kernels in Cyanogens thread here, he just said he has a unique kernel in here and that this thread should be about only his ROM/Kernel. Take this over to the Kernel thread, and the AOKP thread ... No offense, just respect the man and his work.

Should I come to your house and have dinner and then talk about how awesome my OTHER friend can cook?? Think about it....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
do you you think you could possibly make you signature a little bigger so that nobody can post on the same page as you? it makes it easier for people to read through the threads.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Igotsanevo4g:
Anyways...

Is CRT animation a no go? Mines not working and I having heard anything about it..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malaeum:
This is a question... there is a question and answer thread... ;) Please take future questions there.

As of right now, that is correct, it is not working for any of us. This is a very minor thing, development is almost certainly focused on fixing bugs that effect the usability (A2DP, camera issues, etc.) It'll get fixed in due time as these guys are pretty damn good at what they do.

---------- Post added at 05:16 PM ---------- Previous post was at 05:13 PM ----------

Task, for what its worth, in your user control panel you can set it XDA to hide the sigs of other users. I had to log out in order to see what you were griping about... and HOLY MOTHER OF DOG, you have a point there (though its 10 posts per page, even if his signature is 923847894 pixels long). ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tiffany84:
Loving this ROM. Thanks CM Team!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
nice theming...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bud951:
Awesome rom. I cant wait for the more stable builds. One issue im having NFC was working fine until I flashed the NFC with screen lock mod and now I dont have the NFC option anymore :( Is there a way to get it back without re flashing?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nismax:
Ignore task guy he is got issues. Big times. I have not seen your sig yet Im on tapatalk app and i already like your sig. Request... can you make it bigger ? Hopefully his head explodes....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bradyonly:
Mature much? Task is right. It's unnecessarily big and no one cares about all of your devices, kernels, accessories and the state of your bootloader... amirite?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dk2000zx:
we should stick to the topic btw lol
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AtoZ0to9:
current topic is his sig though... OHHH, the original topic... ma bad...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Artimus009:
Not cool. You shouldn't instigate more problems by voicing your opinions about other people...especially a Dev.

Back on topic...looking through the gerrit and this release def looks like a solid daily driver even though its only a preview. I'm wondering what its going to be like when its out of preview and into nightly mode.

S3 AOKP Jellybean KT747 by Task650 & Ktoonsez
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] eujin209:
Quick question. I haven't been online in a bit but the last ROM I installed was RC2. I see the stable build is now available. Can I go from RC2 to the stable build like when flashing new nightlies? Or has something changed?

Sorry for the noob question. Appreciate it :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
Installed stable version for 2 S3, one runs perfectly, one with random reboot (happened twice already) we'll see if this will become a problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] matrixzone:
Check if they have the same bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] digirat:
What features do the nightlies have that the stable doesn't?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenlester:
Yes, just flash stable like the nighties. The process hasn't changed since RC2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Sakiwinkie:
I am running 10.1 Stable and it is going well.

Does anyone know if you can disable the battery charging light while in full screen programs like Netflix?

Also has anyone played with the Auto brightness levels and gotten better results?

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Manually, settings/system/battery light

Automagically, probably could set up a tasker (or similar) profile. You'll have to do your research to get it set up I imagine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
They are the same. I checked right after the first reboot.

Beside I doubt you can flash with the older bootloader
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bentonhall:
Has anyone noticed that the home button does nothing if you short press it while in the app drawer? Works normal for me if I'm in any app, just not while in the app drawer.

Running 10.1.0 stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
probably just you, I'm also running 10.1 stable and nothing of sort

tried on normal launcher and 3rd party launchers (buzz, apex, nova)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
Ever since dirty flashing to the most recent nightlies and even the stable build, I have noticed that my battery life has literally halved from what it was before. Is that even possible? Would doing a clean wipe and reinstall of the stable build possibly fix this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arabcamel:
It could. Before you do that, you can download apps like wakelockdetector to see what is eating up your battery life. Your battery drain could be the result of a rogue app that you recently installed.

I recently had an issue where my "enhanced email" app was continuously polling for email after i flashed an update to th ROM i'm using. I found this out with "wakelockdetector" and I removed the email account and readded it. Now all is well.

---------- Post added at 03:17 PM ---------- Previous post was at 03:16 PM ----------

Privacy Guard I beleive.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
BetterBatteryStats or Wakelockdetector to see what's going on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ScOULaris:
I'll give Wakelock Detector a shot, but I know I haven't installed any new apps in a long while. The only thing that changed was dirty-flashing the CM updates. And when I look at my battery stats it shows that my phone is only away for a few slivers at a time. Like 90% of the time it isn't showing as being in an awake state, but my battery life went down from about 16 hours to 10 hours.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] x-geo:
hello everybody

i am testing in my SIII At&t i747 the stable release (10.1.0).... but the phone heats in any app like facebook or whatsapp.... i came from cm 10.0 stable release making all wipes...

any recomendation in the installation of this release? any recommended kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bruce Lee:
Heat is normal since this phone is a powerful phone. Could you please elaborate on the temperature? My phone heats up especially on ingress since it uses a ton of resources. I am running the same ROM with no issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
FYI

A new official Canadian release is out. MF1. It is based on 4.1.2 so it's a very minor update but with this comes a new bootloader. Is anyone able to extract the Odin flashable bootloader like we had with the latest update prior? We will likely need to get a JIRA report open to get them to add this bootloader or add this bootloader to the assert. Better get the files ready before we do this cause I'm sure all hell will break loose once again.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
JIRA. :p

Nice catch though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Stupid auto correct. Thanks for correcting me. I've fixed up the OP.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Doomstick:
Is privacy guard enabled on 6-24 nightly? I went to app info but didn't see the option.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
No, it's in the 6-26 nightly.

http://10.1.cmxlog.com/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
I'll get on this (Both a flashable file and a Gerrit patch) when I wake up in the morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kraenesk:
I'm having issues getting vibration working. Have factory reset. Poisoned to stock re rooted factory reset and installed again and still no vibration. Have it turned on every where

Edit. It magically started working on it's own on a reboot to change something else...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] krapt0:
I can not get screen shot to work... Is it in this ROM? I am on latest nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killer Okain:
Still unable to get in-call notifications of SMS with the stock app with stable. Hasn't worked in any 10.x rom. Have vibrate selected in all the necessary places but no dice. Anyone else experiencing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slow_DC4:
Have you tried Volume Down + Power at the same time?

Another way is Settings > System > Power Menu > tick box next to Screenshot. Then all you'd have to do is hold down the power button and press Screenshot.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
a bug report for the front camera problem has been filled in jira... https://jira.cyanogenmod.org/browse/CYAN-1504

I've added a comment to let everyone know that this problem was fixed in the latest RootBox rom release (4.1). So the CM maintainers should probably check the code of this rom or contact de developer/maintainer to see what can be done to fix the problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Had my second random reboot on 10.1.0. So far both was when listening to podcast driving in the car. Using headphones plug in no bluetooth. Wonder if it's something with notifications at the same time something is playing?

I do get notifications when listening but it's random when it reboots. Will keep watching. I reboot first thing in the morning so it's not like a timing thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Was GPS active at the time by any chance?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Post your /proc/last_kmsg

Task650 is rebooting also, which in on for first time. Looks modem related.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
no, unless it popped up and closed, sometime i see the icon and it goes away even though i don't have any gps apps open? I use foursquare regularly so if it's gps it's not appearent that's what causing it.

can you tell me how? (PM if it doesn't belong on here)

I updated to the latest bootloader and modem while i was on M2 so I would be able to move to the 10.1.0 stable when it was released. I have my doubts that it's modem related because i did not have random reboots on M2 even with the new modem but I'm no expert either ;).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Task's AOKP has an issue with reboots while listening to audio while GPS is active. If GPS is on and is used however briefly, that may be what's going on. It seems this issue is related to the modem based on what I could gather from my last_kmsg. I haven't had this issue yet on CM 10.1 (thank God!), but it wouldn't surprise me if it wasn't limited to AOKP.

The last_kmsg is located in "/proc", by the way. I usually copy and paste it to my ext sdcard and then email it to myself (it won't let me share it from its original location for some reason).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
https://dl.dropboxusercontent.com/u/8573299/last_kmsg

edit: doh, looks like it's blank?

edit: looks like when i copy it and try pasting it somewhere else once it's gets to the destination it has 0 bytes? Suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
Hmm, that's odd. When you view it directly in "/proc" is it blank?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
no looks like it's 14kb or so.

doing some searching now, this might help? http://www.codefirex.com/index.php?p=/discussion/7/how-to-help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Killer Okain:
I found this JIRA for RC4 https://jira.cyanogenmod.org/browse/CYAN-1325 and this change http://review.cyanogenmod.org/#/c/43970/ Is it possible this didn't make it into 10.1.0?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
From terminal:

su

cat /proc/last_kmsg > /sdcard/lastkmsg.txt

That will output your last kmsg to a file named lastkmsg.txt on your internal memory.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zadigre:
you can also copy the last_kmsg automatically after a crash with the following app :

https://play.google.com/store/apps/details?id=se.mumu21.bootlog
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jiangyi:
Gerrit commit adding the latest Canadian firmware (Merged): http://review.cyanogenmod.org/#/c/44836

ODIN-flashable package for I747MVLDMF1: http://d-h.st/7hA

Just a note: As it stands right now, anyone with this new bootloader version will not be able to flash any builds before tomorrow's nightly, including the RCs and stable build, unless they explicitly edit the updater-script to remove the bootloader assert. This is one of the few exceptions where I wouldn't bash people against doing that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
Awesome, here it is: https://www.dropbox.com/s/5ng87lbas01yzhp/lastkmsg.txt

---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------

Awesome, installed! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goodtimes50:
This doesn't look like a modem issue to me. Could be some kind of issue with your external sdcard, but I'm far from an expert so take that with a MAJOR grain of salt...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Just a quick question. Is this IN ADDITION to LK4 or is LK4 being removed from the assert forcing everyone to the latest? I'm upgrading either way but was just curious.

Cheers and thanks again for doing this. Saves me the trouble of having to open a beg report. It's nice to have someone around who can help out like this.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
If you check the commit it's adding, not replacing. :)

require version-bootloader=I747UCDLK3|I747MVLDLK4|I747MVLDMF1|I747MUMBLK3|I747MUMBLL1

Previously

require version-bootloader=I747UCDLK3|I747MVLDLK4|I747MUMBLK3|I747MUMBLL1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Thanks. Hadn't quite gotten that far yet.

I guess the question is then in the long run what's the game plan? If we start allowing more than 1 "acceptable" bootloader it's quite possible CM runs into the same issue it just resolved by forcing everyone to one common bootloader.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
I understand your train of thought and agree (partially). It's possible there would be no issue whatsoever with any new or "deprecated" bootloader that is currently accepted in the future, thus we wouldn't run in the same problem.

I think the upgrade of the bootloader alone is difficult for a lot of less experienced CM users and last thing we need is to make it more complicated for no good reason.

In short: We'll cross that bridge when we come to it. :p
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Agreed. Was simply asking the question. It is nice if we can keep everyone on the same page and while yet I agree, all bootloaders going forward should be stable and acceptable but the problem is there are now more variables introduced. I'm just of the school that less variables makes debugging easier.

Yes we will cross that bridge when we get to it.

I can also report that the new modem has no affect on the 4G issue I've documented a while back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] polobunny:
So still no fix on that I see? Did you ever find a suitable workaround in the mean time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thatusmguy:
Where can I find the latest bootloader. I'm on lk3 and keep getting the status 7 error when trying to flash the latest nightly. Coming from official AOKP 6-15-13 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MSgtSimon:
See my quoted post above. Simply, I would guess that you are actually on an earlier bootloader, but the modem version is ...LK3.