yashsingh1/xdaforums huggingface dataset:
[Sony Xperia S, Acro S, Ion] seahorsepip:
It has everything to do with graphics working except hdmi.

But it has a 1px line bug as been reported multiple times in the previous pages.
[Sony Xperia S, Acro S, Ion] heavens dragon:
im using the latest test version n there seems to bug with battery i left the phone at 86% b4 i went to bed n found the phone at 86% when i woke up n thn i rebooted only to see it went up to 88% ..it only dropped when i did the 3 vibration reboot
[Sony Xperia S, Acro S, Ion] alveos:
Just use dark wallpaper as i do, and there is no line ;) i mean, it is there but you dont see it ;)
[Sony Xperia S, Acro S, Ion] sorcio46:
New issue submitted: https://code.google.com/p/opensemc/issues/detail?id=22

Screen becomes Black when using the Camera Tile

What steps will reproduce the problem?

1. Unlock the phone

2. Pull down the notification bar

3. Open the Quick settings panel

4. Click on the camera tile to wake the camera

5. Do some click on the camera tile to shoot some photos

6. Press the home button

7. Screen becomes Black

What version of the product are you using? On what operating system?

Open SEMC RC1 chocolate | CM10.1-20130712-UNOFFICIAL-nozomi
[Sony Xperia S, Acro S, Ion] mirhl:
[MENTION=3141585]heavens dragon[/MENTION] [MENTION=4060983]sorcio46[/MENTION]

you are falling in the usual not developing related things

bug should go to code google (and that's good, you created a ticket)

BUT PLEASE don't complain about any battery drain PLEASE

(unless you lost 90% in half an hour :\)
[Sony Xperia S, Acro S, Ion] RaymanFX:
Invalid, because RC1-choclate is NO release!

People, please only submit bugs for releases that I marked as such.

I clearly stated RC1-chocolate is a test release, thus I don't want it to clobber the issue section etc.
[Sony Xperia S, Acro S, Ion] frikakwa:
-root explorer then system/etc.

-edit hw_config.sh

-find "proximity sensor configuration"

-change values to the below:

val_cycle=1

val_nburst=1

val_freq=5

val_threshold=1

val_filter=1

Is this better? Does it work? :-S
[Sony Xperia S, Acro S, Ion] RaymanFX:
Well, you're not cool either.

Go and compile the rom yourself, see if you can do better.

Speaker volume is fine for me, I don't know if I included the low-in-call colume fix in RC1 though. Try RC1-chocolate, that has it integrated for sure.

And now I dare you ask for the link! Search the thread, you'll find it.

You could at least have stated on which version you are before complaining.

Also, why do people tend to ignore the forum rules?

Open a new issue at my Google Code Project Home, the link is given in the first post.

Development threads are for development only, not for complaining about 'uncool' things.

This is the last time I'll respond to such irrelevant posts, I'll report you to the moderators now so they can decide if cleaning is needed. AGAIN.

Now back on-topic: [MENTION=2145830]frikakwa[/MENTION], I would never have gueesed hjacking the proximity sensor's threshold would improve the display wakeup, since I am 100% sure it's a derp in the new video drivers, but since I see you're getting positive feedback, thanks for this!

I have an idea where I could improve the wakeup in the kernel already, it's about the LED driver and suspend/resume technique now.

We might actually need to extend the resume logic because our video drivers depend on event timers, which are not currently implemented in the LED driver.. I'll give it a shot and let you know :)
[Sony Xperia S, Acro S, Ion] anon_freak:
Moderators... [MENTION=3463426]RaymanFX[/MENTION] I gonna ask this as long as RaymanFX answers my question why he doesn't makes a discussion thread...
[Sony Xperia S, Acro S, Ion] rolex0815:
And now for something completely different. ;)

Is it possible, that something in the repos is broken?

Compile failed yesterday evening (yeah, removed the TWRP directories).

