[ROM][ICS][UNLOCKED][ALL MDPI] Helium Light / updated 23-july-14 - Sony Ericsson Xperia Mini, Mini Pro, Xperia Pro, A

TOO MUCH TEXT!
Pictures:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
READ THIS FIRST - THEN DOWNLOAD BELOW.
UNLOCKED BOOTLOADER ONLY!
REMEMBER TO FASTBOOT ERASE SYSTEM/FASTBOOT ERASE USERDATA AFTER INSTALLING KERNEL! (if this makes no sense to you, read the stuff in blue below)
INSTALL HELIUM ROM FIRST, THEN INSTALL DEVICE FILES - failing to do so will result in a black screen after loading CWM (just nap out the battery, reinsert and enter CWM if you forget, then install device files)
For the daring, here you go:
Helium Light ROM - http://www.mediafire.com/download/cib6c62goaq6aa6/helium-light.zip
De-Bloated (Now even smaller!) Helim Light ROM V 1.14 beta - http://www.mediafire.com/download/o2nbydf8a0aco76/helium.v1.14b.zip
COCONUT (LwW) :
Device Files: http://www.mediafire.com/download/ia974mga7u3rl39/helium-coconut-device-files.zip
Kernel: http://www.mediafire.com/download/5vaj2o871hcwks4/coconut-helium-light-v2.img
MANGO (Mini Pro) :
Device Files: http://www.mediafire.com/download/a1f5vsolggs4npj/helium-mango-device-files.zip
Kernel: http://www.mediafire.com/download/wrmbhj9f1wjrdy5/mango-helium-light-v2.img
SATSUMA (Active) :
Device Files: http://www.mediafire.com/download/miy1baois8xxmvm/helium-satsuma-device-files.zip
Kernel: http://www.mediafire.com/download/c265j08x66s03a2/satsuma-helium-light-v2.img
SMULTRON (Mini) :
Device Files: http://www.mediafire.com/download/p6vtvlhfnukkm22/helium-smultron-device-files.zip
Kernel: http://www.mediafire.com/download/d7utcoagzcp8dic/smultron-helium-light-v2.img
This ROM is based on Saqib Nazm's wonderful work, Fluorescent Feather ROM. So most of what´s right with this ROM is his work and thanks to him. : )
The ROM is based on Kappa by kast with batteryfixes added by karandpr.
If anyone wants to use this to build something else upon this, feel free to do so!
If you have no idea how to fastboot erase system/userdata, I made this file for you.
Kernel flasher - http://www.mediafire.com/download/hzn3iqh25g5pxij/Kernel_Flasher.zip
Put this where ever you want (more thanks to karandpr! : ).
Put the kernel image in the IMG folder in Kernel_Flasher. Make sure you only have ONE kernel in the IMG folder. Only put the kernel you wish to flash in the IMG folder. Putting more than one kernel in IMG folder will fail.
Right click on and run Kernel_Flashing_Tool.bat as admin. Hook up your phone. Does not matter if it is in a ROM, in CWM or in fastboot mode. The batch file will do it all.
BUT: This only works if you have the drivers in windows installed for your phone (you do if you have used flashtool to flash other kernels before).
This also makes it easy to flash "back to" a standard kernel later.

---

Reserved for a rainy day.

---

Just in case, also, mods, I have no idea what I'm doing. Please don't ban hammer me for trying to give something back to the community, but rather advice me if I'm doing something wrong or have forgotten something. : P

---

How can?
Verbato said:
IF IT DOESN'T BOOT - DID YOU FASTBOOT ERASE SYSTEM/FASTBOOT ERASE USERDATA?
If you did and it still doesn't want to boot then please report back and I'll make a small change to the ramdisk.
Until there is a Doppler 180, this will be the only kernel with the right layout for this ROM. You could use a regular kernel, but you'd end up with a lot of free space in /system and very little in /data.
Also, minor bug, first time you install the kernel and boot it up wireless won´t work until you reboot. Wireless modules have been added to the ramdisk. But for some reason, the very first time it boots they don´t load. No idea why. Just one of life´s great mysteries I guess. Only happens first time you boot the kernel after installing it.
If you want even more space for installing large programs or even more, insanely many, programs, then I'd recommend you use Mounts2SD. If you download the apk you could even place it in the rom's zipfile inside of /data/app, and it'll be there from first boot! : )
If anyone wants to use this to build something else upon it, feel free!
Click to expand...
Click to collapse
WT19i Lww User : It Doesnt boot.. how can get into cwm if it doesnt boot? already flash coconut kernel, cant get into cwm.. how to erase system on fastboot? can u explain it?

---

blackpaper07 said:
WT19i Lww User : It Doesnt boot.. how can get into cwm if it doesnt boot? already flash coconut kernel, cant get into cwm.. how to erase system on fastboot? can u explain it?
Click to expand...
Click to collapse
So... Do you use Windows or OSX? There are several guides out there on how to install fastboot.
xda explanation
Explanation on how to install fastboot in windows, with pictures and all
The commands you want to run are, simply:
Code:
fastboot erase userdata
Code:
fastboot erase system
And if you have the kernel in the same folder as fastboot you could also install it like this:
Code:
fastboot flash boot helium-coconut.img

