Overclocking 825Mhz attempt - Sony Ericsson XPERIA X10 Mini

I'm gonna try this on my Mini but I have a question. Can my battery/cpu melt by running 825Mhz or higher than 729Mhz?

I also run 122Mhz as lowest

I've gone 781, thats about all the balls I have to go up to. Device is still perfect.

good luck! let us know how it went

Theshawty said:
I'm gonna try this on my Mini but I have a question. Can my battery/cpu melt by running 825Mhz or higher than 729Mhz?
Click to expand...
Click to collapse
No dude.....if ur CPU is not capable of it, it will go into an infinite loop which can be easily restored by xRecovery, that all.
__________________
If you like my post, thank me!
X10 Mini: Android 2.2.1 (MiniCM RC2 by nobodyAtall).

Yeah :\
Phone went into an infinite loop, but I wiped settings in xRevovery...

i see that the cellphone cpus are the same with the desktop/laptop ones. some can take more heat, some not. mine is stable at max 749. once i go a step up, it will freeze when doing some task. tried 825 and it freezes as soon as i hit apply.

yea... same thing here... when I set 825MHz it frozes few sec later... and phone restarts and works normaly on 720MHz...

I once accidentally set my frequency to 825mhz in SetCPU(damn those sliders) but switched it back to 652 mhz like, instantly, and there was no damage done. =D

Yeah, also tried that. It instantly froze and gave me a bootloop. Mine is stuck @ 710MhZ default setting ^.^
Sent from my X10mini using XDA App

Yours is stuck at 710 mhz? You have to use No-frills Cpu to set or just use SetCPU, you cannot change them through performance settings.

aloy99 said:
Yours is stuck at 710 mhz? You have to use No-frills Cpu to set or just use SetCPU, you cannot change them through performance settings.
Click to expand...
Click to collapse
This is false. You should be able to change them directly through CyanogenMod CPU settings..

Mine can pull 748 max, anything higher and it reboots, no bootloop though as always turn set at boot off for testing frequencies
Sent from my X10mini using XDA App

aloy99 said:
Yours is stuck at 710 mhz? You have to use No-frills Cpu to set or just use SetCPU, you cannot change them through performance settings.
Click to expand...
Click to collapse
No Sorry, I didn't mean that it really stuck, of course I can change them.. but mine is set at default settings.
I also tried setting it to 768MhZ but gave me frequent reboots. So I just set it to default
Sorry for bad english..

NO NO NO,
it overheats the phone and moreover that speed is unnecessary

Overclocking is logarithmic in terms of overall system speed. Running the clock at 800mhz isn't double the speed of the processor at 400mhz, the advantage gain compared to even 700mhz would be miniscule. The processor would most likely become unstable and result in a much poorer performance than default clock speed.
Sent from my U20i using Tapatalk

obsidian_eclipse said:
The processor would most likely become unstable and result in a much poorer performance than default clock speed.
Click to expand...
Click to collapse
and later we have to change the phone itself (result of a big hole)

Heres my overclocking results, i used quadrant to benchmark, I'm running 787mHz no problem, is this around normal results ??? would just like to know incase its not performing properly
{
"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"
}

banari.sushanth said:
NO NO NO,
it overheats the phone and moreover that speed is unnecessary
Click to expand...
Click to collapse
At 710mHz ("remember on boot" option enabled) the phone works like a charm compared to the factory 600mhz frequency, which is awful - the phone is slow like a running snail!
Over 710mHz when I turn on "remember on boot" option, after a reboot the phone goes to a bootloop, from which I can not escape even with Xrecovery simply because I can not enter the Recovery module at all.
Over 710Mhz even with the "remember on boot" option disabled, to avoid the bootloops after restart, the phone is too unstable and the positive effects from the overclock are much less than its advantages.

banari.sushanth said:
NO NO NO,
it overheats the phone and moreover that speed is unnecessary
Click to expand...
Click to collapse
Strange as my phone runs 787mHz without even a sniff of temp rise or freezing, and that's even with extreme usage
Sent from my U20i using xda premium

Related

[MOD] Galaxy S II Overclocked to 1.5GHz: 4000+ in Quadrant!

