{Z}[DEVELOPMENT] - CM11 - Android 4.4 - FreeXperia Project

[didicola]

Because our builds are broken?
See couple posts above yours.

Looks like there is nobody at CM working on fixing fusion3 devices

@FXP i dont know exactly under what circumastances do you work and cooperate with the cyanogenmod general corporation but the changes in the nightlies arent officially supported so as to have official updates like M2 or M3 ?

dont get me wrong i dont underestimate all the effort you do and we all thank you for what you try and devellop but the cm team cant just assign a develloper to maintain yuga(it is the same as nexus 4 without the sd card right?) ps. for god's shake they maintain galaxysmtd but not yuga seriously now?

can you plz clarify something else: the builds you make are more updated and more bugfree than official outdated cm11?
and a last point if it is a kernel issue can we just use meow kernel and all the issues will be solved?

thanks for your time!

 

[Burag]

I'm pretty sure that FXP builds are 100% CM source, so no improvments are made in them. Also our kernel is not buggy - it's just outdated...

Anyway, it's a big shame on CM team that our builds are actually broken since android 4.4 appeared. Almost 4 months passed, and yet, not much really changed for us.
As someone mentioned back in this thread, 4 years old Galaxy S has better CM support than our 1 year old fusion3 devices...
I was patient for a long time, but now I'm just frustrated - just got back to stock rooted 4.3...

@FXP
Guys, do you even visit XDA or just log in, post new (still broken) build and log off?
C'mon... You could at least explain to users why this situation is still not resolved...

 

[infected_]

@FXP i dont know exactly under what circumastances do you work and cooperate with the cyanogenmod general corporation but the changes in the nightlies arent officially supported so as to have official updates like M2 or M3 ?

dont get me wrong i dont underestimate all the effort you do and we all thank you for what you try and devellop but the cm team cant just assign a develloper to maintain yuga(it is the same as nexus 4 without the sd card right?) ps. for god's shake they maintain galaxysmtd but not yuga seriously now?

can you plz clarify something else: the builds you make are more updated and more bugfree than official outdated cm11?
and a last point if it is a kernel issue can we just use meow kernel and all the issues will be solved?

thanks for your time!

I'm pretty sure that FXP builds are 100% CM source, so no improvments are made in them. Also our kernel is not buggy - it's just outdated...

Anyway, it's a big shame on CM team that our builds are actually broken since android 4.4 appeared. Almost 4 months passed, and yet, not much really changed for us.
As someone mentioned back in this thread, 4 years old Galaxy S has better CM support than our 1 year old fusion3 devices...
I was patient for a long time, but now I'm just frustrated - just got back to stock rooted 4.3...

@FXP
Guys, do you even visit XDA or just log in, post new (still broken) build and log off?
C'mon... You could at least explain to users why this situation is still not resolved...

dont talk bad of the FreeXperiaProject maintainers... it because of they Z1 and others official nightly builds started...

wanna know the difference between FXP and CM build?! look at the d*** logs:

http://fxpblog.co/installation/cyanogenmod/changelog/

and whats the issues with the Z and CM 11... ?!? i have it running my own linaro builds on it without issues at all, since i bought it 15days ago..... daily driver, rock solid.

so please inform yourselfs a litle more before saying nonsense..

regards.

 

[didicola]

dont talk bad of the FreeXperiaProject maintainers... it because of they Z1 and others official nightly builds started...

wanna know the difference between FXP and CM build?! look at the d*** logs:

http://fxpblog.co/installation/cyanogenmod/changelog/

and whats the issues with the Z and CM 11... ?!? i have it running my own linaro builds on it without issues at all, since i bought it 15days ago..... daily driver, rock solid.

so please inform yourselfs a litle more before saying nonsense..

regards.

at least i didnt say anything bad regarding fxp
if you read my post you would have known that
i just said that the official cm dont make snapshots for us! i guess it is not a lie you see it
i have abandoned cm builds and i use yours with linaro modifications

 

[infected_]

at least i didnt say anything bad regarding fxp
if you read my post you would have known that
i just said that the official cm dont make snapshots for us! i guess it is not a lie you see it
i have abandoned cm builds and i use yours with linaro modifications

@FXP
Guys, do you even visit XDA or just log in, post new (still broken) build and log off?
C'mon... You could at least explain to users why this situation is still not resolved...

