LightBlog

samedi 9 novembre 2019

How to Copy Data from iOS to Android with MobileTrans

Transferring data from one smartphone to another shouldn’t be a difficult task. However, when you’re moving your personal files from an iPhone to and Android, it can get a little tricky. Many transfer methods require you to connect both devices to a computer to properly transfer all of your important files. The most convenient way to go about this would be to have an app that can transfer everything wirelessly without any need for a PC. This is where MobileTrans comes in. MobileTrans is a powerful iOS to Android transfer app that makes the process effortless. Completing a transfer manually can be slow and sometimes very difficult for certain type of files. MobileTrans will help you grab all of your files and get you setup on a new device.

When you download the MobileTrans app, you can select your contacts, messages, videos, photos, music, apps, wallpapers and voice memos, and copy your data to Android. There are two ways for you to do this. The first way is by connecting the app to your iCloud account and pulling your backed up data from there. The second way is to use a USB cable for a direct tether from one phone to the other. Most file types are supported with up to 13 different types that are compatible with the iOS to Android transfer.

Using advanced data analysis technology, MobileTrans makes the file transfer process extremely fast. Compared to other data transfer apps, MobileTrans supports a much quicker process.

For MobileTrans to work with your phones, you must have compatible devices. MobileTrans is compatible with iCloud 8.0 and up , iOS 5.0 and up, and Android 4.1 and up. You can get the free version of MobileTrans which will allow you to transfer photos from iOS to Android. To transfer more file types, you can upgrade to the full version of the app.

MobileTrans – Copy Data to Android

MobileTrans - Copy Data to Android (Free+, Google Play) →

You can download the MobileTrans app for free from the Google Play Store, using the link above.

iCloud Transfer

Step 1: Download the app from the link above and install it on your Android phone and select import from iCloud.

Step 2: Log in to the iCloud account with your Apple ID and passcode. Enter the verification code if you have enabled the two-factor authentication.

Step 3: The app will scan your iCloud and detect all the different types of files. It will then list all the different types and allow you to choose which ones you’d like to transfer. Select your files and tap start importing.

Step 4: Now you just wait for the process to complete.

Direct Transfer

Step 1: Download the app from the link above and install it on your Android phone and select import from USB cable. You will need an iOS to Android adapter to connect the two phones. If you don’t have one, you can find them on Amazon.

Step 2: MobileTrans will begin scanning all of the data in your iPhone. The scan time will depend on the amount of data that you have stored on your phone.

Step 3. Once the software has scanned all of the data, a list of file types will be shown. You can select the types of file you want to transfer, then select start importing.

MobileTrans also has a detailed guide on how to sync everything between your two phones, just in case you get stuck somewhere.

About MobileTrans

MobileTrans in available for Windows, macOS, Android and iOS. The software supports just about any combination of operating systems. This includes Android, iOS, and even Windows Phone. MobileTrans also offers complete backup and restore solutions to help protect you from data loss. They even have a solution for transferring WhatsApp data from one device to another. While transferring photos is available in the free version of the app, you can check out their pricing to see what options they have for more features.

It is important to note that none of your data is stored on MobileTrans servers. Their methods use direct connections from transferring your personal files. Your data stays on your devices, which is important for those of you that care about your privacy.

Next time you are in need of a data transfer solution, check our MobileTrans and you’ll see for yourself how this software makes the entire process a whole lot easier.

We thank MobileTrans for sponsoring this post. Our sponsors help us pay for the many costs associated with running XDA, including server costs, full time developers, news writers, and much more. While you might see sponsored content (which will always be labeled as such) alongside Portal content, the Portal team is in no way responsible for these posts. Sponsored content, advertising and XDA Depot are managed by a separate team entirely. XDA will never compromise its journalistic integrity by accepting money to write favorably about a company, or alter our opinions or views in any way. Our opinion cannot be bought.

The post How to Copy Data from iOS to Android with MobileTrans appeared first on xda-developers.



from xda-developers https://ift.tt/32tw8As
via IFTTT

vendredi 8 novembre 2019

Samsung Camera app hints at a future Galaxy phone having a 108MP camera

Samsung is currently the only image sensor vendor that makes a 108MP image sensor for smartphones. Even though they’re the ones to have made it, their own smartphones aren’t the ones using it right now. So far, only Xiaomi uses it in the Mi Mix Alpha and Mi Note 10/CC9 Pro, and the early results seem to be pretty good. Samsung isn’t leaving all the fun to Xiaomi, though. According to code we found in the latest version of the Samsung Camera app, Samsung will very likely be including a 108MP camera on one of their future smartphones.

While delving into the Samsung Camera app from the third One UI 2.0 beta which was released yesterday for the Galaxy S10, I found code that adds 108MP output resolution support. We’ve heard rumors that Samsung is likely to put its 108MP image sensor in the Galaxy S11, but there’s nothing in the code confirming that this output resolution is specifically for the upcoming Galaxy S11. All we can say is that at least one of the upcoming Galaxy smartphones from Samsung will support it. We will likely know what phone will be using this sensor in early 2020 as more information leaks.

In the screenshots below, we can see that the Samsung Camera has added support for a resolution of 12,000 by 9,000 pixels. This is 108,000,000 total pixels, or 108MPs. Like the Mi Mix Alpha or Mi Note 10, Samsung will likely employ pixel binning to improve low-light shots. This means the Galaxy smartphone using this sensor likely won’t be outputting full 108MP resolution photos by default, but rather 27MP or 12MP photos by combining 4 or 9 pixels respectively and turning them into a single pixel, making each pixel effectively larger than any of the individual pixels.

108MP resolution support in Samsung Camera app 108MP resolution support in Samsung Camera app

In the past, Samsung hasn’t added support for a resolution or sensor unless they were actively working on shipping them in a future Samsung device. This is because the engineering and cost of development for software just aren’t worth it as a testbed for possible hardware. That means when we find support for a specific resolution or feature, it will very likely be making it into one of the future smartphones that Samsung is planning on launching.

We are very excited about these new 108MP smartphone cameras. Xiaomi is already doing wonders with it, and I think it’s really going to take Samsung’s cameras to the next level.


