yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] DiGi91:
Tried it a while ago and it didn't see like it was compatible with what I wanted to do? I use both poweramp and copilot 100% offline and once in a while I will tether to use spotify. I also do not have a dedicated mic for google now and seeing as I am offline doesn't seem like there is much going for me.

Correct me if I am wrong. Automate is a great concept and I have tried it back when I have my appradio and arunchained.

---------- Post added at 05:47 PM ---------- Previous post was at 05:45 PM ----------

No viper for me and I have not had a single audio problem. Loved XDAuto to death but just like any other android device and ROMs; it does not work 100% on all devices. It is what it is lol

It also seems snappier to me for some weird reason. I am using 1.3.0 with MCU 46 (I think) and rooted with Kingroot.
[Android Head-Units] jkchr1s:
I still can't believe we are the only two that have audio issues with xdAuto. I tried for hours one day to get to the root cause, but nothing seemed to be out of the ordinary. I even ran a cpu monitor and no significant spikes during the pauses. I've just kind of learned to live with it. Logcat seemed to happily chug along with no significant output during the pauses.

If only spotify had an EQ that would be perfect for me...
[Android Head-Units] DiGi91:
I gave up and decided to try the stock ROM after I was having so many other issues and it's been alright for me as of right now. I am in the process of "updating" my music library as we speak so let's see if that causes any issues on the stock ROM. I wish Spotify supported playback of local files and the EQ; such a perfect interface for the car!
[Android Head-Units] Eddy TheHell:
Well, I updated my nu9001 with the new mcu v49 and stock rom 1.3 ( 2gb data partition )

Didn't test everything but I still have 1 gb data partition and the rest nand flash is unmounted and it's like unmountable.

Everytime I mount it, it gone unmounted again. Can somebody help please?!

The 1 gb data partition is my biggest problem how can I solve it?!
[Android Head-Units] x5nder:
I have audio skipping issues with xdAuto as well. Only bluetooth audio streaming is flawless. The more things running in the background (TomTom, DailyRoads) the more often the audio skips.
[Android Head-Units] spoks:
What kind of audio issues do you have? If it is audio skipping by audio player and your music collection (usually quite large) are on SD card, then try to search this thread. There was different solutions for this. In general you have to tell to player App not to read whole library every time. There were some problems in first [MENTION=260727]Tuatara[/MENTION]'s ROMs, but now seems everyone here are using either XDA or stock rom.

---------- Post added at 03:01 PM ---------- Previous post was at 02:56 PM ----------

Search for [MENTION=260727]Tuatara[/MENTION]'s post where are explanation of steps, how to get 2GB partition. If I remember right, there were also other member (from Moscow?) "guide" for this.
[Android Head-Units] jkchr1s:
Brief, half second to second pauses in audio. It happens with Play Music, PowerAmp, Spotify, and every other music app.

It skips with music on internal storage, SD card, streaming, or downloaded Spotify tracks. I've tested with a clean flash, installed only a single music app with < 100 songs, and it will still skip.

The only correlation I can make is usually the CPU throttles down and is trying to jump back to full speed when it occurs. It's almost like (forgive me I know this is an Intel term) SpeedStep is throttling down the clock speed and then it skips, then CPU will jump back to full speed.
[Android Head-Units] Bokomaru:
Did those issues exist before xdAuto 1.1.6c2? I know some people experienced some odd issues with that version but didn't have them before (even though there were no actual code changes that should have affected it). I don't experience any issues like that on my test boxes or on the one in my vehicle, but I use ROMs that I built myself.
[Android Head-Units] jkchr1s:
Yeah, I've always had the pauses. I flashed xdAuto first thing after I bought it, so I can't speak to whether or not it did it with the stock rom.
[Android Head-Units] zeroprobe:
Which link did you use I'll check it
[Android Head-Units] Bokomaru:
Are you sure these half second pauses aren't happening when your phone (assuming it is connected to HU with bluetooth) plays a notification?

---------- Post added at 10:30 AM ---------- Previous post was at 10:01 AM ----------

