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
(First off, I'm not 100% certain that this thread is in the right place. Devs, please move if necessary.)
I have a SM-T210 that I have recently flashed the NoleKat_v2.1 (KitKat 4.4.2) build on, and while I'm 90% happy with it, there is one small annoying thing that is bothering me and I wanted to see if there was a work-around available that I don't know about and/or whether I'm doing something wrong.
One of my favorite features of the Galaxy Tab, something that I had learned to lean on, was the autocomplete function. I know this new build has the autocomplete--I've found it works on SOME of the functions, but ONLY certain functions. It no longer works in email, Facebook, or several other apps where I found it useful. I have gone through my settings and can't seem to find a control to turn it on or off.
Any input would be appreciated.
I found the "Android Auto Complete Tutorial" on the tutorialspoint website. (I'd post the link, but XDA does not let me post outside links because I've posted less than 10 posts). I was wondering if their tutorial could be used to make autocomplete work on my Galaxy Tab.
Update 09.12.17: The methods below may not fully work on the latest OS versions. There is an ongoing discussion in the last pages so I hope it gets cleared out eventually, sadly I've been busy with my studies and haven't touched my phone since initially making this thread (it's on OOS 4.0.2). I write this just to make sure I don't waste your time accidentally, so please check the latest replies if you're on newer OS versions.
Hello everybody,
*the undermentioned methods and app(s) require root*
I have asked you guys in the AKT thread if you would like to see a small tutorial on how to stop the constant "com.google.android.gms/.measurement.PackageMeasurementService" and "net_scheduler" wakelocks that might or might not be responsible for the device waiting longer than it should before dozing off.
Please keep in mind that this method does work for me, and might or might not work for you, as everybody uses different things/apps so in case you see unwanted behavior, just revert back and sigh that the method has failed you.
I am not responsible for any hardware-/software damage that may occur upon using these settings.
So, now that we've got all the generic stuff out of the way, first few words about why this might bother you:
1) You don't like your device doing stuff you didn't make it do.
2) You want to minimize wakelocks
3) You're here because you just saw the two beforementioned wakelocks and already decided you want to get rid of them.
So, regarding the first one, all I can say is I got the method from this reddit post , which briefly explains which services are doing the waking and what they are. Starting with "At the heart of Firebase is Firebase Analytics, a free and unlimited analytics solution. .." got me raising an eyebrow, as I don't like handling control of my device to other people, without me even knowing.
UPDATE: I have merged the two approaches into just using one app and making the changes on a global level, so you can just do them in like 5 minutes and forget about it, but in case you have problems with disabling package measurement you can also check the hidden text just below for instructions using another app, which was basically "the old way".
So to get rid of the "snooping", as already described in that post, you need to download MyAndroidTools.
Disclaimer: Disabling some services/receivers may "crash" the app. I found it is normal, just go back to where you were and check if you managed to disable the thing you wanted, if yes, then it was successful.
1. Open the app
2. Click on the top left to open the panel, click on Broadcast Receiver.
3. On the menu that opens go to the right column named System. Click search on the top right, type "Play" and choose the Google Play Services option.
4. In the search bar there type at least "ana" and disable the two found results with the names "AnalyticsReceiver" and "AnalyticsSamplerReceiver"
5. Hit x and search again for at least "meas". You will see three results with the names "AppMeasurementInstallReferrerReceiver", "AppMeasurementReceiver" and "PackageMeasurementReceiver*". Disable all three.
****Update 15.02.17*** Apparently this one resets every once in a while, I blame this again on Google's efforts to have their spying on, but anyways. Go to services->system->Google Play Services->search "meas"->disable both "AppMeasurementService" and "MeasurementBrokerService". The third one (PackageMeasurementService) will restart too so don't bother. This should do the trick though.
6. There was discussion about "Campaign Tracking" . I only found it in the same System menu, in Android Pay, by searching at least "cam" you get the result "CampaignTrackingReceiver". Disable it if you feel you want to. I don't use Android Pay and cannot say if it breaks something there, but otherwise have it disabled and haven't noticed any problems so far.
7. Search for Google Play Store in System. In that option, search for at least "app" and disable "AppMeasurementReceiver". Hit x and search for at least "fir", then disable the two results with names "FirebaseInstanceIdInternalReceiver" and "FirebaseInstanceIdReceiver"
8. Done. All the setttings are now global for any sort of app measurements, as far as I know.
This is the "old way" of dealing with app measurement. If you have done the steps above just ignore (hide) this part and continue with disabling net_scheduler below.
So to get rid of the "snooping", as already described in that post, you need to download Root Package Disabler or equivalent alternative.
ATTENTION: As per the last version of the app, I see there might be a bug which reverts some settings when you use the search bar, so please try and find the services by hand in stead of searching, as it is more reliable.
1. Open the app
2. Start with the left-most pane, e.g. "Installed". There you can see all your installed apps
3. Click on the first app on the list, it will display a small menu. Apps that use services will have the bottom-left option named "SERVICES" available, click there. This will take you to the services list that this app uses.
4. Click on the searching icon on the top-right in order to filter the services we need disabling.
5. Write at least "appm" . If the AppMeasurementService is used by this app, it will now be displayed.
6. Tick that off (the switch will turn gray)
7. Hit x, and search again for at least "fireb". This will display all services that use the Firebase SDK. You may also check under the name of the service and see the word is contained in the "executable name", so it might not always have "an official" name that states Firebase, but still use one of their "executables" (sorry for lack of detail)
7.1 Check for any other services that have "analytics" in their description, although I haven't checked if this stops something useful, but I doubt it.
8. When you're done with the current app, it will no longer call these services and cause wakelocks as long as the services remain stopped. To my experience the settings stay after reboot, it's just the above mentioned bug you have to keep in mind since it happened to me now while making the guide, and I know it came with the latest update.
9. Go back to the installed pane and maybe tick on the star next to the app in question. It will be added to the "favourite" list where you can have all those apps and don't bother to search them again if needed.
10. Repeat from step 1 for the next app and go through all your apps. If not you will still get calls to this service from the apps that still have these services on. Also a reminder here, you have to remember and check every new app you install, as most apps do have the service enabled.
11. After you're done with all apps in "Installed", check out bloatware (I think I haven't found anything there, but it's worth checking).
12. "System" apps that I know have some of those services: Calendar, (probably) Chrome (I have that disabled so dunno), Drive, Duo, Gboard, Google Play Services, Google Play Store, Google VR Services.
Here are two pictures how an app's services list looks like, and one with some of the services disabled:
all services on
some services off
After doing these steps, you should charge your battery to 90% to reset the battery statistics and you should see that the "com.google.android.gms/.measurement.PackageMeasurementService" wakelock no longer occurs (or stays really, really low, and not thousands like before). If you still have it after all this, then you probably have an app you haven't disabled the services for.
The second approach will get rid of the "net_scheduler" wakelock. Thanks to @denon480 for the idea, it's post #34 in this thread It involves installing (again) MyAndroidTools or equivalent alternative.
1. Open the app
2. Click on the top left corner to open the menu panel.
3. Click on Broadcast Receiver
4. Navigate to the System pane
5. Click on search on the top right. Search for Google Play Services. Click on them when they show up
6. In the search top right, write at least "sche" and you will see the two receivers responsible for the "net_scheduler" wakelock, "SchedulerInternalReceiver" and "SchedulerReceiver" . Here's a picture how it looks
7. Switch the first one off. The app will quit, don't worry.
8. Go back to where you were (steps 1 to 6) . You will see that you indeed managed to swtich that receiver off.
9. Switch the second one off. The app will quit, again no worries.
10. Check if you managed to switch the second one as well. After that you're done!
I hope I could help you guys out. I know there is nothing fancy in these methods but felt a thread might be useful as I saw a good number of requests when I mentioned it in the AKT thread.
Also sorry for misleading the guys I already told it was going to be a short guide, I honestly thought it would take way less words than it did. But I think it is for the better.
Have fun.
* Reserved *
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
MeggaMortY said:
* Reserved *
Click to expand...
Click to collapse
I think Everything is fine or?
tzbigworm said:
Going through this guide, I was able to get the services disabled through root package disabler, bit my android tools kept force closing for some reason.
*edit* uninstalled, rebooted, reinstalled, and was able to get the app to stay open, and got them disabled. I'm curious to see what my wake locks are going to look like tomorrow. This is pretty much the nougat answer to amplify, huh? =)
Click to expand...
Click to collapse
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
1+3_FA said:
I think Everything is fine or?
Click to expand...
Click to collapse
Yup looks great.
MeggaMortY said:
Hope it gets rid of those for you too. If I remember correctly I noticed the problem since Nougat, but then again I've been on Android since only a few months, coming from a big pause. Last time I was around we were rocking the HTC HD2 and had to deal with very different problems.
Click to expand...
Click to collapse
Crazy how much of a beast that phone was. People forget it's actually a windows phone, Android was put on it so much lol!
Thanks for the tips. Works great!
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
youknownothing said:
Thank you for your awesome work!
I have two more questions:
1. What about CampaignTrackingService? Could we disable this one as well?
2. In MyAndroidTools under Broadcast Receiver there are lots of receivers like AppMeasurementReceiver or FirebaseInstanceIdReceiver. They also need to be disabled or disabling the corresponding service is sufficient?
Thank you very much
Click to expand...
Click to collapse
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
MeggaMortY said:
1. I initally disabled that in a few apps and didn't have problems System-wide or with the apps. So you can give it a go and in case of apps not functioning you can revert those back.
2. No for now it's okay to just use the Package Disabler for that. Like I said both apps have similiar functionality, there's probably a way to find the right service/receiver and disable it globally from MyAndroidTools, then we won't need the Package Disabler. But since it did work for me and I don't install new apps more than like once a week, I just didn't bother figuring it out. I can only say that disabling certain services/activities in MyAndroidTools can brake functionality or even bootloop your device, so be very careful in case you wanna find out if it's possible.
Click to expand...
Click to collapse
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
youknownothing said:
Thank you for your quick response. I'll give it a try, if anything goes wrong I'll let you know.
Is there any difference between Package Disabler and Disable Service app? I've tried the former, but it was really buggy. Scrolling was so glitchy and with lots of stutters that I've accidentally disabled few services. So I've used Disable Service with success. Now I only wonder whether both apps have the same functionality. Do you happen to know that?
Thanks in advance
Click to expand...
Click to collapse
Assuming you're disabling services, which we are lol (should've been more obvious for me too I guess), I'd say you should be fine, and even say maybe the same goes for just using MyAndroidTools, just scroll through the Service menu in Table Third-Party and you'll see the same settings you applied with the other app/Package Disabler. I guess I was lazy to realize that since I liked I can favourite the apps I need to keep an eye on in the Package Disabler.
So all in all you should be okay, but even better you may try and just use MyAndroidTools for both. I have some exams coming so I won't be able to test those things but will make sure to update the tutorial if indeed that turns out to be right (for the app you suggested or even just MyAndroidTools).
Give a shout in case you find out something more. And thanks for the info
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Mr.Jay said:
I suppose that this two methods doesn't compromise any function of the device right? For example loosing notifications or similar
Sent from my OnePlus 3
Click to expand...
Click to collapse
Like mentioned, it works fine for me, and probably depends on personal usage. I don't use Google Pay for example, and Chrome, and Google Music.... but besides those I haven't had problems anyway.
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
NJGSII said:
Disabled everything that is said to do in this thread and it worked great while I was at home while on wifi. I had drain of .5% an hour at times. However today while at work and on LTE, drain went up to 2.6% an hour, plus wakelocks from play services was waking up the device on average over 3 times a minute. When I looked into it further there was one service under play services where all the alarms were coming from. I do have a screenshot of this. Anyone have any insight to this? For the record, I do keep location off on my device.
Edit: I wonder f it comes from moving around a lot, as I'm always on the move as I manage a restaurant. Its not really a major drain, but still makes me wonder.
Click to expand...
Click to collapse
Have you disabled location history in the Google App? The problem is this guide fixes only one concrete aspect of the whole "Google stalking experience" shenanigans. Please check for the thing I mentioned and also in Settings -> Backup & Reset, make sure Back up my data is off if you haven't logged in an account and intend to use that - these two things were also draining battery for me when I was on the go as far as I can remember.
LMcR92 said:
Followed the guide, thanks for this like said before kind of amplify for nougat. But as I was disabling net.schedule I noticed "my android tool" can do the fire base and app activity. Under service activity and press <...>
Click to expand...
Click to collapse
I did some checking on that list and am currently testing a way to only use MyAndroidTools for the whole aproach. If it turns out to be working the whole guide would get reduced to like 10 clicks, since the settings are global. I'll post more info after a day or so to make sure it is working, but as for now I see promising results.
Anyone used Franco's Servicely app to do this?
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
MeggaMortY said:
Up, I have updated the guide to just using MyAndroidTools and disabling the receivers on a global scale. So now you just have to do it once and (hopefully) forget about it.
Click to expand...
Click to collapse
Will Doing like #1 post notifications from Gmail?
techusthad said:
Will Doing like #1 post notifications from Gmail?
Click to expand...
Click to collapse
Don't know what you mean by #1 - disabling the AppMeasurement stuff, e.g. first set of instructions? I haven't had problems with Gmail and I use it with two accounts on there.
Hello folks. I've been reading a lot to fix this issue but no luck yet so I come to you. I have a Pixel 4XL running android 11, and a smartwatch brand Haylou Ls05, with the apk Haylou Fit.
The thing is I cant set the proper permissions to use the location services in the background. Mi GF has a android 10 phone and no problem.
I already tested everything I founded over the internet and nothing works. When I start running, the app goes good until the screens is off and the tracking of the running gets lost.
Any suggestion? Thanks in advance!!
Are you running without your phone? This watch doesn't have any GPS chip or functionality, so it is not going to track your location or track your your route by itself. Sorry if this was obvious already but I don't know what your use case is. On Android 10/11 you can control the location use on a per-app basis. If your watch app uses the newest API and supports this function, you will see under the Haylou Fit app permissions>>location the following: (Allow all the time/Allow only when using the app/Ask every time/ Deny). If you don't see this option in your app settings then the app itself needs to be updated. It's not the phone that is the issue, but the app. See the screenshot attached. Android 10 has this same functionality, so I'm not sure why your GF's is working correctly and yours is not. You may try removing and re-installing? Please post a screenshot of what you are seeing under location permissions for this app. Cheers.
Thanks very much for your answer. Yes, I run with the cellphone to use the gps of it because the watch does not have gps. Sorry i'm not very familiar with API, but I understand now that it is a problem of the app itself and not of android. My screenshot doesn't show the "allow all the time" item, as i would like to.
Any way to force it? like patching the app o magisk or something I could do? I like this watch very much , its small and light, and would really like to be able to use it..
Thanks you for the answer.
Agustín.
agucasta said:
Thanks very much for your answer. Yes, I run with the cellphone to use the gps of it because the watch does not have gps. Sorry i'm not very familiar with API, but I understand now that it is a problem of the app itself and not of android. My screenshot doesn't show the "allow all the time" item, as i would like to.
Any way to force it? like patching the app o magisk or something I could do? I like this watch very much , its small and light, and would really like to be able to use it..
Thanks you for the answer. Agustín.
Click to expand...
Click to collapse
Not that I know of. I still would like to know why the app it works on your GF's phone (10) and not yours (11) because they both have the same location security options. Is the "always" option available on hers, or is it working on the "when app is running"? Running the same version? This may be related to the API used by the app and until the dev updates it, it will not work. Try contacting the dev? Contact info is available on the Google Play Store.