Monday, September 4, 2017

Registration for Chrome Dev Summit 2017 is Open, Oct 23-24 in San Francisco

When you ask someone about developer conferences from Google that impacts Android, the immediate answer is almost always Google I/O. This is a very important event for native Android application and games developers, but there are other events that also benefit the Android ecosystem. One such event is one held by Google called the Chrome Dev Summit and while they don't always specifically target the Android platform, they do focus on new features for it.

Earlier this year we reported on the deep integration of Progressive Web Apps (WebAPKs) for Chrome on Android. They went live back in January of this year, but we were actually able to get a demonstration of how they work at the 2016 Chome Dev Summit. Much like Google I/O, this conference is targeted at developers but only those who are actively building on the Chrome platform. Chrome has been getting more and more popular over the years so it makes sense for Google to offer these for developers.

So the 2017 Chrome Dev Summit is coming up on the 23rd and the 24th of October with the registration page being live right now. It will be taking place in San Francisco this year and it will be held at the Yerba Buena Center for the Arts. The doors open at 8AM on the 23rd and will then be closed at 6PM on the 24th. Pricing has yet to be revealed to the public, but you can register for your spot right now through the event's landing page (linked below).

During the two-day event, developers will be able to speak directly with Chrome engineers just like Android developers get to interact with Android engineers at Google I/O. There will be codelabs available just like they had them setup last year, and attendees will get to learn more about Progressive Web Apps, as well as looking at the new features that are coming to the web platform.


Source: Google



from xda-developers http://ift.tt/2eDkPCG
via IFTTT

All Nokia Android Smartphones to Receive Update to Android Oreo

Nokia, in combination with HMD Global, is looking to make their presence known to the Android consumer base. The Nokia 8 is shaping up to be a stellar phone, with some good specs for a decent price and, even better, all running stock Android. The company's phones have been receiving a security patch update monthly, and now things are looking even better for Nokia's smartphones.

The Chief Product Officer of HMD Global, Juho Sarvikas, tweeted that all of Nokia and HMD's smartphones, which includes the Nokia 3 (their only MediaTek based device), will receive Android Oreo.

The Nokia 3 is the most "budget" phone of all of their smartphone line-up, and yet it too is receiving Android Oreo. This marks a change from budget phones from other manufacturers which are never usually updated, except for some exceptions. As mentioned above, there is no timeframe given, but Nokia so far has had a decent track record for device updates. Their phones are receiving timely security updates, which we've praised them for in the past. HMD Global have been critical of OEMs in the past, especially over update times. For those of you who miss stock Android, Nokia's devices run pure Android which enables quicker updates. This is also made possible by the dedication from HMD Global to update the devices quickly.

HMD Global also promised two years of updates at least, meaning the Nokia 3,  5 and 6 are pretty close to that two-year deadline for when OS upgrades come out. We'll wait and see what happens with that, but in theory, the Nokia 3, 5 and 6 could receive Android P. With HMD Global's dedication so far to updates, it's probably safe to assume that if it's possible to upgrade those devices to Android P, then they will.


 



from xda-developers http://ift.tt/2eVLqrM
via IFTTT

Nokia 8 to Cost £499 in the UK and be Shipped on the 13th of September

Many of us at XDA have been awaiting the Nokia 8 for months now, as it is the company's first Android phone running the latest Snapdragon processor, and can be considered to mark the true "return" of Nokia. The official announcement of the device showed us the specs, and now we're being shown the price and ship date.

The Nokia 8 is supposed to ship on September 13th, according to the Carphone Warehouse in the UK. It is meant to launch at a cost of £499.99. This is interesting, as the device's price in Europe was previously announced to be €599, while £499.99 at current market rates is €546. The other currently available UK seller, Clove, has released the same price and same shipping date. We noticed there are more colour options available on Clove however. The Carphone Warehouse has only the Steel and Tempered Blue colours, while Clove sells those and the Polished Blue and Polished Copper colours. There are still no announced dates or prices for a US release however. 

For those of you not familiar with the Nokia 8, if you live in the UK you will get all of the following for only £499.99.

  • Qualcomm Snapdragon 835
  • 4GB RAM
  • 1440 x 2560 pixel IPS LCD display (554 DPI)
  • 64 GB UFS 2.1 storage
  • 3090mAh battery
  • Steel, Tempered Blue, Polished Blue or Polished Copper
  • Dual 13MP camera made in collaboration with ZEISS
  • MicroSD card slot supporting SDXC
  • Nokia OZO spatial audio
  • 3.5mm headphone jack
  • IP54 certified (Protected mostly from dust, resistant to splashes of water across the front of the device)

