yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kangi26:
It's 2Chainz's thread not mine
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malaeum:
Kangi, since both of you were ambitious enough to start threads at pretty much the same time, can you edit your OP on the thread you started to point people over to 2chainz's thread? That way we can just focus on the one? Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] PuffinNugz:
Wrong. Questions about CM10 belong in the CM10 Q&A thread. Not in this thread. Period.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] alexgarrett:
And all of this arguing in the thread is also conducive to the development process? Just let the mods clean it up how they will, no need for an entire page of arguing what belongs and what doesn't... just my .02
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] unh1nged:
Solid.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] d.cortez:
3. Yes, it's loud, not max loud. Pushing volume down lowers the volume.

4. Pushing volume up increases the volume to normal levels

FYI, I'm using the 7/20 build, with ROM's kernel and good battery life (not many calls [20 mins], but 3 hours screen time over 12 hr period and still 39% battery left)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
Rearranged
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] iBotPeaches:
I just don't get when I build from source, camera works fine. When I use the posted roms it doesn't.

I'd assume cyanogen has right camera files so I'm literally mind blown.

Sent from my SGS3 AT&T Variant
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TonyStark R.I.P.:
and this statement helps development.... how?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Scottyedmonds:
And that comment just adds to the un- needed garbage. I spend what feels like hours going through shat posts on here of people complaining about other people's posts adding to the piles of shat consuming my time trying to see issues and resolutions. Read the entire thread like you should and you won't add the the shat! Rant over

Here's something useful!

I'm having issues with any audio out besides speaker

Headphones work but don't work within a call, the mic doesn't work in specific.

Also tried to use Jawbone JamBox and wouldn't transmit audio via blue tooth to it. Haven't seen either of these issues discussed here.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] answer1o1:
I've been using this rom for the past 24hrs+. I installed the camera fix and Google Now mod and it's been running near perfect. Everything is smooth and fast. Battery life is great. I had 49% battery on 15hrs+. Only once in a while an app will FC, but a simple reboot will fix it. No biggie. Favorite rom so far and I've tried all the roms available. Looking forward to future updates. I just miss flash player lol.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gomisensei:
Some are having the headphone mic problem for call audio, some say they aren't.

a2dp is a known issue (see OP) tho for me, bluetooth works for call audio, but not music audio. Bluetooth also works for remote control; I can use the fwd/back/pause/play key's on my headset, but the sound comes thru the handset speaker.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dstruct2k:
Call audio through bluetooth uses the headset protocol (2-way mono audio, with 1-way data link), which is working fine, but media playback uses A2DP (1-way multi-channel audio, with 2-way data link) which, as mentioned previously, is incorrectly routed to the device speaker. The data link of A2DP works fine, which is why song titles will appear on the other device and you are able to use the other device to control the media playback.

Wired headset seems to work fine for me using the headset that came with the SGS3. I have confirmed that it is not the device microphone picking up voice by simply covering both the headset microphone and the phone microphone alternately while making a voice recording. The headset works properly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] los0325:
Search the thread I found a flash player apk and I watched the Ufc fight last night on this phone with this ROM using stock browser
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] malaeum:
First of all there are lots of posts on here *****ing about the lack of being on topic. I agree, but I won't waste a dedicated post as it adds to the mess. I thank those who care, but at the same time, please ask yourself "is this going to help this thread overall?" There are plenty of people who post garbage without reading a damn thing so your post doesn't actually help all that much. (See los3025's post for an example of someone who clearly doesn't understand the point of this thread, nor would he ever try to).

Steve (Cyanogen) has fixed the camera issue, he just forgot to correctly apply the fix in the last build. I'd guess he updated the source (after building 7/20) before he left town for the weekend and thats why you're seeing this behavior. Its fixed in the T-Mo variant according to the man himself.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] T3hBraveBoss:
when I try to install the rom in cwm, I get status 7 installation aboorted
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sNoxious:
I'm not having any problems or anything, I would just like to ask a question. Can I update TWRP to 2.4.1.0 using GooManager or is it only through flashing .tar?

Sent from my Samsung Galaxy S III
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
You can do either, but using GooManager is MUCH simpler and doesn't require any work on the user's end.

@Capt

- Which carrier are you on?

try using the following and creating a new APN ->

Name: ATT Phone
APN: phone
Proxy: Not Set
Port: Not Set
Username: Not Set
Password: Not Set
Server: Not Set
MMSC: http://mmsc.mobile.att.net
MMS Proxy: proxy.mobile.att.net
MMS Port: 80
MCC: 310
MNC: 410
Authentication Type: None
APN Type: default,mms,supl
APN Protocol: IPv4
APN Roaming Protocol: IPv4
Bearer: Unspecified

