yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] red13dotnet:
Yeah, my interest here is in providing a stable base platform, with the underlying functionality to do what we need. KISS is the name of the game. Customizing the UI beyond a usability enhancement point is really a subjective thing. I'm gonna work on giving people the foundation for whatever they choose to do. and yeah, still all primary work will be KK, sorry guys. I've been looking further into it and it will still be a royal pain to get L working for us. And that's just running at all, not with full functionality. I know everyone wants the newest baddest thing, believe me I'm right there with you but I also want it to work and work well.
[Android Head-Units] Dream Reality Syndrome:
My sentiments exactly. Function over form
[Android Head-Units] Stormbringer!:
One more vote for going slow with this device and using KK. I haven't even installed mine as I'm waiting for all the kinks to get ironed out (that and its !%!#^%^ cold out where I'm at)...

Let Newsmy do the development for L and we can refine it when the time comes.
[Android Head-Units] alaninsitges:
Timely http://android-developers.blogspot.com.es/2014/11/begin-developing-with-android-auto.html
[Android Head-Units] easyguy:
I found this for tabletUI, but it doesn't work too well. anyone can get this to work?

http://xdaforums.com/xposed/modules/xposed-tabletkat-1-0-1-true-tablet-ui-t2862722
[Android Head-Units] Skybet:
Split Screen anyone?

Hi there, I carefully read all the 80 pages but still I haven't found an answer to my main question: has anyone successfully managed to do spit screen on this unit?

I guess 99% of time I would leave a 2/3 map and 1/3 gmusic with albumart displayed....

Would'nt it be cool?

And what about resistive Wheel commands, it seems they are supported, anyone knows exact procedure to have them working?
[Android Head-Units] easyguy:
Tried a few apps/xposeds did not work too well for split screen, I wanted the same with waze and music app, but did not work well at all. heard L have built in split screen so waiting for that update, unfortunately.
[Android Head-Units] usafle:
Had it installed and working on my Nexus10. Then realized for whatever reason it absolutely crushed my FPS on any app I was using. Perhaps due to the screen re-draw? Promptly removed it.

--------------------------

We need a link on the OP to the Wiki page.
[Android Head-Units] nestortoledo:
I just thinking about the navbar.

As we have right know phisical buttons for home, back and power

In navbar, i vote for something like android auto .

Navigation icon ---- Phone Dial icon ---- Multitasking ---- Music icon ---- Radio icon

Navbar should be always visible and bigger similar to android auto http://www.android.com/new/images/auto/slide-1.jpg

This way main APP we use while drive are always avaiable in easy way

If we finaly get AOKP navbar settigns, we can doo this,if not will be nice to have something like this navbar
[Android Head-Units] easyguy:
Cannot find a navbar where it suits my needs. Thinking about getting into rom editing and making my own navbar. All I need is a "next" button and I cannot find that anywhere.
[Android Head-Units] Zaphod-Beeblebrox:
The more I think about it, the more I think bringing AOKP to this device would jump start a lot of the features. Plenty of things like Ribbons, Custom Navbar, extended screen mode, etc. Hover for notifications.

The only thing we lack is a true Tablet mode. That's the one piece of code I'm most interested in working on. And as limited as my time has been of late, I'm much more inclined to work on one new system, than trying to port over a bunch of crap I did a year ago.
[Android Head-Units] NU5002S:
Just bought a NU5002S from Summer. Hope to get a tracking number a week from now.

I like a really big screen. Can we start a topic for the NU5002S ? Where is a link to a wiki closest related to it that I can read up on?
[Android Head-Units] wacko37:
Me too. ... stock due to be in a week. Can't wait.

The nu3001 is the closest to this device apart from the larger screen extra 1gb ram. But this is yet to be confirmed.

Zaphod-Beeblebrox will be the first member to recieve this unit which should be very soon, you can rest assure he will fill us all in on the difference etc
[Android Head-Units] spoks:
Do you have any idea why bluetooth connection works, let's say randomized - sometimes it connects fine, sometimes not? Sometimes the phone shows "connected" and it is possible to receive calls on HU, but no to make calls from HU - HU shows that bluetooth state is not connected.

I have had no such problems with other original HU, for example, VW RNS510 system (no Android :) )
[Android Head-Units] Bokomaru:
The xdAuto builds are based on the source we have, the lastest which is 1.1.6.