Thanks to PNF Software for providing us a license to use JEB Decompiler, a professional-grade reverse engineering tool for Android applications.

The post Samsung Camera app hints at a future Galaxy phone having a 108MP camera appeared first on xda-developers.



from xda-developers https://ift.tt/2NsJdWn
via IFTTT

I’ve used the Galaxy Fold for a month: Yeah, this is the future

There’s no getting around the fact that the Samsung Galaxy Fold is a hotly debated device. Since its inception, and throughout its fair share of turbulence, the phone has garnered a fair amount of critics. Given that this device presents such a radical departure from traditional form factors, such skepticism is not only expected but perhaps even healthy. Yet at the same time, many reviews have barely just arrived, and the verdict regarding its failures and triumphs is yet to be fully decided.

For a few years now, I’ve been really into phones. At first, I really only cared about the specifications. Truthfully, this got boring quickly. So for the past year or so, I’ve been more interested in unique and fun phones. The most fun, exciting, and just straight-up cool phone I’ve used is the Samsung Galaxy Fold.

Galaxy Fold XDA Forums

Before delving into the details, I want to just state off the bat that I think it’s worth the price. I am aware that many readers will disagree, but I hope to make my reasons clear by the end of this editorial. The fact is that using the Galaxy Fold is not like using any other phone. It’s thicker, heavier, more delicate, and weaker than most modern handsets. That doesn’t mean you need to baby it, but you can’t abuse it either, and we’ve subconsciously grown increasingly reliant on the respectable durability that modern flagships now offer. The Galaxy Fold is very special, and looking at videos and pictures, or even reading a review, can’t give you anything close to the idea of what using the phone is like.

Samsung Galaxy Fold
Display Type Main display: 7.3” QXGA+ Dynamic AMOLED Display (4.2:3) Infinity Flex Display, 2152×1536, 362ppi
Cover display: 4.6” HD+ Super AMOLED Display (21:9), 1680×720, 399ppi
Size Folded: 62.8 x 160.9 x 15.7mm ~ 17.1mm
Unfolded: 117.9 x 160.9 x 6.9mm ~ 7.6mm
Weight: 276g
Display Color Palette HDR10+ main display only
System-on-chip Snapdragon 855
RAM Capacity 12GB (LPDDR4X)
Storage Capacity 512GB UFS 3.0
Speaker System
  • Stereo speakers and earphones: Sound by AKG
  • Surround sound with Dolby Atmos technology
Headphone Jack
  • No
  • Samsung Galaxy Buds in the box
Front Camera Folded: 10MP 2PD AF F2.2 (80°)
Unfolded: 10MP 2PD AF F2.2 (80°) + 8MP depth camera
Rear Cameras Triple Camera
  • Ultra-Wide: 16MP F2.2 (123°)
  • Wide-angle: 12MP 2PD AF F1.5/F2.4 OIS (77°)
  • Telephoto: 12MP F2.4 OIS (45°)
Battery Capacity 4380mAh (typical) dual battery
Wireless Charging Yes, Fast Wireless Charging 2.0, Wireless Power Share 5W
Fast Charging
  • Yes, Samsung Adaptive Fast Charging, 15W PD
  • Adaptive fast charger in box
Biometrics Capacitive side fingerprint scanner
Water and Dust Resistance None
Software Android 9 Pie with One UI

About this article: Samsung did not provide this device for review. I purchased it myself for personal usage. 

In any other review or hands-on article, this section normally would be about the design of the phone, meaning color, aesthetics, and dimensions. Stuff like that isn’t really important when talking about a foldable, and the first real foldable in particular. I know people will want to know my take on it, though, so let me quickly just go through it.

It has glass on the front and back which is sloped down into the aluminum rails. The hinge is made out of stainless steel which feels very premium. It is visible on the side of the phone while folded, and completely flat on the side, sloping down into the front and back panels. I have the silver model, which has a mirror finish and very subtle color-shifting effects with direct and strong light.

 

Let’s get to the crucial distinguishing component that enables the Fold to be so interesting: the hinge. It’s made of stainless steel and is visible on the side of the phone while folded. It is completely flat on the side and slopes down into the front and back panels. There is a very slight gap in-between the hinge and the panels of the phone. This is to let the hinge open and close smoothly but does leave it open to getting water or dust into the body.

Note 10+ vs Galaxy Fold Thickness

What is most important is the design of the foldable display and, to put it simply, how it folds. The Galaxy Fold has what I consider the best foldable design, at least in terms of where we are in the age of plastic foldable displays.

The body of the phone is made of glass and aluminum while the main display is plastic. While the phone is folded, the display is protected. While it is unfolded, it is you who must protect the display. The panel is very safe while closed because the gap between the phone isn’t large enough for really anything to fit in, and the additional caps Samsung added address some of the early issues that were reported regarding particle ingress. Sand and small pebbles will, of course, be able to fit into the gap, but that’s the nature of having a gap.

On the other half of the phone, you’ve got the  headphone jack USB C port. On that same right/bottom half of the phone, you have the fingerprint scanner, power button/Bixby button, and volume rockers. Unlike the Galaxy S10e, the power button and fingerprint scanner are different. At first, I didn’t like this because it just felt weird. As I used the Fold more, I actually really started liking it because it’s very easy to accidentally hit the buttons while holding the phone because of its size. It’s nice to have the fingerprint scanner only on while the display is on. It also has an option to swipe to bring the notification shade down, but again, I kept it off because I kept accidentally hitting it.

With that said, we have to talk about the display durability. This is the main “drawback” of foldable displays. The display is made of plastic, which is not optimal, but currently, there is no consumer-ready foldable glass. The concern is that there will be deep scratches, dents, or you could just crush the display if you press too hard. You know what, it’s true. Both of those could totally happen. The thing is, they likely won’t.

Looking through the gap of the Galaxy Fold while folded

