yashsingh1/xdaforums huggingface dataset:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
Same issues with a2dp. Fuzzy skipping and robot voices after a minute or two. Also can't flash kt kernel for some odd reason. Never have I gotten an error trying to flash it, downloaded it again, same thing. All after a dirty flash. Too tired to wipe. Thanks man
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
There's nothing different in this ROM that would prevent any kernel to be flashed.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Maybe because you didn't do a full clean install. I wiped everything, /system, /data, /cache, /dalvik, and even /data/media. FULL wipe. only thing i left was my external SD Card. I'm going to my car to get my bluetooth headset right now to try this. I'm pretty interested in this bluetooth as I've been considering getting a stereo for my vehicle that supports A2DP and have been holding off until 4.2.1 ROMs get this sorted out.. will report back soon. unless I fall asleep before I get out of bed ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ballgum:
I just updated. Tried to test Bluetooth by making a regular phone call after bootup, and Bluetooth connected to my phone but said "no call" even when I was on the call. I could only hear and talk through phone itself. I tried to restart Bluetooth service, but am getting problem now where " Bluetooth turning off" and won't change until I reboot phone. I haven't tested with music yet.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Why can't I just update it without it creating a subdirectory /0 folder and saying things like "keyboard aosp crashed" every time? Anybody know? Really sorry if this has been asked before. Glad you released another update Task! Thanks!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mbc663:
The kernel flashed from my external, but wouldn't from internal. Not complaining, just stating
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
Well try Wiping system, cache, and dalvik-cache. Then installing the ROM and Gapps again. That will retain all of your apps and data, but put new OS files back on the phone. Kind of like installing a fresh install of Windows onto a PC, but having all of your personal info and files backed up on a flash drive attached to the computer. make sense? good. :good:

I ALWAYS do a clean flash off a full wipe for every update to ensure that I dont see thes problems you listed. And the point of it is, I NEVER see these errors that people are reporting.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Not ROM related. Roms don't flash anything. Recoveries do. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Thank you very much, giving this a go as we speak. Woohoo thanks! It worked.

Using CWM Touch Recovery juts wiped System, Cache, and Dalvik Cache. Thanks, I think the problem was that I didn't realize I had to format "system".
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
I may be the last one here to notice this guys but if you flash Ktoonsez's kernel you can check the lock frequencies box within general settings and it fixed game lag for me so far. And @ task, great update as usual. Again, thanks. Night guys!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Bluetooth seems to be fixed :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] guitarofozz:
No
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
Task, thanks for being the first to try n' fix Bluetooth... but unfortunately it remains busted. I did get a new pair of earphones and not missing it so much right now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nappent:
And how long did you listen to music via bluetooth?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] issam1979:
Bluetooth still same with robot issue, now even freezes when i turn it off. And Playerpro now ONLY freezes when i try to play music with bluetooth on and paired.

Set from my SAMSUNG-SGH-I747 using xda app-developers app
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] KorGuy123:
Everything works great that I need. I honestly don't know when you get to sleep. Great job, thank you!
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Aaron78:
Task and others, I think a dirty flash is a no go on the 1/15 release. I dirty flashed it with wiping cache and dalvik and kept keep systemUI FCs on reboot. Rebooted into recovery and wipe system, plus cache and reflashed rom+gapps and same issue. Went back to 1/13 release.

(And yes, I read the OP about not posting issues without a full wipe, but I am not prepared to do that this morning.)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] justin860:
Sucks for you dude, works great for me :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nkawal:
Same here. I did a dirty flash and no issues so far. I could care less about Bluetooth. :)

Sent from my GS3 running the latest AOKP by Task650.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] LoneFlac:
Forgot to wipe system.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] sdlopez83:
Used bluetoooth with mxplayer for 5 mins duck dynasty played fine. Will try again soon.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Zehlek:
I just dirt y flashed from 1/13 to 1/15 and it works perfect. Thanks for the update task
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] dlbjmb35:
Dirty flash...runs like a charm. :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] xzil3d:
Dial *#*#4636#*#* and modify the value in: Phone information -> Set preferred network type -> WCDMA preferred
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
And why are you posting this here? You went against the installation process that is posted in the OP. Either follow the instructions or expect this to happen. But either way there's no need to be posting it here.