How did you do the update? In looking through the recovery code in order to make xdAuto able to be easier flashed without using rkbatchtool I noticed that the code only flashes the parameters file (which sets the partition size) in a few unique situations.
[Android Head-Units] jkchr1s:
Yes, positive. I don't connect my phone to the phone BT module, just the one for the tethering profile in the settings app (not separate BT app)
[Android Head-Units] pfdeadpool:
Is there a way to remove encryption once you've chosen to encrypt the device? I decided to encrypt it worrying that if someone stole the radio/car they'd have most of the personal info on my phone- but now startup takes ~twice as long, with two lock screens. On the security menu "Encrypt Device" is simply greyed out. Any ideas? Thanks

*edit running 1.1.6c & MCU v48
[Android Head-Units] Bokomaru:
I've never tried to turn on encryption, it's on my long todo list. I vaguely recall seeing that encryption was disabled in the rom configuration. What ROM and version are you using?

Here are some things to try:

Under "Security" you might be able to "Clear Credentials"

Under "Backup & reset" you can try "Factory data reset"

If you are using xdAuto, you could go into recovery and try to wipe everything
[Android Head-Units] pfdeadpool:
I'm running xdAuto 1.1.6c & MCU v48. Unfortunately "Clear Credentials" is also greyed out. Looks like I'll be going back to my backup when I get some time. Just a heads up to everyone looking to encrypt I guess, always good to have a backup. I set it up to use a 4 digit pin. The system boots into the encryption screen, you enter the 4 digit pin (for encryption); the system boots to the XDA screen, you enter the same 4 digit pin (for the headunit pw), the system then boots. And I don't think there is a way to encrypt without jointly using a pin/password lock (could be wrong). On the plus side encryption didn't take the 1 hour+ they warned, probably <10 minutes, and certainly <20 minutes. Guess I'll just stick to using a regular PIN & not encryption.
[Android Head-Units] Totoix:
Editing xml files did not work, or I could not find the right file to edit.

But, I finally discovered that, there is a bg.png in res folder. I replaced it with the png which I attached. It solved my problem. I made the png based on the original one. I alligned the lines by trial and error several times. I still don't know how to permenently solve this problem which makes the app compatible with different screen sizes.
[Android Head-Units] Eddy TheHell:
I used the stock 1.3.0 (2gb data partition) link from the wiki but it was my fault I updated using sd card and I should have used the computer method.

Everything is fine now.
[Android Head-Units] Eddy TheHell:
I used the sd card method.
[Android Head-Units] Zaphod-Beeblebrox:
If you've now gotten this to the point where the radio app is aligned when navbar off, why don't you post the APK here for others?

---------- Post added at 07:06 AM ---------- Previous post was at 07:05 AM ----------

Stock Rom 1.3.1 released - here:

http://pan.baidu.com/s/1mg0En5A#path=%2FCarPad_v1.3.1
[Android Head-Units] Totoix:
Sure, attached is the apk file. The file is compiled from the latest source codes in the xdAuto repository.
[Android Head-Units] blacklistedcard:
I wonder what changes have been added.
[Android Head-Units] e.sjolund:
NR5002 First thoughts

Hello guys, I just got the headunit in the mail today, and I thought I should share my first thought so far :)

The first thing I want to point out is that the WiFi antenna is sticking out on the left side (screen facing towards you) and that can be in the way for mounting in a custom faceplate etc. I also noticed that the WiFi antenna is emitting noise to the amp causing "popping" noise. Taking your hand over the antenna eliminated the sound, so should be an easy fix. (extend/ relocate the antenna.)

External thoughts on the unit is that i really like the modular design in the back. It got connectors for everything, and they seem to fit pretty snug. I did end up buying the 5.1 audio output connector, but feel it´s a pity that it does not come included (2$ for the cable). Also find it annoying that it got screws holding the lcd faceplate in place, makes for more work on mounting. (The unit does not fit the car, så got to make my own faceplate).

On first power up the unit seems pretty quick (20s?) and you get to the standard Carpad3/2 interface. The unit did come with MCU version 49 and Carpad 3 version 3.0. I did not play a lot around, but switched to xdAuto straight away. I got to give a big shout out to everyone who has contributed! A lot of good features, and a good Wiki page for support! Next step is going to be to make my own boot logo as well as fine tune this well oiled machine :laugh:

So to put it short, a great unit with a lot of features. xdAuto makes the unit a lot more user friendly and adds more features.