The Nokia Steel

If you are not already interested, the HMD Global made device will run stock Android Nougat 7.1.2 at launch, with "fast updates" promised. Their current devices have been receiving timely security updates, so there is no reason to doubt them just yet. We'll need to wait and see how long takes them to release Android Oreo.

However, there is still no sign of the 6GB RAM, 128GB storage "Gloss Blue" variant which Nokia also announced. This may either be delayed, coming to other markets or cancelled entirely. Hopefully we see that device soon, as some may be waiting for that instead of buying a device with 4GB of RAM and 64GB storage. Some may find 64GB of storage small depending on how you use your device.

What's more, when ordering from the Carphone Warehouse you will also receive a free Nokia Steel smartwatch worth £119. This smartwatch has an 8 month battery life, a movement tracker and a sleep monitor. This watch will also connect to a Nokia Body+ and a Nokia BPM+. The Nokia Body+ is a smart weighing scales, while the Nokia BPM+ is a smart blood pressure monitor. You can share health data between all of your devices through the Nokia suite of products.

The Nokia 8 – Truly the return of Nokia?

The device so far looks absolutely stellar, especially at such a price point. If the price remains at £499.99, then it is in the same price range as the OnePlus 5's 128GB models. You also will have the added benefit of the majority of mobile carriers having the device for sale, while in the UK the only shops officially selling OnePlus devices are O2 stores. For those scared of purchasing their device from OnePlus (be it because of the online aspect, customer support and so on) the Nokia 8 may be an enticing prospect.

The specs are simply awesome for this price point, undercutting a lot of the competition if the device holds out to be as good as it looks on paper. We recommend waiting for reviews before making a decision, but so far the device has piqued my interest, and I assume yours too.


Via: Nokiamob

Purchase from Carphone Warehouse Purchase from Clove



from xda-developers http://ift.tt/2vZrTMG
via IFTTT

Sunday, September 3, 2017

Framework Modifications for OxygenOS on the OnePlus 5

Some people dislike certain stock settings in Android, such as the height of the navigation bar, the low battery alert, and a few other small things. XDA Senior-Member SyCreed over on our OnePlus 5 forums has released a flashable zip, modifying the system framework, which promises to do the following.

  • Removed the Input Method switch in notification panel.
  • Navigation bar height reduced from 46dp to 34dp.
  • Low battery notification will appear at 10% left, instead of 15%.
  • The volume warning is removed.
  • Enable Burn In Protection, like what smart watches use.

This mod makes changes to the framework-res.apk file located in /system/framework via a flashable zip in your recovery, so back it up in case you have any issues. This mod only works on OxygenOS on the OnePlus 5!


OnePlus 5 System Modifications



from xda-developers http://ift.tt/2iSI7G6
via IFTTT

Interview with Francisco Franco, Developer of the Franco Kernel (Part 2) – OEMs, Kernel Improvements, Custom ROMs & More!

I recently had the pleasure of interviewing the man behind one of the most popular Android kernels ever, the Franco Kernel. Currently, the kernel is available on many different devices, including various Nexus & OnePlus devices and the Google Pixel / Pixel XL.

In this part, we talk about Francisco Franco's opinions on OEMs and some changes in the Android kernel, his future plans and a bit of his personal life.


There have been reports of SDCardFS issues, like you'd see them around the forums and I'm just wondering do you think it's down to OEM implementation, like do you think the actual system is fundamentally sound and the issue is OEMs?

No no no. I think when the first issues appeared, like big issues, if I remember correctly they were on the OnePlus 3T maybe, yeah they were using a, like,half-baked SDCardFS implementation that wasn't even finished. I don't even think the Google Pixel version is 100% finished. According to the Android team, the guy that was talking about this on one of their podcasts, said they were still finishing stuff and OnePlus was using like a half year old version it was just meat work, it wasn't finished. So that's asking for trouble, I guess.

Ah okay, yeah I remember seeing stuff like files not being deleted without having to reboot, and if that's down to the OEM implementation then yeah.

