This app was mentioned in 19 comments, with an average of 1.47 upvotes
Sounds like you proximity sensor isn't working.
Download Androsensor to see what the sensor is seeing. https://play.google.com/store/apps/details?id=com.fivasim.androsensor&hl=en
Scroll down to proximity sensor and see the phone reading. If you're in a little room you reading should be 2.0 or above. Having a number there means the sensor is working and you have a software bug. If it reads 0 then your sensor isn't getting light and the phone will trigger the screen to go dark during calls because it thinks it is to your ear. This means something is blocking sensor. For me, it was a scratch on my screen protector over the sensor (the oval under the ear speaker).
Take a look at AndroSensor, it outputs a ton of data. I don't know anything about Pokemon, so if it doesn't work for you, at least I tried.
If you install for example AndroSensor, you can check the proximity sensor, but it usually has only two states.
Install a sensor app and test your proximity and brightness sensors.
Here's a random one I can't vouch for but found in another thread.
It might be a sensor. Similar thing happened to me on my pixel. Turned out the screen protector was just slightly covering the light sensor. I don't know where that sensor is on the op7pro but here is a piece of software that I can tell you what the phone is doing, https://play.google.com/store/apps/details?id=com.fivasim.androsensor Think it's the light sensor, but might be different in this phone.
I'm seeing the same thing (using both AndroSensor and Sensors Multitool): no magnetic field or orientation readings. All other sensors appear to be fine.
I would also like to know whether or not my phone is defective.
Would any of you be able to check your sensor readings and share it? I use AndroSensor https://play.google.com/store/apps/details?id=com.fivasim.androsensor
I've been using this app since I had the original Moto Droid. Never failed and it's outdated 4 yrs. I'm really curious if anyone else has same sensors that failed. Test proximity and light sensor by covering top edge above the display.
Well, I noticed the issue because when I receive or initiate a call, my phone screen turns off like it's pressed against my head and I can't get the screen to come back on unless the call terminates. But I belive I confirmed my assumption with the app below. Right when I launch the app the proximity sensor says 2 inches, then immediately goes to 0 and won't change again.
https://play.google.com/store/apps/details?id=com.fivasim.androsensor
Anything that uses the onboard sensors like Androsensor: https://play.google.com/store/apps/details?id=com.fivasim.androsensor&hl=en . That app can enable you to do labs involving mechanics, optics, electromagnetism, and sound.
You can also use Android phones to detect cosmic-rays with the camera: https://wipac.wisc.edu/deco/home
Sorry about that. After making the signature spoofing and following the steps to install microG, I've installed the MozillaNlpBackend and I enabled it but whenever I tried any service/app/site (like Google Maps or OpenStreetMap) to retrieve my location it kept loading forever or until it stopped searching and prompted me with some toast saying it couldn't connect or retrieve location.
Also, using Androsensor I've found out that my GPS doesn't work on CM. It shows Satellites in range: 0(0), when in Stock ROM showed 2(0) satellites (I guess that was because I was in a building with poor reception).
> What do you think is a good way to "prove" this?
Put the phone through real-world scenarios, then log sensor readings. Here is an app to log the readings:
https://play.google.com/store/apps/details?id=com.fivasim.androsensor&hl=en
This is a real concern and not something you should take lightly. My phone gets quite warm sitting on my desktop Qi charger at comfortable room temperature. And now imagine that the phone is resting in a car in direct sunlight while on a road trip using GPS (which by itself makes the phone hot), or in a purse or pocket on a hot day outdoors.
You need to really run this device through the paces before selling them.
I don't know how accurate this app is but you can use your phone to measure the decibels.
https://play.google.com/store/apps/details?id=com.fivasim.androsensor&hl=en
> From the dashboard.
Right. We're talking about very different things. What you are seeing on the dashboard is interpreted data.
What constitutes 10 steps?
What constitutes 1 flight of stairs?
What constitutes 1 mile?
What constitutes asleep/restless/awake?
Those things are interpretations of what the sensors in the device actually record.
When I say "data," I'm referring to the sensor data from the device. When you say "data," you're talking about fitbit's charts. If those work for you, then that's great.
> If you are talking about paying for the right to download your data and move it to another source, I am already way ahead of you.
Yup. Streets ahead.
I have no interest in "moving it to another source," I need a way to perform my own data analysis, as their charts don't contain what I need to know. Specifically, I need to correlate motion, pulse, and environmental data during sleep. Even with access to what fitbit calls the "intraday" data,
I didn't buy into their program, it was handed to me. That's irrelevant, however.
> Terms of Agreement and educate yourself before you invest yourself into something you can't bail out of.
Yeah, thanks. "Bailing out" is not the issue, accurate data in order to make specific determinations is. The Charge HR heart rate reporting is inaccurate, no matter how it's worn. (That's easily demonstrable with a stopwatch. Try it yourself. I'll do it now: Actual BPM: 68. Per Charge HR: 78.) Fitbit has admitted as much when one of their exec's stated that the HR numbers were only useful as averages over long periods of time.
Many users report absurd numbers for step count, stairs climbed, and distance walked. This is probably largely due to the fact that the figures are analytical interpretations, and the methods used to derive them. If you drive on a bouncy road, for instance, you're going to rack up a lot of steps.
If you have access to an Android device, the free app Androsensor will give you a sense of what sensor data looks like.
The Fitbit is perfect for some users. You are one of them. Enjoy.
do you just want the sensor data , or with camera too ?
androsensor records all the sensors to a csv file
https://play.google.com/store/apps/details?id=com.fivasim.androsensor&hl=en_US
E. G. https://play.google.com/store/apps/details?id=com.fivasim.androsensor
There's a proximity reading. It's a binary one, meaning it's zero or max.
I had a bad proximity sensor on my 2XL when I first got it. Used this app to make that determination.
https://play.google.com/store/apps/details?id=com.fivasim.androsensor
Download this app and see what's being reported by the sensors.
Now since Apple doesn't expose numbers we have to look at reviews and assume (yes it is a big assumption) that downloads and ratings are closely correlated.
Filmr: 630
LapseIt: 1419
iMovie: 9077
Videoshop: 2934
Androsensor: 7301
Some massively unknown random app on Android has nearly the same amount of reviews as the most popular video editor you listed and more than the other 3 combined.
https://play.google.com/store/apps/details?id=com.fivasim.androsensor
So yeah... the notion that it is in anyway mainstream to edit videos on the iPhone is just silly.