[ROM] Android Open Kang Project

**mclarryjr** · 06-21-2012, 03:56 PM

I like to use my GPS so I'll stay with 38 for now, thanks everyone for testing it for me

**SeigaGen** · 06-21-2012, 09:21 PM

Latest Franco kernel 192 features 1651 mhz OC.

Needless to say, my nexus didn't like that setting. I had some random freezes and restarts.

Sent from my Galaxy Nexus using Tapatalk 2

**dmmarck** · 06-21-2012, 10:36 PM

Originally Posted by SeigaGen

Latest Franco kernel 192 features 1651 mhz OC.

Needless to say, my nexus didn't like that setting. I had some random freezes and restarts.

Sent from my Galaxy Nexus using Tapatalk 2

I ran it for an hour but did nothing of substance.

Sent from my Galaxy Nexus using Android Central Forums

**tony bag o donuts** · 06-22-2012, 06:25 AM

Hopefully 40 drops soon to fix the gps issues but I have a feeling that will be a milestone release.

**atlas9171** · 06-22-2012, 10:01 AM

Originally Posted by 2defmouze

GPS just locked on here in about 12 seconds, Fwiw.

Sent from my Galaxy Nexus using Tapatalk 2

Yeah, mine locks in pretty quickly also on build 39 using franco nightly 190, not sure what the cause of the problems for others is. Only time I had an issue was using linaro build.

**2defmouze** · 06-22-2012, 10:10 AM

Originally Posted by atlas9171

Yeah, mine locks in pretty quickly also on build 39 using franco nightly 190, not sure what the cause of the problems for others is. Only time I had an issue was using linaro build.

I'd guess more often than not they didn't wipe when they flashed, restored bad data, are victim's of coincidence and just got some slow locks in a bad area or at a bad time, are exaggerating the issue (not on purpose probably, but still) .. Or some combination of all those possibilities

As is the case when you experience bugs that most other people are not, it's usually, logically, something you did.

EDIT: just tested again for the heck of it and it locked on in like 6 seconds..

Sent from my Galaxy Nexus using Tapatalk 2

**atlas9171** · 06-22-2012, 10:15 AM

Originally Posted by 2defmouze

I'd guess more often than not they didn't wipe when they flashed, restored bad data, are victim's of coincidence and just got some slow locks in a bad area or at a bad time, are exaggerating the issue (not on purpose probably, but still) .. Or some combination of all those possibilities

As is the case when you experience bugs that most other people are not, it's usually, logically, something you did.

EDIT: just tested again for the heck of it and it locked on in like 6 seconds..

Sent from my Galaxy Nexus using Tapatalk 2

Probably all pretty logical reasons, I know I came from a different ROM so I wiped which could be why I'm having no problems, I checked mine a few times and every app locked in within a few seconds.

**AZDROIDX** · 06-22-2012, 11:09 AM

Originally Posted by dmmarck

I ran it for an hour but did nothing of substance.

Sent from my Galaxy Nexus using Android Central Forums

I've tried 14xx and currently on 13xxMHz, really don't see much over 12xxMHz where I usally stay at. I do like the new 576MHz though. Love AOKP and Franco combo!

**tony bag o donuts** · 06-22-2012, 11:20 AM

Originally Posted by 2defmouze

I'd guess more often than not they didn't wipe when they flashed, restored bad data, are victim's of coincidence and just got some slow locks in a bad area or at a bad time, are exaggerating the issue (not on purpose probably, but still) .. Or some combination of all those possibilities

As is the case when you experience bugs that most other people are not, it's usually, logically, something you did.

EDIT: just tested again for the heck of it and it locked on in like 6 seconds..

Sent from my Galaxy Nexus using Tapatalk 2

Did a full wipe, restored data, didn't work. did full wipe, downloaded app, still no go. I am in a fringe 4g area though.

**SeigaGen** · 06-22-2012, 02:46 PM

Originally Posted by dmmarck

I ran it for an hour but did nothing of substance.

Sent from my Galaxy Nexus using Android Central Forums

Yeah, my phone is getting redonculously hot with the new nightly kernel 192 Franco. Phone will restart on high cpu usage like GPS.

Sent from my Galaxy Nexus using Tapatalk 2

**dmmarck** · 06-22-2012, 02:53 PM

Originally Posted by SeigaGen

Yeah, my phone is getting redonculously hot with the new nightly kernel 192 Franco. Phone will restart on high cpu usage like GPS.

Sent from my Galaxy Nexus using Tapatalk 2

What are your settings?

Sent from my Galaxy Nexus using Android Central Forums

**SeigaGen** · 06-22-2012, 03:10 PM

Originally Posted by dmmarck

What are your settings?

Sent from my Galaxy Nexus using Android Central Forums

1.5 ghz high, 729 low, Wheatley gov. Voltage settings haven't been touched.

