yashsingh1/xdaforums huggingface dataset:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] wilbarger:
I am running 3/6 nightly with Moretz 1.05 with no issues at all.

This is kinda crazy, but seems that everyone that has audio problems reverts back to 2/26 and the problem goes away. I never flashed 2/26, but started with 2/28 and have never had any audio issue. Maybe a crazy question for some of the real brains in this thread, but could the issue be something in 2/26 instead of every other nightly? Have any of you with NO audio problems ever flashed 2/26. I know it sounds nuts, but worth a try to help find an answer.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 1BadWolf:
+1

Edit: I see CvD has updated to 1.06. I'm gonna flash and test.

Brought to you by time and relative dimensions in space.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
I'm on 3/6 and motrtz 1.06 and everything seems fine so far. Have done a few reboots and still working. Keeping fingers crossed.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] nelsonmc:
Yesterday I tried the M2 03/04 . Wipe everything and flashed also gapps-20130301... Everything was ok , and a started to instal some of my apps and one of the freeze at the instaletion process. So I rebboted and audio still ok . After some more installetions another freeze and another rebbot the audio problem comes again .

I tried to wipe cache e dalvik , fix permissions and the problem still there . Call conection is ok , but with no sound ...

I am at uclf6...

Back 02/ 24
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 1BadWolf:
So weird. I just finished restoring because I lost phone audio after flashing Moretz 1.06. Now I'm back on 3/6 with Moretz 1.04 and call audio is back. I didn't have any of these issues until yesterday. I didn't get call audio on the 3/4 at all, regardless of the which kernel I tried, so I would be surprised if it was the kernel that is the issue. Who knows, because I sure don't.:rolleyes:

Brought to you by time and relative dimensions in space.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Weird is right. After a few more reboots I lost the audio. :banghead:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] oktubr3:
To any person who reported audio problems, someone reported the logs to Cyanogen team? They are getting bugs reports for M2 version only.

Enviado desde mi SAMSUNG-SGH-I727 usando Tapatalk 2 // Sorry for my little English.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] copene:
3/6 w/1.06 = audio broken

3/6 w/1.04 = :good:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rpr69:
3/6 w/1.05 and w/1.06 = no issues.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] 1BadWolf:
Have you rebooted any afterwards? Jd1639 said the same thing as you until after a few reboots.

Brought to you by time and relative dimensions in space.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tkjeeper:
It's been asked several times, this is not the Moretz thread, there should be no discussion of it here. I understand everyone trying to help those flashing nightlies with audio issues but I thought there was no support on this rom without a stock kernel? C vs. D is great, but this is a cm 10.1 thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
Thanks for reminding us. You're right
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ItsDon:
Agreed.

CM10.1 stock rom/kernal issues are free to be discussed here.

CM10.1 + any other kernal should be discussed in the kernal thread.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] stoopendis:
Phone audio

Did a full wipe. Flashed 03-06 and then immediately new gapps (03-01). Audio on phone OK. Rebooted a few times..still OK.. Re-installed my apps via TiBU. and after a reboot.. still OK. 10 minutes..another reboot..still OK!!

will report back if problem comes back.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] beall49:
Thank you because now I'm confused...are people having issues with the stock kernel or not?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ItsDon:
Yes, I believe so which is why they are resorting to using another kernel. Doing that just causes confusion in this thread. It's a sticky situation (chicken/egg) but we gotta keep this thread strictly for unmodified CM10.1.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Andrw0830:
I agree, I just mentioned about Mortez Kernel as a temporary fix for the audio problem. I haven't tried the newer 1.06 to see if it still worked, I was just trying to help anyone who wanted to keep the latest CM10.1 without having to stay on 2/26.:)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Xeodus:
Just to let you know - flashing TWRP through goo manager, clearing the cache and reflashing CM fixed the problems and he's now happily playing with his new ROM.

Thanks again for the advice :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Krakozawr:
My brother catch an audio problem today. Yesterday I install to his Skyrocket the 03/04 CM with moretz 1.5 kernel for undervolting and arr works fine. Today from the morning all stay OK but after some time audio was broken.

Nothings works, just a full wipe and clear installation resolve it. Still with the latest CM 03/06 with a stock kernel now. All fine :D
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Krakozawr:
Upss!

Just now brother catch this bus again. During application's installation from playstore.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
What?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] mrfeuss:
Ok, so after about a dozen reboots I still have working audio. My process:

Nandroid>Wipe Cache>Wipe Dalvik>Flash 3/1 GApps Signed>Dirty Flash 3/6 Nightly (Full-not CM Updater)>SK8's Fix Permissions

