Release date | 1.9.19 / 1.9.18 beta



Rep: (1941)
Hey.

Thanks to our brave testers, the first public release did come out, a strange and unexpected time "after the release" came.
If you suddenly missed the link - here it is:
https: //play.google.co…s? id = ru.fourpda.client

In addition to other strange consequences, this means that normal people now havemore or lessnormal version to use, and we have now a separate channel in the beta that you can put the ill-conceived and unfinished features.
If you are brave in heart and deeply convinced that the use of an unfinished functional that will appear, annoy, change, and even disappear at times, does not hurt you, but you are already used to writing bug reports, you can join the testing here:
https: //play.google.co…ting/ru.fourpda.client

A stable version will be released every two to four weeks, or even more often if a bug requires urgent correction. Beta will come out on the same schedule once or twice a week.

In this thread, all versions will continue to be posted, both stable and beta. They will appear here a few hours before the GP. Not because we love this theme more, just a GP slow.
If you put the program from GP - it will be silently updated when the time comes. If you put the APK-shku hands, then it will show the notification, as in the good old days.

Current stable version:
Setup file1.9.19
Changelog

Current beta version:
Setup file1.9.18
Changelog


Useful links:
Actual release
Customer discussion
Bugtracker(information about errors found)
Wishes(tips and tricks for the development of the application)
FAQ on client functionality

Thank you for your participation.

Post-release text
As many of you have noticed, version 1.2.0 appeared on Google Play a few days ago.
What does this mean for all of us and for this topic?
  1. We consider version 1.2.0 as usable by the general public.
  2. Stable versions will be posted on Google Play, the minor version of which (the second digit in the version) has an even number as a value.
  3. The stable version will receive one feature update between two weeks and a month and, if necessary, a technical release with bugfixes.
  4. The stable version will not receive notification of updates from this topic, it will be updated only through Play.
  5. In this topic, we will continue to upload beta versions, the minor version of which is odd, they will come out as before, one or two a week, they will also receive a notification as before, in the form of toast in the application.



Text on open beta time
Hey.

Today we are launching an open testing mobile client.savagemessiahzine.comfor Android. The application has already passed closed testing. Thanks to “Friendssavagemessiahzine.com”Many bugs were fixed, but the client still has the status of“ beta ”, which means that there is still a lot of work ahead. We ask you to treat this with understanding.
We need your help in order to quickly identify errors and make the application even more stable and convenient.


Setup file1.3.0
Changelog


Along the way, we will answer several global questions that were somehow formulated during closed testing.

Q. Will you even finish something or release it and throw it away?
A. Until a stable release, work will go on continuously, that is, every working day. We plan to build assemblies once every few days, at least once a week.

Q. Why such a terrible design, where is the material?
A. We believe that the current design is rather laconic and allows to implement the entire planned set of functions. In other words, first the function, and then the design. Some specific suggestions for improving usability and navigation, we are happy to consider inwishes, but the options "to remake everything strictly according to the guidelines" do not need to be offered, it is impossible.

Q. Will you do what you are asked about?
A. Of course. Write your ideas inwishes, well, or vote in the same place for other people's ideas (or against).

Q. Will you do everything you are asked about?
A. Of course not. It's all pragmatic, the maximum demand for a minimum of man-hours. What they don’t vote for or what to do for a very long time will be done last.

Q. Will there be an app in google play?
A. Will be after exiting beta status.

Useful links:

Actual release
Customer discussion
Bugtracker(information about errors found)
Wishes(tips and tricks for the development of the application)
FAQ on client functionality

Thank you for your participation.


Text on closed beta time

Hello!

We continue our inconspicuous beta testing, and here is the link -version 1.0.0 ( go to hell give me the file ).

Along the way, we want to answer several global questions that were somehow formulated in the topics of this section.

Q. Will you even finish something or release it and throw it away?
A. Until a stable release, work will go on continuously, that is, every working day. We plan to lay out assemblies once every few days, at least once a week, except for the next two weeks, when we will not lay out anything. But this week we will give another one.

Q. Why such a terrible design, where is the material?
A. We believe that the current design, despite its brevity, is sufficient to implement all the planned functionality. In other words - first functional, and then design. Some specific suggestions for improving usability and navigation, we are happy to consider inwishes, but the options "to plow everything strictly according to the guidelines" we will postpone to the after-release.

Q. Will you do what you are asked about?
A. Of course. Write your ideas inwishes, well, or vote in the same place for other people's ideas (or against).

Q. Will you do everything you are asked about?
A. Of course not. It's all pragmatic, the maximum demand for a minimum of man-hours. What they don’t vote for or what to do for a very long time will be done last.

Q. Why are you hiding in the sub-forum, where is the announcement?
A. So far, the audience growth rate is more than enough for us. We want to get rid of at least the most critical acute angles before the rain from the reports pours on us.

