[ROM][Official] AICP - 12.1 - N 7.1 amami

[SpiritCroc]

AICP
Android Ice Cold Project

AICP is known by everyone as the "Ice Cold Project" that started on a Desire HD years ago and since then evolved into a mature ROM with the BEST community you can find!!!

Until Lollipop, the Rom has always been based on AOKP. Unfortunately, since AOKP stopped development (but made a comeback later), we changed our base to CM when it comes to hardware, drivers and some features.
With the rebrand of CM to LineageOS (LAOS) we are now actually LAOS based with some tweaks from AOSP.

If there are any bugs, either we will sort them out or LAOS team, if it concerns their code base. This rom isn't LAOS supported, so no need to report errors or bugs to them!!

#include <std_disclaimer.h>

/*
 * Your warranty is now void.
 *
 * We are not responsible for bricked devices, dead SD cards,
 * thermonuclear war or you getting fired because the alarm app failed. Please
 * do some research if you have any concerns about features included in this ROM
 * before flashing it! YOU are choosing to make these modifications, and if
 * you point the finger at us for messing up your device, we will laugh at you. Hard & a lot.
 *
 */

Feature list (rough Overview)

In the beginning we would like to thank:

LineageOS & CM (R.I.P.) team
maxwen
DU team
SlimRoms team
Resurrection Remix team
OmniRom team
SuperLamic, Sony-Lineage-3.4 team, Hazou, Sonyxperiadev
Community
...

@LorD ClockaN
@zipsnet
@eyosen
@semdoc
@Drgravy
@Hashbang173
@SpiritCroc
@wartomato
@eboye
plus the rest of the crazy bunch that we call "team"
...

We are paying for servers that build nightlies/weeklies and everything that comes with it, so EVERY DONATION will really be appreciated and be used to cover those expenses.
Thank you!!

Latest Stable Release Version 12.1

Download link: http://dwnld.aicp-rom.com/?device=amami
No more official Nougat support since focus shifted to Oreo! You can still get my unofficial Nougat builds here:
https://basketbuild.com/devs/SpiritCroc/amami/AICP-n7.1

Full Changelog link: http://dwnld.aicp-rom.com/?device=amami

Google Apps:
Beans gapps
Or
Open GApps (ARM or ARM64 7.1 pico or nano, depending on your phone's architecture)

If you experience a black screen in some apps (e.g. in Youtube or in camera app), please go to Developer options and enable "Disable HW overlays". Alternatively, you can also add a quick setting for this setting after having enabled developer settings. This setting is not persistent, so you will have to set it after each boot!

Reboot to recovery not working

You tell...

The ROM should contain everything you need to enjoy Android Nougat. You don't need to install any Add-Ons, simply download the latest ROM, GApps, flash it and go!
If you want the device to run the ROM "rooted", you can flash a root solution of your choice after the ROM Zipfile.

It is STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup as this can cause stability issues that are very hard to debug.
If you believe you know what you're doing - then fine, go ahead, but please don't complain if you experience any strange behavior.


How to flash:
(Again: Don't do it if you don't know it!)

Make sure you have real recovery!
Download the ROM and GApps and transfer them to your device
Boot to recovery (TWRP recommended)
Wipe system, Cache, data and ART/Dalvik cache
Flash ROM Zipfile
Flash/Install GApps (optional, needed for e.g. Google Playstore to work)
Flash/Install the root solution of choice (optional)
Reboot to system

The ROM has GApps persistance in between dirty flashes, so you only have to flash them once!
The root solution should be flashed together with every OTA update (= ROM Update)!


Supported root solutions:

Magisk v13.x

SuperSU - stable and beta available (Site by CCMT that took over the the marketing from chainfire)
SuperSU - direct download link for the latest SuperSU directly from the dev (chainfire)

Lineage SU-addon (check your needed version: 14.1 arm or arm64) -> the removal zip is available here too.


PREREQUISITE FOR OTA:
To be able to flash using the buildin OTA app that needs TWRP recovery installed to work.
You can still use LAOS recovery and OTA app, but you will need to download the zip file and flash it manually from within your recovery. Zip gets saved in the "AICP_ota" folder on your internal storage.
Please be sure that you are on the latest TWRP recovery.

If you want to contribute to the AICP or wanna see what is being worked on/merged, feel free to visit our Gerrit review system. (Link is at the bottom!!!)

IceColdJelly AICP G+ community

Kernel source: https://github.com/AICP/kernel_sony_msm8974/tree/n7.1

ROM & Additional links:
Gerrit Code Review
Github

You want to see a normal night at the "DEV office", click here!!
​

XDA:DevDB Information
Android Ice Cold Project (AICP) 12.1 Amami, ROM for the Sony Xperia Z1 Compact

Contributors
SpiritCroc
Source Code: https://github.com/AICP

ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.x
ROM Firmware Required: Unlocked bootloader, real recovery
Based On: AOKP, CyanogenMod, LineageOS, Omni-ROM, DirtyUnicorns

Version Information
Status: No Longer Updated

Created 2016-07-29
Last Updated 2018-03-02

 

[NeoAqr]

another new rom How is it going with the camera?

 

[CmDaRkShAdOw]

another new rom How is it going with the camera?

I heard that it's similar to du

 

[FotoMichi]

Someone have some Screenshots from this ROM ?

 

[CmDaRkShAdOw]

Someone have some Screenshots from this ROM ?

It looks like normal marshmallow, but wait, I'll install it and give you some

 

[CmDaRkShAdOw]

Here are screenshots!
@SpiritCroc why SIM card don't working? o

 

[SpiritCroc]

@SpiritCroc why SIM card don't working? o

It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?

 

[CmDaRkShAdOw]

It's working for me, although the SIM is not recognized immediately, but a few seconds after boot.
Have you tried a reboot? Clean flash? SIM was working for you on DU, am I right? Have you modified the ROM (Xposed, ...)?

I was waiting a few minutes. Tried reboot, clean flash(wipe system, data,cache, art) on DU was fine, not modified

 

[NeoAqr]

Here are screenshots!
@SpiritCroc why SIM card don't working? o

whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now

 

[CmDaRkShAdOw]

whoop. new SnapDragon camera UI. I wonder if the camera is more stable than DU's . if it doesn't freeze frequently I will go get it now

Yes. It's more stable than du,and photos are better.

 

[[GER]Roxxor]

SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?

Overall looks like a good MM ROM! Thank you!

EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.

 

[levone1]

AICP

Sudden battery drain a couple of times on 7/24 build, but love it overall, (i usually assume stuff like that has simething to do with Xposed, etc. anyway). Using newest build now. What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...

SIM is working for me. AudioFX is crashing when starting to play music. Music playing works, but the crash is annoying and I guess equalizer doesn't work.
Also my bluetooth MAC address has a lot of zeros. Is that normal?

Overall looks like a good MM ROM! Thank you!

EDIT: oh. Very important! Flashing this ROM will overwrite your recovery with CM recovery. I hope that the ROM creator can remove it.

We all should use real recovery by now - can't be overwritten.

 

[[GER]Roxxor]

We all should use real recovery by now - can't be overwritten.

Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.

And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".


Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.

EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.

EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.

 

[SpiritCroc]

What would really wrap this up nicely is M5 kernel. The idea has been tossed around a little. @Myself5 has said he's willing to build if someone will maintain, (he doesn't have Z1c anymore). Maybe you'd be a candidate...

