Develop Bugs

Fix for poor A2DP quality on 4.2.2

Just wanted to share this here. There is clear audible decrease in audio quality on 4.2.2 when listening over bluetooth (A2DP). All the higher tones were somehow garbled, like cymbals, or high vocals, etc. I could clearly notice the poor quality on 4.2.2 on my car stereo and also the improvement after installing the fix on my stock rooted GN 4.2.2 (GSM). I haven't tested this on custom ROMs.
Steps:
Root your phone, if not rooted
Make Nandroid backup (in worst case, you might not be able to boot)
Download bluetooth.default.so http://code.google.com/p/android/issues/detail?id=39632#c158 Also attached to this message.
Download audio.a2dp.default.so http://code.google.com/p/android/issues/detail?id=39632#c163 Also attached to this message.
In /system/lib/hw, rename bluetooth.default.so to bluetooth.default.so.bak (or whatever)
In /system/lib/hw, rename audio.a2dp.default.so to audio.a2dp.default.so.bak (or whatever)
Copy files to /system/lib/hw
Set permission on both files to be same as with the original files (644)
Restart phone

Edit: deleted

jpalo said:
Just wanted to share this here. There is clear audible decrease in audio quality on 4.2.2 when listening over bluetooth (A2DP). All the higher tones were somehow garbled, like cymbals, or high vocals, etc. I could clearly notice the poor quality on 4.2.2 on my car stereo and also the improvement after installing the fix on my stock rooted GN 4.2.2 (GSM). I haven't tested this on custom ROMs.
Steps:
Root your phone, if not rooted
Make Nandroid backup (in worst case, you might not be able to boot)
Download bluetooth.default.so http://code.google.com/p/android/issues/detail?id=39632#c158 Also attached to this message.
Download audio.a2dp.default.so http://code.google.com/p/android/issues/detail?id=39632#c163 Also attached to this message.
In /system/lib/hw, rename bluetooth.default.so to bluetooth.default.so.bak (or whatever)
In /system/lib/hw, rename audio.a2dp.default.so to audio.a2dp.default.so.bak (or whatever)
Copy files to /system/lib/hw
Set permission on both files to be same as with the original files (644)
Restart phone
Click to expand...
Click to collapse
hey man !! u made my day !! thanks a lot !!!

manumanfred said:
From CM Team I got reply once for my question about Bluetooth A2DP audio streaming. They said the CM Bluetooth files are not compatible with stock android ROM. So I didn't dare to test the A2DP file but I just downloaded latest night and I took that Bluetooth audio .so file and worked.
Thanks for information that the files worked on your nexus..
Click to expand...
Click to collapse
interesting, what was your question? because i feel like the CM bluetooth quality has gone down too

murso74 said:
interesting, what was your question? because i feel like the CM bluetooth quality has gone down too
Click to expand...
Click to collapse
I asked information about the bluetooth files for A2DP streaming fix..
CM's Bluetooth quality (I mean A2DP streaming quality) is much better than on stock ROM.
I noticed the difference when I tested CM10.1 first Nightly of JB 4.2.2..

Does this help with call quality over standard Bluetooth
Sent from my Galaxy Nexus using xda app-developers app

ok i'm sorry, but just to be clear, doing this on CM10.1 won't do a think correct?

I have been looking for something like this!!! Thank you! What exactly does it do? Does it increase the bitpool of the stream?
FYI, I just noticed that it changed my bluetooth device name to "Nexus 4" which can easily be changed back in the bluetooth settings...

Very, very good fix. thanks

murso74 said:
ok i'm sorry, but just to be clear, doing this on CM10.1 won't do a think correct?
Click to expand...
Click to collapse
Interested in this answer as well. Can anyone clarify please?

Is it possible/likely that in addition to fixing issues with quality, this will also resolve the high-speed playback problem? A few other people and myself have experienced BT audio streaming where it plays back way too fast in the car. So far there doesn't seem to be a qualified fix for it. I'm interested to try this and see what happens - just wanting to see if anyone knew for certain ahead of time.

manumanfred said:
From CM Team I got reply once for my question about Bluetooth A2DP audio streaming. They said the CM Bluetooth files are not compatible with stock android ROM. So I didn't dare to test the A2DP file but I just downloaded latest night and I took that Bluetooth audio .so file and worked.
Thanks for information that the files worked on your nexus..
Click to expand...
Click to collapse
I have tested this fix in a Rooted Stock Nexus 4. So they are compatible with stck ROM. Just FYI.

