yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] skewty:
Had to leave CM10.1 for a while.

Bluetooth too unreliable for my requirements and voice calls don't always work (other side can't hear me). Also while on a call sometimes I can't get the screen to stay on..it basically can't decide if it should be on or off (Prox sensor issue?).

I am enjoying the a2dp Bluetooth of this TW ROM. Eagerly awaiting CM 10.2 stable.

Sent from my WIND T999v.
[T-Mobile, Samsung Galaxy SIII] EXV:
Has anyone had issues regarding the native email app? Whenever I set it up with Yahoo, I will get several notifications saying it can't log in. However later on during the day it will pull a few emails as if I had no log in failures.

From my SGH-T999 S3 running Rootbox and BMS Kernel
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
+1

I get this constantly. Tried setting it up every way possible. Some days are worse than others. I posted this a few pages back but I don't think anyone responded. If I find something 'll post it here. Nothing yet.
[T-Mobile, Samsung Galaxy SIII] savir90:
Hey guys

Stable release is awesome...one huge problem...idk if the cm team overlooked this, or else but,

-1.DSP MANAGER is a huge mess...the tabs assigned to said audio channels don't match...for example to adjust Bluetooth audio channel you've gotta use the "speaker audio" channel eq, same with the headphone channel...over all its very irrational

-2.Increasing the decibel value In the eq for any specific frequency will result in audio clipping/distortion in said freq range...this is due to having a fixed preamp gain value on the entire band which is simply set too high pre-Eq, as a result, there is no room left in the audio band to make adjustments...

The rule is, at 0db the audio band is simply maxed out with no room for adjustment...anything over 0db and all you're doing is simply overloading the band which results in distortion/clipping...the higher you go over 0dbs the heavier the distortion will get....it looks like the preamp gain is set at 0db by default with no way of changing it, this means its already maxed out before it goes thru the eq prossesing.

The preamp gain for the entire band seems to be set at 0db by default with no way of changing it, so let's say you want to increase the bass range (example 30hz) by +6db..you will get heavy distortion/clipping because at this point the overall band gain will be 6db's over the max

DSP manager is able to increase any frequency by 12 db, ideally you would need to lower the entire band by 12db...this gives you 12db's to work with, without exceeding 0db which is the breaking point for distortion/clipping....so the correct set up for this to work without any distortion what so ever is the following, the fixed preamp for the entire band should be set at -12db, at this setting it would be impossible for DSP manager to over exceed 0db, anything over 0db will result in distortion, which in this case is the problem....you want to be able to tune a band, not overloaded as DSP is currently doing...

In conclusion, all we need to do is lower the preamp gain value to -12db before it goes thru the audio processing, does anyone know where in the libs can I find this value?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Use fauxsound with a custom kernel. Dsp still a little wonky but it's better.
[T-Mobile, Samsung Galaxy SIII] savir90:
I forgot to mention I'm on 10.1 stable, clean flash, stock kernel, stock everything..

I'm gonna start messing with lib files...any help would be awsome
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Fine if you don't want fauxsound try this http://xdaforums.com/showthread.php?p=38983349
[T-Mobile, Samsung Galaxy SIII] Just_K:
Assert FAILED HELP cm10.1

Cm10.1 status error 7 !!!

1. I checked md5 ...it matched

2. Was using CWM then switched to TWRP

3. I edited the script.txt , edited the "arrests", compressed and was NOT found on my SD/internal Card.

I am doing a clean flash every time. Running = s3 tmobile, cm10.0

"Assert FAILED"

Edit: got it to work ... Updated firmware mnasledov
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Has Anyone had problems wit the Lock screen music widget not updating until the device is unlocked
[T-Mobile, Samsung Galaxy SIII] Just_K:
MMS Problem CM10.1

Running CM10.1 Tmobile..... MMS Problem

I can only send mms from the from the front facing camera.

I can receive mms.

I get an error when trying to send picture from the back camera... "service not activated on network"

EDIT... This only happens when you change the back camera setting to "SUPER"
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Posted several pages back
[T-Mobile, Samsung Galaxy SIII] duhitsrandy:
tried a battery pull with nothing coming of it.. flashed all the way back to the experimental from march and everything is working fine again. dont really know where the problem is in between that build and now
[T-Mobile, Samsung Galaxy SIII] pappuhathi:
Anyone having issues with Google+ in the nightlies of 8th and 9th July? It keeps force closing for me.
[T-Mobile, Samsung Galaxy SIII] timosuomi:
No issue here on the 7/9 nightly.

