[Q] GPS issue / cannot turn on

Search This thread

p012t

Member
May 13, 2014
9
0
Hi guys,

I am having issues with my GPS/location service. Basically it will not turn on. When I try to turn it on in settings it just freezes and I get an error saying settings has closed. When I try to use the toggle switch from the pull down menu same thing but this time the System UI has stopped.

Has anybody ran into this issue before? Please help out

if this helps i am rooted on infamous v8.0 rom / 3.4.0 kernel / andriod 4.2.2

Thank You all
 
Last edited:

Karakoram2

Senior Member
May 7, 2011
1,125
492
Could try reflashing your ROM or Odin to stock and start over.



Sent from my SGH-M919 using XDA Premium 4 mobile app
 

p012t

Member
May 13, 2014
9
0
Try checking the logcat after it crashes.

Sent from my Galaxy S4

Hey, I checked the logcat as you send and I narrowed it down to this, I think this is the error im not too sure
its kind of hard to read

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

Do you have any idea if this is the issue and how do I fix this ?

Thank you
 

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
Hey, I checked the logcat as you send and I narrowed it down to this, I think this is the error im not too sure
its kind of hard to read

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

Do you have any idea if this is the issue and how do I fix this ?

Thank you

Just a guess, but try fixing permissions in recovery, or open terminal emulator and run
Code:
 ls -l /dev
 
  • Like
Reactions: p012t

Skipjacks

Senior Member
Nov 1, 2011
5,416
4,329
Baltimore
I already have wiped the cache and dalik cache as well as fixing permission from recovery. Nothing worked

Then you are left with no recourse other than to reflash the rom in recovery or flash back to stock using Odin and start over.

Your logcat doesn't show the cause of the problem. It just shows the result of the problem.
 

MultipleMonomials

Senior Member
May 25, 2012
724
244
San Diego
I think that reflashing the rom doesn't affect the /dev partition. Maybe fix permissions doesn't either. Would you run the ls -l command and post the output?

Sent from my Galaxy S4
 

p012t

Member
May 13, 2014
9
0
I think that reflashing the rom doesn't affect the /dev partition. Maybe fix permissions doesn't either. Would you run the ls -l command and post the output?

Sent from my Galaxy S4

ran the command and all this shows up

