yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] cronot:
Drivers, by definition, are software that's meant to "drive" (control and abstract behaviour) something, and this "something" in the context of an Operating System, is usually the hardware on a given device - and nothing more. Memory management is a logical concept that sits in the core of the system itself - it isn't related to hardware, at least not directly.

So no, your assertion is incorrect - whatever changes there is in memory management on Android 4.2, the fact that some of the nozomi drivers are closed source wouldn't make a difference to it - in this context, it's an apple to oranges comparison, it doesn't make sense. That's why I mentioned late in my post about the HAL (Hardware Abstraction Layer (thanks justmara :) )) - this is both the drivers and system libraries that are needed to make the hardware (display, audio, touchpanel, camera, etc.) work correctly, and my point is that the changes between Android 4.1 and 4.2 are mostly functional, not low-level, unlike with the transition from 2.3 -> 3.0/4.0 and 4.0 to 4.1, where there were important changes on the HAL - I can say that with a relative certainty because I followed the transition from CM10 to CM10.1 for the Samsung Galaxy S, and their device tree (as in the CM source) between these two versions are almost the same, most low-level changes went to the kernel, and even then, most of those changes were ported from upstream (i.e., not device-specific).

Even it there were tricky HAL issues to be worked around that having only blob drivers would make it harder, trust me, IT CAN be done, all it takes is that developers are willing and have the resources to do it. Don't trust me? Look at the Motorola Milestone community: there's very little source code for anything on the Milestone - the only thing that Motorola provided full sources for was the kernel, but until recently that didn't really matter much because, to make things worse, the bootloader for the Milestone is locked (i.e.: it couldn't run a custom-built kernel at all until very recently, until they found a very unconventional and creative way to do it) and yet, the guys there managed to cram fricking CM9 AND CM10 into it! Sure, it's not very usable - because, you know, it's a fricking 3 year old phone, that has specs way below the minimum required - but conceptually, it works fine, specially CM9 (there are people actually on it for daily use)
[Sony Xperia S, Acro S, Ion] justmara:
Hardware Abstraction Layer.
[Sony Xperia S, Acro S, Ion] Dillby777:
Illumination Bar Notification

Hi Guys

i'm trying to get the "Illumination Bar Notification" app working in CM10 FXP 201 i've followed this: http://xdaforums.com/showpost.php?p=31592702&postcount=1180&nocache=1 which was mentioned by rundgong to do. it appears it has worked for people as its recommended to do.

i've been playing around with the files a bit with stock and file's supplied. i can get all the files over to my phone just fine except the file "lights.semc.so" causes the led and illumination bar to not work and the screen brightness is at max.

when i check the logs when testing the app with this setup i get an error "Error opening '/data/lightservice.soc' (-2)"

if i remove the file everything works as normal and there isn't any errors when trying to test from the app.

has anyone else been able to get the app to work on CM or any idea why lights.semc.so messed with the phones lighting?

it would be nice to have this app functioning again. :)

edit: i have been searching the internet and the xda forums and there doesn't appear to be any more info apart from the above link.
[Sony Xperia S, Acro S, Ion] Jonzzon9:
Anyone else experienced that the "settings-button" changed to some weird icon?

Check the attachment!
[Sony Xperia S, Acro S, Ion] AliAlsuhail:
I think the sensor is messed up (hence it was disabled in stock ROM) and not a CM bug
[Sony Xperia S, Acro S, Ion] mzr7:
Isn't that the quick settings icon from 4.2?.
[Sony Xperia S, Acro S, Ion] memphis77:
My girlfriend has this icon since updating to 4.2.1 Never seen on 4.1.
[Sony Xperia S, Acro S, Ion] cronot:
[cittation needed], please. Not that I think that's impossible, but it's equally hard to believe that Sony could have botched a standard hardware component that almost every Android phone has, to the point of having that component disabled on their own - official - firmware. Is Sony so bad at hardware design that every other Android phone out there did that right except them?
[Sony Xperia S, Acro S, Ion] mirhl:
Auto-brightness WORKS

At least in the ics MIUI

This means it's not an hardware problem

you only need to "calibrate" sensor or preset i think
[Sony Xperia S, Acro S, Ion] RaymanFX:
WRONG. JUST PLAIN WRONG IN THE "HAL" PART

Sorry, but we need to get this straight: The transition from CM10 to CM10.1 may not affect all devices in the same way, but it actually affects our Xperia S in a lot of ways.

Nearly the complete HAL system (audio, display, gps etc) supported our msm8660 chip in JB (CM10).

Now, as of 4.2.1, only the msm8960 is supported and e.g. the display HAL is only meant to be compiled for that specific chip instruction set.