---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------

You are the first person I've heard of using CWM on a Carpad3. To me it looks like it is complaining about installing an older version of software over a newer version. So presumably you had a stock version installed, added CWM, then are trying to flash an older zip file on it.
[Android Head-Units] dedosoa:
in fact as i was complitely out of ideas, i am in that moment updating to an oficial chinese download, i oder to try to apply the xdAuto update. after that. At this moment the chinese has been updated succesfully.

Thanks for the advice.

Ok i am actually on a v1.3.1 are you sugesting to downgrade to 1.1.5 (wich is the less oficial chinese closer to 1.1.6) in order to update?

The thing is when i have upgraded from 1.2.7 to 1.3.1 it has prompted with update.img on the external_sd plugged. It didn't when i applied update.img from xdauto1.1.6. so what i did is copy the update.zip wich it worked on trying to update but ended on the image from the previous post and showing the recovery.

At this moment update.img from the 1.1.6c is not working, neither on external or internal trying to update from stock v1.3.1

Any idea?

Sorry about that guys i really apreciate your help...
[Android Head-Units] Bokomaru:
You've gotten yourself in a bit of a pickle. The only recovery that will be able to handle the .img files is the stock recovery, CWM or TWRP have no support for them (and I don't have the time or motivation to add it to TWRP).

Your options are limited:

If you have a computer and a USB male to male cable you can use the rkbatchtool to flash an image over. Though I think most people won't have a male to male cable.

Create a zip image from the xdAuto repo (or wait till a new versions comes out, maybe today or tomorrow)

Grab the recovery.img from some image and use dd to manually overwrite the existing recovery.
[Android Head-Units] petros3:
Another link for faster downloading? for 1.3.3 Stock Rom.

thanks.
[Android Head-Units] leonkernan:
To be honest, it's because of bugs in the Bluetooth app.

The way connections are made is a bit fragile at times and is something i'm still to address properly.

edit: To expand on this a bit.

The current setup relies on the Bluetooth module automatically reconnecting to the last device it was connected to. The idea being you do your first connection from the phone and from then on the auto reconnect feature keeps you connected to the same each time.

One problem with this is when you pair a different device to the headunit. I'm testing this out now, but it seems to get confused if there have been multiple devices paired with the unit.

The plan is to add proper pairing and device management to the Bluetooth app next.

Then there will be a list of paired devices and the software will be able to manually handle the connections rather than rely on the auto connection feature of the bluetooth adapter.

I showed the start of this previously but it didn't get completed and was lost.

Adding it back properly is something I plan to work on soon.
[Android Head-Units] Zaphod-Beeblebrox:
I don't think that image was CWM. I think that's the stock recovery? In which case, you need a full .img file, not a .zip
[Android Head-Units] spoks:
I see. But in general problem is that last device (in my case it is mostly same phone all the time, no other devices are in use) is not connected or is not recognized as connected.

Unfortunately Newsmy do nothing to resolve this bug and our only help is your investigations and changes :good:
[Android Head-Units] ElfinJNoty:
Has anyone attempted to install Google Cast Receiver? It doesn't show as compatible in the app store.... But would be fantastic if we could get it to work. Think I am going to attempt to sideload it this morning. I expect it will not work, but wish me luck!
[Android Head-Units] ElfinJNoty:
Also wanted to share the following thread for those of you who like black and/or clear themed apps. I use the Clear(stock) PlayStore, Black Google App, Black YouTube, Black Push bullet, Clear Play Music.

Black or clear Google App + Google Now launcher(and xposed GNL Settings) gives you a great user interface for home screen and app drawer!

TeamBlackOut.... Been theming on XDA for as long as I can remember.... They have an app to download all the goodies in their thread. Highly recommended. #whiteuimustdie :)

http://xdaforums.com/showthread.php?t=2283828
[Android Head-Units] Bokomaru:
Is that stock recovery? I've never seen a menu on it.
[Android Head-Units] ElfinJNoty:
Us being on an older api(KitKat) rather than LP.... Makes this a lot more difficult than I first imagined.

