Database Users

HTC working to fix voice calling fault on HTC One M7 and mabye M8

Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls.
A HTC spokesperson confirmed the problem to TechRadar, with a recent HTC Service Pack downloaded from the Google Play Store the presumed (but unconfirmed) culprit.
The firm says resolving the problem, which could also be affecting One M8 users, is its number one priority and has told customers to expect the roll out in the coming days.
The statement says: “We are aware that some HTC One M7 (and possibly some M8) users have recently been experiencing audio issues making network calls on their devices.
“WiFi calling does not seem to be impacted at this time. We're working around the clock with our technical teams and partners to resolve the issue as a number one priority.
“We will provide further updates as soon as we can. For anyone experiencing this issue with your HTC One (M7 or M8), you may want to try WiFi calling, and we ask that you please contact your local Customer Care: www.htc.com/support."
Speculation suggests the Service Pack may have caused the instability, but HTC isn’t offering up that information at this stage. As the original report points out, if you haven’t downloaded the update yet, it may be wise not to do so.

jkolner said:
Read more in this link.
HTC plans to issue a fix for an issue preventing some owners of the HTC One M7 handset from placing and receiving calls..
Click to expand...
Click to collapse
This might explain the issues I have been experiencing since the 5.01 OTA. Call recording has failed with every SW I have tried. Sound quality during calls has crackling and is very poor.

This makes a lot of sense, in the last couple of days mine has had the same problem as was told by HTC that it was a hardware issue, but if this is the case may just hold back and wait for an update.

I've had mine recently producing no audio at either end when answering a call, a reboot seems to sort it out for a while. Hopefully this is all it is and they can sort it out fairly soon, I'm in the middle of buying my first home and trying to talk to lawyers and stuff gets a bit embarrassing when this happens.

Oh my a God.

Thought was mine only!
Sent from my HTC One using XDA Free mobile app

I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.

Pavlova said:
I noticed that also, when my wife called me, and said about sound distorsions during the call. The solution in my case was returning to branded T-Mo firmware, and not updating HTC Service Pack from Play Store.
Click to expand...
Click to collapse
On M8 Original GPE, HTC service pack was installed with 5.01 OTA update. No choice on whether to install or not - it appeared on the list of updated apps.
Apart from sound issues (which I suspect come from HTC/Google disabling features at the Kernel level), I am now experiencing delayed touch response.

Yes, but as I remeber, it was updated also after initial startup. Last update of the Service Pack (on Sense) in Play Store was from 11th December. Anyway, on T-Mo firmware 3.29.118.9 call quality is much better. Also ringtones and notifications are more clear.

Just got a service pack update.

for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching

Andrew149 said:
Just got a service pack update.
Click to expand...
Click to collapse
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
RedBlackPellet said:
for me I am running the latest gpe 5.0.1 and my problem is that the upper speaker is not ringing but it plays music just fine
uninstalled all google and htc services and the problem is gone F%[email protected] this
I thought that my phone was damaged spent 2 hours searching
Click to expand...
Click to collapse
Can you pls give a little more details as to what specifically you uninstalled. Thanks.

Roadrunner100 said:
Yeah, Christmas graphics for DotView. Nothing fixed otherwise.
Can you pls give a little more details as to what specifically you uninstalled. Thanks.
Click to expand...
Click to collapse
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related

RedBlackPellet said:
well till now I am not sure that it is software or hardware problem but when I uninstalled google play services to factory settings the problm is gone and when I restart the Device the Problem is back again Will try to downgrade to 4.4.4 gpe to insure that the problem is not software related
Click to expand...
Click to collapse
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1

Roadrunner100 said:
A quick summary of issues:
Google have confirmed memory leak issues with 5.01. An update is supposedly on the way: http://www.xda-developers.com/android/lollipop-memory-leak-fixed/
I've fixed Touch Delay by going into recovery and clearing cache.
Sound and playback issues are probably to do with Google disabling certain features in Lollipop, one of which results in an inability to record calls - access for third party apps to intercept caller voice has been disabled. I'd speculate that this hatchet-job has led to most of the sound issues some have encountered on Original M8 GPE's.
A partial explanation can be found here: http://forum.xda-developers.com/showpost.php?p=56397342&postcount=1
Click to expand...
Click to collapse
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution

RedBlackPellet said:
does this means that my problem [upper speaker doesn't ring but it plays music just fine also the ear piece is working as it should] is due to software issue but I reverted to 4.4.4 and the problem exists the upper speaker doesn't ring but on sense it rings whenever the proximity sensor is not covered [facedown or in pocket it doesn't ring ]
well try to revert now to 4.4.2 1.54.401 firmware and rom and see if the problem persists
on my friend's one m8 and brother''s one mini 2 that proximity sensor covering issue exits but I am not sure what to do and can't decide whether it is software or hardware or even a problem after all I found sony xperia users complain about upper speaker not ringing due to safety precaution
Click to expand...
Click to collapse
Like you I'm trying to find out what's going on. I can confirm issues with the proximity sensor. I have further issues like skype not gaining access to camera, voice call issues like loud speaker switching on by itself during a call.. etc. What's clear at the moment is that this GPE release is screwed up big time. Like you I've reset the device a few times, but noting changes. Same problems reappear.
I think that finding out more is difficult since there are no specific Forums or threads dedicated to non converted stock GPE's. So finding out more about issues specific to this version is very hard... I have two other colleagues with Original GPE's (mine is a very early device, their's purchased recently) that have the exact same issues, so I can only assume that this is not HW related, but due to Google disabling certain features and getting it badly wrong or HTC's service Pack at fault. In the office there are three other Sense M8's, which don't have any of these issues, but none of them are on Lollipop yet, so I cannot compare until they get HTC's update.

I have a OEM gpe m8, running mrjaydee82's lollipop gpe ROM. I've seen no weirdness besides memory leak.

Nexus Bugs In Update 6.0.1

So when I bought my Nexus 6P I knew I was going to get the latest updates as soon as Google released them. I also expected to find minor bugs because we are getting updates much faster as well.
What I was not expecting is to both, bugs that make for a nearly unusable device and minor annoying ones. For my device the bugs that hit me hard are;
Max Volume Bluetooth Speaker Bug - Most bluetooth speakers are stuck in max volume mode and can't be turned down. Distorts the audio and creates a situation were you could blow out the speaker. Not all speakers are effected.
No LTE On Boot - Annoying to have but "fixable" by putting the device in Airplane mode. Otherwise no Data or SMS until you do and hope your phone doesn't reboot in you pocket while waiting for an important message.
No Phone Calls - You can't make or receive calls. As a result you can't check VM either. No amount of Airplane mode or rebooting will fix it. Neither will the phone service menu.
My concern here is that Google hasn't patched these bugs yet, even after releasing another update to 6.0.1 M. For now I'm fine with downgrading to 6.0.0M but I'm missing out on updates.
To add to insult any ROM build with the 6.0.1 source is effected by these bugs, so I can't even use most ROMs unless I find an older version.
I guess my main question here is this:
Is this normal? Does Google usually go so long without patching the bugs?
Seems really silly to have a phone, but not be allowed to make or receive calls at all and not be able to send SMS or email unless you do a few tricks first. It's a phone. Don't they test these things?
Disclaimer: I already know not all 6P or Nexus devices are effected. That does add to my confusion as they all should be the same exact device.
EDIT: I also wanted to add that when I got the device I could do all these things however even downgrading will no longer allow phone calls. Something is retaining.

Well that's weird mate. I'm on 6.0.1 and have none of these problems.
I was experiencing awful battery life after the latest update but clearing the cache has made a huge difference

Have you tried reaching out to Google? It would be helpful if you could share how you upgraded to 6.0.1? As mentioned above did you clear cache? The more info you can provide; the faster someone can help you.

The Bluetooth volume issue is the only one I have and only on one of my speakers. The others with fine.

Huh, ya 6.0.1 here too and none of these issues are present.

Having strange issues? 6.0.X or 7.0 bring strange bugs? If you haven't already, try..

Flashing the very first 6.0.0 (MDA89D).
In my ventures this last week or so, after dealing with the Battery issue (15-30% power off range) and having my speakerphone mysteriously stop working (It was as if I hit mute to the person on the other end) I have been doing all the research and tinkering I could think of to see if these were indeed hardware or software issues with our 6P.
So in my venture, It may be that 7.1.1 fixed the battery issue for me, as after 3 full rundowns over the past few days, I was able to run down to 3% and then 1% 2 times before shutdown which is immensely better than shutdown anywhere from at best 13% to ~25-30% at worst when you're trying to use your phone through the day.
This was done by running the Mountain app to put a load on the device while I do other things. Once I see it hit 15% I allow it to turn on Battery Saver and watch as it ticks down to 1-0% and goes into Shutdown.
Not sure how truly comprehensive this test is, but so far, it is pretty incredible to have such an improvement over what many of us have been experiencing with our battery life being a cointoss through the day.
I only had 7.1.1 flashed as a fresh image straight from google, TWRP 3.0.2-3 and SuperSU 2.78 SR5 for Root for this test. No Google Account connected or anything else syncing or updated that would touch the battery or run in the background.
Now for my Speakerphone issue. I cannot recall exactly when the issue happened, but since I have been running PN since literally the day I got my Nexus, somewhere in that time, with a lot of dirty flashing from one MM update to the next, messing with Kernels, and overall going quite a while between clean flashes until I finally did one for the move to 7.0, I lost my Speakerphone Mic and only the sound for speakerphone was coming out of the bottom speaker. After testing my Refurb replacement and now my "fixed" original 6P, sound for the speakerphone is supposed to use both Speakers when everything is working normally.
The test for this was easy to do with the Skype Test Call. Just call it and turning on Speakerphone would either work, it records my voice and plays it back, or when it wasn't working, it would just end quickly telling me it doesn't hear anything (and the audio only comes through the bottom speaker).
So TL/DR and plainly, my recommendation if you haven't already done so, and you are having similar interesting and semi baffling issues such as these, try flashing the oldest Image available for our 6P as I did (Directly from google, I just did the Flash-all.bat file as it was included with the minimal ADP terminal on Windows 8.1) and let it do its thing. Once I was in the original MM build, I just skipped my way to my homescreen, downloaded Skype from apkmirror, and logged into that to do the test. Boom! After the test was a success, I downloaded the 7.1.1 image, flash-all.bad'ed that and did the same skip to test.... And Boom! Speakerphone Continues to work normally.
Now to test the battery side by side with both devices to see how bad my old one has degraded if it indeed has done so... or if 7.1.1 has indeed fixed that as well.

External Speaker useless after 8.1 OTA update (impossibly quiet)

Not, rooted, located in US.
Before I did the OTA update to 8.1 last night, my external speaker worked fine, both for speakerphone calls, and media playback.
During my first use of 8.1 today, the external speaker is now so quiet (on full volume) that it's useless in all but the quietest rooms.
Calls on speakerphone are barely louder than if I just shut the speaker off. Watching Youtube on full blast is barely discernible in an average noise environment, and forget listening to music outside or in the car.
Anyone else experiencing this?

Same problem here
It's a official software bug. Most of the people who updated Oreo got this issue. If you want to use your phone use any other custom ROM available here. Otherwise need to downgrade to Nougat. If you can wait for another update from Moto to rectify this bug means bare with this volume issue untill Moto releases new update to fix this.

kingmari said:
It's a official software bug. Most of the people who updated Oreo got this issue. If you want to use your phone use any other custom ROM available here. Otherwise need to downgrade to Nougat. If you can wait for another update from Moto to rectify this bug means bare with this volume issue untill Moto releases new update to fix this.
Click to expand...
Click to collapse
Thanks for the feedback. Unfortunately I doubt Moto will ever release a fix for this.
I never bothered rooting this phone, I guess I am going to find out if its even possible, now that it has Oreo on it.

slimbobaggins said:
Thanks for the feedback. Unfortunately I doubt Moto will ever release a fix for this.
I never bothered rooting this phone, I guess I am going to find out if its even possible, now that it has Oreo on it.
Click to expand...
Click to collapse
Rooting stock Oreo is even easier compared to Nougat, because you don't need a custom kernel anymore. Still I would advise to use the new Loony Kernel or ElementalX for being able to use different RGB values if your device has screen retention problems.

Other observations from this OS "upgrade:"
My phone now struggles to stream Youtube to Chromecast... video/sound sometimes is choppy... previously no issues at all.
Sometimes the phone randomly decides Wifi wont work. Can flip the switch to the on position, but it still says "Wifi is off." Only recourse is to restart the phone.
Overall very disappointed. Can't wait until I get a chance to root and ditch this OTA update.

OP5 Camera not working, constant crashing/rebooting (I have searched threads etc)

Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.

arcticphoenix said:
Ever since my update to 9.0.5 my camera hasn't been working, as well as phone has been blacking out, system freezing up, the LED Light turning to a sort of baby blue color until I force reboot it (this bug has been with my phone since my first boot upon a full charge from 0% after unpacking it). I have scoured the forums of here at XDA and official One Plus forums. All other people have similar camera bugs but those are features of the camera bugging out and easily fixed with a cache clearing. My issue is with the system itself, and no amount of clean (Very) flashes results in a fix. If I go into recovery, select all partitions and format those, even repeatedly has this annoying system bug persist. The camera does come back if I revert to 8.1 OTA and custom ROMs, but the security patches are too far behind for me to keep using them. I am posting here to find out if anyone has had this issue and successfully fixed it as it has been over 2 months since I received my OP5 but I cannot use it for any intensive task as it worsens the freezeups and reboots. Further I live in a remote Alaskan village and there isn't even a OP Center close to the state to send it in. No amount of stock flashing fixes it at all and I am about to curse Oneplus for not being able to push out a stable device.:crying: :edit: I forgot to add that the gyroscope no longer functions as well. Not even in the factory testing menu by entering *#808# in the dialer with the stock roms.
Click to expand...
Click to collapse
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.

strongst said:
It's more likely that you have an hardware issue according to your detailed description of the issue. Cause the gyroscope is also needed for proper camera functionality, camera app may crash.
Click to expand...
Click to collapse
Yeah it is part hardware and part software. A couple of months ago I used the cracked unbrick tool found here at XDA and I regained most functionality which was lost after upgrading from 9.0.4 - 9.0.5, though I do still get system freeze ups and reboots. But that is from a faulty unit not any of the ROMs.
I apologize for reviving an old post so any mods may close this thread.

arcticphoenix said:
...
I apologize for reviving an old post so any mods may close this thread.
Click to expand...
Click to collapse
THREAD CLOSED on request of OP.