P.S- You're wrong anyways. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
Might be a noob question, but isn't dirty flashing somewhat counterproductive for the discussion? If you're dirty flashing how can you accurately report bugs?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
You are definitely correct. It is very counterproductive and does nothing to help in any way when troubleshooting. :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] diabolik711:
I noticed the Navigation Bar ring targets from the lockscreen do not open and bi pass the lockscreen. After you unlock the application is open but does not take you there from lockscreen.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] cdjaney:
Bluetooth

Hey Task. Saw you asking for feedback...been on and off your ROM quite a bit lately patiently waiting for bluetooth...so flashed over from TW this AM to test. Much of this was probably pointless but here's a fast rundown of what I attempted and results.

Rebooted after initial install and let it settle. Installed Google Play Music, Apollo and doubleTwist for testing. Paired with my Bose BT speaker. Tried several songs on default ROM settings (governor etc). Wasn't awful, but almost no bass...some of that could be slightly tweaked with EQ...but still not that good. Started getting the robot sound and some speeding and slowing.

Changed governor to Performance and scheduler to deadline. Seemed to be less of the robot and other issues, but that came and went still. Still no bass (not that I expected that to change). Tried streaming audio from my Bible app...very few problems...but again...came and went.

I couldn't see any tie to time used, or source used. ie, problems are still there, but MUCH better than it was.

Thank you for your efforts! Really.

Edit: this was from full wipe. Factory reset/cache/dalvik/system and then even format data (TWRP). :thumbup:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] McAwesome:
Testing now will report. :)

Initial result is no bass even using cm jb fix of making a phone call. Also get alien sounds when playing song paused for a bit it went away and didn't have enough time to play for more then a minute after un pause but played fi e just no bass.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnovanova:
I keep coming back to this rom it's solid. I have bluetooth radios in both my cars so I use it a lot. It's the only thing that needs fixing as far as I could tell but the rom is so sweet I'll just use my auxiliary plug for now. I don't know how long I'll last since I hate having wires everywhere but the rom sure is worth it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
Don't use Bluetooth but will try in my dad's car. But the Rom is flaw less must say you put touch j@zzz to shame can not go back. Will report back with my findings on the Bluetooth.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
This is ridiculous. I've seen this too many times in the thread. Just because you guys say "Sorry for breaking the rules..." doesn't make it cool to post things that don't belong. Please take this question elsewhere. There is a whole Q & A forum for you guys to start threads to ask these types of questions. Please do so. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
Your right if I do every one else would. :understand:sorry will get back to you on Bluetooth testing waiting for download of 1/15 update.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Medlock87:
I was experiencing UI crashes after a dirty flash, too but that's what nandroid backups are for. After a wipe, no issues obviously. Wish I could test bluetooth. I've been contemplating getting a new stereo for my car to make things easier but for now I use an auxiliary cable..I'll just wait until the issues are reported fixed. Great work as always Task! Some of my next paycheck will be going your way in a week! :highfive:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thacounty:
This reminds me of Talladega Nights - "With all do respect that ain't worth a velvet painting of a whale and a dolphin gettin it on." "Just because you say with all do respect doesn't mean you can say whatever you want!" "It sure the heck does, it's in the Geneva Convention!"

Just having some fun. As usual, great release. The fact that you are working on bluetooth when you don't even use it shows that you do care about the users.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
wurd
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Kostazu:
Task,

It's probably been done, but a little rule 6 love for ya, keep up the good work. :)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mikecantreed:
I've been getting wakelocks from Chronus even though I'm not using that widget anywhere. Nothing significant but its there.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] remydlc:
Tried the new update, and BT dont work. just reporting as requested. Bass is gone, and after few seconds, got the robot/distorted audio.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
If you don't use it just freeze it with titanium backup. That should stop it from trying to update. Those wake locks are probably just from that app trying to update the weather or calander events.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
For someone who cares nothing about Bluetooth (you), I want to say thankyou for caring that I do. Hope is a good thing to have for others!

I guess it is easier to deal with the masses with a rod even when you have a big heart...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
you're welcome. and yes it is. if i didn't then things would be a complete mess here. i've learned this from my prior threads. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] geoldr:
Yeah Task honestly you're awesome. Thanks for trying to fix bluetooth for us.

Also, maybe it's a good idea for us who test bluetooth to also post which music player we are using to listen to music. Maybe that has something to do with it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] e-thug:
A2DP boondoggle

