Database Info

Keyboard randomly freezes on DHD ROMs!

I have had no major problems with my Inspire 4G while on Inspire 4G ROMs (well... Stock, rooted stock, and Inspired Ace which is customized for the inspire.) On every DHD ROM I have installed, there seems to be a problem with touch input. When typing emails, searches, SMS, and other things random keys will just stop working! Sometimes I can tap them repeatedly and fix it while others you have to exit whatever app you are in and open it back up. It gets really annoying.
I am currently on CoreDroid, but have had this problem with TB Fusion, RCMixHD, and RCMix3D as well. Since Inspired Ace worked fine I tried flashing its HTC_IME.apk to see if this fixed the problem. It didn't. I seem to be the only one with these problems on the Inspire. Has anyone else noticed? Does anyone have any suggestions for what could cause these issues?
(Yes, I am aware of the problems flashing ime packages from other ROMs can cause, I was just trying to see if it fixed the problem. I had to backup zip ready to flash in case it caused FC problems...)
Thanks in advance guys!

I'm using leedroid and I have the same problems of random keys not working at random times.
Sent from my Inspire 4G using XDA Premium App

It's a driver issue with inspires iirc. No fix
Sent from my Inspire 4G using XDA App

1.18.12 said:
It's a driver issue with inspires iirc. No fix
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Wait so there is no possibility of ripping the drivers from stock and flashing or getting a kernel with them? And how come it worked on Inspired Ace? Did gtg465x get the driver issue fixed? Not trying to sound angry there just a bit perplexed since IA was dhd based....
Sent from my Desire HD using XDA App

Might be hardware than, I do remember it being brought up and it's unfixable.. I've had it happen on factory stock plenty of times. I just change my screen to horizontal and fixes it.
Sent from my Inspire 4G using XDA App

1.18.12 said:
Might be hardware than, I do remember it being brought up and it's unfixable.. I've had it happen on factory stock plenty of times. I just change my screen to horizontal and fixes it.
Sent from my Inspire 4G using XDA App
Click to expand...
Click to collapse
Hmm... Well mine never did that. Only failed to rotate a few times due to a few malfunctioning third party apps... If i find a fix I will post it.

I've had this as well and thought that maybe it was Better Keyboard having an issue with either the Inspire in general, or CoreDroid. So this is happening to others using the stock keyboard. Glad it's not just me.

Demented71 said:
I've had this as well and thought that maybe it was Better Keyboard having an issue with either the Inspire in general, or CoreDroid. So this is happening to others using the stock keyboard. Glad it's not just me.
Click to expand...
Click to collapse
No you aren't alone... I consulted gtg465x and he only edited a few things in /system/customize so I flashed the IA /system/customize/default.xml and it seems to have greatly improved. Noticed one of those such lags but it is not the one out of every hundred that it was. I typed this a few other things multiple sms one of which was long and only had to tap one key multiple times to get it to work. And only three taps at that!
If I further test it I will ask gtg for his permission and post the default.xml in a flashable zip.
Now all that is left to do is edit build.prop to make my phone say inspire not dhd then flash from mdj v21 to 23, calibrate battery for this ROM (grr... Coredroid updates wiped my battery stats while it was only at 63 percent charge during install) and then I can finally be happy and leave my phone exactly how it is! Yeah that will last all of what? A week maybe? Haha nah I am happy on coredroid!
Sent from my Desire HD (INSPIRE 4G!) using XDA App

I've had this happen to me on multiple ROM's and it always seems to be the "e" key that stops working for me. I just restart my phone or change input methods and it usually fixes it for a while.
Wish there was a permanant fix cause it does get annoying.