Well, I don't have any experiences with modifying kernel (I've always used the kernel that comes with the ROM in the past).
I can build the kernel together with the ROM, anything else I'd have to learn first...

Of course real recovery can be overwritten, why shouldn't it? It just depends if the flashing procedure writes a new recovery to the recovery partition or not. This is the first time that a ROM flash overwrote my recovery.

And I am using it. I did the Emma bootloader upgrade once and didn't have any compatibility problems with ROMs requiring real recovery. And I used TWRP 3.0.2 and flash it by "fastboot flash recovery".


Didn't this flashing procedure overwrite the recovery for anybody else? I flashed the 29.07 build.

EDIT: Ok. I do not get what is happening here... I flashed TWRP via fastboot and it is still launching CM recovery. I did not experience this strange behavior with CM12.1, DU MM and FXP MM AOSP. With all those ROMs TWRP started without issues.

EDIT2: I found the issue. I think this ROM installs a "unreal recovery" in system. If I push the VolDown Button from the moment I push Power, then TWRP starts. If I only push VolDown when the violet light appears, then CM recovery starts. I find this quite confusing, and I guess this is aimed at people without real recovery. Would be nice if @SpiritCroc could clarify if this is intentional.
I figured that CM recovery is in system, because if I install RR kernel (boot.img) and TWRP (recovery.img) still CM recovery is started if pressing on violet light. It is the only partition I did not overwrite.

Real recovery isn't touched by AICP, it still can be accessed the usual way (first press volume button before pressing power & hold until sony logo appears). It's the same way as in DU. In DU, you cannot reboot to recovery or boot to recovery when the sony logo appears after a normal power on. AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.

First press & hold volume button, power on -> device boots recovery partition
Power on while not pressing volume buttons -> device boots into ROM
Power on while not pressing volume buttons, then press volume when notification LED lights up -> tell the ROM you want to access recovery, which has no access to real recovery, but uses inbuilt recovery instead

 

[[GER]Roxxor]

AICP has an inbuilt recovery (CM recovery in this case) that can be accessed via reboot to recovery or when the notification LED is showing during boot up, which can be used instead of real recovery, but doesn't replace it. That's the intended behaviour. If I find the time I might look into replacing the built-in CM recovery with TWRP.

Thank you very much for clarifying!

About the AudioFX issue(somehow I cant attach files):

