Tried the update today and ended up loading my backup. Had problems with it not drawing my home screens and seemed to have lag issues. I made zero changes to the kernal other than loading it.
I'm using this and it seems great, but I don't really have anything to compare it against. I've heard good things about franco's. Anybody have a good comparison between the two?
The Following User Says Thank You to TheWenger For This Useful Post:
So is the general consensus that 1.5 or lower are IMOs beat for AOKP??
1.6's have had some battery drain issues. 1.6.4 was better. I'm testing Faux's kernel now it is solid. 1.6.6 came out last night late and I've seen reports that battery drain issues have been nipped in the bud. I'd say flash 1.6.6 if you are seeing any kind of battery drain issues in the first 24hrs. Will finish testing Faux's tomorrow and back to Imo!
Quote:
Originally Posted by Trooper
Battery has been bad for me today. But just flashed the aokp rom and 1.6.4 today. Should I give it a few days or flash a different rom and kernel?
I'd give it 2 full days yeah
Quote:
Originally Posted by TheWenger
I'm using this and it seems great, but I don't really have anything to compare it against. I've heard good things about franco's. Anybody have a good comparison between the two?
I haven't tried #12 franco yet, but earlier iterations have been great in battery life and especially performance....top notch. But I've had one nagging issue with franco #10 and below: slight lag upon initial wake aka when waking up screen and unlocking. Might have been fixed by now try it
The Following User Says Thank You to jbdan For This Useful Post:
Tried the update today and ended up loading my backup. Had problems with it not drawing my home screens and seemed to have lag issues. I made zero changes to the kernal other than loading it.
When you first try a kernel you need to give it time and a extra reboot for things to settle. Did you try this or just immediately didn't like it so swapped?
Sweet same here. Now if I can just get the kernel loaded tonight. Hope battery life is better. Twas bad yesterday. 7 hours or so moderate use and twas dead. Standard battery. I have an extended on order from VZW coming this week.
Sweet same here. Now if I can just get the kernel loaded tonight. Hope battery life is better. Twas bad yesterday. 7 hours or so moderate use and twas dead. Standard battery. I have an extended on order from VZW coming this week.
Yeah 7 hours moderate is kind of rough. I have the extended battery still in the box haven't needed to try it yet as battery life has never been an issue for me. Nice to have it though for those days I know I might need it!
1.6.6 from everything I'm reading looks to be back on track, comparable to earlier builds (battery life wise) like 1.4 and 1.5 minus the kernel/Linux updates.
1.2 was insanely good for me, it feels odd going back to an earlier kernel as I like to get the latest greatest like most of us do, but I'd like to try 1.2 again just to see!
The Following User Says Thank You to jbdan For This Useful Post:
Thanks for your feedback man. Well I flashed 1.6.6 here at work a lil while ago. Dunno if its a coincidence or not, but my phone seems to be getting warm/hot since I flashed it. Will keep an eye on it the rest of the day to see how it goes.
If it continues, will flash an older kernel or maybe just try out P3's rom. I hear its pretty darn good.
Thanks for your feedback man. Well I flashed 1.6.6 here at work a lil while ago. Dunno if its a coincidence or not, but my phone seems to be getting warm/hot since I flashed it. Will keep an eye on it the rest of the day to see how it goes.
If it continues, will flash an older kernel or maybe just try out P3's rom. I hear its pretty darn good.
Thanks!
I've had my phone get warm many times before on a fresh kernel flash. Give it a little time and see what happens.
Also, be sure you go into settings> apps> all and scroll to setCPU (if your using it or any cpu controlling app) and click on it and clear data before flashing a new kernel. You want to clear out any overclocks or undervolting you did on your present kernel. Also go into setCPU and uncheck "set on boot" if you have it checked.
Let us know how you like 1.6.6 I'll be flashing a new kernel tomorrow so I need some direction
The Following User Says Thank You to jbdan For This Useful Post:
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
We have 2 Imo threads now. Perhaps they can be combined? Anyway, 1.6.6 exp 2 is running awesome for me. IX governor 230 slot. No issues with this kernel, I think he finally nailed it.
The Following User Says Thank You to bjanow For This Useful Post:
We have 2 Imo threads now. Perhaps they can be combined? Anyway, 1.6.6 exp 2 is running awesome for me. IX governor 230 slot. No issues with this kernel, I think he finally nailed it.
That is what I have been seeing. Thanks for reporting on it!
We have 2 Imo threads now. Perhaps they can be combined? Anyway, 1.6.6 exp 2 is running awesome for me. IX governor 230 slot. No issues with this kernel, I think he finally nailed it.
What is the exp 2? I do not see that acronym on the download page.
I have lean kernel 1.6.6 exp4 230 but what do you guys mean when you say 230 slot? Is that in the undervolting page in setcpu? and you just click it ? or do you mean set the low cpu to 230 and reboot?
Last edited by litobirdy; January 19th, 2012 at 09:38 AM.
I have lean kernel 1.6.6 exp4 230 but what do you guys mean when you say 230 slot? Is that in the undervolting page in setcpu? and you just click it ? or do you mean set the low cpu to 230 and reboot?
Set the speed to 230MHz (underclock the cpu). You'll notice if you open up setCPU you have the option to lower the cpu frequency to 230MHz with the 230 exp4 1.6.6 version. I'm trying it now and also using the hotplug gov. I'm keeping the max at 1200MHz
Set the speed to 230MHz (underclock the cpu). You'll notice if you open up setCPU you have the option to lower the cpu frequency to 230MHz with the 230 exp4 1.6.6 version. I'm trying it now and also using the hotplug gov. I'm keeping the max at 1200MHz
ok,
but I thought InteractiveX already enables the hotplug needed for screen off cpu off
ok,
but I thought InteractiveX already enables the hotplug needed for screen off cpu off
I thought that too. They're learning me over @ the rootz
Hotplug governor can and will disable a cpu core when the the screen is ON or OFF depending on the load. InteractiveX is a hybrid of sorts and has a screen-OFF hotplug feature that disables a cpu core ONLY when the screen is off. From what I understand they also scale differently when the OS is calling for more power to run a certain task/tasks. It's all very fascinating to me
The Following User Says Thank You to jbdan For This Useful Post:
I thought that too. They're learning me over @ the rootz
Hotplug governor can and will disable a cpu core when the the screen is ON or OFF depending on the load. InteractiveX is a hybrid of sorts and has a screen-OFF hotplug feature that disables a cpu core ONLY when the screen is off. From what I understand they also scale differently when the OS is calling for more power to run a certain task/tasks. It's all very fascinating to me
So we need to run the hotplug goverenor and not interactivex on setcpu?
/me is confused.
Ok I am running the LeanKernel 1.6.6 on Redemption ROM 1.0.4.
In SetCPU, thanks to binaryvisions, this is all I did.
Open up SetCPU.
Click on Scaling and selected interactivex
Click on Set on Boot.
So, is this all I need to do? Is there something else that needs to be done to "save" this config in SetCPU?
Now I see some of you talking about the hotplug governor setting.
You can see my confusion.
Again, not a n00b here, but can someone dumb this all down for me a bit?
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
You got the right idea Trooper. As soon as you open setcpu it enables the settings, no need to click save when you change them either. I would not use set at boot until you are certain that is what works for your phone. If you get a lockup due to a kernel mismatch with your hardware then it's tough to get out of it. When you reboot just make it a habit of going into setcpu, check your settings and back out.
I'm not running hotplug yet but I might give it a shot later today. I d/l the 180 version this morning of exp 4 so I just want to sit with IX for a while to make sure my phone can handle it.
The Following 2 Users Say Thank You to bjanow For This Useful Post:
So we need to run the hotplug goverenor and not interactivex on setcpu?
/me is confused.
Ok I am running the LeanKernel 1.6.6 on Redemption ROM 1.0.4.
In SetCPU, thanks to binaryvisions, this is all I did.
Open up SetCPU.
Click on Scaling and selected interactivex
Click on Set on Boot.
So, is this all I need to do? Is there something else that needs to be done to "save" this config in SetCPU?
Now I see some of you talking about the hotplug governor setting.
You can see my confusion.
Again, not a n00b here, but can someone dumb this all down for me a bit?
Thanks!
You need to run whichever governor you feel like running and whichever works best on your phone. What runs great on mine won't necessarily run great on yours
Hotplug gov has been unstable for the most part (not for some folk though), until this latest exp4 came out according to the developer. I've never run it and have always enjoyed both InteractiveX and Interactive. I'm testing hotplug now I've been waiting for imoseyon to give the go ahead.
bj gave the rest of the info
The Following User Says Thank You to jbdan For This Useful Post:
I would suggest trying out the 180 I didn't really like the hot plug gov and like IX better hot plug should be better for the battery but I like knowing my phone will default to a slot that can handle what it it doing more than trying to conserve battery but my battery also never drops below 30%
I'm on stable 1.6.6. Is the experimental significantly better on battery? And which governor is the best on battery? From what I could glean of the discussion above, I am thinking hotplug, but just checking to make sure I didn't misunderstand.
Edit: went and found the link on the difference here and decided to come back and update it for anyone else wondering. Looks like hotplug is likely to save more battery, but also not as stable. I will try both and report back (though I think the results are individual-phone-dependent).
Last edited by quiklives; January 20th, 2012 at 11:15 PM.
The Following User Says Thank You to quiklives For This Useful Post:
I'm on stable 1.6.6. Is the experimental significantly better on battery? And which governor is the best on battery? From what I could glean of the discussion above, I am thinking hotplug, but just checking to make sure I didn't misunderstand.
Edit: went and found the link on the difference here and decided to come back and update it for anyone else wondering. Looks like hotplug is likely to save more battery, but also not as stable. I will try both and report back (though I think the results are individual-phone-dependent).
I never tried 1.6.6 stable just the 1.6.6 exp4 version and used hotplug. It was 100% completely stable for me on hotplug and battery life is excellent. It matched my favorite 1.2.1 IAX UV'd battery wise and was just a little bit snappier to my surprise. I just swapped kernels tonight (gave 1.6.6 exp4 a good 46+ hours) and am now testing out franco's 13.1 for the wknd. Wanted to go to something different & also see how far he has come along. Last time I tried his was at nightly 10.
I never tried 1.6.6 stable just the 1.6.6 exp4 version and used hotplug. It was 100% completely stable for me on hotplug and battery life is excellent. It matched my favorite 1.2.1 IAX UV'd battery wise and was just a little bit snappier to my surprise. I just swapped kernels tonight (gave 1.6.6 exp4 a good 46+ hours) and am now testing out franco's 13.1 for the wknd. Wanted to go to something different & also see how far he has come along. Last time I tried his was at nightly 10.
OP update to 1.7.1!
I JUST flashed 1.7.0 like an hour ago! lol
The Following User Says Thank You to quiklives For This Useful Post:
HAHA it's sickening how fast stuff just pops out. In a good way!
You might want to go to 1.7.1 as some reverts were made to 1.7.0 that caused Kejar (developer of gummy) to make the request to imoseyon. I think he mentioned 1.7.0 was not smooth enough, not about battery issues iirc
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
I was just about to go back too until I saw 1.7.1 released and addressing the drain. So far it's looking pretty good. 2.5 hours down 3%, very comparable to .6. Taking it out for a spin now in 4G.
For me, 1.6.6 exp3 ran flawless and good batt stats.
1.7 gave me quirks in SMS when I wanted to edit text. It just acted up not doing what I wanted it to do.
Put in 1.7.1 and its all good so far.
I liked 1.6.6 exp3 so I'll keep it in the wings.
1.7.1 is looking pretty good though.
Device(s): S3, Galaxy Nexus(wifi), TB(backup), DI(wife), Eris (love that thing)
Carrier: Not Provided
Thanks: 336
Thanked 484 Times in 358 Posts
Ok, not better but similar. At 39% now, heavy use for me, solid 11 hours. I can live with that. I could prob get 15 or more out of this easily but will plug in now. First cycle too, it can and should get a little better. Def worth the flash. Oh, btw, I'm running Jake's script with 1350 always and 230 low. No lag and snappy as heck.
Ok, not better but similar. At 39% now, heavy use for me, solid 11 hours. I can live with that. I could prob get 15 or more out of this easily but will plug in now. First cycle too, it can and should get a little better. Def worth the flash. Oh, btw, I'm running Jake's script with 1350 always and 230 low. No lag and snappy as heck.
2Likes
haven't needed to try it yet as battery life has never been an issue for me. Nice to have it though for those days I know I might need it!