Once you've entered the information, make sure you press the menu button, and then SAVE , or you'll have to do it over again.

Apply the APN by clicking the button to the right of it, then put the phone into airplane mode until you see the airplane mode icon in the status bar. once you do, take it out of airplane mode and reboot. let me know how the signal looks upon the reboot with the new APN
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Latest modem, lk3. I don't use titanium backup so no, I don't restore anything. I'm not tethering, nor using BT audio, car dock or anything like that.

---------- Post added at 04:51 PM ---------- Previous post was at 04:39 PM ----------

I'm on AT&T and I'm already using those APN settings. They are the default settings. When I restart the phone, the signal strength stays at full bars for a minute or two but then it goes back to 0. Since the only way to get it back to full bars is to make a call, I'm guessing it's a glitch within CM10.1 or something like that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] howtomen:
Try a different modem.

trolol and awayyy!! Expect typos this is my phone.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
Did you restore to defaults in the APN settings?

Sent from my Samsung Galaxy S-BEAST!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I have tried all of them. It's not the modem because the signal connectivity works fine on stable cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
I haven't had a chance to do the report yet. I am not getting the problem you detailed, I only use Google Music on my phone (apollo and poweramp if needing to test). I can't report what I can't reproduce :(
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nyamoV2:
Quiet hours set wrong? I know mine was
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
No quiet hours are set.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] HAVOK83:
I was having issues with network also but after creating a new APN with info provided my signal has been holding great and NO drops to 0/no service. The APN that was provided is NOT default because I had reset mine to default and compared them and they are slightly different. Whoever is still having issues try the APN. Thanks for posting APN!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I tried his APN settings and no luck. :mad:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Actually it reminds me of back in November when there were a bunch of problems on AT&T with connectivity. Some folks did not see it and for a while the ones that did were roasted. It sounds like Capt has a more advanced form of whatever was going on then.

Sorry dude... if another ROM works for you, I'd switch for now. And yoou ought to make a bug report to CM.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I just don't understand why it happens only on cm10.1 and not on stock or stable cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] draino623:
I've had this problem on both cm 10.1 and aokp. I "reset to default" in the APN settings and it fixes it every time. Don't know what else to tell you. We need to get back OT. If you continue to have the same problem flash stock and start over. :)

Sent from my Samsung Galaxy S-BEAST!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Did a bluetooth bug report, https://jira.cyanogenmod.org/browse/CYAN-291

Please vote for attention
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] vln004:
Latest cyan + latest leankernal has working encrypted wifi tethering.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
That is the "new" APN that AT&T will be using across the board to phase out the older WAP and PTA since they don't work with some SIM cards
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
Statements like this are why you get some backlash... I haven't been doing this long myself, but when you say things like this to people who know more than you and I both together, its gets them angry haha...

Just because a modem pack works fine in cm10 does not mean it will work fine in cm10.1, this is where you have to expand the idea about your problem. If you don't understand this, its going to be kind of hard to help fix your issue.

Dont assume, and try what people suggest, regardless of you thinking you KNOW what it is, I can guarantee we don't always know what we think...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] araemo:
How does it sound to you? For me, it sounds... not right, but I couldn't describe it well. Kyle thinks there's a low-pass filter being applied somewhere in the audio chain, and he's working on tracking it down.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gtridr:
That really is odd, as normally VoIP apps and the like (Visual Voicemail, Skype, Google Voice, etc.) cannot access the ear piece, for example i cannot listen to my voicemail through the earpiece, it plays through the speaker.

Rather odd to see the opposite. i'll try and get some logs up for this issue.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] GEnx320:
I can confirm this. Set up an encrypted network and both my laptop and tablet connected and internet worked fine. The only issue (and as far as I know it may be specific to Canadian carriers as it's happened since 4.1) is that I can only get it to work on HSPA+, it won't work with LTE, but hey, at least it works! Any more Canadians seeing this?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] JDM STi:
You are correct on this one, at least for Rogers customers. Since 4.1, I could no longer get WiFi tethering working with LTE enabled doesn't matter on secured network or OPEN.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] kingpongg:
I get a lot of... feedback maybe? Some subtle heading and popping that sometimes isn't so subtle. Beyond that it sounds about the same as the 3.5mm aux.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] axiomjunglist:
I'm curious how this works. Carriers use all sorts of tricks to see if you are legally tethering. Without getting into the politics, I'm just curious if this allows for more discreet tethering. Anybody know?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TKG26:
Finally decided to root my GS3... First flash CM10 nightly... so far so smooth... :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dennka:
Does anybody know how to fix call id issue? it comes in symbols.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
Please help make the pain stop!

