I've been using official Cyanogenmod 12 Nightlies for a while now and after a while I only noticed that I do not have GPS lock on.
At first, I thought it might be an issue with the rom, so I flashed CM11 by Quarx. I'm still getting no GPS lock-on.
A bit more than a half a year ago I used the CM11 by Quarx and I had GPS lock-on. I've been testing it by using apps like GPS status but to no avail.
Thank you for your help!
I'm using XT1032 8GB EU GSM model.
[SOLVED]
I restored the original 4.4.3 firmare which I had backed up just after unlocking my bootloader and flashing TWRP and it locked on almost instantly!
Now I flashed CM11 on top of it and it works like a charm!
Related
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Always had the same problem when running Paranoid Android (not tried other ROMs). Had to return to stock, where GPS runs fine. Would also love to kknow how people have got it functioning.
I am trying too. I modified gps.conf files, tried some workarounds mentioned in cm11 thread like restoring GPS Status backup from stock with titanium so far with no success. Some people say that it works but it doesn't on mine whatever I do.
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Interesting, why does it work on some while it doesn't on others? Maybe some variants are having problems...
I have xt1033 asia version.
spajdo said:
I run on CM and I don't have any problem. Everything works fine with gps and I didn't use any fix or something similar.
I'm on CM 11-20140627 and I have 1032 phone.
Click to expand...
Click to collapse
Which recovery did you use?
CWM
As I wonder is about library missing or some partition need from stock ?
I've also been using the micro gapps package, would this matter?
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
TMaxtor said:
I had problems with Paranoid Android and GPS too... If anyone know something about that, please comment!
Click to expand...
Click to collapse
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
thestory101 said:
Hey i found a solution, you have do this flash following in this order.
- flash stock 4.4.4 (depend on your current)
- flash cm
- flash gapp
I try this twice and work like a charm.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I am having he same problem on XT1032 running Carbon ROM. GPS worked fine on stock, no signal with Carbon.
I found many answers saying to flash stock and then reflash custom ROM. I will try it, but I wonder, how does this help? Isn't the phone restoring the whole system? Do I have to keep the gps.conf from stock?
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Did you wipe anything, like Dalvik, Cache and Data, or you just flashed it over?
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Sorry people, I was so happy to have my phone back working, I forgot to write it back here.
Yes it worked indeed, all I did was flashing back the stock, going outside to have a gps lock with gmaps, then re-flashing back the Carbon. I also kept a copy of the gps.conf, but I never needed it, the GPS got a fix quickly. Working fine so far, it only takes some tens of seconds to fix, from time to time.
I can't remember if I also did all the wiping, I think I didn't, but I made so many trials in a couple days, I am not sure.
Thanks a lot guys!
am05 said:
I've read in some CM thread on here you need to flash stock ROM then enable GPS and get a lock. Once you've done that then flash your custom rom. Sounds STUPID and dosent make sense I know, but a lot of people say this is how they got it to work.
EDIT: I can confirm. I've just flashed stock 4.4.4 and played around with google maps. Flashed CM11 nightly and my GPS is now working ok
Click to expand...
Click to collapse
Yes, this worked for me too on PA.
I couldn't even see a single sat (it wasn't just a lock problem). No matter with gps patch, gpx fix app, or gps.conf I used.
What I did?: Back to stock, lock GPS, flash again the custom ROM (but don't wipe /system!).
Good luck on that guys, it should work for you too.
thestory101 said:
Hi all,
Did anyone able to use gps with custom rom ( I would say CM base). I research and try everything that's I could find here but not success.
Every time I do clean wipe everything including a internal storage. So that will nothing left behind.
I know that stock is work fine with gps. some said that install and replace stock but I have no idea that what file will left in our device when we delete all.
Click to expand...
Click to collapse
GPS works fine on this unofficial CM11 rom for me. Stable daily driver rom for me, YMMV.
General advice is to:
- make sure you get a GPS lock on stock rom first
- flash CM11 (or other custom rom)
There may not be a file left on the device. it may just be that stock contains the code to initialize the GPS functionality on the SoC or chipset firmware. Whatever, it works...
Hey everybody!
A few days after having flashed CM11 on my phone, I lost the mobile network signal... I restored to stock (4.4.4) but it didn't work so I came back to the latest C11 nightly... I tried a lot of things, like flashing the stock radio firmware, reboot, plane mode on and of,...But still no signal. Any idea, i'm worrying...:crying:
Thx for reading:highfive:
No idea guys?
Hello,
I am facing a weird problem regarding the proximity sensor on all CM11 roms.
I was using lollipop roms for a long time now, and have been following latest builds, until I decided that I liked KitKat more. I already had a backup of temasek's last CM11 build, so I reverted to that one, after flasing the cm11 firmware. All was working perfect until I reverted a backup of my 5.1.1 rom, to try xposed. Again, before doing so, I flashed the latest cm12 firmware. After a couple of days experimenting with xposed, I eventually went back to my kitkat rom. After boot, I noticed that the proximity sensor wasn't working. I had already flashed the cm11 firmware before restoring, but I went and flashed it again. Problem was still there. I then tried cm11s 44s firmware, 05Q firmware and 05Q modem only. The proximity sensor problem was there in all cases. (Shows 0.0cm, like I always have my phone in my ear or pocket). I then tried flashing a complete cm11s rom (05Q) with no success.
This is not a hardware problem, as the sensor is working FINE on ALL lollipop roms. I used sensor box in all my tests. I even tried proximity fix from play store, but it did nothing. I also tried to install it as secondary on multirom, then flash the firmware, but again, no success.
I really really need some help on this one, I can't troubleshoot it on my own, I am out of ideas.
Thanks in advance.
(My device is OnePlus one - always using boeffla kernel on both lollipop and kitkat roms.)
EDIT: Solved. Look at my last post.
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
chazxt said:
Flash again only modem but matching http://forum.xda-developers.com/oneplus-one/general/ref-oneplus-one-modem-collection-t2858734 I had the same problem, flashing again modem solved this issue for me.
Click to expand...
Click to collapse
Hello,
Which modem did you flash from that thread? I have only tried the 44s from there but it was a no go.
Thanks in advance.
XNPH44S for me it worked
Hello,
Finally found a fix for my problem.
It seems that I had to flash from fastboot the CM11 nightly modem from here: http://forum.xda-developers.com/showpost.php?p=57125376&postcount=389
The process doesn't wipe anything in case anyone is wondering, it just flashes the modem ( NON-HLOS.bin)
I flashed Euphoria-OS 1.1 (June-29 build, Lollipop v5.1.1), everything was great except non of the sensors work - accelerometer, orientation, proximity etc. I then downloaded a sensor app and it said "sensors are not present on your device".
The Euphoria Lollipop was a clean flash from PA v4.45 (Kitkat 4.4.4), I wiped everything and did factory reset. Flashed cm12 firmware before I flashed ROM and Gapps to avoid problems. Because I only noticed sensor issue after several hours, I thought it might be caused by an app I installed, went back to the drawing board and did a another clean flash, still no dice. Went on and flashed other Lollipop ROMs like CM12 nightly and XenonHD, still the same problem.
I've now done a Nandroid restore and back to PA Kitkat, all the sensors are working fine. So no hardware issue, definitely Lollipop specific.
Any help would be greatly appreciated, desperately wanting to bring my OPO to lollipop. Maybe I should flash a new radio? not sure if that'd do anything to the sensors :crying:
mickey4mice said:
I flashed Euphoria-OS 1.1 (June-29 build, Lollipop v5.1.1), everything was great except non of the sensors work - accelerometer, orientation, proximity etc. I then downloaded a sensor app and it said "sensors are not present on your device".
The Euphoria Lollipop was a clean flash from PA v4.45 (Kitkat 4.4.4), I wiped everything and did factory reset. Flashed cm12 firmware before I flashed ROM and Gapps to avoid problems. Because I only noticed sensor issue after several hours, I thought it might be caused by an app I installed, went back to the drawing board and did a another clean flash, still no dice. Went on and flashed other Lollipop ROMs like CM12 nightly and XenonHD, still the same problem.
I've now done a Nandroid restore and back to PA Kitkat, all the sensors are working fine. So no hardware issue, definitely Lollipop specific.
Any help would be greatly appreciated, desperately wanting to bring my OPO to lollipop. Maybe I should flash a new radio? not sure if that'd do anything to the sensors :crying:
Click to expand...
Click to collapse
Haven't ran CM12.1 so I'm not sure if they're having any issues with the sensors but have you tried OxygenOS or CM12S?
I know those 2 lollipop builds by far are the most stablest as I use them as a base for my ROM and all works fine. But to reduce the hassle, you can always stay on kitkat
Side note: Do you have a link for AOSPA KK?
Are you sure, you flashed the latest firmware? What is your baseband version in Settings>about phone?
Okay I finally got it resolved after reading through the thread about non-working proximity sensor. What I did was extracting NON-HLOS.BIN file from firmware and flash it with fastboot. Apparently flashing firmware in TWRP did not update at all, wired.
I had a nightly of CM13 working, but the SD card wasn't working correctly, so flashed the 20160820 snapshot, and everything was good except there was no connection to the sprint network. Wifi was OK. I tried flashing the latest nightly (20160930), and same issue. All downloaded from the CyanogenMod website.
So gave up and tried restoring the backup but it has failed, sdcard issue.
Tried the snapshot of 12.1 but it just bootlooped.
Edit:
So I tried flashing the 12.1 snapshot (20161001), still the same.
Edit:
I flashed this stock rooted - http://forum.xda-developers.com/spr...ment/rom-g900ppca-6-0-1-stock-rooted-t3387717 and got cell signal, but data only for a few minutes.
Any way i can get cell and data?
what version of TWRP are you using and what baseband are you on?
youdoofus said:
what version of TWRP are you using and what baseband are you on?
Click to expand...
Click to collapse
Thanks for the reply. I ended up reflashing the stock Deodexed rooted ROM and the cell signal came back, so at least I was able to make calls.
I was about to try an old Lollipop ROM, but saw the latest comments on this Resurrection Remix thread all seemed happy, with no issues, so late last night flashed it. So far this morning I haven't seen any problems, I have cell signal, LTE and the SD card seems to be working as intended. Wifi is good too. Just need to checkout Bluetooth and even that's not essential. Will play with it today and see. So I think I'm good for now. Again, thanks for your reply.
syco123 said:
Thanks for the reply. I ended up reflashing the stock Deodexed rooted ROM and the cell signal came back, so at least I was able to make calls.
I was about to try an old Lollipop ROM, but saw the latest comments on this Resurrection Remix thread all seemed happy, with no issues, so late last night flashed it. So far this morning I haven't seen any problems, I have cell signal, LTE and the SD card seems to be working as intended. Wifi is good too. Just need to checkout Bluetooth and even that's not essential. Will play with it today and see. So I think I'm good for now. Again, thanks for your reply.
Click to expand...
Click to collapse
Glad to hear! Don't hesitate to inquire if you have more questions