How To Remove Number From Truecaller Directory List

As we are using PC and Smartphone in day to day to routine. These devices makes our life simple and easy. We access internet on these devices and access useful services to get information and entertainment. Many Websites, apps, games are available for our devices. Smartphone apps are increasing rapidly after Android OS comes into market. Android is an open source OS for mobile devices so it attracts developers. Millions of different apps are available in Play Store. I already listed out some best android apps and for games lovers also listed out best android games. Even Many apps are available which help to find many useful information.

Basic purpose of mobile is calling so we their are some apps which helps to enhance the calling feature. Like we all want to know who is calling from unknown mobile number. There are many websites available on internet to get this information. But for smartphone Truecaller is one the popular app to trace a mobile user location and name. Truecaller has global phone number directory. You can easily trace the number when you get call from unknown number. But Truecaller totally destroy your phone number privacy. If you call to unknown person by mistake or dialed any wrong number then it will becomes serious issue. So to secure mobile number details we need to remove it. Our main motive is to secure and maintain our number privacy. If you want to know how to remove your number from Truecaller then read this article because today we are going to discuss the method to remove number from Truecaller database.

Method To Remove Your Number From Truecaller Directory.

Step 1. Open your Web browser and type the following URL without Quotes and press Enter.

http://www.truecaller.com/unlist

Step 2. Now you see the Truecaller Unlist Phone Number Webpage. Scroll the page down.

Step 3. In this Page you have to select some options like reason, verification captcha and verification code and enter your Phone Number etc.

Step 4. After filling the form you have to click on the blue unlist Button After that your number is successfully removed from Truecaller database.

Note:- Before Removing your number You have to deactivate your Truecaller account so that Truecaller verify that your the actual owner the number.

I hope you like this method and successfully removed number from Truecaller app. Don't forget to share it with others.

BSNL to set up 40,000 Wi-Fi hotspots

BSNL to set up 40,000 Wi-Fi hotspots

Union Minister for Communications Ravi Shankar Prasad launches Wi-Fi Interet facility in the Taj Mahal complex.

Bharat Sanchar Nigam Ltd. plans to set up 40,000 Wi-Fi hotspots across the country in three years at a cost of Rs. 6,000 crore to provide seamless Internet connectivity.

The plan is part of efforts revive the company, Telecom Minister Ravi Shankar Prasad said on the sidelines of the launch of Wi-Fi at Taj Mahal on Tuesday.

Anupam Srivastava, Chairman and Managing Director, BSNL, said the tender for the project was likely to be floated by July.

“Initially, we plan to set up the hotspots in PPP [public-private partnership] mode. The investment made by private operators will be in addition to ours,” he said.

The public sector company will set up another 2,500 Wi-Fi hotspots in 250 tourist and religious locations at a cost of Rs. 500 crore by next March. These include the Jaganath temple in Puri, Nasik (where Khumb Mela is held), Khajuraho, Fatehpur Sikri and Hampi.

At Taj Mahal, the company’s Wi-Fi service will be free for 30 minutes during a 24-hour block three times a month, which visitors can utilise in multiple sessions. After the free usage, a subscriber can continue using the service by opting for subscription plans of Rs. 20 to Rs. 70 valid from 30 minutes to a day.

Facebook's new photo app uses facial recognition technology

Social networking site Facebook has launched a standalone photo sharing app that makes use of facial recognition technology.

The app called 'Moments' will allow Apple and Android users to quickly share pictures privately among friends who are in the frame as the app sifts through images using facial recognition, somewhat similar to the "tagging" feature on Facebook .

Product manager Will Ruben in his blog post, explaining the usability of the app, said at any group outing or wedding, friends try and get the same group picture clicked from their respective smartphones as sharing the pictures later is cumbersome.

"Now sharing the pictures of your friends from your smartphone and getting the ones that your friends clicked with you in the group will be easy," he said.

The app also allows you to create groups and syncs photos of your friends. This will ensure easy access to pictures clicked from multiple smartphones.

'Moments', launched in United States on Monday, is expected to be rolled out in other countries over time.

from:http://businesstoday.intoday.in/story/facebooks-new-photo-app-uses-facial-recognition-technology/1/220617.html

FACEBOOK IS ABOUT TO CHANGE YOUR LIFE AGAIN!

All those secret stalkers out there, it’s time to be a little more careful about your tendencies. Facebook has announced a new development, and this update is about to blow your mind.

Source : coryhall

Now stories on which you linger for longer than usual will appear on the newsfeed of your friends because Facebook believes that it is worth sharing, and engaging.

