yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] dunksalot:
I have some thoughts in line with your questions below. Thanks for sharing your thoughts by the way - you wouldn;t share if you didn't care. :D

- Boot time is far from 15 sec. It's more like 25 sec just to get to the app launcher.

Mine is actually slower than that but I have active wallpaper and use a different launcher - am used to it by now. Occasionally I have an Android "starting apps" screen that takes a few minutes to do some sort of cycle.

- Stand by mode is not usable since it seem to only turn screen off. The Bluetooth connection is not interrupted and music streaming apps like TuneIn are not paused.

What do you use Standby Mode for? It sounds like something you would need to keep the power on for an extended period of time thereby draining the battery? Isn't this that "wishlist" item everyone has with every system due to battery drain management?

- Configuring SWC (analog, not CAN bus) is a hassle, it took me a few attempts to actually do it. Either buttons are not recognized, or later mixed up or configuration is not getting saved. The order of buttons while programming seem to affect this, so eventually, with right order, I was able to make them all working, kinda.

Does it work or not work...basically what does "kinda" mean? I do not have a canbus version - mine is generic but I may be getting a new car soon so I am more curious than anything here.

- Switching input source and moving between music tracks using SWC is glitchy. Occasionally instead of going to the next song, the radio is turned on. This is while the current app doesn't change, only the audio does.

What is "SWC"?

- Changing unit specific system settings occasionally causes the unit to reboot.

I've had a couple of random reboots in my 5 months having this unit but that's similar to my Samsung Edge 6+ phone. My Samsung is more refined but that's made in the millions unlike car head units.

- I was using Wase for navigation, pressing navigation button while in Wase causes it to crash. It also crashing if I try to change current audio source using Mode SWC button.

I don't use Waze. You should email Thomas about this it is a very common app.

- A2DP audio quality is subpar. Trying to fix it with EQ makes things even worse. Like, 17kHz slider just increases background high-pitch noice.

Some day someone will develop a fully digital output head unit capable of delivering studio quality audio.