I think I've found a couple cast-receiving options.... But I'd mostly like it in my car for passengers to use if they wanted to play something. I attempted a few different older versions of the official google cast receiver app with no success. I could get it to install and run fine, no fc. However, because I'm using a wifi-tether network, my phone doesn't think it is on a WiFi network, so any casting app(the one that sends) requires WiFi to be activated. I know there is an xposed module that can spoof a device into thinking it is on WiFi rather than data.... But I didn't go that far to attempt.

The methods I was able to find that supposedly work(I was unable to confirm) require an xposed module for a workaround since GooglePlayServices version 6.5. And since I don't expect any of my passengers to have an xposed framework on their devices.... Ultimately I am giving up on trying to get this working right now.

There were a few apps that are available for purchase, but I wasn't confident in them working because of the non WiFi connection issue I mentioned(when trying to send from my phone), as well as development of the apps being pretty sparse. Couldn't locate one that had a release within the last 6 months. And google has been all about the security of late, and know they are constantly pushing updates to prevent exactly what I'm attempting to accomplish(they want you to buy the dang Chromecasts lol)

If anybody else is interested in this as well, or has any pointers or suggestions(or references, and or has gotten their CarPad to work as a receiver?) Please feel free to pm me or share results(only if successful) here in the thread.

Elfin Out ;)
[Android Head-Units] dedosoa:
Thanks to all!

Finally i took a Windows laptop, Had a male to male usb cable and installed xdauto via Rkbachtool.

Thanks to all the people that made this thing possible.
[Android Head-Units] Bokomaru:
xdAuto 1.1.6d released

New version of xdAuto released. Download links at the new thread: http://xdaforums.com/android-auto/android-head-units/xdauto-rom-newsmy-carpad-t3266694

1.1.6d: December 8 2015
Add OTA-Updater software to make updates easier
Disable rkupdateservice
Update usb_modeswitch to 2.2.6
Add 3 ITU Regions to Radio. (Allows US AM stations to be properly spaced)
Fix bug with Radio not adding favorites in certain cases
Update usb_modeswitch and switch to building from source
Add Bluetooth AVRCP support (playing track info and play position)
Bluetooth phone will now show the caller name provided by the connected phone
Bluetooth audio can now be controlled by SWC without opening the Bluetooth audio app first
Fix for volume popup breaking immersive mode in apps such as Automate beta
[Android Head-Units] Totoix:
Is the new version compiled from this repository:

https://github.com/Nu3001/

?
[Android Head-Units] Bokomaru:
Of course
[Android Head-Units] Totoix:
One last question. Whic MCU is suggested with this version?
[Android Head-Units] Bokomaru:
Whatever works best for you. If you are using one of the newer Carpad3 devices you will need to use a newer version since they mostly just add hardware support. I'm still using v41 on my Carpad2 device.
[Android Head-Units] spoks:
I flashed new release with RKBatch tool, because had stock 1.3.2 Rom on board (with 1Gb partition).

Now I do not get further than dancing bubles after xdAuto logo, no matter how long I am waiting to.

Should it be so? :eek:
[Android Head-Units] Zaphod-Beeblebrox:
Please move that discussion to the new thread.
[Android Head-Units] spoks:
Have I missed something? Do we have a new structure in NU3001 thread? :confused:

wow. ok.ok. I found it :)
[Android Head-Units] Zaphod-Beeblebrox:
Did you even read the post that you quoted?
[Android Head-Units] [Bob]:
Hey guys,

It looks like I've got a bit behind things. Last time I logged in, this thread had 200 pages, now it's 800. Tried to search a bit to find an answer for my questions, did not, so if someone would be so kind to take two minutes:

1. I'm on Tuatara ROM 1.1.4 ... Can I just flash xdAuto 1.1.6d with rkbatchtool without issues ?

2. Is the new NR3001 worth the upgrade ? My main issue right now is with the BT call quality which is horrible compared to the stock HU. Has anything improved in this department ?

Thank you !
[Android Head-Units] ElfinJNoty:
A lot of things could be affecting your Bluetooth call quality(BT power from your phone, the microphone you are using, just to list two)

But xdAuto has some tweaking to the BT handling, not sure about call quality but I know the interface and incoming calls has been improved over Tuatara's now outdated build.

If you already have tuatara's ROM it is suggested to flash the twrp recover, then you can install xdAuto right on top. But the batchtool will also work.

