Android Suite 2.4.1 Beta Release

The Android team is pleased to announce 2.3.13 and 2.4.1 betas of the Bible, Biblia, FSB, Verbum and Vyrso apps.

The Android Reader Suite version 2.4.1 requires Android 2.3 or newer. We will continue to ship 2.3.x app updates to both the beta and stable download channels as well as the Google Play store as necessary to fix critical issues and allow for continued resource availability on Android 2.2 devices.

If you installed the app via the download link you can upgrade to the latest beta by clicking on the download link listed below, download the appropriate apk for your device and upgrading your existing app. If you want to receive an automatic notification when a new beta is available click on the gear icon, selecting the “about” option then change the Update Channel option from “stable” to “beta” (no quotes). Note: This Update Channel option only appears on the About page if you installed the app via our download link.

If you discover any issues please create a new post and include the following info:
  Description – How were you using the app when the problem occurred.
  App Info – Which app you are using. (Bible, Biblia, Faithlife Study Bible, Vyrso)
  Device Info – (Nexus 7, Motorola Triumph, Droid Bionic, Kindle Fire (1st gen))
  Android Version – (2.2, 2.3, 3.x, 4.0, 4.1, 4.2)

Download

Bible 2.3.13 (Build 81) & 2.4.1 (Build 100)
- Beta download – http://downloads.logos.com/Android/Logos/beta/index.html
Biblia 2.3.13 (Build 54) & Biblia 2.4.1 (Build 72)
- Beta download – http://downloads.logos.com/Android/Biblia/beta/index.html
Faithlife Study Bible 2.3.13 (Build 54) & 2.4.1 (Build 74)
- Beta download – http://downloads.logos.com/Android/Faithlife/beta/index.html
Verbum 2.3.13 (Build 18) & 2.4.1 (Build 36)
- Beta download – http://downloads.logos.com/Android/Verbum/beta/index.html
Vyrso 2.3.13 (Build 71) & 2.4.1 (Build 89)
- Beta download – http://downloads.logos.com/Android/Vyrso/beta/index.html

New (2.4.1)

Requires Android 2.3 or later
Support for creating new note documents
Visual Cue indicator appears post navigation
Rich Text Editor Toolbar support
- Bold / Italics / Underline
- Justification / Indenting
- Bulleted / Numbered lists
- Font face / size
- Link support
- Ability to clear all formatting

New (2.3.13)

Checks for new Android 2.2 available updates
Can only be installed on Android 2.2 devices

Fixed (2.3.13 and 2.4.1)

Last reading position not stored while reading offline
Other miscellaneous improvements

Find more posts tagged with

Comments

Mark Barnes

I don't suppose there's any chance of continuing some level of support for Android 2.1, is there? Those of us using rooted e-ink devices are stuck at that level, and we're obviously very keen to get the Logos app on those devices.

Gabe Martin

https://community.logos.com/discussion/comment/485124#Comment_485124

Mark,

I know that there are/were several e-ink device users out there that were able to get our older 1.x version of the apps to run on their devices. I was fascinated by that because even when we did support Android 2.1 we didn't officially support eInk displays. One of our Android support criteria is that it's running an OEM version of Android that's installed through one of the supported stores (Google Play or Amazon). As cool as I think it is that our app could run on e-ink displays running Android 2.1, attempting to support that configuration would simply prove to costly in terms of costs/benefits to our users. Devoting time to that configuration would take away from progress being made on implementing new features or improving existing features for a much larger (and growing) pool of users.

That's one of the reasons we are beginning to phase out Android 2.2. The number of combined Android 2.2 users across our entire suite of apps has decreased significantly and the development cost related to continued support for Android 2.2 - API 8 grows each time newer Android versions are released. We are currently supporting 9 different API levels (or Android OS versions) running on three types of device configurations - phones, readers (7" tablets), and tablets.

Mark Barnes

https://community.logos.com/discussion/comment/485221#Comment_485221

I know that there are/were several e-ink device users out there that were able to get our older 1.x version of the apps to run on their devices.

Yes, it is possible if you can find the .apk file - but as you know, newly compiled resources aren't compatible. It was just that compatibility I was hoping for.

We are currently supporting 9 different API levels (or Android OS versions) running on three types of device configurations - phones, readers (7" tablets), and tablets.

Ouch. I do wish someone would develop an e-ink reader that ran a vaguely up-to-date version of Android.

JoshInRI

Why are the (in my opinion) somewhat basic sections (like passage guide or searches) buried in the App?

I wish the interface made it appear like the app was more than just a reader please.

I want to be able to access and search quickly during a group Bible Study for example.

The way it exists right now, myGroup has moved on to another passage by the time I actually get to locate and use the resources for what we are studying.

Change the interface so its got some functionality right off the main menu if you please.

JoshInRI

Does the update fix the hightlighting issue that exists between Windows version and Android on a Nexus 7 please?

I had to unistall the application and reinstall it to get my highlighting between devices to update properly.

Thanks for all you do.

joshua

Randy W. Sims

https://community.logos.com/discussion/comment/485242#Comment_485242

Ouch. I do wish someone would develop an e-ink reader that ran a vaguely up-to-date version of Android.

[Y] [Y]

Randy W. Sims

https://community.logos.com/discussion/comment/485244#Comment_485244

I wish the interface made it appear like the app was more than just a reader please...

There are many great features along these lines that you can vote for on the Mobile UserVoice page. If you don't see anything you like, then you can create new suggestions. Try to describe the features you want in as much detail as possible so it is easy for others to understand. Maybe provide example usage scenarios of how you envision the features working.