I have Samsung Galaxy S25. I decided to give default Samsung Keyboard a try (I previously used SwiftKey). I type in Polish and English. When long pressing a letter (eg 'a') I expect to choose a single alternative symbol ('!' in this case) and polish letters derived from 'a' ('ą'). Instead I get 1 expectedy symbol, 1 expected polish letter and 10 different a-adjacent characters to choose from, from (I guess) all the languages in the world. How do I make the keyboard to propose ONLY polish letters (and a symbol)?

Mobile operators in Brazil have added a leading digit, but *only* for São Paulo numbers. Now, both landline numbers (in São Paulo and otherwise) and mobile numbers from other states have 8 digits, while São Paulo mobile numbers have 9 (in addition to the optional area code that's 2 digits). I'd like 8-digit numbers to be formatted like 1234-5678 and 9-digit numbers formatted like 123-456-789. Is this possible? I've read the answers to following questions and none of them anwers this question: - https://android.stackexchange.com/questions/3527/is-it-somehow-possible-to-change-the-format-of-a-telephone-number-being-displaye - https://android.stackexchange.com/questions/25920/the-way-numbers-are-displayed-broken-up

Google Lens has a feature in which the user can download offline language packs so translations can be performed without an internet connection. That sounds great, but it appears to be very buggy. Language downloads often get stuck at 80-83%, and often even if they reach 100%, they never get added as offline languages. To make matters worse, after failed downloads, Google Lens often no longer thinks the offline language translation files are available for some languages. It's a buggy mess. How does one clear all the data/cache for Google Lens in Android 16, hopefully without clearing anything else? Clicking on the icons in the Google Lens 'Translate from' screen does not work properly.

I have had this question for quite a long time and I hope that it can actually be done. I live in Greece, but I mainly use my Android (Lollipop 5.0.2) mobile phone in English (US). The reason is that this is my personal preference. I feel a lot more comfortable having a UI in English. The problem I have is that when using applications that operate based on locale settings (distance, decimal points, etc) everything is according to the US locale and that's normal. But I live in Greece and would like, for example, Foursquare to display km instead of miles by default. Even though that's something you can change in settings, the decimal point in the Calculator app cannot be changed (US locale uses . for the decimal point and , for the thousands, while in Greek locale it is the other way around). So, is there a way (not necessarily a user-friendly one) to fine tune these settings to match the Greek locale, while still using EN_US as the display language? This does not answer my question. I would also be interested in manually editing the US locale, if necessary and possible.

I type in both English and in Hebrew on a Windows 10 PC and on Android. The latter device is a Pixel 4a(5G), running Android 11. The image attached to this question shows two Keyboards. The top one is a J.Burrows KB200 Bluetooth keyboard - a physical keyboard. Superimposed over it, in red characters, is a representation of a Hebrew-language keyboard layout. It represents the key-mapping you get in Microsoft Windows, when the input language is switched to Hebrew by selecting that setting on the language bar. That Bluetooth keyboard is compatible with both OS's mentioned above and can be paired with both devices. (Note that the red letters on the top row should be ignored. The crucial characters on that row are the diacritics attached to the letters. The letters are there only to show the positions of the diacritics relative to the letters they are attached to. The same applies to the rightmost key on the next row down.) The bottom keyboard is a screenshot of a virtual keyboard - Microsoft's OSK keyboard for Windows, showing its keyboard layout when the input language is switched to Hebrew on the language bar. This mapping has become a de-facto standard. In Hebrew script, all letters of the alphabet are consonants. There are also 14 vowels, which are represented by diacritics that go below, above, or in the letters they are attached to. In Windows, you add diacritics to Hebrew letters in a word processor (e.g. Word) that supports it as follows: Turn on CapsLock, position the cursor immediately to the left of the letter you want to add the diacritic to, then type the relevant key while holding down the shift key. To resume Hebrew alphabetic typing, you must turn off CapsLock. In the Windows keyboard layout for Hebrew, there are 14 keys for typing those vowels. On the J.Burrows keyboard, the keys for the first 13 vowels are the 13 leftmost keys on the number row (row 2), i.e. all the keys on row 2 except the Delete key at the far right. On the Microsoft OSK keyboard, those 13 keys are the 13 middle keys on the number row (row 1), i.e. all the keys on row 1 except the Esc key at the far left and the Backspace key at the far right. The 14th vowel, called "Qubuts," should be mapped to the key inscribed with "\" and "|" (lowercase and uppercase.) (Remember this one. It will be important for later.) On the J.Burrows keyboard, that key is the rightmost key on row 3, and on the Microsoft OSK keyboard, when the input language is set to Hebrew, it is the key on row 3 immediately to the left of the Enter key. At first, after connecting a new keyboard to an Android device, you will only be able to use it to type in the system's default input language. To use it with your desired input language(s), you must tell Android which language(s) you want to type in with that keyboard. That configures Android to use its keyboard layout(s) for your language(s) to interpret input it detects from that keyboard. (A keyboard-layout maps keys on a keyboard to characters in a language.) For that reason, whenever you connect a new physical keyboard, Android prompts you to set up keyboard layouts for it. If you miss the prompt, the path, on Android 11, to the relevant menu in the Settings is: **Settings > System > Languages & Input > Physical keyboard**. The physical keyboard must be connected and switched on for this to be shown. At that point, you have the option to switch on "**Use on-screen keyboard**," which keeps the virtual keyboard displayed even when you are using the physical keyboard. That is an optional setting, but to be able to switch languages on the physical keyboard, you must tap here on "**Set up keyboard layouts**," and then select the languages you want to use from a list of languages. (In my case, I select English (U.S.) and Hebrew.) Note: in Android 14 (and perhaps also in 12 and 13), you may not find "Hebrew" in the alphabetical list of language names among those starting with "H." It will be shown in Hebrew as "עברית" probably at the end of the list. After selecting your desired language(s), tap the left arrow at the top of the list to back out of that menu. At that point, Android presents you with a dialog box in which you can choose the language you wish to use for now. Do that, and note what it tells you about how to switch between languages. In the example shown above, it says, "to switch, press Control-Spacebar." Then continue backing out until you have completely exited the settings menu. The pairing and the selection of keyboard layouts only needs to be done once. Subsequent usage of the keyboard only requires that you switch on the keyboard and switch on Bluetooth on the Android device. When using a physical keyboard on Android, the method of typing Hebrew vowels is the same as the one used in Windows, described above. Likewise, in all respects except one, the Android keyboard layout for Hebrew is the same as the Microsoft one. The sole exception is that the 14th vowel, called "Qubuts" (Unicode Character U+05BB ) is completely missing from the Android layout. That vowel is shown here **בֻ** beneath the letter **ב**. Bearing in mind that, as mentioned above, the Microsoft keyboard layout has become a de-facto standard, and looking at the Microsoft OSK keyboard, you can see how, for a designer of a keyboard layout who is using the Microsoft layout as a guide, it is easy to overlook that character, because of its very unobtrusive position on the Microsoft OSK keyboard and also because it is similar in shape to a backslash (\), which is the unshifted character on that key. I have tried every combination of keystrokes I can think of and I can find no way to type it on Android, which convinces me that it has been erroneously omitted from Android's keyboard layout for Hebrew. This omission is very frustrating for a person typing in Hebrew. It is like trying to type in English on a keyboard with no comma on it, or a keyboard with no letter "u" on it. I'd like to know if those keyboard layouts that you are required to select from when connecting a new keyboard are native to Android or if they are supplied by Google, and how to notify the relevant people of this bug. Also, are those layouts editable without rooting the phone? If so, it might be possible to overcome the problem. If anyone has a solution, I'd be glad to hear it. **UPDATE:** I now have proof positive that what I observed using the J.Burrows keyboard is not hardware specific. I connected a USB-wired keyboard to my Android phone using an OTG-style adapter (USB-C, male to USB-2, female). The keyboard is a standard, 104-key, Dell, SK-8115. The phone recognised it as a keyboard and it worked immediately, but if I wanted anything other than the default keyboard layout and input language, I had to set up keyboard layouts, as described above, choosing the languages I wanted to use. Then, when I switched the input language to Hebrew by pressing Ctrl-Space, I could type 13 out of the set of 14 diacritics used as Hebrew vowels, but not the Qubuts character. The same keyboard attached to a PC can type a Qubuts, using the expected key as expected in Windows (the method described above.) The Android Qubuts bug is very real - at least in Android 11. **UPDATE 2:** Today I had the opportunity to test for this bug on a friend's Pixel 8a running Android 14 and I can confirm that this bug also exists in Android 14. The results of my testing on that phone were identical to what I reported above. **HOW TO REPLICATE THIS BUG:** This is how you can test whether your device or version of Android is affected by this bug, regardless of whether you can read Hebrew or not. The process for connecting the keyboard and setting up the required keyboard layouts is detailed above (note what was mentioned there about where to find Hebrew in the list), but I will recap here just what to type to replicate this bug: (a) If the physical keyboard is not currently typing in Hebrew, switch to Hebrew input, usually by typing Ctrl+Space on the physical keyboard. (b) type C [space] C. You should see: ב ב. Then place the cursor immediately to the left of one of those two Hebrew letters. (c) Turn on CapsLock, then, while holding down Shift, press 6 on the top number-row. It should now show as בֶ , proving that the method for typing diacritics works. (d) Turn off CapsLock and move the cursor to the immediate left of the second of those two Hebrew letters. (e) Now repeat step (c), but instead of pressing 6, press the key with \ and | on it. (f) You will either see בֻ or |ב . If the latter, you have replicated the bug. Available here is a PDF, no longer essential to this question, but containing a description of the problem, plus more information, with illustrations, about using multiple input languages on both Windows and Android and on typing diacritics. It is also easier to read. **UPDATE 3 A possible workaround:** This is not really an answer; it can't fix the bug in Android's stock keyboard layout for Hebrew. Nor is it, of itself, a workaround, but it could pave the path to one, if only I had the expertise to make use of it. Perhaps someone who does may step in to help ... Thank you Morrison Chang for pointing me to this related question asked here in 2019, which led me to this question , asked in 2013, to which there were a few answers linking to apps or resources no longer available, so they were dead-ends, but one answer by nymabatur of May 3 2021 points to this app by Calin-Darie on the Google Play store: More Physical Keyboard Layouts . I installed it. (There is no icon and it does nothing except add a bunch of keyboard layouts to Android's stock layouts.) One of the layouts it contains is a Hebrew one. It shows up in Android's layout list as "**Hebrew (standard)**" with the subtitle "Extra keyboard layouts" beneath it. It doesn't help with this problem; in fact, it makes it worse. Not only can't you type a Qubuts when that layout is selected, you also can't type any of the other 13 Hebrew-diacritics (U+05B0 - U+05BA, and U+05BC) - at least not in the manner that Windows users and users of Android's stock Hebrew layout are accustomed to typing them. So I don't know what standard Calin's layout follows, but it's certainly not the Microsoft one that, as I mentioned above, has become a de-facto standard - also followed by Android, save for the omission of the Qubuts vowel. But it does hold some promise of a solution. Firstly, it is an open-source app, residing here on Git Hub. Also, here , under "issues" luigge asks if there is a way to create a custom layout to use with the app. To that, jidhub replies that that is exactly what his fork does. I don't know if what jidhub has created is installable on an Android device as an app, even if it has to be sideloaded, or how to insert a custom layout in it. I have zero experience or knowledge in creating keyboard layouts, but it seems to me that if someone more savvy in this area were to approach such a task as follows, it should not be too difficult to create a workaround for this bug. If a developer started with a copy of Android's stock Hebrew layout, which, aside from the missing Qubuts, is quite a satisfactory one, and then added just one more character - the Qubuts, of course - mapped to the "\ |" key, but with the proviso that it should only produce a Qubuts when both CapsLock and Shift are on, and the developer can add that custom layout to jidhub's fork of Calin's project and turn it into an app, that would be exactly what is needed as a workaround for this bug. This may be of some help. (thank you again Morrison Chang for the link), but I'm not sufficiently knowledgeable in this area to make good use of it myself.

Is it possible to force localization through a specific satellite system in case of jamming/bad reception. I see on GPS test that my phone (S23+, Android 14) can receive Glonass/Galileo/Beidou But I did not manage to base navigation on one of them (Maps or other). I will be happy to find a solution, preferably with offline maps, in order to minimize external data dependency.

I have an issue with achievements in Google Play Games. I've noticed this when playing Clash of Clans (but it's not limited to it. Every game that has Russian translation of achievements is affected). I used to use Russian language in the game and my Google account. Now my Google account and system language is set to Ukrainian, and the language of the game is set to English. Google Play country is set to Ukraine. However, Play Games continues to show achievements in Russian. I can't find how to change it. I've already asked for the help from the community, but got no answer after more than a week: https://support.google.com/googleplay/thread/251211195

