Rep: (738)
You can pull the shortcut of your favorites into the launcher in more or less relevant androids.



Rep: (738)
Intriguing news, bought at 625 was asked to pay up to 705. I wonder what will happen if you do not pay.



Rep: (738)
Chinesestarted to collectmoney for Pocket 2 Max.



Rep: (738)
* giz.sergion ,
In the pre-production review, such was not promised for sale.
But i5 and i7 in the Y-line are kind of crap, they differ from m3 only in frequencies. With equal tdp i7-8500ysuperior tom3-8100y as much as 15%. Perhaps, with better cooling in Max, the difference would be even a little more, but taking into account the difference in the price of devices from the same one mix - xs for whom these processors are.



Rep: (738)
Anguish @ 06/20/19, 16:45*
pocket and noisy and hot, not sure if p2 max will fix it

Fox posted a video today, says cold.
https://youtu.be/wH3n1vn64As



Rep: (738)
* Forbiddendnb ,
Sony, like Samsung, has a proprietary mechanism for systemic themes (and, it seems, there are no longer any in x3).
Those. their framework, when the application does not overwrite some parameter with its own theme and takes the system one, loads it from third place. Manufacturers have complete freedom of action here, they can make any changes to the framework (on the latest androids, however, the substrate works on the stock framework, apparently they added some api).

But system topics to the issue of applying the theme to an application from an external apk is nothing.

Post has been editeddci - 07.06.19, 11:45



Rep: (738)
* mcarrowlaw ,
If in a nutshell, an application can only use themes that are written in its own hml, the theme should have an id resource that the framework will look for in internal resources (herefor example, there is an explanation, I remember that I read somewhere a post on this topic from Diane Hekborn, but I’m too lazy to look for it).

Those. There is no way to pull up the topic from the external apk. There is no way to collect a theme in the code from some kind of flowers and wood chips.
If it would be possible, we would not have all this hemorrhoids with skin engines at all, write to yourself android themes and apply.



Rep: (738)
* mcarrowlaw ,
Neither this nor the question of prohibition or permission

In the case of a pop-up menu, this is a question of the feasibility of this task by means of skins in general. Changing the heading with the theme in the client in some other hard-coded colors is easy, but to do it all with code is not clear how. When this menu appeared in the main window from above around 5-6 of the android, there was a hack, now it is a separate dialogue created by the code of the framework, which complicates everything to an incomprehensible degree.

In the case of alerts, they are playtext now, there are no layouts, layouts, nothing of this, i.e. nothing to pull the colors and drovers.
Those. there is no prohibition, but there is no infrastructure for skins either.

* Displax ,
Yeah. The only use of the attribute, there was no code to support it.



Rep: (738)
* gar_alex ,
Yes, and jumped a couple of builds back, before that just did not work. : lol:

but it is the lesser of problems
With Legacy build, frankly, the main question is whether it will be able to hold out to the end of 1.9 or have to be forked from the main tree before.

We have, not counting the caliper and fcm, only two third-party libraries that have been at least api14 for several years.
For both of us, for this reason, we use ancient pre-revolutionary branches, both have compatibility problems and stupid bugs, both, being updated, will require serious adaptation of the code. At this point, it will be impossible to support Legacy build on the main branch, it will have to be forked into a separate tree and there will be further support for significant bugs and some easily portable features.

Most likely, this will happen at the moment of q appearance in the wild, most likely the minimum api of the main version will be raised to 16, since Google did it on its librariesHalf a year ago, and the rest quickly catch up.



Rep: (738)
* Locman 27 ,
Not which top, where the name of the topic, etc.



Rep: (738)
* Locman 27,
Cool. Here's another build. When it hangs - make a longtap on the title, it will collect and send the necessary info.

Attached files

Attached fileru.fourpda.client-1.9.6-p2.apk(3.38 MB)



Rep: (738)
* mcarrowlaw ,
Yes, it is, but it's hard to fix it, because It is impossible to use the system theme from the skin, and the pop-up element belongs to the framework ...



Rep: (738)
* Heraldist,
So it is described in briefthere.
A non-legacy build is assembled as it is, with current KFOR, gets into the market, etc.

Legacy build:
  1. Collected by old KFOR (25).
  2. Thanks to the old KFOR works in androids from 2.3.3 (normal build - starting from 4.0).
  3. Does not contain the FCM library, since It does not pass on the minimum version of the android.
  4. Thanks to the compatibility mode with old programs, in new androids (8.0 and older) it allows you to customize notifications "as before".
  5. In the play it can not be laid out.



Rep: (738)
* mcarrowlaw ,
In 1.9.6, there are no skins tasks left, i.e. everything should work, in theory.



Rep: (738)
* mcarrowlaw ,
1.9.6? Took the first one from the gallery.

Attached images
Attached Image



Rep: (738)
* Locman 27 ,
Hint, this build is different.



Rep: (738)
* Locman 27,
* mad_shaman
And what circumstances? Launched by hands and here it is, opened from the alert, return from the dialogue?
In any case, these are some races of two instances of the same activity, try this build.

Attached files

Attached fileru.fourpda.client-1.9.6-p1.apk(3.38 MB)


Post has been editeddci - 05.06.19, 17:56



Rep: (738)
* mcarrowlaw ,
Where exactly? It is used in several places.



Rep: (738)
* yampic,
It is in the skin. The client changes in this thread a little more.
Little
Attached Image


Remote CSLs are proxies, i.e. contain only one default state with a single color, they were used by the old mechanism to bypass the cache.
If these CSLs in the skin have not changed, then there is no need to delete them and edit the drawables, they are no longer used.



Of the bugs above, only one touched the skins themselves - the preview button, you need to correct itadd xml-ku.

Post has been editeddci - 05.06.19, 14:19



Rep: (738)
* -Kowalski- ,
If you get hurt, don’t bet, there’s always a mistake.

Post has been editeddci - 05.06.19, 12:41

Full version

Help     rules

Now: 08/11/19, 19:51