Database Users

Phone won't properly switch from vibrate to sound

at&t 8525 owner, here.
So, I've had this issue for a little while now after I flashed Shadow TE ROM. But it's continued since then... so here's the issue:
I go into work and turn the phone onto vibrate. After I leave work, I switch back to sound on (ring & vibrate). Even though the icon shows the sound is back on, it's not. It only vibrates. It acts as if the speaker is still asleep.
So for awhile I'd have to reset my phone every day to get it working again until I realized I can go into sound settings / notifications and I find that the phone's jumped back to the default ringtone and more than that, I have to literally push PLAY to test the sound in order for the speaker to "wake up" if you will. Then the phone's fine until the next day.
Ok so back to present:
I got fed up and thought it was Shadow TE. So I flashed CRC's v9.2 ROM. Still had the same speaker issue! I was advised to flash a shipped rom.... which I did.... and flashed CRC's v11. Issue still remains.
I've searched the board and could only find one other person make mention of this a couple years ago and no one ever addressed it. Does anyone have any suggestions? I'd appreciate it greatly.

Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.

nonegiven said:
Same problem here with a custom Titan ROM. Installed the same software as every other ROM that I've used so the problem must be in the ROM somewhere.
Click to expand...
Click to collapse
Could be... but why does no one else seem to have this issue? Wouldn't there be tons of people replying here?
I did find that instead of switching it to vibe when I arrive at work, I switch it to silent... and SOMETIMES when I go back to Sound it works ok for a few hours but then it goes back to silent without warning so I miss calls and texts a lot. Might as well force the sound back on through Notifications Menu anyway. I'm SO getting away from Windows Mobile ASAP.
As soon as the Blackberry Bold is released here in the US, I'm buying it.... unless something about it disappoints me, in which case I'll settle for the iPhone 3G. The Bold can't come soon enough.
Who would like to claim this Hermes when I'm through with it? What are you willing to pay?

Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.

nonegiven said:
Try making sure that your ringers are in the windows\rings folder. Saw it somewhere else and it seems to be working.
Click to expand...
Click to collapse
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.

cozbaldwin said:
Hmm... I tried putting them in, like, 4 places... but none of them seemed to be that location. I'm doing it now and I'll test tomorrow. Thanks for the tip.... i hope it works.
Click to expand...
Click to collapse
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...

cozbaldwin said:
Sorry to report that this didn't help.
C'mon AT&T... release the Bold.... let's get this thing released already...
Click to expand...
Click to collapse
Don't know what to tell you then. Make sure you're not running any 3rd party software.

[Q] Time Issues

Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?

Okay, An update
This is happening when I reboot the device.
Is there something in settings that I am missing, or is there a registry setting I can change?

do you have your "date & time" settings set automatically?

Yes
bleui said:
do you have your "date & time" settings set automatically?
Click to expand...
Click to collapse
Yes time setting is automatic, even tried setting it in the registry.
It got that bad yesterday my phone reset itself to Jan 1980.

It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?

