Database Info

Disabling Bluetooth headset initiated dialing (my own solution)

After searching for hours and hours for a way to disable voice dialing + dial last number function from my Bluetooth headset, i've decided to code my own solution, in a form of AT commands audio gateway extension. Since others may find this useful as well, i am packing it in a cab and posting it here.
All it does is putting a small audio gateway extension replacement DLL (just 4kbytes) in windows directory and changes the MS audio gateway extension settings in registry to use this replacement DLL. All the DLL does is responding with "ERROR" on the voice dial and last number dial commands from the headphone, that it. This does the trick.
To install: install the cab, reset the device
To uninstall: remove using the system control panel, reset the device
As simple as that. No guaranties. It replaces a system DLL functionality after all, don't blame me if renders your device unbootable, unusable, blows it up or even kills you... well, you know the drill, use it on your own risk. I'll be happy if someone else finds this useful.

it is embarrassing when you don't know about calling somebody
I appreciate your perfect solution
installed in kaiser with WM 6.5 OS and nokia BH-102
I tried many things and it is working perfectly
thanks

Thanks worked perfect for my wired headphones with a faulty call button.

Wired headphones?! Are you sure? Cause i would really doubt any wired headphones would allow AT commands audio gateway extension, or, in fact, communicate using AT commands.
But, if it really works... if the system actually simulates those commands and passes those through the extension... maybe i'll finally make my wired remote work with something other than the damn AudioManager program.
I am too lazy to go to my car right now (thats where the wired remote currently is), but tomorrow i am totally going to see if this really blocks the call button on that wired remote. If it does, i am going to see if the other buttons also pass through the extension, and, well, you know whats next. But i really really doubt it, its probably just a coincidence or something.
Thanks for the info.

Yes wired headphones? mine are just cheap hands free ones off ebay but pressing the button does nothing now,which is great it use to dial my last number sometimes without pressing it too.

I tried it on HD2 (Leo) but it is not working
is there any way to let it works on it
thanks in advance

I found the BT audio gateway service not loading the dll on startup on some of the devices. Try installing SK tools, go to services menu, stop the BT Audio Gateway service and then start it again, while having my cab installed. If it suddenly works and blocks the dial button after the service restart, then there may be a 'solution', as simple as making a little app that restarts the service after the device is fully loaded. Not a perfect solution, but well, if it works, then why not.
BTW, can someone point me to the right direction on how to restart WM services programatically ? What API does this ?

thanks for quick response
I tried what you said. I used Task Manager v2.9 the BT Audio Gateway already stopped and I could not start it
it says the system cannot open the device or file specified.
I have replaced the dll file manually and still
when I clicked "find in registry" it is located in HKLM/Services/BTAGSVC
BTAGSVC.dll

Replaced the DLL manually ? The BTAGSVC one ? With mine ?!?! Don't !!!
Read my post again to understand how the trick works. My DLL is by no means not a BTAGSVC replacement. What i means in my last post is that for some reason, when BTAGSVC initially loads, at the device start, it won't load the AT extension DLL (my one). I would assume this may happen because the file system is not mounted yet, or some similar reason, i don't know. And the reason i told you to try restarting the BTAGSVC is to try & see if it helps to start the service when the device is fully loaded.
Again, do not replace the BTAGSVC with my DLL, you can lose the BT audio functionality this way.

no I did not replace BTAGSVC with yours (BTAWGS)
I tried exactly what you have said. I was saying that service belongs to this file as stated in registry.
you told me te restart the service and I told the service is already stopped plus I could not start it for that error
recently I could not find BTAWGS dll file in windows folder
my question: this dll file (BTAWGS) does it exist in the original rom and your cab replace it?
regards

from my readings in this great forum
I think the bluetooth stack especially in hd2 is different than other htc devices and it is has different driver
it is WIDCOMM driver, is that true?
if so that means your file isn't gonna work

If the device is using non-MS Bluetooth stack - there is a near-100% chance my trick is not going to work, sorry.

thanks for the direction
but if I want to edit the dll file
what is the best program to do so
and what is the values that I have to change
can you tell me what you have changed in your dll file

Just in case anyone is still interested, i've now got an HD2 and found a way to disable the bluetooth dial on it. It's a bit nasty/hackish, though. Do the following:
1) Copy the "BTTrayCE.exe" from the device to your PC using any available method.
2) Open the "BTTrayCE.exe" with any available hexeditor
3) Look for "+BLDN" and "+BVRA", replace them with something like "xxxxx"
4) Replace the file in Windows directory with the patched file using any available means.
NOTES: The "BLDN" stands for "Bluetooth - Last Dialed Number", "BVRA" stands for "Bluetooth Voice Recognition Activation", those are, in fact, the AT commands your bluetooth headset sends to the phone when you push that nasty button by mistake.

[MOD] AppRadio Unchained - Full mirroring for Pioneer AppRadio 2 and 3