hitokiri.pr said:
I have tested this fix in a Rooted Stock Nexus 4. So they are compatible with stck ROM. Just FYI.
Click to expand...
Click to collapse
I know it because I have fixed BT quality on my ROM!!
And I have used other files too to fix it..

murso74 said:
ok i'm sorry, but just to be clear, doing this on CM10.1 won't do a think correct?
Click to expand...
Click to collapse
Probably only works on stock. CM should have same/similar fix on some later build, check the Google bug thread at http://code.google.com/p/android/issues/detail?id=39632.

jpalo said:
Probably only works on stock. CM should have same/similar fix on some later build, check the Google bug thread at http://code.google.com/p/android/issues/detail?id=39632.
Click to expand...
Click to collapse
CM10.1 has the A2DP audio straming fix and I'm using some CM10.1 BT files on my ROM..
No sense to add the files to CM10.1 when it's fixed in CM10.1..

manumanfred said:
CM10.1 has the A2DP austio straming fix and I'm using some CM10.1 BT files on my ROM..
No sense to add the files to CM10.1 when it's fixed in CM10.1..
Click to expand...
Click to collapse
Interesting... I noticed the highs in my car seemed raspy a day before these were posted. I guess it was in my head
Sent from my cm_tenderloin using Tapatalk 2

Thanks so much for posting this OP!!! I have been lamenting my purchase of the N4 until this fix. The phone is now perfect! Well aside from no voice search for music like Siri (Google Voice search never pulls up my music).

I finally fixed my Bluetooth in call audio.I switched back to 4.1. This really sucks as I got used to 4.2.2 pull down toggles. I really hope Google gets this straightened out. This fix does help the Bluetooth audio streaming but my work truck and headset are not A2DP and when in call the volume seems to fade in and out. My Subaru has A2DP and made music easy to listen too but in call still seemed bad.
Sent from my Galaxy Nexus using xda app-developers app

Any chance this fix works on non-Nexus hardware? Since moving to a JB phone from one running ICS I have lost two very useful facilities - Llama being able to pick up cell changes without the screen being on and good quality BT audio.

Not sure if this will help anyone else but found doing factory reset fixed most of my 4.2.2 Bluetooth issues. Ota gave me issues. When 4.2.2 Google factory image was released I fastboot flashed it did a factory reset immediately and all seems to work fine but id tags for songs.
Sent from my Galaxy Nexus using xda app-developers app

Liquid Smooth jb v2.1 stable

Live in goo manager. Just thought I'd let you all know!

Just installed. Running smoothly, none of the issues I experienced in RC2 so far. Great work.

RC2 Stabel and Bluetooth audio
&Son said:
Just installed. Running smoothly, none of the issues I experienced in RC2 so far. Great work.
Click to expand...
Click to collapse
Anyone confirmed if the Bluetooth audio distortion on calls via in car systems has been fixed in this release?

mm0wkj said:
Anyone confirmed if the Bluetooth audio distortion on calls via in car systems has been fixed in this release?
Click to expand...
Click to collapse
Its a stable version so it should work. I can't answer because I hate BT lol But give it a shot. I'm also using the latest AK CYLON kernel. His work is usually flawless
Sent from my Galaxy Nexus using Tapatalk 2

heath2805 said:
Its a stable version so it should work. I can't answer because I hate BT lol But give it a shot. I'm also using the latest AK CYLON kernel. His work is usually flawless
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks Heath. Was a bit reluctant to reflash as I've spent a few days tweaking my RC1 build and have a shed load of apps loaded for my boys to play with..
I may wait until someone posts a positive on hands free before rebuilding again.

I don't use Bluetooth and can't confirm it working, but this ROM is just awesome!
It has all the features you will need and it runs really smooth. I can really recommend it. Only thing not working for me is sphere in camera - not a big deal though...

hudl said:
I don't use Bluetooth and can't confirm it working, but this ROM is just awesome!
It has all the features you will need and it runs really smooth. I can really recommend it. Only thing not working for me is sphere in camera - not a big deal though...
Click to expand...
Click to collapse
I don't have sphere option in mine. Wouldn't that depend on what gapps you used? I used the latest in goo 20130301
Sent from my Galaxy Nexus using Tapatalk 2

