That sounds a lot like a kernel issue of not ramping up the cpu for usage after wake.
Hmm interesting thought. I'm using the default kernel that comes with the ROM (upgraded from OOS 11). I haven't messed with it.
F i got it.
I mostly wanted to rule out custom settings. Some people like to under clock for the perceived power savings, when often faster ramp up to highest clock speed during use and quick ramp down at rest can net to less power drain.
Msmtool to convert TMobile to global, then u can unlock bootloader (see guide section)My bad . I have one question tho, when I boot into fastboot and type on CMD fastboot devices it doesn't show anything . I have all the drivers, latest adb . And I'm running on 188.8.131.52, any ideea ? P.S. I was trying to unlock the bootloader. Then install the rom.
/* Your warranty is now void. * * I am 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 me for messing up your device, I will laugh at you. */
FIRST INSTALL: 1. Be sure you are using latest OOS11 on both slots. 2. Download this recovery. 2. A) Be sure you have unlocked bootloader B) Reboot to bootloader C) Plug your phone to your PC and do the following commands: fastboot devices (this one to make sure your device is ok to flash) fastboot flash recovery recovery.img fastboot reboot recovery 3. When on recovery (grab it on Downloads section above), select Factory Reset > format data 4. On this step, you can select either format scheme, F2FS or ext4 ( I highly recommend F2FS) *THIS WILL WIPE ALL YOUR DATA, BACKUP YOUR ***** 5. After format is done, click on the back arrow on top left, and click on "APPLY UPDATE", then "APPLY FROM ADB" 6. Now, on your PC, do the following command: adb sideload *insert your derp zip package name here* (sometimes, you should get an error, that gives you an option to continue or not, hit "yes" to continue, that's normal) 7. After it's done, your phone should light up on recovery again, and on your terminal, it should have something like: adb failed to read command:no error. That's normal, just reboot your phone via recovery and you are done MAGISK: 1. Once your settled your phone, reboot to recovery. 2. Hit "APPLY UPDATE", then "APPLY FROM ADB" 3. On your PC, do the following command: adb sideload *insert Magisk package name here* 4. Once it finishes, reboot your phone *DIRTY FLASH (ONLY POSSIBLE IF YOU WERE ALREADY RUNNING AN OLD DERP BUILD): 1. Via OTA (Just hit to download and wait, once download finishes, let it reboot) 1. A) To keep Magisk, you can go to Magisk and select it to "INSTALL TO THE INACTIVE SLOT" before letting it reboot (not supported on A12 for now) 2. Via ADB Sideload. 2. A) Reboot to recovery B) Select 'APPLY UPDATE', then "APPLY FROM ADB" C) On your PC, do the following command: adb sideload *insert your derp zip package name here* D) Once it's done, reboot. To keep Magisk, you will need to repeat the steps on *MAGISK* section