[DEV] Triumph Kernel Thread (01/19/2013)


  1. BSydz

    BSydz Well-Known Member Developer

    Ok, everybody that is interested in getting a more stable system overall, may want to chip in as much as possible. I am going to spend some time just working on kernels. I know we don't have a ton of people that know kernels but hopefully in time this will have all the details that you need.

    I am just gonna start this off with some reading material, that should light a fire under your backside, if you have been working on this phone like I have.

    I'll hide it in time but just want to show this to you guys. This is all the work that FIH put in to our device after Motorola and VM abandoned our phone. Our kernel history stops at 2011/03/25, our device is FB0(X6 group) and FD1(our phone). It is also cool as it shows which files that were modified to address the issues. This is just what changed after ours was released, I will attach a full edited version that will only have our product related changes from the beginning, but it is gonna take some time. This is a good reference as to what needs to be changed in the system files as well.

    *-----------------------------------------------------------------------------
    * 0.100.0568 2011/05/25 15:40
    *-----------------------------------------------------------------------------
    Team : SW2-6-1
    Issuer: Johnny Lin
    Mark : Div6-D1-JL-AddUSBDbgInfo
    IssueKeys:[FB0.B-4562]
    Summary: DUT can't continue to charge
    Do : [Change]
    - By some situation, usb register info can help us to check the state and status of USB phy. And than try to reset USB to recover the usb state. It need set a value to the debug file node to enable this function. And need bebug file node or the setting of USB Debugging (Setting->application->development->USB Debugging) to triger this.


    [Symptom]
    - None

    [Cause]
    - None

    [Solution]
    - None

    [Notes]
    - File node: sys/kernel/debug/USBDBG/ResetUsb

    [Expose]
    - No.

    Files :
    * ./android/kernel/drivers/usb/gadget/msm72k_udc.c
    * ./android/kernel/drivers/usb/otg/msm72k_otg.c
    * ./android/kernel/drivers/usb/gadget/f_adb.c
    *-----------------------------------------------------------------------------
    * 0.100.0564 2011/05/23 20:00
    *-----------------------------------------------------------------------------
    Team : SW2-6-1
    Issuer: Johnny Lin
    Mark : Div6-D1-JL-QualcommFix23
    IssueKeys:[FB0.B-4562]
    Summary: DUT can't continue to charge
    Do : [Change]
    - Port the fix of qualcomm release (23).
    - Modify the wrong debug log.

    [Symptom]
    - None.

    [Cause]
    - It has been observed that with some non-compliant chargers, h/w issues suspend interrupt resulting in UDC driver requesting to stop charging.

    [Solution]
    - ignore such reuests if a wall-charger is being used.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/usb/gadget/msm72k_udc.c
    * ./android/kernel/drivers/usb/otg/msm72k_otg.c
    *-----------------------------------------------------------------------------
    * 0.100.0564 2011/05/23 10:15
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Chris Deng
    Mark : SW2-6-1-CONN-CD-CONNECT_AFTER_ADDED-00
    IssueKeys:[FD1.B-766]
    Summary: DUT cannot connect to the second hide WIFI AP.
    Do : [Change]
    - Add connect() after saveNetworks().

    [Symptom]
    - 1.Connect a WiFi network.
    2.Add another hide WiFi network,and check the DUT's status.

    DUT reconnect to the first WiFi network again, and the hide WiFi network status is "Remember".

    [Cause]
    - Because of android not support this feature.

    [Solution]
    - Do connect() after saveNetworks() in WiFiSetting.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/packages/apps/Settings/src/com/android/settings/wifi/WifiSettings.java

    Reviewer:
    Erwin Yang

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]

    *-----------------------------------------------------------------------------
    * 0.100.0559 2011/05/19 11:37
    *-----------------------------------------------------------------------------
    Team : SW2-5-1
    Issuer: Matt Peng
    Mark :
    IssueKeys:[SQ01.B-726]
    Summary: add AID_LOG to the group list of logcat/klogd process.
    Do : [Change]
    - Before logcat/klogd is fork, add AID_LOG group to allow read system logs.

    [Symptom]
    - logcat process is disappear.

    [Cause]
    - None

    [Solution]
    - None

    [Notes]
    - logcat/klogd will run with system-process.

    [Expose]
    - None.

    Files :
    * ./android/external/klogd/loggerlauncher.c

    Reviewer:
    Ken Chen
    *-----------------------------------------------------------------------------
    * 0.100.0557 2011/05/18 21:40
    *-----------------------------------------------------------------------------
    Team : SW2-6-1
    Issuer: Johnny Lin
    Mark : Div6-D1-JL-FixAdbStatusUsbDebugging
    IssueKeys:[FB0.B-4573]
    Summary: Usb Tethering can't enable when disable Usb Debugging
    Do : [Change]
    - Modify the function to handled adb function enable/disabl separetely.

    [Symptom]
    - None

    [Cause]
    - Because the config of USB tethering in the driver is adb + tethering. But it may cause that no match when disable USB debugging (disable adb).

    [Solution]
    - Modify the function to handled adb function enable/disabl separetely.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/drivers/usb/gadget/android.c
    *-----------------------------------------------------------------------------
    * 0.100.0556 2011/05/18 17:05
    *-----------------------------------------------------------------------------
    Team : SW2-5-1
    Issuer: Matt Peng
    Mark :
    IssueKeys:[SQ01.B-726]
    Summary: Rollback r10759 due to logcat process are disappear.
    Do : [Change]
    - None

    [Symptom]
    - None

    [Cause]
    - None

    [Solution]
    - None

    [Notes]
    - logcat/klogd will run with root-process.

    [Expose]
    - None.

    Files :
    * ./android/external/klogd/loggerlauncher.c

    Reviewer:
    Ken Chen
    *-----------------------------------------------------------------------------
    * 0.100.0554 2011/05/17 11:40
    *-----------------------------------------------------------------------------
    Team : Div2-D5-BSP
    Issuer: Abbott Chung
    Mark : Div2D5-AC-BSP-Add_baattery_ID_command-00
    IssueKeys:[SQ01.FC-91]
    Summary: Implement Battery id set and get in FTM command.
    Do : [Change]
    - Add battery id command set and get in FTM.

    [Symptom]
    - Huawei request in SF8.

    [Cause]
    - They want to trace product out when device have battery issue.

    [Solution]
    - Save the battery id in NV item by oem smem command.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    Kernel:
    * ./android/kernel/drivers/char/ftmgpio.c
    * ./android/kernel/drivers/char/ftmgpio.h
    * ./android/kernel/arch/arm/mach-msm/proc_comm.c
    * ./android/kernel/arch/arm/mach-msm/proc_comm.h
    FTM:
    * ./FTM/project/QCOM7x30/hal/gpio.c
    * ./FTM/project/QCOM7x30/hal/gpio.h
    * ./FTM/ftm/command.c
    * ./FTM/ftm/command.h
    * ./FTM/ftm/dispatcher.c

    Reviewer:
    Libery Liu
    *-----------------------------------------------------------------------------
    * 0.100.0552 2011/05/17 14:53
    *-----------------------------------------------------------------------------
    Team : SW2-5-1
    Issuer: Matt Peng
    Mark : SW2-5-1-MP-LogProcess_User-00
    IssueKeys:[SQ01.B-726]
    Summary: (CTS) Switch DbgCfgTool processes(logcat/klogd) to non-root process.
    Do : [Change]
    - Change the logcat/klogd fork by DbgCfgTool as system user.

    [Symptom]
    - CTS fail due to logcat/klogd are non-root processes.

    [Cause]
    - None

    [Solution]
    - Before the process is fork, use setuid/setgid to switch user to "system"

    [Notes]
    - klogctl is a root-privileges syscall, we must hack kernel under a safty control.

    [Expose]
    - None.

    Files :
    * ./android/external/klogd/loggerlauncher.c
    * ./android/kernel/security/commoncap.c

    Reviewer:
    Ken Chen
    *-----------------------------------------------------------------------------
    * 0.100.0550 2011/05/16 19:35
    *-----------------------------------------------------------------------------
    Team : Kernel
    Issuer: Stella Chen
    Mark : Kernel-SC-ALS_range_setting-00
    IssueKeys:
    Summary: Modify ALS range setting
    Do : [Change]
    - Modify ALS range setting

    [Symptom]
    - None.

    [Cause]
    - Touch panel is changed, this affects the sensitivity of light sensor.

    [Solution]
    - None.

    [Notes]
    - None.

    [Expose]
    - No.

    Files :
    * ./android/frameworks/base/services/java/com/android/server/PowerManagerService.java
    * ./android/frameworks/base/core/res/res/values/Config.xml
    * ./android/vendor/fih/sf6/fih-overlays/default/frameworks/base/core/res/res/values/Config.xml


    Reviewer: Colin Hong


    Review:
    [History Details*]OK
    [Code Review*]OK
    [Verifications*]OK
    [Function*]OK
    [Quick Test] OK
    *-----------------------------------------------------------------------------
    * 0.100.0549 2011/05/16 16:22
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Eric Chen
    Mark : None
    IssueKeys:[FB0.B-4208]
    Summary: Add some log in wpa_supplicant
    Do : [Change]
    - 1. Add some log in wpa_supplicant

    [Symptom]
    - None

    [Cause]
    - None

    [Solution]
    - None

    [Notes]
    - None

    [Expose]
    - None

    Files :
    * ./android/external/wpa_supplicant_6/wpa_supplicant/ctrl_iface.c
    * ./android/external/wpa_supplicant_6/wpa_supplicant/src/drivers/driver_wext.c

    Reviewer:
    Chris Deng

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0547 2011/05/16 10:50
    *-----------------------------------------------------------------------------
    Team : Div2-MM
    Issuer: Sendow Chen
    Mark : DIV2-MM-SC-JNI_INTERFACE-00
    PCR : None
    IssueKeys:[FB0.B-4538]
    Do :
    [Change]
    - Build FM tools only in SF8 series.

    [Symptom]
    - None

    [Cause]
    - None

    [Solution]
    - Add project flag in mk file to build fm_server tools in SF8 only.

    [Notes]
    - No.

    [Expose]
    . No

    Files :
    * ./android/system/core/toolbox/Android.mk

    *-----------------------------------------------------------------------------
    * 0.100.0545 2011/05/13 17:00
    *-----------------------------------------------------------------------------
    Team : SW2-6-1
    Issuer: Johnny Lin
    Mark : Div2-SW6-JL-FixAGPSPort
    IssueKeys:[FB3.B-1801]
    Summary: Fix the port number of AGPS when setting to null. (For GCF.)
    Do :
    [Change]
    - Modify port number to 0 when it is minus value.

    [Symptom]
    - None

    [Cause]
    - When the port of AGPS is set to null, AP will set random number. But sometimes it may set minus value. Modify it to 0.

    [Solution]
    - Modify port number to 0 when it is minus value.

    [Notes]
    - No.

    [Expose]
    . No

    Files :
    /android/frameworks/base/core/jni/android_location_GpsLocationProvider.cpp

    *-----------------------------------------------------------------------------
    * 0.100.0543 2011/05/12 22:25
    *-----------------------------------------------------------------------------
    Team : SW252-BSP
    Issuer: Rexer Lin
    Mark : 1.SW252-rexer-upld-01
    PCR : None
    IssueKeys:[SQ01.B-710]
    Do :
    [Change]
    1. not repeat use proc command get wifi_mac and product_id

    [Symptom]

    [Cause]

    [Solution]
    1. storage wifi_mac and product_id and not repeat use
    proc command get

    [Notes]

    [Expose]
    . No

    Files :
    1.
    *.\android\kernel\arch\arm\mach-msm\fxx_info.c
    *-----------------------------------------------------------------------------
    * 0.100.0540 2011/05/11 18:19
    *-----------------------------------------------------------------------------
    Team : SW2-5-1
    Issuer: Matt Peng
    Mark :
    IssueKeys:[SQ01.B-726]
    Summary: (CTS) turn off log for CTS test project/model
    Do : [Change]
    - For CTS test models, we specify additional DefaultDbgConfig setting which logs are turn off.

    [Symptom]
    - CTS fail due to log is turn on.

    [Cause]
    - None

    [Solution]
    - Add specify setting for CTS test models, currently we have:
    DefaultDbgConfig_FB0_8004.xml
    DefaultDbgConfig_FB0_8006.xml
    DefaultDbgConfig_FB0_8007.xml
    This specific settings are the same with release setting.(logs turn off)

    [Notes]
    - From now on, if the specific setting match current FIH_PROJ/FIH_CUST_MODEL_CODE, we apply it as DefaultDbgConfig.xml.
    Otherwise, the DefaultDbgConfig.xml will be debug setting.

    [Expose]
    - None.

    Files :
    * ./android/system/core/rootdir/Android.mk
    + ./android/system/core/rootdir/etc/DefaultDbgConfig_FB0_8004.xml
    + ./android/system/core/rootdir/etc/DefaultDbgConfig_FB0_8006.xml
    + ./android/system/core/rootdir/etc/DefaultDbgConfig_FB0_8007.xml

    Reviewer:
    Ken Chen
    *-----------------------------------------------------------------------------
    * 0.100.0529 2011/05/04 20:30
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Chris Deng
    Mark :
    IssueKeys:[FB0.B-4441]
    Summary: Open BTWLANCOEX debug msg.
    Do : [Change]
    - Open BTWLANCOEX debug msg

    [Symptom]
    - None.

    [Cause]
    - To monitor hotspot and BT action.

    [Solution]
    - Enable BTWLANCOEX debug msg to keep investigating.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * . /android/vendor/qcom/opensource/bt-wlan-coex/Android.mk

    Reviewer:
    Erwin Yang

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]

    *-----------------------------------------------------------------------------
    * 0.100.0524 2011/05/04 15:38
    *-----------------------------------------------------------------------------
    Team : DIV252-BSP
    Issuer: Abbott Chung
    Mark :
    IssueKeys:[SQ01.FC-91]
    Summary: Add CPU information in file node.
    Do : [Change]
    - Store CPU information in file node

    [Symptom]
    - None

    [Cause]
    - None


    [Solution]
    - Read share memory data then store data to /proc/cpu_number

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    BSP:
    * ./android/kernel/arch/mach-msm/fxx_info.c
    * ./android/kernel/arch/mach-msm/smd_private.h
    * ./android/kernel/arch/mach-msm/smd.c
    * ./android/bootable/bootloader/lk/platform/msm_shared/smem.c

    Reviewer:
    Libery Liu

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0513 2011/05/02 10:41
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Eric Chen
    Mark : None
    IssueKeys:[FB0.B-4207]
    Summary: Fix bug in WAPI certification
    Do : [Change]
    - 1. Fix bug in WAPI certification

    [Symptom]
    - 1. Sometimes it is hard to connect WAPI AP in certification way.

    [Cause]
    - 1. String of ca, and client_cert is keystore://USRCERT_as, and keystore://USRCERT_ASUE
    in the first time connection. They become string /data/certificate/as, and /data/certificate/ASUE
    after the setting is writen into /etc/wifi/wpa_supplicant.conf.
    Originally the program logic uses '_' to find location of string "as", and "ASUE".
    This program logic is error when the second connection.

    [Solution]
    - 1. Improve code

    [Notes]
    - None

    [Expose]
    - None

    Files :
    * ./android/external/wpa_supplicant_6_WAPI/wpa_supplicant/os_adaptor.c
    * ./android/external/wpa_supplicant_6_WAPI/wpa_supplicant_wapi

    Reviewer:
    Chris Deng

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0512 2011/04/29 21:00
    *-----------------------------------------------------------------------------
    Team : SW252-BSP
    Issuer: Rexer Lin
    Mark : SW252-rexer-dual_SD-00
    PCR : None
    IssueKeys:[SF5.B-2828]
    Do :
    [Change]
    to determine if support dual SD card
    [Symptom]

    [Cause]

    [Solution]
    dtermine the flag which be passed by emmcboot

    [Notes]
    this is for boot.img part
    [Expose]
    . No

    Files :
    *.\android\kernel\arch\arm\mach-msm\board-msm7x30.c
    *.\android\kernel\arch\arm\mach-msm\fxx_info.c
    *-----------------------------------------------------------------------------
    * 0.100.0509 2011/04/27 16:30
    *-----------------------------------------------------------------------------
    Team : SW2-5-Multimedia
    Issuer: Seven Lin
    Mark : MM-SL-HS WAKE UP IN SUSPEND-01
    IssueKeys:[P***.B-793]
    Summary: Fix- DUT wake up when plug/unplug in suspend mode
    Do : [Change]
    - Fix- DUT wake up when plug/unplug in suspend mode

    [Symptom]
    1.Suspend DUT, and wait for a while, plug in headset
    2.Suspend DUT wait for a while, unplug headset
    3.DUT wakes up.

    [Cause]
    1.Headset plug in/out is defined as wake up pin at present.

    [Solution]
    1.Remove input_report_key function when headset plug in/out

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/switch/switch_gpio.c


    Reviewer:


    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0507 2011/04/26 19:03
    *-----------------------------------------------------------------------------
    Team : SW2-5-1
    Issuer: Matt Peng
    Mark : SW2-5-1-MP-Modem_Debug_NV-00
    IssueKeys:[SQ01.B-715]
    Summary: Write Modem Debug NV according to NV_ERR_FATAL_OPTIONS_I (#905) in DbgCfgTool
    Do : [Change]
    - 1. Write Modem Debug NVs (#905, #4399, #6470) through smem proc oem command instead of RPC calls.
    - 2. Remove the write path of DbgCfgSetDetectHWReset.

    [Symptom]
    - Several NVs need to be write to make sure we can got a valid RAM dump.

    [Cause]
    - None.

    [Solution]
    - Create a smem proc command to write modem debug NVs in the same time.

    [Notes]
    - * NV Item Name AutoDownload Action Reset Action No Action
    - * 905 NV_ERR_FATAL_OPTIONS_I 0 1 2
    - * 4399 NV_DETECT_HW_RESET_I 1 0 0
    - * 6470 NV_CACHE_WT_I 1 0 0

    [Expose]
    - None.

    Files :
    * ./android/kernel/arch/arm/mach-msm/proc_comm.c
    * ./android/kernel/arch/arm/mach-msm/proc_comm.h
    * ./android/kernel/arch/arm/mach-msm/dbgcfgtool.c
    * ./android/kernel/arch/arm/mach-msm/include/mach/dbgcfgtool.h
    * ./android/system/core/include/cutils/dbgcfgtool.h
    * ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/ModemRamdumpConfig.java
    * ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/Utils.java
    * ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/ProfileManager.java
    * ./android/development/FIH/DbgCfgTool/GUI/res/values/strings.xml
    * ./android/development/FIH/DbgCfgTool/JNI/DbgCfgToolAPI.c

    Reviewer:
    Ken Chen

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0504 2011/04/25 21:13
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Money Chien
    Mark : Div2-SW6-MM-MC-Hm0357Orientation-00
    IssueKeys:[SQ01.B-714]
    Summary: Fix hm0357 preview reversed issue for SF8 series.
    Do : [Change]
    - 1.Enable H_Flip and V_Flip in hm0357_reg_init().
    - 2.Modify SENSOR_MIRROR_MODE() for sensor_Orientation = MSM_CAMERA_SENSOR_ORIENTATION_270

    [Symptom]
    - Hm0357 front camera preview abnormal when device is SF8 series.

    [Cause]
    - SF8 series HW design is reversed with FB series.

    [Solution]
    - 1.Enable H_Flip and V_Flip in hm0357_reg_init().
    - 2.Modify SENSOR_MIRROR_MODE() for sensor_Orientation = MSM_CAMERA_SENSOR_ORIENTATION_270

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/media/video/msm/hm0357.c
    * ./android/kernel/arch/arm/mach-msm/board-msm7x30.c

    Reviewer:
    Sendow Chen

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0503 2011/04/25 19:37
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Eric Chen
    Mark : None
    IssueKeys:[FB0.B-4207]
    Summary: Change cert_chmod.sh for Gingerbread
    Do : [Change]
    - 1. Change cert_chmod.sh for Gingerbread

    [Symptom]
    - 1. CTS in Gingerbread fails. => change permission of /data/misc/certificate/
    from 777 to 775 to make CTS success
    - 2. Behavior of changing permission makes SFXG.B-92 occur
    - 3. For solving symptom 1, and 2, we change position of certificate from
    /data/misc/certificate/ to /data/certificate/

    [Cause]
    - 1. Permission of /data/misc/certificate/ is 777. It has write permission in other
    group.
    - 2. There is no write permission for CertInstaller.apk to write file into /data/misc/certificate/

    [Solution]
    - 1. Change cert_chmod.sh for Gingerbread
    - 2. In Gingerbread, we change position of certificate from /data/misc/certificate/ to
    /data/certificate/

    [Notes]
    - None

    [Expose]
    - None

    Files :
    * ./android/device/qcom/msm7630_surf/cert_chmod.sh


    Reviewer:
    Josh Chang

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0500 2011/04/21 12:21
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Chris Lu
    Mark : Div2-SW6-MM-CL-FrontCameraInitFail-00
    IssueKeys:[FB0.B-4430]
    Summary: Fix front Camera ANR when suspend/resume.
    Do : [Change]
    -Fix front Camera ANR when suspend/resume.

    [Symptom]
    -1.Front Camera ANR when suspend/resume.
    2.Cann't access front camera anymore.

    [Cause]
    -1.qup_i2c fail when quickly suspend/resume.
    2.mutex is locked even if init fail.

    [Solution]
    -1.Delay and retry 3 times if fail.
    2.Unlock mutex if still init fail.

    [Notes]
    -None.

    [Expose]
    -None.

    Files :
    * ./android/kernel/drivers/media/video/msm/hm0356.c
    * ./android/kernel/drivers/media/video/msm/hm0357.c

    Reviewer:
    Money Chien

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0496 2011/04/20 12:17
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Chris Lu
    Mark : Div2-SW6-MM-CL-mt9p111noImage-02
    IssueKeys:[FB0.B-4402]
    Summary: Fix Camera ANR when access it.
    Do : [Change]
    -Fix Camera ANR when access it.

    [Symptom]
    -Camera frame timeout.

    [Cause]
    -Native_start_video takes too much time.
    FIH camera will open front camera and main camera first before actually using camera.
    Main camera is not follow correct power on and power off sequence.

    [Solution]
    -If main camera is asked to release before it init done, we power off sensor directly.

    [Notes]
    -None.

    [Expose]
    -None.

    Files :
    * ./android/kernel/drivers/media/video/msm/mt9p111.c

    Reviewer:
    Money Chien

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0493 2011/04/18 17:40
    *-----------------------------------------------------------------------------
    Team : SW2-6-1
    Issuer: Johnny Lin
    Mark : None.
    IssueKeys:[FD1.B-857]
    Summary: Remove USB Host config from Kernel config
    Do : [Change]
    - Remove USB Host config from Kernel config.

    [Symptom]
    - None

    [Cause]
    - Because all device don't have this feature, remove this cnfig, and it may cause some usb issue in some situation.

    [Solution]
    - Remove USB Host config from Kernel config.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/aarch/arm/configs/FB400_defconfig

    Reviewer:
    Ken Chen

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0489 2011/04/15 15:00
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Chris Deng
    Mark :
    IssueKeys:[FB0.B-4284]
    Summary: DUT would not scan Wi-Fi networks after changing SSID
    Do : [Change]
    - Roll-back csrApiScan.c

    [Symptom]
    - [Step]
    1. Power on DUT and Home screen ready
    2. Turn on Wi-Fi and enter Wi-Fi settings
    3. Do not connect to AP and check the Wi-Fi networks list
    4. Change AP's SSID
    5. Press Menu key then tap Scan
    6. Wait for 1 minute then check the Wi-Fi networks list again

    [Actual Result]
    DUT would not refresh the Wi-Fi networks list and still show old SSID

    [Cause]
    - This sdie effect for welcom solution. Qualcomm suggest us to roll-back this file.

    [Solution]
    - Roll-back csrApiScan.c, and verify pass.

    [Notes]
    - Specific WiFi AP : Netgear WG602

    [Expose]
    - None.

    Files :
    * ./android/vendor/qcom/proprietary/wlan/libra/CORE/SME/src/csr/csrApiScan.c

    Reviewer:
    Erwin Yang

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]

    *-----------------------------------------------------------------------------
    * 0.100.0488 2011/04/14 20:58
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Money Chien
    Mark : Div2-SW6-MM-MC-mirrorFront-00
    IssueKeys:[SQ01.B-701]
    Summary: Update new camera registers.
    Do : [Change]
    - 1.Disable tcm9001 mirror setting in init reg table.
    - 2.Add SENSOR_MIRROR_MODE case in tcm9001md_set_sensor_mode() function.

    [Symptom]
    - SF5 front camera preview abnormal in Gingerbread.

    [Cause]
    - None.

    [Solution]
    - 1.Disable tcm9001 mirror setting in init reg table.
    - 2.Add SENSOR_MIRROR_MODE case in tcm9001md_set_sensor_mode() function.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/media/video/msm/tcm9001md.c
    * ./android/kernel/drivers/media/video/msm/tcm9001md_reg.c
    * ./android/kernel/arch/arm/mach-msm/board-msm7x30.c
    * ./FTM/project/QCOM7x30/hal/targets/tgtcommon/sensor/tcm9001md/tcm9001md.c

    Reviewer:
    Sendow Chen

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0474 2011/04/11 15:00
    *-----------------------------------------------------------------------------
    Team: SW2-5-1
    Issuer: Bryan Hsieh
    Mark: none
    IssueKeys:[FB0.FC-21] Add tcpdump in product
    Summary:[FB0.FC-21] Add tcpdump in product
    Do : [Change]
    - Add tcpdump feature in DbgCfgTool

    [Symptom]
    - None.

    [Cause]
    - None.

    [Solution]
    - Add tcpdump feature in DbgCfgTool

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/development/FIH/DbgCfgTool/JNI/Android.mk
    + ./android/development/FIH/DbgCfgTool/NI/tcpdumpJNI.c
    * ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/Utils.java
    + ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/TcpdumpTool.java
    * ./android/development/FIH/DbgCfgTool/GUI/src/com/fihspec/DbgCfgTool/TestOptions.java
    * ./android/development/FIH/DbgCfgTool/GUI/res/values/strings.xml
    * ./android/development/FIH/DbgCfgTool/GUI/res/layout/test_options.xml
    -------------------------------------
    * 0.100.0466 2011/04/01 13:50
    *-----------------------------------------------------------------------------
    Team : SW2-6-1-CONN
    Issuer: Chris Deng
    Mark :
    Issuekeys:[FB0.B-4337]
    Summary: DUT doens't support to connect with WAPI AP. (Model is 7021 & 7121)
    Do : [Change]
    - Add new model is support WAPI function.

    [Symptom]
    - DUT cannot connect with WAPI AP.

    [Cause]
    - These models are not support WAPI function.

    [Solution]
    - Add 7021 & 7121 into msm7630_surf.mk, and make sure it workable.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/device/qcom/msm7630_surf/msm7630_surf.mk

    Reviewer:
    Erwin Yang

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0458 2011/03/30 15:12
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Chris Lu
    Mark : Div2-SW6-MM-CL-mt9p111noImage-01
    IssueKeys:[FB3.B-1228]
    Summary: Fix camera sensor no image issue
    Do : [Change]
    - Fix camera sensor no image issue.

    [Symptom]
    - Can't get picture or camera frame timeout.

    [Cause]
    - Sensor is not stable, sensor no image issue.

    [Solution]
    - Reset camera sensor when there is no image issue.
    Power off sensor when release if sensor was reseted or init was not finished.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/media/video/msm/mt9p111.c
    * ./android/vendor/qcom/android-open/libcamera2/QualcommCameraHardware.cpp

    Reviewer:
    Money Chien

    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0450 2011/03/29 15:40
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Chris Lu
    Mark : Div2-SW6-CL-Camera-LensC-02
    IssueKeys:[FB3.B-1091]
    Summary:
    Do : [Change]
    - Remove transfrom formula for sensor OTP error in FB3.

    [Symptom]
    - Camera will display pink.

    [Cause]
    - Main camera mt9p111 will use transfrom formula for wrong OTP camera module.

    [Solution]
    - FB3 will not have wrong module, we don't need this transfrom formula.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/kernel/drivers/media/video/msm/mt9p111.c


    Reviewer:


    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]
    *-----------------------------------------------------------------------------
    * 0.100.0449 2011/03/29 15:14
    *-----------------------------------------------------------------------------
    Team : Div2-SW6-2
    Issuer: Chris Lu
    Mark : Div2-SW6-CL-Camera-RecordOverlapped-00
    IssueKeys:[FD1.B-574]
    Summary:
    Do : [Change]
    - Fix bug The video image is overlapped when set Video quality to Low(30m) or MMS

    [Symptom]
    - In portrait mode, the video is overlapped when set Video quality to Low after taking pictures.

    [Cause]
    - When taking picture in protrait, ap will setrotation to 90, but this is not clear when switching to camcorder.
    HAL will set 90 to VPE, which is not support yet.

    [Solution]
    - Hard code rotation to 0 when setting vpe parameters.

    [Notes]
    - None.

    [Expose]
    - None.

    Files :
    * ./android/vendor/qcom/android-open/libcamera2/QualcommCameraHardware.cpp


    Reviewer:


    Review:
    [History Details*]
    [Code Review*]
    [Verifications*]
    [Function*]
    [Quick Test]

    Advertisement
    :
  2. BSydz

    BSydz Well-Known Member Developer

    Notes
    ZipLipZ likes this.
  3. BSydz

    BSydz Well-Known Member Developer

    Details of changes made
    ZipLipZ likes this.
  4. jhonka232

    jhonka232 Well-Known Member

    Great thread man! This is a great find! Any chance you know what "DUT" means?
    BSydz likes this.
  5. rukin5197

    rukin5197 Well-Known Member

    I wish I could see diffs of the commits. But the camera ones are definitely ones to pay attention to, might be able to compare those files to the stock kernel and see if we can implement the fixes
  6. Omniscience3

    Omniscience3 New Member

    DUT usually means 'Device Under Test'. Not sure if that's the case here though.
    jhonka232 likes this.
  7. BSydz

    BSydz Well-Known Member Developer

    My goal was to create a kernel based off of the M410 kernel, that will work across the board. But that has changed, to finding the latest kernel branch from FIH. I spent all day yesterday trying to figure out where TJ got his code from for the 2.6.35.7 kernel, I found some clues but never found exactly where he got it, he said he got it from Huawei, so I downloaded every available kernel they had. I did find an updated branch which is the Huawei Vision U8850. It has a month of updates beyond the M410 kernel. What led me to this are two files, include/linux/fih_hw_info.c and arch/arm/mach-msm/fxx_info.c. It is messed up cause when you search for those files our development is what comes up.

    The differences that I am looking for are:
    fxx_info.c: added Product_MP1, which the vision kernel has

    fih_hw_info.c: added Product_MP1, which the vision kernel has

    I am thinking that the one I got is slightly past what TJ used, cause there is a difference in the msm_camera.h that is about the autofocus and them using the wrong patch. Plus it has a few extra lines in the fxx_info.c.

    Our issue is that, through the hands of so many devs the GPU drivers have changed and it is hard to tell which ones they are and where they came from. That was the issue with getting the m410 kernel to work on CM7.

    Our reboot issues are tied to the force module being implemented to make wifi work. Cause our wifi module is looking for 2..6.32.9-perf as the kernel. That's why while mantera was updating the kernel he had to keep the version number the same. But then found the force module thing and never looked back. I want to just stay with the stock kernel and implement as many fixes as possible. We know that our kernel can work with ICS just fine as the xperia plays official ICS beta uses the same kernel as ours, as in 2.6.32.9.

    Any way, hopefully we can get a solid kernel base to work with, our biggest issue is gonna be with the init scripts and getting the permissions right, I stripped out a ton of stuff from both the init.triumph.rc and the uevent.triumph.rc and everything still worked fine.


    Any body that get a random reboot, use a root explorer to zip the last_kmsg, it is located here proc/last_kmsg. It is usually too long to read on the phone and gets truncated but the bottom is usually where the details are. I know that the 2.6.35.7 kernel is crashing the modem/amss, and that is why it reboots.

    Ok, I've rambled enough for now.
  8. rukin5197

    rukin5197 Well-Known Member

    Couldn't we just hack up the wifi module to look for 2.6.35.x? Sounds easy but I predict it will be hard. I don't know much about C language, so I can't be of much help, but I would like to get more into it.
  9. dsmryder

    dsmryder Well-Known Member Contributor

    Do you know what modual it was?

    I went looking at mantera's commits. He releases a ROM with the problem fixed, but he has so many patches with so many updated files it's hard to tell what was done.

    And in case, the 0.6.12 was built Aril 8th
    The last release that had the problem wasn't listed, I don't know when it was built.
  10. rukin5197

    rukin5197 Well-Known Member

    EDIT: Derp
  11. adamto

    adamto Well-Known Member Developer

    What does finding the latest FIH branch buy us?

    Other than the touchscreen issue, is there anything holding us back from m410 kernel? Maybe this will be my next project.
  12. dsmryder

    dsmryder Well-Known Member Contributor

    I don't know if it went into the kernel or not, but way back when Whyzor rewrote the touchscreen drivers and made it way easier to use. I'll see if I can find the commit (maybe not today) and link the posts when they came in. I remember because I commented on the "release delay" he put in there. I think it is the driver that's used in CM7.

    I think this is the first commit
    This is the history for it
    I hope it helps.
  13. BSydz

    BSydz Well-Known Member Developer

    Well I had just wrote about a page of info when my battery backup went on the fritz and shut my PC down. But I'll try again. this time it will be in short hand.

    I have found 3 kernel sources from the same branch, as in they all have the same change history but were released at different times. We have the kenel_2_038(stock), M410(Cherry/Mi410/Welcomm), and the U8850/C8850 kernel. These are all identical up to the point they were released, the info in the first post is all pulled from the history file from the M410 kernel, which is edited to show all specific stuff to our device. FD1 is us, but we use the FB0 as our base. And you will see that there are fixes for us even though we never got an update. Now the only real difference in the U8850 kernel is camera stuff. While the U8850 is not in our family it is based on the same board, the only differences I see is the touchscreen, BT and Wifi.

    The touchscreen is a huge difference. Especially when it comes to doing things on a pixel basis, like trying to place an object right were you want it. The touchscreen drivers also fix the lines in the screen when the phone is woke up, that some devices experience. My dev phone has the issue while my good phone doesn't. I recently restored a backup of the Sharp ROM and figured I'd see if there was a difference, I had been playing AB Space on PA and it was a pain to get the angle just right, cause it would jump all around and even move on the release. While on the Sharp ROM the graphics were way faster and the touch was leaps and bounds better. I have incorperated the drivers in to both of my Froyo ports and also in to the CM7 kernel, all with very good feedback. The only problem is that i just did the CM7 kernel as a test so I didn't think about saving or pushing my changes, So I don't know which of the 10 CM7 kernels is the one that is being used in CM7. Right now CM7 is using the prebuilt kernel that I had built. The CM7 kernel you were using didn't have the changes I had made. Check this out most of the info is on that page.
    http://androidforums.com/triumph-al...ev-cm7-build-2012-12-28-a-24.html#post5281872

    I ran the modified M410 kernel with Sharp 2.2.2 for over a week and all was good. The camera was a lil wonky, mostly to do with focus, but that was to be expected since I was using a different kernel. The problem is that, we have had so many hands in the pot that some things have just been left behind, and that is what worries me. That is why I started working on PA, just to start fresh and only pull in what changes were needed. The basic things to get the M410 kernel to work with the CyanogenMod ROMs is the GPU drivers, and the touchscreen changed in ICS so to get it to work the pressure lines need to be added.

    OK, I'm running out of steam here, almost 2 hours on a post, I had so much info before and now it is all scrambled in my head.
    Thanks, I'll see if there is anything I can use.
Loading...

Share This Page