Hi everyone.
I have few issues with HTC One m7 (stock phone, upgraded to android 4.4 by itself).
1. When I make a call (using stock phone app) right after using Google CHROME it goes straight to speakerphone. I am not in car mode or using any kind of handsfree device. Then I have to manually return it to normal mode. This happens ONLY after I open CHROME and within few minutes go to make a call. Every time with CHROME and not with any other app.
2. Haptic feedback when typing texts is not working. It is enabled, baterry is full and no battery saving options are enabled. It doesn't vibrate in any app (with writing text available), but with incoming calls and all notifications vibrating works fine.
So are these maybe known issues with kitkat or do I have to take it to service, or you have any other ideas...
Thank you so much!
bobbydoors said:
Hi everyone.
I have few issues with HTC One m7 (stock phone, upgraded to android 4.4 by itself).
1. When I make a call (using stock phone app) right after using Google CHROME it goes straight to speakerphone. I am not in car mode or using any kind of handsfree device. Then I have to manually return it to normal mode. This happens ONLY after I open CHROME and within few minutes go to make a call. Every time with CHROME and not with any other app.
2. Haptic feedback when typing texts is not working. It is enabled, baterry is full and no battery saving options are enabled. It doesn't vibrate in any app (with writing text available), but with incoming calls and all notifications vibrating works fine.
So are these maybe known issues with kitkat or do I have to take it to service, or you have any other ideas...
Thank you so much!
Click to expand...
Click to collapse
your first issue (the speakerphone thing) it is a common kitkat issue, even some users on custom ROMs have it, dont know much about the other issue though
bobbydoors said:
Hi everyone.
I have few issues with HTC One m7 (stock phone, upgraded to android 4.4 by itself).
1. When I make a call (using stock phone app) right after using Google CHROME it goes straight to speakerphone. I am not in car mode or using any kind of handsfree device. Then I have to manually return it to normal mode. This happens ONLY after I open CHROME and within few minutes go to make a call. Every time with CHROME and not with any other app.
2. Haptic feedback when typing texts is not working. It is enabled, baterry is full and no battery saving options are enabled. It doesn't vibrate in any app (with writing text available), but with incoming calls and all notifications vibrating works fine.
So are these maybe known issues with kitkat or do I have to take it to service, or you have any other ideas...
Thank you so much!
Click to expand...
Click to collapse
issue 1 is common and appears somehow related to Chrome. issue 2 is odd - you sure you have vibration turned on settings > language & keyboard > HTC Sense Input > vibration feedback ?
Related
hello all and thanx for your help
this is a new problem, started as a random one and now this is the situation -
I have one of samsung's sounds defined as a ringtone (tried to change, doesn't solve the problem). the volume is set just fine for incoming calls, and vibration is on (and turning it off doesn't matter).
I receive notifications for sms and emails just fine.
BUT the phone doesn't ring for incoming calls!!! I miss almost every phone call I get. restarting the device doesn't help. as i said it started randomally, here and there, but now it happens all the time. I'm not in silent mode obviously, and entering it and then exiting doesn't help.
I tried switching from the samsung launcher to LauncherPro, happens in both.
please help!
Have you put unofficial firmware on the phone .
jje
It happened to me too with an official JPY.
Sent from my GT-I9000 using XDA App
It happened to me before & is due to this NetQin Mobile Manager just uninstall it, hope it help.
Hey guy,
I love this phone and the ability to touch the screen to wake it via the app eXperience Pro.
The only issue is that with the framework / module loaded , when I receive or make a call, the phone would be close to my ears which means that the proximity sensor will shut the screen off. However, when the conversation ends, I wouldn't be able to turn the screen on, either by tapping the screen or pressing the power button.
There are times that when I am not in a call, and my phone is just sitting idle, and when it comes to waking it up, it wouldn't do so. I have to manually restart it just like the issue above. What I noticed yesterday was that my led notification light was on indicating that I had a message. I didn't look at it until after awhile which I realize that I couldn't turn on the phone. The led notification was still working.
Then I decided to call up my phone and I could hear the dial tone from my other phone, however, my xperia Z was sitting idle with its screen off without any ringtone and so on.
I would really like to feature to work flawlessly. Tried it on about 4 ROMs, and the issue persist. Is there any way for me to show the log so someone could figure out whats causing the phone to behave this way?
Without the module loaded, the phone works just fine. I have sent a PM to the developer but have not received any replies since.
not all apps are made for every android phones out there. If its causing issues to your Z, just stop using it or contact the app developer (which you did) and hope for the best.
I dont think there is anyone willing to just make a rom or tweak just for a specific app to function flawlessly on an Z. Especially when its not a super popular app.
LitoNi said:
not all apps are made for every android phones out there. If its causing issues to your Z, just stop using it or contact the app developer (which you did) and hope for the best.
I dont think there is anyone willing to just make a rom or tweak just for a specific app to function flawlessly on an Z. Especially when its not a super popular app.
Click to expand...
Click to collapse
My main concern is what is causing this to happen and to see if other xperia Z users are facing the same issue.
I'm using this app.. For me until now no problem..
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
I have same problem. It's bug?
finalbillybong said:
Using a Nesux 5 on 5.0 when I enable 'mute connected phone' in Android Wear it does not work.
If I press Vol + or - 'Muted by Android Wear' is displayed in the Interruptions menu (if that's what its called?) but the phone still beeps for notifications and rings for call.
I have tried reinstalling Wear as well as clearing the cache.
Has anyone else had this issue? Is there a work around?
Click to expand...
Click to collapse
Yes. I am facing this problem too! Seems like a compatibility bug with Android Lollipop. Might be due to the implementation of the 'Notification Priorities'.
Hope some updates come up soon to fix them!!
I'm running 5.0.1 on my HTC One M7 GE. The mute works with 5.0.1. It's a "priority" mode setting. Where the phone does not ring, but certain notifications may make a sound if they are priority and could be lowered.
Glad it's not just me then. Hopefully it'll be address in 5.1/5.0.1
Fixed in the latest Android Wear app. Version 1.0.5
Also seems to be OK on Lollipop 5.0.1 on the watch! Yay
Hum ... I still have the problem. Mute seems alright for notifications but not for phone ring.
I have Nexus 5 on 5.0 (LRX21O), Gear Live on 5.0.1 (LWX48P) and Wear App 1.0.5..1630507.
Also, I'm using Wear Aware app for being notified on watch if phone is missing, but starting with Lollipop, I have 5 ou 6 false alert each day.
I was working perfectly with KitKat.
May be it is the Wear aware app. I'll try another one.
Maybe 5.0.1 on phone will fix this when it will be available.
For now, our nexus 5 only have 5.0 (https://developers.google.com/android/nexus/images)
Anybody found a solution for this?
I have a possible work around but need help with tasker.
I set up a profile for when connected by bluetooth so that the ringer is off and vibrate is off but because off lollipop it does not work. Think it's the do not disturb option.
In my phones setting-lg g3- i can create a vibrating pattern that is a split second long and really weak.
What i need help with is how to recreate this in tasker. I.e is there a way of changing vibration strength in tasker and pattern.
If so we will be able to create this work around until a offical option is available.
Merry Christmas
Phil
Update;
Couldn't find a way of doing it through tasker despite asking on the relevant forums and hours messing around. Think tasker needs a few tweaks to allow these options to work on lollipop.
Although i found a app that works. I can set a rule to put my phone on silent but the watch still vibrates and visa versa when not connected.
https://play.google.com/store/apps/details?id=com.fancy01.myprofiles
Hope this helps, I'm going to do a few more rules for Wi-Fi, location etc using this app.
Cheers
Phil
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Firefyter said:
I got the watch for Christmas and I have the same issue. My Gmail is muted, but the phone rings and all the other notifications sound off. I have a Nexus 5 running Lollipop 5.01 with the newest version of Wear and 5.01 on the watch. I'll be monitoring this thread for updates...
Click to expand...
Click to collapse
The link in my post above yours is to a profile managing app that does what is required. I'm not sure if the free version works as i can't remember but paid one does.
I created a profile that mutes ringtone, no vibrate with a rule that activates the profile when connected to bluetooth device.
It switches notifications on the watch to priority so don't change that as it will make the phone start ringing/vibrate.
Work around that works
I have the same issue. Here what I do.
Android watch is connected and set to mute apps
Tap the volume rocker (for me nexus 6) and you'll see it says muted. For my work day I leave it on all.
Tap the bell icon and the phone will be put on vibrate. It's working great for the moment.
Best work around I have found.
The issues has returned for me on the latest version of the Wear app....
I'll start with the details of my phone.
Phone/Model: HTC Desire 626s (0PM92)
Carrier: Virgin Mobile
Android version: 5.1
HTC Sense Version: 7.0
So I bought a new phone from Best Buy yesterday, and transferred my old plan over to this new phone. We got everything activated, and made a call to make sure it worked, and the calling was successful. I figured everything was okay until I received a text from my father and my phone didn't vibrate. I checked my settings and put it into vibrate mode, and it still didn't vibrate on the next text. I downloaded Chomp SMS (I have a pro subscription) and used its "Test notification" function to create a notification similar to that made when I receive a text. Next, I contacted VM customer support and HTC Device support and both told me to restart the phone (which didn't fix anything even after several resets), install a sounds manager app (none of which have seemed to work so far), and finally file a defective product report. I'm hoping I don't have to do this. Any suggestions as to how I should proceed?
Easy way to test vibrate:
Go into Settings->Sound & notifications and tap the Sound Profile. Then tap Vibrate - the phone should vibrate as soon as you select Vibrate - if not, then you have a hardware issue...
Sent from my SM-T230NU using Tapatalk 2
jtrosky said:
Easy way to test vibrate:
Go into Settings->Sound & notifications and tap the Sound Profile. Then tap Vibrate - the phone should vibrate as soon as you select Vibrate - if not, then you have a hardware issue...
Sent from my SM-T230NU using Tapatalk 2
Click to expand...
Click to collapse
I'll give you your thousandth thanks!
Weirdly, It vibrated today upon boot, but selecting the vibrate option didn't make anything happen.
Thanks for the 1000th thanks!
Does it vibrate every time you turn it on? My guess is that it's an intermittent problem, but it definitely sounds like a hardware issue... If vibrate is important to you, I'd get it replaced.
Sent from my HP SlateBook 10 x2 PC using Tapatalk 2
Hi all,
my 4X, Miui 9.5.4.0 ROM, will not receive text messages most of the time. I can send texts OK but for the most part I cannot receive a text. I say for the most part because every now and then one seems to sneak through for some reason.
The only messaging app installed is the stock MIUI one that came with the phone. I did try a couple of other messaging apps with the same result. They have since been removed.
Any thoughts or ideas appreciated.
TIA
Greg
ghines said:
Hi all,
my 4X, Miui 9.5.4.0 ROM, will not receive text messages most of the time. I can send texts OK but for the most part I cannot receive a text. I say for the most part because every now and then one seems to sneak through for some reason.
The only messaging app installed is the stock MIUI one that came with the phone. I did try a couple of other messaging apps with the same result. They have since been removed.
Any thoughts or ideas appreciated.
TIA
Greg
Click to expand...
Click to collapse
I can't imagine it's something wrong with MIUI? it never actually happened to me, I'd contact your carrier first, perhaps they have blocked numbers from texting you
I recommend also checking in Settings; System apps > Call settings > Blocklist to see if the phone has blocked incoming test messages from any numbers
snkmv said:
I can't imagine it's something wrong with MIUI? it never actually happened to me, I'd contact your carrier first, perhaps they have blocked numbers from texting you
I recommend also checking in Settings; System apps > Call settings > Blocklist to see if the phone has blocked incoming test messages from any numbers
Click to expand...
Click to collapse
I've just placed the SIM into another phone and it works fine, so it's not the carrier. Checked blocklist and nothing there, plus I can miss and intermittently get texts from the same person.
It's got to be a MIUI thing!
ghines said:
I've just placed the SIM into another phone and it works fine, so it's not the carrier. Checked blocklist and nothing there, plus I can miss and intermittently get texts from the same person.
It's got to be a MIUI thing!
Click to expand...
Click to collapse
Do you notice that you lose signal a lot? It could be a faulty antenna band too, it can be replaced under warranty
snkmv said:
Do you notice that you lose signal a lot? It could be a faulty antenna band too, it can be replaced under warranty
Click to expand...
Click to collapse
No I have a strong signal, so I do not think it's that.
Just did a test:
1. Rebooted phone
2. As soon as the lockscreen appears I sent a text from my wife phone.
3. It is received.
4. Wait one minute and send another 3 texts from my wifes phone.
5. None received.
6. Reboot phone.
7. The 3 missed texts arrive as soon as the phone reboots.
8. Wait one minute and send another 3 texts from wife's phone.
9. None received.
10. Reboot phone
11. 3 missed texts arrive as soon as the phone reboots.
It has to be MIUI.
ghines said:
No I have a strong signal, so I do not think it's that.
Just did a test
It has to be MIUI.
Click to expand...
Click to collapse
That sounds annoying... If you can, go to developer options, and enable "Show all ANR" and use the phone (especially SMS) for a while to see if the culprit is a system process failing to stay alive, and try to clear all data for that process
You should be able to find the process by going to "Installed apps" and enabling "Show system apps"
Researching more on the problem has no real conclusion at all.. Some people solved the problem by just doing a factory reset, some more gets it fixed after calling their carrier, another gets it fixed (temporarily) by just turning airplane mode on and off
snkmv said:
That sounds annoying... If you can, go to developer options, and enable "Show all ANR" and use the phone (especially SMS) for a while to see if the culprit is a system process failing to stay alive, and try to clear all data for that process
You should be able to find the process by going to "Installed apps" and enabling "Show system apps"
Researching more on the problem has no real conclusion at all.. Some people solved the problem by just doing a factory reset, some more gets it fixed after calling their carrier, another gets it fixed (temporarily) by just turning airplane mode on and off
Click to expand...
Click to collapse
I have found the problem. "Turn on MIUI optimization" in Developer Options was turned OFF. Turning it ON fixed the receiving of texts. Tried several times turning it OFF and then ON and texts stopped everytime it was OFF. Don't know what this setting does but it needs to be ON to receive texts.
ghines said:
I have found the problem. "Turn on MIUI optimization" in Developer Options was turned OFF. Turning it ON fixed the receiving of texts. Tried several times turning it OFF and then ON and texts stopped everytime it was OFF. Don't know what this setting does but it needs to be ON to receive texts.
Click to expand...
Click to collapse
That's weird! I have it off all the time, what it does is
1. Closes apps in memory prematurely, this can be bad or good, unused ram is wasted ram anyway
2. Monitor background services and disabled part of it when you're not actually using it, this killed notifications for certain apps for me, at least back in MIUI 8
There's more, but it's really trivial like UI changes it does, happy it's solved though