yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] earthman6020:
ODBII Interface via bluetooth

Hi!

Sorry if this has been asked already, I just thought i put it out there for someone to try (I have no unit yet).

Does ODBII via bluetooth work using this: https://devzone.parrot.com/boards/5/topics/show/612 workaround posted for the parrot asteroid smart? It seems to be possible to scan for the devices, but not to connect (probably because of the passcode?) The parrot asteroid smart had the same problem, and this seemed to circumvent it ...

Can anyone try? (or has anybody tried this)

edit: typo
[Android Head-Units] quacka:
Where did you get this from? I am looking for one with external mic to save me from opening it up.

Does it sound clear with the external mic plugged in?
[Android Head-Units] dykast:
I have searched and can't find a definitive answer to my question. I have the 4.1 version with the same face as the ones posted in the first thread. Their is a micro-usb port on the front. I know I can connect a USB flash drive through the included USB to Micro-USB adapter and it will show up as a storage device. I would like to bypass the "dongle" and get something like this http://www.amazon.com/Leef-Multi-Use-Android-Tablets-Windows/dp/B00DGNSM1M/ref=cm_cr_pr_product_top

I have seen lots of posts about OTG(On the go) but they all relate to Torque. I am just wondering if this device should work. Thanks
[Android Head-Units] KID52:
It should work fine. It will not work - unit is mini USB, drive is micro USB.

My question though, would be why do you want something sticking out the front when you can use a hidden MicroSD card instead?
[Android Head-Units] KID52:
I installed ADW from an APK and have not had any issues with it, great launcher.
[Android Head-Units] dykast:
I get what your saying. I already have a 32gb Micro SD card in there. I honestly just hate the MicroSD as a "portable" device. I can't tell you how many times I have taken it out of the unit and it flew somewhere out of the slot because of the spring and me sitting their looking for it for 10 minutes.(yeah I am not that smart). The usb stick would be more for just moving music downloaded on a computer to the 32gb MicroSD card I have in there already. But thanks for the reply:) Going to order it.
[Android Head-Units] sciallo:
This keeps coming up, [MENTION=1915855]KID52[/MENTION] Since .23 is instrumental in fixing GPS maybe we should revive links to it, with big bold bad warnings around it not to have it touch the MCU. People have been warned but they do need it.

In fact, maybe links to .68 should disappear since that does brake something every time it's used and no matter how it's used.

Just my two cents...

The little drive you posted has a micro-usb connector, if I'm not wrong the connector on the face is mini-usb...

I plan on using a couple of these http://www.ebay.com/itm/390669391145?ssPageName=STRK:MEWNX:IT&_trksid=p3984.m1439.l2649 In my car plugged into my usb hub to have easy to access usb ports somewhere without necessarily having a usb stick dangling or sticking out (pun) of the unit.
[Android Head-Units] KID52:
Fair enough, but if it's only being used for transferring music, is the cable that much of an inconvenience?

Maybe some sort of WiFi sync would be easier than having to copy from the USB drive to the MicroSD?
[Android Head-Units] KID52:
I agree with removing 2.6.68, I was considering it for a few days.

With regards to the warning, since the 2.6.68 GPS warning is being ignored, I can't see the 2.6.23 warning being followed either.

That even went through my head, but for some reason I posted the opposite of what I was thinking lol. You are correct though, the front port is mini USB, and that drive is micro USB.

Edit: What is worse, is I even wrote my post saying it wouldn't work due to being micro not mini, and then deleted it :( The joys of being tired...

On another note, I wanted to have similar panel mounted USB sockets in my car, but fear my precision rectangular cutting skills are not up to par.
[Android Head-Units] sciallo:
Oh, I might have been 30 seconds too late... Well, it still has the regular usb you can use with the adapter cable...
[Android Head-Units] kschumake83:
The thing is, here at xda, no one reads. Not even big bold underlined bright red text. You could probably even name the file willf@#$%&%messupyourunit.zip and someone will flash it. .23 can make a brick out of your unit, .68 just messes with GPS and its fixable.
[Android Head-Units] dykast:
ACK!!! Saw your post, you are correct! Didn't order it. Thanks for the save!!! 1 Internet rewarded to you my good sir!

