yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] TreeFiddyTacos:
Well damn, you hit the nail on the head. I changed it to the Metra OE radio and now everything works, except for my volume up button for some reason strange reason. I just assigned the up volume to another button however and now I have full functionality. Thanks for the help and explanation!

And someone else wanted pictures so i posted them below.

I have a powered usb hub connected to the radio's 12v accessory power. Going into that is a 500gb hard drive, and two extra usb ports. I picked up a part off of ebay that replaces my factory usb-aux inputs just below the radio, and the aux goes into the AUX IN in the radio. I also have a video input in the glove box in case I ever wanted to hook something up. It was a fairly easy install as all the radio wires were the same color, my only trouble was with the ASWC-1 controller.
[Android Head-Units] Zaphod-Beeblebrox:
I have the exact same failure. Volume Up isn't recognized. If you decide to try any of the others and have better luck, let me know :)
[Android Head-Units] usafle:
I posted my export of my tasker tether on/tether off a while ago for those of you having issues.
[Android Head-Units] kingamra:
Went back a few weeks... describes my issues with bt also... still having similiar? BTW how the new house?

Link to [MENTION=3159413]usafle[/MENTION] tasker post...

http://xdaforums.com/showthread.php?p=58355242

---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------

To touch on swc (pun intended)

Volume up/down work

Only thing that goofey whatever I assign to program key changes radio station input (fm, am etc) but still does the desired program (used to be bt answer/hangup toggle)
[Android Head-Units] blacklistedcard:
I was successful at compiling, but I can't find the update.img file. I did run the ./mkimage.sh ota and it was successful. I checked the folder rockdev folder, but there is no update.img file. Just the separate *.img files?

[root@asteriskserver nu3001]# ./mkimage.sh ota

TARGET_PRODUCT=rk3188

TARGET_HARDWARE=rk30board

system filesysystem is ext4

make ota images...

create boot.img with kernel... done.

create recovery.img with kernel... done.

create misc.img.... done.

create system.img... done.

[root@asteriskserver nu3001]# cd rockdev

[root@asteriskserver rockdev]# ls

Image-rk3188

[root@asteriskserver rockdev]# cd Image*

[root@asteriskserver Image-rk3188]# ls

boot.img misc.img pcba_small_misc.img pcba_whole_misc.img recovery.img system.img

[root@asteriskserver Image-rk3188]#

---------- Post added at 03:38 AM ---------- Previous post was at 03:07 AM ----------

Here is the list of *.img files after the complete compile:

[root@asteriskserver nu3001]# find -name "*.img"

./device/rockchip/rksdk/loader/misc_loadercmd.img

./out/target/product/rk3188/obj/PACKAGING/systemimage_intermediates/system.img

./out/target/product/rk3188/recovery.img

./out/target/product/rk3188/system.img

./out/target/product/rk3188/ramdisk-recovery.img

./out/target/product/rk3188/ramdisk.img

./out/target/product/rk3188/boot.img

./sdk/emulator/snapshot/snapshots.img

./rockdev/Image-rk3188/recovery.img

./rockdev/Image-rk3188/system.img

./rockdev/Image-rk3188/misc.img

./rockdev/Image-rk3188/boot.img

./rockdev/Image-rk3188/pcba_small_misc.img

./rockdev/Image-rk3188/pcba_whole_misc.img

./rkst/Image/myrootfs.img

./rkst/Image/recovery.img

./rkst/Image/misc_data.img

./rkst/Image/misc.img

./rkst/Image/pcba_small_misc.img

./rkst/Image/pcba_whole_misc.img

./rkst/Image/misc_factory_test.img

./kernel/drivers/staging/ft1000/ft1000-pcmcia/ft1000.img

./kernel/drivers/staging/ft1000/ft1000-usb/ft3000.img

./kernel/kernel.img

./RKTools/windows/固件工厂工具/bin/kernel.img

[root@asteriskserver nu3001]#
[Android Head-Units] usafle:
Yup still having issues with the random BT drops. Had one today actually. Went to dial a phone number in the HU and it told me that there was no BT device connected. Even though my phone stated it was connected. Only way to fix is to disconnect the BT and reconnect. Its still annoying. Lol

