yashsingh1/xdaforums huggingface dataset:
[Nexus 4 Q&A, Help & Troubleshooting] silvagroup:
My wife destroyed her display. Did same but gyro works fine but proxy is the problem. Work around so far is to set power button to end calls becasue screen just goes black when making/receiving calls kind of makes phone useless if you can't see screen.

I too have taken it apart several times and still nothing. Next plan is to find a new sensor unit and replace it.

From what I have been able to see in all my searching the proxy is extremely sensitive any deviation in placement, smuge on unit or display, minor deviation on color of display, screen protector, any interference from skins can affect it so check all those also.

In one of the threads on the Galaxy Nexus there is a patch to turn off sensor and there is mention of app in market that does the same, haven't tried yet have to get phone from wife to try, could be possible solutions also.

Will post back with findings as I get to try them.

Found great app in market Sensor Kinetic Pro shuts off proximity sensor or any other sensor no more problem with black screen after making calls. Still going to try replacing sensor however found it on Amazon less then $5.00.
[Nexus 4 Q&A, Help & Troubleshooting] dhaub:
Somewhat comforted to see others are also having the same problem... I recently replaced my nexus 4 screen only to have my proximity sensor fail on me too. Interestingly enough, i disassembled my phone multiple times to test if the sensor still works, turns out it does, but it is super sensitive. In my first experiment I had the sensor dangling out of the socket to see if it was still receptive to light, it worked perfectly - I used my hand as a 'face-simulator' to test for sensitivity. I then tried to place it back in the rubber grommet with the grommet seated firmly in the socket and what I found was that it worked, so long as there was only limited pressure on the enclosure. For example, it only works when there are no adjacent screws (for the plastic motherboard cover) applying pressure in the nearby area. I thought I could live with that, but then I tried putting the rear plastic cover back on and,... back to square one, dead screen on-call. I figure it has something to do with either pressure sensitivity or perhaps the pressure from the screws or the rear cover pushes the sensor too close to the glass?

Anyway I'd be keen to see if replacing the audio jack will actually fix the problem, any of you guys had any success with that? Meanwhile i'm going to just use the power button for ending calls. Any tips for how to use the speakerphone during a call?

Cheers fellas.
[Nexus 4 Q&A, Help & Troubleshooting] silvagroup:
New sensor arrived yesterday changed out my wife's non functioning sensor and new one working great. Old sensor was bad !!!! She had dropped the phone several times and last accident she unintentionally threw it. Suggest no one do that :)
[Nexus 4 Q&A, Help & Troubleshooting] dhaub:
New sensor arrived the other day, I have since swapped out the old one, everything works great now!
[Nexus 4 Q&A, Help & Troubleshooting] chamilun:
17

whered u get the sensor?
[Nexus 4 Q&A, Help & Troubleshooting] btack:
I know this is old but I'm having the same issue. How did you guys make out? Were did you get the sensor? Saw one on ebay $109 seems pricey
[Nexus 4 Q&A, Help & Troubleshooting] chamilun:
I put a case on mine and it started working. It always would work if i put a bit of pressure on different parts of the phone. So im not sure if bad contact on sensor or if more some type of alignment issue. But it does work now. speakerphone is terrible since cracked screen tho..
[Sony Xperia S, Acro S, Ion] nelikp:
Credits to

[MENTION=222278]FREE[/MENTION] Xperia Project [MENTION=4193338]CyanogenMod[/MENTION] [MENTION=3463426]RaymanFX[/MENTION] [MENTION=3507070]ganeshbiyer[/MENTION] [MENTION=834547]letama[/MENTION] [MENTION=3996553]kin912[/MENTION]

@PA team [MENTION=535343]all[/MENTION] user who keep supporting

ROM 4.2

this still on very first phase

Source

https://github.com/OpenSEMC

uploading

updating soon.....

View attachment 2212660
[Sony Xperia S, Acro S, Ion] nelikp:
For now on...

got permission to port deedwar roms for XAS

it is:-

1- Beanstalk

2- Jellybeer

Bug list for now:-

1-no network at all

2-camera blank on potrait mode (still can capture)

**camera working good on landscape mode

3--galery blank on potrait mode (still can capture)