---

Verbato said:
So... Do you use Windows or OSX? There are several guides out there on how to install fastboot.
xda explanation
Explanation on how to install fastboot in windows, with pictures and all
The commands you want to run are, simply:
Code:
fastboot erase userdata
Code:
fastboot erase system
And if you have the kernel in the same folder as fastboot you could also install it like this:
Code:
fastboot flash boot helium-coconut.img
Click to expand...
Click to collapse
wow this so complicated.. surely cannot install this rom.. only use windows 8.. anywhere thanks..

---

blackpaper07 said:
wow this so complicated.. surely cannot install this rom.. only use windows 8.. anywhere thanks..
Click to expand...
Click to collapse
Everything you haven't tried before seems complicated. Once you've tried it it isn't so difficult. : )
The last link, with pictures, is really the easiest to use.
Also, it's just a matter of installing a different kernel and your phone is fine again. So no worries. : )

---

Verbato said:
Everything you haven't tried before seems complicated. Once you've tried it it isn't so difficult. : )
The last link, with pictures, is really the easiest to use.
Also, it's just a matter of installing a different kernel and your phone is fine again. So no worries. : )
Click to expand...
Click to collapse
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..

---

blackpaper07 said:
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..
Click to expand...
Click to collapse
No, you have to do that with every kernel that uses a different partition layout scheme for the phone. You have to do the same with the doppler kernel (which is where I was inspired to make this, btw). But yeah, I am the first one to make a ROM dependant on this. Saves you a whole lot of space in /data though! : P

---

blackpaper07 said:
im not worry about my phone.. already try most all rom in this site for my lww.. but only this kernel need to erase data n format on fastboot.. sometimes hard to learn it.. on the screenshot looks cool.. .. but cant use it..
Click to expand...
Click to collapse
you have to do the same with Doppler and CM11 kernels as well, the reason being the partition sizes are modified to give you more space in the /data partition along with the ability to install more apps into the phone's storage rather than on an SD card which you would have to do if using stock partition sizes because you would quickly run out of space on the /data partition after installing only a few apps...
whew! now that's what i call a long sentence! :laugh:

---

nice.
but one thing.
the stock camera is better than cyber-shot (my experience)

---

RaphaelHam said:
nice.
Click to expand...
Click to collapse
Thank you : )
RaphaelHam said:
but one thing.
the stock camera is better than cyber-shot (my experience)
Click to expand...
Click to collapse
You think so? I've always liked cyber-shot better. But maybe you're right. : )

---

i test this rom in my xperia active , whit radeon kernel ,after 2 day everything is good, very fast , just reporting one bug (xperia kybord forc close) i use last version xperia kybord now.
i'm agree whit this frind RaphaelHam stock camera is much more better than cyber-shot.

---