However, our device still contains the qualcomm msm8660 chip, and because of that we need to hack either the new HALs to be compatible with our chipset and kernel registers or we forward-port the old HALs. That's why I need so much time and effort to get my 4.2.1 CM10.1 port atleast to boot to the homescreen.

So, long story short, no support for our msm8660 chipset in even the CyanogenMod repositories in the future again. Ever. (99% sure about that)
[Sony Xperia S, Acro S, Ion] alexferdean:
So this means we won't have an official 4.2 update?

Xperia S
[Sony Xperia S, Acro S, Ion] cronot:
My point in the previous post is, if there's a HAL for the msm8660 in Android 4.1, it's conceivable that it could likely be used in 4.2 too with few changes. I've just looked around for detailed changelogs for 4.2.x, and in all of those I could find there wasn't any change that would even suggest a modification on the HAL; as opposed to 4.1 (from 4.0), where there are many more changes where it's clear the HAL was changed.

But whatever, I'm not going to argue over this, I'm just going to take your word for it for the time being, if only because I'm

not

too excited about 4.2 at this point, and because I'm too new in the community to pretend I know all about the nozomi - I'm mostly drawing from my experience with previous devices, so far. I'd actually be more happy at this point if we could get CM10 right - there's no point in thinking about CM10.1 if even CM10 still has many issues (and no authoritative explanation about the reasons, or even acknowledgement, for them).
[Sony Xperia S, Acro S, Ion] akkiannu:
That was known long time ago!

