Develop Bugs

[Q] Why is the newest Netarchy Kernel making my Stock Root Rom's FPS WORSE?!

Can anyone help me out?
I'm running stock rooted 2.2 (deodexed) and flahsed over the 4.0 zip... and the scrolling is choppier than all hell. I re flashed the stock kernel, and it was back to being fine again. So, I tried again, with wiping the caches first, and still choppier than all get out when I flashed the kernel.
It's definitely the right kernel, but what the hell am I doing wrong here? Any help would be appreciated.

And, I'll even throw in 5-10 dollrs for someone who can give me an answer that works.

This could be because of the new settings he just changed. Try the download that is 4.0.2 and not 4.0.3, or try overclocking your processor to 1.2GHZ with OC widget or SetCPU.

What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.

Ok, so I installed 4.0.2, and it seems to be running better, but still some choppiness on the menu up and down scrolling when "all apps" is opened.
I have no idea how to use SetCPU (noob yep... graphics guy... not a tech guy_, so I took a screen:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Wpould you mind just telling me where the sliders should be?

nukedukem said:
What kind of screen do you have? If you have a Nova panel, you may need to adjust T2 values to get the best performance. Just my 2 cents.
Click to expand...
Click to collapse
I have a Nova, but, I have no idea what T2 panels are and how to adjust them. If you could point me to the right app or direction, that'd be awesome. I'll donate to you as well if it helps.

There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
There's an app floating around here called NovaFreq formerly evoswitch. It allows you to change the panel frequency to improve fps. Everyone gets different results. 450ish was usually the best for me. Basically trial and error. Most haven't needed it with recent kernels though. As for setcpu, the higher the max frequency the better fps performance, but overclocking comes with some risks. Im usually underclocked at 576max / 245min. You can also set profiles to run certain speeds when screen off, charging, etc. Helps a lot with battery life. I would move your max down to 998 or 1113 and min to 245. Ondemand is usually a good scaling setting. Hope this helps.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.

Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app

dglowe343 said:
Glad to help. Feel free to send my donation to one of the developers on this forum. Without them I wouldn't have known any of that.
Sent from my FROYO'D EVO using xda app
Click to expand...
Click to collapse
Good ****
Sent from my PC36100 using XDA App

TJDuckett said:
Wow thanks. I downloaded nova frequency, but just left it at default, and changed the setcpu, bc I was getting random reboots with the overclock. I also set profiles to way lower when the screen is off and the phone is at lower battery percents.
This phone officially runs like it's on crack now. Good stuff.
Guys, PM me ur paypals, and I dont' mind donating a few bucks tomorrow.
Click to expand...
Click to collapse
LOL bro. Not only did I tell you to use NovaFreq, but I also told you not to use SetCPU. You were getting reboots b/c it was set too high and you don't want to set it below 245 when screen is off. I don't think SetCPU is so great for *most* people. I could have helped you on GTalk and taken your money...gladly would have

(Answer) possible fix for phone not waking.

In my quest to figure out why my phone will not wake after sleeping for 5 minutes on a custom kernel like vision, genocide or twilight I have solved the issue.
The issue is that some phones like mine do not undervolt very well at 100mhz. I use setcpu to change my scaling to 200/1000 instead of 100/1000.
The issue is even setting setcpu to 200 minimum it still defaults to 100mhz when the phone is in a sleep state. To combat this problem 100mhz needs to go.
The simple fix is this, set a profile in set cpu as follows.
Screen off maximum-200mhz
Screen off minimum-200mhz
Governor-ondemand
Priority-100%
As you can see from my screenshot of cpuspy 100mhz is rarely being used now. I hope this fix works for others so to the users having the no wake after sleep try it out and report back with your results.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Its been a whole day and I have not had a single issue with the phone not waking from sleep. So far so good.

I've done this exact same thing,my brothers epic still freezes over night (while him/his phone sleeps),but mine has been rock solid now,only problem is I like 100mhz at sleep; I used to set setcpu 100mhz-200mhz screen off/priority 100%,this seemed to make the lock screen smoother on wake,ohwell,I won't fight progress
Sent from my SPH-D700 using XDA Premium App

I never had a problem waking on Bonsai 4.0.1 at 100mhz. Now that I'm on ACS I had to switch to 200-1000 or I would have a huge slow down. Although even at 200-1000 ACS is still givng me better battery life.

Battery life is better,but I would like to see 100mhz at stock voltage...
Edit::: In the middle of me typing that,the phone froze,setcpu 200mhz-1000mhz,newest Twilight kernel,so now I'm guessing my phone dosnt like to be under-volted very much...
Sent from my SPH-D700 using XDA Premium App

This fix is not for the freezing condition. This fix is for the phone not waking after going into a sleep state.
Just setting 200/1000mhz in setcpu doesn't work as it will still use 100mhz when the screen is off. This is why you should set a screen off profile of 200/200 to force the phone to use 200mhz during a screen off sleep state.
Before I did this I could not use any kernel without having to pull the battery every 10 minutes due to the phone not waking up.
With my method I have had zero wake issues and am running 1400mhz as well on vision 1.1
Here is a screenshot of how I have the profile set up.

The Genocide 1.0 OP recommends NOT using setcpu, instead they recommend Voltage Control. They have a whole mini tutorial of how to use it in their thread. See my sig for quick access. You can also disable 100mhz all together (which is what stock settings without any root does) Your Epic CPU is only supposed to be 200/1000. So you can use Voltage Control to set what levels you want your cpu to have access too. It is quite useful. I have still had an occasional SOD problem. I have noticed that the processor jumps quickly when waking up, so perhaps it is both an underclocking issue for you (with setcpu) and an under volting issue for me. I will see, but I hope this helps.
Edit: there is no difference between 100Mhz and 200Mhz as they both use the same voltage.

So setting it to 200 wont help battery? I should just leave it to 1000/1000?
Sent from Snarf high on SRF 1.02 till freezes are fixed

Censura_Umbra said:
The Genocide 1.0 OP recommends NOT using setcpu, instead they recommend Voltage Control. They have a whole mini tutorial of how to use it in their thread. See my sig for quick access. You can also disable 100mhz all together (which is what stock settings without any root does) Your Epic CPU is only supposed to be 200/1000. So you can use Voltage Control to set what levels you want your cpu to have access too. It is quite useful. I have still had an occasional SOD problem. I have noticed that the processor jumps quickly when waking up, so perhaps it is both an underclocking issue for you (with setcpu) and an under volting issue for me. I will see, but I hope this helps.
Edit: there is no difference between 100Mhz and 200Mhz as they both use the same voltage.
Click to expand...
Click to collapse
Im using vision kernel and this worked for me since voltage control is not compatible with vision kernel.

churro7 said:
So setting it to 200 wont help battery? I should just leave it to 1000/1000?
Sent from Snarf high on SRF 1.02 till freezes are fixed
Click to expand...
Click to collapse
Why would you set 1000/1000. Set 200/1000

Interesting, gonna give this a shot. I have the same issue on every kernel I've ever used.

tenaciousj said:
Interesting, gonna give this a shot. I have the same issue on every kernel I've ever used.
Click to expand...
Click to collapse
Hope it works for you as my phone is the same way.

Seems to work so far...

tenaciousj said:
Seems to work so far...
Click to expand...
Click to collapse
Good deal..

Kernels Overclocking/Voltages/Governors

Morning guys. I think I've clogged up Agats kernel thread enough with this so figured I should hop on over here and ask about what's going on.
First of all a big thanks to the few kernel devs we have over here. I understand that we did just recently get source so I'm not blaming anyone for the issues I'm encountering.
All I've been trying to do these past few days is see how far I can max out this phones performance. I'm not concerned right now with battery life. I live in a God awful data/signal area... but since source has dropped I have noticed without even touching a single setting improvements in performance.
So all I've been trying to do these last few days is overclock to 1.4 and KEEP it at 1.4 while my screen is on. I've mostly been using Tegrak Ultimate and Voltage Control and staying at Performance gov. From what Voltage Control is telling me though is the majority of the time I'm stuck at 800 MHZ. Very rarely am I at 1.4 and not only that the phone is barley ever at 500MHZ or 200MHZ. I've tried overvolting up to +75 across the board but that hasn't changed anything. I've tried different Schedulers and have seen a little improvement using CFQ. I've kept my governor at Performance.
I've never really been a big overclock guy. This just started as me seeing how far I can push this phones performance without it melting in my hands. LOL. Now though I'm just trying to learn and or understand why 96% of the time I'm sitting at 800mhz.
Thanks in advance for any feedback and especially thanks to Sleshepic, Agat, and RJ for the work they've put into these source kernels.
I've included a number of screenies..... sorry they are kind of random but it's what I've been posting in Agats thread..... but it gives you the general idea of what I'm getting at.
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SPH-D710 using xda premium

what ROM are you running? it would seem like you have conflicting scripts running. like a script which is preventing you from using certian steps. And even capping you at 800MHZ. Have you tried a full wipe then flash your rom and agat's kernel again? just wondering if there is a left over script from a perivous rom or battery saver mod. I have been following you on the kernel thread. hell, Ive been using google this to see if i can come up with something. thats I have right now.
link for reading: http://www.setcpu.com/documentation.html

g_ding84 said:
what ROM are you running? it would seem like you have conflicting scripts running. like a script which is preventing you from using certian steps. And even capping you at 800MHZ. Have you tried a full wipe then flash your rom and agat's kernel again? just wondering if there is a left over script from a perivous rom or battery saver mod. I have been following you on the kernel thread. hell, Ive been using google this to see if i can come up with something. thats I have right now.
link for reading: http://www.setcpu.com/documentation.html
Click to expand...
Click to collapse
Thanks man. You might be on to something there. I'm going to look further into scripts and how they may conflict with Tegrak/Setcpu/Voltages.
This could very well be the issue...... I can't think of anything else it could be.
Thanks again.

caspersfi said:
Thanks man. You might be on to something there. I'm going to look further into scripts and how they may conflict with Tegrak/Setcpu/Voltages.
This could very well be the issue...... I can't think of anything else it could be.
Thanks again.
Click to expand...
Click to collapse
No problem. im also checking it out as well. I'll keep ya informed as what else i could find.
Go team venum! lol

Well I'm not getting anywhere on this. A few days ago I was testing Manufan's Hooligan ROM(awesome ROM by the way) then did a fresh install over to Mijjah's Goodness ROM. I just asked in his thread and Rwilco12 said there isn't a script in the ROM. He thinks there may be some apps conflicting.
The only thing I have left to do is another fresh install. Judging by the lack of responses in this thread I may be the only one having this issue.

do you have multiple OC apps? like i had to delet Rom tool box when I started using voltage control. same way when I had tagraz. I beleive you can only have on OC app at a time as they will conflict by trying to gain control over the CPU.

Yeah I'm running 0.2.3 and here's mine.
Sent from my SPH-D710 using xda app-developers app

g_ding84 said:
do you have multiple OC apps? like i had to delet Rom tool box when I started using voltage control. same way when I had tagraz. I beleive you can only have on OC app at a time as they will conflict by trying to gain control over the CPU.
Click to expand...
Click to collapse
Well I have Rom Toolbox Pro but I'm just using that to change my font. I have Setcpu frozen thru TB and just using Tegrak Ultimate.
When I get home from work later I'm going to do a fresh install. Use Rom Toolbox Pro to change my font then freeze it. Then just use Tegrak and not install Setcpu.
See if that does it. Thanks again for your feedback.

caspersfi said:
Well I have Rom Toolbox Pro but I'm just using that to change my font. I have Setcpu frozen thru TB and just using Tegrak Ultimate.
When I get home from work later I'm going to do a fresh install. Use Rom Toolbox Pro to change my font then freeze it. Then just use Tegrak and not install Setcpu.
See if that does it. Thanks again for your feedback.
Click to expand...
Click to collapse
no problem. just something i was thinking about.

[APP] SU Root Tools

***THIS APP NEEDS A ROOT PHONE***
This app includes root tools that you can use with a simple click. Its currently under development, this means that it will get new things added.
***INCLUDES***
Reboot
Reboot in Recovery Mode
Reboot in Bootloader Mode
Quick Reboot
Power off your device
Wipe cache and dalivk-cache
Wipe dalvik-cache
Wipe battery stats
wipe cache
Free up RAM
backup bootanimation
install bootanimation
Save a LogCat
Save App specific LogCat
Turn On/Off CPU2
Kernel mods:
1. Overclock
2. Select Governor
3. Governor Settings for:
---EVERY GOVERNOR (PLEASE REPORT IF IT DOESN'T WORK)
***ONLYE FOR GALAXY NEXUS AND GALAXY SIII***
CPU temperature notification.
I will add more and more features.
Download now from PLAY STORE!!!

Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2

Really nice stuff! If I were you, I'll add extra features that no other competitors have
Swyped on my Galaxy Nexus running AOKP with Franco Kernel

very good work, compliments!!

Version 1.5
Changed orientation to portrait. Added a bootanimation preview button. Easier file chooser for bootanimation. Completely different look for kernel mods. App more user friendly. Fixed some minor bugs. Removed some unused toast messages.
Need some test for bootanimaton preview. Please report back

Updated to latest, Version 1.6, with many fixes

unforgivenmercy said:
Looks good thanks. Will helping testing as much as possible.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Could you try the cpu temp notification, just turn it on and off like 10 times and tell me if you get any FC or if its not showing.
Thanks

Version 1.7
A lot of bug fix. Fixed governor settings not applying, added a check box to set governor at boot, fixed clear cache for ROMs that doesn't support it, fixed crash for CPU temp notification, fixed loop when device can't reboot, clear cache, etc. Added GSF id and System id info, (Will just show it to you).
Click to expand...
Click to collapse
If anyone get any other FC when enabling CPU temperature read, please report it again, since it should be fixed. Thanks.

New version with Rom management. Only available for CWM Recovery!!

I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus

The Gingerbread Man said:
I think you have a minor typo in OP 'turn off CPU 2' should be 'turn off CPU 1' as cores are CPU 0, CPU 1 (duel core) then CPU 2 and CPU 3 (for quad core device)
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.

Rotary Heart said:
Yes I know that, but for not developers people seeing a number 1 is like the first CPU will be off. Since you normally start counting with the number 1. I did name it number 1 in one of the tests and I received a lot of e-mails asking me if its safe to turn off the first CPU and why I'm not doing it with the second CPU. So I decided to change the number so that way people wont get confused.
So basically you are right, but I did it on purpose.
Click to expand...
Click to collapse
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus

The Gingerbread Man said:
I see and no worries I was just checking, I don't intend on using this but just wanted to make sure you knew the correct labeling for the cores
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Thanks anyway

[Q] One X overheating and not going into low cpu speed - Trickster MOD

Hi there!
I have 2 HTC One X, one of them is overheating in normal use and the other, with exactly the same use, is not.
I mean normal use by 10 minutes on facebook, 5 min on e-mail program, 5 min on internet browser.
Both have the same stock ROM version with Android 4.1.1, HTC Sense 4+, Software Number: 3.14.707.24.
During the tests they were not charging, almost same battery level and same installed and running apps. Also were purchased the same day in the same store. The only things that actually changes are the accounts, contacts and other personal data.
After use I have checked on Trickster MOD app to compare the temperature. And the Hot One X was really hotter, as expected:
- Hot One X:
Battery temperature: 42ºC Health: Good
CPU temperature: 52ºC
- Other One X:
Battery temperature: 35ºC Health: Good
CPU temperature: 39ºC
But, besides that, I saw something odd on the "Hot One X", it was not going into low cpu speeds.
Trickster MOD says:
Not Used States
51 MHz, 102MHz, 204Mhz
This explains why is getting hotter.
Also this is only happening on the "Hot One X", on the "Other One X" the Not Used States list is empty.
Here is a screen shot of the Hot One X:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Also, comparing to the "Other One X", the 340Mhz cpu speed is much less used on "Hot One X", what means it uses more higher speeds. There was no lags on neither phone.
So my question is:
Is there any way to make it use also the low speeds? I mean, is there any configuration for this?
I think that maybe there is some way to enable/disables cpu speeds, or make a profile: uses more that, less that.
If that is true, how to do it?
Thanks

anyone have any ideas?

Anyone facing the same issue? Install trickster MOD free from Play Store and check your One X

Which governor are you using?

TToivanen said:
Which governor are you using?
Click to expand...
Click to collapse
Both using "ondemand", but I tried "conservative" too and the same issue. Also I tried "powersave", but both devices became so so lag that I couldn't even open any other app (about 5 seconds to scroll down a page) so I selected "ondemand" again.
The overheat was happening on the Hot One X since the Jelly Bean update, even before Root Unlock and Trickster MOD. The Trickster MOD just helped me to guess what was happening.

tried factory reset already?
Reflashing rom and kernel might help
Or a simple RESTART might help too.

miHah said:
tried factory reset already?
Reflashing rom and kernel might help
Or a simple RESTART might help too.
Click to expand...
Click to collapse
Yes, I've tried factory reset 2 times with Jelly Bean.
Haven't tried to reflash the rom, I'd like to use the original rom Jelly Bean or ICS, is that possible?
Isn't there any configuration for enable/disable cpu speeds?
Restarted several times using: turn off / turn on, restart from menu, turn off / hold power button for 20 sec. (slow startup), disable fast boot and restart.
Thanks

Any more ideas?

maybe you had mods installed on the other one? i had this before the cpu wont go down 1.5hz and then it over heats

Sorry, what mods do you say?
By the way, both devices were hard reseted and were installed exactly the same apps.
Isn't there any way to enable/disable cpu speeds? I guess it should be that somehow, maybe failure applying htc rom update.
Jimboi2008 said:
maybe you had mods installed on the other one? i had this before the cpu wont go down 1.5hz and then it over heats
Click to expand...
Click to collapse

Maybe mods like changing build props etc or sound mod or mods that changes framework my suggestion flash a rom without any mods then check and see if itll fix it.

Jimboi2008 said:
Maybe mods like changing build props etc or sound mod or mods that changes framework my suggestion flash a rom without any mods then check and see if itll fix it.
Click to expand...
Click to collapse
It's a stock Jelly Bean rom, original, never flashed any other ROM. It's rooted right now, but the issues appeared before root.

Maybe u can try to flash new kernel or better yet flash stock rom again see if it still like that.

Jimboi2008 said:
Maybe u can try to flash new kernel or better yet flash stock rom again see if it still like that.
Click to expand...
Click to collapse
I'll try that, do you know where I can find the stock rom and instructions for flashing it? Thanks