zenfone6: Add some product blobs
Change-Id: I6e0d674193edee3c943c2d2bb695678bb7989842
diff --git a/extract-files.sh b/extract-files.sh
index 2eaabc9..ed29f36 100755
--- a/extract-files.sh
+++ b/extract-files.sh
@@ -59,8 +59,7 @@
# Initialize the helper
setup_vendor "$DEVICE" "$VENDOR" "$CM_ROOT" false "$CLEAN_VENDOR"
-extract "$MY_DIR"/proprietary-files-qc.txt "$SRC" "$SECTION"
-extract "$MY_DIR"/proprietary-files-qc-perf.txt "$SRC" "$SECTION"
+extract "$MY_DIR"/proprietary-files-product.txt "$SRC" "$SECTION"
extract "$MY_DIR"/proprietary-files.txt "$SRC" "$SECTION"
"$MY_DIR"/setup-makefiles.sh
diff --git a/prebuilt/system/etc/sensors/proto/descriptor.proto b/prebuilt/system/etc/sensors/proto/descriptor.proto
deleted file mode 100644
index 08b1555..0000000
--- a/prebuilt/system/etc/sensors/proto/descriptor.proto
+++ /dev/null
@@ -1,803 +0,0 @@
-// Protocol Buffers - Google's data interchange format
-// Copyright 2008 Google Inc. All rights reserved.
-// https://developers.google.com/protocol-buffers/
-//
-// Redistribution and use in source and binary forms, with or without
-// modification, are permitted provided that the following conditions are
-// met:
-//
-// * Redistributions of source code must retain the above copyright
-// notice, this list of conditions and the following disclaimer.
-// * Redistributions in binary form must reproduce the above
-// copyright notice, this list of conditions and the following disclaimer
-// in the documentation and/or other materials provided with the
-// distribution.
-// * Neither the name of Google Inc. nor the names of its
-// contributors may be used to endorse or promote products derived from
-// this software without specific prior written permission.
-//
-// THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS
-// "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT
-// LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR
-// A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT
-// OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
-// SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
-// LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
-// DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
-// THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
-// (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE
-// OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
-
-// Author: kenton@google.com (Kenton Varda)
-// Based on original Protocol Buffers design by
-// Sanjay Ghemawat, Jeff Dean, and others.
-//
-// The messages in this file describe the definitions found in .proto files.
-// A valid .proto file can be translated directly to a FileDescriptorProto
-// without any other information (e.g. without reading its imports).
-
-
-syntax = "proto2";
-
-package google.protobuf;
-option go_package = "descriptor";
-option java_package = "com.google.protobuf";
-option java_outer_classname = "DescriptorProtos";
-option csharp_namespace = "Google.Protobuf.Reflection";
-option objc_class_prefix = "GPB";
-
-// descriptor.proto must be optimized for speed because reflection-based
-// algorithms don't work during bootstrapping.
-option optimize_for = SPEED;
-
-// The protocol compiler can output a FileDescriptorSet containing the .proto
-// files it parses.
-message FileDescriptorSet {
- repeated FileDescriptorProto file = 1;
-}
-
-// Describes a complete .proto file.
-message FileDescriptorProto {
- optional string name = 1; // file name, relative to root of source tree
- optional string package = 2; // e.g. "foo", "foo.bar", etc.
-
- // Names of files imported by this file.
- repeated string dependency = 3;
- // Indexes of the public imported files in the dependency list above.
- repeated int32 public_dependency = 10;
- // Indexes of the weak imported files in the dependency list.
- // For Google-internal migration only. Do not use.
- repeated int32 weak_dependency = 11;
-
- // All top-level definitions in this file.
- repeated DescriptorProto message_type = 4;
- repeated EnumDescriptorProto enum_type = 5;
- repeated ServiceDescriptorProto service = 6;
- repeated FieldDescriptorProto extension = 7;
-
- optional FileOptions options = 8;
-
- // This field contains optional information about the original source code.
- // You may safely remove this entire field without harming runtime
- // functionality of the descriptors -- the information is needed only by
- // development tools.
- optional SourceCodeInfo source_code_info = 9;
-
- // The syntax of the proto file.
- // The supported values are "proto2" and "proto3".
- optional string syntax = 12;
-}
-
-// Describes a message type.
-message DescriptorProto {
- optional string name = 1;
-
- repeated FieldDescriptorProto field = 2;
- repeated FieldDescriptorProto extension = 6;
-
- repeated DescriptorProto nested_type = 3;
- repeated EnumDescriptorProto enum_type = 4;
-
- message ExtensionRange {
- optional int32 start = 1;
- optional int32 end = 2;
- }
- repeated ExtensionRange extension_range = 5;
-
- repeated OneofDescriptorProto oneof_decl = 8;
-
- optional MessageOptions options = 7;
-
- // Range of reserved tag numbers. Reserved tag numbers may not be used by
- // fields or extension ranges in the same message. Reserved ranges may
- // not overlap.
- message ReservedRange {
- optional int32 start = 1; // Inclusive.
- optional int32 end = 2; // Exclusive.
- }
- repeated ReservedRange reserved_range = 9;
- // Reserved field names, which may not be used by fields in the same message.
- // A given name may only be reserved once.
- repeated string reserved_name = 10;
-}
-
-// Describes a field within a message.
-message FieldDescriptorProto {
- enum Type {
- // 0 is reserved for errors.
- // Order is weird for historical reasons.
- TYPE_DOUBLE = 1;
- TYPE_FLOAT = 2;
- // Not ZigZag encoded. Negative numbers take 10 bytes. Use TYPE_SINT64 if
- // negative values are likely.
- TYPE_INT64 = 3;
- TYPE_UINT64 = 4;
- // Not ZigZag encoded. Negative numbers take 10 bytes. Use TYPE_SINT32 if
- // negative values are likely.
- TYPE_INT32 = 5;
- TYPE_FIXED64 = 6;
- TYPE_FIXED32 = 7;
- TYPE_BOOL = 8;
- TYPE_STRING = 9;
- TYPE_GROUP = 10; // Tag-delimited aggregate.
- TYPE_MESSAGE = 11; // Length-delimited aggregate.
-
- // New in version 2.
- TYPE_BYTES = 12;
- TYPE_UINT32 = 13;
- TYPE_ENUM = 14;
- TYPE_SFIXED32 = 15;
- TYPE_SFIXED64 = 16;
- TYPE_SINT32 = 17; // Uses ZigZag encoding.
- TYPE_SINT64 = 18; // Uses ZigZag encoding.
- };
-
- enum Label {
- // 0 is reserved for errors
- LABEL_OPTIONAL = 1;
- LABEL_REQUIRED = 2;
- LABEL_REPEATED = 3;
- // TODO(sanjay): Should we add LABEL_MAP?
- };
-
- optional string name = 1;
- optional int32 number = 3;
- optional Label label = 4;
-
- // If type_name is set, this need not be set. If both this and type_name
- // are set, this must be one of TYPE_ENUM, TYPE_MESSAGE or TYPE_GROUP.
- optional Type type = 5;
-
- // For message and enum types, this is the name of the type. If the name
- // starts with a '.', it is fully-qualified. Otherwise, C++-like scoping
- // rules are used to find the type (i.e. first the nested types within this
- // message are searched, then within the parent, on up to the root
- // namespace).
- optional string type_name = 6;
-
- // For extensions, this is the name of the type being extended. It is
- // resolved in the same manner as type_name.
- optional string extendee = 2;
-
- // For numeric types, contains the original text representation of the value.
- // For booleans, "true" or "false".
- // For strings, contains the default text contents (not escaped in any way).
- // For bytes, contains the C escaped value. All bytes >= 128 are escaped.
- // TODO(kenton): Base-64 encode?
- optional string default_value = 7;
-
- // If set, gives the index of a oneof in the containing type's oneof_decl
- // list. This field is a member of that oneof.
- optional int32 oneof_index = 9;
-
- // JSON name of this field. The value is set by protocol compiler. If the
- // user has set a "json_name" option on this field, that option's value
- // will be used. Otherwise, it's deduced from the field's name by converting
- // it to camelCase.
- optional string json_name = 10;
-
- optional FieldOptions options = 8;
-}
-
-// Describes a oneof.
-message OneofDescriptorProto {
- optional string name = 1;
-}
-
-// Describes an enum type.
-message EnumDescriptorProto {
- optional string name = 1;
-
- repeated EnumValueDescriptorProto value = 2;
-
- optional EnumOptions options = 3;
-}
-
-// Describes a value within an enum.
-message EnumValueDescriptorProto {
- optional string name = 1;
- optional int32 number = 2;
-
- optional EnumValueOptions options = 3;
-}
-
-// Describes a service.
-message ServiceDescriptorProto {
- optional string name = 1;
- repeated MethodDescriptorProto method = 2;
-
- optional ServiceOptions options = 3;
-}
-
-// Describes a method of a service.
-message MethodDescriptorProto {
- optional string name = 1;
-
- // Input and output type names. These are resolved in the same way as
- // FieldDescriptorProto.type_name, but must refer to a message type.
- optional string input_type = 2;
- optional string output_type = 3;
-
- optional MethodOptions options = 4;
-
- // Identifies if client streams multiple client messages
- optional bool client_streaming = 5 [default=false];
- // Identifies if server streams multiple server messages
- optional bool server_streaming = 6 [default=false];
-}
-
-
-// ===================================================================
-// Options
-
-// Each of the definitions above may have "options" attached. These are
-// just annotations which may cause code to be generated slightly differently
-// or may contain hints for code that manipulates protocol messages.
-//
-// Clients may define custom options as extensions of the *Options messages.
-// These extensions may not yet be known at parsing time, so the parser cannot
-// store the values in them. Instead it stores them in a field in the *Options
-// message called uninterpreted_option. This field must have the same name
-// across all *Options messages. We then use this field to populate the
-// extensions when we build a descriptor, at which point all protos have been
-// parsed and so all extensions are known.
-//
-// Extension numbers for custom options may be chosen as follows:
-// * For options which will only be used within a single application or
-// organization, or for experimental options, use field numbers 50000
-// through 99999. It is up to you to ensure that you do not use the
-// same number for multiple options.
-// * For options which will be published and used publicly by multiple
-// independent entities, e-mail protobuf-global-extension-registry@google.com
-// to reserve extension numbers. Simply provide your project name (e.g.
-// Objective-C plugin) and your project website (if available) -- there's no
-// need to explain how you intend to use them. Usually you only need one
-// extension number. You can declare multiple options with only one extension
-// number by putting them in a sub-message. See the Custom Options section of
-// the docs for examples:
-// https://developers.google.com/protocol-buffers/docs/proto#options
-// If this turns out to be popular, a web service will be set up
-// to automatically assign option numbers.
-
-
-message FileOptions {
-
- // Sets the Java package where classes generated from this .proto will be
- // placed. By default, the proto package is used, but this is often
- // inappropriate because proto packages do not normally start with backwards
- // domain names.
- optional string java_package = 1;
-
-
- // If set, all the classes from the .proto file are wrapped in a single
- // outer class with the given name. This applies to both Proto1
- // (equivalent to the old "--one_java_file" option) and Proto2 (where
- // a .proto always translates to a single class, but you may want to
- // explicitly choose the class name).
- optional string java_outer_classname = 8;
-
- // If set true, then the Java code generator will generate a separate .java
- // file for each top-level message, enum, and service defined in the .proto
- // file. Thus, these types will *not* be nested inside the outer class
- // named by java_outer_classname. However, the outer class will still be
- // generated to contain the file's getDescriptor() method as well as any
- // top-level extensions defined in the file.
- optional bool java_multiple_files = 10 [default=false];
-
- // If set true, then the Java code generator will generate equals() and
- // hashCode() methods for all messages defined in the .proto file.
- // This increases generated code size, potentially substantially for large
- // protos, which may harm a memory-constrained application.
- // - In the full runtime this is a speed optimization, as the
- // AbstractMessage base class includes reflection-based implementations of
- // these methods.
- // - In the lite runtime, setting this option changes the semantics of
- // equals() and hashCode() to more closely match those of the full runtime;
- // the generated methods compute their results based on field values rather
- // than object identity. (Implementations should not assume that hashcodes
- // will be consistent across runtimes or versions of the protocol compiler.)
- optional bool java_generate_equals_and_hash = 20 [default=false];
-
- // If set true, then the Java2 code generator will generate code that
- // throws an exception whenever an attempt is made to assign a non-UTF-8
- // byte sequence to a string field.
- // Message reflection will do the same.
- // However, an extension field still accepts non-UTF-8 byte sequences.
- // This option has no effect on when used with the lite runtime.
- optional bool java_string_check_utf8 = 27 [default=false];
-
-
- // Generated classes can be optimized for speed or code size.
- enum OptimizeMode {
- SPEED = 1; // Generate complete code for parsing, serialization,
- // etc.
- CODE_SIZE = 2; // Use ReflectionOps to implement these methods.
- LITE_RUNTIME = 3; // Generate code using MessageLite and the lite runtime.
- }
- optional OptimizeMode optimize_for = 9 [default=SPEED];
-
- // Sets the Go package where structs generated from this .proto will be
- // placed. If omitted, the Go package will be derived from the following:
- // - The basename of the package import path, if provided.
- // - Otherwise, the package statement in the .proto file, if present.
- // - Otherwise, the basename of the .proto file, without extension.
- optional string go_package = 11;
-
-
-
- // Should generic services be generated in each language? "Generic" services
- // are not specific to any particular RPC system. They are generated by the
- // main code generators in each language (without additional plugins).
- // Generic services were the only kind of service generation supported by
- // early versions of google.protobuf.
- //
- // Generic services are now considered deprecated in favor of using plugins
- // that generate code specific to your particular RPC system. Therefore,
- // these default to false. Old code which depends on generic services should
- // explicitly set them to true.
- optional bool cc_generic_services = 16 [default=false];
- optional bool java_generic_services = 17 [default=false];
- optional bool py_generic_services = 18 [default=false];
-
- // Is this file deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for everything in the file, or it will be completely ignored; in the very
- // least, this is a formalization for deprecating files.
- optional bool deprecated = 23 [default=false];
-
- // Enables the use of arenas for the proto messages in this file. This applies
- // only to generated classes for C++.
- optional bool cc_enable_arenas = 31 [default=false];
-
-
- // Sets the objective c class prefix which is prepended to all objective c
- // generated classes from this .proto. There is no default.
- optional string objc_class_prefix = 36;
-
- // Namespace for generated classes; defaults to the package.
- optional string csharp_namespace = 37;
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-
- reserved 38;
-}
-
-message MessageOptions {
- // Set true to use the old proto1 MessageSet wire format for extensions.
- // This is provided for backwards-compatibility with the MessageSet wire
- // format. You should not use this for any other reason: It's less
- // efficient, has fewer features, and is more complicated.
- //
- // The message must be defined exactly as follows:
- // message Foo {
- // option message_set_wire_format = true;
- // extensions 4 to max;
- // }
- // Note that the message cannot have any defined fields; MessageSets only
- // have extensions.
- //
- // All extensions of your type must be singular messages; e.g. they cannot
- // be int32s, enums, or repeated messages.
- //
- // Because this is an option, the above two restrictions are not enforced by
- // the protocol compiler.
- optional bool message_set_wire_format = 1 [default=false];
-
- // Disables the generation of the standard "descriptor()" accessor, which can
- // conflict with a field of the same name. This is meant to make migration
- // from proto1 easier; new code should avoid fields named "descriptor".
- optional bool no_standard_descriptor_accessor = 2 [default=false];
-
- // Is this message deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for the message, or it will be completely ignored; in the very least,
- // this is a formalization for deprecating messages.
- optional bool deprecated = 3 [default=false];
-
- // Whether the message is an automatically generated map entry type for the
- // maps field.
- //
- // For maps fields:
- // map<KeyType, ValueType> map_field = 1;
- // The parsed descriptor looks like:
- // message MapFieldEntry {
- // option map_entry = true;
- // optional KeyType key = 1;
- // optional ValueType value = 2;
- // }
- // repeated MapFieldEntry map_field = 1;
- //
- // Implementations may choose not to generate the map_entry=true message, but
- // use a native map in the target language to hold the keys and values.
- // The reflection APIs in such implementions still need to work as
- // if the field is a repeated message field.
- //
- // NOTE: Do not set the option in .proto files. Always use the maps syntax
- // instead. The option should only be implicitly set by the proto compiler
- // parser.
- optional bool map_entry = 7;
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-message FieldOptions {
- // The ctype option instructs the C++ code generator to use a different
- // representation of the field than it normally would. See the specific
- // options below. This option is not yet implemented in the open source
- // release -- sorry, we'll try to include it in a future version!
- optional CType ctype = 1 [default = STRING];
- enum CType {
- // Default mode.
- STRING = 0;
-
- CORD = 1;
-
- STRING_PIECE = 2;
- }
- // The packed option can be enabled for repeated primitive fields to enable
- // a more efficient representation on the wire. Rather than repeatedly
- // writing the tag and type for each element, the entire array is encoded as
- // a single length-delimited blob. In proto3, only explicit setting it to
- // false will avoid using packed encoding.
- optional bool packed = 2;
-
-
- // The jstype option determines the JavaScript type used for values of the
- // field. The option is permitted only for 64 bit integral and fixed types
- // (int64, uint64, sint64, fixed64, sfixed64). By default these types are
- // represented as JavaScript strings. This avoids loss of precision that can
- // happen when a large value is converted to a floating point JavaScript
- // numbers. Specifying JS_NUMBER for the jstype causes the generated
- // JavaScript code to use the JavaScript "number" type instead of strings.
- // This option is an enum to permit additional types to be added,
- // e.g. goog.math.Integer.
- optional JSType jstype = 6 [default = JS_NORMAL];
- enum JSType {
- // Use the default type.
- JS_NORMAL = 0;
-
- // Use JavaScript strings.
- JS_STRING = 1;
-
- // Use JavaScript numbers.
- JS_NUMBER = 2;
- }
-
- // Should this field be parsed lazily? Lazy applies only to message-type
- // fields. It means that when the outer message is initially parsed, the
- // inner message's contents will not be parsed but instead stored in encoded
- // form. The inner message will actually be parsed when it is first accessed.
- //
- // This is only a hint. Implementations are free to choose whether to use
- // eager or lazy parsing regardless of the value of this option. However,
- // setting this option true suggests that the protocol author believes that
- // using lazy parsing on this field is worth the additional bookkeeping
- // overhead typically needed to implement it.
- //
- // This option does not affect the public interface of any generated code;
- // all method signatures remain the same. Furthermore, thread-safety of the
- // interface is not affected by this option; const methods remain safe to
- // call from multiple threads concurrently, while non-const methods continue
- // to require exclusive access.
- //
- //
- // Note that implementations may choose not to check required fields within
- // a lazy sub-message. That is, calling IsInitialized() on the outher message
- // may return true even if the inner message has missing required fields.
- // This is necessary because otherwise the inner message would have to be
- // parsed in order to perform the check, defeating the purpose of lazy
- // parsing. An implementation which chooses not to check required fields
- // must be consistent about it. That is, for any particular sub-message, the
- // implementation must either *always* check its required fields, or *never*
- // check its required fields, regardless of whether or not the message has
- // been parsed.
- optional bool lazy = 5 [default=false];
-
- // Is this field deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for accessors, or it will be completely ignored; in the very least, this
- // is a formalization for deprecating fields.
- optional bool deprecated = 3 [default=false];
-
- // For Google-internal migration only. Do not use.
- optional bool weak = 10 [default=false];
-
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-message EnumOptions {
-
- // Set this option to true to allow mapping different tag names to the same
- // value.
- optional bool allow_alias = 2;
-
- // Is this enum deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for the enum, or it will be completely ignored; in the very least, this
- // is a formalization for deprecating enums.
- optional bool deprecated = 3 [default=false];
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-message EnumValueOptions {
- // Is this enum value deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for the enum value, or it will be completely ignored; in the very least,
- // this is a formalization for deprecating enum values.
- optional bool deprecated = 1 [default=false];
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-message ServiceOptions {
-
- // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
- // framework. We apologize for hoarding these numbers to ourselves, but
- // we were already using them long before we decided to release Protocol
- // Buffers.
-
- // Is this service deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for the service, or it will be completely ignored; in the very least,
- // this is a formalization for deprecating services.
- optional bool deprecated = 33 [default=false];
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-message MethodOptions {
-
- // Note: Field numbers 1 through 32 are reserved for Google's internal RPC
- // framework. We apologize for hoarding these numbers to ourselves, but
- // we were already using them long before we decided to release Protocol
- // Buffers.
-
- // Is this method deprecated?
- // Depending on the target platform, this can emit Deprecated annotations
- // for the method, or it will be completely ignored; in the very least,
- // this is a formalization for deprecating methods.
- optional bool deprecated = 33 [default=false];
-
- // The parser stores options it doesn't recognize here. See above.
- repeated UninterpretedOption uninterpreted_option = 999;
-
- // Clients can define custom options in extensions of this message. See above.
- extensions 1000 to max;
-}
-
-
-// A message representing a option the parser does not recognize. This only
-// appears in options protos created by the compiler::Parser class.
-// DescriptorPool resolves these when building Descriptor objects. Therefore,
-// options protos in descriptor objects (e.g. returned by Descriptor::options(),
-// or produced by Descriptor::CopyTo()) will never have UninterpretedOptions
-// in them.
-message UninterpretedOption {
- // The name of the uninterpreted option. Each string represents a segment in
- // a dot-separated name. is_extension is true iff a segment represents an
- // extension (denoted with parentheses in options specs in .proto files).
- // E.g.,{ ["foo", false], ["bar.baz", true], ["qux", false] } represents
- // "foo.(bar.baz).qux".
- message NamePart {
- required string name_part = 1;
- required bool is_extension = 2;
- }
- repeated NamePart name = 2;
-
- // The value of the uninterpreted option, in whatever type the tokenizer
- // identified it as during parsing. Exactly one of these should be set.
- optional string identifier_value = 3;
- optional uint64 positive_int_value = 4;
- optional int64 negative_int_value = 5;
- optional double double_value = 6;
- optional bytes string_value = 7;
- optional string aggregate_value = 8;
-}
-
-// ===================================================================
-// Optional source code info
-
-// Encapsulates information about the original source file from which a
-// FileDescriptorProto was generated.
-message SourceCodeInfo {
- // A Location identifies a piece of source code in a .proto file which
- // corresponds to a particular definition. This information is intended
- // to be useful to IDEs, code indexers, documentation generators, and similar
- // tools.
- //
- // For example, say we have a file like:
- // message Foo {
- // optional string foo = 1;
- // }
- // Let's look at just the field definition:
- // optional string foo = 1;
- // ^ ^^ ^^ ^ ^^^
- // a bc de f ghi
- // We have the following locations:
- // span path represents
- // [a,i) [ 4, 0, 2, 0 ] The whole field definition.
- // [a,b) [ 4, 0, 2, 0, 4 ] The label (optional).
- // [c,d) [ 4, 0, 2, 0, 5 ] The type (string).
- // [e,f) [ 4, 0, 2, 0, 1 ] The name (foo).
- // [g,h) [ 4, 0, 2, 0, 3 ] The number (1).
- //
- // Notes:
- // - A location may refer to a repeated field itself (i.e. not to any
- // particular index within it). This is used whenever a set of elements are
- // logically enclosed in a single code segment. For example, an entire
- // extend block (possibly containing multiple extension definitions) will
- // have an outer location whose path refers to the "extensions" repeated
- // field without an index.
- // - Multiple locations may have the same path. This happens when a single
- // logical declaration is spread out across multiple places. The most
- // obvious example is the "extend" block again -- there may be multiple
- // extend blocks in the same scope, each of which will have the same path.
- // - A location's span is not always a subset of its parent's span. For
- // example, the "extendee" of an extension declaration appears at the
- // beginning of the "extend" block and is shared by all extensions within
- // the block.
- // - Just because a location's span is a subset of some other location's span
- // does not mean that it is a descendent. For example, a "group" defines
- // both a type and a field in a single declaration. Thus, the locations
- // corresponding to the type and field and their components will overlap.
- // - Code which tries to interpret locations should probably be designed to
- // ignore those that it doesn't understand, as more types of locations could
- // be recorded in the future.
- repeated Location location = 1;
- message Location {
- // Identifies which part of the FileDescriptorProto was defined at this
- // location.
- //
- // Each element is a field number or an index. They form a path from
- // the root FileDescriptorProto to the place where the definition. For
- // example, this path:
- // [ 4, 3, 2, 7, 1 ]
- // refers to:
- // file.message_type(3) // 4, 3
- // .field(7) // 2, 7
- // .name() // 1
- // This is because FileDescriptorProto.message_type has field number 4:
- // repeated DescriptorProto message_type = 4;
- // and DescriptorProto.field has field number 2:
- // repeated FieldDescriptorProto field = 2;
- // and FieldDescriptorProto.name has field number 1:
- // optional string name = 1;
- //
- // Thus, the above path gives the location of a field name. If we removed
- // the last element:
- // [ 4, 3, 2, 7 ]
- // this path refers to the whole field declaration (from the beginning
- // of the label to the terminating semicolon).
- repeated int32 path = 1 [packed=true];
-
- // Always has exactly three or four elements: start line, start column,
- // end line (optional, otherwise assumed same as start line), end column.
- // These are packed into a single field for efficiency. Note that line
- // and column numbers are zero-based -- typically you will want to add
- // 1 to each before displaying to a user.
- repeated int32 span = 2 [packed=true];
-
- // If this SourceCodeInfo represents a complete declaration, these are any
- // comments appearing before and after the declaration which appear to be
- // attached to the declaration.
- //
- // A series of line comments appearing on consecutive lines, with no other
- // tokens appearing on those lines, will be treated as a single comment.
- //
- // leading_detached_comments will keep paragraphs of comments that appear
- // before (but not connected to) the current element. Each paragraph,
- // separated by empty lines, will be one comment element in the repeated
- // field.
- //
- // Only the comment content is provided; comment markers (e.g. //) are
- // stripped out. For block comments, leading whitespace and an asterisk
- // will be stripped from the beginning of each line other than the first.
- // Newlines are included in the output.
- //
- // Examples:
- //
- // optional int32 foo = 1; // Comment attached to foo.
- // // Comment attached to bar.
- // optional int32 bar = 2;
- //
- // optional string baz = 3;
- // // Comment attached to baz.
- // // Another line attached to baz.
- //
- // // Comment attached to qux.
- // //
- // // Another line attached to qux.
- // optional double qux = 4;
- //
- // // Detached comment for corge. This is not leading or trailing comments
- // // to qux or corge because there are blank lines separating it from
- // // both.
- //
- // // Detached comment for corge paragraph 2.
- //
- // optional string corge = 5;
- // /* Block comment attached
- // * to corge. Leading asterisks
- // * will be removed. */
- // /* Block comment attached to
- // * grault. */
- // optional int32 grault = 6;
- //
- // // ignored detached comments.
- optional string leading_comments = 3;
- optional string trailing_comments = 4;
- repeated string leading_detached_comments = 6;
- }
-}
-
-// Describes the relationship between generated code and its original source
-// file. A GeneratedCodeInfo message is associated with only one generated
-// source file, but may contain references to different source .proto files.
-message GeneratedCodeInfo {
- // An Annotation connects some span of text in generated code to an element
- // of its generating .proto file.
- repeated Annotation annotation = 1;
- message Annotation {
- // Identifies the element in the original source .proto file. This field
- // is formatted the same as SourceCodeInfo.Location.path.
- repeated int32 path = 1 [packed=true];
-
- // Identifies the filesystem path to the original source .proto.
- optional string source_file = 2;
-
- // Identifies the starting offset in bytes in the generated code
- // that relates to the identified object.
- optional int32 begin = 3;
-
- // Identifies the ending offset in bytes in the generated code that
- // relates to the identified offset. The end offset should be one past
- // the last relevant byte (so the length of the text = end - begin).
- optional int32 end = 4;
- }
-}
diff --git a/prebuilt/system/etc/sensors/proto/nanopb.proto b/prebuilt/system/etc/sensors/proto/nanopb.proto
deleted file mode 100644
index 9b2f0fb..0000000
--- a/prebuilt/system/etc/sensors/proto/nanopb.proto
+++ /dev/null
@@ -1,97 +0,0 @@
-// Custom options for defining:
-// - Maximum size of string/bytes
-// - Maximum number of elements in array
-//
-// These are used by nanopb to generate statically allocable structures
-// for memory-limited environments.
-
-syntax = "proto2";
-import "google/protobuf/descriptor.proto";
-
-option java_package = "fi.kapsi.koti.jpa.nanopb";
-
-enum FieldType {
- FT_DEFAULT = 0; // Automatically decide field type, generate static field if possible.
- FT_CALLBACK = 1; // Always generate a callback field.
- FT_POINTER = 4; // Always generate a dynamically allocated field.
- FT_STATIC = 2; // Generate a static field or raise an exception if not possible.
- FT_IGNORE = 3; // Ignore the field completely.
-}
-
-enum IntSize {
- IS_DEFAULT = 0; // Default, 32/64bit based on type in .proto
- IS_8 = 8;
- IS_16 = 16;
- IS_32 = 32;
- IS_64 = 64;
-}
-
-// This is the inner options message, which basically defines options for
-// a field. When it is used in message or file scope, it applies to all
-// fields.
-message NanoPBOptions {
- // Allocated size for 'bytes' and 'string' fields.
- optional int32 max_size = 1;
-
- // Allocated number of entries in arrays ('repeated' fields)
- optional int32 max_count = 2;
-
- // Size of integer fields. Can save some memory if you don't need
- // full 32 bits for the value.
- optional IntSize int_size = 7 [default = IS_DEFAULT];
-
- // Force type of field (callback or static allocation)
- optional FieldType type = 3 [default = FT_DEFAULT];
-
- // Use long names for enums, i.e. EnumName_EnumValue.
- optional bool long_names = 4 [default = true];
-
- // Add 'packed' attribute to generated structs.
- // Note: this cannot be used on CPUs that break on unaligned
- // accesses to variables.
- optional bool packed_struct = 5 [default = false];
-
- // Add 'packed' attribute to generated enums.
- optional bool packed_enum = 10 [default = false];
-
- // Skip this message
- optional bool skip_message = 6 [default = false];
-
- // Generate oneof fields as normal optional fields instead of union.
- optional bool no_unions = 8 [default = false];
-
- // integer type tag for a message
- optional uint32 msgid = 9;
-
- // decode oneof as anonymous union
- optional bool anonymous_oneof = 11 [default = false];
-}
-
-// Extensions to protoc 'Descriptor' type in order to define options
-// inside a .proto file.
-//
-// Protocol Buffers extension number registry
-// --------------------------------
-// Project: Nanopb
-// Contact: Petteri Aimonen <jpa@kapsi.fi>
-// Web site: http://kapsi.fi/~jpa/nanopb
-// Extensions: 1010 (all types)
-// --------------------------------
-
-extend google.protobuf.FileOptions {
- optional NanoPBOptions nanopb_fileopt = 1010;
-}
-
-extend google.protobuf.MessageOptions {
- optional NanoPBOptions nanopb_msgopt = 1010;
-}
-
-extend google.protobuf.EnumOptions {
- optional NanoPBOptions nanopb_enumopt = 1010;
-}
-
-extend google.protobuf.FieldOptions {
- optional NanoPBOptions nanopb = 1010;
-}
-
-
diff --git a/prebuilt/system/etc/sensors/proto/qti_gravity.proto b/prebuilt/system/etc/sensors/proto/qti_gravity.proto
deleted file mode 100644
index 1348f23..0000000
--- a/prebuilt/system/etc/sensors/proto/qti_gravity.proto
+++ /dev/null
@@ -1,53 +0,0 @@
-// @file qti_gravity.proto
-//
-// Defines standard message types for the QTI Gravity Proto
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_gravity.proto";
-
-enum qti_gravity_msgid
-{
- option (nanopb_enumopt).long_names = false;
- QTI_GRAVITY_MSGID_QTI_GRAVITY_MOTION_DATA_EVENT = 1029;
-}
-
-// Device Motion State detected by the gravity sensor
-enum qti_gravity_device_motion_state
-{
- option (nanopb_enumopt).long_names = false;
-
- // Device motion state is unknown
- QTI_GRAVITY_DEVICE_MOTION_STATE_UNKNOWN = 0;
-
- // Device is at absolute rest, an example of which
- // would be lying undisturbed on a desk
- QTI_GRAVITY_DEVICE_MOTION_STATE_ABS_REST = 1;
-
- // Device is at relative rest, an example of which
- // would be held steady in the user hand undergoing
- // no orientation change
- QTI_GRAVITY_DEVICE_MOTION_STATE_REL_REST = 2;
-
- // Device is in motion
- QTI_GRAVITY_DEVICE_MOTION_STATE_MOTION = 3;
-}
-
-// Configuration Message
-// Used to either request for a certain configuration of the qti gravity sensor or
-// alter an already existing configuration of the qti gravity sensor
-// Uses sns_std_sensor_config defined in sns_std_sensor.proto
-// The message field definitions are as follows:
-// 1) float sample_rate
-// containing the required sample rate of the qti gravity sensor in hertz
-
-// Data Message
-// Output data event generated by the qti gravity sensor.
-message qti_gravity_motion_data_event
-{
- // Device motion state detected using the gravity vector
- required qti_gravity_device_motion_state device_motion_state = 1 [default=QTI_GRAVITY_DEVICE_MOTION_STATE_UNKNOWN];
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_accel.proto b/prebuilt/system/etc/sensors/proto/sns_accel.proto
deleted file mode 100644
index 0d5bb88..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_accel.proto
+++ /dev/null
@@ -1,103 +0,0 @@
-// @file sns_accel.proto
-//
-// Defines the API for Accelerometer Sensors.
-// All Accelerometer Sensor drivers are required to comply with this API.
-// Any new functionality for Accelerometer Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_std_event_gated_sensor.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Accelerometer Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "accel".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute values in mg/LSB unit.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in +/-g unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Accelerometer Sensor handles the sns_std_sensor_config
-// message request with msgid SNS_STD_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG
-// for all non-gated stream enable/update requests.
-// 2. The Accelerometer Sensor handles the sns_std_sensor_config
-// message request with msgid SNS_STD_EVENT_GATED_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG
-// for all gated stream enable/update requests.
-// a. Accelerometer stream is gated on the motion detection feature
-// available on most accel hardware. This feature is published via the
-// "motion_detect" Sensor by the same driver library as "accel" Sensor.
-// b. If "motion_detect" is not supported then the Sensor does not support
-// stream gating. Any gated client request is rejected in this case.
-// 3. The Accelerometer Sensor uses batching_period item in
-// sns_std_request as the requested batching rate to determine
-// hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Accelerometer Sensor publishes acceleration data stream events
-// using the sns_std_sensor_event message.
-// 2. Each stream event contains three output data fields where data is
-// in m/s2 units and is factory calibrated.
-// 3. Data in the stream is adjusted to Android coordinate system relative to a
-// mobile device held with screen facing the user in it's natural orientation:
-// X-axis: parallel to the screen pointing to the right
-// Y-axis: parallel to the screen pointing to the top
-// Z-axis: perpendicular to the screen pointing towards the user
-// This conforms to the mobile device axes orientation as specified by the
-// Android Sensor API.
-// 4. Data in the stream event is ordered as:
-// data[0] = X-axis
-// data[1] = Y-axis
-// data[2] = Z-axis
-// 5. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 6. The Accelerometer Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 7. The Accelerometer Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and comp_matrix fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-// 8. When all outstanding requests to the Sensor are gated requests and if the
-// "motion_detect" Sensor is enabled then the accel Sensor stops generating
-// output events.
-// a. When motion detect interrupt fires:
-// - All existing accel gated stream requests are converted to non-gated
-// stream requests.
-// The accel Sensor publishes an event with message ID
-// SNS_STD_EVENT_GATED_SENSOR_MSGID_GATED_REQ_CONVERTED_TO_NON_GATED to
-// to indicate this change to it's gated clients.
-// - The accel Sensor resumes generating output to all clients.
-// So in effect motion_detect Sensor and accel gated Sensor stream have
-// a one shot behavior.
-// b. The Sensor resumes generating output events if motion detect interrupt
-// is disabled potentially due to a new non-gated accel stream request or
-// the request to motion_detect Sensor is disabled.
-// 9. When all outstanding requests to the Sensor are gated requests but if
-// "motion_detect" Sensor is not enabled then the Sensor continues to generate
-// output events.
-
-// Handling self-test requests:
-// 1. The Accelerometer Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Accelerometer Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Accelerometer Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Accelerometer Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_accel_cal.proto b/prebuilt/system/etc/sensors/proto/sns_accel_cal.proto
deleted file mode 100644
index bbe04a0..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_accel_cal.proto
+++ /dev/null
@@ -1,32 +0,0 @@
-// @file sns_accel_cal.proto
-//
-// Defines message types for the Accel Calibration Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_cal.proto";
-
-// The Accel Calibration Sensor determines the calibration parameters
-// for accel sensor
-
-// Accel Calibration Sensor Attributes:
-// - SNS_STD_SENSOR_ATTRID_TYPE: "accel_cal"
-// - SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG message ID is used to
-// enable the sensor
-// - SNS_CAL_MSGID_SNS_CAL_RESET message ID is used to reset the algorithm
-// and any previously determined calibration parameters.
-
-// Stream Events:
-// - SNS_CAL_MSGID_SNS_CAL_EVENT message ID is used to report calibration
-// parameters to the client of the sensor. The sns_cal_event message as
-// defined in sns_cal.proto is used to report this data event where the
-// units for the bias field in the message are in rad / s
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_ambient_light.proto b/prebuilt/system/etc/sensors/proto/sns_ambient_light.proto
deleted file mode 100644
index 09cceff..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ambient_light.proto
+++ /dev/null
@@ -1,73 +0,0 @@
-// @file sns_ambient_light.proto
-//
-// Defines the API for Ambient Light Sensors.
-// All Ambient Light Sensor drivers are required to comply with this API.
-// Any new functionality for Ambient Light Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Ambient Light Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "ambient_light".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in Lux/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in Lux unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Ambient Light Sensor supports both streaming and on-change
-// modes and the operating mode is configured in the Registry.
-// 2. The streaming Ambient Light Sensor handles the sns_std_sensor_config
-// request for all stream enable/update requests.
-// 3. The on-change Ambient Light Sensor handles the
-// SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG request for
-// all stream enable/update requests.
-// 4. In on-change mode the Sensor uses interrupt operation and reports
-// samples for only significant change in ambient light.
-// Example: +/- 10% change.
-
-// Handling stream events:
-// 1. The Ambient Light Sensor publishes current illumination data stream
-// events using the sns_std_sensor_event message.
-// 2. Each stream event contains two output data fields where data is
-// factory calibrated and ordered as:
-// data[0] = ambient light in Lux
-// data[1] = raw ADC value associated with data[0]
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Ambient Light Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Ambient Light Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new request.
-
-// Handling self-test requests:
-// 1. The Ambient Light Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Ambient Light Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API. The factory test for Ambient Light Sensor calibrates
-// the sensor such that it's output Lux value is comparable to a standard
-// Luxmeter output in any lighting condition.
-// 3. The Ambient Light Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Ambient Light Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_ambient_temperature.proto b/prebuilt/system/etc/sensors/proto/sns_ambient_temperature.proto
deleted file mode 100644
index 6f8b8df..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ambient_temperature.proto
+++ /dev/null
@@ -1,68 +0,0 @@
-// @file sns_ambient_temperature.proto
-//
-// Defines the API for Ambient Temperature Sensors.
-// All Ambient Temperature Sensor drivers are required to comply with this API.
-// Any new functionality for Ambient Temperature Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Ambient Temperature Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "ambient_temperature".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in degrees Celsius/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in degrees Celsius unit.
-// 4. The ambient_temperature sensor is an on-change sensor.
-// 5. The SNS_STD_SENSOR_ATTRID_RATES attribute is not applicable
-// since this is an on-change sensor.
-// 6. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Ambient Temperature Sensor handles the SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// message ID for all stream enable/update requests.
-// 2. If the physical sensor supports hardware FIFO then the Ambient Temperature
-// Sensor uses batching_period item in sns_std_request as the requested
-// batching rate to determine hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Ambient Temperature Sensor publishes data stream events using the
-// sns_std_sensor_event message.
-// 2. Each stream event contains one output data field where data is
-// factory calibrated and ordered as:
-// data[0] = Ambient Temperature data in degrees Celsius
-// 3. Each stream event publishs an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Ambient Temperature Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Ambient Temperature Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The Ambient Temperature Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Ambient Temperature Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Ambient Temperature Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Ambient Temperature Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_amd.proto b/prebuilt/system/etc/sensors/proto/sns_amd.proto
deleted file mode 100644
index 1e3f967..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_amd.proto
+++ /dev/null
@@ -1,50 +0,0 @@
-// @file sns_amd.proto
-//
-// Defines message types for the Absolute Motion Detector (AMD) Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// AMD calculates motion and stationary states. AMD will initially start in an
-// unknown state, and later transition to motion or stationary.
-
-// AMD Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "amd"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for AMD Sensor
-enum sns_amd_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_AMD_MSGID_SNS_AMD_EVENT = 772;
-}
-
-enum sns_amd_event_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_AMD_EVENT_TYPE_UNKNOWN = 0;
- SNS_AMD_EVENT_TYPE_STATIONARY = 1;
- SNS_AMD_EVENT_TYPE_MOTION = 2;
-}
-
-message sns_amd_event
-{
- // AMD motion state
- required sns_amd_event_type state = 1 [default = SNS_AMD_EVENT_TYPE_UNKNOWN];
-}
-
-// Stream events:
-//
-// The sns_amd_event message is used to publish updated state
-//
-// AMD does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_aont.proto b/prebuilt/system/etc/sensors/proto/sns_aont.proto
deleted file mode 100644
index de4b136..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_aont.proto
+++ /dev/null
@@ -1,37 +0,0 @@
-// @file sns_aont.proto
-//
-// Defines message types for the AONT(Always On Test) Sensor.
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The Always On Test Sensor runs an Always On sensors usecase for stability test coverage
-
-// Always On Test Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "always_on_test"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Stream Events:
-enum sns_aont_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_AONT_MSGID_SNS_AONT_DATA = 1024;
-}
-
-// Data Message
-// Output data event generated by the aont sensor.
-message sns_aont_data
-{
- // AONT output - Accel data along axis x,y,z in m/s2
- repeated float aont = 1 [(nanopb).max_count = 3];
-}
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_async_com_port.proto b/prebuilt/system/etc/sensors/proto/sns_async_com_port.proto
deleted file mode 100644
index b9d492f..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_async_com_port.proto
+++ /dev/null
@@ -1,166 +0,0 @@
-// @file sns_async_com_port.proto
-//
-// Defines standard message types for the Async Com Port
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std.proto";
-
-// Asynchronous Com Port
-//
-// The Asynchronous Com Port provides access to buses like I2C, I3C, SPI and others.
-// A complete list of all buses available in the sns_async_com_port_bus_type enum.
-//
-// The Asynchronous Com Port can perform read and write operations on these buses
-// asynchronously. This is the recommended way to perform large bus reads (example:
-// reading a large FIFO buffer). This file describes the use of the async com port
-// (ascp) API.
-//
-// First, the client must configure the port using the sns_async_com_port_config
-// message.
-//
-// To perform one or more read or write operations, the client should send the
-// sns_async_com_port_vector_rw message.
-//
-// A single sns_async_com_port_vector_rw message can contain multiple
-// sns_async_com_port_vector messages, the async com port will efficiently perform
-// all the transactions that are part of the parent sns_async_com_port_vector_rw
-// message. The results of the transaction will be sent as an sns_async_com_port_vector_rw
-// event.
-//
-// The async com port will internally manage efficiently opening and closing the
-// bus power lines and clock settings. The async com port can safely be used along
-// with the synchronous com port service.
-//
-// To help with encoding and decoding the sns_async_com_port_vector_rw messages,
-// utility functions are provided in sns_async_com_port_pb_utils.h
-
-
-// The operation to be performed by the async com port
-enum sns_async_com_port_operation_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_ASYNC_COM_PORT_OPERATION_TYPE_READ = 0;
- SNS_ASYNC_COM_PORT_OPERATION_TYPE_WRITE = 1;
-}
-
-// The bus type to be accessed by the async com port
-enum sns_async_com_port_bus_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // I2C bus:
- SNS_ASYNC_COM_PORT_BUS_TYPE_I2C = 0;
-
- // SPI bus:
- SNS_ASYNC_COM_PORT_BUS_TYPE_SPI = 1;
-
- // I3C bus, standard data rate:
- SNS_ASYNC_COM_PORT_BUS_TYPE_I3C_SDR = 3;
-
- // I3C bus, double data rate:
- SNS_ASYNC_COM_PORT_BUS_TYPE_I3C_HDR_DDR = 4;
-
- // I3C bus, legacy I2C device attached to I3C bus:
- SNS_ASYNC_COM_PORT_BUS_TYPE_I3C_I2C_LEGACY = 5;
-}
-
-// The registry address type to be used by async com port
-enum sns_async_com_port_reg_addr_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_ASYNC_COM_PORT_REG_ADDR_TYPE_8_BIT = 0;
- SNS_ASYNC_COM_PORT_REG_ADDR_TYPE_16_BIT = 1;
- SNS_ASYNC_COM_PORT_REG_ADDR_TYPE_32_BIT = 2;
-}
-
-// Configuration message
-message sns_async_com_port_config
-{
- // The bus type
- required sns_async_com_port_bus_type bus_type = 1;
-
- // Slave Address for I2C.
- // Dynamic slave address for I3C.
- // Chip Select for SPI.
- required fixed32 slave_control = 2;
-
- // Register address type for the slave
- required sns_async_com_port_reg_addr_type reg_addr_type = 3;
-
- // Minimum bus clock supported by slave in kHz
- required fixed32 min_bus_speed_kHz = 4;
-
- // Maximum bus clock supported by slave in kHz
- required fixed32 max_bus_speed_kHz = 5;
-
- // Platform bus instance number (BLSP number)
- required fixed32 bus_instance = 6;
-}
-
-// A single read or write operation.
-message sns_async_com_port_vector
-{
- // Read or write operation
- required sns_async_com_port_operation_type operation = 1;
-
- // Register address
- required fixed32 reg_addr = 2;
-
-
- // Number of bytes to read or write.
- // The async com port will ignore this field for a write
- // operation and use the size of the buffer present in the message.
- //
- // For events generated by the async com port, this field will always match the
- // size of the buffer when it is present.
- optional fixed32 num_bytes = 3;
-
- // Buffer
- // The async com port will ignore this field in a request for a read operation.
- optional bytes buffer = 4;
-}
-
-
-// A collection of read and write operations
-message sns_async_com_port_vector_rw
-{
- // Number of operations
- required fixed32 num_vectors = 1;
-
- // Read/write operations
- repeated sns_async_com_port_vector vectors = 2;
-}
-
-// Notifies the client of an error during a transaction
-message sns_async_com_port_error
-{
- // Registry address
- required fixed32 reg_addr = 1;
-
- // Number of bytes that was to be read/written
- required fixed32 num_bytes = 2;
-
- // Error code
- required sns_std_error error_code = 3;
-}
-
-
-// Message IDs
-enum sns_async_com_port_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_ASYNC_COM_PORT_MSGID_SNS_ASYNC_COM_PORT_CONFIG = 512;
- SNS_ASYNC_COM_PORT_MSGID_SNS_ASYNC_COM_PORT_VECTOR_RW = 1024;
- SNS_ASYNC_COM_PORT_MSGID_SNS_ASYNC_COM_PORT_ERROR = 1025;
- SNS_ASYNC_COM_PORT_MSGID_SNS_ASYNC_COM_PORT_REG = 1026;
-}
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_basic_gestures.proto b/prebuilt/system/etc/sensors/proto/sns_basic_gestures.proto
deleted file mode 100644
index dfec6ba..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_basic_gestures.proto
+++ /dev/null
@@ -1,101 +0,0 @@
-// @file sns_basic_gestures.proto
-//
-// Defines message types for the the basic_gestures sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-// Basic Gestures algorithm provides the ability to detect a Push, Pull,
-// or Shake gesture.
-// Basic Gestures reports "Axis Unknown", when the direction of a shake cannot
-// be reliably determined.
-
-// Basic gestures Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "basic_gestures"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_BASIC_GESTURES_MSGID_SNS_BASIC_GESTURES_CONFIG is used to enable the sensor
-
-// Message IDs for Basic gestures Sensor
-enum sns_basic_gestures_msgid
-{
- option (nanopb_enumopt).long_names = false;
- SNS_BASIC_GESTURES_MSGID_SNS_BASIC_GESTURES_CONFIG = 512;
- SNS_BASIC_GESTURES_MSGID_SNS_BASIC_GESTURES_EVENT = 1024;
-}
-//To mask Basic gesture algorithm output states
-enum sns_basic_gestures_event_mask
-{
- option (nanopb_enumopt).long_names = false;
- // For masking push and pull states
- SNS_BASIC_GESTURES_EVENT_MASK_PUSH_AND_PULL = 1;
- // For masking shake left and right states
- SNS_BASIC_GESTURES_EVENT_MASK_SHAKE_LEFT_AND_RIGHT = 2;
- // For masking shake top and bottom states
- SNS_BASIC_GESTURES_EVENT_MASK_SHAKE_TOP_AND_BOTTOM = 4;
- //For masking shake other state
- SNS_BASIC_GESTURES_EVENT_MASK_SHAKE_OTHER = 8;
-}
-// Device Basic gesture detected by Basic gestures sensor
-enum sns_basic_gestures_event_type
-{
- option (nanopb_enumopt).long_names = false;
- //Phone is pulled away from the user in a direction perpendicular to the screen
- SNS_BASIC_GESTURES_EVENT_TYPE_PUSH = 1;
- //Phone is pulled toward the user in a direction perpendicular to the screen
- SNS_BASIC_GESTURES_EVENT_TYPE_PULL = 2;
- //Phone is shaken toward the left
- SNS_BASIC_GESTURES_EVENT_TYPE_SHAKE_LEFT = 3;
- //Phone is shaken toward the right
- SNS_BASIC_GESTURES_EVENT_TYPE_SHAKE_RIGHT = 4;
- //Phone is shaken toward the top
- SNS_BASIC_GESTURES_EVENT_TYPE_SHAKE_TOP = 5;
- //Phone is shaken toward the bottom
- SNS_BASIC_GESTURES_EVENT_TYPE_SHAKE_BOTTOM = 6;
- //Phone is shaken, but phone shake direction cannot be clearly determined
- SNS_BASIC_GESTURES_EVENT_TYPE_SHAKE_OTHER = 7;
-}
-// Event Message
-// Output data event generated by the basic_gestures sensor.
-// Default values of optional fields added in registry
-message sns_basic_gestures_config
-{
- //Sleep time in seconds
- optional float sleep = 1;
- //Push threshold m/s/s(default = 1.5G),where G=9.81188
- //min_push_threshold:1G, max_push_threshold:5G
- optional float push_threshold = 2;
- //Pull threshold m/s/s (default = 1.5G)
- //min_pull_threshold:1G, max_pull_threshold:5G
- optional float pull_threshold = 3;
- //Shake threshold m/s/s(default = 1.5G)
- //min_shake_threshold:1G, max_shake_threshold:5G
- optional float shake_threshold = 4;
- //For masking output events.
- //By default, All states reported.
- //Client should use sns_basic_gestures_event_mask fields for masking,
- //specific events
- //Example: If client doesn't want push and pull events,then,
- //client updates event_mask with SNS_BASIC_GESTURES_EVENT_MASK_PUSH_AND_PULL
- //event_mask |= SNS_BASIC_GESTURES_EVENT_MASK_PUSH_AND_PULL;
- optional bytes event_mask = 5;
-}
-
-// Event Message
-// Output data event generated by the basic_gestures sensor.
-message sns_basic_gestures_event
-{
- // basic_gestures sensor state info
- required sns_basic_gestures_event_type state=1;
-}
-
-// Stream events:
-//
-// The sns_basic_gestures_event message is used to publish updated state
-//
-// Basic_gestures sensor does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_bring_to_ear.proto b/prebuilt/system/etc/sensors/proto/sns_bring_to_ear.proto
deleted file mode 100644
index a8937f0..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_bring_to_ear.proto
+++ /dev/null
@@ -1,40 +0,0 @@
-// @file sns_bring_to_ear.proto
-//
-// Defines message types for the the Bring_To_Ear sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// Bring_to_ear sensor detects bring to ear event,
-// When a device has been held in a face-up position,
-// afterwhich the device is brought to the user's ear, with the top of the device facing upwards.
-
-// Bring to ear Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "bring_to_ear"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-
-// ## Event Message: SNS_BRING_TO_EAR_MSGID_SNS_BRING_TO_EAR_EVENT
-// Reported upon new detection of bring_to_ear event
-
-
-// Message IDs for Bring to ear Sensor
-enum sns_bring_to_ear_msgid
-{
- option (nanopb_enumopt).long_names = false;
- // Empty Message
- SNS_BRING_TO_EAR_MSGID_SNS_BRING_TO_EAR_EVENT = 1024;
-}
-
-// Stream events:
-//
-// The sns_bring_to_ear_event message is used to publish updated state
-//
-// Bring_to_ear sensor does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_cal.proto b/prebuilt/system/etc/sensors/proto/sns_cal.proto
deleted file mode 100644
index 0c43669..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_cal.proto
+++ /dev/null
@@ -1,118 +0,0 @@
-// @file sns_cal.proto
-//
-// Defines standard message types pertaining to calibration
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// For dynamic calibration supported by Calibration Sensors:
-// Client will use the standard on change config message id to enable
-// Calibration Sensor. Calibration algorithms are inherently on change in
-// behavior.
-
-// For both dynamic calibration supported by Calibration Sensors &
-// factory calibration supported by Physical Sensors:
-// Client can send an empty request with the msg id for reset
-// to reset the calibration parameters.
-enum sns_cal_msgid
-{
- option (nanopb_enumopt).long_names = false;
- SNS_CAL_MSGID_SNS_CAL_RESET = 512;
- SNS_CAL_MSGID_SNS_CAL_EVENT = 1022;
-}
-
-// Calibration Event
-// Used as an output data event by Calibration Sensors to convey
-// dynamic calibration estimates and
-// as a config event by Physical Sensors to convey factory calibration
-// being applied
-//
-// A) The data field of the sns_cal_event message
-//
-// 1) float bias[] (Nx1 vector)
-// The zero bias (B) correction subtracted to get calibrated sample.(Nx1 vector)
-//
-// 2) float scale_factor (Nx1 vector)
-// The scaling (SF) to be done before doing any bias correction.
-//
-// 3) float comp_matrix (NxN matrix)
-// The compensation matrix (CM). The matrix elements are in row major order ie:
-// CM = CM0 CM1 CM2
-// CM3 CM4 CM5
-// CM6 CM7 CM8
-//
-// The calibrated sample (Sc) is computed as following.
-//
-// if SF, B and CM are available,
-//
-// Sc = CM * ((S .* SF) - B)
-//
-// if only B and CM are available,
-//
-// Sc = CM * (S - B)
-//
-// if only SF and B are available,
-//
-// Sc = ((S .* SF) - B)
-//
-// if only SF is available,
-//
-// Sc = S .* SF
-//
-// if only B is available,
-//
-// Sc = (S - B)
-//
-// if only CM is available
-//
-// Sc = CM * S
-//
-// where:
-// Sc = Calibrated sensor sample
-// S = Sensor sample (Nx1 vector)
-// SF = Scaling factor to be applied to S
-// CM = compensation_matrix
-// B = bias
-// "*" represents matrix multiplication
-// ".*" represents element-by-element multiplication
-//
-//
-// B) The status field of the sns_std_sensor_event message contains
-// the quality of calibration defined by sns_std_sensor_sample_status as
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE = 0; // Sample is unreliable.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_LOW = 1; // Sample is low accuracy.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_MEDIUM = 2;// Sample is medium accuracy.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH = 3; // Sample is high accuracy.
-
-message sns_cal_event
-{
- //Optional bias value
- //If no bias is being published this will be of size 0.
- //Generic for different axes biases.
- //Size is defined by axes value inherently.
- repeated float bias = 1;
-
- //Optional scaling factor
- //If no scaling factor is published this will be of size 0.
- //Size if published is has to be equal to the axes of the data
- repeated float scale_factor = 2;
-
- //If no CM is being published this will be of size 0.
- //Optional CM values .
- //Size if published should be equal to matrix of size [axes*axes]
- repeated float comp_matrix = 3;
-
- // Event sample status.
- required sns_std_sensor_sample_status status = 4 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-
- // Calibration ID, a unique identifier for the calibration set being used
- // As an example, could be set when there are distinct calibration sets for different
- // device modes being maintained
- optional fixed32 cal_id = 5;
-}
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_ccd_ttw.proto b/prebuilt/system/etc/sensors/proto/sns_ccd_ttw.proto
deleted file mode 100644
index e26d1cf..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ccd_ttw.proto
+++ /dev/null
@@ -1,35 +0,0 @@
-// @file sns_ccd_ttw.proto
-//
-// Defines message types for the ccd_ttw Sensor.
-//
-// Copyright (c) 2017-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The CCD ttw (tilt_to_wake) detects substantial phone rotation (gesture) within
-// limited period ending in a specific range of the pitch and roll angles.
-
-// tilt_to_wake Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "ccd_ttw"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for ccd_ttw Sensor
-enum sns_ccd_ttw_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_CCD_TTW_MSGID_SNS_CCD_TTW_EVENT = 775;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_CCD_TTW_MSGID_SNS_CCD_TTW_EVENT is used to
-// publish ccd_ttw event
-//
-// ccd_ttw does not publish configuration events.
diff --git a/prebuilt/system/etc/sensors/proto/sns_ccd_walk.proto b/prebuilt/system/etc/sensors/proto/sns_ccd_walk.proto
deleted file mode 100644
index 0a100c1..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ccd_walk.proto
+++ /dev/null
@@ -1,40 +0,0 @@
-// @file sns_ccd_walk.proto
-//
-// Defines message types for the Walk CCD.
-//
-// Copyright (c) 2017-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// CCD Walk calculates a walk state.
-// When a walk is detected, the sensor will send one WALK event.
-// To send additional walk events, the sensor must be re-armed with the
-// SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG event again.
-//
-// No events are generated when not in the walk state.
-
-// CCD Walk Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "ccd_walk"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_SINGLE_OUTPUT
-
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Walk Sensor
-enum sns_ccd_walk_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_CCD_WALK_MSGID_SNS_CCD_WALK_EVENT = 773;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_CCD_WALK_MSGID_SNS_CCD_WALK_EVENT is used to
-// publish the walk event.
-//
-// Walk does not publish configuration events.
diff --git a/prebuilt/system/etc/sensors/proto/sns_client.proto b/prebuilt/system/etc/sensors/proto/sns_client.proto
deleted file mode 100644
index 75fda30..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_client.proto
+++ /dev/null
@@ -1,116 +0,0 @@
-// @file sns_client.proto
-//
-// Defines the interface between external clients and the Sensors QMI Client
-// Manager. The Client Manager is the primary path for external clients
-// to communicate with the SSC.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std.proto";
-import "sns_std_type.proto";
-
-// Message IDs
-//
-// Message IDs uniquely identify a particular message amongst all message
-// supported by a Sensor, both requests and events; they need not be unique
-// between different Sensors. IDs are subdivided into several reserved pools.
-// These reservations are made so that Framework components can appropriately
-// optimize their processing.
-//
-// Reserved for Framework use only:
-// 0-127 - Request Messages
-// 128-255 - Non-recurrent events (configuration updates, one-time events, etc)
-// 256-511 - Recurrent and/or periodic events (e.g. sensor samples)
-//
-// Sensor use:
-// 512-767 - Request messages
-// 768-1023 - Non-recurrent events
-// 1024-1536 - Recurrent events
-//
-// Note that messages serving as request messages can also be sent as
-// configuration events back to the client (with the same ID). While batching
-// data for a non-wakeup client, if the AP is in suspend and all batching space
-// exhausted, the oldest recurrent events may be dropped.
-
-// Framework-defined message IDs:
-enum sns_client_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Disable request explicitly handled only on the client interface.
- SNS_CLIENT_MSGID_SNS_CLIENT_DISABLE_REQ = 10;
-
- // NOTE: 120-127 Are reserved
-}
-
-enum sns_client_delivery {
- option (nanopb_enumopt).long_names = false;
-
- // Send events whenever available (at sample rate or batch period)
- // - If a batch_period larger than system capacity is requested, all data
- // will be sent upon capacity exhaustion.
- // - The flush_period will be effectively ignored, as unsent batched
- // data will not accrue in the buffer.
- SNS_CLIENT_DELIVERY_WAKEUP = 0;
- // Send events only when client processor is awake; batch otherwise. Once
- // the target processor exits suspend, any/all pending events will be sent.
- SNS_CLIENT_DELIVERY_NO_WAKEUP = 1;
-}
-
-
-// Request Message
-message sns_client_request_msg {
- // SUID associated with this request; intended destination
- required sns_std_suid suid = 1;
-
- // See comment above
- required fixed32 msg_id = 2;
-
- // Whether to wakeup the client processor (if it is in suspend), when an
- // event is generated and ready to send. The Qualcomm Client Manager will
- // enforce these criteria for all clients; this information is made available
- // to sensors for optimization purposes only.
- message suspend_config {
- // Processor on which the client resides; If a flush occurs for one client
- // on an external processor, all clients will receive a flush of data.
- required sns_std_client_processor client_proc_type = 1 [default = SNS_STD_CLIENT_PROCESSOR_APSS];
-
- // Whether to send events while the specified processor is in suspend.
- required sns_client_delivery delivery_type = 2 [default = SNS_CLIENT_DELIVERY_WAKEUP];
-
- //The client expects that, when the message with an id specified in this list
- //is generated, the message should only be delivered to the client if data
- //is already being delivered to the processor mentioned above.
- repeated fixed32 nowakeup_msg_ids = 3;
- }
- required suspend_config susp_config = 3;
-
- // Base message payload; contents will be partially specified by Sensor developer
- required sns_std_request request = 4;
-}
-
-message sns_client_event_msg {
- // SUID associated with this Event; source of data
- required sns_std_suid suid = 1;
-
- // An event generated by a Sensor; used within sns_client_event_msg and SensorBatchMessage
- message sns_client_event {
- // See comment above
- required fixed32 msg_id = 1;
-
- // Timestamp associated with this event
- // For most events, this timestamp is specified by the Sensor.
- // For events generated by the Framework (such as configuration updates or
- // error events), this timestamp refers to the time at which the event was
- // created.
- required fixed64 timestamp = 2;
-
- // Dynamic length payload, containing the actual data/event
- // This payload will need to be decoded separately, using the Sensor-specific
- // header file
- required bytes payload = 3;
- }
- repeated sns_client_event events = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_cmc.proto b/prebuilt/system/etc/sensors/proto/sns_cmc.proto
deleted file mode 100644
index 2bdb018..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_cmc.proto
+++ /dev/null
@@ -1,81 +0,0 @@
-
-// @file sns_cmc.proto
-//
-// Defines message types for the Coarse Motion Classifier (CMC) Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-
-// CMC Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "coarse_motion_classifier"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for CMC Sensor
-enum sns_cmc_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_CMC_MSGID_SNS_CMC_EVENT = 772;
-}
-
-// Gives the state which the algorithm is capable
-// of detecting
-enum sns_cmc_motion_state
-{
- option (nanopb_enumopt).long_names = false;
-
- // stated with 1 to match with algo where 0
- // is for UNKNOWN
- SNS_CMC_STATIONARY = 1;
- SNS_CMC_MOVE = 2;
- SNS_CMC_FIDDLE = 3;
- SNS_CMC_PEDESTRIAN = 4;
- SNS_CMC_VEHICLE = 5;
- SNS_CMC_WALK = 6;
- SNS_CMC_RUN = 7;
- SNS_CMC_BIKE = 8;
-}
-
-// Gives the information about the states represented
-// by sns_cmc_motion_state
-enum sns_cmc_motion_state_event
-{
- option (nanopb_enumopt).long_names = false;
- // when any state of any of the motion state cannot
- // be determined. The first event of first client will
- // typically have all states as SNS_MS_UNKNOWN
- SNS_MS_UNKNOWN = 0;
- // A given motion state is ACTIVE
- SNS_MS_ACTIVE = 1;
- // A given motion state is INACTIVE
- SNS_MS_INACTIVE = 2;
-}
-
-message sns_cmc_event
-{
- message data
- {
- // motion state by CMC
- required sns_cmc_motion_state ms_state = 1;
-
- // gives UNKNOWN/ACTIVE/INACTIVE information for the motion state
- required sns_cmc_motion_state_event ms_state_event = 2 [default = SNS_MS_UNKNOWN];
- }
-
- repeated data events = 1;
-}
-
-// Stream events:
-//
-// The sns_cmc_event message is used to publish updated state
-//
-// CMC does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_cmd.proto b/prebuilt/system/etc/sensors/proto/sns_cmd.proto
deleted file mode 100644
index 7221815..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_cmd.proto
+++ /dev/null
@@ -1,37 +0,0 @@
-// @file sns_cmd.proto
-//
-// Defines message types for the Continuous Motion Detector (CMD) Sensor.
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// CMD identified continuous motions such as vehicle and walk. CMD will initially start in an
-// unknown state, and later transition to motion or stationary.
-
-// CMD Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "cmd"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for CMD Sensor
-enum sns_cmd_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_CMD_MSGID_SNS_CMD_EVENT = 772;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_CMD_MSGID_SNS_CMD_EVENT is used to
-// publish CMD event
-//
-// CMD does not publish configuration events.
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_da_test.proto b/prebuilt/system/etc/sensors/proto/sns_da_test.proto
deleted file mode 100644
index 59ab8f4..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_da_test.proto
+++ /dev/null
@@ -1,56 +0,0 @@
-// @file sns_da_test.proto
-//
-// Defines the API for communicating with the Driver acceptance
-// test sensor.
-// This is to used by the linux command line partner application
-// to send string messages to the sns_da_test_sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_da_test_msgid {
- option (nanopb_enumopt).long_names = false;
- SNS_DA_TEST_MSGID_SNS_DA_TEST_REQ = 512;
- SNS_DA_TEST_MSGID_SNS_DA_TEST_LOG = 768;
- SNS_DA_TEST_MSGID_SNS_DA_TEST_EVENT = 1024;
-}
-
-//This message contains the test parameters as a single string in the format below
-//-testcase=<not_mandatory> -sample_rate=< any +tive value > -sensor=<data_type>
-//-duration=< any +tive value in seconds> -batch_period=<+tive value in seconds>
-message sns_da_test_req {
- optional string test_args = 1;
-}
-
-//This message contains any return data from the test driver including PASS/FAIL
-//msg. and explainations if applicable
-message sns_da_test_event {
- optional string test_event = 1;
-}
-
-// Sensor State log message
-// This definition is used by da_test sensor to log test
-// information when publishing sensor api event
-message sns_da_test_log {
- //Time elapsed between streaming start request time and first sample received
- required uint64 time_to_first_event = 1;
-
- //Time elapsed between streaming stop request time and last sample received
- required sfixed32 time_to_last_event = 2;
-
- //Time when last sample was received
- required uint64 sample_ts = 3;
-
- //Total number of samples received
- required uint32 total_samples = 4;
-
- //time delta between samples avegraged over number of samples
- required uint32 avg_delta = 5;
-
- //configures sample rate received in the SNS_STD_SENSOR_PHYSICAL_CONFIG_EVENT
- required sfixed32 recvd_phy_config_sample_rate = 6;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_dae.proto b/prebuilt/system/etc/sensors/proto/sns_dae.proto
deleted file mode 100644
index 777bd82..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_dae.proto
+++ /dev/null
@@ -1,256 +0,0 @@
-// @file sns_dae.proto
-//
-// Defines all high-level messages sent to/from the Nano sensor environment
-//
-// Copyright (c) 2017,2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-import "sns_std_type.proto";
-import "sns_interrupt.proto";
-import "sns_async_com_port.proto";
-
-
-enum sns_dae_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // to initialize the nano sensor before it can be used
- SNS_DAE_MSGID_SNS_DAE_SET_STATIC_CONFIG = 600;
-
- // provides nano sensor with S4S config info after the initial S4S synch period
- SNS_DAE_MSGID_SNS_DAE_S4S_DYNAMIC_CONFIG = 601;
-
- // to start nano sensor streaming
- SNS_DAE_MSGID_SNS_DAE_SET_STREAMING_CONFIG = 602;
-
- // no message body
- // to flush FIFO data before changing ODR and/or WM
- // no data event will be generated
- SNS_DAE_MSGID_SNS_DAE_FLUSH_HW = 603;
-
- // no message body
- // to request nano sensor to generate data event from the available data
- // HW flush will NOT be done
- SNS_DAE_MSGID_SNS_DAE_FLUSH_DATA_EVENTS = 604;
-
- // no message body
- // to stop nano sensor streaming
- SNS_DAE_MSGID_SNS_DAE_PAUSE_SAMPLING = 605;
-
- // no message body
- // to stop S4S schedule
- SNS_DAE_MSGID_SNS_DAE_PAUSE_S4S_SCHED = 606;
-
- // response from DAE sensor for each request
- SNS_DAE_MSGID_SNS_DAE_RESP = 800;
-
- // message from DAE sensor to deliver all available data
- SNS_DAE_MSGID_SNS_DAE_DATA_EVENT = 1200;
-
- // message from DAE sensor to deliver unhandle interrupts
- SNS_DAE_MSGID_SNS_DAE_INTERRUPT_EVENT = 1201;
-}
-
-enum sns_dae_timestamp_type {
- // Unknown timestamp type
- SNS_DAE_TIMESTAMP_TYPE_UNKNOWN = 0;
-
- // The timestamp corresponds to an interrupt. Timestamp captured with hardware
- // timestamping engine
- SNS_DAE_TIMESTAMP_TYPE_HW_IRQ = 1;
-
- // The timestamp corresponds to an interrupt. Timestamp captured with software
- // within the interrupt handler
- SNS_DAE_TIMESTAMP_TYPE_SW_IRQ = 2;
-
- // The timestamp is the current system time when the data was read. The data
- // was read due to a system timer firing (for polling & S4S sensors)
- SNS_DAE_TIMESTAMP_TYPE_TIMER = 3;
-
- // The timestamp is the current system time when the data was read. The data
- // was read due to a flush command.
- SNS_DAE_TIMESTAMP_TYPE_SYSTEM_TIME = 4;
-}
-
-// S4S static information
-//
-// This contains S4S information which does not change during the life of the S4S sensor
-message sns_s4s_static_info {
- // Register address of the S4S ST command
- required int32 st_reg_addr = 1;
-
- // Optional data byte which needs to be sent along with ST
- optional int32 st_reg_data = 2;
-
- // Register address of the S4S DT command
- required int32 dt_reg_addr = 3;
-}
-
-
-// Triaxial sensor input to output axis conversion
-message sensor_to_phone_conversion {
-
- // input axis index (x=0, y=1, z=2)
- required uint32 ipaxis = 1;
-
- // output axis index the above input axis maps to
- required uint32 opaxis = 2;
-
- // whether the input needs to be negated when
- // translating to the output axis
- required bool invert = 3;
-}
-
-// Accel static informtaion
-//
-// Accel configuration setting that is not expected to change at run time
-message sns_accel_static_info {
-
- // Factory calibration: offset, in g's (DEPRECATED - moved to sns_accel_dynamic_info)
- repeated float offset_cal = 1 [(nanopb).max_count = 3, deprecated = true];
-
- // Factory calibration: scale factor (DEPRECATED - moved to sns_accel_dynamic_info)
- repeated float scale_cal = 2[(nanopb).max_count = 3, deprecated = true];
-
- // range in G
- required int32 accel_range = 3;
-
- // axis map to convert from sensor to phone
- repeated sensor_to_phone_conversion axis_map = 4 [(nanopb).max_count = 3];
-}
-
-
-// Accel dynamic informtaion
-//
-// This data may be updated each time the accel configuration changes
-message sns_accel_dynamic_info {
- // ODR
- required float odr = 1;
-
- // How many initial samples after ODR change are invalid
- required uint32 num_initial_invalid_samples = 2;
-
- // Factory calibration: offset, in g's
- repeated float offset_cal = 3 [(nanopb).max_count = 3];
-
- // Factory calibration: scale factor
- repeated float scale_cal = 4 [(nanopb).max_count = 3];
-
-}
-
-// Polling config info
-message sns_polling_config_info {
-
- // Absolute time, in 19.2MHz ticks since boot, at which to poll the sensor
- required fixed64 polling_offset = 1;
-
- // interval between polling
- required fixed64 polling_interval_ticks = 2;
-}
-
-// Sensor static configuration
-//
-// This data may not change for the life of the sensor, and should be configured
-// at initilization/boot time.
-message sns_dae_set_static_config {
-
- // name of the function table for the nano version of the physical sensor
- required string func_table_name = 1 [(nanopb).max_size = 32];
-
- // Operational mode of the sensor:
- // 0 --> Polling
- // 1 --> Interrupt
- // 2 --> IBI (I3C In Band Interrupt)
- required int32 interrupt = 2;
-
- // x/y/z axis map for this sensor (DEPRECATED - moved to sns_accel_static_info)
- repeated int32 axis_map = 3 [(nanopb).max_count = 3, deprecated = true];
-
- // irq_config required if interrupt == 1
- optional sns_interrupt_req irq_config = 4;
-
- // ibi_config required if interrupt == 2
- optional sns_ibi_req ibi_config = 8;
-
- // s4s_config required if sensor supports S4S
- optional sns_s4s_static_info s4s_config = 5;
-
- // port configuration
- required sns_async_com_port_config ascp_config = 6;
-
- // Only for accel sensors
- optional sns_accel_static_info accel_info = 7;
-}
-
-// S4S dynamic information
-//
-// This contains S4S information which may change with S4S configuration
-message sns_dae_s4s_dynamic_config {
-
- // Absolute time, in 19.2MHz ticks since boot, of the start of an S4S T_PH period
- required fixed64 ideal_sync_offset = 1;
-
- // Time, in 19.2MHz ticks, in one S4S T_PH period
- required fixed64 sync_interval = 2;
-
- // S4S resolution ratio (RR), as defined in the S4S spec. The final S4S RR will
- // be 2^-(11+resolution_ratio).
- required int32 resolution_ratio = 3;
-
- // Minimum time, in 19.2MHz ticks, after the S4S T_PH period to send ST/DT
- // messages. Will depend on clock accuracy of the sensor, as well as current
- // sync_interval
- required int32 st_delay = 4;
-}
-
-message sns_dae_set_streaming_config {
-
- // minimum number of samples between data events; may still receive fewer samples
- required uint32 dae_watermark = 1;
-
- // discard data older than this limit (relative to current system time)
- optional fixed64 data_age_limit_ticks = 2;
-
- // required for polling sensors
- optional sns_polling_config_info polling_config = 3;
-
- // Only for accel sensors
- optional sns_accel_dynamic_info accel_info = 4;
-
- // Expected number of bytes read from sensor for each call to the DAE environment
- // "get_data" driver function.
- // If not included, default value is 100 bytes.
- optional uint32 expected_get_data_bytes = 5;
-}
-
-message sns_dae_resp {
- // Message ID this error code is associated with
- required int32 msg_id = 1;
-
- // result of the request associated with this response
- required sns_std_error err = 2;
-}
-
-message sns_dae_data_event {
- // Timestamp: For interrupt based sensors, this is the timestamp of the IRQ.
- // For polling sensors, this is the timestamp of when get_data() was called
- required fixed64 timestamp = 1;
-
- // Timestamp type
- optional sns_dae_timestamp_type timestamp_type = 3;
-
- // Format of the sensor_data is vendor specific, and up to the nano sensor
- // implementation.
- required bytes sensor_data = 2;
-}
-
-message sns_dae_interrupt_event {
- // timestamp of the IRQ.
- required fixed64 timestamp = 1;
-
- // Format of registers are vendor specific, and up to the nano sensor implementation.
- required bytes registers = 2 [(nanopb).max_size = 8];
-}
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_data_acquisition_engine.proto b/prebuilt/system/etc/sensors/proto/sns_data_acquisition_engine.proto
deleted file mode 100644
index 21ef2c5..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_data_acquisition_engine.proto
+++ /dev/null
@@ -1,11 +0,0 @@
-// @file sns_data_acquisition_engine.proto
-//
-// Includes sns_dae.proto
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-import "sns_dae.proto";
diff --git a/prebuilt/system/etc/sensors/proto/sns_device_mode.proto b/prebuilt/system/etc/sensors/proto/sns_device_mode.proto
deleted file mode 100644
index 66b5efd..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_device_mode.proto
+++ /dev/null
@@ -1,61 +0,0 @@
-// @file sns_device_mode.proto
-//
-// Defines message types for the Device Mode Sensor.
-//
-// Copyright (c) 2017-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// DEVICE_MODE determine the current mode of the device
-
-// DEVICE_MODE Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "device_mode"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-// - Client must remove stream to disable the sensor
-
-// Message IDs for DEVICE_MODE Sensor
-enum sns_device_mode_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_DEVICE_MODE_MSGID_SNS_DEVICE_MODE_EVENT = 772;
-}
-
-enum sns_device_mode
-{
- option (nanopb_enumopt).long_names = false;
- SNS_DEVICE_MODE_UNKNOWN = 0;
- SNS_DEVICE_MODE_FLIP_OPEN = 1;
-}
-
-enum sns_device_state
-{
- option (nanopb_enumopt).long_names = false;
- SNS_DEVICE_STATE_INACTIVE = 0;
- SNS_DEVICE_STATE_ACTIVE = 1;
-}
-
-message sns_device_mode_event
-{
- message mode_spec {
- required sns_device_mode mode = 1;
-
- required sns_device_state state = 2;
- }
- // Device Mode
- repeated mode_spec device_mode = 1;
-}
-
-// Stream events:
-//
-// The sns_device_mode_event message is used to publish updated mode
-//
-// DEVICE_MODE does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_device_orient.proto b/prebuilt/system/etc/sensors/proto/sns_device_orient.proto
deleted file mode 100644
index d667df0..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_device_orient.proto
+++ /dev/null
@@ -1,57 +0,0 @@
-// @file sns_device_orient.proto
-//
-// Defines the API for the Device Orientation sensors
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// A device orientation sensor reports the current orientation of the device.
-//
-// Minor or transient rotations should not cause a new event to be reported,
-// and this sensor should only be implemented with the help of an accelerometer.
-// Moving the device to an orientation where the Z axis is vertical (either up
-// or down) should not cause a new event to be reported.
-
-// ## Device Orientation sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "device_orient"
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: SNS_DEVICE_ORIENT_MSGID_SNS_DEVICE_ORIENT_EVENT
-
-// Message IDs for Device Orientation Sensor
-enum sns_device_orient_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_DEVICE_ORIENT_MSGID_SNS_DEVICE_ORIENT_EVENT = 776;
-}
-
-enum sns_device_orient_event_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_DEVICE_ORIENT_EVENT_TYPE_UNKNOWN = -1;
- // Device is in default orientation (Y axis is vertical and points up)
- SNS_DEVICE_ORIENT_EVENT_TYPE_DEFAULT = 0;
- // Device is rotated 90 degrees counter-clockwise from default orientation
- // (X axis is vertical and points up)
- SNS_DEVICE_ORIENT_EVENT_TYPE_POS_1 = 1;
- // Device is rotated 180 degrees from default orientation (Y axis is
- // vertical and points down)
- SNS_DEVICE_ORIENT_EVENT_TYPE_POS_2 = 2;
- // Device is rotated 90 degrees clockwise from default orientation (X axis
- // is vertical and points down)
- SNS_DEVICE_ORIENT_EVENT_TYPE_POS_3 = 3;
-}
-
-message sns_device_orient_event
-{
- // Detected state
- required sns_device_orient_event_type state = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_diag.proto b/prebuilt/system/etc/sensors/proto/sns_diag.proto
deleted file mode 100644
index 5819ae4..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_diag.proto
+++ /dev/null
@@ -1,433 +0,0 @@
-// @file sns_diag.proto
-//
-// Defines log messages used by the sensors diag service
-//
-// Copyright (c) 2016-2019 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std.proto";
-import "sns_std_sensor.proto";
-import "sns_client.proto";
-
-// Batch Sample Type
-enum sns_diag_batch_sample_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // This is the only sample in the batch
- SNS_DIAG_BATCH_SAMPLE_TYPE_ONLY = 0;
-
- // This is the first sample of the batch
- SNS_DIAG_BATCH_SAMPLE_TYPE_FIRST = 1;
-
- // This is an intermediate sample of the batch
- SNS_DIAG_BATCH_SAMPLE_TYPE_INTERMEDIATE = 2;
-
- // This is the last sample of the batch
- SNS_DIAG_BATCH_SAMPLE_TYPE_LAST = 3;
-}
-
-// Sensor Interrupts
-enum sns_diag_interrupt
-{
- option (nanopb_enumopt).long_names = false;
-
- // Interrupt caused by detection of a threshold being
- // exceeded
- SNS_DIAG_INTERRUPT_THRESHOLD = 0;
-
- // Interrupt caused by detection of movement of the device
- SNS_DIAG_INTERRUPT_MOTION = 1;
-
- // Interrupt caused by detection of tilting of the device
- SNS_DIAG_INTERRUPT_TILT = 2;
-
- // Interrupt caused by detection of free fall
- SNS_DIAG_INTERRUPT_FREE_FALL = 3;
-
- // Interrupt caused by detection of double-tap
- SNS_DIAG_INTERRUPT_DOUBLE_TAP= 4;
-
- // Interrupt caused by detection of acceleration shock
- SNS_DIAG_INTERRUPT_SHOCK = 5;
-
- // Interrupt caused by CCD AMD
- SNS_DIAG_INTERRUPT_CCD_AMD = 6;
-
- // Interrupt caused by CCD WALK
- SNS_DIAG_INTERRUPT_CCD_WALK = 7;
-
- // Interrupt caused by CCD TILT
- SNS_DIAG_INTERRUPT_CCD_TILT = 8;
-
- // Interrupt caused by CCD TE0
- SNS_DIAG_INTERRUPT_CCD_TE0 = 9;
-
- // Interrupt caused by CCD TE1
- SNS_DIAG_INTERRUPT_CCD_TE1 = 10;
-
- // Interrupt caused by CCD TE2
- SNS_DIAG_INTERRUPT_CCD_TE2 = 11;
-}
-
-// Opaque Payload
-// This message defines the fields used to log an undefined payload
-message sns_diag_opaque_payload
-{
- required bytes payload = 1;
-}
-
-// Batch Sample
-// This message defines the fields used to log batched data.
-message sns_diag_batch_sample
-{
- // Indicates if the sample is the first, intermediate, last or only
- // sample of a batch
- required sns_diag_batch_sample_type sample_type = 1 [default = SNS_DIAG_BATCH_SAMPLE_TYPE_ONLY];
-
- // Timestamp of the sensor state data sample
- required fixed64 timestamp = 2;
-
- // Sensor state data sample
- repeated float sample = 3;
-
- // Data status.
- required sns_std_sensor_sample_status status = 4 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-// Sensor State Hardware Interrupt Log Packet
-// This message defines the fields used to log sensor state information
-// pertaining to hardware interrupts
-// This message is used as the payload field of sns_diag_sensor_log
-message sns_diag_sensor_state_interrupt
-{
- // Type of sensor hardware interrupt
- required sns_diag_interrupt interrupt = 1;
-
- // Timestamp when the interrupt occurred
- required fixed64 timestamp = 2;
-}
-
-// Sensor State Raw
-// This message defines the fields used to log sensor state information
-// pertaining to raw uncalibrated physical sensor data.
-// This message is used as the payload field of sns_diag_sensor_log
-message sns_diag_sensor_state_raw
-{
- repeated sns_diag_batch_sample sample = 1;
-}
-
-// Client API Response Message
-message sns_diag_client_resp_msg
-{
- // The error response sent to the client
- required sns_std_error error = 1;
-}
-
-// Client API log packet
-// This message defines the fields to log all
-// Request, Response and Event messages at the Client API
-// This message is used as the payload field of sns_diag_sensor_log
-message sns_diag_client_api_log
-{
- // The client id that identifies the client connection
- required fixed64 client_id = 1;
-
- // Data type of the source sensor
- required string src_sensor_type = 2;
-
- // The Client API log packet payload
- oneof client_api_log_payload
- {
- // Client API Request message as defined in sns_client.proto
- sns_client_request_msg request_payload = 100;
-
- // Client API Event message as defined in sns_client.proto
- sns_client_event_msg event_payload = 101;
-
- // Client API Response message as defined in sns_diag.proto
- sns_diag_client_resp_msg resp_payload = 102;
- }
-}
-
-// Sensor API log packet
-// This message defines the fields to log all Request and
-// Event messages at the Sensor API
-// This message is used as the payload field of sns_diag_sensor_log
-message sns_diag_sensor_api_log
-{
- // The message id of the message being logged
- required fixed32 message_id = 1;
-
- // Timestamp associated with this message
- required fixed64 timestamp = 2;
-
- // Data stream associated with this message
- optional fixed64 stream_id = 3;
-
- // The Sensor API log packet payload
- oneof sensor_api_log_payload
- {
- // Sensor API Event message containing sensor specific event message
- // as defined in the sensor's proto api file
- sns_diag_opaque_payload opaque_payload = 100;
-
- // Sensor API Request message as defined in sns_std.proto
- sns_std_request request_payload = 101;
- }
-}
-
-// Sensor log packet
-// This message defines the fields to log all sensor specific
-// messages. This includes Sensor API messages, Client API messages,
-// HW Interrupt messages, Sensor State messages
-message sns_diag_sensor_log
-{
- // Log ID for the log packet
- required fixed32 log_id = 1;
-
- // Timestamp when log packet.was generated
- required fixed64 timestamp = 2;
-
- // Sensor UID for the log packet
- required sns_std_suid suid = 3;
-
- // Data type provided by the Sensor UID
- required string sensor_type = 4;
-
- // The instance id of the sensor to which this
- // message was passed to or obtained from
- required fixed64 instance_id = 5;
-
- // The log packet payload
- oneof sensor_log_payload
- {
- // Sensor specific Sensor State Algo message
- sns_diag_opaque_payload opaque_payload = 100;
-
- // Sensor API message
- sns_diag_sensor_api_log sensor_api_payload = 101;
-
- // Client API message
- sns_diag_client_api_log client_api_payload = 102;
-
- // Sensor State Raw message
- sns_diag_sensor_state_raw sensor_state_raw_payload = 103;
-
- // Sensor State Hardware Interrupt message
- sns_diag_sensor_state_interrupt sensor_state_interrupt_payload = 104;
- }
-}
-
-// Sensor Instance Mapping Log Packet
-// This message defines the fields used to log sensor instance mapping
-// information. This message is used as the payload field of sns_diag_fw_log
-message sns_diag_instance_map_log
-{
- // The instance id of the source sensor instance
- required fixed64 src_instance_id = 1;
-
- // Array of destination Sensor Instance IDs or Sensor IDs that the
- // source sensor instance is feeding to.
- // If no destination instance ids are specified it signifies
- // deletion of the source instance
- repeated fixed64 dest_instance_id = 2;
-
- // Array of data stream ids that the
- // source sensor instance is feeding to
- repeated fixed64 stream_id = 3;
-}
-
-// Island mode states
-enum sns_diag_island_state
-{
- option (nanopb_enumopt).long_names = false;
-
- // In Island mode
- SNS_DIAG_ISLAND_STATE_IN_ISLAND_MODE = 0;
-
- // Not in Island Mode
- SNS_DIAG_ISLAND_STATE_NOT_IN_ISLAND_MODE = 1;
-
- // Island mode disabled
- SNS_DIAG_ISLAND_STATE_ISLAND_DISABLED = 2;
-}
-
-// Island mode transition Log Packet
-// This message defines the fields used to log
-// transitions into and out of island mode
-//
-// This log packet is generated each time the system transitions into or out
-// of island mode or when island mode is disabled or when triggered by
-// a request to the diag sensor
-//
-// This message is used as the payload field of sns_diag_fw_log
-message sns_diag_island_transition_log
-{
- // Timestamp of the transition
- //
- // When logpacket is triggered, this timestamp will retain
- // the timestamp when the current state became effective.
- required fixed64 timestamp = 1;
-
- // Island state after transition is completed
- required sns_diag_island_state island_state = 2;
-
- // User defined cookie
- // Used by test scripts to identify logs triggered
- // by messages sent to the SSC
- optional fixed64 cookie = 3;
-
- // Total time system spent in island since device boot(micro seconds)
- optional fixed64 total_island_time = 4;
-}
-
-// Island exit vote Log Packet
-// This message defines the fields used to log vote for island mode exits.
-//
-// This log packet is generated at each call to island_exit()
-message sns_diag_island_exit_vote_log
-{
- // Timestamp
- required fixed64 timestamp = 1;
-
- // SUID of the Sensor responsible for the vote
- optional sns_std_suid sensor = 2;
-}
-
-// Heap IDs
-enum sns_diag_heap_id
-{
- option (nanopb_enumopt).long_names = false;
-
- // Primary Heap
- SNS_DIAG_HEAP_ID_HEAP_MAIN = 0;
-
- // Island Heap
- SNS_DIAG_HEAP_ID_HEAP_ISLAND = 1;
-
- // PRAM Heap
- SNS_DIAG_HEAP_ID_HEAP_PRAM = 2;
-
- // EVENT Heap
- SNS_DIAG_HEAP_ID_HEAP_EVENT = 3;
-
- // BATCH Heap
- SNS_DIAG_HEAP_ID_HEAP_BATCH = 4;
-
- // Event buffer
- SNS_DIAG_HEAP_ID_EVENT_BUFFER = 100;
-}
-
-// Memory status Log Packet
-// This message defines the fields used to log the memory utilization
-// This log packet is generated when a request is sent to the diag sensor
-message sns_diag_mem_utilization_log
-{
- // Timestamp
- required fixed64 timestamp = 1;
-
- // Heap ID
- required sns_diag_heap_id heap_id = 2;
-
- // Total Memory
- required fixed32 total_memory = 3;
-
- // Used Memory
- required fixed32 used_memory = 4;
-
- // User defined cookie
- // Used by test scripts to identify logs triggered
- // by messages sent to the SSC
- optional fixed64 cookie = 5;
-}
-
-// Event Service status Log Packet
-// This message defines the fields used to log the memory utilization and
-// other statistics from the Event Service.
-// Used only for SW debug; *not guaranteed to be backward compatible*
-// This log packet is generated when a request is sent to the diag sensor
-message sns_diag_event_service_log
-{
- // Timestamp
- required fixed64 timestamp = 1;
-
- // User defined cookie
- // Used by test scripts to identify logs triggered
- // by messages sent to the SSC
- optional fixed64 cookie = 2;
-
- message heap_stats
- {
- enum sns_event_service_heap_id
- {
- SNS_EVENT_SERVICE_HEAP_ID_ISLAND = 0;
- SNS_EVENT_SERVICE_HEAP_ID_MAIN = 1;
- }
- // Heap ID
- required sns_event_service_heap_id heap_id = 1;
-
- // Total memory available in heap (in blocks)
- required fixed32 total_memory = 2;
-
- // Current memory consumption (in blocks)
- required fixed32 used_memory = 3;
-
- // Maximum memory consumption since last log packet (in blocks)
- required fixed32 max_memory = 4;
-
- // Total clusters available
- required fixed32 total_clusters = 5;
-
- // Current number of clusters in use
- required fixed32 used_clusters = 6;
-
- // Maximum in-use clusters since last log packet
- required fixed32 max_clusters = 7;
-
- // Number of allocation failues since the last DIAG log packet
- // If Island will result in island exit; else causes dropped samples
- required fixed32 alloc_failures = 8;
-
- // Largest event allocation since the last DIAG log packet (in bytes)
- required fixed32 max_size = 9;
- }
- repeated heap_stats stats = 3;
-}
-
-// Framework log packet
-// This message defines the fields to log all framework messages. This
-// includes memory, island, instance mapping messages.
-message sns_diag_fw_log
-{
- // Log ID for the log packet
- required fixed32 log_id = 1;
-
- // Timestamp when log packet.was generated
- required fixed64 timestamp = 2;
-
- // The log packet payload
- oneof fw_log_payload
- {
- // Sensor Instance Map message
- sns_diag_instance_map_log instance_map_payload = 100;
-
- // Sensor Island Mode
- sns_diag_island_transition_log island_mode_payload = 101;
-
- // Sensors Island Exit vote
- // NOT SUPPORTED YET.
- sns_diag_island_exit_vote_log island_exit_vote_payload = 102;
-
- // Sensors Memory Utilization
- sns_diag_mem_utilization_log memory_utilization_payload = 103;
-
- // Event Service status log
- sns_diag_event_service_log event_service_payload = 104;
- }
-}
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_diag_sensor.proto b/prebuilt/system/etc/sensors/proto/sns_diag_sensor.proto
deleted file mode 100644
index 20f47ab..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_diag_sensor.proto
+++ /dev/null
@@ -1,51 +0,0 @@
-// @file sns_diag_sensor.proto
-//
-// Defines standard message types to communicate with the
-// diag service
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_type.proto";
-
-enum sns_diag_sensor_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_DIAG_SENSOR_MSGID_SNS_DIAG_LOG_TRIGGER_REQ = 520;
-}
-
-// Log packets that can be triggered by the diag sensor
-enum sns_diag_triggered_log_type {
- option (nanopb_enumopt).long_names = false;
-
- // Triggers generation of sns_diag_island_transition_log
- // Only one log is generated per request
- SNS_DIAG_TRIGGERED_LOG_TYPE_ISLAND_LOG = 1;
-
- // Triggers generation of sns_diag_mem_utilization_log
- // A single request will generate a log for each separate memory
- // pool in the system
- SNS_DIAG_TRIGGERED_LOG_TYPE_MEMORY_USAGE_LOG = 2;
-}
-
-// Trigger generation of log packets. Depending upon
-// the type of log packet that is being triggered,
-// multiple log packets can be triggered for each
-// request.
-//
-// If the log packet that is triggered has been disabled
-// no log will be generated.
-message sns_diag_log_trigger_req {
-
- // User defined cookie
- // Used by test scripts to identify logs triggered
- // by messages sent to the SSC
- optional fixed64 cookie = 1;
-
- // The type of log packets that the diag sensor must
- // generate.
- required sns_diag_triggered_log_type log_type = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_distance_bound.proto b/prebuilt/system/etc/sensors/proto/sns_distance_bound.proto
deleted file mode 100644
index ab84971..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_distance_bound.proto
+++ /dev/null
@@ -1,149 +0,0 @@
-
-// @file sns_distance_bound.proto
-//
-// Defines message types for the Distance Bound (DB) Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// Distance Bound (DB) algorithm tracks the distance covered in meters
-// It expects, as part of its request, distance in meters. DB reports the client
-// when this distance is covered from the instant the request was received.
-// After a client sends a DB request for distance, it can query DB for
-// distance accumulated at any instant before the final breach occurs
-
-// DB Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "distance_bound"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_SINGLE_OUTPUT
-
-// Stream Requests:
-
-// Message IDs for DB Sensor
-enum sns_distance_bound_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_set_distance_bound
- // Purpose:
- // A distance bound request from the client
-
- SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND = 516;
-
- // Uses message: None
- // Purpose:
- // client can query the distance accumulated at a given instance
- // before final breach occurs.
- // Note: This message should be preceeded by a
- // SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND request msg
-
- SNS_DISTANCE_BOUND_MSGID_SNS_GET_DISTANCE_ACCUMULATED = 517;
-
- // Uses message: sns_distance_bound_event
- // Purpose:
- // This event corresponds to request:
- // SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND
- // This event is raised when the breach occurs.
-
- SNS_DISTANCE_BOUND_MSGID_SNS_DISTANCE_BOUND_EVENT = 772;
-
-
- // Uses message: sns_get_distance_accumulated_event
- // Purpose:
- // This event corresponds to request:
- // SNS_DISTANCE_BOUND_MSGID_SNS_GET_DISTANCE_ACCUMULATED
- // This event reports the distance accumulated at a given
- // instance when the request is received
-
- SNS_DISTANCE_BOUND_MSGID_SNS_GET_DISTANCE_ACCUMULATED_EVENT = 773;
-}
-
-
-// Gives the state which the algorithm is capable
-// of detecting
-enum sns_distance_bound_motion_state
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_DB_MS_UNKNOWN = 0;
- SNS_DB_MS_STATIONARY = 1;
- SNS_DB_MS_MOVE = 2;
- SNS_DB_MS_FIDDLE = 3;
- SNS_DB_MS_PEDESTRIAN = 4;
- SNS_DB_MS_VEHICLE = 5;
- SNS_DB_MS_WALK = 6;
- SNS_DB_MS_RUN = 7;
- SNS_DB_MS_BIKE = 8;
- SNS_DB_MS_MAX = 9;
-}
-
-// Request message
-// message associated with SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND
-// This message will result in atmost one sns_distance_bound_event when
-// the requested distance is covered
-// If client resends a fresh sns_set_distance_bound before the older is serviced
-// the older request will be lost and new distance will be calculated from that
-// instant
-
-message sns_set_distance_bound
-{
- // The distance bound in meters. When the distance travelled exceeds this,
- // an event is sent to the requestor
-
- required float distance_bound = 1;
-
- // speeds associated with different motion states.
- // if client does not send any motion state speed,
- // default values will be taken for that motion state
-
- message speeds {
- required sns_distance_bound_motion_state state = 1;
- required float speed = 2;
- }
-
- repeated speeds speed_bound = 2;
-}
-
-// Event message
-// message associated with SNS_DISTANCE_BOUND_MSGID_SNS_DISTANCE_BOUND_EVENT
-// This event corresponds to request:
-// SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND
-// This event will be raised after the breach occurs.
-
-message sns_distance_bound_event
-{
- // Distance accumulated in meters since the last sns_set_distance_bound
- required float distance_accumulated = 1;
-}
-
-// Event message
-// message associated with
-// SNS_DISTANCE_BOUND_MSGID_SNS_GET_DISTANCE_ACCUMULATED_EVENT
-// This event corresponds to request:
-// SNS_DISTANCE_BOUND_MSGID_SNS_GET_DISTANCE_ACCUMULATED
-// This event will be raised instantly upon receiveing the above request,
-// reporting the distance accumulated till that instance.
-// NOTE:
-// In following situation an error event,
-// SNS_STD_MSGID_SNS_STD_ERROR_EVENT, with payload sns_std_error_event, having
-// appropriate error code, will be raised:
-// 1. In absence of any prior SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND
-// error event with error code SNS_STD_ERROR_FAILED will be raised.
-//
-// 2. If a breach has already occurred for a prior
-// SNS_DISTANCE_BOUND_MSGID_SNS_SET_DISTANCE_BOUND request, error event
-// with error code SNS_STD_ERROR_NOT_AVAILABLE will be raised.
-
-
-message sns_get_distance_accumulated_event
-{
- // Distance accumulated in meters since the last sns_set_distance_bound
- required float distance_accumulated = 1;
-}
-
-// DB does not publish configuration events.
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_dpc.proto b/prebuilt/system/etc/sensors/proto/sns_dpc.proto
deleted file mode 100644
index b173f81..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_dpc.proto
+++ /dev/null
@@ -1,64 +0,0 @@
-// @file sns_dpc.proto
-//
-// Defines message types for the DPC(Device Position Classifier) Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The DPC Sensor provides device position information
-
-// DPC Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "device_position_classifier"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for DPC Sensor
-enum sns_dpc_msgid {
- option (nanopb_enumopt).long_names = false;
-
- //send to new client immediatly to inform current device position
- SNS_DPC_MSGID_SNS_DPC_EVENT_CONFIG = 777;
-
- //send when detect device position change
- SNS_DPC_MSGID_SNS_DPC_EVENT = 1030;
-}
-
-// Stream events:
-//
-// The sns_dpc_event message is used to publish updated device position
-// The sns_dpc_event_config message is sent immediately to new client to inform the current device position
-
-enum sns_dpc_state
-{
- option (nanopb_enumopt).long_names = false;
-
- // when algo cannot identify other states
- SNS_DPC_UNKNOWN = 1;
- // Device stationary and display within +/-15 deg of horizontal plane
- SNS_DPC_FLAT_STATIC = 2;
- // Device is not in FLAT_STATIC state and prox close
- SNS_DPC_HIDDEN = 3;
- // User picks up the device
- SNS_DPC_IN_HAND = 4;
- // User hold the device and facing the display
- SNS_DPC_FACING = 5;
-}
-
-// Events types from DPC Sensor
-message sns_dpc_event
-{
- required sns_dpc_state dpc_state = 1;
-}
-
-message sns_dpc_event_config
-{
- //current dpc state
- required sns_dpc_state dpc_state = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_ext_svc.proto b/prebuilt/system/etc/sensors/proto/sns_ext_svc.proto
deleted file mode 100644
index dd5b999..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ext_svc.proto
+++ /dev/null
@@ -1,81 +0,0 @@
-// @file sns_ext_svc.proto
-//
-// Sensor provides access to external QMI services.
-//
-// This Sensor will create a QMI connection to the external service upon
-// receipt of the first request. Subsequent requests will be sent upon the
-// same connection. The connection will be closed after the client closes
-// the data stream.
-//
-// An error event will be sent upon any received QMI error, including upon
-// the error callback. It is then the responsibility of the client to close
-// the data stream, and re-open a new one if desired.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_ext_svc_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Send a QMI request message
- SNS_EXT_SVC_MSGID_SNS_EXT_SVC_REQ = 512;
-
- // Asynchronously received response message
- SNS_EXT_SVC_MSGID_SNS_EXT_SVC_RESP = 768;
-
- // Asynchronously received indication message
- SNS_EXT_SVC_MSGID_SNS_EXT_SVC_IND = 1024;
-}
-
-// External services supported by this Sensor
-enum sns_ext_svc
-{
- option (nanopb_enumopt).long_names = false;
-
- // QMI_LOC; see location_service_v02.idl
- SNS_EXT_SVC_LOCATION = 0;
-}
-
-message sns_ext_svc_req
-{
- required sns_ext_svc svc_id = 1;
-
- // QMI/IDL Message ID
- required int32 msg_id = 2;
-
- // Client-specified transaction ID, to be returned in sns_ext_svc_resp
- optional int32 transaction_id = 3;
-
- // Contains the QMI-decoded request message.
- required bytes payload = 4;
-}
-
-message sns_ext_svc_resp
-{
- // QMI/IDL Message ID
- required int32 msg_id = 1;
-
- // Transport error, as defined in qmi_client.h; Defaults to QMI_NO_ERR
- required int32 transp_err = 2;
-
- // Client-specified transaction ID, as provided in sns_ext_svc_req
- optional int32 transaction_id = 3;
-
- // Contains the QMI-decoded response message
- // May be empty if transport_err != QMI_NO_ERR
- required bytes payload = 4;
-}
-
-message sns_ext_svc_ind
-{
- // QMI/IDL Message ID
- required int32 msg_id = 1;
-
- // Contains the QMI-decoded indication message.
- required bytes payload = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_facing.proto b/prebuilt/system/etc/sensors/proto/sns_facing.proto
deleted file mode 100644
index 8decd9f..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_facing.proto
+++ /dev/null
@@ -1,60 +0,0 @@
-// @file sns_facing.proto
-//
-// Defines message types for the the facing sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// Facing calculates face up, down and neutral states. Facing will initially start in an
-// unknown state, and later transition to face up, down and neutral.
-// Neutral state reported to client on demand
-
-// Facing Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "facing"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Facing Sensor
-enum sns_facing_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_FACING_MSGID_SNS_FACING_EVENT = 1024;
-}
-
-// Device Facing state detected by Facing sensor
-enum sns_facing_event_state
-{
- option (nanopb_enumopt).long_names = false;
- SNS_FACING_EVENT_STATE_UNKNOWN = 0;
- //Phone has just moved to a facing-up phone posture
- //which is defined as screen up.
- SNS_FACING_EVENT_STATE_UP = 1;
- //Phone has just moved to a facing-down phone posture,
- //which is defined as screen down.
- SNS_FACING_EVENT_STATE_DOWN = 2;
- //Phone has just left either the facing-up
- //or the facing-down phone posture
- SNS_FACING_EVENT_STATE_NEUTRAL = 3;
-}
-
-// Event Message
-// Output data event generated by the facing sensor.
-message sns_facing_event
-{
- // Facing sensor state info
- required sns_facing_event_state state = 1[default = SNS_FACING_EVENT_STATE_UNKNOWN];
-}
-
-// Stream events:
-//
-// The sns_facing_event message is used to publish updated state
-//
-// Facing sensor does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_fmv.proto b/prebuilt/system/etc/sensors/proto/sns_fmv.proto
deleted file mode 100644
index 2a56cba..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_fmv.proto
+++ /dev/null
@@ -1,40 +0,0 @@
-// @file sns_fmv.proto
-//
-// Defines the API for Filtered Magnetic Vector.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A FMV sensor reports the filtered magnetic vector
-//
-// ## FMV sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "fmv"
-//
-// ## Request Message: sns_std_sensor_config
-// sns_std_sensor_config::sample_rate is used to specify the sampling rate (Hz)
-// of the FMV sensor. Sensor will generate data events at this rate.
-//
-// ## Event Message: sns_std_sensor_event
-// 1. Output of the FMV sensor will be populated in sns_std_sensor_event
-// 2. Each stream event contains three output data fields in µT (micro Tesla)
-// 3. Data in the stream is adjusted to Android coordinate system relative to a
-// mobile device held with screen facing the user in it's natural orientation:
-// X-axis: parallel to the screen pointing to the right
-// Y-axis: parallel to the screen pointing to the top
-// Z-axis: perpendicular to the screen pointing towards the user
-// 4. Data in the stream event is ordered as:
-// data[0] = X-axis
-// data[1] = Y-axis
-// data[2] = Z-axis
-// 5. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-//
-// sns_std_sensor_event::status specifies the reliability of the sample value
-// value is of type sns_std_sensor_sample_status. see sns_std_sensor.proto for
-// details.
diff --git a/prebuilt/system/etc/sensors/proto/sns_fw.proto b/prebuilt/system/etc/sensors/proto/sns_fw.proto
deleted file mode 100644
index 3cededd..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_fw.proto
+++ /dev/null
@@ -1,23 +0,0 @@
-// @file sns_fw.proto
-//
-// Defines Framework internal values.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-// Internal Framework message IDs
-// Note: These message IDs must not conflict with those in sns_std_msgid
-enum sns_fw_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Special message only sent by the Framework; not processed by Sensors
- // Empty Message
- SNS_FW_MSGID_SNS_DESTROY_REQ = 120;
-
- // Special message only sent by the Framework; not processed by Sensors
- // Empty Message
- SNS_FW_MSGID_SNS_DESTROY_COMPLETE_EVENT = 250;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_game_rv.proto b/prebuilt/system/etc/sensors/proto/sns_game_rv.proto
deleted file mode 100644
index ea0dee6..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_game_rv.proto
+++ /dev/null
@@ -1,48 +0,0 @@
-// @file sns_game_rv.proto
-//
-// Defines the API for Game Rotation Vector sensors
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A GameRV sensor reports the orientation of the device relative to an
-// unspecified coordinates frame. It is obtained by integration of
-// accelerometer and gyroscope readings. Therefore the Y axis doesn't point
-// north but instead to an arbitrary reference.
-//
-// ## GameRV sensor attributes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE is "game_rv"
-//
-// ## Request Message: sns_std_sensor_config
-// sns_std_sensor_config::sample_rate is used to specify the sampling rate (Hz)
-// of the GameRV sensor. Sensor will generate data events at this rate.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the GameRV sensor will be populated in sns_std_sensor_event
-//
-// The orientation is represented by the rotation necessary to align
-// the coordinate frame with the device's coordinates. That is,
-// applying the rotation to the world frame (X,Y,Z) would align them with
-// the device coordinates (x,y,z).
-//
-// The rotation can be seen as rotating the device by an angle theta around an
-// axis rot_axis to go from the reference device orientation to the current
-// device orientation. The rotation is encoded as the four unitless x, y, z, w
-// components of a unit quaternion:
-// sns_std_sensor_event::data[0] = rot_axis.x*sin(theta/2)
-// sns_std_sensor_event::data[1] = rot_axis.y*sin(theta/2)
-// sns_std_sensor_event::data[2] = rot_axis.z*sin(theta/2)
-// sns_std_sensor_event::data[3] = cos(theta/2)
-//
-// Where:
-// - the x, y and z fields of rot_axis are the East-North-Up coordinates
-// of a unit length vector representing the rotation axis
-// - theta is the rotation angle
-//
-// sns_std_sensor_event::status specifies the reliability of the sample value
-// value is of type sns_std_sensor_sample_status. see sns_std_sensor.proto for
-// details.
diff --git a/prebuilt/system/etc/sensors/proto/sns_geomag_rv.proto b/prebuilt/system/etc/sensors/proto/sns_geomag_rv.proto
deleted file mode 100644
index 5da3151..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_geomag_rv.proto
+++ /dev/null
@@ -1,50 +0,0 @@
-// @file sns_geomag_rv.proto
-//
-// Defines the API for Geomagnetic Rotation Vector sensors.
-// This Sensor is similar to Rotation Vector, but uses a magnetometer instead
-// of a gyroscope.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A GeoMagRV sensor reports the orientation of the device relative to the
-// East-North-Up coordinates frame. It is obtained by integration of
-// accelerometer and magnetometer readings.
-//
-// ## GeoMagRV sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "geomag_rv"
-//
-// ## Request Message: sns_std_sensor_config
-// sns_std_sensor_config::sample_rate is used to specify the sampling rate (Hz)
-// of the GeoMagRV sensor. Sensor will generate data events at this rate.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the GeoMagRV sensor will be populated in sns_std_sensor_event
-//
-// The East-North-Up coordinate system is defined as a direct orthonormal
-// basis where:
-// - X points east and is tangential to the ground.
-// - Y points north and is tangential to the ground.
-// - Z points towards the sky and is perpendicular to the ground.
-//
-// The rotation can be seen as rotating the device by an angle theta around an
-// axis rot_axis to go from the reference device orientation to the current
-// device orientation. The rotation is encoded as the four unitless x, y, z, w
-// components of a unit quaternion:
-// sns_std_sensor_event::data[0] = rot_axis.x*sin(theta/2)
-// sns_std_sensor_event::data[1] = rot_axis.y*sin(theta/2)
-// sns_std_sensor_event::data[2] = rot_axis.z*sin(theta/2)
-// sns_std_sensor_event::data[3] = cos(theta/2)
-//
-// Where:
-// - the x, y and z fields of rot_axis are the East-North-Up coordinates
-// of a unit length vector representing the rotation axis
-// - theta is the rotation angle
-//
-// sns_std_sensor_event::status specifies the reliability of the sample value
-// value is of type sns_std_sensor_sample_status. see sns_std_sensor.proto for
-// details.
diff --git a/prebuilt/system/etc/sensors/proto/sns_gravity.proto b/prebuilt/system/etc/sensors/proto/sns_gravity.proto
deleted file mode 100644
index b520a08..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_gravity.proto
+++ /dev/null
@@ -1,30 +0,0 @@
-// @file sns_gravity.proto
-//
-// Defines standard message types for the Gravity Sensor
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// Configuration Message
-// Used to either request for a certain configuration of the gravity sensor or
-// alter an already existing configuration of the gravity sensor
-// Uses sns_std_sensor_config defined in sns_std_sensor.proto
-// The message field definitions are as follows:
-// 1) float sample_rate
-// containing the required sample rate of the gravity sensor in hertz
-
-// Data Message
-// Data event generated by the gravity.
-// Uses sns_std_sensor_event message defined in sns_std_sensor.proto
-// The data field of the sns_std_sensor_event message
-// contains a float array of length 6 with the following definition
-// 1) float data[0] to data[2]
-// Representing the gravity values along x,y,z axes in m/s2.
-// 2) float data[3] to data[5]
-// Representing the linear acceleration values along x,y,z axes in m/s2.
-// Determined as the delta between the accel and the gravity values
-// along that axis.
diff --git a/prebuilt/system/etc/sensors/proto/sns_gyro.proto b/prebuilt/system/etc/sensors/proto/sns_gyro.proto
deleted file mode 100644
index 5eb4ff1..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_gyro.proto
+++ /dev/null
@@ -1,74 +0,0 @@
-// @file sns_gyro.proto
-//
-// Defines the API for Gyroscope Sensors.
-// All Gyroscope Sensor drivers are required to comply with this API.
-// Any new functionality for Gyroscope Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Gyroscope Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "gyro".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in dps/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in dps unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Gyroscope Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-// 2. The Gyroscope Sensor uses batching_period item in
-// sns_std_request as the requested batching rate to determine
-// hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Gyroscope Sensor publishes device rotation data stream events
-// using the sns_std_sensor_event message.
-// 2. Each stream event contains three output data fields where data is
-// in radians/sec units and is factory calibrated.
-// 3. Data in the stream is adjusted to Android coordinate system relative to a
-// mobile device held with screen facing the user in it's natural orientation:
-// X-axis: parallel to the screen pointing to the right
-// Y-axis: parallel to the screen pointing to the top
-// Z-axis: perpendicular to the screen pointing towards the user
-// This conforms to the mobile device axes orientation as specified by the
-// Android Sensor API.
-// 4. Data in the stream event is ordered as:
-// data[0] = X-axis
-// data[1] = Y-axis
-// data[2] = Z-axis
-// 5. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 6. The Gyroscope Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 7. The Gyroscope Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and comp_matrix fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-// Handling self-test requests:
-// 1. The Gyroscope Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Gyroscope Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Gyroscope Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Gyroscope Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_gyro_cal.proto b/prebuilt/system/etc/sensors/proto/sns_gyro_cal.proto
deleted file mode 100644
index 5b5ac30..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_gyro_cal.proto
+++ /dev/null
@@ -1,32 +0,0 @@
-// @file sns_gyro_cal.proto
-//
-// Defines message types for the Gyro Calibration Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_cal.proto";
-
-// The Gyro Calibration Sensor determines the calibration parameters
-// for gyro sensor
-
-// Gyro Calibration Sensor Attributes:
-// - SNS_STD_SENSOR_ATTRID_TYPE: "gyro_cal"
-// - SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG message ID is used to
-// enable the sensor
-// - SNS_CAL_MSGID_SNS_CAL_RESET message ID is used to reset the algorithm
-// and any previously determined calibration parameters.
-
-// Stream Events:
-// - SNS_CAL_MSGID_SNS_CAL_EVENT message ID is used to report calibration
-// parameters to the client of the sensor. The sns_cal_event message as
-// defined in sns_cal.proto is used to report this data event where the
-// units for the bias field in the message are in rad / s
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_gyro_rot_matrix.proto b/prebuilt/system/etc/sensors/proto/sns_gyro_rot_matrix.proto
deleted file mode 100644
index 32614fc..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_gyro_rot_matrix.proto
+++ /dev/null
@@ -1,50 +0,0 @@
-// @file sns_gyro_rot_matrix.proto
-//
-// Defines standard message types for the Gyro Rotation Matrix
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-enum sns_gyro_rot_matrix_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_GYRO_ROT_MATRIX_MSGID_SNS_STD_SENSOR_EVENT = 1024;
-}
-
-// Data Message
-// Data event generated by the gyro rotation matrix.
-// Uses sns_std_sensor_event message defined in sns_std_sensor.proto
-// The data field of the sns_std_sensor_event message
-// contains a float array of length 10 with the following definition
-// 1) float data[0] to data[8]
-// 3 by 3 Gyro Rotation Matrix output
-// Representing the rotation from previously sampled gyro values
-// to the current one.
-// The matrix definition is as follows:
-// curr_gyro_XYZ[3X1] = gyro_rot_matrix[3X3] * prev_gyro_XYZ[3X1]
-// data[0] = gyro_rot_matrix[0,0]
-// data[1] = gyro_rot_matrix[0,1]
-// data[2] = gyro_rot_matrix[0,2]
-// data[3] = gyro_rot_matrix[1,0]
-// data[4] = gyro_rot_matrix[1,1]
-// data[5] = gyro_rot_matrix[1,2]
-// data[6] = gyro_rot_matrix[2,0]
-// data[7] = gyro_rot_matrix[2,1]
-// data[8] = gyro_rot_matrix[2,2]
-// 2) float data[9]
-// Gyro Norm of the currently sampled gyro data
-// determined as the sum of squares of gyro on each of the axes
-// i.e. curr_gyro_X^2 + curr_gyro_Y^2 + curr_gyro_Z^2
-
-// Configuration Message
-// Used to either request for a certain configuration of the Gyro Rotation Matrix Sensor or
-// alter an already existing configuration of the Simulation Sensor
-// Uses sns_std_sensor_config defined in sns_std_sensor.proto
-// The message field definitions are as follows:
-// 1) float sample_rate
-// containing the required sample rate of the Gyro Rotation Matrix sensor in hertz
diff --git a/prebuilt/system/etc/sensors/proto/sns_hall.proto b/prebuilt/system/etc/sensors/proto/sns_hall.proto
deleted file mode 100644
index 31aaa06..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_hall.proto
+++ /dev/null
@@ -1,81 +0,0 @@
-// @file sns_hall.proto
-//
-// Defines the API for Hall Sensors.
-// All Hall Sensor drivers are required to comply with this API.
-// Any new functionality for Hall Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-
-// Attribute requirements:
-// The Hall Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "hall".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute is not applicable since this is an event
-// sensor.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values as 0 and 1.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Hall Sensor handles the SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// message ID for all stream enable/update requests.
-// 2. The Hall Sensor operates in on-change mode and report
-// samples only for magnet NEAR/FAR transitions.
-
-// Message IDs for hall Sensor
-enum sns_hall_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_hall_event
- // Purpose: An output data event from the hall sensor to it's client.
- SNS_HALL_MSGID_SNS_HALL_EVENT = 770;
-}
-
-enum sns_hall_event_type {
- option (nanopb_enumopt).long_names = false;
-
- SNS_HALL_EVENT_TYPE_FAR = 0;
- SNS_HALL_EVENT_TYPE_NEAR = 1;
-}
-
-// Events types from hall Sensor
-message sns_hall_event
-{
- // Hall NEAR/FAR output event
- required sns_hall_event_type hall_event_type = 1 [default = SNS_HALL_EVENT_TYPE_FAR];
-
- // Hall sensor sample status
- required sns_std_sensor_sample_status status = 2 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-// Handling stream events:
-// 1. The Hall Sensor publishes magnetic field proximity data stream
-// events using the sns_hall_event message.
-// 2. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 3. The Hall Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-
-// Handling self-test requests:
-// 1. The Hall Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Hall Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Hall Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_heart_beat.proto b/prebuilt/system/etc/sensors/proto/sns_heart_beat.proto
deleted file mode 100644
index db785a0..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_heart_beat.proto
+++ /dev/null
@@ -1,31 +0,0 @@
-// @file sns_heart_beat.proto
-//
-// Defines the API for Heart Beat sensors
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A heart beat sensor reports everytime a heart beat peak is detected.
-//
-// Peak ideally corresponds to the positive peak in the QRS complex of
-// an ECG signal, and the event timestamp should correspond to the time this
-// peak occured.
-//
-// The sensor is not expected to be optimized for latency. As a guide, a
-// receipt latency of up to 10 seconds is acceptable.
-//
-// ## Heart Beat sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "heart_beat"
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the Heart Beat sensor will be populated in sns_std_sensor_event.
-//
-// sns_std_sensor_event::data[0] = confidence in the detection of the peak
-// where 0.0 represent no information at all, and 1.0 represents certainty.
diff --git a/prebuilt/system/etc/sensors/proto/sns_heart_rate.proto b/prebuilt/system/etc/sensors/proto/sns_heart_rate.proto
deleted file mode 100644
index c6f90f5..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_heart_rate.proto
+++ /dev/null
@@ -1,55 +0,0 @@
-// @file sns_heart_rate.proto
-//
-// Defines the API for Heart Rate Detection Sensors.
-//
-// Copyright (c) 2017-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// A sensor of this type returns the current heart rate in beats per minute
-// (BPM). Because this sensor is on-change, events must be generated when and
-// only when BPM or status have changed since the last event.
-//
-// Upon the first activation, unless the device is known to not be on the
-// body, the status field of the first event must be set to UNRELIABLE.
-//
-// ## Heart Rate sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "heart_rate"
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the Heart Rate sensor will be populated in sns_std_sensor_event.
-//
-// SNS_HEART_RATE_MSGID_SNS_HEART_RATE_EVENT::data[0] = current heart rate in beats per minute (BPM)
-//
-// SNS_HEART_RATE_MSGID_SNS_HEART_RATE_EVENT::status specifies the reliability of the sample value
-// value is of type sns_heart_rate_event_type.
-
-enum sns_heart_rate_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_HEART_RATE_MSGID_SNS_HEART_RATE_EVENT = 779;
-}
-
-enum sns_heart_rate_event_type {
- option (nanopb_enumopt).long_names = false;
-
- SNS_HR_STATUS_NO_CONTACT = -1;
- SNS_HR_STATUS_UNRELIABLE = 0;
- SNS_HR_STATUS_ACCURACY_LOW = 1;
- SNS_HR_STATUS_ACCURACY_MEDIUM = 2;
- SNS_HR_STATUS_ACCURACY_HIGH = 3;
-}
-
-// Events types from heart_rate Sensor
-message sns_heart_rate_event
-{
- required float heart_rate = 1;
- required sns_heart_rate_event_type heart_rate_event_type = 2 [default = SNS_HR_STATUS_NO_CONTACT];
-}
\ No newline at end of file
diff --git a/prebuilt/system/etc/sensors/proto/sns_humidity.proto b/prebuilt/system/etc/sensors/proto/sns_humidity.proto
deleted file mode 100644
index 7ae47bc..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_humidity.proto
+++ /dev/null
@@ -1,69 +0,0 @@
-// @file sns_humidity.proto
-//
-// Defines the API for Humidity Sensors.
-// All Humidity Sensor drivers are required to comply with this API.
-// Any new functionality for Humidity Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Humidity Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "humidity".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in %RH/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in %RH unit.
-// 4. The Humidity Sensor is an on-change sensor.
-// 5. See sns_std_sensor.proto for other attributes.
-
-
-// Handling stream requests:
-// 1. The Humidity Sensor handles the SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// message ID for all stream enable/update requests.
-// 2. The Humidity Sensor supports on-change mode of operation.
-// 3. In on-change mode the Sensor could use interrupt operation and
-// reports samples for only significant change in humidity.
-// Example: +/- 5% change.
-
-// Handling stream events:
-// 1. The Humidity Sensor publishes ambient relative humidity data stream
-// events using the sns_std_sensor_event message.
-// 2. Each stream event contains one output data field where data is
-// factory calibrated and ordered as:
-// data[0] = Humidity data in %RH (% Relative Humidity)
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Humidity Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Humidity Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The Humidity Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Humidity Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Humidity Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Humidity Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_interrupt.proto b/prebuilt/system/etc/sensors/proto/sns_interrupt.proto
deleted file mode 100644
index ed9f8c2..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_interrupt.proto
+++ /dev/null
@@ -1,140 +0,0 @@
-// @file sns_interrupt.proto
-//
-// Defines standard message types for the Interrupt Sensor. The Interrupt
-// Sensor is a QC written platform Sensor which is used by physical Sensor
-// drivers that use interrupts like data-ready interrupt (DRI), FIFO watermark
-// interrupt, etc. These physical Sensors must use the API defined in this file
-// to send requests to and parse events from the Interrupt Sensor.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_interrupt_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // This message is used to register for notifications for a physical interrupt
- // pin with the interrupt sensor.
- SNS_INTERRUPT_MSGID_SNS_INTERRUPT_REQ = 512;
-
- // This message is used to register for notifications for an In Band
- // Interrupt (IBI).
- SNS_INTERRUPT_MSGID_SNS_IBI_REQ = 514;
-
- // Data event from interrupt Sensor.
- //
- // This message is generated each time a registered
- // interrupt fires. This message ID corresponds to
- // the message sns_interrupt_event
- SNS_INTERRUPT_MSGID_SNS_INTERRUPT_EVENT = 1024;
-
- // Interrupt sensor event marking it as registered
- //
- // This message is generated when an interrupt has
- // been successfully registered. Sensors should not
- // turn on the hardware interrupts until this
- // event has been recieved from the interrupt sensor.
- // This event has no body and the event length is 0
- SNS_INTERRUPT_MSGID_SNS_INTERRUPT_REG_EVENT = 1025;
-
- // Notification message to the interrupt Sensor that
- // a level triggered interrupt has been serviced and cleared.
- //
- // In case of level triggered interrupts, when the interrupt
- // fires, the interrupt sensor disables the interrupt until
- // it is serviced and cleared at it's source. This message
- // is used to notify the interrupt sensor that the interrupt
- // has been serviced and cleared so that it can be re-enabled.
- // This message is not applicable to edge triggered interrupts.
- // This message does not have any payload.
- SNS_INTERRUPT_MSGID_SNS_INTERRUPT_IS_CLEARED = 513;
-}
-
-// Types of interrupt triggers.
-enum sns_interrupt_trigger_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_INTERRUPT_TRIGGER_TYPE_RISING = 0; // Trigger type rising edge.
- SNS_INTERRUPT_TRIGGER_TYPE_FALLING = 1; // Trigger type falling edge.
- SNS_INTERRUPT_TRIGGER_TYPE_DUAL_EDGE = 2; // Trigger type rising and falling edge.
- SNS_INTERRUPT_TRIGGER_TYPE_HIGH = 3; // Trigger type high level.
- SNS_INTERRUPT_TRIGGER_TYPE_LOW = 4; // Trigger type low level.
-}
-
-// Types of interrupt pin drive strength.
-enum sns_interrupt_drive_strength
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_INTERRUPT_DRIVE_STRENGTH_2_MILLI_AMP = 0; // Specify a 2 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_4_MILLI_AMP = 1; // Specify a 4 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_6_MILLI_AMP = 2; // Specify a 6 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_8_MILLI_AMP = 3; // Specify an 8 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_10_MILLI_AMP = 4; // Specify a 10 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_12_MILLI_AMP = 5; // Specify a 12 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_14_MILLI_AMP = 6; // Specify a 14 mA drive.
- SNS_INTERRUPT_DRIVE_STRENGTH_16_MILLI_AMP = 7; // Specify a 16 mA drive.
-}
-
-// Types of interrupt pin pull.
-enum sns_interrupt_pull_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_INTERRUPT_PULL_TYPE_NO_PULL = 0; // Do not specify a pull.
- SNS_INTERRUPT_PULL_TYPE_PULL_DOWN = 1; // Pull the GPIO down.
- SNS_INTERRUPT_PULL_TYPE_KEEPER = 2; // Designate as a Keeper.
- SNS_INTERRUPT_PULL_TYPE_PULL_UP = 3; // Pull the pin up.
-}
-
-// Client request message for Interrupt Sensor.
-message sns_interrupt_req
-{
- // Interrupt pin number.
- required uint32 interrupt_num = 1;
-
- // Interrupt trigger type.
- required sns_interrupt_trigger_type interrupt_trigger_type = 2;
-
- // Interrupt pin drive strength configuration.
- required sns_interrupt_drive_strength interrupt_drive_strength = 3;
-
- // Interrupt pin pull configuration.
- required sns_interrupt_pull_type interrupt_pull_type = 4;
-
- // Interrupt pin type. True if this is a chip
- // TLMM GPIO. False if this is an SSC TLMM GPIO.
- required bool is_chip_pin = 5;
-}
-
-// Client request message for Interrupt Sensor.
-message sns_ibi_req
-{
- // Slave address for I3C
- required uint32 dynamic_slave_addr = 1;
-
- // Platform bus instance number (BLSP number)
- required uint32 bus_instance = 2;
-
- // Number of optional + mandatory bytes supported by the sensor hardware
- required fixed32 ibi_data_bytes = 3;
-}
-
-// Event generated by the Interrupt Sensor.
-message sns_interrupt_event
-{
- // Interrupt pin number or dynamic slave address
- required fixed32 interrupt_num = 1;
-
- // Timestamp when trigger event on the interrupt
- // was detected.
- required fixed64 timestamp = 2;
-
- // If an IBI event, the data associated with the event
- optional bytes ibi_data = 3 [(nanopb).max_size = 32];
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_mag.proto b/prebuilt/system/etc/sensors/proto/sns_mag.proto
deleted file mode 100644
index 6c8868f..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_mag.proto
+++ /dev/null
@@ -1,75 +0,0 @@
-// @file sns_mag.proto
-//
-// Defines the API for Magnetometer Sensors.
-// All Magnetometer Sensor drivers are required to comply with this API.
-// Any new functionality for Magnetometer Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Magnetometer Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "mag".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in µT/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in µT unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Magnetometer Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-// 2. If the physical sensor supports hardware FIFO then the Magnetometer
-// Sensor uses batching_period item in sns_std_request as the requested
-// batching rate to determine hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Magnetometer Sensor publishes ambient magnetic field data events
-// using the sns_std_sensor_event message.
-// 2. Each stream event contains three output data fields where data is
-// in µT (micro Tesla) units and is factory calibrated.
-// 3. Data in the stream is adjusted to Android coordinate system relative to a
-// mobile device held with screen facing the user in it's natural orientation:
-// X-axis: parallel to the screen pointing to the right
-// Y-axis: parallel to the screen pointing to the top
-// Z-axis: perpendicular to the screen pointing towards the user
-// This conforms to the mobile device axes orientation as specified by the
-// Android Sensor API.
-// 4. Data in the stream event is ordered as:
-// data[0] = X-axis
-// data[1] = Y-axis
-// data[2] = Z-axis
-// 5. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 6. The Magnetometer Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 7. The Magnetometer Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and comp_matrix fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The Magnetometer Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Magnetometer Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Magnetometer Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Magnetometer Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_mag_cal.proto b/prebuilt/system/etc/sensors/proto/sns_mag_cal.proto
deleted file mode 100644
index 3ce0441..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_mag_cal.proto
+++ /dev/null
@@ -1,32 +0,0 @@
-// @file sns_mag_cal.proto
-//
-// Defines message types for the Mag Calibration Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_cal.proto";
-
-// The Mag Calibration Sensor determines the calibration parameters
-// for magnetometer sensor
-
-// Mag Calibration Sensor Attributes:
-// - SNS_STD_SENSOR_ATTRID_TYPE: "mag_cal"
-// - SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG message ID is used to
-// enable the sensor
-// - SNS_CAL_MSGID_SNS_CAL_RESET message ID is used to reset the algorithm
-// and any previously determined calibration parameters.
-
-// Stream Events:
-// - SNS_CAL_MSGID_SNS_CAL_EVENT message ID is used to report calibration
-// parameters to the client of the sensor. The sns_cal_event message as
-// defined in sns_cal.proto is used to report this data event where the
-// units for the bias field in the message are in micro Tesla.
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_mcmd.proto b/prebuilt/system/etc/sensors/proto/sns_mcmd.proto
deleted file mode 100644
index c8554ca..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_mcmd.proto
+++ /dev/null
@@ -1,58 +0,0 @@
-// @file sns_mcmd.proto
-//
-// Defines the API for Magnitude Change Motion Detection Sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// A magnitude change motion sensor reports once
-// - The device is moving
-// - The device is detected to be stationary
-// The period of time to monitor for stationarity is 5 seconds.
-// After reporting, conceptually the algorithm's state is reset,
-// and detection begins again.
-//
-// Motion here refers to any change in accelerometer greater than 78ug in
-// any direction
-//
-// Stationarity here refers to change in accelerometer smaller than 78ug in
-// any direction for 5 seconds.
-//
-// ## Magnitude Change Motion Detect sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "mcmd"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Message IDs for Magnitude Change Motion Sensor
-enum sns_mcmd_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Configuration Request
- SNS_MCMD_MSGID_SNS_MCMD_CONFIG = 512;
-
- // Empty Event
- // Indicates that the requested state has been detected
- SNS_MCMD_MSGID_SNS_MCMD_EVENT = 770;
-}
-
-// Detected states supported by the MC Motion Detector
-enum sns_mcmd_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_MCMD_TYPE_STATIONARY = 0;
- SNS_MCMD_TYPE_MOTION = 1;
-}
-
-// Configuration Message
-// Used to specify the MCMD configuration
-message sns_mcmd_config
-{
- // Which detector type to enable
- required sns_mcmd_type type = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_motion_detect.proto b/prebuilt/system/etc/sensors/proto/sns_motion_detect.proto
deleted file mode 100644
index 781d52a..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_motion_detect.proto
+++ /dev/null
@@ -1,52 +0,0 @@
-// @file sns_motion_detect.proto
-//
-// Defines standard message types for Motion Detect Sensor. All physical Sensor
-// drivers that support Motion Detect Sensor are required to support the
-// event messages as defined in this file.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-
-// Attribute requirements:
-// The Motion Detect Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "motion_detect".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS, SNS_STD_SENSOR_ATTRID_RANGES,
-// SNS_STD_SENSOR_ATTRID_RATES attributes are not applicable since this is
-// a single output sensor.
-// 3. See sns_std_sensor.proto for other attributes.
-
-
-// Handling stream requests:
-// 1. A message with ID SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is an
-// enable request to the motion_detect sensor.
-// 2. A client deletes the data stream with motion_detect Sensor to disable it's
-// original enable request.
-
-// Message IDs for motion_detect Sensor
-enum sns_motion_detect_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // The motion_detect Sensor publishes an event with this message ID
- SNS_MOTION_DETECT_MSGID_SNS_MOTION_DETECT_EVENT = 771;
-}
-
-enum sns_motion_detect_event_type {
- option (nanopb_enumopt).long_names = false;
-
- SNS_MOTION_DETECT_EVENT_TYPE_DISABLED = 0;
- SNS_MOTION_DETECT_EVENT_TYPE_ENABLED = 1;
- SNS_MOTION_DETECT_EVENT_TYPE_FIRED = 2;
-}
-
-// Events types from motion detect Sensor
-message sns_motion_detect_event
-{
- required sns_motion_detect_event_type motion_detect_event_type = 1 [default = SNS_MOTION_DETECT_EVENT_TYPE_DISABLED];
-}
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_multishake.proto b/prebuilt/system/etc/sensors/proto/sns_multishake.proto
deleted file mode 100644
index c608751..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_multishake.proto
+++ /dev/null
@@ -1,71 +0,0 @@
-// @file sns_multishake.proto
-//
-// Defines message types for the the multishake sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-// The multishake sensor detects shakes along an axis and
-// generates an event when a client specified number of consecutive shakes
-// to the device occur. There is a sleep period after a multishake event
-// is reported during which shakes are not detected. This sleep period
-// is configurable through the registry.
-//
-// ## Multishake sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "multishake"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-//
-// ## Request Message: SNS_MULTISHAKE_MSGID_SNS_MULTISHAKE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: SNS_MULTISHAKE_MSGID_SNS_MULTISHAKE_EVENT
-// Reported upon new detection of multishake event.
-//
-// ## Configuration Message: Multishake does not publish configuration
-// messages.
-
-enum sns_multishake_msgid
-{
- option (nanopb_enumopt).long_names = false;
- SNS_MULTISHAKE_MSGID_SNS_MULTISHAKE_CONFIG = 512;
- SNS_MULTISHAKE_MSGID_SNS_MULTISHAKE_EVENT = 1024;
-}
-
-enum multishake_axis
-{
- option (nanopb_enumopt).long_names = false;
- // Phone is shaken, but phone shake direction cannot be clearly determined
- MULTISHAKE_AXIS_UNKNOWN_AXIS = 0;
-
- // Phone is shaken in the X axis according
- // to the android coordinate system
- MULTISHAKE_AXIS_X_AXIS = 1;
-
- // Phone is shaken in the Y axis according
- // to the android coordinate system
- MULTISHAKE_AXIS_Y_AXIS = 2;
-
-}
-
-message sns_multishake_config
-{
- // Select the shake axis along which shake events are detected by
- // the algorithm instance. Multiple axes can be selected.
- // To detect shakes starting from a left shake or a right shake, use
- // shake_axis = [MULTISHAKE_AXIS_LEFT, MULTISHAKE_AXIS_RIGHT]
- //
- // If shake_axis is not provided, then a multishake event along any
- // axis will be reported.
- repeated multishake_axis shake_axis = 1 [(nanopb).max_count = 3];
-}
-
-message sns_multishake_event
-{
- // Specifies the axis along which the shakes were detected If shakes in
- // multiple axes were detected, the direction of the first shake is reported
- // in this field.
- required multishake_axis shake_axis = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_oem1.proto b/prebuilt/system/etc/sensors/proto/sns_oem1.proto
deleted file mode 100644
index 570f8d7..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_oem1.proto
+++ /dev/null
@@ -1,39 +0,0 @@
-// @file sns_oem1.proto
-//
-// Defines standard message types for the OEM1
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-enum sns_oem1_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_OEM1_MSGID_SNS_OEM1_DATA = 1024;
-}
-
-
-// Configuration Message
-// Used to either request for a certain configuration of the Sim Sensor or
-// alter an already existing configuration of the Simulation Sensor
-// Uses sns_std_sensor_config defined in sns_std_sensor.proto
-// The message field definitions are as follows:
-// 1) float sample_rate
-// containing the required sample rate of the Sim sensor in hertz
-
-// Data Message
-// Output data event generated by the oem1 sensor.
-message sns_oem1_data
-{
- // oem1 Vector along axis x,y,z in m/s2
- repeated float oem1 = 1 [(nanopb).max_count = 3];
-
- // Accuracy of the data
- required sns_std_sensor_sample_status accuracy = 2;
-}
-
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_offbody_detect.proto b/prebuilt/system/etc/sensors/proto/sns_offbody_detect.proto
deleted file mode 100644
index 04255c9..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_offbody_detect.proto
+++ /dev/null
@@ -1,55 +0,0 @@
-// @file sns_offbody_detect.proto
-//
-// Defines the API for Offbody Detection Sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// An offbody detect sensor reports every time the device transitions from
-// off-body to on-body and from on-body to off-body (e.g. a wearable device
-// being removed from the wrist would trigger an event indicating an off-body
-// transition).
-//
-// This sensor must be able to detect and report an on-body to off-body
-// transition within 1 second of the device being removed from the body,
-// and must be able to detect and report an off-body to on-body transition
-// within 5 seconds of the device being put back onto the body.
-//
-// ## Offbody Detection sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "offbody_detect"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: SNS_OFFBODY_DETECT_MSGID_SNS_OFFBODY_DETECT_EVENT
-
-// Message IDs for Offbody Detection Sensor
-enum sns_offbody_detect_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_OFFBODY_DETECT_MSGID_SNS_OFFBODY_DETECT_EVENT = 772;
-}
-
-enum sns_offbody_detect_event_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Current state is unknown: not yet detected
- SNS_OFFBODY_DETECT_EVENT_TYPE_UNKNOWN = 0;
- // Device has been detected to be on-body
- SNS_OFFBODY_DETECT_EVENT_TYPE_ON = 1;
- // Device has been detected to be off-body
- SNS_OFFBODY_DETECT_EVENT_TYPE_OFF = 2;
-}
-
-message sns_offbody_detect_event
-{
- // Detected state
- required sns_offbody_detect_event_type state = 1 [default = SNS_OFFBODY_DETECT_EVENT_TYPE_UNKNOWN];
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_pedometer.proto b/prebuilt/system/etc/sensors/proto/sns_pedometer.proto
deleted file mode 100644
index 800ac74..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_pedometer.proto
+++ /dev/null
@@ -1,57 +0,0 @@
-// @file sns_pedometer.proto
-//
-// Defines message types for the Pedometer Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The Pedometer Sensor detects steps taken by the user
-//
-// The Pedometer Step event is generated when the user takes a step.
-// The event includes the latest step count accumulated since activation.
-// All clients to Pedometer get the same step event.
-// The timestamp of the event indicates the time of the latest detected step.
-
-// Pedometer Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "pedometer"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Pedometer Sensor
-enum sns_pedometer_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_PEDOMETER_MSGID_SNS_STEP_EVENT = 1028;
-
- //send to client immediatly to inform current step count
- //msg body same as sns_step_event
- SNS_PEDOMETER_MSGID_SNS_STEP_EVENT_CONFIG = 775;
-}
-
-// Events types from Pedometer Sensor
-message sns_step_event
-{
- //an incrementing step count
- required uint32 step_count = 1;
-}
-
-message sns_step_event_config
-{
- //current step count
- required uint32 step_count = 1;
-}
-
-
-// Stream events:
-//
-// The sns_step_event message is used to publish updated step count
-//
-// Pedometer does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_pedometer_wrist.proto b/prebuilt/system/etc/sensors/proto/sns_pedometer_wrist.proto
deleted file mode 100644
index 65a6348..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_pedometer_wrist.proto
+++ /dev/null
@@ -1,56 +0,0 @@
-// @file sns_pedometer_wrist.proto
-//
-// Defines message types for the Pedometer_wrist Sensor.
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The Pedometer_wrist Sensor detects steps taken by the user
-//
-// The Pedometer_wrist Step event is generated when the user takes a step.
-// The event includes the latest step count accumulated since activation.
-// All clients to Pedometer_wrist get the same step event.
-// The timestamp of the event indicates the time of the latest detected step.
-
-// Pedometer_wrist Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "pedometer_wrist"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Pedometer_wrist Sensor
-enum sns_pedometer_wrist_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_PEDOMETER_WRIST_MSGID_SNS_PEDOMETER_STEP_EVENT = 1028;
- //send to client immediatly to inform current step count
- //msg body same as sns_step_event
- SNS_PEDOMETER_WRIST_MSGID_SNS_PEDOMETER_STEP_EVENT_CONFIG = 775;
-}
-
-// Events types from Pedometer_wrist Sensor
-message sns_pedometer_step_event
-{
- //an incrementing step count
- required uint32 step_count = 1;
-}
-
-message sns_pedometer_step_event_config
-{
- //current step count
- required uint32 step_count = 1;
-}
-
-
-// Stream events:
-//
-// The sns_step_event message is used to publish updated step count
-//
-// Pedometer_wrist does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_physical_sensor_test.proto b/prebuilt/system/etc/sensors/proto/sns_physical_sensor_test.proto
deleted file mode 100644
index f15c7f4..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_physical_sensor_test.proto
+++ /dev/null
@@ -1,80 +0,0 @@
-// @file sns_physical_sensor_test.proto
-//
-// Defines test API message types for physical sensors.
-//
-// All physical Sensor drivers are required to use this API to support
-// self-test. SNS_PHYSICAL_SENSOR_TEST_TYPE_COM is a mandatory test type and must be
-// implemented in all physical Sensor drivers. Any new or device-specific
-// test type may be defined in the Sensor-specific API.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_physical_sensor_test_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Test config request to a physical Sensor
- SNS_PHYSICAL_SENSOR_TEST_MSGID_SNS_PHYSICAL_SENSOR_TEST_CONFIG = 515;
-
- // Test event message from a physical Sensor
- SNS_PHYSICAL_SENSOR_TEST_MSGID_SNS_PHYSICAL_SENSOR_TEST_EVENT = 1026;
-}
-
-// Supported test types for physical sensors
-enum sns_physical_sensor_test_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Software test.
- SNS_PHYSICAL_SENSOR_TEST_TYPE_SW = 0;
-
- // Sensor Hardware test.
- SNS_PHYSICAL_SENSOR_TEST_TYPE_HW = 1;
-
- // Factory test used for Sensor calibration.
- SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY = 2;
-
- // Communication bus test.
- SNS_PHYSICAL_SENSOR_TEST_TYPE_COM = 3;
-}
-
-// Physical Sensor test configuration request
-message sns_physical_sensor_test_config
-{
- // Requested test type.
- required sns_physical_sensor_test_type test_type = 1;
-}
-
-// Physical Sensor test event
-message sns_physical_sensor_test_event
-{
- // Result if the test execution was successful:
- // true for success
- // false for failure
- required bool test_passed = 1 [default = true];
-
- // test_type from sns_physical_sensor_test_config that
- // this event corresponds to
- required sns_physical_sensor_test_type test_type = 2 [default = SNS_PHYSICAL_SENSOR_TEST_TYPE_COM];
-
- // Driver specific test data. This field can be used
- // to pass additional information like failure codes, debug data, etc.
- optional bytes test_data = 3;
-}
-
-// Self-test and streaming concurrency requirements:
-// 1. If the sensor is streaming and there is a client request to run
-// self-test (any test type) then the driver:
-// a. Pauses the stream
-// b. Executes the self-test request to completion
-// c. Resumes stream
-// 2. If the self-test is running and there is a client request to start
-// a sensor stream then the driver:
-// a. Rejects the stream request
-// b. Continues executing the self-test request to completion
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_pose_6dof.proto b/prebuilt/system/etc/sensors/proto/sns_pose_6dof.proto
deleted file mode 100644
index 4ba9ee2..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_pose_6dof.proto
+++ /dev/null
@@ -1,70 +0,0 @@
-// @file sns_pose_6dof.proto
-//
-// Defines the API for Pose Six Degrees of Freedom sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A pose 6dof sensor events consists of a rotation expressed as a quaternion
-// and a translation expressed in SI units. Pose of the device is defined as
-// the orientation of the device from a Earth Centered Earth Fixed frame and
-// the translation from an arbitrary point at subscription.
-//
-// ## Pose 6DOF sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "pose_6dof"
-//
-// ## Request Message: sns_std_sensor_config
-// sns_std_sensor_config::sample_rate is used to specify the sampling rate (Hz)
-// of the Pose 6DOF sensor. Sensor will generate data events at this rate.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the Pose 6DOF sensor will be populated in sns_std_sensor_event
-//
-// A Pose 6DOF sensor reports the orientation of the device relative
-// to the East-North-Up coordinates frame. It is obtained by
-// integration of accelerometer and gyroscope readings.
-// The East-North-Up coordinate system is defined as a direct
-// orthonormal basis where:
-//
-// - X points east and is tangential to the ground.
-// - Y points north and is tangential to the ground.
-// - Z points towards the sky and is perpendicular to the ground.
-//
-// The orientation is represented by the rotation necessary to align
-// the East-North-Up coordinates with the device's coordinates. That is,
-// applying the rotation to the world frame (X,Y,Z) would align them with
-// the device coordinates (x,y,z).
-//
-// The rotation can be seen as rotating the device by an angle theta around an
-// axis rot_axis to go from the reference (East-North-Up aligned) device
-// orientation to the current device orientation. The rotation is encoded
-// as the four unitless x, y, z, w components of a unit quaternion:
-//
-// sns_std_sensor_event::data[0] = x*sin(theta/2)
-// sns_std_sensor_event::data[1] = y*sin(theta/2)
-// sns_std_sensor_event::data[2] = z*sin(theta/2)
-// sns_std_sensor_event::data[3] = cos(theta/2)
-// sns_std_sensor_event::data[4] = Translation along x axis from an arbitrary origin.
-// sns_std_sensor_event::data[5] = Translation along y axis from an arbitrary origin.
-// sns_std_sensor_event::data[6] = Translation along z axis from an arbitrary origin.
-// sns_std_sensor_event::data[7] = Delta quaternion rotation x*sin(theta/2)
-// sns_std_sensor_event::data[8] = Delta quaternion rotation y*sin(theta/2)
-// sns_std_sensor_event::data[9] = Delta quaternion rotation z*sin(theta/2)
-// sns_std_sensor_event::data[10] = Delta quaternion rotation cos(theta/2)
-// sns_std_sensor_event::data[11] = Delta translation along x axis.
-// sns_std_sensor_event::data[12] = Delta translation along y axis.
-// sns_std_sensor_event::data[13] = Delta translation along z axis.
-// sns_std_sensor_event::data[14] = Sequence number; ascending sequentially from 0
-
-// Where:
-// - the x, y and z fields of rot_axis are the East-North-Up coordinates
-// of a unit length vector representing the rotation axis
-// - theta is the rotation angle
-//
-// sns_std_sensor_event::status specifies the reliability of the sample value
-// value is of type sns_std_sensor_sample_status. see sns_std_sensor.proto for
-// details.
diff --git a/prebuilt/system/etc/sensors/proto/sns_ppg.proto b/prebuilt/system/etc/sensors/proto/sns_ppg.proto
deleted file mode 100644
index c3fc279..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ppg.proto
+++ /dev/null
@@ -1,43 +0,0 @@
-// @file sns_ppg.proto
-//
-// Defines the API for PPG Sensors.
-//
-// Copyright (c) 2017-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-
-// Attribute requirements:
-// The PPG Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "ppg".
-// 2. SNS_STD_SENSOR_ATTRID_RATES attribute values in Hz.
-
-// Handling stream requests:
-// 1. The PPG Sensor handles the sns_std_sensor_config
-// message request with msgid SNS_STD_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG
-// for all stream enable/update requests.
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_STREAMING
-// 2. The PPG Sensor uses batching_period item in
-// sns_std_request as the requested batching rate to determine
-// hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The PPG Sensor publishes PPG data stream events
-// using the sns_std_sensor_event message.
-// 2. Each stream event contains three output data fields
-// data[0] => PPG ch1
-// data[1] => PPG ch2
-// data[2] => 128 if touched, 0 otherwise
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The PPG Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_pressure.proto b/prebuilt/system/etc/sensors/proto/sns_pressure.proto
deleted file mode 100644
index 2c62bdc..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_pressure.proto
+++ /dev/null
@@ -1,65 +0,0 @@
-// @file sns_pressure.proto
-//
-// Defines the API for Pressure Sensors.
-// All Pressure Sensor drivers are required to comply with this API.
-// Any new functionality for Pressure Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Pressure Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "pressure".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute values in hectoPascal/LSB unit.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in hectoPascal unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Pressure Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-// 2. If the physical sensor supports hardware FIFO then the Pressure
-// Sensor uses batching_period item in sns_std_request as the requested
-// batching rate to determine hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Pressure Sensor publishes atmospheric pressure data stream events
-// using the sns_std_sensor_event message.
-// 2. Each stream event contains one output data field where data is
-// factory calibrated and ordered as:
-// data[0] = Pressure data in hPa (hectoPascal)
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Pressure Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Pressure Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The Pressure Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Pressure Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Pressure Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Pressure Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_proximity.proto b/prebuilt/system/etc/sensors/proto/sns_proximity.proto
deleted file mode 100644
index 257725f..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_proximity.proto
+++ /dev/null
@@ -1,111 +0,0 @@
-// @file sns_proximity.proto
-//
-// Defines the API for Proximity Sensors.
-// All Proximity Sensor drivers are required to comply with this API.
-// Any new functionality for Proximity Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2019 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Proximity Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "proximity".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute is not applicable since this
-// is an event sensor.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in cm unit (proximity distance).
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Proximity Sensor supports both streaming and on-change
-// modes and the operating mode is configured in the Registry.
-// 2. The streaming Proximity Sensor handles the sns_std_sensor_config request
-// for all stream enable/update requests.
-// 3. The on-change Proximity Sensor handles the
-// SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG request for
-// all on-change enable/update requests.
-// 4. In on-change mode the Sensor uses interrupt operation and reports
-// samples only for NEAR/FAR transitions.
-
-// Message IDs for proximity Sensor
-enum sns_proximity_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_proximity_event
- // Purpose: A non-recurring output data event from the proximity sensor to its client.
- SNS_PROXIMITY_MSGID_SNS_PROXIMITY_EVENT = 769;
-
- // Uses message: sns_proximity_event_recurrent
- // Purpose: A recurring output data event from the proximity sensor to its client.
- SNS_PROXIMITY_MSGID_SNS_PROXIMITY_EVENT_RECURRENT = 1031;
-}
-
-enum sns_proximity_event_type {
- option (nanopb_enumopt).long_names = false;
-
- SNS_PROXIMITY_EVENT_TYPE_FAR = 0;
- SNS_PROXIMITY_EVENT_TYPE_NEAR = 1;
-}
-
-// Events types from proximity Sensor
-message sns_proximity_event
-{
- // Proximity NEAR/FAR output event
- required sns_proximity_event_type proximity_event_type = 1 [default = SNS_PROXIMITY_EVENT_TYPE_FAR];
-
- // Proimity sensor raw data
- required uint32 raw_adc = 2;
-
- // Proximity sensor sample status
- required sns_std_sensor_sample_status status = 3 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-message sns_proximity_event_recurrent
-{
- // Proximity NEAR/FAR output event
- required sns_proximity_event_type proximity_event_type = 1 [default = SNS_PROXIMITY_EVENT_TYPE_FAR];
-
- // Proimity sensor raw data
- required uint32 raw_adc = 2;
-
- // Proximity sensor sample status
- required sns_std_sensor_sample_status status = 3 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-// Handling stream events:
-// 1. The Proximity Sensor publishes object proximity data stream events
-// using sns_proximity_event message.
-// 2. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 3. The Proximity Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is a change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-
-// Handling self-test requests:
-// 1. The Proximity Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Proximity Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API. The factory test for Proximity Sensor calibrates
-// the sensor to detect an object (including light and dark colored)
-// at 5cm distance from the physical sensor.
-// 3. The Proximity Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Proximity Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_psmd.proto b/prebuilt/system/etc/sensors/proto/sns_psmd.proto
deleted file mode 100644
index c3eab9f..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_psmd.proto
+++ /dev/null
@@ -1,59 +0,0 @@
-// @file sns_psmd.proto
-//
-// Defines the API for Persistent Stationary/Motion Detection Sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// A persistent stationary/motion sensor reports once
-// - The device is moving/not still
-// - The device is detected to be still/stationary
-// The period of time to monitor for motion and stationarity should be greater
-// than 5 seconds, and less than 10 seconds. After reporting, conceptually
-// the algorithm's state is reset, and detection begins again.
-//
-// Motion here refers to any mechanism in which the device is causes to be
-// moved in its inertial frame. eg: Picking up the device and walking with it
-// to a nearby room may trigger motion whereas keeping the device on a table
-// on a smooth train moving at constant velocity may not trigger motion.
-//
-// Stationarity here refers to absolute stationarity. eg: device on desk.
-//
-// ## Persistent Stationary/Motion Detect sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "psmd"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Message IDs for Persistent Stationary/Motion Sensor
-enum sns_psmd_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Configuration Request
- SNS_PSMD_MSGID_SNS_PSMD_CONFIG = 512;
-
- // Empty Event
- // Indicates that the requested state has been detected
- SNS_PSMD_MSGID_SNS_PSMD_EVENT = 768;
-}
-
-// Detected states supported by the PSM Detector
-enum sns_psmd_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_PSMD_TYPE_STATIONARY = 0;
- SNS_PSMD_TYPE_MOTION = 1;
-}
-
-// Configuration Message
-// Used to specify the PSMD configuration
-message sns_psmd_config
-{
- // Which detector type to enable
- required sns_psmd_type type = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_registry.proto b/prebuilt/system/etc/sensors/proto/sns_registry.proto
deleted file mode 100644
index e671efe..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_registry.proto
+++ /dev/null
@@ -1,65 +0,0 @@
-// @file sns_registry.proto
-//
-// Sensors Registry message definitions for internal and external clients
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-// Registry Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "registry"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_SINGLE_OUTPUT
-
-// Registry Sensor message IDs:
-enum sns_registry_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_REGISTRY_MSGID_SNS_REGISTRY_READ_REQ = 512;
- SNS_REGISTRY_MSGID_SNS_REGISTRY_WRITE_REQ = 513;
- SNS_REGISTRY_MSGID_SNS_REGISTRY_READ_EVENT = 514;
-}
-
-message sns_registry_data
-{
- message item
- {
- option (nanopb_msgopt).no_unions = true;
-
- // Item name (i.e. Only item-specific name, sans group name)
- required string name = 1;
- optional fixed32 version = 2;
-
- oneof data
- {
- sns_registry_data subgroup = 10;
- string str = 11;
- float flt = 12;
- sfixed64 sint = 13;
- }
- }
- repeated item items = 3;
-}
-
-message sns_registry_read_req
-{
- // Full name of the item or group to be read
- required string name = 1;
-}
-
-message sns_registry_write_req
-{
- // Full name of the group to be written
- required string name = 1;
-
- required sns_registry_data data = 2;
-}
-
-message sns_registry_read_event
-{
- // Full name of the group which was read
- required string name = 1;
-
- required sns_registry_data data = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_remote_proc_state.proto b/prebuilt/system/etc/sensors/proto/sns_remote_proc_state.proto
deleted file mode 100644
index 05777ee..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_remote_proc_state.proto
+++ /dev/null
@@ -1,63 +0,0 @@
-// @file sns_remote_proc_state.proto
-//
-// Defines standard message types for the Remote Processor State sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_type.proto";
-
-// remote_proc_state sensor receives remote processor state
-// notifications and sends these notifications to its clients
-
-// remote_proc_state Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_NAME: "Remote Processor State"
-// SNS_STD_SENSOR_ATTRID_TYPE: "remote_proc_state"
-// SNS_STD_SENSOR_ATTRID_VENDOR: "QTI"
-
-enum sns_remote_proc_state_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_remote_proc_state_config
- // Config request to receive remote processor stat updates
- SNS_REMOTE_PROC_STATE_MSGID_SNS_REMOTE_PROC_STATE_CONFIG = 512;
-
-
- // Uses message: sns_remote_proc_state_event
- // This event is generated when the remote_proc_state service
- // sends out the remote processor state change notification
- SNS_REMOTE_PROC_STATE_MSGID_SNS_REMOTE_PROC_STATE_EVENT = 1024;
-}
-
-// Remote processor state config request
-// Note: Currently the only supported processor is Apps:
-// SNS_STD_PROCESSOR_APSS
-message sns_remote_proc_state_config
-{
- // Requested processor type
- required sns_std_client_processor proc_type = 1;
-}
-
-// Supported processor state event types
-enum sns_remote_proc_state_event_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Processor is suspended
- SNS_REMOTE_PROC_STATE_SUSPEND = 0;
-
- // Processor is awake
- SNS_REMOTE_PROC_STATE_AWAKE = 1;
-}
-
-// Remote processor state event
-message sns_remote_proc_state_event
-{
- // Processor type whose state is updated
- required sns_std_client_processor proc_type = 1;
-
- // Event type with state of the processor
- required sns_remote_proc_state_event_type event_type = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_resampler.proto b/prebuilt/system/etc/sensors/proto/sns_resampler.proto
deleted file mode 100644
index 8c9b7d7..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_resampler.proto
+++ /dev/null
@@ -1,90 +0,0 @@
-// @file sns_resampler.proto
-//
-// Defines standard message types for the Resampler
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std.proto";
-import "sns_std_sensor.proto";
-import "sns_std_event_gated_sensor.proto";
-
-// Resampler Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "resampler"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_STREAMING
-
-// Sensor output event:
-// Resampler use sns_std_sensor_event for it's output event
-
-enum sns_resampler_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_RESAMPLER_MSGID_SNS_RESAMPLER_CONFIG = 512;
- SNS_RESAMPLER_MSGID_SNS_RESAMPLER_CONFIG_EVENT = 776;
-}
-
-// Type of requested resampled rate
-enum sns_resampler_rate
-{
- option (nanopb_enumopt).long_names = false;
-
- // Requested resampled rate is fixed
- SNS_RESAMPLER_RATE_FIXED = 0;
-
- // Requested resampled rate is the minimum required
- SNS_RESAMPLER_RATE_MINIMUM = 1;
-}
-
-// Resampler output quality
-enum sns_resampler_quality
-{
- option (nanopb_enumopt).long_names = false;
-
- // Resampler output is the same as input sensor data
- SNS_RESAMPLER_QUALITY_CURRENT_SAMPLE = 0;
-
- // Resampler output is filtered down from input sensor data
- SNS_RESAMPLER_QUALITY_FILTERED = 1;
-
- // Resampler output is interpolated and filtered down from input sensor data
- SNS_RESAMPLER_QUALITY_INTERPOLATED_FILTERED = 2;
-
- // Resampler output is interpolated down from input sensor data
- SNS_RESAMPLER_QUALITY_INTERPOLATED = 3;
-}
-
-// Configuration Message
-// Used to either request for a new configuration of the Resampler Sensor or
-// alter an already existing configuration
-message sns_resampler_config
-{
- // UID of the Sensor to be resampled
- required sns_std_suid sensor_uid = 1;
-
- // The requested resampled rate in Hz
- required float resampled_rate = 2;
-
- // The requested rate type as defined in sns_resampler_rate
- required sns_resampler_rate rate_type = 3;
-
- // Set to true to enable filtering, else false
- required bool filter = 4;
-
- // Set to true if sensor to be resampled is event gated
- optional bool event_gated = 5;
-
- // Number of axes of the sensor data
- optional uint32 axis_cnt = 6;
-}
-
-// Config event to inform client sample quality
-// of all subsequent sns_std_sensor_event from resampler
-message sns_resampler_config_event
-{
- // Quality of the resampled sensor data as defined in
- // sns_resampler_quality
- required sns_resampler_quality quality = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_rgb.proto b/prebuilt/system/etc/sensors/proto/sns_rgb.proto
deleted file mode 100644
index 63a63ab..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_rgb.proto
+++ /dev/null
@@ -1,78 +0,0 @@
-// @file sns_rgb.proto
-//
-// Defines the API for RGB Sensors.
-// All RGB Sensor drivers are required to comply with this API.
-// Any new functionality for RGB Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The RGB Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "rgb".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute values in µW/cm2/LSB unit.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in µW/cm2 unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-
-// Handling stream requests:
-// 1. The RGB Sensor supports both streaming and on-change
-// modes and the operating mode is configured in the Registry.
-// 2. The streaming RGB Sensor handles the sns_std_sensor_config
-// request for all stream enable/update requests.
-// 3. The on-change RGB Sensor handles the
-// SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG request for
-// all stream enable/update requests.
-// 4. In on-change mode the Sensor uses interrupt operation and reports
-// samples for only significant change in R/G/B/clear channel irradiance.
-// Example: +/- 10% change.
-
-// Handling stream events:
-// 1. The RGB Sensor publishes color data in ambient light using the
-// sns_std_sensor_event message.
-// 2. Each stream event contains six output data fields where data is
-// factory calibrated and ordered as:
-// data[0] = Red channel irradiance in µW/cm2
-// data[1] = Green channel irradiance in µW/cm2
-// data[2] = Blue channel irradiance in µW/cm2
-// data[3] = Clear channel irradiance in µW/cm2
-// data[4] = Color Temperature in Kelvin
-// data[5] = raw clear channel ADC value
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The RGB Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The RGB Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The RGB Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The RGB Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API. The factory test for RGB Sensor calibrates
-// the sensor such that it's output is comparable to a standard Chromemeter
-// output in any lighting condition.
-// 3. The RGB Sensor could implement other test types.
-
-// Handling test events:
-// 1. The RGB Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_rmd.proto b/prebuilt/system/etc/sensors/proto/sns_rmd.proto
deleted file mode 100644
index 7b66ed1..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_rmd.proto
+++ /dev/null
@@ -1,51 +0,0 @@
-
-// @file sns_rmd.proto
-//
-// Defines message types for the Absolute Motion Detector (RMD) Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// RMD calculates motion and stationary states. RMD will initially start in an
-// unknown state, and later transition to motion or stationary.
-
-// RMD Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "rmd"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for RMD Sensor
-enum sns_rmd_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_RMD_MSGID_SNS_RMD_EVENT = 772;
-}
-
-enum sns_rmd_event_type
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_RMD_EVENT_TYPE_UNKNOWN = 0;
- SNS_RMD_EVENT_TYPE_STATIONARY = 1;
- SNS_RMD_EVENT_TYPE_MOTION = 2;
-}
-
-message sns_rmd_event
-{
- // RMD motion state
- required sns_rmd_event_type state = 1 [default = SNS_RMD_EVENT_TYPE_UNKNOWN];
-}
-
-// Stream events:
-//
-// The sns_rmd_event message is used to publish updated state
-//
-// RMD does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_rotv.proto b/prebuilt/system/etc/sensors/proto/sns_rotv.proto
deleted file mode 100644
index 8dde922..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_rotv.proto
+++ /dev/null
@@ -1,53 +0,0 @@
-// @file sns_rotv.proto
-//
-// Defines the API for Rotation Vector sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "sns_std_sensor.proto";
-
-// A ROTV sensor reports the orientation of the device relative to the
-// East-North-Up coordinates frame. It is obtained by integration of
-// accelerometer, gyroscope, and magnetometer readings.
-//
-// ## ROTV sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "rotv"
-//
-// ## Request Message: sns_std_sensor_config
-// sns_std_sensor_config::sample_rate is used to specify the sampling rate (Hz)
-// of the ROTV sensor. Sensor will generate data events at this rate.
-//
-// ## Event Message: sns_std_sensor_event
-// Output of the ROTV sensor will be populated in sns_std_sensor_event
-//
-// The East-North-Up coordinate system is defined as a direct orthonormal
-// basis where:
-// - X points east and is tangential to the ground.
-// - Y points north and is tangential to the ground.
-// - Z points towards the sky and is perpendicular to the ground.
-//
-// The orientation is represented by the rotation necessary to align
-// the East-North-Up coordinates with the device's coordinates. That is,
-// applying the rotation to the world frame (X,Y,Z) would align them with
-// the device coordinates (x,y,z).
-//
-// The rotation can be seen as rotating the device by an angle theta around an
-// axis rot_axis to go from the reference device orientation to the current
-// device orientation. The rotation is encoded as the four unitless x, y, z, w
-// components of a unit quaternion:
-// sns_std_sensor_event::data[0] = rot_axis.x*sin(theta/2)
-// sns_std_sensor_event::data[1] = rot_axis.y*sin(theta/2)
-// sns_std_sensor_event::data[2] = rot_axis.z*sin(theta/2)
-// sns_std_sensor_event::data[3] = cos(theta/2)
-//
-// Where:
-// - the x, y and z fields of rot_axis are the East-North-Up coordinates
-// of a unit length vector representing the rotation axis
-// - theta is the rotation angle
-//
-// sns_std_sensor_event::status specifies the reliability of the sample value
-// value is of type sns_std_sensor_sample_status. see sns_std_sensor.proto for
-// details.
diff --git a/prebuilt/system/etc/sensors/proto/sns_sar.proto b/prebuilt/system/etc/sensors/proto/sns_sar.proto
deleted file mode 100644
index 6c69bef..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_sar.proto
+++ /dev/null
@@ -1,93 +0,0 @@
-// @file sns_sar.proto
-//
-// Defines the API for Specific Absorption Rate (SAR) Sensors.
-// SAR sensors typically detect human object proximity using change in capacitance
-// levels of copper touch pads/buttons.
-// All SAR Sensor drivers are required to comply with this API.
-// Any new functionality for SAR Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-
-// Attribute requirements:
-// The SAR Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "sar".
-// Each SAR sensor (example individual capacitive button) shall be published
-// as an independent sensor with a unique Sensor UID.
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute is not applicable since this
-// is an event sensor.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in cm unit (proximity distance).
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The SAR Sensor handles the SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// message ID for all stream enable/update requests.
-// 2. The SAR Sensor operates in on-change mode and reports
-// samples only for object (typically human) NEAR/FAR transitions.
-// Since it is an on-change sensor, the sar sensor publishes an initial data event
-// event for each new client request.
-
-// Message IDs for SAR Sensor
-enum sns_sar_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_sar_event
- // Purpose: An output data event from the SAR sensor to it's client.
- SNS_SAR_MSGID_SNS_SAR_EVENT = 769;
-}
-
-enum sns_sar_event_type {
- option (nanopb_enumopt).long_names = false;
-
- SNS_SAR_EVENT_TYPE_FAR = 0;
- SNS_SAR_EVENT_TYPE_NEAR = 1;
-}
-
-// Events types from SAR Sensor
-message sns_sar_event
-{
- // SAR NEAR/FAR output event
- required sns_sar_event_type sar_event_type = 1 [default = SNS_SAR_EVENT_TYPE_FAR];
-
- // SAR sensor raw data.
- // Format of this data is driver specific.
- optional bytes additional_sar_data = 2;
-
- // SAR sensor sample status
- required sns_std_sensor_sample_status status = 3 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-// Handling stream events:
-// 1. The SAR Sensor publishes human object proximity data events using sns_sar_event message.
-// 2. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 3. The SAR Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-
-// Handling self-test requests:
-// 1. The SAR Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The SAR Sensor may implement SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The SAR Sensor could implement other test types.
-
-// Handling test events:
-// 1. The SAR Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_sensor_temperature.proto b/prebuilt/system/etc/sensors/proto/sns_sensor_temperature.proto
deleted file mode 100644
index d9da6b9..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_sensor_temperature.proto
+++ /dev/null
@@ -1,66 +0,0 @@
-// @file sns_sensor_temperature.proto
-//
-// Defines the API for physical Sensor Temperature Sensors.
-// All Sensor Temperature Sensor drivers are required to comply with this API.
-// Any new functionality for Sensor Temperature Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Sensor Temperature Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "sensor_temperature".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in degrees Celsius/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in degrees Celsius unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Sensor Temperature Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-// 2. If the physical sensor supports hardware FIFO then the Sensor Temperature
-// Sensor uses batching_period item in sns_std_request as the requested
-// batching rate to determine hardware FIFO watermark.
-
-// Handling stream events:
-// 1. The Sensor Temperature Sensor publishes physical sensor temperature data
-// stream events using the sns_std_sensor_event message.
-// 2. Each stream event contains one output data field where data is
-// factory calibrated and ordered as:
-// data[0] = physical Sensor Temperature data in degrees Celsius
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Sensor Temperature Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Sensor Temperature Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-
-// Handling self-test requests:
-// 1. The Sensor Temperature Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Sensor Temperature Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Sensor Temperature Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Sensor Temperature Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_sig_motion.proto b/prebuilt/system/etc/sensors/proto/sns_sig_motion.proto
deleted file mode 100644
index 9890861..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_sig_motion.proto
+++ /dev/null
@@ -1,33 +0,0 @@
-// @file sns_sig_motion.proto
-//
-// Defines the API for Significant Motion Detection Sensors.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// A significant motion sensor reports once if "significant motion"
-// is detected. After reporting, conceptually the algorithm's state is reset,
-// and detection begins again.
-//
-// ## Significant Motion sensor attributes:
-// SNS_STD_SENSOR_ATTRID_TYPE is "sig_motion"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-//
-// ## Request Message: SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG
-// No configuration is available for this sensor.
-//
-// ## Event Message: SNS_SIG_MOTION_MSGID_SNS_SIG_MOTION_EVENT
-// Reported upon new detection of significant motion.
-
-// Message IDs for Significant Motion Detect Sensor
-enum sns_sig_motion_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Empty Message
- SNS_SIG_MOTION_MSGID_SNS_SIG_MOTION_EVENT = 772;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_signal_sensor.proto b/prebuilt/system/etc/sensors/proto/sns_signal_sensor.proto
deleted file mode 100644
index 3269575..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_signal_sensor.proto
+++ /dev/null
@@ -1,47 +0,0 @@
-// @file sns_signal_sensor.proto
-//
-// Defines standard message types for the Signal Sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-// Signal sensor
-//
-// The signal sensor provides a mechanism to turn asynchronous callbacks into
-// events that are passed to the client. The client subscribes to this sensor
-// using the sns_signal_sensor_req message.
-//
-// The signal sensor provides a thread and a flag to the client via the
-// sns_signal_sensor_token_event event upon subscribing to the service.
-
-// Message IDs
-enum sns_signal_sensor_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_SIGNAL_SENSOR_MSGID_SNS_SIGNAL_SENSOR_REQ = 512;
- SNS_SIGNAL_SENSOR_MSGID_SNS_SIGNAL_SENSOR_TOKEN = 1024;
- SNS_SIGNAL_SENSOR_MSGID_SNS_SIGNAL_SENSOR_NOTIFY = 1025;
-}
-
-// Signal sensor request
-//
-// Subscribe to the signal sensor.
-message sns_signal_sensor_req
-{
- required bool enable = 1;
-}
-
-// Signal sensor token
-//
-// Provides the thread and flag to the client
-message sns_signal_sensor_token
-{
- required fixed64 thread = 1;
- required fixed32 flag = 2;
-}
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_sim.proto b/prebuilt/system/etc/sensors/proto/sns_sim.proto
deleted file mode 100644
index 256ee73..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_sim.proto
+++ /dev/null
@@ -1,30 +0,0 @@
-// @file sns_sim.proto
-//
-// Defines Header config packet strcture for finding out sim sensors config info
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_std_type.proto";
-
-enum sns_sim_msgid
-{
- option (nanopb_enumopt).long_names = false;
- // message not required
- // Purpose: Created only for Offline/Online Playback to inform end of the
- // file status to client
- SNS_SIM_MSGID_SNS_SIM_END_OF_THE_FILE_EVENT = 1027;
-}
-
-/*Header config packet proto message. It will come as a first packet in event dlf file*/
-message header_info {
- message sensor_info{
- required sns_std_suid suid = 1;
- required string data_type = 2;
- repeated sns_std_attr attributes = 3;
- }
- repeated sensor_info info= 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_sim_legacy.proto b/prebuilt/system/etc/sensors/proto/sns_sim_legacy.proto
deleted file mode 100644
index 7067fa3..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_sim_legacy.proto
+++ /dev/null
@@ -1,32 +0,0 @@
-// @file sns_sim_legacy.proto
-//
-// Defines standard message types for the Simulation Sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// Data Message
-// Data event generated by the simulation sensor.
-// Uses sns_std_sensor_event message defined in sns_std_sensor.proto
-// The data field of the sns_std_sensor_event message
-// contains a float array of length 3 with the following definition
-// 1) float data[0] to data[2]
-// containing the triaxial sensor data in floating point.
-// Units for different sensors are as follows
-// Accel: m/s2
-// Gyro: rad/s
-// 2) sns_std_sensor_sample_status status;
-// containing the sample status as defined by the sns_std_sensor_sample_status enum
-// in sns_std_sensor.proto
-
-// Configuration Message
-// Used to either request for a certain configuration of the Sim Sensor or
-// alter an already existing configuration of the Simulation Sensor
-// Uses sns_std_sensor_config defined in sns_std_sensor.proto
-// The message field definitions are as follows:
-// 1) float sample_rate
-// containing the required sample rate of the Sim sensor in hertz
diff --git a/prebuilt/system/etc/sensors/proto/sns_std.proto b/prebuilt/system/etc/sensors/proto/sns_std.proto
deleted file mode 100644
index 08897b4..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_std.proto
+++ /dev/null
@@ -1,128 +0,0 @@
-// @file sns_std.proto
-//
-// Defines standard messages used across multiple Sensor API definitions
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import public "sns_std_type.proto";
-
-// Framework-defined message IDs:
-enum sns_std_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Query a Sensor for all attributes
- // @event sns_std_error_event
- SNS_STD_MSGID_SNS_STD_ATTR_REQ = 1;
-
- // Flush a Sensor.
- // When a sensor receives a flush request it publishes any unpublished
- // samples. The sensor always publishes a SNS_STD_MSGID_SNS_STD_FLUSH_EVENT
- // event to indicate completion of a flush request.
- // All Sensors handle this flush request message.
- // Empty Message
- // @event sns_pb_flush_event
- SNS_STD_MSGID_SNS_STD_FLUSH_REQ = 2;
-
- // NOTE: 10 - 20 Are reserved for Client Manager
- // NOTE: 120-127 Are reserved
-
- // All published attributes for a Sensor
- SNS_STD_MSGID_SNS_STD_ATTR_EVENT = 128;
-
- // Indicates no further events will be generated in response to a flush req.
- // Empty Message
- SNS_STD_MSGID_SNS_STD_FLUSH_EVENT = 129;
-
- // Indicates an error has occurred
- SNS_STD_MSGID_SNS_STD_ERROR_EVENT = 130;
-
- // NOTE: 250-255 Are reserved
-}
-
-// Base message payload, from which all other Request payloads must extend
-// The message will be delivered decoded within the Sensor API
-message sns_std_request {
- message batch_spec {
- // Logically a timer will be registered for this many microseconds.
- // All events generated since the last timer expiration will be saved
- // until the next timer has fired. This period is interpreted as a maximum
- // period specified by the client; events may be delivered to client at a
- // faster rate (smaller batch period).
- // A batch period of 0 indicates that no batching shall occur.
- required uint32 batch_period = 1;
-
- // Sensor supporting Data Acquisition Engine shall support flush_period.
- // Sensor shall not drop data that is more recent than flush_period.
- // Sensor may drop data that is older than the flush_period.
- // Effective flush period may be smaller due to system constraints,
- // or larger in the case of a concurrent client with a larger value.
- // flush_period, if set, should be greater than or equal to batch_period.
- // If flush_period is less than batch period the behavior is undefined.
- // Value defaults to value set for batch_period; units in microseconds
- optional uint32 flush_period = 2;
-
- // If flush_only = true, the sensor should only send data to the client
- // on receiving a flush request or if the sensor cannot accumulate flush
- // period worth of data.
- optional bool flush_only = 3 [default = false];
-
- // If max_batch = true for all requests, the sensor should operate at
- // maximum batching capacity. If a request has both max_batch = true
- // and flush_only = true, flush_only takes precedence.
- optional bool max_batch = 4 [default = false];
- }
- // Batching is disabled by default
- optional batch_spec batching = 1;
-
- // Dynamic length payload, containing the actual data/configuration request
- // This payload will need to be decoded separately, using the Sensor-specific
- // header file. If the request does not contain any message body then this
- // field is not present.
- optional bytes payload = 2;
-
- // Set to true if a client intends to be a passive client. Else it is an
- // active client request. Absence of this field shall be treated as an active
- // request.
- // If all requests to the sensor are passive then it shall be in off
- // state and stop streaming.
- // If the sensor has at least one active request then it shall be enabled
- // and configured according to all active and passive requests.
- // When all active clients are flush_only then passive clients are also treated
- // as flush_only.
- // When all active clients are event gated then passive clients are also treated
- // as event gated.
- // delivery_type field in passive requests shall be configured as
- // SNS_CLIENT_DELIVERY_NO_WAKEUP.
- // Actively enabling one sensor shall not lead to enabling of another
- // sensor having only passive requests. For example: enabling gyro shall not
- // lead to enabling of sensor_temperature, and vice versa.
- optional bool is_passive = 3 [default = false];
-
-}
-
-// Query a Sensor for its list of attributes
-message sns_std_attr_req {
- // Register for updates when the attributes of a Sensor change
- // This option is not presently supported
- optional bool register_updates = 2;
-}
-
-// Contains all Sensor attributes; sent in response to an sns_std_attr_req,
-// or upon an attribute change to a registered Sensor
-message sns_std_attr_event {
- repeated sns_std_attr attributes = 1;
-}
-
-// An Error Event generated by a Sensor/Instance or the Framework
-message sns_std_error_event {
- // SNS_STD_ERROR_NOT_AVAILABLE - Transitory error in the Sensor; some data
- // may have been lost or dropped, but streaming should resume.
- // SNS_STD_ERROR_INVALID_STATE - Catastrophic error in the Sensor; do not
- // expect any further data. Client may try sending enable-request again.
- // SNS_STD_ERROR_NOT_SUPPORTED - Sensor received an unsupported request; or a
- // supported request at an unexpected time.
- required sns_std_error error = 1;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_std_event_gated_sensor.proto b/prebuilt/system/etc/sensors/proto/sns_std_event_gated_sensor.proto
deleted file mode 100644
index 46555c7..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_std_event_gated_sensor.proto
+++ /dev/null
@@ -1,45 +0,0 @@
-// @file sns_std_event_gated_sensor.proto
-//
-// Defines standard message types for Sensors with output streams that can be
-// gated on an event from another Sensor.
-// Example: "accel" Sensor can be gated by motion detect event published by
-// the "motion_detect" Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-enum sns_std_event_gated_sensor_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Message ID to send a gated request to a Sensor.
- // Note that the client is responsible to send separate
- // requests to the Sensor that provides the gating event.
- SNS_STD_EVENT_GATED_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG = 518;
-
- // An event gated Sensors uses this event message ID to indicate to it's
- // clients that the gated stream is converted to a non-gated stream.
- // This typically happens when the gating event occurs.
- // Example: When "accel" is gated on "motion_detect" and if the
- // motion detect interrupt fires then the "accel" Sensor publishes
- // this event to it's clients before the accel data stream starts.
- SNS_STD_EVENT_GATED_SENSOR_MSGID_GATED_REQ_CONVERTED_TO_NON_GATED = 772;
-}
-
-// Request and Event messages:
-// 1. An enable request to an event gated sensor uses message
-// sns_std_sensor_config with message ID
-// SNS_STD_EVENT_GATED_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG.
-// 2. An event gated sensor publishes an output event to it's clients when
-// the gated request is converted to a non-gated request. It uses event
-// message ID SNS_STD_EVENT_GATED_SENSOR_MSGID_GATED_REQ_CONVERTED_TO_NON_GATED
-// with no message payload.
-// 3. An output data event from an event gated sensor uses message
-// sns_std_sensor_event. See sns_std_sensor.proto and sensor-specific
-// proto file for details.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_std_sensor.proto b/prebuilt/system/etc/sensors/proto/sns_std_sensor.proto
deleted file mode 100644
index 2c1f46d..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_std_sensor.proto
+++ /dev/null
@@ -1,382 +0,0 @@
-// @file sns_std_sensor.proto
-//
-// Defines standard message types for all Sensors. All physical Sensors are
-// required to implement this API as is or derive from it. For all other
-// Sensors, these messages are highly recommended. That being said, Sensor
-// developers may choose to define Sensor-specific message API for any
-// new/Sensor-specific functionality.
-//
-// Copyright (c) 2016-2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_std_sensor_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- // Uses message: sns_std_sensor_config
- // Purpose:
- // 1. A stream request from a client to a sensor.
- // 2. A config/ack event from a sensor to the client.
- SNS_STD_SENSOR_MSGID_SNS_STD_SENSOR_CONFIG = 513;
-
- // Does not use any message body.
- // Purpose:
- // 1. An enable request from a client to an on-change sensor.
- // Subsequent request from same client will be treated as NOP
- // 2. A config/ack event from an on-change sensor to the client.
- SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG = 514;
-
- // Uses message: sns_std_sensor_physical_config_event
- // Purpose: A configuration event from a Physical Sensor (streaming and event)
- // to the client.
- SNS_STD_SENSOR_MSGID_SNS_STD_SENSOR_PHYSICAL_CONFIG_EVENT = 768;
-
- // Uses message: sns_std_sensor_event
- // Purpose: A data event from a Sensor.
- SNS_STD_SENSOR_MSGID_SNS_STD_SENSOR_EVENT = 1025;
-}
-
-// Status for each sensor sample
-enum sns_std_sensor_sample_status
-{
- option (nanopb_enumopt).long_names = false;
-
- // Sample is unreliable.
- SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE = 0;
-
- // Sample is low accuracy.
- SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_LOW = 1;
-
- // Sample is medium accuracy.
- SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_MEDIUM = 2;
-
- // Sample is high accuracy.
- SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH = 3;
-}
-
-// Attribute IDs available for use by Sensors
-// Some are marked as REQUIRED, and must be published by every Sensor. Others
-// are OPTIONAL, and may be only necessary for physical Sensors.
-//
-// Each Sensor may define their own custom attributes, using the form:
-// <proto_name>_attr_id. Attribute IDs have the following reserved ranges:
-// 0-511 : Held for sns_std_sensor_attr_id
-// 512-1023 : Reserved for internal QTI use
-// 1024-1535 : Available for use by Sensor developers
-enum sns_std_sensor_attr_id
-{
- option (nanopb_enumopt).long_names = false;
-
- // REQUIRED
- // String
- // Human-readable sensor name
- SNS_STD_SENSOR_ATTRID_NAME = 0;
-
- // REQUIRED
- // String
- // Human-readable vendor name
- SNS_STD_SENSOR_ATTRID_VENDOR = 1;
-
- // REQUIRED
- // String
- // Data Type used by this Sensor
- SNS_STD_SENSOR_ATTRID_TYPE = 2;
-
- // REQUIRED
- // Boolean
- // Whether this Sensor is available for clients
- SNS_STD_SENSOR_ATTRID_AVAILABLE = 3;
-
- // REQUIRED
- // Integer
- // Sensor version
- SNS_STD_SENSOR_ATTRID_VERSION = 4;
-
- // REQUIRED
- // [String]
- // .proto files specifying the incoming request and outgoing event messages
- SNS_STD_SENSOR_ATTRID_API = 5;
-
- // OPTIONAL
- // [Float]
- // Supported sample rates in Hz
- SNS_STD_SENSOR_ATTRID_RATES = 6;
-
- // OPTIONAL
- // [Float]
- // Supported resolutions
- SNS_STD_SENSOR_ATTRID_RESOLUTIONS = 7;
-
- // OPTIONAL
- // Integer
- // Supported FIFO depth in number of samples
- SNS_STD_SENSOR_ATTRID_FIFO_SIZE = 8;
-
- // OPTIONAL
- // [Integer]
- // Active currents in uA for all sns_attr_op_modes. Length of the array
- // of active currents must match the length of the array of operation modes.
- SNS_STD_SENSOR_ATTRID_ACTIVE_CURRENT = 9;
-
- // OPTIONAL
- // Integer
- // Inactive current in uA
- SNS_STD_SENSOR_ATTRID_SLEEP_CURRENT = 10;
-
- // OPTIONAL
- // [{float,float}]
- // Supported operating ranges
- SNS_STD_SENSOR_ATTRID_RANGES = 11;
-
- // OPTIONAL
- // String
- // Operating Modes ("LPM", "HIGH_PERF", "NORMAL", "OFF")
- SNS_STD_SENSOR_ATTRID_OP_MODES = 12;
-
- // OPTIONAL
- // Boolean
- // Whether the Sensor supports Data Ready Interrupt (DRI) or IBI
- // (In Band Interrupt).
- SNS_STD_SENSOR_ATTRID_DRI = 13;
-
- // OPTIONAL
- // Boolean
- // Whether a Sensor support synchronized streaming.
- SNS_STD_SENSOR_ATTRID_STREAM_SYNC = 14;
-
- // OPTIONAL
- // Integer
- // Encoded message size of the data event generated most often by the Sensor
- SNS_STD_SENSOR_ATTRID_EVENT_SIZE = 15;
-
- // REQUIRED
- // Integer: sns_std_sensor_stream_type
- // Streaming Type
- SNS_STD_SENSOR_ATTRID_STREAM_TYPE = 16;
-
- // OPTIONAL
- // Boolean
- // Whether this Sensor is dynamic (connected/disconnected at runtime)
- SNS_STD_SENSOR_ATTRID_DYNAMIC = 17;
-
- // OPTIONAL
- // Integer
- // When multiple Sensors of the same hardware exist, this attribute differentiates.
- SNS_STD_SENSOR_ATTRID_HW_ID = 18;
-
- // OPTIONAL
- // Integer: sns_std_sensor_rigid_body_type
- // The rigid body on which the Sensor is placed.
- SNS_STD_SENSOR_ATTRID_RIGID_BODY = 19;
-
- // OPTIONAL
- // float[12]
- // Location and orientation of sensor element in the device frame.
- SNS_STD_SENSOR_ATTRID_PLACEMENT = 20;
-
- // OPTIONAL
- // Boolean
- // Boolean: True for a physical sensor
- SNS_STD_SENSOR_ATTRID_PHYSICAL_SENSOR = 21;
-
- // OPTIONAL
- // [Integer]
- // List of supported self-test types from sns_physical_sensor_test_type.
- SNS_STD_SENSOR_ATTRID_PHYSICAL_SENSOR_TESTS = 22;
-
- // OPTIONAL
- // Float
- // Sensors chosen resolution in it's engineering units.
- SNS_STD_SENSOR_ATTRID_SELECTED_RESOLUTION = 23;
-
- // OPTIONAL
- // float[2]
- // Sensors chosen {min, max} range in it's engineering units.
- SNS_STD_SENSOR_ATTRID_SELECTED_RANGE = 24;
-
- // OPTIONAL
- // [float]
- // List of additional sample rates for low latency clients in Hz.
- // These are additional rates for low latency clients extended from list
- // of rates published in attribute SNS_STD_SENSOR_ATTRID_RATES.
- // This is supported for internal clients only. External clients shall not use this API.
- SNS_STD_SENSOR_ATTRID_ADDITIONAL_LOW_LATENCY_RATES = 25;
-
- // OPTIONAL
- // Boolean
- // Boolean: True if the sensor supports passive request, False otherwise.
- // If this attribute is not supported, then the sensor does not support passive requests.
- // Sensors that do not support passive requests, will service all requests as active requests.
- SNS_STD_SENSOR_ATTRID_PASSIVE_REQUEST = 26;
-}
-
-// Sensor stream configuration request
-// or configuration change message
-message sns_std_sensor_config
-{
- // Sample rate in Hz.
- required float sample_rate = 1;
-}
-
-// Sensor data event
-message sns_std_sensor_event
-{
- // Output data field for all Sensor.
- repeated float data = 1;
-
- // Event sample status.
- required sns_std_sensor_sample_status status = 2 [default = SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE];
-}
-
-// Stream types
-enum sns_std_sensor_stream_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Used for Sensors that report data periodically.
- // Example: accel, gyro, mag
- SNS_STD_SENSOR_STREAM_TYPE_STREAMING = 0;
-
- // Used for Sensors that report data only on change in value.
- // Example: proximity, hall
- SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE = 1;
-
- // Used for Sensors that have a single data event in reponse to a request.
- // Example: SUID, motion detect
- SNS_STD_SENSOR_STREAM_TYPE_SINGLE_OUTPUT = 2;
-}
-
-// Rigid body types
-enum sns_std_sensor_rigid_body_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Used for a Sensor mounted on the same rigid body as the display.
- SNS_STD_SENSOR_RIGID_BODY_TYPE_DISPLAY = 0;
-
- // Used for a Sensor mounted on the same rigid body as a keyboard.
- SNS_STD_SENSOR_RIGID_BODY_TYPE_KEYBOARD = 1;
-
- // Used for a Sensor that is mounted on an external device.
- SNS_STD_SENSOR_RIGID_BODY_TYPE_EXTERNAL = 2;
-}
-
-// Sensor stream configuration event
-message sns_std_sensor_config_event
-{
- // Current sample rate in Hz
- required float sample_rate = 1;
-}
-
-// Physical sensor stream configuration. This message reflects the current
-// configuration of the physical sensor.
-message sns_std_sensor_physical_config_event
-{
- // Current sample rate in Hz for streaming sensors or highest rate of value
- // change for on-change sensors. 0 if sensor is disabled.
- // Note: if stream will be synchronized via S4S or I3C, this is the sample
- // rate after synchronization is complete.
- optional float sample_rate = 1;
-
- // Current hardware water mark setting. 1 if FIFO not in use.
- optional uint32 water_mark = 2;
-
- // Sensor sample value min and max range
- repeated float range = 3 [(nanopb).max_count = 2];
-
- // Sensor sample value Resolution
- optional float resolution = 4;
-
- // Sensor operation mode
- // If all requests to the sensor are passive then it shall use
- // operating_mode = "OFF"
- optional string operation_mode = 5;
-
- // Sensor active current in uA
- optional uint32 active_current = 6;
-
- // Sensor streaming is synchronized via methods like S4S and/or I3C.
- // Note: if the stream is not yet synchronized, this field should be
- // false, and an additional config event sent with stream_is_synchronous
- // set to true once the clocks have been synchronized.
- optional bool stream_is_synchronous = 7;
-
- // Sensor has enabled Data Ready Interrupt
- optional bool dri_enabled = 8;
-
- // Current DAE water mark setting. 0 if non-DAE sensor.
- optional uint32 DAE_watermark = 9;
-
- // The sync anchor is only valid for polled or synchronized sensors.
- // It is a timestamp of a future (or past) sns_std_sensor_event.
- // For synchronous sensors: this may be used by clients to determine the
- // synchronized timeline before it is synchronized.
- optional uint64 sync_ts_anchor = 10;
-}
-
-// Attribute requirements:
-// The Physical Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_AVAILABLE attribute value (bool) as true when it's dependencies
-// are met and the hardware is present and responsive.
-// 2. SNS_STD_SENSOR_ATTRID_NAME attribute value (string) as the name of the sensor model.
-// 3. SNS_STD_SENSOR_ATTRID_VENDOR attribute value (string) as the name of the sensor vendor.
-// 4. SNS_STD_SENSOR_ATTRID_VERSION attribute value (decimal) as the version of the driver.
-// 5. SNS_STD_SENSOR_ATTRID_RATES attribute as a float array of supported sample rates in Hz
-// for streaming sensors. On-change sensors publish the highest rate of value change.
-// 6. SNS_STD_SENSOR_ATTRID_FIFO_SIZE attribute value (decimal) as the maximum FIFO depth in
-// number of sensor samples available to it when enabled standalone.
-// The value can be zero if FIFO is not supported.
-// 7. SNS_STD_SENSOR_ATTRID_ACTIVE_CURRENT attribute as an integer array representing active
-// currents in uA corresponding to the sns_attr_op_modes attribute.
-// 8. SNS_STD_SENSOR_ATTRID_SLEEP_CURRENT attribute value (float) as the current in uA when
-// the sensor is in power down mode.
-// 9. SNS_STD_SENSOR_ATTRID_OP_MODES attribute value as an array of string values
-// representing different hardware operating modes.
-// 10. SNS_STD_SENSOR_ATTRID_DRI attribute value (bool) as true when it supports
-// interrupt based streaming else false when polling.
-// The source of data ready interrupt (DRI) could be completion of measurement
-// cycle, FIFO water mark (if sns_attr_fifo_size value is greater than 0),
-// threshold, etc.
-// If the sensor is capable of streaming in both polling and DRI modes then
-// it publishes separate Sensors for each mode such that the one with DRI
-// publishes SNS_STD_SENSOR_ATTRID_DRI value as true and the one with polling
-// publishes SNS_STD_SENSOR_ATTRID_DRI as false.
-// 11. SNS_STD_SENSOR_ATTRID_STREAM_SYNC attribute value (bool) as true when it
-// it supports a synchronous streaming mechanism like S4S and/or I3C.
-// 12. SNS_STD_SENSOR_ATTRID_EVENT_SIZE attribute value (decimal) as number of bytes in the
-// output data event for the Sensor.
-// 13. SNS_STD_SENSOR_ATTRID_STREAM_TYPE attribute value (sns_std_sensor_stream_type) as the
-// supported stream type.
-// 14. SNS_STD_SENSOR_ATTRID_DYNAMIC attribute value (bool) to indicate whether the sensor
-// can be added at runtime.
-// 15. SNS_STD_SENSOR_ATTRID_HW_ID attribute value (string) to uniquely identify multiple
-// sensor hardware of the same model on a platform.
-// 16. SNS_STD_SENSOR_ATTRID_RIGID_BODY attribute value (sns_std_sensor_rigid_body_type) as the rigid
-// body on which the sensor is mounted.
-// 17. SNS_STD_SENSOR_ATTRID_PLACEMENT attribute value as the location and orientation of
-// the sensor hardware.
-// 18. SNS_STD_SENSOR_ATTRID_PHYSICAL_SENSOR attribute value (bool) to indicate if the sensor is
-// a physical sensor
-// 19. SNS_STD_SENSOR_ATTRID_PHYSICAL_SENSOR_TESTS attribute value as array of supported
-// sns_physical_sensor_test_type test types.
-// 20. SNS_STD_SENSOR_ATTRID_SELECTED_RESOLUTION attribute value chosen from the
-// SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute array.
-// 21. SNS_STD_SENSOR_ATTRID_SELECTED_RANGE attribute value chosen from the
-// SNS_STD_SENSOR_ATTRID_RANGES array.
-// 22. SNS_STD_SENSOR_ATTRID_ADDITIONAL_LOW_LATENCY_RATES attribute as a float array of supported
-// sample rates in Hz additional to rates in SNS_STD_SENSOR_ATTRID_RATES, this is only for low
-// latency clients like direct report mode.
-// See sensor specific .proto files for sensor specific attribute information.
-
-// Recommendation for device drivers to select configuration:
-// 1. Choose fastest sample_rate among all client requests.
-// 2. Choose fastest batch rate (using batch_period) among all client requests. For streaming clients,
-// treat batch rate equal to requested sample rate for that request.
-// 3. If HW FIFO is supported then:
-// a. If all requests are max_batch then the driver configures highest FIFO watermark.
-// If DAE is supported, the DAE watermark should be INT_MAX.
-// b. Else FIFO watermark is determined based on sample_rate from #1 and batch rate from #2.
diff --git a/prebuilt/system/etc/sensors/proto/sns_std_type.proto b/prebuilt/system/etc/sensors/proto/sns_std_type.proto
deleted file mode 100644
index 9d9f744..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_std_type.proto
+++ /dev/null
@@ -1,79 +0,0 @@
-// @file sns_std_type.proto
-//
-// Defines standard data types used across multiple Sensor API definitions
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-// Represents an unique Sensor
-message sns_std_suid {
- required fixed64 suid_low = 1;
- required fixed64 suid_high = 2;
-}
-
-// Represents an attribute value
-// Attribute values may be a single value, array of simple values, or
-// an array of complex tuples
-message sns_std_attr_value {
- // "data" submessage required to support recursion
- message data {
- option (nanopb_msgopt).no_unions = true;
- oneof value {
- sns_std_attr_value subtype = 1;
- string str = 2;
- float flt = 3;
- sfixed64 sint = 4;
- bool boolean = 5;
- }
- }
- repeated data values = 1;
-}
-
-// An individual attribute from a Sensor
-message sns_std_attr {
- // A standard list of attributes is available within sns_std_sensor_attr_id
- // Additional attributes may be defined by sensors, using the format:
- // <SENSOR_PROTO_NAME>_ATTRID_<ATTR_NAME> (e.g. SNS_ACCEL_ATTRID_ODR)
- // Additional IDs must fall within the range of 1024-2047
- required int32 attr_id = 1;
- // Attribute value
- required sns_std_attr_value value = 2;
-}
-
-// Error codes
-enum sns_std_error {
- option (nanopb_enumopt).long_names = false;
-
- /* No error occurred; success. */
- SNS_STD_ERROR_NO_ERROR = 0;
- /* Unfixable or internal error occurred. */
- SNS_STD_ERROR_FAILED = 1;
- /* This API is not supported or is not implemented. */
- SNS_STD_ERROR_NOT_SUPPORTED = 2;
- /* Message contains invalid data type,
- * e.g., unknown message ID, unknown registry group, or unexpected
- * Sensor UID. */
- SNS_STD_ERROR_INVALID_TYPE = 3;
- /* Catastrophic error; expect no further data */
- SNS_STD_ERROR_INVALID_STATE = 4;
- /* One or more argument values were outside of the valid range */
- SNS_STD_ERROR_INVALID_VALUE = 5;
- /* This operation is not available at this time */
- SNS_STD_ERROR_NOT_AVAILABLE = 6;
- /* This action was rejected due to the current policy settings */
- SNS_STD_ERROR_POLICY = 7;
-}
-
-//The enum contains all the processor types supported.
-enum sns_std_client_processor {
- option (nanopb_enumopt).long_names = false;
-
- SNS_STD_CLIENT_PROCESSOR_SSC = 0;
- SNS_STD_CLIENT_PROCESSOR_APSS = 1;
- SNS_STD_CLIENT_PROCESSOR_ADSP = 2;
- SNS_STD_CLIENT_PROCESSOR_MDSP = 3;
- SNS_STD_CLIENT_PROCESSOR_CDSP = 4;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_suid.proto b/prebuilt/system/etc/sensors/proto/sns_suid.proto
deleted file mode 100644
index 508fd82..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_suid.proto
+++ /dev/null
@@ -1,49 +0,0 @@
-// @file sns_suid.proto
-//
-// Defines standard message types to request and receive SUIDs.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_type.proto";
-
-enum sns_suid_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_SUID_MSGID_SNS_SUID_REQ = 512;
- SNS_SUID_MSGID_SNS_SUID_EVENT = 768;
-}
-
-// Well-known SUID for use by all clients.
-// All other Sensor UIDs must be discovered dynamically
-message sns_suid_sensor {
- required fixed64 suid_low = 1 [default = 0xabababababababab];
- required fixed64 suid_high = 2 [default = 0xabababababababab];
-}
-
-// Request sent by internal or external client for the list of SUIDs that
-// advertise the specified Data Type
-// Note: Additional requests arriving on the same connection, will not result
-// in a replaced request, but instead the new request will be appended to any
-// active registrations.
-message sns_suid_req {
- required string data_type = 1;
- // Register for updates to the list of SUIDs advertising data_type
- optional bool register_updates = 2;
-
- // Each datatype has one sensor configured to be "default". If following
- // field is set to true, only the SUID of the default sensor will be
- // sent via the suid event
- optional bool default_only = 3 [default = true];
-}
-
-// Event specifying the list of SUIDs associated with the given Data Type
-// Receipt of this event indicates that a change to this list has occurred
-// since the previous event.
-message sns_suid_event {
- // Direct copy of sns_suid_req:data_type
- required string data_type = 1;
- repeated sns_std_suid suid = 2;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_thermopile.proto b/prebuilt/system/etc/sensors/proto/sns_thermopile.proto
deleted file mode 100644
index 2e24181..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_thermopile.proto
+++ /dev/null
@@ -1,62 +0,0 @@
-// @file sns_thermopile.proto
-//
-// Defines the API for Thermopile Sensors.
-// All Thermopile Sensor drivers are required to comply with this API.
-// Any new functionality for Thermopile Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The Thermopile Temperature Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "thermopile".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in degrees Celsius/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in degrees Celsius unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The Thermopile Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-
-// Handling stream events:
-// 1. The Thermopile Sensor publishes data stream events using the
-// sns_std_sensor_event message.
-// 2. Each stream event contains one output data field where data is
-// factory calibrated and ordered as:
-// data[0] = Object temperature in degrees Celsius
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The Thermopile Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The Thermopile Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The Thermopile Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The Thermopile Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API.
-// 3. The Thermopile Sensor could implement other test types.
-
-// Handling test events:
-// 1. The Thermopile Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_threshold.proto b/prebuilt/system/etc/sensors/proto/sns_threshold.proto
deleted file mode 100644
index bb34195..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_threshold.proto
+++ /dev/null
@@ -1,91 +0,0 @@
-// @file sns_threshold.proto
-//
-// Defines standard message types for the Threshold Algorithm
-//
-// Copyright (c) 2018 - 2019 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std.proto";
-import "sns_std_sensor.proto";
-import "sns_resampler.proto";
-
-// Threshold Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "threshold"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_STREAMING
-
-// Sensor output event:
-// Threshold uses sns_std_sensor_event for it's output event.
-// An event is generated by the threshold algorithm only if the threshold is met
-// on any of the axis for the sensor.
-// Thresholding can be done as value based delta between current value and
-// the last generated output. Or thresholding can be done as the delta between
-// current value and the last output, as a percentage of the last output.
-// Thresholding can also be done based on the current value going beyond a particular
-// absolute threshold value.
-// When thresholding criteria is met , an event is generated by the algorithm.
-
-enum sns_threshold_msgid
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_THRESHOLD_MSGID_SNS_THRESHOLD_CONFIG = 512;
-}
-
-//Thresholding types
-enum sns_threshold_type
-{
- option (nanopb_enumopt).long_names = false;
-
- // Provide thresholding as a delta between current value
- // and last reported value, exceeding above the configured threshold.
- SNS_THRESHOLD_TYPE_RELATIVE_VALUE = 0;
-
- // Provide thresholding as a delta between current value
- // and last reported value, compared as a percentage of the last reported value,
- // where the percentage is the configured threshold.
- SNS_THRESHOLD_TYPE_RELATIVE_PERCENT = 1;
-
- // Provides thresholding of the current value against a fixed configured
- // threshold value.
- SNS_THRESHOLD_TYPE_ABSOLUTE = 2;
-
- // Provides thresholding of angle between current and last reported quaternion
- // for quaternion sensors, in radians
- SNS_THRESHOLD_TYPE_ANGLE = 3;
-}
-
-// Configuration Message
-// Used to either request for a new configuration of the threshold Sensor or
-// alter an already existing configuration or query the current configuration.
-message sns_threshold_config
-{
- // UID of the sensor from which data is being requested from.
- required sns_std_suid sensor_uid = 1;
-
- // The threshold value per axis.
- // The number of threshold values need to be less than or equal to the number of
- // sensor data axes.
- // For SNS_THRESHOLD_TYPE_ANGLE, a single threshold_val value representing the
- // angle between current and last reported quaternions
- repeated float threshold_val = 2;
-
- // Tells us how to use the thresholding value provided.
- required sns_threshold_type threshold_type = 3;
-
- // The message id to be used to configure the underlying sensor.
- // This is used together with the below payload field.
- required uint32 payload_cfg_msg_id = 4;
-
- // Dynamic length payload, containing the actual data/configuration request
- // This payload will need to be decoded separately, using the Sensor-specific
- // header file.
- required bytes payload = 5;
-}
-
-// Config is used to inform the client of the configuration that was set,
-// after a configuration is done .
-// The config message is sent back to the client
-// in the threshold config message.
-// All data events are generated as sns_std_sensor_event.
diff --git a/prebuilt/system/etc/sensors/proto/sns_tilt.proto b/prebuilt/system/etc/sensors/proto/sns_tilt.proto
deleted file mode 100644
index 8458776..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_tilt.proto
+++ /dev/null
@@ -1,49 +0,0 @@
-// @file sns_tilt.proto
-//
-// Defines message types for the Tilt Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The Tilt Sensor looks for a change in angle of a gravity vector from an
-// anchor vector.
-//
-// The initial anchor vector is based on an average of one second of
-// accel data after initial activation.
-//
-// The gravity vector is calculated based on an average of two seconds of
-// accel data.
-//
-// The anchor vector is reset to the current gravity vector each time the
-// Tilt event is generated.
-// There is only one anchor vector shared amongst all clients.
-//
-// The Tilt event is generated when the current gravity vector is 35 degrees
-// or more from the anchor vector.
-
-// Tilt Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "tilt"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Tilt Sensor
-enum sns_tilt_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_TILT_MSGID_SNS_TILT_EVENT = 774;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_TILT_MSGID_SNS_TILT_EVENT is used to
-// publish tilt event
-//
-// Tilt does not publish configuration events.
-
diff --git a/prebuilt/system/etc/sensors/proto/sns_tilt_to_wake.proto b/prebuilt/system/etc/sensors/proto/sns_tilt_to_wake.proto
deleted file mode 100644
index ceabc92..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_tilt_to_wake.proto
+++ /dev/null
@@ -1,36 +0,0 @@
-// @file sns_tilt_to_wake.proto
-//
-// Defines message types for the tilt_to_wake Sensor.
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The tilt_to_wake detects substantial phone rotation (gesture) within
-// limited period ending in a specific range of the pitch and roll angles.
-// It uses proximity sensor to block the tilt event reporting in pocket or purse
-
-// tilt_to_wake Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "tilt_to_wake"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for tilt_to_wake Sensor
-enum sns_tilt_to_wake_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_TILT_TO_WAKE_MSGID_SNS_TILT_TO_WAKE_EVENT = 775;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_TILT_TO_WAKE_MSGID_SNS_TILT_TO_WAKE_EVENT is used to
-// publish tilt_to_wake event
-//
-// tilt_to_wake does not publish configuration events.
diff --git a/prebuilt/system/etc/sensors/proto/sns_timer.proto b/prebuilt/system/etc/sensors/proto/sns_timer.proto
deleted file mode 100644
index 82bcc01..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_timer.proto
+++ /dev/null
@@ -1,149 +0,0 @@
-// @file sns_timer.proto
-//
-// Defines standard message types for the Timer Sensor
-//
-// Copyright (c) 2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-syntax = "proto2";
-import "nanopb.proto";
-
-enum sns_timer_sensor_timeout
-{
- option (nanopb_enumopt).long_names = false;
-
- SNS_TIMER_SENSOR_TIMEOUT_MIN_TIMEOUT_NANOSEC = 100000;
-}
-
-enum sns_timer_msgid {
- option (nanopb_enumopt).long_names = false;
-
- // Timer config message.
- //
- //Corresponds to the message sns_timer_sensor_config.
- // This message is used to start, reconfigure or
- // stop the timer sensor
- SNS_TIMER_MSGID_SNS_TIMER_SENSOR_CONFIG = 512;
-
- // Timer event message.
- //
- // Corresponds to the message sns_timer_sensor_event.
- // This event is generated when a timer's timeout
- // occurs.
- SNS_TIMER_MSGID_SNS_TIMER_SENSOR_EVENT = 1025;
-
- // Timer registration message
- //
- // This message is used to acknowledge that a timer was successfully
- // registered. This event contains the sns_timer_reg_event with the
- // options selected by the timer sensor. The event will be re-sent each time
- // the timer sensor automatically adjusts the period of a periodic timer.
- SNS_TIMER_MSGID_SNS_TIMER_SENSOR_REG_EVENT = 1026;
-}
-
-// Priority of timer events
-enum sns_timer_priority {
- option (nanopb_enumopt).long_names = false;
- // Priority LOWEST is used for low priority timers
- SNS_TIMER_PRIORITY_LOWEST = 0;
- // Priority OTHER is used for general timer events, and should be used
- // by default
- SNS_TIMER_PRIORITY_OTHER = 10;
- // Priority POLLING is used for polling physical sensors
- SNS_TIMER_PRIORITY_POLLING = 50;
- // Priority S4S is used for S4S schedules
- SNS_TIMER_PRIORITY_S4S = 100;
-}
-
-// Timer configuration message.
-// The minimum time resolution supported by the timer is
-// min_timeout_nanosec
-
-message sns_timer_sensor_config
-{
-
- // The time of starting the timer in ticks. This is typically current time.
- required uint64 start_time = 1;
-
- // The timeout period starting from start_time, in ticks.
- required uint64 timeout_period = 2;
-
- // If this timer is periodic. If true, the timer will be rearmed to
- // timeout_period when the timer fires. If false, the timer will be disarmed
- // after firing once. The memory associated with this timer will not be
- // released until this connection is terminated.
- required bool is_periodic = 3;
-
- // The start_config allows the timer sensor to modify the start_time. This may
- // allow the timer sensor to synchronize with other nearby timers to save power
- // if the exact value of start_time is flexible.
- // If this message is not present, default values are 0.
- message start_config_message {
- // The start_time may be adjusted to start early by this many ticks.
- required uint32 early_start_delta = 1;
- // The start_time may be adjusted to start late by this many ticks.
- required uint32 late_start_delta = 2;
- }
- optional start_config_message start_config = 4;
-
- // The timeout_config allows the timer sensor to modify the timeout_period.
- // This may allow the timer sensor to synchronize with other timers to save
- // power if the exact perodicity is flexible.
- // If this message is not present, default values are 0.
- message timeout_config_message {
- // The initial timeout_period may be adjusted smaller by this many ticks.
- required uint32 low_timeout_delta = 1;
- // The initial timeout_period may be adjusted larger by this many ticks.
- required uint32 high_timeout_delta = 2;
-
- // jitter_ticks only applies if "is_periodic" is true. After the first
- // TIMER_SENSOR_EVENT, the timeout_period will only be adjusted by this many
- // ticks in each period. The accumulated adjustments will stay within the
- // low/high bounds defined in this message.
- optional uint32 jitter_ticks = 3;
- }
- optional timeout_config_message timeout_config = 5;
-
- // Set this to true to cause the timer sensor to send a TIMER_SENSOR_REG_EVENT
- // and include this timer as part of the timers to be synchronized, but the
- // timer will not actually be started, and no TIMER_SENSOR_EVENTs will
- // be generated.
- // This is useful to know how to synchronize to other timers on the system
- // without actually causing timer events to occur.
- optional bool is_dry_run = 6 [default = false];
-
- // If multiple timers expire at the same time, timer events with higher
- // priority will be sent first.
- // default: other
- optional sns_timer_priority priority = 7 [default = SNS_TIMER_PRIORITY_OTHER];
-}
-
-// Timer Sensor event
-// This event is generated each time the timer fires. The time at which the timer
-// fires can differ from the requested timeout by up to min_timeout_nanosec.
-// The client is responsible for checking the requested_timeout_time and the
-// timeout_time fields and determine if additional delays must be added.
-message sns_timer_sensor_event
-{
- // The timeout period generated from the timer_sensor_config message in ticks.
- required uint64 requested_timeout_time = 1;
-
- // The time at which the timer fired, in ticks.
- required uint64 timeout_time = 2;
-}
-
-// Timer registration message
-//
-// This message is used to acknowledge that a timer was successfully
-// registered. This event contains options selected by the timer sensor based
-// on the config event.
-// The event will be re-sent each time the timer sensor automatically adjusts
-// the period of a periodic timer.
-message sns_timer_sensor_reg_event
-{
- required uint64 start_time = 1;
- required uint64 timeout_period = 2;
- required bool is_periodic = 3;
- required bool is_dry_run = 4;
- required sns_timer_priority priority = 5;
-}
diff --git a/prebuilt/system/etc/sensors/proto/sns_ultra_violet.proto b/prebuilt/system/etc/sensors/proto/sns_ultra_violet.proto
deleted file mode 100644
index 7bb7fd2..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_ultra_violet.proto
+++ /dev/null
@@ -1,72 +0,0 @@
-// @file sns_ultra_violet.proto
-//
-// Defines the API for Ultra Violet (UV) Sensors.
-// All UV Sensor drivers are required to comply with this API.
-// Any new functionality for UV Sensor can be defined in a
-// device specific API file.
-//
-// Copyright (c) 2016-2017 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-import "sns_physical_sensor_test.proto";
-import "sns_cal.proto";
-
-// Attribute requirements:
-// The UV Sensor publishes:
-// 1. SNS_STD_SENSOR_ATTRID_TYPE attribute value as "ultra_violet".
-// 2. SNS_STD_SENSOR_ATTRID_RESOLUTIONS attribute value in degrees mW/cm2/LSB.
-// 3. SNS_STD_SENSOR_ATTRID_RANGES attribute values in degrees mW/cm2 unit.
-// 4. See sns_std_sensor.proto for other attributes.
-
-// Handling stream requests:
-// 1. The UV Sensor handles the sns_std_sensor_config
-// message request for all stream enable/update requests.
-
-// Handling stream events:
-// 1. The UV Sensor publishes UV data in ambient light using the
-// sns_std_sensor_event message.
-// 2. Each stream event contains following factory calibrated data fields:
-// data[0] = Bit mask to determine which outputs are supported:
-// bit[0]: 1 if UV-A is supported else 0
-// bit[1]: 1 if UV-B is supported else 0
-// bit[2]: 1 if Total UV is supported else 0
-// bit[3]: 1 if UV index is supported else 0
-// all other bits are 0
-// data[1] = UV-A radiation in mW/cm2
-// data[2] = UV-B radiation in mW/cm2
-// data[3] = Total UV radiation in mW/cm2
-// data[4] = Unitless UV index number
-// 3. Each stream event publishes an accuracy field:
-// SNS_STD_SENSOR_SAMPLE_STATUS_UNRELIABLE to mark invalid samples when hardware is
-// yet to stabilize after the sensor is configured.
-// SNS_STD_SENSOR_SAMPLE_STATUS_ACCURACY_HIGH to mark samples when they are valid.
-// 4. The UV Sensor publishes a configuration event using the
-// sns_std_sensor_physical_config_event message.
-// It publishes this event each time there is change in hardware config of the sensor
-// and contains current physical sensor config of the sensor.
-// 5. The UV Sensor publishes a factory calibration event using the
-// sns_cal_event message. It uses bias and scale_factor fields in this event.
-// It publishes this event each time there is change in it's factory calibration
-// data or when a client sends a new streaming request.
-
-// Handling self-test requests:
-// 1. The UV Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_COM test
-// type using the physical sensor test API.
-// 2. The UV Sensor implements SNS_PHYSICAL_SENSOR_TEST_TYPE_FACTORY test
-// type to determine factory calibration parameters using the physical
-// sensor test API. The factory test for UV Sensor calibrates
-// the sensor such that it's output is comparable to a standard
-// UV Meter output in any lighting condition.
-// 3. The UV Sensor could implement other test types.
-
-// Handling test events:
-// 1. The UV Sensor uses sns_physical_sensor_test_event message to publish
-// a test completion event.
-// 2. The test_passed field in sns_physical_sensor_test_event is used to output the
-// pass/fail result of self-test execution.
-// 3. The test_data field in sns_physical_sensor_test_event could be used to output any
-// driver-specific error data.
diff --git a/prebuilt/system/etc/sensors/proto/sns_wrist_tilt_gesture.proto b/prebuilt/system/etc/sensors/proto/sns_wrist_tilt_gesture.proto
deleted file mode 100644
index 37482d9..0000000
--- a/prebuilt/system/etc/sensors/proto/sns_wrist_tilt_gesture.proto
+++ /dev/null
@@ -1,49 +0,0 @@
-// @file sns_wrist_tilt_gesture.proto
-//
-// Defines message types for the wrist_tilt_gesture Sensor.
-//
-// Copyright (c) 2018 Qualcomm Technologies, Inc.
-// All Rights Reserved.
-// Confidential and Proprietary - Qualcomm Technologies, Inc.
-
-syntax = "proto2";
-import "nanopb.proto";
-import "sns_std_sensor.proto";
-
-// The Tilt Sensor looks for a change in angle of a gravity vector from an
-// anchor vector.
-//
-// The initial anchor vector is based on an average of one second of
-// accel data after initial activation.
-//
-// The gravity vector is calculated based on an average of two seconds of
-// accel data.
-//
-// The anchor vector is reset to the current gravity vector each time the
-// Tilt event is generated.
-// There is only one anchor vector shared amongst all clients.
-//
-// The Tilt event is generated when the current gravity vector is 35 degrees
-// or more from the anchor vector.
-
-// Tilt Sensor Attribute Requirements:
-// SNS_STD_SENSOR_ATTRID_TYPE: "wrist_tilt_gesture"
-// SNS_STD_SENSOR_ATTRID_STREAM_TYPE: SNS_STD_SENSOR_STREAM_TYPE_ON_CHANGE
-
-// Stream Requests:
-// - SNS_STD_SENSOR_MSGID_SNS_STD_ON_CHANGE_CONFIG is used to enable the sensor
-
-// Message IDs for Wrist Tilt Gesture Sensor
-enum sns_wrist_tilt_gesture_msgid {
- option (nanopb_enumopt).long_names = false;
-
- SNS_WRIST_TILT_GESTURE_MSGID_SNS_TILT_EVENT = 774;
-}
-
-// Stream events:
-//
-// A NULL message with message ID SNS_TILT_MSGID_SNS_TILT_EVENT is used to
-// publish tilt event
-//
-// Tilt does not publish configuration events.
-
diff --git a/proprietary-files-product.txt b/proprietary-files-product.txt
new file mode 100644
index 0000000..df0b24a
--- /dev/null
+++ b/proprietary-files-product.txt
@@ -0,0 +1,131 @@
+# Alarm
+-product/app/PowerOffAlarm/PowerOffAlarm.apk
+-product/framework/vendor.qti.hardware.alarm-V1.0-java.jar
+product/lib64/vendor.qti.hardware.alarm@1.0.so
+product/lib/vendor.qti.hardware.alarm@1.0.so
+
+# Bluetooth
+product/lib64/com.qualcomm.qti.bluetooth_audio@1.0.so
+product/lib64/vendor.qti.hardware.audiohalext@1.0.so
+product/lib64/vendor.qti.hardware.btconfigstore@1.0.so
+product/lib/com.qualcomm.qti.bluetooth_audio@1.0.so
+product/lib/vendor.qti.hardware.audiohalext@1.0.so
+product/lib/vendor.qti.hardware.btconfigstore@1.0.so
+
+# Camera
+-product/priv-app/seccamservice/seccamservice.apk
+-product/framework/vendor.qti.hardware.sensorscalibrate-V1.0-java.jar
+product/lib/libQTEEConnector_system.so
+product/lib/libseccam-ipc.so
+product/lib/libseccamservice.so
+product/lib/libseccam.so
+product/lib/vendor.qti.hardware.camera.device@1.0.so
+product/lib/vendor.qti.hardware.cvp@1.0.so
+product/lib/vendor.qti.hardware.scve.objecttracker@1.0-adapter-helper.so
+product/lib/vendor.qti.hardware.scve.objecttracker@1.0.so
+product/lib/vendor.qti.hardware.scve.panorama@1.0-adapter-helper.so
+product/lib/vendor.qti.hardware.scve.panorama@1.0.so
+product/lib/vendor.qti.hardware.seccam@1.0.so
+product/lib/vendor.qti.hardware.sensorscalibrate@1.0.so
+product/lib64/libQTEEConnector_system.so
+product/lib64/libseccam-ipc.so
+product/lib64/libseccamservice.so
+product/lib64/libseccam.so
+product/lib64/vendor.qti.hardware.camera.device@1.0.so
+product/lib64/vendor.qti.hardware.scve.objecttracker@1.0-adapter-helper.so
+product/lib64/vendor.qti.hardware.scve.objecttracker@1.0.so
+product/lib64/vendor.qti.hardware.scve.panorama@1.0-adapter-helper.so
+product/lib64/vendor.qti.hardware.scve.panorama@1.0.so
+product/lib64/vendor.qti.hardware.seccam@1.0.so
+product/lib64/vendor.qti.hardware.sensorscalibrate@1.0.so
+
+# Display api
+product/lib/libsdm-disp-apis.qti.so
+product/lib/libsd_sdk_display.qti.so
+product/lib/vendor.display.color@1.0.so
+product/lib/vendor.display.color@1.1.so
+product/lib/vendor.display.color@1.2.so
+product/lib/vendor.display.color@1.3.so
+product/lib/vendor.display.config@1.0.so
+product/lib/vendor.display.config@1.1.so
+product/lib/vendor.display.config@1.2.so
+product/lib/vendor.display.config@1.3.so
+product/lib/vendor.display.config@1.4.so
+product/lib/vendor.display.config@1.5.so
+product/lib/vendor.display.config@1.6.so
+product/lib/vendor.display.config@1.7.so
+product/lib/vendor.display.postproc@1.0.so
+product/lib/vendor.qti.hardware.qdutils_disp@1.0.so
+product/lib64/libsdm-disp-apis.qti.so
+product/lib64/libsd_sdk_display.qti.so
+product/lib64/vendor.display.color@1.0.so
+product/lib64/vendor.display.color@1.1.so
+product/lib64/vendor.display.color@1.2.so
+product/lib64/vendor.display.color@1.3.so
+product/lib64/vendor.display.config@1.0.so
+product/lib64/vendor.display.config@1.1.so
+product/lib64/vendor.display.config@1.2.so
+product/lib64/vendor.display.config@1.3.so
+product/lib64/vendor.display.config@1.4.so
+product/lib64/vendor.display.config@1.5.so
+product/lib64/vendor.display.config@1.6.so
+product/lib64/vendor.display.config@1.7.so
+product/lib64/vendor.display.postproc@1.0.so
+product/lib64/vendor.qti.hardware.qdutils_disp@1.0.so
+
+# IMS
+-product/priv-app/ims/ims.apk|993e75757565d87b8eac95644b789463a667598e
+lib/libdiag_system.so
+lib64/libdiag_system.so
+-product/framework/com.qualcomm.qti.imscmservice-V2.0-java.jar
+-product/framework/com.qualcomm.qti.imscmservice-V2.1-java.jar
+-product/framework/com.qualcomm.qti.imscmservice-V2.2-java.jar
+-product/framework/uimservicelibrary.jar
+-product/framework/vendor.qti.ims.callinfo-V1.0-java.jar
+-product/framework/vendor.qti.ims.rcsconfig-V1.0-java.jar
+product/etc/permissions/com.qualcomm.qti.imscmservice-V2.0-java.xml
+product/etc/permissions/com.qualcomm.qti.imscmservice-V2.1-java.xml
+product/etc/permissions/com.qualcomm.qti.imscmservice-V2.2-java.xml
+product/lib/com.qualcomm.qti.imscmservice@1.0.so
+product/lib/com.qualcomm.qti.imscmservice@2.0.so
+product/lib/com.qualcomm.qti.imscmservice@2.1.so
+product/lib/com.qualcomm.qti.imscmservice@2.2.so
+product/lib/libimscamera_jni.so
+product/lib/libimsmedia_jni.so
+product/lib/lib-imsvideocodec.so
+product/lib/lib-imsvtextutils.so
+product/lib/lib-imsvt.so
+product/lib/lib-imsvtutils.so
+product/lib/vendor.qti.hardware.radio.ims@1.0.so
+product/lib/vendor.qti.hardware.radio.ims@1.1.so
+product/lib/vendor.qti.hardware.radio.ims@1.2.so
+product/lib/vendor.qti.hardware.radio.ims@1.3.so
+product/lib/vendor.qti.hardware.radio.ims@1.4.so
+product/lib/vendor.qti.ims.callinfo@1.0.so
+product/lib/vendor.qti.ims.rcsconfig@1.0.so
+product/lib/vendor.qti.imsrtpservice@2.0.so
+product/lib/vendor.qti.imsrtpservice@2.1.so
+product/lib64/com.qualcomm.qti.imscmservice@1.0.so
+product/lib64/com.qualcomm.qti.imscmservice@2.0.so
+product/lib64/com.qualcomm.qti.imscmservice@2.1.so
+product/lib64/com.qualcomm.qti.imscmservice@2.2.so
+product/lib64/libimsmedia_jni.so
+product/lib64/lib-imsvideocodec.so
+product/lib64/lib-imsvtextutils.so
+product/lib64/lib-imsvt.so
+product/lib64/lib-imsvtutils.so
+product/lib64/vendor.qti.hardware.radio.ims@1.0.so
+product/lib64/vendor.qti.hardware.radio.ims@1.1.so
+product/lib64/vendor.qti.hardware.radio.ims@1.2.so
+product/lib64/vendor.qti.hardware.radio.ims@1.3.so
+product/lib64/vendor.qti.hardware.radio.ims@1.4.so
+product/lib64/vendor.qti.ims.callinfo@1.0.so
+product/lib64/vendor.qti.ims.rcsconfig@1.0.so
+product/lib64/vendor.qti.imsrtpservice@2.0.so
+product/lib64/vendor.qti.imsrtpservice@2.1.so
+
+# IOP
+product/lib64/vendor.qti.hardware.iop@2.0.so
+product/lib64/vendor.qti.hardware.perf@2.0.so
+product/lib/vendor.qti.hardware.iop@2.0.so
+product/lib/vendor.qti.hardware.perf@2.0.so
diff --git a/proprietary-files-qc-perf.txt b/proprietary-files-qc-perf.txt
deleted file mode 100644
index e69de29..0000000
--- a/proprietary-files-qc-perf.txt
+++ /dev/null
diff --git a/proprietary-files-qc.txt b/proprietary-files-qc.txt
deleted file mode 100644
index e69de29..0000000
--- a/proprietary-files-qc.txt
+++ /dev/null
diff --git a/proprietary-files.txt b/proprietary-files.txt
index 9a7e64b..73a9666 100644
--- a/proprietary-files.txt
+++ b/proprietary-files.txt
@@ -63,22 +63,6 @@
product/lib64/vendor.qti.hardware.data.cne.internal.constants@1.0.so
product/lib64/vendor.qti.hardware.data.cne.internal.server@1.0.so
-# Display api
-product/lib/libsdm-disp-apis.qti.so
-product/lib/libsd_sdk_display.qti.so
-product/lib64/libsdm-disp-apis.qti.so
-product/lib64/libsd_sdk_display.qti.so
-product/lib/vendor.display.color@1.0.so
-product/lib/vendor.display.color@1.1.so
-product/lib/vendor.display.color@1.2.so
-product/lib/vendor.display.color@1.3.so
-product/lib/vendor.display.postproc@1.0.so
-product/lib64/vendor.display.color@1.0.so
-product/lib64/vendor.display.color@1.1.so
-product/lib64/vendor.display.color@1.2.so
-product/lib64/vendor.display.color@1.3.so
-product/lib64/vendor.display.postproc@1.0.so
-
# DPM
-framework/tcmclient.jar
product/bin/dpmd
@@ -109,6 +93,7 @@
product/lib64/vendor.qti.hardware.fm@1.0.so
# Gallery
+product/etc/preferred-apps/asus.xml
-priv-app/AsusGallery/AsusGallery.apk;PRESIGNED
priv-app/AsusGallery/lib/arm/libmpbase.so
priv-app/AsusGallery/lib/arm/libjni_filter_show.so
@@ -140,6 +125,15 @@
-priv-app/AsusGalleryBurst/AsusGalleryBurst.apk;PRESIGNED
priv-app/AsusGalleryBurst/lib/arm/libgifencoder.so
+# GalleryBurst Video Editor
+etc/videoeditor/Soothing.mfim
+etc/videoeditor/Charming.mfim
+etc/videoeditor/Energetic.mfim
+etc/videoeditor/Lively.mfim
+etc/videoeditor/Graceful.mfim
+etc/videoeditor/Happy.mfim
+etc/videoeditor/Dynamic.mfim
+
# GPS
etc/permissions/com.qti.location.sdk.xml
etc/permissions/com.qualcomm.location.xml
@@ -161,18 +155,6 @@
-product/priv-app/HotwordEnrollmentOKGoogleWCD9340/HotwordEnrollmentOKGoogleWCD9340.apk;PRESIGNED
-product/priv-app/HotwordEnrollmentXGoogleWCD9340/HotwordEnrollmentXGoogleWCD9340.apk;PRESIGNED
-# IMS
-lib64/libdiag_system.so
-product/lib64/libimscamera_jni.so
-product/lib64/libimsmedia_jni.so
-product/lib64/lib-imsvideocodec.so
-product/lib64/lib-imsvtextutils.so
-product/lib64/lib-imsvt.so
-product/lib64/lib-imsvtutils.so
-product/lib64/vendor.qti.imsrtpservice@2.0.so
-product/lib64/vendor.qti.imsrtpservice@2.1.so
--product/priv-app/ims/ims.apk|993e75757565d87b8eac95644b789463a667598e
-
# NFC
#-app/NQNfcNci/NQNfcNci.apk
#-framework/com.nxp.nfc.nq.jar
@@ -187,6 +169,89 @@
#lib64/libnqnfc-nci.so
#lib64/libnqnfc_nci_jni.so
+# Sensors
+etc/sensors/proto/nanopb.proto
+etc/sensors/proto/sns_physical_sensor_test.proto
+etc/sensors/proto/sns_ccd_ttw.proto
+etc/sensors/proto/sns_std_sensor.proto
+etc/sensors/proto/sns_async_com_port.proto
+etc/sensors/proto/sns_tilt.proto
+etc/sensors/proto/sns_cmd.proto
+etc/sensors/proto/sns_interrupt.proto
+etc/sensors/proto/sns_basic_gestures.proto
+etc/sensors/proto/sns_game_rv.proto
+etc/sensors/proto/sns_accel_cal.proto
+etc/sensors/proto/sns_dae.proto
+etc/sensors/proto/sns_gyro_rot_matrix.proto
+etc/sensors/proto/sns_sensor_temperature.proto
+etc/sensors/proto/sns_pedometer_wrist.proto
+etc/sensors/proto/sns_wrist_tilt_gesture.proto
+etc/sensors/proto/sns_humidity.proto
+etc/sensors/proto/sns_heart_beat.proto
+etc/sensors/proto/sns_remote_proc_state.proto
+etc/sensors/proto/sns_oem1.proto
+etc/sensors/proto/sns_ext_svc.proto
+etc/sensors/proto/sns_diag.proto
+etc/sensors/proto/sns_rotv.proto
+etc/sensors/proto/sns_sim.proto
+etc/sensors/proto/sns_aont.proto
+etc/sensors/proto/sns_heart_rate.proto
+etc/sensors/proto/sns_accel.proto
+etc/sensors/proto/sns_device_orient.proto
+etc/sensors/proto/sns_bring_to_ear.proto
+etc/sensors/proto/sns_std.proto
+etc/sensors/proto/sns_registry.proto
+etc/sensors/proto/sns_gravity.proto
+etc/sensors/proto/sns_rgb.proto
+etc/sensors/proto/sns_offbody_detect.proto
+etc/sensors/proto/sns_data_acquisition_engine.proto
+etc/sensors/proto/sns_cmc.proto
+etc/sensors/proto/sns_distance_bound.proto
+etc/sensors/proto/sns_std_type.proto
+etc/sensors/proto/sns_pose_6dof.proto
+etc/sensors/proto/sns_sim_legacy.proto
+etc/sensors/proto/sns_sar.proto
+etc/sensors/proto/sns_threshold.proto
+etc/sensors/proto/sns_std_event_gated_sensor.proto
+etc/sensors/proto/sns_timer.proto
+etc/sensors/proto/sns_cal.proto
+etc/sensors/proto/sns_hall.proto
+etc/sensors/proto/sns_proximity.proto
+etc/sensors/proto/sns_mag_cal.proto
+etc/sensors/proto/sns_multishake.proto
+etc/sensors/proto/sns_diag_sensor.proto
+etc/sensors/proto/descriptor.proto
+etc/sensors/proto/sns_client.proto
+etc/sensors/proto/sns_thermopile.proto
+etc/sensors/proto/sns_psmd.proto
+etc/sensors/proto/sns_ultra_violet.proto
+etc/sensors/proto/sns_mag.proto
+etc/sensors/proto/sns_signal_sensor.proto
+etc/sensors/proto/sns_amd.proto
+etc/sensors/proto/sns_da_test.proto
+etc/sensors/proto/sns_dpc.proto
+etc/sensors/proto/sns_suid.proto
+etc/sensors/proto/sns_resampler.proto
+etc/sensors/proto/qti_gravity.proto
+etc/sensors/proto/sns_tilt_to_wake.proto
+etc/sensors/proto/sns_device_mode.proto
+etc/sensors/proto/sns_sig_motion.proto
+etc/sensors/proto/sns_gyro.proto
+etc/sensors/proto/sns_ambient_light.proto
+etc/sensors/proto/sns_pressure.proto
+etc/sensors/proto/sns_mcmd.proto
+etc/sensors/proto/sns_fw.proto
+etc/sensors/proto/sns_ppg.proto
+etc/sensors/proto/sns_geomag_rv.proto
+etc/sensors/proto/sns_facing.proto
+etc/sensors/proto/sns_gyro_cal.proto
+etc/sensors/proto/sns_pedometer.proto
+etc/sensors/proto/sns_fmv.proto
+etc/sensors/proto/sns_rmd.proto
+etc/sensors/proto/sns_ccd_walk.proto
+etc/sensors/proto/sns_motion_detect.proto
+etc/sensors/proto/sns_ambient_temperature.proto
+
# Telephony
etc/permissions/qti_libpermissions.xml
etc/permissions/qti_permissions.xml
@@ -200,4 +265,4 @@
-product/priv-app/qcrilmsgtunnel/qcrilmsgtunnel.apk
# Wlan
--product/framework/vendor.qti.hardware.data.iwlan-V1.0-java.jar
\ No newline at end of file
+-product/framework/vendor.qti.hardware.data.iwlan-V1.0-java.jar
diff --git a/setup-makefiles.sh b/setup-makefiles.sh
index e62d730..aea3363 100755
--- a/setup-makefiles.sh
+++ b/setup-makefiles.sh
@@ -47,35 +47,9 @@
# The standard blobs
write_makefiles "$MY_DIR"/proprietary-files.txt
-# Qualcomm BSP blobs - we put a conditional around here
-# in case the BSP is actually being built
-printf '\n%s\n' "ifeq (\$(QCPATH),)" >> "$PRODUCTMK"
-printf '\n%s\n' "ifeq (\$(QCPATH),)" >> "$ANDROIDMK"
-
-write_makefiles "$MY_DIR"/proprietary-files-qc.txt
-
-# Qualcomm performance blobs - conditional as well
-# in order to support Cyanogen OS builds
-cat << EOF >> "$PRODUCTMK"
-endif
-
--include vendor/extra/devices.mk
-ifneq (\$(call is-qc-perf-target),true)
-EOF
+write_makefiles "$MY_DIR"/proprietary-files-product.txt
cat << EOF >> "$ANDROIDMK"
-endif
-
-ifneq (\$(TARGET_HAVE_QC_PERF),true)
-EOF
-
-write_makefiles "$MY_DIR"/proprietary-files-qc-perf.txt
-
-echo "endif" >> "$PRODUCTMK"
-
-cat << EOF >> "$ANDROIDMK"
-
-endif
EOF