[Xperia Z5 Compact Android Development] LolaPalocz:
Get the device into recovery at what point ?

If it's after having 'fastboot flash boot boot.img' and 'flash recovery twrp.img' , you should issue 'fastboot reboot', then plug usb cable off, and get the white Sony screen (and when the led blinks purple, you should hit Vol-Up and get into TWRP).

I didnt get it at first (got a black screen, but my led blinked red and phone kept rebooting - thought it was bricked). That was when flashing when I was on Sony stock Lollipop .200.

I then flashed (with flashtool, full wipe) Sony stock MM .185, hoping that would be enought to unbrick it, and it worked. I then re-did what I did before to fastboot flash boot and recovery (to install CM13), and then I got the Sony white screen, and could enter recovery, and go on with CM13 installation.

---------- Post added at 03:26 PM ---------- Previous post was at 02:45 PM ----------

I've been testing various ROMs hoping I would find one that would get me less than 1%/hour standby battery drain (my tests and results in another thread started by Zacharias), with no success.

As a last test, I thought I would give this CM13 a go, and I'm glad I did ! I get 0.3%/h standby battery drain with it !

I don't understand how it could be so power efficient, compared to stock ROM. I get the same wakelock patterns with stock and with CM13, so there's no obvious reason. The processes list is cleaner with cm13, without all the sony apps, but these sony apps do not really use much cpu/power according to batterystats.

Anyway, I find this CM13 overall very usable (3 days on it, and happy). Very good work ! I plan to stick to it !

A few points :

I got 3 "died while sleeping" over 3 days (can't power on the phone, have to hit Power+VolUp). No hint in logs. The first happened after a night after the install, with no app/account installed, and data/wifi/bt disabled, with the 'efficient' power profile. I just did a 'adb shell dumpsys batterystats', unpluged, screenoff'ed, and a few minutes later tried to screenon'ed it, and it did not respond. Tried to reproduce this, with no luck. I'm sorry I can't provide more information.

3-4 seconds after i play a sound, there's a small audio glitch, probably when audio circuitry is cut off or suspended.

Already mentionned in some other Z5 CM13 thread, we don't get our original mac address. We get a randomized one starting with 00:90:4c:xx:xx:xx, the xx:xx:xx being randomized at boot. I didnt manage to set it back to my stock mac address via script (i need that to keep my wifi mac filtering).

With stock ROM (stock kernel or Androplus's one), we keep our original mac adress. I don't know if it's the ROM or the kernel/ramdisk job.

I tried to look at androplus and yours repositories to see if stuff should be happening in the init* scripts, but didnt find anything.

I found out that for older xperia devices, /system/sbin/macaddrsetup is used to get the mac addr out of the TA partition and write it in something like /sys/devices/fb000000.qcom,wcnss-wlan/wcnss_mac_addr, but there's no such thing in androplus sources. This macaddrsetup is only used to write somewhere the Bluetooth mac address.

I dont get how and when the macaddress should be set, if it's directly by the wifi driver, or some other helper.

But I saw in the driver code that it somehow tries to get the real mac adress (which in our case seems to be 00:00:00:00:00:00) and if the 4th and 5th parts are both 00, it does this random generation of a mac address starting with 00:90:4c .

In our dmesg, we see :

[ 10.859355] wifi_platform_get_mac_addr
[ 10.862970] somc_wifi_get_mac_addr: Failed to get information from file /sys/devices/platform/bcmdhd_wlan/macaddr (-2)
[ 10.873676] [somc_wifi_get_mac_addr] Exiting. MAC 00:90:4C:C8:FA:C0

And we indeed do not have a /sys/devices/platform/bcmdhd_wlan/ directory.

I haven't tried reinstalling a stock ROM to see what happens, but I'll look next time I want to test one.

Thanks again to all of you for this great work.