The house is good. Thanks for asking. Shopping for patio furniture now that its finally starting to thaw out here in NY. I've realized that patio furniture is STUPID expensive. And for what???? Plastic?!!?!!
[Android Head-Units] DaveSmith_1:
Thanks both of you. [MENTION=3159413]usafle[/MENTION] I tried your profile and it works exactly like what I currently have - it'll successfully start tethering, but won't stop it. I've been meaning to root this phone anyway, so I suppose I'll try next unless anyone else can offer a suggestion.

With regards to the BT random disconnects some of you have had, I've also had them. One thing I think that has helped me avoid that is to have phone AND music connect by BT. Even though I don't intend to stream media audio from my phone to my HU, keeping both profiles active seems to make for a more stable BT connection. The thing I would like to figure out (may require an overhaul of the BT/phone apps) is how to get the HU to properly connect after boot to a call already in progress. If I get into my car already on the phone, the HU will connect after boot but won't actually make the audio connection. In fact, my phone will recognize the BT connection and go into headset mode so I can't speak to or hear the call until I select "handset" from the call screen on my phone. Anyone else experienced this?

BTW, [MENTION=391948]Zaphod Beeblebrox[/MENTION], go ahead and add me on GitHub - "DaveSmith-1". Not sure how much time I can contribute, but I definitely want to help improve this software.
[Android Head-Units] zerosys:
Hm both if them are brand new. I bought them from amazon just for the unit. Is 12V enough power for the unit? If I set the power supply to under 12V the unit won't power on, maybe 12V is undervoltage?
[Android Head-Units] leonkernan:
I've been running my android box in the house using only the mini USB port connected to a 1500mA USB charger from an Android tablet.

Only other connection was a mini hdmi to hdmi cable to my TV and a USB mouse. The thing ran reliably for several hours playing music and installing apps, etc over wifi.

Are you running just the android box hooked up to a tv or the whole thing (screen and all) instead of in a car?
[Android Head-Units] zerosys:
I am running just the Android box connected to a TV.

I tried to connect only to a mini USB cable from TV's USB port earlier but I had the the red pixels and flickering also. So I thought USB power isn't enough and I bought the power supply unit.

Maybe I should take a foto and post it here during the day.
[Android Head-Units] leonkernan:
My instinct says either the HDMI cable or your Android box has a faulty HDMI connector.
[Android Head-Units] Zaphod-Beeblebrox:
Yea, looks like I forgot a piece of the rockdev repo and some instructions. I was focused on getting Android to compile, I forgot to test the image generation. Working on it now. You'll have to re-sync, but you won't need to re-compile, just redo the images.

Ok, I've added you.

in regards to adding or not adding people to the repo. Please understand that you don't need to be added to the repo to use the source, make improvements and submit pull (merge) requests). The only thing adding you to the org is gives you certain push rights. Those that were given those rights please be careful with them. Do not write to the master branch. create a test branch, etc.
[Android Head-Units] zerosys:
Hm do I have to change any setting or just plug in the power supply, plug in the Hdmi cable and that's it?
[Android Head-Units] Zaphod-Beeblebrox:
Repo & Readme updated. should generate you an update.img now. Thanks for catching that!
[Android Head-Units] leonkernan:
That's all I did.

Another thought I had: are you using a hdmi to mini-hdmi adapter? If you are and that's the issue, switching cables wouldn't help if that was the same part.
[Android Head-Units] zerosys:
No it's no adapter it is a one cable, mini Hdmi on one side and Hdmi on the other side.

The red dots and lines from the first two pictures appears by clicking buttons in dialogs. The blue dots on the third pictures are e.g in Google play store without interactions.

And after a couple of clicks with USB mouse the TV turns black for 1 to 3 seconds.
[Android Head-Units] leonkernan:
My tv blanked out at one point shortly after I got everything running, it turned out Android was switching the resolution to suit the TV.

Did it do it more than once during the same session?

As for the red dots, while there is a slim possibility it could be a firmware issue, last time I saw that on a device it was a faulty display connection.
[Android Head-Units] zerosys:
The blank out happens almost every third or fourth mouse click. In the Bluetooth application it happens every couple seconds without interactions.

