yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] letama:
Yes. RGBX is indeed reversed, so it is BGR. However, I checked source again, RGBX is in fact ABGR, not BGRA. I'm not sure where the alpha is on sony though.

I'm looking into this because of aroma: I'm using cm10 cwmod in my dual boot system, and aroma colors are whacked. I started digging into this, so I compiled a full fbset, here is what I have on a stock firmware:

mode "720x1280-0"

# D: 0.002 MHz, H: 0.003 kHz, V: 0.002 Hz

geometry 720 1280 720 3840 32

timings 418037760 45 128 3 9 3 4

rgba 8/24,8/16,8/8,8/0

so, if I'm reading well, it's abgr, and RGBX should be ok.

However, when I'm on cwmod, I have this:

mode "720x1280-0"

# D: 0.002 MHz, H: 0.003 kHz, V: 0.002 Hz

geometry 720 1280 720 2560 16

timings 418037760 45 128 3 9 3 4

rgba 5/11,6/5,5/0,0/0

RGB565.

The problem is that with current recovery-gfx.c, we have this:

#if defined(RECOVERY_BGRA)

#define PIXEL_FORMAT GGL_PIXEL_FORMAT_BGRA_8888

#define PIXEL_SIZE 4

#elif defined(RECOVERY_RGBX)

#define PIXEL_FORMAT GGL_PIXEL_FORMAT_RGBX_8888

#define PIXEL_SIZE 4

#else

#define PIXEL_FORMAT GGL_PIXEL_FORMAT_RGB_565

#define PIXEL_SIZE 2

#endif

As we define "RECOVERY_BGRX" string in makefile, it gets defined nowhere and defaults to RGB_565.

minui Android.mk has this:

ifeq ($(TARGET_RECOVERY_PIXEL_FORMAT),"RGBX_8888")

LOCAL_CFLAGS += -DRECOVERY_RGBX

endif

ifeq ($(TARGET_RECOVERY_PIXEL_FORMAT),"BGRA_8888")

LOCAL_CFLAGS += -DRECOVERY_BGRA

endif

but nothing for BGRX...

So at the end, when recovery-gfx.c do this:

if (ioctl(fd, FBIOPUT_VSCREENINFO, &vi) < 0) {

it sets frame buffer to 565, else case on pixel format:

} else { /* RGB565*/

vi.red.offset = 11;

vi.red.length = 5;

vi.green.offset = 5;

vi.green.length = 6;

vi.blue.offset = 0;

vi.blue.length = 5;

vi.transp.offset = 0;

vi.transp.length = 0;

}

That's why I'm asking about this... a bit lost :) Why 565 ?
[Sony Xperia S, Acro S, Ion] K900:
Woo. That's probably because BGRX was there in CM9 and now it's not there for CM10. 565 is just the default fallback for everything really.
[Sony Xperia S, Acro S, Ion] letama:
Yes, 565 is fallback, so if BGRX was removed in cm10 it makes sense! I'll check cm9 then. Thanks!

---------- Post added at 07:20 PM ---------- Previous post was at 06:53 PM ----------

Ok, I checked cm9, it's the same (at least, now), so I guess I should consider it as a bug. I'm trying to compile with RGBX only and no custom ui, because if my fbset is correct, stock is exactly running on rgbx scheme (ABGR) and not BGRA.

*edit*: Recovery is fine with RGBX and fbset is consistent with stock, so I believe it's the way to go. I'm having issues with keys though, first press on key is kind of buffered and doesn't do anything, second press triggers both at the same time... Oh well, more debug needed.
[Sony Xperia S, Acro S, Ion] elfeneco:
Update done to FXP140 ok... Torch in notification bar functional. Thx.
[Sony Xperia S, Acro S, Ion] AnrgKrshn:
Hey guys!

Hope you're all doing well today :)

I was just wondering if there's been an update on the camera situation... I thought Sony released the binaries as part of the AOSP effort? Or does this have nothing to do with it?

