I've just installed QuickSpell from MobiSystems on my Nexus. When I go into the Language & input section of Settings, and change which spell checker to use, my selection is not "sticky" - the setting reverts to the Android default.
When I make the selection of QuickSpell, I get a verification dialog box - "Attention! This spell checker may be able to collect all the text you type, including personal data like passwords and credit card numbers. It comes from the app QuickSpelll.Use this spell checker?" (doh! isn't that what I just selected?)
I select "OK", of course, then go on to do whatever I was going to do.
When I power off, then power back on later, this setting reverts to the Android default. It does this even if I disable the Dictionary Provider app, which seems to re-enable itself too when rebooted.
Another similar odfity in the Language & inputs settings is the "voice typing" option. This too is not sticky, even if I have all the voice-related apps even if I have all the voice function apps disabled. I'm not sure if any of these are re-enabled by reboot, but I suspect so since I know I have had to disable something(s) off this sort repeatedly.
The only system-level type modsI have is the Nova launcher. I run Lookout Premium for security, but I know that that is not the source of the problem. They quickly replied to my email about this and said that Lookout does not make changes of any kind to any settings. They merely detect what apps do in re: privacy and report on their behavior, letting the user decide whether to uninstall or continue using apps that can/do access potentially private data, include Lookout itself.
Having to re-enable QuickSpell as my default with each reboot is a pain in the fingers (carpal tunnel, you know, from a zillion years as a now-retired software engineer. A new keyboard app is next, since I really hate this one. I'll take suggestions on that too.)
Becky
Related
I like many Android users use the the WidgetLocker app for its vast customization, functionality, and practicality. However the one glaring flaw that causes great frustration to many is the fact that it doesn't work well (or at all) with the Android 2.2+ pattern lock. Well after playing around with it and some apps from the Market, I might've found a solution to the problem. It's rigged up, but it works well with a couple of caveats; here are the steps to do it:
1. Obviously make sure WidgetLocker has been downloaded from the market and enabled. Make sure "Appear on boot" is checked in the "Behavior" setting.
2. I have it set on a Custom Timeout, but I'm not sure that'll affect it or not. (Once I got it to work I didn't wanna screw with the settings lol )
3. Under the "Advanced" setting, make sure "HomeHelper Component" is checked and that "HomeHelper's Launcher" and "Select System Home" have been set to the WidgetLocker HomeHelper and your launcher of choice respectively
4. ***For Rooted Users, Make sure "Root Helper" is checked (I also have the last 4 settings checked after "Always unlock to Home" which is under "Root Helper"
5. Once that's completed goto the Market and download a FREE app called "AutoLock" by mooapps
6. Once downloaded and installed, open it, make sure its enabled and set the Automatic lock delay to 10 seconds (This confuses the system lockscreen timer for some reason, but it confuses it long enough to allow WidgetLocker to work properly, but not enough where it overrides the pattern lock)
7. Set your pattern lock to your desired time and enjoy!!!
CAVEATS
- This is clearly not affiliated with TeslaCoil Software lol
- I don't know how to get it to startup automatically when you turn on your phone
- I don't know if this'll work with the pin lock or password
- I don't know if this'll even work for your phone, but I know it works for my Droid X
***If anyone else would like to test this out and add to this thread that'd be awesome or if anyone finds an easier way then by all means share the wealth of knowledge
Hopes this helps all of the frustration with this otherwise great app!!!
[UPDATE!!!] It does do a weird thing when you try to interact with the notification bar, it goes back to the regular lockscreen, BUT you don't have to go through 2 lockscreens to do it
Hi all,
Just out of curiosity. I have a 3rd party app on my phone (not available on the Google Play Store, obviously)
I am currently running Android 7.0. When accessing the settings - - > apps--> theApp--> permissions where one can adjust the permissions on demand, I noted that the "Telephone" permission for this specific app cannot be switched off.
When selecting to switch it off there is the usual prompt that the app won't work as intended and I "continue anyway". The slider goes into the off position. Then when clicking back and then opening the permissions, the Telephone permissions switch is back into the on position.
What do you make of this? I have suspected that the app is "spying" somehow for quite some time. Reverse engineering on the apk itself had some very strange permissions logged in the Android Manifest file.
I would really like to hear your opinion....
41 views and zero replies....
I received the phone and have been using it since 2/10. I have the 8/256gb version with the Chinese ROM. The phone is awesome with regards to build quality and so on, but I'm extremely frustrated with the issues that I'm seeing daily. I'm ready to ditch it and return to my Xiaomi Mi Mix.
Notifications are all turned off by default and every app notification must be turned on individually. So every new app needs this manual step.
Notifications, even if enabled correctly, lock screen, does not show up on the lock screen
Various apps do not receive new "data" such as emails until opened. (runs in background, just noticed the application freeze option, and turned that off)
Device Administrator removes MS Outlook as device admin regularly, used to be daily. (required by work)
When plugged into USB-C for Android Auto, must change setting to Transfer files, every time in order to activate Android Auto.
Resets Assistive Voice App nightly, removes Google Assistant and elects none, not even breeno voice.
Depending on task, it switches to use the Breeno Browser instead of Chrome as an intermediary and therefore does not fully like to the next task.
Swiping down on home screen brings up breeno search via breeno browser.
Cannot activate Location Sharing Services even if Location is turned on. I think this has to do w/ limitations on the "Region"
Things that I know does not work
Cannot use 3rd party messaging app. Once 3rd party app is set as default, it switches back to Oppo msgs app due to "security"
Cannot use another Launcher.
Cannot use Google Assistant wake up phrase
Can anyone else confirm if you're also experiencing the above? I'm willing to reset the phone but I think these are "defaults" and not like a choice I made during set-up to cause these issues. Thanks for reading.
The issues you mention are common and are part of the challenge of owning a phone with a Chinese rom. The trade-off is that you own a unique phone with awesome hardware.
I have been able to get all notifications to work though adjusting the notification options as you say, but you can also adjust the power saver and start-up options. You can also lock apps in the recent tasks screen.
You can also uninstall some of the built-in Chinese apps via adb. See the thread in the Find X forum. For example I have uninstalled the browser so it never comes up. I have not uninstalled the launcher as I am ok with the Oppo one.
Issues I have not been able to resolve: changing the default messaging and assistant apps for the long term.
For me, I know the experience of buying a phone with a Chinese rom is never going to be as smooth as a pixel or Samsung in terms of usability, but I love the fact that it is unique and appreciate the hardware (eg charging speed).
Unfortunately, the uniqueness of the phone does not overwhelm these limitations that causes daily resetting of certain defaults for me.
I'm ok w/ not using the Launcher and some other items like google assistant. However, other limitations really create barriers that can't be looked past for me.
I think I'll look for an opportunity to get the Xiaomi Mi 10 pro when possible and sell the Reno Ace.
Can anyone explain the various options for "stopping" an app? As far as I can tell, you can:
1. Swipe it off the app switcher screen
2. Long press and hit "Pause app"
3. Long press, tap info, and turn off all notifications
4. Go to settings, apps, and "force stop"
What's the technical difference between all of these? It seems unbelievable that there isn't a simple way to fully stop all processes associated with an app until you manually restart it.
I'm mainly interested in squeezing the last bit of use out of old phones.
Well, I thought this would get more of a reaction. Would it be more enticing if I asked for a more technical discussion on how these functions work?
I know I can Google this stuff, but pretty much everything I come across is focused on the basics of turning off notifications. The most technical content in the articles I've found says things like, apps don't use system resources when they're just sitting in the background and appear in the app switcher. But honestly, that seems ridiculous. If an app CAN send a notification, regardless of whether Android displays it, then it will obviously use resources periodically.
So I'm looking for what actually happens when you turn off notifications, pause an app, swipe it off the switcher, or force close. After that I'll be looking for a tool that will make it easy to manage what I want running.
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
m0d hipp¥ said:
Hello,
I'm curious I can get some help. I have an android box that hooks up to my TV. I have an app I use called "Key Mapper" that allows me to remap my keyboard keys so I can create shortcuts. One of the issues I find with the app is that sometimes I have to exit out of it and reopen it and re-enable accessibility within the App.
In Android Settings I already have accessibility enabled so it should be good, but when I reboot the device it seems to always stop working until I close out of the process and re-open it up.
My theory is that maybe I need to delay the auto boot of the application. It starts up with Android automatically but if I can have it delayed start that may resolve the issue. Is there an app or some way I can adjust the auto boo setting to delay it say 10 seconds after Android loads up?
Click to expand...
Click to collapse
After your OS finishes booting and loads the full OS stack, a system-wide message called Broadcast Intent will be sent to all apps, notifying them that your device has completed booting (this intent is called BOOT_COMPLETED). Then it's up to the individual app to use that broadcasted intent to pre-load in memory whatever they want (or simply not react at all).
The thing is you want to delay auto boot for that specific application, so there are 2 options for that:
you turn off auto boot in the App itself (if it provides such an option).
you block the app from receiving the intent broadcasted.
The second option is also achieved either by using a task killer to force kill the app (which defeats your point IMO) or it manipulate the app from receiving the intent entirely. Both of these options require root access.
If you have root I suggest The App: SD maid (pro version). Under app control you can modify which system Broadcasts that Keymapper recieves (among them could be boot_completed). See attached screenshot from my device for example.
Hope I helped somehow
Thank you for your response. That was super helpful! The device I am playing around with is a Mekotronics R58x, and it had some sort of modified root that was conflicting with Magisk. I read somewhere on these forums that someone suggested renaming the su file if it exists in /system/xbin/su; which it did. I renamed it and rebooted and after that everything worked wonderfully. Keymapper was still autobooting like previously, but this time all the services loaded right up and I didn't have to restart the app it just worked.
Basically I think the issue was this custom su file that was conflicting with Magisk and causing a headache with the keymapper. I'm glad I stumbled across the fix, but either way your post was also very helpful! Thank you!