Tag: Android

Troubleshooting in-app QR-code scanning on your phone

Service Victoria contact-tracing QR code sign at Fairfield Primary School

The Service Victoria QR-code contact-tracing system was one of those app-based QR code setups that may not work properly if your phone’s QR code recognition subsystem isn’t working

A situation that happened with my Android phone recently was that the Services Victoria QR code app failed to recognise a check-in QR code even though it has normally been doing that before. I had to then resort to entering the venue-specific manual-entry code printed below the QR code on the signage to begin the check-in process for that area.

This problem can also happen with something like WhatsApp, Signal or something similar when you are attempting to bind a desktop or other secondary client device to your service’s account. This also extends to Wi-Fi Easy Connect setups that allow you to enrol your phone or another device in to a desired Wi-Fi network.

It can also happen with book+app setups used with interactive books, second-screen apps that are part of interactive-TV setups, or some app-driven coupon systems that are dependent on recognising QR codes for their functionality. Even setting up app-based multi-factor or password-free authentication is dependent on QR codes when you are provisioning that mobile-based authentication app with an online service.

In use cases like WhatsApp, there may not be any alternative like a human-readable code or an NFC tag to use as an alternative to scanning a QR code. This would then make the app or function useless for its intended purposes.

The situation described here is that a QR-code-dependent app that was previously recognising QR codes for that associated system fails to recognise them.

But how did I troubleshoot this problem further?

A lot of these apps that have QR-code scanning functionality are dependent on functionality within iOS or Android that works with the camera to recognise these codes and make them useful for software on your phone. This is to avoid the need for the software developer to reinvent the wheel when it comes to adding this functionality to their apps.

WhatsApp and Signal's relationship with their desktop clients

.. as can setting up Signal or Whatsapp to work with your regular computer or iPad

But if this fails, the apps that depend on this functionality don’t perform as expected when you attempt to scan a QR code with them. This is even though they have enabled the camera and are passing through the vision to the app’s “viewfinder” window. Of course you might think that the rear camera’s lens is dirty or scratched or you are attempting to scan a poor-quality reproduction of the code.

One way to troubleshoot this kind of situation is to scan this kind of code with a dedicated QR-code scan app that is part of your phone’s operating system. Most Android users would have this as part of the Quick Settings menu. Here, this app has the camera behave in a manner optimised for scanning barcodes and QR codes as if it is called upon by one of these QR-dependent apps.

On some platforms, the Camera app’s QR-code recognition function may behave differently due to it using different in-app software from what is part of your phone’s operating system. This is due to the camera software working on a “photography first” approach rather than a “barcode scanning first” approach.

If this app fails to recognise any QR code, you are dealing with a situation where the software processes associated with QR-code recognition crashing or hanging. This situation may happen with other software on your phone underperforming or behaving in an abnormal manner. Here, you may find that it is a good idea to fully restart your phone, which will effectively get everything to a known point.

In this case, you would have to shut down then restart your phone so as to cause it to fully restart. You should see your phone’s manufacturer or operating system logo appear on the screen as part of the restart process.

After the phone is restarted completely, attempt to scan any QR code with the above-mentioned dedicated QR-code scan app that is part of your phone’s operating system. Usually that will succeed after you have restarted your phone due to the necessary software processes being restarted.

You may have also had to deal with a software update for the QR-code recognition software as part of a software-quality or security update for your phone’s operating system. It is typically to rectify any bugs or security exploits in the affected software or simply to “tune up” the software for better performance.

If that succeeds, attempt to scan the QR code using the app you had problems with so you can identify whether that app is at fault or not. It is also a good idea to check for new versions of this app by visiting your mobile platform’s app store and checking for software updates.

The need for a software update for that app may be due to the app’s developers re-engineering it to take advantage of newer QR-code-recognition software libraries, and may also have to apply for any QR-code-dependent apps on your phone. It is although the revised software libraries are most likely written to support “legacy” application software but offer a “new way in” for newer apps.

