Related
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
machostallion said:
I've been using llama for quite a while with a lot of success on the stock rooted rom. I use multiple locations to control sound profiles, custom actions, etc.
The most important action I use is that once I'm in my "home" area, Wifi is turned on and once connected to Wifi, the phone goes into airplane mode with Wifi kept on and Sipdroid activated. Once I disconnect from Wifi, airplane mode is turned off and mobile service is restored.
This works flawlessly on rooted stock 4.2.1. However, on the CM 10.1 nightlies, llama constantly freezes and force closes and doesn't perform the scheduled tasks. Also, This morning there was some weird interaction with it and CM. My alarm was supposed to go off at 630 am. My internal clock was telling me it should have already gone off I looked at my phone and the CM chronus lock screen clock showed 6:42. I unlocked the phone and the UCCW clock on my home screen also showed 6:42. The system clock on the notification bar, however, showed the time to be something like 6:17. Obviously I was confused. Within seconds the system clock changed to 6:42 and the alarm went off. Curiously, llama was also not on the correct profile.
Anyone have any experience or ideas? I love using both llama and CM but there seems to be something causing problems. I haven't contacted the developer of llama but I don't expect any support for custom roms. I haven't tried it with anything other than stock and CM so far on the Nexus 4.
Click to expand...
Click to collapse
Mendanbar said:
I've been using llama on the CM10.1 nightlys with no trouble. I had problems with llama profiles a couple weeks ago due to the way JB based roms handle notification and system sounds. I contacted the developer and he was able to send me a custom apk that solved the problems. Those changes have since been folded into a new release that he put on the play store. The developer is very responsive and had no issues with the fact that I was using a CM nightly build.
It sounds like there might be some things happening beyond just llama problems with your configuration, though. The system clock not being in sync with the other apps is very strange. Are you using a custom kernel with CM10.1? I'm using Franco kernel #28 and my phone is rock solid.
Click to expand...
Click to collapse
I had the same problems you described back in December when I was running the beta off of the devs site. All seemed fixed when it got released to the play store.
Currently I'm running the CM stock kernel. I haven't made any mods, no theming, etc. It was a clean install with full wipes of everything twice. I flashed it with TWRP 2.3.3.
It is odd that the system clock could be behind the widget clocks. I've seen it the other way around where the widget would be behind the system if waking the phone after being in deep sleep a while. It's more strange that I can't open llama at all when I'm on mobile data now. It will only open when on Wifi. I do have quite a few Wifi dependent actions but since they work fine on the stock rom they should in theory work on CM. Maybe I'll keep testing and try to get a logcat to show something for the dev
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Update: Twice yesterday, I got missed texts and calls (saw them via google voice site on computer). I checked my phone and saw that it was in airplane mode with wifi off. This doesn't even make sense, since wifi is set to only turn off "upon leaving home"
ziddey said:
I'm using llama for the same purpose as you.
Events:
1. At Home - enable WiFi
2. When your phone connects to %AP% - enable Airplane Mode and enable WiFi // haven't looked into if it's possible to override wifi shutting off upon entering airplane mode in jb4.2 yet
3. When your phone disconnects from %AP% - disable Airplane Mode
4. Upon leaving Home - disable WiFi
I'm using the version available from the market as of yesterday and also see it constantly freezing up while trying to set it up. It's never force quit on me though and comes out of its stall after half a minute or so each time. I haven't tested it extensively yet, but after getting it setup, it seems to be working okay so far. I used to use a battery of other apps to achieve the same thing, but unfortunately the easily accessible airplane mode toggle api is removed from jb4.2 so those apps don't work anymore. I found that llama has a workaround that requires root, so it'll have to do for now.
I too am using sipdroid.
You aren't using llama for anything to do with alarms right? Then it's weird that causes your clock issues. You can try to see if ClockSync, https://play.google.com/store/apps/details?id=ru.org.amip.ClockSync, works on jb4.2. I had to use it on my HTC Sensation because the clock would drift hard when not connected to a cell tower for some reason. I think it might have been related to a specific kernel I was using, but a few times I saw it lose almost an hour in a 24 hour period.
Click to expand...
Click to collapse
I have been unable to duplicate the system clock glitch. I don't use llama for any alarms but I do have quite a few time based events to control volume levels and screen brightness. . After further testing, llama seems to do most of the set actions about 80% of the time. Sometimes it will be one of the actions in a string doesn't stick and sometimes it will miss a time based event. For some reason it has consistently missed the event at 11pm when it's supposed to put the phone into silent mode and lower the screen brightness. That time event is based on being in my "home" area, however, usually at that time my other events have been triggered which puts the phone in airplane mode with Wifi. Keeping Wifi on after triggering airplane mode also doesn't happen quite often. I know JB changed the permissions for apps accessing and modifying airplane mode but since I'm rooted and llama was changed to support it, it should work. I think there may be needs to be an option to add additional delays between multiple actions that are triggered by the same event.
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
lilfleck said:
Llama still doesn't work with CM. I contacted the dev and he said that the ROM requires additional permission to perform the actions like disabling/enabling wifi and bluetooth...
Boo I love llama.
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.arlosoft.macrodroid :good::good:
Hi,
I checked the web on this issue and have found it being reported on other sites but I can't seem to find the resolution, if there is one....
I received my Nexus 4 last Friday. Been digging it ever since. I came from the SG2 Skyrocket on att. I realized how much I miss the pure Android experience on a phone without the carrier's bloatware and manufacturer software.
however during the Super Bowl, my buddies and I discovered a weird bug on the phone. Upon waking up from a "long" hibernation, my time/clock is off by 20-30 minutes. Once I reboot the phone, the time is corrected. However, it's kinda weird waking up in the morning, my bedside clocks displays the correct time but when i wake up my phone, the time/clock is incorrect.
Has anyone experienced this? Does anyone know the resolution??
Much thanks..........
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Hash_Map said:
It happened to me once or twice before on my N4 stock/rooted. What is your setup under Settings>Date and Time ? Sometimes when you have Automatic date & time and Automatic time zone enabled and you are out of mobile network service, the time doesn't get updated until your phone mobile connection is restored. In my opinion, this behavior smells like a bug. Post a screen shot of that settings page if you could....
Click to expand...
Click to collapse
Hi Hash,
Thanks for the feedback. I went into the settings, as you directed, and see that both Automatic date & time (use network provided time) and Automatic time zone (use network provided time zone ) are both checked.
I will try and take a picture tomorrow morning for, again, it was weird looking at my cell phone which says 5:35am when my bedside clock showed 6:00am.
Schwacker
My Issue with Pictures
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Schwacker said:
All,
To document what is happening to my phone, I am attaching pictures to this post. The early morning picture post, I had my Wifi turned on. After the pictures were taken, I turned off WiFi an let it go int hibernation until I woke up at 6am. As you'll see in the second picture, my time/clock was way off.
I am using Beautiful Widgets for the clock but can't see that causing my issues.
Any thoughts? Hate to return the phone for I'm really loving it but don't want the phone if I can't depend on the time!
Thanks!
Click to expand...
Click to collapse
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
grubbster said:
Have you tried the stock clock to see if Beautiful widgets is the issue. Try that first. Next thing I would try is to leave WiFi on during sleep and see if the issue is fixed. I would expect to have some lag after a wakeup for the clock to update but no more than 15 seconds. Good luck.
Click to expand...
Click to collapse
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Schwacker said:
Thanks Grubbster -- I have to admit and I'm somewhat embarrassed in doing so, I couldn't figure out how to use the stock clock on my home screen and when I couldn't figure it, I thought "hey, I purchased Beautiful Widgets...I'll just add that clock to my screen....".
FYI -- I have always left my wifi on during the night and into hibernation. Last night I had the brain child thinking maybe it's the Wifi that is causing my delays for when I first noticed the time issue on Sunday, it was while I had my Wifi on....so I thought I'd turn it off to see if the time would be correct......freaking weird....
Click to expand...
Click to collapse
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
grubbster said:
The stock clock is a widget. Just go into your widgets, long press the clock, and drag it to your home screen. Also, does the clock in the status bar show the correct time when waking up?
Check your beautiful widget app settings to see if there is anything related to updating system settings. Maybe a frequency (10 min, 15 min, etc.) that needs to be changed.
Click to expand...
Click to collapse
Ok. Thanks -- duh -- there it is. I'll try this for a day to see if this will resolve the issue.
This has happened to me once, on Faux's kernel. It was my first time ever undervolting my device, and I undervolted by -100 mV (fast binned chip). It did it twice, and both during deep sleep. But the time corrected itself once I go into Settings > Date & Time and unchecking-and-rechecking the Auto Time setting.
Do you use a task killer?
Michealtbh said:
Do you use a task killer?
Click to expand...
Click to collapse
No. No task killer....though I have to admit....I was discussing my issue with a fellow phone geek. He believes my 2 options are: if it's an internal hardware issue, I'll need to get a new phone if it loses connection to the antenna which connects to my att network for the time/clock. Or if it's a software issue, then maybe a flash can resolve it.
I'm also going to contact Google later today and see what my return options are if, by tomorrow, I'm still experiencing this..
Thanks...
The question is as short as the title. I've a Samsung Galaxy Note 3 & it has started showing issues where the CPU remains in lowest possible frequency (250Mhz) and it doesn't go to deep sleep.
I tried uninstalling all the apps that I installed in last 2 days but I can still see the issues.
Searching on google isn't helping either. Most of the posts that get in search results are the posts where people paste the betterbatterstats output. On the official wiki, https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/wlan_wake , it's mentioned that a sniffer should be used to debug.
I saw that most of the sniffers actually require root. So, how do I debug this wakelock without rooting my phone?
Thing to note is, I was not seeing this wakelock since a few days back and I started seeing it just today. I don't want to switch off the wlan while the screen is off & I actually want to fix this.
PS: Please help as I've actually very religiously searched on the internet and I'm unable to find the solution.
wakelock detector
Sent from my SM-N9005 using Tapatalk
Chenglu said:
wakelock detector
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
That's how I came to know about it (using BetterBatteryStats though). It's a kernel wakelock, not a partial one. So, it's not what's triggered by the apps and hence it isn't easy to find the app that's causing it.
At various places, people are suggesting that some app is constantly using the wlan0 and hence the wakelock but I'm not sure which one.
So, anyone knows?
Bump
shadyabhi said:
The question is as short as the title. I've a Samsung Galaxy Note 3 & it has started showing issues where the CPU remains in lowest possible frequency (250Mhz) and it doesn't go to deep sleep.
I tried uninstalling all the apps that I installed in last 2 days but I can still see the issues.
Searching on google isn't helping either. Most of the posts that get in search results are the posts where people paste the betterbatterstats output. On the official wiki, https://github.com/asksven/BetterBatteryStats-Knowledge-Base/wiki/wlan_wake , it's mentioned that a sniffer should be used to debug.
I saw that most of the sniffers actually require root. So, how do I debug this wakelock without rooting my phone?
Thing to note is, I was not seeing this wakelock since a few days back and I started seeing it just today. I don't want to switch off the wlan while the screen is off & I actually want to fix this.
PS: Please help as I've actually very religiously searched on the internet and I'm unable to find the solution.
Click to expand...
Click to collapse
Have you tried disabling automatic time zone in settings?
My note used to have this wlan_wakelock ,but after I disabled automatic time zone its' seems to be fine.
That's weird
tyrand3 said:
Have you tried disabling automatic time zone in settings?
My note used to have this wlan_wakelock ,but after I disabled automatic time zone its' seems to be fine.
Click to expand...
Click to collapse
How'll that even remotely effect wlan_wake?
Guys, I was really hoping if someone could help... Thanks
N900 Wakelock
Hi
I had the same problem
Sometimes it's happened when I change WIFI state (On/Of)
Follow this:
0)I use Cpu Spy app to determine wakelock & Deep Sleep Problems
1) go to Wifi settings & turn on Wifi
2) go to Advanced
3)Set "Keep Wi-Fi on during sleep" to "Never"
4)Wait some seconds (I used to turn off screen, wait for some seconds)
5) turn off wifi
if you want to use wifi, turn on wifi and set "keep Wi-Fi..." to "Always" or not.
Notice that befor turning of Wifi, set it to "Never"
notice that when your phone is connected to charger T before disconnecting charger, unlock phone and wait for a few seconds while screen is on, then disconnect charger,
4.3
N900
XXUCMK1
XXUCMK2
Few possible causes:
- Do you have Wifi Scanning set to enabled? (Wifi settings)
- Do you have Use Wifi Networks enabled in Location settings in both Settings and Googe Settings?
so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.
How did you delete msg+ / my verizon? With "adb?
Thanks,
Rob
update to AW 2.7, u can disable via system apps
turning off every thing is not called smart, better buy a normal watch then
I'm not going to try all of these things, but I have noticed that it re-enables the cellular radio. I'm going to try putting it in airplane mode and just keeping the bluetooth connection on. My only issue is, is there any way to get rid of the airplane icon on the watchface?
geminihc said:
so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.
Click to expand...
Click to collapse
mistermojorizin said:
I'm not going to try all of these things, but I have noticed that it re-enables the cellular radio. I'm going to try putting it in airplane mode and just keeping the bluetooth connection on. My only issue is, is there any way to get rid of the airplane icon on the watchface?
Click to expand...
Click to collapse
I believe rebooting the watch is what turns on the cell signal. Mine stays off until I reboot. You don't need to turn on airplane mode to turn off the cell signal. I was going to write an app to do this automatically on boot, but can't unless someone finds a method to root it.
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.
Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.
Click to expand...
Click to collapse
I installed 2.8 on mine through ADB
Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
Click to expand...
Click to collapse
You can disable the charging display by going into app settings and disabling the charging app. I never found a way to keep the screen lit up while charging even with the always on enabled so I wrote an app to do it. https://play.google.com/store/apps/details?id=com.turndapage.watchwake
Jackson1983 said:
For the always on feature, the watch face actually changes to a different face from the one I set. It's like a screen saver version of the face which I am using. Is there any way to fix the face throughout?
And how do you guy update to 2.7? Mine updated to 2.0 and it says it's the latest version.
And where is the setting for the power saving mode? Mine enter power saving at 15%.
Click to expand...
Click to collapse
You're taking about ambient display. The app that sets your watch face controls that. Some have settings for this either on watch or on phone, some don't and you can't change it if you're using that face. I use watchmaker, which lets me edit every image layer in my faces and select which parts stay on. Also can create layers only visible in ambient mode.
mistermojorizin said:
I installed 2.8 on mine through ADB
Click to expand...
Click to collapse
How did you update through ADB?
nastynate435 said:
How did you update through ADB?
Click to expand...
Click to collapse
got adb over wifi going, got the apk from apk mirror (the watch specific wear apk), then did something like
adb connect 192.168.0.102 (or whichever ip your watch gets)
put the apk in the directory where my command window was
adb -s 192.168.0.102 install -r wearapp.apk
BUT, this is not necessary anymore. 2.8 just installs automatically now from play store on the watch.
You can just block message+ in the notifications screen, and install messages from play store
Always Best Imformation
geminihc said:
so i have been seeing REALLY crappy battery usage on my wear24 on aw2.7 despite turning off alot of things and barely using any apps.
now i EVEN have always-on ambient , and my watch lasts almost 3 days. since its always on, i rarely need to use the watch (eg. wake). i use the Sleek face which shows my agenda , weather, date, various other info on my face all the time so i just look at it. and incoming messages are shown still. here is what i do:
-KEY THING: AIRPLANE MODE! eventho i turn off LTE in connecticvity, i dont know if its a bug, but it's super annoying it keeps coming back on. this is the #1 change that improved it IMMENSELY. i think this turns off alot of useless wake functions and sync'ing
-turn off wifi (auto still keeps searching)
-only use BT
-delete msg+ / my verizon
-turn off OK google / tilt to wake
- no gestures
- no location
-turn on always on
One more thing if anyone can figure out, the watch auto turns on battery saver when under 10%. i'm curious if we can force this mode when its at 100%.
Click to expand...
Click to collapse
Always Best Information
My wear24 the battery is draining down so fast, i think its be bad battery. How can i replace the battery for my wear24?
I can't find the apk on apkmirror. Can you please post the link or the exact name of the apk.
abusalad said:
My wear24 the battery is draining down so fast, i think its be bad battery. How can i replace the battery for my wear24?
Click to expand...
Click to collapse
I just got mine for $43 on eBay and it went from 93% down to 2% on a single reboot. It then stayed on 2% from 6:30pm til 6:50am when it finally died. So I charged it from 0% to 59% then it jumped to 100%. Then it discharged to 77% and then dropped to 43%. sounds like a calibration issue.
On the plus side, unlike the moto 360 it appears the back is actually screwed on instead of glued on which is great news. I may unscrew it when I get home and see how easy the battery is to access.
Recently, i bought a Korean V20 F800L and received Oreo update. But every night, at 23:00, it automatically turns on wifi and keep i will have new notifications when i wake up.
I go to bed at 22:00 and always turn off wifi, close all recent apps before that. I think it may be something relates to Sync, backup or update but i couldn't find it.
Is there any solution for this?
Check settings-> smart settings and the configuration you have there.
anonik said:
Check settings-> smart settings and the configuration you have there.
Click to expand...
Click to collapse
nothing turned on
I don't have oreo yet on my V20 but I don't think that settings have changed that much so try to check at
settings->apps->configure apps->special access->modify system settings
There you will see the apps that have the authority to change your settings. Check the configuration of these apps one by one to see if something is set for the hour that the wifi changes to on.