Hello everyone.
Please tell me what are the names and where are the system programs:
Map
Fingerprint
Nfc
Blis Westher
For example, the Bluetooth system application is located here:
# cd /system/app/Bluetooth
and
# cd /system/app/BluetoothMidiService
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
â settings â apps & notification â display the xx apps â 3 dot menu â show system process â âBLUETOOTHâ â advanced â âSCROLL TO THE BOTTOMâ â com.android.bluetooth
when not located in /system/app, they are often in /system/priv-app
⌠and
also allows a 
Search.
So if you search weather you are led to
foundation.e.blissweather.
To add to thisâŚThose who want to know what some of those obscure system apps are like pebble, squircle, circle ,seedvault, tall cutout, osuLogin, rounded rectangle, RubikâŚteardrop etc. Iâm not seeing any thing in this forum or the docs that cover these system procs. Would be nice to go to the bottom of the app where it lists the version and repository name and point to an explanation. They saw fit to show the system list of applications but not point to a definition.
Cheers, Luka
Hello. Thank you very much for your answer.
As for my example with BLUETOOTH or for example MAP (com.generalmagic.magicearth) it is clear, but how can I find the program that is responsible for the fingerprint?
And I do not want to just disable BLUETOOTH or NSF, I want to completely remove their systems!
How can I do this?
Addition to my question. Below is a list of system programs, where in the /e/OS wiki can I find such a list with an explanation for each program, for example:
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 Bluetooth is Bluetooth
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Stk the SIM card menu
etc.
============
/system/app # ls -l
total 120
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 AccountManager
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BasicDreams
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BlissIconPack
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 Bluetooth
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BluetoothMidiService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BookmarkProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CarrierDefaultApp
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CertInstaller
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CompanionDeviceManager
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 CtsShimPrebuilt
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 EasterEgg
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ExtShared
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 GsfProxy
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 HTMLViewer
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 KeyChain
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 LiveWallpapersPicker
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Message
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 OpenKeychain
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 PacProcessor
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 PlatformCaptivePortalLogin
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 PrintRecommendationService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Profiles
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SecureElement
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SimAppDialog
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Stk
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Talkback
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Traceur
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 WallpaperBackup
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 WebCalendarManager
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 eDrive
==================================================
/system/priv-app # ls -l
total 200
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 AdvancedPrivacy
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BackupRestoreConfirmation
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BlissLauncher
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 BlockedNumberProvider
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 BuiltInPrintService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CalendarProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CallLogBackup
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 CellBroadcastLegacyApp
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ContactsProvider
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 CtsShimPrivPrebuilt
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DocumentsUI
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DownloadProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DownloadProviderUi
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DroidGuard
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DynamicSystemInstallationService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ExternalStorageProvider
drwxr-xr-x 4 root root 4096 2009-01-01 03:00 FMRadio
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 FakeStore
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 FlipFlap
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 FusedLocation
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 GmsCore
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 InProcessNetworkStack
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 InputDevices
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 LineageParts
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 LineageSettingsProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 LocalTransport
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ManagedProvisioning
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 MediaProviderLegacy
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 MmsService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 MtpService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 NetworkPermissionConfig
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ONS
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 PackageInstaller
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 PlatformNetworkPermissionConfig
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ProxyHandler
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SamsungDoze
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Seedvault
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SettingsProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SharedStorageBackup
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Shell
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SoundPicker
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SplitInstallService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 StatementService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 TeleService
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Telecom
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 TelephonyProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 TimeKeep
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Updater
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 UserDictionaryProvider
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 VpnDialogs
=====================================
/product/app # ls -l
total 40
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 Backgrounds
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 BrowserWebView
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 DeskClock
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Etar
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 ExactCalculator
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 LineageThemesStub
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 LocalContactsBackup
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 ModuleMetadata
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 PhotoTable
drwxr-xr-x 2 root root 4096 2009-01-01 03:00 TrichromeLibrary
========================================
/product/priv-app # ls -l
total 16
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Contacts
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 Dialer
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 OneTimeInitializer
drwxr-xr-x 3 root root 4096 2009-01-01 03:00 SettingsIntelligence
Short answer is âYou canâtâ, at least if you expect the device to continue functioning.
Longer answer is that to remove them, you would need to make a build that does not include the components you donât want. Even then, it may be that you cannot even build without some of those components: if some of the core software components rely on the components you donât like, then they will not build without them. Only way to find out is to try.
The fingerprint sensor is implemented in very low-level software, which will interface with whichever system component handles authentication. Same will be true for the software which runs Bluetooth, or NSF (whatever that is - did you mean NFC, in which case the same applies). You canât just remove such low-level software components from a built ROM
Thank you for your answer.
Okay, the important part of my question, what do they mean and where can I find the name of system programs in the wiki, we will skip now.
You wrote that if I, for example, delete BLUETOOTH or NFC (sorry, I was in a hurry and wrote it incorrectly), then NFC and BLUETOOTH will work?
# mount -o rw,remount /
# rm -R /system/app/Bluetooth
# rm -R /system/app/BluetoothMidiService
How can you prove this?
No. I wrote that it you remove the low-level software components that make these features work there is a good chance that your phone will not work at all.
You said
To âremove their systemsâ you would have to do a lot more that delete the two apps you named. Disabling those apps would probably have exactly the same effect as rm -R-ing them: it certainly would not 'remove their systems` (whatever that means)
How do you know this? Have you tried to do what I wrote or are you reasoning theoretically (without practice) and then launch NFC or BLUETOOTH.
I donât know what you call a low-level solution, you wrote several times but didnât explain what you mean, for me a low-level solution is physical removal (disconnection from the NFC board)
No I have not tried it because I want my phones to work 
I am âreasoningâ on the basis of my knowledge and experience as a software engineer and working with Android custom ROMs.
If I wanted to completely âremove their systemsâ (and I still donât know what that means), I would do something like the following, in an adb root shell with system mounted and writable:
cd /
find . -iname "*bluetooth*" -delete
find . -iname "nfc*" -delete
And - on the outside chance that succeeded, I wouldnât expect my phone to function at all, until I reflash it with a working ROM. But if you are working from a level of competence that allows you to physically remove hardware, then I salute you, and bow to your superior knowledge, experience, and expertise 
Goodbye and good luck!
I understand your humor, but I will tell you that you do not need to have much competence to look at the datasheet of the phone, open the phone cover and remove the NFC plate and delete the files that I wrote about.
And to raise your information level as an engineer, I want to tell you that BLUETOOTH is considered the most vulnerable protocol, read about: BlueSmacking, Bluebugging, BlueJacking, BlueSnarfing, Bluesniping, KNOB
Hardware kill switches instead?
There might be reasons why people donât really approach this in the way you want to.
There are reasons why billions of users around the world use malicious WhatsApp, do you know the answer why?)) There is a free XPMM with the same functions and you can install it on your server, Richard Stallman has already talked about all this many times.
Watch his video.
Thatâs why many use BLUETOOTH!
As for the physical hardware switch (not software), this is a good solution in my opinion.
Some users used my main question for their own purposes, until I received an answer, where on the /e/OS website there is information wiki purpose of system programs the list of which I wrote above.