In the case of your jurisdiction’s contact-tracing check-in app, you may have to do a Google image search for QR codes relating to that platform. Here, some of these images will represent a sharp-enough representation of a “production” QR code at a known place. Or a club or similar organisation may have set up and posted a “test” or “set-up” code to help members with the onboarding process for the contact-tracing check-in platform.

Conclusion

Your phone not working properly with QR codes may not be just a camera or lens problem but software associated with this functionality that simply had stalled or crashed. Here, you may find that you simply restart your phone to gain full functionality.

Some apps on your Android device crashing lately? WebView may be the culprit

Article

Android main interactive lock screen

Apps crashing frequently on your Android smartphone or tablet? Check out Webview – it may be the culprit.

Android apps like Gmail are crashing and ‘WebView’ is to blame | Engadget

My Comments

You may have found that with your Android phone some apps like news apps, email apps or online banking apps are crashing lately. It will also affect apps or games that use advertising and the app or game crashes when an ad appears.

This is to do with the Webview system app that allows a native Android app to utilise Google Chrome’s logic to show Web-based HTML content within the app’s user interface. But a recent version of this app has been found to be buggy and is responsible for causing these software crashes.

A temporary fix that has been put forward is to uninstall the latest Chrome updates on your Android device. Or you go to the Google Play Store or the Settings – Apps menu to uninstall Android System Webview.

But Google have lately worked on a bugfix for this problem and are now rushing this out as a software update for Chrome and Webview. These are expected to be delivered as part of the latest Google Play software updates and should be delivered by 24 March 2021. On some devices, you may find that these updates are delivered as separate packages.

Once these are updated, you shouldn’t find your apps that use Web-based content crashing frequently.

Google improving on their simplified cross-platform software development platform

Article

Samsung Galaxy Tab Active 8" business tablet press picture courtesy of Samsung

It will become easy to develop apps to run on smartphones..

Microsoft helps with Google’s Flutter 2 update to improve apps on Surface Duo | Windows Central

Google’s Flutter 2 update could be a major win for apps on Windows 10 | Windows Central

My Comments

Now with three major desktop computing platforms and two mobile computing platforms on the market, there is a demand to create software that can run on all of them. It also means that the software has to operate in a manner that suits the different user experiences that different computing devices offer.

Lenovo Yoga Tablet 2 tablet

.. and tablets

The differing factors for the user experiences include screen size and general aspect ratio as in “portrait” or “landscape”; whether there is a keyboard, mouse, stylus or touchscreen as a control interface; or, nowadays, whether there are two or more screens. Then you have to think of whether to target a mobile use case or a regular-computer use case and optimise your software accordingly. You may even have to end up targeting “small mobile” (smartphone), “large mobile” (iPad or similar tablet), “desktop” (desktop or laptop computer including 2-in-1 convertibles) or “lean-back” (smart TV / set-top / games console) use cases at once.

Dell XPS 13 Kaby Lake

.. and laptops with the same codebase

Google and Microsoft have established a partnership to make Google’s Flutter 2 software development platform as something to create desktop+mobile software solutions. It is building on Microsoft’s foundation stones like their BASIC interpreters which got most of us in to personal computing and software development.

Here it is about creating common codebases for native apps that target iOS, Android, Windows 10, MacOS and Linux; alongside Web apps to work with Chrome, Firefox, Safari and Edge. But the question that could be raised is if an app is targeted for Google Chrome, would this work fully with other Chromium-based Web browsers like the new Microsoft Edge browser, the Opera browser or Chromium for Linux.

The creation of Web apps may be about being independent of platform app stores which have a strong upper hand on what appears there. Or it may be about reaching devices and platforms that don’t have any native software development options available to average computer programmers.

Some of the targeted approaches for this new platform would include “progressive Web apps” that can run on many platforms using Web technology and omit the Web-browser “chrome” while these apps run.

