yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] letama:
v2 out

Here you are,

Wifi is fixed in this one. Just reflash it on top on previous one.

I also separated locked bootloader boot mechanism from cm in zip if Ion people want to adapt it, check lb-and-wifi directory. To adapt it for ion, you need to extract ion cm10 initramfs, tar it into cm.tar (tar -cvf, not compressed), then replace it in zip. Same goes for recovery, you can also grab a recovery.tar if it exists for ion.

You may have to adapt step2.sh regarding notification led, I'm not sure XS dev are same as ion, having them working is good to help debugging.

Here is a quick explanation of the principle:

Stock kernel is calling /system/bin/pre_hw_config.sh in its initramfs, we hijack the script to replace stock behavior to launch cm. To do that, I do it in two steps, first, pre_hw_config.sh will grab step2.sh and busybox from /system/bin, copy them to /tmp, relink busybox applets then launch step2.sh. Step2.sh will grab /system/bin/cm.tar, extract it to / then umount everything to start init again.

Wifi fix is basically use some stock binaries and firmware plus disable wifi direct. Just replace the binaires with the one for ion, hopefully it should work.
[Sony Xperia S, Acro S, Ion] adam20115:
Thank for this man, ive just flashed it in my LB xperia S, wifi works, but when i install the gapps, the home button doesn't work anymore and none of the google apps work
[Sony Xperia S, Acro S, Ion] Olivier:
This is really caused by GAPPs. I suggest you to use these.
[Sony Xperia S, Acro S, Ion] adam20115:
thanks man, i shall test the rom out and tell you the results :)

---------- Post added 2nd January 2014 at 12:28 AM ---------- Previous post was 1st January 2014 at 11:55 PM ----------

I've installed it with the gapps you suggested and I no longer have any problems at all, the only thing I've really found is that the camera is a bit slow to open, but apart from that its fine
[Sony Xperia S, Acro S, Ion] apurba_ron:
Will it be working on Xperia acro s LT26W
[Sony Xperia S, Acro S, Ion] letama:
Not directly, no, it has to be adjusted, acro s has different init/fstab files afaik.
[Sony Xperia S, Acro S, Ion] apurba_ron:
Thanks mate:rolleyes:
[Sony Xperia S, Acro S, Ion] -PiLoT-:
the camera takes a long time to open. using the one included in this rom. and nexus 5 camera
[Sony Xperia S, Acro S, Ion] MrGezz:
for ion, we also need to adjust our init/fstab files ??? or more ??

did not see your post a while ago .. haha
[Sony Xperia S, Acro S, Ion] Wyzco:
MrGeez do you think you could modify it based on this Post Instruction?

here Post #26
[Sony Xperia S, Acro S, Ion] MrGezz:
I don't know , haha . still need to learn :)
[Sony Xperia S, Acro S, Ion] rErEaT:
very nice!

I have only problem with camera and gps :)
[Sony Xperia S, Acro S, Ion] letama:
Gps looks fine here, are your date and time correct? That's the usual cause of problem.

---------- Post added at 10:04 PM ---------- Previous post was at 09:52 PM ----------

Difficult to be completely affirmative without having the device but basically, yes, that's all you need:

1) make sure that stock init.*.rc is calling /system/bin/pre_hw_config.sh

2) if it does, check step2.sh in zip file, you may have to adapt the notification led device names

3) extract your device cm10 initramfs and tar it back to cm.tar

4) replace recovery.tar

5) replace system with your cm10 one.

6) re-zip

After, it depends on your cm10 implementation, you may have to fiddle a bit with stock files for wifi/camera/... Ion/hikari/nozomi are more or less same motherboard so it should be similar to what I did for XS.

---------- Post added at 10:15 PM ---------- Previous post was at 10:04 PM ----------

To do that, you may want to check my thread if you don't know how to extract kernels. With cyanogen kernel, you have to start at sksplit (sin2raw not needed) until end of step 4.
[Sony Xperia S, Acro S, Ion] warlock6:
Hello, please, do you know if it works also with Xperia Arc S locked bootloader´s ???
[Sony Xperia S, Acro S, Ion] MrGezz:
I'm stuck with tar step , how to tar the file exactly ???
[Sony Xperia S, Acro S, Ion] Olivier:
You can always try. :)

http://www.cyberciti.biz/faq/how-do-i-compress-a-whole-linux-or-unix-directory/

Gesendet von meinem Xperia S mit Tapatalk
[Sony Xperia S, Acro S, Ion] Tommy-Geenexus:
How the hell should a nozomi rom work on an arc s?