sh-3.2$ ls -l
-rw-r--r-- root root 4686 1969-12-31 19:00 MSM8960_lpm.rc
drwxr-xr-x root root 1971-01-02 22:43 acct
drwxrwx--- system cache 1970-12-30 01:22 cache-rwxr-x--- root root 268108 1969-12-31 19:00 charger
dr-x------ root root 1971-01-02 22:43 config
lrwxrwxrwx root root 1971-01-02 22:43 d -> /sys/kernel/debug
drwxrwx--x system system 2014-05-16 19:34 data
drwxrwx--- system system 1971-01-02 22:43 data_1
drwxrwx--- system system 1971-01-02 22:43 data_2
drwxrwx--- system system 1971-01-02 22:43 data_3
-rw-r--r-- root root 136 1969-12-31 19:00 default.prop
drwxr-xr-x root root 2014-05-15 17:23 dev
drwxrwx--x system radio 2013-10-25 23:14 efs
lrwxrwxrwx root root 1971-01-02 22:43 etc -> /system/etc
-rw-r--r-- root root 18622 1969-12-31 19:00 file_contexts
dr-xr-x--- system system 1969-12-31 19:00 firmware
dr-xr-x--- system system 1969-12-31 19:00 firmware-mdm
-rw-r--r-- root root 768 1969-12-31 19:00 fstab.qcom
-rwxr-x--- root root 164648 1969-12-31 19:00 init
-rwxr-x--- root root 4638 1969-12-31 19:00 init.carrier.rc
-rwxr-x--- root root 2487 1969-12-31 19:00 init.goldfish.rc
-rwxr-x--- root root 6737 1969-12-31 19:00 init.qcom.class_core.sh
-rwxr-x--- root root 2320 1969-12-31 19:00 init.qcom.class_main.sh
-rwxr-x--- root root 4266 1969-12-31 19:00 init.qcom.early_boot.sh
-rwxr-x--- root root 5142 1969-12-31 19:00 init.qcom.lpm_boot.sh
-rwxr-x--- root root 22863 1969-12-31 19:00 init.qcom.rc
-rwxr-x--- root root 3045 1969-12-31 19:00 init.qcom.ril.sh
-rwxr-x--- root root 4486 1969-12-31 19:00 init.qcom.sh
-rwxr-x--- root root 3514 1969-12-31 19:00 init.qcom.syspart_fixup.sh
-rwxr-x--- root root 35297 1969-12-31 19:00 init.qcom.usb.rc
-rwxr-x--- root root 6004 1969-12-31 19:00 init.qcom.usb.sh
-rwxrwxrwx root root 38414 1969-12-31 19:00 init.rc
-rwxr-x--- root root 9193 1969-12-31 19:00 init.target.rc
-rwxr-x--- root root 1795 1969-12-31 19:00 init.trace.rc
-rwxr-x--- root root 3947 1969-12-31 19:00 init.usb.rc
drwxrwxr-x root system 1971-01-02 22:43 mnt
drwxrwxr-x root system 1971-01-02 22:43 mnt_1drwxr-xr-x system system 1971-01-02 22:43 persdata
drwxrwx--x system system 1971-01-02 22:43 preload
dr-xr-xr-x root root 1969-12-31 19:00 proc
-rw-r--r-- root root 2759 1969-12-31 19:00 property_contexts
drwxr-xr-x root root 1969-12-31 19:00 res
drwx------ root root 2013-06-06 21:35 root
drwxr-x--- root root 1969-12-31 19:00 sbin
lrwxrwxrwx root root 1971-01-02 22:43 sdcard -> /storage/emulated/legacy
-rw-r--r-- root root 1976 1969-12-31 19:00 seapp_contexts
-rw-r--r-- root root 134977 1969-12-31 19:00 sepolicy
dr-xr-x--- system sdcard_r 1971-01-02 22:43 storage
dr-xr-xr-x root root 1971-01-02 22:43 sys
drwxr-xr-x root root 2014-01-08 19:49 system
lrwxrwxrwx root root 1971-01-02 22:43 tombstones -> /data/tombstones
-rw-r--r-- root root 272 1969-12-31 19:00 ueventd.goldfish.rc
-rw-r--r-- root root 6662 1969-12-31 19:00 ueventd.qcom.rc
-rw-r--r-- root root 4794 1969-12-31 19:00 ueventd.rc
lrwxrwxrwx root root 1971-01-02 22:43 vendor -> /system/vendor
sh-3.2$

once again thank you all for helping
 

waylo

Senior Member
May 9, 2010
1,670
489
I had the exact same thing happen myself!

First time was last week. Out of the blue, GPS shut itself off and wouldn't come back. Systemui closes with any attempt to turn on GPS.

I found that if I cleared the data partition it came back. Not a great solution as it didn't pinpoint a cause. Not sure how a setting related to gps could get so messed up as to deactivate it.

A week later, the same error popped up.

I put in for a warranty replacement, in case it was a hardware issue.

Running wicked 6.

---------- Post added at 07:04 AM ---------- Previous post was at 07:01 AM ----------

My phone is still in the same state so happy to help troubleshoot with you.

Trying what was recommended here now.

---------- Post added at 07:15 AM ---------- Previous post was at 07:04 AM ----------

When it borked last week, I found that restoring an older system partition did not help at all. But formatting the data partition did.

I was a bit perplexed because I wasn't sure how an app could muck up the GPS settings such that it wouldn't be able to turn on!
 

PanchoPlanet

Senior Member
Oct 15, 2011
3,894
984
Crooklyn
I think data partition keeps system app data and non system app data separate. ???
Feel free to elaborate.
Pp.

Sent from my SGH-M919 using XDA Premium 4 mobile app
 

waylo

Senior Member
May 9, 2010
1,670
489
Well the system apps are kept in the system partition. The settings related to the system are kept in the data partition. So very few things done day to day affect the system partition directly.

At least for me, I've had the same setup for almost 5 months as I never saw the reason to upgrade past 4.2.2. So having this happen to me twice in two weeks is worrisome.

The fact that I could get things restored by wiping /data points to some corrupted setting perhaps. I restored the apps from my nandroid and that worked fine for another week so I don't think it's a user app, but certainly possible.