3 hours. 25% battery gone.

As far as I can recall, I did not use google maps from my office today. So awesome that it's showing up here.

First screenshot shows my battery getting crushed.

Second shows "Google Now" off.

Third shows that yes, applications should in fact be able to use my location. This is one of the most useful things about a smartphone.

Is this an S3 thing? I have an S2 on latest nightly with the same settings and it drains at LESS than one percent per hour while idle.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blasterrr:
I am on M1 Build and my drain is barely 3% an hour on a standby. One of the best battery lives since having the phone on this nightly.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
Closed. You can't report bugs against nightlies. Flash the M1 and post the bug report if it happens on M1. Otherwise wait for M2.

Have a look here. Turning off Google Now does nothing to help with the battery drain. Google Now is actually pretty neat so I just leave it running. What helped for my battery drain issues was to turn off Google location services: that's the Google process that verifies nearby wifi APs to determine your approximate location.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nakedninja42:
Yeah, saw that this morning. I thought of flashing m1 but this has been an issue since the first nightly build released... :eek: If I have time again this week I will redo the report with m1...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bmvik:
I tried searching and it's so weird I can't come up with a hit. CM jelly bean doesn't automatically delete text messages. I set it to auto delete past 500 per thread. It will work for a day max. And then I will see the count rise. What's up with that? I am on the latest stable build.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
I don't know what changed in the latest nightly but the signal is a lot better than what it used to be. The latest nightly has only one fix "Settings: Fix build" but somehow it improved the signal strength. There are a few times that it goes back to 0 but most of the time it stays at full bars now. I told you guys it wasn't the modem, kernel or my phone's fault. I knew the problem was within cm10.1 and I was right.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
I don't know what to tell ya man. Everything we suggested was more so to confirm that it wasn't any of those issues, you know? Sometimes stuff just doesn't agree, I really don't know, I didn't look into that commit at all. But I'm glad its all good for you now!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I'm going to have to tell you that you're wrong. It's a good thing it started working better for you though. Luck is on your side I guess. That "Settings: Fix Build" commit was only a change to the Greek Language. It would not change anything in reference to signal strength. You're more than welcome to look at the commit itself if you like. :D

https://github.com/CyanogenMod/andr...mmit/1b68d29d85f50fe774ec6b912ef274487b3d0945
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] python2121:
I would love to know why LTE toggles don't work months later, but the nightlies are working great.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] zmore:
After only 19 hours of uptime on the 2/11 nightly I ran into the "home&menu button press stuck acting as longpress" bug; usually it takes more than a day for it to show itself (only diff was I was listening to more music via headset than usual). I wanted to try avoiding a reboot this time, but toggling everything under the sun in settings didn't restore functionality, so a reboot it is. (Nothing in useful logcat).

This might be a tough bug to crack, seeing as many of the devs never run a ROM longer than 24 hours anyway. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Something must have changed in the latest nightly somewhere because it fixed the issue I was having. I know the Settings: Fix Build commit didn't fix anything important in the latest nightly but how do you explain how it fixed the problem I was having all this time? Nothing changed this time, I flashed it like a normal ROM and installed all of my apps.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flashedmytiltblind:
I'm still running into this problem as well, though I haven't factory reset'd in a while. I did, however, full reset (factory/cache/davlik) my brothers phone coming from Paranoid Android, and he got the problem within 24 hours as well running the 02/11 nightly. Is there any leads on this issue? It only seems to happen to me once every few days, usually after charging overnight, fwiw.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Fallon:
Just ran into the long press bug myself... probably a day of uptime & now a long press is anything longer than .2 seconds or something. It takes noticeable concentration to tap fast enough to do a short press. 2/9 nightly I believe.

---------- Post added at 08:42 PM ---------- Previous post was at 08:13 PM ----------

Reboot resolved the symptoms for now, but I expect it back tomorrow. I had custom hardware button mappings enabled, but turning them off pre-reboot didn't change things.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LanceM:
You crack me up. I'm done recommending advice for you since your last 2 posts completely prove you haven't heard a word of it.

If you seriously believe that flashing the latest Greek rom fixed your issue, then your in the wrong forum, and nothing anyone is going to say will persuade you differently. You are caught in a case of believing what you want to be believe not what you can prove. Good luck with that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Cusa:
Flashing the "Greek" rom fixed the issue so you can say whatever you want. As I said, nothing changed when I flashed the latest nightly so there must have something different that night have not been posted in the change log?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] RobbieL811:
Nothing was different in that ROM except updated Greek translations! You have already been told. Damn, you are one hard headed SOB! You have argued and argued for the past month w/ the people that have been trying to help you! Thank GOD your problem is fixed so I can quit reading your same argumentative posts over & over!