Also, I do got a couple of questions:

- Can you change the navigation bar? - replace it for another? for instance import it from another kitkat rom?

- Is there an easy way to change the default DPI on the rom? (I would like smaler icons, the use an xposed module for changing the DPI of sertian apps.)

- Does the audio from bluetooth streaming go though the android part? (viper4android does not seem to work on streaming)

Thanks
[Android Head-Units] leonkernan:
1. not sure

2. yes, either with an app like this or by setting the dpi before compiling a build

3. I think the carpad 3 is the same as the carpad 2 in that regard. So the audio from the Bluetooth module is passed direct to the amp, not via Android.
[Android Head-Units] Orisai:
Does the NR series include 4-channel RCA pre-amp outputs?
[Android Head-Units] zanix:
Yes and no, it's 6 channel [Front R/L, Rear R/L, Center, Sub] but you have to add it ($2) when you buy a NR series CarPad

---------- Post added at 10:21 PM ---------- Previous post was at 10:20 PM ----------

Yay, someone looked at the wiki! :good:

---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------

The navbar has options in settings.

As for replacing it, you may be able to use a xPosed navbar module to do this.
[Android Head-Units] e.sjolund:
I see. I´ll try the app as i got no experience with compiling. Too bad about the bluetooth and navbar, guess i got to try and see if I can find an app or xposed module. I did notice that the superSU app did not allow for changing og the navbar. You actually have to buy the upgraded version for those features.

You´re correct about the audio output. The 5.1 connector also got two wires for the amps remote (Gnd and 12v+)

Someone got to be the first :laugh:

I´ve puzzled with the settings, just not completely the way I wanted it. I´ve been using a nexus 7 in the car for awhile, and I really like my current navbar setup. So my goal it to copy that. I did look into xPosed, but seems like navbar features need a super-superSU, so got to fix that first, then see if it will work :)

Also, did we find a solution to why the screen would not turn on when the car key is on? Mine just tuns on the lcd, and I have to manually touch the screen for it to come to live. - I do remember a member saying to flash the Carpad3 kernel? and that fixed it?
[Android Head-Units] alaninsitges:
This is a different (though just as annoying) problem. When the phone makes any noise (ring, notification, etc.) the mixer in the MCU activates the analog channel that the BT audio is run through, causing a noticeable pop followed by a second one when the notification has finished - so 2 pops in the space of maybe 2 seconds. It got so bad that I just shut off BT and use the speakerphone builtin to my Nexus 6. I wish there were a way to only have phone calls go through BT and leave the other noises directed to the phone speaker.

BTW I had serious problems with the stuttering and pausing on my HU as well, I disabled Viper (switched off "Master Power") and they went away. Running Tuatara's last ROM and some MCU from the dark ages.
[Android Head-Units] spoks:
download from Baidu

How you, guys, are downloading from Baidu? :confused:

Normal download button asks for login, but Fast speed button wants to install some .exe ....
[Android Head-Units] Zaphod-Beeblebrox:
I was never able to do a direct download from there. I ended up creating a Baidu account, and then I just copy it to my account/folder. I then use that .exe file (it's a baidu file manager/upload tool). to download it.

Problem for me is it's all Chinese, no english setting, etc. Plus I'm a little freaked out about the security side of it. I ended up using Google translate on my phone to take photos of the screens and translate them enough to know which buttons I needed to hit to log in to my account :) I then only start it and log in (I don't let it remember my credentials) long enough to download the file and then exit.

Still not very safe. If it's a malicious app, then I'm already a victim, but I take reasonable security precautions and review with my desktop, and I haven't discovered anything bad from using the app.
[Android Head-Units] zanix:
If you are running the stock ROM, then you need to root it. The xdAuto ROM already is rooted.
[Android Head-Units] e.sjolund:
I am running xdAuto, but it seem slike the superSU app that managed super user details did not allow for navbar changes without buying their premium app.

I did find a way to edit the height of the navbar using gravitybox, but it won´t allow me change and add new navbar buttons and commands. I also countered a problem with gravitybox. The navbar can be adjusted, but the icons wont shrink to along. Hopefully, or maybe it would be possible to make this possible in the future? :)
[Android Head-Units] zanix:
Might want to ask Zaphod about this then, I think you need a navbar module that replaces the default one.