Ehm maybe I have to update firmware? I received the unit and plugged it in, I didn't updated anything.
[Android Head-Units] leonkernan:
Worth a try, I haven't done that with mine yet. It only arrived yesterday and I took it for it's first drive today.

It's currently on MCU version 31 and system version 1.1.1
[Android Head-Units] zerosys:
Hm, update application gets forced close everytime i open it...
[Android Head-Units] leonkernan:
You need to do it in the car, with both the Android part and the Screen part connected and powered on.

Otherwise the program will fail because it can't talk to the MCU.
[Android Head-Units] zerosys:
Ah okay, i about to do that shortly. Thanks for your help dude!
[Android Head-Units] blacklistedcard:
Worked great! The whole compile process works without any errors/failures. I'm adding some I/O schedulers and Governors now. I also set the default i/o scheduler to noop and the governor to performance. Looking at the overclocking too.

Sad thing is..... I just cracked the glass on my NU3001. Touch does not work anymore. :crying: Summer you there?
[Android Head-Units] zerosys:
Okay, i updated the mcu but no changes. Then i played around with the resolutions, after a couple of "failures" i found a resolution on the Newsmy which shows everything correct. No red pixels and no blackscreen...

Finally i can use it on TV and install apps etc.
[Android Head-Units] blacklistedcard:
Installed the compiled update.img. it booted fine and I have started adding stuff. I did notice the language defaults to Chinese not English.
[Android Head-Units] briangig:
Have either of you attempted to update the firmware on your ASWC-1? Info here: http://axxessinterfaces.com/index.php?main_page=page&id=15
[Android Head-Units] leonkernan:
Just had a bit of a scary moment when I attempted an MCU update. a little while ago

I grabbed the v35 link from a page or two back and put it on an SD card, the update utility found it and started the update.

Then it got stuck at 3%... I left it fo 15 minutes and it didn't move.

At this point I didn't want to restart the unit as it may well not restart, so I disconnected the Android box and reconnected it to reset it and cancel the update. That allowed Android to reboot but I still risked a broken screen if it powered off and the MCU was corrupt.

I quickly grabbed the v34 update and wrote it to a different SD card and then used the update utility to flash it, this time it went properly and rebooted the whole unit successfully.

I'm not sure if there's an issue with the v35 update or if I used a bad card or something, but take care when you do your MCU updates!
[Android Head-Units] miket007:
Finally got mine installed today in my Cadillac.

I have a few questions and apologize if they might have been covered. I went through the carpad and was able to pair it with my s4 via blueooth, it only paired as an internet device and not as a phone. I am not sure why this is the case as I would want to use my phones hands free through my head unit. Any thoughts?

I wasn't able to locate a second bluetooth setting for connection to OBD devices. Is there a setting somewhere I missed?

Finally, whats the best way to update the cpu? I would preer not to sit in the car over wifi. Can it be connected to a windows PC?
[Android Head-Units] leonkernan:
To pair a phone for handsfree use you need to pair through the Bluetooth app itself, pairing in Android settings is for the second one.
[Android Head-Units] blacklistedcard:
It gets stuck sometimes. I have seen it happen with other firmware versions. I was good with v35.

---------- Post added at 04:29 AM ---------- Previous post was at 04:24 AM ----------

How do I do the pull request to git? I have added I/O schedulers and governors.
[Android Head-Units] blacklistedcard:
I got the exFat driver to compile. Testing it to see if it works good.

CC fs/exfat/exfat_api.o

CC fs/exfat/exfat_blkdev.o

CC fs/exfat/exfat_cache.o

CC fs/exfat/exfat_data.o

CC fs/exfat/exfat_bitmap.o

CC fs/exfat/exfat_nls.o

CC fs/exfat/exfat_oal.o

CC fs/exfat/exfat_upcase.o

LD fs/exfat/exfat.o

LD fs/exfat/built-in.o
[Android Head-Units] Beand1pped:
A little Help

Hey how are you? I apologize for bothering so much but needed some guidance. I found Tuatara's instructions but needed some help.

"Bring up the unit from STOCK first.

If you wish to only use the android box, connect up a 12V/1A centre-tip positive (or better) power supply to the unit.

Use a mini HDMI cable to connect to a monitor.

Use a keyboard/mouse wireless combo in the host port, and you're ready to test. just connecto usb on android box?