- Screen brightness control is useless. The HU uses max brightness by default and flips it between max and min values with illumination control. There is no way (at least I couldn't find one) to just turn the screen off while keeping unit on. Ironically, current implementation of stand-by mode would do the trick, but it only activates with ignition switch.

I noticed the screen is a bit overly bright at night but did not think much of it. I'll take a closer look into that though.
[Android Head-Units] GaMeR64:
SWC means Steering Wheel Controls.

My illumination switching doenst work that great either. My car has an Auto Light setting that turns the lights on automatically when it gets dark but the illumination on the unit just lives a life on its own. Must be a wrong signal in the CANbus I guess. Because the illumination wire isn't connected anywhere so the signal must come from CANbus.
[Android Head-Units] dunksalot:
That is a future model thing. Disregard. I already asked.
[Android Head-Units] vk34554:
Thanks for your comments, I'll reply in-line.

Well, one of the reasons for me to buy this unit was its fast boot time. I already have a unit that takes 30-40 sec to get to the launcher and a few minutes before you can do anything meaningful with it. Saying that, the InDashNet unit is still faster then MTCD, it's just not as fast as they advertise.

I've seen "starting apps" screen only a few times, usually after I disconnect and reconnect the battery.

Yes, but even one hour option that they have currently could be quite convenient, if they would implement it properly. If I stop by somewhere for a short period of time, like gas station, it's nice to have the unit not shutdown right away. Battery drain doesn't seem to be a concern, at least in my case.

"Kinda" means that it's working but not without occasional problem, like Waze crashing when I change input source, or radio turns on during music track changes. Volume up/down and mute buttons work reliably.

Some one already pointed this out, it's just common abbreviation for steering wheel buttons (controls).

Since I finished messing with settings, I don't get any more reboots so far. Still, I don't think this is a good reason to ignore them. Most likely they indicate bugs in settings app.

Yeah, I probably will. Though I'll contact Otium support since I bought my unit from them. Maybe they have some updates or recommendations.

No need for one, I'm not looking for anything fancy. It's just A2DP output is noticeably worse then in most other Bluetooth devices I had to deal with in the past. Even comparing to the radio or music playback of the same unit the difference is too noticeable.

Yeah, this is matter of personal preference. I like to have an option to just turn screen off, sometimes it gets too distracting even on lower brightness level.

---------- Post added at 05:13 AM ---------- Previous post was at 04:57 AM ----------

I think I found a workaround for Google Play Music issue, when it skips tracks during play back. If you navigate to the album you want to listen, don't just press Play, download it instead. There is an option for this, a round icon with an arrow pointing down to the right from the album name. More often then not it will work and download the album locally, then playback starts just fine, no skipping. Obviously, it's not going to work for their radio stations but for regular music albums and playlists seems to work okay.
[Android Head-Units] iizbor3d:
I'm not sure if anyone noticed, but in the google+ thread Thomas wrote Parrot Bluetooth is under development... Any ideas on how this will work with our units? I hope I won't have to buy a new unit just to get parrot.
[Android Head-Units] GaMeR64:
I just received my 2 NooElec dongles and was excited to try them out. I have bought Wavesink Plus but that doesn't output any audio. The normal stock radio output keeps playing.

Both dongles have this. I checked and Wavesink is tuned to a channel and has enough reception (in the green) but there is no audio output.

Does anyone else had this issue and was there a solution for this?
[Android Head-Units] MAStx:
Just a couple of notes inline with your comments since you are using a unit that looks like it is InDashNet but maybe it does have differences based upon some issues:
[Android Head-Units] samdu:
Yeah, mine doesn't take any more than fifteen seconds to boot, either. Pretty impressed by that, actually.

---------- Post added at 09:26 PM ---------- Previous post was at 09:24 PM ----------

Ditto your comments about the power down situation and Waze. I only wish there were something like an eight hour standby or longer.
[Android Head-Units] vk34554:
I was referring to the steering wheel buttons. My unit looks exactly same as the universal InDashNet unit, volume knob and everything else.

The main board looks identical to one from InDashNet, I posted a picture of it earlier. Though, theoretically it could be that it has some hardware differences, who knows. It is also possible that it has older MCU firmware. Is there a way to check?

I just received reply from Otium support, not much help from them so far, they didn't mention any firmware updates available.
[Android Head-Units] mrphil101:
Looking at posts in threads for other units, there are pictures that have faceplates identical to the indash units, main boards look about the same, just get different components. I would imagine that most or all of these Chinese units have parts bought off of Alibaba. Not like they are designing from scratch. Many commonalities between these units, and I would imagine that is why Thomas, and it appears most other HU "manufacturers" will not release the code for their units, to close of a one size fits all situation.
[Android Head-Units] kwalsh24:
So I just got my unit in and checked the software version... Its on v98 which I don't see posted online?

So far I'm happy once again with Thomas and this unit. Screen is way better than the 8" one ever was! Glad I switched over to the universal unit. Still having the issues with the time being off by an hour... Lets hope that get a fixed!
[Android Head-Units] samdu:
The time issue is baffling.

But since you just got your universal and it's running a more recent version... Does the color control for the physical buttons work for you?
[Android Head-Units] kwalsh24:
They do... Till you reboot lol. Then they reset l. Only seems to do red and green... Blue seems to be white.
[Android Head-Units] samdu:
I'd prefer red. Would match my dash lights. It's been blue since day one. Can't get it to change.
[Android Head-Units] GaMeR64:
Hmm, again a setting that doenst seem to be remembered. I had a talk on the Google + page and other people also have issues where these kind of settings don't seem to have been saved after a reboot.

I have this with Wavesink with my DAB+ adapter. Everytime I reboot the unit I have to select OK to use it.

Thomas, can you fix this because this issue seems to be system wide.
[Android Head-Units] dunksalot:
Thomas told me that he is rarely on XDA but is on the InDashNet Google+ page almost daily. He primarily follows the Excel sheet on there for fixes. So for your best chance of seeing fixes quickly please add anything you come across to the Google+ bugs doc and I'd send Thomas an email (with a detailed description) indicating you added it.
[Android Head-Units] car_dude_123:
Mine just drained my new car battery. Returning it to Amazon.
[Android Head-Units] dunksalot:
Otium, right?
[Android Head-Units] car_dude_123:
Yup.
[Android Head-Units] car_dude_123:
Got my 2GB Joying double din device and it's simply brilliant. Software not as polished as 1GB version, but everything works well and it's stable. It even uses internal device battery to make boot up 1s if you leave car for just a few minutes. Let's hope it doesn't kill my new car battery, but so far so good.
[Android Head-Units] GaMeR64:
How is the normal boot speed/time?

And how does Bluetooth calling work? Any static? Or crisp and clear sound?
[Android Head-Units] vk34554:
Well, after using MTCD unit for a few weeks I'm back to my Otium unit.

It has its quirks, but it's so much more responsive that I think this is worth the hassle. Most issues I have with it are minor, I can live with them.

I'm getting responses from Otium support, some of them are helpful. :) For instance, 15 sec boot time is indeed a fact, but only on clean unit. Running update and getting most up-to-date apps from Google Play increases boot time to 20 seconds, adding more apps makes it more slow. Well, I guess this is reasonable. They also suggested to use Shortcuts app to control screen brightness, and indeed, it's quite convenient. There is also screensaver mode that turns screen off and shows only time. I put the shortcut activation button right next to the volume knob and it doesn't interfere with running app controls in most cases.

Current firmware version is R0095, they promised to send R0101 later, hopefully some stuff is addressed there.

So, I'm keeping my init.

Btw, KernelAdiutor identifies it as InDashNet, just as another confirmation that Otium units are actually InDashNet.
[Android Head-Units] xdamember2:
I'm expecting my 2GB Joying 7" 2DIN on Monday. The In Dash has at least one problem that I don't foresee being fixed such as occasionally I have to reset it because there isn't any raster. And after every reset settings get lost. I can't ask to return it because I opened it and wired the antenna / amplifier power output to the accessory power input. Seeking the next FM station works so much better when the antenna amp is receiving power. I've turned into a radio junkie, I've been buying the latest and greatest every 2 months. The technology has come a long way since the Asteroid.
[Android Head-Units] GaMeR64:
Found the original IndieGogo campaign which had some interesting quotes.. I can't help crossing my mind the last days that it all just seems it was just to sell some radios because a lot of quotes from the campaign are just not being done.

- There doenst seem to be fixed much in the motherboard design part (in the IG campaign video). Because why in the world (and after 4 years) the Bluetooth troubles in all Chinese head units are still there. If you design your boards In-house, these problems would have to be dealt with after the first batch that was released. They just seems to be assembled as every other Head Unit with all the same parts except the CPU board.

- The key feature of the unit was it's Open-source software. Without that it's just the same as any other Android headunit. And now it seems the MCU is all closed source. Which means you will never get the possibility to do "whatever you want" and make the unit better. So what can we actually do more with this unit then with any other Chinese unit?

Really doubting if this ever going to happen (and should have been so from day 1 and not promise people stuff and then never deliver):

And it is starting to piss me off that emails don't get answered and problems don't seem to get fixed. Since the day I received my unit the SWC didn't work. I think I have sent 6 emails about this (and the other problems) and maybe half of the emails get answered (the latest emails weren't answered at all). And like most emails to any Chinese seller. If you ask a few questions in 1 email maybe half gets partly answered. So annoying...

