build.prop Tweaks Not Working FRF72 - Nexus One Q&A, Help & Troubleshooting

Hello,
Previously I was using two particular tweaks to get faster speeds (HSDPA) and the H logo in the signal indicator.
The tweaks are:
Code:
ro.ril.hsxpa=1
ro.ril.gprsclass=11
These tweaks work fine on FRF50 and previous builds of Android 2.1. I cannot gete FRF72 to work with the tweaks. I remain on 3G full full bars and no H for HSPDA signal/indicator. I have run speed tests and get slower speeds 2MB instead of 4MB+ I get on HSDPA.
Can anyone give any insight? I have tried multiple reboots, multiple build.prop pushes, etc.
I do:
adb remount
adb push build.prop /system
adb shell reboot
I check the build.prop with File Manager from Apollo Software. It shows the code lines are in there.
My build.prop is as follows:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=FRF72
ro.build.display.id=FRF72
ro.build.version.incremental=40830
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2
ro.build.date=Fri Jun 11 11:57:07 PDT 2010
ro.build.date.utc=1276282627
ro.build.type=user
ro.build.user=android-build
ro.build.host=android-test-4.mtv.corp.google.com
ro.build.tags=release-keys
ro.product.model=Nexus One
ro.product.brand=google
ro.product.name=passion
ro.product.device=passion
ro.product.board=mahimahi
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=qsd8k
# ro.build.product is obsolete; use ro.product.device
ro.build.product=passion
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=passion-user 2.2 FRF72 40830 release-keys
ro.build.fingerprint=google/passion/passion/mahimahi:2.2/FRF72/40830:user/release-keys
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.ril.enable.managed.roaming=1
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
keyguard.no_require_sim=true
ro.setupwizard.mode=OPTIONAL
ro.ril.oem.nosim.ecclist=911,112,999,000,08,118,120,122,110,119,995
ro.ril.emc.mode=2
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.config.ringtone=CaribbeanIce.ogg
ro.com.google.clientidbase=android-google
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
ro.com.android.wifi-watchlist=GoogleGuest
ro.error.receiver.system.apps=com.google.android.feedback
ro.setupwizard.enterprise_mode=1
ro.sf.lcd_density=240
rild.libpath=/system/lib/libhtc_ril.so
wifi.interface=eth0
wifi.supplicant_scan_interval=15
ro.telephony.default_network=0
ro.opengles.version=131072
dalvik.vm.heapsize=24m
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=1
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.ril.hsxpa=1
ro.ril.gprsclass=11

Nevermind, seems to be working, just no "H" icon. I have to do some more speed testing. Woudl rather the H icon show up so I know but as long as it's works it's OK.
I went back to FRF50 and it works there fine, (H), just not on FRF72.
Can other confirm? I have tried different tweak values as well such as:
Code:
ro.ril.hsxpa=2
ro.ril.gprsclass=12

you have an H on an FRF50 rom? which one are you using?
And yes the H is more of an indicator rather than a difference in speed.

Use the fixed build.prop for FRF72 from here: http://htcpedia.com/forum/showthread.php?p=65478
Works great.

nxt said:
Use the fixed build.prop for FRF72 from here: http://htcpedia.com/forum/showthread.php?p=65478
Works great.
Click to expand...
Click to collapse
Confirmed working with the "H"?
Trying now...

y2whisper said:
you have an H on an FRF50 rom? which one are you using?
And yes the H is more of an indicator rather than a difference in speed.
Click to expand...
Click to collapse
Honestly dont know, it's a stock pre-rooted one. Nothing added, from when it was first posted a long ass time ago haha. Brb testing a bunch o crap.

Neg, doesnt make the H appear. I guess this is a ROM edit in another file. However, with or without my tweaks on FRF72 i get 3MB down and 0.15up, seems on par with what i was getting before.
Thanks for the help.

when i set ro.ril.hsxpa=1 then i only get 384Kbps upload speeds. as soon as i set ro.ril.hsxpa=2 my upload goes right up to 1.5Mbps.
and stock ROMs all have ro.ril.hsxpa=2, but people somewhere decided to start editing their build props to ro.ril.hsxpa=1 which basically removes HSUPA from my findings.

from what i have read 1 does give a boost to some, but seems mainly to be tmobile subscribers.

