yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] zanix:
xdAuto has this built in.

If you are on the stock ROM, you can fire an Android intent from tasker

https://xdaforums.com/wiki/index.ph...id_Intents_.28Volume.2C_Mute.2C_and_others.29
[Android Head-Units] robertusIT:
I see that about intent , for now I'm on xdauto, but i don't understand how to change master volume to 13 for example.

In wiki only xdauto intent for change volume are:

Volume Up
android.intent.action.BONOVO_VOLUMEADD_KEY
Turn up the volume by 1
Volume Down
android.intent.action.BONOVO_VOLUMESUB_KEY
Turn down the volume by 1

But change volume from or to 1, you can't set a specific volume.

( I need it because when i listen radio or music, and receive a call, when i accept it, the volume is so loud, so a tasker that set up for calls, volume on 13, is perfect, than i made another exit task to come back music with another volume. )
[Android Head-Units] catu:
Reg #9367 (how do I qoute?

Nobody with experience in debugging this kind of thing? VAGCom or Android log maybe?
[Android Head-Units] robertusIT:
no experience in this way but i can suggest to disable canbus in MCU app settings, and try if device reboot or not.
[Android Head-Units] peregrines:
Hi guys!

All of a sudden I get the message "your device is not compatible" when trying to reinstalling Tomtom Go or some other apps from Play Store.

Do you know why this happens?

Did you experience the same?

I am on the latest XDauto build with Carpad2!

Thanks!
[Android Head-Units] zanix:
This is the crappy part, there is no intent to set the volume to a specific level.

I have a Tasker task that resets the volume when going into standby. I have the task hit volume down 30 times, then up 8 times and it actually works decently.

You can probably do the same when a call is incoming, it should have enough time to run before you even pick up the call.
[Android Head-Units] robertusIT:
i provided to uploaded catlog to my issue with my Nexus 5 but i have this problem also with my Samsung S7 Edge completely stock no root.

View attachment README.txt

View attachment 4056629

Issue:

With my Nexus 5 Nougat when i call a number, i have No Number, so radio doesn't show caller name or number.

If i call a number like 1234, same issue if i compose from phone or radio.

Only when i receive a call i can see the number or call name, but when i accept call, show no number..... :( why ?

With my new phone Samsung S7 Edge completely stock no root, same trouble... unbeliable....

Works only if put in my nexus 5 marshmallow, in this way i can see number or call name in my radio, and also if i call 1234 from my phone or radio, i can see in radio the number.

Please if someone can figure out, why.... will be very great.

note. i tried stock rom 1.4.2, same trouble, exactly like in xdAuto.
[Android Head-Units] Zaphod-Beeblebrox:
You should take a look at this:

https://github.com/Nu3001/packages_...m/bonovo/bonovohandle/HandleService.java#L257

You can use intents to set the 'balance'. In bonovo terms, balance is just a percentage of volume, right? so set the balance on all four channels to 50%, and then restore them to your previous values after the call...

It would also be trivial for me to add an intent to set the volume. Now that I'm actually doing a little code again, I'll put it on the short list.
[Android Head-Units] robertusIT:
I see also, when i flashed stock rom 1.4.2 ( last build ), that there are a difference between it and xdauto, in MCU section.

In stock rom you have in Car Config - Vehicle Configuration RGB Backlight

In very important for who have a rear camera, because settings the exposure.

in xdAuto 1.1.6f but also in others version, this feature seems to be removed, i don't know why but is different MCU setup.

As you can see, MCU version is the same, 57.

I only tried to flash stock rom to provide logs for "No Number" about outcoming call ( some posts ago ), and i see these differences.

Can be possible to reintroduce this feature?
[Android Head-Units] Zaphod-Beeblebrox:
Have you even read this thread regarding the source code that we have. There is a reason we version xdAuto with 1.1.6(x). It's based on the source code leaked from Newsmy (by accident - they didn't intend for us to get it). That leak was version 1.1.6.

If you want the other MCU features they've added, get them to release the code.

