Change log;
- Added support for Ino Reader
- Improved loading speed for Feedly cloud
- Other fixes
Thursday, August 22, 2013
D7 Reader 2.2.8
The new version includes support for "Ino Reader" as the 3rd reader service with other improvements. It has been published to the Google Play and as usual it will take sometime to appear in your individual devices.
Change log;
Change log;
Subscribe to:
Post Comments (Atom)
I am now using D7Reader pro together with InoReader. However new unread articles do only show in D7Reader pro if I first open InoReader in my Webbrowser and refresh the subscriptions. Is it possible to override this problem?
ReplyDeleteI am using D7 Reader pro 2.2.8 with InoReader.
ReplyDeleteThere are two issues.
(1) When I select (tap) a tag (folder) on the Subscriptions view, feed items sometimes fail to load. (A circling icon shows up and never disappears.)
(2) Tapping the big check mark on the article list sometimes fails to mark all items as read. (This leaves the unread counts on the Subscriptions view unchanged.)
I'd appreciate if you could fix these problems.
TIA.
I got an error with D7 reader pro. There is the traces.txt
ReplyDelete----- pid 22179 at 2013-10-24 10:17:59 -----
Cmd line: com.droidlab7.reader.pro
DALVIK THREADS:
"main" prio=5 tid=3 NATIVE
| group="main" sCount=1 dsCount=0 s=Y obj=0x4001b250 self=0xbcf0
| sysTid=22179 nice=0 sched=0/0 cgrp=unknown handle=-1343993184
at android.os.BinderProxy.transact(Native Method)
at android.app.ActivityManagerProxy.handleApplicationError(ActivityManagerNative.java:2358)
at com.android.internal.os.RuntimeInit.crash(RuntimeInit.java:339)
at com.android.internal.os.RuntimeInit$UncaughtHandler.uncaughtException(RuntimeInit.java:76)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:887)
at java.lang.ThreadGroup.uncaughtException(ThreadGroup.java:884)
at dalvik.system.NativeStart.main(Native Method)
"background thread" prio=5 tid=13 WAIT
| group="main" sCount=1 dsCount=0 s=N obj=0x4673ef20 self=0x14c078
| sysTid=22185 nice=0 sched=0/0 cgrp=unknown handle=1493688
at java.lang.Object.wait(Native Method)
- waiting on <0x170500> (a android.os.MessageQueue)
at java.lang.Object.wait(Object.java:288)
at android.os.MessageQueue.next(MessageQueue.java:148)
at android.os.Looper.loop(Looper.java:110)
at android.os.HandlerThread.run(HandlerThread.java:60)
"Binder Thread #2" prio=5 tid=11 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x46770a68 self=0x86360
| sysTid=22184 nice=0 sched=0/0 cgrp=unknown handle=548840
at dalvik.system.NativeStart.run(Native Method)
"Binder Thread #1" prio=5 tid=9 NATIVE
| group="main" sCount=1 dsCount=0 s=N obj=0x467708f8 self=0x852f8
| sysTid=22183 nice=0 sched=0/0 cgrp=unknown handle=908392
at dalvik.system.NativeStart.run(Native Method)
"Signal Catcher" daemon prio=5 tid=7 RUNNABLE
| group="system" sCount=0 dsCount=0 s=N obj=0x467381e8 self=0xefbe8
| sysTid=22182 nice=0 sched=0/0 cgrp=unknown handle=1148488
at dalvik.system.NativeStart.run(Native Method)
"HeapWorker" daemon prio=5 tid=5 VMWAIT
| group="system" sCount=1 dsCount=0 s=N obj=0x44291f10 self=0xa6710
| sysTid=22181 nice=0 sched=0/0 cgrp=unknown handle=752552
at dalvik.system.NativeStart.run(Native Method)
----- end 22179 -----
Here are some extra background information. I used D7 on my B&N Nook Simple Touch which is running Android 2.1
DeleteCiao,
ReplyDeletefor me is impposible to mobilize article with Instapaper, return always error 400, help!
thank's in advance
What is the fastest RSS cloud?
ReplyDeleteIt's not working with inoreader for at least 45 days
ReplyDeleteBefor it was perfect
No more update? Two year without update!
ReplyDelete