Google has a common kernel tree, with all the work that they are doing to support that common tree, and then the OEMs [and] manufacturers such as Qualcomm take that common tree and build their patches on top of that, and then the OEMs get the trees from the manufacturer and then they work their specific hardware patches on top of that. So you're already on a third layer and you probably have like a half-year-old drivers most of the time, when the device ships and the SDCardFS that they were using was very old, so I think that was slightly irresponsible from them to do that. On my own my kernels, every time I've had to I've made a change so that everyone wouldn't use SDCardFS so that this wouldn't happen at all.

Seeing as you said it's slightly irresponsible of some OEMs to do that, what would your favorite OEM be in terms of developer support and just general polish?

Google. It's not even a contest, if you can count them as an OEM. Other than them.. Maybe OnePlus? Maybe now it's better? I think? Maybe? I think so. I'm here thinking, I'm looking at all my devices.

The hundreds of devices right in front of you?

I have… one, two, three, four, five, six, seven, eight, nine, ten, eleven, twelve, thirteen, fourteen
devices here!

Jesus Christ.

They are mostly Google devices, couple of OnePluses. No, Google is the best hands down, it's not a contest.

Ah okay! Well, which currently have you been working on the most recently? Like have you kind of picked up one and just decided "this is fun and I'm working on this for a while now", or is there something about the devices that draws you to one more than the other when you're developing for it?

Mmmmmm, not really. I guess if I start merging patches for the Nexus 6P, I then go to the Nexus 5X and probably go to the OnePlus 3 and 3T, and now with the [OnePlus] 5 being kind of new I took a couple days to try to understand what was happening what was needed .When I'm on the Nexus 5, I go to the OnePlus One and then the OnePlus X maybe. I think that's probably it. I don't decide I'm gonna wake up one day and decide "that's the device I'm going to work on today". I go to the forums, read what people are saying and then try to see what others have been doing and try to get tips from Google and Qualcomm and try to keep things synced together I guess. But… maybe lately I've been focusing a little bit more on the OnePlus 5 for sure, the Nexus 6P, the Nexus5X and the OnePlus 3 and 3T.

Would you have any, advice I guess, for any aspiring kernel developers or like what's been the most important skill for you as well as a kernel developer?

You have to read a lot, and I claim to know almost nothing compared to others. I guess read a lot and be prepared for long nights and if you actually want to maybe learn something really deep, choose a subsystem and try to dissect it and try to build something for that subsystem and then go from there. Maybe the scheduler one.. if I was to do that now, I would try to just study the task scheduler from the kernel and try to understand what was happening there, but it's very deep, very complicated. Make changes and just see them happening and read a lot. Subscribe to a lot of mailing lists from actual Linux and read, read a lot for sure.

Have you ever thought about development on the actual Linux kernel? Like let's say you're on the actual Linux kernel yourself, trying to merge patches look into that kind of thing.

Hmmm not at all. I don't have time for that! It's a lot bigger, and to do that you need lots of different parts of hardware to actually test stuff. I guess there are so many different developers that actually know what they're doing. I have no place in there.

Has custom ROM development ever interested you?

Pfft, not at all. It's kind of boring! Of course I've compiled Android a couple times, but it takes so long to compile and it's very boring. All the custom ROMs you see on XDA… like 99% of them are just copying patches from one another and just adding an app here and another app there, or changing some colors and then they are happy that they made some changes, and after all they didn't do anything. So I have paid no attention to that. I mean — I mean the guys from Lineage, the former CyanogenMod, those guys know what they're doing. They actually do more than just make apps. I guess now the Paranoid Android guys are doing something good of course, but I haven't been paying very much attention to them. The others, don't ask me about them either, I really don't care about ROMs.

Would you have an opinion on Paranoid Android? I know you said you don't really care, but would you have anything to say about them if you've even looked at their source code or commit history or whatever?

I remember when they started, I remember what they've done, the things they achieved back then before you had any idea of themes or colours or… the old pie controls were awesome. I respect them a lot, and there are a couple still there that I know they know what they're doing. I don't know what they are doing right now, so I cannot comment on anything I guess. If anyone is listening try them out I guess, but I really have nothing to say. I never pay attention to ROMs anymore. I guess I'm happy that they're doing something now. I hope they get to monetize what they're doing somehow, like licensing or working with other OEMs. I hope so! They also did that with the first Oxygen version for OnePlus… I hope they monetize! I guess if you're doing this, you hope you make some money out of it because working with Android, like any other platform in the world, takes time and you have to eat and pay bills like anyone else. I hope they monetize. At least something, they deserve it.

