Database Users

[APP] Voice Runner (Another GPS APP)

Hi All
Well this is another GPS App and my first so as people say "please be gentle".
I wrote this for my wife and me for when we are running or cycling.
The idea behind it was to know how fast, far, average speed and time travelled while listening to music without have to look at your phone. It basically says the info you want, the voice is a basic computer voice. It will also say any sms that come in while in use but it can only say words and numbers not any text speak but which I might be able to add later.
My biggest problem is because the voice isn’t particularly loud of clear I need to be able to pause the HTC music software while it’s speaking. If anyone knows how to do that please help I was hoping the pause button on the wired headphones might have a virtual key number but I haven't found it yet.
If I can get the above problem solved am hoping to add a lot of useful info to the display and to the spoken info such as a buddy runner based on a previous run or target settings.
In the setting menu the only item that’s functional at the mo is the repeat voice setting. As you may see the whole program is at a very early stage at the mo so again please be gentle.
http://rapidshare.com/files/187741228/Voice_Runner_0.2.CAB.html

Sir if you can find a way to pause or mute music with hardware button on wired earphones, You will make me really up...

Nexus One -- Incall Bug

So here's my issue.
During a call if i recieve a SMS/MMS/Email, my earpiece volume drops dramatically and i can use the volume rocker and put it too full and it still doesn't get back to a decent level.
So i was wondering if anyone else has noticed this and is having this small problem, other than that i am completely happy with the phone so far , haven't touched my iPhone since i recieved the Nexus One Jan 7th
P.S. i have SMS Popup app installed and same problem, so i have tried removing the app and still no cure
I haven't tried this on SpeakerPhone or BT Headset

