yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] kwalsh24:
Its apple music on an android platform.... Diagnostic issue solved hah ?

---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------

I too am curious as to what this issue is... I just thought I was missing something with the new firmware that I haven't played with yet.

Question tho, how does the gps sound leveling work? Is there now an option in the settings to adjust this manually?
[Android Head-Units] swyner:
LMAO. I was waiting for someone to say that!!!

---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------

There is a setting now in VIM Preferences. You can adjust it here only (ie it's not dynamic with volume control) and set it to Mix with Max volume (or level 1-4). I find Mix Max works fine at all volume levels and road noise.
[Android Head-Units] kwalsh24:
Hmm awesome. I found that on the old firmware that the gps sounds were crazy loud if you have nothing else playing. As soon as soon as I turned on the aux input the gps sound was cut in half and actually the volume was inconsistent. One time I could hear it OK the next boot up not at at... Hopefully with the change it works better. That was the only thing I didn't like about the unit. Other then that I was extremely happy with the overall performance minus the screen flicker.

---------- Post added at 08:55 PM ---------- Previous post was at 08:55 PM ----------

I couldn't help myself... I'm anti-mac so it was really hard not to pass up hah
[Android Head-Units] CompletelyNumb:
For those of us without the developer edition, what do we need to connect via USB to do updates? I notice in the pictures the devs got a separate pin cable for the back that had a USB/ADB label.

Do I connect through the mini USB port in the front? Or do I need to get another type of cable from ebay for this?
[Android Head-Units] swyner:
There should have been a blue usb female cable and the same rca type cable as the developer edition. I forget what they are labelled but the rca cable is purple and usb is blue. They both plug into the back of the unit. Again I followed the same instructions from the google drive PDFs that are actually labelled "developer edition". Nothing is different in terms of plugs and how you upgrade the firmware.

Edit: use the "Developer Guide" (link is on the Google+ community) and go to section 4. System Reflash and it describes exactly how to update. Like I said, no difference between "Developer Edition" and OEM fascia models like ours. The small purple RCA looking plug is called UBOOT. You must plug in the male side with the wires connected (like a force ground). Then connect USB into the female USB SLAVE plug (blue) and connect that to your computer. With those connections, and the Phoenix Suite software on your PC, proper drivers installed, you should be good to go.

The biggest pain were getting the right drivers but I posted a link I used to do that (and others have had success). Next is the UBOOT plug is VERY short and I was able to JUST make it reach glove box. That way I can put the male side in and connect USB Slave without removing my unit.

Hope this helps
[Android Head-Units] swyner:
Hey guys...looks like Thomas uploaded new firmware to address the back button issue with Radio App. I haven't downloaded or tried it but it's there on Google Drive.
[Android Head-Units] swyner:
Installed most recent firmware and back button is fixed!!!!!!! Also I noticed radio and other music app mixing is fixed too!! No need to close radio app out (which only works with soft close button on radio as expected) as for example tunein radio starts playing and radio somehow mutes. As soon as I pause tunein radio the Radio starts playing. This is getting so much better each time guys.
[Android Head-Units] kwalsh24:
Awesome stuff. My replacement board was sent out Friday so I should be back in the game this week hopefully !
[Android Head-Units] j0bro:
Hey swyner, where exactly is this update you mentioned? I received no updates in the Google Drive folder. Has it been pulled perhaps?

Edit: Confirmed, I saw in my Google Drive client's activity log that the files have been pulled.
[Android Head-Units] swyner:
There is a new 79_L now that replaced the 78. Not sure what changed or why. I guess I will download and see!!
[Android Head-Units] swyner:
Ok so I have emailed Thomas because not sure what is going on. The 78 firmware was working perfect in terms of back button and sound mixing. When radio app was playing and I start say tunein radio the radio app does NOT close but mutes and let's the sound of the tunein radio to play perfectly. When I hit pause or stop the radio would play again. To some this may not be ideal but for me this is perfect. I really only listen to radio and some other music streaming app so when I start one then the other this "mixing" behaviour is perfect.

Then 078 firmware was taken down and replaced with 079. I installed 079 and the back button is still fixed but the music mixing is totally screwed up. Now, if I am listening to radio and ANYTHING mixes with sound (GPS, notification, other music app) the radio app closes out. I have to relaunch the radio app every time. This is not good for anyone!!! Lol

In both firmware the auto restart app function is gone when cold boot. In previous firmware the last app I had in the forefront loaded automatically upon cold boot. This held true for radio app if it was on my screen when shut down. I have been asking Thomas to make it so the last AUDIO app to be playing no matter if in foreground or not should auto load on cold boot. So I think he went backwards here.

Hopefully I will get some response from Thomas soon.

Edit: Thomas just emailed and said there will be a fix for the radio shut down issue in 079 tomorrow.
[Android Head-Units] kwalsh24:
In really liking the support and progress so far with Thomas and this radio! So far its far better then the huifei and the newsmy unit I had. Great job Thomas and minions of!

Now if only I could get a discount on a second unit it would buy one for my truck lol. Ill likely just get a cheaper android unit for it as it won't be my daily driver, unless I lose my vw tdi due to the emission scandal then it may lol
[Android Head-Units] swyner:
Ok so now firmware 79A is posted. Sound mixing is fixed. A couple of observations

1) the radio app loads very quickly after cold boot BUT only with the stock launcher.

