yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Rvnheart:
I didn't mean to cut off capacitive buttons, just the silver frame around them.

Thanks for the quick reply. I'll go ahead and start asking the dimensions of that HU to make sure if it'll fit.
[Android Head-Units] zanix:
Keep us up to date as well, I'm sure there are a few of us that are curious if you succeed in modifying this.
[Android Head-Units] sterod:
Sorry if this has been answered already but can xdAuto 1.1.6c2 be loaded onto the new NR3001 units?
[Android Head-Units] zanix:
xdAuto should be able to run on the NR series, the stock ROM is exactly the same for both NU and NR series. I recall someone already trying it and working. Can I get a confirmation from someone that has loaded xdAuto on a NR?
[Android Head-Units] shomesomesho:
Yes, I'm running 1.1.6c2 on my NR.
[Android Head-Units] leonkernan:
Edit: Ignore me, i'm getting the MCU and Android updates confused...
[Android Head-Units] zanix:
MCU is also the same.
[Android Head-Units] leonkernan:
I know, for some reason I was thinking the driver changes were made to Android rather than to the MCU.

In which case they wouldn't have been applied to xdauto. Since they were done on the MCU it doesn't matter.

So, just ignore me :-p
[Android Head-Units] zanix:
I wonder if we should just create an apk from the GitHub until we get a new xdAuto build.

Maybe I'll look into that since I've been meaning to get an environment set up to work on Android apps.
[Android Head-Units] Bokomaru:
I could kick out a version of the apk easily, but it would be great to have more people working with the code. I'm really hoping to have some time over the holidays to push out a new version.
[Android Head-Units] Zaphod-Beeblebrox:
I would be very interested in the actual dimensions of the 10.1" units. Looking at the size of the bezels (not just the plastic trim, but the amount of bezels dedicated to the capacitive buttons), I'm wondering if the actual screen size is really 10.1". I've been thinking about putting a 10.1 in the expedition (won't fit into the GMC truck).

Yea, I was hoping to find a little time to play with the radio app myself this weekend, but i'm not holding my breath.
[Android Head-Units] Rvnheart:
I asked the dimensions from Summer and I'll inform you as soon as I get the reply.
[Android Head-Units] supremekizzle:
Hello, current owner of Nu5001 with a couple of questions. First, is the NR series worth upgrading to? What is different about it in terms of pros. Second, is there a way to hook the android box up to my TV to customize the head unit? It's around 20 degrees Fahrenheit in Minnesota so I'd rather not do it outside. Do I need a mouse for it? Thank you!
[Android Head-Units] Dream Reality Syndrome:
http://xdaforums.com/wiki/index.php...ggle_view_desktop#CarPad_II.2FIII_Differences

http://xdaforums.com/wiki/Newsmy_CarPad/FAQ under the section "What ports does it have?"

I'm pretty sure you will need a mouse if you're not connecting the box to a computer
[Android Head-Units] Totoix:
Edited:

Is there a way to change transition animation between two windows(or app interfaces)? Currently, active interface gets smaller and goes to behind of the new interface which is getting bigger and coming from behind. I want the android switch between them without any animation. Is it possible?
[Android Head-Units] Zaphod-Beeblebrox:
Look under developer options and the transition/animation options. I do not think you can change the animation style (that was something we added in AOKP back in the day - might be possible to port some of that code). However, you should be able to change the scale/duration to such that it largely doesn't appear.
[Android Head-Units] IdleCuriosity:
Brake action

In the wiki there is a photo of the old wiring harness that had all 20 pins present and 20 labelled wires.

My NU3001 arrived with two harnesses (one for Nissan, one ISO) and in both cases three of the 20 pins are missing. By elimination, I am missing CAN-L, CAN-H and BRAKE. Missing CAN-L and CAN-H is OK for a universal head unit, since it wouldn't know how to interpret that information (pity it can't be redirected into Torque).

What effect does the BRAKE input have on the head unit? Does it prevent video from playing unless the vehicle is parked?
[Android Head-Units] Zaphod-Beeblebrox:
That is the general purpose of a brake input. To restrict Video & Navigation operations. However, I don't think any of that functionality is included anywhere in the software. It would be nearly impossible to restrict apps in that way, so maybe that's why the removed the wire.
[Android Head-Units] MrTSolar:
I believe those wires are on a separate harness (mine has two harnesses, ISO for power and speakers, and an AV harness which has some other wires on it).