I'm travelling to country X. I want to install an application which isn't available in my country, but is available in country X; but I prefer to download and install it in advance, while the data connection is still cheap. Unfortunately, the Play Stores does not allow me to install this app. Is there any way to circumvent this limitation?

I have just bought a surprisingly-cheap refurbished Samsung S10+ to (eventually) replace my elderly S7. I have not yet tried to connect it to my Samsung/Google accounts. The S10+ is running Android 12. Settings > About phone shows:

Phone number                   unknown
Model name                 Galaxy S10+
Model number               SM-G975F/DS
Serial number                      ...
IMEI (slot 1)                      ...
IMEI (slot 2)                      ...
United Arab Emirates       TRA ID: ...
                               TA: ...

The S7 has Android 8 and does not show a country on this setting page. What is the significance of the country? How does it affect operation of the phone? I am in UK. Should I be trying to change the display to say UK? Perhaps flash a local firmware? I can provide information from Software information, etc, if any of that will be relevant.

I translated the firmware Flyme 8.0.0.0A Stable (RU & UA) for Meizu Note 9 and Meizu 8X, but I can’t kill the Chinese in the quick settings: The fact is that China’s events are taking place there - the usual date, for example, if you translate from Chinese “己亥 年 十月 廿六” - “October 26.” Who can help remove this problem from the quick settings? Or at least tell me where to look in SystemUI.apk , I suspect that somewhere in the Smali code. Thanks.

