Does MI3 have Temperature Sensor?
I can see it under CPU-Z sensors list but none of the apps from play store can detect it or measure temperature.
Also what about Pedometer Sensor?
mchauhan said:
Does MI3 have Temperature Sensor?
I can see it under CPU-Z sensors list but none of the apps from play store can detect it or measure temperature.
Also what about Pedometer Sensor?
Click to expand...
Click to collapse
Tried and not working, I think it's ROM issue becasue some folks says that It was working before kitkat update
I have tried it on MIUI 7 stable and it reads temperature correctly.
Mighty_Pak said:
I have tried it on MIUI 7 stable and it reads temperature correctly.
Click to expand...
Click to collapse
Which app are you using?
Related
Hey guys. I have looked around and can find no info on some of the tabs sensors. From what i understand the chipset is straight out of the galaxy s phones, which is the reason i see the existence of a proximity sensor but dont see any data from it.
Anyone have a clue whether it actually exists?
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
triplex76 said:
chipset and sensors are different things....even if the chipset supports a certain type of sensor doesn't mean it should be there if there is no need to be there.
galaxy tab doesn't need a proxy sensor cause you are not going to put it beside your face when calling...
Click to expand...
Click to collapse
Doesn't need and doesn't have are different things. Point is, if it was stated that the tab has a proximity sensor, where is it?
I'm pretty sure it has one, in the unofficial CM build Technomancer says he fakes i at 10CM
There is no proximity sensor in Galaxy Tab.
My CM7 sensors driver pretends there is one and reports 10CM distance so the Phone app behaves better.
Thanks mate, that's what you said in the last thread back in October, but why do all the sensor pingers see it? Are they checking code rather than hardware?
Also, is there a working, sensitive light meter anywhere for the tabs ambient light sensor? The couple I've tried refuse to work...
There is working light sensor in the Tab. Both my CM7 and Samsung ROMs support it just fine. It has range from 0 to 6000 Lux snapped to one of several levels in the kernel driver. You can actually read it from sys interface.
The proximity sensor in my CM7 sensors driver is just software reporting constant 10cm to the system. The sensors test apps in my CM7 (I uses Sensor Test and Plot http://www.appbrain.com/app/sensor-test-and-plot/com.golborne.android.SensorTest) just reports 10cm from my fake sensor.
I think there is some leftover code in Samsungs sensors driver that may report presence of proximity sensor.
Yep, i use it as well, but my issue is with the three avaliable states the driver seems to report.
I get 5, 22 and 75. Are there only three levels then? And no way to modify them outside the kernel?
I can get up to 6000lux using strong LED flashlight directly on the sensor.
There is another sys device that can read unprocessed data that has values not snapped to 5,22,75 etc... but Samsung's driver uses the snapped device (and so is mine).
This is very annoying... im trying to make an app that needs a proximity sensor to work as intended so the light sensor as well as the sleep mode implementation are really no substitute.
In any case, im sure it will be quite usefull for all tablet owners running 2.2 and up and using a case. I will have a closed beta for xda members by the end of the day, so people can test it over the weekend.
Would you like a shot, mancer?
I don't know what would you do but if I understand why not to use the g-sensor ... just like in samsung omnia...put backwards enable silent courtesy mode.
the proximity sensor will be useful if you use the leather case to close the screen when touches the screen , like ipad 2 and galaxy tab 10.1 V they have proximity sensors , but i noticed that the sensor exists using sensor applications they see it exists but not giving readings
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
ftgg99 said:
Hi - there is no sensor, the sensor list showing it is just a glitch from the galaxy s motherboards. And the functionality youre describing is already available in my app Killswitch - you can get both the lite and full version from my signature...
Click to expand...
Click to collapse
Thanks I already bought it from market and it's great
Sent from my GT-P1000 using XDA App
Great! Im working on an update that will help improve the accuracy of the light sensor functions... been getting some flack for not updating it
Watch this space!
On my Xperia T running stock, rooted .141 any time I install an app such as Lux or Velis, they detect the light sensor (and CPU-Z does too) but after a very short time neither brightness app nor CPU-Z can detect it, and Sony's 'adapt to brightness conditions doesn't work properly. Uninstalling the app and rebooting makes the light sensor work again.
Can anyone else confirm that this is the case on their device also?
reshonda said:
On my Xperia T running stock, rooted .141 any time I install an app such as Lux or Velis, they detect the light sensor (and CPU-Z does too) but after a very short time neither brightness app nor CPU-Z can detect it, and Sony's 'adapt to brightness conditions doesn't work properly. Uninstalling the app and rebooting makes the light sensor work again.
Click to expand...
Click to collapse
I am facing the same issue with V. Rebooting makes lightsensor work again.
Any solution available?
Very common issue on our devices : http://forum.xda-developers.com/showthread.php?t=2453223
Mine does not work anymore at all... Perhaps it will wake up one day...
Hi all,
i am just about to buy a Moto G 2014.
But i have a question regarding the sensors.
Is there a true magnetic compass or the like?
I mean a sensor that shows up magetic north without using GPS data.
I checked the spec sheet but they tell about a digital compass and/or gps compass. The spec sheets differ...
Which makes me wonder if there is a sensor for orientation.
So i would be very glad if someone who owns the device could do a sensor test.
The app GPS STATUS or SENSOR BOX for Android tells the truth.
Turn GPS to off.
If there is a magnetic sensor GPS STATUS immediately shows the compass rose turning northward and the value of the magnetic field.
If there is no such sensor it tells that this function is disabled.
SENSOR BOX nearly the same ..
Thank you in advance and enjoy your device.
There is compass / magnetic sensor
bhavin192 said:
There is compass / magnetic sensor
Click to expand...
Click to collapse
NICE!
bhavin192 said:
There is compass / magnetic sensor
Click to expand...
Click to collapse
Bhavin,
Can you tell me this screenshot is from which app?
Thanks,
Gaurav
MotoG_-_Gaurav said:
Bhavin,
Can you tell me this screenshot is from which app?
Thanks,
Gaurav
Click to expand...
Click to collapse
It's GPS Status & Toolbox
Why the physical buttons of my Mi5 basic does not work on AOSP roms?
What panel type is your phone? Check using apps like CPU-Z. If your panel type is LGD, that will be the issue. Xiaomi hasn't released the updated kernel files needed for Mi5 with that panel, hence touch sensitivity for Mi5 with LGD panels on custom ROMs is wonky. There is nothing the custom ROM developers can do about it and I doubt the issue can be solved until Xiaomi releases the updated files needed!
You are correct, it's an LGD issue, but AFAIK, the problem has been fixed in the latest builds of the official Lineage 14.1.
21.03 Is the problem still in LOS version?
murdem said:
21.03 Is the problem still in LOS version?
Click to expand...
Click to collapse
In my case yes it is.
CPU core offline or n/a in lineage 14.1
Hey can someone help me find out why my phone is being so sluggish?
'3c system tuner' app shows cpu2 is always offline and cpu3 is sometimes 'n/a' and other times it's matching what cpu0 and 1 are doing which is usually idling at 1.03Ghz.
Are the CPU cores shutting down on purpose or is something maybe wrong with my phone?
Semore666 said:
Hey can someone help me find out why my phone is being so sluggish?
'3c system tuner' app shows cpu2 is always offline and cpu3 is sometimes 'n/a' and other times it's matching what cpu0 and 1 are doing which is usually idling at 1.03Ghz.
Are the CPU cores shutting down on purpose or is something maybe wrong with my phone?
Click to expand...
Click to collapse
try DevCheck app from Play Store and validate for sure that some of your core are off. 3c system tuner is a bit outdated for our SOC and may not read and differentiate correctly the two clusters.
georgekav33 said:
try DevCheck app from Play Store and validate for sure that some of your core are off. 3c system tuner is a bit outdated for our SOC and may not read and differentiate correctly the two clusters.
Click to expand...
Click to collapse
Thanks heaps for that, I wanted to check if it could have been something I had installed or some bug with the lineage version so I updated lineage, no avail, then formatted and it worked. 3c system app was showing all 4 cores firing.
Also downloaded devcheck and seems all good. I am really curious as to what caused the issue now...
Lineage os
i have problem on my mobile mi5 with tempered glass and i have problem with buttons only on lineage os now its fixed or no?I have now miui.
Sparkly15 said:
i have problem on my mobile mi5 with tempered glass and i have problem with buttons only on lineage os now its fixed or no?I have now miui.
Click to expand...
Click to collapse
Thats propably due to your LCD panel. Which one do you have?
I think this happened at around the time that I installed the latest update. I checked the sensors through the *#0*# menu and found that my gyroscope's value isn't moving and my magnetic sensor is spinning. I calibrated the magnetic sensor using Google Maps and also the Edge screen, but still it happens. I tried playing a racing game which relies on my gyroscope to steer and to my surprise, it works fine. I also tried to test my magnetic senor by downloading a compass app, and it properly displays my current bearing. I'm also not entirely sure but my accelerometer data aren't properly telling that it's on a flat surface although it actually is.
Is anyone also having this issue?
I did just remember that when I downloaded the update, I had an intermittent connection, would a part of the update be corrupted so that the drivers for the gyro and compass be mismatched?
I also have a youtube video showing what my screen displays when I do a sensor test.