CM12 Official Nightly Lollipop GPS Not working. - Galaxy Note II Q&A, Help & Troubleshooting

I am running the latest nightly from https://download.cyanogenmod.org/?device=t0lte
I have TWRP 2.8.5.0 installed as my recovery.
In order to test your GPS you need to change the following setting. (Otherwise clever stuff happens and your location is guessed from wifi/cell tower locations)
Menu==>Settings==>Location==>Mode==>Device Only
My problem is that none of the nightlies seem to have a working GPS. This can be seen by installing one of the many GPS Test Apps (GPS Test, GPS Status& Toolbox), they will never get a fix.
Is there any known fix for this?

I faced the same problem with you,it seems lost some api about GPS.
But I don't know how to fix it.
I hope one day CM team can fix it as fast as possible

So I havent found anything yet but it seems that some of the unofficial CM12 ROMs have got working GPS (Device Only)
http://forum.xda-developers.com/galaxy-note-2/development-n7105/rom-unofficial-build-linaro-t2997775
I have no clue how they have done it though.

Fixed the GPS by applying the ROM fix in this thread
http://forum.xda-developers.com/showpost.php?p=57640318&postcount=32
Sent from my iPad using Tapatalk HD

GPS Fix
http://forum.xda-developers.com/moto-g/help/guide-fix-gps-cm12-t3084705

In this case the fix has now been added to the CM Official Nightly.
It was related to a missing driver which is what my previous link pointed to.

Related

Defy CM7 RC1.5 GPS Problem