This mod is not developed / maintained anymore.
The mod is based on an (now) old version of the Pioneer AppRadio app that does not support the latest Android versions and head units.
If it works then it works but if not then you are on your own. There is no support. Also the ARUnchained GPS Injector app is not developed anymore.
To use AppRadio Unchained please get the paid version from the Play store called ''AppRadio Unchained Reloaded".
For details see here: AppRadio Unchained Reloaded
If you don't want to root your phone and have Android 7 or higher there's AppRadio Unchained Rootless
Old information:
=================================================================================================
The Pioneer AppRadio is a radio with a 7" touch screen. Android devices can be connected via HDMI and shown on the screen.
Touches and keypresses are sent back to the Android device via Bluetooth. The radio has a GPS receiver and data is sent
over Bluetooth as well. In essence a very nice concept.
To connect to an AppRadio there's a Pioneer AppRadio app available in the Play store. The Pioneer AppRadio app
is however quite restrictive. It allows only to run a small number of apps that are approved by Pioneer. These approved
apps can interact with the AppRadio app because they have a built in Pioneer SDK. The number of useful apps is small.
For details look here: Pioneer Appradio Knows website.
The goal of this project is to modify the Pioneer AppRadio app in such a way that it allows full mirroring.
This means that any app can be used and controlled using the touch screen and keys on the headunit.
Also any application can receive GPS data from the AppRadio.
Setup guides by RogerH
Pioneer AppRadio with Nexus 5
Setting up Pioneer AppRadio with Android Stick
Links
CNET article that gives a nice overview
Video from Steven Solazzo
Video from SinisterC6
Video from Neil Fontamillas
Video from M Sylvester showing AVH-4000NEX working
Video from M Sylvester showing AVH-8000NEX working
Video from M Sylvester showing Samsung Note 3 hardware setup
Video from Pascal H showing ARU in action in a Porsche 997 Turbo (in French)
Current status of the AppRadio Unchained Mod (free)
Beta release 6 is available for testing.
You can download it from here: arunchained0.16.apk
For Android HDMI sticks there's a special version available.
You can download it from here: arunchained0.15stick.apk
Current status of AppRadio Unchained Reloaded (has built in GPS Injector) (paid)
In addition to the AppRadio Unchained mod of the Pioneer AppRadio app, a completely Pioneer-less app was developed.
Basically it allows you to connect to your AppRadio in a faster and easier way without the need to use Tasker.
For details see here: AppRadio Unchained Reloaded
Current status of the ARUnchained GPS Injector (to be used with the AppRadio Unchained Mod) (paid)
GPS injection on system level using mock locations is available in the playstore here: ARUnchained GPS Injector
For GPS Injector details go to the FAQ here: ARU FAQ
Please fill out the survey here: ARUnchained GPS Injector survey
Navigation apps that already have AppRadio support like Waze and Navfree still work using the HU GPS. If you only use those apps then you don't need ARUnchained GPS Injector.
Head unit models that have built in navigation like AVIC-Z150BH, AVIC-F50BT and similar are not supported as Pioneer does not support sending of GPS data to the android device. If you are unsure, a test that can be done is to install Waze, if Waze can use the GPS of the head unit, ARUnchained GPS Injector works as well.
Release notes beta release 6
Rotation locker only active when HDMI connected.
ARU menu also available when not connected from Settings / Help menu.
Rotation locker and Start GPS Injector are now separate options.
Release notes beta release 5
Right part of the screen not reachable on Nexus 5 issue fixed.
Touch made more accurate for all phones.
Release notes beta release 4
Start / stop GPS Injector service when bt connected / disconnected.
SWC extended with ff & rw (to be tested by M.a.s.e-> doesn't work)
Play/Pause of HU quick menu bar now working.
Release notes pre-beta release 3
Steering wheel controls are working now.
For details go here: ARU FAQ
Release notes pre-beta release 2
Multitouch implemented.
Hardware keyboard issue fixed.
Options menu available.
Rotation locker.
Invert XY-coordinates. -> Does not work 100% yet.
Release notes pre-beta release 1
Radio buttons are working now.
Alternate method for setting uinput access rights fixed.
Release notes pre-beta release 0
Root access is required so your phone must be rooted.
For now it only allows using the touch screen.
Only single touch is supported.
Keys from the radio don't work yet.
GPS from the radio doesn't work yet.
Steering wheel controls don't work yet.
Users have reported it working on AppRadio 2, AppRadio 3, AVIC-F950, AVH-X8500BHS and AVH-X8550BT.
Disclaimer: Use at your own risk. Basically if it damages anything (you / your phone / your radio / your car or whatever),
don't blame me.
Donating
If you like my work and want to donate something, click on the "DONATE TO ME" button. However the first page will show in Dutch ( I guess because I am registered there).
Two solutions:
1) In another browser window logon to Paypal first. Then press the "DONATE TO ME" button here.
2) At "Donatiebedrag" enter the amount in US$ you want to donate, at "LOG IN OP PAYPAL" enter your logon details. After logon the language will change to your local language.
FAQ
For FAQ go here: ARU FAQ
Common issues and solutions
For an overview of common issues go here: Common issues and solutions compiled by stewbuntu
For help on what hardware to use you can also go here: Appradio forums It's basically the ARLiberator forum but has information about how to setup your hardware too.
Compatibility list
This app is compatible with any AppRadio that is supported by the original AppRadio app.
Details of supported Android devices:
Please fill out the survey here: ARUnchained survey
You can also report the issues that you have.
See attached ARUnchainedSurvey03.zip file for results of the survey. It's a zipped pdf file (had to zip it because of pdf size limitation on XDA). It gives a good overview of what phones/radios are working with ARU.
Old releases
Beta release 5 is still available in case 6 doesn't make you happy: arunchained0.15.apk
Beta release 4 is still available in case 5 doesn't make you happy: arunchained0.14.apk
Pre-beta release 3 is still available in case 4 doesn't make you happy: arunchained0.13.apk