task, will you switch to 4.2.2 once it becomes available? I'm holding out on stock rooted until A2DP works. It sucks! But 4.2.1 will be dead in the water once the new source hits developers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] notmilk:
Reporting back on Bluetooth problem

Just tested 1/15 build, Bluetooth still giving a lot of static noise after streaming music for a few mins, like everyone said no bass whatsoever.

but Task, your effort on fixing the Bluetooth problem is much appreciated. Other than the Bluetooth issue, the ROM is nearly perfect.

I keep going back to the 12/23 Build, the Bluetooth on that one is perfect. hopefully it gets all resolved soon. thanks again for your work bro.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
4.2.2 has nothing to do with fixing A2DP for this device. Still unsure where you guys are getting this info. And no. I will never update to 4.2.2. :eek:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
Regarding Bluetooth.

Clean Install. Couldn't connect to new device (NO AVAILABLE DEVICES). Then Bluetooth wouldn't shut off.

Logcat attached, if interested.

No other issues. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] theadb:
I had the same issue when updating to last release. I rebooted and Bluetooth started to work fine after that. I haven't used it for streaming audio in a while, but I use it for phone calls with Ford Sync and all seems well.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
They are obviously referring to this AndroidPolice post. Whether or not you hold them in high regard as a trustworthy news source is a different subject.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Yes. I know what they are referring to. But that's for the nexus 7. Our device is unrelated to that and the A2DP fixes that need to happen are not upstream from Google. They need to be fixed on our side. 4.2.2 will not fix A2DP for us is what I'm saying. We need to fix it.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maDIEmG:
Reporting about Bluetooth:

Still gets the robotic voice/speed up on tracks and when trying to turn BT off it freezes the system forcing me to hard reset by pulling the battery. Tried with proplayer,Google music. Also thanks for the support you show we all know BT its your top priority but really appreciate that you do take some time to look into it and that's part of why I stick with it. =)

Edit: had this weird issue with keyboard crashing IFK what was up with that hut its working fine now.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colbynmeghan:
I was listening to Pandora via Bluetooth headset today. Never have it skip nor robotic voice. I did have some static but switched it from high quality to normal did the trick.

Did have the issue with Bluetooth not turning off proprtly , all I did was force stop Bluetooth and it stopped. No system freezing.

I did a fresh install let it settle reboot then ran Bluetooth. Works.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] TBayTom:
Most complaints have to do with speakers, does your headset provide noticeable bass? A headset that plays music sounding like it's playing out of a tin can with no bass normally wouldn't notice much of a difference. (I'm picturing a small bluetooth ear piece on one ear, correct me if I'm wrong)

My car plays the music fine, but it's low volume with no bass.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wolfnumba1:
Not sure if this has been mentioned but I doubt it (and if it has then oh well) I am effected by the Bluetooth issue as well however everyone that is complaining about it should take a look at this article.

http://feedproxy.google.com/~r/AndroidNewsGoogleAndroidForums/~3/R4YUqqZV0BM/
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Bluetooth has worked just fine on 4.2.1. We made changes that broke it. This doesn't apply.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] nonnarb:
Thank you for providing a logcat. If more people were to do logcats for the bluetooth issues, I'm sure it would narrow down things for Task.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] wolfnumba1:
Never had any issues with Bluetooth other than the low bass over A2DP and I use a Bluetooth headset everyday not sure what you broke lol I have flashed every release since I can remember.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jridda10121:
I use Bluetooth very little what I have noticed is that it works just with same reports posted previously robotic noises and couple force closes. also works good for a hour straight I used with little static, is what I noticed. but it's great that you are trying to work on something you don't use.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Umm... yes dude. We are all talking about AD2P. And it has worked perfect on 4.2.1. Changes had to be made and it was broken in the process. So that's what was broke. By us. Not Google.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpride:
by "We", do you mean AOSP, AOKP, CM, etc? Or something (someone) else entirely?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
The world
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] darkconz:
I have been back and forth on 4.1.2 and 4.2.1 because of the Bluetooth issue. I like to report something on bluetooth issue. As of 1/15 ROM (I tried twice and both times they were clean flashes), turning off bluetooth while in the car and connected to my car's BT then turning it back on will freeze my phone. Either I have to do a battery pull or hold the power button for 20 seconds to turn off. However, while still in the car, turning the phone back on still freezes the phone because bluetooth is trying to connect.

