Database Users

Very important. please read. x10 source petition.

This is for the benefit of all x10 Xperia users.
Sign this petition so we can gain any and all source or tools for our x10 from
Sony / Sony Ericsson.
This petition includes libraries for the camera, the screen or gpu and the touch input driver.
Only with your help can we truly make a difference.
http://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-xperiahttp://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-experia

Good idea.
Even today, our 4" screen, 1 GHz CPU, 8-32Gb SD machine is not that bad.
It's a sad thing that we bought a good Sony hardware limited by a very lame software.

Andre Verissimo said:
This is a temporary message, and I will edit it if somebody answer the question bellow.
Sometime ago, due to Android license, Sony posted in a technical site the source code file called
x10_x10mini_X10minipro_x8_eclair_2.1.A.0.435.tar.gz
that seems to have all the Eclair C-language source code, resources and makefiles for everything (including all the drivers [8,338 files], libs, scripts, kernel, firmware etc) inside our "Rachael" X10, and also for X10mini and X10minipro.
Is this what you're looking for?
Click to expand...
Click to collapse
Yes... but not exactly.
We also talking about getting these features working.
I believe we may be missing a few things.
There must also be 2.3 sources somewhere.
For interest sake.. could you link me to that source?
So far thanks for doing your best to free our device.
Would someone be so kind as to post this link on modaco?

Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz

Andre Verissimo said:
Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz
Click to expand...
Click to collapse
The question now... is everything truly there?

We are talking about 46,194 files inside 3,212 folders.
We need a real top developer / elite hacker (like z, The_Laser or DoomLord) to check it for us. Maybe this is what they were looking for.

Andre Verissimo said:
We need a real top developer / elite hacker (like z, DoomLord or The_Laser) to check it for us. Maybe this is what they were looking for.
Click to expand...
Click to collapse
It's very possible they already have it...
But i want to look deeper into the hardware.

They knew about that package long time ago in the kernel and bootloader passing thread.
Also, we WILL not have true multitouch cause this type of touch screen does not support it, all it can do is fake the dual touch. (As you see in new Xperia 2012 Sola phone, SONY combines this type of touch screen with new type (Arc type till now) so they can using without touch the screen, you will notice that you can use a soft cloth and touch the screen too)
About 16M colors, I'm not sure cause some source say this screen can display, some not.

silveraero said:
They knew about that package long time ago in the kernel and bootloader passing thread.
Click to expand...
Click to collapse
That means we are missing parts from the puzzle.
Continue voting please..
:edit
Thanks for editing after me hitting thanks.
Others are saying the opposite of what you have posted about the touch input.
We can still use the rest of the files.
Continue voting please..

Just wrote there some words from my heart . Best wishes about this petition. I hope Sony make some surprise for us. I really count on it, cause I wanted it so long, to make my projects better .

DiKeJ said:
Just wrote there some words from my heart . Best wishes about this petition. I hope Sony make some surprise for us. I really count on it, cause I wanted it so long, to make my projects better .
Click to expand...
Click to collapse
I'm out of thanks..
Thanks allot.
we need all the support we can with this.

Oh ya, I wanna vote too but that site require postal code or zip code that my country does not use and keep saying not recognise. What the hell?

Andre Verissimo said:
Please, take a look at
http://developer.sonymobile.com/cws...load/x10x10minix10miniprox8eclair21a0435targz
Click to expand...
Click to collapse
I just had a quick glance over the included kernel, which is of version 2.6.29 (As expected)
It's codename is "Temporary Tasmanian Devil"
As far as I can see with this quick glance, I cannot find any Sony / Sony Ericsson specific patches that might be needed for some of the devices hardware, such as the wireless and camera. The default source from the official kernel is there.
I haven't checked it out thorough yet, but It might be as some of us suspect: Some needed patches or "addins" might not be included at all.
I cannot find any separate patch files either, nor any signs where they could be.
It simply could mean that this included kernel is pre-patched, so someone need to extract these patches by comparing it to standard/official Android Linux 2.6.29 kernel sources.
Someone might ask: -"Isn't it the case that the default/standard Android Linux kernel 2.6.29 is the proper one?"
Well if that was the case, many problems would have been solved a long time ago. We know how hard it was to get the camera, wifi, bluetooth and some other hardware to work properly, as people either needed to pull small parts out of SE's developers, or simply reverse-engineer them.
My suspicion after the quick glance over:
We're having a default Android 2.6.29 Linux kernel without patches.
There's some included code in sub-folders under vendor/semc folder. Glansing that one over, it also appear to be some default sources. Nothing that stands out. But then I'm no expert in this.
I can be completely wrong here, as I just glanced it all over. Please do correct if I'm wrong (Which I hope to be ).