I know this issue has been beaten worse than Rihanna, but it's been affecting a lot of people and I wanted to share what worked for me.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] NoSpamDan:
I full wiped and flashed an interim experimental March 5 version of CM10.1 (thanks Roger) using the 3-1 gapps and apps restore and call audio was fixed... until about 5 reboots and 15 hours later. Stopped working sometime today when the dialer delay and no audio problem randomly came back.

Had to restore my Mar3 nightly backup for now. :(

Debating flashing to the Mar6 nightly at the moment. I read the change log but there seems to be a lot of obscurity in what was committed from various requests, although I saw some mention of Bluetooth and I think audio...

I'm anxious to see the general consensus on the latest nightly as far as call audio working. Hopefully this bug is cornered at least :confused:

Sent from somewhere in Galaxy S2...
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] tkjeeper:
This is turning into quite a clusterf*ck!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] alanjames01:
I did a full wipe followed by the 3/6 rom and new gapps. Booted fine and I let Google restore all my apps. Phone audio worked. Rebooted and still good audio. Then on next reboot, started boot looping. Another hard reboot and still boot looping. Back to 2/26 but getting closer
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
That it is from all the Frankenstein stuff to try to make it work, but they are trying to make it work for everyone. Im on 2/26 for now keep it going Top.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ossito:
Not sure where issue is with this audio stuff but 3/3 running fine
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ka724ka:
I did full wipe, install 3/6 build and then new gapps (20130301). When boot completed, tested call audio has no problem. Reboot and calling out audio was broken, went to APN and found setting changed to 'ATT Phone', re-checked to 'ATT LTE', reboot couple of times, calling out audio is good.

Carrier: AT&T

Radio: UXUMA7
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
Can't make out your photo, everything stock? Radio, Kernel ?
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] kindofabuzz:
Just to chime in, everything works great on my skyrocket.

:)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Apsidal:
I'm on 3/3 and it's running great. It's fast and I have BY FAR the best battery life of any ROM or OS I've installed on this phone! I'm afraid to change it even when the stable releases!
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] uselessbass:
I was on latest nightly went back to m2 I was having a lot if freezing on last nighty it was the only nightly I had real issues with back on m2 everything's good again
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] rdnckreaper:
No audio even with bluetooth

I just flashed the 36 last night, it is the first flash I have done since 26 and I tested it this morning and have no audio what so ever even through my bluetooth. Nanding back to 26. I have stock recovery and stock radio latest gapps (wondering where photo sphere is with that one) and running twrp as a recovery.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] brogdonbr:
For What It's Worth

Since I complained a few pages back, I thought I'd share where I'm at. I'm cautiously optimistic that things are going to be OK now. When I rolled back to 2/26, I immediately noticed that a lot of my critical apps were severely misbehaving. So, I decided to do a fresh download of 3/6, fresh download of 3/1 GApps, and try it again. Just like the first time, everything was fine until I re-booted. After the re-boot, yes, call audio was dead. This time, instead of rolling back, I opened Koush's ROM Manager and ran Fix Permissions. I think I read that Fix Permissions helped someone. I don't know if it matters that Rom Manager fixes permissions from within an active Android session or not, but my call audio came back.

If audio dies again, I'm going to check the APN as I am on ATT and saw a few posts back that random changes to the APN could break call audio. I didn't check that before. Oddly enough, as I'm typing this, I thought I'd check and my APN was ATT Phone instead of ATT LTE. I switched it back to ATT LTE and made a successful test call.

It would be interesting to see if the people who have never had a problem with 3/6 were non-ATT customers.

I'm going to call this progress.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] sgvalenti:
I'm on ATT and I have never had a problem with the audio on any of these nightlies
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ossito2012:
Instead of take a beating mentioning whether stock or not :D, i will re-up the pic.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] brogdonbr:
Oh well...worth a shot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] pcidiot:
3/07 is up.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
On ATT and no issues with call audio from first 4.2.2 nightly to latest 3/7 installing on to of each other. APN is always ATT LTE and I've never fixed permissions. All works very well using stock kernel so following a strict update path there is nothing wrong with the ROM update path. It is more likely related to auxiliary installations, restores, etc.

I think those people having issues should be reporting on their APN when call audio fails, changing and fix permissions if needed with an initial reboot as well as subsequent reboot results checking APN again. This sound very likely important and relevant. It may also be important to highlight other auxiliary processes you are performing above and beyond a stock install that may be invalidating your failure reporting so as to help the dev quantify what is and is not is important to look at from a stock perspective. Too much mud in here to be effective.

Additionally, I will do a full wipe this morning and clean install 3/7 with latest gapps and all app installs restored only through play store and validate expected functionality both before and after subsequent reboots catching logs as required.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] Trinition:
No audio problems (any nightly, on AT&T)

Same here. I've flashed just about every nightly since the beginning of 10.1. I've never had an audio problem.