For a deep scratch to appear, you would need to run sand over the display. Will this ever happen intentionally? Probably not, but stray hard particles might find their way onto the display or inside your pocket when out and about. For a dent, you would need to press down pretty hard with your fingernail. This is what Zach from Jerry Rig Everything did in his infamous durability video. Will you ever drag your fingernail through the display so hard it permanently dents the display? No, probably not, at least not intentionally. I can’t say I’ve ever done this on any phone ever, and I certainly would not do it on the Fold. What about crushing the display? You can’t put excess pressure onto the display, so while closing it you can’t be pressing down on the middle of the screen. Doing this will likely break the display over time. Samsung warns you about it as well, so as long as you pay attention to the documents in the box with the Fold, you’ll be good. It is possible to exert pressure by, say, accidentally sitting or laying on the phone while it’s hiding under a cushion or sheets. With a Fold, you have to be slightly more careful and aware of such situations.

It’s also important to talk about ingress. The Galaxy Fold is not IP68 rated. The Galaxy Fold can be damaged by entering into contact with sand or water. Samsung can’t fully seal the hinge into the body of the phone because of the design limitations. If it’s raining, you can’t have your phone out. If it’s snowing, you gotta keep it sheathed. If you’re at the beach, you better keep it in your car, as you don’t want sand in the hinge. These situations are all based around sand and water because that’s the main thing you have to worry about, otherwise, it’ll last through most people’s 9 to 5 job.

Software: One UI but it folds

I don’t want to re-review One UI because it’s honestly not worth it. I have a full One UI review you can check out for a good look into the software. The Galaxy Fold has the same basic One UI software and experience. Instead of just going over One UI again, let’s talk about how the software on the Galaxy Fold works, because it’s obviously not going to be the same as a device like the Galaxy Note 10, right?

Well, it’s actually very similar and pretty intuitive. The base software is the same. You have access to all your apps on the front screen and main screen. While you are on the front screen, the phone thinks it’s a phone. When you unfold it, the Fold thinks it’s a tablet. This might be a little confusing so let me give you an example. While you have the Galaxy Fold closed and open Samsung Music, it says “Control your music without unlocking your phone.” Nothing to think twice about, right? Well, when you open the Galaxy Fold it says “Control your music without unlocking your tablet.” It’s a one-word difference but says a lot about the software experience.

The software on most Android tablets is absolutely horrible because most developers don’t design their apps for Android tablets, specifically, as these have awful sales. This is fair, we shouldn’t expect developers to make apps for devices that won’t be used as often. Most people would assume that foldables have the same general principle as tablets: if they won’t sell, why develop for them? Samsung knows this is going to be an issue so they made it easy for developers to develop for the Galaxy Fold. They also worked with hundreds of app developers to add Galaxy Fold support for app continuity out of the box. Samsung says hundreds of apps of the Google Play Store and Galaxy Store already support App Continuity. I can totally see this. Out of 131 apps installed on my Galaxy Fold, only 8 don’t support continuity. For those 8 apps, you just click the re-size button in the navbar and it will reload the app to the larger screen. Even some apps that haven’t been updated in a long time support it. I’m not sure what type of black magic Samsung is doing, but it is so good and so fast. It feels like complete and finished software.

Adobe Photoshop Mix doesn’t have continuity

App continuity is one of the really great features Samsung is really pushing. Saying “oh yeah the Fold has app continuity and it’s good” doesn’t really tell you anything about it. Let me give you an actually practical example I legitimately use every day. I get a lot of emails, as you would expect, and to quickly check one out, it’s not worth opening the main display. So I can read through them on the front and select the email I want to read and respond to. I open the email on the front display and realize, “man this is really small.” All I have to do is open the larger display, and I’m at the same place with the same info ready to work. It’s seamless as well, with no loading or awkward transitions in-between.

Besides App Continuity, there really are no Fold specific features. There is nothing new in the camera or in the UI. It’s got One UI 1.5 which means Your Phone from Microsoft is preinstalled and it has those fancy Live Focus Camera and AR Doodle modes. That’s seriously about it. That’s not a bad thing though. It has every setting you could ever need and more. One UI as an Android skin is extremely well done and it really didn’t need anything more for the Fold. Samsung did a very good job on the software.

Camera: bigger display is better

The camera on this phone is essentially the same as the Galaxy Note 10+. I highly recommend just going and reading the camera section on that review. In case you don’t want to go over to that review and read that entire section, here’s a small blurb that describes the camera very well.

Previous Samsung phones have had issues with their cameras. It wasn’t about quality or actual hardware issues, rather it was all about the color science. Samsung’s colors are usually cooler and the saturation is turned up to 11. This made the pictures straight out of the shutter in auto mode great for something like Instagram. If you wanted more true to life photos, though, this wasn’t really great. With the Galaxy Note 10+, Samsung changed things a bit. The photos are not as saturated as before. Don’t get me wrong, they’re still not perfectly true to life, but it’s much better than earlier devices.

You’ll likely want to see a few pics for yourself, so here are some shots I took with my Fold’s rear cameras. You can check out the full Google Photos album in the link right below.

Galaxy Fold Album Google Photos

Something photo samples won’t show is how good the Fold is for taking pictures. Unlike the monsters that take pictures with iPads, the Galaxy Fold doesn’t feel obnoxious. The big display is actually pretty great for photos. Every picture looks good on the viewfinder and it makes taking pictures fun. Using the smaller display, pictures are just alright. Photos are truly the main display task.

Experience: You can not imagine it until you use it

This “experience” section of the review is something I wouldn’t normally do. Most people know what using a phone is like. It’s a metal and glass slab with bright lights moving quickly. You’re probably reading this on one and you probably know what it’s like to use a normal old phone. I could give you a Pixel 4 XL or Redmi Go and they are basically the same experience. Sure, differences in cameras, software, speed, whatever. They are basically the same. The Galaxy Fold is something brand new.

When closed, it feels good. It’s heavy, but a good heavy. My Galaxy Fold has a little creaking to the hinge. According to Samsung, this is normal, because the hinge will loosen with time. If it gets too annoying, you can easily bring the Fold to a service center where they can tighten the hinge for you. The reason for the loosening in the first place is to keep it from snapping. The wiggle apparently keeps it loose and lets it fold for those 200,000 folds.