Signed and wrote a few words. I hope to God that our phones could be what they were meant to be or at least could be. Good luck Omega.

voted!!
Hope for the best

thanks guys keep it up.

Interesting comment from DooMLoRD.
yes i know... Sony is ahead of others in this matter... their low end device Tapioca (ST2x/WT2x) is going to have ICS!!! and trust me its going to create a HUGE uproar by users of X10, X10 mini, X10 mini pro, X8 as they have similar hardware to Tapioca...
Click to expand...
Click to collapse
we have better processor and screen than rumoured Tapioca but less ram.

OmegaRED^ said:
This is for the benefit of all x10 Xperia users.
Sign this petition so we can gain any and all source or tools for our x10 from
Sony / Sony Ericsson.
This petition includes libraries for the camera, the screen or gpu and the touch input driver.
Only with your help can we truly make a difference.
http://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-xperiahttp://www.change.org/petitions/sony-sony-erricson-source-code-if-any-available-for-the-x10-experia
Click to expand...
Click to collapse
Will this really work.
Petition signed
Sent from my LT26i using xda premium

THeLogiC said:
we have better processor and screen than rumoured Tapioca but less ram.
Click to expand...
Click to collapse
It's just business. They won't relase official ICS for device which has 3 years. Of course it's possible, but then they won't sell newer devices from 2011 or 2012 line. All what they can do is give us sources - then we start magic .
BTW: I can tell that many polish people signed on this petition - I think my forum made a trick . Thank you all patriots!

Hoping this comes to life
Sent from my X10S using xda premium

NVDIA TEGRA Documentation to be Released

Will this help development of ICS and JB ROMS? http://www.engadget.com/2012/09/23/nvidia-to-offer-up-documentation-for-tegra-graphics-core/
This should solve the video camera issues and other issues I think.
It's the documentation for the Tegra chips.

Looks like a good news and a bit of light for ICS+JB for our Atrix. Lets keep waiting...

No idea, but good find nevertheless.

Assuming this is released, what else will be needed to release a stable CM9?

It really depends on whats is going to be released. We don't know if its going to be useful yet.
Sent from my MB860 using xda app-developers app

Yeah it will help even to make better kernels, is a shame that my Atrix touchscreen died totally two days ago (thread reported will move soon, does not belong here).

RAFAMP said:
Assuming this is released, what else will be needed to release a stable CM9?
Click to expand...
Click to collapse
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms

hainguyen273 said:
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms
Click to expand...
Click to collapse
Thank you for your replies, guys!
So, with the graphics drivers into the kernel we would get 100% working roms?

RAFAMP said:
Thank you for your replies, guys!
So, with the graphics drivers into the kernel we would get 100% working roms?
Click to expand...
Click to collapse
Yes.

fviero said:
Yes.
Click to expand...
Click to collapse
I hope it's soon then!