(Don't have the error message now *facepalm*).

On Sunday, all went good.
[Sony Xperia S, Acro S, Ion] ny-hardcore:
https://github.com/CyanogenMod/android_vendor_cm/commit/5d4847b8e4e53bf3107c22a3f8edfb0a307e4e8c

This maybe?
[Sony Xperia S, Acro S, Ion] ApriliaM3:
It's enough now thanks guys because this discussion issue has been done to death.

To anyone that's still confused, the OP owes you nothing... not even an explanation.

Also, I've got better things to do with my time than to keep coming here and cleaning up the mess.

This is a Development Thread so please get back on-topic and stay there.
[Sony Xperia S, Acro S, Ion] airwolf1544:
[MENTION=3463426]RaymanFX[/MENTION].. any progress with codefirex? Their changlog website doesn't look good.. no update since over one month.. :rolleyes:
[Sony Xperia S, Acro S, Ion] RaymanFX:
Hey, sorry for the late reply.

Yeah, that's because we started a new project from the ground up, called 'codefireXperiment'.

You can find out current codebase here: https://github.com/codefireXperiment

Our website is currently here (interactive changelogs will be coming): http://www.beta.codefirex.com/

We're getting new servers and hosts at the moment, and I am responsible for the Asus EEEPad Transformer 101, Nozomi, Hikari and Aboa, so I am pretty busy. I'm also working on our video drivers, making little progress every day.

Stay tuned for more updated. It won't be long until the first CFX release now!
[Sony Xperia S, Acro S, Ion] ishamm:
off topic, but if your doing transformer 101, is there any chance you'll do the 700 to? :D

Chocolate release is working great for a few days now!
[Sony Xperia S, Acro S, Ion] gagaggogo:
I think CodefireX will be amazing.
[Sony Xperia S, Acro S, Ion] alveos:
Beta codefirex doesnt work ;/
[Sony Xperia S, Acro S, Ion] RaymanFX:
Hey guys, a little status update:

I'm currently preparing yet another chocolate based kernel, which basically contains - well - more chocolate.

I found a proper entry point into CAF's jb_mr1_chocolate branch from where I could cherry-pick all the nexessary commits onto the Sony base.

This one should get rid of the offset issue, as well as the suspend/resume issue and there's also a good chance it'll get us HDMI back.

I will be pushing the kernel source once I am satisfied with it and have it working nice enough to be a daily driver.

Please note that in order to get us the best video drivers we can possibly get, I sacrificed workload on all other opensemc issues, like tethering, etc.

Video drivers are most important for now, because they deeply affect battery life as well as general UI performance (MDP composition).

Stay tuned! :)
[Sony Xperia S, Acro S, Ion] alveos:
Thanks rayman for new info. How about camera freezes after raking picture and no 1080 in stock camera? Is it in your fix list?
[Sony Xperia S, Acro S, Ion] lantianer:
[MENTION=4982178]alveos[/MENTION]: please look into page one or use the search function for the next time

https://code.google.com/p/opensemc/issues/list
[Sony Xperia S, Acro S, Ion] cronot:
Hey [MENTION=3463426]RaymanFX[/MENTION], nice to hear from you again.

Re: top offset 1px issue: I've been using chocolate for a few days, and I just couldn't spot that thing. And yes, I've tried setting a bright wallpaper and such; still can't spot it, as far it seems to me the display looks perfect, no weird top 1px line offset for me. The only noticeable issue is really the suspend/resume problem (and the hw_config.sh tweaks don't really seem to matter). I've got a few other issues too related to apps, that I was going to report on the project bug tracker, but since you asked to not report issues for the chocolate release, I'll hold them until you're ok with it.

Keep up that awesome work! Thanks!

Edit: For you people that do have that 1px offset problem: Do you think that 1px thing can be spotted on a (not HD) video? If so, I'll try to capture my phone's screen with another camera I have so you guys don't think I'm crazy :)
[Sony Xperia S, Acro S, Ion] Yakandu:
Dont be afraid, i dont see that 1px bar too
[Sony Xperia S, Acro S, Ion] mirhl:
Don't piss for 1px offset

We know that there are some problems, and that is only the tip of the iceberg (which maybe is the only thing tbat normal user see)

There are a lot of other giggles buggy under it (mdp composition, hdmi.. butter.. and so on)

And rayman is already doing his best to fix all

Gossiping only burder the situation

So, pleeease, don't bother about the usual bugs
[Sony Xperia S, Acro S, Ion] cronot:
I hate to call you out, because I've seen your interactions with the community and you are a cool guy and valuable member of the community, and I also hate doing this specially because right now I've setup myself as being guity of derailing the thread into pointless discussion / offtopic; but please, read again what I posted - first of all, I'm not pissing anyone off, I'm providing feedback and actually also asking for more feedback. And more importantly, I'm not pissing anyone off because I've got a bug, but I'm providing feedback that, apparently, I DON'T HAVE a bug that everyone is supposed to have. And this may be relevant, because if some people do have that bug and RaymanFX fixes it for him/them, it's possible that it may actually break things for people that DON'T have the bug - and it seems now I'm not the only one. So I think it's important to clear this up so RaymanFX may handle the bug appropriately.
[Sony Xperia S, Acro S, Ion] mirhl:
[MENTION=2843496]Cronos[/MENTION]

There are not first-class xperia s and second-class xperia s