not you, this dear fellow over here...

 

[Burag]

dont talk bad of the FreeXperiaProject maintainers... it because of they Z1 and others official nightly builds started...

I'm not talking bad about @FXP.
Z1 nightlies started? That's great and stuff, but it's not fair that they've abandoned us in favor of Z1.
Is there any developer currently working on fixing fusion3 devices? (and by fixing I mean no dirty hacks, but fixing the root cause which are kernel/blobs).

wanna know the difference between FXP and CM build?! look at the d*** logs:
http://fxpblog.co/installation/cyanogenmod/changelog/

Did you notice that those changes are in repos that belong to CyanogenMod?
So no, FXP builds aren't something more than just compiled CM sources.

and whats the issues with the Z and CM 11...

Constant audio glitches and stuttering caused by outdated kernel and blobs.

 

[Vishalkris]

@Burag bro calm down u just have to switch to meow kernel and just raise your minimum frequency to 486 and choose your governor and io...or else leave it as it...u won't face issue with audio Sutter..if the new build of meow kernel doesn't work for you choose 1 later build and things would work out.. Peace

Sent from my C6603 using Tapatalk

---------- Post added at 11:58 PM ---------- Previous post was at 11:56 PM ----------

[/COLOR @Burag its not easy for fxp team to do everything they just DONT have the kernel commits..or else it won't hurt them to update the kernel as they are doing it for free and not asking or forcing to pay so patience

Sent from my C6603 using Tapatalk

 

[infected_]

I'm not talking bad about @FXP.
Z1 nightlies started? That's great and stuff, but it's not fair that they've abandoned us in favor of Z1.
Is there any developer currently working on fixing fusion3 devices? (and by fixing I mean no dirty hacks, but fixing the root cause which are kernel/blobs).


Did you notice that those changes are in repos that belong to CyanogenMod?
So no, FXP builds aren't something more than just compiled CM sources.


Constant audio glitches and stuttering caused by outdated kernel and blobs.

ignorance is bliss...

cheers..

 

[rlees85]

Does anyone know of a good dirty hack for fixing the audio problem? Even if it means having to build from source I would like to hear from you as its annoying the hell out of me and I will be relying on the phone a lot for music/etc soon...

I'd rather put up with it then go to stock.

I have tried the suggestion a few pages back regarding changes to AudioHardwareALSA.h, I found this file in two locations and made the correct changes. Built and installed and all this does is change the awful "popping" sound into a stutter. If anyone wants this ZIP let me know.

I checked the MEOW thread - the latest MEOW kernel has the same issue. The previous MEOW kernels are ancient so I expect would cause problems and you could just go to a earlier CM kernel probably with the same result.

I am in no way having a dig at FXP I know they are working on loads of other devices and I had no problem to donate to them a while back. I just want to fudge this somehow until it does get looked at by FXP/meow or someone else (who is more knowledgeable than myself!)

 

[aidfarh]

I'm using Omnirom and does not notice any audio problem. I'm not saying you should switch to Omnirom but maybe you can look into what's the difference between CM and Omni and figure out what Omni's doing right with regards to the audio.

 

[ghost7.me]

Does anyone know of a good dirty hack for fixing the audio problem? Even if it means having to build from source I would like to hear from you as its annoying the hell out of me and I will be relying on the phone a lot for music/etc soon...

I'd rather put up with it then go to stock.

I have tried the suggestion a few pages back regarding changes to AudioHardwareALSA.h, I found this file in two locations and made the correct changes. Built and installed and all this does is change the awful "popping" sound into a stutter. If anyone wants this ZIP let me know.

I checked the MEOW thread - the latest MEOW kernel has the same issue. The previous MEOW kernels are ancient so I expect would cause problems and you could just go to a earlier CM kernel probably with the same result.

I am in no way having a dig at FXP I know they are working on loads of other devices and I had no problem to donate to them a while back. I just want to fudge this somehow until it does get looked at by FXP/meow or someone else (who is more knowledgeable than myself!)

Had them on mine, and one day decided to change the profile to "performance" which helped/stopped the "cut outs" when playing music

No idea how/why it solved it for me

 

[rohit25]

Well I am on PABX ROM .... Have no issues what so ever.... Plus got appops installed so basically I am good....
You could try it .... I am eagerly looking for cm to implement the 4.3 blobs and then my love to CM would be back.... ?

Sent from Dilli

 

[Burag]

ignorance is bliss...

Yeah, you have just replied to my post with 3 words...

bro calm down u just have to switch to meow kernel and just raise your minimum frequency to 486 and choose your governor and io...or else leave it as it...u won't face issue with audio Sutter..if the new build of meow kernel doesn't work for you choose 1 later build and things would work out.. Peace

Bro, this is not true, so please stop misleading other users. As proven by @rlees85, meow kernel doesn't fix the issue.
Actually, all kernels / ROMs that are based on CM sources and TheMuppets blob repo are affected by this issue (Omni, AOKP etc.).

its not easy for fxp team to do everything they just DONT have the kernel commits..or else it won't hurt them to update the kernel as they are doing it for free and not asking or forcing to pay so patience

Let's clarify this a little bit - I'm not forcing anyone to do anything.
In the first place, I just wanted to know why this issue is not fixed. I'm not demanding the fix (!). I'd like to just get some information...

I have tried the suggestion a few pages back regarding changes to AudioHardwareALSA.h, I found this file in two locations and made the correct changes. Built and installed and all this does is change the awful "popping" sound into a stutter..

Unfortunetly, AFAIK, apart from that fix or updating kernel/blobs to 4.3, no other solution was ever proposed...

Going back to the actual development:
Does anyone know what should I do to update blobs and kernel by myself (or atleast try to achive this)?
I have a working CM build enviroment, basic C knowlage and semi-advanced Java knowlage - is this enought? ;P
I wonder if it would even boot if I just copy-paste new blobs and complie the kernel form Sony's sources?

 

[cdesai]

Hi,

The current kernel isn't outdated at all, it has been updated to a recent upstream (codeaurora) branch, which means, it is close to what an OEM would base their kernels on.
However, the CM kernel isn't based off sony's 4.3, as it dropped after we had updated it.

We are working on updating the blobs, however, there is an issue, calling is completely broken with the new blobs.
3G/Texts are fine, but calls aren't.
Haven't got a chance to look at it again yet, as we're all quite busy (personally speaking, I barely have time these days, and maintaining multiple devices makes it even less) - can't even imagine what it would be like for Kali-/FXP

I Hope that clears any doubts you guys had.


Btw, we merged tap-to-wake functionality earlier today (thank championswimmer for the find), it should be available in tomorrow's builds.
It is the right way to do it, and doesn't cause any additional battery drain, so if any kernel developer is reading this, I suggest you go for this approach.

 

[feydakin]

Have someone found the option to enable tap 2 wake? I checked all the menues twice but hadnt any luck

 

[SuperHanss]

Hi,

The current kernel isn't outdated at all, it has been updated to a recent upstream (codeaurora) branch, which means, it is close to what an OEM would base their kernels on.
However, the CM kernel isn't based off sony's 4.3, as it dropped after we had updated it.

We are working on updating the blobs, however, there is an issue, calling is completely broken with the new blobs.
3G/Texts are fine, but calls aren't.
Haven't got a chance to look at it again yet, as we're all quite busy (personally speaking, I barely have time these days, and maintaining multiple devices makes it even less) - can't even imagine what it would be like for Kali-/FXP

I Hope that clears any doubts you guys had.


Btw, we merged tap-to-wake functionality earlier today (thank championswimmer for the find), it should be available in tomorrow's builds.
It is the right way to do it, and doesn't cause any additional battery drain, so if any kernel developer is reading this, I suggest you go for this approach.

I assume the call problem requires a different fix to this - https://github.com/omnirom/android_device_sony_qcom-common/commit/43bed8ab08d73e7e69c21232b1d1472199bd2127

Looking forward to including the official d2w in my PA builds

 

[hutilicious]

Im loosin sort order in the app drawer randomly..is it only me? using nightly 2014-02-19 and trebuchet

Sent from my C6603 using xda app-developers app

 

[Danifamous]

Trebuchet is not appearing in the last 3 nightlies for me. Please confirm?

Sent from my C6603 using XDA Premium 4 mobile app

 

[iKillCypher]

@cdesai

are the ril still active ? for the new blobs causing calls to be broken?

 

[Tantawi]

@cdesai

are the ril still active ? for the new blobs causing calls to be broken?

I am very interested as well, hope the new blobs are merged soon.