Question for anyone with the stock ROM. Is there a way to turn down the volume of the bluetooth phone connection? I was driving yesterday with the music on and volume about half. My phone rang and it nearly deafened me.
[Android Head-Units] h0tw1r3:
My NR3001 came in last week. Kicking myself because I assumed the 5.1 (pre-amp) harness came with the unit. Wish I would have found this page/wiki before ordering. I'm going back and forth with Summer on getting one sent...

Hooked up to the bench and did a couple quick videos. Please excuse the quality.

Unboxing:

[youtube]y48oF_Nw8VQ[/youtube]

First boot:

[youtube]IbOEYeUVD8Y[/youtube]

Embedded videos not working on Firefox for me, click the heading links.
[Android Head-Units] zanix:
The FAQ page really needs some work.

This maybe? No idea if it will work.

XuiMod for xPosed: http://repo.xposed.info/module/com.zst.xposed.xuimod
[Android Head-Units] ElfinJNoty:
[MENTION=2190016]Zaphod-Beeblebrox[/MENTION]

Why did work on an aokp build stop? What were the issues you were facing when attempting? Are there other devices that use our head units chipset that could be cross referenced? Specifically a phone or tablet rather than an android box?

I'm interested because I'm thinking of asking some of my peeps to help in building a cm based ROM.
[Android Head-Units] robertusIT:
deleted
[Android Head-Units] Zaphod-Beeblebrox:
I ran into a lot of driver/hardware issues that I wasn't able to overcome. someone like [MENTION=4173803]Bokomaru[/MENTION] could probably fix them, but at the time, I didn't want to mess with it any longer.

Quite honestly, I came to the conclusion that the way I use the device, AOKP only had a few items that would be handy. Most notably was the NavBar. Many of the other features we had in AOKP I just didn't see as being useful here. And if you know anything about developers, you know that unless we find it particularly appealing, we probably aren't going to spend time on it (that's why you need many people working/contributing to a ROM - so varied perspectives and interests get represented).

I finally came to the conclusion that I could do a more appropriate navbar for xdAuto than trying to port AOKP, so that's what I did. My original attempts are still hosted on my personal github (not the NU3001 one), so if anyone wants to tackle it, feel free.

But again, Think about what it is in CM (or AOKP) that you want to see in a ROM for this unit. If it's a few isolated features, you may be better off trying to port those few things rather than porting the whole ROM.
[Android Head-Units] zanix:
I added your videos to the links section on the wiki, thanks for making them!

I think we can also blame xPosed since it has made it possible to get some of those extra features from custom ROMs added in.
[Android Head-Units] torzo:
[/COLOR]

And where is that google drive ? :)
[Android Head-Units] Zeeksi:
ive run into an issue where my headunit wont turn on, anyone know what to do? All that happened was someone pressed the radio app just as the headunit turned off and now the whole thing wont start. I've tried letting it rest for 3-4 hours unplugged, i've tried reflashing the rom. What else can I do?
[Android Head-Units] e.sjolund:
Why don´t you? Would be great with diversity. Although as mention, it´s probably easier to import source into the exciting rom, but I would encourage you to try a CM based rom! I´m currently trying myself to learn (early stage) and understand how android manifest etc. work, so I can import/make features that I like into xdAuto. One day I´ll reach my goal and manage to make and import features. Hoping to create/ copy the navbar of Slimcat(so you can add your own features/ user defined soft buttons). But Im in an early stage of learning, so it will probably take some time.
[Android Head-Units] shomesomesho:
Is there a way to increase screen brightness or is that a hardware limitation?
[Android Head-Units] Bokomaru:
I personally think building something not based on stock is going to be a major effort with little reward. There are device specific changes spread all over the place through the code base so it wouldn't be as "easy" as porting CM to a new phone.

---------- Post added at 11:01 AM ---------- Previous post was at 10:55 AM ----------

That is interesting, are you able to connect to the Android box with USB (and ADB) while the Android box is connected to the head unit?

I'd be curious to see if the Android box is receiving data from the head unit over the serial channel.

