• 2

G3 GPS收訊不良 完全解決方法

感謝大大,找出位置了,墊了紙片後,抓到13顆以上,之前不到10顆,這方法太有效了,我的GPS又真正復活了
charles.cyc wrote:
請問第二張圖是哪一...(恕刪)


第二張圖是拆下上背蓋的反面,我也對了一會兒才找到~

charles.cyc wrote:
請問第二張圖是哪一個...(恕刪)
照這方法試過了,最近在車上放前檔也沒用,
昨天在拆開一次,用砂紙磨過的漆包線,直接
再兩個接點繞圈連接起來,線大概留25-30mm
但原本的天線接觸面沒有貼起來,
在空曠地站了5分鐘,頂多只有一顆。
這是天線問題還是gps. Conf的問題?



貼上gps. Conf
# This configuration file (GPS) is automatically generated from shell script.
#Uncommenting these urls would only enable
#the power up auto injection and force injection(test case).
#XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra2.bin
#XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra2.bin
#XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra2.bin
# TODO:LGE_GNSS: Please DO enable the next line when you merge the CAF
XTRA_SERVER_1=http://xtrapath1.izatcloud.net/xtra3grc.bin
XTRA_SERVER_2=http://xtrapath2.izatcloud.net/xtra3grc.bin
XTRA_SERVER_3=http://xtrapath3.izatcloud.net/xtra3grc.bin
#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

#Version check for XTRA
#DISABLE = 0
#AUTO = 1
#XTRA2 = 2
#XTRA3 = 3
XTRA_VERSION_CHECK=0

# Error Estimate
# _SET = 1
# _CLEAR = 0
ERR_ESTIMATE=0

# Server Region
NTP_SERVER=time. stdtime. gov. tw

# DEBUG LEVELS: 0 - none, 1 - Error, 2 - Warning, 3 - Info
# 4 - Debug, 5 - Verbose
# If DEBUG_LEVEL is commented, Android's logging levels will be used
DEBUG_LEVEL=1

# Intermediate position report, 1=enable, 0=disable
INTERMEDIATE_POS=0

# Below bit mask configures how GPS functionalities
# should be locked when user turns off GPS on Settings
# Set bit 0x1 if MO GPS functionalities are to be locked
# Set bit 0x2 if NI GPS functionalities are to be locked
# default - non is locked for backward compatibility
#GPS_LOCK = 0
# TODO:GNSS_LGE: Please DO enable the next line when you merge the CAF
GPS_LOCK=0x0

# supl version 1.0
SUPL_VER=0x20000

# Emergency SUPL, 1=enable, 0=disable
SUPL_ES=0

#Choose PDN for Emergency SUPL
#1 - Use emergency PDN
#0 - Use regular SUPL PDN for Emergency SUPL
USE_EMERGENCY_PDN_FOR_EMERGENCY_SUPL=0

#SUPL_MODE is a bit mask set in config.xml per carrier by default.
#If it is uncommented here, this value will overwrite the value from
#config.xml.
#MSA=0X2
#MSB=0X1
#SUPL_MODE=
# TODO:LGE_GNSS: Please DO enable the next line when you merge the CAF
SUPL_MODE=1

# GPS Capabilities bit mask
# SCHEDULING = 0x01
# MSB = 0x02
# MSA = 0x04
# ON_DEMAND_TIME = 0x10
# GEOFENCE = 0x20
# default = ON_DEMAND_TIME | MSA | MSB | SCHEDULING | GEOFENCE
CAPABILITIES=0x31

# Accuracy threshold for intermediate positions
# less accurate positions are ignored, 0 for passing all positions
# ACCURACY_THRES=5000

################################
##### AGPS server settings #####
################################

# FOR SUPL SUPPORT, set the following
# SUPL_HOST=supl.google.com
# SUPL_PORT=7276
# TODO:LGE_GNSS: Please DO enable the next line when you merge the CAF
SUPL_HOST=supl.google.com
SUPL_PORT=7276

# FOR C2K PDE SUPPORT, set the following
# C2K_HOST=c2k.pde.com or IP
# C2K_PORT=1234

# Bitmask of slots that are available
# for write/install to, where 1s indicate writable,
# and the default value is 0 where no slots
# are writable. For example, AGPS_CERT_WRITABLE_MASK
# of b1000001010 makes 3 slots available
# and the remaining 7 slots unwritable.
#AGPS_CERT_WRITABLE_MASK=0

####################################
# LTE Positioning Profile Settings
####################################
# 0: Enable RRLP on LTE(Default)
# 1: Enable LPP_User_Plane on LTE
# 2: Enable LPP_Control_Plane
# 3: Enable both LPP_User_Plane and LPP_Control_Plane
LPP_PROFILE=0

################################
# EXTRA SETTINGS
################################
# NMEA provider (1=Modem Processor, 0=Application Processor)
NMEA_PROVIDER=1
# Mark if it is a SGLTE target (1=SGLTE, 0=nonSGLTE)
SGLTE_TARGET=0

##################################################
# Select Positioning Protocol on A-GLONASS system
##################################################
# 0x1: RRC CPlane
# 0x2: RRLP UPlane
# 0x4: LLP Uplane
A_GLONASS_POS_PROTOCOL_SELECT=0x0

################################
# LGE EXTRA SETTINGS
################################
VENDOR=GLOBAL
LGE_TLS_MODE=1
LGE_GPS_POSITION_MODE=1
LGE_IMPROVE_LOCATION_ERROR=1

