yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Zaphod-Beeblebrox:
Track progress looks nice. and is something I will try to add later. My reading up on that so far has indicated it's buggy in pre-lollipop. Remember that we run this code as SysUI, and it has to be agnostic to music apps. IE, we can only query the information that MUSIC apps are supposed to report. Even then, we are at the mercy of the app to do it properly! Many do not. And the systems for doing this have changed over the years, so unless an App/Developer is active and stays current with android evolution, their app might continue to work just fine, but miss out on some of these features.

Anyway, I'm going to proceed on with the buttons I have and try to have something ready for release this evening. The navbar will be a bit unbalanced, but not that big of a deal. If someone comes up with a great idea for a replacement button, I'll implement it.
[Android Head-Units] nestortoledo:
Yes I mean for future updates not for now :)

Yes leave as is it. And we listen others users ideas. Once webget navbar in actual status working sure will occurs some ideas while use it
[Android Head-Units] renedis:
The volume does mute on the nu3001 when long pressed on the VOL- hardware button.
[Android Head-Units] gcgc77:
data communicate cable between box and hu

Hi there,

just wondering whether the data cable which connects the android box with the head unit could be extended?

By the way, which king of cable is it?

I need to fix the android box quite distant from the head unit (placed in a motorhome), therefore I need something like 5 meters cable.

Does anybody have an idea how to handle that?
[Android Head-Units] deeznutz1977:
FireWire I believe.
[Android Head-Units] DragonFlye:
Tried it............mmmmmmm. Look a bit out of date, can't quite put my finger on it, but it looks like it's from 2012. the interface is a bit too cluttered (in my opinion). Also, some features are not as intuitive as they should be.

For now, I'll keep using Car Dashdroid. The user interface is more mature/minimalistic. Though it can use some tweaks/enhancements, it is

very

usable and probably the best front-end at the moment.
[Android Head-Units] gcgc77:
thanks deeznutz1977.

Do you know if there are limitations on the cable length?

Will I find a cable like the one you posted with connectors to be soldered?

I need to pass the cable through a tight pipe and connectors will not fit. Therefore I need to set them after passing the cable through.

:eek:
[Android Head-Units] renedis:
Ive used a 10 meter cable with succes!
[Android Head-Units] danny6869:
Some help with final touches?

Hey folks! I have done my best to search and read through this huge thread, but there are a few things I am hoping to get answers on from some of you more experienced folks. First my back-story. I ordered and received TWO NU3001 units a few weeks back, and have since installed them in my vehicles. At first I was underwhelmed with the sound quality, and the usability of the unit, as I guess I was hoping for a better out-of-box experience. After installing tautura's rom, and setting up VIPER, the units sound MUCH BETTER, so I am much happier today than I was a week ago or so, however. This brings me to my questions/comments...

1. I seem to be having an issue of a "crackling" noise that comes and goes. I have tried swapping head units, and android boxes, and I seem to only have the problem with the one head unit/android box combination, but it's so infrequent, that I can't be certain of anything (it could even be my amp/speakers, as I seem to never be able to replicate it without that in the mix) It seems odd, and I am mentioning this, incase anyone has any brilliant ideas on what it might be, or how I could easily diagnose.

2. Does anyone else have the problem of the radio app (which is the worst part of this head unit so far), basically not relinquishing audio control back to android? In other words, when I play the radio app, and click the X to close it, I cannot hear my other android apps when I run them, or play through them, however, I see my visualizer on my homescreen behaving as if audio is playing. This only seems to be happening with one of my head units...which was working perfectly until a few days back when this weirdness started.

3. I assume everyone else out there also has the problem of the radio playing "mixed" with the android audio as well? (you have to close the radio app, or else you get both sources playing at the same time)

4. Does anyone out there know of any APP, or setup which would allow for a button press (like SOURCE on my steering wheel controls) to go to the next running APP? I would love to be able to cycle through running apps like that, I think it would be a very good use of the SOURCE button, and would mimic most other stereos' behaviours.

(what would it take to get XDA to setup a proper forum for us? this thread is getting unwieldy)
[Android Head-Units] leonkernan:
Grab the radio app from Post #3519 and give it a try, it fixes both these issues.
[Android Head-Units] kingamra:
China FM
[Android Head-Units] miket007:
Hi All,

