Skip to main content

Google expected to launch Pixel 2!


Google is prepping to launch the Pixel 2 and Pixel XL 2 in October, specifically October 5. At least that's according to Twitter tipster @evleaks, aka Evan Blass, who has proven a reliable source on pretty much everything in the past, so we think this is 100% legit. 

Pixel XL 2 will be manufactured by LG, while Pixel 2 will be made by HTC

virtually bezel-less display

Google Pixel XL 2 won’t be the only smartphone with a bezel-less display. Samsung Galaxy S8, S8+ already have Infinity Displays with no bezels on the sides and reduced bezels on top. The newly launched Galaxy Note 8 also has the same display. Apple iPhone 8 is also supposed to get rid of the bezels and opt for a full-frontal display with no home button. Xiaomi Mi Mix 2 will also launch in September with no bezels at all.

However, sources claims that the standard Pixel 2 will have a 4.97-inch screen, while a larger model will land with a 5.99-inch one.
While Pixel 2 XL will have a 6-inch AMOLED screen, supplied by LG.

Google Pixel 2 XL Specs

Google Pixel 2 XL is being strongly linked with the new Snapdragon 836 chipset.(This is obviously an update over the 835 version that appeared in other flagship devices earlier this year, such as the aforementioned Galaxy S8)
Snapdragon 836 will be an octa-processor with the same 10nm FinFET design and clock speeds of up to 2.5 GHz. The Google Pixel 2 is codenamed ‘walleye’ while the Pixel XL 2 has the codename Taimen. The Pixel 2 was also spotted in a FCC (Federal Communications Commission) filing and the phone could also have ‘squeezable’ edge sensors like the HTC U11. Both the phones are expected to run Android Oreo when they launch.

Water resistance

It's also rumored that the Pixel 2 will come with a waterproof design. A Senior Editor at 9to5Google reported a source has said the phone will be dunkable when it's released.

May lack a 3.5mm headphone jack

We've seen newer renders that claim to show off the final design of the Pixel 2 family of phones. Much of it falls in line with what we've seen previously, but the most noteworthy change is the lack of 3.5mm headphone jack.
Further case renders from Olixar (which you can see below) add to the suspicion the Pixel 2 and Pixel 2 XL will drop the legacy tech, while separate sources for 9to5Google Managing Editor Stephen Hall add more fuel to the 'no headphone jack' fire.

The Google Pixel 2 is rumoured to run Android 8.0.4GB of RAM64GB or 128GB of storage12MP rear and 7MP front-facing camerasImprovements over the Pixel's cameraRear-facing fingerprint scanner

Price considerations

According to sources the Pixel 2 will apparently carry a loftier price tag than its predecessors - something we hope doesn't turn out to be true. The old one started at $649 (£599, AU$1,079), or $769 (£719, AU$1,269) for the XL version, so it was already expensive.

References:

https://www.valuewalk.com/2017/08/google-pixel-2-xl-specs/?all=1http://www.gadgetsnow.com/mobile-phones/Google-Pixel-2

Labels:

Comments

Post a Comment

Popular posts from this blog

Mastering Per-App Language Preferences: From Android 10 to Android 13+

  One of the most requested features by users is the ability to use an app in a language different from the system language. While Android 13 (API 33) introduced "Per-App Language" settings at the system level, implementing this backward-compatibly for older devices like Android 10 (API 29) used to be a challenge involving manual configuration wrapping. Today, thanks to AppCompat 1.6.0+ , we have a unified, standard way to handle this. Here is the modern guide to implementing seamless language switching. The Architecture: How it Works On Android 13 and above, the system handles the storage and application of your app's locale. On older versions, the AppCompat library manages this behavior by storing your preference in an internal XML file and injecting the resources during the activity lifecycle. Step 1: The Locale Helper Utility Instead of scattering logic across your app, use a clean LocaleHelper object. This handles the distinction between the system LocaleManager (...
Post a Comment
Read more

Beyond Scanning: Meet the All-in-One AI Document Assistant by Digitify Vision Technology

In an era where efficiency is the ultimate currency, information is scattered everywhere—on physical paper, within QR codes, and inside lengthy digital documents. The challenge isn't just capturing this data; it’s making it work for you. At Digitify Vision Technology , we believe your smartphone should be more than just a camera—it should be a high-performance engine for your daily workflow. Today, we are proud to unveil our most powerful update yet: a total evolution in AI-driven document management. 💡 Key Features of the New Update We’ve bridged the gap between physical information and digital action by integrating advanced vision and audio intelligence into a single, seamless experience. 🔍 Precision Scanning for Everything Our advanced vision engine is now more versatile than ever. Intelligent Document Scanning: Capture crisp, professional-grade scans of physical papers, contracts, or handwritten notes. QR Code Extraction: Instantly scan any QR code to extract text, read URL...
Post a Comment
Read more
  Optimising Android Launch: Mastering App Startup & The Modern Splash Screen The first few seconds of an app’s life determine a user's first impression. A slow start or a flickering white screen can lead to immediate uninstalls. In this guide, we’ll look at how to streamline your initialisation using the App Startup Library and ensure a seamless visual transition with the Android 12 Splash Screen API (with full backward compatibility for API 29). Part 1: The App Startup Library Traditionally, apps initialised multiple components using separate content providers. This adds overhead and slows down launch time. The Jetpack App Startup library allows all components to share a single content provider, significantly improving performance. Why use it? Performance: Shared content provider reduces overhead. Order: Explicitly set the initialisation sequence. Simplicity: Both library creators and app developers use a unified interface. Part 2: The Modern Splash Screen API Starting ...
Post a Comment
Read more