I have no idea, but I'm just asking, hope you don't mind.
[Sony Xperia S, Acro S, Ion] K900:
Not those binaries.
[Sony Xperia S, Acro S, Ion] ace-drink:
just tried 140 CM 10....is it possible that the earpiece volume during calls is quite low? much lower than normal....

Is this a known bug?
[Sony Xperia S, Acro S, Ion] elfeneco:
I don't see this problem on mine.

However I still have problem with proximity sensor during a call3 I mean, screen switch off when I get it near my ear but doesn't switch on when I move it away. I have to press power button to make it back. :confused:
[Sony Xperia S, Acro S, Ion] Phantasm4489:
How come the cm9 gets builds on the official build server for nozomi but cm10 doesn't? Will this be addressed at some point? I presume the new ota feature will rely on the get.cm server. It would be nice to see this feature in the coming builds.
[Sony Xperia S, Acro S, Ion] HooLIMAN87:
Imo when CM10 is stable enough (working camera etc) will get his place on get.cm. ;)
[Sony Xperia S, Acro S, Ion] Phantasm4489:
The build server caters for both stable and nightly builds.
[Sony Xperia S, Acro S, Ion] letama:
OK! I finally figured it out. So first, I confirm that RGBX_8888 is ok. Here is the diff I used, basically get rid of custom graphics recovery-gfx.c and change format:

diff --git a/BoardConfigCommon.mk b/BoardConfigCommon.mk
index 326410a..f7037cd 100644
--- a/BoardConfigCommon.mk
+++ b/BoardConfigCommon.mk
@@ -84,11 +84,10 @@ TARGET_CUSTOM_BLUEDROID := ../../../device/sony/fuji-common/bluedroid/bluetooth.
ENABLE_WEBGL := true

# Custom boot
-TARGET_RECOVERY_PIXEL_FORMAT := "BGRX_8888"
+TARGET_RECOVERY_PIXEL_FORMAT := "RGBX_8888"
TARGET_RECOVERY_PRE_COMMAND := "touch /cache/recovery/boot;sync;"
BOARD_CUSTOM_BOOTIMG_MK := device/sony/fuji-common/custombootimg.mk
TARGET_RELEASETOOL_OTA_FROM_TARGET_SCRIPT := device/sony/fuji-common/releasetools/semc_ota_from_target_files
-BOARD_CUSTOM_GRAPHICS := ../../../device/sony/fuji-common/recovery/recovery-gfx.c
BOARD_CUSTOM_RECOVERY_KEYMAPPING := ../../device/sony/fuji-common/recovery/recovery-keys.c
BOARD_USE_CUSTOM_RECOVERY_FONT := \"roboto_15x24.h\"

Doing this will trigger a bug in cwm double buffering as it goes 32bits, it tries to create a virtual buffer with 4 x Physical instead of the two required and fails with nozomi. Here is the fix:

