[Q] This Captivate has a gyro or not? - Captivate Q&A, Help & Troubleshooting

I've read that the Captivate/GalaxyS has a "six-axis" accelerometer but no gyroscope. Is this six-axis device sufficient to emulate the gyroscope? My application needs acceleration with reference to some point outside the phone (aka, TYPE_LINEAR_ACCELERATION). Is this possible on a Captivate?
My Cappy is running SlimICS 3.3 and lists six sensors:
1. SMB380 3-axis accelerometer
2. MS3C 3-axis Magnetic field Sensor
3. CM Hacked Orientation Censor from CM Team
4/5. GP2A Light/Proximity sensors
6. Rotation Vector Sensor 2 from CyanogenMod Project
#3 and #6 look like they might help, if they can tell me which direction is down. I don't mind having to calibrate from a stable position first. Are #3 and #6 hardware sensors or some emulated thing or some wrapper on the other three axes for #1?

Related

[Q] Can Galaxy sense the footprint of your finger? [= pressure enabled apps]

Can anyone test whether Galaxy S software / hardware wise can detect the area touched by your finger? If this is possible then pressure related applications would also be possible. Imagine invoking a right click just by tapping your finger in a different way (so as to cover a greater surface) - the music / drawing apps / or GPS scroll speed in such programs or other (e.g. the greater the "pressure" the quicker the scrolling).
Any ideas?
i highly doubt that this is possible and it is definitely not supported by the android api...
edit: i just looked into the api reference and saw that android does support pressure for touch events. i have no idea however if the galaxy s does support this. i think i will try it ...
edit2: sorry but i have to disappoint you, i always get the value 0.15686275 for the motion-event's pressure...but at least the galaxy s supports 5 finger multitouch while the htc devices can't even track 2 fingers right: http://www.youtube.com/watch?v=hVlsRCMltDg & http://www.youtube.com/watch?v=KRCDRXYJBCY
afaik this is only possible with resistive screens that report back the pressure, not with capacitive screens.
bommel0815 said:
afaik this is only possible with resistive screens that report back the pressure, not with capacitive screens.
Click to expand...
Click to collapse
nje, looks like it will be possible with capacitive screens as well soon: http://www.intomobile.com/2009/12/3...touchscreens-with-multi-touch-coming-in-2010/
edit: okay to be precise ... it will be possible on a capacitive touch enabled screen

[Q] REQUEST How to disable the proximity sensor Nexus One (Android 2.3.3)?

How to disable the proximity sensor? Sensor does not work after the break. Can not be replaced. Now I can not make and receive calls. Help please. (Nexus One - Cyanogen Mod 7.0.0-RC1 (or RC2))
_____________________________________
found one solution: http://forum.xda-developers.com/archive/index.php/t-764368.html
...in /system/lib/hw/sensors.mahimahi.so defines the device name of the proximity sensor, normally /dev/cm3602.
Hexedit the file to change the name of the device to something that doesn't exist, and you will no longer use the proximity sensor.

[Q] Compass with wrong orientation in Maps

Hi guys,
this is my problem/question: in Google Maps i have the orientation of the blu arrow (that indicates my position) that is the opposite of my real orientation. So i think: s**t ! Samsung has badly mounted my compass! .. So i have install GPS Status &Toolbox but here the orientation is correct! I have also calibrated all the sensors.. So what is the problem?
Thanks, Carlo. (sorry for my english)
while in google maps with the wrong orientation, have you tried moving the phone quickly in a figure of 8 motion in front of you?
that often seems to reset the orientation and fix compass issues for me

[DEVS ONLY] Kenzo hardware variations