We can and have implemented things Newsmy never even dreamed of in xdAuto. However, when it comes to anything dealing with the MCU, we are incredibly limited by not only a lack of recent source code in their MCU communication apps, but in not having code for the MCU itself.
[Android Head-Units] robertusIT:
Yes I know that, my question is because with the same MCU, if you change only ROM from stock to xdauto, you have different feature in mcu, like rgb backlight.

Seems that ROM can be influence MCU?

Thanks anyway for the explanation and for the amazing support.

If you have time to spend about strange issue of no number for outgoing call, or if needed others logs, please tell me

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Head-Units] Danny.69:
Try extracting the mcu.apk from the rom stock.

And update in xdauto, it is possible that so to have that option
[Android Head-Units] Zaphod-Beeblebrox:
What you are getting in this device is more of a promise. I was only moderately interested in this device until the full source code was 'discovered' :) While some of the other units (AN-21U series in particular) might be better suited out of the box, the longer term promise for customization is stronger in this unit. If you don't like the radio interface in the AN-21U, you can do some minor theming and face-lifting, but your stuck with the underlying code. With this unit, we can (and probably will) completely re-write and/or add functionality.

Some earlier discussions centered around Android Auto. While we won't port a true Android Auto OS to this device, we can certainly make it mimic the look and feel.

Just a lot of open promise in an early device.

Also, to update my AOKP progress, I ran into a compile error that I haven't been able to overcome yet. [MENTION=6095496]red13dotnet[/MENTION] is also pulling down my repo to see if he can sort it out. With work and the Thanksgiving holidays this week, I doubt I'll get any time to work on it this week or weekend.
[Android Head-Units] stops91:
That is exactly how I feel. I want this device to replace my radio with extra features that come with it like GPS but I don't want this as a tablet in my dash. If I wanted that I would just buy a Nexus 7 in my country and do the same for half the cost of this unit with shipping. Basically I would like for the radio to work perfectly (with RDS) and for bluetooth calling to work perfectly. Everything else is a great bonus.
[Android Head-Units] welshblob:
I asked her this morning and she confirmed it was compatible and it was $15 extra. Sounds good to me.
[Android Head-Units] spoks:
Then, probably, this unit is not for you at this time. Take a look at Android+winCE units, but as I know they is not bug-less too.
[Android Head-Units] stops91:
Don't get me wrong - this unit is perfect and the work that red13dotnet has been doing makes it even better. Without his development this would just be another standard Android unit. I don't think I would ever buy an Android+winCE unit because of their crappy software and hardware.
[Android Head-Units] nestortoledo:
I get this unit, mainly for the avaiable source code, and teh amazing developers behind it (@Zaphod-Beeblebrox, [MENTION=6095496]red13dotnet[/MENTION] and more to come for sure will do an amazing job on this)

I dont care much about the UI. as most of the app can be themed, and with sone teaks on the android plus a custom made UI themer + zooper sure i can get something that cover my needs.

For me the big points of this nesmy units are

- Full source avaiable

- Separte android box

- Quadcore processor vs others

I was looking at Huifei units and are pretty nice and have cusom models avaiable for each car model and a litle cheaper than newsmy,

But after reading and reading all units have his own problems.

Problems that if are not solved by the manufacturer, will be easy for xda developera to fix with the source.
[Android Head-Units] snahrck:
Hi Guys, I have a question about the video inputs.

If we connect the a camera to this unit do you thing it is possible to have access to the video input in an App? I work with image processing and we could do many nice things, such as birds eye view and other image transformations, customizable guidelines, object detection, ... well, many of possibilities. I have experience with android programming and image processing and would volunteer to create such an App if it is possible.
[Android Head-Units] vortexring:
To clarify, yes this is by far the best unit out there, hardware wise and software wise, it looks good, and seems to be well built, with decent components unlike many of the previous variants/iterations.