################################
# LGE GLOBAL SUPL SETTINGS
################################
#NTP_SERVER#
NTP_SERVER=time. stdtime. gov. tw
NTP_SERVER_US=north-america.pool.ntp.org
NTP_SERVER_EU=europe.pool.ntp.org
NTP_SERVER_CIS=ru.pool.ntp.org
NTP_SERVER_AU=oceania.pool.ntp.org
NTP_SERVER_SCA=south-america.pool.ntp.org
NTP_SERVER_AME=africa.pool.ntp.org


#SUPL_VER#
SUPL_VER_262_2=0x20000
SUPL_VER_214_1=0x20000
SUPL_VER_222_10=0x20000
SUPL_VER_UNF=0x10000

#SUPL_HOST#
SUPL_HOST_262_2=supl.vodafone.com
SUPL_HOST_214_1=supl.vodafone.com
SUPL_HOST_214_18=supl.vodafone.com
SUPL_HOST_222_10=supl.vodafone.com
SUPL_HOST_204_4=supl.vodafone.com
SUPL_HOST_268_1=supl.vodafone.com
SUPL_HOST_226_1=supl.vodafone.com
SUPL_HOST_202_5=supl.vodafone.com
SUPL_HOST_530_1=supl.vodafone.com
SUPL_HOST_276_2=supl.vodafone.com
SUPL_HOST_278_1=supl.vodafone.com
SUPL_HOST_234_15=supl.vodafone.com
SUPL_HOST_286_2=supl.vodafone.com
SUPL_HOST_505_3=supl.vodafone.com
SUPL_HOST_208_10=supl.google.com
SUPL_HOST_647_10=supl.google.com
SUPL_HOST_208_9=supl.google.com
SUPL_HOST_UNF=supl.iusacell.com
SUPL_HOST_NXT=location.entel.pe

#SUPL_PORT#
SUPL_PORT_262_2=7275
SUPL_PORT_214_1=7275
SUPL_PORT_214_18=7275
SUPL_PORT_222_10=7275
SUPL_PORT_204_4=7275
SUPL_PORT_268_1=7275
SUPL_PORT_226_1=7275
SUPL_PORT_202_5=7275
SUPL_PORT_530_1=7275
SUPL_PORT_276_2=7275
SUPL_PORT_278_1=7275
SUPL_PORT_234_15=7275
SUPL_PORT_286_2=7275
SUPL_PORT_505_3=7275
SUPL_PORT_208_10=7275
SUPL_PORT_647_10=7275
SUPL_PORT_208_9=7275
SUPL_PORT_UNF=7275
SUPL_PORT_NXT=7275

#LGE_TLS_MODE#
LGE_TLS_MODE_262_2=1
LGE_TLS_MODE_214_1=1
LGE_TLS_MODE_222_10=1
LGE_TLS_MODE_204_4=1
LGE_TLS_MODE_268_1=1
LGE_TLS_MODE_226_1=1
LGE_TLS_MODE_202_5=1
LGE_TLS_MODE_530_1=1
LGE_TLS_MODE_276_2=1
LGE_TLS_MODE_278_1=1
LGE_TLS_MODE_234_15=1
LGE_TLS_MODE_286_2=1
LGE_TLS_MODE_505_3=1
LGE_TLS_MODE_208_10=1
LGE_TLS_MODE_647_10=1
LGE_TLS_MODE_208_9=1
LGE_TLS_MODE_UNF=7

################################
# LGE DEBUG INFORMATION
################################

# [1] target__Product= g3_global_com
# [2] target__Device= g3
# [3] target__Carrier= GLOBAL
# [4] target__Country= COM
# [5] target__Chipset= MSM8974
# [6] target__EngineVer= GEN8B
# [7] target__BuildVariant=

##############EOF################
你把訊號根地線直接短路

手機抓的到訊號才有鬼....
不知是不是刷了fulmics 7.6的關係

不管是接漆包線還是把底部墊高增加接觸面積,在空曠地GPS TEST不是橘就是黃,還沒看過綠色

而且還是站了2分鐘左右才有這成果




老婆的SAMSUNG手機貼在落地門上,才2-3秒就跑一堆出來室內竟然還有這麼多

我的室內0顆





有人刷fulmics 7.x版也會這樣嗎?

nagisaK wrote:
你把訊號根地線直接...(恕刪)







nagisak大,

我試過了夾紙片,空曠地等了3分鐘,還是抓不太到衛星頂多2-3顆Inview,1顆inuse

3Dfix完全跑不出來,一直顯示No Fix

我照你的說明焊接一條細的漆包線(砂紙磨過),背蓋先不鎖上去,1-2分鐘後可以抓到十幾顆衛星

背蓋接點用膠帶貼起來後,鎖上背蓋又抓不太到了!一定要天線外露???我把漆包線鎖在背蓋裡,

G3的GPS真的體質不良,不曉得是硬體的關係還是韌體的關係?

要把銅線穿過背蓋

然後用膠帶固定在背板外面

(同時要把原本的天線接點用膠帶絕緣貼起來

我指的是原本背蓋內的原廠GPS天線 也就是原本教學說背後要墊紙的那個 上下兩個金屬接點都要用膠帶蓋起來

這樣GPS訊號才會從銅線收進來)

反正你蓋上外殼後也看不到

(如果蓋不起來 你就用細一點漆包線的 我是用很細那種)

既然你天線拉出來能抓到衛星 那應該不是韌體問題

(題外話 新刷機第一次定位比較久是正常的)



  • 2
內文搜尋
X
評分
評分
複製連結
Mobile01提醒您
您目前瀏覽的是行動版網頁
是否切換到電腦版網頁呢?