There are settings in the Android settings area to control some aspects of the navbar.
[Android Head-Units] e.sjolund:
Thanks, I´ll try to have a look in the Android setting, although it will be like looking though a needle in a haystack, due to my limited skills.

[MENTION=2190016]Zaphod-Beeblebrox[/MENTION] , could you have a look at it, if you got time/ if it´s even possible?
[Android Head-Units] swyner:
Hey all, long time member of xda and have had my share of Android Headunits.....last one was the Parrot Asteroid and then was anxiously waiting for the RNB6 which was cancelled. I stumbled across this as it looks pretty nice. I have a few questions as I wait for Summer to accept my Skype invite that maybe you could help me with....

1) The newest stock rom and MCU, does this allow us to change the standby time more than 2 or 4 hours? Would like to have 12 hour option so all day I will avoid the 20 sec cold boot

2) Even during a cold boot, does the reversing camera show up immediately if you put in reverse while Android is booting up?

3) Does anyone have specifics about the audio preout quality? Is it the normal 2V regular Android headunit subpar voltage? I do have Alpine processor that accepts 5.1 input so wondering if anyone has used the new output and how does it sound? Does it only have 5.1 processing from the Android side? Any more info on the overall audio quality?

4) It's been hit or miss for me when it comes to Radio (FM) reception with any aftermarket HU. The Parrot Asteroid was absolutely horrible and the current Dynavin N6 is awesome (better than OEM). How does this rank? Anyone hear more about RDS implementation?

5) I read somewhere in these 778 pages that Google Maps does not work well since "there is no compass in this headunit". Is this true? Anyone have Google Maps working?

6) 3G/4G dongle support. Has anyone had luck with this? I have a Huawei 4G dongle that worked with Parrot Asteroid but did not work with another no name Android Headunit. Was curious on people's experience

Thanks in advance!!
[Android Head-Units] Zaphod-Beeblebrox:
What Zanix means is that xdAuto contains builtin options for Navbar controls. You can select/deselect all of the pre-built buttons we've made. Just got to settings->navbar and turn on/off any of the buttons.

As for using xPosed/Gravity Box, You can expect to have limited success with that. xPosed modules depend on having fairly stock android resources and code available. xPosed uses Java tricks to 'expose' the builtin methods of the stock code and intercept/replace that code at runtime. Most of the buttons we've added to xdAuto will be unknown to xposed, so there won't be any code meant to deal with it.

However, it's *possible* that if you turned off all the extra buttons, and only turned on the stock android ones (back/home/recents), that xposed could modify those particular buttons. I don't think there were any significant changes in that part of the code. But again, I think you should look at the options that are already available, and maybe go back and read up in this thread about how the intent based buttons work. It's not a perfect or one for all system, but for everything I've ever found to want in head unit, it does wonders.

---------- Post added at 05:25 AM ---------- Previous post was at 05:18 AM ----------

1) - I think people are having to pull the MCU Settings app from xdAuto to make that work. It can be made to work, but will take a little effort.

2) - Pretty sure this is a yes.

3) - Have no clue

4) - I think FM does OK. I don't think it's quite as good as the OEM radio was in my truck, but most others on here have said it is better than others they have used. RDS is still a unicorn. I've glanced through some of their code, and they have lots of little pieces of it, but it doesn't seem complete. I think the guy that was doing most of the early code (cuger88 on Baidu) is gone, as his baidu files haven't changed in months. We might be able to poke around with what they do have started and work with it, but only if they've got it implemented on the MCU side, and just haven't figured out how to tie it back to android. If they don't have the MCU code working, then we are out of luck.

5) - Google maps works just fine. I mostly use Waze, which is better, and works even awesomer! (yes, I did that). I have noticed that certain apps (Nokia Here, possibly Maps) Don't show the direction of travel - most likely related to the lack of a compass.

6) - Lots of discussions in the thread on this one - I don't know the full answer.
[Android Head-Units] e.sjolund:
Oh, i must have misunderstood him. I´ve already been playing with those features, but I though he ment to go into the xdAuto build and look for the navbar code. So, sorry [MENTION=1802543]zanix[/MENTION] for the confusion.

