yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] jkchr1s:
Hey everyone, I just started researching this head unit after using a Klyde RK3066 unit and being totally dissatisfied with sound quality. I've read through several pages of this forum and had a few questions I didn't see answers to...

1. My Klyde unit's sound quality flat out sucks. It seems to be missing a very wide range of audio (almost no low-end/bass, weak mids, and very strong highs) while using Android apps (Spotify/etc) and very muddy sounding FM. I finally got fed up with it and put my stock stereo back in, but I really miss having Spotify/Google Music right on my head unit. I spoke with Sindy and she was very helpful, but I was wondering if anyone that previously had a HuiFei/Klyde unit can verify that the sound quality in this unit is better? And from what I understand, most people use Viper or something similar with this one... it just worries me that even with the Klyde, running Viper it didn't fill the "missing gap." Does the audio sound "full" with these units?

2. One thing I loved about my Klyde was the CABUS plug and play adapter that just worked OOB with steering controls. They initially shipped the wrong one and I bought a PAC adapter for my Wrangler. It's the RP4-CH11 - http://www.pac-audio.com/productDetails.aspx?ProductId=1116 - This worked great for sound, but the steering controls wouldn't work because my harness only had the KEY2 wire (not a KEY1 for some reason) since it was "plug and play." I have it installed in a 2014 Jeep Wrangler with high speed canbus. Has anyone used this PAC adapter for SWC? Do you just cut the headphone jack plug and solder to WHEEL KEY 1 and WHEEL KEY 2?

3. I saw on here someone with a Wrangler sold their unit because it didn't fit. Any others with a Jeep/Dodge/Chrysler have problems using a universal double DIN adapter?

4. For those of you who had satellite radio in the past and miss the playlists, I have a working app (that still needs UI love, but does work) that scrapes songs played on your favorite stations, de-dupes them, and throws them in a Spotify playlist. It's a work in progress, but you can install the app, add a channel, point it to a playlist, and hit sync. Still work to be done, but the meat of it is built. I consider this release "alpha 2" but it does work. See attached zip for apk :) Edit: Source here - https://github.com/jkchr1s/spotirius-android

Thanks for the help!

Update: New build of Spotirius. Rewrote most of the backend logic so it's more efficient.
[Android Head-Units] zanix:
Yep, the wiki does state that root is broken this way. I have no idea if you can update su via recovery or not.

I don't remember if the stock recovery has a GUI, you probably want to flash CWM or TWRP first.

If you want a proper pre-rooted ROM with a bunch of neat features I would suggest just flashing to xdAuto
[Android Head-Units] Bokomaru:
The stock recovery is very basic, you cant really do much with it. Like [MENTION=1802543]zanix[/MENTION] says, CWM or TWRP is the way to go
[Android Head-Units] larsomen:
and now the waiting begins

I just ordered the NU3001 2gb from summer.

I have to say, i haven't encountered service like this anywhere else.

Summer is very kind and helpfull, she even put 3 extra VW (fakra FM adapter, Quadlock adapter) cables in the order for free that I even couldn't really find myself!

Does someone have some tips for me for when i receive my HU?

Like what to install etc. (xdauto)
[Android Head-Units] Zaphod-Beeblebrox:
I think we are confusing buttons here. Navigation (the arrows) is for Maps/Waze, etc. It launches a 'URI:geo' intent. The Automotive (speedometer) button launches the CAR_MODE intent.

As to why ALDLDroid responds to the NavButton after running requires a little understanding of intents & filters. And this is obviously an intuitive guess on my part, since I have no access/knowledge of their code.

Intent Filters can (and should) be defined in the AndroidManifest.xml file of your app. Many other things get defined here (permissions, some service startups, etc). But this is basically how you tell Android to interact with your program.

Intent Filters can also be Registered and Removed at run time. Bonovo uses this method quite frequently to register listeners once a service starts up. There are some use cases where you might want to listen for specific intents ONLY if your app/service is already running (putting filters in the manifest means your app will be launched for those intents even if your app or service isn't running).

It's quite possible that this app is registering a URI:geo listener once you navigate somewhere, but doesn't include one in the manifest. But I'm more interested in what happens with the Automotive button (speedometer).

I'm finishing up some code to allow the user to turn on/off each of those custom buttons. I have a few small bugs to chase out of the code, then will push that to git hub. Once that is done, I'm going to turn my attention back to these intent filters.

---------- Post added at 05:57 AM ---------- Previous post was at 05:47 AM ----------

A little help with USB OBD please.

I bought one of these:

http://www.amazon.com/gp/product/B005ZWM0R4/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

ScanTool OBDlink SX USB. I bought a small powered USB 2.0 Hub, and a 12V to 5V converter to power the HUB off of ignition wires. I have both the OBDlink and my C270 webcam plugged in, but I've never gotten the OBDlink to work (Tried Torque, and scantool's app). I've also tried connect the OBDLink directly to the Android box.