And we have a smallFunctional FAQ!

Thanks for your help!

Original text
Hello!

Today, we decided to quietly begin a relatively public beta test of our mobile application without any announcement.
Here we would write what it was for us it was a long way, we call it beta 'cause it betta' than nothin ', but in short, here is the file:

Attached fileEn.FourPDA-Aligned.apk(5.86 MB)



So far this section is visible only to Friends.savagemessiahzine.comand groups above, and only these strong-willed people will miss the inexorable login form in the application.

The form in the application will work as the first two feedback channels (menu of the main page ->feedback), andbugtrackerIn the near future, we will also come up with something with wishes.
Yes, the crashes are automatically assembled, if you, of course, have not removed the corresponding checkbox in the settings (we beg, do not remove!), But if you still stumble upon a crash, fill the mold in the bag tracker - it will be much more convenient to fix it.

And, dear users, of course, the application lacks themes, lacks closer integration with other installed applications and many other important aspects, which we, of course, will add, but at the moment we want to test the infrastructure under a load comparable to the combat one, and at the same time give you a relatively full-featured product, so do not rush immediately to look for something missing, we know that much.

That's all. Tomorrow we will most likely hang an announcement, breathing life into this section, but for now - early access only for the most observant. :)


Post has been editeddci - 13.04.20, 16:35
Reason for editing: 01/09/19



Rep: (1941)
Application version1.8.0 beta from 2018.3.26


Attached fileru.fourpda.client-1.8.0.apk(3.21 MB)


Hello again.

In this presumably short beta, we will test the following potentially buggy changes:
  • To bypass the deadlock in the NIO of some versions of the android, we had to rewrite several critical pieces of code in the network part. If your connection is “hanging”, especially when uploading files, check, most likely this problem no longer exists. If you do not hang anything - hold on, maybe a couple of bugs in the new code, we still have to fix it.
  • Attaching attachments in QMS. We do not yet know how it will look as a result, most likely it will not be possible to load all types of files and they will be stored for a limited time, but for now, you can simply attach files.
  • Slightly flipped interface. A little more standard classes and animations, much less crutches. From the differences in use - the bookmarks with the main one cannot be svaypom, the left menu is pulled out only from the edge of the screen. Over the course of this beta, the flip will continue.
  • A dozen more minor changes (any number of attached images are hidden, several changes in skins, all sorts of typos and bugs) that are shallow for beta, but which are also relevant.


As always with the first beta build, we will turn on the update notification tomorrow, so as not to surprise too large audiences with unexpected bugs.



Rep: (1941)
Application version1.8.1 beta from 2018.3.27


Attached fileru.fourpda.client-1.8.1.apk(3.21 MB)


Fixed:
  • Drop in user menu.
  • No handling of clicking on file attachments in QMS.
  • Lack of context menu attachments in QMS.
  • Incorrect behavior of bookmark shortcuts in the left menu.
  • Climbing scroll bar in the left menu.



Rep: (1941)
Application version1.8.2 beta from 2018.3.28


Attached fileru.fourpda.client-1.8.2_p1.apk(3.21 MB)


Changes:
  • Added the ability to view the user's votes in the reputation of other users (in the reputation history of the "As Voted" menu).
  • The keyboard hides when opening the left menu.
  • Fixed fast scroll buttons processing.
  • Fixed incorrect sorting of skins in rare cases.
  • Fixed the error of applying the skin to ActionMode in QMS and editing the post.
  • Fixed other minor bugs and typos.



Rep: (1941)
Application version1.8.3 beta from 2018.4.10


Attached fileru.fourpda.client-1.8.3_p2.apk(3.21 MB)


Changes:
  • Added the ability to complain about the reputation and comments of the site.
  • Fixed bugs.




Build updated at 17:08, fixed a rare hangup. If you do not see problems - you can not update.

Post has been editedsavagemessiahzine.com - 10.04.18, 15:08



Rep: (1941)
Application version1.8.4 beta from 2018.4.10


Attached fileru.fourpda.client-1.8.4_p1.apk(3.21 MB)


Fast fix to fresh sync error in 1.8.3.
Day Fails. Defective build re-laid.

Post has been editedsavagemessiahzine.com - 10.04.18, 19:09



Rep: (1941)
Application version1.8.5 beta from 2018.4.27


Attached fileru.fourpda.client-1.8.5.apk(3.21 MB)


A dozen small fixes.
If there are no serious problems in this build, the next one will be stable.



Rep: (1941)
Application version1.8.6 stable from 2018.5.24


Attached fileru.fourpda.client-1.8.6.apk(3.21 MB)


Stable 1.8.



Rep: (1941)
Application version1.8.7 beta dated 2018.10.08


Attached fileru.fourpda.client-1.8.7.apk(3.22 MB)