If you wish to use the head unit, connect a +12V/3A (or better) power supply - a PC ATX supply is perfect) to the red and yellow power wires.

Connect speakers (4Ohm are best) if you've got them.

Hook up the android box through the firewire cable.

Now you're ready as if it were in the car - touchscreen and all.

Once you've got the unit going, have a play.

Put the MCU update on the SDCard.

Select the MCU update.

Update to v34.

Now you're up to date.

Connect up the OTG USB (mini USB) to your PC, and install all drivers as per Wiki or in thread (rockchip for adb, recovery, etc.) how do i connect this to my pc?

Ensure you can connect to the device over adb. (i.e. adb shell). i dont know how to do this

Install RKBatchTool1.6

Click "switch" and make sure the android box restarts and you get a green box shown. (check drivers if not!)

Select your ROM image.

Flash the ROM by clicking RESTORE to update. It will reboot automatically.

Enjoy your new ROM.

Customization time:

Install FactoryTool 4.4, and modify the ROM to your liking.

Select Image. Click Switch, Restore, and flash your new ROM.

(lather, rinse, repeat the last two steps as much as needed)"

Any help would be appreciated
[Android Head-Units] Zaphod-Beeblebrox:
Yes, at this point this is PURE 1.0.9 source. Only the kernel had any changes. I'm pretty sure the stock ROMS all default to cn. It's an easy change. Look in /device/rockchip/rk3188 for system.prop ... edit to your liking (this becomes the build.prop). There is also a system.prop in /device/rockchip/rksdk. The latter one is generic to RK devices, then the rk3188 is overlaid on top. So settings in rk3188 will over-ride rksdk.

Now that I know that the stock build is working properly, we can start updating things like these build props, etc. I started on this yesterday but I've screwed up the java installation on my VM and I'm having trouble building myself now (I hate you ECLIPSE!! I was building fine until I tried to install that to work on code!) [/QUOTE]

Yea, I updated right before I did the physical install. Have checked a few times since, and no new updates. What hasn't been updated is my GMOS-04. It has a jtag port rather than micro-usb, and I'm too cheap to buy a cable ;)

I haven't done this in a while. In my former AOKP life, we used a gerrit instance, and we pushed all changes there to be reviewed/approved. I think the proper way to do this is to fork the repo (so you have a local repo), commit your local changes and push to your own repo. Then you should be able to submit a pull request from github. Since you are forked from our repo, the pull request comes in there.

I'm not a kernel guru, so I'll let the others review your changes before merging.

---------- Post added at 08:41 AM ---------- Previous post was at 08:38 AM ----------

I just pushed SystemUI & BonovoRadio from both 1.0.9 and 1.1.4 and all decompiled just fine with this site. Pushed the source over to my VM and did a quick diff. Going to be a pain the arse to go through, but it appears to have worked.
[Android Head-Units] Zaphod-Beeblebrox:
Well, after googling & googling, and trying to rip Java out of my VM and throw it down the road, I think I finally rid myself of eclipse, Open JDK 7 and re-installed Oracle-JDK 6. Build is processing. I have Android Studio installed for code editing. Now if I could just get back my Sat & Sun to work on some code :(
[Android Head-Units] Psy87:
Is anybody experiencing music stops when listening to audio from usb? (fat32)

Another issue for me is, that after short standby the usb stick is not mounted correctly. I have to unplug and plug in again.

Is there a way to use the android box with pc? I mean to simulate a window with the screen from the box?
[Android Head-Units] Invidiousdemise:
Can someone please quell my fears and tell me you would order this device again and again? I am tired of waiting on the Parrot RNB6
[Android Head-Units] blacklistedcard:
Your joking right? I went to that site and tried all the bonovo applications. The progress bar would just sit stuck at the *.jar part. I just need some time to get setup with my own branch.
[Android Head-Units] miket007:
Finished the install in my caddy. Nice and clean. Now on to updates and configuration.
[Android Head-Units] deeznutz1977:
I would, I'm actually thinking of getting the 8 (2gb ram) inch and putting the 7(1gb) in the Passat. :)
[Android Head-Units] Invidiousdemise:
WTF!???!! They seem to have more than doubled the price!
[Android Head-Units] renedis:
Have you read the wiki or this topic?
[Android Head-Units] Invidiousdemise:
I have read quite a lot despite how ignorant my post seems.
[Android Head-Units] nestortoledo:
Have any one get OK Google everywhere work on this unit?

With latest google search version it should work on any kitkat or lollipop

I have it working on note 3 with kit kat and with lollipop

But for some reazon, the menu options doesnt appear on nu3001

PD. I played a litle with DPI, and found that for car 213 dpi is one of the best.

160 all System UI looks so small. and with240 (stock one) is too big.

And with 213 all are more balanced, all bonovo app run fine no force close. only one look ugly is the radio one. rest looks nice (with 160dpi i get FC)
[Android Head-Units] renedis:
Price changes (up to double the price) are normal. Most of the time the price raises just before a big event so they can give you a 50% discount ;) its just a marketing technic.

