[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 483: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/bbcode.php on line 112: preg_replace(): The /e modifier is no longer supported, use preg_replace_callback instead
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4668: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4670: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4671: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
[phpBB Debug] PHP Warning: in file [ROOT]/includes/functions.php on line 4672: Cannot modify header information - headers already sent by (output started at [ROOT]/includes/functions.php:3815)
XWidgetSoft Forum :: View topic - [SOLUTION !] KitKat 4.4.2 Freeze Clock
XWidgetSoft Forum
https://bbs.xwidget.com/

[SOLUTION !] KitKat 4.4.2 Freeze Clock
https://bbs.xwidget.com/viewtopic.php?f=3&t=6326
Page 1 of 1

Author:  Slavoo [ May 22nd, 2016, 6:18 am ]
Post subject:  [SOLUTION !] KitKat 4.4.2 Freeze Clock

Test in progress.... in my LG G2 with Stock ROM 4.4.2

Error is in @datetimecore1

Look at screen. The default is 30 minutes in the Android !!!
Should be changed to one minute!

1. Option (tap on widget)
2. Edit Widget
3. Others
4. datetimecore1 --> Attributes
5. Core Setting --> Interval = 1 second !!!
6. Only update when minute changed = OFF !!!

Check it this !

2016-05-22-16-13-31.jpg
2016-05-22-16-13-31.jpg [ 145.96 KiB | Viewed 4614 times ]

Author:  Slavoo [ May 22nd, 2016, 6:25 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

@Jimking

Your widget

2016-05-22-16-21-30.jpg
2016-05-22-16-21-30.jpg [ 145.41 KiB | Viewed 4612 times ]

Author:  Jimking [ May 22nd, 2016, 7:40 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

When I create weather widgets I always leave the default accuweather core values of the designer.
About the "Should be changed to one minute!"
NO, because:
1) We're talking about the weather Slavoo. There is no sense having the update time to one min!
The weather not changes every min Slavoo! Even the accuweather service doesn't update every min... (check the app's settings -> 15min minimum)
2) The weather data updates ONLY with internet connection ON.
So even with one min update time if the wifi is off the weather will not update.
4) More data usage and maybe cpu. The app will try to update every min. Why?
5) The user can easily change the update interval through the app's settings
viewtopic.php?f=23&t=5317

pm:
I think that the clock data that not updates after some hours has nothing to do with the accuweather core.
These are two different things (!) and the proof is that even you use a single clock widget on KitKat the time will freeze equally..

Author:  Slavoo [ May 22nd, 2016, 8:07 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

But the change relates @ datetimecore1
not @ accuweathercore1

Author:  Slavoo [ May 22nd, 2016, 8:32 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

@ datetimecore1
I do not understand how it had come in Interval 30 minutes ??? I am writing here about the editor for Android.
In the PC editor does not have anything like that.

Screenshot 2016-05-22 18-30-57.jpg
Screenshot 2016-05-22 18-30-57.jpg [ 25.12 KiB | Viewed 4597 times ]

Author:  Jimking [ May 22nd, 2016, 9:08 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

Ok, I think we have confused a bit the two cores..
1) The problem that actually exists is the time freezing, so we need to talk ONLY for the datetimecore.
2) All the clock widgets -> Android version, use as default the "Updated every min".
And this because the widgets not have the second hand! So the core will update when it's necessary, every one min.
If you disable this on Android, then you will be able to use clocks with second hand BUT the ram consumption will increase (also the movement is not so regular)
That's why Tony enabled this by default.
3) I NEVER changed ANYTHING to the datetime core and to be honest I don't know the real meaning of this "Interval" setting since the option before this " Only update when minute changed " is enable!

So, the conclusion.. Since ALL the widgets that have the datetimecore use the DEFAULT values, and these widgets WORK FINE for almost all the OSs except the kitkat, the problem maybe is not there. Because if the issue is caused from this "Interval" setting, NONE of the widgets should work.... (!)
Something is wrong with the KitKat OS that blocks somehow XWidget and don't let it to work properly.

Author:  Slavoo [ May 22nd, 2016, 9:14 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

Test in progress....
It seems to me that it is good. But it's too early for a final conclusion. Tomorrow I will write here is the result.

Author:  Jimking [ May 22nd, 2016, 9:23 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

If you have the possibility to test the app on some other phones with other OSs (not KitKat) you will see that the clock widgets work fine..
(without change anything in the designer)

Author:  Slavoo [ May 22nd, 2016, 11:22 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

But I do not have another phone and I have no way of checking on other phones.

The initial proposal:

CLOCK WORK !!! :D :D :D

However, not working Update inteval
viewtopic.php?f=3&t=6327

So was a mistake to fix. For me important.

Author:  Slavoo [ May 22nd, 2016, 11:29 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock


Author:  Jimking [ May 23rd, 2016, 1:19 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

So, let me understand. Changing manually this "Interval" setting" the clock works fine now..?

Author:  Slavoo [ May 23rd, 2016, 7:44 am ]
Post subject:  Re: [Probable SOLUTION !] KitKat 4.4.2 Freeze Clock

YES

I set Interval in @datetimecore1 = 1 minute

Author:  Slavoo [ May 23rd, 2016, 10:16 am ]
Post subject:  Re: [SOLUTION !] KitKat 4.4.2 Freeze Clock

CONCLUSIONS:

It is light freezing or it is not.
From 0 sec to 0.5 - 1 sec.

I set the interval to 1 second

This does not solve the problem completely but it is much better than it was.

OK_Think_Stock_360.jpg
OK_Think_Stock_360.jpg [ 6.42 KiB | Viewed 4569 times ]

Author:  Jimking [ May 23rd, 2016, 11:23 am ]
Post subject:  Re: [SOLUTION !] KitKat 4.4.2 Freeze Clock

The fact is that happens only on KitKat. But if this is the solution then Tony should change it for the next version.

Author:  Slavoo [ May 23rd, 2016, 12:00 pm ]
Post subject:  Re: [SOLUTION !] KitKat 4.4.2 Freeze Clock

I think it's temporary. Tony must fix Xwidget, so that work on all systems.

I would add that I have not noticed greater consumption of RAM and battery

Jimking, you wrote that you have a phone with KitKat, where the error occurs.
Check my way and write requests.

Author:  Jimking [ May 23rd, 2016, 12:21 pm ]
Post subject:  Re: [SOLUTION !] KitKat 4.4.2 Freeze Clock

You didn't understand ...The ram and battery consumption increases a lot not changing this option but the other one before the ''interval''
Check your first screenshot. And this is for activate the support for seconds.
I wrote that I have a phone with KitKat and yes I confirm that I have the same issue with the clocks... Fortunately is my old Galaxy S rooted so I don't even use it. :)

Author:  Slavoo [ May 23rd, 2016, 10:55 pm ]
Post subject:  Re: [SOLUTION !] KitKat 4.4.2 Freeze Clock

I don't know. I change interval to 1 second and clock working.
viewtopic.php?p=13445#p13445

Not working this: viewtopic.php?f=3&t=6327
That's all from me.

Page 1 of 1 All times are UTC - 8 hours
Powered by phpBB® Forum Software © phpBB Group
http://www.phpbb.com/