h0ng said:
It sounds like the battery *may* be ****ed up, I have no idea about the htc hd2 (I've only had mine for a couple of months), but on my old phone(s), some of them have had that "time resetting" too, and the people at the tech support said the battery needed to be replaced.
Sorry for hijacking your thread:
I have a similar error with my phone (yukixda v4):
If I send myself a text message at say... 01:35... it's sent 01:35, but the one i recieve has the timestamp at 01:34... this is both with and without automatic time settings..
any ideas?
Click to expand...
Click to collapse
Truth is no matter what is causing this... TWO big issues for me when choosing a phone software set up.
The phone knows what freakin time and date itis
The phone nor the software on should destroy batteries
but thanks guys it really was fun to play with.

Don't use automatic, mine does the same if I set to automatic.
I thought it was something with Giffgaff as I would set automatic and the time would be right but later on during the day it would be some crazy time and date.
Set to manual and your clock will be fine

dunno about any of that but, i do know that if i boot in to MAGLDR is gets buggered up, doesnt matter if the time is manually set or auto set, it always buggers up, dont boot to it and all is good
, at least for me anyway

I'm having the same issues. Time and sometimes dates getting screwed up. Only started happening to me about a couple of weeks ago now. But it's frustrating at the least. I've switched mine to manual setting at the moment. Gonna see how it goes over the next week.
One thing though, it isn't happening to my wife's HD2. She is using the older version of WP7, I'm currently on Yuki's more recent NODO version...

as per my post above yours if you use magldr or even the bootloader it gets messed up, so dual booting droid may be a reason, or using bootloader / magldr to charge, other than that i dont have this issue

Not got dual-boot on my phone, neither do U boot to magldr to charge... But it's happening to my phone every few days so far. Today it was out by 28mins. I want to see if having it on manual time/date does any better...

i also have a problem with my hd2,
9 times out of 10 when i reboot the phone the time and date will be wrong with no pattern i can spot (started to do this out of the blue- no updates or new roms).
im currently running with a cooked win mo image and android on the sd card.
battery still has a respectable life although seems to run out quicker than it once did so i may purchase a new one. (the old one is just over 12 months old)
also my phone has started to freeze on pin request after receiving a text so im gonna try a new image too
if anyone else has seen problems like these and solved them drop a noobie a helping hand pleeeeaaasseeee....

It's not HD2 related
The same issue happens to me (phone jump approximately 36 hours foward randomly)
The phone was a LG Optimus 7 on official rom but never managed to fix this issue (automatic date or not)

ForgetfulGuru said:
Hi guys and girls,
Been using WP7 about a week now and one niggling little issue is doing my head in. Sorry if it has been mentioned before or is covered under some other issue, I did try a search and got nothing relating to it.
My issue; the clock on the phone keeps jumping to random times.
I am using YukiXDA latest build and could find nothing relating to this isue there either.
Would like to know if others have had this problem and what have they tried to remedy it?
Is it a ROM issue or is it a hardware issue?
Click to expand...
Click to collapse
I have the same issue! It happened some months after flashing xboxmods v. 1.11 Rom. It can't be a battery problem because I use 3 different batterys ^^

[BUG] Other person can't her me mid-call, mic gets muted

Hi,
in the last days with my S3 on every call I had which went for more than 1 minute the other person suddenly couldn't hear me anymore. Sometimes it happened after a minute, sometimes after 3 minutes, but in the last 4 calls it happened every time!
Reception came back after some seconds and from then on it was really bad, the other person had hard problems understanding me.
I searched around and found this thread of GNex owners having the same problem:
http://androidforums.com/samsung-galaxy-nexus/472451-vzw-other-person-cant-hear-me.html
Then I found it in the Issues DB too
http://code.google.com/p/android/issues/detail?id=24019
Do you guys know more? it is really bad, since this is my business phone so nearly every call is an important one and it really bugs me out.
Anyone having same problems?
I hope someone can help me out.

Yes I have the exact problem. It's driving me nuts and I've tried different roms and kernels.
Sent from my GT-I9300

Have you tried to DISable the noise canceling feature?

No but I will try it and report back.
By the way I'm on stock LF6 4.0.4 in Germany (with o2 as my carrier. Unbranded. )
Is the noise canceletion buggy?
Sent from my GT-I9300 using xda app-developers app

I've read that some kernels cause issues like this.
Also, in UK, in Birmingham on Orange, I have been having issues like this, and it usually occurs when the Signal Switches over from Orange to T-Mobile, mid call, and once onto T-Mobile signal, the call breaks up or goes quiet.
Maybe an issue switching from 2G to 3G or back mid call also?

BobFL said:
Have you tried to DISable the noise canceling feature?
Click to expand...
Click to collapse
Will try also. The only reason I haven't got rid of this phone is it mostly happens on o2 calls, I am on giffgaff which is run by o2, The op is o2! Hmmm
Sent from my GT-I9300 using xda app-developers app

just yesterday I again had the issue....and my noice cancelling was off...so this is not causing it....
I'm bumping this in hope someone has a cure.
The new rom LFB is not yet published for Germany but for UK. Perhaps it makes a difference? Can somebody in UK with LFB who previously had the issue please check?

Same problem, no solution
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).

the-0ne said:
I'm facing the same issue. Tried searching for any possible explanations, but haven't found anything conclusive.
I've tried disabling and enabling noise cancellation and all combinations of the in-call options.
There are 2 or 3 main theories which I've encountered:
1. The microphone goes to sleep when the phone display does. As soon as someone seems to not able to hear me, I move the phone away and the screen wakes up. This seems to sort it out temporarily.
2. Someone had posted on FixYa indicating that they tried putting a small piece of cotton after removing the back panel just behind where the mic is. Haven't tried this!
3. Everyone else seems to think that a factory reset would set it right. I haven't tried this as I need to find a bit of time to do this.
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Which ROM are you using right now?

Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.

Try this for a fix
goto settings
sound
Toggle on then off or off then on the screen lock sounds then try again :good:

the-0ne said:
Also, I'm wondering if flashing to CM9's RC1 or 2 will sort out the issue. I'm thinking that it has to be a software glitch. In fact, someone reported that they solved it this way (can't remember where).
Click to expand...
Click to collapse
Hey,
just so you know. I am on CM9 and I have kind of the same issue. Sometimes audio is unidirectional, both ways actually, unable to recreate it so far. What always seems to work is my bluetooth headset. Switiching between the two of them makes me lose audio entirely. I have tried many things, even rebooting the phone Sometimes it helps, sometimes it doesn't. I'm guessing it has something to do with BT.
I am NOT facing the issue with losing audio in the middle of the call when the display goes to sleep. The display goes to sleep because of the ligth sensor, btw. - not because the system is idling The display is not needed once the phone realizes it's attached to your ear (lights off).
It's driving me nuts
BUT: CM9 is amazing so far. It's fast, it's open, everything works just fine. Except for the phone as a phone of course

change modem

Oomahey said:
Which ROM are you using right now?
Click to expand...
Click to collapse
Using Stock right now. OTA updates till Jun 26th.
badaeng said:
Ihad the same issue on CM9 and got rid of it by flashing another radio. I originally had the xxlef, tried the xxlfb and ended up with the xxlf5 which works fine so far.
Click to expand...
Click to collapse
Mine's currently DDLF3
winwiz said:
Toggle on then off or off then off the screen lock sounds then try again
Click to expand...
Click to collapse
I've just tried this, will report back. How do you think lock sounds affect the mic, though?

