Nokia XL was proclaimed by Nokia at mobile world congress  earlier this year beside Nokia X and Nokia X+. Nokia XL is currently accessible on companys official on-line store for Rs 11,489 and can be delivered in 5 working days.
The Nokia XL is merely accessible in green color

Image courtesy: Nokia.com

Feature and specification of Nokia XL

The Nokia XL runs on Nokia X software platform version 1.0 that relies on the Android Open Source Project.
This Smartphone also doesnt have access to Google play store .The user might get all apps from the Nokia store or third party developer.
Further all the Google services on this Smartphone are going to be replaced with Microsoft Services.

This Smartphone sports a 5 Mega pixel rear camera with led flash and 2MP front facing camera for video calling,
Connectivity possibility of Nokia XL includes Bluetooth, WiFi. and GPS with AGPS

The Nokia XL Dual SIM comes preloaded with Nokia MixRadio and other Popular apps like Facebook, Twitter, WeChat, Viber, and Skype.BBM, Plants vs. Zombies 2,and Vine.

Nokia XL supports dual SIM (GSM + GSM ) cards with dual standby. It has a 5.0"  WVGA touchscreen display with resolution of 480*800 pixels and provides a pixel density of 187 ppi. The Nokia XL is motivated by 1 GHz dual Core Qualcomm snapdragon S4 processor couple with 768 MB of RAM.
Storage possibility of Nokia XL comes with 4GB of built-in internal storage and it was additionally supported expandable storage up to 32 GB with the assistance of MicroSD card slot.

Feature and Specification of Nokia XL

Name	Nokia XL
Manufacturer	Nokia
Dimensions	141.4 x 77.7 x 10.9 mm
SIM Support	Dual - Micro SIM GSM + GSM
Display	12.7 cm, LCD 187 ppi,Capacitive Multipoint-Touch
Resolution	WVGA (800 x 480)
Connectivity	2G, 3G, Wi-Fi - , GPS, USB WAPI
Video Recording	Yes
Camera	Rear: 5 Mega Pixel with LED flash,
	Front: 2 Mega Pixel 720p
Sensors:	Ambient light sensor, Accelerometer, Proximity, sensor
Camera Feature	Auto exposure,enter weighted auto exposure,Still image editor
	Panorama lens,
Battery	2000 mAh ST: 37 days, TT: 16 h(2G), 13 h(3G)
Processor	Dual-core 1 GHz Qualcomm Snapdragon S4
RAM:	768 MB
Storage:	Internal : 4 GB
	External: Expandable up to 32 GB via microSD
Audio	MP3, AMR-NB, AMR-WB, FLAC, MIDI
Video	H.263, H.264/AVC, MPEG-4
Operating System	Nokia X software platform 1.0
Color	Green
Additional feature	Mobile VPN, Data encryption for device,Device lock password
	Firmware update, Device lock, PIN code, Device lock passcode,
Sales Package:	Nokia XL Dual SIM, Charger AC-20, Battery BN-02 2000 mAh,
	Nokia Stereo Headset WH-108, Quick guide
Price	Rs 14,489

Source: Nokia.com

Read More..

This post is part of Whos at Google I/O, a series of guest blog posts written by developers who are appearing in the Developer Sandbox at Google I/O. Its also cross-posted to the Google Code blog which has similar posts for all sorts of Google developer products.

Mojo Helpdesk from Metadot is an RDBMS-based Rails application for ticket tracking and management that can handle millions of tickets. We are migrating this application to run on Google App Engine (GAE), Java, and Google Web Toolkit (GWT). We were motivated to make this move because of the application’s need for scalability in data management and request handling, the benefits from access to GAE’s services and administrative tools, and GWT’s support for easy development of a rich application front-end.

In this post, we focus on GAE and share some techniques that have been useful in the migration process.

Task failure management

Our application makes heavy use of the Task Queue service, and must detect and manage tasks that are being retried multiple times but aren’t succeeding. To do this, we extended Deferred, which allows easy task definition and deployment. We defined a new Task abstraction, which implements an extended Deferrable and requires that every Task implement an onFailure method. Our extension of Deferred then terminates a Task permanently if it exceeds a threshold on retries, and calls its onFailure method.

This allows permanent task failure to be reliably exposed as an application-level event, and handled appropriately. (Similar techniques could be used to extend the new official Deferred API).

From the existing Mojo Helpdesk: a view of a user’s assigned tickets.

Appengine-mapreduce

Mojo Helpdesk needs to run many types of batch jobs, and appengine-mapreduce is of great utility. However, we often want to map over a filtered subset of Datastore entities, and our map implementations are JDO-based (to enforce consistent application semantics), so we don’t need low-level Entities prefetched.
 So, we made two extensions to the mapper libraries. First, we support the specification of filters on the mapper’s Datastore sharding and fetch queries, so that a job need not iterate over all the entities of a Kind. Second, our mapper fetch does a keys-only Datastore query; only the keys are provided to the map method, then the full data objects are obtained via JDO. These changes let us run large JDO-based mapreduce jobs with much greater efficiency.

