I am using a porn blocker to protect my kids. But I got to know that there is a workaround to that by rebooting into safe mode. I also tested it and I was able to access everything. Now my paid subscription to blocker seems useless. I am also worried about the kids. So is there any way I can block safe mode in my device? Like editing build.prop file or making any other change and safe mode blocker.

How can I export bookmarks from my Android 4.1.2 Stock Browser, for use in Chrome and Firefox on my PC? I've checked the stock browser thoroughly, but could not find anything like the Export feature found in desktop browsers. Would appreciate some help, since I have a ton of book marks on my phone, and need them on my PC.

My HTC One M7 phone is S-OFF, has the latest firmware 7.19.401.2, and has nicely installed "ViperOne+9.0.0-fix", the recovery is TWRP 2.8.6.0. Everything works very well, except that the proximity sensor seems erratic, and when I have a call the ear seems to press different programs on the touchscreen. I would like to return to complete HTC stock ROM so that I assure myself the proximity sensor works well enough (or does not). Do I have to downgrade the firmware to be able to install the stock ROM? I have downloaded the stock ROM PN07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2_Radio_4T.35.3218.16_10.33Q.1718.01L_release_421790_signed.zip but seem to be unable to install from TWRP. Or maybe the only way is via fastboot? With the commands: 1) htc_fastboot oem rebootRUU 2) htc_fastboot flash zip RUU.zip 3) htc_fastboot reboot-bootloader Can someone more experienced give some advice, please?

What is the best way to set the left-right balance on a pair of earphones/headphones? I've looked into it, but I can't seem to find an easy way to do this. Does anyone know of a way to do this? I know very little about Android development, so a simple solution would be best (preferably an app). I am on a rooted Nexus 6P on stock Android 7.1.1

Is in Android there is an available database set for limits display frame rate? If they’re available, is using ADB/Root (Terminal), or how, or even it can't? I've been searching this for years, and not get an answer yet. Actually, this is for tweaking to trigger any benefits. This like my other phone embedded feature is Xperia STAMINA mode which is it can set the display frame rate (to 2x lower from 30 fps) for battery saving. But... I mean is not only for that. Many others too that can benefit. So, is this can available on a pure Android system? Or this only self-made for manufacture's hardware so that not possible available on others except Xperia devices? If there are other threads that I don't know. Please let me know. I'll understand it, and try if it makes sense.

Android 13 and 14, under settings, there's only options for SIM specific ringtones: There's no "Default" ringtone! (NOTE: screen shot from websearch. I'm using a stock android on a PIXEL, and on a MOTOROLA. Both have the same options as the screen shot, which is for illustration that there is "ring tone" for each SIM card, and no "default") Yet, every app is set to use "Ringtone: Default"! This causes apps like whatsapp, to ring for whatsapp calls using the original default of the phone (which is NOT set to either SIM card's ringtones)... now i get the atrociously horrible and unbearable "hello moto" ringtone for those apps. I could configure every single app to use a different ring tone, but why if they are all using the "default"... the question is how do i set the "default" i want? I cannot believe google screwed up that bad again and there's no way to set it. I just think this is usual google usability and the setting is hidden in some completely non-obvious place. -- Another tidbit. I have four phones. Pixel pro with one SIM card and one E-Sim. (both being used) Pixel with one SIM card and one E-sim (only physical sim present, esim empty) Motorola with one SIM card and one E-sim (only physical sim present, esim empty) Motorola with two physical sim cards, but only one inserted. On all phones, they run android 13 and 14, stock from manufacturer. And the ringtone settings are exactly the same as the included screenshot (but with the regular Material design styling)

Following Google's guide for flashing/restoring the stock Android ROM, and initially using the default *flash-all.sh* shell script to flash the stock Android ROM to my device, I noticed that I am not able to do this successfully on the second consecutive attempt. When flashing the stock Android ROM the first time (usually when flashing the stock over a custom ROM or flashing the stock recovery over the existing TWRP recovery), the first attempt successfully flashes the stock Android ROM to the device and I am presented with the Android setup wizard. However, if I repeat the same flashing process once more, the device is stuck on the Android logo boot animation. I read that this is caused by the cache partition not being erased before flashing. Several tutorials have claimed that the cache needs to be wiped from within the recovery, and although I have tested this to be successful, I would prefer a method that can erase the cache during the flashing process (or an adb or fastboot alternative) without having to re-enter recovery. I have tried adding the fastboot commands to the *flash-all.sh* shell script to erase cache and erase userdata, either before or after flashing all of the partitions with those of the stock image, but it does not solve the issue. My device is the Huawei Nexus 6p and I am using the latest stock Android ROM for Angler (8.1.0 (OPM7.181205.001, Dec 2018)), which does not contain a *cache.img* file (removed since Android 8.0). I am aware that I could extract the *cache.img* file from an earlier stock image (e.g. Android 7.0) and flash that with fastboot, but I'd prefer not to have to rely on two different stock images, and one just for the archived *cache.img*. My customised *flash-all.sh* shell script, inspired by examples here and here , is as follows:

