Rockbox.org home
release
dev builds
extras
themes manual
wiki
device status forums
mailing lists
IRC bugs
patches
dev guide
translations



Rockbox mail archive

Subject: Re: Make iPod Nano 2G stable for 3.7?

Re: Make iPod Nano 2G stable for 3.7?

From: Michael Sparmann <theseven_at_gmx.net>
Date: Thu, 28 Oct 2010 10:05:26 +0200

Am 28.10.2010 09:56, schrieb Alex Parker:
> 6. There have been reports that the display contrast on at least one of
> the LCD types used in this series is worse than in the OF, making
> colours appear a bit greyish. As I don't have an affected device, I
> can't test or try to fix this.
>
>
> If it is readable so affected people can see to change the contrast,
> then not a blocker IMO.

Currently there's no LCD contrast setting, as we don't know the exact
types of the LCD and which registers to change. We just use the same
settings as the OF. The contrast problems are coming from a patch that
undervolts the LCD to 2.6V (instead of 3.0V) to prevent some awful noise
from the LCD and increase battery runtime. Even though the reason of the
noise is still not known (and I'm not experiencing it on my device), and
the battery life increase seems to be marginal on mine, people have been
in favor of this patch and it was committed.


> 7. There are still some patches in the queue, for example LCD sleep and
> hardware keyclick support, which would be nice to have but won't be
> committed for 3.7.
>
>
> Non-essential.

Still I'd like to see HW keyclick and that dynamic runtime estimation
patch committed one day, the latter at least for flash-based targets.
What's blocking those? Are they candidates for 3.8?


> 8. Before starting playback for the first time, the iPod seems to use a
> few mA more current than normal, probably because the Wolfson codec
> isn't initialized correctly yet. As this stops when PCM is started the
> first time, it shouldn't have a major impact on battery runtime.
>
>
> Not a blocker IMO.

I forgot to mention that there's also a quite noticable popping noise
when powering on the device, which is probably related. This is
apparently a bug in the driver of that Wolfson codec, we should have a
look at it after the release.
Is this also happening for other targets which use the same codec?


Received on 2010-10-28

Page template was last modified "Tue Sep 7 00:00:02 2021" The Rockbox Crew -- Privacy Policy