Database Develop

GPS Status 2 for Adnroid 1.5

Hello all,
As developers start to use firmware 1.5 I have updated the GPS status app to work with the new firmware.
The good news is that I no longer have to use internal APIs. Some features have been removed or changed:
- Screen orientation settig has been removed as it can be configured globally in 1.5
- Magnetic declination setting is removed too, but the good news is that declination is now automatically calculated (without internet access) based on a geomagnetic model. The model also gives the absolute value of the magnetc field at your location which is also displayed.
- finally: the GPS is not automatically turned on, because average programs can no longer turn on the GPS (it is possible only by using the system settings program) (GPS switch appliction will no longer work)
Have fun, comments are welcome.
Rudolf

If you start the app without enabling GPS first, it crashes right away.

Karolis said:
If you start the app without enabling GPS first, it crashes right away.
Click to expand...
Click to collapse
Thanks, noted the issue.

Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...

i hope this works because GPStatus is my favorite app.

g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.

without moving, my heading goes frim 78-81deg.

joeydsmith said:
g force registers at 1.00 as default... it doesnt seem to be as accurate as gps status was on 1.1, or its more sensitive i dunno.
Click to expand...
Click to collapse
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Having acceleration at 1.0 g is correct (at least GPS Stus 1.5 works the same way) as we are standing on the surface of the earth Thats a different stiry whether it is correct to call it "acceleration" for ordinary people (I know Einstein would not mind it )

lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.

joeydsmith said:
lol yeah cant u jsut make it x-1? or sumthing lol, but yeah you are right we exipreince 1 g all the time.
Click to expand...
Click to collapse
Version 1.4 did that, but that was not correct.
The problem is that acceleration is a vector not a scalar. I.e. I have to add/substract vectors not scalars...
example:
- If you would accelerate horizontally with 1g and in addition the earth has also 1g gravity, you would feel (and your phone would measure) approximately 1.41g (sqrt(1g^2+1g^2))
- on the other hand if you would accelerate vertically (upwards) with 1g, your body would feel 2g
The real problem: it is not possible to measure the direction of your acceleration (and according to Einstein its not even distinguishable from the gravity at all).
Maybe I will assume that the acceleration is horizontal (which is true for most ordinary people, moving on the surface of Earth). The rest (astronauts during launch, parachute jumpers) will get slightly wrong results, but I'm hoping they will have better equipment than relying on their G1

Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
meanwhile i thanks so much your work and hope gpsstaus.apk go to work in the future at least good that we have working in the past...
best regards and electronics greetings from spain

I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...

rhornig said:
Right, I've detected this too. It seems that the new formware is doing much less filtering than the 1.1 version. This gives a faster response with much more errors. Unfortunately I cannot do anything about it at the moment.
Click to expand...
Click to collapse
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...

unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
Click to expand...
Click to collapse
That sounds like the compass is being influnced by a magnetic field, try waving the phone in a figure 8 to get it to reset itself.

koxx said:
Crash on 5.0.1Gr3.
I switch GPS ON before launching.
It shows the first screen, and "force close" ...
Click to expand...
Click to collapse
Thanks. Fixed (hopefully) and updated the first post.

delta_foxtrot2 said:
I noticed a small problem with the magnetic declination, the mag declination here is - 6° 39' west according to ngdc.noaa.gov, anyway when the compass moves slightly west from north it shows -1 to -6 then jumps to 350...
Click to expand...
Click to collapse
Yepp. Thats a bug. Thanks for finding I will fix it for the next release.

unicornio said:
Rudolf i am a fan of your gpsstatus.apk and since i load the 1.5 in my dev phone i wanting for your upgrade. really i do not understand what happens with this firmware but i think that the compass do not work anyway and all operations that in the past (and that work in my g1-not updated- phone) put to work the compass now is not responding...i have my compass pointing near the east!!!...
may be (that you says) is the automatic magnetic declination are actuating but the pointing i shure that is a mistake...
i am very fustrated and worried if this issue and if you can help me to understand this, it would be very appreciated...
Click to expand...
Click to collapse
After firmware upgrades or if you experience strong magnetic field the internal compass must be recalibrated. Check the heading reading in the upper left corner. If it contains ?, ?? or ??? after the number, then your compass is inaccurate and must be recalibrated.
As alsready mentioned, you should draw big 8s in the air with your phone for about a minute. If everything goes well, the ? marks should go away and your compass should be much more accurate.

