Database Develop

[ROM Feedback] CM 6.0.2 (09/05/10)

To my knowledge, there is no thread dedicated to the new numerical releases of CM. Let us start with the newest, CM 6.0.2.
Please post your anecdotal data, including benchmarking scores, bugs, and glowing experiences. Perhaps this will serve as an unofficial repository for issues that prove consistent.
Note: After modifying my WiFi settings, specifically disabling sleep mode while the screen is off, I've encountered no related instability.
Mail FC Fix: http://forum.xda-developers.com/attachment.php?attachmentid=394316&d=1283500340
Systemic issues yet to be addressed:
-LEDs do not work save for charging
-Outgoing calls initially drop before reconnecting
-Lockups or reboots, likely stemming from SetCPU
-OS does not recognize internal storage

Does this version fix the wifi not staying on?

Did you change your settings to Never sleep for wifi and just left the wifi on? Thanks...I want to try different settings and see if I can eliminate reboots/shut downs.

are we waiting for the nightly for the newest fixes like LEDs or is there gonna be a new release like .3?

OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.

not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.

seanmcd72 said:
OP you are a month behind (it's 9/3 not 8/3)
After fixing the mail fc, this rom is very stable except for one lingering issue. I guess it might be wifi related. I went all day without any issues with wifi on constantly (and bt) but when I left work (and seemingly as soon as I got out of wifi range) the phone was locked up with nothing on the screen, unresponsive. I had to pull the battery. This has happened since RC3 for me. I am going to try it without wifi over the weekend. Otherwise, BT streaming adio now works perfect, and the internal memory gets scanned for pics/images. I'm going to keep running it though as this wifi bug should be fixed soon.
Click to expand...
Click to collapse
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I would have to second the issue with SetCPU. As soon as I overclocked it and began using the rom I noticed the phone would get hot abnormally fast and would reboot a few times within the first few hours. Not sure what is going on here as it worked fine on the RC.

Fuzzy_Dunlop said:
Yes, there definitely is still issues with wifi. The issue seems to be exacerbated when running SetCPU with a profile that underclocks when the screen is turned off. Since I've stopped using SetCPU I havent had a single freeze, although I might have just gotten lucky so far.
SetCPU will not run at startup for me, even with the option checked to start at boot. I had to set Tasker to run it at boot as a workaround.
When phone is in Airplane mode I still am able to recieve text messages.
Click to expand...
Click to collapse
I didn't even notice setcpu till you said that. Phone was back to 998mhz
Sent from my INCREDIBLE using XDA app

My phone doesn't vibrate when I receive an incoming call when the phone is set to vibrate.

Has anyone else noticed the keyboard lag when using the Messaging app? Browser and this xda app seem to work fine with no lag..
Other than that, smooth.

dnoyeb said:
not to mention we're commenting on it in the more official thread posted up by the author of the rom .
http://forum.xda-developers.com/showthread.php?t=755690&page=111
however just to say it.. so far its running quite well, I found a correlation between wifi and BT causing issues with each other... commented on it in the other main thread after some extensive testing today.
Click to expand...
Click to collapse
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.

Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).

I get random reboots and freezes every thirty minutes if so on a fresh wipe of 6.0.3 I tried with setcpu and without but always with the built in hotspot running. Same issue since RC3

LED notifications dont work. LauncherPro Plus FCs on every reboot, other then those things im good with it, great wallpapers , great rom

Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...

Panda Fuzz said:
Battery life is terrible compared to sky raider with king kernel. Once we get some real kernels for this rom it should be better...
Click to expand...
Click to collapse
And you know the issue is the kernel because...?

mp3sum said:
I believe the thread referenced by you refers to RC3, whereas I am specifically looking for feedback on the newest numerical releases of CM 6 for the incredible.
Click to expand...
Click to collapse
actually if you read the thread, you'll see koush himself is in there dealing with 6.0.2, offering up kernels and fixes...
he just hasn't updated the topic title.

Okay this may be a stupid question but how do I apply the mail fix?

mp3sum said:
Update: leaving battery percentage at 91 before bed with system panel running, will see whats eating up the most juice. So far stable n fast with no issues (except LCDs).
Click to expand...
Click to collapse
Battery life was down to 81% 11 hours later, and the phone had been placed in Airplane mode while running Gentle Alarm and a few widgets (no auto task killer).
Breakdown:
System 0.6%
System Processes 0.3%
System Panel 0.3%
android.process.acore 0.1%
Plus several honorable mentions with 0.0%. I have yet to perform this experiment with Ruby or ID.

