I'm on sense 5, .42 arc reactor kernel,
While using kernel tuner or setcpu I set my frequency to 1.8 as the max. Everything works fine for a little bit then after a few minutes I check back and it is set back down to 1.5? I've cleared cache and fixed permissions as well as restarting my phone.. any help?
Sent from my EVO using xda app-developers app
A little bit more info is needed, are you s-off? what Rom are you running? Mean Bean has a script that sets everything at 1.5 or 1.7 depending on your sticky settings, Viper rom has a daemon that controls the over clock, governor, etc...
edit: my bad just read your post, if you are on sense 5 there was an edit that you had to do in the init.qcom.posboot.sh for your OC to stick, depending on the release that you are using...
I am currently s-off, and on sense 5. I am not so inclined on going about doing that? Lol ... How would you recommend me doing that, can I do that through my phone without the need for a computer?
Sent from my EVO using xda app-developers app
sorevilo said:
I am currently s-off, and on sense 5. I am not so inclined on going about doing that? Lol ... How would you recommend me doing that, can I do that through my phone without the need for a computer?
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Which Sense 5 revision are you on? There were issues with CPU frequencies sticking on some of the older revisions, but has since been fixed as of r141. I'm running it now and am no longer having issues with the CPU frequencies sticking.
Sent from my EVO using xda premium
FinZ28 said:
Which Sense 5 revision are you on? There were issues with CPU frequencies sticking on some of the older revisions, but has since been fixed as of r141. I'm running it now and am no longer having issues with the CPU frequencies sticking.
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I am actually on 141 also, hmm could it have come back
Sent from my EVO using xda app-developers app
How do I go about trying to fix this?
Sent from my EVO using xda app-developers app
Ok I found out how to edit that which you mentioned, do you know what exactly it is I need to re-write? Thanks it would be much appreciated
Sent from my EVO using xda app-developers app
Related
Just wondering if that's weird
Sent from my ADR6425LVW using xda app-developers app
zkrp5108 said:
Just wondering if that's weird
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
No, normal behavior. It only comes on as needed. (well, should.)
Should come on when the load on the processor increases more. Check the Times tab up at the top right of that screen after you've done something processor intensive like loading up a game. Will probably show a few stats for the second core as well.
Forcing the second core on is not recommended either.
zkrp5108 said:
Just wondering if that's weird
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
PhantasmRezound said:
No, normal behavior. It only comes on as needed. (well, should.)
Should come on when the load on the processor increases more. Check the Times tab up at the top right of that screen after you've done something processor intensive like loading up a game. Will probably show a few stats for the second core as well.
Forcing the second core on is not recommended either.
Click to expand...
Click to collapse
yep. second core is only used when needed. like a computer, the phones first core is primary but if it feels it cant hold up it will turn on the second one.
Some processors are designed to use all cores at all times.
This one only uses the second core when it's under heavy load.
Sent from my ADR6425LVW
asynchronous CPU its totally normal
Sent from my Paranoid Android GT-19100 using xda premium
josephnero said:
asynchronous CPU its totally normal
Sent from my Paranoid Android GT-19100 using xda premium
Click to expand...
Click to collapse
Right, that was the word I was looking for.
Sent from my ADR6425LVW
Do you guys know how to undervolt w system tuner
Sent from my ADR6425LVW using xda app-developers app
zkrp5108 said:
Do you guys know how to undervolt w system tuner
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
You need a kernel that has voltage control.
Sent from my ADR6425LVW
wlmeng11 said:
You need a kernel that has voltage control.
Sent from my ADR6425LVW
Click to expand...
Click to collapse
I do
Sent from my ADR6425LVW using xda app-developers app
zkrp5108 said:
I do
Sent from my ADR6425LVW using xda app-developers app
Click to expand...
Click to collapse
System Tuner from the Play Store, theres a voltage tab, i
Sent from my ADR6425LVW using Tapatalk 2
System tuner can force 2nd online.
Sent from Rezound
ICS could definitely use it. My games are more choppy and laggy since ICS. I know GB couldnt utilize second core because the kernel didnt support it. Youd think it would try to use it with the Sense lag... Lol
In my experience, undervolting doesn't do much to improve battery life. All these new Sense kernels are fun to play with, but they haven't done a thing to improve performance for me. And I've tried all the recommended settings that are supposedly great.
And yes, they may work fine... But I can't say any of them were noticeably better than stock. In fact, most were worse.
But, the flasher in me will continue to experiment. It's just what we do.
abby_nitewolf said:
System Tuner from the Play Store, theres a voltage tab, i
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Yea but how do you use it? I see people saying like I do 75 across the board does that mean they are just hitting the -12.5v till it equals 75 total lower volts?
Hey guys...
I'm running Gingeritis 3D v1.2 with Ziggy's kernel.
What's the best settings to get better and longer battery life?
Sent from my ADR6400L using xda premium
Use imos kernel, 1024 max ,smartass governorv2 and undervolt -75 all across the board if possible.
Sent from my ADR6400L using Tapatalk 2
Should it work fine with Gingeritis 3D?
I've actually never flashed a kernel... so if I do flash this kernel, will it remain there even after I change to another ROM?
Sent from my ADR6400L using xda premium
If you change roms you'll change kernels unless you are using a Rom that has the same kernel. It's not like radios. It's easy to flash just wipe caches and flash the kernel in recovery.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
If you change roms you'll change kernels unless you are using a Rom that has the same kernel. It's not like radios. It's easy to flash just wipe caches and flash the kernel in recovery.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
My current ROM, Gingeritis 3D v1.2, is a sense based ROM that came with Ziggys kernel. So because my ROM is sense based, I must find the most recent kernel by Imoseyon that is a GB/Sense kernel... correct?
Can you help me verify that this is the correct and most recent kernel available that is compatible with Gingeritis 3D v1.2?
Link: http://rootzwiki.com/topic/603-kern...kernel-620-6312-camcorder-fixed/page__st__840
Thanks a lot for you help man.
You always seem to help me.
Try version 6.1. It's based off of 605.9 so it should work just fine.
Sent from my ADR6400L using Tapatalk 2
Okay, thanks man. Flashing it shortly.
Sent from my ADR6400L using xda premium
Flashed and phone runs nicely so far.
I'll get back at a later date to report battery life.
Thanks so much man!
Sent from my ADR6400L using xda premium
RBarnett09 said:
Flashed and phone runs nicely so far.
I'll get back at a later date to report battery life.
Thanks so much man!
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
You're welcome. Glad its working out so far.
Sent from my ADR6400L using Tapatalk 2
Very noticeable battery life difference.
So far I am running your recommended 1024000MHz max and 245760MHz min on the smartassv2 governor.
Across the board right now I am actually -125 and it still runs perfectly. May keep dropping it as long as it can handle without freezing, or is this bad?
Sent from my ADR6400L using xda premium
RBarnett09 said:
Very noticeable battery life difference.
So far I am running your recommended 1024000MHz max and 245760MHz min on the smartassv2 governor.
Across the board right now I am actually -125 and it still runs perfectly. May keep dropping it as long as it can handle without freezing, or is this bad?
Sent from my ADR6400L using xda premium
Click to expand...
Click to collapse
It isn't bad just remember not to check apply at boot so that if you get a reboot it doesn't get stuck at that voltage.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
It isn't bad just remember not to check apply at boot so that if you get a reboot it doesn't get stuck at that voltage.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Yeah, that would suck. Lol.
Thanks a lot man! You definitely showed me a way to get longer life out of my battery.
Sent from my ADR6400L using xda premium
So I get the game and it says not supported on your device. Is this normal
Sent from my EVO using xda app-developers app
leo72793 said:
So I get the game and it says not supported on your device. Is this normal
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Nope I was running it on premier ROM not to long ago. Maybe try updating it
Sent from my EVO using xda premium
leo72793 said:
So I get the game and it says not supported on your device. Is this normal
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
im on the viper 2.0.2 and mine is working... I've read other threads and people is having that problem...
HTC EVO LTE
Same Rom as you. Just got it latest version. Not sure what's up
Sent from my EVO using xda app-developers app
leo72793 said:
Same Rom as you. Just got it latest version. Not sure what's up
Sent from my EVO using xda app-developers app
Click to expand...
Click to collapse
Did you change your LCD density?
Negative captain. All stock except for basic tweaks from viper app
Sent from my EVO using xda app-developers app
Works for me with stock with goodies and jelly bomb rom! What could have happened is you may have accidentally changed your build prop ( custom market,changing screen dpi or even running aosp at a different DPI) do other apps work fine?
Sent from my EVO using xda premium
Completely stock, out-of-the-box here and it works pretty good. Got it the day it dropped in the Play Store and haven't been prompted for an update since then.
I've only had issues with this game while running an AOSP ROM. I've tried it on two different Sense ROMs and it's worked great.
I have had it running on AOSP and sometimes it won't start completely, sometimes it'll freeze after a race, and usually the menus will look funky (like images didn't get loaded correctly).
Sent from my EvoLTE so please pardon any typos
So ever since I S-Offed, I've been using it to flash multiple Sense kernels (Bulletproof, ArcReactor, etc.) And I've been experiencing constant random reboots and it then giving the notification that the values weren't applied properly after a bad restart. Is anyone else getting these notifications or are they a product of me constantly flashing one on top of the other (wiping Dalvik cache and cache beforehand though)
Sent from my EVO using xda app-developers app
Oh yeah, I'm currently running Elemental X 4.2 at stock frequencies on the "Erie" I/O and "intellidemand" governor, although even switching it around to the other governor/I/Os are giving me the reboot issues
Sent from my EVO using xda app-developers app
My phone has been acting a lil funny to. Don't wanna bad mouth anybodies kernal, but if somebody out there has the stock kernal for 3.16 I'd be really grateful.
Sent from my EVO using xda premium
Captain Throwback always has something good.
http://themikmik.com/showthread.php...oted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
budeone said:
Captain Throwback always has something good.
http://themikmik.com/showthread.php...oted-Based-on-Latest-OTA-(Odexed-and-Deodexed)
Click to expand...
Click to collapse
Just curious...that thread says 2.13. Is it the same kernal as 3.16?
Sent from my EVO using xda premium
Weirdly enough I think I solved the issue: I've been using No-frills CPU Control for my kernel customizations and always check the "apply at boot" option, I unchecked it this morning and I haven't gotten ANY random reboots. If you have that option clicked, try unclicking it and see what happens, it seems to have solved the problem for me
Sent from my EVO using xda app-developers app
Jason021680 said:
Just curious...that thread says 2.13. Is it the same kernal as 3.16?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
No it's not the same kernel
Sent from my PoS MoPho
Jason021680 said:
Just curious...that thread says 2.13. Is it the same kernal as 3.16?
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Nope, my error
http://themikmik.com/showthread.php...wel-Firmware-Collection-Latest-3-16-651-3-OTA
3.16.651.3 JellyBean OTA
Im trying to use flash gui to get the kernal , but its not working. I tried the boot .img and the full firmware.
Sent from my EVO using xda premium
This one is when I try the boot.img
Sent from my EVO using xda premium
You have to name the file pj75img.zip and boot in boot loader
Sent from my EVO using xda premium
This is with the full firmware
Sent from my EVO using xda premium
budeone said:
You have to name the file pj75img.zip and boot in boot loader
Sent from my EVO using xda premium
Click to expand...
Click to collapse
I'm s-on, that's why I'm trying to use flash image gui
Sent from my EVO using xda premium
Jason021680 said:
This one is when I try the boot.img
Sent from my EVO using xda premium
Click to expand...
Click to collapse
You may have to flash a completely new ROM and just keep it at that (reflash your current Sense ROM and just keep the stock kernel on it)
Jason021680 said:
I'm s-on, that's why I'm trying to use flash image gui
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Did you download the image file or the whole full firmware?
LemonNinja said:
You may have to flash a completely new ROM and just keep it at that (reflash your current Sense ROM and just keep the stock kernel on it)
Click to expand...
Click to collapse
Like a rooted stock Rom right? The trick is just finding one that the kernal hasn't been changed to a custom one.
Sent from my EVO using xda premium
My phone appears to be reporting 51.3 F but I am sure it is C. Could it be a build.prop setting issue?
Sent from my HTC_Amaze_4G using xda premium
bhtm said:
My phone appears to be reporting 51.3 F but I am sure it is C. Could it be a build.prop setting issue?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
are you on stock...? or which ROM currently you running
hatim_rajput said:
are you on stock...? or which ROM currently you running
Click to expand...
Click to collapse
Well I have ORD but ARHD 4 at the moment.
Sent from my Amaze 4G using xda premium
bhtm said:
Well I have ORD but ARHD 4 at the moment.
Sent from my Amaze 4G using xda premium
Click to expand...
Click to collapse
Post it on arhd thread so mike can have a look at it if it's something to do with the build.prop
Sent from my HTC_Amaze_4G using xda premium
bhtm said:
My phone appears to be reporting 51.3 F but I am sure it is C. Could it be a build.prop setting issue?
Sent from my HTC_Amaze_4G using xda premium
Click to expand...
Click to collapse
I'm not too keen on Celsius but if it was 50 Celsius isn't that like on fire?!?
Maybe it's just cold and Fahrenheit? Or a bug/glitch?
Sent from my HTC Amaze 4G running ViperAmaze Sense 4.1.
SuperAfnan said:
I'm not too keen on Celsius but if it was 50 Celsius isn't that like on fire?!?
Maybe it's just cold and Fahrenheit? Or a bug/glitch?
Sent from my HTC Amaze 4G running ViperAmaze Sense 4.1.
Click to expand...
Click to collapse
50C-80C is quite normal for just about any CPU/GPU, whether mobile or desktop running with some load.
This is happening on several stock based ROMs and CM based. After further playing around I suspect the kernel code isn't actually talking to a sensor (or there is no sensor on the Telus Amaze) as the temperature is always 11.3C (and I'm indoors at 20C). Tried several battery apps from the play store.
Just a curiosity, no impact from what I can tell.