digitalnirvana

Symbian Anna features and improvements detailed With the announcement of the Nokia E6 and X7 phones, Nokia also introduced the world to the refreshed Symbian^3 operating system Symbian Anna. Previously referred to as PR2 by the company, the update brings up to 50 enhancements to the OS, and, in Nokias own words its purpose is renewing Symbian smartphones. The Symbian Anna update will be available in coming months for owners of current Symbian^3 phones, i.e., the Nokia N8, C7, C6-01 and E7. New features of the OS include: New icons: Giving Symbian a new look does go a long way Improved text input: Portrait QWERTY mode, split-screen typing Improved browser: Version 7.3 of the native Symbian browser has much better performance, and, also brings numerous touch and interface improvements, from the URL entry bar, integrated search/address field, to the always visible toolbar buttons. Email and IM enhancements: Microsoft Communicator Mobile support, as well as email enhancements like full meeting request support and hardware-accelerated device encryption Improved Photo Gallery interface: Landscape and portrait interfaces have been improved for usability Enhanced Ovi Maps: Version 3.06 of Ovi Maps brings smart search, Facebook/Foursquare/Twitter check-ins, location-sharing via email and SMS (including with non-Nokia users), updatable/downloadable maps via Wi-Fi, and public transport networks Enhanced Ovi Store: Version v2.06xx brings improved search, including auto-complete, spell-checking and Internet search engine optimization and error fixes; increased file size limits for downloading over WLAN Enhanced Social: Version 1.3 brings status updates in contact card, ability to retweet and view follower list in Twitter, higher resolution image uploads, ability to add caption to images Enhanced Ovi Suite: Version 3.x brings improved device software update features, as well as the ability to download free street maps, new music and mobile apps. Device backup has also been improved, as has Ovi Sync. Developers would be interested in knowing that Symbian Anna supports the following frameworks Flashlite 4, Java Runtime 2.2, Qt Mobility 1.1, and Qt4.7. Check out screenshots of some of the changes, below: New icons on homescreen Portrait homescreen Photo Gallery landscape Web browser Browser options Split-screen typing

Nokia finally announces Nokia E6 and X7 phones, along with Symbian Anna OS refresh Nokia has finally officially announced two much leaked Symbian models – the Nokia E6 business phone and X7 entertainment phone. Along with the two new models, it has also finally refreshed the Symbian^3 OS, with the Symbian Anna update. New features bring all those little interface details we’ve been hearing about for the better part of a year, in a total of 50 enhancements, including new icons, an improved browser, homescreen, split-screen input, and Ovi Maps application. Specifications here.

Apple iPhone 4 pricing in India: be ready to pay a premium Bharti Airtel, and later Aircel, announced the imminent Indian launch of the Apple iPhone 4, and everyone wants to know what the damage will be. We expect Apple to follow the same pricing trends it has in the past when introducing new models while retaining previous generation devices on the shelves – the iPhone 4 will be priced at roughly the same price as the iPhone 3GS at launch – around Rs. 42,000 for the 32GB version. As always, substantially more than its U.S. price. The iPhone 4 16GB version should retail for less, at about Rs. 37,000. Apple will also significantly drop the prices of the iPhone 3GS, so if you are still itching to get your hands on one, good for you.

Victim of this myself with fake pendrive. This is ingenuious, do not know whether to laugh or cry at the brilliance of this idea.

^ Yes because this would mod the framework-res.apk.

^ There is a retail invoice given alongwith the product which shows date of purchase it mentions warranty is by brand only. So if one keeps copy of this invoice then it should suffice.

Dhiraj ji this one does not ship to India, what screen protector/pouch do you use?

YouTube launches live broadcasting service YouTube has launched a live broadcasting service, called YouTube Live, in a bid to broadcast increasing numbers of sports and music events as they are happening. Google has launched a two-day livestreaming trial on its video-sharing website, YouTube “Today we're announcing the initial roll out of YouTube Live, which will integrate live streaming capabilities and discovery tools directly into the YouTube platform for the first time," said YouTube Live product manager Joshua Siegel. YouTube has been trialling live streaming over the last couple of years. Previously it has broadcast one-off events live, including U2’s concert at the Rose Bowl in Pasadena, cricket from the Indian Premier League, and a State of the Union address from Barack Obama. CitizenTube, a channel on the YouTube website dedicated to political discussion, has also regularly hosted live streams. Only select partners will be able to use the live stream platform in its first iteration. “Today, we'll also start gradually rolling out our live streaming beta platform, which will allow certain YouTube partners with accounts in good standing to stream live content on YouTube," explained Siegel. "The goal is to provide thousands of partners with the capability to live stream from their channels in the months ahead." The first big event scheduled to be live streamed via YouTube Live this year is Coachella, a major US music festival. Source: telegraph.co.uk