**galery working good on landscape mode
[Sony Xperia S, Acro S, Ion] nelikp:
Reserve for changelog
[Sony Xperia S, Acro S, Ion] nelikp:
and another onemore for future
[Sony Xperia S, Acro S, Ion] pharix:
Another good work.
[Sony Xperia S, Acro S, Ion] wyymcy:
-no signal (GSM) at all

-no extSD present

:p:p:p
[Sony Xperia S, Acro S, Ion] kin912:
no signal (GSM) at all.Your phone is a pad?
[Sony Xperia S, Acro S, Ion] ganapathyraman_s:
I have used PA 2.53 and 3.10 on my ion. Infact the first Custom ROM I used on my Ion once I learnt unlocking, flashing pre-rooted ftf, adding recovery and backing up my working stock ROM was PA 2.53. Both the versions of PA ROM had the chronic problem of GSM and Data signal drop and overheating of device. I am skeptical of trying any PA based ROM because of my previous experience. However, i will be happy to try and test once the basic bug of GSM not working is solved.
[Sony Xperia S, Acro S, Ion] Toledo_JAB:
[MENTION=4312703]nelikp[/MENTION],

I am giving you a friendly reminder that all ROM threads for releases need to be GPL compliant.

The ROM thread OP needs to contain a link to the source used in compiling a working KERNEL.

If you use a stock kernel, then link the stock source download.

If you have any questions, just PM me.

~JAB

Moderating from my Xperia ION on 4.1.2 & RooTED by DooMLoRD.
[Sony Xperia S, Acro S, Ion] peddarson:
can you add a few more information to this Rom please? is it really android 4.2???
[Sony Xperia S, Acro S, Ion] kin912:
I think the problem is in the kernel.
[Sony Xperia S, Acro S, Ion] goodnightPal:
Where did u get the 4.1 aoba kernel source?
[Sony Xperia S, Acro S, Ion] kin912:
The kernel is lt26 mod for lt28.
[Sony Xperia S, Acro S, Ion] goodnightPal:
I see could u give me a guide or source I would try port sg
[Sony Xperia S, Acro S, Ion] sorgo:
The SONY open source archive is:

http://developer.sonymobile.com/downloads/opensource/

This is the XS 6.2.B.0.200 source

http://developer.sonymobile.com/dow...es/open-source-archive-for-build-6-2-b-0-200/

I don't know if this is what you're looking for
[Sony Xperia S, Acro S, Ion] kin912:
You can fix the bug of baseband?:eek:
[Sony Xperia S, Acro S, Ion] goodnightPal:
I don't know I just try understand and build it if I can
[Sony Xperia S, Acro S, Ion] kin912:
The sources of lt28 have not been rolled out yet.
[Sony Xperia S, Acro S, Ion] twent4:
@nelikp

Thanks for this build but is there any chance we can just get CM10.1? I keep seeing many CM derivatives even though i wasn't certain FXP has a working up-to-date kernel done... so how come Slim and PA keep popping up without a stable CM build?

thank you
[Sony Xperia S, Acro S, Ion] nelikp:
actually this is port from JellyBeer for XAS and base on OpemSEMC for ION BETA

Rom in my hand but I can't share it because [MENTION=3463426]RaymanFX[/MENTION] didn't give permission to share this port..

he only give permission if I compile from his source..

but I got really big headache when keep getting error

and maybe I can't share it at all..

sorry about that

RaymanFX working on his kernel to get working GSM

if u wanna feel the 4.2 android on your ION, feel free to download from "GENERAL SECTION " and look at openSEMC for ION
[Sony Xperia S, Acro S, Ion] nelikp:
with a tons of help from great Recognized Contributor [MENTION=3507070]ganeshbiyer[/MENTION]

i able to build opensemc source by RaymanFX and his team

will try to get permission from JellyBeer for XAS developper to release this port soon

credit to

Ganeshbiyer for a single second he read my pm, replied my pm.

assist any single problem on my compiling season

any singgle word from ganeshbiyer

RaymanFX and the team for the OpenSEMC source

FXP the really big name in this industry