y2whisper said:
from what i have read 1 does give a boost to some, but seems mainly to be tmobile subscribers.
Click to expand...
Click to collapse
yeah i've read all those threads, and i think its all placebo effect. everyone posts numbers like "my download went from 650kbps to 800kbps. well at that point they are not hitting the upper limits of the network anyway, so that is just variations in network load giving those different readings.
here in my area we have a non-loaded network. so when i run speeds tests i hit 2-3Mbps down and 1.5Mbps up every time. so that seems to be hitting the upper limit of the network. then when i change to hsxpa=1 it immediately gets capped at 384kbps upload. of course i am on ATT but that shouldnt make a difference.
think of it this way, all stock ROMs have hsxpa=2, which is HSUPA. setting hsxpa=1 is just reducing your connection, putting a cap on it, so that you only get 3.6 hsdpa and 384kbps upload. i cannot break 0.37Mbps when i have it set to =1, no matter how many speed tests i run. the instant i change to =2, it flies right up to 1.5mbps upload.
so unless these people are all hitting the upper limits already, its placebo IMO. i have so many screenshots where i compare this.

Related

[APP] FuzeHFix

Okay, here's an app that will try to unstick the Fuze's HSDPA settings. It sets:
HKLM\OEM\RIL:
DisH = 0
EnableHSDPAIcon = 1
and resets them again as a start-up app after every soft-reset. It will then stay around for 2 minutes making sure those registry changes stick and then quit.
This may/may not fix the FUZE's speed issues especially if the DisH isn't read after the OS is up and running. Credit goes to the HSDPA thread that brought this up.
Takes 1K of memory, and 12K of storage.
2008/11/15: new version 1.1 just deletes DisH and enables the icon. May work out better. Choose your path.
This is awesome. I hope it works.
Have you attempted to counteract the PROVXML which loads up on start? Can this even be done without hard resetting or flashing a new ROM?
iboj007 said:
Have you attempted to counteract the PROVXML which loads up on start? Can this even be done without hard resetting or flashing a new ROM?
Click to expand...
Click to collapse
Probably can't fight that without doing the hard-reset/reflash.
The ShowSIM contacts in the OEM Kaiser roms stuck also and needed a new rom to permanently fix.
These settings can be found in
HKLM/Software/OEM/RIL
DisH is set to 1 from ATT --- No tweak app will mod this - change it to 0, and we should all be good to go.
acardinale said:
DisH is set to 1 from ATT --- No tweak app will mod this - change it to 0, and we should all be good to go.
Click to expand...
Click to collapse
The point is it gets reset to 1 after every soft-reset.
This app mods it to 0 and refixes that during every soft-reset. Anyways, the better fix may be to just delete the key.
New version 1.1 does that. Choose your pill.
my setting never reset after softreset ... my adjustment was still there.
:/
I just tested 1.1 and think that the fixes are cosmetic only. After reboot, I had an H instead of a 3G, but dslreports speedtest (flash) to Parsippany NJ did not show improvement in upload speeds.
Hfix Down Up Latency 3G/H
N 486 354 143 3G
N 773 363 169 3G
N 438 336 117 3g
Y 631 347 100 h
Y 440 321 116 h
y 482 351 117 h
And just for giggles, I removed 1.1, rebooted, installed HFIX 1.0, rebooted, and ran the same tests again. Below is a summary table showing all tests with the last 4 being HFIX 1.0:
HFIX Vers Hfix Down Up Latency 3G/H
1.1 N 486 354 143 3G
1.1 N 773 363 169 3G
1.1 N 438 336 117 3g
1.1 Y 631 347 100 h
1.1 Y 440 321 116 h
1.1 y 482 351 117 h
1 Y 712 899 141 h
1 y 412 596 170 h
1 y 838 326 134 h
1 y 914 364 159 h

[Q] /system/etc/gps.conf - What does XTRA_SERVER_? do?

Pottering around the SGS to-day and came across this file:
/system/etc/gps.conf. I renamed the file and commented out the entries that reference the XTRA_SERVER in the original.
/system/etc # cat gps.conf.20101105
NTP_SERVER=north-america.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
I have not noticed a lot of difference using the GPS after I removed the XTRA_SERVER_? entries.
Does anyone know what the purpose of these entries are?

About A-GPS Servers (gps.conf)

