ANNOUNCE: Diablo-Turbo first beta available - Page 43 - maemo.org

many408 | # 421 | 2011-06-11, 14:22 | Report

Originally Posted by many408 View Post

And dpkg-query -L osso-software-version-* gets me

Package 'osso-software-version-*' is not installed.

I have package-view on this thing; it says I have rx34, so will proceed with the next two steps...

All good, now on to systemui and telescope.

Thanks very much.

Did I say thankyou?

THANKS.

maacruz | # 422 | 2011-06-11, 15:59 | Report

Originally Posted by many408 View Post

All good, now on to systemui and telescope.

Those are easy.
apt-get install telescope
apt-get install advanced-systemui
Then go to the control panel and enable the asui battery applet.
Doesn't your device look better now?

many408 | # 423 | 2011-06-12, 11:45 | Report

Originally Posted by maacruz View Post

Those are easy.
apt-get install telescope
apt-get install advanced-systemui
Then go to the control panel and enable the asui battery applet.
Doesn't your device look better now?

Yes mutch

but

There is now a small problem with Videocamera.

When I start it, it does not get past the "starting camera" stage (unless it times out to standby) until I tap somewhere above the screen in the grey area where the "Videocamera" text is. When I do that, the settings/about/close menu drops down. Another tap gets rid of the menu and shows the camera image(s), with a blanked-out square where the menu was.

More details:

The initial "starting camera" message appears in a white-line frame, which after a short pause to is shifted up about 10 pixels, loosing the top and right lines of the frame and leaving a grey line on the bottom where the bottom white line of the frame was.

If I wait until the app says the camera is on standby and then tap on the little white box it shows me ("tap <box> to activate") almost the same thing happens - "starting camera" in white-line frame, no images BUT there's no upward shift - the top and right lines of the frame do however disappear.

If I wait and do it a second then it does wake up and show images correctly.

In all cases tapping "record" shows a full-screen and it starts recording as it should.

It this a window-priority-thing?

maacruz | # 424 | 2011-06-12, 13:43 | Report

Originally Posted by many408 View Post

Yes mutch

but

There is now a small problem with Videocamera.

When I start it, it does not get past the "starting camera" stage (unless it times out to standby) until I tap somewhere above the screen in the grey area where the "Videocamera" text is. When I do that, the settings/about/close menu drops down. Another tap gets rid of the menu and shows the camera image(s), with a blanked-out square where the menu was.

More details:

The initial "starting camera" message appears in a white-line frame, which after a short pause to is shifted up about 10 pixels, loosing the top and right lines of the frame and leaving a grey line on the bottom where the bottom white line of the frame was.

If I wait until the app says the camera is on standby and then tap on the little white box it shows me ("tap <box> to activate") almost the same thing happens - "starting camera" in white-line frame, no images BUT there's no upward shift - the top and right lines of the frame do however disappear.

If I wait and do it a second then it does wake up and show images correctly.

In all cases tapping "record" shows a full-screen and it starts recording as it should.

It this a window-priority-thing?

Yes, it is a bug in X window compositing, which has been enabled by telescope.
As workaround you can start the camera app with the following command line:

Code:

(camera &); sleep 5; dbus-send --type=method_call --dest=org.freedesktop.Notifications /org/freedesktop/Notifications org.freedesktop.Notifications.SystemNoteInfoprint string:""

The dbus-send command will cause a small empty notification in the tray, and that will remap the window.

The Following User Says Thank You to maacruz For This Useful Post:
jwernerny

ggoebel | # 425 | 2011-06-23, 18:06 | Report

I've just finished wading through all 43 pages in this Diablo Turbo thread. First off, thank you maacruz! I've just updated my first n800 to DT. The user interface is noticeably more responsive. And many folks have expressed their thanks for fixing numerous bugs related to freezing, crashing, and reboots. Thank you maacruz!

Next up... is a rehash of the original instructions for folks wondering if they missed something important between the 1st and last pages of this thread :-) Most of the discussion in this thread was related to folks not following the directions, troubleshooting bugs which were eventually fixed, or discussing work arounds for off topic or loosely connected subjects. If you follow the following, you should be fine... [caveat emptor, backups are golden, and the usual disclaimers...]

How to install:
Pre-requisites:
rootsh: http://wiki.maemo.org/Root_access

Optional Pre-requisites: CSSU installed on top of latest Diablo firmware, Advanced systemui
Updating Firmware: http://wiki.maemo.org/Updating_the_firmware
CSSU: http://wiki.maemo.org/Diablo_Community_Project
ASUI:http://talk.maemo.org/showthread.php?t=63292

Download Diablo Turbo zImage and *.deb files from:
https://garage.maemo.org/frs/?group_id=2036
(don't download files under the sources or obsolete headers)

Create directory /media/mmc1/dt (your external SDHC card)
move all saved dt files to this location

[Verify you have at least 8 MB free]
Open filemanager, press the info button or file->details

[become root:]
start utilities, xterm
> sudo gainroot

[Repository extras-devel or CSSU repository must be enabled to install this]
(where ?? substitute 34 for N800, 44 for N810, 48 for N810-wimax)
> dpkg -r osso-software-version-rx??
> apt-get install osso-software-version-rx??-unlocked
> cd /media/mmc1/dt

[now to install all debs expect an error about sysvinit when you execute the following...]
> dpkg -i *.deb

[work around the aforementioned error by installing sysvinit again]
> dpkg -i sysvinit_2.85-22.osso15-dt1_armel.deb

[optionally, upgrade to the testing kernel]
> fiasco-flasher -f -k zImage

reboot

start utilities, xterm
> uname -a
[you should see the following...]
Linux noname 2.6.21-omap1 #2 PREEMPT [build date] armv6l unknown

enjoy...

Last edited by ggoebel; 2011-06-24 at 12:08. Reason: include maacruz's updates

The Following 14 Users Say Thank You to ggoebel For This Useful Post:
Blue Turtle, buurmas, cstryon, daperezg, GatoViejo, gazza_d, jwernerny, lidow, lma, maacruz, momcilo, SD69, Snoshrk, tso

maacruz | # 426 | 2011-06-23, 19:25 | Report

@ggoebel:
Thanks for your refreshing rehash. Much easier to understand than mine.
With your permission, I'll put them in the first post

ggoebel | # 427 | 2011-06-23, 19:27 | Report

Originally Posted by maacruz View Post

@ggoebel:
Thanks for your refreshing rehash. Much easier to understand than mine.
With your permission, I'll put them in the first post

Sure. Rehashing things is considerably easier than making them happen in the first place. Thank you!

GatoViejo | # 428 | 2011-06-24, 02:00 | Report

Thanks for the summary. However, the zImage file is downloaded and not mentioned again. What happens with it?

maacruz | # 429 | 2011-06-24, 08:30 | Report

Originally Posted by GatoViejo View Post

Thanks for the summary. However, the zImage file is downloaded and not mentioned again. What happens with it?

You can optionally flash it to update the kernel to the last testing release. See the updated first post.

The Following User Says Thank You to maacruz For This Useful Post:
GatoViejo

mcow | # 430 | 2011-06-24, 16:27 | Report

I would tweak the instructions a bit more to make it clear that
1) zimage is optional before instructing to download
2) gps-driverguard.deb is not needed for N800 before instructing to download

The Following User Says Thank You to mcow For This Useful Post:
maacruz