yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
What change in particular makes it look so good to you?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
All of them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Huh? I posted it dude. Also. The kernel is clearly labeled. Word of advice for you next time. Always read what you are flashing. If you don't. You could end up potentially ruining your device.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Was there a nightly? I'm on the 1-31 nightly, unless this is the latest
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
You are in the latest... Last two nightlies failed to build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
...... Everything you're telling me is something I know. My goodness.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Well you fooled me then dude. Your posts prove that. Just read before you flash is all I said. I would do that or you will be the next to start a thread with "HELP!" in the thread title is all I'm saying. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I figured since the last few builds haven't made it through I would compile a build for you guys while your waiting. I have't tested considering I don't run CM right now and have too much going on but I know it works. ;) Everything has been synced up to 8:30am PST Today.

CM10.1 Build-2.2.2013

DOWNLOAD HERE
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
thanks task..:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Did you put your motor in it for added pizaz!? or is this just a straight 10.1 compile?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
All things I compile get built with my kernel. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Excellent! :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
Running super smooth!! Thanks!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Your one of the good guys Task!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
Google voice is broken. It only plays messages over the speaker, and yes the option is selected correctly in options...

Also there's some awesome lag when ever trying to type in swype that makes it almost unusable...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Not seeing the lag you speak of in Swype
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DeathKoil:
It effects more than just Google voice. Unfortunately you cannot open a bug ticket with Cm for nightlies, only stable, release candidate, and monthly builds. Google voice works properly on M1 but was broken on the very next build. I've got all of the information to open a ticket saved, waiting for M2 to be released so that I can report it.

I've narrowed down the issue as well. Details can be found here:

http://xdaforums.com/showpost.php?p=37471018
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Anyone else with atrocious battery life on 1/31? I tried everything to get it like usual. However android system is at the top with input devices being number 1 under that category. I wiped everything as usual before any upgrade I do, and installed tasks 1/26 kernel with the regular settings that I use. I did recalibrate the battery last night as it ate battery last night like a fiend.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Not atrocious, but i have had better. I typically use the included kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
"Google services" is slaughtering my battery. Anything if you monitor logcat?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
I must be one of the lucky ones. I was getting almost 5 1/2 hrs of screen time with ktoons kernel.

Sent from my Samsung Galaxy S-Beast!!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Turn off Google Now and Location Services.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LuckyStrike88:
How is the stability of the latest 10.1 Nightly vs, the last CM10 nightly? I am still on the latter and have not upgraded my wifes phone because it is relatively stable, the only issues being, most camera apps don't work, and bassless BT without making a call first. Have these been addressed?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
As a followup to my previous post about installing this kernel to see if it fixes the slowdown and laggy behavior my S3 exhibits, I found today, about 15 hours into using the new kernel, the S3 indeed became laggy again. It started being noticeable when using the default keyboard, then was very obvious when taking pictures - the camera lagged as it was trying to refresh the screen while moving the phone around.

I wish it had fixed it, but, alas, it seems independent of whatever changes you've made. I've read it theorized that it is some issue with using launchers other than trebuchet (I use Nova Launcher Prime), but I have not verified these claims.

Thanks anyway, task! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Signal Strength

Does anybody else have some weird numbers for Signal Strength under Settings->About phone->Status?

Mine shows 2147483647 dBm and 255 asu.

I see that same dBm number in the status bar when I set the signal status style to text. And I see it in Phone info as well.

Only on LTE, though. It's fine on GSM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrhaley30705:
Yeah, same here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Finally someone who has the same issue as me. I have been having this issue where the signal bar goes to 0 and the only way to get it to work is to call someone. If I don't call someone and go under battery settings, it will tell me "time without signal 67%".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I see the same thing...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rifleman2:
Ditto, same thing here.

Sent from my external brain.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
It's been that way for awhile now on LTE..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
It's actually not just on LTE. I have the issue on HSPA+ as well.

Further, I had this issue on CM10 back in December when I drove cross-country. Anytime I was in a 2g area on AT&T, it would do this to me. It was actually so bad that times & dates got screwed up and wouldn't rectify themselves when moving to a 3g or greater area until several iterations of reboots/airplane modes. In addition to this behavior, I could send/receive no texts or push through any data. I could, however, make phone calls - but they didn't fix the issue.