I was on the Dec 2012 google apps and had no problem. Now I'm on the March 2013 google apps and still have no problem.

The only ONLY odd thing I ever had was my APN was missing after one flash, but a reboot fixed it -- and it has never happened again.

So it seems we have two conflicting theories based on very real observations:

Some newer change in the nightlies breaks audio (because older nightlies work OK)

Something other than a change in the nightlies breaks audio (because so many on the latest nightlies don't EVER have the problem)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] stoopendis:
You may be on to something. I was running 03-06 with no probs. I dirty flashed 03-07 this morning. I expected it to have the audio probs but I didn't. So I did a reboot and bam! no audio. I messed with the apn settings by changing it to a different apn on the list then back again and 'walla" I have audio again.

:confused:
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
Just wiped everything and did a clean flash of 03/06 and gapps 201303 and rebooted let it settle tried to make a call no audio. I checked APN and ATT Phone phone was selected I selected ATT LTE pta did a test call audio working rebooted checked APN this time it stayed ATT LTE audio is still working. Still working after several reboots. Fingers crossed. Great job Top.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] onealvideo:
I use UCLF6 because I get better coverage... The CM10.1 has the RIL FOR UCLI3 built into it but other compatible radios are fine....
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
I don't know if I want to muddy the waters with this. But I'm having nothing but problems. I:

Did all wipes and factory re-set

Flashed UCLL3 (previously had problems with XUMA7 so thought I'd try this)

Flashed 3/6

Booted and didn't have problems with calls

Went through 6 re-boots, one I lost baseband but a re-boot brought it back

Then flashed 30301, signed into google but no apps restored

Then it went down hill, no call, which a fix permissions in recovery (TWRP) fixed

RE-booted and no call again

This is where I gave up. I had minimal problems until gapps was installed. Don't know if that will help anyone or just cause more confusion.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
Here is what I did I don't know if it will work for you but it worked for me.

I went back to stock with all of AT&T junk which has UCLI3 radio.

I'm using CWM recovery the latest one don't remember number off hand.

Wiped and factory reset.

Format system

Installed CM20130606

Installed gapps 201303

Wipe cache

Wipe dalvik

Fixed permission (CWM had two fix permission I selected "Sk8 fix permission"

Rebooted and let sit for 5 minutes.

Go into setting and if your on AT&T make sure that ATT LTE pta is selected.

That worked for me good luck. And I don't know anything about TWRP maybe someone else could address that.:)

It has been work
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] jd1639:
You're on the UCLI3 radio? That looks like the only difference

God promised men that he'd put beautiful women in all corners of the world. Then he laughed and laughed and made the world round
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] brogdonbr:
Throwing Some Fuel On The Fire...

I'm only posting these updates in the hopes that ANY information helps pinpoint the issue. After my earlier post describing my adventure with 3/6, here's what happened when I flashed 3/7.

I dirty flashed 3/7 using CM updater. When the phone rebooted, phone audio was broken. I checked the APN settings, and ATT LTE was still checked. I ran Fix Permissions using Rom Manager, and rebooted--still dead audio. I rebooted into recovery wiped Dalvik and cache, and now phone audio is back. Call audio still works after a reboot.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
Used cmupdater for newest nightly. Call audio still broke for me as well. Wiped caches and fixed permissions.. No luck.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] scubamikejax904:
Grab cyandelta from the market I've been using it and haven't had any problems (used cmupdater for the m2 update and got the no audio bug).

Rocking cm10.1 3-7-13 nightly with no issues
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ozziedog:
CMUpdater didn't work for me.

I downloaded CM 03/06 and gapps 201303 straight to phone and flashed it from their and so far audio is working. Knock on wood :)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
CMUpdater may be persisting the problem. Check your APN is on LTE first. If not, change, reboot, potential clear dalvik and cache again and reboot. If that doesnt fix it, you may need a clean install to correct whatever artifact is following you. Restoring from anything other than google account may persist problem at this point... so only do that last after verifying the phone is working after several reboots.

---------- Post added at 09:06 PM ---------- Previous post was at 09:03 PM ----------

Ok so having never had an audio issue, I blew my phone out for a fresh install to see if I could recreate the problem.

UCL3 Radio

Full charge, USB Disconnected

Boot into CWM6027touch_v14.4.6Sk8

Wiped and factory reset.

Format system,data,cache & dalvik

Installed CM-10.1-20130307-nightly

Installed gapps 20130301

Rebooted, attached to wifi,signed in to Google and let it begin restoring my 46 apps.

While google restored my apps, I checked my APN and "ATT Phone" was selected, not the "ATT LTE" that should have been. This alone suggests a problem but I did not change it so as to confirm a potential issue first.

I made an outgoing call and it worked fine, requested a return call and it worked fine as well.

