yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] usafle:
I'm still waiting for my new Firewire cable to come in and hope that solves most of my issues, hence why I haven't been posting much on here.

What's the status with the WiKi/Knowledge Base? It would be a great help for many other users if we can consolidate all this information into a clear easy to read format. I've been here since the start and even I am getting lost trying to keep up.

I'd be more then happy to add my .2 cents to the WiKi on how to flash Red's ROM and stuff like that with screenshots and etc. Or, is one person supposed to handle all that?
[Android Head-Units] Zaphod-Beeblebrox:
Anyone can start/edit/maintain a wiki. It's meant to be a group effort.
[Android Head-Units] Dream Reality Syndrome:
I've only been able to edit the generic head unit page. I still can't figure out how to begin a new page. I'm too much of a noob concerning Wiki pages
[Android Head-Units] Zaphod-Beeblebrox:
Ok. I created it:

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001

If everyone could jump in and start editing it. 1st post would likely be a good place to start.

Also, link to it from the other android radio pages please.
[Android Head-Units] usafle:
I just copied / pasted the first paragraph from the OP into it (Yes I stole from the OP). I've never done a Wiki page either and thought it would be a lot more "WYSIWYG" type of thing. So, just wanted to see how it worked.
[Android Head-Units] abburns:
Wiki updated with most of first post including picture. I will do more later.
[Android Head-Units] renedis:
I will do the "connector" part, where to connect which cable..
[Android Head-Units] guap:
after some investigations thanks to [MENTION=5536629]kommando[/MENTION] hints, I came to this http://xdaforums.com/showthread.php?t=1239713

and this is my gps.conf.

NTP_SERVER=0.it.pool.ntp.org
NTP_SERVER=1.it.pool.ntp.org
NTP_SERVER=2.it.pool.ntp.org
NTP_SERVER=3.it.pool.ntp.org
NTP_SERVER=0.europe.pool.ntp.org
NTP_SERVER=1.europe.pool.ntp.org
NTP_SERVER=2.europe.pool.ntp.org
NTP_SERVER=3.europe.pool.ntp.org
NTP_SERVER=it.pool.ntp.org

XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin

# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0

# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0

# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0

# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1

# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1

################################
##### AGPS server settings #####
################################

# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=3425
SUPL_SECURE_PORT=7275
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert

# FOR C2K PDE SUPPORT, set the following
C2K_HOST=c2k.pde.com
C2K_PORT=1234

CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE

# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE

Will sse if it's an improvement or not, this should enable agps and wifi assistance if specified in apn settings (apn type = "default,supl,agps")

Feel free to try it, better replace ntp server with your local servers according to this http://www.pool.ntp.org/en/ (curently it is contry, italy, and europe my zone)
[Android Head-Units] leonkernan:
I'm interested in what improvement this makes.

I'm no GPS expert, but I can't see any code for sending data back into the GPS device to help speed up the fix, only a basic connection setup and NMEA parser.

Any improvement is probably coming from the wifi positioning since the wifi chip has a tighter level of integration with Android.
[Android Head-Units] guap:
you're right about wifi.

anyway agps is a real benefit syncing on the fly the device gps satellite list with the list in view of the cellular tower. Supl protocol also uses the ip address to get a rapid preliminary fix and download a list of known satellites in the nearby to help the gps to obtain a proper and quicker fix
[Android Head-Units] Bokomaru:
With these devices I doubt there will be any noticeable difference. All of these tweaks only really help locking onto position quickly when a device first powers on or checks for location. The GPS in the head unit is always on any time the unit isn't sleeping, so it won't be losing it's signal very often. On a device that is powered by battery you wouldn't want to leave GPS on all the time because of the current draw, so they added lots of hacks to make the location gathering less energy intensive.
[Android Head-Units] NutFM:
FYI I have checked two 3g modems: Huawei e1550 and e173, both work straight forward in modem only mode(AT^U2DIAG=0) on 1.6.1c and 1.9.1 firmwares.
[Android Head-Units] gohigher123:
Hello

Isn't there a way that when i'm listening to music from usb and i power off my car and than later that day i power the car on again , that the player remembers where it was just before powering off. That's an option i really miss.
[Android Head-Units] kwalsh24:
So this is still somewhat over my head, is there an example of how to configure tasker to use the code properly?
[Android Head-Units] fogimup:
Hi all,

