Related
Hi , does anyone know if its possible to attach an external antenna ( for the cell phone not the gps or wifi ) on an htc magic. Im guessing it would have to connect thru the mini usb port. Cant seem to find my answer, I only come accross passive repeaters. Thank you
Bump. I'm interested in actually modding the phone if needed.
doubt it, magic is one of the phones that have the lowest amount of mods in the market (the tmobile mytouch variation only has 1 legitamate carrier for housings for example). plus the antenna is a sticker-- open up your backdoor, two stickers by the camera. but I suggest to get a better signal dont put your hand on the top by the camera while texting or calling, and take off any cover you may have on the back like pouches and etc...
wow, no wonder the signal it pulls is so weak
idk what you guys are talking about, the signal is great for me. My gf has the slide and i always have one signal lvl better than her. (3g>edge)
The stickers by the camera are for Bluetooth and GPS. How do I know? Cause the part number is printed on them. 'Amphenol-BT-090601' and 'Amphenol-GPS-090601'
freddudek said:
The stickers by the camera are for Bluetooth and GPS. How do I know? Cause the part number is printed on them. 'Amphenol-BT-090601' and 'Amphenol-GPS-090601'
Click to expand...
Click to collapse
pwned
freddudek said:
The stickers by the camera are for Bluetooth and GPS. How do I know? Cause the part number is printed on them. 'Amphenol-BT-090601' and 'Amphenol-GPS-090601'
Click to expand...
Click to collapse
So where is the phones antenna located at?
Maybe it is a coxial cable located inside the phone.
According to androidtablets.net not only does the the nook color have a bluetooth chip but also a fm radio chip but with stock os you cant use it of course. Does this mean that with cm7 you can also access the fm radio ability like it allows you with bluetooth? If anyone knows please post below.
No, the FM chipset is not connected to any sort of antenna therefore it does not work, regardless of if your running stock or CM.
Midnitte said:
No, the FM chipset is not connected to any sort of antenna therefore it does not work, regardless of if your running stock or CM.
Click to expand...
Click to collapse
Ok but could it be possible to add an wire antenna? Or could you add one like that of an android phone as someone did with an htcs speaker and added it to the nook or is it impossible?
Some phones use headphones as the antenna. I wondered this about the nook, but never cared to find out.
Good Question
colorfulnookie said:
Ok but could it be possible to add an wire antenna? Or could you add one like that of an android phone as someone did with an htcs speaker and added it to the nook or is it impossible?
Click to expand...
Click to collapse
I have wondered about this myself. I bought and learned how to root my Droid 4 for the sole purpose of having the FM radio. I am working on getting my Nook Color to run CM7, and found your post when I searched. I know on my D4 I needed to have it rooted and installed Spirit FM, it works well with the headphones attached. I also found a way to make an antenna using a Radio Shack plug and the antenna off an old cordless phone handset, It works surprisingly well! I don't see why it wouldn't work for the NC, IF it has the fm chip, and IF we can access it. I don't know if Spirit FM has been tested with it or not, but it's worth looking into.
KrellaKrentoshi said:
I have wondered about this myself. I bought and learned how to root my Droid 4 for the sole purpose of having the FM radio. I am working on getting my Nook Color to run CM7, and found your post when I searched. I know on my D4 I needed to have it rooted and installed Spirit FM, it works well with the headphones attached. I also found a way to make an antenna using a Radio Shack plug and the antenna off an old cordless phone handset, It works surprisingly well! I don't see why it wouldn't work for the NC, IF it has the fm chip, and IF we can access it. I don't know if Spirit FM has been tested with it or not, but it's worth looking into.
Click to expand...
Click to collapse
This has been addressed many times, in this forum and others. To my knowledge no one has gotten anything other than static from any app (Spirit included) with any headphones at any time. I'd guess that there is no connection between the radio chip and the headphone socket, for antenna functionality.
I haven't pursued this in a while though, so there could be newer info out there.
Hmmm
tonestertm said:
This has been addressed many times, in this forum and others. To my knowledge no one has gotten anything other than static from any app (Spirit included) with any headphones at any time. I'd guess that there is no connection between the radio chip and the headphone socket, for antenna functionality.
I haven't pursued this in a while though, so there could be newer info out there.
Click to expand...
Click to collapse
Good to know. I will do a little searching in the morning and post any info I may find. Do you know if any guts tinkering has occured to make that connection? I am hoping for a simple, easy solution, like modifying an atrix lapdock to work for a Droid phone
KrellaKrentoshi said:
Good to know. I will do a little searching in the morning and post any info I may find. Do you know if any guts tinkering has occured to make that connection? I am hoping for a simple, easy solution, like modifying an atrix lapdock to work for a Droid phone
Click to expand...
Click to collapse
Been doing some digging since I last posted, and the news, I'm afraid, is not promising.
I learned that the FM receive and transmit (!) antenna functions of the WL1271 chip are on different pins than the WLAN/Bluetooth antenna pins.
In addition, there are dedicated FM Audio Out L/R pins which I would suspect are not provided for on the Nook board/module. It's not clear to me if these are the only outlet for any FM decoded by the chip, though.
These, along with the fact that TI pretty much abandoned the FM feature of this chip in the OMAP implementation, (by their own admission) make the FM radio function for us... challenging.
tonestertm said:
Been doing some digging since I last posted, and the news, I'm afraid, is not promising.
I learned that the FM receive and transmit (!) antenna functions of the WL1271 chip are on different pins than the WLAN/Bluetooth antenna pins.
In addition, there are dedicated FM Audio Out L/R pins which I would suspect are not provided for on the Nook board/module. It's not clear to me if these are the only outlet for any FM decoded by the chip, though.
These, along with the fact that TI pretty much abandoned the FM feature of this chip in the OMAP implementation, (by their own admission) make the FM radio function for us... challenging.
Click to expand...
Click to collapse
Challenging isn't the same as impossible, and it must surely be easier than trying to get CM7 installed to SD card for my NC. I'm beyond stuck on that one, been trying off an on for a year. It seems to me that if the problem lies in the hardware, we should be able to correct that. BTW, did I see correctly, there may be FM TRANSMIT capabilities?! That would rock!! I would be blissfully happy just getting FM recieve to work. If the pins aren't provided for on the NC board, what would be a possible way to correct that?
KrellaKrentoshi said:
Challenging isn't the same as impossible,
Click to expand...
Click to collapse
True.
and it must surely be easier than trying to get CM7 installed to SD card for my NC.
Click to expand...
Click to collapse
I had difficulty with that the first time, too. I can probably help, but either in PM or another thread; been running SD cards for about as long as you've been trying.
It seems to me that if the problem lies in the hardware, we should be able to correct that. BTW, did I see correctly, there may be FM TRANSMIT capabilities?! ...
Click to expand...
Click to collapse
Unfortunately, even though there are some great resources around (see the Novaports sticky above, for one) there's just not enough solid info yet to discover whether there's access to the necessary pin. The whole chip is about 1/4 inch square, containing about 115 contact sites in what's called a ball grid array, or BGA, all on the bottom surface of that tiny, "wahfer-thin" speck. This is married to a daughtercard which brings the necessary contacts out to the real world and has some more circuitry (most notably the chip which handles the wireless/bluetooth antenna switching). There's no way to tell from the pictures I've found whether they designed any access to the FM receive pin for the outside world. And I'd bet good solid money that there's no access to the FM transmit pins (separate Antenna and Audio L/R).
So, not impossible, but the real question is, how much would you be willing to spend to re-engineer a new daughtercard to gain access to these things (if, in fact, they're not accessible)? It would undoubtedly be more than the price of a brand new tablet which already contains all these things and more.
If they did bring the RX pin out on the daughtercard, then it should be possible to do some microsoldering and a lot of what I've just said is moot. But without disassembling one I have no way of knowing. If this were the case, then Spirit would likely be the way to go, as I ran across indications that Mike was doing some serious digging into this issue last year. There's also an infinitesimal ray of hope for drivers from a ROM that somebody put together for one of the Droids, which uses the same chip, that apparently has FM working.
I suppose one moderately simple test would be to load up Spirit, and bring a moderately powerful FM transmitter right up to the base end of the Nook, hoping for some leakage through all the shielding, and see if a signal can be picked up. Unfortunately, unless the result were positive, we'd be no further than we already are.
Oh. Ok
tonestertm said:
True.
I had difficulty with that the first time, too. I can probably help, but either in PM or another thread; been running SD cards for about as long as you've been trying.
Unfortunately, even though there are some great resources around (see the Novaports sticky above, for one) there's just not enough solid info yet to discover whether there's access to the necessary pin. The whole chip is about 1/4 inch square, containing about 115 contact sites in what's called a ball grid array, or BGA, all on the bottom surface of that tiny, "wahfer-thin" speck. This is married to a daughtercard which brings the necessary contacts out to the real world and has some more circuitry (most notably the chip which handles the wireless/bluetooth antenna switching). There's no way to tell from the pictures I've found whether they designed any access to the FM receive pin for the outside world. And I'd bet good solid money that there's no access to the FM transmit pins (separate Antenna and Audio L/R).
So, not impossible, but the real question is, how much would you be willing to spend to re-engineer a new daughtercard to gain access to these things (if, in fact, they're not accessible)? It would undoubtedly be more than the price of a brand new tablet which already contains all these things and more.
If they did bring the RX pin out on the daughtercard, then it should be possible to do some microsoldering and a lot of what I've just said is moot. But without disassembling one I have no way of knowing. If this were the case, then Spirit would likely be the way to go, as I ran across indications that Mike was doing some serious digging into this issue last year. There's also an infinitesimal ray of hope for drivers from a ROM that somebody put together for one of the Droids, which uses the same chip, that apparently has FM working.
I suppose one moderately simple test would be to load up Spirit, and bring a moderately powerful FM transmitter right up to the base end of the Nook, hoping for some leakage through all the shielding, and see if a signal can be picked up. Unfortunately, unless the result were positive, we'd be no further than we already are.
Click to expand...
Click to collapse
So I guess the best thing I can do for the moment is to get CM7 to boot and try Spirit on it. I can do that, and I have a transmitter that might work too. I will post the results.
KrellaKrentoshi said:
Challenging isn't the same as impossible, and it must surely be easier than trying to get CM7 installed to SD card for my NC. I'm beyond stuck on that one, been trying off an on for a year. It seems to me that if the problem lies in the hardware, we should be able to correct that.
Click to expand...
Click to collapse
Really?
have you tried this post?
http://forum.xda-developers.com/showthread.php?t=1000957
because that's been around for quite some time...and it is rather easy...
and it's been around for well over a year....
just sayin...
yep
I have tried it, and 2 others, and im stuck.
KrellaKrentoshi said:
I have tried it, and 2 others, and im stuck.
Click to expand...
Click to collapse
okay...it's pretty simple...but i'll bite....where are you stuck? what exactly about the process is messing you up...
you get the CM7 image, burn it to your SD card using the program provided...insert it into the nook and press the power button...
plasticarmyman said:
okay...it's pretty simple...but i'll bite....where are you stuck? what exactly about the process is messing you up...
you get the CM7 image, burn it to your SD card using the program provided...insert it into the nook and press the power button...
Click to expand...
Click to collapse
..........and watch the little blue android on the skateboard for the next 20 mins until i shut it off. It wont get past the blue dude's splashscreen. I'm working on it on another thread and PM. In the meantime, do ya think you could run the little experiment mentioned a few posts back please?
I made some progress today!!
tonestertm said:
True.
I had difficulty with that the first time, too. I can probably help, but either in PM or another thread; been running SD cards for about as long as you've been trying.
Unfortunately, even though there are some great resources around (see the Novaports sticky above, for one) there's just not enough solid info yet to discover whether there's access to the necessary pin. The whole chip is about 1/4 inch square, containing about 115 contact sites in what's called a ball grid array, or BGA, all on the bottom surface of that tiny, "wahfer-thin" speck. This is married to a daughtercard which brings the necessary contacts out to the real world and has some more circuitry (most notably the chip which handles the wireless/bluetooth antenna switching). There's no way to tell from the pictures I've found whether they designed any access to the FM receive pin for the outside world. And I'd bet good solid money that there's no access to the FM transmit pins (separate Antenna and Audio L/R).
So, not impossible, but the real question is, how much would you be willing to spend to re-engineer a new daughtercard to gain access to these things (if, in fact, they're not accessible)? It would undoubtedly be more than the price of a brand new tablet which already contains all these things and more.
If they did bring the RX pin out on the daughtercard, then it should be possible to do some microsoldering and a lot of what I've just said is moot. But without disassembling one I have no way of knowing. If this were the case, then Spirit would likely be the way to go, as I ran across indications that Mike was doing some serious digging into this issue last year. There's also an infinitesimal ray of hope for drivers from a ROM that somebody put together for one of the Droids, which uses the same chip, that apparently has FM working.
I suppose one moderately simple test would be to load up Spirit, and bring a moderately powerful FM transmitter right up to the base end of the Nook, hoping for some leakage through all the shielding, and see if a signal can be picked up. Unfortunately, unless the result were positive, we'd be no further than we already are.
Click to expand...
Click to collapse
I got my NC running CM 7.2.0. Turns out I needed to rename the ROM and also something was bad on my SD card. I have been happily exploring CM7 and getting my google apps on my NC for 2 hours now. Among the apps I downloaded is Spirit FM, the free version for testing. It loads well, I plugged in headphones and an antenna and can't get a signal, not even static. I will look for my transmitter tonight/tomorow and see what happens then. Thanks for all the encouragement and support on the CM7 thing yall!
Yay!
KrellaKrentoshi said:
I got my NC running CM 7.2.0. Turns out I needed to rename the ROM and also something was bad on my SD card. I have been happily exploring CM7 and getting my google apps on my NC for 2 hours now. Among the apps I downloaded is Spirit FM, the free version for testing. It loads well, I plugged in headphones and an antenna and can't get a signal, not even static. I will look for my transmitter tonight/tomorow and see what happens then. Thanks for all the encouragement and support on the CM7 thing yall!
Click to expand...
Click to collapse
Looking forward to your results. And, Enjoy!
I did the test.....
tonestertm said:
True.
I had difficulty with that the first time, too. I can probably help, but either in PM or another thread; been running SD cards for about as long as you've been trying.
Unfortunately, even though there are some great resources around (see the Novaports sticky above, for one) there's just not enough solid info yet to discover whether there's access to the necessary pin. The whole chip is about 1/4 inch square, containing about 115 contact sites in what's called a ball grid array, or BGA, all on the bottom surface of that tiny, "wahfer-thin" speck. This is married to a daughtercard which brings the necessary contacts out to the real world and has some more circuitry (most notably the chip which handles the wireless/bluetooth antenna switching). There's no way to tell from the pictures I've found whether they designed any access to the FM receive pin for the outside world. And I'd bet good solid money that there's no access to the FM transmit pins (separate Antenna and Audio L/R).
So, not impossible, but the real question is, how much would you be willing to spend to re-engineer a new daughtercard to gain access to these things (if, in fact, they're not accessible)? It would undoubtedly be more than the price of a brand new tablet which already contains all these things and more.
If they did bring the RX pin out on the daughtercard, then it should be possible to do some microsoldering and a lot of what I've just said is moot. But without disassembling one I have no way of knowing. If this were the case, then Spirit would likely be the way to go, as I ran across indications that Mike was doing some serious digging into this issue last year. There's also an infinitesimal ray of hope for drivers from a ROM that somebody put together for one of the Droids, which uses the same chip, that apparently has FM working.
I suppose one moderately simple test would be to load up Spirit, and bring a moderately powerful FM transmitter right up to the base end of the Nook, hoping for some leakage through all the shielding, and see if a signal can be picked up. Unfortunately, unless the result were positive, we'd be no further than we already are.
Click to expand...
Click to collapse
Houston, we have a problem. I have a stock nook running cm7 on sd card. Spirit FM Free with superuser permissions granted couldn't pick up the transmitter. :crying: I even put the transmitter right up against the nook and didn't hear anything, so it's not looking very good. I know on my droid 4 I had to have it rooted in order for the FM to work, I wonder if that is the case here? Anyone got a rooted nook to try this experiment out on? Once my warrenty is up I will try "nooting" and see if FM works then. If it is the daughter card, I am at a loss. Anyone got an idea about what we can do next? tonestertm, I can't find your Novoports sticky. Can you repost the link please?:good:
KrellaKrentoshi said:
tonestertm, I can't find your Novoports sticky. Can you repost the link please?:good:
Click to expand...
Click to collapse
No need for a link, the Novaports thread is the third one down from the top of this forum.
While searching the web for a few things I ran across this file, I hope it can be of use to others as well.
Asus ME370T Schematics
Enjoy.
So as rear camera they sepose to use a OV5650 module.
Just soldering one to the pcb won't work, will it? That would be too easy.
wired57 said:
While searching the web for a few things I ran across this file, I hope it can be of use to others as well.
Asus ME370T Schematics
Enjoy.
Click to expand...
Click to collapse
This is GREAT!
Unfortunately, this file only has 44 of the 99 pages mentioned on the 1st page of the PDF.
Can you do a little more snooping around to see if there are any other docs for the ME370T?
Thanks. I'm going to be trying to add the 5MP camera from a TF-101 to my N7 and these are a BIG help.
See here: http://forum.xda-developers.com/showpost.php?p=31936554&postcount=88
bigbop said:
This is GREAT!
Unfortunately, this file only has 44 of the 99 pages mentioned on the 1st page of the PDF.
Can you do a little more snooping around to see if there are any other docs for the ME370T?
Thanks. I'm going to be trying to add the 5MP camera from a TF-101 to my N7 and these are a BIG help.
See here: http://forum.xda-developers.com/showpost.php?p=31936554&postcount=88
Click to expand...
Click to collapse
Did you make any progress on this? Is the schematic valid for the 7? I have a bunch of ov5642 modules (with AF VCM) that I might want to integrate and would be nice to know if this is worth looking into.
raf1hh said:
Did you make any progress on this? Is the schematic valid for the 7? I have a bunch of ov5642 modules (with AF VCM) that I might want to integrate and would be nice to know if this is worth looking into.
Click to expand...
Click to collapse
I just took delivery of an N7 with a cracked touchscreen yesterday (it works fine with an external USB mouse).
The rear camera has a 24 pin inline connector.
The original camera on the ME370T device was an 8MP autofocus module.
I received the 5MP autofocus module from an Asus TF-101 and I scavenged a 26pin connector from a DVD drive.
I need to dig up the drivers and kernel bits for the rear TF-101 camera. Hopefully, someone has the individual modules available for the Jellybean release or maybe if I talk nice to one of the kernel devs, they can add them in to one of the offshoot kernels for me to try, one I get the hardware installed.
Note - this is not for the novice weekend hardware hacker - I've been working in electronics for many years and have some of the latest tools for surfacemount rework needed to install the connector.
bigbop said:
I just took delivery of an N7 with a cracked touchscreen yesterday (it works fine with an external USB mouse).
The rear camera has a 24 pin inline connector.
The original camera on the ME370T device was an 8MP autofocus module.
I received the 5MP autofocus module from an Asus TF-101 and I scavenged a 26pin connector from a DVD drive.
I need to dig up the drivers and kernel bits for the rear TF-101 camera. Hopefully, someone has the individual modules available for the Jellybean release or maybe if I talk nice to one of the kernel devs, they can add them in to one of the offshoot kernels for me to try, one I get the hardware installed.
Note - this is not for the novice weekend hardware hacker - I've been working in electronics for many years and have some of the latest tools for surfacemount rework needed to install the connector.
Click to expand...
Click to collapse
if you get this working is there a chance you'd be willing to commission yourself to do others N7's?
bigbop said:
I just took delivery of an N7 with a cracked touchscreen yesterday (it works fine with an external USB mouse).
The rear camera has a 24 pin inline connector.
The original camera on the ME370T device was an 8MP autofocus module.
I received the 5MP autofocus module from an Asus TF-101 and I scavenged a 26pin connector from a DVD drive.
I need to dig up the drivers and kernel bits for the rear TF-101 camera. Hopefully, someone has the individual modules available for the Jellybean release or maybe if I talk nice to one of the kernel devs, they can add them in to one of the offshoot kernels for me to try, one I get the hardware installed.
Note - this is not for the novice weekend hardware hacker - I've been working in electronics for many years and have some of the latest tools for surfacemount rework needed to install the connector.
Click to expand...
Click to collapse
The TF101 uses ov5640 sensor. I don't know who produces the module though. Basic drivers for ov5640 (no AF) are out there and it should be possible to integrate them. Since the camera connector is 24 pin, I would assume that it is MIPI.
That will be an awesome thing to add! seriously :laugh:
raf1hh said:
The TF101 uses ov5640 sensor. I don't know who produces the module though. Basic drivers for ov5640 (no AF) are out there and it should be possible to integrate them. Since the camera connector is 24 pin, I would assume that it is MIPI.
Click to expand...
Click to collapse
The 24 pin connector on the back uses the serial interface from the camera.
Have a look at the schematics I've uploaded ( I grabbed these from the ME370T PDF)
I have the OV5640 spec sheet but it's only for the image module, not the complate device with the 24pin flex cable.
It appears just from eyeballing the TF-101 5MP camera module, it's a perfect match for the N7 rear connector.
bigbop said:
The 24 pin connector on the back uses the serial interface from the camera.
Have a look at the schematics I've uploaded ( I grabbed these from the ME370T PDF)
I have the OV5640 spec sheet but it's only for the image module, not the complate device with the 24pin flex cable.
It appears just from eyeballing the TF-101 5MP camera module, it's a perfect match for the N7 rear connector.
Click to expand...
Click to collapse
I know of three connection types for cameras:
CSI (Serial) - older cameras (around foryo time) used this
DVB - Not used
CSI2 / MIPI - Used by most new components. I believe the ov cameras support both (CSI and MIPI)
The actual ov modules are built by 3rd party companies like Trully, Globaloptics, Sunix etc. Finding the correct data sheet is the tough part because the modules are not marked. One possible way to solve this is to reverse engineer the driver for the TF101, if it's available, or to go with a module that you know. Like I said before i have a handful of ov5642 modules with a 24pin flatflex...
Take a look at the attached pics. On the left is a ov3640 by Sunny Optix, on the right ov5642 by Trully. Both have 24pin flatflex with pins down.
Based on your docs and images from ifixit (sorry, have not taken apart my N7), it looks like all we need is a surface mounted 24 flatflex connector at CON3 or am I missing something?
raf1hh said:
Based on your docs and images from ifixit (sorry, have not taken apart my N7), it looks like all we need is a surface mounted 24 flatflex connector at CON3 or am I missing something?
Click to expand...
Click to collapse
Yup, I've got a 26 pin connector I removed from a DVD drive. I figure I can put in a small spacer to ensure the flex stays in place. I found a 24pin connector on Newark Electronics website but there's a $15 shipping charge for a $2 connector.
+1
raf1hh said:
Based on your docs and images from ifixit (sorry, have not taken apart my N7), it looks like all we need is a surface mounted 24 flatflex connector at CON3 or am I missing something?
Click to expand...
Click to collapse
A correct camera module, connector, drivers/config files, etc.
I'm going to start a new thread specifically for getting the rear camera working on the Nexus 7 as we've essentially hijacked this thread.
New Thread: http://forum.xda-developers.com/showthread.php?t=1990387
Hi Folks,
I have created this thread to both discuss the possibility of and working to add back, the original 5MP rear camera to the Asus nexus 7 tablet that Google had Asus remove from the retail device.
This is essentially a continuation of the posts I started in the Asus ME370T Schematics thread .
This is what I've done so far:
- Purchased a Nexus 7 with a cracked touch surface as my hardware hacking device. It works with a usb mouse just great :laugh:
- Purchased a used Asus TF-101 5MP rear camera module from Ebay
- Studied the Nexus schematics (available here) and created small schematic sub-sheets specifically for the camera and power circuits
- Inspected both the camera module pins and the rear CON3 connector pins on the Nexus PCB - they match 100% electrically
- Recovered a connector from an old DVD drive for installation at CON3 - (Newark wants $15 S&H for a $2 part)
What needs to be done next:
- Remove the shields from the Nexus PCB and determine if there are any surface mount components that are missing that will prevent the rear camera from working.
- If parts are missing - use the available schematics (Nexus and other) to make an educated guess of what parts are missing and install them.
- Check the system logs to see how the front camera shows up when detected.
- Install the connector at CON3
- Boot the device and verify the front camera still works
- Install and verify the camera module is seated properly and there is a proper electrical connection to CON3.
- Boot up the unit and check the system logs to see if the rear camera is detected.
- Determine if the front camera still works.
At this point, since there is no driver for a rear camera in the Nexus 7, I will need to find the driver for it from the TF-101 ICS or JB ROM in addition to determining what configuration files need to be modified/created.
These are the schematics and photos I have so far and have attached below:
-rear camera (CON3) pinouts, camera power circuits, picture showing the TF-101 5MP module beside CON3, front camera pinouts
Please note
- I am NOT willing to modify any on else's Nexus if this works. I'm in Canada and it's too much of a hassle (and expensive) to ship stuff around up here. Besides, the front glass is just too fragile on these devices.
- This project is not for the weekend experimenter - I use a microscope and special soldering equipment when working on devices like this. If all you have is a solder gun/pencil, this project is not for you.
- I make no representations of fitness for any particular use and if you attempt to 'play' or modify your Nexus 7 following any details provided in this thread, you will be totally responsible for everything (good or bad) that happens to your device. That is why I purchased a partially broken device ($50 on Ebay) specifically to play with.
So, who IS this project for?
- It's for all the experienced hardware hackers out there who are able to work with devices like the Nexus 7 without destroying anything and want to 'play' with their toys!
- It's also for any software types who would be happy to help with the driver and config files to get a rear camera functional. Your assistance would be greatly appreciated. I'm a hardware guy - always have been - always will be.
The Camera Module:
The current REAR camera module as specified in the schematics is an OV5650. There has been some talk of using an OV5640 or OV5642. The FRONT camera module is an Aptina 1040.
The issue with this is the modules need to have the exact same electrical pinout as CON3. Maybe someone can find a source for replacement TF-101 rear camera modules out of Asia?
There was also some talk of the front 1.2MP camera using the same electrical (MIPI) interface with 24pins but having a different pin assignment for the data lines. If that's the case, then theoretically, one should be able to re-wire an additional front camera to CON3 and you should be able to use both.
Another item of note is the camera configuration file in /system. It appears that one of the directives in addition to 'front' & 'rear' is 'USB'.
Does that mean with the right driver, USB camera and OTG connector we can use external cameras with the Nexus 7?
If indeed we can, then we don't need to hack CON3 and instead, use an external high-res USB camera.
Unfortunately, the device uses USB v2.0 so an external camera would probably suffer from a slow frame rate - or would it?
This is what this thread is about - playing with the Nexus 7 to add either a rear camera internally or externally.
Comments? Questions? Additions? Drivers?
Very neat. Following this thread
Use an iPhone 4 rear 5MP camera module?
Now this is interesting....
The ME370T schematics for the Nexus 7 specify the rear camera module as being an OV5650.
This document claims the iPhone 4's rear camera module is ALSO the OV5650 as do a number of other teardown reports.
In addition, the iPhone's module has an LED flash!
Ebay has a pile of vendors that sell the iPhone 4 rear camera module very cheaply.
In fact this vendor has them new for $2.50 as of Nov 13/12.
Of course you need to remember that the pinout is completely different.
Anyone have the iPhone 4 schematics for the rear camera?
bigbop said:
Now this is interesting....
The ME370T schematics for the Nexus 7 specify the rear camera module as being an OV5650.
This document claims the iPhone 4's rear camera module is ALSO the OV5650 as do a number of other teardown reports.
In addition, the iPhone's module has an LED flash!
Ebay has a pile of vendors that sell the iPhone 4 rear camera module very cheaply.
In fact this vendor has them new for $2.50 as of Nov 13/12.
Of course you need to remember that the pinout is completely different.
Anyone have the iPhone 4 schematics for the rear camera?
Click to expand...
Click to collapse
I would not waste time on a ovt module for the iphone. It very likely is a custom module with who knows what inside. If you get lucky, you will get the sensor up and running, but forget about the AF VCM and the DSP operation. The module might be labeled 5650, but I guarantee you that it was a custom job for Apple. If you look at the grouper kernel source tree, there is ov5650.c, but this driver is bare-bones. All it has the inits for the different resolutions and read/write gain and exposure functions.
My suggestion is to first try to integrate a lower-end ovt module that has a public driver and that you know the pinout to. If I find sombody local in socal that can solder the surface mount for me, I will try to integrate the ov5642 because I have the full schematics and the driver already written. After that the next step will be to try to integrate a higher end module, most likely something based on the imx105 from Sony.
If you comfortable compiling drivers, take a look at the ov5642 for a DellStreak5. The kernel that has been open sourced by Dell, has the full driver including the firmware for the micro that controls the AF VCM.
Cool...Nice to hear that,Good luck mate for ur success.
my two cents
would it be possible to flip the front cam around or something? like take the front cam then make a cable or resolder the connector on the other side, something like that.
you might also be able to make something like the vainworks stand but that makes a back cam, not front; or something.
I dont really know, just throwing out ideas here.
good luck!
thejrcrafter2 said:
would it be possible to flip the front cam around or something? like take the front cam then make a cable or resolder the connector on the other side, something like that.
you might also be able to make something like the vainworks stand but that makes a back cam, not front; or something.
I dont really know, just throwing out ideas here.
good luck!
Click to expand...
Click to collapse
I looked at the full schematics again and it appears the front camera uses 1 serial data pair whereas the rear uses 2 serial pairs. It might still be possible to use a front camera on the rear but since the TF101 camera is already the one that appears to be a drop-in, I'll stick with that for now.
Set from my Nexus 7 using xda app-developers app
raf1hh said:
I would not waste time on a ovt module for the iphone. It very likely is a custom module with who knows what inside. If you get lucky, you will get the sensor up and running, but forget about the AF VCM and the DSP operation. The module might be labeled 5650, but I guarantee you that it was a custom job for Apple. If you look at the grouper kernel source tree, there is ov5650.c, but this driver is bare-bones. All it has the inits for the different resolutions and read/write gain and exposure functions.
My suggestion is to first try to integrate a lower-end ovt module that has a public driver and that you know the pinout to. If I find sombody local in socal that can solder the surface mount for me, I will try to integrate the ov5642 because I have the full schematics and the driver already written. After that the next step will be to try to integrate a higher end module, most likely something based on the imx105 from Sony.
If you comfortable compiling drivers, take a look at the ov5642 for a DellStreak5. The kernel that has been open sourced by Dell, has the full driver including the firmware for the micro that controls the AF VCM.
Click to expand...
Click to collapse
I understand, but at $2.50 ea, I ordered one to play with.
One trick I've developed to interconnect devices that use flex cables is to use an intermediate flex as an adapter.
That is to say, I grab a flex cable used in a DVD/CD drive, slice it down to the correct pin width and then create offset solder tabs along the cable by scraping off the protective plastic covering. See photo below.
Yes, I may probably get signal reflections ocurring if the data rates are high, but that is the chance I'm willing to take. It just makes interfacing so much cheaper and simpler. Again, you need a very fine soldering tip (0.3mm) and a microscope to work with this.
I've also included photos of the TF-101 5MP camera for the part numbers.
As I mentioned previously, it would be nice to find an inexpensive source for the TF-101 5MP camera modules.
Hopefully, someone will be able to identify the module from the part numbers below.
UPDATE: I just Googled the flex number and up pops the module, for sale from Asus in Europe of all places. A little pricey though:
CAMERA MODULE 5.0M PIXEL
Product Info
Order number: 04G625000810
Type: CAMERA
Description: LITEON/10P2SA511
Price Info: 37.03 Eur
Hi,
is it possible to create a video input (HDMI or Composite) instead of rear camera??
audiophile1 said:
Hi,
is it possible to create a video input (HDMI or Composite) instead of rear camera??
Click to expand...
Click to collapse
That would require making a new thread at the risk of becoming off topic.
Sent from my Nexus 7 using xda app-developers app
I was hoping that this thread would show up eventually. I added a front facing cam to my Vibrant, but it looks like this might be a little more complicated.
Good luck, I'm interested in seeing where this goes.
Does anybody have a N7 with a broken screen that they would like to sell to help the cause? I have a mint conditions N7 and would rather keep it that way
Thanks
Gotta love that XDA community.
raf1hh said:
Does anybody have a N7 with a broken screen that they would like to sell to help the cause? I have a mint conditions N7 and would rather keep it that way
Thanks
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1997273
Check with this guy, he broke his screen, maybe he'd be willing to sell it.
raf1hh said:
Does anybody have a N7 with a broken screen that they would like to sell to help the cause? I have a mint conditions N7 and would rather keep it that way
Thanks
Click to expand...
Click to collapse
Check out Kijiji and Ebay - I picked up one from each for an average of $60.
Both are 16GB units with cracked touchscreens.
Everything else works on them and I've been using them with USB mice.
You just need to be patient.
In the last week, Newark Electronics has reduced its shipping charge to Canada from $15 down to $8.
This means I will now order the proper 24pin FPC connectors I need for CON3.
In case anyone else is thinking of ordering these connectors, they are here.
The connector needs to have the pins inside along the top, not the bottom.
I'm going to wait until Black Friday though as Newark a bunch of other stuff on sale I need.
bigbop said:
Check out Kijiji and Ebay - I picked up one from each for an average of $60.
Both are 16GB units with cracked touchscreens.
Everything else works on them and I've been using them with USB mice.
You just need to be patient.
Click to expand...
Click to collapse
Thanks, I got one of ebay yesterday for 71 bucks. I also found a shop that will do the surface mount connector for me next week.
raf1hh said:
Thanks, I got one of ebay yesterday for 71 bucks. I also found a shop that will do the surface mount connector for me next week.
Click to expand...
Click to collapse
All you need now is the 5MP rear camera module from a TF-101 tablet.
I scored one on ebay for 99 cents (but $8 shipping).
Remember that you need a connector that has the internal pins across the top, not the bottom. Look at the photo of the camera module in my 1st post. The flex cable pins face up when the module is mounted.
I had hoped to sell my busted screen N7 (8 gig) for $75-100....
Might not be realistic though. I am buying a new tablet, and this broken one needs a good home... I only used it for 4 days before it broke.
bigbop said:
All you need now is the 5MP rear camera module from a TF-101 tablet.
I scored one on ebay for 99 cents (but $8 shipping).
Remember that you need a connector that has the internal pins across the top, not the bottom. Look at the photo of the camera module in my 1st post. The flex cable pins face up when the module is mounted.
Click to expand...
Click to collapse
I'm hoping to reuse an existing ov5642 module + flash board that I have laying around. Hopefully my new tablet will get here next week so I can get started on this project. Btw, did you probe your board already, are the schematics valid?
Hi All,
Im thinking of buying a new head unit for my BMW E90, are there any preferences over these brands? Im swaying towards the Eonon GA7165/GA8165 but i believe most of these units are all the same but branded differently?
<--Update-->
Right so after carefully considering everything for 2 years I finally bought one!
I've just purchased the Xtrons PE9890BIPL
https://xtrons.co.uk/bmw-3-series-android-8-0-pe9890bipl
It is on offer for just £239.99 which to me was a steal as second hand units (if you can find one) tend to sell for around £150+ because most people paid £300ish.
it has a beefy specced system of an Octa Core PX5 processor with 4GB RAM and a 32GB ROM running Android 8.0. This unit also has a big 9" screen at the expense of losing a DVD drive and some physical buttons (all of which can be used from your own steering wheel controls) but they offer the same spec with a smaller screen and contains the physical buttons if you'd prefer the physical buttons and DVD drive.
the newer head units running Android 9.0 aren't as good, currently offering a quad core PX35 processor (same x64 bit architecture but runs more efficient) and only 2GB RAM and 16GB ROM so it's a downgrade really.
Then of course we move onto the brilliant XDA forum for custom ROMS, and it just so happens they've already managed to get Android 9.0 onto these PX5 units
So I chose Xtrons because from what I've read most companies buy these units from the same supplier and brand them leaving other factors to be considered, for me xtrons is UK based so next day delivery, plus clearence prices, they also offered the beefier head unit, support seems okay (some chaps hasd ssues with steering wheel functions not working after locking and getting back into car, long story short they sent people new looms and sorted) and then on top of this XDA developers providing custom ROMS which can fix a lot of the common issues. I'll provide another update when it comes on Monday
at the moment
8-core-px5 - Dasaita > All because of the different (stand-alone BT and WiFi chips)
4-Core-px3 - IMHO the only differnce is the OS. 7.1 has no custom roms yet, so yo probably have a bloated OS
difference at both to consider: AMP chip TDA7388 or TDA7850, clear recomindation is the TDA7850 because ist has way more power and sounds clearer and more crisp
https://de.aliexpress.com/item/Car-android-GPS-For-BMW-E93-318LI-E92-325-E91-320LI-E90-328LI-autoradio-navigation-head/32808481136.html
zapedge said:
difference at both to consider: AMP chip TDA7388 or TDA7850, clear recomindation is the TDA7850 because ist has way more power and sounds clearer and more crisp
Click to expand...
Click to collapse
Hey I'm new here.
Is the selection of AMP chip important ? Seems there's very few manufacturers using TDA7850.
The few that do use TDA7850 seem lots more expensive. Is this normal ?
Example http://smarty-trend.com/13-2-din-universal
zapedge said:
at the moment
8-core-px5 - Dasaita > All because of the different (stand-alone BT and WiFi chips)
Click to expand...
Click to collapse
1) BT and Wifi are going to be on the *same* chip, so don't need to pluralize that.
2) The positioning of that particular RF chip (whether it be on the SoM or the host board) doesn't *technically* matter. The downside to being on the host board is typically that the reseller may have a bigger part in writing software that interfaces with it, and reseller written software is always a very bad thing.
3) Intel Sofia units also have the wifibt and GPS chips on the SoM.
Even with the wifibt on the SoM, the resellers *still* manage to mess it up, however, it may be somewhat easier to clean up in this case.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
bgroper said:
Hey I'm new here.
Is the selection of AMP chip important ? Seems there's very few manufacturers using TDA7850.
The few that do use TDA7850 seem lots more expensive. Is this normal ?
Example http://smarty-trend.com/13-2-din-universal
Click to expand...
Click to collapse
I think it may have to do mainly with your needs and expectations.
Neither is going to satisfy anyone who self-identifies as an "audiophile".
I think the main differences are that the 7850 is slightly more powerful (4x50 vs 4x45 watt), and is ok with 2 ohm speakers where the 7388 is 4 ohm only.
http://www.st.com/content/ccc/resou...df/jcr:content/translations/en.CD00179160.pdf
http://www.st.com/content/ccc/resou...df/jcr:content/translations/en.CD00145702.pdf
luciusfox said:
1) BT and Wifi are going to be on the *same* chip, so don't need to pluralize that.
2) The positioning of that particular RF chip (whether it be on the SoM or the host board) doesn't *technically* matter. The downside to being on the host board is typically that the reseller may have a bigger part in writing software that interfaces with it, and reseller written software is always a very bad thing.
3) Intel Sofia units also have the wifibt and GPS chips on the SoM.
Even with the wifibt on the SoM, the resellers *still* manage to mess it up, however, it may be somewhat easier to clean up in this case.
---------- Post added at 07:19 PM ---------- Previous post was at 07:17 PM ----------
I think it may have to do mainly with your needs and expectations.
Neither is going to satisfy anyone who self-identifies as an "audiophile".
I think the main differences are that the 7850 is slightly more powerful (4x50 vs 4x45 watt), and is ok with 2 ohm speakers where the 7388 is 4 ohm only.
http://www.st.com/content/ccc/resou...df/jcr:content/translations/en.CD00179160.pdf
http://www.st.com/content/ccc/resou...df/jcr:content/translations/en.CD00145702.pdf
Click to expand...
Click to collapse
Which make and model has the 7850 chip? I've just had a look at the Eonons, Xtrons and Joying units for the E90 and the most I have found is 4x48w and all the rest are the same 4x45w.
Not sure which chip mine got but I do have the Octacore GA7165A and I'm really happy with it just a few setup things I need to figure out. I also installed Viper4Android which improves the sound greatly only issue I'm facing is it does not apply to the MTC radio.
nils_92 said:
Not sure which chip mine got but I do have the Octacore GA7165A and I'm really happy with it just a few setup things I need to figure out. I also installed Viper4Android which improves the sound greatly only issue I'm facing is it does not apply to the MTC radio.
Click to expand...
Click to collapse
Probably because the radio analog output never touches the CPU. It goes RADIO --> BD37xxx --> amplifier --> speakers.
The BD37xxx is an audio processor/mixer. Bunch of analog inputs, bunch of analog outputs, i2c control from either the MCU or SoC depending in which vendor it is.
nils_92 said:
Not sure which chip mine got but I do have the Octacore GA7165A and I'm really happy with it just a few setup things I need to figure out. I also installed Viper4Android which improves the sound greatly only issue I'm facing is it does not apply to the MTC radio.
Click to expand...
Click to collapse
Hi mate,
Good to hear that Viper4Android works on the GA7165A model, so you've not experienced any other issues? On a YouTube video I've read various things such as Audio quality being poor through Spotify which is one of the main things I'd want, and also phone calls sounding muffled, though I assume that's probably down to the positioning of the Mic itself. What sound system do you have as well mate, is it stock or upgraded?
luciusfox said:
Probably because the radio analog output never touches the CPU. It goes RADIO --> BD37xxx --> amplifier --> speakers.
The BD37xxx is an audio processor/mixer. Bunch of analog inputs, bunch of analog outputs, i2c control from either the MCU or SoC depending in which vendor it is.
Click to expand...
Click to collapse
Very surprised you know information as detailed as that Knowing all that you do, what would you advise to purchase?
mrsweet1991 said:
Hi mate,
Good to hear that Viper4Android works on the GA7165A model, so you've not experienced any other issues? On a YouTube video I've read various things such as Audio quality being poor through Spotify which is one of the main things I'd want, and also phone calls sounding muffled, though I assume that's probably down to the positioning of the Mic itself. What sound system do you have as well mate, is it stock or upgraded?
Click to expand...
Click to collapse
I’ve got the stock sound system of a 2006 E91 I have installed Spotify but I haven’t used it yet still waiting for my mifi device but I’ll give it a shot maybe tomorrow and let you know.
In terms of Bluetooth / phone Bluetooth music is very good and also works through Viper4Android for the phone function itself I’ve only used the internal mic so far and that is a bit quiet but I’ll install the external mic later in the hope that it will improve the volume issue.
One thing I did have was V4A wouldn’t start automatically until I installed it as a system app now or does that just fine and from a sound quality perspective it is not worse than the default Prof. Head unit if anything I would say better since I can set a more granular sound set-up ( I like deep bass when the radio is not too loud just like the loudness feature on other stereos).
Not sure where you live if anywhere near southwest London feel free to pm me and we can meet for a coffee and you can have a look at it
@mrsweet1991 Have not yet tinkered with the mic but I did try Spotify for you and can report it works just fine I left the Spotify EQ off and instead use V4A and the sound quality is as good as an MP3 on the USB.
Hope that helps.
Have now installed the external mic however I had to disconnect the internal mic to get good quality I might go ahead and solder the external mic onto the internal port so I can use that for OK Google etc as well but with external mic and internal disconnected the quality is good.
How can i root the ga8165 and install xposed framework?
Another thoroughly derailed / hijacked thread
mrsweet1991 said:
Hi All,
Im thinking of buying a new head unit for my BMW E90, are there any preferences over these brands? Im swaying towards the Eonon GA7165/GA8165 but i believe most of these units are all the same but branded differently?
Click to expand...
Click to collapse
I recently purchased this unit (GA7165A)and installed it.
If you purchased this unit how do you like it so far?
By the way I have a L7 AMP (fiber) and had to do a bit of research to figure out a few functional work around.
nils_92 said:
Have now installed the external mic however I had to disconnect the internal mic to get good quality I might go ahead and solder the external mic onto the internal port so I can use that for OK Google etc as well but with external mic and internal disconnected the quality is good.
Click to expand...
Click to collapse
Hi Mate,
Been such a long time since I've been on here, I just wanted to say a big thanks for the information it's good to know. I'm hoping one day I might get a break from fixing things on the car and actually get to stick an eonon unit in! Last time I here the 7165a was the best out and now there's a 8165a lol
mallen462 said:
I recently purchased this unit (GA7165A)and installed it.
If you purchased this unit how do you like it so far?
By the way I have a L7 AMP (fiber) and had to do a bit of research to figure out a few functional work around.
Click to expand...
Click to collapse
Hi mate, I've not had a chance to buy one yet.. I seem to end up fixing the bloody car all the time haha. Walked in for an MOT and come out with a failure for a snapped rear spring and a couple of other minor things.. Starting to get back on track now though, so I take it you have the logic 7 system? Mines just the basic system with underseat subs so should be easier to setup but less rewarding on the sound quality side haha.
Also interested in buying a unit for my E90, just not sure how to pick a unit and know that im getting one of the more reliable manufacturers with stable software? Anyone have experience with the Eonon 8165A? seems like the best deal..
Xtrons
Sent from my [device_name] using XDA-Developers Legacy app
Can any GA8615a owners vouch for the sound quality? Is it any worse than the stock HU?