I've got the PB76AA3AP unit... I'm on a non-Bose but amped car, I got the rear speakers working, mainly because I didn't plug the blue+green connectors to power them in the first place...
Anyway! I've noticed my unit has a really quickboot, to the point it's more of a restore of the system state, rather than actually booting up, is this normal? Just worried in case it kills my battery.
Yes it doesn't sound right that, I had the same with a previous android unit and my battery went dead. It turned out there is a red wire on them that needs disconnecting, on mine it had a connector so it were 2 red wires plugged together so I simply unplugged the connector and problem sorted! If you have one whole red wire then I've read elsewhere that it's a case of cutting it.
Alternatively it could be a faulty canbus box.
Cool - I've got some information from them, they initially suggested following this
However, I don't have the second half of that red cable they're saying to join together...
Then they've just said cut the red from the canbus, and I've confirmed that they're on about this
They're not saying to join the cable together. Theyre saying like I said in my post that the cable will already be joined together and you need to disconnect it, that's why it's draining the battery. By the looks of that though it has no connector so needs cutting like you have said.
I ordered the same unit a few days ago and it's just been delivered for me to collect so I'll be installing it today so I'll let you know what I find.
On Step 3, they are saying to join the cables together (that weren't initially)... I've confirmed with Xtrons, if the two ACC are separated prior, cut the red from the canbus and join the originally separated ACC...
Yes I see what you're saying now.
From my experience though from when I had one of these units before, if you cut that red cable you have identified then that will stop the unit from draining the battery and it will turn off properly.
If you cut it and it doesn't work (but I'm sure it will) you can always join it back together again
Just cut it as suggested, didn't power the unit on anymore. Joined them back up and a bit of electrical tape over it and it's back on for now.
Xtrons are sending me a new loom and canbus unit, once that arrives I'll go mental with a MM, that way I have something that functions to go back to.
I'll post results if I find something out; hopefully it'll help others who may face this situation.
Thanks for your help ab1702
Yeah - also was asked to try the brown by them as well.After you have cut that cable have you tried joining those other 2 red cables together that you have dangling loose in the picture, one is above your gearstick in the picture and the other is below it and to the left in the picture
Yeah - also was asked to try the brown by them as well.
You should be fine, they're suggesting it could be a faulty canbus box - sending a new one out and a new loom as I had to make a cut (not much of an issue, but nice gesture from them either way). They're sending from their UK depo, so hopefully have it by the weekend or Monday/Tuesday.
I did notice even after rooting and using terminal to shutdown (su | reboot -p) it still booted itself back up and then went to sleep mode, which is using power, as I was able to get an adb connection through to it still, when running a dmesg I could see that there was still a charge going through.
I could kill this completely by hitting the reset button behind SD/RST; when attempting another adb, connection fails (but I can't confirm if there's still charge going to it).
So.. I've installed it and everything seems to be working fine. When it comes to turning it off if I turn the ignition off but leave the keys in then it still works like the original Audi unit did but when I pull the keys out it then says power off shutting down, so all seems to be fine there.
All my cables look exactly the same as yours so something of yours must be faulty. Everything was pretty much plugged in for me in the box, I just had to plug the speakers into the unit and the main power adaptor connected to the loom and then connect that to the cars quad lock loom and everything was done. Even the aerial came already connected with a dual fakra connector.
I must say I am impressed in this android 6 unit as the octa core makes it boot up much quicker than my last unit I had which was android 4.4.
I have Bose speakers and these worked straight away at the proper volume and so far there doesn't seem to be any interference with the sound (although I haven't took it for a proper drive yet with the new unit in).
I ordered DAB with it aswell which is working perfectly fine.
The only slight annoyance I have is that I haven't got a reverse camera but when you put the car in reverse it cuts all the screen off as if it were showing you the rear camera view and I haven't figured out if this can be turned off yet. I have got the volume to stay on when this happens though so it isn't a major problem.
Can someone put up some more picture of the fit on these, also interested in the colour match on the plastic from the various unit manufacturers.
Good to hear that yours is working fine - that'll give hope to others looking to get the same unit. I've had nothing but good service from Xtrons regarding my issue too.
Once you've taken the keys out and it's done it's shutdown, few hours later, when you start up again - does it boot straight away into what you had before, or does it load the OS completely with bootlogo?
For the reverse camera, I was told to cut one of the wires to kill the reverse camera (I think it was labelled reverse), I didn't cut it as I want to get camera eventually. I couldn't find anywhere in the menu or factory menu to turn it off.
Good to hear that yours is working fine - that'll give hope to others looking to get the same unit. I've had nothing but good service from Xtrons regarding my issue too.
Once you've taken the keys out and it's done it's shutdown, few hours later, when you start up again - does it boot straight away into what you had before, or does it load the OS completely with bootlogo?
For the reverse camera, I was told to cut one of the wires to kill the reverse camera (I think it was labelled reverse), I didn't cut it as I want to get camera eventually. I couldn't find anywhere in the menu or factory menu to turn it off.
Right so I came to it today then about 5pm and started the car and the unit came straight on instantly so no boot up. I'm unsure to be fair whether this is normal or not though with these new units as when I take the keys out of the ignition the unit turns itself off and I can't turn it back on at all not even by pressing the power button on the unit unless I turn the ignition back on, so it is as if it has no power to it which would seem normal to me.
When I had a problem with my old android 4.4 not turning off it wouldn't go off even when you took the keys out of the ignition whereas this one does. On the old one I had to press the button on the front to turn it off but that would only put it into sleep mode which would drain the battery after a few days, this was until I found the fix for it(Which on that one was to disconnect 2 of the red wires that were coupled together). After I found the fix for it then it would reboot itself every time you turned the ignition off and on so to be honest I'm unsure whether this new one will drain the battery or not but I've got a feeling it will not.
Does yours do the same as what I am describing here with my new one or not?
Mine does the same thing, my ultimate test to confirm if it was still on/alive was to hook up my laptop via adb, turn the car off, and see if I was still able to pull information on the unit - which I was. Also using terminal emulator I was able to confirm that my uptime hadn't reset either... I don't know if this is because of the yellow cable giving it a trickle of power.
When I asked Xtrons, they said it should be displaying the boot logo every time the car is powered - hence why I went through their troubleshooting with them.
It could ultimately be correct as-is, and that their email guys are just unaware and are going via the old information/guides they were provided - I assume that because of the link they provided is for their older looms.
I've got the multimeter out and have been giving fuses a few prods and pokes to confirm if I can find one that turns off when the key is out - and I did find one, but the other half started moaning so I had to head in... I'm half tempted to connect the red + yellow to this, I don't use the radio so am not bothered if I lost the saved stations (well, none are saved atm). I'm going try play around again tomorrow morning
Thanks for sharing the knowledge. It's what I thought of a few last weeks.Hi Leon - Xtrons gave me this link: https://1drv.ms/u/s!AjrY0uqbW_kBgzGKO1x_CECC9815 for GPS/maps. Personally I use Google Maps.
I've had issues with Google Maps crashing after an hour or so of driving (when using it for navigation), having it running on the maps it worked fine with no problem and didn't crash. I've used the update Xtrons gave me to bring me up to the latest version available (checked via xda-devs) but still had this issue. I've since had to re-root as the update ran a flash on system.
The method for rooting, without having to use kingoroot's root manager all the time and without having to remove files from system to remove their app and have the ability to use SuperSU, I did the following:
- Download Kingoroot (not installed yet)
- Download and install SuperSU
- Install and run Kingoroot with an internet connection
- Soon as it says that root was successful, go and run SuperSU
- This will allow SuperSU to become the default root manager, before Kingoroot runs it's **** of wanting the be the only one to provide root access..
- You can then safely uninstall Kingoroot, and you now have SuperSU for root manager, apply the update to the binaries (it won't fail, unless you have kingoroot still installed)
I then changed the kernel governer to performance, and made the minimum usage to 1Ghz (it was 242mhz or something before), I used Kernel Adiutor for this.
Performance on the device was great since doing this, I've not had any Google Maps crashes at all, but I did notice the memory usage was still fairly high, considering it's not really doing much, it looked as if the cause of this was Google Play Services (surprise surprise)...
I took my lenses out, and put my nerd glasses on and got to work and playing around.
I removed all Google Play services, and anything related, so Gmail, Google Maps, Play Store were all removed. The device was smoooth, but kinda useless unless you used a sideloaded apk/GPS. I tried sideloading Google Maps, didn't work - needs play services. Memory usage at this stage was great.
As a bit of an xda-devs vet, I decided to replace Play Services with a minimalist version... So to follow the rest of this, you should have deleted all Google Play Services apps from your device, be it via terminal, adb or root file explorer. They're in /system/app
- Download and install FlashFire, https://flashfire.chainfire.eu/ (you should already be rooted here, and using chainfire's SuperSU)
- Download the correct xposed framework, arm64 for me
- I used FlashFire to flash the .zip file (I haven't ported TWRP to the MTCD unit yet)
- I then downloaded and installed the Xposed app
- Install and enable FakeGApps in Xposed, activate then reboot the unit
- Download MicroG (http://microg.org), MicroG Services Framework, MicroG Store, MicroG Services Core
- Install these three, then reboot the unit again
- Go to Settings > Accounts > Add Account, and add your Gmail account
I've seen on other devices (not car related), that people do have issues using MicroG's Store, there's an alternative called BlankStore https://github.com/mar-v-in/BlankStore. I personally didn't bother, I just downloaded Maps, Play Music, Google Now, YouTube, Chrome from here https://gappsandroid.blogspot.com/ - You can just download the apk for whatever you want for most things online anyways, alternatively you can use the Amazon Store which has a lot of the same things.
IF you do hate everything after this is done, and want Google Play back, remove the MicroG stuff, and download Gapps zip and flash using FlashFire (I did in the end)
Eitherway, since doing this, the performance is insanely great - no choppy sound from the satnav, the mrs watches **** on youtube, flicks back to the satnav if i need it, and the radio etc etc without any hiccups, before it would eventually start slowing down... especially on those trips to Edinburgh without stopping.
Hopefully the blurb above has helped someone who is having issues with performance after a few hours of driving.
This weekend I plan to install the reverse camera, I've pulled the boot card off, and trying to figure out where to drill the whole in the plastic besides the handle, if anyone has any pictures they can show, I'd appreciate it.
So are you saying that in order for GPS to work smooth..get rid of anything to do with Google?
I've already purchased a camera, I went for Amazon product ideally have this next to the boot handle, anyone done it? I dunno where to drill through the plastic