I've now managed to install this unit in my Nissan Patrol and gotta say it looks good. I do have one issue and that I haven't been able to figure out yet and that's with the equaliser.

Before I connected to the WIFI, I was able to control each speaker's gain with the stock equaliser app. After the WIFI connection the stock app seemed to update and I then found Bass, Trebble and Mid controls. However they did not work no matter what I tried. I then reset back to factory default and got the old equaliser app which once again let me control each speaker's gain but no trebble, bass or mids.

I'm pretty sure I've read every post in this thread over the last week and I wasn't able to find anyone else with this issue or a fix.

I've also tried this under MCU v40 and ROM 1.1.5 but still the same problem.

Would appreciate hearing from others on this issue or if anyone else has experienced it but not been too concerned.

My next step is to root it and install xdauto possibly with viper, as I've read that the equaliser is good... but I would have expected the stock ROM to have working sound controls.
[Android Head-Units] oldschool.matrix:
My audio shop can't figure out how to get my steering wheel controls properly wired. They bought the CANbus device too. I have a 2013 Kia Soul. Does anybody know exactly which wires go where?

---------- Post added at 12:19 PM ---------- Previous post was at 12:16 PM ----------

I flashed a new ROM to the unit... Now the front panel buttons don't illuminate anymore. I read in one place that there is a LED app that can control the front panel lighting, but I can find it on the unit, posted anywhere and even Emailed Summer... who has no idea what I'm talking about.

Has this happened to anybody else?
[Android Head-Units] Bokomaru:
Not really any examples out there. You basically can just send broadcast intents out to change the sources.

---------- Post added at 12:36 PM ---------- Previous post was at 12:34 PM ----------

This likely depends on the music app you are using. I have my standby set so the android box runs for 24 hours and I drive almost every day so my music is always starting up where I left off.
[Android Head-Units] F16Freek:
Google Voice

Hey guys,

I'm running XDAuto v1.1.6c and MCU v40. I use Google Voice as my phone service, so I've been trying to get it configured on the nu3001. I've got it installed and I can make calls if I go directly into Hangouts Dialer without an issue. However, when I try to make a call w/ "Okay google, call...." it looks up the person just fine, then pops up a gray screen like its going to open something (Google Voice I assume), then immediately closes and goes back to the Google Now page w/ the person I was trying to call. Has anyone successfully gotten Google Voice to work from the Newsmy, am I just overlooking something? Please send help! :p

Thanks,

Andrew
[Android Head-Units] Bokomaru:
I've never seen anything other than the stock sound controls on here. If your app has a bass, trebble, etc. settings I'd be interested to see the apk and where it came from.

---------- Post added at 12:42 PM ---------- Previous post was at 12:38 PM ----------

I did some googling and at least the 2012 Kia Soul had resistive sterring wheel controls, but couldn't find anything definitive on the 2013 model.

Check the "Update settings" app on the device for the "Backlight Keys" settings or whatever the stock version called it. Adjusting the blue setting would adjust the brightness on the 3001 units.
[Android Head-Units] f(x):
Check your car type in mcu settings. That tre bass settings are only for VW/Sonata car.

Btw, viper is included in thr xAuto rom.

---------- Post added at 10:03 PM ---------- Previous post was at 09:54 PM ----------

Dose it work if your music is on the sd card? Both Apollo and Winamp on mine will resume after a reboot/power off, but all my music files are on the sd card though.
[Android Head-Units] kwalsh24:
There's tre / bass adjustments for the vw series ? That's news to me will have to check into that one now
[Android Head-Units] jkchr1s:
I tried getting an antiglare screen protector, and it looks much, much brighter in the sunlight now. I found it on amazon for $5 and cut it down. The viewing angle isn't quite as good as without it, but I'm much happier with it in direct sunlight.

Cover-Up UltraView ASUS VivoTab RT TF600T 10.1-inch Tablet Anti-Glare Matte Screen Protector https://www.amazon.com/dp/B00CYFZ52M/ref=cm_sw_r_awd_wTUPvbE2TZDQ2
[Android Head-Units] Zaphod-Beeblebrox:
I've been running a 160dpi test build for a little while and I don't like it any better than I did the first time around. I also ran a 200 DPI version for a bit, and it didn't seem to offer any real improvement for me over 240.