I have successfully overclocked the new Samsung Galaxy S II to 1.504GHz. This speed is enough to allow it to achieve really high benchmark scores like over 4000 points in Quadrant! 1.5GHz is a 25% overclock and makes this fast phone even faster and snappier in day to day usage.
Instructions:
1. You'll need the latest version of odin3 and the USB drivers for Windows. jutley's post on debranding the phone has links to both: http://forum.xda-developers.com/showthread.php?t=1064894
2. Grab the kernel. It is a tar file for odin with the overclocked kernel and a initramfs with proper modules for the kernel: http://setcpu.com/files/galaxysii_oc_v1.tar
3. Reboot the phone into download mode using ADB:
adb reboot download
4. Flash the kernel using odin3 by placing the tar file in the PDA section and pressing "Start."
5. The phone will reboot automatically.
6. Use SuperOneClick to root your phone if you haven't already. ADB should have root access with this kernel so it'll just work.
7. Grab SetCPU and try 1.504GHz.
Source code (with relevant commit for the overclock. I also enabled the interactive governor in the config): https://github.com/coolbho3k/galaxysii_oc
I haven't gone crazy on the voltages - 1.504GHz is stable at 1375mV on my device. Depending on your device, there may be even more headroom. I've gotten speeds of up to 2GHz to boot with instability (my unstable 1.8GHz Linpack run is currently in the Linpack top 10), but at very high voltages and temperatures. Leave it up to other developers to give you higher/more dangerous frequencies and voltages. If you stress the CPU a ton the phone will become hot to touch (though it does to a certain extent even at stock frequencies - there is not much thermal insulation between the processor and your hands in such a thin phone).
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
The usual disclaimers apply here. Only do this if you know what you're doing. Though the long term stability/reliability of similar overclocks on other Android based ARM devices is known, this software is provided with no warranty, and I can't be held responsible if you fry your device.
Video:
A 1.504MHz overclock:
{
"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"
}
...breaks over 4000 points in Quadrant:
...and almost 60 MFLOPS in Linpack:
Since Linpack and Quadrant aren't (sufficiently?) multithreaded, you won't see that much improvement over single core Cortex A8 devices at the same clock. But these are dual core phones!
Developers: keep in mind that the Galaxy S II source currently "fixes" voltages on this revision of the Exynos to be 25mV less than what is in the table. Upon boot, the driver will actually print the real voltages at each level (look for ASV voltage_table in the kernel log) if you don't know which chipset revision a particular phone has. The overclock itself is controlled in the s5pv310_apll_pms_table.
Enjoy!
Damn .........
This is when I really wish I had a SGS2. Can't wait till it comes to American shores, great work coolbho, see you on Engadget tomorrow..
OMG already? I was wondering when this would happen. God bless you man.
Wonderful work man. Can't get Odin to download on my home rig so I'll be playing around w/ this tomorrow at the office With overclocking already here and the inevitable kernel optimizations to come, this phone is truly going to be the beast everyone suspects.
Thanks man!
..and what about undervolting?
WOW, nice work
Thanks!
Holy crap, nice work! How much hotter is it getting in the back of the phone at 1.5ghz?
Sent from my GT-I9100 using Tapatalk
Very good job here mate. It's about time somebody attempted to overclock such a sweet phone.
I will flash this with Odin tonight.
Again, great job & thanks
Not bad eh?
rovex said:
Not bad eh?
Click to expand...
Click to collapse
how you getting that score im getting just above 4000
Haha well played
coolbho3000 said:
Current features in this kernel: Added 1.504GHz overclocking step (default frequency is still 1.2GHz for safety - use SetCPU to safely raise the frequency) and relevant modifications, 800MHz sleep death fix, interactive governor, ro.secure = 0.
Click to expand...
Click to collapse
What is the 800MHz sleep death fix?
Can someone run this overclock against AnTutu Benchmark as well please ....i find this a little more stable than quadrant.
Ty
S
Sent from my GT-I9100 using XDA App
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
MrDeacon said:
Very impressive indeed. The only question that comes to mind is if there really is a need to squeeze out higher frequencies. The CPU isn't really a bottleneck on the SGS2, is it?
Click to expand...
Click to collapse
CPU is always a bottleneck for calculations. Probably not a bottleneck in most apps though.
My install went smoothly. Quadrant showed 4144, 3892, and then 4100. Im going to try running it throughout today and see what happens. Cant wait for this to mature.
WOW.! Flashing right this second.! You people are geniouses.!
Sent from my GT-I9100 using Tapatalk
just wanted to add
oh crap.. i just realized who posted this, its Mr. Overclock himself, the creator of SetCPU... woo we have a star in our mits!

[Q] Only one core going upto 1.512GHz