Does this mean that we have to wait a long time for 4.2 and still we will have a lot of non-working list? :(
[Sony Xperia S, Acro S, Ion] a4rocks:
Never thought I would say this but after everything that has been discussed, I hope someone from the FXP team issues a clarification for the same (even if it takes time out from all the dev work). I would not like to believe most of what has been said but if some of it is true, I am so running to buy myself a Nexus immediately. The (purported) future is quite grave and scary. In fact, I am sure everyone following the FXP builds would like most of what has been said to be simply quashed as talk but till the time there isn't any official word, I would brace myself for the worst :(
[Sony Xperia S, Acro S, Ion] Jonzzon9:
It's really weird, the icon suddenly changed when I was on FXP148. I thought it would get back to normal when udating to FXP201 but it's still the same.. :confused:

Well well, no big problem, just weird. :cool:
[Sony Xperia S, Acro S, Ion] ebnneo:
The only thing we can do is hope and pray that in the future skirt version 4.2.

Enviado de meu Xperia S usando o Tapatalk 2
[Sony Xperia S, Acro S, Ion] someone755:
Wait, if I get this straight;

-no JB 4.2 EVER --> no CM 10.1 --> no AOKP absed on it --> how in the name of [something] is that possible!?

So Sony made a flagship phone, made it developer friendly, and put hardware in it that 4.2 doesn't support!?

Sometimes I wonder why they'd do that... Maybe because they can't supports so many phone models at the same time, they just make it so that updating is impossible :(

I completely agree with a4rocks; if all this is true, I'm banning everything Sony out of my life!
[Sony Xperia S, Acro S, Ion] cronot:
Just to clarify: It can't be said for sure if Sony will provide an official firmware based on 4.2 because they themselves have yet to provide an official statement on this subject. What they have officially announced so far is that they'll update to 4.1, or at least that's what they've scheduled to do in the coming months - wether they'll honor this schedule remains to be seen. Regarding a 4.2 update, we'll have to wait for an official announcement from Sony which shouldn't happen before 4.1 itself is released - but I think the odds are very much that they won't provide any update to 4.2.

Boycotting Sony for that reason specifically (not providing an official Android 4.2 update) is not reasonable, IMHO. While I agree that's a sad state of affairs, the even sadder fact is that almost every other Android device manufacturer / brand out there does the same - there are few Android phone manufacturers that provide more than one major version upgrade for their devices (so if Sony manages to come out with 4.1, they'll already be a fortunate exception), many provide only one major version update for Android - *IF* they ever provide any (for certain devices it's provided only bugfix updates to the firmware, and no update at all to a major Android version). So if you're willing to ban Sony because of that, you'll have to do the same for every other Android manufacturer, except maybe the Nexus line from Google, which usually goes through 3 or 4 official (as in, released by Google) major Android versions update iterations - or at least that was the case at some point, I'm not really certain how's that going lately.

What was being discussed here is that, despite Sony not providing an official update to 4.2, it doesn't mean it can't be done non-officially, i.e. via CyanogenMod and AOKP. It may take a little extra work from the developers, but it's possible - the discussion so far was centered around how much work would it actually require.

Personally, I don't really care if Sony provides an update for 4.2, I *may* care a bit about 4.1 because it might make things a bit easier for the devs to fix things in CM, but it's not essential, because you know - we do have CM10 (Android 4.1) right now after all, even if there's a few issues to fix, and I still rather use it with the problems it has than use Sony's official firmware - actually, that's been true for every Android phone I've owned: Although they sometimes bring some unique features not available on non-official ROMs, I absolutely hate how the manufacturers completely pollute and make a travesty of the original / standard Android UI with their "Blur"s, "Touchwiz"zes or whatever they name their skins. I'd much rather have my Android UI and experience as Google idealized it, thankyouverymuch. That's why I've always used CM on every Android phone I've had.
[Sony Xperia S, Acro S, Ion] tomfan203:
R there anything not working?

Anything not working?

Camera full quality working?

HDMI working?

Project Butter working?

Illumination bar LEDs working?

Mobile Bravia Engine working?

xLoud working?
[Sony Xperia S, Acro S, Ion] mirhl:
only think isn'y working is FM radio and 1080p recording (720p works though)

project butter is fully enabled

bravia engine and xloud is sony's goodies not open sourced

if you want xloud, check acid mod

@cronot nice views
[Sony Xperia S, Acro S, Ion] m1st3r1:
HDMI is working fine in cm10. If u can't see ur launcher, maybe the launcher doesn't support landscape. Just head to the apps you want to play in HDTV (eg: mxplayer, some games), and they'll work fine.
[Sony Xperia S, Acro S, Ion] rc_enzo:
Have got to say, ever since I updated to 201 the kernel has become a lot more snappy than it used to be. Haven't had the need to flash another.

What I've read in this thread so far is that it is a huge challenge to build a fully functional CM10.1... I hope it will be figured out soon, I didn't buy this phone for sticking on older firmwares :P
[Sony Xperia S, Acro S, Ion] cronot:
Don't forget ALS (Ambient Light Sensor, for automatic brightness) and Proximity sensor, that acts erratically for many people (including myself). Check this page for a detailed list on what is/isn't working, and then look below for the addendum:

1080p video recording doesn't work (1080p+ photos and 720p video works);

Panorama photos doesn't work correctly;

Proximity sensor acts erratically (it usually doesn't turn on the screen when a call ends);

Automatic brightness doesn't work at all, seems to be disabled on CM10, no one knows why;

Everything else that @tomfan203 asked for that's not in this list works, except the Bravia engine and xLoud, which are Sony's proprietary features, so you should never expect them to be built-in on CyanogenMod ever, as it aims to be a distribution of Android as free from proprietary features as possible. It may be possible to do something like a Bravia / xLoud addon like the AC!D guys do with their AC!D engine, but it'll never be built into CM10 itself. Also, actually I believe the Bravia engine requires DRM, which you lose when you unlock the bootloader, so this is something you're only gonna get on Sony's official firmware anyways.
[Sony Xperia S, Acro S, Ion] mirhl:
light sensor works

maybe it's a bit inaccurate, but after you adjust its setting (via an app and/or via display setting) it's a bit better

i never noticed proximity sensor bugs (but i don't call so much..)

then, 1080p photo.. is a bit bad to say

we have 12MP photo, and that's it
[Sony Xperia S, Acro S, Ion] cronot:
Well, you may want to look on past posts then, because I'm not the only one with problems on auto-brightness. I did try that Disable Xperia Brightness app (which the Xperia S is not even explictly listed as supported, btw) - it does nothing for me as far as automatic brightness, the only thing it changes for me is the brightness range (the screen gets brighter; the default brightness range on CM10 is too low, which is actually another problem on CM10 I forgot to mention - the default maximum brightness on CM10 is about half you get when using that app), and even so, the app works very erraticaly - it has frequent ANR occurrences, and because of that you need a bit of luck for it to even get root previleges with Superuser. But again, it does nothing for automatic brightness on my XS, the "Sensor", "Screen" and "Buttons" values on "Settings / Display / Automatic Backlight / Edit other levels..." always shows "-1", no matter what I do, indicating the driver either is not returning a proper value, or isn't working at all.

Well, yeah, 1080p photo is actually a bit awkward term... What I meant was that any (vertical) resolution above 1080 pixels, up to the maximum (12MP) is available for photos, yes.
[Sony Xperia S, Acro S, Ion] xpla:
Does HD-Voice works with plain FreeXperia install or does it need specific CSC Files?
[Sony Xperia S, Acro S, Ion] Dillby777:
update fails

Hi Guys

I've tried to update to latest but it failed with the usual make_extf4fs failed on /dev/block/mmcblk0p12 error which corrupts the system.

I took a backup before i did anything but i since haven't been able to restore the data.

The only way i'm able to get it working again is to use the method here: http://xdaforums.com/showthread.php?t=1596285

which allows me to format system and from that recovery then install the new rom.

It's rather annoying having to do a complete wipe of the phone every time and then have to reset it all back up again.

Is this a known fault?
[Sony Xperia S, Acro S, Ion] nileshgr:
I have faced this many times. Install the original recovery. Flash the ROM and gapps. Then flash boot.img found in the archive.
[Sony Xperia S, Acro S, Ion] debriuman:
I'm do like that:

Before update to new CM10, backup all apps, and data TitaniumBackup

next wipe

next install update CM10

next install gapps

restore from TitaniumBackup data and apps

Always when do update I have errors:(, and I must do like that.
[Sony Xperia S, Acro S, Ion] lumanz:
Before the wipe flash Bin4ry recovery with fastboot. That's how I do it everytime.
[Sony Xperia S, Acro S, Ion] airwolf1544:
Before update to new CM10, backup all apps, and data TitaniumBackup

next install update CM10

(next wipe) no need - in case of errors only wipe cache and dalvik cache

(next install gapps) no need - only in case of errors

restore from TitaniumBackup data and apps
[Sony Xperia S, Acro S, Ion] ILoveAndroid77:
Checkout the App ButtonLED. It works for me with FXP202 :)

Illumination Bar blinks in default settings every 4 seconds for 1 second.

Tested missed calls so far. Not sure about text, mail, whatsapp, ...

http://xdaforums.com/showthread.php?t=1958939
[Sony Xperia S, Acro S, Ion] Dillby777:
the boot.img the one from the backup i took in CWM?

thanks for the info guys. i'll check them out next update time. slightly more involved than a quick update but it if saves me from having to reset my phone up again its a no brainer.

thanks again.
[Sony Xperia S, Acro S, Ion] Dillby777:
how did you get it to work? according to the thread it doesn't work on Jelly Bean yet.

EDIT: i was able to get this app working on CM10 so atleast those of us who liked the Illumination Bar Notification app can get back some of that functionality again

http://xdaforums.com/showthread.php?p=36725647&posted=1#post36725647
[Sony Xperia S, Acro S, Ion] cpuks:
Recovery is broken yet not repaired. Flash img via fastboot

Wysyłane z mojego Xperia S za pomocą Tapatalk 2
[Sony Xperia S, Acro S, Ion] lh95:
Sorry to be all hipster but is anyone else's instagram acting up? The photo editor is weird.
[Sony Xperia S, Acro S, Ion] nileshgr:
Known issue. Don't know if it's specific to CM10 or Jelly Bean in general (vaguely remember reading about the latter, but not sure).

---------- Post added at 11:38 AM ---------- Previous post was at 11:33 AM ----------

The boot.img which is present in the CM10 ROM you downloaded.

First flash original recovery (find the thread in this forum).

Install the zips.

Then use fastboot flash boot boot.img from your computer after extracting it from the archive.
[Sony Xperia S, Acro S, Ion] Dillby777:
ah cool, thanks for the clarification. :)
[Sony Xperia S, Acro S, Ion] rc_enzo:
You mean the one posted by Bin4ry? ( http://xdaforums.com/showthread.php?t=1596285)
[Sony Xperia S, Acro S, Ion] nileshgr:
Yes. That works for me, the recovery packed with the kernel doesn't seem to work.

Alternatively, you can use Nova Kernel, based on FXP kernel which has TWRP instead of CWM.
[Sony Xperia S, Acro S, Ion] rc_enzo:
Steps to a safe update (this is what I've just done):

Optional: Backup all your apps with Titanium, or do a full NANDROID backup

Boot your phone into fastboot mode.

Flash the FreeXperia Recovery (by bin4ry) with

fastboot flash boot recovery-nozomi.img

Then:

fastboot reboot

The system will automatically boot into the recovery.

Install the update from there.

Reboot the phone. No further action needed.

Thanks to nileshgr for giving advice.
[Sony Xperia S, Acro S, Ion] stavca:
yes, NOVA kernel is working when updating your ROM

first, wipe your cache and dalvik cache (no data loss, this is not needed but could avoid problems), then flash new FXP ROM and finally flash NOVA kernel, if you were using it before (I recommend this)
[Sony Xperia S, Acro S, Ion] Anan HS:
hey developer and testers...

im curious about something cuz its been quite some time since i left the firmware flashing.

i was juz wondering, is the gapps that ive used before still can be use for new FXP202 ?

or gapps has a new update... can you all please lend me a hand..
[Sony Xperia S, Acro S, Ion] jerpelea:
fm is working (scans and displays rds)

now we have to solve audio routing to have sound
[Sony Xperia S, Acro S, Ion] Evil_Sephiroth:
FXP201 atm (with nova kernel)....all work for me (don't know HDMI cause i don't use it)

Only random reboot first 2 day..now rock solid^^
[Sony Xperia S, Acro S, Ion] airwolf1544:
Wow. Thank you. Great news :thumbup:

Gesendet von meinem Xperia S mit Tapatalk 2
[Sony Xperia S, Acro S, Ion] zn533:
It sounds like you're close to getting FM Radio! That's good news.

Any ideas on getting the 'dark' theme to work in messaging? I know it's been brought up before. Has anyone tried the 'dark passion' fix with any joy?

A belated Happy New Year to you all!
[Sony Xperia S, Acro S, Ion] nileshgr:
Epic! Epic!

---------- Post added at 07:42 AM ---------- Previous post was at 07:12 AM ----------

You need to use gapps for jelly Bean.
[Sony Xperia S, Acro S, Ion] tupacsoul:
EPIC! Thank you guys!

---------- Post added at 03:37 PM ---------- Previous post was at 03:29 PM ----------

Then, if FXP solves FM radio, the only issues in this rom are...

- 1080p recording

- Autobright

¿Any more?
[Sony Xperia S, Acro S, Ion] cronot:
On my list, in addition to the above, I'd put:

- Erratic behaviour of proximity sensor (i.e.: screen sometimes doesn't turn on (or takes a very long time to do so) at the end of calls or during calls if you take the phone off from near your face to do something);

- Panorama photos.
[Sony Xperia S, Acro S, Ion] Akhil:
Guys, let me clear y'all one thing that last post by fxp wasn't about CM10 but was about CM10.1, So stop giving your list of whats not working...
[Sony Xperia S, Acro S, Ion] b3rx:
deleted
[Sony Xperia S, Acro S, Ion] ishamm:
In the change log for the next release, it says "latest cm10", what changes does that bring, or where can I find a log for it?
[Sony Xperia S, Acro S, Ion] //RF:
http://review.cyanogenmod.com/#/q/status:merged,n,z
[Sony Xperia S, Acro S, Ion] dmbardal:
Getting this while trying to install the ROM.

"symlink: some symlinks failed"

Any ideas ?
[Sony Xperia S, Acro S, Ion] elvirag:
It's okay, I had this too. All is fine...

Can't wait for fxp131, gonna explode!!!:victory:
[Sony Xperia S, Acro S, Ion] oojjii:
+1
[Sony Xperia S, Acro S, Ion] lilude56214:
Still waiting fxp131 cm10 to be released whereas is playing with the latest CM9

Not bad :D
[Sony Xperia S, Acro S, Ion] noob.fl:
Arg... i cant wait i cant wait i cant wait... I CANT WAIT... WHERE IS 131... *junkieshuffle* :silly::silly::silly:

sorry if ths thread has nothing to do with developement and just with a new JB fanboy :laugh:
[Sony Xperia S, Acro S, Ion] juzz|NOR:
Please. All unrelated talk either in General or Q&A thread.
[Sony Xperia S, Acro S, Ion] MantisEngine:
So as I can read on the thread, the few I've just read, CM9 is working really fine, does it? I mean, are there any bugs or something?

And for CM10, well, there are bugs right?

I just want some summary feedback from someone, I've already read the thread, and I just wanna know if there is any problem with CM9.

Thanks :D:cyclops:
[Sony Xperia S, Acro S, Ion] elvirag:
SO WHY NOT PUBLISH THIS IN CM9?!:confused::confused::confused:

Damn, I'm subscribed and every post makes me jump with joy... So please, people!

Till FXP updates this thread with the number 131,

I don't wanna hear a peep ouutta ya'll! :highfive::p
[Sony Xperia S, Acro S, Ion] ej_424:
What big improvements/fixes is FXP 131 going to bring. I'm pretty excited as well, and still on ICS due ot the bugs the current build has. Coming from a Galaxy Nexus I really want JB back :) Love this device though.

I heard the reason for the lack of development is currently due to the locked bootloaders is this true? I guess most branded phones in the UK and what not can't be ulocked. Luckily I paid a pretty penny off a US Site and have a unbranded fully unlocked phone :).
[Sony Xperia S, Acro S, Ion] colossus:
Stop spamming this thread with useless posts Guys, if you have nothing constructive to post then do not bother!