Related
My wife and I got new Galaxy S II phones from C Spire earlier this month. They came with Android 2.3.6 out of the box, but a tech guy loaded 4.1.2 while we were still in the store. A few days later, I noticed a few odd things on both phones when using Google Maps:
With "Use wireless networks" checked, "Use GPS satellites" unchecked, and Wi-Fi off:
Maps plots my coarse location, so that I can see the blue directional arrow surrounded by a relatively large circle. So far, so good. But if I drive somewhere and keep Maps up, it never updates my position.
With "Use wireless networks" checked, "Use GPS satellites" checked, and Wi-Fi off:
Maps plots my coarse location, just as above. The GPS icon appears and starts flashing in the notification area. Five minutes later, it will still be flashing. Again, if I drive somewhere and keep Maps up, it never updates my position.
With "Use wireless networks" checked, "Use GPS satellites" either way, and Wi-Fi on:
Maps plots my coarse location, just as above. If I drive by a Wi-Fi network, Maps zooms over to the proper location, and the surrounding bluish circle is much smaller. However, after a few seconds, it zooms me back to my original position, and the much wider circle is back. And I know my car is incapable of teleportation.
Here are the things I have done:
Used the Text CS service, was told to make sure I had a clear view of the sky, turn GPS off and back on, turn the phone off and back on, and finally to try a factory reset, which I eventually did and got the same results.
Tried several GPS apps for deleting and re-downloading AGPS data.
Talked to a C Spire sales person and tech person, called their customer service number, and talked to the tech guy who installed the updates to our phones the day we got them. He worked with it for a while, had me reset the phone through recovery mode (neither forms of resetting restored the original version of Android), and finally said he'd get us replacement phones. This shouldn't be taken as a rant against C Spire; all of these people were very friendly.
Went to my local C Spire store and got the replacement phones set up (they already had 4.1.2 on them, and I'm not sure if they came that way or if someone updated them). Exact same problem still occurred.
Did a chat with Samsung customer service. Had me restart the phone in Safe Mode, and that still didn't help. Suggested I call in and setup a support ticket, which I haven't done yet.
Our previous phones were both the original Galaxy S (SCH-I500). While the phones themselves seemed to bog down in their old age (and froze or reset themselves at least daily), the mobile network locating and GPS locating worked amazingly. Under decent conditions, the GPS might take 5 seconds to lock.
I finally had a bit of a breakthrough today, but it hasn't resolved the issue where location via mobile network won't update (scenario 1 in the numbered list above). I found out about GPS NMEA data, which, for those who have no reason to learn about such things, is the raw data transmitted to and from a GPS satellite and receiver, and installed GPS NMEA Tool. After starting the app, I waited for a bit, and still no GPS lock. The initial view presented by the app is a human-readable summary of the data, and at some point I opened up the raw GPS NMEA log. It started spouting off a few lines that looked to be saying "I can't find a dang thing," but suddenly all of that changed. I switched back to the summary view, and sure enough, I had a fix on several satellites. I exited the app, opened Google Maps, and it got a lock again. It didn't stay locked the whole time, and it was slow to update my position, but it did work.
As far as I know, GPS NMEA Tool is only a diagnostic tool that doesn't perform any magic fix to the phone. I thought this might just be a strange coincidence, but after being inside this evening, I took my phone back outside. I opened up Maps, and after a few minutes, I didn't have a lock. I fired up GPS NMEA Tool, and after a minute or so I had a lock again.
So, does anyone have any clue what might be going on? Here's the info on my phone:
Using an Otter Box Commuter case. I don't think it has any metal in it, and I think someone at a C Spire store tested the GPS without the case on.
Model: SCH-R760X
Android version: 4.1.2
Baseband version: S:R760.01 K.GB28
Kernel version: 3.0.31-980103
[email protected] #3
SMP PREEMPT Fri Mar 1 04:29:20
KST 2013
Build number: JZO54K.SCH-R760X.GB28
Hardware version: H:R760.01 K.Q
Software version: GB28
Mobile network type: EvDo-rev.A
Well, I haven't gotten the GPS to lock in again, so I'm guessing the GPS NMEA Tool has anything to do with it. So basically, I'm still experiencing the exact same issues as before.
Well, apparently Samsung sent a batch of GS2s that weren't properly configured for C Spire. The stores were told not to sell those phones. I'm supposed to have a replacement very soon. So I suppose this issue is now finished!
Ok, I assumed getting a new phone would solve the problem, but it didn't. I'm on my fourth phone, I think, and they all seem to behave the same way. A few new things:
When I left the store with the new phone, I turned on Google Maps and left GPS off. My coarse location did update a few times, but then it stopped doing so after I was about 2 miles from the store.
I can get my coarse position on Maps to update by either restarting my phone, making a call, or sending a text. Obviously, my phone connects to a new tower when I change locations, because I can make calls and not have them drop soon after. Also, I figure people wouldn't be able to call me if I left the tower that my phone currently thinks it's connected to. It seems that unless I do something proactive, the phone doesn't want to acknowledge that it's moved on to a new tower.
Occasionally I can have GPS work for a little bit, but it never lasts for long.
Still going on. About the only thing new I know is that this seems to be isolated to GS2s running 4.1.2.
Another update regarding my (probably hopeless) situation. I captured data packets (which only seems to work if using Wi-Fi; on 3G, the phone doesn't look to handle the TCP/IP stuff itself) with Shark, and it looks like my phone has no problem communicating with googleapis.l.google.com. The actual data is encrypted, though.
The phone continues to report that I'm connected to the same base station (specifically, the same sector) until I do one of the above-mentioned things, although sometimes I'll have to make a call twice before the phone figures out where it is. Also, I've noticed that sometimes, if I've driven from point A to point B (we'll say they're 25 miles apart), after a single brief phone call, Maps might move my location to a spot in the middle of A and B. It may then move my location to point B after a second call.
So I still have no freaking clue why my phone won't properly report what tower it's connected to until certain events occur.
Also, I'm guessing the GPS issue at least partially stems from my phone not knowing where the heck it is most of the time. If it's getting assisted GPS data that's intended for a different location, that would definitely cause a delay in finding satellites.
By the way, I'd love to know if anyone else is experiencing this issue, or anything similar.
robg37 said:
.
By the way, I'd love to know if anyone else is experiencing this issue, or anything similar.
Click to expand...
Click to collapse
Wanted to let you know I am experiencing the exact set of problems you are with my Galaxy 2 from CSpire. The gps works in a very inconsistent manner. Some days it works perfectly. Some days it doesn't work at all. Weather and cloud cover have no bearing on whether on not it works.
I spoke to someone at Samsung, but they were no help. They said I could send it in for repairs, but knowing my luck they would test it during one of the few times it works perfectly.
I'll be anxious to hear if you or somebody else discovers a fix for it.
Palaver23 said:
Wanted to let you know I am experiencing the exact set of problems you are with my Galaxy 2 from CSpire. The gps works in a very inconsistent manner. Some days it works perfectly. Some days it doesn't work at all. Weather and cloud cover have no bearing on whether on not it works.
I spoke to someone at Samsung, but they were no help. They said I could send it in for repairs, but knowing my luck they would test it during one of the few times it works perfectly.
I'll be anxious to hear if you or somebody else discovers a fix for it.
Click to expand...
Click to collapse
Unfortunately, I don't have a solid answer. But based on my experience and your response, I'm guessing there's some sort of issue with the 4.1.2 update that screws up how the location is reported. I've seen GS2's in stores that have 2.3.6, and they seem to work fine (although I obviously can't run off with one to test it). Plus, if this issue had been present when the phone was first released, I figure it would be much better documented. The problem now is:
There are 2 newer generations of Galaxy S out. Most people buying new phones are going to choose one of the newer 2.
Of those already owning this phone, many won't have updated them to 4.1.2.
Of those who have updated or recently purchased a GS2 that's already running 4.1.2, many won't ever make use of the location functionality.
Out of those who have noticed this issue, I'm sure there are a decent amount who are eligible for new phones soon and just decide to deal with it for a short time.
Out of those who still have a while on the contract, many will likely never get around to doing anything about this issue.
So there are probably a very small number of people who have a GS2 running Android 4.1.2 and who have noticed this issue and want to do something about it. If this issue is specific to the C Spire phones (or C Spire and a few smaller carriers), that further limits the number.
I don't know the details on how a carrier and a manufacturer work together on a version of Android for a particular phone, so assuming there's a real problem (which obviously isn't hardware), I don't know how it could be fixed. Also, I don't know how much effort Samsung and any wireless carriers who carry this troubled phone are going to put forth, given that this phone is probably considered to be in its "end of life" stage.
Samsung also gave me the option of sending the phone in, but I'd be without my phone (unless I got a loaner phone) for 2 weeks or so, and I don't know if I'd be expected to pay shipping to get it there.
I figure the best option would be to see if C Spire would allow you to trade the phone for a different model. It's not ideal, since you'd either have to move to a different brand or move up to a 4G plan (if you're in a situation like mine where you have an older plan that you can keep as long as you have a 3G phone). But I'd say at least talk to someone at a store and see what they might offer. And please let me know how it goes, if you decide to do that. Best of luck!
Another thought: You could have the phone reverted to Android 2.3.6. Again not ideal, but I figure it would fix the issue. I don't know if there's any official way for this to be done, but I'm sure a way could be found.
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.
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?
Hello everyone,
I've recently purchased a Samsung Stellar second hand from a family member. I intend to use this device for T-mobile(It's a Verizon device) and the device seems to be carrier locked. I've tried five different SIM cards and multiple factory restores for each and only the Verizon chips will work. Verizon customer support refuses to acknowledge both the problem and device, giving me the run-a-round and different and equally unhelpful answers each time. My question is, is there anyone who can help me? I'm looking for a method to either unlock this phone or a root/Cyanogenmod/ROM combination that will allow this device to be more than a glorified music player that also uses apps.
tmp8101 said:
Hello everyone,
I've recently purchased a Samsung Stellar second hand from a family member. I intend to use this device for T-mobile(It's a Verizon device) and the device seems to be carrier locked. I've tried five different SIM cards and multiple factory restores for each and only the Verizon chips will work. Verizon customer support refuses to acknowledge both the problem and device, giving me the run-a-round and different and equally unhelpful answers each time. My question is, is there anyone who can help me? I'm looking for a method to either unlock this phone or a root/Cyanogenmod/ROM combination that will allow this device to be more than a glorified music player that also uses apps.
Click to expand...
Click to collapse
T-Mobile is a GSM network; the Stellar is CDMA - so you aren't taking it *there*. You can take it to a CDMA provider (such as Sprint) or a CDMA network (while not Verizon - since they don't support BYOD) but an MVNO that uses VZW's towers is still a possibility (such as Tracfone). I took my ex-VZW Galaxy Nexus to Tracfone without issues; unlike VZW itself, Tracfone could care less what firmware you use on your devices as long as the firmware itself supports the device. (I use *unified* (tuna) firmware for GNexi (by unified, I mean the firmware supports maguro, toro, AND toroplus devices - as such, it is at home on any Galaxy Nexus) - comes in really handy as the builder is Japanese, and has a maguro GNex, while I have a toro device, and I'm American - and I don't have "sushi" issues - or sashimi issues, either.)
I happen to have a Galaxy Stellar at my elbow, and I'm looking for a community ROM to support it so a friend of mine can pass it down when she retires it. (I'm thinking that it is of a similar age to the GNex; from the legend of the handset itself, it's of the same series as the Galaxy S, and may well be the in-between of the Nexus and S3, as it, like the Nexus, originally ran ICS. If I turn up anything, I'll post it in the thread.
I'm sorry if this wasn't in the right area, I googled up this same question and this board has it the most it seems. If its in the wrong area, please move the topic to the right area so I know where to ask next tome (or link and I'll delete this ((if possible)) and recreate).
I've been using PDANet USB Tethering for the last 3 years or so with Boost Mobile, Samsung Galaxy S3. My phone is showing severe signs of age and issues, and I'm having tons of PDANet related issues. I have unlimited 4G LTE data, but I can't use my wireless tether because the phone company detects it and stops it at 8GB where as USB tethering I've gotten 100+ GB in a single month no issues.
I'm looking for a new phone I can get, that I can somehow mask everything I do on it so that the phone company is unable to see what I'm doing on it, and won't be able to determine if I'm using my phone's wireless tethering features. I prefer a smartphone, obviously, cause I do take it with me where I go and like to have access to my apps. I'm inexperienced with installing ROMs or rooting, never figured out how with my S3 because all the topics are outdated and inaccurate and I only ended up damaging the phone trying. I've got about a week or two to find a new phone that will work with Boost Mobile. My current phone's network mode is CDMA/LTE/EVDO, just to give you an idea of what network I'd need to use for Boost (CDMA I guess?). I need 4G as well, it seems that 3G doesn't work at all at my location and I only get 1 bar of 4G LTE when I'm at home in a specific 3 inch by 3 inch space in my room that I have to tape my phone down to, but at least it works.
There's no other internet options available to me where I live, so my phone is my internet. Just to clarify before people suggest getting an internet service.
Just to be sure, I don't want anything made by Apple, but that should be obvious, posting in the Android forum.
I have found that Boost Mobile won't let me use anything but like 6 specific phones only. Two of the choices being the S7 and the S8.
I've done a search on Amazon looking for unlocked S8 phones, however the comments and reports all claim these unlocked devices are a lie and don't actually work with services they claim to, or have conflicting reports and such. I'm unable to find an Unlocked S8 for use with Boost Mobile.
I've found that I can edit the APN to add 'dun' to my type list, to bypass the data limit of Mobile Hotspot, however I am hoping that it doesn't also cause the company to start charging me hundreds of dollars a month. I want to make sure they can't actually see the traffic either, I don't want my ISP knowing what I'm doing online, because they will just turn around and sell every website I visit to third parties which is now a thing in the USA.
I'd rather Boost not know whats installed on my phone or what websites I visit.
Thread closed as per OP request.