yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] babymatteo:
It all depends on your location too. It may work for me but not you etc...

But yah after doing the buil.prop trick, my Mobile Network Type changed from HSPA: 10 to HSPA+:15

Big difference in data speeds.
[T-Mobile, Samsung Galaxy SIII] id_twin:
Yeah, unfortunately neither build.prop tweaks seem to be affecting my speed one way or another. Chalk this one up for a loss.
[T-Mobile, Samsung Galaxy SIII] jgalan14:
I get requiered missing parameters when trying to upload pictures with tapatalk, but yeah speeds are better for me
[T-Mobile, Samsung Galaxy SIII] Markdental:
Add this anywhere? Also, can it be used in stock?
[T-Mobile, Samsung Galaxy SIII] ge3kswag:
i don't think it's supposed to be a space between.

---------- Post added at 11:06 AM ---------- Previous post was at 11:04 AM ----------

i add it and replace the other values that are already there.
[T-Mobile, Samsung Galaxy SIII] cwalker29:
Please tell how to remove the Google search bar from the home screen. I HATE that

Sent from T mobile galaxy s3 (24mbs down) 4g network
[T-Mobile, Samsung Galaxy SIII] brfield:
I cant get SU to work in adb on latest build. Couldn't on yesterday's either.

Pone pops up with "shell denied Superuser permissions." I can't change it either in the Superuser app
[T-Mobile, Samsung Galaxy SIII] SeanFloyd:
Hey guys,

Only issue I'm having is LED notifications not working right with GOSMS. Tried adding it as an app in the CM led settings but the light turns off after about 5 seconds.
[T-Mobile, Samsung Galaxy SIII] brfield:
Nevermind to my post above, in Development, make sure root is for Apps and ADB
[T-Mobile, Samsung Galaxy SIII] cwalker29:
Anybody?
[T-Mobile, Samsung Galaxy SIII] zer0trip:
Odd issue.

I'm still getting the call echo but I'm getting it in ever JB rom I've tried. On stock I have the same issue until I disable noise suppresion option during a call however I cant seem to find that option in the JB Roms.

Am I missing something?

and yes I've tried turning the volume all the way down but it is still present.
[T-Mobile, Samsung Galaxy SIII] phantommusik:
I got one force close on the Updater and the download for the newest nightly failed the first time but went through just fine on the second.

EDIT: Just discovered that I haven't updated my signature in awhile...
[T-Mobile, Samsung Galaxy SIII] brfield:
It posted twice, sorry. 'Twas an accident.
[T-Mobile, Samsung Galaxy SIII] brfield:
I cannot for the life of me get this rom, or any CM10 based rom to work. I am using CWM Touch.

The phone won't unlock after I wake it up, so it isn't really a sleep of death, because it wakes.

I cannot answer any calls. The UI is horribly laggy.