I am hoping someone smarter than I can shed some wisdom....

I am using a 500GB USB drive with my unit and noticed that the OS does not see the proper available storage from this drive in settings/storage. It mounts fine and music apps can play from it. However, I use PLEX media server and I have been trying to sync files from my media server (over wifi) to the head unit. In the Plex app for Android (which is installed on my HU), you can set the storage location for sync'ed material. However in trying to set the location to the USB drive, Plex doesn't see the USB drive as an optional location. It also doesn't see the external SD card thats in my HU. I have this same app running on my S4 with a large SD card without issue. I would like to think this isn't a Plex issue but rather something in the OS.

Does anyone have any thoughts on this?
[Android Head-Units] MrG3kk0:
Hey you guys,

long time no read lol

Someone can quickly show me how to flash Tuatara Carpad II ROM?

Or let me know the Post Number?

Would be great, i need some changes again on that radio ;)

thank you guys :)
[Android Head-Units] gcgc77:
thanks renedis.

Could yuou please say if the firwire you used has 6 or 9 pin connectors?

cheers.
[Android Head-Units] alaninsitges:
It doesn't look like 2012, it looks like 2004. I had something that looked almost exactly the same in my car back in the bad old days of car PC and Centrafuse. It seems to be a copy of that. I agree that Dashdroid is much much better looking. Also I was surprised when I got a call on my phone (previously paired with the phone BT on the NU3001 for streaming music) and the Dashdroid UI popped up! It makes and answers calls with no problem at all and looks great doing it. No idea how/why but awesome.

Anyway in the next week or two there will be a new launcher/music control app available for our HUs that will make us quickly forget about fugly navbars and such.
[Android Head-Units] Zaphod-Beeblebrox:
??

elaborate.
[Android Head-Units] nestortoledo:
What launcher, can you give more info?
[Android Head-Units] Zaphod-Beeblebrox:
ROM Alpha Build

So here is a first test release of a full ROM. It's Alpha quality. While it should be good enough for daily use, there are some issues I know need to be worked out. Biggest among them is a lack of proper root. I suspect King Root will fix it, but I need to read up a bit on how to embed root in AOSP style builds. Also note that this is kind of a middle ground between 1.0.9 and 1.1.4. [MENTION=6488418]asidorowicz[/MENTION] has been doing great work bringing our source up to the 1.1.4 level, but he is not yet finished. As such, some of the little issues that were fixed by Newsmy releases, might have crept back in.

As for the adds, well obviously the new Radio with audio ducking. I've also expanded the functionality of the navbar, and added immersive mode for Navbar and status bar. All of these things 'function', but have little oddities. Try it out and keep detailed notes about what works/doesn't and under what circumstances, uses, etc. Getting logs is very helpful as well.

Also note, I have not yet embedded clockwork recovery. If you are on [MENTION=260727]Tuatara[/MENTION] ROM, you can/should back up your existing setup. Even without CWM on this ROM, you could always flash Tuatara ROM back, and then use CWM to recover.

This does pull some of Tuatara's mods (included repartitioning to 3gb /data). I don't know if this will run as update from SDcard (I do everything within RKBatch Tool), but if it does, I would expect it to wipe your data.

Lastly, While I want bug reports and help with testing these things, you have been warned that this is Alpha. It might crash, it might have bugs you can't stand. Don't flash it unless you are able/willing to report and are capable/willing to reflash back to something else and resetup your device.

Linky: https://drive.google.com/file/d/0B0MJcW3sI4ZPSlM4Z1BPdDRsbzA/view?usp=sharing
[Android Head-Units] nestortoledo:
Thanks for your hard work.

Any way to install the navbar in Tuatara's rom ??
[Android Head-Units] Zaphod-Beeblebrox:
You'd have to pull several pacakages, and I'm not sure how well they'd all react. I've done quite a bit of the testing within Tuatara's ROM, but as I put all the puzzle pieces together (especially working within the Settings framework), more packages became involved. I'm not sure if this would be a complete list:

/system/priv-app/SystemUI.apk

/system/priv-app/Settings.apk

/system/framework/android.policy.jar

