nDroid (TE) feedback thread

[Nistrod]

OK, I offer the following screen shots of an app I wrote to give me the screen parameters of various devices. One is a Desire, the other is a Nexus 4.
One thing that always got me was that on the Desire, a 25mm line is not the same length as a 160dp line - even though they should be. Depending on how you layout things, this used to bite me regularly. The Nexus 4 also has Xhigh density vs the High of the Desire.

Cheers

[ACTCMS]

One thing that always got me was that on the Desire, a 25mm line is not the same length as a 160dp line - even though they should be.

There have always been problems converting between mm and dpi...

Alex

[bgowland]

One thing that always got me was that on the Desire, a 25mm line is not the same length as a 160dp line - even though they should be.

Without wanting to take this thread too much in the direction of Android technicalities, they shouldn't be the same.

With a physical dpi of 254 in the x-axis and 480 physical pixels in width, the actual display width is 480/254 = ~1.89 inches or 48 millimetres. For normalisation purposes, a 480x800 hdpi screen (such as the Desire) is considered to have a width of 320dp (according to the Android docs at least). In that case, a line which is 160dp in length is half the screen width and should, therefore, be 24mm in length. If you want to take it further and use Pythagoras' Theorem, even though the Desire claims a diagonal screen size of 3.7 inches, it's actually ~3.67 inches.

This is a problem with Android as a whole and not specific devices - the fact that normalisation of all screens means compartmentalising to ldpi, mdpi, hdpi, xhdpi, tvdpi and small, normal, large and x-large means there is a whole load of fuzzy logic going on with potential overlaps depending on physical pixels, dpi and actual screen sizes in any given dimension. Attempting to work with absolute rather than logical characteristics when dealing with Android is a road to madness.

Getting back to the tabs issue though...the only reason I compared my Desire to what you're seeing on the Nexus 4 is I'm not actually doing anything with tab layout, sizing or the fonts used for any screen size or density. For some reason on the Desire the labels (Today, etc) are all spaced equally without multi-line problems - they just work. The fact we see problems on the Nexus 7 in portrait, your Nexus 4 and Alex's teblet suggests the common denominator is Android v4 or the support libraries I'm using so older Android versions can use the Action Bar.

I'll work it out (hopefully).

Cheers,
Brian

[ACTCMS]

Without With a physical dpi of 254 in the x-axis and 480 physical pixels in width, the actual display width is 480/254 = ~1.89 inches or 48 millimetres. For normalisation purposes, a 480x800 hdpi screen (such as the Desire) is considered to have a width of 320dp (according to the Android docs at least). In that case, a line which is 160dp in length is half the screen width and should, therefore, be 24mm in length. If you want to take it further and use Pythagoras' Theorem, even though the Desire claims a diagonal screen size of 3.7 inches, it's actually ~3.67 inches.

Exactly as I said here...

There have always been problems converting between mm and dpi...

Alex

[bgowland]

Exactly as I said here...

There have always been problems converting between mm and dpi...

Alex

Sorry I missed that the first time around - very droll.

[bgowland]

Todays shows are still starting at 10am (I am in UTC + 10). It is 13:55 and All Timeslots and Now / Next are correct.

Post the nDroidServiceHelper.log - I still can't work out why you're experiencing this. It might be when the epg files are being generated at the service end.

Cheers,
Brian

[Nistrod]

OK, today it is behaving itself.
I will check regularly and post if/when the problem occurs again.
Mmm, I did install 2.0.0 of the service.

[bgowland]

OK, today it is behaving itself.
I will check regularly and post if/when the problem occurs again.
Mmm, I did install 2.0.0 of the service.

I have made some changes in v2.0.0 of the service and some in v2.0.8 of the app (which I assume you've downloaded???). If that's the case, how is the ABC2 / ABC4 logo and also seven day tab titles?

[ACTCMS]

Is v2.0.0 intended to be targeted at .net4? I tried installing on XP which is up to .net3.5 and the installer wanted v4.

I then tried it on the new laptop (W7ProSP1 x64 with V4.5) and the installer threw an exception - see attached.

Alex

[bgowland]

Is v2.0.0 intended to be targeted at .net4? I tried installing on XP which is up to .net3.5 and the installer wanted v4.

Not just intended...it is built for .NET v4 (I even had to install VS2010 to do it...yuk).

I then tried it on the new laptop (W7ProSP1 x64 with V4.5) and the installer threw an exception - see attached.

Alex

OK, I've only tested it on my XP SP3 machine so maybe there is an x64 issue - I'll check.

Cheers,
Brian