digitalnirvana

^ Another great offer, you must have good negotiation skills.

That would be extremely controversial because except the Xoom all existing tablets are on 2.x, surely there would be a backlash if this is implemented and it would harm 3.0 badly, surely customers would not buy new tablets just for new OS. Clearly remember Notion Ink saying the Adam which is 2.2+ would get 3.0, so need to see what Google does.

Detailed review here.

Thanks for the info. The Vodafone tariffs are the best IMO as they offer the customer try before you buy option, thereby making customers accustomed to 3G so most will eventually subscribe.

^ Glad to be of help.

Update - found another way, see http://forum.xda-developers.com/showthread.php?t=1008596 apparently removing systemupdater.apk will stop the prompts so no need to edit build.prop, again please take a backup and instead of removing the apk I suggest rename it so that if you decide to go for OTA you can rename it later on.

^ Welcome, I have just given the generic process, glad to help, but note exact process might be bit different for Epic or other phones. Do remember to take a backup of build.prop before you do anything as without this file it will not boot, and it is must to get correct version of the build, try searching the XDA Epic forums for details of the process.

^ The OTA updates go to cache so if you want to recover 91 MB reboot to recovery and clear cache or use cache cleaner app from market. This would not stop the update reminder coming because OS is not updated and it would download again and try to install, the way to stop OTA prompt is to edit build.prop to show the updated version. Generic steps: 1. In Root Explorer, go to /system/ 2. Tap Mount R/W at the top, then long-press on build.prop and scroll down to Open in Text Editor 3. Once the file is open as a text file, scroll down until you see the line that says similar to: "ro.build.fingerprint" and change the versions mentioned there to the latest build. 4. Tap the back key and say "Yes" when it asks you to save (it will automatically back up the original file for you but better to keep a backup) 5. Tap Mount R/O at the top 6. Reboot Please get exact version details and keep a backup before proceeding.

Josh if your criteria is QWERTY in addition to touch screen, go for Epic from Hetal bhai, or check the Droid Pro from Genius bhai. It is all down to what are your requirements.

Rajanbhai you certainly have the gift of the gab, great post.

Yes Hetal ji just noticed that, you are correct...was in hurry to post after reading the topic because thought the 3rd graph was amazing my bad...

New User Features UI refinements for simplicity, speed and power-efficiency Faster, more intuitive text input (redesigned keyboard and text input) Improved power management Control over applications (Manage Applications – running tab) New ways of communicating, organizing (NFC, VoIP, SIP) Downloads management Camera access (front and back) New Developer Features Performance Concurrent garbage collector Faster event distribution Updated video drivers Native input and sensor events Gyroscope, rotation vector, linear acceleration, gravity, and barometer support Improved 3D motion processing Open API for native audio Native graphics management Native access to Activity lifecycle, window management Native access to assets, storage Robust native development environment Mixable audio effects Support for new media formats Access to multiple cameras New Platform Technologies Media Framework New media framework fully replaces OpenCore, maintaining all previous codec/container support for encoding and decoding. Integrated support for the VP8 open video compression format and the WebM open container format Adds AAC encoding and AMR wideband encoding Linux Kernel Upgraded to 2.6.35 Networking SIP stack, configurable by device manufacturer Support for Near Field Communications (NFC), configurable by device manufacturer Updated BlueZ stack http://www.youtube.com/embed/Jx3pdWBlZ34 Source: thinkdigit.com Disclaimer: could not find post which details out benefits of Android 2.3 Gingerbread hence posting, if this is redundant mods do delete.

Kumaar thank you for sharing, respect and reverence for how the Japanese are handling this situation.

Numbers reveal: BlackBerry owners looking to switch to iPhone and Android devices Nielsen, one of the biggest market research companies in the world, has released its smartphone market numbers for the past 6 months. Like all market research, it has to be taken with a pinch of salt, but the numbers are interesting anyway. Current figures for new subscribers in the US peg Google/Android’s market share at 27%, RIM/BlackBerry’s share at 33%, and Apple/iPhone’s share 23%. While Android’s rising numbers have proponents of the green robot jumping with joy, one has to agree that Apple, with a single device, is still strong and competing against Android’s innumerable devices. In terms of all subscribers in the US for the quarter ending June 2010, BlackBerry has 35% of the share, iPhone 28%, Windows Mobile 15%, while Android is still at a measly 13%, though rising as fast as WinMo is falling. Perhaps the most interesting statistic is of the survey “Next Desired Smartphone OS”, which reveal that more than 50% of BlackBerry owners are looking to switch to iPhone (29%) and Android (21%) devices with their next purchase. These are astonishing numbers, quite indicative however of how the iPhone and Android devices are sneaking up on both corporate and consumer markets as the must-have devices. We’ll just have to wait for RIM’s BlackBerry OS 6.0 to make its mark and wow back customers with a shiny new interface. Source: thinkdigit.com Note to mods - please could you increase the image size, could not do it. Thanks.

