Related
Hi all.... this is not your usual "I want to listen to FM on my otherwise unsupported ROM" request. What I'm requesting I think would be far more interesting, and if applied properly, could benefit many makes and models of phone. For that reason, maybe this belongs in an even more general forum, but I'm starting here because this is the phone I have and I don't know just how many other models use this same hardware.
I see that the HTC Doubleshot / T-Mobile MyTouch 4G Slide, along with several other phones, has a BCM4329-B1 radio chipset. This chip is reported in many places to be capable of not only FM Radio receive but also transmit. Unfortunately, that's as far as anyone goes with listing what it's capable of doing. Partly because of this (and partly because of search overload or maybe me not knowing what terms to use in my search), I can't find specs enough on the chip to know the full range of frequencies it receives. I have seen enough to imply that the same chip handles bluetooth, wifi, as well as FM broadcast band. Something as widespread as that might just be capable of extending receive capabilities outside of the usual broadcast band (for instance, maybe it can be used as a "police scanner" of sorts).
If nothing else, I think it would be fantastic to have an APK that can take MP3s or perhaps any kind of streaming media and retransmit it, low-power of course, to a nearby FM radio set to receive on the same frequency (much easier to get e.g. Pandora into every room in my house this way). I just figure if I'm going to ask for this I may as well ask for the world, right? Of course I don't expect a multiband ham radio to pop out of my phone, but if I could use it to maybe pick up a wireless microphone at 181 MHz, or act as a frequency meter (similar to WiFi Analyzer apk) for low-power transmitter troubleshooting, that would be phenomenal. Icing on the cake would be the ability to record what it receives, assuming it receives outside of band (record-to-file equals record-to-stream, here, meaning also record-and-serve-on-a-wifi-or-4G-link).
Any takers?
I wish I could offer time and skill but I just don't know enough about development nor does my life lend much in the way of free time for hobbies... I'm hopeful someone else has already thought of this.
Regards and TIA
cj chitwood said:
I'm hopeful someone else has already thought of this.
Click to expand...
Click to collapse
I have a unique position on this, because it's a problem I run into consistently.
When i'm doing this and can't hear anything around me, and the camera gets no music when it records.
The only good way to deal with this without getting a noise disturbance violation at night is to use a couple of androids to sync all the music up - person(s) on camera has a device with headphones, sync up with the one playing music next to the camera.
There is no smooth way to handle that in random locations all over the place, way out of wifi range and possibly with no cell service as well.
There is no easy answer but there are ways of making it work. I'd write up a guide on how we do it now, but being down to only one device I can't run through it in front of me now, i'll have to wait until I see my friend again so we have two or 3 machines to use at once or I get my hands on another one (hopefully soon - this is my biggest aggravation with being temporarily down a device, no bluetooth or interacting with another device testing)
Since someone else in interested in the exact same issue here i'll take the time at some point to sit down and recap what worked or didn't work and link to the things that did. Have to be another day though, i'm pretty tired now and gonna catch some sleep soon.
Anyone else put effort into something like this?
Blue6IX said:
I have a unique position on this, because it's a problem I run into consistently.
When i'm doing this and can't hear anything around me, and the camera gets no music when it records.
Click to expand...
Click to collapse
ah HAH! I WONDERED what you had for a "day" job!
Joking aside though, I'm surprised out where there's no cell signal they worry about noise violations... Here, there's a time limit (15 minutes at a time with at least I think a 5 minute break IIRC) but you can make noise pretty much any time at night. Just don't wake the neighbors up and nobody complains
Thanks for posting your thoughts. I'm willing to test insomuch as it won't risk the device. I just don't know enough to program my own app for this...
...if it's even possible: a guy at work reminded me today that just as CPU manufacturers use the same chip designation to indicate a CPU with and without features like L2 cache, phone mfgrs like Samsung (he has a not-so-new Galaxy phone) have been known to use this same chip with the FM radio capabilities completely absent to the point that someone in the know actually removed the chip from his device, hooked it up on a bench, and was completely unable to get it to do anything FM radio related. It may be that while some iterations of the chip overall are capable of being made with transmit, that it's quite likely transmit itself was left out of the hardware itself.
I'd still like to see if it's possible. Maybe if the chip identifies itself in the OS, we can see how it does, and maybe it will hint at whether transmit was included or not.
Found this:
http://forum.xda-developers.com/showthread.php?t=1042094
Which implies this was originally touched upon before the Evo... However, it also provides enough info as to say the only FM receive/transmit this chip will do OOB is FM broadcast band (76-108 MHz). Still, it can transmit...
Bump!!!!
That would be ill if you could transmit on FM band ...... anyone make any progress?
Although why not just stream via bluetooth? what would the advantage to transmitting on fm band be other than epic nerd street cred
Some_dude36 said:
Bump!!!!
That would be ill if you could transmit on FM band ...... anyone make any progress?
Although why not just stream via bluetooth? what would the advantage to transmitting on fm band be other than epic nerd street cred
Click to expand...
Click to collapse
Not all devices support a2dp
Sent from my RubiX ICS Infused using Tapatalk
Fm xmit might go farther, especially if the right antenna can be made.
Fm can be simultaneously received by multiple devices. Think here tv-out to a small portable projector showing the latest theatrical releases in full composite glory and stereo sound out of the viewers' battery operated headphone radios all while offering 4g data hotspot... :~/
Honestly, the real reason for me is the fm radios in the garage are louder than the portable computer speakers I've been playing Pandora through and I hate the dinky transmitter that came with my wife's ipod because it only does 4 stations high in the band. This would make that much easier (and I'm sure many others would find a use for this).
--
Sent from my Android ”phone”:
HTC DoubleShot /T-Mobile MyTouch 4G Slide running Bulletproof
FM Transmit:
I get asked this question regularly, and my response is generally: "Forget about it, almost no Android phones connect the FM Transmit pins anywhere useful".
But a few months ago a helpful person sent me an HTC FM transmit app. Apparently it was meant for the T-Mobile/HTC Mytouch 4G, and apparently that device is supposed to have the transmit pins connected.
I have no idea (yet) if that is true or if this also applies to the "Slide" variant.
I'm sure this will only work on ROMs that use the Broadcom proprietary Bluetooth stack and that have sufficient parts of Sense present. IE, a stock or stock derived ROM. It probably requires Froyo or GingerBread.
If anyone has or can load such a ROM and wants to try, and will commit to reporting their results, email me at mikereidis AT gmail.com and I'll send the APK.
Thanks...
mikereidis said:
FM Transmit:
...
But a few months ago a helpful person sent me an HTC FM transmit app. Apparently it was meant for the T-Mobile/HTC Mytouch 4G, and apparently that device is supposed to have the transmit pins connected.
I have no idea (yet) if that is true or if this also applies to the "Slide" variant.
Click to expand...
Click to collapse
I had one tester who reported success, but on the non "Slide" version. Details and a link to the app are here: http://forum.xda-developers.com/showpost.php?p=31328070&postcount=4391
mikereidis said:
I had one tester who reported success, but on the non "Slide" version. Details and a link to the app are here: http://forum.xda-developers.com/showpost.php?p=31328070&postcount=4391
Click to expand...
Click to collapse
I installed it on a stock sense rom on the MT4GS and the app loads, but when I press transmit it just stays on the "FM Transmitter turning on" so I'm guessing that means that it won't work...
marc12868 said:
I installed it on a stock sense rom on the MT4GS and the app loads, but when I press transmit it just stays on the "FM Transmitter turning on" so I'm guessing that means that it won't work...
Click to expand...
Click to collapse
Thanks for trying.
That's exactly what happens on my Desire HD and Desire Z running stock derived Gingerbread.
The success report for the non-slide phone was on Android 2.2.1. I don't know if 2.3.x is possible, but I'll find out when I get my myTouch 4G HD hopefully by the end of the week.
I expect to add a transmit test function to my FM app Spirit at some point, and it will then likely work on any ROM, though audio routing could be a challenge.
marc12868 said:
I installed it on a stock sense rom on the MT4GS and the app loads, but when I press transmit it just stays on the "FM Transmitter turning on" so I'm guessing that means that it won't work...
Click to expand...
Click to collapse
I get the same exact scenario myself. I even went to the extent of making sure I had some audio playing to make sure that it wasn't just the fact there was no audio and it might have been waiting for it. still no joy. It appears that the slide variant of the MyTouch 4G does indeed not have the Fm transmit pins connected. then again, I have not looked at my logs yet, so I do not know exactly what it has been doing.
--
Sent from my Bulletproof Swiss Army Doubleshot using the XDA app and stock voice to text.
Hope this lolcat helps
https://www.box.com/shared/6parlnbt3j3y6o5fgopq
--
Sent from my Bulletproof Swiss Army Doubleshot using the XDA app.
The logcat doesn't show any errors with executing the FM Transmitter app. What I can see is the FM Reciever gets activated on the logcat. I should say that FMTx & FMRx cannot be run in the same time.
1. So the error could be the FMTx got killed by the FMRx intentionally.
2. BCM4329 driver doesn't have the code to interact with the FMTx chipset.
If the mt4gs does indeed have FMTx on it's chipset then I'm sure it's working/connected on the board else we wouldn't have any FM Radio on our device.
Bluetooth, FMTx & FMRx is located in the same part of the chipset. One dies then all of them dies.
Now anybody here could link me to the stock kernel of the device which made this work? I could look at the bcm driver on that kernel and maybe I could hook it up on the mt4gs kernel to make it work.
---------- Post added at 11:51 AM ---------- Previous post was at 11:23 AM ----------
Ok guys confirmed! Hardware should be capable of transmitting fm frequencies.
Looking at the data sheet FM Tx & Rx are bidirectional which means as long as FM Rx is working so will be Tx.
{
"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"
}
Now the problems left would be the driver & the Hardware Abstraction Layer(HAL). Since we already have an FM Tx app.
LOLcat ?
Yes, the 4329 has TX inside, no problem, but I'm pretty sure it can only transmit or receive at one time, never simultaneously.
Every time I've looked at the internals of the Broadcom proprietary Bluetooth stack I've seen the transmit function, and HTCs implementation tends to include that, and their own mods.
The biggest issue should be whether or not the Transmit pins are connected to the headset. Heck, most of the phones with this chip don't even connect the receive antenna pins. (IE no FM radio whatsoever, grrr, what a waste.)
That said, I'm not quite sure why the TX app hangs on most phones, other than the plain myTouch 4G. There might be some difference and I hope to get to the bottom of it.
And eventually, I should be able to make Transmit work on any BCM4329 device with the transmit antenna pins wired, but there will likely be very few such devices.
And before anyone asks, it will likely be completely infeasible to make the hardware mod needed, same as for FM receive antenna pins.
I see 28 downloads of the FMTx app now.
mikereidis said:
LOLcat ?
Yes, the 4329 has TX inside, no problem, but I'm pretty sure it can only transmit or receive at one time, never simultaneously.
Every time I've looked at the internals of the Broadcom proprietary Bluetooth stack I've seen the transmit function, and HTCs implementation tends to include that, and their own mods.
The biggest issue should be whether or not the Transmit pins are connected to the headset. Heck, most of the phones with this chip don't even connect the receive antenna pins. (IE no FM radio whatsoever, grrr, what a waste.)
That said, I'm not quite sure why the TX app hangs on most phones, other than the plain myTouch 4G. There might be some difference and I hope to get to the bottom of it.
And eventually, I should be able to make Transmit work on any BCM4329 device with the transmit antenna pins wired, but there will likely be very few such devices.
And before anyone asks, it will likely be completely infeasible to make the hardware mod needed, same as for FM receive antenna pins.
I see 28 downloads of the FMTx app now.
Click to expand...
Click to collapse
Hi! As I said if FMRx works then should be FMTx. So it's clear now that hardware wise FMTx should be fully working. Now software wise that I still don't know.
Regarding antenna I'm not quite sure if it's really necessary? You see I have a device here Nokia N900 which has a built in FMRx & FMTx feature which was really implemented by nokia. And I already dissassembled it alot of time to the point I know each and every part of it And I can activate it's FMTx without the need of a headset. I just need to play the music player select the Transmit FM option and select the frequency I want then I can channel the music to any radio reciever 1 to 2 meters away from me without the need of an antenna.
http://wiki.maemo.org/N900_Hardware_FM_Radio_Transmitter
Riyal said:
Hi! As I said if FMRx works then should be FMTx. So it's clear now that hardware wise FMTx should be fully working. Now software wise that I still don't know.
Regarding antenna I'm not quite sure if it's really necessary? You see I have a device here Nokia N900 which has a built in FMRx & FMTx feature which was really implemented by nokia. And I already dissassembled it alot of time to the point I know each and every part of it And I can activate it's FMTx without the need of a headset. I just need to play the music player select the Transmit FM option and select the frequency I want then I can channel the music to any radio reciever 1 to 2 meters away from me without the need of an antenna.
http://wiki.maemo.org/N900_Hardware_FM_Radio_Transmitter
Click to expand...
Click to collapse
Yes, the CHIP has all the hardware needed. But the most important "hardware part" is the connection of something to the FM Tx antenna pin. Even if the pins aren't grounded (Which tends to kill all chance) and left floating, the chips are inside "RF shields" will just about kills any chance of reception/transmission.
Every radio receiver or transmitter MUST have an antenna. On some devices it may be internal and you don't see it, but it's definitely there. On old AM radios internal antennas were a LONG piece of wire wrapped around a bar (ferrite?).
In some cases, an antenna is just circuit board traces. For high frequencies, such as cell or GPS or Bt/WiFi only very small antennas are needed. For lower frequencies, like FM around 100 MHz, the best antennas are roughly the length of headset cables.
This could possibly be coiled and wrapped around something and hidden inside the phone. But it's there, no way around needing an antenna.
I have some phones that do remarkably well with no wired headset for an antenna. But an "antenna" of sorts is still there, even if it's only several millimetres to centimetres of circuit board traces meant to connect the antenna pins on the chip to the headset.
Yeah, LOLcat. when you go into command prompt, "adb lolcat" is the same as "adb logcat". Apparently, the team at Google said "logcat" so often and so fast it sounded like "lolcat" to them.
Mikereidis is correct, you do need an antenna, even if it's hidden. Otherwise you have extremely high standing wave ratio (SWR) that will eventually fry your transmit amplifier. This is basic radio theory at play, that one learns when becoming FCC licensed radio operators like General Radiotelephone Operator or Amateur Radio Operator (I'm the latter of these, KE4EDD, though I haven't picked up a transceiver in about a decade).
Like he said, it's not as critical at higher frequencies because wavelength (and therefore necessary antenna length) is shorter and can be hidden inside the device (take the cover off your MT4GS and you'll see three separate antennae all up around the camera lens -- they're just thin sheets of metal on this phone).
Still, the pinout of the chip itself is important. This I know nothing of as I haven't seen it. either way, if the spec sheet says Rx and Tx work on the same connections (e.g., they both require the same pins to be "high" in order to physically activate either mode) then all we need is to get the HAL and driver set up. I know nothing of this as well. Wish I could help. All I can do is offer my phone's lolcat services.
On that note, I received a <sisa:###:##:#::#> text message this morning, appears that it's a T-mo thing, that T-mo is trying to update my phone (which is running a custom ROM), and now my digitizer doesn't work, so I may need to hold off on even the lolcat until I get it fixed.
cj chitwood said:
"adb lolcat" is the same as "adb logcat". Apparently, the team at Google said "logcat" so often and so fast it sounded like "lolcat" to them.
Click to expand...
Click to collapse
Learn something new every day. But I think it was more a joke about the very popular meme than mis-hearing: http://en.wikipedia.org/wiki/Lolcat
cj chitwood said:
you do need an antenna, even if it's hidden. Otherwise you have extremely high standing wave ratio (SWR) that will eventually fry your transmit amplifier. This is basic radio theory at play, that one learns when becoming FCC licensed radio operators like General Radiotelephone Operator or Amateur Radio Operator
Click to expand...
Click to collapse
I know the theory, but I've never believed that low power, under 100 mw transmitters get damaged too often. But I imagine a final output transistor on a chip can't take as much abuse as an external one.
cj chitwood said:
Still, the pinout of the chip itself is important. This I know nothing of as I haven't seen it. either way, if the spec sheet says Rx and Tx work on the same connections (e.g., they both require the same pins to be "high" in order to physically activate either mode) then all we need is to get the HAL and driver set up.
Click to expand...
Click to collapse
Documents about these chips are "very secret". I can't even find much on Chinese sites that specialise in proprietary documents. The official vague block diagrams can't be trusted either.
But if the transmit and receive pins were the same pins, I'm pretty sure we would have achieved FM transmit long ago on the most popular Broadcom chips, on devices that support receive. That said, I think the much rarer Qualcomm Tavarua chips use the same pins, and there are no transmit reports on them.
I've looked at schematics of some phones, and I've seen FM antenna pins specifically labelled as "Rx", so that's another clue in favor of the idea that Rx and Tx pins are different. This might also be easier to achieve on the chip.
I wonder too if it's easier to achieve FCC etc certification if the hardware design specifically makes FM transmit impossible.
I'm certain it is easier to achieve, as long as they can certify to the FCC that no more than so many milliwatts will be pushed out. Then again, with as many transmitters as there are that are available to the public, it can't be that hard to do.
We keep talking about Tx and Rx pins. In my limited experience with chips, I'm wondering if these are antenna pins, or activation pins. I also wouldn't be surprised if it was that some chips have a mode select pin (high is one mode, low is another) that could be labeled both as Tx and Rx, and each mode requires a separate other pin to have a certain voltage on it to provide power for that section of the chip. Alternatively, to have two mode select pins, again whichever one is hot selects the mode, and the third pin provides power for both modes, and thus is labeled Tx Rx even if the mode select pin isn't attached.
Either way, if pinouts are so secretive about this, it's pointless to discuss pins because they literally could be anything. I think however that you having seen the innards and/or schematics of these devices means that you would know more than I as I have yet to even crack mine open
Oh and the lolcat thing... no, you really can type "adb lolcat" in command prompt and it runs a logcat. The explanation for this was literally that they said "logcat" so fast it sounded like "lolcat". I am fully aware of the meme, http://icanhascheezburger.com and have forwarded quite a few on to the wife even.
http://www.chipworks.com/blog/recentteardowns/2013/04/25/inside-the-samsung-galaxy-s4/
No mention of the known BCM4335 BT/WiFi combo chip yet, so clearly still preliminary.
Flagship phone day is here! If you see this message then we are still analyzing the device
...
Samsung N5VA101 Exynos 5 Applications Processor
Samsung KMV3W000LM-B310 NAND
Samsung K3QF2F200C-XGCE 2 GB DRAM
Samsung S2MPS11 Power Management IC
...
Samsung S2MPS11 Power Management IC
Wolfson WM5102e Audio Hub Codec
Intel PMB9820 Baseband Processor
Intel PMB5745 Baseband Processor
I274 U311 – likely Bosch BMP180 or STM 331 Pressure sensor – to be verified (shown)
Synaptics S5000B Touch Screen Controller (shown)
...
Broadcom BCM2079 NFC Chip (shown first)
Two Knowles S1039 Microphones (shown second)
Silicon Image SI8240BO Transmitter
Skyworks SKY77615-11
Maxim MAX77803
Murata SWC GKF48 Antenna Switch Module
Remember…we’re still working.
Click to expand...
Click to collapse
Anyone knows those chips:
Intel PMB9820 Baseband Processor
Intel PMB5745 Baseband Processor
It should be for GSM/3G but why two chips?
CQ7 said:
Anyone knows those chips:
Intel PMB9820 Baseband Processor
Intel PMB5745 Baseband Processor
It should be for GSM/3G but why two chips?
Click to expand...
Click to collapse
Article seems finished now and the 2nd has changed to "Intel PMB5745 RF Transceiver".
And I see the BCM4335 is in what they call "A nifty little WiFi Module" which also contains a Skyworks Front End Module.
iFixit teardown for AT&T version:
http://www.ifixit.com/Teardown/Samsung+Galaxy+S4+Teardown/13947/1
Repairability Score: 8 out of 10 (10 is easiest to repair)
anybody know if that flash chip (Samsung KMV3W000LM-B310) is potentially susceptible for SDS problem?
any other phone using this chip so far?
Diamond 2 owner said:
anybody know if that flash chip (Samsung KMV3W000LM-B310) is potentially susceptible for SDS problem?
any other phone using this chip so far?
Click to expand...
Click to collapse
I doubt they would knowingly get an SDS infected chip on the S4
so we just gotta wait and see if anything bad happens
what SDS problem means????
PLUG313 said:
I doubt they would knowingly get an SDS infected chip on the S4
so we just gotta wait and see if anything bad happens
Click to expand...
Click to collapse
can anybody explain SDS meaning?
aasim92 said:
can anybody explain SDS meaning?
Click to expand...
Click to collapse
sudden death syndrome
Hi,
i downloaded a few GPS test apps, and the best result i got was 15m.
How many satellites did you get, and how many meter accuracy?
How to improve GPS reception?
That's what I got
this is my test
PX5 Glonass Not use
He sees the satellites, but he does not use them
PX5 Glonass Not use
Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.
kesztió said:
Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.
Click to expand...
Click to collapse
This is the PX 5-2G HA unit Marshmallow ROM I own.
Upgrading the ROM of this unit to oreo.
And this is JOYING's FYT based PX5 unit.
It is obviously a problem of ROM that oreo ROM can not use GLONASS. If you want the accuracy of the position information downgrade to marshmallow or buy a FYT unit is early.
warata said:
This is the PX 5-2G HA unit Marshmallow ROM I own.
Upgrading the ROM of this unit to oreo.
And this is JOYING's FYT based PX5 unit.
It is obviously a problem of ROM that oreo ROM can not use GLONASS. If you want the accuracy of the position information downgrade to marshmallow or buy a FYT unit is early.
Click to expand...
Click to collapse
Thanks, Warata, but I still have some problems and questions.
1. The “good” configuration with Marshmallow on your photo still shows an accuracy as bad as 6 m. And no words about SBAS, Beidou or Galileo satellites.
2. I think the PX5 bord revision is very important: I have REV 8.0, something like this:
which is based on U-blox NEO M8, while REV 4.0 still uses U-blox 6 or 7. Are you sure they use all the same revision?
3. Is it safe to downgrade across different manufacturers but same PX5 board, same revision? If so, do you have the downgrade kit for Marshmallow in order to make me sure this is the problem? (It should be an update.zip of approx. 1 GB, I’d greatly appreciate if you sent me it by wetransfer, zoltan .at. studiorip .dot. com.)
4. The “native” U-blox application (u-center for windows, you can access the android unit by the U-blox droid center, if both are in the same TCP subnet) shows a bit different: Both GLONASS and GPS are used simultaneously, I can see 2 SBAS satellites, and things get even better if enabling the full power mode. Does it mean that the U-center can bypass the Android driver?
5. Wouldn’t be enough to change just the Android driver, not the whole OS? If so, do you have a clue, how the original U-blox Android driver can be purchased?
Thanks!
kesztió said:
1. The “good” configuration with Marshmallow on your photo still shows an accuracy as bad as 6 m. And no words about SBAS, Beidou or Galileo satellites.
2. I think the PX5 bord revision is very important: I have REV 8.0, something like this:
which is based on U-blox NEO M8, while REV 4.0 still uses U-blox 6 or 7. Are you sure they use all the same revision?
3. Is it safe to downgrade across different manufacturers but same PX5 board, same revision? If so, do you have the downgrade kit for Marshmallow in order to make me sure this is the problem? (It should be an update.zip of approx. 1 GB, I’d greatly appreciate if you sent me it by wetransfer, zoltan .at. studiorip .dot. com.)
4. The “native” U-blox application (u-center for windows, you can access the android unit by the U-blox droid center, if both are in the same TCP subnet) shows a bit different: Both GLONASS and GPS are used simultaneously, I can see 2 SBAS satellites, and things get even better if enabling the full power mode. Does it mean that the U-center can bypass the Android driver?
5. Wouldn’t be enough to change just the Android driver, not the whole OS? If so, do you have a clue, how the original U-blox Android driver can be purchased?
Click to expand...
Click to collapse
Photo 1 and Photo 2 are definitely the same HA unit. Only the difference in firmware. So I can assert that it is a firmware problem that GLONASS can not be used with oreo. PX5- 4G-KLD Oreo I purchased recently was also unable to use GLONASS.
I upgraded marshmallows to Oreo using the kumarai's upgrade kit.
https://forum.xda-developers.com/android-auto/mtcd-software-development/px5-oreo-rom-t3736950
I attempted to downgrade PX5-4G-GS oreo unit to marshmallow in the same procedure, but that did not work.
JOYING's FYT based unit is totally different on the same PX5, and both GLONASS and BeuDou can be used. However, other satellites can not be recognized.
Other questions are beyond my knowledge. Please wait for other respondents.
Please write
Official Dasaita forum: PX5 Android 8.0 Glonass Not use, Only GPS (USA) http://www.dasaita.com/bbs/viewtopic.php?f=4&p=108
eter711 said:
Hi,
i downloaded a few GPS test apps, and the best result i got was 15m.
How many satellites did you get, and how many meter accuracy?
How to improve GPS reception?
Click to expand...
Click to collapse
Its not really appropriate for GPS to output accuracy in a distance unit. What they output is a level of "confidence" that you are within the GPS's rated accuracy of the position being reported. You can't translate from that measure to a distance unit, so they make something up, usually based on a linear multiple of the rated accuracy.
For instance, it may give you a 50% confidence of being within 6 feet of the reported coordinates. Or it might give you a 90% confidence that you are within 6 feet. In either case, you could very well be within the 6 feet, and in fact, you could be "dead on", but it can only provide you with a probability. Despite that, it may present 50% within 6-feet as a 20 foot radius, or 90% within 6-feet as a 7 foot radius.
Don't get too overly hung up on it. If you want a better idea about how close the GPS reads to reality, open up google maps in satellite view mode, and see how close your physical location is to the center of the target based on landmarks.
---------- Post added at 05:23 PM ---------- Previous post was at 05:18 PM ----------
kesztió said:
Exactly the same problem, did you got any improvements in the meantime?
BTW the on-board navigation chip in PX5 boards is among the best ones: U-blox NEO M8. So it’s really unbelievable how this thing could happen.
Click to expand...
Click to collapse
Are you sure its really a U-blox? U-blox GPS receivers are among the most notorious for counterfeits. They use some crappy nobody brand gps receiver, and program its microcontroller to communicate as a u-blox.
https://www.u-blox.com/en/counterfeit-products-and-u-blox-brand-misuse
96carboard said:
Are you sure its really a U-blox? U-blox GPS receivers are among the most notorious for counterfeits. They use some crappy nobody brand gps receiver, and program its microcontroller to communicate as a u-blox.
Click to expand...
Click to collapse
I cannot be 100% sure but in U-center it declares itself to be at least M8030 (Actually nobody pretended to be NEO 8M, it was just my thought), and with a correctly placed antenna it indeed can get 100% inside a 2,5 m diameter deviation map, at least for 20-30 minutes. So co-operating by u-center is not an issue. (Though on just 2 Hz with multi-GNSS config (GPS + GLONASS) all GLONASS satellites suddenly die.)
The big problem is with all other 3rd party applications.
Here is the text output at startup:
19:05:23 $GNTXT,01,01,02,HW UBX-M8030 00080000*60
19:05:23 $GNTXT,01,01,02,ROM CORE 3.01 (107888)*2B
19:05:23 $GNTXT,01,01,02,FWVER=SPG 3.01*46
19:05:23 $GNTXT,01,01,02,PROTVER=18.00*11
19:05:23 $GNTXT,01,01,02,GPS;GLO;GAL;BDS*77
19:05:23 $GNTXT,01,01,02,SBAS;IMES;QZSS*49
19:05:23 $GNTXT,01,01,02,GNSS OTP=GPS;GLO*37
19:05:23 $GNTXT,01,01,02,LLC=FFFFFFFF-FFFFFFED-FFFFFFFF-FFFFFFFF-FFFFFFFD*2E
19:05:23 $GNTXT,01,01,02,ANTSUPERV=AC SD PDoS SR*3E
19:05:23 $GNTXT,01,01,02,ANTSTATUS=DONTKNOW*2D
19:05:23 $GNTXT,01,01,02,PF=3FF*4B
So do I have a counterfeit version or not?
*UPDATE* I forgot to update the baud rate to 19200 baud, that’s why the chip apparently hasn’t been able to face 2 Hz multi GNSS. That is, it’s almost sure that the chip is not NEO M8, “just” naked M8030, but at least I simply don’t think such a widely used board like PX5 uses fake M8030 chip. This is ridiculous.
warata said:
Photo 1 and Photo 2 are definitely the same HA unit. Only the difference in firmware. So I can assert that it is a firmware problem that GLONASS can not be used with oreo. PX5- 4G-KLD Oreo I purchased recently was also unable to use GLONASS.
I upgraded marshmallows to Oreo using the kumarai's upgrade kit.
I attempted to downgrade PX5-4G-GS oreo unit to marshmallow in the same procedure, but that did not work.
JOYING's FYT based unit is totally different on the same PX5, and both GLONASS and BeuDou can be used. However, other satellites can not be recognized.
Other questions are beyond my knowledge. Please wait for other respondents.
Click to expand...
Click to collapse
JOYING's FYT based unit on PX5 is also Android 8 Oreo or just an earlier version (Android 7 or 6)? (And what does FYT mean?)
kesztió said:
JOYING's FYT based unit on PX5 is also Android 8 Oreo or just an earlier version (Android 7 or 6)? (And what does FYT mean?)
Click to expand...
Click to collapse
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
https://forum.xda-developers.com/an...iew-joying-px5-2gb-android-version-8-t3789422
warata said:
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
Click to expand...
Click to collapse
Tying to understand.
The hardware (PX5 Rev. 8.0) is the same, just the software is different? Or there are different PX5 boards for FYT and QD respectively?
warata said:
FYT based PX5 is only Android 8.0. There is no compatibility with QD(MTCE) models.
See this thread for details.
Click to expand...
Click to collapse
Do you know which on-board GPS chip is used on FYT versions? For HCT this chip is U-blox M8030 but for FYT this can be different.
I present to you my way of improving GPS accuracy: using a Holux M1000, connected to navigation via bluetooth ( Bluetooth GPS apk from Market). I also tried U-Blox7, but the result is even worse than with the native receiver. HCT-PX5, rev.10.
The notion of "accuracy" in GPS is not nearly as straightforward as you may have been lead to believe. In fact, most of these GPS HAL's will be fudging the accuracy based on the HDOP value. HDOP means "horizontal dilution of precision". While a smaller DOP value does typically indicate a greater precision, it is in NO WAY related to horizontal accuracy in terms of an actual distance, which is what Android reports.
In other words, if you're using an NMEA GPS, then you can basically ignore the reported accuracy in Android -- its meaningless.
Now there are ways to get more reasonable values, but this requires you to deal with the binary format that is output by your GPS module, not the standard NMEA output. For example, using the gpsd Android HAL (https://gitlab.com/gpsd/gpsd/-/tree/master/android), because gpsd uses the binary format for some GPS units (ublox in particular), it will output a reasonable distance for accuracy.
Very interesting ! Can you tell us how to do it on ours devices ?
fratellos said:
Very interesting ! Can you tell us how to do it on ours devices ?
Click to expand...
Click to collapse
If you can build Android from source, you just add gpsd to your local manifest and device makefiles, and remove the nonsense hal they previously included. However, as this thread appears to be related to chinese "px5", its not that simple. I'd say you would have to build it in AOSP, then manually copy in the files needed for it.
But the bottom line is really this; you don't actually need to do this. Making the accuracy values correct won't change the actual accuracy of the gps output, so all you really need to do is IGNORE the accuracy value.
If you want to get a picture of what the actual accuracy of your gps is, hook it up to a gnu box, let it get a fix with gpsd, and see what accuracy it spits out, then just remember that number and substitute in your head.
Automotive navigation doesn't actually require all that great of accuracy. If its accurate to within a few HUNDRED feet, that's good enough, because the software will snap your location to the nearest road anyway.
Not many manufacturers make head units to match my car, a 2004 C5, even less with the newer PX5 units. I did find this one,
https://www.seicane.com/android-199...mirror-link-backup-camera-dvr-obd2-dab-s32577
Anyone familiar with this brand? Do they make their own or repackage?
What 2004 C5 is? (I expected a Citroën C5)
the link you provided is for a 2004 Audi Series (A4, A3, A6)
I think the same Audi you linked is on Daasaita (HotAudio):
https://es.aliexpress.com/store/pro...2804594516.html?spm=a2g0v.12010612.0.0.cLbLd3
ikerg said:
What 2004 C5 is? (I expected a Citroën C5)
the link you provided is for a 2004 Audi Series (A4, A3, A6)
I think the same Audi you linked is on Daasaita (HotAudio):
https://es.aliexpress.com/store/pro...2804594516.html?spm=a2g0v.12010612.0.0.cLbLd3
Click to expand...
Click to collapse
Audi C5 is the Volkswagon/Audi platform code,
https://en.wikipedia.org/wiki/Audi_A6#C5_.28Typ_4B.2C_1997.E2.80.932004.29
What I need is for the A6 only, not the A3 or the A4. The A3 and A4 both use a different size face plate. I need one for the A6 from those years specifically.
anyone have one of these Seicane units?
is there any reason to think it's any different than the other PX5 units as far as modding and firmware upgrades?
thanks!
Hello, yes I do have a unit bought by Seicane SELLER.
Seicane is just reseller and you will get all sorts of units built buy other MANUFACTURERS if you buy from them.
In my case I bought a unit for Subaru and found it to be an MTCD device built by Klyde (MCU manufacturer code: KLD).
So as of my current knowledge you won't really know what manufacturer built your unit until you check the system about screen for the real manufacturer. And as a result the devices are no different than the ones bought by any other reseller.
Don't buy from them, they have worse to NO service at all!
I have a broken (warranty) seicane unit, i am mailing with them now for 1,5 month to get instruction how to send back.
They give bull**** answers or ask bull**** questions to keep you waiting, after a while they stop responding.....
I advise do absolutely NOT BUY from them, just a worse and also expensive seller....
B3rt said:
Don't buy from them, they have worse to NO service at all!
I have a broken (warranty) seicane unit, i am mailing with them now for 1,5 month to get instruction how to send back.
They give bull**** answers or ask bull**** questions to keep you waiting, after a while they stop responding.....
I advise do absolutely NOT BUY from them, just a worse and also expensive seller....
Click to expand...
Click to collapse
Seicane are a seller not a manufacturer, there are no "Seicane" units.
Whats wrong with your unit ?
typos1 said:
Seicane are a seller not a manufacturer, there are no "Seicane" units.
Whats wrong with your unit ?
Click to expand...
Click to collapse
I know they are sellers and not manufactors, but have no idea who is the manufacturer.
But warranty is given by a seller, not a manufactor, they sell it as there own but give no support what so ever on it.
If you have a problem they simply ignore it and hope you stop complaining and so there problem is gone.
Please make sure if you buy from China that you chose a seller which does give support!
The problem with my unit is it does not turn of anymore.
When plugged in it directly boot up, also when acc is off, when acc is turned on and off agin it should turn off by ACC control through can-bus control.
It seems can-bus is not working properly anymore....
When i asked support i get the most stupid answers such as:
check the 12V acc wire is connected... DUH there is no 12V acc wire in my car, it is fully can-bus, also there is NO 12v acc wire in the connector of the radio!
This then i get 4 times to check!
Now i get 5 weeks (i contact them 3 times a week) that there engineers are checking the software, FIVE WEEKS !!!!!
I am now aprox 9 weeks contacting them how to solve this (the unit was when i first reported it under warranty, now it is out of warranty...)
I never buy/order from them again!
I hope no one does!
B3rt said:
I know they are sellers and not manufactors, but have no idea who is the manufacturer.
But warranty is given by a seller, not a manufactor, they sell it as there own but give no support what so ever on it.
If you have a problem they simply ignore it and hope you stop complaining and so there problem is gone.
Please make sure if you buy from China that you chose a seller which does give support!
The problem with my unit is it does not turn of anymore.
When plugged in it directly boot up, also when acc is off, when acc is turned on and off agin it should turn off by ACC control through can-bus control.
It seems can-bus is not working properly anymore....
When i asked support i get the most stupid answers such as:
check the 12V acc wire is connected... DUH there is no 12V acc wire in my car, it is fully can-bus, also there is NO 12v acc wire in the connector of the radio!
This then i get 4 times to check!
Now i get 5 weeks (i contact them 3 times a week) that there engineers are checking the software, FIVE WEEKS !!!!!
I am now aprox 9 weeks contacting them how to solve this (the unit was when i first reported it under warranty, now it is out of warranty...)
I never buy/order from them again!
I hope no one does!
Click to expand...
Click to collapse
I know a lot of sellers have bad support. I m just trying to see if I can help.
The stereo will have pins for ACC even if the loom does not have wires, what ahv eyout ried so far ? Have you asked on here for help ?
The MCU type will tell you who makes your unit.
typos1 said:
I know a lot of sellers have bad support. I m just trying to see if I can help.
The stereo will have pins for ACC even if the loom does not have wires, what ahv eyout ried so far ? Have you asked on here for help ?
The MCU type will tell you who makes your unit.
Click to expand...
Click to collapse
Yes thx for any help, but the problem is within the canbus decoder i believe.
It is a unit specific for a Mini cooper, it has besides the radio/android part also the dials for fuel, obd and other car control lights etc, these also do not work properly anymore.
This car section is also controlled by the can-bus part of the unit.
The android part itself works fine, it is the can-bus part which is not working properly anymore.
The MCU have the letter KGL in it, i have really no idea who is the 'real' manufactor, but i actually doubt the manufactor will help.
B3rt said:
Yes thx for any help, but the problem is within the canbus decoder i believe.
It is a unit specific for a Mini cooper, it has besides the radio/android part also the dials for fuel, obd and other car control lights etc, these also do not work properly anymore.
This car section is also controlled by the can-bus part of the unit.
The android part itself works fine, it is the can-bus part which is not working properly anymore.
The MCU have the letter KGL in it, i have really no idea who is the 'real' manufactor, but i actually doubt the manufactor will help.
Click to expand...
Click to collapse
Yes, I know the type, it has a round screen. KGL are the manufacturer - Shenzhen Kai Ge Le.
In factory settings, how many options are there for your car, for Minis ?
You can list CAN Bus decoder by manufacturer, how many many are showing for Mini ?
I ask this because you may be able to sort things out by getting a new CAN Bus decoder.
typos1 said:
Yes, I know the type, it has a round screen. KGL are the manufacturer - Shenzhen Kai Ge Le.
In factory settings, how many options are there for your car, for Minis ?
You can list CAN Bus decoder by manufacturer, how many many are showing for Mini ?
I ask this because you may be able to sort things out by getting a new CAN Bus decoder.
Click to expand...
Click to collapse
I will take a look, at the moment the device is stored in a box
Thx for the tip!
Witson sells one for our cars...just picked one up for my allroad
Sent from my iPhone using Tapatalk Pro
Seicane = Bad Customer Service + Do nothing for you after the sale.
I purchased a Head Unit from them back in June 2018. The bluetooth module has never worked and after going around with them about it, they sent me a different module, not the Parrot BT module I purchased originally. Replacement of the BT module requires disasembly of the unit, de-solder old BT, solder new one, but the reason the BT did not work was that a few of the SMD resistors were damaged during build or soldering the BT module in. 3 months since purchase and still dont have a working unit. Now they want me to ship the unit back but I know they will void warrentee due to customer opening the unit (not the factory), and will claim I damaged the board attempting replacement. Oh, did I tell you they never told me the BT module was soldered onto the main board?? When they offered to ship a replacement BT I was under the impression it was a snap in module simular to how PC processors or flat cable connectors lock in. They knew, but dont want to deal with problems.
Remeber, they are only resellers, not the manufacturer. They all buy from the same manufacter for the most part. Good luck if you do get one that works as expected from them.
Seicane:
CPU: 8 core 64-bit CPU Coretex-A53 @ 1.5G
Memory: 3891
Kernel Version: 4.4.93+ [email protected] #263 Wed May 9 09:36:56 CST 2018
Build Number: px5-userdebug 8.0.0 OPR5.170623.007 end.hct.20180515.095719 test-keys
MCU Version: MTCE_KLD_V2.80_1 Mar 1 2018 16:54:22
Model: px5(800x480)
Android version: 8.0.0
Android security patch level: October 5, 2017
Dont buy Seicane
I will just add that I purchased from Seicane in May 2018 and at day 174 I have tonight lodged PayPal buyer dispute due to the ongoing issues I have ane the absolutely substandard customer service. Simply terrible. Buyers beware.
If PayPal cant resolve this then I will be offering payment to anyone in the forum who can resolve the issues for me.. watch this space. Dont buy Seicane!
G
Duck020 said:
I will just add that I purchased from Seicane in May 2018 and at day 174 I have tonight lodged PayPal buyer dispute due to the ongoing issues I have ane the absolutely substandard customer service. Simply terrible. Buyers beware.
If PayPal cant resolve this then I will be offering payment to anyone in the forum who can resolve the issues for me.. watch this space. Dont buy Seicane!
G
Click to expand...
Click to collapse
Seicane are a seller only, there are no "Seicane" units.
What MCU do you have ?
What problems do you have ?
typos1 said:
Seicane are a seller only, there are no "Seicane" units.
What MCU do you have ?
What problems do you have ?
Click to expand...
Click to collapse
Hi typos1,
The spec for my unit as follows:-
Head Unit: Seicane s081988f
OS: Android 7.1.2 (Nougat)
CPU: Allwinner T8, 8-core Cortex-A7 @ 1.8GHz
Memory: 2GB DDR3 RAM, 16GB EMMC, 2xUSB2
Display: 9", 1024x600 capacitive
MCU Version: T8.3.19-23-10-E43101-171127
System Vers: V9.2.2_20171202.103838_TW2
Linux Kernel: 3.10.65 (20171129)
Security Patch Level: 2017-07-05, 7.1.2 (Nougat)
Issues still unresolved:
Microphone only works for phone calls, no android apps (no OK google)
Screen calibration slightly off by 0.5cm
Audio from AM / FM radio good, but Android apps (google maps, Spotify, youtube etc) audio louder from front left channel than all other channels
no root, unable to add some apps that I would like
Using AM / FM radio and waze, an alert in waze mutes AM / FM radio and it does not return. This doesn't happen in google Maps
When using google maps, something happens to the audio where it sounds like it changes the audio fade to front speakers more than rear speakers but when this happens the balance between left and right seems to be corrected resolving issue 3. System audio preferences for navigation set to use all 4 speakers but doesnt appear to be working
I suspect that there are other issues that I cant recall right now but whats listed above is enough to be unsatisfied with the product. The primary issues that I need resolved are the Microphone and the Audio being all over the place depending on what app is used. It just needs to be consistently balanced left to right, front to back right in the middle for all apps.
I am not against using an updated system ROM or MCU but I am not knowledgeable in this area and despite doing quite a bit of research I still havent figured out if there is a compatible release that I can apply to my unit, and frankly with all the time invested in research, forums, testing and trying to resolve issues with the re-seller I've got more important things to do with my time (work, family, hobbies)
Any assistance that can be provided would be greatly appreciated and rewarded.
cheers
G
I bought about 9 months ago, directly from Seicane a radio of 9 "android 8 PX5, 8 core 64 bit cortex A53, memory 3891 MB, MCU MTCE HF V2.86 May 28 2018, for a Subaru Forester, the integration and the connectors are excellent but the radio had problems with the bluetooth handled by google and when connecting the cell phone via usb Easyconected, it did not recognize the cell phone, I asked for support but the solution from them was simple, and it was still the same, at the end I found a firmware of Hal9k, I installed to the radio and with this all these problems were solved, the link is "https: //forum.xda -developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477 ", Seicane never respond very bad seller.
Duck020 said:
Hi typos1,
The spec for my unit as follows:-
Head Unit: Seicane s081988f
OS: Android 7.1.2 (Nougat)
CPU: Allwinner T8, 8-core Cortex-A7 @ 1.8GHz
Memory: 2GB DDR3 RAM, 16GB EMMC, 2xUSB2
Display: 9", 1024x600 capacitive
MCU Version: T8.3.19-23-10-E43101-171127
System Vers: V9.2.2_20171202.103838_TW2
Linux Kernel: 3.10.65 (20171129)
Security Patch Level: 2017-07-05, 7.1.2 (Nougat)
Issues still unresolved:
Microphone only works for phone calls, no android apps (no OK google)
Screen calibration slightly off by 0.5cm
Audio from AM / FM radio good, but Android apps (google maps, Spotify, youtube etc) audio louder from front left channel than all other channels
no root, unable to add some apps that I would like
Using AM / FM radio and waze, an alert in waze mutes AM / FM radio and it does not return. This doesn't happen in google Maps
When using google maps, something happens to the audio where it sounds like it changes the audio fade to front speakers more than rear speakers but when this happens the balance between left and right seems to be corrected resolving issue 3. System audio preferences for navigation set to use all 4 speakers but doesnt appear to be working
I suspect that there are other issues that I cant recall right now but whats listed above is enough to be unsatisfied with the product. The primary issues that I need resolved are the Microphone and the Audio being all over the place depending on what app is used. It just needs to be consistently balanced left to right, front to back right in the middle for all apps.
I am not against using an updated system ROM or MCU but I am not knowledgeable in this area and despite doing quite a bit of research I still havent figured out if there is a compatible release that I can apply to my unit, and frankly with all the time invested in research, forums, testing and trying to resolve issues with the re-seller I've got more important things to do with my time (work, family, hobbies)
Any assistance that can be provided would be greatly appreciated and rewarded.
cheers
G
Click to expand...
Click to collapse
You have an Allwinner chipset (not Rockchip or Intel Sofia) and "MTCD" or "MTCE" does not appear in your MCU field, so you dont have an MTCD/E unit and are in the wrong forum, try the Android Headunits general forum.
migcep said:
I bought about 9 months ago, directly from Seicane a radio of 9 "android 8 PX5, 8 core 64 bit cortex A53, memory 3891 MB, MCU MTCE HF V2.86 May 28 2018, for a Subaru Forester, the integration and the connectors are excellent but the radio had problems with the bluetooth handled by google and when connecting the cell phone via usb Easyconected, it did not recognize the cell phone, I asked for support but the solution from them was simple, and it was still the same, at the end I found a firmware of Hal9k, I installed to the radio and with this all these problems were solved, the link is "https: //forum.xda -developers.com/android-auto/mtcd-software-development/rom-hal9k-rom-3-mtcd-e-head-units-t3847477 ", Seicane never respond very bad seller.
Click to expand...
Click to collapse
Thanks Migcep !! I think you saved me. So little about the same unit I bought for my Forester. Glad you shared your info.
My app uses a Bluetooth connection to pair with external HW. On some phones it works as expected, while on others I have a lot of issues connecting. I'm going to get samples of phones that give me the most trouble.
1) Where do I find information about each phone's BT module? Is it inside the chipset?
2) Any tips you'd like to share?
Thanks!
I can't offer anything from a development perspective, but I can tell you that the Bluetooth transceiver is part of the SoC modem. However, be aware that the Bluetooth firmware stack actually dictates the capabilities of the hardware - you'll see little difference between, say, a Snapdragon 300 and an 800 if they're both running Bluetooth 3.1.