OP, don't mean to hijack your thread but I think the situation is the same.

If you wish for a quick fix, backup your apps/sms/etc, wipe data, then restore the apps individually with titanium backup.
 

p012t

Member
May 13, 2014
9
0
I think you ran ls -l and not ls -l /dev. My fault for giving confusing directions.

Sent from my Galaxy S4

no problem this is what i get when i run it

sh-3.2$ ls -l/dev
ls: Unknown option '-/'. Aborting.
sh-3.2$ ls -l /dev
crw-rw-r-- system radio 10, 26 1971-01-02 22:43 alarmcrw-rw---- adb adb 10, 31 1971-01-02 22:43 android_adb
crw-rw-rw- root root 10, 22 1971-01-02 22:43 ashmem
crw------- nfc nfc 10, 35 1971-01-02 22:43 bcm2079x
crw-rw-rw- root root 10, 23 1971-01-02 22:43 binder
drwxr-xr-x root root 2014-05-15 17:22 blockcrw------- bluetooth bluetooth 10, 224 1971-01-02 22:43 btlock
drwxr-xr-x root root 1971-01-02 22:43 bus
crw------- root root 10, 29 1971-01-02 22:43 ccid_bulk
crw------- root root 10, 30 1971-01-02 22:43 ccid_ctrl
crw------- root root 5, 1 1971-01-02 22:43 console
crw------- root root 10, 14 1971-01-02 22:43 cpu_dma_latency
drwxr-xr-x system system 1971-01-02 22:43 cpuctl
crw------- root root 10, 236 1971-01-02 22:43 device-mapper
crw-rw---- system qcom_diag 243, 0 1971-01-02 22:43 diagcrw------- root root 10, 56 1971-01-02 22:43 dsp_debug
crw------- root root 10, 37 1971-01-02 22:43 ecryptfs
crw-rw---- system system 10, 17 2014-05-15 17:23 efs_bridge
crw------- root root 10, 25 1971-01-02 22:43 epm_adc
crw-rw-rw- root root 1, 7 1971-01-02 22:43 full
crw------- root root 10, 229 1971-01-02 22:43 fuse
crw-rw---- system camera 235, 0 1971-01-02 22:43 gemini0
crw-rw-rw- system system 10, 36 1971-01-02 22:43 genlock
drwxr-xr-x root root 1971-01-02 22:43 graphics
crw-r----- radio radio 239, 0 1971-01-02 22:43 hsicctl0
crw-r----- radio radio 239, 1 1971-01-02 22:43 hsicctl1
crw-r----- radio radio 239, 2 1971-01-02 22:43 hsicctl2
crw-r----- radio radio 239, 3 1971-01-02 22:43 hsicctl3
crw-rw---- system system 10, 183 1971-01-02 22:43 hw_random
crw------- root root 89, 0 1971-01-02 22:43 i2c-0crw------- root root 89, 11 1971-01-02 22:43 i2c-11
crw------- root root 89, 12 1971-01-02 22:43 i2c-12
crw------- root root 89, 13 1971-01-02 22:43 i2c-13
crw------- root root 89, 16 1971-01-02 22:43 i2c-16
crw------- root root 89, 17 1971-01-02 22:43 i2c-17
crw------- root root 89, 2 1971-01-02 22:43 i2c-2crw------- root root 89, 21 1971-01-02 22:43 i2c-21
crw------- root root 89, 3 1971-01-02 22:43 i2c-3crw------- root root 89, 4 1971-01-02 22:43 i2c-4crw------- root root 89, 7 1971-01-02 22:43 i2c-7crw------- root root 89, 9 1971-01-02 22:43 i2c-9-rw-r--r-- system system 1 1971-01-02 22:43 icd
-rw-r--r-- system system 1 2014-05-15 17:22 icdr
drwxr-xr-x root root 1971-01-02 22:43 inputcrw-rw-r-- system system 10, 63 1971-01-02 22:43 ion
crw-rw-rw- system system 242, 0 2014-05-17 09:02 kgsl-3d0
crw------- root root 1, 2 1971-01-02 22:43 kmem
crw------- root root 1, 11 1971-01-02 22:43 kmsg
drwxr-xr-x root root 1971-01-02 22:43 log
crw------- root root 10, 237 1971-01-02 22:43 loop-control
crw-rw---- system radio 10, 38 1971-01-02 22:43 mdm
crw-rw---- system camera 252, 0 1971-01-02 22:43 media0
crw-rw---- system camera 252, 1 1971-01-02 22:43 media1
crw-rw---- system camera 252, 2 1971-01-02 22:43 media2
crw------- root root 1, 1 1971-01-02 22:43 mem
drwx------ system system 1971-01-02 22:43 memcgrp
crw------- root root 271, 0 1971-01-02 22:43 mhl_dev
crwx------ system system 10, 10 2014-05-15 17:22 mobicore
crw-rw---- radio system 10, 9 2014-05-15 17:22 mobicore-user
crw-rw---- system audio 10, 48 1971-01-02 22:43 msm_aac
crw-rw---- system audio 10, 54 1971-01-02 22:43 msm_aac_in
crw-rw---- system audio 10, 55 1971-01-02 22:43 msm_acdb
crw-rw---- system audio 10, 44 1971-01-02 22:43 msm_amrnb
crw-r----- system audio 10, 51 1971-01-02 22:43 msm_amrnb_in
crw-rw---- system audio 10, 43 1971-01-02 22:43 msm_amrwb
crw------- root root 10, 39 1971-01-02 22:43 msm_amrwb_in
crw------- root root 10, 42 1971-01-02 22:43 msm_amrwbplus
drwxr-xr-x root root 1971-01-02 22:43 msm_camera
crw-rw---- system audio 10, 41 1971-01-02 22:43 msm_evrc
crw-rw---- system audio 10, 52 1971-01-02 22:43 msm_evrc_in
crw-rw---- system audio 10, 45 1971-01-02 22:43 msm_mp3
crw-rw---- system audio 10, 47 1971-01-02 22:43 msm_multi_aac
crw-rw---- system audio 10, 40 1971-01-02 22:43 msm_qcelp
crw-rw---- system audio 10, 53 1971-01-02 22:43 msm_qcelp_in
crw-rw-r-- system system 244, 0 1971-01-02 22:43 msm_rotator
crw-rw---- system audio 10, 46 1971-01-02 22:43 msm_rtac
crw------- root root 254, 0 1971-01-02 22:43 msm_sps
crw-rw---- system audio 248, 0 1971-01-02 22:43 msm_vidc_dec
crw-rw---- system audio 248, 1 1971-01-02 22:43 msm_vidc_dec_sec
crw-rw---- system audio 247, 0 1971-01-02 22:43 msm_vidc_enc
crw------- root root 247, 1 1971-01-02 22:43 msm_vidc_enc_sec
crw-rw---- system audio 249, 0 1971-01-02 22:43 msm_vidc_reg
crw-rw---- system audio 10, 50 1971-01-02 22:43 msm_wma
crw-rw---- system audio 10, 49 1971-01-02 22:43 msm_wmapro
crw------- root root 10, 13 1971-01-02 22:43 network_latency
crw------- root root 10, 12 1971-01-02 22:43 network_throughput
crw------- root root 10, 57 1971-01-02 22:43 nmea
crw-rw-rw- root root 1, 3 1971-01-02 22:43 null
drwxrwx--x shell shell 1971-01-02 22:43 pipescrw-rw---- radio vpn 108, 0 1971-01-02 22:43 ppp
crw------- root root 10, 1 1971-01-02 22:43 psauxcrw-rw-rw- root root 5, 2 2014-05-17 09:02 ptmx
drwxr-xr-x root root 1969-12-31 19:00 pts
crw-r----- radio radio 10, 60 1971-01-02 22:43 qmi0
crw-r----- radio radio 10, 59 1971-01-02 22:43 qmi1
crw-r----- radio radio 10, 58 1971-01-02 22:43 qmi2
crw-rw---- system drmrpc 241, 0 1971-01-02 22:43 qseecom
crw-rw-rw- root root 1, 8 1971-01-02 22:43 random
crw------- root root 10, 62 1971-01-02 22:43 rfkill
crw------- root root 238, 0 1971-01-02 22:43 rmi0
crw-r----- radio radio 10, 32 1971-01-02 22:43 rmnet_mux_ctrl
crw------- system system 253, 0 1971-01-02 22:43 rtc0
crw------- root root 10, 34 1971-01-02 22:43 sec_misc
crw------- root root 251, 1 1971-01-02 22:43 smd1
crw------- root root 251, 11 1971-01-02 22:43 smd11crw-rw---- bluetooth bluetooth 251, 2 1971-01-02 22:43 smd2
crw------- root root 251, 21 1971-01-02 22:43 smd21crw------- root root 251, 27 1971-01-02 22:43 smd27crw-rw---- bluetooth bluetooth 251, 3 1971-01-02 22:43 smd3
crw------- root root 251, 36 1971-01-02 22:43 smd36crw-rw---- system system 251, 4 1971-01-02 22:43 smd4
crw------- root root 251, 5 1971-01-02 22:43 smd5
crw------- root root 251, 6 1971-01-02 22:43 smd6
crw-rw---- bluetooth bluetooth 251, 7 1971-01-02 22:43 smd7
crw------- root root 10, 61 1971-01-02 22:43 smem_log
drwxr-xr-x root root 1971-01-02 22:43 snd
drwxr-xr-x root root 2014-05-15 17:23 socket
crw-rw---- system system 10, 16 1971-01-02 22:43 ssp_sensorhub
crw------- root root 10, 33 1971-01-02 22:43 tgt
crw-rw---- root shell 10, 11 1971-01-02 22:43 tspdrv
crw-rw-rw- root root 5, 0 1971-01-02 22:43 tty
crw-rw---- root system 4, 0 1971-01-02 22:43 tty0
crw------- root root 4, 1 1971-01-02 22:43 tty1
crw------- root root 4, 10 1971-01-02 22:43 tty10crw------- root root 4, 11 1971-01-02 22:43 tty11crw------- root root 4, 12 1971-01-02 22:43 tty12crw------- root root 4, 13 1971-01-02 22:43 tty13crw------- root root 4, 14 1971-01-02 22:43 tty14crw------- root root 4, 15 1971-01-02 22:43 tty15crw------- root root 4, 16 1971-01-02 22:43 tty16crw------- root root 4, 17 1971-01-02 22:43 tty17crw------- root root 4, 18 1971-01-02 22:43 tty18crw------- root root 4, 19 1971-01-02 22:43 tty19crw------- root root 4, 2 1971-01-02 22:43 tty2
crw------- root root 4, 20 1971-01-02 22:43 tty20crw------- root root 4, 21 1971-01-02 22:43 tty21crw------- root root 4, 22 1971-01-02 22:43 tty22crw------- root root 4, 23 1971-01-02 22:43 tty23crw------- root root 4, 24 1971-01-02 22:43 tty24crw------- root root 4, 25 1971-01-02 22:43 tty25crw------- root root 4, 26 1971-01-02 22:43 tty26crw------- root root 4, 27 1971-01-02 22:43 tty27crw------- root root 4, 28 1971-01-02 22:43 tty28crw------- root root 4, 29 1971-01-02 22:43 tty29crw------- root root 4, 3 1971-01-02 22:43 tty3
crw------- root root 4, 30 1971-01-02 22:43 tty30crw------- root root 4, 31 1971-01-02 22:43 tty31crw------- root root 4, 32 1971-01-02 22:43 tty32crw------- root root 4, 33 1971-01-02 22:43 tty33crw------- root root 4, 34 1971-01-02 22:43 tty34crw------- root root 4, 35 1971-01-02 22:43 tty35crw------- root root 4, 36 1971-01-02 22:43 tty36crw------- root root 4, 37 1971-01-02 22:43 tty37crw------- root root 4, 38 1971-01-02 22:43 tty38crw------- root root 4, 39 1971-01-02 22:43 tty39crw------- root root 4, 4 1971-01-02 22:43 tty4
crw------- root root 4, 40 1971-01-02 22:43 tty40crw------- root root 4, 41 1971-01-02 22:43 tty41crw------- root root 4, 42 1971-01-02 22:43 tty42crw------- root root 4, 43 1971-01-02 22:43 tty43crw------- root root 4, 44 1971-01-02 22:43 tty44crw------- root root 4, 45 1971-01-02 22:43 tty45crw------- root root 4, 46 1971-01-02 22:43 tty46crw------- root root 4, 47 1971-01-02 22:43 tty47crw------- root root 4, 48 1971-01-02 22:43 tty48crw------- root root 4, 49 1971-01-02 22:43 tty49crw------- root root 4, 5 1971-01-02 22:43 tty5
crw------- root root 4, 50 1971-01-02 22:43 tty50crw------- root root 4, 51 1971-01-02 22:43 tty51crw------- root root 4, 52 1971-01-02 22:43 tty52crw------- root root 4, 53 1971-01-02 22:43 tty53crw------- root root 4, 54 1971-01-02 22:43 tty54crw------- root root 4, 55 1971-01-02 22:43 tty55crw------- root root 4, 56 1971-01-02 22:43 tty56crw------- root root 4, 57 1971-01-02 22:43 tty57crw------- root root 4, 58 1971-01-02 22:43 tty58crw------- root root 4, 59 1971-01-02 22:43 tty59crw------- root root 4, 6 1971-01-02 22:43 tty6
crw------- root root 4, 60 1971-01-02 22:43 tty60crw------- root root 4, 61 1971-01-02 22:43 tty61crw------- root root 4, 62 1971-01-02 22:43 tty62crw------- root root 4, 63 1971-01-02 22:43 tty63crw------- root root 4, 7 1971-01-02 22:43 tty7
crw------- root root 4, 8 1971-01-02 22:43 tty8
crw------- root root 4, 9 1971-01-02 22:43 tty9
crw-rw---- bluetooth net_bt_stack 246, 0 1971-01-02 22:43 ttyHS0
crw------- root root 245, 0 2014-05-15 17:30 ttyHSL0
crw-rw---- system system 245, 1 1971-01-02 22:43 ttyHSL1
crw-rw---- system radio 188, 0 2014-05-15 17:23 ttyUSB0
crw-rw---- system vpn 10, 200 1971-01-02 22:43 tun
crw------- system system 240, 0 1971-01-02 22:43 tzic
crw-rw---- system net_bt_stack 10, 24 1971-01-02 22:43 uhid
crw-rw---- system net_bt_stack 10, 223 1971-01-02 22:43 uinput
crw-rw-rw- root root 1, 9 1971-01-02 22:43 urandom
drwxr-xr-x root root 2014-05-15 17:23 usb
crw-rw---- root usb 10, 27 1971-01-02 22:43 usb_accessory
crw-rw---- system system 10, 28 1971-01-02 22:43 usb_mtp_gadget
crw-rw---- system camera 81, 3 1971-01-02 22:43 v4l-subdev0
crw-rw---- system camera 81, 6 1971-01-02 22:43 v4l-subdev1
crw-rw---- system camera 81, 15 1971-01-02 22:43 v4l-subdev10
crw-rw---- system camera 81, 7 1971-01-02 22:43 v4l-subdev2
crw-rw---- system camera 81, 8 1971-01-02 22:43 v4l-subdev3
crw-rw---- system camera 81, 9 1971-01-02 22:43 v4l-subdev4
crw-rw---- system camera 81, 10 1971-01-02 22:43 v4l-subdev5
crw-rw---- system camera 81, 11 1971-01-02 22:43 v4l-subdev6
crw-rw---- system camera 81, 12 1971-01-02 22:43 v4l-subdev7
crw-rw---- system camera 81, 13 1971-01-02 22:43 v4l-subdev8
crw-rw---- system camera 81, 14 1971-01-02 22:43 v4l-subdev9
crw------- root root 7, 0 1971-01-02 22:43 vcs
crw------- root root 7, 1 1971-01-02 22:43 vcs1
crw------- root root 7, 128 1971-01-02 22:43 vcsa
crw------- root root 7, 129 1971-01-02 22:43 vcsa1crw-rw---- system camera 81, 1 1971-01-02 22:43 video0
crw-rw---- system camera 81, 2 1971-01-02 22:43 video1
crw-rw---- system camera 81, 0 1971-01-02 22:43 video100
crw-rw---- system camera 81, 4 1971-01-02 22:43 video2
crw-rw---- system camera 81, 5 1971-01-02 22:43 video3
crw-rw---- system camera 81, 16 1971-01-02 22:43 video38
crw-rw---- system camera 81, 17 1971-01-02 22:43 video39
crw-r--r-- root root 10, 15 1971-01-02 22:43 xt_qtaguid
crw-rw-rw- root root 1, 5 1971-01-02 22:43 zero
sh-3.2$
 