Josh - welcome to the forum, definitely you will not get better deal than the Fascinate one, great handset from one of the gurus, go for it.

Could not find this on MTS website, might be not updated yet.

Agree with both the posts but sometimes need to know whom to beat and whom to join. China has R&D based economy where it is mandatory for MNCs to do technology transfer when doing business, India has approached the open economy as a market while China has approached it as a producer, there are many stark differences in their economic policies, so comparing China with India only on one aspect of national card system would be not fair.

Thanks Rajan and CM for your views.

The Samsung Mobile Unpacked 2011 CTIA event was meant to introduce the world to just the Galaxy Tab 8.9, but Samsung had a surprise in store – a completely new Galaxy Tab 10.1 than it had shown off at MWC 2011, with a fancy new slim design that’s thinner than Apple’s latest iPad. The two Honeycomb tablets have been given competitive prices pegged to the iPad 2, with the 16GB WiFi-only 10.1-inch model priced at $499 and the 32GB model at $599, while the 16GB WiFi-only 8.9-inch model will retail for $469, and the 32GB model for $569. For now, only WiFi models of the two tablets have been announced, though 3G and 4G HSPA+ tablets were detailed. The WiFi-only Galaxy Tab 10.1 is scheduled to hit shelves in the U.S. on June 8th, and the WiFi-only Galaxy Tab 8.9 has been given an ‘early summer’ or July-August arrival. Find specifications in the Samsung released spec sheets above. While Samsung has still not revealed exact nature of the 1GHz dual-core application processor that powers both tablets, it’s still assumed to be Nvidia’s Tegra 2 offering. Both tablets are thinner than the 8.8mm thick iPad 2, measuring just 8.6mm. The large 6000 mAh and 6860 mAh batteries that power the devices are expected to give about 10 hours of video playback. Both tablets also pack Wi-Fi a/b/g/n connectivity, will support Flash 10.2, and have dual speakers for stereo surround sound. Both the 10.1 and 8.9-inch tablet have an impressive WXGA 1280x800 resolution screen, and both feature Samsung’s TouchWiz 4.0 UI onboard which will have features such as the ability to resize widgets, both its own Live Panel and Google’s native widgets. The Mini Apps Tray was also deemed useful, but redundant in the fact of Google’s app launcher. Samsung has also thoroughly customized the native apps in the Galaxy S-style. The CTIA event also showcased some TouchWiz 4.0 features like Readers Hub, Social Hub, and Games Hub. Some regions can expect vanilla versions of the tablets however. Source: thinkdigit.com

^ Sadikk bhai is doing both MEID registration and EVDO. Getting your phone's MEID registered will make it like official handset and voice would work. Please contact Sadikk bhai on his thread and he would help you, after you get MEID registered then go to webworld and activate it by using retain MDN or *228 HCC.

Thanks my parent is diabetic so will think of buying this, any reviews of the product?

^ Not sure about the other points so would rather not comment, but on the topic of - the existing limits of 5 limited value free withdrawals per month while using other bank ATMs I have used banks outside India which offer unlimited free ATM usage even of other banks. These ATMs were mostly in railway stations and guess were meant to facilitate users. There were other ATMs also which did not offer unlimited free usage of other banks and this was specified in the ATM itself. So it is mostly matter of common sense. The goodwill that a bank gets by allowing free use to a harried traveller using another bank's card cannot be measured. Visa and Mastercard are worldwide and cannot be beaten, so why does not RBI negotiate cheaper transaction charges for domestic transactions for Indian banks? This way everyone wins.

