Database Develop

[Q] Automatically answer incoming calls when Bluetooth is connected

Hello everybody,
I'm struggling to find a way to automatically answer incoming calls on my Moto G 2nd gen (stock ROM) when the Bluetooth headset is connected. When I bought the phone, i.e., before the Lollipop update, I used a third-party application (Handsfree) to answer incoming calls when the Bluetooth is connected. After the update to v5.0.2, neither Handsfree nor any other similar application I found on the Play Store seems to work anymore, and I always have to manually click the headset button to answer the call, which is quite unpractical.
I searched on the internet a little bit, and it looks like this feature has been removed (!!??) with the Lollipop update, but other websites report that the feature is still present in Motorola Assist, which I couldn't manage to get working since I couldn't find any option for automatic answer in the Driving Mode, nor anywhere else. Any ideas? Is perhaps this feature available on some custom ROM, such as Cyanogenmod?
Thank you very much!

Even i am looking for the solution might be lollipop update broken all apps which use to automatically answer the calls

st1led said:
Hello everybody,
I'm struggling to find a way to automatically answer incoming calls on my Moto G 2nd gen (stock ROM) when the Bluetooth headset is connected. When I bought the phone, i.e., before the Lollipop update, I used a third-party application (Handsfree) to answer incoming calls when the Bluetooth is connected. After the update to v5.0.2, neither Handsfree nor any other similar application I found on the Play Store seems to work anymore, and I always have to manually click the headset button to answer the call, which is quite unpractical.
I searched on the internet a little bit, and it looks like this feature has been removed (!!??) with the Lollipop update, but other websites report that the feature is still present in Motorola Assist, which I couldn't manage to get working since I couldn't find any option for automatic answer in the Driving Mode, nor anywhere else. Any ideas? Is perhaps this feature available on some custom ROM, such as Cyanogenmod?
Thank you very much!
Click to expand...
Click to collapse
Tasker can do this, and SO much more. Its brilliant for automating anything on your android device

Duck86 said:
Tasker can do this, and SO much more. Its brilliant for automating anything on your android device
Click to expand...
Click to collapse
Thank you for your suggestion. I tried to achieve this functionality with a Tasker script, taking inspiration from here: tasker.wikidot.com/btautoanswer. Actually, the link seems to refer to some older version of Tasker, because I had to to do slightly different steps. However, the functinality "Take call" which seems to be crucial to do what I want is "unavailable on this device". This is confirmed by the tasker changelog: tasker.dinglisch.net/changes/changes4.6.html
Removed
action Take Call: not available on Lollipop+ (Google not granting the needed permission)
Click to expand...
Click to collapse
How did you do that with Lollipop?

U need to root for tasker to work for picking up the call automatically... google ruined the lollipop

I see. I will try and let you know. Should I see the Take Call action as available upon rooting?

st1led said:
I see. I will try and let you know. Should I see the Take Call action as available upon rooting?
Click to expand...
Click to collapse
so how can i take call with tasker on lollipop?

robertusIT said:
so how can i take call with tasker on lollipop?
Click to expand...
Click to collapse
Sorry for not following up. I don't have access to the device at the moment since the request for help in this thread was originally meant for another person. I won't be able to try the solution bloodhound42 suggested before a couple of months, unfortunately. Feedback is appreciated if some adventurer wants to try first!

Anyone able to run the app called utter!?

OK, I've been wrecking my brain trying to figure out why I can't get the app to run on my note 4. I've been to the devs. Xda page for the app. But he has been mia since February and my post keep getting ignored. I thought I'd make a last ditch effort and try here. Basically the app crashes when I try to launch it. I've downgraded Google search in hopes that it would fix the issue but no luck. I'm running a stock rooted 4.4.4. Any help would be appreciated.

Runs on my stock Rugby Pro running stock 4.1.2 Jelly Bean well enough to allow voice dial and texting from the bluetooth headset on my motorcycle helmet. Without the headset, it is hit-and miss because the app always tries online via wifi first. If in good wifi it still works, but when not good wifi it hangs for a variable (sometimes long) time looking for network. I loaded tasker to toggle wifi off/on when bluetooth is connected, and this seems to fix it well for use daily on my commute by motorcycle. If I drive, I'll probably need to use a bluetooth earpiece. I get the feeling that planets must align for this to work, and it does for me. Developer seems to have abandoned it. I think offline voice recognition - at a minimum for voice dial - should be a mandatory capability for all phones. (And S Voice does NOT work!) If I had not found a fix, I was planning to put my SIM back in the old Rugby II flip and just use the Pro for wifi. They are company phones, and I only went the smartphone route to get company email.
Loading the original Play store version worked for me initially, with no crash issues but still experimenting and learning commands. Then I loaded the latest beta (see page ~ 720 of his main thread) and it seems even better, and Tasker fixed the wifi issue somewhat.
Sent from my LePanII using Tapatalk 2

