Related
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
=======================
NOV 24 UPDATE
Numerous improvements/corrections/bugfixes (I'm not removing the previous version as this one haven't been much tested).
Enjoy!
Thanks dude. Great job
avs333 said:
I wrote this program because I was unable to find a good app capable of recording the other side of the call properly.
Except for AirVoice, all such apps record the speaker rather than the line, and you barely hear the other side in the recordings.
The guy who wrote AirVoice knew the trick but seemed to be very annoyed by the negative feedback from Android Market, where the users of various devices (with the list of supported ones clearly stated!) tried to install that program. Because it wasn't open source, I had to disassemble it in order to write what I wanted exactly.
So the app uses an esoteric HTC driver, and NEEDS THE ROOT ACCESS just to open the device. If you do "adb shell chmod 666 '/dev/voc*' ", it'll never ask you for root access (but you have to be ROOT to execute that command).
It writes the calls in either WAV (recommended) or MP3 format (not tested much; needs some time to encode the file after the call, but the size is about 4 times smaller), stereo (left ear is your voice, right is that of the other party), to "/sdcard/voix" directory.
The kernel driver itself is kinda buggy. Actually, the auto-answer mode is non-functional for kendon's & ninpo's kernels (others not tested). Do NOT select it in Settings unless you've got such ROM and particularly need to reboot your phone on each incoming call . It'd be nice if somebody try to fix that.
If you select "Ask each time" for any incoming calls, be sure to wait half a mo until the confirmation dialog appears. The "Foreground service" (default) setting is also recommended because Android may otherwise kill it if memory is low.
Any comments are welcome. I'm not sure that I'll ever add something to this program because I'm too lazy for that, but any bugs will reasonably be fixed. The code is open source, PM me if you're a programmer and have any ideas how to improve it.
Click to expand...
Click to collapse
thanks, good job
but recorded sound a lit low, any chance to make it loud
Aha Thats Great Now i can prove my prank calls
no auto start, please add (i mean after re-boot)
Hi-Fi said:
but recorded sound a lit low, any chance to make it loud
Click to expand...
Click to collapse
No problems with sound volume here, but I'll see if I can add some basic volume normalisation...
Hi-Fi said:
no auto start, please add (i mean after re-boot)
Click to expand...
Click to collapse
Added as an option in Settings. Also fixed a triffle UI bug (forgetting to set proper dialog attributes).
Just tried this, works great on my Hero (Vanilla Eclair 4.0). Thank you very much for this one!
Interesting software. Could you possibly add a new feature: The app saves all calls, but deletes them, if you don't move them to another folder/to your PC.
This because I could record all of my calls, without the risk of making a huge 1Gt folder to fill up my memory. So if the user could choose how many recent calls (2,5,10) the app saves before deleting them I'd be great!
What about battery draining?
This great app is also tiny enough not to reduce drastically battery duration?
TIA
I'd love to see this generalized to not require the HTC driver. Do you think that would be possible?
cool app. anyone know if it would be possible to play an audio file directly to the caller? would come in handy rickrolling damn telemarketers
Very good work. Handy app, for sure.
Can you enable recording mid call?
Works in all Androis Devices? I have a Milestone.
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Having same issue on rooted G2.
Sent from my T-Mobile G2 using XDA App
MercuryTangent said:
Awesome idea, I've been looking for exactly this sort of software.
I'm having a bug I hope someone can help me with. When I start the program I get a prompt that says "Device does not exist, or its permissions cannot be changed." When I click "OK" it takes me to the screen to uninstall the program.
I'm running an Evo, fully rooted, NAND unlocked, running Virus Airbourne ROM and King #11 kernel.
I never get the prompt from the SuperUser app to give the app root access.
I tried the adb command but it gave me the error:
Unable to chmod dev/voc*: No such file or directory
Click to expand...
Click to collapse
I experience the same problems on my rooted DINC. ROM and kernel are in sig.
Am I right to assume that this is a HTC Hero exclusive?
bemymonkey said:
Am I right to assume that this is a HTC Hero exclusive?
Click to expand...
Click to collapse
Likely so, but I'm hoping the dev will extend it or I can find a way to make it work
This is amazing app. The only thing I would beg the author to consider a white status bar icon for normal running service as colored icons there usually break the aestetics of Android UI. The icon can change or become colored while recording, but when only running in the background it should remain white.
I have the same problem (link to uninstall) on my Nexus One. Everything works fine on Hero
Name: Media Volume Settings
Marketplace description:
Have you ever noticed that after opening some application or game, the volume for media playback (from zune for example) is higher or lower ? Or that some games have the volume too high ?
This application allows to fine tune that internal background media volume, separately from the main device volume. It can also be useful when an application or game has background music too loud or too soft.
Please note it DOESN'T work while connected to Zune, which restores volume to 100%. Also note it can't control in-call, device or notifications volume nor can keep the settings after a reboot due to WP7 features/limitations, about which I can't do anything.
Trial is ad-supported
Updated in 1.4:
- customizable presets
- better compatibility through the Dispatcher (should help ?)
- better interface, up/down buttons
__
Please remember that you can't update a trial application in the marketplace at the moment. You have to uninstall and reinstall it.
Notes:
I've noticed many application that can alter background/zune music volume (Bowling xx is one) and also some others that had their internal volume too high, so that even at volume 1/30 it was annoying at night (Krashlander is one). Some of them are now allowing internal volume regulation in later updates. This application solves both problems. I'm also looking into adding live tile (with volume value), not sure about the possibility of it...
Available in English,Italian and German .
before reporting it doesn't work, please note:
- it doesn't allow to make general volume higher
- media volume is used by most application and zune to control background music and sometimes sounds too (so you can fine tune with this)
- there are applications that modify this volume at start. There are many of these that don't set it back when they exits (and that's one of the main uses of the application)
- at boot, you always have 100% media volume
- when connecting to zune or synching wirelessly, it resets media volume to 100%
- while connected to zune, you can't alter volume
- it can't control in-call, notifications, alerts, ringtones, or door bell volume. I'm looking into controlling your dog bark, though
Source: http://forum.xda-developers.com/showthread.php?p=10881451
Zune Marketplace Link: http://social.zune.net/External/Lau...oneAppID=0774b6ec-f323-e011-854c-00237de2db9e
Please, anybody voting in the poll above, leave a comment with your phone model (and if it works). Thanks
Thank you !
That was my problem exactly, I had to restart my phone each time some application modified the volume especially when I wanted to use Zune and the music came out quite low. In fact I thought something was wrong with the speaker...
I’ve actually even used it with a game which had very loud background music.
Thanks, I'm going to release a free, ad-supported version in some days.
Trial updated to ad-support
The application has been updated with ad-supported, unrestricted use, trial version. Buying removes the ads. Please remember that you can't update a trial version in the marketplace at the time, you have to uninstall and reinstall it.
I've also found out that comparing two omnia7, both coming from germany, that one is quite louder than the other, even on max volume (both media and main device volumes at 100%). I've also checked the device gain in through diagnosis codes and they are the same. However I'd say the quiter one is already loud enough.
Or maybe that's to point on the fact that the louder one has been debranded by flashing a new rom ? (warranty repair, came broken from an extremely rude german internet shop which refused to replace it ! If you are going to buy one in Germany I can pm his name, so you can avoid what I've been through)
You should add all the different volumes settings to it... like system volume, notification volume, etc. Then it could be a one stop place to change volume for all aspects of the device.
thesecondsfade said:
You should add all the different volumes settings to it... like system volume, notification volume, etc. Then it could be a one stop place to change volume for all aspects of the device.
Click to expand...
Click to collapse
To the best of my knowledge, the wp7 toolkit doesn't allow you to manipulate device (system) volume. There is also no separate notification volume in windows phones, it uses the same as ringer/device volume.
link to zune market place
first of all nice application!
can you please tell me how to get the link to the application in marketplace once the application is uploaded. The only way i thought to view the application is search in zune software.
Thanks.
Thanks.
I got that problem too. First thing I did was trying to get something out of the assembly, but right in the middle of it I discovered the appropriate command.
I'm on the wrong computer now and can't remember what it is, but I think it's something that sound like OpenMarketPlacePage. If I remember correctly, you don't need to get the id, call the link, etc.
Version 1.3 with german localization
I've just pushed the update to 1.3 to the testing process. Besides adding localization for our german friends (who apparently couldn't understand what the application does), there are some interface tweaks.
Most importantly, I've found out that connecting the phone to Zune has the effect of resetting the media volume to 100% and keeping it there while connected.
Regarding managing other volumes, at the moment I can't see a way. I guess there are three volumes at least: device (main), in-call, and media volume.
thanks....
There are some reviews on the market which just say that it won't work. If anyone noticed that it fails to regulate the volume, please indicate which model of phone is tested on and maybe the carrier/nation as well as it's also weird it didn't work for 2 out of 2 australian users...
as of now:
Success on:
2 omnia7
1 dell venue
2 focus
2 hd7
5 unknown
Failed on:
1 surround
2 focus
1 hd7
2 unknown
Do you think you could control ring volume separately ?
Works on my Focus, although resets on reboot.
I like it, but I wish we could simply set the media volume level straight up (0-30) instead of fractions of the system volume. I'm assuming that's much harder to implement, though.
menger said:
Do you think you could control ring volume separately ?
Click to expand...
Click to collapse
Unfortunately not at the moment. From the looks of it, the sdk only exposes a few stuff to manage that background music volume, probably in order to manage it in-game easily.
Even if with some complex way one could control other volumes, it wouldn't pass certification because it would probably not use standard calls...
mcorrie1121 said:
Works on my Focus, although resets on reboot.
I like it, but I wish we could simply set the media volume level straight up (0-30) instead of fractions of the system volume. I'm assuming that's much harder to implement, though.
Click to expand...
Click to collapse
Glad you like it. Well, again, it would probably be nice to manage it that way, but at the moment the way media volume is designed completely forbid this. In fact at the beginning I was looking to implement something like this, but my guess is that this is how the volume settings work. After adapting a bit to it, it actually makes sense too.
At the beginning I was longing for an android-like, 6 channel volume mixer, but now I think they were too many and this is an easier way to manage volume.
The fact that it resets at reboot is another technical limitation/feature. The media volume is a 'soft' settings and I can't control what starts when the phone reboots. It's also a feature because if the volume got incorrectly set by some application (muted for example!) then you possibly wouldn't have a way to reset it.
What makes less sense is that it resets to 100% when connected to zune, which also stops the music. I'm sure there might be some explication behind it, it's just a tiny bit annoying...
maqwp7developer said:
first of all nice application!
can you please tell me how to get the link to the application in marketplace once the application is uploaded. The only way i thought to view the application is search in zune software.
Thanks.
Click to expand...
Click to collapse
Forgot to clarify:
in order to open your app marketplace page, you can do this in the code:
MarketPlaceDetailTask task = new MarketPlaceDetailTask();
task.Show();
while otherwise to know the product id or even the link for the application, once published, you can see it in the app hub details page.
It doesn't work on my HTC HD7. ever try to play a game with sound on this device no volume at all the sound is so ,so low.
jabtano said:
It doesn't work on my HTC HD7. ever try to play a game with sound on this device no volume at all the sound is so ,so low.
Click to expand...
Click to collapse
I'm sorry I'm probably misunderstanding you. Do you mean that you are trying to increase the general volume in a game using this application ?
Yes the overall volume on this device is bad in order to listen to tunes you have to use a headset otherwise there is no volume.
Sent from my HD7 using Board Express
However this app works great on my wifes focus. HTC HD7 has s volume issue HTC says to download there app that is much like this one it didn't work so I was hoping this one would.
Sent from my HD7 using Board Express
Not sure if this is the right forum. I found that double tapping the button on a headset causes HTC One to redial the most recent number in my call logs. I did find a thread with the same topic but it only mentions a workaround and not a solution. So I created a small app with a broadcast receiver to listen for headset events and perform the appropriate action (and hopefully disallow the device to take over). But no matter what i try, the device always ends up redialling. I tried digging into the source code to see how the device intercepts these events and found that the phone app registers a broadcastreciever for MEDIA_BUTTON intent with priority 1001. So i registered mine with a higher priority (tried 1002, then Integer.MAX_VALUE), but still the device takes over. Moving my apk to /system/app and setting the proper permissions didnt help either. Registering my receiver with AudioManager.registerMediaButtonEventReceiver or AudioManager.registerMediaButtonEventReceiverForCalls (using reflection) doesn't help either because i can see from the logs that phone app intercepts the event even before audio service does. I can see clearly that the MediaButtonReceiver in Phone.apk is the one performing the redial. So if anyone has had success with intercepting headset events before the phone app, please guide me so that i can go about tweaking my ONE so that i can use headset controls like in iPhone.
P.S. The closest possible solution that i came across is to write a service which makes sure that there is always a dummy entry at the top of call logs (MediaButtonReceiver in the phone app does not redial if the most recent number is blank, -1 or -2), then install an app like Jays or headset button controller to get the desired functionality. But this is an ugly workaround because the call logs will always have a dummy entry at the top and not all headset events are propogated to these apps, meaning they dont work most of the time.
Note. This redial functionality seems to be specific to HTC.
Solved
Juja01 said:
Not sure if this is the right forum. I found that double tapping the button on a headset causes HTC One to redial the most recent number in my call logs. I did find a thread with the same topic but it only mentions a workaround and not a solution. So I created a small app with a broadcast receiver to listen for headset events and perform the appropriate action (and hopefully disallow the device to take over). But no matter what i try, the device always ends up redialling. I tried digging into the source code to see how the device intercepts these events and found that the phone app registers a broadcastreciever for MEDIA_BUTTON intent with priority 1001. So i registered mine with a higher priority (tried 1002, then Integer.MAX_VALUE), but still the device takes over. Moving my apk to /system/app and setting the proper permissions didnt help either. Registering my receiver with AudioManager.registerMediaButtonEventReceiver or AudioManager.registerMediaButtonEventReceiverForCalls (using reflection) doesn't help either because i can see from the logs that phone app intercepts the event even before audio service does. I can see clearly that the MediaButtonReceiver in Phone.apk is the one performing the redial. So if anyone has had success with intercepting headset events before the phone app, please guide me so that i can go about tweaking my ONE so that i can use headset controls like in iPhone.
P.S. The closest possible solution that i came across is to write a service which makes sure that there is always a dummy entry at the top of call logs (MediaButtonReceiver in the phone app does not redial if the most recent number is blank, -1 or -2), then install an app like Jays or headset button controller to get the desired functionality. But this is an ugly workaround because the call logs will always have a dummy entry at the top and not all headset events are propogated to these apps, meaning they dont work most of the time.
Note. This redial functionality seems to be specific to HTC.
Click to expand...
Click to collapse
Finally got this working. It can be done by modifying the keylayout file and mapping scancode 226 to MEDIA_STOP instead of HEADSETHOOK and then writing a service which can intercept and handle this. As for making sure the service has highest priority in intercepting media button events we need to register a content observer for "media_button_receiver" setting (The device changes this setting whenever an application registers itself as a registerMediaButtonEventReceiver), and on every change register ourselves again as the mediaButtonEventReceiver so that we always stay on top of the stack.
This Threader is a Spin-off of the original: [Android 4.1+] Headunit for Android Auto - 160117 - Self Mode+ other fixes, x86, 720p by the late :crying: @mikereidis.
App links: https://www.b3itlabs.com/prod.php?id=1
PlayStore: https://play.google.com/store/apps/details?id=gb.xxy.hr
Previous XDA Lab purchases can be downloaded using: https://www.b3itlabs.com/download.php
Last edited: 20/04/2023
Version 7.X Released
- It has braking changes for WiFi, this is mainly due to recent Android SDK limits, like toggling WiFi, BT, getting Mac address and others. Therefore WiFi connection now does need a helper app on the phone.
- Dropped GLES20 as too many issues reported by different bad implementations
- Resolution is now automatically detected based on the cars screen.
- SelfMode (running on phone screen) works without the need of activating developer options in Android Auto.
Last edited: 07/02/2021
Version 6.3 Beta 1 released
- Re-wrote whole rendering process to use GLES20, in simple terms video render should use GPU
- Much better scaling approach
- Added support for native AA Wireless. This will only work on the units where the BT is accessible from the Android, as many of those android powered Chinese units, have a separate BT board. For devices which supports this, no headunit server or no WiFi Launcher is needed.
- Changed key mapping, user can now define their own buttons as they wish.
Last edited: 21/06/2020
Version 5.2 released
- Removed WiFi Direct
- Improved menu UI CREDIT and THANKS TO @sebaw
- Updated margin setting
- Added option to record audio using BT mic (motorcycle helmets)
- Added button to reconnect WiFi connection ( phone and unit depended won't work on all units, please read app forum for how to connect)
- Option to disable touchscreen
- Removed brightness adjustment (some users experienced problems adjusting brightness after using previous version, sadly they need to do a factory reset of the unit, and update to current version)
Version 5 released
- New UI CREDIT and THANKS TO @sebaw
- New over-scan approach allowing any resolution units to work properly (including portrait mode)
- New mic source (should help with speech recognition)
- Added option to keep status bar (user request)
- Added welcome setup
- Added possibility to use old USB driver (android built in one) in case you cannot get it connected with the new version
- Added option for Gain control on mic
- Added option to keep Wifi off (for USB use)
- Changed Wifi Direct implementation (you will need to install the Wifi Launcher for HUR on the phone to use Wifi Direct)
- Removed option to stretch full screen as this is not needed any more (it will always be full screen)
- Fixed Incoming mode not setting password for some devices
- Fixed app crash when Wifi toggled during app running
- Fixed night icon colors for devices running 4.x
- Fixed app freeze if permissions denied
- Fixed app crash after device unplugged when using native android USB driver.
- Fixed day/night calculation if share GPS turned off
- Code cleanup
- Other bug fixes.
Also a big THANK YOU to @ppietak for helping with code cleanup and bug fixes!
Version 4.5 released
- Fixes for USB shuttering
- New USB driver
- Fixes for reverse camera not resuming on some units
- Added support for incoming connection listener (automating Wifi) - Experimental, read below how to connect
Version 4.4 Released
Change log
Fixed broken touchscreen
Changes on WideScreen mode and HD
Fixes for Rotary
Potential fix for black screen for second connection over Wifi
Left/Right hand driving position option (for widescreen)
Buffer setting for mic (could help when Assistant does not hear what you're saying)
Enjoy XDA Ad Free and check out:
Version 4.3 Released
Change log
Fixed double skip on Spotify when using SWC
No more decoder workaround needed (updated code for video playback)
Added support for rotary (arrow keys can be used for non-touch input)
Enhanced mic input (mic sampling rate can be adjusted in settings for better compatibility)
Added intent: "gb.xxy.hr.WifiP2P" for Wifi-Direct start
Added app color scheme (dark menu for night)
Mapped Key N to open Maps (N=Navigation)
Mapped Key L to open Multimedia (L = Listen)
Changed USB code, hoping to help those who suffered for USB disconnection problems
Fixed a serious bug in share GPS code
For some rooted android headunits the app can now disable the default call screen being overlayed when HUR is running (only if HUR is set as the navigation app!) This will require ROOT
Version 4.1 Released
Change log
Removed Google Play Services dependencies
Honda compatibility fixes
Some other small bug fixes
Version 4.0 Released
How to use the app?
USB Mode
Plug in the USB to your device (in case of tablet use an OTG cable), when prompted make sure you allow HUR to be the default app for the action and you check the always box.
If you are running the app on a device with Android 7.0 or higher, you might need to pull down the notification bar and select the connected USB device before the app starts (this is device dependent)
If the app does not start automatically when you plug in your phone, you can always open HUR, tap the USB button and select the phone from the list.
Wifi Mode
READ SECOND POST
Self Mode (when Android Auto and HUR are running on the same device)
Open HUR and press the self mode button. (you need to make sure Android Auto, Google Play Service, Google maps, Google Text To Speech is also installed on the device and it's up to date)
FAQ / Troubleshoot
All I get is a black screen
- If you are using an Android powered headunit (Joying, Xtrons, etc) look for a setting on your device which allows Video Playback during drive
- Try changing HUR settings and enable Software decoding
What does the "Share GPS" do?
- Share GPS actually forwards the GPS data of your device to the phone, so phone will need to do less work, comes really handy if you have an Android powered headunit, with external GPS antenna, however, if you using a tablet which is built into the dashboard, it's possible that you want to turn off this feature, because your phone will have a more accurate GPS fix.
What is the Sink Audio
- This option enabled HUR to work as a speaker for your phone. If you disable this option, all the sounds will be outputted on your phone speaker (or if your phone is connected to a Bluetooth device, then they will be played back on that)
My carrier doesn't provide data allowance for Wifi, what can I do?
Wifi data used between phone and tablet is classed as intranet not internet so it won't count against your data usage, but do be careful if you have auto-updates enabled on the device running HUR those updates will be downloaded over the phone's Wifi hotspot and that will incur data costs.
I have audio-sink enabled but phone calls are coming from the phone speaker. Why?
Android Auto is designed to sink all the audio over USB (Wifi) except phone calls where it will ALWAYS use a Bluetooth headset, if none is connected it will just flip the phone to speaker mode.
Are any hardware keys supported?
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
M Key - Mic
H Key - Takes you to home screen
What about intents?
gb.xxy.hr.playpause Same as pressing the Play/Pause media button.
gb.xxy.hr.next Same as pressing the Next media button.
gb.xxy.hr.prev Same as pressing the Prev media button.
gb.xxy.hr.mic Triggers microphone input.
gb.xxy.hr.phone Same as pressing the dial key (answer phone call when ringing, takes you to dialer screen otherwise).
gb.xxy.hr.day Enables day theme.
gb.xxy.hr.night Enables night theme.
gb.xxy.hr.togglenight Switches between day and night theme.
I need more help.
- Feel free to ask a question on this thread, or you can always drop me an email to [email protected]
How do I collect a bug report / logcat
1. Enabling Developer Mode
1. Open Settings > About phone.
2. Scroll down to the Build number.
3. Tap the Build number 7 times in quick succession until "You're now a developer" appears.
4. Return to the Settings menu and select Developer options.
5. At the top of the screen, make sure 'Developer options' is set to On (green).
6. Scroll down to Debugging and enable both USB debugging and Bug Report Shortcut on (green).
7. Tab on Logger buffer sizes: Default setting is 256K. Select 16M to help capture more information for debugging. Of note, it can affect the apps performance especially with lower spec phone, so change it back after you have finished submitting bug reports.
2. Capturing a Bug Report
It's very important to do this right after you experience the issue again, so your device can log at least one occurrence of the issue.
1. Hold the Power button down until the menu appears.
2. Select Take bug report. and wait for the device to capture the bug report.
3. Tap the 'Bug report captured' notification when it appears.
4. Share the bug report. (I recommend to email it to yourself.)
5. Download the bug report to your computer.
6. Send the bug report by email to [email protected]
IF YOU UPGRADED TO ANDROID AUTO 2.X
Dial Pad is broken - Workaround available:
- Open AA -> About -> 3 dot menu -> Developer settings -> Application mode -> change to developer. This will bring back the Dial screen.
Version 3.0 Released
Changelog:
- Move USB functions from C to Java
- USB popup numbers limited to 2 and they should remain saved
- App will only start on a phone manufacturer vendor
- App is now running in multi-thread for better performance
- Much enhanced Wifi speed
- Better USB stability
- Should work on RK3188 units as well
- App runs as service so can be run in the background as well
- While running in background supports notification control for media
- While running in background on units running 5.0+ and above you will enjoy Heads-Up notifications for navigation
- Ability to rename the "Headunit" to your own prefered string.
- Fixed Wifi-Direct so can connect over Wifi-Direct as well, but not all devices seems to work
- Moved string to XML so translation to other languages should be implemented in the future
- Fixes some memory leaks
- Supports custom hardware keys
Version 2.5a Released
- Fix for USB close bug in 2.5
Version 2.5 Released - Attention contain BUG
- Left/Right button goes into endless loop
- Added support for ARM64
- Changed car name from Emil to Headunit
- Added mirror output support for HUD display.
Version 2.4 Released
- Improved performance (Wifi should be on par with USB now, even with Audio transport enabled)
- Improved touch sync (no accidental long touches and other strange occasional bugs)
- Option to share the GPS with the phone (reduce battery usage footprint on phone)
- Final fixes for Day/Night calculation and theme switching
- Auto volume adjust fixes (on supported ROM, the volume adjuster is hidden from the user)
- Software decoding works with Audio as well.
Version 2.3 Released
- Improvements and fixes for auto volume adjust
- Improvements and fixes for hardware key input
- Wifi speed improvements (should be able to run smoothly even with transport sound enabled)
- Tweaks for SelfMode (home and recent app button can be used to gracefully exit the app)
And the biggest change:
- Unlimited Browsing support - This is experimental and hacky it's possible that Google will close the loophole at some point but for the time being it works.
Version 2.2 Released - With some major changes
- Fixes for Communication Error 2 received with Play Service 10.X
- New Self mode
- Corrected channels order
- Unlimited browsing working when car is parked (only for Android Auto 1.6)
- Totally changed the Day/Night toggle logic, now the calculations are done inside the headunit app and updated each 10 minutes, so if you're driving all day the sunset/sunrise should be correct. even if you are 500 miles more to the north or west or whatever.
- Added Auto adjust volume option (works for bluetooth audio as well).
- Changed all the key mapping, and using real keys instead of simulated touches:
Supported hardware keys:
Volume Up
Volume Down
Media Next
Media Prev
Media Play
Media Stop
Media Rewind
Phone answer key (In case of incoming call it will answer the call, in case of not being on a call it will take you to the dial pad
F key - Same as Phone Key
D key - Changes to Day theme
N Key - Changes to Night theme
M Key - Mic
H Key - Takes you to home screen
The following keys are still usable but they are based on simulated touches:
Up Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
Version 2.0 Released
Changelog:
- Fixed calculated night mode
- Added support for Software decoding (should work now with any device) - If you have problems running HUR, go to settings and enable Software decoding. Do not use software decoding with audio transport, the audio playback will suffer a lot, consider streaming the audio from the phone to a A2DP directly or using a cable to connect the phone Jack to the stereo AUX, or if your phone is rooted you might want to consider Wifi Audio streaming app, it's too much to ask from the Software decoder to do both Audio and Video, unless you have a very strong CPU, but if that is the case I'm pretty confident that the Hardware decoding will work on the device.
- Added option for letterbox display (prevent distortion of stretch)
- Added option to start the app when connected to Wifi
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
Version 1.5 Released - Key features
- Stable Wifi connection
- Added support for Android 7.0 (Self mode as well)
- Self mode running in stable and usable way
- Connecting USB cable will start app automatically (even if phone is running Android 6.0 or 7.0)
- Supports keyboard shortcuts:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
- Uses light sensor (if available) for toggling Day/Night theme.
If you are updating from version older than 1.2 please read:
You won't be able to install it over the old one (Key signature changed!), so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
App requirements:
- Android 4.1 or higher
- H264 Hardware decoding!
How to use the app: (Please read this steps before asking for help)
1) USB OTG
- Plug in the OTG cable to your tablet, connect your phone, done!
2) Self mode (for AA 2.0) - See Video
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Exit Android Auto
- Start HUR and select Self
3) Wifi
- From the phone create a Wifi hotspot
- Start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
- Connect your tablet to the newly created Wifi hotspot
- Start the Headunit Reloaded app
- HTC ATTENTION! If your phone is a HTC, please change the default IP address to: 192.168.1.1
- Select Wifi
4) Wifi Direct (not supported by all phones/tables)
- Start Headunit Reloaded on the tablet
- Select Wifi Direct
- On the phone go to Settings -> Wifi -> Advanced -> Wifi Direct, join the group. (Do not try to connect as to a normal Wifi it will not work!)
- On the phone start Android Auto, Go to About, if you are not a developer yet press the "Android Auto" header 10 times, from the 3 dotted menu select "Start Head Unit Serve"
Other important notes:
Software Decoding
- Based on the feedback although it works, I'm not recommending this app for those with Joying or any other Rockchip (RK3188, RK3066) powered headunit. Feel free to use the trial and decide yourself, but it appears to be painfully slow on those devices.
To exit the app
If you are connected with USB, just unplug the USB cable, DO NOT use the exit from the menu. If you are running Wifi, Wifi Direct or Self mode, ALWAYS use the exit button from the left drawer menu!
Audio transport option
Will forward (sink) all the audio from the phone to the tablet if enabled, EXCEPT phone call audio, that will go trough the phone speakers or Bluetooth Handsfree if connected. If you wish to stream all the audio from the phone directly to your A2DP bluetooth, then simply disable the Transport Audio option.
Day/Night toggle
The device running the Headunit Reloaded app will be responsible for changing the theme. You can chose between using the light sensor of the device to toggle between day and night mode, or you can use calculated sunset sunrise mode, or even force it to one theme only. If you have previously installed AA Helper to your phone, please uninstall it!
Auto Start on Wifi
This option will launch HUR whenever you are connected to a Wifi (specific Wifi can be named)
Auto increase volume on speed
The logic behind is a very simple approach, every time the speed increases it will send a vol + key to the phone and every time the speed decrease it will send a vol - to the phone. This requires the device running HUR to have a GPS receiver.
OLD STUFF:
Version 1.3 (Wishlist version) - Released
- Added option for easy car mode toggling. (Car mode can be disabled if not using Self mode - avoid conflict with other Car apps)
- Auto Hide status + action bar while running the app no need to use the Hide option from menu
- App will automatically close when Wifi connection is lost
Version 1.2b - Released
- Buffer overflow protection - Special Thanks to invis-zz from GitHub (https://github.com/invisi-zz) - This should random crashes while using the app.
- Removed Send Log feature (it was classed as backdoor/trojan and Google was blocking the app on playstore)
- Updated OpenSSL library to 1.0.1t (used OpenSSL contained vulnerabilities and Play store blocked the app)
- Managed to get the app on PlayStore (wonder if it will stay...) - https://play.google.com/store/apps/details?id=gb.xxy.hr
Signature Key changed!!!!
I had to update the APK signature key (I'm trying my luck with Play Store), this means if you try to install the new version you won't be able to install it over the old one, so please uninstall the previous version before updating, HOWEVER if you were upgraded for free from Mike's version, please follow this steps:
1) On XDA Labs, click the download Stable
2) When prompted to install select Cancel
3) Open a file explorer and go to Storage -> Android -> com.xda.labs -> files
4) Locate the newly download APK and copy it somewhere else.
5) Uninstall the old version
6) Install the APK which you just copied.
If you miss any of the steps, just reinstall the old version you received from me by email and try again, let me know if you are stuck.
Version 1.1 Stable - Released
Jumping the version number due to significant amount of changes:
Removed Day/Night/Auto mode (see bottom of this post for a better solution.)
Added new setting for 720p Video - Fully working now (even on Wifi)
Changed Self mode start sequence (if the phone is rooted it will start automatically and then go back to HU), if your device is not rooted, please use the following sequence to start Self mode:
Start HU app
Select Self mode
When AA opens select Start Developer Server
Added support for hardware keys (simulating touches), so if your tablet is integrated with the car remote you can control AA from the remote.
Hardware keys as follow:
M = Start the Mic
N = Navigation Tab
P = Phone Tab
H = Home Tab
E = Entertainment Tab
UP Arrow = Scroll Up
Down Arrow = Scroll Down
Left Arrow = Moves to next Left tab
Right Arrow - Moves to next right tab
S = Play/Pause button (only works in Entertainment tab)
F = Next track (only works in Entertainment tab)
R = Prev Track (only works in Entertainment tab)
Some other minor tweaks, to improve stability and make Self mode connect 9 out of 10 times.
Fully integrated x86 native binaries
Declared app as CAR HOME, for those using SelfMode it is crucial, that when you get prompted which should be the default CAR HOME app (Android Auto or HU) you select HU!!! - This is needed to be able to bring back the HU on top after a successful connection is established. AA is trying to override everything..... and to block the user out of his phone as soon as it's connected to the car.
Transport Audio option will affect USB connections as well (You can keep the audio on your phone/bluetooth, when connected with the OTG cable)
Version 1.03b released - Beta
- You will find it in XDA Labs (under the Beta version)
- Fixes Wifi/Self mode for some devices which didn't connect before
- Increased stream buffer size to match the DesktopHeadUnit app (128Kb vs 64Kb)
Version 1.02 release
- Fixed wifi not connecting on some device only after numerous attempts (see explanation below if interested)
The issue looks to be related to the timing, on some occasions and on some devices the phone either sends the SSL data too soon, either too late, either to slow and because the TCP socket is set to non-blocking mode, it can end up in a missed packet in the initial Handshake. I have tweaked this now, so the TCP socket will connect in non-blocking mode, but will switch to blocking mode and wait for full message after a successful connection and once the SSL Handshake is out of the way it will revert back to non-blocking mode, uhhh event reading this makes me dizzy
This however could make the initial startup slightly slower than it was.
- Corrected AutoStart option (Working properly now)
- Fixed USB device overlapping Settings text on the drawer menu
- Added "Send Log" function to be used if there are problems for easier debugging.
Version 1.01 released
- Potential Wifi disconnect fix (see: http://forum.xda-developers.com/showpost.php?p=68078605&postcount=16 for details)
- AutoStart option added to the menu
Very sadly Mike passed away this year and his software stopped working after a Google Update, he left us a slightly outdated GPLv3 version of the software at: https://github.com/mikereidis/headunit which I have used to rebuild (or ty to) rebuild up to his latest build with some additional small modifications as well as fixing the issue caused by Google.
The forked version can be found on: https://github.com/borconi/headunit if anybody is intersted.
Since the app released by him isn't working any longer I have created the new version of it and slightly re-name it just to avoid any confusion.
I take almost no credit in this app, except for some minor changes, and finding the fix for what Google have broke (changed), which was a painful task.
I'm not a developer as such, and this app would never have existed if it wasn't for @mikereidis, however I have spent now several weeks studying the app and understanding how it's working and I plan to continue with the maintenance/development of the app.
I have published the app on XDA Labs under the new name: "Headunit Reloaded Android Auto" and it is now available for purchase. As I have stated previously I'm intending to support all of Mike's customers, so if you have purchased Mike's application before, please email me a proof of purchase to [email protected] and you can have a free copy of the spin-off app.
How to use (Self / Wifi ) ?
1) Self mode.
See instructions in version 1.1
2) Wifi Mode
Start AA on your phone, tap the header 20 times till you become a developer, once that is completed from the menu select Start Head Unit server. Now start tethering on the phone, connect the tablet to the newly created wifi hotspot, start HU on your tablet and select Wifi. This will make the HU app try to connect to the default Android gateway (192.168.43.1), if you need to change this, use the Settings menu from the HU option list. If HU doesn't start on first, do try a few more times, first setup sometimes proves tricky. If this is the first time you connect your phone to the a HU, please make sure you answer all the questions on the phone.
3) Wifi p2p
This is not supported by all devices and might not work for your device, plus sometimes it can be slightly buggy. Start WifiP2p on the tablet from the HU. On the phone go to Wifi Direct (this is usually found in Advanced Wifi settings settings - DON'T TRY TO CONNECT LIKE TO A NORMAL WIFI and look for a new available connection. If you can see one tap to join. Once you joined the network, give it about 30 seconds or so, then open the AA on the phone and start the head unit developer server (same as describe it above). If you're lucky it will work instantly, if not you might need to play around with it.
Other Options:
Possibility to toggle the Audio mirroring when using a Wifi connection. By disabling the Audio mirroring, you will keep all the audio on your phone rather than on the tablet (or on the handsfree) if the phone is connected to the handsfree. This will improve the performance greatly, since audio will use up a significant quantity of Wifi bandwidth when communicating between the 2 device.
USB OTG connection.
Have remained unchanged and it will work same way it did till now, see original threader for details.
I will monitor both Threads and will do my best to help and support everybody.
Well done! Thanks so much for your hard work Emil.
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Syphe said:
*Purchased
Also cloned and starting to build it as am having issues with my Joying head unit showing black screen after connecting (Test shows a black screen also).
looking forward to getting this running.
Click to expand...
Click to collapse
What version of Android is your unit running? I haven't heard of any with less than lollipop being able to run this so far, h.264 decoding is absent or poorly implemented.
Edit....see the bottom of this post
http://forum.xda-developers.com/showpost.php?p=68010519&postcount=1449
Wifi Mode - Starting with HUR 7.X
Braking changes with version 7.X
Only for phones running Android 9 or higher, if you still use Android 8 phone, you won't be able to connect over WiFi. Device running HUR, can have any version of Android.
Phone Setup:
Install Wifi Launcher for HUR on the phone ( https://play.google.com/store/apps/details?id=com.borconi.emil.wifilauncherforhur&hl=en_US )
Make sure you give the app all the permissions, including draw over other apps, otherwise it cannot start Android Auto from the background!
Open the app and select the car's BT adaptor from the list (make sure phone is NOT connected to the car's BT, but BT is enabled!)
If you want your phone to create the hotspot, turn on the option to Enable hotspot (this will probably not work if you are on Version in the USA due to carrier limitations!), likewise if you want your car to create the hotspot or you want to use an incar wifi module, leave this option turned off.
Only turn on the legacy option if HUR specifically instruct you so.
Car/Headunit setup:
Connect to the phones hotspot or if you are using an incar WiFi connect to that network. Alternatively if you want HUR to create the hotspot and connect your phone to it, enable the option in HUR settings.
Open HUR
As soon as the 2 devices are on the same network, HUR will fire up on your car screen.
Emil Borconi said:
Hi Syphe.
The core of the app is the same as the original, and the app does require a hardware H264 decoding supported by the OS. Till now we are not aware of any chinese HU which support this. Please contact me by email and I'll refund your purchase.
Click to expand...
Click to collapse
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Christopher Price said:
You might want to post a "demo" version with just Mike's test mode that plays an H.264 screencap of AAuto running. Would be a good requirement-diagnostic app to have on hand, wouldn't take much time to bake - and it wouldn't have to track source either...
Just be sure to have it display a message popup saying that this is only a requirement check app, not an interactive demo. Something that informs users that its sole purpose is to make sure the decoders work. Maybe call it "Headunit Decoder Requirement Check.apk"
Click to expand...
Click to collapse
Yeah I thought about that myself.... will probably create a small check app in the near future (just need to catch up with all my other work now, which has been pushed behind to get this done)
bugger, thought it was quite promising when everything started to connect itself
I've been building my own app to do simple notification mirroring over a wifi tether, but this would have been much easier haha.
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
kevster0522 said:
Does anyone know if there is a problem with xda labs on marshmallow or something? I've been trying to download this head unit app for the past week (was trying the old one and now this new one) and every time I click the pay now button for PayPal it just hangs there saying "Contacting PayPal". Is there maybe some other way to purchase the app? Any help would be appreciated, I really want to try this app out!
Click to expand...
Click to collapse
Hi.
Yeah the XDA labs app can sometimes play funny, if your having any kind of issues feel free to contact me directly be email, on [email protected]
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
fmark said:
Hi Emil,
I had a chance to play with your new version. I got it to work, however it was not simple and I have a few issues.
I'm using it in WiFi mode. My Android TV stick(5.1.1) runs HeadUnit app and is connecting to my phone (Samsung Galaxy S7 Edge) that runs WiFi hotspot option.
The problem is that I need to click WiFi (in the menu of HU) many times for it to connect to my phone. It can take 5 to 15 clicks on Wifi option in HU for the phone to connect.
Is it the same for you? Any idea what can be the problem?
Also, I'd like to automate it somehow. I'm not using USB, so I'd like the HU app to be always ready for WiFi connection. Is it possible?
Thank you!
P.S.: I have some other issues/comments as well, but I'll keep them for later
Click to expand...
Click to collapse
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Emil Borconi said:
Hi Mark.
No it's connecting usually on the first attempt (sometimes on the second) but most of the cases it's first one. Yes I do plan to add a setting for Auto-Start mode in the settings which will make the app start in (Self / Wifi / wifip2p) as selected.
Does your phone have 3g/4g connection while tethering? The change which broke everything im Google Play service 9.2 is actually running a certificate check against google server, so without an internet connection to it won't start.
I had once or twice problem with the wifi myself (I got a debug message saying no route to the ip, meaning the Routing table on the tablet (stick in your case) got something wrong) a simple restarted did cleared the problem.
Please do report back if the problem persist and I'll send you a debug enabled app so I can get an understanding of what is going on, however probably that won't happen before Wednesday, looking forward to a long weekend.... of field work that is..
Click to expand...
Click to collapse
Yes, my phone has 4G connection while tethering.
Lets try the debug output. Could you please send me the .apk with debug messaging? I'm curious to see what is going on when it fails to connect.
Thank you!
Im interested too because isnt working on my s4 and nexus7 2012
wpostma said:
Im interested too because isnt working on my s4 and nexus7 2012
Click to expand...
Click to collapse
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Christopher Price said:
Need much more information to help. What S4 firmware, carrier, and Android version are you running? What Nexus 7 firmware? Are you trying to connect over Wi-Fi or USB?
Click to expand...
Click to collapse
It might be about the Wifi connection, I had some connectivity issues over Wifi myself the last day, but they were fully random, at a first look they point to the TCP socket.... I'm investigating this.
I got some Wifi disconnected myself but it is very random, it can occur after 1-2 minutes or after 3-4 hours... so testing potential FIX for the issue isn't going to be easily. At the first investigation it looks to be something related with the pooling/keeping connection alive. I have tweaked this and made a new build, currently running for about 20 mins and looks OK, but as said the disconnect can occur randomly at any point.
The worst part is that the logs do not give any hint on what could be the cause of this, neither on the HU part, neither on the AA side, they only mention a broken PIPE bu no hint on what can be the cause...
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Christopher Price said:
I'm guessing you've already tried, but running a 0 byte ping in the background every few seconds to keep the pipe open?
Click to expand...
Click to collapse
setting socket to keppalive looks to sort the problem, I'm trying to figure out failing handshake at the moment. On TCP sometimes the handshake fails, trying a few more times passes..., handshake over usb always passes....
Looking at the code and notes Mike seems to struggle with it as well in the past...
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
skitty said:
When trying wifip2p, I can see the wifi connection from the tablet on my phone but when I try to connect to it, it wants a password. How do I know what this is?
Click to expand...
Click to collapse
Emil Helped me with this problem. You don't actually connect through your wifi networks menu, use Wi-Fi Direct instead. Found here: wifi networks menu > 3-dot menu > Advanced > Wi-Fi Direct
Can system settings be changed without root
I have gone into settings then sound settings
I then get an if statement
I just want to turn my system sound back on at a certain time
Im not sure what to do
Thanks
trickyrick said:
...
I just want to turn my system sound back on at a certain time
Im not sure what to do
Thanks
Click to expand...
Click to collapse
This sounds like you want to disable DND (do not disturb). The action for that doesn't require root. It's in audio category. The "all" setting will allow all sound, effectively disabling DND. I believe you must enable Tasker's notification setting in the system settings (main OS, not Tasker). If you are using any relatively recent Tasker version, you should be prompted for any missing permissions the first time you setup the (any) action.
Can system settings be changed without root
I have gone into settings then sound settings
I then get an if statement ....
Click to expand...
Click to collapse
Yes, Tasker is designed to run most of its actions without needing root. You do need to give permissions through ADB for some restricted actions, such as using the AutoTools plugin -> secure settings action. I think this is the action you are asking about. See Tasker User Guide - Grant Secure Settings
I have no idea what you mean by "I then get an if statement".
If you have a task (or profile) that doesn't work the way you expect, it helps others help you if you post the entire task (profile).
Before exporting, if you have sensitive information such as logins, api keys or anything else, you might consider setting those values to a variable and use the variable in your tasks so the values won't export with the task.
To export a task (profile) description for posting, press on the name to highlight the task (profile). Go to the 3-dot menu and select export -> Description to Clipboard.
Now you'll be able to paste it. Be aware, it easier to use something like pastebin.com / hastebin.com and link to a post here. If you paste directly into a post here, the forum software will convert semicolons with characters directly after, into emoticons making it very hard to read.
Thanks for the replys
It's my wife's phone she goes to work and turns the sound off (not the DND) She drops the menu down and clicks on the sound icon then there is a line through the speaker icon at top of screen. She forgets to turn on the sound when she leaves work and I can't get ahold of her cause she can't hear the phone ringing. Was hoping to use tasker to turn sound back on at 5pm
I use ADB to connect tom my AmazonFire TV
Ive tried to connect to my cell but cant
ADB connect (ip of cell on my network)
It says it cant connect
Ive opened a command prompt within the install of the ADB
USB debugging is already on
When I attach phone I get no promt to alow debugging
trickyrick said:
I use ADB to connect tom my AmazonFire TV
Ive tried to connect to my cell but cant
ADB connect (ip of cell on my network)
It says it cant connect
Ive opened a command prompt within the install of the ADB
USB debugging is already on
When I attach phone I get no promt to alow debugging
Click to expand...
Click to collapse
ADB requires the proper drivers for the device installed on the computer your using. Using a data cable would be more reliable than over Wi-Fi, particularly to set-up. At the top of the forum, in the search manufacture and model of the device then it's forum should show up in the results. Every device forum has an "ask any question help thread". If you can't find how to ADB to the device in the forum, that's a good thread to get help in.
However, to turn the ringer volume up doesn't require anything special. Audio -> ringer volume. Explore all of the volume settings actions in the audio category.
Ok ill explore how to install ADB for my phone. In regards to the sound. You said it easy to turn volume up but my system volume is off not turned down Any option I try to turn volume up does not work. I dont see an option to first turn it back on
OK well Ill be dam. Figured out the ADB
Now its working turns the sound on at the specified time
Thanks for all your help have a good day