The new Flutter 2 platform will also be about creating apps that take advantage of multiple-screen and foldable setups. This is in addition to creating fluid user interfaces that can run on single-screen desktop, tablet and smartphone setups. The idea of creating a user interface for multiple-screen and foldable setups is seen as catering to a rare use case because of fewer foldable devices like the Microsoft Surface Duo on the market let alone in circulation. Another question that can crop up is multiple-screen desktop-computing setups and how to take advantage of them when creating software.

What I see of this is the rise of software-development solutions that are about creating software for as many different computing platforms as possible.

Microsoft to support Android on Windows further

Articles

Computer - smartphone interlink concept

Android and Windows are getting closer with Microsoft working on having Android apps run on Windows 10 in a virtual machine

Microsoft’s ‘Project Latte’ aims to bring Android apps to Windows 10 | Windows Central

Microsoft is working on an Android subsystem for Windows 10 | Bleeping Computer

My Comments

Microsoft is intending to have Windows able to run software written for the Android mobile operating system.

There was a previous attempt in the form of Project Astoria to simplify the process of porting Android apps to Windows 10. But recently the “Your Phone” subsystem offered to people who use certain Android phones the ability to run their apps in Windows. This worked around having Windows 10 working as a graphical terminal for your Android phone in order to run the Android software.

But Microsoft is using Windows Subsystem for Linux, currently used to run text-based UNIX/Linux environments on Windows,  as a basis to run Android software on your Windows computer. Firstly, Android is a Google-based fork of Linux intended for mobile-platform devices and this may make Microsoft’s job more easier.

Here the Android app will be run within an Android virtual machine on your Windows computer. This is in conjunction with WSL gaining support for X11 (X Window) and Wayland GUI subsystems for UNIX/Linux computing so that graphically-rich software for those platforms, including shells like GNOME can run on Windows 10.

There will be a requirement to make the Android app independent of Google Play Services because Google won’t release this functionality to devices other than native Android or ChromeOS devices. But this could be part of repackaging the software for the Windows platform.

This kind of compatibility will encourage Android software developers to write software that takes advantage of devices with large display surfaces like tablets and Chromebooks as well as smartphones. It will also make this software relevant to people who use Windows-based 2-in-1s like the Dell Inspiron 14 5000 or the Lenovo Yoga range.

There will be some app classes that will benefit from being made available through the Microsoft Store to run on Windows computers. Some apps like native clients for video-on-demand services will be about being able to enjoy these online video services on your laptop. The same holds true for sports scoreboard apps and mobile-platform “guilty-pleasure” games. Also there will be the idea of having Instagram, Snapchat and co running on your regular computer which will be valued by those of us who see a social media presence of importance for ourselves or our business efforts. Let’s not forget taxi and rideshare booking apps where there is the desire to use them from a regular computer perhaps to book rides for others.

Another use case is software written to make your Android phone a control surface for the smart home. It is primarily exhibited through “app-cessory” software that is written to convert your smartphone in to a control surface for various devices with the link facilitated using Wi-Fi or Bluetooth. But it can be software written to manage a smart-home platform like Amazon Alexa or Google Home and there may be the desire to have this run on a regular Windows computer.

Microsoft will need to have extra people to vet software that comes in to the Windows Store in order to keep malware out. This is because Google was overwhelmed with Android-based malware creeping in to their Play app store and they had to increase the number of people taking control over what ended up there. This danger will increase especially if it is feasible to “write once run anywhere” for both Windows and Android.

It is part of having Microsoft Windows 10 as the most flexible open-frame desktop operating system thanks to it supporting a wide range of software types: Progressive Web Apps, Win32 native Windows apps, Universal Windows Platform apps, UNIX/Linux software via Windows Subsystem for Linux and, to come, Android through Project Latte.

Having Windows, desktop Linux or ChromeOS on the desktop and Android on the mobile devices could be about building out a computing ecosystem that is totally about flexible open-frame computing.

Microsoft to allow Android apps to run with Windows

Computer - smartphone interlink concept

You can soon run your Android phone’s apps on your Windows computer but they will run in place on the smartphone with your Windows computer being the user interface

Article