roxandn said:
just reporting one bug (xperia kybord forc close) i use last version xperia kybord now.
Click to expand...
Click to collapse
Thank you! Of course it only works with mini pro (the one I have), it's made for slide-out-keyboard, and since only mini pro has that the "extra files" for that app, they are only added with the mini pro device files. Fixed now though. : )
Sorry for not realising this sooner.
Also, a minor bug no one has mentioned and hopefully not noticed, the installer-script says "installing mini pro device files" in all the roms. Which isn't true. I just copied everything to every "phone", apart from the device files which are unique for every device. This has been fixed as well, just to prevent any panic.
The device files are VERY important. Which is why I've made a rom for each device rather than a simple click-o-rama, which could lead to a simple mistake. Which could lead to a bit of work. : P
So safety first.
I'm thinking about making a "skeleton" out of this ROM and dumping it in developers. It would be nice to have a simple "skeleton-rom" that can be used to build upon. One that only has what is needed in it (a lot of the files in a lot of the roms are full of stuff and things people either don't realise are there - but unnecessary, or just have no clue what are for and unnecessarily leave in there) and is easy for any developer (or trying-out-making-your-own-rom-developer) to make what ever out of. For instance, there is a file called "dop.iso" in most of the roms /system/etc-directory. Get it? "ISO"? It's a CD-file. With a Windows program. Meant to be used in Windows. Not needed for android. Really not. Doesn't take up much space, 1.8Mb, but still. Unnecessary file. And then we have a lot of copies of "toolbox" in /system/bin, called chown, chmod, etc. Which is silly, because most scripts make symlinks to toolbox in /system/bin with those names anyways, so they just take up space, a lot of space! Better still, make symlinks to busybox instead (like I have done). Now I've even edited the ramdisks so /system/xbin is first in path. Means that busybox is found first and any command run in shell uses busybox (like ls, which now gives pretty colours!).
So... in all, there is a lot of space that could be saved. Next thing is finding out of how to save space in /system/lib... Hmmm...
Oh, well. ROMs are updated. I've moved to MediaFire btw. d-h.st didn't want to work properly on upload (the files didn't show up at all!). MediaFire has a nice upload-resume if anything goes wrong. So, MediaFire it is. Also, MediaFire doesn't delete the files if they aren't downloaded by someone within so and so a long time. Also, ramdisks are updated as well. Just a tiny change to path. That's all.

---

Verbato said:
Thank you! Of course it only works with mini pro (the one I have), it's made for slide-out-keyboard, and since only mini pro has that the "extra files" for that app, they are only added with the mini pro device files. Fixed now though. : )
Sorry for not realising this sooner.
Also, a minor bug no one has mentioned and hopefully not noticed, the installer-script says "installing mini pro device files" in all the roms. Which isn't true. I just copied everything to every "phone", apart from the device files which are unique for every device. This has been fixed as well, just to prevent any panic.
The device files are VERY important. Which is why I've made a rom for each device rather than a simple click-o-rama, which could lead to a simple mistake. Which could lead to a bit of work. : P
So safety first.
I'm thinking about making a "skeleton" out of this ROM and dumping it in developers. It would be nice to have a simple "skeleton-rom" that can be used to build upon. One that only has what is needed in it (a lot of the files in a lot of the roms are full of stuff and things people either don't realise are there - but unnecessary, or just have no clue what are for and unnecessarily leave in there) and is easy for any developer (or trying-out-making-your-own-rom-developer) to make what ever out of. For instance, there is a file called "dop.iso" in most of the roms /system/etc-directory. Get it? "ISO"? It's a CD-file. With a Windows program. Meant to be used in Windows. Not needed for android. Really not. Doesn't take up much space, 1.8Mb, but still. Unnecessary file. And then we have a lot of copies of "toolbox" in /system/bin, called chown, chmod, etc. Which is silly, because most scripts make symlinks to toolbox in /system/bin with those names anyways, so they just take up space, a lot of space! Better still, make symlinks to busybox instead (like I have done). Now I've even edited the ramdisks so /system/xbin is first in path. Means that busybox is found first and any command run in shell uses busybox (like ls, which now gives pretty colours!).
So... in all, there is a lot of space that could be saved. Next thing is finding out of how to save space in /system/lib... Hmmm...
Oh, well. ROMs are updated. I've moved to MediaFire btw. d-h.st didn't want to work properly on upload (the files didn't show up at all!). MediaFire has a nice upload-resume if anything goes wrong. So, MediaFire it is. Also, MediaFire doesn't delete the files if they aren't downloaded by someone within so and so a long time. Also, ramdisks are updated as well. Just a tiny change to path. That's all.
Click to expand...
Click to collapse
I had actually seen that ISO file and wondered WTF it was doing inside a ROM, then thought it must be there for a reason and let it be :laugh:
It would actually be great to have a cleaned up skeleton ROM, I'd use it as is (or maybe after deleting a few .APKs from within ) because theoretically, the less clutter the more free resources and the longer the battery life (I hope ) right?

---

rahimali said:
the less clutter the more free resources and the longer the battery life (I hope ) right?
Click to expand...
Click to collapse
The fewer services run at the same time, the less use there is of the CPU and the less battery it uses. Also, you could download CPU Adjuster (free) and undervolt the CPU. On mine I can make it stable at 750 between 134400 to 364800, 875 between 460800 to 768000 (but as always, your mileage may wary). That makes a whole world of difference in lasting time for the battery. What's stable beyond that depends on how lucky you are with your CPU. Trial and error.
Also, CPU Adjuster lets you have different clock speed settings depending on whether your phone is charging, discharging or in a call (or a whole lot of other circumstances, but I only use charging and discharging). So I don't use any higher clock setting than 768kHz when not charging and 1.4MHz when charging.
Sounds technical. Is really easy when you install and use CPU Adjuster.

---

Plz fix xperia keyboard bug for lww
Sent from my WT19i using xda premium

---

Good work @Verbato
dop.iso is for pc companion installation....

---

AFAIK ,you are compiling modified master branch of Kappa.
Before(or after your edits) use .
Code:
git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
This is the battery bug patch of @kast in Kappa 1.7/Lite branch.
Win win for people
Also fork kappa officially and provide the links to source to comply with GPL.
Including the defconfigs you use :angel:

---

karandpr said:
AFAIK ,you are compiling modified master branch of Kappa.
Click to expand...
Click to collapse
I am using whatever git clone git://github.com/KaSt/Kappa is giving me.
karandpr said:
Before(or after your edits) use .
Code:
git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
This is the battery bug patch of @kast in Kappa 1.7/Lite branch.
Click to expand...
Click to collapse
Thank you! That would really help a lot! : )
But... :-/
From a fresh git clone:
Code:
$ git cherry-pick 04516aaab7f7fe0fa248a07f73c051551c68a6e8
error: could not apply 04516aa... I2C Fixes for 100% Battery bug
hint: after resolving the conflicts, mark the corrected paths
hint: with 'git add <paths>' or 'git rm <paths>'
hint: and commit the result with 'git commit'
Any idea why it doesn't work? (AKA "What am I doing wrong?" : P )
karandpr said:
Win win for people
Also fork kappa officially and provide the links to source to comply with GPL.
Including the defconfigs you use :angel:
Click to expand...
Click to collapse
: )
Will do!