yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] Bokomaru:
If the android box isn't receiving the keypresses then it is likely related to something inside the HU. I've only ever worked with the 3001 and 5002, can you open up your unit and see if anything has broken loss or come unplugged? Some pictures of the insides and connections would be cool for the wiki

Edit: What keys are/aren't working?

---------- Post added at 11:51 AM ---------- Previous post was at 11:39 AM ----------

Well they would need to do complete testing to determine what is actually wrong.

I've only heard about the key presses and the USB stuff, hadn't heard these other issues. Does the touchscreen work fine all the time? Any other issues? All of the issues you mention are things that are related to the serial channel that rides 2 pins on the "Firewire" cable. Touchscreen touches, button presses, GPS NEMA info, power state changes all ride across the serial channel.
[Android Head-Units] kwalsh24:
Zero, none notta all key presses do nothing. All key presses were perfectly fine before this replacement box & before I bricked the original box. I did open the HU and there was nothing lose or broken, all connections were tapped in place.

At this rate, I would be better off with a new unit vs sending this one back. If I were to get a new unit it wouldnt be a Newsmy. I'll email Summer one last time to give her an update on the key presses not even being detected in a report log... doubt that it will get me anywhere but guess worth a shot.
[Android Head-Units] Bokomaru:
I don't know how that unit is setup, but didn't you say volume worked? What about the touchscreen?
[Android Head-Units] kwalsh24:
The volume only works on the touchscreen navi bar, the knob doesnt, as it wont detect.

No other issues reside, touchscreen has been working fine, the GPS hasnt been bad lately, it was at the point where I would have to restart the android box to get the GPS signal to detect.

There was an issue with the HU not wanting to turn on after having the key pulled for 30 or so minutes, that issue hasnt come back since I changed the standby from 24hrs to 12hrs.

The laggy HU powerup from a complete shutdown is random, it occurred today actually when I has the android box pulled to configure it on my laptop. Had to pull the power cycle the box to get the screen to turn on....

So im trying to figure out the firewire cable and how it works, does video travel over 4 of the lines and the serial signal travel over 2?
[Android Head-Units] Bokomaru:
I documented the pins in another post somewhere on here. 2 pins are video (using the THine chips), 2 pins are serial, 1 pin is 12v, and the other is ground.

If you have a serial monitor you can tap into the serial pins and log them, I've got a Bus Pirate I have hooked up to them to log.

Edit: Did the "laggy HU powerup" happen when you had the device also hooked to your laptop? That is kind of expected behavior (not ideal though) because the android box is running at a normal state when plugged in via USB (since it is powered) instead of running in standby mode like it would if it was only hooked to the HU power.

Edit2: Can you take pictures of how those HU buttons connect inside the HU? Also the board? I really would suspect they use the same board and connector knowing how companies build products.
[Android Head-Units] kwalsh24:
Hmm nope don't have that lol. My guess is the serial lines work on series? Where both need to be connected in order for them to work?
[Android Head-Units] blacklistedcard:
Do we need to still investigate the libmobiledevice?
[Android Head-Units] Bokomaru:
One pin is TX and one is RX so if it was only half connected you would get some pretty odd results. Like your volume would never adjust since the touchscreen touches get sent from HU->Android and then the command to adjust the volume goes Android->HU
[Android Head-Units] kwalsh24:
Hmm okay so then it's not a FireWire cable connection issue. Its more something inside the head unit then.
[Android Head-Units] Dream Reality Syndrome:
I'm not sure, what does that do? I'm perfectly happy with my setup thus far so I wouldn't wanna mess with it.

Bought Poweramp and realized I can delete songs on the iPod and edit tag info all on a whim, as well as utilize the star rating system. Plus I have music on this iPod both upload thru iTunes and simply as data thru Windows USB mount. Of course, iTunes can't read the music I mounted, but Poweramp reads both partitions! After I set the library directories, of course.

Now the only thing I would want to improve on is Poweramp needing to scan the entire library every time I shut off the car. Seems as though USB is unmounted every time I turn my car key off, and with such an extensive music collection, its annoying waiting for the scan to complete every time I run out of the car for 5 min.