Seems like it's a deeper issue if it was previously there and has crept back in. I saw it early in January on CM10.1, but haven't seen it come back until the last week or so.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
I have older nightlies if anyone is interested. I think I have 1/20, 1/22, 1/27
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 02busa:
Mine has been showing signal strength perfectly fine on HSPA+ & below is all I can tell ya.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
new nightly is out, time to flash =D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I'd normally rush into flashing it, though I'm happy with task's self-compiled CM that he posted the other day: with that I have absolutely no A2DP issues!! Go figure! I understand that that boasts task's take on the CM kernel. What's the secret there?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
a2dp is fine on stock CM10.1 post-fixes, the problem is, after listening for a while, the phone starts to 'lag' and eventually becomes unusable/a2dp streaming stops. That is, with 01/31. I haven't tried the new build yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Well, that's precisely what I'm sayin': task's version doesn't do that! I have noticed what you say with the regular non-task compile, though for me problems start when attempting to navigate a playlist using the next, pause, previous headset buttons. Otherwise, streaming works fine if I don't do any navigation...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
This was just recently posted. Can't anybody follow a Mod's statement??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] superstargoddess:
Camera ICS breaks the camera? That sucks. Oh well, Cyanogen is on it with JB, so I'm sure it will be fixed soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
For such an early release this build is pretty solid IMHO. One of the better ones for the SG3! :good: Great job Cyanogen! I'm gonna buy you some beer next week!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
This thread is slowing down. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drwx:
I searched and didn't see this posted with these symptoms. Here is a brief description of the issue that i've found that is repeatable. If I have sounds turned on (not on silent or vibrate-only), and I'm listening to music with the headphones or an aux cable in the car, and I get a message or phone call or anything that plays a system sound, when the audio returns the volume is very very low even though the volume indicator appears to be turned up. Turning the volume up doesn't make it any louder. To fix it, I have to turn the volume down one click. Then it gets louder. then I can turn it up another click.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mastergrillo:
Well cyanogen is out if town

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
That's good. Means most of the bugs have been found or fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] NewKlNGjames:
Honestly people, the mods are going to lock this thread because we have 113 pages of useless crap.

Unless you have a rotatable problem that isn't in the op and you have a log to go with it please don't post here. If it is not of value to cyanogen to help him make changes to the Rom, please don't post here.

This thread is for people to help, not get help.This is not the place to talk about g apps, ask how to flash or even mention how much you love this Rom.

Please be respectful to the people donating their time to actually work on this project and put your posts in the correct place!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Repeated launcher crashes every time my phone reboots. It started after I installed the modded Google wallet apk so I'm going to uninstall it but I'll provide a log of it as soon as I test to see if that's what caused it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cuhrazy:
Have you tried a third party launcher? Like nova?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mash2k3:
im loving this rom so far, but there are a few s3 stock apk's i miss like myfiles for example is there a away to install it on this rom.

so far i tried flashing through cwm did not work, tried installing it using root exploler and it says install failed and finally snapdragon toolkit which gave me an error about certificates.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Moh_Jay:
Look up file manager in the market. Touchwiz apps won't work because they needs touchwiz framework
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cincygeek:
I had to jump ship back to CM9 due to the battery draining rather quickly :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
I've been using File Manager for a long time, it also gives you access to the root folder just like Root Explorer, and you can select multiple items at one......but it's free!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] therealdamiani:
Here are a few Stock SGS3 apps that work with Cm10 that doesnt need TWFW:

http://xdaforums.com/showthread.php?p=29144851#post29144851

Download and copy & paste Apk to System>Apps
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malaeum:
I might have another bug to add to the list, can someone please try to reproduce it?

When switching from the handset to speakerphone, the speakerphone volume is at maximum by default. Hitting the volume down button shows the volume slider is at the minimum volume already and thus the call volume continues at the maximum despite the fact that the OS thinks its at the minimum. To decrease the volume from the maximum you actually have to hit the volume up button to take it one notch up from the minimum volume (on the indicator) and upon doing so the volume switches to the correct level, that is, how loud it should be at one notch above minimum. Dropping it one notch back down to the minimum then produces the expected behavior.