diff --git a/minui/graphics.c b/minui/graphics.c
index 3183cd1..39db237 100644
--- a/minui/graphics.c
+++ b/minui/graphics.c
@@ -167,7 +167,7 @@ static void get_memory_surface(GGLSurface* ms) {
static void set_active_framebuffer(unsigned n)
{
if (n > 1) return;
- vi.yres_virtual = vi.yres * PIXEL_SIZE;
+ vi.yres_virtual = vi.yres * 2;
vi.yoffset = n * vi.yres;
vi.bits_per_pixel = PIXEL_SIZE * 8;
if (ioctl(gr_fb_fd, FBIOPUT_VSCREENINFO, &vi) < 0) {

I'm going to submit a bug report to freexperia issue tracker. Sorry for the laziness (lack of time too :)) of not going to gerrit, too much setup for a single patch.
[Sony Xperia S, Acro S, Ion] K900:
Bad idea. You need to define PIXEL_SIZE somehow.
[Sony Xperia S, Acro S, Ion] letama:
I didn't undefined PIXEL_SIZE, it's still defined, but it's not used anymore in calculating virtual y size. virtual y size is always x2 to have two frame buffers to do double buffering.

PIXEL_SIZE is defined here:

#if defined(RECOVERY_BGRA)
#define PIXEL_FORMAT GGL_PIXEL_FORMAT_BGRA_8888
#define PIXEL_SIZE 4
#elif defined(RECOVERY_RGBX)
#define PIXEL_FORMAT GGL_PIXEL_FORMAT_RGBX_8888
#define PIXEL_SIZE 4
#else
#define PIXEL_FORMAT GGL_PIXEL_FORMAT_RGB_565
#define PIXEL_SIZE 2
#endif

and that's why vi.yres_virtual is ok (with luck) with 565 but is not with BGRA or RGBX
[Sony Xperia S, Acro S, Ion] K900:
Yeah, that's the problem. But patching the recovery source is wrong, it needs to be done in the device tree. Maybe add another define.
[Sony Xperia S, Acro S, Ion] letama:
No, it's not wrong, it's definitely a cwm bug. PIXEL_SIZE has nothing to do there... it should be fixed in cwm source, it's not device dependent and it should always be 2 except if they decide to do triple or quadruple buffering which I highy doubt. The fact that it works on other devices is pure luck and forgiveness of fb drivers, and a waste of memory.

*edit* More background on this:

When you look at set_active_framebuffer, you have this:

vi.yoffset = n * vi.yres;

This is how the double buffering is working: n is 0 or 1 (gr_flip() sets it like this gr_active_fb = (gr_active_fb + 1) & 1 ), so the view port is 0 -> yres (buffer 0) or yres -> yres x 2 (buffer 1), and your virtual buffer height should be yres x2.
[Sony Xperia S, Acro S, Ion] K900:
Not too sure about that. Anyway, talk to koush or whoever is in charge of CWM now.
[Sony Xperia S, Acro S, Ion] KeiranFTW:
CM10 has triple buffering (part of butter)
[Sony Xperia S, Acro S, Ion] K900:
I don't think the recovery uses that.
[Sony Xperia S, Acro S, Ion] letama:
Yes, in surface flinger and opengl, but not in recovery with frame buffer. Buffer swap is driven by gr_active_fb = (gr_active_fb + 1) & 1 ), and this will never go above 1.
[Sony Xperia S, Acro S, Ion] championswimmer:
Why don't you you send your patch to gerrit asap

Just git clone the recovery from gerrit itself and push into refs/for/jellybean
[Sony Xperia S, Acro S, Ion] letama:
Ok, will do, I need to dig into the way to setup and properly submit to gerrit, complete noob about this.
[Sony Xperia S, Acro S, Ion] tomfan203:
Camera n all features work ?

Can I move apps from Phone to Internal Storage as before on official Sony ICS & GB ?

Coz I experienced this problem with CM9 on my LT26i :

The "Move to Internal Storage / Phone / SD Card" btn were gone...
[Sony Xperia S, Acro S, Ion] xpsg:
Camera and HDMI not working. I think project butter ain't working too.

Sent from my Hikari
[Sony Xperia S, Acro S, Ion] K900:
Oh wow. You're most definitely the first one to notice those. Something is definitely broken there. Like, maybe, your reading ability?
[Sony Xperia S, Acro S, Ion] HooLIMAN87:
I think that he just replied to guy above him. ;)
[Sony Xperia S, Acro S, Ion] K900:
Oh, I probably missed it because of the huge screenshot, sorry.
[Sony Xperia S, Acro S, Ion] xpsg:
I was just replying to the post above me. Tapatalk didn't quote the post when I tapped reply.

Edit: I've edited the post to include the quote.
[Sony Xperia S, Acro S, Ion] krushhh:
Nice roms these cm9/10's... but for me: better sound + bravia engine + fewer bugs > a (slightly) faster rom
[Sony Xperia S, Acro S, Ion] championswimmer:
We never asked for your opinion

This is a dev thread not a place to share your "views"

---------- Post added at 09:47 PM ---------- Previous post was at 09:45 PM ----------

Send me your patch, commit msg, name and github email id if you wish

I can commit on your behalf with your authorship
[Sony Xperia S, Acro S, Ion] letama:
Thanks for the proposal! I finally took my courage, battled a bit with my ssh setup and succeeded uploading first one. I need this one to go through before pushing the second one.
[Sony Xperia S, Acro S, Ion] DeJe63:
Oh man... :rolleyes:

You mean it's a self satisfying thread? :angel:
[Sony Xperia S, Acro S, Ion] championswimmer:
Its xda-DEVELOPERS forum

Not xda-USERS forum

Thing is if you find a problem tell us

If you dont like our work.... Why they hell did you even sign up here to post your rotten views... We have no problem if you like stock.... Keep your liking to yourself

Not aimed at you but in general to whiners
[Sony Xperia S, Acro S, Ion] :
Let's stay on topic shall we.

Sent from my Nocturnalized One XL using Forum Runner
[Sony Xperia S, Acro S, Ion] megamarini:
Battery

Anybody could tell me the duration of battery? is it good?
[Sony Xperia S, Acro S, Ion] realfelix:
I've used this for like 3 days, the battery is nice, you can get one day and a half easily imo.
[Sony Xperia S, Acro S, Ion] Ben36:
Project butter working?
[Sony Xperia S, Acro S, Ion] realfelix:
feels much smoother than CM9 to me.
[Sony Xperia S, Acro S, Ion] schickel:
I don't know if everybody seen this post: http://xdaforums.com/showthread.php?t=1920733

CAMERA IS WORKING :)
[Sony Xperia S, Acro S, Ion] ishamm:
I don't remember having seen this covered, but apologies if it's been asked: is there a way to get the bravia engine from xs or xt working on cm10? Also will the ac!d sound mod work on this? Thanks
[Sony Xperia S, Acro S, Ion] redmissile:
Mine goes one day and few hours, with data always on.

