SMS Bluetooth App - Ornate TrueSmart

So I found this app which looked really promising but unfortunately doesn't work for me.
Basically would let our Omates send/receive sms via our phones Bluetooth while using our existing phone number. Would be great to not have to rely on wireless or a sim card with a new number.
I was never able to get the Bluetooth to work as it never connected with phone. Im not sure if it is a issue with my phone or with my Omate.
If someone wants to try and see if it works that would be great. The program is $2.99 but you can just refund withing 15 min if it doesnt work like i did.
Heres a full description & link:
Tablet Talk is a tablet SMS texting app that lets you text from a tablet and even make voice calls, while your phone stays in your pocket! It works with all Android tablets, including Nexus, Galaxy, Note, and Kindle Fire tablets. Unlike other apps, Tablet Talk doesn't force you to use a new phone number... your friends, coworkers, and family can contact you with your existing Android phone number. In addition, Tablet Talk does not require an Internet connection, does not store your data, and does not eat your battery!
https://play.google.com/store/apps/details?id=com.apdroid.tabtalk
Does anyone know of another app like this we could use?
Thanks

BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet

Lokifish Marz said:
BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet
Click to expand...
Click to collapse
darn that stinks. hopefully one day lol
thanks Lokifish

AndroidFileHost said:
So I found this app which looked really promising but unfortunately doesn't work for me.
Basically would let our Omates send/receive sms via our phones Bluetooth while using our existing phone number. Would be great to not have to rely on wireless or a sim card with a new number.
I was never able to get the Bluetooth to work as it never connected with phone. Im not sure if it is a issue with my phone or with my Omate.
If someone wants to try and see if it works that would be great. The program is $2.99 but you can just refund withing 15 min if it doesnt work like i did.
Heres a full description & link:
Tablet Talk is a tablet SMS texting app that lets you text from a tablet and even make voice calls, while your phone stays in your pocket! It works with all Android tablets, including Nexus, Galaxy, Note, and Kindle Fire tablets. Unlike other apps, Tablet Talk doesn't force you to use a new phone number... your friends, coworkers, and family can contact you with your existing Android phone number. In addition, Tablet Talk does not require an Internet connection, does not store your data, and does not eat your battery!
https://play.google.com/store/apps/details?id=com.apdroid.tabtalk
Does anyone know of another app like this we could use?
Thanks
Click to expand...
Click to collapse
I got this app to work. I figured I've blown more than $3 in my life of silly stuff. I've only tested it once, but it was fun to reject a call from my wrist.
First part:
Both devices are initially detected as a phone. You have to manually go in on the TrueSmart and switch it to "tablet". (Menu->Settings->Setup->Device Type)
Second part:
The bluetooth pairing screen is too big. (It was written for a tablet, no doubt.) If you installed "App Settings" module for Xposed, switching the DPI to 80 will get you past the pairing screen, after which you can put the DPI back to default.
Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls.
Post back if you try and it works or doesn't.
jd

jdommer said:
I got this app to work. I figured I've blown more than $3 in my life of silly stuff. I've only tested it once, but it was fun to reject a call from my wrist.
First part:
Both devices are initially detected as a phone. You have to manually go in on the TrueSmart and switch it to "tablet". (Menu->Settings->Setup->Device Type)
Second part:
The bluetooth pairing screen is too big. (It was written for a tablet, no doubt.) If you installed "App Settings" module for Xposed, switching the DPI to 80 will get you past the pairing screen, after which you can put the DPI back to default.
Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls.
Post back if you try and it works or doesn't.
jd
Click to expand...
Click to collapse
Awesomw trying it now. Do you have a link to the xposed app settings. The one i just tried didnt work when telling it to change the dpi
Thanks

AndroidFileHost said:
Awesomw trying it now. Do you have a link to the xposed app settings. The one i just tried didnt work when telling it to change the dpi
Thanks
Click to expand...
Click to collapse
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd

jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
most likely its the ts. i own a moto x and have had nothing but issue maintaining a BT connection with the watch. the ts drops the bt connection after 30 secs

rhineymac said:
most likely its the ts. i own a moto x and have had nothing but issue maintaining a BT connection with the watch. the ts drops the bt connection after 30 secs
Click to expand...
Click to collapse
I am having the same issue with the BT on my OTS. It drops connection with my Moto X pretty fast.

Same thing here - about a 30 second connection between the TrueSmart and my stock Nexus7 2013, then it drops.
Sent from my Nexus 5 using Tapatalk

If the range is poor it's an antenna issue. Otherwise it's the firmware.

Lokifish Marz said:
If the range is poor it's an antenna issue. Otherwise it's the firmware.
Click to expand...
Click to collapse
defiantly the firmware on mine dont think its a bad antenna. Really hope they get on the ball and fix this stuff. I cant even get the bluetooth to see my cars bluetooth or headphones. Not sure whats going on. Really frustrating I cant use it for the things i bought it for.
If it is a bad antenna I doubt I'd be able to even request a replacement since every email to them seems to go into a black hole lol

jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
Ya i did his patch but dont have xposed installed. Redid the patch and still nothing. Ill keep tinkering with it. Once i get the dpi working ill test this out further.

