I'm using CM7 Eaglesblood 2.8 with the T15 Trinity kernel.
My problem is that my GPS won't turn on after my phone has been on for a while. I'm not 100% sure after what exactly the GPS stops working, but so far every day I try to use it after my phone has been on for a day, this error occurs.
It works once I reboot, but I don't want to have to reboot my phone every time I wish to use my GPS.
Some details:
-the GPS is enabled, but the icon in the notification bar doesn't turn on when I am atttempting to use GPS
-I've attempted using a series of apps that use GPS and this behavior is consistent throughout all of them
-I've experienced the same issue on the newest CM7 Hellfire ROM with the faux SV and OC/UV 048 kernels which makes me think this is an issue with CM7 or the G2X
-I've used GPS status and it produced no results
-I've searched this error through both your forum search and Google. Google produced some results, but none of them helped
So my question, or rather request, is to know whether or not I'm the only one having this problem. I use my GPS a lot, so this is very annoying. Also if someone was having this problem, I'd like to know how they fixed it (and also if they didn't)
GPS is properly fixed in 21y firmware the stock 2.3.4 release, but that means no custom roms.
Sent from my LG-P999 using XDA
Hmm okay, thanks. Well in any case, I have a custom ROM which I rather use than the stock. Is there a solution available for CM7 users?
Possibly unrelated, but yesterday my GPS started becoming inaccurate as well as malfunctional. I haven't changed anything, so I'm thinking it's similar to when data is slow some days. If that's the case, it'll fix itself over time.
The original problem still remains, however. Right now I'm under the impression that this is a problem that doesn't have a solution.
I had nothing but trouble with GPS on my G2X. I even exchanged the phone twice in an attempt to get one with a decent GPS. All the symptoms you describe would occur on my phone. Sometimes I'd have to do multiple reboots to get it working again. Since I updated the baseband last week it's been working much, much better.
I miss running CM, and I hope that devs will find a way to make custom ROMs work with the new baseband, but I'd rather have a working phone than a custom ROM. In addition to the GPS issue, my random lock-ups haven't appeared yet either. Granted I haven't had this update on my phone a full week yet, so I can't be certain that it's fixed all the problems yet.
Related
Good morning guys,
I've tried every 'fix' under the sun to make my GPS work 'better' (takes 5 minutes to lock my loc), but to no avail.
(I'm on Scott's amazing CM10 JB rom)
Is every JB rom having these issues? Would it be better to just goto ICS?
I travel for work, so Maps is my best friend lol
Thanks in advance,
Sent from my SGH-I997 using xda app-developers app
Scotts latest CM10 initial locked for me in 1 minute 24 seconds.
So, GPS isn't broken across the board. Sometimes there are issues, and sometimes it works fine, but by and large, the issues are local to the individual user.
If GPS is that important, I would suggest that you go back to stock and work your way up. Or just stick with stock.
Understand a solution is important, however not a good idea to create duplicate threads.
http://forum.xda-developers.com/showthread.php?t=1902360
I love the work scott has done, and i realize it isn't across the board. It just stinks that I can't use his masterpiece as a daily driver
Sent from my SGH-I997 using xda app-developers app
use cm9. every jb rom on this phone has issues with agps. weird thing is it is running but not helping to find sats. with gps.conf mods even the "use ref loc" feature seems to work which is network triangulation to help it figure out a rough location for a starting point but the phone still seems to use the standalone gps to find sats.... i tried logging it but nothing really gave me a clue to the actual problem. the gps isn't broken but it doesn't work so well for most of us without agps working to it's full potential.
It works well in ICS. Currently running cm and GPS locks in less than a minute.
In jb it would take 20+ minutes and sometimes say I was a mile away.
GPS has always been bad as far as I'm concerned. I've actually had better luck with the JB roms from late August onward than I have with Froyo or Gingerbread. Have you actually been able to rely on GPS for directions with this phone? I always end up having to ask at a gas station!
brian Marshall said:
It works well in ICS. Currently running cm and GPS locks in less than a minute.
In jb it would take 20+ minutes and sometimes say I was a mile away.
Click to expand...
Click to collapse
Turn off Google location. It might be nice to have Google now but its the worst for navigation. You need real GPS location for maps. Problem is that with jb agps doesn't work correctly so the GPS lock takes forever, leave GPS on with the screen on for another 15 minutes after the first loc for the ephemeris data to download. that should last a few days before you have to do it again.
ICS on the other hand has absolutely impeccable GPS performance for me. Much better than what came from Samsung on my phone.
Cypher rom
I used Cypher rom, and it has great GPS lock.
atrix4nag said:
I used Cypher rom, and it has great GPS lock.
Click to expand...
Click to collapse
first of all, i appreciate that GPS works fine for some people -- why are you reading this thread then?
i'm not even going to list everything i've done to troubleshoot, but before you say 'people posting things and not checking it out themselves' i can tell you that i have tried EVERYTHING, spent hours working on the GPS issue with my phone and come to the conclusion that JB does not have proper GPS on SOME infuse phones, whether it be by region or some latent hardware defect that the ICS or GB roms compensate for, my GPS dosen't lock. i've been through like 20 gps.conf files, read about every setting in the file and tried every variation thereof, gone back to GB, gone to ICS, back to JB, multiple times, testing the result, my phone locks in 5 seconds in ICS or GB, not in JB. had same results in cm10, cypher, remICS, th3bills aokp, his miui, etc...
if my hardware was bad, i wouldnt lock in 5 seconds in GB.
one of my pet peeves is everytime you ask a question in a forum being told you're in the wrong thread when it would have taken less time to provide a helpful answer. posts telling people to move to another forum are also noise, and then further posts telling people they didn't try hard enough, or 'mine works so you're wrong' are also just noise, and not helpful to anyone. the other pet peeve is being told, after spending hours working on an issue, to stop whining because it's being worked on, when you were just trying to help in the first place. or when you read the first sentence of my post and tell me to do something i clearly stated i had already tried in my post.
nobody is whining, we just use infuse phones, and like our GPS to work.
also to be clear this isnt really directed at atrix4nag in a negative way, i just happened to reply to his message.
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
rpod83 said:
A while ago I rooted my AT&T HTC Inspire and put on Cyanogenmod 7.2.0, and things are all working quite well except the GPS. However, extensive googling and I've not been able to find something that exactly matches my symptoms. It always camps quickly, that's no problem. When it is connected, things seem fine and fast. However, each time I start driving navigation, after about 5 mins it loses the GPS signal and won't recover on its own. It will recover if I turn off the GPS and turn it back on. At that point we're back to normal but eventually it will happen again and it's quite annoying and unsafe to have to toggle the radio to keep navigation going.
I have tried several combinations of the RILs/Radio software found here: http://forum.xda-developers.com/showthread.php?t=1106324
However, there is never a behavior change. It is beginning to make me think maybe the problem is not with my radio software. Is there any kind of middleware as part of the ROM which may be causing this? Can anyone think of a way to troubleshoot bad hardware? I wonder if it is possible my baseband hardware was damaged through the modding process?
Thanks!
Click to expand...
Click to collapse
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
MagicalHobo said:
I believe that this is just a bug with the Navigation app on Cyanogenmod 7.x ROMs. It happened to me on every CM7 ROM I ran and I remember reading that it was the Navigation app's fault. But it's a normal bug, nothing should be damaged hardware-wise unless this happens on Sense or ICS ROMs that don't have documented cases of this issue.
Click to expand...
Click to collapse
Thanks, MagicalHobo. Did you ever try a different ROM with success?
rpod83 said:
Thanks, MagicalHobo. Did you ever try a different ROM with success?
Click to expand...
Click to collapse
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Please post all questions in the Q & A section. Thanks! Thread moved.
Sent from my Galaxy Nexus using Tapatalk 2
biglittlegato said:
This is a common problem on AOSP ICS roms as well. I have read it is fixed on aospx, but the rom was too vanilla for me to keep it long enough to test.
As for Gingerbread, I can tell you that Navigation works perfectly on all ClearDroid roms as well as Virtuous Unity through 2.35, I can't remember using Nav on Gingerbeast.
Sent using the power of the dark side.
Click to expand...
Click to collapse
From my experience, GPS works perfectly on aospx.
Hi All!
Recently, while surfing through the ocean of ROMs for my LG G2X P999, I came across this ROM. Couldn't find any link related to this on XDA. So thought of pointing the G2X owners to this link:
http://www.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536/
Flashed it just yesterday. Apart from the Video-recording did not notice any bugs so far. In fact I haven't used it enough to comment on bugs. But I can confirm that Calls and Wifi are both working fine.
If any one knows any prior publication of this work on XDA; please let me know so we can avoid duplicates.
Hackfest in development section.
Sent from my LG-P999 using xda premium
Wifi calling probably does not work
Sent from my LG-P999 using xda premium
Pain-N-Panic said:
Wifi calling probably does not work
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
It doesn't,
I can't get it to work on anything that is not CM7 based.
Kinda blows that our phone is limited to cm7. I love cm7 as it is treating me well, but selection is always a nice privilege
Sent from my LG-P999 using xda premium
nagenderjeet said:
Hi All!
Recently, while surfing through the ocean of ROMs for my LG G2X P999, I came across this ROM. Couldn't find any link related to this on XDA. So thought of pointing the G2X owners to this link:
http://www.androidauthority.com/g2x-p999-t-mobile-cyanogenmod-10-cm10-unofficial-115536/
Flashed it just yesterday. Apart from the Video-recording did not notice any bugs so far. In fact I haven't used it enough to comment on bugs. But I can confirm that Calls and Wifi are both working fine.
If any one knows any prior publication of this work on XDA; please let me know so we can avoid duplicates.
Click to expand...
Click to collapse
so data is working? i thought the data or radio was still broken. does this mean we may get a somewhat stable build of JB?
Still a hackfest.
Sent from my LG-P999
Pain-N-Panic said:
Kinda blows that our phone is limited to cm7. I love cm7 as it is treating me well, but selection is always a nice privilege
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Spawne32 said:
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Click to expand...
Click to collapse
Well the problem is that other developers take the vanilla cm7 code and tweak/mod the hell out of it which is always awesome but they put out an unstable build/ROM. If you haven't tried vanilla CM7.2 from get.cm (latest build) then you're missing out. I have had the ROM installed running with mazout's latest kernel for over a week now and its been running extremely well. All and any problems that I experienced with this setup were directly due to ignorance and human error as I'm still a flaming n00b. At the same time they were great learning experiences and easily fixed.
Spawne32 said:
I tried a couple different versions of CM7 over the past few days, and its nothing but a nightmare. It will run flawlessly for hours and then something quirky will happen and I either cant get data, or cant make calls, or my screen locks up, and im rebooting the phone or looking for a fix on google. Wound up just going back to the stock rom with faux123 kernel.
Click to expand...
Click to collapse
The problem is going to lie in your setup somewhere.
Maybe kernel level as it is known that some G2xs will run great on Trinity but crash on Faux and vice versa. That's just a quick example.
I've run vanilla CM7 for like 13 months now and do not encounter the issues you are describing.
Soooo...what's your setup.
ROM w/build date
Kernel and version
Baseband date
Sent from my LG-P999 using xda premium
Data does work
joker550 said:
so data is working? i thought the data or radio was still broken. does this mean we may get a somewhat stable build of JB?
Click to expand...
Click to collapse
Data does work but there is issue related to rapid battery drain. Back to my stock ROM. This hasn't been updated since a long time. I wonder if any developer at all is working on this phone or not!
nagenderjeet said:
Data does work but there is issue related to rapid battery drain. Back to my stock ROM. This hasn't been updated since a long time. I wonder if any developer at all is working on this phone or not!
Click to expand...
Click to collapse
You are late to the party... This device is a dying device. There's 1 dev working on a CM7 Kernel and that's about it. More than likely we will never see fully working 4.1.1 or higher on our device. They tried real hard and are some talented people (our devs), but LG handed them a broken pile of excrement and said, "here you go... Jellybeans!!"...
New2my8125 said:
You are late to the party... This device is a dying device. There's 1 dev working on a CM7 Kernel and that's about it. More than likely we will never see fully working 4.1.1 or higher on our device. They tried real hard and are some talented people (our devs), but LG handed them a broken pile of excrement and said, "here you go... Jellybeans!!"...
Click to expand...
Click to collapse
That's almost all true! I have another old phone, Mytouch4g/HTC Glacier. On that one I am running 4.2.2 and there is a lot of development still on. Huge number of ROMs which can be used as daily drivers. But here we don't even have a perfectly working 4.0.4. But again, no complain to Developers. they have tried really hard with a lot of time invested in this device. All the blame on LG.
This phone is lightning fast on 2.3.X variants. still very much usable. I may be late to the party, but the party is yet not over
I just want to chime in that I used this and the phone is working. The camera seems slower (and therefore more blurry). Other than that everything that I use (I do not use bluetooth, tethering, or wi-fi calling) is working. It's about the same speed as CM7 I had on here before. Don't know about battery since I only just did it.
If anyone knows any tricks for the camera please share. I babysit a toddler and his face is often blurry in photos. I'm pretty sure with this new ROM it will be even more blurred. I have already removed the plastic cover over the camera lens, it's not that issue. This is clearly software as it has gotten slower with this ROM.
We thought we might have a jellybean breakthrough when cm started deving cm10.1 on the p990 and had the courtesy of posting a half port of their work in progress. I believe it's called AdamPK's cm10.1 and is usually found with Mazout360 kernel. Hardware Acceleration Work so no camera, camcorder, sluggish or other problems that plagued the hackfests but they ran into and issue with the radio because O2x and G2x use different radio chips. So you have wifi but no data and battery can't be read correctly but other than that it would be as close to a perfect 4.x as we could get.
http://forum.xda-developers.com/showthread.php?t=1977573
Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Wipster said:
Hi all,
I am using CM 9.1 on my HTC Sensation (pyramid), and recently the device has been intermittently crashing to power off.
Here are some details on the software.
Android version: 4.0.4
Kernel: 3.0.36
Baseband: 11.69.3504.00U_11.22.3504.07_M
The crashes can happen in waves, so it powers off I power it on and it boots and I can get to unlock the phone then it crashes again. However it can happen randomly during operation as well, generally after unlocking and might be linked to lack of GSM signal but I cant confirm this.
The crashes do not seem to happen if the device is plugged in, and as the crash is like a battery pull I thought possibly dodgy connection however no amount of shaking and pressing or twisting can trigger it.
I have logcat in *:V and nothing is ejected that looks suspect, it just ends.
I have also logged kmsg, which ended up being huge but doesn't end at any spectacular failure.
My next step if we cant find anything up with software will be to load stock HTC back on and see if the problem is still apparent.
Anyone seen anything like this?
Click to expand...
Click to collapse
There are people who report crashes when phone connects to GSM instead of WCDMA, you can lock your phone to WCDMA Only on the testing menu (dial *#*#4636#*#* and go to "Phone information").
Also, changing ROM might help. there is officialy built CM10, and CM10.1 is quite stable (I'm using it myself as a daily driver for a month now). Also there are many Sense ROMs which are very stable.
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Wipster said:
Hi Thanks for replying,
I shall try that however in the UK the signal is pretty poor in my area so I'm not sure how usable it will be, it seems to crash at the end of a call pretty reliably now, here is another kmsg there appears to be a raft of kernel Oops's prior to the end of the log.
Click to expand...
Click to collapse
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
astar26 said:
I do not know how to read a kmsg so I can't help you there, but did you try my advice? Also, you can flash another kernel from the Android Development forum, just find one to your liking that works with CM ICS.
Click to expand...
Click to collapse
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Wipster said:
I did indeed try locking to WCDMA only, however this rendered my phone useless in most of my common locations with no service. So I turned it back, I am able to connect to a GSM network alright.
I have just updated to a nightly of CM10, as there are no stables yet for my phone. The kernel still warns about a stuck clock so there is still an underlying bug in the kernel there or hardware fault, which I will look into. And so far so good, no crashes however I havnt used it much, time will tell.
Thanks
Click to expand...
Click to collapse
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
astar26 said:
Glad to help. The kanged 10.1 is quite stable (available in the Android Development forum), you could use that. There are also more kernels available, that might work well.
Click to expand...
Click to collapse
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Wipster said:
Well unfortunatly CM10 crashes just as much, and its looking more like its signal related. I was in a place with either very poor or 0 signal and it was constantly crashing after boot, presumably searching for network.
Maybe its the radio and RIL? I would like to avoid changing these parts though if at all possible.
Edit: Attached is the kmsg for CM10 at a crash.
Click to expand...
Click to collapse
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
astar26 said:
It's probably not RIL. Since the ICS update different RILs don't seem to matter (they work well for all radios). for example - two days ago I changed my radio - and it worked just fine without any further modifications.
You said you used CM10, but did you use albinoman's CM10.1? both ROMs you tried basically use the same kernel (from cyanogenmod), and downloaded from the same site (unless you use a Kang and I'm wrong). even sense ROMs, just to rule out kernel problems.
Click to expand...
Click to collapse
It was stock CM9 and CM10 I have tried, no other kernels.
With the CM10 image, can I just install a kernel from another ROM and it 'work' or do I need to change roms over to test?
I upgraded the radio (11.76A.3504.00U_11.24A.3504.31_M) using the latest RUU and then plopped my CM10 backup back on and so far so good, signal seems better however I'm sure that's placebo, will keep you posted.
Edit: OK so upgrading the radio did nothing whatsoever. Still crashing.
Attached is a nice crash, stops at msm_pm_power_collapse something to do with shutting down CPU, maybe for clock change, I have changed the minimum clock freq to 384Mhz just in case mine is a device which cant do 192mhz.
Just tried Albinomans ROM and its still crashing.
Attached is the kmsg and the logcat in verbose mode.
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