Looked through all the answers and tried a few things none of them worked.
The phone number is programmed in and works on apple phones and dials the extension - but it does not work on Android.
We tried adding commas before the extension and also tried adding a "w" instead of "pp", none of these work. This was all we read when going through previous questions and responses.
For instance, we tried inputing these lines:
Number here
Number here
Number here
Number here
Any other suggestions to get this to work on Android phones?
Related
I wanted to implement a normalizer for a username Field (I use Redux form), which would result in all of the capital letters being immediately transformed to lowercase.
I used the Redux Form normalizing example, and it worked very well on the Android Emulator (exactly as in the link above, so I didn't record it).
However, I decided to test it on an Android device (Samsung Galaxy S8+ with Android 8.0) and ran into a weird case: the first letter got lowercased perfectly, but inputting any other letters would clone the previously input ones.. The same happened when I ran the app on my coworker's Xperia with Android 6.0.
Finally, after failing to figure it out, I just moved the normalization to my login saga, where I just split the body into username: action.loginForm.username.toLowerCase(), password:(...). However, I'm curious if any of you have encountered a similar bug/know how to solve it? Such knowledge would definitely make the code more readable:)
I understand CodeMirror has issues on mobile and behavior varies with extensions in use.
However, for me it seems pretty much unusable everywhere I encounter it on Android. Have a look at Kotlin Koans and try the Backspace key. Amongst other things, I get gobbledygock and a bunch of newlines.
I did not find a single way around this. Tried two devices (OnePlus 3T and Pixel C) running Android 7 and 8 using on-screen keyboards or bluetooth physical ones. The results are pretty much the same.
This seems pretty odd and I am surprised nobody (Google?) is stepping in to fix it.
I'd like to use an Android device for basic (CodeMirror-based) coding, and I'd very much appreciate a suggestion to get around this annoyance. :)
Thanks
Code Editor inserts a new line above current line on every keypress
Android native app using WebView, backspace doesn't work properly
I am trying to get telephone styling/highlighting working in mobile for current iOS and Android devices. It works fine for telephone numbers, but it also treats other numbers the same (makes them clickable links that open up the phone dialer). These include zip codes and other numbers that should not be treated as phone numbers. I am aware that you can disable this functionality completely using the meta tag below:
<meta name="format-detection" content="telephone=no">
However, I want the functionality, just ONLY on phone numbers.
I also am aware that you can disable this and then add links around all phone numbers using "tel:x-xxx-xxx-xxxx", but that seems really tedious and I was hoping to find a better solution (if there is one).
The telephone number recognition is rather primitive and even erroneous, so it is perhaps best switched off, using the method mentioned. For example, the Android 4 browser does not recognize my phone number in the standard international format (it ignores the country prefix and operator code, when spaces are used).
But if you wish to make use of it and still switch it off for other numeric strings, then the following observation might be useful: The Android browser seems to treat a sequence of seven or more digits (e.g., 1234567) as a phone number, if a single space character intervenes. It does not work that way if there is no space (1234567) or if there is more than one space (1 234 567) or if there is an intervening hyphen (123-4567). A no-break space is not taken as a space, so the following would not be recognized: 123 4567.
I’m afraid this is not consistent across browsers that have such features.
I found that the best solution (for me) is to keep this enabled, by not having the meta tag, and just manually fixing the "mistaken links" that are created. Since I only care about supporting iOS and Android, the current versions at that, it was easiest to go through and fix the few numbers that were being linked as phone numbers. I tried #Jukka's suggestion with but found that it added the undesired space, so I found that (soft hyphen) was the best route to go.
Example:
If you have any kind of account number that is 7+ numbers long, it will be considered a phone number.
1234567 - Appears as a phone number
1234567 - Does not appear as a phone number
Note that these were only tested in current iOS and Android operating systems.
I am trying to read a long text from the sdcard to an edittext in Android.
On almost all devices this works very well, except for some samsung devices. When I try to read anything over 10kb the string I read it too gets the whole file. When I try to add this to the edittext its cut off at 10kb. Even if I put it in a loop trying to add a little bit at the time with append it still doesn't add more than 10kb.
On every phone I have tried this works, on HTCs, Sony Ericssons, the nexus phones, but none of the Galaxy S... phone can do it.
Has this happened to anyone else?
Is there a workaround?
10 minutes after posting this question for the 20th time on the web without any answers I find it myself!
In your layout file, in the EditText, add android:maxLength="some high value" and it works!
Interesting that most other devices don't come with a limit while some Samsung phones does for the edittext!
I have a link that looks something like:
Call Support
This link works perfectly fine when using an iOS device. When clicking the link while on Android however the phone attempts to dial 1234567890 (the number without the extension). What is the proper way to do this so that it will work across devices
This appears to be a known bug/issue which may be due to the lack of standards around this feature, as comma,'W','P' are all specific implementations which could change as the Manufacturer may switch out the standard dialer for their own.
http://code.google.com/p/android/issues/detail?id=13684
Try commas instead of 'p' for the pauses. I believe Android's pause character is a comma.