Soon launch Android apps on Windows 10 PC via Your Phone app, as Samsung & Microsoft collaborate | Windows Central

Microsoft Your Phone’s Android apps access feature will be available for all Android smartphones eventually | Windows Central

My Comments

Most desktop-operating-system vendors and other third parties are implementing software that interlinks mobile-platform devices, especially smartphones, with your regular desktop or laptop computer.

It is capitalising on the fact that the user interface and software that a regular computer running a desktop operating system has is more capable for making your work presentable, compared to what a smartphone or mobile-platform tablet offers. But your smartphone or mobile-platform tablet can earn its keep for acquiring content for your magnum opus like taking notes, taking quick photos or browsing the Web for material.

This is typically to allow you to gain access to your mobile device’s data or use your mobile device’s native communications ability from your regular computer’s screen and keyboard. Some of these platforms may even allow you to start viewing a Website on one device then continue viewing it on the other device; or even implement a cross-device “clipboard” so you can copy something you saw on your mobile device then paste it in to something you are editing on your regular computer.

But Microsoft have taken this concept further by working on the “Your Phone” interlink software to allow you to run software installed on your Android smartphone from your Windows 10 regular computer. For example, you could effectively manage your Instagram presence using your Android smartphone’s Instagram client but working it with your Windows laptop’s screen and keyboard. Or you could kill time during a long process on your Windows computer by running a “guilty-pleasure” casual game that you normally play on your Android phone but have its user interface happening on the regular computer.

Effectively, this arrangement runs the software on your Android phone but has your Windows-based computer acting as a “terminal” that is providing input and output for that phone.  It is based on Microsoft’s experience with Remote Desktop Protocol a.k.a Terminal Services which allows one Windows computer to effectively control another Windows computer.

Some questions may come about like transferring files between your computer’s Windows file system and your smartphone’s Android file system for uploading to the app, something that will be considered important for Instagram users who upload video content.

When this function is released as part of the next major feature update for Windows 10, it will initially be able to only work with some Samsung devices. But Microsoft will intend to have it fully available across all of the Android-based devices that can run the “Your Phone” Windows interconnector software.

Here, Microsoft is underscoring the idea of allowing “open-platform” mobile-computing and regular-computing devices to interlink with each other no matter the operating system. This is even to the extent of running mobile-platform apps “in place” on the mobile device.

Google to make USB Power Delivery mandatory for newer USB-C Android devices

Article

USB-C connector on Samsung Galaxy S8 Plus smartphone

Newer Android smartphones and tablets with USB-C ports will need to be compliant with USB Power Delivery

Google now requires Digital Wellbeing and USB-C PD charging standard for new Android phones | The Verge

Google will require ALL Android devices with USB-C to support USB-PD | AusDroid

Google requires new Android devices with Type-C ports to not break USB-PD compatibility | XDA Developers

What Is USB-PD And Why Is Google Enforcing It? | Gizmodo

USB Power Delivery explained | Android Authority

My Comments

A feature that is asked for with smartphones and tablets is to support fast battery charging as well as the ability to operate the mobile device on external power while it charges.

Dell XPS 13 2-in-1 Ultrabook - USB-C power

… to have the same kind of USB-C power-supply connectivity as this Dell XPS 13 2-in-1 Ultrabook

Typically this was satisfied by USB battery chargers working up to 5V 2.4A and feeding the device from a USB Type-A socket to a USB Micro-B, USB-C or Apple Lightning (MFi) port. As well, chipset manufacturers like Qualcomm introduced proprietary fast-charge solutions that different phone manufacturers implemented. These required the use of chargers that had the corresponding chipset circuitry and often they were offered by the phone’s manufacturer as a supplied or “official” accessory.

But Google are now requiring that Android devices that have a USB-C connection are to fully support USB Power Delivery. This was initially a recommended feature but from September 2019 it will be a mandatory feature for new Android smartphones to gain full software support like Google Play Services and the Google Play Store.

