yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
I went back to 12/27 and audio works again with stock kernel - may hang out until 12/31 unless anyone has any better ideas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] DarthDerron:
Based on what I hear I guess data works well with KTs kernel which was my biggest concern. HAPPEH HAPPEH HAPPEH :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Check under Settings->Wireless & Networks->More...->Mobile Networks->Network Mode.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dammit_dan:
I keep on getting camera cannot connect after taking a picture and have to reboot to make it work again.

I am using 12/30 nightly full wipe of all and clean install. I did flash the KT Kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
It throttles down to 3g when you're not using data and when you need it goes to lte if you're in an lte area.

---------- Post added at 08:01 AM ---------- Previous post was at 07:39 AM ----------

I also just installed the 12/30 version with the kt747-12/29 kernel and it works perfect. Even you tube works which didn't work for me on 12/29 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] goobs408:
Did you try fixing permissions?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Re audio, it seems to me that it's working fine for me with *most* apps (on 12/29 and the stock kernel; haven't checked this with 12/30 yet, but I don't see how it would have changed). The exception is Apollo; whenever Apollo starts up and/or tries to play music (haven't nailed down exactly what triggers this, other than that trying to play music definitely causes it, and it occurs sporadically otherwise), it freezes up and does its best to take the rest of the system with it - i.e. random freeze-ups and possibly needing reboots in exactly the manner that other people are describing.

I'm wondering if freezing Apollo will help alleviate this behaviour at all.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] andriel:
Google Voice issues

Not sure if this is related to the other Gapps issues, but 12/29 did NOT like the 12/19 Gapps for me. Voice would not open at all. Keyboard, search, or any feature requiring voice search would shut down. Flashed the 12/12 Gapps and had no issue from there.

For the record, I did a clean install. In fact, I even formatted system, data - everything - because I wanted to rid myself of some old junk. The good news is -- 12/29 with 12/12 Gapps is the absolute smoothest & butteriest I have seen to date. My phone is absolutely liquid. Haven't tested everything, mind you, but wow - am I happy with the butter.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
FYI - Latest KT 12/29 kernel is running great on CM 10.1 12/30 nightly. Tested most things but not BT. Audio, video, data, GPS all seem ok. Feels really smooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
Just noticed a little problem I'm having with the touch screen. When I swipe up to go further down on the page goes the opposite way and when I use swype the swipe will get interrupted in the middle of the word and spell two different words
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
Are you using the stock kernel or a different one?

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] erbsmokah:
I'm having this problem with the 12/29 KT kernel but not with stock kernel. I tested both for a brief time but could only duplicate with KT's kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
Anybody with 12/30 (stock kernel) able to test Pandora? Still acting odd/locking up the phone?

Everyone seems to be running KT or not trying Pandora/Apollo/etc, which rather defeats the purpose of the nightlies as a test-bed for developers to garner feedback for improvements that eventually are part of the stable release.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Obviously, which I said if you read my post. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dammit_dan:
Sorry to ask, but how do you do that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tarphoun:
I have problems with some audio apps as well. Some of them just lock up when you try to play something. I tested on cm-10.1-20121229-NIGHTLY-d2att and cm-10.1-20121230-NIGHTLY-d2att using Built-in Kernel as well as KT747-Kernel-AOSP-JB-MR1-ATT-12-29-2012. Same results on all accounts.

These lock up on playback : Apollo, PlayerPro, Pocket Cast.

These work fine : Rdio, TuneIn Radio, Youtube.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Recovery -> Advanced

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
I flashed 1230 from 1226 which is the best version for me so far.

If I try to play any audio from any music app, the phone locks up and I have to pull the battery.

Flashed back to 1226 and all is fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] milicigoran:
Using KT kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RegBuckley:
I don't pull battery I just hold power button for 10 sec to reboot. Also I notice after audio glitch I get wake locks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Im using the ktoonsez 12/21 experimental kernel and it has fixed my audio problems.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
So the latest Nightly has the audio problem or the 12/29 also has it?

Sent from my Nexus 7
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pberge:
The 12/21 kernel fixed my audio problems as well. I tried moving to the new 12/29 kernel release and the audio problems came right back.

