Re: [MeeGo-dev] How to add songs to Meego handset Music Player?

[Zhao, Forrest]

Music Player has not been officially released with MeeGo 1.1. It's not 
feature-complete and still in development/testing phase.

You'll find the announcement and release note when it's officially released.

Thanks,
Forrest


From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Karthick
Sent: 2010年8月12日 18:37
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] How to add songs to Meego handset Music Player?

@ Zhenqiang :

I couldn't find any folder like Music under ~/.

Whether I have to create a folder "Music" under ~/ ?

And, I couldn't get what it is.  any other dir monitored by tracker (you can 
set your special dir by tracker-preferences).

And also, I want to know which file formats it supports..

I couldn't find any release notes in meego handset music player source code.

If u have, could you please share it?


2010/8/12 Chen, Zhenqiang 
mailto:zhenqiang.c...@intel.com>>

Copy your song files to ~/Music or any other dir monitored by tracker (you can 
set your special dir by tracker-preferences).



   From: meego-dev-boun...@meego.com 
[mailto:meego-dev-boun...@meego.com] On 
Behalf Of Karthick
   Sent: 2010年8月12日 14:03
   To: Development for the MeeGo Project (discussion list)
   Subject: [MeeGo-dev] How to add songs to Meego handset Music Player?


   Hi,

   How to add songs to Meego handset music player?

   If anyone knows, please tell me.

   --
   Regards,
   Karthick














___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev



--
Regards,
Karthick












___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] segmentation fault with /usr/bin/ivihome

[axel . endler]

Hi Robin,
thank you, this works better.
... so I replaced the following in /etc/sysconfig/uxlaunch
OLD: session=/usr/bin/startivi
NEW: session=/usr/bin/ivihome -style plastique

Yes: Bug 5225 - segmentation fault with /usr/bin/ivihome


Best regards,
Axel.




Robin Burchell  
Sent by: meego-dev-boun...@meego.com
08/12/2010 02:27 PM
Please respond to
"Development for the MeeGo Project \(discussion list\)" 



To
meego-dev 
cc

Subject
Re: [MeeGo-dev] segmentation fault with /usr/bin/ivihome






Hi Axel,

Excerpts from axel.endler's message of Thu Aug 12 20:33:51 +0100 2010:
> Can anybody help?
> where do I find the core?
> Who should I sent them?

Have you reported an issue on http://bugs.meego.com?

Regardless, something you could try would be to avoid using the 
Maemo6/MeeGo Qt
style, as I've seen that cause problems with some applications in the past 
-
modify the startivi script to call ivihome -style plastique or something, 
and
see if you get any luck there. This is just a hunch, but...

Best,

--
Robin Burchell
http://rburchell.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] segmentation fault with /usr/bin/ivihome

[Robin Burchell]

Hi Axel,

Excerpts from axel.endler's message of Thu Aug 12 20:33:51 +0100 2010:
> Can anybody help?
> where do I find the core?
> Who should I sent them?

Have you reported an issue on http://bugs.meego.com?

Regardless, something you could try would be to avoid using the Maemo6/MeeGo Qt
style, as I've seen that cause problems with some applications in the past -
modify the startivi script to call ivihome -style plastique or something, and
see if you get any luck there. This is just a hunch, but...

Best,

--
Robin Burchell
http://rburchell.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[David Greaves]

On 12/08/10 20:52, Auke Kok wrote:

On 08/12/2010 12:33 PM, Alistair Buxton wrote:

On 12 August 2010 19:07, Ryan Ware wrote:

David,

Seeing your post is a bit disconcerting.
It's hard to decide write a post like that but I felt it should be discussed 
more. I tried to be balanced, raise the issues and my objective was to improve 
the current position.



I would completely disagree that
there are problems on non-Atom hardware. The specific problem is that a
Core 2 or newer is needed.

I'm not a CPU guy so I may have conflated atom and core-2. Blame marketing :)

OTOH it's equally disconcerting that a modern linux distro won't run on modern 
x86 hardware.


As for the scrutiny point, I guess I missed a "will" out: "not all of which will 
stand up to scrutiny".
Please do point out my errors, I am interested in the debate ... I would like to 
see a mechanism for broadening the places MeeGo can go.



Yes, that still does leave a lot of older
hardware out in the cold since they do not support SSE3. It does
however,
include a lot of hardware that is out there. It did start selling in
July
of 2006.

My AMD CPU is less than 12 months old but Meego does not work on it.

$ cat /proc/cpuinfo | grep SSSE3
(no output)

Incidentally my 1 month old 6-core Phenom x6 won't run it.


no matter how much we lower the "baseline", there will always be more
people saying "but I have this CPU and that one is not supported".

At one point you have to say "stop", and disappoint people. You can't
satisfy everyone.


I agree Auke. I really tried to emphasise my understanding of Intel's position; 
but I feel that the exclusion effect is too high.


Anyhow... what can be done to make the baseline/reference MeeGo a *common* 
platform? One that will run on the *majority* of hardware out there and welcomes 
the linux community with open arms!


It can be optimised for Atom - and I actually think it needs to be... the 
journalists would have a fit if it was a smidgen slower than any other distro.


But the community (by which I mean the "other" community since I know MeeGo *is* 
the community ) would currently have to rebuild the entire OS without the 
ssse3 optimisation flag. Is this sensible?


