curious if anyone has flashed any of the asian ROMs and found the FM radio chip in our VIbrant?
IIRC its not a software issue, the vibrant doesn't have the hardware. Though it wouldn't be the first time an FM radio was hidden in a phone.
Sent from my SGH-T959 using XDA App
was hoping it had been found to still be there
I thought the same chip by Broadcom was used in all Galaxy S variants that integrates BT, GPS and FM radio
http://www.intomobile.com/2010/02/1...-with-media-playback-and-recording-functions/
I really have no idea about the hardware, but maybe that's why there is problems with the GPS, they didn't use the chip that has the BT/GPS/FM in it and used something else that took out the FM part and screwed up the GPS. Just a wild off the wall speculation.
there was an initial post by TravUK identifying the chipset as the Broadcom BCM 20751 and that is a 3 way chip (BT/GPS/FM)
but later he corrected that as a mistake - others found in the UK version of the i9000 and the US Tmobile delivered Vibrant (T959) and i believe in the AT&T Captivate, that the chip was a Broadcom 4751, which is a singular function chip, GPS only
so the FM chip must reside by itself or with the BT chip
I guess without doing the full autopsy we won't know what chipset they used unless someone who knows inner land of Samsung can leak it - bummer, I wish there was dmesg or similar output that you can parse to get the idea of the hardware used.
As said the BCM 4751 is the gps chip, not the aforementioned 20751. However, the phone still needs a wifi/bluetooth chip, and from one of the captivate threads I believed it was identified as the BCM4325, which also has fm capability. I think it is the only broadcom chip with bluetooth 3.0 and wifi b/g/n. So fm has to be on the chip. Whether or not everything is still connected on the pcb is still a question, but there doesn't seem to be any reason for samsung to have changed anything if they're still using the same chips.
Even if the chip supported FM, there is a lot more to it in terms of powering those circuits, integrating them into the audio circuitry, and providing leads for an antenna. Even if you could "activate" the chip you may not be able to pick up anything or hear anything.
Related
Hi there,
I can't find detailed information about the i9000 chipset
What I know :
S5PC110 SoC which includes :
CPU : ARM Cortex-A8 1 Ghz
GPU PowerVR SGX540
S5PC100 spec sheet <=== Not the right SoC we have in our beloved smartphones ^^
block diagram: (can't insert image as a new user)
www dot samsung dot com/global/system/business/semiconductor/product/2010/5/25/213794S5PC100.gif
Detailed spec sheet: (can't insert link as a new user)
www dot samsung dot com/global/business/semiconductor/productInfo.do?fmly_id=834&partnum=S5PC100&xFmly_id=229
Click to expand...
Click to collapse
What's missing :
GPS/Wifi/BT/Radio/FM components.
Anyone got information regarding these components ? or maybe others interesting to mention here ?
Thanks
EDIT : quoted the links which points to S5PC100, as S5PC110 datasheet is not publicly available yet.
Dissasembling
(www).careace.net/2010/06/09/disassembly-of-the-samsung-galaxy-s/
GPS FM BT (not confirmed) broadcom BCM20751 (i suspect inside Samsung B-B23)
DAC wolfson WM8994
Thanks for your reply.
some more research pointed me to another broadcom component that may be embedded into SWB-B23 => BCM4329 (but this one has no GPS)
These IC seems to embed an FM transmitter as well. I'd like to confirm this point, as it may be interesting to exploit.
Doesn't already have a built in radio app? Mine does
You have an inbuilt FM radio app and the SGS has emition capabilities too. I love listening to my mp3 on my car
slightly off-topic but anyway...
I must have missed something then.
How do you transmit audio played by Samsung mp3 player on your SGS to your car audio system ?
I would love to know how to transmit my mp3s and audiobooks to my car radio fm tuner too!
Sent from my GT-I9000 using XDA App
must be secret function since I can't find it in the manual/review site ?
Probably through bluetooth..?
Unfortunately my car audio system does not receive anything else than AM/FM frequencies..
dmulligan said:
I would love to know how to transmit my mp3s and audiobooks to my car radio fm tuner too!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
i do it via bluetooth, or as an USB mass storage device.
it depends on your Car's Deck Receiver
Alijones implied that he uses the fm transmitter rumoured to be in the i9000.
Sent from my GT-I9000 using XDA App
nooooo the SGS i9000 comes with a FM radio to listen, not to transmit.
http://www.samsung.com/global/busin....do?fmly_id=834&partnum=S5PC100&xFmly_i d=229
667MHz (O/D) Operating Frequency at 1.2 V
Click to expand...
Click to collapse
isnt it 1GHz?
667mhz is at 1.2V
No one said you can't up the voltage to 1.22v or something like that and get a higher frequency.
Also, the link is a bit wrong.
It's leading to the S5PC100, while in the galaxy S we have the S5PC110
You're right... the link is wrong... sorry for this, i'll remove it ASAP.
Btw S5pc110 is not publicly available yet... we'll have to wait.
Just looked at a teardown report of the Epic 4G (hat tip to los1223). It appears that the Epic 4G does not even use the same GPS chip as its GSM cousins. This is certainly news to me, because reading the tea leaves I have assumed that all Galaxy S phones shared the same GPS hardware, even if the software was in different stages of development and debugging.
According to the teardown, the Epic 4g uses the multifunction Qualcomm QSC6085 for GPS functions. (Presumably this is because of the CDMA radio, so the Fascinate design is probably similar.) Previous analysis the GSM variants, based on the international I9000 model as well as the Captivate and the Vibrant, showed they use a Broadcom BCM4751 chip.
This would explain why the symptoms of the GPS problems on the Epic, and the firmware modules, are not the same as those on the GSM variants. But amazingly, it seems that Samsung managed to screw up two different GPS designs in two different ways.
Is one chip better than the other?
I know my co-worker's TMobile Galaxy S (Captivate, Fascinate, Masticate...whatever) just recently received the GPS update and he states it is now spot on and very quick to lock.
Didn't ask about any hard coded location, though, like ours. I'll have to do that on Monday.
Thats ame gps as the motorola droids use I think
The new QSC6085 features include:
Support for EV-DO Rev. A with backward compatibility to EV-DO Rel. 0 and CDMA2000
Equalizer technology for increased EV-DO data throughput
Powerful GPS location capabilities, including gpsOne(R) multi-mode hybrid assisted GPS technology, enabling a broad variety of location services such as navigation, social, safety and security applications
Up to 3 megapixel camera support with anti-shake capability
15 fps video encode and decode capability
72-voice polyphonic ringtones with support for multiple audio codecs
Multiple technologies to improve network capacity, including QUALCOMM Linear Interference Cancellation (QLIC(TM)) with pilot and traffic cancellation, and Fourth Generation Vocoder(TM) (4GV(TM)), published as the EVRC-B 3GPP2 standard codec, which gives network operators the flexibility to prioritize voice quality or network capacity
Support for multiple bands, including 800 Mhz, 1900 Mhz and the AWS band (1700/2100 Mhz), with mobile receive diversity
Cost-effective 65 nm process technology and a 12 mm x 12 mm package size
othan1 said:
Is one chip better than the other?
Click to expand...
Click to collapse
Let me first lead off by same I'm not an expert on chipsets. That being said, I did a lot of research on the QSC6085 when I was looking to see if it supported TV out or if we were never going to have that feature (I can honestly tell you that I don't know enough about this stuff for a conclusive answer, but right now I'm guessing no for the 3.5mm port).
Anyhow, the QSC6085 is an integrated processor that does a lot of this with one chip rather than having multiple chips that do many individual things. The purpose was to reduce costs and potentially, create power savings as well.
The other galaxy S phones (at the least the GSM ones) have a dedicated GPS chip to where the Epic's/Fascinate's baseband modem (QSC6085) handles all kinds of things, including GPS.
Other devices that use the QSC6085 (like the Droid, Droid 2 and my Sierra Wireless modem) do not seem to have the same GPS problems as the Epic/Fascinate which tells me it's a Samsung implementation issue and not a problem with the chip.
It's either the software (highly likely, no reason for us to not get a fix within seconds even if it is horribly inaccurate) or an insensitive GPS antenna. The GPS antenna is easily spottable on the Vibrant and Fascinate. It's covered by black tape next to the SD card on the Fascinate, it should be the same on the Epic 4G.
heygrl said:
It's either the software (highly likely, no reason for us to not get a fix within seconds even if it is horribly inaccurate) or an insensitive GPS antenna.
Click to expand...
Click to collapse
the snr numbers and the cold start fix tell us it is both, mainly software though.
All current Note users, anyone here can tell me if any of the currently released Note's have NFC? Also read a spec sheet somewhere stating it to be optional, any chance we can get this as an add-on accessory?
I'm also keen to find this out. The UK devices have NFC listed as 'optional' which doesn't really reveal anything useful. Can anyone who has one identify whether the capability is there but not enabled or just not present? It would be nice to think that the devs here could enable it if it was available.
NFC: Optional
It will be supported by a connection through the micoUSB *sigh*
However, the Korean models will get internal NFC and LTE (4G) support. I was going to hold out for that model but aterwards I learned they will not have the Exynos but instead a Snapdragon (Qualcomm S3) chip instead.
I prefer an ARM chip (TI OMAP, Samsung in-house, ST-Ericsson, Nvidia Tegra) rather than Qualcomm = usually more devices, better performance, less battery drain, fewer driver issues, possible to recylce drivers from one device to another.
Hi,
I am wondering whether the Galaxy S4 (I9500, specifically) can be used as a development board.
By this I mean something like the Raspberry Pi, BeagleBone, etc.
The I9500 already has powerfull CPU, 2G RAM and lots of ROM. What is missing (if at all) is:
# I/O pins. I am sure the exynos 5 has lots of I/Os, but the question is how many of them are accessible on the I9500 board? Looking at techinsights.com teardown article, the motherboard looks very dense and no I/Os seem to be accessible, but hopefully I a, wrong.
# Ability to run Android 4.0 (or any other version) with minimal resources. For example, is it possible to run Android in text-mode so that we leave the RAM and CPU power for the application we want to run/use?
# Availability of replacement parts individually. In such case, we would "buy" a blank motherboard with only the CPU, RAM, ROM and PMIC chips. All other chips (all of networking) are irrelevant. This should not be too expensive(or is it?). This poses another question about the ability to modify Android so that it still work without having the other chips on board.
BTW: Where is the GPS module? It is not mentioned in the teardown article.
Regards,
1ccbf
Many users report that FYT boards (Android 8 Joying) give a much better navigation performance than PX5 MTCE boards (Android 8 Dasaita, Wondefoo etc.) Despite that latest PX5 MTCE boards (Rev. 8.0) all use a performant, latest generation U-Blox M8030 GNSS chip.
Want to find out why, so, as a first question:
Does somebody know which on-board GPS chip is used on PX5 FYT boards (the ones which power the recent Joying head units)?
Just because I'm afraid you may post this question in every thread on the forum unless someone answers....here you go http://www.icofchina.com/d/file/xiazai/2016-12-05/b1be6f481cdf9d773b963ab30a2d11d8.pdf
You will notice that the specs are worse than that of the UBLOX but when considering GNSS performance it's not all about the chipset. They (MTC) could have used a XO instead of a TCXO which would make the performance very poor. Alternatively their RF impedance matching may be poor. There are a number of reasons why the FYT implementation could be better.
px5:
9600 port speed.
1HZ.
SBAS nad Glonass not workig (nem működik)
MTC Adroid API bad (rossz, nincs jól implementálva)
emre33 said:
px5:
9600 port speed.
1HZ.
SBAS nad Glonass not workig (nem működik)
MTC Adroid API bad (rossz, nincs jól implementálva)
Click to expand...
Click to collapse
Jut have contacted a big PX5 MTC reseller on facebook, he was very helpful and there are good chances that he’ll forward our concerns to the manufacturer.
BTW, please note that using U-blox U-center application the chip performs really decent, even good, just a bit less performant compared to the crystal-driven, high-end Neo M8N + a fairly expensive, mid-range professional antenna. So I don’t think there would be necessarily a bad hardware installation, Android 8 is the faulty piece here.
I’ll keep you informed once I find new information.
(Üdv, és inkább folytassuk 100%-ban angolul, hogy többiek is értsék.)
kesztió said:
Jut have contacted a big PX5 MTC reseller on facebook, he was very helpful and there are good chances that he’ll forward our concerns to the manufacturer.
BTW, please note that using U-blox U-center application the chip performs really decent, even good, just a bit less performant compared to the crystal-driven, high-end Neo M8N + a fairly expensive, mid-range professional antenna. So I don’t think there would be necessarily a bad hardware installation, Android 8 is the faulty piece here.
I’ll keep you informed once I find new information.
(Üdv, és inkább folytassuk 100%-ban angolul, hogy többiek is értsék.)
Click to expand...
Click to collapse
I highly doubt that Android 8 is doing anything wrong. It interfaces with the chip using NMEA protocol. So old and so standard that it would be a challenge to get wrong. The only thing Android may be messing up is feeding ephemeris data to the chip so that it can hot start. In any case that will not affect the tracking capability.
emre33 said:
px5:
9600 port speed.
1HZ.
SBAS nad Glonass not workig (nem működik)
MTC Adroid API bad (rossz, nincs jól implementálva)
Click to expand...
Click to collapse
He is asking for the FYT model, not the QD model.
Glonass works fine on the FYT model, not on the QD model.
looxonline said:
I highly doubt that Android 8 is doing anything wrong. It interfaces with the chip using NMEA protocol. So old and so standard that it would be a challenge to get wrong. The only thing Android may be messing up is feeding ephemeris data to the chip so that it can hot start. In any case that will not affect the tracking capability.
Click to expand...
Click to collapse
Won’t be so sure. How you can explain that I can select any constellations I want from U-center and the satellite data (including SBAS corrections) work as expected – but switching to any Android GPS test application instantly „kills” Glonass and SBAS satellites? Interesting that (in conformity to the USING GNSS RAW MEASUREMENTS ON ANDROID DEVICES white paper) a new location API is implemented since Android Nougat – and exactly this was the moment when things suddenly went wrong on MTC PX5 systems (users report that on Marshmallow everything was OK).
looxonline said:
Just because I'm afraid you may post this question in every thread on the forum unless someone answers....here you go
You will notice that the specs are worse than that of the UBLOX but when considering GNSS performance it's not all about the chipset. They (MTC) could have used a XO instead of a TCXO which would make the performance very poor. Alternatively their RF impedance matching may be poor. There are a number of reasons why the FYT implementation could be better.
Click to expand...
Click to collapse
Thanks a lot for your help, you received the thanks point.
See my remarks for emre33 about the possibly wrong hardware implementation of the U-Blox M8030.
looxonline said:
I highly doubt that Android 8 is doing anything wrong. It interfaces with the chip using NMEA protocol. So old and so standard that it would be a challenge to get wrong. The only thing Android may be messing up is feeding ephemeris data to the chip so that it can hot start. In any case that will not affect the tracking capability.
Click to expand...
Click to collapse
"Android" does not interface with the GPS at all. Its the HAL's job to interface with the hardware. It is the vendor's responsibility to write a HAL for their hardware, and as you can imagine, the budget chinese hardware vendors don't do that great of a job at that. The HAL uses callbacks to feed data into Android.