yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] Gallardo994:
[MENTION=3463426]RaymanFX[/MENTION], if we speak about HAL to use, I'd certainly say that the best choice is to continue chocolate-like versions development with CAF.

CAF is definitely much smoother and it gives a way better experience. It also doesn't cause *a lot* of problems (unless you want to play a heavy 3D game). So far, we don't want one more choppy stock with just a look of CM, do we? :)

Powered by TVR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] darkado:
legacy if it's fixable would be much better cause from what I understand, chocolate involves a lot of jury rigging.
[Sony Xperia S, Acro S, Ion] Forzaferrarileo:
Hey [MENTION=3463426]RaymanFX[/MENTION], can ypu explain me the differences between msm-3.4 branch and jb_chocolate? The.first one seems to be more updated
[Sony Xperia S, Acro S, Ion] mirhl:
should be better explained here
[Sony Xperia S, Acro S, Ion] switzerland92:
Maybe one quick poll would better express public opinion here? :D
[Sony Xperia S, Acro S, Ion] mirhl:
I think that this shouldn't be democratic

But more "meritocratic"

I mean.. the opinions of devs, imho, are way more valid than normal users' ones
[Sony Xperia S, Acro S, Ion] Trevor Chuah:
Thanks for the answer.

Because as I read your previous posts, you sounds like wont touch about these blobs directly from Sony since it is not open.

Thank you.
[Sony Xperia S, Acro S, Ion] Peter_95:
I choose legacy. It will save your time, and don't need to do it twice ..... :) and it can be used more easily on every android that will be released until android 13 sneaky sandwich .... lol .... i vote for legacy .....
[Sony Xperia S, Acro S, Ion] mat2057:
Hey, thank you for you answers. I'll take a look at it when I'm back from y short "summer break".

Did anyone experience what I noticed about the CPU frequency and scheduler with last CM sources and chocolate kernel? I can provide logcat when I'm back if you want [MENTION=3463426]RaymanFX[/MENTION]

In my opinion, if you/we can find out what's wrong with the current legacy version, I definitely vote for this version.
[Sony Xperia S, Acro S, Ion] rolex0815:
Have you ever tried the STOCK JB?

I mean because maybe you have a quite higher demand on "stutter-free" as e.g. Sony has. :)

I'm running now STOCK (because of battery, it's simply great) but I have dualboot and could compare against your current version.

STOCK ROM has also some lags when switching homescreens, when switching in launcher a.s.o but for *me* it's not a big deal.
[Sony Xperia S, Acro S, Ion] Gallardo994:
Do we want one more stock-like laggy rom? I guess not.

Powered by TVR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] mirhl:
I'm running stock jb too

But the lag you are referring to, aren't the same rayman is

Random (rare) lags in the homescreen are normals

But if for example you try to pull up and down fast the status bar, you would notice that stock is WAY more sticked to your finger (at least compated to legacy versions, chocolate is claimed to have fixed this)

Then, the problem it's not only the notificiation/status bar... but of course this only a sympton of something bigger and more code related..

I hope you will understand
[Sony Xperia S, Acro S, Ion] ishamm:
will this rom recieve the CM Focal Camera app when it drops? looks very impressive!
[Sony Xperia S, Acro S, Ion] Gallardo994:
When CM sources are updated, should be.

Powered by TVR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] switzerland92:
Is there a possibility to implement HAVS or SVS sysfs in 3.4 kernel?
[Sony Xperia S, Acro S, Ion] RaymanFX:
I already did it for msm8x60. But I want to have working video drivers prior to doing anything else.

https://github.com/OpenSEMC/android...mmit/0be76273651f3b5257cc6dc8838874752ff77b5e

BTW, funny things. Looking at Android 4.3, me might be forced to use the legacy display HAL, because as Letama discovered already, mako dropped support for adreno 2xx blobs and I highly suspect CAF to do the same for 4.3/mr2, meaning absolutely no more msm8660 support, so the only blobs we could possibly use would be legacy ones, at least for adreno concerns.

I don't know if a mr1/mr2 video drivers solution with legacy gpu drivers would work though.. But it sounds messy and will be for sure.

Anyways, working my ways through the latest CAF code to see what I can get. This time I payed more attention to Sony's modifications than I did before, still using the mako gpu/vidc drivers though.
[Sony Xperia S, Acro S, Ion] switzerland92:
Oh, so there is sysfs support... I was confused because I use IncrediControl app for controlling voltages and my device can undervolt with very good results (even below 700mV on lowest CPU state).

IncrediControl throws error because it can't find any sysfs support in kernel.

Maybe if it's possible to put