fastboot flash bootloader bootloader-angler-angler-03.84.img
fastboot reboot-bootloader
sleep 2
fastboot flash radio radio-angler-angler-03.88.img
fastboot reboot-bootloader
sleep 2
fastboot flash recovery recovery.img
fastboot reboot-bootloader
sleep 2

# no cache image (cache.img) in Android 8.0+, instead:
fastboot erase userdata
fastboot erase cache

# does not seem to flash images, even if extraced into the PWD
fastboot -w update image-angler-opm7.181205.001.zip

# ... which is the equivalent to (in the correct order) 
fastboot flash boot boot.img
sleep 2
fastboot flash system system.img
sleep 2
fastboot flash vendor vendor.img
sleep 2

fastboot erase userdata
fastboot erase cache
sleep 2
fastboot reboot

Q: What command(s) can I use during the flashing process (i.e within the bootloader) to successfully erase the cache partition so that I am not stuck on the boot animation logo upon startup?

I recently bought a Realme XT phone 8 GB variant. I usually get only 4 GB RAM free and the rest of the RAM is used by the system. So I want to know if it's usual for an 8 GB RAM system to take up to 4 GB RAM for the system process. Below is a screenshot taken from the 'Developer options -> running services' >

I have Samsung Galaxy M12 on stock Android 12. When I'm reading about Samsung features on the internet (including [tag:samsung]-related questions here), sometimes I found that I don't have such features on my phone, like Secure Folder. What are the possible reasons for the lack of features?

I am having problems setting the kernel to permissive (SElinux). I have already tried the setenforce 0 command with terminal but it immediately goes back to enforcing as soon as I set the setenforce 0 command. So I finally got fed up and decided to monitor what was actually going on in my phone by using a logcat. After looking at the logcat, I found a line of code that could be setting the kernel to enforcing by default. Here is the code: /audit ( 6001): type=1404 msg=audit(1479393162.929:264): config_always_enforce - true; enforcing=1 old_enforcing=1 auid=4294967295 ses=4294967295 The config_always_enforce is set to true so that means I should probably set this to false. Unfortunately I don't know where this value is in my system. Does anyone have any idea? I have a Galaxy S6. Also, I removed all the Knox apps, but everytime I reboot, I get Knox folders reappearing and a file called knox emulated in the /storage folder. Have I not removed all the Knox apps? I will post my logcat that way ya'll can take a look at it. I hope you all can help me because I really want a custom ROM so I can use Xposed.