hainguyen273 said:
Once Tegra2 graphic driver source is released, Atrix devs then just simply update and compile the expecting module (.ko file) to put into the kernel of their roms
Click to expand...
Click to collapse
I'm not particularly knowledgable about the ins and outs of Nvidia's modules so I might be wrong here, but I seem to recall a dev on this forum saying that is wasn't just a matter of the binaries being compiled against a different kernel (which could be worked around if it was just version checking), but that it depends upon functionality that only exists in newer kernel versions.
If somebody on this forum were skilled enough/had the time to donate to port the Nvidia 3.1.10 sources to the Atrix, we could have fully functional ICS/JB today. But it's not reasonable to expect the few skilled kernel devs here to make up for Motorola's slack.
Over in the One X forum, richardtrip has ported the reference 3.1.10 kernel using only a few bits of hTC code for the camera, so it is certainly possible for somebody without 'inside knowledge' to do, but it has taken him months of hard work. (we're on 2.6.39 'till hTC's official jellybean drops, which uses a 3.1.10 kernel anyway)

Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?

thantos said:
Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?
Click to expand...
Click to collapse
The phone would probably be functional without a fingerprint driver, though.

This is not kernel module source they are releasing; they are just saying they are willing to provide more information to the opensource community. NVIDIA has recently indicated they may provide documentation to those working on the nouveau drivers (opensource NVIDIA PC drivers); under an NDA. Meaning that they will provide the documentation to those that work on the opensource driver but not allow the information to be shared. For this to be helpful we would need the documentation provided to someone who is working on opensource Tegra drivers; which I do not believe there is anyone. So this would probably be picked up by those working on the nouveau drivers. Best case if all the information is provided and they decide to work on it it would probably be at least a year before we would have anything stable for use.

thantos said:
Well.. there is still the matter of the fingerprint scanner beyond the kernel. But we can't get too greedy now can we?
Click to expand...
Click to collapse
Yeah, same for the lapdock.
Enviado desde mi MB860 usando Tapatalk 2

[Q] Is it as simple as compiling cyanogenmod?

Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.

evodev said:
Would it be as simple as compiling cyanogenmod for a new phone? We have official builds for my phone (lg Optimus g), and various other AOSP based projects. The main reason I am asking is I have compiled cyanogenmod night lies before, and this looks very interesting so I want to try to get it working on my phone.
Click to expand...
Click to collapse
It is

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Just a quick question,will it support mediatek devices?

s.sawrav said:
Just a quick question,will it support mediatek devices?
Click to expand...
Click to collapse
Yes.
We have early support for the r819.

I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.

Mayank7795 said:
I hope OmniROM is also meant for devices with low specs like for my Xperia U. I am interested to try it as a user.
Click to expand...
Click to collapse
If you have a working AOSP, it should be available without problems.

@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers

What about devices that have CM10 only?

lozohcum said:
What about devices that have CM10 only?
Click to expand...
Click to collapse
You need at least an unofficial CM 10.2 / AOSP 4.3.

JoinTheRealms said:
@XpLoDWilD
Would it be worth me attempting to build this for the tf700, or do you guys have plans for it?
Cheers
Click to expand...
Click to collapse
Building is always worth an attempt...
I used to build my own CM, i'm gonna try to build my own omni too but i'm struggling. I must be doing something wrong with the repo init but I can't seem to find what... I'm gonna update my buildbot first because it's been awhile, and maybe try again tomorrow.

As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
That's why its worth scrawling through XDA, going through guides and learning to dev. Nothing wrong with a dev who decides to leave an older version for a newer version. They're doing it for fun and free.

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
As long as there is no hard reason to stop supporting a device and we have someone who is taking care of that device we will try
On the other side - there is constant evolution which sometimes will make it necessary to leave a device "behind" if the effort will become too large
Sent from my Find 5 using xda app-developers app

XpLoDWilD said:
It is
Click to expand...
Click to collapse
Not quite yet... Not until we have roomservice up and running.
(For those that didn't understand what I said - roomservice is the part of CM's repo management system that will automatically sync a device tree and all dependencies. roomservice is HEAVILY dependent on github's APIs, so we couldn't even start work on that particular piece of infrastructure until the project went public.)

lozohcum said:
As always everyone forget about non-highended devices and lower android versions. Everytime new android version appers, all devs greedily jump on in and start making roms only for it. Nexus 7, Xperia Z/Z1... I vomit. And of course experienced devs are not willing to share their's knowledge about device maintenance
Click to expand...
Click to collapse
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.

mattman83 said:
The reason for the Nexus/Xperia Z support is because the vendors have AOSP source for pretty much the entire device readily available. The Xperia Z series (Z, Z Tab, Z1) have source widely available for (IIRC) pretty much everything bar the radio. Heck - sony had uploaded AOSP 4.3 sources before CM had 10.2 nightlies running, from memory.
Anything beyond that boils down to porting existing patches, or people bringing up other devices. This will generally happen for more widely used devices first simply because there's more likely to be someone available with the skills to do it. By the sounds of Omni is working, you could have pretty much any obscure old phone but if you're happy to do the bringup then it'll get added
M.
Click to expand...
Click to collapse
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance

pulser_g2 said:
I actually have a plan about getting legacy devices involved in the form of a "legacy branch" complete with legacy maintainers. It's tricky to get started off, but might prove useful for anyone wanting to get longer community support for their devices.
Click to expand...
Click to collapse
I hope the Acer IconiaTAB A5000 will get supported.

Please, support for RAZR i (x86)

lozohcum said:
Someone should write a definitive guide about converting CM10 device tree to AOSP JB device tree, so more people can work on devices maintenance
Click to expand...
Click to collapse
Problem is, every device has its own pitfalls. Some are harder to overcome than others.
For example, the lack of NEON in tegra2 combined with the dependency of newer gapps on NEON really screws tegra2 devices, and there isn't much that can be done about it.
Also, in some cases, the things needed to get a device working aren't in the tree, but are in the frameworks to handle OEM-specific oddities (RIL hacking in opt/telephony, which I admit I'm not too familiar with...) or platform support. Sometimes, old devices get left behind simply because their platform overall is a ***** to support beyond a certain point. (See how MSM8660 devices have been lagging lately, due to Qualcomm pretty much sunsetting that chipset.)

