Re: T-Mobile with ASU on GTA01?
I'm everything but an expert (quite the contrary..) but maybe the programmers can learn something valuable from you if it works with some images and not with another, they might be able to identify (part) of the problem. It might be useful if you post some more information: (type of sim card, images that work, images that don't work) y On Fri, Jul 11, 2008 at 4:58 AM, Chris Hessing [EMAIL PROTECTED] wrote: So at the risk of starting this thread back up, why does my SIM work with two of the images, but not the others? Is it a difference in kernels? Some plumbing between the UI and the kernel? Or a UI issue? (Or all of the above?) Basically, can I flash the kernel from an image that worked, and a rootfs from one that didn't, and expect to have a working solution? If not, can someone help me understand where the issue is, so that I can take a look and see if I can get a working patch? Marcus Bauer wrote: On Wed, 2008-07-09 at 17:29 +0200, Michael 'Mickey' Lauer wrote: Am Mittwoch 09 Juli 2008 10:23:51 schrieb Marcus Bauer: This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. That is a very interesting engineering approach... Thanks for cutting my answer to make it look like I don't care. The investigation into the probelem simply stopped. If finding the solution is out of your abilites then simply forward the problem to somebody else. For heaven's sake, what is the key function of a mobile phone? Exactly, making calls. The cheapest phone you buy at your local vendor will do so. If you run into a hardware/firmware bug that prevents users from doing so, then forward the problem to somebody who can solve it. There was a even a mail from Erin concerning this subject: http://lists.openmoko.org/pipermail/community/2008-March/014122.html And one day you abandon the bug. You simply did not care. At least the test procedures would have needed to be adapted adequately to catch those phones. ___ 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: T-Mobile with ASU on GTA01?
So at the risk of starting this thread back up, why does my SIM work with two of the images, but not the others? Is it a difference in kernels? Some plumbing between the UI and the kernel? Or a UI issue? (Or all of the above?) Basically, can I flash the kernel from an image that worked, and a rootfs from one that didn't, and expect to have a working solution? If not, can someone help me understand where the issue is, so that I can take a look and see if I can get a working patch? Marcus Bauer wrote: On Wed, 2008-07-09 at 17:29 +0200, Michael 'Mickey' Lauer wrote: Am Mittwoch 09 Juli 2008 10:23:51 schrieb Marcus Bauer: This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. That is a very interesting engineering approach... Thanks for cutting my answer to make it look like I don't care. The investigation into the probelem simply stopped. If finding the solution is out of your abilites then simply forward the problem to somebody else. For heaven's sake, what is the key function of a mobile phone? Exactly, making calls. The cheapest phone you buy at your local vendor will do so. If you run into a hardware/firmware bug that prevents users from doing so, then forward the problem to somebody who can solve it. There was a even a mail from Erin concerning this subject: http://lists.openmoko.org/pipermail/community/2008-March/014122.html And one day you abandon the bug. You simply did not care. At least the test procedures would have needed to be adapted adequately to catch those phones. ___ 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: T-Mobile with ASU on GTA01?
ASU works basically, but getting telephony work with it is a matter of luck. Mostly it doesn't work at all, mostly the qtopia phoneserver eats 90% CPU.. On Wed, Jul 9, 2008 at 3:05 AM, steve [EMAIL PROTECTED] wrote: No ASU is a pre alpha set of applications. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Hessing Sent: Tuesday, July 08, 2008 4:19 PM To: List for Openmoko community discussion Subject: T-Mobile with ASU on GTA01? Hi all, Hopefully I get my terminology right. Late last year there were some issues with the T-Mobile SIMs and the GTA01. I got side-tracked on my GTA01 efforts and never sent my phone in for the firmware update. A few days ago I tried an OpenMoko build from late April, and found it worked with the T-Mo SIM. For fun, I also played with the FSO image, and had no problem. When I flashed a current ASU image (if my terminology is correct, the ASU image is the Qt/X11 image), it didn't work. The signal strength indication would change from time-to-time, but when I dialed it just said dialing, and the phone on the other end didn't ring. (There was also no indication that the phone had registered with the T-Mobile network.) Has anyone seen this? Should I even be expecting it to work? Thanks! ___ 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: T-Mobile with ASU on GTA01?
On Wed, 2008-07-09 at 09:25 +0200, thomasg wrote: ASU works basically, but getting telephony work with it is a matter of luck. Mostly it doesn't work at all, mostly the qtopia phoneserver eats 90% CPU.. You may have one of the broken GSM modems. From my four phones two have a broken GSM - that's 50%. They constantly reconnect to the cell tower and inbetween the can't make phone calls and loose the GPRS connection but without notifying the pppd. This is the same with the mature OM2007.2 images as well as with the professionally by Trolltech developed pure qtopia images, the ASU images the the new hyped FSO images. This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. That is a very interesting engineering approach... The bug in question is: http://docs.openmoko.org/trac/ticket/1024 The big problem with Openmoko is this not invented here mentality. The OM2007.2 images were working well, GTK is a valid platform for mobile gadgets (see Nokia N700, N800, N810), you can add bling (see clutter) and there is a huge developer base. The qtopia port to X adds a second huge developer base. But instead of going on and having a base for testing the hardware, there came this change to ASU and etk which probably 0.1% of Linux developers use. And despite what Lauer Co try to make us believe, this alienates GTK and qt developers. Just look on the planets of KDE and GNOME - nearly no mentionings. The developer mailing list: a big void. But the real problem here is that basically due to this reinventing the wheel with ASU nobody inside Openmoko has ever really used the phones thus plenty of things which could have come up simply got lost. If Sean, Wolfgang and Steve would have started to exclusivly eat their own dogfood, i.e. using the Neo as their daily phone, things like oszillating GSM modems, non working GPS, SIM cards, deep discharge batteries, noisy headsets would have been since long ironed out. Before now all the fanbois jump onto me and accuse me of trolling: in order to come to some lifestyle competitor of Apple the important thing is that the basics work and that they work reliably. Accepting brokeness as part of freedom is doing a disservice to the free software world. And it is even more unacceptable as there were 5000 people buying a Neo 1973 more or less for nothing. They all would have been more than happy to participate in advancing the Neo. The point being: the Neo *is* a fantastic concept. Bring it there. Stop ASU, concentrate on the basics, get the gtk and qt communities in. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
You surely are right in some points, you might even be right with the broken modem (still trying to figure that out), but I strongly disagree with you in the most other points (off topic, but I'll reply anyway). On Wed, Jul 9, 2008 at 10:23 AM, Marcus Bauer [EMAIL PROTECTED] You may have one of the broken GSM modems. From my four phones two have a broken GSM - that's 50%. My 1973 seems to be fine, I did calls with all images on the Freerunner, too, and can't tell what are software-problems and what not. They constantly reconnect to the cell tower and inbetween the can't make phone calls and loose the GPRS connection but without notifying the pppd. Can't confirm this for 100% of the cases, I did some calls on the 1973 over the last year, even ones with some minutes and it was fine. The main problem was the miserable sound quality. At least that seems to be hardware-fixed in GTA02. Didn't test much GPRS, but had no loss of connection yet. This is the same with the mature OM2007.2 images as well as with the professionally by Trolltech developed pure qtopia images, the ASU images the the new hyped FSO images. Imho the OM2007.2 images are all but mature. Even ASU is more predictable and reliable (except the Qtopia on X11 parts). Qtopia is ok, Qtopia on X11 is a mess and still not really working most of the time. This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. I wonder that I haven't heard of this yet, but let's hope they are figure it out and fix it. That is a very interesting engineering approach... :( The bug in question is: http://docs.openmoko.org/trac/ticket/1024 The big problem with Openmoko is this not invented here mentality. The OM2007.2 images were working well, GTK is a valid platform for mobile gadgets (see Nokia N700, N800, N810), you can add bling (see clutter) and there is a huge developer base. The qtopia port to X adds a second huge developer base. Like said before, they are (at least for me) all but working well (not even to mention the UI design with 2-color icons without ever knowing what they might mean). I don't see how GTK will bring the huge userbase. Nobody knew about EFL/ASU/FSO from the release of neo1973 until december, but there barely was any development. In my opinion the reason is, that there was no real API, mostly not even backends (except a messy GPSD and GSMD). The FSO-stack is what's needed to get that API and to get the developers. They don't want to have a 1-Toolkit-Strategy, they mostly want a nice stack to work with and use for their frontend what ever they want. Btw. - the main developer of the so called Underground realized that a year ago. The userbase of Nokias Internet Tablet Series is huge, but it looks for me as the developerbase isn't that big in relation, and that with a GTK-stack. Even Nokia bought Trolltech, and I bet they'll drop GTK eventually (and this is a huge sign, as GTK is LGPL and so much more interesting for commercial and closed source apps than Qtopia with GPL and commercial licenses!). They are paying the Trolltech folks now, and they are also paying EFL developers. Looks like the CAN see beyond their own nose. Qtopia doesn't add a huge developer base. Qtopia was used mainly in closed environments, there is no open source developerbase. Note that I talk about Qtopia, not about Qt. I like Qt as much I like GTK and I think both are really necessary on the Openmoko platform (as much as I dislike much parts of KDE and especially GNOME). The biggest project with the NIH-syndrom is definitely GNOME. They do _all_ from scratch, they'd never ever use anything that's not from them. Hell, I'm glad that there is FDO to coordinate between them and the (still imho) much less arrogant KDE people. The bling-argument with clutter can be just a joke, talking about a platform without OpenGL capable drivers (and for the coming device even without OpenGL capable hardware). But instead of going on and having a base for testing the hardware, there came this change to ASU and etk which probably 0.1% of Linux developers use. And despite what Lauer Co try to make us believe, this alienates GTK and qt developers. Just look on the planets of KDE and GNOME - nearly no mentionings. The developer mailing list: a big void. I don't see your point here (exepct that you are GTK- and maybe GNOME-developer and don't like other platforms). Etk behaves under Illume/Enlightenment just like GTK and Qt do. There's no difference at all. Nobody is forced to use Etk and nobody ever will. The difference is, that you can use what you want without to be forced to use something specifically (like Qtopia without X11). Im also glad, that it looks like there is no need for Evolution and GConf in future, I personally don't like them and don't want to be forced to use them.
Re: T-Mobile with ASU on GTA01?
Dear Marcus, your mail touches many subjects and let me just pick out a few: First of all thanks for buying 4 phones from us! We are still an 'Open Source project' more than a company and people need to believe in the bigger picture to buy from us now. Believe it or not - we all eat our own dog food. You cannot believe how many mails Steve wrote to me complaining about his broken/buggy/ unchargeable/etc. Neo. I admit that I am carrying two phones around with me, a Blackberry and a Neo. Want to replace the Blackberry but we are not there yet. dogfood, i.e. using the Neo as their daily phone, things like oszillating GSM modems, non working GPS, SIM cards, deep discharge batteries, noisy headsets would have been since long ironed out. Exactly our top priorities. I am amazed by how closely you are watching what's going on with Openmoko. Let me just clarify this: We are not (knowingly) shipping defective products. Our complete production testing software is under GPL now (http://git.openmoko.org/?p=system-test-suite.git;a=summary ) Every peripheral of every phone is tested in the factory. (BTW, we are trying to open this up more, with open factory statistics etc. But that's a long-term goal) So some people see bugs. All the things you list above. In certain situations, certain countries, with certain GSM base stations, certain SIM cards, etc. etc. And after months and months of improving the Neo, we decided to start shipping. Get more Neos out into real life, get more customer feedback. Because in the end that's the only thing that can really focus the whole company. Engineers are self-loving animals sometimes. Do not over-estimate the power Sean or me or Steve have over some of these guys. But when the mailing lists have people who paid money for their phones, everybody will listen. Openmoko is different, we do all this openly. If you want to return your two non-working phones, I'm sure we find a solution. We will absolutely make sure that you get two fully functioning phones in return. Hope this helps (a bit, I know you still have 2 phones with broken GSM as you say), keep us honest :-) Best Regards, Wolfgang On Jul 9, 2008, at 4:23 PM, Marcus Bauer wrote: On Wed, 2008-07-09 at 09:25 +0200, thomasg wrote: ASU works basically, but getting telephony work with it is a matter of luck. Mostly it doesn't work at all, mostly the qtopia phoneserver eats 90% CPU.. You may have one of the broken GSM modems. From my four phones two have a broken GSM - that's 50%. They constantly reconnect to the cell tower and inbetween the can't make phone calls and loose the GPRS connection but without notifying the pppd. This is the same with the mature OM2007.2 images as well as with the professionally by Trolltech developed pure qtopia images, the ASU images the the new hyped FSO images. This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. That is a very interesting engineering approach... The bug in question is: http://docs.openmoko.org/trac/ticket/1024 The big problem with Openmoko is this not invented here mentality. The OM2007.2 images were working well, GTK is a valid platform for mobile gadgets (see Nokia N700, N800, N810), you can add bling (see clutter) and there is a huge developer base. The qtopia port to X adds a second huge developer base. But instead of going on and having a base for testing the hardware, there came this change to ASU and etk which probably 0.1% of Linux developers use. And despite what Lauer Co try to make us believe, this alienates GTK and qt developers. Just look on the planets of KDE and GNOME - nearly no mentionings. The developer mailing list: a big void. But the real problem here is that basically due to this reinventing the wheel with ASU nobody inside Openmoko has ever really used the phones thus plenty of things which could have come up simply got lost. If Sean, Wolfgang and Steve would have started to exclusivly eat their own dogfood, i.e. using the Neo as their daily phone, things like oszillating GSM modems, non working GPS, SIM cards, deep discharge batteries, noisy headsets would have been since long ironed out. Before now all the fanbois jump onto me and accuse me of trolling: in order to come to some lifestyle competitor of Apple the important thing is that the basics work and that they work reliably. Accepting brokeness as part of freedom is doing a disservice to the free software world. And it is even more unacceptable as there were 5000 people buying a Neo 1973 more or less for nothing. They all would have been more than happy to participate in advancing the Neo. The point being: the Neo *is* a fantastic concept. Bring it there. Stop ASU, concentrate on the basics, get the
Re: T-Mobile with ASU on GTA01?
Am Mittwoch 09 Juli 2008 10:23:51 schrieb Marcus Bauer: This is another hardware problem which is shared with the Neo 1973 and thus known since a year. The answer by Dr. Michael Lauer was Guys, this is a Heisenbug. We pray that it does not occur too often in the field.. That is a very interesting engineering approach... Thanks for cutting my answer to make it look like I don't care. Guys, please visit the bug to see the full story. :M: ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
On Wed, 2008-07-09 at 16:38 +0200, thomasg wrote: Like said before, they are (at least for me) all but working well (not even to mention the UI design with 2-color icons without ever knowing what they might mean). Some of the icons are all but intuitive but this is a question of the icons and not of the toolkit. The FSO-stack is what's needed to get that API and to get the developers. The FSO-stack is another case of reinventing the wheel. It sounds nice on the paper but in reality this is a horror. There are PIM APIs like eds and whatever in the KDE world or qtopia is used. It took years for them to grow mature and nobody needs yet another API. The thing is that Michael Lauer massively dislikes C and needs everything reinvented in Python. C has its place in the embedded world as much as Python has. But again we cut a huge slice out of the developer base. The current work separation between gsmd and phone-kit is a very clever one, but again not invented here but at o-hand. There have been plenty of alternatives been offered for the current gsmd but they were all blocked out. And many of those people simply left. The userbase of Nokias Internet Tablet Series is huge, but it looks for me as the developerbase isn't that big in relation, and that with a GTK-stack. What makes you think this will be different with ETK? This means even less developers. Even Nokia bought Trolltech, and I bet they'll drop GTK eventually And shortly afterwards Nokia bought Symbian. They are not going to drop any of the three. They just do everything to put up a front against Google's Android. That's what they fear. They are paying the Trolltech folks now, and they are also paying EFL developers. Yes, there is a cool application for connecting the N800 to your car electronics and see into the engine management. The point being is that there are way less ETK developers than GTK developers or qt developers Again on the developers: they had nothing to work with. This is simply not true. It was just a lack of documentation. And I can't help it, but this has been deliberately blocked in order to pave the way for this ASU/FSO. Even developers from o-hand who developed for Openmoko in their freetime finally left the boat being completely disgusted by the fact of constantly running against walls. FSO with it's dbus-api will make this much easier IMHO this is just pure nonsense. I know that it has been repeated over and over again by Michael Lauer because it is his baby. It is one big pack that rather would be split in tiny packages. That makes development and debugging a lot easier. Moreover this will take another two years until it has some API stability. A huge API like this doesn't come overnight. Last not least: if you want to use your code in the future on a moblin device you are just doomed/trapped in an API that nobody else uses. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
They are paying the Trolltech folks now, and they are also paying EFL developers. Yes, there is a cool application for connecting the N800 to your car electronics and see into the engine management. Which one is that? (just googled up carman: http://openbossa.indt.org/carman/index.html, this one?) I already dropped a note about openmoko on openecu forum mentioning freerunner as a plausible platform to craft a nice mobile monitoring software for ECUs (via OBDII or smth better like Subaru select monitor interface). Unfortunately I don't know much about status of openmoko development, neither about ECU related software. Thus I couldn't suggest any plausible start point (besides mentioning RomRaider since I wasn't aware about carman or any other Maemo-based software) http://forums.openecu.org/viewtopic.php?t=3514 -- Yaroslav Halchenko Research Assistant, Psychology Department, Rutgers-Newark Student Ph.D. @ CS Dept. NJIT Office: (973) 353-5440x263 | FWD: 82823 | Fax: (973) 353-1171 101 Warren Str, Smith Hall, Rm 4-105, Newark NJ 07102 WWW: http://www.linkedin.com/in/yarik ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
The FSO-stack is what's needed to get that API and to get the developers. The FSO-stack is another case of reinventing the wheel. It sounds nice on the paper but in reality this is a horror. There are PIM APIs like eds and whatever in the KDE world or qtopia is used. It took years for them to grow mature and nobody needs yet another API. how far are they toolkit independent? ie do these apis work with gtk/etk/whatever or are they deeply integrated with kde/qtopia? The thing is that Michael Lauer massively dislikes C and needs everything reinvented in Python. C has its place in the embedded world as much as Python has. But again we cut a huge slice out of the developer base. well, you need somebody willing to put some effort into things -- and it helps, if you love it. This is simply not true. It was just a lack of documentation. And I can't help it, but this has been deliberately blocked in order to pave the way for this ASU/FSO. Even developers from o-hand who developed for Openmoko in their freetime finally left the boat being completely disgusted by the fact of constantly running against walls. i wouldn't know about that -- but as much as i would like you to ask for proof: i think it only will force this thread down the slope into a flame war which will solve nothing. FSO with it's dbus-api will make this much easier IMHO this is just pure nonsense. I know that it has been repeated over and over again by Michael Lauer because it is his baby. i think those argumenta ad personam aren't going anywhere. i don't know about past wars and fights and honestly -- i am not interested at all. so let's just skip the i don't like X because X likes Y part and come to something useful: - what makes you think fso will not solve anything (besides the already mentioned problem of maturity) - what toolkit agnostic apis are available Last not least: if you want to use your code in the future on a moblin device you are just doomed/trapped in an API that nobody else uses. well, what api do you see coming to be used on future moblin devices? as far as i can see both of the approaches (limo and google) are basically closed, exposing a careful selected window to the devices. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
Yaroslav Halchenko wrote: They are paying the Trolltech folks now, and they are also paying EFL developers. Yes, there is a cool application for connecting the N800 to your car electronics and see into the engine management. Which one is that? (just googled up carman: http://openbossa.indt.org/carman/index.html, this one?) Hehe, was just researching how much effort it would be to port to openmoko. Does not look too bad. It runs python and uses gtk or efl as frameworks. It heavily uses hildon stuff, but mot of them should be easily replaceable. I'm not going to do this in the next time. But it seems doable. What i did not check yet is how much their interface code depends on screen resolution. I expect very much. But regarding the small screen on openmoko, some redesign seems a good idea anyways... The nice thing would be that openmoko could provide accelerometer data and gps out of the box... -- Drucken Sie diese Mail bitte nur auf Recyclingpapier aus. Please print this mail only on recycled paper. ___ Openmoko community mailing list community@lists.openmoko.org http://lists.openmoko.org/mailman/listinfo/community
Re: T-Mobile with ASU on GTA01?
I've not used the ASU on a 1973, but I know I've never been able to place calls using the ASU on Freerunner and I use T-Mobile in the USA with the exception of the first image released. I've always assumed ASU just didn't work. On Tue, Jul 8, 2008 at 7:19 PM, Chris Hessing [EMAIL PROTECTED] wrote: Hi all, Hopefully I get my terminology right. Late last year there were some issues with the T-Mobile SIMs and the GTA01. I got side-tracked on my GTA01 efforts and never sent my phone in for the firmware update. A few days ago I tried an OpenMoko build from late April, and found it worked with the T-Mo SIM. For fun, I also played with the FSO image, and had no problem. When I flashed a current ASU image (if my terminology is correct, the ASU image is the Qt/X11 image), it didn't work. The signal strength indication would change from time-to-time, but when I dialed it just said dialing, and the phone on the other end didn't ring. (There was also no indication that the phone had registered with the T-Mobile network.) Has anyone seen this? Should I even be expecting it to work? Thanks! ___ 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: T-Mobile with ASU on GTA01?
ASU is pre alpha. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Kevin Dean Sent: Tuesday, July 08, 2008 5:10 PM To: List for Openmoko community discussion Subject: Re: T-Mobile with ASU on GTA01? I've not used the ASU on a 1973, but I know I've never been able to place calls using the ASU on Freerunner and I use T-Mobile in the USA with the exception of the first image released. I've always assumed ASU just didn't work. On Tue, Jul 8, 2008 at 7:19 PM, Chris Hessing [EMAIL PROTECTED] wrote: Hi all, Hopefully I get my terminology right. Late last year there were some issues with the T-Mobile SIMs and the GTA01. I got side-tracked on my GTA01 efforts and never sent my phone in for the firmware update. A few days ago I tried an OpenMoko build from late April, and found it worked with the T-Mo SIM. For fun, I also played with the FSO image, and had no problem. When I flashed a current ASU image (if my terminology is correct, the ASU image is the Qt/X11 image), it didn't work. The signal strength indication would change from time-to-time, but when I dialed it just said dialing, and the phone on the other end didn't ring. (There was also no indication that the phone had registered with the T-Mobile network.) Has anyone seen this? Should I even be expecting it to work? Thanks! ___ 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: T-Mobile with ASU on GTA01?
No ASU is a pre alpha set of applications. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Hessing Sent: Tuesday, July 08, 2008 4:19 PM To: List for Openmoko community discussion Subject: T-Mobile with ASU on GTA01? Hi all, Hopefully I get my terminology right. Late last year there were some issues with the T-Mobile SIMs and the GTA01. I got side-tracked on my GTA01 efforts and never sent my phone in for the firmware update. A few days ago I tried an OpenMoko build from late April, and found it worked with the T-Mo SIM. For fun, I also played with the FSO image, and had no problem. When I flashed a current ASU image (if my terminology is correct, the ASU image is the Qt/X11 image), it didn't work. The signal strength indication would change from time-to-time, but when I dialed it just said dialing, and the phone on the other end didn't ring. (There was also no indication that the phone had registered with the T-Mobile network.) Has anyone seen this? Should I even be expecting it to work? Thanks! ___ 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