Unfortunantely i'm stuck with the fu***ing ics stock, so i can't test and fully understand

But if some user have this bug and some not, it's only due to what that users have done

And since there's no magic inside, all the necessary it's in plain c(++) on github

Whatever the problem could be, you haven't provided a logcat, nor a new theory

So, imho, it was an aimless, gossipy remark (but still 100 times better than those noob posts with fix it! Im the president of usa!)
[Sony Xperia S, Acro S, Ion] alveos:
I dont want any other app like camera+!!! Thats why i am asking about normal camera.
[Sony Xperia S, Acro S, Ion] zekozeko:
Great news! One suggestion, if I may :) I was reading the other day that AOKP finally moved to 4.2.2, and FXP is working on CM 10.1, so... You're seeing where this is going :) Maybe you could port AOKP for XS instead of working on CM. I'm not sure how different is aokp tree from cm's... Just a suggestion. Respect for all your work :good:
[Sony Xperia S, Acro S, Ion] someone755:
Dude, porting AOSP-based ROMs is easy once you have a base. CM in this case.

Also, the newest AOKP update is MR2. MR1 has been available for some time now. (4.2.2.)

I already have a semi-working port of 4.2 MR1, but I'm having issues with the SDcard not being mounted and the com.android.phone crashing (and no data connection, or calls or sms etc.)

(off topic: can anyone help here? Or redirect me to somebody that could?).

He'll do what he wants, and currently, he wants a stable 10.1 build (or so it would seem, I could be wrong)...
[Sony Xperia S, Acro S, Ion] zekozeko:
Ofcource he will do what he wants. Was I ordering him?! And right because comments like yours I repeated several times that I'm just suggesting. For my sake, I'll always go with cm rather then aokp. I was giving suggestion with community on mind...And his personal goals. As you can see with eos and now this new rom that he is partaking in, his first choice for development are roms that isn't available already for our device. Because they take more effort, and he obviously likes challenges - look at the time and effort he puts in mdp thingy.

And please, don't call me dude, I'm not 15 years old.

Regards,

Not holding any grudges.

Edit: [MENTION=276667]ny-hardcore[/MENTION]ˇ I somehow missed your thread :)
[Sony Xperia S, Acro S, Ion] ny-hardcore:
Not trying to hijack the thread but my unofficial AOKP 4.2.2 build using opensemc & aokp sources can be found here:

http://xdaforums.com/showthread.php?t=2273254
[Sony Xperia S, Acro S, Ion] alveos:
I just noticed that flashlight is blinking when turned on for more then 3 seconds. Talking about chocolate bulid.
[Sony Xperia S, Acro S, Ion] sneaky55121:
Hi,

I'm trying to install the ROM RC but I get error Status 7, any idea to solve it?
[Sony Xperia S, Acro S, Ion] Schakel:
Try to format data + system.

Then flash.
[Sony Xperia S, Acro S, Ion] seahorsepip:
If still not wokring by previous suggestion make sure that you use the latest recovery, flash the kernel first with flasboot in this case to get the latest recovery ;)
[Sony Xperia S, Acro S, Ion] Memethecat:
I've been told that PAC 23 has its own permission system, similar to openpdroid & pdroid2.

I know they use a lot of RaymanFX work, so was curious if this ROM had its own permission system too.

Tx
[Sony Xperia S, Acro S, Ion] ishamm:
Since 4.3 has now been released, are you able to update this to the new version, or am I being unrealistic XD
[Sony Xperia S, Acro S, Ion] GTDarthYoda:
http://www.youtube.com/watch?v=JmvCpR45LKA
[Sony Xperia S, Acro S, Ion] cronot:
Fun fact: I was actually going to post asking about 4.3 on the XS, but obviously as a joke, because I know it's an unreasonable question at this point in time, and I was going do it more to make fun of some noobs and crazy users. But someone actually beat me to it and asked it for real!

My goodness...

Ok, to be less of a d*ck and actually answer your question: The CM team themselves (from whose work OpenSEMC is derived from) have just started work on CM 10.2 (Android 4.3), so no, don't expect anything for the next few weeks or even months. I'm sure the CM Team will have a working build of CM 10.2 in a few days, but getting that ported over to OpenSEMC may not be a trivial task depending on how many breaking changes there are on Android 4.3 wrt to drivers and HAL. Even OpenSEMC as it is right now has a few remaining issues, so it's not realistic at all to make such a question so early.

And yeah, that youtube video above serves you well.
[Sony Xperia S, Acro S, Ion] switzerland92:
Another thing is - 4.3 doesn't bring anything special for us. Maybe biggest change is for WiFi and location but there is really no need for 99,999% folks out here to use 4.3.