CyanogenMOD for CM10.1 source
[Sony Xperia S, Acro S, Ion] kin912:
Read my replys in fxp's cm10 thread,you will get the good news.;)
[Sony Xperia S, Acro S, Ion] nelikp:
i seen it last two days (correct me if i'm wrong)

told to ganeshbiyer

he told me the fix ready on opensemc thread (i don't know which thread (XS/XAS/General section)

i meant no network fix
[Sony Xperia S, Acro S, Ion] kin912:
You read first.http://xdaforums.com/showpost.php?p=44878004&postcount=453

I think [MENTION=3507070]ganeshbiyer[/MENTION] can fix it.
[Sony Xperia S, Acro S, Ion] nelikp:
yess...

i saw ganeshbiyer post on miui

he did it again!

finally we already have 4.2.2 without """"badbug"""

maybe it just a smallbug

or zerobug cm10.1
[Sony Xperia S, Acro S, Ion] nelikp:
[MENTION=834547]letama[/MENTION]

i can pm you the logcat.txt

(because pm text can more than bla bla bla)

error while pm

here i attached the log

View attachment logcat.txt

i run on android terminal (teminal.apk)

su

logcat -b radio *:v
[Sony Xperia S, Acro S, Ion] letama:
Thanks! I prefer in a thread anyway, it's easier to browse back and forth and you can attach files...

You obtained a proper log. However, it doesn't look good, I don't see anything easy to solve... We'll have to dig deeper. I need you to do few things:

1) in terminal or with adb, type getprop | grep svc and give me the result.

2) I need another log, this time with this command:

logcat -b radio -b system -b main *:v

Let the device boot and wait for something like 30 seconds after it has booted before taking the log.

3) after you obtain this one, do this:

setprop persist.radio.adb_log_on 1

then reboot and take the same log as 2).

these 2 logs will be big, so you may want to redirect to a file on sdcard and grab it from pc:

logcat -d -b radio -b system -b main *:v > /sdcard/full_log.txt
[Sony Xperia S, Acro S, Ion] nelikp:
i will try to get the required logs
[Sony Xperia S, Acro S, Ion] Najuto9tail:
This is based on cm10? So locked bootloaders can not even try to use it. I wish somebody could hack the bootloader to unlock it on any ion device.
[Sony Xperia S, Acro S, Ion] g.man.7489:
based on cm10.1
[Sony Xperia S, Acro S, Ion] kin912:
Let me do this from opensemc rc1.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Just for information:

http://i-miss-erin.blogspot.com/2009/11/radio-layer-interface-in-android.html
[Sony Xperia S, Acro S, Ion] nelikp:
u learned somethin'
[Sony Xperia S, Acro S, Ion] nelikp:
run the 2nd promp

morethan 6hours terminal still keep running..

please help to get the logcats
[Sony Xperia S, Acro S, Ion] g.man.7489:
I've known this before. just somthing strange to me with new this device "ION"

Hope that you will release this 4.2.2 soon and 4.3 maybe :p (4.3 is on NEO now)
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
@letama

Logs as per request

Set 1:

Full log is huge so attaching it
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
@letama

Set 2:

Full log is huge, so attaching file

full log:
[Sony Xperia S, Acro S, Ion] kin912:
[MENTION=4312703]nelikp[/MENTION] [MENTION=834547]letama[/MENTION] [MENTION=3507070]ganeshbiyer[/MENTION]

There is something wrong with the kernel of opensemc,I can not get the logcat [MENTION=3507070]ganeshbiyer[/MENTION] get it now!
[Sony Xperia S, Acro S, Ion] nelikp:
yess...we work better together!

ganesh..lucky i stop the terminal, because i get wrong log...too many line something like "missmatch"
[Sony Xperia S, Acro S, Ion] kin912:
[MENTION=3507070]ganeshbiyer[/MENTION] [MENTION=834547]letama[/MENTION]

He just need the log of radio,system and main.

adb logcat -d -b radio -b system -b main *:v > C:\full_log.txt
[Sony Xperia S, Acro S, Ion] letama:
Thanks for the logs!

Hum, you shouldn't need 6 hours to get the log, I guess the command was wrong or something went bad.

Anyway, your problem is quite simple: ril daemon is crashing bad.

Here is what I need you to do next:

cat /init.rc

and give me the result

Next, I need you to do this:

getprop | grep ril

and give me the result

Next do this:

stop ril-daemon
/system/bin/rild

and tell me if it shows something

Next do this:

strace -fFv -s 1024 /system/bin/rild

and give me the result

Sorry for the amount of stuff :) I'm trying to limit the round-trips...
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
cat /init.rc

getprop | grep ril

stop ril-daemon

/system/bin/rild

shows the same output as the strace command below

strace -fFv -s 1024 /system/bin/rild
[Sony Xperia S, Acro S, Ion] nelikp:
too fast too furious!

i just need to restore to backzax before i can mount sd to pc...

:fingers-crossed:
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
My Mistake.

File too large .. attached it.
[Sony Xperia S, Acro S, Ion] letama:
Good! Thanks.

Now, can you try to reboot, then

chmod 666 /dev/diag
stop ril-daemon
start ril-daemon

does it start showing pin dialog ?

If not, can you do the strace again:

stop ril-daemon
strace -fFv -s 1024 /system/bin/rild
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Did not show pin dialog.

Attached the log below.
[Sony Xperia S, Acro S, Ion] letama:
Ok, rild is going further, so I believe that before trying to diag further, you should edit your /ueventd.semc.rc.

You need to add a line like this:

/dev/diag 0666 root root

This file is in kernel initramfs, you have to rebuild it or unpack repack kernel as you prefer.

file should be in CM tree in something like:

device/sony/nozomi/config/

To make sure that it works, a ls -l /dev/diag after reboot should give you this:

crw-rw-rw- root root 241, 0 2013-08-26 11:46 diag

You need rw-rw-rw, not rw-r-r like you probably had before.

After it's done, I'll need a logcat -b radio *:v again.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
@letama

Thanks for your time.

I will do this when I reach home. (@office right now)

@nelikp

Could you do it now. Build the boot.img again as per below.
[Sony Xperia S, Acro S, Ion] nelikp:
I can't found

opensemc/device/sony/aoba/config/ueventd.semc.rc

still looking for it maybe somewhere else

using the search button

==================================

edit

==================================

found 5 files for ueventd.semc.rc

and added the line like your request

now cleaning and rebuild entire rom...

another 200 minutes it should be ready to check..
[Sony Xperia S, Acro S, Ion] nelikp:
[MENTION=834547]letama[/MENTION]/ [MENTION=3507070]ganeshbiyer[/MENTION]

how to set permission on the source tree?

or it can simply set by rootxplorer after the boot?

============================

edit

============================

just right click/properties/permission tab/

and set to

read write

read write

read write
[Sony Xperia S, Acro S, Ion] pharix:
Good work brothers. Just checking this thread every 5 minutes to see the progress.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
the ueventd.semc.rc you need to change is in

device/sony/fuji-common/rootdir
[Sony Xperia S, Acro S, Ion] nelikp:
yess after clean and rebuild using your setup.tar.gz

it shown only one ueventd.semc.fc

(on your given directory)

and here the line i added
[Sony Xperia S, Acro S, Ion] letama:
Ah, yes, forgot that cm has splitted device trees... sorry.

So, how is it doing now ?

ls -l /dev/diag is ok ?

Can you get me a logcat -b radio *:v ?
[Sony Xperia S, Acro S, Ion] nelikp:
i don't know how to compile "kernel only"

now compiling entire "rom+kernel"

it take arround 200 minutes

I will run terminal when it boot later

and keep you update
[Sony Xperia S, Acro S, Ion] letama:
Oh, sorry, thought it was done. No problem, let me know, we'll carry on...
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
No need to build whole ROM.

Just do

. build/envsetup.sh

lunch

mka bootimage -j4
[Sony Xperia S, Acro S, Ion] nelikp:
yess boss

this is what i need..

did your arrived at home sir?
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Another 90 mins.
[Sony Xperia S, Acro S, Ion] nelikp:
i don't understand this

ls -l /dev/diag is ok ?

so after the step given before compiled the kernel

flash the rom+new kernel

then get the logcat -b radio *:v

is it correct??
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
ls -l /dev/diag
[Sony Xperia S, Acro S, Ion] nelikp:
very happy look you arround boss...