Hi there,
Galaxy SIII has "XTRA_SERVER_1=http://gllto.glpals.com/4day/latest/lto.dat" server line in gps.conf file, while Galaxy S has "XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin".
What is the difference between those servers? And which is better for faster GPS fix? Or "XTRA_SERVER_1=http://gllto.glpals.com/4day/latest/lto.dat" server is compatible with I9000?
Thanks in advance.
no answers?
They're different servers, that said, they're interchangeable. Why don't you try interchanging them? Remember to back up.
Here's mine, it's the fastest in my country:
NTP_SERVER=0.ca.pool.ntp.org
NTP_SERVER=1.ca.pool.ntp.org
NTP_SERVER=2.ca.pool.ntp.org
NTP_SERVER=3.ca.pool.ntp.org
NTP_SERVER=ca.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS:
# 0 - none, 1 - Error,
# 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
ACCURACY_THRES=5
INTERMEDIATE_POS=0
ENABLE_WIPER=1
SUPL_HOST=supl.google.com
SUPL_PORT=7276
REPORT_POSITION_USE_SUPL_REFLOC=1
# blank
xtra.bin is basically used by QUALCOMM , lto.dat is used by Broadcom Chip of BCM47511. Do a whois on glpals.com and gpsonextra.net and you will know which company uses which services. There is no great idea to change the Software of GPS to Qualcomm from broadcom ...
Gps-nitz-ntp
Hi all,
Sorry to post there but after lot of search, i haven't get any information
Does NITZ protocol is used only by GSM network and is it the default protocol used by android system to sync time?
Things I know is that:
- user can't set time without root privileges
- NTP server could be used only with third-party apps
- there is a gps.conf file in /system/etc and inside there is a line NTP_SERVER=... I want to know the meaning of gps.conf file cause my final goal is to try to sync device with NTP server wihout root priviledge but by redirecting NTP request to my own NTP server (changing DNS maybe) I used some packets sniffer and I can't see some NTP packets (over Wi-fi or GSM)
Thanks fo help

[FIX] for no in-call audio/T-Mobile US/4.2.2/.33 radio or lower