Sent while playing on my phone.
[T-Mobile, Samsung Galaxy SIII] rage913:
There was a recent update in the Play Store. Have you downloaded it? Of not try clearing out your cache in the manage apps.
[T-Mobile, Samsung Galaxy SIII] jermaine151:
I have this same issue and I believe I know why it happens. Yahoo mail has blocked the T-Mobile IP addresses from accessing their servers on IMAP. When you get the login failed errors, you're probably on 4G. When you're on WiFi, you're not coming from T-Mobile IP address and it logs in and gets the mail. I have no idea why they would do that. No one wants to use their Mail app just for Yahoo mail.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
That makes sense. I'll have to pay closer attention when I get the error again. I personally like the native Email app and use it for exchange also. I don't like T-Mobile. Does that mean it can't be set up using POP either? Thanks for the info.
[T-Mobile, Samsung Galaxy SIII] ce_rob:
while i'm still on 10.1 stable, i've noticed a drop in data speeds and reception since mid-may - around the time i was required to update my firmware (possibly related?). i've seen other people mention similar issues, but have never seen anyone reply with a fix. where i USED to get full reception/bars, i get a fraction/one bar - with edge and H+/3G constantly dancing. hell, as i'm typing this from my office, i see NO bars/NO reception where i used to get at least half. i've tried two radios/modems with almost the same results.

does ANYONE have any ideas? i'm tempted to start testing other ROMS, touchwiz based included, as i simply cannot deal with these reception issues. :(

HELP!
[T-Mobile, Samsung Galaxy SIII] Halotron:
I've had the same problem occasionally, but I'm now quite certain it's TMO's fault. They've been doing maintenance and upgrades all over the country since about that time. Friends of mine with TMO and stock ROMs have been having the same issue.
[T-Mobile, Samsung Galaxy SIII] ce_rob:
it's quite the opposite with me, oddly enough. GF has tmobile as well and ALWAYS has great reception where i don't. i mean seriously, if they're doing maintenance or upgrading, they're doing a piss-poor job at it. EVERYWHERE i go, i've got spotty reception and less-than-stellar data speeds.
[T-Mobile, Samsung Galaxy SIII] hatchback:
I went back to my previous modem. I been getting from 0.42 to 2 Mbps download speeds with this modem T999UVDMD5, where I used to get between 8 to 13 Mbps.

I'm back now to normal after restoring T999UVDLJA modem. I'm using stock TMO rooted touchwiz. Hope this helps!
[T-Mobile, Samsung Galaxy SIII] ce_rob:
awesome, thanks for the reply! i'll give that modem a try :)
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Oh it's definitely T-mobile. Between upgrades and attempting to merge all software and towers with MetroPOS signal is all over the road for me today and yesterday. Some people I know with Metro can't use the stock email app for POP3 emails. None received or sent.

On a side note, I'm about to clean wipe and flash the latest stable! GAME ON! :D
[T-Mobile, Samsung Galaxy SIII] mondokat:
Any chance this is an ssl issue? Usually the mail servers support ssl on an alternate port and certain ISP's block the unencrypted port from the phone/client side. I'd be a little surprised if tmo is blocking non-ssl mail though, it's usually home dsl and cable modems that have those ports blocked.
[T-Mobile, Samsung Galaxy SIII] duhitsrandy:
anyone have any idea what would break my audio between the march experimental build and todays newest build? for some reason every rom ive flashed in between those dates is the same thing, everything is fine for a while.. then no audio in phone calls and when trying to play music the phone starts to freeze when playing/switching songs. whether i do a clean wipe, wipe the cache, try different ways to backup my apps, even just clean wipe and install everything from the play store manually.. it does the same thing. only fix is going back to the march experimental build
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
This is why I quit using AOSP. I refuse to use it until phone calls are reliable again. I prefer CM over TW. But I don't really have a choice right now.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I've never experienced anything like that. Odd. 10.1.1 is solid so far.
[T-Mobile, Samsung Galaxy SIII] timosuomi:
Nor have I. Calls have been dead reliable for me. I haven't really had any real issues in a while, aside from the T-Mobile MMS bug.

Sent while playing on my phone.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It really seems to be a hit or miss problem. I've been on TW for ~10 days now, so maybe it's fixed. There have been times where people were up in arms about X problem, and I couldn't replicate it on my side. Consider yourselves lucky.
[T-Mobile, Samsung Galaxy SIII] mondokat:
ditto