No, it does not to be clear.

Sent from my white Xperia™Z
[Sony Xperia S, Acro S, Ion] letama:
so you have the initramfs extracted in a directory, right ? In this directory, you see init.rc, init.semc.rc (or sony) files ?

in this directory, just type

tar -cvf ../cm.tar .

tar file will be created in directory above.

One last thing I forgot to mention: when you replace system directory, make sure to copy system/xbin/busybox from mine to the same location. Mine is a static version, cynaogen stock is a dynamically linked. We need static to have the script work properly.
[Sony Xperia S, Acro S, Ion] MrGezz:
just the recovery.tar left .. how to get it ??
[Sony Xperia S, Acro S, Ion] letama:
I guess you have a locked bootloader version for your phone ? You can re-use this one. I did twrp as I prefer it and the cwm I grabbed wasn't working so well, but you can use whatever is working for yours.

If you don't have a lb version, it's the same principle as cm10 cm.tar, grab twrp for instance, extract initramfs, tar it back to recovery.tar
[Sony Xperia S, Acro S, Ion] Guynan:
Extracting initramfs

How do you extract the initramfs? I'm looking at porting to Ray, and can't quite get my head around this, any help would be much appreciated.

Thank you for your excellent work. :)
[Sony Xperia S, Acro S, Ion] letama:
Check this:
[Sony Xperia S, Acro S, Ion] MrGezz:
how to make sure init.*.rc is calling /system/bin/pre_hw_config.sh , I'm stuck with the sony bootlogo thou , n I can enter recovery .. haha
[Sony Xperia S, Acro S, Ion] letama:
You can or you can't enter recovery ? If you are able to reach recovery, it means that script is called.

To make sure that init*.rc are calling it, boot stock firmware and do from adb:

cd /
grep pre_hw_config *.rc

If you see as result "exec /system/bin/pre_hw_config.sh" or "exec sh /system/bin/pre_hw_config.sh", you're good.
[Sony Xperia S, Acro S, Ion] MrGezz:
I can enter recovery :)
[Sony Xperia S, Acro S, Ion] letama:
Good! Except if this is the old recovery, it means that the script is working.

Can you try to boot cm once again, reboot, and grab from adb dmesg and /proc/last_kmsg ?
[Sony Xperia S, Acro S, Ion] MrGezz:
I can confirm that it is the recovery for the ROM , btw , do you mean the cm for LB ??
[Sony Xperia S, Acro S, Ion] letama:
Ok, I'm a bit lost :). Yes, I meant try to boot cm for lb again, the one that gets stuck.

You are able to enter your original recovery, but not the one from you cm for lb attempt, that's what you mean?
[Sony Xperia S, Acro S, Ion] MrGezz:
haha, sorry to confused you , I meant the recovery for cm for lb ..
[Sony Xperia S, Acro S, Ion] letama:
Ok :) Good... So I need dmesg and cat /proc/last_kmsg to try to understand why cm doesn't boot.
[Sony Xperia S, Acro S, Ion] MrGezz:
I need to take it when I enter recovery right ??
[Sony Xperia S, Acro S, Ion] letama:
Yes. Your logs are good. Interesting...

In last_kmsg, first thing strange is this:

[ 17.969940] enable_store: android_usb: already disabled
[ 17.971649] init: cannot execve('/sbin/sh'): Permission denied

And this shows that /system is not mounted:

[ 18.239685] init: execve /system/bin/sh (ret = -1, errno = 2)
[ 18.239898] init: cannot find '/system/bin/tad', disabling 'tad'
[ 18.241851] init: execve /system/bin/sh (ret = -1, errno = 2)
[ 18.244995] init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
[ 18.245025] init: cannot find '/system/bin/vold', disabling 'vold'
[ 18.245056] init: cannot find '/system/bin/sh', disabling 'qcom-c_core-sh'
[ 18.245086] init: cannot find '/system/bin/netd', disabling 'netd'
[ 18.245086] init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
[ 18.245117] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[ 18.245117] init: cannot find '/system/bin/drmserver', disabling 'drm'
[ 18.245147] init: cannot find '/system/bin/mediaserver', disabling 'media'
[ 18.245178] init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
[ 18.245178] init: cannot find '/system/bin/installd', disabling 'installd'
[ 18.245208] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
[ 18.245208] init: cannot find '/system/bin/keystore', disabling 'keystore'
[ 18.245239] init: cannot find '/system/bin/sh', disabling 'qcom-c_main-sh'
[ 18.245239] init: cannot find '/system/bin/iddd', disabling 'iddd'
[ 18.245269] init: cannot find '/system/bin/suntrold', disabling 'suntrold'
[ 18.245269] init: cannot find '/system/bin/fast-dormancy', disabling 'fast-dormancy'
[ 18.245300] init: cannot find '/system/bin/illumination_service', disabling 'illumination'
[ 18.245330] init: cannot find '/system/bin/sh', disabling 'hw_config'
[ 18.245330] init: cannot find '/system/bin/updatemiscta', disabling 'updatemiscta'
[ 18.245361] init: cannot find '/system/bin/nvimport', disabling 'nvimport'
[ 18.245361] init: cannot find '/system/bin/touchd', disabling 'touchd'
[ 18.245391] init: cannot find '/system/bin/imei_transporter', disabling 'imei_transporter'

