Question Play systemupdate keeps coming back [debug / technical] - Google Pixel 6 Pro

I have something weird with the Google Play systemupdate.
I an currently on 'September 1, 2022'
When I click on it then once every 5 days or so I get a message saying that there is an update of 712K available (looks small to me).
Then 'something' is installed and the phone asks to restart. I obviouysly reboot.
However, I have a script (using adb) that checks ALL packages and versions and when I run this BEFORE and AFTER the upgrade -> NOTHING has changed.
Attached is an adb log where I grepped for 'Finsky'.
In the log you can see that it downloads a package called: com.android.mainline.libs
And from what I can judge from the log: the package is successfully decompressed and the resulting APK is copied to some location.
Then - judging from the log - I am assuming that the phone tries to install that package.
Then at the end of the log it says:
Code:
10-14 16:44:18.504 6712 7515 I Finsky : [65] mgc.a(91): IQ: no installs to evaluate. Skipping.
To be clear: this package does NOT exist on my phone.
As mentioned, after rebooting, NOTHING has changed (same packages, same versions).
Then for a few days I don't get any updated when I press the Play systemupdate.
Then suddenly, the same 712K reappears and the whole thing repeats again.
(play systemupdate remains on September 1, 2020)
Anybody have any clue what's going on here???
Could someone please check if you have the package com.android.mainline.libs on your phone?
Just do:
Code:
> adb shell
$ pm list packages | grep libs
and let me know if you see any output there.
:- confused