Find a way to make a living out of it.

It's hard, but at least for ROMs it's hard. But I hope they do it somehow, or consulting. There are always some OEMs that needs help with something. Those minor OEMs that don't have the budget to hire 100 guys to work on stuff. I guess that's probably something they can offer but I'm not going to give that sort of suggestion because I don't know myself but I guess that's it.

Do you have anything big in the works?

I spend most of my time working on apps, more than anything. After 6 years of patching kernels here and there it gets tiresome after a while, because most of the devices right now just ship with something that's good enough or stuff that I did before is now already there. It's also all sorts of troubles sometimes to flash a kernel. For the Google Pixel for example, it took me a long time trying to to get it out, because of their A/B system. The OnePlus 5 as well took like a week to even boot it for stupid things.

For the Google Pixel for example, it took me a long time trying to to get it out, because of their A/B system

After SELinux changes too, you get tired after a while. I still got a kick out of it and I have no intentions to stop because I also have other apps to monetize on top of it, so I would be stupid to just let it go. I have lots of users and I also owe them that because without them I wouldn't be here, so it's still a challenge but it will be less of a challenge as the time goes by because because of the changes the OEMs are making to their kernels, and Google as well. I suspect in two, three, four, four years maybe we wouldn't be able to do what we do right now because of the security changes and it's getting harder to crack. I suspect three, four years maybe I'll be out of business in these things, haha.

Do you see it as an attack on developers, or is it just a security thing?

No no no, just security! There's no attack whatsoever. I'm not a big conspiracy theorist.

Ah yeah exactly, I've seen lots of people think it's an attack on developers and all that.

No, not at all. They just want what's best for the platform and therefore the platform is having a tightened security, and if that's what they need to do, they will do it! And we are just a small niche, so if we suffer and it's good for the platform then I don't care. Because the platform has so, so many, so many users around the world and I'd rather have those half a billion users enjoy security and being safe from attacks. I don't mind if I lose my job I guess.

Do you have any other applications in the works,or any ideas for applications or are you working on improving your current ones that you have?

I pushed a new app a month ago. I think XDA wrote about it, it's called Gratus. It means "gratitude" in Latin. It's an app, almost like an offline social network, where you remember stuff that you're grateful for in your life and you post them there, and then you get reminded every time you unlock your device through a notification or widget and you just get a big smile every time you unlock your device. Imagine, on average a person unlocks their device around 100 times a day, so every time you unlock it if you see a positive message that you yourself wrote… like imagine you're grateful for your cats or your grateful for some food you love or someone in your life or some event. I mean, it just gives you a big smile and I think in a world that's so crazy right now and sometimes so negative — if you get a little kick out of your own positivity and gratitude I think it will help lots of people. The app is free, and has a small enough payment that unlocks all the features, but it already has a lot of different pictures for the free version. I guess everyone should try it.

Gratus - promoting good vibes and positivity (Free+, Google Play) →

I have lots of other apps, little tools for example yesterday I released a new version of my app called "NapTime" that improves the way Doze works on your device. Previously, it was just for rooted users. Since yesterday, it works also for non-root users.

Naptime - Super Doze now for unrooted users too (Free+, Google Play) →

I have other apps too, like the kernel app. It's one that gave me all and I still give it too much attention and I'm working on a better version, so I'm always busy.

Manager & Updater for Franco Kernel ($3.99+, Google Play) →

Always something to do and keep you going!

Haha, yes.

Well I guess there's only one more question really, which is I guess if you have any other hobbies? Anything else you would spend time on non computer-related or programming-related.

Well as probably any other normal person, I'll watch a lot of movies, I love cinema, I love watching quality movies. I like to read a lot and I'm not a pretty socially awkward guy, I am fine socially but I prefer to be alone and left alone.

Ah, so kind of an introverted kind of way?

Uhhhhh, yeah if I can I'll spend spend a week at home alone, by myself just playing games and cracking stuff. I spend a lot of time with my girlfriend of course, but it's mostly enjoy everything that you can enjoy that life gives you. I'm a pretty happy guy, I don't have that many expectations of crazy stuff to go out every day or jump off a cliff. I just really want to be left alone and hack stuff and enjoy Android, watch a good movie and read a good book, play a good game I guess. I've a pretty normal life.

Well I guess that's everything I have for you then and I guess good luck in the future!

