[ROM][8.1][UNOFFICIAL] Android Ice Cold Project v13.1 - Moto G5S ROMs, Kernels, Recoveries, & Other Devel

Removed

---

moto actions?

---

the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly

---

KamiGooDz said:
moto actions?
Click to expand...
Click to collapse
Yes, it's available

---

snapchat don't work, how fix?

---

Update
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
FpX said:
the system is not compatible with the Turbo Power function, it is not the charger because I tested it in Lineage 15 and it is working perfectly
Click to expand...
Click to collapse
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
KamiGooDz said:
snapchat don't work, how fix?
Click to expand...
Click to collapse
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.

---

AsD Monio said:
aicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
January security patch
Fixed battery drain on devices without NFC
Changed default CPU governor for the little cluster to interactive (was performance before, caused some battery drain as well)
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?
I think you need to pass the SafetyNet check for it to work. I passed SafetyNet on this ROM by installing the SafetyPatch Magisk module and enabling Magisk Hide for Google Services Framework and Google Play Store.
Click to expand...
Click to collapse
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)

---

anybody tested nin moto g5S xt1795 indian edition
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:28 AM ---------- Previous post was at 07:26 AM ----------
anybody tested in moto g5S xt1795 indian edition
---------- Post added at 07:29 AM ---------- Previous post was at 07:28 AM ----------
anybody tested in moto g5S xt1795 indian edition ?

---

FpX said:
01-19 12:02:45.025 W/BroadcastQueue( 704): Background execution not allowed: receiving Intent { act=android.intent.action.ACTION_POWER_DISCONNECTED flg=0x4000010 (has extras) } to com.google.android.gms/.chimera.GmsIntentOperationService$PersistentTrustedReceiver
01-19 12:02:45.060 E/MDMCTBK ( 753): [0] - showStatus:MdmCutbackHndler Status: Qmi =1, cg=0, ep=0, vc=0, dc=0, cn=0, wf=0, mf=0,wfd=0, apm=0, usb=0, stopqmi=0, wireless=0, bf=1, md=0,fpf=1
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.003964(secs)
01-19 12:02:45.064 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000189(secs)
01-19 12:02:45.082 E/BatteryExternalStatsWorker( 704): no controller energy info supplied for bluetooth
01-19 12:02:45.113 E/QCOM PowerHAL( 488): extract_stats: failed to open: /d/system_stats Error = No such file or directory
01-19 12:02:45.114 E/BatteryExternalStatsWorker( 704): modem info is invalid: ModemActivityInfo{ mTimestamp=3549929 mSleepTimeMs=3248076 mIdleTimeMs=-3228711 mTxTimeMs[]=[0, 0, 0, 0, 0] mRxTimeMs=280 mEnergyUsed=0}
01-19 12:02:45.173 E/MDMCTBK ( 753): [0] - eventLoop:Event Loop - time to execute = 0.000448(secs)
Click to expand...
Click to collapse
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.

---

AsD Monio said:
All of these lines are also present in the logcat on my device and they do not seem to be related to charging. Can you send the full logcat? And maybe a dmesg kernel log since it may be kernel related. Also, what model do you have (XTxxxx) and which firmware are you running? Does it still not work in the new build? The old one from the 13th had some battery drain which could result in slow charging, especially on models without NFC - the NFC service caused a permanent wakelock.
Click to expand...
Click to collapse
I was using the previous build, now it's working perfectly, thanks!

---

Update
aicp_montana_o-13.1-UNOFFICIAL-20190121
Changes
Enforcing SELinux
Download: http://www.mediafire.com/file/hquz82ge8werfgf/aicp_montana_o-13.1-UNOFFICIAL-20190121.zip/file

---

Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.

---

newinnov said:
Thanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Click to expand...
Click to collapse
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.

---

AsD Monio said:
Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
Click to expand...
Click to collapse
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.

---

Flashed it om my wifes phone yesterday, she's very happy, less battery drain and wifi is better, which was the main reason to try a custom rom.
Thanks guys!

---

Hi, is Fingerprint, camera photo/video recording, and Moto display notifications working good ?
Thank´s

---

One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"

---

SvenHee said:
One thing is weird, the phone always reboots to twrp. To boot the system I then have to reboot from twrp to bootloader and then press "start"
Click to expand...
Click to collapse
I had that happen to me as well, it's not the ROM's fault. Either fastboot or the stock recovery store some data in the /misc partition. That tells the bootloader/kernel to boot to recovery by default. It's probably meant to ensure that a partially upgraded system does not get booted while flashing a stock ROM. To fix it just wipe the /misc partition, I recommend making a backup first. I used dd in the terminal in TWRP for both operations (adb shell will work as well but it has some problems with displaying some characters in the Windows command prompt). To back up the partition:
Code:
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
^ (replace "external_sd" with "data/media/0" to save it in the internal storage instead of the external microSD card)
To wipe /misc:
Code:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
It may also work using fastboot, though I have not tried this way:
Code:
fastboot erase misc

---

Thanks!
That is slightly intimidating to execute but I'll give it a go!

---

aicp_montana_o-13.1-UNOFFICIAL-20190116
My device : xt1799-2
64bit os.
VoLte works for my xt1799-2.
Bugs:
1. Can't copy any file from the device to my PC. The same bug in crDroid 8.1.0 rom. And lineageos. This happens in all the third party rom between 8.1.0-9.0. Date at least before 2019-09-23. But can copy the folder from the device. But also can send file to the device, so weird.
________________________________________________
I see the lineageos 15.1 changelog:
2019-09-23:
September security patch
Optimized SEPolicy
Fixed MTP (thanks to @wiktorek140)
We're back to LTE
________________________________________________
But can copy the folder from the device. But also can send file to the device, so weird.
2. Front camera doesn't work.
3. Fingerprint doesn't work.
4. Delay a lot when you scroll the page, or move the app icon. The same bug in crDroid 8.1.0.
5. Call recorder. If you don't open the speaker, the inner voice recorded from the other side is too small, unable to hear it clearly.