DaSilva | # 211 | 2010-05-05, 15:09 | Report

Yeah, that's right but nothing shows me an update (no App manager and no apt-get upgrade) and I have updated AutoDisconnect from 0.2x to 0.3x when 0.3.1 was already released so I don't know how this could have happened and how I can fix it.
Any suggestions?

calvin_42 | # 212 | 2010-05-05, 15:29 | Report

Really strange I've uninstalled AutoDisconnect but with an update I only find the 0.3 version.

But the 0.3.1 is on the repository : http://maemo.org/packages/view/autodisconnect/.

I have no idea about how it is possible!!

Anyone reading this thread, could you please just post the version of AutoDisconnect you see in the update manager ?

Thanks!

kerneld | # 213 | 2010-05-05, 17:35 | Report

Hey! Only installed your app today, but it was v0.3 .. Just uninstalled and tried again and all I get is 0.3 -- that's from devel, though.. Is 0.3.1 available in some other repository? It could be devel just taking priority, for some reason.

Couldn't get your app to work, though.. Manually running the autodisconnect_network_runner script, returns the following:
Could never see it running in the background on top and searching for the pid returned nothing, so I assumed the above errors are preventing it from running. No log file to be seen either. Have uninstalled it for now (pitty, though, your app looks promising and is something I'd really appreciate having), so didn't test this: do you have to reboot after instalation to get it working? This being a linux distro and not windows, I don't particularly like rebooting unless absolutely needed.

Ah, and by the way, I think the description text is a bit garbled up, pretty sure the example for the disconnection threshold says the opposite of what you meant it to say ("if it's less than <threshold> it won't disconnect" shouldn't one of those be the opposite?).

---

Last edited by kerneld; 2010-05-05 at 17:42.

calvin_42 | # 214 | 2010-05-05, 17:37 | Report

OK good news DaSilva. The problem was caused by the Mameo AutoBuilder, which didn't put on the repository the armel version. So I've uploaded again the same version under 0.3.1-2 and it is now working!

Keep me posted if it now works for you!

calvin_42 | # 215 | 2010-05-05, 17:50 | Report

Hi!

So as I said just above, the 0.3.1-2 version is now available. The description text has been corrected too

Well running the autodisconnect_network_runner script won't work because it needs other parameters, but it shouldn't return a syntax error. Are you using sh ? The problem doesn't come from the script but from the environment.you're running it. This prevent from the program to run correctly (no reboot is required).

Cheers!

kerneld | # 216 | 2010-05-05, 18:01 | Report

Bash, actually (what else? :P). Does it depend on busybox being the shell? I ask 'cause I've relinked sh to bash (for a bunch of reasons).

I'll download the newer version and resume testing.

316comp | # 217 | 2010-05-05, 18:05 | Report

is it worth bothering with this app if I like to have my email checking every 5min (amongst other things requiring an active connection)?

calvin_42 | # 218 | 2010-05-05, 18:07 | Report

Ahah Well Busybox uses the ash shell, so it may be the problem. Easy to know :

Try to run :

Is the OK displayed ?

calvin_42 | # 219 | 2010-05-05, 18:11 | Report

No if you want an almost-always active connection AutoDisconnect won't be very useful! 5 mins is a too short interval.

kerneld | # 220 | 2010-05-05, 18:13 | Report

I'm sure Calvin can give you more insight but if you're checking for mail at such short intervals and have other "crap" leeching data off of your connection, unless every single one of those apps is synchronized to the same intervals and pulls the data at the same time, don't bother.

I mean, you'll have to activate the "Always connect" thing on Settings, so anything that needs network access will bring the link up when it needs it. You could set autodisconnect to work at 1 minute intervals and put a relatively high threshold there, in which case it'll bring down the connection at the latest 1'59'' after the last big chunk of data was downloaded, but if the connection is going up and down several times within that 5 minute interval (of your mail widget/app) then it's probably not worth it -- the added overhead will likely negate any savings on battery.