AndroidFileHost said:
Ya i did his patch but dont have xposed installed. Redid the patch and still nothing. Ill keep tinkering with it. Once i get the dpi working ill test this out further.
Click to expand...
Click to collapse
xposed and it's required files do not come preintalled with the final release of the patch.

Lokifish Marz said:
xposed and it's required files do not come preintalled with the final release of the patch.
Click to expand...
Click to collapse
ya i looked through the patch and didnt see it so im installing it manually. Thanks for the reply

Lokifish Marz said:
BT paring/tethering in that manner does not work on any of the x201s.
What works;
Phone > BT Pair/Tether > x201 w/ SIM > Data/Internet
What doesn't work;
x201 > BT Pair/Tether > Phone w/ SIM > Data/Internet
Click to expand...
Click to collapse
jdommer said:
I'm still battling this. The app works perfectly on wifi, but very unreliable on bluetooth. Unfortunately, my phone is an SGS3 running CM11 and the bluetooth there is only slightly more reliable than the bluetooth on the TrueSmart so I'm not sure where the problem lies. I haven't gone through the app maker's FAQ yet, and am hopeful I can make it work.
Anyhow, to answer your question:
If you installed Loki's patch, you should have an app called xposed installer. Make sure you have gone in the framework section and done install/update and the reboot required after.
Then go back into the xposed installer and into download. Down in that list somewhere you should find the App Settings module. Download that and install it.
Then go back and into the modules menu. Make sure you have a checkmark in the App Settings module and reboot again.
Now, you can go into app settings (should be a normal app - or you can navigate to it through xposed installer and modules then click on App Settings) and choose the Tablet Talk application and change its DPI to 80. Instead of switching it back to "0" of no override after, I've got it on 92 right now because that makes the dialer portion of the app usable for tablet talk. If you don't care, you may want to go back to default.
Good luck!
jd
Click to expand...
Click to collapse
So i got it to work over bluetooth with the instructions your provided. I can send text messages but it doesnt show any recieved. So thats better then nothing I guess lol. Ill keep tinkering with the settings. Not sure why its not syncing the responses.
Also not being notified of phone calls either but i can make them. So not sure if its just some setting i have wrong that is not letting notifications and things come through. Any ideas?
This didnt help
"Third part:
The app settings by default don't relay phone controls over to the tablet (watch) so you need to change the settings to make this happen. From the watch, Menu->Settings->Caller ID/Phone Calls"
On the phones app it shows the sync log and does show the text messages but the watch is not receiving them. There is a setting on the phone app that says Incoming SMS Fix. Use only if your phones sms app blocks tablet talk from receiving messages.
That doesnt fix the issue. Wonder why you were able to block a call on your watch but I cant.
Ill keep tinkering.

AndroidFileHost said:
That doesnt fix the issue. Wonder why you were able to block a call on your watch but I cant.
Ill keep tinkering.
Click to expand...
Click to collapse
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd

jdommer said:
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd
Click to expand...
Click to collapse
ok gotcha ya i hope the mythical update makes this work it would be awesome. Im going to write to the developers of the app to see if they can adjust it to better fit on the watch. I doubt they will but cant hurt to ask.
Really hope we see a bluetooth fix for the omate this month but i highly doubt it lol

jdommer said:
Glad you got it partially working. It looks like the problem is with the BlueTooth on the watch. It can send data to the phone, but it doesn't receive the responses.
The time I did get the call to show up on the watch, I had switched it over to WiFi connect mode. I only realized that after I had already posted.
Anyhow, the app looks pretty decent. Maybe the infamous mythical future firmware update for the watch Bluetooth with fix everything[tm].
jd
Click to expand...
Click to collapse
Ya i got it to receive a few times but defiantly is the bluetooth on the watch being funky

AndroidFileHost said:
Ya i got it to receive a few times but defiantly is the bluetooth on the watch being funky
Click to expand...
Click to collapse
At the cost of battery life, ive been running this semi-reliably using my phone as a hotspot and using tablet talk's hotspot mode feature, and connecting on the "tablet"/SmartWatch using wifi mode. Using it like this only makes me wish it worked properly over Bluetooth because short of forwarding all notifications, this is a great great app.

Helgaiden said:
At the cost of battery life, ive been running this semi-reliably using my phone as a hotspot and using tablet talk's hotspot mode feature, and connecting on the "tablet"/SmartWatch using wifi mode. Using it like this only makes me wish it worked properly over Bluetooth because short of forwarding all notifications, this is a great great app.
Click to expand...
Click to collapse
Someone over at Google+ suggested Tablet Notifier. I have received call notifications and SMS successfully over Bluetooth with it. No sending SMS, but that is really not a big deal for me; I hate typing on the watch. Only tried it for a few minutes, but the more of us breaking it, the faster we find if it breaks.
jd

Related

[USER][CM7] Bluetooth tips and tricks...and questions