You could try to copy/replace those out of my image, change permissions, and reboot. However, if it doesn't work, your system will be practically unusable at the UI level. So, make sure you can do this while connected to PC for adb access to revert if it goes bad :)
[Android Head-Units] nestortoledo:
OK, Let me first download your rom and will try it.

If works fine i will upload a update.zip, so others can flash it in recovery
[Android Head-Units] renedis:
6 pin connector!
[Android Head-Units] c5vette211:
USB Detection

I am having an issue with my device recognizing a USB device. From what I read the device is a RS232 output protocol. The device is a ELM327 USB adapter to run with Torque app.

When i connect the device it pops up with a message asking if i want to make this open with Torque as a default app.

I select yes and then nothing is being recognized beyond that. I tried downloading something specific to the device by plugging it into my PC and getting info. It is coming up on my PC as a comm port.

Device description: USB-Seial CH340

Manufacturer: wch.cn

Object name:\device\USBPDO-6

class long name: Ports(com&lpt)

class installer: MsPorts.dll.protsclassinstaller

I downloaded the wch.cn CH340 android driver and installed the apk on my device. when i connect my device it opens the app and it is a terminal. not sure what to do now. Not sure if its an android issue or a Torque app issue?
[Android Head-Units] briangig:
Check out the Wiki
[Android Head-Units] leonkernan:
Most of these devices use an FTDI USB to Serial chip that Android supports out of the box. Since yours doesn't it gets a little more difficult as you've found.

Now you've installed the driver, connect the device and close the terminal, then open Torque and see if it locates the device.

If it does, then you should just need to change the default application for that USB device. If not, that you might not have the right driver.
[Android Head-Units] jpapadami:
FYI, If you want to lower the voice guidance for iGO, Sygic, or any other navigation software, you can do this by lowering the Alarms volume under "Sound > Volumes". Just figured this out yesterday and decided to share if anyone is interested.
[Android Head-Units] briangig:
Is he talking about https://plus.google.com/communities/102908788212710276577 ?
[Android Head-Units] c5vette211:
Thanks. I did try closing the terminal and then trying to connect with torque. It still did not recognize the device. I will keep searching for a different driver i guess. :good:
[Android Head-Units] leonkernan:
Ok, I guess you downloaded this one: http://www.wch.cn/download/CH341SER_ANDROID_ZIP.html

I think that one is for application developers who want to build support for that chip into their applications (if I believe the Google translation)

People with other headunits seem to be hitting the same roadblock as you with that chip:

http://xdaforums.com/showpost.php?p=57526935&postcount=6127
[Android Head-Units] c5vette211:
Yes that is the driver i used. It was the only thing I could find. I will look at the other post on that. It sucks because I want to use the Torque app with USB for real time response to my head unit. The blue tooth is too laggy.
[Android Head-Units] nestortoledo:
That launcher looks very nice
[Android Head-Units] Bokomaru:
[MENTION=2190016]Zaphod-Beeblebrox[/MENTION]

Still waiting for my HU to show up but can't wait to try this out. I wonder if you would be better off starting a new thread for your ROM rather than having it all buried in here?
[Android Head-Units] alaninsitges:
He is.
[Android Head-Units] danny6869:
Hmmm...I tried it, but still have the issues. The only thing that fixes it is hitting the power button off then on, or telling the unit to restart (after closing the radio app).
[Android Head-Units] Zaphod-Beeblebrox:
The guy writing this clearly has great design skills. This looks to be very well designed and laid out. He's paid very close attention to material design guidelines.

However, at the end of the day, it will be limited by the access/focus that an app/launcher has. If you notice in the video, you have to leave the app to start/interact with the various music apps. What he's provided is a nice front end to multiple music apps. I see that he has buttons for other controls, but once you select them, you leave his app. You must come home/back to his app to see them again.

The beauty of 'fugly navbars' is that they are always there. I have much more control of the operations and visuals than you will ever get through an app. The funny part is the visual aspect of the button bar is exactly what I want to turn the NavBar into! I suck at the graphics part of this, but we'll get the functionality working first, then some of the others in this forum can help spruce up the visuals.

For example, I spend most of my time with the Nav screen up. His pretty visuals will be nowhere to be seen during this. But the Navbar will be.