I have never been more confused by hardware variants. So, for the benefit of myself and other developers working on this device, I would like to compile all the relevant information about hardware variants here. And also what is working/not working.
Please, no chit chat. Only post here if you know the answer to these questions.
Fingerprint Sensor:
fpc1020 (older devices) and Goodix (newer devices)
Does the Goodix sensor work on all versions of MIUI or only the more recent versions?
Does the /data/goodix folder only show up if you have the goodix sensor?
Touchscreen:
FocalTech (older devices) and Atmel (newer devices)
Are there FocalTech devices with the Goodix fingerprint sensor? Or do all Goodix devices have the Atmel screen?
What is the output of
Code:
cat /sys/class/input/input*/name
Panel:
Mine is BOE, are there other panels?
Front Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
Rear Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
If you have goodix folder on /data,you have a goodix fp
Goodix fp works on all miui versions..
Sorry for my bad English
I have a phone with goodix fingerprint.
Does the Goodix sensor work on all versions of MIUI or only the more recent versions?
Does the /data/goodix folder only show up if you have the goodix sensor?
Click to expand...
Click to collapse
It works on all MIUI Lollipop versions. Also it works on Miui MM (6.7.21; other versions was not tested by me) but sometimes.
It does not work on the official CM13 builds. Maybe it need fingerprintd patch to work. So we need source code.
Front Camera:
Are there different ones? and what versions of MIUI do they work on/not work on?
Click to expand...
Click to collapse
I think that there two revisions with different front camera hardware.
Both versions has driver in the CM13 kernel sources. All works on all miui versions.
BUT it does not work on custom MM roms because TheStrix did not add enough blobs from MiuiMM vendor folder
my panel is BOE too (no vibro on buttons in cm) but second version is TIANMA
I have goodix fp, atmel touchscreen and newest rear camera which one isnt working on custom roms. What a good chance How can I know which panel in my phone? And I want to know, is there any chance to all the these working together except miui? Sorry for my bad english.
mine tianma nt35596 panel fpc fp sensor
mine tianma nt35596 panel fpc fp sensor
There are 3 panels boe,sharp and tianma. I have tianma, also there are 2 different light sensors liteon and sensortek I have liteon.
Sent from my Redmi Note 3 using Tapatalk
theres 2 back camera (s5k3p3_omida and s5k3p3_fxxxx i forgot the numbers after f)
and 3 front cam (doesnt remember)
Fingerprint Sensor:
I have FPC1020 one. I guess most of kenzo's have it.
For CM, I use fingerprint HAL/libs from MIUI M builds for kenzo. We have updated FPC1020 kernel driver that works with M fingerprint HALs. (here)
Not sure about goodix, I never tried it. Maybe the kernel driver released by Xiaomi in their LP release may not go well with M Goodix fingerprint HAL/libs found in MIUI M builds for kenzo. (As LP HALs won't work on M)
Touchscreen:
I have Focaltech FT5X06 one.
Of what I know till now, I never saw a Goodix FP sensor being shipped with devices with Atmel touchscreen (I may be wrong here though)
Display Panels:
Xiaomi added device tree entries for 3 panels in their kernel release
tianma-nt35596
boe-nt35532
sharp-r63315
Mine has tianma-nt35596. And I have seen the devices having the other 2 panels. Also I never came across any RN3 other than these 3 panels so this is it most probably.
Front Camera:
Mine has "ov5670_omi5f06"
Would like to know what all camera sensors other than this Xiaomi ships.
I have a jira issue reported for CM13 by some guy claiming from camera do not work for him. Recently said he have a
Rear Camera:
Mine has "s5k3p3_omida01"
Again, would like to know what all camera sensors other than this Xiaomi ships.
I think, few have "s5k3p3_gt24c64" as well.
EDIT: For the eeprom{0,1,2,3,4,6} defined here,
"qcom,[email protected]" (rear) uses eeprom0 eeprom1 eeprom3 eeprom4
"qcom,[email protected]" (front) uses eeprom2 eeprom6
Now, about additional sensors mentioned here, are handled by this code committed by Xiaomi originally: https://github.com/TheStrix/android...mmit/a887d0c73d029c339a50dc8d16ce698c13eaa1ae
TheStrix said:
Rear Camera:
Mine has "s5k3p3_omida01"
Again, would like to know what all camera sensors other than this Xiaomi ships.
I think, few have "s5k3p3_gt24c64" as well.
Click to expand...
Click to collapse
Most devices have either Omida or s5k3p3_f16s01c
@TheStrix I have Atmel and goodix in my device. How can I know which panel and camera sensor is in my device? Sorry for my english.
Probably rare, but I have a Sharp r63315 panel
Indian version of Kenzo comes with Mostly Tianma nt35596 and Focaltech (FW) 0×20, Camera Rear Samsung S5k3p3_omida01, Front Omnivision ov5670_omif506 and Lightsensor is sensortek(I have replaced LCD panel and after that i got same tianma and Fpc so mostly in india they ship with Tianma,Fpc)
Goodix FP related files displayed in "/sys/class" folder on my device.
mine has
TP Version: FocalTech FT5346
LCD Tianma nt35596
Camera s5k3p3_omida01, ov5670_omi5f06
FPC Fingerprint
Sensortek proximity sensor
(bought from china)
btw I just bought mine recently and on the box it says 2016.7 so I don't think older / newer decides the hardware in the phone, probably factory's or maybe just the availability of parts.
I have two Redmi Note 3:
Dark Gray 32GB (Aug/2016):
Fingerprint Sensor:
Not unlocked bootloader so cannot conclusively tell one, but can take photos by fingerprint. Also have "uninput-fpc" in /sys/class/input/input11/name, and "[email protected]_fpc1020.108" in /sys/class/input/input11/name.
So I guess it is FPC one.
Touchscreen:
Focaltech FT5346
Display Panels:
tianma-nt35596.
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Gold 32GB (July/2016):
Fingerprint Sensor:
Same as the above.
Touchscreen:
ATMEL
Display Panels:
boe-nt35532
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
i have s5k5e8_yx13:0 front camera sensor
Cod3AlchemisT said:
I have two Redmi Note 3:
Dark Gray 32GB (Aug/2016):
Fingerprint Sensor:
Not unlocked bootloader so cannot conclusively tell one, but can take photos by fingerprint. Also have "uninput-fpc" in /sys/class/input/input11/name, and "[email protected]_fpc1020.108" in /sys/class/input/input11/name.
So I guess it is FPC one.
Touchscreen:
Focaltech FT5346
Display Panels:
tianma-nt35596.
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Gold 32GB (July/2016):
Fingerprint Sensor:
Same as the above.
Touchscreen:
ATMEL
Display Panels:
boe-nt35532
Back Camera:
s5k3p3_omida01
Front Camera:
ov5670_omi5f06
Click to expand...
Click to collapse
The color doesn't matter
I have a jira issue reported for CM13 by some guy claiming from camera do not work for him. Recently said he have a
Click to expand...
Click to collapse
Yeah, that's me
---------- Post added at 10:06 PM ---------- Previous post was at 10:02 PM ----------
FP : fpc102x( probably 1020 ) worked on all ROMs that have been tested ( miui+cm )
Panel : BOE
Touchscreen : Atmel dt2w kernel doesnt work
Front camera : S5K5E8 works only on the miui based ROMs ( including xiaomi.eu ones )
Back camera : S5K3P3 worked on all ROMs that have been tested ( miui+cm ). The flash is bugged, capturing images with flash is really weird, the exposure is incorrectly set and the picture gets whitish and unrealistic colors, when i turn off the flashlight it has a weird double flickering instead of just turning off, really weird and uncommon on the mediatek version. ( i had the mtk in the past )
Im really looking forward for fixes related to the front camera, its really painful it does not work with official cm 13 ROM
---------- Post added at 10:10 PM ---------- Previous post was at 10:06 PM ----------
Light sensor : stk3x1x ( seems to be the same as proximity one, im getting all the information from Aida64
Kate Hardware
@flar2 would it also be possible to officially support the Redmi Note 3 Special Edition?
This version is originally meant for the Taiwanese market, but it features all the necessary LTE Frequencies to work in Europe. The Pro version lacks LTE here in Germany (one important band not supported).
The special edition will boot CM13 with it's kernel, it will just force close in the fingerprint settings. This apparently can be fixed by flashing the Kenzo firmware (without radio).
I will get my Special Edition early next week and will be posting the hardware details in this thread.

Problem with OIS

On the LineageOS 14.1 or AospExtended ROM V4.2 firmware, the stabilizer does not work in 4 directions, but only in 2. I understood this because of the activated 2 api. If you disable it, then patch calibration will help https://github.com/dobragab/Mi5Calibrate
However, then the front camera will be upside down! I do not know how to solve this problem. I found a possible solution on the Internet, but it does not work!
Code:
Enable it yourself from the build.prop, set persist.camera.HAL3.enabled to 1. Note that front camera will be vertically flipped after this, so modify /system/etc/camera/msm8996_camera.xml as well. Change MountAngle for CameraId 2 (there are two of them, change both) from 360 to 270.
Https://www.tapatalk.com/topic/73822/35626
How do I calibrate the camera? Who does it work in 4 directions at all?

Categories

Resources