Re: Problems with broken distro and AUX
Good luck. Let me know if you manage to fix it, 'cause I'm in a similar situation - my daughter dropped my FR and after that the AUX button doesn't work. I haven't gotten around to taking the case apart to see if it's an easy fix yet. Fortunately I have Qi install and I just manually rename boot partitions to determine which OS boots. So far it's generally working, but if I manage to seriously break a distro it could get interesting... Warren On Wed, Dec 9, 2009 at 1:29 AM, Maciej Piechotka uzytkown...@gmail.comwrote: Some time ago I broke my AUX button so I cannot access NAND/NOR bootloader. What worst some time after I broke distro during update and I cannot access neither by ssh nor by X11 (keyboard is not displayed). I will have an access to debug board in two weeks or I may ask someone but is it possible to somehow fix it (with or without debug board)? Regards ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Testing feeds
I saw in another thread that the OM2009 unstable tree was accidentally built in the testing dir - so they removed it rather than having people screw up their builds. I think testing 5 is supposed to be here in the next day or two... Warren On Thu, Jun 11, 2009 at 5:36 AM, tammaro pamdirac palombo pamm...@gmail.com wrote: I'm not sure but look at this page http://downloads.openmoko.org/repository/experimental/README.html On Thu, Jun 11, 2009 at 10:13 AM, David Fokkema dfokk...@ileos.nl wrote: Hi list, This morning, I tried an opkg update using Om2009, which uses the testing feeds. However, upon checking in my desktop browser (to rule out networking problems) I discovered that http://downloads.openmoko.org/repository/testing/ is completely empty. Any thoughts? Thanks, David ___ 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 -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Thanks, Joerg - I hadn't noticed that comment. Hmm - would it be possible to add a note at the top of the file itself indicating this? I found a post by you in the community list indicating that this was the 'real' state file to use, and so have been using it. I didn't think to check the comments on the associated issue. And frankly, my audio quality with it is better than with any of the other state files I've tried - much less buzz. Is it possible that the changes in the -a7 file reduce the impact of the buzz? I'm probably going to keep using it until I get the buzz fix operation performed. Warren On Tue, Jun 9, 2009 at 9:14 AM, Joerg Reisenweber jo...@openmoko.orgwrote: Am Mo 8. Juni 2009 schrieb Warren Baird: complained that I sounded a bit muffled, so I reset it to the 101 (same as gsmhandset-a7.state), and since then it seems pretty good - my wife has please notice: http://docs.openmoko.org/trac/ticket/2121#comment:3 gsmhandset-a7.state is deprecated! cheers jOERG -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [om2009-r4] Warren's Settings Worked for Me (was Re: Om2009 testing release 4)
Hi Joerg, I certainly don't mean to downplay the research you did - I was just trying to explain the experiences I've had. When I set control.5 to about 85 I no longer heard a buzz when I called myself on a phone - A few people complained that I sounded a bit muffled, so I reset it to the 101 (same as gsmhandset-a7.state), and since then it seems pretty good - my wife has complained once about some intermittent minor buzz, but I've had a number of phone conversations where people said I sounded fine. I've still seen varying opinions on these mailing lists ranging from 'only 5% of people need the buzz fix' to 'everyone with an A5 or A6 needs the buzz fix'. Is the official line that everyone with an A5 or A6 would benefit from the buzz fix? Warren On Mon, Jun 8, 2009 at 9:49 AM, Joerg Reisenweber jo...@openmoko.orgwrote: Warren said: I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. Another unconfirmed taletelling about Buzzfix by ALSA settings. Don't you think we checked this prior to coming up with a hw-rework after months and months of wrestling with this issue? /j ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I'm starting to think that this must be the case. I've always had people complain that they got a lot of static when they called me - I thought I had the buzz problem in fact. I just spent the time to figure out how to use alsamixer to tweak things, and if I set control.5 (Mono Playback Volume) to 83 from above 100 like I've seen in other gsmhandset.state files (ranging from 100 to 110 seems normal), I get a perfectly clear signal on the other end. I'll see if people now complain that I'm too quiet... but it's a lot better than the static. I'd suggest that *everyone* try out alsamixer - I just called my phone with a landline, and then fired it up alsamixer and experiemented with what alsamixer called 'Mono' until the static went away... Wish I'd figured that out months ago... Warren On Fri, May 29, 2009 at 8:45 PM, Petr Vanek van...@penguin.cz wrote: The link to the statefile produces a lot of static and echo. I've tweaked mine to a usable level. It is attached to this email. This file still needs work. Hmm.. interesting, I have no problems with it.. I wonder if the FR's are unique in this sense..? i can only speak for myself - we have to FRs in our family and yes they really are unique in this sense - one needed this state file tweaking to put volume lower, another to set volume up higher Petr ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I'm using TR4 - I had to tweak the gsmhandset.state file (as mentioned by someone else in a thread - I can't recall where right now - sorry). Without the tweak I was able to receive calls, but the audio quality was horrible - really bad background buzz. I am using u-boot - I upgraded it probably 6 months ago. Don't recall the version off-hand, but I can check if you need me to. Warren On Tue, May 26, 2009 at 11:16 AM, Chris Jenks ch...@jenks.us wrote: On Tue, 26 May 2009, Alexander Shulgin wrote: Finally it works for me after qi reflash. :) -- Alex I thought it was working too until I got a couple calls. The callers hung up after not being able to hear me at all. Isn't anyone else having this problem? I'm using the latest u-boot, kernel and root in testing, all dated May 21st, on a stock Freerunner, flashed to v11 of the GSM firmware. I suppose I can see if qi fixes it, but every time I try qi I get WSOD. Chris ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Best graphics performance?
'graphics performance' is a pretty broad category - can you share some details about what exactly you are trying to do? Are you interested in general UI response? blitting rasters to the screen? Rendered 2d vector stuff? 3d? FWIW, I've generally found that QTExtended feels a bit snappier to me than the X based distros under general use - although I haven't quantified that. Warren 2009/5/26 Sten Kvamme s...@kvamme.se Hi, What distro will give the best graphics performance? ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: Om2009 testing release 4
I didn't see the /var/cache issue, but I just installed on the sd card, rather than flashing. I can say that TR4 is definitely improved over TR3 - very impressive for such a short cycle. There's still a long way to go on the usability side. For example I still haven't figured out exactly where to click to get the option to call or sms someone from my address book - I just kinda blindly poke at the screen in the area above the dial-pad, and eventually the list shows up. I'm going to try using it as my phone for a couple of days, just to see how if I can stand using it instead of QtE... :-) Any info on importing contacts? if I'm going to use it as my daily phone, I'd like to be able to get my contacts in there... Warren On Fri, May 22, 2009 at 12:07 PM, Alexander Shulgin alex.shul...@gmail.comwrote: On Fri, May 22, 2009 at 6:24 PM, Chris Jenks ch...@jenks.us wrote: On Fri, 22 May 2009, Alexander Shulgin wrote: Hi, Just flashed the latest images and now I get this on boot: In: /var/cache: No space left on device (+ a few more, /var/lock among them) The phone boots up to om-gta02 login prompt. X doesn't start and usb networking doesn't work either. Tried to reformat uSD card, but this didn't help (didn't expect this to work, however). What can I do about the problem? Anyone else getting the same? -- Alex I didn't even notice the /var/cache problem (wasn't paying attention), and I haven't had any problem with the X server, but I can confirm the usb networking problem - I don't get a usb0 interface on my connected desktop as I did with the testing version from the 9th. Also, I tracked the problem down to the root image - the u-boot and kernel images, flashed back to the working images on the 9th, don't fix the problem. ... Oh, silly me. I just realized I didn't reflash the boot loader. Will try a bit later. -- Alex ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support -- Warren Baird - Photographer and Digital Artist http://www.synergisticimages.ca ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: [QT Extended Improved 20090316 snapbuild] Wake up from suspend on incoming call
Hmm - I haven't tried one of the QT 4.4.3 builds yet, but I've been running a 4.4.2 build for many months and it resumes fine, and (unlike 2008.X) resumes quickly enough that I can actually answer my calls. I did see some discussion on the list about kernel logging levels impacting the speed of resume - I'm not sure that it impacts whether the resume happens at all. Good luck. Warren On Mon, Mar 16, 2009 at 12:53 PM, Ian darkstarsw...@gmail.com wrote: This is the same issue that made me dismiss Qtopia earlier on but frustrated with every other available distro I decided to see if it had been solved yet: QT Extended won't resume from suspend on an incoming call (possibly SMS as well), it will only respond to the event if it is already on. If it was suspended it believes that it is receiving the event when it is later turned on, likely well after the event. Is this why the default setting is not to suspend? Is there another power saving work around (such as replacing the lock program with something that forces the display to remain off until a physical button is pressed, a call received or so forth)? I haven't tested it extensively yet (freshly flashed... again), but how are other users dealing with the lack of decent power management (carry a second battery, charger or USB cable?), or am I missing something obvious? Cheers, -I -- http://darkstarshout.blogspot.com/ -- On the day *I* go to work for Microsoft, faint oinking sounds will be heard from far overhead, the moon will not merely turn blue but develop polkadots, and hell will freeze over so solid the brimstone will go superconductive. -- Erik Raymond, 2005 -- Please avoid sending me Word or PowerPoint attachments. See http://www.gnu.org/philosophy/no-word-attachments.html ___ 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: Experiences with GTA02 and OM2008.12 (was part of the Brick thread)
Hey Craig, Unfortunately your experience matches pretty well the experience I had with the OM2008.8 distro. I switched to QtE 4.4.2 when it came out, and have had a much better experience - I haven't encountered missed calls or SMSs. The only tweaking I did was to turn on suspend in the power managment UI, and to disable the speakerphone alsa config, since it seemed to be causing feedback on occasion. The downside of QtE is that you can't take advantage of all the cool X based software people are putting together. I'm a bit disappointed by your report, though - I had kinda hoped that 2008.12 was making progress If you do experiment with SHR let me know how it goes - the reports I've heard with it sound good... And I definitely agree with your comment about open source devices --- I've used linux for a long time, and I do expect to have to fiddle with it a bit to get the config right initially - but then I expect rock solid performance - not missed calls and texts and having to reboot all the time. I don't think that's an unreasonable expectation. QtE comes pretty close - but I'd love to find an X based distro that also does... Warren On Sat, Jan 17, 2009 at 6:31 AM, Craig Woodward wo...@rochester.rr.comwrote: First off, I want to thank Tom for the blog pages he has setup. They're a great reference for setting up the OM base software, and really should be put on the main Wiki release pages somewhere. I'd say the out-of-box functionality of most of the OM releases is highly enhanced if you follow the directions he's posted. Tom Yates madhat...@teaparty.net wrote: On Wed, 7 Jan 2009, Craig Woodward wrote: And core functionality on ALL Neos, like making and receiving calls and SMS, is still unreliable. i'm sorry, but i think that's unfair; my GTA02A6 has been my main phone since i bought it at the end of august 2008. you may never have been able to make things work for you, but it's wrong to say that core functionality on all neos is unreliable; it's fine on mine. Really? Your main phone? On my Neo, applying the same patches you note on your blog, core functionality is NOT reliable. I write device drivers, firmware, SDKs, and applications for a living, so it's not like this is new stuff for me. Try as I may, I can't get this phone to be a phone. And really, I shouldn't have to patch and tweak an image from my phone's manufacture to get base functionality, like making and receiving calls reliably. To be fair before giving up on it, I tried loading up 2008.12 last weekend. This weekend I plan on trying the latest of a couple other releases, like SHR and Android. I even used your blog (which is really a great setup walk though) and a couple other references to get things up and running quickly. At first I was very hopeful and inspired by the improvements I saw since the last OM release I tried (which was admittedly 2008.8). In particular I found that some of the interface was more polished. GRPS setup and usage was MUCH more solid than in the past. In fact, GPRS is now probably the most stable sub system I've used on the FreeRunner. Even suspend seemed to be working with test calls I did from my office phone early on. I did find some annoying bugs in interface still: email not working, SMS not using contact info, etc. But I figured those are user-space problems, which can be fixed later. Polish wasn't my main concern... base functionality was my focus. The first night the phone ran over night and didn't crash, which was great. I used GPS Wifi in the morning, and it worked well. Finally, I tried making a call and it crashed, lost network, and refused to get signal again. After a reboot it registered fine, and my outbound call went well. I hoped it was a glitch from being on almost 12 hours, and went in to work. At work, I got a call but was not able to answer it. The answer button on the screen would highlight, but the phone just keep ringing. A reboot and a call back worked. An hour later I got a call and was able to answer, but the person on the other end couldn't hear me. A reboot again fixed it. Later that day the phone rang half a ring, and went right to the dialog that tells me I'd missed the call. The caller later told me it rang several more times than usual before going to voice mail. Repeat for the next day or so... Of about 15 calls I know about over the two days I was using my Neo, 9 answered as expected. Only one outbound call had an issue out of about 8. Not a very good rate for a phone. Near the end of day one, it dawned on me that I *never* got notification that I had waiting voice mail, which comes as a text message from my provider. In fact, I discovered (over several reboots) that I'd missed most inbound text messages. And despite my phone saying text messages were being sent, only 14 of about 26 actually made it to the carrier, based on reports from friends AND my
Re: battery on Qtopia 4.4.2
Salut Francois, I'm also using QtE 4.4.2, and I get something more than 48 hours of battery. I think the trick is enabling suspend - I think it's off by default - if you go into settings, select 'Power Management', and make sure that something reasonble is set for the suspend timeout - I have mine set as 20s to dim, 30s to display off, and 40s to suspend. The big difference with QtE vs. the 2008.X distro's I've used is that the phone unsuspends quickly enough that you can reliably answer incoming calls - when I was using the 2008.X based distros I regularly missed calls... Hope this helps. Warren On Wed, Jan 14, 2009 at 12:01 AM, François de Ryckel f.deryc...@gmail.comwrote: Hi everyone, The lifespan of a battery charge on my FR is no more than one night. Anything one can do about it? I'm a newbie in the Opemoko community - I'm a linux user since a few year but definetely not a computer geek! I'm just a big opensource software user fan - so go easy with the explanations :) Thanks in advance for your help. Francois ___ 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: 4.4.2 quick feedback, was: Re: QT Extended version 4.4.2 release is out!
2008/11/3 Jaroslav Reznik [EMAIL PROTECTED] Hi all! As I have read this thread and tried 4.4.2 by myself, it looks like every new release is more and more buggy :( QtE guys took bad example from OpenMoko developers :( Well, as I found out recently, there's really only *one* QtE guy when it comes to FR support... I also thought it had more broad support on the FR within the QT group, but it's just Lorn working on the QtE port to the FR. I think more community testing is a great idea - However, I suspect that a lot of the instabilities and bugs people are seeing are actually due to the underlying kernel, which I believe is the one provide by OM... Warren ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Re: 4.4.2 quick feedback, was: Re: QT Extended version 4.4.2 release is out!
On Fri, Oct 31, 2008 at 10:01 AM, Quasar [EMAIL PROTECTED] wrote: - There are some issues with the suspend/resume. I tried calling my phone after it suspended and it didn't wake up. - It's a minor issue but when the phone starts up, the battery indicator shows it's charging (it wasn't), this stopped once I connected the phone to the charger then removed it. I haven't seen the charging issue, but I also see the suspend/resume issues --- I just installed 4.4.2 this afternoon, and I've let the phone sit long enough to suspend 3 times now. Twice it woke up when I called it, and once it didn't. Not a great average. It hasn't woken up for SMS messages at all - and since I used google calendar with sms notification as my mobile calendaring solution - that's a pretty big issue. I'm going to continue testing over the weekend and see what else I see, but so far it seems like a step backwards compared to 4.4.1 :-( Warren ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
Phone failing to dial out or answer
[I sent this to the mailing list from a different account about a week ago - but I just checked the archives, and it looks like it never showed up - which would explain the lack of response. Hopefully I'll have better luck this time] Hi all, twice in the last week I've seen a rather nasty behaviour of my FR - it got into a mode where I could dial-out or receive calls, but without any real warning until I tried to dial-out or I actually received a call. The behaviour was that I would attempt to dial a call, and I'd get to the normal 'dialing'screen, and the number would appear with 'Dialing' underneath it, and it'd just sit there - no audio, nothing. I let it sit for quite a while, and nothing ever happened. The second time this happened I was near a landline, and when I tried calling my #, the FR showed an incoming call, but when I tried to answer it, it wouldn't answer, and I just saw another incoming call, and when I tried to answer that, yet another incoming call, etc. The first time I ended up rebooting 3 or 4 times before it started working, the second time it started working properly after a single reboot. The first time it happened I was running an FDOM build from mid Sept, and the second time I was running QT Extended, so it doesn't seem to be distro dependent. Unfortunately I wasn't near a computer I could log into from either time, so I don't have logs. anyone know what could cause this? Is it a know issue, or should I open a bug? Any workarounds or ways to avoid it? Is it valuable to open a bug without logs? I must admit this doesn't give me a lot of confidence in using the FR as a phone. I was late making a relatively important business call, since I couldn't dial out without rebooting the phone, which isn't exactly a quick option... Warren ___ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support