USB Power Delivery is already implemented as the power source for laptops like recent iterations of the Dell XPS 13 or Apple MacBook Air or as a power-source option for USB-C-equipped laptops like the Dell Inspiron 14 5000 2-in-1 convertible laptop. This is augmented with the availability of power-supply devices working to this standard such as battery packs or USB-C monitors.

Here, Google wants to implement the USB-PD standard for the Android platform for a number of reasons. Here USB-PD implements a standard voltage-and-current ladder to supply power to the device according to what the power-supply device can offer and what the device can take. Therefore an Android device manufacturer can design a device to take the right power level to, perhaps, facilitate fast-charging or high-performance operation while connected to a USB-PD power source.

As well, the standard is a known common standard that is managed by USB Implementers Forum rather than a device or chipset vendor for the benefit of the industry. This puts less pressure on power-supply vendors to cater to different proprietary fast-charging requirements.

This standard will also accelerate the availability of USB-PD-compliant power-supply designs for every sort of application and at price points that appeal to everyone. It can also encourage innovation when it comes to power-supply design whether this is for one or more devices or to work from an internal battery, 100-250V AC mains power or 12-24V DC vehicle/marine/aircraft power.

Householders won’t even have to worry about the number of USB chargers available that will charge their mobile device quickly. As well, the environment will benefit because of the reduced number of useable chargers going to landfill but the reality with these chargers is that they are still kept available as “spare” or “convenience” chargers until they fail to function.

USB Power Delivery can also allow for a mobile device to be a power source for a peripheral like a portable hard disk or a USB digital noise-cancelling headset. This may require the mobile device to be equipped with two USB-C sockets if it is to be of use with people who need to be able to run their devices from external power.

Personally, I could see this happening that someone will engineer a cost-effective way to have a USB-PD-compliant power supply to simply be a general-purpose power supply. This will end up with this technology being used simply to power all sorts of lighting, novelties and other devices, like what is happening with the current USB specification.

Google’s approach with mandating the use of USB Power Delivery for all Android mobile devices equipped with USB-C connectors will keep up Android’s fame as the mobile platform built on common open standards.

Google to provide wireless across-the-room data transfer to Android

Article

USB-C connector on Samsung Galaxy S8 Plus smartphone

Google Fast Play could open up an improved point-to-point data transfer experience to Android smartphones

Google working on ‘Fast Share,’ Android Beam replacement and AirDrop competitor [Gallery] | 9To5Google.com

Fast Share is Google’s Android Beam replacement: Here’s what you should know | Android Authority

My Comments

Google is to provide as part of the Android platform a new “open-frame” point-to-point data-transfer solution. This solution, known as Fast Share, implements Bluetooth and peer-to-peer Wi-Fi to transfer text, pictures, Weblinks and other resources.

The Android platform had two different peer-to-peer data-transfer solutions previously. The first of these was the Bluetooth profile that was implemented by Symbian, Microsoft and others to transfer pictures, contact details and the like since the rise of the feature phone. The second of these was the Android Beam which used NFC “touch-and-go” as a discovery method and initially used Bluetooth but moved towards peer-to-peer Wi-Fi as a transfer method.

This was while Apple was using AirDrop across their ecosystem which included iPhones and iPads. In Apple’s true style, it was part of keeping as many users on the iOS platform and you couldn’t do things like transfer to other mobile or desktop platforms.

Google is intending to have Fast Share as part of their Play Services software package rather than being “baked in” to a particular version of the Android operating system. Here, Fast Share can be run with Android devices running older versions of the operating system which is a reality with a significant number of phones where the manufacturer won’t provide support for newer Android versions on particular models.

Advance images of this concept shown on the Web are underscoring a tentative plan to port it to their own ChromeOS and Apple’s iOS operating systems. If Microsoft and Apple are interested, it may be seen as a way for Windows or MacOS regular-computer users to share resources across the room on an ad-hoc basis. As well, Google could look at how Fast Share can be implemented in a “headless” form whether for sending or receiving the data.

