sonyxperiadev / device-sony-aries Goto Github PK

View Code? Open in Web Editor NEW

45.0 13.0 40.0 39.46 MB

Makefile 36.06% C 61.40% Shell 2.55%

device-sony-aries's Introduction

Copyright (C) Sony Mobile Communications 2014

This is the Android device configuration for Xperia Z3 Compact (Shinano platform).

Build instructions http://developer.sonymobile.com/knowledge-base/open-source/open-devices/aosp-build-instructions/

device-sony-aries's People

Contributors

Stargazers

Watchers

device-sony-aries's Issues

Battery service errors in AOSP 7

Periodically the logcat show this:

10-26 13:35:33.793  3158  3213 E BatteryStatsService: no controller energy info supplied
10-26 13:35:33.793  3158  3213 E BatteryStatsService: no controller energy info supplied
10-26 13:35:33.795  3158  3193 E BatteryStatsService: power: Missing API
10-26 13:35:33.821  3158  3213 E BatteryStatsService: modem info is invalid: ModemActivityInfo{ mTimestamp=0 mSleepTimeMs=0 mIdleTimeMs=0 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=0 mEnergyUsed=0}

Missing ro.qti.sensors values

On AOSP 6.0/6.01/7 the sensor appears to be present:

aries:/ # dumpsys deviceidle
...
  mMotionSensor={Sensor name="Significant Motion Detector", vendor="QTI", version=2, type=17, maxRange=1.0, resolution=1.0, power=0.12998962, minDelay=-1}
...

However apps cannot read values from it. For instance: https://play.google.com/store/apps/details?id=de.j4velin.pedometer works perfectly with stock ROMs, but cannot use the sensor on AOSP.

brcm-uim error messages

When running AOSP 6.0.1 with the current binaries every couple of seconds the log is populated by these entries:

10-12 17:11:57.034 18363 18363 I brcm-uim: brcm-uim: Begin main
10-12 17:11:57.035 18363 18363 I brcm-uim: brcm-uim: Begin vnd_load_conf
10-12 17:11:57.035 18363 18363 I brcm-uim: brcm-uim:Attempt to load conf from /etc/bluetooth/bt_vendor.conf
10-12 17:11:57.035 18363 18363 I brcm-uim: brcm-uim:UartPort = /dev/ttyHS0
10-12 17:11:57.036 18363 18363 I brcm-uim: brcm-uim:UartBaudRate = 4000000
10-12 17:11:57.036 18363 18363 I brcm-uim: brcm-uim:FwPatchFileName = BCM43xx.hcd
10-12 17:11:57.036 18363 18363 I brcm-uim: brcm-uim:FwPatchSettlementDelay = 100
10-12 17:11:57.036 18363 18363 I brcm-uim: brcm-uim: End vnd_load_conf
10-12 17:11:57.037 18363 18363 I brcm-uim: brcm-uim: Begin vnd_load_conf
10-12 17:11:57.037 18363 18363 I brcm-uim: brcm-uim:Attempt to load conf from /etc/bluetooth/bt_stack.conf
10-12 17:11:57.037 18363 18363 I brcm-uim: brcm-uim:BtSnoopLogOutput = false
10-12 17:11:57.038 18363 18363 I brcm-uim: brcm-uim:BtSnoopFileName = /sdcard/btsnoop_hci.log
10-12 17:11:57.040 18363 18363 I brcm-uim: brcm-uim: End vnd_load_conf
10-12 17:11:57.040 18363 18363 I brcm-uim: brcm-uim:lpmenable 0
10-12 17:11:57.040 18363 18363 I brcm-uim: brcm-uim:Opening install before start of Polling
10-12 17:11:57.040 18363 18363 E brcm-uim: brcm-uim: ERR unable to open /sys/bus/platform/drivers/bcm_ldisc/bcmbt_ldisc.93/install (No such file or directory)
10-12 17:11:57.040 18363 18363 E brcm-uim: brcm-uim: ERR restarting uim

Android Boot camera.msm8974.so Error

Hi,

I have few issues with the AOSP 6.0 for Z3C.

First I had to comment these lines to get it to compile.:

enum mdp_rev { MDSS_MDP_HW_REV_100 = 0x10000000, MDSS_MDP_HW_REV_101 = 0x10010000, //8x26 MDSS_MDP_HW_REV_102 = 0x10020000, };

(file: hardware/qcom/display/msm8974/libqdutils/mdp_version.h)

Secondly after having a successful build

Android is starting but it is stuck in the boot process.
There is a error in the camera.msm8974.so (replacing this file by the same file but from the Sony beta marshmallow rom will get the phone to boot).

/system/lib/hw/camera.msm8974.so (qcamera::QCamera3HardwareInterface::initStaticMetadata(unsigned int)+1377)

Do you also have any idea why ?

Thanks

.

NFC not working properly

When running AOSP 6.0.1 every attempt to use NFC and android beam (between Z3C and galaxy nexus) fail. Even "standard" NFC does not work. For instance this sequence of messages is repeated many times when bringing my yubikey neo next to the back of the device:

10-12 16:53:41.680  5075  5403 D NfcAdaptation: NfcAdaptation::HalDeviceContextDataCallback: len=4
10-12 16:53:41.681  5075  5312 I BrcmNfcNfa: NFC received ntf gid:0
10-12 16:53:41.681  5075  5312 I BrcmNfcNfa: nci_proc_core_ntf opcode:0x7
10-12 16:53:41.682  5075  5312 I BrcmNfcNfa: nfa_dm_nfc_response_cback () NFC_GEN_ERROR_REVT(0x500d)
10-12 16:53:41.682  5075  5312 I BrcmNfcNfa: nfa_dm_disc_data_cback ()
10-12 16:53:41.682  5075  5312 I BrcmNfcNfa: nfa_dm_disc_sm_execute (): state: DISCOVERY (1), event: INTF_ERROR_NTF(10) disc_flags: 0x1
10-12 16:53:41.683  5075  5312 I BrcmNfcNfa: nfa_dm_disc_sm_execute (): new state: DISCOVERY (1), disc_flags: 0x1

No modem

The Sony vendor binaries don't contain the modem data required for the drivers to load and initialise.

Manually copying the contents of /etc/firmware cause the modem to load but repeatedly reset.

sonyxperiadev / device-sony-aries Goto Github PK

device-sony-aries's Introduction

Copyright (C) Sony Mobile Communications 2014

device-sony-aries's People

Contributors

Stargazers

Watchers

Forkers

device-sony-aries's Issues

Recommend Projects

Recommend Topics

Recommend Org