Replicant

Hello, yes, I can confirm this issue. A bit more details:

Phone: Samsung Galaxy Note 2 N7100 (same on Samsung Galaxy S3 i9300)
OS: Replicant 6.0 0003
Connection: WiFi connection through AR9271 USB Dongle, no SIM card inserted
Software: Browsers (in general, including additional software from f-droid such as Firefox Klar/Focus)

Expected behaviour: click on link to a file (e.g. PDF), browser asks if you want to download the file, file gets downloaded to the "Downloads" folder, done.

Observed behaviour: click on link to a file, browser asks you if you want to download the file, download is added to queue but never starts. Also, you can't manually force it to start, it's stuck.

For me, this is pretty annoying, because Replicant should be fully functional without relying on SIM cards. It is currently not possible to download PDFs or any other files from the browser in a WiFi-only setting.

Any ideas?

Update - found a workaround: elinks in Termux can download whatever file you want, which you can then move to your normal folder :) However, this is of course really inconvenient, and I would still like to learn why this doesn't work in "normal" browsers.

Hi,

I also noticed that behaviour.
I think it's a side-issue, related to the one I solved last summer (Issue #1792).
The integrated download app is pausing as soon as any download starts, and it's never resuming.
This almost cerainly has to to with the framework not reporting the available WiFi or USB network connection to the Download app, just like the previous Issue #1792.

I thought my patch solved the problem generally, for every possible app. But it seems I was wrong.
I think I overlooked something and didn't consider some other possible paths in the framework's code.

I can definitely debug that and try to solve it again.

Thanks for reporting!

[EDIT: I opened a new Issue #1867 on the tracker. Any progress will be reported on that page.]

Stay tuned.

Fil

Hi,

I have same problem. I use Galaxy S3 with Replicant 6.003 with OTG and Dongle Wifi Atheros. The Telegram (and others) not work with Wifi OTG using RepWifi. But F-droid and OsmAnd works ;)

Fil, thanks for give us an feedback about this problem. =)

att

wellton costa wrote:

Fil, thanks for give us an feedback about this problem. =)

Hi Wellton,

thanks for reporting your case.

As stated before, I'm aware of that issue, and I'm (slowly) working on a resolution..
I am sure it IS possible to solve that by modifying appropriate functions in the application framework.
Unfortunately I haven't had time to work on that during the last 20 days or so.. but rest assured I'm not giving up!

If anybody has time to help, please feel free to contact me to join efforts; my early work is documented on tracker #1867 and I shall give starting advice to anybody who wants to work on that.
It's not that complicated on the technical side, but to work that out one needs to spend a lot of time building Replicant and debugging.. time that I currently lack..

For now, thanks to everybody who has taken the time to report the issue and detail their use case.

Fil

Hi everybody.

This issue is going to be solved soon by a new release of RepWifi.
You can view the state of the issue on the tracker: #1867.

Happy hacking,

Fil