ADB is an acronym for Android Debug Bridge and is a development tool for the Android Mobile Operating System. There are different ways to install adb on windows. Below listed two methods, the first method is "Complete", which involves installing the Android SDK (Software Development Kit), and the second "Quick" way. Either should be fine for rooting etc. INSTALLING ADB ON WINDOWS - METHOD A, THE "COMPLETE" WAY, USING THE SDK Step 1 Download and install USB drivers for your phone. Step 2 Download and install the Android SDK (Software Development Kit) Starter package from http://developer.android.com/sdk/index.html There are two choices for Windows there, a simple zip file which you can unzip somewhere appropriate on your PC (e.g. put it on C:\ if you like). Or there's an installer (which is the recommended option according to the Android website), though that forces you to download some Java stuff which we don't really need for adb and takes a lot longer to install (but there won't be any harm in getting). If you downloaded a .zip or .tgz package (instead of the SDK installer), unpack it to a safe location on your machine. By default, the SDK files are unpacked into a directory named android-sdk-<machine-platform> e.g. android-sdk-windows. You can read all about how to install the SDK at http://developer.android.com/sdk/installing.html . Ignore all the stuff about Eclipse though, you don't need that unless you're going to start writing Android apps. Now, from version 8 (Android 2.3) of the SDK onwards, adb has been taken out of this starter package. If you downloaded version 7 (Android 2.2), then you've already got adb and you can skip Step 3 and go straight to Step 4 below. Otherwise you need to proceed to Step 3 to add adb to the SDK. Step 3 Assuming you have version 8 of the SDK Starter package onwards, now we need to add the Platform Tools component to the SDK, because that contains adb. Run "SDK Manager" on your PC. You will find that in the root directory of the SDK, so you can open up a file explorer window to find that, then double-click on "SDK Manager" to run it". Wait for a few seconds while it checks on the Android website for updates etc, let it then pop up with a window showing you what is on offer. Add the "Android SDK Platform Tools", you can "reject" (i.e. don't install) all the other things it offers you if you like, though there's no harm in installing them (just takes up disk space on your PC). Step 4 Now we need to update your Path variable. This lets you run adb on your PC from a command window no matter which directory you are in (which makes things a lot easier). If you don't setup your Path, then every time you want to run adb, you will either have to type the whole long pathname where you put adb, or cd to where you've put adb and run it from there (which could be inconvenient if you are transferring files to/from your phone). On your PC, right-click on "My Computer" and select "Properties". (on Vista, click on "Change Settings"). Go to the "Advanced" tab, then select "Environment Variables". Find the "Path" variable in the list of variables that it shows (you might need to scroll), and then double-click on that entry to edit it. Add the full path of the "tools" and "platform-tools" folders of the SDK to your path. e.g. if the SDK has been installed in "c:\Program Files\android-sdk-windows", then add to the end of your Path ";c:\Program Files\android-sdk-windows\tools;c:\Program Files\android-sdk-windows\platform-tools" (Please Note - don't put any spaces between the semi-colon and pathname, otherwise it won't work !) Click on OK to exit out of the dialog, then OK again to get out of My computer's properties. After you reboot your computer you'll have it set up. Step 5 On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this. Step 6 Plug your phone into your PC using the original USB cable. This is important, do not use a third-party cable since it might not work with adb (even though it might seem fine with other communication with your phone). Step 7 Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus, and type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) : Code: C:\&gt; adb devices This should display something like the following : Code: List of devices attached XXX12345 device ... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 5 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb ! By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output. INSTALLING ADB ON WINDOWS - METHOD B, THE "QUICK" WAY, NO SDK Step 1 Download and install USB drivers for your phone. Step 2 Download this zip archive and unzip it somewhere memorable on your PC (e.g. into a folder on your desktop) - http://dl.google.com/android/repository/platform-tools_r01-windows.zip Step 3 On your phone, go into Menu->Settings->Applications->Development and make sure you have the entry "USB Debugging" ticked. adb will not work without this. Step 4 Plug your phone into your PC using the original USB cable. Step 5 Fire up a command prompt on your computer, e.g. "Run" then "cmd", or pick the "Command prompt" option from the menus. Use the "cd" command to change to the folder that contains the adb.exe and other files that you unzipped in Step 2. Then type in the following (obviously the C:\> bit is your actual PC's prompt, not what you type). To emphasise, you are running this on your PC, not directly from your phone (e.g. terminal emulator) : Code: C:\&gt; adb devices This should display something like the following : Code: List of devices attached XXX12345 device ... where the "XXX12345" bit is actually your phone's serial number. If the list is blank and the phone is plugged in ok, go back to Step 3 and make sure USB Debugging is enabled. If you can see your phone, then you're in business, adb can see your phone and communicate with it, and you're ready to start using adb ! By the way, the first adb command that you type may well also come up with some lines similar to "adb deamon out of date" etc, but don't worry, that's normal, just check the rest of the output. Source and credit: XDA

Currently, HSDPA enables downlink transfer speeds of up to 21 Mbit/s. Please see High Speed Downlink Packet Access.

^ I doubt locked would prevent rooting and custom ROMs. All the US CDMA phones are locked to their carriers but can and are being rooted.