Those cables look like a good idea. Just need to think where to mount them in my car. I am in the middle of putting together a new stereo system with new speakers/amp/sub so I can add those to the mix.
[Android Head-Units] kschumake83:
I use Google drive if I need files from my computer or phone to my SD. It is surprisingly quick.
[Android Head-Units] donaldta:
At this point since the .68 update is more prevalent at ruining the GPS, maybe it is better that both .68 and .23 be taken offline together. Or, maybe put them both online and have passwords which signify what it can do. Like for .23 password, "ThisCanBrickMyMPU" and for .68 password "ThisCanBreakMyGPS". That way knowing the password to archive, the user will get the idea of the problems associated with it. The password can be placed on a zip file or even on the download mechanism.

Post #679

I believe someone already tried it. Although I am not sure if it was in this thread or among the others I am subscribed to. However, I can tell you that the problem is different because on the Parrot Asteroid Smart the logic board does not have a MPU. It is one logic board and the they are using a custom Bluetooth Module, Parrot CK5050, to support pairing for both phone/music and other bluetooth devices. The Bluetooth control panel is available in the settings app as it should be. However, in earlier versions of the firmware, you were only able to pair with devices who's code was 0000 but that has been fixed a couple versions back from the current.

However, on ALL of these generic Chinese head units, the Bluetooth module is not connected to the ARM system board but is a part of the MCU board. That board is handling most of the low level events that the Android board is not. So, it is not a direct connection which is why most third-party apps cannot access anything connected to the Bluetooth Module. There is only one Bluetooth device that can be pair though, it is the Landu ODB2 BT adapter which uses a custom B-Scan ODB2 software. I suspect that company has a special arrangement with the manufacture of the head unit, and they know how to use the proprietary channels to communicate with it.

In my opinion, if your sole purpose is using ODB2 then you might consider using a USB ODB2 adapter instead. They have better read throughput and don't use any power while your car isn't running. A good USB ODB2 adapter can read about 160 On-Board Diagnostic (OBD) Parameter IDs (PIDs) per second, where as a good Bluetooth adapter can only read about 80 PIDs/s.

You do not need a OTG cable for this units. The only purpose for an OTG cable is to signal the USB controller that the client USB port should be switched to a host USB port. It is mainly used on Android phones and tablets that only have a client USB port meant to be connected to a computer for syncing. However, since ALL of the ports on this head unit are host USB ports, a OTG cable is unnecessary and may even cause the USB controller to act inappropriately.
[Android Head-Units] sciallo:
Glad you got it in time :)

I plan to put one right on the top left corner of my dashboard, eyesore, but it will keep my wifi stick right by the windshield to get the most range I can get. Sync over wifi will be my choice for getting files there...

Wow, however fast that is, I can't immagine transfering movies that way... Upload, then download through the internet to go 100 feet away...

Point taken....

---------- Post added at 10:52 AM ---------- Previous post was at 10:49 AM ----------

I like that Idea... hide that password in the red warning writing and laugh when people come back to the forum to ask for the password that was in red right by where they clicked to download the file :p
[Android Head-Units] :
Hey,

is it possible to make Tasker (or a similar tool) recognize the press of the next button?

i tried the multimedia keys that i can select in tasker but i had no luck.
[Android Head-Units] donaldta:
Well, you wouldn't have to hide that password anywhere. In fact, it should be made prominent next to the download links. Maybe I'm looking at it with a different perspective. As it is now the older firmware is guarded by KID52 which is fine as long as he is healthy and responsive in this thread. But, should god forbid anything happen to him then access to those firmware is pretty much lost until he returns or is resurrected.

Yes, I do see him removing the links as a "service" to prevent people from ruining their units if they download from other sites or pages that does not include the warning. However, it is clearly an inconvenience for the people whom know about the issues and just want to fix the problem. At least if they were able to download a passworded archive without looking at the relevant information, they would be "encouraged" to read more. At least the software would remain available and the password in itself should be enough of a hint should they gain it from another source.

