Develop Bugs

1.5 or 1.6 ghz kernel?

Is this able to be done and if so how do u go about compiling a kernel??
Sent from my SPH-D700 using XDA App

Yes it is able to be done.
Sent From My Evo Killer!!!

I've seen the 1.8mhz custom kernels over on the EVO SHIFT 4G thread and the stock speed of that kernel is only 800mhz...and if they can push that a whole ghz past its regular operating speed...then I don't think 1.5 or 1.6 would be out of the question...id love to see that (HINT HINT TO OUR DEVELOPERS!! ;-)).

The problem that needs to be overcome with the current 1.4 kernels is that we're already at the top of the voltage specifications for the CPU (per manufacturers dox anyway) to keep the phone stable at 1.4. All chips are a little different - some phones might be stable with less voltage at this freq or others might be able to handle a little more juice. But, we're already at a 40% overclock... How fast do you really need this thing to be?

I personally would not use it if it was overclocked that high. That is to much for it. And the Shift has a different chip in it so it can be different overclock.

Moved to Q&A. And it can be done if you want to fry your phone

Some phones can't even handle 1.2ghz cause of the ****ty silicone on there chips. This includes my phone .
Thomasskull666 as a 1.4ghz kernel released to the public but he has a private kernel at 1.48ghz. He's trying to get a 1.5 for the public. The 1.6ghz we had on eclair was found out to be a placebo cause of error in the coding. With the phone clocked at 1.6ghz it actually ran at 1.0 and the rest of the phone slowed down. It was like those cartoons and you see a man walking at a steady pace but the background was moving at warp speed.
Sent from my SPH-D700 using Tapatalk

That just seems too fast for this phone. Personally 1.2 GHz seems fast enough while 1.3 GHz is just a nice little cherry on top in terms of speed.

Overclocking question, stability?

Okay, so my question is basically how stable is overclocking your g2? I typically keep it at 800 when I use my phone normally, than 1.5ghz for games. I wante d to keep my g2 at 1.5ghz forever.. is that bad?
My battery obviously increases in temp..

I just use 1GH. It's enough for all game now. and didn't see any bad to battery or phone

I've had my DZ for about three weeks now and all this time I've had it consistently overclocked to 1843MHz. At that high of a speed, I had to let the phone cool down after 20 minutes of use.
Just today I flashed pershoot's 1516MHz kernel and noticed no heat issues after ~45 minutes of consistent use (temps < 40C).

I have had my g2 for.... However long they been out. I have always been overclock to at least 1.5 with zero heat issues. I ran 1.8 and even 1.9 for a good long time as well. Those speeds have heat issues ones that required a battery pull a few times because it started heating up faster then i could shut down the phone. If your going to OC at those speeds makes sure you set temp profiles with alarms.
Sent from my HTC Vision using XDA App

ARM processors, like our snapdragons, are a lot more forgiving on the overclocking front than what you might find in your desktop, for instance.
I still treat overclocking on my phone like I do my computers, though... setcpu has a stress test built in that you can use if you're curious how "stable" your overclock is. but in my experience, I've found that you can get away with just playing around with it and using the phone normally and seeing how it reacts to different clockspeeds.
right now, I run it at 1.1ghz (24/7). I have run it at 1.5ghz (24/7) in the past for PSX/N64 emulators, but I've found with my new setup (pretty light; no widgets, very few things going on in the background, stripped as many unnecessary apps as possible, and not using any animations or fancy bits) that 1.1ghz is more than enough to be able to play the games I play on any emulator smoothly.
you should be fine at any speed that is currently available in the overclocking kernels we have with the exception of flippy's 1.9ghz kernel, which does require some monitoring to keep things cool and stable. but it still does vary from phone to phone. if you're running at 1.5ghz and the phone isn't doing anything wonky, then you shouldn't worry about it. if you're running it at 1.5ghz and you're experiencing stability issues, random force closes that aren't fixable through conventional methods, or heat issues, you should probably back off a bit.
some people have problems at 1.2ghz, some people are running at 1.9ghz all the time and never have problems... just find what works best for normal usage with your device and go with it.. it's not like we keep these things for more than a couple of years anyway, and the processor will be capable of handling the [stable] overclock for that period of time.

im always at 1.2ghz. 768 as min, interactive gov (when i use CM7) and battery has been fine, havent noticed any major issues. hard to tell if it was the rom bugs or OC being the issue but from what i read all my issues others have at various speeds so im guessing it was rom related

i think it depends on the rom.
when i use the Pyromod rom i dont need overclock but for other roms like sense roms those I require OC. I always keep it at 1400 when needed.

[Q] Poor GPU performance with my Epic 4g

