Re: SHR status
W.Kenworthy wrote: Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on this problem. To manually try it, mount debugfs and do the echo command, or create as below and reboot. In /etc/fstab add this line (all one line :) debugfs /sys/kernel/debug debugfs defaults 0 0 and create /etc/init.d/NO_NEW_FAIR_SLEEPERS containing _ #!/bin/sh -x echo NO_NEW_FAIR_SLEEPERS /sys/kernel/debug/sched_features _ and use update-rc.d to add it to the default boot levels. debugfs exposes some knobs and innards of the kernel, the one here making the kernels default scheduler behave more like the BFS scheduler that hit the news a couple of months ago, creating a far more responsive device including when it rings. BillK Tireid it! did not do the job for me: bottup was faster (as soon as the illuem desktop came up i had reception, but the bt symbol was still showing, so something wasn quite ready autosuspend didn't work. everything was _EXTREMELY_ slow (remember om2008.8/fdom? ;-)) shr-settings is borked could't connect to ophonekitd/FSO i sent myself an sms from the internet. - phone woke up 5 seconds later *ring* so i reverted it. rebooted and still have a borked phone. i am using mrmoku-testing and somethign is really fucked up now i don't blame you its just that i want to say that it can be harmful ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Tue, 2009-10-20 at 12:10 +0200, Bernd Prünster wrote: W.Kenworthy wrote: Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on this problem. To manually try it, mount debugfs and do the echo command, or create as below and reboot. In /etc/fstab add this line (all one line :) debugfs /sys/kernel/debug debugfs defaults 0 0 and create /etc/init.d/NO_NEW_FAIR_SLEEPERS containing _ #!/bin/sh -x echo NO_NEW_FAIR_SLEEPERS /sys/kernel/debug/sched_features _ and use update-rc.d to add it to the default boot levels. debugfs exposes some knobs and innards of the kernel, the one here making the kernels default scheduler behave more like the BFS scheduler that hit the news a couple of months ago, creating a far more responsive device including when it rings. BillK Tireid it! did not do the job for me: bottup was faster (as soon as the illuem desktop came up i had reception, but the bt symbol was still showing, so something wasn quite ready autosuspend didn't work. everything was _EXTREMELY_ slow (remember om2008.8/fdom? ;-)) shr-settings is borked could't connect to ophonekitd/FSO i sent myself an sms from the internet. - phone woke up 5 seconds later *ring* so i reverted it. rebooted and still have a borked phone. i am using mrmoku-testing and somethign is really fucked up now i don't blame you its just that i want to say that it can be harmful I doubt its doing anything bad - seems more likely you have a bad/misconfigured install, or possibly a bad/intermittant GSM modem connection (the serial port side) as thats similar to what I see when it doesnt initialise properly - lots of things in the framework do not work well until the GSM serial line is working. It usually takes a couple of minutes after you get the desktop before its registered so something is different if it registered as soon as the desktop comes up. You might want to check the frameworkd.log to see whats really happening. BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
William Kenworthy wrote: I doubt its doing anything bad - seems more likely you have a bad/misconfigured install, or possibly a bad/intermittant GSM modem connection (the serial port side) as thats similar to what I see when it doesnt initialise properly - lots of things in the framework do not work well until the GSM serial line is working. It usually takes a couple of minutes after you get the desktop before its registered so something is different if it registered as soon as the desktop comes up. You might want to check the frameworkd.log to see whats really happening. BillK Now i know what was happening. too late or too early start of frameworkd and/or ophonekitd. stopping and starting manually in the correct order solves all the problmes. br ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
William Kenworthy wrote: ... I gave it another shot and i must say it quite awesome: i called myself from another phone and the moment i heard it ringing my fr woke up and showed the incoming call screen. i know the debugfs approch might not be a nice and clean one, but i couldn't care less when i see hav reactive everything is now. the startup of fso /opehnekitd also fixed itself magically (i thik gremlins are to blame for the previeous fail) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Tue, 2009-10-20 at 15:33 +0200, Bernd Prünster wrote: William Kenworthy wrote: ... I gave it another shot and i must say it quite awesome: i called myself from another phone and the moment i heard it ringing my fr woke up and showed the incoming call screen. i know the debugfs approch might not be a nice and clean one, but i couldn't care less when i see hav reactive everything is now. the startup of fso /opehnekitd also fixed itself magically (i thik gremlins are to blame for the previeous fail) I'm glad you find it as useful as I have. However your experience is mirroring mine in that the FR software seems to work but often (and especially after a crash) it may take a few reboots to work smoothly. I know software is supposed to be deterministic and do the same operations everytime, but from the outside looking in, the FR has a mind of its own :) I suspect cleaning of tmp files, and possibly badblocks or corrupted file system are the causes - gets fixed up during reboot - sometimes see the messages during bootup. So I always do at least 3 reboots before saying a particular upgrade isn't working - as mad as it sounds, it sometimes helps! I am using shr-u from early June with a 2.6.28 kernel last updated before the updates stopped being pushed, and since I have stopped trying to chase the updates, its been very usable (and still has an occasional disastrous crash though :) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
2009/10/19 W.Kenworthy bi...@iinet.net.au are you using the latest moko11 GSM firmware? - anything else and missed messages are a distinct possibility. http://wiki.openmoko.org/wiki/GSM/Flashing BillK Yes, I've updated the firmware. The missed calls are because I can't answer them. I hit answer and the phone keeps ringing. The positive side is that I know who called and can call back. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
Yes, I've updated the firmware. The missed calls are because I can't answer them. I hit answer and the phone keeps ringing. The positive side is that I know who called and can call back. This happens to me on litephone...and I always thought that it was a litephone issue. Which phone-app do you use? (ophonekitd???, shr-launcher???) ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
Am Montag, den 19.10.2009, 12:55 +0530 schrieb Vikas Saurabh: Yes, I've updated the firmware. The missed calls are because I can't answer them. I hit answer and the phone keeps ringing. The positive side is that I know who called and can call back. This happens to me on litephone...and I always thought that it was a litephone issue. Which phone-app do you use? (ophonekitd???, shr-launcher???) I had that with paroli. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
2009/10/19 Vikas Saurabh vikas.saur...@gmail.com Yes, I've updated the firmware. The missed calls are because I can't answer them. I hit answer and the phone keeps ringing. The positive side is that I know who called and can call back. This happens to me on litephone...and I always thought that it was a litephone issue. Which phone-app do you use? (ophonekitd???, shr-launcher???) I use litephone. Here's a thread about this bug. http://n2.nabble.com/FSO-can-t-answer-incoming-call-tp3568219p3568619.html ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
Tried the NO_NEW_FAIR_SLEEPERS hack? - made a real difference to me on this problem. To manually try it, mount debugfs and do the echo command, or create as below and reboot. In /etc/fstab add this line (all one line :) debugfs /sys/kernel/debug debugfs defaults 0 0 and create /etc/init.d/NO_NEW_FAIR_SLEEPERS containing _ #!/bin/sh -x echo NO_NEW_FAIR_SLEEPERS /sys/kernel/debug/sched_features _ and use update-rc.d to add it to the default boot levels. debugfs exposes some knobs and innards of the kernel, the one here making the kernels default scheduler behave more like the BFS scheduler that hit the news a couple of months ago, creating a far more responsive device including when it rings. BillK On Mon, 2009-10-19 at 09:03 +0200, Michal Brzozowski wrote: 2009/10/19 W.Kenworthy bi...@iinet.net.au are you using the latest moko11 GSM firmware? - anything else and missed messages are a distinct possibility. http://wiki.openmoko.org/wiki/GSM/Flashing BillK Yes, I've updated the firmware. The missed calls are because I can't answer them. I hit answer and the phone keeps ringing. The positive side is that I know who called and can call back. ___ 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: SHR status
2009/10/19 W.Kenworthy bi...@iinet.net.au debugfs exposes some knobs and innards of the kernel, the one here making the kernels default scheduler behave more like the BFS scheduler that hit the news a couple of months ago, creating a far more responsive device including when it rings. It's not about responsiveness, there is simply a bug somewhere. Changing the scheduler might hide the bug, but that's rather bad isn't it? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Mon, Oct 19, 2009 at 11:12:51AM +0800, W.Kenworthy wrote: On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote: On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Define reliable telephony as - at least as good as the cheap ~$au100 phones available from your local carrier. Freerunner: much less :( But it's getting better! However that is beyond the point... since the merge is already happening, if nobody did a snapshot of shr-u to move it to shr-t then it's all a moot point, now. Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Mon, 2009-10-19 at 10:56 +0200, Michal Brzozowski wrote: 2009/10/19 W.Kenworthy bi...@iinet.net.au debugfs exposes some knobs and innards of the kernel, the one here making the kernels default scheduler behave more like the BFS scheduler that hit the news a couple of months ago, creating a far more responsive device including when it rings. It's not about responsiveness, there is simply a bug somewhere. Changing the scheduler might hide the bug, but that's rather bad isn't it? ___ Yes, but it depends whether you want to receive calls or not - I prefer to talk to my callers, not have to call them back :) Its a known problem that has been there ever since they switched to FSO. Its supposed to be gradually fixed as they move away from python towards C for the underlying code, but I think scheduling is having a greater effect at the moment as proven by this hack. It doesnt totally fix it, as I was just using midori full screen (in landscape via xrandr) and on exiting midori the caller hung up by the time the display stabilised - and didnt leave a number :( BillK ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
So... what you guys are telling me is nothing has changed since the beginning of september? Is it at least faster than it was before? I remember everything would take forever to load, even the terminal. -- View this message in context: http://n2.nabble.com/SHR-status-tp3845266p3855921.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: SHR status
On Monday 19 October 2009 07:59:37 pm abatrour wrote: So... what you guys are telling me is nothing has changed since the beginning of september? Is it at least faster than it was before? I remember everything would take forever to load, even the terminal. Well I have flashed the image from this month on my phone to test and I haven't played with it much, still reinstalling things and setting it back up. -- We must plan for freedom, and not only for security, if for no other reason than only freedom can make security more secure. Karl Popper 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: SHR status
On Sun, Oct 18, 2009 at 11:01:15AM -0700, abatrour wrote: I was wondering what the status of SHR is. I've been using android lately so I am not caught up as to the progress of SHR. I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. This way people would have a somewhat stable release in Testing to try out stuff Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Sun, Oct 18, 2009 at 9:49 PM, Michal Brzozowski ruso...@poczta.fmwrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? I would advice to go to the latest unstable from 6 of September! Cheers Tony ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
2009/10/18 Tony Berth tonybe...@googlemail.com: On Sun, Oct 18, 2009 at 9:49 PM, Michal Brzozowski ruso...@poczta.fm wrote: What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? I would advice to go to the latest unstable from 6 of September! If this is a known fixed problem, can anyone say if it was a frameworkd problem (= could also be the cause of sometimes missing incoming SMS in my debian/zhone setup) or a UI problem (= not)? Thanks, Neil ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
RE: SHR status
8b48b1570910181149v43786743ue18d3346c1298...@mail.gmail.com 3494db260910181157p39cfadcv55ef478b934a8...@mail.gmail.com Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'm using SHR Unstable as a daily phone. Has quirks=2C but IMHO SHR Testi= ng should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates= and I miss phone calls from time to time. Is there a new one that seems to= have reliable telephony? I would advice to go to the latest unstable from 6 of September! I would advice to stay away from the September release and stick to the Aug= ust one. It's a mess. For example: =20 - FR is ringing=2C but no screen to pick up - Answering second incomming call is still borked=2C despite some work on i= t - Incomming call during shutdown results in infinite loop of vibrating batt= ery and playing sound - Random crashes of phone log application - Phone refusing to suspend and keeps waking up after only a few seconds =20 I've been rebooting and removing the battery to get the phone back to its s= ences almost every day now. This did not happen with the August release. =20 My experience with the August release was a lot more stable.=20 =20 Niels. =20 _ Reageer op foto=92s van je vrienden en bekijk hun reacties op de jouwe. Geg= arandeerd hilariteit!=20 http://www.microsoft.com/belux/nl/windows/windowslive/products/photos.aspx= ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
On 10/18/09, Rui Miguel Silva Seabra r...@1407.org wrote: On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Rui ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- 09 F9 11 02 9D 74 E3 5B D8 41 56 C5 63 56 88 C0 ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
I'm running a build from August but last upgraded on Sept 5th and it's pretty stable. Had a few reports of bad audio quality, and a couple of times where I've missed calls but it's fairly rare. I spent a couple of weeks running the shr-testing candidate - which I believe was basically a copy of the Sept 15th build of shr-u, and it was a lot less stable. Warren On Sun, Oct 18, 2009 at 2:03 PM, Niels Heyvaert nielsheyva...@hotmail.comwrote: 8b48b1570910181149v43786743ue18d3346c1298...@mail.gmail.com 3494db260910181157p39cfadcv55ef478b934a8...@mail.gmail.com Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 I'm using SHR Unstable as a daily phone. Has quirks=2C but IMHO SHR Testi= ng should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates= and I miss phone calls from time to time. Is there a new one that seems to= have reliable telephony? I would advice to go to the latest unstable from 6 of September! I would advice to stay away from the September release and stick to the Aug= ust one. It's a mess. For example: =20 - FR is ringing=2C but no screen to pick up - Answering second incomming call is still borked=2C despite some work on i= t - Incomming call during shutdown results in infinite loop of vibrating batt= ery and playing sound - Random crashes of phone log application - Phone refusing to suspend and keeps waking up after only a few seconds =20 I've been rebooting and removing the battery to get the phone back to its s= ences almost every day now. This did not happen with the August release. =20 My experience with the August release was a lot more stable.=20 =20 Niels. =20 _ Reageer op foto=92s van je vrienden en bekijk hun reacties op de jouwe. Geg= arandeerd hilariteit!=20 http://www.microsoft.com/belux/nl/windows/windowslive/products/photos.aspx= ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
are you using the latest moko11 GSM firmware? - anything else and missed messages are a distinct possibility. http://wiki.openmoko.org/wiki/GSM/Flashing BillK On Sun, 2009-10-18 at 20:49 +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? ___ 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: SHR status
On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote: On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Rui Define reliable telephony as - at least as good as the cheap ~$au100 phones available from your local carrier. Freerunner: much less :( Billk ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: SHR status
I have personally had many troubles with SHR in the past. For one, I don't think the Contacts application has ever worked for my SIM card. It immediately crashes. It might be because it hasn't finished loading all of the contacts from SIM, but crashing is a poor way of handling this issue. Also, the lack of a true 'phone' UI seems to be missing the point (although Launcher does some to fix this). Another thing is that I don't enjoy the laggy graphics. Even by setting it to sw_16, it just looks tacky. Not a good decision to have to make. That being said, I find the custom Settings apps to be fantastic. The only thing that has never worked is the wifi connect stuff, and I think that it's a problem that everyone has. The illume themes are also very good on the eyes. I'm very impressed with the progress made so far. Overall, not for me. I tend to stick with QtMoko/H:1 for reliable phone service and stability. QtMoko's v14 is almost out of the 'getting it to work on the freerunner' stage and onto the 'lets make it a better OS overall' stage which shows the immense progress. H:1 is making huge advancements with their new rev5RC1. The only real issue with it is the lack of ringtone profiles and the wifi app is rather primitive (but you can load others, obviously). I think if you want to have a true 'reliable phone' you should head to one of the ones I just talked about. If you want to be a part of cutting edge phone development, with all of the quirks and caveats, then SHR is what you want. Now all we need is for Android-on-Freerunner to fix the glamo issue so it's not laggy and increase the sound quality of calls, and the Freerunner will be making its way to stardom. -Tonym W.Kenworthy wrote: On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote: On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Rui Define reliable telephony as - at least as good as the cheap ~$au100 phones available from your local carrier. Freerunner: much less :( Billk ___ 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: SHR status
One further hint - if you have any SD card problems, try slowing the SD clock down and/or adjusting the drive for it. I have an otherwise excellent 8G SD card (class 2 I think) that has to have the clock slowed - if not I get all sorts of corruption and weird things happening - with a slightly slower clock, its rock solid. Currently I am using a 16G class 4 card and that does not need a slow clock so YMMMV. Details are on the wiki. BillK On Mon, 2009-10-19 at 00:00 -0400, Tony McKeehan wrote: I have personally had many troubles with SHR in the past. For one, I don't think the Contacts application has ever worked for my SIM card. It immediately crashes. It might be because it hasn't finished loading all of the contacts from SIM, but crashing is a poor way of handling this issue. Also, the lack of a true 'phone' UI seems to be missing the point (although Launcher does some to fix this). Another thing is that I don't enjoy the laggy graphics. Even by setting it to sw_16, it just looks tacky. Not a good decision to have to make. That being said, I find the custom Settings apps to be fantastic. The only thing that has never worked is the wifi connect stuff, and I think that it's a problem that everyone has. The illume themes are also very good on the eyes. I'm very impressed with the progress made so far. Overall, not for me. I tend to stick with QtMoko/H:1 for reliable phone service and stability. QtMoko's v14 is almost out of the 'getting it to work on the freerunner' stage and onto the 'lets make it a better OS overall' stage which shows the immense progress. H:1 is making huge advancements with their new rev5RC1. The only real issue with it is the lack of ringtone profiles and the wifi app is rather primitive (but you can load others, obviously). I think if you want to have a true 'reliable phone' you should head to one of the ones I just talked about. If you want to be a part of cutting edge phone development, with all of the quirks and caveats, then SHR is what you want. Now all we need is for Android-on-Freerunner to fix the glamo issue so it's not laggy and increase the sound quality of calls, and the Freerunner will be making its way to stardom. -Tonym W.Kenworthy wrote: On Sun, 2009-10-18 at 21:46 +0100, Rui Miguel Silva Seabra wrote: On Sun, Oct 18, 2009 at 08:49:02PM +0200, Michal Brzozowski wrote: 2009/10/18 Rui Miguel Silva Seabra r...@1407.org I'm using SHR Unstable as a daily phone. Has quirks, but IMHO SHR Testing should become what SHR Unstable is right now before the next sync. What date is your SHR-u from? I'm using one from August with some updates and I miss phone calls from time to time. Is there a new one that seems to have reliable telephony? Current SHR Unstable. All updates applied. And define reliable telephone... More or less reliable than current testing? :) Rui Define reliable telephony as - at least as good as the cheap ~$au100 phones available from your local carrier. Freerunner: much less :( Billk ___ 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