Thanks for the reply. I have the latest beta install but I still have no luck. I'm wondering if another app such as a antivirus app could be causing it to give me an error.

Doubt it is anti-virus (but possible). Most likely Google Search version or Android version. Check the official thread and find tge ones known to work. I'm just lucky to have a six-month old phone with three-year old software, I guess.

Text and SMS display via bluetooth

Looking for opinions and suggestions for enabling texts and SMS messages to display on the MTCB unit while driving. What, if anything are you guys using?
I searched around already, and found one thread where someone was using tasker and other functions to get messages displayed on the unit from their phone, but that solution didn't appear to be very reliable.
Is there an app that everyone is using? Or am I just late to the party? lol
I realize quite a few of you are using 3G connections with your MTCB, so this conversation is more geared towards those utilizing their Bluetooth only phone connection.

thewesman said:
I realize quite a few of you are using 3G connections with your MTCB, so this conversation is more geared towards those utilizing their Bluetooth only phone connection.
Click to expand...
Click to collapse
Even using a 3G/4G dongle cannot solve the SMS reception problem because these SMS are normally sent to the phone number, not to the 3G/4G SIM number. At most the dongle can be used to send SMS.
ATM no easy solution to this problem (and for social networks use too).

Have you looked at Tablet Talk? I'm not sure it would work over BT since the BT in these devices is locked down, but I believe there is also the option of using Wifi.

The other thread was mine and I was looking for the same thing
As mentioned above, I don't think it's actually possible with these units since it seems the Bluetooth is locked down. Can't remember the specific details but I'm sure it's to do with the Bluetooth service that handles the messages.
I could be wrong though but I know its not possible with tasker anyway and I don't think tablet talk works with Bluetooth cause I looked into that too. At the moment the way I do it is through data which as you say isn't quite as reliable
If you find anything though let me know

dc5daft said:
The other thread was mine and I was looking for the same thing
As mentioned above, I don't think it's actually possible with these units since it seems the Bluetooth is locked down. Can't remember the specific details but I'm sure it's to do with the Bluetooth service that handles the messages.
I could be wrong though but I know its not possible with tasker anyway and I don't think tablet talk works with Bluetooth cause I looked into that too. At the moment the way I do it is through data which as you say isn't quite as reliable
If you find anything though let me know
Click to expand...
Click to collapse
That's why I started this thread, to see if anyone had made any breakthroughs since your initial post. I went ahead and wasted the money on Tablet Talk, and I can confirm that the Bluetooth connection is the issue (Error Code:1) with our units. This seems like such a basic feature that Android would be capable of... my wife's Jeep does it automatically in Uconnect.
One thing I was considering trying with TabletTalk is to go into the factory settings, with the 126 password, and toggle around the Bluetooth type the unit is currently using. I know saving anything in this menu will effectively reset my unit, unless I save settings in Xposed, so I need a block of time to try it that I don't have right now. If it would even make a difference.

thewesman said:
That's why I started this thread, to see if anyone had made any breakthroughs since your initial post. I went ahead and wasted the money on Tablet Talk, and I can confirm that the Bluetooth connection is the issue (Error Code:1) with our units. This seems like such a basic feature that Android would be capable of... my wife's Jeep does it automatically in Uconnect.
One thing I was considering trying with TabletTalk is to go into the factory settings, with the 126 password, and toggle around the Bluetooth type the unit is currently using. I know saving anything in this menu will effectively reset my unit, unless I save settings in Xposed, so I need a block of time to try it that I don't have right now. If it would even make a difference.
Click to expand...
Click to collapse
That's a good idea actually! If I get some free time I'll have a go

"Listen over bluetooth" no longer working

I've searched through the threads but not found this exact issue. I used to be able to activate the moto voice commands over my bluetooth headset. My phone could be in another room and I could activate it. Lately (not sure exactly when it stopped) it seems to have stopped working. I may get it to work 1 in 10 tries but that's it. I've poked through all the menus/settings that I can find that might be related to it and I have had no luck. I've deleted bluetooth profiles, I've even bought a new headset and still no luck. Does anyone have any suggestions to try to troubleshoot this?
Unlocked/rooted MX14 running xposed

Does it still happen in safe mode?

Invalid teleservice ID error when trying to send SMS or MMS