2) audio mixing works like this. If you have radio on you have to close it with the soft button bottom right of radio app. Then open other music source. If you open other music source while radio is playing NO sound will come out of other music source (ie radio continues to take priority). It would be nice if it auto switched audio.

3) while in other audio source and you open radio app, the audio source stops audio and Radio takes priority. This is nice. This is how it should work in reverse when opening audio source while radio is playing.

Overall much better now and a step in the right direction.
[Android Head-Units] splxtreme:
SQ

What is the sound quality like compared to a normal car radio?
[Android Head-Units] swyner:
So I want to try installing Xposed on this. The issue I am having is with flashing the xposed*.zip from this forum http://xdaforums.com/showthread.php?t=3034811

Is there an easy way to install this as everytime I try with the "Update" apk from InDash I get error. Does anyone know if we have ARM or ARM64?

---------- Post added at 06:54 PM ---------- Previous post was at 06:50 PM ----------

I cannot comment from a pure OEM to InDash swap using the built in amp of the InDash unit. I am running RCA out to DSP then to amps. The sound I get is on par with how I had my OEM stereo connected in a similar fashion. There is a bit of feedback noise from the RCAs....not sure if this is a true hardware issue (2v preout DAC on the InDash) but it's likely because I never had noise this bad in any other unit. Perhaps it's a grounding issue but again, never had an issue with other installs (from name brand to Dynavin).
[Android Head-Units] samdu:
The sound quality is better than the stock Bose system in my Miata. Outside of that, I couldn't say.

---------- Post added at 03:51 PM ---------- Previous post was at 03:39 PM ----------

I just sent a support request to Automatic, but figured I'd toss this out here as well. I have an Automatic OBDII adapter that I was using with my phone prior to getting the In-Dash unit. It connects to the OBDII port in the car and communicates with Android via Bluetooth. The problem I'm running into is with the way Bluetooth is implemented on the head unit (I believe). If you look at your settings in Android, you'll see that Bluetooth is disabled. And there's no way to turn it on. I believe this to be because the Bluetooth module is, for lack of a better term, "external" on the In-Dash. So it's kind of controlled separately from the OS (one indication of this is that my phone tends to pair with the unit before Android is finished booting). Anyway, the Automatic adapter/app sees that Bluetooth is disabled at the OS level, so it won't pair or communicate with the unit. Anyone else have an Automatic adapter and find a way to make it work?
[Android Head-Units] swyner:
I have seen this behavior in many Android Headunits. The bluetooth "module" in the InDash is for phone connection only.....it's likely not able to act as Bluetooth module for connecting anything else, hence why there are no settings or bluetooth settings are greyed out. This is something we can ask Thomas directly as I am not sure if it's a hardware limitation or software.
[Android Head-Units] Nogsmoke:
I got one of these units and installed it over the weekend. Pretty pleased overall, I've only had a few issues.

