If adb works its good news try this:
Keep two adb shell sessions open...
On one keep checking kmsg on another keep checking dmesg...
And when freeze occurs get the dump of the logs and post them here
Btw which headsets are you using? Are u using any mods? Have u configured liveware manager?
Sent from my LT26i using XDA
Ok guys I am really sorry for the issues u guys are facing but I really am not sure where the issue has cropped in...
As far as I understand v01a kernel works well on ALL devices right? Then I will start investigating the patches applied for v02...
Btw v03 kernel is ready... Got some awesome patches in which will give smooth performance... After v03 is released I will start work on investigating issues... I will post test kernels for those who are running into issues...
Sent from my LT26i using XDA
i want to install this kernel but i don't know how FW flash before for don't have the freeze.
So guys what's the perfect solution for don't have the freeze?
thanks in advance!
So you advice to start with a FW with root?I'm on Lebanon generic, prerooted. No issues whatsoever.
Sent from my LT26i using XDA
Guys I'm sorry I read this topic and the recovery one, but about some things I'm quite confused, so I'll repeat what I got and tell me if I'm right or wrong...
TO HAVE ROOT
- I have to install the DooMKernel
- To install the DooMKernel I have to unlock the bootloader
- To unlock the Bootloader the easiest way is to follow what is written in the fist post of "Tutorial] Xperia S Bootloader Unlocking & Relocking"
THEN
- If I want to install a rom the only way is to use the Recovery by DooMLoRD that is based on CWM and compatible with Rom Manager
- There is no other way of doing this.
So, last point, the classic "Root modus operandi" that I had on SGS and SGS II like one click or just flashing a "rooted kernel" via pc utility is not yet avaiable, right?
Thank you very much.
you need the fastboot fileshi doom
sorry for my limited english but i don't understand this step of your installation guide:
"save the kernel.elf in the folder with fastboot binaries (fastboot.exe files)"
Where is this folder?
Thanks
look my previous postyou need the fastboot files
do a google search for "fastboot.zip"
download and extract that
faux123 said:ZRAM (aka CompCache aka RAMZSwap)
ZRAM is an updated version formally known as CompCache and RAMZSwap. It was originally designed for 2.6.38.xx kernels, I have backported to our 2.6.35.xx kernel. ZRAM allows real-time compression of memory objects in RAM thus reducing memory pressure for the Linux kernel and can keep more apps in memory longer (more apps in RAM == better performance, less fetching from slower MMC or SDCard). Compression, however, is not Free. Some CPU cycles are required to do the compress/decompression, so there's a slight penalty for it. The original CompCache / RAMZSwap required a user space binary to control its behavior which adds additional penalty to performance, but the new version ZRAM eliminated the need for a separate dedicated daemon, thus reducing the overhead and increased performance from the old CompCache by 20%. Therefore, with the newer implementation of ZRAM interface, the performance penalty is almost negligible
su
mkswap /dev/block/zram0
swapon /dev/block/zram0
Ok guys I am really sorry for the issues u guys are facing but I really am not sure where the issue has cropped in...
As far as I understand v01a kernel works well on ALL devices right? Then I will start investigating the patches applied for v02...
Btw v03 kernel is ready... Got some awesome patches in which will give smooth performance... After v03 is released I will start work on investigating issues... I will post test kernels for those who are running into issues...
Sent from my LT26i using XDA
fastboot flash boot kernel.elf
fastboot -i 0x0fce flash boot kernel.elf
fastboot flash boot kernel.sin
fastboot -i 0x0fce flash boot kernel.sin
[URL="http://xdaforums.com/showthread.php?t=1557452"][IMG]http://icxperia.com/doomlord/doomkernel-sig.png[/IMG][/URL]
Ok so a weeks testing unless stated otherwise below is what i'd consider heavy use.
1080p youtube videos in browser and youtube app for at least an hr, stability test app for an hr, emu games, phone calls etc with 384/1.5ghz(I won't OC any higher then this sorry)/ondemand/deadline and dalvik cache wiped after flashing.
9002 - Used for 2 days, no issues found with the above tests, 41deg max and Stable.
9003 - Stability test report shows ~6mins @ 36 degrees it rebooted. Unstable.
9004 - Used for over 3 hrs with ondemand/BFQ IO set, no issues found with the above tests, 40 deg stable.
9005 - Used for over 3 hrs, no issues found with the above tests, 40 deg stable.
9006 - Used for over 3 hrs, no issues found with the above tests, 40 deg stable.
9007 - Used for over 3 hrs, no issues found with the above tests, 41 deg stable.
9008 - Spin off for 9003, stability test report shows ~1min @38deg it rebooted. Unstable.
9009 - Used for 2 days, no issues found with the above tests. 41 deg stable.
I was able to break the phone with 9003 and 9008 easily with out even overclocking and I always ran stability test first.
No bootloops experienced.
Doomlord can you make a kernel with all the above commits with out these two (9003) offenders for testing? I'm back to using 9002 happily so i don't believe the gpu overclock is having an effect on stability, definitely not for me.
Free Stability Test app in market if any1 wants to try:
https://play.google.com/store/apps/details?id=com.into.stability&hl=en
Stability test log after 9008 crash attached.
-smc
After a while of testing with 9002 vs v1a vs 9009, 9009 offer the best stability without producing unnecessary heat and worse battery life. To me, GPU oc is really not a good option compares to performance vs battery life in return. Perhaps you can release a kernel with all the above optimization without oc of cpu and gpu? For testing purposes