Originally Posted by malybru

Hi,

The "Android is upgrading!" is normal after you clear cache and dalvik.
Have you upgraded from GB?
There are a lot of quirky little differences,which you just have to get used to.



---------- Post added at 11:43 AM ---------- Previous post was at 11:35 AM ----------



Hi,

Go to market and get "Super tool box 10 +"(free)
Then,see if you can move them to your phone with that.

What do you mean by "dalvik"? and how do you clear the cache? I upgraded from GB. I'm half tempted to now do a factory reset and start from scratch.

So the missing messages tab is an ICS quirk, and not something I've done?

Thanks

Originally Posted by CloneboyZA

What do you mean by "dalvik"? and how do you clear the cache? I upgraded from GB. I'm half tempted to now do a factory reset and start from scratch.

So the missing messages tab is an ICS quirk, and not something I've done?

Thanks

Hi,

Whenever you install a new ROM/kernel etc. the dalvik and cache are cleaned to accommodate the new software.
This should not happen after EVERY reboot.
The "clean" dalvik and cache can be found in the recovery .

I'm sorry,but I do not know about the "missing messages tab"

If you are thinking about returning to GB,you will have to downgrade your firmware to hboot 1.17.
If I were you,give ICS a week's trial before you decide.
It grew on me...

Originally Posted by malybru

Hi,

Whenever you install a new ROM/kernel etc. the dalvik and cache are cleaned to accommodate the new software.
This should not happen after EVERY reboot.
The "clean" dalvik and cache can be found in the recovery .

I'm sorry,but I do not know about the "missing messages tab"

If you are thinking about returning to GB,you will have to downgrade your firmware to hboot 1.17.
If I were you,give ICS a week's trial before you decide.
It grew on me...

Well, I'm getting the message after every reboot, that's why I'm thinking about resetting and starting out fresh. Might actually also solve another issue I'm having with data usage too. So to clear dalvik (what actually is that?) and cache, I'd have to enter bootloader?

Not going back to GB, going to run stock ICS for a bit, get used to it, then going to try out a custom ROM, maybe Android Revolution to start with.

Originally Posted by CloneboyZA

Well, I'm getting the message after every reboot, that's why I'm thinking about resetting and starting out fresh. Might actually also solve another issue I'm having with data usage too. So to clear dalvik (what actually is that?) and cache, I'd have to enter bootloader?

Not going back to GB, going to run stock ICS for a bit, get used to it, then going to try out a custom ROM, maybe Android Revolution to start with.

Hi,

I can recommend ARHD highly.
Use the SuperWipe zip before you install it.
This will give your phone a clean base on which to install the ROM.

Do not worry about the dalvik and cache.
When you are next in recovery,have a look and you will see them.

While I've never had the stock HTC Sensation ICS ROM, I remember having read on a Dutch technology board about this issue. I don't think you are the only one having the Dalvik Cache initialisation during boot issue.

Sent from my HTC Sensation using XDA

Hmm...

---

Originally Posted by Arie-

You first have to tell us what you actually want to achieve. You say you want "kernel settings" to stick, but to what effort? Is your kernel default CPU frequency not what you'd like it to be? Would you like to change your voltage settings?
The general answer could be that your kernel resets values on boot, you therefore could write a script that is run at boot. This script (according to you) should be added to . I would suggest to don't mess with files already in place but instead of that, save this script in your init.d folder.

I'm basically flashing an update or a new rom, it contains a kernel so it overwrites mine (Faux123's)...I reboot, let it settle then I flash the Faux kernel, clearing the cache+dal before and after and then rebooting...then I set the cpu to 384~1512 (default is 192~1512) and the sdcache is 128(i think) and I change it to 2048, clicking the Apply on Boot as always...but for some reason now, it doesn't want to stick...so on the reboot it goes back to 192~1512 and 128.

In the init.post_boot.sh file it says it like this:

target=`getprop ro.ident`
case "$target" in "Android_Revolution_HD")

In the build.prop it says:

# Tweaks identyfication code (yes it is misspelled, but I don't think it matters with the # in front)
ro.ident=Elegancia_ICS

So, should I change the init.post to Elegancia_ICS? Would this work?

I'm basically trying to make my cpu freqs to stick, as well as my SDcard Cache...which BOTH don't, so I figure it's the same file or something...

Here is the actual file from my dropbox (I ripped it from the kernel): https://dl.dropbox.com/u/54292644/init.post_boot.sh

Something tells me that I only need this portion:

# Tweak IntelliDemand governor by faux123 (kernel must include this governor!)
# Then set back OnDemand as default governor
#echo "intellidemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo "intellidemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor
#echo "10000" > /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate
#chgrp root /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate
#chmod 664 /sys/devices/system/cpu/cpufreq/intellidemand/sampling_rate
#echo "60" > /sys/devices/system/cpu/cpufreq/intellidemand/up_threshold
#echo "ondemand" > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
#echo "ondemand" > /sys/devices/system/cpu/cpu1/cpufreq/scaling_governor

# Enable ZRAM (kernel must support ZRAM feature!)
mkswap /dev/block/zram0
swapon /dev/block/zram0

And I wonder if I can just erase everything else and just leave this alone and I'll be good? Dunno...

Perhaps you or someone else can help me out?

***EDIT: Got it to work, thanks! System Tuner Pro worked...had the friggin tool on my phone all along! Sheesh!

My suggestion: make a script of based on some "example" scripts from eg. the faux123 thread, and save the file in the init.d folder, than it is executed after boot as well. Changing a file you don't know what it does might not be the wisest. I'll attach my example init.d script for the faux kernel.

#!/system/bin/sh
echo intellidemand > /sys/devices/system/cpu/cpu0/cpufreq/scaling_governor
echo 192000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_min_freq
echo 1404000 > /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq
echo 594000 > /sys/devices/system/cpu/cpu0/cpufreq/screen_off_max_freq
echo 1134000 > /sys/devices/system/cpu/cpufreq/intellidemand/two_phase_freq
echo 1404000 > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_active_max_freq
echo 594000 > /sys/devices/system/cpu/cpufreq/intellidemand/lmf_inactive_max_freq
echo 192000 800000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 310500 825000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 384000 825000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 432000 825000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 486000 850000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 540000 850000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 594000 850000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 648000 875000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 702000 875000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 756000 875000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 810000 900000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 864000 900000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 918000 900000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 972000 912500 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1026000 925000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1080000 937500 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1134000 950000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1188000 975000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1242000 1000000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1296000 1025000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1350000 1025000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1404000 1075000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1458000 1100000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1512000 1125000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1566000 1150000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1620000 1175000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1674000 1200000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1728000 1225000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1782000 1250000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo 1836000 1275000 > /sys/devices/system/cpu/cpufreq/vdd_table/vdd_levels
echo  Was run on boot! > /data/Ran_cpu.log

i have a problem with mycrophone, i have warranty but my phone is rooted, i know that is bought from vodafone but i dont know that is neverlocked or blocked in vodafone and i dont know what stock rom had before, i downloaded RUU_Pyramid_HTC_Europe_1.28.401.1_Radio_10.42.9007 .00P_10.11.9007.15_M_release_192608_signed.exe, should i go for this one ?

HTC Sensation Rooting Help

---

Originally Posted by trkaaa

• you mean by Rooting to unlock bootloader using htc dev and not doing S-OFF
• S-OFF is not that hard ,some managed to to the wire trick from the first time , and it can be S-ONed again when needed
• if you only root and not S-OFF ,
  • you will not be able to install firmware ( except for flashing an RUU which is similar or higher )
  • you will only be able to install custom roms that have your existing firmware ,
  • you will not be able to relock bootloader untill you flash an RUU first , otherwise you will get a security warning and the device will not boot until you unlock the bootloader again
• i only posted this reply for you because you want to install Ordroid " i strongly advise against that " , and also AOSP and AOKP until their known bugs are fixed
• All the posts i see is for members having wifi error that sticks , even after they change roms to solve it , they been asking for solutions for the past one or two months , so do your homework first and search XDA for those posts first
• ARHD is going to have a sense 4 near , so better to wait a bit , and only install very well known roms ( ARHD , insert coin )

Oh okay thanks for the info And i'll wait for the HTC Sense 4.0 ARHD Rom, hopefully it will come soon. Any idea roughly how long itl'll take so should I install the Sense 3.6 version now?

So if I root with S-ON can I revert back to stock and relock the bootloader? Will this revalidate my warranty?

Originally Posted by huzaifah29

Oh okay thanks for the info And i'll wait for the HTC Sense 4.0 ARHD Rom, hopefully it will come soon. Any idea roughly how long itl'll take so should I install the Sense 3.6 version now?

So if I root with S-ON can I revert back to stock and relock the bootloader? Will this revalidate my warranty?

Hi,

I would install ARHD 3.6
There is no ETA for a Sense 4.0 ROM

Yes,you can return to re-validate your warranty.