Abhishek, If you paid by Paypal 1. Login to your account 2. Click on My Account tab 3. Go to Resolution Center 4. Click on Report a Problem tab 5. Select Item Dispute See http://pages.ebay.co.uk/help/tp/problems-dispute-resolution.html for details. Please file the complaint immediately and in your dispute description mention that you have already twice returned the card to seller due to incorrectly described item and the third time also the card is fake.

Battery Icon Mod 1.0 General Description Battery Icon Mod is a general app (root required) for turning the standard battery icon into something more useful and more sophisticated. Important Make a nandroid backup, guide how to do this with Rom Manager here. Only choose the version that matches your device and rom. Also make sure that the rom version matches your current rom. Credits Folks at XDA.

Have not received any call or goods, the status shows confirmed in their website, E-Mailed them for a status update. Got the 8GB SD card and the 8GB pendrive, the packing was good. Yet to test the capacity. Pendrive does look bit plasticky and flimsy. Letsbuy sent some status updates via SMS and E-Mail after my E-Mail, ironically by the time of their status updates the items were received. Overall experience positive.

Google will hold back its Android 3.0 "Honeycomb" to smaller phone manufacturers for an undisclosed period of time, Google said Thursday. Google said that Honeycomb was designed for tablets, not phones, and that it had more work to do before Honeycomb was released in an open-source format, a Google spokesman said in an email. The delay will probably be on the order of several months, Google told BusinessWeek. "Android 3.0, Honeycomb, was designed from the ground up for devices with larger screen sizes and improves on Android favorites such as widgets, multi-tasking, browsing, notifications and customization," Google said in an email to PCMag.com. "While we're excited to offer these new features to Android tablets, we have more work to do before we can deliver them to other device types including phones. Until then, we've decided not to release Honeycomb to open source.We're committed to providing Android as an open platform across many device types and will publish the source as soon as it's ready." That means that smaller phone manufacturers who wish to use Honeycomb will have to wait an undisclosed amount of time before they can get access to the code. But larger OEMs, such as HTC or Motorola, already have access to it. Those OEMs, however, are generally placing it inside of tablets, like Acer is doing. However, that leaves carriers like Cricket Wireless, and its plans to carry forthcoming seven-inch Anydata tablet that will run on Honeycomb, up in the air. Andy Rubin, vice-president for engineering at Google and head of its Android group, explained the delay to BusinessWeek. "To make our schedule to ship the tablet, we made some design tradeoffs," Rubin told the magazine. "We didn't want to think about what it would take for the same software to run on phones." Rubin also said that Google didn't want to risk "creating a really bad user experience". In February, at Google's Honeycomb launch, a Google spokesman said that that Honeycomb is exclusively for tablets right now, and "features will arrive on phones over time." But the version of Android which includes those features on phones may not be called "Honeycomb," or may have a different version number than 3.0. In February, Google announced that the full SDK for Android 3.0 is now available to developers. "The APIs are final, and you can now develop apps targeting this new platform and publish them to Android Market," Xavier Ducrohet, Android SDK tech lead, wrote in a blog post. While app developers get their crack at Honeycomb, OEMs apparently will be much more restricted. Will this reduce Android fragmentation? Time will tell. Source: thinkdigit.com