I'm having some trouble with GPU performance with my Epic 4g on stock EC05 with the Genocide 2.0 kernel.
From my research I conclude that I should be getting ~45-50 fps in nenamark1 v1.6 at stock clocks.
My device can only push out 38fps at 1000mhz and 40fps at 1300mhz - something is wrong here.
I have tried the Syndicate frozen 1.2 rom with the Genocide kernel and achieved the same results. I have since gone back to stock rom.
Does any one have any ideas as to why I am getting such low scores.

yeah i tried on srf 1.2 and actually got 30.3.

ok srf 1.2 oc'ed to 1.4. are you sure your actually overclocking? download a program called cpuspy and see if your actually hitting 1.3
edit: btw i odnt think its possible to get any where near those kind of fps without overclocking..

schnowdapowda said:
ok srf 1.2 oc'ed to 1.4. are you sure your actually overclocking? download a program called cpuspy and see if your actually hitting 1.3
edit: btw i odnt think its possible to get any where near those kind of fps without overclocking..
Click to expand...
Click to collapse
yes, 41.5 fps max at 1.3ghz Something is wrong. shadow Guardian is fairly choppy as well.
My gpu is gimped...

Which Governor? If using "conservative" I don't think it tops 1000 or 1120 even if overclocked to 1400 unlsee you use the very first Voltage Control. Rodderik doesn't support the new Voltage Control or SetCPU. I brought this up to him a while back. He said to use the Voltage Control in the OP of his thread. Just trowing thoughts out there...
Sent from my SPH-D700 using XDA Premium App

I only know how to change the governor with setcpu, I don't see a way to do it with voltage control.