The subwoofer volume is super low, even with my amp turned all the way up. I thought that maybe my amp was expecting L and R channels, so I got a Y splitter, and no difference. Has anyone else run into this and fixed it? Connecting the RCA to one plug behaved the same way.

Another strange thing is that every time I change radio stations my power antenna starts going down then back up.
[Android Head-Units] adfurgerson:
Just a wild idea, but you could try side loading different settings apks to see if one will work. I had success doing that with Amazon Fire stick, stock it would only pair with the stoopid remote and a couple joysticks. After finding an apk that didn't force close I was able to pair with Bluetooth keyboard.
[Android Head-Units] dunksalot:
Check your subwoofer output gain. You may need to adjust that up if it's a new sub amp. I have the same Y-splitter set-up and I thought originally that I blew the amp only to realize the factory gain was set all the way down and muted. Considering you want the radio to run as cool as possible and your amp is going to produce better sound than the head unit, you will want to set your gains slightly higher than normal (my preference at least.)

Your power antenna thing is strange. My antenna is always up but as someone who has read every page of this thread I can say that is a new issue to add to the list.
[Android Head-Units] phatass_dk:
Hi guys,

Newsmy unit owner here. After having read the last 57 pages as well as all other info I could find I am pretty certain that I would have to invest in this fine unit.

One question though, would I be able to install ViPER4Android on it somehow?

Cheers,

Peter
[Android Head-Units] rubenjavier:
Hey guys, there is a new firmware version R0079_B on the google folder, but no release notes... I'll try it today

Also, does anyone is having bad WiFi signal with your phones Hotspots?, I need to take the unit out of the dashboard to get a signal from my phone... too much metal on the car? where do you think that I could connect an antena tho help the internal WiFi from the Unit to pick my phone always?

Cheers
[Android Head-Units] CompletelyNumb:
Turns out if you install the wrong version of Play Services it will brick your HU.

I'll wait for the experts to figure it out.
[Android Head-Units] rubenjavier:
email Thomas with that issue indicating your car brand, model, year... maybe a change in some advance settings is needed to select a specific CAN BUS model (other HeadUnits work like this and they just send it to you pre-setted to your model), or maybe he still need to fix things
[Android Head-Units] rubenjavier:
wich version bricked the HU? to list it on the info post
[Android Head-Units] touchpt12:
All the latest Google Play Services (ARM) stop upon launch. I will test with some previous versions to see if I can find a proper fit.
[Android Head-Units] rubenjavier:
ok, I removed the links to the GooglePlay store apks from the resources post for the time being

...maybe what is needed is one of the gapps packages

you can get them here

http://opengapps.org/?api=5.1

but this are zips to be falshed from a recovery, (I use them with CyanogenMod all the time)

or maybe with some patience, unziped and copied on the SDcard that already have the lollipop image before installing it
[Android Head-Units] swyner:
Wow, little bit of a lull here guys...not much movement from Thomas?? Hate to say it but seems like it's a bit scattered and unorganized...anyone actually talk to Thomas directly and get some firm timelines around 5.1.1 official release? Anyone else have an Octacore unit?
[Android Head-Units] touchpt12:
Thomas did provide Lollipop. We are trying to get certain things working properly (i.e. Play Store/Services). I will reach out to Thomas to see if there are any further developments.
[Android Head-Units] swyner:
Sounds good. I guess Thomas is feeding the prelim/beta version of the 5.1.1 so totally understand some of the work that still needs to be done. For others that might be deciding if this unit is "right for me" are there any videos of the new Lollipop start up time other than the one posted by In Dash Net? From what I can tell in this thread, only one user actually has a unit and working on updating to Lollipop...any others out there?
[Android Head-Units] CompletelyNumb:
It's about 15 seconds for me. |i didn't bother to make a video since one existed.

Pet peeve: hitting back turns off the radio. Need to find a way to make persistent radio until I turn it off.
[Android Head-Units] swyner:
Are you using a canbus module? If so what functions work?
[Android Head-Units] CompletelyNumb:
CANBUS stopped working with this update. Worked fine in KitKat, except that image was all funky for me and I didnt test it heavily.
[Android Head-Units] swyner:
Thanks. Obviously very unpolished experience so far. To be expected with new Lollipop I guess. How is radio reception?
[Android Head-Units] CompletelyNumb:
So far, no worse than my stock HU. I haven't brought it far enough out of the city to test though.