Chrome is Google's proprietary OS closed source targeted at cloud, Android is open source targeted at mobile ecosystem. For notebooks/tabs Chrome would be pushed while for mobiles Android in the interim. Eventually Chrome would be primed to take over Android in my opinion, however if you go through the below article, bit long but good read, and go to the comments given on that website, opinions are divided. Though this is bit off topic, but since you raised this pertinent point, no harm in discussing here. Android vs. Chrome OS: One broad idea with two futures? With the recent statements from Google on the future release of the Chrome OS on tablets in the future, there has been many a healthy debate on the future of the two projects. The Chrome OS vs. Android discussion has been going on for quite some time but with tablets it will be the first time they actually share markets. While certainly very different in their approaches, the two will be competition in the tablet market which seems to grow with each passing day. The question is, is the competition healthy? First off, it’s important to note the differences between the two. Android is a native OS, meaning it’s apps and information is stored on the user machine while Chrome OS is entirely web based. Android is primarily used on mobile devices while Chrome OS is specifically targeted to netbooks and, likely, tablets. Chrome OS will require internet access while Android works with sporadic access Next, it’s important to discuss some of the history of the two projects. Android started and to this day remains a primarily mobile operating system, for phones and PDAs, etc. Nevertheless, it is growing in the tablet field with the most notable product being the Motorola Xoom. Chrome OS is still in the early stages overall, with a release date fast approaching and the tablet mechanics obviously just getting started. So what does the future hold? Well, to be completely honest, I think the two will coexist. There’s been debate over combining the two together into one project, which in programming terms would actually mean to build what the other does from the ground up, but I think there’s subtle but important differences that will lead them into different futures. I love my Android phone and would definitely be interested in a tablet, but at the same time I think I’d prefer a tablet with Chrome OS on it. Why? Because when I’m mobile I expect my machine to be fast. This isn’t a dig at the Android by any means, but when I’ve had my notebook and been travelling, typically what I encounter is a sort of leapfrog: queue up a task, move, work on task, move, queue up next task, etc. With Chrome OS, the real work is being done on servers and machines far more powerful than mine that can pull in the resources desired in a moment’s notice. All the local machine has to do is portray via the monitor and UI what is going on. That, to me, sounds excellent. I’m a huge fan of cloud computing and as a PC gaming enthusiast, have watched as the movement has grown tremendously over the past few years. With the ability to work or browse on the fly in real-time, that to me sounds excellent. You may be thinking to yourself though, ‘You idiot, your hardware must ****,’ and that is certainly part of the case. I’m a budget spender, but more importantly software continues to grow in it’s memory usage rate each year. How does this affect your Chrome OS machine? Hardly at all. Since the actual work takes place ‘off-shore’ the machines that run them must of course be updated while we users get the benefit of things simply just working. The Android doesn’t have this same ability since the work takes place on the user machine. And they’re both great. I love technology dearly, I’m a fan of watching things grow year-in, year-out and hardware is definitely a part of that. There are some things that are just better when run on your own machine, but at the same time a world where things work at the speed of thought is fantastic as well. Chrome OS hands-down offers the greatest speeds of the two, which in today’s world matters greatly. Speaking of today’s world, there is one area where the two differ greatly. I’m from a rural area so constant internet connectivity means having a card from my local phone service connecting me to the internet and even then it’s spotty at best. Chrome OS requires continuous internet access to work and, while we’re still very early in the process, the ability to connect via anything besides a land line or WiFi hasn’t been mentioned. That’s not to say it isn’t in the works but Android has this ability built-in. In larger cities, campuses, or businesses where it’s not an issue Chrome OS will definitely shine and as we progress forwards, more of the country will be covered in WiFi hot spots and such but it’s definitely a chink in the armor for now. I genuinely believe though that there is room for both systems and wouldn’t be at all surprised if they stayed as separate projects. Some people may say it’s stupid to have both, but they play to different crowds and that’s definitely a good thing. Google has the opportunity to please the extreme-mobile, extreme-modder, and casual crowd with both systems should they play their cards right. While splitting up a market with internal competition is widely regarded as a bad move in the business world, I think with the right approach Google can play to their strengths of the individual OSs. I for one like having the options.

The tune has to be .wav, 30 seconds or less, 300kb or less. Few free softwares which help: 1. http://mp3cut.net/ - just upload the main .mp3 file here and trim to required 30 seconds. 2. audacity.sourceforge.net - download and install this, then open the trimmed .mp3 file from step 1. Go to Edit > Preferences and lower bit rate. Then try different combinations and go to File > Export as WAV till the time you get required quality with file size of 300KB.

Have not received any call or goods, the status shows confirmed in their website, E-Mailed them for a status update.

Thanks!