I suspect this is something that would be solved by reflashing the MCU code, but that is pretty hard to do without being able to use the display.
[Android Head-Units] Tuatara:
A link to the google drive, with the (now old) CWM/ROM files is in my signature, even on the post you referenced. :)

Here it is anyways: https://drive.google.com/folderview?id=0B4LT40YiEbW6fmlKNng0bFpjU1FKRVBnR21JZzFrUHA5dWFxVjAzU3RybkF6cUVXd3FpYnM&usp=sharing

However, you may want to instead look at a newer stock/modified ROM (mine was based on 1.1.4), or look at xdAuto (my recommendation) which is continually being refined and improved by the XDA community here.
[Android Head-Units] leonkernan:
A while back the SSD in my development pc died (note to self, think twice about buying OCZ again) and I lost a bunch of in progress code.

Anyway, the last week or so i've started rebuilding it and the first patch is just about ready to go into github.

This one adds Bluetooth track info support and also a remotecontrolclient so the track info appears on the status bar if you have that option turned on.

It got some testing in my car driving to work this morning and is finally working properly. Assuming no big bugs on the drive home it will be getting committed to the xdAuto github when I get home tonight.
[Android Head-Units] kwalsh24:
Awesome to see development still happening for xdauto!
[Android Head-Units] Bokomaru:
I've been there before, lost lots of code/time when something died. Now I keep everything in source control, even if I am the only one working on it. For public projects like this, create a branch to work on it in and commit there. Commit frequently even if it breaks the code base (it's in a separate branch so who cares).

We've had enough changes go in, I think sometime soon we will roll out another release. Especially after this goes in.

Cheers!
[Android Head-Units] kwalsh24:
Will the next release of xdauto be based off of any of the new stock Roms ?
[Android Head-Units] Bokomaru:
Nope, we haven't had another source leak. Though I am working with them to hopefully gain access.
[Android Head-Units] kwalsh24:
Cool sounds good. So far I'm still getting shafted with this replacement board. I now have to tear my car back apart. Reinstall this board that they sent me. Send them photos of the board connected to the ribbon cable (apparently it takes a genius to do this in their world) and send photos of the black screen that happens.

At the amount I've spent on this unit getting it working again... I would of been better off get a while new unit.
[Android Head-Units] Zeeksi:
I'll try connecting via adb later on today, but I think it'd have a decent chance of working due to it connecting and working just fine during the flashing phase.

What would I be doing in that case? I haven't really done anything in adb before.
[Android Head-Units] IdleCuriosity:
If you connect the Android box to both the MCU and (via HDMI) to a display, does that allow you to see what you are doing to flash the MCU?

(Sorry I can't test that myself since I don't have a mini-HDMI cable.)
[Android Head-Units] Bokomaru:
I believe it should, but it's not something I've tested. Just gotta drag a tv/monitor out to the car :)

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

I'd pull off a logcat and also run 'adb shell dmesg' and capture the output. Attach them here (or somewhere else and link to it) and I can take a look and see if anything looks obvious.

This could take some work to figure out, might have to rig up something to allow you to flash the MCU from the command line (which wouldn't be a bad thing to have anyways)
[Android Head-Units] jkchr1s:
If anyone is interested in the NU 7" here in the US, I traded in my Jeep and got a new car it won't fit in any longer. It's the 2GB RAM version CarPad II. PM me if interested.
[Android Head-Units] blacklistedcard:
Off topic.. Did you like your jeep? Thinking of getting the wrangler Rubicon 2016.

---------- Post added at 05:33 AM ---------- Previous post was at 05:28 AM ----------

I'm still hacking away on the exfat file system support. Tried the exfat nofuse driver, load perfectly fine but vold was not coded to mount/reformat etc. Missing the exfat utils. Them I tried to rip the exfat fuse driver code from CM. It almost there.
[Android Head-Units] spoks:
HU wont turn on

I have had similar issues. They happened if I switched off car shortly after HU started, and then after some 10sec turned ON again. HU stayed black, no response.... nothing.

First couple of times there was enough to disconnect Android box fireware cable for some 10 sec. After firewire reconnect everything was fine.

Last time it didn't work. HU was like dead. At same time Android box was booting up and working normally (tested with hdmi output to monitor).

Then I took HU out of car. After reconnecting of all wires couple of times, HU came to life.

Needless to say I didn't find any loose connection or visible bad wire. So, I do not know what was the reason and when it will happen again.
[Android Head-Units] zanix:
Sorry about your HD. Looks great!
[Android Head-Units] torzo:
Yeah found it thx ;)