WiFi dongle works good, I get 3/4 bars of internet in my truck parked outside. R7000 router inside the house.
[Android Head-Units] swyner:
Ya, I see you are in Calgary (I am near Toronto but don't hate me LOL). Would love a real review of this if you get a chance, I guess once you work through the kinks....They don't make an Audi TT version yet (but an A3) but say it could be done for May. I am trying real hard to see if this one is right for me given I am fairly picky about those factors I mentioned (Start up, sound quality, FM radio quality). Keep us posted bud!
[Android Head-Units] touchpt12:
Got a message from Thomas regarding the lack of Google Playstore/Services. For now it seems we will need to fend for ourselves.

I managed to get a dump of the Lollipop image. Going to see if I can extract the system files and compile them to create a custom ROM.

Wish me luck...
[Android Head-Units] CadillacMike:
i too would like a full review. Thinking about these if I get a Jeep
[Android Head-Units] swyner:
Wow....so far not that impressed with some of the interactions people are having with Thomas. This doesn't set a great example of how customers will be dealt with in the future. Maybe I am overreacting and maybe since 5.1.1 isn't officially out yet from them so it's ok but wow. Hopefully we will see some positive results in the VERY near future.
[Android Head-Units] rubenjavier:
When you say that you got a dump of the lollipop image, you mean the .img from Thomas or did you got a source tree for the testing version like the one that exists for the stable kitkat?

.-if its the img and you get a way to repack it, plase share how

.-if its the source tree, please share the link

Im thinking of unpacking the image of one of the HuiFei rk3188 units (got one from eonon) to extract the bootanimations of the different car manufacturers to add them to the lollipop image

About the CAN BUS, Im going to contact Thomas again, last time he told me that he would tell me something this week about my new CAN BUS integration (Peugeot its not the original car list), also I asked about the Audi, lest see if he got something new on that front
[Android Head-Units] touchpt12:
I found some tools online and managed to get a dump of the Lollipop ROM Thomas shared. I extracted the system.img and unpacked it. The following would need to be added to "system\priv-app"

- GmsCore.apk

- GoogleServicesFramework.apk

- GoogleLoginService.apk

- Phonesky.apk

I will report back if it works after I recompile the image.
[Android Head-Units] rubenjavier:
That's great!

I hope the repacking goes well, I just mailed Thomas again to get instructions about the repacking just in case, since Dragonface doesnt work for this image, mostly for the differences in the default build.prop and script.bin files for this HeadUnit for what I can see.

I you can, share the link to the tools and some indications, the O.S. used doesnt matter

Im basically just waiting for confirmation on my CAN BUS working and the source release to get one of this, as a community, I think we can also help to make it better besides the customizations

(asked again about the list of radio chips options for those interested)

Thanks again, as always
[Android Head-Units] Nogsmoke:
Same amp as the old setup, it drives my other speakers as well and they're all fine. I turned the input sensitivity all the way up, and still very little from the sub.
[Android Head-Units] swyner:
Wow, just installed 79A after 78 was removed. Now there is a 79B! Ya, last few (78, 79 and 79A) have no change log but from what I can tell, nothing significant except BACK hard button no longer closes the Radio App. I will ask Thomas for a proper change log.

As for bad WiFi....I always get full bars strong signal to my android hotspot phone in glove box. sometimes it does not connect but I believe that's a phone issue, not the InDash

---------- Post added at 05:20 PM ---------- Previous post was at 05:02 PM ----------

Welcome bud!! Ya, the unit runs really well and the support is good too. Each firmware gets better so good choice with this unit. As for ViPER4Android....yes, I had it working but was not easy to install...you have to have Root, Busy Box installed then change some file location in order to properly install the driver. Once all that was done it worked VERY well for ANDROID ONLY apps....ie it would not work for regular FM radio. I uninstalled it because in my setup, I am running RCA out to DSP then to amps. I did not need to equalize or tweak anything as I do that on my DSP.
[Android Head-Units] splxtreme:
what is Thomas's email? I'm looking to see if this will be offered on Amazon. I have a gift card and this would be the perfect present to myself :)
[Android Head-Units] swyner:
Indashnet@gmail.com
[Android Head-Units] splxtreme:
What DSP are you using?
[Android Head-Units] swyner:
Alpine PXA-H800. Works awesome. The only limitation we have is the subpar DAC audio board used in the InDash (and every other android unit). It's only 2V which means it's more prone to having floor noise which is usually compensated with higher output voltage (like 4 or 5 volts). So the old saying garbage in garbage out applies here a bit. I am able to tune the system very well and sounds like high quality audiophile system.