rhornig said:
Thanks. Fixed (hopefully) and updated the first post.
Click to expand...
Click to collapse
It works now ! thank you !!!

delta_foxtrot2 said:
Running average of the last 5 results would smooth it out, but yea less responsive, if you hooked it into the accelerometer to notice a suden change to reset the smoothing should take care of responsiveness...
Click to expand...
Click to collapse
Thanks. Good idea, however the android framework itself should do the filtering (i'm already using the slowest possible update frequency which means the highest filtering). I will wait until the final 1.5 firmware comes out, and then revisit the issue.

Yay. It works. The compass does look a little faster

Compass issues

I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Sent from my Nexus 6 using Tapatalk

Same issue here
I have the same issue with my Nexus 6 64Gb blue, bought in Germany from Amazon.de.
Calibration helps but it decalibrates soon, and then the compass is off by 90° or 180°.

DontHaveACLue said:
I picked up the nexus 6 from AT&T a couple days ago and love it but I have one issue. The compass is off by 90 to 180 degrees. If I spin it around enough it usually calibrated itself but only lasts until the next time I start maps.
I've seen a couple of comments indicating similar issues but I'm not sure if it is a hardware issue and should be replaced.
Does the compass work correctly for everyone else?
Click to expand...
Click to collapse
That would NOT be a hardware issue. That is entirely software.

doitright said:
That would NOT be a hardware issue. That is entirely software.
Click to expand...
Click to collapse
Why are you so sure it's a software issue if the sensor loses calibration no matter what?

max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
heres one way to calibrate a compass in android.. https://www.youtube.com/watch?v=AzQSsUsOWJc

simms22 said:
heres one way to calibrate a compass in android..
Click to expand...
Click to collapse
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!

ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
If you own a Nexus 6 as well, and do NOT have this issue, please let us know where you bought the device and which exact model it was (white or blue? memory size?)
Thank you very much in advance!
Click to expand...
Click to collapse
bought mine through tmobile. black(blue) 32gb version

max.shirshin said:
Why are you so sure it's a software issue if the sensor loses calibration no matter what?
Click to expand...
Click to collapse
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue. The data generated by the compass HARDWARE is not affected by calibration. The calibration adjustments are applied to values after they have been received from the hardware by the driver, and before being passed on to userland.
---------- Post added at 08:02 PM ---------- Previous post was at 07:50 PM ----------
ingdir said:
Exactly, except that in case of Nexus 6 the calibration only helps for about half an hour. It corrects the compass sensor and it starts behaving as it should, only to start showing random direction when you open Google Maps the next time. I've been testing it for several days, both inside and outside, in different places, running calibration several times a day. In no less than a couple of hours (usually even faster) it goes nuts again.
Click to expand...
Click to collapse
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration? The problem is that a compass reads magnetic fields. Nearly EVERYTHING generates magnetic fields, ABSOLUTELY EVERYTHING that uses electricity will generate magnetic fields. Everything with IRON in it will generate magnetic fields, typically in line with earth's magnetic field so it won't interfere (much), but if that thing with iron in it is MOVED, it will DEFINITELY interfere for quite a long time until it resets.
What the calibration does, is it tries to sort out all the competing magnetic fields in order to lock in to the true earth magnetic field. If you keep switching the compass on at different locations, then absolutely YES, it will spit out various incorrect values. In fact, if you go get yourself a regular old fashioned magnetic compass (with a needle on a pin in an oil bath) and you move it around, it WILL react to all the different things that produce a magnetic field.
Maybe try going into a forest, calibrating it, sitting around for a few hours (maybe a camp fire?), and then checking if it keeps its calibration.

doitright said:
Calibration *IS* a software function. You feed corrections into the compass driver to compensate for the magnetic fields generated by the phone itself. If it is losing calibration, it CAN ONLY be a software issue.
Are you totally certain that this is a function of losing calibration and not of needing a NEW calibration?
Click to expand...
Click to collapse
No, I'm not. Well, here are some possibilities to consider:
1. External magnetic fields affecting the phone in a way the compass goes nuts.
Before Nexus 6, I had Nexus 5 for 1 year and its compass worked perfectly in the same locations where Nexus 6 compass fails: same apartment, same office, same places around the city. Moreover, I don't even remember calibrating my Nexus 5, the compass just worked. Now I have Moto G as a temporary phone as I've sent my N6 back to Amazon, and Moto G compass works excellently as well -- again, no calibration required. So we have at least two devices with compasses working fine in the same environment.
2. Software bug that causes calibration data to be dropped.
I had the compass problem both on stock Lollipop and on CM. I also have a friend who did NOT have any compass issues while running exactly the same setup (first stock, then the same builds of CM) on the same Nexus 6 model. In Android, apps typically can't work with drivers on such a low level that could affect the calibration, and I don't run any special apps (except Google Maps) that do something with the compass. So it CAN be a software bug, but then it has to be very picky. Running a phone on pure CM without Google Maps for several days could be a good test as Maps is the only app that had something to do with a compass on my phone.
3. Some magnetic interference inside the device itself, or the sensor being too sensitive and/or having a hardware problem of its own.
This one seems the most likely to me, as it fits a pattern: the problem happens consistently on one device while never happening on other devices with identical configuration, several users have this problem (there are threads on reddit and other places, too) while the majority seems to be unaffected, and other devices with a compass work just fine in same locations.
Anyway, there obviously ARE devices around which can have a compass working just fine, and be it either a software or a hardware issue with Nexus 6, it's good if more people report a similar issue (or a lack thereof).

I have the same issue. I have calibrated from home and on the road in several states. I does not hold calibration.
I'm road warrior, and this is a real problem when traveling.
Sent from my Nexus 6 using XDA Free mobile app

Oneplus 3 cardboard vr issues [magnetometer]

Hey XDA,
Has anyone else been experiencing random "clicking" (input) in the Cardboard App and YouTube Cardboard Videos? Every 5 seconds or so my magnetometer will spike and cause clicking in these apps making them unusable, if you can please download this app and check your magnetometer readout as to confirm if this issue is just me or if it could be affecting more devices, screenshot attached below of the app and issue I mention.

I have the same problem with my vr, that is working fine with my old galaxy s4.
This is my test, it seems to be a little more accurate, but the issue remain!
Is there any way to turn off magnetometer and use simply a joystick?
Edit: I wrote an email to oneplus support team, next step is an hard reset
Edit2: I have tryed to disable magnetometer sensor, even so it continues to work buggy

Lucifer_90 said:
I have the same problem with my vr, that is working fine with my old galaxy s4.
This is my test, it seems to be a little more accurate, but the issue remain!
Is there any way to turn off magnetometer and use simply a joystick?
Edit: I wrote an email to oneplus support team, next step is an hard reset
Edit2: I have tryed to disable magnetometer sensor, even so it continues to work buggy
Click to expand...
Click to collapse
Thanks for the feedback, please report back if you go through with a hard reset and any follow up with the Oneplus team, hate this to become an RMA issue, I made a custom Cardboard profile that indicates I'm using a button and not the magnetometer sensor for input but it still picks up that as input too, so I'm guessing there's no way to disable that easily.

This is a well known issue and OnePlus claims they have it fixed and it should be in the next OTA. That being said....I don't trust them and already have my return label if they don't finally fix this crap this week.

tw1tch175 said:
This is a well known issue and OnePlus claims they have it fixed and it should be in the next OTA. That being said....I don't trust them and already have my return label if they don't finally fix this crap this week.
Click to expand...
Click to collapse
Thanks for your input, didn't know it was acknowledged and hopefully will be fixed in the 3.1.4, yeah I've had my share of issues with oneplus in the past too but I really like this device, I hope they fix this in the coming update or I'll be opening a ticket as well... No excuse for a faulty component...

Same issue here with my Bobo v4
Wysłane ze zmywarki

3.2.0 has solved the issue for my phone!

Lucifer_90 said:
3.2.0 has solved the issue for my phone!
Click to expand...
Click to collapse
tw1tch175 said:
This is a well known issue and OnePlus claims they have it fixed and it should be in the next OTA. That being said....I don't trust them and already have my return label if they don't finally fix this crap this week.
Click to expand...
Click to collapse
Can confirm for me too, 3.2.0 has solved this issue, if any mod reads this, the thread can be closed, thank you.

Thread closed as per above

Multitouch with +5 fingers

****UPDATE: *****
This is what happens https://imgflip.com/gif/1xvxm0
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?
****EO UPDATE ****
I have been testing with both
Settings -> Developer Options - > Show Pointers (and looking at the top left that says x/x points)
or
Using a multitouch test app like so https://play.google.com/store/apps/details?id=com.the511plus.MultiTouchTester
The latter is nice because it has big handlers and you can clearly see the point/touch flickering like loosing and creating point (hence creating a new point ID)
From what i can say in Marshmallow it worked way better, on the last 2 Nougat updates i saw that at the 7th point it started to do the flickering and with this one it starts at the 5th point.
With 3 fingers screenshot disabled (and all the gestures for that matter) as i know it would create a conflict.
Just tested in a Motorola with Marshmallow and it created the 10 points flawlessly.
I wonder if any of you noticed the same or is something off with my touchscreen?
Might it be a Nougat thing ?
Any known solutions?
I searched around and nothing Nougat related seem to pop up
Just tested with both OP2 and a Moto G5 and they both work great, actually it even worked great on my Samsung Galaxy i9000
I have noticed that for the last 2 updates or so multitouch capability has been decreasing.

When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.

JarJarWinks said:
When are you ever going to use ten fingers to multitask? If it wasn't for the screenshot gesture, we wouldn't even be using three.
Click to expand...
Click to collapse
That is irrelevant for what i am trying to figure out, what i want to know is if it is a HW problem by default or just my HW is faulty or even if it is a Nougat problem.
It works flawlessly on other less capable phones

Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.

pitrus- said:
Either software or hardware fault I would say. I just tried it out without any flickering with 10 fingers on my 3t running latest unofficial LineageOS 15/Oreo ROM.
Click to expand...
Click to collapse
Thank you, from what i get so far is a Nougat thing, all the users that have Oreo seems to work fine

Conductive electricity ?
Ok some pretty strange updates...
I accidentally tested it on a metal table and it worked perfectly, which lead me to think that it might be due to conductive energy or something.
So i tried the test on a wooden table and it does flicker and loose touches, so i pressed with a finger on a metal part of the OP3T casing and the points are registered properly.
I had made a video so people don't think i am crazy here is the result https://imgflip.com/gif/1xvxm0 at this point i can say that is directly related.
What can be the cause of this? Does this happen to any of you as well? Should i open the casing and see if there is anything touching the metal casing that should not ?

anyone ?

This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO

nagi_007pk said:
This is a non issue honestly. If it doesn't change how your phone functions in day to day practical use, you probably shouldn't bother with something like that. The touch display functionally is fantastic especially the screen colors and with the recently fixed touch latency it does happen to be one of the best screens on the market despite its lower resolution. Factually you won't use more than a three touch input so. IMHO
Click to expand...
Click to collapse
It is definitely a problem did you watched the video ? because it seems like a real hard problem to me, use cases for you might be different from others. My old samsung galaxy i9000 as well as my OP2 did not had that problem

It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?

thes3usa said:
It may be a problem for one and may not be a problem in another's eyes.
To address your issue, have you tried switching ROM's? I don't think it could be a Nougat problem, but you might as well try Oreo or even MM.
This may sound funny, but have you tried with another person's fingers?
Click to expand...
Click to collapse
I had the feeling that it might be from the updates (still using official OP updates) but right now i think it might be hardware. Yes i tried with other fingers, thinking about opening the phone to see if there is something touching the metal case inside.

Always on Display Issue

Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.

andrewd71 said:
Is anyone else having an issue with the always on display? Not a big deal but occasionally the AOD goes off and the tap to wake function doesn't work. Unlocking/locking the phone fixes it but it reoccurs again randomly through the day.
Click to expand...
Click to collapse
I was having the same issue when I had the edge notification app installed that makes the screen light up around the camera when you get a notification.
Uninstalled and no issues since

Tap to wake not working for me

Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?

andrewd71 said:
Not sure if this is connected but in addition to the always on display/tap to wake issue when I'm in a phone call the screen will stay off even when I move the phone from my ear to hang up, see the keypad etc. Again I have to use the power button to wake the screen. A problem with the proximity sensor perhaps?
Click to expand...
Click to collapse
Do you have any notification or edge lighting apps installed?

Mdizzle1 said:
Do you have any notification or edge lighting apps installed?
Click to expand...
Click to collapse
No, I've not installed any apps like that.

I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.

czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.

andrewd71 said:
This is an odd one - are you using a case? I just had a case through the post this morning and now using the phone with the case the issues have stopped! I'll keep checking through the day but as of now all is good.
Click to expand...
Click to collapse
Not using a case. It's sporadic. Tap to wake works fine for a while and then stops. The issue during calls is constant. Not major issues just niggles.

Not noticed any bugs with ambient display, but it has used 20 percent battery in 21hrs.
Seems a bit high to me, have just turned it off, not worth a 5th of my battery.

czm said:
I am having both the issue with always on display and the screen staying off during a call even when it's not up to my face. I don't have any edge display app installed. They happened right out of the box. Glad it's not just me.
Click to expand...
Click to collapse
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!

RockStar2005 said:
Yeah I'm having both issues happen RANDOMLY as well. I'm HOPING Google will put out a fix for these two issues very soon.
Tried working with Google's Tech Support Team via chat earlier on the AOD issue. Tried a few things like clearing the cache of the launcher & restarting in Safe Mode then back to Normal Mode, and it seems to be doing it less but then it just did it again for a short time like an hour ago.
Using a case, no edge stuff, and also using Nova Launcher (though it happened in Pixel Launcher as well).
If anyone finds a fix for this, I would appreciate it too!
Click to expand...
Click to collapse
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.

czm said:
Mine is fine for a while them randomly the tap-to-wake won't respond. I had also hoped that the OTA would have addressed, but maybe it is affecting far fewer users than other bugs.
Click to expand...
Click to collapse
Yeah. Seems like more and more people are noticing and like me reporting these various issues to Google. So hopefully the next batch will include fixes for all this stuff.

I have same two problem with AOD, touch to wake up and screen off/on when calling.

DOMIN_ said:
I have same two problem with AOD, touch to wake up and screen off/on when calling.
Click to expand...
Click to collapse
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.

RockStar2005 said:
I recommend you guys report these issues to Google so to increase the odds of them coming up with an OTA sooner than later. You can call them or chat with them via this link (as I did). Just scroll down to the bottom and choose your contact preference.
Click to expand...
Click to collapse
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.

I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.

czm said:
On the pixel support forum they also recommend you report it via settings>about phone>send feedback about device. I think this way it also easily picks up the log files.
Click to expand...
Click to collapse
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Morpherios said:
I believe the answer to all of your questions lies in a faulty proximity sensor. I was driving myself nuts with all of these issues exactly, and no app was the culprit because I factory reset and still had the issue. I'm going to post a link to a Reddit thread that I found that confirmed my suspicions. on Wednesday of this week I went back to Verizon and traded the phone in and now I have received a phone that works 100% as expected.
Reddit thread.
Good luck all, hope this helps.
Click to expand...
Click to collapse
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?

RockStar2005 said:
Yeah I got an e-mail from the support guy to do that as well after he'd ask that I send a bug report. Just did it regarding AOD not staying on all the time and also.............I noticed that Hold for Me doesn't ALWAYS come up when calling businesses. Two examples include T-Mobile Customer Service & a local major hospital in Chicago. In most cases though, it does. Just an FYI. Not sure if this is something that they will fix, but I think it should come up all the time, or AT LEAST when you're calling an established business of ANY kind.
---------- Post added at 05:30 PM ---------- Previous post was at 05:26 PM ----------
Very interesting!
I REALLY don't want to send mine back because I've spent so much time setting it up already (and my sister's too lol). I did some changes in the settings so I'll just cross my fingers and hope it works right.
Is there a way to recalibrate the proximity sensor?
Click to expand...
Click to collapse
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.

Morpherios said:
I don't believe it's a calibration issue. The way mine worked (or didn't as the case may be) was sporadic and seemed to almost be as if the sensor or module was loose? Inside the housing. Quite literally, jostling it around would make it work sometimes. Furthermore, if you download the app in that reddit thread, the proximity sensor tester Link Here, you can sort of gauge yourself if it's actually occurring. With mine, sometimes it would work by swiping my hand over the sensor, the color would change. Other times, the color stayed the same, and as the video showed ,I could put pressure on where the sensor was and change the color. But if it wasn't working, jostling the phone around would sometimes make it work and the color would change.
Additionally in the advanced test in that app, it is supposed to tell you how far away from the sensor an object is. On my (nonworking) phone, that number for distance would be pegged at 0 regardless of how far away my hand was. However if I put pressure on the sensor, it would jump to like 5 cm.
See if your phone is doing these things. If so, I would recommend you get it replaced, as it likely will not work properly otherwise. Verizon deemed this a hardware issue when I swapped phones. Also note that I factory reset twice, and one of those times I imported literally nothing when setting it up. So it wasn't a settings or app issue. I do believe there's a rash of faulty proximity sensors going on here.
Click to expand...
Click to collapse
Hey Morpherios,
Ok.............downloaded that app and tried it out several times. It passed some of the time, but then I'd try it again a few minutes later and it would fail on both tests. Ughh!!
You think even though it passed a few times I still need to replace it?