Related
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.
Well, thats it, I actually can't pick up my phone when I get a call. I can push the green pick up button as many times as I want, but it wont respond, and I end up having to call people back. Anyone else with this issue? (phone info in sig)
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
I agree with Neobbs although when I first read the subject, I thought maybe you needed to work out more....
Same problem here. I can have the phone in my hands looking at it straight up when the phone rings and the phone goes black for about 5 seconds (or about 2 rings) and then the caller id comes up and I start hitting the call/talk button to answer. It goes to VM eventually and me hitting the green button ends up bringing up the recent call list. Auto rotate is disabled, but I do have weatherbug, open home, caller lookup and IM running in the background. Oh... and I have the transistions/animations enabled. That's all i can think of. I'll try removing the caller lookup app to see if it eliminates the problem.
hi,im running rc33 stock rom on bronze tmo g1 in singapore..it happened many a times,even on a cold boot up..wonder what is the actual problem here,mine is not rooted at all..
screamsoflust said:
hi,im running rc33 stock rom ....wonder what is the actual problem here,mine is not rooted at all..
Click to expand...
Click to collapse
why in the world would you do that? (j/k)
bhang said:
why in the world would you do that? (j/k)
Click to expand...
Click to collapse
huh?what do you mean?
screamsoflust said:
huh?what do you mean?
Click to expand...
Click to collapse
he means.. why would you not root your G1???
I think it's a good, fair and valid question.
Do you have installed a customer ring tone ? if yes, choose original ring tone and try again.
I had the same problem when I started using my phone. I dunno what changed but the prob. has disappeared or I got used to hold the pickup button down for a bit longer automatically. I got the feeling that this helped the issue.
My phone is RC33 not rooted... and to answer you question: I've tried but I'm still fighting with my XP to accept the USB driver.
Guess again!
neoobs said:
I am only going to take a guess and say that you have a lot of programs that run in the background.
Maybe try not using auto rotate.
Click to expand...
Click to collapse
mine does the same randomly. Straight after a factory reset.
nothing installed, and my G1 is not rooted (yet).
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
n3rdftw said:
has anyone found a solution for this problem?
Using RC33 with weatherbug running in the background, but it occurs with it installed and without it installed
I swear, the G1 must be the worst phone ive ever used
can't wait for the touch pro 2 now...
google can't release polished software if their lives depended on it.. selling a beta phone is just bs
Click to expand...
Click to collapse
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Meltus said:
Yep, must be terrible if about 4 or 5 people have this problem out of the thousands who have bought it....
I've never had any of these problems, but im guessing they're (probably) firmware related.
Click to expand...
Click to collapse
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
n3rdftw said:
most probably just call back and arent bothered to find out how to fix it on xda
anyways, when you say firmware related, what did you mean?
I installed JF 1.42, and before that, his earlier versions, and way before that my phone started out with RC18, which I then rooted. Would it be linked to that? I've wiped my phone like a dozen times, but the problem is reoccurring perhaps once or twice a day, out of about 30 phone calls a day
additionally, although this may be linked to t-mobiles ****ty service, have you guys noticed a large increase in dropped calls?
I use my phone in both austin tx and houston, and in both locations, about every 10 calls is dropped, I dont know if its just the horrible service they have, or when I move from a location with 3g to edge.
With the new radio, the dropped calls have reduced in number, but still occur randomly
Also, one more thing, and a little off topic, but this has been bothering me,
Is there anyone to get a SMS application that allows me to type using a numpad or something similar on the screen? or at least, have spell correct, cause chompsms' keyboard is way too small to use one handed and still have legible messages, unlike the iphone where the errors would be auto corrected
Click to expand...
Click to collapse
I'm in austin, tx too and I also get the black screen of death almost every time I get an incomming call so maybe it is a location based thing? My g1 is rooted and I have over 70 apps installed and I'm not about to uninstall them 1 by 1 to see which one could be causing it. In the past, rings extended was said to be the one causing the problem but I don't have that installed.
Also, there have been enough requests for t9 and auto correct with chomp, I'm sure it will be in the upcomming updates
Im running Haykuro now and haven't had a single incident so far. Also, I have 73 (yes, seventy-three) MB of free system memory as I moved pretty much EVERYTHING to the SD card. In return, my phone is unable to boot without my SD card... which is a bit strange.
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
It's network related. They better pay this months bill for you. Call Sprint and find out.
Sent from my PC36100 using XDA App
I've had a similar problem lately of not getting calls. I'm not missing all of them, but at least once or twice a day, all of a sudden I'll get a nerw Voice Mail, yet the phone never rang. And, I've had people tell me that when they call, it goes straight to Voice Mail
I just attributed it to having WiFi only on, although that is just a longshot guess on my part.
Ive been unable to receive texts girl 3 days now. Anybody find a fix?
Sent from my PC36100 using XDA Premium App
what rom? if it's calkulin's evio 1.8, there's your problem.
Cm7 final
Sent from my PC36100 using XDA Premium App
dkdude36 said:
what rom? if it's calkulin's evio 1.8, there's your problem.
Click to expand...
Click to collapse
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
dschoenike said:
what's wrong with that Rom? damn, now that I think about it, I ran that Rom and realize my problems started that day. is there a reason why that Rom caused my no calls/texts issue.
Click to expand...
Click to collapse
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
dkdude36 said:
yea. when calkulin upgraded from 1.77 (great rom) to 1.8, he added a bunch of ## codes directly in the menu. but somehow the defaults were messed up. i had this problem too. it affects any rom you flash after. just full wipe and reflash calkulin's, then get your msl from msl reader, and go to the dialer. then type ##data# and select edit. make sure mode of operation is on auto. then, DO NOT OPEN SETTINGS. just power off phone, and flash something else (maybe even calkulin's 1.7.7.)
Click to expand...
Click to collapse
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
dschoenike said:
thank you for that. sorry if this is a stupid question, but will getting a new phone solve my problem? thanks
derek
Click to expand...
Click to collapse
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
dkdude36 said:
i have no idea. i'd try this first, and if it doesn't work, a sprint tech might be able to fix it.
Click to expand...
Click to collapse
wish i woulda asked you guys earlier i unrooted, went back to stock, spent 4 hours in a sprint store, now have a different evo coming in from sprint on tuesday. guess ill try what you said tomorrow before doing the exchange. cant today as im not home. thank you again for all that info. really appreciate it.
derek
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
JoshuaD80 said:
@OP
the problem isn't with your phone, it's with your account. i ran into this a few times while i worked for Sprint, and there for all the issues that came up, the only fix was to delete the account from the network in its entirety and start from scratch. sometimes there's just some corrupted code that no level of tech support knows how to do anything with that just needs to be re-written.
i'm surprised that they ordered you a new phone even though using a different device didn't work. i think it was just a move to make you feel like they're doing something for you tbh. make sure that your line is comp'ed until the problem is resolved. you could probably get your whole bill paid, but you're more likely to get half of it (i'm assuming you only have two lines) covered. my recommendation is don't get greedy, just ask for your half.
goodluck!
Click to expand...
Click to collapse
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
dschoenike said:
thanks for the info. yeah, only two lines on our account. I'm not gonna be greedy seeing as I'm the one who caused the problem (flashed the rom) I just want a working phone now I'm real curious to how long that's gonna take. I'm mean if its my account, a new phone won't solve the issue right? could take Sprint awhile to figure this all out. grrrr. and its all my fault.
Click to expand...
Click to collapse
i'm not convinced it's your fault at all. sometimes funky things happen in the back end on sprint's side.
best of luck to you!
don't think this is a rom specific issue, it's most likely the network.
I'm having the same problem on savage-zen rom rc2...
What may help is updating your radios, prl, etc. I haven't done that in a while, not too sure that it will make a significant difference though.
dschoenike said:
greetings. about a week ago, I noticed I was missing a lot of calls, and not receiving texts. I can call out and send texts, just cant receive anything. well today I had enough and took it to the sprint store. after 3 hours of them working on it, still nothing they went as far as trying my number on a different phone, and even that phone couldnt receive calls then. (never rings). lastly, they gave me a new phone number for my evo, and still cannot get calls. so, I along with them are super confused. is it my evo or the number that's bad? they ordered me a new phone to pick up on Tuesday, but I'm not convinced it'll work. anybody have any idea what on earth could be wrong? I'm running pure stock. oh yeah, Google voice doesn't work either for getting calls, but it can receive texts. wife's phone on our account works just fine. so weird. thanks guys.
Derek
data over 3g and WiFi is working perfectly.
Click to expand...
Click to collapse
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
just letting you know, the pri is different than the radio, and we are talking about evio 1.8 starting problems like this for many, including me.
nucher said:
I had the same problem running Evio 1.8. I tried a number of things (including different ROMS) but what seems to have fixed it was to reflash the radio. I reflashed the PRI 1.77_003 from this thread http://forum.xda-developers.com/showthread.php?t=715485&highlight=radios and my phone has worked fine ever since. Once you're in recovery (amon or clockwork) flash the zip (PRI 1.77_003) and reboot. It will flash the radio and reboot. It might solve your problem.
Click to expand...
Click to collapse
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
dschoenike said:
so do u think its worth rooting again, and trying all that, or wait till I get the different evo and see how that goes? to be honest, I didn't want a different phone. I really liked this one and do you think them giving me a new number affects any of these trouble-shooting efforts? thanks.
Derek
Click to expand...
Click to collapse
If you have the time I would try my suggestion and or dkdude36 suggestion. He is correct in that the PRi is not the radio. I was in a hurry to type out the message. But I do mean the PRI, and I use the 1.77. You'll have to root the phone again, and nan-unlock. Then install a ROM and a recovery. If it doesn't work you'll have to restore it to stock before you return the phone so it will take some time to do all that. I was running Evio 1.8 for a while then one day I couldn't receive calls. I tried many things but the PRI fixed my phone. It's really up to you and how much time you have.
calkulin's evio 1.8
dkdude36 i think is right, i had the same problem a month ago, had to call *2 for help.
want ah guess what rom i was running....evio 1.8!
now i'm on Eternal Prophecy 5.8 got to read the hole thread, zero bugs!
Hello xda, I have this strange issue on stock touchwiz lollipop. I understand that when the phone is on LTE, a switch needs to be made to 3G in order to receive or make a call, and the phone automatically does that.
What my issue is, when i receive a call, the network changes to 3G but it actually takes a while before my phone starts ringing, whereas on the caller's end the phone is already ringing. In other words it takes the caller 2-3 rings before my phone actually starts ringing. I dont think its a modem issue because this issue doesnt exist on CM 12 or any other non-touchwiz based roms. Any ideas?
P.S. i did use search, did not find anything similar to this.
P.P.S. it would also be great if someone could reproduce this issue and confirm.
I would still try to change the modem and see if it changes anything. Besides that I have no clue.
Lennyz1988 said:
I would still try to change the modem and see if it changes anything. Besides that I have no clue.
Click to expand...
Click to collapse
Tried different modems too.. Sadly no avail. Can you reproduce this?
TheAwesomeBit said:
Tried different modems too.. Sadly no avail. Can you reproduce this?
Click to expand...
Click to collapse
No I cannot. I'm running CM
Lennyz1988 said:
No I cannot. I'm running CM
Click to expand...
Click to collapse
oh yeah i should have realised. Hope someone else replies soon!
Hello guys. I have proble with my p7000 and incoming calls. Sometimes the incoming call just bug whole phone. I can't recieve the call and I have to put out the battery. It's really annoying. And also, I don't see who called me in call history. I've made factory reset, but it didn't help. Also I updated my firmware to the version 20150807 but this bug is still here.
Absolutely same problem has man on this video. /watch?v=c588Clm67ME
Please help me.
/Sorry for bad English/
I had the same issue, try the November update from Stock or the Miui rom (the new one, not the one created the day the phone was out), I didn't had the glitch with those 2. I'm trying to know from what that problem come from but I'm far from being an expert sadly. That problem is on all the stock roms except the first and the one from November. All the roms based on stock got that issue (even those based with the November update strangely !?) so I guess it's something related to the voltage or something...
leomon32 said:
I had the same issue, try the November update from Stock or the Miui rom (the new one, not the one created the day the phone was out), I didn't had the glitch with those 2. I'm trying to know from what that problem come from but I'm far from being an expert sadly. That problem is on all the stock roms except the first and the one from November. All the roms based on stock got that issue (even those based with the November update strangely !?) so I guess it's something related to the voltage or something...
Click to expand...
Click to collapse
Thank you. So do you think, that ROMs like cyanogenmod doesn't have this issue? I almost can't use my phone... Today it happened to me again, but not on incoming call, but on alarm clock. So it has to be something with sound/soundcar/voltage of reproductors or something like that.. I am not expert so I am not sure.
filipusfikus said:
Thank you. So do you think, that ROMs like cyanogenmod doesn't have this issue? I almost can't use my phone... Today it happened to me again, but not on incoming call, but on alarm clock. So it has to be something with sound/soundcar/voltage of reproductors or something like that.. I am not expert so I am not sure.
Click to expand...
Click to collapse
The best is to test it. First install TWRP then make a backup of your current rom then install that rom : http://bbs.elephone.hk/thread-8425-1-1.html#.VlyDufkvdhF and see if that problem occur again. Personally I had no issue with the November rom for the P7000 so I'm staying on that one for now, even the root doesn't mess up anything... If that occur with alarm that might be a problem with the sound board/card then I had the same issue, when I get a call, the sound was looping, screen staying black, had to or remove the battery or long long press on the power button.
Hope that will help you !
PS : The november rom is here : http://bbs.elephone.hk/thread-9111-1-1.html#.VlyFPPkvdhE but you need a working flashtool for that one (you need flashtool for a custom recovery too anyway).
solved - cant receive incoming calls 4g'
I know this is an old thread but I have just had this exact same problem and after WEEKS of googling and determination I have found the fix to this problem..
I'm posting it because as I was googling I found that there are still hundreds of people experiencing this today.
HERE IS THE SOLUTION!
Dial *#*#4636#*#* on your phone..
Then scroll down and you will see a small down arrow next to "Set proffered network type"
Choose LTE/GSM/CDMA Auto (prl)
Also, you might need to check one other thing.. On the same screen go to top right ":" drop down nav menu settings shortcut and "Select Radio band" - do this if the 1st change hasn't fixed your incoming calls problem.. You can experiment with AUS, AUS2 or Automatic etc and try again.
I was about to throw this new Elephone S3 back to China but it's all great now
Hope this helps someone
Shakir