Your Android gadgets are the most important things in your life. It contains all your important contacts and information. If you lose your equipment, you will be losing all those sweet memories with the photos and video. But there is some good news to android phone/tablet users, you can now easily find or at least know where your missing phone is with or without using android application.
Showing posts with label Android. Show all posts
Showing posts with label Android. Show all posts
Saturday, July 26, 2014
Your Android gadgets are the most important things in your life. It contains all your important contacts and information. If you lose your equipment, you will be losing all those sweet memories with the photos and video. But there is some good news to android phone/tablet users, you can now easily find or at least know where your missing phone is with or without using android application.
Let’s first look at the way of finding your lost phone which doesn’t contain any app installed on it.
Every android phone carries a unique IMEI
number (International Mobile Equipment Identity Number). It will be
printed at the back of your device. If you are unable to find the
number, you have to launch your phone app and dial the number *#06#.
This will give you the IMEI number of your phone. Store this number in a
safe place so that it helps you in locating your phone when it is lost.
When you file a complaint, this number
has to be added in the report. Your service provider uses this number to
track your phone and tell you where it is. No matter if the person
using the phone is using a different SIM card or has switched off the
phone. Once the device is traced, you can request your service provider
to block it from using.
This is one of the easy ways of locating your lost Android phone or tablet.
Another way of tracking your lost Android
gdget in no time is through Plan B app. This app does not require you
to install any recovery software previously but still helps in finding
your lost phone. All you need to do is log on to your Google play
account. Lookout mobile security offers free software called Plan B.
Download the software from play store to your phone. This will be
possible only if your phone is within the Internet coverage area. Wait
for some time and then send the keyword “locate” without the quotes
through SMS to your phone. And a map showing where your equipment is
will be sent to your Gmail account. This app is very much useful in
situations where you don’t have IMEI number.
If you have installed and configured any of these below android software previously, there is good chance of finding it.
You can log on to Google Play store >
My Android Apps, on your computer and check if you have installed any of
the following apps previously.
Lookout is the best android app for
security and antivirus. So far, it has received millions of downloads.
Just recall if you have installed this on your phone.
If you have activated the option “Missing
Device” in this app, it is easy to find your device. If you have also
enabled “Signal Flare” option, you can trace the last known location of
your android device. This is helpful in case your phone battery is dead
or tablet is switched off.
Now sign in Lookout to locate your
device. The map shows the location of your phone. If you are at a short
distance from the tablet, you can choose Scream option to make a loud
noise to find it.
Google has recently released a new
locator feature for Android gadgets called Android Device manager, which
helps its users locate their lost or stolen phones and tablets. It
functions in the same way as Lookout and Samsung’s “Find My Mobile”.
Here’s how to use Android Device Manager.
Go to the Google Settings app, then
select Android device manager. By default the locator feature is
activated but to activate remove data wipe, select the box next to
“Allow remote factory reset”, then select “activate”.
To use this feature, open the site https://www.google.com/android/devicemanager
and sign in to your Google account. You may be prompted for permission
to allow Android Device Manager to use location data. Select the Accept
tab to continue.
Now you will be provided with a map that
shows the location of your device along with other details such as the
name of the place, when it was last used and more. The location data
doesn’t help you if your phone is misplaced somewhere in your home.
Instead of making a call to your phone using other’s phone, you can call
your phone directly from Android Device Manager. This will make your
device to ring with high volume for 5 minutes, even if it’s in silent or
vibrate mode.
One feature that is missing in Android
Device Manager is remote locking, which can be useful in preventing a
stranger from accessing your data, while you’re tracking its location.
Apart from these, there are other apps
such as Android Lost, Where do My Droid and GadgetTrak that help you in
finding your lost Android phone/Tablet.
Sunday, June 1, 2014
Hi guys,here i am posting about how to root samsung galaxy s3 I9300 Jelly Bean based on XXUFME3 firmware.
Requirements:
1]USB drivers for Samsung galaxy s3 I9300 to transfer files from device to computer Download
2]Download Root Package for Samsung Galaxy S3(CF-Root-SGS3-v6.4.zip) Download
3]Download Odin v1.85 for samsung galaxy s3 firmware Download
Procedure:
1]Download and extract all the above files to the computer.
2]Make sure that the your phone is based on the XXUFME3 firmware.
3] Take backup of your phone data for safety.
4]Charging of phone should be above 80%.
5]Now switch of the samsung galaxy s3 and enters into the download mode by pressing and holding Volume down button and menu button together and then press power button until triangle is appear.Again press power button to continue.
6]Launch Odin on computer (Run as Administrator)
7]Now connect device to the computer by using USB cable.
8]Wait till Odin shows ID: COM box turn to yellow and showing computer port number.This means connection is successfully established.
9]Then in Odin select PDA button and select the file CF-Root-SGS3-v6.4.zip
10]Confirm that the Auto-Reboot and F.Reset Time Check-boxes are selected .And do not select Re-Partition check box .
11]Now click on the start button in Odin to start installation or rooting.It may take some minutes.
12]After installation complted,phone will be restart automatically and then disconnect the USB from the computer.
13]Now Enjoy,you have have successfully rooted.
Disclaimer:
Author Is Not Responsible For Any Kind of Damage To Your Phone And Illegal Use By Users.
Friday, March 14, 2014
With the pace of smartphone evolution moving so fast, there's always
something waiting in the wings. No sooner have you spied the latest
handset, then there's anticipation of something else, the next big
thing.
We've rounded up the best smartphones for 2014, those we consider to
be the best across all platforms, and we've regularly updated that list
as the smartphone world has evolved over the last year from 2013 in to
2014. You can find those in our Best smartphones 2014 feature.
Here we're looking at those phones that haven't yet launched, those
we know are coming, or are anticipated. Some will be rumour, some will
be fact, but here we'll cut through the speculation to highlight those
phones we really want to see.
We'll be updating this list on a regular basis, with those device
rumours we think are credible and exciting, and devices just announced
but yet to hit the shelves. With Mobile World Congress 2014 bringing us a
number of phones, there's plenty to consider.
HTC M8/new HTC One
We've known since July 2013
that the next HTC flagship handset is referred to internally as the HTC
M8, the successor to the M7, the device that became the HTC One.
With HTC saying that the "One" name is here to stay, it's safe to
predict that the final commercial name will be new HTC One or HTC One
(2014) or something like that.
As for the specs, it looks like HTC will be bringing the M8 up to the
mark with a 2.3GHz Qualcomm Snapdragon 800 chipset, a 5-inch 1920 x
1080 pixel resolution display and Android 4.4 KitKat with Sense 6.0.
There's little to surprise in there and we suspect most of the attention
will be on the metal body construction as HTC looks to repeat the
luscious looks of the 2013 HTC One.
One change appears to be the addition of an extra camera sensor on
the rear of the handset, designed to improve focusing, low light
shooting and depth of field.
We'll be keeping a close eye on HTC and bringing you any news we hear
on the next HTC handset. The HTC One will be launched on 25 March at an
event in London and New York, so more will be revealed soon.
Samsung Galaxy S5
So many of the rumours weren't true. There's no bump in resolution,
no metal body, no radical change in the UI. Instead there's a
fingerprint scanner and a heart rate sensor, with Samsung eyeing-up
fitness.
But the Samsung Galaxy S5 is still going to be one of the hottest
phones of the year. It has a 5.1-inch Super AMOLED display with a 1920 x
1080 pixel resolution and there's no lack of power with a 2.5GHz
quad-core Qualcomm Snapdragon 801 chipset.
Speed is on the agenda with a 16-megapixel camera that will focus
fast, as well as a Download Booster offering to pull in files over Wi-Fi
and 4G simultaneously.
There's a whole collection of smart camera and software features, as
well as a new focus on battery life, with the SGS5 offering a low power
mode to make sure you stay connected for longer. The Samsung Galaxy S5
will be available globally on 11 April.
Sony Xperia Z2
The talk of Mobile World Congress has been the Sony Xperia Z2. It
takes the Xperia Z1 - launched only 6 months ago - and refines it. The
screen expands to 5.2-inches and it gets itself a 2.3GHz quad-core
Qualcomm Snapdragon 801 processor and 3GB of RAM, so it could be one of
the fastest phones around.
It's large though, as the previous model was, but it's definitely
better. With added software refinement and Android 4.4 KitKat, it's more
polished and offers more features than the previous device.
Most of the rumours were true: there are front-facing speakers to
boost the sound quality, but also noise cancellation through the
supplied headphones. There's 4K video, as well as stabilisation.
There's no confirmed launch date, but we suspect April, although the phone is on pre-order for £599.
LG G3
LG has seen a return to form in 2013, with the LG G2 doing a lot to
restore faith in the company's smartphone ambitions. That, and the new Nexus 5, see growing anticipation for LG's next flagship device, the LG G3.
The LG G3 is said to land with a 2560 x 1440 pixel resolution
display, with a slight increase in size. One of the strengths of the G2
is packing a larger 5.2-inch display into a handset that's smaller than
some rivals (like the Xperia Z1), so we'd expect to see the same again:
more display without the bulk.
There's talk of LG using it's octa-core Odin chipset to power the G3, as well as looking at a fingerprint scanner for security.
LG G Pro 2
LG has now officially launched the LG G Pro 2, although it's
initially a Korean handset only, with no news on whether we'll see it in
other territories.
The LG G Pro 2 has a 5.9-inch 1080 x 1920 resolution display, 2.3GHz
quad-core Qualcomm Snapdragon 800 chipset, 3GB of RAM, and LTE
connectivity. The G Pro 2 has a 13-megapixel camera with optical image
stabilisation on the rear, capable of 4K video capture.
It looks like a strong competitor for the Samsung Galaxy Note 3 and should be a great phablet.
Nokia Lumia Icon
Nokia has been going from strength to strength in 2013, making
Windows Phone a much more attractive proposition over the past 12
months. The best device so far has been the Lumia 1520, as it breaks new ground for Windows Phone, pushing the display resolution up and making better use of the space available.
The Nokia Lumia Icon brings those phablet skills down to a 5-inch
device, but it's a Verizon exclusive. The Lumia Icon has a full HD
display, along with a 20-megapixel PureView camera and a 2.3GHz Qualcomm
Snapdragon chipset. That's something that might grab the attention of
those getting tired of Android.
The Nokia Lumia Icon is now on pre-order, hitting stores on 20 February for $199 on a 2-year Verizon contract.
Nokia X
One of the most leaked phones, the Nokia X is something of an oddity.
It's an Android phone, but has been removed from Google, so that you
can have mixture of apps you'll find familiar from Nokia's Windows
Phone. Falling somewhere between the too, you'll get access to Nokia's
services, but it will also run Android apps.
There's no Google Play, however, but there will be a Nokia Store to
give you apps and you can sideload apps. The biggest thing about the
Nokia X, however, is price. They're affordable devices and although they
won't give you the best of the smartphone experience, they might
connect those who otherwise couldn't afford a smartphone.
Starting at €99, the Nokia X devices are definitely quirky.
Nokia Lumia 930
There's a new Nokia kid on the rumour block called the Lumia 930,
said to be a 4.5-inch update of the 920/925 level of device. It's been
mentioned that it will bring the top specs of the Lumia Icon to the rest
of the world. Previously there was the Lumia 1520V, said to be a
smaller version of the 1520, so we suspect they are the same handset.
The Lumia 930 is said to have a 4.5-inch 1920 x 1080 resolution
display, a quad-core Snapdragon 800 chipset and a 20-megapixel PureView
camera. With the Lumia 925 getting rather old, it sounds like a likely
spec bump for this important flagship space for Nokia.
There's talk of a launch at Mobile World Congress 2014 at the end of February.
Samsung Galaxy Note 3 Neo
The Samsung Galaxy Note 3 is undoubtedly a great device. It's king of
the phablets and has been a huge success for the company, helping
remind us why big devices are also beautiful.
But for some, it's just too much. It's too big, it's too expensive
and it's overkill: enter the Neo, to bring the Galaxy Note experience to
a wider audience. Samsung has formally announced the Galaxy Note 3 Neo,
but it looks like Neo won't be coming to the UK or US. Those in Poland,
however, you're in luck.
The Galaxy Note 3 Neo features faux leather back, neatly dressing the
5.5-inch 720p AMOLED display, 1.6GHz quad-core processor and
8-megapixel camera. It sounds like the Note 2 in a new coat and that's
pretty much what it is, with LTE thrown into the mix.
Monday, January 27, 2014
In the last quarter of 2013, sale of a Smartphone with ANDROID operating system has increased and every second person you see is a DROID user.
A Russian security firm 'Doctor Web' identified the first mass distributed Android bootkit malware called 'Android.Oldboot', a piece of malware that's designed to re-infect devices after reboot, even if you delete all working components of it.
The bootkit Android.Oldboot has infected more than 350,000
android users in China, Spain, Italy, Germany, Russia, Brazil, the USA
and some Southeast Asian countries. China seems to a mass victim of
this kind of malware having a 92 % share.
A Bootkit is a rootkit malware variant which infects the device at
start-up and may encrypt disk or steal data, remove the application,
open connection for Command and controller.
A very unique technique is being used to inject this Trojan into an
Android system where an attacker places a component of it into the boot
partition of the file system and modify the 'init' script (initialize the operating system) to re-load the malware as you switch on your android.
When you start your device, this script loads the Trojan 'imei_chk' (detects it as Android.Oldboot.1) which extract two files libgooglekernel.so (Android.Oldboot.2) and GoogleKernel.apk (Android.Oldboot.1.origin), copy them respectively in /system/lib and /system/app.
Android.Oldboot acts as a system service and connects to the command-and-controller server using libgooglekernel.so library and receives commands to download, remove installed apps, and install malicious apps.
Since it becomes a part of the boot partition, formatting the device
will not solve the problem. The researchers believe that the devices
somehow had the malware pre-loaded at the time of shipping from the
manufacturer, or was likely distributed inside modified Android
firmware. So, users should beware of certain modified Android firmware.
Two weeks ago, Some Chinese Security Researchers have also detected a bootkit called 'Oldboot', possibly the same malware or another variant of it.
"Due to the special RAM disk feature of Android devices’ boot partition, all current mobile antivirus products in the world can’t completely remove this Trojan or effectively repair the system.""According to our statistics, as of today, there’re more than 500, 000 Android devices infected by this bootkit in China in last six months.
The Android malware Android.Oldboot is almost impossible to remove, not
even with formatting your device. But if your device is not from a
Chinese manufacturer, then chances that you are a victim of it, are very
less.
This bootkit is not the first of this kind. Two years back, in the month
of March we reported, NQ Mobile Security Research Center uncovered the
world's first Android bootkit malware called 'DKFBootKit', that replaces certain boot processes and can begin running even before the system is completely booted up.
But Android.Oldboot malware is a bit more dangerous because even
if you remove all working components of it from your android
successfully, the component imei_chk will persist in a protected boot
memory area and hence will reinstall itself on next boot and
continuously infect the Smartphone.
Users are recommended to install apps from authorized stores such as Google Play, disable installation of apps from ‘Unknown Sources’ and for a better security install a reputed security application.
You can also try to re-flash your device with its original ROM. After flashing, the bootkit will be removed.
Wednesday, January 22, 2014
Now that 2014 is here, it looks like it's time to start thinking about the next-gen smartphones this year is bound to bring us. Well, if there's anything we feel certain about, that's the fact that Samsung is to release its new flagship Android smartphone, the Galaxy S5, in just a few months. It is rumored that the South Korean giant is going to be among the first companies in 2014 to unleash a new top-shelf smartphone, and we can't wait to see what it's really going to look like! Well, exactly what it's going to offer, and whether it will have something to truly wow us with... that we don't know, but there is already a good number of rumors, leaks and indications, all of which can be used to paint an almost believable image of the Galaxy S5.
We've already come across a number of leaks dealing with the Galaxy S5's release date, as well as some of its technical characteristics, such as its supposed screen size, CPU, camera and more. Please, feel free to browse through the following slideshow gallery, where you'll learn more about what's going to be one of the most-discussed smartphones of 2014!
We've already come across a number of leaks dealing with the Galaxy S5's release date, as well as some of its technical characteristics, such as its supposed screen size, CPU, camera and more. Please, feel free to browse through the following slideshow gallery, where you'll learn more about what's going to be one of the most-discussed smartphones of 2014!
Friday, December 27, 2013
Last week, I posed the question concerning how much credit Apple deserves for the coming 64-bit evolution. The TL:DR version goes like this: 64-bit was already in the works in mobile in various ways. Apple certainly built the base quickly, and switched over its platform quite seamlessly, but being first to fully push into 64-bit doesn't necessarily mean that Apple deserves credit for something that was inevitable, especially since the ARMv8 architecture that the A7 uses was first unveiled two years ago. However, it is obvious that Apple deserves credit for making the switch so quickly, and such a long time before any other mobile platform. Apple also deserves credit for making the issue so public, and forcing the competition to move faster on their plans because of how quickly iOS is making the switch.
Interestingly, the comment thread of the editorial didn't focus so much on the question that I had posed, but rather on a run of information from a reader by the name of JakeLee. JakeLee didn't so much refute the points I had laid out as he claimed that Google has a long, difficult road ahead if it expects to optimize Android for 64-bit in the near future. The info from JakeLee has helped to inform this article. Although, my own research into the matter, and help from the Android Developers community on Google+ has shown that the future may not be as troubled for Android as JakeLee made it sound.
First off, I need to clear up a misconception that is often made, and one that I had myself before doing the research for this piece: when talking about mobile devices, there is no real reason to talk about the 4GB RAM limit that 64-bit helps to surpass. 64-bit is actually a misdirection in the mobile space, because the real issue is moving to the ARMv8 processor architecture. ARMv8 and its brand new instruction set architecture (ISA) are responsible for the real performance boosts that we will see, and it just so happens that this change coincides with the switch to 64-bit. The reason that 64-bit is mentioned and not ARMv8 is because 64-bit is a term that even average consumers and mass media understands to a certain extent. There are plenty of performance benefits to be had on devices that are nowhere near 4GB of RAM, like the iPhone 5s.
As we just learned from HTC, chipset makers build the drivers for processors when Google releases the source code for a new Android release, so ARMv8 support is probably already in the works, but Google still needs to optimize Android for the new hardware.
There are pieces of the puzzle that are already in place for Android. As has been mentioned before, the Android kernel includes 64-bit support, which it has inherited from Linux. It is also known that multiple manufacturers are working on 64-bit processors for the next generation of Android handsets. Samsung let it be known very soon after Apple's announcement of the iPhone 5s and A7 SoC that it was working on a 64-bit version of its Exynos chipset. Qualcomm obviously had a bit of a PR fiasco after Apple's announcement, but then recently introduced its first 64-bit mobile processor, the Snapdragon 410, with the implication being that the mid and high-end Snapdragon 610 and 810 would be on the way at some point, and also support 64-bit.
Some also mistakenly try to point to Android 2.3 Gingerbread as a point where Google trying to push Android into a 64-bit world. When Gingerbread came out about three years ago, Google made it a requirement when compiling the actual Android system software to use a 64-bit environment. But, this requirement didn't actually bring the Android software itself any closer to 64-bit support, it was only done in order to reduce the time it took to build the system software.
Yep. That's it. That's all that has been done. Some of you may have expected that last section to be longer, but so far Google has not been taking many steps to bring 64-bit to Android. In fact, there has been no change to the Android Developers documentation, which still states that “Android is currently expected to run on 32-bit platforms. In theory it could be built for a 64-bit system, but that is not a goal at this time.”
All of the Android runtime libraries (media, graphics, file system, etc) and the drivers for the myriad devices are all 32-bit, and would need to up rebuilt for 64-bit, but this shouldn’t be too difficult to do. Really, I could end this section right here, because that’s all the work that needs to be done to move Android to 64-bit compatibility, at least on Google’s side.
Right now, both the Dalvik VM and ART use a 32-bit register, and there is really no way to change that with the current implementation. But, these registers are abstract entities not related to hardware, so they wouldn’t really cause any problems in switching Android to 64-bit. As stated above, the app code is executed directly, so any apps written in Java would be able to run without issue. At most, an app might have to pass through an interpreter, because of minor differences in coding for 32 and 64-bit in Java. But ultimately, using Dalvik or ART makes it easier for Android to move to new hardware (ARMv7, ARMv8, x86, etc) rather than making it more difficult.
The work that has been done
There are pieces of the puzzle that are already in place for Android. As has been mentioned before, the Android kernel includes 64-bit support, which it has inherited from Linux. It is also known that multiple manufacturers are working on 64-bit processors for the next generation of Android handsets. Samsung let it be known very soon after Apple's announcement of the iPhone 5s and A7 SoC that it was working on a 64-bit version of its Exynos chipset. Qualcomm obviously had a bit of a PR fiasco after Apple's announcement, but then recently introduced its first 64-bit mobile processor, the Snapdragon 410, with the implication being that the mid and high-end Snapdragon 610 and 810 would be on the way at some point, and also support 64-bit.
Some also mistakenly try to point to Android 2.3 Gingerbread as a point where Google trying to push Android into a 64-bit world. When Gingerbread came out about three years ago, Google made it a requirement when compiling the actual Android system software to use a 64-bit environment. But, this requirement didn't actually bring the Android software itself any closer to 64-bit support, it was only done in order to reduce the time it took to build the system software.
The work left to be done
Yep. That's it. That's all that has been done. Some of you may have expected that last section to be longer, but so far Google has not been taking many steps to bring 64-bit to Android. In fact, there has been no change to the Android Developers documentation, which still states that “Android is currently expected to run on 32-bit platforms. In theory it could be built for a 64-bit system, but that is not a goal at this time.”
All of the Android runtime libraries (media, graphics, file system, etc) and the drivers for the myriad devices are all 32-bit, and would need to up rebuilt for 64-bit, but this shouldn’t be too difficult to do. Really, I could end this section right here, because that’s all the work that needs to be done to move Android to 64-bit compatibility, at least on Google’s side.
**Beginning technical section. It has been simplified as much as possible, but feel free to skip down if you don't want to muddle through the jargon.**
Another issue that came up quite a bit in JakeLee’s comments was the fact that Android’s Dalvik Virtual Machine uses a 32-bit register, but that turns out to not really be an issue at all. To simplify the explanation of how an Android app works - a developer will write the app code in Java which gets compiled and packaged as an APK. There are then two ways APK is run on an Android device - either the Dalvik VM will execute it directly as bytecode using the Dalvik just-in-time (JIT) compiler. Or, the new ART (Android Runtime introduced in Android 4.4), Android will move to an ahead-of-time (AOT) runtime, which means the app is broken down to bytecode at the time of installation and only the necessary portions of code will be run at the time it is needed.
Another issue that came up quite a bit in JakeLee’s comments was the fact that Android’s Dalvik Virtual Machine uses a 32-bit register, but that turns out to not really be an issue at all. To simplify the explanation of how an Android app works - a developer will write the app code in Java which gets compiled and packaged as an APK. There are then two ways APK is run on an Android device - either the Dalvik VM will execute it directly as bytecode using the Dalvik just-in-time (JIT) compiler. Or, the new ART (Android Runtime introduced in Android 4.4), Android will move to an ahead-of-time (AOT) runtime, which means the app is broken down to bytecode at the time of installation and only the necessary portions of code will be run at the time it is needed.
Right now, both the Dalvik VM and ART use a 32-bit register, and there is really no way to change that with the current implementation. But, these registers are abstract entities not related to hardware, so they wouldn’t really cause any problems in switching Android to 64-bit. As stated above, the app code is executed directly, so any apps written in Java would be able to run without issue. At most, an app might have to pass through an interpreter, because of minor differences in coding for 32 and 64-bit in Java. But ultimately, using Dalvik or ART makes it easier for Android to move to new hardware (ARMv7, ARMv8, x86, etc) rather than making it more difficult.
**End technical section**
The only real issue that Google would face as far as apps and compatibility is with apps that use Android’s NDK to code with C/C++. Those apps would need to have the native bits rewritten for 64-bit compatibility, or else Android would have to have two different versions of the runtime to accommodate those apps, which could lead to performance and battery life issues.
All of that aside, you hit the only real roadblock, which is the same roadblock that has caused problems with Android since its first days. Google would have to do something that it has never been able to do before with Android - getting developers and manufacturers to follow the plan, not jump the gun on hardware, and push software updates quickly.
This has been a constant struggle for Android, and one that has been getting better over time, but one that still isn't fixed enough to make the transition to 64-bit any easier. As we’ve seen with tablets and multi-core processors, Android hardware makers never want to wait for the system to be optimized before introducing new hardware. Android tablets first shipped well before the system was ready, leading to the forgotten Android 3.0 Honeycomb update, which was just a stop-gap on the way to the proper Android 4.0 Ice Cream Sandwich update.
The real work will be in getting developers to update apps with native code for the new 64-bit platform; but it is obvious that the 64-bit hardware is coming soon, much sooner than it will take Google to update Android for 64-bit. This will lead the whole ecosystem to end up in the same vicious cycle where manufacturers will push hardware before the software is ready, and then will likely be slow to update software once the optimizations are done. The first part of the problem will likely occur not through any fault of Google's, but rather because manufacturers (read: Samsung) will want to make sure they have that 64-bit processor in the newest flagship device - and more importantly, in its marketing campaign - before Android is ready to handle it. Then, once Android does get the update to 64-bit, users will have to wait a bit for manufacturers to push out that update.
Of course, this isn’t necessarily a problem for consumers per se, more of an annoyance for those of us who pay attention and understand the real story. All it means is that we will all be subjected to marketing campaigns touting features that offer no real value, which is nothing new. We've seen plenty of features gracing various marketing campaigns that don't really make much difference to the majority of users, like Air Gestures, Face Unlock, and Siri. Samsung and others will undoubtedly market that their products have 64-bit processors, and will conveniently leave out that they offer little to no benefit because the software isn’t ready. But, that is the way marketing works all around anyway, and the average consumer won’t know the difference anyway.
While hardware manufacturers plan to jump the gun and put out 64-bit hardware running software that isn’t optimized, Google hasn’t mentioned at all when we should expect a 64-bit optimized version of Android. Getting there will doesn’t look to be that rough of a road, but it will certainly take time to get there. So, it’s impossible to say when Android will be fully optimized from top to bottom.
The only real issue that Google would face as far as apps and compatibility is with apps that use Android’s NDK to code with C/C++. Those apps would need to have the native bits rewritten for 64-bit compatibility, or else Android would have to have two different versions of the runtime to accommodate those apps, which could lead to performance and battery life issues.
The same major roadblock as always
All of that aside, you hit the only real roadblock, which is the same roadblock that has caused problems with Android since its first days. Google would have to do something that it has never been able to do before with Android - getting developers and manufacturers to follow the plan, not jump the gun on hardware, and push software updates quickly.
This has been a constant struggle for Android, and one that has been getting better over time, but one that still isn't fixed enough to make the transition to 64-bit any easier. As we’ve seen with tablets and multi-core processors, Android hardware makers never want to wait for the system to be optimized before introducing new hardware. Android tablets first shipped well before the system was ready, leading to the forgotten Android 3.0 Honeycomb update, which was just a stop-gap on the way to the proper Android 4.0 Ice Cream Sandwich update.
The real work will be in getting developers to update apps with native code for the new 64-bit platform; but it is obvious that the 64-bit hardware is coming soon, much sooner than it will take Google to update Android for 64-bit. This will lead the whole ecosystem to end up in the same vicious cycle where manufacturers will push hardware before the software is ready, and then will likely be slow to update software once the optimizations are done. The first part of the problem will likely occur not through any fault of Google's, but rather because manufacturers (read: Samsung) will want to make sure they have that 64-bit processor in the newest flagship device - and more importantly, in its marketing campaign - before Android is ready to handle it. Then, once Android does get the update to 64-bit, users will have to wait a bit for manufacturers to push out that update.
Of course, this isn’t necessarily a problem for consumers per se, more of an annoyance for those of us who pay attention and understand the real story. All it means is that we will all be subjected to marketing campaigns touting features that offer no real value, which is nothing new. We've seen plenty of features gracing various marketing campaigns that don't really make much difference to the majority of users, like Air Gestures, Face Unlock, and Siri. Samsung and others will undoubtedly market that their products have 64-bit processors, and will conveniently leave out that they offer little to no benefit because the software isn’t ready. But, that is the way marketing works all around anyway, and the average consumer won’t know the difference anyway.
A slow path to faster speeds
While hardware manufacturers plan to jump the gun and put out 64-bit hardware running software that isn’t optimized, Google hasn’t mentioned at all when we should expect a 64-bit optimized version of Android. Getting there will doesn’t look to be that rough of a road, but it will certainly take time to get there. So, it’s impossible to say when Android will be fully optimized from top to bottom.
The earliest we could hope to see Android with proper 64-bit support and optimization throughout the system would be in the summer along with the Nexus 7 (2014), but even that is pushing it too much. More likely, we’ll see a minor update to Android 4.4 KitKat at Google I/O, and Android 5.0 (Laffy Taffy, maybe?) with proper 64-bit optimization in the fall with the Nexus 5 (2014). Even then, users will have to wait for manufacturers to update devices; and, to make things worse, that hardware is likely going to be claiming 64-bit on spec sheets well before Android is ready.
All of this needs to be sorted out, because ARM processors are quickly hitting a performance plateau, because of an outdated instruction set architecture (ISA). ARMv8 has introduced a completely new ISA, and made the switch to 64-bit, both changes which will lead to faster speeds as long as software is optimized properly. Unlike on desktops, the argument about hitting the 4GB RAM limit is nowhere near the most important factor when talking about the performance benefits of moving to ARMv8 and 64-bit. Clock speeds can’t get much faster without causing heat and battery issues, and adding more cores will only get you so far, unless they are specialized cores to offload low-power processes, like we’ve seen with the motion and voice coprocessors in the Moto X and iPhone 5s. The most efficient way to increase performance on an ARM chip is to switch to the ARMv8 architecture because it can do the same in a single transfer as 32-bit ARM can in as many as 32 transfers, but that requires the software optimizations before you see the real performance increase.
So, we should all prepare ourselves for a lot of empty promises from Android hardware makers over the next year. But, if we keep an eye on Google, and the news coming out about the official software optimizations, we should get a much better idea of when to expect the real changes. 64-bit is certainly on the way, but the real news will be when Android is properly optimized for ARMv8.
reference: Is Android 32-bit or 64-bit?, Android Developers 1 & 2, +Android Development Community (a special thanks to Bartlomiej Janusz for being so patient with my questions)
All of this needs to be sorted out, because ARM processors are quickly hitting a performance plateau, because of an outdated instruction set architecture (ISA). ARMv8 has introduced a completely new ISA, and made the switch to 64-bit, both changes which will lead to faster speeds as long as software is optimized properly. Unlike on desktops, the argument about hitting the 4GB RAM limit is nowhere near the most important factor when talking about the performance benefits of moving to ARMv8 and 64-bit. Clock speeds can’t get much faster without causing heat and battery issues, and adding more cores will only get you so far, unless they are specialized cores to offload low-power processes, like we’ve seen with the motion and voice coprocessors in the Moto X and iPhone 5s. The most efficient way to increase performance on an ARM chip is to switch to the ARMv8 architecture because it can do the same in a single transfer as 32-bit ARM can in as many as 32 transfers, but that requires the software optimizations before you see the real performance increase.
So, we should all prepare ourselves for a lot of empty promises from Android hardware makers over the next year. But, if we keep an eye on Google, and the news coming out about the official software optimizations, we should get a much better idea of when to expect the real changes. 64-bit is certainly on the way, but the real news will be when Android is properly optimized for ARMv8.
reference: Is Android 32-bit or 64-bit?, Android Developers 1 & 2, +Android Development Community (a special thanks to Bartlomiej Janusz for being so patient with my questions)
Wednesday, September 11, 2013
2013 iPhone buyers guide: How to choose between the iPhone and other phones, including Samsung Galaxy, HTC One, Moto X, Nexus, Nokia Lumia, BlackBerry, and more!
Apple has released the brand new, top-of-the-line, flagship iPhone 5s and less-expensive, colorfully fun iPhone 5c. But is either of them the right phone for you? While everyone here at iMore certainly believes the iPhone is still the best phone for most people, most of the time, we're lucky that every major platform now has one or more great phones for us to choose from as well. The iPhone may have the best overall user experience, the highest quality apps and games, the widest range of services, the biggest selection of accessories, and the best customer support, but there are also things the iPhone doesn't offer that other phones do, like much larger screens, physical keyboards, high power cameras, greater hardware options, or simply no Apple about them. How do you know which one is for you? Keep reading!
Most delightful interface and experience
Apple prioritized iPhone user experience from the get-go. It didn't have as many features as other phones of the time, but it had an interface that made every other phone look obsolete by comparison. From slide to unlock to pinch and zoom, it became a mainstream sensation. Over time, Apple's built on that with everything from FaceTime for incredibly easy video calls to Siri for incredibly engaging voice control. A lot of other companies throw a lot more features at the wall, hoping something sticks. Apple's focus on the best, more coherent, most usable features. iOS 7 makes it even better. They re-built the entire interface on top of a game-style physics and particle engine, so it's even more discoverable, playful, and powerful than ever before.
Plus, with the new iPhone 5s, you get Touch ID, a breakthrough fingerprint scanner that lets you unlock your iPhone and buy from the App Store and iTunes Store without having to enter any long, difficult passwords. Simply touch your finger to the Home button and you're in. And it can recognize up to 5 distinct fingerprints!
Highest quality apps and games
Apple is neck-in-neck when it comes to sheer number of items in the App Store, but they're still way ahead when it comes to the quality of items in the App Store. Sure, every platform has more than its fair share of junk, but the best of the App Store is still unmatched. There's a simple reason for that: Early iOS developers came from the very design-centric, experience-centric Mac developer community. That set the bar very high. Likewise, some of the biggest and best gaming franchises came to the iPhone early, and still come to the iPhone first. While you can get a lot of name brand apps on multiple platforms now, many of the boutique apps are still iOS exclusive, including Tweetbot, Fantastical, Drafts, Screens, Twitterrific, Vesper, Launch Center Pro, Infinity Blade, Tiny Wings, Letterpress, and more. That's not even including Apple's own apps, some of the best in mobile, like GarageBand, and iMovie. Other platforms are attaining breadth. iOS has kept ahead on depth.
Widest range of services
When you get an iPhone, not only do you get instant access to all of Apple's great services, like iCloud backups, and iTunes in the Cloud re-downloads, but you also get access to pretty much all of Google and Microsoft/Nokia's best services - like Gmail, Google Maps, Chrome, Google Drive, Google+, Hangouts, Outlook, SkyDrive, Bing, Skype, Here Maps, and BBM (BlackBerry Messenger) coming soon, and to the best third party services like Dropbox, Box, Spotify, Songza, Pandora, Netflix, Amazon Kindle and video, HBO Go, Hulu Plus, and many more. Apple doesn't offer their stuff on any other phones, but almost everybody offers everything on iPhone.
Biggest selection of accessories
From protective to decorative cases, to macro and wide-angle camera lenses, the choice of iPhone accessories remains the best of any phone on the market. Part of that is due to the iPhones popularity. Part of that is due to Apple releasing new designs only once every couple years, and keeping designs on the shelf for 3-4 years. That means accessory makers can sell the same accessory for a lot of phones, for a long time, which is the best thing in the world for them - and for iPhone owners. Instead of worrying about making something for a wide range of phones, they can concentrate on making a wide range of things for the iPhone. No matter what kind of case you want, what capacity battery charger, what kind of photo mount or lens, what type of Bluetooth accessory, chances are you won't only find it, you'll find several different options to choose from.
Best customer support
If you have an Apple Retail Store near you, there's no point choosing any other phone. Apple will not only sell you an iPhone, but they'll help you set it up and show you how to use it, give you free lessons on all the main features. More importantly, if anything goes wrong, they'll fix it for you or swap it for a new phone, usually while you wait. You can make a Genius Bar appointment, walk in with a broken iPhone, and thanks to Apple customer service and iCloud, walk out half and hour later with a replacement phone containing all of your stuff, that's essentially a clone of the one you walked in with. No one else comes close to matching Apple's level of customer service. Appallingly, no one else even tries.
iMore!
Even though the iPhone's user experience is unmatched, the app, accessory, and services unequaled, and the customer service the best in the business, there's still more you may need. That's where iMore comes in. We'll help you get used to your new iPhone, help you figure out which are the best apps, accessories, and services for you, and help show you all the things you can do with it, like photography, music, and more. And when you're ready, we'll help you upgrade to your next phone. Whether you keep up with us on the web, with our iPhone app, or via RSS, Twitter, App.net, Facebook, Google+iMore, YouTube, or iTunes, or some other way, you'll quickly find out the iPhone doesn't only come with great stuff, it comes with a great community!
Who should get the iPhone?
If you want a phone that just works, and that has all the great user experience, app and game, accessory and services, customer support and iMore community benefits, then the iPhone is for you. It's smaller than many competitors these days, doesn't have a hardware keyboard, and there's no giant camera bolted on, but it remains the single best phone in the world at what it does, and what it does it does very, very well.
Unless you have a very specific set of requirements or use cases that make something else a better option for you - see below - get an iPhone. You'll be glad you did.
Who should get Android instead?
If you absolutely need a bigger screen, anything from 4.3-inches all the way up to 6-inch "phablets", you should get Android instead. Apple probably won't make any iPhone that size until 2014 at the earliest, so if you need something between a phone and a tablet, and can't afford both, or if you need something that emphasizes the computing device more than the mobile phone aspect, you'll have to go elsewhere. Both the 4.7-inch HTC One and the ironically named 4.3-inch HTC Mini are great phones with excellent build quality. Samsung isn't quite as well made, but the 5-inch Galaxy S4 and the 6-inch Galaxy Mega are extremely popular and very large respectively. Google's Moto X provides a big screen in a small package and includes highly customizable back plates. LG's Nexus is the best option for those who want a big screen and a stock Android experience.
Who should get BlackBerry instead?
If a physical keyboard and a focus on communications above everything else are a deal-breaker for you, then Apple's iPhone will never fit your needs. BlackBerry, however, is phenomenal at hardware keyboards. They also rebooted their operating system, bringing them fully into the era of modern smartphone. The BlackBerry Q10 is currently the latest, greatest high-end keyboard BlackBerry. The BlackBerry Q5 is lower-end but still terrifically tactile. If you simply insist on being old school, a few BlackBerry 7 devices remain on the market as well.
Who should get Windows Phone instead?
Windows Phones come in a variety of screen sizes and price points, and all run Microsoft's elegant Metro (sticking with it!) interface and experience. The biggest reason to go with Windows Phone - literally - is the amazing camera available on the Lumia 1020. It's almost like they grafted a dedicated point-and-shoot onto the body of a phone. It's also got a big screen and some of the best build quality in the business.
Still undecided?
If you're still not sure about the iPhone 5s or iPhone 5c - or even the still-on-the-market iPhone 4S! - jump into our iPhone discussion forums and the best community in mobile will happily help you out. If you're not sure in general, head on over to your local big box or carrier show and ask to try them out. Don't settle for dummy phones, ask to use demo units, and ask a lot of questions. Then dive into Android Central, Windows Phone Central, and CrackBerry and the experts there will help you make a final, fantastic decision
Saturday, July 27, 2013
There's a division in the world of smartphones. There are phones that
are normal-sized and phones that are super-sized. You will like one
type or the other, more than likely, and we naturally seem to fall into
the latter, rather liking the bigger phones such as the HTC One, Galaxy
S4 and the Note II. But what if you're not a monster-phone fan? What
then?
Then say hello to the Samsung Galaxy S4 Mini, or from here on, SGS4
Mini or just, plain Mini. This phone is designed to offer the features
of its bigger sibling but with a more compact footprint and a marginally
cheaper price. It could be ideal then, but like anything, there could
also be some downsides.
Less screen, less power and less storage
The first and most obvious thing to understand is that the Mini has
less power than the standard SGS4. We're not talking massive differences
here, but you're certainly not getting a Galaxy S4 shrunken down to
iPhone size, although the device is, in terms of dimensions, pretty
close to the iPhone.
In terms of specs, what you get in the Mini is a dual-core, compared
to the SGS 4's quad-core. There's 1.5GB of RAM, which is half-a-gig less
than in the full-sized phone, and you get a maximum of 8GB of storage.
In fact, the storage situation is slightly worse than that, because
there's only 5GB available to the user.
We used to dismiss the internal storage moans of some people,
especially when handsets had the option of adding a microSD card, but
things are changing, and it appears that Google really wants to get away
from external storage. For one thing, it's no longer possible to move
apps to the SD card on a standard phone. This is a problem, because some
games and the like are absolutely massive. Real Racing 3 and The Dark
Knight Rises are over 1GB each, in fact, Batman clocks in at 1.8GB.
Install both those games and a few other apps, some photos and you're
officially done.
To access that microSD card slot, just pop the back off the phone,
remove the battery and you'll see the micro SIM and SD card sockets.
It's worth noting, in some regions, this handset is available with
dual-SIM slots, something we'd quite like to see in the UK.
Gorgeous screen
Although the pixel density here is lower than the SGS4, we adore this
screen. The AMOLED does what it does, and has those colours that are
super-vivid, this is great for normal phone stuff, but when it comes to
photos and videos, it's hardly super-accurate. Even so, it works well
and has plenty of brightness.
Although the screen is small, typing is okay, but you have to use one
hand. We're used to the Note II, which is a two-handed affair, but try
that here and you'll end up with nonsense instead of words. But the
phone is small enough to use with one hand, so this all makes plenty of
sense.
The detail is amazing though, and despite having only a 540 x 960
resolution 4.3-inch screen, that's still got 256ppi which is a decent
amount. You could, if you wanted, compare that to the 441ppi on the
SGS4, but even so it manages to look pretty stunning. Proving, we
suppose, that there's a lot more to a screen than just a number.
Samsung vs. Android
Some pundits have noted that, for the most part, Samsung doesn't
really want to be associated with Android. The firm does all it can to
differentiate its product from the Google Android look and feel. This is
something of a double-edged sword, because Samsung brings an enormous
amount to its phones, and this is all stuff that's not possible with
vanilla Android.
On the flipside, the look of Android with Touchwiz is not something
that goes down well with everyone. For one, we get quite tired of
Samsung's insistence that everything has an S in front of it. S Voice, S
Translator, S Memo and, easily the worst and most counter productive: S
Planner (it's a calendar). S Planner is awful to use, but you can get
the proper Google Calendar app in the app store, so no harm, no foul.
Despite the silly names, almost all of Samsung's apps are really
good. S Translate is well done, simple to use and you can opt to
download HD voices that improve the spoken quality of translations.
What's more, you can control S Translate with your voice - speak English
to it, and it will transcribe what you say, and present a translation.
And, the same in reverse. This is the closest thing to the Star Trek
universal translator you can imagine, and it's possible now, in a
handset that costs a few hundred quid. If that doesn't impress the hell
out of you, you're already dead inside.
We've used "car mode" for navigating too, and it's clever. What it
does is give you the usual S-Voice interface, but it remains permanently
active, waiting for you to say "Hi galaxy" or your own
wake up phrase, when you do this, you can use the phone through voice
command. Ask it to find you a petrol station, and it will do so and push
the answer to Google Maps. It's actually really good, and a feature
that a lot of people probably ignore. It munches battery though, so be
careful.
One thing that does continue to annoy slightly, though, is the
Samsung notion that it must have a duplicate of every Google service.
Presumably, if Samsung thought it could get away with it, it would
remove the Play music, video, app and bookstores, and just use its own.
But it can't do that, and keep the "Google experience" so it has two of
everything.
There's a Samsung apps store, which keeps the Samsung apps
up-to-date, and which you are therefore forced to use. There's the
Samsung Hub, which contains the book, movie, game and music stores. This
is all just the Google Play suite all over again, with vaguely
different selections that add to the confusion of media rights
ownership.
And then there's the Samsung account thing. You have a Google
account, but Samsung also wants you to have a Samsung account. Without
it, you can't access the Samsung stores - perhaps no bad thing - but
it's yet another account to sign in with, and to remember the password
for. It's a pain, and it's redundant.
None of this spoils the device, but it does make Apple look good,
because its product has one of everything. That might be locked down too
far for some, but it's a lot simpler for the customer.
Group Play
One of the features that Samsung has promoted heavily, is Group Play.
The idea here is that multiple Samsung devices can be paired and
combined to play music together. It's a sort of "down-and-dirty" way of
making a speaker system out of phones.
Obviously, you need to have Samsung phones to make this work, and
they need to be recent ones, running the latest software. In Samsung's
world, this is no problem, because everyone has Samsung phones, and
everyone has the lastest software. In the real world, that's unlikely.
We tested it with two recent Sammys, and the results were, honestly, a
bit mixed. The pairing is easy, and you'll have them working together
in no time at all. It sort of works by joining one wireless AP, and
that's all fine. What we did find though, is that the music wasn't quite
synced perfectly. It was really hard to tell by how much they were out,
or which one was fast and which was slow, but the music just didn't
sound right.
It's a nice idea, but it needs some tweaking to really be of much use.
Performance
One of the things we have noticed on the Mini, is just how slick the
Samsung implementation is now. TouchWiz feels more lively and looks more
pretty than stock Android, at least in some regards. Hit the multitask
button, for example, and the dominant window beautifully reduces in size
to show the list of recent apps. Press the one you want, and it
smoothly expands. It's a small thing, but it gives the phone a really
solid feeling.
Speaking generally, in terms of the way the phone runs, it feels to
us as slick as the SGS4, and it's doing that on a processor that's much
less advanced, and with less memory. It really is very impressive, and
it means that anyone buying this phone will feel they're getting a mini
Galaxy S4 experience, rather than a budget experience - which at this
price would have been awful.
We also played some 1080p video, with DTS sound, and it worked. This
is high-bitrate 1080p too, and we have to say that this is seriously
impressive. Of course, 1080p is a bit of a waste on a phone this size,
but what it does do is prove that Samsung understands what consumers
might want, and it gears its devices up accordingly. So both games, and
HD video work really well on this phone, and that's something that
matters to us, and a lot of other people.
Camera
As with most phone cameras, there are a lot of possible options here.
There are two groups: the more sensible shooting modes, which include
HDR, auto and sport, and the silly filter stuff that makes your £300
phone look like a pinhole effort from the 1900s. Filters schmilters,
that's what we say, but you might use them if you hate photography and
want it to die in a filtered mess.
The camera itself is nice to use. It's not a megapixel monster or
anything, but the images it produces have a natural look to them, with
nice colours and plenty of detail. None of that budget phone camera
stuff here, just a really nice crisp image.
The front-mounted camera is fine for selfies, although any
self-respecting duckface should really be pulled in a mirror, with the
rear camera. It's also decent enough for video calls, like anyone
bothers with those.
Call quality
One thing that really did strike us was just how good this phone was
at being a phone. Calls were really nice-sounding. There was plenty of
volume, and the quality was absolutely great. It's nice to use as a
phone, because its size and shape lend it to being pushed against your
ear. This is something missing from larger phones like the Note, and
even the full-sized Galaxy S4. If you're on the phone a lot, we can't
name a handset that's nicer to use than this one.
Battery
There's something odd going on with the Mini, but the battery life -
even with all the gubbins turned on - is really good. We had two email
accounts pushing our mail to us, Frequent messing about with the screen
on, playing Real Racing 3, forgetting to close Real Racing 3 so it was
running - and playing music - for 30 minutes. We used it for text
messages, and calls, and at the end of the day, it's only 38 per cent
drained after 16 hours.
Now, caveat time. We used the phone, and installed a bunch of our
favourite apps, but this was not like our day-to-day phone, which has
all manner of things installed, and now doesn't see a day out, despite
having as much as two-day capacity when new. Some of this might be
battery stability over time, and some of it will be because we have a
lot of stupid apps running, but even so, from a base level the Mini has
impressed us, far more than other phone put in the same position.
Friday, July 5, 2013
Firmware details:
PDA: P5100XXDMC3
CSC: P5100XEFDMA2
PDA: P5100XXDMC3
CSC: P5100XEFDMA2
Version: Android 4.1.2
Check this firmwares first :)
Region supported: Austria, Belgium,France,Germany,UK and More.
The users who fail to update the device automatically,follow the following guide to install update manually.
Check this firmwares first :)
Region supported: Austria, Belgium,France,Germany,UK and More.
The users who fail to update the device automatically,follow the following guide to install update manually.
REQUIREMENTS:
1) Install Tab 2 10.1 USB drivers in computer
2) Enable USB debugging mode from setting.
3) Backup all required data.
4) Tab should be unlocked/rooted.
5) Battery should be full.If battery ends during process it will be results in damage your Tab.
1) Install Tab 2 10.1 USB drivers in computer
2) Enable USB debugging mode from setting.
3) Backup all required data.
4) Tab should be unlocked/rooted.
5) Battery should be full.If battery ends during process it will be results in damage your Tab.
PROCEDURE:
1) Download update first from here.And extract the files.
2) Download Odin3 v3.07 from here.And extract it also.
3) Turn off the Tab and go to download mode.
4) Run Odin 3 from the PC
5) Connect the Galaxy Tab 2 to the PC.
6) Now select these files extracted from the update [XXDMC3] folder to install on the tablet
I] Click on the PDA button and select file with .tar extension.
II] Click on the Phone button and select file with name MODEM.
III] Click the CSC button and select file with name CSC.
IV] Click the PIT button and select thefile with extension .pit its done
Ignore if last three file are not found
7) In Odin,verify that Auto Reboot and F.Reset Time checkboxes are selected. Leave Re-Partition option
8) Hit the start button and installation process will be start and it will take some time.
9)If it say installation successfull then reboot the Tab and remove it from PC.
Enjoy new jelly bean 4.1.2update
I AM NOT RESPONSIBLE FOR ANY KIND OF DAMAGE. :) :) :)
1) Download update first from here.And extract the files.
2) Download Odin3 v3.07 from here.And extract it also.
3) Turn off the Tab and go to download mode.
4) Run Odin 3 from the PC
5) Connect the Galaxy Tab 2 to the PC.
6) Now select these files extracted from the update [XXDMC3] folder to install on the tablet
I] Click on the PDA button and select file with .tar extension.
II] Click on the Phone button and select file with name MODEM.
III] Click the CSC button and select file with name CSC.
IV] Click the PIT button and select thefile with extension .pit its done
Ignore if last three file are not found
7) In Odin,verify that Auto Reboot and F.Reset Time checkboxes are selected. Leave Re-Partition option
8) Hit the start button and installation process will be start and it will take some time.
9)If it say installation successfull then reboot the Tab and remove it from PC.
Enjoy new jelly bean 4.1.2update
I AM NOT RESPONSIBLE FOR ANY KIND OF DAMAGE. :) :) :)
1]USB drivers for Samsung galaxy s3 I9300 to transfer files from device to computer Download
2]Download Root Package for Samsung Galaxy S3(CF-Root-SGS3-v6.4.zip) Download
3]Download Odin v1.85 for samsung galaxy s3 firmware Download
1]Download and extract all the above files to the computer.
2]Make sure that the your phone is based on the XXUFME3 firmware.
3] Take backup of your phone data for safety.
4]Charging of phone should be above 80%.
5]Now switch of the samsung galaxy s3 and enters into the download mode by pressing and holding Volume down button and menu button together and then press power button until triangle is appear.Again press power button to continue.
6]Launch Odin on computer (Run as Administrator)
7]Now connect device to the computer by using USB cable.
8]Wait till Odin shows ID: COM box turn to yellow and showing computer port number.This means connection is successfully established.
9]Then in Odin select PDA button and select the file CF-Root-SGS3-v6.4.zip
10]Confirm that the Auto-Reboot and F.Reset Time Check-boxes are selected .And do not select Re-Partition check box .
11]Now click on the start button in Odin to start installation or rooting.It may take some minutes.
12]After installation complted,phone will be restart automatically and then disconnect the USB from the computer.
13]Now Enjoy,you have have successfully rooted.
Disclaimer:
2]Make sure that the your phone is based on the XXUFME3 firmware.
3] Take backup of your phone data for safety.
4]Charging of phone should be above 80%.
5]Now switch of the samsung galaxy s3 and enters into the download mode by pressing and holding Volume down button and menu button together and then press power button until triangle is appear.Again press power button to continue.
6]Launch Odin on computer (Run as Administrator)
7]Now connect device to the computer by using USB cable.
8]Wait till Odin shows ID: COM box turn to yellow and showing computer port number.This means connection is successfully established.
9]Then in Odin select PDA button and select the file CF-Root-SGS3-v6.4.zip
10]Confirm that the Auto-Reboot and F.Reset Time Check-boxes are selected .And do not select Re-Partition check box .
11]Now click on the start button in Odin to start installation or rooting.It may take some minutes.
12]After installation complted,phone will be restart automatically and then disconnect the USB from the computer.
13]Now Enjoy,you have have successfully rooted.
Disclaimer:
Author Is Not Responsible For Any Kind of Damage To Your Phone And Illegal Use By Users.
Thursday, July 4, 2013
Hello Guys,
I have written this post to tell you something about a Contactive-Universal caller ID android application.This is an awesome application that becomes popular in few days and being popular day by day.The idea behind the application is just great, and the application really delivers what was demanded.Now all of you may be thinking that what exactly it does?
What Contactive Actually Does?
It is simple and mind blowing.If you have call from your friend,you can able to see your friend name and number only.But if you have installed Contactive-Universal caller ID application in your android phone it will automatically search online contactive web dictionary and automatically gives the detail of your friends social network account.Contactive gets its data from Facebook, Twitter, LinkedIn, Gmail, Yelp, Google Places, White/Yellow Pages, and Contactives Global Directory.I found that most of the times the data given by Contactive was right.There are more than seven billion telephone numbers in the world, and a massive amount of web content to crawl, to match each phone number with social network identities,and return that information within seconds to your.Contactive combines all of your phone contacts, social media connections and its very own database of information to provide an address book that is constantly updating itself, and a highly advanced caller ID system.This ability of application make it perfect than other applications.
Interface,Design and Performance:
You can eventually get in love with the UI of the Application.Contactive is easy to understand and easy to setup,It contain user friendly menu system.Profile picture of user are well displayed and every part of application give brilliant response to operator.Searching of friends and family is become now more easy.Keypad section also works well.Overall performance of this application is best.
Final Words:
To conclude, Contactive is an easy to use, yet surprisingly powerful address book app, allowing excellent, meaningful links to social media, friends and family.The app is extremely easy to use, with a quick and easy set up process. Contactive grows your contact list in real time, automatically updating as you make more friends on Facebook, or connections on LinkedIn. It is truly an address book like no other.
Requires Android Version : 2.2 and up
- Download Contactive - Free Caller ID
- Website: http://www.contactive.com
- Demo Video: http://www.youtube.com/watch?v=A07P_tDDQyA
- Play Store: http://bit.ly/14gRD3F