ok i've done everything apart from muffle system logging and max blocker (both fail to install for some reason =S ) , BUT in Govnah the 1st core shows the speed of going upto 1.512GHz, but the 2nd core doesn't go higher than 192MHz...why is that??
ace9988 said:
ok i've done everything apart from muffle system logging and max blocker (both fail to install for some reason =S ) , BUT in Govnah the 1st core shows the speed of going upto 1.512GHz, but the 2nd core doesn't go higher than 192MHz...why is that??
Click to expand...
Click to collapse
It only goes up if it needs it to perform some task. If you're sitting there watching it, it won't go up as it is not needed.
That is a power saving feature of dual cores.
yh but the graph that shows it hasn't gone higher than 192MHz for a while...wheras the 1st core keeps cycling at many different speeds, and i've run everything to get that second core going...but it still won't
What kernel? This has been a known issue with f15. Change the govenor to "ondemand" instead of "ctlondemand". I switched to warthog and dont have the issue anymore.
BTW....not saying its better. Just works for me
using the F4 kernel, both cores will run at the max speed you put, and when it's idling and not doing anything, will run at the lowest speed you put. I totally recmomend it. make sure you leave what ever governer is on the f4 kernel, if you don't, then the second core will stay at the min speed you put, thus not doing much.
thebadfrog said:
What kernel? This has been a known issue with f15. Change the govenor to "ondemand" instead of "ctlondemand". I switched to warthog and dont have the issue anymore.
BTW....not saying its better. Just works for me
Click to expand...
Click to collapse
i'm using uberkernel 22- on demandtcl 1512
go play a 720p YouTube video if fits smooth then everything's fine. I don't get peoples obsession with needing it to go up and down.
durps said:
using the F4 kernel, both cores will run at the max speed you put, and when it's idling and not doing anything, will run at the lowest speed you put. I totally recmomend it. make sure you leave what ever governer is on the f4 kernel, if you don't, then the second core will stay at the min speed you put, thus not doing much.
Click to expand...
Click to collapse
f4 is working really nicely over 2 weeks now. 1.8 both cores. set the min the lowest. still all day battery life.
3 words "Lithium ENYO BenchMark"
test and report your 2nd core activity via govnah... (running in background during test)
edit: "Lithium ENYO BenchMark" eh.... its ok at getting a result but not as much as some more mainstream activities and i now question its "bench marking validity". but the 2nd core is obviously active
look closely as the graph moves quicky depending on your settings
---------- Post added at 04:36 AM ---------- Previous post was at 04:21 AM ----------
i get mixed results but i always see activity from core 2
{
"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"
}
the 2nd is actually while playing a 720 vid
both using "uber kernel" ondemand not the ondemandctl

benchmark scores antutu

What's everyone getting on which ROM, kernel and CPU oc/uv program?
(not sure if this belongs in Q/A or not )
I just got 3799 using the set up below and CPU tuner + virtuos overclock , I got 5000 odd yesterday ?
I still ain't getting any more than 3900 , even uninstalling virtuos overclock controller for sleep n wake, and setting my pc to full power , with my brightness down and all tasks killed in taskmanager.
Try backing down the frequency you set your processor to. I get crappy scores at 1.86 but over 6000 at 1.78. Every chip is different.
What is your setup?ROM,Kernel and mods?Im running Eternity 1.4 w/ziggy's latest kernel and no other mods. Ive gotten [email protected] (reboots at 1.8ghz) and just tested now, [email protected] Try playing around with the governor, Im using setcpu with lagfree.
{
"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"
}
1.78ghz stock de-sensed
Infected ROM eternity 1.4.1.
Ziggy dual core kernel @
1.7
Sent from my PG86100 using XDA App
This is with CleanROM 2.7 (included kernel, no tweaks) not even breaking a sweat. Governor was set to conservative and I'm running "only" 1.62 GHZ OC. I don't like to run it at max. This ROM is a great combo of speed and reliability.
Mike
justj said:
1.78ghz stock de-sensed
Click to expand...
Click to collapse
what launcher are you using ??? do you have many widgets ? many apps installed ? have your wifi enabled ? does this matter do you think ?
I'm one who wants to always get the most out of his phone, but you guys do realize that with numbers like these, it is almost impossible to find any app that is going to have lag, so why even bother to go faster? At these speeds, you're now limited by things like your (data) connection speed and SD card read/write speed. So if we make these things faster, we're never going to see a difference anyway.
Just a does of reality. I don't think many of us use our phones to do number crunching, calculating pi to a billion digits, or use them to process SETI data to search for alien transmissions. Playing Angry Birds at 1.8 Ghz with both dual cores forced online isn't going to look any different than it does stock... except maybe your left hand gets warmer while holding the phone.
Mike
gav-collins1983 said:
what launcher are you using ??? do you have many widgets ? many apps installed ? have your wifi enabled ? does this matter do you think ?
Click to expand...
Click to collapse
I have launcher Pro with many widgets and apps installed. wifi, date everything on. As I found turnning airplane mode on doesn't really matters.
mikeyxda said:
Just a does of reality. I don't think many of us use our phones to do number crunching, calculating pi to a billion digits, or use them to process SETI data to search for alien transmissions. Playing Angry Birds at 1.8 Ghz with both dual cores forced online isn't going to look any different than it does stock... except maybe your left hand gets warmer while holding the phone.
Mike
Click to expand...
Click to collapse
I don't think anyone will run their cpu at max all the time. Not with stock battery anyway. My daily setup is 1.02GHz single core UV @ 950mV. I play games like 9mm, ShadowGun etc and never had any problem with that speed.