heath2805 said:
I don't have sphere option in mine. Wouldn't that depend on what gapps you used? I used the latest in goo 20130301
Click to expand...
Click to collapse
I too use gapps 20130301 from goo and have the sphere option. But when aligning the fist image, the "gallery" closes. I had it working on another ROM, but quality of sphere is really bad when shooting in a room (alignment), so I don't miss it. Maybe/hopefully Google improves it in the next version.
EDIT: Indeed the camera gives me more problems than just a buggy sphere... NO images are taken at all! Not even with a 3rd party camera app!
I think this is a major issue. I read that it should be fixed in Android 4.2.2 but apperently this is not the case. Interestingly I had it working in other 4.2.2 ROMs so maybe there is an issue with this LiquidSmooth release...
Anyone else has troubles with the camera?

hudl said:
I too use gapps 20130301 from goo and have the sphere option. But when aligning the fist image, the "gallery" closes. I had it working on another ROM, but quality of sphere is really bad when shooting in a room (alignment), so I don't miss it. Maybe/hopefully Google improves it in the next version.
EDIT: Indeed the camera gives me more problems than just a buggy sphere... NO images are taken at all! Not even with a 3rd party camera app!
I think this is a major issue. I read that it should be fixed in Android 4.2.2 but apperently this is not the case. Interestingly I had it working in other 4.2.2 ROMs so maybe there is an issue with this LiquidSmooth release...
Anyone else has troubles with the camera?
Click to expand...
Click to collapse
Mine is working just fine. Maybe try and redownload gapps and see if that's the issue. I'm not sure if the new gapps has an effect on camera apk though. If all else fails, you could always redownload the ROM and get a clean install.
Edit: Alright just checked and sphere is working here flawlessly.
Sent from my Galaxy Nexus using Tapatalk 2

BT handsfree still buggy
mm0wkj said:
Thanks Heath. Was a bit reluctant to reflash as I've spent a few days tweaking my RC1 build and have a shed load of apps loaded for my boys to play with..
I may wait until someone posts a positive on hands free before rebuilding again.
Click to expand...
Click to collapse
Bit the bullet and went for the update and tried Bluetooth handsfree. Still not working.:crying:
Connects fine, transfers contacts fine but audio during calls (at any volume level) is distorted and robotic (both ways). Even when connected there is intermittent bursts of quiet and distorted audio through the handset speaker which sounds like the connection is trying to drop out. HTC one, Sony Xperia, HTC Cha Cha, HTC Desire all work perfectly on the same car kit.
Tried all devices on a Saab (2008) Ford (2012) and Renault (2011) all the same. Other devices connect and audio is perfect, S3 distorted.
Anyone recommend a Kernel that they have confirmed BT functionality on in car systems?

heath2805 said:
Mine is working just fine. Maybe try and redownload gapps and see if that's the issue. I'm not sure if the new gapps has an effect on camera apk though. If all else fails, you could always redownload the ROM and get a clean install.
Edit: Alright just checked and sphere is working here flawlessly.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Thanks for telling! I always do a full wipe when flashing ROMs but then I realised that other ROMs also had the same problem "suddenly". So I tried it once more with reverting to stock, re-rooting,... and now also deleted my backup of "Android" folder that I otherwise always restore to keep some settings. What should I say? It works again! Smooth and flawless (including sphere)! :victory:
mm0wkj said:
Tried all devices on a Saab (2008) Ford (2012) and Renault (2011) all the same. Other devices connect and audio is perfect, S3 distorted.
Anyone recommend a Kernel that they have confirmed BT functionality on in car systems?
Click to expand...
Click to collapse
Afaik Google implemented its own Bluetooth stack, which obviously is not that great...
"Android 4.2 introduces a new Bluetooth stack optimized for use with Android devices. The new Bluetooth stack developed in collaboration between Google and Broadcom replaces the stack based on BlueZ and provides improved compatibility and reliability."
http://developer.android.com/about/versions/jelly-bean.html
I'm afraid you will have to wait for Android 5 or other fixes... (can be wrong though. I'm not so firm with this matter)

I noticed many people here having BT issues. Not sure if this helps for calling but definitely helps for audio. Check it out.
http://forum.xda-developers.com/showthread.php?p=38973705
Sent from my Galaxy Nexus using Tapatalk 2