Now, I've not spent much time on this, so I've not done any linux command line/terminal snooping of the USB bus yet. Just curious if I've missed some obvious steps to make USB OBD work.
[Android Head-Units] -=Jeff=-:
Sorry I meant the speedo button on the lower nav bar
[Android Head-Units] madmax1404:
Automatic Tethering

I use the free app 'Trigger' on my phone to enable the Hotspot once the blutooth connection with the Car is established. Works perfect.
[Android Head-Units] Psy87:
I own this OBD adapter as well. Using it with torque pro and dashcommand. I found out, that I had to set a specific protocol and rate I think. Will have a look later. For testing I used the Obd link app. There I found out the corresponding parameters.
[Android Head-Units] JeepAndroid:
Waiting for answers on this. I have the nu3001 and just received my pac-swi and c2r-chy4 but being a noob haven't figured out how to connect it all
[Android Head-Units] -=Jeff=-:
Yes I had the terminology wrong. The program uses the Automotive button on the Navbar, but only after I have launched the program using the actual Icon, what does not happen is on a fresh boot, if I press the automotive button, nothing happens. If I go to the app drawer launch ALDLDroid, then navigate to another app, then press the automotive button, it will then launch the ALDLDroid app.

So my question was mainly around, how does the Automotive button and the Intents work on a fresh boot? I really wish I had the time to invest in learning how to do some of this stuff, I just don't right now.

I had the same problem with my OBD cable, I had to use one of the USB Host apps to 'fix' the Android install as it does not seem to have the host mode active or working initially. I will try my USB cable again to see if it works.

I was running into an issue with trying to have a USB cable connected and an Arduino connected (2 FTDI devices), android does not seem very flexible with that, I have gotten it to work but could never get it to work all the time, always needed some tinkering
[Android Head-Units] larsomen:
hey guys just a quick question.

how do i change the boot logo with the following rom: xdAuto-1.1.6b2-working

i can't load the boot.img in the firmware factory tool.

it gives the following error: unpack firmware fail

kind regards,

Lars Kaptein
[Android Head-Units] danny6869:
Has anyone successfully bought a second android box? I am trying to get in touch with Summer to do so, but have been unable to do so.

I really want to try the cutting edge stuff, but not be without music in my car if something is not good when I am trying this stuff out.
[Android Head-Units] Zaphod-Beeblebrox:
Yes, I have two complete NU5002's and an additional Android box.
[Android Head-Units] larsomen:
nobody knows this?

i've just looked around in the zip file and found a bootanimation.zip file wich contains the bootanimation pictures but that wont be of any use.

Can someone help me?
[Android Head-Units] Zaphod-Beeblebrox:
Just because no one answered in less than 6 hours doesn't mean we don't know. Patience grasshopper.

You can't use the factory tool on an update.zip The .zip files are for use with TRWP or CWM. Easier method of updating.

Rockchip works on .img files (and use 1.1.6b3 by the way, b2 has issues with partitions). Try with 1.1.6b3.img and see where you get. Although, I seem to recall others having issues with Factory Firmware tool and some custom Roms .. not sure.

---------- Post added at 08:14 PM ---------- Previous post was at 07:47 PM ----------

Just pushed a few new commits to github for those building:

1) Temp fix to the make otapackage problem. [MENTION=4173803]Bokomaru[/MENTION] found the change he had made to get his working. He feels we need a better long term solution, but I've committed it for now so we can all build .zips

2) User selectable NavBar Buttons. For those that like/don't like some of the buttons, you can now turn on/off whichever ones you want. I also brought back the stock V-UP/V-Down buttons for those that don't like my 'slider' button. Note that there is no range checking here. Put too many buttons on the bar, and they WILL slide off the screen. I think you can comfortably put 8. 9 is probably pushing things to the edges. 10 will surely make one disappear.

Note that both of the stock Volume buttons now 'MUTE' on long press as well.
[Android Head-Units] janla:
I was close to purchase second box.