Very interesting read and would partially agree, while the post throws up very valid pointers, I still think that approach of an OS manufacturer clamping down on the openness and especially imposing hardware conditions on OEMs is outright failure at worst, and hit and miss at best. Let us take two examples, both dealing with the behemoth we love to hate - Microsoft. Case 1 - Windows Phone 7 did the exact same thing that Android is trying to do by standardizing and dictating the specifications of hardware OEMs. E.g. all phones had to have minimum specifications, had to have specifically mapped Windows button, etc. You can read more on the internet but basically what WP7 tried to do was to achieve uniformity (by specifying mapped keys layout, discouraging skins/shells) and consistent user experience. WP7 did achieve this, but sales wise it has disappointed. Verdict - hit and miss success. Case 2 - Windows Vista did not have reverse compatibility (even though it has compatibility mode but most existing software had problems running on Vista) for existing/older programs and demanded outrageously high hardware capability from OEMs. The reason given was that this level of hardware was needed to experience the benefits of the OS to optimum level. This approach meant a> most home PCs did not migrate to Vista because the hardware criteria was not met and b> most businesses did not migrate to Vista because the programs they wanted to run were often not possible on Vista due to it's lack of reverse compatibility. Verdict - flop. Now look at the current Android landscape. A G1 which is the oldest pure Google phone gets Gingerbread, yet a Hero which is a year newer, does not get Froyo officially. Openness? Double standards, more like! Carriers will always try to not support moderately old sets to push sales of new products. But the Google approach of opensource has allowed devs/geeks to put any version of Android (stock AOSP, not skin like Sense) on any phone. Of course, some hardware limitation would be there like Flash not running on ARMV6 processor, but the bottom line is, users have been able to enjoy latest Android OS on their mobiles by virtue of the opensource community, irrespective of their phone's hardware capability. Now think about Google's approach of curbing openness in the name of reducing fragmentation. Imagine you had spent 200$ on an Epic for a two year contract and 1 year into it, you found your phone is obsolete and would never get any more updates. What would you prefer? An official outdated OS "supported" by Sprint, or a community built/Google provided stock version of latest Android? I know which I would want. Android must not impose hardware limitations on OEMs and definitely must not "Dump the X10s and 2Xs from the portfolio of real Android devices -- and Google can do that by denying them access to its non-open source products like Gmail, Maps, and the all-important Android Market". That would spell death for the platform. Remember, Facebook is waiting in the wings. They have already developed INQ cobranded phone, and they have the advantage of having captive user base of 600 million. Android must find ways to reduce fragmentation, but not at the cost of denying older sets a taste of latest OS.

If you try to upload files above 8 GB are they getting overwritten and corrupt? Looks like fake to me. Open an E-Bay dispute immediately.

Hi Arun, The edit button is not visible on some of my posts e.g. , is there any time restriction after which this button becomes disabled? Regards, Dipan

Good post thanks, + to CM and Genius.

Good informative post thanks, especially with NFC becoming a more mainstream technology. If possible please also add the security aspect, because with wireless communication eavesdropping is a threat like bluejacking for BT etc.

Blackberry Bold Touch Montana - CDMA sibling of Dakota, coming on Sprint and Verizon You can think of the BlackBerry Montana as Dakota's CDMA sibling. With both the Montana and Dakota likely to hit the market under BlackBerry Bold Touch branding, this is RIM's thinnest BlackBerry ever with premium materials and finishes and a forged, machined stainless steel frame. The BlackBerry Montana's features and specs include: Dimensions: 115 x 66 x 10.5mm Processor: Qualcomm 1.2GHz CPU Radio: 800/1900 MHz EvDO Rev A with Receive Diversity (PCS Only); Quad-band GSM/GPRS/EDGE; Dual Band UMTS (HSPA 7.2/5.76) 900/2100MHz Display: 2.8" diagonol - VGA 640 x 480, resolution 287dpi Camera: 5mp - Flash - Image Stabilization - HD Recording (720p) Navigation: Capacitive Touch, Optical Trackpad Keypad: Wide QWERTY - Physical Send, End, Escape, Menu, Right Side Convenience Key, Volume Control Memory: 8GB - 768MB RAM - up to 32GB MicroSd Crad WiFi: 2.4 GHZ b/g/n - 5GHz a/n - Mobile Hotspot Connectivity: Micro USB - Bluetooth - NFC Sensors: Magnetometer - Accelerometer - Proximity The screen resolution is way high, better than the BlackBerry Curve Touch which is going to be a basic touchscreen model. As for the release date, it’s scheduled for Q3 of 2011, not so bad. Source: crackberry.com