That would explain why xposed did not work properly. Tried to use an module to change the navbar and the androidUI quit over and over. Although one mdule did manage to change som of the icons, so guess thats the stock icons. Also, where in the xdAuto build is the navbar code located? Maybe I can configure something out, or learn some.

I do agree that the navbar satisfy all of my needs, i´m just too picky when it comes to layout and somewhat the size :silly:
[Android Head-Units] Zaphod-Beeblebrox:
Being picky is not a bad thing at all. Especially if you are willing/able to do something about it. It's where innovation comes from. Just be sure to share your creations here.

Source code for navbar largely exists here: https://github.com/Nu3001/frameworks_base/tree/master/packages/SystemUI
[Android Head-Units] zanix:
1) This works great on the xdAuto ROM, but others have had success pulling the mcu settings app from it into the stock ROM.

2) I never tried this, now I have to

3) I have the NU3001 so I can't speak about the NR series. I think the power output is most likely 2V. I have not and do not know how to even test this. I do have to have my amp gain set a bit higher than my previous stereo which had 4V outputs. Does any one know how to test the output voltage?

4) Radio reception is good for me. Most issues seem to come from people that forget to connect the antenna power for amplified antennas.

5) Google Maps works just fine as does the Navigation, although rotation is slow since it needs to use GPS to figure out your direction. You also don't get rotating map when you are out of navigation. HERE maps settings menu doesn't even work on these units so you can't configure it.

6) Many people have had luck getting these to work, some people can't get them to work at all. It seems kinda hit and miss.
[Android Head-Units] -=Jeff=-:
The others covered many of the other questions.. I can answer this one:

2) YES, on cold boot the Camera will still work. in fact I start my car, Put it in reverse and by the time I maneuver it and start driving, Android is booted up
[Android Head-Units] nestortoledo:
Thats will be awesome.
[Android Head-Units] Zaphod-Beeblebrox:
I haven't downloaded anything yet.

The biggest reason I haven't been actively involved in AOKP for some time is I've just been too busy. This device has given me a little more 'desire' to get back into coding, but I've not yet pulled the code, set up my VM, etc.

I also want to try and do things in a productive order. With Lollipop source now being available (and both CM and AOKP actively working on getting builds up), it might be worth holding off on feature code and put effort into sorting out the build issues. IE, don't spend a ton of time working on Kit Kat, let's go straight to Lollipop.

While spending some time on the Bonovo apps will not be 'wasted', spending much time in SystemUI (nav/status bar) would have to be re-worked for L.
[Android Head-Units] red13dotnet:
While I agree that L would be a nice step, we do have to remember this is a rockchip system. Drivers and the like may not be workable with an L compatible kernel, not to mention the MCU comms. Additionally, with the rooting issues involved with L and compatibility issues (especially viper which is up to KitKat only) I don't see why we would need to go to L for the foreseeable future. What will it really give us on this platform that is worth what we'd lose? I'd prefer to sit on KitKat and have a working system until L is more mature.

Sent from my Nexus 5
[Android Head-Units] Zaphod-Beeblebrox:
Fair points. Right now, my involvement is still purely theoretical :) You are doing the real work so far. And even past that, I've never been a build/enablement guy. I'm just a Java hack.
[Android Head-Units] red13dotnet:
I appreciate your thoughts on this matter. Also, regardless of KitKat or L, I would greatly appreciate any effort you can make to port your UI enhancements to Amplified. I think I can speak for all of us there. :thumbup:

Sent from my Nexus 5
[Android Head-Units] Zaphod-Beeblebrox:
I'll do my best to bring those features to the device. Having used the AN-21U and it's useless Nav/Statusbar for a while now, I can definitely see where a customizable Navbar will benefit this device. I also want to bring back 'Tablet UI'. Having both a Status bar and Navbar on this device is just wasted space.

As for the L issue, I have a dual motivations here. I recently bought a Nexus 9, and I REALLY want Tablet UI back on it. I have been thinking for almost a year now about how to do Tab UI better than we ever did it before, just not enough time/motivation to make it work.

Now I have two devices that need it, so its getting a little higher on my list :) I would prefer to code that on one base though (L), not do it twice :)

By the way, My DHL tracking number now has a delivery date of 11/20/14. Guess they actually did ship it!