In all honestly though, fsck anyone whom doesn't take the time to read about the related issues and risks. Ignorance of a select few should not be the deciding factor for why everyone has to wait to gain access to it. Those who do take the time to read and search should be able to have access beyond that of the ones that do not. Treating everyone like they are dumb, stupid, and ignorant isn't a good way to help people.
[Android Head-Units] sciallo:
LOL, that "hiding" was sarchastic thinking along the lines of:

And in complete agreement with al your points, especially:

:) I just can envision the posts

Q: "hey, what's the password for unzipping .23??"

A: "Read right next to the link you downloaded it from, yeah that big a$$ writing in red bold letters that starts with '*warning!*'"
[Android Head-Units] donaldta:
That would be awesome. We'd have a clear way of distinguishing those with aptitude in following instructions and those whom are completely inept. The important part in my opinion is to not block it from those with the intelligence to use the files appropriately.
[Android Head-Units] sciallo:
On a separate note (or two)

1) A moderator wasn't happy with the short name for the wiki page and changed it to Tonghai Create AN-21 U the old shorter one still works but redirects, so I thought I'd make it known and I updated all links from the Generic Android Head Unit wiki page as well.

2) I got a reply to my request for a replacement board from my seller:

Looks like I'm adding at least a month to my wait to have a new car stereo in my car, quest that started in November for me :(

(Unless, any of you failed a "screen strength test" and has a cracked screen unit for sale :) )

Or maybe I should buy a S150 and see if I can brick that one too :P

So for now, while I can't do much testing of this and that, I still can try to gather information and work on those wiki pages.

I still want to clean up the Generic Android Head Unit page and end up with some information and tutorials that are common to all units in that page or subpages linked from there and from the individual unit specific pages.

I can use some help knowing what works for all units, for example do "Boot Logo" and "Boot animation" mods work for all of them?

I guess I'll get together a list of possibilities and ask in other threads too...

Requests (possibly with thread post links) for specific Howtos and tutorials to be publishedon the wiki are welcome.
[Android Head-Units] PsychoMcSatan:
Hmmm... this one is another mystery because now my unit behaves just like TOMMYX2's, and djblaze852002's unit in his video. That is, no sound from Android unless the system music or video app is running. However, up until yesterday it was working all the time, no matter which system app was set to start with boot.

And what wrecked it was a partial system reset caused when I was parked with the radio running, and then starting the engine. The voltage drop(?) caused the screen to go black. It quickly turned back on (where it was, no reboot) but my Android music player lost its sound. I previously had a circuit installed that maintained voltage during engine restarts, but after getting a new battery the other day, I decided I didn't need it anymore.

So what I'm getting at with this post is that I believe that voltage drops might be causing a reset of one of the radio's subsystem (the MCU? part) and things get out of sync with Android. What boggles my mind is that now this odd audio behaviour is stuck even with reboot. Did something get logged somewhere telling the MCU what it thinks Android is doing?

I'm going to try and pull the power for a while and see if that resets it to how it was working before (Android sounds always on), but what about the little reset button. I've never touched it as I haven't left my original .60 system software, but does that just reboot normally if you don't have new software on your microSD card, or does it "reset" any settings?

****************

EDIT: I thought that reset button was used for system upgrades, but just read that it's not. So what does the reset but do?

Thanks,

-PMS
[Android Head-Units] chris.r.r:
For me it's the same, ADW launcher works like a charm...
[Android Head-Units] donaldta:
Are you guys using the free version; ADW.Launcher, or the paid/licensed version; ADWLauncher EX? If the problem is as [MENTION=5558952]tdt038[/MENTION] mentioned in Post #1575, then the problem is actually with the licensed version not the free one.
[Android Head-Units] KID52:
Sorry, should have been more specific. I am using ADW Launcher EX, but installed from an APK, not from the AN-21 U Play Store.
[Android Head-Units] KID52:
Hmm, being resurrected sounds interesting!

Password protecting the files sounds reasonable, saves me having to reply to PMs.

If the warning is there in big, bold red text, and the password backs this up, tough sh*t if you brick your unit. Sometimes you get burned when playing with fire.

One thing I will do is make the password text an image, that way people can't blindly copy and paste. I'm sure there will still be someone who doesn't process the warning, but they they have been given enough chances...
[Android Head-Units] donaldta:
That's interesting. Unless you have a hacked patch copy, it seems to contradict this...