Camera also works with the new patch.

Rom is extra smooth, some problems are with, the multi taksing sometimes when you try to switch from app to app the screen freezes and you have to restart the device, also i have tried several bluetooth HF and they connect but no audio is going to them and last when the screen goes off while talking you have to press the power button to see the call and hang up because the screen never goes on again.
[Sony Xperia S, Acro S, Ion] ILoveAndroid77:
Is it a known issue that ui performance is quite bad? Looks like no hardware acceleration? Is this the case just for me?
[Sony Xperia S, Acro S, Ion] megamarini:
What governor do you use?
[Sony Xperia S, Acro S, Ion] ILoveAndroid77:
Ok, it's the camera fix. Without: video playback (of e.g. self recorded full hd clips) is smooth. With fix: about 1-2fps, and UI in general not smooth.. :(
[Sony Xperia S, Acro S, Ion] arminalvand:
not wifi worked in cm10 fxp 140 please help wifi fix not work???

why????

thanks
[Sony Xperia S, Acro S, Ion] Stero!:
Why with cm10 i can't use akg k305?! :(
[Sony Xperia S, Acro S, Ion] Poesini:
Anyone tried to use this on CM10?

http://xdaforums.com/showthread.php?t=1908269
[Sony Xperia S, Acro S, Ion] redmissile:
On demand, why?
[Sony Xperia S, Acro S, Ion] tomfan203:
Move apps

Can I move apps from phone memory to internal storage as in official Sony Xperia S LT26i ROM?

Coz I found this problem on my Xperia S running CM9.1, the "Move to Phone, Internal storage or SD" btn is missing...
[Sony Xperia S, Acro S, Ion] megamarini:
Battery

