I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:
It is so. You can't do nothing about it. Some kernel devs modify that value and write 1.8GHz for example it was on SebastianFM's Overclocked kernel if I remember correctly.
And remember, flashing a kernel before flashing a ROM is like pushing the gas pedal of a car before starting the engine.
Plus, when you flash the ROM, it will replace your kernel with its own.
The Revelation™ ushered in a revolution... Right on, SebastianFM!
Anti_simlock said:
I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:
Click to expand...
Click to collapse
don't look what says in about phone
about phone takes the info from the build.prop file(if i am not wrong)
to see your current freq use setcpu,kernel tuner or system tuner
also do a test with antutu benchmark and it will show you your current cpu freq in the results
rzr86 said:
about phone takes the info from the build.prop file(if i am not wrong)
to see your current freq use setcpu,kernel tuner or system tuner
also do a test with antutu benchmark and it will show you your current cpu freq in the results
Click to expand...
Click to collapse
+1
Anti_simlock said:
I'm running ARHD 7.3 and also flashed the Sultan Kernel (this) but Android is still showing 1.5ghz in the "about phone" section.
Do I need to flash the kernel before I install the ROM?
thx in advance:laugh::good:
Click to expand...
Click to collapse
If you want to change what shows up in about phone, mount system as rw, open /system/build.prop in a text editor. Scroll down and you'll see a section named about phone. Edit whatever you want.
Happy to help.
Related
Hi,
I am currently using the following:
OC Kernel based on Netarchy's overclock parameters
Primes! 1.8.4
Can I flash to "Clemsyn-Blades-CPAjuste-supercurio OC kernel for 3.2 elite ver 12" directly from the above?
Thanks,
1) kernel
2) yup. just make sure you get the kernel meant for prime.
3) remember to flush cache and dalvik.
Cool thanks, will try it tonight.
PS: Yeah I realized I got the spelling error after I hit submit.
Disclaimer:
I don't take any responsibility if your phone explodes, your girl/boyfriend breaks up with you or any other stuff.
Do not flash on anything else than an GT-S7500! No L model or W model, else you get a shiny brick.
Don't forget your warranty will get void if you flash this trough odin. (Unless someone figures out a way to reset the custom binary counter)
So flash AT YOUR OWN RISK.
Click to expand...
Click to collapse
Based on official Samsung Sources. Governors copied from freexperia github. Other changes by me.
Features:
- unsecured
- smartassV2
- SavagedZen (beware: in sleep mode cpu speed is capped at 480Mhz)
- noop sheduler by default
- minimium frequency set at 122Mhz
- enabled 19Mhz and 61Mhz frequencies (use setcpu or similar)
Click to expand...
Click to collapse
Tested with S7500XXLC2/S7500OXXLC1/S7500XXLC2. Flash with odin.
OC Build:
- Overclock frequencies seem to have the same performance but OC is indeed working, thanks to mb-14!
(Confirmed after many tests quadrant/setcpu/neocore cpu frequency is the same from minimal overclock to 1200Mhz)
- My phone as crashed 3 since I've overclocked it, so beware!
- Unless there is a better way of ocing, my newer builds will have oc disabled.
OC build v2 (31 May, 22h):
- Removed all overclock frequencies but 1200Mhz.
Bugs affecting all builds (even official ones):
- "Fuel gauge" might be bugged (maybe due to old/bugged samsung sources?) update:might be an rom bug instead.
- 3 pole headphones have noise in one channel and then the noise disappears (jack sensing bug?)
Sources Help & feedback are appreciated.
EDIT:
New kernel posted minimal changes again (samsung config updated from a new version LE1)
If you don't want an yellow triangle at boot flash my custom rom and then flash the kernel using the terminal.
1-Extract the tar.md5 file
2-Copy the boot.img to the sdcard
3-Use the terminal (or adb) as root to cd to the sdcard folder
4-Then type this "dd if=boot.img of=/dev/block/mmcblk0p8"
If you want to flash a custom recovery it works too, type "dd if=recovery.img of=/dev/block/mmcblk0p12"
Then you can flash whatever rom you want as long you don't use odin to flash an custom kernel or recovery you can keep your warranty intact (if you never flashed any custom kernel/recovery that is).
Keep in mind that this doesn't clear the counter only makes the triangle go away.
Click to expand...
Click to collapse
Custom recovery based on cm9 (5.5.0.4) posted (appears to work fine but more testing is required). Bootloop fixed. If you get stuck in recovery (unknown boot mode) go to "advanced" and choose "reboot recovery" when it is finished rebooting into cwm again choose "reboot system now".
DEVELOPMENT IS STOPPED. I no longer have the ace plus.
successfully flashed on my S7500DDLD1...only thing i noticed is after the flashing is complete phone doesnt boot normally but stays in download mode so i manually rebooted and i have ur kernel on my phone...take ur time and improvise it (startup scripts ,CM/MIUI support) , ALL THE BEST...
Wot's the benefit to flash custom kernel??.... Anyway gud step move ahead in making custom rom also for ace plus
Sent from my GT-S7500 using Tapatalk 2
deadwood01 said:
successfully flashed on my S7500DDLD1...only thing i noticed is after the flashing is complete phone doesnt boot normally but stays in download mode so i manually rebooted and i have ur kernel on my phone...take ur time and improvise it (startup scripts ,CM/MIUI support) , ALL THE BEST...
Click to expand...
Click to collapse
Odd mine rebooted and worked fine on first attempt. I've only messed with one script so far. I'm still thinking what I should add to the kernel.
I'm trying to build aosp but so far no luck.
balliboxer said:
Wot's the benefit to flash custom kernel??.... Anyway gud step move ahead in making custom rom also for ace plus
Sent from my GT-S7500 using Tapatalk 2
Click to expand...
Click to collapse
So far it's to have new governors and a new sheduler.
BUG :
1 . When on savagedzen gov unlocking the phone from sleep is delayed/laggy also if u r listening to music and the lock the screen then the music starts lagging tried increasing the min freq still the same , may be something like a deep sleep or sod bug..
deadwood01 said:
BUG :
1 . When on savagedzen gov unlocking the phone from sleep is delayed/laggy also if u r listening to music and the lock the screen then the music starts lagging tried increasing the min freq still the same , may be something like a deep sleep or sod bug..
Click to expand...
Click to collapse
I'm trying to reproduce the bug, but since my phone is still charging I can't seem to get the music lagging. What music app and music format are you using?
blackburner said:
I'm trying to reproduce the bug, but since my phone is still charging I can't seem to get the music lagging. What music app and music format are you using?
Click to expand...
Click to collapse
Stock music player , mp3 format...
Even while charging the bug exists...
deadwood01 said:
Stock music player , mp3 format...
Even while charging the bug exists...
Click to expand...
Click to collapse
Strange I can't seem to make it lag on savagedzen. The UI feels slower but music isn't lagging. Do you have any sound effect enabled?
Edit: I've got lag when using the EQ and waking the phone.
Edit 2: I've uploaded a hopefully fixed version, let's also hope that the changes that I made won't screw up the battery life.
flashed test kernel 3
the same bug exists wen used with EQ but the intensity of the bug is only 20% compared to the previous one also increasing the min freq to 480 completely nullifies the bug...also with EQ off the bug doesnt exist
will see how the battery life is... btw have u played with the drivers/bus to change the battery life...?
I can't get any lag at all now (after v3). Can you give my all your parameters? EQ settings, mp3 bitrate, where is your music stored and if using an sd card what type of sd card are you using.
I've set the minimum at 19Mhz and on air plane mode and by morning I still had the same battery than yesterday (89%).
The only thing that I changed was the cpu frequency table to include 800 Mhz at the same voltage than 600 Mhz and so far it seems ok, but might not be true to all phones.
blackburner said:
If anyone wants the sources just ask! (Maybe setting up a github account is a good idea?) Help is appreciated.
Click to expand...
Click to collapse
Setting up a github repo is indeed a good idea.Maybe then i can help
mb-14 said:
Setting up a github repo is indeed a good idea.Maybe then i can help
Click to expand...
Click to collapse
I've posted a link to the sources on github. I'm still learning how to use git. But I'm still uploading the sources.
Edit: Uploaded!
Can anybody help me with the cpu frequencies? I've cracked part of it but I don't know what to change since if OC to 1200Mhz I only get 600 Mhz performance
I've attached the table I'm using (xls since ods xda upload gave me the finger lol)
blackburner said:
Can anybody help me with the cpu frequencies? I've cracked part of it but I don't know what to change since if OC to 1200Mhz I only get 600 Mhz performance
I've attached the table I'm using (xls since ods xda upload gave me the finger lol)
Click to expand...
Click to collapse
Check my fork of your kernel on my github.I have got OC working.
P.S: Could you update your repo to the latest kernel source from samsung?My net speed is very sucky
mb-14 said:
Check my fork of your kernel on my github.I have got OC working.
P.S: Could you update your repo to the latest kernel source from samsung?My net speed is very sucky
Click to expand...
Click to collapse
I don't see any new kernel versions on the Samsung open source release center.. I'm still going to test oc did you change anything else than the CPU frequency table?
Edit: Overlclock is working! Thanks to mb-14!
Anyway it looks like the cpu when on OC is always working at the same frequency, since by overclocking it to 1017 I get an 150 ms reduction on setcpu native bench. And it remains the same for all the other frequencies.
For what I've understanded of PLL and CPU clocks looks like the cpu is running at 1200 MHz. (In the frequency table you can claim any frequency but it doesn't mean the cpu is running at that speed)
Edit: With OC my phone crashes after a while (ram dump mode)
Edit 2: Neocore doesn't seem to care too about the cpu frequency I set above the stock 1008Mhz. From 1017Mhz to 1200Mhz the score is always the same (85,6Fps)
Hello,
i have flash your kernel and its running very good!
Galaxy S7500
2.3.6 (S7500XXLA3)
Antutu 3596
Quadrant 2458
Neocore 85,4fps (1018mhz-1200mhz)
with OC 1,2GHZ and Performace mode
thanks!
I wait for the next version
heXXer321 said:
Hello,
i have flash your kernel and its running very good!
Galaxy S7500
2.3.6 (S7500XXLA3)
Antutu 3596
Quadrant 2458
Neocore 85,4fps (1018mhz-1200mhz)
with OC 1,2GHZ and Performace mode
thanks!
I wait for the next version
Click to expand...
Click to collapse
So you found no difference between overclocked frequencies too?
Unfortunately, no difference....
im upgrading the kernel...
my wish:
can you try to integrate the BLN mod?
I found a manual but I have to search again...
thanks
Edit: with new test_stable kernel (1008mhz) 84,3fps neocore
before with 1018mhz it was at 85,4fps
heXXer321 said:
Unfortunately, no difference....
im upgrading the kernel...
my wish:
can you try to integrate the BLN mod?
I found a manual but I have to search again...
thanks
Edit: with new test_stable kernel (1008mhz) 84,3fps neocore
before with 1018mhz it was at 85,4fps
Click to expand...
Click to collapse
the bln mod sounds useful I will check it out!
Edit: flash the new oc version
Yesss!It is very useful!!
neocore says 85,5fps
Edit: The statistic from nofrills cpu control shows that cpu step 61mhz not is in use.my min frequenz is 19mhz.
sorry for my bad english im german ;-)
who finds fault, may keep them ;-)
Hi everyone,
It's my fist post on XDA forum :angel:
I have problem with overclocking my GPU in Sensation. I tried to change "30000000" to "echo 32000000" in max_gpuclk file.
(/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk)
But it does not work. I use "root explorer".
After editing file and click save changes I see something like that: "File saved. Original file backed up as max_gpuclk.bak"
But when I trying to check this file there is still "300000000"
Any ideas ?
:fingers-crossed:
pawel30w said:
Hi everyone,
It's my fist post on XDA forum :angel:
I have problem with overclocking my GPU in Sensation. I tried to change "30000000" to "echo 32000000" in max_gpuclk file.
(/sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/max_gpuclk)
But it does not work. I use "root explorer".
After editing file and click save changes I see something like that: "File saved. Original file backed up as max_gpuclk.bak"
But when I trying to check this file there is still "300000000"
Any ideas ?
:fingers-crossed:
Click to expand...
Click to collapse
If I'm not wrong, you need to have a kernel which supports the 320Mhz 3D GPU value in order for you to OC to that value. Which kernel are you using?
wlteh said:
If I'm not wrong, you need to have a kernel which supports the 320Mhz 3D GPU value in order for you to OC to that value. Which kernel are you using?
Click to expand...
Click to collapse
I have SebastianFM kernel 1.5.2.
and CPU on 1782 MHz
in HTC Sensation XE
pawel30w said:
I have SebastianFM kernel 1.5.2.
and CPU on 1782 MHz
Click to expand...
Click to collapse
Shouldn't have any problems with SebastianFM's kernel. Is it because you realize that it doesn't stick after a reboot? In order to get the settings to stick, you need to put it into a script and place the script in the /etc/init.d folder.
I use this app, works very very good, for oc cpu, gpu, voltages, and some tweaks like disable vsync.
http://forum.xda-developers.com/showthread.php?t=1719934
PS.: Press thanks button
go to system/etc/init.qcom.post_boot.sh
search for the line echo '300000000' sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/gpu_maxclk
change the ' ' to 320000000
and see if it changed.i think it will work
rzr86 said:
go to system/etc/init.qcom.post_boot.sh
search for the line echo '300000000' sys/devices/platform/kgsl-3d0.0/kgsl/kgsl-3d0/gpu_maxclk
change the ' ' to 320000000
and see if it changed.i think it will work
Click to expand...
Click to collapse
I've looked for and I didn't find these line. I copied that file to my PC, and I didn't find it again ;/
But I think @insestito app is working są it's ok
Thanks guys
pawel30w said:
I've looked for and I didn't find these line. I copied that file to my PC, and I didn't find it again ;/
But I think @insestito app is working są it's ok
Thanks guys
Click to expand...
Click to collapse
for sure check gpu_maxclk if it shows you 320000000
follow the path as i mentioned in my previous post
I was running Cromi 4.7 and upgraded to 5.3 today. I also switched over to Hund's 3.4 kernel.
Now, when I change the power setting to performance or eco, the tablet freezes and then restarts (in Balanced mode).
The options I picked during the install process are-
US hunds with experimental tweaks
Software rendering disabled
GPU OC
CPU OV
GPU UV
I can't figure out if I messed something up during the install or if I need to play with the settings in Hunds app. Any ideas?
vickker said:
I was running Cromi 4.7 and upgraded to 5.3 today. I also switched over to Hund's 3.4 kernel.
Now, when I change the power setting to performance or eco, the tablet freezes and then restarts (in Balanced mode).
The options I picked during the install process are-
US hunds with experimental tweaks
Software rendering disabled
GPU OC
CPU OV
GPU UV
I can't figure out if I messed something up during the install or if I need to play with the settings in Hunds app. Any ideas?
Click to expand...
Click to collapse
If you are using Hund v3.4.3 ET with the ET build.prop, you should NOT install the GPU OC, CPU OV, and GPU UV because the ET is already UV/OC for the kernel. Can you tell me what you have in your init folder? You can go here and find it: "/system/ect/init". It is a easy fix that I believe... One more question, did you do a clean installation with a data format?
Thanks,
LMK
LetMeKnow said:
If you are using Hund v3.4.3 ET with the ET build.prop, you should NOT install the GPU OC, CPU OV, and GPU UV because the ET is already UV/OC for the kernel. Can you tell me what you have in your init folder? You can go here and find it: "/system/ect/init". It is a easy fix that I believe... One more question, did you do a clean installation with a data format?
Thanks,
LMK
Click to expand...
Click to collapse
Thanks so much for helping me out with this.
I misunderstood the relationship between the kernel and the ROM. I thought the kernel made those options possible, but that I still needed to select them. So, simply using Hund v 3.4.3 ET enables these options automatically.
The init.d folder has the following files in it: 50CleanTWEAKS, 70B2R, 80Fsync, 89OV, 90 UV, 91GPUUV, and 99hundsapp.
Before I flashed the ROM I did a factory reset with TWRP.
vickker said:
Thanks so much for helping me out with this.
I misunderstood the relationship between the kernel and the ROM. I thought the kernel made those options possible, but that I still needed to select them. So, simply using Hund v 3.4.3 ET enables these options automatically.
The init.d folder has the following files in it: 50CleanTWEAKS, 70B2R, 80Fsync, 89OV, 90 UV, 91GPUUV, and 99hundsapp.
Before I flashed the ROM I did a factory reset with TWRP.
Click to expand...
Click to collapse
I think that your problem is that you under voltage too much which causes the kernel running unstable... So you could try this to see if you can fix your issues...
First, you may want to do a nandroid back from TWRP. Just in case you want to go back to your original state...
Second, delete these files from your init folder: "89OV, 90 UV, 91GPUUV".
Third, reboot your device and see if it is still rebooting when switching to performance mode....Good luck...:fingers-crossed:
Please report back what is happening when you delete those files, thanks..
Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????
Lynxen said:
Hello xda!
Theres something strange going on with my Sensation..
I can not set up my own frq's.
Everytime I set some it goes higher. For example..
I am @ 1080-475 I switch the window to set some profiles and back to the main. bah.. Current max: 1134.. 1450.. 1552.. 1134.
Bar I set before should lock it @ 1080 and it does but just in practice.
I was trying to set some other governors with no succes. It goes higher everytime.
Root acces was given, ROMs tested.
I got phone from my brother. Is it even possible to change some hardware settings or wtf is it that block my ideas????
Click to expand...
Click to collapse
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")
rzr86 said:
what rom do you have?
insert this line in init.qcom.post_boot.sh file
echo the value > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
in the <the value> put your desired freq
do the same for cpu1
then reboot
note: put the lines where it starts with :
case "$target" in
"msm8960")
Click to expand...
Click to collapse
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.
Lynxen said:
I am using SlimKat and Viper. Same bug excist @ both of the roms. Kernels provided with shantur, sebastian and libelty are bugged.
I've changed those values with no results. Once I was trying to set maxcpu_info my root explorer stucked @ saving process. Sth was remaking values @ 1540000 mhz just after rootacces was given to explorer. Some deep **** is going down there.
That's why Sensations are overheating, it's same bug threw all stock kernels/rom @ this forum.
Max values can not be set! They re permanent for some reason - failed coding I suppose.
Libelty Kernel fix Vipers issues. There's no kernel working with KK.
Click to expand...
Click to collapse
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock
rzr86 said:
liberty's and sebastianFM's kernel aren't bugged
i have changed cpu frequencies successfully
in vipers rom disable pnpmanger from venom tweaks
then put your desired cpu freq
about slimkat rom i can't tell you somethig because i have never used that rom
also in stock kernels you can't changed nothing
they do not support overclock or underclock
Click to expand...
Click to collapse
It's possible to scale CPU frequency in slimkat ROM too.