[ROM] [7.1.2] [Substratum/OMS] [UNOFFICIAL] [Honami] Android Ice Cold Project 12.1

[CodeZero]

.
.
.
.

AICP​

Android Ice Cold Project​

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

Until lollipop, ROM has always been AOKP based. Unfortunately, since AOKP either stopped development or will make a comeback later this year, we changed our base to CyanogenMod when it comes to hardware, drivers and some features.

If there are any bugs, either we will sort them or CM team if it concerns their modifications. This ROM isn't CM supported so no need to report errors or bugs to them!!
.
.
.
.
.

• 
  Display and animations:
  • System animations
  • Toast icon and animation
  • Power menu animation
  • IME animation
  • LCD densidy changer
  [*]Status bar:
  • Clock style (position, date view, date format, color, font type and size, seconds)
  • Status bar icons control
  • Battery Icon style (percentage, icon type)
  • Brightness control
  • Show notification count
  • Quick pulldown on QS
  • Superuser indicator control
  • Headset icon
  • AICP logo
  • Traffic Indicators
  • Carrier Label
  • Battery bar
  • Statusbar weather temperature
  [*]Notification drawer:
  • Brightness slider
  • Time contextual header
  • Weather info settings
  • CAF Task Manager
  • Force expanded notifications
  • Disable immersive mode messages
  [*]Recents panel:
  • Clear all button settings
  • Show/hide search bar in recent menu
  • Recents in fullscreen
  • Show/hide clock and date in recent menu
  • Memory bar
  [*]Lock screen:
  • Show/hide music visualizer
  • Show/hide media cover art
  • Lock screen shortcuts
  • Mid-Screen shortcuts
  • Lock screen blur
  • DT2S on lockscreen
  • Lock Clock fonts
  • Lockscreen weather options
  [*]Buttons:
  • Enable/disable navigation bar buttons
  • Left-handed mode
  • Buttons and layout settings
  • Adjust navigation bar dimensions
  • CM button long press, double press features
  • SlimDim
  • Power menu settings
  • Press power button twice for camera
  [*]Misc:
  • Pie Control
  • Gesture Anywhere
  • App Circle Bar
  • Slim Recents
  • OmniSwitch
  • Scrolling cache settings
  • Disable FC notifications
  • DT2S on navigation bar
  • Launch music app when headset is connected
  • Enable/disable screenshot sound
  • Three fingers swipe for screenshot
  • System App remover
  • Take logcat, kmesg, dmesg on the go! (AicpExtras -> Log that 's'hit)
  • AICPStats
  [*]Quick Settings toggles:
  • QS Compass Tile
  • QS NFC Tile
  • QS Sync Tile
  • QS Volume Tile
  • QS Profiles Tile
  • QS USB tether Tile
  • QS Screen timeout Tile
  • QS Performance Tile
  • QS Lockscreen toggle Tile
  • QS Ambient Display Tile
  • QS Live Display Tile
  • QS Brightness Tile
  • QS ScreenOff Tile
  • QS Screenshot Tile
  • QS Expanded desktop Tile
  • QS Music Tile
  • QS Reboot Tile
  • QS LTE Tile
  • QS Nav bar Tile
  • QS SlimPie Tile
  • QS App circle bar Tile
  • QS App side bar Tile

In the beginning we would like to thank:

• CM team
• maxwen
• SlimBean rom team
• CarbonRom team
• LiquidSmooth rom team
• Omni rom team
• DU team
• Community

• @LorD ClockaN
• @zipsnet
• @n3ocort3x
• @semdoc
• @eyosen
• @alienmind
• @Chezbel
• @Drgravy
• @eboye
• @TheStrix
  .
  .
  .
  

We are now paying for servers that build nightlies 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

AICP ROM Download link: Sony Xperia Z1 (Honami)

Gapps Download link: Open Gapps

Full Changelog link: goo.gl/mIgmYG

You can also view changelog at AicpExtras -> About -> Changelog on your phone

- Same as 3.4 KERNEL LineageOS-14.1
​

ROMs should contain everything you need to enjoy Nougat. You are not required to install any Add Ons, simply download the latest ROM, Google Apps, flash it, and go!
You are STRONGLY recommended to fully wipe your device before flashing, and if possible avoid restoring system apps and system data with Titanium Backup - these 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 strange behavior.



How to flash:

• Install latest TWRP/CWM/Philz recovery on your device.
• Make a backup of your current ROM.
• Wipe system, data, cache and dalvik.
• Flash ROM.zip and Googleapps.zip.
• Flash modem.zip
• Reboot system and setup!
• First boot takes time.. So patiently wait or have a pack of chips until it boots