So unless [MENTION=4173803]Bokomaru[/MENTION] or [MENTION=6472486]leonkernan[/MENTION] feel differently, I think I will leave xdAuto at a default of 240dpi. I will, however, merge in some of my changes that make the other DPI's work. There are plenty of ways to manually change the DPI to something you like.

FYI: work has been a bit on the busy side for me lately, and doesn't look to let up for the next few weeks. Probably won't see any new code from me for a few weeks.
[Android Head-Units] leonkernan:
I agree that's probably the best approach, so long as it's possible for people to use other options without things breaking.
[Android Head-Units] oldschool.matrix:
I have 80+gigs of music on a 128gb sd card and have no trouble playing the music or using the Eq.
[Android Head-Units] fogimup:
Thankyou, ordered one, I'll give it a try.
[Android Head-Units] fogimup:
I couldn't find the APK details for the equaliser but I just checked the different Car Config options and f(x) is right. It was nothing to do with the app itself rather the MCU version. With the original MCU v36, I only got Volkswagen and Sonata options, so after the update took effect, there were only non-working controls ie Sonata/VW.

With MCU v40 there is now "Other", which removes the non-working trebble, bass and mid, but allows control of each speaker.

Still makes no sense why Sonata/VW controls don't work or what the differences are, as one would expect trebble, bass, mid controls as defaults on all headunits.

I think it's time to give xdAuto a go now :)
[Android Head-Units] kwalsh24:
Thanks for the photos. I don't think that eq is in xdauto?
[Android Head-Units] leonkernan:
Should be, look for the SoundBalance app.
[Android Head-Units] Psy87:
Is there an intent which I can use to set an absolute value for volume? I want so set a fix startup volume, because after a while of driving I pull up volume to about 20, but if I come back after a break, thats a bit too loud :D
[Android Head-Units] iHarry:
Hello guys.

I have a problem.

I have USB-OBD adapter (www-dx-com/p/elm327-v1-5-obd2-obdii-can-bus-usb-auto-diagnostic-interface-code-scanner-reader-126542)

When I connect it to NU3001 Torque app did not detect it neither other apps like Prolific PL2303 USB-UART do.

But when I connect it to my LG G Pad 8.3 tablet, it detects and working properly.

Also I have simple USB to serial converter and it detects normally on NU3001 and working.

On windows PC both of those devices detects as "prolific usb-to-serial comm port" with same VID and PID.

Where is the problem? Please help.

Sorry for my English.
[Android Head-Units] toologic:
I think you need a pl2303.ko module
[Android Head-Units] guap:
[MENTION=2190016]Zaphod-Beeblebrox[/MENTION] can you update usb_modeswitch package in your next build? Seems a bit outdated and should help many users to get 3g dongles to work out of the box

I just figured out that some devices in compatibility list

http://www.draisberghof.de/usb_modeswitch/device_reference.txt

are not actually in our usb_modeswitch.d (including my Alcatel x215s, uncorrectly configured as x220 and because of this working erratically) We have now v 1.2.0 and latest stable is 2.2.4 :D Also module "usbserial" should be very useful with some new huawei devices. Many of latest parameters and modem doesn't work with our outdated version, some others luckily works anyway.

for anyone out there with same dongle of mine, just drop the attached config files and restart (zap the .txt ext)
[Android Head-Units] pfarley11:
Hi Guys,

Did you happen to hear anything back from these guys?

By the way, I emailed Summer about the display screens. She said that all the replacement display screens they offer right now are the same brightness. She suggested that I purchase a "sun shade frame" . . . (e.g., http://www.ebay.com/itm/New-Univers...e-Screen-Anti-Reflective-Housing/360913137791)

I asked if the unit replacing the NU3001 might have a brighter screen, saying that it would make it the perfect Android HU . . . I'll keep you posted on what she says. Hopefully, they'll consider this for future units. (or maybe replacement displays)
[Android Head-Units] wacko37:
Still talking to a few different supplier/manufacturers. Proving alot harder than i thought.

Came close with a few of the larger companies but it always fails when they ask for my company details???
[Android Head-Units] zanix:
There only seems to be intents for adjusting the volume up/down, but not for an absolute value, unless I'm interpreting the code incorrectly.

Looking at the source code, volume up sends the intent which fires "mHandler.sendMessage(mHandler.obtainMessage(VOLUME_ADD));"

}else if(intent.getAction().equals("android.intent.action.BONOVO_VOLUMEADD_KEY")){
if(dial == null){
//	Log.v(TAG, "++++++ VOLUME ADD+ dial is null");
dial = createVolumeDialog(getVolume());
}else{
if(!dial.isShowing()){
dial.show();
}
Message msg = mHandler.obtainMessage(REMOVE_DIALOG);
mHandler.removeMessages(REMOVE_DIALOG);
mHandler.sendMessageDelayed(msg, VOLUME_DIALOGE_TIMEOUT);
}
mHandler.sendMessage(mHandler.obtainMessage(VOLUME_ADD));
}