#define MIN_VDD_SC 800000 /* uV */

on 700000 or even a bit less?

EDIT: I'm just throwing ideas for future, this is not a demand at all, just an advice :) Love your work!
[Sony Xperia S, Acro S, Ion] ny-hardcore:
I build legacy 2 days ago, almost everything works except video file playback. OMX complains about bad parameter in logcat. Did I mess something up? I did a clobber and redownloaded vendor/sony but problem still exists. Or is this not working at the moment?
[Sony Xperia S, Acro S, Ion] cronot:
Well, I hope you're not spending a lot of time with this... See this. So, it seems root is not so smooth right now, and if you're planning to release 4.3 so soon, be prepared to have some angry users screaming at you because of root apps suddenly stop working; including me (ok, I'm just kidding :) ). But I mean, let Steve and the guys work out the kinks first, and when CM 10.2 has less surprises up its sleeve, then go for it.

Anyway, my 2¢. Cheers!
[Sony Xperia S, Acro S, Ion] switzerland92:
I see GitHub is updated with new source files, does that mean we can expect soon RC1-chocolate-vol-2 ? :D

I'm asking because I would like to reflash ROM (deleted wrong sys. apps) so I don't know should I wait or not...
[Sony Xperia S, Acro S, Ion] ny-hardcore:
The source is in a buildable state. I build a chocolate-staging kernel and AOKP ROM this evening.

Feels fast and fluid. Launcher draws really smooth and launching non backgrounded apps is real smooth

Still some issues with instaweather (black picture) and camera preview flickers and looks like its redrawn in rectangles. Will provide logcats if needed.

Overall very impressed with the progress that is made! Hats off to [MENTION=3463426]RaymanFX[/MENTION]
[Sony Xperia S, Acro S, Ion] alex.tartan:
Is the 1px offset gone? :fingers-crossed:
[Sony Xperia S, Acro S, Ion] RaymanFX:
It is :) took me quite some time, but now virtual/physical display mapping is working perfectly.
[Sony Xperia S, Acro S, Ion] Trevor Chuah:
Previously, I was wondering how the 1 pixel offset looks like (I don't have this issue previously).

But now I experienced it, after it auto reboot when using AirDroid.

But my pixel offset is a bit different with the pixel offset issue mentioned in previous posts...

Mine is Vertically, which means the right ( 1 x 1280 ) vertical line is offset to the left.

Special phone. Hehe
[Sony Xperia S, Acro S, Ion] ^Reloaded^:
does the battery life in chocolate-opensemc kernel is good????
[Sony Xperia S, Acro S, Ion] ishamm:
Just a heads up to people on this rom, Focal, cm teams new camera app, works pretty damn smooth on this! I'm sure when rayman includes it properly is going to be be super smooth!
[Sony Xperia S, Acro S, Ion] darkado:
where to get that app?
[Sony Xperia S, Acro S, Ion] someone755:
I guess you have to wait for Steve and the CM team to officially release it into the CM source and thus the CM builds.

Or are they already there, haven't checked...
[Sony Xperia S, Acro S, Ion] cronot:
It's already on CM 10.2 nigthlies. I don't think they'll include it on CM 10.1 at this point though, so you'll probably have to inject the apk (and whatever dependencies it might have, I haven't checked) manually for CM 10.1.

Edit: Correction: It's on CM 10.2 sources, as mentioned by ishamm, and here. I actually meant that by "nightlies", but in this context the term is misleading because they haven't started nightly builds for CM 10.2 yet.
[Sony Xperia S, Acro S, Ion] ishamm:
It is apparently now in 10.2 sources, i downloaded a zip to flash, i will try to find where it was , some where here on xda
[Sony Xperia S, Acro S, Ion] heavens dragon:
CM focal app u can get it from here ...it works alright bt crashes now n thn though

http://xdaforums.com/showthread.php?t=2384539

edit : seems very buggy for our device i will not recommend installing this
[Sony Xperia S, Acro S, Ion] ishamm:
I've found it to be good, if you close it with a long back press to 'kill' it, then it opens the next time fine. Otherwise it opens with a black screen.
[Sony Xperia S, Acro S, Ion] airwolf1544:
From Letamas Thread [ROM] JB AOSP 4.2.2 beta 3. New: 3.4 kernel, JB proprietaries and EAP-SIM

:)
[Sony Xperia S, Acro S, Ion] mirhl:
could you KINDLY discuss about this "feature" in the DISCUSSION THREAD

thank you

btw i'm referring to useless camera gossip
[Sony Xperia S, Acro S, Ion] frikakwa:
airwolf1544 brought part of a dev discussion back to RaymanFX's thread so... what's wrong with it? :confused:
[Sony Xperia S, Acro S, Ion] Gallardo994:
He was speaking about camera discussion.

Powered by TVR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] airwolf1544:
? Where ?