Can you check permissions in your cm.tar ? Especially for /sbin/sh ?

And check your fstab.semc in it ?

Now, regarding dmesg, this is strange:

<4>[ 20.547363] 140 0 0:00 /tmp/sh -c /tmp/step2.sh
<4>[ 20.547363] 496 0 0:00 {step2.sh} /tmp/sh /tmp/step2.sh
....
<4>[ 20.547393] 562 0 0:00 /tmp/sh -c /tmp/step2.sh
<4>[ 20.547393] 929 0 0:00 {step2.sh} /tmp/sh /tmp/step2.sh
...

<4>[ 20.551025] 1002 0 0:00 /tmp/sh -c /tmp/step2.sh
<4>[ 20.551025] 1358 0 0:00 {step2.sh} /tmp/sh /tmp/step2.sh

It looks like the script is executed multiple times, I don't see why. Could you check recovery.tar init*rc files if they have the exec /system/bin/pre_hw_config.sh ? If they do, comment any occurence in your recovery.tar

Same goes for cm.tar, you shouldn't have any exec /system/bin/pre_hw_config.sh left. I think I forgot to tell this in method, sorry :)
[Sony Xperia S, Acro S, Ion] MrGezz:
okay, it got solves , just comment the line , thanks :) the rom boot :)
[Sony Xperia S, Acro S, Ion] letama:
Ok. Can you upload your cm.tar and recovery.tar ? I'll take a look.
[Sony Xperia S, Acro S, Ion] MrGezz:
I just edit my post, it booting already , need to fix wifi left .. :victory:
[Sony Xperia S, Acro S, Ion] letama:
Great! Good job!

If you need help with wifi, I'd need logcat, dmesg and lsmod after boot.
[Sony Xperia S, Acro S, Ion] MrGezz:
I have not replace the binaries with the one from ion thou , wasn't that what causing the wifi problem ??
[Sony Xperia S, Acro S, Ion] letama:
It could be yes. You need at least to replace the bcm*.ko file, also, did you add the insmod in cm init file ?
[Sony Xperia S, Acro S, Ion] MrGezz:
ok, thanks , ermm , I don't think so ?? how do I do it?? I mean adding it to init file , the one inside cm.tar??
[Sony Xperia S, Acro S, Ion] letama:
You have to check your stock firmware init*.rc, there should be a line that looks more or less like this:

insmod /system/lib/modules/bcm4330.ko nvram_path=/system/etc/wifi/calibration iface_name=wlan0

just add the same line to your cm init.semc.rc. for XS I did it at the end of the "on boot" trigger.

If you did well, after booting cm, lsmod should show you that module is loaded.
[Sony Xperia S, Acro S, Ion] MrGezz:
everything is working now , except in recovery , can't mount sdcard but, external sdcard can be mount , btw , I'm using cwm :) thank you soo much for guiding me :)
[Sony Xperia S, Acro S, Ion] letama:
Great! Congratulation!

Regarding cwm, problem is probably recovery.fstab or missing mount point I guess.
[Sony Xperia S, Acro S, Ion] MrGezz:
I'm using the one that used in JB for ion , could that be a problem ???
[Sony Xperia S, Acro S, Ion] letama:
No, it shouldn't. And it works fine with Stock JB ? Weird. It could be because partitions are not umounted properly before launching recovery, or missing mount point.

What does say /tmp/recovery.log after trying to mount ?
[Sony Xperia S, Acro S, Ion] MrGezz:
attach
[Sony Xperia S, Acro S, Ion] letama:
Hum, ok.