p012t

Member
May 13, 2014
9
0
Well the system apps are kept in the system partition. The settings related to the system are kept in the data partition. So very few things done day to day affect the system partition directly.

At least for me, I've had the same setup for almost 5 months as I never saw the reason to upgrade past 4.2.2. So having this happen to me twice in two weeks is worrisome.

The fact that I could get things restored by wiping /data points to some corrupted setting perhaps. I restored the apps from my nandroid and that worked fine for another week so I don't think it's a user app, but certainly possible.

OP, don't mean to hijack your thread but I think the situation is the same.

If you wish for a quick fix, backup your apps/sms/etc, wipe data, then restore the apps individually with titanium backup.

no problem. so your saying that a certain app caused this to happen ?
when you mean wipe, you mean reflash the rom ??
 

waylo

Senior Member
May 9, 2010
1,670
489
no problem. so your saying that a certain app caused this to happen ?
when you mean wipe, you mean reflash the rom ??

I'm certainly suspicious that an app may have caused this if somehow it didn't access or clear its GPS settings properly, but I don't have a great way of proving this. I'm not even sure how possible it is, for apps without root capability to alter how the system activates GPS.

I do have many apps with root approval, but I've had those for the longest time.

The only thing I do daily is update apps (and run them), so short of a hardware failure, I can't for the life of me think of any other reason. In other words, I don't tinker around with many rooted functions or the /system partition.