Not succeed yet, because above question is still unanswered (important to me).
[Android Head-Units] blacklistedcard:
I rebuild tonight and test out the recovery zip file.

How do I build a zip file recovery for just the kernel file? Google was not my friend on that one. Everything I found is very vague.

---------- Post added at 03:26 AM ---------- Previous post was at 03:22 AM ----------

I don't think Summer will come out and say if they are or not.

The same box that was a rk3288 would be nice. With AC network connectivity
[Android Head-Units] Bokomaru:
There isn't a command to just build an update.zip for only kernel like there is for a full image. You'll need to basically build the zip yourself. There is a base that someone put together that most people use here https://github.com/koush/AnyKernel
[Android Head-Units] blacklistedcard:
Thanks. I try it.
[Android Head-Units] ElfinJNoty:
I didn't get a chance to flash your build of b3 last night... Crazy girlfriend problem

Now you say you will build again... And I am hoping you are willing to share again. I need linaro in my life ;)
[Android Head-Units] Bokomaru:
Other than some wild speculation that there could be something coming out, I have not seen any evidence that suggests an updated hardware version is coming out anytime soon.

Even if a new version came out, the existing box would be far from obsolete. The android box has enough power to do whatever anyone could want and more. Are people trying to mine bitcoins while they are driving?
[Android Head-Units] supremekizzle:
Thank you. So I'm taking it as not needing to fully root to flash a ROM such as xdauto? Just update as you would stock firmware just substituting in the custom ROM? thanks
[Android Head-Units] Bokomaru:
That is correct, you can just flash using the rkbatchtool a new rom. The bootloader is not locked on this device at all.
[Android Head-Units] supremekizzle:
Well well well.... That certainly simplifies things.
[Android Head-Units] blacklistedcard:
Got my new OBDII Connector with GM Lan or SW CAN Support
[Android Head-Units] leonkernan:
Works great here, thanks guys. That's going to make life a lot easier if i don't have to keep reinstalling apps all the time.

I kept the old layout but swapped the clock to the circle home button. Looks really nice.
[Android Head-Units] nestortoledo:
Very good now.

Can you make the navbar to look big when use it on 213dpi ??

Also if you want i can upload this new icons. (more Android auto style) including also volume+ and volume - icons for stock volume

Thanks in advance
[Android Head-Units] Zaphod-Beeblebrox:
Navbar height is set in framework-res.apk. Look in core/res/res/values/dimens.xml I think it's currently set to 100dp. Decompile, change, recompile, push :)