The handler seems to adjust the slider by calling "mSeekBar.setProgress(progress);"

case VOLUME_ADD:
if((mSeekBar == null)||(mTextView == null)||(mImageView == null)){
break;
}
if(mMute){
Log.d(TAG, "VOLUME_ADD--->mMute!!!");
mMute = false;
setMuteStatus(mMute);
mImageView.setImageResource(R.drawable.ic_sysbar_volume);
break;
}
progress = mSeekBar.getProgress();
if(progress < MAX_VOLUME){
progress = progress + 1;
mSeekBar.setProgress(progress);
}
break;

I don't really know Java or know much about Android coding, but my guess is that we might be able to add another intent that takes a value that calls "mSeekBar.setProgress(progress);" to set the volume.
[Android Head-Units] pfarley11:
I wonder if there's a replacement screen/digitizer from a 7" tablet that could be used.(?) I'm not sure how standardized this stuff is. (connectors, sizing, etc) If that was possible, that would sure simplify everything . . .

Amazon has screens and digitizers for pretty much all tablets. It would be great if one of those would work. (maybe with some connector adapters?)

If anybody has one of these on a work bench that they're playing with, it might be worth playing with replacement tablet screens and/or digitizers to see what's possible.(?) I acknowledge that this may be a lot more difficult/complicated than what I'm describing . . . : ) Sorry. I'd help more if I knew what I was talking about.
[Android Head-Units] Bokomaru:
Fixing it up and submitting a pull request on github will be the quickest way to get those changes in
[Android Head-Units] kommando:
Just make a name up, no body checks until you need to place an order, say you are the purchasing manager.
[Android Head-Units] gohigher123:
Where do you find this setting to put the android box in memory for 24h? I can't seem to find it.

---------- Post added at 10:10 PM ---------- Previous post was at 10:03 PM ----------

And i just installed the radio in my car now , everything works accept for the radio app. When i try to start it it says radio has stoped. So what's wrong here?
[Android Head-Units] rendl:
it is in the app called mcu, looks like a computer chip icon. In that APP scroll down to last point. Of course only if you are on XdAuto , in stock ROM it is always 2h.

Gesendet von meinem Nexus 7 mit Tapatalk
[Android Head-Units] gohigher123:
That's the problem why i can't find it. :) I'm not yet on xd . Maybe after flashing xd my radio app will work again?
[Android Head-Units] rendl:
I cannot pair to the HU at all via bluetooth. Where do I have to start the scanning of the HU BT? I read all posts over and over again and those answers say an APP called update settings. I do not have that, I assume it means the mcu APP, but within the mcu APP there is no BT settings..well there is BT upgrade but that is of course something different. I can pair to the box RK.. But not to the HU. What is the typical HU BT device Name and where do I Start that pairing, or is there no config APP at all and it is like leonkernan indicated just open.. but I was not able to pair.thanks

Gesendet von meinem Nexus 7 mit Tapatalk

---------- Post added at 11:06 PM ---------- Previous post was at 10:58 PM ----------

Which Rom Version are you on? Xd is great but maybe before you change you can try to update to latest stock ROM. They just are pushing new version out. Before that you might even try resetting the radio app in the settings..apps etc

Gesendet von meinem Nexus 7 mit Tapatalk
[Android Head-Units] Bokomaru:
All of the HU Bluetooth pairing/setup is in the "Bluetooth" app.
[Android Head-Units] rendl:
Thanks. That was it. How could i have been that blind.
[Android Head-Units] wacko37:
Thats pretty much what i have done, but for them to manufacture something they want my details.... even if i can pay for it or not they need to supply a company.

Also i have searched the digitaliser used on the 8" and it is really cheap. $30 cheap.

From what i have been reading this is the most important part to the antiglare.... using different processes like bonding the layers etc are important so i doubt it the screen needs replacing.