willwalk93 said:
No you aren't alone... I consulted gtg465x and he only edited a few things in /system/customize so I flashed the IA /system/customize/default.xml and it seems to have greatly improved. Noticed one of those such lags but it is not the one out of every hundred that it was. I typed this a few other things multiple sms one of which was long and only had to tap one key multiple times to get it to work. And only three taps at that!
If I further test it I will ask gtg for his permission and post the default.xml in a flashable zip.
Now all that is left to do is edit build.prop to make my phone say inspire not dhd then flash from mdj v21 to 23, calibrate battery for this ROM (grr... Coredroid updates wiped my battery stats while it was only at 63 percent charge during install) and then I can finally be happy and leave my phone exactly how it is! Yeah that will last all of what? A week maybe? Haha nah I am happy on coredroid!
Sent from my Desire HD (INSPIRE 4G!) using XDA App
Click to expand...
Click to collapse
According to my research, editing the build.prop file on Sense ROMS doesn't directly reflect what is listed in About Phone. It seems that you have to edit default.xml in /system/custom/CID.... before installing the ROM

Yeah I read the same thing.right after i posted that... Oh well! Maybe when I get bored enough to do it. And after further testing i concluded that changing the default.xml to disable some of the keyboard layouts and things as gtg465x did didn't really help all that much... On the bright side, i may just go back to inspired ace and use uot kitchen to customize it
Sent from my Inspire 4G using XDA App

So nobody has any other potential fixes for these freezes? Has it happened on every ROM you guys have used or what? I tried replacing my customize folder with the one from ia with cut down keyboard languages and layouts but no luck. Maybe we can find a fix!
EDIT: There may appear to be some confusion here. The problem in reference is not that the keyboard fails to rotate, gets stuck in landscape, or shows that a message is being typed and nothing appears on screen. The problem I am having here is that certain keys in random order at completely random times do not work but the keys around them do. This results in messages such as "Hey that bnd sunded relly gd" instead of "Hey that band sounded really good!!!" because the A and O ceased to function and likewise the exclamation point which is with the A. Also, at times the key will show it is being pressed but stops registering before the symbol it relates to is pressed. These problems exist on stock android keyboard and on sense keyboard. Hopefully someone will find a fix in drivers or something otherwise we will have to wait for a cracked official OTA GB update if that ever happens as they say it will...
Sent from my Desire HD using XDA App

BTT
I´m having the same issue, and it´s driving me crazy!!!
It´s weird, because I´ve had this phone for months, and had no problems, until a week ago.
I´m on Stock ROM BTW.

no solution? this is an on going problem and hard to ignore...

I have to agree with everyone here.. It is a pretty glaring flaw in the Inspire. And many people think that it barely happens.. But it is a problem that occurs for me at least 5 times a day and that is not an exaggeration. Everything that I have been reading does say that this is an impossible thing to fix.. Just a bit frustrating. Does anyone have a way that lessens this from occurring?

ive had this problem also for awhile. ive had it on every custom rom that i can think of. i used coredroid and cm7 for awhile. right now im using miui. ive tried 3-4 different keyboard at least, and had this problem with all of them. the keyboards accuracy also seems to decline. when switching to a new keyboard the problem initially goes away, but it eventually starts doing it again with the different keyboard.

finally! thanks you, guys. Finally I get support for a bug that supposedly didn't exist. I have been out of the rooting and ROM flashing game for a few months, as I got a new Inspire and never got the chance to root it. I finally caught a break from school work and got fed up with having to do battery pulls on the ATT stock ROM (terribly made, I must say. Sense froze daily.) I rooted and flashed the trusty old Inspired Ace and what do you know? flawless. as always. I flash the new coredroid 8.1 to see if the keyboard bug still persisted. For the first day, I had no problems. Then the freezes came back. I think it is very possibly a side effect of the undervolt kernel. As for those that say all phones are not created equally, and my processor just can't take the ROM, is that really likely on two phones in a row while the inspired ace ROM works flawlessly?
Edit: Also, for those that say stick to IA if it works, it hasn't been updated in a long long time and never will be since GTG465x moved to the Captivate

It's not that people don't beleive you, its just that this is not a common enough bug for it to be a software issue. It has to be a specific hardware malfunction. I have never had this problem on any Rom configuration that I have used. I have never seen it as a reported bug either.
Sent from my Inspire 4G Using XDA Premium

Good point... It just still doesn't make since since one DHD ROM didn't do it all yet others do. Coredroid I is not doing it nearly as severely cd6 did. So maybe there is hope that it is a fluke combination of hardware and software bugs rarely manifested.
Sent from my Inspire4G using XDA App

