Related
I've got a Stock Desire running 2.2 and am having an issue with my time and date settings - I'm unable to set the time including seconds. What this means is that my phone is approximately 30 seconds fast or slow, and this is messing up my message threading. This issue is noted as a "Flaw/Annoyance" in this thread by Jaa-Yoo, but I'm having problems with the threading even when I'm having a conversation by SMS with a contact who uses the same network as me (O2-UK).
Is there any way to "force" the handset to update the time manually? If not, do you know what time the clock will automatically update with the network? Can anyone suggest any way I can set the time in HH:MM:SS as opposed to the default HH:MM? (via an app perhaps?)
I've used the handset for over a year and this has only really started to become an issue over the past few months - I'm guessing the timekeeping is just slightly out, and the difference that has built up over time has now started to be a problem. I'd really rather not put up with it for another few months until the seconds fall back into place...
Many thanks for any help or suggestions.
Hello,
Can "Scheduled Power OFF/ON" feature be added into the future builds(LineageOS 14.1)?
I would be happy if Lineage builds get this awesome feature!
There are some third party apps (like automate) which are only capable of switching OFF the device, not capable of turning it back ON......so I request LineageOS team to work on this feature.:good:
Thanks in advance!
Eagerly waiting for this feature...
Sent from my Asus Zenfone 2( Z00A) running Official lineageOS 14.1 builds.
The thing is that this was removed from devices after it was found not to really turn the device off completely. Which makes complete sense as if it is completely off then there is no way to turn it back on.
zelendel said:
The thing is that this was removed from devices after it was found not to really turn the device off completely. Which makes complete sense as if it is completely off then there is no way to turn it back on.
Click to expand...
Click to collapse
On older removable battery Chinese phones when this feature was there, the scheduled power on/off times and dates were the same when the battery was replaced, whether immediately or later (not sure about how much later).
But miui has this feature and it works great on MIUI
Zelendel, kindly point to the commit that was removing the feature.
I would like to try restoring it back for myself.
And what is the programmatic method the app was working? Are you saying that was just enabling airplane mode and switching screen off?
Pretty much that is all it was doing. It was leaving the internet hardware on.
As for the commit. You may not find it. It is not part of the open source android. It is closed sourced and not even really seen anymore on major devices. Most Chinese devices use it as a way to send data back to China when the user doesn't think anything is happening.
i am waiting for solution too.
I think you can make your phone life longer by keeping it off 8 hours a day.
I think that some phones have that hardware ability and some don't. PCs have this ability too.
I own a Xiaomi Redmi Note 7 running on unofficial Lineage OS 17. This feature is partially implemented now.
I set on an alarm.
I power off my phone.
The phone powers up when the alarm goes off. This works only if the alarm is set 5 or more minutes ahead from the time you power off.
As this works flawlessly, it should be pretty easy to add an "Automatic/Scheduled turn On/Off" in the phone settings.
I'm using crontab to automatically turning the phone off at 1 am. The problem is that if I'm still awake and using the phone at that time, it does not warn me. It just turns off. A feature in the phone settings would allow me to abort right before turning of.
If anybody is interested to know the graceful poweroff command, this is my cron tab line
Code:
00 1 * * * am start -a com.android.internal.intent.action.REQUEST_SHUTDOWN
I'm getting this message"One or more enabled modding options are no longer supported on Android 10" pop up on my screen now and then. Anyone have this and know how to get rid of it please?
No, and other than root I'm bone stock, i.e. no mods. So, the question to ask here is, are you running Xposed? If the answer is yes, then your problem is there, and the solution is to remove it completely. If the answer is no, then list your mods, and start working through them one at a time, removing them until the warning stops appearing. The last one you removed will be the culprit, and you can then reinstall your other mods.
So, oneplus always had the ability to enable call recording, they just don't show it to you based on what country you are in / sim in use. However, there are ways via adb commands to enable it. They would have to be run fresh on every boot, but there are ways to automate it. However, now, it seems that oneplus is being much more active and during runtime disabling it randomly (at least popping up a message telling you that it is). I am pretty upset with this change that came in today's hotfix.
thetoady said:
So, oneplus always had the ability to enable call recording, they just don't show it to you based on what country you are in / sim in use. However, there are ways via adb commands to enable it. They would have to be run fresh on every boot, but there are ways to automate it. However, now, it seems that oneplus is being much more active and during runtime disabling it randomly (at least popping up a message telling you that it is). I am pretty upset with this change that came in today's hotfix.
Click to expand...
Click to collapse
There is a Magisk module (enable oos native recording) that enables recording and survives reboot. Just remember to uninstall it prior to any oos update, you can then reinstall it.
I try to stick with stock, as really had no issues. I was able to create an automate script that worked without rooting / modifying the stock firmware that reenabled recording on each reboot. The problem is, now the firmware is actively disabling it during runtime, not just as boot. my "solution" right now is that it seems to be tied to the notification, so if I never dismiss the notification tell me that its disabled, then it doesn't disable it in the future. Not a good solution to leave a notification up (As easy to dismiss by accident). but it really annoys me that they made such an antagonistic change.
I've created a workflow in automate that enables recording on boot and reenables it every time the notification of recording disabling comes up and dismisses the notification. Annoying, but seems to work without any rooting needed.
but i'm so annoyed that they changed this. I use t-mobile's wifi calling for my US SIM (I'm overseas), so everytime i drop out of wifi, it triggers as it seems to trigger everytime there's a "service" change of some sort on it.
Ok so i just got a 6 pro. Rooted day 1 before activation. Running Android 12. Seemed to work fine for a few days. Seemed.... So now my notifications are delayed or not coming thru at all unless i restart. My old phone was a Samsung Note 8 rooted as well. I wanted to get away from Samsung even though I loved the UI because my friend has a pixel 4 XL. Abd i loved how his phone had a better signal than mine, sane carrier and next to each other. Ive googled and watched yt vids to fix this issue. Nothing helps. It will work for 5 mins or 5 hrs then just stop. Even txt wont come thru on Signal. If i restart it will seeming work again. I rarely ever had to restart my Note 8. At this point i just want my brand new phone to work. Since the initial root i havent factory reset or wiped and reinstalled the root. Not sure what i should do first. Also not sure if going to 13 would fix this. Some stuff i read says yes and some stuff says 13 is buggy too. I wish i could put Android 11 on this phone and call it a day. Can anyone please help me? I dont wanna return my new phone.
TL;DR
Android 12 rooted notifications delayed and not working. Halp pls!!!!!
Hi. Have you tried setting any of the particular apps for which you're having trouble with timely notifications to not being restricted from background usage? Long press the app icon / App info / Battery / Unrestricted. In App Info, you can disable "Pause app activity if unused" for those particular apps.
My wife and I have a lot less trouble with timely notifications on our Pixel phones than we did on our two Galaxy Note 10+ phones.
Yes. I've done all of that. I've set battery to unrestricted. Every tip I could Google. And it's still intermittent. It's driving me nuts. I just need this phone to work.
para5it33v3 said:
Yes. I've done all of that. I've set battery to unrestricted. Every tip I could Google. And it's still intermittent. It's driving me nuts. I just need this phone to work.
Click to expand...
Click to collapse
Here's a Reddit thread about a similar issue (seems to be some Google programming error with no fix):
https://www.reddit.com/r/GooglePixel/comments/t2cuuu
I've always had notification issues (late, none) since doze was first introduced. Every phone I've had I've had to run the following command to get notifications:
adb shell dumpsys deviceidle disable
The issue is, this command (which disables doze) has to be run each time the phone is rebooted. I use Tasker to run this script on my rooted P6P on each reboot (you can also use SManager). On my work phone (a non-rooted S10+) I have to open a command prompt and type the command.
I'm not an Android programmer or expert, but running this command has always worked for me. I realize disabling battery optimization and stuff is supposed to do the same thing, but that has been inconsistent, and some of my phones didn't provide the ability to change battery options for some apps.
Also, look for any rogue Magisk modules you have installed.
Good luck.
Hey, have you found the help that you needed ?
I too was having delayed notifications and could not for the life of me figure it out. Turns out it was NordVPN causing the issue. I changed the protocol from "Recommended" (assume that's NordLynx) to "OpenVPN (TCP)" and it fixed it right away!