Almost all KK nightly has GPS issue occurring. I have tried almost all latest nightlies no hope. Anyone else facing same problems …?
Any fix to the issues?
Assistive GPS may work on all the ROM's but not Accurate (Device Only)
Is it Baseband related issue..? I think Baseband is only for network connectivity..
GPS & NFC not working in CM11 Nightlies
b00tbu9 said:
Almost all KK nightly has GPS issue occurring. I have tried almost all latest nightlies no hope. Anyone else facing same problems …?
Any fix to the issues?
Assistive GPS may work on all the ROM's but not Accurate (Device Only)
Click to expand...
Click to collapse
Yes I am also facing similar issue. Developers are not working on resolving GPS problem .It exists in every Nightly.
Please CM11 developers its a request to solve this issue immediately.
Thanks
GPS is fine with me
chinmay1234 said:
Yes I am also facing similar issue. Developers are not working on resolving GPS problem .It exists in every Nightly.
Please CM11 developers its a request to solve this issue immediately.
Thanks
Click to expand...
Click to collapse
I am using AOSPA Legacy 4.41 and GPS is working fine.
However, I've been reading about this problem, as here, like "all KK" ROMs for Xperia L. Was I lucky that I picked the right one as my first KK to test on my phone?
I suggest you give it a try. Personally, I am very happy with it as my daily ROM.
rafaelegomezb said:
I am using AOSPA Legacy 4.41 and GPS is working fine.
However, I've been reading about this problem, as here, like "all KK" ROMs for Xperia L. Was I lucky that I picked the right one as my first KK to test on my phone?
I suggest you give it a try. Personally, I am very happy with it as my daily ROM.
Click to expand...
Click to collapse
I will give it a try.. I think the issue was introduced in latest nightlies and this ROM AOSPA- Last release date 2014-07-05 01:44
Hope to see the drawing curtain issue in these nightlies
agps is not working too
Even for me GPS was not working on latest carbon nightlies and liquidsmooth rom. So i installed old build of carbon in which GPS was working fine and then flashed liquidsmooth by wiping data and cache(didnt format system and data). After that GPS was working properly on liquidsmooth.
In case it takes time to lock location by maps, try FasterGPS and GPS Status app.
Animus03 said:
Even for me GPS was not working on latest carbon nightlies and liquidsmooth rom. So i installed old build of carbon in which GPS was working fine and then flashed liquidsmooth by wiping data and cache(didnt format system and data). After that GPS was working properly on liquidsmooth.
In case it takes time to lock location by maps, try FasterGPS and GPS Status app.
Click to expand...
Click to collapse
I did a wipe of Cache\Dalvic cache to fix the issue and it is working fine now.. ::good:
Related
Just curious, I've tried Milestone AOKP which seems to work the best but it crashes intermittently. I've never had success with CM10. Could someone please help? Thanks!
Viper has always worked well for me.
infernoflo said:
Just curious, I've tried Milestone AOKP which seems to work the best but it crashes intermittently. I've never had success with CM10. Could someone please help? Thanks!
Click to expand...
Click to collapse
I like PACman ROMs. they have the best of everything, and GPS works Flawless everytime. Go with 4.1.2 for a very stable release.
Thanks guys, I'll try those out.
ParanoidAndroid has NOT worked for me either (although it's a great ROM as well).
Official Cyanogenmod 10.1 seems to work perfectly. Always get accuracy of about 1 meter.
Have you been able to use the Navigation or any other app that requires constant GPS tracking?
I just tried PACman rom and it also has crashed on me. I also tried the AOKP (March 7th, but not discontinued) rom and it works for a little longer then crashes.
if using Google Navigation, don't bother cuz is a known issue for google.
Guys, am I the only one getting constant reboots on the latest nightlies? I load up a nightly (have tried 3/17, 3/19, 3/23 so far) and I clear data cache and dalvik prior and post load. I also load the newest 4.2.2 gapps for jb.
The phone reboots itself on everything from Temple Run to basic browsing to music playing through Bluetooth. There seems to be no rhyme, reason, or specific app causing it.
I am using the built in kernel... Is this kernel instability I am seeing?
Please tell me I'm not the only one experiencing this. I am a big fan of cyanogenmod, have used it on many phones over the years but this has been very unreliable for me.
Thanks, Brian
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Shaftamle said:
Did you try to fix permission using cwm or ROM manager? That might help. if not, try aokp 4.2.2 or liquid smooth.
Sent from a Shaftamle Galaxy S3
Click to expand...
Click to collapse
Ok so I fixed permissions on 3/23 cyanogenmod nightly, still constant reboots. Then I flashed aokp (hilbert) newest nightly based on 3.0.68 kernel and I am getting the same problem.
Is there any other way to troubleshoot this? Can someone else speak up who is running the newest night lies without FCs or reboots so I know I'm not crazy.?
Thanks for your IMs as well... I will definitely try newer builds.
bguild said:
Guys, am I the only one getting constant reboots on the latest nightlies?
Click to expand...
Click to collapse
I didn't get constant reboots but I did get random reboots from time to time.
I also noticed the latest nightly I ran (3/23) seems very slow.
My fix was to restore my backup of CleanRom and I may just not return to CM 10.1.
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
NeoMagus said:
Lockups and random reboots have been discussed for the last few pages in both the thread in this section and the dev section, commonly seems to have started 3/18 nightly when they switched over to the 3.4 kernel..newest nightlies were supposed to have some fixes merged but I haven't tried it yet
http://forum.xda-developers.com/showthread.php?t=2071252&page=124
personally had the issue on both 3/20, 3/21 , rolled back to the last nightly on the old kernel which is 3/17 and haven't had it happen since as for AOKP I don't use that so couldn't tell you what the issue is with that ROM
Click to expand...
Click to collapse
My thought is that in my case there may be something else going on. So far I have tried Cyanogenmod 3/17,3/20 and 3/23 nightly, a 3/23 nightly for AOKP, and now I just installed CleanROM 6.2 R2, which is Android 4.1.2 based. I think most of these kernels are 3.0.x based. I am definitely still getting occasional reboots and FCs but I will say it seems CleanROM is the most stable.
The common thread on all of these builds seems to be that the most instability occurs when attempting to connect to a bluetooth device. That is when I get the constant reboots. I'm talking like you start to play a song, and it gets through half way and just completely reboots itself.
I'm going to keep trying here, but I might have found the common thread in bluetooth instability.
Does the 3.4 kernel report as 3.4.x on the newer nightlies?
Yes it shows in the settings, I personally haven't had any issues with connecting or using my A2DP rocketfish Bluetooth headset even when I was on the newer nightlies with the 3.4 kernel, it was more of hadn't used the phone for a while went to turn the screen on and it wouldn't come back had to battery pull.
Haven't had a single problem since rolling back lockup or otherwise so I'm watching the main threads to hear when they get the issues with the kernel figured out before flashing anything newer
Hi. I'm experiencing a problem with the GPS on liquidsmooth 2.5. Starting any application using the GPS(google maps, camera with location tags enabled) causes the phone to reboot. I haven't seen any fix for that problem on the liquidsmooth thread(although others mentioned the same problem), and I've already tried a full wipe and reflashing the ROM.
Thanks for any help!
schok51 said:
Hi. I'm experiencing a problem with the GPS on liquidsmooth 2.5. Starting any application using the GPS(google maps, camera with location tags enabled) causes the phone to reboot. I haven't seen any fix for that problem on the liquidsmooth thread(although others mentioned the same problem), and I've already tried a full wipe and reflashing the ROM.
Thanks for any help!
Click to expand...
Click to collapse
I've experienced the same issue. With 2.4, it was the launcher (nova). With 2.5, it's definitely gps. Had to nandroid back to a more stable rom.
Sent from my SGH-I727 using XDA
Alpha Omnirom 5.0 (Trying to get calls to work properly on CM first before doing more omni builds))
baseband is still unknown. So no phone calls or data.
Alpha Cyanogenmod 5.02 with working baseband
https://drive.google.com/file/d/0B4k5OpXTXcS9NF8zN1dreFAtOUk/view?usp=sharing
Build 5.0.1:
https://drive.google.com/file/d/0B4k5OpXTXcS9NVp0Sm9YMFdEUUE/view?usp=sharing
Calls should now work without lockups. Data seems flakey? Let me know your finding
(This is now working due to rolling back to old RIL blobs (pre 4.3). This means that the connection process takes longer on initial start-up and switching to air-plane mode as well. )
Leave wifi on to avoid reboots.
Also this doesnt have the camera bug fix yet that Derteufel made.
Nice.. Never been a fan of omni.. I'm more a cm or aosp person
Sent from my GT-I9305 using XDA Free mobile app
REVIEW
Thank you very much for this build for the i9305
I have been waiting for the first lollipop build
I installed this rom and this is a written review after one hour of usage
1 the phone boots without any problem
2 lollipop gapps are working
3 Sometimes wifi works and sometimes no
4 Bluetooth works
5 some random reboots and sometimes it stuck so I need to remove the battery to get it working again
6 no FCs at all
7 seems fast
8 when I open an app installe from play store the phone stucks and I remove the battery
Thanks again and I wish u improve this rom in the coming days
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
aaz03 said:
Good job mate but I think it'll be better to edit your thread to make something more attractive, Flash Guide for noobs , links to gapps, alternative dl links , what works, what doesn't , credits , shiet like this would be better for everyone.
The main problem of your rom seems to be the kernel (random reboots , wifi issues , random freezes)
Anyways , good luck and thank you for the rom
Click to expand...
Click to collapse
Thanks for the feedback.
This isnt meant for n00bs to flash yet. This is an alpha.
In Alphas you expect to get problems! This is only meant for testing and for trying out 5.0 on your device...
can we flash this normally?
CM 5.0.1 build added to OP. Please read notes about what isnt working before flashing!
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
limnaln said:
So the latest build is the most stable one (CM12)? Can I help you in any way, testing, logs or something?
Click to expand...
Click to collapse
Well at this point in time no. I've just got to try to figure out whats going wrong still and then people can test to see if it works for them and if there is any long term problems with it. Until then its just make a change, compile and flash and I'll let people know if I get anywhere.
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Tested. Boots okay. Data baseband ok. Incoming calls ok. Outgoing calls impossible. Tested with 2g
laurent.siku said:
for me it is stuck on bootloop... first flashed wih wipe full/dalvik/cache then flashed gapps - bootloop. second dirty flashed again, booted, android is upgrading, optimizing apps, then rebooted and again bootloop... how to get past this ?
Click to expand...
Click to collapse
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
infrag said:
As I said this doesnt have the camera firmware patch added so some people might get bootloops... I'll add this in the next day or two from Derteufel
Click to expand...
Click to collapse
So, we are at the final step - outgoing calls, huh?
There also appeared some new commits on nameless gerit, just informing
Outgoing calls can be made now. But it seems to lockup when hanging up. New link in OP for 'new' build.
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Edit: only got one question. Can wifi be turned off. Will disabling it cause bootloops?
infrag said:
Calls should now work!
This is using old ril blobs so initial connection from boot will take longer. Also I think data is stuffed a bit. Seems to take a long time to get connected. Seems to work for me after that though. Post your finding please!
Hopefully Derteufel can figure out the problem with the newer blobs but till then this is working if anyone is interested.
Click to expand...
Click to collapse
Yes, it does work indees! In and out! Really great, the whole system is smooth.
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Great work on calls! Please let us know when you include the camera firmware fix so I can download again and flash, this is the only thing causing me bootloops and preventing me for further testing. Thanks
Sent from my GT-I9305 using XDA Free mobile app
winxuser said:
Great work. Will be swapping back to the i9305 from the note 2.. All we need now is for someone to work on the stock cm kernel to make it smoother.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse
Stock kernel? We are only using that to get data working... I'm sure Derteufel will switch to his own kernel as soon as he irons out the problems with phone calls locking up etc. (Or he switches to old RIL blobs for now)
Then there will be the challenge of getting R4P0 drivers to work properly.
After that who knows? Fix opensource compass?
Then Nameless may have other upgrades to implement for HWC.
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
No such issue here. Try full wiping and then reflashing CM.
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
avalanch said:
thanks for reply. I did that several time. But with no luck. Any other suggestion ??
Click to expand...
Click to collapse
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Primokorn said:
I recently had BT issues on CM12 and I do think that's a rom issue. Other users also reported bugs with BT.
Flash every nightly until the fix comes or switch to another custom rom for the moment.
Click to expand...
Click to collapse
Thanks for that info. Good to know i am not the only one. I am on a mission of trying all the Cm12 Nightly from jan onward till today. Hopefully 1 of them will work... Any suggestion for most stable of nightly is appreciated. Thanks. Trying different roms too.
avalanch said:
Hi i am currently using Cm12 Nightly 5.0.3 030315, With cm stock kernel. When i play audio thru my car Bluetooth it skips after ever 5 to 10 sec. If i watch video, the audio is delayed. The audio works perfect on regular bluetooth headset. The troubleshoot i did fix this problem so far.
Tried ever build after 02/21 till now still same thing.
I tried custom kernel like franco and elementalx. Did changes in hotplug while using franco kernel. Change Processor setting to performance under cyanogenmod. I have been trying find the fix but with no luck. The only thing that works is if i go back to cm11. Once i do that everything is normal.
Side Note, Every time i installed the Rom it was clean install.
Any help is appreciate at this moment. Thanks in advance.
Click to expand...
Click to collapse
I have the same problem with a 32GB nexus 5 and the recent cm12 nightlies, I have found a dozen or so forums/pages about the problem but nothing that seems to help. I have tried flashing different radio.img file and different kernels, the problem only happens in my car, my bluetooth headphones and everything else works fine. My car can take phone calls but not play back music/audio from anything without skipping every 5-10 seconds for ~1 second
That's because CM team still don't get, that it's better to start building a house from the ground, then from the roof. It's a kernel related issue.