Re: Lagging ambient light sensor and display backlight in N900
Dawid Lorenz writes: > I've recently noticed that switching display back on after moving phone away > from ear is preceded with considerable amount of lag, which makes every > in-call interaction with device (hang up call, select a digit, switch > speaker etc.) quite troublesome. I'm not sure what caused this, as I have an > impression it used to work better before and display was getting back on > quite quickly. > > Does anyone suffer from similar problem and have a clue how to improve that? > Are there any ambient light sensor settings hidden somewhere deep under /etc > or similar? I've noticed it and find it very aggravating (in addition to the cases you mention, there is the "see who's on call waiting" case). Would love to know if there is a solution. I can't recall if it used to be better, though. -- -John Sullivan -http://wjsullivan.net ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Searching in the app manager
Andre Klapper writes: > Hi, > > Am Mittwoch, den 09.06.2010, 17:07 +0100 schrieb Bernard Tyers: >> There used to be a handy function in the app manager to search. >> Has it moved? It used to be in App Manager->Download->Click on >> Application Manager top bar and find "search". > > It was removed in favor of "search as you type". I don't understand why one replaces the other. It would be nice to have both. (Also, sure would be nice if the arrow keys scrolled the listings in the app manager...) -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: Upgrade to PR 1.2 gone wrong
Alejandro López writes: > operation). When the moment for the reboot came, the problems started: > my N900 would start booting never asking for the security code, and > when starting to show the desktop, it would reboot; and the loop > started again. It was impossible to power it off except by removing > the battery. I had the same experience, with the reboot loop at the same point, after doing apt-get dist-upgrade (which I did because the app manager was telling me I needed to use the proprietary Windows Nokia software suite). I ended up flashing it, and restoring my settings/apps from backup, and it seems to be working fine now. -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
Re: N900: Git / symlink weirdness on ext3 sd card?
chombee writes: > On Mon, Mar 15, 2010 at 11:06:32AM -0700, John Sullivan wrote: >> I have my micro-sd card formatted as ext3. On that card, I have a git >> repository. In that git repository, I have some symlinks. On other >> computers with the same repository, the symlinks are symlinks. On the >> N900 however, the symlinks have become just files, whose only content is >> the name of the file they are supposed to target. So, "foo" should be a >> symlink to "bar". But instead, "foo" is a file with contents "bar". > > But that's exactly what a symlink is, isn't it? I think git has > committed the symlinks themselves into your repo, rather than the > files that the symlinks link to. That is what git does by > default, iirc. > Not sure what you mean by that, but the checkout of the same git repo works as expected (as in, the symlinks are symlinks) on other systems. -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
N900: Git / symlink weirdness on ext3 sd card?
I have my micro-sd card formatted as ext3. On that card, I have a git repository. In that git repository, I have some symlinks. On other computers with the same repository, the symlinks are symlinks. On the N900 however, the symlinks have become just files, whose only content is the name of the file they are supposed to target. So, "foo" should be a symlink to "bar". But instead, "foo" is a file with contents "bar". git status shows everything as normal -- it does not think anything has been modified or is weird. git reset --hard HEAD does not change anything. The filesystem does not appear to be otherwise corrupted. Any ideas what the heck is going on here? -- -John Sullivan -http://wjsullivan.net -GPG Key: AE8600B6 ___ maemo-users mailing list maemo-users@maemo.org https://lists.maemo.org/mailman/listinfo/maemo-users
