yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
Perhaps this would be a good add to the OP

http://cyanogenmodlog.wordpress.com/faq/

Also, some simple dirty flash instructions would be good for the OP. I know a lot of the postings look like issues caused by bad flashing, or app data issues. This info is available if you search, but it's a bit confusing the way it's presented. Maybe this helps:

I do all this with ROM Manager, it can also be done by hand.

1) Do a Nandroid backup from a software version you are fairly happy with. You can use this to always go back.

2) Prepare for the flash by clearing Dalvik cache, cache, data and system, it's ok to reformat.

3) Flash the new ROM and then flash Gapps

4) Reboot (See Note 1 below)

5) Once phone starts Reboot into Recovery again

6) From Advanced Restore, restore Data (see Note 2)

7) Reboot/enjoy

Note 1: At this point the phone is completely clear of your data, if you want to test specific aspects of the build, this is when to do it. If something works now, but doesn't work later, it's not a ROM problem. If it's broken here, it *IS* a ROM problem. If you don't want to go back to your previous settings/configuration, just start from here and move on.

Note 2: This will restore your screen configurations, icons, passwords, apps and saved app settings. After you restart, if you find an app is acting weird, you should go into App Settings, do a Force Stop, then Clear Cata, if it's still not working try a reinstall of the app.

If you screw up you can always restore your nandroid backup from step 1 and get things back the way they were.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ferris2375:
How is the home button wake issue with the last few builds?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jjcore:
Same. Two presses to wake up. Sometimes one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Can't speak for anyone else, but it's consistently one press for me here. (I *am* on an i747m; maybe that makes a difference?)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] MethodX:
New Nightly is out

http://get.cm/?device=d2att
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Make sure under Settings/More/Mobile Networks that network mode is set to LTE/GSM/WCDMA and not GSM/WCDMA preferred.

Also, being "almost" positive about LTE being in your area makes me wonder :P
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
It also says a lot about a person when ...

It also says a lot about a person when they ask a question that's been asked and answered a thousand times.

Peter

---------- Post added at 12:21 PM ---------- Previous post was at 12:19 PM ----------

I have the I747M, and I also have the home button issue. It's intermittent, but still there.

Peter
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Phateless:
Didn't realize the man himself is personally heading up the work on this device. Now I'm really excited.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
GPS doesn't work on the latest build for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Flyarnk:
Works great for me!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] abteer:
Go to settings -> location services-> GPS source and make sure internal is toggled.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] FaithCry:
hey guys,

sorry if its been asked before, (i would use search but tapatalk doesn't have it/i dunno where it is) but does anyone have issues with google now not being able to pick up your voice when you ask a question? i'm having a hard time compared to the gnex.

thanks, and apologies! :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] IUH1991:
Already was toggled, still nothing.

Never mind, got it to work by using GPS test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Google Now and some other services that record voice/ audio seem to be routed to use the top mic. I'm unsure whether this is feature or bug with Google Now, as I feel much more natural talking to the top when asking for information or giving a command.

Sent from my SAMSUNG-SGH-I747
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loserskater:
It's not a feature, I believe it's throughout the rom. I think recorded videos have the same issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hunter99507:
Im having trouble flashing via twrp, it says failed when it tries to read the file. I am going from stock to cm10

It fails after it says "verifiying partition sizes" in twrp. Im assuming thats causing the problem. How do i fix that?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
L@@k at what the OP says
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
All of my recorded audio comes out faint, you can barely hear it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacecasespiff:
Try this. Before you listen to your recording toggle the volume a few times. I've had no audio when I record video so I toggle the volume and now I can hear my recording just fine. I don't know if its the same issue ad the mic but it might help
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
Hey thanks but even when I send voice notes to other people, they can't hear either.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Dennis0201:
I have the same issue since CM10 uses top mic to record the audio. There is one specific app Line which tends to use regular mic to record and now it's not working at all. I hope CM10 can supports regular mic to record audio, not top one ONLY.

Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] derberts:
Ya because this rom is brilliant
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
Is there any good app same as Task manager? As I do not have it anymore with this ROM and lately my battery has quick discharges quite often.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] smelenchuk:
Anything you specifically need from TM that you can't get from the normal long-press-Home-button menu?

