Monthly Archive:: August 2017

Apple to replace iPhone home button with gestures

Mark Gurman has a major scoop about the next iPhone:

Apple Inc. plans to transform the way people use its next high-end iPhone by eliminating the concept of a home button and making other adjustments to a flagship device that's becoming almost all screen, according to images of the new device viewed by Bloomberg News and people familiar with the gadget.

The home button is the key to the iPhone and the design hasn't changed much since it launched in 2007. Currently, users click it to return to the starting app grid that greets them multiple times a day. They hold it down to talk to the Siri digital assistant. Double click it and you get multitasking where different apps screens can be swiped through like a carousel.

Apple is preparing three new iPhones for debut next month. One of the models, a new high-end device, packs in enough changes to make it one of the biggest iPhone updates in the product's decade-long history. With a crisper screen that takes up nearly the entire front, Apple has tested the complete removal of the home button - even a digital one - in favor of new gesture controls for tasks like going to the main app grid and opening multitasking, according to the people and the images.

I don't really dwell too much on iPhone rumours, but this one is an exception because one, it's about a major change to the core user interaction model of iOS and the iPhone, and two, I happen to know this rumour happens to be accurate.

The removal of the home button and replacing it with what is effectively a gesture area is probably the single-biggest user interface change in iOS since the day it was released, and it also happens to be yet another step in the enduring quest Android and iOS are on to become more like webOS. Steven-Troughton-Smith (go support his work!) showed a number of mockups to give a better idea of what it's going to look like.

Replacing the iconic home button with a gesture area is actually a pretty fundamental shift in the interaction model of iOS. It seems to indicate that Apple is confident enough that users are well-versed in touch interfaces enough to start "hiding" important, crucial interactions - like going back to the homescreen - behind gestures that are clearly less discoverable than that huge home button. Google did something similar - but far less consequential - by removing the "drawer" button in Android's dock with a swipe-up gesture.

If this trend persists, it would seem Apple's (and to a lesser extent, Google's) engineers think that the touch paradigm is old and established enough to be more abstract, which opens up a whole slew of other possibilities. Up until now, undiscoverable gestures were generally used for more power-user oriented interactions, but with this next iPhone, they will be used for basic, cornerstone iOS interactions.

Sailfish OS 2.1.1 released

Jämsänjoki update fixes dozens of bugs reported by our community, adds many improvements and new corporate features, like mobile device management (MDM), new Camera user interface with quick access from Lock Screen, smarter Calendar on Events, WPA2 Enterprise PEAP support, new VPN options (PPTP, L2TP), Bluez version 5 for Jolla C and much more.

At some point, I need to write a retrospective of some sort about Sailfish OS. My Jolla Phone and Tablet are collecting dust in a closet somewhere, so I might as well put them to good use.

In any event, Jolla also unveiled something called Sailfish X, which is a ROM image of Sailfish for the Sony Xperia X. Interestingly enough, the ROM image isn't free - it costs about €50 and requires a Linux PC to flash it onto the Xperia X you need to buy separately. Peculiar business model, but who knows - I've seen stranger things.

Google announces ARCore, its answer to Apple’s ARKit

With more than two billion active devices, Android is the largest mobile platform in the world. And for the past nine years, we've worked to create a rich set of tools, frameworks and APIs that deliver developers' creations to people everywhere. Today, we're releasing a preview of a new software development kit (SDK) called ARCore. It brings augmented reality capabilities to existing and future Android phones. Developers can start experimenting with it right now.

We've been developing the fundamental technologies that power mobile AR over the last three years with Tango, and ARCore is built on that work. But, it works without any additional hardware, which means it can scale across the Android ecosystem. ARCore will run on millions of devices, starting today with the Pixel and Samsung's S8, running 7.0 Nougat and above. We're targeting 100 million devices at the end of the preview. We're working with manufacturers like Samsung, Huawei, LG, ASUS and others to make this possible with a consistent bar for quality and high performance.

Essentially Google's answer to Apple's ARKit, and definitely a rebranding (at least partially) of Project Tango.

Remote desktop finally coming to GNOME on Wayland