JAC kernel bug: using audio randomly kills phone

(I figured to post this in Android Development as it wasn't really a fit for any other forum; and made its own thread since multiple ROMs and threads use non-stock kernels.)
I ran into an issue running JAC's OC/UV kernel, as detailed at http://forum.xda-developers.com/showthread.php?t=806116 . Essentially, whenever any kind of audio was playing, whether through headphones or the speaker, local media (i.e. mp3 player) or remote (i.e., Pandora), at some point the phone would just.. die. Capacitive buttons wouldn't light up, no unlock; music would die; and basically a battery pull was required to turn the phone back on. adb logcat reports nothing - you can see the audio streaming, then the logcat shut off with the phone.
Based on the thread above (and searching the Bionix thread), it seems that a non-stock kernel does this. (There are only a couple of posts out of the thousands on Bionix's thread.) I have not tested KingKlick's kernel, only JAC's; perhaps KK doesn't suffer from this. This issue is independent of overclocking/underclocking the phone (verified by setting JAC kernel to 1000/200, then uninstalling setcpu); Voodoo lagfix (verified by disabling lagfix and running audio for about an hour); and ROM (tested using multiple versions of Franken-Twiz and Hybrid - maybe there's an inherent issue with eugene's mods, but I haven't seen any other posts.)
I suppose this thread serves as a warning/bug report for anyone that might encounter this issue if running a non-stock kernel. The best way to resolve AFAIK is to revert to a stock kernel.

Thank you for posting this! My phone had suffered from this at random times since I started using JAC's kernel. I asked about it in a couple of threads but never got a single reply. Glad to know it's not only me

I'm running the same kernal and about 20 minutes ago running pandora my phone just turned off too and had to pull the battery to restart
Sent from bionix 1.9.1 jacs oc/uv kernel

Had that issue at the Gym the other day, not even on Bionix.

I had similar issues, also with the KK Kernel, its not just JAC's kernel. You don't have to pull the battery either to get out of the freeze, you can hold the power button for several seconds and it does a hard reset.
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Just a little work around, try it to see if it works for you.
Sent from my SGH-T959 using XDA App

Actually this is a known problem since even the G1.
If you have anything like setCPU, which I do, and you set the idle or lowest speed lower then 400 Mhz the phone will more then likely freeze up when playing music or when going to idle.
I don't remember off the top of my head what causes it to do this when it goes below that certain Mhz, but Im sure I or someone here can dig the old thread up.

Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App

Ive had this problem to.... but it was ONLY with Jacs 1.1, I revert every ROM back to his 1.0 and have no problems. Everytime I dont, I get a phone freeze.

I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys

jmercil said:
I have found though that the KK Kernel is less likely to do it if you set your setcpu to 400 min and 1000 max before using pandora. Those settings seems to have worked for me every time..also after setting up pandora make sure to fix permissions with rom manager.
Click to expand...
Click to collapse
Interesting. I'll try installing JAC OC/UV/Voodoo again and see if this observation is consistent.

r6kid said:
I was having this problem with jac's newest kernel so I went back to his first OC/UV, it is a known problem and he's working on it according to his twitter. how I got around this is I used his OC script and got rid of setcpu, from what Quadrant says I'm still running 100/1200. Hope that helps you guys
Click to expand...
Click to collapse
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.

Would have to agree. There's a bug somewhere. Not sure if its limited to jacs though.
Currently on masters rom kk. Only problem is pandora.

i had this problem too. kinda disappointed cause the kernels make everything run so much better. so i had to go back to using stock cause i listen to music a lot :/

There's definitely some hardware variability, because I can't recreate this bug. I listen to music all day long (MixZing, Slacker, Pandora) running 1.8 w/ JAC's OC/UV Voodoo. Never seen this.

Likewise with Jacs 1.1, had a couple other weird issues running that specific kernel too, not a single problem when I flashed back to 1.0
Sent from my T959 running Bionix1.9 with Jacs OC/UV and Voodoo

i get this same thing. ive had it happen with SetCPU both installed and not. right in the middle of a good song bam phone just shuts up. walk over to my toolbox and sure enough the phone is in a state of being divided by zero and only a battery pull lets it return to the world of the living. not greally a good thing when i have sevearl iphone dorks in the shop and they pop on over to my speakers and they say out of the way lets plug in a REAL phone. makes me want to scream LOL. ****ing iphone >_<
i retort with soooo when you get it out of the box....thats it right? nothing can be changed right? oh look that program sucks....what you cant make your own? ...yea...i thought so. hey look im making a call in the scrap room surrounded by 4ft thick concrete walls.... i got full bars lol. they got nothing in the empty parking lot cuz there holding it wrong LOL

Blkegk said:
Man without this thread I could never get pandora to work with a custom kernal. I setcpu at 400 min and 1000 max and not a single freeze. Thanks so much for posting that tip, you made my day.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Glad it worked for ya!
Sent from SGSV Bionix 1.9.1 KK OC/UV with the quickness!

sxfx said:
Yeah, I think the problem only exists when you use the OC kernel with setCPU, and setup setCPU under 400Mhz, other wise the kernel with out setCPU works just fine when it goes below 400Mhz.
Once again I don't remember why it does that but it has something to do with setCPU not being able to initialize properly after the phone goes idle and falls below 400Mhz.
Click to expand...
Click to collapse
I tried that though, as you can see in the thread I linked to above. Uninstalling SetCPU didn't help..

I think it's hardware.... One of the unlucky ones....

Try with a stock kernel. Jac and kk kernels do uv by default, which is like overclocking in reverse. It has the same possible stability issues.

[Q] Why does my hero keep restarting? (Gingerbread 2.3.2 aosp)

It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!

If your using the stock kernel I think its overclocked to 768 not sure though. Try one of dec's 691 kernel the #589 is my recommendation. Hope it helps good luck.
Root-Hack-Mod-Always™

jlopez512 said:
It always restarts automatically, when i make a call, the call just freezes and when i turn the phone on from standby to see what happen, well you guessed it, it restarts! its pretty annoying i went through 2 batteries today in 8 hours, because of the restarts. please help!
Click to expand...
Click to collapse
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!

runngwlf said:
There could be a lot of things happening. The most common is that your running a clock speed higher than that which your phone can handle. Not all heros are created equal, mine for instance starts rebooting at anything higher than 691. Try a different kernel or if using setcpu or over clocking widget to lower your upper end clock speed. Your phone freezing when coming out of standby can mean your lower clock speed is too low. ASOPGB has JIT enabled by default as well. Go into the settings and turn it off, then reboot. You will just have to play until you find out what works for you. Good luck!
Click to expand...
Click to collapse
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass

il Duce said:
Set cpu or similar will not fix the issue, laie was right a capped 691 kernel is needed and probably a capped recovery as well. Btw jit is no longer default in gb, and jit would not cause reboots anyway.
sent from my hero, which no longer sucks ass
Click to expand...
Click to collapse
Ahh thanks for the info, I had not gotten through all the new posts on the other ASOP GB threads. Good to know though. I have no tried out the rom, I plan to this weekend and my phone does NOT like kernels that clock above 691.

[Kernel] Dragon TEST... SetCPU profiles support...

http://www.tabbal.net/files/Dragon-Kernel-Voodoo-OC-v3.3-T1.zip
Dragon 3.2 w/ a fix that seems to work for setCPU screen off profiles setting the CPU to low values. Please note: The max freq in setCPU for that profile is what will be used, no scaling. I set it to 200Mhz and it's working fine every time I fire it back up.
The original patch is from here: https://review.source.android.com//#change,20804
Created by coolbho3k for the Nexus S, I backported it to Froyo. If we get good test reports from others, I'll push the changes to github tomorrow so other devs can use it.
When testing, please either use known good OC/UV settings, or don't OC/UV at all. Phantom OC/UV crashes won't help us know if this is working well for others. I've tested it with and without, turning my phone on/off like a madman... working fine so far.
Hmmm... early reports aren't looking good. Perhaps something isn't quite right. lol... Be warned if you try it, read all the comments. Might have to declare this one a fail. Too bad the NS cpu-freq driver is so different.. maybe I'll try pulling the whole thing over..

Downloading now report back tomorrow! This sounds promising.
Sent from my SGH-T959 using XDA App

Will test as soon as i get mine back to stock! Its just what I felt like doing today.
I did have a question..
Do we need to adjust it to say.. performance,on demand powersave? or will it just default?

just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots

coolkid893 said:
just flashed it on my phone its been running warm hot even then after about 10 15mins of running it reboots
Click to expand...
Click to collapse
wow that can't be good. Sounds like the phone is overheating..

PaiPiePia said:
wow that can't be good. Sounds like the phone is overheating..
Click to expand...
Click to collapse
ya i know an its not even o/c its set to only max at 800mhz lol i think im gonna reflash to 3.2 to be safe but its a step in the right direction good try

Ok Im gunna have to try and install setcpu first.. otherwise my phone loads and restarts a few minutes into being on the desktop.

Testing now, Just UV'ed my clocks, and now setting profiles.

Observation so far:
SetCPU, and Uvolting seems to lock up my phone, and cause a reboot, and phone is pretty warm/hot.

Confirmed I can not run this either.

Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App

junxracr said:
Couldn't use it. Phone would shut off as soon as scanning started. Kept happening everytime I tried to start phone :¬( going back to 3.2 has been stable at 1.4 ghz.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Im having better luck using profiles with 3.2 than with this one. I've been using set cpu since 3.2 came out with no problems @1.4 and on powersave when screen is off. I have made no changes to the UV settings.

yikes ! i smell quadrant score in few min lemme install it

Has anyone got a "kernel panic" on this before? I'm not sure what I could have done wrong.. had to Odin back to stock. Forgot to back up before I flashed, shame on me. lol.

kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D

bartek25 said:
kernel panic wipes your data ? everytime kernel panicked on me i just restarted =D
Click to expand...
Click to collapse
Nah, it didn't wipe my data. I had to Odin back to stock because I couldn't go into Clockwork Mod Recovery Mode. It would go into Kernel Panic and it reset all my launcher settings....

Was running hot for me also. Back to stock and then to bionix .
I think that when you get things fine tuned you will have a great Kernal.

GPS fix files for ICS roms

This is not my work.
Found these cwm flashable files in the Experia ROM thread, and since I've tried about everything possible to fix the GPS death after deep sleep, I figured I'd try flashing these before going back to froyo and a consistently reliable GPS fix.
Well, they worked for me. I'm currently on slim 3.1, subzero's build 34 kernel as the stock kernel didn't work for me after deep sleep. It has worked for others, but even if it did work for me, I can't live without voodoo sound, and that doesn't work on stock kernels. Plus you can undervolt with something like subzero's kernels which extends battery life.
I was never even able to get a lock before on slim, but after flashing and rebooting I locked 10 birds in 20 seconds. After a 25 minute deep sleep (93% according to CPU spy) I was able to lock again albeit it took about 40 seconds.
Thought I'd post these since so many others have same issues.
Credit goes to the dude (kchau15) in the experia rom dev.
Files:
http://db.tt/K8r6SZNQ - Yag2
http://www.mediafire.com/?7wjfloa7lfih43d - Experia Files
http://db.tt/ykBYNwL9 - ultimate cleaning script
UPDATE : Seems these work well on latest subzero kernels also - tested v26 and v34 and v80.. I'm using v80 with consistent results on AOKP 35. Initial lock is very fast under 10 seconds, subsequent locks after deep sleep is 40-60 seconds but will always find it, just a little more patience.
Best results when you flash the ultimate kernel cleaning script in recovery before installing a new kernel, then allow phone to boot normally before rebooting back to the recovery and flashing the GPS files. Yaggf2 first and then experia before rebooting phone normally.

Thanks I'll try this out on my wife's Vibrant later and report back. Right now it's running teamhacksung's CM9 with the Glitch kernel and the full yagf2 change. Initial GPS locking is incredibly fast since yagf2 but deep sleep still kills the GPS.
Update: Nope. Still lose GPS once the Vibrant going into deep sleep. Using Icy Glitch V14B5, I'll have to try another kernel.
Update 2: Works now after switching to the Kiss 2.2 kernel.

I decided to change modem from kb1 to ka6 and had to flash both the yag and then the experia fix one after the other before rebooting , and still working after deep sleep! Been 3 hours since last used and locked within 30 seconds!

I'll give this a try and report back shortly.
Update: Was unsuccessful on CM9 alpha build 17, stock kernel. Would not lock after deep sleep (verified sleep with cpu spy).

what were your steps to install it?
Sent from my SGH-T959 using XDA

I took a close look at these GPS files and they are the exact same GPS files as ICZen v1.3 except for the gps.xml. I tested these GPS files with ICZen v1.3 and the SubZero Build#21 with voodoo color and the GPS still doesn't lock after deep sleep. The GPS not locking after deep sleep has to be kernel related if the stock ICS Slim v2.8 kernel locks after deep sleep and no other kernel except Kiss v2.2 will lock after deep sleep. I just tested the the stock ICS Slim v2.8 on ICZen v1.3 and the sure enough after 30 seconds or so the GPS locks perfect after deep sleep with 7-9m accuracy just like before deep sleep. Now hopefully MP can figure out what code in the Slim ICS kernel is different then his SubZero kernel code and fix GPS after deep sleep for good!

I couldn't get the gps symbol to appear, let alone have working gps on ics. I tried it and not only did my gps symbol appear, I got a lock in 30 sec. Thanks for sharing. Using icssgs rom btw.
Sent from my SGH-T959 using xda premium

kobesabi said:
what were your steps to install it?
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
simply flash the file

hurtz777 said:
I took a close look at these GPS files and they are the exact same GPS files as ICZen v1.3 except for the gps.xml. I tested these GPS files with ICZen v1.3 and the SubZero Build#21 with voodoo color and the GPS still doesn't lock after deep sleep. The GPS not locking after deep sleep has to be kernel related if the stock ICS Slim v2.8 kernel locks after deep sleep and no other kernel except Kiss v2.2 will lock after deep sleep. I just tested the the stock ICS Slim v2.8 on ICZen v1.3 and the sure enough after 30 seconds or so the GPS locks perfect after deep sleep with 7-9m accuracy just like before deep sleep. Now hopefully MP can figure out what code in the Slim ICS kernel is different then his SubZero kernel code and fix GPS after deep sleep for good!
Click to expand...
Click to collapse
If you read iczen op I sent them the files lol
Sent from my SGH-T959 using xda premium

It only works on stock slim ics install. I tried with other custom kernels and no lock after deep sleep. But stock works every time.
After allowing rom to install and settle, just flash the yag and then the experia GPS files in recovery one after the other.
Only downside is.that stock kernel can't really use voodoo sound. Its kinda usable via DSL manager but sounds like ****.
Its a decision between voodoo sound and GPS for me! Hopefully soon we won't have to choose.

Still no worky aftet 20min deep sleep on euphoria + kernel 4.1...i'll try experia later
Sent from my SGH-T959 using XDA

kobesabi said:
Still no worky aftet 20min deep sleep on euphoria...i'll try experia later
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
This only works on slim ICS with stock kernel.

this prevented my phone from going into deep sleep on euphoria. besides that it made my gps get high accuracy in about 5 seconds. probably won't use it though

Works great on euphoria.. phone goes into deep sleep, and GPS works afterwards, thx it solved my GPS problems..
Sent from my SGH-T959 using XDA

Was the deep sleep more than 20 min before trying again?
Which kernel did you use with euphoria?
Did you do anything else other than flashing?
Sent from my SGH-T959 using XDA

What kernel did you use?
Sent from my SGH-T959 using XDA

Stock kernel.... and yes more than 20 min, in fact as I waked up checked the CPU spy and the phone was in deep sleep whole night, and the GPS locked in about 45sec using Google Maps.
Sent from my SGH-T959 using XDA

joroboyvn said:
Stock kernel.... and yes more than 20 min, in fact as I waked up checked the CPU spy and the phone was in deep sleep whole night, and the GPS locked in about 45sec using Google Maps.
Sent from my SGH-T959 using XDA
Click to expand...
Click to collapse
Getting the same results as jorobovyn. Euphoria + GPS fix + KA6 Modem. Only other change I made was to the GPS.conf file to add more ntp servers.
Sent from my Galaxy Nexus using XDA

dark79 said:
Getting the same results as jorobovyn. Euphoria + GPS fix + KA6 Modem. Only other change I made was to the GPS.conf file to add more ntp servers.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
Are you using Google stock kernel also? I'm only getting it working on kiss V2.2 (eww now I'm all sticky), and stock kernel. Consistent with stock kernel, sometimes loose GPS after very long deep sleep with Kiss.. Interested to see if other kernels also work.
BTW - can you post links to how you changed the GPS config file?
Thanks!

Update: euphoria + kiss 2.2 kernel + this fix = working GPS even after 20 min. After 2hr, it takes about 30 sec to get it see the birds...much better than before...i didn't have to reboot. If you retried again after that, it locks within 5sec.
I wanna try stock kernel without flashing from scratch and restore all the apps again. Anybody have a link for just only the stock kennel to euphoria?
Sent from my SGH-T959 using XDA