So now I need adb shell dmesg and adb shell mount just after booting recovery. I guess you only miss something like umount /dev/block/mmcblk1p18 in your step2 script.
[Sony Xperia S, Acro S, Ion] MrGezz:
I just use your TWRP recovery , and it work .. :) thanks again :) now xperia ion lb user will be happy :)
[Sony Xperia S, Acro S, Ion] Wyzco:
Big Thanks

Yes we are!!!! lol :good:
[MENTION=834547]letama[/MENTION] Thank you [MENTION=5031348]MrGezz[/MENTION] Big Thanks and [MENTION=4329876]djolivier[/MENTION] hank you all! :)
[Sony Xperia S, Acro S, Ion] TiMiN8R:
I'm trying to port this over to Xperia T. With some help from [MENTION=4329876]djolivier[/MENTION] I've got it booting part-way, leds are working and I can get to CWM. I can adb to it so I can grab debugging info. CWM can mount internal and external storage and I was able to flash a kernel.zip. Flashing roms is not possible though because there's a problem with /system. It shows as mounted but it has no content. So either recovery.fstab or unmounting problem I guess.

Booting to CM hangs at a black screen.

I've done all that so it is most likely a video driver issue, last_kmsg shows a lot of this

[ 34.382084] Pid: 1057, comm: SurfaceFlinger
[ 34.382206] CPU: 0 Tainted: G W (3.4.0-g5b052b2-00815-g719dabf #1)
[ 34.382298] PC is at 0x4028996e
[ 34.382359] LR is at 0x4028f67d
[ 34.382450] pc : [<4028996e>] lr : [<4028f67d>] psr: 600f0030
[ 34.382450] sp : 40dc1c28 ip : 4019df80 fp : 40074988
[ 34.382633] r10: 00000000 r9 : 00000500 r8 : 000002d0
[ 34.382725] r7 : 00000001 r6 : 400741f8 r5 : 4028d000 r4 : 4007499c
[ 34.382847] r3 : 00000000 r2 : 00000000 r1 : 00000000 r0 : 00000000
[ 34.382908] Flags: nZCv IRQs on FIQs on Mode USER_32 ISA Thumb Segment user
[ 34.383030] Control: 10c5787d Table: b45bc06a DAC: 00000015
[ 34.383183] [<c0014710>] (unwind_backtrace+0x0/0x11c) from [<c0018350>] (__do_user_fault+0x7c/0xc4)
[ 34.383274] [<c0018350>] (__do_user_fault+0x7c/0xc4) from [<c06e49f4>] (do_page_fault+0x374/0x3c0)
[ 34.383427] [<c06e49f4>] (do_page_fault+0x374/0x3c0) from [<c000847c>] (do_DataAbort+0x134/0x1a8)
[ 34.383580] [<c000847c>] (do_DataAbort+0x134/0x1a8) from [<c06e3234>] (__dabt_usr+0x34/0x40)
[ 34.383702] Exception stack(0xedf2dfb0 to 0xedf2dff8)
[ 34.383763] dfa0: 00000000 00000000 00000000 00000000
[ 34.383885] dfc0: 4007499c 4028d000 400741f8 00000001 000002d0 00000500 00000000 40074988
[ 34.384037] dfe0: 4019df80 40dc1c28 4028f67d 4028996e 600f0030 ffffffff
[ 34.516343] pgd = ed1bc000
[ 34.516435] [00000000] *pgd=00000000

So how would I fix that? Use a different stock kernel? Or could I try a newer CM (10.1/2/11)?
[Sony Xperia S, Acro S, Ion] letama:
Hi,

Yes, umounting system didn't go well, it's still mounted before launching recovery:

<4>[ 9.645811] ***** PL: umount result: *****
<4>[ 9.646940] rootfs on / type rootfs (rw,relatime)
<4>[ 9.646940] tmpfs on /dev type tmpfs (rw,nosuid,relatime,mode=755)
<4>[ 9.646940] devpts on /dev/pts type devpts (rw,relatime,mode=600)
<4>[ 9.646940] proc on /proc type proc (rw,relatime)
<4>[ 9.646940] sysfs on /sys type sysfs (rw,relatime)
<4>[ 9.646940] none on /acct type cgroup (rw,relatime,cpuacct)
<4>[ 9.646940] tmpfs on /mnt/asec type tmpfs (rw,relatime,mode=755,gid=1000)
<4>[ 9.646940] tmpfs on /mnt/obb type tmpfs (rw,relatime,mode=755,gid=1000)
<4>[ 9.646940] none on /dev/cpuctl type cgroup (rw,relatime,cpu)
[B]<4>[ 9.646970] /dev/block/platform/msm_sdcc.1/by-name/System on /system type ext4 (ro,relatime,discard,data=ordered)
[/B]<4>[ 9.646970] /dev/block/platform/msm_sdcc.1/by-name/SDCard on /mnt/int_storage type ext4 (rw,nosuid,nodev,relatime,discard,noauto_da_alloc,data=ordered)

You should stop at least this:

<4>[ 9.445414] 155 0 0:02 /system/bin/ta_qmi_service
<4>[ 9.445414] 157 9999 0:00 /system/bin/rmt_storage

with stop or killall.

Yes, you have to match your android stock version with cm version. What is your stock firmware android version ? At this point, logcat is working so I'd need logcat *:v to have more details.
[Sony Xperia S, Acro S, Ion] TiMiN8R:
OK I added those two to the "stop services" section in step2.sh and now system is unmounted properly and functioning normally in CWM.

But, now it doesn't get to the black screen as before and after rebooting to recovery I can't get last_kmsg:

~ # cat /proc/last_kmsg
cat /proc/last_kmsg
cat: can't open '/proc/last_kmsg': No such file or directory

Went back to the previous version but I can't get a logcat at the black screen, adb is just hanging at "waiting for device".

Stock android for T is 4.1.2 so CM10 is the best bet but we'll be getting 4.3 in the next week or so.
[Sony Xperia S, Acro S, Ion] letama:
Ok. So, if system is unmounted properly, this is the way to go.

Regarding no last_kmsg, you should always get one if you reboot and not shutdown. How do you reboot ? Long press until one vibration and it reboots ? Or long press until 3 vibrations then power on by long press power ? If it's similar to XS, you should do the one vibration to get last_kmsg. Long press to three is full power down and memory is cleared.
[Sony Xperia S, Acro S, Ion] TiMiN8R:
You're right, must've turned it off instead of rebooting. So now the problem is that system isn't mounted anymore. It must be remounted through init.rc?

[ 11.698733] init: cannot find '/system/bin/servicemanager', disabling 'servicemanager'
[ 11.698855] init: cannot find '/system/bin/vold', disabling 'vold'
[ 11.699008] init: cannot find '/system/bin/netd', disabling 'netd'
[ 11.699099] init: cannot find '/system/bin/debuggerd', disabling 'debuggerd'
[ 11.699221] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
[ 11.699313] init: cannot find '/system/bin/surfaceflinger', disabling 'surfaceflinger'
[ 11.699435] init: cannot find '/system/bin/app_process', disabling 'zygote'
[ 11.699557] init: cannot find '/system/bin/drmserver', disabling 'drm'
[ 11.699649] init: cannot find '/system/bin/mediaserver', disabling 'media'
[ 11.699771] init: cannot find '/system/bin/dbus-daemon', disabling 'dbus'
[ 11.699862] init: cannot find '/system/bin/installd', disabling 'installd'
[ 11.699984] init: cannot find '/system/bin/keystore', disabling 'keystore'
[ 11.700137] init: cannot find '/system/bin/handle_compcache', disabling 'compcache'
[ 11.700808] init: cannot find '/system/bin/sh', disabling 'console'
[Sony Xperia S, Acro S, Ion] letama:
Yes, it should be remounted by cm initramfs through init.*.rc. I don't know which rc is responsible for mounting in your cm, you should check mount or mount_all.

In your log, this line looks suspicious:

[ 11.519822] init: could not import file '/init.qcom.rc' from '/init.rc'

Is it (init.qcom.rc) part of stock and/or cm ?
[Sony Xperia S, Acro S, Ion] letama:
Hum, ok.

Could you upload the init*.rc from stock and your cm.tar ? I want to take a look.

Orders of imports shouldn't matter, mount must happen on the "on fs" trigger and init.qcom-etc.rc commands should happen on a trigger that comes later like "on post fs" for instance.

I confirm, ro.hardware property is from kernel /proc/cmdline (it contains androidboot.hardware=qcom for instance).

Just to confirm, ro.hardware is qcom in stock firmware, sony in cm ?
[Sony Xperia S, Acro S, Ion] TiMiN8R:
Well, somehow it does seem to matter. I copied the mount_all command to init.qcom-etc.rc and now it does boot. It also contains "on init" and "on early-boot" triggers, I put it in between those. Now I still have a black screen but I do have logcat and adb shell.

The whole order of importing *.rc's is completely different between stock and cm. I've attached the ramdisks from both in the cpio.7z.

And I can't thank you enough for your help and especially your very speedy replies!
[Sony Xperia S, Acro S, Ion] letama:
Indeed, in your case it matters as both files are on same trigger "on fs"

Root cause of surface flinger is this:

E/libgenlock(21316): genlock_create_lock: open genlock device failed (err=Permission denied)

E/gralloc (21316): alloc_impl: genlock_create_lock failed

Your problem is probably again sony/qcom. Can you try to rename or copy ueventd.sony.rc to ueventd.qcom.rc ? It should help.

Also, I'd suggest to rename temporarly /system/lib/hw/camera.whatever.so to something like camera.whatever.so.renamed to avoid it trying to load at first, it doesn't seem to start well.

You may also want to check in this directory if you shouldn't rename some file.sony.so to file.qcom.so...
[Sony Xperia S, Acro S, Ion] TiMiN8R:
I'm getting now why it's such a mess. Pulled this from logcat:

I/DEBUG ( 653): Build fingerprint: 'Sony/LT30p_1269-0608/LT30p:4.0.4/7.0.A.3.195/PPP_xw:user/release-keys'

The CM10 I'm using as base is the official one, but it's from last year, before we had an official Sony 4.1.2. So all the proprietary blobs etc are from the old .195 ICS firmware. I will download the latest FXP and start again, hoping that will yield better results.
[Sony Xperia S, Acro S, Ion] letama:
Oh, yes, didn't catch that. Hopefully FXP team did the same as they do with our XS, use JB kernel source code and upgrade blobs. If you still have the sony/qcom ro.hardware difference, you'll have to rename the ueventd, it's critical to have the proper access rights on devices.
[Sony Xperia S, Acro S, Ion] TiMiN8R:
Yes the latest FXP release seems to be pretty up-to-date. It's at least based on the JB kernel source, though not the very latest.

I renamed init.sony.rc to init.qcom.rc, ueventd.sony.rc to ueventd.qcom.rc and moved the whole "on fs" part from init.qcom.rc to init.qcom-etc.rc.

It's booting and logcat is much cleaner, no camera and surfaceflinger spam but still no display.

Last_kmsg is full of

MDP: unknown ioctl (cmd=40506d89) received!

So now I guess I have to find some libs or modules responsible?
[Sony Xperia S, Acro S, Ion] letama:
mdp is video driver. The message means that your stock kernel doesn't implement the same video ioctl as the one used in cm hal.

There is no easy way to solve that I'm afraid. You can try to play with dlls (check this for a list), but it has big chances to fail. The proper way to do that is to get fxp repo, patch hal to match stock kernel and recompile cm.
[Sony Xperia S, Acro S, Ion] TiMiN8R:
I replaced hwcomposer.msm8960.so, that seems yo have fixed it. Also tried a couple of others that didn't work: gralloc.msm8960.so (can't start), copybit.msm8960.so (brought back the camera probs). Still no screen.

