Related
The first couple of nightly builds were awesome for bluetooth but all the resent one have had issues for me. My problem is with wireless headphones namely the Motorola S9's. On the stock rom they worked awesome and rarely cut out. On DC3 they worked great and never cut out but I hated sense UI. So I start using CM6 and man was I surprised that bluetooth headphones worked great once again. Well somewhere along the line something has happened to bluetooth and now unless I am sitting perfectly still my head phones constantly cut in and out. I have since went back to DC3 and they work great again. Obviously I want to go back to CM6 but I use my headphones all the time. My question to the devs is did the power get dropped on CM6 for bluetooth and is there a way to turn it back up. I have asked this question on Cyanogen's site but honestly I don't think people read the forums over there. I would be willing to donate for a cranked up power profile for bluetooth (and yes I am already a donator on Cyanogens site just because I love his work) . Or does anyone have an idea on how to set it higher. I know everyone is trying to save battery but if I wanted to save battery I would have bought another blackberry with a tiny screen.
I did send a PM to Cyanogen but he never replied and to be honest I didn't expect him to. Im sure he gets 100's of PM's per day.
I am having a very similar issue. For me it's my BT Headset as well as my car's bluetooth( Motorola add on). It will connect ok but constantly drops off or in some cases simply refuses to dial the outgoing call. Like BuddaBelly I have tried several different Roms, including the latest DC and Fresh which both worked without any hiccups. Thought it might be a Froyo Issue but I have no problems with a Nexus One running 2.2. Any ideas?
I have the same problem i also have bluetooth issues on DC3.5 which is froyo. I dont use a Motorola headset (jawbone) so just wanted to throw this out that it doesnt appear to be just Motorola.
on a side note to Budda, You dont have to use sense ui in DC yuo cn download ADW Launcher (what cyanogem has as defualt) or any other launcher (launcherPro, another good choice) and even completely disable sense from the phone once you do through dconfig.
anyway Just thought i would throw this out there
omegasun18 said:
I have the same problem i also have bluetooth issues on DC3.5 which is froyo. I dont use a Motorola headset (jawbone) so just wanted to throw this out that it doesnt appear to be just Motorola.
on a side note to Budda, You dont have to use sense ui in DC yuo cn download ADW Launcher (what cyanogem has as defualt) or any other launcher (launcherPro, another good choice) and even completely disable sense from the phone once you do through dconfig.
anyway Just thought i would throw this out there
Click to expand...
Click to collapse
Yeah I know I can disable sense but it is still built in if you know what I'm saying. I just tested my headphones on my wife's stock evo and they work great. I do know for a fact that one of the first cm6 builds had perfect working Bluetooth so I'm just trying to see if we can have an option to turn up the Bluetooth power
Well after getting the official news that froyo is coming to evo this next week I expect this will get worked out at that time.
Hello all, new to the forum. Have been reading loads of topics and the amount of info available is great.
If it is possible at all, I would greatly appreciate some help with my desire.... I bought an unlocked/unbranded desire in London. Was waiting for the OTA update for Froyo 2.2 and tried to download it when I was finally prompted to on my phone but it would not download, saying the file was corrupted. Hence I installed it manually by downloading and installing the update.
Now for some reason, my phone will keep going onto "car mode" which will turn on and off randomly and repeatedly. This turns the screen on (even if its in my pocket) and drains the battery. All calls go to speaker automatically. Called HTC customer support and they claim the desire is not even meant to have a car mode- whether that is them talking crap or not is another question. They also said I have voided my warranty by updating manually.
How do I disable this annoying car mode permanently? From my reading I believe it is impossible to root my phone now as it is already running froyo 2.2.
If someone, anyone can help me or give me any advice that would be great
Thanks again in advance
Ali
Someone must have an idea..... ?
if you look in the development section, there is a thread where i think they managed to downgrade the new hboot to 0.80 look here
http://forum.xda-developers.com/showthread.php?t=741672
i assume that will make your device rootable again using unrevoked
That is odd. I didn't think that the desire had a car mode built in but I know there is an app which does that as I have it. It's called Car Mode (surprisingly).
Presumably you haven't got that app (or something similar) installed which might be causing it? If not you could try installing the app, using it to disable car mode and then uninstalling it.
snowmobile said:
That is odd. I didn't think that the desire had a car mode built in but I know there is an app which does that as I have it. It's called Car Mode (surprisingly).
Presumably you haven't got that app (or something similar) installed which might be causing it? If not you could try installing the app, using it to disable car mode and then uninstalling it.
Click to expand...
Click to collapse
froyo comes with htc car panel
AndroHero said:
froyo comes with htc car panel
Click to expand...
Click to collapse
Oh ok thanks. I didn't know that as I haven't got Froyo yet. Clearly the HTC customer support team didn't know either!
I think Froyo OTA comes with support for Car Panel, but not the actual app. I had to install it manually. But it might be in the rom you used. Second the turn off. Go to +> shortcuts>Settings>Car Dock and you should see the options, including Auto Launch.
al89nut said:
I think Froyo OTA comes with support for Car Panel, but not the actual app. I had to install it manually. But it might be in the rom you used. Second the turn off. Go to +> shortcuts>Settings>Car Dock and you should see the options, including Auto Launch.
Click to expand...
Click to collapse
Thank you, did exactly what you said and no more car mode
Now only problem left is that the screen still turns itself on for no reason.... my htc desire is on crack
Another problem with froyo it does my head in !
Sent from my HTC Desire using XDA App
Is there a way to fix this? I don't understand what's prompting the screen to periodically (and randomly) turning on. Even when wi-fi is off.
And when it does turn on, i lock the screen - and it turns on again as if the phone is taking the piss out of me lol. Drives me (and i'm sure all other users experiencing this) insane!
Any fix?
People have said this happens when a couple of the data prongs on the USB/Charge cable are shorted. Not sure why it's happening for you. Have you tried a factory reset?
You might want to install the OTA 2.2 update again. To do that you will have to wipe the device completely using this code. (came from this thread)
*2767*3855#
Think before you give this code. This code is used for factory format. It'll remove all files and settings including the internal memory storage. It'll also reinstall the phone firmware.
After that it should be possible to update the phone to 2.2 again.
I recently rooted my wife's g2 and installed CM7.1-rc1 on it.
She quickly realized that the phone's sound didn't work unless she put it on speaker.. The guide I followed should have set s-off as well and when I start into hboot (or whatever the recovery mode is called) i do see a message at the top about s-off..
I've installed both the 7.1rc-1 and the latest nightly release and they both have this problem.
After doing this I've also installed the latest radio which appeared to install just fine.. I downloaded the latest radio from here: http://forum.xda-developers.com/showthread.php?t=970809
Version 12.56.60.25_26.10.04.03
In About phone->Baseband version it now lists 12.56.60.25U_26.10.04.03_M
I wasn't able to find much else in the forums about this problem except for an incredible s and a wilfire.. It may be related to S-Off but i'm not sure exactly what to check. There are so many guides on how to root I just picked one that seemed easy, I can't even remember which one it was.. I obviously have root access just fine since I am able to install roms with no problems, I just can't get in call sound to work without turning on the speaker phone..
Note that the sound worked fine before rooting but I am not sure it worked with the stock version rooted since I only had that on here for a few hours and didn't make any calls.. Perhaps I should go back to stock and see if it even works there... Any suggestions before I do that?
Also, the original guide I used was basically the same as the one here: http://forum.xda-developers.com/wik..._Vision#VERIFY_.28using_.22gfree_verify.22.29
Reading through that tutorial I found how to verify s-off, superCID and sim lock off.. according to the output all of those things are correct:
Code:
# ./gfree_verify
gfree verify_cid returned:
@CID: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@SIMLOCK= 00
OK
# start ril-daemon
#
Edit -- Since i posted this I have reverted back to the original sense 2.2 rom (the one that came with the phone) and I still have this problem.. This is the rooted version, I have not de-rooted/s-on'd the phone yet.
Just to clarify, only the incoming volume doesn't work and only if speakerphone is off.. I've played with all the different volumes on the phone with no luck.. The mic works fine as the other person can hear me whether speakerphone is on or not.
Adding screenshots of the boot screen if that helps.
Just a status update..
I have since unrooted s-on'd the phone putting it back to the factory settings and i still have this problem.. Ironic that this could be a hardware problem when it happened literally right after the whole root process and what not.. At least it should still be under warranty so I'll be calling htc either tomorrow or monday if they aren't available by phone on weekends.
My wife is still going to blame me for this but I'm not sure what else I can possibly do.. Perhaps the customer service person will have an idea what can be causing this.. I have played around with headphones and car mode. With headphones on I get sound from the headphones just fine.. If i turn on speakerphone while i have headphones plugged in the sound does not come out the speaker on the phone (just my headphones) which means it doesn't appear that my phone thinks there are always headphones plugged in -- otherwise speakerphone wouldn't turn on.
My only other option to returning it is just tell my wife to always use speakerphone, which she won't like for sure.
mwolfe38 said:
Just a status update..
I have since unrooted s-on'd the phone putting it back to the factory settings and i still have this problem.. Ironic that this could be a hardware problem when it happened literally right after the whole root process and what not.. At least it should still be under warranty so I'll be calling htc either tomorrow or monday if they aren't available by phone on weekends.
My wife is still going to blame me for this but I'm not sure what else I can possibly do.. Perhaps the customer service person will have an idea what can be causing this.. I have played around with headphones and car mode. With headphones on I get sound from the headphones just fine.. If i turn on speakerphone while i have headphones plugged in the sound does not come out the speaker on the phone (just my headphones) which means it doesn't appear that my phone thinks there are always headphones plugged in -- otherwise speakerphone wouldn't turn on.
My only other option to returning it is just tell my wife to always use speakerphone, which she won't like for sure.
Click to expand...
Click to collapse
got same problem on my HTC HD2... warranty is over I think.. more than 1year.. guess i will need pay for it to repair. =/
this might help
Hey I'm not sure if you've fixed your problem yet but I had kind of the same problem with my rooted HTC g2.....I tried everything to fix it and then finally I remembered that I had froze the "car home" app using my backup pro. I felt like the biggest jackass in the world but after I unfroze it all my sound was back to normal. Hope this helps you out but either way everybody can get a laugh thanks to my stupidity :-D
The fact that your headphones work and your small speaker does not suggests that this is a hardware issue. I would look up the hardware guide for this phone and see where you can find a new speaker, it may just be as simple as that!
I dont think it's a hardware problem, or it's just a super coincidence but after rooting my desire z with 2.3.3 android to CM7 2.3.7 i'm also unable to VOL UP or VOL DOWN during the call !
Also would appreciate if someone helps.
Prancuzas said:
I dont think it's a hardware problem, or it's just a super coincidence but after rooting my desire z with 2.3.3 android to CM7 2.3.7 i'm also unable to VOL UP or VOL DOWN during the call !
Also would appreciate if someone helps.
Click to expand...
Click to collapse
Did you do a full wipe before flashing the ROM? Not wiping when moving between ROMs can cause a lot of random bugs.
yeah, i did!
although i used Clockwork
Now i've been reading that there are better recoveries for whipping stuff..
I use same Radio 12.56.60.25U_26.10.04.03_M. And i am able to install all roms without issues. BUT! Yesterday i updated to latest US MIUI and i lost sound in phone speaker and MIC. After plugging in headphones i was able to hear from headphones, and use internal phone mic. Try to flash some clean rom like virtuous g-lite or sense 2.0.0. Or if u want to use CM, try to flash other kernel.
There is an issue with a lot of Android devices where the OS thinks the headphone is being plugged in and unplugged on its own.
I have rooted 4.0.4 AOKP and it still occured.
Search for this FREE application (no ads) to fix it: Wired Headphone Routing Fix
dmwoods said:
There is an issue with a lot of Android devices where the OS thinks the headphone is being plugged in and unplugged on its own.
I have rooted 4.0.4 AOKP and it still occured.
Search for this FREE application (no ads) to fix it: Wired Headphone Routing Fix
Click to expand...
Click to collapse
Tried the app and I still can't hear the person on the other side. I really wished it worked. Or maybe im using it wrong or something..
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
kozij said:
Hi guys, I have a strange problem and I couldn't find any Qs and As to it in the forum so I thought I'd post it up and see if someone can help me figure this problem out.
I was running EliteMod and out of nowhere this problem arose.
Whenever I put in my headset the phone would become unresponsive/frozen, and on the odd occasion it would work, but after a few minutes would randomly restart.
I thought it may have been the rom so I flashed another.
I'm now running Cyanogenmod 9 ICS beta 10 and the problem is still apparent.
I'm at a loss of what it could be.
Any help would be great.
Cheers
Edit:
I should add that when I reflashed Cyanogenmod 9, I put the headphones right at the start when setting up a fresh google account on startup, still the same result. Which is why it has me so confused. It came up at random, and a fresh flash won't get rid of it.
Click to expand...
Click to collapse
I had this same problem for two different reasons with two different phones.
The first time, which seems unlikely for you, was a problem with DSP Manager that comes with CM9 causing my phone to crash and restart.
The second is manufacturer error. The phone has a titanium case, and due to some errors in assembly, when I would plug in headphones, the system would freeze and restart. Because I still had warranty, I had it replaced and the problem disappeared.
If you have a multimeter there are ways to check for a short, but I'm not sure if you are familiar with this.
Hope this helps!
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
blutooth
Sent from my HTC Vision using xda premium
kozij said:
Ahh I see.
I guess that would make the most sense... a hardware fault.
I'm out of warranty so I guess no more music via this phone.
Thanks for the advice
Click to expand...
Click to collapse
If you still want to try and find a solution, get some electrical tape (or another strong insulating tape) and cut off a thin strip lengthwise (about 0.8-1cm width x 3-4 cm length) and tape it to the top of the headphone plug on your headphones so that it blocks any contact with the titanium.
demkantor said:
blutooth
Sent from my HTC Vision using xda premium
Click to expand...
Click to collapse
I use a pair of Bluetooth headphones and a Bluetooth-enabled car radio. But alas, if you care a lot about your sound quality, then Bluetooth certainly is *not* the way to go.
But if you care that much about audio quality, you would have a dedicated device which uses all it's processing power for playback, right?
I'm currently running Re-Calked.E4GT.0.2.1.FI25. For the most part everything is solid, and getting some of the best battery life I've ever gotten out of the phone (24 hrs with ~2hrs screen time no problem if in a good signal area).
The one little problem I'm having is any time I finish a call using my in-car bluetooth device, the screen blacks out for a while then I get a message saying Com.android.phone has stopped.
The device is still connected to bluetooth (music starts streaming again, etc...), but if I try to make another call, the dialer won't enable bluetooth (a lot of weirdness about finding a bluetooth device when you tap the bluetooth button on the dialer UI). A hot-boot puts everything back again the way it should be until my next call. This happens 100% of the time on bluetooth, never on a regular call - speaker or otherwise.
I don't think it's Re-Calked's fault, I've experienced the same problem on the stock ROM (FH25). It was fine on FH13, and I'm fairly certain FI03 was good too, but I got dismal battery performance on these kernels.
Any suggestions? This is a real downer for me ... I'd hate to have to try an older ROM since everything else is effin' fantastic! (BIG thanks tdunham!!)
UPDATE:
If anyone else runs into this problem, flash the FF18 Phone from THIS POST (thanks tdundham)
The problem appears to be related to the phone being in landscape orientation, which is only available during a call when docked in a car dock.
I'm using the Official Samsung Vehicle Mount
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Edit: It would help if you could backup and flash back to FI03 to verify if the problem still exists on that version.
tdunham said:
Wish I had an answer for this for you but...
I've seen several frustrated posts concerning Bluetooth pairing with vehicles on ICS with no clear workaround/solution. I don't have a vehicle with onboard Bluetooth to troubleshoot the issue. I bet it's a doable fix too if it's just a matter of porting over some older library files or something from FI03. Maybe we can experiment with some file replacements to see if we can get it working.
You listen to music over Bluetooth too? I wonder if the media player is conflicting too somehow. What happens if you don't have streaming music and recieve a call?
Click to expand...
Click to collapse
Actually it's not a built-in bluetooth. It's a "Belkin Bluetooth Car Hands-Free Kit for Apple iPod, Apple iPhone, BlackBerry,and Android Smartphones, US Version" ... search for that on Amazon ... tried to post a link, but I'm too much of a noob to post links yet, apparently.
I have the phone in a Samsung windshield mount, and the Belkin device ports all audio through the aux-in jack of my car stereo. It also has a built-in microphone so that I can use it for calls.
I have experimented a bit to see if it was a conflicting app, but it still happens even if I'm using nothing else. Worked fine on the older kernels, even with multiple apps running (Car Home Ultra, Waze, and Play Music are typical) went wonky as of FI25. I even tried disconnecting it from the dock and disabling car mode. The only thing that causes it is being connected to bluetooth and ending a call, and then it happens every time. Doesn't matter if I initiate the call or receive it. (Which is useful, because I could easily test by calling 611)
I wish I had another Bluetooth device to test if it was specific to the Belkin ... but that's all I've got.
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
tdunham said:
No problem. I live out of Waze. Glad I found the fix for the full navigation voice cutoff for that (and Google Voice) and included it in the FI25 rom. I'll look into posting a couple of flashable zips for you to experiment with for the Bluetooth library files.
Click to expand...
Click to collapse
Thanks for that ... can't wait to try. Going to flash your new Re-Calked update soon too.
On a tangent regarding Waze ... did you install the latest update? I can't stand the way they use 30% of the screen with that black bar ... even worse when you get close to your destination and that other menu bar pops in above it. 50% of the screen covered with useless info.
I rolled back to the prior version from my Titanium backup.
I only used Waze this morning once after the update but didn't really check it out.
Backup your phone.
Flash this first - FI03.flash.first.zip
Test bluetooth, if it isn't working move on...
Flash this second - FI03.stock.lib.zip
Test bluetooth. Even if it is working, flash this next. FI03.stock.lib.zip
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
romgnascher said:
Very cool. I'll give it a shoot tomorrow at lunch if I get a moment.
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yeah, don't forget to backup first.
Sent from my SPH-D710 using xda premium
So, it looks like I was wrong with my initial investigation.
I did flash the first file ... everything connected fine. Placed and disconnected a call no crash. But what I DIDN'T do was put the phone in the car dock.
So, I think the problem isn't bluetooth at all. I think it's some interaction with the car dock. If the phone is connected to the car dock when I disconnect the call ... that's when com.android.phone crashes (I can start the call connected, just need to disconnect before I end the call). I also had a suspicion that Car Home Ultra might have been a factor, but it happens even if Car Home Ultra is not running. I thought I had tested this scenario originally, but I guess I missed that one.
I'll flash back to my nandroid later and reconfirm these results. In the mean time ... any thoughts on what the car dock might be doing to trip up the phone?
UPDATE:
Now that I've narrowed it down to the dock, I found this bug report that appears to be related to my issue (yay, I'm not the only one):
http://code.google.com/p/android/issues/detail?id=34612
Down the end of that thread, it appears that the issue seems to be related to the phone being in portrait mode ... not necesserily the dock, it's just that you can only get portrait mode during a call when docked.
Just curious. Does your dialer rotate when docked so you can make a call?
Anyway, I sent you something in a PM check it out.
Edit: I'm working on one more thing to add to that. Give me a little while.
Cool, I'll look at it afterI get the kids to bed.
Yes, the dialer rotates in the dock. Also, when in a call, the contact's photo is also rotated and moved left.
Sent from my SPH-D710 using xda app-developers app
Ok we're running out of choices I guess. Try this older stock dialer and if that doesn't work, I guess that's it for now.
Thanks for your efforts whatever the outcome!
I'll flash this tomorrow and see how we go.
I just flashed the new Re-Calked update by the way. No problems, good stuff and it's been idling at around 1.6%/hr.
Changing out the phone did the trick!
OP updated with resolution.
Sent from my SPH-D710 using xda app-developers app
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
Cool, I'll look at this one too. Have an answer for you by lunch time.
tdunham said:
Hold your horses there cowboy.
That is a totally unmodified phone.apk. Let me upload a modfied one you can try too. This one is FI03, disabled ascending ringtones, roaming notification fix. Might be something else too but I can't remember.
Click to expand...
Click to collapse
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
romgnascher said:
So I tried that phone. Crashes on disconnect just like the others. Back to the FF18 phone and it works like it should.
Click to expand...
Click to collapse
That's fine, as long as we got it working for you.