While unfolded, it feels very thin and even thinner than most flagship phones. It actually feels great to use unfolded, as it should. The weight distribution is insanely balanced and well-distributed, so it doesn’t feel very heavy. The thing is, it isn’t totally flat but features a 2 degree offset between screens. It’s almost flat and almost impossible to tell it isn’t under most conditions, but if you look closely you can see it. My Fold folded flat for the first 2 or 3 weeks of owning it. After close to a month, it’s less flat than when I unboxed it.

Even then, the user experience is absolutely amazing. It is not like using any other phone or tablet: the tablet size is actually very nice with a fine aspect ratio. It makes looking at Reddit, Twitter, Gmail, or just any other app more interesting. Everything is bigger, and as they say, bigger is better.

Something else Samsung didn’t tell you is that you can use the device while it’s not totally folded or unfolded. You can use the fold at a 90-degree angle, which might seem uncomfortable, and it is. Using the phone at around 135 degrees is actually pretty great. It makes it feel like you are reading a book. It’s not going to look the best, as there are some differences in the look of the display with colors and brightness, but it still works.

Folding the phone shut is also just amazing. Feeling the phone snap flat to a tablet is just something you can not describe in words. It’s such a satisfying feeling. Opening and closing it piques the interest of everyone, no matter what phone they use. Again, it’s hard to describe in words. It’s the type of device where you need to try it yourself to really understand how amazing the experience is.

Conclusion: The Future comes at a premium

When considering the Galaxy Fold, the first thing you’re likely going to think about is the price. It’s expensive, retailing at $1,980 — but in reality, you’ll end up spending a bit more. This is because of two reasons. First, because sales tax exists. I ended up paying $2,150.76 for mine from Best Buy. The second reason is actually due to availability. If you really want to get this phone, you’ll have to buy one from sites like eBay or Swappa. They are currently sold out around the world with stock being resupplied very slowly. As the basics of economics state, low inventory with high demand means higher prices.

The price isn’t a huge deal, even if it is a huge price. While the phone is too expensive compared to modern flagships, it is not meant to compete for the same customers, given it is in a category of its own: a paradigm-shifting luxury product. It’s a product targeted at a very particular segment that’s willing to pay a premium to be first. It’s not that it is not meant to be owned by everyone because it is luxurious or something, but rather because it is a first-generation foray into a new product category, and it is currently sought after by first-adopters.

To me, the Galaxy Fold is well worth the price. Yes, $2,000 is a large amount of money. It is a lot more than any person should spend on a regular phone. Luckily, the Galaxy Fold is more than that. It’s a luxury product, with both style and function. When you walk into a room, everyone wants to know what device you have. When you are walking around, it just looks stylish to hold. It’s also functional in a way no other phone on the market is, because it is an actual tablet that fits in your pocket. There is nothing more stylish and functional I can think of in the Android space, especially this well-engineered. Something like this isn’t going to be inexpensive, at least not yet, so for a starting price of a luxury item in a new product category, the price is right.

Galaxy Fold XDA Forums

At the end of the day, with something like the Galaxy Fold, it’s going to be hard to change anyone’s mind about it. Trust me, I’m not trying to. I’m just trying to say that after using it for about 5 weeks, it is my favorite phone I’ve ever used. There is no phone or experience like the Galaxy Fold. The Fold makes me excited for future foldables because after using it, I firmly believe foldables are going to be the future of mobile computing.

In the unlikely situation you would be interested in picking up the Galaxy Fold, it isn’t easy. It is only available in-store at specific carriers and Samsung stores around the world. In the US, you can only pick up the Galaxy Fold at specific AT&T and Best Buy stores along with the three Samsung Experience Stores. If you are interested, I recommend checking out your regional Samsung website. It really does vary by region.

The post I’ve used the Galaxy Fold for a month: Yeah, this is the future appeared first on xda-developers.



from xda-developers https://ift.tt/2p0POxT
via IFTTT

The evolution of Google Pixel series: from Google Pixel to Google Pixel 4 & Google Pixel 4 XL

It’s not often that we think about the evolution of a brand. Sure, we compare the phones year after year, but we rarely take a step back and examine the long-term growth. Google has been taking a bare minimum approach to upgrading their phones annually, especially with the most recent launch. But how much has the Google Pixel series evolved since the beginning?

Before I get into the evolution of the Pixel series, I want to talk about Google’s philosophy. The Pixel series was never meant to compete on maxed-out specs; it was supposed to be a phone made “The Google Way.” The Pixel phones integrate very closely with Google services and provide easy and fast access to Google’s best software. The Pixel phones are meant to make your life easier by making you interact with your phone less and still get a lot done.

Part of the Pixel philosophy was about doing the most with the least. This is why Pixel phones traditionally don’t have tons of RAM or a handful of cameras. They didn’t get dual cameras until 4 years in. Google was capable of doing a lot without going all out, so they didn’t. This is obvious when you look in-depth at all the changes Google made throughout the Pixel series over the past four years. So let’s do just that.

Pixel and Pixel XL

The original Google Pixel, also known as the OG Pixel, was Google’s first flagship smartphone. This phone had Google’s new Google Assistant. It also had Google’s first real attempt to get into the camera game. At the time, it had the best camera. It also had pretty basic specs for late 2016. The Snapdragon 821, 4GBs of RAM, 32GB or 128GBs of storage, a 3450 mAh battery, a single 12.3 MP rear camera, and a 5.5-inch QHD display. This is, by all means, a very basic 2016 phone.

The average hardware of the Google Pixel was easily forgotten because of Google’s absolutely fantastic software. The phone felt fast and clean. There was no excess bloatware or meaningless changes to the software. Google made changes where needed and did not make excessive changes. The lack of changes along with the new Google Assistant made the Pixel the best phone at the time.

Image from TechSpot

The OG Google Pixel also looked fantastic. It came in three colors, Quite Black, Very Silver, and Really Blue. These three colors were absolutely fantastic and had very accurate names to the colors of the phone. It was the start of Google’s infamous dual-tone design with a glass and aluminum combo on the back. The OG Pixel was one of the best Pixel phones in the series because of how Google essentially came out of nowhere with game-changing camera software.

