Develop Bugs

Splash top 2 brick?

Guys -
I installed the Splashtop 2 on my Nexus 7 running AOKP and Trinity Krenel, and it bricked my device twice. Just running the software and suddenly it crashes, then no buttons work. Then the screen starts to flash and it shuts down. I was unable to get into recovery. I need to push a new recovery to get it running back again. This has happen twice today. Anyone else having this issue?

Its bricked?
So you put it in the trash or sent it back to ASUS?

I'm going to go out on a limb here and say this is not related to splashtop.

I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.

Hemidroids said:
Its bricked?
So you put it in the trash or sent it back to ASUS?
Click to expand...
Click to collapse
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium

tdrussell said:
I'm going to go out on a limb here and say this is not related to splashtop.
Click to expand...
Click to collapse
I would see why you would say this....however this happened twice when using the new splashtop. My set up or system has not changed in days. Only thing that changed was me installing splashtop. Once I stopped using it and went back to the old one. No issues. Someone else n the market review described the same thing to a t.
Sent from my Nexus 7 using xda premium

Installed HD2 this morning and same problem, freeze when changing from sharp to smooth. Hard reset twice, to get it to boot now the speaker sounds like its blown, was streaming some video from the PC. Running EOS + stock kernel.
Something isn't right with it that's for sure, avoid for now is my advice.
Sent from my Nexus S using xda premium

Knether said:
No.. I know how to get out of a jam. The device would not boot afterward the system froze, then rebooting I got stuck at Google screen. Then it wouldn't get into recovery from bootloader I had to flash a new recovery and flash back up. Sounds like it was bricked at the time to me.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Oh......so its not a brick. Might want to change the title.

Splashtop also froze my Nexus 7, fortunately hasn't knackered the speaker or anything. I was going to blame my undervolt though...

sensory said:
I had an issue using Splashtop 2 today that freaked me out a little. Going from Sharp to Smooth froze my N7 and when it booted back up, which took longer than usual, the speaker made a faint but distinct "hissing" noise then a louder "tap"
Everything is working again but that's never happened before. Not sure I liked Splashtop 2 enough to bother with it after that.
Click to expand...
Click to collapse
I had this same thing happen to me. Everything froze up then my Nexus rebooted itself. Other than that the app runs pretty damn good for me. No rooting or roms on mine.

PA 1.97a, Trinity Kernel @ 1640 (ondemand/deadline), Nova Launcher, Dark Jelly Theme.
Daily use out of Splashtop with absolutely no issue. It's one of the things I like best about this tablet.

my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app

xxmonsterx said:
my only negative view towards the nexus 7 is the influx of noobs that dont know what brick means. i have a g1 with a bad spl flash. that is a brick. you sir just need to flash a factory img. your not bricked.
Click to expand...
Click to collapse
Influx of noobs? I've been around XDA a bit longer than you. I am deeply sorry forum wordsmith for using the word brick not in the fashion you so desired.
Moving on:
I just wanted to get this word out there and just making sure its not my device. I spoke with Splash top and "they're on it." So we'll see :highfive:

Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.

xxmonsterx said:
Sorry good sir. I do suppose that was a bit rude. I may have taken out my dissapointment with what xda is becoming on you. My bad bud. I'm not here to compare the d!cks bro. I just can't stand seeing all these help I'm bricked threads.
Click to expand...
Click to collapse
No harm no foul. I don't hold grudges. Conflict resolution at its best. Thanks for that, means a lot and restores my faith in people. :laugh:

Harry GT-S5830 said:
The only reason he can't access recovery is because of a bug in boot loader 3.34 so its even less of a brick and more of a don't OV and OC
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?

Knether said:
What is this bug you speak of?
Also, OC and OV is causing issues? Sorry If i dont know about this just yet, is there a thread that speaks about this?
Click to expand...
Click to collapse
Try acessing recovery through boot loader on a healthy N7 and not plugged in, you will find that you can't access recovery. There's quite a few "Q" threads saying that I OC to 1600 and overvolted by 50MHz across the board, and my nexus fried? Why is this??
Sent from a Nexus 7 using my fingers

I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.