Hi There
I've been using CM7 RC1.5 for at least a week. Everything works smoothly, much better than the crappy stock ROM does, except for the GPS.
Whenever I try to locate myself with Google Maps by GPS, the GPS fails to locate. The GPS is fully functional with the stock ROM and I have no idea what the problem really is.
I haven't tried RC1.5 yet, but I was having the same problem with CM7 RC1. I tried everything and couldn't get the GPS to work. Finally I flashed a nightly build of CM7 (8/17) and it started working again. I would start there and see if you can't reverse engineer the problem.
Use this fix : http://forum.xda-developers.com/showthread.php?t=953630
Flash it in custom recovery
Basically all it does is edit /etc/gps.conf to include time servers for your region from here http://www.pool.ntp.org/en/
Thanks
The issue has been fixed
a similar problem with the GPS was not fixed pravarth's link
i flashed CM 7.1.0 stable and the device just doesn't get my location using the GPS.
Apps like GPS Status and GPS Test plus give no results on GPS satellites found .
Any ideas ?
PS : it's defiantly a ROM problem. On Miui, GPS tracking was working. The only difference was that on MIUI, GPS apps will often reboot my phone.
Thanks.
GPS problem is fixed in my case after choosing my region from the Baseband Switcher.
Now i get some results in GPS status.
Orange Romania worked for me after choosing Central Europe, Hong Kong, Taiwan, Arabia, France, nordic 3.4.x, UK 4.5.1-85
My GPS problem is persisting.
I`m using CM7 RC 1.5, applied the patch for my country, changed the baseband still no luck.. .
If someone can help me, i`ll appreciate it. Thank you in advance.
Edit: I`v solved my problem using this http://forum.xda-developers.com/showpost.php?p=18777808&postcount=1150

[FIX][20-NOV] Omega v33.1 and v33.2 (+stockXXELK4) GPS fix

**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.1+v33.2 ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far).
**Where you can use it ?**
Tested so far on Omega v33.1, confirmed working on Omega v33.2 as well including some other XXELK4 stock/custom based ROMs
Not needed for Omega >=v33.3 or patched stock ROM XXELK4
**Just press THANKS if it worked**
Thanks to Omegas Team.
All you need to do to fix is flash a different kernel
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Incorrect. Lots of people running 4.1.2 on various kernels and still facing the same problem. Myself included having tried 3 different kernels.
Sent from my GT-I9300 using xda app-developers app
Kickasskev said:
All you need to do to fix is flash a different kernel
Click to expand...
Click to collapse
Not helping. Already tried. This is nearly annoying like the hello hello bug. Not all got it and every phone needs a different fix.
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
Chris_84 said:
Edit: Tried the fix before and don't work for me. Can't get no fix after flashing but it could also related that I got a custom kernel installed. You say you on custom kernel too. Did you flashed the video fix?
Click to expand...
Click to collapse
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
*sorry* I just flashed also another modem just prior to that fix, see 1st post...however when I flashed different modem before I was trying to fix GPS issue, it didn't help at all
shaarky said:
No, just Omega, custom Kernel and then this simple fix. Wait for the 1st fix, also be connected to data/Wifi. Best for testing is GPS test.
Click to expand...
Click to collapse
Don't know for sure but think maybe the video fix who install the old libs brake GPS again but I'm not sure. As I wrote in omega thread. After dirty flash it works perfect even with custom kernel and after installing the video fix it brake down again.
Throwing out of the window from my flying Ferrari killer S3 driven by a proud omega team member
It's working so far.
I haven't flashed fix video but installed siyah so sooner or later I'll need the video fix.
I'll let you know how it goes.
Sent from my GT-I9300 using xda app-developers app
shaarky said:
**Symptom**
Loosing GPS fix on I9300 after 20sec-20mins on latest XXELK4 / Omega v33.x ROM mainly in case of 1st lock on more then >10 satellites.
**Possible solution**
Flash in CWM this one for fixing the GPS issue on Omega v33.2 (tested on 33.1 and was working).
**How it's done**
I simply took all related GPS files from previous Omega version where GPS was working fine and replaced them.
**How to install**
Simply via CWM and perform eventually permission fix after (just for case)
**Result**
Before I was loosing all GPS satellites in 20-30sec, now it looks stable, locking up to 15(17max) satellites
**Which solution I tried before and didn't help**
FasterGPS, setting the parameters
Reflashing Omega on Omega (noWipe)
Reseting aGPS data, downloading new one
Installing another modem, now I'm on I9300DDDLJ1
Turning off GPS, Google location, location via Wifi, rebooting phone and re-enabling again.
Wiping cache + Dalvik-cache + Fixing permissions (after this step I had to reflash no-Wipe the ROM)
Flashing another kernels - stock, GalaxiSih, now I'm on Boeffla-Kernel
**Warning**
Be sure you have nandroid backup and/or reflash no-wipe in case of troubles (wasn't however observing any issues by myself so far). Tested so far on Omega v33.1 only, but should work on v33.2 as well including some other XXELK4 stock based ROMs
**Report and let others know if this helps or not and/or press THANKS**
Thanks to Omegas Team.
Click to expand...
Click to collapse
Tried all what you have said you had tried and also no luck - still having GPS problems.
Installed the fix.
Before installation, using Waze, I used to get a fix within 5 seconds, and then I used to lose the signal after 3-5 Mins. max.
After installation - got a fix same within ~5 secs, and I kept it on for about 10 mins and I had no signal loss.
I will try it further on my way home (about 20-30 min drive) and post results.
Thanks alot - hope this might just do it!
***EDIT***
Drove 20-25 mins home - all working fine.
Will do more testing tomorrow, but looks like this is the fix, for me anyhow.
Big thanks!
Work for me.
This fix work for me. Test during 40 min of navigation .I´m on Omega 33.1 with video fix and Kernel Perseus 26.1
Will test again on the end of the day.
is the "use wireless network" is turn on on your rom??
or turn off??
not working for me on omega 33.2 + stock kernel
liad1981 said:
is the "use wireless network" is turn on on your rom??
or turn off??
Click to expand...
Click to collapse
Is ON
Sent from my GT-I9300 using Tapatalk 2
Small report:
Today morning I use GPS (Waze and Be On Road) to navigate to my work (15km).
Lost signal every 3 - 5 minutes. Strange.
In my work I flash your fix.
Navigate (Be On Road) approximately 15km to customer and 15km to work. Working absolutely good.
Thank you.
I will test later much more and report again.
Update1: On the way home from work gps navigation (Be On Road) work like a charm. I am lucky
Update2: Today on way from home to work, working very well. Thank you. Now I vote for YES
Hi my friend. But suddenly your fix work here. Did another full wipe. Installed my usual stuff and got no fix. Then I thought I try again your zip and it works for now. Will test how long but really hope that's it.
Sent from my GT-I9300 using xda premium
i installed 33.2 with no wipe on 33.1 and i had the gps problem.
it found the first fix but after 2-3 minutes the fix isnt possible.
i did a first check with your fix and it seems to work now...tomorrow on my way to office i will give it a try
thx
How did I miss this! Going to flash and test on the way to work tomorrow...looks promising!
Sent from my GT-I9300 using Tapatalk 2
Not sure i tried this one, but just flashed it and will try in about 2 hours and will report back.
For me it's working now.. I'm on Omega 33.2 and latest Siyah
tapatalked via SGS3 on OMEGA and Motomoto00
Oke, just had my 25 minutes drive.
Flashed your zip before went on the road, double checked that Use wireless networks was enabled again, this afternoon i disabled it and gps worked again.
And from work to home, not one single drop off gps noticed using Sygic.
Also watched carefully to Sygics speed meter and it was corresponding with the speed i actually drove, not going from 30 to 100 i saw yesterday before gps broke down.
Looks your file did it for me.
Deleted

Motorola Droid Razr M mic working on cm-11-20140814-NIGHTLY

I wanted to comment on http://forum.xda-developers.com/showthread.php?t=2735565&page=75 but I don't have enough posts/permissions so I'm starting a quick thread to let the CM 11 developers know that the mic (for phone calls) is working on cm-11-20140814-NIGHTLY (yay!)
Also, it seems the WiFi is stronger/consistent but I'll need a few days to see if I still get the disconnects that I've had for the past week.
Update: after the first call, phone microphone no longer works (sigh...
Since dhacker29 has abandoned CM 11 (see twitter.com/dhacker29/status/492840260481859585), I ended up switching to Gummy (loki.rombitch.com/Devs/Gummy/moto_msm8960/NIGHTLY/) (which he still supports)
And how is mic and WiFi on Gummy? I'm going to install it when I repair my phone.
Sent from ZTE V889S using Tapatalk
http://forum.xda-developers.com/showthread.php?p=54888085
Seems it is still broken.
Sent from my XT907 using XDA Free mobile app
August 23, 2014 builds and later have the speakerphone fix: twitter.com/dhacker29/status/503044191392649217
WiFi bug fix was also apparently rolled into the Aug 23+ nightlies: github.com/CyanogenMod/android_kernel_motorola_msm8960dt-common/commit/13df898776edb42ac77c5cdb1aeade4d01434954
Sigh... WiFi still broken on Gummy and CM 11 nightly: twitter.com/emmons_az/status/505830673278832641
Argh... and now no GPS at all
...time to switch back to CM 11 since at least it has Privacy Guard and seems to be keeping pace with Razr M fixes
It appears Motorola devices require you to run GPS at least once on stock before installing a custom ROM in order to "unlock" GPS: forum.xda-developers.com/showpost.php?p=54608635&postcount=3789
What a lame "feature". I'll try that and see if I get my GPS back.
Okay, so GPS now works thanks to the "unlock" step mentioned above.
WiFi still stuck on the dreaded "Obtaining IP Address" bug:
forum.xda-developers.com/showthread.php?t=2735565&highlight=obtaining+ip+address&page=78
forum.xda-developers.com/showthread.php?t=2609966&page=22
code.google.com/p/android/issues/detail?id=11236
Still no luck and running out of options so I'm going to downgrade from KitKat to JellyBean and install the JellyBean bootloader version of CM 11: download.cyanogenmod.org/?device=moto_msm8960_jbbl&type=nightly
I was able to downgrade to the Jelly Bean bootloader and then install the latest CM 11 _jbbl nightly using this guide: mrbluecoat.blogspot.com/2014/07/tutorial-installing-cyanogenmod-on.html
So far so good. WiFi picks up my wireless network (without having to use the static IP address workaround needed with the KitKat bootloader: blog.chaucery.com/2012/05/fix-for-obtaining-ip-address-android.html). GPS is also working now that I know to enable GPS on the stock ROM before flashing.
...fingers crossed :silly:
morgud said:
I was able to downgrade to the Jelly Bean bootloader and then install the latest CM 11 _jbbl nightly using this guide: mrbluecoat.blogspot.com/2014/07/tutorial-installing-cyanogenmod-on.html
So far so good. WiFi picks up my wireless network (without having to use the static IP address workaround needed with the KitKat bootloader: blog.chaucery.com/2012/05/fix-for-obtaining-ip-address-android.html). GPS is also working now that I know to enable GPS on the stock ROM before flashing.
...fingers crossed :silly:
Click to expand...
Click to collapse
JB BL CM11 doesn't need that GPS "unlocking" step - mine grabbed a GPS fix in 3 seconds right after flashing CM11 (that's right, I can't even believe it myself).
Sent from Google Nexus 4 @ CM11
[WARNING: XDA Premium 4.0.13 lacks Signature function - do not update]
AndyYan said:
JB BL CM11 doesn't need that GPS "unlocking" step
Click to expand...
Click to collapse
FYI, my GPS works fine on Navigator, RunKeeper, GPS Test, etc. but on Google Maps I get a giant blue circle indicating my coarse accuracy isn't locking onto my position. I'm running the latest CM 11 nightly on Motorola Razr M. Thoughts?

Weird CM 11 and CM 11 based ROMS issue with calling

Hi fellow forum members!
I recently found great ROMS at Kevin's web storage. I tried them all and they work amazingly well except for one thing. When I make a call for a first time after a clean boot everything is fine. But when I make another call I can not hear anything nor the person I'm calling. After a reboot I have one shot again. Each time I want to call I need to reboot my phone. It only happens on CM 11 based GPROJ ROMS. Anyone encoutered this issue before? Any suggesting? Solutions?
Thanks, Zunex
nuraH6 said:
Quote:
Originally Posted by ShorelineDroid
Can anyone confirm the new nightly still has the call issue?
Alright, so after chatting with a CM maintainer we've been able to narrow it down to an upstream CM issue along with the phone not going into deep sleep. So, point is, no matter how many of our commits I revert it still won't fix the problem until CM fixes it on their end. I'm told it shouldn't take too long and will keep an eye on CM gerrit to see when an update is pushed into their code to fix these issues. So its not just PAC it's an LGOG gproj that sync'd to CM after 10/4.
Until the issue is resolved you can use the nightly 10/4 as it doesn't have the dialer or deep sleep issues and I will update when I hear more.
Click to expand...
Click to collapse
Same problem here on PAC-man ROM
I am facing the same issue with 10/13 nightly build. Its so frustrating to miss out so many important calls due to this call issue. They pulled back their 10/16 and 10/17 nightly build citing some major issue with the builds. Expecting a build asap with fixed call issue.
I had same problem. I was going back to CM snapshot-M11. This doesn't have call problem.
Is it fixed yet? Any news on this?
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Fotonic said:
Updated today to cm-11-20141025-NIGHTLY-e975 but the calls bug is still there...
So, what should we do to solve this?
Click to expand...
Click to collapse
Thanks for the heads up. I don't know. I really don't wanna go back to stock because of dsp manager but this bug forces me to. Hope it gets fixed soon.
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
I installed the stock rom after this issus. I think the stock rom has a good battery life.
cabe2001 said:
Reading This I found the solution to audio-caf problem. The solution is replace in system/lib/hw the library audio.primary.msm8960.so for a working one, I used the library from official M11 and now everything is OK. Attached is the library I used.
Click to expand...
Click to collapse
Confirmed working!
Thanks cabe2001.
Does anyone have the skills to create a flashable zip that overwrites audio.primary.msm8960.so with a working version?
Is it as simple as deleting everything from a standard CM zip?

Has anyone got a 5.1.1 ROM with WORKING rotation?

Title says it all.
I've tried numerous ROM's from moonlight, and they worked great up until recently where I cannot get rotation to work at all. I have instaled ColorOS 2.0 as a substrate package, but still doesnt work.
The previous ROM I used was moonlight's Blisspop port, because rotation worked. Then I stopped receiving mobile signal so I changed ROM. Now I have mobile signal, but no rotation.
Mokee also does not work, and they have open issues of this on their bug tracker, but no responses. So I assume they are ignoring it.
Prefer latest ROM's of course, but as long as rotation works I don't mind. Any help is appreciated.
Sorry to do this, but, bumping post. Lack of rotation is killing me. Using a manual rotation app just doesn't cut it.
Anyone have any idea on a way to 'fix' the issue? I assume it must be software based, seeing as it worked in previous ROMs. Definitely not hardware, as I am not the only one with the issue, according to the bug reports on MokeeDev tracker. Alternatively, it seems that it could be an issue with the Oppo firmware, as the issues reported are on various Oppo devices.
PS. Rotation works on older versions of Android. It is only an issue on Lollipop ROMs. I tested this with a ColorOS 2 ROM. Moonlight, the dev of the Lollipop ROMs says that for rotation to work you must first install ColorOS 2.0 as a substrate package. I did this, rotation worked fine. Booted to TWRP, wiped and installed Lollipop and rotation does not work.
Seriously need some help here guys, if anyone can provide any it would be greatly appreciated.
IAmOmicron said:
Sorry to do this, but, bumping post. Lack of rotation is killing me. Using a manual rotation app just doesn't cut it.
Anyone have any idea on a way to 'fix' the issue? I assume it must be software based, seeing as it worked in previous ROMs. Definitely not hardware, as I am not the only one with the issue, according to the bug reports on MokeeDev tracker. Alternatively, it seems that it could be an issue with the Oppo firmware, as the issues reported are on various Oppo devices.
PS. Rotation works on older versions of Android. It is only an issue on Lollipop ROMs. I tested this with a ColorOS 2 ROM. Moonlight, the dev of the Lollipop ROMs says that for rotation to work you must first install ColorOS 2.0 as a substrate package. I did this, rotation worked fine. Booted to TWRP, wiped and installed Lollipop and rotation does not work.
Seriously need some help here guys, if anyone can provide any it would be greatly appreciated.
Click to expand...
Click to collapse
Yes, same thing is happen to me when using lollipop.

Categories

Resources