If you're trying to diagnose battery issues, randomly killing tasks may not help very much - you could try out BetterBatteryStats or similar, which helps tremendously (when used properly) in identifying what's using up your battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacecasespiff:
I think I have a fix for this. Not sure if it fixes the low sound but I know it fixes the no sound that kept me away from all cm10 ROMs. Open the video that you want to watch then toggle your volume up and down a few times then play your video and you should now have sound . I've been reading that's what you need to to after installing most of these ROMs is to toggle the volume . So it the same thing .
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
I really wish I had a better handling on the inter workings of android, because this audio routing issue seems to me to be a trivial undertaking. Or if not in the code, then its in the drivers. How can we not use drivers from TW os when they are specially designed to talk to the hardware Anne answer to the software, what does it matter what software asks the question. And if it does, way can't we convince the drivers they are inside a TW ROM? I'm good with java, php, HTML, CSS, perl, and even had a few tangos with the samali code? I think that's what they're calling it, anyways. In building any application or software, audio issues where never an issue. But I have no idea where to begin to fixing this. I've tried several times to start my own King's of cm10 so I could start to get a handle on androidOS but every time something goes wrong in the setup of my building system. I've tried several Linux distributions, all 64 bit on an overkill system with ssd drives and raid arrays and a six core processor, you'd think it would just fall together. But most of the time its during the initial repo sync, or the numerous apt-gets to manage all the necessary programs and libraries that are also needed, then there's the android SDK. So many things to go wrong when I just want to help!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
TouchWiz doesn't have anything to do with AOSP CM10. Samsung doesn't make their drivers open source that I know of.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
So then why do we have this audio routing issue that's been there for a month now? Can any devs chime in on this please?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Nightly builds. Deal with it. End of discussion.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kplaga:
I HAVE THAT PROBLEM WHEN I AM MAKING PHONE CALL. I THE SPEAKER IS SO SILENT.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PeterGuru:
Nightly Builds or not ...

Nightly Builds or not, it's NOT the end of the discussion, and who are you to tell us otherwise?

Yes, I am fully aware of how difficult and time-consuming it can be to develop ROMs. I've done it myself, and like the business I own, unless you are willing to help your customers (we Android users), your efforts will die a tragic death.

It would be nice if someone could provide some kind of answer to the mic recording issue, even though it's not a problem for me ... and even if that answer is something we don't want to hear. Having a response is better than being left out in the cold.

Peter

Addendum: Here's what I would define as a professional response: "Hello, everyone. I'm "so and so" with the development team. We recognize the issue with the recording location, and we are looking into it. You can be sure that if there's a solution, we'll find it. However, right now we can't say how long it will take but, rest assured, your comments have been noticed, and we take them seriously.

Regards,

So and So
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mitchdickson:
That's all well and good, but you are not a cyanogenmod customer.

I'm sure the devs are working on it and when it's fixed, it'll be made available to us. There's nothing more to say about it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
This is not a business. These are not customers, and you, myself and everyone else in this disaster of a thread (as most rom discussion threads are) are entitled to absolutely squat.

The devs are not here to hold your hand, pat you on the head, and tell you everything will be ok. Have some bloody patience and let them do the work. Or, go back to some crappy touchwiz rom where everything works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
I don't know where you got the idea that I am demanding this to be fixed right ****ING NOW!

No, I simply want to know, as a programmer, what exactly is wrong with audio routing that I may perhaps even join in to try fixing it. Who do I talk to about this? I'm pretty confident this thread will not produce any answers.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
in another rom when I was doing normal long-press-Home-button menu, I had task manager, in this rom not. That's why I asked
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Sounds like stock rom. This is AOSP based. They will be very different.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
seems like it and that's why I asked if there is something like that if any.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
Open the app that is bothering you and long press back button to kill it. This is a setting I think, if that setting is off it won't work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spacecasespiff:
I would go to the cm website and email them.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xiphosurus:
date / time is lost every reboot

Every now and then, I get an error from Whatsapp that my date is wrong (3/14/1970). I found that if I uncheck "Automatic date & time", even if I manually correct the date, it loses the correct date after a reboot. Is this a bug?

Even when I do check "Automatic date & time", it seems the correct date/time is updated automatically after Whatsapp complains...

Also, all my nandroid backups show modified time as the 1970 date, this is bad, as now I don't know which is which...

This reminds me the date/time error on desktops when the CMOS battery is dead... but for the phone what other battery is there other than the big one??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Yes this is a bug. I use ClockSync with sync on boot as a workaround.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jamesbra:
They probably have an irc Chan. If so that would be the best place to talk to devs and see if your skills could be useful : )

Sent from my slowly but surely customizing SGS3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Their IRC channel is #attSGS3 on Freenode and it's DEAD. Unless you know of some other one which I would be happy to join.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
You sound really pathetic. Developers made this thread to get feedback because this ROM is not 100% daily driver material. Its a DEVELOPMENT thread. It was made to bring up such issues.

As for me, I reverted back to "some crappy touchwiz ROM" because CM10 's audio bug wasn't working for me. Even in the touchwiz ROM, everything doesn't work 100% so I don't know what your saying.

Unless your a developer and know what your doing (and from your xda account, it looks like your neither) how about some respect towards others, and let them talk about what they honestly want to talk about/ bring up.

Are you a moderator? No. Are you a recognized developer? No. Are you, just like me and 98% of us here, just a guy that loves to flash ROM's and tinker our phone? Yes.

You, my friend. Are a troll. And this is when I stop feeding you.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
I went on a github hunt, and it appears that there is only one actual maintainer for this device, and it's cyanogen (aka Steve).

Path: https://github.com/CyanogenMod/android_vendor_cm/blob/jellybean/CONTRIBUTORS.mkdn

The other listed maintainer has been inactive for a year now: https://github.com/Unhelpful?tab=activity

This sucks, because cyanogen's way too busy and d2att isn't even on the officially supported device list: http://wiki.cyanogenmod.com/wiki/Devices_Overview

EDIT: It appears there are two people who do anything for d2att:

cyanogen

noobnl (indirectly through contributing to general d2 devices)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
You'll have to forgive Peter -- being Canadian he's ultra nice & apologetic and expects everyone else to be too. :)

And in regards to the dev-unacknowledged month-old low-recording volume audio bug: It's not *that* bad. The volume is low, sure, but if you max it on playback it's "good enough". I record my kid with this "crappy ROM". :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
That was helpful. :rolleyes:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
Most commits are on d2-common.

Gerrit is generally a better place to check out what's going on. http://review.cyanogenmod.com

Also, if you want to contribute, just start. Code changes have to be approved so if they don't like it, the device maintainers reject it.

So if you feel you have the ability to fix it, grab some logcats, grab the sources and have a look. You'll learn a lot more pouring through the code yourself than asking people here. #cyanogenmod-dev can also be somewhat useful.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Perhaps you could help me finding the specific commit that switched the audio mics.

The problem first occurred in the Sept 11 build, so naturally I looked through september 10 and 11 commits:

http://review.cyanogenmod.com/#/q/status:merged+project:CyanogenMod/android_device_samsung_d2att,n,z

http://review.cyanogenmod.com/#/q/s...nogenMod/android_device_samsung_d2-common,n,z

Did not find anything relevant in there. Looked in general commits:

http://review.cyanogenmod.com/#/q/status:merged,n,001fac0500005a12

Did not find anything relevant there either. What am I doing wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
A lot of audio changes were pushed around the 4th and 5th. Specifically stuff to do with the sub mic/stereo audio recording. Whether it "broke" the media recording or not is another issue.

I think the best way to go about it is not from the standpoint of "someone broke it around this date" but instead doing some diagnostic work and fixing it based on where the code is currently. So much has been changed in the audio in the last month, and with good reason.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] catzilla:
Perhaps for this specific problem this would be the best approach.

However, for general purpose: how does a commit make it into a nightly build? My assumption was that if a commit was merged at any time where time(nightly1) > X > time(nightly2), it will be in nightly2.

Is this wrong?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thracky:
First the change is submitted to Gerrit for review, then the device maintainer(s) review the code. Once it's approved by the maintainers, it gets merged and will be put in on the next nightly.

http://wiki.cyanogenmod.com/wiki/Howto:_Gerrit

Fairly good overview.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nate_sheedy:
My thoughts exactly Peter.

And I run CM10 as a daily driver with out complaint. Furthermore, my initial statement was not meant as a complaint, but only any inquisition as to the logic and relation behind the simple problem of "my sound don't work".

Regards

Nate.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
Is there a option in cm10 if somebody call I called text them with a text message I will call back like he original s3?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] the_professor.:
cm 10 blu tooth error

i download it cm 10 d2att.my bluetooth connects but no audio.any ideas how to fix it?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BourqueJ:
No voicemail indicator

Hi,

