I have a Reliance LYF mobile phone and want to enable the developer mode. I looked for all options in the settings but haven't found anything to enable developer mode. Is the developer mode option available on it?

In *Developer options*, there is a setting called "Always allow Wi-Fi roam scans" with the description: > **Always allow Wi-Fi roam scans** > > Allow/disallow Wi-Fi roam scans based on the amount of data traffic present at the interface The description leads me to guess it might be useful when you are on the edge of the WiFi coverage zone, switching to another WiFi may be faster. Googling threw up results confirming my guess on posts like [this](https://supportforums.cisco.com/discussion/12543176/workaround-android-devices-do-not-roam-wifi) (a few more on similar lines). However, would request more explanation, since this is not encountered commonly as a suggestion to counter WiFi drops. **Is it of any use for end-users to activate it?**

I recently bought an Intenso microSDXC UHS-I Premium card, formatted it as internal storage, and the content has been moved without any errors. But after that, the phone started having several issues: - Most photos, videos, music, and recorded audio files are missing. - Some apps—like CamScanner, Foxit PDF Reader, and the camera—don’t work. - WhatsApp media (voices, images, videos) can’t be downloaded or saved. - App updates can’t be installed. - Storage shows a negative value (see attached photo). I’ve tried common fixes online and contacted the manufacturers, but nothing has worked. I also couldn’t find an option to reformat or separate the internal storage from the SD card. What would be the best next step? Should I try reinserting the SD card and choosing "forget" option, enable “Force allow apps on external” in Developer Options, or is there a better solution to recover the files and resolve the storage issues? - Device Name: Redmi Note 9 Pro - MIUI version: MIUI Global 12.0.3 Stable 12.0.3.0(QJZMIXM) - Android version: 10 QKQ1.191215.002

I have a Huawei phone. When I searched the "Forced RTL Layout" option, it shows up. When I click on it, it leads me to the top of Developer Options. But nowhere on the list do I see the Force RTL option. This is very frustrating and I can't seem to find anyone talking about it online. My old phone was also a Huawei and the same problem happens. Both my parents have Huawei phones and neither of them has the option either. How can I get the Force RTL option out and apply it?

My son has a Motorola Moto G73 5G (XT2237-2), always used it normally without trying to root it. So the bootloader has not been unlocked. It is stuck in a boot loop. I can boot into fastboot mode (by pressing power and volume down) and then into recovery, but I am not allowed to change anything. While the phone was still working properly we should of course have enabled Developer Options, Allow USB Debugging and Allow OEM Unlocking, but it is too late for those. Is there another way to get to the data before doing a reset? - If side-loading the firmware in recovery mode is possible, I guess that would wipe the data, but mounting in recovery mode (to save any content) does not seem to work. - I tried accessing the phone with fastboot and adb (from the linux prompt) and the phone recorded receiving the commands fastboot oem unlock and fastboot flashing unlock, but then that was not allowed because we had not allowed unlocking from the Developer Options menu.

My cell phone is a Samsung Galaxy Pocket 2 (SM-G110B/DS) running Android 4.4 KitKat. I found the developer options, and "by mistake", I selected one of the overlays. The problem is that the overlay has a bigger resolution than what my screen supports, and it doesn't let me touch the screen (Overlay #1 1280x720). I have turned the phone off and on again and it didn't work, I took off the battery, pinched it, and tapped on it several times... nothing changed, but that overlay is still there and doesn't let me touch the screen. How can I turn this overlay off?

I am trying to create some apps on my xiaomi smartphone (MIUI 8), but when I try to run an app, the error INSTALLATION_CANCELED_BY_USER appears. I found that the problem is that I must enable the "Install via USB" option from developer settings. When I try to do so, I get a screen that says I have to login/signup with an MI account in order to enable this option, which is something I am not willing to do. So, I have 3 questions: - Why did they make it neccessary to provide an account for enabling an option like this? - Is there any way I can bypass the MI login screen and enable the option? - The reason I don't want to connect my phone to an MI account is that I am concerned about personal data being uploaded. Is it a logical concern?

This has been asked many times: how to block the installation of applications from an APK file, how to block the package installer, etc. The common answer is that it is impossible, because if you disable the package installer, the device will not boot and will remain stuck in a boot loop. Fixing the boot loop is very simple, but it does not matter at the moment. I found a way to block an activity of the package installer so that the device could start normally, pm disable com.android.packageinstaller/.InstallInsalling It works great, blocks application installation, and the device works without any issues. I know it is still possible to bypass it and install apps through ADB, but it still helped me a lot. Now, I'm looking for the name of the activity that will disable the developer options. Maybe block the "About phone", or the clicks on "Build Number", or only the "USB debugging" options - through pm disable activity, or maybe through permissions. Does anyone have an idea or can help me find the names of the activity? The activity name of the developer options is com.android.settings/com.android.settings.SubSettings, but it's related to almost every part of the settings. Is there anything more specific?

When I try to open developer options, the settings app just crashes. My device is a Nokia 3 TA-1032, running Android 9 (firmware version 00WW_5_230). Here is the log:

> FATAL EXCEPTION: main
Process: com.android.settings, PID: 5147
java.lang.RuntimeException: Unable to resume activity {com.android.settings/com.android.settings.SubSettings}: java.lang.RuntimeException: failed to set system property
	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3815)
	at android.app.ActivityThread.handleResumeActivity(ActivityThread.java:3847)
	at android.app.servertransaction.ResumeActivityItem.execute(ResumeActivityItem.java:51)
	at android.app.servertransaction.TransactionExecutor.executeLifecycleState(TransactionExecutor.java:145)
	at android.app.servertransaction.TransactionExecutor.execute(TransactionExecutor.java:70)
	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1836)
	at android.os.Handler.dispatchMessage(Handler.java:106)
	at android.os.Looper.loop(Looper.java:193)
	at android.app.ActivityThread.main(ActivityThread.java:6702)
	at java.lang.reflect.Method.invoke(Native Method)
	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:911)