google pixel

Pixel XDA Forums / Pixel XL XDA Forums

Pixel 2 and Pixel 2 XL

The Pixel 2 and Pixel 2 XL were a pretty big step up. Unlike the OG Pixel, the Pixel 2 and Pixel 2 XL did look pretty different. The Pixel 2 kept some chunky bezels at the top and bottom of the phone while the Pixel 2 XL had slimmer bezels. Both phones had stereo front-facing speakers, the Snapdragon 835, 4GBs of RAM, 64GB or 128GB storage options, a single 12.2MP rear camera, and OLED displays. The smaller Pixel 2 had a 1080p display while the larger Pixel 2 XL got a 1440p display. These specs were, again, nothing crazy, but they were the minimum Google needed to get a great and simple device onto the market.

They kept Google’s approach of making interacting with the phone easier while the phone improves your life without needing to do anything. This came through Google’s new features, Now Playing and Active Edge. Now Playing recognizes music playing around you without using much battery and keeping all the processing on the device. Active Edge made Google Assistant easier to use by just needing a simple squeeze on the sides to activate it.

The design of the Pixel 2 and Pixel 2 XL were also very practical. Google didn’t really go all out on design or features. They kept only a single rear camera in a time where dual cameras were becoming popular. Google also kept their dual tone aluminum and glass back. It came in a total of four different colors between the Pixel 2 and Pixel 2 XL. The Pixel 2 XL came in Black & White, also known as Panda, and Just Black. The Pixel 2 came in Kinda Blue, Just Black, and Clearly White. The Pixel 2 XL was one of my favorite phones of all time.

google pixel 2 xl

The Pixel 2 wasn’t perfect, though. There were lots of issues with performance and RAM management a few months after the phone had launched. Google tried to figure some of these out with software updates, and it did help for some. There was also the issue with the Pixel 2 XL display. There was insane blue shift in some units. It was a lottery if you were to get a good or bad display. This was also the first Pixel to drop the headphone jack, which was controversial at the time.

Pixel 2 XDA Forums / Pixel 2 XL XDA Forums

Pixel 3 and Pixel 3 XL

The Pixel 3 and Pixel 3 XL was not the huge upgrade many believe the Pixel line needed. Google kept with their classic approach of bare minimum specs and life-improving software. The Pixel 3 and Pixel 3 XL had very minimal specs for a 2018 flagship. It came with the Snapdragon 845, 4GBs of RAM, 64GB or 128GB storage options, dual front-facing cameras, a single 12.2MP rear camera, and a fully glass back. This was, once again, nothing extreme, but it got the job done.

Besides design, which I will get into later, most of the new features from the Pixel 2 to the Pixel 3 came in the camera. Google added a bunch of new features including Top Shot, Motion Auto Focus, Night Sight, and Super Res Zoom. While it didn’t reinvent the whole camera experience on the Pixel, it made it much better. Night Sight, in particular, was another game-changing camera feature. It drastically improved what you could get out of a smartphone camera in bad lighting conditions. Now, similar modes are present on nearly every flagship phone on the market.

One of the bigger hardware changes and upgrades in the Pixel 3 was the all glass back and wireless charging. This all glass back was, of course, for wireless charging and Google’s own Pixel Stand. This glass back was one of the first glass phones with a frosted glass finish. It was easy to scratch but felt absolutely amazing to hold. The Pixel Stand also helped make wireless charging more useful in your life by essentially turning a Pixel on a Pixel Stand into a Google Home. This, once again, makes the Pixel phone more useful for you and helps bring Google’s services into your life.

google pixel 3 xl

It might sound great, but there were some issues with the Pixel 3 and Pixel 3 XL. The notch on the Pixel 3 XL was ginormous, which was more of a design flaw than an issue. The actual issues come with the performance and black frosted glass back. The black Pixels would get permanently scratched. The pink and white Pixels would as well, but you couldn’t see it because of the color. The performance issues came from the lack of RAM in the Pixel. My Pixel 3 XL would force stop playing music if I were to take a picture or even simply send a picture through a chat app. Sometimes switching between two apps would even force all background apps to close. It was a real issue with the Pixel 3, but Google did its best at fixing it. Over time Google was able to help the RAM management, but it still isn’t as good as a phone with more RAM.

Pixel 3 XDA Forums / Pixel 3 XL XDA Forums

Pixel 3a and Pixel 3a XL

The Pixel 3a and 3a XL are the first of their kind in the Pixel series. They were meant to be cheap and very good phones for the masses. They launched at $400 and $480 respectably. The interesting part about these devices wasn’t the price or the features you got on the phone, but what you got in comparison to the Pixel 3.

The Pixel 3a came with a Snapdragon 670, 4GBs of RAM, 64GBs of storage, a single front ultra-wide camera, a single rear 12.2MP camera, and 5.6-inch and 6.0-inch FHD+ OLED displays. This is pretty similar to the Pixel 3. In actual usage, it ended up being about the same speed as the Pixel 3 even though the processor wasn’t as good.

The combination of price and features is what made the Pixel 3a so interesting. For half the price, the Pixel 3a had the same features as the Pixel 3. The hardware wasn’t as good as the Pixel 3, sure, but it was also half the price. This was a huge deal and actually became the best selling unlocked phone on Amazon for a while. A lot of reviewers actually considered the Pixel 3a better than the Pixel 3 simply due to value. The Pixel 3a will likely be known as the most successful Pixel.

Pixel 3a XDA Forums / Pixel 3a XL XDA Forums

Pixel 4 and Pixel 4 XL

These past generations have all lead to the newest, latest, and greatest: the Pixel 4. Just a few weeks ago, Google launched the Pixel 4 and Pixel 4 XL. These Pixels are known in the tech community to be a bit of a flop. The reason is, once again, they don’t have insanely large batteries or crazy specs. They are the bare minimum Google thinks it needs to provide you with the features you’ll need to simplify your life.

