yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] jakejm79:
I would cut the wires going to the internal mic in the middle (so you never need to worry about soldering to the board) and then just wire in one of those 3.5mm jacks that has would only bypass the internal mic when an external was plugged in.
[Android Head-Units] andsmith79:
Thanks for the response! I could definitely give that a shot. Would still like to understand what's going wrong with the way I'm attempting to wire in the new jack. Could it possibly be something to do with the gauge of wire I'm using? I tried with 22 gauge solid conductor as we as the stranded wire in the pics. I've also included a pic of my soldering job to the PCB.
[Android Head-Units] jakejm79:
Everything looks fine and that is exactly how I did mine, have you tried a different mic?
[Android Head-Units] andsmith79:
Yep that's what I thought. I tried with an external mic from an old Kenwood car radio I had. I spliced the cable which contained a copper wire and another small copper shielded cable. I cut the wires that I soldered to the board and connected it to the spliced ends of the mic and could not get any outbound audio. I bought a cheapo stereo mic from Microcenter that I might give a try next. I tried this one connected to the jack I installed without success. If I were to splice the wires of the stereo mic any idea which wires would be the ones to use? I'm guessing just trial an error until I finally touch the correct pair.
[Android Head-Units] jakejm79:
You would want to use the shield (which I assume would be ground) and then one of the +ve feeds for either channel (either of the insulated wires) in theory it shouldn't matter which you use, but you could always pick the left one to be consistent with the whole mono/stereo thing.
[Android Head-Units] jakejm79:
So I have on last issue I am trying to resolve, a way to launch 'Voice Search' from a long press of one of the a steering wheel button.

I currently have my SRC button mapped to Home (scan code 102), long press seems to bring up the Recent Apps Popup.

If I change the keypad.kl layout so scan code 102 points to SEARCH then pressing the SRC button once does indeed open Google Search, but long pressing of it still brings up the Recent Apps Popup, it is as if a long press of the button associated to scan code 102 brings up Recent Apps Popup regardless of way is mapped to scan code 102 in the keypad.kl file.

I have tried the same thing with the menu button (scan code 139) and a long press just behaves the same as short press, i.e. I change the keypad.kl file so scan code 139 points to SEARCH and a short press will open Google Search but a long press will also open Google Search (it should open Voice Search), I believe this is because the way the SWC are setup, i.e. MENU - (L)MENU and rather than a long press = a long press of menu and long press just equals a single press of menu. I have tried mapping a different function to the long press, i.e. MENU - (L)MUTE and it doesn't seem to work for the second function and nothing happens on long press.

I have tried using the Xposed Additions module and the long press action is never processed, I think that is due to the reason above and the way the MCU handles the long presses from the SWC, therefore Android never sees a long press.

Also it appears that a long press of scan code 102 brings up Recent Apps Popup regardless of what action scan code 102 is mapped to in the keypad.kl layout, same for scan code 158 (default BACK) long press of that kills the current Audio App regardless of what action its mapped to.

Anybody have any ideas on how to map Voice Search (or any other app) to a long press of a SWC button?
[Android Head-Units] donaldta:
Have you checked what the result is when you use the KeyTest app when you hold down whatever key? As I understand the MCU doesn't necessarily pass on the long press. So, you're better off programing a long press function that you do not use to switch its scancode with SEARCH keyevent.

