yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
I guess the only thing left to do since it seems to be working for everyone else... ready? Wipe and re-flash. If that fails then you'll need to format your internal SD too. Titanium Backup and Nova or Apex makes returning to full RM a breeze, since home screens AND many settings can be restored easily.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tasteslikechicken:
For me, it shows "3G" when at idle but then switches to the "H" or "H+" when there's any transmission. It is probably done for power saving. In my experience, CM10 also did this but never displayed the "3G" unless you really were in an UMTS-only area.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Lessaj:
Always shows 3g even when transmitting. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] :
Well I tried to use the January 13, 2012 CM10 but after booting it says "System setup has crashed" and then "Google apps has crashed" and it repeats this. I've flashed the ROM correctly and wiped everything but the problem persists. Just for your information I'm on jellybam prior to flashing Cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Just curious if anyone else has such a high battery drain from screen display. I think around 45-60% is normal for most people. I use to get around 55% with stock TW with full brightness. I'm on 01/13/13 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
I'm running the 1/13 nightly and the volume control pops up when the phone is locked. Not when the screen is off, but when the lock screen is up. If you hit the volume rocker up or down, it shows up on the screen. Any way to prevent this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maladju:
Without seeing a full day of stats and times, I would like to remind that if the rest of the system is using less power, it stands to reason that your screen will use a higher proportion per percent of battery drain than before.

Edit: unless you are not using your screen as much...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
That is true and I am aware of that. I should probably wait until later in the day to post a screenshot then. I know yesterday I wasn't impressed with the battery life at all. Just thought maybe this was common for some people.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
Anyone else having the issue of the home button taking you to the task list rather than to home when you press it from within an app? I feel like there have been numerous home buttons problems through the weeks, most of which I haven't experienced, but this one is pretty annoying.

I am running 1/14/13.

Thanks in advance,

David
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] tj_ona:
Yeah, i am having the same problem, but a reboot fixed it for now....
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
This was discussed earlier. Use a JB modem. LK3 for AT&T. LK4 for Canadian.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rytymu:
Rumor has it that 4.2.2 will address Bluetooth streaming problems... I wonder when that will be merged...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
As a side note...i used to have this same problem. I flashed LK3, problem resolved. I'd always reflash modem after flashing nightlies. but after flashing 1/13 nightly, i didnt reflash the Modem and my data signal has been fine.

Does the LK3 modem need to be reflashed every nightly or does it persist?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] chrisj22:
Has anyone found a fix for the home button issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TheSchatz:
Build 1-14 here, is anyone else getting compatibility problems in Google Play? It tells me my device is incompatible with just about anything, including Google's own services (Search, Play Music, etc.) which means voice search and voice typing don't work because they can't update.

I have my dpi set to 300, but that isn't the problem as I have reset it in my troubleshooting. I've tried clearing the cache/app data of Play Store and Download Manager, then rebooting and trying again (worked on my old Captivate) to no avail.

Is this problem just me? It has been on previous builds as well, and I did a full wipe before moving up to 1-14.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Once 4.2.2 is merged, A2DP will be fixed !

http://news.softpedia.com/news/Andr...udio-Streaming-Fix-Claims-Google-321408.shtml
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] spectrumfox:
I have encountered that bug regarding the home button suddenly functioning as if I was holding it down and bringing up the task manager instead of going to the Home screen. So, it definitely exists. Running 1/14 nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sk8trix:
Well I found it to work only on an open network I guess eventually it will be addressed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
Oops, delete...

---------- Post added at 07:45 PM ---------- Previous post was at 07:35 PM ----------

I had the same thing happen using DPI 300. Even though I put it back it broke compatibility with a bunch of stuff on Google.

Don't remember if I had to full wipe or just reflash ROM and gapps to fix it, but try wiping caches and reflash ROM and gapps first.

I eventually gave up on messing with DPI because of stuff like this. Seems like no matter how meticulously I installed everything or what DPI setting I used, I eventually wound up seeing this problem
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
The 1/15 build removed this silly commit. Was seeing this under Settings > Launcher every day at 3AM.

Did anybody else see this?

New commit for 1/15 removed this "hack".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
It also seems like Google keeps a record of your DPI in their database and it takes a little time to reset. We had this problem with 132 DPI on the HP TouchPad. I could be wrong though.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
Hey all, quick question on the LED notification light.

I used CM10.1 to program my GMail to be a 'red' light and a Text to be a 'green' light.

Say I get an email, it blinks red (as expected)

I then get a text a minute later. It still blinks red

It seems to only show the first notification color even if multiple exist. Is it possible to do either of the following:

-Show both (alternate red and green in this case)

-Show the most current (green in this case)

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
When you set DPI you have to clear data for Play Services and Google Services Framework. Reboot and then sign in to the store.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
100% agree, not only is it not moderated by forum moderators even those who took it into their own hands have given up. It's totally a loss at this point. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Swiftks:
Well you can rest assured that I will now be following this thread and deleteing the useless posts.

To everyone:

Your post should only pertain to this thread.

If you have questions, search before you post it. Also, your question should pertain to this ROM. If your question is about a kernel, modem, etc. please post it in the appropriate thread... Which is not this thread.

If your have a issue or problem, pertaining to this ROM... First, search to see if your problem/issue has already been reported. If it has, there is not need to report it again. Secondly, if you want your issue to be seriously addressed, you should include a log cat. If you don't know how to do this... Search.

Consider this your only warning. Continue to break these rules, and I will have no problem giving you an infraction, and we will go from there.

Thank you for your attention.

Sent from my SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Wi-Fi toggle lost?

Is anyone else lost the Wi-Fi toggle in the notification bar? It disappeared few nightlies ago and I can't get it back.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
I'm on 1/13 and I have my wifi toggle. Go go Settings > System > Notification drawer > Widget buttons. Then disable it, go back to the home screen. Then go back and re-enable it. Does it come back?

As mentioned a few posts above: enable it and disable it and post a logcat showing if there's an error.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Here is a strange overlay bug I have encountered while using Jump Desktop for RDP to my Windows server. Upon connecting to the server I see this repeatedly in my logcat:

E/qdhwcomposer( 243): configure: commit failed
E/qdoverlay( 243): Failed to call ioctl MSMFB_OVERLAY_SET err=Operation not permitted
E/qdoverlay( 243): MdpCtrl failed to setOverlay, restoring last known good ov info
E/qdoverlay( 243): == Bad OVInfo is: mdp_overlay z=0 fg=0 alpha=255 mask=-1 flags=0x40000 id=-1
E/qdoverlay( 243): src msmfb_img w=736 h=1280 format=14 MDP_RGBX_8888
E/qdoverlay( 243): src_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 243): dst_rect mdp_rect x=0 y=0 w=720 h=1280
E/qdoverlay( 243): == Last good known OVInfo is: mdp_overlay z=0 fg=0 alpha=0 mask=0 flags=0x0 id=-
E/qdoverlay( 243): src msmfb_img w=0 h=0 format=0 MDP_RGB_565
E/qdoverlay( 243): src_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 243): dst_rect mdp_rect x=0 y=0 w=0 h=0
E/qdoverlay( 243): MdpCtrl Lkgo ov has id -1, will not restore
E/qdoverlay( 243): Ctrl commit failed set overlay
E/qdhwcomposer( 243): configure: commit failed

The current work-around is to lock the screen and then unlock it, otherwise it gets stuck on the black screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ormandj:
That's the one thing that has been driving me nuts with 10.1. I'm glad to see it will be fixed upstream. Thanks for the link, and I hope the merge happens as soon as possible.

CM10.1 (latest nightly, 15th of Jan. 2013) is running wonderfully for me at this point. There have been a few minor glitches but they are being addressed quite rapidly by the CM team; the BT streaming of audio has been the only on/off again issue that's really been quite bothersome for extended periods of time.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Looks like there may already be a fix coming tonight... Fingers Crossed
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] BAM1789:
What fix are you talking about? A2DP is an ANDROID problem, not CM. We'll have to wait till 4.2.2 is merged before it's fixed...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
I am aware of google commenting on 4.2.2, A2DP. I am referencing the commits that are coming in for the nightly.

See here

libmedia: implement samsungs isSeparatedStream, built audioparameter

Committer

codeworkx<codeworkx@cyanogenmod.org>Jan 14, 2013 2:46 PM

Parent(s)

e0df2e7b19749ad40488d06bb557ce8d96ab3c37	audioflinger: Allow mixed use of JB A2DP HALs and ICS policy

and here

Make an exception for MR0_AUDIO_BLOB in loadHwModule_l

Without this exception samsung JB stock audio HAL crashes

Change-Id: I596e6e077f5bd4236359de48db754100e0a133e4

Committer

madmack<alali48@gmail.com>Jan 14, 2013 8:19 PM

Parent(s)

e0df2e7b19749ad40488d06bb557ce8d96ab3c37	audioflinger: Allow mixed use of JB A2DP HALs and ICS policy

Your emphasis on it being an "ANDROID" problem is true, but to insist that the CM team cant/ wont fix this before then is far from a fact.

