Database Info

CM7 Lockscreen/Ringtone Issue

Hey guys. I installed CM7 over the weekend and am sporadically getting issues when receiving calls. Occasionally I get what, more or less, sounds like an odd ring/alarm sound over my set ringtone. This issue isn't a big deal in and of itself, but when it happens, the ring/alarm sound continues on through the call and both the person who made the call and I can hear it. This results in me having to end the call and call them back. I never have this problem when making calls and it doesn't happen all the time when receiving. The way the lock screen stutters when it happens makes me think it has something to do with it but that's a wild guess.
Is anyone else running into this issue? It's happened twice since I installed CM7. Everything else seems to be working great btw, it's nice to have this rom out. Just thought I should make this post since I doubt I'm the only person with the issue.
Also -- I don't use any ringtone apps or sound software at all other than whats on the rom.

There's probably a hundred posts about this over in the fascinate forum for this rom. I have been running CM7 for a few days now and haven't had this happen. I don't get many calls tho. Check out the fascinate development thread for more info on this.
Sent from my SCH-I500 using XDA App

Ahh. I should have done some searching over there considering it's a port. My apologies - thanks for the heads up!

Possible Bluetooth Fix G2x - Works so far

Okay.. I know. This is my first post, but don't use that to determine the validity of the information.
I've been on here for months, just didn't have anything useful to contribute until now.
Switched from rooted Gingerbread MT3G to G2x - was pretty excited till the bluetooth issues set in.
Didn't have the random reboots like everyone else. I think that happened once in my pocket... not thing to write home about there. This damn bluetooth was killing me though. Like a bad toothache badly in need of a root canal. Every time I picked up the phone I was reminded how beautiful but flawed this is.
So my search began. Poured over LG forums, T-Mobile and Google searches, compiling information. It became clear that this didn't seem like a hardware issue. The crappy Andriod 2.2 shipped with the phone was the issue. To me it seemed like this wasn't fully tested before shipping. Has sold tens of thousands of these phones and were largely unaware of the issue - the techs were surprised when the reports came in - mainly from US based customers on T-Mobile. In my quest I stumbled across an app that reported to fix a similar issue on a few other phones and gave it a shot, and it worked. So real simple here you go:
1. Root your phone, if you haven't already done so. I did with a heavy heart. Was waiting to do so but this issue was driving me nuts.. I used these scripts to Mac and Linux (I'm a unix guy):
http://forum.xda-developers.com/showthread.php?t=1048309
2. Download, from the market, and run, the following app:
>>>> Bluetooth Fix Repair <<<<
That's it!!
Here's what I did to test:
a. Left headset on, power cycled phone
b. Left phone on, power cycled headset
c. Out of range disconnect on head set, then moved back in range - successfully placed call.
d. Received call from a fresh connect, force range disconnect, then reconnect - successfully received call.
e. Disconnected headset from phone menu, then reconnected, placed call successfully.
f. Left headset and phone on for hours, multiple disconnect/reconnect - successfully placed calls.
I'm using a Blueant Q1, with the Blueant app from the market - BTW.
All seems to be well so far.. Give it a shot

fix the a2dp on gb and i'll give you your first donation.

What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!

donbeth said:
What were the issues you had? My bluetooth seems to work fine, except the volume seems low and of course it helps to drain the already short battery life -- sorry, don't mean to be adding another battery rant!
Click to expand...
Click to collapse
My battery life is fine. Lasts the whole day and then some. Check the running apps and kill the unnecessary tmobile apps and anything else that you don't need. Another way to save battery is to drop the data rate down to 2G. Settings --> Wireless & Networks ---> Mobile Nets --> Use 2G. I know, defeats purpose of having 4g, but it works fine for email and IM.
Bluetooth issue:
Bluetooth disconnects and doesn't reconnect. Only way to resolve is to power cycle phone. Sometimes it would indicate that it was connected where it wasn't. Multiple folks have the same issue. Doesn't seem to matter whether it's a headset or car bluetooth.. same issue.

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
Wish I had the time to get into the ROMs. Don't know how you guys do it..

Returned the original G2x today and got another. Well, bluetooth is jacked on this one also. You know, I shouldn't have to be messing with this damn thing I paid $300 for. It should work.. The right thing for T-Mobile to do is recall the G2x and replace it the new dual core nexus for affected users. This phone is a piece of shyte.

The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.