[Q] SetCpu manual Undervolt vaues

Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
weaz_da_smel said:
Hey guys,
Ok the people who know about SetCpu and undevolting with it...
If I key in UV-values that go further than the slide-bar can take, i.e over -500mV,
does the undervolting actually go under the -500mV??
At the moment I've tried:
216mhz at -725mV [No hang when I run max and min cpu frequency at both 216Mhz]
456mhz at -650mV [No hang when I run max and min cpu frequency at both 456Mhz]
EDIT: I also ran the stress tests at said frequency settings and still no cpu hang or reboot.
I want to see if this goes further, but Im not sure if SetCpu is actually making the UV values go over -500mV.....
Cheers guys
current config: latest Blue Chronic rom, faux 2.1 kernel, carrier unlocked at&t atrix.
Click to expand...
Click to collapse
any jump more than 100mV between steps and it wont do the changes
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Atrix_Owner said:
I have been thinking about undervolting as well and I was wondering if really does make that big of a difference like some people say? Do you really notice that it improves your batter life?
Click to expand...
Click to collapse
The benefits of undervolting are lower power which leads to lower heat and longer battery life. I'm not sure if these power savings translate if the cpu is idle or in some type of sleep mode and the other problem is that all the other components are still using the same amount of power so the real savings might not be much if your phone is mostly idle.
But, my phone idles at 216Mhz and I have almost halved that voltage at that level so the best case scenario is that the cpu is using 1/4 the power it would normally.
I haven't done any testing but I do know there is some savings and we're all here cause we like to tweak things so you might as well undervolt cause it's pretty simple.
I would start with these levels:
1000 - 950mV
912 - 900
750 - 800
608 - 700
456 - 600
312 - 500
216 - 400
The only rule I know for undervolting is the 100mV between steps rule but I know there is some other rule at play as described in my previous post, but I don't know what it is. So really, I'm not sure if the voltages at the lower frequencies are actually being applied.
Hey thanks for the info. I don't know if I'm doing this correctly. After I undervolted, I clicked "set on boot" and rebooted my phone but I'm not sure if I did it right. For example, when you look at the "1000mhz", on the right it says "Max 1000mV" which is the default setting but shouldn't it be "925mV" because I subtracted -75mv? Look at this pic and tell me if it's like it should be.
{
"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"
}
Ya, that's right. That max voltage I think is a misnomer I think it should say default voltage really and that's just there for reference. So, when your cpu is operating at 1000Mhz it is operating at 925mV, with your current setting, it doesn't vary.
If you want to try to push for lower voltages you just want to uncheck set on boot so you avoid getting into a reboot cycle. YMMV on what kind of undervolt will be stable. I gave you my numbers because I think my phone is not as stable as others since it can't handle the 1.45Ghz overclocking kernel.
My phone isn't overclocked btw and I'm using Faux123's enhanced stock kernel 1.0ghz. I will try to push the volts even lower and see how that goes. One thing that I can say for sure is that when I play GTAIII, my phone doesn't overheat as much as it used to so this defiantly fixed the overheating issue that I was having with almost any game.
my setcpu doesnt have voltages tab.. y?
borjok536 said:
my setcpu doesnt have voltages tab.. y?
Click to expand...
Click to collapse
B/c you're not using a custom kernel.
Sent from my CM7 Atrix 4G
mebster123 said:
The 100mV steps are the limiting factor if you use the higher frequencies which require relatively high voltage not to cause problems. What the OP might be curious about, and what I'm curious about is if I limit my phone to say 600MHz then I can set the voltage of all higher frequencies as low as I want because the phone will never use those frequencies, then I can try to find the true lower bound of the lower frequencies. The problem is I can set the lowest frequency to 0, keeping the 100mv steps, and the phone still runs fine (by limiting my phone to 216MHz), so there is some other rule in effect besides the 100mv between steps rule.
This is something that is limited by the chip itself but I guess that these rules would have to be written in the kernel, so I'm going to post over in the faux kernel thread.
Edit:
I don't have enough posts to post in the developer forum. Can someone copy the jist of my question over in the faux thread or somewhere else appropriate and with marginally high traffic? Thanks.
Click to expand...
Click to collapse
What I gathered from my own experience, experimenting and looking at code is the following:
The 100 mv limit between steps seems to be more of a nvidia guideline for best chip performance. It is not an actual limit in the software, no matter the values you input, they will be applied.
What is indeed limited (and so in the code) is the lowest possible undervolt. In faux's it is 750 mv and clemsyn's (was, not sure if still is) 650 mv.
If you push any voltage past that limit, it won't be applied. Try it for yourself.