Hi guys.. I have a proble with the battery... the battery drain is very good but the percentage jump in very irregular way.. like from 90% to 86%... I've tried to calibrate battery, wipe cache, withe dalvik cache and wipe battery stats but the "problem" persist.. has anyone a solution?
[Sony Xperia S, Acro S, Ion] jerpelea:
FXP141 released
​
[Sony Xperia S, Acro S, Ion] SilentEYE:
I had the same problems with screen freezes. is there any solution?
[Sony Xperia S, Acro S, Ion] Poesini:
Im guessing CM10 wont have nightlies until its stable?

Or at least not released to the public like in bbqdroid?
[Sony Xperia S, Acro S, Ion] utsav911:
Anyone having random screen flickering with fxp141?

sent from my lightening fast Xperia™ Arc HD!
[Sony Xperia S, Acro S, Ion] nemer12:
this one I think is a common bug :-s .

if not i had them also ( i dont have cm 10 anymore, not worth at this moment)
[Sony Xperia S, Acro S, Ion] DavosR:
Do I need to unlock the bootloader? If so, you can unlock the bootloader even if the configuration menu says: "Bootloader unlock allowed: No"?? :confused:

Thanks guys! :thumbup:
[Sony Xperia S, Acro S, Ion] utsav911:
At least not by official way I guess :confused:
[Sony Xperia S, Acro S, Ion] PhilAd:
You should read sticky threads and the first post. There are people in this forum who took a lot of time to wrote clear and easy to read FAQ and Tutorials. Furthermore there is a searchfunction in case that you cannot find the correct sticky thread.

Just an information for future questions. Normally this threads are not used to be for answering the same questions every day.

Gesendet von meinem LT26i mit Tapatalk 2
[Sony Xperia S, Acro S, Ion] redmissile:
Just finished flashing FXP141, still needed to flash the camera fix after the update, for the camera to work, only for pictures and panorama not video.

The bt is working now, also while taking a call and screen goes out, after you remove the phone from your ear the screen goes on again. I had an issue with that with fxp139
[Sony Xperia S, Acro S, Ion] PhilAd:
u might need to flash the camera "fix" until there is a solution to get the camera working with ION instead of PMEM.
[Sony Xperia S, Acro S, Ion] fak521:
In cm blog they put M build will be available then why no official cm 10 build for XS is not available?
[Sony Xperia S, Acro S, Ion] K900:
These builds come from official maintainers of CM for the device. You can think of them as official nightlies.
[Sony Xperia S, Acro S, Ion] fak521:
Hmm that's well known from news bro why don't add it to official list ... cause these devs are very good in what they doing
[Sony Xperia S, Acro S, Ion] K900:
Because the CM policy is only to accept fully working devices. There is still no camera and it's a blocker.
[Sony Xperia S, Acro S, Ion] fak521:
yes

thats acceptable point bro..

i am waiting for your words to come true

hope to get jelly bean in oct last or before november half as you said bro
[Sony Xperia S, Acro S, Ion] luaifarah:
what does fxp141 differ from fxp136?
[Sony Xperia S, Acro S, Ion] Poesini:
If you ask these kind of questions you should not be using this ROM

http://code.google.com/p/freexperia/
[Sony Xperia S, Acro S, Ion] luaifarah:
lol thanks but i already used 136 and i saw that 141 has some issues (although i do know of other issues in 136)

so my question was what are the DRAMATIC differences that i can easily notice! thanks anyway :D

plus i have sxs and it seems that there arent many differences for sxs
[Sony Xperia S, Acro S, Ion] carlos118:
CM are adding a M2 build for this phone, does that mean it is a different developer? Also was the M2 based on this code? I do not see any CM10 nightlys on their site so can anyone clarify what is happening with CM10?

Also i saw them post a CM10 M1 build for the xperia s but i do not see that on the site either?
[Sony Xperia S, Acro S, Ion] luaifarah:
so cm10 is stable now? camera and everything else works?
[Sony Xperia S, Acro S, Ion] K900:
No. Camera. Doesn't. Freaking. Work.
[Sony Xperia S, Acro S, Ion] scook94:
Your patience with these numpties always amazes me!