Caused by: java.lang.RuntimeException: failed to set system property
	at android.os.SystemProperties.native_set(Native Method)
	at android.os.SystemProperties.set(SystemProperties.java:183)
	at com.android.settingslib.development.AbstractLogpersistPreferenceController.updateLogpersistValues(AbstractLogpersistPreferenceController.java:178)
	at com.android.settings.development.LogPersistPreferenceController.updateState(LogPersistPreferenceController.java:56)
	at com.android.settings.dashboard.DashboardFragment.updatePreferenceStates(DashboardFragment.java:317)
	at com.android.settings.dashboard.DashboardFragment.onResume(DashboardFragment.java:169)
	at com.android.settings.dashboard.RestrictedDashboardFragment.onResume(RestrictedDashboardFragment.java:137)
	at android.app.Fragment.performResume(Fragment.java:2568)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1341)
	at android.app.FragmentManagerImpl.moveFragmentToExpectedState(FragmentManager.java:1576)
	at android.app.FragmentManagerImpl.moveToState(FragmentManager.java:1637)
	at android.app.FragmentManagerImpl.dispatchMoveToState(FragmentManager.java:3046)
	at android.app.FragmentManagerImpl.dispatchResume(FragmentManager.java:3008)
	at android.app.FragmentController.dispatchResume(FragmentController.java:204)
	at android.app.Activity.performResume(Activity.java:7314)
	at android.app.ActivityThread.performResumeActivity(ActivityThread.java:3807)
	... 11 more

Can someone let me know why this is happening? I think it's because I removed the Chinese "evenwell" apps that came with the phone (probably spyware).Thanks in advance for your reply.

I have an Android device that's used for mobile testing. This device has cell connectivity and is separately connected to an ethernet cable (used for ADB). How can I configure the Android device so that mobile data is used for internet connectivity and NOT the ethernet connection? adb shell ifconfig lists the active network interfaces:

eth0      Link encap:UNSPEC    Driver r8152
          inet addr:192.168.1.194  Bcast:192.168.1.255  Mask:255.255.255.0 
          inet6 addr: fe80::acc9:34c6:24a1:f137/64 Scope: Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2141 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:792 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:559025 TX bytes:84086 

rmnet_data0 Link encap:UNSPEC  
          inet addr:10.76.204.250  Mask:255.255.255.252 
          inet6 addr: 2600:380:c034:e7ed:b901:d247:67b4:d598/64 Scope: Global
          UP RUNNING  MTU:1430  Metric:1
          RX packets:8811 errors:0 dropped:0 overruns:0 frame:0 
          TX packets:6886 errors:0 dropped:0 overruns:0 carrier:0 
          collisions:0 txqueuelen:1000 
          RX bytes:7386188 TX bytes:1569087 