I thought it might have been a new version of Google Now/Search but I haven't been able to test that decisively.

When I wiped /data and restored all the apps, it worked just fine for another week without me rolling back any apps, so, a little frustrating in that respect.

If I'm right about something in the /data partition causing this mayhem, you don't have to reflash the ROM. Make sure your apps are backed up, and just wipe /data in your recovery. This clears out all your settings for the ROM, but all the apps/settings you chose in the AROMA installer will still be in the /system partition. When you reboot, it will be as if you are booting after a fresh install, mostly. Check and confirm that your GPS is now working, and then reinstall your apps.

Let me know if I'm on the right track if you decide to go this route.
 

bobolinko

Senior Member
Nov 5, 2010
338
64
Everett WA
I had this problem om Saturday and I was determined to find what in the heck caused the problem. I did not have any problem on Friday, and the GPS lock was making a lock in 3 sconds then... Saturday, nothing! I do remember updating Super Compass on Friday, but the phone worked all day! after that...

I reverted to nandroid back up I made a month ago and all was good, except I didn't have a helluva lot of stuff that was updated, and saved on the device (including and most importantly, all the GPS tweaks that made the GPS soooooo frickin good) since the update so I reloaded the current OS and started uninstalling all the stuff since a week ago. rebooted the phone, and all was good!