Do you know if the latest 4.1.2 will be incorporated in the the next FXP build? I may jump back on board CM10 if it is.
[Sony Xperia S, Acro S, Ion] K900:
Already there for M2.
[Sony Xperia S, Acro S, Ion] scook94:
Shame there's no M2 for nozomi though.
[Sony Xperia S, Acro S, Ion] RawkBob:
Of course it will, fxp always build to the latest version of cm over each weekend when they push out the builds.

IMO the 'm' versions shouldn't include the nozomi and hikari as they are not complete - no camera. The Fxp team should point this out to cm to avoid the masses moaning about the missing m version each release.
[Sony Xperia S, Acro S, Ion] luaifarah:
inhale... exhale O.o
[Sony Xperia S, Acro S, Ion] nemer12:
why do they say that M2 for xperia s ?? if there is no m2 for xperia s ?? lol :\
[Sony Xperia S, Acro S, Ion] Poesini:
Yep no nozomi version for M2 :(
[Sony Xperia S, Acro S, Ion] electrash:
Wait till it get uploaded man :)

Sent from my LT26i
[Sony Xperia S, Acro S, Ion] GiantAxe:
okey so i installed the latest release of CM10 for Nozomi, aftherwards wiped cache, dalvik and factory reset like normal. (atleast this was the case with CM9 i believe)

now it boots fine and all, it sees the wifi's from the entire neightbourhood, however: I cant connect to any of em. (we got 3 in our house, none of em works)

i probably did something wrong i guess. so anyone able to help me out.
[Sony Xperia S, Acro S, Ion] Poesini:
Im not judging anyone, but M1 didnt appear with nozomi either so :/

Anyway yeah we just have to wait
[Sony Xperia S, Acro S, Ion] realfelix:
Dont you understand that CM does only accept complete working builds?(CAMERA is a big blocker)
[Sony Xperia S, Acro S, Ion] Poesini:
I do understand, but i read first then talk

http://www.cyanogenmod.com/blog/cyanogenmod-10-m2

CyanogenMod 10 :: M2

October 11th, 2012

Cyanogen

124

Continuing with this month’s M-Series release, M2 is burning up CPU time on the build servers right now!

The M-Series is our monthly release series. The devices we build M for are essentially stable, and ready to be your daily driver.

We are building M2 for these devices:

Galaxy Nexus GSM (maguro)

Galaxy Nexus VZW (toro)

Galaxy Nexus Sprint (toroplus)

Galaxy S2 GT-I9100G (i9100g)

Galaxy S2 AT&T LTE (skyrocket)

Galaxy S2 T-Mobile (hercules)

Galaxy S (galaxysmtd)

Galaxy S B (galaxysbmtd)

Captivate (captivatemtd)

Galaxy S3 Sprint (d2spr)

Galaxy S3 VZW (d2vzw)

Galaxy S3 AT&T (d2att)

Galaxy S3 TMO (d2tmo)

Galaxy S3 US Cellular (d2usc)

Motorola Xoom (wingray/stingray)

Nexus S (crespo)

Nexus S 4G (crespo4g)

Galaxy Note AT&T (quincyatt)

Galaxy Note T-Mobile (quincytmo)

Google Nexus 7 (grouper)

LG Nitro HD (p930)

LG Optimus Black (p970)

LG Optimus LTE SKT (su640)

Sony Xperia Acro S (hikari)

Sony Xperia S (nozomi)
[Sony Xperia S, Acro S, Ion] mpttrung:
You guys see it

CHANGELOG

FXP142

CM9.1

- latest cm 9.1

- GSM Voice & Data (P)

- WIFI (P)

- RECOVERY (P)

- REBOOT to recovery (P)

- ROMMANAGER (P)

- LIGHTS (P)

- GPS (P)

- WIFI MAC fix (P)

CM10.0 - M2

- latest cm 10.0

- HDMI (T, S, ION, Acro S)

- Camera/Camcorder (T)