:good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dammit_dan:
Anyone else having issues with AT&T Visual Voicemail not working?

I tried searching, but search isn't working at the moment.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
hey guys im like panicking because this is the second time im flashing CM 10.1 on my phone and again ALL my files are GONE :( the weird thing is it says i have only 6GB free which i had before i flashed cm10.1 but i cant seem to find any of my files anywhere.... please help

EDIT: NEVERMIND I FOUND THEM IN /DATA/MEDIA ;D im happy as fudge!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bxsteve31:
it wasnt working for a few of us either. the thing just spins and spins for me but it never gets to the voicemail screen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] peneoark:
ERMAHGERD
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
I don't think those are the fixes we are waiting for. :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dammit_dan:
Same here. Hope it works soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Helloworld294:
guys i found an interesting topic about this DATA MEDIA crap. http://teamw.in/DataMedia

now has anyone ever encountered this issue?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
This started to happen to me a a couple of nightlies back (maybe over a week). It is not limited to the home button, but to the menu and back buttons as well. This issue kicks in at random, and then when I touch any of these buttons, the phone interprets the "simple press" as a "long press". For the "home" button, this will bring the task manager, and for the "menu" button, it takes me to "Google Now" (because that's what I configured long press on "menu").

This doesn't go away until a reboot. The other work around is to select an app that doesn't have a lot of history, then click "back" (I usually choose the "Battery Stats" then click the "back" button).
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] madmack:
I'm afraid you're right. These fixes that we pushed are to get the Note 2 LTE variants going with CM10.1. Nothing specific for the D2.

I'm wondering why everyone thinks A2DP is broken from google's upstream? all references I see is that google acknowledges the issue for the N7 only. I don't think I've seen the other nexus 4.2.1 devices having any a2dp issues.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
Man, ... well that just sucks :banghead:, thank you for the info, I had the same thought about my nexus 7, it is running just fine... Or at least it appears to be.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
I've been thinking the same thing. Not to mention, a2dp was previously working on cm 10.1. I think it's just a CM/AOKP problem.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] shamidude:
I am afraid you are right... I was hoping that this was an upstream issue from Google (http://code.google.com/p/android/issues/detail?id=39633#c443) ... but now that you mentioned it: I think the early 10.1 nightlies didn't have the a2dp issue. Unfortunately, I deleted those early nightlies from my device, and I can't locate them on the CM site.

I wonder if there are others who are still using early 10.1, and whether they have BT issues or not...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ibanezbass:
I used a2dp flawlessly right before Christmas.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] imstill@g:
If anyone has access to something to test, Task just released his ROM with a Bluetooth fix... Someone please go test and report back to us less fortunate:D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Oh man, Task is really working some magic on his ROM and kernel. I'm very tempted to try AOKP for the first time because of his efforts. But I love CM...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Or just a little patience and you would see reports about whether it works or not.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Found somewhat of a work around for the unread text notification light not working properly. It seems like it stops working once the screen goes on. If you set your text messages notification settings - disable screen turns on when receiving text, the notification light works the same as an email.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] VeryCoolAlan:
Okay so does it affect how backups and restores work? Or affect anything else?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ReidStylez:
No.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
that's weird..I haven't had any issues with LEDs at all..notification or charging..1-15 nightly
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
Still no bluetooth on 1/16. Another day, another lack of bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
When your screen is off, and you receive a text message which makes the screen turn on for a short period of time to notify you, then times out and screen goes off, your notification light still works?

I'm on 01/13 and it works only until the screen times out. The led lights up when the screen turns on, but once the screen times out, the notification light disappears.

My work around is so that the screen doesn't turn on when I receive a text. The screen stays off but my notification light just turns on when I receive one.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] marinierb:
BT phone connects to my car just fine.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kennyaa:
He's referring to bluetooth audio streaming not working.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Johnny424:
yeah maybe that's the difference..I never allow my screen to come on when texts are received..other wise it would be turning on all the time due to my wife texting so much..my led blinks as should when screen is off ..and that is all that im concerned with I will let the screen time out and see what happens
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
Guys, since its related, a page of two ago I posted something on the LED light as well... Im not sure if this is normal functionality or broke in a recent release

I used CM10.1 to program my GMail to be a 'red' light and a Text to be a 'green' light.

Say I get an email, it blinks red (as expected)

I then get a text a minute later. It still blinks red

It seems to only show the first notification color even if multiple exist. Is it possible to do either of the following:

-Show both (alternate red and green in this case)

-Show the most current (green in this case)