Nice work! I can't wait to get home and test it out.
In the other thread I saw that someone had a S4 working with the AR3 using your app, so you have me really tempted to upgrade from the AR2 If you get GPS working on the AR3 you can definitely count on a donation from me.

FAQ
ARUnchained GPS Injector
The ARUnchained GPS Injector app has two parts inside. One is the GPS service and one is the UI activity.
The service is the part that injects the GPS data into mock locations. ARU 0.14 and up will start this service automatically when a bluetooth connection is made to the HU (at the same moment that the rotation locker is started). The GPS service is stopped when bluetooth is disconnected.
The UI activity is started when you start the ARUnchained GPS Injector app from the launcher. It shows the status of the GPS service and also the actual GPS data. The purpose is to be able to check whether the service is working properly. With the start / stop buttons the GPS service can manually be started / stopped.
For the GPS service to work Mock locations has to be enabled. To use the phone built in GPS, Mock locations has to be disabled. It can become tedious to set this manually so ARUnchained GPS Injector has an auto on/off Mock locations feature. In order for this to work ARUnchained GPS Injector has to be converted into a system app.
This involves moving "mars.area51.arunchainedgps.apk" from "/data/app" to "/system/app". This can be done with root explorer for instance. Set permission to rw-r--r-- and reboot your phone. On Android 4.4 (KitKat) you should move the apk to "/system/priv-app" folder instead.
For pre-KitKat Android versions converting to system app can be done using Titanium backup:
Open Titanium Backup
Search for ARUnchained GPS Injector
Long press and choose convert to system app
Reboot phone.
Converting to system app using free ES File Explorer
1. Make sure in ES File Explorer, Root Explorer is enabled and Mount R/W is on RW
2. Copy pkg.apk in /mnt/asec/mars.area51.arunchainedgps-1 to SDCard and rename it 'mars.area51.arunchainedgps-1.apk'
3. Install 'mars.area51.arunchainedgps-1.apk' from SDCard
4. Move 'mars.area51.arunchainedgps-1.apk' from 'data/app' to /system/app or /system/priv-app on 4.4.x
5. In /system/app or /system/priv-app select 'mars.area51.arunchainedgps-1.apk' and in menu select Install.
6. After install reboot
How to make a logcat using an app called Catlog
Start Catlog logcat through app menu and select record.
Select home button so you leave Catlog app running.
Go through process to start ARU and connect to AR.
Once you know the bug was created, open the Catlog app from notification bar (this stops recording).
Select the recording, which is named by date-timestamp...from action selection pick share by email...this zips the logcat and system info txt files into one zip.
Email to self and share the zip with dev by email or any other method you want.
On my Samsung phone not the whole screen is shown but a part is cut off
A) The default Samsung launcher doesn't handle landscape well. The solution is to install an alternative like Nova launcher.
On my Samsung phone touch stops working after calibration
A) Verify your phone is rooted properly.
B) On Android version 4.3 and higher Samsung has Knox security and SELinux is in enforcing mode.
This somehow prohibits accessing the /dev/uinput device which is required to be able to input touch/key events on system level.
In order for ARU to work Knox has to be disbled and SELinux has to be in permissive mode.
Possible fix 1:
First install an app called Android Terminal Emulator then open a terminal and type
the following lines pressing enter after each line:
su
pm disable com.sec.knox.seandroid
Now wait a bit till knox is killed and finally type:
setenforce 0
If this works, you have to do it every time you reboot your phone. It can be automated with Tasker for instance
Possible Fix 2:
Install the Xposed framework and the Wanam module.
At Security hacks tick " Disable Knox notifications" and "Disable SEandroid".
Reboot.
Possible Fix 3:
If the other fixes don't work and your bootloader isn't locked you can try to install a custom kernel that has Knox disabled and SELinux in permissive mode by default.
Keyboard use
It's not necessary to install Car Keyboard. Only the original Pioneer AppRadio app needs that.
Note that the virtual keyboard created by ARU is sometimes incorrectly detected as a hardware keyboard.
This prevents the software keyboard to be shown and makes it impossible to enter anything.
To check / set the keyboard settings:
Click the menu button on ARU.
At the right bottom click on "Change input method"
A pop-up is shown that CarKeyBoard has to be installed. Ignore it by clicking OK.
The dialog for selecting the input method is shown.
Make sure hardware keyboard is switched off.
Use of the hardware buttons:
The home, menu and back button now work as advertised.
To go back to the native interface you have to open the AppRadio app manually and then press the home button.
To go to the AppRadio app easily, swipe down the status bar and click the AppRadio notification.
Fast option to go back to the native interface: Double click the home button, touch the blue bar in the middle with 4 squares on the left.
Release notes pre-beta release 2
Multitouch implemented.
Multitouch works now. AppRadio 3 has a bug which makes it a bit unpredictable.
Hardware keyboard issue fixed.
Sometimes the virtual keyboard created by ARU was incorrectly detected as a
hardware keyboard preventing the software keyboard to be shown. Fixed now.
Options menu available.
The options menu can be reached from the app's main screen. There's now an additional ARU
option sub menu available with two options:
Rotation locker.
Invert XY coordinates.
When in AppRadio Mode homescreen, select menu button, select ARU, there you will see the ARU feature options...only accessible when connected to HU at this time.
Options can be set but will only become active after force stopping the app and then restarting it.
Go to Settings->Apps->AppRadio Unchained and do a Force stop. After that just start ARU again
and the options will take effect.
Rotation locker.
Forces rotation to be in landscape when enabled.
Locker becomes active when a bluetooth connection is established with the radio.
Locker is deactivated when bluetooth is disconnected.
Invert XY-coordinates.
Necessary for some tablets and HDMI sticks.
Currently this options doesn't work well. Somehow it will switch mode during calibration, giving
incorrect calibration results. After that touches are at the wrong position meaning app is useless.
Will look into it soon.
Release notes pre-beta release 3
Steering wheel controls
Steering wheel controls are working now.
Currently supported are: previous track and next track.
There might be more but I couldn't get it out of my radio.
Of course there's volume, mute etc. but that is handled directly by the radio
and never sent to the phone.
In case there are commands sent by the radio to the phone besides the ones already implemented the logcat will contain this:
Don't know how to translate RemoteCtrlInfo = <number>. Let me know the number and what remote control command you were
issuing and I can add it.