And, although I have done that too with many paid apps (non-patched), for me its going from Android 4.2 - 4.4 on my Nexus 4 and side loading it onto Android 2.3 device (Asteroid Smart & Droid 2) which works fine for me. The license checks are still going to the Google Play. I thought that it may have been something to do with the newer version of Androids or something like that but if you're able to do it with ADW Launcher EX then I'm not so sure anymore.
[Android Head-Units] fcortes626:
ok so my seller resent the update file and i updated and it still doesnt work. the update is just the official .68 update file. I sent him a youtube video showing how my unit is unusable and asked again if he would take care of the shipping charges for his defective unit.
[Android Head-Units] KID52:
The APK was indeed patched, probably the reason why it works.

Edit: Has anyone tried the paid version of Poweramp? The trial is not visible in the Play Store, but the license app is. With the previous suggestions given by [MENTION=5389783]donaldta[/MENTION] it should be possible to download it from the Play Store using Market Helper (I think that was the name). But will the license work?

For those who want 2.6.68 and 2.6.23, the links are live in the main post.
[Android Head-Units] TOMMYX2:
Try http://market.1mobile.com/#

i have the Paid Version,and it woks great for me.
[Android Head-Units] donaldta:
Yes, but like most developers they only include a special library that activates the full copy from the free version. SuperSU and Titanium Backup use similar mechanisms for the Pro versions. You should not have any problems downloading it with Market Helper (not the one from Google Play) though if it still doesn't show up as a package to install then use AppBrain in tandem with Market Helper. Otherwise, just download the free version to your phone then sideload the apk. Then buy the license to gain the full features past the 13 day trial.
[Android Head-Units] chris.r.r:
I use the free version from Play Store...
[Android Head-Units] pgarrity18:
After I flash .23 should I do factory reset again before flashing .62?
[Android Head-Units] donaldta:
Thanks, well at least that explains it.

---------- Post added at 04:25 PM ---------- Previous post was at 04:24 PM ----------

Why not go straight to .70?
[Android Head-Units] pgarrity18:
I prefer the layout of .62. But should I do a factory reset first?

Just flashed .23 and even on .23 my gps is showing no signal. I'm starting to think I am screwed. Everyone STAY AWAY from .68

---------- Post added at 05:35 PM ---------- Previous post was at 05:33 PM ----------

No I can't even restart it. I tried and it is still stuck saying update start. Update end.
[Android Head-Units] kschumake83:
What app are you using to check GPS? Some apps can't see the way our GPS is set up, try Google maps, sygic, or copilot as they are verified working. A factory reset won't hurt either which way though. You didn't mess with the MCU did you? Does all the radio, aux, disk, and other factory apps work?
[Android Head-Units] pgarrity18:
I managed to get it open again. I went through the update process one more time, flashing .23 again. It opened. Then I did a basic restart (not an update with the SD card removed) and it opened no problem. I then used gps test (the one already installed) and it showed signal. Tough to say if the problem is fixed though, because it would work intermittently before as well. Now I am about to flash .62. We will see how the gps does. I will test with your suggested apps as well. Before, the apps were always having trouble locating my truck. Google maps and co-pilot to be specific. And usually when they stopped working, the gps test would say the same.
[Android Head-Units] PsychoMcSatan:
Just fixed my sound issues (exact same as you describe) by disconnecting power for a bit. On next boot it started up the radio and was tuned to 87.9 which is static here, but it did still have my saved stations. I did a long press of 'back' and then started up my N7 music app and sound is back to normal.

So it appears there are some system settings that are kept in memory as long as the radio is connected to the battery. One of them appears to be the radio station you were last dialed in to, but clearly it must also store some sort of sound priority state.

It got me thinking that maybe someone having GPS issues might want to try disconnecting power to see if there is some corrupt GPS setting that is being maintained in system memory.