Couple days ago when I was working with Rockbox on Android I was trying to build database files, which would rid the need to scan if Poweramp has a similar feature.
[Android Head-Units] Bokomaru:
Can you take some pics of the inside of the HU?
[Android Head-Units] kwalsh24:
err not currently as the HU is installed in the car, not certain how many more times the plastic dash will allow me to take it apart. I do know I need to make new USB cables for my hub as 2 I made arent working. So if I have time this week to make new & replace ill have to take the dash apart to re-route them dow to the centre console. I can then take the radio apart to take photos.
[Android Head-Units] Bokomaru:
I'm really curious if it's the same board internally and how the front buttons hook up.
[Android Head-Units] htc-rocks:
OK noob question time. Might help other new owners too?

When switching to xdauto am I correct in thinking that flashing Tuatara's rom first is no longer required? We can go straight to xdauto from stock?

So now it's just a case of updating MCU to most recent then flash latest xdauto with RKBatchTool - no messing with partitions?

I don't mind updating the wiki with a guide once I get my head round it! (Unless it's already been written and I've missed it!)
[Android Head-Units] kwalsh24:
That's what i did. Flashed mcu then did direct to xdauto with batchtools
[Android Head-Units] htc-rocks:
OK good. And you don't think that has anything to do with your button issues? I also have the vehicle specific version and it sounds like your having a nightmare with your unit.
[Android Head-Units] kwalsh24:
Nope they weren't working on stock either. I was on xdauto on my original box with no issues
[Android Head-Units] Zaphod-Beeblebrox:
You should be able to flash xdauto.1.1.6c.img with batchtool. Then you will need to flash 1.1.6c2.zip with the TWRP recovery. We did not (and probably will not from here out) create a .img file for c2. Flashing that first .img file will set up all the partitions and recovery. From there out, flashing zips in TWRP is easier. You also do NOT have to wipe /data when flashing unless we specifically say to (ie, if major structural changes happen, then a data wipe might be necessary ... none of that has happened to date)

