Good idea. I don’t know why I didn’t think of that.
2 Likes
@Samtee-1 Can i ask you how far did you get with Android Auto? Works fine? Google app blocked? Or does it show? Just webview keeps you from using the app?
Tried Using Android Auto and i came to conclusion that the google app needs to opened. Or it will close on you the AA. Then found a whole discussion about this here and adding it under the accessibility function. A nice write up would be helful for others so they dont have to search through all of this.
Also an index in a stickied post would be cool. For example under flip phones, a post with simple keywords and a link to that topic. Whether it be Transfer SMS and Call logs, (and a clickable link), Transfer and backup Notes… and any other guides or useful info to reference in a single post. Basically what i would call a wiki so users dont have to sift through all the posts in select topics.
So you can block not hide Google app but only do that once you connect it to the car and allowed all the permissions but if that doesn’t work you can block webview and that should work fine too.
It worked for me.
Somehow the f30 managed to do all that without installing, blocking or disabling Google. Android auto works well wirelessly there. If anybody can reverse engineer their method it will be a great help to society.
Maybe they use there own spoofed Google app and maps
Which you can get from a magisk moudel
If course they do. Just need to get it via a untouched old f30 without the updates.
Okay I’ll have to play around, thanks.
The weird part is as long as you had it working when it was connected to the car it will continue to work, but as soon as you hide the Google app and disconnect the wire it will stop working. What I realized is it won’t reconnect properly once you hide the Google app.
But I’ll try to block the app and see how that goes. I guess it will show as an app on the device but won’t be clickable.
With Google Play Store I’m assuming everyone here has to un-hide it, update the few apps and rehide it should you want the apps to be up to date?
Correct.
1 Like
Version 1.19
When I run the set device owner command, it says
Exception occurred while executing 'set-device-owner':
java.lang.IllegalStateException: Not allowed to set the device owner because there are already some accounts on the device.
When I run dumpsys device_policy it says:
Current Device Policy Manager state:
Immutable state:
mHasFeature=true
mIsWatch=false
mIsAutomotive=false
mHasTelephonyFeature=true
mSafetyChecker=null
Enabled Device Admins (User 0, provisioningState: 0):
com.oss.egate/.a:
uid=10375
testOnlyAdmin=false
policies:
wipe-data
reset-password
limit-password
watch-login
force-lock
expire-password
encrypted-storage
disable-camera
passwordQuality=0x0
minimumPasswordLength=0
passwordHistoryLength=0
minimumPasswordUpperCase=0
minimumPasswordLowerCase=0
minimumPasswordLetters=1
minimumPasswordNumeric=1
minimumPasswordSymbols=1
minimumPasswordNonLetter=0
maximumTimeToUnlock=0
strongAuthUnlockTimeout=0
maximumFailedPasswordsForWipe=0
specifiesGlobalProxy=false
passwordExpirationTimeout=0
passwordExpirationDate=0
encryptionRequested=false
disableCamera=false
disableCallerId=false
disableContactsSearch=false
disableBluetoothContactSharing=true
disableScreenCapture=false
requireAutoTime=false
forceEphemeralUsers=false
isNetworkLoggingEnabled=false
disabledKeyguardFeatures=0
crossProfileWidgetProviders=null
organizationColor=-16746133
userRestrictions:
null
defaultEnabledRestrictionsAlreadySet={}
isParent=false
mCrossProfileCalendarPackages=[]
mCrossProfilePackages=[]
mSuspendPersonalApps=false
mProfileMaximumTimeOffMillis=0
mProfileOffDeadline=0
mAlwaysOnVpnPackage=null
mAlwaysOnVpnLockdown=false
mPreferentialNetworkServiceEnabled=false
mCommonCriteriaMode=false
mPasswordComplexity=0
mNearbyNotificationStreamingPolicy=3
mNearbyAppStreamingPolicy=3
mAdminCanGrantSensorsPermissions=false
mUsbDataSignaling=true
mWifiMinimumSecurityLevel=0
mPreferentialNetworkServiceConfigs:
networkId=0
isEnabled=false
allowFallbackToDefaultConnection=true
includedUids=[I@e03d1fd
excludedUids=[I@849aef2
Removing Device Admins (User 0): [ComponentInfo{com.oss.egate/com.oss.egate.a}]
mPasswordOwner=-1
mPasswordTokenHandle=0
mAppsSuspended=false
mUserSetupComplete=true
mAffiliationIds={}
mNewUserDisclaimer=null
... and more
When I open the eGate app, everything that needs device owner is grayed out.
I tried removing and re-setting the device owner, but I still get the same issue.
What is going on?
1 Like
If you have gmail, whatsapp, or other accounts on the device, android won’t allow setting the device owner.
1 Like
I checked Gmail, it is logged out
I dont have WhatsApp
1 Like
Is there a way to check what account is causing it? I thought dumpsys device_policy would show but I guess not…
I also tried
adb shell dpm list-owners
but it returned
no owners
What else can be done?
1 Like
You can try to run adb shell pm suspend com.appname that is a bit a better block as it doesn’t show the google notifications and it shouldn’t make a problem for Android auto
Will it cause the app to disappear?
What if going to app settings and clearing data and cache would that bring it back to life?
I guess i can give that a shot and see what happens. Seems like your saying the google app even when blocked from running will still work but would display notifications? While your method not?
Had the same issue.
But removed every account from the device. Not a single account was on, then ran this command …
What device you trying to set device admin on?
Here’s another but he was trying on a classic, which now has its own apk for the egate filter.
Eventually I want eGate to display a list of accounts that need to be removed first, as Android does provide the necessary APIs for that.
1 Like