terminal still keep running on my phone

now it look something like this

E/RILD ( 7574) xxxxxxxxxxxxxxx

E/RILD ( 7575) xxxxxxxxxxxxxxx

E/RILD ( 7576) xxxxxxxxxxxxxxx

E/RILD ( 7577) xxxxxxxxxxxxxxx

E/RILD ( 7578) xxxxxxxxxxxxxxx

E/RILD ( 7579) xxxxxxxxxxxxxxx

E/RILD ( 7580) xxxxxxxxxxxxxxx
[Sony Xperia S, Acro S, Ion] nelikp:
I got this

crw-rw-rw- root root [COLOR="Red"]240[/COLOR], 0 1970-01-30 00:16 diag
[Sony Xperia S, Acro S, Ion] letama:
Ok, thanks for the logs!

The /dev/diag is ok now. From now on, I don't need the "strace" and "getprop | grep ril".

It still has issue, so now, could you get me:

adb logcat -d -b radio -b system -b main *:v

?

Wait a bit after boot to take it, something like 60 seconds, then take the log.

Thanks!
[Sony Xperia S, Acro S, Ion] nelikp:
sorry if i late

it still keep running

View attachment radio.txt

now we go to next log reading
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
adb logcat -d -b radio -b system -b main *:v

logcat attached
[Sony Xperia S, Acro S, Ion] nelikp:
this what i get

View attachment new.txt
[Sony Xperia S, Acro S, Ion] letama:
Ok, thanks.

rild is still crashing, but we can't strace it the way we did before as it crashes a bit too far in the process.

Here is what you can try

1)

setprop persist.radio.adb_log_on 1

sync

then reboot

then get me same logcat.

2) your misc_ta daemons are looking weird, can you try replace these files:

/system/lib/libta.so

/system/lib/libta_rmt_clnt.so

/system/bin/ta_reader

/system/bin/ta_rmt_service

/system/bin/tad

/system/bin/updatemiscta

with one coming from Sony JB firmware for ION ?

While you're at it, replace also

/system/bin/qmuxd

/system/bin/secchand

/system/lib/libqc-opt.so

/system/lib/libqcci_legacy.so

/system/lib/libqdi.so

/system/lib/libqdp.so

/system/lib/libqdutils.so

/system/lib/libqmi.so

/system/lib/libqmi_client_qmux.so

/system/lib/libqmiservices.so

/system/lib/libqservice.so

/system/lib/libril-qc-qmi-1.so

I don't know if RaymanFX did a specific proprietary for ion as they are so similar, but there could be subtle differences... I don't know.

Then sync, reboot and give me a full log and a getprop | grep svc to see if I see progress.

If nothings goes, next step could be complicated.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Already from Latest JB firmware. (I Added them)

Added these libraries

Phone does not boot.

main2.txt after doing

main3.txt

edit:

After about 10 mins it booted automatically.After the boot logo it was on blank screen for about 10 mins.

Main4.txt - after booting
[Sony Xperia S, Acro S, Ion] letama:
Strange... I presume the problem is there, no reason that using proprietaries from Ion breaks so bad. I guess we are on right track, we should get the proper combination of proprietaries from Ion instead of using XS ones.

Can you try one thing, add /system/bin/rild on top of the one I gave you ?

BTW, main2 is showing that ril daemon is trying to talk to radio subsystem but never go further.

I'll try to unpack ion rom to see difference on my side...
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
I had synced from opensemc git hub repo. I don't know if RaymanFX has updated the github. So looked into aoba-vendor-blobs.mk and took all the files from .211 latest ion firmware.
[Sony Xperia S, Acro S, Ion] letama:
Sounds like a good idea, and strange it crashes. Can you try strace again ?

stop ril-daemon
strace -fFv -s 1024 /system/bin/rild
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Attached the log
[Sony Xperia S, Acro S, Ion] letama:
Ok, there is another problem, with qmuxd this time.

You have this:

[pid 3437] connect(14, {sa_family=AF_UNIX, path="/dev/socket/qmux_radio/qmux_connect_socket"}, 44) = -1 ECONNREFUSED (Connection refused)