jlevy73 said:
The BT fix was short lived My bluetooth must have disconnected half a dozen times today. Very frustrating.
Click to expand...
Click to collapse
I have a Blueant Q2 that collects dust because it is useless trying reconnect it every time it disconnects (far too often) while I'm driving, what's the point? Bluetooth is a fail on the G2X.

So the damn bt issue is still not resolved.
Sent from my Sensation using xda premium

ICS fixes the BT issue... but how? And can it be done for previous versions too?
I have tried the ICS CM9 and it seems to fix this BT issue. Not sure how it happens. Can one of the developers comment and maybe implement the fix in their ROM as well?

crazythunder said:
fix the a2dp on gb and i'll give you your first donation.
Click to expand...
Click to collapse
It works in the SK ICS builds.

I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).

mansa_noob said:
I know it is an old thread but would like to share my experience here.
My only desire was to have the bluetooth not disconnect without announcing the disconnect. I saw this issue in GB 2.3.3 and below and saw it fixed on 2.3.4 and above, only to see another issue (no mute via bluetooth) crop up.
I have, however, by sheer luck and burning hours at it managed to fix it for 2.3.3. Haven't tried to see if it fixes the mute problem yet. I am satisfied with Weapon G2x 3.0 R1 .
Here is the link to my post. http://forum.xda-developers.com/showthread.php?t=1590523. Note that you will loose everything in the internal SD card so be prepared. It seems that the disconnect problem has its root in another partition (other than /data, /system and /cache). I have been problem free for almost 3 weeks now.
Will try with 2.3.4 and above later to see if the mute issue gets fixed too .
Try at your own risk and post results as you find. The reference thread in the post can be used to create an out of the box G2x with T-Mobile ROM so no chance of bricking (I believe this phone is unbrickable ).
Click to expand...
Click to collapse
Wow you dug up deep for this. I believe this is the time we didn't have a2dp on cm roms
Sent from my LG-P999 using xda premium

All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.

SovereignKnight said:
All these new roms are amzing however, Hellfire Sandwitch and Pheonix both have this damn Bluetooth issue. I go to make a call and no sound comes to the bluetooth except some static and then it goes away. I hear nothing. I switch to speaker phone and I hear the dialtone on that. What the heck is going on with the bluetooth on these roms? Both ICS and GB share the same problem. I'm using that fix posted on the forums that makes any rom work with the new march 2012 BB update.
Click to expand...
Click to collapse
check the irl too?

No haven't done that. Not sure how you mess with the irl. I know it has something to do with baseband. But I don't think it has anything to do with Bluetooth?

[Q] can't hear other side in conversation.

hey,
I bought the nexus s (9023) about two months ago, stock rom, not rooted, and for the last week or two, it started making problems.
about 1-5 times a day, i can't here the other side at all. as if it's on mute. not even the ringing tone, before I'm answered. the only thing that solves it, is to restart the phone.
in other forums i've read that it's a mess, and that i should use my warranty. the problem is i bought the phone abroad, and shipping it should take about 3 weeks.
is it a common issue?
can i solve it alone, mabye by switching to a non-stock rom?
i'll be very happy to read some good news here, but bad news is better than non.
thanks a lot,
tal
p.s, iv'e downloaded system info to monitor the temp, and it doesn't happen necessarily when the phone is hot.

I don't know... I am rooted, I have used 5 different roms since purchasing my phone.
Stock
CM 7
Savaged Zen
Oxygen
Soju
I have also used several kernels
CM Stock
Netarchy
Matrix
James Bond
Trinity
So far, on all roms and kernels I have experienced the same problem. You make a call and it connects, looking at the screen the time counter is going but there is no sound; it will sit there and hold the call for 30-55 seconds then ends call. A quick redial and bam it works. Some people have reported that they answered and there was nothing. I don't know, it's really obnoxious.
The other, more annoying problem is that randomly on calls throughout the day the phone will just reboot itself. Right in the middle of a call. AHHHH like 3-5 times daily!

help, anyone?
i'm stuck with this, and a bit clueless.

Well, somehow I discovered that the problem is related to the bluetooth. as long as it's turned of, nothing will happen, on the other hand, when I use my earphone (most of my conversations happen while driving) i need to restart my phone every 1-2 calls
any ideas?

just u can't hear other one while calling u?
thanks.

so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.

