Re: Sad Story
Although I do agree with you that I'm whining, I ask you can to a look at your own statements: 'Though not yet truly fixed', 'Usually', 'though it's not tackled' Let me say what I wanted to say: A phone would, should, must, work reliably every time. If there is a 'slight' chance of error, it would prove a liability. For example: Let us say that you were kidnapped by someone, and you wanted to make a 911 call, and the ALSA volume screwed up, or the GSM screwed up, then you wouldn't be looking forward to 'hack a fix' that night, would you? I hope and pray 'karma' doesn't take a toll on Openmoko devels. Yeah, If I were going to file it a ticket, it would be this: 'Make Openmoko work all the time, in all these scenarios'. I'm sure my ticket would be dismissed as being too 'general', but it represents a hole that all of us (as in Openmoko owners) feel. Forget my ticket, I check the Trac every week. I haven't even seen the Om2008.10 release out there yet, not all of it's issues are closed. Instead of blaming me for not filing a ticket, blame yourself for not closing all those other tickets yet. @Joel: See, when Openmoko's marketing department sells this phone as 'Free your phone', I'm sure they are referring to a 'phone' not a 'unstable but hackable computer'. If, there was a lawyer willing to take up these causes and whine on the owners' behalf, it would land Openmoko in class-action trouble, causing millions in litigation. Oh, there are lawyers who take up more frivolous lawsuits, and you know they win. Please refrain from saying that 'you got exactly what you paid for', or 'you weren't promised a thing'. See, Openmoko devels may not have themselves been responsible for this false marketing. But Openmoko as an organization includes everyone concerned (the devels). As a person representing Openmoko Inc, you should be responsible to your stakeholders. Including your customers. See, if everything you have made until now were fixed immediately, the community would benefit. And I speak for 1973 owners as well. You should have fixed the GTA02 months back, when you released it. Instead, you people are working on GTA03/Neo Whatever. It proves that you don't care about the community, You just care about the bunch of people who might want to buy your upcoming phones, who sponsor your own selfish causes and suffer while you are working on GTA04. I'm sick and tired of reflashing my phone every time, reconfiguring it every time, hoping it would 'all' work at one point of time. Why don't you do something about this instead? Joel Newkirk wrote: > If there's nothing YOU can do with the freerunner then it's just a > worthless paperweight - wanna sell it for $10? I might go to $20 if you > insist, it really is a pretty paperweight. > > > I'm sick of people whining like this. If you have a specific issue, raise > it, if you have a fix, post it. If you have general bitchiness send it to > /dev/null. The latest stable kernel version at kernel.org is 2.6.27.8, but > they're working on 2.6.28. Does that mean that "clearly... they didn't get > it right yet"? > > To state that "there is nothing you can do with the freerunner" is just a > sign of whininess, or lack of creativity or interest. I use mine daily as > a phone and a pocket computer, and nightly as a hobbyist project, and have > for several months. You don't need to be a programmer, but at this point > in the lifecycle of the FreeRunner you do really need an understanding of > Linux, or at least willingness and capability to learn. (at least if you > aspire to do more than place/receive calls, use GPS, send/receive SMS, etc > - the smartphone basics don't require linux-specific knowledge) > > My GPS works great. > > I've not had any GSM 'buzz' problems AFAIK. I've suffered from the GSM > echo problem which is now satisfactorily (though not perfectly) addressed, > and the 'bouncing Calypso' problem where GSM loses and regains > registration. (which is avoided lately - though not yet truly fixed - and > only apparently affects a portion of shipped units with particular GSM > firmware) > > Suspend and resume usually work fine. (qualified as 'usually' because I > frequently change rootfs, kernel and bootloader - and some combinations > thereof have problems) > > Oh, and I've had no problem with GPRS. At one point I was turning it on > and off via an icon, then I changed over to have it always-on or on-demand > - if not plugged into a host PC and wifi is down it 'just works'. Setting > this up this way requires some knowledge of linux, granted. But I found > Assisted-GPS and GPRS to work just fine back under 2008.8 with the > wiki-documented addition of a settings app that enabled/disabled GPRS, > Wifi, and AGPS. More recently frameworkd (FSO and SHR) has taken care of > AGPS and GPRS nicely, though it's not yet tackled wifi. > > AFAIK nobody here was promised a perfect fully-functional smartphone. If > they were, and wa
Re: Sad Story
On Fri, Dec 12, 2008 at 9:30 AM, W.Kenworthy wrote: > On Thu, 2008-12-11 at 22:20 -0500, Joel Newkirk wrote: > > If there's nothing YOU can do with the freerunner then it's just a > > > For me, I would love to be able to guarantee that I can receive SMS > messages with the same reliability as the cheapest phone on the market - > the FR cant do that and its not something I can fix. And thats a > constant problem for me. > > BillK Does not and tracking kernel make wake from suspend on sms arrival work reliably? My phone has been doing that for sometime now. Rakshat -- -- Please use Firefox as your web browser. Its protects you from spyware and is also a very feature rich browser. www.firefox.com ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
On Thu, 2008-12-11 at 22:20 -0500, Joel Newkirk wrote: > If there's nothing YOU can do with the freerunner then it's just a Joel do keep in mind you appear to be one of the lucky ones who has hit on a combination where the FR works to a standard you are happy with - not all of us (and I think thats a VERY large number of FR owners) are in your lucky circumstance. For me, I would love to be able to guarantee that I can receive SMS messages with the same reliability as the cheapest phone on the market - the FR cant do that and its not something I can fix. And thats a constant problem for me. BillK ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
If there's nothing YOU can do with the freerunner then it's just a worthless paperweight - wanna sell it for $10? I might go to $20 if you insist, it really is a pretty paperweight. I'm sick of people whining like this. If you have a specific issue, raise it, if you have a fix, post it. If you have general bitchiness send it to /dev/null. The latest stable kernel version at kernel.org is 2.6.27.8, but they're working on 2.6.28. Does that mean that "clearly... they didn't get it right yet"? To state that "there is nothing you can do with the freerunner" is just a sign of whininess, or lack of creativity or interest. I use mine daily as a phone and a pocket computer, and nightly as a hobbyist project, and have for several months. You don't need to be a programmer, but at this point in the lifecycle of the FreeRunner you do really need an understanding of Linux, or at least willingness and capability to learn. (at least if you aspire to do more than place/receive calls, use GPS, send/receive SMS, etc - the smartphone basics don't require linux-specific knowledge) My GPS works great. I've not had any GSM 'buzz' problems AFAIK. I've suffered from the GSM echo problem which is now satisfactorily (though not perfectly) addressed, and the 'bouncing Calypso' problem where GSM loses and regains registration. (which is avoided lately - though not yet truly fixed - and only apparently affects a portion of shipped units with particular GSM firmware) Suspend and resume usually work fine. (qualified as 'usually' because I frequently change rootfs, kernel and bootloader - and some combinations thereof have problems) Oh, and I've had no problem with GPRS. At one point I was turning it on and off via an icon, then I changed over to have it always-on or on-demand - if not plugged into a host PC and wifi is down it 'just works'. Setting this up this way requires some knowledge of linux, granted. But I found Assisted-GPS and GPRS to work just fine back under 2008.8 with the wiki-documented addition of a settings app that enabled/disabled GPRS, Wifi, and AGPS. More recently frameworkd (FSO and SHR) has taken care of AGPS and GPRS nicely, though it's not yet tackled wifi. AFAIK nobody here was promised a perfect fully-functional smartphone. If they were, and want to complain about it, talk to whomever made the promises. Most of us, at least, are here to participate in a community comprised in large part of developers who are finding new things to 'do' with the FreeRunner every day. We are ALL the 'they', though I read your post to use "they"="Openmoko". Did you happen to notice that Andy, the person to whom you replied, is "one of them"? In fact, the same Andy as referred to in the kernel mentioned, 2.6.28 "ANDY-tracking", which AIUI Andy has devoted quite a bit of time and effort to, making all the Openmoko-specific kernel bits work with a kernel version that's still not even "out", and is very distinctly a moving target, as the upstream source changes slightly on a frequent basis. Sorry if I've offended, but I really am getting tired of the frequent generalized complaints posted about 'it no work', 'it junk', etc. j On Thu, 11 Dec 2008 23:02:13 +0530, "Karthik Kumar" wrote: > Next week, not as of NOW. Clearly, the point was, they didn't get it > right yet. So unless they have actually done something, there is > nothing you can do with the freerunner. > > On Thu, Dec 11, 2008 at 10:14 PM, Andy Green wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Somebody in the thread at some point said: >> | Hi, >> | >> | For instance, the Openmoko GPS signal level is bummed because of a >> | hardware fault, also there are merely quirks to solve them. The >> >> ... which was worked around in kernel once the aggressor signal was >> identified. >> >> https://docs.openmoko.org/trac/ticket/1542#comment:27 >> >> | Openmoko battery discharging, suspend and resume have not been ironed >> | out fully yet. You would see these in _ANY_ basic phone out there. And >> | people have been giving commands to get the GPRS modem to work. You >> | see what I'm talking about? Nothing is connected, really. >> >> The problem with charger restarting is solved >> >> https://docs.openmoko.org/trac/ticket/1158#comment:33 >> >> and suspend and resume should be on a way more solid footing now on the >> 2.6.28-rc andy-tracking kernels. Starting next week the root >> filesystems will be adapted for these kernels and we start to provide >> packages for them. >> >> | Now, If you can't get to fix these today, how do u expect a person to >> | program it well enough to rescue it back? You can't expect everyone to >> | spend all their time getting their bare minimum phones to work, do >> | you? >> >> Well, three of the four things you mention are solved AFAIK. It leaves >> "people have been giving commands to get the GPRS modem to work"... it >> doesn't quite sound like the terrible thing that supports the general >> ar
Re: Neo due-2 - NG - last chance
Robin Paulson wrote: > > 2008/12/12 GreyCardinal : >> How? >> Please write steps >> >> r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * >> /sys/class/backlight/pcf50633-bl/brightness > > it's a text file; try: > > vi /sys/class/backlight/pcf50633-bl/brightness > > assuming you have vi installed > > if you don't know already how to use vi, you might want a vi manual to > hand before starting > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > r...@om-gta02:~# cat /sys/class/backlight/pcf50633-bl/brightness 63 -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1644925.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [SHR] linphone without /usr/bin/linphone
Al Johnson wrote: > On Tuesday 09 December 2008, Julien Cassignol wrote: >> On Tue, Dec 9, 2008 at 1:32 AM, Joachim Ott wrote: >>> Yes, this install the commandline client. And the graphical client? When >>> I click on the icon, it wants to execute linphone and not linphonec. >> None was built. Find a good one, or tell me what is the name of the bb >> recipe for a good not CLI client, and I'll build it :-) > > linphone is a good lightweight client, but the bb version is rather out of > date, and there's a dependency problem regarding libosip2 which needs to be a > 2.x version. And we don't get the GUI. Someone had a working linphone 2.x > with GUI, and patches to switch the alsa state for ringing and call pickup. I'm the one. I've also made some patches to make it more finger friendly but I've to finish my work before of putting something up... Unfortunately nowadays I'm also too busy to collect the src to put online... :| -- Treviño's World - Life and Linux http://www.3v1n0.net/ ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
2008/12/12 GreyCardinal : > How? > Please write steps > > r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * > /sys/class/backlight/pcf50633-bl/brightness it's a text file; try: vi /sys/class/backlight/pcf50633-bl/brightness assuming you have vi installed if you don't know already how to use vi, you might want a vi manual to hand before starting ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Neo due-2 - NG - last chance
j newkirk wrote: > > > How? Please write steps r...@om-gta02:~# ls /sys/class/backlight/pcf50633-bl/brightness * /sys/class/backlight/pcf50633-bl/brightness Applications: AlarmServer Qtopia qtmail Settings: PluginManager.conf.lock packages: picssounds r...@om-gta02:~# -- View this message in context: http://n2.nabble.com/Neo-due-2---NG---last-chance-tp1630257p1644575.html Sent from the Openmoko Support mailing list archive at Nabble.com. ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
It does make a good paper weight. On Thu, Dec 11, 2008 at 12:32 PM, Karthik Kumar wrote: > Next week, not as of NOW. Clearly, the point was, they didn't get it > right yet. So unless they have actually done something, there is > nothing you can do with the freerunner. > > On Thu, Dec 11, 2008 at 10:14 PM, Andy Green wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Somebody in the thread at some point said: >> | Hi, >> | >> | For instance, the Openmoko GPS signal level is bummed because of a >> | hardware fault, also there are merely quirks to solve them. The >> >> ... which was worked around in kernel once the aggressor signal was >> identified. >> >> https://docs.openmoko.org/trac/ticket/1542#comment:27 >> >> | Openmoko battery discharging, suspend and resume have not been ironed >> | out fully yet. You would see these in _ANY_ basic phone out there. And >> | people have been giving commands to get the GPRS modem to work. You >> | see what I'm talking about? Nothing is connected, really. >> >> The problem with charger restarting is solved >> >> https://docs.openmoko.org/trac/ticket/1158#comment:33 >> >> and suspend and resume should be on a way more solid footing now on the >> 2.6.28-rc andy-tracking kernels. Starting next week the root >> filesystems will be adapted for these kernels and we start to provide >> packages for them. >> >> | Now, If you can't get to fix these today, how do u expect a person to >> | program it well enough to rescue it back? You can't expect everyone to >> | spend all their time getting their bare minimum phones to work, do >> | you? >> >> Well, three of the four things you mention are solved AFAIK. It leaves >> "people have been giving commands to get the GPRS modem to work"... it >> doesn't quite sound like the terrible thing that supports the general >> argument you're making. >> >> - -Andy >> -BEGIN PGP SIGNATURE- >> Version: GnuPG v1.4.9 (GNU/Linux) >> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org >> >> iEYEARECAAYFAklBQ4oACgkQOjLpvpq7dMpMqwCeJRix5jq8OH4JHR9OZiy+ylQS >> KYIAnjwxIPRXmY/qiBsDF0yAXhg1AUIB >> =JLh7 >> -END PGP SIGNATURE- >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > > > > -- > Karthik > http://guilt.bafsoft.net > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Paul Email - pault...@gmail.com There were moments when he looked on evil simply as a mode through which he could realize his conception of the beautiful. Oscar Wilde - The Picture of Dorian Gray ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: |> 2.6.28-rc andy-tracking kernels. Starting next week the root |> filesystems will be adapted for these kernels and we start to provide |> packages for them. | Next week, not as of NOW. Clearly, the point was, they didn't get it | right yet. So unless they have actually done something, there is | nothing you can do with the freerunner. GPS stuff was done months ago... the other two are fixed now in 2.6.28-rc based kernels... and it'll filter through to our standard packages next week. Really: it's not a good basis for doom and gloom :-) - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklBUsoACgkQOjLpvpq7dMoIsgCghNmFTzXtFTX9fk5xUXi5qaj2 z+UAn0QuBNqicr56XqrUxIDEcv6HyP+m =Vb4z -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
Next week, not as of NOW. Clearly, the point was, they didn't get it right yet. So unless they have actually done something, there is nothing you can do with the freerunner. On Thu, Dec 11, 2008 at 10:14 PM, Andy Green wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Somebody in the thread at some point said: > | Hi, > | > | For instance, the Openmoko GPS signal level is bummed because of a > | hardware fault, also there are merely quirks to solve them. The > > ... which was worked around in kernel once the aggressor signal was > identified. > > https://docs.openmoko.org/trac/ticket/1542#comment:27 > > | Openmoko battery discharging, suspend and resume have not been ironed > | out fully yet. You would see these in _ANY_ basic phone out there. And > | people have been giving commands to get the GPRS modem to work. You > | see what I'm talking about? Nothing is connected, really. > > The problem with charger restarting is solved > > https://docs.openmoko.org/trac/ticket/1158#comment:33 > > and suspend and resume should be on a way more solid footing now on the > 2.6.28-rc andy-tracking kernels. Starting next week the root > filesystems will be adapted for these kernels and we start to provide > packages for them. > > | Now, If you can't get to fix these today, how do u expect a person to > | program it well enough to rescue it back? You can't expect everyone to > | spend all their time getting their bare minimum phones to work, do > | you? > > Well, three of the four things you mention are solved AFAIK. It leaves > "people have been giving commands to get the GPRS modem to work"... it > doesn't quite sound like the terrible thing that supports the general > argument you're making. > > - -Andy > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org > > iEYEARECAAYFAklBQ4oACgkQOjLpvpq7dMpMqwCeJRix5jq8OH4JHR9OZiy+ylQS > KYIAnjwxIPRXmY/qiBsDF0yAXhg1AUIB > =JLh7 > -END PGP SIGNATURE- > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > -- Karthik http://guilt.bafsoft.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
missing eth0
hello arne, sorry i am on the road with a html mail interface. if i look into the list archive and press reply the text of the original message is not included and i have to copy and insert it to the answer. at the bottom there is my original message of this thread. meanwhile i made a dmesg on both neos and they differ from each other. here the relevant parts. on the working neo: [8.39] sdio_wlan 00:01: driver attached [8.395000] sdio_wlan 00:01: SDIO device, IDs SD_0001 (active) on the not working neo: [3.535000] pnp: the driver 'sdio_wlan' has been registered it seems that driver is registered but the device is not being activated. on both neos uname -a is giving the same: Linux om-gta02 2.6.24 #1 PREEMPT Thu Nov 6 02:57:37 CST 2008 armv4tl unknown as i said before (first message) both neos are flashed with the same images and system from http://downloads.openmoko.org/releases/Om2008.9/ Om2008.9-gta02-20081106.uImage.bin Om2008.9-gta02-20081117.rootfs.jffs2 already with the "original" and delivered system Om 2007.2 (old stable) the wifi on the same neo did not work. anybody knows how to check if the wlan hardware is working or defect? thanks peter On Thu Dec 11 16:36:30 CET 2008, arne anka wrote: > please, always answer the last message! otherwise your messages are > completely out of context an there's no thread to follow. > sounds as if you (and your friend) use a monlithic kernel with the > > > module > built in. > to make sure, do > uname -a > and compare the kernel version number. > additionally you need to give the name of the distribution you are > > > using, > since i do not know where to find logs, maybe saying something useful. > > try > logread > or > dmesg On Thu, Dec 11, 2008 at 6:56 PM, peter boehm wrote: > hello list, > > i purchased a neo freerunner and flashed it successfully with > > Om2008.9-gta02-20081106.uImage.bin > Om2008.9-gta02-20081117.rootfs.jffs2 > > my problem is that the eth0 device (interface) is not present on the > system: > > # ls /sys/class/net/ > /sys/class/net/lo//sys/class/net/usb0/ > > therefore i am unable bring up the eth0 interface i.e: > > # /sbin/ifconfig eth0 up > ifconfig: SIOCGIFFLAGS: No such device > > on my friends device with the same system and kernel the eth0 interface > is brought up and we can see it in /sys/class/net/eth0/ and also it can > be brought up with the ifconfig command. > > any help would be appreciated > peter ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Somebody in the thread at some point said: | Hi, | | For instance, the Openmoko GPS signal level is bummed because of a | hardware fault, also there are merely quirks to solve them. The ... which was worked around in kernel once the aggressor signal was identified. https://docs.openmoko.org/trac/ticket/1542#comment:27 | Openmoko battery discharging, suspend and resume have not been ironed | out fully yet. You would see these in _ANY_ basic phone out there. And | people have been giving commands to get the GPRS modem to work. You | see what I'm talking about? Nothing is connected, really. The problem with charger restarting is solved https://docs.openmoko.org/trac/ticket/1158#comment:33 and suspend and resume should be on a way more solid footing now on the 2.6.28-rc andy-tracking kernels. Starting next week the root filesystems will be adapted for these kernels and we start to provide packages for them. | Now, If you can't get to fix these today, how do u expect a person to | program it well enough to rescue it back? You can't expect everyone to | spend all their time getting their bare minimum phones to work, do | you? Well, three of the four things you mention are solved AFAIK. It leaves "people have been giving commands to get the GPRS modem to work"... it doesn't quite sound like the terrible thing that supports the general argument you're making. - -Andy -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAklBQ4oACgkQOjLpvpq7dMpMqwCeJRix5jq8OH4JHR9OZiy+ylQS KYIAnjwxIPRXmY/qiBsDF0yAXhg1AUIB =JLh7 -END PGP SIGNATURE- ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: missing eth0
please, always answer the last message! otherwise your messages are completely out of context an there's no thread to follow. sounds as if you (and your friend) use a monlithic kernel with the module built in. to make sure, do uname -a and compare the kernel version number. additionally you need to give the name of the distribution you are using, since i do not know where to find logs, maybe saying something useful. try logread or dmesg ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
missing eth0
i moved this thread from [EMAIL PROTECTED] to here hello everybody | you better move that discussion to the support list. i opened the thread there | what does lsmod on the NOT working neo: # lsmod Module Size Used by ipv6 259684 8 on the working neo of my friend: $ lsmod Module Size Used by ipv6 259684 8 | say? is g_ether listed? not listed on both neos | what gives modprobe g_ether? on the NOT working: # /sbin/modprobe g_ether FATAL: Module g_ether not found. on the working: $ /sbin/modprobe g_ether FATAL: Module g_ether not found. | do a find /lib/modules -name g_ether\* | any results? nothing found on both neos thanks peter ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
Hi, For instance, the Openmoko GPS signal level is bummed because of a hardware fault, also there are merely quirks to solve them. The Openmoko battery discharging, suspend and resume have not been ironed out fully yet. You would see these in _ANY_ basic phone out there. And people have been giving commands to get the GPRS modem to work. You see what I'm talking about? Nothing is connected, really. Now, If you can't get to fix these today, how do u expect a person to program it well enough to rescue it back? You can't expect everyone to spend all their time getting their bare minimum phones to work, do you? -Karthik On Thu, Dec 11, 2008 at 5:35 PM, rakshat hooja <[EMAIL PROTECTED]> wrote: > > > On Thu, Dec 11, 2008 at 5:04 PM, Karthik Kumar <[EMAIL PROTECTED]> > wrote: >> >> One of the things I would like to say here is that if Openmoko had >> actually made the OS & hardware work pretty reliably, we might at >> least be able to program it for such things (protection and what not) >> >> Else it's just a matter of time before all Freerunners are stolen and >> nothing could be done about that. >> >> I wish Openmoko would release a stable version in gta02 than fiddle >> around with gta03. I suspect they should have done this to the owners >> of the neo1973 as well. >> > > I think Qtopia, FSO and SHR work well in Neo 1973 as well. And from what I > understand the same software will run on GTA02 and GTA03 > > Rakshat > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > > -- Karthik http://guilt.bafsoft.net ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
On Thu, Dec 11, 2008 at 5:04 PM, Karthik Kumar <[EMAIL PROTECTED]>wrote: > One of the things I would like to say here is that if Openmoko had > actually made the OS & hardware work pretty reliably, we might at > least be able to program it for such things (protection and what not) > > Else it's just a matter of time before all Freerunners are stolen and > nothing could be done about that. > > I wish Openmoko would release a stable version in gta02 than fiddle > around with gta03. I suspect they should have done this to the owners > of the neo1973 as well. > > I think Qtopia, FSO and SHR work well in Neo 1973 as well. And from what I understand the same software will run on GTA02 and GTA03 Rakshat ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
One of the things I would like to say here is that if Openmoko had actually made the OS & hardware work pretty reliably, we might at least be able to program it for such things (protection and what not) Else it's just a matter of time before all Freerunners are stolen and nothing could be done about that. I wish Openmoko would release a stable version in gta02 than fiddle around with gta03. I suspect they should have done this to the owners of the neo1973 as well. -Karthik On Thu, Dec 11, 2008 at 5:00 PM, Karthik Kumar <[EMAIL PROTECTED]> wrote: > I wouldn't worry about the robber coming home and beating you up for a > USB charger at all. It looks like many el-cheapo phones (<$60) come > with USB chargers and cables which also work with the Freerunner. That > makes it easier to steal the Freerunner though :( > > Keeping a poison-pill splash screen sounds like a great idea. Maybe > you could keep a screaming sound too (Help! I'm stolen) which can be > disabled if u quickly pressed some keys/parts of the screen when it > boots up. Of course, if you're lazy to do that, you could be in > trouble for stealing your own phone. > > On Thu, Dec 11, 2008 at 4:27 AM, Yorick Moko <[EMAIL PROTECTED]> wrote: >> since there is a mini-usb port the robber will be able to find it out; >> he'll probably beat you to death for wasting his time with something >> that vagely looks like like a phone but that he can't get to work as >> one even after tinkering with it for months :) >> >> On Wed, Dec 10, 2008 at 11:15 PM, Joachim Ott <[EMAIL PROTECTED]> wrote: >>> Putting your address on the splash screen could turn into a poison pill for >>> yourself. The robber could come to your house and beat you with a pair of >>> tennis shoes until you tell him where you have the charger. >>> >>> >>> >>> ___ >>> support mailing list >>> support@lists.openmoko.org >>> https://lists.openmoko.org/mailman/listinfo/support >>> >>> >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Sad Story
I wouldn't worry about the robber coming home and beating you up for a USB charger at all. It looks like many el-cheapo phones (<$60) come with USB chargers and cables which also work with the Freerunner. That makes it easier to steal the Freerunner though :( Keeping a poison-pill splash screen sounds like a great idea. Maybe you could keep a screaming sound too (Help! I'm stolen) which can be disabled if u quickly pressed some keys/parts of the screen when it boots up. Of course, if you're lazy to do that, you could be in trouble for stealing your own phone. On Thu, Dec 11, 2008 at 4:27 AM, Yorick Moko <[EMAIL PROTECTED]> wrote: > since there is a mini-usb port the robber will be able to find it out; > he'll probably beat you to death for wasting his time with something > that vagely looks like like a phone but that he can't get to work as > one even after tinkering with it for months :) > > On Wed, Dec 10, 2008 at 11:15 PM, Joachim Ott <[EMAIL PROTECTED]> wrote: >> Putting your address on the splash screen could turn into a poison pill for >> yourself. The robber could come to your house and beat you with a pair of >> tennis shoes until you tell him where you have the charger. >> >> >> >> ___ >> support mailing list >> support@lists.openmoko.org >> https://lists.openmoko.org/mailman/listinfo/support >> >> > > ___ > support mailing list > support@lists.openmoko.org > https://lists.openmoko.org/mailman/listinfo/support > ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