Bump
Well, in preparation for android 4 I decided to get used to AOSP ROMs since they will probably be more widely available than ICS Sense ROMs. After using cm7.1 for just two days, the bug is still there. Note that this is a different inspire than the thread was started on. Does anyone have any solutions? It just makes no sense that this bug does not occur for me on Inspired Ace or Stock but does on every other GB Rom I have tested. For everyone reading this with the urge to pop a comment at me like "Stupid, stick with IA if it works," that ROM has been abandoned since May 5, so it is outdated. Any hopes for ICS roms solving the problem?
Keyboard app is not the problem. Does it on touch input (sense ROMs), swiftkey X, swype, and android default keyboard.

GPS Problem

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.

How to upgrade the LG G2x P999 to Android 4.1.1 JB via CyanogenMod 10 (Unofficial)

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

[Q] [HELP] CM 9.1 intermittent crashes

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.

[Q] GPS and JB Roms issues

I am using AOKP rom, and my GPS is not working properly. The particular issue, however, is somewhat different from what I could find on this forum. In my case, the GPS cannot keep lock on the satellites for more than a couple of seconds. It can lock to 7-10 satellites quite quickly, but then it loses lock on them and then has to spend several seconds relocking. This cycle goes on while the GPS is being used. So, I can find my current position without a problem, but the lack of permanent lock makes it very hard to use navigation.
I have tried many "fixes" mostly dealing with gps.conf modification, but none of them could solve my short-lived lock problem. When I reverted back to stock Gingerbread, the GPS could keep lock without a problem, so I could track my continuous movements within 3 meters accuracy. I tried using gps.conf from Gingerbread in AOKP, but the problem was still there. So, I can only assume that the problem lies with the kernel itself.
So, my question is what 4.1.2 Jelly Bean kernel would you suggest me to try? I really like AOKP rom, but as far as kernel goes, I am open to any suggestions. I really want to be able to use the navigation again I would appreciate any inputs.

E107946 said:
I adeading AOKP rom, and my GPS is not working properly. The particular issue, however, is somewhat different from what I could find on this forum. In my case, the GPS cannot keep lock on the satellites for more than a couple of seconds. It can lock to 7-10 satellites quite quickly, but then it loses lock on them and then has to spend several seconds relocking. This cycle goes on while the GPS is being used. So, I can find my current position without a problem, but the lack of permanent lock makes it very hard to use navigation.
I have tried many "fixes" mostly dealing with gps.conf modification, but none of them could solve my short-lived lock problem. When I reverted back to stock Gingerbread, the GPS could keep lock without a problem, so I could track my continuous movements within 3 meters accuracy. I tried using gps.conf from Gingerbread in AOKP, but the problem was still there. So, I can only assume that the problem lies with the kernel itself.
So, my question is what 4.1.2 Jelly Bean kernel would you suggest me to try? I really like AOKP rom, but as far as kernel goes, I am open to any suggestions. I really want to be able to use the navigation again I would appreciate any inputs.
Click to expand...
Click to collapse
As development on 4.1.2 is dead, you could try a 4.3 rom since theres a few to try. If not i would simply revert back to gb. Idk how accurate you need it to be, but i use my navigation on carbon 4.3 without a hitch.

Well, anything you can suggest from 4.3 that would be as stable as AOKP 4.1.2? I have been using it for almost a year, so I can't really go back to GB. If it was not this GPS issue, I would be using my current 4.1.2 until I get a new phone. Just like I will be using Ubuntu 12.04 until I need to buy a new laptop

E107946 said:
Well, anything you can suggest from 4.3 that would be as stable as AOKP 4.1.2? I have been using it for almost a year, so I can't really go back to GB. If it was not this GPS issue, I would be using my current 4.1.2 until I get a new phone. Just like I will be using Ubuntu 12.04 until I need to buy a new laptop
Click to expand...
Click to collapse
These 4.3 ROMs are moving towards stable at tremendous speeds. Take your pick
I'm not saying they have no bugs at all, but I've been using 4.3 daily for about a month now with no serious issues
Sent from my SAMSUNG-SGH-T769 using XDA Premium 4 mobile app