But if you want to buy, please contact Summer.. She will always give you a good and fair price.
[Android Head-Units] briangig:
Shot in the dark (don't have my unit yet), do you have the google now launcher installed?

---------- Post added at 07:50 PM ---------- Previous post was at 07:47 PM ----------

Too bad. What vehicle are you installing in?
[Android Head-Units] leonkernan:
Try the trick listed here:

http://www.androidpolice.com/2014/07/03/still-dont-have-ok-google-everywhere-try-this-simple-trick/

Basically, you search for Google Now Everywhere in the Google search app and then the option appears for some reason.
[Android Head-Units] Zaphod-Beeblebrox:
2005 GMC Sierra Denali
[Android Head-Units] blacklistedcard:
Well the driver loads fine when booting. I did try a sdcard that as formated as exfat but it did not mount. I'm guessing that I need the exfat-utils to be installed. I also tried to not have the standard vfat driver compiled into the kernel. I thought they might conflict. I'm still hacking away to getting the exfat nofuse working.
[Android Head-Units] nestortoledo:
Nothing to do with google now launcher.

Im speaking about the OK Google EveryWhere, that allow to use OK Google on any screen or app, included aftermarket launchers .....

You can see the settings on this screenshot http://i.kinja-img.com/gawker-media...ogressive,q_80,w_636/ww4cewamon8y5gmomzx8.png

On mine nu3001 only first optiion appear

---------- Post added at 09:41 AM ---------- Previous post was at 09:41 AM ----------

Thanks but tired to test that and no lucky
[Android Head-Units] Beand1pped:
Rockchip Batch Help

Hello, I have updated MCU to Vers. 34, but can not install clockwork mod. When I plug Android box to PC it shows pink just like the WIKI says, but when I push switch to reboot into recovery it just turns off. I know its because I don't have clockword mod, but I don't know how to install this. I tried reading Tuataras Page on Google drive, but Rockbatch says Loading firmware failed. Any help would be appreciated

Thanks.
[Android Head-Units] jpapadami:
When the Android Box is plugged in and you get the pink window in Rockbatch tool, open up Device Manager, find the Android device, and update the USB drivers with the ones from this zip file. I had the same problem where I couldn't get to the green window in Batchtool, but this ended up fixing the issue.
[Android Head-Units] Beand1pped:
Thank you for trying

Thank you very much for the Help, but I just tried it and it is the same drivers I have installed now.

---------- Post added at 01:03 PM ---------- Previous post was at 12:52 PM ----------

I deleted the android device w/driver and plugged in usb again with new drivers and Worked! Turned Green! Thank you very much for your help.
[Android Head-Units] Psy87:
how can I simulate the 3 dot menu when I disabled the software buttons?
[Android Head-Units] jpapadami:
Install the Xposed Framework and then install the module GravityBox. There you can use Pie Control to simulate Back, Home, Menu, etc...
[Android Head-Units] zerosys:
Hm xposed on a car device, useful?

May i ask hat do you exactly use from xposed/gravitybox in the car?
[Android Head-Units] jpapadami:
I don't use it because I have one of my SWC keys mapped to the menu action. But I have heard that other people use it.
[Android Head-Units] nestortoledo:
OK manage to solve this.

Initialy the google search app was installed on system/app

just moved it to system/priv-app and after a reboot. now have the OK GOOGLE EVERYWHERE settings.

So i can use oK Google on any screen or app