This behavior is the same on both the 12/29 and 12/30 nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] russell1997:
I'm sticking with 26 until I see audio is fixed and bluetooth is reliable.

Both.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Where can I get the 12/21 release of ktoonsez kernel?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Off of his kernel thread. Just look around the dates of 12-20 & 12-21. Its under "Original Android Development".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Right here: http://www.mediafire.com/?6ucxm4f733frnu8
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
12/29 ktoonsez kernel is pretty sweet!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
In the change log for next nightly it says:

'update to uscc lk5 kernel sources', anybody know what that means?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
But apparently audio does not work with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Audio working fine here with 12/30 nightly with KT kernel 12/29. I use poweramp though. YouTube works perfectly also.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 12packabs:
Running that same setup and same for me. Apollo and Play Music do lock up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I flashed ktoonsez 12/29 ,SIO and Interactive, I cleared cache and data for play music, rebooted, and play music is fine for me both streaming and device music
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
Is it normal that the data signal sometimes displays nothing at all? Then it will come back after 5-10 secs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikeandjaimie:
Add slacker to the list of non working music apps.. Sux cause it's the only thing I pretty much use.. Love there Hard Rock channel. Finger crossed it gets nailed down soon heh
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sublimejosh2000:
This most likely pretains to the US Cellular variant, not ATT...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Mine is doing that too, its certainly not normal but I'm not too worried, its works
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
I've consistently seen that in two circumstances - when the phone's first connecting to a mobile network for a given boot, and when the phone's connecting to an LTE network after being on something else. I think it's normal.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] android_4life:
This Kernel says AOKP will that work with pure CM? I know AOKP is CM based, but I just wanted to make sure before I flash.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ormuz:
Yes it works. I'm using it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
That's the Ktoonsez 12-21 kernel. It will work with Cm10.1. Check his kernel thread. I think he put a new one out.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Agreed - I had the audio issues until I went back to the 12/21 kernel - now finally audio is working great with the 12/30 nightly and the 12/21 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
What exactly is that audio problem you guys were experiencing? Is that the Pandora, Slacker and any other audio apps?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Anytime I tried to play audio on any of Google Play Music, Mog, Pandora or Beyondpod, the phone would freeze and need to be restarted. This is similar to many people here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
Aokp is not cm based. But they are both aosp based which is what the kernel is for
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
Yes it is!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
No, it's not. Ask Task.. ha

---------- Post added at 01:51 PM ---------- Previous post was at 01:49 PM ----------

That 12/21 kernel is ONLY for Cm10.1. It was specially made by ktoonsez.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Maroon Mushroom:
Tested it and was able to recreate the issue using turtable.fm last night.

It was able to play a few tracks but eventually it completely froze. Had to battery pull.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Just noticed something with the group messaging.

When sending a textmessage to multiple recipients, it sends from the same thread. The responses come back as individual threads per person. Aren't they supposes to come back to the same thread?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
They stay within the same mms message (Multiple Recipients) for me and can be seen when just selecting the individual.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No. It's not. All it takes is a little initiative to look for yourself if you would like the information. This picture is pretty self explanatory. AOKP does use some cm code but for the most part is from google source up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well let me re-word that. The initial outgoing message , going from me to X amount of people, is one thread. All of the responses from each individual will be received by me as an individual message from each individual recipient of the initial outgoing message to X amount of people. The initial outgoing thread will not have any other messages in it other than the initial one I sent.

I thought the responses were supposed to go to the initial thread? Similar to iOS group messaging
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
And I can see those incoming messages in both places, group and individual.... Idk mang...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
That's weird.. I just tested it again with 3 recipients and all of the responses came back as their own individual thread as if I didn't have the group message
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nccu_eagles:
Why did they draft Greg Oden ?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tjisana:
When calling an automated system like voicemail I don't think the phone is sending the keys I press. When I enter my voicemail password on cm10(or even aokp) it tells me incorrect password but when I use a stock ROM it works......

Anyone else getting this issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Yes I did once with Google Voice, but after a reboot and going to bed it seemed fine in the morning..

---------- Post added at 04:50 PM ---------- Previous post was at 04:37 PM ----------

OK confused.. The group messaging works fine with some people and not others. Is it a device/carrier of the recipient based thing?

