Develop Reference

Mobile telephone detection creates links on other numbers, such as zip codes

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.

HTML troubles in standard Email app on Android tablet

I use HTML coding in email marketing.
Nowadays It is important to nice represent email offers both in standard and mobile version.
So, exist the certain tricks which help you to made your emails looks nice on mobile devices (without bugs and gaps).
For example, the most famous trouble is the tearing of content of email letter due to changing of text size by mobile device.
To ban this feature of device I use next css-trick:
#media only screen and (max-width: 480px) {
body {
-webkit-text-size-adjust:none;
}
This trick works fine if I check my email in mobile device browser.
But it is not work if I check it in standart app for viewing emails.
For example here are the screenshots made from Android Tablet PC in standart "E-mail" app (version 4.1):
You can see, that the content is torn because of the incorrect text size.
How to avoid it?

Firstly, using media queries is not 100% supported in all email clients (Gmail for example). Fortunately, this doesn't need to be in a media query.
A webkit specific declaration will only work in webkit based clients (mac for example). See the htmlboilerplate (line 35), you could also add the ms prefix:
-webkit-text-size-adjust:100%; -ms-text-size-adjust:100%;
I doubt this will address your Android tablet however. This may be something unavoidable, unless adding !important to your font-size can do the trick.

Dipaly farsi text in android webview (for phones not supporting farsi)

In farsi letters are attach together to form writing scripts. However when I save HTML pages using "UTF-8" or "Windows-1256" encdoings, and try to display them using webview in android, letters are diplayed seperately and in left-to-right direction (instead of RTL).
I should notice that this case is not happening in phones supporting farsi.
Correct form should be like this (snapshot from phone supporting farsi):
Bad-formed text happens in phones not supporing farsi (Persian):
It should be noticed i've used persian font in both cases.
I also see some solutions for normal Strings in java which changes character on by one in this
question
My question: Can i fix this cases (or it should be fix by phone vendors)? if possible what is solution?

I hit this bug a lot when I was doing keyboards. The problem is that the build in canvas.drawText function in Android didn't support RTL languages. There was a patch for it, but it wasn't part of the default build of Android. So only models going out to those parts of the world that used it tended to have it. Unfortunately I know of no way to test whether it has the patch. And if it doesn't, there's no way to fix it. You could try reversing the text, but then you'd break devices which did have the patch.
Long story short- there is no way to fix it. However, I'd be shocked if Google hasn't picked up the patch in mainline by now (it existed back in the 2.2 days), so its a shrinking number of phones effected.

You can try making html with reverse font sequence! just write a windows app to get font and deliver reverse one, and use it in your android device

Why is this android device enlarging text?

The website is tavistockrestaurants.com. We are trying to make this design work well in popular mobile devices. A particular android device seems to be enlarging the text, and I am unsure why. This causes the "contact" link in the top to wrap, and causes unecessary line breaks throughout our website. Notice the form is getting pushed below the images in this screenshot? It's supposed to have white space on the bottom!
We do have -webkit-text-size-adjust: none in place for all elements (using asterisk *). Is there an android equivelant? Has anyone experienced this on any android devices?
This behavior does not occur on all android devices. We have only seen this on Android 4.x, but I cannot reproduce it with my android 4.0 emulator.
What it currently looks like:
What it should look like:
(I do not have the specific device model used in the screen cap)

In CSS, pixels are not pixels.
Or rather, 1 CSS pixel does not always map to 1 hardware pixel. On certain high-DPI Android devices, one CSS pixel can be 1.5 or 2 hardware pixels. The Opera guys have a good overview on the topic.

Samuels answer is correct.
There is a workaround though. You can target specific devices and change the styles for that device specifically using classes or stylesheets. If you are using PHP you should be able to parse the "User-Agent" and determine which device the client is using and add a class to the body tag (and use that class to target that specific device in your CSS).
There are also services that will allow you to send users to a different version of the site depending on the device they are using. Here is a site that does the work for you.
There may also be device specific CSS being generated on loading the page. Using a CSS reset may also help your site be more cross-browser compatible.

Creating Android UI like HTC Sense

Do you have any idea what's the starting point to develop an UI for Android OS, similar with HTC SenseUI ?
Can I create that on top of Android or I need to get the Android source code ?
Thank you.
Florin Matincă

You'd need to modify the Android OS to some extent, but since Android is open source, that's not a problem.
The problem is getting it installed on phones - if you've noticed, the only companies that have custom UIs are also phone manufacturers, so they can just ship their phones with it installed. Also, if a new version of Android comes out, you'd need to get the new source, and modify most of it again.
Distribution would be a serious problem...

HTC Sense consist of a variety of functions.
Some like the Lock Screen can be implemented as normal programs. The start screen for programs can as well.
The systems setting for example can't be easily replaced without going into the android source code.

I have to disagree with xil3, there are some realy popular home screen replacements out there not restricted to a certain brand.
ADW.Launcher
LauncherPro
HelixLauncher
HelixLauncher2
All four are available on market place and therefor the distribution is simple.
HelixLauncher (and 2) are based on the Launcher from android itself, for which the sources are available as a git repository. This means you could use these sources to start your own Home Screen replacement.
So have fun!