Vibrant keeps shutting off and freezing!

i have a jelly bean rom on my phone and for a while it worked fine with a custom kernel. then it started to freeze as soon as i hit the lock button. so it wouldnt turn back on. it always does it now. but when i take off the kernel it works fine with the stock jb rom kernel. ive tried slim bean, cm10, helly bean and they all freeze with a custom kernel. they use the devil or sephamore kernel. both give me the same problem and i dont know what is causing it when the kernels were meant to work on these roms. some help would be much appreciated
Are you overclocking or anything? Undervolting? Live OC? Maybe your phone can't handle it.
theexel said:
Are you overclocking or anything? Undervolting? Live OC? Maybe your phone can't handle it.
Click to expand...
Click to collapse
its overclocked to 1.3 ghz with this kernel but it should be able to handle it. i used to run it at 1.6 on gingerbread and ics roms. the devil kernel ran fine with with live overclock on ics. im using sephamore on jb with live overclock of 105% and its undervolted. i dont know if this is the problem though as i used to run at higher clock speeds with undervolting and live overclock.
Try flashing the kernel, but don't overclock or undervolt.
See if it reboots/hangs.
Then try just overclocking.
Then try just undervolting.
Etc.
Just so we can narrow down the problem.
Also, is deep idle enabled?
Edit: May I ask why you overclock so high?
If it's for performance, you're much better Live OC'ing like 10% and leaving the min at 200 + the Live OC.
Heck, maybe even 20%, it'll be super snappy.
Unless you play games, then I understand.
My settings:
{
"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"
}
theexel said:
Try flashing the kernel, but don't overclock or undervolt.
See if it reboots/hangs.
Then try just overclocking.
Then try just undervolting.
Etc.
Just so we can narrow down the problem.
Also, is deep idle enabled?
Edit: May I ask why you overclock so high?
If it's for performance, you're much better Live OC'ing like 10% and leaving the min at 200 + the Live OC.
Click to expand...
Click to collapse
Yeah ill try that out and i disabled deep idle i think it still does it. if i awaken my phone periodically it wont reboot.
and i used to just because i could i usually kept the max at around 1.5 ghz. i would just use 1.6 maybe for some heavier games. but now the processor is only at 1.3 ghz and 1.46 with the devil kernel as i dont play much games anymore.
i keep my min at 200.
and when i flash the kernel do you want me to leave it alone not change the governor or scheduler? or anything of that sort?
actually i have live oc to 130% i was thinking of the devil kernel i tried earlier sorry.
How are you disabling Deep Idle?
With the Kernel app or NSTools, or?
Do it with the kernel app.
Let me try some higher settings real quick just to get an idea.
Yeah, leave it how it comes.
Ondemand is fine if you want battery life and for the ROM to be snappy.
Noop is fine, too.
Smartmassv2 seems laggy on this kernel.
theexel said:
How are you disabling Deep Idle?
With the Kernel app or NSTools, or?
Do it with the kernel app.
Let me try some higher settings real quick just to get an idea.
Yeah, leave it how it comes.
Ondemand is fine if you want battery life and for the ROM to be snappy.
Noop is fine, too.
Smartmassv2 seems laggy on this kernel.
Click to expand...
Click to collapse
i used nstools and also i have smooth profiles on and the overclock is running at 1.3 ghz yours is around 1 ish? did you set it in the kernel app to set the clock speed? my smartassV2 seema to be faster with me. I am running sio scheduler with SmartassV2.
i am going to start playing with the settings now.
may i ask what rom and kernel you had working?

Categories

Resources