tal89 said:
so it was in the beginning, but now neither of us can hear the other. no matter who made the call.
and again, only when BT is working.
Click to expand...
Click to collapse
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App

it's quite obvious, unfortunately it doesn't work.

cutiyar said:
If u can hear him,just press and then unhold it ,then u can hear him.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
i can't hear, and he can't hear as well.

tal89 said:
i can't hear, and he can't hear as well.
Click to expand...
Click to collapse
hehee its problem ,
am really disappointing with nexus s , but i dont have enough money to buy HTC product again.

any solution?
Hi, did anybody have any solution to this problem?
I live this problem on almost half calls of specific numbers.
I am desparate...

Try setting discoverable timeout to never? Have you tried a different Bluetooth device?
Sent from my Nexus S 4G using xda premium

I have this problem too. This seem to happen on some Kangs and nightly, but not all of them. I can't hear when someone calls me. But when I call someone, I can hear them. I always have Bluetooth off (do not use them).

I live the same problem. No problem for outgoing calls. For incoming calls, I cannot hear caller's voice but they can hear me. It is not for all numbers.
I am on t-mobile and nexus s (cynagenmod nightlies). For all incoming calls from tmobile numbers no problem. But for almost all other carriers, it is just random.
I feel like I started having this problem after updating from CM 7.0.2 to 7.1 RC and thereafter(but not very sure on this).

If anybody still following this topic, I would suggest you to contact samsung if you still have warranty. On the second attempt they sent me a brand new phone with box and accessories.
Sent from my SGH-T989 using XDA

Or, you might give it a try with a different radio for your model:
http://forum.xda-developers.com/showthread.php?t=1116884
If you go this road, make sure you backup your EFS folder.

What i would do is if it is still in warranty just give it back to them and they'll probably give you a new phone. Since you said it takes 3 weeks to ship, just wait for it and use another phone if possible. Its not like your life is going to end. I think the problem is, not every phone is the same so there will be problems especielly when flashing a rom. For example unstable roms might not allow you to use this app or have serious effects on your phone.
Best to give it back to samsung and get a replacement.

Really confused! Audio drops during calls

Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!

are you running any special ROM or anything because its happening to me as well

I have been having the same problem for almost a month now. I was rooted when this started happening. I went back stock still happened. New 4g card still happened. Another phone still happened. I have been getting the runaround from verizon the whole time they have no clue what is going on.
On a side note asked a friend that works at a little vzw store if they have seen this problem and sure enough she had. She told me that they had a customer go through 4 phones and she started making calls and was told by Customer Support that it was a known thing and there was a software update coming out for that.
After hearing this I called good ole *611 yet again and they were clueless and said they knew nothing about it. *sigh*
¿GotJazz? said:
Something very weird just started happening with my SamChg.
When I am a few minutes into a phone call (about 3 - 4 minutes), all audio drops out on both sides of the call. The call is still connected, but neither side hears anything anymore.
I did a factory reset on the phone, but it didn't make a difference.
What can be causing this? If I can't use my smartphone as a phone, I'm screwed!
Click to expand...
Click to collapse

What rom ???

Yorto said:
What rom ???
Click to expand...
Click to collapse
Umm can't even remember now was a month ago LOL. But my 2nd phone I didn't put one app on or anything left it bone stock and still had the same problem. Same as the customer my friend had they would mess up right out of the box.

probably weak antenna

no you don't lose signal call keeps running you lose Audio.

chiahead52 said:
are you running any special ROM or anything because its happening to me as well
Click to expand...
Click to collapse
Yorto said:
What rom ???
Click to expand...
Click to collapse
Yes, I am running a custom ROM, but it's basically a stock rooted & voodoo'd EE4 ROM (by danalo1979, I think). It's got all the yucky poo-brown colors and all the bloatware.

Same issue here. I'm running completely stock right now, non-rooted. Sometimes the audio will drop at the onset of placing a call (I won't even hear ringing) and sometimes it will happen a few minutes into a call. Other parties do say they can hear me though.
Personally, I've noticed that this problem only happens when I am also connected to a Wireless Network. If I'm running 4G/3G, sometimes I hear echos of my voice, but the audio won't drop out.
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
What should we do? Personally, I'd like to wait for the SG2 to arrive before I start complaining. My plan would be to basically flip out explaining that I need my phone to work like a phone, etc. Then flip out that I paid for 4G and my decision was battery based (so I don't get stuck with a Thunderbolt). I bet I could talk my way into a new SG2 over this... Just saying.