PREREQUISITE FOR OTA:
To be able to flash over OTA app, TWRP recovery is needed!
You can still use CWM and OTA app, but only to download zip file and flash it manually from within recovery. Zip gets saved under AICP_ota folder on your internal SDcard.

If you want to contribute to the AICP or wanna see what is being worked on/merge feel free to visit our gerrit, link is at the bottom!!!

ROM:
Github link: https://github.com/AICP
Gerrit link: http://gerrit.aicp-rom.com

AICP Google+ community

XDA:DevDB Information
Android Ice Cold Project 12.1, ROM for the Sony Xperia Z1

Contributors
CodeZero
ROM OS Version: 7.x Nougat
ROM Kernel: Linux 3.4.x
Based On: LineageOS

Version Information
Status: Beta

Created 2016-11-09
Last Updated 2017-07-14

 

[CodeZero]

Kernel Source:
Github link: https://github.com/SuperLamic/android_kernel_sony_msm8974/tree/cm-14.1​

 

[CodeZero]

Note :-
Here are some basic rules you guys need to know before posting issues

DO NOT report issues if you didn't do full wipe
If you have issues then please mention your model number and variant and also if youve flashed any additional mods
Provide logcats if you have any FCs or bootloops
DO NOT report issues if you flash custom kernel
Do NOT post information and features and comparison of other ROMS
Flash GAPPS after every release to avoid issues with Google apps FCs
DO NOT ask for ETA PLEASE provide logs if you have any sort of issues.
Enjoy​

Credits :- ​

Thanks to ROM have been built on
Legacy Server
Special Thanks to SuperLamic, tomascus, nailyk, rcstar6696, xkeita, jerpelea , alviteri and to all the developers who have contributed
Let me know if I missed anyone​

 

[LinkRaf]

Nice work man!

 

[monnett]

Hellyeah awesome work :good::laugh:

 

[santeria27]

Modem link???

Sent from my Xperia Z1 using XDA-Developers mobile app

 

[CodeZero]

Modem link???

Sent from my Xperia Z1 using XDA-Developers mobile app

What variant you own??? if you own C6092 than you need to flash modem.zip from here http://xdaforums.com/showthread.php?t=2614645

 

[santeria27]

Ah okay i have c6903 thx for fast info i will now test it!!

Sent from my Xperia Z1 using XDA-Developers mobile app

 

[Snp Mania2]

Very glad to see great @CodeZero come at here

 

[gauravbhakuni90]

Hate to say this but seems like battery bug is still here too . The battery icon doesn't show it charging but it is charging although at a slower rate . But i'll take it cuz atleast it is charging . Else everything is great. Thanks dear dev for your efforts .

Edit- After a reboot the system detects correctly whether charging over USB or on AC . And the icon is working correctly now .

 

[Snp Mania2]

Yes also same on MM rom need a reboot for charging work,but after that if unplug n plugin again the charging is not working, sorry bad english

 

[papica]

bootleader

 

[Zetsuno]

Bootloader must by unlocked?

 

[Masterblop]

Bootloader must by unlocked?

Yes

 

[CodeZero]

Yes also same on MM rom need a reboot for charging work,but after that if unplug n plugin again the charging is not working, sorry bad english

Weird for me everything is working fine except camera even charging is fine from the first boot itself can you please get me logs ?

 

[lm/\/trix]

Installed and everything is fine, but no simcard detected.

Sony Z1 Unlocked C6903

 

[CodeZero]

Installed and everything is fine, but no simcard detected.

Sony Z1 Unlocked C6903

try to reboot your device and check again might be glitch

 

[lm/\/trix]

Sim detection was because of Pin.

Why FM Radio tries to get Root Access?

Folder mount failed to mount folders with built in Super User. No problem with SuperSu.


Installed GTA SA. there ARE some lag...

 

[pokepokepoke]

Weird for me everything is working fine except camera even charging is fine from the first boot itself can you please get me logs ?

Sim detection was because of Pin.

Why FM Radio tries to get Root Access?

Folder mount failed to mount folders with built in Super User. No problem with SuperSu.


Installed GTA SA. there ARE some lag...

Camera isn't working at all or is it dark like in Aosp.

Actually FM Radio is Aicp Extras app trying to get root access that's an upstream AICP bug

 

[santeria27]

root: flash the last supersu.zip via recovery thats all and works fine! and mobile data by me dont work!!!! sms,tele,etc works

Telephony

One of the most common features related to making phone calls, call blocking, is finally now being made a requirement for any device running Android 7.0 Nougat.

