Database Users

GPS Woes

Having issues with GPS working. IT is not even seeing any sats. I have my old GNEX and that is working great, no issues. I used GPS Status to reset/download the GPS data and no luck. I tried the latest CM build and an old CM build...no luck. I tried a different 4.3.1 ROM all together, no luck. I would try a 4.2.2 but GOO has been down all damn day
Anyway, any one else having issues with GPS? Hope GOO is back up soon because if this is a phone defect, then I need to flash back to stock. Wish I would of tested GPS out of the box, but I didnt even think to do so.
thanks

techbeck said:
Having issues with GPS working. IT is not even seeing any sats. I have my old GNEX and that is working great, no issues. I used GPS Status to reset/download the GPS data and no luck. I tried the latest CM build and an old CM build...no luck. I tried a different 4.3.1 ROM all together, no luck. I would try a 4.2.2 but GOO has been down all damn day
Anyway, any one else having issues with GPS? Hope GOO is back up soon because if this is a phone defect, then I need to flash back to stock. Wish I would of tested GPS out of the box, but I didnt even think to do so.
thanks
Click to expand...
Click to collapse
Happend to me also, some rom u flashed used different gps regions.
EASY SOLUTION: Download android tweaker app from play store and set your country and region with it.
(= BeanStalk LGG2 =)

moonjak said:
Happend to me also, some rom u flashed used different gps regions.
EASY SOLUTION: Download android tweaker app from play store and set your country and region with it.
(= BeanStalk LGG2 =)
Click to expand...
Click to collapse
Tried this....still doesnt work. Any more ideas?

techbeck said:
Tried this....still doesnt work. Any more ideas?
Click to expand...
Click to collapse
If you are on stock do gps calibration inside hidden menu.
(= BeanStalk LGG2 =)

moonjak said:
If you are on stock do gps calibration inside hidden menu.
(= BeanStalk LGG2 =)
Click to expand...
Click to collapse
I am on the latest CM nightly build. Cannot go back to stock. All the links do DL stock roms are down because of GOO

THis is what I did to get GPS working....
1) Flashed CleanROM 4.2.2 and established a lock
2) Factory rest in recovery and applied CM 10.2 M1
GPS now works fine. Before I was restoring a CM backup but I had to flash the original CM ROM in order to get GPS working.

I am on stock rom, and have same issue. I began to think that this is a hardware problem. What type your g2? Mine is d802b.
There is another method to download stock rom, have you tried it?

htcm7 said:
I am on stock rom, and have same issue. I began to think that this is a hardware problem. What type your g2? Mine is d802b.
There is another method to download stock rom, have you tried it?
Click to expand...
Click to collapse
Stock and 4.2.2 ROMS are fine. It is a known issue going from stock to CM. Some G2 phones do have hardware problems tho.

No satellite fix on any kitkat rom. Why?

I tried "every" custom kitkat rom and I never got a satellite fix. It works fine on stock and stock based jelly bean roms. I know that some others have the same issue. I'm on an 802. If you had the same issue and actually solved it please let me know. If you still have the issue, let's find out what we've got in common to find a solution.

android404 said:
I tried "every" custom kitkat rom and I never got a satellite fix. It works fine on stock and stock based jelly bean roms. I know that some others have the same issue. I'm on an 802. If you had the same issue and actually solved it please let me know. If you still have the issue, let's find out what we've got in common to find a solution.
Click to expand...
Click to collapse
Have you tried resetting the gps A-Data? There is a couple of apps in playstore witch can do this!
Do you have Tele"hor" or Netcom?

Dirtyzecret said:
Have you tried resetting the gps A-Data? There is a couple of apps in playstore witch can do this!
Do you have Tele"hor" or Netcom?
Click to expand...
Click to collapse
Yes, I have. And my carrier shouldn't play a role when it comes to getting a satellite fix. Takk uansett.

First time it can take several minutes, just be patient and on an open location
Sent from my LG-D802 using Tapatalk

darkobas said:
First time it can take several minutes, just be patient and on an open location
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
I see dozens of satellites immediately but they never lock. Not after waiting for hours unfortunately.

You need to do a nandroid, wipe and install a stock based rom, get a gps lock, and then wipe and restore your backup. That's what I ended up doing (also installed the gps fix zip under stock because I still wasn't getting a lock), and it seems to still be working a few days later.
Sent from my LG-VS980 using Tapatalk

I had to do the same steps. Worked for me as well.

I waited half a year with starting this thread, hours later, @vertigo uploads a build of omni rom which has the issue fixed. Hooray!

Random reboot with lollipop 5.1

I installed loillipop 5.1, from scratch using the factory image. All went smooth and the performance was much better than with 5.0.2 (which was my previous version), but I have random reboots unless I stay connected to the wall. This can be easily reproduced by putting the tablet to sleep (i.e., I pressing power button). Immediately my nexus reboots (99% of times).
I tried everything possible. Factory reset. Reistalled after formatting every possible partition. Reistalled starting from scratch without using my google backups. Nothing helps.
The only solution was to come back to 5.0.2 (again through the factory images, flashing and formatting everything).
Last test I am going to do is to use the OTA to go from 5.0.2 to 5.1 but I do not have much hope.
Anyone else experiencing similar problems?
It looks like an hardware issue put in evidence by the new kernel that is part of 5.1, but it could eb enything else.

