@the droopy error:
I guess, that droopy is throwing an exception if it writes on FAT32. Since 1.0.6 there is newer droopy version active, which does a chmod during upload as a last step. Chmod is not possible on FAT32
The next difference is, that on OpenWrt droopy is running as root, while RPi it is running as the webserver user (better). I guess there is the major difference.
@Android
We have a fix since 1.0.6 which should fake the answer from the google server, so that Android should think it is still connected with a good signal and valid internet. [github.com]
stylsuxx, can you try to digg out more information about that?
- Which android version
- tcpdump against the wifi interface and if it tries to contact a static configured dns server?
edit:
I just installed your image on my RPi1. The shoutbox problem is a general PirateBox problem, which likely happens on OpenWrt, too. The initial message, written during bootup, does not properly refresh when a person write something. As soon as the first stuff is written, it works. On OpenWrt, I was able to fix it with timestamping the file with a valid date.. (the problem is on browser's end)
The fileupload on normal filesystem (without expanding the storage with moving to fat32 works).. will test the other case this evening
I guess, that droopy is throwing an exception if it writes on FAT32. Since 1.0.6 there is newer droopy version active, which does a chmod during upload as a last step. Chmod is not possible on FAT32
The next difference is, that on OpenWrt droopy is running as root, while RPi it is running as the webserver user (better). I guess there is the major difference.
@Android
We have a fix since 1.0.6 which should fake the answer from the google server, so that Android should think it is still connected with a good signal and valid internet. [github.com]
stylsuxx, can you try to digg out more information about that?
- Which android version
- tcpdump against the wifi interface and if it tries to contact a static configured dns server?
edit:
I just installed your image on my RPi1. The shoutbox problem is a general PirateBox problem, which likely happens on OpenWrt, too. The initial message, written during bootup, does not properly refresh when a person write something. As soon as the first stuff is written, it works. On OpenWrt, I was able to fix it with timestamping the file with a valid date.. (the problem is on browser's end)
The fileupload on normal filesystem (without expanding the storage with moving to fat32 works).. will test the other case this evening