ditto
[T-Mobile, Samsung Galaxy SIII] larva_pro:
Anyone can tell us about 10.1.1 ,Bluetooth, battery?. It Is better than nightly 7/9?
[T-Mobile, Samsung Galaxy SIII] duhitsrandy:
atleast someone knows what im talking about, i reverted all the way back to the march build and everything works fine again. even without flashing the old firmware. thing is it seems like my battery life is better and i dont really notice much difference between it and the newer versions.

but ill be damned if i dont want that 10.1.1 stable to work even though i probably couldnt tell the difference
[T-Mobile, Samsung Galaxy SIII] mdfritz:
Ditto. Had to go to a TW Rom last week cause my "X problem" that no one could replicate was a Google account sync bug that rendered my phone basically useless on aosp.
[T-Mobile, Samsung Galaxy SIII] ajm786:
10.1.1 seems to be a "downgrade" from the latest nightlies. If you read what the CM team posted on their website, it's nothing but 10.1 with the security patches on top of it. You lose things like Privacy Guard and whatever else they might have integrated into the nightlies since 10.1 came out.

So just FYI, the latest available nightly, 7/9, has the security fixes baked in, so you should be good to go. I'd know all this is true because I installed 10.1.1 and found features missing.
[T-Mobile, Samsung Galaxy SIII] timosuomi:
10.1.1 also appears to clear your alarms. Yes I was late for work this morning. ;)

Sent while playing on my phone.
[T-Mobile, Samsung Galaxy SIII] PennStater:
I did a clean install of 10.1.1 yesterday and haven't noticed any issues at all yet. I also downgraded to the UVDLJC baseband (which was probaby more of an upgrade compared to UVDMD5).
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I've been out and about in areas with a better signal than near my home. Since I've installed 10.1.1 (and this probably had nothing to do with it) the native email app seems to be functioning as it should. Not a single Yahoo Mail sign-in error yet (knock on wood).

That, for me, throws out the idea that errors are coming from being on 4G or any other signal I can get.

So basically I'm still clueless as to why this was happening in the first place. All seems well for now but we know how this can play out.

Who knows...it's too intermittent.
[T-Mobile, Samsung Galaxy SIII] ce_rob:
is there a flashable zip that makes it as easy as upgrading from older firmware (like many of us did when it was a requirement)? or does it have to be done via odin?

edit: to downgrade back to UVDLJC, i mean.
[T-Mobile, Samsung Galaxy SIII] PennStater:
All I did was flash the zip from here: http://xdaforums.com/showthread.php?t=1880987
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
The link PennStarter posted is to the basebands (which I think is what you wanted in the first place).

In the event you wanted the LJC firmware it can be downloaded here:

http://xdaforums.com/showthread.php?t=2282603

If you read/scroll down a bit in the OP you can download the LJC firmware here -> https://dl.dropboxusercontent.com/u/173554095/T999%20Devel/T999UVDLJC_firmware.zip
[T-Mobile, Samsung Galaxy SIII] ce_rob:
there we go, that's what i was looking for. i'd be able to revert back to the UVDLJC firmware and still flash current nightlies, correct?
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
As far as I understand, you are correct and I believe that does include the LJC baseband as well but you can use your choice of basebands (there are many out there).
[T-Mobile, Samsung Galaxy SIII] ce_rob:
you, sir, are a gentleman and a scholar.
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
I wouldn't go that far, but thanks and you're welcome! :good:
[T-Mobile, Samsung Galaxy SIII] rage913:
Has anyone run into issues with social media cameras? Google hangouts uses the native camera for capturing pictures but as soon as I do something with instagram or fb my phone crashes and I go into a hard reboot. Haven't run into the issue before but I'm stock 7-6 nightly. Have done the normal clear cache/data and redownloading the apps. Rather annoying. Lol. Been thinking about doing a complete clean install.
[T-Mobile, Samsung Galaxy SIII] tropaios:
Hey, has anyone else lost the ability to sideload apks?

I noticed it on the 0628 nightly, and just upgraded to 10.1.1, and it's the same on both. Despite having unknown sources enabled, when I open an apk in root explorer the installation dialog opens, showing all of the app permissions, but the install button is non functional. It's not greyed out, simply nothing happens when it is tapped, though the cancel button works fine. I've tried it now with several apks I know are good to no avail.

