yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mendy7511:
And I am with Fido and I have no problem either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Deggy:
Quoting for later use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] yulet:
We got no nightlies in the last 2 days :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
I would seriously rather them stop doing nightlies all together and just focus on CM10.1. Once they get the camera fixed Im making the jump and won't look back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wavrunrx:
dude the nightlies are done automatically by a buildbot.

producing nightlies has absolutely nothing to do with how fast 10.1 is pushed out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
Did a fresh clean install last night. Having black screen and lock ups after ending a phone call. Any suggestions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Did you alter min/max or voltages? I've read some folks have had success increasing min to 486.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
I had the exact same thing happen to me. But after three or four calls, it stopped doing it and works fine now.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
Will try. Thank you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
No matter what, someone is checking, double checking, and merging code. Yes, they might be built by a computer, but it does not check or merge code.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ima.monstaaa:
I'm not sure if its available in CM10 (running AOKP currently), but I know that its just not waking from disabling the screen via prox sensor. So if you're able to you can disable the prox sensor during calls to avoid that issue, but its not a fix by any means.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mis3:
I'm the opposite. I would much rather them fix the couple of bigger issues with 10.0 instead of focusing on 10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Everyone is going to make the jump, so I dont see the point.. but everyone can have their own opinion!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GHOSTIVVI:
Cm10 is fine the way it is. I'd rather them focus on 10.1 and have everyone transition to that instead
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
So I went back to CWM v5.8.4.5, and then reflashed into v5.8.4.7 and still no luck. The error is symlink: some symlinks failed, E: Error in /sdcard/cm-10-20120718-unofficial-d2tt.zip, (Status 7)

I'm not sure if this is a SU, recovery, or zip problem and I'm at an absolute loss! I've tried downloading the file multiple times so I don't think it's a zip or download problem. Any other ideas?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Jhoopes517:
Did you root before hand? I used the toolkit.

Maybe flash back stock and go straight from the toolkit in
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Were are u getting your cwr from ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
I've used the one I downloaded from the OP link, as well as straight from Rom Manager, neither are working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kobos311:
Yeah I found the issue most of you are flashing ICS gapps to fix the camera there is a gapps and a camera data zip somewhere then reboot and then recovery and flash the current jb gapps and everything should work then still working on a cm build of this just At work right now and trying to code and help customers is difficult haha

Sent from my SAMSUNG-SGH-I747 using Xparent SkyBlue Tapatalk 2
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ThatTmoGuy:
working on BBS but no MTP.

yeah im still having MTP issue's is there a fix yet? im just going to dropbox BBS but mtp would be nice!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drawde40599:
Weird , if I was u I'd just start doing **** , things I would do , u have a SD card ? Pull it out try without card .... pull battery for 5 min , make sure su binary up to date , remove root permissions from ROM manager clear caches from ROM manager try agn . Uninstall and reinstall ROM manager , these are all things that have fixed past issues with past phones for me some don't make sense on y u would even try ( I no this ;) ) but I've read every page of this thread and official ROM manager has fixed for everyone with your fail ... your issue is strange . Hope that helps ...

Edit : I've even seen the way u enter cwr being important try 3 button entry to cwr instead of reboot to recovery.....

I'm no dev just a guy with to many phones running cyanogen ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] airtower:
It should be, but it requires a patched APK found here as well as build.prop changes to make the app think you're running an htc_jewel. The patched apk alone will get you a running app but if you want to activate your $10 prepaid card you have to mod your build.prop, or so I'm told at least.

I gave up after getting the patched APK running since I was apprehensive about editing my build.prop in a build as green as these CM10 builds are. Let me know if you're able to get it running.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naturefreak85:
That's likely Google Now. Do you have Latitude turned on? Google Now with the location services WILL use more power.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
lat is off, i'll check to verify...

I just don't understand how my xoom isn't doing that. have a look, i'll post the pics in a sec. my xoom is the same setup (JB) with same widgets, apps, google now etc.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Shouldn't be comparing battery life/drain for a tablet and phone, like comparing apple to oranges. Unless both have the same exact hardware, your going to pull your hair out trying to get them t be the same.

