Can anyone shed light on how to do this with a Nexus 5X? NV editor (never used it) Thanks so much
This does not make sense. Use a priority. Gravitybox available.
glehel said:
This does not make sense. Use a priority. Gravitybox available.
Click to expand...
Click to collapse
Sure it makes sense. If people can add bands they should be able to subtract them. (see the link below, I'm not familiar with how to do what they are talking about though)
Thanks for telling me about GravityBox. I can't tell if it actually turns off the radios, and if they are off at startup. I need 2G and any less secure bands eliminated completely. So preferences are not what I'm looking for. I'm running Copperhead (an AOSP without google services) so I'm not sure that GravityBox would work.
So yeah, I want it to be like the chip for those bands are nonexistent. I think that modifying the firmware/image would work, I dont think I need the GSM chip at all since I'm on Verizon. If I could leave out the GSM radios firmware that might work but have no idea how to do modify ROM images. I bet others would like to remove just 2G or others though.
I can't post links yet but this search should bring you to a page that discusses the NV number editing
" [HOW TO] Add RF & LTE Frequency Bands to Qualcomm Phones "
Related
Just wondering what the build.prop for the G2 says under the ro.ril.hsxpa heading.
So far as I can tell, there's 3 settings thus far known for this value
ro.ril.hsxpa=0 which limits the phone to UMTS downloads and uploads
ro.ril.hsxpa=1 which enables HSDPA for downloads, uploads remain limited by UMTS
ro.ril.hsxpa=2 which enables full HSPA (HSDPA and HSUPA).
What I want to know is if the G2 has it set to anything other than 2, which might signify a special setting for HSPA+. It might be useful in case other phones have the needed chipset, but it's software disabled by the build.prop.
Thanks in advance for any response. I know the ROM has been dumped, but it will take me longer to d/l it than for you to pull it up in your file explorer. If I get no reply, I'll post my findings here anyway.
# grep ro.ril.hsxpa build.prop
ro.ril.hsxpa=2
ro.ril.hsxpa = 2
Virtuous' Desire Z Sense ROM for the G2 has ro.ril.hsxpa=3. Googling has yet to give me an answer as to what value 3 means though...any ideas?
chewy106 said:
Virtuous' Desire Z Sense ROM for the G2 has ro.ril.hsxpa=3. Googling has yet to give me an answer as to what value 3 means though...any ideas?
Click to expand...
Click to collapse
i changed it to 3 also,
changed it twice on the same build.prop. for some reason all the ro.ril's are in there twice.
so far i dont see a difference at all.
sheek360 said:
i changed it to 3 also,
changed it twice on the same build.prop. for some reason all the ro.ril's are in there twice.
so far i dont see a difference at all.
Click to expand...
Click to collapse
apparently i stick with umts when i changed both values to 3, it wouldnt switch to hspa or hspa+
Hi folks,
There is a hidden Service menu acessible by dialing *#*#197328640#*#*, on SGS SIII (it seems to be part of towchwiz).
This secret code launches an apk but I do not know what it is, and this apk, shows a lot of information, one of these is the frequency (In MHz) that is in use by the device.
I need this information, to buy an gsm repeater/amplifier, to my house because the signal strength is very weak, and my carrier, have licences to operate in two frequencies in my region.
So, can someone discover that apk, extract it, and post it here, so I can try to install it on my Galaxy Nexus?
It could ensure that I will buy the correct repeater.
Thanks
rafareino said:
Hi folks,
There is a hidden Service menu acessible by dialing *#*#197328640#*#*, on SGS SIII (it seems to be part of towchwiz).
This secret code launches an apk but I do not know what it is, and this apk, shows a lot of information, one of these is the frequency (In MHz) that is in use by the device.
I need this information, to buy an gsm repeater/amplifier, to my house because the signal strength is very weak, and my carrier, have licences to operate in two frequencies in my region.
So, can someone discover that apk, extract it, and post it here, so I can try to install it on my Galaxy Nexus?
It could ensure that I will buy the correct repeater.
Thanks
Click to expand...
Click to collapse
Doesn't work on intergalactic or AeonFluxx ROMs.
Sent from my SAMSUNG-SGH-I747 using xda premium
As I said before, it's part of touchwiz, so it will be available only in stock sgs s3.
Has someone one stock to try to extract?
Sent from my Galaxy Nexus using xda app-developers app
rafareino said:
As I said before, it's part of touchwiz, so it will be available only in stock sgs s3.
Click to expand...
Click to collapse
And because of this, it will not work on a ROM that does not have the TouchWiz framework. I'm pretty sure it would not work on your Galaxy Nexus, as it does not use TouchWiz UI.
rafareino said:
Has someone one stock to try to extract?
Click to expand...
Click to collapse
I believe it is serviceModeApp.apk. I can't be 100% sure if it's it only app you would need, particularly because it is tied to TouchWiz framework. You can extract it from one of the numerous stock or a stock-based ROM, available in the Android Development section.
Hi there, I've noticed that the sub-category of the none LTE N7 version "android development" is much more active and populated than the LTE version and I was wondering if it's possible to install the non LTE Roms (or Ubuntu for example) on the LTE version and loose the LTE functionality or it's completely incompatible?
I've already Googled it and searched XDA but I was not able to find any related information and would really appreciate it if anyone could shed a light here, thanks in advance.
i'd like to know myself
Well certainly the LTE radio would be non-functional. Possibly the GPS since it depends partially on the mobile network. As far as any other function, I've no idea.
It appears that all that it takes to compile for Deb instead of Flo is just a different compile option and having the binaries. But most devs don't bother, which is very disappointing. The number of files affected is pretty large, and I don't think post-compile porting is practical (I looked at this briefly)..
I've been hesitant to try just flashing a Flo rom on my Deb. I suspect it wouldn't cause any permanent issues, or we'd see more "oops I bricked my N7" posts from those flashing the wrong Roms. But I'd rather not test on MY device unless I knew for sure it was safe.
lotherius said:
Well certainly the LTE radio would be non-functional. Possibly the GPS since it depends partially on the mobile network. As far as any other function, I've no idea.
It appears that all that it takes to compile for Deb instead of Flo is just a different compile option and having the binaries. But most devs don't bother, which is very disappointing. The number of files affected is pretty large, and I don't think post-compile porting is practical (I looked at this briefly)..
I've been hesitant to try just flashing a Flo rom on my Deb. I suspect it wouldn't cause any permanent issues, or we'd see more "oops I bricked my N7" posts from those flashing the wrong Roms. But I'd rather not test on MY device unless I knew for sure it was safe.
Click to expand...
Click to collapse
Thank you very much for sharing your findings on this issue with such a detailed answer, it's highly appreciated.
GOOD NEWS CM 12 on E980 every thing work LTE-phone work.
http://forum.xda-developers.com/optimus-g-pro/general/data-voice-heard-phone-t3061313
DangNavyCM12-F240L-Fix fix dial audio after I mod .
PS.. when update the new rom voice not heard,don't forget to update my mod .
By DangNavy
Now I can go spring fishing, 2 days of the testing, happy got my lollipop ,any girls want some.HA HA HA
PS...Don't forget give me some love
Go fishing
Audio call fix
Can you explain what this does exactly? I have needed to install your mod for every CM nightly, and also for Blisspop on my e980 running on tmobile. Just curious what it does, in case your patch file stops working for new version.
Thanks again!!
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
damainman2015 said:
thank you hawkwind!! Yea I was curious because in roms like CM, Blisspop, or even slimLP there is no mention to needing anything after installing the ROM to make the sound work during calls. However I always have to install this patch to make it work so it leads me to wonder what is different about my e980 that causes me to have issues that no one else seems to bring up lol .
Click to expand...
Click to collapse
In the earlier version of the blisspop, the dev had changed the values in the build.prop file so the users would not needed to do so them selves. Since this was such an old issue according to that posting, perhaps dev thought that it was no longer necessary to change those two values.
Hi I'm using stock g4 ux4.0 lollipop g pro v12 final rom and during phone calls I have to use headphones whit mic because there is no sound without them . Will this fix work for me?
It may, though I think with the ROM you're using there is a patch for the sound issue, check the dev's thread first. Otherwise try the solution we've discussed here with prop.mod editor anyway, since it will not harm your device even if, it doesn't fix your problem. Just remember to reboot the phone once you're done with changing the values.
hawkwind212 said:
I think it changes at least these 2 options in /system/build.prop file
1. persist.audio.dualmic.config, from 'endfire' to 'false'
2. persist.audio.handset.mic.type, from 'digital' to 'analog'
You can change these values yourself with the prop.mod editor, but you also have to change these values every time you update or install the ROM. The dangnavy script also changes some other values, but the two I've mentioned are the ones that effect the in-call phone mic volume. I got these solutions from this post: http://forum.xda-developers.com/showthread.php?t=2709781
Click to expand...
Click to collapse
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
ShadySquirrel said:
If changing these doesn't affect other variants (E985/6/9 and even F240x), I'd be glad to change them in my device tree.
Click to expand...
Click to collapse
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Couldn't agree more. Since this is variant specific thing, I won't change anything... I've put an info about that in Slim's thread, but it looks like people really don't like reading.
hawkwind212 said:
A good old saying, if it's not broken, no need to fix it. These changes only work for e980 with at&t in USA. If the provider is t_mobile, that's another matter. I don't think other ogp variants have this phone Mic issue. Like I've said, this is an old topic, I'm surprise that so many people are still asking about it.
Click to expand...
Click to collapse
Just wanted to state, this patch is what fixes the no call audio issue for me while utilizing the TMobile network.
Ok.. so I've been doing some investigating. These are virtually the same hardware. Qualcomm Processor, 3GB RAM, same sound, video, etc chips.
Sprint has enabled the FM radio in their unit .. Nobody in Canada has.
How can we extract what Sprint did for their model so I can do it on mine? Or can I just flash a P rom on this unit? That seems like a no-go but then I can't see any physical difference between the two units.
Thanks for whatever advice is out there..
knoxster said:
Ok.. so I've been doing some investigating. These are virtually the same hardware. Qualcomm Processor, 3GB RAM, same sound, video, etc chips.
Sprint has enabled the FM radio in their unit .. Nobody in Canada has.
How can we extract what Sprint did for their model so I can do it on mine? Or can I just flash a P rom on this unit? That seems like a no-go but then I can't see any physical difference between the two units.
Thanks for whatever advice is out there..
Click to expand...
Click to collapse
I'm not a dev. But i do some modding. I think that's all software related. So either pull the correct files from a Sprint Rom with proper csc setup. Or flash a sprint Rom with your kernel and data fix. Either way might work.
Just don't do anything blindly. Make a complete backup of phone and do some more research. Best advice i have! Good luck!
knoxster said:
Ok.. so I've been doing some investigating. These are virtually the same hardware. Qualcomm Processor, 3GB RAM, same sound, video, etc chips.
Sprint has enabled the FM radio in their unit .. Nobody in Canada has.
How can we extract what Sprint did for their model so I can do it on mine? Or can I just flash a P rom on this unit? That seems like a no-go but then I can't see any physical difference between the two units.
Thanks for whatever advice is out there..
Click to expand...
Click to collapse
I don't have time but from what looking i did. Try adding this to the others.xml file in csc folder:
<CscFeature_Common_SupportNextRadio>TRUE</CscFeature_Common_SupportNextRadio>
And this file attached into framework folder:.
I'm not for sure this is all you need but i believe these have to do with it.
THANKS!
aaron74 said:
I don't have time but from what looking i did. Try adding this to the others.xml file in csc folder:
<CscFeature_Common_SupportNextRadio>TRUE</CscFeature_Common_SupportNextRadio>
And this file attached into framework folder:.
I'm not for sure this is all you need but i believe these have to do with it.
Click to expand...
Click to collapse
So you are right on the money. I've spent the day comparing identical versions of the same software release. One from SPRINT the other a Canadian carrier's version of the same ROM.
These are the two biggest catches I've run across. There maybe a few minor points, but I'm not sure how relevant they are. So I'm going to start here. A painful sense of 'this is somehow controlled via a kernel setting' lingers but.. to those willing to risk it all, bla bla bla.. here we go!
I'll report back shortly.
knoxster said:
So you are right on the money. I've spent the day comparing identical versions of the same software release. One from SPRINT the other a Canadian carrier's version of the same ROM.
These are the two biggest catches I've run across. There maybe a few minor points, but I'm not sure how relevant they are. So I'm going to start here. A painful sense of 'this is somehow controlled via a kernel setting' lingers but.. to those willing to risk it all, bla bla bla.. here we go!
I'll report back shortly.
Click to expand...
Click to collapse
:good: let me know.
knoxster said:
So you are right on the money. I've spent the day comparing identical versions of the same software release. One from SPRINT the other a Canadian carrier's version of the same ROM.
These are the two biggest catches I've run across. There maybe a few minor points, but I'm not sure how relevant they are. So I'm going to start here. A painful sense of 'this is somehow controlled via a kernel setting' lingers but.. to those willing to risk it all, bla bla bla.. here we go!
I'll report back shortly.
Click to expand...
Click to collapse
How it coming? Get it working?
I'm not by my pc, but i noticed files pertaining to this in the following system folders:
/lib
/etc/permissions
/framework
/csc edits.
Might want to check other folders in /etc also, like firmware.
aaron74 said:
How it coming? Get it working?
I'm not by my pc, but i noticed files pertaining to this in the following system folders:
/lib
/etc/permissions
/framework
/csc edits.
Might want to check other folders in /etc also, like firmware.
Click to expand...
Click to collapse
I've found files in those same folders that bear relevance. And further, there's a system level android permission :
android.permission.ACCESS_FM_RADIO
And then.. the final point - the sticky-wicket -- probably some change in the kernal to support all of the above.
I continue to tinker -- no success yet.
knoxster said:
I've found files in those same folders that bear relevance. And further, there's a system level android permission :
android.permission.ACCESS_FM_RADIO
And then.. the final point - the sticky-wicket -- probably some change in the kernal to support all of the above.
I continue to tinker -- no success yet.
Click to expand...
Click to collapse
I've just recently tried also, even on a sprint phone. No go yet.
It must be all software related. As i stated, I'm even on n910p but what I'm trying to accomplish is running a gsm rom on it. So that proves in missing software. Hopefully for you it isn't built into the framework files. Might be kernel. I'll try. Let you know.
aaron74 said:
I've just recently tried also, even on a sprint phone. No go yet.
It must be all software related. As i stated, I'm even on n910p but what I'm trying to accomplish is running a gsm rom on it. So that proves in missing software. Hopefully for you it isn't built into the framework files. Might be kernel. I'll try. Let you know.
Click to expand...
Click to collapse
In comparing the DPK1 rom between Sprint and Rogers.. other than the areas I've mentioned .. much of it appears to be the same.
My goal here is to know a) if it's in the kernel or just all in the standard software.
My gut says i'ts NOT in the kernel.. but
but they don't have the same lte bands right ?
Samsung announced FM tuners will be enabled in most smart phones in the Canadian marketplace!
https://www.sammobile.com/news/samsung-activate-smartphone-fm-chips-us-canada/