I am not sure what exactly goes where and I'm tired of messing with it.
This is what I'm looking at:
#alloctest 0x2000
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd initrd.gz
#
# The following kernel parameters are useful
# ppp.username - The username used to connect to the network when dialing
# ppp.password - The password used to connect to the network when dialing
# ppp.apn - Set apn of your provider
# ppp.nostart - Set ppp.nostart=1 to disable starting the ppp connection on boot
# msm_sdcc.msmsdcc_fmax - The maximum frequency (in Hz) used by the SD controller
# pm.sleep_mode - The mode used when the phone is off
# 0=Power Collapse Suspend, 1=Power Collapse, 2=Apps Sleep,
# 3=Slow Clock and Wait for Interrupt 4=Wait for Interrupt
# Default is 1, use 1 for best power savings
# board-htckaiser.panel_type - Panel type used to power the panel off and on
# 0=Don't power off the panel (Default)
# 1=Sony 2=Topoly 3=Topoly (probably just the same as 2)
# lcd.density - Defaults to 160, 128 shows more on screen
#
set cmdline "board-htckaiser.panel_type=0 ppp.apn=www.vodafone.net.nz ppp.username=none ppp.password=none pm.sleep_mode=1 mddi.width=324 mddi.height=432 no_console_suspend board-kaiser-keypad.atttilt=0"
boot
Please just send me the file to [email protected]
C'mon, search the wiki. It took me a whole 30 sec to find this!
set RAMSIZE 0x07000000
set RAMADDR 0x10000000
set FBDURINGBOOT 0
set MTYPE 1553
set KERNEL zImage
set initrd "\Storage Card\initrd.gz"
set cmdline "[email protected] ppp.password=CINGULAR1 board-kaiser-keypad.atttilt=0 pm.sleep_mode=4 board-htcvogue.panel_type=0 msm_sdcc.msmsdcc_fmax=20000000 no_console_suspend"
boot
Click to expand...
Click to collapse
Dave
Still not connecting to internet. Do I need to erase all the other stuff out of the middle?
Do you need to ask this in another thread?
DaveTheTytnIIGuy said:
C'mon, search the wiki. It took me a whole 30 sec to find this!
Dave
Click to expand...
Click to collapse
Thanks. It worked. However, now all the icons and fonts are huge. I have to zoom out every time I go to a new page. Plus my dialing pad numbers are all smushed together and the home screen icons as well.
Does anyone know how to (if at all possible) overclock a Milestone running the CyanogenMod ROM? I've tried Milestone overclock but it only works with the original ROM and reboots my phone instantly after applying changes.
I've also tried using G.O.T. OpenRecovery from Recovery mode to overclock it, and it says it applied successfully, but after booting the phone back into Cyanogen it says it's still at a sad 550MHz.
Any suggestions or apps would be greatly appreciated!!
Thanks
First of all you must be Rooted. (Just mentioning it, I guess you are.. )
Now, with Androidiani Recovery you get a set of Pre-fixed Overclocked sets up to 1.1GHz.
With GOT Recovery you choose the MHz and vsel you want to use.
One time I was flashing a newer ROM, did the Overclock through GOT, it said "Applied successfully" but It didn't work. Problem was I forgot to Root again the phone. So don't forget that.
/system/etc/init.d/10overclock
here is OC, edit it with root explorer
Thanks Babis_ECE... So after overclocking it with GOT I have to ROOT the phone a second time? If so I will try it, but could you explain why?
petyo.tsanov said:
/system/etc/init.d/10overclock
here is OC, edit it with root explorer
Click to expand...
Click to collapse
Found the file with Root Explorer but it won't actually open the file. Also, you say to edit it, is it as simple and changing the MHz or is it more complex than that?
Babis_ECE said:
First of all you must be Rooted. (Just mentioning it, I guess you are.. )
Now, with Androidiani Recovery you get a set of Pre-fixed Overclocked sets up to 1.1GHz.
With GOT Recovery you choose the MHz and vsel you want to use.
One time I was flashing a newer ROM, did the Overclock through GOT, it said "Applied successfully" but It didn't work. Problem was I forgot to Root again the phone. So don't forget that.
Click to expand...
Click to collapse
Thanks Babis_ECE... So after overclocking it with GOT I have to ROOT the phone a second time? If so I will try it, but could you explain why?
You didn't get what I meant. I am just saying, Root again your phone through Recovery (GOT, Androidiani, etc) and then try again to Overclock. I believe it will do the trick.
you say your are running cyanogen already? then dont use GOT open recovery. use androidiani open recovery.
i believe from androidiani you can change overclocks, but normally i just do it myself.
what you do is find that file in root explorer, make root explorer read/write ("R/W"button in the top right), long press the file, open in text editor, and change the values.
you're going to see a part of the file that looks like this:
Code:
echo 58 > /proc/overclock/max_vsel <-change this
echo 900000 > /proc/overclock/max_rate <-change this
#echo "5 900000000 60" > /proc/overclock/mpu_opps
echo "4 700000000 48" > /proc/overclock/mpu_opps <-change this
echo "3 550000000 42" > /proc/overclock/mpu_opps <-change this
echo "2 250000000 30" > /proc/overclock/mpu_opps <-change this
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 900000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table <-change this
echo "2 550000" > /proc/overclock/freq_table <-change this
echo "3 250000" > /proc/overclock/freq_table <-change this
milestonefail said:
you say your are running cyanogen already? then dont use GOT open recovery. use androidiani open recovery.
i believe from androidiani you can change overclocks, but normally i just do it myself.
what you do is find that file in root explorer, make root explorer read/write ("R/W"button in the top right), long press the file, open in text editor, and change the values.
you're going to see a part of the file that looks like this:
Code:
echo 58 > /proc/overclock/max_vsel <-change this
echo 900000 > /proc/overclock/max_rate <-change this
#echo "5 900000000 60" > /proc/overclock/mpu_opps
echo "4 700000000 48" > /proc/overclock/mpu_opps <-change this
echo "3 550000000 42" > /proc/overclock/mpu_opps <-change this
echo "2 250000000 30" > /proc/overclock/mpu_opps <-change this
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 900000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table <-change this
echo "2 550000" > /proc/overclock/freq_table <-change this
echo "3 250000" > /proc/overclock/freq_table <-change this
Click to expand...
Click to collapse
Thanks for the specific details, but I am still missing something. What do I change those values to? Obviously it'll depend on what I want to overclock the phone to, but it's not written as simple as 600MHz or 1GHz. I just don't want to start putting #'s in assuming that I'm doing it right. Sorry to be a pain, but I want to make sure I don't screw up my phone.
gingalls said:
Thanks for the specific details, but I am still missing something. What do I change those values to? Obviously it'll depend on what I want to overclock the phone to, but it's not written as simple as 600MHz or 1GHz. I just don't want to start putting #'s in assuming that I'm doing it right. Sorry to be a pain, but I want to make sure I don't screw up my phone.
Click to expand...
Click to collapse
900000 = 900000 kHz = 900 MHz = .9 GHz
therefore, 600MHz = 600000
1 GHz = 1000000
etc.
the other numbers (60, 48, 42 etc) are the vsel aka the voltage. fyi, stock is 56. you probably dont want to set these too high (like higher than 64, 68 maybe). experiment to see what is stable for your phone. people on this forum gotten pretty low
there's an overclocking thread you can read for more info. just dont try to follow any outdated instructions.
milestonefail said:
900000 = 900000 kHz = 900 MHz = .9 GHz
therefore, 600MHz = 600000
1 GHz = 1000000
etc.
the other numbers (60, 48, 42 etc) are the vsel aka the voltage. fyi, stock is 56. you probably dont want to set these too high (like higher than 64, 68 maybe). experiment to see what is stable for your phone. people on this forum gotten pretty low
there's an overclocking thread you can read for more info. just dont try to follow any outdated instructions.
Click to expand...
Click to collapse
OK, so the fact that the echo has a # in front of it means the overclocking will not reach 900MHz, but the 3 options below it will fluctuate based on what the phone is trying to do? In other words my phone will actually over and under clock itself on the fly anywhere between echo 700000000 (700MHz), 550000000 (550MHz) and 250000000 (250MHz)? So if I change all 3 of those #'s to say 800000000 (800MHz) then it will stay at 800MHz constantly? If I'm right I'm assuming I'll have to change the 700000, 550000 and 250000 #'s all to 800000 as well?
gingalls said:
OK, so the fact that the echo has a # in front of it means the overclocking will not reach 900MHz, but the 3 options below it will fluctuate based on what the phone is trying to do? In other words my phone will actually over and under clock itself on the fly anywhere between echo 700000000 (700MHz), 550000000 (550MHz) and 250000000 (250MHz)? So if I change all 3 of those #'s to say 800000000 (800MHz) then it will stay at 800MHz constantly? If I'm right I'm assuming I'll have to change the 700000, 550000 and 250000 #'s all to 800000 as well?
Click to expand...
Click to collapse
those first two lines (with the 900000 and 58 in my case) are counted as well. so there are 4 levels. for me they are 900 MHz, 700, 550, and 250. you might want to install the SetCPU app as well so you can see and manage the steps. also, if you change the first one to 800000, it wont stay at 800 constantly. it will ramp up to that frequency when needed, but it will lower itself to one of the lower frequencies when you dont need that much processing power.
just so you know, every line that starts with # is a commented out line (doesnt affect the code)
Babis_ECE said:
You didn't get what I meant. I am just saying, Root again your phone through Recovery (GOT, Androidiani, etc) and then try again to Overclock. I believe it will do the trick.
Click to expand...
Click to collapse
Unfortunately this did not work
gingalls said:
Unfortunately this did not work
Click to expand...
Click to collapse
its not going to work because you cant use GOT open recovery with cyanogen mod
hey you guys (and girls if there are any)
I'm using The froyo mod 2.9, and android 2.2.2
I'm having a little heat and battery problem,
but, I don't want to change the mod to something else.
I saw that there is a option to flash a ULV setting for the proccessor,
then, the phone can achive extra battery life and lower heat,
without leaving the froyomod.
because I'm a newbie, I wanted to ask, how it can be done?
It will affect the froyo mod?
are there any other problems that I need to be aware of?
thanks alot :]
*edit : found the ULV packs, how should I install them? as an Update (OR/updates) ? do I need to make any cache clear or not? and if I need to make a clear cache, wich one and what are the affect of the cleaning? (or wipe :/ )
thanks!
Why don't you just change your OC-settings in the OR overclocking menu?
if you have to go, don't say goodbye..
TBH I found that even running ULV didn't help battery usage much on FroyoMod, nor heat.
Anyway just put the ULV.zip from the FroyoMod thread into your OpenRecovery/Updates/ folder and update from AOR. Nothing will happen as it only updates the 10overclock file.
As already told the ULV just replaces the 10overclock file in system/etc/init.d
You have to adjust the settings yourself.
#!/system/bin/sh
insmod /system/lib/modules/overclock_milestone_21.ko
echo 0xc0295704 > /proc/overclock/cpufreq_stats_update_addr
echo 0xc004e4b0 > /proc/overclock/omap2_clk_init_cpufreq_table_addr
echo YOUR VALUE > /proc/overclock/max_vsel
echo YOUR VALUE> /proc/overclock/max_rate
#echo "5 800000000 48" > /proc/overclock/mpu_opps
echo "4 700000000 46" > /proc/overclock/mpu_opps
echo "3 500000000 35" > /proc/overclock/mpu_opps
echo "2 250000000 27" > /proc/overclock/mpu_opps
#echo "1 125000000 32" > /proc/overclock/mpu_opps
#echo "0 800000" > /proc/overclock/freq_table
echo "1 700000" > /proc/overclock/freq_table
echo "2 500000" > /proc/overclock/freq_table
echo "3 250000" > /proc/overclock/freq_table
insmod /system/lib/modules/cpufreq_interactive.ko
echo interactive > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
insmod /system/lib/modules/cpufreq_conservative.ko
#echo conservative > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo 125000 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/sampling_rate
#echo 25 > /sys/devices/system/cpu/cpu0/cpufreq/conservative/freq_step
Click to expand...
Click to collapse
I think [email protected] is the best, but [email protected] will work too, but your battery will drain quite fast.
What is the best %(size) of swappiness? i have 60 now how about 30 or 40
goldenr said:
What is the best %(size) of swappiness? i have 60 now how about 30 or 40
Click to expand...
Click to collapse
Definition: Swappiness is tendency of kernel to move memory(Real ram) to swap partition/file.
So, Swappiness 100 = move to swap partition/file more. (Many ram, high latency)
Swappiness 0 = move Don't move unless memory(Real ram) is really full. (Less ram, low latency)
So, heavy game = Swappiness 50-100 (Noticable lag at start but, smooth later on)
Smooth operation = Swappiness 0-50
Update : Aug 8th 2017
These settings should benefit any helio X10 device maybe even other mediatek octa core devices.
The idea behind these settings is to keep the CPU in the lower frequency states and prevent unnecessary power drain when performing simple tasks.
to apply these settings I used Kernel Aduitor.
First Up Interactive Governor Settings
Code:
[SIZE="3"]Above hispeed delay - 20000 1326000:30000 1469000:40000 1781000:10000
Bootpulse duration - 0
hispeed freq - 1183000
boost - 0
go hispeed load - 70
io is busy - 0
min sample time - 20000
target loads - 60 1183000:80 1326000:90 1469000:97 1625000:99
timer rate - 25000
timer slack - 35000[/SIZE]
Limit you CPU to 1781MHz To save some battery all 1.9GHz does is produce heat and the performance isn't worth it.
Also you must disable touch-boost by editing the build prop line; ro.mtk_perfservice_support=1 to ro.mtk_perfservice_support=0
This will save a lot of battery life as the CPU won't jump to high frequencies when you touch the screen.
Also in Virtual Memory settings set the folowing
dirty ratio - 90
dirty background ratio - 80
dirty expire centisecs - 1000
dirty writeback centisecs - 2000
swappiness - 40
vfs cache pressure - 10
Z-RAM disksize - 300MB
Next up....... RAM management so the HTC X9 RAM management is good but it can be made better by going into the low memory killer tab in Kernel Auditor and tapping on the light option.
and that is it. we can't do much without a custom Kernel......... Also you can increase entropy by changing it's read value to 1664 and write value to 2048. I don't know if this is needed on marshmallow but I did it anyway.
Even more battery Savings
You will need Tasker for the following.............
Note: This Will limit your CPU to 5 cores and reduce unecessary CPU Scaling also will disable some bug checks
Make a new 'device boot' profile and add the following as tasks
1. Wait 30s
2.Run Shell:
Code:
[SIZE="3"]
su
echo "0" > /sys/module/alarm_dev/parameters/debug_mask
echo "0" > /sys/module/alarmtimer/parameters/debug_mask
echo "0" > /sys/module/binder/parameters/debug_mask
echo "0" > /sys/module/earlysuspend/parameters/debug_mask
echo "0" > /sys/module/sbsuspend/parameters/sbsuspend_debug_mask
echo "0" > /sys/module/pvrsrvkm/parameters/gPVRDebugLevel
echo "0" > /sys/module/musb_hdrc/parameters/debug_level
echo "0" > /sys/module/lowmemorykiller/parameters/debug_level
echo "5" > /proc/hps/num_limit_low_battery
echo "5" > /proc/hps/num_limit_power_serv
echo "5" > /proc/hps/num_limit_thermal
echo "5" > /proc/hps/num_limit_ultra_power_saving
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
echo "1781000" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo "1781000" > /proc/cpufreq/cpufreq_limited_max_freq_by_user
echo "0" > /proc/gpufreq/gpufreq_input_boost
echo "0-4" > /dev/cpuset/foreground/cpus
[/SIZE]
Make Another tasker Profile 'on device unlock'
1.Run Shell;
Code:
[SIZE="3"]
su
echo "99" > /proc/hps/up_threshold
echo "90" > /proc/hps/down_threshold
echo "0" > /proc/hps/rush_boost_enabled
echo "0" > /proc/hps/input_boost_enabled
[/SIZE]
Credits;
jajk - Learned a lot from his Skinny Custom Boot thread.
I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.
m3johan said:
I haven't noticed any freezing on my device. Everything runs smoothly all the time.
I will test your settings if it starts annoying me.
I guess the x9 isn't the most popular phone for rooters.
Click to expand...
Click to collapse
nope
thx.methods u said work on my htc x9.but like the 'Even more battery Savings' i not done yet
Htc one x9
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.
Lord Dre said:
Hello, am new here. I came on here cos I need help with my HTC One X9. You have to forgive me if I ask dumb questions cos like I said earlier, am new to everything here. So please be patient with me.
While in use, my fone drops from say 90% to zero and then shuts down. After a while when I turn it on, battery returns to 90%. At other times, while in use it shuts down even when charging....in this state it reboots several times and gets very hot.
Please what can I do? Thank you.
Click to expand...
Click to collapse
It's battery problem, Chagne it