PRO1, AICP 16.1 (Android R) Official Build

[Hook 3,005]

Updated to the  27 OCT weekly via OTA.  All went smoothly and root was maintained, October security patch.

[EskeRahn 5,451]

1 hour ago, Hook said:

Updated to the  27 OCT weekly via OTA.  All went smoothly and root was maintained, October security patch.

(do with flash - after some troubles with win11)

[EskeRahn 5,451]

Minor bug. Just got this notification:

I would say a bit early to suggest to turn on the battery saver at 94% *LOL*

[EskeRahn 5,451]

26 minutes ago, EskeRahn said:

I would say a bit early to suggest to turn on the battery saver at 94% *LOL*

....it happened shortly after unplugging at 98%. Which in it self will give a drop in voltage. I then checked for new app updates at the Android Market. So in total it went from 98 to 94 in fairly short time, and the logic mathematically predicts that it will be depleted shortly....

Perhaps this could be prevented by adding a check for NOT doing these estimates within the first minutes after unplugging.

[Hook 3,005]

6 hours ago, EskeRahn said:

Minor bug. Just got this notification:

I would say a bit early to suggest to turn on the battery saver at 94% *LOL*

Just, FYI, I am not getting this.  Could an app you have be triggering this?

[EskeRahn 5,451]

58 minutes ago, Hook said:

Just, FYI, I am not getting this.  Could an app you have be triggering this?

Well there is strictly nothing wrong, it is just an unwanted warning. When they have two points with 98 and 94 % with 2½ minutes distance, the matematical extrapolation is about 1hour remaining stamina....

The problem is if the estimate is just mathematical or sensible...

[EskeRahn 5,451]

Update to November 3, with October 1 security patch using OTA went slowly but smoothly.
Known keyboard bug still there (see lineage thread)

With a charger attached and display on during update, there was a slight decrease in the estimated remaining percentage (25 to 23%) during the install. It only seemed to pull about 0.2A at 5V, or roughly 1W from the charger. That was a bit odd. After boot it went to 1A (5W) - as I would expect (using a slow charger to be kind to the battery).

[Hook 3,005]

Updated to the  03 November weekly via OTA.  All went smoothly and root was maintained, October security patch.

[Hook 3,005]

Updated to the  10 November weekly via OTA.  All went smoothly and root was maintained, November security patch.

[agent008 243]

Wiped my phone which was still running AICP beta, installed November 10th build yesterday. I'm battling SafetyNet issues now but the ROM is running fine.

[agent008 243]

Hey guys, I'm having an issue with location. I already had the same problem on AICP Q beta. (Beta also had an issue with notifications. Most apps' notifications never played a sound or vibrated, this is now working on AICP R).

I can't reliably get my location on Google Maps and other apps that depend on Google's location services infrastructure. I've already gone through all of the location settings and permissions to no avail.

It seems that apps that communicate directly with the GPS work OK.

Does anybody have any suggestions? Is AICP's standard behaviour to not allow location to work?

My setup:

* AICP 16.1 - 20211110 build
* MindTheGappas 20210920 build
* Magisk 23.0 with Props Config, Riru and safetynetfix
* Props set up to simulate a Google Pixel 5 with Android 11

Help needed... Thanks in advance!

Edited November 11, 2021 by agent008

[Hook 3,005]

1 hour ago, agent008 said:

Hey guys, I'm having an issue with location. I already had the same problem on AICP Q beta. (Beta also had an issue with notifications. Most apps' notifications never played a sound or vibrated, this is now working on AICP R).

I can't reliably get my location on Google Maps and other apps that depend on Google's location services infrastructure. I've already gone through all of the location settings and permissions to no avail.

It seems that apps that communicate directly with the GPS work OK.

Does anybody have any suggestions? Is AICP's standard behaviour to not allow location to work?

My setup:

* AICP 16.1 - 20211110 build
* MindTheGappas 20210920 build
* Magisk 23.0 with Props Config, Riru and safetynetfix
* Props set up to simulate a Google Pixel 5 with Android 11

Help needed... Thanks in advance!

Google Maps does fine with my location, but I had to agree to allow it to use location services or whatever they call it.  It was a pop-up that showed up when I hit the locate icon.  I'm using  Open Gapps, but I wouldn't expect that to make a difference.