Thank you so much I always look forward to give these interviews, I hope I was informative enough for anyone who is reading!


Check out Part 1 by clicking this button!



from xda-developers http://ift.tt/2iU473l
via IFTTT

Interview with Francisco Franco, Developer of the Franco Kernel (Part 1) – Origins, HMP vs EAS, F2FS & More!

I recently had the pleasure of interviewing the man behind one of the most popular Android kernels ever, the Franco Kernel. Currently, the kernel is available on many different devices, including various Nexus & OnePlus devices and the Google Pixel / Pixel XL.

In this part, we talk about Francisco Franco's journey into kernel development and his opinion on the changes Android has undergone over the years.


I'm Adam Conway here on XDA to interview Francisco Franco, developer of the Franco Kernel! Do you want to introduce yourself?

Sure, my name is Francisco, as you just said, and I guess I've been on XDA for 1 million years already! Been doing all sorts of stuff. Kernels, apps, and lately I've been slacking a little bit more on kernels because it gets tiresome after a while, but I'm still full force on most of my devices.

Okay, so I guess lots of people would be familiar with your work, but a lot of people wouldn't be familiar with the actual person behind the work. So I guess really do you have any kind of past experience before kernels? Like any computer science degree or anything like that beforehand?

I've always been passionate about computers, as any kid while growing up I guess. After I turned 18 and I decided to go to university like everyone else, and I think I was taking computer science or something but after a year or so, I figured that not what I was actually passionate about. After that year my expectations were starting to drop low because it was all talk and no action, and I was starting to feel bored – not because I was better than anyone else, I was just average – but the actual disciplines weren't exactly what I wanted. So I talked to my parents, and they were aware that I wasn't very happy in that.During the Christmas of 2010, I got my first Android phone. An LGP 500, that's a budget phone, very cheap, but I knew it was running Linux, and my favorite discipline in university was computer architecture or something, operating systems. And we were learning a little bit of shell and talking a little bit about the Linux kernel, and what was part of the kernel and all the connectivity in the kernel, and the actual operating system, and that was fascinating for me. And then I started to rebuild the Linux kernel for my old laptop together with a friend. We crashed our laptops like 100 times doing that, but we learned through the process. And then I started to play with my LG, and I guess the first thing I did was trying to push a little bit more performance because that device was actually pretty crappy. So the best thing I could do was just go through the standard Linux kernel parameters for the actual memory management and stuff, and just try to find something a little bit better than what was already there. I had fun a little bit then.

I think I haven't told this before in previous interviews, but back then that device was using an old file system called YAFFS – that means Yet Another Flash File System, but it was pretty slow when we tried to mount like a RAM-backed swap disk so, I don't remember specifics, but we did all sorts of different experiments with that and we ended up mounting the Dalvik on top of the memory RAM that had to be rebuilt every reboot because, as you know, RAM goes away every time we reboot. But it made opening applications and running benchmarks quite faster so we were happy. So after that, I started to go a little bit deeper, and try to compile LG's kernel sources for the device, and I made all sorts of bad judgments and all sorts of mistakes – Wi-Fi network, whatever – everything that you can possibly imagine from someone with no experience. This was fun, I learned a lot. I guess after a year or six months [of] doing that I was a little bit more focused, and I knew a little bit better what I had to get the downloads. That's what we all want at the end of the day. After that, I managed to get some donations and move up to other devices. I guess the Nexus S, then the Galaxy Nexus and then after that period, I managed to get my first app out. I guess I've been very fortunate and I've been able to finance myself buying new devices, and it blew up from there. So I guess at the end of the day I owe everything to, I wouldn't say XDA but the platform that XDA provides us.

And the community kind of behind it and all that.

Yes yes, I mean the platform, that's the community and the actual forums. For anyone listening, this isn't a paid sponsor or anything, I'm not being paid to say this, it's just true!

There's no video, the people don't see the gun being pointed at your head, it's alright.

Hahaha, yeah but someone will say that I'm being paid to say this so I'll just say it! But yeah, yeah it's been a marvelous platform for me to build cool stuff, learn a lot, I've learned everything there by mostly doing mistakes and in learning I still do my fair share of problems. I destroyed my Xiaomi Redmi Note 3, uh, the bootloader is just destroyed. So I have to connect it again with my Windows computer that's sitting back there and have to reflash everything and it's been sitting here for like three months. I'm getting all sorts of hate from everyone that I'm not paying attention to that device, and so I still make [mistakes] I guess, so even after all these years there's still stuff to learn and I've been very fortunate to have been through this journey and it's been awesome.