Only if there is so much discussed lower RAM usage - then I'm in! 685 megs of RAM is very low considering that every other phoned advertised with 1GB of RAM has at least 800MB of available memory.

EDIT: Most of the news regarding 4.3 are under the hood so porting and making it work can take much more time than you think ;)
[Sony Xperia S, Acro S, Ion] ishamm:
Well thanks for the real explanation, first comment aside..

I understand it's not a simple task, but just assumed that since its a small update it might be "coming soon"

As for it not bringing much to the device, the graphic processing changes will presumably prove useful for all of us.
[Sony Xperia S, Acro S, Ion] FenrirMX:
Not really when you consider the biggest problem every dev is having for our XS is that Qualcomm has not and will not release any drivers for our chipset for anything after Android 4.1.
[Sony Xperia S, Acro S, Ion] mat2057:
[MENTION=3463426]RaymanFX[/MENTION] I hope I'm not off-topic.

I'm trying to build OpenSEMC "legacy" and I encounter this issue (even after a "make clean"):

Of course, the file exists. The makefiles in display and display-caf seem to be the same. I haven't succeed in finding where this comes from. Do you have an idea?

I've built another version with the "chocolate" kernel but there's something wrong: the CPU settings are not taken into account, the CPU is always at its max frequency (1512 MHz), but it's set at 1134 MHz everytime I boot... (I assume you use display drivers from display-caf. Do I have to modify anything else than BoardConfig.mk?)

I know this is a dev version, but... is it a kernel issue or does it come from CyanogenMod?

If anyone can help or have an idea.

Thank you for your answers
[Sony Xperia S, Acro S, Ion] ishamm:
Ah i had just thought they were skipping 4.2 for some reason, not stopping all together. What a pain, but thanks .
[Sony Xperia S, Acro S, Ion] gagaggogo:
Anyway, after have a try on different ROM, the one made by RaymanFX is my choice.
[Sony Xperia S, Acro S, Ion] goodwin_c:
In hardware/qcom/display/common.mk change in /display-legacy/ to /display/ (wrong common include path, because out directory is display and not display-legacy)

edit: in hardware/qcom find all *.mk files with "/display-legacy/" and "/media-legacy/" entries and replace them to "/display/" and "/media/"
[Sony Xperia S, Acro S, Ion] RaymanFX:
Hey, sorry for the late answer, been really busy this week..

This is right. The includes and dependencies are pointing to display-legacy and media-legacy instead of just display and media when we set TARGET_DISPLAY_VARIANT to legacy in our BoardConfig.

You'll also have to change the include paths for media-legacy, mostly in vidc/vdec and venc IIRC.

The thing is, I attempted a legacy build yesterday, and all games are working, video playback is fine, and basically everything just works.

BUT it's just so stuttery. It's nowhere near as smooth as e.g. RC1 or RC0 or even RC1-chocolate.

And the bad thing is, I cannot find any borked things, because there are none. Logcat shows nothing, neither does dmesg. They just show what they are supposed to show - everything working fine, where it definately doesn't work fine.

Thing is, there are other 8660 devices out there (e.g. the HTC EVO 3D), those are using the legacy HAL just fine, with faked vsync and it is real butter. They don't have the problems I am having currently.

So for now, I'm a bit lost here, whether to continue on chocolate kernels, which might never be perfect, but definately work better right now - or go with the legacy attempt, which seems more proper at the first glance, because we could theoretically support msm8660 until Android 13 "Sneaky Sandwich" without too much hassle and work each version.

Opinions please. :) This is a community effort and I don't want to make all these decisions on my own.
[Sony Xperia S, Acro S, Ion] ny-hardcore:
i would say legacy, will save you a lot of headache in the long run in think...

FYI; i'm not a programmer, but is isn't possible to add some extra debugging to the display-legacy stuff so that logcat is (even) more verbose?
[Sony Xperia S, Acro S, Ion] switzerland92:
[MENTION=3463426]RaymanFX[/MENTION]

I stayed on RC1 chocolate even if it had fewer features than other ROMs just because phone feels and works soooo smooth and fast. Definately best non-stock ROM out here. I think Android 4.2.2 is mature enogh to be used for long periods of time, even after Key Lime Pie. It just has everything I personally need and use.

Maybe if some day you'll find out why it is stuttery on legacy drivers you could fix it - that would be perfect hit :D

Well, my opinion on your dilemma - if you can work on existing chocolate kernel until you think it is good for daily use and after that go for legacy. To be honest, I use RC1 chocolate as my daily driver and there wasn't a single reboot, major lag or some other problems with apps or features. Every time I flash your ROM i also flash custom camera that works good so I really don't have any major critique.