I suppose I expected Android to handle this like Linux, but it seems the default folder names must stay in English. Is this just the Irish-language locale on Samsung or does it work that way for other languages? Is there a way to let the OS know what my localised folders are? **Edit:** By default folders, I mean the user folders called *Downloads*, *Music*, *Pictures*, etc.

I'd like to connect a German Macintosh keyboard to my Android device. It uses swapped signals for °/^ and ` as well as different positions for [, ], {, } and @`. It also has a bunch of special characters, but I don't consider those of high priority. I tested [More Physical Keyboard Layouts](https://play.google.com/store/apps/details?id=varzan.extraKeyboardLayouts) , but it doesn't feature Macintosh layouts ([yet](https://github.com/calin-darie/extra-keyboard-layouts/issues/29)) . I also saw the [External Keyboard Helper Pro](https://play.google.com/store/apps/details?id=com.apedroid.hwkeyboardhelper) that allows to define a custom layout, but it requires a Google Account to buy it from the Play Store, but I need a solution that works with AOSP. (Free apps on the Play Store are fine, because I can download those anonymously using the Aurora Store.)

My Android 10 phone's voice recognition for English works extremely well, but when I travel to India it switches to expect an Indian accent, and I can barely get it to take my dictation that way, even though I can adapt to speak the local accent some of the time. Can we tweak some settings to avoid this change in the underlying machine learning model so that it keeps interpreting my English dictation as either UK or US accents of English, thus retaining its existing, pre-travel, levels of accuracy? I really rely on voice dictation quite a lot. When referring to voice recognition, I primarily mean the voice typing feature available through the Google Keyboard's microphone icon, but I suspect that the same underlying components also handle the "Hello Google" stuff. When I go outside of India, it clearly does revert back to expecting US or UK accents again, as if over-adapting to the geography rather than remaining loyal to the user that's already using it. Actually, at least one person native to India who speaks the Indian accent and dialect of English has mentioned the same issue to me, which they only experience in reverse ― voice recognition accuracy plummets for them when they travel to other English-speaking countries.

I have a Bluetooth external keyboard with German layout (QWERTZ) that worked well with my old Huawei P10 Lite phone (Android 8.0). Unfortunately with my current Oppo Android 12 (ColorOS 12.1) phone I have a big problem: I cannot switch the keyboard layout, that is: Make Android know that the keyboard layout is German. When I press Shift+Space, then the layout of the *virtual* keyboard displayed changes, but the keys on the external keyboard "still send the wrong character" (e.g.: I press Z on the keyoard, but Y is entered on the phone). Did I use the wrong method to change the layout of the external keyboard, or is this some bug? I see this question is very similar to https://android.stackexchange.com/q/200692/377587

How can I set the date format to ISO 8601 (e.g. 2023-04-29) or RFC 3339 in GrapheneOS?

Google Maps always shows me distance values for direction results / navigation in miles, although it does show me a scale on the map itself in metric units. I rather prefer to get my direction distances in metres/kilometres. Is there any way to achieve this in Google Maps? I searched a bit for this and suggestions seem to be to change locale in Settings > Language and Keyboard. Mine is currently set to English UK.

My phone (Fairphone) does not have the 'English (UK)' locale, only the US one. I recently discovered how to download custom voices for Google text-to-speech ('Install voice data' from settings) and have downloaded a UK English voice to replace the default American voice, which I find incredibly irritating (sorry, Americans!). Unfortunately, even though I have downloaded the voice data, I still seem unable to switch to the new voice, as 'English (UK)' is still not an option when visiting TTS's 'Language' menu. Am I missing something here? How do I make my phone speak to me in my native language? (My Android version is 4.2.2)

I want to have both english **and** german prediction and auto correction at the same time for the stock keyboard (Jelly Bean here). My use case: Multi-tasking between english and german domains on my tablet where I both need the keyboard (e.g. Google Talk with my german friends and editing/answering questions on Android Enthusiasts in english). Problem: I don't want to switch off prediction/auto-correction nor do I want to switch to an alternative keyboard. At the moment I have to manually switch between en/de keyboards when I switch tasks (from *Google Talk* to the *browser* and back). This is annoying. I don't mind the keyboard layout (QUERTZ or QUERTY) but would prefer the english one. How can I have simultaneous multi language prediction/auto-correction in the stock keyboard?

My Google cards are acting weird. 40% of the cards are in other languages which I have no clue of. It's sometimes Urdu, sometimes Russian, and sometimes god knows which one.  I have tried hitting "not interested" on several of these, but it keeps coming up in my feed. I'm pretty much sure that I have not changed any language and settings on my phone. I haven't had any recent app installs too. Anybody help me with this?

I have moved from Hong Kong to the UK. I am now physically in the UK connected to the UK network with a UK number and a UK SIM. However, I can't change my Play Store country to the UK. Initially, in the Play Store app in Android, under country and profiles, there was Hong Kong and it suggested me to change to the UK, listing a few options how I can add a payment method, including adding credit / debit card, Three Pay, etc. I tapped adding credit / debit card, and it showed a warning saying that I won't be able to use my current balance, and I won't be able to change again for 365 days. I tapped continue, the warning disappeared, and nothing happened. I then used my computer to signed in Google Pay, created a UK profile, and added a UK debit card to it. Then under country and profiles, both Hong Kong and the UK appeared, with Hong Kong selected. When I tapped the UK, the same warning appeared, and after I tapped continue, the warning disappeared and nothing happened. I have two Android phones and they behave the same. I cannot delete my Hong Kong payment profile as I have a Developer account and an AdSense account tied to it. How can I change my Play Store country to the UK? I have tried deleting storage and cache for my Play Store, and also tried removing the Google account and adding back in, but they didn't help. Initially on the first day I landed the UK a box did appear for me to enter my account details, but I hadn't got my debit card yet at that moment so I didn't continue.