Google Nexus S 4G - 4G big brother of Google Nexus S, coming on Sprint likely on Apr 24 Connectivity Quad-band GSM: 850, 900, 1800, 1900 Tri-band HSPA: 900, 2100, 1700 HSPA type: HSDPA (7.2Mbps) HSUPA (5.76Mbps) Wi-Fi 802.11 n/b/g Bluetooth 2.1+EDR Near Field Communication (NFC) Assisted GPS (A-GPS) microUSB 2.0 Display 4.0" WVGA (480x800) Contour Display with curved glass screen Super AMOLED 235 ppi Capacitive touch sensor Anti-fingerprint display coating Size and weight 63mm x 123.9mm x 10.88mm 129g Hardware Haptic feedback vibration Three-axis gyroscope Accelerometer Digital compass Proximity sensor Light sensor Processor and memory 1GHz Cortex A8 (Hummingbird) processor 16GB iNAND flash memory Cameras and multimedia Back-facing: 5 megapixels (2560x1920) 720 x 480 video resolution H.264, H.263 MPEG4 video recording Auto focus Flash Front-facing: VGA (640x480) 3.5mm, 4-conductor headset jack (stereo audio plus microphone) Earpiece and microphone Software noise-cancellation Battery Talk time up to 6.7 hours on 3G (14 hours on 2G) Standby time up to 17.8 days on 3G (29.7 days on 2G) 1500 mAH Lithum Ion Software Android 2.3 (Gingerbread) Android Market Calendar Gmail Google Earth Google Maps with Navigation Google Search Google Talk Google Voice Voice Actions YouTube The device has just passed through the FCC under the model number ‘SPH-D720′ which Engadget previously confirmed is the model number for the Nexus S 4G. The FCC testing confirms the presence of the WiMAX radio for Sprint’s network. (source: FCC via AndroidCentral) The Nexus S 4G is said to be essentially a 4G-compatible Nexus S, with virtually nothing changing from the original Nexus S. With the FCC paperwork indicating that the device being tested is a CDMA model that uses WiMAX, that points to a phone being offered by Sprint. And the next 4G phone to be offered by the nation's third largest carrier will be the Google Nexus S 4G. Sure, other Android phones have 4G connectivity, but the beauty of the Google Nexus S 4G is that it is "Pure Android" which should put it near the front of the line for the next Android OS build after the included Gingerbread. In fact, running stock Android should allow the phone to always have the most up to date build of Google's open source OS. As for the launch of the phone, Phonearena recently reported that April 24th appears to be a likely date to expect the phone's release by Sprint, with a price of $199.99 expected for those signing a two-year contract.

Blackberry Bold Touch Dakota - GSM BB combining Bold and Touch, coming end May The BlackBerry Dakota is rumoured to be launched in late May. It holds basically the same form factor as the Bold series, but mixes a full QWERTY keyboard with a touchscreen. Besides using a touchscreen, an optical keypad will be available to navigate the screen. This phone, which is said to be internally known as R005, and nicknamed "Bold Touch" is expected to offer a 2.8-inch capacitive screen with a resolution of 640 x 480 a 5MP camera, equipped with flash, will capture video in 720p, and BlackBerry OS 6.1. Also available are 4GB of internal storage and 768MB of RAM. A great addition is the 3G mobile hotspot that has been added, not to mention the NFC connectivity. The Wi-Fi N, Bluetooth and MicroUSB port come as no surprise. In addition, the Dakota is going to ship with the new BlackBerry 6.1. The new version of the BlackBerry platform now supports Magnetometer and Digital compass APIs, OpenGL-ES 2.0, event-base geo-fencing location APIs and much more. Specifications Quad-band GSM/GPRS/EDGE Tri-band UMTS 5 megapixel camera with HD video recording, flash, and image stabilization 4GB of built in storage, 768MB of RAM 2.8-inch VGA 640 x 480 capacitive screen WiFi b,g,n on 2.4GHz and 5GHz frequencies 3G mobile hotspot! MicroUSB port Bluetooth NFC Magnetometer Accelerometer Proximity sensor 10.5mm thin Launches with BlackBerry OS 6.1 A leaked spec sheet for the BlackBerry Bold Touch Dakota reveals that the phone will be humming with a 1.2GHz Snapdragon processor on board. With a 2.8 inch LCD VGA display and a 35-key QWERTY keyboard, the handset will be another attempt by RIM to compete with the Apple iPhone and Android handsets. One thing to note is it lists the Dakota’s processor as ‘QC 8655′, which looks to be the Qualcomm Snapdragon MSM 8655. It is great to see that the Dakota will be running on a solid processor for 2011. The Dakota will run on 5GHz WiFi and have 8GB eMMC, which means you may be able to use all the internal memory for app installs. Sources: phonearena.com, crackberry.com, phonedog.com and BGR.com

Leaked screen shot indicates that a 16GB version of the Motorola XOOM is on the way Glancing over a recently leaked screen shot from Verizon’s Device Management system, it indicates that the carrier will be selling a 16GB version of the XOOM – of course, it’ll be enabled for 3G right now, but it’ll get 4G whenever that happens.