What would be the cost of:
* building for x86 [1]
* identifying packages that benefit from ssse3 and building 2 versions of them?
or
* doing what Qt does and having runtime selection of optimised code? [2]

Oh, AFAIUI mic2 will only run on ssse3 hw... so even if you have a core-2 device 
(see Ryan, I'm getting it) you may not be able to build an image for it on your 
desktop - assuming I'm factually correct still, how does that help MeeGo?


David

[1] x86 = runs on 'popular x86 chips' in laptops/desktops from, say, 2006. This 
includes eg AMD Athlon/Phenom. Note "runs", not optimised for.

[2]
http://mg.pov.lt/meego-irclog/%23meego.2010-08-12.log.html#t2010-08-12T11:06:02
--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Fernando Muñoz]

Isn't it possible to build non-ssse3 images with OBS? I don't think
they require too much code change, or if any is needed, just different
gcc settings.

- Fernando
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Auke Kok]

On 08/12/2010 12:33 PM, Alistair Buxton wrote:

On 12 August 2010 19:07, Ryan Ware  wrote:

On 08/12/2010 06:42 AM, David Greaves wrote:


On 12/08/10 00:06, martin brook wrote:



Hi,

After a lively discussion on #meego
(http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html from 21:17)
I have created a wiki page to further community developmet of a non
SSSE3 Meego build.

http://wiki.meego.com/Devices/nonSSSE3

If you can help in any way or have any comments please add your meego
nick to the wiki with details or catch up with us in #meego



And I've been collecting comments - not all of which are mine and not all
of
which stand up to scrutiny - but which I think *do* reflect a lot of
opinions
and general 'buzz'.

http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html




David,

Seeing your post is a bit disconcerting.  I would completely disagree that
there are problems on non-Atom hardware.  The specific problem is that a
Core 2 or newer is needed.  Yes, that still does leave a lot of older
hardware out in the cold since they do not support SSE3.  It does however,
include a lot of hardware that is out there.  It did start selling in July
of 2006.


My AMD CPU is less than 12 months old but Meego does not work on it.

$ cat /proc/cpuinfo | grep SSSE3
(no output)



no matter how much we lower the "baseline", there will always be more 
people saying "but I have this CPU and that one is not supported".


At one point you have to say "stop", and disappoint people. You can't 
satisfy everyone.



___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Alistair Buxton]

On 12 August 2010 20:33, Alistair Buxton  wrote:
> $ cat /proc/cpuinfo | grep SSSE3

Of course, I meant "cat /proc/cpuinfo | grep ssse3" (lower case)

-- 
Alistair Buxton
a.j.bux...@gmail.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] segmentation fault with /usr/bin/ivihome

[axel . endler]

Can anybody help?
where do I find the core?
Who should I sent them?

PRECONDITION
sudo mic-image-creator --run-mode=0 --cache=mycachedir --format=loop 
--arch=armv7l --release=daily  --compress-disk-image=none --config=i
vi-armv7l-beagle.ks
copy all drivers to /media/Angstrom/lib/modules/2.6.34.1-x2
with or without /etc/init.d/pvr start

TEST
/usr/bin/ivihome --version

RESULT (on console)
2010-08-03 00:24:57 [libcontextsubscriber] WARNING 
[infoxmlbackend.cpp:59:InfoXmlBackend::InfoXmlBackend(QObject*)] Registry 
path "/usr/share/contextkit/providers/" is not a directory or is not 
readable!
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Qt Maemo 6 Style init
appName: /usr/bin/ivihome
Segmentation fault
### BTW: mkdir /usr/share/contextkit/providers # does not help

RESULT (on X window)
I got the following window (repeating all 5 seconds):

A crash occurred in ivihome
The panel will be restarted





Best regards,
Axel

uxlaunch.log:
[04.030609] [221] Error: Unable to open session with ConsoleKit: 
org.freedesktop
.CkConnector.Error: Unable to open session: Failed to execute program 
/lib/dbus-
1/dbus-daemon-launch-helper: Success
[04.030853] [221] launching session bus: dbus-daemon --fork --session 
--print-pi
d 7 --print-address 9


MORE LOGs
/usr/bin/startivi
root window unavailible (maybe another wm is running?)
2010-08-03 00:34:28 [libcontextsubscriber] WARNING 
[infoxmlbackend.cpp:59:InfoXmlBackend::InfoXmlBackend(QObject*)] Registry 
path "/usr/share/contextkit/providers/" is not a directory or is not 
readable!
2010-08-03 00:34:28 [libcontextsubscriber] WARNING 
[infoxmlbackend.cpp:59:InfoXmlBackend::InfoXmlBackend(QObject*)] Registry 
path "/usr/share/contextkit/providers/" is not a directory or is not 
readable!
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Qt Maemo 6 Style init
appName: ividesktop
Qt Maemo 6 Style init
appName: /usr/bin/ivihome
/usr/bin/startivi: line 13:   763 Segmentation fault  ividesktop
/usr/bin/startivi: line 13:   765 Segmentation fault  $panel
A crash occured in ivihome
The panel will be restarted
2010-08-03 00:34:43 [libcontextsubscriber] WARNING 
[infoxmlbackend.cpp:59:InfoXmlBackend::InfoXmlBackend(QObject*)] Registry 
path "/usr/share/contextkit/providers/" is not a directory or is not 
readable!
Connecting to deprecated signal 
QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
Qt Maemo 6 Style init
appName: /usr/bin/ivihome
/usr/bin/startivi: line 13:   773 Segmentation fault  $panel
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Alistair Buxton]

On 12 August 2010 19:07, Ryan Ware  wrote:
> On 08/12/2010 06:42 AM, David Greaves wrote:
>>
>> On 12/08/10 00:06, martin brook wrote:
>>
>>>
>>> Hi,
>>>
>>> After a lively discussion on #meego
>>> (http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html from 21:17)
>>> I have created a wiki page to further community developmet of a non
>>> SSSE3 Meego build.
>>>
>>> http://wiki.meego.com/Devices/nonSSSE3
>>>
>>> If you can help in any way or have any comments please add your meego
>>> nick to the wiki with details or catch up with us in #meego
>>>
>>
>> And I've been collecting comments - not all of which are mine and not all
>> of
>> which stand up to scrutiny - but which I think *do* reflect a lot of
>> opinions
>> and general 'buzz'.
>>
>>    http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html
>>
>>
>
> David,
>
> Seeing your post is a bit disconcerting.  I would completely disagree that
> there are problems on non-Atom hardware.  The specific problem is that a
> Core 2 or newer is needed.  Yes, that still does leave a lot of older
> hardware out in the cold since they do not support SSE3.  It does however,
> include a lot of hardware that is out there.  It did start selling in July
> of 2006.

My AMD CPU is less than 12 months old but Meego does not work on it.

$ cat /proc/cpuinfo | grep SSSE3
(no output)

-- 
Alistair Buxton
a.j.bux...@gmail.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Gabriel M. Beddingfield]

On Thu, 12 Aug 2010, martin brook wrote:

After a lively discussion on #meego 
(http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html from  21:17)  I 
have  created  a  wiki page  to  further community developmet  of a non SSSE3 
Meego  build.


So, what happens when a vendor ships SSSE3 binaries "for 
MeeGo" and the hapless users can't run it because they don't 
have the right processor?


-gabriel


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] [PATCH/sreadahead] Add __NR_ioprio_set for ARM and PowerPC like in uxlaunch. This is to fix ARM build error for sreadahead in MeeGo OBS.

[Carsten Munk]

2010/8/2 Auke Kok :
> On 08/02/10 10:28, Carsten Munk wrote:
>>
>> Originally sent as merge request in gitorious but mail with patch is
>> preferred by maintainer.
>>
>> Signed-off-by: Carsten Valdemar Munk

Any progress? Just double-tested this simple patch in OBS and on
device, seems to make some kind of difference on ARM as well so we'd
like to ask to have it integrated.

Best regards,
Carsten Munk
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[Ryan Ware]

On 08/12/2010 06:42 AM, David Greaves wrote:

On 12/08/10 00:06, martin brook wrote:
   

Hi,

After a lively discussion on #meego
(http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html from 21:17)
I have created a wiki page to further community developmet of a non
SSSE3 Meego build.

http://wiki.meego.com/Devices/nonSSSE3

If you can help in any way or have any comments please add your meego
nick to the wiki with details or catch up with us in #meego
 

And I've been collecting comments - not all of which are mine and not all of
which stand up to scrutiny - but which I think *do* reflect a lot of opinions
and general 'buzz'.

http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html

   

David,

Seeing your post is a bit disconcerting.  I would completely disagree 
that there are problems on non-Atom hardware.  The specific problem is 
that a Core 2 or newer is needed.  Yes, that still does leave a lot of 
older hardware out in the cold since they do not support SSE3.  It does 
however, include a lot of hardware that is out there.  It did start 
selling in July of 2006.


I understand that you say some of the points on the blog post don't 
stand up to scrutiny, but it would be really helpful if you pointed out 
which ones didn't.


BTW, this is being sent from a Lenovo T400 running MeeGo which 
definitely doesn't use an Atom.


Ryan
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] Making meego fast - quick tests and lots of input needed

[Gary Birkett]

Hi,

One of the big things people want nowadays with an OS is speed.
They expect a nice fast solid slick experience.

Last night during the discussions in IRC, performance was mentioned and how
it is lacking in meego at the moment.
Now, we can talk about it being an alpha and a beta and unreleased and its
going to get faster all we want, but it has to get faster from all angles.
There are going to be all sorts of different optimisations available and we
have to start somewhere.


On the n810, I used to have the capability of running in alternative
resolutions.
I could run my applications at full high resolution which did not always run
perfectly quickly and drained the battery a bit more
Or I could change to a lower resolution and carry on running exactly the
same using MUCH less CPU and battery

This also had the drastic effect of making it run *REALLY REALLY FAST*

One of the things about Meego is that it is designed to be run on different
handsets with different screen resolutions.
Some of them will be lower than others and some will be higher.

To gain maximum performance on the reference N900 and to test out this
resolution invariance,
I would like to find out how to change the resolution in Meego.

Now, stskeeps told me that libmeegotouch does infact support variable
resolutions:

 and working out how to operate in alternative resolutions *WILL* be
needed when you get other devices onboard
 lcuk: libmeegotouch already runs in alternative resolutions
 check devices.conf sometime

However, when I have asked about this in the past have heard that there are
some issues with applications not playing too well with variations.
These if true would need to be sorted, but as a quick simple test, I opened
liqbase on my n900 and tried changing the resolutions and rerunning.

 I just did some testing in liqbase
 and running liqbase at *800*480 *gets a framerate doing a certain
task at *45fps*
 running same task at *640*480 *gives me *55fps*
 I do not have capbility to test this [in meego]
 can someone PLEASE try on n900 changing the parameter stskeeps
mentioned
 and tell me if it does change resolution
 and if its a valid strong improvements?
 lcuk: that isn't what sets screen resolutions, just what
resolutions it's expected to work with :P
 so then setting that parameter is first step
 what else? - even accepting a black line down the side
 is it entirely down to the graphics driver?
 the yuv overlay mode can be coerced into stretch to fit (it just did
it for me now)
 I have never managed or tried with rgb

Quite drastic improvement for a 5 minute test!!!

Drawing 20% less pixels gives a speedup of ~20%

Now your turn Meego, how much improvement can be got by changing the
resolution?
how is it done?  stskeeps mentioned in IRC about the parameter just being
the libmeegotouch stuff
so there will be more needed I bet.
what problems are there?

What other mechanisms can be tried???

where else can we get rid of large chunks of sluggishness?

Gary
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] dbus-c++ vs libdbus-c++

[Auke Kok]

On 08/12/2010 02:56 AM, Alexey Khoroshilov wrote:

Looking at 1.0.80.14.20100810.1 repository [1] I wonder if there is any
reason to have two similar packages dbus-c++ and libdbus-c++?

dbus-c++-0.5.0-4.12.armv5tel.rpm:
usr
bin
  dbusxx-introspect
  dbusxx-xml2cpp
lib
  libdbus-c++-1.so.0
  libdbus-c++-1.so.0.0.0
share
  doc
libdbus-c++-0.5.0
  AUTHORS
  COPYING

libdbus-c++-0.5.1-3.12.armv5tel.rpm:
usr
bin
  dbusxx-introspect
  dbusxx-xml2cpp
lib
  libdbus-c++-1.so.0
  libdbus-c++-1.so.0.0.0
share
  doc
libdbus-c++-0.5.1
  README



sounds like a bug, let's treat it as one - can you file a bugzilla pls?

Auke
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Black screen of death when running applications on meego-handset (was: Re: Future of hildon?)

[Jesse Barnes]

On Wed, 11 Aug 2010 17:53:26 +0100
Robin Burchell  wrote:

> Hi Cornelius,
> 
> Excerpts from Cornelius Hald's message of Sun Jul 04 13:04:58 +0100 2010:
> > Here[1] are some screen shots of running a GTK+ application
> > (xfce4-about) on MeeGo/Handset. If mcompositor and mdecorator are both
> > running, I'm only getting a blank screen. Disabling one of both gives
> > some results.
> 
> Did you ever get to the bottom of this? I'm still hearing reports about 3rd
> party applications (not using libmeegotouch) getting black screens of death,
> I don't think it's just an SDK issue because the latest reporter at least was
> using qemu.
> 
> This seems like a pretty serious issue, and I can't find any current bug 
> report
> on it, despite it still (seeming?) to exist.

Yeah, this is an open bug: http://bugs.meego.com/show_bug.cgi?id=2953.
I'm digging into the decorator and compositor now to see what the root
cause is.

-- 
Jesse Barnes, Intel Open Source Technology Center
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Josep Roura]

The buttons in red I experienced too this effected I saw some videos that
this icons has the correct colors but in my case they are always in red. In
my case with bs=4096 it works.

On Thu, Aug 12, 2010 at 16:21, Radi, Rami  wrote:

> I changed my dd command to "dd bs=8192
> if=meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-1.0.80.20100812.0431-mmcblk0p.raw
> of=/dev/sdd" and it made a difference!
>
> Thank you. I guess putting the right size makes a difference, even if the
> whole image is a bit more than 2 GB
>
> Now the device boots successfully, but it looks a bit weird. The main
> applications button and others are in red, as if some pictures were not
> loaded correctly. You can see how it looks by downloading the picture:
> http://www.yousendit.com/download/aHlTU2VpOC9LVlUwTVE9PQ
>
> If anyone can tell me if what I am experiencing is normal or not, I would
> really appreciate it
>
> Thank you,
>
> Rami
>
> -Original Message-
> From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On
> Behalf Of Sharavana Ram Kumar S
> Sent: Thursday, August 12, 2010 2:12 PM
> To: Development for the MeeGo Project (discussion list)
> Subject: Re: [MeeGo-dev] correct way to flash Meego arm5tel
> 1.0.80.13.20100803.2 image on N900
>
> Hi,
>
> >> I tried "./flasher-3.5 -l -b -k " right now and had the same
> problem. the same messages came up then the phone shuts down.
> >> Any clues?
>
> Are you sure the phone goes off?
> Initially it took time for showing up the UX
>
> Also I hope you have added the following line to /etc/rc.local file
>
> echo 255 > /sys/class/backlight/acx565akm/brightness
>
> Regards
> Sharavana
> Aricent Technologies (Holdings) Limited
> Bangalore.
>
>
> "DISCLAIMER: This message is proprietary to Aricent and is intended solely
> for the use of the individual to whom it is addressed. It may contain
> privileged or confidential information and should not be circulated or used
> for any purpose other than for what it is intended. If you have received
> this message in error, please notify the originator immediately. If you are
> not the intended recipient, you are notified that you are strictly
> prohibited from using, copying, altering, or disclosing the contents of this
> message. Aricent accepts no responsibility for loss or damage arising from
> the use of the information transmitted by this email including damage from
> virus."
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
> -
> Intel GmbH
> Dornacher Strasse 1
> 85622 Feldkirchen/Muenchen Germany
> Sitz der Gesellschaft: Feldkirchen bei Muenchen
> Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
> Registergericht: Muenchen HRB 47456 Ust.-IdNr.
> VAT Registration No.: DE129385895
> Citibank Frankfurt (BLZ 502 109 00) 600119052
>
> This e-mail and any attachments may contain confidential material for
> the sole use of the intended recipient(s). Any review or distribution
> by others is strictly prohibited. If you are not the intended
> recipient, please contact the sender and delete all copies.
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>



-- 
L'ahir és història
El demà és un misteri
L'avui és un regal
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Radi, Rami]

I changed my dd command to "dd bs=8192 
if=meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-1.0.80.20100812.0431-mmcblk0p.raw
 of=/dev/sdd" and it made a difference!

Thank you. I guess putting the right size makes a difference, even if the whole 
image is a bit more than 2 GB

Now the device boots successfully, but it looks a bit weird. The main 
applications button and others are in red, as if some pictures were not loaded 
correctly. You can see how it looks by downloading the picture: 
http://www.yousendit.com/download/aHlTU2VpOC9LVlUwTVE9PQ

If anyone can tell me if what I am experiencing is normal or not, I would 
really appreciate it

Thank you,

Rami

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Sharavana Ram Kumar S
Sent: Thursday, August 12, 2010 2:12 PM
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] correct way to flash Meego arm5tel 
1.0.80.13.20100803.2 image on N900

Hi,

>> I tried "./flasher-3.5 -l -b -k " right now and had the same 
>> problem. the same messages came up then the phone shuts down.
>> Any clues?

Are you sure the phone goes off?
Initially it took time for showing up the UX

Also I hope you have added the following line to /etc/rc.local file

echo 255 > /sys/class/backlight/acx565akm/brightness

Regards
Sharavana
Aricent Technologies (Holdings) Limited
Bangalore.


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
-
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] libtimed compilation

[ext-bernd.wachter]

"ext hoangnguyen"  writes:

> Yeah, that was a stupid question. Waht I want to know is whether they
> are planning to port libtimed (and other closed source components) to
> meego ?

Yes. libtimed won't make it into the September release, though. 

Bernd
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Tobias Renz]

After writing the image with dd boot back into maemo. Then back into flasher
mode. Then reload the kernel and see if it works.
Tobias
> Hi,
>
>
>> And finally I flashed the generated kernel file using the following
>> command:
>>
>> *./flasher-3.5 -f -k
>>
"meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
>> -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks*
>>
>> * *
>>
>
> Why are you using the option -r <>.ks file? why is it needed here?
>
> For me this image is working properly.
>
>
> --
> Regards,
> ssrk
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Sharavana Ram Kumar S]

Hi,

>> I tried "./flasher-3.5 -l -b -k " right now and had the same 
>> problem. the same messages came up then the phone shuts down.
>> Any clues?

Are you sure the phone goes off?
Initially it took time for showing up the UX

Also I hope you have added the following line to /etc/rc.local file

echo 255 > /sys/class/backlight/acx565akm/brightness

Regards
Sharavana
Aricent Technologies (Holdings) Limited
Bangalore.


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Radi, Rami]

I tried "./flasher-3.5 -l -b -k " right now and had the same 
problem. the same messages came up then the phone shuts down.

Any clues?

Rami

-Original Message-
From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On 
Behalf Of Sharavana Ram Kumar S
Sent: Thursday, August 12, 2010 1:58 PM
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] correct way to flash Meego arm5tel 
1.0.80.13.20100803.2 image on N900

Hi,

   just ./flasher-3.5 -l -b -k  will do

Regards
Sharavana
Aricent Technologies (Holdings) Limited
Bangalore.

From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of 
ssrk [ssrk...@gmail.com]
Sent: Thursday, August 12, 2010 5:23 PM
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] correct way to flash Meego arm5tel 
1.0.80.13.20100803.2 image on N900

Hi,

And finally I flashed the generated kernel file using the following command:
./flasher-3.5 -f -k 
"meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
 -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks


Why are you using the option -r <>.ks file? why is it needed here?

For me this image is working properly.


--
Regards,
ssrk


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev
-
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Sharavana Ram Kumar S]

Hi,

   just ./flasher-3.5 -l -b -k  will do

Regards
Sharavana
Aricent Technologies (Holdings) Limited
Bangalore.

From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] On Behalf Of 
ssrk [ssrk...@gmail.com]
Sent: Thursday, August 12, 2010 5:23 PM
To: Development for the MeeGo Project (discussion list)
Subject: Re: [MeeGo-dev] correct way to flash Meego arm5tel 
1.0.80.13.20100803.2 image on N900

Hi,

And finally I flashed the generated kernel file using the following command:
./flasher-3.5 -f -k 
"meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
 -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks


Why are you using the option -r <>.ks file? why is it needed here?

For me this image is working properly.


--
Regards,
ssrk


"DISCLAIMER: This message is proprietary to Aricent and is intended solely for 
the use of the individual to whom it is addressed. It may contain privileged or 
confidential information and should not be circulated or used for any purpose 
other than for what it is intended. If you have received this message in error, 
please notify the originator immediately. If you are not the intended 
recipient, you are notified that you are strictly prohibited from using, 
copying, altering, or disclosing the contents of this message. Aricent accepts 
no responsibility for loss or damage arising from the use of the information 
transmitted by this email including damage from virus."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Ameya Palande]

Hi Rami,

On Thu, 2010-08-12 at 13:25 +0200, ext Radi, Rami wrote:
> Hi all,
> 
>  
> 
> I created the 1.0.80.13.20100803.2 raw file using the
> mic-image-creator command as in
> http://forum.meego.com/showpost.php?p=6580&postcount=90 on Fedora 13.
> 
>  
> 
> Then I wrote it to a 8GB ssd mmc card using the following:
> 
> dd bs=4069
> if=meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-1.0.80.20100812.0431-mmcblk0p.raw
>  of=/dev/sdd

In above command, I guess bs=4096 or bs=8192 is good.

>  
> 
> And finally I flashed the generated kernel file using the following
> command:
> 
> 
> ./flasher-3.5 -f -k
> "meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
>  -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks

Since you already wrote the meego rootfs to SD card, there is no need to
pass "-r" option to flasher.

"flasher -f -k  -b" should be enough.

Cheers,
Ameya.


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[ssrk]

Hi,


> And finally I flashed the generated kernel file using the following
> command:
>
> *./flasher-3.5 -f -k
> "meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
> -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks*
>
> * *
>

Why are you using the option -r <>.ks file? why is it needed here?

For me this image is working properly.


-- 
Regards,
ssrk
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] State of ARM N900 kickstart-generated image?

[José Luís]

Hi Tom,

This is a problem with the last image-creator application. I have updated
them today and had the same problem. To fix then you can apply the following
simple patch:

diff --git a/mic/imgcreate/creator.py b/mic/imgcreate/creator.py
index 32542ea..1709da9 100644
--- a/mic/imgcreate/creator.py
+++ b/mic/imgcreate/creator.py
@@ -134,7 +134,7 @@ class ImageCreator(object):
 self._dep_checks.remove(dep)

 if not os.path.exists("/usr/bin/qemu-arm") or not
is_statically_linked("/usr/bin/qemu-arm"):
-creator._dep_checks.append(("/usr/bin/qemu-arm-static",))
+self._dep_checks.append(("/usr/bin/qemu-arm-static",))

 return True



[]'s


2010/8/12 Tom Chen 

> Hi,
>
> i try to build the N900 image as the post
> http://forum.meego.com/showpost.php?p=6580&postcount=90  said , but i got
> the error like below.
>
> Retrieving
> http://repository.maemo.org/meego/2a5e7de0123d9723051f4f6396a9d4c0/builds/trunk/1.0.80.13.20100803.2/nokia-n900-non-oss/repos/armv5tel/packages//repodata/nokia-proprietary-comps.xml.gz...OK
> Warning: can't get
> http://repository.maemo.org/meego/2a5e7de0123d9723051f4f6396a9d4c0/builds/trunk/1.0.80.13.20100803.2/nokia-n900-non-oss/repos/armv5tel/packages//repodata/repomd.xml.key
> Retrieving
> http://repo.meego.com/MeeGo/builds/trunk/1.0.80.13.20100803.2/core/repos/armv5tel/packages//noarch/meego-release-1.0.80-2.2.noarch.rpm...OK
> Available target architectures: [u'armv5tel']
>
> MeeGo release 1.0.80
>
> Traceback (most recent call last):
>   File "/usr/bin/mic-image-creator", line 807, in 
> ret = main()
>   File "/usr/bin/mic-image-creator", line 744, in main
> creator.set_target_arch(target_arch)
>   File "/usr/lib/python2.6/site-packages/mic/imgcreate/creator.py", line
> 137, in set_target_arch
> creator._dep_checks.append(("/usr/bin/qemu-arm-static",))
> NameError: global name 'creator' is not defined
> [r...@tom Meego]#
>
> i already update my image-creator and build it again. the version of
> mic-image-creator is 0.19, is that right?
>
> Br
> Tom Chen
>
> On Thu, Aug 12, 2010 at 2:42 AM, Tom Chen  wrote:
>
>> Hi,
>>
>>thanks, i will try it.
>>
>> Br
>> Tom Chen
>>
>>
>> On Thu, Aug 12, 2010 at 2:38 PM,  wrote:
>>
>>> Hi,
>>>
>>> > if i build the N900 image as you said, what's the command i should used
>>> to run it on my fedora13 host? my fedora13 installed with VMWare.
>>>
>>> He talks about the real hardware, not a virtual machine.
>>> To run a N900 image, you need QEMU (or the real hardware).
>>>
>>> Cheers,
>>>
>>> Fathi
>>>
>>> ___
>>> MeeGo-dev mailing list
>>> MeeGo-dev@meego.com
>>> http://lists.meego.com/listinfo/meego-dev
>>>
>>
>>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>
>


-- 
José Luís do Nascimento
Signove - Enjoy Innovation
Home page: http://www.signove.com
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] correct way to flash Meego arm5tel 1.0.80.13.20100803.2 image on N900

[Radi, Rami]

Hi all,

I created the 1.0.80.13.20100803.2 raw file using the mic-image-creator command 
as in http://forum.meego.com/showpost.php?p=6580&postcount=90 on Fedora 13.

Then I wrote it to a 8GB ssd mmc card using the following:
dd bs=4069 
if=meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-1.0.80.20100812.0431-mmcblk0p.raw
 of=/dev/sdd

And finally I flashed the generated kernel file using the following command:
./flasher-3.5 -f -k 
"meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2-vmlinuz-2.6.35~rc6-133.2-n900"
 -r meego-handset-armv5tel-n900-nokia-proprietary-1.0.80.13.20100803.2.ks

I then disconnect the USB cord then the phone starts to boot, then the phone 
shuts down. The last few messages that are shown on the screen ar:
Freeing init memory : 140k
Mmc1: new high speed MMC card at address 0001
Mmcblk1: mmc1:0001 MMC32G 29.8 GIB
Mmcblk1: p1 p2 p3

Can someone help me find out what I am doing wrong?

Thank you,

Rami
-
Intel GmbH
Dornacher Strasse 1
85622 Feldkirchen/Muenchen Germany
Sitz der Gesellschaft: Feldkirchen bei Muenchen
Geschaeftsfuehrer: Douglas Lusk, Peter Gleissner, Hannes Schwaderer
Registergericht: Muenchen HRB 47456 Ust.-IdNr.
VAT Registration No.: DE129385895
Citibank Frankfurt (BLZ 502 109 00) 600119052

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] libtimed compilation

[hoangnguyen]

On Thu, 2010-08-12 at 12:52 +0200, Carsten Munk wrote:
> 2010/8/12 hoangnguyen :
> > Does anyone have any idea on how to compile libtimed from harmattan ? I
> > am trying to compile it in fedora 13.
> >
> > Thanks,
> > Hoang
> 
> I believe libtimed is not a open component, I think you might be
> asking in the wrong place and you might want to talk to your project
> manager about this topic.
> 
> Best regards,
> Carsten Munk
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev

Yeah, that was a stupid question. Waht I want to know is whether they
are planning to port libtimed (and other closed source components) to
meego ?

:).

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] libtimed compilation

[Carsten Munk]

2010/8/12 hoangnguyen :
> Does anyone have any idea on how to compile libtimed from harmattan ? I
> am trying to compile it in fedora 13.
>
> Thanks,
> Hoang

I believe libtimed is not a open component, I think you might be
asking in the wrong place and you might want to talk to your project
manager about this topic.

Best regards,
Carsten Munk
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] libtimed compilation

[hoangnguyen]

Does anyone have any idea on how to compile libtimed from harmattan ? I
am trying to compile it in fedora 13.

Thanks,
Hoang

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] non SSSE3 MeeGo

[David Greaves]

On 12/08/10 00:06, martin brook wrote:

Hi,

After a lively discussion on #meego
(http://mg.pov.lt/meego-irclog/%23meego.2010-08-11.log.html from 21:17)
I have created a wiki page to further community developmet of a non
SSSE3 Meego build.

http://wiki.meego.com/Devices/nonSSSE3

If you can help in any way or have any comments please add your meego
nick to the wiki with details or catch up with us in #meego


And I've been collecting comments - not all of which are mine and not all of 
which stand up to scrutiny - but which I think *do* reflect a lot of opinions 
and general 'buzz'.


  http://mer-l-in.blogspot.com/2010/08/are-intel-subverting-meegocom.html

David

--
"Don't worry, you'll be fine; I saw it work in a cartoon once..."
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] How to add songs to Meego handset Music Player?

[Karthick]

@ Zhenqiang :

I couldn't find any folder like Music under ~/.

Whether I have to create a folder "Music" under ~/ ?

And, I couldn't get what it is.  any other dir monitored by tracker (you can
set your special dir by tracker-preferences).

And also, I want to know which file formats it supports..

I couldn't find any release notes in meego handset music player source code.

If u have, could you please share it?


2010/8/12 Chen, Zhenqiang 

>
> Copy your song files to ~/Music or any other dir monitored by tracker (you
> can set your special dir by tracker-preferences).
>
> 
>
>From: meego-dev-boun...@meego.com [mailto:
> meego-dev-boun...@meego.com] On Behalf Of Karthick
>Sent: 2010年8月12日 14:03
>To: Development for the MeeGo Project (discussion list)
>Subject: [MeeGo-dev] How to add songs to Meego handset Music Player?
>
>
>Hi,
>
>How to add songs to Meego handset music player?
>
>If anyone knows, please tell me.
>
>--
>Regards,
>Karthick
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev
>



-- 
*Regards,*
*Karthick
*
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

[MeeGo-dev] dbus-c++ vs libdbus-c++

[Alexey Khoroshilov]

Looking at 1.0.80.14.20100810.1 repository [1] I wonder if there is any 
reason to have two similar packages dbus-c++ and libdbus-c++?


dbus-c++-0.5.0-4.12.armv5tel.rpm:
usr
  bin
dbusxx-introspect
dbusxx-xml2cpp
  lib
libdbus-c++-1.so.0
libdbus-c++-1.so.0.0.0
  share
doc
  libdbus-c++-0.5.0
AUTHORS
COPYING

libdbus-c++-0.5.1-3.12.armv5tel.rpm:
usr
  bin
dbusxx-introspect
dbusxx-xml2cpp
  lib
libdbus-c++-1.so.0
libdbus-c++-1.so.0.0.0
  share
doc
  libdbus-c++-0.5.1
README


[1] 
http://mirrors1.kernel.org/meego/builds/1.0.80/1.0.80.14.20100810.1/core/repos/ia32/packages/i586/


--
Regards,
Alexey Khoroshilov
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] How to add songs to Meego handset Music Player?

