yashsingh1/xdaforums huggingface dataset:
[Samsung Captivate Glide] lambgx02:
Well, you have to grab the Android tree using git, then apply the Samsung "patches" on top of the tree, patch the bluetooth stuff, then build. It's... involved. But start here:

Initialize a Build Environment | Android Open Source

.. and grab the Samsung code from the SOSRC:

Samsung Open Source Release Center

My patch would probably apply cleanly, but I'm not familiar with the Note at all. If you give it a shot, good luck! :good:
[Samsung Captivate Glide] chappatti:
Thanks !!! Will try......
[Samsung Captivate Glide] beybus:
Is it possible to make fix with 128 bitpool?
[Samsung Captivate Glide] lambgx02:
Nope; the a2dp specification limits it to 64.
[Samsung Captivate Glide] beybus:
How to flash this? Im trying in cwm (zip from card) and gettin error, installation aborted.

I also tried to replace this file in root explorer but after reboot I cant check bitpool - error (broken pipe, lol)
[Samsung Captivate Glide] lambgx02:
Are you trying to install on a Captivate Glide running the ICS build?
[Samsung Captivate Glide] beybus:
Aww, I now realized that mod is for Glide only.

Is it possible to make smthn like this but for i9000?
[Samsung Captivate Glide] lambgx02:
It may be, but unfortunately I don't have one.
[Samsung Captivate Glide] rogernizzLe:
When the bluetooth bug in CM10 gets squished, will this be compatible with the ROM as is?
[Samsung Captivate Glide] cn2661:
WOW Oh my mama, incredible. Finally solved this pain in Ar*e.

Bluetooth sound is no longer crappy. Cheers mate.
[Samsung Captivate Glide] marascool:
Is there any chance, that this patch will work on LG Swift L5, Android 4.0.3?

I also suffer because of poor audio quality over BH-504 stereo bluetooth.
[Galaxy S III Q&A, Help & Troubleshooting] mohnim:
I want to unlock my gs3 which is locked onto the UK 3 network, what is the best way I can unlock it without taking it to a mobile shop????
[Galaxy S III Q&A, Help & Troubleshooting] kdogguk:
http://xdaforums.com/showthread.php?t=1846451

Search button is your friend ;)
[Galaxy S III Q&A, Help & Troubleshooting] AMoosa:
Although the 3 handsets are branded ROMs, I don't think they are locked onto the 3 network.
[Galaxy S III Q&A, Help & Troubleshooting] InevitableDJ:
Even if it is locked to three if you got it on a contract after 30 days you can request for an unlock which I did and now my phone is unlocked to all networks
[Galaxy S III Q&A, Help & Troubleshooting] biffroy:
Hi guys,

I used Siyah Kernel on my SII for dual Booting but see that Siyah doesn't yet do this on the SIII. Is there any Kernel that allows dual booting on the SIII?

Thanks if anyone can give me any info :)
[Galaxy S III Q&A, Help & Troubleshooting] DimonVideo:
No other kernel. Still wait :)

---

DimonVideo.ru
[Galaxy S III Q&A, Help & Troubleshooting] zodiaxe66:
The partition where dualboot is located is only 500mb and most roms is larger than that,so gorkhan is brainstorming on how to solve this and I'm quite sure that he won't implement it before JB sources is out,even then he has to make a full stable JB kernel before implementing dualboot,so don't expect it soon.
[Sony Xperia P, U, Sola, Go] Cach123:
Title says it all i think :)
[Sony Xperia P, U, Sola, Go] AnrgKrshn:
You should try CM9.1 or FXP137 or CM10

CM9.1 is ICS on CyanogenMod whereas FXP 137 is an unofficial CyanogenMod CM9 for the Xperia S. CM10 is Jelly Bean. Not everything is working in CM10, though and it's pretty unstable, so use caution with it.

I myself am using stock ICS with Advanced ICS Stock Kernel by Arakmar

Please hit the thanks button if I helped :)
[Samsung Galaxy Nexus] iGoogleNexus:
Just got the email stating that starting September 17 you will no longer be able to add funds to the prepaid card...October 17 the prepaid card will be Discontinued ... if u have 10 bucks that u haven't used... time to use it

-Google