Another thing I noticed is when streaming music in my car via BT, in 4.1.2 I can see the title and album names on my car's dashboard. This hasn't been the case ever since initial release of 4.2.1 for me. The dashboard always display "Audio Streaming". I can however change tracks via buttons on my car. I use Poweramp for audio playback.

I guess one thing that 4.2.1 fixed for me was while streaming music in my car, the screen can finally time out and go to sleep. In 4.1.2 I have to use the power button to turn off the screen if ANYTHING caused the screen to come on.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] colbynmeghan:
I have some bass and it is a Motorola s10hd. It goes on both ears its not a mono headset
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] maDIEmG:
I'll try and see if my older bluetooth headphones work, I tried it in my car and a newer pear of bluetooth headsets I use at work.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mrnovanova:
Sorry about that. I guess my phone just had a brain fart.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I thought you were a bot that cracked in here or something for a minute. Just didn't want 10 pages of the same post over and over and over. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] manny05:
Is anyone else having msm_otg wake lock. I can't seem to get rid of it lol did a fresh install twice and it's still there :(

sent from my GALAXY SIII
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ViciousLSD:
No issues here...
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] rani9990:
Touchwiz is amazing. SIKE! That's the wrong ROM. (SupaHotFire reference)

Great job task. I can't believe that this thing is running so smooth. It's unbelievable. I believe your sleeping hours are approximately 0 hours, what with juggling this ROM and your real life. Thanks so much.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpom1983:
Bluetooth didn't work for me.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Join the club with the rest of the same reports. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
Bluetooth is working for me. If it was something specific that wasnt working my bad fir the post but I had success in sending an apk over Bluetooth to a skyrocket.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
bluetooth has always worked fine for me. its the steaming aspect of it that isn't i guess.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] jpom1983:
yeah, i can send a file, but the music streaming doesn't work. if you catch it quick enough it doesn't freeze up.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Gandalf:
A2DP will be working soon enough. Trust me. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] markjo:
Bluetooth worked PERFECTLY for me in the car today, tied to my Pioneer head unit. Drove for 40 minutes playing music the whole time and it was flawless! I was genuinely surprised and very pleased.. but then a soon as I pulled into my parking space, it started sounding like a Transformer being murdered.. damnit.

Task whatever you did to the code, copy and paste it a million times so Bluetooth will work longer. right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Tankshell:
Anyone having trouble receiving pictures?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
No. Just search the last couple pages since the latest release and you would notice that no one is reporting it. Unless they are on a Canadian carrier.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] bdithug:
Just curious why mms would not work for Canadian carriers only?

Also curious as to if the notification light works the same way as cm10.1. If you receive a text msg which makes your screen turn on, does the notification light stay on once the screen times out?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I have no clue why canadian users would have problems. I make this for AT&T so that could be the reason. No this rom doesn't handle notification lights like cm10.1.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Who's available to test a build with some more bluetooth changes and can flash and respond really fast? Do not pm me. just post here and i'll send a link via pm. I want someone who can actually flash, test bluetooth streaming, and report back asap. Thanks.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
me
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
you're able to test streaming right?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] crewxp:
here
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
I need people who can test this now. So if any of you can't then don't bother posting. I want to try and knock this out asap and i don't have much time until i leave town friday morning.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
you just posted that you weren't in your car?
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] thejust:
I can test

Also MMS works fine here on virgin mobile (bell)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] 1weener:
yes
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] lordmorphous:
I can do it right now
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Check your pm boxes.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] torontomark:
Very happy to help out. I can go and load and test on my car. Easy for me.

Thanks Task for making this happen - I kinda knew that you would get around to this :)

M
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] Bob Simons:
I can test now

ready to install and test
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
Why you no update towers???????????????????? :silly:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
I can test first thing in the morning as soon as I get to my store and stream to my jambox if that will help at all
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Read post above. ;)
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
Check your pm box
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] SeanHacker:
That's next on my list in concurrent with the mythical creatures that will now command the wheel of Rom Control. :D
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] busarov:
I can test.
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] ktoonsez:
FLOAM :D :good:
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] gauthier81:
MMS working fine here on Rogers
[AT&T, Rogers, Bell, Telus Samsung Galaxy S III] mar5hal:
Touché