Sent from my Galaxy S3
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Did you know that things can sometimes "fix"... or break without explanation?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] patthe:
This problem is fix for month now, lol

upgrade your RADIO will fix the problem.

Also its normal if it goes from 3G to LTE, when the internet is not use it will go down to 3G so save battery.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
I'm going with he had some bad downloads and wasn't checking md5 but now that he has a good download, it flashed correctly and now his phone works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gavingreystone@gmail.com:
Delete
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] czechpunk:
It didn't happen right away for me either, but I too am now experiencing this after running the 2/11 nightly for 2 days. I'm also noticing that it's all the buttons, not just the home button, and the trace function on my keyboard doesn't show the path anymore. It still types but is missing that.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] flexfulton:
Oh and don't forget the great screen shots he kept posting that show nothing but a full wifi signal and either a low cell signal or a strong cell signal. Absolutely no valuable information there. It's something we all see from day to day.....a fluctuating cell signal which is why they have the "bars" in the first place.

Haha.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nlz242:
I am on Rogers en encountered the same issue. No WiFi Tethering + LTE. I figured it may have been an hardware (antena) issue as ive read that LTE uses the 2 internal antenas... but i really dont know. I'm currious to know if this works with other providers.

Related to this issue, since i tought it may have been an antena thing, i decided to try USB Thetering instead but never got it to actually work even tho the drivers were properly installed on my windows computer (both 3G and LTE). Is USB Thetering actually functional? (Not complaining that it's not, just wondering, so i dont spend time trying to get it to work, hehe).

All this has been done on 2013-02-10 with KT747 kernel (2013-02-08). Id love to get some form of LTE thetering going, as i will be spending alot of time on business trips in the comming weeks and Hotel WiFi are usually hit-or-miss. But if it is not currently possible, i'll live with it. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bmvik:
Hope someone have seen the same issue
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] fireforhire:
This google voice bug is old and ridiculous. Back to cm10.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] python2121:
Well I appreciate the assistance, but I flashed the latest radios and no dice on my unit. I have never once seen it drop down to 3g from LTE to save battery (though I have, of course, seen it drop from H+ to 3g). Maybe I am flashing the wrong radios or something.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] pmgnet:
What's going on here?

I'm on adb wifi trying to figure out what Google Services is doing to my battery.

Logcat is flooded below with these messages. I'm not connected to bluetooth right now. I used it on the way to work though.

02/12 build. Trying 02/13 next.

D/ ( 1507): bta_jv_rfcomm_stop_server: send BTA_JV_RFCOMM_CLOSE_EVT
E/BluetoothSocket(20260): bindListen, fail to get port number, exception: java.io.IOException: read failed, socket might closed, read ret: -1
D/BluetoothManagerService( 756): checkIfCallerIsForegroundUser: valid=true callingUser=0 foregroundUser=0
W/BluetoothAdapter(20260): getBluetoothService() called with no BluetoothManagerCallback
E/BluetoothServiceJni( 1507): SOCK FLAG = 3 ***********************
D/ ( 1507): bta_jv_free_rfc_listen_cb: max_sess:0
W/bt-btif ( 1507): invalid rfc slot id: 10474
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gberger42:
My phone screen keeps waking up for no reason! It has been eating up all my battery because of this.

I'm running the Feb 07 nightly

Any idea why this happens??
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] loonieryan:
To all those looking for Google Photos/Picasa sync in the Gallery, you can try this GalleryGoogle.apk from the Grouper (Nexus 7) stock ROM. It syncs with Google and the camera still works, as long as you don't try to use Photosphere. Just replace Gallery2.apk in the d2att CM10.1 zip file with GalleryGoogle.apk from the Grouper stock ROM under /system/app before flashing the zip file. There are other ways of course, e.g. RootExplorer, ADB, etc. so have at it. You'll also want to clear data for the Gallery app if you're doing a dirty flash.

I tried the GalleryGoogle.apk for Mako (Nexus 4) from Gapps and that definitely did not work for me.

Edit: actually the GalleryGoogle.apk from the Mako (Nexus 4) stock ROM also works, which is larger in size than the Grouper one. I got the Mako one from the deodexed stock ROM here.

Edit 2: I just tried copying over the liblightcycle.so from the Mako stock ROM into /system/lib and now Photosphere works as well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] blackroseMD1:
So, by pulling GalleryGoogle apk and liblightcycle.so from the stock rom and replacing them in CM10,1, you now have a fully working AOSP camera? That's awesome.