Finding the device ID for Exchange when you use the native mail app for iOS is fairly straightforward, but if you use the Outlook for iOS app, it is much harder to find.
I’ve discovered a process to uncover the device ID, because it appears to be hidden from the Outlook app alltogether.
See this screenshot from an Outlook App device in Exchange Online. Compare it to the one below it of a device added with the native mail app.
The native mail app gives you more detail, which can help you identify the correct device easier. The Outlook app has almost no information besides the iOS version which is usually outdated.
Solution Outline:
We can get the device ID from your device that uses the Microsoft Outlook App, but you need to perform some additional steps.
You will need a Windows PC with the Microsoft store to download the Microsoft Diagnostic Data Viewer The mobile device in question must be connected to the same Wireless network as the diagnostic PC. The outlook app will create a TCP connection to the PC to send logs.
Go into Settings and enable Office diagnostic data viewing on, and Remote Office diagnostic data viewing on
Open the Outlook App and go into Settings>Privacy Settings>View Diagnostic Data on Windows
Copy the Office Connection String from the Diagnostic Data Viewer, and enter it into the Connection String field on the Outlook App.
Exit back to the main screen of Outlook, and check for new messages by pulling down on the Inbox screen. You should see your mobile device show up on the sidebar of the Diagnostic Data Viewer
Select this device, and you should see JSON debugging information. This localId matches what we see in Exchange Admin Center
Bonus: How to find the Exchange Device ID in the native Mail App
Go to Settings>Mail>Accounts>Add Account
Select Microsoft Exchange. The Exchange Device ID should show at the bottom of the page.
If you own a DJI Smart Controller, you may have come across this message while trying to plug it in to charge.
Current charging speed slow. Please use the charger that comes with the device for a faster charging speed.
Slow charging a smart controller could represent a hazard, because the slow charge rate isn’t enough power to maintain the battery level while flying your drone.
After a recent incident where the smart controller shut down while I was flying a drone, I became determined to find a solution to be able to rapid charge the controller via a battery pack I already had
A forum post I discovered mentioned the controller used Qualcomm’s QuickCharge standard. Qualcomm’s QuickCharge standard is a pre-USB PD era charging standard that allows negotiated charging above 5v for supported devices.
I didn’t want to buy yet another battery pack just for an antiquated standard, so I opted to make a cable that converts USB PD to QC instead.
Parts list (Amazon Affiliate links):
Any USB PD battery pack that supports 12v(rare) or 20v output(More common). I used an Insignia I got for cheap, but any 65W capable USB PD charger will do
The braided cord goes into the battery pack, and the barrel plug goes into the QC 3.0 adapter. This braided cord is the magic sauce that tells the charger to output 20v, and send that to the “yipin Hexha” adapter
That adapter will let you charge your Smart Controller significantly faster than before, and your controller won’t die while charging. Hope this helps!
Note: Fuse Taps are directional! For unpopulated fuse banks, only put a fuse in the top and leave the passthrough spot empty.
Fuse Locations
Fuse 47 (red wire on right) should be unpopulated. The left side will provide +12V when the car is on. Insert the fuse tap with the fuse facing down. You can use this for Radar Detectors, Remote wire for amp turn on, Dashcam, etc.
Fuse 31 (yellow wire on left) will provide the car +12v at all times. You can use this for parking mode wire
Ground Location
Remove the front door scuff trim.
Remove the hood latch release handle by pulling it away from the trim
Remove the front door body side weatherstrip.
Using a screwdriver or remover, remove the cowl side trim
Under this you will see a bolt used to hold the dashboard to the chassis.
Remove the bolt and grind down the paint in a small patch around the bolt hole to expose the bare metal.
This is a guide on how to replace the touchscreen on a Mazdaconnect infotainment system.
This guide involves some basic tools and a $15-$25 part from Aliexpress. It is significantly cheaper than having a dealership replace the entire CMU ($1500+), or DIY replacing the whole screen assembly($200).
The problem: Repeated hot/cold cycles causes de-lamination of the adhesive used to combine the touchscreen cover and the digitizer. This failure was a manufacturing defect, and newer vehicles produced by Mazda do not have this problem.
If your car is experiencing any of the issues seen below, this operation may be required to resolve.
If your car is still under full warranty, you can get it replaced at no charge. Info
Note: I took these pictures while re-assembling, after fixing my screen. If something doesn’t look right, let me know. Certain steps in this guide must be done with extreme caution to not damage the screen PCB. If you are not comfortable with working on electronics, do not begin this guide.
If you found this guide helpful, please consider using the affiliate links below to purchase Tools needed for this project.
Disclosure about affiliate links: “When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.”
I use software called Tftpd64 to create a tftp server on my windows PCs. I tell it which folder I dump all my config files into.
when the phone boots, it will look for [mac address].cfg, if it can’t find that, it will look for [mac address]-web.cfg, then 000000000000.cfg.
000000000000.cfg is supposed to be the catchall for phone provisioning. It should not contain any actual phone provisioning commands, it only helps the phone point to other configuration files.
000000000000.cfg defines the following settings before the phone boots:
the firmware update file location
which config files to load (I recommend setting up a generalize.cfg file, then a [PHONE_MAC_ADDRESS]-sip.cfg file for each individual phone)
where to store boot logs (polycom phones will write its boot logs back to the TFTP server)
where to store call history logs (polycom phones will write this back to the TFTP server)
This is an example deployment scenario:
The phone reads 000000000000.cfg because it couldn’t find [phone mac].cfg or [phone mac]-web.cfg
Phone will check for firmware updates defined in the file, if none are found it will continue
000000000000.cfg points to generalize.cfg and [PHONE_MAC_ADDRESS]-sip.cfg
generalize.cfg is read and applied (these settings apply to all phones)
[PHONE_MAC_ADDRESS]-sip.cfg is substituted for the phones MAC, and then is read. (these settings contain passwords, and settings specific to that phone)
The phone boots
The following settings are important for a FreePBX Deployment
generalize.cfg – Settings that don’t change, used by all phones.
msg.mwi.1.callBackMode=”contact” – This is part of the fix for the voicemail button. By default it is set to “register”, but FreePBX requires SIP phones to call a number to get voicemail
voIpProt.SIP.AlertInfo.1.value=”Auto Answer” – When a user dials *80[ext], typically the phone will autoanswer. This is known as page/intercom mode. Special SIP headers are sent by FreePBX so the phone recognizes a page from a regular call. Setting this will make the phone aware of a page
voIpProt.SIP.AlertInfo.1.class=”ringAutoAnswer” – your polycom phone has profiles that define what ringtone to use, how many times to ring, and to auto answer. This setting will tell the phone to auto answer if the SIP.AlertInfo field equals “Auto Answer”
attendant.resourceList.1.label=”Page All” – I have my main page group set to 900 in FreePBX -> Applications -> Paging and Intercom -> Page Group. These commands will create a softkey button to page all phones in page group 900.
attendant.resourceList.1.address=”900″
attendant.resourceList.1.type=”normal”
[PHONE_MAC_ADDRESS]-sip.cfg – you will need one of these per phone, since the attributes defined in this file are specific to each phone
msg.mwi.1.subscribe=”[ext]” – enter your sip extension here to get the mailbox to work
msg.mwi.1.callBack=”*98[ext]” – enter *98 and your sip extension here. This is the number that is called when the voicemail button is pressed.
Other notes:
Web interface changes:
Whenever you manually go into the web interface and make a phone setting change, the phone will write a file [phonemac]-web.cfg to the TFTP server
This will prevent it from loading 000000000000.cfg in the future.
Web browser:
The VVX phones have a full featured web browser, good for internal company resources, or in my case, garage door openers, door buzzers, etc.
Metra 40-LX11– adapts the subaru/lexus/toyota/scion square antenna to the round motorola type. Extra blue wire hanging off is not used. clip off.
Metra 70-1761 – main harness, power, front rear speakers. Simply match colors from sony end to Metra end, and (preferably) solder, properly crimped butt connectors also work.
Adding more functionality
AX-SUB28SWC-6V – subaru/toyota/lexus/scion use a standard 28 pin connector.
This connector has the capability to provide:
reverse camera video and power
aux input
steering wheel control (2 banks of resistors)
vehicle speed sense (Pulse)
parking brake sense (GND activated)
reverse gear sense (+12V)
CANBUS
powered microphone power and audio
However not all features are available in the WRX, as some pins are missing.
The AX-SUB28SWC-6V requires modification to work with the WRX. This is the only option available for retaining steering wheel control and backup cam. Out of the entire install, this part gave me the most trouble because the connector had to be re-pinned.
Luckily I made a diagram that should help you figure out what goes where.
When it was all said and done, I only needed 5 of the pins in the 28 pin connector:
Reverse Trigger
Parking Brake
SWC Ground
SWC Bank 1
SWC Bank 2
Also note: the Metra connector is fragile, do not force in.
Steering Wheel Control
The black connector end of the AX-SUB28SWC typically connects to a Metra Axxess ASWC-1 can be chopped off, because the XAV-AX100 is capable of reading the signals directly from the steering wheel via pins 21-23 on the 28 pin connector Pins 21-13 can be soldered/crimped directly to the 3.5mm jack, then connected to the “remote” port on the XAV-AX100 (see wiring diagram)
Backup Camera
the WRX backup cam requires 6V. The AX-SUB28SWC-6V includes a 12 to 6V converter for this purpose. When shifted into reverse, pin 2 of the 28 pin connector is given 12V. That 12V is sent into the 12to6 adapter, and 6V gets sent out to power the reverse camera. The 2018 WRX Premium uses a 5 pin connector for backup camera video and power, instead of the 28 pin (as is common in other Toyotas) If yours uses the 5 pin, there is no known wiring harness you can buy to adapt the backup camera. We must make our own with breadboard jumpers.
Take 5 of those wires, and cut and strip them, the bare wire side will be soldered to:
Ground
6V in (from 6V out on the 12to6 converter)
VID (+) (RCA Shield)
VID (-) (RCA Center)
Not used
stick them into the OEM camera harness and tape (see wiring diagram for detailed info)
USB Ports
AX-SUBUSB2 Converts a standard male USB connection to the subaru connector found on the OEM harness. This allows you to use the OEM usb ports in your car, with an aftermarket stereo.
(This only works out of the box with WRX’s with a single USB port in center console)Newer WRXs have 2 USB ports and have a builtin USB hub. Since Android Auto/CarPlay is not compatible with USB hubs, a single Aux/USB combo module from 15-17 WRX can be swapped in, if needed. (video coming soon)
Aftermarket Door Speakers
Metra 72-8104 – door speaker, minor modification to plastic adapter required to get proper fitment
Screws (3 per door). OEM screws that connect speaker to door, have too large of a head to accommodate the Metra 72-8104. Any hardware store will carry a screw with a smaller head that won’t interfere with the speaker adapter. (these are not machine screws, they have pointed tips, they go into the plastic inserts in the door)
Speaker Foam – Creates a seal between the speaker frame and plastic Metra adapter to prevent vibrations.
Dynamat (recommended) – Stick inside door panel, reduces vibrations, gives door speakers more bass, and makes interior quieter
Steps Afterward
After you get everything running you’ll want to do a couple things:
Test the backup cam by going into reverse
Turn off the ugly proximity lines in the head unit settings.
Program steering wheel controls in custom mode
Customize your XAV’s wallpaper
Firmware update your XAV
Make sure all FM stations are coming in, (test fringe stations to check if the antenna amp is working)
Load up android auto and check if the parking brake sensor works
turn on/off your headlights to see if the illumination/dimmer wire works.
Quick tip. Avoid running a positive wire from the tail light harness to your head unit for a backup camera
this pink wire in the driver side kick panel cover is the wire that provides 12V when the car is in reverse. Plug this into your head unit to automatically bring up the reverse camera