Greetings.
Have you tried using any other kernel, eg. franco kernel?

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Thanks for the suggestion, I didn't know Franco had released a version of his kernel for 5.1. I tried latest M-Kernel but it is not working with 5.1. Now I am sideloading the OTA from a stable 5..0.2, just to see if going to 5.1 using OTA helps. Will report if I succeed and in case I didn't will try with FK (and report).
Meanwhile, any other suggestion is welcome

Fobos531 said:
Greetings.
Have you tried using any other kernel, eg. franco kernel?
Click to expand...
Click to collapse
Current situation after some more tests:
5.0.2 from factory image (full wipe): works
5.0.2 -> 5.1 via OTA: reboot each time goes to sleep (unless wall powered or attached to PC USB)
5.1 from factory image (full wipe): same as above
rastapop 5.1 (full wipe): same as above
5.1 + franco kernel R82: same as above
I would try to increase CPU voltage: any suggestion how to do? Which kernel to use? Which app to adjust voltages? I am going to try with franco kernel and trickstermod (which I already bought) but I am not sure this combination will allow me to adjust voltages.
EDIT: no way to adjust voltages with FK for 5.1. Reverting back to 5.0.2 and waiting someone gives suggestions or has similar issues (or releases new kernels)

Sideload 5.1, same issue. Even worse than 5.0.2.
Sent from my Nexus 7 using XDA Free mobile app

killerfrank said:
Sideload 5.1, same issue. Even worse than 5.0.2.
Click to expand...
Click to collapse
Even in your case the device reboots just after entering sleep mode? Please confirm, I thought I was the only one, but if this happens to others then it must be a software issue, not hardware.

This does not happen at all to me(using stock 5.1 with Franco Kernel).

This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.

_Hobbz said:
This is indeed happening to me as well with the factory 5.1 image. Also thought Franco Kernel could possibly be a solution but didn't work. I had F2FS previously but reverted to install stock 5.1.
Click to expand...
Click to collapse
It looks like a mixed hw/sw problem. It is indeed clear that 5.1 works on most N7, either being installed from factory images or after an OTA upgrade, but for some of us it results in rebooting when the machine goes to sleep.
I attached last_kmsg (/proc/last_kmsg) just after the problem manifested. This is exactly what happens every time I put the device to sleep (pressing the power button or leaving it alone for a couple of minutes) and it repeats always the same (with the same kmsg).
Anyone knows how to extract other information that could be useful to isolate the source of the problem? Notice that I cannot do a catlog since the device doesn't go to sleep if it is connected to a PC (so I cannot recreate the problem).

Your battery is dying, I've been getting the same problem until I replaced the battery today.

richarddwyer10 said:
Your battery is dying, I've been getting the same problem until I replaced the battery today.
Click to expand...
Click to collapse
A hardware problem related with the power unit of the device was also my first hypothesis, but under 5.0.2 i everything works perfectly and the battery has the original duration. Under 5.1 also everything works... until the device goes to sleep. Only then it reboots.
Was this the behavior in your case?

I've been getting the same issues on my N7 since updating.

regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....

ondoy1943 said:
regret to disappoint you people, but i have not a single reboot in my nexus 7 since doing a clean install from cm12. two days being unrooted, no reboots; now running three days rooted, still no reboot. could be due to the clean install i did. lol.....
Click to expand...
Click to collapse
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.

gianpaoloc said:
I also made a clean install of 5.1 using the factory image and formatting everything (from system to data and cache). Still I have the reboots. I come back to 5.0.2 (same procedure: clean install from factory image) and had no reboots in four days of use. Clean install of rastapop (5.1 based) or 5.0.2 -> 5.1 via OTA resulted in the same situation: The device reboots as soon as it goes to sleep.
I know several users installed 5.1 and have no issues, this is why I think this is a hardware problem put in evidence from the new software.
I hope someone find a way to deliver a 5.1 version that do not present the problem (I like how smoother 5.1 is w.r.t. 5.0.2). Perhaps a new kernel or a new rom as a whole.
Click to expand...
Click to collapse
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.

_Hobbz said:
I've seen other people reporting the same issue on the nexus help forums too so hopefully Google will be looking in to this.
Click to expand...
Click to collapse
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks

I've given up on LP for the N7. I've gone back to KK. Stability is awesome, performance is great. LP was a disaster on the N7. Performance issues, lock ups, etc. No matter how many times I clean installed it, etc, it just wasn't good.
I'm now officially calling it Lollipoop (at least for the 2012 N7). But, it is an old device. I'm still waiting to see how it turns out on my LG G3 phone. I'm sticking with KK on that phone as well for now until I know for sure it runs well on it.
Stability over bleeding edge.