Edit: looks like if the recipient has an SMS app capable of group messaging.. It will work. For me, iPhone users responses stay within the group thread. Others that are on android 4.1.1 with stock ROMs return as an individual thread. Got it. I may sound stupid posting my mental process out loud here but im sure there's at least one other that was wondering the same :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
I'm not exactly sure what is going on here. I never paid attention to my SD card before, but when I was starting to reach the internal memory limits, I started to move over gigs of pictures and videos to my SD card in the device.

Well first I noticed that the internal memory is at a path called /storage/emulated/0

I have no idea why the internal storage is like this.

Then I tried to access my sd card and the only application that could access it was FX File Manager. ES File Explorer and the CM file manager can't access the sd card.

The FX file manager is able to access it. ES can see it only when you want to move a file to the card and then it starts listing many locations. I think they were like /storage/sdcard0 /storage/sdcard1

And once I started to move over thousands of photos and video to the card, Google+ started to use all my battery and data for some reasons my phone would heat up and I had to uninstall the Google+ app. Turns out the SD card was being mounted and unmounted by some kind of software bug. There was no issues with the card card hardware wise, but the system would unmount the card from the file system unexpectedly.

This would somehow also cause Google+ to think new photos were available to upload and would continue to upload hundreds of existing old photos every time the sd card was remounted.

It came to a point where I think the file system became messed up and the OS is reporting it. I'm out of town and I don't have the adapter to check up on the micro sd card to see if any actual fil system damage occurred.

I removed my SD card in the mean while. I wonder if I found a bug related to the sd card. Wanted to report this in to see if others have a similar issue or such.

I also am curious on why the file system on the device is set up like it is with paths like I posted above, where it says emulated and /0.

I also found many old device files and media files located in /storage/emulated/0/0 and it can keep going down like that. It seems like it happened on the major OS upgrade.

Note I am not complaining, I am reporting an issue I came across and I hope it helps in the development.

This was on the Dec 27th build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
For the love of God learn how to search.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
For the love of god. Shut up.

Seriously, instead of being helpful or confirming, you tell me to go away and search for something I'm reporting.

I'm SO SORRY... I pay attention to the thread every day the best I can. It expands by several pages each day and I have yet to see any mention or report or change log mention this topic.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rupa:
If the message coming back I'd a regular SMS (eg they'll are still on cm10) then it will not come back add a group SMS. If their phone replies with a proper group reply, then it will get threaded (eg iPhone out current cm 10.1)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
I use root browser & don't have any problems moving stuff to my extSD. Maybe you should try to backup all your apps & do a clean install. Try out root browser first & see if the problem persists. Its a good app it just makes you look gay when you say the name of the app to someone else lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
I'm thinking of doing a full wipe of the device in the future and doing a complete clean install and storage. I'm gonna back up all my files when I get back home.

I'll check out ROot Explorer. FX file manager is nice until you need to move, copy, or extract. Horribly slow on that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
All this hostility is unwarranted! Yes searching is helpful but doesn't always give you the answers you are looking for , for your specific question.

Regardless, CM10.1 incorporated a new system for storage making it "emulated" which allows for multiple user devices. Meaning the initial user is at sdcard0/0. And follow on users are "sdcard0/1, sdcard0/2 and so on. It saved your old files in "legacy" so you didn't lose them.

On a cell phone, its not really useful unless you share the phone with someone else, but I can most definitely see the value of it with something like a family tablet.

Anyway, that's why the storage is all different now. So you can do what you will with the /legacy file system. Just make sure you don't delete anything you need

---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------

Yea I did a little playing around with different people that I know have cm10.1 / android 4.2.1 / iOS and realized that
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Go to the pages where cm10.1 was first released. There is page after page of discussion regarding why the file system is arranged this way. Also talks abut why you get recursive /0/0 folders. It has been beaten to death hence the frustration with why it is brought up again 10 days later.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MystikMajik:
Does anyone know where I can find an inverted version of this latest CM MMS apk? All the versions I've found are much older and less functional.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Drybones5:
Tank you very much. I hadn't even thought about the user account switching ability. Doesn't come to mind much on a phone, indeed.

