Hello,
I was running cm11 jfte a while, and works perfect.
But i wanted to try cm12 so installed 12.1 jftexx
And i was not charmed of lollipop .
so i did go back to cm11 jfte after a few weeks i found out that my gps not work (not us gps every day).
gps test app found nothing.
installed back to stock not working
clear install cm11 not working
install cm12.1 again gps works.
i use gps test app for testing the gps.
But i want cm11 how can i go back with a working gps?
give this app a shot , https://play.google.com/store/apps/details?id=tisinadev.activegps
Maybe you baseband has changed? Or try to set the agps to your location .
I tryed different GPS aps but nothing helps.
My son had the same s4 but runs still cm11 witch i also had exact same version..
Cm12 did change something
spikehome said:
I tryed different GPS aps but nothing helps.
My son had the same s4 but runs still cm11 witch i also had exact same version..
Cm12 did change something
Click to expand...
Click to collapse
Had the same issue. Installed CM12.1 but went back to 5.0.1 GPE: No GPS anymore.
Fixed it by flashing Stock Firmware with Odin, installed TWRP again and flashed my GPE rom again.
I tryed stock with Odin already.
Not helped
Related
I've recently moved to a new state and have been having to use my phone's GPS several times a week.
At the time I was using one of the Cyanogenmod 11 snapshot builds(sorry, I can't remember which one ). The GPS worked flawlessly. I would always update to the next snapshot build as they came out. One our two updates later my GPS couldn't seem to get a fix on my location. I tried wiping and doing a clean install of the ROM. Still had issues.
Eventually I got fed up with cyanogenmod and wiped my phone and installed Paranoid Android 4 beta 1. Had the same problem with the GPS. I tried several of the other beta releases as they came out to see if the problem was resolved. It wasn't.
So I restored my phone to stock using the Google factory images (4.4.2). The GPS worked beautifully. So I stuck with stock for a while and did the OTA update to 4.4.3.
After a while I started to miss the features and customizations that come with custom ROMs. So I wiped and flashed Paranoid Android 4.4 RC2. The GPS still can't seem to lock. On the rare occasion that it does it can't keep up with my car, especially if I turn onto another road.
Does anyone know what's up with the GPS? Didn't seen to have this issue at all on Jelly Bean custom ROMs. Is this an issue with Kitkat custom ROMs? Possibly a hardware issue? Any help would greatly appreciated.
Current setup:
Phone: Nexus 4(16gb)
ROM: Paranoid Android 4.4 RC2
Sent from my Nexus 4 using XDA Free mobile app
There appears to be an issue with KitKat and GPS. I'm running stock 4.4.4 and I can't get a GPS lock. I've tried everything I can, including a factory reset. I don't remember having the issue with 4.4.3, but I've seen issues reported going back to 4.4.2.
I don't know about you, but a reboot usually does it for me.
Hello dear xdaers,
I have an n9006 which I have been using with Omega rom for quite a while. And the phone itself is a genuine n9006, not a clone, I checked the first day.
I just recently decided to get my hands on a new rom and get the kitkat feeling so I have tried some custom roms and they worked fine. Then I decided to try an AOSP rom, W03 Slimkat v23 (http://forum.xda-developers.com/showthread.php?t=2638116)
This thing seems really well working for me except for one little! problem and it is the fact that there seems to be no baseband. And the status page shows unknown for practically everything except wifi.
In the light of this I panicked a bit and flashed latest stock rom from sammobile with odin. Everything works fine again (except the exclusion and the effort to make sure google services stay away. I remember struggling a lot to get google playstore and services installed. Then giving up and installing omegarom which kept me going for a while)
After this I backed up EFS and Radio from twrp recovery and flashed the W03 Slimkat v23 again, did the restore from the recovery and bam!
nothing.
Everything seems to be the same. I went back and forth between stock and slim and couldn't fix it.
The thing is I have nowhere the knowledge level of the users in this forum and I just have to learn all the things like odin and recoveries and download modes in one day and apply them. I probably am missing some fundemantal stuff. (heck I don't even know if EFS and Radio has anything to do with baseband) So please feel free to correct me on what I'm doing wrong and thanks in advance!
Update: I just tried to flash slimkat NON aosp version : http://forum.xda-developers.com/showthread.php?t=2669713
Same thing all over.
Backup EFS
Here bro, this may help you. http://forum.hovatek.com/showthread.php?tid=310#sthash.VtNUlpur.YxNJv18Z.dpbs
Can anyone help me?
When I install a aosp rom like the 4.4.4 roms
Everything works fine exept that during a call the screen goes black and there is no way to turn it back on again, only a reboot works.
I'm currently on the phoenix rom and that works good, also Imperium works fine.
With slimsaberkatrom or a Google edition tom I get the screen freeze.
Samsung s4 gt-i9505
You tried on PA and CM?
On Paranoid Android or CyanogenMod you have the same issue?
Yes, also tried paranoid rom, same issue.
Everything works exceptioneel the dialer
abarthcoupe said:
Can anyone help me?
When I install a aosp rom like the 4.4.4 roms
Everything works fine exept that during a call the screen goes black and there is no way to turn it back on again, only a reboot works.
I'm currently on the phoenix rom and that works good, also Imperium works fine.
With slimsaberkatrom or a Google edition tom I get the screen freeze.
Samsung s4 gt-i9505
Click to expand...
Click to collapse
Proximity sensor issue? Try recalibration while on a stock based ROM then reflashing aosp.
Seems like a proximity sensor problem. Used xposed installer to disable the sensor,and seems tot work fine now.
I look a wile around the internet before bringing my problem here.
My issue is like this. I use cm 12.1 and at some point few days ago my GPS stop working. I mean my phone cannot see any GPS Satellite.
I try the following:
Put back the official rom, both 4.4.4 and 5.0
Flash different Kernel.
Flash the PIT
Flash the modem.
Install 2-3 different Roms.
Now i'm back to cm 12.1 and is still have the same issue. What it can be? Is hardware problem? What i can do ?
Looking forward to your help guys.
Dear Community,
I hope that this is the right place to post and any of you can help me.
My (aktual) Hardware/Software bits:
Galaxy Note 3 (SM-N9005)
Android: 5.1.1
Baseband-Version: N9005XXUGBOD3
Kernel-Version 3.4.108-f2fs-temasek-cm12.1-hlte-v1.25+
temaseksnappy #1
Temasek unofficial version V16.4
Build: LMY48J test-keys
Recovery: twrp 2.8.7.0-hlte-4.4
My actual problem is the following: My Note 3 by default had a 4.4.2 OFW on it, which I early upgraded to Lolipop 5.0.1. Everything works for the OFW 4.4.2 and 5.0.1 fine. As soon as I try to flash it with a CFW like CM11, CM12, CM12.1, CM12.1 (temaseksnappy), Gummy 4.4.4 I am losing the feature of auto rotation.
Of cource I did a clean flash, wiping DALVIK/CACHE/DATA and system, double time even one befor the flash, one after.
I also tried to put the battery, sim and sd out for few min before rebooting, while autorotation is manualy turned off.
Even a MODEM I flushed to fix this issue, but without success. Nothing helps but going back to OFW.
My last try was downgrading to the original 4.4.2, including baseband trieing from there to go to any CFW (CM11) as well as from OFW 4.4.2 -> OFW 5.0.1 -> CFW 5.1.1 (http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375)
There was also a post about a possible missing or broken lib in /system/lib which I replaced
Nothing helps (libGNU... something). This helped me alreay once in OFW after kicking out all the junk apps, but this is a different storry and not related anyhow.
Is there anybody out there who has the same problem or even better knows a solution?
My shot would be that:
1) CM has a problem with my particular hard-/software (Kernel, Baseband, Recovery, whatever) as I just tied CM or at least CM based CFWs.
PLEASE HELP.
Thank you very much in advance.
After about almost a year I cam back, giving again a try to CM, However I still have the same issue. Finally Anybody please!
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Rosli59564 said:
Do you have the same issue with touchwiz 5.1.1 and 6.0.1?. Not the cm/aosp roms which aren't samsung based.
Sent from my SM-N920C
Click to expand...
Click to collapse
Hello,
Thx for your reply. Right now I am on CM13 (temasek hlte v9.6)
http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375
This might should be specially compiled for sm-n9005 like mine.
Everything expect rotation works fine. However The accelleration is also working fine as I tested with "sensor test". Even the integrated camera App is rotating, however the rest is not.
In addition I downloaded "adaptive rotationfree", If I set it "stock Auto" nothing happens, but if I set it to "force auto" the rotation will work exacly once and then stops undtil I force it to portrait again.
What do you mean exactly with "touchwiz"? Is this jus a different kernel or a whole CFW?
As I wrote in the frist post I tried already a lot of CFW and ALL had this issue, but the OFW ;(
What shell I flush to get this working, which is not OFW?
BIG THX for YOUR HELP
Touchwizz is the firmware that comes with the stock Samsung firmware .
Also in custom Samsung based roms .
Hello,
thx for the tip with TouchWiz vs aosp. At the moment I am running "DarkLord N5 Release Candidate 2.12" which can get find here: http://forum.xda-developers.com/galaxy-note-3/development/rom-darklord-s6-port-alpha-t3083087
This Rom is TouchWiz Based and guess what ....
Autorotation works.
However I do not understand what the problem realy is and would prefer to run cm13 insteat. I mean even samsung devices got a accellerator within which works also fine with AOSP software, showing numbers moving while turning the phone. In addition for example on the post http://forum.xda-developers.com/galaxy-note-3/development/hlte-spr-vzw-temaseks-unofficial-t2953375 it is said that this is explicite for note 3 including the model n9005. So ...
Can anybody point me to the problem or even better to the fix?
Is there any chance CM would fix this?
Regards