Update the stable a bit before launching the beta.

Changes:
  • Added the ability to change the login.
  • The post editor is again used for complaints.
  • Changed the logic of transitions to posts, now the client will go to the topic in which the post was, even if it was permanently deleted (previous versions also received part of the functionality, but only for temporarily hidden posts).
  • Added a hint in the post editor that you can scroll through the tag strip.
  • Fixed other minor bugs and typos.





Rep: (1941)
Application version1.8.8 stable from 2018.12.10


Attached fileru.fourpda.client-1.8.8.apk(3.25 MB)


Changes:
  • In the gallery of skins, keywords appeared that allow filtering of skins according to one or another feature (as long as there are few, more - more).
  • On Oreo and above, the alerts are divided into channels, the sound and vibration settings for each channel are in the application properties in the system settings (there is a transition in the application settings).
  • On Oreo and above, silent mode is removed (this is a forced change due to Google Play policy).
  • The tag bar scroll indicator is replaced by a scrollbar.
  • Added quotes in QMS.
  • Hidden text is now block (with title and frame).
  • There will be a point regarding curators, stay tuned.
  • Fixed bugs.





Rep: (1941)
Application version1.8.10 stable dated 2018.12.13


Attached fileru.fourpda.client-1.8.10.apk(3.24 MB)


If you have Oreo (8) or Pie (9) and you have already been updated this week, download the file with a browser, not a client, otherwise, you will most likely have difficulty installing.

Changes (including 1.8.9):
  • Information about supervised topics in the profile.
  • More sorting options for favorites.
  • Indicator for typing a message and sending a file to QMS.
  • Confirmation of gluing the last posts.
  • The list of hashtags in the gallery is by default collapsed to three lines.
  • When downloading apk to Oreo and above, the client asks permission to install files if such permission has not been obtained earlier (without it, the downloaded file will not open from the curtain).
  • Alerts on Oreo and above could not work, now they should.
  • Fixed a bug with hanging (especially) the gallery of skins and / or the connection as a whole.
  • Other bugs fixed.





Rep: (1941)
Application version1.8.11 stable dated 2018.12.21


Attached fileru.fourpda.client-1.8.11.apk(3.4 MB)


Changes:
  • Added color to the group "Curators".
  • Curators can combine posts.
  • Incompatible skins are no longer displayed in the gallery if they are not installed.
  • Fixed several minor problems with tags (anchor is not visible, hide reduces the size, code does not show a one-word parameter, attachment is not displayed if there is no file).
  • Fixed processing of incorrect links to reputation.
  • Fixed a bug with square brackets in the list of supervised topics.
  • Fixed a bug due to which FourpdaJobService could remain in memory and lead to increased battery consumption (who watched - check, please, unsubscribe).
  • Added basic FCM support. If you do not receive notifications in the background, you can try to enable FCM in the "Background Event Checker" setting. Please note, this is the initial implementation, incl. server part, it can work in different ways. Also note that on OnePlus phones this approach alsomay not workwithoutadditional actions.
  • APK in releases will now be two. The main one that you see in this release will be assembled by the current SDK with the current target (in this release 28/26, from 1.9 - 28/28), it will support those operating systems that are supported in the current SDK, at the moment - starting with API 14 (Android 4.0). Also, legacy APK, SDK and target will be 25 from the next build, it will not have FCM, notification channels and, probably, some other future OS-oriented functionality.





Rep: (1941)
Application version1.8.12 stable from 2018.12.28


Attached fileru.fourpda.client-1.8.12-26.apk(3.4 MB)

Legacy APK (Android 2.3.x, 3.x)


Changes:
  • Bugfixes on the background mode.
  • From this version going Legacy APK.





Rep: (1941)
Application version1.8.13 stable from 2019.01.10


Attached fileru.fourpda.client-1.8.13-26.apk(3.4 MB)

Legacy APK (Android 2.3.x, 3.x)


Changes:
  • Error correction.





Rep: (1941)
Application version1.8.14 stable from 2019.01.24


Attached fileru.fourpda.client-1.8.14.apk(3.4 MB)

Legacy APK (Android 2.3.x, 3.x)


Changes:
  • Editing polls (in the subject three points ->Edit).
  • Initial saving of search settings (settings are saved depending on the type of page from which the search is opened).
  • Delete your messages in the QMS for the interlocutor within 48 hours after writing.
  • Improved support for FCM on devices that do not have startService whitelist, setting is marked as beta.
  • Correction of other errors.





Rep: (1941)
Application version1.8.15 stable from 2019.05.16


Attached fileru.fourpda.client-1.8.15.apk(3.34 MB)

Legacy APK (Android 2.3.x, 3.x)


Since the main commit planned for this release has become too voluminous, we will put it in a new beta next week.
In the meantime, update the stable, a lot of patches have accumulated.

