Here we go: weird package with redundant name found on running on my device.

Vomitorius

Quantum browse all posts, they comment in most of them

Quantum

Vomitorius The devs only get involved if its a serious problem(probably relayed from the mods). The mods do check most posts, but not all. If its that big of a problem tag one of the mods then

fid03

Vomitorius browse all posts, they comment in most of them

No, they literally do not do that, which you can see from opening their profile page. Not sure what you're insinuating by saying you're worried about them not posting in this thread.

aurocha

I haven't checked, but everytime I do a new install of GOS and Google Play Services, at some point, the Play Store tries to install a package called "Device Configuration" that pulls other Google packages normally installed when you run the stock Pixel Android, or, as some call it, PixelOS.

I usually deny the installation of that app and deny the auto install of the apps the Play Store pulls.

Can this be one of the apps that's automatically installed after installing and updating Google Play Services?

Cheers,

tempproc

aurocha I don't have Google Play Services installed that I know of

fid03

tempproc especially since it's problematic (uses user info for music music recognition, live caption and smart suggestions, none of which that I activated or want).

How are you deducing that the app does that?

fid03

Could someone who says they have this app on their device please provide a screenshot of its app entry, so that we're 100% sure we're talking about the same app with the exact same name?

Probably9857

fid03

Looks to me like it came with QPR2.

As a P7a user, I was on QPR1 yesterday, and did not have that package. After updating today, now I have it.

OP has the correct package name: com.google.android....

Googling suggests something to do with lockscreen widgets.

BTW, the project did comment on it in this other thread:

GrapheneOS It does not connect to the network or run any code.

Probably9857

Sorry...I was confusing questions about two completely different packages. (But probably with similar answers.) Apologies for adding to the confusion.

Mods may delete both of my posts.

Novalissoide

Probably9857 to me like it came with QPR2.

Installation in my sample/example dates back to July 2025, the date I installed GrapheneOS, and it hasn't received update after that.

Novalissoide

both of these;

com.android.ondevicepersonalization.services
18:6C:57:F1:12:C4:19:0C:8E:48:2B:35:BA:11:EB:99:86:67:31:17:4F:DD:32:39:A5:73:44:46:A9:B5:83:67
(which is installed on my p6a)

and

com.google.android.ondevicepersonalization.services
8C:84:D2:C0:C5:96:83:FB:0B:9B:DA:31:A1:59:0E:A1:4F:8E:91:5F:BB:33:31:04:8D:2D:69:68:A8:F6:F1:82
(which i took from apkpure)

both are expressed, depending on context as:
android.ondevicepersonalization.services

The first is signed by GrapheneOS, the other by Google Inc. California, US

They differ a tiny bit, but seems mostly identical. Right now, I'm not at desk and can't compare them in detail.

fid03

Likely installed by some Google app then. Can someone who has the exact package name given by the OP open the app entry for it, scroll down and look for the text "Installed by"?

No one has confirmed as far as I can see that they are seeing the exact (including "google") package name that the OP provided: com.google.android.ondevicepersonalization.services.OnDevicePersonalizationApplication

tempproc Double-check that you didn't misspell the package name?

Novalissoide

fid03 Big Holidays might have squelched their immediate angst of the intruding file, we don't know.

Vincent96

fid03 There is no option to see what installed this specific package. It's also listed as a system app.

GrapheneOS

tempproc com.android.ondevicepersonalization.services is a standard Android Open Source Project component which is part of GrapheneOS. If that's not present then you're not using GrapheneOS. The com.google prefixed name is used by the code internally and then there are 2 package names for the app itself with and without google based on whether it's the AOSP variant or their Google Mobile Services variant. This is the same approach as many other components. There's nothing special about this case.

Vomitorius Repetitive posts with baseless claims of compromise and fearmongering about standard Android Open Source Project system components don't need a response from the project every time. There are already plenty of threads about it. We'll just make it officially against the rules.

fid03 External package name and internal package name don't need to match. The external name is often set to com.android for AOSP by default and overridden to com.google.android for Google Mobile Services variants. The internal code can be either of those and it doesn't need to match.

graphny

Model: Pixel 7.
BuildNo: 2025121701.
Google Play Store: Installed.
I can't find it too. Link1 Link2 Link3

fid03

Vincent96 There is no option to see what installed this specific package. It's also listed as a system app.

Ok. The package you're seeing, does it have this exact name (including "google") "com.google.android.ondevicepersonalization.services.OnDevicePersonalizationApplication" ?

Vincent96

fid03 The name is com.android.ondevicepersonalization.services.OnDevicePersonalizationApplication

fid03

Vincent96 The name is com.android.ondevicepersonalization.services.OnDevicePersonalizationApplication

Thank you for confirming. Then it's not the package name that OP provided.

tempproc You're asking what this package is, yet already claiming with confidence what it does. There's no evidence in this thread so far that it does what you say it does, only loose claims that cause people to be worried about something that no one has provided proof that is preinstalled on a GrapheneOS device yet alone proof that it's problematic. Asking you to please provide a screenshot of the app entry you're seeing.

marq2

https://source.android.com/docs/core/ota/modular-system/ondevicepersonalization

tempproc

fid03 I cannot edit OP but this is exactly the name: com.android.ondevicepersonalization.services.OnDevicePersonalizationApplication

tempproc

nologo I do not remember having gone through all the way in enabling those authorization for this app, but this could be the culprit. I'm going to blacklist F-Droid seeing as it doesn't seem to have any auditing of the apps they host even if they're popular downloads

« Previous Page Next Page »