As for icons, yes we would love for you to get involved and push some new graphics. It would be great if you were able to set up a mini dev environment (it doesn't take a new/dedicated machine - If you have decent desktop power available to you, you can set up a VM). I'd love to see you get involved in changing the colors/backgrounds/graphics etc to a more AA look.

---------- Post added at 06:33 AM ---------- Previous post was at 06:30 AM ----------

Need detailed status report. And what vehicle? I'm interested in the GM Lan part (I have 2005 Sierra Denali). I still haven't had much time to work on my USB OBDLink SX, but I'd consider dropping the money on the MX if it works better.
[Android Head-Units] jkchr1s:
Well I ordered my 7" last night, can't wait to get this thing in! I love that you can pull the android box in the house to tinker around with, should be much easier than the huifei units. :) Thanks all of you for the details on the site and a clear and detailed wiki!
[Android Head-Units] kingamra:
[MENTION=2190016]Zaphod-Beeblebrox[/MENTION]

I should have went with the 7 inch for install in my celica... I had to trim the center dash bezel but unfortunately toyota did not make it easy... it's a multi compartment piece with supports built In between compartments on the backside of the bezel.. I had to hack into those and couldn't get the install kit (metra) to work at all... it's functional... just not as pretty as the hummer install... I do have 2 more cars to try to make it better... hahaha

Put on b3 last night.. looking forward to my morning test drive...

Thanks for all the development work everyone !
[Android Head-Units] blacklistedcard:
I can confirm that the make otapackage works now. I rebuilt my rom/kernel and flash it fine. All my applications and settings were intact afterwards.

Here is the Linaro 4.9.3 flashable rom/kernel with overclocking @ 1.8ghz.. I just sync'd up with GIT and rebuilt it. It has the working phone contacts with the stock people application.

https://www.dropbox.com/s/62nd0rn8wu975p0/rk3188-ota-eng.root.zip?dl=0

---------- Post added at 01:38 PM ---------- Previous post was at 01:31 PM ----------

Have a 2003 Impala with the OBDLink MX bluetooth. It's a nice unit. I was getting about 32 average pids/sec, which is higher than the basic elm32 v1.2 that I had. The GM extended PIDS worked fine. Some of them did not work for my car like abs. Still testing out just how many GM extended PIDS are working with my Impala.

I actually like OBDLink Android application better than Torque Pro. You can even update the firmware on the dongle by the OBDLink Android application, which is nice.
[Android Head-Units] -=Jeff=-:
SWEET.. let me know what it supports.. then I can possibly plan to ditch the OEM radio in my Daily Driver for another NU3001
[Android Head-Units] [Bob]:
This is priceless :D

[YOUTUBE]TIepdLO9Dm0[/YOUTUBE]
[Android Head-Units] Zaphod-Beeblebrox:
My Head hurts

Ok, so I've spent most of the evening working on these intent filter based buttons. I was so proud that I had found a pretty elegant way to do this without having to build custom listviews, static lists of package names, etc. However, with the 'elegance' and the fact that Android does not 'enforce' any of their guidelines, I'm left with little hope of making this a complete solution without resorting to hackery. see this:

05-27 21:01:51.707: D/StatusBar.ExtensibleIntentButton(602): starting PreLoad
05-27 21:01:51.707: D/StatusBar.ExtensibleIntentButton(602): Starting getRunningTask
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): Resolve Count:1
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): Task Count:2
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): TI:com.teslacoilsw.launcher
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): RIorg.prowl.torque
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): TI:com.example.radio
05-27 21:01:51.717: D/StatusBar.ExtensibleIntentButton(602): RIorg.prowl.torque
05-27 21:01:51.827: D/dalvikvm(995): GC_FOR_ALLOC freed 510K, 17% free 3246K/3876K, paused 10ms, total 10ms
05-27 21:01:52.097: D/dalvikvm(995): GC_FOR_ALLOC freed 502K, 16% free 3256K/3876K, paused 10ms, total 10ms
05-27 21:01:52.217: I/ActivityManager(473): START u0 {act=android.intent.action.CHOOSER flg=0x10000000 cmp=android/com.android.internal.app.ChooserActivity (has extras)} from pid 602
05-27 21:01:52.257: W/IntentResolver(473): resolveIntent failed: found match, but none with CATEGORY_DEFAULT
05-27 21:01:52.277: W/IntentResolver(473): resolveIntent failed: found match, but none with CATEGORY_DEFAULT

These are some debugging lines I put into the code to see how my package matching logic was working. Basically, the system gets a list of packages that match the intent (Resolve Count / RI), along with the current active tasks (Task Count/TI). It does this to relaunch an active task even if it isn't the 'default'. But the takeaway here is that toque is catching the intent filter I use.

But look at the last two lines. The ActivityChooser requires that the app define not only the CATEGORY_CAR_MODE, but also the CATEGORY_DEFAULT filter. This is something that has to be done at the App level.

So, My only other 'solution' is to make mini-apps/helpers for apps that we might want to use. IE, I could make an small app that does nothing but launch Torque (or Poweramp), but I can define the AndroidManifest the way I need it to. Kind of a crappy way to do it, but I might have to.
[Android Head-Units] ElfinJNoty:
Xposed modules ? Would be awesome
[Android Head-Units] vip-25:
Hi guys,

I need music player app stock rom

because I installed xdAuto rom, but nothing this app
[Android Head-Units] Zaphod-Beeblebrox:
Temp Fix for PowerAmp & Torque

So, based on my above analysis/post, I decided to write two little quick apps to launch PowerAmp & Torque. I was then able to structure the manifest the way I wanted to, so they respond properly to my intents. While it's not my favorite approach, it allows me to handle these special cases without cluttering up the ROM code.

I've pushed the apps to the xdAuto repository: http://xfer.aokp.co/?developer=zaphod&folder=nu3001

Install each APP as necessary. I'll clean up the Text/Icons later (I copied the structure from SwitcheCE so it has a Windows Icon!! :) I will push the source code to our github when I get a chance, so that other helpers can be easily generated for apps people might want.

Note that I will *NOT* have these built and included in xdAuto. If you want/need them, you should install them separately. If we forced them into the ROM, it would create problems for people who don't have/use these specific apps.

