Is there any way to stop the screen from detecting input during a call? There was on the 650 (Palm OS) but I can't find an option here.
Found it - the option was under the KeyGuard app in Utilities.
Related
Is there any way I can stop SMS previews in the lock screen? It is PIN protected (standard windows.. Settings -> Lock -> Simple PIN) but still shows my messages on the screen. I don't want it to do this, otherwise I wouldn't have used a PIN in the first place!
I have tried unchecking (Sounds & Notifications -> Notifications -> Message : New Message -> Display message on screen) but this makes no difference.
What can I do to stop this? Thanks
Anyone
I've had this Samsung S3 for six months now rooted with stock AT&T JB ROM. I'm starting to use the phone in the car more and am perplexed how difficult I'm finding it to do some pretty simple, commonly useful things. Here's what I'm trying to achieve:
- When phone connects to bluetooth in car, to on Car Mode and Driving Mode
I already use Llama and turning on Car Mode is easy. Driving Mode looks like I have to use a custom Android Intention (haven't tried it yet)
1. Replace lock screen (currently using Widget Locker) with Car Dashboard for easy app launch and forwarding of songs being played in Power Amp, Spotify or Pandora. Strange that Llama toggles Car Mode but the toggle on the OS is "Driving mode" Seems Driving Mode controls TTS activation and Car Mode toggles the Car Mode app. I think this is just the problem with Touchwiz not being "Android Standard" functionality?
2. Make it so I don't have to press a button to wake phone but don't eat battery with screen usage. The only Car app I've found that comes close to this is the iBOLT Dock'n Drive app where you set the screen brightness slider all the way down and it just shows a clock jumping around the screen. I don't even want the stupid clock - but I guess it's nice to know the phone is in car mode waiting for me to touch the screen. Unfortunately music controls are not on this dash app and the Car app with Pandora integration (forget the name) doesn't have the blank the screen mode without sleeping.
3. When a text comes in, I want either (a) and auto-response that I'm driving and to call me if its urgent, or BETTER, (b) allow me to speak "reply" and do a voice to text response or "auto response" to send my auto response. S-voice allows you to say 'reply' but only if the text comes in when the S-voice app is the currently opened app. If phone is sleeping and text comes in, all it does is read the text. Disabling widget locker and having no lockscreen slider made no difference.
Sidenote: I've also discovered on the S3, because I don't use S-Voice, (I have home double tap mapped to Google Voice Search), the TTS doesn't work. If I manually launch S Voice once, then TTS works but if I remove it from the background apps list then no TTS. That's sort of a side issue.
4. If car mode is enabled, on GoSMS I don't need a pop-up. Just TTS. But GoSMS still thinks I haven't seen the message. So even though I heard the message GoSMS keeps pinging me with a reminder (which I do want repeat reminders for unread texts when NOT in car/driving mode) Strangely there is no Car/Driving mode settings in GoSMS. Surprising. And the Auto Response has to therefore be manually toggled.
It appears I may have to add some 3rd party apps to achieve what I want and possibly dump GoSMS - I've also found that CloudSMS (to replicate SMS to my tablet) doesn't work with GoSMS running. Boo. Hiss. I GoSMS is such a superior SMS program in most all other respects. Hate to see it go.
Seems what I'm asking to do shouldn't be so complicated. With all Google's resources, I'm surprised this isn't all built-in to Android and easily used.
Getting close. Turned off option on GoSMS to disable other messaging notifications (fixed CloudSMS issue).
Found two promising apps:
SMS+Car - Does the job but the it doesn't use the native Google voice recognition and more importantly doesn't read calendar reminders. What it DOES do is mark the SMS messages it reads as read!
Enhanced SMS + Caller ID+ - This is the better app, it cleaner, more options, used native Google voice recognition. It's missing one thing though, DOESN'T MARK THE SMS AS READ! Dealbreaker.
Search continues...
Is there a way to lengthen the "time on" for the lockscreens w/o entering password?
Title asks it all 8)
Looking to extend the awake time for the lockscreen while it's waiting for one to enter the password, unlock pattern, etc.
EDIT: Reason being - while using the Xposed Quick Access module it would be nice if the screen didn't off itself after a couple of seconds whilst I'm reading whatever info I have set for Quick Access-ability.
Thanks!
Sooo... I think I've solved this issue with a Tasker task. Tested with an n = 1 data set, but that one was a success. Looking forward to future testings to see if this works and solves the issue.
For those interested - in Tasker, I set up an app profile and triggered screen on, never timeout while that app is open / on-screen. Not the most perfect task since I'll have to actively remove the app from the screen for the phone to operate the lock function as normal, but I think it'll work for what I was hoping to do.
- Using Xposed Notification mod, I can pull down the notification menu down when I receive a new notification (an email for example).
- Or even better, using the Dynamic Notifications app I can open the email straight from the dynamic notification (similar to the function found on the Moto X for those not familiar).
- Then through the Xposed Quick Access mod, the email opens right over the lockscreen without going through the whole unlocking the phone process saving a few motions, clicks, etc.
- Then the Tasker task takes over and keeps the screen on whilst I'm reading / responding to the email, then when I delete the email and the lockscreen appears, the Tasker task ends and the screen goes back into default screen off / timeout mode.
Hopefully this will help someone else out in the future, or give someone else another idea! 8)
What i have been trying to do is create somewhat of a script that i can run on my windows machine with my android device connected and have it install an apk and set device settings such as:
- WiFi: SSID and Password
- Display Settings: - When device is rotated and change to the second option (can't remember which one it was)
- Sound & Notification Settings: Blocking gmail and not displaying notifications on the lock screen
- Security Settings: From swipe lock to none
So far the best way i have found of automation this is using a chrome app called Vysor that connects to my Android device and lets me control it from my computer, then using AutoIT i use the X,Y positions on the screen to make the click and then use the "Send()" function to send keys such as passwords and so forth.
Surely there is a better way to do this does anyone have any idea?
When the phone is asleep and someone is calling, it is all ok. So just like in the screenshot number 1
The incoming dialer appears normally.
However, when he unlocks the phone and the desktop is displayed, when someone calls us, the incoming call dialer does not appear. It is like in screen number 2. There is only a bar with "Reject /" Receive "call notification
This notification pops up after 3-4 seconds of delay from the ringer
This happens on every phone app.
Actions taken:
- Removal of application data
- Cache removal
- Reinstallation
- Disabling the system dialer and installing another (Google Phone)
- Setting of notifications and appropriate selection
- All permissions granted
- Proven "Do not disturb" mode
The whole problem arose after the OSS11 Stable EU update
Nothing helps
Anyone have any idea?