Bump for an awesome ROM!!!

Finally a stable release. Wish they had an "official" Galaxy nexus thread though.
Sent via Tapatalk on LiquidSmooth Galaxy Nexus

GherkinSavorus said:
Finally a stable release. Wish they had an "official" Galaxy nexus thread though.
Sent via Tapatalk on LiquidSmooth Galaxy Nexus
Click to expand...
Click to collapse
They had, but it's closed now. Don't know why.
Sent from my Galaxy Nexus using Tapatalk 2

But...
I thought TeamLiquid broke up into CarbonJB. Is Liquid coming back!?

Liquidsmooth jb v2.2 official is up in goo...
Sent from my Galaxy Nexus using Tapatalk 2

Not for toro plus :banghead:
Sent from my Galaxy Nexus using Tapatalk 2

Galaxy S3 and Torque App.

Hey guys I have been having an issue with my S3 running custom rom, Torque app and ELM327 Bluetooth
*First off, my Nexus 7 running Paranoid Android 3.15 is perfect.
I can connect to bluetooth but Torque app does not recognize the device
1) S3 running Task650 Rom doesn't work,
2) I factory reset S3 back to stock running 4.1.2 and WORKS PERFECT.(no root access)
3) Because I dislike touchwiz I decided to run PA 3.15 same as tablet but the same issue.
Is it the phone or custom rom or app?
The app does have one setting for customer rom but doesn't seem to do the trick.
Torque>setting>general preferences>force bluetooth connection type>
3 options: 1) off (default) 2)Force Encrypted Connections 3)Forced Unencrypted Connections
*force bluetooth connection type description
Leave this set to "off" unless you are running a Custom Rom(CM/AOKP/ETC) and are hacing connection problems - it is a workaround for buggy android bluetooth driver and custom rom.
I need your help please.

Contact the developer of the app and let him know of your issue. It's your best bet besides going back to touchwiz.

http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3126.00

CZ Eddie said:
http://torque-bhp.com/forums/?wpforumaction=viewtopic&t=3126.00
Click to expand...
Click to collapse
Thank You CZ Eddie, I guess CM 10.1 is the only Custom Rom that works.
I've tested.