I suspect my Google settings restore may change my APN automatically to LTE on reboot. Wifi is slow at work so I'm still waiting for my apps to finish installing before first reboot but...

so far call audio works fine even with the wrong APN
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
How did you come to this conclusion? All CMUpdater is doing is downloading a zip and then kicking your phone into recovery to flash it.

Now, the installation script within the zip itself only formats /system. It does not wipe cache, dalvik or user data (hence a dirty flash). So in that regard, sure I guess you could say that the problem persists if it resides outside of /system and the kernel; both of which are fully replaced during a flash.

Because the problem is intermittent and not impacting all users, it's enormously difficult to nail down what the root cause is. TC is looking at the logs they have to try and track it down, but not even all of them have experienced the problem.

At this point, it is being worked on and if they need more info they'll certainly ask for it.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Yes, this exactly. There is a potential for files to remain from version to version which could be contributing. I think its important to point this out for those troubleshooting problems that exist when updating but are different when installing from scratch.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
The only files that stick around are user files, not system files.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
Settings, Shared preferences and internal storage data persists. Any one of these could be storing something that has changed from version to version and is now referenced differently. Its not uncommon for nightly's to change this through the early development stages.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] lazer77:
The lte APN is the only one I have. I deleted the others. After cmupdater did its thing, I checked call audio.. Broke. So I then rebooted into recovery, wiped caches/fixed permissions.. Still broke. Has happened to me on every nightly after 2/26 which is what I'm on now without problem.

Edit: earlier today I tried my luck with the 3/6, didn't notice the 3/7 nightly. After work I'll try to manually update to 3/7 using cwm to see if that changes anything.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] car vs driver:
That's what I just said, you only said it differently ... for everyone else, here's a bit of education on the android file system:

/boot

The boot partition, this is where the kernel and ramdisk live. This is overwritten when you flash a new kernel or flash a rom (since pretty much all ROM's include a kernel). Your phone will not boot without it. When this partition gets hosed, that's typically when you have a hard brick.

/recovery

This is where your recovery lives. Obviously, it is bootable and depending on your recovery, will allow you access to other partitions when booted into this mode (including ADB shell access).

/system

This is where the Android operating system itself lives. All system applications live here in various directories. When you flash a rom, it is standard for the installation script to format this partition before flashing the new files to ensure that your old ROM is gone first.

/data

Here is where user data lives, such as user specific application configurations, downloaded apps, etc. Typically, a ROM installation will not wipe this partition. You have to do that on your own.

/cache

You guessed it ... here's where your application and dalvik cache live. Wiping this does not remove any settings or personal data. This data is automagically rebuilt when you start using your phone.

/misc

As the name implies, this does a number of things. It is primarily used to pass data around during the boot sequence. It also contains various hardware configuration settings.

So, when you flash a nightly only two of those partitions are touched during installation /system and /boot. If you've elected to wipe anything else on your own, that's entirely different.

My standard approach is to wipe the cache partition prior to a flash (including dalvik) to keep at least that much of it clean.
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] SoCalHTCFuze:
No Issues with CM 10.1 stock on UCLI3 with gapps 20130301 when installed from scratch

My wifi was very slow so I turned it off and let it complete using Mobile Data. With the APN set to "ATT Phone" it connected 4G and had no issues completing my app installs. I verified again that this setting remained and rebooted the phone.

After reboot, verified "ATT Phone" was still selected and made several incoming/outgoing calls with no issue. Rebooted again and again, and still no call audio issues.

I then switch my APN to "ATT LTE" and made several incoming/outgoing calls with no issue. Rebooted several times, and still no call audio issues.

So my conclusion is that there is nothing wrong :good:. I suggest you follow the same procedures above and verify before attempting other Kernels, Titanium backups or the likes of other modification which could skew your results.

---------- Post added at 10:13 PM ---------- Previous post was at 10:04 PM ----------

I had a feeling we were saying the same thing but I wasn't sure, I was just restating to be sure.

Nice writeup on the structure. I think this is very likely a persistent setting issue that has been changed and is now resolved. As more people install fresh this audio issue will likely go away. One of the pains of early adoption on your daily driver ;)
[AT&T Samsung Galaxy S II Skyrocket SGH-I727] ronbot:
Had phone audio dead issues, was on v 03 04 until 30 minutes ago.

Decided to restore nan backup from v 02 15... just prior to loading 02 26

(did Cache Wipe and System first)

Restore is OK, phone audio is working fine, rebooted twice

Best guess where to go from here?

my apps - should I take all the 34 (!) 'updates' Google Play is telling me I need (I was up to date on all apps before restoring)

thoughts?

/edit/

Immediately after restoring from v 02 15, had to set APN selection, was blank, did this before I tried phone