I have noticed unusual and unwanted behavior from a few of my system apps, most notably Google Play Services, Google Account Manager, and Google Services Framework. These apps cause force closes on their own operations as well as those of other apps, they seem to have the capability to take over functionality of my phone completely at times. So, I used the Virustotal.com tool to analyze permissions on these apps to determine if they are present with the right capabilities built into them for the version that came pre-installed on the phone. For each of these apps, they returned between 10-20 additional permissions each that they were not designed to have, suggesting that they have been tampered with. My phone is not rooted or modified in any way and I have had it for less than a year. These additional permissions were labeled: > (Unknown permission from android reference) designating these specific permissions as not being native to these apps. Some of these permissions are specifically designed for transmission and communication of data via C2DM and Gtalk to other devices, as well as exposure of saved account details including passwords. This leads me to conclude that sensitive personal information has been leaked to third parties. Here is the output for Google Account Manager as an example: VirusTotal SHA256: 602db0ceb05877fb6996fd2a3510721d0e32463a6e784ba5cc60ae1f71bb3226 File name: GoogleLoginService.apk Detection ratio: 0 / 53 Analysis date: 2014-07-20 19:04:51 UTC ( 9 months, 1 week ago ) 0 0 Analysis File detail Additional information Comments 0 Votes Behavioural information The file being studied is Android related! APK Android file more specifically. The application's main package name is com.google.android.gsf.login. The internal version number of the application is 19. The displayed version string of the application is 4.4.4-1215936. The minimum Android API level for the application to run (MinSDKVersion) is 8. The target Android API level for the application to run (TargetSDKVersion) is 17. Risk summary The studied DEX file makes use of API reflection Permissions that allow the application to access Internet Permissions that allow the application to access private information Other permissions that could be considered as dangerous in certain scenarios Required permissions android.permission.CHANGE_NETWORK_STATE (change network connectivity) android.permission.READ_SYNC_SETTINGS (read sync settings) com.google.android.providers.gsf.permission.READ_GSERVICES (Unknown permission from android reference) android.permission.USE_CREDENTIALS (use the authentication credentials of an account) android.permission.DUMP (retrieve system internal status) android.permission.READ_LOGS (read sensitive log data) android.permission.WRITE_PROFILE (write the user's personal profile data) android.permission.CHANGE_COMPONENT_ENABLED_STATE (enable or disable application components) android.permission.READ_SYNC_STATS (read sync statistics) android.permission.RECEIVE_BOOT_COMPLETED (automatically start at boot) android.permission.INTERNET (full Internet access) com.google.android.googleapps.permission.GOOGLE_MAIL_SWITCH (Unknown permission from android reference) android.permission.BACKUP (control system back up and restore) com.google.android.googleapps.permission.GOOGLE_AUTH.youtube (Unknown permission from android reference) android.permission.SUBSCRIBED_FEEDS_READ (read subscribed feeds) android.permission.MANAGE_ACCOUNTS (manage the accounts list) com.google.android.gtalkservice.permission.GTALK_SERVICE (Unknown permission from android reference) com.google.android.permission.BROADCAST_DATA_MESSAGE (Unknown permission from android reference) com.google.android.googleapps.permission.GOOGLE_AUTH.YouTubeUser (Unknown permission from android reference) android.permission.PERSISTENT_ACTIVITY (make application always run) com.google.android.googleapps.permission.GOOGLE_AUTH.ALL_SERVICES (Unknown permission from android reference) com.android.vending.TOS_ACKED (Unknown permission from android reference) android.permission.ACCESS_NETWORK_STATE (view network status) com.google.android.providers.settings.permission.READ_GSETTINGS (Unknown permission from android reference) com.google.android.providers.settings.permission.WRITE_GSETTINGS (Unknown permission from android reference) com.google.android.googleapps.permission.GOOGLE_AUTH (Unknown permission from android reference) android.permission.WRITE_CONTACTS (write contact data) android.permission.WRITE_SYNC_SETTINGS (write sync settings) android.permission.AUTHENTICATE_ACCOUNTS (act as an account authenticator) android.permission.BROADCAST_STICKY (send sticky broadcast) com.android.vending.billing.BILLING_ACCOUNT_SERVICE (Unknown permission from android reference) android.permission.WRITE_SETTINGS (modify global system settings) android.permission.READ_PHONE_STATE (read phone state and identity) com.google.android.googleapps.permission.GOOGLE_AUTH.mail (Unknown permission from android reference) com.android.vending.INTENT_VENDING_ONLY (Unknown permission from android reference) com.google.android.providers.talk.permission.READ_ONLY (Unknown permission from android reference) com.google.android.googleapps.permission.ACCESS_GOOGLE_PASSWORD (Unknown permission from android reference) com.google.android.providers.talk.permission.WRITE_ONLY (Unknown permission from android reference) android.permission.VIBRATE (control vibrator) com.android.chrome.TOS_ACKED (Unknown permission from android reference) android.permission.SUBSCRIBED_FEEDS_WRITE (write subscribed feeds) android.permission.ACCESS_WIFI_STATE (view Wi-Fi status) com.android.vending.billing.ADD_CREDIT_CARD (Unknown permission from android reference) android.permission.WAKE_LOCK (prevent phone from sleeping) android.permission.CHANGE_WIFI_STATE (change Wi-Fi status) android.permission.READ_CONTACTS (read contact data) com.android.vending.billing.IBillingAccountService.BIND2 (Unknown permission from android reference) android.permission.READ_PROFILE (read the user's personal profile data) com.google.android.gtalkservice.permission.SEND_HEARTBEAT (Unknown permission from android reference) android.permission.GET_ACCOUNTS (discover known accounts) Permission-related API calls ACCESS_NETWORK_STATE Landroid/net/ConnectivityManager;->getActiveNetworkInfo()Landroid/net/NetworkInfo; called from Lcom/google/android/gsf/loginservice/BaseActivity;->hasNetworkConnection()Z READ_PHONE_STATE Landroid/telephony/TelephonyManager;->getLine1Number()Ljava/lang/String; called from Lcom/google/android/gsf/login/RecoveryDataActivity;->initViews(Landroid/os/Bundle;)V USE_CREDENTIALS Landroid/accounts/AccountManager;->invalidateAuthToken(Ljava/lang/String; Ljava/lang/String;)V called from Lcom/google/android/gsf/loginservice/GoogleLoginService$GlsImplementation;->invalidateAuthToken(Ljava/lang/String;)V INTERNET Ljava/net/ServerSocket;->(I)V called from Lcom/google/android/common/http/TestHttpServer;->(I)V Landroid/webkit/WebView;->(Landroid/content/Context;)V called from Lcom/google/android/common/GoogleWebContentHelper;->initializeViews()V Landroid/webkit/WebView;->(Landroid/content/Context;)V called from Lcom/google/android/gsf/login/CustomWebView;->(Landroid/content/Context;)V VIBRATE Landroid/app/NotificationManager;->notify(I Landroid/app/Notification;)V called from Lcom/google/android/gms/auth/GoogleAuthUtil;->a(Landroid/content/Context; Ljava/lang/String; Ljava/lang/String; Landroid/os/Bundle;)Ljava/lang/String; ACCESS_WIFI_STATE Landroid/net/wifi/WifiManager;->getWifiState()I called from Lcom/google/android/gsf/login/SetupWirelessActivity;->tryEnablingWifi()Z GET_ACCOUNTS Landroid/accounts/AccountManager;->getAccountsByType(Ljava/lang/String;)[Landroid/accounts/Account; called from Lcom/google/android/gsf/login/BaseActivity;->isFirstAccount()Z Landroid/accounts/AccountManager;->getAccountsByType(Ljava/lang/String;)[Landroid/accounts/Account; called from Lcom/google/android/gsf/login/AccountIntroActivity;->maybeSkipAccountSetup()Z Landroid/accounts/AccountManager;->getAccountsByType(Ljava/lang/String;)[Landroid/accounts/Account; called from Lcom/google/android/gsf/login/EduLoginActivity;->removeAnyNewAccounts()V READ_SYNC_SETTINGS Landroid/content/ContentResolver;->getIsSyncable(Landroid/accounts/Account; Ljava/lang/String;)I called from Lcom/google/android/gsf/login/SyncSettingsFragment;->updateListViewData(Landroid/accounts/Account;)V CHANGE_COMPONENT_ENABLED_STATE Landroid/content/pm/PackageManager;->setApplicationEnabledSetting(Ljava/lang/String; I I)V called from Lcom/google/android/gsf/login/ShowErrorActivity;->onClick(Landroid/view/View;)V MANAGE_ACCOUNTS Landroid/accounts/AccountManager;->removeAccount(Landroid/accounts/Account; Landroid/accounts/AccountManagerCallback; Landroid/os/Handler;)Landroid/accounts/AccountManagerFuture; called from Lcom/google/android/gsf/login/EduLoginActivity;->removeAnyNewAccounts()V Landroid/accounts/AccountManager;->removeAccount(Landroid/accounts/Account; Landroid/accounts/AccountManagerCallback; Landroid/os/Handler;)Landroid/accounts/AccountManagerFuture; called from Lcom/google/android/gsf/loginservice/GoogleLoginService$GlsImplementation;->deleteAllAccounts()V Landroid/accounts/AccountManager;->removeAccount(Landroid/accounts/Account; Landroid/accounts/AccountManagerCallback; Landroid/os/Handler;)Landroid/accounts/AccountManagerFuture; called from Lcom/google/android/gsf/loginservice/GoogleLoginService$GlsImplementation;->deleteOneAccount(Ljava/lang/String;)V AUTHENTICATE_ACCOUNTS Landroid/accounts/AccountManager;->getUserData(Landroid/accounts/Account; Ljava/lang/String;)Ljava/lang/String; called from Lcom/google/android/gsf/loginservice/GoogleLoginService;->accountHasFeatures(Landroid/accounts/AccountManager; Landroid/accounts/Account; [Ljava/lang/String;)Z Activities com.google.android.gsf.login.AccountIntroActivity com.google.android.gsf.login.AccountPreIntroUIActivity com.google.android.gsf.login.AccountIntroUIActivity com.google.android.gsf.login.PlusQueryActivity com.google.android.gsf.login.PlusFaqActivity com.google.android.gsf.login.NameActivity com.google.android.gsf.login.BadNameActivity com.google.android.gsf.login.PhotoActivity com.google.android.gsf.login.LearnMoreActivity com.google.android.gsf.login.WaitForDeviceCountryActivity com.google.android.gsf.login.CaptchaActivity com.google.android.gsf.login.SetupWirelessIntroActivity com.google.android.gsf.login.SetupWirelessActivity com.google.android.gsf.login.LoginActivity com.google.android.gsf.login.EduLoginActivity com.google.android.gsf.login.UsernamePasswordActivity com.google.android.gsf.login.PrepareAccountSetupActivity com.google.android.gsf.login.LoginActivityTask com.google.android.gsf.login.ShowErrorActivity com.google.android.gsf.login.SyncIntroActivity com.google.android.gsf.login.CreateAccountActivity com.google.android.gsf.login.PlusActivity com.google.android.gsf.login.PlusCheckTask com.google.android.gsf.login.UsernameActivity com.google.android.gsf.login.CreateAccountTask com.google.android.gsf.login.ProfileTask com.google.android.gsf.login.NameCheckTask com.google.android.gsf.login.CheckAvailTask com.google.android.gsf.login.SuggestUsernameActivity com.google.android.gsf.login.VerifyProfileActivity com.google.android.gsf.login.ChoosePasswordActivity com.google.android.gsf.login.RecoveryIntroActivity com.google.android.gsf.login.GetCountryListTask com.google.android.gsf.login.RecoveryDataActivity com.google.android.gsf.login.AccountSecurityActivity com.google.android.gsf.login.PicassaInfoActivity com.google.android.gsf.login.GoogleServicesActivity com.google.android.gsf.login.TermsOfServiceActivity com.google.android.gsf.login.BrowserActivity com.google.android.gsf.loginservice.GrantCredentialsPermissionActivity Services com.google.android.gsf.loginservice.GoogleLoginService Receivers com.google.android.gsf.login.DevicePolicyActivatedReceiver Service-related intent filters com.google.android.gsf.loginservice.GoogleLoginService actions: android.accounts.AccountAuthenticator, com.google.android.gsf.action.GET_GLS Activity-related intent filters com.google.android.gsf.login.AccountIntroActivity actions: com.google.android.accounts.AccountIntro, android.intent.action.MAIN categories: android.intent.category.DEFAULT Receiver-related intent filters com.google.android.gsf.login.DevicePolicyActivatedReceiver actions: com.google.android.apps.enterprise.dmagent.AUTO_REGISTRATION_FINISHED Code-related observations The application does not load any code dynamically The application contains reflection code The application does not contain native code The application does not contain cryptographic code Application certificate information Issuer DN: C=US, ST=California, L=Mountain View, O=Google Inc., OU=Android, CN=Android C: US CN: Android L: Mountain View O: Google Inc. S: California OU: Android Subject DN: C=US, ST=California, L=Mountain View, O=Google Inc., OU=Android, CN=Android C: US CN: Android L: Mountain View O: Google Inc. S: California OU: Android Who should I bring this information to the attention to? Is it pretty much certain that my phone is completely compromised?

(Stock android.) "E:Cannot log to file /dev/fscklogs/log" -Other phones don't prompt this during the data wipe(factory reset), this is fecking intentional. Also it got no battery charging cycle count in the bug report neither. Is there any other reliable way to determine if the phone is genuinely brand new? Through Recovery Mode and Android Settings, Wipe Data(Factory Reset) related log entries should persist in the recovery log file under Recovery Mode right? The related log entries should persist even after reboot, power off, wipe data(factory reset), right? Other phones I've used will retain all wipe data related log entries. Currently I've a brand new android phone that doesn't do that. 'Wipe data' related log entries will disappear after powering off or rebooting the device(the recovery log file still exist, and judge by the changes of the numbers inside every [ ] at the start of every line, all remained log entries are actually newly generated, though the log file's size will shrink back to the exact size before the wipe data action). (It proceeds like this: Go into the recovery mode; No wipe data related entry inside the recovery log file; Perform wipe data; Related entries appear, the log file's size increases; Reboot or power off then on again; Wipe data related entries disappeared, the log file's size shrink back to before the wiping, the numbers inside every [ ] at the start of every lines have changed.) Such shady doing, alternating the default logging behavior.

I have Micromax A89 mobile with ICS 4.0.4 OS AND MTK 6577 processor. I would like to install Jellybean 4.2.2 OS on my MMX A89 device. Is it possible? Even I would like to install Kitkat 4.4 too if possible? 1. What are the steps to install Jellybean 4.2.2 (or 4.3) on my MMX A89 device (safer way to install)? 2. If I could able to install Jellybean 4.2.2 on MMX A89 then further it is possible to install Kitkat 4.4 in future? Can anybody help me for this?

I am trying to figure out if there is a method of installing Xposed framework on **stock ROM** without custom recovery (e.g CWM or TWRP). The conventional method that I am well familiar with is installing the framework via Xposed app on a rooted device. I researched a bit and most workarounds were promising although not successful: According to this source , the method involves setting the system partition writable then pushing the necessary files via adb commands however fails with Permission denied errors. I suspect bootloader issues (which seems to be locked) here but not very sure. The other way, described here doesn't need custom recovery. This involves installing a third party application (FlashFire) to flashed unsigned .zip but unfortunately seems to require root (from description). The last one involves using new systemless xposed framework but the problem is that it supports android 5+ versions. So is there any convenient way of installing xposed framework on **stock recovery without root**? **Edit** Following important discussions raised in comments, I guess I have to explain why I want to bypass root-based installation procedure, it's because the device in use is not rooted, so I need to use a non root installation mrthod. Contrary to the comments however, some users have used Xposed without **root**: > **Xposed only needs root access when you install** it, then everything > else is completely transparent to the user because the framework acts > as a **separate conduit** to the system -- it doesn't go through the usual > SU channels Also the device is running Android 4.3 stock

I had noticed in my phone's applications manager, that the size of the system apps are displayed as 0B, which indicates that no memory space is occupied by that particular app. Please see this screenshot in which the pre-installed Browser app is shown to have occupied no memory space: " class="img-fluid rounded" style="max-width: 100%; height: auto; margin: 10px 0;" loading="lazy"> But, I know that every app is composed of several files, so no app can have 0B size. But, the size of third-party apps are shown correctly. Why does this happen ?

Every spam call I get is from a different "burner" number. Android asks me if I wish to "block and report" the number. I wish to report it, but not block it, as it may be a spoofed number from someone who I will eventually wish to hear from. Is there a way to "report" only? See also https://android.stackexchange.com/questions/179400/can-i-report-phone-numbers-as-not-spam-callers And https://www.nomorobo.com/ My particular phone is "stock google pixel" but answers for any version of android are welcome.

I was playing around with the Google SDK and realised that I could not browse the filesystem/external storage, etc. I feel extremely silly asking this, but how do I browse the SD card?

I understand and can patch avb on devices that don't use EROFS filesystem as we normally just edit `/etc/fstab` which is normally in boot.img or boot.bin or in boot_a.bin with devices that A/B or plain images. The main issue I have is that when you have just modified your system or super your changes don't appear untill you have disabled avb, especially on devices that no longer use ext4 images.

Appears Wire no-longer takes bug reports ala https://github.com/wireapp/wire/issues/391 so maybe someone here knows from where this problem originates. I run newer Wire in Kotlin on Graphene OS, so stock Android mostly, without google play services. Wire imposes a buggy on-screen keyboard, which you can reproduce like: 1. type at least two words like "cat dig" with a type-o in the last word, but before the last letter. 2. press space to start another word, 3. press back at least three time, like you wanted to change the "i" to an "o", 5. wire incorrectly removes the space between the last two words, which gives "catdo". not the expected "cat d" This bug never happens in other apps, only Wire. I've not tried to reproduce this on true stock Android, but it's unlikely Graphene OS changes the keyboard much if at all. Is this some problems caused by some configuration outside Wire itself perhaps? It's clear Wire changes the keyboard, but maybe they use some Kotlin keyboard libs for which this problem is known?

I am having an issue with mobile data no longer working. Mobile data *was* working the day after updating to Android 5.1 on my Nexus 5. But now (1 day later) it is not connecting to mobile data. It just has the cellular icon, with an exclamation point. I've tried toggling data, airplane mode, WiFi, rebooting, factory reset, and resetting the SIM card. The last thing I tried is to call my carrier and go through 2 hours of troubleshooting. They said the only thing left for them to do is send me a new SIM card. It makes no sense. Everything else works fine. I can make and receive calls. Texting works. And WiFi works as well. Just not the mobile data. The weird thing is that it stopped working on the first day of my mobile data cycle. But the carrier swears that all is well on their side.