Well, I guess seeing as you started with the… LGP 500 was it?

Yeah, yeah.

How many years ago was that? Because that must have been around the original versions of Android right? Around Froyo or something?

Yeah, that shipped with Froyo and it was upgraded to Gingerbread couple months afterward. That device I think was 2010, beginning of 2011, probably earlier. I know my account on XDA was created in December 2010 but I had the device beforehand. So I guess probably around that time, yeah.

How has Android evolved performance wise since then? Like how has it changed for you writing kernels back then and writing them now? And I suppose what your opinions are on the changes.

Kernel wise, I think we have evolved with the actual Linux kernel and all the changes that the Android team actually wanted to implement for a certain Android release, so they dictate most of what special features the kernel will have, based on what they want to ship. But I guess actual performance, more cores actually help a lot because back then you didn't have any real way to move this thread (sic), or imagine network requests through a background thread, or at least actual real-time threading. I think that was the biggest change throughout the years, having more ways to spread out your work, and not have Android just slow down because everyone is trying to grab that little bit of CPU share. More than anything I think multi-core and actual real multi-threading backed by Linux. I thought that [was] the biggest change.

Ah okay, so what's your opinion then on HMP vs EAS? Because obviously EAS is only new and only being used in a few devices — like you use a Google Pixel right?

Yes, currently I am using a Galaxy S8, but I have a Pixel too. I don't know both in that [much] detail, they are just different implementations of how a multi-clustered device should act based on what's happening on the device at certain times. Running two different clusters with two different power consumptions, it's quite hard. You have to meet expectations of tasks moving up and down, and there's a latency involved in there and HMP was the first real implementation of a real multi-clustered architecture for ARM, because if I remember correctly, before HMP was in real-world usage, Samsung had an initial implementation where either you were using the first four cores, like low power cores, or four high-performance cores but they were never running at the same time. But then afterwards with the HMP the cores were ready to be used at any time and tasks just moved from one cluster to another and vice versa and that worked out, but you didn't have that much information from the scheduler to show this to the governor to actually decide what kind of frequency would be used at that specific time, so you had to deal with, like, trying to understand what happens in [about] 20 seconds and then based on what happened there, you decide what to do. EAS, it's more [about] understanding what's going to happen in the future and deciding in real time based on the power outputs of each core, and then it's a bunch of calculations and complicated things in the background

Like energy models and so on to back it all up.

Yes, I guess so, it's quite complicated, I don't know all the specifics I've read a bunch of documents but it's quite complicated and it's not just turning a switch on and having that ready to use. I get that question a lot can you implement EAS on XYZ phone. My replies are always "It's not turning a knob, it's not like that, it took a whole team of Googlers and guys from Linaro to implement that and you have to move stuff around, doing stuff, test stuff and that's just too much work and kind of going blind" and… yeah. It's hard.

So you have to know exactly what you're doing, it's not a one man job kind of thing?

Yeah you have to know what you're doing, anyone can pick the patches and merge them but actual testing and making sure it's working correctly and you would need a proper machine to detect the power usage of each component and there's a bunch of tables on the kernel where you can write the power of each core, and based on that the code will decide what to do. It's quite complicated. I don't think it's a definite solution for all the problems, but it's definitely the best we have right now.

So you see it as an improvement?

Yeah sure, miles miles miles away. It's a definite improvement from HMP or any other architecture, because if you can understand what's going to happen in the future you can react much faster to any request or whatever is happening on the device, that's why the Google Pixel is so fast and so smooth, because everything is happening almost in real-time. It's moving the frequencies up and down which is the easiest way to hit expectations of performance.

I guess with that then, if there's more adoption in the future of EAS, how do you see that affecting your own development as regards kernels? Would you still stick with HMP or would you go with already released energy models? For example on the OnePlus 3, [ROM developers] are re-using the energy model from the Google Pixel for EAS. Could you see yourself doing something like that?

I probably won't do that, if the device doesn't ship with EAS to begin with then I probably won't implement it in any way or form because as I said it's quite a lengthy process and no one in XDA knows better than all these engineers, so we are just trying to play God I guess.

On that note talking about the future with Android and kernels, what's your opinion then on the recent Android Oreo release? Do you think the changes are good? Have you looked at any of the new kernel commits?