It is also great that there are people on board such as [MENTION=2190016]Zaphod-Beeblebrox[/MENTION], [MENTION=6095496]red13dotnet[/MENTION], to name but a few, who seem to have the specialist skill sets to improve this device; but sometimes, even with the best will in the world, peoples circumstances change and their availability to generously commit time and effort into this projects can sometimes stop, that is my only concern.

Maybe at this point it is too much of an "enthusiasts" product as it requires some work to get it into a decent polished state. Unfortunately I don't have any skills in this area other than flashing ROMs onto phones, and that's about as far as it goes for me. I wish I could contribute more but I wouldn't even have a clue where to start; half the time I read these guys posts and I wonder if I'm actually still reading English :silly: Without a decent foundation and fundamental understanding in this field, half of it sounds like gobbledygook to me!

I do think that some sort of "skin" is required that makes the interface more user friendly in a car environment, and like so many have eluded too, half the current solutions out there look like they have been designed by a kindergarten kid, have Apple managed to poach all the decent GUI designers out there?!:mad:

I also think that skin needs to have the ability to have a colour theme applied to it, so for example any highlights or selection emphasis (whatever the correct term is) will reflect the selected colour theme, so for example if you drive an Audi, you can select the "Red" theme, and using the current radio app in the unit as an example, which currently has a blue based interface, it would now be red, ...or amber, or green etc.etc. depending upon the chosen "theme" hopefully you get the picture:) I know Pioneer have implemented something similar in their latest units. The great thing about this unit is it's hardware design is so "clean" that it can fit in any car and look nearly OEM, so it would be great if the interface could reflect this by providing the user with the ability to theme it with their chosen colour.
[Android Head-Units] red13dotnet:
Video sources connected to the h/u cannot be accessed by android apps. Think of the h/u like a television and the android box has the ability to change the input on the television like a remote but it cannot understand whats on the television. UVC compatible webcams plugged into usb work in apps, certainly in the default camera app....though there is some work to be done there as well, i was able to get a camera to work for photos but not video recording... camera config needs tweaking per model of camera used I believe, though that could just be a limitation of the google camera app.
[Android Head-Units] alaninsitges:
Perhaps you didn't notice, but you're not posting on the comments section of bestbuy.com.

XDA-Developers is enthusiasts and developers.

And for all those whining that they just want a good radio (is FM even still a thing?) and phone dialer, why on earth are you messing around with an Android HU? Go buy a Parrot handsfree kit and add it to your stock radio.
[Android Head-Units] stops91:
FM is a pretty big thing where I live, yes. Also there are people that share a car and not everyone is tech savy and/or can play their music from Spotify for example.
[Android Head-Units] red13dotnet:
I think one of the big draws for me was having a car stereo that can literally do anything I can dream up but that passengers are afraid to touch. To me that's a bonus :D
[Android Head-Units] spoks:
:laugh: Perfect!!!
[Android Head-Units] NU5002S:
Hell yeah! Give people more to play with and they will learn faster.

There's so many things that Android can do for automation now that we have an active, stationary computer in our car.

It's like being sent a developer's toolkit for your 10 year old car...
[Android Head-Units] defy_user1:
Hi there...

Found something on ebay.de

http://www.ebay.de/itm/400811879899

It is the same unit like all the others right?

What does Fastboot-System means? I asked them how long does it take to boot up the system, the answer was:

10 seconds coldstart, 5 seconds warmstart - Is this possible?

thanks guys

Edit:

They told me that kernel and launcher are optimized... interesting, maybe I'll give it a try
[Android Head-Units] alaninsitges:
Exactly! There is so much stuff I want to do with mine!

Which makes this a good time to talk about CAN bus support on our units and hopefully save others a lot of time and hassle.

The TLDR is that (after talking with the tech guys at Newsmy) there is no built-in CAN bus capability in the NU3001. The wires labeled CAN H and CAN L are there "for future use" on other models.

Over the last month I've studied a lot about CAN bus to get a better idea about how to use it with the Newsmy. My hope is to be able to create a MMI-type system to control many of my car's settings and functions, as well as get access to performance, diagnostic and telematics data - not just on the head unit but also available to a connected app using the car's 3G connection.

