Posts Tagged ‘application’
Security application for your Android phone
Android is a multi-process system, in which each application (and parts of the system) runs in its own process. Most security between applications and the system is enforced at the process level through standard Linux facilities, such as user and group IDs that are assigned to applications. Additional finer-grained security features are provided through a “permission” mechanism that enforces restrictions on the specific operations that a particular process can perform, and per-URI permissions for granting ad-hoc access to specific pieces of data.
Now the question arises that how does this security application works for your cell phone.
A basic Android application has no permissions associated with it, meaning it cannot do anything that would adversely impact the user experience or any data on the device. To make use of protected features of the device, you must include in your AndroidManifest.xml one or more <uses-permission> tags declaring the permissions that your application needs.For example, an application that needs to monitor incoming SMS messages would specify:
<manifest xmlns:android=”http://schemas.android.com/apk/res/android” package=”com.android.app.myapp” > <uses-permission android:name=”android.permission.RECEIVE_SMS” /></manifest>At application install time, permissions requested by the application are granted to it by the package installer, based on checks against the signatures of the applications declaring those permissions and/or interaction with the user.
The permissions provided by the Android system can be found at Manifest Permission. Any application may also define and enforce its own permissions, so this is not a comprehensive list of all possible permissions.
A particular permission may be enforced at a number of places during your program’s operation:
•At the time of a call into the system, to prevent an application from executing certain function.
•When starting an activity, to prevent applications from launching activities of other applications.
•Both sending and receiving broadcasts, to control who can receive your broadcast or who can send a broadcast to you.
•When accessing and operating on a content provider.
•Binding or starting a service.
Declaring and Enforcing Permissions
To enforce your own permissions, you must first declare them in your AndroidManifest.xml using one or more <permission> tag.
This mechanism allows a common capability-style model where user interaction (opening an attachment, selecting a contact from a list, etc) drives ad-hoc granting of fine-grained permission. This can be a key facility for reducing the permissions needed by applications to only those directly related to their behavior.
The granting of fine-grained URI permissions does, however, require some cooperation with the content provider holding those URIs. It is strongly recommended that content providers implement this facility, and declare that they support it through the android:grantUriPermissions attribute or <grant-uri-permissions> tag.
Mr. P. Gomez, a well known name in the world of technology who has made significant contributions in rendering hacking tips and Mobile Phone Hacking. He is currently working under the supervision of well reputed big companies.
Nokia E7
Nokia business phones were originally sold under the ‘Communicator’ series and for most of the time, they were not well-received because those phones were too bulky and pricey, despite offering some of the best features of its time. However, with the recent success of the E series, Nokia seems to have found a formula to make the high-end business phones a success too, and armed with that success comes the new Nokia E7.
The Nokia E7 does not have the two keyboards like the Communicator models or the full QWERTY keyboard that took up most of the space in the previous E series phones like E72 and so on. Instead, the Nokia E7 offers a 4 inch touch screen display and the full QWERTY keyboard is hidden underneath it. The keyboard slides out in the landscape mode should you have the need to use it. Otherwise, the phone is pretty much dominated with the huge screen that has the AMOLED technology, along with a few hardware buttons to activate the camera and the volume keys.
The camera, which can be activated by the dedicated camera key in the side of the phone, is an 8 megapixel one and it can shoot videos in great details because it supports 720p HD video recording. The phone features 3G and Wi-Fi connectivity for faster internet browsing. This is particularly useful when you want to watch the National Geographic or CNN channels using the phone’s WebTV application. The phone also lets you watch YouTube videos directly without any other application. It also has an internal GPS receiver that offers free lifetime navigation with Nokia’s very own Ovi Maps.
The price for all these features is a meagre ?584.99 when the phone will be launched in the UK early next year with some very competitive phone deals.
Public transport navigation for Windows Mobile
CityAdvisor is a navigation platform to guide you traveling in the city.
CityAdvisor is a navigation platform to guide you traveling in the city.
This project contains:
- a searching application running on Windows Mobile
- a resource website http://www.cityadvisor.net to assembly existing maps and documents
- a MapCreator to let users create their own map
World Cup 2010 app for Windows Mobile phones
This is new small World Cup 2010 application for Windows Mobile, which has been entirely developed using the Compact Framework. This app requires a touch-screen device with Windows Mobile and the Microsoft .Net Compact Framework 3.5 installed on the device.
