Related
Hi everyone, love the site
Due to fortunate (and cheap) circumstances I am now the owner of two XDA/Wallaby/Qtek 1010 devices.
After much playing, I got to wondering if it was possible to modify these devices so they communicate directly with each other rather than using the existing (vodafone NZ) GSM network. I assume it would at least require modification of the radio stack ROM, if it is even possible. I guess the existing functions provided by the radio stack to the OS would be restricted to specific network related operations.
Does anyone have any further information about this, or modification of the radio stack? Also what are the risks? I understand that the wallaby is pretty resilient to permanant breakage through dodgy flash writes etc.
BTW if this sort of modification is illegal due to frequency licencing etc, then I am asking about this in a purely hypothetical sense
as far as i know it's supported by all of gsm pda's
when one setup a connection
one pick cellline rather then grps
ppl who have an isp which dont use grps
use it that way
of cause for 2 devices it would require software to work
where one acted server and the other client
like the good old seriel cable connection between 2 pc's
whoops, I mean without any celluar network involvement at all, just device to device communication over the cell phone radio of the devices. Pretty strange idea I know, but would it be possible?
if they used the 900/1800/1900 Frequiencys it would be illegal as it would interupt other devices in the area from being able to reach their gsm antennas
hmm damn there goes that idea. Such potential for long range comms too!
Hi All.
I've had an X10 mini pro on T-Mobile UK for nearly a year, and love it, but I am faced with a problem:
At work, I get absoluteley no signal. However, there are Wifi networks everywhere that are freeley available. It seemed logical to me that I aught to be able to get my phone to use those wifi networks to obtain a signal, so I did some research and found this generally to be reffered to as UMA (Unliceneced Mobile Access?)
For anyone who's coming across this technology for the first time, this is a facility which allows your mobile phone to use wifi connections as a backup for service signal, and switch seemlessley between them for use on calls (through your regular phone number [NOT VOIP!]) and texts.
I've read a lot of conflicting oppinions and statements on this, and wanted to ask here (In a place of expert knowledge and understanding) what the real truth is behind all this.
1: Is UMA a hardware or software based tool?
-I've heared numerous statements on this, including:
a) "Your phone can not do this if you don't have the correct hardware"
b) "The standard hardware (provided you have wifi access) is all you need, only the software needs to allow support"
C) "You need sufficient wifi technology AND the correct software to enable this"
Which is true?
2: "Service Providers are holding back on UMA support as it removes their justification for charging the user for calls"
- I've seen this in a few places, but it doesn't make sense to me. Sureley, despite the fact that the call is connected by a wifi signal, it still needs to find its way through a telephone exchange. Telephone exchanges cost money to maintain and manage, so that can't be right? can it?
- If anything, sureley this would give service providers a competative advantage as they can guarentee better signal coverage. It would seem more logical to me that the issue is less with the hand set, but with the providers managing the incoming and outgoing call data via the wifi network?
3: "UMA is/isn't supportend on android version X.X"?
- Again, I've seen conflicting info on this. What's the score?
Thought this was the right place to discuss all this and find the real truth behind UMA. My final question of course being:
4: Is there a UMA app or method by which I can use wifi as a signal backup? If not, is anyone looking into it and how soon may users see the benefits?
Appreciate any light that can be shead on this to dispurse the smoke and mirrors that seenm to surround it.
Thanks,
Oliver
hmmm
Supprised noone's responded to this... did I miss something?
In the USA, T-mobile has an app that does this. T-mobile USA uses the term wi-fi calling.
Is there such a thing in the UK? I know that the Optimus T (essentially the same as Optimus One) has this ability. I found this list of phones that work with this feature on T-mobile USA.
Phones that can make use of this new feature:
Blackberry 8520
Blackberry Bold 9780
Samsung Vibrant (SGH-T959)
Samsung Vibrant II (Galaxy S 4G)
LG Optimus T
myTouch 3G Slide
myTouch 4G
Motorola Defy
Motorola Cliq 2
Motorola Cliq XT
Sidekick 4G
G2
G2X
Nokia Astound (C7-00)
Nokia Mode (E73)
Samsung t339
Some other older android phones can work as long as the app has been ported for the device. Very YMMV
Click to expand...
Click to collapse
I do not think your phone is available through T-mobile USA, so it is not on the list. Someone figured out how to bring wi-fi calling to non-tmobile Roms for the Optimus T/Optimus One phone. http://forum.xda-developers.com/showthread.php?t=1116268 However, I am fairly certain that this type of app needs the cooperation of your carrier to work.
Action_Man_1 said:
Hi All.
I've had an X10 mini pro on T-Mobile UK for nearly a year, and love it, but I am faced with a problem:
At work, I get absoluteley no signal. However, there are Wifi networks everywhere that are freeley available. It seemed logical to me that I aught to be able to get my phone to use those wifi networks to obtain a signal, so I did some research and found this generally to be reffered to as UMA (Unliceneced Mobile Access?)
For anyone who's coming across this technology for the first time, this is a facility which allows your mobile phone to use wifi connections as a backup for service signal, and switch seemlessley between them for use on calls (through your regular phone number [NOT VOIP!]) and texts.
I've read a lot of conflicting oppinions and statements on this, and wanted to ask here (In a place of expert knowledge and understanding) what the real truth is behind all this.
1: Is UMA a hardware or software based tool?
-I've heared numerous statements on this, including:
a) "Your phone can not do this if you don't have the correct hardware"
b) "The standard hardware (provided you have wifi access) is all you need, only the software needs to allow support"
C) "You need sufficient wifi technology AND the correct software to enable this"
Which is true?
2: "Service Providers are holding back on UMA support as it removes their justification for charging the user for calls"
- I've seen this in a few places, but it doesn't make sense to me. Sureley, despite the fact that the call is connected by a wifi signal, it still needs to find its way through a telephone exchange. Telephone exchanges cost money to maintain and manage, so that can't be right? can it?
- If anything, sureley this would give service providers a competative advantage as they can guarentee better signal coverage. It would seem more logical to me that the issue is less with the hand set, but with the providers managing the incoming and outgoing call data via the wifi network?
3: "UMA is/isn't supportend on android version X.X"?
- Again, I've seen conflicting info on this. What's the score?
Thought this was the right place to discuss all this and find the real truth behind UMA. My final question of course being:
4: Is there a UMA app or method by which I can use wifi as a signal backup? If not, is anyone looking into it and how soon may users see the benefits?
Appreciate any light that can be shead on this to dispurse the smoke and mirrors that seenm to surround it.
Thanks,
Oliver
Click to expand...
Click to collapse
Try this solution, T-Mobile and Orange have done a deal where they can use eachothers signals, go back to netwoork settings and you should find " T-Mobile-Orange 3G"... Connect to that and it may work.
It seems that T-Mobile and Orange both have very bad coverage compared to other competators.
I'm trying to pair my S6 edge to my TL but I keep getting blocked by the trusted devices menu.
Basically I'm able to start the pairing process and setup a pair code but when my car asks me to name the device the pairing process stops. I get a notification that asks me to add the car to my trusted devices list but when I do my car keeps telling me I can't start the pairing process from the phone. It's like if I have to add my car to the trusted devices list before I start pairing in order to finish pairing the car and phone. Is there any way to disable to smart lock so I can pair my car? I never had any issues with previous galaxy devices.
It's worthy to note that I was able to pair my Gear 2 and Nexus 9 without all this hassle
thanks.
bump
What year TL?
I wouldn't trust a TL either LOL. Works fine for BMW M3 with iDrive
Works on my 2012 TL but BT track info doesn't display which sucks!
Elisha said:
What year TL?
Click to expand...
Click to collapse
05
I was able to make a video with what exactly happens that prevents me to pair my phone and my car. Basically, i can go though the entire process but when i get to the part where i have to name the phone it cuts me off. Then I have a "trusted devices" message that pop up on the phone asking me to pair with my car to add it to the trusted list, and when i go in bluetooth devices, it does say pair. Usually it should say connected. When I try to connect to it in BT devices, it asks me for my 4 digit code and after I input it, my car tells me the pairing process can't be initiated from the phone...I don't know what to do, this is the first phone i was not able to pair. I think its a lollipop thing but i cant confirm because my note 4 that ran lollipop was already paired with the car when i got the OTA 4.4 to 5.0.
https://youtu.be/7mPvjCjWSYI
bump
Bump!
I also made a thread on an Acura forum if anybody is interested
http://acurazine.com/forums/audio-b...air-05-tl-galaxy-s6-edge-931791/#post15466470
Turn off Smart Lock? Settings> Lock Screen and Security > Other Security Settings > Trust Agents and uncheck Smart Lock?
one of the first things i tried. Thx anyways
Important update.
I was able to pierce the mystery of my pairing problem. It seems as not all S6 edge are created equal.
Long story short, my dad got himself a new car, Benz GLA250, thats comes with networking capabilities when paired with a smartphone. His company supplied iphone didnt share the network connection with the car so he asked me to try with my S6. As i tried to enable bluetooth tethering, i couldnt find it. I made a few searches on XDA and found that some people are complaining about missing functions on their edge, BT tethering was one of the main features some people didnt have, others were missing some toggles also. It seems as some phones dont have it. Don't ask me why because its not a carrier restriction, some people on T-Mo had it, others didnt.
The only solution was to flash a custom rom with BT tethering enabled. As I didnt want to go through the entire flashing process, and also because i didnt want to trip knox in case it break SamsungPay, i called up my friend that had the same phone I didnt and found out he also didnt have BT tether. Since he didnt care about knox or Samsungpay, i flashed him a custom rom and was fianlly able to pair my TL with the edge, and was also able to connect to my dads car.
So i guess it's a software problem. Not sure why that option was left out for some, but i guess it'll be fixed in the upcoming 5.1.1 update. Also worth noting that samsung did release a fix for the missing toggles through an app in the galaxy store.
Does anybody know why BT tethering is gone on my variant? I've heared of some carriers taking out that option (and hotspot) but that was mostly because of the unlimited data plans, but in canada they never block anything on our variants, neither the bootloader or any other function.
Has anybody with an S6 edge W8 also have the BT tethering missing?
I'm trying to pair my galaxy s6 edge to my acura mdx 2006, and i can't do it. Is my phone too new to my car?
Just in case anybody is still interested in this problem, I found out that this "era" of TL ('04-'08) ONLY accepts cell phones from this time period.
Meaning if one doesn't have a cellphone dating back from these years "IT AIN'T GONNA WORK!" There is a cellphone compatibility list online
that one can find out which cellphone works from multiple makers and carriers.
And the answer to your question....YES, its too new.
Hello?
i recently bought the omate truesmart+.
very happy with it until i realized that as it is a standalone phone.
just wondering if there is a way i can tether it to my phone to get the notifications and also answer calls without inserting a sim card on the watch.
i am a complete novice when it comes to tech but willing to learn so instructions and help in layman's term would be most appreciated.
ayan13 said:
Hello?
i recently bought the omate truesmart+.
very happy with it until i realized that as it is a standalone phone.
just wondering if there is a way i can tether it to my phone to get the notifications and also answer calls without inserting a sim card on the watch.
i am a complete novice when it comes to tech but willing to learn so instructions and help in layman's term would be most appreciated.
Click to expand...
Click to collapse
Nope the TrueSmart series are only telecom standalone (3G) and can only be used with a BT headset as it is a standalone device. You may consider the Omate Racer or Roma for BT companion only device to be paired with your iOS and Android smartphone
or the Omate Rise which can do both companion (BT) and Standalone (3G)
or you can consider many other BT companion smartwatches from other manufacturers.
Try SWApp, it's mentioned in other threads in this forum community as being a great companion enabling app.
Try Tablet Talk it may work
Re: Verizon 6.0 OTA update, LG G3, after the update last month, my Bluetooth connections (three different headsets) became useless, with both parties to a call cutting in and out and the BT indicator going on and off repeatedly. After a series of complaints and escalations Verizon sent a replacement with Lollipop installed. Problem solved until VZW pushed the update to the new unit. Now I have the same trouble with BT. I am cell tech savvy but at the end of my patience. Has anyone experienced this issue and is there a fix? Many thanks.
I have not had the issue but I only connect to my car's built in bluetooth for call audio.
i had a little issue pairing to my plantronics voyager legend but it was getting the headset into pairing mode. once paired, flawless.... just make sure you turn off those stupid smart sensors on the headset. they cause tons of disconnect issues.
i also have it paired to a tone pro (HBS-730) and a JBL Clip, and pioneer headunit in my van. no issues.
Brian
Similar problem here. Since the Marshmallow update, I cannot pair to my Basis Peak fitness monitor, pair intermittently to my Aukey wireless headphones, and am getting erratic operation on my Wahoo Kickr Snap smart bike trainer.
No issues with my car (Hyundai) or Logitech boombox speaker with a clean install. Try deleting all of the Bluetooth devices from your phone, then delete the phone profile from the device if possible, power cycle both and pair again.
Third G3 VS985 in a row broken by MM update!
(I am the OP this thread): Third replacement unit has BT issues following the 46A update. VZW "2nd tier tech support" claims no one else has reported this issue, which is, of course, bull****.
I have an appointment in early March with an attorney who does consumer class action work. No guarantees, but she is interested in hearing more. Anyone else experiencing similar problems should message me. Thanks.
wjanowski said:
Similar problem here. Since the Marshmallow update, I cannot pair to my Basis Peak fitness monitor, pair intermittently to my Aukey wireless headphones, and am getting erratic operation on my Wahoo Kickr Snap smart bike trainer.
Click to expand...
Click to collapse
Same here (but Motorola Moto G 3rd Edition 2015 with OTA Marshmallow) . I suspect that Basis Peak is just not fully compatible to Android 6.0.1 in general.
BT issue on Marshmallow update
I have found that my G3 will now not pair with devices that use a dedicated app to pair with the phone. All other devices seem to pair normally.
I have 2 devices that use a dedicated app to sync over BT and they will not connect.
I have 2 devices that sync using the basic BT pairing method on Android and they connect no problem.
I wonder if there is an added security setting in Android 6.0 that is blocking these types of connections.
I had the same problem - won't connect to my Basis Peak, but is fine with my Pioneer radio after the update. I opened a helpdesk ticket with Basis, and here is their response:
I hope you are well. We have discovered that there is a connectivity issue with the LG G3 phone.
In mid-February, Verizon upgraded its LG G3 users to the newest Android operating system, Marshmallow (Android 6.0.0). Following this update, Verizon LG G3 customers, now running 6.0.0, became unable to sync or pair with their Basis Peaks.
When Basis became aware of this issue, our Android team began running tests to determine what was causing the incompatibility. Our team discovered that the LG G3 has trouble maintaining a stable bluetooth connection when running 6.0.0. The Peak uses a secure communication link to transmit data to your phone, which requires a more complex connection process. What is happening is that the unstable bluetooth connection of a LG G3 running 6.0.0 tends to drop before the secure communication link can be established, thus the Peak can neither pair nor sync with the phone.
Several other BT devices are having difficulties with the LG G3 handset running 6.0.0. The company, Tile, saw a BT issue with 6.0.0 and they worked with Google to develop a fix which is being rolled out with 6.0.1 While Tile’s issue was not specifically related to the LG G3, we believe that the next Android release may resolve the issue we are experiencing, as we have several customers who are able to sync while on 6.0.1.
(More information about Tile’s 6.0.0 issue can be found here: (I can't post URL's yet...)
We currently are working towards being able to validate that 6.0.1 will resolve the communication issue between the LG G3 and the Peak.
We take this situation very seriously and will update you as soon as we know more. We appreciate your patience.
Verizon pushed update to 47A today, BT issue unchanged
I was hopeful when I saw a new system update to the LG G3, but it doesn't help the Bluetooth issue with 6.0...
My JBL Flip worked fine with 46A but only supports call audio with version 47A.
Why has Verizon Wireless abandoned customers using the LG G3?
Verizon Wireless customers using the LG G3 (VS985) received a mandatory update to "Marshmallow" (6.0) earlier this year. Following the update, four of my five Bluetooth devices no longer worked reliably. Verizon referred me to LG, which in turn suggested that I contact Google.
I discovered (on this forum and Verizon's own) a large number of Verizon customers complaining that they too have had their Bluetooth functionality badly reduced. Some of us have spent additional money on higher priced devices in order to use the phone legally on the road. My hearing aid connects to the phone via BT, so I'm s*** out of luck.
Verizon's troubleshooting steps do not address the problem. There is an apparent solution in 6.0.1, but Verizon declines to make it available on the G3.
Having worked in the wireless industry, I believe nothing is pushed to Verizon customers until and unless it has been vetted and approved by the carrier. My educated guess is that Verizon failed to do proper diligence and wants to get out from under the problem by dropping support for the G3 and suggesting that customers pay to "upgrade" to a newer model.
Within the next few days, I'll be moving my numbers to one of their competitors. Verizon Wireless has failed to support a large group of its customers and deserves to lose them.
bobgowa said:
Within the next few days, I'll be moving my numbers to one of their competitors. Verizon Wireless has failed to support a large group of its customers and deserves to lose them.
Click to expand...
Click to collapse
I understand what you're saying, and the frustration. If I were in the same position, I'd downgrade to 10B, root and put @xdabbeb_vs985_2.0.0 ROM on (based on 35B). All carriers tend to not care anymore once they've delivered what they expected to be their last OTA to a device.
roirraW "edor" ehT said:
I understand what you're saying, and the frustration. If I were in the same position, I'd downgrade to 10B, root and put @xdabbeb_vs985_2.0.0 ROM on (based on 35B). All carriers tend to not care anymore once they've delivered what they expected to be their last OTA to a device.
Click to expand...
Click to collapse
I'd love to. However, while I'm pretty capable with RF technology, this is above my pay grade and I don't know anyone who can do it for me. Any ideas out there?