Hope I'm not duplicating anything, but there seems to be a lot of BT related questions and none answered in one unified place. Also I think the BT Dev thread should be left to the devs (to keep it easier for them to work on things, rather than help us mere mortals ).
This applies to CM7 (latest nightlies, Tablet Tweak RCs) ONLY (as far as I know).
So, if bluetooth does not turn on, there a few things that you can try.
Do a HARD reset (that is, hold down the power button until the NookColor turns off, then start it back up.
Fix Permissions in ClockworkRecovery:
Boot into CWR (w/SD, load it in. With CWR installed on eMMC, go to ROM Manager > Reboot into Recovery. Alternatively, hold down the power plus "N" button for ~8 seconds (from a shutdown NookColor).​
Try both!
An interesting thing to note is some users (myself included) can only start up bluetooth within a pretty short window of time after the NC has booted up. Not sure why timing is important, but could be a factor for those who cannot start up BT after some given time of operation.
I found this tip that may work after a fresh (read: wipe system/data) install, but may also work after flashing a nightly over a nightly.
If you're ready to turn on Bluetooth, there's a trick. If you don't do this, Bluetooth will just refuse to turn on / be enabled.
Turn off wifi (Settings > Wireless & Networks > Wi-Fi)
Reboot
Turn on Bluetooth (Settings > Wireless & Networks > Bluetooth)
Turn on wifi
It seems a bit odd, but that's what you have to do. From then on out it'll work fine.
Click to expand...
Click to collapse
Credit here (step 2)
For a list and description of devices that work with the NC, check this out:
Known functional Bluetooth devices
For tethering data via BT, try android-wifi-tether. While it can be used to create an access point on your phone via wifi, you can also opt to use BT to create the tether. This works well in conjunction with TetherGPS which I use to provide GPS info to the NC from my G1 while using CoPilot Live to show navigation (I don't have data on the G1).
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
ace7196 said:
Tried that previously and it did not work for me.
In other words, it works as with all the kernels I've tried (your OC'd and stock kernel): it will start up if I start is quickly, but otherwise not.
Click to expand...
Click to collapse
me too. I went back to 4/4 since them. If I leave BT on all the time, it is on when I boot, but if I turn off BT and reboot, it won't come on without a hardboot (holding down power.)
Fix permissions is NOT needed, just a hard boot.
dalingrin said:
If you have the BT enable problem try this kernel and let me know if it changes anything:
http://forum.xda-developers.com/showpost.php?p=12683824&postcount=1754
Click to expand...
Click to collapse
For the last few days Ive been trying to get BT working w/ my car stereo, using phiremod 5.3
I have no problems enabling Bluetooth (first time I had to reboot a few times and fix permissions)
With it flat against the stereo, I'm 'paired but not connected' and getting it to actually connect usually takes 4 - 5 tries.
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.
Seems like it changed something on my end...
Just figured I'd mentioned it.
(I can go back to the other kernel, or a different version of cm7, and see if I get the same connecting/ stuttering problem, if you thing it would help)
Btw- thanks so much for sharing all of your hard work!
breebauer said:
After its connected- when I try to play any kind of music, it gets stuck every few seconds- and stays stuck for more than a few seconds (like 10) and plays again.
I just downloaded this kernel, (wiped caches, fixed permissions again) and it connected on the second time, and only got 'stuck' once for maybe 2 seconds, and played the rest of the song with no problems.!
Click to expand...
Click to collapse
I dont' know if anyone who's building from source wants to take a look at this patch committed 3 days ago on the omapzoom tree to frameworks/base, but it seems to address a bluetooth corruption problem.
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Check out this posting:
http://forum.xda-developers.com/showthread.php?t=1024963
I believe you also need the Bluetooth GPS Provider app from the market.
Calla969 said:
Can anyone who's using the copilot app tell me exactly how to get it set up? I can get the GPS signal to the nook but then I get an error about an invalid imei number.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
I'm running Phiremod v5.3 cm7 from emmc and cm7 nightlies from sd card. I usually have a data sd card but can switch it out. I have updated the cm7 sd card before. Not sure which nightly and OC I used last. Could use ClockWorksMod to flash this kernel to Phiremod v5.3. Could replace the kernel, uImage, on the SD card. Usually there are different kernels for emmc and sd card.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Question: will 'Wireless Tethering' work in place of 'tether-wifi'? Or does it -have- to be 'tether-wifi'? Thanks!
any software will work that tethers.:-D
ace7196 said:
Never had an issue with the IMEI number, but here's how I got it setup.
Start with the TetherGPS app running server on the phone and client on the NC, as well as tether-wifi from google running on the phone, then connect to the AP on the NC
Next, open/install the app. It should read the GPS data from the phone
Now, switch back to a wireless connection with internet access, download the voice, then enter the serial/etc...
Finally, load the app back up after all the registration stuff 'n things, and use the "internet" connection from the phone to grab the GPS info.
Click to expand...
Click to collapse
Apparently the latest version of Copilot has introduced this error. I have spoken with tech support regarding the issue and they told me that they are aware of the problem and will release an update early next week that will fix the problem. Apparently if you have version 8.2.504 it works, but the new version breaks it. The dev won't send me a copy of the old version, so I guess I'll just have to wait and hope.
lschroeder said:
Copied and edited from cm7 user thread.
I have xoom bluetooth keyboard with disconnect issues. Would the special kernel help with this?
From the accessories thread. "I found a work-around. Download the app Bluetooth Keyboard JP, change the settings in settings > Language and Keyboard to that app, then connect the keyboard." Anybody else try this or others? Blue Input is another one. I know of one more but can remember its name.
Another issue: When I have the keyboard active and playing flash files from the internet, it seems to buffer more. If I move the keyboard out of range or use settings to disconnect the keyboard, the buffering is less and the flash files play better. I have cyfi bluetooth external speakers. When I use them I get the same buffering issue, so I just use an external player through the headphone jack instead.
Click to expand...
Click to collapse
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
breebauer said:
Does anyone know where (on the Nook) the BT chip/antenna is located?
It might help to know, since the range is so limited...
Click to expand...
Click to collapse
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
khaytsus said:
http://www.zdnet.com/photos/nookcolor-teardown/487636?seq=62&tag=content;photo-frame#photo-frame
So across the bottom and up the right side as you hold it portrait.
Click to expand...
Click to collapse
Thanks! That makes a big difference...
(For some reason, I was thinking it was on the upper left corner- not sure why)
chisleu said:
I don't know if that is a solution, but the problem appears to be a conflict between wifi and bluetooth. Turn off wifi and most of your keyboard problems will go away.
Also there is an app on the market called "Null Keyboard" Which simply turns on a keyboard device that disables everything keyboard related. It doesn't disable bluetooth input, but it gets rid of the long-press pop ups and is suppose to solve other issues as well (including the software keyboard popping up every time you want to type.)
I haven't had time to install it, but it's purchased.
Click to expand...
Click to collapse
I was just using google voice to text from several feet back. In fact it was hard to read the small print from that distance. I did not realized that keyboards have a larger range then headsets.
Testing Bluetooth Keyboard JP now. Force closes, so just switched to swift keyboard I downloaded from amazon app store for free. To get out swift keyboard and get a null keyboard, I hit the back key on the xoom keyboard, then the virtual swift keyboard no longer shows up.
@chisleu do you have a link or instruction to modify bluetooth keyboards so that keys can have their mappings corrected. Xoom has some correct and some wrong or disabled under CM7.
Couldn't get BT to work at all however powering down while the wifi is off, and turning the bluetooth on before the wifi made it works on the first try. Was streaming Slacker to my stereo in a matter of minutes. Wifi doesn't seem to interfere with the BT audio stream at all, audio sounded crisp and perfect. Range however was still limited to a foot or so.
Hoping there is a possible hardware mod that can hook up an antenna to the BT chip. I'd be in heaven if I had full BT functionality on this beast.
FYI, Although I don't have any RF experience I'm still an electrical engineer so if anyone can toss me a bone on the PCB layout or pinouts of the nook I might be able to try stuff to boost the range.
What is the feasibility of adding dial-up networking client support to CM7? Some folks are able to tether their NC to their phone using an ad hoc wifi network, and others have had success via a Bluetooth personal area network (PAN) using the "pand" utility. Unfortunately, I have a Blackberry phone, and it does not support the PAN profile. It does, however, support dial-up networking (DUN) over Bluetooth (confirmed with a Windows laptop).
According to https://sites.google.com/a/android.com/opensource/projects/bluetooth-faq, "dund" is the client utility that is needed to establish a dial-up connection from Android to another device. When I run this command on the NC, it says "dund: not found". I'm not a developer and don't know how much effort would be involved in adding this functionality to the build. Is it just a matter of including the binaries, or is there additional development work involved?
Thanks in advance..

Tablet Talk App

So since I've been using tablets since the xoom came out I always wanted to be able to send texts through my tablet but have them send with my phone's number. At first there was syncSMS, which was pretty good but required drop box to sync up messages. Then I started using Text tab which would pair the devices with BT. The app was ok, the interface wasnt that great but it did the job. I just bought Tablet Talk from the market and I have to say I LOVE this app, not only does it give you the option to connect via BT or Wifi(must be on same wifi network) but the interface is much better than text tab. Plus you can control your mobile phone. Meaning, if you want to call someone it has a dialer and when you dial from your tab it will place the call on your handset, you can even activate speakerphone on your mobile phone. Granted you need to have your phone close for the calling stuff and I am wondering if you connect the two via BT if you can actually use your tab to talk(I havent tested on BT yet) but I think it's still pretty neat. And when you get a call it displays the caller id number on your tab so no more having to pull the phone out of your pocket to see who's calling.
I have been using it over wifi since last night and havent even seen it eat much battery at all and I left it running all night. Anyway, I would HIGHLY recommend this app... It's the best Tab/Phone SMS app I've seen so far
ok so no audio routing when connected via BT, but it's still a pretty cool feature
When I get a call it shows me who is calling on my tab, and also rings on the tab. You can answer the call from the tab but it activates the handset, but as I said in the OP from the tab you can also activate the speakerphone on your phone
Try...
Tablet Talk
Routes calls and texts.
Sent from my ADR6425LVW using Tapatalk 2
RED ZMAN said:
Try...
Tablet Talk
Routes calls and texts.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
it routes the audio as well?
edit: My bad... that's the app I have.. lol I dont know why I thought it was Tablet Text. I dont see a way to route the audio though. It just activates the call on the phone
Is there a way for it to recognize the hotspot app on your phone as the wifi network? I have the hotspot on my phone enabled..but it still ask me to connect to a wifi network.
Have you tried the Sidecar app? It is available in the Play market.
mrkrabs said:
Is there a way for it to recognize the hotspot app on your phone as the wifi network? I have the hotspot on my phone enabled..but it still ask me to connect to a wifi network.
Click to expand...
Click to collapse
hmm not sure.. I havent tried.. but why not just connect via bluetooth?
I haven't tested it extensively, but it definitely looks like a good app. I will be testing it more once I start making progress on installing the tablet in the car.
I bought it the other day and wished I did the trial first. It does work well, but my phone seems to disconnect often from Bluetooth. So then I have to manually turn the screen on and reconnect.
Guess I need to fool with the settings on my phone some more. It's very useful, except for this little quirk I'm having.
Sent from my PG86100 using xda premium
KB112 said:
I bought it the other day and wished I did the trial first. It does work well, but my phone seems to disconnect often from Bluetooth. So then I have to manually turn the screen on and reconnect.
Guess I need to fool with the settings on my phone some more. It's very useful, except for this little quirk I'm having.
Sent from my PG86100 using xda premium
Click to expand...
Click to collapse
hmm that's odd. Email the dev, I emailed him a couple of questions and he replied pretty quickly. The first time within hours of my email, the 2nd one a day or two after.
It seems to be an ics issue on the Evo 3D leaks. All of them have this issue for me. That's why I think I need to play around in my wifi settings a bit. Thanks for the suggestion though
Sent from my Clean Rom'd HTC Flyer using XDA Premium.
i bought the app but i cant install it on my phone with over 300mb free i need help keeps sayin i need to free up space
edit- i fixed it by jus pushing it to the phone via adb

[Q] no push notifications on wifi with KK

I upgraded my phone to KK back in late december and have been on it ever since but one problem has plagued me since then and I'm hoping to get some insight here. heres the problem...
When im connected to wifi (and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.Often i turn my screen on and get a barrage of notifications that i should have gotten hours ago. Ive tried all the sleep modes and Ive tried turning off wifi optimization.Nothing works and I know for fact it did not do this on JB.
I DO get text messages and phone calls instantly though but nothing else will wake my phone up. While i do enjoy the deep sleep, i would like to get my notifications in a reasonable amount of time without having to turn the phone on to check them.
Has anyone else had this "problem"?
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
SteveMurphy said:
Nope. Have you looked into what is and isn't checked in your Google Settings? There's a Play Games tab that allows you to mute certain games, essentially stopping their notifications. I don't suppose you've messed with that, have you?
It's strange, I've not really heard of this, especially since you're getting texts and such.
Click to expand...
Click to collapse
Yeah i know and I've googled it to death for a few months now. I'll check g settings but idk why that would stop gmail. It's like when I'm on Wi-Fi w/ the screen off its just a plain old dumb phone. I turn the screen on and the notifications just flood in.
Edit: nothing in g settings is muted. The only thing i can think of is i don't have app data synced in accounts.
I think i figured it out. I had "sync app data" unchecked in accounts. So far I've been getting notifications screen on and off. Now if someone will just play back to me on wwf...
EDIT: i may have spoke too soon. It still doesnt wake up without turning on my screen
hey @SteveMurphy do you by chance use the active display?
razen_kain said:
hey @SteveMurphy do you by chance use the active display?
Click to expand...
Click to collapse
I did when I was using Omni and it worked great. I haven't used it since running RR, however.
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
razen_kain said:
[...](and this is only with wifi, not MD) I don't get my push notifications (gmail,fb,words,hangouts,etc) when the screen is off.[...]
Click to expand...
Click to collapse
cyril279 said:
So you're wifi connected, and have actively turned mobile data off? I have never even tried that...
If, however, you mean that this happens only when you're connected to WiFi, then no, I have not experienced this issue.
The only other setting that I can think of that pertains to sync is in system settings > Data usage > settings > [ ] auto-sync data, but I don't think that would cause the awake-vs-sleep sync issues that you're describing.
I used to use Active display, I currently use AcDisplay, I'll likely go back to using the baked-in active display.
Click to expand...
Click to collapse
No i never turn mobile data off. I just meant that notifications come as expected when I'm on mobile data but on Wi-Fi, once the phone hits deep sleep (<a minute) i won't get notifications unless i turn the screen on.
I ask about active display because i remember when on resurrection ROM i was using it and getting notifications then and kind of forgot about it but I'm on PAC 4.4 now and it's doing it again. However i was using the init.d scripts they have baked in but have them all turned back off now to see if that fixes it.
It's the strangest thing I've seen. It's like when I'm on Wi-Fi and turn the screen off it just disconnects from all data even though i can plainly see that it is not. Angela has the same phone with the same settings as mine but on RR 5.0.5 and she gets notifications fine.
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
razen_kain said:
@cyril279 I knnow this is off topic but have you tried this AD app? Its got some other features/customizations that aren't on the built in AD
https://play.google.com/store/apps/details?id=com.greatbytes.activenotifications
Click to expand...
Click to collapse
cyril279 said:
That was actually one of the first active-display variants that I tried. It worked well, but there were a couple hiccups that kept me shopping. The add-on AD clones have great features, but they don't play well with the stock lockscreen, or they leave the [home] button active, or involve significant lag when evoking the notification. The baked-in clones operate fluidly, but without the cool-stuff. I haven't tried active notifications recently though, maybe the updates have smoothed things out. I'm definitely down to try it again.
AcDisplay's development has been re-directed by Motorola. It's still my favorite of the clones, the beta version is boss, but it still isn't as fluid as the built-in boring-ol Omni AD.
Click to expand...
Click to collapse
Well all my testing so far has lead me no where with the exception of using that app. So far, I've not been able to reproduce the problem while using it. The question is,"what is it doing" to make it work....
EDIT: The app does not fix it....
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
razen_kain said:
just thinking out loud herebut, could this be a kernel issue? Im currently using PAC's kernel that comes packaged in the rom. Maybe I should try @RenderBroken 's kernel...?
Edit: Using RB's kernel breaks some of the PAC features and it did not fix my notification issue
https://code.google.com/p/android/issues/detail?id=42272
Click to expand...
Click to collapse
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms. Are you only having issues trying to get PAC running on your phone? Is it KK or JB?
Click to expand...
Click to collapse
Its 4.4 and I have faced this issue on every rom Ive tried since switching to KK. Im starting to wonder if it's not an issue with my wifi. Im wondering if maybe my wifi is suspending my connection when my phone goes quiet.
RenderBroken said:
PAC uses a modified ramdisk compared to other CM derived roms...
Click to expand...
Click to collapse
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
SteveMurphy said:
Render, great information as always. razen, I'm no help to you on this - just felt like popping in to say "hi".
Click to expand...
Click to collapse
It's always good to have you around buddy.
[SOLVED] Not Receiving Notifications on WiFi
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Great news, glad it was an easy fix!
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
Great news! Now you just need to install DD-wrt on your router and turn it from a $40 router to a $400. I know you like to tinker but check it out. ITs free and its just firmware for certain routers. It turned my old wrt54g into a baus
razen_kain said:
My suspicions have paid off!! I started suspecting my router was the culprit so i pulled out my old netgear2400 and hooked it up and low and behold my notifications starting lighting my phone up again!!
The problem was the Xfinity router that came from comcast. Apparently it was closing the "heartbeat" line to stay connected when the screen was off before the heartbeat would send again, if that makes sense.
For the time being I'm going to just use my netgear router BUT I was able to fix the problem with the Xfinity router by using an app called Push Notification Fixer. Just install it, follow the instructions, and set the WIFI/mobile data heartbeat to the recommended settings. If that don't work start shortening the heartbeat time. It'll make sense when you see the app.
Hope this helps someone else along the way. I went a LONG WAY down the google rabbit hole before I figured this one out.
Click to expand...
Click to collapse
I'm having the same issue with KitKat CM11 ROM on my HP Touchpad (which is WiFi only), and will have to try this. Notifications come in instantly on my iPhone/iPads, but my Touchpad gets some serious delays...sometimes right away, and sometimes delayed.
By the way, did "Sync App Data" setting for an account have anything to do with push notifications, or is that more for backup purposes?
---------- Post added at 02:32 PM ---------- Previous post was at 02:04 PM ----------
Oh darn, mine is still delayed even with the push notification fixer installed and WiFi heartbeat at 5min. Even after I've just rebooted my Touchpad, actively using it, and not even 5 minutes has passed. Delay was 8 minutes and then the notifications came streaming in.
With Android/KitKat, do you have to have the app open in the background for push notifications to go thru? Or run the app at least once after a reboot?

Advanced calling is officially online

No need to do the workarounds anymore, if you're on Lollipop now just go to Advanced Calling and activate it!
GigaSPX said:
No need to do the workarounds anymore, if you're on Lollipop now just go to Advanced Calling and activate it!
Click to expand...
Click to collapse
I'm assuming that would mean official lollipop is iminent
GigaSPX said:
No need to do the workarounds anymore, if you're on Lollipop now just go to Advanced Calling and activate it!
Click to expand...
Click to collapse
cool I'm going to delete my workaround if I can figure out how. Wonder if it's 509... And I just read a post on here about stagefright 2.0 ****ing bullshat so our phones are still vulnerable to specialy modified mp3 and mp4- so someone can do remote executions. but so is everyone elses phone...
I do hope this is something positive, not getting to hopeful just yet, have not seen any indication of a OTA yet.
1linuxfreak said:
I do hope this something positive, not getting to hopeful just yet, have not seen any indication of a OTA yet.
Click to expand...
Click to collapse
What differences do you hope in seeing in the OTA from what's already out?
GigaSPX said:
What differences do you hope in seeing in the OTA from what's already out?
Click to expand...
Click to collapse
Final build, did you say the or someone else that the .ftf R4C still didn't have the Stagefright patch? I do hope the final release has that patched and the new Stagefright 2 patch as well.
I have beta tested Winders/Linux and other software for years and the final release is well final, may be some bugs still but most are squashed and gone.
This is not my first pony ride, although I have not posted on XDA I have been active in the Android community since the first Moto Droid, just not on XDA.
Have used Linux since Red Hat then Corel days, Google it.
Thanks for the heads up. I was able to activate it from the My Verizon app on stock KitKat. I've never flashed lollipop either
cccthestyle said:
Thanks for the heads up. I was able to activate it from the My Verizon app on stock KitKat. I've never flashed lollipop either
Click to expand...
Click to collapse
that's interesting so we could have had this all along. I thought kitkat didn't support advanced calling natively that's what I've read and I know our phones don't have dual radios so I don't get it I want to revert back to test it but I will take your work for it. Do you actually have 4g when on a call now. and can you use the Internet while on the phone.
Tigerhoods said:
that's interesting so we could have had this all along. I thought kitkat didn't support advanced calling natively that's what I've read and I know our phones don't have dual radios so I don't get it I want to revert back to test it but I will take your work for it. Do you actually have 4g when on a call now. and can you use the Internet while on the phone.
Click to expand...
Click to collapse
We wouldn't have had this all along because in the my verizon app if you tried to add the advanced calling feature to a line with an xperia Z3v you'd get an error saying it wasn't a volte capable device. It referred you to a list of volte capable devices and the z3v wasn't on the list. I do however do not understand how advanced calling would work on kitkat.... for one thing they're missing proprietary libs for HD video calling as well as the apps and the IMS bootstrap to keep advanced calling on between reboots, but hey if it's working for people on Kitkat that's wonderful news, they deserve it. I'd take it as a good sign that they finally got around to adding volte in their systems, to me that says the OTA is greenlighted and we're just waiting on the beginning of the roll out. What's disappointing is that Verizon is giving us 5.0.2, but hey it's better than what we've had. I'm grateful.
I can confirm mine is working on 5.0.2.
Has anyone else been unable to mute calls that are not HD Voice?
Today I deactivated advanced calling. I believe it was causing excessive noise during Bluetooth calls. I never had Bluetooth issues before Lp and advanced calling. 4.4 was flawless for me
Added advanced calling to my stock 4.4 phone, but I don't get simultaneous voice and data during calls. ?
Tigerhoods said:
that's interesting so we could have had this all along
Click to expand...
Click to collapse
Not quite -- I'm on stock 4.4 and I've enabled the feature with Verizon, but after rebooting my phone I still don't see an option to turn on Advanced Calling features. (Am I missing them in the menus? Where are they?)
MobyGamer said:
Not quite -- I'm on stock 4.4 and I've enabled the feature with Verizon, but after rebooting my phone I still don't see an option to turn on Advanced Calling features. (Am I missing them in the menus? Where are they?)
Click to expand...
Click to collapse
That's the lollipop part. The advanced calling is it's on tab in the OS settings.
Anyone else have issues with activating advanced calling. I select the HD calling in the settings. I get a message that indicates I already have HD calling and that I should restart my phone. Restart and same message pops up when I get a call that I don't have data while on a call.
Sent from my D6708 using Tapatalk
Solution: had to delete HD calling from Verizon, waited over night then added HD calling from the settings menu. Don't know how many times I've added and removed advanced calling before but waiting seemed to do the trick.
Sent from my D6708 using Tapatalk
How do i deactivate advanced calling. I have had tons of issues since activating it. I still get a message when i get calls saying no data available, i also cannot enter credit card numbers. I have not been able to successfully enter a card number even once since activating it, every time i am very careful an hit the right keys but it says thats not a working card. I have had no issues what so ever doing that before activation of advanced calling. Is there a way to remove or deactivate it completely or at all?
Samwest1 said:
How do i deactivate advanced calling. I have had tons of issues since activating it. I still get a message when i get calls saying no data available, i also cannot enter credit card numbers. I have not been able to successfully enter a card number even once since activating it, every time i am very careful an hit the right keys but it says thats not a working card. I have had no issues what so ever doing that before activation of advanced calling. Is there a way to remove or deactivate it completely or at all?
Click to expand...
Click to collapse
Just turn it off. There's a toggle in settings... If you're on lollipop.. Which if you're not, I guess you could do it in my verizon add remove features
Well i never actally turned any of the toggles on. I just activated advanced calling thru my verizon app. Since i activated it, i have not been able to enter a credit card number sucessullly, i know that advanced calling feature was the change that made my poblem. Becouse before activating it i never had an issue, but within a couple hours of activating it, i tried to enter my credit card number over phone call and every single time (ive tried so many times since the activation of advanced callig) every time it tells me sorry, thats not the right number. Ive tried with multiple cards, and the same result evey time. I just want to know, besides turnig off the toggles in settings( that i never used or turned to on). Is it possible to deactivate it thru verizon or delete it from my account. Can someone help me figure it out. It has been a huge inconveniance for me. The only toggles i have in settings are one for hd voice and one for video calling, and on above those 2 that is not labled and i figured was to turn advanced calling on or off. I never used it. When i first activated it ,it was done through my verizon app, an i didnt realize till reading more later on here , that there was section in settings for advanced calling. By that time i was already trying to remove it due to my card number entering issues, so i never turned any of the toggles on. Anyone know of anything that i could do to remove the feature completely.

New PG1 WiFi Calling update dropping today

New update dropping today!
Details:
https://www.att.com/esupport/article.html#!/wireless/KM1086930
Sweet, they finally pushed WiFi calling to the S7.
That explains why the security update took longer than usual, AT&T has been knocking them out the first week or so of every month till now.
Thanks, downloading now.
Installed on the regular S7.
So I updated (took about 1 hour to download and update). Immediately I noticed 3 things:
1) A notification with a link to a Display Settings dialog with the option to change DPI between Large and Small. "Settings-> Device->Display->Display scaling" will get you there later. This dialog box is not new; previously you could only reach it by adding .DisplayScalingActivity to Nova Launcher. What used to be called "Standard" is now called "Larger". What used to be called "Condensed" is now called "Smaller".
2) Wi-Fi calling was added to my quick notification settings. It is turned off by default. Toggling it on brought me to a setup wizard asking me to update my physical address for emergency 9-1-1 service. "Settings -> Connections -> Wi-Fi Calling" will get you there later. A very small "+" appears within the standard Wi-Fi status bar icon when Wi-Fi calling is ready. Both my Wi-Fi and cellular signals are strong yet the icon comes and goes. I initiated a Wi-Fi call to voicemail and it asked for my password, which does not happen for cellular calls.
3) Android security patch level: July 1, 2016
Scaling is standard in U firmware and also via a display scaling app in the play store. Just an FYI
joe3681 said:
Scaling is standard in U firmware and also via a display scaling app in the play store. Just an FYI
Click to expand...
Click to collapse
Perhaps, but this update added it to the stock AT&T firmware...finally,
Flashed stock then updated to this. Even wiped first. Advanced messaging is useless unless someone else has it. Connected to wifi since setup and it hasn't once shown the icon wifi calling is available.
joe3681 said:
New update dropping today!
Details:
https://www.att.com/esupport/article.html#!/wireless/KM1086930
Click to expand...
Click to collapse
That article still shows apf2.
Sent from my VK815 using XDA-Developers mobile app
New to reading? The whole article is about new update. Pf2 is listed under where it says PREVIOUS UPDATES
so who is going to try the eng-root method on this update?
buradd said:
so who is going to try the eng-root method on this update?
Click to expand...
Click to collapse
I was considering it just to see if it works. Root isn't what it used to be, battery killer more than anything these days but I curious...
joe3681 said:
I was considering it just to see if it works. Root isn't what it used to be, battery killer more than anything these days but I curious...
Click to expand...
Click to collapse
I'm highly considering going without root. I do think battery was slightly better stock as well.. also I really miss Samsung pay.. and there isn't much to do with Xposed.. I got the notification bar to display network speed and AdBlock..oh and call record is nice but not necessary... other than that, not much to do with root on this device unless someone can fill me in..i can install trebuchet and Google keyboard without root.. also I miss being able to sign into my chase app with fingerprint..
Sent from my SAMSUNG-SM-G930A using XDA-Developers mobile app
joe3681 said:
New to reading? The whole article is about new update. Pf2 is listed under where it says PREVIOUS UPDATES
Click to expand...
Click to collapse
It didn't when I looked at it.
Sent from my VK815 using XDA-Developers mobile app
I tried to test the wifi calling out and turned on airplane mode and then turned wifi back on. It shows the wifi calling symbol on top, but when i try to make a call a notice pops up telling me I have to turn airplane mode back off to make a call. It seems that it should make a wifi call just fine with only wifi active? Has anyone else tried this with success?
scott14719 said:
I tried to test the wifi calling out and turned on airplane mode and then turned wifi back on. It shows the wifi calling symbol on top, but when i try to make a call a notice pops up telling me I have to turn airplane mode back off to make a call. It seems that it should make a wifi call just fine with only wifi active? Has anyone else tried this with success?
Click to expand...
Click to collapse
A call went through in airplane mode on my S7
farfromuman said:
A call went through in airplane mode on my S7
Click to expand...
Click to collapse
Well it's very strange. I did several power cycles (on / off) and cleared the cache in recovery and it now wifi calling seems to be working in airplane mode. It's working for now with both calls and texts. I guess its just buggy. Hopefully clearing the cache did the trick.
scott14719 said:
Well it's very strange. I did several power cycles (on / off) and cleared the cache in recovery and it now wifi calling seems to be working in airplane mode. It's working for now with both calls and texts. I guess its just buggy. Hopefully clearing the cache did the trick.
Click to expand...
Click to collapse
theres no need to turn airplane mode on to make calls over wifi just toggle data off and they all go on wifi
tlopez1973 said:
theres no need to turn airplane mode on to make calls over wifi just toggle data off and they all go on wifi
Click to expand...
Click to collapse
Do you have a quick setting for data? I do not. Or do you mean through the mobile data settings menu and turn "mobile data"
off?
buradd said:
so who is going to try the eng-root method on this update?
Click to expand...
Click to collapse
No one is brave enough yet lol, although it should work fine. Some of the other carriers received updates and were still able to root.
Sent from my VK815 using XDA-Developers mobile app

Categories

Resources