qrees said:
I've got the same problem with Splashtop and Nexus 7. Original ROM, no root. After switching smooth<>shart Nexus just reboots. Also there seems to be nothing interesting in logcat.
Click to expand...
Click to collapse
I seems to be fixed after todays update, but it's still strage that single app could crash the whole device.

Phone keeps resetting randomly

Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.

okay, i'm not a dumbass (maybe). Phone keeps resetting on its own randomly still but less frequently after I overclocked.

How is your battery condition? Like how old is it? Do you have and tweaks (kobridge or phakker scripts)
Cpusleep app? And you said it happens on a few ROMs, I would say it maybe a battery or hardware issue. Also, do you check the MD5 sums before you flash the different ROMs?
Sent from my SPH-D710 using XDA

Battery condition is good, I actually have two oem batteries that I use daily and swap them when one dies.
I'm not running any tweaks currently, but when I flashed the roms recently its been through a nandroid backup of my previous working rom. But I'll try a clean install without a backup and see if that works. Thanks
Sent from my SPH-D710 using xda premium

Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium

Subiegsr said:
Okay, just did a fresh clean install from recovery. The phone still resets, I've noticed if it's plugged in to a charger though instead of resetting it will just turn off and show me the battery charging screen.
Also, how do you check the MD5 sums? I always thought the phone recovery automatically checks this before it flashes a rom?
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Are you using a stock battery charger? Is the charging cable damaged or loose? I had an issue with an after market charger making my phone freeze up before.
Not to my knowladge, but it never hurts to check it. I use md5sum app.
Sent from my SPH-D710 using XDA

Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!

What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2

Subiegsr said:
Okay, I flashed a totally different ROM and it seemed to have solved the problem for now. Most likely it was a ROM issue, which is kind of weird since it was using the same rom before without any issues, even when I did a recovery of it. Oh well, maybe it was the right combination of apps and crap. But so far right now, everything is good. Thanks for the help g_ding84!
Click to expand...
Click to collapse
No problem, just wanna find out the root cause of the reboots.
Sent from my SPH-D710 using XDA
---------- Post added at 11:29 PM ---------- Previous post was at 11:26 PM ----------
cp320703 said:
What were you using to under/overclock? Setcpu specifically has been known to cause the exact issue you were having, namely random reboots, however I would not be shocked to find other overclocking utilities that could cause the same problem. Regardless I'd be willing to bet that whatever you were were using to adjust the clock speeds was the source of the issue as opposed to the ROM.
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
You may be right on the money with that. It could be causing script confliction. Between the ROM and the CPU app. But I do know that cpu app scripts will override the ROMs cpu scripts, but not all the time.
Sent from my SPH-D710 using XDA

Subiegsr said:
Don't know what happened, my phone has been going strong with a the SuperGalaxy rom 1.7 with no problems. I recently updated to 1.8 and it ran fine for the past two days with no problems. Then after leaving the phone on the charger at work yesterday, the phone kept resetting randomly. I unplugged it, hard reset, flashed a different rom, everything, and it still keep resetting randomly. Not sure what the problem is, any suggestions?
Edit: I'm a dumbass, realized my cpu was under clocked to 800mhz, running smooth at 1400mhz now.
Click to expand...
Click to collapse
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA

g_ding84 said:
I would bring your battery in sprint. You may need a new one.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I have 3 OEM and 4 extended they all do the same thing.
Sent from my SPH-D710 using xda app-developers app

You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817

tysonrj said:
You might try this thread...
http://forum.xda-developers.com/showthread.php?t=1916817
Click to expand...
Click to collapse
Thank you very much. I didnt know this was an issue with the phone.

FuMMoD said:
This has been happening to me all day today even after Changing roms and removing every tweak related app. It even reboots inside the recovery menu wtf
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Does it reboot in download mode? If not..I would odin to stock and go from there see if that fixes things.

Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).

