Check if android php

Android Detection with JavaScript or PHP

I’ve noticed that two of my blog posts continue to get more popular each week: iPad Detection with JavaScript or PHP and iPhone and iPad detection with JavaScript or PHP. What’s obvious is that Android development is a hot topic that will only grow. Here are a few methods by which you can detect iOS’ main competitor: Android.

The JavaScript

Searching the user agent string for «Android» is the quickest method:

The PHP

Again, we’ll use PHP’s strstr function to search for Android in the user agent:

Bonus! .htaccess Detection

We can even use .htaccess directives to detect and react to Android devices!

And there you have it: three different Android device detection! Have fun with your mobile development!

Recent Features

9 Mind-Blowing WebGL Demos

Interview with a Pornhub Web Developer

Incredible Demos

Create Keyboard Shortcuts with Mousetrap

pointer Media Query

Discussion

Very neat solution! 😀 I love the detection via .htaccess. Thanks a lot!

Depending on how you have your site setup, you may also want to detect that it’s not already at the android address.

Would be useful if you are just theme switching, instead of going to a completely different website.

Here you go, swap out the stylesheets: http://codesnipp.it/code/1103

Very nice. However, the PHP solution is slightly flawed. Strstr() returns the position at which the “needle” was found, or boolean false if it’s not found at all. If “Android” was found at the very beginning of the string, it would return 0, which evaluates to false. This is obviously incorrect. The solution is to make a typed check.

Also, it might be a good idea to use stristr() , for case insensitivity.

Nice tip. However, you might wanna use stripos() since it’s faster.

Updated guys. Android never appears at the beginning of the UA strings, but it’s good to keep good practices.

Absolutely fantastic, David! Keep up with the good work. Thank you for sharing!

Very nice article!

For a detailed detection with php check out the tera-wurfl project.
I’m using it in my projects to detect all mobile devices.

There are a lot of people who are against user agent detection (preferring something more universal such as window size detection with CSS media queries, for example).

However, I think there’s still a place for it if you architect your site properly. You’re never going to detect the string “Android” in a non-Android device, for example.

As long as there’s a fallback for when no “sure-fire” match is made, I don’t see why we can’t add UA detection as an enhancement to our sites, as long as we ensure no false positives and that the experience isn’t broken by detecting UA.

(also worth noting: people should always have the option to switch to “full/standard” website; if they feel like swiping and zooming around, let them!)

Nice post but why should you deliver an android optimized page for somebody using an android tablet with a screen size just like the iPad?

One example: you want to showcase a store button for Google Play to your Android users, and not show an iTunes button.

I agree with Andi. The Tera-WURFL project is the way to go. the amount of detail you can get from each device is simply amazing. so much more than user agents and window size, but playback capabilities, versions, etc.

Nice but I think you shouldn’t use browser but feature detection. It might be possible that users won’t use the android stock browser and also change the user agent to iPhone/iPad or desktop PC (Firefox or IE).

I’m open to suggestions for feature detection on the client side. What would you recommend?

User agent sniffing must die. Nice job advocating this bad practice.

Thank you so much Mathias!

If you don’t want people to know your user agent, then don’t tell them your user agent. That’s like complaining about davidwalsh.com publishing the comment you just willfully posted.

Android’s dev blog points out that simply looking for “Android” in the UA might cause you to serve a mobile version of the site to a large-form-factor Android device.

When will if(isAndroid) evaluate to true in your examples?

Almost always (-1 anyone?)!! Badly implemented bad practice!

Top Stuff David. As an aside, you can use a service like http://www.handsetdetection.com to do Android detection as well. Handset Detection can also tell the difference between tablets & handsets – which can be handy for redirection. (disclaimer : I work there).

To allow visitors to go from your mobile site back to your standard site check the http_referrer. If the referrer is your mobile site then disable the check. 🙂

Thanks for sharing! Just what I needed 🙂

Thanks for the code! What those ‘bad practice’ nay-sayers are missing is that many companies have mobile versions of their websites which need to detect mobile browsers.

No, the “naysayers” are likely not in that unfortunate group (those that have painted themselves into a corner with bloated GP libraries and other poor practices).

And they do not “need” to detect any such thing. Think.

Guys, this is not a good way to serve an alternate site for mobile. It doesn’t matter what the name or user agent of the device is. What matters is if the device has the capabilities to perform the things you need it to do.

If a new mobile phone gets released tomorrow that does everything an Android can do, it should see your mobile website too no matter what user agent it has.

For a better solution see modernizr. http://www.modernizr.com/

More like see Media Queries. 😉

Browser sniffing is a stupid, error-prone and reviled practice, “backed” by a decade of failures. Doing it on the server side is completely clueless as you could very well be talking to a proxy.