I have nexus 7, sgs3 and galaxy 10.1 all running JB. My nexus of course has the best battery life t that's because it came with JB. My Galaxy Tab drains battery with AGPS or GPS on when it works fine on my other devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
I'm not comparing battery life. I'm comparing wakelocks :) with running same os, and same apps, I would say it's much closer than apples to oranges. lol

don't even look at the battery life. look at wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Wakelocks generally are battery drainers. My point is, not everything is going to be the same between the two no matter how much you try. I have the same exact applications installed on each of my device but my Galaxy Tab has the most issues with wakelock/battery drain compared to my sgs3 and Nexus 7. I can't have location services on at all or the wakelock kicks in for hours and that's because it still needs work as the sgs3 still needs work and the xoom still needs work. If the camera crashes on the sgs3 it creates a wakelock but doesn't happen to my other devices. This is alpha, expect differences between devices...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Goatblaster:
Didn't read back all the way, but not sure if you tried this already RE wakelocks. Did you try going into "system settings" menu -> "sound" and unchecking "dial pad touch tones", "touch sounds" and "Screen lock sound"? I've had these wakelock sgs1, sgs2 in the past, so I just keep them disabled completely now - could be the culprit.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
I'll try that, I remember about that from my atrix actually.

that was the culprit for audioOUT_x one I think
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boland216:
I'll give this a shot and let you know, thanks very much for advice!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
Kind of confusing how these could be wake locks when the screen is off lol, I'll try it out
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Nelsocracy:
I find it strange that LTE works on AT&T but isn't working on the Canadian carriers, even with the proper APNs. I've been trying to look into a way to fix it but I don't really know what I'm doing so I haven't had much luck. I edited the xml file with the default values to fit the Rogers LTE apn but I still have only HSPA+ and 3G connection.

Could this be something on the carrier end? Do they have a way to block certain connections?

This rom is awesome but I'm too used to LTE now so I'm hoping there is some workaround.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kenneth.Torres:
So I tried to go to the camera app from the lock screen, I took a picture but force closed and now I have 2 camera and gallery apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
I'm in the same boat. I'm sure the camera will be properly fixed, eventually. Same with the overlay.

But the LTE issue is puzzling to say the least. I've tried all I could (not much really) and I don't get it. I don't see how it could be something on the carrier end unless there is some sort of an handshake protocol that takes place on other carriers. LTE is working with ATT, is it with Sprint Tmo and Verizon (not even sure if they support LTE to being with)?

Edit: I'm also wondering if this issue exists on other LTE phones (GS2 LTE) on Rogers with CM10
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ysandhu:
I have tried CM10 before.. almost 2 months back. came back to stock Samsung just because of camera image quality.

Can someone share .. if there is any improvement with camera image quality. I mean in comparison to stock camera image quality.

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
the CM10 camera works pretty freakin good man, just sayin.. i will NEVER use TW.. EVER. its just too laggy and choppy and so full of erroneous BS
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kswa1987:
edit: wow I am really tired, that was some **** grammar.

Outline format:

- have run the stable

- am running the latest nightly

- CM camera just isn't as good as the TW camera

: End :
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mis3:
Last I tried 2 weeks ago, video camera still had the same problems with the bottom microphone not working, making volume way too low. At this point, that's a deal breaker for me because I have a six month old. Bluetooth problems were just a minor annoyance.

I used cm10 or aokp for 6 weeks, and did like the options, but switched to the new official jb roms. After de-bloating and using kt kernel, it runs just as smooth as cm or aokp, I get better battery life, and camera, camcorder, and video playback are tons better. If cm could fix those, I would come back, but instead, it's on to 10.1, which will bring a new set of bugs.

CM is a great option for some people, and everyone should check it out, but it seems kind of silly to make statements that you will never ever use tw because it's too choppy and too much bs. Anyone who flashes custom roms should be interested in trying out everything, then go back to what you like best.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Altaman:
I agree, fix the couple issues & put out a final stable then move on fully to 10.1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vvelvetelvis:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Camera and recoder both work fine on latest nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mis3:
Really? You confirmed that the video recorder is correctly using the bottom microphone to record sound and have replayed videos you took with a correct and loud volume?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
Google Maps won't use GPS location