Worth the upgrade? Think we've got a few people following the thread with the new NR model, I'll defer to their input if they think its worth.
[Android Head-Units] kamhunt:
Hi. When a region is in the Radio ( e.g. СHN ) After reboot is reset to EUR . Not remembered my choice! Who faced such problem ?
[Android Head-Units] e.sjolund:
Is there by any chance that you could create a partition file for the NR´s? Would be great to have 20GB for internal storage.

Anyone know if there are the any future plans for creating a ROM whit a bigger internal storage partition, for the NR´s?
[Android Head-Units] Bokomaru:
I'm working on coming up with a good solution that will hopefully let users select their own size, but if I don't have time for that I'll just have a flashable zip that selects the size. The problem is that the stock recovery only flashes the parameter file in a few very specific cases.
[Android Head-Units] blacklistedcard:
I try to duplicate tonight. Should not be doing that. Did you try setting it and redo a scan. Then close the radio application?
[Android Head-Units] kamhunt:
I will do as you said. I've transferred all my old settings and the Radio ceased to remember the region.
[Android Head-Units] h0tw1r3:
Guess what came today?

NR5002!!! Will do an unboxing video and first boot tomorrow.
[Android Head-Units] Bonsario:
Dear Bokomaru,

that would be awesome! I really need to increase my data partition to 3 or 4 GB (only have 1 atm), but if I would do it with RKBatchtool it would wipe my whole data.

Could you please make a .zip first for TWRP? Would be great!

Also I have one question, my time is always wrong. Using automatic time and time zone also dont work...dont no what to do.
[Android Head-Units] Zaphod-Beeblebrox:
It's unlikely that any solution will be able to resize that partition without wiping the data. Your best bet is to just backup your apps, do the resize in RKBatchtool and set it up again.
[Android Head-Units] robertusIT:
I want to gift me this christmas a radio for my car and i think that NR3001 is better than NU3001 because:

1 - Microphone in the mic works with Ok Google, without any issue right? ( for me vocal command when you driving is better to have more safe )

2 -NR have more storage to NU so is better, no? if i buy NU i need to put a big pen drive in usb ( only one i see )

3 - I don't understand it:

4 - In CarPad II: Android hardware is separate and is connected to the head unit via a FireWire cable

5 - In CarPad III: Android hardware is integrated into the head unit

What means?

6 - And also i see that CarPad II, have sd slot, but i all pictures i didn't see any slot. NR doesn't have it.

7 - I don't understand this "android box" for NU unit. ( that needed to buy a part, 100$)

8 - If i need to update my rom or change with a custom rom, i see that in NR, needed to put all files in Internal SD Card, but in NU you need to use "Android box?" so without you can't?

Isn't clear in wiki page how to. My problem is update and to do that, i break down from my car this radio and connect it to my pc.

9 - I want if is possible, buy this radio, and before to put it in my car, i update or change with xdauto or automate( in my huouse, but i don't know how to turn on without auto power cable) and when radio is in my car, i update only via ota or with little .zip in recovery.

Thanks for the patience
[Android Head-Units] ElfinJNoty:
I can only speak on the NU3001 model(ghats which I own)

The "head init" installed in your car and is the display and hardware. This is a double-din size unit and where your wiring harness connect the device to the car(power, radio, GPS antenna connection, rear view camera connection, steering wheel controls, etc.)

The "android box" acts as the brains for the device... And is a separate device which connects to the head unit via a FireWire cable(allows for exchange of power and video signal). The two must be used together. My android box lives in my glove box with the FireWire cable run through the back of the glove box and into the dash, connecting to the head unit. With the NU3001, and the other NU models, the android box is removable. Can be brought inside and connected to an HDTV via a mini-HDMI. With a wireless mouse/keyboard, can be used as a full set-top-box for home use. In the home, power can be supplied to the android box via a male mini USB connection plugged into a computer or a wall plug(USB, same as for charging your phone) the mini USB input on the android box serves as an USB-OTG input. So works for powering the device, but also as a connection to mount an external storage device, or a computer connection(this is how you can flash stock and custom firmware/Roms to the device)

The android box can then be brought back out to your vehicle and connected to the double-din head unit portion(FireWire) and goes back to being like a small PC connecting to it's touch screen monitor.

There is in fact a micro SD card slot.... I have a 64gb inserted in my device. It shows up on the device as externalSD. The android box's internal storage shows as internalSD. If connecting a USB flash drive, that displays as USBstorage1.

I have a Logitech c270 USB camera/microphone mounted on my dash facing forward(for use as a dash can) but my mount has a swivel so I can turn it around and have it face me for a hangouts video call or photo. The wire from the camera is hidden in the dash, run behind the "head unit" and around into the back of my glovebox, for plugging into the full size USB slot in the android box. Camera works well with the built in camera app, and most other 3rd party photo apps. The microphone detects "OK Google" 90% of the time. I use the mic for voice control, google searches, and voice typing.

There is also the microphone that comes with the unit, which does not receive enough power for use with "okay google" detection. It is also hard wired to the "head unit"'s own separate Bluetooth module.... Which is used exclusively for calls while connected to your phone via Bluetooth(shows as a BTHFD(Bluetooth hands free device). This allows for calls and music streaming directly to the " head unit". The head unit can not pass this audio through to the android box. But it is not needed to, works as expected. The "android box" has its own Bluetooth receiver for everything else you would use BT for.
[Android Head-Units] Zaphod-Beeblebrox:
As for box/headunit. See these photos:

Box is hidden in glove box, etc. and connects to HU via firewire cable

http://imgur.com/a/ipQTQ
[Android Head-Units] ElfinJNoty:
Yeah.... What Zaphod said :)
[Android Head-Units] mureren71:
Flash troubles RK Batch Tool

