yashsingh1/xdaforums huggingface dataset:
[Android Head-Units] swyner:
Agreed. When I had the old Parrot Asteroid Smart...that first splash screen seemed to be "impossible" to change....whether it's built right into the ROM/code or something. Just like the old BIOS message on PCs....anyway, yes, have always wanted any unit to just boot to working BUT if there is a lag (ie 15 seconds like InDash) then the least it could do it look OEM from the start of the boot up.

I do not see any visible changes like "Radio/Aux/Bluetooth UI" comment in the change log. Nothing seems different from FW 95. The only other noticeable item is the boot up volume level. That works as I have tested moving that dial from 7 (default and password required for Vehicle Preference) to 10 and it works as described. Other than that, nothing else so far.
[Android Head-Units] CompletelyNumb:
Just got my replacement 1024 unit from Thomas. Couple of issues:

1) battery was dead in truck day after, and every day since. Today it wouldn't even boost, had to buy a new battery. Guy in store thinks its related to the new head unit. Anyone else experience a parasitic draw? For the most part I just swapped the decks, left the wiring the same, only thing new is the USB camera.

2) Running v93, loud pop noise in speakers when switching head unit on, and between radio stations. Was this fixed?

3) USB camera. I read it was a front facing one, rear facing will be on the RCA jack. How do I operate this camera? Can it be used as a dash cam? I installed it but no default apps are present to use it.

