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

Root [ROM] AOSP BURNTH3ORy

brizey said:
I may try interactiveX...been using smartass for a while now.

What is a good way to see your sleep speed?
Click to expand...

InteractiveX is the only governor I run.

You can use setCPU like Scotty said above or you can use speedtweak.sh (on Imos' kernel) and "view in time stats" It will list the voltage slots and number indicating how long it's been in use. The higher the number the longer it's being used.
 
when it was sleeping at the max,it was set on on demand,wich is what i always use. not sure why its scaling 1024 all the time :eek: at first i was gonna set a screen off profile,but then i decided to play wiht governors. "powersaver" immediately scaled down to 245 while watching the set cpu screen,tho it seemed a little sluggish when waking up. i could try bumping the min up a lil but ive always used 245 and my phone doesnt seem to care normally. so i switched to "smoothass" and its been scaling 768 and thats taken up a big chunk of the pie... wich is prolly the amount of time its actually been sleeping(20%) sicne ive been messing with it all day.

despite the high sleep time,the battery has actually been preetty good. i wouldnt say its been harder on my battery than anything else,tho again,its hard for me to tell the way i use my phone.

ive got 5% left,and 8 hours and 20 minutes on the charge. voice calls taking up 27%,and bluetooth 11%. prolly had close to my usual 3ish hours of voice calls over bluetooth,wich has been connected most of the time.

no doubt imos leankernel works,but i think ill experiment with this one another couple days. maybe try som ohter governors and maybe a screen off profile. all in all its running so good i hate to mess with it :D

this rom works great on my phone and i love the UI... i cant wait for the transparent keyboard and pulldown :cool:

Edit: almost forgot... had 4g on most of the day as well
 
WormDoes said:
I'm not doubting it's running smoothly. I was more concerned with the speed it sleeps at. I would get 6 hours of use if I was lucky with my phone sleeping 96% of the time at 1024. No thanks. If it ain't broke, don't fix it (read: Imoseyon's LeanKernel)
Click to expand...

I have been very tempted to flash over to IMO's 3.5.8, I really like that kernel and it seems to really like my phone. I figured I would give this rom at least one day (read full charge when I leave for work, no charge until I get home) before I decide if I want to flash back to IMO's
 
Yeahha said:
I have been very tempted to flash over to IMO's 3.5.8, I really like that kernel and it seems to really like my phone. I figured I would give this rom at least one day (read full charge when I leave for work, no charge until I get home) before I decide if I want to flash back to IMO's
Click to expand...

His kernels, especially 3.5.8, run so well on my phone it's an automatic flash after the ROM for me.
 
WormDoes said:
His kernels, especially 3.5.8, run so well on my phone it's an automatic flash after the ROM for me.
Click to expand...


I almost did that too. But with all the talk he did about the eclipse kernel I couldn't resist trying it out. I'm also thinking about turning off compcache and setting up a swap partition, I noticed after running on the same rom for 5 days I was getting some lag that I used to only associate with compcache. Hell might not even bother with the swap partition and just remove the use of compcache.
 
I was using InteractiveX on the 1.4 kernel which was great for sleeping, but whenever I turned the phone on the CPU would jump to 1024. Ondemand seems to be working better for me. I'm flashing his vanilla 1.5 now so I'll have to experiment with this new kernel of his.
 
My opinion there's no need for swap on the tbolt, much less AOSP, and I have compache disabled. Still running the RAM script, and I always have mid to high 40% available RAM.

swap just doesn't seem like it would ever serve a noticeable purpose I guess.
 
Ibrick said:
My opinion there's no need for swap on the tbolt, much less AOSP, and I have compache disabled. Still running the RAM script, and I always have mid to high 40% available RAM.

swap just doesn't seem like it would ever serve a noticeable purpose I guess.
Click to expand...


I was thinking the same thing actually. I just realized that compcache was enabled by default on this rom before I came to work and didn't have the time to restart to disable it. I thought more about swap after I posted that and figured it would be pointless or make very little difference compared to running it on my old og droid or even the d2g
 
I'm thinking this kernel has a "sticking" problem. I use setcpu and noticed my phone just hangs at my max speed. Regardless of governor. I bet that's the cause of high high consumption while sleeping. If this continues I will definitely be going back to imo.

Edit: rebooted let the phone sit, checked setcpu and the phone is resting at 768MHz. My min is 245. I made a backup and am gonna try imo.
 
Looks like I need to download setCPU again to monitor the speed my CPU is running, if I am also getting stuck at above max for no reason I will be back on IMO as well.
 
Yeahha said:
Looks like I need to download setCPU again to monitor the speed my CPU is running, if I am also getting stuck at above max for no reason I will be back on IMO as well.
Click to expand...

Thats a good idea.
Going back to imo's kernel fixed the problem. Resting at my min of 245.

FWIW benchmarks also improved :)
 
I had 78% at 245 after about 3 hours using the supplied kernel and smartass. This included about 45 minutes of screen off music. Sigh...it is amazing how varied everyone's experience is.
 
Idk I was watching my frequency with setcpu and regardless of changing governors it was stuck. Even after a reboot.
 
Yeah I just checked my phone, I'm sitting above 85% after 4.5 hours off the charger. Could it be a setCPU vs using cm settings to set the speed? I used the settings within CM settings, it seems to me if I was getting hung at a higher clock speed it would affect the battery more.
 
sooo how is this rom overall? Im on aosptheory1.5x and its great for me, battery lasts all day/night. whats the difference between the two?
 
Yeahha said:
Yeah I just checked my phone, I'm sitting above 85% after 4.5 hours off the charger. Could it be a setCPU vs using cm settings to set the speed? I used the settings within CM settings, it seems to me if I was getting hung at a higher clock speed it would affect the battery more.
Click to expand...

Could be. But I've never had that particular problem and I always use setcpu.
This also may not be happening to everyone. Just those who are having high usage while the phone is asleep.

Such as myself, worm and Scottie.
 
Chrizzl3 said:
sooo how is this rom overall? Im on aosptheory1.5x and its great for me, battery lasts all day/night. whats the difference between the two?
Click to expand...

From what I understand this is a custom version of AOSPTheory, I like it and it could be a daily driver if you wanted to use it as one, you have of course seen the kernel discussion

digdug1 said:
Could be. But I've never had that particular problem and I always use setcpu.
This also may not be happening to everyone. Just those who are having high usage while the phone is asleep.

Such as worm and Scottie.
Click to expand...

Yeah, I've used setCPU plenty of times and never had any issue like that. Like it has been said before no two phones are built the same.
 
Yeahha said:
. Could it be a setCPU vs using cm settings to set the speed?
Click to expand...

i dont think so... ive always used setcpu to set min/max and governor,and never felt like it was in correct. still not sure what i want to do... i want to give it another day or 2 before jumping back to imo. thinking i may stay with smoothass and set a screen off profile.

im sure the faster speen affects it while sleeping,but my battery was actually pretty good with todays useage :)
 