I am sure you can count on us here, we'll try to send you logcats, test your releases, maybe help you solving bugs and errors. :)

EDIT: Uptime over 180 hours and still works like when I turned it on. No ROM is able to perform like that, I'm serious.
[Sony Xperia S, Acro S, Ion] Trevor Chuah:
Just a noob question:

Is Legacy HAL = Sony Proprietary (Closed source) Driver?
[Sony Xperia S, Acro S, Ion] switzerland92:
As far as I know yes, those are drivers from latest open source drivers provided by Sony from their dev site.
[Sony Xperia S, Acro S, Ion] mirhl:
Could latest 3.4 kernel fxp cm10 give some tips about this dilemma?
[Sony Xperia S, Acro S, Ion] cronot:
Ok, the little dev in me prefers the legacy solution because it's a more robust and stable solution in the long run.

But...

I've got really hooked into the smoothness of the RC1-chocolate release, I'm not sure I can settle for less anymore :) In fact, as far as "video" issues, I've had very little (not even worth it getting into details), so as far as I'm concerned, the "video" part is already perfect for me. So, my suggestion is: Keep the current CAF driver (from chocolate release) for now, but let go of working on it for the time being, and instead work on pending usability issues like Wi-Fi tethering, Torch light flickering and Camera freezing (and only that - I'd say don't bother with 1080p video for now either because it seems to be a problem on stock too (and hence it's probably not an easy fix, if at all possible), and I don't care about it anyway). Once these issues are fixed, then OpenSEMC will actually be almost perfect and actually deserving of an "RC" tag ;) and then after that I think it'll make sense to investigate the legacy driver and try to fix whatever issues it has.

Sony released the kernel sources a couple months ago, it was my understanding that FXP built their kernel based on these sources, just like RaymanFX did - isn't that correct?

Cheers!
[Sony Xperia S, Acro S, Ion] RaymanFX:
Nope. Hell, I'll never rely on more closed source proprietaries than I absolutely have to.

This would be scary. The legacy HAL(s) can be found at OpenSEMC's github, respective repo name.

(media-legacy and display-legacy)

As I said above, nope, you're on the wrong track. Sony does not provide any HAL modules at all (except for DASH, which I don't even use).

Sad truth is: No, not at all.

They don't even have a working Radio on their CM-10 build, in fact, I am ages of work ahead of FXP.

They could sove their radio problems if they would just make use of all the work I already did. I honestly don't know why they refuse to use my resources. And my current chocolate kernels are also AGES ahead of their current 3.4 kernel, regarding drivers and msm specific kernel code.

In addition to that, I had a talk with Kali- on IRC and he said he didn't even know there was a thread for cm-10.1 in Fuji device section (nozomi, hikari, aoba), and he also said he didn't care about 4.2 on Fuji boards (until that point of time, of course I don't have any intel on their current plans). So what I can say for sure is: FXP does not have ANY 4.2 (CM-10.1) build ready for our devices. They are so far away from a 4.2 build as one can possibly be. Hell, they don't even have a working Cm10 build with the 3.4 kernel, eventhough Kali- did great work on the kernel.

(Maybe except that he uses RTC write to communicate with the Radio via kernel, which is not recommended by Qualcomm, because it offers various security breaches, that's why I am using a timer daemon injected by the ramdisk (this is safe and, well, just works as you can see)

As always, no criticism towards FXP at all. I'd happily help them and maybe even join them (not the team, but the development efforts) if they'd just act towards 4.2 or even 4.3 (mr1/mr2) for our Nozomi. I am not willing to step back and resurrect CM10, that's just a waste of time for me.

I'll work my best to get 4.2 running as good as possible and then move on to 4.3.

A first CM-10.2 build might be dropped soon, along with a new kernel (it will be experimental and highly unstable though, because CM-10.2 is far from being build-able, but I already worked my ways around this).
[Sony Xperia S, Acro S, Ion] alveos:
Rayman, is it huge difference between 4.2.2 and 4.3 kernel? Maybe it will be better, to start with 4.3 / 10.2 and move on. I am not a developer, thats just my opinion.
[Sony Xperia S, Acro S, Ion] LLy_BosHi:
I'm not asking for 4.3 or KLP right away

But which one that would be possible to going further after 4.2 is considered 'stable' ? Legacy or chocolate?

Well... I just love my XS and I want to see development going further

Even if I have new device I won't sell my XS and would keep it

So I really appreciated that you willing to spend your free time developing our device

Sent from my LT26ii