The kmesg is in a rar because the txt file was too big.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
Thanks! I think i'll flash the 9/15 tonight
[T-Mobile, Samsung Galaxy SIII] sarni84:
Man the latest nightlys have been so smooth. I'm on 9/30 everything works great. To the people having problems wipe and reflash. Because this is where its at!
[T-Mobile, Samsung Galaxy SIII] elesbb:
No its not. Lol. I've been wiping everything and starting fresh. I'm about to take a recording of the failed hold back to kill issue presented in the latest nightly. I am then going to flash back to the 9/15 build as that's the only one which nothing goes wrong with.
[T-Mobile, Samsung Galaxy SIII] ahoslc:
I just want my bluetooth back :(
[T-Mobile, Samsung Galaxy SIII] elesbb:
I want that, plus smart statusbar working, and hold-back-to kill working again.. The part i dont get is how it WAS working perfectly and now its not.

Im not trying to sound selfish or disrespectful in any way. Being a developer myself, (creating programs not ROMs) I cant see how changing something and breaking something else is a progressive maneuver.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
Does anyone have the link to the 9/15 build?
[T-Mobile, Samsung Galaxy SIII] joshnichols189:
10/01 working great over here.

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
and loud audio recording. Its been quiet ever since echo was fixed around 8-29 and echo started around 8-19. So 8-18 is the last one I have. I was on 9-25 and 9-15 but the low audio volume is a killer. You can hardly even hear recorded audio in videos and voice recordings
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
U noticing any issues
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Only the top microphone is being used
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
9/25 has been fine for me. Everything else afterward borked Bluetooth.
[T-Mobile, Samsung Galaxy SIII] sarni84:
Yes it is lol I notice u complain a lot. And u say your a programmer u should know that new features will sometimes break old ones. That's the nature of this ...flashing ROMs. If sh#t ain't working for u then try another ROM. If u say there is bugs submit it! Don't complain in here nothing will get done! 9/30 is fine for me only thing that I notice is recording sound is low. But ain't nothing to ***** about that petty little ****. Everything is awesome. Damn man guess u never ran an ICS ROM on the g2x . Talk about bugs! What we have here is amazing and definitely dd material. Most everything works......be thankful and we are lucky the bugs we have are small
[T-Mobile, Samsung Galaxy SIII] qpinto:
The hold the back key to kill an app has worked for me. I'm on 29 though.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Well for those who dont believe me here is your proof :(
[T-Mobile, Samsung Galaxy SIII] Teo032:
Hey guys, a bit confused. Where are the earlier builds? The link in op has like 9/27 as the earlier builds for cm10. Looking for a build with bt media working correctly. Elesbb mentioned it was before 9/27. is it hidden somewhere on that site lol
[T-Mobile, Samsung Galaxy SIII] elesbb:
Here is the 9/27 build. Its the oldest showing up on cm.get.com. So they might delete them after so long :/
[T-Mobile, Samsung Galaxy SIII] Teo032:
Oh and have you guys tried pulling the audio policy file from earlier builds and pushing it to the new ones? That's what I'm trying to do
[T-Mobile, Samsung Galaxy SIII] pgallard:
I updated every day the new nightly and to be honest i never have any problems with the rom. I believe people get bugs because they don't wait 10 minutes after the new update or installation.
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
why wait 10 mins....I did notice that some things started working a bit after I started.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Where do i begin reporting bugs? Ive posted logcats and everything on this forum only to be *****ed at. I am not complaining, i am simply saying that something isnt working and as a developer you dont continue adding new features and new code when the current code is not working. No i will not use a different ROM for on other devices such as my GS2 and the Nexus things are working perfectly fine in the CM10 build. So its obvious that its something going on with the commits for our devices. And yes, 9/30 is fine for YOU. Doesnt mean the ROM is perfect and flawless and fine for everyone.

I am thankful for what they do, what im not thankful for is how they continue to add code to something that already needs revision. You cannot debug something when you keep throwing in variables and other code. Having the CM updater was pointless when we have a crap load of bugs to begin with. When something isnt working you stop, fix it, then continue on with it. Ever since 9/15 everything has gone downhill, things that were working stopped working, so why did they continue to add to the code when theres stuff that needs to be looked at?

But to say "everything is working great and this build is the best" isnt valid. In order to develop a seemless anything, you have to report issues, even when they are small. I just feel as if they should stop with the nightly builds, go back to code from the 9/15 build, and implement things one by one and in a logical order.
[T-Mobile, Samsung Galaxy SIII] eddylee09:
Can someone please post a mirror to the 09/15 build? I can't find it anywhere and the link that was posted a while back is now dead.
[T-Mobile, Samsung Galaxy SIII] pgallard:
In most others roms development ask to wait 10 minutes after a new installation and reboot right away after the 10 minutes past or you will have problems with the rom.

In my experience with this rom I don't have problems like an other users and the only I can think is the 10 minutes wait and reboot.

If the 10 minutes rule is not important why others development insist we most to wait to avoid problems.
[T-Mobile, Samsung Galaxy SIII] AviatorJud:
I'm completely with you man. I used to post bugs here thinking that MAYBE the developer MIGHT want bug reports and feedback in these threads since he did start the threads himself. Instead the thread is full of moronic and useless responses like "PERFECT ROM!!! NO PROBLEMS WHATSOEVER! CYANOGEN IS GOD!!!!". For some reason I thought this place would be somewhat professional, but for the most part it is full of douchey fanboys who post nothing useful and berate anyone who mentions any problems as being disrespectful to the almighty cyanogen.

For example, a month ago cm10 had MAJOR issues, namely with the actual PHONE..you know, the most important feature of the device? Both myself and a friend who were running the same versions could almost never complete a call without either dropping, or echo, or reboots or some other audio issue. Yet most of the responses here were " A+++ ZERO problems! Cyanogen rulez!". Pretty much indicating most people here are probably children who don't rely on their phone for anything important.

So don't expect your helpful reporting to be appreciated or even heard here..that's basically my point. Just be patient and wait for the next food pellet to be dropped. Whatever you do, don't DARE question Cyanogen's methods or process. You'll get burned as a heretic.

---------- Post added at 05:09 PM ---------- Previous post was at 05:02 PM ----------

And the mods are the real problem. Whenever these issues come up, they just delete all the valid discussion and leave nothing but the "mad props" posts. Very mature. My posts will probably be gone soon.
[T-Mobile, Samsung Galaxy SIII] PENKO956:
been using cm9 to avoid the low volume in record issue in cm10

9/9- has excellent battery life everything seems to work flawlessly

http://get.cm/?device=d2tmo
[T-Mobile, Samsung Galaxy SIII] leyvatron:
You sir shall not be rooted. You need stock and call it a night.
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Is Google now still using the wrong Mic too? it never understands me lol
[T-Mobile, Samsung Galaxy SIII] elesbb:
Give me a sec, i'll upload it then.
[T-Mobile, Samsung Galaxy SIII] elesbb:
Here is the logcat of the hold back to kill not working, and of it working. It doesnt work most of the time.
[T-Mobile, Samsung Galaxy SIII] qpinto:
8/15 is here : http://get.cm/get/3ws

---------- Post added at 06:44 PM ---------- Previous post was at 06:39 PM ----------

then it doesnt work for you. a lot of the bugs and things that you are addressing some of us aren't getting. at this point in time you are an anomoly with a bug. remember these are NIGHTLY RELEASES. they are expected to have a couple bugs here and there.

you are saying 9/15 is the best. i personally have had great success with 9/27. currently on 9/30. it operates the same imo. perhaps you are overlooking something when you are flashing "fresh." here are the steps that i currently use when i want a "fresh start."

usually use TB for messages and contacts. maybe a couple game datas. thats it. let me clarify. just app data. not the whole app.

boot into cwm

data wipe/restore

wipe cache

wipe dalvik

go into mounts and format storage

flash version of cm10

flash gapps

boot

log in and set up my google account

let phone download and restore my phone for 10 minutes over wifi

reboot phone

that usually does it. other than me setting my desktop back to how it was and restoring data to messages and a couple games thats it.

G'Luck
[T-Mobile, Samsung Galaxy SIII] paullu:
Auto brightness still not working?!

I thought it fixed on/30 anyone?
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Yeah. All apps besides phone use the top mic for whatever reason.
[T-Mobile, Samsung Galaxy SIII] GATORZZ28:
CM Updater error

Since flashing the 10-01. I keep getting the CM 10 updater has stopped? Anyone else having this issue?
[T-Mobile, Samsung Galaxy SIII] sarni84:
You have a valid point. I know they have a bug tracker or somewhere u can post log cats. I'm sure with a little searching u will find it. And yes the updater is fc on me now. But again a little bug and nothing that ROM toolbox couldn't delete ;)
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
But they don't want bugs entered in the bug tracker for non stable builds...
[T-Mobile, Samsung Galaxy SIII] rygtuu:
is anyone else having inconsistent wifi issues on the new update?
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
You mean where you have to toggle it off and on for it to connect? I've been having that for a while.
[T-Mobile, Samsung Galaxy SIII] rygtuu:
uhh no like i turn it on and it disconnects and reconnects and disconnects and reconnects when the wifi toggle is on and im like stop trolling me :(
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Nope haven't had that one yet
[T-Mobile, Samsung Galaxy SIII] rygtuu:
oh ok if anyone has, please let me know if there is a fix or something. and i know my problem is different from yours but did you get it fixed or are you still having that problem?
[T-Mobile, Samsung Galaxy SIII] joe98200:
My only "fix" for this was to disable WiFi in settings and re-enable it again. Seemed to do the trick. Otherwise, I forget the connection and resubmit connection details.
[T-Mobile, Samsung Galaxy SIII] janitorjohnson:
I have been reading about all these different bugs that everyone is having right now. Let me tell you real quick that I am not having any of these issues and I dirty flashed 10/1 this morning and still works like a charm. Nothing is force closing whatsoever, wifi works without a hitch. I use google now with no problems. So on and so forth. Everything works. I can't quite explain why it seems to be bug free for me.

...

...

...

Wait now that I think about it I think I may know the solution......

See Screenshot

Liam Neeson has scared all the bugs away.
[T-Mobile, Samsung Galaxy SIII] NYC1992:
I have notice that while on the 9/28 rom.

---------- Post added at 09:14 PM ---------- Previous post was at 09:13 PM ----------

I have noticed that while on the 9/28 rom.
[T-Mobile, Samsung Galaxy SIII] brfield:
What recovery is everyone using? I just went back to stock and am re-rooting in an effort to put an end to my issues.
[T-Mobile, Samsung Galaxy SIII] flipperWhip:
I'm using ClockworkMod

http://www.clockworkmod.com/rommanager
[T-Mobile, Samsung Galaxy SIII] elesbb:
Not to be cocky but I know how to flash a ROM. I've had quite a few devices starting with the tp2 having android on it.

But you have the link with the proof that it's not working.. I don't see how that's only limited to my device. And 9/15 is running perfectly as I can hold back to kill I can use Bluetooth to steam music I can use smart status bar. Those three things do not work in 9/27 and up.

I'm just gonna stop reporting issues and keep 9/15 until a rc or other stable build gets released. Sorry for trying to be productive in reporting my issues which were all supplied with logcats.
[T-Mobile, Samsung Galaxy SIII] brfield:
Which one, Touch or Normal. I had touch, as I like the interface instead of buttons, but I am not sure if that was the cause of the issues.
[T-Mobile, Samsung Galaxy SIII] cwalker29:
Yes sir! Been driving me crazy.. 9/29

Sent from T mobile galaxy s3 (24mbs down) 4g network
[T-Mobile, Samsung Galaxy SIII] omejia466:
So question.. With cm10 there's a pop up when texting for long periods of time. Anyway to disable?
[T-Mobile, Samsung Galaxy SIII] tlytkine:
So far what works for me when updating is wiping the dalvik cache and regular cache, flashing the update over the older nightly, flashing the gapps again and finally wiping the cache & dalvik cache. This gets rid of nearly all issues between updates. If you have already updated without doing this then just wipe the cache & dalvik cache, flash the gapps again and wipe the cache & dalvik cache again.
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
I saw a commit a while back to add an option for this. It said by default its like 30 messages within a 15 minute period or something like that. Guess it never got merged.
[T-Mobile, Samsung Galaxy SIII] omejia466:
So as of right now. No way to disable this?
[T-Mobile, Samsung Galaxy SIII] alanbradshaw:
Stereo Bluetooth

Updated to the latest nightly 10-2 stereo bluetooth still broke. The song info and progress is displayed correctly but the audio is routed to the phones speaker.....
[T-Mobile, Samsung Galaxy SIII] xanderdad:
The CM update server was hauling the mail this morning!
[T-Mobile, Samsung Galaxy SIII] pgjensen:
same here, but there was nothing in the changelog to fix it. i'm sure someone is working on it.
[T-Mobile, Samsung Galaxy SIII] Illusion81:
I do the same, works every time.
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
I just did my first dirty flash todayever on my s3 and it seems fine. Sure is nice but having to do everything over again lol.
[T-Mobile, Samsung Galaxy SIII] BklynB3ast70:
I just did a full clean wipe and when i installed this rom. all i get is 3g and not 4g in Phx.. can anyone assist. when i go back to stock - i get 4g without a problem. thxs
[T-Mobile, Samsung Galaxy SIII] AnthonyAldrete:
They replaced the 4g for H+ icon I believe. I'm getting 4G speeds and I live in Phoenix too :)
[T-Mobile, Samsung Galaxy SIII] street954:
Use speed test to determine data connection speed

CM displays more types of network connection than stock. Probably same connection/network/speed, just displayed differently.

If that isnt the case you can always flash an older radio
[T-Mobile, Samsung Galaxy SIII] volcomguyaz:
+1 for Phoenix... All is good.
[T-Mobile, Samsung Galaxy SIII] bigxie:
I'm fairly certain the stock ROM displays regular UMTS as '4G'. This was a trend with T-Mobile phones I started noticing on the Sensation. AT&T also does this on the iPhone 4S. It's quite disingenuous, but I digress.

Anyways, H+ is the icon that will indicate when you're connected on HSPA+. Keep in mind, that the phone will drop back down to 3G (UMTS) when data is idle.
[T-Mobile, Samsung Galaxy SIII] nicogetz:
I tried this, and also found an old post from 09/05 where someone said that by replacing the /system/lib folder from 09/04 or before, they were able to revert the one mic problem. Although someone was kind enough to upload the lib folder, I don't have a copy of the 09/05 build and I think at this point there have been too many new commits for the old system/lib to work with newer builds (at least for someone of my skill level). For curiosity's sake, does anyone have a copy of an older nightly? (8/25-9/04??).

Edit: found them on goo.im after ~3 minutes of searching.
[T-Mobile, Samsung Galaxy SIII] flipperWhip:
Currently using Touch without issue. I've used Normal in the past with good results. If you think there were issues with Touch give Normal a try... flashing recoveries is quick and easy.
[T-Mobile, Samsung Galaxy SIII] rufolangus:
I still get stuck on edge from time to time. Sometimes i have to recover or reflash to get back on 4g speeds. Anyone know a quick work around to force it to connect at 4g?
[T-Mobile, Samsung Galaxy SIII] stonew5082:
Huh. Tried going into advanced network settings and searching for your provider?

May also need a new SIM card.
[T-Mobile, Samsung Galaxy SIII] oscarwylde:
I haven't seen that, but I do know that sometimes the security algorithm used in wpa2 securities can be a little screwy at times. Could try checking the wireless settings on the router. I had that problem with a brand new laptop before... just food for thought

Edit: sorry, forgot to say specifically AES is where that issue comes into to play in my experience, I always dumb the security down to WPA-PSK for testing as it almost never fails.
[T-Mobile, Samsung Galaxy SIII] elesbb:
I dont think thats ROM related as the device will connect to whichever signal is the strongest.

But you can force 4g by using the toggle option to toggle 2g, 3g, 2g+3g.

Set it to 3g only and it will not connect to 2g
[T-Mobile, Samsung Galaxy SIII] redfin8288:
I dirty flashed 10/1 yesterday and 10/2 today through TWRP Recovery . My signal bounces between HSPA + and 3G at work in Huntsville , AL. Which is the norm for here. I haven't had signal issues flashing any of the Nightly updates. I have also flashed a few different modems and currently running on UVLI8.
[T-Mobile, Samsung Galaxy SIII] URPREY:
Mine stays on 3G until I use data then it ramps up to H+. I wouldn't say it bounces back and forth because it's working as designed.

Sent from my T-Mo SGS3
[T-Mobile, Samsung Galaxy SIII] blink515:
Im having the same issue. I know it's not my router since it is only a month old and none of my other devices are having issues.

I'm using the newest modem available if that may be related. Though I didn't have any problems before.
[T-Mobile, Samsung Galaxy SIII] zxsix:
Those of that need Bluetooth audio stream, there is a simple build.prop edit that fixes it. Can be found in the Verizon d2vzw official cm10 thread.

http://xdaforums.com/showthread.php?p=32270379
[T-Mobile, Samsung Galaxy SIII] eruscool:
this worked for me thanks, i used build prop editor from the market

find

lpa.decode=true

change it to

lpa.decode=false

and enter

lpa.use-stagefright=false

credit to badseed767
[T-Mobile, Samsung Galaxy SIII] aNYthing24:
Cyanogen is looking at the A2DP problem. Should be fixed soon.
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
Is this for the streaming audio

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] eruscool:
yes it fixes the issue with streaming audio through bluetooth.
[T-Mobile, Samsung Galaxy SIII] george241312:
The 10/01 nightly had music problems fc fc when playing music and was really slow to get to the new track ...

