Related
Hello everybody,
just started a temporary sale for NFC ReTag PRO...
Use any NFC tag (write protected and re-writable) to trigger multiple functions on your device!
You can use this app to associate multiple functions (e.g. toggle Wlan, Bluetooth, Mobile Data, Airplane mode, start navigation,run Tasker task, launch any installed app, use media buttons, call a phone number, add a timestamp, calendar entry and many more) to a specific NFC Tag via an app internal database.
Get it NOW and save some money
Link to the Support thread:
forum.xda-developers.com/showthread.php?t=1477138http://
Free version also available !
Nice and first! Downloading now...
Text to speech bug
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
GenePaton said:
Hi all,
I've come across a weird bug that once i have run the "speak current time" actions under the labs section, my phone continues to speak the time for other various actions (eg opening/closing folders, setting the alarm etc).
So far there seems to be no way of stopping it, even killing the Google text to speech service does nothing.
Anyone else with this problem or any solutions?
Regards
G
Click to expand...
Click to collapse
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
ascsa said:
Hi G,
received your e-mail and replied this via e-mail a couple of minutes ago ...
Hi Gene,
No, you are the first reporting this. There is no Retag background service which could cause this and NFC Retag doesn´t change a TexttoSpeech setting, therefore I would say it´s not related, but stranger things had happen.
First thing I thought, it´s probably related to the CAR Mode ... a lot of devices speak a lot of things (Sms received, folder opened etc. ) while in car mode..annoying and mostly unexpected ... the first time it happen to me, I was completely clueless what was causing this and how to disable.. So please check if the car mode is enabled.
Second thought was the Standard Android Accessibility feature, please check under Settings--> Accessibility that the TalkBack option is disabled (provides spoken feedback for blind users ).
If this doesn´t help, reboot your device and please check again...If the issue still occurs, could you please give us some more details (device, firmware version, etc.) and if possible a log file, so we could analyze this in detail?
Click to expand...
Click to collapse
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
GenePaton said:
Hi ascsa,
Thanks i got your email. Great to see such quick response from developers. I wasn't expecting it, hence the post here as well.
Just to clarify for any other readers, i'll repeat what i sent in my reply email to you.
Driving mode and talkback are disabled on my device.
I found a temporary fix by clearing the data from Application Management->All->Google text to speech service, but it then randomly starts again at a later time. I think the fault may lay more with Android than any app as there are a couple of other applications out there having the same issue. Something about Android calling the wrong service (text to speech) when various apps are started.
For your and others information, my device is a Samsung Galaxy S3 GT-I9300T Android 4.1.2 Stock Vodafone AU ROM, rooted. Baseband I9300TDUELL2.
Cheers
G
Click to expand...
Click to collapse
No Problem ... ... but let´s move to the official support thread (http://forum.xda-developers.com/showthread.php?t=1477138&page=100) ...because this is an old thread ...NFC Retag PRO is currently NOT on sale ... and we shouldn´t confuse the users ...
Just to clarify for any other readers, my e-mail answer to your last post :
The Galaxy S3 GT-I9300 (international model) is one of our main testing devices. Not sure if, there is a problem with the Vodafone Rom or the Australian T model, but it´s working fine here on 4.1.2.
Had a short look at our code and the official api and everything seems fine ... but without a log file or better a device on which we could reproduce the error it´s nearly impossible to be sure ...However, you mentioned it happens with other apps, too , so I would bet on some Vodafone "enhancements" ...
Btw. have you tried the Samsung TTS engine (settings--> language& input -->text-to-speech output--> preferred engine) instead of the Google engine?
I notice there are several versions of tasker. Which do I need?
Muscipula
Sent from my SM-G903F using Tapatalk
Hi all.
Just a question about a possible software bug you might be able to help me test.
Under the progam Latitude, when you go into the menu [location settings] you can chose to activate automatic check-ins.
Every time I activate this the phone writes my selection has been saved, but the nect time I open the menu, the activation is gone.
I talked with LG support, and they told me it worked on there phone, so I have to send the phone ind for repair.
But to be honerst I'm not sure the understod the problem.
So can you help me, an test on your phone, if it remembers the activation og automatin check-ins i latitude or not
Thanks
Solved (Sort of)
I guess there are not many around using Laitude
Anyway found out it's not my phone (as LG support claimed). dut a BUG in google maps.
Here's what I found, including a fix if anyone are interested....
Issue 33719: Latitude "Automatic check-ins" setting reverts to disabled
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
You can probably unpair (from both the phone and sync) and then repair and when you repair just deny the MAP access request.
Also, you should be able to turn off new message download in Sync
triton302 said:
My X is paired to my 2013 F-150 via SYNC and it automatically adds the voice, media and message features upon connecting. However, every time I get a text, SYNC stops everything to tell me I have a new text message, and it's annoying. You can turn MAP off temporarily by manually disabling it while the phone is paired, but once it re-pairs with SYNC, it automatically activates MAP again. I do use the voice and media though.
My question is this... is there any way to permanently disable the MAP feature on the X? I don't use it and never will. I always check my phone when a new message arrives or wait until I'm at a stop. I just want to be able to be able to remove the MAP feature.
Click to expand...
Click to collapse
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
boosting1bar said:
Did you ever find a solution for this? I just got a '14 Raptor and it does the same damned thing. I've deleted the phone pairing and repaired and deny access when repairing but it still automatically connects to all 3 protocols when I get in the truck. My phone is actually an LG G3 but it seems to be an android problem and not a specific phone problem.
Click to expand...
Click to collapse
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Yeah that's exactly what I'm getting in my 14 Raptor. Terrible, I guess I have to disable it every time I get in the car now.
triton302 said:
Nope. I also got a '14 Focus ST and the bluetooth "feature" is even worse on it. Since I have the full touchscreen, it will now display the notification that I have a text, and who it's from. Again, you can temporarily disable it on the phone but not permanently.
Click to expand...
Click to collapse
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
dtg7 said:
Do you guys have root? if so maybe you can try something. but keep in mind I have not tried this myself and also I could be completely wrong.
Anyway, I noticed in my moto x build.prop file (that sets the phone settings on boot) that one of the lines seems to disable Bluetooth SAP on boot. The line is
ro.qualcomm.bluetooth.sap = false
if that can turn off SAP maybe
ro.qualcomm.bluetooth.map = false
can turn off MAP on boot.
Keep in mind editing build.prop the wrong way can give you boot up problems. Backup the file, and also keep track of and set the appropriate permissions for the file.
In fact, it's probably better before editing build.prop to try the setting on the fly. In a terminal emulator with SU enabled try the line
setprop ro.qualcomm.bluetooth.map false
then check that with getprop and with your car.
this is safer if you have any problems you can just reboot. if it works you can proceed to build.prop
Click to expand...
Click to collapse
Great idea, however I just tried it with no avail.
I just thought of something as well... my fiance has a '13 Focus SE with the base stereo, and she has the same model phone as me (VZW X Dev). Her SYNC doesn't alert her to new messages, but my truck with the same SYNC setup did, but I figured my truck had a more recent version of SYNC. I dunno, all I know is it's annoying as hell and I'd like to find a more permanent solution. Especially since I'm contemplating on buying the Droid Turbo in the future and I'm sure it will do the same thing.
triton302 said:
Great idea, however I just tried it with no avail.
Click to expand...
Click to collapse
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
dtg7 said:
That sucks... Just to clarify I assume you tried this with a terminal emulator. did you remember to give it root before running the setprop command? i.e. type su and enter. without root setprop will appear to go through but won't actually set anything. And if it's set properly, getprop ro.qualcomm.bluetooth.map should return false like it does for SAP. otherwise it will return empty.
Another thing that might or might not make a difference, was Bluetooth on when you tried this, if so try it with Bluetooth off.
As for the difference between the two SYNCs my guess is you're right the version difference could be affecting something. A quick Google search suggests some versions of SYNC have a setting for MAP. in SYNC menu check System Settings -> Advanced -> MAP Profile
Click to expand...
Click to collapse
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
boosting1bar said:
The newer SYNC version doesn't have that MAP option, that was the first thing I found when googling as well. (and for the record I don't have a moto, I'm using an LG G3 and found this thread while searching for a solution). Unfortunately my build.prop doesn't have those lines in it. Not sure if I could just add the MAP entry or not, that's above my knowledge base
Click to expand...
Click to collapse
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
https://play.google.com/store/apps/details?id=cn.wq.disableservice
good luck.
dtg7 said:
well without putting in commands manually I see two things you guys can try. the first doesn't need root while the second one does.
1) turn on Bluetooth on your phones, then go to Settings -> Apps -> Running -> Bluetooth Share then just Stop the Map service. This method will stick as long as you don't turn off Bluetooth and start it again, and as long as you don't restart the phone. if you do either you'll have to do the stopping again.
2) this requires that your phone be rooted, but on the plus side it might be more permanent. There's a nifty app in the play store made by some benevolent developer that claims to disable any service started by any app. appropriately enough the app is called Disable Service. You open the app, slide over to the System Apps section, find Bluetooth Share and click it, then just uncheck the Maps service box. So simple, but won't work without root. Try it with Bluetooth off and if that doesn't work reset it then try it with Bluetooth on. But word of caution you don't want to go messing around disabling other things unless you're sure of what you're doing. disabling the wrong thing will cause you problems.
good luck.
Click to expand...
Click to collapse
Thanks so much! Option 2 is exactly what I've been looking for! Option 1 doesn't work for me because I use Trigger and have conditional BT on/off and that would just recreate the same problem lol.
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
triton302 said:
Just tried option 2... If any of those services are unchecked, Bluetooth itself turns off automatically and won't turn back on until that service is restored.
Click to expand...
Click to collapse
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
boosting1bar said:
Yep same here, tried it on my way home yesterday and the disable service app completely disables bluetooth if you disable MAP.
Click to expand...
Click to collapse
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of profile).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Roger, I'm off work today so I'll try these out here shortly.
EDIT: From what I recall, if you have a recent version of MFT, there are no options whatsoever for MAP, in phone or system settings. I'll double check.
EDITING EDIT: #2 doesn't work.
dtg7 said:
Wow no breaks...but not quite out of ideas yet. a few more to spitball, going from simple to more complex:
a) we've established there's no option to disable MAP from within SYNC under System Settings. What about under Phone Settings? Indications are there should be an option there to turn off Message Notification. If it's there set it to OFF. frankly I'd expect there to be such a setting somewhere in there.
b) reaching a bit here, but in Disable Service app I notice there's another system app that has Bluetooth service settings. the app's name is org.codeaurora.bluetooth (Apparently Code Aurora is the Qualcomm Linux kernel). No idea if this will work where the other failed but won't hurt to try. the service says BluetoothMasService but if you check the full name it is map (maybe service instead of protocol).
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
that's it. personally I still prefer my original idea of figuring out how to do it manually thru setprop and build.prop, but if that's not an option then try these.
Click to expand...
Click to collapse
I think we have a winner! #3 works perfectly.
I tested it with the phone unlocked and locked, rebooting the phone, toggling bluetooth on and off, turning the car on and off... seems to work every time. As long as you turn off just the SMS/MMS options, you can still have it send and receive calls and allow the device to remain unlocked while connected.
Ahhhh...... Success feels good...
Xposed is pretty amazing... It gives us a fighting chance lol.
if only they'd installed Xposed on Skynet things might have turned out differently...
dtg7 said:
c) this one brings out the big guns. not only do you need root, but you also need Xposed installed. if you already have Xposed then it would be quick to try. if not, just read up on it. anyway, with Xposed installed you need the AppOpsXposed module. when you have that up and running you open the App Ops screen of the Bluetooth Share app (a few ways to do that, doesn't matter how). in that screen you turn off all of Bluetooth Share's access to SMS. Basically you disable Bluetooth from interacting with Messaging. you revoke the permissions. Bluetooth will still work unaware that it can't access messages, and I figure if it can't access messages it damn well can't send them to the car.
There's another module that can do this more thoroughly, but App Ops is less scary/more user friendly.
Click to expand...
Click to collapse
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
You're welcome!
boosting1bar said:
Awesome, worked here as well!! I'd looked through xposed and didn't see any modules that would do what we were after, completely forgot about AppOps. Outstanding work and thanks so much for the help!
Click to expand...
Click to collapse
How did you get this yo work? I am on a cm12 Rom also with the same issue.
Did all the above, but anytime I start the Bluetooth afterwards, it just reactivates the "Read / Write sms messages permission all over again nd im back to square 1.
Sorry to bump an old thread. But its still yhe same issue I am dealing with.
I have a Note 8 NOT rooted and tried to make SecureTask become a device owner. I followed Option 1 in the instructions to the letter. When, after Factory Reset, I sent the ADB command to make SecureTask a device owner it worked fine and confirmed ST was now a device owner.
I then set up my Google and Samsung accounts. When I try to do a restore of my backup "Samsung account" is greyed out and tells me that the restore is disabled due to security policies. I tried to update the policies manually but it says I already have the latest.
The Google account restore is also greyed out.
After another Factory Reset and starting Google and Samsung accounts normally (without trying to set SecureTask device ownership first) the backups are restored without problem.
Can anyone point me towards a solution, I would really love to use SecureTask...
Thanks
Is the a setting within secure task to enable/disable backups? The play store description indicated there is;
"20) Enable/disable android backup (Android 8+ and device owner needed)".
I don't use SecureTask, but opt for AutoTools instead.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Thanks for the reply. I don't need to use SecureTask to enable disable backups, I mainly need to be able to kill apps without rooting. My problem is that after properly installing SecureTask with device ownership, I can't restore my phone due to Samsung security policy. I could start from scratch but I am afraid that the security policy will cause problems later on as well... I'll have a look at what AutoTools allows to do...
My point was, if SecureTask can toggle the ability to back up accounts, then maybe it's incorrectly configured causing your problem.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
It's possible, I am not sure as I didn't open the app, I only side loaded it before trying to restore... I looked at auto tools you recommended and I was able to make a kill.app profile (no root), which solved my current problem. I would still like to use SecureTask for its other options if I can get around that Samsung policies restriction...
Happy Holidays to every one.
Problem solved
The developer of the SecureTask plugin answered my question on his forum and, as it can be useful to other people, I am posting it:
"Default Android behavior: after device owner installation backup/restore is disabled. Solution: after installation and after you granted permissions, use the backup plugin action from Tasker to enable the backup service."
This was also what Ktmom wrote to me but I had not fully understood his reply right away...
Problem solved, thank you! :good:
ktmom said:
Is the a setting within secure task to enable/disable backups? The play store description indicated there is;
"20) Enable/disable android backup (Android 8+ and device owner needed)".
I don't use SecureTask, but opt for AutoTools instead.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
You were right, I should have used the option to turn Backup On of OFF... I did not think of doing it when I tried my installation as I had read too quickly the description of what the plugin could do (my interest was in the first items listed so I did not go to the end of everything it could do ) and when you posted your reply I thought it was an option to use after the phone was restored and not before it was restored! The developer replied to me on his forum and explained that it is a normal Android behavior to have backup disabled and told me this is what I had to do. So, even though you are not using SecureTask plugin, you had the exact right answer, sorry I did not understand it immediately! You have been a great help. Thanks and happy New Year!
Samsung owners read this!
TheEarman said:
You were right, I should have used the option to turn Backup On of OFF... I did not think of doing it when I tried my installation as I had read too quickly the description of what the plugin could do (my interest was in the first items listed so I did not go to the end of everything it could do ) and when you posted your reply I thought it was an option to use after the phone was restored and not before it was restored! The developer replied to me on his forum and explained that it is a normal Android behavior to have backup disabled and told me this is what I had to do. So, even though you are not using SecureTask plugin, you had the exact right answer, sorry I did not understand it immediately! You have been a great help. Thanks and happy New Year!
Click to expand...
Click to collapse
Warning to Samsung owners: if you have a Note 8 or similar model (S8, S9...) there is a big problem. After following the instructions to make SecureTask a device owner, resetting and using the Backup ON-OFF option, the GOOGLE BACKUP works fine and can be used to restore the phone (but not including the folders and their location).
However the SAMSUNG BACKUP still does not work! The SecureTask plugin developer says it must be specific to Samsung and he does not know how to fix it.
As Samsung Backup is much better than Google Backup (it fully restore with folders and icons in proper location) and I don't know what else could be affected by the Samsung Backup not working, I ended-up removing SecureTask as a device owner. My main use for it would have been to use the Kill function to close programs elegantly and quickly. I instead use AutoInput which allows the same thing but in a much less elegant way and it takes much longer to process... but it works on a non rooted phone.
I have also tried to Helium but it does not restore the folders either...
If anyone finds a way to unlock Google Backup after installing SecureTask as a device owner, I would love to hear about it. Thank you!
TheEarman said:
Samsung owners read this!
Warning to Samsung owners: if you have a Note 8 or similar model (S8, S9...) there is a big problem. After following the instructions to make SecureTask a device owner, resetting and using the Backup ON-OFF option, the GOOGLE BACKUP works fine and can be used to restore the phone (but not including the folders and their location).
However the SAMSUNG BACKUP still does not work! The SecureTask plugin developer says it must be specific to Samsung and he does not know how to fix it.
As Samsung Backup is much better than Google Backup (it fully restore with folders and icons in proper location) and I don't know what else could be affected by the Samsung Backup not working, I ended-up removing SecureTask as a device owner. My main use for it would have been to use the Kill function to close programs elegantly and quickly. I instead use AutoInput which allows the same thing but in a much less elegant way and it takes much longer to process... but it works on a non rooted phone.
I have also tried to Helium but it does not restore the folders either...
If anyone finds a way to unlock Google Backup after installing SecureTask as a device owner, I would love to hear about it. Thank you!
Click to expand...
Click to collapse
I'm a little late to the party but wanted to share a workaround I found in case anyone else is having trouble accessing Samsung backup with Securetask set as device owner.
I have a S21 Ultra, and after enabling backups via the plugin only Google backup was working. I needed Samsung backup to work so I kept looking around. While what I found isn't automatic, you can't still manually backup and restore from Samsung cloud. The steps are:
1. Go to settings and click ACCOUNTS AND BACKUP
2. Select MANAGE ACCOUNTS
3. Select your SAMSUNG ACCOUNT
4. Select MY PROFILE
5. Select SAMSUNG APPS AND SERVICES
6 Select SAMSUNG CLOUD
Once in Samsung Cloud you can manually backup and restore your phone as normal! It seems Samsung only greys out the menu shortcut in settings without actually disabling the Cloud. I hope this helps someone!
Hi,
Does anyone have any screen flickering with the Oppo Find x3 Pro? If yes, is there any fix?
Mine is doing the flickering when used at 120Hz Refresh rate, I've attached a short clip with the issue.
It seems that the issue is related to the gallery app, also the scrolling is very slow (60Hz is smoother and faster). I've tried a random gallery app from Play store and works just fine. Can anyone do a port of the OnePlus gallery app?
Thank you!
Just tested, with c47 update, Dark Mode Enabled, 120Hz and I have no flickering issues with Oppo Gallery app.
But by default I use Google Photos app.
Quick update
I've contacted Oppo and this was their reply:
By the situation described by yourself, this matter is being addressed and some handsets are receiving an update specially for this screen flickering. Also, each handset is used on different SIM providers, so this means the update is not received in the same time. Please open Settings>Apps>App management> Tap the 3 dots top corner right>Show System> Type in the search bar “Software update”> Storage usage> Clear data and Clear Cache please. After this, please also restart the handset. Rest assured there is no need to request a repair, as this aspect has been addressed, but please also understand that the update will be received shortly, and the most important is that the screen has no faults developed.
Update :
After using TunnelBear and changing location to Belgium I was able to update the phone and after a few restarts the issue was fixed. Hurray!