![]() |
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
|
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
|
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
|
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
|
Re: 'Fixed in Fremantle' and Diablo community SSU
installed on my N810 running all the stuff in my signature and no issues.
Thanks for the continued work to "tune"/"fix" Diablo. |
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
As for getting USB networking working, it's getting a bit off-topic for this thread but here goes anyway: install the maemo-pc-connectivity meta package (actually I think only pc-connectivity-manager and connection-switcher are really needed), use the "PC Connection" status bar applet to select "USB network", and set the IP address on the host side manually. The tablet side is 192.168.2.15/24 so any other 192.168.2.x address with netmask 255.255.255.0 will work on the other side. For Windows hosts you'll need to install the .inf first, but I'm afraid I can't help with anything past that. |
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
deb http://repository.maemo.org/community/ diablo free non-freeI've added these repositories. I presume the Catalogue name can be user-defined so it shouldn't make a difference? Catalogue Name: Community SSU Catalogue Name: Community SSU TestingHowever I now get this error where the Community repository fails to refresh: http://repository.maemo.org/communit...el/Packages.gzThe Testing repository refreshed fine :) but the Community one failed :(. |
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
Yes, the stable repository is currently empty. Feel free to edit the wiki page If the current status section isn't clear enough. |
Re: 'Fixed in Fremantle' and Diablo community SSU
Quote:
The only change from the last -testing version is a cleanup of the osso-pdf-viewer patches (source-level, no effect on runtime). |
Re: 'Fixed in Fremantle' and Diablo community SSU
Regarding poor memory performance after some time of usage, I have just found a major culprit, gpsdriver, again a closed component, has an ugly memory leak of about 1.5-2 MB/day of non swapable memory (I caugt it eating 19 MB of resident RAM). The only workaround is to restart it or disable it when not needed.
|
All times are GMT. The time now is 14:54. |
vBulletin® Version 3.8.8