It is starting to look that easy answerable questions get answered (like the WiFi point question on the G+ page) but a simple question about a fix to use Bluetooth in a normal way isn't. If the questions are "too difficult" it seems they just look the other way and hope we forget about it.

I really had good hope for this Head Unit but except for a speedier processor and a little more RAM it just doesn't seem to get much better then this...

And what pissed me off even more was that they were "very busy" with developing new products?!?!? What? Seriously? Maybe it's about time you start to make your original unit "usable"!!

And yes, I know I bought a Chinese head unit. So I should have known. But how hard could this be when you are "in this business for multiple years"...
[Android Head-Units] kwalsh24:
All the Chinese want to do is move product and make money in any way possible. So losing and deceiving the customer tends to be the way. In happy with my new unit so far. The time thing is really annoying tho and I just done get how it hasn't been fixed. Other then that I likely don't stress my system out as much as others so maybe that's why I am happy with it. Was it worth all the money? Likely not. However at the time when I purchased it there was nothing else like it
[Android Head-Units] t.idn:
I am not going to have any culture debate here. You will say WTF when the P** BT module asked for 2K+ MOQ or unit price close to $100.

Please state your issues, car info and order id in detail to the email indashnet(at)gmail.com, we will double check what's going on and what we can do for you. Thanks.
[Android Head-Units] j0bro:
My issue is that there is still not a hint of any source code and/or SDK being provided. It would be no more than fair to fulfill your promise on this.
[Android Head-Units] kwalsh24:
Yeah would be awesome if this unit would just fully to open aource as indash would benefit from it in the end as they would have people allover the world contributing in making this unit truly shine. Just a shame its not viewed like that as I love my unit its far better then the last 3 I've owned and would surpass many on the market if it was open source and tweaked by the every day user
[Android Head-Units] GaMeR64:
I will not say WTF (ever) if this a choice for quality. And i will say * Thumbs Up* for this. Low quality parts will cause irritation if it doesn't do what a user expects. High quality parts let's a user enjoy its product more. Also low quality parts will raise more (support) questions which will cost time (which isn't going to generate money). The less problems to solve and questions to answer will result in spending more time on innovation and bringing the quality to a higher level.

So high quality parts + keeping people updated on what's happening = A very happy userbase where people will tell other people: I know a good unit for that! If a product is really good its users will sell it for you.

We are all here to help because we believe in this. Otherwise we wouldn't be here investing our time, money and effort in getting your radio better (which will make us and any future buyer happy). If we help each other (the users helping Thomas, Thomas helping the users) we all win here.

Please try to keep us informed about what's happening and what is coming for us. Together we can really make this radio THE BEST ONE!
[Android Head-Units] swyner:
Ya, I am really concerned about the level of customer support with these guys. I was told today to order the Audi A3 unit but put in my notes it's for Audi TT as they are making that model, just have not updated website. I am fairly sure this is another Chinese company simply based on my communications with them. It's similar to many of the companies like Joying, Pumpkin, etc where you send an email one day, it takes another for them to respond then it doesn't effectively answer your question so you have to respond, wait another day, etc.

I just wish a company would develop a high end Android head with serious R&D on audio quality (FM chip, Amp chip) or borrow from the name brand units. Invest time in making it start up in seconds (MCU development) and get the damn hardware optimized for the Android software. I know Parrot, Clarion, Blaupunkt and Rydeen all had Universal Android head units with exceptional audio quality (6V preout on parrot asteroid) and have many options for "sleep" (up to a week on Blaupunkt). They all ran on Android 2.3 which is now outdated but man, it worked very well as a CAR STEREO first. Anyway, I am ranting (LOL) but come on. There is a market out there for those that want name brand audio quality with Android OS and car specific fascia. Maybe I should start a company?? LOL
[Android Head-Units] j0bro:
Oh it was clear to me that it's a Chinese startup; started from an Indiegogo campaign, very sparse info on blog/website, no advertising. The thing is though that this type of initiatives can make quick progression when they use their community well and I think they have the potential. All units listed on their website are the same one, the only difference are the face plates, which are borrowed from many other existing models. So the only thing they need to develop is essentially, the motherboard and software support. The SoC + GPU are quite capable so as I said lots of potential and Android can be customized to whatever they need. I worked in the automotive navigation industry for 4 years and usually, the hardware components that are chosen for most mid to high end systems perform sh*tty to say the least.

In-Dash.net is a project by Mind Bridge, Shenzhen, China run by Thomas Chen and Sheng Hu Chai, as listed on their current Indiegogo page (December 2015)

In an earlier campaign (September 2013), they seemed to have easily reached their goal of getting $10,000. That time Thomas Chen (architect) teamed up with Shun Fang (product manager). The unit had an ARM Cortex A8 SoC with a Mali-400 GPU and ran Android 4.0.

The 2015 campaign failed at getting enough backers, where the product was placed as an 'Open Source infotainment system'. The SoC of the current model is an Allwinner A83T octa-core (ARM Cortex A7 + PowerVR SGX544 GPU). If they release a good software basis (Android 5.1.x, rooted hopefully) it could be a very competetive unit.

I hope I can get a reply on my questions, I would like to build one into my Kia Sorento which accepts a standard 2-DIN model.

---------- Post added at 10:58 PM ---------- Previous post was at 10:15 PM ----------

Aha, found a review of someone who bought another type of head unit (Pumpkin Android 4.4 based), but also for the Kia Sorento. From the small image on the in-dash-net product page it seems the face plate used on these units are identical. So yeah, they only put in different electronics and software.
[Android Head-Units] rubenjavier:
I've always contacted Thomas using indashnet@gmail.com, thats how I've been able to get all the answers and info so far that are published and updated on the first two threads. Since its a Chinese startup based in China and english its not its first language, I always try to keep the questions short and to the point, and the answers usually take sometime because of different timezones.

I'm still waiting for some answers about new CANBUS apks to add more models, the precise list of FM radio chips available to choose from, and the lists of WiFi dongles that are tested so far.

Maybe its time to show InDashNet how the interest is rising for the units here on XDA and get the 5.1.1 source tree released soon just like the 4.4.4

Note: to those people asking for model specific faceplates, I think like the other OEM Head Units, they just use the faceplates availables in China and can be bought trough aliexpress or taobao (taobao site is completely in chinese, I had bought car pieces there that are not available on aliexpress using the web spreenow wich is in english)
[Android Head-Units] rubenjavier:
First post updated with more pictures from the actual hardware, so nobody has to fish for the right post, credits goes to CompletelyNumb, also added a link to touchpt12 video of the 5.1.1 Lollipop moded image with a working Playstore and Nova Launcher
[Android Head-Units] CompletelyNumb:
Tried flashing the 5.1.1 image with working playstore and it failed every attempt. I'm not certain what the issue is, but it's been proven dozens of times now that I am unable to flash any image altered with dragonface, whether by me or now by someone else. Thomas' images all flash no problem. Very frustrating.
[Android Head-Units] touchpt12:
When flashing the ROM, you will see the progress bar get half way and then display the CODE1 error. It will seemingly stall but it should progress until the end with a CARD OK notification. At that point, you can remove the MicroSD and reboot your head-unit. Let me know if this works. I am still trying to tweak the ROM.
[Android Head-Units] LIx2NG:
Hi Ruben,

Based on my recent discussion with them, CAN support will be available as a "premium addon". But this is not a firm decision yet and the features are to be defined, as their priority is 5.1.1 release right now. I shall be able to give you (and the forum) more information later (yeah I'm sort of an "insider").

Model-specific units are more than changes of faceplates; the backplain PCB and wiring are customized to fit the factory plugs to enable drop-in replacement. And I don't think they are sourcing from Ali/Taobo because plastic modeling factories/workshops are abundant in Shenzhen area.

Cheers,

LIx2NG