Cheers
[Android Head-Units] swyner:
Is it the Universal or car specific with canbus module? Never have or heard of anyone having battery drain on these. Only thing I can think of is something to do with canbus module if that controls your remote on/off wire like in some VW/Audi cars....however, I have that and everything is perfectly fine. I have NOT installed the USB front facing camera (yes that is what it's for....and there is a specific app that is the only app known to use this but forget the name...MPAS or something like that). Reverse camera is typical (same as 99.9% of all headunits) where it's RCA in. The loud pop noise when switching head unit on/off sounds like you have some amp on/off issue like I had. The blue/white wire out of indash labelled ANT or AMP on absolutely sucks for any remote turn on....I had to switch my harness to use the red wire out of indash (ACC wire of sorts) which turns on my amps AND ANT wire.....works flawlessly with zero thump. Never had the between radio stations "pop noise".

Sorry, can't help much but I am wondering if your old 800 res unit had firmware from WAY back that seemed to not have some of the issues the 1024 newer firmware units had with car specific harness/canbus. That is the only thing I can think of in your situation. Like I said, I had to do some creative wiring for the pop sound on AMP turn on and for radio reception to be excellent.
[Android Head-Units] CompletelyNumb:
My 800 unit came from the factory with a perfect canbus integration. After the first SW update, my steering wheel controls never worked. HU crashed when trying to program them. The new 1000 unit, same deal. Both came with a vehicle specific canbus module that shows the exact same vehicle info, but the part numbers are different. Going to swap them today to see what happens.

I'll email Thomas about the popping. Rewiring is a little out of my comfort zone.
[Android Head-Units] kwalsh24:
Replacement unit? How did you manage that?
[Android Head-Units] swyner:
Ya....if there is a weak point about this unit it's the OEM Canbus integration that other Android Headunits have mastered (including SWC, display info on car display, A/C info, etc). Also, I had received the first canbus module for my audi and it was crap....no SWC, no nothing. Wiring was ok just nothing worked. The AMP turn on and ANT wire out of the indash harness is the issue. I have made Thomas aware and maybe it's only for my car (and now yours) but those blue or blue/white turn on wires just suck. Not sure if the amps are low (as I tested and 12V is present) or it's the timing of turning on (hence the amp pop sound) but I had to rewire my harness to use a spare red wire from the indash harness to connect to my Audi harness to turn on my amps. After that, no pop on normal turn on and off...just on hard reset (push the little button).

---------- Post added at 09:50 PM ---------- Previous post was at 09:48 PM ----------

He was part of the early 800 resolution series from the early adopter campaign. Thomas offered upgrade to 1024 resolution for small price (or free) as he will no longer support the 800 resolution units (too hard to manage two roms, two firmwares, etc, etc)
[Android Head-Units] kwalsh24:
Ah makes sense. Well hope he received a good unit with a good reliable screen lol
[Android Head-Units] CompletelyNumb:
Swapped out the entire main wiring harness with canbus to the new one that came with the 1024. Steering wheel controls worked after that. Still a pop when turning on and switching stations though. Guess we'll see in the morning about power draw, maybe it was an issue with the new deck and old harness.
[Android Head-Units] iizbor3d:
SO funny thing, i'm trying to download the new update and it gives me the error forbidden. This is on chrome.
[Android Head-Units] kwalsh24:
Here's a complete random question... Does anyone know where the radio manufactures (like thomas) get the actual cages / radio trim from? My parents have a ct200h with a weirdly placed fugly radio and they want to upgrade to a navi unit. However im only seeing 2 on the market and both are wince based. Curious if I could get the cage / trim from one source and the radio from another and make my own creation
[Android Head-Units] dunksalot:
RE #1 - When you say "truck" implies you would have a larger than normal battery. I have the universal version and had a dead battery 4 months after installing my new HU. It turned out I had a non-functional cell the whole time so it could only produce 13.8V instead of 14.4V and this was a 3-yr old battery. I read about these units draining the battery and I have a Viper alarm to boot. So I would have thought this HU would kill my battery months ago if the HU's draw was that great. My guess is you were nearing the end of life on that battery anyhow, but these units do rely on the battery at least a little bit more than your traditional car stereo vendors.

RE #2 - Yes it was fixed. You must have amp(s).

RE #3 - It can be used as a dashcam. There are some comments not that far back on this thread about the cam use.

FYI...the rest of this week is the Mid-Autumn Festival holiday in China so I wouldn't expect emails nor software revs. Everyone will be partying and getting their moon cake on.
[Android Head-Units] Nogsmoke:
Hmm. I had that pop show up after I flashed the mcu to the latest as well as installing the 97 update. The 81b and.prior may did not have the pop.

I was able to get rid of it by turning off the 15 min sleep period, but I walked out to the car after it was parked since yesterday afternoon and the battery is dead. Charging it now, but has anyone had this issue? I'm wondering if it never turned off at all.
[Android Head-Units] swyner:
When you start up the indash each time especially overnight does it cold boot? Meaning the octa core boot screen then the android splash screen? If so this means the indash is shutting right down. That would leave your can box as the likely culprit. Let us know.
[Android Head-Units] Nogsmoke:
Yeah, I think so. I unhooked the battery and have it on the charger still (it's at 50%). I'll double check once it's all charged back up.

What did you mean by can box?
[Android Head-Units] MAStx:
I just did the 97 update - no problem. Except the base Radio app is gone. Well, that isn't nice. Do I need to run it again or reset?
[Android Head-Units] j0bro:
Had the same. Did it again and it reappeared!
[Android Head-Units] mrphil101:
I have used the camera for a fcws camera with the installed app, it didn't work well at all for me so I installed a dashcam app. In both apps there are two lines of data in the upper left of the screen that have gps data that does not update. On the fcws app the info is below the status bar. With the dashcam app, the info is behind the status bar, and the status bar will not hide. I uninstalled the fcws app thinking that was causing the issue but apparently not because it is still there. Also the direction of travel and the speed will not show on the dashcam app. I think the installed gps app has "control" of the data, and is not passing it to the requesting app properly or at all and that is where the data on screen is coming from.

I would prefer that the NAVI
[Android Head-Units] mrphil101:
I have used the camera for a fcws camera with the installed app, it didn't work well at all for me so I installed a dashcam app. In both apps there are two lines of data in the upper left of the screen that have gps data that does not update. On the fcws app the info is below the status bar. With the dashcam app, the info is behind the status bar, and the status bar will not hide. I uninstalled the fcws app thinking that was causing the issue but apparently not because it is still there. Also the direction of travel and the speed will not show on the dashcam app. I think the installed gps app has "control" of the data, and is not passing it to the requesting app properly or at all and that is where the data on screen is coming from. I cannot get the correct altitude to display in the app. It is either zero feet or 93 feet, when I know I am at 35 feet (Florida gulf coast)

I would prefer that the NAVI hard button was user configurable so that the nav app of choice could be assigned. How often will it be used to see how many satellites are there? Is this a viable request? should it be added to the spreadsheet?
[Android Head-Units] j0bro:
You *can* select your app of preference for the NAVI button, just go into Settings > Quick Launch and change the app for the 'N' key shortcut.
[Android Head-Units] mrphil101:
has anyone that submitted the easy connect info to tom received the code to access it. I submitted it on time and have not heard anything else about it.

---------- Post added at 02:37 PM ---------- Previous post was at 02:28 PM ----------

Same here. It came back after restarting the unit. I did not redo the update.
[Android Head-Units] MAStx:
Well, surprise! Yes, about an hour later! Magic! :p

---------- Post added at 09:53 PM ---------- Previous post was at 09:51 PM ----------
[Android Head-Units] kwalsh24:
Well. Its time. Its time to send an email to Thomas about my unit. The flickering has gotten bad to the point that its causing headaches for both myself and my girlfriend now. The image burn / ghosting is getting bad also.

See attached... Image one is Google play music the second is a photo of my home screen where you can still read the writing from Google play music.
[Android Head-Units] GaMeR64:
Does anyone have a list of which hard buttons correspond to which letters in the Quick Launch settings?
[Android Head-Units] devlop:
I think it's just the first letter of the button, so Navi would be "N".
[Android Head-Units] Nogsmoke:
So, I did some troubleshooting today and it turns out that my issue is that when I would turn off the car the amp would turn off with everything else, but then about a minute later it would turn itself back on and remain on. A few days of that and a dead battery. The head unit is cold booting, and the amp was still on.

I flashed the mcu back to the 77a build (from the 95 build) and the problem went away, back to powering off (and staying off) when the car is turned off. Strange. I do use the remote amp out from the head unit to turn on the amp. The 97 update doesn't seem to have any effect on this issue, so I've got that installed as well.
[Android Head-Units] CompletelyNumb:
Here's a fun one. Booted up with a blank, formatted SD card in the GPS slot. Screen went all crazy flashing black and white lines everywhere. I reset it and pulled the card out. Since then, screen stays black. Won't connect via USB. Outer LEDs power up, amp clicks, but no screen. Flashing via SD card brings up empty progress bar.
[Android Head-Units] samdu:
The '97 update doesn't work for me. I can install it and boot into it once, but if it shuts completely down and has to cold boot, I get the Lollipop screen with a one pixel line across the top of the screen, then it goes to the recovery screen. Downloading 95 now to see if that works without incident.
[Android Head-Units] CompletelyNumb:
I was unable to flash 97, but 95 worked without a hitch.
[Android Head-Units] samdu:
Yep. 95 works. Don't know what the deal with 97 is.
[Android Head-Units] swyner:
That is weird I have 97 working no problem. Now I did download it shortly after he posted it and installed it with full flash (not update file). I also had the radio app missing until I reset the unit.
[Android Head-Units] j0bro:
Yup, like said, also running the 97 update without problems. Not much new since 95 though.
[Android Head-Units] mrphil101:
I updated to 97 and the only issue I had was having to restart to get the radio to load. I have to run reroot program after every update and load a new binary file for SU.
[Android Head-Units] kwalsh24:
Well... I'm now officially having regrets purchasing this unit. Now that the weather has started to get cooler here in southwestern Ontario Canada my screen has really started to show its true colours. Turned the radio on this morning after it being around 10 degrees Celsius or lower over night and the screen flicker was HORRIBLE!

I've emailed Thomas now twice about this, first email has gone unanswered thus far (sent 4 days ago) Just sent him another as this is NOT acceptable on a $400+ unit. Maybe on a $150 unit but not on this one. I'm starting to get a little annoyed... well maybe a lot annoyed with my unit. To the point that I almost want to uninstall it and box it up.

Its just down right embarrassing to spend this much on a radio and have it flake like this.
[Android Head-Units] j0bro:
Sounds you're having tough luck man. I didn't read such issues from anyone else yet. I can't look into your setup but I can understand your frustration. Hope you get it sorted out.

---------- Post added at 06:57 PM ---------- Previous post was at 06:51 PM ----------

Can anyone please write down the 4 shortcuts that are cycled using the Mode button?

I think they are: b, p, r and another one. Is there a way to customize which 4 Quick Launch shortcuts are being cycled?

Thanks!
[Android Head-Units] samdu:
I did a full flash as well. Twice. With different downloads.

Did you use the Auto Logo application? Because I suspect that might be the culprit.
[Android Head-Units] kwalsh24:
Oh yeah I'm frustrated. I've gotten a email back from Thomas and sounds like I can return this unit and the other guts I have for a new unit. I just hope he will allow me to get a 7" unit over the 8" unit. As I have a strange feeling that its something to do with the 8" screen vs the 7" this also would eliminate the volume button / control issues I've had since nearly day 1

I've also apologised to him as my frustrations likely came across in the email lol.
[Android Head-Units] j0bro:
Anyone who knows the Mode button shortcuts? b, p, r and ?
[Android Head-Units] GaMeR64:
I must say I kind of agree with you. For a € 600,- Radio (incl. VAT) I had really hoped this was a "real" Chinese radio but I feel that a lot of basic functions work really poorly. The phone calling quality is really crap and I even don't use it anymore. People can barely hear me even when I hold the mic in my hand like a walkie talkie. Yeah seriously... [emoji53]

Having to turn function X off for the radio to have a little stable reception is not really what I expected for a radio with this price.

SWC still doesn't work and Thomas doesn't respond to emails anymore. Last mail where he said to be "looking in to this" was around 4 weeks ago. Emailed again last week.. No response.

GPS Time Sync still doesn't work normally. While the time on GPS Test is always correct.

And there is not much "Open Source" about this Open Source radio and I am annoyed that a lot of willing coders on the forums are willing to help and nothing is changed for them to make this a decent radio. I really have no clue how Thomas wants to market this radio for a larger audience. It just feels a lot like the same stuff everywhere in China with an occasional update that doesnt really fix stuff that should work fairly ok in the first place..
[Android Head-Units] Nogsmoke:
So after not having any luck with the subwoofer, I installed a 3Sixty.3 to see if I could get it working again. The 3Sixty also splits it back into the two channels that my amp is expecting and what I had previously from my old Kenwood deck. What is interesting is the levels that I'm seeing from the radio. The subwoofer's signal levels lag behind the other channels until the unit is at maximum, where it's about equal. It's not quite as simple as bumping up the gain, since it'll be increasingly out of whack as the volumes are increased.

Splitting the mono signal back to two signals of the same strength has helped a decent amount, but the way it's levels behave is strange.

I still can't believe that the clock cannot be reliably set. It's flat out embarrassing when people ask about the radio and it can't tell time.
[Android Head-Units] dunksalot:
I use a subwoofer knob as I noticed fluctuations in the signal from song to song. In terms of the clock I set mine to a time zone ahead and it works great now. :p

How do you feel about the sound quality improvement with the 3sixty vs without? Did you go as far as to tune it with a mic? I have a Helix DSP Pro sitting here (and a mic to fine tune) that I want to install but I am contemplating a car purchase so I'm not quite sure if it's worth putting in only to take it out again later.
[Android Head-Units] Nogsmoke:
Hah, I'll have to try that timezone trick. It seemed like it'd always be either an hour ahead or an hour behind.

Other than the sub levels, I haven't really messed with the 3sixty much. To be honest, I'm totally new to the device, so still learning. It didn't come with a mic for setup, I'll have to look into that. I've got a ton of tweaking to do on the system.
[Android Head-Units] kwalsh24:
Well Thomas has said it would be OK to exchange my unit in on a universal 7" to avoid the 8" screen issues and my volume knob issues. However haven't heard anything since as to what to do on my end go get things going.

To chime in on the sub issues. I noticed on my unit that the sub out was quite weak. I ended up tapping into one of the speaker outputs to get my sub to work.
[Android Head-Units] CompletelyNumb:
So since installing my replacement 1024 unit, I've had a dead battery three times. First time was so bad I had to replace the battery. No other changes were made to my truck, just swapped the wiring harness, canbus and head unit. Diagnosing past that is a little beyond my car stereo expertise.

Any ideas?
[Android Head-Units] Nogsmoke:
I had that with the 95 mcu version. It was turning my amps back on a minute after the system powered down. I rolled back to the 77 version and it went away. A few minutes after you turn the car off, take a look at your amps for power lights.
[Android Head-Units] dunksalot:
Thomas mentioned a few days ago he would be traveling - not sure if it was vacation or business. Maybe give him a few more days.

---------- Post added at 07:57 PM ---------- Previous post was at 07:55 PM ----------

Did you try to 097 version? The only thing I can think of (outside of your head unit) may be your alternator.
[Android Head-Units] Nogsmoke:
The mcu update maxes at 95. The regular update is 97. Mcu is in a different folder. It's not clear what all the mcu was supposed to update, but since I'd never updated it before I though it might do some good (maybe fix my clock, haha). No dice there.

The regular update 97 works fine. MCU I had to rev back to R0077A. Not sure what's up with the R0095_08253 version, but it'd flip my amp back on after the car shut off and kill my battery.
[Android Head-Units] CompletelyNumb:
Appreciate the tip, I'll try that out. Thomas got back to me and basically said the head unit couldn't do that. So I don't have too many more options.

Alternator tested fine luckily.
[Android Head-Units] samdu:
Has anyone gotten the Axxess ASWC-1 working with this thing? Finally got around to installing it and, while the connection to the car works great, it doesn't see the head unit at all. And no combination of manually choosing the radio seems to work, either. As far as the connection to the head unit is concerned, I've got Brown/Brown and Brown White/Brown Black.
[Android Head-Units] devlop:
I have it working in my Tacoma. It was connected with my old stereo, so I had to reset it, but it works fine now. I believe I have it wired the same way. You do need to program the buttons for it to work though. It won't do anything otherwise.
[Android Head-Units] samdu:
Hmm... Maybe I'll give programming the buttons a shot again.

Edit: Wait... do you mean programming the buttons on the head unit or on the ASWC? And speaking of programming the buttons on the head unit, is there any feedback when a button has been successfully programmed?
[Android Head-Units] devlop:
I mean programming through the hu. There is no feedback, but I think the on-screen button changes color once it is programmed. If I remember right, you hold down your steering wheel button, then press the on-screen button to program.
[Android Head-Units] xdamember2:
In my experience the timezone adjustment doesn't always do the trick. Eventually after waking from sleep mode the time is stuck an hour off. I'm back to using an app called clocksync or something like that. But it takes a few minutes before the time is right.
[Android Head-Units] kwalsh24:
So my unit has been sent back and I'm getting a universal unit. Yay hopefully this fixes all the issues my unit had.
[Android Head-Units] Sorazy:
Ordered one in Oct. 2, the Status is still Pending now.
[Android Head-Units] xdamember2:
This week was a holiday in China.
[Android Head-Units] GaMeR64:
I received my DAB+ unit today. Tried connecting it but sadly it doesn't work. Not sure if the pinouts on the back of the radio are correct. Also tried putting 12v separately on the black and yellow wire. Also downloaded the DAB apk app from another xda thread but the InDashNet radio says it can't install. Found another DAB+ apk that is used by another usb tuner but this doesn't work either.

The DAB tuner in the box is a decent one by Shinwa that seems to be in other HU's from other non-chinese brands.

Anyone have an idea how we could get this to work or have a solution to get the apk installed?
[Android Head-Units] Sorazy:
It is still Pending now. Send a email to indashnet@gmail.com, but have no response.
[Android Head-Units] CompletelyNumb:
Just an update, I flashed the 77 MCU over the 95 MCU and my battery drain issue stopped. So there is definitely an issue with 95 in some vehicles.
[Android Head-Units] kwalsh24:
I just received my replacement unit. Impressed as I only had my old unit and it's spare parts sent back last week. Thomas again had proven to me that he's going to do his best to stand behind these units. Even if at times it doesn't feel that way. Here's hoping my universal unit is flawfree
[Android Head-Units] ttttubby:
Where and how can I order this? What is the price?
[Android Head-Units] GaMeR64:
Anyone tested the 97 mcu update yet? There's no changelog so I am curious (with many others I guess) what's improved.
[Android Head-Units] iizbor3d:
I believe this was the change log:

1)Booting default volume cfg: VIS>System>Power-On Volume

2)Booting animation(Automaker) Logo(app)

3)DTV/AUX line issue

4)BT/Radio/Music Theme﻿
[Android Head-Units] sasquatch23:
http://www.letmegooglethat.com/?q=InDashNet
[Android Head-Units] GaMeR64:
That's the changelog for the normal update itself. Not for the MCU update which was released on Oct. 11th.

---------- Post added at 11:43 AM ---------- Previous post was at 11:41 AM ----------

http://www.in-dash.net/buy_en/store/

Prices vary for different models.