Could someone please give this procedure a shot and report back with a few quick answers to the following questions?

Make a call on the handset,

Once it connects, switch to speakerphone.

Is it very loud? Mine is. If so, hit the volume down button. Does that decrease the volume?

If not, hit the volume up button once. Does that decrease the volume?

Thanks in advance for your help chasing this down.

Cheers!

Edit—This is almost certainly related to this bug:

@drwx: I just confirmed this, its the exact same (though opposite in magnitude) bug I've been having, same behavior.

Can someone please confirm with speakerphone? So we can confirm both and add them to my semi-official bug list.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] razorseal:
Is there a screen off nfc mod that works with CM10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malinois16:
Most of these don't work. How will touchwiz launcher work without touchwiz framework? I'm no dev to be sure but that just doesn't sound right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
This belongs in q&a
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Im pretty sure its because of his beast kernel. He said that he compiled it from CM sources but used his kernel. Its pretty smooth and flawless for me :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
Yeah, I know it's his kernel, but what exactly in/about his kernel I'd love to know, and I presume CM devs. might also find it useful. Is task's kernel cuttin' any corners? How come CM devs. don't seem interested? (I'm speculating at this point, apologies if this offends anyone.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pixbuf:
When can I get his kernel? Can I just extract it from the ROM he made the other day and flash it with heimdall? Is it the boot.img file?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] CamFlawless:
Check his thread's OP for his underwear kernel download link. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fastest963:
CyanDelta still doesn't show an update but there is one on getcm. Weird.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You're definitely making assumptions here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
FWIW: one thing that yesterday's task-built CM ROM failed at was propagating bind mounts setup in apps amongst other apps, so, I'm glad to be back on today's official CM nightly where it's working again. I rely on the SManager app to run a script at boot that bind mounts a dir on my external 64GB SD to /data/data/com.google.android.music/ in order to fit my dozens of gigs of pinned Play Music. Google will probably never officially support external storage for pinned music, since it's not "secure".

(P.P.P.S. Task: maybe check out this and this patch to get it working on your ROM too)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Those patches were part of the build I posted here considering they have been merged into mainline. There should be no reason that it wouldn't work for you. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aqua1ung:
I certainly am. Would you care to elaborate about the changes that your kernel has vis-a-vis the standard CM kernel? Or is there a place where you've discussed that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
This newest nightly is based off the new aosp release? I flashed it but I'm not sure
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] AJ Newkirk:
Yet you do not bother looking at the source code?

Any kernel has to have the sources available. It can't be that hard to parse thru them and see what he has changed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This information has always been available and open for anyone to see.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
zmore, would you mind posting some step by steps on how you were able to move this over to SD? I can manually resize and maintain android partitions with gparted and tar, but moving google music escapes my skills!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] toddrosenberger:
Anyone tried to play grand theft auto vice city? As soon as you get in a vehicle the screen freezes. Not sure if this is rom related or not, I do know it worked on stock rom though. That's only issue ive had though, pretty damn stable otherwise
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Well, I clicked about a dozen links on Google, and finally got this one. Going to try it out.

http://xdaforums.com/showthread.php?t=1785245
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
Sure - I use a free app called Script Manager to run a small script on boot that bind mounts a dir on my external SD (make sure you create it first) on top of GMusic's internal data dir, masking whatever was there before. Might help to clear data&cache for GMusic once BEFORE you set the auto mount up, just to free up the space.

The script can live anywhere, but mine's @ /sdcard/bindmount_GoogleMusic.sh

am force-stop com.google.android.music
sleep 1
mount -o bind /storage/sdcard1/GoogleMusicCache/ /data/data/com.google.android.music/

Then tell SManager to execute it onboot and that's it.

The force-stop of gmusic at the top of the script is a workaround for a case where sometimes Music has started in the background before the mount is setup at boot, and if you then start the Play Music app UI, it finds itself in an inconsistent state, and happily proceeds to delete everything previously pinned and cached. I'd prefer to use early init.d scripts to avoid this problem, but, bind mounts from there aren't working.