I guess it'll be much better when I do a full phone wipe.

---------- Post added at 06:25 PM ---------- Previous post was at 05:53 PM ----------

The file system isn't the reason I posted. The SD card messing up and causing mounting issues and more was the issue I was reporting. NOt the file system. I was making a comment on it and figured it probably had to do with 10.1. Someone already answered that, even though it wasn't a main concern.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
No. I got yelled at in multiple threads for the same reason. USE THE SEARCH FUNCTION BEFORE ASKING QUESTIONS. You are not right here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Going to say it before a mod comes in here. Its done. Drop it bro
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gordietm:
CM seem to be putting a lot of effort into their Trebuchet launcher lately.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] acloaf:
Sorry I understood your post as asking about the file system so I figured I'd point you in the direction to find that info.

I've had issues with my SD card as well but I'm not sure if its an issue with my card or the software but my card was unmounted and completely unreadable one morning when I woke up. Removing it and trying it in different devices confirmed the failure as it cannot be mounted in any device. Lost a bunch of nandroids but fortunately I keep my most recent ones on the internal SD. I suppose is possible that an issue with the software took out the hardware but I haven't seen any other complaints about it so it may just be a freak incident.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
SD cards do go bad every once in a while.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
Why would you want to do that? Google Now is awesome. Its the one easy thing I demonstrate to iFanboy to shut them up when they start getting out of line.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
Android battery stats are reporting that the phone is sleeping with the screen on. I'm running 12/29 with KT's 12/29 kernel and battery life and heat output seem noticeably better.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
Been running 12/30 nightly with KT kernel 12 /21 and it is running exceptional. Also extracted the aokp messaging app and runs perfectly. Build is A1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] astralmind:
I'm also getting similar results with stock kernel and have been for the past few builds. Sleeping with screen on nice ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Can you upload the AOKP messaging app or inbox it to me?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I was on the phone with my friend and I couldn't hear him at all even with the 'extra volume voice' option checked. I'm on the latest nightly with ktoon's latest kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Slacker is great. It seems to play better songs for me than pandora, but still, I use Pandora 90% of the time. I must be like those people that get in the lane with the most stopped cars at the intersection for no good reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gmac1990:
I'm also having similar issues. Just clean flashed and all and the issue persisted. Anyone have any ideas ?

Before anyone freaks out, yes I am aware these are nightlies. I'm not complaining, just trying to find a solution.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
+1
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mntbighker:
Back to 10.0

I decided to revert to the 10.0 stable until 10.1 appears there. Too many glitches for me lately. After 10.1 is stable I may go back to nightlies.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xaznxplaya:
I'm not able to edit any contact, it crashes instantly, anyone else having that issue?

Ps: It's actually the contact that are synced with haxsync...

PoWeReD By that SeXy s3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MoeisHere:
for those of you having sound issues tonights nightly will fix that. so flash a prior nightly before 12/29 or wait until its up
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Oh? What changed to fix this? I don't see anything immediately evident in the changelogs.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I'm actually looking for it but don't see anything related to sound.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dhinez:
Pretty decent battery life with cm10.1 12-30 and KT 12-21 kernel.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
Im sorry this made me laugh.. What's not "stable" about this? Data is perfect now. The only thing to possibly complain about is battery life and it's not even that bad.. To each their own I guess..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
You haven't used the latest 12-30 build then.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jeremysv:
Hmm.. thought-provoking statement.

What is a "stable" build vs. a "nightly"?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
That I am good sir. Using Ktoonsez 12/21 to fix audio, and just a third party app for old photos to show up. ZERO problems otherwise. I'm a heavy user so my battery life is alway mediocre.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
I'm using 12.30 with not issues besides Pandora (all other music apps have been working fine) and tango which has been acting weird the past few days..other then that everything else is solid
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
A "nightly" can be "stable." "Stable" is just thrown around to much as a build with no bugs, but that's just not the whole truth. This ROM, since data is fixed, is 100% stable and a DD no questions asked.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mmurphmsu:
Running the 12/30 build with the 12/21 KT kernel to fix audio and all is well. I first flashed the 12/29 kernel and the borked Pandora. Reflashed the 12/21 kernel and things are back to normal.