Have you by chance tried to re-flash your MCU? I've had some occasional weirdness that flashing the MCU has solved. Note that the update utility will not let you flash the same MCU you are running (ie, if you are on v45, you'll need to flash v44, and then re-flash v45, etc). This is a limitation that we need to fix in that utility (including allowing us to search for the MCU files in different directories - I keep all of the MCU's on the SDcard, and have to move each one to the internal root everytime I want to flash).
[Android Head-Units] Grims:
I am having some issues with steering wheel controls. They randomly work on each press, and each time I assign a value to one the number changes a little. I'm guessing the connectors I used is throwing the resistance off.....but was wondering if anyone else has had this issue before I pull it all back out.
[Android Head-Units] Bokomaru:
I have not seen an issue like that but I'm also curious if others have.

How much is the variance? Does it change over time or if you press it 10 times in a row is it always different?
[Android Head-Units] Grims:
I didn't measure the variance but it always seems to be at least 10 off, and different every time I think. Although the buttons do work about 3 out of 10 times.
[Android Head-Units] Dangerous Bob:
Hi All,

I've been keeping an eye on this thread for a while now, and have just replaced my car so its time to get a new HU! I followed the links to purchase but the prices appear to have almost doubled in price from $360 to $710 USD since I last looked. At over $800 it puts them in the same bracket as the Pioneers and Alpines?

tradesolution.hk appears to be selling the same product, but has mixed feedback as a supplier. Does anyone have any experience with them on here or any other suggestions?

Many Thanks.

DB.
[Android Head-Units] kwalsh24:
I have yes. I was on mcu 40, then tried 42 I believe but now on either 44 or 45. Thought that myself that perhaps it was a mcu issue but not change. Even ran that past summer but it never was acknowledged. I'm just curious if there is something different that this Android box isn't designed to see vs the original when it comes to the serial bus?
[Android Head-Units] Dream Reality Syndrome:
Does anyone know how to undefine actions in key editor?
[Android Head-Units] Bokomaru:
All of the software (android and MCU) is the same regardless of the physical HU version. If it's leaving the HU on the serial lines to the Android box then it should be received on there.

I'd try reflashing back to 40 or 41, those have been the most reliable versions I've seen.
[Android Head-Units] iHarry:
Big thanks! It works great.

Now I have 3Gb partition for apps and another 3Gb empty partition I can't understand for what :confused:

I was using xdAuto 1.16. and /data was 1Gb. Now updated to 1.1.6c2.
[Android Head-Units] wacko37:
Bokomaru, i believe your 100% right on this one.

I tried a few other storage devices, i formatted them, renamed, unnamed them but to no avail. But what i did notice was if you removed the device and cause a "unexpected device removal" when you plug it back in, it mounts ok in "settings-storage" and you are able to unmount and remount without any problems.

But when that happens the device is not readable in any explorer apps. So im guessing whatever coding Newsmy has done to mount the device has not run, the only way to read the device is by a reboot which then runs the Newsmy Code to mount the device.
[Android Head-Units] htc-rocks:
Where are you based? I bought mine from exclusivecarauto.com which worked out the cheapest for me because there were no extra taxes for me in the UK.

If you wanted to buy from aliexpress then I've read earlier in the tread that the prices there do go up and down but if you contact the seller (newsmy) then they will actually sell you one at the lower price.
[Android Head-Units] jpapadami:
I am also having this issue. If I assign a SWC button and then reassign it, the value varies by 10, sometimes more, sometimes less. The buttons always work even though sometimes the reaction time isn't the best and lags. I'm thinking maybe that's why sometimes my mute kicks in when I increase the volume to 18. Maybe it's conflicting with the volume up signal value? Also, when I increase the volume, the closer I get to 18-20, the more the reaction time lags. Once I get passed 20, it barely responds. I have to manually (using the volume up/down on the unit) lower the volume under 20 for the SWC buttons to work again.

I've also tried PBMC, but can't get volume up/down to work when holding the SWC button for the life of me. I'm also trying to understand how the read accuracy works in the KeyEditor app. When I play around with it, the SWC buttons sometimes work better when I use the smallest value (i.e 20), but nothing permanent. I'm about to reflash 1.1.6c.img and then update to 1.1.6c2.zip to see if that might help, because I haven't flashed since Tutara's rom, only updated using the zip files.
[Android Head-Units] gohigher123:
hold down the key editor app icon and wipe it to app info , once there you chose clear cache or delete data.
[Android Head-Units] Dream Reality Syndrome:
Thank you sir! I will do this tomorrow!
[Android Head-Units] leonkernan:
The other way is to just open keyeditor, go to the menu and select clear.

See the attached picture
[Android Head-Units] Dream Reality Syndrome:
I was trying to figure out if there was some sort of menu and how to access it

By the by, has anyone installed and successfully used the YouTube background playback module? Took me a cool minute to get it to work and I wanna see what process other ppl underwent
[Android Head-Units] usafle:
I tried installing that Xposed Module a while ago. Never could get it to work so I gave up on it. Glad to know it's working for someone.

Also, my SWC have become "lethargic" as well. I think it's the MCU update because before it worked flawlessly. Now I have to press the same button a few times repeatedly over and over again in order for it to switch songs / raise - lower volume.. etc..etc..
[Android Head-Units] Dream Reality Syndrome:
I'm almost sure there's a simpler process than what I went through, but this is how I got it to work for me

I believe YouTube comes installed as a system app. I'm not sure what version though. Anyway, I used titanium backup to uninstall it. Then I downloaded and installed an old version (10.10.52 specifically) and after a million reboots in between each step, voila.

I doubt the reboots were necessary but I was really trying to get the module to work. And when I finally had it all working, I had titanium backup convert YouTube back to a system app and I lost playback ability. So, I imagine if you can just remove YouTube from system apps, you may be able to get the module to work with any version. I did have it work once with a 10.22.58 at one point.
[Android Head-Units] isthisadagger:
It should be the can signal for the open door. The N5261 displays open doors when the corresponding can signal is found. That is also the moment it switches off if the ignition is off.

1. Yes you can go straight from stock to xdauto. No Tuataras needed.

2. MCU does not HAVE to be the most recent. Sweet spot seems to be v40 and above. Mine came with v43 and is still on v43 with xdauto 1.1.6c2. No messing with partitions necessary.

Imho the rearview box is only needed if you want to connect the original vw camera (there are 2 versions of this camera. For one of them you might need the box. The other should work without.) I have attached an aftermarket rv camera myself. All aftermarket cameras i know work when connected to the n5261.

I chose one that replaces a rear license plate light. So it is always powered on. The HU switches to the video in of the rv cam using the can bus signal for reverse gear. If you don't want it powered on all the time you will have to take the power from the reverse light which would have meant laying a lot more cable as the license plate is in the bumber and the reverse light is in the trunk lid.
[Android Head-Units] htc-rocks:
[MENTION=6898565]isthisadagger[/MENTION]

Wow thanks - think you have single handedly answered every question I have ever asked!!!
[Android Head-Units] Grims:
Ah, I didn't even know it had a menu. I will have to play with that and see if the read accuracy may be my issue.
[Android Head-Units] gohigher123:
Thanks , i didn't now there was a menu :)
[Android Head-Units] leonkernan:
Don't worry, neither did I until I started digging into the code :)
[Android Head-Units] Totoix:
I disabled the navbar, so I can't reach the menu. Is there a way for me to reach the menu?
[Android Head-Units] leonkernan:
I'm pretty sure the only way is to turn the navbar back on to get access to the menu button.
[Android Head-Units] htc-rocks:
Is there no way to map a physical button to menu? Cos I'm sure this won't be the only time not having the soft key will be an issue?
[Android Head-Units] Totoix:
In my previous android HU the menu was placed in the status bar at the very top right. It was acting like a context menu. Isn't it possible to put context menu icon on the status bar?
[Android Head-Units] Bokomaru:
Lol, I didn't know there was a menu in there either until I was looking at the code yesterday.
[Android Head-Units] iHarry:
Now I left only keyboard connected but I have the same situation. After connecting the keyboard working for couple of minutes and then stop. Here is dmesg output
[Android Head-Units] Totoix:
Hello, have you had any chance to try?
[Android Head-Units] skange01:
I too have been monitoring this thread and have read some others posting similar questions. Responses have been this is a market ploy and it will go back on "sale" in a few days or so. Good luck!
[Android Head-Units] Dangerous Bob:
Based in Aus so probably cheaper to get direct. Thanks for the tip I will get in touch with them.

Cheers,

DB
[Android Head-Units] wacko37:
I have a question (surprise surprise) about the intent android.intent.action.KEYCODE_BONOVO_REVERSE does it contain extra data like on/off or 0-1?

I have a variable add setup for this intent but its proving extremely hard to make the variable reliable (reversing while system is booting for one causes it to miss one intent)

As this intent would represent a 12v on or off would it be easy to implement if not already?
[Android Head-Units] sanangel:
any installed this in a volkswagen?? function steering wheel work without CanBus ?
[Android Head-Units] Dream Reality Syndrome:
Earlier I was messaging Summer on FB about screen protectors, and she said that all units are shipped with one. I told her mine never came with one, so she wanted me to ask the forum if this was the case for any of you. Did your guys' units come with a screen protector?
[Android Head-Units] htc-rocks:
Mine came with a plastic film fitted which is probably what she means. It's not a proper screen protecter and will scuff over time.

I've kept mine fitted for now though because it is less reflective than the bare glass.

I'm in the market for a matt screen protector in the long term.
[Android Head-Units] Dream Reality Syndrome:
I figure that's what she was referring to, but I won't consider that a screen protector, especially because my film had a tab sticking out, which didn't allow the film to sit flush with the screen. The film would eventually fall off in a short time! So I'll put you down as a "no" lol

There's a menu button in the nav bar? I was messing around with the nav bar options under settings and I didn't see a box for "menu"

Ultimately I configured Gravity Box to bring up menus by double tapping the home/clock button, leaving long press to open "recent apps"

---------- Post added at 02:53 AM ---------- Previous post was at 02:48 AM ----------

By restart, do you mean shutting your vehicle off then turning it back on? Or are you rebooting the head unit?
[Android Head-Units] iHarry:
I mean turn off and on android box. I tried it on the table at home without head unit and have the same problem.

I think it is hub issue because any device connected directly to the android box work fine after restart.

Is there any way to re-detect USB devices after loading of Android is finished? Like "Scan for hardware changes" in windows.
[Android Head-Units] htc-rocks:
Has anybody with a 5261 had any luck using the "car light backlight" setting to dim the head unit screen when the car headlights are on?

When I tick the box it just dims the screen regardless if the car lights are on or not.

Anybody else seeing this behaviour?

I'm on MCU 44 and latest xdauto...
[Android Head-Units] Bokomaru:
Unfortunately not, we wouldn't have any way to track it. Even if we had a variable to record state we wouldn't be able to know the initial state just like you discovered.

Edit: The state change comes across as a key press from the head unit. Any improvements would have to be made in the MCU code which we don't have access to the source to do.
[Android Head-Units] wacko37:
Thanks for the explanation.

If only we could get source code for mcu, maybe after they release Carpad3 they might give it to us?
[Android Head-Units] NogginBoink:
Hey everyone! I'm about ready to post my installation success report but before I do, I'm looking for a compatible 3G USB dongle. Amazon has several models of the Huawei E303 that offer same-day shipping. Has anyone had success with the E303? I did a search on the thread for 'E303' and got no results.
[Android Head-Units] NutFM:
you need to unconnect "illumi" wire.
[Android Head-Units] Dream Reality Syndrome:
I was having trouble trying to gather information and find reviews on USB dongles compatible with T-Mobile. In the end I purchased their latest n greatest hotspot and it works perfectly using a 7 port hub.
[Android Head-Units] zanix:
Mine had a film on the screen to protect it during shipping, but not a permanent screen protector.
[Android Head-Units] Dream Reality Syndrome:
Alright I'll say that's 3 of us that didn't receive a "screen protector"
[Android Head-Units] Bokomaru:
I've never seen anything other than the plastic cover on them and I've seen a large quantity of the 3001 and 5002. It does a good job though, protecting the screen until the device gets installed.
[Android Head-Units] Dream Reality Syndrome:
Oh yeah I don't doubt that it protects well during shipping. But to leave it on after installation, there's no way it could last too long. Especially in the heat, and if there's dust (I live in the desert) it can't stick to the unit and keep the screen clear. But maybe that's what Newsmy is hoping for? Idk, I'm not making a big deal of it. I just asked Summer if they'd offer protectors in the future, and she responded with "they all ship with screen protectors"
[Android Head-Units] Bokomaru:
I'm in a desert myself, I keep a cloth nearby to wipe the fingerprints off whenever it gets too bad.
[Android Head-Units] Dream Reality Syndrome:
I think I'll adopt your habit!
[Android Head-Units] pawcu:
Same here. I only got that screen protector with the tab that i removed immediately... hmm maybe i should have kept it... I think its still in the box but i doubt it shall be of any use now :(

I am still having issues with the SWC as well. But only for the next and previous buttons. What i noticed however is that they seem to take a while to work at first. Then after some time they start working perfectly. I dont think the issue is related to the MCU as i tried flashing different versions (40, 44 and 46, now back to 40). I think the issue might be related to the launcher I am using. I installed Buzz Launcher OnDrive UI. I think this started happening ever since i started using it. What i am noticing is that the music widget in the embeded menu of the launcher, takes long to load, the same amount of time for the buttons to start working which makes me think that they are somewhat related. I also noticed that somehow i have 3 music widgets installed.... Are you guys experiencing these issues using the OnDrive UI? This weekend i shall try uninstall it or disable it and check again.
[Android Head-Units] Grims:
Changing the accuracy up to 40 fixed mine. The keyeditor app has a menu that isn't very obvious.
[Android Head-Units] Sixstroke:
Quick question!

Does the BT module send and receive?

Thanks
[Android Head-Units] Grims:
I remember reading in this thread a way to wire up the backup camera so you can view it whenever you want with backdraft, but it will only power up when backdraft is running. I can't find it now though. Does anyone have details on that? My camera has bright LEDs so I can't just wire it up to the ignition wire
[Android Head-Units] wacko37:
Mine was the same. Definitely not what I would class as a screen protector.
[Android Head-Units] Dream Reality Syndrome:
Alright I'm having a hard time. I got a self powered USB hub, and connected to it my hotspot, iPod, ssd drive and a USB OBD. The hotspot and iPod mount fine. It seems the ssd won't mount til I physically disconnect it and reconnect it. The OBD seems to work randomly. Almost like it doesn't receive enough power to turn on. If I mess with the physical connection enough it'll EVENTUALLY come on. Anyone got workarounds or similar issues?