Showing posts with label android. Show all posts
Showing posts with label android. Show all posts

Friday 17 May 2013

List of Tablet and Smartphone Resolutions and Screen Sizes


Manufacturer
Model
Screen Size
Resolution
Type
Acer
Iconia Tab
10.1″
1280×800
Tablet
Amazon
Kindle Fire
7″
1024×600
Tablet
Apple
iPad
9.7″
1024×768
Tablet
Apple
iPad 2
9.7″
1024×768
Tablet
Apple
iPad 3
9.7″
2048×1536
Tablet
Apple
iPhone 3GS
3.5″
480×320
Smartphone
Apple
iPhone 4S
3.5″
960×640
Smartphone
Apple
iPhone 5
4″
640×1136
Smartphone
ASUS
Transformer TF101
10.1″
1280×800
Tablet
ASUS
Transformer Prime TF201
10.1″
1280×800
Tablet
Barnes & Noble
NOOK
7″
1024×600
Tablet
BlackBerry
Playbook
7″
1024×600
Tablet
BlackBerry
Torch 9800
3.2″
480×360
Smartphone
BlackBerry
Torch 9810
3.2″
640×480
Smartphone
Colby
Kyros
7″
800×480
Tablet
HP
TouchPad
9.7″
768×1024
Tablet
HTC
Amaze 4G
4.3″
960×540
Smartphone
HTC
Evo 3D
4.3″
960×540
Smartphone
HTC
Flyer
7″
1024×600
Tablet
HTC
Sensation 4G
4.3″
960×540
Smartphone
HTC
Thunderbolt
4.3″
480×800
Smartphone
Lenovo
IdeaPad A1
7″
1024×600
Tablet
Lenovo
ThinkPad
10.1″
1280×800
Tablet
LG
G2x 4G
4″
800×400
Smartphone
LG
G-Slate
8.9″
768×1280
Tablet
Motorola
Droid BIONIC
4.3″
540×960
Smartphone
Motorola
Droid RAZR
4.3″
540×960
Smartphone
Motorola
Droid Xyboard 10.1
10.1″
1280×800
Tablet
Motorola
Xoom
10.1″
1280×800
Tablet
Nokia
Lumia 900
4.3″
480×800
Smartphone
Samsung
Brightside
3.1″
240×320
Smartphone
Samsung
Epic 4G Touch
4.52″
800×480
Smartphone
Samsung
Exhibit 4G
3.5″
480×800
Smartphone
Samsung
Focus Flash
3.7″
480×800
Smartphone
Samsung
Galaxy S 4G
4″
480×800
Smartphone
Samsung
Galaxy S II
4.52″
800×480
Smartphone
Samsung
Galaxy S III
4.8″
1280×720
Smartphone
Samsung
Galaxy Tab
7″
1024×600
Tablet
Samsung
Galaxy Tab 7.7
7.7″
1280×800
Tablet
Samsung
Galaxy Tab 10.1
10.1″
1280×800
Tablet
Samsung
Gravity Smart
3.2″
320×480
Smartphone
Samsung
Sidekick 4G
3.5″
800×480
Smartphone
Sony
Tablet S
9.4″
1280×800
Tablet
T-Mobile
MyTouch 4G Slide
3.8″
800×480
Smartphone
T-Mobile
SpringBoard
7″
1280×800
Tablet
Toshiba
Thrive
10.1″
1280×800
Tablet


Thursday 9 May 2013

Procedure To Root Samsung Galaxy SII i9100



Points to be taken care of before Proceeding ahead:
  • Warranty will be void by rooting the device but you can get it back by unrooting the phone.
  • Download all needed Tools/software.
  • You may loss device data, so make a backup of all the data like messages, call history, pictures etc before rooting process.
  • Battery of the phone should be charged properly at least to the half level.
  • The updated USB driver of device should be installed on system to communicate properly with the device.
  • Samsung Galaxy SII should be updated to the latest firmware XWKDD.
  • Save the APN Setting, it will be needed after the root process to surf the internet again.

Tools Needed:

1.      ODIN Downloader (Download it from here)
2.      Download SuperOneClick
3.      XWKDD Kernel (Don’t extract it after download, it will use in the Odin process)
4.      USB Data Cable
5.      Samsung’s KIES 2.0 

Procedure:

Step 1: Make sure that you have downloaded and installed all the needed software. Now, set device in USB debugging mode: Settings ->Applications -> Development -> USB debugging.

Step 2: Reboot your device in the download session mode. To get enter in the download mode of Samsung Galaxy SII, switched off the device and turn it on again by holding Volume down button + Home button and Power button simultaneously. You will surely reach to the download mode. This will show screen as mentioned below in picture, on your phone screen.


Step 3: Open ODIN Downloader and install it on your pc.

Step 4: Now, using USB Cable connect the device to computer and keep Odin open. Wait for few seconds then ODIN will notify that the device is connected to the computer. Select the checkboxes next to “Auto reboot” and “F. Reset Time” and kept default else options. After this, press “PDA”  Button and select the XWKDD_insecure.tar file which you have downloaded on your pc already. Now Press “Start” button, after pressing the start button, ODIN will flash the kernel and after flashing, it will reboot phone.. Do not disconnect the device from PC while rebooting.


Step 5: Once the device has been restarted, Open SuperOneClick and press the “Root” tab and restart the device again. Now you have successfully rooted your Samsung Galaxy SII device. 


Types of Mobile Application



Mobile Application 'Types' is quite confusing topic. Here is the description of Application 'Types'

