Removed
Attachments
-
126.5 KB Views: 1,060
-
131.2 KB Views: 1,058
-
162.9 KB Views: 1,054
Last edited:
On my device it shows "charging slowly" but after a few seconds/minutes it starts charging quickly. Can you take a logcat?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
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.snapchat don't work, how fix?
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$PersistentTrustedReceiveraicp_montana_o-13.1-UNOFFICIAL-20190116
Changes
Download: http://www.mediafire.com/file/3cblc9qd2zjqera/aicp_montana_o-13.1-UNOFFICIAL-20190116.zip/file
- 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)
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.
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.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)
I was using the previous build, now it's working perfectly, thanks!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.
Settings -> Apps and notifications -> Notifications -> Notification LEDThanks, ROM is quite stable. I have a question-
How to enable the front battery led for notifications, similar to crdroid in this ROM.
Yes, It was indeed! Actually I flashed the custom kernel on top of that , somehow that was causing trouble. Thanks again.Settings -> Apps and notifications -> Notifications -> Notification LED
I think it should be enabled by default.
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: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"
dd if=/dev/block/bootdevice/by-name/misc of=/external_sd/misc.img
dd if=/dev/zero of=/dev/block/bootdevice/by-name/misc
fastboot erase misc