Well, I started trying to figure out what the max clock speed is for
mmc1 (external SDHC) and why the audio is such crap in SGH-T999.
I thought I would share the differences with US and the i9300 I found.
Starting with the Service Manuals for i535 and i9300 and the
teardowns of the T999 and i9300....
We can figure out enough making some assumptions and also
lacking high quality zooms of all the US board...
First a system overview:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the i9300, the FM radio is sent directly from a Silicon Labs
CMOS FM radio receiver chip to an audio line in on the Wolfson
WM1811 audio codec and speaker driver chip. The schematics
don't provide the part numbers, but through the teardowns people
already know about the Wolfson chip. The SiLabs part hasn't been
mentioned anywhere I have seen. The schematics, pin out, and
part number match the unidentified part in the teardowns as the
SiLabs part:
We can see this extra SiLabs radio chip with is on the thin side of the
board and this chip is missing from the US versions:
All Galaxy S3 boards appear to use the same Murata SoC module
that incorporates the Broadcom BCM4334. From the service manuals,
we see the exact same Murata part and schematics: (top one is i9300)
This might be where the confusion is for people trying to use the i9300
firmware to enable FM radio. Yes, the BCM4334 has FM capabilities and
could have been used for maybe FM radio, but it isn't used in any of the boards.
This is the same WLAN/bluetooth hardware, but an unpopulated pin and a deadend.
There isn't even an external pin you could add a wire to.
Now the audio differences:
What is also of interest is that (sadly) the US Galaxy S3 use the
Qualcomm WCD9310 Audio Codec which drives the headphones.
There aren't any datasheets for what this is capable of. In (at least)
the i535 the speaker is driven with a Texas Instruments TPA2039D1
Audio Power Amplifier. And I suspect it is the same for all the US versions.
Whereas, the i9300 uses the Wolfson WM1811 which both drives the
headset and a speaker driver with many other features.
Code:
TPA2039D1 Class-D, 12-dB fixed-gain audio power amplifier
3.24 W (4 Ω, 5 V, 10% THDN)
2.57 W (4 Ω, 5 V, 1% THDN)
1.80 W (8 Ω, 5 V, 10% THDN)
1.46 W (8 Ω, 5 V, 1% THDN)
Code:
Wolfson WM1811
2W stereo (2 x 2W) class D speaker driver
Capless Class W headphone drivers
(5.3mW total power for DAC playback to headphones)
ReTune™ Mobile 5-band, 4-channel parametric EQ
In both cases we don't really know much about the headphone
driver except that you would rather have the Wolfson chip.
I did find this interesting blog post with some
hints about tailoring the WCD9310. Now if only someone had a Qualcomm datasheet.
Good stuff. Thanks.
On a side note. I know everyone agrees about the superiority of the Wolfson implementation, but I don't find the audio in the T999 to be bad at all. Of course, I haven't directly compared the two, and I am certainly no audiophile. Is there a way to do simple tests (besides how loud it is) to find out how good/bad one's audio is?
I know no one cares, and this should be in a R&D development forum, but anyways, here are the tabla registers.
This would allow hardware control of muting, gains, calibration bias currents...
include /linux/mfd/wcd9310/registers.h and the whole commit
http://goo.gl/HZJgw
In related news, I found the debugfs controls for the battery charging, so I guess this adventure comes full circle.
You should move this nice thread to Hardware hacking instead...
http://forum.xda-developers.com/forumdisplay.php?f=1425
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
aNYthing24 said:
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
Click to expand...
Click to collapse
Yes, but it's more complicated than that.
None of the Galaxy S/S2/S3/Note class devices use the Broadcom chip for FM. The International versions that have FM use a Silicon Labs chip.
Many cheaper Samsung devices use Broadcom for FM.
There are over 200 posts on the subject of FM on the US GS3 here: http://forum.xda-developers.com/showthread.php?t=1732685 The last 20-50 posts or so might give a more complete idea of the findings made.
joederp said:
...hints about tailoring the WCD9310. Now if only someone had a Qualcomm datasheet.
Click to expand...
Click to collapse
Qualcomm datasheets are almost impossible to find/get.
I'm pretty familiar with most of the info you posted, but thanks for the pics and the added details.
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ? There's no clue in the stock ROM of course, the si470x driver is generic and the 470x chips are very similar.
I don't recall exactly the differences with the 4705, but if there's a register difference, I can check on my 9300.
mikereidis said:
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ? There's no clue in the stock ROM of course, the si470x driver is generic and the 470x chips are very similar.
I don't recall exactly the differences with the 4705, but if there's a register difference, I can check on my 9300.
Click to expand...
Click to collapse
I'm about 99% sure the i9300 uses the SiLabs 4705.
I am the only source for that and I figured it out based on looking through the i9300 Service Manual.
They include some schematics that point to a radio chip labeled U203, well I googled the pin names
on the schematic, because everyone reuses they symbols provided with the models/abstracts. So the
schematic labeled U203 pointed to SiLabs names on some of their chips, I googled the FM receivers a
little and found one with the same footprint. The only one that fit was the 4704/05 series which are for
mobile.
Now I went back to the service manual and if you search for U203, you will find a parts list that designates
the part as a SI4705-D50-GM. What was confusing is the parts list table is shifted by one row on the right
column. This can be confirmed throughout the document.
So it doesn't take a rocket scientist to figure out that is what the chip is.
It is a Silicon Labs 4705-D50.
So, I hope that helps the i9300 rom efforts.
aNYthing24 said:
So we have the chip that can be used for FM radio, but the antenna isn't there? Am I understanding this right?
Click to expand...
Click to collapse
I would say that they would need the resistors, and inductors inside the SoC module, and an antenna. And then some was to get the data out of the broadcom chip, and then can it handle FM while using bluetooth and WLAN? So I'm guessing based on the cost and module specs, they abandoned it. For the flagship i9300 international design they just threw in another chip. The respin US version they want to save money and the Wolfson and SiLabs volume and cost makes more sense to use the Qcom part and abandon an extra audio input. Also US cell companies go out of their way to disable FM radio even when it is "free". They would rather you pay for data or some crazy nonsense.
...
joederp said:
I would but some asshole mod just threw my post (Not even a new thread, a legit reply to a thread on 8960)
into the general Q&A thread and removed it from hardware.
http://forum.xda-developers.com/showthread.php?t=1888652
That was a post, not a thread that needed a title.
His own forum rules state:
"relating to the hardware of devices and in many circumstances dealing with families of devices. "
Which my COMMENT was, but the power mad mods have to delete my comment. So they obviously don't care about hardware or my research, so **** that mod.
Click to expand...
Click to collapse
Chill...mods try to keep things orderly. If you feel you're treated unfairly, pm the mods and plead your case...it's never a good idea to publicly criticise staff (made up of volunteers) dedicated to our shared interests.
On topic, the FM stations are miserable here, full of annoying racket and ads...I'd never even consider listening to FM even if the SIII had an operable implementation.
mikereidis said:
Are you sure the GT-i9300 uses an SI-4705 and what's the source of that info ?
Click to expand...
Click to collapse
I just googled some more proof for you that it is Si7405. Check the datasheet and compare the part numbering:
YWW is 2012 Week 7 from the photo.
joederp said:
I would say that they would need the resistors, and inductors inside the SoC module, and an antenna. And then some was to get the data out of the broadcom chip, and then can it handle FM while using bluetooth and WLAN? So I'm guessing based on the cost and module specs, they abandoned it. For the flagship i9300 international design they just threw in another chip. The respin US version they want to save money and the Wolfson and SiLabs volume and cost makes more sense to use the Qcom part and abandon an extra audio input. Also US cell companies go out of their way to disable FM radio even when it is "free". They would rather you pay for data or some crazy nonsense.
Click to expand...
Click to collapse
I'm sure you're right about 4705. 9300 schematic shows DOUT which is the digital out the 4701 doesn't have. I didn't even look at the parts list; previous service manuals didn't use the real part numbers so I figured it was useless again.
It's a shame Samsung didn't use the Digital out IMO. But this leads into the fact that they have a "settled design" for FM on the higher end Galaxy S/S2/S3/Note devices. The "settled design" uses a Silicon Labs si470x chip with analog output. I don't know if SL chips have better audio than Broadcom currently, but I suspect they did when the Galaxy S was designed at least (along with a high quality Wolfsson audio chip.)
Samsungs "settled design" for FM on lower end products always uses Broadcom combo chips, that also support BT and WiFi. FM piggy-backs on the BT core and is handled by the Broadcom proprietary BT/FM stack on stock ROMs.
joederp said:
And the Si4705 uses a 32.7MHz crystal, but it can also take
a reference clock from 31.130 to 40.000
...
Can you read RDS through the SDIO?
Click to expand...
Click to collapse
32,768 Hz (2^15)
Hardware wise, yes all si470x registers, including RDS registers, are accessed via SDIO.
The V4L driver accesses the si470x registers.
Samsungs proprietary Silicon Labs/high end specific FM API accesses the V4L driver.
My Spirit FM app, like the Samsung app, can access the Samsung API. But Spirit can also speak directly to the V4L driver, which is preferred.
So there are multiple software layers between an app and the hardware pins such as SDIO.
I'd be interested to access some unique features of the si4705, such as operation down to 64 MHz. but I don't think the V4L driver allows it, as it's generic to si470x.
Just for your benefit, they saved cost by skipping the crystal for the radio chip, it is using the reference clock from the BT chip which is 37.4 and might impact which freq you can tune.
joederp said:
Just for your benefit, they saved cost by skipping the crystal for the radio chip, it is using the reference clock from the BT chip which is 37.4 and might impact which freq you can tune.
Click to expand...
Click to collapse
There are no FM tuning problems on GT-i9300: 76-90 or 87.5-108.
I didn't mean problems but more like in the datasheet if you don't use crystal and have ref clock then there are certain multiplier issues. I was pointing out they are sharing they wlan
Sent from my SGH-T999 using xda app-developers app
it'd be nice to be able to change the headphone amplifier volume (as voodoo does). Does this information you guys found help in that area? It'd be nice to lower the analogue volume to reduce hiss and artifacts.
Yes and no. You can directly modify the tabla register for the qcom codec, but I don't have and darasheet to know what 00 is versus c4 or whatever in the register. I have to write it up still
Sent from my SGH-T999 using xda app-developers app
joederp said:
Yes and no. You can directly modify the tabla register for the qcom codec, but I don't have and darasheet to know what 00 is versus c4 or whatever in the register. I have to write it up still
Sent from my SGH-T999 using xda app-developers app
Click to expand...
Click to collapse
Any news on that?
Related
A recent teardown by ifixit reveals Evo running Broadcom BCM4329 radio chipset. According to broadcom's official promo page, BCM4329 contains "FM radio receiver and transmitter" capability.
HTC Evo - 1Ghz, 4.3" LCD, WiMax, WiFi a/b/g/n, FM Rx+Tx... I think I'm starting to melt just thinking how much I will enjoy this lil device once I get it on June 4th
frifox said:
A recent teardown by ifixit reveals Evo running Broadcom BCM4329 radio chipset. According to broadcom's official promo page, BCM4329 contains "FM radio receiver and transmitter" capability.
HTC Evo - 1Ghz, 4.3" LCD, WiMax, WiFi a/b/g/n, FM Rx+Tx... I think I'm starting to melt just thinking how much I will enjoy this lil device once I get it on June 4th
Click to expand...
Click to collapse
i bet you 50 bucks that there will not be any transmitting feature installed.. and i bet you that it will take several months before it will get hacked
There is no transmitting feature. You can only listen to the radio with headphones on.
-------------------------------------
Sent via the XDA Tapatalk App
Well, that much I do know... already been down that road with touch pro's "hardware accelerated graphics". HTC is well known not to utilize chip's full potential, let it be due to licensing or whatever reason there is.
After quick search on google, it seems that N1/Desire/iPodTouch3G/iPad all contain BCM4329, and seeing all the good devs coming over to Evo territory I'm having my fingers crossed that someone unlocks/writes a driver+app for that FM transmitter before this christmas
EDIT: ... given that the FM transmitter part of the chip is actually wired to the board
I've been dealing with various radios on linux with x86/x64 hardware for past 5 years, so I'll give Evo a stab and see what I can do with it
And just what will you be transmitting if you could?
i use a bluetooth speakerphone in my car to transmit to my car stereo... it'd be nice to take the speakerphone out of the picture. stream pandora/last.fm to the clock radio i have at work.
as posted above, I'd love to stream music to external speakers such as car's audio which doesnt have no aux/blutooth capability.
Has there been any progress on the FM transmitter part? where can I get more info? or is it just a dead topic without much glory
Would be great to be able to stream audio to the car!! I may be buying wrong cars, but none of them come with stock radios that have aux inputs or such. FM transmitting was availble on TAPE DECKS at one time to 'stream' audio to the car.
How can we have forgotten this ability for our newest devices??
BCM4329 is an 802.11 chipset... and originally a B/G only one if I remember right. FM just means frequency modulated. Would be a 2.4ghz FM transmitter chip. Cant think of any microwave transmitters that are AM really anyhow. So, nowhere even close to the right frequency range. Most likely the wifi chip.
Namopereht
Sent from my PC36100 using Tapatalk
Htc evo 4g has fm transmiter from bc reports.
i posted this over here.
http://forum.xda-developers.com/showthread.php?p=7073406#post7073406
I think we should somehow merge these two threads as they both are trying to achieve the same thing.
so some are going off on the depend and saying the fm means freq mod .
NOPES
Broadcom clearly states its a "FM radio receiver and transmitter."
SO YES IT DOES HAVE THE CAPABILITY TO TRANSMIT AUDIO OVER FM
where i got this from .
http://www.broadcom.com/products/Bluetooth/Bluetooth-RF-Silicon-and-Software-Solutions/BCM4329
as we know software wise the evo has no fm Transmiter software installed and like we know Wifi N was in it and turned off till now.
so sometime soon we hope someone will come out with an APK to use the fm transmiter. (to stream our media to fm radios for car or house use.).
actully if you look at there app guide they have a unit without the FM TX.
BCM4325 Low-Power 802.11a/b/g with Bluetooth® 2.1 + EDR and FM
BCM4329 Low-Power 802.11n with Bluetooth® 2.1 + EDR and FM (Tx and Rx)
from pdf
FM Control: HCI and BSC (I2C-compliant) ports
FM Audio: Stereo analog input and output, bidirectional
FM receiver and transmitter (76 MHz to 108 MHz FM bands);
Standards supported:
- European Radio Data Systems (RDS)
- North American Radio Broadcast Data System (RBDS)
• Programmable FM transmit output power
TECH SPECS FROM PDF
FM
Host Interface: High-speed UART, I2C for control
Standard: RDS (Europe) RBDS (North America)
Operating Frequency: 76 – 108 MHz
Search Frequency Step: 50 KHz
Transmit Output Power: 117 dbuV
Receive Sensitivity: –107 dBm
look on the right you will see fm
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pdf can be found here
http://pdf.eccn.com/pdfs/Datasheets/Broadcom/BCM4329.pdf
While the chip may be capable of FM transmitting, it might need a certain hardware configuration to achieve this. That kind of info should be in the datasheet. We can then look at the circuit board to see it if it has the necessary components to move forward. Of course, I'm saying this because I don't know how easy it is to change the chip config and code the necessary drivers. If the software side is easy, they could just do it and see if it works. I'm not sure that it is though. Are there any other android phones with an FM transmitter? I'd imagine the Nexus One has the same chip. If they haven't gotten it working by now, it probably isn't possible.
an FM Transmitter would be epic.
tlordon said:
so some are going off on the depend and saying the fm means freq mod .
NOPES
Click to expand...
Click to collapse
Yes F.M. stands for Frequency Modulated..
Still, as long as its connected and the software is right, im sure it could work
Sent from my Evo 4G via the XDA app
anybody has the datasheet or pinout diagram for BCM4329? i'll take my Evo apart and see if the pins are soldered to PCB...
anybody has the datasheet or pinout diagram for BCM4329? i'll take my Evo apart and see if the pins are soldered to PCB...
Click to expand...
Click to collapse
Careful now
I hope this happens, but I feel like HTC would have already capitalized on this if it was built-in..
I mean not many phones come with built-in FM transmitting. Sound relay with no BT required!
Good luck all, sorry I can't offer anything here..
topdnbass said:
Careful now
I hope this happens, but I feel like HTC would have already capitalized on this if it was built-in..
I mean not many phones come with built-in FM transmitting. Sound relay with no BT required!
Good luck all, sorry I can't offer anything here..
Click to expand...
Click to collapse
HTC utilizing hardware? No wai....
topdnbass said:
Careful now
Click to expand...
Click to collapse
I have a replacement coming in within few days and can use this opportunity to do some hw diggin =P
Minjin said:
While the chip may be capable of FM transmitting, it might need a certain hardware configuration to achieve this. That kind of info should be in the datasheet. We can then look at the circuit board to see it if it has the necessary components to move forward. Of course, I'm saying this because I don't know how easy it is to change the chip config and code the necessary drivers. If the software side is easy, they could just do it and see if it works. I'm not sure that it is though. Are there any other android phones with an FM transmitter? I'd imagine the Nexus One has the same chip. If they haven't gotten it working by now, it probably isn't possible.
Click to expand...
Click to collapse
If you look at my post above. you will see the chip is bidirectional for the FM. nothing else needed. hardware wise.
we do need the app to run the fm (like you said its not found in other fones yet)
only reason it may not be possible is cause BC hasnt released the app source code yet.
Mast3rpyr0 said:
Yes F.M. stands for Frequency Modulated..
Still, as long as its connected and the software is right, im sure it could work
Sent from my Evo 4G via the XDA app
Click to expand...
Click to collapse
ya but wifi uses Spread spectrum not fm.
frifox said:
anybody has the datasheet or pinout diagram for BCM4329? i'll take my Evo apart and see if the pins are soldered to PCB...
Click to expand...
Click to collapse
again read my post has all hardware info we need.
like i say 2sec ago we need the source code to use it. or someone that knows how to make one. LOL
topdnbass said:
Careful now
I hope this happens, but I feel like HTC would have already capitalized on this if it was built-in..
I mean not many phones come with built-in FM transmitting. Sound relay with no BT required!
Good luck all, sorry I can't offer anything here..
Click to expand...
Click to collapse
you may think that but if you knew how htc and many other companies downgrade products by software to profit you wouldnt say that.
the TP and TP2 both had FM radios (both mine worked after many hours)
Neither had fm listed from htc or sprint.
just example my samsung ln46a640 just needed change in sys menu to turn into a 650 with DLNA.
many products are software limited (its cheaper more profitable to limit via software controlles vs hardware. that way they can be making the next gen product and get 2 out of it.
so many products i could spit out that are soft limited and can be opend up(short version)
jerryparid said:
HTC utilizing hardware? No wai....
Click to expand...
Click to collapse
ya i know like we expect them to do that.
so again lets recap
the chip has standard fm radio both RX and TX biderectionlay. meaning if it works in fm receive mode we can make it work in fm transmit mode. No hardware changes.
We just need the software that will take the music or whtver and feed it into the fm side and speak its lingo to transmit
Erm, might it be a problem that it doesn't appear that the phone itself has any sort of FM antenna built in? I mean, the FM Radio app wont even turn on the radio unless you have headphones plugged in... which would be kind of a problem if you are trying to use the transmitter as an audio sink. Speaking of which, Eclair doesn't seem to have any way to select a default audio sink, it just uses whatever is available that has the highest priority ie: headphones -> bluetooth -> internal speakers. I think I read somewhere that Froyo improves on this functionality, but I'm not sure. I guess you could always just use an app to enable the transmitter, set it to highest priority (if that's even possible,) and then start playing whatever you wanted to be transmitted.
I am doing research for UnBrickable Mod on the Galaxy Nexus. UnBrickable Mod will provide a method of recovering a dead device and guarantee unlocked bootloaders for those with the mod.
I just sorted through the 5,000 page OMAP 4430 processor manual. I believe this OMAP 4430 to be very similar to OMAP 4460 used in the Galaxy Nexus http://focus.ti.com/pdfs/wtbu/OMAP4430_ES2.x_Public_TRM_vK.zip
Rebellos and I will require 2 Galaxy Nexus devices to make this technique work. I've done the research and I thoroughly believe UnBrickable Mod on the Galaxy Nexus is possible.
First Galaxy Nexus will be torn down. The processor must be removed and signal endpoints will be documented.
Second Galaxy Nexus will have the modification applied to it. The device will then be shipped to Poland or worked on remotely from Poland by Rebellos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this device is anything like previous Galaxy devices which I have worked on, the SysBoot will be locked to OneNAND.. 0b100110. To enable Boot from USB, a hardware modification must be performed to change that to 0b000110. This will allow boot from USB then boot from OneNAND.
Keep in mind this is a Texas Instruments chip...
The first thing that struck me as odd is that OneNAND used to be a Samsung technology.. The next thing was the fact that the SysBoot pins function similarly to the Samsung S5PC110/Exynos xOM pins... on S5PC110, xOM5 must be brough high to enable boot from USB then OneNAND. the OMAP4 allows this same functionality by modifying SysBoot5... I believe Samsung helped develop the OMAP4 chip.
Code:
27.4.1 Booting Overview
27.4.1.1 Booting Types
Booting is the process of starting a bootstrap from one of the booting devices.
The ROM code has two functions for booting: Peripheral booting and memory booting.
• In peripheral booting, the ROM code polls a selected communication interface such as UART or USB,
downloads the executable code over the interface, and executes it in internal RAM. Downloaded
software from an external host can be used to program flash memories connected to the device. This
special case of peripheral booting is called preflashing; software downloaded for preflashing is called
the flash loader. The flash loader burns a new client application image in external flash memory. Initial
software is a generic term for bootstrap, downloaded software, and flash loader. After the image is
burnt, a software (warm) reset can be performed.
• In memory booting, the ROM code finds the bootstrap in permanent memories such as flash memory
or memory cards and executes it. This process is normally performed after a cold or warm device
reset.
The ROM code detects whether the device should download software from a peripheral interface (USB or
UART) by using the sys_boot[5:0] pin configuration. This mechanism encompasses initial flashing in
production (external memory is empty) and reflashing in service (external memory is already
programmed).
27.4.1.2 ROM Code Architecture
Figure 27-4 shows the ROM code architecture. It is split into three main layers with a top-down approach:
high-level, drivers, and hardware abstraction layer (HAL). One layer communicates with a lower-level layer
through a unified interface.
• The high-level layer performs the main tasks of the public ROM code: multicore startup, watchdog and
clock configurations, interrupt management, interaction with the power-management IC, and main
booting routine.
• The driver layer implements the logical and communication protocols for any booting device in
accordance with the interface specification.
• The HAL implements the lowest level code for interacting with the hardware infrastructure IPs. End
booting devices are attached to the device I/O pads.
Figure 27-4 shows the three layers with their modules.
5198
With all the similarities between S5PC110, Exynos, and OMAP4, there is still alot left to do.
If somebody has got ANY info about this device like used chipset models, internal pictures, service manuals, chipset documentations (especially for the CPU, there are few huge manuals from TI about OMAP4460 covering various aspects) please post it or send to Adam or me through PM. This is what we also do need.
Thanks in advance.
^^what he said... we can hardware unlock the bootloader within hours of release if we can get one for destructive teardown.
With more information, we can really unleash the potential.
Love your work Mr Outler, genius..
congrats
edit: and Rebellos you guys go so far beyond, thanks so much!
http://focus.ti.com/pdfs/wtbu/OMAP4460_ES1.0_PUBLIC_TRM_vF.zip
i already love the development on this device <3
you guys are awsome.
Here's the bootmode pins we are concerned with.
h_SYSBOOT_0 pin: F26
h_SYSBOOT_1 pin: E27
h_SYSBOOT_2 pin: E26
h_SYSBOOT_3 pin: E25
h_SYSBOOT_4 pin: D28
h_SYSBOOT_5 pin: D27
--we are not concerned with the following--
h_SYSBOOT_6 pin: AF8
h_SYSBOOT_7 pin: AE8
These values are for the OMAP4430 and should follow on the OMAP4460
Found a dev board based on OMAP4460.. It's called VAR-SOM-OM44
Here are a few things we unearthed in the Galaxy Nexus:
Silicon
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
GPU: Imagination Technologies PowerVR SGX 540 (same as the Galaxy S and Nexus S)
Wifi / Bluetooth module: Broadcom BCM4330 (same as in the Galaxy S II)
Audio codec: Texas Instruments TWL6040
HDMI: Silicon Image MHD SiI9234 transmitter over MHL (same as Infuse 4G and GSII)
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Framebuffer controller: Samsung S6E8AA0 MIPI LCD with Gamma correction driver
Sensors
Geomagnetic sensor: Brand new tri-axial Yamaha YAS530
TouchScreen sensor: Melfas MMSxxx touchscreen
Optical / proximity sensor: GP2A (same as Galaxy S and Nexus S)
Barometric pressure sensor: BOSCH BMP180 (first of its kind in a smartphone)
Triaxial acceleration sensor: BOSCH BMA250
Triple Axis MEMS Gyroscope: InvenSense MPU3050
Fuel Gauge (algorithm to track battery's state of charge): MAXIM MAX17040
Misc. internals
Facial recognition elements (Face Unlock): left eye, right eye, nose base, head, face
Available resolution for standard apps: 720 x 1184px
Refresh rate: 60Hz
LCD Density: 320
Default display color depth: 32bit
Camera uses OMAP Ducati Subsystem, on-screen preview size is 768 x 576
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Android ROM: version 4.0.1, built October 13, 2011
Device name: Maguro
Main input/output type supported: Headphone, Speaker, Microphone, Bluetooth, Voice, FM, S/PDIF over HDMI; USB Audio DAC (digital-to-audio converter with USB input and stereo outputs) should also be supported
engadget, by Francois
borce_razor said:
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
Click to expand...
Click to collapse
great for confirmation. This is what we have been researching
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Click to expand...
Click to collapse
This means 301kohm resistor will work (if wired internally) and we can also get 619Kohm resistor UART output as well. This is awesome. No changes to my setup needed.
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Click to expand...
Click to collapse
Very interesting... I didn't think they had a 3.0 mobile kernel yet. This is good to know. It may need a new version of the SuperUser binary compiled for it.. Many of the currently existing binaries we use may break.
Thanks! And thanks Supercurio!
I'm definitely on board. What's the goal? ~$1,500?
caffeineighted said:
I'm definitely on board. What's the goal? ~$1,500?
Click to expand...
Click to collapse
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
u make a awesome point.
AdamOutler said:
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to also point out that the service manual on the i9000 instructs the service centers to put the device into download mode and download firmware. If the firmware flash fails then it's hardware damage and the board has to be replaced.
Ergo, a bad software flash = a bad board and the board gets replaced
I use i9000 as an example because i9000 is the only example we have of a Galaxy class device service manual.
This is great im so glad there are already devs working hard on making this a reality, im selling my EVO 3D ASAP so i can get this phone as soon as its released!
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
i9100 service manual
borce_razor said:
i9100 service manual
Click to expand...
Click to collapse
I declare and ordain this as understated post of the week.
AdamOutler said:
I declare and ordain this as understated post of the week.
Click to expand...
Click to collapse
with simple words, useful or not ?
ydaraishy said:
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
Click to expand...
Click to collapse
Yeah... but if you erase fastboot than you're screwed
Also, rumor has it that this device will have locked bootloaders... this will help to unlock them.
borce_razor said:
with simple words, useful or not ?
Click to expand...
Click to collapse
Yes
I know it has been asked before over here, but i would like to discuss it again:
Could it be somehow possible to activate TV-Out over the 3.5mm audio connector on the defy?
The Samsung Captivate (aka Galaxy S) has it and the devs managed to support it in their CM7 version for the captivate. Perhaps we could use some of those "drivers"?
It would be just to cool to use the defy with a bluetooth keyboard (apple wireless keyboard working flawlessly btw) and a nice big screen for browsing and writing documents...
Btw the cable looks like this.
i dont think its matter of drivers, if the headphones jack is not wired to give tv output, then it wont be physically possible without a hardware mod... just my opinion, i could be wrong tho...
Indeed. If it's not meant to output video then it's not meant to. End of story ^^
Sent from my 1Ghz CM7 + CM9 Defy
Did anybody proof that its not wired?
At least it can give audio over 3 pins (stereo+mic) - that means all contacts needed are wired. COuld the tv-signal perhaps be "disguised" as audio signal?
shorty66 said:
Did anybody proof that its not wired?
At least it can give audio over 3 pins (stereo+mic) - that means all contacts needed are wired. COuld the tv-signal perhaps be "disguised" as audio signal?
Click to expand...
Click to collapse
Do you really think that motorola would put a video-output capable 3,5mm jack in the phone, and not use it as a feature?? Things aren't free in this world. If there was one, they would have said so, simply because...they could sell more Defys thanks to it.
Putting a really awesome feature in a phone and not saying nothing about it? Come on... xD
In addition our phone isn't event meant for tv-out, forget about having it flowing out of wierd places like an audio jack x)
Sent from my 1Ghz CM7 + CM9 Defy
Do you really think motorola wouldn`t open the bootloader even if they could? They could have sold a few defys more with an open bootloader....
You might have noticed that im not that convinced by your argument.
No **** man. Moto also advertised a gpu less omap 3610. When in all actuality we have omap 3630. Why would they do that? I think this deserves more looking into
Sent from my MB526 using XDA App
I think if it would be possible, chances are that a kernel tweak would be needed to activate it and thus it would not be possible with a locked bootloader.
But still, i think it could be worth it to take a look in the Captivates librarys regarding tv-out.
shorty66 said:
Do you really think motorola wouldn`t open the bootloader even if they could? They could have sold a few defys more with an open bootloader....
You might have noticed that im not that convinced by your argument.
Click to expand...
Click to collapse
Motorola wouldn't have significantly more sales if the bootloader was unlocked: over 80% of consumers don't even know what a locked/unlocked bootoader is
Sent from my 1Ghz CM7 + CM9 Defy
Can the hdmi / vga tv out be sent via USB?
Please dont be naif, you know how much motorola lies about the defy!, i did a search about the defy hardware, the chip as you know is an omap3630 with sgx530 and IVA 2 +, this chip is capable of transmit audio and video, see the pic:
b.imagehost.org/0148/tiomap.jpg
So the probem is software related, maybe its too complicated due to the locked bootloader but i think its totally posible, its just a matter to find some device that uses the same chip, like the Droid x or milestone 2...
gaman12 said:
Please dont be naif, you know how much motorola lies about the defy!, i did a search about the defy hardware, the chip as you know is an omap3630 with sgx530 and IVA 2 +, this chip is capable of transmit audio and video, see the pic:
b.imagehost.org/0148/tiomap.jpg
So the probem is software related, maybe its too complicated due to the locked bootloader but i think its totally posible, its just a matter to find some device that uses the same chip, like the Droid x or milestone 2...
Click to expand...
Click to collapse
not really... we all know the chip is capable, but if it is not physically utilized, no amount of software tweaking will make it possible... i dont think they would have bothered to connect the 3.5mm audio jack with video out if they are not going to use it...
but u r asking the right question... think outside the box, if its even remotely possible, i would like to have this feature
Following your argument i would conclude that it MUST be possile to route a video signal through the headphone jack. Of course you would need a software wrapper which codes the video signal and puts it out as a sound. If you would do that as an app, this might be awfully slow. But i cant see a reason for this to be impossile as the headphone jack IS wired to the sound output and apps ARE capale of using that sound output.
I would really like to use an app like that as a workaround, as long as its fast enough for simple rowsing.
Edit: I just searched the marked for "Image to sound" apps and came across "Spectral" which takes an image, converrts it into a sound spectrum and plazs it. It should not e too hard to change the conversion to conformwith the component video standard.
This would still onlz convert one image and i dout it would be possible to use this with screenshots in realtime but it would be a good step towards video out on the defy.
shorty66 said:
Following your argument i would conclude that it MUST be possile to route a video signal through the headphone jack. Of course you would need a software wrapper which codes the video signal and puts it out as a sound. If you would do that as an app, this might be awfully slow. But i cant see a reason for this to be impossile as the headphone jack IS wired to the sound output and apps ARE capale of using that sound output.
I would really like to use an app like that as a workaround, as long as its fast enough for simple rowsing.
Edit: I just searched the marked for "Image to sound" apps and came across "Spectral" which takes an image, converrts it into a sound spectrum and plazs it. It should not e too hard to change the conversion to conformwith the component video standard.
This would still onlz convert one image and i dout it would be possible to use this with screenshots in realtime but it would be a good step towards video out on the defy.
Click to expand...
Click to collapse
Dude in fact, it is very hard/impossible. One thing is "transform" a digital image in a digital audio. In that case you dont need to make sense, just convert one block of image into one "la" ou "do" and you are good to go.
We have a limited range of frequencies that we can hear and software/hardware generally take advantage of that. Transport analogic video(that may take a broad range of frequencies) trought analogic audio hardware may be impossible for near anything apart form really simple scenes
shorty66 said:
Following your argument i would conclude that it MUST be possile to route a video signal through the headphone jack. Of course you would need a software wrapper which codes the video signal and puts it out as a sound. If you would do that as an app, this might be awfully slow. But i cant see a reason for this to be impossile as the headphone jack IS wired to the sound output and apps ARE capale of using that sound output.
I would really like to use an app like that as a workaround, as long as its fast enough for simple rowsing.
Edit: I just searched the marked for "Image to sound" apps and came across "Spectral" which takes an image, converrts it into a sound spectrum and plazs it. It should not e too hard to change the conversion to conformwith the component video standard.
This would still onlz convert one image and i dout it would be possible to use this with screenshots in realtime but it would be a good step towards video out on the defy.
Click to expand...
Click to collapse
why not route it via the micro usb, may be it could be easier?
I am doing research for UnBrickable Mod on the Galaxy Nexus. UnBrickable Mod will provide a method of recovering a dead device and guarantee unlocked bootloaders for those with the mod.
I just sorted through the 5,000 page OMAP 4430 processor manual. I believe this OMAP 4430 to be very similar to OMAP 4460 used in the Galaxy Nexus http://focus.ti.com/pdfs/wtbu/OMAP4430_ES2.x_Public_TRM_vK.zip
Rebellos and I will require 2 Galaxy Nexus devices to make this technique work. I've done the research and I thoroughly believe UnBrickable Mod on the Galaxy Nexus is possible.
First Galaxy Nexus will be torn down. The processor must be removed and signal endpoints will be documented.
Second Galaxy Nexus will have the modification applied to it. The device will then be shipped to Poland or worked on remotely from Poland by Rebellos.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If this device is anything like previous Galaxy devices which I have worked on, the SysBoot will be locked to OneNAND.. 0b100110. To enable Boot from USB, a hardware modification must be performed to change that to 0b000110. This will allow boot from USB then boot from OneNAND.
Keep in mind this is a Texas Instruments chip...
The first thing that struck me as odd is that OneNAND used to be a Samsung technology.. The next thing was the fact that the SysBoot pins function similarly to the Samsung S5PC110/Exynos xOM pins... on S5PC110, xOM5 must be brough high to enable boot from USB then OneNAND. the OMAP4 allows this same functionality by modifying SysBoot5... I believe Samsung helped develop the OMAP4 chip.
Code:
27.4.1 Booting Overview
27.4.1.1 Booting Types
Booting is the process of starting a bootstrap from one of the booting devices.
The ROM code has two functions for booting: Peripheral booting and memory booting.
• In peripheral booting, the ROM code polls a selected communication interface such as UART or USB,
downloads the executable code over the interface, and executes it in internal RAM. Downloaded
software from an external host can be used to program flash memories connected to the device. This
special case of peripheral booting is called preflashing; software downloaded for preflashing is called
the flash loader. The flash loader burns a new client application image in external flash memory. Initial
software is a generic term for bootstrap, downloaded software, and flash loader. After the image is
burnt, a software (warm) reset can be performed.
• In memory booting, the ROM code finds the bootstrap in permanent memories such as flash memory
or memory cards and executes it. This process is normally performed after a cold or warm device
reset.
The ROM code detects whether the device should download software from a peripheral interface (USB or
UART) by using the sys_boot[5:0] pin configuration. This mechanism encompasses initial flashing in
production (external memory is empty) and reflashing in service (external memory is already
programmed).
27.4.1.2 ROM Code Architecture
Figure 27-4 shows the ROM code architecture. It is split into three main layers with a top-down approach:
high-level, drivers, and hardware abstraction layer (HAL). One layer communicates with a lower-level layer
through a unified interface.
• The high-level layer performs the main tasks of the public ROM code: multicore startup, watchdog and
clock configurations, interrupt management, interaction with the power-management IC, and main
booting routine.
• The driver layer implements the logical and communication protocols for any booting device in
accordance with the interface specification.
• The HAL implements the lowest level code for interacting with the hardware infrastructure IPs. End
booting devices are attached to the device I/O pads.
Figure 27-4 shows the three layers with their modules.
5198
With all the similarities between S5PC110, Exynos, and OMAP4, there is still alot left to do.
If somebody has got ANY info about this device like used chipset models, internal pictures, service manuals, chipset documentations (especially for the CPU, there are few huge manuals from TI about OMAP4460 covering various aspects) please post it or send to Adam or me through PM. This is what we also do need.
Thanks in advance.
^^what he said... we can hardware unlock the bootloader within hours of release if we can get one for destructive teardown.
With more information, we can really unleash the potential.
Love your work Mr Outler, genius..
congrats
edit: and Rebellos you guys go so far beyond, thanks so much!
http://focus.ti.com/pdfs/wtbu/OMAP4460_ES1.0_PUBLIC_TRM_vF.zip
i already love the development on this device <3
you guys are awsome.
Here's the bootmode pins we are concerned with.
h_SYSBOOT_0 pin: F26
h_SYSBOOT_1 pin: E27
h_SYSBOOT_2 pin: E26
h_SYSBOOT_3 pin: E25
h_SYSBOOT_4 pin: D28
h_SYSBOOT_5 pin: D27
--we are not concerned with the following--
h_SYSBOOT_6 pin: AF8
h_SYSBOOT_7 pin: AE8
These values are for the OMAP4430 and should follow on the OMAP4460
Found a dev board based on OMAP4460.. It's called VAR-SOM-OM44
Here are a few things we unearthed in the Galaxy Nexus:
Silicon
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
GPU: Imagination Technologies PowerVR SGX 540 (same as the Galaxy S and Nexus S)
Wifi / Bluetooth module: Broadcom BCM4330 (same as in the Galaxy S II)
Audio codec: Texas Instruments TWL6040
HDMI: Silicon Image MHD SiI9234 transmitter over MHL (same as Infuse 4G and GSII)
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Framebuffer controller: Samsung S6E8AA0 MIPI LCD with Gamma correction driver
Sensors
Geomagnetic sensor: Brand new tri-axial Yamaha YAS530
TouchScreen sensor: Melfas MMSxxx touchscreen
Optical / proximity sensor: GP2A (same as Galaxy S and Nexus S)
Barometric pressure sensor: BOSCH BMP180 (first of its kind in a smartphone)
Triaxial acceleration sensor: BOSCH BMA250
Triple Axis MEMS Gyroscope: InvenSense MPU3050
Fuel Gauge (algorithm to track battery's state of charge): MAXIM MAX17040
Misc. internals
Facial recognition elements (Face Unlock): left eye, right eye, nose base, head, face
Available resolution for standard apps: 720 x 1184px
Refresh rate: 60Hz
LCD Density: 320
Default display color depth: 32bit
Camera uses OMAP Ducati Subsystem, on-screen preview size is 768 x 576
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Android ROM: version 4.0.1, built October 13, 2011
Device name: Maguro
Main input/output type supported: Headphone, Speaker, Microphone, Bluetooth, Voice, FM, S/PDIF over HDMI; USB Audio DAC (digital-to-audio converter with USB input and stereo outputs) should also be supported
engadget, by Francois
borce_razor said:
CPU: Texas Instruments OMAP4460 (same as the Droid RAZR and Archos G9 tablets), 2047.7 BogoMIPS
Click to expand...
Click to collapse
great for confirmation. This is what we have been researching
USB Switch: Fairchild semiconductors fsa9480 (industry standard)
Click to expand...
Click to collapse
This means 301kohm resistor will work (if wired internally) and we can also get 619Kohm resistor UART output as well. This is awesome. No changes to my setup needed.
Linux kernel: 3.0.1 compiled for SMP with voluntary kernel preemption for best interactivity
Click to expand...
Click to collapse
Very interesting... I didn't think they had a 3.0 mobile kernel yet. This is good to know. It may need a new version of the SuperUser binary compiled for it.. Many of the currently existing binaries we use may break.
Thanks! And thanks Supercurio!
I'm definitely on board. What's the goal? ~$1,500?
caffeineighted said:
I'm definitely on board. What's the goal? ~$1,500?
Click to expand...
Click to collapse
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
u make a awesome point.
AdamOutler said:
We're not asking for money yet. I'd rather not ask for money at all. I don't like working with that. Money makes things complicated. I'm a horrible businessman, I realize this... I could capitolize on this.. I don't want to deal with money though.
I'm hoping that someone will donate one for research -or- gets one with a warranty which they can blindly let me borrow for a day or two.
Now I realize that it seems underhanded to warranty a device after destroying it, but keep in mind... This modification has potential to help people who would have warrantied their device in the first place... If this modification keeps just 2 people from sending their device in for service, the manufacturers and warranty providers begin saving money for each UnBrickable Mod performed. The users have less to worry about when flashing ROMs. The developers have less stress about bricking their device while developing.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I897 using XDA App
I'd like to also point out that the service manual on the i9000 instructs the service centers to put the device into download mode and download firmware. If the firmware flash fails then it's hardware damage and the board has to be replaced.
Ergo, a bad software flash = a bad board and the board gets replaced
I use i9000 as an example because i9000 is the only example we have of a Galaxy class device service manual.
This is great im so glad there are already devs working hard on making this a reality, im selling my EVO 3D ASAP so i can get this phone as soon as its released!
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
i9100 service manual
borce_razor said:
i9100 service manual
Click to expand...
Click to collapse
I declare and ordain this as understated post of the week.
AdamOutler said:
I declare and ordain this as understated post of the week.
Click to expand...
Click to collapse
with simple words, useful or not ?
ydaraishy said:
If there's a fastboot mmc erase function, won't that simply be enough to get it into USB boot mode?
Click to expand...
Click to collapse
Yeah... but if you erase fastboot than you're screwed
Also, rumor has it that this device will have locked bootloaders... this will help to unlock them.
borce_razor said:
with simple words, useful or not ?
Click to expand...
Click to collapse
Yes
Hello
It is possible to use a nfc scanner in the Samsung Galaxy S3 to scan microchip that like in our pets? I try to scan a one of the microchip, but phone don`t do anything with it. It not giving any information or "beep" - connection sound. It is possible to scan it with any software?
As far as I know those are LF RFID chips. Maybe there are newer types who operates on HF (13.56mhz).
Sent from my GT-I9300 using xda app-developers app
You will likely have little luck there. RFID implants for animals have been around since the 1990s and there are several incompatible product lines of them (each requiring it's own reading device). Those implants are merely transponders in the 100 kHz range. They are designed to be powered up by the reading device and just beam back the serial number, they have in their ROM. NFC, builds on RFID, but is standardized. It allows two way communication and larger tags can hold several kilobytes of data. The bigger datastorage mandates that data is exchanged at a higher frequency (10 MHz range) in order to do it in the same time. Different frequencies require different antennas. Different antennas mean more hardware cost. So ... there you have it.
onyxbits said:
You will likely have little luck there. RFID implants for animals have been around since the 1990s and there are several incompatible product lines of them (each requiring it's own reading device). Those implants are merely transponders in the 100 kHz range. They are designed to be powered up by the reading device and just beam back the serial number, they have in their ROM. NFC, builds on RFID, but is standardized. It allows two way communication and larger tags can hold several kilobytes of data. The bigger datastorage mandates that data is exchanged at a higher frequency (10 MHz range) in order to do it in the same time. Different frequencies require different antennas. Different antennas mean more hardware cost. So ... there you have it.
Click to expand...
Click to collapse
Ok, and what i must do to read it?
fumberas said:
Ok, and what i must do to read it?
Click to expand...
Click to collapse
To read it with you NFC phone: Nothing, can't be done. Those tags would need to work with 13.56Mhz.
If you want to read it, buy the corresponding RFID reader.