The 10/02 nightly played music fast but glichy .. for some reason it repeats songs like 3times after it just played ... its like they put a new sound engine that sucks but tgx for your hard work cyanmd :)
[T-Mobile, Samsung Galaxy SIII] Trev420:
Did anyone use the Google wallet fix? The one where u change the prop to nexus then switch back?

There are warnings about flashing without wiping the data within the app. Is this necessary for cm10? If u flash a nightly update without wiping data do u need to wipe wallet settings?

I'm okay with wiping settings first, but do I need to change build prop again and register a card?

Also, I've noticed that I can't connect my phone as a media device to my media receiver anymore. I don't remember it being an issue with GB or ICS.

Any insight would be great. Thanks!
[T-Mobile, Samsung Galaxy SIII] RonDigital828:
I used the zip file fix and it works but in gotta load it everytime u upgrade

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] Trev420:
Can u just log into ur wallet account and cards are back? Or do u have to change build prop?
[T-Mobile, Samsung Galaxy SIII] skewty:
Does the GPS compass work? I had GPS issues in later builds. Also, can you post a download link for 9/15? I can't seem to find it anywhere, anymore.

Thanks,

Scott
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Are you guys able to install wallet from the market or does it have to be side loaded? I get the incompatible app bs in the market
[T-Mobile, Samsung Galaxy SIII] thenikeman:
http://goo.im/devs/cm/d2tmo/nightly
[T-Mobile, Samsung Galaxy SIII] danieljordanmaddux:
Download goo manager from the market and you can download builds all the way back to 8-18
[T-Mobile, Samsung Galaxy SIII] Trev420:
side loader. i would assume if u changed ur build prop to nexus u can download it from the market, id rather use the custom apk tho.