Hello! Checked the application on different devices. Everything was ok, well, in some places there are some nuances, but on the whole everything is fine. And so, as they say, the seeker found :)

1st Sony Xperia E-dual

Everything works, except for one. In the status bar, there is a notification of the program, on click on which the main activation of the application should come out - this is how it happens on other devices. So on Sonya there is, so to speak, an "additional" feature :). The program works in the background, the status bar notification. Now!! If you swing the device in any direction, then an event similar to the click on the notification occurs, and, accordingly, the main activation of the application pops up to the foreground. As I understand it, it works the device position sensor in space, but from which .... its event is obtained equivalent to the click event on the notification ?? Who can tell what is happening and how to overcome?

2nd HTC desire.

There is a complete nightmare. Graphics all becomes a curve. Well, this is how it can be overcome = But, on the other hand, half of the application's functionality related to access to the database and telephony management refuses to work. It's just some kind of nightmare, what kind of apparatus is this ??? Here is the question - are there as close as possible emulators of this device that can be cut to the Eclipse, where can I get them? :) For the phone itself is not for me and there is no possibility to work with it directly.

  • OSes on the device are the same? - Water Snake
  • that on a son that on httz 4th android. Before that I checked both on the 2nd and the 4th on various other devices including full knowards from Keta ... there are nuances everywhere, but not critical. In general, performance remains. The very .opa is on the httz, where in general one can say the prog refuses to breathe ... for starters at least with Sonya, it’s up to you to figure out what's behind the canoe from the sensor .... - Demon051
  • @ Demon051 4th is about nothing. For Kitkat (4.4) there are major changes in telephony and access to the database. Take the trouble, bro, to give a specific version ... - Barmaley
  • At httz I can say for sure 4.0.3 on a son only by evening I can find out. sad
  • the graphics have gotten out for one simple reason (I would like to see a screenshot, of course). It collects graphics and layouts from different directories. Most likely, for HTC desire, a specific layout (not the one you expect) is selected. At one time I had a similar problem (on googleTV) - I decided simply - I picked up the correct parameters (dimensions / resolution) in the emulator, achieved the effect and then "highlighted the layouts" - that is, made it so that the same type of layouts and pictures were slightly different and one could distinguish them. But with Sony ... can a person have a user buggy launcher? - KoVadim

1 answer 1

It is difficult to say what the reason is ... Most likely what comes to mind can be:

  1. The assembly is made under the older version of Android, and you have somewhere used API functions not available under earlier versions. Rebuild under the version of Android with the lowest API level - it usually helps.
  2. According to the graph - best practice - how to create an application supported by different permissions.
  3. It is possible that images with hard-coded resolutions or indents / layouts are used as UI elements. The first sign that something is wrong with you if absolute values ​​like android:size=10px are used in the layouts android:size=10px - px is non-kosher, either dp or sp

It is also useful to try to play with Android Compatibility Test Suite

  • I collect with instructions targedapi 7. This is android 2.1. It works on the target platform and above without problems - except for the described case. No super graphics. Standard layouts, regular png. No px. In general, right now, even more interested in what kind of event from the sensor to Sony, causing the output of the main activation of the application. - Demon051
  • Specifying target is not enough. Much more important under which version of the SDK do you build? - Barmaley
  • In the manifest targetSdkVersion = 7, which also corresponds to 2.1. In the project itself, true support or v4 does. This is just to support the notifications builder ... Or am I again not talking about that? :) On Sonya 4.1.1 android. Right now I tried another device with 4.1.1 - everything plows without problems. Your deeds are wonderful .. - Demon051
  • @ Demon051 But not about this! Under which version of the Android SDK you collect! Not targetSdk , but android.jar from which version of the SDK clings ?! Or do you not know what it is? To thrive - the developers have gone ... - Barmaley
  • By the way, the support caliper also depends on the Android SDK version, but it’s already too difficult to go :)) - Barmaley