PDFViewer3.15.3_Android Studio issue

this may caused by scroller value not updated.
i think it can be fixed by adding code:

m_scroller.computeScrollOffset();

at last line of PDFLayout.vSetPos()
so PDFLayout.vSetPos() shall be:
public void vSetPos(int vx, int vy, PDFPos pos) {
if (pos == null) return;
VPage vpage = m_pages[pos.pageno];
vSetX(vpage.GetVX(pos.x) - vx);
vSetY(vpage.GetVY(pos.y) - vy);
m_scroller.computeScrollOffset();
}



this code not confirmed. but i think it may helps.

Hi guys,
I'm using Android Radaee lib for almost 4 years and I've never see this happening until now. It seems that this strange behaviour occurs only on some Samsung Android 10. Unfourtunally I don´t have any device here to reproduce this bug. The lib I'm using is already using this m_scroller.computeScrollOffset(); at the end of SetPos method.

Is there anything I could do? I tried everything here at my devices and I couldn´t reproduce it.

Tks,
Thiago

The only way to fix the problem is restarting the device. Even closing the app doesn't fix the problem. I added the code above but didn't work so I think they will never fix it. It happens only in some devices and only after using the lib many times. Then the bug appears and only gets fixed restarting the device. Nothing else helps... so seems related to a c++ lib bug.

I think they can't reproduce it because it needs some time to appear. At first time it works without problem and happens "randomly". Then it happens while you press the screen while it is scrolling, it moves the view to the first page. If it isn't scrolling it doesn't happen.

Hope it helps...

dear user, are you able to upload a short video to explain the issue?
you opened this old topic and I shall ask you to refresh some details.
 

It would be really weird if a native not-system library could someway corrupt the behavior of the Android framework and virtualmachine.
Are you able to give more details?
What's the device you're experiencing the bug?
Is the bug rising also using our demo project?

I found that the main issue comes from android.widget.Scroller. If the value of SystemClock.uptimeMillis() exceeds 25 days, on some devices, the value of AnimationUtils.currentAnimationTimeMillis() may sometimes exceed 2,200,000,000L. In the Scroller class, the value of AnimationUtils.currentAnimationTimeMillis() is occasionally cast to an int, which causes this bug. You should rewrite android Scroller and prevent from casting value of AnimationUtils.currentAnimationTimeMillis() to int.
to reproducing this bug you can rewrite Scroller and add AnimationUtils.currentAnimationTimeMillis() value with 2,200,000,000L and then you will see the bug.