Still way to alpha to worry about that. I think we'll be fine discussing it in here for a while.
[Android Head-Units] nestortoledo:
OK tried and get it partial wotking.

I get the navbar correctly. but when try to open settings / user interface i get force close. (there should be one missing file)

So i cant enable the media play buttons, also notices there so many lost/waste space on both sides.

On my side, i will do icons less bold (thin style) or more android auto style

attached a screenshot
[Android Head-Units] Zaphod-Beeblebrox:
You are running 213 DPI aren't you? It's going to make everything smaller. I'm still working at 160DPI. We might can provide different [MENTION=1245493]Dimens[/MENTION] for the different densities once we get everything working.

I can't remember what other packages get affected by these changes, so you'll probably need to pull framework.jar/framework2.jar/settings.jar
[Android Head-Units] nestortoledo:
OK will try it tomorrow.

Here navbar with thinner buttons more like android auto, still not finished it,
[Android Head-Units] briangig:
Did you have to do anything special to get the mic recognized? I tried a Logitech HD 9000 and a (i think) a Logitech C120, and they didn't work as mics. Cameras worked fine in DailyRoads.
[Android Head-Units] TomatoOne:
Nope, it just worked. I was surprised and relieved in the same time as I was afraid I'd have to go buy a newer Logitech camera. The microphone hooked up right away, "OK Google" from the launcher screen worked immediately. The camera needed a reboot to be recognized.
[Android Head-Units] briangig:
Weird. It seems people have had good luck getting Android (including people in this thread) to use the mic on the Logitech C270. Just grabbed one off eBay for cheap and we shall see.
[Android Head-Units] Summer-Newsmy:
when you order LCD screen?
[Android Head-Units] spoks:
I do :D
[Android Head-Units] Zaphod-Beeblebrox:
Looks like a new MCU (v.95???) and a 1.1.5 release just dropped. I'm going to try and pull them down, but I have terrible luck with biadu.

If someone gets them downloaded, please repost.

http://pan.baidu.com/share/home?uk=1596625300#category/type=0
[Android Head-Units] deeznutz1977:
1.1.5 is 283 MB. Almost 25%..Edit, link https://www.dropbox.com/s/1gzhv3akb...I-P_KK4.4.2_1.1.5_1024x600_update.tar.gz?dl=0

MCU V_95. https://www.dropbox.com/s/dbf019cy04s3bel/CarPAD-II-P_mcu_v95 (20150326 V9001测试程序).rar?dl=0
[Android Head-Units] Zaphod-Beeblebrox:
There was no changelog on the MCU. Hope there is one on the ROM.

I hate chasing this stuff.
[Android Head-Units] leonkernan:
I take it you've seen these Newsmy forums?

http://www.newsmy-car.com/bbs/forum.php

I'm going though there slowly using Google Chrome to auto translate, but I haven't seen anything about this latest version yet.
[Android Head-Units] Zaphod-Beeblebrox:
that 283MB is compressed. Once deflated, it's about 10MB larger than 1.1.4 (463,165 KB)

I've done the same. Never found anything of interest, but very difficult to manage & navigate through google translate :) Maybe now we know how Summer feels.
[Android Head-Units] leonkernan:
Nothing too interesting when I pulled the text strings out of the MCU update.

Once difference seems to be support for one or more new hardware models

Hardware Version: VA8001_V3

Hardware Version: VA8001_V31

Hardware Version: VA9001_V1

These strings weren't in the MCU v35 at all.
[Android Head-Units] usafle:
Should we wait for you to let us know when it's out of BETA or should we all jump on the G+ community and get in on it now? What do you suggest?
[Android Head-Units] deeznutz1977:
I jumped . I don't even think its released (even in beta) yet.
[Android Head-Units] walio:
Upgraded MCU to the latest. Not worth it. HU and android box both stay connected when removing the key from ignition and opening the door...

Going back to the older version
[Android Head-Units] ElfinJNoty:
Hi guys...

Long time xda'er and had plans to put a tablet in my dash, then did some research and came across the NU3001. I am a forum admin at a site called AllThingsStreaming, we are all about free TV and movies so do a lot of stuff with Kodi Media Center and different set top boxes. So I loved the idea of this android box being removable and can bring into the house ?