I recently bought a Verizon Note 9 (first Samsung phone) so I'm not well versed on things. I have noticed from time to time when I am not receiving carrier signal (still connected to wifi) my texts will start failing with the error "Invalid teleservice id".
After some digging I noticed that my phone number in "About Phone" was incorrectly set to an invalid number 1-265-000-000.
I have cleared all caches and reset all settings I can think of. This problems occurs on all SMS applications. So far I have tried: Google Messages; Samsung Messages; Verizon Messages+.
Where does the "About Phone" page get populated from?
My hunch is the internal number of the phone is getting set by some screwy logic and that is throwing off everything that relies on it.

Invalid teleservide id soulution found
I need people to test this solution to make sure it works across all devices as the error seems to affect all android devices under certain conditions. If you would like to read how I came to this solution to help me check my work or you are just interested please keep reading, If you just want the solution feel free to skip to the bottom paragraph beginning with SOLUTION. If you try this solution, which I actually believe to be a solution and not a hotfix, please respond with 3 pieces of information: 1) Did it work. 2) What Android device you use and the version of Android you are using and 3) Your ISP (Internet Service Provider).
This data is very important.
STORY:
So, last month I switched to Android for a couple of reasons after having used iPhones since the iPhone 5. The two most important things to me were being able to stream music using the LDAC Bluetooth codec and having a crack at Samsung Dex to see if I could avoid buying a laptop next year. I was immediately happy with these features that had been the impetus for switching, but then something unexpected happened: the thing that I have always taken for granted, i.e. my phone sending/receiving calls and texts, was incredibly unreliable on this phone (Galaxy S20 Ultra). After doing some googling and finding the official forums (there seem to be 2 devoted to this issue and I will post this both places) I found the incredibly disheartening ‘hotfix’ of disabling WiFi calling to be completely unnaceptable. Not only because I don’t actually get cell service in my apartment but because a $1400 flagship smartphone should certianly not have less functionality in any area that an iPod Touch circa a decade ago.
Normally I would just take my faulty device down to a Verizon store because although I am in IT I specialize in computers more than phones, however since we have been in isolation this began an approximately 20 hour saga via the phone over the span of May 25th to June 19th. After trying everything I could glean might work from google, and following every step that Verizon tech support asked me to try and actually convincing them to update the carrier settings on my account I was finally given the OK to get a replacement device. It is important to note at this point that I had only been searching this error for my model phone and mistakenly had the idea that it was an incredibly rare issue that was a problem with a select few devices.
So, you can imagine my complete and udder shock after getting the replacement phone, setting it up, and getting the Invalid Teleservice ID Error 4 on the second text message I tried to send on the device. It took me about an hour to really get my wits together because at this point I was trying to come to terms with the very possible reality that I was not going to be able to use my phone at home reliably because I don’t have good reception over WiFi. When my faculties returned, I resolved to read every post I could find on this issue.
What I found is that this problem has been around since certain people started installing Android 8 on their phones and that they have been trying to get Verizon to offer an actual solution since 2017. So here we are 3.5 years later and almost 4 generations of Android later and “the best network” has so far failed to offer any sort of real solution to this problem. However, from getting the error on my new phone and seeing that the error was effecting essentially every model device Verizon sells (that runs Android) gave me a key piece of data: the problem has nothing to do with the device.
After getting deeper and deeper into some forums I noticed that one person reported that this problem only occurs for them when they use an Xfinity WiFi hotspot. That was my lightbulb moment. I am also an Xfinity customer. I then started searching the problem from that perspective and found that most of the people reporting the error and mentioning their ISP were either Xfinity or Spectrum customers, and now I was starting to feel like I might be onto something.
In terms of IT, networking is my weakest area. Nevertheless I dove into some forums that have tried to approach this problem from a networking perspective and although a lot of it was over my head I started to suspect there was something about the firewall on Xfinity and Spectrum routers that is causing the problem. After 72 hours of exhaustive testing ( not only is 24 hours approximately my previous record for not having the error, but I used that time to send out as much information via text messaging as possible to try to cause the error) I am ready to posit a hypothesis as to what is actually causing the problem and post the solution that is currently working for me.
As I have noticed that the problem is most likely to crop up for me when I am using Dex and a physical keyboard and have tried to send many texts in quick succession, the idea came to me that somehow trying to send a large volume of data exacerbates a problem that Xfinity and Spectrum routers have reliably delivering packets in the right order and format over the internet to the Verizon network. So, this is what I decided to try, and it has now worked for approximately 84 hours straight and has performed flawlessly under stress testing (Spamming 500 word texts and hi res photos to multiple people in quick succession using copy/paste).
SOLUTION:
I’m sure many of you who play video games have used a function on your routers to get around NAT issues called the DMZ. The DMZ allows you to put a device using a specific IP address on your personal network outside of the firewall and connect it directly to the internet. For a device that exists on this network wirelessly there is a simple step you must take first. You must assign your device a static IP. If you go into your router settings you will likely find that all devices on your network are assigned IP addresses via a system called DHCP. This essentially means your device will probably have a new IP every time you leave the house and return, so we need to make it the same every time so that the DMZ will function the way we want it to. Every router is going to have a slightly different settings menu, but you should be able to find a tab that lists the CONNECTED DEVICES on your network. What you need to do is change your phone from being a DHCP connected device and assign it a STATIC IP address. Finding the option to do this may be harder than actually doing it, all you need to do when you find the option is change the connection type from DHCP to Static and pick and IP address that will work for you. My network uses 10.0.0.XX for the devices on my home network so I assigned my phone to 10.0.0.99. Then I placed the 10.0.0.99 in the DMZ. In my router menu, the DMZ is under ADVANCED SETTINGS and when you select the DMZ tab, simply enter the IP address you chose for your phone.
To recap:
1) Set your phone to a static IP
2) Put that IP in the DMZ
That’s it. A valid criticism of this solution is that your phone is less secure, however I would respond that the likelihood of your phone being hacked is much smaller that that of a PC and if this slightly loosened security really bothers you, just use a VPN. A VPN will keep you safe in a Starbucks on their free public WiFi and it can protect you here (I actually had a VPN when I got my device and originally I thought it was the cause of the Invalid Teleservice error). CAUTION: There has been a crop of predatory VPN services lately that provide working VPNs, but will charge you a ridiculous amount. I use NordVPN (I found a code on YouTube that gave me 70% off six devices on a 3 year plan, that ended up costing about $100) but there are plenty of good services that will allow you to connect to the internet via a VPN on one device for approximately $2-3 a month.
So please, try this and report back. This error has been the bane of my existence since switching to Android and it is completely unacceptable that Verizon has had literally years to do figure out a solution to this problem and yet they have not. My end goal is not to receive credit but to make sure that in the future Verizon Tech Support actually knows how to help people solve this problem, and their techs don’t take your calls and then look the problem up on google, proceeding to be completely transparent in terms of having no actual knowledge of this issue and literally reading the same forums I have already been over and suggesting the non-solutions posted there in order, i.e. turn off WiFi calling and if that doesn’t work turn off ‘Advanced Calling’.
REMEMBER: If this solution does not work for you, please double check that your changes the router you use have stuck. I have previously had routers that will for reasons I don’t understand change the DMZ domain or switch a device back to DHCP from static or simply fail to save your changes properly.
I await responses eagerly.

