Related
I am having issues with my compass when using the GPS Essentials and Phone Tester app. Basically, these apps both think that the compass is always facing south or southwest. The compass in Google Maps is working though, so I wanted to ask if anyone else has noticed this issue. If not, could someone try to replicate? I am trying to decide if this is actual hardware problem or if Google changed the compass API or something.
tablador said:
I am having issues with my compass when using the GPS Essentials and Phone Tester app. Basically, these apps both think that the compass is always facing south or southwest. The compass in Google Maps is working though, so I wanted to ask if anyone else has noticed this issue. If not, could someone try to replicate? I am trying to decide if this is actual hardware problem or if Google changed the compass API or something.
Click to expand...
Click to collapse
Those apps are probably not compatible with Android 4.4.
I see you have a Nexus 5. Could you please try to replicate the issue, to confirm? Thanks.
tablador said:
I see you have a Nexus 5. Could you please try to replicate the issue, to confirm? Thanks.
Click to expand...
Click to collapse
Well, I don't really have a Nexus 5.
I'm here just to help.
I noticed my compass was wonky in Google Maps and GPS Status. In GPS Status there is an option under Tools to calibrate the compass, and it asks you to rotate the phone 1-2 times along each axis (so spin it in three different ways). After I did that, the compass started pointing in the right direction.
Bro I am on ARB 4.2.2 custom rom, GPS is not working after the univarsal gps fix also. Also the weather widgets weathers are not getting updated, is it realated to GPS problem?
Ya it happened to me too
praveengouda said:
Bro I am on ARB 4.2.2 custom rom, GPS is not working after the univarsal gps fix also. Also the weather widgets weathers are not getting updated, is it realated to GPS problem?
Click to expand...
Click to collapse
What I did was .. After the universal GPS fix I downloaded an app from Google play called GPS Status..
It works like a charm
Has anyone also Problems with the inbuilt Compass of the One? Lately I wanted to use Google Maps while walking and discovered the Compass is working within Google Maps. So i tried a few other Compass Apps, where some do work and others dont.
I did create a Issue on this, but it seems I'm the only one with this Issue so far: https://jira.cyanogenmod.org/browse/BACON-731
Im on stock CM11S, so it cant be any Mod / Custom Rom / Kernel Problems.
Greets
Daniel
Compass issue related to encryption
Hi,
I have the exact same problem. At first, I thought it might be a hardware defect, but that isn't the case.
Is you phone encrypted?
As bizarre as it sounds, it seems like the compass stops working as soon as the phone is encrypted. I did a factory reset - compass started working again. Encrypted phone again - compass no longer working.
Daniel, if your phone is encrypted as well, please update the jira ticket - it will help the developers reproduce / fix the issue.
Bye,
Till
Same problem here, but not encrypted
My Phone is encrypted NOW, but I really dont know if it was back when I encoutered that the Compass does not work with Google Maps.
I will try to Factory Reset if Ive got the Time and see if this does something to Google Maps. I wanted to try CM11 (without S) anyway.
Prior to encryption, my compass was just way off. Generally around 25 degrees counter clockwise. Now that the phone is encrypted, the compass doesn't work at all.
Anyone know if these issues are present on the "Vanilla" CM11 snapshot and/or nightly roms direct download from the CM site?
stewa2jm said:
Anyone know if these issues are present on the "Vanilla" CM11 snapshot and/or nightly roms direct download from the CM site?
Click to expand...
Click to collapse
According to the Jira Ticket, this also does not work on CM11 nightlys.
Compass was always broken even on Nexus 5. I was hoping it would be fixed in 1+1 and so many Google Maps updates and yet this is still an issue.
It doesnt even work on N5 when encryption is enabled? really?
cyablo said:
It doesnt even work on N5 when encryption is enabled? really?
Click to expand...
Click to collapse
havent used encryption, it just didnt work in maps
kolyan said:
havent used encryption, it just didnt work in maps
Click to expand...
Click to collapse
Thats weird. but I dont see the connection to the OPO then, Compass is fine when Phone is not encrypted.
My compass works but it's just way off lol
//edit
Actually I just tried it now since maps got updates recently and now it's kinda right and isn't off by much
Phone isn't encrypted
Sent from my A0001 using XDA Free mobile app
cm11 night 20150105 ,not encrypted.
Compass only worked in notification drawer widget,all other apps didn't work.
My compass was 90 degrees off in Google Maps earlier today. It was 180 degrees off a couple weeks ago too. What causes this?
Same problems here. Anyone an idea?
Compass works on my end but the orientation is off 90 degrees in CM11 I believe. It really throws off walking directions but driving seems ok
try this. download GPS Status & Toolbox @ playstore. calibrate the compass, like here https://www.youtube.com/watch?v=Rak2xhnk0qE
couldn't test it myself yet.
I'm rooted on Pie June update (PQ3B.190605.006) and suffering from infamous "CaptivePortalLogin keeps stopping" issue reported on Reddit ( can't post link due to policy, sorry).
As a temporary solution I use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
To do that in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I'm looking for ideas how to make CaptivePortalLogin to work on PQ3B.190605.006 version.
Tried to remove Magisk, reflash clean and replace CaptivePortalLogin in /system/apps with different APK provided here on XDA, sideloaded July PQ3B.190705.003 version, but nothing helped.
SOLUTION: Clean flash of July update PQ3B.190705.003 on both A/B and full factory reset.
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Thank you so much for workaround! It works.
For your question about March version, I don't have an answer if it worked out of the box, as I didn't try it.
It would be nice to fix CaptivePortalLogin, not sure how to attack it though.
While waiting on support to fix CaptivePortalLogin, I came up with a temporary solution, to avoid a brute force "Airplane mode" method. I decided to use CAPTIVE_PORTAL_MODE_IGNORE in Settings.java to prevent Android from detection of captive portals.
Solution:
in root shell on device run:
settings put global captive_portal_mode 0
The same could be accomplished over ADB.
After updating that setting I don't get notifications until opening page in browser, which redirects me to the login page of the Wi-Fi provider.
I hope someone can benefit from this solution until we get a real fix for CaptivePortalLogin.
I have disabled MAC address randomization in the advanced options of the WiFi network and it seems to solve the issue. Many captive portals use the MAC address to identify the device, so this would be a good explanation of the problem.
Thanks for suggestion. That option was off on my device by default and I didn't play with it. And in my case Captive Portal Login crashed on every network implementation from my corporate one to coffee shop.
R0BiN0705 said:
my workaround for this is basically turning on airplane mode -> turn on wifi and connect to network -> open browser and load a random page to be redirected to the captive portal.
Did it work with the march version? Looks like even stock phones seem to have a problem with it according to reddit. It worked just fine for me on june when it wasnt rooted..
Click to expand...
Click to collapse
This did not help
Still keep getting captiveportal crashed.
Any other suggestions?
Look at my original post or post #4 how to use CAPTIVE_PORTAL_MODE_IGNORE to disable Captive Portal login.
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
djjohnnyblaze said:
Wow! I am glad I am not the only one experiencing this issue!
I have the google pixel 3a with June security patch and rooted with Magisk via patched boot image.
Im wondering, is this due to Magisk or is this an actual issue with the June 2019 Factory Images/OTA?
Thanks!
Click to expand...
Click to collapse
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
pasha_d said:
I speculate it's a bug in June update, because it did crash for me with or without Magisk. But on another hand I would expect more activity on this thread if it is a widespread issue.
Click to expand...
Click to collapse
Looked at some threads on Reddit and it seems like even new devices are having this issue.
I don't think anyone knows what's causing it but this is a big deal. What scares me is one thread that said a replacement device works now with June security update. How could this be hardware though? Especially if it was working prior to June 2019 security update ...
The July security patch did not resolve this issue. How do we escalate this?
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
karimski75 said:
Issue had already been raised... No fix yet.
https://issuetracker.google.com/issues/135711621
Click to expand...
Click to collapse
Not sure where they're going to fix it though, maybe in Q only. I'm looking for a fix in Pie.
Here is the post from assigned developer from Google:
vi.. @google.com <vi.. @google.com> #83 Jul 9, 2019 02:26AM
Marked as fixed.
The issue has been fixed and it will become available in a future Android release. Please keep an eye on the release notes(https://developer.android.com/preview/release-notes)
It crashes for me too. Bummer!
Stock and non-rooted.
Pasha_d posted a solution that worked for me. You need to be rooted.
https://forum.xda-developers.com/pixel-3a/help/captiveportallogin-apk-t3940042
Pasha, did you ever find a copy of the March version of the captiveportallogin.apk?
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
I was able to turn off data. Load a web page and sign in over wifi.
pasha_d said:
No I didn't. The only ones I found on APK mirror were from February. Nobody replied to my original request here on XDA.
Click to expand...
Click to collapse
March apk
After updating to the latest June security update, I've noticed that Google Play Services is using much more battery then before the update.
It's not causing a battery drain, but uses more battery than I care for.
I've tried clearing the cache and automatic updates is turned off in the Play Store.
Anyone else experiencing this and know of a fix?
***OOPS! Just noticed that I've posted in the wrong thread. Hope that it'ok! ***
Yes I have the same problem. I don't have any solution yet
Had the problem but a factory reset did the trick for me. Might be worth a shot
Castro27 said:
Had the problem but a factory reset did the trick for me. Might be worth a shot
Click to expand...
Click to collapse
I also found out that there was problems with the location/compass. Just did a factory reset hoping it will help.
badadam said:
I also found out that there was problems with the location/compass. Just did a factory reset hoping it will help.
Click to expand...
Click to collapse
Are you on June security update? It was a known issue with release firmware that got fixed along with June security patch
Castro27 said:
Are you on June security update? It was a known issue with release firmware that got fixed along with June security patch
Click to expand...
Click to collapse
Yeah, it started after I updated from the April to June security patch.
Works now after a factory reset.
badadam said:
I also found out that there was problems with the location/compass. Just did a factory reset hoping it will help.
Click to expand...
Click to collapse
Hey mate. Any updates on the battery drain issue? I've noticed the heavy drain by google play services once again on my end
Castro27 said:
Hey mate. Any updates on the battery drain issue? I've noticed the heavy drain by google play services once again on my end
Click to expand...
Click to collapse
After factory resetting the device, I went into settings >account> and made sure that the apps I don´t have don´t get syncronized (Google Fit & Google Play Games) there has been no problems with Google Play services drain. All back to normal again.
I with the same problem, even resetting the consumption is triggered again. After the restoration I deleted data from the application, it seems to have improved.
I uninstalled play service update and disable location and now seems it works OK
you can try disabling automatic updates in the play store