And what does the string “Android” imply? Absolutely nothing, not even that the screen is small (use media queries to detect that).

Do not use this code (or code that resembles it) under any circumstances.

Every situation is different, and to say a method is “Stupid” because it is not optimal for your situation is, well, Stupid!

Grow up and think outside of your own circumstances, for everyone’s sake 😉

David, I’m not agree with your comment at all… first of all MediaQueries are great for size(width|height) detection, orientation in mobile browsers that support, aspect-ratio (not very used) and some more stuff like the media (screen|print|etc).

Also, mobile browsers has there own limits that media-query cannot detect, for example iOS has a limited way to read fixed elements, but can be used with caution, android browser has a lot of other limitations, and are a lot of display formats as are a lot of display androids, so you can’t judge if is an android from a MediaQueries .

Something more, MediaQueries could look nice when you want to make the same webpage and mobilepage, but even if you see less content and aside stuff stay hidden, are loaded… so the page has a lot of extra content to load, that is not good either.

Maybe you don’t have the enough experience working with mobile development and repeat something you read in other post, if that is true, be more carefuly to what you say, be sure of your knowledge and never judge the others knowledge… you can say “I don’t share it”, no “It’s stupid” , for your own good =)

The navigator.userAgent value can not determine whether or not it is an android tablet, or an android smartphone. Detecting window.innerHeight or screen.height won’t help either as HD phones have similar resolutions to non-HD tablets!

Is there a better solution.

I need to forward the user to the mobile site when they are on a smartphone, while tablet users would see the normal “desktop” version of the site.

If you use the meta tag viewport, will help in all of the devices that are able to handle with the information, to specify the width that your page should be rendered and other stuff.

That will be applied for any display size.

Research a little more about this and the device-pixel-ratio css property.

I hope this could be helpful

A good read about using media queries to detect device/browser:

They aren’t always as reliable as preached.

I will also point out that before completing this post, I checked jQuery Mobile, Sencha Touch, Phone Gap, etc. They all appear to use UA sniffs. I’ve also not yet been provided a better solution by anyone. I’m more than receptive to receiving one.

To counter the older post nay-saying media queries I’ll point to a newer one promoting them: http://www.html5rocks.com/mobile/mobifying.html

Also, the compat tables referenced by the cloudfour article are

2yrs old. Media queries should work great for Android devices now.

FWIW, the article referenced–the one I wrote–was written on August 3, 2010, not two years ago. The compat tables referenced were tests conducted on real devices during the period of August 1-3 of last year.

Files downloading for display:none img tags is still an issue on iOS. Hence the responsive images js code that the Filament Group has developed for the Boston Globe project they are doing with Ethan Marcotte:
https://github.com/filamentgroup/Responsive-Images

FWIW, most major sites delivering mobile optimized content are still using some aspect of server-side detection–usually in conjunction with client-side feature detection. I know from conversations with Google that they do this and Facebook has been very open about their use of device detection:
http://www.facebook.com/notes/facebook-engineering/crowdsourcing-mobile-device-capabilities/441195668919
http://www.facebook.com/note.php?note_id=10150122073713920

I echo the comments of those who note the specific requirements of a project or product–particularly what devices you need to support–may necessitate different tools. Like most things, it depends.

You should also note that Google/Facebook have gobs of devs to monitor and tweak their UA sniffs when new browsers/devices come out.

As I’ve said before, UA sniffing should be a last resort not a knee-jerk first.

Just stumbled back on this post and your response. I had forgotten about the link to PPK’s tables. I thought you were referring to my tests of mediaqueries, not the link. My mistake.

Источник

Connecting PHP with Android check if value exists in Mysql Database

First of all my php script:

So I check if the name already exists. If yes then is the «success» equals to 2 and if not then is it equals to 0 and the row should be updated. But I get an Error in Android. If the name don’t already exists, it works fine, but if the value exists then the app crashed.. Here is the Async-Task class from Android:

Answers

As an alternative to === and !== , you can also use in_array :

Problem

HttpURLConnection has no JavaScript support, but a needed cookie is generated using JavaScript.

fails, because the cookie __test is missing.

Fix

From a first glance at the JavaScript source the cookie seems to be constant for a given url, so it might be enough to set for a constant cookie:

Alternative: Using a WebView we can grab the cookie, so this is the preferable approach, since it will not break, if the cookie changes and it is not much of a time delay:

and set it as in above example:

Output in logcat

where exactly do i need to place the php file

You need to place PHP file in server. (You can use localhost i.e., your machine but for devices outside you need to keep it on a webserver which you need to purchase a domain and hosting services.)

where and how i need to create the php file.

