Android over usb-if test considerations and changes

The USB if itself is a voluntary logo (logo) certification.

Products that use or have USB markings are subject to this test. The intent is to ensure that all USB devices are of the required quality. There are two ways to test a product: A Compatibility Test meeting sponsored by USB-IF or a private test lab.

If the product is tested for compatibility. It will be included in the USB Integrator list, get a tid number, and have the right to use the USB flag. If you have certification requirements, please contact the appropriate testing institutions.
Change:
1, alps\mediatek\custom\[project_name]\kernel\battery\battery\cust_charging.h
#define Config_usb_ IF  0    //disable usb-if charging
#define CONFIG_USB_IF  1    //enable Usb-if Chargi ng


2, Alps\frameworks\base\services\java\com\android\server\mountservice.java
    Private void Validatepermission (String perm) {
       //if (Mcontext.checkcallingorselfpermission (Perm ) = packagemanager.permission_granted) {
           //throw new SecurityException (stri Ng.format ("Requires%s permission", perm));
       //}
   }
 
Other:
1, over current measurement test configuration, in order to meet USB-IF requirements
USB configured < 500mA
USB un-configure < 100mA
USB suspend < 2.5mA
There is less current in un-configure and suspend states, which is inconsistent with the usual charging experience for mobile phone users. Therefore, it is necessary to make the version number alone.

2, suspend current is small, please note that the phone other peripherals do not power consumption (such as LED, etc.).

3, MS's help site recommended the use of Belkin 7 self-powered USB 2.0 hub, such as the hub impact test, can be directly connected to the mobile phone pcport.

Android over usb-if test considerations and changes