While this may not be a move to hinder casual stalking, it sure will affect the way we use Facebook.

The update is a result of trying to bring to light those posts which people spend time reading, but do not comment or share because they might not want to indulge into debate or controversy. This is an attempt to highlight such valuable content to the forefront.

Source : tumblr

So next time you stare at your ex’s status for more than usual, be careful! Facebook is watching you, and so are the friends on your list!

Latest Android wear update brings serious relevance to wearables

A new update is making its way into Android wear (specifically the LG Watch Urbane, Moto 360, Sony Smartwatch 3, and the Samsung Gear Live) that does something very special--activates dormant Wi-Fi chips.

That's right, dormant Wi-Fi chips will now be active.

There are plenty of other updates worthy of mention:

1. Ability to pair more than one wearable to a single phone
2. Wrist-flicking gesture support
3. Apps remain visible until dismissed
4. Swipe left to access apps and contacts
5. Receive notifications, even when you're using something else on the wearable
6. Emoji drawing
7. Apps can work in black and white ambient mode

But even with the list of improvements, it is still the activation of the Wi-Fi chips that should have your interest piqued. Why? Until now, the only way to receive notifications from your phone was if the phone was near enough to the wearable for a bluetooth connection. That limitation is now gone. As long as your wearable is connected to a wireless network, notifications on the wearable will update. Your phone could be miles away and you'll still get updates.

The playing field for Android wearables has now become far more interesting. Consider this scenario: You don't have your phone with you. You're wearing your smartwatch and you're connected to a wireless network. On that wearable you have a VOIP app (not that one exists at the moment). You open open the app and place a call.

Another idea: You've left the office for lunch and neglected to bring your phone. You need to set a reminder. You have your watch and a nearby wireless. Set the reminder and allow that wireless connection to send said reminder to your smartphone.

The tether has been severed. The possibilities for Android wearables and mobility have shattered the ceiling. What this does is open wide the door for users not having to even carry their phones with them, enjoy much faster data transfer speeds, interaction with network-aware devices, the list goes on and on.

Anyone that has worked with bluetooth enough knows how flaky it can be. It's always been one of those ideas that is far better on paper than in reality. Wi-fi, on the other hand, works and works well. By activating wireless on smartwatches, Google has ensured their wearables will enjoy greater features, speed, and reliability.

I firmly believe that Google was smart to withhold Wi-fi until now. Not only is this the perfect time, due to the Apple Watch, the software stack itself is only now evolving into a truly solid and viable platform. With the addition of Wi-Fi, Android Wear could easily rise above Apple's entry in the wearable platform.

NOTE: How do you enable Wi-Fi? If you happen to have one of the supported devices, all you need to do is enable Cloud sync and wireless come to life.

Some have proclaimed the awakening of Wi-Fi to be a moment of panic on Google's part. With the Apple Watch out and selling well, many feel Google was desperate to add something new and shiny to the table. Thing is, Wi-Fi on Android wear was announced quite some time ago. This is Google making good on a promise and that promise will make good on the Android wear platform.

Although I am still skeptical about the whole of wearables, that skepticism is growing thinner and thinner every six or so weeks. Now that the hardware is up to the spec of the platform, it's now time for Google to concentrate its wearable efforts on the software side of things. Android wear needs third-party apps to really bring the platform to life--third-party apps that can seriously take advantage of available wireless.

If you happen to have a supported device, the Wi-fi activating update should start trickling in over the next few weeks. Once your Android wear device is wireless-ready, you'll most likely feel like you are dealing with a completely different platform.

What do you think? Is the addition of wireless connectivity to Android wear a game changer? Or is the wearable platform destined to fall?

