[ROM][AOSP][4.0.3] Codename Android 1.5.5 [Full Open Source]

[tony bag o donuts]

I am going to reflash...starting last night my soft buttons started to disappear and just give me a small straight back arrow in the bottom left of my screen....rebooting corrects the issue but I may just flash everything again.

Is there a future release coming again? or will it be a bit?

 

[2defmouze]

I am going to reflash...starting last night my soft buttons started to disappear and just give me a small straight back arrow in the bottom left of my screen....rebooting corrects the issue but I may just flash everything again.

Is there a future release coming again? or will it be a bit?

It will be a bit.. Make sure you get a fresh download and check the MD5.. Don't want you to go through the trouble just to have the same issues! Lol

Sent from my Galaxy Nexus

 

[tony bag o donuts]

MD5?

 

[2defmouze]

MD5?

Lol yeah.. under the download link there is an MD5 checksum.. its a unique string of numbers the file will create if its the correct file and not corrupted or anything like that, which can occasionally happen with downloads.

You can download a small md5 checker to your computer that will let you check the file you download. I'd recommend checking the ROM zip on your phone right before you flash it.. if you have root explorer you can just navigate to the file on your sd card, long press, select properties, and in a few seconds it will generate the md5 at the bottom of the properties window. You want it to match the one printed under the download link. Just a safeguard to make sure you get a good download.

 

[tony bag o donuts]

LOL yeah I had done that.
Sorry got confused for a bit.
going to reflash and redo everything.

See you guys on the flip side!:'(

 

[davidnc]

MD5?

Edit:

2defmouze typed faster , lol

 

[2defmouze]

Edit:

2defmouze typed faster , lol

Lol I IZ A NINJA

 

[tony bag o donuts]

Gapps is different file name than the one I had for 1.4. Weird

Sent from my Galaxy Nexus using Tapatalk

 

[maguire11]

What does everyone use for the cpu governor settings if you use the kernel that came with codename 1.4? Does the hotplug one actually turn off one core when the screen is off? What is the best setting for battery life?

Sent from my Galaxy Nexus using Tapatalk

 

[2defmouze]

What does everyone use for the cpu governor settings if you use the kernel that came with codename 1.4? Does the hotplug one actually turn off one core when the screen is off? What is the best setting for battery life?

Sent from my Galaxy Nexus using Tapatalk

I use it as it came with Ondemand gov. You'd probably see a bit better battery with hotplug or interactivex but i get fine battery life with ondemand and I felt those other govs caused just a bit of slowdown to me.

And yes hotplug turns off cpu1 when screen is off, so does interactivex I believe.

Sent from my Galaxy Nexus

 

[Cyber Warrior]

One of the great thing about ICS (stock) is that by default.. it automatically shuts down one of the cores when the screen is off.

 

[greydarrah]

One of the great thing about ICS (stock) is that by default.. it automatically shuts down one of the cores when the screen is off.

So running a ROM, do you think that the ICS control of this overrides whatever governor we might have set? I like that ICS does this, but wonder if you're running a kernel with the governor set to performance or on demand, could it keep the other core always running, or does the fact that we're running a ROM kill the ICS function anyway?

 

[Cyber Warrior]

So running a ROM, do you think that the ICS control of this overrides whatever governor we might have set? I like that ICS does this, but wonder if you're running a kernel with the governor set to performance or on demand, could it keep the other core always running, or does the fact that we're running a ROM kill the ICS function anyway?

Good question lol.. I'm assuming since they're not the stock kernel that its not going to behave the same but that these devs that build custom kernels are re-adding this feature anyways so it doesn't really matter. I just thought it was an interesting feature of stock ics.

 

[dc5_alex]

toggle led flashlight button doesnt work for me in notification widget. anyone else have this problem?

 

[Nechasin]

Twice now, I have used the stock camera to make a video. After stopping the video and pushing the home button, I've put my phone back in my pocket. 5-10 minutes later, I noticed that the phone is screaming hot and if I look at my battery stats, it was been awake the whole time with the screen off. After force stopping the camera app, everything goes back to normal.

The first time, I thought it was just an anomaly, but the second time make me think it is something else.

I'm running Codename 1.4.0 and Franco Kernal 18.2 for the second instance, Franock Kernel 18.0 for the first instance.

 

[2defmouze]

Twice now, I have used the stock camera to make a video. After stopping the video and pushing the home button, I've put my phone back in my pocket. 5-10 minutes later, I noticed that the phone is screaming hot and if I look at my battery stats, it was been awake the whole time with the screen off. After force stopping the camera app, everything goes back to normal.

The first time, I thought it was just an anomaly, but the second time make me think it is something else.

I'm running Codename 1.4.0 and Franco Kernal 18.2 for the second instance, Franock Kernel 18.0 for the first instance.

Lol.. pressing the Home button does NOT close whatever process you have open. Pressing the Back button until you get to home generally does. Alternatively under Developer Options you can enable the option to kill apps by holding the Back button.. personally I didn't like that option I leave it disabled. But yeah, using Home does NOT kill anything and will leave the apps open.

 

[Nechasin]

I didn't have the problem with Stock 4.0.2. If I stop recording, and go to a different app, It didn't kill the battery.

 

[2defmouze]

I didn't have the problem with Stock 4.0.2. If I stop recording, and go to a different app, It didn't kill the battery.

AFAIK it's always been this way. In any case, that's your problem, you need to close the camera app or it will stay open. I have no reason to lie to you.

 

[Nechasin]

Well know that I know it is an problem, that is what I'll do. Sounds like a problem in the camera app.

 

[mack]

You've probably already switch back to Gummy, but I think you're in a very small group if your having to battery pull on codename's latest version. Actually, I've heard of no one else having that level of trouble. If you want to try it again (or haven't changed to Gummy yet), I'd suggest a full wipe and re-flash. Something must have gotten screwed up the first time you flashed it. It's the most stable, fastest ROM I've run so far.

I haven't switched yet, but it has restarted itself about four times this week..