- Xperia Setting (T)

- Fix BT Mac (T)

Finally we have HDMI out and we also have M2 already :)). Waiting for link :D

Thanks CM devs !!!!
[Sony Xperia S, Acro S, Ion] 23qwerty:
So I just successfully installed this, I backed up my phone using the sony pc companion, but the restore fails, saying an error occurred during the restore operation and your content on phone might be corrupt, the backup file on your computer is unharmed and with that you can repeat the restore operation to correct any errors and to try rebooting the phone and restoring again, I've tried that to no avail. What's up here? Is an ics backup not compatible with jelly bean?
[Sony Xperia S, Acro S, Ion] Tintin69:
Mate, You're wrong with this, the Sony backup application has nothing to do with CM10, you should have used a third party app from the play store, backup you're data, install CM10, reinstall the third party app and restore with it.
[Sony Xperia S, Acro S, Ion] redmissile:
I have the same issue but sometimes if you press the power button the screen comes on and you can hang up.

Also some times the screen comes alive by it self if you remove the phone from your ear.
[Sony Xperia S, Acro S, Ion] championswimmer:
Proximity is faulty and is being fixed soon
[Sony Xperia S, Acro S, Ion] sixdaysandy:
Does the Camera/Camcorder working for the T in FXP142 infer that the T shipped with ION based camera drivers?

Or did the Dev's manage to compile some from scratch?

Does that give any hope for a proper fix for the S Camera ahead of a Sony JB Release?

Have to say that either way getting the HDMI output working is superb :)
[Sony Xperia S, Acro S, Ion] K900:
The T is still on ICS, drivers use ION, but are not compatible with the S.
[Sony Xperia S, Acro S, Ion] PhilAd:
nice process. especially for the - just released - Xperia T :)
[Sony Xperia S, Acro S, Ion] carlos118:
FDP 142 change log is up but the file is not. How long is it normally before we can access the file?
[Sony Xperia S, Acro S, Ion] RawkBob:
Usually Sunday or Monday . The next release changelog goes up when they release the file for the last one and is then updated over the week until its released.
[Sony Xperia S, Acro S, Ion] dedei:
DO I still need to fastboot boot.img or will CMW automatically install it??
[Sony Xperia S, Acro S, Ion] jerpelea:
Fxp142 released
[Sony Xperia S, Acro S, Ion] hmsdh:
Why no camera for sxs

why the bloody camcorder doesn't work for XSX and works for T....:crying:

waiting till camera works for SXS:fingers-crossed:
[Sony Xperia S, Acro S, Ion] mpttrung:
Why dont u use this one http://xdaforums.com/showthread.php?t=1920733. It works perfect on my cm10 rom :D
[Sony Xperia S, Acro S, Ion] GiantAxe:
kind of wondered about this, cause everytime someone asks about camera its: Sony has to give us the drivers for it.

however: No sony phone thus far has Jellybean yet

so how is it possible that some Sony phones already got ION camera drivers?

anyway, yay for M2 release

(i hope i can use the wifi now... whenever i try to connect to our own WPA/WPA2 protected router it just doesnt connect)
[Sony Xperia S, Acro S, Ion] Lervly:
I'm installed FXP141 , all basic function is work fine , many thank

but FXP142 , I'm got sound problem (all sound is silence , music can't play and got error , dialer hang when press number) , I'm try re-install , all wipe , all reset but ...still got this problem , Is anyone found like me???
[Sony Xperia S, Acro S, Ion] K900:
Sony uses the same code for ICS and JB drivers, and it's already been switched to use ion. ion is supported on ICS, and is actually the preferred allocator on ICS and up. pmem was deprecated in ICS and removed completely in JB. If we have a new ICS update, it should also contain those drivers if my idea of how Sony's development process works is correct.
[Sony Xperia S, Acro S, Ion] Djscarbo:
Does anyone have the problem of the screen flickering about every 10 seconds? is there any solution to this? thanks