Hi

Just received my new NR5261 unit today :)

Got it powered up on my desk, with an old switch adapter (9-14VDC out, 2.0A out), and all seems ok.

Also hooked it up to my pc, where i have downloaded numerous versions of MCU files, xdauto ROMS, Driver assistant, Rockchip Batch Tool,Rockchip Factory Tool etc.

I have also successfully upgraded the unit from stock version 1.3.0 to 1.3.1, without problems.

But.....Rockchip Batch Tool version 1.6 and 1.8 will load NONE of the downloaded xdauto .img files (1.1.6c, 1.1.6c2, 1.1.6d) (.img file is renamed to update.img, config file changed to SUPPORTLOWUSB=TRUE, driver assistant was successfull, stock version can be flashed!)

What the he.. could be wrong here?

Am i missing something obvious? :(

EDIT: I was......missing something obvious!

Downloaded the real .img. file (+500MB), instead of unpacking the .zip files and trying to use the .img file from that (around 9MB) :-|
[Android Head-Units] robertusIT:
in first, thanks for reply, for all informations and for the patience.

so, if i buy NU3001 and not NR ( that doesn't have android box ), i need also android box, because without i can't change rom with a custom rom like xdauto, right?

and also i can't use any usb port and any sd card, right? are only in android box.

and this andorid box work together head unit when is connected, but when is unplugged, is a mini pc android, right?

NU head unit without android box have the same features, but not sd slot, can't change rom and no usb port, right?

Thanks again, i need it to choose between NU or NR, also because if i buy NU and android box is necessary because without i can't have sd card slot, usb port and no storage like 64gb extra to music and no chance to change rom, i consider the price of NU + android box ( 100$ more less)

I see NU that now have 2GB RAM, first version have only 1GB.
[Android Head-Units] ElfinJNoty:
The latest NU models have 2gb ram.

All NU models come with the necessary android box. It is included with your purchase. The advantage is being able to bring the box inside and use as a set-top-box(mini android PC). It does have an SD card slot and a full size USB slot, and a mini USB slot for USB-OTG connection. The usb-OTG slot is used to connect the android box to a PC. This connection provides enough power for the device. I have also powered on the android box with a FireWire cable connected to my PC. The android box is capable of outputting to the head unit touch screen AND mini HDMI output simultaneously.

For the NR model, I cannot speak on... Have not looked at it. But from the sounds of it, people are able to connect a PC/laptop to it and flash xdAuto. So there must be some type of USB input. From what I have read, does not have an SD card slot though. However, the internal storage on the NR =32 GB (NU = 8gb internal storage)

I personally prefer the NU model. Taking the android box or "brains" of the device inside when wanting to use on my 55inch television is convenient. Also much easier to upgrade/modify software from inside the house versus with a laptop inside the car.

Only drawback is that without the android box connected to the head unit via FireWire..... You will have no functionality on the display in the car. Head unit needs its "brains" to operate.