Subiegsr said:
Update: still resetting. :crying:
Today its been resetting probably about once every few minutes to ten minutes. It's stupid, like the battery will say 60% and when it reboots on its own, the battery will be at like 10%. No idea what the issue may be, but I might try to see if it will reboot in download mode as some of you suggest and maybe try to flash a stock rom. It seems that when it does go in reboot crackhead mode it will do it even in recovery.
The power button will not be as functional during the crackhead reboot mode as well. I'll press it and nothing will happen, but the screen will come on itself (not sure if this is a delay or just the screen coming on by itself lol).
I'm not too worried about exchanging it as of now, since I'm in the market for a new phone, but would like to fix this issue so I can sell the phone; if not I'll just do the trade in thing with Sprint (even though I won't get as much).
Click to expand...
Click to collapse
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.

milky1112 said:
Trade in is roughly $80 bucks (i'm looking to do that with mine this weekend hopefully for the S3) Sorry your having issues.. Mine has done it once ina great while.. but nothing crazy. Good luck on new phone! (I'm a craigslist junky so i'll shop on there for temp replacements lol) Got my Touch for $50 which was an upgrade from my OG Epic.
Click to expand...
Click to collapse
Thanks man. It started doing it today and I took out the SD card and it hasn't done it since. So maybe it was the SD card this whole time?
Hopefully it is.
Sent from my SPH-D710 using xda premium

Kernels for cymod10.1

Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium

cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Look in the CM 10.1 thread I pointed out which are updated and compatible with the latest.

I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.

Aerowinder said:
I guarantee you this: if you have battery problems with the stock CM kernel, you will also have battery problems with another one.
Click to expand...
Click to collapse
Might be the case, but the flicker is resolved for me flashing a 3rd party kernel. I was getting it really bad, like screen would go black and come back 10 times with in 2 seconds so it was nasty. Not sure why it was happening on stock and not custom...

I'm not having any battery problem. Just screen flickering and random reboots. Any fix?
Sent from my SGH-T999 using xda premium

Did you not read what I posted? http://forum.xda-developers.com/showpost.php?p=40525936&postcount=11050

Sorry. I didn't refresh the page so I didn't see what you said. But I would try to flash a new kernel now. Thx for the help.
Sent from my SGH-T999 using xda premium

cyberianrazr54 said:
Just flashed the nightly 4/20 and was having few problem.
1. Screen flicker alot and random times
2. Phone randomly reboot often. Every 45min or so
Wandering if anyone is having any of this problem? How did you fix it?
Heard that it was the cymod kerbal problem and if you flash another one. It will solve the issue. True?
What kernel are you using?
What kernel is compatible with 4/20 cymod 10.1?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:

CodyRst said:
My Story:
Did a clean flash (as ALWAYS), and I have none of those problems. No flickers, no reboots, seems solid here, staying with stock kernel.
:good:
Click to expand...
Click to collapse
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.

mt3g said:
Some aren't and some are. Was like that the old days for the most part. I every single flash unless told not to, clean flash. I wipe my internal and external almost once a week, to avoid issues as well. Just how it is for some of our phones unfortunately.
Click to expand...
Click to collapse
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.

CodyRst said:
Oh ok, gotcha. Kind of weird that it would happen to some and not others...
I suppose i lucked out.
Click to expand...
Click to collapse
Almost all 4.2.2 roms that have the latest merges have reports of it happening. Not alarmed at all, it may end up happening to you soon enough lol.

Would lowering the maximum CPU frequency to 1459 MHz save battery?
Sent from my SGH-T999 using xda premium

You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.

Aerowinder said:
You are still ignoring the actual problem. And until you fix that, your battery life will suck. I can't be any more direct about this. I'm sure people would be happy to help you, if you would ask for it.
Click to expand...
Click to collapse
I'm not having problem with battery. I just want to save more so it can last long.
And it seem like battery life on cymod10.1 with katoon kernel for me is draining pretty fast compare to stock cymod 10.1 and stock kernal
Sent from my SGH-T999 using xda premium

Phantom touches. Never had them before

My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk

dantegl36 said:
I had the same experience the other day. Currently running
Latest version of Clean Rom with ElementalX kernel. After I was finally able to reboot, all was well.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.

littleromeo said:
My 16GB flo was working fine from the beginning. Always kept it up to date with android releases. Never had an issue. Just today while swyping noticed some weird behavior.So, I tested with a multi touch tester. There were some fake touches recorded. It didn't even allow me to reboot. Later with some effort I managed though. After reboot, it works fine. I'm scared cause I bought that in US and I doubt the so called international warranty will be honored in India.Has this occurred to anyone else? What shall I do if it happens again? Is there some fix for this?
Click to expand...
Click to collapse
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
littleromeo said:
I'm running stock+xposed.
Testing with multi touch app seemed to have made it worse for me, even prevented me shutting it down. Hope it doesn't come back.
Click to expand...
Click to collapse

Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks, will do if it starts again.
Abel669 said:
Take a look at this thread, I had the same problem and after flashing boot-ts10.IMG it was fixed.
The flash persists between any new ROM flashing
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Aerowinder said:
If an RMA is not an option, try Abel's solution. It boils down to bad hardware and no quality control. I had to RMA my first one for the exact same reason. Second one is fine.
If you do some googling, you will see that thousands of people have had this problem. Any definitive word from Google or Asus? You wish. They will never admit they made a mistake.
Click to expand...
Click to collapse
Yes I read about them but this is weird cause a reboot solved the problem.

Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app

mister2quick said:
Had this issue start yesterday. Running Sinless 3.2.2 on stock kernel. I've noticed it only start since installing Xposed but that could be coincidence. Reboot fixed it but woke up to it again today...
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
The one I had (before I sent it back to Google), would only do it after it had been started for a while. Reboot would make it go away for a while, but it always came back.
Not related to Xposed.

GPS lock issues anyone?

So just curious...I know there are folks out there with GPS lock issues and the number of ways to fix it... But they don't exactly pertain to me. Not sure if anyone else sees exactly this so here goes:
I can't get a lock on stock roms. If I do it's after waiting upwards of thirty minutes. When it locks it will get lost 2 minutes later. Without fail. This is any ROM based on stock.
AOSP on the other hand... Instant lock. Works without issues. Can drive for hours and not worry even cross country. So.....huh?!
I have used a GPS fix app to no avail and can't assume hardware since it does work on aosp... Any others seeing the same as me? It's killing me because I do want to use stock for other features of my phone but can't because of the constant need to use GPS.
Sent from my LG-LS980 using Tapatalk

Well I recently had the opposite problem. What I did was copy the gps.conf file from my stock setup and saved it in a folder. Then when I went to AOSP, I replaced that gps.conf with the one I saved earlier. Just set permissions to RW-R-R and reboot. Worked like a charm for me.
Obviously your situation is the exact opposite. But I don't think it can hurt to give it a shot.

I've actually done that lol. It doesn't change a thing with stock crazy enough. It's just one of those weird things that forces me to stay aosp and miss out on features I guess.
Sent from my LG-LS980 using Tapatalk

Man, that's weird then. Did you try a tot back to stock? Just to see if it helps?
Sent from my iPad using Tapatalk

KB112 said:
Man, that's weird then. Did you try a tot back to stock? Just to see if it helps?
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
I have indeed! It's just not meant to be lol
Sent from my LG-LS980 using Tapatalk

Try this
MeestaAytch said:
So just curious...I know there are folks out there with GPS lock issues and the number of ways to fix it... But they don't exactly pertain to me. Not sure if anyone else sees exactly this so here goes:
I can't get a lock on stock roms. If I do it's after waiting upwards of thirty minutes. When it locks it will get lost 2 minutes later. Without fail. This is any ROM based on stock.
AOSP on the other hand... Instant lock. Works without issues. Can drive for hours and not worry even cross country. So.....huh?!
I have used a GPS fix app to no avail and can't assume hardware since it does work on aosp... Any others seeing the same as me? It's killing me because I do want to use stock for other features of my phone but can't because of the constant need to use GPS.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
Had the issue on stock 4.2.2 . I updated it to 4.4.2 and now it locks instantly.
Then I tried cloudystock rom and now its better.

MeestaAytch said:
I have indeed! It's just not meant to be lol
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
That's weird bro. Sorry, I'm out of ideas though. Lol

I know this is an old thread but I found this app to fix my gps problems. Yes I have tried all of the ones we usually go to.
Try this one. It locks and keeps it locked on.
https://play.google.com/store/apps/details?id=com.silentlexx.gpslock