Verse navigator not working
The verse selector buttons have not worked since I downloaded the new release. Error message "Navigation Failed"
Comments
-
David Pugh said:
The verse selector buttons have not worked since I downloaded the new release. Error message "Navigation Failed"
David,
If you are running Android 2.1 this is a known issue and should be fixed in the next release. Thanks!
0 -
Thanks for the quick reply and update. I'll look forward to the release![:)]
0 -
I'm having the same problem and I see that it was not fixed in the 1.1 Beta 1 release. Any estimated time on the fix?
0 -
Kyle Baker said:
I'm having the same problem and I see that it was not fixed in the 1.1 Beta 1 release. Any estimated time on the fix?
This is working for me on Android 2.1 - both online/offline - using 1.1 Beta 1. Can you give more more specifics about your device, what version of Android, etc? Thanks.
0 -
Nook Simple Touch with Android 2.1. The last official version that worked for me was 0.94. Since I updated to 1.0.3 and it was broken, and also the 1.1 beta 1 broken, I found through trial and error that I could download Logos-32.apk and it works. No idea what version build 32 corresponds to.
The "Navigation Failed" message comes up immediately whether online or offline.
0 -
Kevin Byford said:Kyle Baker said:
I'm having the same problem and I see that it was not fixed in the 1.1 Beta 1 release. Any estimated time on the fix?
This is working for me on Android 2.1 - both online/offline - using 1.1 Beta 1. Can you give more more specifics about your device, what version of Android, etc? Thanks.
I need to make a correction - this ISN'T working for me on Android 2.1 - I apologize for the error I've made! I'm chatting with a developer now about this issue and he said it should be fixed in Logos 1.1.2.
On a side note, the market share for Android 2.1 has shrunk in half during the last six months, and is down to around 5% of the user base. Eventually we will drop support for Android 2.1 devices because the time spent making sure everything works properly on old Android versions vs. the number of customers using them just won't be practical. I'm not sure when that decision will be made but I felt it should be mentioned.
0 -
Kevin Byford said:Kevin Byford said:Kyle Baker said:
I'm having the same problem and I see that it was not fixed in the 1.1 Beta 1 release. Any estimated time on the fix?
This is working for me on Android 2.1 - both online/offline - using 1.1 Beta 1. Can you give more more specifics about your device, what version of Android, etc? Thanks.
I need to make a correction - this ISN'T working for me on Android 2.1 - I apologize for the error I've made! I'm chatting with a developer now about this issue and he said it should be fixed in Logos 1.1.2.
On a side note, the market share for Android 2.1 has shrunk in half during the last six months, and is down to around 5% of the user base. Eventually we will drop support for Android 2.1 devices because the time spent making sure everything works properly on old Android versions vs. the number of customers using them just won't be practical. I'm not sure when that decision will be made but I felt it should be mentioned.
Kindle Fire is on a customized version of Android 2.3 -Gingerbread. I am not sure of the sub-version. Here are the percentage of users using each sub-version of the android market:
http://developer.android.com/resources/dashboard/platform-versions.html
Its true that 2.1 - Eclair - only uses 5.2%. Version 2.3 Gingerbread for all subversions uses 65% in contrast. Thus, it appears we Kindle Fire users are safe so far for Logos support
0 -
Logos-32.apk was never intended for even beta users to use. It should no longer be available and I'd ask that you not continue to use this version. Logos-29.apk is version 0.9.4.
The next beta/stable release (1.1.2) should fix the issues you are experiencing on 2.1.
0 -
No problem. I just found Logos-32.apk accidentally while trying to get back to 0.9.4. I'm using 1.1.1 again and working around it the issue. Interestingly, "Jump to reference" works even when the verse navigator does not.
0 -
I really appreciate the work you have done to make Logos' app run on Android 2.1. I'm one of the few running Logos for Android on a rooted Nook Touch. The navigation works great again in Beta version 1.1.2 and now the "Favorites" too.
Thanks very much.
0 -
Thank you! I understand the marketing decisions, but I hope you will continue to support 2.1 as long as possible. Having Logos on an e-ink screen is just too good.
0 -
Kevin Byford said:Kevin Byford said:Kyle Baker said:
I'm having the same problem and I see that it was not fixed in the 1.1 Beta 1 release. Any estimated time on the fix?
This is working for me on Android 2.1 - both online/offline - using 1.1 Beta 1. Can you give more more specifics about your device, what version of Android, etc? Thanks.
I need to make a correction - this ISN'T working for me on Android 2.1 - I apologize for the error I've made! I'm chatting with a developer now about this issue and he said it should be fixed in Logos 1.1.2.
Hi Kevin
I was at a meeting yesterday without network access and tried to use the verse navigator in NASB95 (using Logos 2.2.3) and received a navigation failed message when using the verse selection menu.
Other downloaded Bibles (such as ESV) worked fine.
I was able to reproduce this this morning just by putting my Android phone into Airplane mode
Graham
0 -
Graham Criddle said:
Hi Kevin
I was at a meeting yesterday without network access and tried to use the verse navigator in NASB95 (using Logos 2.2.3) and received a navigation failed message when using the verse selection menu.
Other downloaded Bibles (such as ESV) worked fine.
I was able to reproduce this this morning just by putting my Android phone into Airplane mode
Graham
Hi Graham,
I am unable to reproduce this issue with 2.2.4 which we should be releasing today. If after updating to 2.2.4 you still see the issue please let us know. Thanks!
0 -
Hi Kevin
Kevin Byford said:Hi Graham,
I am unable to reproduce this issue with 2.2.4 which we should be releasing today. If after updating to 2.2.4 you still see the issue please let us know. Thanks!
Thanks for this.
I have just downloaded the 2.2.4 beta and no longer see this problem.
Thanks, Graham
0 -
Graham Criddle said:
I have just downloaded the 2.2.4 beta and no longer see this problem.
Thanks for the update Graham.
0 -
0
