• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [ROM]AOSP ShiftTh3ory

scotty85 said:
i dunno,all this talk of kernels,voltages and clock speeds makes my lil brain hurt :eek: what i do know is that my phone does seem to run very well on the tiamat kernel,but like everyone else it seems to be a bit harder on the battery. tomoro ill prolly run it with leankernel and see how that goes.
Click to expand...

Yeah, I feel like I am back in the OG droid forum with all of this kernel/voltage talk. I am definitely glad the 'bolt is not as picky as the droid seemed to be.
 
brizey said:
I have seen it when pushing to 1.8. My phone will run 1.8 on smartass and interactive, but I had freezes on ondemand. Which is weird since interactive jumps to max on wake, then backs off based on a predictive algorithm.

From what I have read, OD is completely reactive, while smartass and interactive are predictive. smartass is supposedly a bit more conservative than interactive.


Edit: yeahha, your post made me think that maybe a quick jump is not all that bad...it may be that ondemand creeps up to max and sticks there under heavy load while the others keep trying to back off.
Click to expand...

I would think the quick jump would be fine as long as the voltage is high enough. I assume you were not using Tiamat's kernel on stock voltage when OC to 1.8. Also I'm under the impression smartass is a mix of interactive and OD. I am not sure of the specifics but it shouldn't jump to the highest slot unless the phone is on the verge of needing more than the 2nd highest slot, idea behind it is why crank it to max if almost max will do.

scotty85 said:
i dunno,all this talk of kernels,voltages and clock speeds makes my lil brain hurt :eek: what i do know is that my phone does seem to run very well on the tiamat kernel,but like everyone else it seems to be a bit harder on the battery. tomoro ill prolly run it with leankernel and see how that goes.
Click to expand...

It's okay Scotty :D as soon as someone has a question about why their bootloader is doing something weird or why something is happening in an obscure part of the root process that no one else here has experienced you will school all of us ;)

SolidOrange said:
Yeah, I feel like I am back in the OG droid forum with all of this kernel/voltage talk. I am definitely glad the 'bolt is not as picky as the droid seemed to be.
Click to expand...

I think the key word here is seemed. Back when I was on my OG Droid the tools and resources were not there, it wasn't a common thing to undervolt past what is stock on the kernel. If the tools and experience had been available at that time they might not have been so finnicky
 
It worked fine for me for 2 days then it drained my battery like crazy the 3rd day 80% in 2 hours or so. I may try the updated version but I will make sure compcache isn't on
 
I'm hoping the "sticking" issues ate resolved. That was my battery killer. If not I had great results with the DT moded kang bang kernel from the store. I go back to it.
 
Fyi there is a new tiamat kernel in the store also. DT said the voltage issues should be resolved with it.
 
Initial impression: this rom keeps getting better and better. Idk if its the new kernel or the new source that 1.2 is derived from but it's all butter. App drawer is smoother (pet peeve), kernel isn't sticking with ondemand or interactive. Smartass and smoothass still hang at 768 though.
 
Well that is good to hear. I wonder if he is changing these with the nightlys of CM. I always run interactive so that is good to hear. Might try running it stock for a while. Do you know if the burnt mod changed or if it matters?
 
I still don't have the sticking problem, and never did before. Wonder what the deal is. Like I had said before, I use the CM settings for governors and cpu speeds and Incredicontrol for voltages. I am at 65% at 254 MHz right now. I will keep and eye on it.
 
Yeahha said:
Well that is good to hear. I wonder if he is changing these with the nightlys of CM. I always run interactive so that is good to hear. Might try running it stock for a while. Do you know if the burnt mod changed or if it matters?
Click to expand...


Yes it has changed. It is supposed to be fixed now and the link is in his op.

Edit: he said it was in his op but I'm not sure if its the new one or not. I got it from the store.
 
I don't think I was having a sticking issue because I didn't for the 2 days before my battery drain issue. I really don't know what caused it. I think I may just be spoiled by IMO's 3.5.8 with the battery life.
 
Yep, my phone is definitely quickly dropping to 254 MHz on smartass with the latest eclipse kernel that came packed with 1.2.
 
YIKES. Downloaded the new burn mod,wiped cache formatted system and flashed the mod. Hung up at the white HTC screen. Had to for a battery pull boot into recovery and reflash the rom!

May try to redownload.
 
digdug1 said:
YIKES. Downloaded the new burn mod,wiped cache formatted system and flashed the mod. Hung up at the white HTC screen. Had to for a battery pull boot into recovery and reflash the rom!

May try to redownload.
Click to expand...

Don't format system before flashing the mod, just wipe cache/dalvik cache.
 
Yeah it was like that with the one I flashed last night. I would like to see a burnt to a crisp version of this rom not smokey/translucent but blacked out
 
Has anyone ever figured out a way to get NFL Mobile to work on this? Otherwise I'll have to restore a sense backup every Sunday during the season.
 
Label me a convert. What's that sso engine they were talking about in the first post. I may try that. On a side note, have you noticed auto brightness likes to stay at the dimmest setting on this rom unless you are in, like, direct light? Is that on purpose? It's really bugging me.
 
You must log in or register to reply here.
Back
Top Bottom