Re: No more optimization team
I opted for the G1, partly for the reasons you've given, but mainly because it turned out to be available as a free upgrade from my old handset. I can't say I'm terribly happy with it. I haven't had my hands on a Freerunner yet for comparison, but depending upon what you want to do with your phone, you may find that the Freerunner gets there first, or has already got there. Is the G1 having problems calling, sending/receiving sms or sound issues? If anyone in the Netherlands is interested in buying my Freerunner please contact me. I'm not a good advocate for the movement anymore, it will probably will be better if someone with a fresh attitude owns it. Based on my experience owning a G1, I'd suggest you try out whatever phone you're planning to use instead before you ditch your Freerunner. Also look at the forums, etc, to see some of the issues people are having. There's no perfect phone out there at the moment. Not looking for a perfect phone, but the basic stuff should be working. Nobody showed up to buy my phone yet, so I might try some images in a few days. I think I will try hackable:1and SHR. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Olivier Migeot wrote: Community, you have this Openmoko company who is still working on their product some months after it's been released. Granted, the first release was nowhere near astounding. But in closed world developement, who could claim such dedication? ;) In a closed world OM would have been panned, the devices returned and probably have been forced out of business by now. Openness is great. FOSS is great. Working base functionality is more important though. After trying to live with the freerunner and OM2008 for a month I bought another phone. My FR is also doing a good impression of a brick most of the time. -- View this message in context: http://n2.nabble.com/No-more-optimization-team-tp1637861p1674010.html Sent from the Openmoko Community mailing list archive at Nabble.com. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Gothnet schrieb: Olivier Migeot wrote: Community, you have this Openmoko company who is still working on their product some months after it's been released. Granted, the first release was nowhere near astounding. But in closed world developement, who could claim such dedication? ;) In a closed world OM would have been panned, the devices returned and probably have been forced out of business by now. Openness is great. FOSS is great. Working base functionality is more important though. After trying to live with the freerunner and OM2008 for a month I bought another phone. My FR is also doing a good impression of a brick most of the time. Maybe i'm teh luckiest guy in the universe, but i've been using my fr as a daily phone without problems (i am always reachable, i don't even know what wsod is, echo is there, but barely noticable, no buzz, te testing image is *FAST*) there are some issues (e.g. i don't like the qpe apps), but the basics are working RELIABLY. the antenna the put into the pill is awesome: i am the only person at the pub, who has reception (which is not always a good thing, becaus there are so many annoying folks out there who keep stealing my time). i am using the testing image (but i also have a backed up 2008.9 which is working perfectly, but slower than the testing, which is why i switched to testing) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
edit: yes, the battery life sucks at the testing image (on 2008.9 i had 40 hours, which is not great, but since i come at least every second day, this was not a problem) ---BeginMessage--- Gothnet schrieb: Olivier Migeot wrote: Community, you have this Openmoko company who is still working on their product some months after it's been released. Granted, the first release was nowhere near astounding. But in closed world developement, who could claim such dedication? ;) In a closed world OM would have been panned, the devices returned and probably have been forced out of business by now. Openness is great. FOSS is great. Working base functionality is more important though. After trying to live with the freerunner and OM2008 for a month I bought another phone. My FR is also doing a good impression of a brick most of the time. Maybe i'm teh luckiest guy in the universe, but i've been using my fr as a daily phone without problems (i am always reachable, i don't even know what wsod is, echo is there, but barely noticable, no buzz, te testing image is *FAST*) there are some issues (e.g. i don't like the qpe apps), but the basics are working RELIABLY. the antenna the put into the pill is awesome: i am the only person at the pub, who has reception (which is not always a good thing, becaus there are so many annoying folks out there who keep stealing my time). i am using the testing image (but i also have a backed up 2008.9 which is working perfectly, but slower than the testing, which is why i switched to testing) ---End Message--- ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Tue, 16 Dec 2008 11:46:01 pm Olivier Migeot wrote: Due to some rather irritating bugs in QTE (high-pitched loud noises from the loudspeaker when answering a call - quite disturbing for co-workers - and duplicating text messages) My guess with that is that's the phone going into speakerphone mode by itself and then causing feedback. I (hopefully!) solved that issue by moving the alsa config file for the speaker phone out of the way and symlinking the gsmhandset file to the original filename. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
2008/12/10 t m ttb.1...@gmail.com The goal of the optimization team was getting us a workable phone. I've installed the testing version yesterday and run into a lot of issues (echo, buzz, not able to wake up) I love the idea of this phone, the openness, the capabilities, but my patience has been stretched beyond tolerance. I have waited more than 2 years for an open phone. Now I have one, I can't use it and I will probably have to wait another half year before the phone will be able to do what any basic phone should be capable of. It is frustrating to see the appearance of great phones like HTC touch or even an iPhone that can do not only basic stuff, but also have the fun part from day one. Android phones are starting to appear. The HTC G1 is not available yet (in the Netherlands), but will be soon. It might not be as open as Openmoko, but it works, has got great features and it is open enough for me.. I opted for the G1, partly for the reasons you've given, but mainly because it turned out to be available as a free upgrade from my old handset. I can't say I'm terribly happy with it. I haven't had my hands on a Freerunner yet for comparison, but depending upon what you want to do with your phone, you may find that the Freerunner gets there first, or has already got there. If anyone in the Netherlands is interested in buying my Freerunner please contact me. I'm not a good advocate for the movement anymore, it will probably will be better if someone with a fresh attitude owns it. Based on my experience owning a G1, I'd suggest you try out whatever phone you're planning to use instead before you ditch your Freerunner. Also look at the forums, etc, to see some of the issues people are having. There's no perfect phone out there at the moment. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Tue, Dec 16, 2008 at 11:32 AM, Jeremy McNaughton jeremy.mcnaugh...@gmail.com wrote: Hi, Just wanting to bring some balance to your (otherwise respectful) comment. Not affiliated to OM, blabla, things like that. I just wanted to chime in on this. I bought the phone not realizing how useless as a phone it would be. And now it's been months, and I still can't rely on it as a phone. Well, maybe it's because I bought the phone for later, still planning to use my old Nokia as a regular phone until Neo's ready, but I'm all in all pretty surprised. In a good way. Of course there's been ups and downs. Every now and then, I tried a new image/distro, and found it awesome at first. As days go by and bugs occurs, I've been less and less enthusiastic, until I tried a new one. With the release of QtExtended 4.4, I tried to put my old Nokia back into the drawer, and use the Neo as my main phone. That whole process was eased thanks to my business dedicated phone, so I wasn't completely left out in the cold even when QTE failed. But for the first time, I was able to put and get calls, without my callers/ees complaining all the time about the echo. The sound wasn't that nice, but it's a cellphone after all, and not so long ago every single cellphone sounded like that. Due to some rather irritating bugs in QTE (high-pitched loud noises from the loudspeaker when answering a call - quite disturbing for co-workers - and duplicating text messages), I tried to move to FSO. And, quite frankly, I'm starting to believe I'll keep this one for a while. I've witnessed no echo nor buzzing yet, been able to send and receive text messages without my them mating like rabbits on viagra - sorry for your antispams, guys) and so on. Of course, I didn't try GPRS nor WiFi, and GPS isn't working as well as it could (well, not at all for now, but I'm investigating it). But at least I can keep it running 24h/day, ssh it and play with it when I feel like it, and still having a working and (as far as I can tell) reliable phone. Until then it sits on a shelf, only getting used every few weekends to test a few images. I'll keep checking the wiki and the lists to see how things are going. But I want to write apps, not troubleshoot echoes and battery problems. I don't know how much time you have, but things are way better when you try it for real than when you read about it. The idea one can get from reading that list is that nothing is working and everyone bitter. From real life testing, it's not that wrong, at least not for everybody. I understand mileage may vary upon several factors (provider, SIM model, Neo revision, lunar month, so on), but for me it's worth the try. I think what Openmoko Inc. really needs is better community relations. It seems that a lot of the dissatisfaction in the community stems from a feeling of being left out of the loop. As a casual member of the community, it is really hard to keep track of what is going on with the project. Once again, it's easier when you're participating, even when it's only testing. Had a few problems posted here, and got some nice feedback, even from OM Inc. people. It really should be hard to keep track when not in it. Looking from the outside, it really seems as though the Openmoko Inc. team is working in isolation, cathedral style. Maybe you should start looking from the inside. The door is wide open :) I would love to see company engineers and developers in constant dialog with the community about the work they are doing on a daily basis. Many open source projects have a blog Planet site, where you can read entries from developers explaining the bugs they are fixing and features they are designing and implementing. This sort of daily interaction would beat a weekly single page of point form notes hands down. Well, I'd rather see them improving OM than in constant dialog. What's most people has been ranting about is the closed fashion of the _design_. And that might be true, but I'm not involved at all in that part (well, even less involved than in the other parts, to be fair) and couldn't notice it. Not that I don't like reading regular updates from developers, but I much prefer running regular updates of their software ;) Sometimes it seems as though Openmoko is depending on community members to fill roles such as maintaining the wiki. For the past view months that I've been reading the wiki and monitoring pages there has been a lot of stale, outdated and confusing information. At various points it has been impossible for me to figure out which kernel to use with which filesystem for a particular distro release within the amount of time I can allot to Openmoko. That's a good point. It's hard to guess what to use and how. But then again, there are so many options out there (FSO, SHR, QTE, ASU and co, Android, ...), with most of them not depending on Openmoko, that it's might be hard for them to maintain documentation about it. Keeping up
Re: No more optimization team
Hi, I just wanted to chime in on this. I bought the phone not realizing how useless as a phone it would be. And now it's been months, and I still can't rely on it as a phone. I was, and still am, excited about writing some python apps for the phone. But frankly I don't see myself doing that until the phone actually works. Until then it sits on a shelf, only getting used every few weekends to test a few images. I'll keep checking the wiki and the lists to see how things are going. But I want to write apps, not troubleshoot echoes and battery problems. I think what Openmoko Inc. really needs is better community relations. It seems that a lot of the dissatisfaction in the community stems from a feeling of being left out of the loop. As a casual member of the community, it is really hard to keep track of what is going on with the project. Looking from the outside, it really seems as though the Openmoko Inc. team is working in isolation, cathedral style. I would love to see company engineers and developers in constant dialog with the community about the work they are doing on a daily basis. Many open source projects have a blog Planet site, where you can read entries from developers explaining the bugs they are fixing and features they are designing and implementing. This sort of daily interaction would beat a weekly single page of point form notes hands down. Sometimes it seems as though Openmoko is depending on community members to fill roles such as maintaining the wiki. For the past view months that I've been reading the wiki and monitoring pages there has been a lot of stale, outdated and confusing information. At various points it has been impossible for me to figure out which kernel to use with which filesystem for a particular distro release within the amount of time I can allot to Openmoko. It looks like the future phone GUI we'll be using is Paroli, which is part of Tichy. Tichy looks really interesting, and will likely be a major part of the Openmoko development platform. If that's the case, why has there been so little information about either project? Openmoko you have this community of users who are still enthusiastic about your product. Do yourself a favour and learn how to keep us interested by opening the lines of communication. Look at other major open source projects that have successfully cultivated active communities around their products. How did they do it? Ubuntu's community didn't happen by accident, it happened by design. Jeremy McNaughton On Thu, Dec 11, 2008 at 5:28 AM, David Garabana Barro da...@garabana.com wrote: On Thursday 11 December 2008 10:55:35 arne anka wrote: sorry, but i fail to understand how this relates to the question of power consumption. and doesn't shr use fso as well? Sorry, I'm not explaying myself... #1024 is annoying me a lot for two reasons 1) If I want to receive calls with phone suspended, I have only one option: SHR As SHR is based in FSO, I suppose you're right, FSO should also work. But only SHR works out of the box. I have tried FSO M4, but I haven't tried to force calypso to never deep sleep. 2) Not deep sleeping, power consumption is not optimal. I know continuously reconnecting consumes more power, but we're consuming more than necessary. And my battery lifetime is not the best in the world ;) I can live without PIM, without calendar, even without Doom ;), but I do need GSM telephony for my work. Having this bug solved, probably I could use FR as daily phone, and be more active on community. I think a lot other people are on the same situation as me. But, as you can read on Steve Mosher's answer, there is one person actively working on this bug. Great news! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On 12/16/08 Jeremy McNaughton wrote: Openmoko you have this community of users who are still enthusiastic about your product. Do yourself a favour and learn how to keep us interested by opening the lines of communication. [snip] Jeremy Your post was very long with many points. Most specifically about engineering and development. We try to talk as opening as possible about engineering work. I can assure you of that. Have you subscribed to the kernel list? The development list? Most of the talk on this list (community) is about things outside of those topics. If there are specific quesetions or problems you have, please just ask questions. Let's get practical together. Most of us at Openmoko, Inc. read these lists. Your comments helps us improve. We're constantly growing and looking to find areas where are very limited internal resources can produce maximum results. Comparing us to Ubuntu is great. I love this challenge. Please keep in mind we're building a company, hardware, a softwarwe distribution, and trying to sell enough Neos to stay in business. That's a lot of moving parts. Adjusting your expectations of what we can do in a short amount of time is helpful. We need your support as much as anyone else's to keep things moving in the right direction. Thanks again for your comments. -Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
well put. I have not had time to get to the community list tonight-- err this morning. I'll address as many of these as possible. Sean Moss-Pultz wrote: On 12/16/08 Jeremy McNaughton wrote: Openmoko you have this community of users who are still enthusiastic about your product. Do yourself a favour and learn how to keep us interested by opening the lines of communication. [snip] Jeremy Your post was very long with many points. Most specifically about engineering and development. We try to talk as opening as possible about engineering work. I can assure you of that. Have you subscribed to the kernel list? The development list? Most of the talk on this list (community) is about things outside of those topics. If there are specific quesetions or problems you have, please just ask questions. Let's get practical together. Most of us at Openmoko, Inc. read these lists. Your comments helps us improve. We're constantly growing and looking to find areas where are very limited internal resources can produce maximum results. Comparing us to Ubuntu is great. I love this challenge. Please keep in mind we're building a company, hardware, a softwarwe distribution, and trying to sell enough Neos to stay in business. That's a lot of moving parts. Adjusting your expectations of what we can do in a short amount of time is helpful. We need your support as much as anyone else's to keep things moving in the right direction. Thanks again for your comments. -Sean ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Thu, 11 Dec 2008 9:28:43 pm David Garabana Barro wrote: 1) If I want to receive calls with phone suspended, I have only one option: SHR As SHR is based in FSO, I suppose you're right, FSO should also work. But only SHR works out of the box. I have tried FSO M4, but I haven't tried to force calypso to never deep sleep. FWIW I can receive calls when suspected with Qt Extended. -- Chris Samuel : http://www.csamuel.org/ : Melbourne, VIC This email may come with a PGP signature as a file. Do not panic. For more info see: http://en.wikipedia.org/wiki/OpenPGP signature.asc Description: This is a digitally signed message part. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Monday 15 December 2008 11:18:03 Yogiz wrote: On Mon, 15 Dec 2008 19:38:31 +1100 FWIW I can receive calls when suspected with Qt Extended. As can I with 2008.9 testing. I have tried all those, you can believe me. Even the latest OM testing image fails for me. I also suspect nearly all my suspend/resume failures are related to #1024. I'm just waiting to SHR to fail on a suspend/resume cycle. Qtextended (every version), 2008.x (I've tried all), FSO, FDOM, fails for me sooner or later. And the sympthoms are allways the same. They resume until they simply stop answering power buttom press. There is not WSOD, they simply doesn't try to resume. I have to hard reset (get off battery and wait a couple seconds) for Neo to revive. It normally, but nor allways, happens after a long suspend cycle. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Mon, 15 Dec 2008 19:38:31 +1100 Chris Samuel ch...@csamuel.org wrote: On Thu, 11 Dec 2008 9:28:43 pm David Garabana Barro wrote: 1) If I want to receive calls with phone suspended, I have only one option: SHR As SHR is based in FSO, I suppose you're right, FSO should also work. But only SHR works out of the box. I have tried FSO M4, but I haven't tried to force calypso to never deep sleep. FWIW I can receive calls when suspected with Qt Extended. As can I with 2008.9 testing. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Fri, Dec 12, 2008 at 2:11 AM, Steve Mosher st...@openmoko.com wrote: Thanks david, One of the difficulties is CND. cannot duplicate which complicates finding the root cause. If you can generate logs that will probably help. Steve Perhaps say what should be run in the phone and what to do to generate the particular log you want and then I could do it too.. my phone after all can be relied upon to show its #1024.. thank you clare David Garabana Barro wrote: On Thursday 11 December 2008 02:23:14 Steve Mosher wrote: RE 1024. The optimization team was not working on 1024. there is one dedicated engineer working on 1024 who specializes in this area. There is some understanding but not certainty on the root cause which may be related to the base station rather than the phone. I don't intend to distract the engineer assigned this task by asking him is it done yet? But I do want to assure folks that there is a dedicated smart as heck person on the problem. More later. Good news, then If you need some type of help on debugging (e.g. trying possible solutions and/or generating logs) count on me. I suffer this bug even with patch applied. It only works for me if I force calypso to *never* deep sleep. Thank you very much!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Thursday 11 December 2008 02:23:14 Steve Mosher wrote: RE 1024. The optimization team was not working on 1024. there is one dedicated engineer working on 1024 who specializes in this area. There is some understanding but not certainty on the root cause which may be related to the base station rather than the phone. I don't intend to distract the engineer assigned this task by asking him is it done yet? But I do want to assure folks that there is a dedicated smart as heck person on the problem. More later. Good news, then If you need some type of help on debugging (e.g. trying possible solutions and/or generating logs) count on me. I suffer this bug even with patch applied. It only works for me if I force calypso to *never* deep sleep. Thank you very much!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Wednesday 10 December 2008 12:11:53 arne anka wrote: setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( don't see that with debian/fso -- i was afraid of it too, but mickey said it wouldn't matter compared to the amount of power drawn by permanent re-connecting ... I know it, but this is not a solution for me. At this moment, I'm only getting reliable calls with SHR. I lose calls when suspended with all the other distros I tried so far. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( don't see that with debian/fso -- i was afraid of it too, but mickey said it wouldn't matter compared to the amount of power drawn by permanent re-connecting ... I know it, but this is not a solution for me. At this moment, I'm only getting reliable calls with SHR. I lose calls when suspended with all the other distros I tried so far. sorry, but i fail to understand how this relates to the question of power consumption. and doesn't shr use fso as well? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Thu, Dec 11, 2008 at 10:55 AM, arne anka [EMAIL PROTECTED] wrote: setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( don't see that with debian/fso -- i was afraid of it too, but mickey said it wouldn't matter compared to the amount of power drawn by permanent re-connecting ... I know it, but this is not a solution for me. At this moment, I'm only getting reliable calls with SHR. I lose calls when suspended with all the other distros I tried so far. sorry, but i fail to understand how this relates to the question of power consumption. and doesn't shr use fso as well? shr uses indeed fso, but they disable deep sleep by default, just because of the bouncing calypso issue (one can simply enable deep sleep if feeling adventurous). Franky ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Thursday 11 December 2008 10:55:35 arne anka wrote: sorry, but i fail to understand how this relates to the question of power consumption. and doesn't shr use fso as well? Sorry, I'm not explaying myself... #1024 is annoying me a lot for two reasons 1) If I want to receive calls with phone suspended, I have only one option: SHR As SHR is based in FSO, I suppose you're right, FSO should also work. But only SHR works out of the box. I have tried FSO M4, but I haven't tried to force calypso to never deep sleep. 2) Not deep sleeping, power consumption is not optimal. I know continuously reconnecting consumes more power, but we're consuming more than necessary. And my battery lifetime is not the best in the world ;) I can live without PIM, without calendar, even without Doom ;), but I do need GSM telephony for my work. Having this bug solved, probably I could use FR as daily phone, and be more active on community. I think a lot other people are on the same situation as me. But, as you can read on Steve Mosher's answer, there is one person actively working on this bug. Great news! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Thanks david, One of the difficulties is CND. cannot duplicate which complicates finding the root cause. If you can generate logs that will probably help. Steve David Garabana Barro wrote: On Thursday 11 December 2008 02:23:14 Steve Mosher wrote: RE 1024. The optimization team was not working on 1024. there is one dedicated engineer working on 1024 who specializes in this area. There is some understanding but not certainty on the root cause which may be related to the base station rather than the phone. I don't intend to distract the engineer assigned this task by asking him is it done yet? But I do want to assure folks that there is a dedicated smart as heck person on the problem. More later. Good news, then If you need some type of help on debugging (e.g. trying possible solutions and/or generating logs) count on me. I suffer this bug even with patch applied. It only works for me if I force calypso to *never* deep sleep. Thank you very much!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Wed, 2008-12-10 at 16:52 +0800, John Lee wrote: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. And you switched your email from .com to .org ... please spare us the politically correct, bring the gossip ! Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
John Lee wrote: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. What the heck? Are there any _long-term_ visions how to make Freerunner a solid and reliable phone? Anyway - kudos goes to the optimization team for their work. PS can appropriate person tell us what is going on and why the optimization team has been dismissed? Kind regards, -- Lech Karol Pawłaszek ike You will never see me fall from grace [KoRn] ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Steve, Sean, anybody more appropriate please clarify this ASAP, no more resources in optimization?? crisis has arrive at least to Openmoko Inc.??? It not sounds any good :( :( 2008/12/10 John Lee [EMAIL PROTECTED]: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
David, the optimization team finished their work a few weeks ago, most people were working on new tasks already. I knew before I had to take the blame for expectations that got unprofessionally raised to a level where we could not deliver, and here I am now taking the blame. Let me explain Openmoko's software strategy for the next 6 months: ---1 current stable image Our current stable image is called 'Om2008.9', available at http://downloads.openmoko.org/releases/Om2008.9/ We are sometimes cherry-picking fixes into it, but admittedly not as many as we would like. If someone wants to step up to become stable maintainer for this image and cherry-pick more fixes into it, please let me know. Alternatively, a number of other images are available, Debian, Qt Extended, Android, FDOM, SHR, etc. See http://wiki.openmoko.org/wiki/Distributions for a more comprehensive list. ---2 Mickey's framework milestones As many people know, the next big thing for Openmoko will be Mickey's FSO framework around d-bus and Python, and the Paroli telephony UI. See http://wiki.openmoko.org/wiki/OpenmokoFramework A few weeks ago, Mickey released milestone 4, available at http://downloads.freesmartphone.org/fso-stable/milestone4.1/ In late January, he plans to come out with milestone 5, in late March with milestone 6. See here for a more detailed roadmap: http://trac.freesmartphone.org/roadmap ---3 next major release, Om2009 After the next 2 FSO milestones, Openmoko will fork off a stable branch, and spend 2-3 months on testing and bug fixing. This will lead to our next major release, Om2009. The telephony UI will be Paroli, see http://code.google.com/p/paroli/ The way things are going right now, we will probably have this release mid-next year. That's about it. Lots of good stuff happening in that direction, most importantly I would mention the progress with our .28 kernel, improved wifi driver, some attempts at getting more out of the glamo chip, improved boot time, etc. Yes, the Optimization team is gone, as part of a bigger company reorganization. Some people were laid off. Some new ones are being hired. John did a great job, and I hope he stays around to continue his excellent work, for example to bring the optimization improvements up into dev.openembedded.org so that more people can see the progress. Best Regards, Wolfgang On Dec 10, 2008, at 5:17 PM, David Reyes Samblas Martinez wrote: Steve, Sean, anybody more appropriate please clarify this ASAP, no more resources in optimization?? crisis has arrive at least to Openmoko Inc.??? It not sounds any good :( :( 2008/12/10 John Lee [EMAIL PROTECTED]: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
the panic about where openmoko puts their efforts in... panic for NO REASON. sorry no offence but, i think it is because of the infacy of some users, which can't hande information and start running around in circles screaming fire, fire fire!. i am sure there will still be optimization, but without a dedicated team, so there won't be regular updates. that was ALL what johne lee said. so calm down, inform yourself. maybe i'm wrong, but i think i can put two and two together Steve, Sean, anybody more appropriate please clarify this ASAP, no more resources in optimization?? crisis has arrive at least to Openmoko Inc.??? It not sounds any good :( :( 2008/12/10 John Lee [EMAIL PROTECTED]: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Le mercredi 10 décembre 2008, Wolfgang Spraul a écrit : David, the optimization team finished their work a few weeks ago, most people were working on new tasks already. I knew before I had to take the blame for expectations that got unprofessionally raised to a level where we could not deliver, and here I am now taking the blame. Hi, First: many thanks to John and the optimization team. I use the testing image as a daily phone, and boot time and interactivity is greatly improved indeed. Second: Basing FDOM on 2008.testing seems even more a good idea now. Given that the official plan does not seem to include its release to the masses. Minh -- Minh HA DUONG, Chargé de Recherche, CNRS CIRED, Centre International de Recherches sur l'Environnement et le Développement http://minh.haduong.com ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
sorry no offence but, i think it is because of the infacy of some users, which can't hande information and start running around in circles screaming fire, fire fire!. sentences like these dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. and then Some people were laid off. Some new ones are being hired. are not likely to inspire confidence (and, imho, they rather sound like there's more to it then just the already expected and scheduled end of team ...). i clearly remember the long and heated debates about the wrench issue (see the archives) and the communication from om being ... worthy of improvement. the same thing applies here: some clear message in the lines of - optimization team reached its intended goals - conclusion what the were exactly and how they were reached - that the members of the team are working on other tasks now - a statement that optimization as such is of course ongoing on all fields would be highly appreciated and, imho, more professional. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Wolfgang Spraul [EMAIL PROTECTED] writes: ---2 Mickey's framework milestones As many people know, the next big thing for Openmoko will be Mickey's FSO framework around d-bus and Python, and the Paroli telephony UI. Thank you very much for this overview of strategy. I have used fso-frameworkd according to my backups since at least 2008-08-23 and to me using it sounds like a good idea. I hope that different subsystems of fso-frameworkd won't rely too much on each other (so that it is possible to answer a call without having the daemon control your display backlight at the same time for example (hypothetical example)). However, I am bit puzzled about building on top of a new graphical toolkit (EFL). Wouldn't we avoid many problems by using established toolkits like QT or GTK+? The UI is supposed to be light so it should be easy to port it to EFL later if there is need? Just like we are prototyping in python and we can later move to C/Vala if needed. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Wed, Dec 10, 2008 at 12:53:18PM +0200, Timo Juhani Lindfors wrote: However, I am bit puzzled about building on top of a new graphical toolkit (EFL). Wouldn't we avoid many problems by using established toolkits like QT or GTK+? The UI is supposed to be light so it should be easy to port it to EFL later if there is need? Just like we are prototyping in python and we can later move to C/Vala if needed. EFL isn't exactly new, just not so popular as gtk+ or qt. I still have to learn it, someday :) Rui -- Kallisti! Today is Prickle-Prickle, the 52nd day of The Aftermath in the YOLD 3174 + No matter how much you do, you never do enough -- unknown + Whatever you do will be insignificant, | but it is very important that you do it -- Gandhi + So let's do it...? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( don't see that with debian/fso -- i was afraid of it too, but mickey said it wouldn't matter compared to the amount of power drawn by permanent re-connecting ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Rui Miguel Silva Seabra [EMAIL PROTECTED] writes: EFL isn't exactly new, just not so popular as gtk+ or qt. Heh, maybe I'm just being a bit debian centric here. I saw libecore0 - Core abstraction layer for enlightenment DR 0.17 in debian experimental and thought that it can't be too established or un-new. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Wolfgang Spraul [EMAIL PROTECTED] writes: Our current stable image is called 'Om2008.9', available at http://downloads.openmoko.org/releases/Om2008.9/ We are sometimes cherry-picking fixes into it, but admittedly not as many as we would like. If someone wants to step up to become stable maintainer for this image and cherry-pick more fixes into it, please let me know. I'm sure more people would contribute fixes if they could figure out how to build the stable distro from source. I re-read http://wiki.openmoko.org/wiki/MokoMakefile again and tried to build it with 1) wget http://www.rwhitby.net/files/openmoko/Makefile 2) make setup 3) make setup-machine-om-gta02 4) sudo sysctl -w vm.mmap_min_addr=0 5) cat build/conf/local.conf EOF PARALLEL_MAKE = -j6 BB_NUMBER_THREADS = 6 GLIBC_GENERATE_LOCALES = en_US.UTF-8 fi_FI.UTF-8 nl_NL.UTF-8 EOF 6) script -c 'make image' ../build1.log but it failed with svn: '/svn/e/!svn/bc/38081/trunk/illume' path not found ... NOTE: package illume-0.0+svnr35818-r13: task do_fetch: failed ... ERROR: Build of /local/lindi/openmoko/mokomakefile/openembedded/packages/e17/illume_svn.bb do_fetch failed The bug report is now at https://docs.openmoko.org/trac/ticket/2169 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Yes - could we have a definitive answer on whether there will be a 2008.12 release of the current testing? I seem to remember that a few weeks ago it was nearly ready and it was almost certainly going to be 2008.11, clearly it slipped... Cheers, - Gunnar Timo Juhani Lindfors wrote: Wolfgang Spraul [EMAIL PROTECTED] writes: Our current stable image is called 'Om2008.9', available at http://downloads.openmoko.org/releases/Om2008.9/ We are sometimes cherry-picking fixes into it, but admittedly not as many as we would like. If someone wants to step up to become stable maintainer for this image and cherry-pick more fixes into it, please let me know. I'm sure more people would contribute fixes if they could figure out how to build the stable distro from source. I re-read http://wiki.openmoko.org/wiki/MokoMakefile again and tried to build it with 1) wget http://www.rwhitby.net/files/openmoko/Makefile 2) make setup 3) make setup-machine-om-gta02 4) sudo sysctl -w vm.mmap_min_addr=0 5) cat build/conf/local.conf EOF PARALLEL_MAKE = -j6 BB_NUMBER_THREADS = 6 GLIBC_GENERATE_LOCALES = en_US.UTF-8 fi_FI.UTF-8 nl_NL.UTF-8 EOF 6) script -c 'make image' ../build1.log but it failed with svn: '/svn/e/!svn/bc/38081/trunk/illume' path not found ... NOTE: package illume-0.0+svnr35818-r13: task do_fetch: failed ... ERROR: Build of /local/lindi/openmoko/mokomakefile/openembedded/packages/e17/illume_svn.bb do_fetch failed The bug report is now at https://docs.openmoko.org/trac/ticket/2169 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Gunnar Aastrand Grimnes gunnar.grimnes [AT] dfki.de DFKI GmbH Knowledge Management Trippstadter Strasse 122 D-67663 Kaiserslautern Germany Office: +49 631 205 75-117 Mobile: +49 177 277 4397 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Hi, On Wed, 2008-12-10 at 18:13 +0800, Wolfgang Spraul wrote: The latest image, including all optimizations from the optimization team are in http://downloads.openmoko.org/daily/testing/ (openmoko-testing-om) We were testing this image a bit, haven't seen the full test report yet. More or less it will be the same as Om2008.9, the most noticeable improvement will be boot time reduction to about 1 minute. To me the most noticeable improvement is that the neo stopped being a power drain while suspended. I don't know whose work it is, but it showed in these testing images and I appreciate it. Regards, Xav ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Bernd, i am sure there will still be optimization, but without a dedicated team, so there won't be regular updates. Correct. From my perspective the updates weren't helpful anyway, I'd rather not talk and instead deliver. The latest image, including all optimizations from the optimization team are in http://downloads.openmoko.org/daily/testing/ (openmoko-testing-om) We were testing this image a bit, haven't seen the full test report yet. More or less it will be the same as Om2008.9, the most noticeable improvement will be boot time reduction to about 1 minute. Now the work in that branch (org.openmoko.dev) is finished, and instead we will bring those fixes upstream into org.openembedded.dev, benefitting many more users, first thing Mickey's FSO builds. Two more FSO milestones over the next 4 months, with optimizations of course continuing everywhere in that time, then a fork into another major release branch. ACTUALLY - speaking about all this - we are looking for a serious distribution maintainer. Someone who can do the exceptionally hard work of distribution integration, fixing bugs, small and large, from top to bottom of the stack, from UI to kernel, across many packages. Someone with a proven Free Software background. Any applications just email me. Best Regards, Wolfgang On Dec 10, 2008, at 5:58 PM, Bernd Prünster wrote: the panic about where openmoko puts their efforts in... panic for NO REASON. sorry no offence but, i think it is because of the infacy of some users, which can't hande information and start running around in circles screaming fire, fire fire!. i am sure there will still be optimization, but without a dedicated team, so there won't be regular updates. that was ALL what johne lee said. so calm down, inform yourself. maybe i'm wrong, but i think i can put two and two together Steve, Sean, anybody more appropriate please clarify this ASAP, no more resources in optimization?? crisis has arrive at least to Openmoko Inc.??? It not sounds any good :( :( 2008/12/10 John Lee [EMAIL PROTECTED]: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Wed, Dec 10, 2008 at 7:44 AM, Timo Juhani Lindfors [EMAIL PROTECTED] wrote: Heh, maybe I'm just being a bit debian centric here. I saw libecore0 - Core abstraction layer for enlightenment DR 0.17 in debian experimental and thought that it can't be too established or un-new. I would usually tend to agree with this statement, but if you did a little more research into Enlightenment, the development for 0.17 has been for at least the last 4 years and the team (mostly led by Carsten Rasterman Haitzler) has started a great initiative to completely build version 0.17 from the ground up and make it the most stable desktop available before even releasing it. Saying this might make people think that development is taking a long time, which is not the case... it has been prompt and steady. They are taking care that everything is designed properly and no major issues are left before releasing it. It has been a few years since I started using it and even though they haven't officially released 0.17, the betas are ever more stable than most desktops I have used, including the EFL framework which is by far the most dynamic, flexible and quickest (and most graphically pleasing) framework for the linux desktop. Openmoko made a great decision to switch to the EFL for it's phone and am greatly anticipating the new changes that will come up in the next few months. Keep up the great work everyone... Will ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
On Wednesday 10 December 2008 10:58:36 Wolfgang Spraul wrote: David, the optimization team finished their work a few weeks ago, most people were working on new tasks already. The most wanted improvement of the optimization team was, at least for me, a solution to #1024. I still suffer it. The bouncing rubber calypso patch doesn't seem to work for me, not in FDOM nor in QtExtended. I can only use my freerunner as reliable phone in SHR, setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( This is the main reason why I can't use my FR as daily phone... I hope this doesn't mean that we have to wait so much for Moko11 firmware with #1024 solution. On the positive side, I have to say that have already patched Moko10, and alll my Movistar (Spanish carrier) 3G SIM problems went away! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Wolfgang thanks a lot for this clear development guide, It really clear my mind and I'm anxious to follow,test and play with all the steps you have mentioned, I will try to helps as much as I can in this line. 2008/12/10 Wolfgang Spraul [EMAIL PROTECTED]: David, the optimization team finished their work a few weeks ago, most people were working on new tasks already. I knew before I had to take the blame for expectations that got unprofessionally raised to a level where we could not deliver, and here I am now taking the blame. Let me explain Openmoko's software strategy for the next 6 months: ---1 current stable image Our current stable image is called 'Om2008.9', available at http://downloads.openmoko.org/releases/Om2008.9/ We are sometimes cherry-picking fixes into it, but admittedly not as many as we would like. If someone wants to step up to become stable maintainer for this image and cherry-pick more fixes into it, please let me know. Alternatively, a number of other images are available, Debian, Qt Extended, Android, FDOM, SHR, etc. See http://wiki.openmoko.org/wiki/Distributions for a more comprehensive list. ---2 Mickey's framework milestones As many people know, the next big thing for Openmoko will be Mickey's FSO framework around d-bus and Python, and the Paroli telephony UI. See http://wiki.openmoko.org/wiki/OpenmokoFramework A few weeks ago, Mickey released milestone 4, available at http://downloads.freesmartphone.org/fso-stable/milestone4.1/ In late January, he plans to come out with milestone 5, in late March with milestone 6. See here for a more detailed roadmap: http://trac.freesmartphone.org/roadmap ---3 next major release, Om2009 After the next 2 FSO milestones, Openmoko will fork off a stable branch, and spend 2-3 months on testing and bug fixing. This will lead to our next major release, Om2009. The telephony UI will be Paroli, see http://code.google.com/p/paroli/ The way things are going right now, we will probably have this release mid-next year. That's about it. Lots of good stuff happening in that direction, most importantly I would mention the progress with our .28 kernel, improved wifi driver, some attempts at getting more out of the glamo chip, improved boot time, etc. Yes, the Optimization team is gone, as part of a bigger company reorganization. Some people were laid off. Some new ones are being hired. John did a great job, and I hope he stays around to continue his excellent work, for example to bring the optimization improvements up into dev.openembedded.org so that more people can see the progress. Best Regards, Wolfgang On Dec 10, 2008, at 5:17 PM, David Reyes Samblas Martinez wrote: Steve, Sean, anybody more appropriate please clarify this ASAP, no more resources in optimization?? crisis has arrive at least to Openmoko Inc.??? It not sounds any good :( :( 2008/12/10 John Lee [EMAIL PROTECTED]: Dear community, I'm writing this to inform you that the optimization team is dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. Regards, John ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
2008/12/10 Minh Ha Duong [EMAIL PROTECTED]: Second: Basing FDOM on 2008.testing seems even more a good idea now. Given that the official plan does not seem to include its release to the masses. I'm doing my best to have a release soon thanks for the support :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- David Reyes Samblas Martinez http://www.tuxbrain.com Open ultraportable solutions Openmoko, Openpandora, GP2X the Wiz, Letux 400 Hey, watch out!!! There's a linux in your pocket!!! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
eeeuhm this is no fix... yes it consumes less globally than with the constant reconnecting, but a ton of c4 is also less harmful than an nuclear bomb doesn't mean we have to be happy with a ton of c4 in our pocket... On Wed, Dec 10, 2008 at 12:11 PM, arne anka [EMAIL PROTECTED] wrote: setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( don't see that with debian/fso -- i was afraid of it too, but mickey said it wouldn't matter compared to the amount of power drawn by permanent re-connecting ... ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Yorick Moko [EMAIL PROTECTED] writes: this is no fix... yes it consumes less globally than with the constant reconnecting, but a ton of c4 is also less harmful than an nuclear bomb doesn't mean we have to be happy with a ton of c4 in our pocket... It's better than without the fix so this is progress. I'm sure that if a better solution would be known by people on the other side of the NDA it'd be implemented right away. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
The goal of the optimization team was getting us a workable phone. I've installed the testing version yesterday and run into a lot of issues (echo, buzz, not able to wake up) I love the idea of this phone, the openness, the capabilities, but my patience has been stretched beyond tolerance. I have waited more than 2 years for an open phone. Now I have one, I can't use it and I will probably have to wait another half year before the phone will be able to do what any basic phone should be capable of. It is frustrating to see the appearance of great phones like HTC touch or even an iPhone that can do not only basic stuff, but also have the fun part from day one. Android phones are starting to appear. The HTC G1 is not available yet (in the Netherlands), but will be soon. It might not be as open as Openmoko, but it works, has got great features and it is open enough for me.. I'm really dissapointed, it feels like losing a bit of faith in a good cause. If anyone in the Netherlands is interested in buying my Freerunner please contact me. I'm not a good advocate for the movement anymore, it will probably will be better if someone with a fresh attitude owns it. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Will Siddall wrote: On Wed, Dec 10, 2008 at 7:44 AM, Timo Juhani Lindfors [EMAIL PROTECTED] wrote: Heh, maybe I'm just being a bit debian centric here. I saw libecore0 - Core abstraction layer for enlightenment DR 0.17 in debian experimental and thought that it can't be too established or un-new. It has been a few years since I started using it and even though they haven't officially released 0.17, the betas are ever more stable than most desktops I have used, including the EFL framework which is by far the most dynamic, flexible and quickest (and most graphically pleasing) framework for the linux desktop. Openmoko made a great decision to switch to the EFL for it's phone and am greatly anticipating the new changes that will come up in the next few months. I do agree. I've used E some years ago, but then I went back to KDE. Now, after re-using and pleasing it in my phone, I decided to put it again on my notbook and I'm more than happy with it: quick, nice, stable (also from daily svn :P) ;). -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
arne anka wrote: sorry no offence but, i think it is because of the infacy of some users, which can't hande information and start running around in circles screaming fire, fire fire!. sentences like these dismissed, so there won't be weekly updates anymore. Further details and reasons behind this are inappropriate to be answered by me. and then Some people were laid off. Some new ones are being hired. are not likely to inspire confidence (and, imho, they rather sound like there's more to it then just the already expected and scheduled end of team ...). i clearly remember the long and heated debates about the wrench issue (see the archives) and the communication from om being ... worthy of improvement. the same thing applies here: some clear message in the lines of - optimization team reached its intended goals - conclusion what the were exactly and how they were reached - that the members of the team are working on other tasks now - a statement that optimization as such is of course ongoing on all fields would be highly appreciated and, imho, more professional. I agree. -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
Wolfgang Spraul wrote: the optimization team finished their work a few weeks ago, most people were working on new tasks already. Mmhmh... I was just thinking... What about the python-loader? If I don't remember wrong, the optimization team had also the task of creating a python loader to enhance the performance of the python applications running on the device (and that with the coming fso+tichy+paroli stack will be more and more used). -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: No more optimization team
RE 1024. The optimization team was not working on 1024. there is one dedicated engineer working on 1024 who specializes in this area. There is some understanding but not certainty on the root cause which may be related to the base station rather than the phone. I don't intend to distract the engineer assigned this task by asking him is it done yet? But I do want to assure folks that there is a dedicated smart as heck person on the problem. More later. David Garabana Barro wrote: On Wednesday 10 December 2008 10:58:36 Wolfgang Spraul wrote: David, the optimization team finished their work a few weeks ago, most people were working on new tasks already. The most wanted improvement of the optimization team was, at least for me, a solution to #1024. I still suffer it. The bouncing rubber calypso patch doesn't seem to work for me, not in FDOM nor in QtExtended. I can only use my freerunner as reliable phone in SHR, setting ti_calypso_deep_sleep = never. That way, it drains a lot of battery even when suspended :( This is the main reason why I can't use my FR as daily phone... I hope this doesn't mean that we have to wait so much for Moko11 firmware with #1024 solution. On the positive side, I have to say that have already patched Moko10, and alll my Movistar (Spanish carrier) 3G SIM problems went away! ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
