I would like to have some way to mark devices as CDD compatible or such,
but can't figure out a way to do this that the ROM builders wouldn't just
say they are.
On Sun, Jan 23, 2011 at 11:52 PM, Jonas Petersson jonas.peters...@xms.sewrote:
On 01/24/2011 08:31 AM, Zsolt Vasvari wrote:
On Jan
24.01.2011 10:52, Jonas Petersson пишет:
Been there too. Camera not returning images, Barcode scanner going
nuts, etc. When I see something wierd I typically ask then to download
my help-page - the http headers will often (but not always) hint when
you have the Frankenstein syndrome.
Yep,
24.01.2011 17:16, Brill Pappin пишет:
Funny you should say that. My Analytics are showing two Nokia N90
entries.
I started wondering if Nokia is playing around with Android or if
someone was hacking Nokia's to run it.
NITDroid - a port of Android for the Nokia internet tablets, including N900:
The M860 appears to be the CDMA twin brother of the UMTS-based U8230 (sold
in Russia, Ukraine, etc.)
The specs at link below say 320x480, 3.5 - a pretty typical HVGA (other
sites I'm not posting here also give the same numbers).
You can see it quite clearly in the screenshots, too:
On 01/23/2011 03:08 PM, kernelpanic wrote:
thanks - I found several other sites that disagree with the
manufacturer's site and state 320x480 as well.
The app was tested and works fine (according to a few other users) on
a Samsung Transform which is 320x455, so not sure why the claim that
it
Getting a little futher OT - I sometimes get comments from users of custom
firmware, in fact, at this point, issues are typically caused by
Frankenstein-like firmware (kernel from here, apps from there, WiFi and
radio drivers extracted from standard firmware, well, you get the idea).
I would
On 01/24/2011 08:31 AM, Zsolt Vasvari wrote:
On Jan 23, 10:46 pm, Kostya Vasilyevkmans...@gmail.com wrote:
Getting a little futher OT - I sometimes get comments from users of custom
firmware, in fact, at this point, issues are typically caused by
Frankenstein-like firmware (kernel from here,
It should be a child of manifest, so that is fine. Do you know what
device this was allowed to be installed on?
On Sat, Jan 22, 2011 at 2:47 PM, kernelpanic j.m.roya...@gmail.com wrote:
ok, thanks. According to the docs, it should just be in the manifest -
I have this
uses-sdk
Er 320x240 is definitely not HVGA. :}
On Sat, Jan 22, 2011 at 4:51 PM, kernelpanic j.m.roya...@gmail.com wrote:
looking at the Huawei website, it states that device is 320x240 HVGA
is the HVGA the issue here?
On Jan 22, 5:35 pm, kernelpanic j.m.roya...@gmail.com wrote:
yes, that's how I
This is all beside the point, but I am just saying that HVGA is by
definition 480x320. They have a mistake in their description. Anyway, in
the platform and elsewhere we don't care about HVGA or any other
resolution names at all, just the actually resolution width and height (and
of course
It would help a lot to find someone with a different QVGA device to see if
your app also shows up there. That will be a big step in isolating whether
this is device-specific problem or something more general.
On Sat, Jan 22, 2011 at 7:24 PM, kernelpanic j.m.roya...@gmail.com wrote:
like I
11 matches
Mail list logo