7.4.1.1. Number Blocking Compatibility
Android Telephony device implementations MUST include number blocking support and:
MUST fully implement BlockedNumberContract and the corresponding API as described in the SDK documentation.
MUST block all calls and messages from a phone number in ‘BlockedNumberProvider’ without any interaction with apps. The only exception is when number blocking is temporarily lifted as described in the SDK documentation.
MUST NOT write to the platform call log provider for a blocked call.
MUST NOT write to the telephony provider for a blocked message.
MUST implement a blocked numbers management UI, which is opened with the intent returned by TelecomManager.createManageBlockedNumbersIntent() method.
MUST NOT allow secondary users to view or edit the blocked numbers on the device as the Android platform assumes the primary user to have full control of the telephony Page 59 of 85 services, a single instance, on the device. All blocking related UI MUST be hidden for secondary users and the blocked list MUST still be respected.
SHOULD migrate the blocked numbers into the provider when a device updates to Android 7.0.


9.13. Safe Boot Mode
Android provides a mode enabling users to boot up into a mode where only preinstalled system apps are allowed to run and all third-party apps are disabled. This mode, known as “Safe Boot Mode”, provides the user the capability to uninstall potentially harmful third-party apps. Android device implementations are STRONGLY RECOMENDED to implement Safe Boot Mode and meet following requirements:
Device implementations SHOULD provide the user an option to enter Safe Boot Mode from the boot menu which is reachable through a workflow that is different from that of normal boot.
Device implementations MUST provide the user an option to enter Safe Boot Mode in such a way that is uninterruptible from third-party apps installed on the device, except for when the third party app is a Device Policy Controller and has set the UserManager.DISALLOW_SAFE_BOOT flag as true.
Device implementations MUST provide the user the capability to uninstall any third-party apps within Safe Mode.

Users who own a separate Android device for their work may now be met with a separate lock screen to grant access to certain apps, an attempt by Google to allow for enterprises to sandbox critical apps separately in case clumsy workers allow a third-party access to their device.

3.9.2 Managed Profile Support
Support the ability to specify a separate lock screen meeting the following requirements to grant access to apps running in a managed profile.
Device implementations MUST honor the DevicePolicyManager.ACTION_SET_NEW_PASSWORD intent and show an interface to configure a separate lock screen credential for the managed profile.
The lock screen credentials of the managed profile MUST use the same credential storage and management mechanisms as the parent profile, as documented on the Android Open Source Project Site
The DPC password policies MUST apply to only the managed profile’s lock screen credentials unless called upon the DevicePolicyManager instance returned by getParentProfileInstance

USB Connections

If you’re familiar with the work done by Nathan K. and Benson Leung with regards to USB Type-C cables, then you might be somewhat aware of the issues regarding USB Type-C interoperability and safety. Many third-party fast-charging methods modify the voltage levels and other parts to provide faster charging at the expense of the device losing compatibility with USB Power Delivery (USB PD) methods. Google is now strongly recommended that OEMs stop modifying their charging methods in this manner, with the possibility of revoking CTS in the future for devices that fail to meet these guidelines.

7.7.1 USB Peripheral Mode
Type-C devices are STRONGLY RECOMMENDED to not support proprietary charging methods that modify Vbus voltage beyond default levels, or alter sink/source roles as such may result in interoperability issues with the chargers or devices that support the standard USB Power Delivery methods. While this is called out as “STRONGLY RECOMMENDED”, in future Android versions we might REQUIRE all type-C devices to support full interoperability with standard type-C chargers

Mobile Data Management

Data Saver is one of the low-key features introduced in Nougat. The feature allows users to restrict background data access only to those apps that are white-listed. This is especially useful to users who are on plans with low data limits. Unfortunately, this feature is not required to be implemented by OEMs.

7.4.7. Data Saver
Device implementations with a metered connection are STRONGLY RECOMMENDED to provide the data saver mode. If a device implementation provides the data saver mode, it:
MUST support all the APIs in the ConnectivityManager class as described in the SDK documentation.
MUST provide a user interface in the settings, allowing users to add applications to or remove applications from the whitelist.
Conversely if a device implementation does not provide the data saver mode, it:
MUST return the value RESTRICT_BACKGROUND_STATUS_DISABLED for ConnectivityManager.getRestrictBackgroundStatus
MUST not broadcast ConnectivityManager.ACTION_RESTRICT_BACKGROUND_CHANGED
MUST have an activity that handles the Settings.ACTION_IGNORE_BACKGROUND_DATA_RESTRICTIONS_SETTINGS intent but MAY implement it as a no-op.