Related
Hi all,
I need some testers from all available roms for x10. From stock rom and all custom roms.
Cause there are many custom roms available and they don't use all the same recovery, it's heavy-handed to create update.zips who can used by everyone. If I count a few there are:
people with a 2.2 rom without the needed files for applying custom kernel
people with a 2.2 rom with the needed files for applying custom kernel
people with a 2.2 rom and xrecovery
people with a 2.2 rom and freexperiarecovery
and so on.
my aim is it, to have one update.zip, who works for all people, no matter if they have applied a custom kernel before or have this recovery and not those...
but i can't test all roms now, cause this would need time and nerves i haven't.
Because that, i made two update.zips:
First includes:
please test this first and if this works, flash the one with the kernel, that we know if there are problems, if they come from the recovery part or the uncompatibility between rom and kernel
chargemon file whos made for FreeXperiaRecovery
FreeXperiaRecovery
Requirements:
this zip should work on all basebands, but i generally prefer bb 2.0.52 from here with bb patch for 2.2 roms from here
Second includes:
chargemon file whos made for FreeXperiaRecovery and boots custom kernel as default
kernel folder: latest custom kernel (k006) with miniloader and splboot.ko files
FreeXperiaRecovery
wifi modules for 2.2 and 2.3 roms
Kernel k011/k012 changelog:
kernel 2.6.29.6
a lil more free ram
removed UV for 998Mhz (seems to be the cause reboots)
Fix FrameCap (Thank Z)
addded all mtd partitions (Thank Z)
volume fix
compiled with new gcc 4.4.3
changed SLAB alocator to SLOB
enabled swap support
added Tiny RCU
added UV/OC (k012)
added UC (k012.1)
FPS cap removed
fixed iptables
Requirements:
Flash the ftf bundle from the latest Cm 7 release with flashtool
Only for 2.2 roms: Basebandpatch 49 from here
Please test the update.zips on your rom (but make a backup before flashing, that you can restore anything if s.th. goes wrong) and report if it works on your rom, and don't forget to tell which rom you tested on.
before installing, make sure you comply the requirements
installation:
For users who haven't FreeXperiaRecovery yet:
first install FreeXperiaRecovery v02.zip
reboot into recovery
install latest version
now boot up system and enjoy
For users who have FreeXperiaRecovery yet:
install directly latest version
now boot up system and enjoy
Legend:
FX = FreeXperia
FXR = FreeXperiaRecovery
gb = Gingerbread
froyo = froyo
only wrote bin or xbin instead of system/bin or system/xbin
Link for first zip (only FreeXperiaRecovery):
FXR_v051.zip
Link for second zip (FreeXperiaRecovery and custom Kernel as default booted):
2.6.29.6_FX_k011+FXR_v0.0.8.2.zip
2.6.29.6_FX_k012+FXR_v0.0.9.1.zip
2.6.29.6_FX_k012.1+FXR_v0.1.0.0.zip
Install this for using the custom kernel with froyo (Thanks ! tsuyo.kou):
http://forum.xda-developers.com/showthread.php?t=1077437
mirror:
http://www.mediafire.com/freerecovery-kernel
I AM NOT RESPONSABLE IF YOU BREAK YOUR DEVICE OR DROP YOUR COFEE !
Notice:
this WILL BREAK DATA2SD and any enhancements/addon features provide by ur current ROM (thanks to DooMLoRD for the information)
All credits go to zdzihu, jerpelea, Bin4ry, Androxyde and all those involved in the FreeXperia project.
Cheers,
L
Trying it on Trips gingerbread MIUI ROM. I'll report back!
It booted, and OC works (setCPU)! Will try it for a while to test performance and battery.
Alright, the touch and animations is very smooth with this kernel. And WiFi works!
I'll use it for a while and see if it drains much battery.
EDIT: As it seems now it drains hella lot battery. :/ Even though im using the BOOST guide and screen of profile in setCPU. Will calibrate the battery a few times and see if it helps..
a1exander said:
Trying it on Trips gingerbread MIUI ROM. I'll report back!
It booted, and OC works (setCPU)! Will try it for a while to test performance and battery.
Alright, the touch and animations is very smooth with this kernel. And WiFi works!
I'll use it for a while and see if it drains much battery.
Click to expand...
Click to collapse
Is FreeXperiaRecovery working?
Downloading now
Im on J's CM7 v 16a incl k006
I know the kernel is inclu but i try urs and report back
Sent from my X10 using XDA Premium App
9Lukas5 said:
Is FreeXperiaRecovery working?
Click to expand...
Click to collapse
Havent tried, I have to go now. But i'll try it later!
Is it not possible for all dev's to use a standard recovery/chargemon?
I think that would save alot of headache and would probably be easier.
Any thoughts?
MarylandCookie said:
Is it not possible for all dev's to use a standard recovery/chargemon?
I think that would save alot of headache and would probably be easier.
Any thoughts?
Click to expand...
Click to collapse
+1
sent from my Z orignal and modded 2.2 powered c64
MarylandCookie said:
Is it not possible for all dev's to use a standard recovery/chargemon?
I think that would save alot of headache and would probably be easier.
Any thoughts?
Click to expand...
Click to collapse
It is possible, but they don't do. So if my zip works on all roms, you can simply apply your rom how it is described in the rom thread and boot it to be sure the rom works and then flash my zip. If anyone make it that way in future, everyone would have the same recovery and you wouldn't have headache
MarylandCookie said:
Is it not possible for all dev's to use a standard recovery/chargemon?
I think that would save alot of headache and would probably be easier.
Any thoughts?
Click to expand...
Click to collapse
+100000
@OP
please mention that this WILL BREAK DATA2SD and any enhancements/addon features provide by ur current ROM
EDIT:
@OP it would be better if u can create an update.zip to take backup of current recovery and then replace it with FreeXperia recovery... also u can create another "BackToStock" update.zip to remove FreeXperia recovery and then restore original recovery...
@ALL
REQUEST:
please keep reporting ur tests in the following thread....
http://forum.xda-developers.com/showthread.php?t=1018391
i just tested it on wolfbreak 6.1.3. v7 or 6.1 update and its a no go.. i get system forclose and once i wait it freezes system, and broke my xrecovery and also sim card doesn't work nor memory card. so again "HOUSTON" its a "NO GO"
wali01x said:
i just tested it on wolfbreak 6.1.3. v7 or 6.1 update and its a no go.. i get system forclose and once i wait it freezes system, and broke my xrecovery and also sim card doesn't work nor memory card. so again "HOUSTON" its a "NO GO"
Click to expand...
Click to collapse
Can anyone confirm??
same thing here with wolf rom. i'm gonna try trip's gingerbread rom.
edit : i confirm it's not working on wolfbreak rom.
tested on jerpelea's v15 stock, everything works except wifi which just shows error, xrecovery works fine.
no rebooting issues.
I have however been using this all day and battery life is good.
wali01x said:
i just tested it on wolfbreak 6.1.3. v7 or 6.1 update and its a no go.. i get system forclose and once i wait it freezes system, and broke my xrecovery and also sim card doesn't work nor memory card. so again "HOUSTON" its a "NO GO"
Click to expand...
Click to collapse
works fine here... but no bootanimation
use this...
http://forum.xda-developers.com/showthread.php?p=13022717#post13022717
on trip miui gingerbreab rom : stucks on SE logo , now i need to fix the phone with seus.
Same here. Also tried with TripMiui 1.0.4 on froyo too and same tesult.
Sent from my X10i TripNMiUI using XDA App
thor2002ro said:
works fine here... but no bootanimation
use this...
http://forum.xda-developers.com/showthread.php?p=13022717#post13022717
Click to expand...
Click to collapse
thor im gonna give it a shot later on thanks..
just have WLOD while restoring apps with titanium backup on Wolfbreak cm 6.1.3 V061
pd1: bluetooth dont work
ok, s.th. strange happened to me, i flashed the same zip again (i haven't edited the file or moved renamed, nothing) but after that second flashing, my recovery was broken too and i got a lot of fc's like described from many others. Now i wanted to flash freexperiarecovery without kernel to see if the problem is there or by the kernel, but can't get the zip file to work. So, I'm going to sleep now, maybe i can't see anything important at the moment cause i'm so tierd. But thanks for testing it yet on some roms
so it seems like LG Optimus one P500 is supported by Rom manager as it is listed in the clockworkmod website.
so after i rooted the phone, i can install CWM Recovery from rom manager right?
and flash custom ROM through it right?
i want to install milk's cm 7.1 port for p500, its listed in the clockworkmod website.
so yeah it should work right? and will installing that ROM fix the well known touchscreen bug on the optimus one? i mean the inverted axis multitouch bug and the cpu spike when scrolling bug, or do i need to flash something else after that? if yes could u pls link me to it.
and from what im seeing, p500 kernel is flashable through recovery eh? unlike the x8/x10 mini/pro in which we need to use flash tool?
edit: ive noticed the mik's os in clockworkmod website is beta 6.5.5 in which the latest one is 6.5.8 right? so ill just download the latest 6.5.8 from xda and flash it through rom manager?
yes, but first do a backup in cwm recovery, then wipe everything, flash rom , reboot, flash gapps, the flash from here http://forum.xda-developers.com/showthread.php?t=1227682 BFS gbs.v19.2, and you should be fine, the spikes arent fixed yet
but LG fixed it already in it latest gingerbread ROM, why isnt it fixed in cyanogenmod rom yet? proof utube /watch?v=wgV56dLSbEs
edit :
from MikOS thread :
beta6.5.5 (2011-06-27):
kernel: franco's v18 + 2.6.32.42
Wired headset media button fix moved to kernel
Camera: higher defaults exposure
Updated CM sources (RC1 now)
its already using franco? do i still need to flash that goldenleaf thing?
Remember, that our device isn't officially supported by team Cyanogen.
And that kernel is the old one - look at development section - there's and updated one (i suggest latest goldenleaf + mik's 6.5.8 (your release is old too))
alright so now i wanna clear things up, heres the step i should do :
1.root+install busybox
2.install rom manager and from there install CWM Recovery
3.download latest goldleaf/GBS kernel and latest mik's OS 6.5.8
4.in rom manager, make backup, flash mik's os ROM, reboot, flash gapps, reboot, flash GBS kernel, reboot, full wipe everything.
5. voila!
so thats it right? is there anything i missed? and can i use gapps from rom manager (20110828 Universal) ? if i can't could u please link me to the gapps that i shud be installing?
edit:can i flash franco.Kernel.v19.4 instead of the goldleaf kernel, coz it seems in franco kernel the cpu spike and axis inversion is fixed
6 - August - 2011 - v19
Good touchscreen drivers which should have the CPU **** fixed and the axis inversion workaround
Click to expand...
Click to collapse
I have only tried this on FroyoPro (all versions) with LinuxDX & AlfsGDX v05/6/7/8. Please try it with your favourite rom/kernel combination and report the results here!
1: Flash FroyoPro.
2: Flash x8FroyoPro-Alfsv8+AllFixv3.zip.
3: Reboot, no need to flash anything else.
Or for older kernels:
Ok this is really easy...
1: Flash Froyo rom & custom kernel of your choice. (Any order.)
2: If you want to use Alfasamsung's Alfsv05/6/7 Kernel: Flash "x8AlfsKernelAllin1FixV2.zip" in ClockWorkMod.
OR
2: If you want to use Doixanh's LinuxDX Kernel: Flash "x8LDXKernelAllin1FixFroyo.zip" in ClockWorkMod.
3: WiFi works now, press thanks.
This is for Froyo roms only!Please Note: Read everything you can in kernel threads & Flashtool thread/website.
I recommend the capped versions of Alfs kernel however uncapped will score higher in bench mark tests.
I also recommend not using compcache and using swap instead. More info in Enable Swap 4 X8.
You only need to flash one of the fixes attached after flashing your ROM, no other flashing necessary!
Credits: doixanh alfsamsung atis112 B.Jay lrakkarl
Returning To Stock Kernel:
To return to stock kernel with out losing your data & with ClockWorkMod & XRecovery enabled:
(No guarantee!!! Try at your own data's risk! However this now works all the time for me.)
1: Flash "x8lrakkarlsBack2StockKernel4Froyo.zip" in ClockWorkMod. Download Here or Mirror.
2: Flash "E15_Stock_Kernel.ftf" with Flashtool. Download stock kernel Here or Mirror.
3: WiFi, offline charging, USB mount, ClockWorkMod/XRecovery all working properly with stock kernel, click thanks!
Please Note: This has only been tested on FroyoPro v2.3! Any other bugs come up, report them here!
Change-Log/Extras:
UPDATED: 26/Jan/12
Added "x8AlfsKernelAllin1FixV2.zip".
This fixes compcache, sd mounting (not that I personally had a problem before), WiFi for Froyo, USB mount, etc
UPDATED: 16/Jan/12
Removed, renamed and re-uploaded all files as per users requests. (Removed my name from files.)
New fix for Doixanh's LinuxDX Kernel "x8LDXKernelAllin1Fix.zip". USB working now. Nice, stable kernel, with no oc. Please test for other bugs.
"x8CustomKernelWifiFix4Froyo.zip" outdated now but in case any person wishes to download, moved it to post#3.
UPDATED: 14/Jan/12
Lots of guide changes and thread updates. It is now much easier for you to do what you want!
Returning to stock kernel is now (hopefully) quick, easy & bug free.
I have now tried the WiFi fix with LinuxDX & WiFi is working but USB mount is not. Didn't check anything else.
UPDATED: 13/Jan/12
"x8lrakkarlsBack2StockKernel4Froyo.zip"
To return to stock kernel but with ClockWorkMod & XRecovery enabled. Ready to flash another rom.
UPDATED: 12/Jan/12
Added "x8lrakkarlsAlfsKernelAllin1Fix4Froyo.zip" as it seemed to be needed.
Flash this if you are using Alfs Kernel on Froyo. It will fix WiFi, USB & offline charging with just one zip.
UPDATED: 11/Jan/12
"x8lrakkarlsBack2StockKernelWifiFix4FroyoV2.zip"
Should work in XRecovery now.
UPDATED: 11/Jan/12
"x8lrakkarlsBack2StockKernelWifiFix4Froyo.zip"
with vold and chargemon, offline charging & USB works now haha.
Please re-download if you were one of the 3 people who downloaded this fix!!!
You can find a list of kernels (& roms) available for our phone here:
http://forum.xda-developers.com/showthread.php?t=1425240
Okey, I will try nAa kernel with froyo pro if you want but i will wait for rom update. Will be new version for CWM?
Yap, i have tried with Floyo made by racht.
The results are:
Floyo 1.0.0 + nAa Kernel = GSM doesnt work
Floyo 1.0.0 + LinuxDX = Wifi doest work
Floyo 1.0.0 + Alfs Kernel = Everything is okay. Wifi can be turned on. But i have not tried it (no wifi in my house)
gerimis said:
Yap, i have tried with Floyo made by racht.
The results are:
Floyo 1.0.0 + nAa Kernel = GSM doesnt work
Floyo 1.0.0 + LinuxDX = Wifi doest work
Floyo 1.0.0 + Alfs Kernel = Everything is okay. Wifi can be turned on. But i have not tried it (no wifi in my house)
Click to expand...
Click to collapse
and what about wifi on nAa kernel. My GSM works on nAa
// edit Ok, does not work
I installed alfs v6 on your froyo pro v2.2 and...my phone's fliyng!Thanks!!!
yeap, easily the fastest rom i ever used with alf's kernel, it seems stable @806mhz
wait froyo pro2.3
Sent from my E15a using XDA App
Hmmmm when i do 3d performance in antutu i get only 11 fps @ 806 mhz, on other roms i get around 20 at the soldiers, anyone else have this issue?
Sent from my XPERIA X8 using XDA App
after I installed Alfs kernel, and apply the update-rom-chargemon+vold-AlfsKernel.zip, the usb debugging always off in flashtools but i can connect sd card to PC
11/040/2012 13:40:07 - INFO - <- This level is successfully initialized
11/040/2012 13:40:07 - INFO - Flashtool Version 0.6.6 built on 2012-01-08 19:34:23
11/040/2012 13:40:18 - INFO - Device connected with USB debugging off
11/040/2012 13:40:18 - INFO - For 2011 devices line, be sure you are not in MTP mode
11/040/2012 13:40:52 - INFO - Device disconnected
Click to expand...
Click to collapse
is this normal? I can't use flashtools with this
problem solved : reinstall drivers from flashtools 0.6.6.0
FroyoBread 23b work fine with alfs kernel, but phone is heating 39C and battery drain very fast
Update:
Added: "x8lrakkarlsAlfsKernelAllin1Fix4Froyo.zip" as users seemed to be forgetting to flash the vold+chargemon fix after the WiFi fix.
Edit:
Japos
I think you have figured this out already but you also need to flash chargemon+vold update from alfasamsung's thread.
aries77
Glad you could work it out, sometimes it feels better if you can figure it out by yourself.
mikhazloy
Which version of Alfs Kernel? Some people are reporting battery drain on v06...
alfs kernel v6
"x8lrakkarlsBack2StockKernel4Froyo.zip"
To return to stock kernel but with ClockWorkMod & XRecovery enabled. Ready to flash another rom.
so before going back to stock i have to flash this?
Yes it would be a good idea!
It is much more dependable than:
"x8lrakkarlsBack2StockKernelWifiFix4FroyoV2.zip" method.
as sometimes (I need more testers) when flashing stock kernel first, CWM/XRec cannot be accessed & all apps force close after rom boots. The only way to fix if this happens is to start from stock rom again or reflash alfs & install a custom rom that is compatible with alfs.
Sorry if this is confusing, the bug is confusing too as I can't work out why sometimes flashing the stock kernel first works fine and other times it doesn't.
(That and I am too busy enjoying FP2.3 with Alfs & making more fixes for other kernels )
In short: You definitely will be able to access CWM/XRec if flashing "x8lrakkarlsBack2StockKernel4Froyo.zip" before flashing stock kernel. It also includes the wifi fix for stock kernel.
thanks for fast respond
lrakkarl said:
Yes it would be a good idea!
It is much more dependable than:
"x8lrakkarlsBack2StockKernelWifiFix4FroyoV2.zip" method.
as sometimes (I need more testers) when flashing stock kernel first, CWM/XRec cannot be accessed & all apps force close after rom boots. The only way to fix if this happens is to start from stock rom again or reflash alfs & install a custom rom that is compatible with alfs.
Sorry if this is confusing, the bug is confusing too as I can't work out why sometimes flashing the stock kernel first works fine and other times it doesn't.
(That and I am too busy enjoying FP2.3 with Alfs & making more fixes for other kernels )
In short: You definitely will be able to access CWM/XRec if flashing "x8lrakkarlsBack2StockKernel4Froyo.zip" before flashing stock kernel. It also includes the wifi fix for stock kernel.
Click to expand...
Click to collapse
Confirmed!..
install "x8lrakkarlsBack2StockKernelWifiFix4FroyoV2.zip" > flash stock kernel > working cwm/xrec..
and cwm/xrec cannot be accessed if "x8lrakkarlsBack2StockKernelWifiFix4FroyoV2.zip" is installed after flashing stock kernel..
btw.. can u please rename the fix .zip file with the shorten file name..
Thank you for testing!
I have now made many thread updates as well as Allin1 fix for LinuxDX.
See change-log for more info & please test LinuxDX with Allin1fix!
Has anyone tried it on froyobread?
This is Rage Kernel v2.9 for Xperia Mini / Mini Pro / Active / Live recompiled to run on FXP CM7.2.0 ROM from Freexperia Project here.
The boot image consists of kernel compiled from DuMOHsmol's Rage Kernel v2.9 source, FXP wi-fi driver and FXP ramdisk. It is tested running in FXP122 CM7.
The kernel is compiled using FXP default config, modified to enabled added features in Rage Kernel, so overall the features is similar to Rage Kernel v2.9 (see post #2 below)
Credits:
Many thanks to DuMOHsmol for Rage kernel source and DoomLord for providing the base/stock source.
Thanks for Freexperia Team for making such a great rom.
Thanks for wucinac, HUdasp, gandhar, Snoopo, & jakobxxl for initial testing and feedbacks.
This kernel will not be updated everyweek like FXP rom releases. It would only be updated if there's update in Rage Kernel or there's update in FXP ramdisk/ROM that requires changes in this kernel too.
I mainly compiled this kernel because it gives good battery life, so I haven't tested all features that Rage Kernel offer. Therefore I can't really confirm that those added features will work fine in CM7. What does work is the basic functionalities (like calls, wifi, bluetooth, camera, etc) and added cpu governors, overclocking options, and added i/o schedulers. What I haven't test: zram and swap.
And because I personally considered this kernel as some kind of a workaround for the battery drain issue in fxp kernel (see post #3 below), then if FXP team has fixed it, this kernel might be no longer needed.
As of version 2.6, changes from original Rage Kernel source are below:
4 files in Rage source replaced with files from FXP source :
- arch/arm/mach-msm/board-semc_mogami.c
- arch/arm/mach-msm/sdio_ctl.c
- drivers/mfd/marimba-codec.c
- drivers/misc/lm356x.c
Files sdio_ctl.c and marimba-codec.c is replaced to avoid compiling errors when using fxp defconfig. The file board-semc_mogami.c is replaced to fix touchscreen problem when using original file. File lm36x.c is replaced to fix force close problem in Torch app.
Another change is patch from here applied to fix the touchscreen issue.
Changes in version 2.7 are included as a patch files in the download post below.
Changes in version 2.8 & 2.9 are related only to cpufreq driver & cpu governors, so the patch from 2.7 can still be used, but the cpufreq part of the diff must be removed.
Version 2.7 / 2.8 / 2.9:
Please see all download links for Mini/Mini Pro/Active/LiveWithWalkman in this #75 post.
Flashing disclaimer applies! Use this kernel at your own risk.
How to use:
1. For the first time CM7 users: Flash the Freexperia CM7 kernel & Rom first, and make sure everything works fine, and then continue to step 2. For those that already have CM7 running, just begin at step 2.
2. Flash this kernel using fastboot.
3. Reboot to CWM and wipe cache
4. Reboot again.
Notes :
- This kernel is not supported in anyway by FXP team or original Rage maintainer DuMOHsmol. Anyone having problem, please don't ask them for support. Just ask in this thread & I'll try to figure it out.
- Battery life is not solely affected by the kernel. It can also be affected by apps/mods/tweaks used or applied in the rom. If battery drain is high, then please check what cause the wakelocks using apps like BetterBatteryStats here
- There are instances that using Google Maps or Latitude (or maybe other gps-related apps) would cause GpsLocationProvider keeping the phone awake, like the case in this post #82 and post #34. This situation can be diagnosed using that BetterBatteryStats app mentioned above. The workaround is to disable gps and reboot the phone.
- Of course, other than advantages, there are also disadvantages using this kernel in FXP cm7. Advantages including: a bit better battery life, more cpu governors, more i/o schedulers, etc. Disadvantages: I perceive sdcard i/o is somewhat slower, sometimes there's lag in video recorder, there might be broken features in future FXP releases, not supported by FXP team, and there might be other problems that haven't been encountered yet. If anyone experiencing more disadvantages than advantages using this kernel, then please consider using FXP kernel instead.
Features (quoted directly from DuMOHsmol's Rage Kernel original post here ) :
DuMOHsmol said:
This is my kernel, it's based on stock SE 4.0.2.A.0.74 kernel sources, with some things from DoomKernel by DooMLoRD (so go and say thanks to him, and other developers too).
It has:
- Overclock up to 2Ghz
- CWM Recovery 5.0.2.7
- Prerooting
- CPU Governors:
brazilianwax
smoothass
smartassV2
SavagedZen
interactiveX
lagfree
minmax
Scary
smartass
interactive
conservative
userspace
powersave
ondemand
perfomance
v2 added:
- Xperia Mini support
- Tun/tap interface enabled (VPN, ipv6)
- Swap support enabled
- Two way call recording support added
- I/O schedulers:
noop
anticipatory
deadline
cfq
bfq
vr
sio
v2.1 changed:
- disabled NFS and CIFS (battery drain fix from DoomKernel), let's see if it can really increase battery life.
v2.2 changed:
- moved to from 4.0.2.A.0.58 to 62 source, though I didn't see any changes
- added 0% battery workaround patch by Bazoocaze. I don't even know what it does but it seems to be something useful since everyone includes this in their kernels
- New cpufreq driver from DoomKernel. You can experience some problems with overclocking now (my phone becomes unstable at 1.8GHz now, instead of 2.0), but phone eats much less battery in sleep. I've also changed 1018Hz to 1024Hz and 249Hz to 245Hz because those new numbers looked wierd
v2.3 changed:
- moved back to 4.0.2.A.0.58 source (just to make sure that everything will work).
- updated version number in ramdisks to 62.
- removed 0% battery workaround patch (it's useless on our devices).
- reverted old cpufreq driver with small fix. It should be stable now and phone seems to eat less battery than in 2.1. (thanks himasura for lots of testing)
- salvaged some ram.
- enabled NTFS support.
- enabled usb-storage driver, so you don't need to manually load usb-storage.ko now.
- Version number now shows version of kernel (#23=2.3).
v2.4 changed:
- Now phone lights up blue led to show when you can enter recovery (thx to DooMLoRD).
- Minor changes in ramdisks.
- Enabled hid drivers for microsoft and a4tech.
v2.5 changed:
- Re-added CIFS
- Enabled ext4 support
- Added zram and cleancache drivers
- Added lulzactive governor
- Root fs now mounts as rw after boot.
v2.6 changed:
- removed lulzactive governor as it wasn't working properly (thx to kamarush and others for pointing that)
v2.7 changed:
- moved to sony 4.0.2.A.0.74 kernel sources (updated touchscreen driver)
- Increased GPU dedicated memory to 4MB
- Updated su binary in autoroot.
v2.8 changed:
- added new cpufreq driver at last (with CPU frequency fixup by DooMLoRD), battery drain is lower now. I left version 2.7 too for those who want higher overclock or have some problems with 2.8.
Everything else is similar to stock kernel for now.
Click to expand...
Click to collapse
A bit background:
I use FXP CM7 rom for my mini pro since release 049 and like it very much. One thing that made me keep switching back to stock rom was the high battery drain, because in my daily activities electric plug is not always readily available, so battery life is critical for me.
In fxp 052 I got a bit desperate and trying to use custom kernel based on stock from bbooff here, with fxp rom. The battery life is excellent, just like stock rom, but I encountered 2 problems: touchscreen sometimes become unresponsive and wifi was not working (even if I replaced wifi modules with stock).
Finally, I decide to learn how to compile android kernel, and I found that it is quite similar with compiling linux kernel, which I've frequently done to my computer and laptop.
So, I compiled kernels from 3 sources and compare the battery life in my mini pro. They are from DoomLord's official SE source, DuMOHsmol's Rage kernel source, and krizky82's X Kernel source. I also recompiled kernel from FXP kernel source using stock semc_mango_defconfig, to see if battery life is better. The conclusion is that best battery life is achieved using stock and Rage Kernel, and I've been using FXP with rage kernel since release 102 and haven't considered going back to stock rom again.
I posted in Rage Kernel thread to thank DuMOHsmol, and since then there's 3 xda members that ask me to share this kernel, so I make this thread.
I hope this could help those who want to use FXP CM7 and need a battery life that's close to what stock rom offer.
Note:
As of release 114/115, FXP kernel also has better power management and quite a good battery life. The power consumption difference between this rage kernel and fxp kernel is not as much as it used to be before. In case of broken features or any problem caused by using this kernel in FXP cm7 rom, then please consider using FXP kernel instead.
hi ,after flash your kernel ,my device have a boot-loop,please check it ,thank you
zhanglz0904 said:
hi ,after flash your kernel ,my device have a boot-loop,please check it ,thank you
Click to expand...
Click to collapse
Okay, I'll check it. I might zip the wrong file. What is your device? I assume it is mini / st15? Because kernel for mini pro works fine in my mango. I'll check and if needed I will re-compile it.
Edit:
I think the problem was I incidentally used wrong ramdisk for mini kernel.
I have made a new kernel for mini, but it needs testing first. So, if anyone's willing to test it, please send me a PM. Thank you...
Edit:
Fixed. Link for mini updated.
Thank you!!
Im using cyanogen fxp 111
Only need flash the kernel?
Or need make a full wipe?
edwarddd said:
Thank you!!
Im using cyanogen fxp 111
Only need flash the kernel?
Or need make a full wipe?
Click to expand...
Click to collapse
You are using mini pro, right? I'm still fixing kernel for mini.
You don't need to do a full wipe, just wipe the cache partition.
Yes im using the mini pro
Thanks!
thanks a lot.even i was switching back to stock because of the battery drain ..will try this on my mini pro today
i am using fxp111 on my st15i,thank you for your great work .
zhanglz0904 said:
i am using fxp111 on my st15i,thank you for your great work .
Click to expand...
Click to collapse
Mini kernel is fixed. Link is updated. Please test it and let me know if you encounter any more problem. Thank you for your feedback...
greenAlgae said:
Mini kernel is fixed. Link is updated. Please test it and let me know if you encounter any more problem. Thank you for your feedback...
Click to expand...
Click to collapse
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
by the way ,some of us using the rage kernel have encountered the same problem,they aslo "complained" the boot-loop ,so i think the problem is kernel itself not the the ramdisk ,i am very happy if you will fix it ,thank you much .respected your work
zhanglz0904 said:
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
Click to expand...
Click to collapse
what is the problem?
im install fixed kernel and everithing working.
no bootlop or error during boot.
zhanglz0904 said:
hi ,greenAlgae ,i am sorry to tell that i encountered the same problems with using your fixed kernel ,it may not the ramdisk,but the drivers,i think .
by the way ,some of us using the rage kernel have encountered the same problem,they aslo "complained" the boot-loop ,so i think the problem is kernel itself not the the ramdisk ,i am very happy if you will fix it ,thank you much .respected your work
Click to expand...
Click to collapse
Is there any error when you flash it using fastboot? Did you get to boot logo only or you get to cyanogen boot animation when the phone bootloop?
wucinac said:
what is the problem?
im install fixed kernel and everithing working.
no bootlop or error during boot.
Click to expand...
Click to collapse
Thank you wucinac. It seems there's some kind of inconsistencies here. Hopefully it can be worked out, else i would have to pull out the kernel for mini altogether.
Sent from my SK17i using XDA
For st15i i have to use fastboot query with flag:
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
P.S. Rage flash'ed without any problems. Kudos to developer, many thanks for merging battery save and direct call record!
oh great! Let's test!
gqcJYb3UN8xSIWNUy2xX said:
For st15i i have to use fastboot query with flag:
Code:
fastboot -i 0xfce flash boot boot.img
fastboot -i 0xfce reboot
P.S. Rage flash'ed without any problems. Kudos to developer, many thanks for merging battery save and direct call record!
Click to expand...
Click to collapse
So, it does work for mini after all, right?
All credits goes to original devs. It was DuMOHsmol who added the features, so your kudos goes to him
Snoopo said:
oh great! Let's test!
Click to expand...
Click to collapse
Yes sir, please test it and kindly let me know how it goes . Any feedbacks - even negative ones - will be much appreciated
Sent from my SK17i using XDA
So long time ago i using stock rom, and rage kernel are the best, i think that are the best kernel
For stock neves restart the phone on overclock , i dont back to stock rom never thanks!!
Sorry for my bad inglish
edwarddd said:
So long time ago i using stock rom, and rage kernel are the best, i think that are the best kernel
For stock neves restart the phone on overclock , i dont back to stock rom never thanks!!
Sorry for my bad inglish
Click to expand...
Click to collapse
Well, overclocking is the feature that I very rarely use. Because I use this kernel for better battery life, and overclocking might just negated that
But I'm glad that it works for you
Sent from my SK17i using XDA
greenAlgae said:
A bit background:
I use FXP CM7 rom for my mini pro since release 049 and like it very much. One thing that made me keep switching back to stock rom was the high battery drain, because in my daily activities electric plug is not always readily available, so battery life is critical for me.
In fxp 052 I got a bit desperate and trying to use custom kernel based on stock from bbooff here, with fxp rom. The battery life is excellent, just like stock rom, but I encountered 2 problems: touchscreen sometimes become unresponsive and wifi was not working (even if I replaced wifi modules with stock).
Finally, I decide to learn how to compile android kernel, and I found that it is quite similar with compiling linux kernel, which I've frequently done to my computer and laptop.
So, I compiled kernels from 3 sources and compare the battery life in my mini pro. They are from DoomLord's official SE source, DuMOHsmol's Rage kernel source, and krizky82's X Kernel source. I also recompiled kernel from FXP kernel source using stock semc_mango_defconfig, to see if battery life is better. The conclusion is that best battery life is achieved using stock and Rage Kernel, and I've been using FXP with rage kernel since release 102 and haven't considered going back to stock rom again.
I posted in Rage Kernel thread to thank DuMOHsmol, and since then there's 3 xda members that ask me to share this kernel, so I make this thread.
I hope this could help those who want to use FXP CM7 and need a battery life that's close to what stock rom offer.
Click to expand...
Click to collapse
I have installed your kernel on my sk17i .. with FXP 111, but overclocking is set to 1024?
Continue only if you have read http://forum.xda-developers.com/showthread.php?t=1801191 and confirm that you have:
1)Unlocked Bootloader
2)Rooted phone
3)CWM installed
4)Have a nandroid backup of your current ROM
5)Have a titanium backup
6)Have a backup of your SD card
A HUGE THANKS TO FXP TEAM FOR MAKING A WONDERFUL ROM !!
CHANGELOG
http://code.google.com/p/freexperia/
Step 1: DOWNLOADS
1)the original thread ( http://forum.xda-developers.com/showthread.php?t=1205141 (thanks fxp!!) )
download http://uploaded.net/file/v9l8usb9/from/odeyra OR http://depositfiles.com/files/4g5uaxpoz
put it on sd card in a new folder, say cm9 and remember the location
2)I'll be giving updates when new versions are released , please check for it on weekends(mostly sundays)
please note that i dont own the zip files and that they are created by the fxp team
for changelogs see this - http://code.google.com/p/freexperia/
3)Download gapps (google apps, remember, they're ics), they're the google apps including face unlock
http://goo.im/gapps/gapps-ics-20120429-signed.zip
put it on sd card in cm9 folder
4)check baseband in about phone,if the last 2 digits are 72, skip this step and the next and go to step 3
if they are not 72,download http://uploaded.net/file/zxqy01dj/from/um2ivw or http://fiberupload.com/j6yudfu5e8za/MT11i_4.1.B.0.431_BB72.ftf
Step 2: FLASHING BASEBAND
1)put the downloaded .ftf file in C:\Flashtool\firmwares
2)connect phone in MSC (mass storage mode) mode
3)start flashtool
4)click on lightning icon on top left.
5)flashmode>ok
6)select firmware> MT11i(device)> 4.1.B.0.431(version)>BB72(branding)
7)press ok and follow the onscreen instructions
8)phone will reboot and now you should be on 72 baseband
how to check? > settings>about phone>baseband version> last 2 digits should be 72
You're now on .72 baseband!!
THIS STEP ONWARDS, YOU'LL NOT BE ABLE TO SEE YOUR SONY OFFICIAL ICS ROM SO PLEASE SAVE/BACKUP YOUR IMPORTANT WORK.
MAKE SURE THAT YOU HAVE 130mb ROM AND GAPPS.ZIP ON SD CARD AND CHARGE YOUR BATTERY TILL 50%
Step 3: FLASHING CUSTOM ( CM9 ) KERNEL
What's a kernel? go here http://www.androidcentral.com/android-z-what-kernel
1)open FXP214-UNOFFICIAL-haida.zip (downloded before) using winRAR and extract a file called "boot.img" to a known location on your COMPUTER say folder "kernel" on desktop.
2)Connect phone in MSC (mass storage mode) mode
3)open flashtool and click on lightning icon
4)select FASTBOOT MODE and click on button"reboot to fastboot mode(via adb) (buh bye sony !! )
5)wait till your notification light goes blue
6)select "SELECT KERNEL TO FLASH"
7)locate to the boot.img file
8)click ok and poof!! new kernel is flashed !!
9)Disconnect phone and DONT turn it on
Step 4: INSTALLING CM9 ROM BY FXP
1)Turn on phone and when you see the free_xperia_team logo, repeatedly press the vol down button till you enter cwm
navigation in cwm-
go up-vol up
go down-vol down
select option-home button
previous menu-back button
2)select wipe data/factory reset>yes
3)select wipe cache partition>yes
4)select advanced>wipe dalvik cache>yes
5)go back to main menu and select install zip from sd card>choose zip>navigate to the folder where you put the 130mb zip file(ROM) and gapps zip>select FXP214-UNOFFICIAL-haida.zip>yes
6)wait for it to install
7)once installed, select install zip from sd card>choose zip>navigate to the folder where you put the 130mb zip file(ROM) and gapps zip>select gapps.zip>yes
8)once both are installed, return back to the main menu and select first option - reboot system
9)wait for system to boot, first will take some time say 5 minutes
10):good: WELCOME TO CM9 :good:
11)set up the phone and install titanium backup and restore your apps!!
12)enjoy the power of cm9!!
Step 5: NANDROID BACKUP
once you've settled with cm9(restored your apps with titanium) and everything seems normal,
1)go to cwm
2)select backup and restore>backup
3)your phone will be backed up within 20 minutes or less
4)once finished, reboot phone
your backup will be stored in "SD card/clockworkmod/backup/<date_and_time_of backup>"
please rename it for convenience say "fxp 214 cm9 (new)"
HOW TO RESTORE?
1)enter cwm
2)select backup and restore>restore>select folder name( eg: fxp 214 cm9 (new) )
3)this will usually take less time than backup
4)reboot phone to the same state at which it was backed up
THIS DOES NOT CHANGE THE KERNEL
to change kernels, you need to do it via flashtool or fastboot mode
fastboot mode?
while phone is in power off state, open USB cover , connect USB to pc but not to phone , press and hold menu button , connect USB to phone and the notification light should go blue , you can now leave the menu button you are now in fastboot mode.
to change kernel while in fastboot mode, open flashtool, click lightning icon>fastboot mode>ok>select kernel to flash>ok>bazinga!!!
UPGRADING?
Are you on a fxp ROM and wanna upgrade to a higher version?
no worries bro!
1)Download the ROM
2)Put it on your SD card
3)For safety just backup your current ROM if anything goes wrong !!
4)Flash the kernel that is in the zip file. For instructions, refer ^ step 3
5)Enter recovery the way you normally do it(down button.)
6)Wipe cache partition and wipe dalvik cache ONLY!!
7)Install zip from SD card
8)Wait.......
9)When done, go to advanced, wipe battery stats for calibrating battery, reboot system
10)Wait....
Yippeeee... ROM upgraded, data safe and same, like a boss B)
GREAT THANKS TO FXP TEAM :highfive:
WANNA TRY MORE ROMS? http://forum.xda-developers.com/showthread.php?t=1313445
IF I HAVE DONE A MISTAKE, PLEASE CORRECT ME BY REPLYING
IF YOU SCREW UP YOUR PHONE, AND ARE TOTALLY HOPELESS, GET THIS
http://www.sonymobile.com/gb/tools/update-service/
OR
just leave a reply
IF I HAVE HELPED YOU ANY WAY, PLEASE DONT HESITATE TO CLICK THE THANKS BUTTON
First of all the title should be changed from ROM to GUIDE
and it should be in general section, not in dev section
Sent from my Xperia neo V
Mate...there are enough tutorials here...and now that neoV too is officially supported by cm...the hassle of editing scripts and applying patches has also gone...and fxp themselves have given enough instructions to flash cm9...and as far as rooting and unlocking is concerned...there are guides for them too.
I wont downshow ur effort...nor will dishearten you...thanks for the effort bro...but actually it is not needed.
Sent from my Xperia Neo V
Thanks for the guide, but what is MTP mode?
Haluki_BR said:
Thanks for the guide, but what is MTP mode?
Click to expand...
Click to collapse
okay now if you're on stock rom (official sony ics), you'll find usb settings and then connect your phone, there'll be 2 modes, MTP is the one in which you can view your sd card on pc named as removable disk
geekynoob said:
Edit-Just saw ur an Indian... i feel lyk banging my head on the wall...
God save me plsss...
Cheers.!
Click to expand...
Click to collapse
the_neo_v_guy said:
why?
Click to expand...
Click to collapse
@the_neo_v_guy - Bro don't bother bout that geeky noob he has an ol habit of digging into useless things !! You are doing a great job ... I appreciate your efforts bro
livesourav said:
@the_neo_v_guy - Bro don't bother bout that geeky noob he has an ol habit of digging into useless things !! You are doing a great job ... I appreciate your efforts bro
Click to expand...
Click to collapse
thanks a lot livesourav
at least some people know how to appreciate
thanks for this guide buddy, it did help me installing cm9!
iamdchosen1 said:
thanks for this guide buddy, it did help me installing cm9!
Click to expand...
Click to collapse
my pleasure
calm down people, I have cleaned a bit and moved this thread to general section
Yes, it IS NECESSARY!
unisol107 said:
Mate...there are enough tutorials here...and now that neoV too is officially supported by cm...the hassle of editing scripts and applying patches has also gone...and fxp themselves have given enough instructions to flash cm9...and as far as rooting and unlocking is concerned...there are guides for them too.
I wont downshow ur effort...nor will dishearten you...thanks for the effort bro...but actually it is not needed.
Click to expand...
Click to collapse
To unisol107 and Aarush: Sorry to disagree with you, but this kind of tutorial is indeed necessary for noobs like me. It's hard to do all these procedures in the correct way and in the correct order by reading dozens of different threads and sites; it is hard to find out what kernel is compatible with this or that rom, what rom is bug-free, what kernel is bug-free, and many, many other important things like that. And many other tutorials are filled with a plethora of abbreviations that are way beyond my knowledge - only to list few obstacles!
The forum's moderators should, indeed, give congratulations to the_neo_v_guy for his effort, and even help him to improve some litle things to make this tutorial even better than it already is! (Some sort of a better text formating and layout fine-tunning would be nice, if possible).
Stick this toppic, by the way! And help the author to mantain it up to date!
(And sorry for my bad English)
(To the_neo_v_guy: Congratulations, man! Keep going on your good work of helping completely noob people like me!
nice job!!! very helpful for noobs!! keep it up!
Some
I have some more questions...
My Xperia Neo V is a MT11i one (originally bought as a MT11a, but I change it to prevent some game incompatibility issues). These are its configurations:
- Stock ICS v 4.0.4 (version 4.1.B.0.431);
- Baseband with 72 in its last two digits;
- Kernel 2.6.32.9-perf [email protected]#9 (for 1.4 ghz overclock capabilities).
I am thinking about installing CianogenMod, but as I said before, I am a noob, and I don't have enough time (nor ninja discipline...) to read all 220 pages of this toppic: http://forum.xda-developers.com/showthread.php?t=1445844&page=220
So, I need help to find answers to these questions:
1 - Does FXP kernells allow overclock?
2 - Do I need to use only FXP kernells under CianogemMod roms, or can I use other Kernels?
3 - Are FXP132 versions of CM10 completely bug-free and fully operational in Xperia Neo V?
4 - If not, what is the newest version of Cianogen rom that is bug-free and fully operational for my Xperia Neo V, and what kernell can I use with it for best performance/overclock and/or battery-friendly use?
Thanks in advance, and sorry for my bad English.
piduca2011 said:
I have some more questions...
My Xperia Neo V is a MT11i one (originally bought as a MT11a, but I change it to prevent some game incompatibility issues). These are its configurations:
- Stock ICS v 4.0.4 (version 4.1.B.0.431);
- Baseband with 72 in its last two digits;
- Kernel 2.6.32.9-perf [email protected]#9 (for 1.4 ghz overclock capabilities).
I am thinking about installing CianogenMod, but as I said before, I am a noob, and I don't have enough time (nor ninja discipline...) to read all 220 pages of this toppic: http://forum.xda-developers.com/showthread.php?t=1445844&page=220
So, I need help to find answers to these questions:
1 - Does FXP kernells allow overclock?
2 - Do I need to use only FXP kernells under CianogemMod roms, or can I use other Kernels?
3 - Are FXP132 versions of CM10 completely bug-free and fully operational in Xperia Neo V?
4 - If not, what is the newest version of Cianogen rom that is bug-free and fully operational for my Xperia Neo V, and what kernell can I use with it for best performance/overclock and/or battery-friendly use?
Thanks in advance, and sorry for my bad English.
Click to expand...
Click to collapse
1 ..yes they do..
2.. fxp or cm9 kernels only..
3.. no..not at all completely bug free!
4. CM7 is the stable release so far.. use kernel here http://forum.xda-developers.com/showthread.php?t=1566871
TheDarkDefender said:
4. CM7 is the stable release so far.. use kernel here http://forum.xda-developers.com/showthread.php?t=1566871
Click to expand...
Click to collapse
CM7 Is on gingerbread and yea its stable and that kernel works only for cm7 not for cm9 :good:
cm9 is currently on RC2(release candidate) and i didnt find any bugs out there
the_neo_v_guy said:
CM7 Is on gingerbread and yea its stable and that kernel works only for cm7 not for cm9 :good:
cm9 is currently on RC2(release candidate) and i didnt find any bugs out there
Click to expand...
Click to collapse
dude! that kernel works for cm9 as well.. IM USING IT!! what kernel are u using for cm9?
TheDarkDefender said:
dude! that kernel works for cm9 as well.. IM USING IT!! what kernel are u using for cm9?
Click to expand...
Click to collapse
i think there may be a problem with my device, im using the kernel which came in the zip file
the_neo_v_guy said:
i think there may be a problem with my device, im using the kernel which came in the zip file
Click to expand...
Click to collapse
Ok .. i tried that too .. both worked fine!
Sent from my Neo V
TheDarkDefender said:
Ok .. i tried that too .. both worked fine!
Sent from my Neo V
Click to expand...
Click to collapse
:good:
Thanks for the detail info.
Thanx for the guide. Much Appreciated:good: