And a handy bug to help track it:
https://bugs.meego.com/show_bug.cgi?id=14980
BR
Carsten Munk
2011/3/29 Carsten Munk :
> Hi,
>
> Seems like fennec-qt is failing to build under armv8el (hard floating
> point port), please check out what goes wrong at:
>
> https://build.meego.com/package/live_bui
Hi,
Seems like fennec-qt is failing to build under armv8el (hard floating
point port), please check out what goes wrong at:
https://build.meego.com/package/live_build_log?arch=armv8el&package=fennec-qt&project=Trunk%3ATesting&repository=standard
devel:browser repository should have the 'armv8el'
> On Mon, Mar 28, 2011 at 4:57 PM, Andy Ross wrote:
> > The tablet apps are Qt/QML. They don't link to libmeegotouch (though
> > there are some transitive dependencies that pull it in and initialize
> > bits of it -- I'm pretty sure it's *not* creating a dummy
> MApplicaiton
> > anymore at least)
On Mon, Mar 28, 2011 at 4:57 PM, Andy Ross wrote:
> The tablet apps are Qt/QML. They don't link to libmeegotouch (though
> there are some transitive dependencies that pull it in and initialize
> bits of it -- I'm pretty sure it's *not* creating a dummy MApplicaiton
> anymore at least) and can't us
A
On 18 Dec 2010 20:33, wrote:
> Send MeeGo-handset mailing list submissions to
> meego-handset@lists.meego.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.meego.com/listinfo/meego-handset
> or, via email, send a message with subject or body 'help' to
> meego-hands
Robin Burchell wrote:
> I have been doing some investigation here. I can save us 10mb per
> app launched by trying to switch off opengl until we get the
> meego-graphics-system fixes in (bug 12929) which should help quite a
> bit.
The tablet apps are Qt/QML. They don't link to libmeegotouch (thoug
Kasi,
> Because when you are on a call, you really don't have much idea/control on
> where your ear/face touches the screen. The regular experience has been that
> sometime during a call, some random apps would have been opened and...!
In a product, touch screen & LCD get disabled when you are
Hi,
On Mon, Mar 28, 2011 at 1:16 PM, Arun Ravindran
wrote:
> The "call" object here is CallProxy*
right, ok, I missed the first argument, please ignore
>>> +bool CallItemModel::multiparty() const
>>
>> this method could do with clearer naming. 'hasMultiparty'?
>>
> Hmm, just followed the conven
Hi,
On Mon, Mar 28, 2011 at 12:34 PM, wrote:
+void CallItem::callMultiPartyChanged()
+{
+TRACE
+emit multiPartyChanged();
+}
after:
+
connect(call,SIGNAL(multiPartyChanged()),this,SLOT(callMultiPartyChanged()));
The "call" object here is CallProxy*
Used as:
CallPro
Hi,
On Mon, Mar 28, 2011 at 12:34 PM, wrote:
+void CallItem::callMultiPartyChanged()
+{
+TRACE
+emit multiPartyChanged();
+}
after:
+
connect(call,SIGNAL(multiPartyChanged()),this,SLOT(callMultiPartyChanged()));
The "call" object here is CallProxy*
Used as:
CallPro
Hi,
>In /usr/lib/duicontrolpanel/meegotouchcp-connman.desktop the Category is
>marked as "Connectivity",
>but there is no such category in /usr/share/duicontrolpanel/categories/
>
>Should the Category in meegotouchcp-connman.desktop be changed to
>"Connections" or
>should the connections.cpcat
Hi,
In /usr/lib/duicontrolpanel/meegotouchcp-connman.desktop the Category is marked
as "Connectivity",
but there is no such category in /usr/share/duicontrolpanel/categories/
Should the Category in meegotouchcp-connman.desktop be changed to "Connections"
or
should the connections.cpcategory be
Hi,
Just some comments from me.
On Mon, Mar 28, 2011 at 12:34 PM, wrote:
> +void CallItem::callMultiPartyChanged()
> +{
> + TRACE
> + emit multiPartyChanged();
> +}
after:
> +
> connect(call,SIGNAL(multiPartyChanged()),this,SLOT(callMultiPartyChanged()));
so, calling callMu
Thanks Jarno,
>Fully loaded battery last at first attempt 5h 30min and on 2nd attempt
>another battery same device 5h 15min (device was of course idle all the
>time)
Great to see the actual figure for the battery life.
Would be nice to include this data in the qa-reports.meego.com
All the best,
From: Arun Ravindran
Added handling of multipart property in the call proxy, call item and callitem
model by adding a signal
to be emited for the property changes. This signal is handled in call manager
now. Removed the usage of
multiparty call items and call names from call manager. Also re ar
Old batteries and we haven't measure terminal voltage. Just make a really easy
and ruff measurements.
--Jarno
> We have done script and with help of that tested the battery life of N900 DE.
> Script just write time stamp for a file every 30sec and after device has shut
> down we read first a
Hi,
> -Original Message-
> From: meego-handset-boun...@lists.meego.com [mailto:meego-handset-
> boun...@lists.meego.com] On Behalf Of Teivas Jarno.1 (EXT-Digia/Finland)
> Sent: 28. maaliskuuta 2011 13:06
> To: meego-handset@lists.meego.com
> Subject: [Meego-handset] N900 DE battery l
> We have done script and with help of that tested the battery life of N900 DE.
> Script just write time stamp for a file every 30sec and after device has shut
> down we read first and last time
> stamp from a memorycard and calculate time.
> Backlight and screen was on all the time during tests
Hi,
More info about those testings.
No configurations and SIM card inserted.
Out from the box with this image:
http://download.meego.com/trunk-daily/builds/trunk/1.1.90.8.20110322.2/images/meego-handset-armv7l-n900-devel/
--Jarno
Hi,
We have done script and with help of that tested the bat
Thanks,
> > I would be very interested to hear your thoughts on this!
>
> My own thoughts are that there's actually another path: cherry-pick
> handset apps to the 'new' UX where there is no functional replacement.
You're right, that's what I meant with option 1 actually (fill the gaps where
ne
Hi,
We have done script and with help of that tested the battery life of N900 DE.
Script just write time stamp for a file every 30sec and after device has shut
down we read first and last time stamp from a memorycard and calculate time.
Backlight and screen was on all the time during tests.
Fu
Hi,
On Mon, Mar 28, 2011 at 10:44 AM, wrote:
> For the option 1) we need to carefully evaluate how to the new concept works
> as a handset UX and specifically on the N900 device (performance, memory
> usage etc.).
I have been doing some investigation here. I can save us 10mb per app
launched
So, for the N900 DevEdition we have some new options now:
1) use new UX as basis
2) use current Handset UX and cherry-pick new apps to replace old ones where
relevant
3) do not use the new UX or apps
I think we already have evidence to show that option 3) is not desired.
For the option 1) we nee
Hi,
Provided we don't want to switch to tablet UX, I sat down and checked
how well the applications run under Handset UX.
General problems:
* Status bar is included in each application and it isn't systemui
* No hook for status bar click (reach systemui) in our meegotouch-systemui
* Task switchi
24 matches
Mail list logo