I posted this in General/LTE but I feel it will be easily found here.
This is to run stock 4.2.2/.33 or lower radio and not have audio issues.
Well after working a 10 hour day at a start-up, I came home and spent another 6 hours debugging our no in-call audio issue. This issue is specific to T-mobile USA customers with a certain N4 configuration. I'll explain it, only because some people will stumble upon this post and won't use the SEARCH!
You'll experience no audio during a call. No audio in the earpiece and no audio going in the mic. This is when you have:
Stock 4.2.2 (It's possible that it works on other roms that have this issue as well. Not sure.)
Either RIL file that is available. (doesn't matter)
Either bootloader (also doesn't matter)
.33 radio or lower
As I mentioned in a prior post, Google changed the sound table file for 4.2.2. This may have been to anger us but I feel like they were trying to enable an audio channel for the new HD calling or whatever. Not sure. Anyway, I verified that these entries are not in AOKP roms and that must be our issue. 4.2.2 radio has some kind of symbolic linking that matches that file and when we install .33, the rom expects that TMUS audio entry to be there and it's not. Any attempt to edit out those entries or use a straight AOKP file would cause a stuck boot animation and I'd have to do a restore...
I spent the last 6 hours tracing where each audio address was hooking too. As well as running logs to see what was going on. In a nutshell, all the audio triggers were reversed because of bad addressing. When you made a call, it would actually DISABLE mic and ear speaker audio! I didn't know how to remedy this as I didn't understand the audio "calibration database" system. So I studied it a bit and I wished I had earlier. The pattern I saw was that the main entity in a group has a set address. Something like 3:1. If any others fit in that main group, they also get 3:1. In the case of audio, think loudspeaker or loudspeaker with "dolby". Both are basically the same, so they can share the upper ranks. So imagine a loudspeaker that is much smaller and takes a different voltage, etc. That would be labeled in the next group of 6:1. So from what I saw, they basically doubled like that pretty often.
Without any further interruptions. The fix!
Your gonna need a root file manager. I like ES file explorer. It'll need to have root access enabled in the settings. You'll also need a text editor. You can use ES built in one but it really sucks. I use 920 text editor. Both those are free apps people. Do a backup before you start this as I had lots of booting issues trying to work this one out.
Now open ES (or other file manager) and navigate to root "/" on your phone. Click on the etc folder and then the snd_soc-msm folder. There will only be one file in there, snd_soc_msm_2x_Fusion3. Do whatever you have to do to change file permissions on that file. In ES, you hold down on file and go down until it brings up a box. Scroll down to the bottom and go to properties. It'll bring up the permissions. Click on the "change" box. Note it's default properties. Write them down if you have to! Now click all the check boxes. Make it a really open file! Then hit OK and go back to the directory. Click on file to open. An "Open As" box will pop up. Open as text in your 920 or whatever your app is.
You'll see the long ass Fusion3 file outlining all sound properties of your device. Were interested in changing line 1804 and 2736. If you have a good text editor, these will be listed on the left. Scroll down to line 1804 and you'll see the ACDBID or audio calibration database ID. Like this...
Modify /snd_soc_msm_2x_Fusion3 diff
...
1777 1777
1778 1778 ACDBID 7:1
1779 1779
1780 + EndSection
1781 +
1782 + SectionDevice
1783 + Name "Voice Earpiece TMUS"
1784 + Comment "Handset Rx device"
1785 +
1786 + EnableSequence
1787 + 'SLIM_0_RX Channels':0ne
1788 + 'RX1 MIX1 INP1':0:RX1
1789 + 'RX1 MIX1 INP2':0:RX6
1790 + 'RX1 Digital Volume':1:68
1791 + 'EAR PA Gain':0OS_6_DB
1792 + 'DAC1 Switch':1:1
1793 + 'SLIM TX3 MUX':0:RMIX1
1794 + EndSequence
1795 +
1796 + DisableSequence
1797 + 'RX1 MIX1 INP1':0:ZERO
1798 + 'RX1 MIX1 INP2':0:ZERO
1799 + 'RX1 Digital Volume':1:68
1800 + 'DAC1 Switch':1:0
1801 + 'SLIM TX3 MUX':0:ZERO
1802 + EndSequence
1803 +
1804 + ACDBID 81:1
1805 +
1780 1806 EndSection
1781 1807
1782 1808 SectionDevice
...
2320 2346 EffectsMixerCTL "SRS TruMedia"
2321 2347
2322 2348 EndSection
2349 +
2323 2350 SectionDevice
2324 2351 Name "HeadsetVM Tx"
2325 2352 Comment "Headset Tx device"
...
2669 2696 ACDBID 6:2
2670 2697 EffectsMixerCTL "SRS TruMedia"
2671 2698
2699 + EndSection
2700 +
2701 + SectionDevice
2702 + Name "DMIC Endfire TMUS"
2703 + Comment "Dual MIC Endfire Tx device"
2704 +
2705 + EnableSequence
2706 + 'SLIM TX7 MUX':0EC7
2707 + 'DEC7 MUX':0:ADC1
2708 + 'SLIM TX8 MUX':0EC9
2709 + 'DEC9 MUX':0:ADC3
2710 + 'DEC7 Volume':1:66
2711 + 'ADC1 Volume':1:100
2712 + 'DEC9 Volume':1:66
2713 + 'ADC3 Volume':1:100
2714 + 'SLIM_0_TX Channels':0:Two
2715 + 'MICBIAS1 CAPLESS Switch':1:0
2716 + 'RX1 MIX2 INP1':0:IIR1
2717 + 'RX2 MIX2 INP1':0:IIR1
2718 + 'IIR1 INP1 Volume':1:51
2719 + 'IIR1 INP1 MUX':0EC7
2720 + EndSequence
2721 +
2722 + DisableSequence
2723 + 'DEC7 Volume':1:60
2724 + 'DEC9 Volume':1:60
2725 + 'SLIM TX7 MUX':0:ZERO
2726 + 'DEC7 MUX':0:ZERO
2727 + 'SLIM TX8 MUX':0:ZERO
2728 + 'DEC9 MUX':0:ZERO
2729 + 'MICBIAS1 CAPLESS Switch':1:1
2730 + 'RX1 MIX2 INP1':0:ZERO
2731 + 'RX2 MIX2 INP1':0:ZERO
2732 + 'IIR1 INP1 Volume':1:0
2733 + 'IIR1 INP1 MUX':0:ZERO
2734 + EndSequence
2735 +
2736 + ACDBID 91:2
2737 + EffectsMixerCTL "SRS TruMedia"
2738 +
2672 2739 EndSection
2673 2740
2674 2741 SectionDevice
Click to expand...
Click to collapse
We need to change the ACDBID 81:1 at line 1804 to ACDBID 7:1. You can just erase the 81 and change it to 7. Just make sure spacing is the same. 1 space between the letters and the 7. Now go down to line 2736 and change the ACDBID 91:2 to ACDBID 6:2. Now you need to save that file. You won't be able to save directly over that file. You'll have to do a "save as" to somewhere that's easy to find. I just chose my download folder. Now go back into ES manager and find your file you made and copy it. Go to the snd_soc-msm folder and delete the original file and then paste your modified one in.
Now go to the properties of your new file and change the permissions back to the original default settings. This is very important. If left unprotected, someone could control any audio settings at will. This includes your microphone. Not cool.
Last but not least, reboot.
Don't forget to backup before starting procedure.
I'm not responsible for dead puppies or bricked phones.
etc. etc. etc.
Forgive any 3am grammar mistakes and enjoy your stock/TM-US/LTE! =)
Why are my lines way off?
Line 1804 : ACDBID 60:1
Line 2736: RX2 MIX 1 etc
You can't. ES text file support is poor. That's why I suggested "920 text editor". It's free and works okay. Search is no good and android as a whole bogs really hard on big text files. It does have numbered lines and quick scroll.
If all else fails, you can copy the file in ES and put it in download location, transfer to pc, do the edits there, put file back on phone and done.
Sent from my Nexus 4 using xda app-developers app
Ok but why are my lines different than yours, using 920
hey great job man. im glad you figured this out. im about to try it out
ceejay83 said:
Why are my lines way off?
Line 1804 : ACDBID 60:1
Line 2736: RX2 MIX 1 etc
Click to expand...
Click to collapse
you might have done something with codecs and stuff if you've tried to use those bypasses to get free voip minutes on your phone (I think)
vickpick said:
you might have done something with codecs and stuff if you've tried to use those bypasses to get free voip minutes on your phone (I think)
Click to expand...
Click to collapse
Nope, never done any of that
thanks, got it working on the first try. just to let you know, its much easier to use root explorer to do the editing. no need to copy anything over to someplace else, plus it backs up the original file too. but, root explorer doesnt show the line numbers, so you have to find the right lines yourself.
ceejay83 said:
Nope, never done any of that
Click to expand...
Click to collapse
weird, I've the exact same file as him
This is exactly what I have been waiting for!!! Finally AOSP BASED ROMS work with T-Mobile LTE.
I hope that ROM devs will incorporate this in their builds, but I'm entirely happy doing it manually.
Great Work:good::good:
Audio works on 4.2.2 on .33 baseband!
]Don't forget about the APN settings for T-mo
Name: T-Mobile US LTE
APN: fast.t-mobile.com
MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc
MCC: 310
MNC: 260
APN type: default,supl,mms
APN protocol: IPv4/IPv6
This is a huge discovery. Mad props to simobile. Is there a way to turn this into a .zip file flashable in recovery, like that zip that adds the lines to the build.prop for LTE? I'm no developer, but being able to flash this would be great, as opposed to editing the file every time a new ROM is flashed.
Sent from my Nexus 4 using Tapatalk 2
droidwrx said:
This is a huge discovery. Mad props to simobile. Is there a way to turn this into a .zip file flashable in recovery, like that zip that adds the lines to the build.prop for LTE? I'm no developer, but being able to flash this would be great, as opposed to editing the file every time a new ROM is flashed.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
copy the file, keep it in your storage, then copy/paste it in the proper place after a flash.
As much as I like cm this basically let's me come back to rasbean which is great.
Sent from my Nexus 4 using xda premium
You sir are the man! I can now successfully use pure aosp ROMs again with the .27 baseband. Very very impressive work.
Many thanks
Sent from my blazing bionic Nexus 4
It works! Too bad I don't have lte in nyc
I'm not in U.S and not using T-Mobile but I have a question, the problem you all talking about is no audio completely during a call, or you have audio but it's cutting off while talking? Cause i'm using .27 radio with 4.2.2 aosp and sometimes I lose incoming audio and my mic randomly during a call. I'll apply the fix if it's related to this problem?
sMtt said:
I'm not in U.S and not using T-Mobile but I have a question, the problem you all talking about is no audio completely during a call, or you have audio but it's cutting off while talking? Cause i'm using .27 radio with 4.2.2 aosp and sometimes I lose incoming audio and my mic randomly during a call. I'll apply the fix if it's related to this problem?
Click to expand...
Click to collapse
This is a very specific problem only for T-mobile customers I believe. Literally there is no audio at all. Like you can't hear the phone ring, the person talk, they can't hear you. Its like the entire microphone and speaker system of the phone shuts down when a call is initiated when on 4.2.2 roms with .33 radio on T-mobile.
Thanks again simobile. Awesome work.
muyoso said:
This is a very specific problem only for T-mobile customers I believe. Literally there is no audio at all. Like you can't hear the phone ring, the person talk, they can't hear you. Its like the entire microphone and speaker system of the phone shuts down when a call is initiated when on 4.2.2 roms with .33 radio on T-mobile.
Click to expand...
Click to collapse
Then it's not exactly my problem. I have things working but losing mic and audio sometimes. Maybe kernel related. Thanks for explanation :highfive:
This needs to be stickied

Bad gps on stock 5.0.1

Anybody experiencing bad gps on 5.0.1 GPE? I hardly get a fix and then I do, I often lost it. I really like playing ingress and it is no good for it.
I have recently bought this phone from another person, which declared it as Developer edition(but it has 32 Gb storage, and it was send to him directly from Czech HTC), it had stock 5.0.1 Lolipop pre-instaled and bootloader locked. I unlocked the bootloader on my phone and rooted it using TWRP 2.8.3.0.
I have also tried to flash htc stock based 4.4.3 rom(Viper 7.2), get fix there and get back to lolipop using nandroid backup, gps was a bit better afterwards, but it has messed the moint points of the internal sd-card and programs could not write to it. So I needed to relock and unlock bootloader again to get internal-sd card formated to the right way.
Do you think, that another radio can help this? I live in Czech republic, do you know which radio can work here?
This is what I have on fastboot screen:
***UNLOCKED***
M7_UL_PVT SHIP S-OFF RH
CID-HTC__032
RADIO-4T.30.3218.21
OpenDSP-v34.128.274.0429
OS-5.11.1700.3
eMMC-boot 2048MB
Dec 2 2014,22:11:20.0
hi!
since upgrade to 5.0.1 my GPS is also not working on my m7 gpe!
I found some reports from nexus owners too, but they wrote that they have disconnects, mine is complety messed up!
maps navigation while driving makes me crazy.
greetz
(Update)
fixed my gps by rooting and editing gps.conf
i used this, maybe you can get something more accurate for your location:
NTP_SERVER=0.de.pool.ntp.org
NTP_SERVER=1.de.pool.ntp.org
NTP_SERVER=2.de.pool.ntp.org
NTP_SERVER=3.de.pool.ntp.org
NTP_SERVER=0.europe.pool.ntp.org
NTP_SERVER=1.europe.pool.ntp.org
NTP_SERVER=2.europe.pool.ntp.org
NTP_SERVER=3.europe.pool.ntp.org
NTP_SERVER=de.pool.ntp.org
XTRA_SERVER_1=http://xtra1.gpsonextra.net/xtra.bin
XTRA_SERVER_2=http://xtra2.gpsonextra.net/xtra.bin
XTRA_SERVER_3=http://xtra3.gpsonextra.net/xtra.bin
# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
DEBUG_LEVEL =0
# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0
# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
ACCURACY_THRES=0
# Report supl ref location as position, 1=enable, 0=disable
REPORT_POSITION_USE_SUPL_REFLOC=1
# Wiper (wifi positioning), 1=enable, 0=disable
ENABLE_WIPER=1
################################
##### AGPS server settings #####
################################
# FOR SUPL SUPPORT, set the following
SUPL_HOST=supl.google.com
SUPL_PORT=7276
SUPL_NO_SECURE_PORT=3425
SUPL_SECURE_PORT=7275
SUPL_TLS_HOST=FQDN
SUPL_TLS_CERT=/etc/SuplRootCert
# FOR C2K PDE SUPPORT, set the following
C2K_HOST=c2k.pde.com
C2K_PORT=1234
CURRENT_CARRIER=common
DEFAULT_AGPS_ENABLE=TRUE
DEFAULT_SSL_ENABLE=FALSE
# TRUE for "User Plane", FALSE for "Control Plane"
DEFAULT_USER_PLANE=TRUE
Click to expand...
Click to collapse
xlokix said:
hi!
since upgrade to 5.0.1 my GPS is also not working on my m7 gpe!
I found some reports from nexus owners too, but they wrote that they have disconnects, mine is complety messed up!
maps navigation while driving makes me crazy.
greetz
(Update)
fixed my gps by rooting and editing gps.conf
i used this, maybe you can get something more accurate for your location:
Click to expand...
Click to collapse
Thanks, I will definitelly try this. I am now sending my phone to the service because of the purple camera issue so I will try it when my phone return.

Categories

Resources