hi can anyone pls help,when I select any of the vibrate options on my incoming call alerts the unit completely powers down when I receive an incoming call, is there any way to stop this as I work on building sites and miss a lot of calls due to this. also is there any way to make tha alphabet bar at the top of the contacts page bigger as the scroll function sucks! thanks in advance.
Besides cutting off sound after a while it indeed also powers down
regulary (and sometimes it even makes a fresh restart by itself).
This is so strange, I like the architecture and the technology,
but I think I will give away this phone and buy myself something else.
Even if its software related this is all a pain in the neck,
there must be something better on the market.
I upgraded my XV6800 to 6.1 using the official upgrade. It's giving me trouble answering calls. When a call comes in I see the notification but when I try to press the Green phone button or the left soft button labeled 'Answer' it doesn't do it! It's like the keys are slow or something. When I use the soft button is DOES flash the soft button label like it recognized the button press. But it does not answer the call! I've had this happen at least a dozen times now so I know it's not just me fumbling with the keys. 9 times of of 10 I can't answer a call!
I've tried hard resetting the device and the symptom persists. I've tried using it without the microSD card loaded. Still the same trouble.
Has anyone else seen this? Or can you recommend a solution?
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
I feel stupid/foolish for shareing that experience but figured just maybe its what your experiencing.
Thanks,
Ben
*edit: by the way... when I had the 6.1 vzw upgrade I had no problem placeing and receiving calls, with the exception of the "user error" I described above. You could always try rolling back to 6.0 and upgrade again. Did you install any other new software after the upgrade to 6.1?
I have been experiencing something similar. PPC 6800 (not Verizon) with 6.0. When phone is locked and call comes in, can’t answer with the button or with BT. 6800 keeps ringing long after caller goes to voice mail. The only way to escape is soft reset. I’m running the original ROM & Radio that came with the 6800.
ygohome said:
so your saying it doesn't show "connected"?
I had something similar to what your describing but it would show as "connected" on my phone. I couldn't hear anything when I'd answer. I realized after several attempts it was that the phone was paired to my cars bluetooth... I was trying to dial my phone as I was walking away from my car but I was still within 30 ft of the car... so all speaker and microphone was still being redirected to the cars system. lol. Same can happen with a bluetooth headset where the conversation (speaker/mic) is redirected to the headset that may be in your pocket or on the kitchen counter. But it would at least show as "connected" on the phone.
Click to expand...
Click to collapse
Nope, never shows connected. It's like the UI has gotten hung somewhere and isn't passing control over to the phone app.
No bluetooth pairings have ever been done to this phone, not before the upgrade and certainly none since. BT isn't even enabled.
Tim may be on to something regarding the lock situation. I've found the lock method a lot less friendly than before 6.1. Can't quite pin it down but it just doesn't seem to unlock properly. Again, it seems to be related to something making the phone 'slow'. On-screen keypresses in the Lock app don't seem to register with the same speed as before 6.1. I can tap a couple of them and not see anything on the screen, then they all run through (showing the screen buttons getting pressed).
My Xv6800 Verizon Does The Same Thing. I Push The Green Hard Button To Answer And It Takes Like 5 Seconds To Answer. It Seems To Happen More When I Have Programs Like Internet Explorer Up, But There Is Still Plenty Of Memory So I Cant See Why It Would Be So Slow. Its Just Frustrating Because Sometimes It Takes So Long The Call Goes To Voicemail And Nobody (fiancee Included) Believes Me! Any Help From Anyone?
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
ygohome said:
fyi... i use an auto close program so when I close an application it really closes. I don't have the slow response or ability to not answer within 5 secs, etc. maybe it is a low memory issue you are experiencing. I don't lock my phone so that may be it too. Sorry I'm not much help here.
Click to expand...
Click to collapse
No, it's definitely not a low memory issue. It's doing this fresh after a reboot having had no other apps even started.
My phone is not rooted. This just started this week. I have not adjusted any settings for quite a while so I am pretty sure I did not do anything to cause it.
Since getting my Note 3 in October I use the voice method of inputting text for email and sms quite often. When starting a message where I want to voice inpput, I click the microphone button and speak what I want to send. Works well for me. Thursday the phone started making a loud, very annoying, beep type sound whenever I launch this by clicking the microphone. It happens even when the phone is in silent mode. I checked the sound options in the phone settings and everything is set as it has always been. All system and keyboard sounds are turned off. I also tried another keyboard app rather than the phone default and it is the same with that.
Does anyone have an idea why this started and how to silence it? Thanks!
I guess this is not an issue for others here. I did find the exact problem on another forum and it started for him just a few days ago also. So maybe something updated automatically that caused this. We will see if more people start complaining about it. By the way we have tried a few different suggestions, including resets, but nothing turns off the noise yet.
0n edit: I looked at my apps to see what recently updated. One of the recent updates was to Google Search. I uninstalled all the updates to Google Search and the problem is gone. So it is a bug in the most recent update to Google Search that turns on that sound with no way to turn it off.
so i have a few issues with my unit. nothing major, but more of an annoyance.
when i get a notification my music stops or is interrupted briefly when paired on Bluetooth. -- there a way to fix that?
steering wheel control interegreation -- i have a 07' cts base and i dont know if i have analouge or digital ones. do i need the pac control unit like i did to keep door chime and onstar?
beeping from what i can tell i can fix, i'd like to get that fixed (i have the ROLLUP and the other threads up right now)
is there a way i can read and send text messages?
i know i have it wired correctly, but i noticed it wakes up super quickly to the point where i'm not comfortable, i'm just more worried about a dead battery. does anyone know the power draw by chance? and if i dont drive it for a few days is that an issue?
i think those are my only issues, i love this damm thing so far!!! much nicer than my AN21
the notification issue is from your phone. Find a way to mute the volume of your notifications on your phone, it varies by phone.
Reading and Sending text messages can't be done unless you use some type of app. T-Mobile now has DIGITS which would do it. I think if you have a data source, then Verizon has their Messages+ app
waking up quick is how it should work. Many people have tested the Dormancy and no one has really had an issue with it. If you are not going to drive for weeks at a time, then maybe turn it off
Not sure why but after the last system update the phone will only come out of black screen sleep mode if I use the fingerprint sensor when theres an incoming call.
Any Ideas ?
This happened to me today too.
Hello, me too! Oreo Beta 2
Anyone ?
going_home said:
Anyone ?
Click to expand...
Click to collapse
Not me, I've never experienced this issue since I got the phone from N then updated to OB2, and now OB3.
Sounds like the proximity sensor may have an issue.
Do you have a screen protector or case?
I don't have that issue with a screen protector and Tudia case and B3.
It's a bug in the latest Google Dialer app. I fixed it be deinstalling the new version/updates then clearing cache and data in the dialer app. It's affecting the Pixel2 XL running 8.1 also. Fixed my issue and I won't let it install the newer dialer version from the play store
In Beta 3, I haven't experienced that problem. I did heavily on 7.1.1
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
going_home said:
Just got another update and still having black screen on incoming calls....
I'm about ready to ditch this phone and get a Pixel 2 XL.
I read where Essential is skipping the 8.0 update because of instability and going straight to 8.1.
Click to expand...
Click to collapse
happened to me last week too.. it only happened after I locked the phone, 5-10 minutes later incoming call or when unlocking the phone the phone shows back screen only for a few seconds then it went back to normal.
the problem went away after I turned off the bluetooth radio.
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
DrvLikHell said:
I've been having this issue for a while now and just today I figured out the cause. At least the cause of my specific issue. I came here to see if anyone else is having similar issues so I'll explain exactly where I'm at.
If a Bluetooth headset is connected to my phone, when a call comes in the screen stays black and I can't see who's calling. If I turn off, or disconnect the BT device, when a call comes in the screen lights up with caller ID like normal. This also affects the missed call notification that happens after a missed call. With a BT device connected, the missed call notification will not show until I wake the phone with the power button, though the notification LED will light.
I'm on stock 7.1.1 and I verified that this is also an identical issue with two other phones which were not on a stock ROM, though I can't remember what they were running. This started happening to me before the NMK24B update. I remember because I was hoping that the update would fix it. I believe it started with NMJ88C because I got my phone on NMJ32F, it updated to NMJ51B shortly after and it was fine in the beginning months.
Click to expand...
Click to collapse
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
I tried two other dialers and it didn't make a difference on my phone. Drupe did work to make the screen show who's calling again, but wow, Drupe has too much.... just, everything. All I want in a dialer is basic functions in a standard format. Drupe is like a carnival of a dialer. I'll keep trying dialers though, since that one did work, maybe another one will too. Thanks for the suggestion.
Yeah, if you just take the Drupe dialer phone icon and put that on your home screen, whenever you select it you'll go right to the normal looking dialer. :good:You may want to try ExDialer. That used to be one I'd use a lot.
Jank4AU said:
I had the black screen issue as well for incoming calls. I just switched to Drupe Dialer from the Play Store and set that as my default dialer. Now my screen lights up with the incoming caller ID and works as it should. By the way, hate to sound like an add, but Drupe Dialer is just awesome and has a ton of functionality, give it a shot. I know that's not the perfect answer as we would expect the native Android dialer to work out of the box with our OS, but it is what it is.
Click to expand...
Click to collapse
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Sent from my PH-1 using Tapatalk
rignfool said:
Before using Drupe...
There should be a warning that goes out to all your contacts saying "I'm about to completely betray you and share EVERYTHING about you online with a company I know nothing about... Please enjoy these spam calls on me"
Click to expand...
Click to collapse
10 million downloads...good enough for me. I've used it for a long time and it's been better for me than the stock dialer. Just my opinion, no one has to use it but it sure beats a black screen when the phone rings.
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Sent from my Pixel 2 XL using Tapatalk
I read about some people being able to fix it by uninstalling dialer updates. Unfortunately, the Essential doesn't have any to uninstall. I'm working around it by using Drupe as my default dialer, but setting the stock dialer as the default app for dialing, if that makes any sense (When an event pops up that requires the dialer, it asks which dialer to use, I selected the stock dialer and told it always use that.) This way incoming calls trigger Drupe, which acts the way it's supposed to on Bluetooth, but I can still use the stock app for making calls and missed calls and such.
bricky23 said:
I have the same problem on the pixel 2 xl. And so do lots of others. I uninstalled the phone update from the play store, and turned off auto update. So far so good. And I am on 8.1 But we will see. And it only happens when I'm on Bluetooth. Unfortunately I use it all the time for work
Click to expand...
Click to collapse
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Jank4AU said:
Yeah, I'm thinking there's a Bluetooth issue (yeah,I know, news flash). But it's been widely reported that some folks are having trouble connecting to their cars Bluetooth. I use a Bluetooth adapter in my car and wireless headphones in the office. No real big issues connecting, but it can be finicky. However, once an event triggers Bluetooth, like streaming a song with Google Play to the adapter, my phones volume buttons become unresponsive. I can only change volume by going into the settings menu or from the Bluetooth device. Sucks. Waiting for the 8.1 beta to do a total clean install. Just bought the device used from Swappa and it came with beta 3 installed, not 100% sure the steps it took getting here. I guess what I'm asking is, does anyone else experience issues with their volume buttons not working occasionally?
Click to expand...
Click to collapse
My volume buttons always work fine, BT or otherwise. Stock 7.1.1. Your issue could very well be related to OB3. I had a little bit of an issue connecting/reconnecting to some BT devices at first, but not lately, so it must have been fixed in the last few patches.