[agent008 243]

10 minutes ago, Hook said:

Google Maps does fine with my location, but I had to agree to allow it to use location services or whatever they call it.  It was a pop-up that showed up when I hit the locate icon.  I'm using  Open Gapps, but I wouldn't expect that to make a difference.

Thanks. Yes, I also agreed to location services. But my phone often loses GPS fix and is usually clueless about where it is (maybe it's a good thing so nobody's tracking me? 😁)

I had OpenGapps on the Q Beta, and also tried OpenGapps with this fresh AICP R install. Didn't make a difference, couldn't make SafetyNet nor GPS work with either of them.

I'm now suspicious of the issue discussed here: 

But, I don't know how to change this file on my phone. Having Magisk installed, it seems I do not have a straightforward /system mountpoint? 🧐

[Hook 3,005]

6 minutes ago, agent008 said:

But, I don't know how to change this file on my phone. Having Magisk installed, it seems I do not have a straightforward /system mountpoint? 🧐

Unfortunately, I'm not much help here.  I simply us Magisk for SU, so I flashed it as a zip and never even open Magisk Manager.  I don't care about safetynet for anything I do.

[EskeRahn 5,451]

I just tried on mine (AICP without Magisk),
I get no fix at all so something is broken indeed.
I'm a little unsure if it was on Lineage or AICP I had it working before (seldom have location on).
But I THINK it has been working on AICP-R for me earlier....

[claude0001 1,337]

14 hours ago, agent008 said:

But, I don't know how to change this file on my phone. Having Magisk installed, it seems I do not have a straightforward /system mountpoint?

In LOS 16.0 /system is no mountpoint. It is a regular folder under /. Do not know about Android 11.

Anyway, my gps.conf is actually at /vendor/etc/gps.conf (with /vendor being the mountpoint of /dev/block/sde36 in my case). /system/vendor is just a symlink to there.

Remember that, even with root access, you cannot easily write to those system folders as they are mounted read-only. You have to first do 

adb root
adb remount

(after enabling adb of course). Then you sould be able to edit every system file from a root CLI. The remounting is not persistent. At the next boot everything will be ro again.

Edited November 12, 2021 by claude0001

[EskeRahn 5,451]

Update to November 17, with November 5 security patch using OTA went slowly but smoothly.
Known keyboard bug still there (see lineage thread)

[EskeRahn 5,451]

I have for the first time had the 'not really charging' bug.
No matter if connected to fast charger or slow charger, and no matter how many times I unplugged and re-plugged.
Restarting brought the charging (connected to fast charger) up from 3mA(!) to 300mA. Unplugging and replugging brought it to 2000mA, where I disconnected and connected to slow charger, charging with 1000mA.

I plugged it last night, and it kept it at 18% over night but did not really charge...
(currently downloaded and now installing update)

[EskeRahn 5,451]

Update to November 24, with November 5 security patch using OTA went smoothly.
Known keyboard bug still there (see lineage thread)

[EskeRahn 5,451]

1 hour ago, EskeRahn said:

I plugged it last night, and it kept it at 18% over night but did not really charge...

My GUESS is that it is a bug in the system that is supposed to prevent overcharging while plugged in and about fully charged, by keeping it an about fixed level.
In some circumstances it kicks in too soon, and keeps it at way too low fixed limit (I plugged it in at 17% yesterday)

[marmistrz 93]

Sounds plausible. I left the phone overnight at 63% and plugged in (but not really charging) and it remained precisely at 63%

[EskeRahn 5,451]

Update to December 1, with November 5 security patch using OTA went smoothly.
Known keyboard bug still there (see lineage thread)

(The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

[EskeRahn 5,451]

Update to December 8, with November 5 security patch using OTA went smoothly.
Known keyboard bug still there (see lineage thread)

(The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

[EskeRahn 5,451]

Update to December 15, with December 5 security patch using OTA went smoothly.
Known keyboard bug still there (see lineage thread)

(The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)

[EskeRahn 5,451]

Update to December 22, with December 5 security patch using OTA went smoothly.
Known keyboard bug still there (see lineage thread)

(The stage after download and install called "Finalising package installation" is surprising slow though - like it is on LineageOS)