Then I loaded one-by-one the apps that were in the current system and as soon as I loaded the "Super Compass" app and tested the GPS for a few minutes, it bombed the GPS and totally would not work again.

I did notice it recently updated so I don't know which version caused the problem, but I do suspect the problem was set up intentionally, as the GPS works for a while, (even if the Super Compass App wasn't running) and then crapps out. Battery pull after 5 minutes and reinstalling and powering up always got the GPS back, but would again run for a few minutes, and then crapp out.

I uninstalled the Super Compasss and no problems, my GPS locks in 3 seconds, and all is good again.

FasterGPS and FasterFix are 2 apps that significantly decrease the gps lock on time, and also have allowed my accuracy down to 10 feet or less.

Agps injector is also an app that increases lock time speed and accuracy. Also if your wireless is left on during GPS navigation, that allows AGPS to combine with the GPS and increase the accuracy result quite a lot. Without AGPS insertion, I was sometimes getting 60+ feet accuracy, but withe the AGPS, it is almost always at 10 feet or less. The AGPS Insertion app also has a function of installing the insertion before the app of your choice runs and puts a new shortcut that does the job on the screen, If you want that. It adds a small graphic to the icon so that you know that it's auto inserting.... If you play with it you'll understand what I'm talking about (only on the paid version)

