maemo.org - Talk - ANNOUNCE: Diablo-Turbo first beta available

maemo.org - Talk (https://talk.maemo.org/index.php)

- OS2008 / Maemo 4 / Chinook - Diablo (https://talk.maemo.org/forumdisplay.php?f=29)

- - ANNOUNCE: Diablo-Turbo first beta available (https://talk.maemo.org/showthread.php?t=69740)

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by heavyt (Post 967266)

N810-WiMAX-43-7:~# flasher-3.0-static -sh: flasher-3.0-static: not found

You don't run flasher on the tablet itself.

Re: ANNOUNCE: Diablo-Turbo first beta available

Oh, forgot to ask last time...

One side effect of DT I've seen on both devices is that their respective App Managers now offer me "phantom" updates of packages that are already present, such as :

- last (Nokia) Diablo update
- Community SSU
- webkit-related stuff
- gps-related stuff

Is this because of installing osso-software-version-unlocked ? Or because my poor tablets have led a promiscuous life ? :-)

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by fpp (Post 968128)

Is this because of installing osso-software-version-unlocked ?

Probably because of this. Install osso-software-version-rx{34,44}-unlocked instead depending on what model of NIT you have

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by maacruz (Post 964106)

...
The new feature of this kernel is the BT UART FIFO optimization patch, for people using a2dp.
Everyone is encouraged to test this kernel, specially those who use Bluetooth with headsets or for inet/transfers.

New testing kernel: https://garage.maemo.org/frs/download.php/9413/zImage

Hi, maacruz.

Just installed new kernel. I will test and tell you.

However my BH-214 bluetooth headset is just the same than before. I mean no a2dp support is added. I supose something else is needed. Do you know what is this "something else"?

Thanks in advance and please keep the great job!

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 968142)

Probably because of this. Install osso-software-version-rx{34,44}-unlocked instead depending on what model of NIT you have

I have one of each :-)
Will do, thanks !

Re: ANNOUNCE: Diablo-Turbo first beta available

Well, after some tests with dt packages plus new kernel there are my results:

1 - I don't see my device to be faster than before in any scenario.

2 - I can't to shutdown properly.

However I want to thank maacruz for the effort on this.

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 968142)

Probably because of this. Install osso-software-version-rx{34,44}-unlocked instead depending on what model of NIT you have

Had a quick go at it this morning on the N810 before taking off.
Uninstalled osso-software-version-unlocked and installed osso-software-version-rx44-unlocked in its place.

Almost all "phantom updates" then disappeared from AppMan, except that it still insisted on updating gpsguard to the same version it already that. I accepted the update, half-expecting some error, but it actually went through and the list is now empty.

So, one problem solved, will do the N800 tonight :-)
Thanks !

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by Straycat (Post 968150)

You need the A2DP support package in the A2DP thread. That configures MPlayer to connect to your headset in lieu of using the speakers. You may also find the updated BlueZ packages to be of use or, alternatively, lardman's dsp-sbc (I don't know which is better: ARM opts or utilization of the DSP?)

Quote:

Originally Posted by Straycat (Post 968855)

1 - I don't see my device to be faster than before in any scenario.

I'm not maacruz, but what's a forum without discussion? :)

To me, my N800 isn't "faster" but it's certainly a lot more responsive, making it faster in that respect. For example, I'd sometimes tap the screen when it was blank and it would take ~5 seconds to wake up. Now, with Diablo-Turbo, it wakes up pretty much instantly.

Quote:

2 - I can't to shutdown properly.

Same. While maacruz's mini-rc/sysvinit packages and the newer kernel have reduced the chances of my N800 hanging upon shutdown, it does still happen.

maacruz, do you happen to have the softcursor, bitblit, font and fbcon modules compiled for your kernel? With those modules inserted and fanoush's fb_update_mode, I could at least see the last messages when shutting down before it hangs

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 968927)

Thanks!

Quote:

Originally Posted by jstokes (Post 968927)

I'm not maacruz, but what's a forum without discussion? :)

Very true, bro. ;)

Quote:

Originally Posted by jstokes (Post 968927)

To me, my N800 isn't "faster" but it's certainly a lot more responsive, making it faster in that respect. For example, I'd sometimes tap the screen when it was blank and it would take ~5 seconds to wake up. Now, with Diablo-Turbo, it wakes up pretty much instantly.

Ok. I understand. But I never had these unresponsiveness with my devices so I don't fell it better now.

Quote:

Originally Posted by jstokes (Post 968927)

Same. While maacruz's mini-rc/sysvinit packages and the newer kernel have reduced the chances of my N800 hanging upon shutdown, it does still happen.

I didn't talk about hanging device but device just rebooting when I choose "shutdown" on "power-menu-pakage" option.

And I repeat my thanks to maacruz. Yours is a really great job.

Re: ANNOUNCE: Diablo-Turbo first beta available

Quote:

Originally Posted by jstokes (Post 968927)

Here you'll find dsp-sbc: https://garage.maemo.org/projects/dsp-sbc/
I'll provide in a couple of days arm optimized BlueZ packages to be part of DT.
I think using the DSP would be better, the CPU will be free to do other things and, by choosing the right op_dsp state, you can get significant battery life savings. Of course, only proper testing can provide the answer.

Quote:

Originally Posted by Straycat (Post 968855)

Well, after some tests with dt packages plus new kernel there are my results:

1 - I don't see my device to be faster than before in any scenario.

LOL
I'll prove you wrong. There is one scenario where the device is faster by any measure or definition.
Open osso-mediaplayer
Start playing a mp3

Code:

time sh -c 'i=0; while [ $i -lt 5000 ]; do i=$((i+1)); done'



real    0m0.852s

user    0m0.762s

sys     0m0.008s

Stop playing the mp3

Code:

echo 0 >/sys/power/op_dsp

Start playing the mp3

Code:

time sh -c 'i=0; while [ $i -lt 5000 ]; do i=$((i+1)); done'



real    0m0.678s

user    0m0.621s

sys     0m0.008s

There, you have it, 20% faster in a pure cpu bound task :D
I can also provide a scenario with 40% longer battery life, just play music after 'echo 3 >/sys/power/op_dsp'
Now, except in this scenario, I never promised a faster device (since the cpu is the same and its maximum frequency is 400 MHZ it can't go any faster), but a more responsive one. Unfortunately it is much more difficult to provide an objective measurement for responsiveness.

Quote:

2 - I can't to shutdown properly.

Yes, it's an old issue. I'll finally provide updated mini-rc packages to workaround it, since I can't reproduce it in qemu.