Hi, From: [email protected] [mailto:[email protected]] On Behalf Of ext Kasi Viswanath Sent: 17. maaliskuuta 2011 5:36 To: Eklund Jukka (Nokia-MS/Tampere) Cc: [email protected] Subject: Re: [Meego-handset] N900 DE meeting minutes - 20110315
On 17 March 2011 00:25, <[email protected]<mailto:[email protected]>> wrote: (Sorry for top post, OWA..) Thanks Quim, fully agreed. Let's cordinate tightly on the communications, I at least won't be publishing anything widely before it actually looks good on YouTube :) See the other thread about how we interact with MeeGo trunk. Hi, Agreed on the video demo part to wait for a presentable/stable release. But in the mean time, if the experimental minds want to try something out, is there any image that is recommended now? Also do you have any update on the Bug 7790 - N900 turns warm quickly after boot<https://bugs.meego.com/show_bug.cgi?id=7790> ? If this bug is solved (or atleast situation improved) in the latest DE dailies, I would be interested to try out the alpha (pre-alpha?) DE images. I’ve made few patches to fix the biggest problems: cpu idle now works up to retention state (clocks stopped, power domains in low power state) on the kernel level, though it’s not enabled by default yet. Also we have a fix for the USB regulator issue which causes the USB regulators to be left on at boot (~30mA extra leak there). Biggest issues still needing fixing: - Display does not automatically blank. This is the biggest blocker in getting any standby-time for the device. (one can do this manually with “echo 1 > /sys/class/graphics/fb0/blank”) - WLAN is taking ~180mA at boot, one needs to manually disable it currently to get to good consumption (or connect to a network which also fixes the issue). - Enable/sys/kernel/debug/pm_debug/sleep_while_idle in init scripts - ISP1707 issue (the USB serial transceiver is not disabled properly which causes a static 14,07mA leak) - Plus set of other minor leaks together… With manually blanking the display and disabling wlan, plus some experimental patches for above issues, I’m looking at ~18mA base idle power consumption. In best case I’m hoping to reach 10mA base consumption with cellular modem enabled. Let’s see how far we can get… Of course Jarkko and Srikar are working on DVFS, that will bring even more benefits for the active use cases. -Kalle Thanks, vkvraju Please feel free to write your ideas to the wiki: http://wiki.meego.com/ARM/N900/Ideas. The first one I wrote already earlier, and it got also picked up. The second one I have had in my mind also (see http://wiki.meego.com/ARM/N900/CoolStuff), but specifying a light process would be great. Jukka ________________________________________ From: [email protected]<mailto:[email protected]> [[email protected]<mailto:[email protected]>] on behalf of Gil Quim (Nokia-MS/SiliconValley) Sent: 16 March 2011 20:36 To: Sugano Makoto (Nokia-MS/Helsinki) Cc: [email protected]<mailto:[email protected]> Subject: Re: [Meego-handset] N900 DE meeting minutes - 20110315 Thanks for the explanation. If I got confused then others might get confused as well. Then again the situation *is* confusing these days especially around the whole Handset UX. A first DE release recommended to power users with a blog post, screenshots, video and link to the project wiki pages will solve most of this confusion around the DE, though. On Wed, 2011-03-16 at 05:41 -0700, Sugano Makoto (Nokia-MS/Helsinki) wrote: > Hi there, > > The target of this DE exercise is to realize the 3 use cases on N900, > with the strong emphasis on the usability [1]. Right, so when it comes to technology decisions DE is basically a challenger of the official MeeGo Handset UX. As long as DE sticks with the official Core OS and with a 100% OSS UX layer, anything running better in DE than in the official Handset UX is sending a message to the official development. The problem is knowing what exactly is the official Handset UX development these days, but now I'm perhaps digressing. :) In addition to the 3 use cases + usability, I propose 2 more essential pieces of the project: - An application manager to allow users to install additional apps without having to tinker with the command line. Integration with the upcoming apps.meego.com<http://apps.meego.com> is all what is needed now. - A light process to allow developers to push apps/features to the DE maintained by themselves and playing by the same rules: open source, MeeGo Core compliance, QA tests, open communication. This way the DE has a potential to become more usable for N900 power users without requiring Nokia to increase the resources currently dedicated. These projects could see the DE as a real MeeGo Handset testing bed, and a proof point in their road to convince the MeeGo project about their inclusion in the official releases. This light process would include the possibility to challenge the current apps chosen, of course. With Makoto's team concentrating on the 3 core uses cases, the usability and the project day to day and a door open to install more apps and have more apps becoming 'pre-installed', this Developer Edition might become the first genuine Handset distro. An exciting project! > Whatever the technology choice would be, this activity will stay open > and yes, you'll find the relevant information on the public wiki [1]. -- Quim _______________________________________________ MeeGo-handset mailing list [email protected]<mailto:[email protected]> http://lists.meego.com/listinfo/meego-handset _______________________________________________ MeeGo-handset mailing list [email protected]<mailto:[email protected]> http://lists.meego.com/listinfo/meego-handset -- http://www.vkvraju.com http://vkvraju.blogspot.com http://vkvraju.wordpress.com
_______________________________________________ MeeGo-handset mailing list [email protected] http://lists.meego.com/listinfo/meego-handset
