Showing posts with label Android Police. Show all posts
Showing posts with label Android Police. Show all posts

Thursday, July 13, 2017

Is This Google’s 2nd Generation Pixel XL, Made By LG




According to Android Police the above image is said to be that of the 2nd generation Google Pixel XL, that is codenamed “taimen” made by LG.

As you can see from the design, this looks a lot like the phone that an XDA member leaked a couple of weeks ago.

According to Android Police's sources, this is the phone that LG has made for Google in place of the HTC made “muskie” that was once thought to be the new Google Pixel XL. It rumored to have a 6 inch LG made AMOLED display with a 2:1 ratio. 

It is also rumored that the new LG made Google Pixel XL phone will sport squeezable sides, just like we've seen on the HTC U11 which will allow you to interact with the phone.


Source: Android Police

Friday, April 26, 2013

Google Android 4.3, Jelly Bean Spotted In Server Logs




  1. Specifically, the build I'm seeing floating around our server logs is Android 4.3 JWR23B, which indicates this is still Jelly Bean (the first letter of the build is always the same as the first letter of the Android version name).
    Now, you might say that server logs can be easily faked, and it happens all the time. You'd be absolutely right, which is why I would have never posted this had I not traced the IP range to Google itself. In fact, 2 different IP ranges, both corresponding to Google employees. Employees that have a lot to do with Android. It's the same IP range that had previously clued us in to some of the unreleased versions of Android before they were announced.
  2. The Android 4.3 devices I've seen so far are Nexus 4 and Nexus 7.
  3. Furthermore, and this was the original tip that prompted me to look for more clues, there are several very recent comments in the official Chromium bug tracker that list JWR23B as a build number, giving more credibility to this finding. The person who left the comments is a Chromium developer, which suggests affinity to Google, once again.

So, what does this all mean?
  1. Google doesn't assign version numbers to Android releases until a short time before they're set to be unveiled. We're talking weeks or a couple of months max.
  2. Google does not assign version numbers to internal/test releases. Those are usually called something like Jelly Bean MR1 and then assigned proper versions number when they're close to release.
  3. Android 4.3 started appearing in the logs recently, while Android 5.X is nowhere to be found, and neither are any K***** builds.
  4. Google I/O is in less than a month.
  5. Everyone has been expecting Google to unveil the newest version of Android at the conference, as Google has traditionally done in the past. Most have suggested that it would be Android 5.0, Key Lime Pie, or some other dessert starting with K, meaning a big leap from Jelly Bean, usually requiring app compatibility updates and bringing serious architectural changes. Think Android 3.0 compared to 2.X and Android 4.0 compared to 2.X and 3.X.
  6. Recently, a rumor started floating around that the next major revision is going to be delayed to give OEMs (and developers) some breathing space.
  7. We now know that Google is working on Android 4.3, which is still Jelly Bean. Today's findings suggest (this part is in my opinion, not a fact) that the company is going to unveil 4.3 and not 5.X at Google I/O. I may end up being wrong on this one, but all the clues are lining up pretty well to fit this theory.
  8. The versioning likely points to OS changes that are not too drastic for developers to adapt their apps to and OEMs to upgrade devices to. Think Android 2.0 -> 2.1, 2.1 -> 2.2, 4.0 -> 4.1, and 4.1 -> 4.2 (especially the latter). This is a good thing - as we know, Jelly Bean can be found on only 25% of devices, and that's after Google reworked the algorithm used to report these numbers.


Monday, March 18, 2013

Google Keep Note Taking App Spotted


Google, as a service provider, tries to cover all aspects of an online life a person could have, providing all the services. If you think of it, the company has the best known search engine and the best known email service. There is also a very good social networking site, a very good operating system for computers and a very popular operating system for mobile device, a very powerful, secure, and stable internet browser, cloud apps, cloud services for business, solutions for almost every kind of need a business could have. When such is the situation, it will be hard at work to try its luck with other popular online services.

With the success of Evernote, it is pretty obvious that people are very serious about taking digital notes on their computers or mobile devices, and they are doing this very much using Evernote. So it is only very evident that Google would want to try this service as well, after its Notebook service failed. The service we are talking about is Google Keep.

If you have heard of this before, you are not alone. This is because we have heard the name and seen the logo before. But according to a post on Android Police, the service was briefly up on http://drive.google.com/keep and that just means that we have to keep an eye on it. Also, the web publication features the above screenshot of the service which was submitted by a Google+ user.

Last year, the search engine giant accidentally leaked a screenshot on its Google Plus page which had a link labelled, “save to Google Keep.” Now, even though we do have anything like that, we have this official image to hold on to. And until the company makes any official announcement this is all we have.



Source: The Verge