[Chen, Zhenqiang]

Copy your song files to ~/Music or any other dir monitored by tracker (you can 
set your special dir by tracker-preferences).



From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] 
On Behalf Of Karthick
Sent: 2010年8月12日 14:03
To: Development for the MeeGo Project (discussion list)
Subject: [MeeGo-dev] How to add songs to Meego handset Music Player?


Hi,

How to add songs to Meego handset music player?

If anyone knows, please tell me.

-- 
Regards,
Karthick














___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] State of ARM N900 kickstart-generated image?

[Tom Chen]

Hi,

i try to build the N900 image as the post
http://forum.meego.com/showpost.php?p=6580&postcount=90  said , but i got
the error like below.

Retrieving
http://repository.maemo.org/meego/2a5e7de0123d9723051f4f6396a9d4c0/builds/trunk/1.0.80.13.20100803.2/nokia-n900-non-oss/repos/armv5tel/packages//repodata/nokia-proprietary-comps.xml.gz...OK
Warning: can't get
http://repository.maemo.org/meego/2a5e7de0123d9723051f4f6396a9d4c0/builds/trunk/1.0.80.13.20100803.2/nokia-n900-non-oss/repos/armv5tel/packages//repodata/repomd.xml.key
Retrieving
http://repo.meego.com/MeeGo/builds/trunk/1.0.80.13.20100803.2/core/repos/armv5tel/packages//noarch/meego-release-1.0.80-2.2.noarch.rpm...OK
Available target architectures: [u'armv5tel']

MeeGo release 1.0.80

Traceback (most recent call last):
  File "/usr/bin/mic-image-creator", line 807, in 
ret = main()
  File "/usr/bin/mic-image-creator", line 744, in main
creator.set_target_arch(target_arch)
  File "/usr/lib/python2.6/site-packages/mic/imgcreate/creator.py", line
137, in set_target_arch
creator._dep_checks.append(("/usr/bin/qemu-arm-static",))
NameError: global name 'creator' is not defined
[r...@tom Meego]#

i already update my image-creator and build it again. the version of
mic-image-creator is 0.19, is that right?

Br
Tom Chen

On Thu, Aug 12, 2010 at 2:42 AM, Tom Chen  wrote:

> Hi,
>
>thanks, i will try it.
>
> Br
> Tom Chen
>
>
> On Thu, Aug 12, 2010 at 2:38 PM,  wrote:
>
>> Hi,
>>
>> > if i build the N900 image as you said, what's the command i should used
>> to run it on my fedora13 host? my fedora13 installed with VMWare.
>>
>> He talks about the real hardware, not a virtual machine.
>> To run a N900 image, you need QEMU (or the real hardware).
>>
>> Cheers,
>>
>> Fathi
>>
>> ___
>> MeeGo-dev mailing list
>> MeeGo-dev@meego.com
>> http://lists.meego.com/listinfo/meego-dev
>>
>
>
___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] N900: Enabling CONFIG_SCHEDSTATS in arm-generic

[Ameya Palande]

Hi Carsten,

On Sat, 2010-08-07 at 20:22 +0200, ext Carsten Munk wrote:
> Hi,
> 
> To look closer at our boot time in ARM/N900 it would be useful if we
> could get CONFIG_SCHEDSTATS enabled in our N900 kernel in order to
> have bootchart working [1]
> 
> README states it might need CONFIG_SCHED_DEBUG too but it doesn't look
> enabled in other configs in the MeeGo kernel.
> 
> Something that can be enabled? :)
> 
> Best regards,
> Carsten Munk
> 
> [1] http://meego.gitorious.org/meego-developer-tools/bootchart

Done!

Cheers,
Ameya.

___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev

Re: [MeeGo-dev] Suggestion on new project ideas

[An Yang]

在 2010-08-10二的 10:03 -0700，Greg KH写道：

> On Mon, Aug 09, 2010 at 10:39:41AM -0700, Auke Kok wrote:
> > On 08/09/10 10:28, Carsten Munk wrote:
> > >2010/8/9 Auke Kok:
> > >>On 08/08/10 11:22, Anup Bansod wrote:
> > >>>
> > >>>I have been studying the architecture for meego for quite a few days now
> > >>>and also the bugs/deficiencies, i have found some things i can work on 
> > >>>like
> > >>>
> > >>>1. Support for NTFS formatted devices
> > >>
> > >>This feature was purposedly not enabled.
> > >
> > >Out of technical curiousity (not intending to start a flamewar) and
> > >just to have a record of this reasoning for future FAQ, why was this?
> > >
> > >Mostly curious from perspective that some people has ntfs formatted
> > >USB hds and such and a fairly common topic of netbook usage is
> > >portability in data.
> > 
> > it's been a while (we basically took the decision from moblin2
> > along), but from what I remember we negatively assessed the
> > stability of it in Linux and we'd rather not ship code that can wipe
> > your data...
> 
> Do you have reports of where this has happened for you?  It's a
> requirement for some of us to ship this, and any reported issues would
> be great to have so we can resolve them as soon as possible.


customer inside before intel inside please intel guys.


> 
> thanks,
> 
> greg k-h
> ___
> MeeGo-dev mailing list
> MeeGo-dev@meego.com
> http://lists.meego.com/listinfo/meego-dev


___
MeeGo-dev mailing list
MeeGo-dev@meego.com
http://lists.meego.com/listinfo/meego-dev