Im gonna install your recovery.

Install xdAuto 1.1.6c and then update to 1.1.6c2
[Android Head-Units] leonkernan:
Ok, i've pushed the Bluetooth audio changes over to the xdAuto git tree.

Hopefully it works ok for everyone.

I've put one extra fix in where the music would still play though even if it was turned off.

Please let me know how it works for you.
[Android Head-Units] Rvnheart:
I got a reply from Summer but they didn't tell me the actual dimensions. Just asked me to send a picture of my car so they could tell me if the unit will fit (as is, I assume) and obviously it wouldn't fit in this case... Though, I did some measuring with Photoshop and even though it's not the most accurate method, it seems that the width of the HU without the silver bezel is around 26cm and there is no way I could fit it in the center console bezel.

The next options would be either the Newsmy unit for VW Tiguan (NR7007) or the one for Kia KX3 (is this Kia unit even official one?) or I could go with the Ownice OL-1645NH which is for the Honda CRV. All of these seems to be few centimeters narrower than the NR7002. Does anyone here have any experience about Ownice units? I know there is a thread for those also but I guess it wouldn't hurt to ask here first.
[Android Head-Units] x5nder:
What's the best way to uninstall Viper4Android completely from the xdAuto rom? Curious to see if it stops the stuttering.
[Android Head-Units] jkchr1s:
I was trying out the stock rooted rom. In xdAuto you can delete the driver, don't remember where its installed though. Once you delete the driver there is another folder in /mnt/sdcard that's called Viper4android, delete that and the apk and you should be good.
[Android Head-Units] zanix:
I've noticed that bug as well, even if music is turned off it was still playing BT media audio.
[Android Head-Units] leonkernan:
Is that after the latest commit?

I've had another read through the possible ways this could happen and I think the patch i'm working on now will silence it whenever the switch is off.

After that I want to start looking into letting the phone play it's own sound when the music switch is off rather than being silenced.

Sadly it looks like that is going to need major changes to the pairing and connection code so it will take a bit of time before it happens.
[Android Head-Units] zanix:
No, it's on the current release of xdAuto. I don't have anything set up to compile anything at the moment.
[Android Head-Units] DiGi91:
Stock ROM is still going strong but has some hiccups here and there. I am thinking of trying out XDAuto since I really am missing a lot of the features. I am honestly growing bored and tired of constantly trying to get it to work the way I want but something keeps me at it... Using Automate and it's okay; not having any service on the HU is the cripple to Automate as I use copilot for all of my navigating.

Still using Poweramp and skips are not present as of right now, on MCU 48 I think. I just want to find a setup that I am happy with lol
[Android Head-Units] Bonsario:
Hi everybody,

just got my new NR5002.

I updated to Xdauto 1.1.6c with SD card and wanted to update the 1.1.6c2.zip via TWRP.

Following error occured:

E: zip file is corrupt!

How can I get it work?

Also I want to update from MCUv47 to v49.

The wiki says: This must be an external SD card, this will not work if placed on the internal SD or USB

As the NR series doesnt have an external SD card slot, I tried it with USB, but it doesnt worked.

What can I do?

Thanks a lot!

Best regards

jo
[Android Head-Units] toologic:
Hmm. This is true, but on the contrary. MCU update files must be on internal_SD in root directory.
[Android Head-Units] Bokomaru:
The USB directory naming the code uses aren't standard and while it is coded to use USB, it doesn't actually work right. It's on the (long) todo list. You can copy it to the internal_sd directory.
[Android Head-Units] Bonsario:
Thanks, after updating to v49, installing the 1.1.6c2 was no problem.

But why there are 2 bluetooth apps? Also in the bluetooth app, the dial numbers are too big...attached a pic.

(http)://fs5.directupload.net/images/151129/f3r7568v . jpg

What can I do against that?

Best regards
[Android Head-Units] leonkernan:
Don't use the Android stock dialer, it doesn't work in landscape.

