Related
I searched for discussions on this and couldn't find any. Sorry if I'm posting something that has already been discussed.
I have followed the saga of GPS on Gingerbread, and I tried out a couple of GB ROMs over the last couple of days and was thrilled to see GPS working!
Unfortunately, the compass, an important component when navigating, it seems is broken on all Gingerbread ROMs for the Vibrant, from what I hear.
What is preventing this from working? Is it another component that is completely blocked until we get a leak?
Thanks!
Bump.
No one knows?
Try turning on the GPS sensor.
Emal510 said:
Try turning on the GPS sensor.
Click to expand...
Click to collapse
As I mentioned, from what I understand, this is an issue with GB ROMs on our phones, similar to the GPS issue that was only just recently somewhat solved. I got that info from the dev of Revolution ROM.
Could someone please test it on the newsets GB ROMs/Kernels? I'm also wondering is it working correctly with CM/MIUI?
I'm almost 100% sure this isn't working in the latest nightlies of CM7. Viewed as a low priority in comparison to the 911 issue and other things.
Here's the story:
Had a vibrant, put Axura (Axura 205 Vibrant) on it. Worked great for many many months, until I broke the screen. I tried to replace it but that's another story.
Fast forward to now, I have a new Vibrant, with the same ROM on it, (flashed from stock).
I have tried 6 or 7 different ROMS of various release (Froyo/GB), but the GPS never shows satellites. I have done the access LBSTest fix as suggested elsewhere in the forums, but still not seeing satellites.
On my old phone this specific ROM (Axura) worked great. Same ROM, another phone, doesn't work.
It feels like the gps hardware is bad (I bought the phone used) but my business partner's phone does the exact same thing.
ANY diagnostic steps or outline would be great! I don't know how to determine if the GPS hardware is functioning properly or not. A link, list or other from someone who has dealt with this before would be a wonderful help.
THANKS!
(The only odd thing I have noticed is the stock rom won't connect to any cellular networks. Putting Axura (or any ROM) corrects that issue.)
EDIT: I should note that enabling "Use wireless networks" allows some data to be used, but I assume this is based off of hardware mac addresses of the wireless routers and google's location database rather than actual satellite data
I should also note the manufacture date is 10.10 and the current modem is JK2.
I have been researching various fixes (in spite of the anomaly stated above) and it seems the hardware soldering fix only relates to pre 10.10 and suggests a modem higher than JI6.
I am tempted to try some other ROMs but have exhausted my attempts and feel maybe this isn't something I can fix anymore. Help still appreciated.
sounds like you'll need to open it and do the HW mod for the GPS antenna contacts to be firm together, I used a piece of shaped plastic to keep the tab in an elevated position so it wouldn't lose tension after its snapped back. then DL heathens GB GPS fix , it works awesome for me, best GPS lock ever
Oh an one more thing, Aurora isn't the best choice of ROM, unless that's what you like. JMHO
Thanks. I'll do both, I am kind of apprehensive about soldering the gps, I have broken things before, although I am ok with a solder gun.
Any suggestions on ROMS? I am open for them, have tried a few (Cm7, SIMPLE, Revolution, + others) but since I couldn't get the gps to work I assumed it was rom related.
You might also try a new modem with a Froyo ROM. Any of the KAx or KBx modems with a Froyo ROM should be an improvement.
Sent from my SGH-T959 using XDA App
dseldown said:
sounds like you'll need to open it and do the HW mod for the GPS antenna contacts to be firm together, I used a piece of shaped plastic to keep the tab in an elevated position so it wouldn't lose tension after its snapped back. then DL heathens GB GPS fix , it works awesome for me, best GPS lock ever
Oh an one more thing, Aurora isn't the best choice of ROM, unless that's what you like. JMHO
Click to expand...
Click to collapse
Something I've noticed with the hardware fix is the author of the post here states that the manufacture date is 9.10 or before, and mine (10.10) shouldn't need it. Is this true?
shrapnelx said:
You might also try a new modem with a Froyo ROM. Any of the KAx or KBx modems with a Froyo ROM should be an improvement.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Running KB5 now. Which app do you recommend for seeing what/how many satellites have a lock? The one I am using now (Gps Status) just has a spinning icon on the bottom, with no info.
I am at a loss as to why this phone won't lock. I'm willing to paypal anyone who has the time and gumption to assist with a true repair.
Edit: Just went outside with the GPS Test app (disabled use WiFi for location) and it could "see" 1 satellite, but was using 0. Does this help in giving an idea as to why it won't work?
Maybe the antenna issue can still exist post the 9.10 manufacturer date.
:S
It's been a while. I miss my GPS and compass working right. Any Ginger roms made improvements to GPS or compass accuracy since last I looked at roms in early summer?
If not, I'm ready to go back to Froyo.
Short answer, yes.
Long answer, search
I searched and read for a half hour. Only thing I see is that GPS works, sorta, if you don't turn it off and compass is still wonky. Nothing new I guess.
stable cm7 with streamline kernel will give you really good gps. first time I was able to use navigation on gb rom. my phone is from original june batch so that saying a lot. compass never really worked on our vibrants.
Yea compas dont work but gps on cm7 with streamline works great ccan be turned off and on at will without adverse effects... its performance however is a bit subpar.. takes a Long time to lock and can sooometimes lose a lock temporarily
Sent from a cell tower to the XDA server to you.
thank you. Just wondering. I was trying to use google sky the other day and it was completely unusable. At least it worked well when I was on froyo.
I have been trying a variety of Android 5.0 Roms on my Verizon Galaxy S4. While most of them work pretty well, there is one thing that is consistent across all the 5.0 roms on my device: the compass' orientation is completely off. When held in portrait mode, the compass points east when facing west and west when facing east. If the phone is rotated into landscape mode, then north and south are flipped instead. The problem seems to be the X-axis of the magnetic sensor. I have tried calibrating the compass in variety of different ways with a variety of different apps. I also tried both the GoogyMax kernel and the Alucard kernel with the same results compass-wise.
While this would appear to be a hardware issue, the compass works perfectly in Kitkat and older roms. I even tried flashing an old Kitkat rom after trying some Lollipop roms and, sure enough, the compass was working properly as soon as the Kitkat rom booted.
Is there any way to mod the system to inverse the number normally reported for the X-axis of the magnetometer? Otherwise, is there some other way to fix this flipped compass issue?I have searched high and low, but can't find anything of use.
Same issue here, but I have sprint sgs4.
MehStrongBadMeh said:
I have been trying a variety of Android 5.0 Roms on my Verizon Galaxy S4. While most of them work pretty well, there is one thing that is consistent across all the 5.0 roms on my device: the compass' orientation is completely off. When held in portrait mode, the compass points east when facing west and west when facing east. If the phone is rotated into landscape mode, then north and south are flipped instead. The problem seems to be the X-axis of the magnetic sensor. I have tried calibrating the compass in variety of different ways with a variety of different apps. I also tried both the GoogyMax kernel and the Alucard kernel with the same results compass-wise.
While this would appear to be a hardware issue, the compass works perfectly in Kitkat and older roms. I even tried flashing an old Kitkat rom after trying some Lollipop roms and, sure enough, the compass was working properly as soon as the Kitkat rom booted.
Is there any way to mod the system to inverse the number normally reported for the X-axis of the magnetometer? Otherwise, is there some other way to fix this flipped compass issue?I have searched high and low, but can't find anything of use.
Click to expand...
Click to collapse
Currently I'm still running the KitKat GPE ROM and my compass is also flipped, I know the fix was to flash a Ktoonz kernel and it would fix the issue for that. However I don't think they've fixed it as yet for 5.0 ROMs.
It's the Kernels.
It's not due to the ROMS or hardware.
The backwards compass is due to the Kernel installed with the ROM or that you may have downloaded and applied. Kernels now are compiled as Unified kernels which work across all carriers. They are simpler for the Devs to manage without having to compile their kernels for each carrier. That messes up our compass though.
KT-Kernel's fixed our issue when they were compiled carrier specific.
Unfortunately for us KT has gone Unified like the other international Kernels and the international base and compass drivers are from the other side of the world, which cause ours to go backwards on East/West.
I have been looking through KT kernels on the Github and trying to make sense of the drivers and compile configs trying to figure out if a dev could ever come up with a patch.
But I am still new to it all when poking through the KT's source files.
I have oneplusone and it shows the same symptom. Installed magneticsensor app and found out that Bz is inverted. Bz is the direction orthogonal to screen such that it is the most important in navigation ! I would like to see the kernel source for the sensor but haven't set it up yet. If you are/know kernel dev, a help would be appreciated.
pastime1971 said:
I have oneplusone and it shows the same symptom. Installed magneticsensor app and found out that Bz is inverted. Bz is the direction orthogonal to screen such that it is the most important in navigation ! I would like to see the kernel source for the sensor but haven't set it up yet. If you are/know kernel dev, a help would be appreciated.
Click to expand...
Click to collapse
You are not going to to find much help for the Oneplus One here. It was definitely a kernel issue though, as for the Verizon Galaxy S4 it was fixed thanks to updates to the Hulk and Alucard kernels that compensate for the flip.
MehStrongBadMeh said:
You are not going to to find much help for the Oneplus One here. It was definitely a kernel issue though, as for the Verizon Galaxy S4 it was fixed thanks to updates to the Hulk and Alucard kernels that compensate for the flip.
Click to expand...
Click to collapse
Actually, I was able to fix it via /system/etc/sensor_def_qcomdev.conf and deleting /data/misc/sensor/sns.reg without touching kernel or hw-lib
see http://forum.xda-developers.com/one...tic-sensor-t3176956/post62301573#post62301573
Theoretically, we're due for a magnetic pole shift. Every 23,000 years our planet pole shifts. I know, sounds crazy doesn't it?
The CM 12.1 ROM for jfltevzw is golden except for the compass. This compass has been an issue for over an year now. I am starting a bounty to try to get this fixed. I will include some relevant informational post quotes below.
Rajones19 summarized the state of the compass on CM for jfltevzw
rajones19 said:
The last time the compass worked correctly for me was on CM11 M9, build 08/04, using Faux123's kernel - faux123-018u. Compass was working on CM10, broken on CM11 unless you replaced the kernel. Functionally was permanently broken when the change was made that disallowed 3rd party kernels in August of last year. I still have that kernel, if it would be of help to you.
The compass appears to work when you are moving, since the GPS actually provides directional data when in motion. When you are standing still, relying on the magnetic sensor for directional data, that is when the problem begins. Compass apps like GPS Status and Toolbox report compass headings in any number of directions, none of which are correct. The directional data provided to other apps that access the compass - the geocaching app, for example, or any of the astronomy apps like Google Sky, is always 180 degrees off. If this was ever fixed, I would be the happiest man in southeast Michigan
In any case, thanks for all you do. It is much appreciated.
Click to expand...
Click to collapse
AntaresOne says the compass works in his CM 12.0 nightlies for jfltexx and expects it to work on jfltevzw but it did not work when I tried his 'optimized CM 12 ROM' which is compatible with all jflte variants
AntaresOne said:
With Smart Compass:
After calibration (by virtually drawing a horizontal 8 on air) it works very well, tested on jfltexx which shares the same Compass chip with other variants
Inviato dal mio GT-I9505
Click to expand...
Click to collapse
Contributions-
phonedawg - $50
vanberge - $25
FernBch -$25
Please PM me if you wish to contribute
I am not going to be a contributor here, because I finally dumped the S4 and moved on. But I would be very curious to know if the compass on AntaresOne's build is actually 100% working, or if it just appears to work after a cursory test with Smart Compass. The real error shows up when you start using other 3rd party apps that rely on the magnetic sensor for directional information. I am not doubting AntaresOne, nor casting doubt on his work - I used his ROMs for quite sometime, and they were stellar in every other way. For everybody's sake, I do hope they get it fixed.
rajones19 said:
I would be very curious to know if the compass on AntaresOne's build is actually 100% working, or if it just appears to work after a cursory test with Smart Compass
Click to expand...
Click to collapse
Tens of users say it works. I am almost certain it works. There might be a limitation in the jfltevzw phone that is causing the compass to not work.
Put me down for 25. PayPal
Sent from my SCH-I545 using XDA Free mobile app
vanberge said:
Put me down for 25. PayPal
Sent from my SCH-I545 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks. Added your contribution.
I can do $25, too.
FernBch said:
I can do $25, too.
Click to expand...
Click to collapse
Thanks. Added your contribution
AntaresOne provided the following zips - Can anyone please try these and let me know if the compass works. I tried these but had no luck.
first flash this: https://www.androidfilehost.com/?fid=96042739161891216 reboot and test compass
if no luck,, flash this: https://www.androidfilehost.com/?fid=96042739161891217 and repeat
As far as I can tell, compass works on my du 5.1 builds.
I have flashed the above files. Each flashed started with a cache & davlik cache wipe.
The sensor hubs seemed like it wanted to work for about 2 seconds then the compass would not lock on a direction solidly. Third party apps report it as being 180 off. Calibrating the compass had no effect.
The S4 fix behaved the same as the usual.
Flashing both also did not work.
I also checked the sensors after each flash (used Advanced Sensor Tester). Each sensor has three color bars associated with it. I can see movement on the magnetic and gyroscope sensor on all three bars when moving the S4 around in various positions.
The orientation sensor shows movement on bars 2 & 3 when moving the S4 around. Bar number 1 only shows movement around the area that would be represented by 180 to 270 degrees (when facing north). Hope it makes sense, I don't know how else to describe it.
FernBch said:
I have flashed the above files. Each flashed started with a cache & davlik cache wipe.
The sensor hubs seemed like it wanted to work for about 2 seconds then the compass would not lock on a direction solidly. Third party apps report it as being 180 off. Calibrating the compass had no effect.
The S4 fix behaved the same as the usual.
Flashing both also did not work.
I also checked the sensors after each flash (used Advanced Sensor Tester). Each sensor has three color bars associated with it. I can see movement on the magnetic and gyroscope sensor on all three bars when moving the S4 around in various positions.
The orientation sensor shows movement on bars 2 & 3 when moving the S4 around. Bar number 1 only shows movement around the area that would be represented by 180 to 270 degrees (when facing north). Hope it makes sense, I don't know how else to describe it.
Click to expand...
Click to collapse
Thanks a lot. We will soon have more zips to test.
jbats said:
As far as I can tell, compass works on my du 5.1 builds.
Click to expand...
Click to collapse
jfltetmo? it works in my jfltexx too (cm-12.0/cm-12.1)
jfltevzw is the unique variant with this issue
I had issues with GPS and compass too. Flashing back to stock KitKat, enabling Location > Device Only, entering Maps, waiting for lock, and then immediately powering the phone off while GPS is locked, and reflashing root and recovery and then flashing custom ROM fixed all my issues. Compass is accurate, GPS is accurate. Has anyone attempted to do it this way? It should be noted that I am using the SPH-L720T Sprint tri-band edition (jfltespr) but my compass and GPS work absolutely flawlessly on DU 5.1 unofficial build.
SwoRNLeaDejZ said:
I had issues with GPS and compass too. Flashing back to stock KitKat, enabling Location > Device Only, entering Maps, waiting for lock, and then immediately powering the phone off while GPS is locked, and reflashing root and recovery and then flashing custom ROM fixed all my issues. Compass is accurate, GPS is accurate. Has anyone attempted to do it this way? It should be noted that I am using the SPH-L720T Sprint tri-band edition (jfltespr) but my compass and GPS work absolutely flawlessly on DU 5.1 unofficial build.
Click to expand...
Click to collapse
Is the compass correct with third party apps? The issue with jfltevzw (SCH-I545) is the compass orientation is usually 180 degrees off. The other issue that seems to affect us is the compass is only correct when moving (orientation is set by GPS). When stationary and even when walking the compass orientation is quite inaccurate.
I might as well chime in on this. I am running jfltevzw and I used to have issues on early builds of lollipop with my GPS not locking at all. Flashing back to either stock ROM or a aosp/cm KitKat build and then reflashing lollipop would fix the GPS for a while but the issue would return after flashing a new nightly. One of the developers over at Vanir found that it was the lollipop GPS blobs causing the issue. Once he started to build with the old KitKat blobs the issue was gone. I hope this helps you guys out.
Sent from my SCH-I545 using XDA Free mobile app
Triscuit said:
I might as well chime in on this. I am running jfltevzw and I used to have issues on early builds of lollipop with my GPS not locking at all. Flashing back to either stock ROM or a aosp/cm KitKat build and then reflashing lollipop would fix the GPS for a while but the issue would return after flashing a new nightly. One of the developers over at Vanir found that it was the lollipop GPS blobs causing the issue. Once he started to build with the old KitKat blobs the issue was gone. I hope this helps you guys out.
Click to expand...
Click to collapse
You are talking about the GPS. This thread is about the Compass. Not the same thing. While some have had trouble with the GPS (I was lucky, it always worked for me), the compass is an entirely different sensor, an entirely different problem, and no published fix for GPS that I ever read had any effect whatsoever on the compass.
FernBch said:
Is the compass correct with third party apps? The issue with jfltevzw (SCH-I545) is the compass orientation is usually 180 degrees off. The other issue that seems to affect us is the compass is only correct when moving (orientation is set by GPS). When stationary and even when walking the compass orientation is quite inaccurate.
Click to expand...
Click to collapse
My compass is accurate in every app I have used to test it (just installed a couple different compass apps to test). Not off by any amount, especially 180 degrees.
EDIT: and before you ask, my location was OFF during the tests.
SwoRNLeaDejZ said:
My compass is accurate in every app I have used to test it (just installed a couple different compass apps to test). Not off by any amount, especially 180 degrees.
EDIT: and before you ask, my location was OFF during the tests.
Click to expand...
Click to collapse
Yes, but your device is NOT the Verizon SCH-I545. The compass issue only seems to affect us. If you have one from Sprint, AT&T, or any other carrier it seems to work properly.
This is the last comment that I am aware of from our maintainer regarding the compass. It comes from post 135 of the CM12.0 thread
invisiblek said:
Well dang, you guys had me excited for the compass stuff =P
Its definitely the magnetic sensor that's jacked up. I actually wonder how well it works in stock.
Wonder if we need some updated firmware that we can't use because of the locked bootloader...
I'm thinking it may be an issue with our driver being updated in the kernel and our firmware not supporting it or something. I'll do some digging through the old stock kernel source, maybe I can hack something in for us.
[/url]
Click to expand...
Click to collapse
What needs to happen is the difference between us and them needs to be determined so maybe it can be figured out why it doesn't work properly for us. I may be way off here but I am curious if maybe one of the other sensors may be influencing the problem, too. I have seen some screwiness with the gyroscope as well (using advanced sensor tester).
FernBch said:
Yes, but your device is NOT the Verizon SCH-I545. The compass issue only seems to affect us. If you have one from Sprint, AT&T, or any other carrier it seems to work properly.
This is the last comment that I am aware of from our maintainer regarding the compass. It comes from post 135 of the CM12.0 thread
What needs to happen is the difference between us and them needs to be determined so maybe it can be figured out why it doesn't work properly for us. I may be way off here but I am curious if maybe one of the other sensors may be influencing the problem, too. I have seen some screwiness with the gyroscope as well (using advanced sensor tester).
Click to expand...
Click to collapse
Relax with the caps lock dude, I was just letting you know what I did to my S4, that had the same issue, that fixed it. If you don't want to try it, good for you.
SwoRNLeaDejZ said:
Relax with the caps lock dude, I was just letting you know what I did to my S4, that had the same issue, that fixed it. If you don't want to try it, good for you.
Click to expand...
Click to collapse
But I have tried it. And I did not mean to offend here.
I have gone as far using Odin to return to bone stock, reroot, recovery, etc. and the issue returns.
If anyone using the VZW variant has tried this and had success, I'm all ears. Maybe I missed something?