Hi,
Final my p-sensor is working fine.
The fix areas are: p-sensor disable ioctl() & platform gpio configurations.
Because of improper configuration in GPIO, while I am moving my device away
from EAR, proximity h/w able to generate interrupt but my driver is unable
to proceed.
Thanks for Androi
Hi CVS,
My device runs on qualcomm Snapdragon.
Yes my device having a support for wakeup-support, i enabled & disabled
during ENABLE & DISABLE ioctls from HAL with enable_irq_wake() &
disable_irq_wake()
calls.
Regards,
Jagan.
On Fri, Jun 17, 2011 at 10:09 AM, Chinmay S wrote:
> Hi Jagan,
>
> S
Hi Jagan,
So, its confirmed that the psensor IRQ has NOT triggered in the non-working
case,
it looks like the psensor IRQ line did not wake-up the suspended device.
Which SoC are you using in your device?
Is "wakeup-support" available on the psensor IRQ line?
How did you enable it?
regards
CVS
Hi CVS,
Thanks for your response.
For non working case [w/o USB] the device is completely suspend.
I should wake-up in two situations
1. Connect USB, move the device near to EAR it's wake-up...and continue
again
2. When call is disconnected by another end. device comes with home-screen.
In non-
Hi Jagan,
>From the attached logs, its obvious that in the non-working case (w/o the
USB cable),
the device has entered complete suspend ( Userspace processes frozen )
and hence the Sensor-HAL code wont be active.
>From the logs you have shared, it appears that the device after going into
suspend
Hi Dan,
I confirm that my driver is configured as wakeble interrupts support.
Regards,
Jagan
On Thu, Jun 16, 2011 at 6:21 PM, jagan <402ja...@gmail.com> wrote:
> Hi Dan,
>
> I still unable to resolve my p-sensor issue.
>
> I will tell you the issue once again
> => Receive one MT call
> => Answe
Hi Dan,
I still unable to resolve my p-sensor issue.
I will tell you the issue once again
=> Receive one MT call
=> Answer the call and put device to close to your ear
=> P-sensor can work and backlight turn off
=> while i am moving phone away from EAR screen is not turned ON.
My p-sensor h/w is
Are you sure that the proximity sensor sent the data to the user space
to wake up the device?
Are you sure that the proximity driver is configured as a wakeable
interrupt?
Dan
On Apr 26, 12:51 am, jagan <402ja...@gmail.com> wrote:
> Dan,
>
> Then what is significance of maxRange, resolution w.r.t
Dan,
Then what is significance of maxRange, resolution w.r.t PROXIMITY_THRESHOLD
value.
When i update the above attributes also,
Some times my device is not resumes, while it is away from my ear.
Thanks,
Jagan
On Tue, Apr 26, 2011 at 11:12 AM, JakeLian wrote:
> Dear Dan,
>
> Thanks for your s
Dear Dan,
Thanks for your suggestions and responses.
Regarding to my question, I have the solution and implement done.
My solution is writting a function to get sensor output data from
sysfs and report it to the framework, then we can monitor it via some
sensor related apk.
Best Regards
Jake
-
Jake
Actually the readEvents implementation is all what you want it to be.
Currently Android uses the input_dev facilities to report sensor data.
But that is frowned upon by the input maintainer in the OS community.
They are looking at
using IIO kernel framework to report industrial sensor techno
Jagan
LGTM
Dan
On Apr 25, 6:13 am, jagan <402ja...@gmail.com> wrote:
> Hi Dan,
>
> Thanks for your response.
>
> Please identify the Sensor Attributes like
>
> name: "my_prox",
> vendor: "my_prox_ven",
> version: 1,
> handle: SENSOR_
Sorry, I have another question about driver implementation for
sensors.
The above discussion are all base on "input dev" mechanism, right?
If I implement a driver and base on "sysfs" mechanism (include get
sensor output value and set output data rate for sensor), how can I
report the sensor outpu
Hi Dan,
Thanks for your response.
Please identify the Sensor Attributes like
name: "my_prox",
vendor: "my_prox_ven",
version: 1,
handle: SENSOR_PROXIMITY_HANDLE,
type: SENSOR_TYPE_PROXIMITY,
maxRange:
So you have a binary prox sensor that reports a zero or one to the
sensor HAL.
The sensor HAL should convert this to some distance in millimeters to
report this to the application layer.
This, in your case, will either be 0 or 9mm.
Do you know how far off the glass the proximity is supposed to
tri
Hi Dan.
Could you please help if you have any inputs on this issue.
On Wed, Apr 20, 20input11 at 10:56 PM, jagan <402ja...@gmail.com> wrote:
> Hi Dan.
>
> For distance event point of view the below are observations
>
> in my driver:
> -
>
> input_set_abs_params(inp
Hi Dan.
For distance event point of view the below are observations
in my driver:
-
input_set_abs_params(input_dev, ABS_DISTANCE, 0, 1, 0, 0);.
in my HAL:
I am setting distance as follows
#define PROXIMTY_THRESHOLD9.0f
float in
I think he is saying to check to see that your JNI and app handle the binary
type if you use Binary Attributes in the driver
On Wed, Apr 20, 2011 at 8:50 AM, jagan <402ja...@gmail.com> wrote:
> Hi Dan,
>
> I didn't get you what you explain.
>
> Could you please Elaborate.
>
> Jagan.
>
>
> On Wed,
Hi Dan,
I didn't get you what you explain.
Could you please Elaborate.
Jagan.
On Wed, Apr 20, 2011 at 8:11 PM, DanM wrote:
> More then likely when you plugged in your USB cable it caused the
> battery to start charging which will wake up the device.
>
> If you report a binary from the prox s
More then likely when you plugged in your USB cable it caused the
battery to start charging which will wake up the device.
If you report a binary from the prox sensor make sure the sensor HAL
converts this to millimeters.
Dan
On Apr 19, 3:29 pm, jagan <402ja...@gmail.com> wrote:
> Hi.
>
> With a
Hi.
With a reff. of device/htc/passion-common/
I am able to port p-sensor on my device.
I am testing with calling my device to another device, after receiving i put
my device into my ear.
screen is OFF, while removing screen ON.. upto here ok.
when i do the same thing in multiple times, at one i
Hi.
As the newly added sensor framework layer in GB.
we may need to change you HAL.
For reff. HAL see device/htc/passion-common/
libsensors
Jagan.
On Mon, Apr 18, 2011 at 6:04 PM, Aditya wrote:
> Dan,
> I had the exact same problem, and my HAL (Hardware Access Layer) was had a
> different n
Dan,
I had the exact same problem, and my HAL (Hardware Access Layer) was had a
different name. Took me a while to figure it out. It would be a good idea to
submit in the the exceptions for this.
-Aditya
On Sun, Apr 17, 2011 at 9:39 AM, DanM wrote:
> I assume you are checking the logcat log an
I assume you are checking the logcat log and not the kernel log?
If you are checking logcat and don't see that your HAL is started make
sure your sensor HAL .so has the correct name
or else Android will not find the HAL and load it
Dan
On Apr 16, 8:40 am, jagan <402ja...@gmail.com> wrote:
> I go
I got the sensor boot logs for drivers,
but while testing any sensor i didn't get any logs from HAL.
Jagan
On Sat, Apr 16, 2011 at 5:15 PM, DanM wrote:
> Is your sensor library being loaded at boot?
>
> Maybe put some log messages in your HAL and first verify that the
> sensor library initializ
Is your sensor library being loaded at boot?
Maybe put some log messages in your HAL and first verify that the
sensor library initialized.
Are you sure that the drivers are producing data?
Dan
On Apr 15, 11:53 pm, Luo Chunbo wrote:
> There framework for sensors are changed in Gingerbread.
>
> A
26 matches
Mail list logo