KarateExplosion6 said:
Weird, but glad to know others are having this issue and that VZW is aware it's happening.
Click to expand...
Click to collapse
Well they do not tell me they know what is wrong they tell me they have no clue. I even explained to them somebody there does know as they have explained the issue to someone else that has had the problem but I still get they you just need another phone speel.

I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1

kvswim said:
I don't have this problem watch as soon as I try to make a call the audio drops...
Sent from my Droid Charge running GummyFroyo 1.9.1
Click to expand...
Click to collapse
same, don't have this problem but i probably just jinxed it.

I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?

Edvard_Greig said:
I've had this happen a couple times too...hard to pinpoint consistency. The other thing I've encountered more than once, is that my mic seems to go off mid-conversation, e.g. I can still hear the person on the other end very clearly, but they can't hear me. Anyone else experience this?
Click to expand...
Click to collapse
I've experienced that. But I'm not so sure I'm not just covering the mic with my finger.

I was on nluetooth, with the phone in the cupholder... Don't think my finger was involved.
Sent from my SCH-I510 using XDA App

Well 2nd Fru and as I told them it would. It does the same thing. Bone stock. *sigh*

One thing that seems odd to me is that I seem to see this problem more when calling another mobile phone vs. a landline.
Maybe it's just my imagination, but I always see problems when calling my wife's mobile phone. Last night, I called a landline for over an hour without any problem.

same here I can talk to customer service for 1hr+ but mobile to mobile most Ican get is maybe 15 min.

I drive around as part of my job and today I tested a call out to my wife who has a charge as well and we were able to talk for over 20 minutes with no issues. That same area I drove through a few days ago caused 3-4 drops in audio before. So in my opinion its a network related issue and hopefully its get fixed 100% cause most of us need our phones to work solidly

To the people losing audio during their calls, can you post your location?
The reason why I ask this is because on the Verizon forums there is an eight page post about this issue. Seems like a lot of people in Arizona are experiencing this. I'm in Chandler, Az and have this issue, especially when calling other VZW people in AZ.
Can't post links yet but check the VZW community forum for the Charge.

[Q] 2.3.4 Speaker Phone Wifi Calling Issues

Hello all!
I am a noob on here so if this has been asked or brought up before please forgive me. I couldn't find any info on this issue. After installing 2.3.4 on my sensation (I am running stock out of the box) I notice when I connect the phone to wifi and use wifi calling that when I use the speaker phone on my phone, the person on the other end can no longer hear me. The person just says hello over and over and totally cuts off the mic on my phone. When I enter it back to the regular headset, it continues to be cut off. When I try troubleshooting the issue I connected to the t mobile network it works just fine. Only when I use the wifi calling feature does this happen. Does this happen to anyone else? Is this a known bug? I did a battery pull and this did not fix the problem. Any suggestion or feed back would be much appreciated. Thank you everyone!

Not one person is having this issue? Can anyone help out there? At least let me know if it is a known issue. I know the speaker phone is terrible but I'm only trying to find out if there is a fix for this.
Thanks!

HTC Sensation Speakerphone does not work on WIFI
I am having the same issue. Speakerphone does not work over Wifi. Person on the other end cannot hear me and I often cannot hear them. When I am not using Wifi, speakerphone works fine. Version 2.3.4 seemed to improve speakerphone volume, but it still does not work over Wifi. I contacted HTC tech support and they said while they were unaware of the problem, but it is possible that it exists. They said they would investigate. We will see. Not sure whether the HTC Amaze has the same problem.

I had the same issue till I S-offed and flashed a new ROM. I think it's something with TMO's factory ROM they have the speaker function turned way down and my first Sensation would do just what urs is.
Rec: Unlock (S-off) and flash a new ROM (I personally am running CoreDroid 2.4)

I'm on ARHD 3.6.2 and non speaker phone works ok, but on speaker I've been told its hard to hear.

I am also having a same issue. I've opened up a ticket with t-mobile. T-mobile techs are looking into this issue. Yesterday I went to the store from which I purchased my sensations and showed them the issue. We tested the issue with other HTC android devices but only sensation is having this Issue.

I noticed this problem a couple months ago, and am surprised there hasn't been a software update to fix it. In the meantime, I just shut off wifi if I expect to make a phone call using the speaker phone, which is somewhat annoying.