Hell yeah man! Thank you! will test soon on my AR3. If you have that bitcoin address set up I'll send you like $20 worth of btc for this mod.

great... waiting so long for getting AR3 support...
will test it today and donate as well...
Gesendet von meinem Nexus 7 mit Tapatalk 4

Original Hack Bounty Crew:
--------------------------------------------------------------------------------------------
$200 lpasq (xda) Confirmation number: 7D019513V95549722
$100 drawblood (appradioforum & xda) Donation made per post on AppradioForum
$50 ofarrell.g1 (xda)
$50 evillela2001 (xda) Confirmation number: 3NF91232VR227492L
$50 Meldoon (xda)
$25 rs2k (xda) Confirmation number: 8R358541KC016842T
$25 jj69chev (xda)
$25 leobg (xda) Confirmation number: 8TE693651C300254U
$25 tnuts22 (xda) Paid
--------------------------------------------------------------------------------------------
$550 Committed - U.S. Dollars
($425) Confirmed Donated
==============================================
$125 Due

hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597

Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.

Your phone has to be rooted for this app to work

tmp_do said:
hey Area51. i have a bugreport for u. appradio app from market work ok on lg p999 with stock 2.3.4 fw, but modified app crash twice at startup. then it work seems fine(cant test it with pioneer now). on same phone with cm7(2.3.7) and cm10 all ok. i have a log dump for u: http://pastebin.ca/2455597
Click to expand...
Click to collapse
I think it may be due to code obfuscation stripping a bit too much code. Thanks for the report.

Droid Bionic
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.

gbual said:
Your phone has to be rooted for this app to work
Click to expand...
Click to collapse
It is rooted.

jdbaldi said:
I donated 50usd...even without the AR2 hardware buttons working, this app is awsome. I use an old rootrd stock Droid Bionic, and your app works perfect for me. No lag, no parts of the screen I can't get to, just works perfect. Thanks for all the hard work, buy some drinks on me.
Click to expand...
Click to collapse
Don't pay me too early, the app is not even finished. I might take the money and run......
J/k, I will finish everything.
And I have to add, thanks a lot for the donation!

Area51© said:
Compatability list
To be done.
Click to expand...
Click to collapse
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.

enjoimadcow said:
Alright just got done testing with my note 1 I717 running stock 4.1.2. Couldn't get it to work at all. Bluetooth is connected as I can stream google play and make phone calls through the unit. However, when I connect the MHL adapter to the deck, I get an icon that I can only describe as a map with a speech bubble with a bluetooth symbol in it with an x by it. I'm assuming it means no bluetooth connection. However streaming music via bluetooth is currently going on. Now on the phone side, normally in the non modified version of ar before the mhl adapter is plugged in and bluetooth is connected, it gives a picture of a usb cable on the phone with an arrow saying plug in. On the arunchained, it just gives the Bluetooth symbol with 6 dots like it's not connected. I'm terrible at bug reports so if you have any questions I'll try to answer it.
Click to expand...
Click to collapse
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.