You will have the ability to share file-based resources like photos, videos, PDFs or vCard-based contact-information files along with URLs pointing to Web-hosted resources or snippets of text. This will satisfy most usage requirements like sharing family snapshots, contact details or Weblinks.

There will be the option to give a sender “preferred visibility” status so they can discover your phone when you are near them. This status means that they will see your device if you aren’t running the Fast Share app. Of course, users can turn Fast Share on and off as required, preferably with the idea of turning it off when using the phone in a public place unless they expect to receive something. You also have the ability to decline or accept incoming files so you have some control over what you receive.

The core issue with Google Fast Share and similar point-to-point across-the-room file-transfer platforms is that they have to work in a truly cross-platform manner so you don’t have to worry whether your friend sitting in that armchair across from you is using an iPhone or Android device when you intend to send that photo to them or share your contact details.

An Android app turns your Chromecast-equipped TV in to a whiteboard

Article

Cast Drawings On Your Phone To Your Television Using A Chromecast And This App | Lifehacker

Video (Click or tap to play)

Get this app here

CastPad (Google Play for Android)

– Free version has ads, in-app purchase for premium version

My Comments

The idea of using a regular TV as the electronic equivalent of a chalkboard (blackboard) or whiteboard has been explored through the 1980s thanks to a few key drivers.

A use case that was being put forward was to work with the then-new hobby of home videography thanks to the arrival of affordable video cameras and portable video recorders. Here it would be about creating title cards for one’s home video projects. As well, third-party peripheral vendors created light-pen setups that work with various home-computer platforms like the Commodore “VIC” computers (VIC-20 and Commodore 64), the Tandy TRS-80 Model 1 and the BBC Micro. The software that came with these setups included an elementary “paint” program that worked with the light-pen and allowed the (low-resolution) drawings to be saved to the computer’s secondary-storage medium (cassette or floppy disk) or printed to a connected printer.

The mouse, along with various graphics programs for later computer platform, extended the concept further even though newer computers were hooked up to displays better than the average TV set.

But the concept has been revived using the CastPad app for Android. This app allows you to draw using your finger or stylus on your Android smartphone or tablet, then “cast” it to your TV or monitor that is connected to a Chromecast or has full Chromecast ability built in. There is also the ability to “cast” to other Android devices running the same software and connected to the same logical network that the Chromecast is connected to.

You can save what you drew to your Android device but I am not sure whether it supports printing via Android’s print functionality. There is a free ad-supported version that is limited to five colours. It may be good enough to show to a child or use for games like Pictionary. But a premium version, which you can purchase through an in-app arrangement allows for infinite colours and a few more features.

A use case that was called out in the article was to improve a family Pictionary game that the article’s author played during their family’s Thanksgiving celebrations. Here, they had a Chromecast connected to their family home’s TV and used their Android smartphone to draw out the word ideas as part of gameplay.

But the app has other use cases such as conference facilities, classrooms and the like that are kitted out with a large-screen TV or video projector. Here, the CastPad app may work as a better approach to illustrating concepts in a basic manner and showing them to a larger audience as part of your presentation effort.

Apple could easily answer this app with something that runs on an iPhone or iPad and uses AirPlay to stream the canvas to an Apple TV. Or the app developers could simply port it to iOS to take advantage of that platform’s user base.

Similarly, there could be the ability to have you draw the graphic on the smartphone or tablet then project it through the Chromecast, which can be useful if you are preparing that diagram for a class. This can also be augmented with the ability to insert printed text in a range of font sizes, something that would appeal to “blackboard diagrammers”.

Apps like CastPad can exploit “screencasting” setups like AirPlay or Chromecast to turn the largest screen in the house or business in to an electronic whiteboard and the touchscreen of your device in to a “canvas”.

Should the Android platform be exclusively dependent on the Google Play app store for software?

USB-C connector on Samsung Galaxy S8 Plus smartphone

A question that is appearing for Android users is whether software developers can sell software independently of Google Play

