Related
Hello!
I'm running EB13.
After I'm running Voice Dial all it does, says something like "Talk, please" Then it is an error message and "Bye".
Nothing else.
How to make it work? Is it working or not?
P.S. I've installed EB13voicedialfix. Still not working.
Is there is the way to make it work somehow?
Not yet I'm am ocd checking these forums for a fix or new rom that contains a fix. Kinda blows
Epic 4g
Im posting here cause my phone is force closing xda app when i hit new topic. Sorry. My apps have recently been force closing on me. The reason i came to post is today my gallery stopped loading. It starts, then "buzz......buzz buzz buzz" force close. I cant change my wallpaper. Xda has been doing this also. Need help or something. Cleared data on gallery, restarted, pulled battery. Still doesnt work.
Sent from my always stock, froyo Epic
I assume you are:
1) running a Deodexed rom
2) Using bluetooth voice dial.
I and many others have the same issue, may want to change the name of your post to reflect that and maybe we can compile details here. EB13 voice dial fix seems to only fix the non bluetooth voice dialer, but as soon as you turn on a bt headset you will see the behavior you mention.
If you are using complete stock EB13 people have been saying BT voice dialing works fine.
I'm hoping one of the devs finds us a fix soon, I would really like this working but wont go back to stock eb13
I'm using eb13 stock and you are right, i'm getting this error on BT voice dial. I don't know you noticed it or not but it is not working without Bluetooth. I mean, it doesn't say anything and I couldn't say anything to the Voice Dial without BT.
Sent from my SPH-D700 using XDA Premium App
By the way, I've noticed that Vlingo is working.
Any Fix for this yet?
Voice dialing works fine in EC05. However I don't know why they can't have a voice READ you the incoming call as a standard feature...hell, it was in crap-ass Windows Mobile. And Vlingo is just too invasive an app for me to consider.
mgh333 said:
Any Fix for this yet?
Click to expand...
Click to collapse
Flash any custom ROM or go to full EC05 stock. BT voice dialing works fine in either.
Do you BONSAI?
I seem to be having problems every so often with the WINAMP not playing music, saying file not able to be played or even in QIK or Gallary, saying video cant be played, but if i do a reboot of phone ( which is PIA due to battery drain), they work again. I seem to remember this issue starting before i updated to FROYO EB13, but wanted to know if anyone else knew about it.
I was using SuperNovas rom over DK28 and to get to EB13, i actually just did a factory reset using ###786## and after entering MLS got a it. After that i went then signed into gmail account, got contacts back, then made sure to get a GPS lock ( outside only, inside house doesnt work) and then went to CWM and flashed the DEOXED version of EB13, I then flashed SUpernovas new rom and then did a ADvanced restore of Data. I never did an wipes in CWM but didnt have any info left after doing to Fact Reset. Anybody else use this method to get to EB13. Everything else works great, dont seem to have any other issues other that GPS lock inside house is still impossible.
come on nobody else is having this problem, somebody posted in the problem thread they had this issue. ANYONE, ANYONE, BUELLER, BUELLER!!
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.
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.
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.
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!!!
JRider said:
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.
Click to expand...
Click to collapse
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://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
musclehead84 said:
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!!!
Click to expand...
Click to collapse
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.
mattallica76 said:
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://forum.xda-developers.com/showpost.php?p=12120496&postcount=1392
Click to expand...
Click to collapse
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.
JRider said:
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.
Click to expand...
Click to collapse
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?
JRider said:
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?
Click to expand...
Click to collapse
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.
mattallica76 said:
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.
Click to expand...
Click to collapse
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.
JRider said:
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.
Click to expand...
Click to collapse
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.
mattallica76 said:
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.
Click to expand...
Click to collapse
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.
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Does your automobiles head unit support Bluetooth phonebook functionality by chance?
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
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?
JRider said:
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?
Click to expand...
Click to collapse
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
mattallica76 said:
Because I remember reading about the phonebook sync causing the Bluetooth to stop functioning. Try disabling the contacts sync and see if that helps.
Sent from my SPH-D700 using Tapatalk
Click to expand...
Click to collapse
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.
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
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
5111 said:
I have had all of the same issues since updating to Froyo. I had them stock and rooted.
Click to expand...
Click to collapse
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.
JRider said:
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.
Click to expand...
Click to collapse
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.
Is anyone else noticing erratic characteristics from the compass while getting a GPS lock with GPS Status/Toolbox?
Can this be one of the problems contributing to my horrible battery life in MidNIGHT 6.0?
In my defense, I did do some searching, both google and within XDA before i posted...
TIA!
Huta
so i guess it's just me then... hmm
Gps is not as accurate for me as well but it still works. The battery problem is most likely the cpu always being used around 35%.
Sent from my SPH-D700 using XDA App
I've had the same issue with mine, I initially was on EC05 stock with CWM 3.0.2.5 then flashed "Swiss Cheese Samsprint" ACS EE03 ROM, and Odin the Modem to EE03 which broke my GPS, I flashed the ACS EE03 GPS Fix, and I get that same icon but no GPS lock, I figured it was the ROM but same thing happened on Midnight ROM 6.0 and also on Gingered 0.07. I stayed at Gingered 0.07 which is basically a combo of Swiss Cheese and Midnight. I probably could get it to work if i downgraded modem and rom back to ec05 stock and lock gps signal before i flash the EE03 modem but im lazy, I dont use GPS all that much anyway.
I am currently using Midnight 6.0, and I have GPS issues, but my battery life is great.
My compass has ALWAYS been essentially useless. Once in a while I can get it calibrated so its KINDA accurate (I'd hate to be lost with the thing and actually NEED to use it, it'd be useless), but I've never had it working well.
As far as GPS goes, I've had it be pretty good when it works (SFR 1.1.0, now 1.1.1) although there was a "crashing" issue where you'd have to relaunch navigation to get it to reinitialize. That being said, 1.1.1 has a fix to prevent this (still testing, seems good so far).
One thing I noticed which I find very interesting. The EE03 Gingerbread leak gave me THE MOST AMAZING GPS PERFORMANCE EVER. I couldn't believe it was the same phone. Immediate locks, never lost a lock (even under a bridge!). That's with both ROM and Modem on EE03. Compass still seemed screwed, which is a damn shame (because it makes me think its just crappy hardware that will never be fixed.
As much as I love this phone, seriously, it's like 9 months since release and we're JUST NOW getting GPS to work right? I love our devs, and they seem to make much better headway but jesus christ, how bad is samsung at their job that a) we're still talking about this bug in STOCK roms 9 months later and b) we clearly have evidence that it CAN be fixed (problems not in hardware).
Now I have a very difficult decision to make. Do I get the Evo3D with potentially terrible battery life (my mom's thunderbolt only lasted til 1pm basic phone/sms) and mediocre camera, or do I try out the S2 hoping samsung's learned their lesson...
Still nothing...
I have tried all 3 Leaked Gingerbread ROMs. I tried the acs ee03 modem + gps fix, with everyone of them. I'm still getting no GPS signal. The icon blinks on the bar! the phone recognizes a signal, I no longer get the warning after I install "the fix" but it still constantly searches in Navigation or any other App. Has anyone figured anything out?
bejealousmofo said:
I have tried all 3 Leaked Gingerbread ROMs. I tried the acs ee03 modem + gps fix, with everyone of them. I'm still getting no GPS signal. The icon blinks on the bar! the phone recognizes a signal, I no longer get the warning after I install "the fix" but it still constantly searches in Navigation or any other App. Has anyone figured anything out?
Click to expand...
Click to collapse
Yeah i forgot who quoted this, but i remember someone saying they opened up google maps after Odin'ing the EC05 Stock rom THEN they flashed everything else, EE03 Modem last. That worked for me, however i still have the funkified compass, even MyTracks cant correctly orient me when I'm jogging, despite knowing my location by 3 meters.
http://forum.xda-developers.com/showthread.php?t=1099041
couple threads down from yours... its basically the GPS fix for DK28... start at stock ec05, get a lock, root, get a lock, odin modem, get a lock, flash any of the ee03 ROMs... should get a lock. As far as the compass goes, not sure. Get spare parts, do wifi sleep never or at least never while plugged... maybe resort to juice defender for now... theres only so much the wizards can do without source.
Try the upside down calibration (menu/settings/display/Horizontal Calibration) before giving up on the compass. For some reason, since Froyo, the pitch axis came up -180 degrees.
This is how to fix your gps.
bejealousmofo said:
I have tried all 3 Leaked Gingerbread ROMs. I tried the acs ee03 modem + gps fix, with everyone of them. I'm still getting no GPS signal. The icon blinks on the bar! the phone recognizes a signal, I no longer get the warning after I install "the fix" but it still constantly searches in Navigation or any other App. Has anyone figured anything out?
Click to expand...
Click to collapse
This nice fellow wrote a post on how to fix the gps problem:
http://forum.xda-developers.com/showthread.php?t=1096020
I've been experiencing the issue of outgoing audio cutting out during phone calls. I'd noticed it first when I tried EF02 and a variety of modems, and now I'm experiencing it still after going back to EC05 with the EC05 modem. Toggling speakerphone "fixes" the problem for that call.
I suppose what I'm trying to figure out is: could having tried EF02 have done something that going back to EC05 didn't resolve? Or perhaps was this happening after EC05 was OTA'd and I just didn't notice it? Is anyone having this on stock EC05?
Before I push to replace what's otherwise a perfect Epic, I want to see if this is a hardware or a firmware issue.
Sent from my Transformer TF101 using Tapatalk
Same issue
I am having the same issue. Tried EF02, which seemed to work great for awhile. Used Odin to return to stock for a completely different issue. Since that time on long calls...in excess of 10 minutes the person on the other end suddenly cannot hear me, and I hear them fine.
Currently ECO5 rooted, but stock otherwise.
Any ideas? I didn't see any answers to the first post, and don't see anything when I searched, prior to this post.