I only want to share what's upcomeing.. I think this dev threads are to talk about the rom, the bugs and the development. Am i wrong?

Gesendet von meinem Xperia S mit Tapatalk 4 Beta
[Sony Xperia S, Acro S, Ion] Gallardo994:
Focal Camera is not related to the rom development.

Powered by TVR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] alveos:
Where is keyboard down button? Like the one on the right corner. I have smiles here ;/
[Sony Xperia S, Acro S, Ion] Great_Geek:
What do you mean ?

Either press the back button (hw key)

Or, press the on screen button on the left side of the home button ;)

If you want emoticons, then you have to change settings in your messaging app :)
[Sony Xperia S, Acro S, Ion] Trevor Chuah:
If you mean the 'Enter' key, I can't find it in language and input setting.

But it can be change in Messaging app, in Messaging app, setting, the last option, you can choose either emoticon or enter key.
[Sony Xperia S, Acro S, Ion] RaymanFX:
Incoming!

Android 4.3 test build with TRIM support, WiFi tethering fixed and Legacy Display drivers (only solution on 4.3 for now) :)

Need to relax right now, but the test build should be there soon.
[Sony Xperia S, Acro S, Ion] switzerland92:
Man, you know, I can't stop smiling... Android 4.3 on our Xperia S i sooooo little time... you are unbelievable!

Next time you'll be in Croatia you have a beer on me! :D

Thank you thank you thank you!
[Sony Xperia S, Acro S, Ion] schickel:
Ajmo sad na pivo :)

4.3 is unbelievable

Gesendet von meinem LT26i mit Tapatalk 2
[Sony Xperia S, Acro S, Ion] akshayguptaus:
Man you are genius. Btw what is the difference b/w legacy drivers and the one you were trying to implement? This is just for my knowledge. Thanks.
[Sony Xperia S, Acro S, Ion] switzerland92:
Haha, dogovorit ćemo nešto :D

OT: Do you folks collaborate together with this ROMs? I see [MENTION=834547]letama[/MENTION] released some screenshots with Android 4.3 so I thought you are making this possible together?
[Sony Xperia S, Acro S, Ion] alveos:
How can i go to another line like this:

1:

2:

3:

4:

5:

Not 1: 2: 3: 4: 5:

Now you understand?
[Sony Xperia S, Acro S, Ion] Toledo_JAB:
Did this work?
[Sony Xperia S, Acro S, Ion] Great_Geek:
Ah, yes, I do understand now :)

You have to go to

Messaging -> (options key) -> Settings -> Soft keyboard (last option)

Here's what it should be :)
[Sony Xperia S, Acro S, Ion] gagaggogo:
Good job, and thank you.

I already hit the thanks.
[Sony Xperia S, Acro S, Ion] naeem123:
Work on locked bootloader?
[Sony Xperia S, Acro S, Ion] prasad90:
Noo
[Sony Xperia S, Acro S, Ion] alveos:
Thanks for info about enter icon ;) waiting for 4.3. Is thrre 3.4 kernel or newer? Maybe finally there will be working system camera ;)
[Sony Xperia S, Acro S, Ion] Gallardo994:
Your Delorean has travelled to the future. We don't have 4.4.

Powered by GSR with Android 4.1.2 on the board.
[Sony Xperia S, Acro S, Ion] switzerland92:
Did anyone built new sources that Rayman uploaded on GitHub? My PC isn't strong enough and does not have free space on it to build source but I hope someone out here can do it :)

There is XDA University link where building Android from sources is well explained:

http://xda-university.com/as-a-developer/getting-started-building-android-from-source
[Sony Xperia S, Acro S, Ion] alveos:
My mistake ;) 3.4 ;)
[Sony Xperia S, Acro S, Ion] someone755:
As I understand, the kernel in all JB versions is 3.4, but there are minor changes in them between the versions.

Wait, did I miss something completely important and we're getting 4.3?

Also, icymi, Sony's announced an update for some 2012 phones. Some phones that currently have 4.1 may make a jump to 4.3. I'm just seeing if they're man enough to give us 4.3... (even though 4.1 is broken)
[Sony Xperia S, Acro S, Ion] Novastylez:
Sony announced 4.3 for the Xperia SP, but not for the S (the SP ist based on MSM8960, the S on MSM8260). As someone said before, Qualcomm dropped the support for our chipset, so Sony will never make an update for our phone :/