#Team MiNCO
[Samsung Galaxy Nexus] Dakota0206:
I got this too. Beat me to posting :D
[Samsung Galaxy Nexus] Grey Ghost:
Yep, just got the email myself. Hopefully they'll have a few options for refunds in October.
[Samsung Galaxy Nexus] t3xboar:
and this means canadians are left high and dry. once again. sigh :(

This was our only option of even using the wallet. the new app that allows all cards requires a USA address on the card added to function.

Oh well. was a fun toy while it lasted.
[Samsung Galaxy Nexus] iGoogleNexus:
Lol perhaps within those months they'll announce an update for international users =]

-Google

#Team MiNCO
[Samsung Galaxy Nexus] flintdragon:
I didn't quite get the announcement. If they are discontinuing the card, why are they going to be changing the $2 non-usage fee to 30 days?
[Samsung Galaxy Nexus] osm0sis:
Yup. Guess I need to go find a way to spend exactly $67.68 in the next month.. :(
[Samsung Galaxy Nexus] bozzykid:
Buy a visa gift card for that amount. :)
[Samsung Galaxy Nexus] El Daddy:
From the email
[Samsung Galaxy Nexus] osm0sis:
Refunded to my BuyFromPowerSeller card with a fake AVS? Probably better that I spend it in Wallet. ;)
[Samsung Galaxy Nexus] Nocturnal86:
Good thing i never used it! But i may put my debit card on soon.
[Samsung Galaxy Nexus] Winesnob:
I should request my $0.56 back.
[Samsung Galaxy W I8150] [iop]wah:
Hi, just want to ask how can i download file directly from my cm9, even if i click the file it would not download..except on play store..
[Samsung Galaxy W I8150] Gary122:
Try opera

Sent from my Biowonder using KOH and NaOH
[Samsung Galaxy W I8150] [iop]wah:
Thx...
[Asus Transformer TF700] edtanas65:
Just noticed this issue this morning..after I tap or press on my display in the center upper prtion of my screen, I get grey blotches remaining... I baby this thing so I was wondering what could cause this issue.... I have sent my 700T in as RMA and hope that it can be fixed... see piks attached for further clarification.. and as you can see in one pik..the mode image after I changed the Performance mode remained static too..

So has anyone else seen this and if so what causes it..defect on screen???

Thank you
[Sony Xperia S, Acro S, Ion] letama:
Hi All,

Here is a new version of my boot manager.

If you didn't see first release, its purpose is to allow dual boot a firmware with two different kernels with a third one that manages boot selection:

Here is a demo of the previous version, it behaves almost the same:

[YOUTUBE]h3kMx921Ts8[/YOUTUBE]

Since first release, I added cwmod and twrp support for both build:

First build is run from native partition, and second build is installled on internal storage via loopbacks. Since first release, I added automatic loobpack creation:

CWM will take care of formatting them.

FIRST A BIG WARNING: all you'll see here is highly experimental, I'm not responsible for any damage or problem it could cause.

I don't have any idea if running a build on loops is wearing off flash memory, it could damage your device.

I don't think it dramatically change anything compared to standard wear on native partitions, but who knows... And something else could go wrong.
​
[Sony Xperia S, Acro S, Ion] letama:
For devs:

Source code:

Trimmed kernel uploaded to gitorious here , branch bootloader_kernel.

Boot menu (FBMenu, thanks to openAOS for initial release!) here.

Embedded kernel flasher kf : here.

Elf kernel splitter sksplit here. I use it mostly to extract kernel and cpio in repackaging firmware.

Background:

Here are some details on how it works:

I trimmed down a stock kernel to remove some fat and add a driver to set a specific memory location.

I embed a small assembly loader with this kernel and its cpio plus the other 2.

The tiny kernel is loaded first, it displays the menu and eventually starts cwm. The menu will set the memory location with the kernel choice, then reboot.

At next reboot, the assembly loader will detect the kernel choice and start the appropriate kernel.

So, in fact, you're booting two times, first the small loader, then the real boot.

It adds some boot time, but it's not dramatic. The advantage is that it's easy to build the loader, it's a simple init. Second advantage, the second kernel is running on a "fresh" start, no left-over in memory, no kexec patch to apply, it works with any kernel. Last, cwm can be embedded with the tiny kernel, so it's finally independent from the build kernel.
[Sony Xperia S, Acro S, Ion] letama:
Repack sample, FXP137 cm9.1:

unzip ../downloads/FXP137-cm-9-20120908-UNOFFICIAL-nozomi.zip

sksplit boot.img

sudo su

mkdir cpio

cd cpio

cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories

emacs init.semc.rc

# mount mmc partitions
# mount /system, set up links to the modem, and remount r/o
mount ext4 /dev/block/mmcblk0p12 /system wait rw barrier=1
mkdir /system/etc/firmware/misc 0771 system system
mount ext4 /dev/block/mmcblk0p12 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 /dev/block/mmcblk0p14 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 /dev/block/mmcblk0p13 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc

becomes:

# losetup on storage
mkdir /sd
mount vfat /dev/block/mmcblk0p15 /sd wait rw
# ro directly as misc is created by install script
mount ext4 loop@/sd/custom_system.ext4 /system wait ro barrier=1
setprop ro.crypto.tmpfs_options size=128m,mode=0771,uid=1000,gid=1000
mount ext4 loop@/sd/custom_data.ext4 /data wait noatime nosuid nodev data=ordered noauto_da_alloc
mount ext4 loop@/sd/custom_cache.ext4 /cache wait noatime nosuid nodev data=ordered noauto_da_alloc

and:

exec sbin/bootrec

becomes

exec /system/bin/chargemon

and save

rm init.semc.rc~

cd sbin

rm e2fsck bootrec bootrec-device fix_permissions killrecovery.sh mke2fs nandroid-md5.sh parted postrecoveryboot.sh sdparted tune2fs

cd ..

find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz

cd ..

rm -r cpio sec2-0x00020000.bin sec1-0x41300000.bin boot.img

mv sec0-0x40208000.bin zImage

emacs META-INF/com/google/android/updater-script

format("ext4", "EMMC", "/dev/block/mmcblk0p12", "0");
mount("ext4", "EMMC", "/dev/block/mmcblk0p12", "/system");

becomes

format("ext4", "EMMC", "/dev/block/loop2", "0");
mount("ext4", "EMMC", "/dev/block/loop2", "/system");

then

package_extract_file("boot.img", "/dev/block/mmcblk0p3");

becomes

package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "2", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);

add before this :

show_progress(0.200000, 0);
show_progress(0.200000, 10);

this:

run_program("/sbin/busybox", "mkdir", "/system/etc/firmware/misc");
set_perm(1000, 1000, 0771, "/system/etc/firmware/misc");

and save, then finally:

zip -r ../cm9-loop.zip *
[Sony Xperia S, Acro S, Ion] letama:
Repack Sample, 6.1.A.2.45 firmware on stock/native:

mkdir stock_6.1.A.2.45_zip

cd stock_6.1.A.2.45_zip

7z x ../downloads/LT26i_6.1.A.2.45_GENERIC_NL.7z

7z x "LT26i_6.1.A.2.45_GENERIC NL.ftf"

rm "LT26i_6.1.A.2.45_GENERIC NL.ftf"

mkdir zip_out

sin2raw kernel.sin kernel.elf

sksplit kernel.elf

mv sec0-0x40208000.bin zip_out/zImage

mv sec1-0x41300000.bin zip_out/initramfs.cpio.gz

sin2raw system.sin system.ext4

sudo su

mkdir system

mount -o loop -t ext4 system.ext4 system

cd system

... optionally add root, busybox:

cp -r /home/tama/supersu/system/* .

cd xbin

chmod 6755 su

cp /home/tama/cm9/out/target/product/gen9/system/xbin/busybox .

cp /home/tama/relink-busybox.sh .

chmod 755 relink-busybox.sh

cd ../..

tar -cvzf zip_out/system.tgz system

... get script from cm9, ..

cd zip_out

cp -a ../../fxp137_cm9_ziploop/META-INF .

emacs META-INF/com/google/android/updater-script

assert(getprop("ro.product.device") == "LT26i" || getprop("ro.build.product") == "LT26i" ||
getprop("ro.product.device") == "LT26a" || getprop("ro.build.product") == "LT26a" ||
getprop("ro.product.device") == "nozomi" || getprop("ro.build.product") == "nozomi");

ui_print("LT26i 6.1.A.2.45 firmware for boot manager (stock)");
show_progress(0.100000, 5);
format("MTD", "system");
mount("MTD", "system", "/system");
show_progress(0.700000, 60);
package_extract_file("system.tgz", "/tmp/system.tgz");
assert(run_program("/sbin/tar", "-cvzf", "/tmp/system.tgz") == 0);
show_progress(0.200000, 10);
assert(run_program("/system/xbin/busybox-relink.sh", "");
unmount("/system");
package_extract_file("zImage", "/tmp/zImage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zImage", "/tmp/initramfs.cpio.gz") == 0);
ui_print("Firmware installation complete");
[Sony Xperia S, Acro S, Ion] letama:
Repackage sample, KA14 with Aroma installer

sudo su
mkdir ka14
cd ka14
unzip /home/tama/sony/downloads/KA14_Xperia_SSpeed.zip
mv zImage zImage.original
sksplit zImage.original
mkdir cpio
cd cpio
cat ../sec1-0x41300000.bin | gzip -d | cpio -i --make-directories
rm *~
rm init
rm init_gb
mv init_ics init
rm recovery.*
rm -r res
rm 1
rm init.sh
cd sbin
rm tune2fs sdparted parted nandroid-md5.sh nandroid mr mke2fs killrecovery.sh fota-ua fota-mke2fs fix_permissions e2fsck checkabortedflash autoroot.sh
ln -s /init ueventd
cd ..
find . | cpio -o -H newc | gzip > ../initramfs.cpio.gz
cd ..
mv sec0-0x40208000.bin zimage
emacs META-INF/com/google/android/updater-script

change:

assert(package_extract_file("zImage", "/tmp/zImage"),
write_raw_image("/tmp/zImage", "/dev/block/mmcblk0p3"),
delete("/tmp/zImage"));

to:

package_extract_file("zimage", "/tmp/zimage");
package_extract_file("initramfs.cpio.gz", "/tmp/initramfs.cpio.gz");
assert(run_program("/sbin/kf", "1", "/tmp/zimage", "/tmp/initramfs.cpio.gz") == 0);

zip -r ../bm_native_ka14.zip META-INF customize system zimage initramfs.cpio.gz
[Sony Xperia S, Acro S, Ion] letama:
AOSP experiment

Special build, aosp 4.2.1 experiment!

This one is special and deserve specific instructions.

First, it's not functional, and will never be.

I just wanted to have a look at current status of AOSP experiment for Xperia S, it required much more fiddling than reasonable and ended into a monster.

Again, I take no responsability if you flash this. It doesn't work properly, it's not tested, it can be bad for your phone :). ​

Second, if you want to install this, read carefully instructions, it's not packaged like a normal loop rom.

Last: special thanks to FXP team, it wouldn't have been this far with the work they did on CM10. I took few binaries from FXP release and few patches from Cyanogen repo, no way to make it run without the work they did.

Now, that the warning are there, here is the status:

What's working:

1) It boots :)

2) Audio

3) Phone call/sms

4) Wifi

What's not working:

1) Data

2) Storage

3) And much more

Pre-Installation:

1) You need around 2G free space on storage

2) It will replace your loop kernel but keeps the loopback files untouched

3) If you want to save your current kernel, you can do this from loopback recovery with adb:

adb shell ke 2 /tmp/zimage /tmp/initramfs
adb pull /tmp/zimage
adb pull /tmp/initramfs

Installation

From loopback recovery, install zip file.

Restore previous loopback rom

Flash build zip file without wiping data/cache

or if you saved your kernel previously:

adb push zimage /tmp
adb push initramfs /tmp
adb shell kf 2 /tmp/zimage /tmp/initramfs
adb shell sync

then boot your loopback build.

Download

Download rom here, mirrors.

FAQ

1) What is this ?

I started this to check status of Google/Sony AOSP experiment. I wanted to see how far they went and how it behaves.

2) Why not making it functional ?

As it is, it's not worth it. To have the running state I have, I had to patch google aosp source, patch kernel, fiddle with FXP binaries, etc... This build is a Frankenstein monster and it would take quite a big amount of work to end up with something that takes many things from CM and doesn't work as good as CM.

We'll see if Sony goes further in releasing proprietaries and source code, but without that, AOSP will end up in CM without CM bonus :)
[Sony Xperia S, Acro S, Ion] Vipitus:
Wow, this is far more superior than 0.1!

So now I can install every ROM on loops?
[Sony Xperia S, Acro S, Ion] letama:
No, that's not possible, you need adapted zip for it. Maybe in a future version, but I think it would be very difficult to patch cpio's on the fly.

I'll continue adapting few builds to give more choice though.
[Sony Xperia S, Acro S, Ion] Vipitus:
For now only CM9, yes?

---------- Post added at 10:02 PM ---------- Previous post was at 10:00 PM ----------

Do this firmware exists?

Do you mean 6.1.A.2.45?
[Sony Xperia S, Acro S, Ion] letama:
Oups, Yes, too much writing sorry :) typo fixed, thanks for noticing.

Cm9.1 only, I'll add more later on, cm10 is difficult because of uncompressed kernel, any other firmware in mind?
[Sony Xperia S, Acro S, Ion] Vipitus:
AOKP JB, MIUI (on stock kernel)
[Sony Xperia S, Acro S, Ion] letama:
AOKP is using CM10 kernel, so same problem, the 10+MB uncompressed kernel doesn't fit. I'll do MIUI first, it should be quicker...
[Sony Xperia S, Acro S, Ion] championswimmer:
make a stock + jb dual kernel too :)

thats needed most right now
[Sony Xperia S, Acro S, Ion] electrash:
Letama sry i know you are tired but i didnt understand this with pack and repack stuff.

Do i have to do that by my self, or just flash and do what you write in first post?

And then i can switch from one rom to another on the go?

Sent from my LT26i
[Sony Xperia S, Acro S, Ion] Soheil_rf:
Seems download link for Cm9 is broken .
[Sony Xperia S, Acro S, Ion] Felimenta97:
+1

I usually don't do that, but I agree. Stock + JB is a must, I guess...

Sent from my LT26i with Tapatalk 2
[Sony Xperia S, Acro S, Ion] Nimche:
This is really nice! Fascinating...

Great Job!
[Sony Xperia S, Acro S, Ion] mpttrung:
I have a Q ? I tried it many times when I finished flash the CM9.1 over the Custom kernel. It always boot on custom kernel. It doest show for me 2 choises like in your video @@

Do I must use 2 roms only in your first page ??
[Sony Xperia S, Acro S, Ion] letama:
Sure, it's possible. It would require some cpio re-work, and maybe aroma removal too if it's in cpio, cpio space is limited. I'll check SSpeed KA12 (can't download KA13, bandwidth exceeded) and if I'm able to make it work, I'll ask krabappel2548 if I can redistribute the modified version.
[Sony Xperia S, Acro S, Ion] Felimenta97:
Please wait until you can download KA13. It seems to have some awesome mods and it's better than KA12. Also ask him if he, on the next releases, can already make the versions ready for dual boot.

What about init.d support?
[Sony Xperia S, Acro S, Ion] letama:
Can't wait :) I'm leaving on business trip tomorrow and may not have easy internet access for a week. I just want to make sure it's possible, going to KA13 won't take much effort.

KA12 (or 13) hase init.d support, so it will be there.
[Sony Xperia S, Acro S, Ion] letama:
Good! and congrats! Do you know what went wrong the first time ?

Yes, it's a bit different, but principle is the same. AOKP does a "mountall" to mount all partitions at once with a config file at root (can't remember the name and I don't have my laptop around). You just have to replace it with the mkdir and mounts -o loop lines

You can unpack my aokp cpio to see how I did it if you want.

Yes, that's ok. They are not included in aokp, so they don't take space on cpio. You can skip safely.

No problem at all, I'm very glad to see someone repackaging too! :)
[Sony Xperia S, Acro S, Ion] Felimenta97:
Oh, I see.

Maybe you could develop a automated tool in the future to do this porting job, when you finish this part :)

Good luck, then.
[Sony Xperia S, Acro S, Ion] Apology11:
I´m running Ubuntu on a virtual machine and something went wrong while copying your program from windows to the virtual machine.

"fstab.semc" I saw that too, but didn´t know what exactly it mounts, but I will look in you cpio and see what you changed :)

I looked at your AOKP init.semc.rc and found this

Is it correct, that mmcblk0p10 is mounted there?
[Sony Xperia S, Acro S, Ion] Giblet-dono:
I have KA13 loaded up on my main partition..

If you just flash it through the recovery for stock..

- I know the recovery has weird colors, but it works with your physical buttons

- choose Sony kernel in aroma!

And after it just re-flash the dual kernel through fastboot.

Also flash the modules form the first post..

you will be allright after that :)!
[Sony Xperia S, Acro S, Ion] Felimenta97:
Thanks for the info. Gonna try it later.

"I got my values. So you can keep yours, OK?"
[Sony Xperia S, Acro S, Ion] Apology11:
I made a FXP 139 for loop partition.

http://uploaded.net/file/vgmkn963

I had to name it like that because when I named it FXP139 uploaded.to said that its a copyrighted file :confused:

All credits go to FreeXperia Team, I just repacked it. With letama´s guide.

I hope it´s okay that I uploaded it.
[Sony Xperia S, Acro S, Ion] M.WeWe:
Noob Question

Sorry For Asking This But I Don`t Know To Much

All I Want Is To Know How To Run Stock Rom And CM9.1 FXP139

With Boot Manager I Don`T Know How To Do It But I Really Want

To Do This Because In CM9.1 I always Lose Mobile network After Reboot

So please Can You Guide Me To Do That.

My Phone Now Running CM9.1 FXP139

-----------------------------

Sorry For My Bad English

----------------------------

​
[Sony Xperia S, Acro S, Ion] Apology11:
Just read the second post in this thread!

1. Make sure that your on 6.1.A.2.45 original Firmware. Download the tft somewhere in this forum.

2. Then download this:

and if you want FXP139 than download this:

http://uploaded.net/file/vgmkn963

3. Then follow the guide on post 2 till step 6.

4. Then go to stock Recovery and flash the "bm_stock_6.1.A.2.56.zip"

5. then follow the guide from step 7 till 10.

6. then flash "bm_loop_cyanogenmod9.1_139.zip" in custom recovery

Your done
[Sony Xperia S, Acro S, Ion] Soheil_rf:
Thanks for update (139)

Please make unsecure kernel for 139 , i cant mount system as R/W
[Sony Xperia S, Acro S, Ion] Apology11:
Strange, I have to ask letama about that. I think fxp kernel is unsecured. I think that this is not caused by a secured kernel.

Send with Tapatalk from Xperia S
[Sony Xperia S, Acro S, Ion] letama:
I don't think default is unsecure by default. To enable unsecure kernel, just edit build.prop in your cpio, and change ro.secure to 0.
[Sony Xperia S, Acro S, Ion] Felimenta97:
OK. I'm going to try KA13, and if it's good I'm going to dual boot it with AOKP. so it will be KA13 + AOKP. But if it isn't good, to restore to the actual state (dual boot kernel with a tweaked stock and AOKP), I would need to re install the dual boot kernel and, on the stock CWM, restore the backup from the normal ROM?

With all this process, the second partition will stay untouched?
[Sony Xperia S, Acro S, Ion] mharckk:
im on dual boot already, tried to install ka13 as stock option, successully installed (custom install,uncheck kernel), but the problem is you will loose root, tried to update superuser but still no joy, so i flashed ics custom kernel to access root, then flashed this dual kernel again, but loose the

second partition (custom), then create new partition, now im good KA + AOKP, but the problem is since im using KA as stock option, then the kernel does not support int.d so i dont know if the tweaks on KA int.d is working :).

edit: i didnt see it @ first, after installing ka rom before u reboot it will prompt you to fix root :)
[Sony Xperia S, Acro S, Ion] Felimenta97:
So basically we need letama to work on it?

"I got my values. So you can keep yours, OK?"
[Sony Xperia S, Acro S, Ion] mharckk:
yeah, if i remember it right he said that its possible to put support for int.d for stock kernel, i dont know if doomlord's tutorial can be used in this kernel :)

here:

[ADDON][Xperia S] Generic startup/init.d scripts support for Stock ROM/Kernel

i tried that but there's error on running the script. :), well i hope letama will have time so that he can make his kernel support this.

well anyway, if you want to install ka rom dont forget to fix root before rebooting (it will prompt u anyway), so that you will retain your custom loopback.
[Sony Xperia S, Acro S, Ion] Apology11:
Do you mean default.prop ?