Supporting transaction semantics

The Datastore supports transactions only on entities in the same entity group. Often, operations on multiple entities must be performed atomically, but grouping is infeasible due to the contention that would result. We make heavy use of transactional tasks to circumvent this restriction. (If a task is launched within a transaction, it will be run if and only if the transaction commits). A group of activities performed in this manner – the initiating method and its transactional tasks – can be viewed as a “transactional unit” with shared semantics.

We have made this concept explicit by creating a framework to support definition, invocation, and automatic logging of transactional units. (The Task abstraction above is used to identify cases where a transactional task does not succeed). All Datastore-related application actions – both in RPC methods and "offline" activities like mapreduce – use this framework. This approach has helped to make our application robust, by enforcing application-wide consistency in transaction semantics, and in the process, standardizing the events and logging which feed the app’s workflow systems.

From the existing Mojo Helpdesk: a view of the unassigned tickets for a work group.

Entity Design

To support join-like functionality, we can exploit multi-valued Entity properties (list properties) and the query support they provide. For example, a Ticket includes a list of associated Tag IDs, and Tag objects include a list of Ticket IDs they’re used with. This lets us very efficiently fetch, for example, all Tickets tagged with a conjunction of keywords, or any Tags that a set of tickets has in common. (We have found the use of "index entities" to be effective in this context). We also store derived counts and categorizations in order to sidestep Datastore restrictions on query formulation.

These patterns have helped us build an app whose components run efficiently and robustly, interacting in a loosely coupled manner.

Come see Mojo Helpdesk in the Developer Sandbox at Google I/O on May 10-11.

Amy (@amygdala) has recently co-authored (with Daniel Guermeur) a book on Google App Engine and GWT application development. She has worked at several startups, in academia, and in industrial R&D labs; consults and does technical training and course development in web technologies; and is a contributor to the @thinkupapp open source project.

Posted by Scott Knaster, Editor

Read More..

So we already knew that 2014 was the year of the wearables, I mean at CES that’s pretty much all we saw. Samsung launched the Galaxy Gear last year at IFA alongside the Galaxy Note 3 and Galaxy Note 10.1 2014 Edition. They are said to be launching the next iteration of Galaxy Gear alongside the Galaxy S5 in March as well. Now there’s a new rumor coming out of The Korea Times, stating that Samsung will unveil Gear Glass at IFA (which is in Berlin every year) this September. Which tells us that it’s likely to be announced alongside the Galaxy Note 4.

This report is stating that the smart glasses are tentatively called “Galaxy Glass”, which wouldn’t surprise me if that were the name, as Samsung loves to put the Galaxy name in front of everything, but then they have spent a fortune marketing that name, so it makes sense. However, a Samsung official has recently stated that they aren’t interested in smart glass right now, but rather to make wearable devices that “provide information at a glance without turning the people using them into cyborgs.” However this report and the recent patent application Samsung filed for smart glasses, suggests that the Korean manufacturer might be launching some smart glasses pretty soon.

Sammobile is citing an unnamed official from Samsung, who stated “the new smart glass to be introduced by Samsung is a new concept of wearable device that can be lead to an exciting culture of communication. The smart glass will present our aim to lead the new market with proven capability. Wearable devices can’t generate profits immediately. Steady releases of devices are showing our firm commitment as leader in new markets.” The report from The Korea Times also suggests that the “Galaxy Glass” will have similar functionality to the Galaxy Gear. In the fact that you’ll be able to view notifications (hopefully you’ll be able to act on them too), take phone calls, take pictures as well as listen to music.

The only thing I’m hoping is different from the “Galaxy Glass” compared to the Galaxy Gear, is that it’s compatible with more devices out of the box. The Galaxy Gear was only compatible with the Galaxy Note 3 and Galaxy Note 10.1 2014 Edition at launch. Since then it’s become compatible with other Samsung devices like the Galaxy S4, Galaxy S3, and Galaxy Note 2. But what about the rest of the Android devices out there? I’d love to see it compatible with those.

Via: Sammobile

Source: The Korea Times

The post Samsung Rumored to Launch their own ‘Glass’ At IFA in September appeared first on AndroidHeadlines.com |.

via AndroidHeadlines.com | http://ift.tt/L2lVCR

Read More..

MOTOROLA KARMA QA1 FROM AT&T has announced the availability of the Motorola Karma QA1. The phone is a variant of the CDMA Hint and features a 2.5 inch QVGA resolution landscape display. This messaging device from Motorola, the Karma QA1 gives customers one-click access to Facebook, and MySpace, plus an all-in-one view of messages with easy scroll navigation.

At 3.46 x 2.51 x 0.70 inches, the quad-band EDGE/dual-band HSDPA device is kind of short and stubby until you pop open the slider to reveal a full QWERTY keyboard. It’s also got a 2.5-inch QVGA display, 2MP camera (with 8x zoom and LED flash), aGPS, web browser, media player, Bluetooth 2.0 with A2DP, 3.5mm jack, and microSDHC slot.

It is available now for $79.99 with a $50 mail in rebate and a 2-year contract.

Read More..