vic_singh said:
Thank You CZ Eddie, I guess CM 10.1 is the only Custom Rom that works.
I've tested.
Click to expand...
Click to collapse
Sorry, I didn't have a keyboard to type with last night so I just copied/pasted the link that I thought would help.
Yeah, AOKP has never worked for me. Some AOSP ROM's work and some don't.
LiquidSmooth was working for me (and is one of my two fave ROM's) for awhile.
But I'm now having trouble getting my cheapo bluetooth ODB sensor to talk. I'm not sure if it's the ROM or the device.
But none worked without some sort of shutdown bug. Which can sometimes be worked around using options in Torque Pro.
Weird thing is, Torque non-Pro always works great.

CZ Eddie said:
Sorry, I didn't have a keyboard to type with last night so I just copied/pasted the link that I thought would help.
Yeah, AOKP has never worked for me. Some AOSP ROM's work and some don't.
LiquidSmooth was working for me (and is one of my two fave ROM's) for awhile.
But I'm now having trouble getting my cheapo bluetooth ODB sensor to talk. I'm not sure if it's the ROM or the device.
But none worked without some sort of shutdown bug. Which can sometimes be worked around using options in Torque Pro.
Weird thing is, Torque non-Pro always works great.
Click to expand...
Click to collapse
I a wild guess to figure out what the problem is. I'm happy with CM.
Man you saved me a lot of time.
Thank you
Sent from my Nexus 7 using Tapatalk HD

CZ Eddie said:
Sorry, I didn't have a keyboard to type with last night so I just copied/pasted the link that I thought would help.
Yeah, AOKP has never worked for me. Some AOSP ROM's work and some don't.
LiquidSmooth was working for me (and is one of my two fave ROM's) for awhile.
But I'm now having trouble getting my cheapo bluetooth ODB sensor to talk. I'm not sure if it's the ROM or the device.
But none worked without some sort of shutdown bug. Which can sometimes be worked around using options in Torque Pro.
Weird thing is, Torque non-Pro always works great.
Click to expand...
Click to collapse
I think it's liquidsmooth... I'm on 2.5 w/ sprint and I can't get it to the OBD sensor..

EvoJok3r said:
I think it's liquidsmooth... I'm on 2.5 w/ sprint and I can't get it to the OBD sensor..
Click to expand...
Click to collapse
I'm now on AT&T Galaxy S4 with SlimBean 4.2.2 and Torque Pro works flawlessly!

CZ Eddie said:
I'm now on AT&T Galaxy S4 with SlimBean 4.2.2 and Torque Pro works flawlessly!
Click to expand...
Click to collapse
Good to know!!! I'll try out Slimbean for the S3. Thanks!

[Q] Bluetooth broken on CM10.1 (+ any 4.2 ROM tried); Drop to CM10.0, or other?

Hi,
I've a few 4G's running Cyanogenmod 10.1-RC4.
Generally great, but ...
Bluetooth is unstable, and refuses to pair with many devices. That's old news -- LOTS of others on 4.2.x-based ROMs are reporting similar problems.
NONE of the fixes/workaround I've managed to find/try have helped. And, AFAICT, Google's "not talking".
My alternatives atm seem to be:
(1) stay on current 4.2 ROM and live without Bluetooth
(2) wait for 4.3, 5.0, or 'whenever' it gets magically fixed
(3) drop back to another version (<= 4.1 ? other) where bluetooth is known to work and be stable.
(1) isn't an option. (2) is plain foolish. (3) seems like a (possible) plan.
QUESTION: What's a recommended choice? I don't need flashy, I need functional -- rooted and without vendor bloatware.
Is CM 10.0 my "best" choice?

BT is imho the only pain point of 10.1/rc5. I too have read that none of the fixes work that corrected it on earlier versions.
Does anyone have a solution to the BT problems that is up to date with 10.1/rc5?

Good questions about cm op. Subscribing.
I'm considering cm for my epic due stock rom being a pos pita, but need bt. Same requirements, functional, not flashy, slim, fast and good battery. Please be sure to update and post here. I'm interested in what route you take.
Zaggy
Sent from a rooted candy bar

Bueller?
Anybody?
756, you figure out what your going to do? Is cm9 an option?
Sent from a rooted candy bar

Zagnutty said:
756, you figure out what your going to do? Is cm9 an option?
Click to expand...
Click to collapse
For getting bluetooth & wifi both working at the same time, CM 9.1 RELEASE is the only viable option in the CM product line. On any of my phones, anyway. Neither 10.0 or 10.1 work.
I switched after finding this bug
https://jira.cyanogenmod.org/browse/CYAN-878#comment-12632
which got no traction at all. Lots of references in there that make you wonder what Google, at least, is thinking.
Between all that, and the thin responses here, v9.1 will be good enoough until I eventually updgrade to other phones/ROMs.

Bluetooth temporary fix
Bluetooth issues are for almost all cm10.1 roms. The only solution is to force stop Bluetooth from applications and the toggle again. It works for me
Hit THANKS if I helped :laugh:

reshampanth said:
Bluetooth issues are for almost all cm10.1 roms. The only solution is to force stop Bluetooth from applications and the toggle again. It works for me ;
Hit THANKS if I helped :laugh:
Click to expand...
Click to collapse
Hi! Just want to know how to force stop bluetooth, I have cm 10.1 and having problem with bt. Thanks in advance

leo8259 said:
Hi! Just want to know how to force stop bluetooth, I have cm 10.1 and having problem with bt. Thanks in advance
Click to expand...
Click to collapse
Go to settings- applications - all applications - bluetooth share- force close
That's it. Toggle again and it shud work
Don't just say thanks, hit thanks

[Q] Google Edition 4.3 (09/07/2013) Question

Being that I'm a noob (<10 posts), I can't post this in the actual ROM thread (mods, please move if you deem it appropriate).
I wanted to ask if there was a way in Google Edition 4.3 to change the clock settings to *NOT* display the hour in bold font?
Is that functionality available and I'm missing it in the settings?
Thanks yeahmann for putting that together and to the entire XDA community for all the hard work!.

Questions and Help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

piotreks4 said:
Being that I'm a noob (<10 posts), I can't post this in the actual ROM thread (mods, please move if you deem it appropriate).
I wanted to ask if there was a way in Google Edition 4.3 to change the clock settings to *NOT* display the hour in bold font?
Is that functionality available and I'm missing it in the settings?
Thanks yeahmann for putting that together and to the entire XDA community for all the hard work!.
Click to expand...
Click to collapse
As far as I know you can't change the look and feel of the widget in 4.3, however you can always install Cyanogenmod cLock widget where you can customize it. Hope this helps.
Sent from my GT-I9505G using xda app-developers app

a103 said:
As far as I know you can't change the look and feel of the widget in 4.3, however you can always install Cyanogenmod cLock widget where you can customize it. Hope this helps.
Click to expand...
Click to collapse
It does help -- thank you.
I actually ended up flashing CM-10.2 because of the availability of better config options and am so far loving it.
Thanks again and best wishes!
P :good:

piotreks4 said:
It does help -- thank you.
I actually ended up flashing CM-10.2 because of the availability of better config options and am so far loving it.
Thanks again and best wishes!
P :good:
Click to expand...
Click to collapse
Whenever you get a chance can you please let me know how's CM 10.2 working for you so far? I mean can that be used as a daily driver with major things (GPS, Bluetooth, NFL, camera etc) working without any issues. If so please let me know which nightly did you flash.
Thanks.
Sent from my GT-I9505G using xda app-developers app

a103 said:
Whenever you get a chance can you please let me know how's CM 10.2 working for you so far? I mean can that be used as a daily driver with major things (GPS, Bluetooth, NFL, camera etc) working without any issues. If so please let me know which nightly did you flash
Click to expand...
Click to collapse
So far, CM 10.2 is rock-solid. I flashed The Sept 5 Nightly. Reason being - Friday gives me 2 days if something doesn't work.
I tried AOKP (too many options for me -- never thought I'd say that) and both Virgin and 'stock' GE (4.3) ROMs (a bit too stock for me).
I have so far set up email (GMail and Work using K-9 + Invitation Processor) and customized some options/appearance (cLock is da-shizznit). The camera works perfectly. I have not set up Bluetooth and not used GPS, yet, but will try both tomorrow on my way to/from work. One thing that I still need to figure out is the file-system layout inside Android (i.e. /storage/0 vs. /storage/legacy, etc...) as I'm apparently using 7.4GB out of 9.6GB available. This is probably because the stock T-Mo version left most of its guts behind and/or I incorrectly cleaned the device after having flashed all the ROMs.
One thing that I've noticed (with all the ROMs, except stock T-Mo) was that when you press the power button to lock/shut-off the screen, it ends up shutting off like an old-school TV. With the stock version, it would go dark seamlessly.
Regardless, I really enjoy having this phone now that I flashed CM on it. The fact that they provide an 'update-CM' option directly inside the settings is awesome in its own right. I'll update this thread once I give GPS and BT a run (can't promise I'll run TV apps on it, though -- that's not my cup-o-tea).
Best!

if you find certain things to be a bit buggy on CM, give Virgin Rom another try. the hardware elements of the phone work flawlessly. in an ideal world, someone would use Virgin Rom as a base and "Cyanogenize" it so that more things were customizable, such as Quick Setting toggles. CM is great, but the nightlies don't have the stability that the GE Roms have, obviously.

Thanks for your inputs...I guess back up of your old Roms may be eating up your internal space (if you have backed them up )...the old tv animation is the crt animation which Google introduced in ICS 4.0

a103 said:
Thanks for your inputs...I guess back up of your old Roms may be eating up your internal space (if you have backed them up )...the old tv animation is the crt animation which Google introduced in ICS 4.0
Click to expand...
Click to collapse
Aaah! Good to know (about the TV animation).
I haven't backed up my old ROMs, but I'll definitely investigate space usage once I find some time.
Tested GPS and BT this morning: played a few songs over the car radio streaming over BT - awesome.
GPS is working good, too. I get a lock within 10 seconds of starting any app requiring GPS.
Thanks to all!

piotreks4 said:
Aaah! Good to know (about the TV animation).
I haven't backed up my old ROMs, but I'll definitely investigate space usage once I find some time.
Tested GPS and BT this morning: played a few songs over the car radio streaming over BT - awesome.
GPS is working good, too. I get a lock within 10 seconds of starting any app requiring GPS.
Thanks to all!
Click to expand...
Click to collapse
Even I flashed the RC2 last night. Using it for a few hours only, but it's rock solid as you mentioned.
Sent from my SGH-M919 using xda app-developers app