Re: ANNOUNCE: Diablo-Turbo first beta available
 

I've mentioned this before but I'll say it once more.

This no longer works the same after installing DT.
http://talk.maemo.org/showthread.php?t=70091

I mostly switch screens between Tear and VNC.

Anyway, if the page on Tear hasn't fully loaded, the screen doesn't switch correctly as it did before.

I have to usually wait until the entire webpage is done loading in Tear, then I can switch applications.

This wasn't the behavior before DT.

Any clues as to what might be causing this?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I don't use VNC but I do use Tear a lot and have never had a problem with it not loading when a I switch away. I normally open links in new windows and immediately switch back to the original window while it loads.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

^ Weird.

On my end it will switch from say Tear to Dial Central or from Tear to VNC and then immediately go back to Tear again.

If a web page is loading in Tear, yeah, sometimes I have to try switching like 7 times before it will actually change applications.

Never once did I experience this behavior before DT.

Oh well I guess. :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I'm not sure exactly how to say it except that switching applications on the fly is back to being fussy again like it was when I first had DT installed some time back.

When it does work correctly though, wow, it switches like twice as fast than without DT, I do have to admit that. :)

Hey, pop quiz.

You know when you click on the Task Navigator thingy, how all of the apps line up on the left side of the screen...

Yeah, is there perhaps a command that will switch to exactly one app you want to go to next?

So say you hit the Task Navigator, and on the screen you'll see something like this...

Dial Central X
Tear X
VNC X
Notes X
File Manager X

If they are in order, could you have a command that says to switch to the top one, or switch to the second or third one specifically instead of rifling through either the previous or the following applications?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Yes, Telescope. ;)

Statusbar applet to open Telescope's app launcher and another statusbar applet to open Telescope's window thumbnails, or home key to get to both. So a statusbar tap or home key press followed by a tap will switch to any app you want.

Now if someone would hack the window manager so a down swipe on the titlebar would minimize a window and a left or right swipe on titlebar would switch to the next or previous window... :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Didn't you make that one code which creates an invisible touch screen surface space on the tablet? So yeah, you can do this. :)

Oh, and what I meant was skipping the whole tapping the screen part to change applications. I really like only having to press one button and I'm done.

Does Diablo have code that knows the order in which apps are launch?

So if I wanted to switch to an app, say that I open 4th, it could go there immediately?

I hope I'm making sense here.

With that Quickswitch thingy I use, it can only go to the previous or following app of what's in the list for Task Navigator.

I guess I'm just asking if there's a possible different way of doing this if say 5 or 6 apps were all being used at once.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Sorry. Sorry.

Let me keep this very simple.

I usually only have two apps running.

Is there a command to switch to either the top app or the bottom app instead of using matchbox-remote -next like I'm doing now?

Maybe trying something else would stop it from being so fussy like the way it is using DT.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

If Quickswitch could be bound to a statusbar applet, I would be very happy.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

pan-daemon expects the signal com.nokia.icd /com/nokia/icd com.nokia.icd.status_changed string:"DUMMY" string:"DUMMY" string:"DISCONNECTING" string:""
I have tried sending the signal by hand but it 's ignored because it doesn't come from the expected service.
icd2 doesn't send that signal when instructed to disconnect with a dbus method call, that's why the problem happens, but I have observed that the signal with string:"IDLE" (instead of "DISCONNECTING") is always sent.
So, I think the best fix is to change pan-daemon so it calls the script when receives the "IDLE" signal.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Telescope already is.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Uploaded maemo-pan_1.0.3 to extras-devel. Fixes disconnection from ASUI.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I know. Quickswitch is the actual funcionality I want while driving, but with my set up it wouldn't work bound to a key, unless it's the home button which Telescope already uses.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I would rather have a statusbar applet that let's you change different Xbindkey profiles.

I think that would be the best way of doing this. :)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I guess we need to learn to code and start creating these things then. ;)

But we're getting off topic.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Anyone know how to configure matchbox the way maemo uses it? The configuration below produces a binary 27k smaller. If I can get this to produce the same binary then I can add titlebar swiping support to switch windows or minimize. :)

http://repository.maemo.org/pool/dia...indow-manager/

./configure --prefix=/usr --enable-standalone --enable-ping-protocol --disable-session --disable-xrm --disable-composite --disable-gconf --disable-startup-notification --disable-expat --disable-debug

EDIT: --enable-standalone shouldn't have been used and gets it within 4k.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Look at debian/rules (--enable-alt-input-wins --disable-xrm --enable-xsync --enable-frameanimation).

Re: ANNOUNCE: Diablo-Turbo first beta available
 

yep, the 1.0.3 change fixes maemo-pan for ASUI.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Another spontaneous reboot earlier today. It actually rebooted twice so the logs from just before were rotated out of existence, but in both the ones I had left the boot reason was 32wd_to this time.