@foobar66
I think this is an issue on Google's end:
I have a similar issue on an entirely different phone (Nokia X100, T-Mobile US variant).
The phone shipped with an out-of-date Google Play system update (Phone release date 10/21,the update was dated 05/21).
It showed an update was available (very small size, in kb's). I'd install, reboot. The update would install, then, the phone would reboot on its own a minute later & the update would disappear. This went on for 5-6 months until I finally got an actual update to install that brought me up to July 2022.
The issue is still ongoing, as I'm showing another update is available, that gets me to August 2022.It installs, reboots, uninstalls back to the older July 2022 Google Play system update.
I tried factory resets, they're of no help.
The only suggestion that I have is to reach out to Google directly.

Thanks for the story. I guess I will have to wait some time to see if there is a future update which actually installs. I would prefer not to do a full reset as you indicate that it did not help.

I have this issue, but with just YouTube. Every time I install the update then reboot, it reverts to 17.17.37. A real pain.

Well I just got this 49mb system update
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

@foobar66
Forgot to ask:
Which system update are you on?
FWIW, I'm on the latest Android 13 Beta & both the (system) Security update & Google Play System update are on October 2022.

I am on October 5 system update (latest) so standard A13.

After installing the 49mb update I got that 712kb update, A13 stable SEP

So after I installed the 712kb that was it, it didn't ask me to install again, they must have forgot to add it into the 49mb system update lol

kevinireland11 said:
So after I installed the 712kb that was it, it didn't ask me to install again, they must have forgot to add it into the 49mb system update lolView attachment 5734907
Click to expand...
Click to collapse
That sounds exactly like what the OP described.
But, even after that small update, he did a deep look at things & there is no evidence of any actual addition of info/update installed from the previous September 2022 Google Play System update.

KOLIOSIS said:
That sounds exactly like what the OP described.
But, even after that small update, he did a deep look at things & there is no evidence of any actual addition of info/update installed from the previous September 2022 Google Play System update.
Click to expand...
Click to collapse
Exactly, looks same like I have ... wait a couple of days and check that this 712Kb comes back. It keeps coming back for me, installs, then reboot (and I guess update is rolled back), then re-appears a few days later.
Will be interesting to see if I get a bigger October update ... usually I lag behind 1 month with Google play systemupdates.

Hmm ... interesting ... looks like com.android.mainline.libs does exist on the phone, it's that one which - I believe - the 712K update is trying to upgrade (and which fails for some reason - or may be 'not needed').
Code:
[email protected][/]# pm list packages --apex-only --show-versioncode
package:com.google.android.neuralnetworks versionCode:330443000
package:com.google.android.conscrypt versionCode:330443020
package:com.google.android.adbd versionCode:330444002
package:com.google.android.media versionCode:330443030
package:com.google.android.compos versionCode:1
package:com.google.android.os.statsd versionCode:330443000
package:com.google.android.adservices versionCode:330442000
package:com.google.android.permission versionCode:330912010
package:com.android.btservices versionCode:339990000
package:com.google.pixel.camera.hal versionCode:409012097
package:com.google.android.appsearch versionCode:330443000
package:com.google.android.mediaprovider versionCode:330911040
package:com.google.android.vndk.v33 versionCode:1
package:com.google.android.resolv versionCode:330910000
package:com.google.android.art versionCode:330443060
package:com.google.android.scheduling versionCode:330443010
package:com.google.android.cellbroadcast versionCode:330911010
package:com.android.apex.cts.shim versionCode:1
package:com.google.android.sdkext versionCode:330810010
package:com.google.android.ondevicepersonalization versionCode:330442000
package:com.google.android.media.swcodec versionCode:330443040
package:com.google.android.ipsec versionCode:330443010
package:com.google.android.virt versionCode:1
package:com.google.android.tzdata4 versionCode:331012000
package:com.google.android.runtime versionCode:1
package:com.google.android.wifi versionCode:330910030
package:com.google.android.uwb versionCode:330810010
package:com.android.i18n versionCode:1
package:com.google.android.extservices versionCode:330443000
package:com.google.mainline.primary.libs versionCode:330932000
package:com.google.android.tethering versionCode:330911010

Good article explaining the Google Play systemupdates can be found here:
Project Mainline explained: How Google Play System Updates work
Project Mainline is one of Google's biggest initiatives to reduce fragmentation and improve security in Android. Here's how it works.
blog.esper.io

And, also interesting command:
Code:
[email protected][/]# cmd transparency get apex_info -v
APEX Info:
com.google.android.appsearch;330443000:a2c600c6e1d52812003d2fcb929b26779147b677f758114386231da515cf7f30
Install location: /data/apex/decompressed/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: AppSearch
Module visibility: hidden
com.google.android.adservices;330442000:c760e1d1743ac0cff8673f74271f4d3e42c7ff6265381458a8c3032d9174071a
Install location: /data/apex/decompressed/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Ad Services
Module visibility: hidden
com.android.apex.cts.shim;1:d360e89d7cc2e3f304229ef8254d626ce221a9eb8dc613987983bda6880bffd4
Install location: /system/apex/com.android.apex.cts.shim.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.adbd;330444002:dd57d98de3a4fe5405afa75ec0da618632abe2acce7b3d58a6c2134ba813cedc
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: ADBd
Module visibility: hidden
com.android.btservices;339990000:2461540e89b9babdb5430d1fd203fbcb455561d77f4532bc4c1c5162b27790e0
Install location: /system/apex/com.google.android.bluetooth.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.compos;1:8558e1c42f70f9bac6158dd7d131802eab0e02ae7d4baf9216f08a4f84b01e9d
Install location: /system_ext/apex/com.google.android.compos.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.art;330443060:e1561888efd71e8c4908f77d5b2988172fc059c339195d8fc764b4826102c3d9
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Android Runtime
Module visibility: hidden
com.google.android.extservices;330443000:7591f33aa4568b3c1223a3a1c3baffceabb4f36576cb5b2a254b51663116631a
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Android Services (APEX)
Module visibility: hidden
com.android.i18n;1:034e5468adeaab036c3132f2d34305a68f9b82b46d48c021f2d1cb8940173787
Install location: /system/apex/com.android.i18n.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.conscrypt;330443020:16d41be92395907fcc20156cd250fb58dd3151a13e8fd8fc4ded54889608d4a8
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Conscrypt
Module visibility: hidden
com.google.android.media;330443030:697bc3212912b01c1dea72f4dd43f85d11c0fe0b8d348d69d90c9a1ebb0546df
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Media
Module visibility: hidden
com.google.android.mediaprovider;330911040:2480386cc0b5fac883a9c3fdb95faaa743a5af6a487f8cf3c3788a78fd609b1d
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Media Provider
Module visibility: hidden
com.google.android.media.swcodec;330443040:718e4783f33b92b6ae9c5d28b580e72c88c76c0a145d5680d3e4156c468a2afd
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Media Software Codec
Module visibility: hidden
com.google.android.neuralnetworks;330443000:9f2415c4d36b4c6b51e41fa59766b9330dbe0e07b3cd88f68ec26de303957b5e
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Neural Networks API
Module visibility: hidden
com.google.android.ondevicepersonalization;330442000:9ce80291035e94f048c41cb2481d018bbe9cab53182b4698bfc1e9a7f9c8206e
Install location: /data/apex/decompressed/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: On Device Personalization
Module visibility: hidden
com.google.android.os.statsd;330443000:2aa8b0dee8541a48f4f9835e12e3e257692de89e084d8cdadd1722762e892e83
Install location: /data/apex/decompressed/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Statsd
Module visibility: hidden
com.google.android.ipsec;330443010:a770e199f7aad099b480df81d669d4d1b33cefa67c3876fb7f122f9486be1429
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: IPSec
Module visibility: hidden
com.google.android.permission;330912010:81b2f2160773d45911751faec4bce24fd76a992e4ab34febac83c101abe73c64
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Permission
Module visibility: hidden
com.google.android.resolv;330910000:ff28067c9a0f70c2ff211dd470abafd69a56ce9308253591325309c81756459e
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: DNS Resolver
Module visibility: hidden
com.google.android.cellbroadcast;330911010:6a568ca448521ff58aa3189f8011215b6dca78500bfa67d0b25736c7456280a9
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Cell Broadcast
Module visibility: hidden
com.google.android.sdkext;330810010:9b963f10159bba65ba72ae8ea2f39c38e7394347842fe1774b592cf1d757fc46
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: SDK Extensions
Module visibility: hidden
com.google.android.runtime;1:76b7294510054103b6bf0f9a2dcf65dcdb1d7570bec8b3642826a56c2af4c5ad
Install location: /system/apex/com.android.runtime.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.tzdata4;331012000:13494225bf87f216ed717a9d29da4b7a25de793eaa315b15d94bbaa305087a70
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Time zone data
Module visibility: hidden
com.google.android.virt;1:996bbe7cc6aad7dd7c1abccc6cf78c433455920fbcf4c50db6cc64a211ea6361
Install location: /system_ext/apex/com.google.android.virt.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.tethering;330911010:3357e8b165d0a77cf30d3327b9242e44e51e4c365c292b396976f0044100731d
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Tethering
Module visibility: hidden
com.google.android.uwb;330810010:8f100f2227cde2421d71173a4c9095d6cf029762968798a3353ad3a659dc7e96
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: UWB
Module visibility: hidden
com.google.android.vndk.v33;1:fcabdb46d2ab408c0e577be689c5b9cb2d92306f99e309fd343cdfe526276b23
Install location: /system/apex/com.android.vndk.current.apex
Last Update Time (ms): 0
Is A Module: False
com.google.android.wifi;330910030:8f8cea16d5c101c1bf32a447f82bc12e195e1cda606cd8c5e770b2cc57a0aa7d
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: WiFi
Module visibility: hidden
com.google.android.scheduling;330443010:9411f4313b026c5c8f6586cdda20e19a1cd8c098a09b812497e155514e23a407
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Device Scheduling
Module visibility: hidden
com.google.pixel.camera.hal;409012097:ccb500fa068056597a175b0d500688c0aa11c4cc2ba0a2b9e6e5d9f4a8ed854c
Install location: /vendor/apex/com.google.pixel.camera.hal.apex
Last Update Time (ms): 0
Is A Module: False
com.google.mainline.primary.libs;330932000:2d86ffbd72435c3c3d01236a1a5bf9b6a2b14da89b1953ebdd8fb80aca80a192
Install location: /data/apex/active/[email protected]
Last Update Time (ms): 0
Is A Module: True
--- Module Details ---
Module name: Dynamic Common Libraries
Module visibility: hidden

OK, so today I got an update of 614K, diff:
Code:
< package:com.google.android.os.statsd versionCode:330443000
---
> package:com.google.android.os.statsd versionCode:330443030
Still on September 2022.

I was on August and thank to this thread checked for a new update.
After reboot: August Version

Related

hidden folders, files...

Since we can extract whole *.FFS and ShpApp.app and ...
I realized that folders complete missing or empty.
For instance folder Security is not visible...
Folder where internal Apps are stored... folder data is empty.
SystemFS\Osp\data
Is full of *.sig and *.htb files.
Thank you very much for TriX.
b.kubica
Best Regards
good.good job
i see some paths in wincomm that i cannot understand what exactly are they
maybe hidden folders??????????
../SHP3/AppSvc/Drm/service/DrmSvcAPI.cpp
/h/bada/Applications/[email protected]@[email protected]@__000/Info/application.xml
any ideas?
../SHP3/AppSvc/Drm/service/DrmSvcAPI.cpp
Click to expand...
Click to collapse
Means apps_compressed.bin
/h/bada/Applications/[email protected]@[email protected]@__000/Info/application.xml
Click to expand...
Click to collapse
Hmmm.
Tempfolder... but I have never seen this action...
Best Regards
I cannot understand what "/h/bada" is
maybe /hidden/bada
it's while installing application via kies
a new one
/etc/powervr.ini
(i know powervr is for GPU)
EDIT
Code:
6576 472.192 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_aco_0029_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(30)
6577 472.227 P00.T09.D001.G77.E125:173C EXCEPTION > OsStartSoftTimer: Started @ different task(Mocha:9) with owner task(IndiServerTask_Ipc:41) for Timer(hTimerBlink_3:0x80290002)
6578 472.227 P00.T09.D001.G77.E125:173C EXCEPTION > OsStartSoftTimer : call back will be expired @ owner task(IndiServerTask_Ipc:41) not current task
6579 472.254 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_aco_0029_01_alt.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(30)
6580 472.299 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_aco_0034_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(34)
6581 472.364 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_agl_0001_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(36)
6582 472.717 P00.T09.D001.G34.E062:1743 EXCEPTION > OsStartSoftTimer: Started @ different task(Mocha:9) with owner task(IndiServerTask_Ipc:41) for Timer(Main_BatteryDrawTimer_32:0x80290001)
6583 472.717 P00.T09.D001.G34.E062:1743 EXCEPTION > OsStartSoftTimer : call back will be expired @ owner task(IndiServerTask_Ipc:41) not current task
6584 472.727 P00.T09.D001.G77.E125:1745 EXCEPTION > OsStartSoftTimer: Started @ different task(Mocha:9) with owner task(IndiServerTask_Ipc:41) for Timer(hTimerBlink_3:0x80290002)
6585 472.727 P00.T09.D001.G77.E125:1745 EXCEPTION > OsStartSoftTimer : call back will be expired @ owner task(IndiServerTask_Ipc:41) not current task
6586 473.227 P00.T09.D001.G77.E125:174D EXCEPTION > OsStartSoftTimer: Started @ different task(Mocha:9) with owner task(IndiServerTask_Ipc:41) for Timer(hTimerBlink_3:0x80290002)
6587 473.227 P00.T09.D001.G77.E125:174D EXCEPTION > OsStartSoftTimer : call back will be expired @ owner task(IndiServerTask_Ipc:41) not current task
6588 473.275 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_agl_0010_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(42)
6589 473.315 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_agl_0012_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(38)
6590 473.341 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_agl_0014_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(22)
6591 473.397 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_agl_0015_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(20)
6592 473.440 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_brief.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(24)
6593 473.488 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0001_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(20)
6594 473.521 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0002_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(28)
6595 473.554 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0004_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(32)
6596 473.599 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0005_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(14)
6597 473.628 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0013_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):( 8)
6598 473.673 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0014_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(10)
6599 473.699 P00.T67.D001.G-1.E-01:0000 ALL > OemFmTfs4SetFileTime : last modified time of "/h/bada/Applications/sg750rl26n/Data/sound/e_hx_m06_hw1_0017_01.msadpcm"is updated. (2010)-(10)-(19) (17):(50):(38)
---------- Post added at 07:41 PM ---------- Previous post was at 07:33 PM ----------
seems while installing an app, all the extracted files goes there
Not new, but...
Command
Code:
FmSecureMode off
With QuB for instance unlock folders like:
Code:
NV
nvm
pdb_profiles
Security
System
Interesting... for me.
If you have activated:
Code:
SHP_CSC_FEATURE_MTP_SHOW_HIDDEN_STORAGE=1
In XPKG5 you can see these folders also in:
Code:
User\HidVol\ExtSys
User\HidVol\IntSys
Not sure if SHP_CSC_FEATURE_MTP_SHOW_HIDDEN_STORAGE=1 is mandatory to set... will check.
But in XXLA1 for instance you can't see folders in User\HidVol\... also after FmSecureMode off...
Also few other folders like temp never seen something in there...
Best Regards
No difference.
With or without SHP_CSC_FEATURE_MTP_SHOW_HIDDEN_STORAGE=1
XPKG5 shows these folders + content in...
Code:
User\HidVol\
Now I will move back to XXLA1 for new tests with path change...
Maybe I can "mount" other folders to Explorer...
First try is to replace
Code:
/AppEx/User/Widget/WRT/
Visible in
Code:
[B]\IntSys[/B]\WidgetApp
First idea to modify Widget.so ...
Result later...
No idea yet what I have to use to fit same length...
Best Regards
Code:
Fm[B]Remove[/B]SymLink
This seems reason why folders are hidden or empty...
Found in WsSyncml.so
Will do some test...
Best Regards