I didn't try using the reset button, but I'm wondering if that would have the same effect as disconnecting power.
[Android Head-Units] Black6spdZ:
The full .68 or partial? I used the partial upgrade back and forth several times between .62 and .68 and GPS still works fine
[Android Head-Units] donaldta:
There's no such thing as "full" or "partial" updates. That was a convention used by [MENTION=1915855]KID52[/MENTION] when he Frankensteined upgrades together to make "full" packages. All the "full" updates should have been removed by now.
[Android Head-Units] PsychoMcSatan:
I switched my USB WIFI dongle to a D-Link DWA-121 and haven't had a drop since I put it in 4 days ago. The dongle that came with the radio never lasted for more than a day.
[Android Head-Units] sciallo:
If anyone did purchase the above mentioned board, please take a few closeup pics of it before installing it. I have some questions...

Also, if anyone opens their unit for whatever other reason, I'd like to see differences between units... So we don't overcrowd this thread, I had started a hardware specific one...

---------- Post added at 07:24 PM ---------- Previous post was at 07:20 PM ----------

Uhmm, that seems to mean that the non frankensteined version of .68 as it came from the manufacturer doesn't brake GPS? Anyone who still has any of the "Full"/"Partial" files should just get rid of em and re-download firmware...
[Android Head-Units] pgarrity18:
I used the Frankensteined version. I guess that was the problem.

---------- Post added at 08:22 PM ---------- Previous post was at 08:19 PM ----------

Crisis averted. After following the advice from this thread, I too can confirm that flashing .23 and then re flashing a later version. In my case .62. The GPS problem goes away.

On to the next issue.

---------- Post added at 08:27 PM ---------- Previous post was at 08:22 PM ----------

I notice that when I either 1) use llama to automatically start playing power amp when it is open or 2) attempt to use a hard button to switch tracks in poweramp, I get the following...

The song plays for about 3 seconds. Keeps playing but the sound goes silent. I can see the time still elapsing. If I use the hard button to change the track again. I hear sound for another 3 seconds. I have to close the app and restart, after shutting off the llama action if I had it on, in order to make it work again. This occurred on .62 both before and after switching to .23 and back to fix the Frankenstein ed .68 gps issue.

anyone else experience this?
[Android Head-Units] Mancubus99:
Thanks for letting me know. My adapter seems to be fine when it's tethered to my phone but not when it's connected to my home network.
[Android Head-Units] ackyo:
Hi Guys,

recieved and installed my VW version of this headunit, so far Great! but with a couple of small issues, main one is the unit will not power off when the ignition is, spoke with a mate from VW sales he thinks it will need a canbus adapter to get the off signal? anyone here with one of these in a VW experiencing this issue? (searched the thread but couldnt find the answer)
[Android Head-Units] donaldta:
Might check with [MENTION=5492644]chris.r.r[/MENTION] and Post #516.
[Android Head-Units] ackyo:
thanks! grr the search function here is not very good.....

have also emailed the seller for a canbus adaptor
[Android Head-Units] kschumake83:
Thank you, thank you, thank you. It works and works great. I never thought about xposed, and the music does not stop when its on the device. And once again, thank you.
[Android Head-Units] chris.r.r:
Same issue here. I described it in Post #1540.

I contacted [MENTION=5648942]vwpassat3c[/MENTION], the guy who posted the video with the panel keys and steering wheel buttons working in Poweramp a few pages back. He reported that he had the same issues first, but that for him the upgrade from .60 on .62 including a factory reset resolved the issue. Now he reverted back to .60 and it's still working, so he suggested to simply factory reset the unit. I don't know if it helps since I haven't tried it yet - but I hope so. Will try it at the weekend...
[Android Head-Units] donaldta:
I am curious did you verify that the unit is actually an AN-21U with the Mstar786 (cedric) CPU/board? I'm wondering since so many faceplates are being used across the Chinese manufacturers for the actual hardware difference between these units. It is possible that your unit is refusing to update with these files because it is not based on the same hardware? Heck, a new thread was opened this morning discussing a possible new head unit variation with a Samsung Exynos 4412 Quad Core CPU.
[Android Head-Units] PsychoMcSatan:
Another thing to try is disconnecting from the battery for a minute which seems to clear settings stored (and possibly corrupted) in memory. You'll want to cut the constant battery 12V, not just the accessory 12V... or just pull your fuse. For me it fixed funky audio issues.