I noticed that with every new Android version for the defy+, we "lose" some of the sensors.
Or do they just get not detected by the apps or even are software implementations that take information from the hardware sensors? Look at the file at the URL below:
https://docs.google.com/document/d/1pi_e5T_CvSRw84RF0DfFBdx-m-IHrPZdJ81PCfAf0bE/edit
Example:
ICS compared to GB: missing gravity sensor, linear acceleration sensor - since the vendor is Google Inc, I assume are these just software implementations?
JB compared to ICS: missing rotation vector sensor (not counting the microphone one since that's not implemented yet)
Questions go in the Q&A section
pepcisko said:
I noticed that with every new Android version for the defy+, we "lose" some of the sensors.
Or do they just get not detected by the apps or even are software implementations that take information from the hardware sensors?
Click to expand...
Click to collapse
I'm noticing this too. Sensor List is telling me that I have Acceleration, Magnetic, Orientation & light. I was expecting to see more in here. Anyuone got any ideas as to what is going on?
http://forum.xda-developers.com/showpost.php?p=32501910&postcount=5643
Related
I apologize if this isn't the correct place to post this, it seemed the most logical group.
I am coming up against some unique issues on a Nexus S. I don't have any mods on this device, it is stock Android 2.3.1 running 2.6.35.7-g7f1638a android-build (at symbol)apa28 #1.
There appears to be a bug on this device which results in the LED torch being disabled when the autofocus callback is called. To reproduce the issue simply:
Set the flash mode to Camera.Parameters.FLASH_MODE_TORCH
Set the focus mode to Camera.Parameters.FOCUS_MODE_AUTO
Start autofocus
This behavior is unique to this device, although I can only admit to having tested on 7 other Android devices. DroidX suffers from a similar bug but rather than the LED turning off, it blinks.
Inspection of the camera parameters inside the callback shows that flash-mode=torch so it is not an issue of the camera parameters being overwritten.
Has anyone seen this issue that might know how to work around it without modifying the device? My attempts at contacting and submitting bug reports to Samsung has failed miserably. It would be appropriate to make the remark that "Samsung is where bug reports go to die".
My primary concern is that the torch feature behaves so differently on every device, yet all of these devices claim to support Camera.Parameters.FLASH_MODE_TORCH. I'm really hoping to find a generic way to work around this issue since I believe there will be a lot more variation in camera driver implementations in the future.
Regards
Are you saying your camera isn't working because mine isn't working it keeps force closing
Sent from my Nexus S using XDA App
Wouldn't you rather submit the bug to Google via their bug tracking forum? I think Samsung is out of the picture.
Hi all,
I apoligise in advance if this has been posted before but it's 4:30am and I don't have anymore time to search for this problem.
I've noticed ever since I've updated my phone to Darky's ROM (starting in dec 2010 with v8) my proximity sensor hasn't been turning my screen off during calls. I'm not sure if this is rom related or not but I ran some tests tonight (using SGS tools and sensor test/z-devicetest) and in all those apps my sensor doesn't seem to respond.
Does this mean it's broken?? Or am i missing some drivers or something??
I'm currently running DarkyROM v10.1.
TIA
Edit: found out that it is indeed working, however only when a bright light shines onto the sensors. Is this normal??
I've had my 1st gen Nexus 7 for almost a year, got it in December as a Christmas present to myself and I've had a few problems ranging from the screen not rotating, to aiming issues in fps games and some random reboots, all of these problems usually fixed themselves or I fixed them through tips and guides online.
However this time I'm a little confused; My Nexus 7 last week had a minor issue regarding screen rotation for a day or two in which it seemed to have stuck either in portrait or landscape and it fixed it's self, although since then I still check by rotating my screen on it's 4 ends to check if it does this correctly because I'm paranoid like that.
Now my current issue is with the gyroscope I believe, in games that have the option to use it, I do like in Modern Combat 4, it makes it easier to aim than using the touch screen to manually aim and fire, before I was able to move the camera in every possible direction to aim my weapon and had no issue, although this time my problem is just that.
I try to aim and it lets me for a moment and then it wants to center it's self and then it's really difficult to move my tablet around to aim at all, although moving it really quickly in another direction fixes it, then I try to aim again and it gives me trouble moving the camera.
Not really sure what to do now as I've tried to do my usual things to fix it, and there are two ways I check to see if it's a major problem, I check Modern Combat 4 and see how the aiming is with the gyroscope enabled, and The Sims Freeplay, the reason I mention the Sims is because earlier this year when I was having gyroscope issues my sims would react as if I was flipping the screen from one landscape to the other and would constantly do this.
Also during this time my screen wouldn't rotate but after a week or two the issue somehow fixed it's self and it was fine until now, although the issue is just aiming in FPS games and my sims react just fine now as I can freely rotate my screen without a problem.
Nobody?
JohnathanKatz said:
Nobody?
Click to expand...
Click to collapse
I direct you to the Google forum on the Nexus 7 Sensor (aka Gyroscope) problem.
Since I am brandy new on this forum, I can't actually post the URL here:
productforums.google.com/forum/#!topic/nexus/GgnRFsw3o-Q%5B176-200-false%5D
There look to be about four or five different problems with sensors including the orientation/gyroscope sensor.
redgatormds said:
I direct you to the Google forum on the Nexus 7 Sensor (aka Gyroscope) problem.
Since I am brandy new on this forum, I can't actually post the URL here:
productforums.google.com/forum/#!topic/nexus/GgnRFsw3o-Q%5B176-200-false%5D
There look to be about four or five different problems with sensors including the orientation/gyroscope sensor.
Click to expand...
Click to collapse
I've checked it out and it doesn't seem like many solutions helped, I'm under warranty so I may just send it in for repairs.
Sensors are not working at all. Screen rotation isn't.. And phone calls don't shut screen off by ear.
Cpu-z isn't displaying sensor status
Got some sensor testing apps and they also don't pick up sensor activity, however they detect the sensors present and give full hardware details.
I got the 9507v
Anything....????? Please
RemixedCat said:
Sensors are not working at all. Screen rotation isn't.. And phone calls don't shut screen off by ear.
Cpu-z isn't displaying sensor status
Got some sensor testing apps and they also don't pick up sensor activity, however they detect the sensors present and give full hardware details.
I got the 9507v
Click to expand...
Click to collapse
Im saying its the rom bugs.
You can check if its the phone or the rom by flashing a stock rom
RemixedCat said:
Anything....????? Please
Click to expand...
Click to collapse
You flashed wrong custom ROM for the GT-i9507V. That ROM is for GT-i9505 (jfltexx). Flash the stock ROM for recover your device.
Any cm snapshot ROMs for it? I was told it would work fine
All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.
Hurricane Andrew said:
All of a sudden yesterday, my trusty old Nexus 10 stopped auto-rotating. Apps that have a fixed orientation will work and rotate the screen, but then the screen stays in that orientation until an app with a different fixed orientation is launched. I downloaded a couple sensor checking apps, and it seems the gyroscope/compass/acceleremeter are just dead. It doesn't register anything at all on the apps. I'm guessing it's just the result of age (no "trauma" to the device such as a drop or anything). Any similar experiences, or thoughts on repairing? I doubt I'll replace the tablet anytime soon, it's really just a media consumption device at this point, though a couple of the games I played used the gryo/accel. My initial thought is it's just time to let it go, use it for what I can, then provide a proper burial when it totally dies.
Click to expand...
Click to collapse
probably your sensor is dead(could you try to install some app that display all sensors informations? you should find that easily on the play store).
could you also tell us what is your ROM ?
I'm running the current official LMY49F, but rooted.
Hurricane Andrew said:
I'm running the current official LMY49F, but rooted.
Click to expand...
Click to collapse
Hm indeed your issue should not happen( I think) with lollipop.
MM had some issues with sensors but since you are on lollipop ...
Hehe, well then you should flash a rom with a QS tile to rotate hehe.
LOL, probably not going to mess with flashing a new ROM. Like I said, I only use it for media consumption and some light gaming...nothing that "needs" the gyro, so I'll just live with it until it totally dies
Huh, son a gun. Just flashed the Feb Nexus update via fastboot, and low and behold, it lives again! Looks like it was software related after all.