(Sry for OT)
[Sony Xperia S, Acro S, Ion] RaymanFX:
I'll save you before someone rants you for rejecting the S3 chipset being abandoned by Qualcomm :)

[Edit - damnit, Novastylez was faster]

Here's the thing. I talked to some Sony internals and responsibles, as well as a russian developer, who is somehow involved with Sony and is a good friend of mine (I'll not name him here directly for some reasons), he also was the person he received the first leaked Jellybean builds back in January.

Long story short, the outcome of this was basically that Sony did some outstanding work on the 3.4 kernel. Instead of just bringing it up-to-date with Jellybean user space drivers (HALs), they updated it to the new CAF API (MR1 respective) and wrapped the Jellybean display HAL around the MR1 API, which was never meant to run on the S3 chipset. So their kernel basically has >4.1 and beyond compatible video drivers, it's just missing fences (that's also why LeTama was able to bring the Sony kernel up-to-date for 4.2 userspace drivers by just adding fences, we discussed this aswell).

==> outcome: I dare to say Sony could basically provide 4.2 or eve 4.3 builds for our device pretty easily.

But I guess they just dropped support for our device (except for bugfix 4.1 releases) because it's and oldie and they have way too much newer devices they have to support.

So what I will be doing the next few days is trying to upgrade my display-legacy HAL to the new MR1 API from CAF, but leave out fences so we don't get into trouble there, leaving the kernel drivers mostly untouched (except for the synchronization driver frameworks).

And yes - the first 4.3 build will arrive soon, I am expecting it to work better than current 4.2 builds actually :)

WiFi tethering is working flawlessly (been using it the last few days without pause), there are close to no display related bugs, battery life feels at least as well as stock, it might only lack some smoothness compared to chocolate versions. But it is stable. No crashes whatsoever. Oh, and HDMI should also work flawlessly here. I am working on improving the legacy drivers, it's just a matter of time until they work at least as well as chocolate drivers.
[Sony Xperia S, Acro S, Ion] waleed78636:
The difference

Hey rayman bro i recorded 1080p with stock app and with a third party app the .211 stock app recording was very laggy while the 3rd party app recording was less laggy why it is so????????????

Dont know it is stupid question but beginner...........So plzzzzz........
[Sony Xperia S, Acro S, Ion] SaZh047:
What the hell does it have to do with this ROM?

Go in Q&A section man !
[Sony Xperia S, Acro S, Ion] someone755:
Thanks for that explanation.

So, if I understand correctly, we (you) have everything we (you) need for all future Jellybean versions (in theory even 4.4)?

And Sony could, if they wanted to, give us the official 4.3?

But if what everyone's saying about Qualcomm dropping support of the S3 chipsets is true, why is 4.3 virtually flawless, as you say? Did Sony do so well with the 3.4 kernel or are you doing your magic again?

Also, personal opinion, I think they'd rather give a bug-filled 4.3 update than a 4.1 fix... :I
[Sony Xperia S, Acro S, Ion] rc_enzo:
I used stock ROMs for quite a while now, because I noticed the new Sony Jelly Bean was considerably smoother than any custom ROM I tried before. (Note: that I tried, other people usually got better performance somehow :P)

I switched back to OpenSEMC today, and I'm stunned to see the improvements since a couple of months. It's amazing.
[Sony Xperia S, Acro S, Ion] mat2057:
I'm trying to build OpenSEMC (cm-10.1) and I'm faced with this error :

Of course, I ran a "make clean" and updated everything. On CyanogenMod github I noticed this commit: https://github.com/CyanogenMod/android_build/commit/ff41d07cb201bea2ba2d29581ef2dd9fffbdc62f (and here: https://github.com/OpenSEMC/android_build/commit/ff41d07cb201bea2ba2d29581ef2dd9fffbdc62f).

The issue seems to come from this, but I don't know how to solve it...

Did anyone manage to build OpenSEMC (cm-10.1) recently?

Edit: same error when building cm-10.2...
[Sony Xperia S, Acro S, Ion] rc_enzo:
I do have a small question though. When taking a photo with the Camera app, after shooting the preview stays still as the picture it just took. Even though it will focus and shoot more photos, it only shows the still photos, not the moving camera image. Already cleared the Gallery's data once.

I'll provide a logcat if necessary.
[Sony Xperia S, Acro S, Ion] Android_UK:
It's already a known issue. Also where is the question? Lol j/k. Most of the issues we have with current build is known to DEV and is being looked at.

