Related
Switched to CM9 last night and I want to Undervolt it to get the max out of the battery.
Plz share your Undervolting experience, which rom, kernel, settings, ect'...
I imagine it will help more people and not just me
Sent from my GT-N7000 using XDA
For now UV is only possible with GB kernels, the ones built from Sammy's source code, and I don't think there's anyone left with gb so this question is pointless for now until we'll get the ICS source code from Sammy
Sent from my GT-N7000 using xda premium
moshikko said:
For now UV is only possible with GB kernels, the ones built from Sammy's source code, and I don't think there's anyone left with gb so this question is pointless for now until we'll get the ICS source code from Sammy
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
It works on Stunner and CM9 for me.
Sent from my GT-N7000 using XDA
Screw that last guy who thinks he knows jacks ass, use your favourite app to change cpu settings or terminal console to change both cpu gpu, assuming ur using the cm9 experimental builds with the kernel included.
And my shared settings to u are:
CPU
1400 - 1175
1200 - 1125
1000 - 1075
800 - 1025
500 - 950
200 - 925
GPU
400 - 1050000
267 - 875000
200 - 825000
And if u know under and overvolting, its pain in the ass to find the right settings which works for u, overheating issues for me are greatly reduced by undervolting.
beckend said:
Screw that last guy who thinks he knows jacks ass, use your favourite app to change cpu settings or terminal console to change both cpu gpu, assuming ur using the cm9 experimental builds with the kernel included.
And my shared settings to u are:
CPU
1400 - 1175
1200 - 1125
1000 - 1075
800 - 1025
500 - 950
200 - 925
GPU
400 - 1050000
267 - 875000
200 - 825000
And if u know under and overvolting, its pain in the ass to find the right settings which works for u, overheating issues for me are greatly reduced by undervolting.
Click to expand...
Click to collapse
Watch you language little a*hole
Cm9 and stunner with all respect have some bugs to use as daily rom ( speaker, otg, ums) and a proper kernel can't be delivered yet until source code is out from Sammy, I bought my note for a reason and it is certainly not to have an oversized GNexus!
Next time think a bit before you comment,
I just gave my opinion for UV with experimental kernel since many hardbricks due to playing with kernels is going on right now, and I know that UV can't cause a brick but the kernel might!
So I prefer a GNote kernel, made from a gnote source code even if it means waiting for it a bit longer, than a kernel made from sgs2 source code .
Sent from my GT-N7000 using xda premium
Giving people false information based on what u think without proof or facts, whatever man send me pms if u rly need to bring up nonsense, spare the thread your whine.
moshikko said:
Watch you language little a*hole
Cm9 and stunner with all respect have some bugs to use as daily rom ( speaker, otg, ums) and a proper kernel can't be delivered yet until source code is out from Sammy, I bought my note for a reason and it is certainly not to have an oversized GNexus!
Next time think a bit before you comment,
I just gave my opinion for UV with experimental kernel since many hardbricks due to playing with kernels is going on right now, and I know that UV can't cause a brick but the kernel might!
So I prefer a GNote kernel, made from a gnote source code even if it means waiting for it a bit longer, than a kernel made from sgs2 source code .
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
You said:
moshikko said:
For now UV is only possible with GB kernels, the ones built from Sammy's source code, and I don't think there's anyone left with gb so this question is pointless for now until we'll get the ICS source code from Sammy
Click to expand...
Click to collapse
This is not true.
Also, be careful with the official ICS ROM. It has the eMMC bug which can "superbrick" your Note, which requires a motherboard swap to fix. I'll be using CM9, which is safe.
searched and found this thread. http://forum.xda-developers.com/showthread.php?t=1433952&highlight=undervolt
How do you Undervolt gpu?
Sent from my GT-N7000 using XDA
pboesboes said:
Also, be careful with the official ICS ROM. It has the eMMC bug which can "superbrick" your Note, which requires a motherboard swap to fix. I'll be using CM9, which is safe.
Click to expand...
Click to collapse
Everything on earth contains the "superbrick" bug... that is, if you were previously on CM9....
NOTE, USE UR OWN VALUES. Applies to cm9 experimental builds with supplied kernel.
If u know how to use terminal console or adb, u can do:
For voltage:
echo "825000 875000 1050000" > /sys/devices/virtual/misc/gpu_voltage_control/gpu_control
For frequencies:
echo "200 266 400" > /sys/devices/virtual/misc/gpu_clock_control/gpu_control
pboesboes said:
You said:
This is not true.
Also, be careful with the official ICS ROM. It has the eMMC bug which can "superbrick" your Note, which requires a motherboard swap to fix. I'll be using CM9, which is safe.
Click to expand...
Click to collapse
Guess I didn't explain myself the way I wanted, no harm done
Most of the time I use speaker when driving which is missing in CM9
So I'm forced to use official rom
That's why I said UV is not possible yet
My bad for including cm9 in my first post
Sent from my GT-N7000 using xda pre mium
clandestino123 said:
Everything on earth contains the "superbrick" bug... that is, if you were previously on CM9....
Click to expand...
Click to collapse
I haven't heard of anyone bricking because of xplodwild's CM9. If you mean chasmodo, that was most likely because he wiped on the LPY kernel.
moshikko said:
Guess I didn't explain myself the way I wanted, no harm done
Most of the time I use speaker when driving which is missing in CM9
So I'm forced to use official rom
That's why I said UV is not possible yet
My bad for including cm9 in my first post
Sent from my GT-N7000 using xda pre mium
Click to expand...
Click to collapse
Yeah, the custom ROMs out there are still a little buggy and probably not the best for daily driving!
pboesboes said:
I haven't heard of anyone bricking because of xplodwild's CM9. If you mean chasmodo, that was most likely because he wiped on the LPY kernel.
Click to expand...
Click to collapse
show me one person who has bricked their phone, who has not first used CM9 or some derivative... I believe that all of these hard bricks are being triggered by CM9 in some way.
clandestino123 said:
show me one person who has bricked their phone, who has not first used CM9 or some derivative... I believe that all of these hard bricks are being triggered by CM9 in some way.
Click to expand...
Click to collapse
You're the one making the claim here, why don't you get some evidence to back it up?
It's quite an extraordinary claim, and I'd be more inclined to believe Entropy512's take on the matter (eMMC bug in leaked kernels) because he's a kernel dev.
Just to be clear, you're talking about this CM9: http://forum.xda-developers.com/showthread.php?t=1627855?
I am currently on ReVolt JB v3.1
Kernel : CM10.1 kernel
I also want to UV my phone for a better battery life.
Can someone help?!
rohhanpandya said:
I am currently on ReVolt JB v3.1
Kernel : CM10.1 kernel
I also want to UV my phone for a better battery life.
Can someone help?!
Click to expand...
Click to collapse
I am on [TEST FIRMWARE][ODIN REPACK] JB 4.1.2 GT-N7000XXLSC clear stock rooted with Philz kernel, and have UV my phone using Tegrak Overclock Ultimate from Google Play (paid app).
My battery life has been greatly improved with UV.
You can find more information on UV in this thread: Undervolting the GT-N7000 for better Battery life http://forum.xda-developers.com/showthread.php?t=2091056
Hi, how can i overclock my tf300t (Clean rom 2.5 oveclock 1.6ghz) to 2.0 Ghz? i read something in the forum but there isn't any kind of guide, i want know if the tablet is stable with this frequency, and if i risk something.
thanks
anthraxx90 said:
Hi, how can i overclock my tf300t (Clean rom 2.5 oveclock 1.6ghz) to 2.0 Ghz? i read something in the forum but there isn't any kind of guide, i want know if the tablet is stable with this frequency, and if i risk something.
thanks
Click to expand...
Click to collapse
Why would you need to overclock so high? Do you want it to explode! xD
Seriously though, would probably advise against it. It's like a whole 700/800 MHz higher than it's meant to run at stock. I'd say it would be very unstable, and probably wouldn't get very far battery-life-wise. 1.6GHz really not enough :/
mozyman said:
Why would you need to overclock so high? Do you want it to explode! xD
Seriously though, would probably advise against it. It's like a whole 700/800 MHz higher than it's meant to run at stock. I'd say it would be very unstable, and probably wouldn't get very far battery-life-wise. 1.6GHz really not enough :/
Click to expand...
Click to collapse
1.6ghz is ok? or i'll risk something?
I did that speed already. But it is very very unstable. random reboots within 10 minutes of use. also the battery life is very low. and the whole tablet is to hot.
i only was using it to see how fast it could go. that was the max. i am at Cutom Rom - 07/10/2012 - [email protected] Edition V02 - The Ultra Fast Rom - based on last Asus Firmware 10.4.2.13 at this moment.
this is very stable. balanced speed is 1.3 and thats oke. Normal performance speed is 1.6 but i only use that when playing games. You dont need those high speeds for daily use.
If you have the financial means to buy a new tablet - you can try all the time to work on this frequency.
With 1,6ghz i'll risk to break the tablet?
i used 2.0ghz about a week daily use. But now im lowered it to 1.8ghz and it is stable my everyday use. and battery lenght is very good maybe better than stock (i made undervoltage, so cpu uses -50mv less power in any speed than normaly/stock )1.8ghz use 1150mv and lowest speed use 775 mv)
Niksunen said:
i used 2.0ghz about a week daily use. But now im lowered it to 1.8ghz and it is stable my everyday use. and battery lenght is very good maybe better than stock (i made undervoltage, so cpu uses -50mv less power in any speed than normaly/stock )1.8ghz use 1150mv and lowest speed use 775 mv)
Click to expand...
Click to collapse
on tf300t? what kernel?
anthraxx90 said:
on tf300t? what kernel?
Click to expand...
Click to collapse
yep on tf300, and i compiled kernel myself, adding these features on it. So it is no downloadable this moment.
ok, and it's normal random reboot on 1,6 ghz? the problem is voltage or kernel?
anthraxx90 said:
ok, and it's normal random reboot on 1,6 ghz? the problem is voltage or kernel?
Click to expand...
Click to collapse
well, if you raise voltage up it may help, but i thing the problem is, that every tablet cpu is "diffrent" than other. This i mean, that these cpu is specsed in other speed than 1.6, 1,8 or 2.0ghz, and some invidiuals might work good in these higher speeds, some get randon reboots / freeze, or some of cpu:s dont even boot higher speeds. (i found out that when few people test my kernel, and it not even booted. And someone it will work fine.) This thing can "cross" by made kernel force cpu speed 1.0ghz at bootup (and i made this my kernel)
Also these tf300 tablet is manufactured atleast couple of diffrent cpu type /cpu id, so kernel have to had support all of these overclocking
It just like computers, some cpu can overclock higher than others, and if you go too high you need extra cooling, and in tablets, it is not possible, like normal pc's
*Most of this is my conclusion only, it may not be 100% accurate truth, but this how i see this thing. And if someone knows better etc, you can correct me *
Niksunen said:
well, if you raise voltage up it may help, but i thing the problem is, that every tablet cpu is "diffrent" than other. This i mean, that these cpu is specsed in other speed than 1.6, 1,8 or 2.0ghz, and some invidiuals might work good in these higher speeds, some get randon reboots / freeze, or some of cpu:s dont even boot higher speeds. (i found out that when few people test my kernel, and it not even booted. And someone it will work fine.) This thing can "cross" by made kernel force cpu speed 1.0ghz at bootup (and i made this my kernel)
Also these tf300 tablet is manufactured atleast couple of diffrent cpu type /cpu id, so kernel have to had support all of these overclocking
It just like computers, some cpu can overclock higher than others, and if you go too high you need extra cooling, and in tablets, it is not possible, like normal pc's
*Most of this is my conclusion only, it may not be 100% accurate truth, but this how i see this thing. And if someone knows better etc, you can correct me *
Click to expand...
Click to collapse
ok when do you release ur kernel's download? i wanna try
anthraxx90 said:
ok when do you release ur kernel's download? i wanna try
Click to expand...
Click to collapse
Well im not home right now, so i dont have any 2.0ghz or 1,8ghz kernel with me, i have only 1.7ghz oc kernel, so you can test it if you want. But just like always, im not taking any responsibility, so test /use it with own risk. https://www.dropbox.com/s/vvmti4knwkeflde/Nixu_Kernel_OC_1700_v0.1_alpha.zip
i'm afraid now loool, what would happen exactly?
after flashing the kernel is locked to the screen asus, does not want to start
That won't happen I flashed it
Sent from my SGH-T989 using xda app-developers app
Finally after someone pm'd me I looked back into GPU Overclocking.
New thread created issues with old thread OP permissions (people seem to be asking the same questions over and over again all information will be kept in OP & DO READ THE THREAD, repetitive questions will now be ignored)
Benefits:
Smoother UI
Handle 2d & 3d core GPU intensive applications & games
Currently only 2D core has been overclocked working on 3D core OC
2D-core original value - 192mhz OC to 245mhz DONE achieved 25% performance boost grp_2d_clk outputs 245760000hz
3D-core original value - 245mhz OC to 300+mhz WIP hoping to achieve 40-50% performance boost
2D-core OC only Download: Coming soon...
Download Links for other devices coming soon...
Works for all HTC Sense/Cm9/Cm10 kernels (Just ask a kernel developer for your device to implement the source code)
Note: Don't have internet on PC so providing 3 main files that need replaced for 2D-core OC to work
Download link to source code: http://d-h.st/wbH
3D-CORE OC TESTS Download: Coming soon...
Do check under sys/kernel/debug/htc_clock/clks/ look for file with all clocks & look for GRP_clks (Graphics clock)
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497
Thanks for your efforts.
I'm trying to follow the link to your Desire thread and it seems it's broken.
Nevermind, found it: LINK
I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2
disconnecktie said:
I think a kernel dev from the droid incredible 2 has a 3d gpu overclock in a kernel but I didn't use it in mine because I worry about the heat output being overclocked combined with that.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2372291
you must be referring to this...
Someone already showed me the commits
no one has managed gpu overclocking at all on any msm7x30/msm8x55 platform/soc devices
I saw it someone's git when I was building my kernel. I couldn't find useful posts about kernel stuff so I just looked for git accounts that were from similar devices.
Sent from my ADR6400L using Tapatalk 2
Probably Kangaroo Kernel based off of Beast Mode.
Oh ya that's the one. Been a while since i looked.
Sent from my ADR6400L using Tapatalk 2
Shaky156 said:
OK so basically today I've been thinking and I've come to the conclusion that I will release the 2D-core OC patch As Soon As Possible, 3D-core Core OC is NOT Impossible but for now I'll give it a break, I will attempt 3D-core OC If/When I can get a hold of a msm7x30/msm8x55 device, as it will make it much easier for both me & users.
So for now you can enjoy the 50mhz increase/bump up, perf boost 25% in 2D-core (will increase performance in both 2D/3D intensive appications as 2D-core is used for 3D AFAIK and increase User Interface performance (Note: This will not take a hit on battery life)), I will also release a couple of fixes on patchas kernel that shouldnt be there/set etc.
(Theres a device available in my area for roughly £90, if anyone wants to contribute towards getting that device or can donate a device , more than welcome and shoot me a PM so I can list you here.)
(This isnt a promise of 3D-Overclock if you donate, if you donate please do so expecting nothing I will only attempt 3D-overclock)
Working device list - all kernel 3.0+ msm7x30/msm8x55 soc devices.
Main thread is in Desire HD Android Development section: http://forum.xda-developers.com/show....php?t=2368497
Click to expand...
Click to collapse
I have an Inc2 id be willing to test on if you'd like...
Sent from my Maserati using XDA Premium
Everyone has been modifying the kernel graphics software layer platform data with values that dont make sense and are impossible more above with values that dont exist within thw graphics table anywayx
3d oc is abit more difficult
Devs + testers join IRC will make life easier
Irc freenode #s1gpuoc
I wouldn't recommend replacing those files in any current kernel directly. Since there is no github to see what the actual changes are isolated from the file, it's hard to say if all the changes made are compatible. Some of them were unnecessary, and simply added credits to a line that was unchanged (most likely because it has been updated since the original writing of the files).
https://github.com/StarKissed/stark...mmit/dc381024f122a114b770076e2992cd5097f5c47c <- The specific changes required
twistedumbrella said:
Does this include a sysfs interface to throttle the overclock?
https://github.com/StarKissed/stark...mmit/618b9e076f7b2c0a8f9f0c5733f61d4ef27261c0
Click to expand...
Click to collapse
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30
Shaky156 said:
There isnt any need for a sys fs at the moment due to the way qualcomm have made their msm7x30
Click to expand...
Click to collapse
Any time values that aren't stock are being forced, it's good to have the option to turn it off but in this case it's only forcing stock values to persist so it doesn't really matter.
Sent from my Galaxy Nexus using Tapatalk 2
Okay after looking @ GPU Overclock for 2 weeks, This is the news on GPU OC for MSM8x55/MSM7x30 socs.
My findings...
2D-core OC from 192mhz to 245mhz successful.
3D-core OC will not happen without me obtaining the datasheet (which is proprietary)
The clocks are protected, via Ownership/Permissions, and maybe an RCU/MPU
No Overclocking the CPU does NOT Overclock the GPU, thats the worst thing I've heard in my life lol.
The lowest the GPU can hit is 192mhz or lpxo freq
Bus is not overclockable, it always is 192mhz
EBI_2D_clk will and has always been 0mhz
Modifying kgsl platform data and/or the graphics table with random values or even calculated values from correct pll freqs will NOT OC the gpu
it's ashame the GPU clocks are protected.
IF anyone is looking to continuing this project and is on the right track you're more than welcome to get in contact with me, especially if you have the msm7x30 datasheet.
The QSD8x50 soc is more open than this soc, so I'm doing a few tests on the HD2
Update
All the changes I made were merged into CoCore-refresh kernel (3.0.31) and 3.0.101 by TeamCanjica, so they will hit 'mainstream' in some time when they release another build.
This thread is over
/Update
Hi,
I've been working on this kernel for some time with improving undervolting in mind. It's based on CoCore Refresh r10 by CoCafe and of course the credit goes to him where it's due.
Main changes:
- rewritten liveOPP internals.
It improved stability a lot - it now allows to use 300/500/700/900 MHz frequencies with no problem and it allows to undervolt low frequencies even more. Freqs >1GHz are now stable at varm=0x32 (at least on my phone), which also saves a lot of power.
Freqs <=400 MHz now use 0x12 (0.925V) voltage by default - It's the original voltage for 400MHz and you can go even lower when undervolting
- rewritten Mali booster algorithm.
It's far from perfect yet, but it eliminated instability due to the fact, that CoCafe's mali booster and "original" booster (switching between APE 50/100 OPP) were working independently and could cause a crash when the original algorithm switched to APE_50_OPP while mali boost was active. APE_50_OPP voltage is 1V by default (0x18), so when clock is boosted to i.e. 700MHz and it switched to 50 OPP, the result was 350MHz @ 1V, which mihgt be too low.
- allow to set APE and DDR OPP with liveOPP
echo apeopp=25/50/100 > arm_stepXX and echo ddropp=...
before the kernel would set ape/ddr opp to 100 for freqs above 400MHz
- allow changing ape_50_opp voltage
echo 0xXX > /sys/kernel/mali/mali_gpu_vape_50_opp
- make wlan/mmc boost tunables available through sysfs in /sys/kernel/performance/*
- Memory split changed to 2G/2G and switch highmem off - it's not needed with this split
- removed some unnecessary drivers and moved others to modules to reduce kernel size
- changed kernel compression to LZO
- 631MB available memory
- 7800ms kernel boot time
Download & install:
Mediafire
That's partition image - flash it with dd:
Code:
dd if=kernel.mk-r1-release.img of=/dev/block/mmcblk0p15
It's also good to create a symlink from /system/lib/modules to /lib/modules - it'll allow modules to autoload, enable modprobe to work and also you can use KoControl app to manage module loading.
Source:
GitHub
TODO:
- create a package for flashing with recovery and place modules (7MB) in /system/lib/modules instead of a ramdisk
- touchbooster has a bug that causes it to limit max freq to 1000MHz on boost.
- figure out how to enable setting of minimal cpu freq - now touchboost always resets it to 100MHz
- add interactive gov from Zwliew kernel
- create more power optimized, auto tuning 'foreground' governor (long story)
My voltage settings
(default kernel voltages are more conservative - set those from init scripts and test them for stability!):
100 - 0x0f
200 - 0x10
300 - 0x11
400 - 0x12
500 - 0x14
600 - 0x18
700 - 0x1d
800 - 0x24
900 - 0x28
1000 - 0x2f
1050..1250 - 0x32
Mali gpu voltage
Default voltage from CoCafe is way too high - idx0 vape could be just 1V since that's the voltage, when mali is running at 1/2 speed (200MHz by default).
My settings (for safety they are 3 steps higher than the lowest working voltage for given freq).
#0 - 0x17
#5 - 0x1c
#9 - 0x23
I don't overclock the gpu - my low index is set to 0 (200MHz), and hi (boosted) to 5(400MHz), which is the original mali freq. That gives mi 100MHz when working at half speed. I don't use any fancy UI effects, so it's enough - when not plaing a game, mali is only working at 100/200MHz and only boosts when loaded. Params:
boost_low idx=0
boost_low threshold=30
boost_delay 2000
boost_high idx=5
boost_high threshold=220
Default kernel settings are left unchanged - set those manually from init scripts.
I place the thread here because I'm not allowed to post in developer forums (<10 messages limit).
MK
Wow. Thanks for your work, mate!
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after using it.
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Good to see another kernel developer for our phone! I'm on stock rom now, I will try it out
Sami Kabir;5571pro. [B said:
Wow. Thanks for your work, mate! [/B]
Most people are using CM or CM/AOSP based ROMs nowadays, but there are only a few people (like me) who still use Jellybean. So, I'll try your kernel very soon and I'll post a review after( using it.
Click to expand...
Click to collapse
The code is on github and there's no problem with merging it with some cm kernel. When I'll try my with some 4.4 again (so far each one had something broken and didn't suit me), I'll probably do it
You joined XDA on 2010 and yet, this is your first post. That just doesn't feel right.. Anyways, keep up the good work, mate. :good:
Click to expand...
Click to collapse
To keep it short let just say that I'm not a sociable type of guy... but when I have something of value, I try to share...
One more thing (most probably know it, but for those who don't) - 99% of "user experience" depends on the settings of governor, mali and touch booster - if you screw this up, no kernel will work smoothly. I had this problem with my first vanilla jb - it sucked as hell(ondemand), but when I set sampling_down_factor to 3-4 suddenly it was very smooth. Default gov params aren't always the best. Thats one of the reasons I'll try to write a governor that tunes itself and adjusts itself to the app currently in foreground - but that's just an idea and it'll take me some time to refresh all the math needed for it...
Anyway - enjoy the kernel.
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Reinkaos said:
Hmm I really wanna test this kernel, but I'm currently on Vanir
I definitely gonna follow your thread, it's good to know Janice is still alive and kicking
Click to expand...
Click to collapse
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
mkaluza said:
You can always ask rom's devs to merge my changes - it's just a few commits.
And how is that rom working for you? At the time I was checking up 4.4 roms each one of them sucked in a different way. Carbon was the closest (in fact it was the only one acceptable) to being useful (feature- and ui-wise), but it had some process spinning in the background and It was draining my batt (it was unkillable because it was a part of lock screen I think - the bug was known, but no fix available at that time).
If it's similar to carbon I might give it a try...
Click to expand...
Click to collapse
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
aioreu the
Reinkaos said:
Well I use to be a Carbon die-hard fan before, but since the dev have got himself another device, so I just had to change rom.
Click to expand...
Click to collapse
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
And then I try Vanir. Surprisingly it's pretty stable, and we have official support by the Vanir team too.
Feature-wise its just as good as Carbon, but I kinda miss the pie, since Vanir doesn't have it.
And I think Vanir have a bit more features than Carbon do.
Click to expand...
Click to collapse
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Anyway can you go lower than those cpu voltage on your OP? Or is it really not stable?
Mine's 1000 is at 0x2c, 800 at 0x20, and that's the lowest I can go.
Click to expand...
Click to collapse
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
And thanks for the gpu voltage :good: , I actually use that value now :laugh:
Click to expand...
Click to collapse
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
mkaluza said:
It's a pity... but I understand that's only the S Advance branch of Carbon thats dead - the rom itself is being developed further?
Click to expand...
Click to collapse
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
I didn't like the pie ;P But if you say it's ok, I'll give it a try when I'm in the mood to reinstall everything on the phone...
Click to expand...
Click to collapse
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Actually I didn't recheck those two and focused on lower freqs - these were the limits with older LiveOPP, but now I can go to 0x22 and 0x2c.
In fact, 0x24 and 0x2f are already undervolted values - original are 0x28 and 0x32. But every bit counts, especially on higher freqs.
Thanks for the tip
But what's more interesting - 900MHz works at 0x23 (didn't test that before - just took a voltage halfway between 800 and 1000)... there's something wrong with this ARM_100_OPP, but I don't know what yet... Will test the rest again later and post my results.
Click to expand...
Click to collapse
No problem man, thought that information would be useful to you.
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Your welcome
When I have time, I'll try to write how to quickly check undervolting limits for both cpu and gpu.
Mk
Click to expand...
Click to collapse
Yes, please do. I would really appreciate that :fingers-crossed:
Reinkaos said:
Yes, only for our device. It's not really dead yet.
The dev has been kind enough compiling new one once in a while.
Click to expand...
Click to collapse
He also left a repo with build scripts and manual, so I'll try to build the rom.
Yeah, I could understand that. Too much of a hassle. Got to reinstall everything back again.
But you know, I always do clean flash, even with nightlies. Imagine backing up, factory reset and restoring everything in every 3-4 days.
But now I get really used to it
Click to expand...
Click to collapse
That's hardcore ;P I have patience to do it 1-2 times a year
Yeah, it would be really nice to go lower, especially on 1000 and 800.
I'm gonna test the rest, and later I would let you know the lowest working voltage that I can go.
Click to expand...
Click to collapse
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
And honestly, I have no idea about kernel stuffs :silly: The least that I can do is to play around with it
Click to expand...
Click to collapse
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Yes, please do. I would really appreciate that :fingers-crossed:
Click to expand...
Click to collapse
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
mkaluza said:
He also left a repo with build scripts and manual, so I'll try to build the rom.
Click to expand...
Click to collapse
Well that's a good news :good:
That's hardcore ;P I have patience to do it 1-2 times a year
Click to expand...
Click to collapse
LOL yeah
mine crashed at 1000MHz/0x2c - I'm on 0x2d now and it seems ok
Click to expand...
Click to collapse
I'm not sure if mine is really stable, gonna test it with your guide on github
You could always learn It's fun, all the info is there to read for free... all it takes is will and time
Click to expand...
Click to collapse
Yeah, I am learning right now
I still cant post links, so you need to go to my github (mkaluza), open the i9070_kernel_CoCore-E repo and go to wiki on the right - there is a page "Undervolting janice". Hope this helps.
Mk
Click to expand...
Click to collapse
So there are scripts that will provide me with some infos when doing UV-ing
And I'm not familiar with registers though, I only do it via liveopp, but still I'll try this
Thanks for the guide
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
P.S. hey you could just spam in OT threads to get 10 posts
Reinkaos said:
I'm not sure if mine is really stable, gonna test it with your guide on github
Click to expand...
Click to collapse
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Anyway I got a question about gpu, lets say my mali low_boost is 400 and high_boost is 480,
does it use the two freq only or it use the other freq in between 400 and 480 too?
Click to expand...
Click to collapse
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
.P.S. hey you could just spam in OT threads to get 10 posts
Click to expand...
Click to collapse
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
mkaluza said:
I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
You like adrenaline, heh
PS: Sorry for OT
mkaluza said:
If you don't get random reboots/crashes than it is - when following my guide, the resulting voltage should be stable, but it isn't always so... I'ts just a starting point that can save you some initial crashes or the other way around - if it doesn't pass freq_jump test, then it isn't stable for sure
Click to expand...
Click to collapse
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Only those two - three actually - also 200MHz (that is low_boost/2), but with ape_50_opp voltage, not the one from dvfs_config. There's not much point in doing any smarter gov because gpu intensive apps usually load it at 100% no matter how much power it has - they just have more fps then.
Click to expand...
Click to collapse
Thanks for the infos :good:
Yeah, maybe, but if those are the rules, then I try to respect them - because I respect the community. (not because I'm some kind of by-the-book guy ;P I ride motorcycle and have already broken so many rules, that they would put me behind bars for life if anybody kept the count ;P).
Click to expand...
Click to collapse
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Force said:
You like adrenaline, heh
PS: Sorry for OT
Click to expand...
Click to collapse
I'ts more about freedom and versatility, but yeah sometimes I like to push it too
Reinkaos said:
Hey, just letting you know, about opptop script, we don't have prcmu-qos folder in /debug. I thought maybe it have a different name, but I couldn't find ape_requirements and ddr_requirements. The others are working fine
Click to expand...
Click to collapse
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
LOL, I'm curious though, what bike do yo own? Must be a real badass one
Click to expand...
Click to collapse
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
mkaluza said:
I forgot... this feature was written by me, so it's available only on my kernel for the moment. But it's not really that important - it was more for debugging purposes for me, now I left it as informative.
I'm trying to build Carbon rom for out phone since last night... when/if I'm done, I'll patch the kernel with my stuff and push it somewhere. What is your kernel version? I think that both carbon and vanir use the same, or at least similar one.
Click to expand...
Click to collapse
Well ok then. Vanir got a 3.0.101 kernel. It's the same I think? I'll flash and test it when you're done, definitely.
Not really I't an old BMW F650 - only 48 ponies (of which some might have already died of old age ;P). But in reality you can do most of the fun stuff with as little as 125cc Anything bigger is usefull for longer trips/highways/trips with passenger/etc... I mostly ride small country roads and light offroad, so I rarely go over 100km/h, so no badass machine is needed something like 350cc would be best I think. Actually - it's not the bike you ride, but how you ride it... and on narrow roads with many turns a bigger bike is event sometimes harder to ride...
Click to expand...
Click to collapse
lol the biggest one I ever been on is about 130 cc. It's small, enough that you could squeeze through traffics
I don't know much about bike, but AFAIK those superbike need different kind of handling too.
Let's speak just about this kernel as for this is meant this thread
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
pictorul20 said:
Please anyone tell me how to find the kernel link . I`m a noob at this part :silly: Thanks
Click to expand...
Click to collapse
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Force said:
Go here and see download link at top of page: https://github.com/mkaluza/i9070_kernel_CoCore-E
Download link : http://goo.gl/FvqPlg
Then check OP to see how to install it.
Click to expand...
Click to collapse
Many Thanks.
So I was wondering about the truth behind the risks of frying your cpu through overclocking or the chip itself degrading faster over time, and if there are such risks do they apply to a simple 2.5 ghz overclocking ?
There isn't any risk like that, unless you are using extremely high voltage, or are at terribly hot place.
I have tested all the overclockable kernels, and haven't found a single one which is steady at 2.6 or 2.8 GHz. Only Faux's kernel at 2490 MHz is stable.
Don't be scared, there's no risk.
PS: I personally use Performance governor by the way, so the CPU is always at max frequency, against all advice I keep using that for past three years, never had a problem, and you can understand where I live the temperature reaches extremely high in summer, so...
devilsdouble said:
There isn't any risk like that, unless you are using extremely high voltage, or are at terribly hot place.
I have tested all the overclockable kernels, and haven't found a single one which is steady at 2.6 or 2.8 GHz. Only Faux's kernel at 2490 MHz is stable.
Don't be scared, there's no risk.
PS: I personally use Performance governor by the way, so the CPU is always at max frequency, against all advice I keep using that for past three years, never had a problem, and you can understand where I live the temperature reaches extremely high in summer, so...
Click to expand...
Click to collapse
That's actually comforting I too am using fauxclock and I live in Egypt so the temperature gets pretty high here, but I'm constantly monitoring the cpu's temperature so I will give the 2.5 ghz overclock a try for a while and see how it goes.
MohamedOMostafa said:
That's actually comforting I too am using fauxclock and I live in Egypt so the temperature gets pretty high here, but I'm constantly monitoring the cpu's temperature so I will give the 2.5 ghz overclock a try for a while and see how it goes.
Click to expand...
Click to collapse
Yeah do that. Just to see if the OC is stable run that damn Antutu benchmark. If the device doesn't reboot/stuck then OC is stable
Best of luck.
devilsdouble said:
Yeah do that. Just to see if the OC is stable run that damn Antutu benchmark. If the device doesn't reboot/stuck then OC is stable
Best of luck.
Click to expand...
Click to collapse
That's the first thing I did actually
MohamedOMostafa said:
That's the first thing I did actually
Click to expand...
Click to collapse
Ha ha. Good. That's on Faux right? I got almost same score (44.7k) when I was checking.
Now if you want more then flash one of those 2.6 or 2.8 GHz kernels, and do the test, and message me if Antutu finishes the benchmark even once
devilsdouble said:
Ha ha. Good. That's on Faux right? I got almost same score (44.7k) when I was checking.
Now if you want more then flash one of those 2.6 or 2.8 GHz kernels, and do the test, and message me if Antutu finishes the benchmark even once
Click to expand...
Click to collapse
will do.
If you want higher you should try out Ultimate Kernel. Although it is removed from XDA, you can still find it on some foreign language site. It's the highest and most stable OC kernel I have used (3.0GHz).
Graffiti Exploit said:
If you want higher you should try out Ultimate Kernel. Although it is removed from XDA, you can still find it on some foreign language site. It's the highest and most stable OC kernel I have used (3.0GHz).
Click to expand...
Click to collapse
3.0 GHz
any benchmark screenshots ??
Graffiti Exploit said:
If you want higher you should try out Ultimate Kernel. Although it is removed from XDA, you can still find it on some foreign language site. It's the highest and most stable OC kernel I have used (3.0GHz).
Click to expand...
Click to collapse
Hmm, just found the topic, and it's mentioned that the topic was close due to non-compliance with the GNU GPLv2 and XDA forum rules, now what's the former thing?
Anyone has the latest version, if it's still updated outside XDA? Want to try it.
djak272 said:
3.0 GHz
any benchmark screenshots ??
Click to expand...
Click to collapse
Sorry cleaned up my screenshots folder as it was taking up a lot of space. Besides Antutu has been constantly getting updates so it may not be accurate.
devilsdouble said:
Hmm, just found the topic, and it's mentioned that the topic was close due to non-compliance with the GNU GPLv2 and XDA forum rules, now what's the former thing?
Anyone has the latest version, if it's still updated outside XDA? Want to try it.
Click to expand...
Click to collapse
I don't know if this is allowed but here it is.
v72
http://www.android-hilfe.de/custom-...ernel-kitkat-tw-only-ultimate-kernel-v72.html
v73
https://www.androidsource.club/foru...kernel-ultimate-kernel-v73-galaxy-note-3.html
Last one I used was v63. So do test it out more because I cannot vouch for the updates. But based from experience, I have never gotten an unstable update from that kernel.
Graffiti Exploit said:
Sorry cleaned up my screenshots folder as it was taking up a lot of space. Besides Antutu has been constantly getting updates so it may not be accurate.
I don't know if this is allowed but here it is.
v72
http://www.android-hilfe.de/custom-...ernel-kitkat-tw-only-ultimate-kernel-v72.html
v73
https://www.androidsource.club/foru...kernel-ultimate-kernel-v73-galaxy-note-3.html
Last one I used was v63. So do test it out more because I cannot vouch for the updates. But based from experience, I have never gotten an unstable update from that kernel.
Click to expand...
Click to collapse
Thanks a lot for the link mate. Downloaded and flashed v73, but I can't get it past the stock clock rate of 2265 MHz! I mean I have tried to set higher frequency than that in S Tweaks, even downloaded Trickstar, SetCPU, but the it'd just stuck at 2265 MHz! I can go lower than 2265 but not higher! Weird!
devilsdouble said:
Thanks a lot for the link mate. Downloaded and flashed v73, but I can't get it past the stock clock rate of 2265 MHz! I mean I have tried to set higher frequency than that in S Tweaks, even downloaded Trickstar, SetCPU, but the it'd just stuck at 2265 MHz! I can go lower than 2265 but not higher! Weird!
Click to expand...
Click to collapse
I think it comes with 2 apps for customization. You apply frequency on the first one and open the other and select apply changes. I'm not sure if it was this kernel or was it AEL. Lol. Anyways good luck. Maybe your ROM doesn't support a certain "stuff". I'm sorry but I really forgot about those terminologies. You can read up on the closed thread if you want. I'm sure you'll have a clue or on that link I gave you. *Google Translate ftw*