Apple`s Metal API Comes for to OS X Desktop

At last year’s WWDC, Apple introduced their Metal API for iOS 8. A low-level graphics API, Metal was originally designed to bring the benefits of low-level graphics programming to Apple’s mobile operating system. And while we typically don’t think of mobile devices as being GPU-bound, in reality Apple has been packing some relatively powerful GPUs like GXA6850 with what are relatively speaking still fairly weak CPUs, which means Apple has ended up in a situation where they can be CPU-bottlenecked on draw calls.

Metal, despite being the 3rd such low-level API to be introduced, was the first to reach production status. Microsoft’s DirectX 12 is arguably not there yet (Windows 10 is still in testing), and Khronos’s Vulkan was still in its primordial Mantle form at this point in 2014. What this means is that out of all of the vendors, it’s arguably Apple who has the lead time advantage in low-level API development. Which is why for the last year we have been wondering if Metal would stay on iOS, or make the jump to OS X.

Yesterday we got our answer, with the announcement from Apple that Metal would be coming to OS X “10.11” El Capitan, and that it would be part of a larger investment into Metal for the company. Along with bringing Metal to OS X, Apple is going to be releasing new API kits that interface with Metal to simplify development, and internally Apple is now using Metal (when available) for parts of the desktop composition rendering chain. At this point it’s fair to say that Apple has gone all-in on Metal.

Consequently the fact that Metal is now over on OS X is not unexpected, but whether it has been planned for or not, it means that we now have 3 low-level APIs on the desktop as well as mobile. OS X’s Metal will be going head-to-head with Microsoft’s DirectX 12 and Khronos’s Vulkan, and this is the first time in a very long that we have seen a viable and competitive 3rd graphics API on the desktop, as DirectX and OpenGL have been the reigning APIs since the turn of the millennium.

Metal's Introduction At WWDC 2014 (Image Courtesy Apple Insider)

As for what this means for Mac users, in the short run it’s a good thing. With Vulkan still in development, had Apple not implemented Metal on OS X, OS X would have needed to stick with classic OpenGL for another year until OS X 10.12. Going with their own API, as was the case with mobile, gets a low-level API on OS X sooner. Furthermore because it’s been on iOS for the last year, Apple gets to leverage all of the developer experience and code already written for Metal, and bring that over to OS X. Which is why developers like Epic are able to show off engines using Metal on OS X so early.

In the long run however there are some big unknowns left to answer, which could have a big impact on how things play out. Apple has not yet released the complete documentation for the newest version of Metal – specifically, we don’t have feature lists – so how the Mac and iOS versions compare feature-wise remains to be seen. My biggest concern here is that Apple will put OS X and iOS at parity, essentially limiting the features available to the lowest common denominator of iOS, leading to Macs in general being behind the curve in graphics features. The other big question is whether Apple will support Vulkan next year once it’s done, or whether they will stick with Metal, essentially turning OS X’s graphics stack proprietary. Which for users could lead to a reduction in game ports to the Mac if developers have to go write against a Mac-specific graphics API.

Apple iOS Metal Thread Model

One thing that is a pretty sure bet at this point is the GPUs that will support Metal. In short, don’t expect to see anything that can’t support Vulkan support Metal due to a lack of necessary features. So I’m expecting Metal compatibility to start with Intel’s Haswell (Gen 7.5) iGPUs, AMD’s GCN dGPUs, and NVIDIA’s Fermi/Kepler dGPUs. El Capitan works on a much wider range of machines of course, so this means only a fraction of those machines get to experience Metal. Though this was the same situation on mobile as well.

As for developers, things will be interesting. As I mentioned before Apple seems to be going all-in on Metal, starting with the fact that they will have Metal back-ends for their Core Graphics and Core Animation frameworks. And actually I’m a bit surprised by this, as basic compositing is not something that is draw call limited. Apple is claiming upwards of 50% performance increases here, so I’m curious just how this works out, but I suspect these are based on low-level benchmarks. Draw call performance is not the only benefit of Metal, but it is the most immediate, so Apple may be leveraging the harder to get GPU benefits here, or just wringing every last Joule of power out by getting to an API that isn't doing high-level state checking.

OS X Metal Performance Improvements: From Apple's Promotional Materials

In any case, by building Core frameworks off of Metal, Apple is in a position where they have to ensure Metal drivers are working well, which is to the benefit of developers. Meanwhile Apple is going one step past Metal on iOS 8 with the release of MetalKit, which is a set of utility functions for Metal to help speed Metal development. As we’ve mentioned before one of the few real pitfalls of low-level APIs is that to best utilize them you need guru-level programmers – after all, the API doesn’t have high-level safety nets to keep developers out of trouble – and with MetalKit Apple is at least partially resolving this issue by providing some base functionality for programmers.

Wrapping things up, though not an unexpected move from Apple, it will none the less be interesting to see how their efforts with Metal go. As a tightly integrated vendor they have the advantage of being able to move quickly when they choose to, which is why we’re seeing Metal come to OS X so soon and to get used by Core OS components so soon. Metal is just a graphics API, but due to Apple’s timing OS X will be the real test for low-level APIs on the desktop, and not just for gaming. Apple is in an interesting position to take advantage of these new APIs like no one else can, so in several ways they are going to be the pathfinder on just what can be done with these APIs.