1. Browser Access: The applications which we are accessing through native browser. Ex : m.yahoo.com, www.google.com, m.redbus.in
2. Hybrid Apps: We are installing the application in our device and for the functioning of that particular application internet is required. Ex : Social Networking Apps(Facebook, Twitter), Instant Messengers(Skype), E-Commerce(Flipkart), Internet Speed Testing(Speedtest)
3. Hybrid Apps: We are installing the application in our device and if required we are connecting it to internet also. Ex : Few games in which we can play alone and we go online too for playing with different players(multi player). And any medical apps where u want to keep a track record of your health and later want to share with your friends or doctor via internet.
4. Native Apps : The applications which we are installing in our device. Ex : Reminders, Few Games etc.

It can be further understand by the communication medium of the apps:

Native Apps- Which can be installed in the devices and the app does not need any data transfer to the server. With out network these apps work in the device. The data about the app will be stored in the device itself. Example Gaming applications. Here the device memory and configuration is very important as the app completely dependent on this.

Client Server apps- They can be called Semi native apps. Here the app can be installed in the device. But the with out a network it cannot be launched. Because It gets the data from the server. With out the data the app will not proceed further. Example Commercial apps like Banking app. Here you basically can see the form UI but the all the data comes from the server. So the device memory is partially dependent just to install the app as the data comes from the server for every service call.

Mobile Web applications.- They can be called as Mobile browser apps as these are not installed in the device. these can be accessed using the mobile browser by hitting the Url of the web. Here the device memory size is not all important as neither of the from or the app data is stored in the device. It is Completely dependent on the quality of the browser. Every thing comes from the server and rendered in the browser when you hit the url.

Comparison between Native Apps, Hybrid Apps and Mobile Apps:

1.Skills/tools needed for cross-platform apps:
Native: Objective-C, Java, C, C++, C#, VB.net
Hybrid:HTML, CSS, Javascript, Mobile development framework (like PhoneGap)
Mobile web:HTML, CSS, Javascript

2.Distribution:
Native:App Store/Market
Hybrid:App Store/Market
Mobile web:Internet

3.Development Speed:
Native:Slow
Hybrid:Moderate
Mobile web:Fast

4.Number of applications needed to reach major smartphone platforms
Native: 4
Hybrid: 1
Mobile web: 1

5.Ongoing application maintenance
Native: Difficult
Hybrid: Moderate
Mobile web: Low

6.Device access
Native: Full access(Camera, microphone, GPS, gyroscope, accelerometer, file upload, etc
Hybrid: Full access(Camera, microphone, GPS, gyroscope, accelerometer, file upload, etc
Mobile web: Partial access(GPS, gyroscope, accelerometer, file upload

7. Advantages
Native: Lets you create apps with rich user interfaces and/or heavy graphics
Hybrid: Combines the development speed of mobile web apps with the device access and app store distribution of native apps
Mobile web: Offers fast development, simple maintenance, and full application portability. One mobile web app works on any platform.

8. Disadvantages
Native: Development Time, Development Cost, Ongoing Maintenance, No portability (apps cannot be used on other platforms)
Hybrid: handle heavy graphics, Requires familiarity with a mobile framework
Mobile web: handle heavy graphics, Can't access camera or microphone

Tuesday 23 April 2013

Android Architecture



Linux Kernel
Android OS is built on top of the Linux 2.6 Kernel
–Linux Core functionality
•Memory management
•Process management
•Networking
•Security settings
–Hardware drivers

Android’s native libraries
–Libc: c standard lib.
–SSL: Secure Socket Layer
–SGL: 2D image engine
–OpenGL|ES: 3D image engine
–Media Framework: media codecs
–SQLite: Database engine
–WebKit: Kernel of web browser
–FreeType: Bitmap and Vector
–SufraceManager: Compose window manager with off-screen buffering.

Android Runtime
Core Libraries
Provides the functionality of the JAVA Programming Language
Dalvik VM
A type of Java Virtual Machine
Register based (not stack machine like JVM)
Optimization for low memory requirements
Executes .dex (Dalvik-Executable) files instead of .class
DX tool converts classes to .dex format

Application Framework
•The blocks that our applications directly interact with.
•Important blocks:
–Activity Manager: Manages the activity life cycle of applications
–Content Providers: Manage the data sharing between applications
–Telephony Manager: Manages all voice calls. We use telephony manager if we want to access voice calls in our application.
–Location Manager: Location management, using GPS or cell tower
–Resource Manager: Manage the various types of resources we use in our Application

Applications
•This is where our applications are placed.
•Some pre-installed applications:
–SMS client app
–Dialer
–Web browser
–Contact manager
•As developers, we are able to write an app which replaces any existing system app.

History of Android


2001 search service for wireless device
2005
Acquire Android(Andy Rubin: Danger CEO, Development Sidekick of T-Mobile)
Acquire Skia(2D Graphics for mobile device)
Acquire RegWireless(Browser and Email for mobile device)
Move Engineers from PlamSource(Dianne Hackborn, etc…)
2007 Nov 5: Android announced
2007 Nov 12: Android SDK released by OHA
2007 Dec 14: Bug-fix SDK released
2008 Jan 3: Android Developer Challenge I starts accepting submissions
2008 Feb 13: m5-rc15 SDK released
2008 Apr 14: 1788 total submissions for Challenge I
2008 May 12: Top 50 Applications in Challenge I announced
2008 Nov: Android Phone(G1 Phone by HTC/T-mobile)
2008 Nov: Full Source Open
2009 Apr: HTC Magic
2009 July: HTC Hero, Samsung i7500, Android Netbook, Set-top……
2009 Aug: Android Developer Challenge II 

Open Source

Industry
•Software stack open-sourced under Apache 2.0 license
•Source available after first handsets ship
•Anyone will be able to build a system image

Users
•Users have control of their experience
•They control what gets installed
•They choose the defaults

Developer
•Don not need permission to ship an application
•No hidden or privileged framework APIs
•Can integrate, extend and replace existing components