You need to take your device to your local high street retail branch of your cell provider and ask them to check your SMS/MMS settings

I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.

K_A_Beausoleil said:
I would love to be able to actually go into a brick and mortar Verizon store but that's currently not possible in WA state. I had to have a tech walk me through checking those settings myself (after doing my own research as well) and had somebody at level 3 of tech support at Verizon manipulate my carrier settings. That's pretty much all I can do during the pandemic.
My solution is still working for me though, however 33 min after I put the same post on the official Verizon forum they closed the thread which had had regular posts over the last 3 years so now I'll never know if it works for anybody else. Additionally, there was somebody on the forum who approached the problem from SMS/MMS settings perspective and it had to do with deleting server settings and whatnot. It was so complicated that I doubt many end users could follow the same steps.
Click to expand...
Click to collapse
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
---------- Post added at 04:37 PM ---------- Previous post was at 04:05 PM ----------
hkjxda said:
Thanks for your efforts. I've had this same issue on my Note 9 for 2 years... Your solution did not work for me.
However, I found a solution this morning. My ISP is not Xfinity or Spectrum. But my network which is spread across a small community blocks some IPsec ports that are required for wifi calling. Enabling those ports on my router does not fix the problem since it is a network/modem setting that I don't have access to.
What does work is having a vpn profile that implements IKEv2/IPsec VPN tunnels on your Android device. I have a NordVPN subscription and downloaded the StrongSwan VPN client from the Play Store. This client only uses IPsec encryption. Using a NordVPN server that has this encryption with the StrongSwan VPN client has allowed me to bypass this network restriction and my wifi calling phone calls and texts go through just fine now.
Hoping this helps someone else...
Click to expand...
Click to collapse
Scratch this... Wifi calling uses it's own IPsec VPN tunnel, VPN clients only encrypt internet traffic, not cell service. Back to square one...