The Pixel 4 and Pixel 4 XL come with the Snapdragon 855, 6GBs of RAM, 64GB or 128GB storage options, a single wide front camera, two rear cameras, and a 90hz display. The Pixel 4 comes with a 5.8-inch FHD+ display from LG while the Pixel 4 XL comes with a 6.3-inch QHD+ display from Samsung. The Pixel 4 has a 2800 mAh battery while the Pixel 4 XL has a 3700 mAh battery. These battery sizes are actually one of the main reasons not to get the Pixel 4 or Pixel 4 XL. The battery life isn’t really that great. The rest of the specs are not even close to what we are seeing in 2019. This was the first Google phone without a fingerprint scanner and the first Pixel phone with a dual camera. Neither of these are necessarily impressive hardware-wise, but make the Pixel experience better.

google pixel 4

There are really only two features Google has added that anyone will actually notice. Those are Project Soli a.k.a. Motion Sense, the second rear camera, lack of a fingerprint scanner, and the 90hz display. Project Soli is a small radar chip Google uses to make changing songs or unlocking your phone faster. It will recognize when you are about to pick up the phone and start scanning your face for the new Face Unlock feature, making it much faster than competing phones with 3D facial recognition. The 90hz display just makes things extra smooth.

Pixel 4 XDA Forums / Pixel 4 XL XDA Forums

Powerful Software NOT Powerful Hardware

Throughout the development of the Pixels, Google has been focusing on software over hardware. The idea of the Pixel is to get Google’s software into your pocket and make it work for you. The Pixel phones really do that. They have always had the newest and best Google Assistant features first, like Google Duplex or Google Lens. They have the smartest and best cameras while using the same camera sensors as $300 budget phones.

Google has always been able to do more with less, and that is what the Google Pixel is all about. On a spec sheet, you can look through the evolution of the Pixel design or specs or even features, and what you’ll notice is Google has been working on bringing useful software features over hardware. That’s why Google put a thick top bezel in the Pixel 4, they know the trade-off in design is worth it in functionality. Project Soli in the Pixel 4 is working to make your experience better, faster, and more natural without you even knowing it’s there.

The original Pixel came out with average hardware but exceptional software in Google Assistant. The Pixel 2 came out with, once again, average hardware, but the cameras and ease of access to Google Assistant with Active Edge and ambient music recognition with Now Playing made the Pixel 2 one of the smartest phones without you knowing it. With the Pixel 3 Google kept up the trend with average hardware, but outstanding cameras and the ability to turn your phone to a home speaker with the Pixel Stand. With the Pixel 4, Google has gone even further than before. The Pixel 4 will work to help you without you even knowing it’s working.

The evolution of the Google Pixel phones shows the evolution of ambient computing. Google is on the leading edge of software and they don’t need that extreme hardware every other OEM is using. The Pixel series has always been about making your life better and easier without you knowing it.

The evolution of the Pixel isn’t hardware or software, it’s that the phone is working in ways you don’t even recognize to help you. At the first Made by Google event on October 4th, 2016 Google said that we would remember that day as an important day in history because of the products they were launching. Almost four years later, I agree.

The post The evolution of Google Pixel series: from Google Pixel to Google Pixel 4 & Google Pixel 4 XL appeared first on xda-developers.



from xda-developers https://ift.tt/32t0DGK
via IFTTT

Developers: It’s super easy to bypass Android’s hidden API restrictions

Flashback to over a year ago, and we’re all excited about seeing what’s to come in the Android P betas. Users are looking forward to new features, and developers are looking forward to some new tools to make their apps better. Unfortunately for some of those developers, the first Android P beta came with a bit of a Nasty Surprise: hidden API restrictions. Before I dive into what exactly that means, let me explain a bit about its context.

What’s This All About?

Android app developers don’t have to start from scratch when they make an app. Google provides tools to make app development easier and less repetitive. One of these tools is the Android SDK. The SDK is essentially a reference to all the functions developers can safely use in their apps. These functions come standard on all variants of Android that Google approves. The SDK isn’t exhaustive, though. There are quite a few “hidden” parts of Android’s framework that aren’t part of the SDK.

These “hidden” parts can be incredibly useful for more hacky or low-level stuff. For instance, my Widget Drawer app makes use of a non-SDK function to detect when a user launches an app from a widget so the drawer can automatically close. You might be thinking: “Why not just make these non-SDK functions part of the SDK?” Well, the problem is that their operation isn’t fully predictable. Google can’t make sure every single part of the framework works on every single device it approves, so more important methods are selected to be verified. Google doesn’t guarantee that the rest of the framework will stay consistent. Manufacturers can change or completely remove these hidden functions. Even in different versions of AOSP, you never know if a hidden function will still exist or work how it used to.

If you’re wondering why I’ve been using the word “hidden,” it’s because these functions aren’t even part of the SDK. Normally, if you try to use a hidden method or class in an app, it’ll fail to compile. Using them requires reflection or a modified SDK.

With Android P, Google decided that just hiding them wasn’t enough. When the first beta was released, it was announced that most (not all) hidden functions were no longer available for use to app developers. The first beta would warn you when your app used a blacklisted function. The next betas simply crashed your app. At least for me, this blacklist was pretty annoying. Not only did it break quite a bit of Navigation Gestures, but since hidden functions are blacklisted by default (Google has to manually whitelist some per-release), I had a lot of trouble getting Widget Drawer to work.

Now, there were a few ways to work around the blacklist. The first was to simply keep your app targeting API 27 (Android 8.1), since the blacklist only applied to apps targeting the latest API. Unfortunately, with Google’s minimum API requirements for publishing on the Play Store, it would only be possible to target API 27 for so long. As of November 1, 2019, all app updates to the Play Store must target API 28 or later.

The second workaround is actually something Google built into Android. It’s possible to run an ADB command to disable the blacklist entirely. That’s great for personal use and testing, but I can tell you firsthand that trying to get end-users to set up and run ADB is a nightmare.

So where does that leave us? We can’t target API 27 anymore if we want to upload to the Play Store, and the ADB method just isn’t viable. That doesn’t mean we’re out of options, though.

The Hidden API “Fix”