My CPU is fine I think. SetCPU also works fine to change the governor. Running the short bench, the lowest result on stock was about 181 ms. Overclocked to 1.3ghz I got 136 ms.
I'm also getting great speed in CPU intensive applications like the n64 emulator n64oid. GPU limited apps like Shadow Guardian and Quake 3 aren't doing as well.
I wonder if my gpu is somehow on power save mode (if that's possible)
Can someone compare their setCPU short bench results to my score of 136 ms?

dooms33ker said:
My CPU is fine I think. SetCPU also works fine to change the governor. Running the short bench, the lowest result on stock was about 181 ms. Overclocked to 1.3ghz I got 136 ms.
I'm also getting great speed in CPU intensive applications like the n64 emulator n64oid. GPU limited apps like Shadow Guardian and Quake 3 aren't doing as well.
I wonder if my gpu is somehow on power save mode (if that's possible)
Can someone compare their setCPU short bench results to my score of 136 ms?
Click to expand...
Click to collapse
More or less what I'm getting. I doubt your gpu is gimped man. And your cpu is deeply integrated with your gpu. Don't think of it like a desktop setup think more like a laptop. Where the gpu is supplemented by the cpus power. 41-44 fps would be normal for 1.3 ghz. What I get at least.
cd's or tapes?

I know a hell of a lot more about notebooks than I do about android phones, and even integrated graphics chips are independent from the CPU. Sure they may be manufactured on the same silicon with the cpu but they can be clocked independently (and even turned off).
The problem with the epic - and android by extension - is that you don't have direct access to the GPU or its driver. I've read that some kernels for certain phones can allow you to overclock the GPU; though none exist for the epic. An yes, I know about chainfire3d, and it's not really a 'driver'.
At least battery life is good for me...

dooms33ker said:
I know a hell of a lot more about notebooks than I do about android phones, and even integrated graphics chips are independent from the CPU. Sure they may be manufactured on the same silicon with the cpu but they can be clocked independently (and even turned off).
The problem with the epic - and android by extension - is that you don't have direct access to the GPU or its driver. I've read that some kernels for certain phones can allow you to overclock the GPU; though none exist for the epic. An yes, I know about chainfire3d, and it's not really a 'driver'.
At least battery life is good for me...
Click to expand...
Click to collapse
As far as I know, this might be exploitable in GB, which is why you are running into problems.

The Root said:
As far as I know, this might be exploitable in GB, which is why you are running into problems.
Click to expand...
Click to collapse
can you please elaborate?

dooms33ker said:
I know a hell of a lot more about notebooks than I do about android phones, and even integrated graphics chips are independent from the CPU. Sure they may be manufactured on the same silicon with the cpu but they can be clocked independently (and even turned off).
The problem with the epic - and android by extension - is that you don't have direct access to the GPU or its driver. I've read that some kernels for certain phones can allow you to overclock the GPU; though none exist for the epic. An yes, I know about chainfire3d, and it's not really a 'driver'.
At least battery life is good for me...
Click to expand...
Click to collapse
What you said about graphics chips might be true.. But it still doesn't change what I said. The problem is not with your gpu. Its with your settings. You may prove me wrong, but what I said is that your gpu directly relies on your cpu. That's why you get a better framerate when you overclock more. Chainfire has nothing to do with this.. I'm sure you know this but its purpose is to fool games by converting "commands" for a certain gpu into another and downsampling textures, etc so that they can run more efficiently on our chips. Ask anybody else what they're getting on that bench and they'll tell you similar numbers at the clocks we discussed. Btw I'm not sure but I think the gpu drivers for our phones might be closed source. Which would explain why oc'ing our gpu would be impossible without custom ass drivers built from the ground up.
cd's or tapes?

OC'ing

What's a safe level to overclock my phone to? I'm running the latest MIUI (1.9.16) with the lastest Tiamat kernel (1.1.3) I'm at about 1344 MHz right now. Can I go much highter?
Sent from my rooted, MIUI DInc2

From my testing, I've found there isn't to much to be gained going over 1.6ghz.
For a safe level I keep mine at 1.2 ghz. This has worked out well for me. Try different frequencies and see what works out for your needs.

I'm running JDKernel with the max set at 1.5 ghz, using the smartass governor. When I look at the "time in state" info, it usually shows about 75% of my time spent at 768 mhz. Seems to be working great.
Sent from my Incredible 2 using XDA App

Well, I tried bumping it up to 1.6, and I locked my phone and the screen turned off, but the keys stayed on, and it wouldn't come back up. So I pulled the battery and went back to 1.3 like it was before. Now its working great. I'm on smartass v2
Sent from my rooted, MIUI DInc2

If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .

PacerguyDon said:
If your having lockups, try installing Incredicontrol from the market and bump up the voltage on the higher frequencies 25-50mv, this should keep you from locking up. I do this when I use the performance governor and want to run Quadrant or Linpack .
Click to expand...
Click to collapse
I've been using SetCPU, cuz I couldn't understand Incredicontrol..... What's ideal if I'm running around 1.6 for voltage?

On the Jd Kernal, I'll bump it up to 1450 and go from there.

PacerguyDon said:
On the Jd Kernal, I'll bump it up to 1450 and go from there.
Click to expand...
Click to collapse
So, you don't know about for Tiamat? I'm using that one.
Plus, would anyone recommend using his Incredikernel as well?

I'll go about the same on the Tiamat. I usually will start at 50 mv over whatever the stock setting is on the kernel when running performance runs.
I didn't know that Chad had done a Kernel for Aosp romed Dinc2's. I know his Dinc1 Kernels were great.

I accidently had my phone at 1.9 for a day running jdkernel, no crashes or anything
Atm when my phone is charging, it gets bumped up to 1.4 and i have no issues at that speed.

Is the phone stable when overclocking past 1.3ghz?

I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?

iArtisan said:
I heard there was a problem with stability issues before. Has it been fixed?
Also, do any of you guys feel the need to OC in the first place?
Click to expand...
Click to collapse
I tried OC'ing to 1,4 for a short time, didnt get any instabilities.
Which leads me to question two. No I don't feel the need to OC this phone, it is still good enough to cope with everything i throw at it.

The worst that will happen is that it will run a little hotter than normal. I was running Trinity Kernel on RasCream ROM clocked at 1.5GHz and it was fine, nothing crashed, no reboots, all was well.
Besides; It's a Nexus, it was built for this!

This varies for everyone
Sent from my GT-I9300 using Tapatalk 2

Meh. It all varies. No 2 chipsets are the same. What may work for someone else may not work for you. Trial and error is the only surefire way to find out.

Hi,
I agree with what has been said above, all the CPU's are not equal but actually the progress made by the kernel devs allows all (or almost) phones to run at 1.3* Ghz (1.34/1.35 Ghz, it depends of the kernel) without any issues.I think it's for all, actually I don't remember a user with issues at 1.3* Ghz...
And for most phones 1.5 Ghz is fine.For some others, above 1.5 Ghz is problematic but it depends also of too many factors.
Now it's not like it when the Genx came out, where 1.3 Ghz was the limit of CPU overclock for all the phones.
And many people can run stable at 1.65 Ghz, also it depends of the kernel.
For me for example my max CPU freq usable each day, so stable is 1.72 Ghz with Glados kernel, above (like 1.8 Ghz) it runs fine for 30 mins, sometimes 1 hour, but after always freeze/reboot... maybe my CPU can't reach this CPU freq or maybe my settings are wrong (voltage) ...
I agree, an extreme overclock like 1.72 Ghz is not really necessary for all day (heat, battery life, etc...) but a little overclock like 1.5/1.53 Ghz and you a difference in certain case (openning some apps, general UI, browsing, etc...).
But if we have the ability to test and play...why not... ,in any case for me it's yes, I like overclock and test the possibilities/limits of my phone, different settings...
Everyone does as he wants and it depends on what you want (battery life,a little more power in some situation like playing or a higher bench score ).

Well considering Texas instruments recommended highest clock speed for this processor is 1.5 ghz I'd say your fine. Anything above that is dependent on how well your chip set will handle it. Besides who honestly has needed to OC for anything other than benchmarks?
Sent From My Sprint Galaxy Nexus