[DEVTALK][CM13/AOSP for the Z4/Z3+]

a-st said:
Hi jerpelea,
I've managed to compile AOSP with latest binaries for my Xperia Z3+ Dual (E6533) but I still have graphical glitches and no dual SIM support. Any hints so far?
EDIT: Please find recovery and ROM here: http://d-h.st/users/a-st/?fld_id=49625#files | Gapps can be used from here: http://opengapps.org (I did choose arm64/6.0/nano)
Flash recovery (Link: http://d-h.st/r94k)
Boot to recovery
Flash ROM (Link: http://d-h.st/7ZlB)
Flash Gapps (Link: http://opengapps.org (I did choose arm64/6.0/nano))
Reboot
Best regards,
a-st
Click to expand...
Click to collapse
Kernel-side:
https://github.com/sonyxperiadev/kernel/commit/ec71e11b61f16205f3bcb61009157869ec35739e defconfig: unify dual sim kernels
so you essentially use aosp_kitakami_ivy_defconfig
https://github.com/Sony-Kitakami/an...mmit/00b98dfa216074615c744fbb3822d2130f343965 dsds support
(device/sony/kitakami)
https://github.com/Sony-Kitakami/an...mmit/0299b4320dc69ae03329db7818c444e3d3d01784 manual approach to satsuki DSDS models
well yeah, you either need a sophisticated "wrapper" or do an additional folder for the dual sim model,
in that repo I currently do an experiment and simply renamed it to see whether it goes through
@a-st
How much experience do you have with development ?
Kernels ? ROMs ?
edit:
the basics and groundwork is already laid out,
three kitakami devices already work,
ivy would be the fourth,
so you'd need to essentially clone/fork the device from sonyxperiadev:
https://github.com/sonyxperiadev/device-sony-ivy
and sync with the changes in our devices (sumire, satsuki, suzuran).
A few guides:
http://xda-university.com/as-a-developer/porting-aosp-roms-using-source-code
http://xda-university.com/as-a-developer/getting-started-with-git-version-control
knowing how to work with git and do proper commits and keeping authorship or assigning the author is a must,
git remote add/rm, git cherry-pick, git commit, git add -A, git status, git fetch, git push, git merge
are the most common basics.
Also knowing how to do git push (pushing branches) and NOT overwriting existing commits is rather helpful
(don't worry it's easier than it sounds)

Thanks for your fast response I never did kernel / ROM development but might find some time to get into it.
I'll try your suggestions. I already cloned ivy to ivy_dsds and did some few modifications which worked fine but without dial SIM support.
Also I'm not totally new to git, but I could need some practice. At work we currently use mercurial which behaves a bit like gut I think.
Looking forward to get CM on our beautiful devices. Thanks for your help so far and keep on going. Maybe we could find some time and could start a little IRC discussion?
Best regards
a-st

Hi @zacharias.maladroit
I managed to fork existing device tree and merge it with ivy config. Currently it's located at https://github.com/a-st/android_device_sony_ivy_dsds
Maybe we could have a look into what else needs to be done?
Are you using IRC? Maybe I could join your channel
Best regards,
a-st

what still not work? thanks u

Alekim91 said:
what still not work? thanks u
Click to expand...
Click to collapse
Even when a successful build is made camera will not function properly. Sony are taking a longgggg time to fix there aosp camera

LMcR92 said:
Even when a successful build is made camera will not function properly. Sony are taking a longgggg time to fix there aosp camera
Click to expand...
Click to collapse
okok well, but dual sim work?

nothing news for cm?

LMcR92 said:
Even when a successful build is made camera will not function properly. Sony are taking a longgggg time to fix there aosp camera
Click to expand...
Click to collapse
This is very disappointing and pathetic from Sony. The camera does not need to be fixed. This is something different. If the camera was the issue the we'd need a fix. It's just that they do not want us to have the camera drivers. They did this on purpose that's why I would not call it a fix. They decided to allow us build an AOSP rom but they are retaining the drivers and camera configuration. If there was a real issue in the camera that is being investigated I would not call this a fix that's why I am not asking for a fix but I am asking sony to give us the camera source files so we can do what they refuse to do.
I am a regretful Xperia Z4 owner. They promised they would support AOSP and they failed to do it. This is my last Xperia Phone I swear.

Jahdiel2011 said:
This is very disappointing and pathetic from Sony. The camera does not need to be fixed. This is something different. If the camera was the issue the we'd need a fix. It's just that they do not want us to have the camera drivers. They did this on purpose that's why I would not call it a fix. They decided to allow us build an AOSP rom but they are retaining the drivers and camera configuration. If there was a real issue in the camera that is being investigated I would not call this a fix that's why I am not asking for a fix but I am asking sony to give us the camera source files so we can do what they refuse to do.
I am a regretful Xperia Z4 owner. They promised they would support AOSP and they failed to do it. This is my last Xperia Phone I swear.
Click to expand...
Click to collapse
100% agree, last xperia phone for me aswell.

Jahdiel2011 said:
This is very disappointing and pathetic from Sony. The camera does not need to be fixed. This is something different. If the camera was the issue the we'd need a fix. It's just that they do not want us to have the camera drivers. They did this on purpose that's why I would not call it a fix. They decided to allow us build an AOSP rom but they are retaining the drivers and camera configuration. If there was a real issue in the camera that is being investigated I would not call this a fix that's why I am not asking for a fix but I am asking sony to give us the camera source files so we can do what they refuse to do.
I am a regretful Xperia Z4 owner. They promised they would support AOSP and they failed to do it. This is my last Xperia Phone I swear.
Click to expand...
Click to collapse
Would you kindly please stop spreading FUD ?
Nothing is being withheld, the camera driver is continually being updated and reworked,
the binary drivers (blobs) have meanwhile several times been updated (including calibration data),
the issue with Sony's AOSP is that it's essentially a one-man army in close work with the community (other devs NOT paid by Sony).
From what I read there' a fisheye issue (still ? already fixed ?) with pictures taken on AOSP-based ROMs compared to Stock
where there's a light fisheye effect on the taken picture cause the lens doesn't match compared to a different Xperia device which uses a similar sensor but a different lens,
this can be fixed by using an algorithm that takes into account of this and makes the taken pictures appear properly.
All source code is available - it's in the hands of capable devs to "fix" it,
so the thing you're demanding is already there.
If you're ranting - mark it as such but please do not spread untruthfulness or lies of any kind

zacharias.maladroit said:
Would you kindly please stop spreading FUD ?
Nothing is being withheld, the camera driver is continually being updated and reworked,
the binary drivers (blobs) have meanwhile several times been updated (including calibration data),
the issue with Sony's AOSP is that it's essentially a one-man army in close work with the community (other devs NOT paid by Sony).
From what I read there' a fisheye issue (still ? already fixed ?) with pictures taken on AOSP-based ROMs compared to Stock
where there's a light fisheye effect on the taken picture cause the lens doesn't match compared to a different Xperia device which uses a similar sensor but a different lens,
this can be fixed by using an algorithm that takes into account of this and makes the taken pictures appear properly.
All source code is available - it's in the hands of capable devs to "fix" it,
so the thing you're demanding is already there.
If you're ranting - mark it as such but please do not spread untruthfulness or lies of any kind
Click to expand...
Click to collapse
You're wrong, If sony want us to use the camera they would have released the specific camera configuration for each device. As they did in the past. I have had several xperias since the X10 there is a specific kernel configuration to use the camera drivers properly. It is not new for devs community that OEMs release sources but not everything at once. The algorithm you mentioned that they will never release is to IMPROVE picture quality not to take a normal decent picture. If you do some research you will see of devs complaining due to Sony not releasing all the drivers for kitakami devices.

@zacharias.maladroit @a-st, guys, I'm not familiar with coding/compiling/fixing stuff, but I'm not a noob neither. Never tried to compile ROMs before by myself/alone, but want to try - I'm in. Need tester/dev - just let me know. I have Ivy (E6553).

MotexT said:
@zacharias.maladroit @a-st, guys, I'm not familiar with coding/compiling/fixing stuff, but I'm not a noob neither. Never tried to compile ROMs before by myself/alone, but want to try - I'm in. Need tester/dev - just let me know. I have Ivy (E6553).
Click to expand...
Click to collapse
Take a look at http://forum.xda-developers.com/xperia-z4/general/guide-cm13-z4-z3-build-t3403776
and
http://forum.xda-developers.com/xperia-z4/orig-development/rom-cyanogenmod-13-e6533-t3451524
what repos Quarx e.g. uses
Sorry can't help since after several attempts and combinations of repos CM13 still wouldn't boot for me with the new 1.3.3 kernel
Also currently can't focus more on it ...

@zacharias.maladroit just try to use different toolchain, when I worked with @moonbutt74 on CM build we faced the same problem, and it was fixed once by changing toolchain. Just give it a try. Also can recommend to use FXP AOSP kernel as base, even with a lot of limitations the new kernel seems to be a really stable and fast (tested by me on everyday scenario during 2+ weeks) - no charging issues, no random reboots, no heat at all.

Any one know who is the maintainer of AOSPA build is?

LMcR92 said:
Any one know who is the maintainer of AOSPA build is?
Click to expand...
Click to collapse
FXP Team

[email protected] said:
FXP Team
Click to expand...
Click to collapse
Not at all. FXP works on AOSP, when Paranoid Android team works on AOSPA. AOSP and AOSPA are different things, and are maintained by different teams, don't mix them.

Sony releases concept software kernel sources

available here: http://developer.sonymobile.com/dow...hives/open-source-archive-for-mob30m-z1-3636/

Still doesn't do us much good as long as they're keeping the proprietary features under lock and key. For as much as Sony tries to "support developers and open source software," giving us a neutered ROM doesn't get us much farther than we already are.

hikihibiki said:
Still doesn't do us much good as long as they're keeping the proprietary features under lock and key. For as much as Sony tries to "support developers and open source software," giving us a neutered ROM doesn't get us much farther than we already are.
Click to expand...
Click to collapse
they do that so you will be forced to buy their next flagship phone that includes the next android upgrade, hence the z3c not getting nougat. It's plain to see....otherwise a lot of users wouldn't buy the same exact phone with minimal hardware upgrades every few months they release a new phone. I'm just fine with MM here and i will prob keep my z3c for the next few years unless the horrible build quality catches up to me.

Fictional Reality said:
they do that so you will be forced to buy their next flagship phone that includes the next android upgrade, hence the z3c not getting nougat. It's plain to see....otherwise a lot of users wouldn't buy the same exact phone with minimal hardware upgrades every few months they release a new phone. I'm just fine with MM here and i will prob keep my z3c for the next few years unless the horrible build quality catches up to me.
Click to expand...
Click to collapse
Probably the Z3 and the Z3C won't get Nougat is because of data encryption and because Qualcomm stopped making Adreno 330 drivers there won't be Vulkan support,and I am not sure would it be easy to make Nougat anyways without GPU drivers

With this sources, we can make a cleaner rom (like SLiMM), near AOSP and with great stability. I will take a look at the code. I invite @Wajk, @Gustavo RD78 and @Marília de Oliveira to look at it too.
The kernel source can be downloaded here
The rom itself can be found here

juliopw said:
With this sources, we can make a cleaner rom (like SLiMM), near AOSP and with great stability. I will take a look at the code. I invite @Wajk, @Gustavo RD78 and @Marília de Oliveira to look at it too.
The kernel source can be downloaded here
The rom itself can be found here
Click to expand...
Click to collapse
Ehh seems like a more out of date kernel when compared with the .291 source, which is almost fully up to date with branch LA.BF.1.1.3_rb1.13 (latest supported codeaurora branch for msm8974) whilst Concept is quite behind on many newer commits.
Other notable differences are like commits from AOSP such as partial resume support already included, and seccomp used instead of Sony RIC (obviously, being based on AOSP).

@tomascus can these features be ported to this kernel or is it too much trouble?

juliopw said:
@tomascus can these features be ported to this kernel or is it too much trouble?
Click to expand...
Click to collapse
Yeah just simple cherry picking:silly:

thanks

They posted the code of the 3657 build
http://developer.sonymobile.com/downloads/all-downloads/open-source-archive-for-mob31e-z1-3657/