The hidden API blacklist only applies to non-whitelisted user applications. System applications, applications signed with the platform signature, and applications specified in a configuration file are all exempt from the blacklist. Funnily enough, the Google Play Services suite are all specified in that configuration file. I guess Google is better than the rest of us.

Anyway, let’s keep talking about the blacklist. The part we’re interested in today is that system applications are exempt. That means, for instance, that the System UI app can use all the hidden functions it wants since it’s on the system partition. Obviously, we can’t just push an app to the system partition. That needs root, a good file manager, knowledge of permissions…. It would be easier to use ADB. That’s not the only way we can be a system app, though, at least as far as the hidden API blacklist is concerned.

Cast your mind back to seven paragraphs ago when I mentioned reflection. If you don’t know what reflection is, I recommend reading this page, but here’s a quick summary. In Java, reflection is a way to access normally inaccessible classes, methods, and fields. It’s an incredibly powerful tool. Like I said in that paragraph, reflection used to be a way to access non-SDK functions. The API blacklist blocks the use of reflection, but it doesn’t block the use of double-reflection.

Now, here’s where it gets a little weird. Normally, if you wanted to call a hidden method, you’d do something like this (this is in Kotlin, but Java is similar):

val someHiddenClass = Class.forName("android.some.hidden.Class")
val someHiddenMethod = someHiddenClass.getMethod("someHiddenMethod", String::class.java)

someHiddenMethod.invoke(null, "some important string")

Thanks to the API blacklist, though, you’d just get a ClassNotFoundException. However, if you reflect twice, it works fine:

val forName = Class::class.java.getMethod("forName", String::class.java)
val getMethod = Class::class.java.getMethod("getMethod", String::class.java, arrayOf<Class<*>>()::class.java)
val someHiddenClass = forName.invoke(null, "android.some.hidden.Class") as Class<*>
val someHiddenMethod = getMethod.invoke(someHiddenClass, "someHiddenMethod", String::class.java)

someHiddenMethod.invoke(null, "some important string")

Weird right? Well, yes, but also no. The API blacklist tracks who’s calling a function. If the source isn’t exempt, it crashes. In the first example, the source is the app. However, in the second example, the source is the system itself. Instead of using reflection to get what we want directly, we’re using it to tell the system to get what we want. Since the source of the call to the hidden function is the system, the blacklist doesn’t affect us anymore.

So we’re done. We’ve got a way to bypass the API blacklist now. It’s a little clunky, but we could write a wrapper function so we don’t have to double-reflect every time. It’s not great, but it’s better than nothing. But actually, we’re not done. There’s a better way to do this that’ll let us use normal reflection or a modified SDK, like in the good old days.

Since the blacklist’s enforcement is evaluated per-process (which is the same as per-app in most cases), there might be some way for the system to record if the app in question is exempt or not. Luckily, there is, and it’s accessible to us. Using that newfound double-reflection hack, we’ve got a one-time-use code block:

val forName = Class::class.java.getDeclaredMethod("forName", String::class.java)
val getDeclaredMethod = Class::class.java.getDeclaredMethod("getDeclaredMethod", String::class.java, arrayOf<Class<*>>()::class.java)

val vmRuntimeClass = forName.invoke(null, "dalvik.system.VMRuntime") as Class<*>
val getRuntime = getDeclaredMethod.invoke(vmRuntimeClass, "getRuntime", null) as Method
val setHiddenApiExemptions = getDeclaredMethod.invoke(vmRuntimeClass, "setHiddenApiExemptions", arrayOf(arrayOf()::class.java)) as Method

val vmRuntime = getRuntime.invoke(null)

setHiddenApiExemptions.invoke(vmRuntime, arrayOf("L"))

Okay, so technically, this isn’t telling the system that our app is exempt from the API blacklist. There’s actually another ADB command you can run to specify functions that shouldn’t be blacklisted. That’s what we’re taking advantage of above. The code basically overrides whatever the system thinks is exempt for our app. Passing “L” at the end means all methods are exempt. If you want to exempt specific methods, use the Smali syntax: Landroid/some/hidden/Class;Landroid/some/other/hidden/Class;.

Now we’re actually done. Make a custom Application class, put that code in the onCreate() method, and bam, no more restrictions.


Thanks to XDA Recognized Developer TopJohnWu, who originally pointed this workaround out to me. Here’s a bit more about how it works, although it’s in Chinese. I also wrote about this on Stack Overflow, with an example in JNI as well.

The post Developers: It’s super easy to bypass Android’s hidden API restrictions appeared first on xda-developers.



from xda-developers https://ift.tt/32qai0J
via IFTTT

Honor 9X Full Day Battery Test

The Honor 9X packs a seriously large battery considering the low budget price of the phone. The 4000mAh battery keeps the phone running effortlessly throughout a day’s worth of usage. The ultra efficient Kirin 9X chipset keeps the phone running fast with minimum battery drain. In this article, we are going to look at the usage of the phone over the course of a day and see how it does.

Honor 9X Specs
Display 6,59″ 1080 x 2340p (391 ppi)
Chipset HiSilicon Kirin 710F
RAM 6GB
Storage 128GB
Main Camera 48MP/8MP (Ultrawide)/2MP (Depth Sensor)
Selfie Camera 16MP Motorized Pop-up
Battery 4,000mAh
Operating System Android 9.1.0 EMUI 9.1.0

An Hour of Minecraft 9%

The first hour of use on my Honor 9X was spent playing some Minecraft. When gaming, I like to use the max settings on whatever game I’m playing, to get the best visual experience. In Minecraft, I set the render distance up to 11 chunks and all the other graphics settings on high. With most budget phones, Minecraft can seriously stress their hardware to it’s limits. With the Honor 9X I played a solid hour of Minecraft with no heat issues, and no performance dips. The game was as smooth of a gaming experience as you can have on Android.

Minecraft of the Honor9X

To help the phone in its gaming performance, I like to set the phone to Performance Mode in the battery menu. This mode prioritizes performance over battery conservation. With performance mode enabled, and the screen brightness set to 50%, I ended up using 9% in an hour of gameplay.

Battery Usage Data After One Hour of Minecraft