Most prominent spam now is

smd_pkt_open: DATA5_CNTL open failed -19

I also noticed this in logcat

I/clearpad_fwloader( 681): hanlde_arg: option = [default]
I/clearpad_fwloader( 681): hanlde_arg: saved.module_id = [0x32]
E/clearpad_fwloader( 681): read_sysfs: Unable to open /sys/devices/virtual/input/mice/name
E/clearpad_fwloader( 681): read_sysfs: Unable to open fwfamily

That is the touchscreen. There is indeed no /sys/devices/virtual/input/mice/name. I'm not sure if it is related to the no video issue but it's a problem nonetheless.

I'm starting a thread in the Xperia T development section to hopefully get some more people in on this.
[Sony Xperia S, Acro S, Ion] lm_sandoval:
HDMI problem

HDMI is not working in the ROM (http://xdaforums.com/showthread.php?t=2593806), video is ok but no audio at all.

Also, it freeze a lot pressing home button (recents apps). Sorry for my english
[Sony Xperia S, Acro S, Ion] yawo76:
How to get music to play through headphones

Hi All,

I was very happy to see the CM10 finally working on locked bootloader. I have successfully installed it on my Xperia S. The only problem I am facing at the moment is that when I connect a headphone the music does not play through it, it still plays aloud as if no headphone were connected.

I have searched through this thread and the developer section thread but have found no solution to it. Please, if anyone can provide an answer I would be very grateful since I like this rom. What is keeping me from using it daily is this sound problem.

Regards!