I've been searching around to find a solution to my problem but I don't see people reporting it.

I'm with bell and running the build 20121007 of CM10. My problem is that I don't have any notification when someone leave a message in my voicemail. I do not have Visual Voicemail... only regarlar voicemail.

Anyone having the same issue? Is there a way to fix this?

Thank you,

Jacques.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] l337krew:
I'm also having the same issue as Borque, voice mails don't show up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tonymtl:
Phone/settings/quick responses
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BourqueJ:
What is your provider? (I'm trying to see if it's provider specific or more general...)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
Are they still going to continue with the Monthly Builds of CM10?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Is it necessary to post this here after posting it in the Q&A forum? :confused:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
Had no feedback in that thread, even after bumping it. Just wondering if they are, or do you think they will?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
My battery drained from 99% to 55% in 4 hr 15 min with only data on, I did not use phone at all. Any thought what can it be? Trying to find out as I have limited use lately, but battery draining really fast
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] h_zee13:
I can confirm that I'm having the same issue. I have a bell S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ztmike:
Can anyone comment on why we can't move third party apps to the external SD card? I found a link talking about it and the reporter goes on to say cyanogen mod ALLOWS this ..but I can't do it running this nightly build? If its not supported in this ROM yet..will it be?

Link:

http://www.chainfire.eu/articles/113/Is_Google_blocking_apps_writing_to_SD_cards_/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wes78:
As of the past few nightlies... the battery is actually amazing, for me. Fairly heavy use past 5 hours since charge and I'm at 83%.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Other devices already have an Oct monthly build, so I would guess d2att s/b coming fairly soon. Haven't heard otherwise.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Pedro Peguero Jr.:
All I needed to hear. Thanks buddy
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] seh6183:
In regards to the mediaserver wakelock, I have been unable to get rid of it. I have tried the following to squash it:

Scanned entire contents of phone and SD card with a program that looks for corrupted files. It found 2 but the wakelock is still there.

Disabled all syncing accounts.

Deleted google music.

Cleared data on "media storage".

The phone is still deep sleeping, it just bugs me that when I check my wakelocks I see a ton from mediaserver.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
what can be an issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
I can't find any mentions of this in the thread. I noticed about three or four nightlies ago that there is some sort of problem with the screen turning on/off at the appropriate times during a phone call. Within a couple of seconds, the screen turns off before I put it to my ear. So it's not the proximity sensor turning it off. Then the real problem is that I can't get the screen to turn back on. The only way the screen will turn back on is when the call is ended. I have to depend on the other person to end the call since I can't get the screen to turn on to do it myself.

The only way I've figured out how to avoid this issue is to turn the screen off myself by hitting the power button. I have to be quick and do this before the screen turns itself off. Once I am able to turn the screen off myself, I have full control of screen on/off using the power button. But not the proximity sensor.

Has anyone else run into this and if so, has anyone found a fix?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
That is a proximity sensor issue. Do you have a spectre on your phone?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] soccermon15:
A spectre? Pardon my noobiness but i don't know what that is

EDIT: found out that the smudge on my peeling screen protector is over the sensor, causing the screen to turn off. That's a relief. I have done way too many clean flashes hoping to fix it
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] arfarf2:
SPECTRE was who James Bond used to fight, duh. I think he had a Galaxy Note tho

Sent using xda premium
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] drewd:
Lol, this Spectre is a tempered glass screen protector that has a rep for affecting the proximity sensor.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Ian1331:
I don't know about you guys but I'm pretty excited about the new LED functions on 10/09! Been waiting on the battery LED and I like that the colour has been adjusted specifically for the D2. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
You guys think it will be possible to add on some stock features like smartstay etc. There are a few in CM10 but there are some cool others that could be added
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] l337krew:
bell also
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] naddie:
Is external storage for the camera a planned feature? It's been a while and still hasn't made an appearance.

It's a concern because IIRC, none of the CM builds for the Vibrant had it (and I think certain models did not either). The SGS2 I9100 had it though (so no rhyme or reason). I hope our I747 will get it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pseudoware:
Wait no more! :good:

http://jenkins.cyanogenmod.com/view...fact/archive/cm-10-20121009-NIGHTLY-d2att.zip
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] slow_DC4:
There's Screebl, it keeps the screen on based on the orientation of the phone rather than using the front facing camera.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bobloadmire:
while that is cool, it's not really the function I'm looking for.