Sent from my Galaxy Nexus using Tapatalk 2

**dmmarck** · 06-22-2012, 03:16 PM

Originally Posted by SeigaGen

1.5 ghz high, 729 low, Wheatley gov. Voltage settings haven't been touched.

Sent from my Galaxy Nexus using Tapatalk 2

It's probably the overclocking, if I had to pinpoint it to anything.

**SeigaGen** · 06-22-2012, 03:41 PM

Originally Posted by dmmarck

It's probably the overclocking, if I had to pinpoint it to anything.

Which was fine on build 191. I've reset it to 1228 and just wait for an updated build to try it out again.

Sent from my Galaxy Nexus using Tapatalk 2

**bbudnick5001** · 06-22-2012, 05:54 PM

Originally Posted by SeigaGen

Which was fine on build 191. I've reset it to 1228 and just wait for an updated build to try it out again.

Sent from my Galaxy Nexus using Tapatalk 2

Updated build out r194

Sent from my GT-I9300 using Android Central Forums

**ultravisitor** · 06-23-2012, 10:59 PM

build 40 is out

**dmmarck** · 06-23-2012, 11:15 PM

Originally Posted by ultravisitor

build 40 is out

Yes it is

**DroidDev** · 06-24-2012, 09:10 AM

Anyone notice when you lock the phone it will still allow you to pull down the notification shade? Defeats purpose of lock screen. Anyone know how to disable that?

I'm on build 39.

Sent from my Galaxy Nexus using Tapatalk 2

**oxymoron** · 06-24-2012, 09:22 AM

Originally Posted by DroidDev

Anyone notice when you lock the phone it will still allow you to pull down the notification shade? Defeats purpose of lock screen. Anyone know how to disable that?

I'm on build 39.

Sent from my Galaxy Nexus using Tapatalk 2

As in slide to unlock? Because that's just AOSP ICS. If you have a password/pin/face unlock set and can still pull down the notification, that's another story.

*customized tapatalk signature*

**DroidDev** · 06-24-2012, 09:28 AM

Originally Posted by oxymoron

As in slide to unlock? Because that's just AOSP ICS. If you have a password/pin/face unlock set and can still pull down the notification, that's another story.

*customized tapatalk signature*

So being able to pull the shade down while phone is locked is per requirements? There a way to not allow the shade to be pulled down when phone is locked like in GB? I don't like people being able to see texts when phone is locked

Sent from my Galaxy Nexus using Tapatalk 2

**KineticMD** · 06-24-2012, 09:28 AM

Originally Posted by DroidDev

Anyone notice when you lock the phone it will still allow you to pull down the notification shade? Defeats purpose of lock screen. Anyone know how to disable that?

I'm on build 39.

Sent from my Galaxy Nexus using Tapatalk 2

Isn't that just a standard feature of Ice Cream Sandwich? The 4+ months I was unrooted I could do that with my GNex too.

EDIT: Wow, lots o' folks beat me to the punch!

**KineticMD** · 06-24-2012, 09:36 AM

Question: When you're just upgrading to a new build (ie. 39 to 40) do you still need to wipe your whole phone before flashing, or can you just flash overtop of your current ROM?

I be a root noob.

**oxymoron** · 06-24-2012, 09:49 AM

Originally Posted by DroidDev

So being able to pull the shade down while phone is locked is per requirements? There a way to not allow the shade to be pulled down when phone is locked like in GB? I don't like people being able to see texts when phone is locked

Sent from my Galaxy Nexus using Tapatalk 2

Yep. Stock ICS. As for a way to circumvent the circumvention... not sure. It doesn't bother me. I just use a pin lock when I leave my phone laying around (I.e. at work). It's in my pocket 99% of the time however. I hear ya about the texts though.

*customized tapatalk signature*

**oxymoron** · 06-24-2012, 09:55 AM

Originally Posted by KineticMD

Question: When you're just upgrading to a new build (ie. 39 to 40) do you still need to wipe your whole phone before flashing, or can you just flash overtop of your current ROM?

I be a root noob.

Best practice = yes. You can get away with not doing a complete data wipe many times when flashing from one build to the next (considering there aren't major changes... devs will let you know), but you can't expect any ROM support if you have issues and you didn't do a full wipe.

I've done it a lot, and MOST of the time it's okay. Occasionally it isn't, then a full wipe is required to fix it anyway. Soo... it's up to the flasher's discretion (but I recommend a full wipe always).

You'll have fun either way though

*customized tapatalk signature*

**2defmouze** · 06-24-2012, 10:03 AM

Everything Oxy said. If you want to dirty-flash, wipe cache, dalvik and (recommended) format /system. Flash the ROM and Gapps. If you run into any issues at all, force closes, errors, weird glitches, whatever, assume it's probably because you dirty-flashed, you dirty, dirty vagabond (jk, I do it sometimes), and you'll need to do a full wipe and flash to fix.