[X]Assistant

[DoktorBOB]

The program does not start
Version: 0.8.1

Updated
The program after launch creates a folder attached to the post in the directorysdcard / Android / dataand next time the screen does not load further.
If you delete it, the program starts and creates the files again.

P.S. file deletioncache.dbin this folder it helps, you see, he is the culprit

Date: 12/04/2015

Attached files

Ru.FourPDA.zip(1003 bytes)


Post has been editedDoktorBOB - 04.12.15, 10:58

[i81]

I, too, it happens - it weighs on a black screen with the inscriptionsavagemessiahzine.combut it helps me to close the application.

[maxx-com]

i81,
The same trouble. Hanging on the welcome screen. The application may crash with an error.

[DoktorBOB]

i81, maxx-com, unfortunately, restarting does not help me, I have to clean the cache constantly

[Kiborg_Man]

There is a problem too. I post the adb log of a successful launch, but with some strange error:log1.txt(5.84 KB)

This adb log after completion with an error:log2.txt(483.9 KB)


It happens on such a hangup the device is rebooted, I will try to reproduce and update the post.
It was possible to reproduce the problem here is the log:log3.txt(490.81 KB)


Post has been editedKiborg_Man - 04.12.15, 20:55

[simorg13]

I confirm. Today faced the same problem.
In order for the client to start, you have to wait for the error "The application does not respond. Close?", I click yes, after that the client starts up normally.
Upd.Just wrote, as it stopped helping. The client does not start at all.
Upd2Deleting the cache.db file helps.

Post has been editedsimorg13 - 04.12.15, 22:59

Reason for editing: Upd & Upd2

[Scipilev]

After the client crashes (0.8.2), when restarting

maxx-com @ 12/04/15, 19:52

Hanging on the welcome screen. The application may crash with an error.

And it comes only from the fifth time, but this is only on my Android 4.4.x. On Android 5+ it seems to be stable, at least there was not one departure

[DoktorBOB]

simorg13,in fact, you can just clean the cache, and I painted the files for developers)) By the way, I sometimes run a second time, and have not found the correctness
Scipilevi have 5 android

Just now I read about the update, installed 0.8.2,it seems to startlags again

Post has been editedDoktorBOB - 07.12.15, 12:17

[Gnomeblack]

0.8.2. Periodically after a couple of hours of non-use, when you try to start the client hangs on the welcome screen. It is necessary to complete manually. After the restart, as a rule, it turns out that there are new messages in QMS, no notification of which was present - which means that the background process also hung. The same was observed in 0.8.1.

Posted 12/05/2015 12:49 PM:

About the same thing is described here:Customer Discussion (Post Brock_UA # 45051604)- two posts in a row.

[simorg13]

[email protected], 14:45

Periodically after a couple of hours of non-use

I may not start after a couple of minutes of not using :(

[kljovyj]

It happened several times when I started up, and I also noticed that after rebooting the phone, the program does not start up by starting up the messages until you start it manually.

Post has been editedkljovyj - 05.12.15, 15:56

[Skwo]

Gnomeblack,
I support, the last two versions are so accurate with the background process trouble ... there is enough memory in the phone, but something goes wrong ...
kljovyj,
and yes, autorun is also lame in both legs.

Post has been editedSkwo - 05.12.15, 23:35

[Gnomeblack]

[email protected], 10:52

My connection for some reason chops

I and another kind person from the forum often noticed that if the grid conditions are not very good, and the client is turned on, the connection is cut down. Tested on two Note 4 and one Note Edge. Hedgehog even reflash - I thought, you never know what the problem is. It does not start immediately, but the longer the client works, the worse the situation. But they did not create a separate topic in the bugtracker, since no logs, no coherent information.

[Snow volf]

GnomeBlack @ 06.12.15, 17:27

if the grid conditions are not very good, and the client is turned on, the connection is cut down.

The same rubbish, while the client from memory you will not unload. I checked on 3 devices, (signatures) Everywhere so. That's just how to report it, without any idea at all.

[Gnomeblack]

Snow Volf,I do not know. Too lengthy and rigorous research is needed, because the networks work for us, then that way, and while you take into account all the components, in order to determine the exact culprit, you will spend a month. I have removed the client from the main ringing telephone.

[Rusm]

GnomeBlack @ 12/06/2015, 1:27 PM

But they did not create a separate topic in the bugtracker, since no logs, no coherent information.

Can do: logcat -b radio>>/sdcard/radio.log?
Only there such porridge will be ...

Post has been editedshoma_81 - 06.12.15, 13:49

[Gnomeblack]

shoma_81,so it should be done more than once, to monitor when the network has disappeared, whether the client has been launched, to spend time on it ... we are not project testers, we have a lot of work.

[Rusm]

Gnomeblack
And who will catch it? If the developer does not have the described error, there is no possibility to reproduce the error, then how to fix it?

[Chichikov]

0.8.1 and 0.8.2 hang on a black screen with a 4pd logo, about 1 time out of three launches will necessarily hang.

[Sergey_Ace]

I decided to try again 0.8.2, but I did not wait .. I rolled back to 0.7.9

Oil painting

P.S. VibeUI 3.0 to 5.1.1