You can create a PHP file in you machine itself. Its as simple as creating a text file but with an extension of .php . Using a wamp on windows (LAMP for linux)you can test it. It has a MySQL in it. LAMP and WAMP will have apache server by default.

Soon after you are finished with writing you php code and testing you can transfer the files through FTP into your webserver. Now to configure the MySQL database you can actually use a control panel at the webserver.

You need to use URL for android application to link the PHP files in turn these PHP files interact with MysQL. for a login lets think like you have created a php file as login.php. On your localhost you can refer it to as http://localhost/myapp/login.php If you need to get it on a webserver which you purchase then you URL will have http://www.yourwebsite.com/myapp/login.php . note that myapp is just a folder where you have uploaded your php files.

Now its just a way by which you can actually have a PHP and MySQL for you android application. I think that tutorials have taught you about using php and mysql connections. For Data exchange you need to know about XML or JSON I think tutorials followed had given you an introduction about it.

You even have a plugin for eclipse to work with php. Just get a help over internet on how to install it. This video might help you.

Источник

Build Your First PHP for Android Application

Операционная система Android повергла рынок сматрфонов в шок :). В отличии от компании Apple, которая предъявляет достаточно строгие требования к разработчикам, которые хотят выставлять свои приложения в iPhone App Store, Google создал платформу Android открытой (в оригинале wide open). В настоящее время вы можете писать приложения PHP. Парни из Irontech создали необходимое, и используя Scripting Layer для Android (SL4A), вы можете создавать на PHP приложения для Android.

Нет!
В этой статье я расскажу как установить, настроить и использовать PHP для Android и SL4A, также мы увидим демо приложения и вы получите первый опыт разработки приложений для Android на PHP.

Установка PHP для Android

Для установки PHP для Android, у вас должен быть телефон или эмулятор поддерживающий Android версии 1.5 или больше, также в настройках установки приложений, должна стоять галочка на установке приложений из неизвестных источников. После всего этого, просто установите два пакета SL4A environment и PHP for Android APK.

Установка SL4A достаточно проста, однако после установки пакета PHP for Android application, необходимо запустить его и нажать «install» для полной установки(В процессе установки программа скачивает где-то около 2 МБ). Если у вас появились проблемы с установкой, то есть видео-демонстрация на Vimeo((или здесь)).

Настройка среды разработки PHP для Android

Если вы установили PHP для Android, теоретически, вы можете писать приложения на своем телефоне. Но с практической точки зрения, это не будет хорошей идеей. То что вы должны сделать это скачать Android SDK, установить эмулятор и начать писать код, используя ваш любимый редактор.

После скачивания SDK, разархивируйте содержимое, запустите приложение Android, находящееся в каталоге tools, и установите эмулятор. В меню Android SDK and AVD Manager, выберите Virtual Devices и нажмите на кнопку New. Назовите ваш эмулятор (например «Droid2») и выберите Android 2.2. Введите 10 МБ в качестве размера SD Card и нажмите Create AVD.

Теперь у вас есть настроенный эмулятор, нажмите кнопочку Start. Здесь возникает некоторая сложность, вы не можете просто скопировать файлы на виртуальное устройство, которое только что создали. Вам необходимо настроить форвардинг портов (port forwarding) и поместить ваш PHP-скрипт на виртуальное устройство, используя программу под названием adb, которая является частью Android SDK. Она также находится в каталоге tools.

Далее вы запустите сервер на вашем виртуальном устройстве, соединитесь с сервером для передачи вашего скрипта. Следующие шаги помогут вам запустить все на столько быстро на сколько это возможно. (Вы можете прочитать полную документацию по этому процессу здесь).

На вашем запущенном виртуальном устройстве перейдите на экран Applications и нажмите SL4A.
# на экране SL4A, нажмите кнопочку Menu, выберите View и выберите Interpreters.
# Нажмите Menu снова, выберите Start Server и выберите Private.
# Опустите область уведомлений (Android notification bar) вниз и вы увидите Службу SL4A. (Нажмите на службу и запишите номер порта, который прослушивает ваш сервер, например 47000.)
# Откройте командную строку и установите форвардинг портов, используя команду adb. Например, введите команду «adb forward tcp:9999 tcp:47000» (замените 47000 на номер вашего порта).
# Установите переменную окружения AP_PORT. На UNIX или Mac, запустите «export AP_PORT=9999». На Windows «set AP_PORT=9999».
# Для теста работы эмулятора запустите «run adb push my_script.php /sdcard/sl4a/scripts» (замените my_script.php на название вашего скрипта).

Вы также можете работать с реальным телефоном. Следуйте теми же шагами, что и с эмулятором. Чтобы облегчить процесс установите переменную окружения ANDROID_HOME, которая будет указывать на расположение вашего Android SDK и добавьте путь к каталогу tools в список путей (что-то я не особо понял как это сделать на телефоне, если читатели знают, то пусть напишут в комментариях)

