Hi there. Only received my S23 Ultra a week or so ago. Had the S22 Ultra and had a routine where at 22h00 my phone must switch off wifi/mobile data/location and switch on do not disturb. It worked flawlessly on the S22, but on the S23 it doesn't switch off the wifi. I have deleted the routine and recreated it, but still the same. The rest of the routine works as it should. Any advice?
termdj said:
Hi there. Only received my S23 Ultra a week or so ago. Had the S22 Ultra and had a routine where at 22h00 my phone must switch off wifi/mobile data/location and switch on do not disturb. It worked flawlessly on the S22, but on the S23 it doesn't switch off the wifi. I have deleted the routine and recreated it, but still the same. The rest of the routine works as it should. Any advice?
Click to expand...
Click to collapse
I have the same routine setup in my device and works flawlessly. Did you use smart switch when moving to S23?
amirage said:
I have the same routine setup in my device and works flawlessly. Did you use smart switch when moving to S23?I
Click to expand...
Click to collapse
amirage said:
I have the same routine setup in my device and works flawlessly. Did you use smart switch when moving to S23?
Click to expand...
Click to collapse
I used smart switch to move over settings...did clean install of all apps. All routines that were brought over works fine, just this one. Deleted it and set it up from scratch...
I had te re-enable all my routines on s23 when I went into routines....
Smart switch as mentioned in this forum is all but Smart. It messes with the new device and has to be decommissioned by Samsung. It's very likely your device will get bogged down with battery drain issues very soon. The best advice for this is to set up the device from scratch after a factory reset
I checked this morning and when the routine is running it shows the wifi is on, but I checked and there was no internet connection... I will do the reset and see if it sorts it out
Well guess what - this is a third Samsung device I have and first one that causes intermittent problems with routines - which seemingly fire at scheduled time or event, but actually do not work and this can sometimes be partial as some of actions get done and others do not... and this is the first device that I acquired so soon after release.
It looks like settings routines up from scratch is not providing final solution to this. One thing that mostly helps is disabling and re-enabling routines that do not work correctly. Bugs seem to be unavoidable with hardware so new as this...
As routines app has a history functionality, it is possible to see if routine has run and failed to do what it is supposed to do or just has not run at all. I have 2 timely activated routines for weekday mornings and now I saw that first one of these just did not ran at all today - and nobody can blame phone being in deep sleep or something because its' scheduled time was after morning wakeup alarm.
It has only one simple function to execute - turn auto-sync on and that's it. This time it just did not run at all. I do not remember having this bad bugs in Routines on any of previous Samsung phones I had before.
Bugs are not only things bugging (I am not sure if pun is intended or not at this point) with Routines on S23. On my previous S20+ I was able to add Routines to Secure folder to do sime routines in there as well, but now it is not possible in normal way. It is possible to add Routines app into secure folder by adding it from Galaxy Store inside the Secure Folder, but after phone is restarted, Routines app will disappear. It was possible to just add it to Secure Folder from existing apps on S20.
Is it another bug or feature? Who knows - but these bugs in Routines that make it unreliable bug me much more than anything related with cameras...
I still can't get NFC to switch on with Google Wallet opening, it stopped working on my old Note9 on Android 9 I think and it's never worked on a Samsung phone since
Related
I had a Mi4i for a year. It is a great piece of hardware, much better than all my previous phones (3 sonys, 2 samsungs, 1 motorola). When CM came, it got overall good, nut just hardware.
I mean MIUI has some nice features, like permissions etc, but also there are huge flaws. Read on...
So I have for a Redmi 3 Pro for a week now...
The good:
Unlocked bootloader.
Build quality is superb. Screen is good (720p is perfect), overall feel is good as well. Battery holds 2-3 days easily.
Fingerprint reader works fine and quickly (under 1sec.), but you have to place your finger "correctly" and have no skin issues. Camera is not too bad but not as good as Mi4i.
Also it is very responsive and quick, much better than Mi4i and all other phones I had. Even when preloaded with many apps.
Backup/restore function works beautifully. Just fully set up your device and do a backup from MIUI menu. Then you can wipe it and load different (stock) ROM version, or rooted xiaomi.eu dev version. All apps are restored quickly and work well.
Mobile signature works well on both SIM cards. Which is great, as not all phones managed that. *cough* Samsung S4 mini duo *cough*.
The bad, same as Mi4i:
1. bluetooth earpiece will lose connection when talking. It drops connection or heavily distorts the audio randomly. But youtube audio plays well on earpiece. Probably something to do with sleep?
Also problems keeping connection to Pebble watch: notifications do not come randomly, sometimes it gets unlinked an is quite a task to get linked again.
2. Apps get closed in the background randomly. Skype, Viber, Hangouts, Whatsapp, email, Pebble, and even calendar... You just stop getting notifications. Extremely annoying when WhatsApp Web stops working every 15 minutes on your PC due to lost connection to your mobile.
I have investigated this further: allowed these apps to autostart, locked them in recents drawer, disabled memory optimizations in performance menu, etc. It improved a little, but still remains an issue.
3. Widgets crash randomly and after restart. For example non-stock clock widget and calendar widget. They just stop updating after an hour or so, also after restart. After another restart they completely disappear.
So all of these issues seem to be connected to some kind of power management issue perhaps? Is there a fix available?
On Mi4i, i have never found a fix and could not use bluetooth handsfree earpiece until CM support was added. On CM13 it works just fine, so definitely not a hardware issue.
Scared from MIUI's PM A clean Android supporting fingerprint scanner would unlock the phone's potential greatly.
I hope in CM12/13 with Pro features support soon.
2. On dev rom you can change Memory optimization settings from Developer options. If you lock app by pulling down from Recents it should not get easily closed.
P.Kosunen said:
2. On dev rom you can change Memory optimization settings from Developer options. If you lock app by pulling down from Recents it should not get easily closed.
Click to expand...
Click to collapse
Yes, I have tried that and still had problems.
Anyone had any success solving bluetooth issues? BT worked perfectly with CM on same device. Maybe it is possible to swap out some drivers?
I have decided to give the Nougat for A3 2016 (A310F) another (and another) chance before returning to Marshmallow but I've had some issues - please let me know do you experience similar problems (Nougat only!).
I've upgraded to Nougat by flashing via Odin DBT code package and went from XEO Marshmallow which did not have any of the described problems.
Was running: Android 7.0, Baseband: A310FXXU3CQE7, Build: NRD90M.A310FXXU3CQE6, Kernel: 3.10.61-11350514
To confirm the below I've reflashed back to 6.0 and flashed 7.0 again (same XEO for 6.0 and same DBT for 7.0) also did factory reset and also added wipe data/cache to the test procedure which helped in couple of cases.
Issues I found with 7.0 so far:
By design:
1. Too small UI elements:
Very small single-line notification slider containing the buttons like enable/disable wi-fi, etc. Previously on Marshmallow and Lollipop it was big enough to handle it without problems. Now (thanks to DreamUX?) it is too small (it is much better on my wife's A510F after Nougat upgrade as the buttons can be way easier pressed without accidentally pressing the button to the left or to the right). This one is quite annoying but probably just because the DreamUX (or whatever it is called) has been designed with "bigger phones" in mind...
2. Flawed Power Saving:
There is absolutely no setting in the OS to set the list of apps that I want to run only in foreground and when entering background should be put to sleep (there is such setting in Marshmallow and I used it to have control over the battery life). This causes the battery life on Nougat to be quite disappointing.
FIX: Flash TWRP (see the TWRP thread for details), did wipe of everything possible. Flash back official 7.0. Currently with normal usage - taken from charger at 06:00 currently 15:40 - battery level decreased from 100% to 88% (previously 8-9 hours on battery after full charge only) I susspect that this may be connected with the software I had installed in the past and some leftovers. So installing 7.0 in cleanest possible way did the trick here.
3. Slow battery charge:
Battery is charging quite slow (location off + wifi off + 3g on + phone not being used (periodically reviewing only the status of charging). Full charge from 30-40% to 100% in c/a 4 hours. Tested wipe data/cache - did not help.
All the time:
1. Crashing Samsung Keyboard (if other used):
When used any other keyboard (tested on Swype and Hacker's Keyboard) from Google Play - everything works fine until I click (be it by accident or intentionally) the emoticon icon (near the send button) while either writing a text message or using any other app where this button is available. The result is Samsung Keyboard (?!) crashing (which is odd as another keyboard is being used at the moment) - after the crash no keyboard is available until selected from the settings General Management\Language and input\Default Keyboard
FIX: Do the wipe of data and cache.
2. VPN not working:
VPN does not work (any attempt to establish PPTP connection fails with the built-in software). Tested wipe data/cache - did not help.
Fixed itself after some time... Now it's working. Either magic or this cannot be tested straight after setting up the OS...
3. Battery drain / decreased life on battery:
Nougat is consuming far more battery than Marshmallow (20% of battery taken in one hour while driving to work (one hour) browsing the web and listening to music compared to 6-8% with Marshmallow). Tests made after wipe of data/cache.
FIX: Flash TWRP (see the TWRP thread for details), did wipe of everything possible. Flash back official 7.0. Currently with normal usage - taken from charger at 06:00 currently 15:40 - battery level decreased from 100% to 88% (previously 8-9 hours on battery after full charge only) I susspect that this may be connected with the software I had installed in the past and some leftovers. So installing 7.0 in cleanest possible way did the trick here.
Often:
1. Stuck "Call" button in UI:
Inability to click "Call" button from the contacts if often calling several contacts (UI seems to lock for 5-15 seconds). To reproduce: Go to the phone app - select contacts, then tap on any contact name (not a picture) - four buttones called "call, message, video call and details" will slide - try tapping "call". Repeat calling several contacts - the UI hangs for couple of seconds making clicking "Call" impossible (home button however works)
WORKAROUND: Swipe finger on the contact to the right of the contact or recently dialled number to start dialling (this always works and does not trigge this bug).
Quite often:
1. Mysterious "installations":
Every couple of hours a notification pops-up that something is downloaded but there it is too quick to notice what was being downloaded, where, etc. It happens regardless if restored to factory defaults (seems to appear also on my wifes A510F after Nougat upgrade). It was not related to apps like messenger or instagram being updated by themselves as this feature was disabled in the settings.
FIX: Do the wipe of data and cache. It seems that the "mysterious downloads" was unsuccessfull attempt to update Android Instant Apps ( https://developer.android.com/topic/instant-apps/index.html )
Rare:
1. Blackout:
The screen turns black. After the restart phone boots up but once started again it defaults to lowest brightness level and need to be adjusted.
FIX: Do the wipe of data and cache.
wolfensg said:
I have decided to give the Nougat for A3 2016 a chance before returning to Marshmallow but I have some issues - please let me know do you experience similar problems (Nougat only!).
I've upgraded to Nougat by flashing via Odin DBT code package and went from XEO Marshmallow which did not have any of the described problems.
Currently running: Android 7.0, Baseband: A310FXXU3CQE7, Build: NRD90M.A310FXXU3CQE6, Kernel: 3.10.61-11350514
Issues so far:
By design:
1. Very small single-line notification slider containing the buttons like enable/disable wi-fi, etc. Previously on Marshmallow and Lollipop it was big enough to handle it without problems. Now (thanks to DreamUX?) it is too small (it is much better on my wife's A510F after Nougat upgrade as the buttons can be way easier pressed without accidentally pressing the button to the left or to the right). This one is quite annoying but probably just because the DreamUX (or whatever it is called) has been designed with "bigger phones" in mind...
2. There is absolutely no setting in the OS to set the list of apps that I want to run only in foreground and when entering background should be put to sleep (there is such setting in Marshmallow and I used it to have control over the battery life). This causes the battery life on Nougat to be quite disappointing.
All the time:
1. When used any other keyboard from Google Play - everything works fine until I click (be it by accident or intentionally) the emoticon icon (near the send button) while either writing a text message or using any other app where this button is available. The result is Samsung Keyboard (?!) crashing (which is odd as another keyboard is being used at the moment) - after the crash no keyboard is available until selected from the settings General Management\Language and input\Default Keyboard
Often:
1. Inability to click "Call" button from the contacts if often calling several contacts (UI seems to lock for 5-15 seconds). To reproduce: Go to the phone app - select contacts, then tap on any contact name (not a picture) - four buttones called "call, message, video call and details" will slide - try tapping "call". Repeat calling several contacts - the UI hangs for couple of seconds making clicking "Call" impossible (home button however works)
Quite often:
1. Mysterious "installations". Every couple of hours a notification pops-up that something is downloaded but there it is too quick to notice what was being downloaded, where, etc. It happens regardless if restored to factory defaults (seems to appear also on my wifes A510F after Nougat upgrade). It was not related to apps like messenger or instagram being updated by themselves as this feature was disabled in the settings.
Rare:
1. Blackout... The screen turns black. After the restart phone boots up but once started again it defaults to lowest brightness and need to be adjusted.
Click to expand...
Click to collapse
I have, so far, experienced none of the things you have mentioned. Google keyboard works great, no random installations, call works perfectly fine.
VPN won't work
i have the exact same call problem as you have but i also have some random android.phone crashes WHILE ON THE SKYPE APP
WHAT IS HAPPENING
I've got no problems I wiped from fast rom. V2. To advance three. My phones fast. But always cold. So I know there's power wasted.... If I were you download eset file manager.. There's a file logger. I also use greenify.
I'm not saying that official Samsung release of Nougat for A3 2016 is a piece of crap but just could be better (or it lacks some testing).
It has some minor flaws either that you need to get used to or you need to find a workaround if too anoying.
In general Nougat was responsive and working quite well. The design of caller UI and the notification dropdown were particularly most irritating for me since I used them both lot of time - that's why I've decided to returned to Marshmallow.
I know that I could used Greenify, etc (I used it some time ago on my rooted Galaxy Ace2) but Marshmallow with all it's features had given me "out of the box" everything I needed for work. That is why Nougat was kind of disappointment as it required some tweaking. I've also spent some time with reseting to factory defaults or flashing 6.0 and upgrading again to 7.0 and flashing again... etc... but the issues still were there. I susspect (but cannot confirm this as I haven't made any research on it) it may be kind of "per device" issue. I had similar problems before with Galaxy Ace2 as the same model (i8160) had two different versions (without any visible differeces/different firmwares etc) which had two different LCD screen whereas devices with S6D27A1 LCD were working all the time fine and devices with the LCD WS2401 (mine was having this one ;] were the lower quality ones and had issues with some firmwares, etc). This could explain at least that some people do not have any issues after the upgrade and some do have.
Man_tzagk said:
i have the exact same call problem as you have but i also have some random android.phone crashes WHILE ON THE SKYPE APP
WHAT IS HAPPENING
Click to expand...
Click to collapse
As for android-phone process crashing I would suggest making wipe of user data and cache partition / reset to factory defaults. This does not seem to be related with the firmware (I doubt that Samsung would release a firmware which is causing that type of issue.
charlander said:
VPN won't work
Click to expand...
Click to collapse
Sadly I don't have Nougat now (I've returned to Marshmallow) and cannot confirm but on Marshmallow VPN works fine.
BTW: Does VPN not work at all, or does not work only with 3G or Wi-Fi?
charlander said:
VPN won't work
Click to expand...
Click to collapse
I returned to Nougat just to play around with it once again (I hoped to get rid of the battery drain issues, etc).
I can also confirm that the VPN support is broken (connecting is not possible) at least with the built-in VPN tool.
A310M Nougat is now available. I flashed it with ODIN over a rooted MM with xposed installed, no wipes.
Everything is working just fine, wifi, bt, calls, keyboard (both gboard and samsung), data, sms, alarm clock, camera (front/back, stills with effects and video), new themes gallery. I'm having just a few hiccups in Chrome with heavy pages. I have no complaints whatsoever.
I kinda like the new layout and icons. Seems fluid. Battery seems fine too. In MM I get around 2 days, +6h SoT with lots of internet browsing, instagram, utorrent, youtube (when I feel lazy to use my desktop), calls (maybe a couple of hours/day), whatsapp all day long, acdisplay always on. I don't use 3g/4g that much because I hardly need it, wifi available in home, college and work.
I'll keep an eye on the battery stats. Gotta let it settle down a bit as I get used to Nougat. I'm really loving it so far.
So after couple of days spend testing, etc. it seems that for me all problems are more or less gone. Basically only two real problems are left:
1. The UI designed clearly for bigger phones and not quite comfortable, but some workarounds are possible.
2. Not working VPN (which is something I really use very very very rarily)
The solution to most problems is instead of insisting on upgrade from 6.01 (which seems to be severely flawed) to do the wipe of data and cache after the upgrade and configure everything from scratch.
However if this won't help (like in my scenario) - you can consider installing custom recovery (please note the warranty void and stuff) - TWRP and wipe evertyhing from there and... flash 7.0 again. To be honest - this last option fixed most issues for me and left me with pretty usable phone (again).
charlander said:
VPN won't work
Click to expand...
Click to collapse
VPN started to work for me on 7.0
wolfensg said:
As for android-phone process crashing I would suggest making wipe of user data and cache partition / reset to factory defaults. This does not seem to be related with the firmware (I doubt that Samsung would release a firmware which is causing that type of issue.
Click to expand...
Click to collapse
Thanks fixed
Hello all,
Unfortunately I observe a significant power drain which was not observed with android v. 5 or 6. On top of that I have some issues with "GPS signal lost" during map navigation. It's going even worst when battery saving functions are on
I tried different "tricks" suggested here, such as wiping cache but with no luck. I'm considering going back to android 6
I'm running nougat in one SM-A310M. To be honest, I'm not experiencing nothing bad. The battery is ok, system stability is ok, performance on and functionality is quite better.
Some things that I've to say:
1 system memory WON approximately 800 MB of free space
2 RAM usage is equal to marshmallow, but too much optimized (reopening apps)
3 the light sensor bugs is gone
4 mine antutu record before were around 27k. Now is ~37k. (I don't know the why, but 3D tests were listed how "unsupported" at the end of tests and now, in nougat, is ok. The RAM score is quite higher also on nougat
5 all the new functionality like notifications, recent apps button, video app can now create GIFs and the pop up blocker (goodbye SIM crazy popups) on home screen are quite useful.
Unfortunately, we don't have the multi window and night mode features, but I general, the update is positive. Nothing bad for while.
I'm attaching two images. The higher value come from nougat.
I had a Ticwatch E before switching to the mix 3 but using it on the mix 3 now I've had so many connectivity issues. Sometimes I'd get notifications and then sometimes the watch would disconnect, just wondering if anyone is using a smart watch that doesn't have these issues or if this is just an issue with the mix 3 and ticwatches.
Thanks
My moto 360 1st gen has also some issues.
Gesendet von meinem MIX 3 mit Tapatalk
I have Huawei Watch GT, no problems at all.
No problems at all here with a Huawei Watch 2 Classic
Amazfit Pace and no problem
Dont know what happens but now All Apps works and the notification grafics are now perfekt again. No more Problems with transpatency
Gesendet von meinem MIX 3 mit Tapatalk
I had some connection issues as well.
I figured out that it only loses connection when I kill all apps and so i tinkered with a few settings:
- disable power-saving for wear OS app
- enable auto start for wear OS
It still loses the connection if you kill all apps but reconnects as soon as you check your watch.
It never loses the connection if I don't kill apps (anymore?).
Hope that helps!
prozac192 said:
I had some connection issues as well.
I figured out that it only loses connection when I kill all apps and so i tinkered with a few settings:
- disable power-saving for wear OS app
- enable auto start for wear OS
It still loses the connection if you kill all apps but reconnects as soon as you check your watch.
It never loses the connection if I don't kill apps (anymore?).
Hope that helps!
Click to expand...
Click to collapse
Open recent apps, long press Wear OS app, and tap on the lock, now, even if you kill all apps, Wear OS won't be killed
Williammmm said:
Open recent apps, long press Wear OS app, and tap on the lock, now, even if you kill all apps, Wear OS won't be killed
Click to expand...
Click to collapse
True, but than you have to open the app in general while it is never actively opened otherwise.
Same thing with automatic started music that gets killed, even when you don't have your player open.
I've got the Galaxy Watch (46mm) and I am able to use it but with a caveat; if you unlock the bootloader you MUST root with Magisk in order to hide the fact that the bootloader is unlocked. Otherwise, the Galaxy Wear app and Samsung Pay with not even open, and you won't be able to connect the Galaxy Watch to your phone. If you keep the bootloader locked and don't want root access, it works normally.
I have a Gear 2 I flashed with Android Wear and it's been working perfectly.
My Watch GT doesn't automatically reconnect after I go out of Bluetooth range.
I've whitelisted all apps from the MIUI battery saver and granted all permissions.
I have also LOCKED the Huawei Health app to stop the system from closing it.
Once Bluetooth has disconnected, The ONLY way to get the watch to reconnect, is by opening Huawei Health or toggling the phone's Bluetooth off & on.
Unsure if it's the Huawei Health app or MIUI that is at fault.
Very frustrating.
Also using a Galaxy Watch (46mm) and it works great for the most part. You do have to root with Magisk to hide the unlocked bootloader (if you unlocked it). Other than that, for some reason I lose notifications on the watch almost every time I reboot the phone or put it in battery saver/extreme battery saver. This has something to do with the way MIUI handles notification access and is very annoying since the only way to fix it is to disconnect the watch from your phone (as in unlink it which wipes the watch NOT just turn off bluetooth), uninstall the Galaxy Wearable app completely, reboot, then re-install the Galaxy Wearable app, reconnect the watch, and restore my backed up data to the watch. It only takes a few minutes now that I know exactly what fixes it but it is really annoying that I avoid using battery saver and rebooting just to not have to deal with uninstalling and reinstalling the watch. If anyone has any better fix for this please let me know lol.
Does anyone use a FitBit? My wife bought a FitBit Versa and it constantly shows and error about the notifications not being available. She has to constantly reboot the phone to get notifications working correctly.
Rockmadeofrock said:
Also using a Galaxy Watch (46mm) and it works great for the most part. You do have to root with Magisk to hide the unlocked bootloader (if you unlocked it). Other than that, for some reason I lose notifications on the watch almost every time I reboot the phone or put it in battery saver/extreme battery saver. This has something to do with the way MIUI handles notification access and is very annoying since the only way to fix it is to disconnect the watch from your phone (as in unlink it which wipes the watch NOT just turn off bluetooth), uninstall the Galaxy Wearable app completely, reboot, then re-install the Galaxy Wearable app, reconnect the watch, and restore my backed up data to the watch. It only takes a few minutes now that I know exactly what fixes it but it is really annoying that I avoid using battery saver and rebooting just to not have to deal with uninstalling and reinstalling the watch. If anyone has any better fix for this please let me know lol.
Click to expand...
Click to collapse
No problem using the Galaxy Watch with unlocked bootloader, not rooted. Using Xiaomi.eu rom.
dunjamon said:
Does anyone use a FitBit? My wife bought a FitBit Versa and it constantly shows and error about the notifications not being available. She has to constantly reboot the phone to get notifications working correctly.
Click to expand...
Click to collapse
I bought the FitBit Versa and had to return it due to notifications never working, even with all battery saving options disabled it just didn't work. Picked up the Galaxy Watch Active instead and that works perfectly, I'd recommend it instead if you still have the option of returning the FitBit. Used it with MIUI at first which worked perfectly after disabling the battery saving features.
I'm now rooted with Pixel Experience, had to download an older version of Samsung Pay to get it to work without detecting root and it's working great on that too.
SamLovesJam said:
I bought the FitBit Versa and had to return it due to notifications never working, even with all battery saving options disabled it just didn't work. Picked up the Galaxy Watch Active instead and that works perfectly, I'd recommend it instead if you still have the option of returning the FitBit. Used it with MIUI at first which worked perfectly after disabling the battery saving features.
I'm now rooted with Pixel Experience, had to download an older version of Samsung Pay to get it to work without detecting root and it's working great on that too.
Click to expand...
Click to collapse
Well, I've been trying to get her to return the watch, but she's looking at other phones instead. Left her to it. Ha!
A bit of background:
I've been trying to set up internet access at a small home out in the country with cell service being the only option. Being cheap, I decided to try going down the route of tethering an old phone (Pixel XL) to a router and getting data-only plan (2GB of high speed at T-mo for $10/mo). The idea was that this would be enough to support my ring security system, some blink cameras and occasional internet use.
The problem:
Initially everything seemed fine. I got an Asus AC1300 (RT-ACRH13) router with USB 3.0 port for tethering and set up the Pixel XL to tether to it. However, I soon discovered the USB tethering option would get disabled by the phone quite frequently. This was due to a number of reasons...power briefly going out (fixed this by adding a UPS); pixel getting an update pushed to it (also disabled); bad weather causing signal to drop (can't fix this one); there appear to be other reasons as well i've not yet identified;
Tried so far:
Installed tasker thinking I could set it up to periodically re-enable tethering. Discovered for that I needed root, so I rooted the pixel. Tasker still complained - got a response from them stating that as of Pie "unfortunately Google now protect this action under the MANAGE_USB permissions which only system apps can get". Tried the Secure Settings app/extension for tasker and that just fails when testing the action without any additional notes - no response from the developer on that.
So, any ideas on how to accomplish what I'm trying to do? All i'd like is for USB tethering to be automatically re-enabled every few minutes if it's off.
L
Sent from my LM-V350ULM using Tapatalk
petik said:
A bit of background:
I've been trying to set up internet access at a small home out in the country with cell service being the only option. Being cheap, I decided to try going down the route of tethering an old phone (Pixel XL) to a router and getting data-only plan (2GB of high speed at T-mo for $10/mo). The idea was that this would be enough to support my ring security system, some blink cameras and occasional internet use.
The problem:
Initially everything seemed fine. I got an Asus AC1300 (RT-ACRH13) router with USB 3.0 port for tethering and set up the Pixel XL to tether to it. However, I soon discovered the USB tethering option would get disabled by the phone quite frequently. This was due to a number of reasons...power briefly going out (fixed this by adding a UPS); pixel getting an update pushed to it (also disabled); bad weather causing signal to drop (can't fix this one); there appear to be other reasons as well i've not yet identified;
Tried so far:
Installed tasker thinking I could set it up to periodically re-enable tethering. Discovered for that I needed root, so I rooted the pixel. Tasker still complained - got a response from them stating that as of Pie "unfortunately Google now protect this action under the MANAGE_USB permissions which only system apps can get". Tried the Secure Settings app/extension for tasker and that just fails when testing the action without any additional notes - no response from the developer on that.
So, any ideas on how to accomplish what I'm trying to do? All i'd like is for USB tethering to be automatically re-enabled every few minutes if it's off.
Click to expand...
Click to collapse
No personal experience with this but the scenario you are describing is a constant problem for people living in an RV (recreational vehicle). You may want to include RV product/solutions to see what they've come up with.
Hi
Andoid 12 (latest via OTA)
non-rooted
The problem is that while there is no problem with SMS / WhatsAPP notifications, no other ones come
Other notifications come only in 2 cases
- unlocks the screen (backlight is not enough, I have to unlock it)
- the phone is charging (then they come normally)
First, I set everything according to my own logic and intuition (it has worked well for the last dozen or so years of using electronics)
The problem still existed - so I looked online and set everything up as people suggested - THE PROBLEM STILL EXISTS
Later I found the website dontkillmyapps
I set up the entire system and applications according to the information provided
THE PROBLEM STILL EXISTS
I even installed an application related to this website that checks the killing of applications, after a two-hour test, all results came out 100% (i.e. nothing killed according to the legend of the tests)
I turned off optimization, turned on dynamic mode, turned on flexi, turned off battery adaptive mode - in short, everything possible at the expense of battery life - ZERO result
Phone unlocked - notifications come, phone locks - they come for about 1-2 minutes and end
Previously, I used A11 (I did not upgrade to A12) on LG g8s and there were no such problems
Its an android issue, not a Zenfone issue. I would just not get notifications on messanger (FB) randomly. It was the same with a S21 Ultra I had before. I always do the steps you mentioned, but it didn't solve the issue. Uninstalling and reinstalling solved it for 1-2 days, then notifications will stop arriving randomly.
I have to admit its better with A13, the notifications are just delayed, I don't think i missed one since I did a clean install about a week ago.