But for me, now i want a 12.1 screen and i will be happy for years to come

8" screen just does not cut it for me anymore!
[Android Head-Units] blacklistedcard:
Lol. Just hook up a 24 inch touch lcd
[Android Head-Units] wacko37:
Is it that simple?
[Android Head-Units] kommando:
PM me, I have a registered company you can use for the inquiry side.
[Android Head-Units] gohigher123:
Can you choose more than 24h on xd? Or choose always ? :)

---------- Post added at 07:19 AM ---------- Previous post was at 07:15 AM ----------

That's the problem , i'm not on stock anymore. I first tried xd first to see what it looks like . And then i tried tuatara .Thats what's on my unit for the moment. I'm about to flash xd again . Hope the app works again after the flash.
[Android Head-Units] wacko37:
Thanks mate. I may take you up on that offer.... there is a few companies i waiting for a response. If all else fails i like send you a pm
[Android Head-Units] gohigher123:
I installed an aftermarket wireless cam on this unit and i must say it's working fine. From the moment you put car in rear , the video pops up. Also when i turn the lights on the units backlight dimms. This is really a nice unit. Ok there's still room for improvements but i'm sure that some people here on this forum will fix everything. :)
[Android Head-Units] rendl:
Not in my car right now, but yes i think you can choose always on. Alternatively you could wire 12V permanent to where currently the red ignition wire goes. However think about draining battery. There is some threads about that subject here.

Gesendet von meinem GT-I9195 mit Tapatalk
[Android Head-Units] Psy87:
A dirty solution could be, to send 40 intents of volume down and then about 10 of volume up to get to absolut 10?

But I dont know when to send. What could be the trigger?

Next step would be, to lower volume if in reverse gear :D
[Android Head-Units] gohigher123:
Does any one now anything about the steeringwheel control mapping? I'm trying to map my volume keys but its not working. When i'm in the mapping app and it try to map volume up , i select volume up and then i push the volume up button on my steering wheel. The mapping than works because there is now a no. filled in on volume up. But when i than try to use the volume up on the steering wheel nothing happens. I'm driving a ford kuga.
[Android Head-Units] fogimup:
I still can't get the equaliser to work even with xdAuto and Viper. BTW, I couldn't find specific setting for Radio on Viper, only headphones, bluetooth and a couple of others.. is there any?

I emailed Summer about the EQ and this is what she replied with: "Does you mean EQ? Our this model do not support EQ. "

hmm.. how can you have a car headunit without a basic working EQ? I've told her about the settings being available but not working, so let's see what she comes back with. Starting to annoy me.
[Android Head-Units] kommando:
The radio is on the head unit not the android box, so Viper cannot see the radio hence no way to use Viper on the radio sound.
[Android Head-Units] rendl:
I understand the Radio is on the HU, but what is this Viper tutorial then good for if it can not control the Radio?:confused:

http://xdaforums.com/wiki/Newsmy_CarPad_NU3001/Viper4Android
[Android Head-Units] Psy87:
For MP3
[Android Head-Units] Bokomaru:
Yes there is an "Always On" setting. I would not recommend changing the wiring though it will definitely run down your battery since the device would never go to sleep.

---------- Post added at 08:39 AM ---------- Previous post was at 08:36 AM ----------

There is already a setting to mute if in reverse. This happens internally on the HU. Someone motivated could code something up to add a setting to lower the volume in reverse, of course it would only work when the android box was booted. Another alternative would be to use tasker to lower the volume, since I added the reverse intent in xdAuto this would be pretty easy to do.

---------- Post added at 08:41 AM ---------- Previous post was at 08:39 AM ----------

If it's showing a number then it sounds like your SWC is hooked up properly, I'd guess it's a software issue. What are you running on there and what is the version?

---------- Post added at 08:44 AM ---------- Previous post was at 08:41 AM ----------

For any sounds that are generated from the Android box. So it will not work with the radio, aux input, or bluetooth input. Personally I almost always am playing audio from the android box, I'm not sure why anyone would be doing anything else. I'm annoyed by commercials/advertisements so I tend to avoid any broadcast media.
[Android Head-Units] zanix:
A very dirty solution, just hope the 40xVolume Down gets picked up before the 10xVolume up
[Android Head-Units] f(x):
I am not familiar with Tasker, can it call a java function directly? If it can, why not just use the setVolume(mVolume), like the one in RadioService, to set the desire volume?