I've been fighting with the cm11 d2lte builds since I updated to a nightly in the beginning of September; since then (I believe the 9/7 nightly was the last one that worked), I've had trouble with GPS losing locks, or getting locks at all. I tried several nightly updates in hopes this was a known and fixed problem, as I've seen many complaints about GPS in cm11, but none of the nightly or snapshot updates helped, and some made things worse.
I have tried everything I could find, including toggling between Maps and other map/GPS related apps, full ROM wipes and fresh installs, wipes to flash stock firmware and then come back to cm11 after getting a GPS lock in stock, 3rd party apps like GPS Status to update/wipe aGPS (assisted) data, etc. The state my phone is in now is:
- Did a full wipe of data and cache partitions
- Installed stock backup, got a GPS lock, and rebooted
- Wiped again and installed the most current cm11 snapshot for d2lte (11-20141008-SNAPSHOT-M11-d2lte)
- Using GPS Status and toggling between Maps and Waze to try and get GPS locks
I'm able to get a lock sometimes, but not often enough and not when I need one most: Maps recently turned a 1.5 hour trip into a 3.5 hour nightmare with a really bad route and no ability to reroute.
As an afterthought, I realized that when I'm in my car, I'm usually using the phone for 2 things:
- GPS/maps
- audio output from headphone jack to car aux input
While playing with GPS on the way home today, I unplugged my audio cable from the headphone jack ... and I suddenly got a GPS lock. Plugged the audio cable back in, and lost the lock. Pulled it again, and got a lock. WTF? I've been fighting with this for a month, and don't think I've seen a single mention of audio affecting GPS.
Can anyone else possibly verify this? And any suggestions on a fix?
Thanks!
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
From my Wicked S3 on SOKP
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
ShapesBlue said:
I've read before that tightening the screws inside the back of the battery sometimes solves this issue
Click to expand...
Click to collapse
Not sure what you mean, but if you mean the 10 screws surrounding
the frame, I've tried tightening them. I don't know of any screws on or beneath the battery.
MrBrady said:
Could be the rom. I'm on the latest AICP nightly and don't have either of those issues, which I have had on other roms.
Click to expand...
Click to collapse
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
deesto-xda said:
I'm pretty sure it's the ROM too, as it had no problem getting a lock when I downgraded to the old stock ROM. But was hoping for a fix as I don't see a lot of lingering complaints. How do you like AICP?
Click to expand...
Click to collapse
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
MrBrady said:
As of right now, it's my daily driver. Previously, I was on Task650's AOKP Build. You can find the latest on Google+ and a thread in the SGS3 AT&T section. Your two issues were mine as well and not may ROMs worked as I wanted. Task650s was the first I found that did work. Unfortunately he's not able to maintain the build any longer, so I started looking for other actively-maintained ROMs.
AICP fit that bill for me. They are constantly updating it. A little too much so in my opinion because they have a new release nightly. However, it's a solid mix of what AOKP with some added goodies that take it to the next level. GPS is rock solid. I use an iBolt Car Dock for my SGS3 and audio out works fine when docked. I haven't had any Bluetooth or SMS/MMS issues as people have reported on other ROMs.
Give it a try and see what you think. Make a nandroid first and you can always revert if it's not to your liking.
Click to expand...
Click to collapse
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
deesto-xda said:
Thanks MrBrady. This sounds good, and I think I'll give it a try.
But I'm still curious about the cm11 issues, and whether anyone else has seen them -- and has some weird fix they might not mind sharing.
Edit: BTW, possibly just a coincidence, but in checking out AICP, I see that the latest "release" ROM from AICP is 'aicp_d2lte_kitkat-6.0-RELEASE-20140909' -- 20140909 happens to be the same dated cm11 nightly i had to keep reverting to because there were so many problems with nightly ROMs released within the first few weeks after that, and GPS hasn't worked properly since. Again, possibly a coincidence, but I wonder if there's a connection.
Click to expand...
Click to collapse
Most custom roms are based off other roms, aicp is one of the many. I switched directly to CM11 today because I was on another version of a cm based rom and the reboots were too much for me.
From my CM11 S3
Related
I downloaded the new PA 3.60 6/11 build from notta yesterday with KT747 Kernel and RErick universal setup. After using for a while, without attempting to call, I was more than happy. At work today I called my girlfriend and in the middle of our conversation the call dropped. Ever since then whenever I try to make a call I get a "com.android.phone has stopped" message or it will connect, close phone screen but keep call in status bar, show that same message, then drop the call. Sometimes it says "Mobile network not found" after trying to call then will reload my bars after. Can't receive calls either but my network shows I have bars and every IMEI & numbers alike are there. Restored nandroid and calls worked.
Thought it might be kernel combo so tried to wipe everything and reinstall but problem persisted. Any ideas on how to fix?
Thanks in advance!
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
andrewk7750 said:
Try the latest paranoid android gapps, i had that problem a few times but after i flashed those the problem stopped. And what's Rerick setup?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I've flashed the 6/10 gapps both times I flashed the ROM, unfortunately. Maybe bad download? I don't know at this point.
Its RErick's from Team Kernelizers setup for the KT747 kernel. Can find him on the TK Mod thread. Great battery life supposedly but didn't get to try it for too long since calls didn't work.
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
antiseen said:
I was running the latest pa with their gapps and calling was fine for about a day then I got the phone crashing every time I tried to make a call and couldn't receive any.
Did nothing different. I didn't try to fix it or anything, I just restored my tw backup.
Unfortunately, I've been running tw mostly these past few months. Occasionally I try out aosp, be it cm or another iteration, but go back due to the annoying deal breaking glitches. I've pretty much given up on running anything other than bone stock on this phone. Not sure if it's just my phone or what, but anything else always has obnoxious bugs that never seem to get squashed.
Shame, too. The developers do great work. Probably just my particular phone as plenty of others seem to run with zero problems.
Stock bloated tw with nova for me. Even the debloated roms run wonky on my phone after a couple days. Always full, clean wipe.
Click to expand...
Click to collapse
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
kenbrownstone said:
The same things HaS been happening to me with alot of asop ROMs. Only way to fix is not use custom kernel and the roam setting have something to do with it. It sucks cause I like the asop ROMs . Its been doing to me for two weeks just wonder if they have changed anything with these ROMs cause it don't matter if its cm PA AOKP or unofficial versions of these I just can run them anymore
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Since I've been having so much trouble with any rom I haven't used a custom kernel since my thunderbolt days. I run whatever kernel the rom comes packaged with.
But like I said, it's probably my phone. It has defective bluetooth that I didn't figure out until well after I purchased the phone. It's got constant loud crackling and popping on stock (ironically, non existent on aosp roms). I doubt that's related but just illustrates the weird differences between phones.
Had the same problem less than an hour ago when i really needed to make a phonecall. Had to restore to my backup i made before flashing PA. Hell of a time for it to stop working.
Sent from my SCH-I535 using xda app-developers app
Well after first believing it was just my phone, after reading these comments as well as the PA thread I've come to the assumption that its something with the ROM and how it behaves with the phone app. Hopefully the details will get resolved soon cause I was really enjoying the new PA. Until then, sticking with hyperdrive.
Thanks guys.
had this problem since upgrading to the 6/11 build.
i could make calls out as long as i didnt press the ok button to dismiss the process stopped message.
i could not receive calls hwoever. it does ring like it should, but it does not allow me to answer.
using latest gapps package.
I've had this problem on both 6/12 and 6/14, using the 6/10 gapps.
Any chance anyone has come up with some way to resolve this?
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
ddurandSGS3 said:
for ppl with this problem, i moved to pacman to get all my newest PA features setup with pie, expanded desktop and halo.
not having htis problem on there.
Click to expand...
Click to collapse
Good suggestion. Really liked PACman for a while, but eventually my call got dropped and I ran into the exact same issue from that point on. At this point I've just decided to go with a TW based rom. With hyperdrive you can still have pie and download Floating Notifications app that is practically the same thing as halo but also has themes available too.
Until that bug can be fixed, going to stick with Hyperdrive. Sweet rom anyway.
First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps
Not an official one, no, I have had the issue since the 4/24 build, but with some recent commits shortly after 10.1.1 it's been much better, but still not 100%. I know carvsdriver has identified the issue and just needs to get some time in to fix it, so it should be coming soon-ish to the latest nightlies. I don't know how likely it would be to get into a 'stable' release very soon, but for me, the nightlies are way better than the stable releases anyway.
Please read forum rules before posting
Questions and help issues go in Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
BT Problems - Getting better
rajb12 said:
First of all, a big thank you to the CM team from a relative noob, for all their great work.
I checked the forums, and there was an issue reported on 9 July about BT randomly turning off, and only fix to turn it on being to reboot. I have experienced the same problem in CM 10.0 stable, 10.1 stable, and now 10.1.2. Not a major issue, but an annoyance - was wondering of there is a fix for that?
Thanks
Raj
Running on Samsung Galaxy SII Skyrocket on CM 10.1.2, radio UCMC1, Gapps
Click to expand...
Click to collapse
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update
cejack said:
I caught a fix for BT in the changelogs on the CM 10.1 nightlies. Just ran the latest nightly update a few nights ago and seems to be much better.
Of course your mileage may vary but if you need some better BT performance in CM10.1 on the Skyrocket, I can vouch that it is now better. For me on 10.1 Stable, BT would turn off if I screwed around a few times with it (pairing and unpairing devices) and would force me to have to reboot to use a new pairing. BT would actually turn off and stay off after enough BT actions. Reboot was only fix. Knock on wood, now I can use the BT settings without problems. I'm hoping nothing bad pops up but I think there are definite BT improvements with the latest nightlies...
SGH-i727
UCMC1 Radio
CM10.1 - 20130727 - Nightly Update
Click to expand...
Click to collapse
I don't know that the commit was a complete fix, but it certainly helped. I saw a post on G+ about it (I think), and the developer mentioned that after 30 BT connections/re-connections, it would stop working, and that it would be hard to fix. It's definitely way better than it was.
Stereo Bluetooth works pretty well. Just listened to 3-4 hour podcast with Stereo Bluetooth P311 headphones.
Also used Motorola H500 bluetooth headset as well. No problem there. Also using 9XX Plantronics headset. No problem either.
All in all - can't complain about BT too much anymore after going from latest stable to more recent "nightly" releases.
If you run into problem.... you'll have to re-boot.
Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.
chas101 said:
Thanks to all the developer of CM 10.1 for a great ROM which has become my DD. One question: Bluetooth still requires an occasional reboot in the latest nightlies. With CM 10.1 now in maintenance mode, is this the best we can expect or is there still ongoing work to fix the problem for good? I have just been rebooting once in the AM, so I don’t get a surprise when I try to use BT in my car, so it’s not a showstopper. Just curious.
Click to expand...
Click to collapse
All I can say is that with 4.3 (CM 10.2), in the past week I have only had to reboot once to fix bluetooth issues, that I can remember.
Hey All,
I know this has been discussed ad nauseum, but I've had trouble finding all of the possible GPS fixes for the Verizon Galaxy S3, could anyone be so kind as to enlighten me? My GPS has been erratic for a while now, and is now at the point where it only shows coarse location, never locks onto any satellites. I'm on CM 10.1. Edit: I THINK I managed to fix it by clearing Services Framework, but I think it's a good idea to have all of the fixes in one thread that can be easily searched. If anyone wants to reply back with other possible fixes, I'll modify this post to include them.
- Tighten the Screws Fix
http://forum.xda-developers.com/showthread.php?t=2201668
- Clear/Download aGPS Data with the GPS Status app (Tools -> Manage aGPS State)
https://play.google.com/store/apps/details?id=com.eclipsim.gpsstatus2
- Apply gps.conf patch
https://play.google.com/store/apps/details?id=by.zatta.agps
- Clearing data on Google Maps and Google Services Framework
- Flashing to a stock ROM and back
--- Anyone have more details on this fix? Would CleanROM work for this purpose? If not, what's a good pre-rooted stock ROM?
Thanks!
Just some food for thought, I have noticed on some ROMs the GPS has issues locking, I only use aosp so can't speak for tw, but whenever I encounter these issues, usually changing out the kernel fixes it right up. Note, I do make sure the screws aren't loose also
FlashHappy78 said:
usually changing out the kernel fixes it right up
Click to expand...
Click to collapse
Got any more details? Do you switch to/from any particular kernel? Do you then switch back to your original kernel, or just use a different one until problems pop up again?
My problems have always been on CM ROMs, never had GPS issues when using a TW-based ROM. Currently it seems like clearing Framework fixed it (for now...), but good to see what everybody else has been doing.
funkymonk101 said:
Got any more details? Do you switch to/from any particular kernel? Do you then switch back to your original kernel, or just use a different one until problems pop up again?
My problems have always been on CM ROMs, never had GPS issues when using a TW-based ROM. Currently it seems like clearing Framework fixed it (for now...), but good to see what everybody else has been doing.
Click to expand...
Click to collapse
I've had good luck with leankernel, and kt747. I haven't taken note of which kernels gave me trouble, but most of the ROMs I run come with a cm source kernel.
Have you REALLY tightened the screws? I mean, don't use a slot screwdriver or a phillips that doesn't fit. Get yourself a good small phillips head driver and tighten them. I have had issues a number of times with GPS. Each time I go tighten the screws and I get locks on 15 satellites while indoors. No joke. I've run CM10, CM10.1, and currently I'm on CM10.2. No issues with GPS.
I use the "teeny turner" screwdriver, picked it up for $6 at the local computer store.
rgrossie said:
Have you REALLY tightened the screws?
Click to expand...
Click to collapse
Thanks. I've been using the tiny screwdriver from a jewelry repair kit. Don't think it gets any tighter, but I'll definitely go back and be sure. For me clearing the Google Services Framework data seems to have fixed the issue.
I saw a new "nightly" has been pushed out for the Relay. Based on the changelog (fixing integer overflows and underflows), this looks like a fix for Stagefright.
I've updated from within the 20150607 nightly, and so far, everything looks good. My GPS and camera still work fine, and I didn't bother toggling any settings before updating.
At least I have ONE phone with a Stagefright fix. It's kind of ironic that it's the oldest of my Androids.
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
So I guess it's time to bite the bullet and do the double-twist-and-backflip GPS fix. Let me go over this for a moment, to get it straight.
I need a new CWM recovery, latest'n'greatest.
I need and old 10.1 or maybe 10.2 ROM image.
I need the old baseband firmware to go with the old ROM image.
Is this the full list?
There have been numerous links to all three of these, but I tried last week, and at least some of them have gone stale. Does anyone have a current and working set of links for them?
My wife's Relay is still at CM11M8, and really it's about time I got her properly flashed forward, especially now with Stagefright and Freak both fixed. We've locked out on Stagefright so far because we have voice-only through PureTalkUSA, only do data on wifi, and therefore don't do MMS.
GPS fix:
You need a CM10.1 build (Only ones ever produced were 'experimental'), the ICS stock baseband (modem) and the JB stock baseband. Recovery doesn't particularly matter, so long as you can flash images, but I still recommend the CWM that has been around for a while (I've tested it, it works fine even with upcoming Images)
Procedure:
Boot into recovery, run a full backup on your device.
flash ICS baseband
Flash CM10.1 Image
Factory Reset
Boot into system (Not sure if this is needed, but I always do.)
Once system boots up, shut system down.
Open phone, pull battery.
Wait ~30 seconds, replace battery.
Boot phone.
Once system boots up, (If you have a way to test it, GPS should work now). Reboot into recovery.
Flash JB baseband.
Restore your system backup.
Reboot into system. Your GPS should now work with your current system.
I posted a reply into a thread, there was an up to date link with just the modem... I can confirm that running on CM nightly (june something) I have no issues with GPS, wifi 2.4ghz band doesnt work with bluetooth enabled though
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
phred14 said:
Last night I bumped both my wife's and my Relays to the latest nightly. There was a new version of clockworkmod recovery posted, so I flashed that, first.
My wife's phone is a bit of an odd one, on two counts. First, it was still at M8 with working GPS. So before doing anything, I went out in the yard, got a GPS lock (using M8), and pulled the battery. I then brought it inside, put the battery back in, and did the flashing. After that, I was able to again take it out in the back yard and get a GPS lock, this time with the latest nightly. (I've done it once, I hope it will work again.)
The second thing about my wife's phone is that it's acting really oddly. Most of the time when the screen blanks, it won't come back. None of the buttons will light the screen. Eventually long-pressing the power button will reboot it. I've verified that when in this "stuck dark" situation I can plug it in and run adb commands against it, so there's a light on in there, it's just that the curtains are drawn. With this in mind, I'm not sure what the story is about getting it to reboot.
My next step would be to search for any settings that might cause this behaviour. It's also giving me the yellow triangle in the notifications, and when I open it, it takes me to some sort of time-date settings area, but I'm not sure what's wrong there. It's possible that a timing problem could cause the symptoms I'm seeing - I'm not sure. My other option is a full wipe.
Click to expand...
Click to collapse
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
dzl said:
Funny, two people in Burlington using the Relay?? I haven't touched mine in a while but I'm itching for something different and I'm sick of my Xperia's stock firmware. I'm gonna give this new build a shot...
Click to expand...
Click to collapse
I got my Relay about a year and a half ago for Christmas, mostly as a learning vehicle, but also for the convenience. The plan from the get-go was to put Cyanogenmod on it. For a while it was wifi-only, then a few months later my wife decided she wanted one, and I found the Family Flex Plan at PureTalkUSA that let us have two phones for the the cost of a Virgin Mobile and TracFone. (What we had before) It's also one of the few ways to get voice-only, and use wifi for data.
The Relay is getting a bit long in the tooth, and perhaps most discouraging "aging" side of it is the ramp-down here. However anything I get will be CM-ready from the get-go.
Flashed the latest CM11 nightly today. No major bugs so far with moderate use throughout the day. So much faster than my Xperia with the stock firmware, actually enjoying Android again.
Sent from my SGH-T699 using XDA Free mobile app
20150823
I had been running M8 since it came out until last weekend. Decided to do a complete wipe and try for the newest nightly to fix the Stagefright bug. Things went real smooth. GPS is working faster than ever.
Everything runs like a dream... except the adaptive light sensor. Adaptive brightness is not working at all. I've check the sensors and the Lux sensor is working fine. If I turn on adaptive brightness, and then adjust, the settings crash. Anyone else experiencing anything like this?
Yeah that is one thing that I have noticed as well, the auto brightness doesn't work. Can't say I've attempted to diagnose it at all though.
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
TPMJB said:
We're still getting nightly releases for this dinosaur?
http://download.cyanogenmod.org/?type=nightly&device=apexqtmo
Crazy! I thought it was all but abandoned!
Click to expand...
Click to collapse
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
phred14 said:
It is, the nightlies are really monthlies. Still, I'm happy to have that, even. Google has issued more Stagefright fixes, and I hope to pick those up as they make it into CM. (Last I knew, Google was only fixing new stuff, but CM was back-porting.)
Click to expand...
Click to collapse
I would like for updates to CM12, but we only have unofficial versions of CM12. I am a noob at compiling and I hear it is an arduous task to get it working.
Magamo said:
After looking through the various codebases of Omnirom and CM, it looks as though Omni's android-5.1 branch, and cm's 11.0, 12.0 and 12.1 branches all have the stagefright fixes. I did not look at anything any earlier than that for CM, and I can confirm that anything earlier in Omni than 5.1.1 will not have the fixes.
Click to expand...
Click to collapse
Some time between then and now (some time in September, I believe) the stagefright fixes were backported to the omni-4.4 branch. I have a build from this running on my relay right now and Zimperium gives it a clean bill of health.
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
kodimagnyl said:
I had sort of given up on "everything works" in one rom and changed when I got to annoyed. Especially issues with GPS, battery drain and hardware keyboard have been bugging me. However, I recently flashed the latest CM 11 nightly (after doing the 10.1 and modem dance) and now: everything works!!! Also customizing keyboard layout to danish ........
BW
Click to expand...
Click to collapse
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
i have a rooted stock rom, can i move to the latest cm11 nightly build?
phred14 said:
Do you have the files to do the 10.1 / modem dance? Do you have a way to share them?
I postponed doing it, and all of the links died. Subsequently, someone suggested that the GPS fix could be done with 10.2, which doesn't require a new modem, but I haven't tried that, and I thought that the old modem was an inherent part of the fix.
Thanks
Click to expand...
Click to collapse
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
kodimagnyl said:
https://stuff.mit.edu/afs/sipb/user...10.1/cm-10.1-20130305-UNOFFICIAL-apexqtmo.zip
http://junk.sandelman.ca/junk/r2s3/RelayMC5modem.zip
https://dl.dropbox.com/u/103520801/RelayLJ1modem.zip
LJ1modem is the old baseband....
Good luck
Click to expand...
Click to collapse
Can't reach the second link, but I've already got a copy of the current modem, the old one is what I've been missing. Things are starting to get busy, so I don't know how soon I'll be able to try it.
BTW, I've been told to do a "nandroid backup", then wipe and load the back-level stuff, do the GPS fix, then a "nandroid restore". I'm going to presume that the backup / restore doesn't handle the modem, and on my way back from back-level, I'll first have to use heimdall to reload the current modem?
Thanks
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
Official builds are out and can be found here...
https://download.cyanogenmod.org/?device=d850
I used the 6.0 micro build gapps from here
http://opengapps.org/
SupaAvenger79 said:
I am building this for my general use and thought it would be nice to share. Just to be clear I am not developing anything just making the builds. I dirty flashed over CM12.1 and flashed the latest GAPPS with no problems. Please do not report problems as this is a nightly build and unofficial.
I used the 6.0 micro build gapps from here
http://opengapps.org/
Nightly Build available here..
https://drive.google.com/folderview?id=0B4rZYkaJF5V0Z3RlR08yclZiVUE&usp=sharing
Click to expand...
Click to collapse
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
crash4fun said:
Thanks for sharing!
What is your experience so far with GPS locking & using Google Maps navigation?
Click to expand...
Click to collapse
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
[Thanks! Will definitely follow this until CM puts out an official build. Couple other guys that were building unofficial seem to have stopped for the time.
SupaAvenger79 said:
It's broke on my end. It can get a position lock but does not seem to track for driving directions. Another bug I discovered was trying to take a picture in a text message and the camera only showing 1 to 2 frames per second, but the regular camera works fine so I assume it has something to do with the text message app. I still use it as a daily driver don't use the driving directions often. I will keep posting the builds as I make them and let you know when that bug is fixed.
Click to expand...
Click to collapse
Ah, yes it appears to get a lock for me as well, but then won't navigate. I've tried messing with gps.conf in several different manners but no luck.
I'm about to abandon the G3 because there is no official CM support. This is where Cyanogenmod is getting bad press - they claim to offer an alternative OS with the latest updates, but some phones are just left in the dust because no one wants to be the maintainer. Best Buy has started selling the 6P - may head over and pick this up!
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
KennyG123 said:
Please post a link to the kernel source of the kernel included in your build as per GPLv2 and XDA requirements.
Thanks! And thanks for your contributions.
Click to expand...
Click to collapse
Sure thing
https://github.com/CyanogenMod/android_kernel_lge_g3
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
scsgoal31 said:
Still using this everyday but, as I'm sure you noticed, charging has been majorly borked since 12/23. Hope you keep this up and I'll be watching CM changelogs for a fix. GPS would be nice too!
Click to expand...
Click to collapse
Yeah I am hoping the problems are not D850 specific or we will never see a fix. I will keep posting builds semi nightly until CyanogenMod starts posting an official build or until I get a new phone in August. I really think this is still a good phone and wonder why the community went to hell on this one.
Have a Happy New Year everyone.
I've been using CM13 for almost a month and its been great. However I only just got an SD card for Christmas. Now, I'm assuming moving apps to the SD card has changed since it let's you format as internal storage now. However that doesn't work for me. Does anyone know how to move apps to the SD card without formatting it as internal storage?
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
slabity said:
How did you build this? I've managed to build CM13 for the D850 too, but the result was the phone freezing at the LG bootup logo. Your build seems to work perfectly fine.
Click to expand...
Click to collapse
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
https://source.android.com/source/initializing.html
Then I made a local manifest to include proprietary drivers from https://github.com/TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
SupaAvenger79 said:
Ummm well I don't know what you did wrong, but here are the resources I used...
Dependencies for the build were grabbed from this site
Then I made a local manifest to include proprietary drivers from TheMuppets along with the branch for the D850 out of cyanogenmod github. Hope that gives you some clues on what went wrong.
Click to expand...
Click to collapse
Strange. That's exactly what I did too.
I'll give it another shot and see what's going on. I'd like to take a crack at fixing some of the bugs.
Looks like tonight's build will fix the power charging issues. Yay!
Just posted the the 12/29 build and GPS is fixed we can now find our nearest Hardee's with ease. Thanks @invisiblek
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
xVermicide said:
is anyone else experiencing data loss constantly? I have to disable/re-enable data to get it to connect, otherwise I get (!) instead of (LTE). I haven't seen anyone else complain about this and yet it still hasn't been fixed on the 12/31/15 build. D850 stock CM kernel on T-Mobile, only one APN on my list. it happens on any CM13-based ROM.
also this new kernel makes my phone near flawless. it feels much more like a nexus. however it is still shutting down the phone when it overheats, hence when you first install the rom and it creates the cache, it will power off once the setup starts.
Sent from my LG-D850 using Tapatalk
Click to expand...
Click to collapse
I had data problems too on Tmo, a quick APN adjustment fixed it:
https://support.t-mobile.com/thread/95900?start=0&tstart=0
thanks, I applied the changes so I'll see if I have anymore problems. if not then this 13 is my new daily driver.
Sent from my LG-D850 using Tapatalk
Just flashed, great so far! Thanks OP!
Sent from my LG-D850 using Tapatalk