I have the same issue that simpletrick had where Google Maps would not seem to use the GPS signal, although both GPS Status and GPS Test capture a fix within mere seconds and relay an accurate position. All I get is the approximation based on the tower. I've tried the whole cache/data/reboot/reinstall of both the Framework and Maps.

He said his was solved with a subsequent flash of the ROM.

I was wondering if anyone had any ideas to fix this problem, without having to do a factory reset?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
yea definitely dude, and I said that because I have tried pretty much ALL of the TW ROMs we have here for the d2att, and I just dont like TW. hence, why I use CM :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortskoolbus:
Hey guys, any chance someone can check this for me? Tying to figure out if it's my problem or if it's an issue with cm10'
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fortesquieu:
Which video player did you try?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuckyStrike88:
I have the solution to this, found at another forum!

1. Go to "Settings > Accounts > Google > Location Settings".

2. Flip the switch to "On" (I found this was off in my case).

3. Try Google Navigation again, it should work fine.

In JB the location settings need to be enabled in 2 different locations, this fix works flawlessly for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I kind of wish the nightly's would switch to weekly's. I think I'm gonna just flash on Sunday night's to the latest update since here lately there hasn't been very many changes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
You can flash as often as you want. Why would you want them to stop working on the rom?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mahler47:
One problem with the CM10 camera is that you can't change the exposure. (More specifically, you can change the exposure but it doesn't do anything.) Might this be one of the reasons why the stock camera has better image quality?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
Amen! I just want the bluetooth to have bass! I will flash everyday until it works. I dont care, i'm just in the podcast industry and listen to shows constantly thru BT>
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
I never said I wanted them to stop working on it. I just think if they would not worry so much about getting a nightly out every day and just do a weekly since there haven't been that many changes lately, it would be easy on them. Maybe going to weekly's would help push out 10.1 (aka 4.2.1) to our devices.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
I vote for Hourly's
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
Hey all. Loving CM10 so far. Wondering if its possible to somehow remap the hardware buttons to move the BACK button to where the current menu button is. I also read some people have added the soft keys. I am open to this but my preference would be to just swap the hardware buttons if possible. I know there is an area in cm10 to customize the menu and home button but nothing as it relates to the back button. Thanks all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
They don't worry about getting a nightly out. There is a buildbot that produces the nightly. They will be merging code and fixing bugs and anything that makes it in by a certain time gets added to the build. This doesn't stop or slow any development at all.

HA. Nice
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kidoh1:
I can confirm that the latest nightly does not fix the microphone issue with the camcorder.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Yeah, I'm still getting really low recording volume also on the new nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dligon:
https://plus.google.com/+CyanogenMod/posts/UVCLobnA8Kz
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Very nice, looks like we're getting there :)

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Can't wait!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
I just scan the changelog to see if there's any major bugfixes or new features added. If yes, flash, else, skip. Of course, if you have OCD (which I don't), you might feel... compelled... to flash every single nightly :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Awesome

---------- Post added at 04:33 AM ---------- Previous post was at 04:32 AM ----------

Working fine for me....on dec 11 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
THANK YOU 1000%. Now if I could only wrap my head around why there are two settings options for the same thing, I'd be set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I have that setting turned off because it causes wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
I assume that the Bluetooth bass(less) bug is still there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Epikarus:
turn off location reporting and location history in Maps settings. this way you can keep location services on while eliminating most of the wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
It has always been off and I still get mad wakelocks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Really? I haven't had one since I flashed the newest cyanogen release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ChrisG683:
Same here. Some days it will never run, some days it will have over 2000 wakelocks with an hour of CPU on time. Usually turning off Location Setings alltogether will fix it, but sometimes Maps still runs.

This has got to be my biggest gripe about the Android ecosystem. Getting rid of Maps isn't really a viable option, and there's no quick toggle for Location Settings, so no matter which way you go it's frustrating.

