hey im wondering if this would work for us or is there some porting needed and is this somthing that would help gps and if im in the wrong section please move.
http://forum.xda-developers.com/showthread.php?t=881941
Very interesting post indeed.
From his findings, I'm also wondering if we have Auto Rotate Screen (the accelerometers) turned off, if that hinders the ability for our GPS to accurately detect location and movement. He suggested that it goes into low-power mode when it isn't detecting movement via the sensors, but didn't say what happens if the sensors are turned off.
...I'm going to have to test this out tomorrow.
Are people still having issues with GPS on the fascinate? Since we more or less had the issue fixed I've had as good or better GPS performance than on my other smartphones.
Da_G is a good buddy of mine, trust me, if anyone knows wtf they are talking about, it would be him....
lane32x said:
Very interesting post indeed.
From his findings, I'm also wondering if we have Auto Rotate Screen (the accelerometers) turned off, if that hinders the ability for our GPS to accurately detect location and movement. He suggested that it goes into low-power mode when it isn't detecting movement via the sensors, but didn't say what happens if the sensors are turned off.
...I'm going to have to test this out tomorrow.
Click to expand...
Click to collapse
im just wondering if this is safe to flash to our phones or does it need to be ported to fascinate
yep still having issues with gps...sometimes doesn't lock. sometimes takes forever. sometimes...omgsh...it actually locks!
not reliable.
I applied the d101 gps fix to eb01 and my gps locks in around 20sec. Auto rotate or not my gosh never locked on eb01 without the d101 fix.
Sent from my SCH-I500 using Tapatalk
Just tested my gps a little. Mine is locking within 5 meters in a brick building with auto rotation on or off. Not in a car currently but I took a little jog and it seemed to follow my direction and location very accurately in both.
So I guess my GPS is pretty good.
Regardless... I wanted to say thanks for reposting that because it was a really interesting read!
It should just work, even though EB01 stock should just work too.
Just don't flash the AT&T-specific version...
The Fascinate doesn't seem to have the same layout concerning the gps jupiter files (I don't see them anywhere, at first glance). Either I am missing something or it's a completely different setup.
There are some settings in his /data/gps/secgps.conf (just a text configuration file) that are different than the stock fascinate file. These might be worth looking into to see if they help improve the signal without using his modified binary. You don't need to flash the file using CWM, just use adb to push a modified file (or root explorer and edit it on the phone itself).
Since this is a CDMA phone, I don't know how many people this would affect, but here is a general Android GPS tip for those who don't live in North America:
In /system/etc/gps.conf, change the address to the server that corresponds to your country:
Code:
NTP_SERVER=[COLOR="Red"]north-america[/COLOR].pool.ntp.org
I usually can't get an accurate lock or any lock at all unless I reboot with gps already enabled. Then I will get a good lock instantly... If I reboot the phone with gps off then I will get no signal/lock again.
Sent from my SCH-I500 using XDA App
Let me share my experience with GPS on EB01, it's GREAT, you just have to turn on GPS "correctly."
If I turn on GPS using the Notification switch, GPS takes FOREVER to lock, if it even does so. Gone several minutes with no lock.
Now here's the thing, if you turn on GPS in the Settings > Location settings, I always get super fast, under 5 second GPS locks. ALWAYS. I've tried this out repeatedly over several days, and it really makes a difference. Once you turn on GPS using Settings, you can leave your phone on, reboot, whatever, and GPS will still be responsive. If you turn it off, wait a while and use the Notification switch to turn on GPS and you're trying to get a cold lock, it'll be slow again, just be sure to use the Setting option and it'll be back to being responsive.
That's my experience.
CrushD said:
Let me share my experience with GPS on EB01, it's GREAT, you just have to turn on GPS "correctly."
If I turn on GPS using the Notification switch, GPS takes FOREVER to lock, if it even does so. Gone several minutes with no lock.
Now here's the thing, if you turn on GPS in the Settings > Location settings, I always get super fast, under 5 second GPS locks. ALWAYS. I've tried this out repeatedly over several days, and it really makes a difference. Once you turn on GPS using Settings, you can leave your phone on, reboot, whatever, and GPS will still be responsive. If you turn it off, wait a while and use the Notification switch to turn on GPS and you're trying to get a cold lock, it'll be slow again, just be sure to use the Setting option and it'll be back to being responsive.
That's my experience.
Click to expand...
Click to collapse
Nice observation...just worked for me too!!
By golly... He's right, although it took me about twenty seconds to lock.
Sent from my SCH-I500 using XDA App
Hmm... I remember this from a different android device I have. The stock power control widget for wifi would take 45 seconds longer for the network to connect then if I would go to the wifi menu and turn it on myself. I found out that there were two methods for turning on the wifi programmatically, and that some widgets used one method and the other widgets used the other.
If I remember right, the fast method changed the setting by calling the wifi menu and emulating the menu press, while the slow method attempted to power on the wifi directly.
$10 says that if you started decompiling, you'd find a similar situation here.
I have a Nexus 5 with Google Play Services v. 6.5.99 and I'm getting some strange behaviour with the Smart Lock feature.
When I initially used the Trusted Places feature, I noticed that when I drove away from my home, the lock function didn't work automatically. This is also happening on my husband's Nexus 6. I don't think this is right and believe the phone should lock when you move away from the unlock zone.
However, the main problem I'm having is that the phone won't lock when I turn off the Home toggle and have no customised places set up. I also deleted a work address in Google Maps and so this option is naturally greyed out in Smart Lock Trusted Places. At one point, I played around with adding my home as a customised place and have since deleted it. I also changed my home address in Google Maps to my parents' address so I could test it when I was at my own home to see if the phone would lock. Nothing seems to work.
The only way I can get the phone to lock now is to disable the whole Smart Lock feature in Trusted Agents, otherwise I have a phone which won't lock. The exception is after a reboot - I have to unlock it once and then the phone stays unlocked.
Because of this, I can no longer use the Face Unlock feature either.
I've read that some people are finding they have to unlock their phone when it should be unlocked already but it's worse if you have no Trusted Places set and the phone won't lock. Does anyone else have this problem?
I too have the same problem with my Nexus. Only way to enable lock for me was to disable smart lock or turn the Location service off
Glad it isn't just me. I set my parents address as a customised place and the behaviour seemed to be as it should be when I went there. It appears that the problem lies with the Home trusted place.
I have the same problem although I've never used trusted places. I have a smartwatch setup as a trusted device, phone is a Nexus 6 rooted
So I've got BT enabled and paired for both my N9 and my N5. The smart lock is on my N9 and set up to trust my N5. It always shows Not connected and requires a PIN.
Also, I've got my home as a trusted place, but it still requires a PIN when I'm there. I've checked Maps, and it knows it's here. It even shows the word "Home" underneath my blue dot.
The only thing that works is Trusted Faces, but that's so finicky I can't rely on it for anything.
Do you have location set to high accuracy? It wont work unless it is.
After a couple weeks of trying to figure out why I cannot initially enable Wi-Fi calling, I was able to get a workable solution. A little bit of backstory first. There are five lines on my account, all of which have Smart Limits enabled. Turns out, Smart Limits disabled vo LTE... This however is required for Wi-Fi calling.
Tldnr, disable ATT SMARTLIMITS if it is enabled, full power cycle (power down not just reset) and try to set it up again.
* this was on a stock s7 no root, no custom rom, full carrier bloated phone.
xwtfbobx said:
After a couple weeks of trying to figure out why I cannot initially enable Wi-Fi calling, I was able to get a workable solution. A little bit of backstory first. There are five lines on my account, all of which have Smart Limits enabled. Turns out, Smart Limits disabled vo LTE... This however is required for Wi-Fi calling.
Tldnr, disable ATT SMARTLIMITS if it is enabled, full power cycle (power down not just reset) and try to set it up again.
* this was on a stock s7 no root, no custom rom, full carrier bloated phone.
Click to expand...
Click to collapse
dealing with similar on a new S8, but I'm wondering if the phone you enabled was purchased from AT&T or at least AT&T branded out of the box because at this point I can't get wifi calling working no matter what because i bought an unlocked s8. thanks for any insight!
Wifi calling
A bit of background:
I've been trying to set up internet access at a small home out in the country with cell service being the only option. Being cheap, I decided to try going down the route of tethering an old phone (Pixel XL) to a router and getting data-only plan (2GB of high speed at T-mo for $10/mo). The idea was that this would be enough to support my ring security system, some blink cameras and occasional internet use.
The problem:
Initially everything seemed fine. I got an Asus AC1300 (RT-ACRH13) router with USB 3.0 port for tethering and set up the Pixel XL to tether to it. However, I soon discovered the USB tethering option would get disabled by the phone quite frequently. This was due to a number of reasons...power briefly going out (fixed this by adding a UPS); pixel getting an update pushed to it (also disabled); bad weather causing signal to drop (can't fix this one); there appear to be other reasons as well i've not yet identified;
Tried so far:
Installed tasker thinking I could set it up to periodically re-enable tethering. Discovered for that I needed root, so I rooted the pixel. Tasker still complained - got a response from them stating that as of Pie "unfortunately Google now protect this action under the MANAGE_USB permissions which only system apps can get". Tried the Secure Settings app/extension for tasker and that just fails when testing the action without any additional notes - no response from the developer on that.
So, any ideas on how to accomplish what I'm trying to do? All i'd like is for USB tethering to be automatically re-enabled every few minutes if it's off.
L
Sent from my LM-V350ULM using Tapatalk
petik said:
A bit of background:
I've been trying to set up internet access at a small home out in the country with cell service being the only option. Being cheap, I decided to try going down the route of tethering an old phone (Pixel XL) to a router and getting data-only plan (2GB of high speed at T-mo for $10/mo). The idea was that this would be enough to support my ring security system, some blink cameras and occasional internet use.
The problem:
Initially everything seemed fine. I got an Asus AC1300 (RT-ACRH13) router with USB 3.0 port for tethering and set up the Pixel XL to tether to it. However, I soon discovered the USB tethering option would get disabled by the phone quite frequently. This was due to a number of reasons...power briefly going out (fixed this by adding a UPS); pixel getting an update pushed to it (also disabled); bad weather causing signal to drop (can't fix this one); there appear to be other reasons as well i've not yet identified;
Tried so far:
Installed tasker thinking I could set it up to periodically re-enable tethering. Discovered for that I needed root, so I rooted the pixel. Tasker still complained - got a response from them stating that as of Pie "unfortunately Google now protect this action under the MANAGE_USB permissions which only system apps can get". Tried the Secure Settings app/extension for tasker and that just fails when testing the action without any additional notes - no response from the developer on that.
So, any ideas on how to accomplish what I'm trying to do? All i'd like is for USB tethering to be automatically re-enabled every few minutes if it's off.
Click to expand...
Click to collapse
No personal experience with this but the scenario you are describing is a constant problem for people living in an RV (recreational vehicle). You may want to include RV product/solutions to see what they've come up with.