Thanks
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] hartford:
Same thing. Screen on when text arrives, LED on. As soon as screen turns off. LED turns off. Guess I'll be disabling "turn screen on when new text arrives" until this is fixed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Thanks for confirming that the issue is not directly related to me. Hopefully this isn't a lot of work to fix.

---------- Post added at 11:13 AM ---------- Previous post was at 11:10 AM ----------

Not sure about having multiple notifications at once. Do you have it setup so that your screen turns on when receiving a text? Or does your screen turn on when receiving an email?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dschamis:
The more interesting thing is that there still seems to be a debate as to whether this is a CM10.1 issue or an Android 4.2.1 issue. Not that it really matters - one day we will do a nightly and it will start working again, but its a bit weird that such a fundamental thing has such open and unknown questions around it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PwnCakes193:
There should be no questions about it... it's a CM issue. It's always been. the only audio problem on 4.2.1 was on the Nexus 7. I'm still not sure why people don't understand that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpstiehl:
It's not a Android 4.2.1 issue. It's definitely a AOSP problem right now. Bt audio used to work just fine with CM10.1 last month. Flash an earlier build if you don't believe. Just don't ask me which one cause I couldn't tell you nor could I provide the build. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ExcelonGT:
Based on the advice of many others...I set up my phone to use Google Voice for VM instead.. Im SOO glad I did..its far better

Better VM notification. ability to listen to VM over email. VM playback integrated into the call log.

It was pretty easy to set up. I used this http://xdaforums.com/showthread.php?t=1882181

---------- Post added at 11:51 AM ---------- Previous post was at 11:43 AM ----------

If i had to take a guess id say 12/26..maybe a couple before that one, maybe a couple after that one
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RoachForLife:
bdithug

It doesnt turn on the screen for texts. Honestly I dont think its related to texts only. IE if I got my gmail (red) then I got a facebook notification (blue) I believe it would still be red. Perhaps this is normal for CM10 or even android for that matter? Would be nice to have options to display first notification, display newest notification, or display all (ie alternating colors)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Urinophoria:
I wouldnt be horribly surprised. takes time to do all the wiping and flashing, so for all I know the DPI may have reset while I was doing all that. I never really bothered to run it down to an underlying cause; I just accepted that after I did it the DPI was fixed, and it was more trouble than it was worth (for me) to monkey with it :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
AOKP has the same issue, which is sourced (to some extent) from AOSP/CM. If it works in AOSP then don't you think it would be rather easy to compare source and migrate working fix in to CM/AOKP? That being said, I actually think you may be wrong and that the issue may also exist in AOSP. Of course, I'm just speculating here. I'll know more once my development & build environment is created...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mt3g:
12-26 is the correct date for the last time BT was working. Link your self to the latest nightly then copy and paste the date and build name, change the date from what ever it was to 122612 and you'll find the torrent of a build you want. For example. Latest build name is something like cm-10.1-011613.zip change it to cm-10.1-122612.zip and you can find your desired torrent.

The issue may be fixed soon for aosp by Google, Maybe!!! They know its fudged up with aosp on nexus 7 and confirmed it a wip so we can only hope that this will lead for fixes for aosp all around that have source provided... If I assume and have read correctly.

T-Mobile SGS III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
I think you are correct with that assumption. I think it takes the first notification and displays that color. Doesn't matter if you get different notifications afterwards, the first one appears to stay until the screen goes on.

Your suggestion would be a nice option to have though.

Although I think fixing the bug - where if the screen turns on with a notification, it disappears when the screen times out - is probably more important. At least IMO.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well since we've got some truly brilliant developers here that work specifically with our device, and a TON of members that are more than willing to learn/test/help out in any way to get this fixed... and now that you have confirmed that 12/26 had A2DP working flawlessly on it... maybe with a little code-diving.. we can come about a solution ourselves without Google's "help" :highfive::good: This is something I'm seriously looking into myself, just need a little head-start and guidance for the first bit..

using your trick for getting older nightlies, I was just able to get the torrent file for the 12/26 nightly. I can't download torrents at work, so I'll have to wait until I get home. By this evening provided I don't get pulled I should be able to have a developing environment setup on my MacBook Pro as well..
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
I don't know anything about coding or anything like that and I'm sure the answer is no and I'm sure it's been thought of before but I noticed bluetooth share in Titanium Backup that I could backup. Is there anything from the Dec 26th build that could be stripped out with titanium backup and imported into the new nightlies that would fit it? I'm sure it's a deeper coding issue than that but I thought I would suggest it.

I'm at work and unable to try right now for myself. Just an idea though.