Unfortunately I am not allowed to post links since I am too new of a user.
Go to imgur and check out the image who's ID is 4FEMS
(It'd be great if someone could edit a link in)
I once asked about a similar port on the back of my old VN250 dumbphone over on the SparkFun IRC channel at freenode, I recall them mentioning something about it being there so manufacturers could easily write an image to a large number of devices. Is that true? If so/not could this be used to facilitate hacking the device?
I might be able to hack up a connector if I knew what kind of jack that was.
post the link by replacing the : witha a - i couldnt find the pic you talked about
sure thing
http-//i.imgur.com/4FEMS.jpg
Google it.
I am almost certain that this is a "u.fl" interface. If you look on a Wireless NIC you will see the same connector. This connector is for a wireless antenna. You could try connecting an antenna to It. I have one and will tell you the results.
Its for connecting an external antenna, many phones have this somewhere but its usually hard to find and easy to damage if you mess around with it.
Related
I have purchased a HICES Android Car/DVD unit for my Camaro. Being on that forum, which I won't mention, has helped a lot with some of the fitment issues we (maybe about a half dozen of us have purchased from word of thread). The company actually sells many different unit for different vehicles. We have been in direct contact with the representative of the company and he has quickly (within 2 months) corrected the fitment issues so this unit should now literally be plug and play.
Earlier versions were 2.3.4 and he has now upgraded newer units to 4.0.3 and upgraded us who purchased prior to the upgrade. Customer service wise he has been great. Also, since I had to download the upgrade, I know have those files saved to a MicroSD.
I have searched these forums for HICES, etc. however all I seem to pull up are the other Chinese branded units. There is one issue with this unit which I was hoping someone on here might actually have a suggestion. Is it possible that in the hardware for a "tablet" there is no microphone? These units only lack a way to communicate through BT. In doing the upgrade to 4.0.3 it has lost its ability to communicate through BT using the dongle provided. In the Camaro the bluetooth mechanism is located in the stock headunit, which obviously causes a problem when you remove it to replace it with this.
Because of the communication with the company rep our best bet may be to stick with letting them get this figured out, but I was hoping someone on here may have one and just not posted about it. I would really like to see what this is capable of.
Sorry I can't post outside links, but searching Google for HICES Android will pull up the website.
When I am allowed, I will post the website to the forum where there are more pictures and video of the unit, it just comes down to none of us being knowledgeable with android.
Thanks for any support
Brian
Somebody here suggested that the HICES Deckless head unit is based on the AN-21u. There's a hardware hacking thread here (http://forum.xda-developers.com/showthread.php?t=2610926)
Some people have added an external hardware microphone, but nobody has checked AFAIK that they board is the same. Maybe you'd be willing to remove your unit and open it up. The thread I linked above shows what you'd need to look for.
I was just wondering if and how i could make sure my wireless network card will work with remix os and maybe how i could go about making sure it works without having to hook it up with wires because i would have to ear down walls to hook it up with wires. i will link the page that has my exact product with its windows drivers and everything the company offers. www intellinet-network com/barcode/523981 (okay maybe not link... this is my first time ever posting on a forum) sorry it wouldnt let me link because i havent done ten posts yet
So i'm in the process of converting all of my cars to cars to android. I am having quite the time actually getting units that aren't defective or used in some way. This one came w/ a harness cut so short it's nearly useless, it has SU on it, a bunch of the previous users documents, his phone pairing info, his email account, gmail account, misc documents/pictures, nova launcher, Pandora account, Xposed stuff, etc. Joying took in a return and didn't even look at the damn thing and just sent it back out to another customer. Nice job joying! Anyway after all this I wanted to see if they hacked anything inside and I found this thin 36ish AWG wire soldered between two resistors. I am unsure if this is a mod or stock. I cannot believe joying would do this however the solder job looks quality so I don't know. Can anyone tell me what the purpose of this is if it is not stock? I've probably going to send this back given the circumstances but I'd like opinions on this wire.
Thanks guys.
Dave
TT_Vert said:
So i'm in the process of converting all of my cars to cars to android. I am having quite the time actually getting units that aren't defective or used in some way. This one came w/ a harness cut so short it's nearly useless, it has SU on it, a bunch of the previous users documents, his phone pairing info, his email account, gmail account, misc documents/pictures, nova launcher, Pandora account, Xposed stuff, etc. Joying took in a return and didn't even look at the damn thing and just sent it back out to another customer. Nice job joying! Anyway after all this I wanted to see if they hacked anything inside and I found this thin 36ish AWG wire soldered between two resistors. I am unsure if this is a mod or stock. I cannot believe joying would do this however the solder job looks quality so I don't know. Can anyone tell me what the purpose of this is if it is not stock? I've probably going to send this back given the circumstances but I'd like opinions on this wire.
Thanks guys.
Dave
Click to expand...
Click to collapse
All I can say is I bought a new unit from Xtrons and it was new and there was a very similar thing on the board mounted behind the touch screen. No idea if this will actually help you but based on all the other crap that is on the unit I would definitely send it back and ask them to pay for the postage as well.
I've looked more thoroughly and there are also resistors missing, I'm fairly sure this was modified by someone. I'd really be curious if someone can tell me what this person was up to here.
Dave
TT_Vert said:
I've looked more thoroughly and there are also resistors missing, I'm fairly sure this was modified by someone. I'd really be curious if someone can tell me what this person was up to here.
Dave
Click to expand...
Click to collapse
It may be a last minute-change to the circuitry on the part of the manufacturer.
I have seen some similar things here and there in the past, where you purchased the last run of the "old-style" circuits that have to have a few extra traces or runs included, and the only way to do that is to install a jumper, leave out a few components, do some extra manual soldering, etc.
If it functions okay, and you're not noticing any critical defects in the performance of the unit, I wouldn't worry about it if I were you. There is a very low likelihood that some end-user would simply go in and start desoldering things and throwing in jumpers, and you get a product that still functions in good order. The average Joe would simply break it doing things like that; the person who did that knew what they were doing, even if it looks somewhat unprofessional.
(If it works, don't fix it.)
Spoke to the vendor and they told me they did not do the modification.
Dave
I cant see anything that doesnt look like it wasnt done by the factory, does everything work ?
Resistors are missing and a jumper wire has been added. I would hope they wouldn't have left it like that. Regardless Joying says it was not done by them.
Dave
TT_Vert said:
Resistors are missing and a jumper wire has been added. I would hope they wouldn't have left it like that. Regardless Joying says it was not done by them.
Dave
Click to expand...
Click to collapse
Missing, or just not been added because they are not needed on your version ? Nothing looks out of the ordinary to me. Joying are sellers, not a factory so I doubt theyd have done anything internally to your unit. Does everything work ?
The pads appear to have solder on them. The device also had someone elses data on it. There was no way I was going to accept this as a new device.
Dave
Hello, wondering if any one could help me out. I'm trying to find out information on using a direct link between our radios and the can bus without using a can box... Does any one have any information if the two pins in the main connector labeled can+rx/can-tx at locations pin 1 and pin 11 in the attached picture, can be utilities for this. Thanks!
trav473 said:
Hello, wondering if any one could help me out. I'm trying to find out information on using a direct link between our radios and the can bus without using a can box... Does any one have any information if the two pins in the main connector labeled can+rx/can-tx at locations pin 1 and pin 11 in the attached picture, can be utilities for this. Thanks!
Click to expand...
Click to collapse
While I am certainly no expert here, I would say that you probably can not interface with the vehicle without something to interpret the data coming from the vehicle. Canbus, Arduino, R2-D2, etc.
Your quest needs more info. What is the ultimate goal?
From what i have seen, experienced on this so far is the CANBox job is two fold, one is electrical interface to car and the other is software , on the software side there are subtle difference between cars on OBD code meanings, these boxes convert the signals in both electrical format (12volts can differential to 3.3 can tx/rx) and software format so the signal coming out to the head unit is a common CAN protocol at low voltage for the headunit regardless if the car is using CAN, K Line, KKL type protocols.
see the schematics here https://forum.xda-developers.com/android-auto/mtcd-hardware-development/canbox-versions-t3763383
I'am currently reverse engineering one for a vw right now for purpose of research for fun.
darkspr1te
darkspr1te said:
From what i have seen, experienced on this so far is the CANBox job is two fold, one is electrical interface to car and the other is software , on the software side there are subtle difference between cars on OBD code meanings, these boxes convert the signals in both electrical format (12volts can differential to 3.3 can tx/rx) and software format so the signal coming out to the head unit is a common CAN protocol at low voltage for the headunit regardless if the car is using CAN, K Line, KKL type protocols.
see the schematics here https://forum.xda-developers.com/android-auto/mtcd-hardware-development/canbox-versions-t3763383
I'am currently reverse engineering one for a vw right now for purpose of research for fun.
darkspr1te
Click to expand...
Click to collapse
This is what I am somewhat looking for... I was figuring as much that the Can boxes were to make the connections to various OEMs universal between the Android radios. I'm researching for the heavy duty truck market. That market all uses a J1939 SAE standard and I'm wanting to see if it was possible to perform all the translation (hardware and software) within the MCU.... And do away with the CAN box.... Thanks for the info... I plan on building an Arduino box to start sorting out the data that is broadcast on that datelink, but need the know what the possible expectation the MCU is looking for on the input side...
trav473 said:
This is what I am somewhat looking for... I was figuring as much that the Can boxes were to make the connections to various OEMs universal between the Android radios. I'm researching for the heavy duty truck market. That market all uses a J1939 SAE standard and I'm wanting to see if it was possible to perform all the translation (hardware and software) within the MCU.... And do away with the CAN box.... Thanks for the info... I plan on building an Arduino box to start sorting out the data that is broadcast on that datelink, but need the know what the possible expectation the MCU is looking for on the input side...
Click to expand...
Click to collapse
I have made progress on this,
see
CANBOX reverse engineering
I think you can use an OBD2 ELM327 adapter selecting the correct protocol with command AT SP <n>. Search correct number <n> in ELM327 command list. That selection remains permanent in the device. This way you will have text messages formed with byte numbers in hexadecimal format. The USB/Serial speed will be apparently 38400 bps or perhaps another as 115200. But I think it is simply an USB connection and serial speed doesn't matter about response time. I have a device that only works fine at 38400 bps as it sends strange symbols at 115200, for example. It is possible to install OBD2 device hidden giving it supply through pin 16 and connecting pins 6 and 14 CANBUS. I wish to do this installation but my car has easy accesible CANBUS through a TTL line that arrives to the radio, almost sure in P2P mode, not two lines at 2.5 V with dominant and recessive states as a multinode bus.
I think OBD2 devices used to program ECUs works with pure binary messages (standard SAE J2534). But I don't know messages format nor protocol. Nevertheless, although in ASCII format programs have more work to do, they are easier to do.
Hello everyone and greetings from Greece!
I am a university student of Mechanical Engineering and I have to take on my diploma thesis at car CAN bus communications. My teacher has asked me to find information on this topic like: bibliography, articles etc. from official and valid sources and learn some basics. For exhample: what is CAN bus, Linbus, what the K communication line does etc. As well as to find a cheap CAN bus usb interface, software and a simple dbc file to do some very basic measurements (not encrypted) at a vehicle.
Any help is useful for me! Also if u have another forum at your mind that i can write please tell me.
Thank you very much in advance everyone for your time and for your help!
ok, I will tell you first that this is a big rabbit hole you are going down but I have some tips for you that will assist.
CAN bus refers to a specific communications type (protocol, voltage, topology) as does K-line, KKL , LIN bus, RS 485 etc , they often are pooled together under the names like OBDII/j2534/sae j1962 . then you will also see that the individual systems will also have other names like K-line is also known as ISO9194.
Then there are interface's you will see that are not in OBDII but 'maybe OBD1' like ALDL (a GM system often used in Suzuki vitara's up to 1996) or ford EEC III/IV up to 2000.
This will also mean that the plugs on the car for interfacing maybe different between brands so for practical work make sure you choose a recent car that falls under latest EU regs for OBD access.
If you choose your thesis on OBDII and it's sub protocols you might be out of luck as most of the good sites with technical info are on russian servers/DNS and i've found them off line recently.
If you choose a sub protocol (canbus for example) there a lot of info on EEVBlog forums, canbus wiki. There is also info on the Open ECU forums and openOBD forums if it's still up (great site for info but very toxic)
If you are going into the practical side more (bus sniffing, replay attacks etc) you will need OBD2 splitters, OBD2 reader "like the elm327" and a CANbus chip and MCU to put custom code on.
I chose stm32 based chips for the canbus MCU side and use both CANBUS inverters(electrical connection to canbus network) and mcp2515 spi canbus interface (converts canbus to spi)
also a good DSO wont go amiss if you dont have access to one at uni.
darkspr1te
some easy links
Canbus links
darkspr1te said:
ok, I will tell you first that this is a big rabbit hole you are going down but I have some tips for you that will assist.
CAN bus refers to a specific communications type (protocol, voltage, topology) as does K-line, KKL , LIN bus, RS 485 etc , they often are pooled together under the names like OBDII/j2534/sae j1962 . then you will also see that the individual systems will also have other names like K-line is also known as ISO9194.
Then there are interface's you will see that are not in OBDII but 'maybe OBD1' like ALDL (a GM system often used in Suzuki vitara's up to 1996) or ford EEC III/IV up to 2000.
This will also mean that the plugs on the car for interfacing maybe different between brands so for practical work make sure you choose a recent car that falls under latest EU regs for OBD access.
If you choose your thesis on OBDII and it's sub protocols you might be out of luck as most of the good sites with technical info are on russian servers/DNS and i've found them off line recently.
If you choose a sub protocol (canbus for example) there a lot of info on EEVBlog forums, canbus wiki. There is also info on the Open ECU forums and openOBD forums if it's still up (great site for info but very toxic)
If you are going into the practical side more (bus sniffing, replay attacks etc) you will need OBD2 splitters, OBD2 reader "like the elm327" and a CANbus chip and MCU to put custom code on.
I chose stm32 based chips for the canbus MCU side and use both CANBUS inverters(electrical connection to canbus network) and mcp2515 spi canbus interface (converts canbus to spi)
also a good DSO wont go amiss if you dont have access to one at uni.
darkspr1te
some easy links
Canbus links
Click to expand...
Click to collapse
Okay, thank you, I will take into account what you have mentioned. I believe the links will help me in the thesis. Greetings!
Posting here as you never know...
I'm looking to access the UART on the LG G Watch R or Urbane (or regular? It's probably the same method).
Does anyone have some leads on this? From the kernel source, it might be that providing between 0.81 and 1.00 V on the USB "ID" pin might enable it. However, I just got the watch, and don't even know which pins are exposed to the pogo contacts? Would the ID pin be exposed?
In any case, I'll go grind some info on it, but feel free to post what you know here.