I don't know if it's significant, but at the time I was logged in via ssh and running BMEFree.py (testing power drain when using a particular AP). The tablet was otherwise idle and the screen off and locked. The battery level was ~90%.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I had many reboots when playing with bmefree.py.
I think it is possible that two bme requests, one from bmefree and another from ASUI, can coincide in time and trigger a reboot.
I also had a strange event today. My N810 switched off itself after sounding the alarm, but it looks more like one of those hardware issues it has from time to time. Uptime was 7 days.
Anyway, I have discovered that the fuse module doesn't load. It seems I built the -3 kernel and fuse module with DEBUG_PREEMPT but somehow managed to save .config without it. I have just uploaded a new zImage with DEBUG_PREEMPT so fuse works.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Do anybody have the kernel modules need for pptp VPN?
ppp_mppe.ko and others. I mean for turbo kernel.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

List the modules you need and I´ll build them when I get the time.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Hey, maacruz, you are the man!

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I found list of modules in http://talk.maemo.org/showthread.php?t=13725

crypto_algapi
arc4
sha1
cryptomgr
blkcipher
cbc
pcbc
ecb
ppp_mppe

Thanks

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I guess need to compile also new kernel.
I applied your patches to kernel source from kernel-source package,
changed .config to include ppp_mppe module and compiled modules.
Have error while install modules into memory.
Unknown symbol crypto_alloc_base
Unknown symbol crypto_has_alg
Unknown symbol crypto_free_tfm
I tried to compile kernel and got error
mm/vmscan.c:1614 error: structure has no member named `pages_lots'
PS
Sorry. I missed *.diff files from patches directory :)
To be continue

Re: ANNOUNCE: Diablo-Turbo first beta available
 

CONFIG_CRYPTO in DT kernel is not set.
Kernel should be recompiled with
CONFIG_CRYPTO=y
CONFIG_PPP_MPP=y

Re: ANNOUNCE: Diablo-Turbo first beta available
 

vpn pptp works with DT!
I can upload kernel and modules.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Can you load the modules in the published DT kernel binary, or do they require a new kernel build?
Please post here the .config file for your kernel

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Needs to compile new kernel because CONFIG_CRYPTO=y isn't set in DT kernel. I'll post .config later ( forget USB cabel at home :) )
The difference in config is:
CONFIG_CRYPTO=y
CONFIG_PPP_MPP=y

Re: ANNOUNCE: Diablo-Turbo first beta available
 

my kernel config

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I just noticed that having sudser (which does not allow you to do "sudo gainroot", but does allow most "sudo" usages) is not enough -- you need rootsh. Otherwise this fails for me:
Anyway, I tried everything today & it all seemed to succeed, but after reboot I got this in X Terminal:
Not, as stated in the instructions:
I assume that this is OK based on some other comments in this thread, but please let me know if not.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Does (or can) this crypto discussion also cover cryptsetup /dm luks? I use this type of encryption with my desktop linux system.

* Detailed kernel compilation with cryptsetup with config images are here

* These modules were mentioned in this posting:
dm-mod (required for dm-*)
dm-crypt
Devicemapper (userspace binaries for dm-mod)
dmsetup or cryptsetup-luks (frontends for dm-* API)

* Further links: 1, 2, 3, 4, 5, 6, 7

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Everything is OK, you just have installed the last kernel binary zImage

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks, maacruz. BTW, since I installed DT I have twice gotten the situation where it won't dim and the power button fails to work. I know that this is discussed in this thread -- I apologize that I haven't grasped all the details or the current status of the problem. This is not a big problem for me because I can just reboot using the advanced power monitor and the problem goes away. But please let me know if there is anything I can do to troubleshoot the problem. Also, if I figure out any pattern for what triggers the behavior I will of course post here.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

If it happens just after booting, the problem is in MCE, a closed source component, so we can't fix it (we tried, a lot).
Workaround is to restart mce from xterm (/etc/init.d/mce restart)

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Thanks. I'll see if I can identify a pattern (it's certainly not obvious that it is caused by rebooting). Re: the workaround, perhaps others have mentioned this but, for those who use Personal Menu, it's easy to create a "Command" item for that mce command you mentioned. That would be a handy way to fire off the workaround whenever needed.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Heh, thanks for the reminder. had forgotten about that.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I've duplicated the problem a few times in the past week. In those cases I've plugged my N810 in for the night and awakened to find it having the dimming problem. I may have set the alarm all those days. So it could be due to the alarm or it could be happening at some random point in the night. But it doesn't happen every time I plug in my N810 for the night or every time I use the alarm feature.

In these times, restarting mce has solved the screen dimming problem, but the power button still doesn't pull up the system ui menu. I have to reboot to get that back.

Are there any tests I can run now to get more information about the power button problem? Or any tests I should run the next time I duplicate the dimming problem?

Re: ANNOUNCE: Diablo-Turbo first beta available
 

So your not using Advanced System UI, Buurmas?

If so that is interesting, as so far i had figured it was a ASUI issue.

Re: ANNOUNCE: Diablo-Turbo first beta available
 

Try restarting systemui after restarting mce

Re: ANNOUNCE: Diablo-Turbo first beta available
 

I don't think that I have ever experienced the non-dimming bug, but I have lost the power button a few times.

Try this instead next time to avoid rebooting.

sudo /etc/init.d/mce restart


Edit: And also what Mac said. :)