![]() |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
|
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
https://garage.maemo.org/plugins/scm...ui&view=markup Line 1148 opens the log and line 400 writes to it. Just change the prefix so you don't overwrite my log file, add a setting to enable the log and have everyone with the shutdown problem enable it and send in their logs after it happens. |
Re: ANNOUNCE: Diablo-Turbo first beta available
i do have the shutdown crash. My install is as of yesterday.
|
Re: ANNOUNCE: Diablo-Turbo first beta available
This is abso freakin' lutely fabulous!
I'll test MPlayer later and post any noticable changes since I encode my videos beyond what my N800 can usually handle (720x480 *lol*). So many thanks for this Mac! :swoon: |
Re: ANNOUNCE: Diablo-Turbo first beta available
Hey Mac, I've been using this cute little script extensively for quite some time. It always worked 100% of the time.
http://talk.maemo.org/showthread.php?t=70091 Since installing DT now, many times it just goes back to the same screen I was on. It's almost like my hardware keys are automatically doing a double tap or something. Can you explain this? |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
xbindkeys is very tricky with its xbindkeysrc file format, and any error like a missing/extra space means both scripts get executed at the same time, producing the observed behavior. By the way, a simpler and cleaner way to achieve the same would be this .xbindkeysrc Code:
"matchbox-remote -next" |
Re: ANNOUNCE: Diablo-Turbo first beta available
Thanks Mac!
I'll try your suggestion and see if that cleans up the behavior. But yeah, it always, always worked before, every single time. Now, there are times when I'll have to press the key like 4 times before it actually changes the screen... so something is definitely different now. Hopefully your new coding for this will take care of the issue since I love going from one app to another in a 10th of a second. :) |
Re: ANNOUNCE: Diablo-Turbo first beta available
I finally had time to take a proper look at this. Installed today, seems to work fine.
But one bug, one of the postinst scripts, I think it was for the kernel package, complained about missing python. I don't have that installed and the package didn't require it. It did still install fine. |
Re: ANNOUNCE: Diablo-Turbo first beta available
I finally got around to backing up my N810 and installing DT...
WOW! There is definitely a perceived speed up and increased responsiveness. When run by itself, Canola seems to get through scanning for files much faster. Other applications also seem to start quicker. I tried running Wesnoth, and it seems to load faster, but getting into the game does not seem much faster. The big change is that now I can do something else while waiting for Wesnoth to load a game instead of looking a an expensive brick. As a side note, I have been adjusting a few VM related things that seem to also help with DT. Here's the script I use: (Note: I use swap on a dedicated partition on my removable SD card) Code:
sysctl -w vm.swappiness=25 |
Re: ANNOUNCE: Diablo-Turbo first beta available
Quote:
Well, python is used to adjust the backup kernel image size, so your zImage backup is the whole mtd1 flash device. That wouldn't have to be bad by itself, except for a few hundred KB lost, but if what I've read about the development of 0xFFFF is correct, writing an image the same size of the mtd device will cause troubles. You better cut the size of /usr/share/Diablo-Turbo/backup/zImage-backup or you risk a reflash if you uninstall kernel-dt-sd. Install python and then, as root: Code:
echo -e 'import struct\n\ |
All times are GMT. The time now is 16:26. |
vBulletin® Version 3.8.8