I can't get µg Unified Nlp working

Hello, I´m on CM13 last lightly (this problem occurrs also in last snapshot). I´ve installed µg Unified Nlp (Version 1.6.7 from F-droid) and MozillaNlpBackend but I´m unable to activate the Backend. I recive the "Error initializing backend" message.
Self-Check shows:
Permissions granted​Permission to access approximate ocation (network-based): Unchecked​Network location provider support​Android version supported: Checked​System supports location provider: Checked​UnifiedNlp status​UnifiedNlp is registrated in system: Checked​Location backend(s) set up: Unchecked​Network-based location enabled: Unchecked​What's or where's the problem? Am I missing something?

XSharedPreferences issue with Target API 28

Hi guys i know the issue is Xsharedpreferences even if you set permissions to 777 the xposed cant read the file when the app is compiled with api 28 maybe due to recent selinux changes but if you use target api 27 or below ,the xposed can hook and read preferences properly maybe backward compatibility.
Any guys get to work around this in their xposed modules?
I possible fix i know is that moving the preferences to /data/folder/prefs.xml then it can read
no, api 28 introduced a new SELinux permission
makeworldreadable or 777 is useless
one sulotion is use api 27 or lower
or set SELinux to Permissive(not recommended)
Maybe you can use other methods such as ContentProvider, or put it to sdcard?
BytesReverser said:
Hi guys i know the issue is Xsharedpreferences even if you set permissions to 777 the xposed cant read the file when the app is compiled with api 28 maybe due to recent selinux changes but if you use target api 27 or below ,the xposed can hook and read preferences properly maybe backward compatibility.
Any guys get to work around this in their xposed modules?
I possible fix i know is that moving the preferences to /data/folder/prefs.xml then it can read
Click to expand...
Click to collapse
use this code on initzygote
Code:
final File a = new File("/data/user_de/0/packagename/shared_prefs/prefs.xml");
final File b = new File("/data/user/0/packagename/shared_prefs/prefs.xml");
final File c = new File("/data/data/packagename/shared_prefs/prefs");
File file;
int sdk = Build.VERSION.SDK_INT;
if (sdk == 23) {
file = a;
} else if (sdk < 23) {
file = b;
} else {
file = c;
}
myPref = new XSharedPreferences(file);
myPref.makeWorldReadable();
myPref.reload();
if (myPref == null) {
myPref = new XSharedPreferences(BuildConfig.APPLICATION_ID, xmlPrefs);
myPref = new XSharedPreferences(file);
}
myPref.makeWorldReadable();
myPref.reload();