Создание Android приложений на PHP

Написание приложений на PHP очень легкий процесс после того как вы настроили все что описано выше. Единственно что стоит отметить, что версия PHP для Android очень урезана. В вашем распоряжении будут основные функции PHP и поддержка JSON. А если же вы являетесь разработчиком Android, который хорошо знаком с Java фреймворком для Android, вы заметите что Scripting Layer для Android не обеспечивает доступ ко всем компонентам, которые бы вы получили, используя для разработки Java (будем надеятся что это только пока).

То что обеспечивает SL4A — это только фасад к подмножеству Android API. (Полный список методов, обеспечиваемых SL4A, доступен тут ) В чем же прикол PHP для Android — вы можете легко разрабатывать приложени е и видеть его работу, написав всего лишь несколько строк кода. Давайте рассмотрим приложение, которое работает с котировками, которое занимает меньше 60 строк кода.

1. ‘QUOTE_SERVER’ , ‘http://quoter.take88.com/?ticker=%s’ );
2. require_once( «Android.php» );
3. $droid = new Android();
4. $action = ‘get_tickers’ ;
5. $tickers = » ;
6. while (TRUE) <
7. switch ($action) <
8. case ‘quote’ :
9. $droid->dialogCreateSpinnerProgress( «Querying stock information server . » , «Please wait» );
10. $droid->dialogShow();
11. $quotes = @array_slice(json_decode(file_get_contents(sprintf(QUOTE_SERVER, $tickers))), 0, 3);
12. $droid->vibrate();
13. $droid->dialogDismiss();
14. // Possible data points.
15. // «SYMBOL»,»NAME»,»LAST_TRADE»,»MORE_INFO»,»LAST_TRADE_DATE»,»LAST_TRADE_TIME»,»OPEN»,»DAYS_HIGH»,»DAYS_LOW»,»DIVIDEND_SHARE»,»PE_RATIO»,»52_WEEK_LOW»,»52_WEEK_HIGH»,»VOLUME»
16. $output = » ;
17. for ($i = 0, $cnt = count($quotes); $i «Company: » . $quotes[$i]->NAME . «\n» ;
18. $output .= «Ticker: » . $quotes[$i]->SYMBOL . «\n» ;
19. $output .= «Last trade: $» . $quotes[$i]->LAST_TRADE . «\n» ;
20. $output .= «\n» ;
21. >
22. $output = html_entity_decode($output, ENT_QUOTES, «UTF-8» );
23. // Something is wrong with ‘
24. $output = str_replace( «‘» , «‘» , $output);
25. $droid->dialogCreateAlert( «Your stock quotes» , $output);
26. $droid->dialogSetPositiveButtonText( «Get new quote» );
27. $droid->dialogSetNegativeButtonText( «Exit» );
28. $droid->dialogShow();
29. $response = $droid->dialogGetResponse();
30. if ($response[ ‘result’ ]->which == ‘negative’ ) <
31. $action = «exit» ;
32. > else <
33. $action = ‘get_tickers’ ;
34. >
35. break ;
36. case ‘get_tickers’ :
37. $response = $droid->getInput( «Stock Tickers (max. 3)» , «Enter Tickers.\nSeparate with spaces.» );
38. $tickers = str_replace( ‘ ‘ , ‘+’ , $response[ ‘result’ ]);
39. $droid->vibrate();
40. $action = ‘quote’ ;
41. break ;
42. case ‘exit’ :
43. $droid->exit();
44. exit();
45. break ;
46. >
47. >
48. ?>

* This source code was highlighted with Source Code Highlighter .

Скопируйте и поместите этот код в редактор, сохраните под именем quoter4android.php и загрузите его в эмуляторе. Если эмулятор не запущен, запустите его, настройте форвардинг портови загрузите quoter4android.php, используя adb.

Для запуска приложения в вашем эмуляторе, перейдите на экран приложения, нажмите иконку SL4A и нажмите quoter4android.php.

Для установки quoter4android.php на ваш телефон, вы можете настроить форвардинг портов, но легче соединить телефон с компьютером через USB и скопировать скрипт в каталог sl4a/scripts. Однако для запуска скрипта, необходимо отсоединить его от компьютера, иначе вы не увидите установленные скрипты, а зщатем кликните иконку SL4A.

Заключение

С SL4A и PHP for Android можно сделать много интересных вещей; эта статья всего лишь маленькая демонстрация возможностей. Все эти приложения очень молоды — новая версия SL4A вышла когда я писал эту статью — и в будущем мы будем получать все новые и новые возможности.

Источник