On a related note Thomas and I chatted a bit about this and he may eventually include a great quality DAC with 4V output in the future. Not sure if we can upgrade the current board or if it will be a new unit.
[Android Head-Units] splxtreme:
That would be awesome! Thanks for the info.
[Android Head-Units] phatass_dk:
Thanks mate,

I already feel like a part of you In-Dash.net pioneers as I have read your struggles and concerns throughout the thread. :)

Thanks for the information on ViPER4Android. I am happy to hear that it is possible to install.

I have read guides for the 'Busy Box'-install you mention and it seems relatively straightforward.

I am still awaiting a response from Thomas regarding CANbus support for the VW Polo 6C/Golf VII (2013+ GTI) and if he comes through with that I'll join you guys on this adventure.

Another question - Any of you have newer VWs where the ABS TPMS system has to be reset from the stock radio? I still haven't found a solution on how to do this from any of the Android head units out there.

/Peter
[Android Head-Units] swyner:
There are others on this forum with VW Golfs...just not sure what year/model so hopefully they chime in.

Just a note about InDash and OEM Canbus features.....there have been some issues with the canbox for some Audi and VW users...I basically could not use mine as it was causing wiring issues, no SWC, etc. Anyway, Thomas is very aware of this but is focusing his efforts on the software performance for ALL InDash units first (rightfully so) then will work on specific Canbus issues. I have asked him to implement as many TWO WAY canbus features as possible as other Android units have this. This includes: SWC, info in DIS (MFD for VW) including RDS info, song info, Bluetooth caller ID, etc and then info from car on InDash unit (AC, tire pressure, other info from OBD connection).
[Android Head-Units] kwalsh24:
Ill chime in in regards to the canbus, I too experienced the same issues as swyner mentioned and have replaced the Canbus box with a axxess box (haven't tested it yet tho as my radio is down) in my 2009 jetta / golf sportwagen... from my past experiences with external canbus boxes provided with android units... They've all given me the same issues with not retaining accessory power, not giving 2 way communication to those with the mfd displays. I don't have fancy climate controls so can't speak on that subject...

Imo if you want some features to remain you may need to go an alternate route for the canbus box... Its really hard to say if Thomas can program the box itself or if its don't by an external group.
[Android Head-Units] j0bro:
Did some DIY-ing today again and what do you know: the SWC work! I used my portable scope to detect when I got some signal from the car's remote interface and when I found it I installed a wire from the signal to the Key-2 5V input of the OctaCore, no other connections (so using common ground, just like one of you guys mentioned earlier). I then could enter the VIS/SWC screen and hold+click the desired buttons and see them being highlighted blue. Everything works OK now, yay!

[MENTION=2251099]swyner[/MENTION]: I reinstalled the SWC adapter that used to be in for my previous Pioneer unit and sure enough, the power wiring is now fixed (Constant 12V is now connected instead of ACC only). I now see that the unit only shuts down whenever I pull the key, instead of switching from ACC to OFF and thereby leaving the key in. Also, the unit springs back to life almost instantly after turning the ignition on again, and app settings are now saved. I guess this will also fix my Android cache problems (Optimizing apps x of y...)

I also briefly checked the USB camera that came with my unit, it seems to belong to the Movon app (MDAS) with which you can have FCW (Front Collision Warning, looks cool). Definitely worth checking out later on.

I also upgraded the firmware to 79B, everything seems to work smooth, the dreaded Back-button issue is fixed! Finally the radio plays on when you use Back anywhere else, a big improvement.

View attachment 3811940

View attachment 3811941

View attachment 3811942

View attachment 3811943