Initially I assumed that supporting CAN bus was kinda like adding Bluetooth or an ethernet port. But it's not. CAN bus is a mess of a network made up of lots of combinations of topologies, protocols, and bus speeds, compounded by a a vast and poorly-documented (for us outside the manufacturer) set of messages that's proprietary to each car. That's why the notion of a universal CAN bus decoder/adapter thingy isn't the right way to think about it - it really has to be something that's specific to a car model.

The 8-inch model that some people have been purchasing is made for a specific car (a Chinese something which name escapes me) and so that unit does include a CAN bus decoder built-in, but it's only going to work with the messages and etc. for that particular car.

In the case of my car, a Saab 9-3, Saab's CAN bus implementation is called i-Bus, running the GM LAN protocol, and it is used for just about everything: my factory radio has no accessory wire, no illumination wire, no SWC wires, etc. It's just power and a data connection pretty much, and the radio is turned on and off by network messages over the i-Bus. Same with changing the illumination level, determining if there is a CD changer or amp present, and responding to the steering wheel controls (the SWC buttons are also connected to the i-Bus). So in order to even install the Newsmy correctly I have to use a CAN bus adapter like this. It connects inline to the radio harness and then provides the wires needed to connect the HU. I have to buy another adapter (for the CAN bus adapter) to provide the KEY1, KEY2 and GND wires that the Newsmy needs.

Some cars have the necessary wires to connect to the Newsmy's SWC, and some don't. Either way, this adapter I bought is restricted to radio functions, so there's no solution here for doing the other stuff I want to do. I'm still researching that.
[Android Head-Units] red13dotnet:
What does intrigue me though is that although it may not now be implemented, the MCU processor in the nu3001 does include a hardware can bus transceiver. However, without source code for the MCU, it is highly unlikely we would ever be able to access it in a meaningful way.
[Android Head-Units] vortexring:
Oh really, this isn't best buy (or Currys for my kindred friends) ? ....anyway someone's a little tetchy:cool:

It is worth remembering that although this site is primarily followed by enthusiasts, me included, and developers, me not included:o, the product is found for sale on various sites that aren't sites associated with enthusiasts or developers, and is marketed as a finished polished product.

I don't think anyone, including me is "whining", I'm just tempering the enthusiasm for a product and mixing in a sprinkling of reality. All I was saying is that in it's current state it's not quite there, and if that's what some people were expecting then surely it is wise to make people aware of some of it's short comings, it's called a balanced discussion:)

Maybe FM isn't your "thing" but I don't think just because you don't find a need for it, that you can dismiss it offhand for those that do have a need for it, anyway it is marketed as part of the device, so what is wrong with expecting it to work properly and in an integrated fashion with the rest of the head unit, and likewise for the hands-free phone app, I don't understand why you think this is expecting too much?!
[Android Head-Units] Dream Reality Syndrome:
Might this help?

http://canb.us/about
[Android Head-Units] welshblob:
I noticed Alan (?) has already posted on the canbus triple reddit discussion. Looks like the triple is an interesting device and I hope they have more to sell soon.
[Android Head-Units] robertusIT:
I tried but no success, say installed but when you try to open MCU, crash.

A reboot fixed the crash but isn't update MCU section.

Inviato dal mio Nexus 5 utilizzando Tapatalk
[Android Head-Units] miket007:
Carpad for sale

I wasn't sure where to put this....sold my car so don't need any longer....

I have a Carpad 2S NU3001 complete Android unit. Specs are listed below for the unit. Also included are the following items:

AXXESS Technologies GMOS-06 00-05 Cadillac Onstar Harness Adapter

Metra 95-2005B Double DIN Installation Dash Kit for Select 1996-Up Cadillac Vehicles

Metra Axxess ASWC-1 Universal Steering Wheel Control Interface

METRA 40-GM10 - Antenna Adaptors - Aftermarket radio to GM Antenna W/Mini plug

This is a plug and play set up for the Cadillac…

Specifications:

• NU3001 Universal Pure Android CarPad 2S