[ROM][11.0][UNOFFICIAL][Testing] LineageOS 18.1 for Wileyfox Swift

Code:
#include <std_disclaimer.h>
/*
* 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.
*/
Remarks:
This thread is thought to collect issues and ideas. It has to be considered being a TESTING version.
Once everything is mature, an official build may be possible.
Installation:
If you are on stock OS, you need a custom recovery first. You can get the recommended Lineage recovery in the official installation instructions link below.
If you are coming from stock or other ROMs, you need to make a factory reset.
As always, make sure to backup before installing this ROM.
Also make sure you've got the correct firmware installed before installing LineageOS.
More detailed instructions at:
Install LineageOS on crackling
115ek's test builds (for testers only)
Downloads
Recommended Google Apps package:
none: GApps don't fit at the moment. A repartitioning is needed. Currently thinking about this...
Donate to support development:
Donate via PayPal to LineageOS
Changelog
06.12.2021
updated lineage sources
11.09.2021
fixed livedisplay
updated lineage sources
22.07.2021
initial version
reserved
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
petexd said:
It's been a while since I tried 18 and I'm tempted to look at the latest. Before I do, are there any major problems other than gapps. I appreciate it needs to be tested but I'd like to be aware if there are any major parts not working.
Click to expand...
Click to collapse
Livedisplay is not working at the moment.
I had to remove it because it wouldn't load my photos and I didn't have time to play around with it. It's actually my only phone. It did, however, instal basic flamegapps.
I also got error 255 when tryin to restore my backup but I'm up and running now with 17.1. I'll try 18.1 again soon when I have more time to mess around with it and if I can sort out error 255
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
ajjin0 said:
Very cool, thanks! What is the upstreaming status? That would be great as microG builds would be available automatically as well. That one I'd install right away.
Click to expand...
Click to collapse
I've got so less time at the moment. I hope I'll find some to continue the work.
New build is up. Livedisplay is working now.
Download
Wow great work.
@115ek Thank you for the new build.
I tried to compile Lineage18.1 myself, but ended up in a boot loop. I assume this is the relevant part of the log, since it repeats over and over again:
Spoiler
Code:
01-01 21:28:58.399 4357 4357 I [email protected]: LiveDisplay HAL service is starting.
01-01 21:28:58.404 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.458 4357 4357 D DISP_API: disp_api_get_num_display_modes.
01-01 21:28:58.510 4357 4357 D DISP_API: disp_api_get_num_display_modes successful getting num-of-modes = 6.
01-01 21:28:58.512 220 220 I hwservicemanager: getTransport: Cannot find entry [email protected]::IDisplayModes/default in either framework or device manifest.
01-01 21:28:58.512 4357 4357 E HidlServiceManagement: Service [email protected]::IDisplayModes/default must be in VINTF manifest in order to register/get.
01-01 21:28:58.513 4357 4357 E [email protected]: Could not register service for LiveDisplay HAL DisplayModes Iface (-2147483648)
01-01 21:28:58.514 4357 4357 E [email protected]: LiveDisplay HAL service is shutting down.
01-01 21:28:58.521 0 0 I init : Service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) exited with status 1
01-01 21:28:58.521 0 0 I init : Sending signal 9 to service 'vendor.livedisplay-hal-2-0-legacymm' (pid 4357) process group...
01-01 21:28:58.521 0 0 I libprocessgroup: Successfully killed process cgroup uid 1000 pid 4357 in 0ms
01-01 21:28:59.391 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:28:59.391 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
01-01 21:28:59.393 219 4360 W libc : Unable to set property "ctl.interface_start" to "aidl/android.hardware.power.IPower/default": error code: 0x20
01-01 21:28:59.395 0 0 E init : Control message: Could not find 'aidl/android.hardware.power.IPower/default' for ctl.interface_start from pid: 219 (/system/bin/servicemanager)
01-01 21:29:00.392 219 219 I servicemanager: Since 'android.hardware.power.IPower/default' could not be found, trying to start it as a lazy AIDL service
01-01 21:29:00.392 4193 4193 W ServiceManager: Waited one second for android.hardware.power.IPower/default
My local manifest looks like:
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="115ek/android_device_wileyfox_crackling" path="device/wileyfox/crackling" remote="github" />
<project name="115ek/android_device_cyanogen_msm8916-common" path="device/cyanogen/msm8916-common" remote="github" />
<project name="115ek/proprietary_vendor_wileyfox" path="vendor/wileyfox" remote="github" />
<project name="LineageOS/android_kernel_cyanogen_msm8916" path="kernel/cyanogen/msm8916" revision="lineage-17.1" />
<project name="LineageOS/android_hardware_sony_timekeep" path="hardware/sony/timekeep" remote="github" />
</manifest>
Does your manifest look the same? Are there any additional patches I have to apply to get it working? I would highly appreciate it if you could share your steps to build LineageOS 18.1.
mmustermann717 said:
Does your manifest look the same?
Click to expand...
Click to collapse
This should be fine, yes.
mmustermann717 said:
Are there any additional patches I have to apply to get it working?
Click to expand...
Click to collapse
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
Thank you very much! That worked.
I increased the system partition, a little while ago and backups were restoring OK so I've decided to try 18.1 again.
I must say, it performs really well for the stuff I need. I also like that I can now do calendar etc backups to my sdcard. Much more sensible IMO.
Thanks 115ek. A great job.
I'd like to have a go at building but I'm not sure where to start without the explicit menu like 17.1
Thanks to 115ek for the 18.1 set up and to mmustermann717 for his local manifest. I have managed to build 18.1 after a few errors which appeared to be out of memory problems.
I fixed that and was able to complete the build.
Thanks both of you
I was too quick to brag. Im getting a boot loop. I made the changes from 115ek's response #12, so I don't know where I've gone wrong.
Can either of you tell me please?
115ek said:
This should be fine, yes.
Yes. I still have some local changes I didn't push yet. There are two kernel patches required for enforcing SE linux which I didn't upload yet.
But permissive mode should work. You can switch to permissive for now by:
adding androidboot.selinux=permissive to https://github.com/115ek/android_de...7d4427d6896080f77946/BoardConfigCommon.mk#L94
The thing you see in the log is the broken livedisplay. I also have a local unpublished change here:
Code:
--- a/manifest.xml
+++ b/manifest.xml
@@ -184,6 +184,10 @@
<name>IDisplayColorCalibration</name>
<instance>default</instance>
</interface>
+ <interface>
+ <name>IDisplayModes</name>
+ <instance>default</instance>
+ </interface>
<interface>
<name>IPictureAdjustment</name>
<instance>default</instance>
You can try it that way. But in any case I should publish those changes. I just need to find some spare minutes to write a proper commit message and clean things up.
Click to expand...
Click to collapse
I've tried all of this several times. I get a successful build but a boot loop every time.
The lineage source says successful, it doesn't actually boot so I have no idea how to find any error? Is there anything I can look for? Or can you guess?
I'd appreciate the help if you can. Thanks.
Hey
petexd said:
how to find any error?
Click to expand...
Click to collapse
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
petexd said:
Or can you guess?
Click to expand...
Click to collapse
You could, but I'm not sure if that really helps.
petexd said:
Is there anything I can look for?
Click to expand...
Click to collapse
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
This is the line you asked about:
BOARD_KERNEL_CMDLINE := console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 loop.max_part=7 androidboot.selinux=permissive
I've tried my build with your boot.img but it still bootloops.
115ek said:
Hey
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I've tried again and the last 4 lines of the build are:
2021-10-18 16:11:33 - ota_from_target_files.py - INFO : done.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Warning: could not find RADIO/filesmap in <zipfile.ZipFile object at 0x7f982df1bf50>.
Compressing system.new.dat with brotli
warning radio-update: no radio image in input target_files; not flashing radio
[100% 24/24] build bacon
Package Complete: out/target/product/crackling/lineage-18.1-20211018-UNOFFICIAL-crackling.zip
#### build completed successfully
Is this OK? I thought bacon was another phone (oneplus?)
Hey
115ek said:
The best way would be attaching some cables to get a console over UART. However, this requires some hardware knowledge and most likely some soldering. I haven't had a look into the crackling hardware yet.
Then you could use the android logcat command. Unfortunately adb has to work for that.
A third option could be "loggy", a simple script writing the logs to a defined location. Have a look here.
You could, but I'm not sure if that really helps.
What does this line looks like (exactly!) in your sources? Could you post it here?
I'd try to use a known to be working boot.img - you could extract one from my latest 18.1 upload. That way you could exclude some potential problems.
Click to expand...
Click to collapse
I get this , just bfore the build completes successfully. Do you know if this has anything to do with the problem.
99% 463/464] Package OTA: out/target/product/crackling/lineage_crackling-ota-eng.pet
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read VENDOR/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read PRODUCT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read SYSTEM_EXT/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/etc/build.prop
2021-10-19 18:02:26 - common.py - WARNING : Failed to read ODM/build.prop