There weren't as many changes on the kernel side on the Nexus 6P and the Nexus 5X, just little fixes here and there. On the Google Pixel, they were iterating on the EAS implementation, and they spent some time improving the binder section, because now the binder, together with Project Treble, it's like splitting different packages, so they have to go through 50 or 100 different patches to improve the binder and get it separated into different processes. Other than that, it was just normal work for a big release. When there's a new platform release, you usually don't mess with the kernel that much, because messing with the kernel you actually need a lot of QA, if you sometimes change one thing you hear it affects something in another subsystem. That's what they usually do, that's why you don't have a kernel version bump between platform upgrades. It is just a lot of work. Usually not worth it but yeah, it was mostly binder stuff, a little bit of the scheduler, and the usual security fixes. I went through them all, but nothing really caught my mind. My attention was only brought to the binder.

Ah okay, so just the standard stuff really.

Yeah, they're quite complicated and don't ask me for specifics!

This is an entirely different topic, what's your opinion on F2FS against ext4? Because you'd see a lot of people will say that F2FS is unstable and stuff and causes issues, I'm just kind of wondering what's your take on it.

I don't know either [about] specifics because file systems are quite hard, there are a lot of moving parts here and there. I'll just quote a Google engineer which says that based on their test, F2FS doesn't perform any faster than the ext4, and on top of that when they were testing stuff for the Google Pixel, F2FS didn't provide support for… I think it was file block encryption, while ext4 for supports it. So that alone means — just scrap it. You have to think about two things, ext4 is being worked on for like 20 years with a lot of very smart engineers from different companies and they know what they're doing. F2FS was, if I remember correctly, implemented by Samsung. It's quite a new file system so things as complicated as these take time to improve and iterate, as you can see from the Apple file system that was just released on iOS, and they are going to do the same for Mac OS. Things take time, you need a huge team to do these things correctly. I'm a big supporter of "if it's working, don't touch it" and what we have right now — it's working, and I don't think it gives you any performance problems so I don't see a reason to mess with it.

Ah okay, that's fair enough! What about SDCardFS being switched to from FUSE? What would your opinion be on that?

That happened because the older FUSE file system was one of the worst things that happened on Android. The performance was horrible, there were a lot of system calls between the kernel and the user space and now with SDCardFS it's done properly. It's a normal file system to deal with this, again I don't know the specifics as it's a very complicated thing, but what I've read and seen and heard from different podcasts from the Android team is, it basically fixed all of the problems with the old system. That was quite horrible, performance was horrible.


Check out Part 2 by clicking this button!



from xda-developers http://ift.tt/2guTu2A
via IFTTT

Support for Android Apps in Extended Desktops is Coming to Chromebooks

Since Android app support came to Chromebooks, Google has been working tirelessly in order to make these apps look and feel more integrated into the Chrome OS system. While Android app support itself is still in beta, we've seen true improvements. Apps work way more fluently compared to before, and with Android Nougat, apps can be opened in phone orientation/form instead of just a full screen, tablet interface for all apps (you can also force freeform windows in Developer options). However, while it's definitely usable up to this point, there's still plenty of work to be done. Luckily, Google is addressing some of these issues.

Before, one of the most annoying limitations of Android app support was the inability to move Android apps across extended desktops. Google has addressed this behavior, also adding some additional improvements in order to make extended display workflow more easily manageable with Android apps. As discovered by ChromeUnboxed.com, Android apps can now be moved across all displays, like regular windows inside Chrome OS. The previous behavior locked Android apps to the Chromebook's primary display, making additional screens pretty useless when using Android apps. This changed behavior should come with the newest Chrome OS update in your Chromebook.

Also, if you closed an Android app inside your other displays and you open it again, the app will reopen in that same display. These two changes, added to all the previous Android app improvements, should make for a much more cohesive and comfortable experience if you use your Chromebook with multiple screens, and should feel like a much more finished product. Having in mind that lots of Chromebooks keep getting Android Nougat app support, we're probably at the final stages of the beta, and way closer to the integrated experience Google promised almost a year ago. So, we're excited for all the changes surely coming soon to future Chrome updates. If you want to learn more about these changes, head over to ChromeUnboxed.com to read more.


Source: ChromeUnboxed.com



from xda-developers http://ift.tt/2gAFxDZ
via IFTTT