Hope this helps some of you out there to get the most out of your GPS on such a great device like ours, running "top shape"!

Good Luck and Aloha
 

waylo

Senior Member
May 9, 2010
1,670
489
I had this problem om Saturday and I was determined to find what in the heck caused the problem. I did not have any problem on Friday, and the GPS lock was making a lock in 3 sconds then... Saturday, nothing! I do remember updating Super Compass on Friday, but the phone worked all day! after that...

I reverted to nandroid back up I made a month ago and all was good, except I didn't have a helluva lot of stuff that was updated, and saved on the device (including and most importantly, all the GPS tweaks that made the GPS soooooo frickin good) since the update so I reloaded the current OS and started uninstalling all the stuff since a week ago. rebooted the phone, and all was good!

Then I loaded one-by-one the apps that were in the current system and as soon as I loaded the "Super Compass" app and tested the GPS for a few minutes, it bombed the GPS and totally would not work again.

I did notice it recently updated so I don't know which version caused the problem, but I do suspect the problem was set up intentionally, as the GPS works for a while, (even if the Super Compass App wasn't running) and then crapps out. Battery pull after 5 minutes and reinstalling and powering up always got the GPS back, but would again run for a few minutes, and then crapp out.

I uninstalled the Super Compasss and no problems, my GPS locks in 3 seconds, and all is good again.