---------- Post added at 07:45 AM ---------- Previous post was at 07:43 AM ----------

We don't like the bonovo Music app. We removed it from xdAuto. We are including Apollo instead. Apollo is an open source music player with much more functionality than the stock music player. If you MUST have the stock player, then you could extract it from one of the stock ROMs (or even Tuatara's)
[Android Head-Units] Psy87:
Apollo does not recognize any music from my USB Stick, everything is empty
[Android Head-Units] JeepAndroid:
Help Wiring

Hi folks

I've tried reading the wiki, but cant figure this out.

The unit comes with three sets of wires, I think I have figured out where the wheel key and AUX IN etc go

but what about the two adapters one with reverse v.com and the antenna and the other with illumi, reverse etc. There is Power/speaker socket (A) but that can only take one, and then the other?

Cheers
[Android Head-Units] Zaphod-Beeblebrox:
Are you on b2 or b3? b2 has partition mounting issues. might not have anything to do with the music app.
[Android Head-Units] Psy87:
I'm on b3. Just recognized this, but its not an issue for me since I'm using PowerAmp.
[Android Head-Units] larsomen:
i've tried b3 yesterday, sadly gives the same error.

also tried rk3xxx firmware tool, but that one also doesn't work.

Has someone succeeded in changing the boot logo of xdauto?

Or any suggestions on what to try next?
[Android Head-Units] Bokomaru:
Spent way too many hours figuring this out, but I finally figured out what was causing xdAuto to not work if flashed directly from the factory rom via rkBatchTool.

Changes are in github, maybe we can bundle a new release tomorrow.
[Android Head-Units] Zaphod-Beeblebrox:
It's likely that our kernel img is packed somewhat differently than the stock images (not sure - I don't mess with much at that level, I'm a UI/Button guy :)) if you absolutely must change the boot logo, you could always pull the source code from our github, change the logo there and compile your own special version.

---------- Post added at 02:57 PM ---------- Previous post was at 02:53 PM ----------

BTW, I posted a b4-alpha set of images on the repo this morning. This was prior to [MENTION=4173803]Bokomaru[/MENTION] 's fix, so you might want to wait for his final b4, but if you are already on xdAuto, or tuatara, you should be able to flash the alpha just fine.

http://xfer.aokp.co/?developer=zaphod&folder=nu3001

I'm also anxious to hear from those few of you who have downloaded my helper apps. What other heavily used apps need some intent firing love (I think a lot of you are using iGo... does it handle the map intent properly?) - if not, all I need is the full package name of the app (I think you can get it from settings/apps)
[Android Head-Units] -=Jeff=-:
I downloaded the PowerAmp App.. might get to it tonight.. we will see
[Android Head-Units] Bokomaru:
I've never used the firmware factory tool, it only runs on windows. I believe you have to load the update.img with it though, and not just the boot.img
[Android Head-Units] larsomen:
sadly xdauto doesn't come in update.img version :(

so that won't be an option
[Android Head-Units] Bokomaru:
Really? I'm pretty certain every version Zaphod or myself has uploaded has had an img as well as a zip.
[Android Head-Units] larsomen:
yeah i know what you mean, but i've already tried the following:

xdAuto-1.1.6b2.img

xdAuto-1.1.6b3.img

they don't seem to be recognised as update.img files, like zaphod said, the file structure/architecture may be different?
[Android Head-Units] Bokomaru:
The img files are generated by the rockchip tools, so it should be in the proper format. Maybe it's something as simple as renaming them update.img for the tool to recognize it.

Next time I fire up a virtual windows environment I can try the tool out and see what happens. Is there a specific error message it gives?
[Android Head-Units] larsomen:
i just tried renaming it to update.img

just like with the normal name it displays unpack ok.

but then it gives a message wich says "kernel path no exist!"
[Android Head-Units] DragonFlye:
Nice video easyguy!

But you got to mind de WAF. My wife is gonna ask questions if the unit starts with an desktop full of icons, not knowing which is which. It needs some kind of easy going launcher or overlay to quickly choose between music playing, radio, navigate etc.

This guy made some interesting overlay @ youtube.com/watch?v=v6bQxkjOaDI
[Android Head-Units] usafle:
A car stereo install shop.

I am trying to update this thing with Red's custom ROM. I cant figure it out. How are you guys flashing this?

I've got the rockchip batch tool installed and the adb drivers installed and windows 7 detects the device.

But the Rockchip Batch tool shows no connected device.