11:22:04.332   819  2920 I MediaFocusControl:  AudioFocus  requestAudioFocus() from [email protected][email protected] req=1flags=0x0
07-30 11:22:04.335   336  6146 D NuPlayerDriver: reset(0xb3a38120)
07-30 11:22:04.335   336  6146 D NuPlayerDriver: notifyListener_l(0xb3a38120), (8, 0, 0)
07-30 11:22:04.335   336  6198 W AMessage: failed to post message as target looper for handler 0 is gone.
07-30 11:22:04.335   336  6198 D NuPlayerDriver: notifyResetComplete(0xb3a38120)
07-30 11:22:04.337  5999  6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.337  5999  6011 E MediaPlayer-JNI: JNIMediaPlayerFactory: bIsQCMediaPlayerPresent 0
07-30 11:22:04.338  6181  6181 I HeadsetService: Starting service.
07-30 11:22:04.347   336  3033 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.347  6181  6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.347  6181  6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.348  6181  6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.348  6181  6181 E HeadsetService: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348  6181  6181 E HeadsetService: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at org.cyanogenmod.audiofx.HeadsetService.saveDefaults(HeadsetService.java:521)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at org.cyanogenmod.audiofx.HeadsetService.onCreate(HeadsetService.java:389)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.app.ActivityThread.handleCreateService(ActivityThread.java:2923)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.app.ActivityThread.-wrap4(ActivityThread.java)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1446)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.348  6181  6181 E HeadsetService: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.350   336   336 W AudioFlinger: createEffect() effect not found
07-30 11:22:04.350  6181  6181 E AudioEffect: set(): AudioFlinger could not create effect, status: -22
07-30 11:22:04.350  6181  6181 E AudioEffects-JNI: AudioEffect initCheck failed -3
07-30 11:22:04.350  6181  6181 E AudioEffect-JAVA: Error code -3 when initializing AudioEffect.
07-30 11:22:04.351  6181  6181 D AndroidRuntime: Shutting down VM
07-30 11:22:04.352  6181  6181 E AndroidRuntime: FATAL EXCEPTION: main
07-30 11:22:04.352  6181  6181 E AndroidRuntime: Process: org.cyanogenmod.audiofx, PID: 6181
07-30 11:22:04.352  6181  6181 E AndroidRuntime: Theme: themes:{default=, iconPack:org.twelf.cmtheme}
07-30 11:22:04.352  6181  6181 E AndroidRuntime: java.lang.RuntimeException: Unable to start service [email protected] with Intent { act=android.media.action.OPEN_AUDIO_EFFECT_CONTROL_SESSION cmp=org.cyanogenmod.audiofx/.HeadsetService (has extras) }: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3073)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.app.ActivityThread.-wrap17(ActivityThread.java)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1461)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.os.Handler.dispatchMessage(Handler.java:102)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.os.Looper.loop(Looper.java:148)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.app.ActivityThread.main(ActivityThread.java:5475)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at java.lang.reflect.Method.invoke(Native Method)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: Caused by: java.lang.RuntimeException: Cannot initialize effect engine for type: 0bed4300-ddd6-11db-8f34-0002a5d5c51b Error: -3
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.media.audiofx.AudioEffect.<init>(AudioEffect.java:411)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.media.audiofx.Equalizer.<init>(Equalizer.java:139)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at org.cyanogenmod.audiofx.HeadsetService$EffectSet.<init>(HeadsetService.java:95)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at org.cyanogenmod.audiofx.HeadsetService.addSession(HeadsetService.java:208)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at org.cyanogenmod.audiofx.HeadsetService.onStartCommand(HeadsetService.java:431)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	at android.app.ActivityThread.handleServiceArgs(ActivityThread.java:3056)
07-30 11:22:04.352  6181  6181 E AndroidRuntime: 	... 8 more
07-30 11:22:04.354   819   835 W ActivityManager: Process org.cyanogenmod.audiofx has crashed too many times: killing!

EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?

 

[SpiritCroc]

EDIT: Additional question: Why did you go for omnirom sources and not directly for sonyxperiadev?

I'm a bit lazy and they have inline kernel building while sonyxperiadev use a prebuilt kernel.
Additionally, they have some more modifications like TWRP configs which can become handy when building some custom ROMs, and they even have some commits cherry-picked from CM device tree (e.g. in order to enable reboot to recovery), while sonyxperiadev is clearly aimed at pure AOSP.
It worked fine when I was experimenting with different device trees for DU, and for now I just stick with it.
I think I'm going to directly fork sonyxperiadev when Nougat arrives, though

 

[yjosipy]

Now this thead has explained a lot of my confusion regarding recovery i have tried ACIP but because there was only 2-3 Cpu gouvernors and device was always hot (something is causing increased temps and batt drain)anyway there are 2 recoverys one that we call real recovery and that one after power on which flashes alongside ROM.
And if you lower the freq of cpu you will get random reboots

Sent from my D5503 using XDA-Developers mobile app

 

[H0bi]

Verry nice Rom. Camera is a bit more stable than the du one.

For me Autorotation don't work.

 

[CmDaRkShAdOw]

I'm sorry. SIM Card works fine. Last time I had issue while flashing and I ignored it. Today SIM card didn't work on DU. Don't know why.

 

[SpiritCroc]

New build is up.
- Fix sensors not working (e.g. no working auto-rotation)
I was surprised by how few people noticed/complained about that...