Changes:
  • Added support for response templates in themes (release).
  • Fixed a lot of bugs.





Rep: (1941)
Application version1.9.0 beta from 2019.05.28


Attached fileru.fourpda.client-1.9.0.apk(3.39 MB)

Legacy APK (Android 2.3.x, 3.x)


Hello.

To this beta, we have accumulated three serious problems with various mechanisms that do not work as intended. Each of them is too large to be called a bug, because requires a thorough processing of the appropriate mechanism, under the spoilers, I will briefly describe each of them with a small technical background, and alternately in the following builds they will be solved:
  1. Notifications
    Notifications initially worked fine, but they were gnawed badly by the war for power consumption and, as a result, the inability for applications to perform tasks in the background at predictable times.

    Even more complicated the features of branded energy saving (for example, the removal of the assigned Job, inoperabilitydocumented whitelistetc.), which resulted in an unacceptable percentage of devices on which the delivery of notifications became random.

    So we replaced the entire old notification system, which was tied to individual APIs for each object and therefore needed to connect to the server, unified update information and now it can be delivered in various ways, including the body of FCM messages.

    Now FCM is selected by default during installation, all notifications should arrive with no more than a 15-second delay and the application processes them without connecting to the server. Periodic synchronization in this mode still remains (once every 40 minutes, in the next release it will be once every 60 minutes) for backup.

  2. Skins
    In Android, as you know, there is no built-in mechanism that allows, at the price of acceptable effort and compact local code, to replace application resources with others external to it. Partly for such a role is suitable mechanism for those, but it does not work with external resources at all.

    Historically, the skin mechanism in the client was made an override of the getResources context method (this is legal) and an override of hidden methods of the returned object (and this is legal), with which the framework loads colors, images and other resources. Thus, one small class got the opportunity to decide which resource to load, built-in (as usual) or external (if the skin is turned on), and the layout and the rest of the code practically didn’t depend on, happy end.

    That is, no. In this scheme there is one small nuance, the intercepting code somehow needs to be addressed further to the framework / OS, but these methods are hidden. It is good that it is easy to get around with the help of reflex (and now it is illegal).
    Starting from API28 / Pie for picking up the frameworkput sanctionsIn the case of the described mechanism, for now the line in the log or, if debugging is available, the message is on the screen, but for the next android it will all stop working.

    Work on a less convenient and productive, but a legitimate solution comes to an end and will be in the next build.

  3. Bookmarks
    Bookmarks were conceived as a simple short list of daily used links, but statistics show that we were mistaken.

    People store up to several thousand lines and this causes a number of problems:
    First, for the application, bookmarks are settings. A bad decision, but for a short list it will go, for a big one there are so many drawbacks in it that this is a disaster.
    Secondly, bookmarks are synchronized all together, which takes a lot of time and leads to the loss of this information, especially if the synchronization was turned off before in the settings.
    Third, it is not clear why live like this and how to look for something in this volume.

    Therefore, firstly, storage in a normal database, secondly line-by-line synchronization, thirdly - daddies. This will be a bit further on beta.


In this build, commit on the first issue.
Replacing the notification system included alteration of event handling in general, so pay attention, please, if something is not updated automatically when it should, or it is updated when it should not.

As always with the first beta build, we will turn on the update notification tomorrow, so as not to surprise too large audiences with unexpected bugs.



Rep: (1941)
Application version1.9.1 beta from 2019.05.28


Attached fileru.fourpda.client-1.9.1.apk(3.39 MB)

Legacy APK (Android 2.3.x, 3.x)


Oops! Immediately bug fixes for the three most evil bugs.



Rep: (1941)
Application version1.9.2 beta from 2019.05.29


Attached fileru.fourpda.client-1.9.2.apk(3.39 MB)

Legacy APK (Android 2.3.x, 3.x)


More bug fixes.
  • The "back" button in the Pie was not processed.
  • Group notifications ignored other notification settings.
  • Another ten small.



Rep: (1941)
Application version1.9.3 beta from 2019.05.30


Attached fileru.fourpda.client-1.9.3.apk(3.39 MB)

Legacy APK (Android 2.3.x, 3.x)


Cross out:
  • Several server synchronization errors (incorrect counters, repeated notifications, unreadable references).
  • Group notifications are not hidden, even if everything is read.
  • A page with an open editor could automatically update; A page with an open editor could be reused when you click on an alert.
  • Fall in a releaser.



Rep: (1941)
Application version1.9.4 beta on 2019.06.04


Attached fileru.fourpda.client-1.9.4.apk(3.38 MB)

Legacy APK (Android 2.3.x, 3.x)


  • Fixed several minor bugs synchronization alerts.
  • A new mechanism for the use of skins.


Full version    

Help     rules

Now: 04/22/20 at 11:22 AM