Daniel Aleksandersen writes:

Jonas Ã…dahl from Red Hat has been busy adding new D-Bus APIs to libmutter. Mutter is the GNOME window manager and Wayland compositor. The two new APIs, org.gnome.Mutter.RemoteDesktop and org.gnome.Mutter.ScreenCast, expose a PipeWire stream containing the contents of the system's screens. The new APIs can create full-screen streams, or streams for individual windows. Only the former has been implemented.

These new APIs finally allows for services such as RDP and VNC servers and screen recording under Wayland. Once again, Mr. Ã…hdahl delivers! He has also created GNOME Remote Desktop, a new user-level systemd service daemon that is built on the new RemoteDesktop API in libmutter, plus VNC support from libvncserver. The new service can be used to connect up a remote VNC client to your local screen’s session. GNOME Remote Desktop appears to be a drop-in replacement for Vino server.

GNOME has been without its own Remote Desktop option since the switch to Wayland, and this work fills that gap.

Half-Life’s writer maybe just revealed the plot of HL2: Episode 3

So this happened, and half the internet is in a frenzy. Now, admittedly, it doesn't take much to frenzy the internet, but this is truly a doozy:

The lesson here is "never go to sleep". All sorts of things happen while people sleep. Cats go on adventures, presidents threaten nuclear war and, well, ex-Valve writers post thinly-disguised plot summaries of the unreleased and, so far as best guesses go, long-cancelled Half-Life 2: Episode 3. Long time Half-Life scribe, the excellent Marc Laidlaw (who left Valve last year), casually tossed out a link to his website last night, which led to a short story about Gertie Fremont, Alex Vaunt and their climactic battle against evil alien invaders the Disparate (the site's having a wobble, but the page is archived right here).

While that might sound like satirical tomfoolery, the actual story very much sounds like how the final chapter of Half-Life 3 could have played out. It involves time-travelling cruise liners, resurrected overlords, the heart of the Combine and the fate of one Doctor Gordon Freeman.

This is really happening.

Everything points to this being a thinly-veiled act of rebellion against Half-Life's creators never getting the chance to finish the story they were telling. Half-Life 2: Episode 2 ended on probably the biggest unfulfilled cliffhanger in gaming history, and for almost ten years now, we've been waiting for a continuation or a conclusion. This must be incredibly frustrating for the original creators of the Half-Life series, and honestly, I'm surprised it's taken them this long to start breaking rank.

From everything we've heard over the years, we can conclude that there will never be a Half-Life 3 or even an Episode 3. Many - if not most - of the original creators of Half-Life 1 and 2 have left Valve, and the company has little to no incentive to create a game that, like Duke Nukem Forever, will never live up to the hype they themselves created.

The established theory regarding why there's no Half-Life 3 or Episode 3 is that Valve wanted the game to be as defining and revolutionary as Half-Life 1 and Half-Life 2, but I think that's the wrong mindset to have. Gaming has come a long, long way since the late 90s and early 2000s, and over roughly the past decade or so there simply haven't been any games that rebooted or revolutionised entire genres, or established new ones. The only game I can think of in the past ten years that created a new genre of games and had an everlasting impact on the industry is Minecraft, and that was a fluke.

The industry is more mature, more settled now, and it's much harder to be revolutionary today than it was 20 years ago. The great games of today aren't revolutionary; they are evolutionary, perfecting and polishing established genres, taking them to new heights. Games like The Witcher 3 and Horizon: Zero Dawn aren't loved because they changed the industry; they're loved because they took existing genres and executed them in the very best ways the current generation of technologies allows us to do.

I see no reason why Half-Life 3 or Episode 3 should change the world or revolutionise what we think of as games. Just let it tell a great story with the characters we love, polish its chosen genre to perfection, and people will love it just as much 20 years from now as we love Half-Life 1 and 2 today.

Germany publishes ethical guidelines for self-driving cars

Some light weekend reading: ethical guidelines for self-driving cars, as proposed by an ethics commission of the German government.

The technological developments are forcing government and society to reflect on the emerging changes. The decision that has to be taken is whether the licensing of automated driving systems is ethically justifiable or possibly even imperative. If these systems are licensed - and it is already apparent that this is happening at international level - everything hinges on the conditions in which they are used and the way in which they are designed. At the fundamental level, it all comes down to the following question. How much dependence on technologically complex systems - which in the future will be based on artificial intelligence, possibly with machine learning capabilities - are we willing to accept in order to achieve, in return, more safety, mobility and convenience? What precautions need to be taken to ensure controllability, transparency and data autonomy? What technological development guidelines are required to ensure that we do not blur the contours of a human society that places individuals, their freedom of development, their physical and intellectual integrity and their entitlement to social respect at the heart of its legal regime?

Cars are legalised murder weapons, and the car is probably one of the deadliest inventions of mankind. Self-driving cars, therefore, open up a whole Pandora's box oef ethical dilemmas, and it only makes sense for governments and lawmakers to start addressing these.

Beyond the ethics related to life and death, though, there are also simpler, more banal ethical considerations. What if, in the hunger for more profits, a car maker makes a deal with McDonalds, and tweaks its self-driving car software just a tad bit so that it drives customers past McDonalds more often, even if it increases total travel time? What if a car maker makes similar deals with major chains like Target, Walmart, and Whole Foods, so that smaller chains or independent stores don't even show up when you say "take me to the nearest place that sells X"? Is that something we should allow?

Should we even allow self-driving car software to be closed-source to begin with? Again - cars are legal murder weapons, and do we really trust car manufacturers enough not to cut corners when developing self-driving car software to meet deadlines or due to bad management or underpaid developers? Shouldn't all this development and all this code be out there for the world to see?

Interesting times ahead.

Librem 5: a security and privacy focused GNU/Linux smartphone

Purism, maker of Linux laptops with Coreboot, have started started a crowdfunding campaign for their smartphone. Now, I rarely - if ever - link to crowdfunding campaigns (for obvious reasons), but I feel this one might just be quite, quite desirable for many OSNews readers.

Librem 5, the phone that focuses on security by design and privacy protection by default. Running Free/Libre and Open Source software and a GNU+Linux Operating System designed to create an open development utopia, rather than the walled gardens from all other phone providers.

A fully standards-based freedom-oriented system, based on Debian and many other upstream projects, has never been done before - we will be the first to seriously attempt this.

The Librem 5 phone will be the world's first ever IP-native mobile handset, using end-to-end encrypted decentralized communication.

It'll have hardware killswitches for the camera, microphone, WiFi, and the baseband. I wish the team a lot of luck - they'll need it, because making a phone is hard.

Android 8.0 overhauls installing apps from unknown sources

This is a pretty big change, detailed only a few days ago.

Eagle-eyed users of Android O will have noticed the absence of the 'Allow unknown sources' setting, which has existed since the earliest days of Android to facilitate the installation of apps from outside of Google Play and other preloaded stores. In this post we'll talk about the new Install unknown apps permission and the security benefits it brings for both Android users and developers.

Google goes into more detail a few paragraphs down:

In Android O, the Install unknown apps permission makes it safer to install apps from unknown sources. This permission is tied to the app that prompts the install - just like other runtime permissions - and ensures that the user grants permission to use the install source before it can prompt the user to install an app. When used on a device running Android O and higher, hostile downloaders cannot trick the user into installing an app without having first been given the go-ahead.

This new permission provides users with transparency, control, and a streamlined process to enable installs from trusted sources. The Settings app shows the list of apps that the user has approved for installing unknown apps. Users can revoke the permission for a particular app at any time.

Good move.

Samsung unveils Galaxy Note 8

Samsung has finally unveiled the Galaxy Note8, revealing the (rather heavily-leaked) device at its Unpacked event in New York City today. You won't be surprised to know that it comes with little in the way of surprises. It's basically a bigger Galaxy S8+ with a stylus and dual cameras.

The Note8 is something of a chance for Samsung to make things up to fans of the Note series, after the Note7 was forced off shelves because of defective batteries that led to the smartphone catching fire. Knowing that Note fans were deprived of a generation of hardware, Samsung is likely eager to capitalize on the eagerness of said fanatics to finally upgrade.

I'm not the target market for a Note, but you have to admit - these recent Samsung flagships are a far, far cry from the ugly, plasticky crap they used to make. There's no accounting for tastes - or practicality - but this Note 8 is a beautiful piece of engineering.

Rethinking the D-Bus message bus

David Hermann writes:

Later this year, on November 21, 2017, D-Bus will see its 15th birthday. An impressive age, only shy of the KDE and GNOME projects, whose collaboration inspired the creation of this independent IPC system. While still relied upon by the most recent KDE and GNOME releases, D-Bus is not free of criticism. Despite its age and mighty advocates, it never gained traction outside of its origins. On the contrary, it has long been criticized as bloated, over-engineered, and orphaned. Though, when looking into those claims, you’re often left with unsubstantiated ranting about the environment D-Bus is used in. If you rather want a glimpse into the deeper issues, the best place to look is the D-Bus bug-tracker, including the assessments of the D-Bus developers themselves. The bugs range from uncontrolled memory usage, over silent dropping of messages, to dead-locks by design, unsolved for up to 7 years. Looking closer, most of them simply cannot be solved without breaking guarantees long given by dbus-daemon(1), the reference implementation. Hence, workarounds have been put in place to keep them under control.

Nevertheless, these issues still bugged us! Which is, why we rethought some of the fundamental concepts behind the shared Message Buses defined by the D-Bus Specification. We developed a new architecture that is designed particularly for the use-cases of modern D-Bus, and it allows us to solve several long standing issues with dbus-daemon(1). With this in mind, we set out to implement an alternative D-Bus Message Bus. Half a year later, we hereby announce the dbus-broker project!

The Apple IIe design guidelines

Just a scanned PDF version of the Apple IIe design guidelines.

This guide is divided into two parts. Part I contains recommendations to softqare, firmware and hardware designers who want their products to work smoothly with the Apple IIe, as well as the Apple II and II Plus. These recommendations pertain to the interface between Apple II Series computers and the products that are to work with them.

Part II pertains to the interface between software products and their human users. The recommendations in this section of the guide apply to designers of software for Apple IIIs as well as Apple IIs. The user interface guidelines derive from the experience of countless Apple II and III users, as observed by more than a dozen computer and teaching professionals. These guidelines should make it easier for both programmers and users to create and benefit from the tools that Apple computers put at their disposal.

An awesome read.

Introducing Chrome Enterprise

Since we launched Chrome OS in 2009, our goal has been to build the simplest, fastest, and most secure operating system possible. And we've been inspired by all the ways we've seen businesses embrace Chrome, from Chromebooks in the office, to shared Chrome devices in the field, to signage and kiosks for customer engagement in retail. But with so many different business needs - not to mention so many different devices - companies have also told us they want a single, cost-effective solution that gives them the flexibility and control to keep their employees connected. That's why today we're announcing Chrome Enterprise.

Chrome Enterprise offers a host of features, including access to enterprise app storefronts,  deep security controls, 24/7 support, as well as integration with cloud and on-premise management tools, VMware Workspace ONE and Microsoft Active Directory.

Chrome OS keeps marching on.

Why PS4 downloads are so slow

Game downloads on PS4 have a reputation of being very slow, with many people reporting downloads being an order of magnitude faster on Steam or Xbox. This had long been on my list of things to look into, but at a pretty low priority. After all, the PS4 operating system is based on a reasonably modern FreeBSD (9.0), so there should not be any crippling issues in the TCP stack. The implication is that the problem is something boring, like an inadequately dimensioned CDN.

But then I heard that people were successfully using local HTTP proxies as a workaround. It should be pretty rare for that to actually help with download speeds, which made this sound like a much more interesting problem.

The detailed article contains tips to address the problem somewhat.

Google officially releases Android 8.0 Oreo

Today, we are officially introducing Android 8.0 Oreo, the latest release of the platform - and it's smarter, faster and more powerful than ever. It comes with new features like picture-in-picture and Autofill to help you navigate tasks seamlessly. Plus, it's got stronger security protections and speed improvements that keep you safe and moving at lightspeed. When you're on your next adventure, Android Oreo is the superhero to have by your side (or in your pocket!).

Coming to a device near you. Eventually. Maybe. But probably not.

Google to release Android O on 21 August

On August 21st, a solar eclipse will sweep across the entire United States for the first time since 1918. Android is helping you experience this historic natural phenomenon so you can learn more about the eclipse and count down to the big day - when you’ll meet the next release of Android and all of its super (sweet) new powers, revealed via livestream from New York City at 2:40PM ET.

If a new operating system version is released, but nobody's able to use it, has it really been released?

Getting my Amiga 1000 online

Amiga Love has had a few articles on getting various Commodore machines back online and into the BBS world. From C64s to Amiga 500s (et al) as well as the terminal programs we use; PETSCII capable (i, ii) in case you're trying to hit an C64 BBS from your Amiga or ANSI capable, like A-Talk III, for most other boards. There are a lot of options out there, and the BBS scene is vastly smaller than back in the day, but it's not dead by any stretch. Oh no, dear reader, it is not dead. (I see four lights!) If anything, the interest in this form of socializing and connecting seems to be growing lately as hardware options become easier to build and less expensive to source.

Tonight, I finally got my Amiga 1000 online for the first time ever and connected to some of my favorite BBSes. And oh my god, have you ever seen a more beautiful sight? I doubt it. Well, at least not for about 30 years, give or take.

About 2000 years from now, Amiga will be the object of a world religion. It just cannot die.

Retesting AMD Ryzen Threadripper’s game mode

In this mini-test, we compared AMD's Game Mode as originally envisioned by AMD. Game Mode sits as an extra option in the AMD Ryzen Master software, compared to Creator Mode which is enabled by default. Game Mode does two things: firstly, it adjusts the memory configuration. Rather than seeing the DRAM as one uniform block of memory with an ‘average’ latency, the system splits the memory into near memory closest to the active CPU, and far memory for DRAM connected via the other silicon die. The second thing that Game Mode does is disable the cores on one of the silicon dies, but retains the PCIe lanes, IO, and DRAM support. This disables cross-die thread migration, offers faster memory for applications that need it, and aims to lower the latency of the cores used for gaming by simplifying the layout. The downside of Game Mode is raw performance when peak CPU is needed: by disabling half the cores, any throughput limited task is going to be cut by losing half of the throughput resources. The argument here is that Game mode is designed for games, which rarely use above 8 cores, while optimizing the memory latency and PCIe connectivity.

I like how AnandTech calls this a "mini" test.

In any event - even though Threadripper is probably way out of the league of us regular people, I'm really loving how AMD's recent products have lit a fire under the processor market specifically and the self-built desktop market in general. Ever since Ryzen hit the market, now joined by Vega and Threadripper, we're back to comparing numbers and arguing over which numbers are better. We're back to the early 2000s, and it feels comforting and innocent - because everyone is right and everyone is wrong, all at the same time, because everything 100% depends on your personal budget and your personal use cases and no amount of benchmarks or number crunching is going to change your budget or personal use case.

I'm loving every second of this.

iOS 11 has a ‘cop button’ to temporarily disable Touch ID

Apple is adding an easy way to quickly disable Touch ID in iOS 11. A new setting, designed to automate emergency services calls, lets iPhone users tap the power button quickly five times to call 911. This doesn't automatically dial the emergency services by default, but it brings up the option to and also temporarily disables Touch ID until you enter a passcode. Twitter users discovered the new option in the iOS 11 public beta, and The Verge has verified it works as intended.

It's sad that we live in a world where our devices need features like this, but I commend Apple for doing so.

Build your own Linux

This course walks through the creation of a 64-bit system based on the Linux kernel. Our goal is to produce a small, sleek system well-suited for hosting containers or being employed as a virtual machine.

Because we don't need every piece of functionality under the sun, we're not going to include every piece of software you might find in a typical distro. This distribution is intended to be minimal.

Building my own Linux installation from scratch has always been one of those things I've wanted to do, but never got around to. Is this still something many people do? If so, why?