Any ideas?

---------- Post added at 04:40 PM ---------- Previous post was at 04:34 PM ----------

Never mind, I went through and started disabling running apps. It seems Twilight was somehow for some reason putting an overlay over the install button making it impossible to press. Disabling that fixed my problem.
[T-Mobile, Samsung Galaxy SIII] rage913:
Still haven't found a fix for the camera but I think that's just a cm bug. Other users have reported the same thing in a the Q/A for the t999. Also looks like the mms glitch thing is back. Running the 7.9 nightly. Used the mms fix from a while ago but I don't think it took. Man... :banghead:
[T-Mobile, Samsung Galaxy SIII] GinoAMelone:
I was getting weird failures sending SMSs with 7/12. Reverted to 7/9.
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Flashed 10.1.2 no other mods and I seem to have lost privacy guard. Did they move the setting maybe? It no longer pops up in my bar when opening an app either.
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It's not in 10.1.2, that's why you can't find it.
[T-Mobile, Samsung Galaxy SIII] jermaine151:
POP3 should work fine.

I think Yahoo has gotten the message and unblocked Tmo's network. I could re-create this issue over and over, before. Now I'm on 4G and it logs me in fine. This isn't the first time that Yahoo did that. When I had my Droid Incredible, they did the same thing and finally unblocked it. Hopefully it's now working consistently for you guys as well.
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
Does anyone know where I can disable the home button from waking up the phone....seems like it was implemented but I can find it anywhere.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Lockscreen, screen security
[T-Mobile, Samsung Galaxy SIII] Spiyder:
Ahhhh, I missed that it pulled. Dang, I liked it. Sure it will be back soo. Thanks :)
[T-Mobile, Samsung Galaxy SIII] stonew5082:
It's in the nightly from the 12th
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It wasn't pulled, and won't be added any time soon. It's 10.1 stable code with a few security holes patched.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Why can't i Install any RC or Stable releases on the T999L i can only seem to install nightlies
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Since I can read minds, you need to edit the script file to support your device.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
but if the Nightlies install shouldn't the RC and Stable install as well
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
The stable releases use old code. So not necessarily. You can open up the updater script of one that installs and one that doesn't to verify.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
The difference is nightlies support MB7 while stable doesn't. Do what was already suggested. Just extract the zip, remove those asserts all together and be done with it.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
If i remove them all together it just says failed to install
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
It would really help everyone if you would give more information. We are here to help, but can't do anything when you give us no information.

You say that when you removed "them", installation fails. Paste in here what you removed, and what the error message said.
[T-Mobile, Samsung Galaxy SIII] Bray90820:
Thanks for the help but i just figured it out. it turned out that the zip was not signed when i zipped it
[T-Mobile, Samsung Galaxy SIII] moose&beer:
If I switch from AT&T to T-Mobile, and keep my GS3 from AT&T and use it on T-Mobile (after properly unlocking, etc.), will I need to flash the T-Mobile CM ROMs instead of the AT&T ones?
[T-Mobile, Samsung Galaxy SIII] matrixzone:
At&t
[T-Mobile, Samsung Galaxy SIII] moose&beer:
Is that because my device is still an i747 but being used on t-mobile? Or some other reason? Thanks for the help
[T-Mobile, Samsung Galaxy SIII] ziggy46:
that is correct, keep using the at&t roms because the only thing your changing your carrier not the entire device
[T-Mobile, Samsung Galaxy SIII] moose&beer:
Will do! Thanks!
[T-Mobile, Samsung Galaxy SIII] Sixonefour:
So the MMS issue is still in 10.1.2?

I tried to send a 6.03MB picture and it failed (numerous attempts with a good connection). I reduced it down to roughly 350KB and it sent on the first attempt. Does anyone know the size limit?
[T-Mobile, Samsung Galaxy SIII] improperburial:
It seems like the limit is right around1 mb anything under that should send through without issue
[T-Mobile, Samsung Galaxy SIII] yanikd:
VLDMF2