Hi
JFYI, I have just updated my 2 sons' N7 2012 (coming from Omnirom) to Lollipop 5.1 (with Nexus Root Toolkit v2.0.4, meaning following the same procedure)
- 1 of them fine
- 2nd one with the issue reported here; which is why I'm on this thread now
updated kernel to franco r82
the issue remains...
will keep checking this thread
thansk
beng

gianpaoloc said:
Sorry, which forums do you exactly mean? Something here on XDA or something managed by Google directly? If you could forward us to the right place we could add our report. The more we are the easier it is that Google takes the issue into consideration (I hope
Thanks
Click to expand...
Click to collapse
So I can't post links yet because of my low number of forum posts but if you google 'nexus help after update to 5.1, it won't wake up after in sleep mode, please help' then it should be the first result that shows up.
Things were running fairly well for me with the slimkat 5.0.2 rom on F2FS so I'll likely switch back to that while this gets sorted out.

I've had my n7 for 2 years now, flashed all kinds of custom Roms, bricked it, fixed it, encrypted it, unencrypted it several times, and It has never ran as slow as it did on lollipop. I tried, 5.0, 5.0.2, and 5.1 I even reset kk to stock and let the ota's do the job and no matter what, LP is still not usable in my opinion. I feel sorry for the people that take the ota and do not know how to revert back to kk.
Sent from my Nexus 7 using Tapatalk

PACrom Beta 3 signal issues

I see others have signal issues with their Moto X Play on PAC. Does anyone actually know how to overcome this? When I first start the rom and start setting it up (when you sign in with google account etc) I have a signal... Then it drops out and stays out, even after a reboot.
Tried with wifi on and wifi off, wifi off rebooted etc..

Seems to be if you first flash a rom for xt1563 then it should work. I'm guessing you have xt1562 like the others with this issue.
Sent from my XT1562 using Tapatalk

I can confirm to any one using the XT1562 and has the loss of signal like I did, if you flash all the way back to stock using the XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12, then reflash twrp, then reflash your custom rom of choice, gapps, set up etc.. It's then ok.
All is now working perfect and has been for 24 hours + using the Cyanogenmod rom and battery life seems pretty darn decent!

Thanks @ephumuris ... Only just seen your reply, but my above method worked perfectly, thanks for your reply, I have added a thanks on your post

Google Play Services keeps FC

I couldn't be the only one with this issue. I've tried stock Nougat, rooted and unrooted. I've also tried Substratum latest version, Nougat. No matter what I get a FC by Google Play Services every few minutes. Tried clearing cache and data for Play Services, it seemed to help for some time then the problem came right back. This happened on my 5X which I'm selling now, as well as my 6P. Anybody else having this issue?
Until it is cleared up I'm sticking with 6.0.1.

If you don't have the latest version of Play Services you can try updating to the newest version. Check your installed version against the newest one on APK Mirror.
Sent from my Nexus 6P using XDA Labs

Getting FC on 6.0.1 now too. Got the appropriate Play Services from APK Mirror but no improvement. Enabled all permissions for it. Only thing I can think of now is installing apps one at a time until I start getting FC
Sent from my Nexus 6P using Tapatalk

Hello all! I have the same problem on my Nexus 6P brand new...
Play Services stops all time, i cannot download or update a thing from play store, i cannot communicate with google servers (only some times)
Downloads some times gives me error 960...
Keyboard also crashes a lot
I've tried: Flashing different stock roms, flashed pure nexus custom rom... also tried bunch of different gapps packs... made an nandroid backup from another nexus 6p working and put it on mine... etc.. nothing happens... there is also a tricky thing on wifi connections... i have to wait much too long for it recognizes the internet connetion (it connets fine at the network).. tried in 4 different houses, and with 3 different sims...
Anyone has a clue here? im done reading and trying.
Thanks in advance!

Make sure you guys are using the correct vendor img, that will cause alot of problems if is incorrect

StarRavier said:
Make sure you guys are using the correct vendor img, that will cause alot of problems if is incorrect
Click to expand...
Click to collapse
Thanks man, in kinda noob doing all these. How do i know whats my right vendor img?

Wysh said:
Thanks man, in kinda noob doing all these. How do i know whats my right vendor img?
Click to expand...
Click to collapse
Check your rom, under Settings > About Phone, verify your build number for example NBD91K or NBD90X for example. Most custom Rom's link the vendor img in the post somewhere. If your familiar with flashing then you shouldn't have a problem. If not use, skipsoft toolkit to help you root/flash or anything else android.

sketron13 said:
I couldn't be the only one with this issue. I've tried stock Nougat, rooted and unrooted. I've also tried Substratum latest version, Nougat. No matter what I get a FC by Google Play Services every few minutes. Tried clearing cache and data for Play Services, it seemed to help for some time then the problem came right back. This happened on my 5X which I'm selling now, as well as my 6P. Anybody else having this issue?
Until it is cleared up I'm sticking with 6.0.1.
Click to expand...
Click to collapse
Thanks! Ive just checked and i used the right vendor for pure nexus rom.
Thats not the problem.. In stock also i have this problem.
I have no more clue