I've run into a problem, that seems to have happened since updating to 1.8.3, but I am unsure if it happened immediately following update or not.
Whenever my phone is docked in the vehicle dock, when I press the 'home' button, the screen just flickers and does not go to the Car Home application. It just stays on whatever application I have active at the time. I have to go to the drop down menu and select the option to open Car Home instead. Cannot figure out how to fix this or have found any resolution on these forums.
Possibly relevant info:
Phone is 1.8.3, rooted with Gingerbreak.
No additional Car Home application installed.
Tasker set to deactivate lockscreen when docked (any type)
Tasker set to turn on bluetooth, max media volume, turn off notification volume and turn on GPS when docked to vehicle dock.
No settings have been changed since the 1.8.3 update.
Anyone have any ideas?
Related
The Bluetooth button on the phone screen (during a call) has never worked for me. To turn on bluetooth I have to go back to home screen and turn it on from there. Is this only my phone or is this true for others?
drraypalmer said:
The Bluetooth button on the phone screen (during a call) has never worked for me. To turn on bluetooth I have to go back to home screen and turn it on from there. Is this only my phone or is this true for others?
Click to expand...
Click to collapse
I haven't used Bluetooth recently, but as an option you could also put the Bluetooth widget in the strip of notifications power widget, available when you pull the notification bar down. More convenient than on the in-call screen anyway.
Configure what widgets are present and what order they're presented in here -> Settings/CyanogenMod settings/Interface/Notification power widget
From there choose "Widget buttons" to choose what widgets to show, and "Widget button order" to change what order they're shown in.
Hint: If you unchoose all the notification power widgets from the "Widget buttons" menu, and then re-choose only the ones you want and in the order you want them, you won't have to re-order them in the "Widget button order" menu.
Thanks, I actually had the button on the notification screen, just hadn't thought of using it during a call yet. Good idea! I'm still curious why the in-call button doesn't work, but this will make it easy enough to turn on.
Just flashed from GSBv2.2G to GSBv2.5 this morning and haven't tried that bluetooth button on the phone screen yet.
I'm using the notification power widget and it works like a charm. Super fast compared to stock.
drraypalmer said:
Thanks, I actually had the button on the notification screen, just hadn't thought of using it during a call yet. Good idea! I'm still curious why the in-call button doesn't work, but this will make it easy enough to turn on.
Click to expand...
Click to collapse
You're welcome! Probably just an oversight in the CM7 development.
When I have the dock on the Prime I use it like a laptop. I can't wake the tablet using the "lock" key on the keyboard though - it only seems to lock, not unlock (no toggle).
And the tablet doesn't wake automatically when I open the clamshell so I have to push the button on the top.
Is there an option somewhere I'm missing? I'd like to be able to wake it either from a keyboard shortcut or whenever I open the clamshell!
both said functions are present on my tf prime out of the box. I also don't recall seeing any settings that manages these. maybe something is wrong?
It should automatically come on when you open it from the dock. If it isn't doing that, it's possible your dock is not working as it should. Maybe take your TFP to somewhere that has a dock in stock and try it out there.
Other than that, if you enable the power savings mode for the dock under Settings -> Asus customized setting -> MobileDock Battery saving mode then it won't wake up with any key presses, but it will wake up with touchpad clicks unless you've disabled the touchpad via the 4th button from the top left prior to hitting the lock button.
Thanks guys! I'll take the dock back and get it swapped. Obviously something is amiss.
agentdr8 said:
It should automatically come on when you open it from the dock. If it isn't doing that, it's possible your dock is not working as it should. Maybe take your TFP to somewhere that has a dock in stock and try it out there.
Other than that, if you enable the power savings mode for the dock under Settings -> Asus customized setting -> MobileDock Battery saving mode then it won't wake up with any key presses, but it will wake up with touchpad clicks unless you've disabled the touchpad via the 4th button from the top left prior to hitting the lock button.
Click to expand...
Click to collapse
thanks for pointing that out. it really helps to be able to wake it up without reaching for the tiny power button. One thing tho, if i press the touchpad, it wakes up to the lock screen, but if i press any key on the keyboard it wakes up unlocked. is this normal?
I always used "Car Home Ultra" as car-app on my S4. I triggered "carmode" on my S4, after which it tried to launch the default carmode-launcher. So, whenever you pressed the Home-button in Carmode, the carmode-launcher (Car Home Ultra, in my case) is shown, instead of the regular Touchwiz-launcher.
The problem: carmode can be triggered on the S6 (for example with Tasker), but it does not ask for the default carmode-launcher. When I open Car Home Ultra, it flips back to Touchwiz as soon as I press the home-button. Samsung's own Cardock-app, named "Car Mode" cán do this trick (opening at the press of the home-button when driving), but I do not like it due to limited capabilities.
Did anybody else get their Cardock-app to function as the default launcher when in Carmode?
https://play.google.com/store/apps/details?id=spinninghead.homepatch
Thanks, you just made my day!
No problem.
My phone froze on me and I put out the battery but I noticed that :
1. I cannot receive calls. I can make calls, but when anyone calls me, it will ring twice on their end and then go to voice mail. My phone does not react at all.
2. My phone will not use the security grid. It will not enable either by widget or by going to the phones menu > security and enabling it. You can enable it, power phone off and back on and it goes right to the desktop. No lock screen period.
3. The home and search buttons on the bottom of the phone do not function. They vibrate like they are working but will they will not do anything.
4. And finally, when doing a long press on the power button, the airplane mode and other options do not appear. The only option available is the "Power Off" button.
Please, if anyone has experienced this or has an idea on how to fix this issue or what caused it, please let me know.
My Chromebook used to turn off the screen anytime I pressed the power button. I often use it to type notes during presentations, and I loved having a fast easy way to turn off the screen to save power if I knew I wouldn’t be typing anything for 5 or 10 minutes.
A few months ago, a ChromeOS update changed this so it only works it tablet mode now, pressing the power button in laptop mode now opens an on-screen menu with options to shutdown, log off, or lock screen. The best workaround I have found so far is to use the brightness keys to get the screen off, but it’s a pain to get it back to the right brightness level every time.
I have the Chromebook in developer mode, and I would like to do one of the following (in order from most to least preferred):
1. Restore power button functionality to how it was before.
2. Re-purpose the lock screen button on the keyboard for turning off the screen.
3. Add a keyboard shortcut to toggle the screen on and off.
4. Add a “Turn off screen” option to the current on-screen menu.
I never really modified ChromeOS before. Has anyone else done these things? Where should I begin? Thank you.
Here is some relevant documentation, maybe the information at the bottom is useful?:
https://chromium.googlesource.com/chromiumos/platform2/+/master/power_manager/docs/power_buttons.md
I was able to do it by adding the flag "--force-tablet-power-button" to /etc/chrome_dev.conf and restarting the UI, but changes to that file don't seem to persist accross system reboots.
edit: I used the instructions at the bottom of this page: http://www.chromium.org/developers/how-tos/run-chromium-with-flags