I have been told that the G4 contains this chip but AT&T has not activated it for anyone. Is there any way to do this? Not to familiar with it at all, I know some versions have it but some don't.
I've read all kinds of things about it, some say that the Carrier's will actually short or remove connections from the FM chip so there is basically no way to enable it. I don't know what is fact and what is speculation. I don't think anybody does to be honest. Short of the carriers engineers.
That being said I was looking at the build prop file and noticed a line that said ro.fm.transmitter=false
I'm really tempted to change the false to true, but I don't want to mess anything up. That, and it can't be that simple. If it was, someone would've figured it out by now.
Sent from my VS986
I have a H815K phone on Telstra, and it has a FM Radio application, and can use FM Radio.
rick09 said:
I've read all kinds of things about it, some say that the Carrier's will actually short or remove connections from the FM chip so there is basically no way to enable it. I don't know what is fact and what is speculation. I don't think anybody does to be honest. Short of the carriers engineers.
That being said I was looking at the build prop file and noticed a line that said ro.fm.transmitter=false
I'm really tempted to change the false to true, but I don't want to mess anything up. That, and it can't be that simple. If it was, someone would've figured it out by now.
Sent from my VS986
Click to expand...
Click to collapse
This setting is for an FM transmitter which is not present in any variant of G4 - meaning it does not transmit the audio FROM the phone to the external FM receiver (remember? some Nokias had this in the past).
There is no setting in build.prop in my D815 EU for FM radio. I suppose it's actually removed from the software. There isn't any separate audio chip - it's built into Qualcomm. Firmware disables it. Perhaps there is an entry in the MISC partition (mmcblk0p22) which configures all features (have taken a look in a HEX editor but no apparent entry for FM radio).
Related
Hi,
I'm looking for a software to manually lock my Qtek 9090 on a specific GSM cell (or a specific antenna, somehow). It's very easy to do such a thing on my old Nokia using the hidden menus, but I never found a Pocket PC application that can do that. Any idea ?
Hi yannl,
this shouldn't be a big deal for those how know how to program such a thingy. I assume it should be possible to block the phone program from calling (or even simpler and uglier simply to kill it's process) when you are not in the "right" cell.
As dutty's cell profiler is able changes diverse settings or even launch apps, etc. depending on the cell you're in, it shouldn't be too difficult to realize your wish...
HTH,
BGK[/url]
Thanks. I contacted Cell Profiler to ask them about a feature like that. But I'm very surprised that no software around allows to lock on a cell.
why would you like to do so ?
locking phone to a specific cell/BTS/WTS
AlCapone said:
why would you like to do so ?
Click to expand...
Click to collapse
please tell if there is any way to lock the phone to specific Scrambling code or a BTS, needs it for some testing.
Hello all. I appreciate your help on this question. I have posted this over at the CM forum as well, but it is a non CM specific Android 4.3/Gnex question, so I think it's post here is appropriate. Also, I think this is more of a general Android development type of question and seems more suited for this forum's members.
I am on 10.2-20131127-NIGHTLY-toro (Android 4.3), coming from 10.0.0 (Android 4.1). It is running pretty well for me for the last 2 days, however...
I do have some intermittent audio skipping when streaming music to my Kenwood DNX8120 headunit in my car. In the past (on Android 4.1), I have been able to resolve this by using some bluetooth audio.conf tweaks (changing /system/etc/bluetooth/audio.conf). The problem is that the bluetooth stack was completely changed since Android 4.2, and you can no longer change bluetooth settings in this way.
I understand there are some build.prop changes that I can make to accomplish the setting changes I need, but I need some help identifying which build.prop properties correspond to the audio.conf settings I need. If I recall correctly, the audio.conf settings I changed were: "Master=true", "MaxConnections=10", "SBCSources=10", the "Enable" string (see below), as well as "HFP=true" to make the A2DP stream work without skipping.
Also, I am a noob at changing build.prop and I need to know if I am even understanding it's use correctly? Will it control settings the way I think it will?
One of the build.prop settings I have learned about is called "ro.bluetooth.request.master" and I think I need to set this to "true", but I don't know the other props that I need to change.
Thanks in advance for your responses and insight.
Here is the whole audio.conf file that used to work well with my headunit on Android 4.1...
Code:
$ cat audio.conf
[General]
Enable=Sink,Control,Headset,Gateway,Source
Master=true
AutoConnect=true
[Headset]
HFP=true
MaxConnections=10
FastConnectable=false
[A2DP]
SBCSources=10
MPEG12Sources=0
[AVRCP]
InputDeviceName=AVRCP
MetaDataBlackList=Ford Audio
Any answer?
Did you happen to come up with an answer? I just upgraded to 4.4 from 4.2 and now I have audio dropouts in my car. Up until now this never happened. It's interesting that on my phone (not a Nexus) the dropouts can be avoided if I keep the screen awake. I guess I would really like to know if there are any settings I can tweak.
pro450 said:
Did you happen to come up with an answer? I just upgraded to 4.4 from 4.2 and now I have audio dropouts in my car. Up until now this never happened. It's interesting that on my phone (not a Nexus) the dropouts can be avoided if I keep the screen awake. I guess I would really like to know if there are any settings I can tweak.
Click to expand...
Click to collapse
Nope. No one was able to help me. I've searched and researched. I know it's possible to fix, but there is no documentation out there and no one has come forward with any information. Sorry for the bad news.
I did have a moto x for a short time on kitkat, and it did skip less, but it did skip.
I know this thread is like 1.5 year old, but have any of you managed to fix that damn bluetooth thing ? Or implement the "master" setting line into bluetooth config file ?
My G4 is on its way.
I was wondering if anyone can confirm we can reenable the FM functionality with root?
Such as using the Spirit FM app?
Nobody? Need some help to verify this. Otherwise I have no reason to root..
come on guys, for anyone with a root G4 (At&t, Tmo or Vzn).... it is a quick check.
Spirit1 and Spirit2 say they're for AOSP roms only, so probably not. I'm not going to pay the $9 to find out.
Tried nextradio and it doesn't see the receiver. (Rooted US Tmobile) I believe I earlier possibly saw an item on a hidden menu that referred to the receiver, not sure if this could possibly turn the fm receiver chip back on.)
Hi
I am trying to enable VoLTE and WiFi calling on my Nexus 5x. My carrier supports these features, and as far as I know, Nexus 5x is capable of supporting them as well. My phone is rooted, and runs Pixel 2 ROM which I found on xda (https://forum.xda-developers.com/nexus-5x/development/rom-pixelmod-lg-nexus-5x-t3486862). I have Magisk flashed and I just enabled the "VoEnabler" module so that I get the necessary toggles in Settings. They appear, but unfortunately, they do not work. When I check IMS registration in ##4636## (##INFO##) it still says "Not registered". I have learnt that I need to enable a certain "profile" for the Qualcomm radio chip as well, so I downloaded QPST_2.7.460 and managed to see the phone in PDC.exe after installing the correct Qualcomm drivers on my PC, and setting the DIAG PORT to on for the phone by issuing the command 'su; setprop sys.usb.config diag,adb' in a Terminal emulator on the phone. Where I am stuck now, is in PDC, because it only shows me 3 profiles: HW_DEFAULT, SW_DEFAULT and ROW_Generic_3GPP. I read that Vodafone_India, or Telefonica UK, or Telia Finland would be profiles that may work with my carrier and allow my phone to register with IMS, but unfortunately I do not have those in the list. So, my question is, does someone have more experience with this, can I load MBN files for this profiles using the "Load" button in PDC? If so, do files coming from other Nexus 5x, or even other phones work? If anyone has any experience with this, any help would be grately appreciated.
A little update: I tried with some of the mcfg_sw.bin files from the stock ROM, unfortunately, it just cannot activate for Sub0 and switches back to ROW_Generic_3GPP. Furthermore, I downloaded an LG G4 firmware, as that phone uses the same chipset, and tried to see the files extracted from the KDZ file usig 7zip, yet none of the "mcfg_sw.bin" files actually appear in PDC so I cannot "activate" it on the phone. Would really appreciate someone with a bit of experience to guide me on this one.
Thank you very much.
PS. Sorry if this is the wrong section, feel free to move it wherever it belongs to.
Your carrier needs to have enabled these features in their network for your phone model, too.
I've found that support for VoLTE is very spotty among custom ROMs. Some don't seem to pay any attention to it, some say they "support" it but it doesn't seem to work. That may be a per-carrier issue. FWIW I'm on Verizon in the USA and CandyROM is one of the few I've found that "supports" VoLTE, *and* it actually works for me, *and* the ROM is actively maintained. So maybe try that one if you're not too attached to PixelROM. I wish this feature was paid more attention by developers, it really makes a big difference in call quality.
The carrier supports it, of course. Do you have the same phone (5x) and run CandyROM on it? Have you got a link for it? I don't see how ROMs really have to do anything special, since they do not touch the radio partition, which is still the one from stock. You just have to add the toggles to the Settings app by editing build.prop, I guess. But I will take a look anyway, maybe it actually works, although my carrier does not support this actual model, I was hoping I couod change the modem config on it and force it to work with WiFi calling and VoLTE.
https://forum.xda-developers.com/nexus-5x/development/rom-candy8-1-beta-t3749484/page9
Yes, I have a 5X, run this ROM, and VoLTE works.
Jacquestrapp said:
https://forum.xda-developers.com/nexus-5x/development/rom-candy8-1-beta-t3749484/page9
Yes, I have a 5X, run this ROM, and VoLTE works.
Click to expand...
Click to collapse
Maybe I'll try it, although I am pretty sure it won't work by default on my carrier, since it has the same default radio which lacks the proper config for my network. That's what I am trying to get, a proper config that will work with my phone, by switching it with Qualcomm PDC.
For Verizon, the necessary config is already in the radio image, of course, and probably gets picked up automatically when the device signs into the network. For Europe, all I see is EE UK...
In the UK the operator EE does support VoLTE for many phones but not for the N5X, even if you've "provisioned" it in your ROM.
Hello,
I apologize in advance if there's a better spot for this, but I am looking for an entry point to accomplish this, so please point me in the right direction if this would be better suited elsewhere (was torn between here and software)
I currently have an Xtrons tq700l, which includes the tef6686 chip for radio reception.
I've looked into it quite a bit, and I've seen people using the tef6686 to receive shortwave broadcasts with excellent results on PCs.
I would like to edit the frequency table/spacing, so the AM broadcast band uses 5khz stepping and can go up to 28mhz (since I don't expect app makers to add a separate SW tab, as this is sorta a niche desire, I'd just extend the AM band to include SW and use SW stepping)
I've installed a few replacement applications, and notice they all respect the region setting as set in the car settings menu, so I assume this rules out simply editing the radio tuner application itself.
So the question comes down to, where exactly is the radio region actually stored? It almost seems like this would likely be in an XML file somewhere with the ranges and stepping, but with these head units, all bets are off.
Any direction one can provide that can get me going in the right direction would be extremely appreciated.