Related
I have the Verizon Touch Pro2 and recently upgraded to Windows Mobile 6.5 using the official release.
I saw someone else have this problem (he posted a video of the issue) but I cannot find if he found a solution.
Normally, if you press the top button, the blacklight turns the device's backlight on or off. If off and you press the Power button, the device tells you "Backlight is off. Press button to turn on." and points to the top button with a little green arrow.
Well, something is wrong with mine. When the backlight is off, pressing the top button does nothing. The problem is intermittent and very frustrating.
Now the device is not locked/crashed because the power button will bring up the message. Also, if I call my phone, it comes up. If I txt my phone, it comes up. If I plug my phone into my computer via USB, it comes up. But pressing the top button doesnt make it come up.
I've flashed the phone 3 times to try to get rid of the problem. Originally the phone had the 6.1 stock Verizon ROM. I have not ever try to load a custom ROM on this phone. I have no special software installed on the phone. I am not using the Sense interface, I'm using the Windows Default.
Please help! & Thanks to all you gurus!
I've only noticed this problem when my device gets too hot, so try to keep it out of the sun/heat. I've been on Mighty Mike rom for the past week and have had no issues.
i dont think its the heat..
burtonsnow8 said:
I've only noticed this problem when my device gets too hot, so try to keep it out of the sun/heat. I've been on Mighty Mike rom for the past week and have had no issues.
Click to expand...
Click to collapse
i have not noticed any heat issues. the problem has occurred both when the device was plugged in and not plugged in. in rooms with temperatures from 68° to 76° F and never in direct sunlight..
i think the problem has something to do with email.
i have it setup to check my yahoomail via imap. its downloading messages from years ago, even though its been setup to do only the past 30 days, how is this possible?
ive seen it say 2000+ new emails on the today screen, and dating back to 2003 the last time i was able to turn the backlight on via USB, the yahoomail account was in a perpetual disconnecting... sometimes erroring at being unable to synchronize at all..
also the error reporting service has told me that "tmail.exe" keeps crashing.. im assuming its crashing cause its getting overloaded with too many emails.. can any provide some input?
ive deleted the yahoomail account for now and will see if it happens again..
update
almost 24 hours later, no locking up. device is running smooth.
i fear that the issue is related to the email problem.
it downloading 2000+ emails must have been it.. im assuming
has anyone else had the backlight issue? and have you found it may be related to email?
im going to wait 2 more days and re-add the yahoomail account and see what happens.
That is very interesting. Have you tried using seven for your mail?
http://www.seven.com/
almost 48 hours later..
burtonsnow8 said:
That is very interesting. Have you tried using seven for your mail?
http://www.seven.com/
Click to expand...
Click to collapse
no ive never heard of it.. it looks like id have to join a beta to get it for my phone..
and although i enjoy the idea of using something that works i dont like just giving up on the whatever is wrong with the software.
and...
almost 48 hours later the phone has not at all locked up.. i fear the issue is directly related to whatever it was doing with my yahoomail account.
the settings were: imap yahoomail, html, 2kb, 30days, no attachments.. i think thats all thats relevant.. and it was downloading well over 2000 messages from as far back as 2003
im going to add the mail account back tonight to see what happens..
simplyvega said:
no ive never heard of it.. it looks like id have to join a beta to get it for my phone..
and although i enjoy the idea of using something that works i dont like just giving up on the whatever is wrong with the software.
and...
almost 48 hours later the phone has not at all locked up.. i fear the issue is directly related to whatever it was doing with my yahoomail account.
the settings were: imap yahoomail, html, 2kb, 30days, no attachments.. i think thats all thats relevant.. and it was downloading well over 2000 messages from as far back as 2003
im going to add the mail account back tonight to see what happens..
Click to expand...
Click to collapse
Since you mentioned it I was mulling it over...I really think you are onto something with that mail message, because the two times I did that I had a message waiting.
Seven should be free, I've posted the cab below.
Same thing with mine...
I've had the same thing happening with my TouchPro 2. I found a quasi-work around that helps limit the number of freezes, but it sure increases the number of pocket-dials I make. In the advanced section of the power settings deselect the "turn off backlight if device is not used for" box. Then decrease the "turn off device if not used for" box to 1 minute. I'm still getting really good battery life (lasts all day) and it's not a new battery.
I sure hope there's some sort of update or fix for this issue soon, because this is only a work-around.
Backlight issue on Verizon
I was having the same problem. I do not know if you have mobile email installed. I did. I removed it and so far so good. You will have to hold the back light button for about three seconds sometimes but it always works. No more soft resets. The only issue is that you have to contact Verizon and have them stop the text notifications from OZ Mail. The way Mobile E mail works is the third party software company sends a text which you never see because mobile email software gets it and uses it to give you the notification that you have new mail. Tech support had to create a trouble ticket in order to stop these text messages. Every time I got a email I would get a text from OZ mail with about 20 something alphanumeric numbers. SO far so good!
I had this problem with mine and it appeared to have something to do with my 3.5 audio jack... it was like it thought there was somthing plugged in there but there wasn't. as soon as i plugged in my headphones the screen came right on...
update - and semi-isolation
so after days of not having my yahoomail account configured, and my phone not locking up once, i added it back with the following settings:
imap, 7days, 2kb, no attachments. (the original issue occurred with similar settings, only 30day past messages and not 7)
it worked for a few days, then when i was leaving work today i took my phone out of my locker and noticed the backlight was on. an alarm had gone off.
then i looked at yahoomail and it said i had 2000+ new messages.. the first message dated from august 2008
i turned the backlight off. when i tried to turn it back on it worked. but later in the evening it did not. it hung like it was doing when i started this thread. and it was in the process of "downloading headers" for hours. upon clicking "send/receive" to make it disconnect, it sat on disconnect for a long time, without doing anything.
something is clearly wrong with yahoomail or perhaps simply the imap service
who should be contacted? someone at verizon?
isleepinabucket said:
I had this problem with mine and it appeared to have something to do with my 3.5 audio jack... it was like it thought there was somthing plugged in there but there wasn't. as soon as i plugged in my headphones the screen came right on...
Click to expand...
Click to collapse
i noticed my screen coming back on this evening when i got out of my car. i have bluetooth set up from my car deck to my phone for audio streaming and hands free.. it automatically connects when i turn the car on and disconnects when i turn the car off. upon disconnect the phone usually displays an error saying that the hands-free device has been disconnected.
it looks like the phone will respond when any kind of event happens (ie plug/unplug of headphones, phone call, txt message, alarm, etc..) so whatever the hell is wrong the phone is not actually crashed, just the backlight wont respond to the top button..
What your describing bis not new... nor is it limited the the TP2 or HTC phones. Commonly referred to as "failure to wake" or "sleep of death" (do ba search). Potentially effects all WinMo devices.
Frequently attributed to programs running in the background as the phone goes into sleep mode. By Programs, this could mean an active applicationyou initiated, a system program running invisibly in the background or an event that creats a notification while the phone was asleep.
Workaround is similar to what you've already tried: Extend the amount of time it takes for the device to go to sleep (+ve found 3 minutes sufficient, allowing for more time to multitask with multiple programs running).
Try not to put the phone to sleep with known programs running under the task manager.
Use Lumos to conserve battery life, since youre possibly keeping the device on for longer periods.
Keep availible RAM using a RAM cleaner and clean up duplicate notifications. I use MemMade for both.
This is a software issue and the circumstances are descibed in Microsoft's documentation for software developers. They test for programs that contribute,or create this problem before they go into the marketplace.
Sorry for the typos. In class banging out a hasty responce.
I've been having the same issue too, intermitantly maybe twice a month. I can't find any pattern.
I use Google Latitude, Batti, and I sync email every 30 minutes (Exchange to my univeristy, and IMAP to AOL) but I also have my computer set to download messages and erase messages after 2 days so I never have more than about 100 messages to sync.
WM 6.5 Verizon ROM (it came preloaded out of the box)
Sometimes, it locks up immediately after bootup (as a moment ago) sometimes it will run great for weeks before having problems. I can't find a pattern.
I've had my triumph about 2 months and it worked great til now. But last night I turned my triumph off and back on, and as soon as it booted up, it asked me to activate again. But I was still able to make phone calls out. I checked with virginmobile and they said my phone is fully activated and gave me the procedure to edit my activation to get it activated again. I went through that procedure and the phone rebooted, but it still asks me to activate. When I click activate on the phone it says "searching for network 1 2 3" then says error and asks me to call virginmobile. I'm still able to use the internet and make phone calls out so I think it's a problem with the phone, not my virginmobile service. Anyone know how to fix this problem?
My Dad has the same problem with his. Try a factory reset.
Factory restore totally worked! here's the instructions I used https://motorola-global-portal.cust...a-triumph---master-reset-/-factory-data-reset
if you leave for few minutes it disappears by itself. no need to go thru activation process.
it lasted over 24 hours for me
Mine started doing this after I used Titanium Backup to remove some of the stock bloatware apps. I left the Activation app alone. As soon as I rebooted, and now every time I boot the phone, it asks me to activate. I just hit 'Home' and then clear the notifcations. It doesn't come back again until I reboot.
Mine started doing this today. I wonder if they did some kind of update. I have not installed any apps in a few weeks. I also reboot every am due to a bad memory drain.
Sent from my MOTWX435KT using XDA App
So, this is bit of a new issue, one I've not had before. I wish Hangouts/Messenger still had the Service Center ID in the settings in order to fix this, but, in the long/short run...
I unboxed my pixel and put my SIM in, started the phone. LTE/UMTS work perfect, locked right on, good signal/speeds, can place/receive calls, all is right in the world? I noticed after an hour I hadn't received any texts, and after feeling very unimportant, I sent a SMS to a friend, and got an immediate error. Out of curiosity, I went into the INFO settings (*#*#3646#*#*) and went into the SMSC settings. pressed refresh, which, populated an error. I manually typed mine, hit update, went back to hangouts, and voila!
The next day, I restarted the phone ( I like to do this often. I am also this user who actually turns their phone off from time to time ) and noticed upon restart, the problem resurfaced, like as if I never updated it to begin with.
Is this occurring with anyone else? I've yet to see a phone completely dump it. I'd prefer not to download another SMS application really, but, it's just inconvenient those few times I do restart it that I lose that SMSC number...
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
I'm having this same issue. I've contacted support about it, but haven't gotten a response yet (they said I would have an update yesterday).
If I manually put the SMSC in, and then Update, I can send texts briefly, but eventually I start getting an error 38 instead. A reboot and then manually entering the SMSC again allows me to send texts again.
vagosto said:
I'm having the problem as well but still haven't been able to fix it with the same procedure you did. It's driving me nuts.
UPDATE EDIT: I just realized the Wifi is interfering with it. As soon as I turned off the wifi, the txt would go out.
Click to expand...
Click to collapse
I'm curious if setting your mobile data to always-on would be a functional workaround to help until they can get this fixed for real. Have you tried that?
My Pixel suddenly stopped being able to make and receive phone calls a few days ago. The Phone app is extremely sluggish trying to make a call, will usually finally "connect" and look like the call is open, but I hear nothing but silence on the other side, and the other person can't hear me. It's slow to try and hang up, too. I see calls coming in, and can try and answer, but with the same result. Missed calls are registered. Voicemail also does not work. I can see there is a message, but can't play it.
Running 8.1 with February 5 security patch. Carrier is Verizon. I've gone in the store, and they switched out the SIM card. I've also tried a hard factory reset, all with no difference to the problem. The phone is over a year old, so I think a replacement is not possible...
If anyone can help me or has any ideas, I would greatly appreciate it! Thanks!
It's a hardware problem, Google is aware of the problem, they should replace your device. Contact Google, even if you are out of warranty they will replace the device for you!
OK WORKAROUND FOR ANSWERING CALLS UPDATE:
Found this floating on some other forum, not sure where after this mad dash of a search I did this morning, but original credit to them...
When you receive a call and the phone is active and unlocked, press the power button to lock the phone and bring up the blue call management screen. Now you can swipe to answer.
This seems to work for more than one test call as I've tried this multiple times in a row.
NO REAL WORKAROUND FOR MAKING CALLS YET (outside of airplane mode toggle, or using Google voice/hangouts to place calls).
GOOGLE SUPPOPRT - THIS IS CLEARLY A SOFTWARE ISSUE, not a 3rd party app issue either since the problem goes away for answering calls when you press the lock screen or toggle airplane mode for placing calls. Please STOP ASKING CUSTOMERS TO invest hours of time (or money) FACTORY RESETTING PHONES, or REPLACING/BUYING NEW PHONES.
MY HUNCH, is there is some core google service that isn't being used in SAFE MODE, but starts being used on NORMAL BOOT that is causing all these issue. I really DOUBT its a 3rd party app.
Thanks for your replies. I've contacted Google, and they didn't seem to think it was justification for replacing the phone out of warranty. They said I could either take it to a repair place to fix it or trade it in for the new Pixel 2 and get some money for it.
The workaround for answering calls works to connect the call and start the timer, but I still can't hear the caller and they can't hear me...
I still after much troubleshooting have found no way in which calls are functional. In addition to the attempts made above, I've since tried to uninstall and reinstall the phone app, and also to install a different phone app. No change to the problem. Even more curious, the problem still persists in Safe Mode.
If anyone has any more ideas, I'm all ears! Thanks!
So far, I can't seem to find anyone else having this exact issue. Starting yesterday, I was not able to answer or make a phone call. The dropdown "incoming call" notification came, but I couldn't tap answer or reject. The button would light up like it was registering my touch, but nothing would happen. I went to my contacts to return the call and nothing happened when I tapped call. I tried manually dialing the number, same thing. I tried other contacts, all the same thing. I restarted the phone and the problem went away, for a little while, then came back ( should note that if I am in my car and on bluetooth, I can answer a call using the car's answer function, but I can't make calls). A few times, the phone would make the call, but maybe a minute to two minutes later, like the Android phone app was moving in super slow motion. Things I have tried: clearing cache/data from phone app, uninstalling all updates from phone app. Nothing seemed to help other than rebooting, but that only works for a little while. I have not yet done a factory reset.
I am on Android 8.1 on T-Mobile.
I run a business and can't be without my phone! This is very frustrating. Google support wasn't much help.
Thanks!
Lou
It's a defective phone by manufacture, it's a crack in the audio codec on the motherboard. Contact Google or the retailer you bought your phone from if you are still under warranty or even if it's finished you should get a replacement from Google anyway.
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
louballs said:
Thank you. The Google support person I spoke with yesterday didn't mention anything about this. I'll have to reach out to them to see if they will issue a replacement as it's out of warranty. Is this the same issue that the class action suit is about?
Click to expand...
Click to collapse
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Alaadragonfire said:
Exactly that is the same issue, mine was under warranty but as I am out of Canada, they told me they will replace it only if I bring it back to Canada, unfortunately I am still outside and the warranty finished, I tried to fix the phone at a local shop and they damaged the phone totally trying to fix it, I just bought another one after, but this time I made sure the device was manufactured after 2016, mine is March 2017 and it doesn't have the mic issue.
Click to expand...
Click to collapse
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
louballs said:
Looking at the online info for the cracked audio are you sure it's the same issue I'm experiencing. It's not that I can't hear anyone or people can't hear me it's that my phone will not even attempt to make a call or answer a call. It just won't respond to me pushing the "answer" or "dial" button. Also, I haven't been able to replicate this issue in safe mode. Maybe something else at work??
Click to expand...
Click to collapse
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Alaadragonfire said:
It's the same thing my phone used to do, I even reinstalled the factory image and setup a new phone and still acted the same.. I hope yours is not but unfortunately if you had the same experience in safe mode then it is what it is my friend
Click to expand...
Click to collapse
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
louballs said:
Ok, though I have NOT been able to replicate it in safe mode, so that's why I was wondering if maybe something else. I'll try to get them to replace my phone and hopefully that fixes it.
Click to expand...
Click to collapse
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
Thanks! I was hoping to avoid as it's super annoying, but that's my last option.
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Alaadragonfire said:
Try to factory reset it from the settings, maybe it will work and it turns out to be some issue/app that is making your phone to act like that, just back up everything on your phone as the factory reset deletes everything on the phone. If it didn't work out then you should replace your phone.
Click to expand...
Click to collapse
nichos said:
I'm glad I've found this thread - I have the exact same issue. Tmobile and a pixel (1) that this just started happening with.
If i reboot the phone I can dial out, but after that it won't dial anymore. If I do attempt to dial, it seems to dial like the OP says, a few minutes later.
I'm able to answer the phone from the lock screen (by swiping up) but the drop down with answer and decline don't work when the screen is unlocked.
I've tried removing updates, clearing cache and defaults on the phone app, no luck. A reboot is the only fix, but it seems to last only for 1 call.
I havent dropped the phone or anything. @louballs, please report your findings after a reset, I'll keep playing with my phone too, maybe we can figure this out.
Click to expand...
Click to collapse
Well, I'm glad I'm not alone. Is it possible it's a network thing with Tmobile? I'm not saavy enough to say it's possible or not, but maybe the other members can tell or help troubleshoot. It can't be coincidence we both have the exact same problem.
Same problem with a Pixel 1 and Verizon
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Switchkey said:
Having the same problem. When I get a call I get a drop down with the caller and answer or decline button. Neither one works and I have to just let it ring out. I get a missed call notification but no voicemail notification. I have deleted truecaller app and rebooted but no change.
Click to expand...
Click to collapse
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
nichos said:
I've found that if it's ringing, you can press the power button and it will take you to the "swipe up to answer" blue screen. That works for me.
Doesn't solve the problem any of us are having, but at least you can answer calls when they come in.
@Switchkey are you on Tmobile too?
Click to expand...
Click to collapse
Verizon
I have a Pixel XL 1st edition and I just started having this problem yesterday. The drop down menu won't work to answer calls and if I try to call back it won't go through until a minute after I try to connect the call. I'm on the Verizon network so I doubt it is a carrier issue. My best guess is that it has something to do with the most recent update. I really hope this gets resolved. It's the first real issue I've had with this phone.
The latest trick
Tried calling my wife from the car while driving using Google Assistant. Three times it said it understood I wanted to call my wife's mobile but it did nothing. 20 minutes later while I am driving I hear "Hello?" 20 minute delay on voice dialing a number. Luckily she said hello. If it had been someone else they might have just listened to me go about my day. This all started in the last few days. Prior to that the Pixel 1 phone has been great.
Same problem here. TMobile pixel 1. A reboot fixes temporarily. Started in the past week.
Update:
So from the beginning, I have NOT been able to replicate this problem in safe mode. I can make/answer calls with no issues whatsoever. So on Sunday night I spent some time uninstalling almost all of my apps and the issue seemed to go away. I went back in and reinstalled them and my phone was fine up until this morning. So because it was working for a couple days and works in safe mode. Is it possible that it is some sort of app conflict? I don't want to spend countless hours on this, but I really don't want to buy a new phone. Google will NOT exchange for me and I still owe $200 for this damn phone as I did the installment plan! This is very frustrating. Can anyone having this issue consistently try it in safe mode and report back to see if they can replicate it? In the mean time, I'm just going to run my phone in safe mode so I can answer calls at work.
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
ApertureAndroid said:
Hey guys, my dad has been having the same issue on his Pixel. I quickly scrolled through the most recent posts on /r/GooglePixel and found this post. The comment mentioning disabling the phone permission for all other apps other than your default phone app seems to be working for my dad. So, I guess that's a workaround until Google fixes it (better than staying in Safe Mode, at least).
Click to expand...
Click to collapse
Interesting find! That might explain why after uninstalling a bunch of apps it started working again, for a while. Perhaps one of the apps is causing some conflict? I've just done a clean install again after uninstalling a bunch of apps I don't use anymore. If it comes back, I'll check the permissions and report back!