...

Looking to set rmnet_data0 (mobile data) to be the network interface used for internet instead of eth0. Device can be rooted if needed.

I'm using the Island application for the sake of isolating and cloning certain applications on my Samsung running One UI 6.1. Whenever I try to unlock developer options, I get the following error: > Action not allowed > > To disable this restriction, please refer to corresponding setting in Island. The error tells me that I should see the corresponding option in the Island application itself, but there is no any kind of option to unlock developer options. I've been trying to contact numerous people considering the problem I'm having. The developer is not answering. Some people are telling me that the work profile shouldn't allow developer options anyway. What do you think could be a solution?

One of my phones has had the developer options enabled and I don’t remember doing it. It’s not rooted and does not have bootloader enabled. I’m wondering if this happened when someone else had physical possession of the phone. Is it possible to check this via adb, perhaps it’s recorded in a file or the modification date of a file that can be seen via adb shell without root permission? Or perhaps another method? Android 14 / Pixel 7 Pro

I have a Pixel 2 XL that I MUST keep on Android 10 for various reasons. *(Yes, I am aware of the implications of doing this. This is a device that I use for development tasks, I don't go to random websites on it, I don't install unknown apps, I never use it away from my trusted home WiFi network, etc.)* However Google seems hellbent on making me upgrade. Every few days I get a popup message (shown below) asking me to "restart now to finish the update." **I get this popup even though I have "automatic system updates" turned OFF in Developer Settings, and even though I have Google Play Services notifications turned OFF.** Is there any way to stop this message from appearing?

I have a Samsung Galaxy A12. In the Developer options, OEM unlocking cannot be found. I have tried various guides and they all boil down to change the date and reboot the system. I have tried this multiple times. Do I really need to wait 7 days to get access to OEM unlock? Is there a way to change this setting via the Android shell or ADB?

Can developer options and Bug Reports be used to spy on a person's phone use? For example by a spouse or parent? 

The phone is a brand new phone that was provided by my carrier in Canada (Telus). The phone is carrier unlocked. I verified this by putting a non Telus sim into it and making a call. Once the "Developer Options" menu is enabled, the "OEM unlock" is greyed out, I tried the following in all kinds of order: - factory reset... many times - all software updates - connection to the internet (via wifi) - Using android recovery I performed a factory data reset in the erase Wipe data/factory reset option - enabled "USB debugging" in developer options - I asked chat GPT and tried all the options that were technically possible. When I look on the "Fastboot Mode" screen, the device state is locked. I called my phone provider, and the technical support is trying to help, but I don't see that working out. Does anyone know of a secret menu that allows the enabling of this setting? What can I do?

So, I was bored and I decided to check some developer options to see what they could do. I found this option called 'smallest width', at first, I set it from 392 to 100 and it automatically set itself to two hundred something, I believe. So, I did the same thing, but this time, I set it to 1000, thinking that it would automatically set itself to the maximum value possible... But it didn't. Right after pressing 'Ok', my screen became so small and a message popped up saying "System is not responding", then my phone restarted to recovery. Unlike many people who were facing this problem on the internet, my phone's bootloader is unlocked, I have TWRP recovery installed, my phone is rooted and I had USB debugging on. I rebooted to bootloader and tried adb devices, but my phone wasn't there. After that, I booted to TWRP, clicked Mount, checked all boxes (I couldn't check storage), and clicked Mount USB Storage. This time, my phone showed up on the list. Check the image below. I don't know if it's okay that it's saying recovery instead of device, but I ran adb shell wm density reset and it didn't work. The same with adb shell wm size reset. As you can see in the image, there was no error, but the phone still didn't want to boot. After that, I tried to check my current screen size and density using adb shell wm size and adb shell wm density, but there was no response. I also checked the build.prop file in /system and found this line persist.miui.density_v2=440, I changed it to 220, but nothing happened. Now my question is, why is there no response when I run adb shell wm size/density? It doesn't work in the TWRP terminal as well. Is this command supposed to be in the /sbin directory? Because I couldn't find it there. How can I add it if it is not there? And lastly, if you can suggest any other way to fix my phone that would help me a lot.