An Hour of Music 3%

For me, an hour of music a day is really overkill. In reality I’ll probably listen to a few tracks while I’m headed out for lunch, just to find out that Popeye’s is once again sold out of their chicken sandwich. But just to be thorough in my testing, I’ll assume an average user will stream one hour of music on their Honor 9X. For this test, we will use Google Play Music to stream, and have the screen off. Streaming music is the best time to enable the Power Saver Option, since this isn’t a graphics intensive task and wont affect the music playback in any way.

Battery Usage Data After One Hour of Music

After an hour of streaming songs on Google Play Music, the Honor 9X only used 3% of its battery. This means that even if you’re low on battery, you can still get hours of music time out of your Honor 9X. Long car rides is the most logical time to toggle on Power Save Option and just let your music play. This battery saving feature from EMUI is very effective.


An Hour of YouTube 11%

YouTube on the Honor 9X

Aside from some intensive 3D gaming, streaming video is usually most stress you’ll put on your smartphone battery. For the video streaming test, I’ll play a one hour long YouTube video with the screen at 70% brightness. I will not have Power Save Option or Performance Mode on.

Battery Usage Data After One Hour of YouTube

After an hour of streaming a YouTube video, I was able to get the battery down to 78% capacity. The video played in full-screen, only being interrupted by a few advertisements. In the hour of YouTube I only lost 11% battery in total. You should be able to comfortably watch several movies throughout your day, or binge a handful of episode of a show before needing to recharge.


Ten Minutes of Filming and 100 48MP Photos 7%

For this next test I’ll take a look at camera usage. I filmed 10 minutes of footage at 1080p resolution and 60FPS. These are the max video settings supported by the Honor 9X. Next, I took 100 photos with the 48MP sensor.

Fun Fact: 100 photos at 48MP takes up 674MB

Filming on the Honor 9X

Ten minutes of filming is probably way more than you’d use on an average day, but it’s important to know how much battery this will use if you’re going to be using your Honor 9X to document a vacation, or shoot some videos for the internet. After filming for 10 minutes and shooting 100 photos at 48MP, I managed to kill about 7% of the battery over the course of 14 minutes.

Battery Usage Data After 10 Minutes of Filming and 100 Photos


An Hour of GPS 6%

GPS on Android phones is probably way more efficient than most people think. If you’ve got GPS running and have your screen off when you’re not looking at it, GPS will barely touch your battery over the course of an hour. For this test, I left my screen on at 25% brightness and no battery save features were used. I took my phone out for a one hour ride on my electric scooter (which makes me look very cool btw) in the freezing cold temperatures. The app I used for GPS navigation was Google Maps.

Battery Usage Data After 1 Hour of GPS

After a full hour of usage, I drained another 6% from the battery on the Honor 9X.

Eight Hours of Sleep 6%

Alright it’s bedtime. Nothing too significant will be done to prepare the Honor 9X for the night. The display will be off and the phone will be set to silent to test the standby drain.

Battery Usage Data After 8 Hours of Standby Time

In the morning, the battery had dropped to 59% while losing 6% overall during the night. With 59% we have a whole second day of use ahead of us before needing to recharge.

The Honor 9X has a very impressive battery life. You’ll easily be able to get through an entire day on one charge, and most people will be able to go through two. See what others are saying about the Honor 9X in the community forums.

Honor 9X forums
We thank Honor for sponsoring this post. Our sponsors help us pay for the many costs associated with running XDA, including server costs, full time developers, news writers, and much more. While you might see sponsored content (which will always be labeled as such) alongside Portal content, the Portal team is in no way responsible for these posts. Sponsored content, advertising and XDA Depot are managed by a separate team entirely. XDA will never compromise its journalistic integrity by accepting money to write favorably about a company, or alter our opinions or views in any way. Our opinion cannot be bought.

The post Honor 9X Full Day Battery Test appeared first on xda-developers.



from xda-developers https://ift.tt/2K29vfY
via IFTTT

Samsung adds 3D face unlock on the Galaxy S10 5G with One UI 2.0

When Samsung announced the Samsung Galaxy S10 5G, they didn’t make a big deal out of the TOF (Time-of-Flight) cameras included in the phone. This was because even though they could be used for a lot of cool features, Samsung didn’t really invest in it on the software side. With One UI 2.0, Samsung is finally getting around to it by adding 3D facial recognition. They had the hardware, now they have the software.

This comes from Twitter user @TEQHNIKACROSS  who realized that Samsung had enabled the TOF camera for face unlock after installing the latest One UI beta on his Korean Galaxy S10 5G. While this won’t change the face unlock experience a lot, it does make it more secure. Before this update, the phone would use the front-facing camera only for face unlock. This is by no means secure. While it was fast and accurate, it still left the phone open to unlocking by using a photo of the owner. The Galaxy S10 5G should no longer have this issue.

While the software doesn’t say it specifically has it, TEQHNIKACROSS actually posted a picture of the 3D scanner working. While a normal camera uses light-sensitive diodes on the sensor to absorb light, a TOF sensor both sends out an IR blast and collects the light and depth data based on that blast. The red beam you see below is that IR blast being sent out of the Galaxy S10 5G by the TOF camera.

3D facial recognition is by no means new. Apple has long had it on the iPhone, for example. There have even been a few Android phones with 3D facial recognition before Samsung enabled it on the Galaxy S10 5G. The Huawei Mate 30 Pro and LG G8 ThinQ both use TOF sensors on the front for secure facial recognition, while the Huawei Mate 20 Pro and Pixel 4 use a more Apple-like approach with their sensors.

Samsung Galaxy S10 5G XDA Forums

If you have a Galaxy S10 5G and want this update, you’ll need to wait for One UI 2.0. The S10 5G is currently available in Korea for the One UI beta and could expand to other regions soon. If you have an S10 series phone running the One UI 2.0 beta, One UI 2.0 beta 3 is rolling out to devices right now.

The post Samsung adds 3D face unlock on the Galaxy S10 5G with One UI 2.0 appeared first on xda-developers.



from xda-developers https://ift.tt/2rsojOJ
via IFTTT