Today I received my 16GB MicroSD to replace my now full 8GB.  Normally to transfer contents it’s quite straightforward – just copy everything to computer then back onto the SD card (or from SD to SD if you’ve got a card reader).  However, if you’ve got a rooted phone running apps2sd (also known as Apps2Ext) then there’s slightly more work involved to make sure that you end up transferring all your apps too.  The method below describes how I managed it, and under that I’ve listed a few alternatives…

Requirements

1. Rooted phone
2. SD card with ext partition
3. ADB installed – how to

source

if [ condition is true ]
then
execute these commands
else
execute those commands
fi

The else clause is optional, but you must end the construct with the fi command. You can also have nested if clauses by using the elif command like this:

if [ condition1 is true ]
then
execute these commands
elif [ condition2 is true ]
then
execute these commands
else
execute those commands
fi

So what kind of conditions can we test for? If you’re dealing with numbers, here are the conditional expressions you can use. In other words, any of these expressions can go inside the brackets on the if or elif statement:

num1 -eq num2 True if num1 equals num2.

num1 -ne num2 True if num1 is not equal to num2.

num1 -lt num2 True if num1 is less than num2.

num1 -gt num2 True if num1 is greater than num2.

num1 -le num2 True if num1 is less than or equal to num2.

num1 -ge num2 True if num1 is greater than or equal to num2.

If you’re comparing character strings, these are the valid conditional expressions:

str1 = str2 True if str1 and str2 are identical.

str1 != str2 True if str1 and str2 are not identical.

-n str1 True if str1 is not null (length is greater than zero).

-z str1 True if str1 is null (length is zero).

You can also test certain file conditions, such as whether or not files exist, the type of file, and so on. Here are the conditional expressions for files:

-f somefile True if somefile exists and is an ordinary file.

-d somefile True if somefile exists and is a directory.

-s somefile True if somefile contains data (the size is not zero).

-r somefile True if somefile is readable.

-w somefile True if somefile is writable.

-x somefile True if somefile is executable.

And finally, here are the logical operators, for performing tests that involve and, or, and not conditions.

cond1 -a cond2 True if both cond1 and cond2 are true.

cond1 -o cond2 True if either cond1 or cond2 is true.

! cond1 True if cond1 is false.

source

else
{
document.getElementById(varoff).style.display = 'none';
document.getElementById(varon).style.display = 'block'
}
}


100 Trying

extended search being performed may take a significant time so a forking proxy must send a 100 Trying response

180 Ringing
181 Call Is Being Forwarded
182 Queued
183 Session Progress

2xx—Successful Responses

200 OK
202 accepted: It Indicates that the request has been understood but actually can’t be processed

3xx—Redirection Responses

300 Multiple Choices
301 Moved Permanently
302 Moved Temporarily
305 Use Proxy
380 Alternative Service

4xx—Client Failure Responses

400 Bad Request
401 Unauthorized (Used only by registrars or user agents. Proxies should use proxy authorization 407)
402 Payment Required (Reserved for future use)
403 Forbidden
404 Not Found (User not found)
405 Method Not Allowed
406 Not Acceptable
407 Proxy Authentication Required
408 Request Timeout (Couldn’t find the user in time)
409 Conflict
410 Gone (The user existed once, but is not available here any more.)
412 Conditional Request Failed
413 Request Entity Too Large
414 Request-URI Too Long
415 Unsupported Media Type
416 Unsupported URI Scheme
417 Unknown Resource-Priority
420 Bad Extension (Bad SIP Protocol Extension used, not understood by the server)
421 Extension Required
422 Session Interval Too Small
423 Interval Too Brief
424 Bad Location Information
428 Use Identity Header
429 Provide Referrer Identity
433 Anonymity Disallowed
436 Bad Identity-Info
437 Unsupported Certificate
438 Invalid Identity Header
480 Temporarily Unavailable
481 Call/Transaction Does Not Exist
482 Loop Detected
483 Too Many Hops
484 Address Incomplete
485 Ambiguous
486 Busy Here
487 Request Terminated
488 Not Acceptable Here
489 Bad Event
491 Request Pending
493 Undecipherable (Could not decrypt S/MIME body part)
494 Security Agreement Required

5xx—Server Failure Responses

500 Server Internal Error
501 Not Implemented: The SIP request method is not implemented here
502 Bad Gateway
503 Service Unavailable
504 Server Time-out
505 Version Not Supported: The server does not support this version of the SIP protocol
513 Message Too Large
580 Precondition Failure

6xx—Global Failure Responses

600 Busy Everywhere
603 Decline
604 Does Not Exist Anywhere
606 Not Acceptable

source

source

Apps on Facebook.com are loaded into a Canvas Page. A Canvas Page is quite literally a blank canvas within Facebook on which to run your app. You populate the Canvas Page by providing a Canvas URL that contains the HTML, JavaScript and CSS that make up your app. When a user requests the Canvas Page, we load the Canvas URL within an iframe on that page. This results in your app being displayed within the standard Facebook chrome.

For example, suppose that you have a web app available at http://www.example.com/canvas. This is your Canvas URL. When you setup your app on Facebook, you must specify a Canvas Page name that is appended to http://apps.facebook.com/. In this example, we will use your_app as the Canvas Page name. When the user navigates to http://apps.facebook.com/your_app in their browser, they will see the contents of http://www.example.com/canvas loaded inside of Facebook.com.

Note that http://www.example.com/canvas cannot forward to another URL via HTTP redirect responses, e.g. response code 301, but has to return the response directly.

source