Hi all.
I have had my gear 2 for about 1 month now and I am running Hyperdrive RLS 18.1 on my MDK Galaxy S4 phone.
Since getting the watch, i ran Tizen Mod 3.0 with no issues until about a week ago.
I noticed that my bluetooth connection would cut in and out unexpectedly and at random. I started to troubleshoot until I finally got frustrated and just unrooted my watch and return back to stock.
However, I still cannot pair my watch to my phone.
I though maybe xposed framework may be interfering with the pairing process so I deactivated, wiped cache and delvik cache and rebooted.
Started the pairing process again but the phone still says " Failed to Connect to your gear via Gear manager. Refer to Manual for more information."
I have no idea how to get this up and running again and this watch is only 1 month old.
How can i figure out why the bluetooth pairing is not working anymore.
Someone please tell me what am I doing wrong or what the hell is going on with this damn device. I am at my wits end with this.
Just an update. I reflashed my rom in an effort to rectify this situation. Still no go. Someone please help.
I had some similar situation. I ended up resetting my watch and factory default my phone. I think that when the watch goes into pairing mode after deleting the connection, the watch is not always fully reset. I could trick it to connect to a different device which completely wipes the watch and then reconnect to your own phone. The factory default of my phone also must have fixed some bluetooth config corruption.
I restored most of my apps with Titanium Backup after the wipe.
I have my watch connected to a rooted Note3 running Wanam Xposed.
Sent from my SM-N9005 using XDA Free mobile app
I had a feeling I would have no choice but to do a complete wipe on my phone. Very annoying. But thanks sharing your experience. I'm gonna start completely from scratch and report my findings.
RJV3 said:
I had a feeling I would have no choice but to do a complete wipe on my phone. Very annoying. But thanks sharing your experience. I'm gonna start completely from scratch and report my findings.
Click to expand...
Click to collapse
I JUST WIPED MY WHOLE DAMN PHONE AND I STILL CANNOT PAIR MY GEAR 2 TO THE PHONE!!!
Not yelling at you at all, just venting.....
This is definitely a first for me with the pairing issue. I'm going to try on my wifes Note 3 and see if that works.
If all else fails, will try to send this dame thing back to Dell.
Sucks because I already spent money on a stainless steel band for the watch and clear full body skin protector from skinomi.
Four resets and 4 factory resets on the galaxy gear 2 watch, the Damn phone and watch paired! UNBELIEVABLE. I am using the previous build of gear manager and refuse to update. My Problems began with the newer build. Thanks for the reply to the applicable.
Good to hear it worked. I have been messing around with it quite a bit as well.
Are you using TW as default launcher? I use GoLauncher. My Gear doesn't reconnect automatically after a reboot of my phone. I think I noticed that when I use GoLauncher as default, it does not reconnect automatically whereas when I run TW as default, it does. Can't confirm this for sure though.
Sent from my SM-N9005 using XDA Free mobile app
That's very odd. I'm using action launcher pro instead of stock tw launcher. I don't like too many icons all over the place. Also, another user reported the gear manager got updated today and already people complaining it breaks gear 2 connection. I can't verify it though and I won't update until I know any bugs are fixed.
I updated mine and this time no problems. Others reported problems though in another thread. Maybe it was ok because all was freshly installed here recently. I will run some auto connect tests shortly to see if my hunch was right.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
I updated mine and this time no problems. Others reported problems though in another thread. Maybe it was ok because all was freshly installed here recently. I will run some auto connect tests shortly to see if my hunch was right.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Running a custom rom?
No, watch is now running stock. My Note3 runs stock 442, rooted, Wanam Xposed.
Sent from my SM-N9005 using XDA Free mobile app
gschot said:
No, watch is now running stock. My Note3 runs stock 442, rooted, Wanam Xposed.
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Okay.
Anyone successful in updating running a TizenMod?
I'm thinking that the new Gear Manager is detecting root on the watches causing it not to connect.
Still reading through the comments section of the 9/17 update and almost everyone has cited connection issues with the new update. Can everyone be wrong?
I am also assuming that most of the comments are from non-rooted users, so they may stuck with the update until Samsung addresses the issue. Very annoying considering what I just went through........
I have a new problem. I tried to download previously purchased apps for the gear 2, and even previously downloaded free apps for the gear 2 and I keep getting (WO:WO:FAILED) error message. I can't get any new watch faces installed.
I know if running Tizen MOd Rom 3.0 i can get some of the apps to install since the dev has signed some of the free apps with his signature in order to work with his rom, but I cannot understand why the apps are failing to install fresh out the box??
Successfully updated and working
Binary100100 said:
Okay.
Anyone successful in updating running a TizenMod?
I'm thinking that the new Gear Manager is detecting root on the watches causing it not to connect.
Click to expand...
Click to collapse
I successfully updated the Gear Manager today and had no problems yet (didn't have much time with it, though). I'm running TizenMod 2.0. The watch didn't reset and connected without a problem to my S4 (latest 4.4.2 stock rom, rooted and with old bootloader).
Gear Manager v2.2.14090599
Antic said:
I successfully updated the Gear Manager today and had no problems yet (didn't have much time with it, though). I'm running TizenMod 2.0. The watch didn't reset and connected without a problem to my S4 (latest 4.4.2 stock rom, rooted and with old bootloader).
Gear Manager v2.2.14090599
Click to expand...
Click to collapse
I have an MDK GS4 here with hyperdrive rls 18.1 rom and was running tizen mod 3 and the 9/5 gear Manager update. Had a lot of connection issues. Then reverted to stock rom on my gear 2 and still had connection issues. Reverted to old gear Manager and connection is fine, but now can't install my downloaded apps / watch faces on my gear 2. Keep getting WO:WO :FAILED. Error message. Anyone know how I can resolve this?
Possible workaround
I have the same connection problem on a stock Note 3 and stock Gear 2.
While I was messing around I might have found a workaround.
Make sure bluetooth is enabled.
Then just open your bluetooth devices (long-press the bluetooth icon in the notifications tray) and you should see Gear 2 is grayed out. Just tap it and it should go blue.
Then go to gear manager and it should be connected. If not reconnect it through gear manager.
I've had to do this a couple times in the last 2 days but it seems to hold it's connection unless I reboot or if it goes into deep sleep.
twelc said:
I have the same connection problem on a stock Note 3 and stock Gear 2.
While I was messing around I might have found a workaround.
Make sure bluetooth is enabled.
Then just open your bluetooth devices (long-press the bluetooth icon in the notifications tray) and you should see Gear 2 is grayed out. Just tap it and it should go blue.
Then go to gear manager and it should be connected. If not reconnect it through gear manager.
I've had to do this a couple times in the last 2 days but it seems to hold it's connection unless I reboot or if it goes into deep sleep.
Click to expand...
Click to collapse
I had noticed this too. Unfortunately, we shouldn't have to do all of that.
Try freezing this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I noticed that it was very recently installed so I froze it, rebooted and everything except SHealth sync seems to work now.
Can someone help me get passed this error message.
RJV3 said:
Can someone help me get passed this error message.
View attachment 2943084
Click to expand...
Click to collapse
Are the issue resolved ? Heard there was a Gear Manager update. I am planning to get a Gear 2 and run custom Rom on it but like to know if these issue is affecting everyone or just some.
Related
Does anybody else have a problem with their caller ID? I am on t-mobile in the US and sometimes the phone number shows up, sometimes it says unknown. This happens randomly even the same person. One time, their caller id would show up, the other time it'd say unknown.
I'm on Tmobile USA as well and don't have any of these problems.
Maybe try clearing the contacts and sync them again?
Sent from my HTC VLE_U using XDA
I never had caller ID... Though I remember it was one of the "bonus apps" the icon of which was shaped like a gift box.
Given my repulsion to bloatware, I deleted it. Finally, frustrated with the whole lack of caller ID, I finally dropped $6.99 on White Pages Pro (or something like that). Now my caller ID is great and it adds the info if I want to make a new contact. Very nice.
Sent from my HTC One-S (rooted), stock ROM
Got a new one at costco...Same problem..wtf. Can it be the sim card or something? Any ideas?
So this is what I mean about the unknown caller ID problem. Unknown callers with a phone number is not the problem. The problem is unknown callers calling me with no phone number. And these numbers are not blocked. I asked my friend to help me test it for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This happens on and off WIFI calling and this is my second One S with the same problem. Kinda annoying because I don't know who to call back if I get a missed call.
I've been having the same problem. I took it back to the t-mobile store and they gave me a new one but after a few days the problem came back. I'm not sure if it's the phone or the sim card.
jmnz said:
I've been having the same problem. I took it back to the t-mobile store and they gave me a new one but after a few days the problem came back. I'm not sure if it's the phone or the sim card.
Click to expand...
Click to collapse
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Xdpker06 said:
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Click to expand...
Click to collapse
Yeah I thought I was the only one having this problem. I'm from around the LA area and no I don't have that app.
I also have the same problem. I am in Foxboro, MA. I called Tmobile and they are telling me it's a network issue. Supposed to be resolved in 72 hours. I'll post back with my results.
I seem to be running into the similar issue. I once resolved it by installing the Rooted nandroid available here, it had gone away so I re installed a custom rom but then after a couple weeks it came back? I read thru the forums that's it may have to do with facebook contacts? I'm trying out the new energy rom now, hopefully it clears the problem
mbotelho said:
I also have the same problem. I am in Foxboro, MA. I called Tmobile and they are telling me it's a network issue. Supposed to be resolved in 72 hours. I'll post back with my results.
Click to expand...
Click to collapse
Sweet. I factory reset my one s last night and haven't had this problem today. Don't know whether to attribute it to the reset or t mobile fixing their network. Either way everything's good so far.
Xdpker06 said:
Sweet. I factory reset my one s last night and haven't had this problem today. Don't know whether to attribute it to the reset or t mobile fixing their network. Either way everything's good so far.
Click to expand...
Click to collapse
I tried factory resetting my phone about a week ago but after a few days the problem came back. I'm hoping T-Mobile resolves this problem soon.
Try Factory Reset and also try clearing Cache/Data in the Phone Application Settings if applicable. Obviously, reboot afterwards.
I'm going to assume you are not rooted.
I did a factory reset as well, but still had the problem. I'll try to clear my Phone data/cache first and also try another factory reset today.
I spent an hour on the phone with Tmobile advanced tech support. They think it's a network issue, but haven't figured out exactly what it is yet.
Another thing, when I have Wifi calling on, my caller id works just fine. Really weird.
I did another factory reset today, didn't update any of the apps, basically didn't touch anything and caller id is still not working.
I am also on the latest OTA update. I wonder if that has anything to do with it?
I love this phone, just wish I could tell who is calling me.
So I've discovered a little more from testing this morning. Would be interested to hear if anyone else sees the same thing.
Reboot the phone with Wifi off -> Caller ID works -> Turn on Wifi and Wifi calling ->
Caller ID broken.
Reboot the phone with Wifi off -> Caller ID works -> Turn on Wifi with no Wifi calling -> Caller ID still works.
Looks like the issue might be related to Wifi calling somehow. I'll update Tmobile tech support and hopefully they have some kind of answer.
Ok so after hours of reseting the phone, the settings, wipping everything, re installing the Rom all this over and over, doing nandroid etc... I finally got it to show me the caller ID again.
It was weird because for a while I could get it to show it to me after a new install but then as soon as I'd reboot, It go back to the same thing.
Still confused as far as what is making it hide the caller info. I doubt it's Tmobile network because then I would imagine at least some other phones would have similar issues. then again I don't know because when it started again for me yesterday I was just driving on the road, no settings had been changed (although I had just left my house wifi)
its very confusing
well i am having the same issue. and i have Samsung Galaxy S2. my caller id shows as UNKNOWN
Xdpker06 said:
Yes! Thank you! I thought I was alone here. Where are you from? Do you by any chance use an app called screen filter?
Click to expand...
Click to collapse
Just want to share that I'm having the same issue on my One S. Seems random but have not done any testing to try to figure out a pattern. I'm in southern NH if that makes a difference.
Sent from my cm_tenderloin using xda premium
HeydavidV said:
Just want to share that I'm having the same issue on my One S. Seems random but have not done any testing to try to figure out a pattern. I'm in southern NH if that makes a difference.
Sent from my cm_tenderloin using xda premium
Click to expand...
Click to collapse
Thanks for sharing. I'm in the bay area in CA. I don't want to jinx it, but I haven't had this problem occur in 48 hours. But I have noticed that it occurs more when new numbers call you for the first time so I don't really know because I haven't had anybody new call me.
Got an S3 a week ago, coming from a Nexus. Took it home and rooted and rom'ed it with AOKP M1.
Used the nav for the first time yesterday, and I literally had to have the phone in my left hand within an inch of the window or it would lose GPS.
Tried all the tricks
FasterFix, Faster GPS, GPS Toolbox
Tried this
http://forum.xda-developers.com/showthread.php?t=1880810
I can get a lock if I am outside usually, driving is very challenging to get a lock. Had the same type of issue with my Fascinate and ended up exchanging it before it finally worked.
Will I need to do the same here?
I have not tried it stock, stock sucks.
I have not tried either of these yet, but wondering if it's worth even trying to polish a turd or move on.
http://rootzwiki.com/topic/37182-tutorial-how-to-fix-a-bad-gps-on-galaxy-s3-verizon/
http://forum.xda-developers.com/showthread.php?t=1880411
I remember when I first flashed aokp or aosp I had same problem. I had to go back to stock TW and get gps lock and then flash aokp/aosp. Same thing for nfc. Not sure if that is still the case. Haven't been on aosp for a while now.
Sent from my SCH-I535 using xda premium
Its had lock on the stock image, just never really used it to nav.
having the exact same issue as you, tried most of the fixes/apps from the play store. almost wondering if there is a hardware issue. does anyone know if swapping in a gps.conf from say stock ICS would improve performance in the jellybean vrlblk3 leak?
Back to stock now, and it's not any better.
Stupid thing has to be almost touching the glass or outside of the car to not drop GPS. I am going to call VZ and get a replacement sent out.
a vz rep told me to power down the phone, pull the sim for 30 seconds and try to get a lock again. it worked for my wifes phone but not mine. vz is overnighting my replacement, but try that sim card method though
What I did was take off my case. It is a basic rubber case which I'd love to have, hut it really lags my locking. So once I did...I get like an instant lock now.
Sent from my SCH-I535 using xda premium
I was having GPS problems. I was finding satellites but not locking on and stuck in the "searching for GPS..." mode. I tried everything -- clearing data, the AGPS patch, flashing modems and new ROMS.
SOLVED: Odin stock.vzw_root66.tar. Then, do a full factory reset by typing *2767*3855# into the dialer. This will completely wipe the internal storage, not just /data like in recovery.
From there, your SGS3 is basically as good as new, and you should be able to set the GPS up normally.
Edit: I think the problem has to do with the VRBLK3 bootchain. Keep that in mind when reflashing.
sweeds said:
I was having GPS problems. I was finding satellites but not locking on and stuck in the "searching for GPS..." mode. I tried everything -- clearing data, the AGPS patch, flashing modems and new ROMS.
SOLVED: Odin stock.vzw_root66.tar. Then, do a full factory reset by typing *2767*3855# into the dialer. This will completely wipe the internal storage, not just /data like in recovery.
From there, your SGS3 is basically as good as new, and you should be able to set the GPS up normally.
Edit: I think the problem has to do with the VRBLK3 bootchain. Keep that in mind when reflashing.
Click to expand...
Click to collapse
Completely agree... I did the same about 5 days ago. Have not had a problem yet. I have been testing it multiple times a day. Locking is very good after root 66. I also used triangle away before Odin to reset flash counter.I am afraid to install a custom recovery now. I really agree that it has something to do with the bootchain and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SCH-I535 using xda app-developers app
I really do miss KCrapMods... If anyone does this and is brave enough to install a recovery let me know how it works out. I need GPS to bad right now to play around.
sweeds said:
I was having GPS problems. I was finding satellites but not locking on and stuck in the "searching for GPS..." mode. I tried everything -- clearing data, the AGPS patch, flashing modems and new ROMS.
SOLVED: Odin stock.vzw_root66.tar. Then, do a full factory reset by typing *2767*3855# into the dialer. This will completely wipe the internal storage, not just /data like in recovery.
From there, your SGS3 is basically as good as new, and you should be able to set the GPS up normally.
Edit: I think the problem has to do with the VRBLK3 bootchain. Keep that in mind when reflashing.
Click to expand...
Click to collapse
i may try this soon to help confirm it works. i already have a replacement being sent to my house since i had already tried "everything else".
both my wife's and my phones lost GPS about the same time before the JB update. no ROM flashing or and crazy apps were being used. just stopped locking.
For you guys on CM10.1 and I would guess any AOSP based build, this commit http://review.cyanogenmod.org/#/c/29531/ should clear up this issue of GPS working for some and not others. Looks like if you flashed a rom and had GPS turned off at the time, your GPS could get locked in a way that made it not function properly anymore.
Looks like this commit will be in the next nightly, but I made an unofficial CM10.1 build yesterday with it, if you want to give it a try and see what happens.
http://d-h.st/4zP
Got my replacement and locked on right away from inside my building.
Are you saying that if I flash again its going to screw up again?
This thing is so laggy compared to AOKP's 4.1
I got my replacement and flashed a pre rooted Rom, installed recovery with Rom manager, unlocked the bootloader with ez unlock then flashed beans build 8. No GPS problems whatsoever. I get a lock down to 3 meters within 10 seconds
Sent from my SCH-I535 using xda premium
Turn on wifi first before using gps. You'll get a lock on in seconds.
Sent from my SCH-I535 using Tapatalk 2
Turning on Wi-Fi is not gonna help the GPS once you start traveling when Wi-Fi isn't available
Sent from my SCH-I535 using xda premium
The new phone with Beans 8 is locking instantly, this ROM is amazing so far. Thanks for pointing it out.
Simple mechanical GPS fix involving tightening the back frame of the phone
Hi,
I have a simple GPS fix that worked for me. I'd like to mention that the solution may not work for all but it did work for me after I tried just about every fix possible. For example I flashed back to stock, performed numerous battery pulls, used many of the AGPS patches, made numerous edits to the gps.conf file, reprovisioned my phone, checked different ROMs, uninstalled/reinstalled Google Maps, cleared data for Google Maps and Google Service Framework, and so on.
I tried all of the above methods because my GPS would take forever to get a fix both indoors and outdoors (I know it usually takes longer to get a fix indoors), wouldn't hold the fix while navigating and my GPS apps kept stating "Searching for GPS", would see 20+ satellites but would never lock on to them...man it was really frustrating. I just about gave up.
However, as I was trying to follow another procedure to fix my GPS which required me to pull my battery I noticed that when I removed my back cover that the back frame that has all the screws was slightly loose on the left side. Once I tightened them all up my GPS worked immediately! I've tested for a day and I consistently got a lock on the satellites in about 2-15 seconds depending on my location. My navigation also worked and wouldn't cut in and out.
Like I said it may not work for everyone but I would recommend that if you have a GS3 definitely check the back frame of your phone and make sure everything is secure. I've tried my GPS on the stock and CM 10 stable ROMs and I have achieved GPS locks consistently.
I hope this helps. Maybe this has already been shared but I figured I would post in case some of you haven't seen it yet.
Cheers.
Hello Guys,
I know many people here are wondering that how to fix the GPS issue after upgrading to Jelly Bean 4.1.2 I have been searching for a long time now and last week I found a proper fix for this problem at last
The GPS problems people are facing after upgrading to 4.1.2 JB are :
1. GPS taking a long long time to show my location
2. Maximum time it shows that unable to find my location
3. Even if I use Gps Fix or GPS Fix Delux application, I have to do the fix everytime I turn on my GPS, reboot my phone, if I'm not using GPS more that 1.5 - 2 hours
It's Really Annoying . . . Thats Why I came up with a brilliant solution of this which whill need fix for 1 time only. You will never have to fix your GPS again.
The Steps for One Time fixing the GPS issue:
1. Download this Application from play store : GPS Status - Test & Fix
2. Go under open sky
3. Open the application.
4. If you see that your Latitude and Longitude are not Showing, then your GPS is not working.
5. For that case, 1st tap on the "Reset GPS"
6. Then Tap on the "Get Xtra Data"
7. This will take 5-10 mins of time to completing the fix. But make sure you are under open sky and You are Connected to Internet. To get the Xtra Data, the application will need Internet connection.
8. After a while when you will see that the application is showing your Latitude and Longitude, you will understand that your GPS has been fixed. You will never have to run this app ever again. From now on your GPS will get auto locked to your position.
Enjoy
*** NO ROOT REQUIRED ***
Screenshots:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this thread helped you, dont forget to hit the thanks button :good:
This 'Xtra data' thing is in "GPS Aids' as well. But it does not stick forever. Are you saying now after using the tool you mentioned, anytime you are outdoors just opening say for example Navigation or Maps you get a direct gps lock within a minute or so without making use of additional gpsfix apps ever?
Can you post your gpsconf file here after you have used this app?
RAD7 said:
This 'Xtra data' thing is in "GPS Aids' as well. But it does not stick forever. Are you saying now after using the tool you mentioned, anytime you are outdoors just opening say for example Navigation or Maps you get a direct gps lock within a minute or so without making use of additional gpsfix apps ever?
Can you post your gpsconf file here after you have used this app?
Click to expand...
Click to collapse
Yes brother it worked for me even if I do reboot my phone or turn on my gps after long time keeping it in off state, it just auto lock my position. Yes sometime tough it takes a little time, but I never have to do gps fix again. Also as you requested I'm attaching my gps.conf file here.
You can get it from here: https://www.sugarsync.com/pf/D1732447_087_30755727
P.S.: It took almost 1 minute and 29 seconds to lock my position.
Sent from my ME865 using Tapatalk 2
isaumya said:
Yes brother it worked for me even if I do reboot my phone or turn on my gps after long time keeping it in off state, it just auto lock my position. Yes sometime tough it takes a little time, but I never have to do gps fix again. Also as you requested I'm attaching my gps.conf file here.
You can get it from here: https://www.sugarsync.com/pf/D1732447_087_30755727
P.S.: It took almost 1 minute and 29 seconds to lock my position.
Sent from my ME865 using Tapatalk 2
Click to expand...
Click to collapse
I used root tweaker and m getting it fixed
Sent from my ME865 using xda premium
Ok I used this tool today and I tested it randomly through the day before I came to commenting and I second your post that indeed this thing has been the best so far of all tools I used for the gps fix. The reason I had asked for your gpsconf file was to see values this tool wrote & yours is the global ntp pool, I have mine manually edited as the India ntp server. On second use it did refuse to lock but thereon the results have been nearly instantaneous :good:
RAD7 said:
Ok I used this tool today and I tested it randomly through the day before I came to commenting and I second your post that indeed this thing has been the best so far of all tools I used for the gps fix. The reason I had asked for your gpsconf file was to see values this tool wrote & yours is the global ntp pool, I have mine manually edited as the India ntp server. On second use it did refuse to lock but thereon the results have been nearly instantaneous :good:
Click to expand...
Click to collapse
Really happy to know that it worked for you brother, sometimes it take 2 minutes to lock the gps. Don't worry just wait it will be automatically locked
Sent from my ME865 using Tapatalk 2
Worked perfectly, bro. Thanks for the solution. I must say JB 4.1.2 absolutely rocks!
Thank you worked for me too! I recently purchased GT-H9500 (S4 clone) I'm pretty sure I checked the gps when I got it a week ago and it worked. I rooted a few days ago and it did not work.
The app took about 15-20 minutes. it was interesting watching it, first it was 0/0 then 0/1 then 0/2 etc, finaly the screen populated with similar data above.
the magnetic field is "not available" for some reason
ozzman77 said:
Worked perfectly, bro. Thanks for the solution. I must say JB 4.1.2 absolutely rocks!
Click to expand...
Click to collapse
I'm really glad to know that it works for you. Please don't forget to give a thanks a reputation.
Sent from my ME865 using Tapatalk 4 Beta
mgh0621 said:
Thank you worked for me too! I recently purchased GT-H9500 (S4 clone) I'm pretty sure I checked the gps when I got it a week ago and it worked. I rooted a few days ago and it did not work.
The app took about 15-20 minutes. it was interesting watching it, first it was 0/0 then 0/1 then 0/2 etc, finaly the screen populated with similar data above.
the magnetic field is "not available" for some reason
Click to expand...
Click to collapse
I'm really glad to know that it works for you. Please don't forget to give a thanks a reputation.
Sent from my ME865 using Tapatalk 4 Beta
Hi,
I have tried "GPS Status - Test & Fix" in my LG Optimus L5 II Dual E455 phone and it didnt fix the issue. I got the phone 2 weeks back and only first time the navigation worked. I think i did an update software for LG the first time and I think it stopped working after that. I had tried the "GPS Status - Test & Fix" several times,also restarted and reset the phone couple of times. it hasnt fixed yet.
Any other suggestions would really help.
Thanks in advance.
An Update:
Now my GPS is working. What i had tried is i went to LG Customer Support and they swaped my Sim 1 and Sim 2 as my Sim 1 was earlier in roaming. Then they enabled my Data Connectivity instead of wifi and were able to get the position in the google maps. But my GPS application "navfree" and "GPS Status-Test & Fix" were still not able to fix the Satellites.
So, i came out disappointed. Then i travelled with my Data Connectivity enabled and used "Google Apps" for navigation for one whole day. Then i tried the "GPS Status - Test & Fix" and few other GPS fix apps and they all started getting the satellite fixed. Now, i disabled and tried the GPS app "navfree" for past few days without Data Connectivity and its working.
So in Summary to have it work :
1. Swapped the Sim's
2. Enabled Data Connectivity in the non-roaming SIM
3. Use Google Navigation for a day with it
4. Run "GPS Status -Test & Fix" in open sky and reset old data and get new GPS Data.
5. GPS satellite got fixed
6. Turned off Data Connectivity
7. Tried NavFree app.
8. working for past few days without issue and without data connectivity.
Hope that helps for other users.Also, thanks to "isaumya" for providing the initial solution.
din_jig said:
Hi,
I have tried "GPS Status - Test & Fix" in my LG Optimus L5 II Dual E455 phone and it didnt fix the issue. I got the phone 2 weeks back and only first time the navigation worked. I think i did an update software for LG the first time and I think it stopped working after that. I had tried the "GPS Status - Test & Fix" several times,also restarted and reset the phone couple of times. it hasnt fixed yet.
Any other suggestions would really help.
Thanks in advance.
Click to expand...
Click to collapse
Interesting I find this post today as I am in roughly the same boat, except I have owned the phone for a couple of months now and was beginning to think it was related to a software update. I may try restoring an earlier version and seeing if that fixes it.
spunkylm said:
Interesting I find this post today as I am in roughly the same boat, except I have owned the phone for a couple of months now and was beginning to think it was related to a software update. I may try restoring an earlier version and seeing if that fixes it.
Click to expand...
Click to collapse
Can only speak for Motorola Atrix 2 & the one & only final fix for the damned gps lock issue is by a user called 'ghittone', that is the only one that works & nothing else, period!!
thanks
Thanks dude.. I works...!!
Hey, the "Get Xtra Data" for me works really fast, not even close to 5-10min you said. How do I know it's working?
:good::good::good:
I didnt work for me
Hi,
I did what you said. after sometime it shows the screen you have shared, however whenever I start that app again or even try to navigate using google map problem remains as it is
Hi,
I have a strange issue that only seems to affect my Gear 2 - everything else on Lollipop seems OK.
I am running the leaked stock ROM N9005XXUGBNL8 - rooted. I have also loaded the latest Gear Manager - 2.2.14112899.
When I turn on the watch or Phone, the devices connect correctly, and everything seems to work well. My problem is when I move out of range. The watch shows that the Bluetooth disconnects, but the phone still thinks that it is connected. When i move back into range, the phone and watch remain disconnected unless I manually reconnect by turning the phones Bluetooth off and then on again.
I have reloaded both the phone and watch, but still have the same issue. Sine the Lollipop ROM has not yet been formally released, I cannot ask Samsung for help, so if anyone can suggest a solution, I would be very grateful.
Thanks in advance, Richard
Hello,
I have the same problem with note 3 lollipop and gear 2.
I hope there will be a fix when lollipop arrives officially.
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Blainstorm said:
Hello,
I have the same problem with note 3 lollipop and gear 2.
I hope there will be a fix when lollipop arrives officially.
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the reply - at least I am not alone in this and that I am not imagining he issue
I also similar issue. Sometimes it reconnects automatically and other times I should manually reconnect from the Gear Manager.
Lets wait for the final Lollipop release
I am also facing the same problem. I reloaded the gear application twice and also flashed the ROM again after factory resetting the Note 3 but no change. Hope will get the solution soon.
Facing similar problem. After latest update of Note4 (still 4.4.4) watches not reconnect and bluetooth switches off. To manually reconnect i need to press "connect" in watches AND in gear manager. If i just turn on bluetooth watches connects and instantly disconnects turning bluetooth off.
The Gear Manager today updated to 2.2.15011799.
I do not know if this has improved matters yet, but will post if it does.
Update,
Seems to disconnect OK, but will not reconnect automatically. I don't know what is wrong with Samsung, but this really hampers the use of the watch.
After the update today, it works perfectly now!
It seems, the gear manager was the bad guy!
Best regards
Sent from my SM-N9005 using XDA Free mobile app
Still does not really work for me. I need to toggle bluetooth on the phone after a disconnect, but not every time.
Next day the same problems. But the gear is now faster connecting and transferring data. Before the update the gear taken 20 or 30 seconds to sync the calendar app. Now it's open Instantly.
Sent from my SM-N9005 using XDA Free mobile app
RDHoworth said:
Still does not really work for me. I need to toggle bluetooth on the phone after a disconnect, but not every time.
Click to expand...
Click to collapse
Had the same problem as well but downloaded "bluetooth auto connect" from the Play Store https://play.google.com/store/apps/details?id=org.myklos.btautoconnect&hl=en and this seems to have resolved the bluetooth connectvity problem. My gear 2 connects everytime.
Good luck
---------- Post added at 04:05 PM ---------- Previous post was at 03:59 PM ----------
I recently updated Gear Manager on my Note 3 running the leaked Lollipop 5.0. ALthough my gear 2 and manager works I have noticied that the Gear (watch) Icon which normally appears on the top left of the screen is no longer there. The gear notification messgae is still there. Anybody with a similiar issue?
Same here.
Also tried the Bluetooth auto connect, but this does not seem to work. Can you share the settings you used?
Thanks
Sent from my iPad using Tapatalk
I have noticed some more detail:
When i go out of range, the watch disconnect but often, the phone still seems to think the watch is connected. However, when I check the phones bluetooth setting, the watch is connected, but the Phone Audio is disabled. Occasionally, only a reboot will cure this.
I have also spotted several other issues relating to Bluetooth and Lollipop on the XDA forums, such as intermittent connection to Car phone systems, which I have also noticed. I am beginning to suspect that the main problem here is with the Lollipop bluetooth rather than specifically with the Gear. The ensd result is the same - a system that does not work correctly that should be supported and fixed by Samsung.
I have just upgraded the room to the Polish ROM released yesterday and carried out a factory reset.
I still have the same issues. It seems fairly clear that the phone does not recognise that the phone goes out of range and so status connected.
Given Up
I have given up and reverted to the Stock KitKat ROM. Guess what? everything now works.
I don't think that Android 5 is ready yet - will now wait for 5.1
Search for S6 apps (it is on in xda-developers forum as well). There is a version of the Gear Manager that solves the reconnect issue. I tested it shortly and it works on official lollipop for Note3.
EDIT: After some reboots, recconects are not working properly again.
Any news on how to solve this guys? Same problem here...
Enviado de meu SM-N910F usando Tapatalk
Hello every body,
I've the same problem with my N9005 under Lollipop.
Problem with bluetooth reconnection of my Gear S.
And for me I've another problem, my phone reboot several time per day, maybe due of this problem.
Do you face this problem too?
Hi!
This is the problem with me too! Not reconnecting. Do you have any solutions?
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
I have that same problem.
I tried 5 different custom roms, I tried the kernel, it didn't work.
everything is working, only the sound on the phone call is neither going nor coming. same as normal earphone with bluetooth earphone.
audio recording in video recording, music working, microphone recording sound, but no sound in calls. There is an imei signal, but there is no solution.
Even emergency calls have the same problem.
why could it be?
Thank You for replying, OnlineBeyin!
And here I thought, I was completely alone in this. At least there's someone out there sharing the pain!
Well, here's to a strage new Problem.
In a funny way, I love this about digital technology; it never gets boring - as soon as you'd think you've got your stuff figured out, along comes a curious problem you've never heard of or even expected to be possible.
I havent found a solution yet but having someone with the same problem gives me hope, maybe together we can work it out.
I don't think it's about the custom ROMs since You tried five of them to no avail. What do You mean by "trying a kernel"?
I've come to terms with it since I kind of enjoy the silence that not being able to answer calls has provided, but there is some other strange behaviour that might hint at a possible solution I have not yet explored:
I've taken a look at the NikGApps package I was using (core) and I've realised that
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I might need the basic version, since the core version does not provide an obvious dialer (What does "AOSP" stand for?) nor "Google Carrier Services", both of which seem quite important for phone calls.
Now me being a rather lazy fellow by nature, I thought I could just install the basic version over the the core version. In doing that, the clock app stopped working. I don't know why but opening it leads to the app crashing.
I've just seen Your post so I wanted to reply first rather then try a bunch of stuff and keep you waiting for an answer, but that's where I'm at.
So this strange behaviour (not being able to open the clock app) leads me to belive that...
<TL;DR>
Could there be an issue with different versions of programs running in the background?
(My point being Android is basically a customized version UNIX which has some similarities with Linux with which I have some modest experience with.
There I've experienced such issues around the OS telling me (paraphrasing) "the thing You want won't work like that because it is dependent on something that cannot be resolved automatically. You gotta have this version of that other thing to talk to that version of yet another thing and you have to solve that first. Then it'll work.")
So, long story short,
just to rule out this source of error, the next thing I'm going to try is to make a clean install with the full and original Version of GApps just to see if it'll work and go from there. If that won't help, I'll find out if there is something like the bash terminal from Linux just so I can see what the phone is doing exactly.
I hope this helps, if at least to spark an idea from somebody, anybody else!
I really want to get this phone working at some point, if only for sustainability's sake!
hi mate, still having the same problem...
Here's what I've tried and what I'm sure of
I tried turning off features such as google assistant voice listening and it didn't work.
I tested multiple microphones in the device with hardware test programs and the speaker that acts as a handset and it works fine.
The device is calling the other party, sending sms, just because there is a voice exchange problem, I have no doubts about imei etc.
It's purely a software issue. it's so clear
The first thing I would try would be to go back to the original rom. I haven't tested this before.
I also think that the device may have different criteria according to different countries, so there may be a conflict. But I don't think I made a lot of mistakes, to be honest.
It's very important to me that you share your every attempt.
I really want to operate this device. It's my favorite device.
In the meantime, I opened the device and tried to change the transmission films. I tried changing the bottom charging port. These are not solutions.
Hi
Cyberfreak1992 said:
I'm at the end of my rope here and I'm loosing patience with this very strange problem:
Some time ago, I received a HTC U11 from a friend. Since I came from a impenetrable (AT&T locked) Samsung Galaxy S7, I didn't bother testing the U11 before tinkering with it. I missed the freedom of a custom OS so much, that I just wanted that back again. So I don't know if the phone had worked with the originial software on it.
Naturally and right away, I unlocked it, flashed TWRP (3.6.1_9_0) , LineageOS 18.1 (2022-02-19), as well as Magisk (v24.3) and a core version of the GApps (NikGapps Core ARM64 2021-05-01) as to bloat my system as little as possible.
Now, everything seemed to be in working order. I can install and use any app like I would normally. Strangly enough, I can even send and receive speech messages in WhatsApp (haven't tried any other messenger app though).
However, if I try to make a phone call (through 3rd party apps like WhatsApp as well as "classical" phone calls alike) there won't be any audio, in neither directions from either source. Can somebody just...... I'm not that much of a noob, usually, so, HOW?
Starting out, I had another issue that a call (incoming or outgoing) would not be visible even in the task manager. I could solve the issue by reapplying a "special permission" to the phone app so it was allwed to pose itself on top of the other layers. Still, there was no audio - so could it have something to do with permissions?
Or am I missing an important (background) up with the core version of the GApps?
What I've tried so far:
- All the wipes up to and including a complete factory reset.
- Superficially checking, if I missed something during installation (nothing immediate springs to mind).
- Trying a different phone app (contacts+).
- Checking permissions of phone app.
- Trying loudspeaker and normal speaker settings.
- Using a land line to connect to my phone to check if there's any audio in either direction.
- Banging my head against the wall...!
Please help me find the reason behind this issue. It's just completely non-sensical to me that I can send and receive audio messages but my audio doesn't work during calls in both ways.
Click to expand...
Click to collapse
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Happy new year, everyone!
System23 said:
Hi
I had the same Issue with the sound in Calling etc... , this is a Problem with the DSP and when you use a CustomROM than use LineageOS_18.1-for_OREr_PIE_firm_with_DSP_patch-monthly_builds and after install ROM you must Flash this HTC_U11_DSP_TWRP_Flashable_OREO_2.33.401.19_install.zip that Fixes my Audio Problem and its work fine.
when you would more you find it here, HTC U11 - CustomROMs all with DSP Patch
Click to expand...
Click to collapse
With great pleasure I'm here to announce:
Can confirm this works! Just tried it today, the patch straightforwadly fixes this issue.
I had to skip the integrity check in TWRP to be able install it, but that should be obvious.
I already lost hope.
All the thanks and all the glory definately go to System23!