It should be this:

[pid 10606] connect(14, {sa_family=AF_UNIX, path="/dev/socket/qmux_radio/qmux_connect_socket"}, 44) = 0

[pid 10606] recvfrom(14, "▒\0\0\0", 4, 0, NULL, NULL) = 4

[pid 10606] pipe([15, 16]) = 0

Can you do a ls -l /dev/socket/qmux_radio ?

And show me the init.semc.rc ?

and a ps ?
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
I will post it in the morning. My net is down at the moment.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
radio

init-semc.rc
[Sony Xperia S, Acro S, Ion] letama:
Ok, nothing obvious there :(.

Let's go strace way then...

Can you:

1) strace startup:

stop ril-daemon
stop qmuxd
strace -fFv -s 256 /system/bin/qmuxd

It will probably not stop, just do a Ctrl+C like 3/4 seconds after launching strace

2) strace in-place

start qmuxd
ps | grep qmuxd

Note qmuxd pid (first numeric column)

next, open another shell window, in one do:

strace -Ffv -s 256 -p <pid>

when this one is running, go to the other window and do:

start ril-daemon

Do a ctrl+C after few seconds.

Last one, give me the result of "ps"

Thanks!
[Sony Xperia S, Acro S, Ion] nelikp:
i left for a last few step...

i'm sure that i will make you confuse if i give the next log
[Sony Xperia S, Acro S, Ion] letama:
That's ok, you can try... You both doing logs is good, you're probably not exactly at the same dll versions as ganeshbiyer and it's interesting to be able to compare behavior.
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
Here you go,

1) strace_qmuxd.txt

2) strace_qmuxd1.txt
[Sony Xperia S, Acro S, Ion] nelikp:
ok will try it out
[Sony Xperia S, Acro S, Ion] letama:
Ok, it keeps looping on /dev/sdioctl0 which is strange. I don't have sdioctl0 either, but in mine, it also opens /dev/smdcntl0

Can you do me a ls -l /dev/smd* ?

and maybe the content of ueventd.semc.rc ?
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
ls -l /dev/smd*

what is this libreference-ril.so... it is referred in rild.c source.
[Sony Xperia S, Acro S, Ion] nelikp:
ls -l /dev/smd*

View attachment 2216392
[Sony Xperia S, Acro S, Ion] letama:
it's the reference ril, a kind of "demonstration" version of a ril dll. rild will load a ril dll, default would be libreference-ril.so if you don't have a rild.libpath.

I'm a bit out of ideas now, I have no clue of why qmuxd doesn't even try to open /dev/smdctl0

Here is what we have on yours:

Here is mine:

This is almost at startup, and we don't see any syscall that would explain the difference.
[Sony Xperia S, Acro S, Ion] nelikp:
just my 2 cent opinion...

Is it need to add a line into ueventd.semc.fc just like before or somewhere else
[Sony Xperia S, Acro S, Ion] ganeshbiyer:
In the build.prop there is this line

rild.libargs=-d /dev/smd0

is it okay

I suppose it is.
[Sony Xperia S, Acro S, Ion] letama:
Yes, I have the same one and I believe it's ignored... smd0 access is obsolete now.
[Sony Xperia S, Acro S, Ion] kin912:
[MENTION=834547]letama[/MENTION] [MENTION=3507070]ganeshbiyer[/MENTION] [MENTION=4312703]nelikp[/MENTION]

I think the bug is in kernel.Because ganeshbiyer fixed the ril bug also can be used in XS.
[Sony Xperia S, Acro S, Ion] goodnightPal:
I dont understand. You sad. If we get the jb source than possible to port cm10.1. So what
[Sony Xperia S, Acro S, Ion] letama:
It could be yes. What I would do is grab 211 kernel source code for XS and Ion and compare source code to see what differs. Kernel should be similar and it should be relatively easy to pinpoint the differences.

I don't have HD space and time to do this, but if someone do it, I can help to track it down.

Here is what I would do:

Download source codes for both.

Unpack Ion in one directory.

Create a git in it (git init ; git add . ; git commit -m "Ion 211 kernel")

Unpack XS in the same directory.

Do a git status and report here.

Do a git diff and post it here.