I think it's an app problem, not an Android problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Developer options are not saved when the phone is rebooted. I noticed this because hw overlays are enabled once again when playing dead trigger.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I believe this is a known issue and it will be fixed with the release of 4.2.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Boss2212:
Is there any way to change target locations of the apps to external SD (more precisely for the offline music on Play Music) using this ROM setting? Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Sounds good, I also had a random reboot today when replying to a text message, but didn't have one after that. Might have just been a one time thing.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
I've had a few reboots on the last 3 night lies.

Also does anyone know the difference between the ringer mode with lines coming out of the speaker, and the same symbol with one vertical line on the back of the speaker? Is the latter vibrate and ring? They seem to be the same in usage.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
This happens on occasion. It may be best to clean,clear, wipe... everything. Then re-install. I've not had an issue in quite some time.

.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ak789:
Has anyone seeing choppy video and too much noise on skype on cm10 nightlies? I have 3-4 nightly all have the same issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Why don't we get a stable rom now instead of attempting to have the latest and greatest? This has really been pissing me of lately.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
how could anything you use for free, piss you off dude?

AT&T SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MJPollard:
I'm sorry, I think I missed the passage of the law that states "free" means "immune from criticism" (or, in this case, being pissed off). Guess I must've been asleep that day...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
I have no idea what isn't stable. Everything on my phone works fine. The latest nightly works great. If you want completely stable and support it is time to go stock.

The ROM isn't immune from criticism, but it is a little ridiculous when someone has spent countless hours coding something and now your bluetooth bass doesn't work so you are pissed.

Edit: Redundant statement haha
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I don't ever get random reboots on CM10 w/ Ktoonsez's kernel & I'm undervolted like crazy on top of that! Works great for me. Very quick & snappy for me! One of the reasons people are on Cyanogenmod is so that they can have the "latest & greatest"! You can always go back to stupid @$$ Touchwiz!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
what part of his post would qualify as criticism? did we (you and I) read something different? because the post I read said he was pissed over the fact that cm attention has shifted too 10.1..either way I'm done with wasting space over it..CM10 is 100% stable with one or two small issues..

AT&T SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shortskoolbus:
I was using moboplayer, which I know used to work with everything. But actually I just tried mx player and is working... so guess is okay now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] garrettc67:
Your question has been answered in many places. The devs don't want to fix things twice, first for 10.0 and then again for 10.1. You are pissed that they won't do extra work for free?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Getting very good battery life on the 12/11 build
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
Adding to what that other guy said, I appreciate all the hard work, but I will admit that I'm a little frustrated with the Bluetooth bass bug. This is one of the most used features on my phone, and I'm stuck on the 11/10 build because I want it to "just work". I get where he's coming from on this issue...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chris_barsoum:
Hey I have a couple of questions.

1. Is it possible to make the sd card the default location for anything (eg, downloads)? I've done some searching and it doesn't look like it's possible for the camera.

2. Also, is there a setting to keep the capacitive buttons always on?

Thanks in advanced.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
For your camera save's to the SD card, go to this link and download and flash the zip file for JB.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Bluetooth issues

The unofficial 10.1 has the bluetooth bass fixed! Now it is just the camera that keeps it from being a DD for all! I just wonder why the "fix" can't be applied to this ROM... must be more compliated than that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tony_YYZ:
It's not as simple as just copy and pasting sections of code from one OS to the other especially if the architecture and underlying framework is not the same.

Could just be that the issue was never present in 4.2 due to some features that were added to 4.1.x by the CM team are now native in 4.2.x
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Delete this
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
It's not possible to use it if isn't stable. So what there is to be greatful for? I am happy about this current rom and development but they should really focus on only one point and make it stable.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Wond3r:
What is there to be grateful for?

It's called effort. What incentive would they have to release anything at all if everyone was ungrateful for their time?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CptTwinkie:
Please don't confuse buggy and unstable. They are different and calling the rom unstable when it is not is libelous.

Now if you really have a problem with the bugs in this rom then I see two solutions for you: Fix it yourself or use a different rom. Neither one of these is accomplished by whining in a development forum.

Sent from my Galaxy S3 [AT&T][CM10]
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Latest nightly is awesome. I love it. Great job cm10 team!