yashsingh1/xdaforums huggingface dataset:
[HD2 General] koolxx:
hi, T-Macgnolia, thanks for the reply. the reason i want an older version than 3.14 is cuz you said that 3.14 isn't compatible with older radios, which i need to eliminate static from my hd2. you suggested, therefore, that i try older radios which are more compatible with roms older than 3.14.

i'll be installing yahoo messenger tonite, just to let you know.
[myTouch 4G Q&A, Help & Troubleshooting] syntropic:
My glacier is not being recognized by my pc. I have reinstalled all of the windows drivers from HTC, rebooted pc, tried a different usb port, even tried re-flashing the CM7/RC4 update, but the problem persists.

My next option would be to wipe/reset-reflash-then restore settings. But if I do that, I want to make I sure I don't accidentally restore the corrupt file... Does anyone know where this phone driver (or the file that is causing this error) is on the phone so I can avoid restoring it?
[myTouch 4G Q&A, Help & Troubleshooting] option94:
That issue has nothing to do with your phone unless the actual usb port went bad.

This is definitely a computer issue.
[myTouch 4G Q&A, Help & Troubleshooting] syntropic:
Well, its not like I have any reason to not believe you, but, I guess thinking it has to do wih the phone gives me a bit more hope.

Honestly, I don't know what could have happened. It was working fine maybe a week ago, and now no matter what I do, windows says its not recognized...specifically windows says "device not recognized, try re-plugging the device back into the usb port. If it continues to not work, replace the device" (yeah right...i think I will pass on windows' suggestion in this case).

I have also tried reinstalling the usb laptop filters/drivers too. I am thinking it has to be something obvious because I have not done anything unusual since it worked properly.
[myTouch 4G Q&A, Help & Troubleshooting] TrueBlue_Drew:
So do you have the SDK set up then? You can also try setting up adb with the method found in my signature. Have you tried a battery pull and then see if your device is recognized through adb?
[myTouch 4G Q&A, Help & Troubleshooting] syntropic:
Do you mean just pull out the battery, but plug in the (mini) USB and try and get adb to work?

By the way, its not adb exactly which had the problem. ,Its just that suddenly, windows is stating it doesn't recognize the device..(code 43 in device manager properties). I didn't do anything (i don't think), and its driving me crazy. I have not pulled the battery yet, but I have retried just about every other driver install/reinstall.
[myTouch 4G Q&A, Help & Troubleshooting] TrueBlue_Drew:
Just pull out the battery and put it back in and power up.

So when you say it wont recognize it, you mean as a external storage device then? That could be a SDcard issue but sounds like a PC issue. First thing I would do is see if your device is recognized in adb. Follow the link in my signature if you dont allready have adb set up. That should tell you if your usb is functioning also. If that all goes well, I would check your SDcard and make sure your issue isnt there.
[myTouch 4G Q&A, Help & Troubleshooting] syntropic:
Ok... Just ask me... No, it its not recognized in ADB, nor is windows liking it.

Windows sometimes says "USB DEVICE HAS malfunctioned". When trying PDANet drivers, I get error =103. I dint know how ADB FEELS as there is no feedback, but I have started ADB, ran adb devices, nothing listed, I have toggled USB debugging just to see what would happen, and I can tell the device us being disconnected and reconnected (based on audible alert), but otherwise, same as always.

I am starting to think it is the SD. And that maybe I dropped it a few feet on to the carpet or something mild like that, and I need to re-seat the SD. Sound logical?
[myTouch 4G Q&A, Help & Troubleshooting] syntropic:
I don't seem to be making any progress whatsoever. I really need to get this phone recognized because I ned to do some boot animation and splash screens

As said, I have tried everything possible with driver installation and uninstallation, both using revo-uninstaller and the device manager. Does anyone think it might possibly be the phone our could this only be a windows issue?

Does anyone have any more possible suggestIons?
[HD2 General] koolxx:
has anyone been able to elminate static on their hd2 by modding the radio rom?
[HD2 General] T-Macgnolia:
Yes koolxx you can more than likely solve your static problem with modding your HD2. Go to the HTC HD2 Master Radio Thread and start downloading and flashing different radio versions. Just do not flash a 2.04.50.xx, 2.05.50.xx, or a x.xx.51.xx radio to a T-Mobile HD2 as it will brick a T-Mobile HD2.

Good luck. :D
[General Topics] cardio11:
...

As a complete noob to the android world..i must say...i F*Kn love androids :)
[Continuum General] sytech55:
Lost the Applications icon that was listed in Action bar. Need help getting it back.
[Continuum General] sytech55:
I'm using ADW launcher. I've checked the ADW Settings but I can't find where to add the Application icon. How do I get Application icon on one of my pages?????
[Continuum General] lincoln3823:
hold down on a empty spot on any page then cluck launcher actions then click on open/close app drawer