Over the last few months, Epic Games released their Android port of Fortnite in a manner that is very unusual for a mobile-platform app. Here, they released this port of the hit game as an APK software package file that is downloaded from their Website and installed on the user’s Android device as if you are installing a program on a regular Windows or MacOS computer. This allows them to maintain control over the sale of game additions and similar merchandise without having to pay Google a cut of their turnover. Or it could allow them to maintain control over the software’s availability such as issue beta or pre-release versions of software or simply offer high-demanding software like action games to devices known to perform at their best with the software.

The Android platform has a default setting of disallowing software installations unless they come from the Google Play Store or the device manufacturer’s app store. This is a software-security setting to prevent the installation of software that has questionable intent on your Android device. But the “regular” computer platforms have implemented other approaches to allow secure installation of software thanks to their heritage of being able to install software delivered on package media or from download resources like the software developer’s Website or a download site. It also caters towards the role that regular computers play in the course of business computing where line-of-business software is being installed on these systems by value-added resellers and solutions providers.

This question will become more real as the Android platform is taken beyond mobile devices and towards the smart TV like with NVIDIA Shield or recent Sony smart TVs. It could also appeal towards other “smart devices” like network printers that are based on the Android software codebase where there is a desire to add functionality through an app store.

Recent efforts that Microsoft, Apple and the open-source community have taken to protect our regular computers against include software-authenticity certification, least-privilege execution, sandboxing and integrated malware detection. In some cases, there is the ability for users to remove software-authenticity certificates from their regular computer in case questionable software was deployed as highlighted with the Lenovo Superfish incident.

Similarly, these operating system vendors and many third parties have developed endpoint-security software to protect these computers against malware and other security threats.

Google even introduced the Google Play Protect software to the Android platform to offer the same kind of “installed malware” detection that Windows Defender offers for the Windows platform and Xprotect offers on the MacOS platform. Samsung even implements Knox as an endpoint-protection program on their Android devices.

Android does maintain its own app store in the form of the Google Play Store but allows device manufacturers and, in some cases, mobile-phone service providers to create their own app store, payment infrastructure and similar arrangements. But it is difficult for a third-party software developer to supply apps independent of these app stores including creating their own app store. This is more so for app developers who want to sell their software or engage in further commerce like selling in-game microcurrency without having to pay Google or others a cut of the proceeds for the privilege of using that storefront.

Android users can install apps from other sources but they have to go in to their phone’s settings and enable the “install unknown apps” or a similar option for them to install apps from sources other than the Google Play Store or their OEM’s / carrier’s app store.

What could be done for the Android platform could be to support authenticated software deployment that uses the same techniques as Microsoft and Apple with their desktop and server operating systems. It can also be augmented with the creation of authenticated app-stores to allow software developers, mobile carriers, business solutions providers and the like to implement their own app stores on the Android platform. The authentication platform would also require the ability for end-users to remove trusted-developer certificates or for certificate authorities to revoke these certificates.

It could allow for someone like, for example, Valve or GOG to operate a “Steam-like” storefront which is focused towards gaming. Or an app developer like Microsoft could use their own storefront to sell their own software like the Office desktop-productivity suite. Then there are people courting the business segment who want to offer a hand-curated collection of business-focused apps including line-of-business software.

But there would have to be some industry-level oversight regarding certified apps and app stores to make it hard for questionable software to be delivered to the Android ecosystem, This also would include app stores having to make sure that their payment mechanisms aren’t a breeding ground for fraud in its various forms.

There will be the common question that will crop up regarding alternative app stores and developer-controlled or third-party-controlled app-level certification is the ability to purvey apps that have socially-questionable purposes like gambling or pornography. Here, the Android ecosystem will have to have the ability to allow end-users to regulate the provenance of the software installed on these devices.

At least the Fortnite software-distribution conversation is raising questions about how software is delivered to the Android mobile-computing platform and whether this platform is really open-frame.

Bluetooth Fast Pairing–to be part of the Android platform

Articles

Android main interactive lock screen

Most recent Android smartphones may be able to support one-touch pair-up for Bluetooth accessories