So I updated my canadian SGH-T999V firmware/boot loader from VLDLL1 to the just released VLDMF2 and now CM won't flash unless I edit the updater-script. I'm guessing this will be fixed soon, but just wanted to warn other canadian users.
[T-Mobile, Samsung Galaxy SIII] LuigiBull23:
That's because CM doesn't have support for MF2 just yet as it was just released. Current builds only validate LL1 for your model. Just wait it out and I'm sure future builds will support the firmware and include the bootloader validation but until then, you're only option is to remove those asserts from the script and you should be golden.
[T-Mobile, Samsung Galaxy SIII] GinoAMelone:
I only see a setting for unlock there, not wake.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Yeah I'm dumb sorry
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
I try to change things in sec_keys.kl and that still hasn't worked for me!
[T-Mobile, Samsung Galaxy SIII] Ksunnyv1011:
Is anyone using MD5 baseband and can confirm they have no issues? I want to go back to that since it provided much better data speeds for me.
[T-Mobile, Samsung Galaxy SIII] itzsmokey:
I've never had any problems with the baseband, but the firmware is a different story tho.
[T-Mobile, Samsung Galaxy SIII] corkythetard:
Can you give more info about the issues you're referring to? Kind of hard to paint with a broad brush to answer a question like that when you don't mention any specific "issues," that you have concerns about. I'm on MD5, and for my use I have zero issues.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Anyone else getting video upsidown on streaming apps?
[T-Mobile, Samsung Galaxy SIII] khoikn:
I used MD5 since it first came out and noticed some battery drainage issues.

Switched to LI6 and greatly improved my battery, which sucks because MD5 had more stable/better data speeds for me too.

I suggest you try it out for yourself for a couple days and see what happens.
[T-Mobile, Samsung Galaxy SIII] klin1344:
Oops, didn't mean to thank you lol.

But know, I do not experience that. What apps are causing you issues?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Netflix and xfinity
[T-Mobile, Samsung Galaxy SIII] lextex:
Just updated to 10.1.2 and I'm still getting reboots when I try to use the FFC in Instagram.

Anybody know why this still happens?
[T-Mobile, Samsung Galaxy SIII] corkythetard:
I never use the FFC in Instagram, but I have been on 10.1.2 since it was released(Clean install). Just tried it and got the hot boot. Grabbed a logcat, but am unable to narrow down the error at work. Will post a link to my logcat after work today.
[T-Mobile, Samsung Galaxy SIII] mondokat:
Ha, I just tried it and got a full reboot, not just a force close. Ouch.

On the other hand, in instagram's options there is a section called "advanced options" and under that is a place to choose whether or not to "use instagram's advanced camera". if you uncheck that, when you try to take a picture it asks for a source, and you can choose camera, then it uses the built in CM camera, which can do ff ok. That works. If you try to check that option back on, it warns that the feature doesn't work on all phones and if you have problems, turn it off.

So there you go.

:highfive:
[T-Mobile, Samsung Galaxy SIII] lextex:
Just tried and the CM front-facing-camera forced a reboot as well.
[T-Mobile, Samsung Galaxy SIII] rage913:
Thank you. Lol. Been driving me up a damn wall but w.e. Been odd not having that problem and then it magically appears. Blah. Question, can someone tell me how to run a log cat in stupid terms? I know that I have to have one of the various apps installed but in terms of using it, to actually get a log on something like this? Because this issue relates to all third party apps that don't use the native cm camera. Or better explaining would be social media apps that use its own camera (instagram, fb, and even twitter I believe) hangouts works fine because it's using the native camera but yeah curious.
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
If its causing reboots you need a "last_kmsg". Its located at /proc/last_kmsg. You can either get a root explorer and find it or in terminal emulator you can do:

# cp /proc/last_kmsg/sdcard

To put it on the internal storage or:

# cp /proc/last_kmsg/extSdCard

To put it on you SD card
[T-Mobile, Samsung Galaxy SIII] Derzicom:
My logcat looks like this
[T-Mobile, Samsung Galaxy SIII] rage913:
... I see what you did there :rolleyes:
[T-Mobile, Samsung Galaxy SIII] Danvdh:
I nearly fell off my chair
[T-Mobile, Samsung Galaxy SIII] corkythetard:
This worked like a charm! Much appreciated! :good::highfive:
[T-Mobile, Samsung Galaxy SIII] Vodkanakas:
got 2 questions here

1) I downloaded the latest nightlie to try on my phone again and I can't view any pics or files that are on my phone. its like it all dissappeared but it all still there just can't view it. any ideas on what happened?

2) do I need to install the 10.1.1 and 10.1.2 after the newest nightlie and 20130301 gapps?
[T-Mobile, Samsung Galaxy SIII] lextex:
Ran this command and then tried the FFC in instagram. Got a reboot.