FasterGPS and FasterFix are 2 apps that significantly decrease the gps lock on time, and also have allowed my accuracy down to 10 feet or less.

Agps injector is also an app that increases lock time speed and accuracy. Also if your wireless is left on during GPS navigation, that allows AGPS to combine with the GPS and increase the accuracy result quite a lot. Without AGPS insertion, I was sometimes getting 60+ feet accuracy, but withe the AGPS, it is almost always at 10 feet or less. The AGPS Insertion app also has a function of installing the insertion before the app of your choice runs and puts a new shortcut that does the job on the screen, If you want that. It adds a small graphic to the icon so that you know that it's auto inserting.... If you play with it you'll understand what I'm talking about (only on the paid version)

Hope this helps some of you out there to get the most out of your GPS on such a great device like ours, running "top shape"!

Good Luck and Aloha

Thank you for your contribution. Your problem sounds similar but very different too.

Did your GPS setting automatically turn off, and attempts to turn it back on result in a System UI crash?

The OP and I are having issues where it just simply will not turn on. It's not exactly as you had described, where it works for several minutes and then craps out. GPS pinpointing and accuracy is not the problem here.
 

bxferrari92

New member
Sep 29, 2008
1
0
I'm certainly suspicious that an app may have caused this if somehow it didn't access or clear its GPS settings properly, but I don't have a great way of proving this. I'm not even sure how possible it is, for apps without root capability to alter how the system activates GPS.

I do have many apps with root approval, but I've had those for the longest time.

The only thing I do daily is update apps (and run them), so short of a hardware failure, I can't for the life of me think of any other reason. In other words, I don't tinker around with many rooted functions or the /system partition.

I thought it might have been a new version of Google Now/Search but I haven't been able to test that decisively.

When I wiped /data and restored all the apps, it worked just fine for another week without me rolling back any apps, so, a little frustrating in that respect.

If I'm right about something in the /data partition causing this mayhem, you don't have to reflash the ROM. Make sure your apps are backed up, and just wipe /data in your recovery. This clears out all your settings for the ROM, but all the apps/settings you chose in the AROMA installer will still be in the /system partition. When you reboot, it will be as if you are booting after a fresh install, mostly. Check and confirm that your GPS is now working, and then reinstall your apps.

Let me know if I'm on the right track if you decide to go this route.


hey sorry for such a late reply. I finally got fed up of no gps and decided to wipe my data as well... so far my gps has been functioning normally. I guess it was a app that messed up the gps settings or something
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Try checking the logcat after it crashes.

    Sent from my Galaxy S4
    1
    Hey, I checked the logcat as you send and I narrowed it down to this, I think this is the error im not too sure
    its kind of hard to read

    05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

    05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

    05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

    05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

    05-16 11:26:03.925 27813 27813 E QSEECOMAPI: : Error::Failed to open /dev/qseecom device

    Do you have any idea if this is the issue and how do I fix this ?

    Thank you

    Just a guess, but try fixing permissions in recovery, or open terminal emulator and run
    Code:
     ls -l /dev