Sent from my Rooted Space Time Continuum w/h a 2600mAh battery
[Continuum General] sytech55:
You don't want to know how long I looked for this! I've been all over the screen trying to get it. Many thanks!!!
[Continuum General] lincoln3823:
LOL no problem the samething happened to me the first time I used ADW just remember for next time

Sent from my Rooted Space Time Continuum w/h a 2600mAh battery
[Thunderbolt General] pats4life100:
can we get a rom built with spb shell as the launcher like how the devs use launcher pro and others
[Thunderbolt General] jonwgee:
sure, if it was a free app
[Thunderbolt General] Kid_Cudi:
This is not a Q&A forum...

Thunderbolt «» das BAMF Remix
[Thunderbolt General] andrew8806:
Paid apps are to not be included in roms. XDA does not promote piracy. Closing thread.
[Epic 4G General] JRider:
I've tried pretty much every Froyo ROM that's been released, stock and custom, and have yet to find one that doesn't have Bluetooth issues. It seems to me that the "added Bluetooth functionality" of Froyo has caused problems that have yet to be isolated.

I didn't have any connection issues with any Eclair. It sucks, because I keep bouncing back and forth when a new Froyo ROM is released hoping I won't have these same problems. But I always do!

By the way, the problems are with my hands-free system in my car-- where it will not reconnected without turning on and off Bluetooth. It will also lose it's pairing information, and need to be re-paired on occasion. My wife's Incredible has zero problems in the same car; as does the Epic when it's running Eclair.