I can 2nd this bug.
Along side, if you were to use any touch tone to send DTMF tones while on the phone (say you're entering your credit card or something), it also goes down real low. This is definitely a bug.
C

ya ....argh!!...hopefully a firmware update fix

I have experienced the bug as well...but what is even more strange is that if I get another text message or email and it causes the phone to vibrate the in-call volume shoots up even louder than it was before. I think it may have something to do with dual microphone and background noise cancellation this phone has.

No problem for me?
Just thought I'd offer some more input, but I don't think my phone is experiencing this problem..? I am currently on the phone with T-Mo, and had to enter numbers via the number pad while in the call, and the volume didn't adjust (neither up or down) at all.

I'm glad I found this thread. I should have read through all of the posts in XDA before starting a brand new thread about this. Sorry guys! I even have this issue listed on google's help forum with some ppl indicating the same. The call volume decrease for me when a call comes in. I have to put the phone on speaker, then take it off speaker in order to get the volume back to where it was. I use to have the volume decrease during an active call when a email or text comes in, but a small work around was to set the ringtone and notifications to silent in settings and in text and emails. Does anyone know if this is a software or hardware issue? or if there will be an OTA update to fix? This phone is amazing otherwise...I know there isn't a TON of ppl reporting this, so I hope google doesnt forget about us. I received a replacement that did the same thing along with new bugs the original didn't have, so I sent it back.

I have it also. Just thought it was me!

@johnboywilson, do you think google will come out with an OTA update for this? This is technically my first android phone, so im not sure how often they come out with updates, or if they get to all the issues no matte how few ppl might be having them. I had WinMo before, and they were pretty good at getting to bugs, sometimes even if just a handful of ppl have them. I had a samsung behold II for 2 weeks. I've only been using android for a little over a month now.

next time this happens will someone try swapping to speaker phone then back to handset and see if it goes back to where it was. I've had a problem a couple times where I couldn't hear the caller, switched to speaker phone, heard them fine, switch back to handset and the volume was back to normal. I honestly dont remember if I had received a notification at the time or not but I'd be curious to know if it is the same thing.

@zjchaser, if you had seen my two previous posts, you would have seen that I use the speaker phone on then off method to correct the volume decreasing when a call, text or email comes in while on a call. This is just a work around and not a fix. I need to know if we will get an OTA update to correct???

@Mrplennium I`m sure they will. if you go onto google support pages you will see what questions people are asking and what faults other people are experiencing.
@zjchaser I have had that problem too. If im on a call and i switch between speaker phone and handset the sound goes off. If i then make a new call the sound is still off and i have to switch between speaker and handset to get it to come back on!
Still love the phone though..

@johnboywilson, I hope you are right. I am one of those ppl that started a thread on the google forum about this issue, and others have been reporting it. I was just fearful that this is one of those issues that's in the minority, so google might skip over it. I hope that's not the case. Other than that, this is by far the BEST phone i've ever owned. I have no other issues with it.

I use the wired headset mostly, but I can confirm this as well. It isn't just another call or SMS for me that causes it...anything that adds a notification (SMS, plugging in to USB, email...anything!). The volume either goes crazy up, or crazy down. It seems to alternate.
It went down the other day after an email during a call, so I had to put the rocker all the way up just so it would sound normal. Shortly thereafter, I got a text and lost my hearing for about 10 mins...the phone can get very loud.
Seriously, this needs to be fixed.

Yup, it happens through the wired headset as well. I think it's def a software issue. Hope you have google people patrolling this site and seeing these issues as well. The first OTA update is coming this week, but for the 3G issue. No one knows what other possible fixes might be included.

Even received a replacement that did the same thing. Not sure why some ppl have working devices, and others have these software glitches. I doubt i'll ever be an early adopter again.

WOW! ok, after 3 preliminary tests, I can conclude that the OTA update has resolved this issue!!!!! YEEPEEE!!!!!!!! Now the phone is PERFECT! I will keep monitoring the situation throughout the day to see if it stays that way, which I can't imagine why it wouldn't!!!THANK YOU GOOGLE!!!!

it didnt fix the problem when i did the update,still have low incall volume

If you have low incall volume - rise it, or flash a kernel with volume boost hack. This bug has been resolved months ago. You're talking about something else.

HD2 issues: Any assistance?

Hello all,
I purchased my HD2 on release day and so far I love it. For the most part the phone has been problem free and everything works perfectly. However recently I ran into a few issues.
1) When playing music with Windows Media player or the Music Player I will sometimes get odd skipping in songs. I looked at my screen and the microphone symbol at the top of the screen was blinking like crazy and I could hear a voice asking me to repeat commands again. I believe it was the voice dialing feature. One time it actually called someone. My phone started dialing out in the middle of a song and I had to pull the battery to make it stop calling people.
2) Text messaging.. The text messaging app has some serious bugs. Hopefully there is an update or a better solution out there. Some of the problems I have with texting are: Phone goes to a crawl when a text comes in, when typing texts it will just stop showing what I am typing. I have to click all around the window and sometimes can get it to come back up. If I cannot get my text to come back I have to close the app down and then go back in.
3) I am not sure if this is related to the sms app or not but I tried to edit a contact and the phone become incredibly unstable. It restarted itself and when sense loaded it popped up a message saying that swipe was not designed for my phone type. After that reboot my phone acted up a lot until I restarted it about 6 times. Then it was stable but the texting app was worse than ever.
I did a bunch of google searches and couldn't come up with any fixes for these issues. So any input would be welcome.
My phone is stock. I have no interest in flashing a new rom. I blame all these problems on sense (WinMo actually seems perfect despite what the uneducated spew across the net daily).
Thanks for reading

1) Sounds like you're simply activating the MSVC, which is done buy a long press off the send key (you're probably accidentally long pressing the 'play/send' button on the headphones.
Two solutions: 1) Simply disable MSVC (Settings>personal>Voice Command; Uncheck Enabled) 2) Be more careful so you don't accidentally press the button.
2)Just click the text input area (just above the keyboard where the text is suppose to be) and everything you typed will show up and continue to show up.
3) Never heard or seen this.
I don't know how much stuff/time you've put on/into this phone, but you might want to consider a hard reset.

Thank you for your response:
I was not using the headphones. I had it connected to my stereo in my Jeep. The HD2 was sitting alone on the seat next to me with nothing around it. It's done it several times now - so I don't think it was anything environmental.
Clicking in the text area used to work fine but not anymore. I have to click the last text message that came in and it will open a option menu, close that and then click in the open text area several times. This started happening once I tried to edit my contacts and my phone lost it's mind.
I don't want to do a hard reset but it might have to come to that. I have all the apps I like installed and everything seems to be working nicely with those few exceptions.
Ohh and one last complaint. Slacker >< why does it stop playing songs so much? I read other people were having problems with that too but I cannot seem to find any fix. Should I just give up on it and go to Pandora?

[Q] How do I stop this sound?

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.

Incoming Calls / Black Screen ?

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.