Area51© said:
Hmmm, basically that part (Bluetooth communication etc.) is not changed from the original app. So I don't really understand why there is a difference. It seems you are using an AR3 but I have an AR2, so I guess icons on the headunit are different.
On my phone side I get a Bluetooth symbol with 6 dots as well, and it's working.
Click to expand...
Click to collapse
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.

enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Phone side is same as I get. AppRadio side I can't compare I have an AR2.
On the phone side I only get that Bluetooth icon with the 6 dots. I think the other is because you have Bluetooth streaming.

lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
Thanks.
This link got me into the design mode somehow. Do you have to give everybody access before they can enter data?
Maybe a field to state working or not working and if not, why not would be nice.
Will look at it later, my gf wants me to watch the last episode of Dexter now.

lpasq said:
Try this https://docs.google.com/forms/d/1sz8ItL_d4NlLWP33-JK1aaxv8-LWZGuKPjr1RuMNlBI/edit?usp=sharing
Area51...paste link to OP if it works for you.
Click to expand...
Click to collapse
I tried it again but now I got a message that the file is in the owners bin. When I clicked the link, I entered into design mode or something. I had to click "View live form" to enter data. But it seems someone else entered data in design mode and replaced all the titles with the answers he wanted to give. Do you have a copy? Maybe need another link to go to the View live form mode right away.