The reason I'm hoping for a Froyo release that doesn't have Bluetooth issues is because I do like some of the issues Froyo offers, but having working Bluetooth is more important. :(
[Epic 4G General] stir fry a lot:
I've had that issue before but SFR 1.1.0 w/ Vision kernel has been flawless for me. I've been running both since the first day of release.
[Epic 4G General] tigerknight:
My issue with bluetooth is that unless I hang up with the special 'hang up' button on my dash panel (the other party hangs up first, or the call drops, or etc) then my car thinks it is still on a call and won't release the audio back to music.
[Epic 4G General] musclehead84:
The new bonsai rom doesn't seem to have the problem. If you are having the problem then wipe data in cwm. Sometimes you have a corrupt data carryover

Sent From My Evo Killer!!!
[Epic 4G General] mattallica76:
None of the Bluetooth issues currently present in EC05 are ROM related. The problem you are describing occurs usually after ext4 conversion or switching from one ROM to another. I haven't heard anyone report this type of issue that is running stock EC05.

I posted a solution in that has helped several folks and myself who were experiencing similar issues. Try this and let me know how it goes.

http://xdaforums.com/showpost.php?p=12120496&postcount=1392
[Epic 4G General] JRider:
I'm currently running Bonsai 4.0 and it's seem to have been the worst. Are you telling me the they've done something in their latest release that fixes this issue? I don't see anything in their release notes that mentions this.

And trust me, I wipe data in CWM every time I try a new ROM.
[Epic 4G General] JRider:
Interesting... I seemed to have the problem with stock EC05 as well. I Odin'd to D18, then ran the stock update.zip for EC05. I wiped as well.

I'm going to look at your post right now.
[Epic 4G General] JRider:
Ok, I just took a look. Wouldn't an Odin to D18 and/or a wipe delete this corrupt data in the data/misc/bluetoothd anyway?
[Epic 4G General] mattallica76:
Yes, they both would, unless you restored it with Titanium or Nandroid/CWM. If you still have issues after trying the method in my post, you might want to double check your baseband version to make sure it's EC05. The Bluetooth is part of the modem. You might try reflashing the EC05 modem as well.
[Epic 4G General] JRider:
I've never restored anything after reflashing. Coming from Windows Mobile ROM flashing taught me it's never a good idea to do.

I'm definitely on EC05 baseband. I've also tried reflashing the EC05 modem with Odin as well. At first I thought that fixed it for me. But a day later, the problems were back. :(

Again, whenever I flash back to an Eclair ROM, I don't experience any of these problems. So I'm more opt to think the issue lies in Froyo's "updated bluetooth" features.
[Epic 4G General] mattallica76:
EB13/EC05 definitely has a couple BT issues, but the one your describing has not happened on my stock Epic and only happened on my rooted one under the conditions I described in previous posts (and was fixed). We use both phones with several BT devices pretty extensively. If data wipes and reflashes haven't worked for you, and your issue is only with one BT device, you might try clearing the memory of the device. Also you should see if you have issues pairing with other devices.
[Epic 4G General] JRider:
Thanks for all of your input!

Like I said in my original post, my wife's Incredible works with the same car without any issues. I've also tried "factory resetting" and erasing all paired devices in the car. And it always ends up with the same issue- any Froyo ROM I run has problems. Like I said, I've tried several, with wipes and Odin to stock, and stock EC05. All of them have the same problems.

I'm definitely not the only person who's experiencing the issues I'm describing. If you read through this other thread at another forum (http://androidforums.com/epic-4g-su...82-bluetooth-problems-after-froyo-update.html) you'll see a couple people describing the exact same problems. One user even talks about the phone showing that it's still connected to the device even after the car is shut off. And the only way to disconnect is turn off bluetooth. Another user talks about the car randomly reporting it as "BCRM Device" instead of what the Bluetooth device name is. Both of these problems, I've had as well.

Trust me, if I can find the cause of this issue, or a ROM that doesn't have it, I'm willing to give it a go. I want the Froyo enhancements, just not the bluetooth issues.
[Epic 4G General] mattallica76:
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
[Epic 4G General] JRider:
Yes, it does.

Actually, one of the things Froyo does better with handsfree in the car is this feature. Eclair won't sync my Exchange contacts for some reason. It will only sync "Phone Contacts". It also doesn't handle the recent call log as well either. For some reason it will show sent emails and texts in my call history in the car. With Froyo, neither of these problems exist. But that means nothing when there's a fundamental issue with bluetooth itself.

Why do you ask?
[Epic 4G General] mattallica76:
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
[Epic 4G General] JRider:
I actually went back to DI18 yesterday, rooted, removed bloatware, and I haven't had a single problem with hands-free Bluetooth in my car.

Again, there's definitely issues with Bluetooth in every version of Froyo. Disabling certain basic features (that other phones have been successfully doing for years) just to get it to work is not an option for me.

For now, I'll run Eclair, and hopefully these issues are resolved at some point.
[Epic 4G General] hofs1:
I will totally agree with the OP Stock 2.1 was fine with my Parrot BT system. Since 2.2 Ive tried a bunch of roms and finally back to bone stock AND i still get a ton of BT issues ( disconnects,missing calls, phone is muted after calls etc etc) I miss my Palm Pre...lol
[Epic 4G General] 5111:
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
[Epic 4G General] JRider:
I've been running DI18 (stock and rooted) for the past two days with literally zero problems with bluetooth. I even loaded the EC05 modem to prove it has nothing to do with the modem (apparently bluetooth is part of the modem tar). So right now, I'm running Eclair DI18 with EC05 modem and bluetooth is working flawlessly.

So I will say it one more time... there is something in Froyo for the Epic that is causing bluetooth issues. It's not the kernel, it's not the modem, it's the Android OS (Froyo 2.2) that is causing the issues with bluetooth.
[Epic 4G General] omgitzsars:
JRider- Just as an FYI, I am having the EXACT same problems you describe with my Moto Roadster. You aren't alone. I've tried most of what you said you've tried with no luck as well. Hope somebody finds a solution.
[Epic 4G General] Paleryder:
I wonder if it would be worth looking into updating the drivers on your stereo possibly the culprit, just a though
[Epic 4G General] JRider:
I don't think so. For one, it's a brand new car with the latest firmware. And two, I'm not the only one having these issues.
[Epic 4G General] Top Nurse:
Op: there is a rom that doesn't have bt issues. Unfortunately it hasn't been made yet. :D
[Epic 4G General] JRider:
Actually it has. It's called Eclair.
[Epic 4G General] JRider:
Just an update. I've been running Eclair (DI18) for about a week now, and Bluetooth has been running perfectly!

Maybe this newly announced Gingerbread release will include a fix. Until then, I'm sticking with what works.
[Epic 4G General] nathan951:
I'm having problem with my epic and my Kenwood stereo on bonsai 4.0.

My wife is having problems with her epic stock EC05 and her ford Sync.

So there is a Bluetooth problem....
[Epic 4G General] Quis89:
After using my Bluetooth...then turning it off my speaker no longer works. All audio comes from the earpiece. Music, ringtones, notifications...everything. I have to power my phone down to activate my speaker again. Anyone had this issue? I would be OK if there was a fix other than a soft reset as I'm not always able to perform one immediately.
[Epic 4G General] dwallersv:
Yes, you're no alone. Several people have reported this bug.

I've had it occur a few times, and like you, the only solution was a reboot. The 3-4 times it's happened have all been seeming without any usage pattern I can discern as a cause, and most of the time it doesn't occur -- i.e., disconnecting BT returns things back to the way they should be.

I've found I have the fewest occurances of problems when I leave BT on the phone on all the time and never turn it off, simply enabling/disabling by turning my BT device on and off. This doesn't eliminate all occurances of the various problems (this among them), but it seems to minimize them.
[Epic 4G General] mpscmedic:
It has to be with the way the phone is rooted. I use my bluetooth, and have had 0 issues with viper ROMS and Syndicate. You might need to odin back to stock and reroot.
[Epic 4G General] Top Nurse:
I *think* the problem is that some new devices don't play well with our Epic. I'm sure Samsung was only concerned that someone could use a BT ear piece while driving.

Sent from Bonsai 7.0.3
[Epic 4G General] mattallica76:
This problem is a bug that exists while using Bluetooth on a device for both ad2p and phone calls. The only workaround (until Sammy or one of our great devs comes up with a fix) is to use the BT device for one or the other. This will prevent the audio from being routed to the phones earpiece after BT disconnects. To do this, go into the phones BT settings. Then long press the device that you are having trouble with. Next uncheck "Media Audio" or "Phone Audio", depending on which purpose you want for the device.
[Epic 4G General] mattallica76:
Has absolutely nothing to do with root or ROM. BT has been messed up ever since the first Froyo betas. This particular issue only effects folks that use BT for both media audio and phone audio simultaneously (on Froyo).
[Epic 4G General] mattallica76:
Most of these same devices played well in Eclair, but not on Froyo. Samsung is know to use a messed up Bluetooth stack in general.
[Epic 4G General] Bobulus:
I frequently use my BT headphones with my Epic. It supports both ad2p and phone calls.

I've experienced the 'calls routed to earpiece' thing several times.

My experience is that doing things in a certain order takes care of the problem.

- Start out streaming music through the BT device.

- Pause music.

- Wait 2-3 seconds for a noticible 'click' (or lack of background static) after the music pauses for the streaming audio to actually disconnect <- step people aren't doing!

- Turn off BT device.

- Turn off BT on phone.

As long as I wait for that click, I don't get the earpiece routing problem, and can continue to my my headphones for both calls and music.
[Epic 4G General] mattallica76:
None of that will matter if you receive or make a call during the streaming. You will still end up with the audio in the earpiece instead of the speaker. Although your information here might be useful to mkasick, as I sent a request to him a while back to look into this problem.
[Epic 4G General] fsunole01:
Similar Issue

I just got a new Epic (replacement) and this one is having issues with just working well with VW Bluetooth. When it connects, I'm able to make one phone call, but then even though it shows paired, calls come straight to phone. If I try calling through VW Bluetooth, says "Dial Up Failed" Then I have to disconnect, unpair, repair and reconnect - but then it only works for one call again. I saw a couple others with this issue, but no comments on it. Any clues, suggestions? It's really frustrating and then I notice that my phone will automatically activate the Music Player...even more curious.

Just as a side note, the last Epic also had Froyo without any issues like this...had to replace because it was a speaker malfunction...

Hope this forum can help! Thanks in advance.
[Epic 4G General] motog35:
OMG! I thought I was the only one with this problem. This happens all the time with my Parrot Bluetooth, as well as the volume routing through the ear piece and not speaker.

This is very frustrating to say the least.
[Epic 4G General] JRider:
Just checking back in. It's now been over a month since I've gone back to 2.1, and I have literally had zero issue with bluetooth in the car.

It's so refreshing to get in and a few seconds later the phone is connected and ready to send/receive calls.

Every once in a while I miss some things Froyo offered. But when I ran Froyo, I was frustrated every day when my bluetooth wouldn't work. So I'm much happier now. :)
[Epic 4G General] JRider:
Well, I'm going to check back in once again.

I couldn't stand running Eclair any longer-- especially since Gingerbread is right around the corner (hopefully). I installed Bonsai's latest Froyo ROM today knowing that I was going to have to deal with Bluetooth connection issues in my car. But, I did it anyway.

At first, things seemed to be looking up. Could it be? Is it possible I found a Froyo ROM that doesn't have this weird Bluetooth problem? No. It was just a tease. After running a couple errands, I came back into the house and realized my phone thought it was still connected to my car. As you know, this was one of the bugs.

So I went back out to the car to toy around with it. I decided to take some advise from one of the earlier posts about using media streaming along with phone, and how that is the issue. So I disabled media streaming on my phone, as well as the function all together in the car's Bluetooth settings. So far, my phone has connected and reconnected every time. I've gone in and out about 5 times now (made a couple calls as well) and the phone connects and reconnects every time.

Now, it's too early to tell if this truly is a workaround. But I'm hoping it is. Obviously, not using media streaming is a bit of a bummer. But for me, it's something I rarely use anyway. I have Sirius, and a USB stick full of songs. It's definitely more important to me to have stable Bluetooth calling.

I will update in a couple days.

P.S. I haven't tried any of the beta Gingerbread ROMs yet. Maybe this is all moot because it's been fixed.
[Epic 4G General] DroidApprentice:
I certainly hope so, although it's prompted surprisingly little discussion for being one of the phone's biggest bugs. I have a BT headset and a BT stereo streaming device and using them both at the same time causes audio routing problems etc. quite often, as I've mentioned.
[Epic 4G General] JRider:
Well, after a longer test period, it appears there are still Bluetooth issues. I thought disabling the media playback had taken care of the issue, but all of the same problems I was having before have crept back.

It's so frustrating. I sure hope something is fixed in the next update.
[Epic 4G General] JRider:
It's fixed!

It seems as though the latest Gingerbread update (EI22) has fixed every bluetooth issue that were present in Froyo! I'm so happy to have working bluetooth again.
[Epic 4G General] JohnCorleone:
Good to hear. That drove me nuts on my Epic.
[Streak 5 Q&A, Help & Troubleshooting] mid_life_crisis:
What audio formats does the Streak play?

I never had so much trouble looking up the answer to such a simple question.
[Streak 5 Q&A, Help & Troubleshooting] mid_life_crisis:
So experimentation shows that it doesn't play lossless wma files.

Is there a lossless format that will play on it?
[Streak 5 Q&A, Help & Troubleshooting] bugmenotacc:
get PowerAMP it plays plenty of file types:

mp3, mp4/m4a (including alac), ogg, wma*, flac, wav, ape, wv, tta (* some wma pro files may require NEON support)

I love it, it's automated, so when I plug in my headphones (even BT ones) it resumes play.

the basic player is just that, basic.

I'd link it, but I'm new, look it up on appbrain.
[Streak 5 Q&A, Help & Troubleshooting] rebski:
Good question. I can only speak for FLAC support as I don't use anything else.

The only Android media player that I know of that recognises FLAC is PowerAMP

http://powerampapp.com/

I second @bugmenotacc's endorsement.
[Streak 5 Q&A, Help & Troubleshooting] mid_life_crisis:
I tried PowerAmp and it didn't play the album I ripped to flac.

I read the help section this morning (amazing what you can learn when you do that) and found out about selecting folders instead of the android library and lo and behold flac files play. Looks like I'll probably end up buying PowerAmp.
[Streak 5 Q&A, Help & Troubleshooting] rebski:
Yes it gets a bit confusing, glad you got it sorted too.

I loaded about 6 albums to my sd card today and set Android Settings to pull in the album artwork. Which all happened very quickly and seamlesly.

It is probably old fashioned of me but I prefer to set a Music folder rather than always have the app search my device for files.

Enjoy the app.
[Atrix 4G Q&A, Help & Troubleshooting] Greenbelt:
Have any bell Atrix owners been successful at installing gingerblur?
[Atrix 4G Q&A, Help & Troubleshooting] ScottRTL:
I have been googling the hell out of this, and it looks like a Big ol' no...