Hi all,
Friend and I both have the Incredible S, loving it! He has a slight issue and I can't for the life of me solve it. Everything was working fine but now when he has an incoming call and the screen is off the incoming call screen flashes up briefly then disappears and device shows normal 'desktop' - you can't answer the call!
If you call his phone and the screen is active, incoming call screen pops up as expected and you can answer call.
Any ideas peeps?
Thanks
Ant
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Sliphorn said:
Hmmm,
I'm having the exact same problem. Running Fresh Evo on HTC Evo. Would love to know why this is happening. Any ideas?
Click to expand...
Click to collapse
Never worked it out, friend did factory reset in the end to fix it.
Ant
Bummer. Here's some info:
Latest Fresh EVO
Rom Manager
Rom Manager Janitor
Juice Defender Ultimate Juice
Titanium Backup Pro
Cachemate for Root
ShootMe
Adfree Android
adbwireless
Call Control (problem before this, though)
Launcher Pro
Any hints?
Having the same exact issue. This sucks... This started today for me around noon ( no calls before then), and has persisted throughout the day. Yesterday was fine.
I use Google voice for all of my calls.
The only thing I've done today that I haven't done every other day was that I installed the Gtalk app this morning. In the past, I've used Gmail directly. However, my computer was off during at least one of the phone calls I received today, so I can't imagine this could be it...
Perhaps because I installed gAlwaysIdle (an addition to Gtalk that makes you never go idle or always be idle) as well?
Does this correspond with anyone else's experience?
I'll probably just reflash my phone
<Rooted Atrix 4g running GingerBlur>
hmm this sounds like a serious firmware problem tho..
all i could suggest is flash a firmware that the most of the ppl are using, and dont got probs with...
well doing a good reboot seems to help alot these days. So disable the fastboot option en turn it off, wait a while (10 secs should be enough) en start the device again.
Also had some of the trouble like crashing things and this solved it for me. Give it a try and hope it will fix it.
Otherwise there seems to be no other way than a factory reset (go htc!)
Related
Hello, I've recently set up ActiveSync for 15 minute intervals during peak time. I set "Vibrate" for New E-Mail Messages. Usually it vibrates for a few short bursts, but at least once per day the vibration motor freezes up and won't stop vibrating until I press the power button. The only other recent change to my settings was that I installed Bandswitch to keep connected to the Edge network and disconnect after 120 seconds. I don't know if this change is related to the vibration problem. Anybody have any suggestions?
if you have Magic Fingers installed, you might try uninstalling it
thanks for the advice, but I don't have Magic Fingers installed
hey. weird cause i used to have the same issue before, my phone whenever it received an email it would not stop vibrating until i removed the battery. lol weird i know. r u using the stock rom? ever since i changed rom's from stock i havent had that problem before.
try flashing ur rom to an upgraded att or htc rom, maybe it would solve ur issue as it did to me
best of luck
I have the exact same issue with incoming emails. For now I have turned off notification. Configuration is pretty generic.
This happened to me...
This happened to me once with the stock ROM. I have since upgraded to the leaked AT&T Tilt ROM and it hasn't happened since.
Any Hints?
MadMatt- Any hints about where to find the "leaked" ATT Tilt ROM ?
ATT Leaked ROM
benmorris said:
MadMatt- Any hints about where to find the "leaked" ATT Tilt ROM ?
Click to expand...
Click to collapse
Here you go...Hope this helps.
http://forum.xda-developers.com/showthread.php?t=341886
One more
I also have this problem, but its not with every e-mail. I receive between 10 and 20 e-mails a day and the continuous motor only happens about once every other day. I'm also on the stock ATT ROM. Anyone figure out what's going on with this?
emmit said:
I also have this problem, but its not with every e-mail. I receive between 10 and 20 e-mails a day and the continuous motor only happens about once every other day. I'm also on the stock ATT ROM. Anyone figure out what's going on with this?
Click to expand...
Click to collapse
I'm glad I'm not the only one.
this issue is a bummer
oh yeah this is becoming a real pita
Me too...
Using Blackberry connect on stock ROM on Tilt, new messages occassionally cause a constant vibration until I hit the power button.
Would love to know how to stop this,
ncdave
In my experience I have found that this is caused by the device being forced to do something, i.e. check email, recieve email, before the device is fully "awake". The solution for me was acheived through the use of kaiser tweak. This also means there's a registry mod. for it as well, unfortunately I left my Kaiser at home today. If ylou change the device wake up to something more acceptable such as 15 seconds or 30 seconds instead of the 1 second default you may find this fixes your problem as it has for me!
If you did that, wouldn't you stand the chance of missing most of your phone calls while the phone is sleeping?
Hi all,
Sorry if this has been noted as one of the bugs with the official 6.1 upgrade, but after a bit of searching I was unable to find anything. Everything seemed to be fine until a couple hours ago. I was at work and hence had not used the phone itself for a while. I was setting up my email accounts again. then a hour or so later, the phone started vibrating for a notification of new emails and would not stop. I had to do a reboot. Now, every time I try to place a call, it uses the speakerphone, and will not switch back no matter what I do. I hit the button for speakerphone and there it says it has changed, and the icon in the status bar on the top also changes, but it still uses the speakerphone. I've not tried with my bluetooth in my car yet to see if that is working ok...
Any suggestions? This is a real problem for me and one that I need an answer to sooner rather than later.
Thanks in advance for your help.
Solved - the problem was with SRS Wow HD audio driver
Just FYI - incase anyone else is having the same problem.
I worked backwards and unintsalled each program I had put on one by one and tested the phone. Turned out that I forgot I had installed SRS Wow HD sound driver. Once I uninstalled that and rebooted, everything has worked fine since.
Sad that this does not work with 6.1 as it was a really nice piece of software.
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Funny you mention this, because I'm having the same problem. I thought it may have been a tweak I'd done and was going to do a hard reset today.
The only cab I've installed is Microsoft MyPhone. And had to edit the reg to allow the changing of the notification light timing in the Sounds & Notifications settings.
Do you know if this happens before you've made any changes to settings or installed any software on the phone? I don't recall having any problems like that myself with Timor installed, but I'm also not sure I received a text in that time. I haven't tried the other ROMs you listed.
It seemed to happen after I edited the reg settings.
Doesn't seem to be a constant occurance though. I happened to me 12 hours ago, even after a soft reset. But now I just sent a test message to myself, and all is ok... weird
Well I've regularly installed My Phone, Marketplace, Bing, Groovefish, and MP3 Trimmer, but I'd rather not delete and hard reset everything to do a test if someone knows a fix
I haven't had this issue...I am using the Valkrie Firestorm 5 and even when my phone is sleeping my phone vibrates as I get SMS messages and emails...
Well I have hard reset and held off installing using the My Phone. Everything seems well with recieving on time...but now the screen turns on everytime i get a message. It didn't used to do that and I find it quite annoying..I looked around my settings and Advanced Config and couldn't find anything.
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Me too...
I thought it was the result of all the hacking, tweaking and breaking I've been doing on this flash since I've been using it as a "scratch pad" but the problem you are all describing sounds identical.
I will also second the Home screen suggestion. Hit 'End' after you are done messing with the phone to go back to the Home screen. There is definitely a notification bug related to not alarming/vibrating when not on Home screen.
Though I have observed this issue, this does not completely explain my problems. Sometimes I don't actually even receive the SMS or MMS until the next day or after rebooting my phone! Most of the time it's fine though. I'm going to do a clean flash and see if that gets rid of that issue.
Same Here
I have run across the same problem with a number of the cooked ROMs. I never really noticed the problem with the stock ROM though. In my experience some of the cooked ROMs are having a problem handling the text messaging. I have over 3000 text msgs in my backup and as soon as I try to view an older text, the systems tend to lag and freeze up to the point that I need to soft-reset. Im using Athine right now and so far it has handled the text msging just fine without freeze or lag, but it also seems to have the same notification delay bug that the other ROMs have.
dwarf said:
It happens in the stock HTC rom too.
It normally doesn't happen if you come out of the text messages and go back to the home screen after you reply to someone. It's a really annoying bug
Click to expand...
Click to collapse
Yeah I'm familiar with that bug. But I go back to the home screen 99% of the time then shut the screen. I'll get a message and the LED will start blinking, but only when I turn the screen back on will it ring and vibrate.
Same problem here with the cell pro rom
ftmoe said:
Hello,
I've been having a problem with a few of the custom builds (Timor, AthineOS, CellPro Evo), and one problem I've noticed with each of the ones I've used is that when I get a text it doesn't notify until I wake the screen back up. Once I do that it vibrates and rings, but its up 30min after I got the text. Is this a known problem with a fix or am I better off sticking with a stock ROM?
Thank You
Click to expand...
Click to collapse
I have the problem with almost all of the ROM. Does anyone know if it could be a result of not using the right radio?
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
nackas said:
I could be wrong.. but I don't think it has anything to do with the radio. There doesn't seem to be any problem is receiving the message from the carrier, it's more-so the OS not notifying. This has only happened to me since trying the new WM 6.5.5 builds with Sense 2.5. Previous to these builds I have never had any issues, and only used EnergyROM with a COM2 build, and Sense 2.1
Click to expand...
Click to collapse
Im not sure about all the technical stuff your talking about...I just know that on almost every ROM I flash, when the phone goes to sleep, they seem to not do anything. Its only when I wake it up do I receive text messages, notifications and the weather doesnt update on its own in the prescribed time its supposed to according to the settings I have selected.
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
steviewevie said:
The radio version may affect the quality of your reception. So if you have no reception then that will obviously delay texts getting through, and stop you being able to get to the weather servers. But I can't see why it should have anything to do with delayed notification of texts that are already on your phone.
I realise this might not help you much, but on my EnergyROM (see my signature for full details), my phone gets texts fine when it's asleep.
The weather isn't designed to get automatically updated when your phone is asleep though. There was a recent thread on how to change the registry to make it do so, if you haven't done that then your weather stuff may well be acting correctly.
Click to expand...
Click to collapse
Awesome...thank you so much for the information and help
This is the thread about getting weather to update automatically - http://forum.xda-developers.com/showthread.php?t=585373
WHY DONT YOU JUST USE A ENERGYROM????? I dont have any issues with those roms and i just updated to the .88 radio. no issues as of yet.
I upgraded my Captivate to gingerbread/talon/continuum yesterday.
That went fine and everything was hunky dory.
Phone was working fine the whole day today, incoming/outgoing calls, data.
I came home and installed Skype and thats when all hell broke loose.
Now the phone part is dead (kinda!). I can make calls fine but if I get a incoming call, the call gets disconnected after 1 ring and I get a msg popup (like some error) but I cant really see what the message is.
I also noticed that it disconnects me from ATT network when a call comes in and then after a little bit it reconnects.
I also verified this by going to the About->Status screen and then making a call.
It normally says ATT but for a couple of secs after call drop it says 'Unknown'.
What did I do to screw it up and how can I fix it?
Thanks
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
mommehK said:
Glaring obvious first question -- did you try uninstalling Skype to see if that resolved anything?
mK
Click to expand...
Click to collapse
Sorry, I should have added that to my first post.
Yes, I did uninstall Skype and reboot the phone, just incase, but no difference.
Still the same.
Update:
After playing around with various things for a couple of hrs, I finally gave up and reflashed Continuum.
Everything started working again.
Applied my Ti backed up config and loaded Netflix. Same problem. Dialer died with an incoming call.
I reflashed Continuum again and everything started working as expected.
I then applied my Ti backup, still everything working.
I am in the process of updating all my apps and then lets see if everything is still working.
The only thing that is missing for now is the Netflix app.
I will keep everyone updated if its the Netflix app causing the issue or its the Skype.
activemind: Keep us posted if you find a cause. I am on a Samsung Vibrant (3g) via TMOB but have been having the same issue today with a completely different rom (simply honey). This is actually about the 6th thread I've found in the past two days having this same issue on Galaxy S phones.
I have had this problem before and what caused it was restoring system data with titanium. Make sure you are only restoring apps.
Sent from my GT-I9000 using XDA Premium App
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
tigane1 said:
I just recently decided to root my phone shortly after changing providers from t-mobile to family mobile which is run through t-mobile but cheaper. I figured fresh start all around right?
Well I rooted it, put cm10-or-10.1 linaro on it (forgot which) did some v6 supercharging (had no idea what I was doing, probably shouldn't have bothered) and everything was fine except when I would receive or make a call the phone app would freeze up and at times I could hear the person calling inbound but they couldn't hear me. I could call them back okay though. I figured I'd try a different rom, it didn't help. Now when I make outbound calls the screen freezes in the transition from pressing call to the screen it displays during the call, then the screen shuts off which I assume is the proximity sensor kicking in and then I can either turn it back on and the screen displays correctly or the hardware key lights come on but the screen stays black. Upon hanging up it just sits on the during call screen with everything grayed out for about 10-20 seconds before it finally goes back to home.
So far I've been through: the stock rom, peach sunrise, cm10 linaro and cm10.1 linaro and none of them have been error free. Is this a hardware issue that can be addressed? I've searched around for a topic similar but with no real luck. This is the closest I could get http://forum.xda-developers.com/showthread.php?t=1293442 and they seemed to come to the conclusion that it was an internal memory error.
Click to expand...
Click to collapse
Try aoip its up to date and works good.
schuylkillparanormal said:
Try aoip its up to date and works good.
Click to expand...
Click to collapse
working on downloading it but the download keeps failing -_-
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Mwas. said:
When switching Roms second, third and .... times, did you do a rom wipe?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Yes rom and cache/dalvik. And if I forgot I went back and wiped and re-installed it.
tigane1 said:
Yes rom and cachredowvik. And if I forgot I went back and wiped and re-installed it.
Click to expand...
Click to collapse
There's nothing wrong with the link try redownloading the ROM something might of got corrupted.
I fixed it. Kind of
I did a bit more searching using some different terms and people were having trouble with the proximity sensor on their phones causing similar problems so I turned mine off and the problem corrected itself! So now I guess I just have to deal without having a functioning proximity sensor during calls, oh well, not a biggie. I appreciate the help though guys.