sonyxperiadev/device-sony-common

Copyright (C) Sony Mobile Communications 2014

This is the Android common configuration for Sony platforms.

Build instructions https://developer.sony.com/develop/open-devices/guides/aosp-build-instructions/

device-sony-common's Issues

TARGET_KERNEL_VERSION is not set anywhere causing compile error

./device/sony/common/Android.mk:102: /Android.mk: No such file or directory
Which points to:

 include $(display-hal)/Android.mk

https://github.com/sonyxperiadev/device-sony-common/blob/n-mr1/Android.mk#L102

Where should TARGET_KERNEL_VERSION := 3.10 be set? Shinano?

sonyxperiadev/device-sony-shinano#365
???

AOSP support for Xperia L3 I4312

build failed because of toybox

Phone: X Compact
AOSP: 6.0.1

got error:

No rule to make target `out/target/product/kugo/utilities/toybox', needed by `out/target/product/kugo/root/init.real'.

I tried to build toybox alone

$ mmm external/toybox/

failed again

Fingerprint is not common, 8974 do not have it

01-01 00:20:09.857  3941  3941 D SubSettings: Launching fragment com.android.settings.SecuritySettings
01-01 00:20:09.888  3941  3941 V SecuritySettings: No fingerprint hardware detected!!
01-01 00:20:09.897  3941  3941 D AndroidRuntime: Shutting down VM
01-01 00:20:09.899  3941  3941 E AndroidRuntime: FATAL EXCEPTION: main
01-01 00:20:09.899  3941  3941 E AndroidRuntime: Process: com.android.settings, PID: 3941
01-01 00:20:09.899  3941  3941 E AndroidRuntime: Theme: themes:{}
01-01 00:20:09.899  3941  3941 E AndroidRuntime: java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.is_hardware_backed(java.lang.String)' on a null object reference
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3131)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3162)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2509)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.-wrap11(ActivityThread.java)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1347)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.os.Handler.dispatchMessage(Handler.java:102)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.os.Looper.loop(Looper.java:148)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.main(ActivityThread.java:5458)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at java.lang.reflect.Method.invoke(Native Method)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
01-01 00:20:09.899  3941  3941 E AndroidRuntime: Caused by: java.lang.NullPointerException: Attempt to invoke interface method 'int android.security.IKeystoreService.is_hardware_backed(java.lang.String)' on a null object reference
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.security.KeyStore.isHardwareBacked(KeyStore.java:381)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.security.KeyStore.isHardwareBacked(KeyStore.java:376)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at com.android.settings.SecuritySettings.createPreferenceHierarchy(SecuritySettings.java:307)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at com.android.settings.SecuritySettings.onResume(SecuritySettings.java:630)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.Fragment.performResume(Fragment.java:2263)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1008)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1148)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1130)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:1963)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.FragmentController.dispatchResume(FragmentController.java:174)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.Activity.performResume(Activity.java:6348)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3120)
01-01 00:20:09.899  3941  3941 E AndroidRuntime:    ... 10 more
01-01 00:20:09.900  1196  2269 W ActivityManager:   Force finishing activity com.android.settings/.SubSettings
01-01 00:20:09.903  1196  2269 W ActivityManager:   Force finishing activity com.android.settings/.Settings

Impossible to rebuild ODM image correctly

I try to regenerate ODM image.

