Hi guys.
Since yesterday, I've noticed a strange issue on my Moto G: the compass does no longer work. I've tried a couple of apps from the Play Store, none works. GravityBox's "Compass" tile doesn't work either. I've also booted my phone into factory mode, opened the internal testing app (aka CQATest), and it also didn't pick up any readings from the magnetic sensor. I've flashed stock 4.4.4, GPE 4.4.4, CM11, and stock 5.0.1, but it didn't work with either firmware. Here's what the logcat shows when I try using the compass:
Code:
I/AKMD2 ( 321): Compass Opened.
D/Sensors ( 1114): AkmSensor: set enable_mag to 1
D/Sensors ( 1114): AkmSensor: set delay_mag to 200.000000 ms.
D/Sensors ( 1114): AkmSensor: mEnabled[1] = 1
D/Sensors ( 1114): AkmSensor: set delay_mag to 20.000000 ms.
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
E/AKMD2 ( 321): GetMagneticVector has failed (0x0004).
D/Sensors ( 1114): AccelerationSensor: set delay 200
D/Sensors ( 1114): AkmSensor: set enable_mag to 0
D/Sensors ( 1114): AkmSensor: set delay_mag to -0.000001 ms.
D/Sensors ( 1114): AkmSensor: mEnabled[1] = 0
I/AKMD2 ( 321): Compass Closed.
Has the magnetic sensor been definitely screwed up for some reason? If yes, I'll send my phone to a service center...
Hello, it seems my magnetic sensor has the same issue, did you figure it something out to resolve it?
i think this depends on the ROM you are in. my compass is totally bonkers ever since i've installed nougat based ROMs. it works very slow if you are able to calibrate it within the same app, but resets to its unusable state once you get out of the app
Thank you for your response, I'm using LOS 14.1 right now, but like you said all nougat roms give me problemes with compass, but in my case it doesn't give me any value on cpu-z, I tried flashing 5.1 stock rom and it gave me orientation sensor values but no magnetic field sensor values, I think sensor is broken. Maybe I'll try with other roms, I remember it was working ok with Identity Crisis with marshmallow
from what i remember it was working fine with MM ROMs i tried. happened only after flashing nougat ROMs. if you flashing an older ROM (pre-nougat) for the sake of getting compass working, and it still fails, i recommend you atleast run fastboot commands;
mfastboot erase modemst1
mfastboot erase modemst2
Click to expand...
Click to collapse
failing that, i would also reflash latest radio firmware with those commands;
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
Click to expand...
Click to collapse
Thank you, I tried that but it persist the same issue, on marshmallow or early orientation sensor gave me values but no magnetic field sensor values, on nougat magnetic sensor doesn't gave me values at all. Maybe sensor is broken.
koshikas said:
from what i remember it was working fine with MM ROMs i tried. happened only after flashing nougat ROMs. if you flashing an older ROM (pre-nougat) for the sake of getting compass working, and it still fails, i recommend you atleast run fastboot commands;
failing that, i would also reflash latest radio firmware with those commands;
Click to expand...
Click to collapse
Three years have passed since I wrote the original post. During that time, my (now dead) phone had its motherboard replaced due to a broken SIM card slot. Regardless of ROM and/or Android version, the magnetic sensor worked at all times (but it was slower under Nougat). So, it means that the previous board's sensor was gone for good.
(Or perhaps was it something software-related?)
Related
Here is log and source I've tried
Code:
D/HEROCSensors( 321): +open_data_source
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:open_data_source:
128
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:open_data_source:
131
D/HEROCSensors( 321): +_bma_open
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:52
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:55
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:65
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:71
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:78
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:80
E/HEROCSensors( 321): bma_open: failed to write bwidth range: -1
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:_bma_open:83
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:open_data_source:
134
W/HEROCSensors( 321): device/htc/liberty/libsensors/sensors.c:open_data_source:
149
E/HEROCSensors( 321): fd open failed in open_data_source! No handle returned.
D/PhoneWindow( 862): DebugMonitor class=com.android.browser.BrowserActivity foc
us=true
V/browser ( 862): onWindowFocusChanged hasWindowFocus:true
I/LOGTAG ( 862): HTCFlashPlugin.handleMessages
W/InputManagerService( 321): Window already focused, ignoring focus gain of: co
[email protected]
D/Twitter-MessageReceiver( 509): action android.intent.action.USER_PRESENT
D/FacebookReceiver( 509): Intent.ACTION_USER_PRESENT SyncInterval=7200000,currT
ime=1310057695771
D/FacebookReceiver( 509): Intent.ACTION_USER_PRESENT lastStreamSyncTime=1310057
695773,lastFriendSyncTime=1310057695773
But gsensor working:
Code:
D/G_SENSOR_CALIBRATION_USER( 2334): Calibration USER 1.7
D/G_SENSOR_CALIBRATION_USER( 2334): main: chip_layout = 1
D/G_SENSOR_CALIBRATION_USER( 2334): Offset setting: x=7 y=-12 z=-11
I not understand. Anyone have idea?
How its work
http://www.bel.fi/~alankila/Junk.git/akmd/jni/
i'm on it, it's part of the sensor lib.
and photon doesnt have akm.
Diference between Liberty and Heroc bma150 sensor library
G-Sensor fix ??
i see on http://htc-linux.org/wiki/index.php?title=PhotonStatus that the G sensor mus work. where can i find it ??? or is it not release yet?
tigercvv said:
G-Sensor fix ??
Click to expand...
Click to collapse
no, but r0bin will fix it
HI all,
after upgrading to CM10.2.0 + gapps20130813, I can't download any app from play store. Here is error log:
Code:
D/Finsky ( 2264): [1] LightPurchaseFlowActivity.handleAppPermissionResult: Permissions accepted: com.adobe.air
D/Finsky ( 2264): [1] InstallerImpl.requestInstall: Request install of com.adobe.air v=3900138 for single_install
D/Finsky ( 2264): [1] InstallerImpl.kick: Installer kick com.adobe.air - starting com.adobe.air
I/WindowManager( 393): Screenshot Window{4229a650 u0 com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity} was all black! mSurfaceLayer=21025 minLayer=21025 maxLayer=21025
D/DfeApi ( 2264): [1] FastHtmlParser.fromHtml: Doing slow HTML parse due to unexpected tag <a href="h
I/qtaguid ( 2264): Failed write_ctrl(u 55) res=-1 errno=22
I/qtaguid ( 2264): Untagging socket 55 failed errno=-22
W/NetworkManagementSocketTagger( 2264): untagSocket(55) failed with errno -22
I/qtaguid ( 2264): Failed write_ctrl(u 74) res=-1 errno=22
I/qtaguid ( 2264): Untagging socket 74 failed errno=-22
W/NetworkManagementSocketTagger( 2264): untagSocket(74) failed with errno -22
E/Volley ( 2264): [183] BasicNetwork.performRequest: Unexpected response code 500 for https://android.clients.google.com/fdfe/delivery?doc=com.adobe.air&ot=1&st=ENKZoJUF%0A&vc=3900138&bvc=3900106&pf=1&ch=X2W72i9OO7JwJusqo8TaRPiecyQ
I have tried to remove all the data and cache for app: Google play store and Google play service, and reboot the device. But that still didn't work.
Has anybody met the same issue ?
neo_yxm said:
HI all,
after upgrading to CM10.2.0 + gapps20130813, I can't download any app from play store. Here is error log:
Code:
D/Finsky ( 2264): [1] LightPurchaseFlowActivity.handleAppPermissionResult: Permissions accepted: com.adobe.air
D/Finsky ( 2264): [1] InstallerImpl.requestInstall: Request install of com.adobe.air v=3900138 for single_install
D/Finsky ( 2264): [1] InstallerImpl.kick: Installer kick com.adobe.air - starting com.adobe.air
I/WindowManager( 393): Screenshot Window{4229a650 u0 com.android.vending/com.google.android.finsky.billing.lightpurchase.LightPurchaseFlowActivity} was all black! mSurfaceLayer=21025 minLayer=21025 maxLayer=21025
D/DfeApi ( 2264): [1] FastHtmlParser.fromHtml: Doing slow HTML parse due to unexpected tag <a href="h
I/qtaguid ( 2264): Failed write_ctrl(u 55) res=-1 errno=22
I/qtaguid ( 2264): Untagging socket 55 failed errno=-22
W/NetworkManagementSocketTagger( 2264): untagSocket(55) failed with errno -22
I/qtaguid ( 2264): Failed write_ctrl(u 74) res=-1 errno=22
I/qtaguid ( 2264): Untagging socket 74 failed errno=-22
W/NetworkManagementSocketTagger( 2264): untagSocket(74) failed with errno -22
E/Volley ( 2264): [183] BasicNetwork.performRequest: Unexpected response code 500 for https://android.clients.google.com/fdfe/delivery?doc=com.adobe.air&ot=1&st=ENKZoJUF%0A&vc=3900138&bvc=3900106&pf=1&ch=X2W72i9OO7JwJusqo8TaRPiecyQ
I have tried to remove all the data and cache for app: Google play store and Google play service, and reboot the device. But that still didn't work.
Has anybody met the same issue ?
Click to expand...
Click to collapse
Try different network connection if not work try to go back anyof your nandroid backup.Maybe there is a bad sector in your sdcard try to do scandisk to your sdcard with windows scandisk app.
mypat said:
Try different network connection if not work try to go back anyof your nandroid backup.Maybe there is a bad sector in your sdcard try to do scandisk to your sdcard with windows scandisk app.
Click to expand...
Click to collapse
I have another device in the same network, and Google Market works well on it. And I don't think the bad sector will cause the HTTP 500 server side error.
After factory reset, the downloading get to work.
Now, in the progress to restore all my previous data.
neo_yxm said:
After factory reset, the downloading get to work.
Now, in the progress to restore all my previous data.
Click to expand...
Click to collapse
Also have the same problem, and can not settle down by factory reset
Mastermindsaifee said:
Also have the same problem, and can not settle down by factory reset
Click to expand...
Click to collapse
Try a clear cache from recovery.
andrei1015 said:
Try a clear cache from recovery.
Click to expand...
Click to collapse
Ok trying
---------- Post added at 03:19 PM ---------- Previous post was at 03:15 PM ----------
andrei1015 said:
Try a clear cache from recovery.
Click to expand...
Click to collapse
Reset to factory settings
Tried with a different account
Wipe cache from 4EXT Recovery
Still same issue ....
---------- Post added at 03:22 PM ---------- Previous post was at 03:19 PM ----------
andrei1015 said:
Try a clear cache from recovery.
Click to expand...
Click to collapse
Is that related to fixing permissions from recovery ? Please guide me if that so, i have 4EXT recovery
I'm not sure what the fix permissions option does.But you can try it. I don't think you're going to lose much.
andrei1015 said:
I'm not sure what the fix permissions option does.But you can try it. I don't think you're going to lose much.
Click to expand...
Click to collapse
In recovery , I tap on "Fix permissions", and then the problem solved
Some of you may be familiar with my trials with my T699. To make a long story short, (see that story here http://forum.xda-developers.com/showthread.php?t=2528444) (thanks gee one!)
I was attempting to put CM on my Relay and I ended up hard bricking it.
I can now boot but I need a SD card installed to do it.
Recently I was playing around with adb and was running logcat which dumped a whole mess of wonderful information.
The line I thought was important was the following -
I/rmt_storage( 125): No EBR found
It is my guess that I messed up (corrupted) the EBR and that is why I am dependent on the external SD card.
My question is, does anyone know how to restore the EBR to working condition? I have tried to use odin to put the stock
image on but I think it is just over-writing the image on the SD card. If it can be done using adb that would be very great too since
it appears to be working well.
Oh, and the other thing I noticed, if I do not put the SD card, with image, into the slot I just boot into QHSUSB-DLOAD mode.
Which means much but is not useful at this time.
Thanks all,
Lou
I have added the first 25 lines of the logcat -
--------- beginning of /dev/log/main
I/rmt_storage( 125): Target is APQ8064: 1074445686
I/rmt_storage( 125): No EBR found
I/rmt_storage( 125): Error (-1) parsing MBR partitions
I/rmt_storage( 125): Registering modemst1: 0x4a /boot/modem_fs1
I/rmt_storage( 125): Registering modemst2: 0x4b /boot/modem_fs2
I/rmt_storage( 125): Registering fsg: 0x58 /boot/modem_fsg
I/rmt_storage( 125): Registering ssd: 0x5d ssd
I/rmt_storage( 125): 4 GPT partitions found
D/ICD ( 183): icd .02 runs
E/DataRouter( 186): Main entered
E/DataRouter( 186): switchUser
E/DataRouter( 186): monitor_usb_thread
E/DataRouter( 186): server_init
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Opening of the usb select file failed fd is -1 & errno is 2
E/DataRouter( 186): Initialise USB and start the thread
E/DataRouter( 186): dr_usb_init
E/DataRouter( 186): USB Interface is open with 0x9
E/DataRouter( 186): USB interface is now configured for usb_fd = 0x9
E/DataRouter( 186): THREAD LAUNCH
E/DataRouter( 186): monitor_data_of_usb
E/DataRouter( 186): USB monitor thread launched, usb_fd= 0x9
E/DataRouter( 186): init_cur_sock
E/DataRouter( 186): Before the usb select
I/DEBUG ( 182): debuggerd: Mar 16 2013 22:15:51
*** UPDATE ***
I found another interesting line in line in the logcat ...
W/PackageManager( 674): Library not found: /system/framework/com.qualcomm.location.quipslib.jar
More on de-bricking
I have been continuing my hunt on how to permanently de-brick my T699. The following thread does not leave me with
much hope . I know it is for Evita on the HTC One but I see similar behaviour when I hook my T699 to linux.
http://forum.xda-developers.com/showthread.php?t=1966850&page=40
If anyone can comment on this it is greatly appreciated.
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
I/MountService( 872): encrypting storage...
I/power ( 872): *** release_dvfs_lock : lockType : 1
D/SSRMv2:CustomFrequencyManagerService( 872): releaseDVFSLockLocked : Getting Lock type frm List : DVFS_MIN_LIMIT frequency : 1188000 uid : 1000 pid : 872 tag : [email protected]
D/lights ( 872): button : 0 +
D/lights ( 872): button : 0 -
D/qdutils ( 321): getuiClearRegion:70 wormRect( l = 0 t = 0 r = 720 b = 50)
D/qdutils ( 321): getuiClearRegion:76 FinalwormRect( l = 0 t = 0 r = 720 b = 50)
E/SMD ( 346): DCD ON
I/SecureStorage(12345): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(12345): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Load image request failed ret = -1, errno = 14
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (12345): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (12345): App is not loaded in QSEE
E/QSEECOMAPI: (12345): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (12345): Error::Loading image failed with ret = -1
E/SecureStorage(12345): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(12345): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(12345): [ERROR]:Error cannot connect to TA/driver!
Click to expand...
Click to collapse
Any ideas?
ccoager said:
Using Stock 4.3 ROM from here,
http://forum.xda-developers.com/showthread.php?t=2591895
After a fresh install, wipe /data, wipe /cache, wipe /dalvik cache - I tried a full device encryption. I get a picture of a green Android but nothing happens. As I read, the device should reboot and start the encryption process. However, mine never reboots.
I checked logcat and it has some interesting messages,
Any ideas?
Click to expand...
Click to collapse
My recommendation? DON'T DO ENCRYPTION!! you may get your phone in a lockmode and unable to recover data..
Is there anything else that could be causing this?
I have not chosen device encryption and I am also seeing these messages in logcat..
I/SecureStorage(15360): [INFO]: Secure Storage Daemon is preparing to run
I/SecureStorage(15360): [INFO]: Secure Storage Daemon successfully binded a socket
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_stor.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
D/QSEECOMAPI: (15360): QSEECom_start_app sb_length = 0x19a040
D/QSEECOMAPI: (15360): App is not loaded in QSEE
E/QSEECOMAPI: (15360): Error::Cannot open the file /firmware/image//sec_storage.mdt
E/QSEECOMAPI: (15360): Error::Loading image failed with ret = -1
E/SecureStorage(15360): [ERROR]:Loading app sec_stor and sec_storage failed
E/SecureStorage(15360): [ERROR]:Fail to open session with qualcomm
E/SecureStorage(15360): [ERROR]:Error cannot connect to TA/driver!
E/SMD ( 213): DCD ON
Same Problem
I am getting the same thing and when I rooted my SCH-r530u I disabled the Knox thing
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon is preparing to run
02-20 22:57:11.660: I/SecureStorage(10292): [INFO]: Secure Storage Daemon successfully binded a socket
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_stor.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: D/QSEECOMAPI10292): QSEECom_start_app sb_length = 0x19a040
02-20 22:57:11.660: D/QSEECOMAPI10292): App is not loaded in QSEE
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Cannot open the file /firmware/image//sec_storage.mdt
02-20 22:57:11.660: E/QSEECOMAPI10292): Error::Loading image failed with ret = -1
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Loading app sec_stor and sec_storage failed
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Fail to open session with qualcomm
02-20 22:57:11.660: E/SecureStorage(10292): [ERROR]:Error cannot connect to TA/driver!
02-20 22:57:12.161: V/AlarmManager(411): waitForAlarm result :8
Click to expand...
Click to collapse
What does it mean? I keep getting it every few seconds while the screen is on
* I was going to edit out the sad faces but its too funny cause it fits the situation perfectly*
hi all, as the title says my gps is broken after upgrading through odin. Neither restoring NC2 or flashing cm11 solved the issue. Can anyone tell me if is an hadware problem? logcat keep continously spamming this while searching location
E/LocSvc_ApiV02(856): D/virtual void LocApiV02::eventCb(locClientHandleType, uint32_t, locClientEventIndUnionType):2551]: event id = 36
E/LocSvc_ApiV02(856): D/Reporting postion from V2 Adapter
E/LocSvc_utils_q(856): D/msg_q_snd: Sending message with handle = 0x792A50B0
E/LocSvc_utils_ll(856): D/linked_list_add: Adding to list data_obj = 0x792A50B0
E/LocSvc_utils_q(856): D/msg_q_snd: Finished Sending message with handle = 0x792A50B0
E/LocSvc_utils_ll(856): D/linked_list_remove: Removing from list
E/LocSvc_utils_q(856): D/msg_q_rcv: Received message 0x792A50B0 rv = 0
E/LocSvc_MsgTask(856): D/MsgTask::loop() 865 listening ...
E/LocSvc_utils_q(856): D/msg_q_rcv: Waiting on message
E/LocSvc_utils_q(856): D/msg_q_snd: Sending message with handle = 0x88B7F318
E/LocSvc_utils_ll(856): D/linked_list_add: Adding to list data_obj = 0x88B7F318
E/LocSvc_utils_q(856): D/msg_q_snd: Finished Sending message with handle = 0x88B7F318
E/LocSvc_utils_ll(856): D/linked_list_remove: Removing from list
E/LocSvc_utils_q(856): D/msg_q_rcv: Received message 0x88B7F318 rv = 0
E/LocSvc_MsgTask(856): D/MsgTask::loop() 866 listening ...
E/LocSvc_utils_q(856): D/msg_q_rcv: Waiting on message
E/LocSvc_ApiV02(856): D/void LocApiV02::reportPosition(const qmiLocEventPositionReportIndMsgT_v02*):2004]: Ignoring position report with sess status = 7, fix id = 119
E/LocSvc_ApiV02(856): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 90 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
effry said:
hi all, as the title says my gps is broken after upgrading through odin. Neither restoring NC2 or flashing cm11 solved the issue. Can anyone tell me if is an hadware problem? logcat keep continously spamming this while searching location
E/LocSvc_ApiV02(856): D/virtual void LocApiV02::eventCb(locClientHandleType, uint32_t, locClientEventIndUnionType):2551]: event id = 36
E/LocSvc_ApiV02(856): D/Reporting postion from V2 Adapter
E/LocSvc_utils_q(856): D/msg_q_snd: Sending message with handle = 0x792A50B0
E/LocSvc_utils_ll(856): D/linked_list_add: Adding to list data_obj = 0x792A50B0
E/LocSvc_utils_q(856): D/msg_q_snd: Finished Sending message with handle = 0x792A50B0
E/LocSvc_utils_ll(856): D/linked_list_remove: Removing from list
E/LocSvc_utils_q(856): D/msg_q_rcv: Received message 0x792A50B0 rv = 0
E/LocSvc_MsgTask(856): D/MsgTask::loop() 865 listening ...
E/LocSvc_utils_q(856): D/msg_q_rcv: Waiting on message
E/LocSvc_utils_q(856): D/msg_q_snd: Sending message with handle = 0x88B7F318
E/LocSvc_utils_ll(856): D/linked_list_add: Adding to list data_obj = 0x88B7F318
E/LocSvc_utils_q(856): D/msg_q_snd: Finished Sending message with handle = 0x88B7F318
E/LocSvc_utils_ll(856): D/linked_list_remove: Removing from list
E/LocSvc_utils_q(856): D/msg_q_rcv: Received message 0x88B7F318 rv = 0
E/LocSvc_MsgTask(856): D/MsgTask::loop() 866 listening ...
E/LocSvc_utils_q(856): D/msg_q_rcv: Waiting on message
E/LocSvc_ApiV02(856): D/void LocApiV02::reportPosition(const qmiLocEventPositionReportIndMsgT_v02*):2004]: Ignoring position report with sess status = 7, fix id = 119
E/LocSvc_ApiV02(856): I/<--- void globalEventCb(locClientHandleType, uint32_t, locClientEventIndUnionType, void*) line 90 QMI_LOC_EVENT_POSITION_REPORT_IND_V02
Click to expand...
Click to collapse
Have you tried downloading gps test from playstore and clear your ephemeris data. Then reboot
xdm9mm said:
Have you tried downloading gps test from playstore and clear your ephemeris data. Then reboot
Click to expand...
Click to collapse
Yes but no help at all the app did not even see see satellites
Inviato dal mio SM-N9005 utilizzando Tapatalk
My gps doesn't work on Samsung 4.4.2. It works on Temaseks AOSP rom
Sent from my SM-N9005 using Tapatalk
effry said:
Yes but no help at all the app did not even see see satellites
Inviato dal mio SM-N9005 utilizzando Tapatalk
Click to expand...
Click to collapse
I have a satlock within 3 seconds, may i suggest to reflash the rom you have followed by a data factory reset Runing ND3 stock.
gee2012 said:
I have a satlock within 3 seconds, may i suggest to reflash the rom you have followed by a data factory reset Runing ND3 stock.
Click to expand...
Click to collapse
I've tried completely wiping my device and installing several different stock Kitkat roms but it still won't work. Have you ever had any gps problems or has it always worked?
Sent from my SM-N9005 using Tapatalk
matust said:
I've tried completely wiping my device and installing several different stock Kitkat roms but it still won't work. Have you ever had any gps problems or has it always worked?
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
It always worked for me, maybe you just have a defective device (gps module) that needs to be repaired.
It worked fine for me on 4.3, and works fine on AOSP 4.4.2. Kitkat hasn't been released on any of the carriers in my country so I can only hope that will fix it.
Sent from my SM-N9005 using Tapatalk