Here is what I am trying to achieve, I'm trying to derive an adb shell command that allows me to toggle these switches inside the settings app programmatically. I've used dumpsys to figure out these component names (at least that's what I believe). fuxi:/ # dumpsys package com.android.settings Service Resolver Table: Non-Data Actions: android.service.quicksettings.action.QS_TILE: 47bc38b com.android.settings/.development.qstile.DevelopmentTiles$ShowLayout filter 6c8cc68 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 236e881 com.android.settings/.development.qstile.DevelopmentTiles$GPUProfiling filter fe7d26 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 7e10d67 com.android.settings/.development.qstile.DevelopmentTiles$ForceRTL filter 1924714 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" a688bbd com.android.settings/.development.qstile.DevelopmentTiles$AnimationSpeed filter a4545b2 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 4671903 com.android.settings/.development.qstile.DevelopmentTiles$WinscopeTrace filter 4d6c080 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 11726b9 com.android.settings/.development.qstile.DevelopmentTiles$SensorsOff filter be0afe permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 6b8425f com.android.settings/.development.qstile.DevelopmentTiles$WirelessDebugging filter 52764ac permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" b7a7575 com.android.settings/.development.qstile.DevelopmentTiles$ShowTaps filter 6bd90a permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 1c8a57b com.android.settings/.development.qstile.DevelopmentTiles$DesktopMode filter cfc1f98 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" 89f3f1 com.android.settings/.development.qstile.DevelopmentTiles$ShowRefreshRate filter 767bd6 permission android.permission.BIND_QUICK_SETTINGS_TILE Action: "android.service.quicksettings.action.QS_TILE" Packages: Package [com.android.settings] (225ab18): appId=1000 sharedUser=SharedUserSetting{e7ec628 android.uid.system/1000} pkg=Package{c61500b com.android.settings} codePath=/system_ext/priv-app/Settings resourcePath=/system_ext/priv-app/Settings legacyNativeLibraryDir=/system_ext/priv-app/Settings/lib extractNativeLibs=true primaryCpuAbi=arm64-v8a secondaryCpuAbi=null cpuAbiOverride=null versionCode=34 minSdk=34 targetSdk=34 minExtensionVersions=[] versionName=14 usesNonSdkApi=true splits=[base] apkSigningVersion=3 flags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP KILL_AFTER_RESTORE ] privateFlags=[ PRIVATE_FLAG_ACTIVITIES_RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION ALLOW_AUDIO_PLAYBACK_CAPTURE DEFAULT_TO_DEVICE_PROTECTED_STORAGE DIRECT_BOOT_AWARE PARTIALLY_DIRECT_BOOT_AWARE PRIVILEGED SYSTEM_EXT PRIVATE_FLAG_ALLOW_NATIVE_HEAP_POINTER_TAGGING ] forceQueryable=false queriesIntents=[Intent { act=com.android.setupwizard.action.PARTNER_CUSTOMIZATION }] dataDir=/data/user_de/0/com.android.settings supportsScreens=[small, medium, large, xlarge, resizeable, anyDensity] usesLibraries: org.apache.http.legacy com.qti.extphone.extphonelib usesOptionalLibraries: androidx.window.extensions androidx.window.sidecar usesLibraryFiles: /system/framework/org.apache.http.legacy.jar /system_ext/framework/extphonelib.jar timeStamp=2009-01-01 08:00:00 lastUpdateTime=2009-01-01 08:00:00 installerPackageName=null installerPackageUid=-1 initiatingPackageName=null originatingPackageName=null packageSource=0 appMetadataFilePath=null signatures=PackageSignatures{f549ee8 version:3, signatures:[92d864b3], past signatures:[]} installPermissionsFixed=false pkgFlags=[ SYSTEM HAS_CODE ALLOW_CLEAR_USER_DATA ALLOW_BACKUP KILL_AFTER_RESTORE ] privatePkgFlags=[ PRIVATE_FLAG_ACTIVITIES_RESIZE_MODE_RESIZEABLE_VIA_SDK_VERSION ALLOW_AUDIO_PLAYBACK_CAPTURE DEFAULT_TO_DEVICE_PROTECTED_STORAGE DIRECT_BOOT_AWARE PARTIALLY_DIRECT_BOOT_AWARE PRIVILEGED SYSTEM_EXT PRIVATE_FLAG_ALLOW_NATIVE_HEAP_POINTER_TAGGING ] apexModuleName=null User 0: ceDataInode=5887 installed=true hidden=false suspended=false distractionFlags=0 stopped=false notLaunched=false enabled=0 instant=false virtual=false installReason=0 firstInstallTime=2009-01-01 08:00:00 uninstallReason=0 disabledComponents: com.android.settings.Settings$LanguageAndInputSettingsActivity com.android.settings.SetupFingerprintSuggestionActivity com.android.settings.development.qstile.DevelopmentTiles$AnimationSpeed com.android.settings.development.qstile.DevelopmentTiles$WinscopeTrace com.android.settings.development.qstile.DevelopmentTiles$ShowLayout com.android.settings.development.qstile.DevelopmentTiles$GPUProfiling com.android.settings.development.qstile.DevelopmentTiles$ShowTaps com.android.settings.homepage.DeepLinkHomepageActivity com.android.settings.development.qstile.DevelopmentTiles$ShowRefreshRate com.android.settings.development.qstile.DevelopmentTiles$SensorsOff com.android.settings.development.qstile.DevelopmentTiles$ForceRTL com.android.settings.search.SearchStateReceiver enabledComponents: com.android.settings.development.qstile.DevelopmentTiles$DesktopMode com.android.settings.development.qstile.DevelopmentTiles$WirelessDebugging com.android.settings.Settings$ConnectedDeviceDashboardActivity com.android.settings.Settings$PowerUsageSummaryActivity com.android.settings.Settings$WifiDisplaySettingsActivity com.android.settings.Settings$BluetoothSettingsActivity com.android.settings.Settings$DevelopmentSettingsDashboardActivity com.android.settings.SetupRedactionInterstitial com.android.settings.Settings$WifiSettingsActivity com.android.settings.WebViewImplementation com.android.settings.Settings$UserSettingsActivity com.android.settings.Settings$DataUsageSummaryActivity com.android.settings.Settings$LanguageSettingsActivity I am assuming by enabling this components via pm enable com.android.settings/.development.qstile.DevelopmentTiles$ShowLayout should get the job done. Unfortunately, it gives me this error. fuxi:/ $ su fuxi:/ # pm enable com.android.settings/.development.qstile.DevelopmentTiles$ShowLayout Exception occurred while executing 'enable': java.lang.IllegalArgumentException: Component class com.android.settings.development.qstile.DevelopmentTiles does not exist in com.android.settings at com.android.server.pm.PackageManagerService.setEnabledSettings(PackageManagerService.java:4035) at com.android.server.pm.PackageManagerService.-$$Nest$msetEnabledSettings(PackageManagerService.java:0) at com.android.server.pm.PackageManagerService$IPackageManagerImpl.setComponentEnabledSetting(PackageManagerService.java:5962) at com.android.server.pm.PackageManagerShellCommand.runSetEnabledSetting(PackageManagerShellCommand.java:2489) at com.android.server.pm.PackageManagerShellCommand.onCommand(PackageManagerShellCommand.java:269) at com.android.modules.utils.BasicShellCommandHandler.exec(BasicShellCommandHandler.java:97) at android.os.ShellCommand.exec(ShellCommand.java:38) at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onShellCommand(PackageManagerService.java:6474) at android.os.Binder.shellCommand(Binder.java:1097) at android.os.Binder.onTransact(Binder.java:914) at android.content.pm.IPackageManager$Stub.onTransact(IPackageManager.java:4403) at com.android.server.pm.PackageManagerService$IPackageManagerImpl.onTransact(PackageManagerService.java:6458) at android.os.Binder.execTransactInternal(Binder.java:1363) at android.os.Binder.execTransact(Binder.java:1304) Is it permission issue? I have root access for shell. For reference, this is the source code for the relevant part. Yes, I'm trying to do this on a custom rom https://github.com/AOSPA/android_packages_apps_Settings/blob/uvite/src/com/android/settings/development/qstile/DevelopmentTilePreferenceController.java

I have a Samsung Galaxy S23 Ultra running Android 14, which I am almost certain has malware/a rootkit on it. I'd like to take a forensic image of the device. In developer mode, the 'USB debugging' mode is shaded in and set to off. I don't know how to unshade it and set it to enabled. How might this have happened and what can I do to get an image off of it?

I use my device with a different Smallest Width setting (600 instead of default 400 something). it makes everything better for me EXCEPT it totally ruins the scaling of one or two apps. Is there any way to change this setting or otherwise fix the scaling just for these apps?