Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,733,899 Members 49,383 Now Online
XDA Developers Android and Mobile Development Forum

[Q] GPS issue / cannot turn on

Tip us?
 
p012t
Old
(Last edited by p012t; 13th May 2014 at 08:50 PM.) Reason: missing information
#1  
Junior Member - OP
Thanks Meter 0
Posts: 9
Join Date: May 2014
Default [Q] GPS issue / cannot turn on

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
 
Karakoram2
Old
#2  
Karakoram2's Avatar
Senior Member
Thanks Meter 111
Posts: 583
Join Date: May 2011
Could try reflashing your ROM or Odin to stock and start over.



Sent from my SGH-M919 using XDA Premium 4 mobile app
 
p012t
Old
#3  
Junior Member - OP
Thanks Meter 0
Posts: 9
Join Date: May 2014
Quote:
Originally Posted by Karakoram2 View Post
Could try reflashing your ROM or Odin to stock and start over.


Sent from my SGH-M919 using XDA Premium 4 mobile app
Im actually trying to avoid that. You have any other ideas? I guess it has to be a software bug of some sort.
the gps just stopped working out of nowhere.

Thanks
 
MultipleMonomials
Old
#4  
MultipleMonomials's Avatar
Senior Member
Thanks Meter 239
Posts: 713
Join Date: May 2012
Location: San Diego
Try checking the logcat after it crashes.

Sent from my Galaxy S4
Devices:
Galaxy S Fascinate (Hellybean 4.2.2)(retired)
Galaxy S4(Cyanogenmod)
Galaxy Tab 2 10.1(Cyanogenmod)

Having trouble with the Fascinate? Check out Droidstyle's awesome guide here.
Having trouble with the Galaxy Tab 2 10.1? Check out my guide here.
The Following User Says Thank You to MultipleMonomials For This Useful Post: [ Click to Expand ]
 
p012t
Old
#5  
Junior Member - OP
Thanks Meter 0
Posts: 9
Join Date: May 2014
Quote:
Originally Posted by MultipleMonomials View Post
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
Old
#6  
MultipleMonomials's Avatar
Senior Member
Thanks Meter 239
Posts: 713
Join Date: May 2012
Location: San Diego
Quote:
Originally Posted by p012t View Post
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
Devices:
Galaxy S Fascinate (Hellybean 4.2.2)(retired)
Galaxy S4(Cyanogenmod)
Galaxy Tab 2 10.1(Cyanogenmod)

Having trouble with the Fascinate? Check out Droidstyle's awesome guide here.
Having trouble with the Galaxy Tab 2 10.1? Check out my guide here.
The Following User Says Thank You to MultipleMonomials For This Useful Post: [ Click to Expand ]
 
p012t
Old
#7  
Junior Member - OP
Thanks Meter 0
Posts: 9
Join Date: May 2014
Quote:
Originally Posted by MultipleMonomials View Post
Just a guess, but try fixing permissions in recovery, or open terminal emulator and run
Code:
 ls -l /dev
I already have wiped the cache and dalik cache as well as fixing permission from recovery. Nothing worked
 
Skipjacks
Old
#8  
Skipjacks's Avatar
Recognized Contributor
Thanks Meter 3786
Posts: 4,810
Join Date: Nov 2011
Location: Baltimore
Quote:
Originally Posted by p012t View Post
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.
Do you want insanely better battery drain when your phone is idle? Check out this thread!
Have a question about the T Mobile Samsung Galaxy S4? Click here for the Help Thread!
 
MultipleMonomials
Old
#9  
MultipleMonomials's Avatar
Senior Member
Thanks Meter 239
Posts: 713
Join Date: May 2012
Location: 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
Devices:
Galaxy S Fascinate (Hellybean 4.2.2)(retired)
Galaxy S4(Cyanogenmod)
Galaxy Tab 2 10.1(Cyanogenmod)

Having trouble with the Fascinate? Check out Droidstyle's awesome guide here.
Having trouble with the Galaxy Tab 2 10.1? Check out my guide here.
 
p012t
Old
#10  
Junior Member - OP
Thanks Meter 0
Posts: 9
Join Date: May 2014
Quote:
Originally Posted by MultipleMonomials View Post
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
Thread Tools
Display Modes


XDA PORTAL POSTS

TWRP Now Available for the LG G Watch and Samsung Gear Live

Over the past week or so, we’ve talkedquite a bit about the first … more

Slate Calendar Helps You Organize Your Life

Without calendars in some form or another, most of our lives would be utter chaos. Unless you are … more

Shane Francis to Talk Android, Robotics, and Vision at XDA:DevCon 2014

Our international xda:devcon 14in Manchester, UK on the weekend of … more

LG G Watch Tool is a Toolkit all Owners Need

The LG G Watch is one of the first two devices hitting the market rocking the highly anticipated … more