enjoimadcow said:
hmmmm. I uninstalled the app, restarted the phone, reinstalled, gave root access, and still nothing =(. I made an album of screenshots and pics http://imgur.com/R7sU3gf,vBVOGAN,VAiII0J,U5NEyBC#3 . When I go to the center icon it gives me a message like app radio does not seem to be installed, when I hit ignore, I see the home screen of android, but I get that hand with the x when I try to do anything.
Click to expand...
Click to collapse
Have you paired the radio to the phone under Bluetooth settings? Also - check if phone is "selected' on the connection tab on the radio itself (I recommend auto connection to be set to ON)

[Q] Keyboard Dock doesn't work when device is encrypted?

Hi all,
Got a P3100 that needs to be encrypted for various reasons. There is no way around it, unfortunately. It is running stock ICS 4.0.3, unrooted (also non-negotiable)
I have one of these docks:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When entering the Encryption password on boot it functions perfectly. As soon as it reboots into android, it ceases functioning.
It functions 100% correctly on an unencrypted device, but as soon as it is encrypted it ceases to work at all. Why is this? Is there any way around it?
It still charges through the dock if I plug the dock in, regardless of encryption. The dock has a blue LED for indicating when caps lock is enabled/disabled. I noticed that if I leave caps lock on, then insert the tablet into the dock the LED will flash on briefly, then the tablet will indicate that it is charging (when the dock is plugged in), fthen the LED will go out and no longer responds to the caps lock key.
I find this all very odd as using a keyboard and/or mouse via USB OTG cable works fine, but the official accessory does not?
Any help?
Thanks

Bump!

bump

Bump

One last ditch attempt - bump!

Well, since no one replied so far it would seem you're either having a problem no one ever experienced or knows a solution about.
Seeing the Verizon logo on your device, and reading "stock ICS 4.0.3"... I take calling Verizon and asking them about the odds of one of their "ROM betterfications" maybe screwing up is a futile attempt?
Anyway, while your problem description is a bit thin you at least worked out that it seems to work with a USB OTG connected keyboard/mouse. Now... when you plug the tablet into the keyboard dock... is the keyboard totally "dead" or do some of the keys still work? If the tablet still reacts to the "navigation" keys it would indicate a software problem. At least on the Tab 8.9 the keyboard dock doesn't work when the Samsung keyboard isn't selected as the default input method, but it still reacts to the one or another odd key. If it doesn't react at all, you already gave the 30-pin connector in the dock a visual inspection (you may need a magnification glass) to rule out it could be damaged?
If the dock happens to work flawlessly when the device is not encrypted (no physical damage of the connector) but starts acting up once the device is encrypted you already found the problem... some kind of software problem when the device is encrypted. It would actually be interesting if logcat would show some error upon plugging the tablet into the dock (if it does, that may give a clue about what went wrong).
What are the chances of upgrading the firmware? Google just showed me a Verizon page claiming that there's a Jelly Bean 4.1.2 OTA upgrade. How about updating and checking if it solved the problem at hand?
As a value added tip for the future: it's better to resort to Bluetooth keyboards / mice instead (plus a tablet stand so the tablet can stand in front of you in portrait or landscape orientation). Gives you the adavantage that you can use it with another device (i.e. the Logitech K800 can pair with up to 3 devices and be easily switched between them) once you move on to some better tablet/phone, and you're not bound to sit right there but have freedom to move the keyboard around.

BoneWithABeagle said:
Well, since no one replied so far it would seem you're either having a problem no one ever experienced or knows a solution about.
Seeing the Verizon logo on your device, and reading "stock ICS 4.0.3"... I take calling Verizon and asking them about the odds of one of their "ROM betterfications" maybe screwing up is a futile attempt?
Anyway, while your problem description is a bit thin you at least worked out that it seems to work with a USB OTG connected keyboard/mouse. Now... when you plug the tablet into the keyboard dock... is the keyboard totally "dead" or do some of the keys still work? If the tablet still reacts to the "navigation" keys it would indicate a software problem. At least on the Tab 8.9 the keyboard dock doesn't work when the Samsung keyboard isn't selected as the default input method, but it still reacts to the one or another odd key. If it doesn't react at all, you already gave the 30-pin connector in the dock a visual inspection (you may need a magnification glass) to rule out it could be damaged?
If the dock happens to work flawlessly when the device is not encrypted (no physical damage of the connector) but starts acting up once the device is encrypted you already found the problem... some kind of software problem when the device is encrypted. It would actually be interesting if logcat would show some error upon plugging the tablet into the dock (if it does, that may give a clue about what went wrong).
What are the chances of upgrading the firmware? Google just showed me a Verizon page claiming that there's a Jelly Bean 4.1.2 OTA upgrade. How about updating and checking if it solved the problem at hand?
As a value added tip for the future: it's better to resort to Bluetooth keyboards / mice instead (plus a tablet stand so the tablet can stand in front of you in portrait or landscape orientation). Gives you the adavantage that you can use it with another device (i.e. the Logitech K800 can pair with up to 3 devices and be easily switched between them) once you move on to some better tablet/phone, and you're not bound to sit right there but have freedom to move the keyboard around.
Click to expand...
Click to collapse
It's not a Verizon model, it's unbranded (I'm in the UK) - that image is just a stock photo. The dock is not damaged and functions 100% when a device is unencrypted. I'm 100% sure the issue lies in the encryption.
It works on the encryption 'enter password' screen but no further
Chances of upgrading the firmware are 0%. Same with using Bluetooth keyboards and mice as they are used in a clinical business environment and the various risks involved with disconnection/potential for data breach via bluetooth are sadly too great.
You spoke of 'logcat' - how would I access this?
Thanks for the reply! Even though I think it's a lost cause it's hugely appreciated.

SmokinWaffle said:
It's not a Verizon model, it's unbranded (I'm in the UK) - that image is just a stock photo. The dock is not damaged and functions 100% when a device is unencrypted. I'm 100% sure the issue lies in the encryption.
It works on the encryption 'enter password' screen but no further
Click to expand...
Click to collapse
Well, in this rather sad case it's almost safe to assume that there's a software issue between the software stack for the dock and the device encryption (though that's freakin' weird that Samsung's QC didn't test out this particular scenario).
SmokinWaffle said:
Chances of upgrading the firmware are 0%. Same with using Bluetooth keyboards and mice as they are used in a clinical business environment and the various risks involved with disconnection/potential for data breach via bluetooth are sadly too great.
Click to expand...
Click to collapse
Yeah. I understand that all sorts of wireless connectivity is a absolute no go around medical equipment, especially in ICU's.
However, that security model a bit through the roof. While I understand that patient records are confidential and the internal network of a hospital is a critical infrastructure because equipment could be interconnected, it's not that easy to hack into the system through a active BlueTooth connection (especially not when the default on Android is "Not visible") ... your WiFi network (by the end of the day your tablet needs to somehow connect to the LAN, and since the Tab 2 doesn't come with a ethernet jack that only leaves us with WiFi) is the more vulnerable attack vector for someone really wanting to get in (for whatever ill intent). However, we don't want to start a "network security" debate here.
SmokinWaffle said:
You spoke of 'logcat' - how would I access this?
Click to expand...
Click to collapse
There are two ways to get to the system log. One way, enabling you to catch the boot-up process, is to turn on adb debugging in the developer options on the tablet, have the tablet connected via the charging cable to a PC, have the drivers and "adb" installed and "adb logcat > logcat.txt" running so it starts fetching the log at the earliest moment possible (as soon as adbd was started on the tablet).
The other way is to install, for example, "CatLog" from the Play Store. This program displays the logcat output inside a nice application right there on the tablet and also enables you to write the log-roll to a text file for further analysis. This doesn't get the early log output, but running it right after a boot-up and letting it record while you try to mess about with the dock's keyboard will get as much data as somehow possible in case it would show a error related to it (logcat has a bit of a buffer, when invoked fast enough it might be able to get to the bits of the early log).
One "security concern" involved here (in regards to the slightly paranoid setup of your work place(?)) is that this log contains a lot of data you may not want to show to the public - like the Google e-mail address associated with the device, several IDs like the one of the WiFi AP and the tablet and so on... you can even see which apps have been launched during boot. That gives away so much info to make a system/network admnistrator already wearing a tin-foil hat to totally go bananas.
SmokinWaffle said:
Thanks for the reply! Even though I think it's a lost cause it's hugely appreciated.
Click to expand...
Click to collapse
Well, apart from the latent chance that a fix might be impossible, the main problem I see is that it's obviously a employer issued device (given you're from the nursing staff and not a patient of the facility) therefore hard to give out logs to strangers on the Internet for "look-see" when you're already trapped in a tin-foil hat wearers environment. To try and track down the problem one needs to see what's going on with the device, and that would mean laying eyes on data that's surely deemed "our admin eyes only" in your case. That, at least, would be my definition of the "main reason for the lost cause".
Anyway, if you can install CatLog and review the log and spot a meaningful error feel free to post the bits relating to just the error instead of a full system-log.

SGS5, StockRom and RS232 (Aten UC232)

First I hope this is the correct place cos the other RS232-posts I've searched for seems to be spread out.
I've been looking to solve a problem I got with my SGS5 and using Aten UC232A
to connect it to RS232 devices. The problem is that I either won't get a connection at all or it disconnects after like 1 seconds to 1 minute and after that i'ts tough as "frell" to try to get it to work again without waiting for eg. 30 minutes.
I've seen people using their Androids with Arduino so it got to be something that I missed. I can also say that I tested this with a friends SGS5 with another ROM and it has the exact same problem. My SGS5 has StockROM and Lollipop (5.0) kernel.
As I've understood it all I need to do is to install a terminal program, in my case I tried these: 'USB Serial Terminal Lite' and 'Slick USB 2 Serial Terminal'.
It won't matter if the device itself is connected to the UC232A since it's the UC232A that gets disconnected all the time.
The device I'm trying to get into is a radar and since it only gives me a few seconds to type in the control characters before going into run mode again (after I switched it to settings) I need the terminal to have lots of macros that I can save 'cos there's no time to fiddle with the keyboard.
Also, since this is supposed to be used at work later, it would great if it didn't need 'root access' since most there won't do that, but if it's the the only thing to fix it, it'll have to do.
So know my question is, is this just a dream to get this to work or am I missing something.
Is there any change at all that I will get my RS232 app that I was thinking of creating to work when not even this seems to work?
//B52

[Guide] How to use Tasker to fix all calls being sent to Gear S3

The Problem: On many non-Samsung phones, all calls, even when answered on the phone itself, get sent to the watch's speakerphone, requiring the user to manually switch the sound back to the handset every time a phone call happens. As a side problem, the watch conflicts with other Bluetooth devices capable of of being used for calls, like car stereos and headsets. Several threads on xda and elsewhere discuss these issues; however, the only solution posted is to disable the "Phone Audio" profile of the watch in settings. This is sub-optimal because it completely disables the ability to use the watch as a phone speaker.
The Solution: I have put together a series of Tasker profiles and tasks that utilize the BlueTask plugin to control the connection of the Gear S3. A convenient detail about BlueTask's disconnection method is that it only seems to affect the "Phone Audio" component of the Gear S3, leaving all other functionality untouched during a call. I use the proximity sensor to determine whether or not the call is being made/answered on the phone itself vs the watch. The assumption is that if you leave you phone in your pocket, bag, or face down on the desk, then you answered the call via the watch. I understand this is not a perfect method for determining which device is answering the call, but it works pretty well in my testing. In addition, an exception is made for when a wired headset is hooked up to the phone, as one may leave their phone in their pocket while answering using such a headset. Finally, an additional profile I call the "Car profile" will automatically disconnect the watch and disable its Tasker profiles while connected to specified Bluetooth devices like a car stereo, Bluetooth headsets, etc.
Setup:
Re-enable "Phone Audio" for Gear S3 if you previously disabled it (Settings>Bluetooth>Gear S3)
Install Tasker (if you haven't already)
Install BlueTask
Go to Tasker>Preferences>UI>Beginner Mode. Disable it (if it is not disabled already).
Go to Tasker>Preferences>Monitor>Display Off Monitoring>Proximity Sensor. Set it to "Yes"
Download the Tasker project attached to this post to your phone
Import the project into Tasker (Press and hold the home tab in the bottom left corner of tasker and then click Import)
Enter the new "Bluetooth" project and open "Car Profile" in "Profiles"
Delete the Dummy MAC address in the Profile and replace it with the MAC addresses of any car stereos and/or bluetooth headsets you use with your phone. If you have multiple of such devices, separate each address with a "/" (the magnifier glass icon does this for you). If you have no such devices, feel free to disable or delete this profile.
Open "Disconnect Gear S3" in "Tasks"
Open the "BT Connection" action
Replace the dummy information with your Gear S3's Name and MAC address
Repeat steps 10, 11, and 12 for the "Connect Gear S3", "Car Mode", and "Exit Car Mode" tasks.
Complete!
Let me know if this works for you. Also, suggestions for how this project could be improved are welcome.

Its works fine on #LGV20 so no need for this fix.
Sent from my LG-H990 using Tapatalk

I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you

OneRealDaniel said:
I've downloaded the project to my phone but when I launch tasker and try to import the profile I can't find the file, even though I can see it using a file explorer. I've changed the.Prj to .prf and Tasker sees it but when I try to import it it gives me an error that says the for contains multiple projects.
Any help would be appreciated, thank you
Click to expand...
Click to collapse
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.

Beginner mode
MehStrongBadMeh said:
Is it downloading as a .prj or .prj.xml ? It should be the latter. If it isn't, rename it to have a .prj.xml extension. Otherwise, not really sure what is going on. I haven't had any trouble importing Tasker projects in the past.
Click to expand...
Click to collapse
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.

OneRealDaniel said:
Thanks for getting back to me. Im new with Tasker, the only reason I bought it was because of this issue and because I saw your post. All I needed to do was disable beginner mode in preferences, under Ui, and the house icon appeared, from there it was very simple to follow the instructions. Thank you for sharing your solution to this very inconvenient problem.
Once I get to test it ill make sure to give you feedback.
Click to expand...
Click to collapse
Thanks for letting me know about that, I'll add that to the steps.

Hi i downloaded the App but seems it doesnt work for me. I set it up according your instructions but still no change. But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic? That once someone picks up a call that it select this option right after.
Added 2 screenshots one from the Standard run and one of the option to select an audio divice when making a call.
Thx for any help.
Edit: Works Now thx alot i had an incorrect name set for the device... i will test it if it works always but so far so good. thx alot

Jafabibe said:
But i háve an idea i spoted that when i make call from phone i háve an option to choose which audio divice to use if i select my phone it doest work but when someone picks up and then i select it it Works. So i am thinking is there a way to make this automatic?
Click to expand...
Click to collapse
I wanted to use this system as part of the automation workflow. The problem is that, when dialing someone, it switches the audio output when they pickup, instead of during Phone Offhook (the moment you hit dial). As a result, I can't detect the actual moment the audio device is switched, so I disable the watch audio entirely to prevent it from from happening.

Hello guys. I have non rooted stock nexus 5x. I have followed steps from first post but I always get error (attached).
Please any ideas what's going on?
Edit: Sorry guys. Please ignore it. I have added wifi mac for gear instead of bluetooth mac. I'm going to test it.

I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.

GabrielAK89 said:
I am trying to use this for my phone.
I opened the prj.xml in notepad, edited my MAC address and name of bluetooth for car and gear s3.
When i press the play button in the bottom left corner i get the error non-existing plug-in code type Action: 704475526.
Any idea what i can do?
Thanks.
Click to expand...
Click to collapse
Probably install Bluetask as per the instructions.

I solved the problem using Macrodroid.

GabrielAK89 said:
I solved the problem using Macrodroid.
Click to expand...
Click to collapse
Can you tell us, the other users, what you did to get it solved ?
As we are in a forum, others can benefit using your solution.
So please share.

I just got my Nokia 8 Sirocco, and I thought it was bad BT performance on my new device, when it probably is my Gear screwing me over. Thank you for this Tasker-project, I've just finished setting it up, and l am looking forward to seeing is effect!

Unfortunately, the macrodroid way don't work anymore for me.
Don't know why.
I am retrying the Tasker way. I get the error:
12.53.42/E FIRE PLUGIN: Connection / com.twofortyfouram.locale.intent.action.FIRE_SETTING: 8 bundle keys
12.53.42/E Connection: plugin comp: com.balda.bluetask/com.balda.bluetask.receivers.FireReceiver
12.53.42/E add wait type Plugin1 time 60
12.53.42/E add wait type Plugin1 done
12.53.42/E add wait task
12.53.42/E Error: 2
Does anyone know what it means?
LE: When i am in the car i don't get this error. Everything seems to be with green dot. But the magic never happen. The tusker is not triggered. Should i make other settings to work?
I also tryed Bluetooth auto connect. Bad luck with that also.

Hi!
I've been meddling with Tasker for the past few days and discovered that choosing the Headset profile to connect to and disconnect from the Gear S3 works better for me.
I've started out with MehStrongBadMeh's guide and tasker xml file (many thanks by the way!), but found out my phone was unable to connect the Gear S3. It disconnected OK to connect the car bluetooth, but would not reconnect Gear S3. Running the task also gave errors as reported by few others on this thread.
But everything seems to be in order when Headset profile is selected for Gear S3. Will test out extensively and will report back if I need to change anything else.

I believe I created that xml was created before bluetask handled specific profiles, hence the need to explicitly set headset now. I don't actually use this profile anymore, as calls started being routed properly when I updated my HTC 10 to Oreo (and continue to be routed properly on my OnePlus 6).

Just wanted to say a massive thank you for this. I have just bought the Galaxy Watch and have a Samsung S6 Edge with lineageos. I was having the issue where everything was being rooted through the watch. Your guide has got this working as it was designed.
My notes would be for anyone trying this - do not change the device name as it doesn't seem to work (i am guessing this is referenced in other profiles) - just change the mac address to your watches Bluetooth mac address.

Any update on this I still get an Error 2 and it never seems to connect on its own to my car audio

Solved with MacroDroid:
Trigger: Call active (any contact)
Action: Kill application Galaxy Wearable
Constraints: Trigger fired Call active
AND In call
App Alive BG Galaxy Wearable