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: 9.0f,
resolution: 9.0f,
power: 0.5f,
minDelay: 20000,
and my PROXIMTY_THRESHOLD would be 9.0f
Please verify the above attributes, tell me if anyting i did incorrect.
Thanks,
Jagan
On Sat, Apr 23, 2011 at 5:22 PM, DanM <murpd...@gmail.com> wrote:
> 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
> trigger?
> Thats what PROXIMITY_THRESHOLD is supposed to be set to.
>
> You also need to tell the Sensor Manager the proximity attributes via
> the sensors_t struct.
>
> Incorrectly defined attributes may mean that the value may not be
> reported to the application.
>
> Dan
>
> On Apr 21, 9:45 am, jagan <402ja...@gmail.com> wrote:
> > 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(input_dev, ABS_DISTANCE, 0, 1, 0,
> 0);.
> >
> > > in my HAL:
> > > ----------------
> > > I am setting distance as follows
> >
> > > #define PROXIMTY_THRESHOLD 9.0f
> >
> > > float indexValue (size_t index) {
> > > return index * PROXIMITY_THRESHOLD;
> > > }
> >
> > > pending_event.distance = indexValue(event->value);
> >
> > > Is there any problem with index calculation in indexValue()? or
> > > PROXIMTY_THRESHOLD value is improper?
> >
> > > Please let me tell me know if you have any inputs.
> >
> > > Jagan.
> >
> > > On Wed, Apr 20, 2011 at 9:24 PM, mike digioia <mpd...@gmail.com>
> wrote:
> >
> > >> 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, Apr 20, 2011 at 8:11 PM, DanM <murpd...@gmail.com> 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 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 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 instance while
> i am
> > >>>> > putting my device into my ear,
> > >>>> > it's going OFF, while removing it's screen is not turn back to ON.
> > >>>> > but when i connect my usb cable, it's turn ON.
> >
> > >>>> > What is the relation between p-sensor vs USB here.?
> >
> > >>>> > I am changing my p-sensor driver that supports input subsystem by
> > >>>> setting
> > >>>> > params as
> > >>>> > input_set_abs_params(input_dev, ABS_DISTANCE, 0, 1, 0, 0);.
> >
> > >>>> > Is the above setting is correct for Proximity Sensor?
> >
> > >>>> > Please correct me if any thing i am setting wrong.
> >
> > >>>> > Please let me know if any inputs on this issue.?
> >
> > >>>> > Thanks,
> > >>>> > Jagan
> >
> > >>>> > On Mon, Apr 18, 2011 at 6:40 PM, jagan <402ja...@gmail.com>
> wrote:
> > >>>> > > 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 <
> > >>>> aditya.s.mukher...@gmail.com>wrote:
> >
> > >>>> > >> 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 <murpd...@gmail.com>
> wrote:
> >
> > >>>> > >>> 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 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 <murpd...@gmail.com>
> > >>>> wrote:
> > >>>> > >>> > > 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 <lu...@paragonfmc.com>
> wrote:
> > >>>> > >>> > > > There framework for sensors are changed in Gingerbread.
> >
> > >>>> > >>> > > > And and think you can refer
> > >>>> device/htc/passion-common/libsensors
> > >>>> > >>> > > > or device/samsung/crespo/libsensors
> >
> > >>>> > >>> > > > There are some sample code of sensors in these
> directories.
> >
> > >>>> > >>> > > > Thanks
> > >>>> > >>> > > > Chunbo
> >
> > >>>> > >>> > > > On 04/15/2011 08:43 PM, jagan wrote:
> >
> > >>>> > >>> > > > > Hi All,
> >
> > >>>> > >>> > > > > I am upgrading my android device[with qualcomm
> chipset]
> > >>>> into
> > >>>> > >>> > > > > Gingerbread.
> >
> > >>>> > >>> > > > > I am facing a problem with All my sensors are not
> working
> > >>>> on
> > >>>> > >>> device.
> >
> > >>>> > >>> > > > > I ported:
> > >>>> > >>> > > > > -----------
> > >>>> > >>> > > > > => sensor drivers in kernel [i got the boot up sensor
> > >>>> init logs]
> > >>>> > >>> > > > > => my HAL sensor daemon [having all sensor operations
> > >>>> from user
> > >>>> > >>> space
> > >>>> > >>> > > > > to call driver code]
> >
> > >>>> > >>> > > > > With the above changes my sensors are not working.
> >
> > >>>> > >>> > > > > As per my analysis there is a new sensorservice layer
> is
> > >>>> added in
> > >>>> > >>> > > > > Gingerbread.
> >
> > >>>> > >>> > > > > Is there any way to change my HAL, to support new
> > >>>> sensorservice
> > >>>> > >>> added
> > >>>> > >>> > > > > by GB.
> >
> > >>>> > >>> > > > > Please tell me any one how to add my sensor HAL to
> > >>>> Gingerbread.
> >
> > >>>> > >>> > > > > Thank you.
> > >>>> > >>> > > > > Jagan
> >
> > >>>> > >>> > > --
> > >>>> > >>> > > unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >>>> > >>> > > website:http://groups.google.com/group/android-kernel
> >
> > >>>> > >>> --
> > >>>> > >>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >>>> > >>> website:http://groups.google.com/group/android-kernel
> >
> > >>>> > >> --
> > >>>> > >> Aditya Mukherjee
> > >>>> > >> Rutgers University
> > >>>> > >> Department Of Computer Science
> >
> > >>>> > >> --
> > >>>> > >> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >>>> > >> website:http://groups.google.com/group/android-kernel
> >
> > >>>> --
> > >>>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >>>> website:http://groups.google.com/group/android-kernel
> >
> > >>> --
> > >>> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >>> website:http://groups.google.com/group/android-kernel
> >
> > >> --
> > >> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> > >> website:http://groups.google.com/group/android-kernel
>
> --
> unsubscribe: android-kernel+unsubscr...@googlegroups.com
> website: http://groups.google.com/group/android-kernel
>
--
unsubscribe: android-kernel+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-kernel