Please may I remind folks to use search for already posted questions before posting as vital info can be overlooked because the same questions come up time after time when the solutions are there. Thanx
[Sony Xperia S, Acro S, Ion] rc_enzo:
Good point, I haven't put a question mark anywhere... Anyway, I can live with it. I'll be patient. ;)
[Sony Xperia S, Acro S, Ion] alveos:
[MENTION=834547]letama[/MENTION] already posted a 4.3 version ;) Lets see if this one will be better ;D
[Sony Xperia S, Acro S, Ion] Phantasm4489:
same error here when trying to build
[Sony Xperia S, Acro S, Ion] RaymanFX:
I'm sorry, forgot to push this little nugget: https://github.com/OpenSEMC/android...mmit/456ef290b44f24e591006ebe4368634f6a609a03

It will take care of the issues :)

CM merged the necessary code in platform/build to support custom bootimage makefiles as we are using one to generate the elf binary containing the bootimage in the end (this was our plan for CM-10.1), and now we can just use the default AOSP releasetools because they will automagically give us a working boot.img in the end instead of a inappropriate one and a working .elf one.

I am keeping the releasetools around for obvious reasons though - if CM decides to drop support for this or if we need future reference for AOSP builds.
[Sony Xperia S, Acro S, Ion] alveos:
Thanks rayman for nre info ;) We are waiting for 4.3 ;) Is there a huge difference between 4.2.2?
[Sony Xperia S, Acro S, Ion] GTDarthYoda:
IMO not really...

Got the new nexus 7 and it feels just like my first one.
[Sony Xperia S, Acro S, Ion] ultima888:
I don't think the stock app in RC1/Chocolate was capable of recording video in 1080, only 3rd party app. So maybe that's why it's irrelevant.
[Sony Xperia S, Acro S, Ion] alveos:
No 1080p in rc1 znd chocolate
[Sony Xperia S, Acro S, Ion] mat2057:
Thank you ! I think you can push it for the cm-10.1 branch as well :)

Now there's an issue with DSPManager package (packages/apps/DSPManager/cyanogen-dsp/cyanogen-dsp.cpp:211:1: warning: missing initializer for member 'audio_effect_library_s::get_descriptor' [-Wmissing-field-initializers]), but I don't think it comes from the fork.
[Sony Xperia S, Acro S, Ion] Phantasm4489:
thanks, the cm10.2 builds now but i just get a bootloop when i flash it and logcat just shows this:

W/IMediaDeathNotifier( 588): Media player service not published, waiting...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

W/AudioSystem( 588): AudioFlinger not published, waiting...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

W/IMediaDeathNotifier( 588): Media player service not published, waiting...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

W/AudioSystem( 588): AudioFlinger not published, waiting...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...

W/IMediaDeathNotifier( 588): Media player service not published, waiting...

I/ServiceManager( 588): Waiting for service media.player...

I/ServiceManager( 588): Waiting for service media.audio_flinger...
[Sony Xperia S, Acro S, Ion] RaymanFX:
Ohey people,

Despite some people spamming my inbox, scared to death, I am still alive.

4.3 boots, but I don't consider it stable enough to be released just now.

The main reason for this decision are as follows: I want to provide a working system for everybody so you can grab OpenSEMC sources and it builds a working system without too much hassle. You probably know several distributions kinda rely on OpenSEMC, like P.A.C, Slimbean, AOKP and all others except for Letama's AOSP. Mainly, we're having issues with frameworks/av, but this is a known and hot discussed topic at CM in general for pre msm8960 devices. I could go dirty all over, crap LPA and Tunnel support out of the repo, but this is not where we want to go, having future Android versions in mind. I am currently working on a system designed for legacy devices, as our Nozomi is one with my CodefireX team leader Synergy. Once we're all setup, CodefireX aswell as fresh OpenSEMC builds with start rolling out.

As for the display drivers, it is to say I've gotten the legacy drivers to work as good as possible right now, but in fact the chocolate versions still have the absolute edge.

So what I am going to do now is to leave the legacy story behind and improve chocolate drivers and especially rework the kernel. Tons of stuff not needed for a mr1 bringup on our platform slipped in, namely WiFi display driver changes to mdp/msm_fb which can cause overlay issues because we don't have a third framebuffer device handling WFD. (fb0 = primary display; fb1 = external display, i.e. HDMI; fb2 = WFD, does not exist on Nozomi). Also, I really want to revert the QSEED/CSC post-processing engine, as it deeply affects MDP composition aswell and the 'old' MDP4 HSIC sharpening engine seems to do the job just fine.

This sounds like a lot of changes, but it should only take me a few days to figure if we can gain an improvement here. See ya soon, I'll keep you posted! :)