It should and i have never received reports to the contrary. You are, however, free to test and inform me if im wrong so that i can try and fix it
First of all, I loved this version of AICP for Albus. It's extremely light and fast, it don't even compare to others custom roms I've tested before for Albus that run older Androids still with poor performance. It brought this phone back to the life! Many thanks to the team!
Oddly, after installing this AICP 16.1 on my Z2 Play, the recharge feature started to bug:
View attachment 5622871
The phone stopped to recharge when it is turned on. It shows the little lightning indicating the power input, but at the battery config menu, it shows the message: "Not charging" (or "Não está carregando", in portuguese as you can read in the image).
Addly, in the instant I remove the recharge cable with the phone turned on, it abruptly turns off (just like if I removed the battery).
View attachment 5622873
With the phone turned off, it recharges the battery normally. It shows the big image indicating the rechargement (with the lighting icon in the middle, indicating the power input).
View attachment 5622875
But when I remove the recharger cable with the phone turned off, the big image that indicates the rechargement do not disappear. It get stuck in the screen without the lighting part, but the stand-by mode keeps working normally (the screen continues to turn off for inativite, and turns back on if I click any button, but always at this recharging screen without the lightning icon).
Once stucked at this recharging mode, I have to hold the power buttor for many seconds to force the phone to reboot into the Android system.
1. I have changed the battery recently. Unfortunately, I didn't tried to recharge the new battery with the stock rom before to flash the AICP 16.1, battery experts may say if it could be a battery flaw rather than the rom.
2. I'm not using generic rechargers (I tested in multiples newer original Motorola chargers).
fastboot oem config bootmode " " fastboot reboot
That's the first time i've seen that. Cool that you figure it out!
I was over-enthusiastic, sorry about that... But first night after update battery consuption really was 1%, unfortunately later on it went back to 3-4% percent as usual... Apparently some app was loaded next day, or some process was activated again, I don't know.
If you are on stock but still get no signal then i can't help you. I can help you as far as the ROM is concerned. You might want to try RETAIL or RETIN and see if either one helps
#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. * */
I am working on a 4.9 port, just it's tricky to give timelines. For example, it took me 2 months to get to userspace, 2 weeks to bring up nfc, half of usb, camera, touchscreen,audio. And now it's taking me 3 months to fix the other half of usb and fighting the front cameraoh alright. i was just curious since i couldnt find any device trees for albus on 12, i think ill try experimenting with gsi, although a full custom rom would be better.
anyways thanks for all the great work you do on this device, the z2 play would be no where without your work.
Really sounds like your phone is using the old O modem/firmware; all modern Q+ roms require P modem (you just need to flash NON-HLOS.bin from the P RETAIL release)
I think i could spoof the data in kernel, but i wouldn't recommend doing this; if your battery gets too hot you can just have a fire in your hands. Li-Pol batteries are extremely sensitive to heat which is why these devices have a dedicated battery temp sensor