[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1

Central project page
[EOL][SODP][ROM][AOSP][XZ2, XZ2C, XZ3] SonyAOSP 12.1 [Alpha]
The Sony Open Devices Project is always happy about volunteers (coding, testing, etc) :) Also mainlining your favorite snapdragon powered xperia device into the mainline kernel is possible and we will be glad to help you! Official site...
forum.xda-developers.com
09.02.2022
android-12.0.0_r28 (February security patchlevel)
OEMv1c support
Click to expand...
Click to collapse
14.02.2022
hotfix for the bootloop
Click to expand...
Click to collapse
30.03.2022
android-12.1.0_r1 (March security patchlevel)
Click to expand...
Click to collapse
MartinX3 said:
30.03.2022
Click to expand...
Click to collapse
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Carljaynp03 said:
a question why you don't upload photos of the user interface, and what options are available, I currently have the Xperia XZ2 Compact, and I'm thinking of changing the rom for this one based on Android 12.1
Click to expand...
Click to collapse
It's 90% aosp.
Please report any bug in the linked issue tracker.
MartinX3 said:
It's 90% aosp.
Please report any bug in the linked issue tracker.
Click to expand...
Click to collapse
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Carljaynp03 said:
any direct contact number for more information I am new in the world of custom roms, I want help, I can contribute with the work done please
Click to expand...
Click to collapse
Thank you, please follow the link in the first post.
There it is also in the first post.
12.04.2022
android-12.1.0_r3 (April security patchlevel)
Click to expand...
Click to collapse
Bug....the touch does not work and it seems to reboot intermittently
Mint rhfo said:
Bug....the touch does not work and it seems to reboot intermittently
Click to expand...
Click to collapse
Bug....report?
MartinX3 said:
Bug....report?
Click to expand...
Click to collapse
Yeah! It's Bug report!
Mint rhfo said:
Yeah! It's Bug report!
Click to expand...
Click to collapse
I don't see a valid bug report according to the instructions.
Or you claim that I'm god and know everything.
But maybe I'm god, who knows.
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
BigWoodFarmer said:
Hello,
Android Custom Rom noob here. Just picked up a XPERIA zx2 Compact and wanted to use this guide to flash a more current Android on the phone (came with Android10).
I followed some guides and was able to unlock my bootloader and enable USB Debugging. I used adb platform tools to boot the device in fastboot mode and flashed the files as described in the instructions.
Errors encountered:
fastboot flash oem _a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
fastboot: error: cannot load '_a': No such file or directory
I changed the command to: fastboot flash oem_a SW_binaries_for_Xperia_Android_12_4.19_v1c_tama.img
Sadly, the device reboots after a few seconds showing the sony logo. Reboots about three times and then says corrupted image, then shuts down. What am I doing wrong?
Thanks for your help guys!
Click to expand...
Click to collapse
Hey,
I'm sorry and fixed the type.
There was a wrong whitespace character in the manual.
It's `oem_a`, that's correct.
Did you flash everything and wiped the userdata before?
Because other XZ2C owners were able to post logs.
Also it is mandatory to run the latest stock firmware on both slots once before in the lifetime of your phone.
Hi,
Thank you for your fast reply. I flashed everything and wiped as described with "fastboot -w"
I am unsure what you mean by both slots, you mean Firmware and Software Content Erase? I used EMMA to flash: H8324 52.1.A.0.618 Customized_UK 1313-5469 R3C User-Live COM on the device.
Some other questions I had:
a) Do I need Magisk for root on the device?
b) can I use another Version the twrp 3.4.0.0.? If I install this to my recovery partition, I can't use it when booting since the screen seems frozen.
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
BigWoodFarmer said:
sry for asking some dumb questions in my last post. I was now able to install this Android 12 Version. I think the problem was, that i didn't wipe the device before the deployment.
Thanks again for all your work on this.
*EDIT*
Can you suggest a twrp version I should use? I cannot start 3.4-0-0 (2020-06-14_21-07-37) anymore using fastboot boot
**EDIT #2**
I received the following error: "there is an internal problem with your device, contact manufacturer". I will attach output of logcat -b all
Click to expand...
Click to collapse
Nice that you achieve to flash it.
The camera is currently not implemented because of the russian invasion in the ukraine.
Code:
04-12 19:02:48.363 0 0 I init : starting service 'vendor.camera-provider-2-4'...
04-12 19:02:48.451 3114 3114 I [email protected]: [email protected] legacy service is starting.
04-12 19:02:48.452 3114 3114 D ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.453 3114 3114 D hw-ProcessState: Binder ioctl to enable oneway spam detection failed: Invalid argument
04-12 19:02:48.452 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc44 returned -22
04-12 19:02:48.453 0 0 I binder : 3114:3114 ioctl 40046210 7ff5fbfc24 returned -22
04-12 19:02:48.489 3114 3114 E [email protected]: Could not load camera HAL module: -2 (No such file or directory)
04-12 19:02:48.489 3114 3114 E [email protected]_64: getProviderImpl: camera provider init failed!
04-12 19:02:48.490 3114 3114 D RefBase : RefBase: Explicit destruction, weak count = 0 (in 0xb400007a624ceaa0)
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::getCurrentInternal not linked, returning null
04-12 19:02:48.491 3114 3114 W RefBase : CallStack::logStackInternal not linked
04-12 19:02:48.492 3114 3114 E HidlServiceManagement: Could not find instance 'legacy/0' in library [email protected] Keeping library open.
04-12 19:02:48.493 3114 3114 E LegacySupport: Could not get passthrough implementation for [email protected]::ICameraProvider/legacy/0.
04-12 19:02:48.501 0 0 I init : Service 'vendor.camera-provider-2-4' (pid 3114) exited with status 1
04-12 19:02:48.501 0 0 I init : Sending signal 9 to service 'vendor.camera-provider-2-4' (pid 3114) process group...
04-12 19:02:48.501 0 0 I libprocessgroup: Successfully killed process cgroup uid 1047 pid 3114 in 0ms
04-12 19:02:48.504 0 0 E init : process with updatable components 'vendor.camera-provider-2-4' exited 4 times in 4 minutes
04-12 19:02:48.513 0 0 I init : processing action (sys.init.updatable_crashing=1) from (/system/etc/init/flags_health_check.rc:10)
04-12 19:02:48.514 0 0 I init : starting service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)'...
04-12 19:02:48.541 0 0 I init : SVC_EXEC service 'exec 29 (/system/bin/flags_health_check UPDATABLE_CRASHING)' pid 3115 (uid 1000 gid 1000+0 context default) started; waiting...
04-12 19:02:48.564 3115 3115 I flags_health_check: ServerConfigurableFlagsReset reset_mode value: 1
04-12 19:02:48.565 3115 3115 I flags_health_check: ServerConfigurableFlagsReset updatable crashing detected, resetting flags.
Please subscribe to
[Tama][XZ2C][AOSP12][4.19] Apollo camera provider init failed (every 5secs) · Issue #751 · sonyxperiadev/bug_tracker
Platform: Tama Device: XZ2C (apollo) Kernel version: 4.19.188-ge73c1a837c4f-dirty Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a (latest official Sony...
github.com
[Tama][4.19][AOSP12] Device reboots for no clear reason any time it is not idle · Issue #755 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: AOSP12 Software binaries version: 12_4.19_v1c_tama Previously working on n/a Description The device reboots after a few minutes o...
github.com
[TAMA][12][4.19] Bootloop · Issue #748 · sonyxperiadev/bug_tracker
Platform: Tama Device: Apollo Kernel version: 4.19 Android version: 12 Software binaries version: v1c Previously working on Stock Description Bootloop and no ADB logs available. The device was flas...
github.com
and firstly this will get fixed: https://github.com/sonyxperiadev/bug_tracker/issues/770
20.05.2022
android-12.1.0_r5 (May security patchlevel)
Click to expand...
Click to collapse
Because of problems with the ftp server the new release is on google drive.
Click to expand...
Click to collapse
Hello, what changes between this rom and the stock based roms ?

Categories

Resources