avetny said:
change modem
Click to expand...
Click to collapse
Does CM9 come with an integrated modem switcher? I don't like messing around with "packages" too much. The more you mod everything, the less stuff has got to do with each other and it is more likely to run into trouble, because as a developer you can't really consider every side effect
So if this is actually about the modem (which I doubt, because the connection is just fine, it's just the audio output and input that is kind of broken) - what modem would I use with CM9? Can I just flash a random one over the current one?
Appreciate the advice.
Andreas

I notice that as soon as I take the phone away from my ear and the screen lights up I can again be heard... Wonder if there's a problem with the light off sensor affecting the mics too... It ALWAYS goes away when I remove the phone from my ear and the light sensor allows the backlight to come on again...
Might be a crazy thought but the evidence does seem to support this. I haven't turned off the light sensor in settings yet, if I even can, but was going to try next call...

I updated to BLG8 and I will see tomorrow if it happens again. Today I already had one call which lasted 11 minutes without interruptions. I will report as soon as I got more calls to test.

I had the same prob...
I just reflashed the official firmware frm the service centre.
Sent from my GT-I9300 using xda app-developers app

Same problem here. Tried several roms, kernels and modems. Only one working for me is Checkrom v3 with xxlbf... but here also after a while some calls it reappears... I reflash modem and I am set for the next couple calls... then again
Ps: i am from Romania on Vodafone
Sent from my GT-I9300 using xda premium

I'm the OP and I now didnt had the problem for 2 months with the last stock ICS build.
It seems to be resolved.
I'm now on JB since today (XXDLIH) and will report if it comes back.

[Q] Phone is frozen after a call

So I switched to GB from WM65 and found it's pretty slow but usable. I don't have time to switch back to WM65 so I'll stick with GB.
Now, one big issue I have is the phone app (not wifi app, just plain phone). When I dial a number, the screen goes black to prevent pressing the wrong button with your ear etc. Problem is, I can't get back to the screen, meaning I don't have access to the dialpad. Annoying when you're on queue and you need to press a key to get to a menu... like repeat a message on your messagebank for instance.
Second issue, is after the call, the phone is frozen for about a minute or two. Nothing responds. Then it comes back alive.
I haven't found any threads on this, though users seem to complain about wifi calling, which is not my case.
Anyone has seen this ?
Txs.

Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.

I had this problem with almost every gingerbread build on my HD2.
Im not sure what's causing it, but i fixed this issue by installing screebl lite from play store. While this app enabled, phone would wake up normally after a call in 99.9% of the cases. You should try the same.
Strangely, i don't have any issues on ICS or JB roms.

Marvlesz said:
Can you please tell us which ROM that is?
I know that this issue was fixed, but maybe your ROM is just too old. Or maybe the developer didn't include the fix.
Click to expand...
Click to collapse
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?

Boags said:
Android Version 2.3.7
Baseband Version 15.42.50.11U_2.15.50.14
Kernel Version 2.6.32.15_tytung_gb_r16 [email protected] #292
Build nr GWK74 (nexusHD-Gingerbread V3.3a) DataOnEXT
Got it from this dude http://forum.xda-developers.com/showthread.php?t=905060
So there is a patch ?
Click to expand...
Click to collapse
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.

Marvlesz said:
Okay, I have looked throughout that thread's pages, and it seems that you're not the only one with that problem. So apparently the ROM doesn't have the fix (which is weird, because tytung almost always fixes everything in a rom before moving onto another one).
You're better off changing the ROM, or maybe trying to figure out what is wrong with your device and those who're facing the same issue.
Click to expand...
Click to collapse
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|

Boags said:
Thanks Marv, so...no hotfix ? no patch ? just change ROM ? this is silly :|
Click to expand...
Click to collapse
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.

Marvlesz said:
Well, the fix wasn't a flashable zip, it was implemented. It was a problem with the proximity sensor if I recall correctly. And since I don't use this ROM, I can't really help you much.
I tried googling the problem (it's fun, you should try it) and this came up : http://forum.xda-developers.com/showthread.php?t=1376251
Your sensor/screen could be dirty making it hard for the proximity to detect. You can try another non-GB ROM and see if the problem is still present.
I am sorry I can't help.
Click to expand...
Click to collapse
Right, I'll go with the hypothesis that a dirty screen hinders proximity sensors. That should affect a black screen DURING a call (issue I'm also facing) but that should not affect the phone once the call is terminated, should it ? What I mean is, in my case, when I hang up a call, I can't use my phone for a couple of minutes, until it comes back to life. I will get a new "screen protector" and see what happens in the meantime though.
As for a hotfix, seems odd there is none out there. Thanks for trying.

call log ( missed calls) not working after root.

I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?

Me too!
Bam9 said:
I had recently had my phone flashed to the best carrier for the area im in ad noticed a few problems. im rooted with cm11 but sticking with the stock debloated rom. the carrier flash had actually cased some issues initially with the screen turning on and fully lighting up, but when i started flashing new roms that issue was fixed. I thought it had fixed all my issues, but as I found out yesterday, my call log is still completely null and void. it shows no calls in or out, and ive made plenty. but the bigger part is that I dont even know about a missed call until I get the voice mail notification. ive tried apps to record them but im guessing they work off whatever stock files control that and thy read nothing as well right now
has anyone had this problem or possibly know of a fix?
Click to expand...
Click to collapse
I am also experiencing the exact same issue. Rooted Vzw g2 on page plus. I've searched phone for a log file that looks like it corresponds to the call logs but no love. It is a little obnoxious as I have no idea who calls me if I miss the call.
Have you found a solution?

me, too!
Any insight?

I've not found a thing that will help us, I've found others experiencing the problem, but no solution. I'm running a stock debloated rom and i think therein lies the problem. Something that was removed that was seen as bloatware is most likely what actually tracks the call log. I've been searching for a rooted bloated stock rom, but to no avail. I ran a few other roms and had a call log, but the roms overall sucked and i like the ui of the stock especially the camera app....I'll keep looking, but hopefully someone in the know sees this post and helps us out

I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..

I am running through the same issue, no recent and missed call history, my messaging is fine. The G2 was rooted and flashed to PP. I am wondering if you have solved the problem, if so, could you please share your solution, very much appreciated.
Bam9 said:
I was flashing different stock roms and differet Gapps and whe it boots into the backup scree to set the phone up the number it was showing saying my sim was already set up wasnt actually my number. I dot know where or why the number was coming from. but alas, my call log worked ad on called id's it still showed up as the right number. so i began puttig all my stuff back on it and updating things and something i updated chaged that and now im back where I was without a call log.
i dont know what files i had flashed excatly, so now its just a guessing game and lots of flashing..
Click to expand...
Click to collapse

same issue
I am having the same issue. I flashed to pageplus, rooted and installed xdabebbs rom. I dont see call history in my recent calls app. Please let me know of a solution

No solution yet, see someone say it could be because of flashing, so how you do the flash, yourself or someone help you.

Find out solution, simply reflash NAM only, i used DFS.

same problem here.
@gjbwj what for you mean reflash NAM?
Running VS982.5 ROM if it maters.
Pretty sure it was something I restored with TiBU that caused it. My wife's phone has the same ROM but I didn't restore anything but apps on her phone.
I would rather not have to start over for what should just be one file corrupted.