Android ‘Fast Pair’ will quickly connect Bluetooth devices | Engadget

Announcing Fast Pair – effortless Bluetooth pairing for Android | Android Developers Blog

My Comments

Google has answered the setup method that Apple has implemented for their AirPod wireless in-ear headset by implementing a software-driven “quick-pair” setup that will be part of Android.

This method, called Bluetooth Fast Pairing, works on Android handsets and other devices that run Android 6.0 Marshmallow onwards and have Google Play Services 11.7 or newer installed and support Bluetooth 4.0 Low Energy (Bluetooth Smart) connectivity. You will have to enable Bluetooth and Location functionality in your handset, but you don’t have to look at Bluetooth device lists on your smartphone for a particular device identifier to complete the setup process.

Google Fast Pair in action - press image courtesy of Google

Click or tap this image to see Google Fast Pairing in action

It is meant to provide quick discovery of your compliant Bluetooth accessory device in order to expedite the setup process that is involved with new devices or to “repair” Bluetooth connections that have failed. This latter situation can easily occur if data in the device regarding associated Bluetooth devices becomes corrupted or their is excessive Bluetooth interference.

The user experience will require you to put your accessory device like a Bluetooth headset, speakers or car stereo in to Bluetooth-setup mode. This may simply be through you holding down the “setup” or “pair” button till a LED flashes a certain way or you hear a distinct tone. On the other hand in the case of home and car audio equipment that has a display of some form, you using the “Setup Menu” to select “Bluetooth Setup” or something similar.

Then you receive a notification message on your Android device which refers to the device you just enabled for pairing, showing its product name and a thumbnail image of the device. Tap on this notification to continue the setup process and you may receive an invitation to download a companion app for those devices that work on the “app-cessory” model for extended functionality.

Google implements this by using Bluetooth Low Energy “beacon” technology to enable the device-discovery process. This is similar to the various beacon approaches for marketing and indoor navigation that are being facilitated by Bluetooth Low Energy, but they only appear while your accessory device is in “Bluetooth setup” mode.

The Google Play servers provide information about the device such as its thumbnail image, product name or link to a companion app based on a “primary-key” identifier that is part of the Bluetooth Low Energy “beacon” presented by the device. Then, once you tap the notification popup on your Android device, the pairing and establishment process takes place under Bluetooth Classic technology.

I see this also as being similar to the various “Plug And Play” discovery process implemented in Microsoft Windows and Apple MacOS whenever you connect newer peripherals to your computer. This is where Microsoft and Apple keep data about various peripherals and expansion cards that are or have been on the market to facilitate installation of any necessary drivers or other software or invocation of class drivers that are part of the operating system. For Google and the Android platform, they could take this further with USB-C and USB Micro-AB OTG connectivity to implement the same kind of “plug and play” setup for peripherals connected this way to Android devices.

This system could be taken further by integrating similar logic and server-hosted databases in to other operating systems for regular and mobile computer platforms to improve and expedite the setup process for Bluetooth devices where the host device supports Bluetooth Low Energy operation. Here, I would like to see it based on the same identifiers broadcast by each of the accessory devices.

The Bluetooth Fast Pairing ability that Google gave to the Android platform complements NFC-based “touch and go” pairing that has been used with that platform as another method to simplify the setup process. This is more for manufacturers who don’t have enough room in their accessory device’s design to provide an NFC area for “touch-and-go” setup thanks to very small devices or where NFC doesn’t play well with the device’s aesthetics or functionality.

It may be a point of confusion for device designers like Alpine with their car stereos who place their devices in “discoverable” or “pairing” mode all the time so you can commence enrolling your accessory device at your phone’s user interface. Here, the device manufacturer may have to limit its availability to certain circumstances like no devices paired or connected, or you having to select the “Bluetooth” source or “Setup” mode to invoke discoverability.

At least Google have put up a way to allow quicker setup for Bluetooth accessories with their Android platform devices without the need to build the requirement in to the hardware.