Update, May 3rd: it appears Lumiya may have been caught by recent changes to changing Google Play policies and Google’s updated developer terms (which apparently require the agreement of all app developers).
The changes to the Google Play policies actually caused some companies – such as HTC – to temporarily remove their apps from Google Play until they could issue updates in compliance with the new policies, with HTC commenting:
In order to comply with the latest Google Play policy, we have temporarily removed a number of HTC applications from the Google Play Store. Applications will be republished over the coming weeks as we deploy new updates.
Sources have suggested that, subject to compliance with the the new policies, smaller developers have either removed their apps or may have had their apps suspended by Google Play pending their formal agreement to the new policies.
I’ve not heard back from Alina on the subject, but Lumiya Support Manager, Kaleaon, indicated that the above may well be reason for Lumiya’s (hopefully temporary) disappearance from Google Play, saying:
I know Alina’s been busy, so she may not yet have had the time to provide her approval.
I’ll provide further updates should I obtain more news.
I was going to hold-off blogging on this until I’d heard back from Alina Lyvette, but as there is already some discussion on the matter, as well as some blog posts, I thought I’d add some notes.
Lumiya is currently unavailable from the Google Play website.
With the recent confirmation that Linden Lab is working on an iOS solution for accessing Second Life, there has been renewed interest in what is available – and it struck me that since my initial reviews of mobile clients such as Mobile Grid Client (2011) – and with the exception of Lumiya – I’ve not really updated on those clients that are available.
This being the case, here’s a quick round-up of those mobile (Android and iOS) solutions recorded on the Third Party Viewer Directory. These are not intended to be comprehensive reviews, but will hopefully provide a general overview of the products and their capabilities / status.
Mobile Grid Client is the longest running of the Android clients listed on the TPV Directory. A text-only application, it provides a range of options, including OpenSim support – but these are subject to the subscription package taken, one of which must be selected after an initial 14-day trial period.
The available subscription options are:
“Standard” version: L$250 per month, with a selection of features disabled (e.g. giving inventory to others, creating / copying notecards, changing your active group, paying avatars, OpenSim support).
“Pro” version L$450 per month / L$4500 per years, with access to all available features.
In 2011, this was a reasonable application, given what was available at the time. Today, however, and even allowing for the subscription payments being non-recurring (so opting out is easy at the end of a subscription period), when compared to Lumiya (below), Mobile Grid Client is notably over-priced, even at the “Standard” subscription model.
First released in 2012, Lumiya was, up until the start of 2017, routinely updated to keep pace with the latest viewer releases from Linden Lab as well as to provide bug fixing issues with various android platforms.
This application has such a well-rounded suite of capabilities, including plug-ins for voice and improved rendering (both available for free), that it pretty much matches the “full” viewer in features and functions, up to and including Bento support (January, 2017). It even has VR (Cardboard) support!
Initially text-only when first introduced, Lumiya quickly progressed to basic graphical rendering prior to maturing into a very capable graphical client with continued improvements to the graphical UI to allow for better, easier and more comprehensive in-world interactions. For those who use it, Lumiya also respects RLV / RLVa
Lumiya is the Rolls Royce of mobile Second Life / OpenSim clients, although development work seems to have frozen. There have been recent issues for some with the use of voice in recent months.
Even for occasional text use, inventory management, etc., this is the go-to Android client, while the 3D world rendering adds a whole now level to mobile SL / OpenSim use. True, the graphics are not as crisp and fresh as the “full” viewer, but considering everything Lumiya is packing into a hand-held device and it has not been developed within major financial input and technical support, it is not to be dismissed on that basis.
Very much the standard-bearer for what can be developed by way of mobile SL / OpenSim applications using Android.
Appearing around the same time as Lumiya, LittleSight provides basic text chat and IM capabilities to users – albeit with ads displayed periodically. Additional capabilities, such as teleporting, and the removal of the ads can be had on payment of a small fee.
The most limited of the three Android clients, and one with reported issues for users trying to log-in with the latest version. While I encountered no problems myself with logged-in on re-installing LittleSight on my tablet device, I did find the map failed to render, but that seemed to be the only issue.
Given the need for payment, and the sheer volume of capabilities presented in Lumiya, unless the latter expressly will on work on a particular device, it is hard to see why anyone would opt to use LittleSight. You may not need all the tools available in Lumiya, but having them available just in case is not necessarily a bad thing.
On Friday, January 20th Lumiya, the Android client developed by Alina Lyvette gained the latest in what has been a flurry of updates for the client, with the release of version 3.4. This sees Lumiya gain support for the Project Bento skeleton extensions and rendering of associated avatar meshes and accessories.
All of the Bento updates are under-the-hood; there are no UI changes, and no Reset Skeleton options as seen in Bento-supporting viewers. As Alina explained to me in discussing the release, Lumiya’s approach to rendering should generally result in Bento avatars and accessories rendering correctly in the 3D world view.
For the vast majority of times, this is indeed the case. You can select and wear a Bento avatar or Bento accessory such as a head and wear / unwear it without any problems.
However, as was noted during Bento’s development, when swapping between quadruped avatars, which can involve severe deformation of the avatar skeleton, and bipedal avatars, there can be times when your avatar doesn’t always resume its proper shape in the 3D world view, resulting in the avatar appearing deformed in your view (see below, right.
These occurrences tend to be very intermittent / rare. As with their occurrence in a viewer, they might be the result of race conditions and / or missed appearance messages.
As Lumiya does not have any Reset Skeleton options, the problem can be fixed in one of two ways:
Tapping the actions menu icon (top right of the screen) and selecting Stop Avatar Animations. This will generate an appearance update, and should correct the problem
Exiting the 3D world view, and then enabling it again. This will again force an appearance update, and correct any deformation.
Note that in testing, these kinds of deformation issues didn’t extend to other avatars changing their form within viewing range of Lumiya 3.4, and they always rendered correctly following a change. However, should other avatars appear deformed in your 3D world view, try exiting and re-started the 3D view and see if they then render correctly.
Outside of this, Bento HUDs, where supplied can be added and used in the usual manner with Lumiya – attach the HUD, then select it via the on-screen HUD button.
As well as the Bento update, Lumiya 3.4 includes a couple of bug fixes:
Avatars should no longer get stuck in the non-animated pose (“T” pose).
Avatars should no longer flash when loading rigged mesh attachments.
Given the nature of things, the code may yet require further nips and tucks, but on the whole, and outside of the rare deformation issue mentioned above, I didn’t encounter significant issues – although my selection of Bento items is admittedly narrow, and my testing could not in any way be comprehensive. All told, another great update to SL’s most cost-effective and feature-rich mobile client / option.
On Friday, January 13th, Alina Lyvette released version 3.3.1 of the Lumiya Android client for Second Life and OpenSim.
The release builds on the 3.3 update, which added Voice capabilities to Lumiya, by providing additional audio controls for Voice together with Bluetooth headset support, which are combined in a single easy-to-use UI addition. As well as this, the release includes a number of bugfixes.
The audio controls can be displayed any time that Voice is enabled and about to be used – see my Lumiya 3.3 review for details on how to enable Voice in Lumiya.
With voice enabled, tap on the telephone handset icon as you would to launch a Voice conversation. When the microphone bar is display on your screen either in local chat or as a result of someone accepting your Voice IM request, tap anywhere on the bar except the microphone icon or the X, and the audio controls will be displayed.
These comprise three elements:
And overall volume slider
A toggle button to activate your device’s external speaker
A toggle button to direct audio through your Bluetooth headset.
Note that for Bluetooth connectivity to work, you will also need to update to the latest Lumiya Voice plug-in app and, obviously,have a Bluetooth headset pair with the device being used to run Lumiya. Once paired and the headset is active, Lumiya will automatically route incoming audio to the headset when you establish a voice call. Should you wish to place the incoming audio on your device’s speaker (and back), use the buttons on the Lumiya audio controls, described above.
Bug Fixes and Minor Improvements
The bug fixes and smaller improvements with this release comprise:
A fix for some texture uploads to fail.
A fix to prevent camera position being reset when exiting 3D view.
Region restart messages and other alerts will now display correctly.
Objects will be automatically rezzed under land group when possible.
Adding Bluetooth support is an obvious step now Lumiya supports Voice, and while I was unable to test it myself (the only Bluetooth earpiece I have is a good decade old and has lain in a drawer for most of that time, and so unsurprisingly didn’t work when allowed to see light of day), the process appears simple enough.
A number of people have asked me about Lumiya and Bento. As I noted in my last Lumiya review, Alina is working on it, and probably the fairest time frame to put on it is that it will be released when it is ready 🙂 .
On Sunday, December 18th, Alina Lyvette released Lumiya 3.3, the Second Life / OpenSim Android client for smartphones and tablets.
The new update brings with it Voice chat via the built-in microphone on your device (or suitable Bluetooth unit connected to your device), the ability to upload images via your device, and additional VR support, including Google Daydream. The realise notes are available here.
Voice chat for Lumiya 3.3 requires the download and installation of the free Voice plug-in app. Once you’ve downloaded and installed the plugin, the first step is to enable Voice:
Log-in via Lumiya.
Tap the menu icon (top left of the screen) and then tap Settings > Chat and Messages
Tap Enable Voice Chat and make sure it is checked as enabled. To disable, tap the option again.
With Voice chat enabled you can use voice for open chat, IM calls and via the 3D World view.
To initiate Voice chat in open chat, tap on Local Chat in Lumiya. then tap the telephone handset icon in the top right of the screen. This will enable your device’s microphone and display the open / close microphone bar. Tap the microphone icon to activate your microphone; the icon will turn green, indicating the microphone on your device is hot, and the bar will display the instruction to Speak Now.
Remember to tap the bar again when you’ve finished speaking to prevent any extraneous noises around you from being picked-up and transmitted in-world. To close the current Voice chat session at any time, tap the X on the right of the chat bar (arrowed to the right, above).
IM Voice Calls
For an IM voice call, tap the name of the person you wish to IM (e.g. via the list of people nearby or your Friends list). When the IM window has opened, tap the telephone handset icon (top right.The microphone bar is displayed, with the message “Connecting…”. The person you are calling, assuming they are on a full viewer, will receive the usual Voice call message (shown inset, below).
If they accept the call, the microphone icon on the left of the bar will turn green, indicating they’ve accepted the call, and your microphone is now hot. Remember to tap the bar when you’ve finished speaking to prevent any extraneous noises around you from being picked-up and transmitted in-world.
If they reject the call, or opt to converse in IM via text, the microphone bar will vanish.
If they do not answer the call before the Voice connection times out, the microphone bar will vanish.
To end the call, tap the X on the right of the microphone bar.
Note that you can restart the conversation from the IM window by tapping the Action menu icon (three vertical dots, top right of the screen) and selecting Voice Chat from the drop-down. This will initiate a fresh call.
Should you be in receipt of an IM Voice call when using Lumiya, a drop-down will appear at the top of the window you are using, and you can opt to accept or reject the call. If you reject the call, but wish to converse via IM text and are not in the IM chat window, you’ll have to manually switch to the IM window for the person who called you.
If you accept the call, the microphone bar will be displayed, and your microphone will be hot. Remember to tap the bar when you’ve finished speaking to prevent any extraneous noises around you from being picked-up and transmitted in-world.
Thanks to an article by Beq Janus and news passed to me by Whirly Fizzle, this blog was recently able to cover the issues of Voice installation failures in the Radegast lightweight client, and the work put into rectifying the problems.
In short, it was discovered that Radegast would no longer install the SL Voice package due to the location the installer was pointing to being a) not provided by Linden Lab; b) no longer valid. Shortly after this was discovered, Beq found a temporary workaround to get things going using the Radegast version of the SL Voice package, and Whirly found a means to manually get Radegast to work with the current SL Voice package from Linden Lab.
In response to a plea from Beq for developers to consider helping to provide a more robust solution, Cinder Roxley stepped in, and in short order had Radegast’s installer updated to work with the current SL Voice package.
Cinder has now confirmed she hopes to continue maintaining working on Radegast.
“It would just be a shame to see Radegast become obsolete considering how useful it is, especially in terms of accessibility.” she told me, after I heard confirmation she’d be continuing the work. “Right now, Voice is updated, and Bento is now in. I still need to do AIS v3 [inventory handling].”
Given that the current website for Radegast can no longer be accessed for updates, Cinder is working on a new site as well, although as she notes, bringing everything together will take time and energy.
“I already have a full plate with work and life and Alchemy,” she said, “So anyone else who wants to help out is more than welcome to.”
There’s no immediate time line for a further Radegast update, but knowing the work is continuing is likely to come as good news to a lot of people – and if other developers are interested in helping out, please contact Cinder in-world.
In the meantime, thanks to Cinder for taking up the challenge.