Technically, the KEYCODE_APP_SWITCH wasn't implemented until Honeycomb (Android 3.0 - API Level 11). So, your Launcher might have an OnKey listener service registered for a particular scancode or keycode and brings up the recent apps.
[Android Head-Units] jakejm79:
A long press is registered just the same for Scan Code 102 (home), 139 (menu), 158 (back), 164 (play/pause), 163 (next) and 165 (prev). Those are the only scan codes (the default action is in parenthesis) that I can map to the steering wheel controls (I really hate that they didn't include a search action as mappable to the SWC, it was common on pretty much every GB device).

I think the problem is that a long press from the SWC (or panel keys) is never passed on as a long press (since the SWC settings allow (though it doesn't actually work) for mapping of a different action for normal press vs. long press). The only ones that do appear to pass on is the long press scan code 102 (home) that does the Recent Apps Popup and 158 (back) that kills the app, I do need to try a different launcher to make sure that the Recent Apps Popup is just the default Recent Apps action and not something independent of that the MCU calls up.

I've delved into the smali code in the android.policy.jar file, and I think I have found the correct area to edit, I just don't know what to change.

.line 511
new-instance v0, Lcom/android/internal/policy/impl/[B][COLOR="Red"]PhoneWindowManager$3[/COLOR][/B];

invoke-direct {v0, p0}, Lcom/android/internal/policy/impl/[COLOR="Red"][B]PhoneWindowManager$3[/B][/COLOR];-><init>(Lcom/android/internal/policy/impl/PhoneWindowManager;)V

iput-object v0, p0, Lcom/android/internal/policy/impl/PhoneWindowManager;->mHomeLongPress:Ljava/lang/Runnable;

Changing the part in red (the PhoneWindowManager$3.smali file seems to contain the code for the the Recent Apps Popup), I just don't know what to change it to launch Voice Search instead. The only other reference to long press is for the power button so I can't just swap the code for the search button.
[Android Head-Units] donaldta:
Not sure if it applies here but have you seen this?
[Android Head-Units] jakejm79:
I think that is for devices with a navigation bar (i.e. onscreen buttons) since the UI handles the input for onscreen buttons. The file that is referenced to doesn't exist in the Ouku's 2.3.X SystemUI.apk.

I took a closer look at PhoneWindowManager$3.smali and at the end of the code is the following:

invoke-virtual {v0}, Lcom/android/internal/policy/impl/PhoneWindowManager;->showRecentAppsDialog()V

I think the key part is the 'showRecentAppsDialog' if I could change that to 'launchVoiceSearch.apk' or whatever the correct term would be it should then work.
[Android Head-Units] sciallo:
I don't have a unit to test with, but if I remember right there was a third option for super-long press, ad we speculated it might be to allow for a long press event of the regular press ... Eg. try to set a super long press for the home button, and see if long press will now be passed by the MCU...

Just a thought.
[Android Head-Units] jakejm79:
I did try that a little and I think it just extended the delay between when the single press action was activated and the long press action was activated (even though you cant seem to have separate actions for the SWCs), i.e. setting Menu-(L)Menu, one press = menu, long press (after 1 second) = menu. Setting it to Menu-(S)Menu, one press = menu, long press (after 2 seconds) = menu.

But I will definitely revisit it, seems like it would make sense since there isn't really much reason to differentiate between a 1 second long press and a 2 second one. I wont hold my breath about the home button since long press of that always worked (it just forced the recent apps popup regardless of what I tried to associate with it). But if I could get it to work with menu, I can then edit the kl file and used xposed advanced to hack my way to where I want to be.

I s'pose I could get another JoyCon EXR, but I have a hard time spending $50 just to get this one little problem sorted.
[Android Head-Units] mano154:
Hello everyone, I have been following this thread for sometime, I have read every post but there is one thing that I can't understand. I bought my unite from pumpkin, custom made for the camry. I have noticed that many of the systems discussed here my have a different appearance, but have the same system information.

First, can I upgrade this unite to a higher firmware or different firmware.

2nd, Is it possible to root this device, and if its possible how.

Please any help will be appreciated. Thank you

This is the system.

View attachment 2546555

CUP Information

Freescale I.MX53

RAM Information

512N DDR3 800

Andriod Version

2.3.7

MCU Version

2.19.9-1-10-1

System version

2.20.21

DVD Version

2.13.11-1200wb

I have never rooted before so this is my first time. Please any help will be appreciated. Thank you
[Android Head-Units] donaldta:
Just use Framaroot.
[Android Head-Units] sciallo:
[MENTION=5389783]donaldta[/MENTION] you're confusing this with the s150?

Yes, the roms available here should work AND installing those will give you root. Nothing you need to do really.

---------- Post added at 10:24 AM ---------- Previous post was at 10:22 AM ----------

See Wiki page
[Android Head-Units] donaldta:
Yeah, you're right. I am. I should probably just refer people to the wiki.
[Android Head-Units] mano154:
Hello and thank you for replying sciallo,donaldta.

Which one of these should I download, I know that I have a Capacitive screen and use a wifi dongle thats hooked up to the back of the screen.

Capacitive USB OBDII SW Controls.zip - This is for capacitive screen units that use a USB OBDII dongle with Torque Pro

Capacitive BT OBDII SW Controls.zip - This is for capacitive screen units that use a BT OBDII dongle with Torque Pro .Thank you any help will be greatly appreciated
[Android Head-Units] donaldta:
It actually doesn't matter which of the two you use, unless you intend on immediately using Torque with a specific ODBII adapter type for your car. The one for the USB ODBII has the /etc/carit_version2 file necessary for Torque Pro to scan the Linux devlinks. However, this same file blocks the use of Torque from using a Bluetooth ODBII adapter, hence the different versions. So at a later time, should you choose to get the opposite from the one you had used then you can just add or delete the file as necessary instead of reflashing the ROM.
[Android Head-Units] jakejm79:
Yeah all the long press vs. sup long press does is vary the time needed for the long press portion to activate. That being said the (super) long press function doesn't really work on these units, you can't set a separate function for the long press portion. Also it seems no way to get a long press to Android, since they are handled by the MCU (I believe due to the long press function of the SWC settings, despite the fact it doesn't work). The only time I can get anything to resemble a long press to android is for home and the recent apps popup, but I'm thinking that is actually still handled by the MCU and android never sees the long press action.

I think I am just going to use home2 shortcut, a double click of home for voice search is close enough I guess.
[Android Head-Units] donaldta:
I've notice that this was in the rooting section of the Wiki for the Ouku unit. Have you tried using the following content as /system/etc/permissions/android.hardware.bluetooth.xml file.

<?xml version="1.0" encoding="utf-8"?>
<!-- Copyright (C) 2009 The Android Open Source Project

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->

<!-- This is the standard feature indicating that the device includes
Bluetooth -->
<permissions>
<feature name="android.hardware.bluetooth" />
</permissions>

...and...

<feature name="android.hardware.bluetooth" />

...into the tablet_core_hardware.xml file if it exists? This should add the Bluetooth section into the Setting app but it won't work unless you actually have a Bluetooth module that is accessible from Android.
[Android Head-Units] mano154:
Thank you so much, I Just finished updating and everything works fine.Its slower then before and uses a lot of memory but I guess that how updates are.Thank you so much, and god bless you.
[Android Head-Units] sciallo:
That hasn't come up before... Can anyone confirm? care to elaborate a little?

One of the advantages of these cusom roms used to be faster boot time and less bloatware... Maybe we added a few too many kernel modules and would be better off just using the ones we need for our adaptors?
[Android Head-Units] jakejm79:
I didn't work on any of the Bluetooth stuff (Hal9K did that), I just posted everything that was in the most recent ROM since I had worked on that. I can try and take a look and see if it makes any difference, but are you saying I would need a working usb Bluetooth dongle to verify it, because I don't have one of those.
[Android Head-Units] mano154:
Hello and thank you for replying

One of the things that I noticed when using the new update is that its lags when opening or closing applications, so I installed an app that I used before to free memory, Its called Clean Master.What I noticed is that the system is using 90% after the update instead of 60% before the update of its memory.I used Clean Master boost memory and close all the applications on the system but it only goes back to 80%.The apps take longer to open especially the navigations apps, also I don't have as many installed apps as I did before.Thank you and I hope this helps, if you need anymore information please do not hesitate to ask.
[Android Head-Units] donaldta:
I don't think anyone has bothered to make one. There have been a few people that have reported success in this thread though. Just use the "Search this thread" tool to filter them out.

Yes, I believe that's for a completely different unit; he S100/S150.
[Android Head-Units] donaldta:
Okay, I took a look into Torque Pro a little more. I decompiled the APK and in the Torque_1.8.12\smali\org\prowl\torque\landing\FrontPage.smali file, I found the following lines of code.

new-instance v4, Ljava/io/File;

const-string v0, "/system/etc/carit_version2"

invoke-direct {v4, v0}, Ljava/io/File;-><init>(Ljava/lang/String;)V

invoke-virtual {v4}, Ljava/io/File;->exists()Z

move-result v0

This is the part which Torque Pro identifies that the /system/etc/carit_version2 file exists and I guess acts accordingly for your device.

sget-object v0, Landroid/os/Build;->USER:Ljava/lang/String;

const-string v1, "Parrot"

invoke-virtual {v0, v1}, Ljava/lang/String;->contains(Ljava/lang/CharSequence;)Z

move-result v0

For the Asteroid, it is checking the User String of the Build. You can also see the information with the following commands.

$ [B][COLOR="RoyalBlue"]getprop ro.build.user[/COLOR][/B]
Parrot
$

I'm not sure if you want to try to spoof this on your device but the setting is in the /system/build.prop file.

$ [B][COLOR="RoyalBlue"]grep ro.build.user /system/build.prop[/COLOR][/B]
ro.build.user=Parrot
$

If it works then you should be able to reduce the number of different ROMs for the Ouku.
[Android Head-Units] jakejm79:
Thanks Donald I will give that a try.
[Android Head-Units] Prdie:
Bluetooth dongles

Hi guys, I've got another not yet succesfull hunt for the correct bluetooth dongle to work with OBDII BT adapter and my OUKU 2.3.7

The adapter is this one, I've chosen it due to it's size :

http://www.ebay.com/itm/Super-Mini-...ter-Auto-Scanner-TORQUE-ANDROID-/171157742809

I'm able to connect to it with my notebook and scanning works without problems with supplied ScanMaster software. So I assume, that it works and it's not defective.

First dongle I tried is Trust 3.0 :

http://www.trust.com/products/produ...CONNECT&ProductGroup=USB-ADAPTERS&artnr=17772

It doesn't even connect to the android (the BT checkbox in QBT Lite cannot be checked), probably due to the Atheros 3000 chipset. No worries, let's try an older one.

Then I found these two dongles, quite cheap and similiar to ones already confirmed as working in some of the previous posts. Linux mentioned as well, only BT 2 supported which is ok I assume :

http://www.softcom.cz/eshop/bluetooth-usb-ultra-mini_d55412.html

http://www.softcom.cz/eshop/bluetooth-adapter-pro-bezdratovou-komunikaci-_d67090.html

Both are working in the same way :

The android recognizes them and BT can be turned on.

Both can be paired with internal MCU BT phone module (just for testing, I've unpaired them then)

Both can be paired with the OBDII module (I've used pairing code 1234) - QBT setting shows OBDII - paired but not connected

But neither one can support connection from any OBDII program (Torque Pro, Lite, ScanMasterLite etc...).

Forex Torque : When I launch it, it shows in the adapter status, that the device is BT enabled (first row) and that it is connecting to OBD (second row). Then it connects (second row shows ok), but after a second it disconnects, forcing the BT to shut down and to turn on again. And this behaviour is repeating forever.

Scanmaster is the same - message connected OK to the OBD adapter followed by disconnect, bluetooth turn off and turn on again.

Could you suggest anything to debug ? Anything to set up ?

Thank you

Prdie
[Android Head-Units] ryrager:
Identifying this unit?

Hi All

Can someone help me identify this unit?

Please add http and www to the link below

aliexpress.com/store/product/TOYOTA-RAV4-Android-Car-DVD-GPS-Radio-Player-2009-2010-2011-2012-With-TV-3G-GPS/104670_1478009408.html

Would like to mod it etc.

Thanks
[Android Head-Units] G2k0:
Hey guys. Just a heads up, I added the BT dongle and USB hub I've been using on the wiki page. JakeBullit had found and mentioned these many posts ago. Nice small and inexpensive. The BT is a Komodo Mini Bluetooth Micro Wireless Dongle Adapter (you can find them on amazon & ebay for about $4). See wiki ;)

[MENTION=1926253]Prdie[/MENTION] - I have a similar OBDII (looks just like yours but its white). Works fine. The 2nd set of BT adapters look like the ones I mentioned above. Those should work fine (look just like the one I have). On occasion mine also does what you mentioned. I noticed that if the unit powers up and if the BT icon appears in the status bar, Torque will pick it up. Its almost like hit or miss. I dont use torque that much as it doesn't really provide me with any info I need to know or dont already know (probably because of the model/make of my car and the fact that most of the info I would like to know is thru canbus which Torque does not detect). So I use it if I need to see any diagnostics (which is rare).

On a different note has anyone with an OUKU notice the GPS (on occasion) go crazy? It seems like every so often my location is off (sometimes up to 100m or more). While driving its a pain because it keeps trying to recalculate my route. I've seen this happen with Waze and Google Maps (as these are the two gps apps I use).
[Android Head-Units] sciallo:
According to the Generic Android Head Unit wiki page:

http://xdaforums.com/wiki/Generic_Android_Head_Unit
[Android Head-Units] ryrager:
Thanks but not really

I thought so too but its not running WinCE, just android 2.3.4 or Qdroid
[Android Head-Units] sciallo:
pure android (both your listing and the s150) the s100 runs wince but can be converted since it's the same hardware...

Confirm it with the guys at this thread
[Android Head-Units] donaldta:
Technically, the S100 runs WinCE and Android 2.3 but I fail to see where that was mentioned in the wiki link you posted. It is not supposed to be. The S150 is currently a "pure" Android 2.3 version but according to Alan Wong (the ROM developer) there is no difference with the upcoming models that will have 4.0 pre-installed.
[Android Head-Units] jakejm79:
Didn't work, Torque would give an error message about USB device manager not being able to be started or something similar and under USB settings it would just display no compatible adapters found.
[Android Head-Units] donaldta:
Darn. Sorry, I guess you're stuck with carit file. If you'd like I can create a script to create / delete the file as necessary. Heck, I can create a Tasker App Factory APK to switch between the two conditions as necessary. This will prevent you from having to supply two separate ROMs just for Torque's sake.
[Android Head-Units] jakejm79:
Maybe, but I don't think I will be releasing any more ROMs, there really isn't any bugs/issues left to be resolved (at least things that aren't a personal preference) that would need to be packaged into the ROM.

Maybe Ian should package the option for creating the carit file into torque pro, lol.
[Android Head-Units] sciallo:
There is a thought, and it seems he is one of the more responsive developers, I wouldn't be surprised to see him do that.
[Android Head-Units] jakejm79:
Yeah maybe he could add a 4th option when picking the adapter type, BT, Wifi, USB and then whatever specific form of USB is invoked with the carit file being present.
[Android Head-Units] donaldta:
Please tell me you're kidding. The /system/etc/carit_version2 file is an original file from the Ca-Fi units which Ian uses to identify Torque Pro is running on one. The idea is that Torque Pro will alter its sub-routines accordingly so that it use an ODB2 adapter that is connected to its USB port. JakeJM has included this file in 2 of the 4 ROMs of the Ouku to spoof Torque Pro into thinking it is running on a Ca-Fi unit. The drawback to these files is that it also seems to disable the use of a Bluetooth ODB2 adapter with a USB to Bluetooth dongle installed on the unit.

I've been trying to help him find a way to reduce the number of ROMs because it is confusing for people to pick which of the four to use.

Well, just in case you change your mind, I created a stand-alone APK with Tasker App Factory. The only caveat is that you'll need to install busybox if your ROM does not already include awk, [, chmod, mount and rm command line binaries. The app drawer name is "Toggle BT/USB" and has the Torque icon. Each time you launch the app it will cycle the files as necessary for BT or USB.

I also included the Tasker.xml file incase anyone wants to modify or import into their own Tasker projects.
[Android Head-Units] jakejm79:
Thanks Donald, I haven't looked at the apk yet, but does it include any toast notifications? i.e. a pop up at each toggle, just thought it might be a little easier if you lose track of which mode it is in, rather than having to load up TP to check.
[Android Head-Units] donaldta:
Yes, it does. It shows a toast message for each file modified. You can also verify by looking at the presence of the /system/etc/carit_version2 or /system/etc/permissions/android.hardware.bluetooth.xml files.

---------- Post added at 08:28 AM ---------- Previous post was at 08:19 AM ----------

Btw if you can provide me a copy of the handheld_core_hardware.xml or tablet_core_hardware.xml file that comes with your ROM, then I can also add the necessary lines to enable the Bluetooth menu in the settings application.
[Android Head-Units] jakejm79:
Thanks Donald, I will create a new ROM at some point soon that includes this.

I couldn't find either of those xml files, I checked the /system/etc/permissions/ folder and also did a search on the whole system image and found nothing, but feel free to take a look, here is a zipped version of the system folder:

https://www.dropbox.com/s/gcr9ahafqskkygy/system.zip