I ordered the 2gb NU3001 and am looking forward to its arrival in a few days, as well as joining you folks in maximizing the devices capabilities. Hope to get some help from you guys as well as contribute what I can

---------- Post added at 09:01 AM ---------- Previous post was at 08:57 AM ----------

BTW I purchased mine from a 3rd party seller on AliExpress for $380 shipped(to USA) and think it is coming with a free reverse camera.

My first question is.... Are there any videos or screen shots available of these custom builds I've seen being mentioned(taratura? Or amplified?)

Also would like to know the best place for a guide to using the rockchip software to update. And as far as I can see, I don't see people referring to xposed modules. Are you guys using xposed successfully with the device?

I only ask because I see a lot of efforts going into modifying the nav bar and I know there are a few xposed modules which if nothing else could reveal some helpful code, which already allow you to modify icons and button targets.

I'm also wondering if someone can refer me to a good 12v (how many amps?????) plug for the box when using it out of the vehicle. I saw mention of "old Nokia charger" somewhere, but hope to learn a bit more before plugging in random old plugs I have stashed to try and power and box. I've had some unfortunate experiences doing that in the past :)

Thanks in advance
[Android Head-Units] dwa87:
Just curious... why do we need a 12V power supply at all? I plugged the Android box (OTG port) into my computer and it's working quite well. I even flashed the new ROM using only the OTG power. I use the additional USB port for keyboard/mouse.
[Android Head-Units] alaninsitges:
Just to be clear I wasn't talking about your navbar in particular being fugly. I don't like anything down there wasting screen space.

I think he's got a solution for nav and some of the other apps needing focus (in the demo video he's basically scraping lockscreen controls) but the long-term purpose of the app is to enable AA-enabled apps to run on a local machine and not require a tethered phone.
[Android Head-Units] gazdaaa:
Canbus support

Hi, my plan is to install this head unit in Audi A3 2011 year (8P), it has 2 din radio, so it will fit, but my question is, has someone tried to install this unit in any audi car newer than 2008, and with what success with Canbus connections.

In a nutshell:

Does and which versions of HU support canbus

Does it support parking sensors

Thanks for help.
[Android Head-Units] Zaphod-Beeblebrox:
I didn't think you were talking about *MY* navbar :) Although it does need some graphic design love.

But what exactly do you call that button bar at the bottom of his app? Essentially, he's going Immersive mode (to hide the Android Navbar), and then put an even larger bar of shortcuts. His approach is good for applying to multiple devices that may or may not have source code. But, why deal with the limitations that come with being an 'App' rather than 'THE SYSTEM!' when we have source code.

It's a notable goal to try and do AA style apps locally, but it'll be a tough sell without source (and we don't have Android Auto source that I'm aware of).

Don't get me wrong, I think the app is cool, and very beautiful. I've joined the beta community as well. I'd like to put this thing through its paces and see what it can do. If nothing else, it'll give me great ideas for how to extend our navbar.

I saw some discussion of people asking him about open sourcing his code, and while he didn't say no, I didn't get all warm and fuzzy about that prospect either.

About 1.1.5:

I loaded it up and did very quick setup so I could drive for a while today. The biggest change I saw was that they have fully switched to 160dpi. I still think its a bad idea. While they increased the size of the navbar a bit to compensate, and set the font size to HUGE, many aspects of that setup are just way to small to comfortably interact with. I think the sweet spot between maximizing screen resolution and visual size will end up being somewhere between 200 and 220.

[MENTION=6488418]asidorowicz[/MENTION] did a quick scan through the image and has identified some resource changes, but not a lot of new code. I think the resource changes are to deal with the 160dpi change. The only new functionality I saw was in the MCU update app. It now has a function to set the 'standby time' (wasn't this in one of the test build releases?). Asidorowicz also noted new JNI code for the MCU app, so I suspect this function actually works now.

I'll be flashing back to my test build and some Navbar code I'm working on soon. Nothing I really like about 1.1.5

And just FYI, I'll be travelling a lot the next week or two, so development will likely pause for a bit.
[Android Head-Units] briangig:
Has anyone had luck with any US compatable T-Mobile USB 3g/4g dongles?