Use the Bluetooth app's dialer screen or tap on a phone number in the people app.
[Android Head-Units] Bonsario:
Can I replace the Bluetooth app with another one which looks better?
[Android Head-Units] leonkernan:
Try Exdialer.
[Android Head-Units] IdleCuriosity:
Admitting defeat

I have had my NU3001-01-H for a couple of weeks now, playing with it on my desk. It works perfectly (even finding my position inside under a tin roof). I have been able to install xdAuto, and I have had a lot of fun setting it up the way I would like it to work in my car.

However, my car is an Australian Toyota Camry 2014, and its original head unit sits in a curved panel and is surrounded by buttons and knobs. The NU3001 (being a double-DIN unit) needs a dash kit, and I had ordered one before I bought the NU3001. The problem is that the dash kit didn't quite fit my car. It was close, but the lengths of the mounting posts differed slightly - the end effect being that the dash kit sat flush with the car's dash at the top, but the gap gradually widened on the way down until at the bottom there was a gap of about 4mm. I know 4mm doesn't sound like much, but it was rather obvious, and my wife wasn't happy about it.

I thought it might just have been one brand of dash kit, so I bought a different one. Guess what, it was exactly the same as the first! Makes me wonder if the Australian Toyota factory uses a slightly different mould compared to the rest of the world, despite the dash appearing to be identical.

I couldn't just trim away part of the dash kit, because what it needed was extra plastic to fill the gap. I was not willing to start messing about with rubber moulding to hide the gap. So I gave up. If nothing else, I hope this post may save any future Australian Camry owners from suffering the same frustration I have experienced!

The dash kits have gone back, since they didn't fit the car they were advertised to fit.

I can't reasonably return the NU3001, since there was and is nothing wrong with it, and shipping costs from Australia would be prohibitive anyway. So it looks like my best option is to try selling it (presumably to someone in Australia, since it would only save postage costs for a local buyer).

I have read the XDA rules, which prohibit selling in the forums and recommend using Swappa. However, when I went into Swappa, my choice was between iPhones, Smartphones and Tablets, none of which seemed quite right. I suppose Tablets would be closer than Smartphones?

Does anyone have any experience of (privately) selling this type of device? In particular, would Swappa be more likely than (say) eBay to be found by someone interested in an NU3001?
[Android Head-Units] Bokomaru:
I've seen the rules but I think (hope) that just posting that here will be enough to drive an AU buyer to send you a PM about it. There is a pretty small market for these type of devices and I think the general rules are to keep businesses from taking advantage of XDA users here, so I think you are fine (though I'm not a moderator and don't speak for them)
[Android Head-Units] leonkernan:
A couple have sold recently on eBay I think. One was close to me here in Melbourne and the other in NSW.

Both sold for close to the original price.

Know what you mean about the unit not fitting in a Toyota too well. Mine sticks out more than the original but because of the Prius C flat dash design in doesn't look too bad.

I made the extra pieces to fill the sides on mine as the normal aftermarket filler pieces left a big gap.
[Android Head-Units] mureren71:
Hi

New here on the forum, and new to Android as well!

Bought myself a Newsmy NR5261 (Carpad 3 version!), and i'm expecting to receive it in around one week :)

However, i would like to hook it up right beside my pc, while i'm updating MCU, ROM, apk's, changing and exploring settings etc.

How is this best done?

I would think something like an old 240V AC to 12V DC powersupply/transformer, removing the plug, stripping the wires, and connect the Newsmy red+yellow wires to the power supplys +12V wire, and the Newsmy black wire to the power supplys ground wire.

Is this how to do it, and if it is, what output should the power supply have in milliamps?

Also, the newest stock ROM has a 2,5GB partition for system. How can this be changed in XDauto ROM?

I found this http://xdaforums.com/showpost.php?p=58859034&postcount=2975, but i'm afraid i need more help than that :)

Best regards

Thomas
[Android Head-Units] mureren71:
Excellent news, especially if this applies to the NR5261 too! (fingers crossed.... :))
[Android Head-Units] ddbigs:
Hi, just found this thread and a little confused. First post mentions that only the universal unit is pure android? Is this still true? I see some unites at Newsmy that are car specific. I found my car but its under CarPad 2 (dual system). So I don't want this?

Also I found another site that sells a unit specific for my car (Nissan Altima / Teana) and they say pure android. Should I stay away?

Thanks