Yeah I haven't got a widget to monitor the CPU speeds yet but compared to how the battery is lasting it seems to me it must not be hanging up on a high speed. Trying to figure out how to set up a cpu speed widget with tasker currently with little success :mad:

Add: I have figured out a way to automatically underclock with the screen off with tasker so if I am hanging at a higher speed I can force it to underclock until I wake it :D
 
scotty85 said:
i dont think so... ive always used setcpu to set min/max and governor,and never felt like it was in correct. still not sure what i want to do... i want to give it another day or 2 before jumping back to imo. thinking i may stay with smoothass and set a screen off profile.

im sure the faster speen affects it while sleeping,but my battery was actually pretty good with todays useage :)
Click to expand...


Have you used setcpu to monitor your frequency?

I may try reflashing the Rom w/o wiping just to see. I'm not worried about my phones sleeping frequency. I'll use a profile in setcpu for that. I just don't like my frequency sticking at any certain one. May as well be using the performance governor.
 
digdug1 said:
Have you used setcpu to monitor your frequency?

I may try reflashing the Rom w/o wiping just to see. I'm not worried about my phones sleeping frequency. I'll use a profile in setcpu for that. I just don't like my frequency sticking at any certain one. May as well be using the performance governor.
Click to expand...

just by viewing info/time in state.

and by watching what it is scaling when the app is running. i like to use a governor(typically ondemand) that will scale the min(245) without anything processor intensive going on. an ocasional spike to something higher i dont worry too much about,and chalk up to some process doing... something in the background.

when i checked it this morning with on demand as the governor it was 1024 and never changed :eek: smoothass scales more less constantly at 768,but does jump occasionally to 1024
 
scotty85 said:
just by viewing info/time in state.

and by watching what it is scaling when the app is running. i like to use a governor(typically ondemand) that will scale the min(245) without anything processor intensive going on. an ocasional spike to something higher i dont worry too much about,and chalk up to some process doing... something in the background.

when i checked it this morning with on demand as the governor it was 1024 and never changed :eek: smoothass scales more less constantly at 768,but does jump occasionally to 1024
Click to expand...


That was my exact problem. Same frequency issues. I think it's a kernel issue. I experienced that a few times with my droid1.
I flashed imo's .11 kernel and am sitting steady on 245 at idle.
 
has anyone whose gone back to imo lost any speed or responsiveness? thats what i love about this and id hate to give it up.
 
scotty85 said:
has anyone whose gone back to imo lost any speed or responsiveness? thats what i love about this and id hate to give it up.
Click to expand...


Nope. Same feel but my benchmarks improved. I made a backup before swapping just in case. There is also a link to the eclipse kernel in the store.
 
You must log in or register to reply here.
Back
Top Bottom