• Single system: Android 4.4.2. Support upgrade.

• CPU: quad core, ARM A9 processor frequency 1.6GHZ.

• GPU: quad core, ARM A9 processor, graphics accelerator.

• RAM: 2GB.

• ROM: 8GB.

• Touch screen: 7 inch Multi point capacitive touch screen. Light transmittance is greater than 90%.

• Display: HD digital display, 1024*600 resolution.

• GPS module: UBLOX 6M.

• WIFI: 802.11b/g/n.

• Expansion cards: support SD card extension

Thread on the head unit:

http://xdaforums.com/andr...arpad-t2865525

Link to my install thread...

http://www.cadillacforums.com/forums...l#post14075625

I have about $700.00 invested in in this with the interface box, modules and wiring harnesess...

$250.00. plus actual shipping

[IMG="picture"]http://www.cadillacforums.com/forums/attachments/deville-parts-sale/408146d1471193838-carpad-android-audio-system-complete-20150315_133619_w-potter-dr.jpg[/IMG]
[Android Head-Units] deeznutz1977:
Does anyone have a link to a functional version of viper4andriod . I deleted mine and factory reset the head unit
[Android Head-Units] bylmy:
How do I change this file? I tried to use RSexplorer to open the directory "data" , it said I have to root head unit first. How do I root the Eonon GA6163 head unit?
[Android Head-Units] Zaphod-Beeblebrox:
Mask ROM mode

For those that have a NU box that won't flash, one possible solution is to put the box into MASK ROM mode. This sort of unlocks the enand to allow flashing when something has gotten corrupted in the main bootloader section, etc. I have a box that appears to function, but wouldn't take a flash through RKBatchtool, or any other of the RK tools I've tried to flash with.

Find illustrations to get the unit into mask mode has been difficult as all the other instructions I've seen involved shorting out pins on the enand chip, and they've all shown chips with exposed pins. Something our units don't have. I finally toyed around with the board (it's useless to me at this point anyway - so what's the worst that could happen, I fry it?) and found out which pins to short.

On the back side of the circuit board, directly underneath where the enand chip would be, there is a group of resistors. One of the spots is just two solder joints labeled R74. Short those pins while booting and the unit will be in MASK ROM mode.

[IMG="Circuit board"]http://i.imgur.com/MbpFhHz.jpg?1[/IMG]

Unfortunately, my board still won't flash, so I'm assuming the enand is dead. Just hoping this might help somebody else.

I now have two dead NU boxes sitting on my bench. My NR series is my daily driver in my truck and is making it difficult to do software testing for xdAuto. If anyone has a spare NU box they need to get rid of, please let me know. Would greatly help my development efforts.

---------- Post added at 05:24 AM ---------- Previous post was at 05:22 AM ----------

Are you running xdAuto? It includes viper. Should be able to just reflash and it'll reinstall?
[Android Head-Units] deeznutz1977:
I wasn't but I am now thank you
[Android Head-Units] zanix:
I wonder why I didn't think of that... That's a decent workaround
[Android Head-Units] CashMoney474:
Anyone have experience working sending in a unit for warranty repair? Bought my 7in Carpad 3 in December, installed it by January and yesterday it just stopped turning on. Checked voltage at all connections, everything is as it should. Going to proceed with a warranty claim since I can't think of anything else to troubleshoot.

If anyone has any advice, please let me know. I've verified 12v on acc and 12v line. ground is good. Can't look into it anymore without breaking the warranty sticker off. Unit doesn't respond, no lights come on. :crying:
[Android Head-Units] krembuk:
anybody here using carpad 1? carpad 1 is linked through a connector that looks like a firewire to the head unit running WinCE.

I'm just interested to know whether the NU source code in the github contains the driver for that connection. I know the kernel is for RK3188 and I have to port it to RK3066.

Thanks in advance!
[Android Head-Units] Invidiousdemise:
I need the android box for the NU3001 if anyone wants to sell theirs. Also willing to sell the screen portion of my headunit if someone needs it.