So firstly, I extract filesystem from official Sony ODM image.
unzip -X -b SW_binaries_for_Xperia_AOSP-N_MR1_4.4_v03-yoshino.zip
simg2img SW_binaries_for_Xperia_AOSP-N_MR1_4.4_v03-yoshino.img SW_binaries_for_Xperia_AOSP-N_MR1_4.4_v03-yoshino.raw.img
mkdir -p /tmp/odm
sudo mount -t ext4 -o loop SW_binaries_for_Xperia_AOSP-N_MR1_4.4_v03-yoshino.raw.img /tmp/odm
mkdir -p $(ANDROID_PRODUCT_OUT)/odm
cp -rf /tmp/odm/* $(ANDROID_PRODUCT_OUT)/odm/.

At this point, the file access rights are good for files on "bin" directory (0755).

But, when I execute "make custom_images", the new ODM image looses file access rights for files on "bin" directory (0644 instead of 0755).

Please tell me how should I fix it.

Proprietary for Sony Xperia XA F3116

Hello Sony developers,

I had known that you did NOT support for F3116 device. However, could you please provide a prebuilt binaries for graphics of SONY XA (F3116). I would like to create my own project to upgrade my devices to Android P

Thank for reading!

Regards.,
Kha Tran

In my linux kernel ,I don't find device file

About android go version config

Hi ,
I want to compile android oreo go version ,but I dont,t find bsp config in android source code in device/,
where I can find some infomation about android Oreo go version

sony

DO NOT CLOSE! Template for device checkboxes

Add (parts of) this to your PRs if you want people to check it on their devices.

### loire
- [ ] suzu
- [ ] kugo

### kitakmi
- [ ] satsuki
- [ ] satsuki_dsds
- [ ] sumire
- [ ] sumire_dsds
- [ ] suzuran
- [ ] ivy
- [ ] ivy_dsds
- [ ] karin
- [ ] karin_windy

### kanuti
- [ ] tulip

### shinano
- [ ] leo
- [ ] aries
- [ ] sirius
- [ ] scorpion
- [ ] scorpion_windy
- [ ] castor
- [ ] castor_windy

### rhine
- [ ] honami
- [ ] amami
- [ ] togari

Device decryption blocked by power hal (/data still busy)

Hello,

since the treble update of the hal components the device decryption is broken. Unmounting of /data is impossible because the power hal is blocking

/data/misc/powerhal/rqbsvr

I'm not yet completely familiar with the new treble system so I only created a workaround and did not open a PR. But it looks like it is necessary to restart the powerhal after decrypting /data.

My device is an Xperia XZ (tone_kagura)

Something like the diff below works for me but it is only a hack:

index fded359..c7a3fd2 100644
--- a/rootdir/init.common.rc
+++ b/rootdir/init.common.rc
@@ -51,6 +51,12 @@ on init
     write /sys/block/zram0/comp_algorithm lz4
     write /proc/sys/vm/page-cluster 0
 
+on property:vold.decrypt=trigger_reset_main
+    stop power-hal-1-0
+
+on property:vold.decrypt=trigger_post_fs_data
+    start power-hal-1-0
+
 on post-fs-data
     # Create directory used by bluetooth subsystem
     mkdir /data/misc/bluetooth 0770 bluetooth bluetooth```

not sure if it is conflict with lineage's own recovery

Excuse me.
When I'm building lineage 15.1 for Xperia X Compact with Sony AOSP Team's codes, I met a troule.
As I know, lineage 15.1 is using TWRP as its own recovery. But AOSP for Sony is using another recovery.
When I am building lineage 15.1, these two different recoveries may be conflict and I don't know how to switch off one of them.
Sorry for disturbing.

Build error on z3c, aries regarding device/sony/common/healthd/healthd_board_sony.cpp

I am not able to compile anymore, n-mr1
Get the following errors:

target thumb C++: libhealthd.aries <= device/sony/common/healthd/healthd_board_sony.cpp
device/sony/common/healthd/healthd_board_sony.cpp:125:9: error: no matching function for call to 'gr_font_size'
        gr_font_size(&char_width, &char_height);
        ^~~~~~~~~~~~
bootable/recovery/minui/minui.h:61:6: note: candidate function not viable: requires 3 arguments, but 2 were provided
void gr_font_size(const GRFont* font, int *x, int *y);
     ^
device/sony/common/healthd/healthd_board_sony.cpp:127:18: error: no matching function for call to 'gr_measure'
    str_len_px = gr_measure(cap_str);
                 ^~~~~~~~~~
bootable/recovery/minui/minui.h:60:5: note: candidate function not viable: requires 2 arguments, but 1 was provided
int gr_measure(const GRFont* font, const char *s);
    ^
device/sony/common/healthd/healthd_board_sony.cpp:131:5: error: no matching function for call to 'gr_text'
    gr_text(x, y, cap_str, 0);
    ^~~~~~~
bootable/recovery/minui/minui.h:59:6: note: candidate function not viable: requires 5 arguments, but 4 were provided
void gr_text(const GRFont* font, int x, int y, const char *s, bool bold);
     ^
3 errors generated.

Xperia 10 II (XQ-AU52) simlock going to be an issue?

I plan to unlock and reflash a XQ-AU52, flash first with emma and the latest android, later move on to sailfish x. The device is offered on ebay saying it has a "Netlock". Is such a lock a pure software thing i can get rid of, or i will get rid of with the bootloader unlock? Or could it be something that will prevent me using that device?

.

.

Android O

ping @kholk
device/sony/common/power/power.c:433:45: error: property_get() called with too small of a buffer
property_get(PROP_DEBUGLVL, propval, "0");

Sony Open Device Support for Mediatek SOC

I am pretty tired of people blaming MEDIATEK all the time!!
The problems we have is with Sony NOT MediaTek.
There is plenty of MediaTek Sources which are open but Sony add their own stuff which we find hard to overcome. Sony removed MediaTek's SPFlashtool support in favour of Sony's S1 Protocol which has no way to recover the device once soft bricked.
This makes things very difficult since we cannot replace the preloader and or LK.
Sony should release open preloader, lk, logo and secro so we can flash those without bricking the device.
Earlier Sony MTK devices used to have "TEST" images included in the firmware packages which were flashed on bootloader unlocked devices but these images used to brick the phones just see the "flashtool" threads regarding the C4, M5 and variants of.
From the XA on these "TEST" images were removed and the bricking of MTK's ended.
So ask your OEM's like Arima to provide the standard MediaTek or fully open Sony ROM's for the Sony L1 code name SM31 Pine for example.
Nothing to do with MEDIATEK it's 100% OEM's preventing us doing anything on these cheaper devices hence why we get no OS upgrades on the L devices the L1 released on N and is still on N today Same for the L2 and probably the L3 and L4.

As said before I am happy to donate a Sony L1 and provide the mt6737 source code to any leading Sony Xperia Dev who thinks he/she is capable.

can't flash the provided odm image

log (as root):
fastboot flash oem SW_binaries_for_Xperia_AOSP_O_MR0_4.4_v02_tone.img
target reported max download size of 268435456 bytes
sending 'oem' (212596 KB)...
OKAY [ 9.656s]
writing 'oem'...
FAILED (remote: Command not allowed)
finished. total time: 9.670s

Device: Xperia XZ
shasum from zip checked