HTH.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
How's the battery life on the 02/03 Nightly? I'm still at the M1 release just for the battery life. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
What the hell is wrong with mediaserver? It keeps waking up my phone even though I fully wipe between ROMs and I haven't even installed not even one app from Google play just to test it. I'm using the barebones of cm10.1 and mediaserver is giving me all sorts of wake locks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Excellent battery wth KT kernel, idling at about a percent an hour!

---------- Post added at 01:18 AM ---------- Previous post was at 01:15 AM ----------

Try reflashing. It shouldn't be doing that. If you run a music player and then kill it, Media Service should stop too unless you do something to wake it again.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
I wonder if the following is a ROM or a network issue. I'm currently in France, and am staying there for 5 months. Simce arriving, I noticed heavier battery drain (now it's about 7% an hour compared to 3 back home). I unlocked my phone and I'm using a french sim card. I've been on a few nightlies since arriving (clean wipe always) and the problem doesn't go away. Is the fact that I'm not on my home network (Rogers) causing this drain or would it be a rom issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kenkill:
which modem is better for your region, france have different network.

update your modem!!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I agree, usually I don't see significant battery drain unless I have poor network signal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] t.square:
Thanks! Where would I find french modems for a canadian SIII?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] philalford:
Recorded my drive to work the other day with the time lapse feature in the stock camera app in CM10.1. It's really, really cool and thought I'd share. http://youtu.be/52_AEx9hjDA

Now flame away :D

(P.S. I don't always drive like that, just wanted to make it interesting!)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Very bad lag after bluetooth audio

Getting very bad lag on new nightly 0204. Press and hold home button and back button vibrations are long, like they are dragged out. sluggish home screen. Slow to turn on screen from power button.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BlackDino:
whoa that is trippy, anyone know of a time-lapse app that allows you to record while in the background?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] adammur:
I'm getting exactly the same issues.

Sent from the future in a tie-fighter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
I don't understand this and I want to reproduce it. Press and hold the Home button then press the Back button?

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arminyack:
The 2/04 build broke my data =/. Anyone else having this "issue"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I think what the previous poster is saying is that actions are laggy, such as holding the Home button to bring up the recent apps, or the Back function.

This is the behavior that I and others reported last week on builds from the last 10-12 days or so. It's very visible in the 12-12-12 gapps camera app, as well as the basic AOSP keyboard in any app that uses it. It only happens to me after 15 or so hours of use, independent of battery level.

I think I may be closer to narrowing down the behavior to a common subset of activities that lead to the lag on my phone, but I'm not yet sure. Fresh (clean) installs don't help, nor do other kernels.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] etham3:
Your IMEI might have disappeared. Do a search on the forum on how to restore it if thats the case. Be warned, it is rather tedious and may require you to return to stock touchwiz (at least it did for me).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
A small bug I found in 2/04: select dark theme for SMS doesn't work

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
The dark theme is only for the SMS popup for Quick Replies. Take a look at the heading that setting is nested under.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pcshano:
that's really weird

i remember one of the previous version they have dark theme for SMS itself, not quick reply
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] moose&beer:
What version? I don't remember such a setting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
And you guys are using the Stock CM10.1 kernel?

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Is the signal strength fixed in the new build? The stock TW ROM doesn't have this problem but on cm10.1 it goes to 0 and drains the battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ganjah:
I was for the first week of experiencing those issues, yeah. Now I'm using task's kernel and, although it didn't fix the lag issues, it has better battery life than I had seen on the late January CM10.1 kernel(s?).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Have you tried using Ktoonsez' kernel? That's what I'm using and haven't had any problems.

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blk_jack:
It seems this is related to a bluetooth audio bug. Seems to happen if you boot up with bluetooth enabled and it attempts to pair (too?) soon after boot. Try disabling bluetooth and rebooting.

The issue will spam your logs with audio related error messages and make vibrations seem really long and pronounced.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
This is absolutely insane. I'm starting to hate cm10.1 because of the damn signal strength bug. It completely drains the phone 0.