Related
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.)
Hello Guys,
welcome to the world of Team-Exodus.
What is Team-Exodus ?
We are a small group of entusiasts that like to learn more about Android and the Android-ROM developement.
We aren't exactly beginners But there is still room to learn more (you never end learning).
What is Exodus-Rom ?
Maybe, we better should start, what Exodus-Rom isn't: It isn't a (semi)professional mainstream ROM like CyanogenMod,AOKP or similar Roms. We don't focus on buzzword features, nor are we into "bling bling" options. We don't need a "change clock color" option, just because we can do it. These are "low hanging fruits", something nearly everybody can do, who has a computer to compile Android.
So what is Exodus-Rom, what is our focus on ?
We mainly focus on learning how things can be done. We are more into "quality over quantity". We prefer to have 4 or 5 real good and stable working features and not 20-30 features that work... somehow... sometimes...
We want performance, a fast, smooth fluid UI, a real good user experience, not a overbloated kang rom.
For instant that's the main reason why we currently don't have a Marshmallow Rom online, but I will give you a little more information regarding Exodus-6.0 (marshmallow) later.
But before that, who are we, who is "Team-Exodus" ?
The core team of "Team-Exodus" consists of the following guys:
@PrimeDirective - Dave, a very talented developer from the US, founder and Team Leader of Team-Exodus, specialist in App developement (for instant our Exodus Updater or the Drop Wallpaper App) and also our specialist for in deep functionalities of the Android Rom (like a complete rewritten Navbar customization). He currently uses bacon (Oneplus One) and Flounder (Nexus 9) for developenemt
@Raja.M - Raja, a real nice guy from India, he is our java specialist, he started Android developement something link 6 month ago but his knowledge is fast growing. He developes on the bacon (Oneplus One)
@TheCrazyLex - Alex, a kernel specialist from germany, he joined Team-Exodus like 3 month ago, mainly responsible to optimize and unify our kernels where possible. He also uses the Bacon (Oneplus One) as developement device.
@usmcamgrimm - Adrian, our graphics and theme specialist. Beside his amazing wallpapers, he is also responsible for all our LGE G3 devices. He mainly developes on the VS985.
@Martin_Ro - myself, Martin, also from germany, mostly responsible for the server with the build system, gerrit and download page. I'm also developing here and there if I find some time as I'm a married guy with to young boys. I'm developing on shamu (Nexus 6).
But beside this core team, there are a lot more ppl that help us making the Exodus Rom as amazing as possible, I will add some more of them step by step
So, now, back to Marshmallow and why it takes so much more time to bring an Exodus-6.0 to you guys:
For this to understand, you need to know more about where we come from.
On late 2014 we (Dave and Me) parted from VanirAOSP (that wasn't really AOSP but also used CM as base at that time btw) because we feeled like it started to get more and more into that mainstream "feature count is everything".
With 5.1 we started to directly use CyanogenMod (cm-12.1) as base, but was somewhat annoyed by upcomming issues because they used their open source branch as testfield for unfinished stuff, so for 6.0 we decided to go as near as possible back to strict AOSP.
But a matter of fact is: With strict AOSP you aren't able to support every device, and not as many devices as we want to support. So we have had to make some decisions and try some stuff. In the end we started developing Exodus-6.0 with a Mixture of strict AOSP and CAF as base, with the really amazing wide support of CyanogenMod regarding devices.
But with this, we got back to one of our main concerns: CyanogenMod is doing a fantastic job regarding device support (nobody can beat them in that department) but they are cluttering their stuff more and more. In the past few month, they started to create their own SDK, their own framework. And their SDK started to grow like a octupus, sticking his arms into every aspect of android. But we don't want to use their sdk, so we needed to remove it from everywhere.
And that was, what took so long. We wanted the device-tree and their hardware layer, but not their feature, and for sure not their SDK. And removing that stuff from everywhere inside the device-trees and Hardware layer.
Also we needed to use some of their code stuff in various places to make the connection between our AOSP/CAF based ROM and their hardware/device stuff.
So that took us nearly a month to finish up, but now we have first working experimental builds for bacon, shamu and VS985 so we can go into the real developing stuff.
There is still a lot to do (bring back all the features we want to, make the rom that fluid that you might be used to from EXODUS-5.1 etc.) But the real hard part is done now and we are way neared to a first public beta. Depending on the time Dave can find for Exodus (he is really really busy currently because of a new job), we expect to have a public beta by the end of the month...
So stay tuned and be patient
Made sticky
Hello! I enjoyed the 1/2 of the core team's and the new teams work since JB VanirAOSP to Exodus .
Just wondering, it would be cool to say what you do to seperate you guys from the rest. I know you guys build with jdk8 instead of jdk7 for the lollipop builds and use Linaro with some optimization flags.
I'd like to know if you do more than that and also I am wondering how JDK8 especially helps with optimization.
If you need a tester for bacon. I'm here very big fan of 5.1.
Nice to hear the updates... waiting patiently...
Sounds like the beta will become a christmas present.
Gesendet von meinem Nexus 5 mit Tapatalk
big fan/user of Exodus 5.1 on falcon. out of all the LP ROMs i've tried this has to be one of the most stable and lean ROMs out there. love the amount of essential customization catered here and skipping of cliche features that no one bothers to use (atleast me).
big thanks to @sachoosaini for introducing me to the ROM.
Well here it goes on
@PrimeDirective always a great human and great developer who supported Falcon despite the fact that i can never able to contribute the device to you. I find a best buddy out there who will always be my friend... Now @koshikas thanks Dave for supporting this phone, i never did anything for exodus.. But i am committed for future. If Dave continues the journey for exodus i will be with him in all way... Well what he told me around 6-7 months back is now coming to the real world. Now they support falcon or not. But I am honored by Dave for being there with all the silly questions people ask in community, falcon has great life indeed now its upto the team they develope for it not. I will donating device as soon as I am getting my salary which i am for sure going to get soon..... Wish Luck to exodus....6.0 is on the horizon
If you need a tester...
Hey, if you guys need an experienced tester for bacon, look no further. :good:
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I'm with this guy
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Coolkid90 said:
Where do I go to look at the rims ?....dir a HTC m8 Sprint
With S-on
Click to expand...
Click to collapse
Hm, ok, might be, because english is not my mother language, but for me this sound like "too much drugs and not enough sleep"....
Oh, and by the way:
we just prepared the open source manifest so you can start contribute
I will write a short Facts thread for Exodus-6.0 so you know how to build, and what we changed regarding device-support...
Excelente
Looking real forward to Exodus MM!
sir I am with you here.
AndroidPr0 said:
Hey, if you guys need an experienced tester for bacon, look no further. :good:
Click to expand...
Click to collapse
I m new here and wish to get some knowledge from senior member.
Thanks for this great rom
Exodus seems cool... hyped for MM release!
delete : found it
"err on the side of kindness"
Hi guys
Only to keep you informed: We started publishing official release builds for Exodus-6.0.
Look into your devide Android Developement sections for more information or on our g+ community: https://plus.google.com/communities/106801227383087889476
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.
Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, skip the MM release and create the maybe last ROM update for our beloved XZ1? A release of stock based N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:
wrong forum, xperia z1 won't have a stable MM ROM........................
->--- said:
Hello dear developers,
I think some of you know, that the XZ3 is in the Android preview program for Nougat. https://developer.sony.com/develop/smartphones-and-tablets/android-n-developer-preview/
As far as I can see in wikipedia the hardware of Z1 and Z3 are very similar. The Z3 is the last of the Z series with very similar hardware.
Because there are so many Xperia devices, the community of developers is very thinned out. There is not even one MarshMallow release which is running without problems until now and Google is already short before releasing Nougat.
Sadlly I am no developer on my own. I already fail at creating the necessary Linux environment. But there are many great developers and skilled people here on the forum. Wouldn't it be a great idea that you bundle your skills, jump over the MM release and create the maybe last ROM update for our beloved XZ1? A release of N.
It is just an idea, but it would be great if some of you would capture the idea :fingers-crossed:
Click to expand...
Click to collapse
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work for the Z1, but I think you're beating the dead horse at this point.
kentexcitebot said:
I've wondered for a long time now: you talk crap about Sony's software, complain about their blobs being 'crap', and claim Sony isn't friendly to OSS, yet you continue to develop and deploy custom ROMs for the Z1. If it's such a hurdle to develop, why not move to a developer friendly platform/device like the Nexus 6P? I appreciate your work, but I think you're beating the dead horse at this point.
Click to expand...
Click to collapse
LP 5.1 is pretty good. It is better than stock. Today I replaced the rear camera module (the old one stopped focusing) and camera is superb. No bugs in LP.
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it. I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
Security updates are coming and lp will be supported for a long while. Normal users don't care about versions either. They want a stable device and they get it in LP...
optimumpro said:
I may move to Nexus, but the phone I buy has to be metal or glass, plus Z1 has enough life ahead of it.
Click to expand...
Click to collapse
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
I don't care about M or N. From my point of view, Google changes SDK, so that prior features won't work, and in exchange gives us a few different icons and slightly different interface.
...
Normal users don't care about versions either.
Click to expand...
Click to collapse
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
Security updates are coming and lp will be supported for a long while. They want a stable device and they get it in LP...
Click to expand...
Click to collapse
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).
kentexcitebot said:
The OnePlus 3 is the next best developer-friendly platform after the Nexus devices. Warranty doesn't go bad if you root or unlock bootloader. It even got CM 13 before launch! It also happens to have a metal back, 16MP shooter with OIS, and everybody's favorite 'Dark Mode'. I don't mean to advertise, but for $399, I'd say that's a great bargain. Don't get me wrong, the Z1 still works beautifully when all is OK, but it's really starting to show it's age: your device's rear camera module stopped focusing until you replaced it, several user's battery in the Z1 (not just on XDA) is going bad, and my Z1's touch digitizer has issues on tap (probably from abuse, but people reported self-cracking screens with their touchscreens completely broken). Not too many people want to go through the trouble of sending it in (to China?!) or fixing it themselves.
Um, what? According to many tech sources, that's the highlight issue with Android: fragmentation. If you wanted to know Android's biggest problem, this is it. In fact, people (including some casuals) blast Android because of this. Maybe you don't care about Android versions, but if you stick with LP or an older platform, you're contributing to the problem.
As you can probably tell, I've already switched to a different device: a OnePlus 3. Oxygen OS 3.1.3 (6.0.1 Marshmallow), from experience, is quite stable and is developed by the team behind Paranoid Android. Sure, LP's code is more stable because it's been out longer and has more revisions, but it really depends of how you interpret the term (because I've experienced no crashes or FCs so far on MM). I'm fine if you continue holding the torch for Z1's AOSP/CM ROM community and keep LP more secure/stable for them, but I find it a bit redundant as most users have already moved away from this device and transitioned to MM (and even N DP4).
Click to expand...
Click to collapse
Fragmentation has nothing to do with Android versions. Neither Android version has done anything to reduce fragmentation as compared to the previous one. It is the fact that there are hundreds of different devices with varieties of hardware. However, different hardware does not create fragmentation. Unlike Apple, Windows and Linux work on many devices. The problem for Android is that manufacturers don't want to provide hardware addresses (to make open source drivers) or blobs to work with hardware. The question is: why manufacturers provide the necessary info for Windows and Linux, but refuse the same with Android and mobile devices. And I am yet to hear an answer to this...
optimumpro said:
None of Xperias will have stable custom roms above LP 5.1.1, because everyone has switched to AOSP trees. Sony blobs are protected by DRM, so, they won't work with camera wrappers and Sony's blobs for AOSP have always and will continue to be crap. Sony doesn't want you to have custom roms. So, think of developer friendlier manufacturers. This crap about Sony being friendly to open source is just that. Their open source developers are just PR people. Sony AOSP has never had a stable rom: not for JB, not for Kitkat and not for LP...
Click to expand...
Click to collapse
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Would you have any test build that could be tried out? I'd love to test it out...
olokos said:
Actually, they have been doing a lot of work and are very friendly about AOSP. MM already has a working camera if you use 1.2.2 kernel. The only issue there is zoom focus and application restarts when switching between front and back camera, but apart from that everything works well. Sony is being very developer friendly and you can't take that away from them.
Click to expand...
Click to collapse
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...
optimumpro said:
Doing "a lot of work" and having stable releases, which they have never had on any android version, are 2 different things. Aren't they? Camera aside, how about random reboots, blank screen issues, failure to wake up, battery drain, slow charging, overheating: what more do you need? And by the way, you think camera focus is the only issue? I bet a lot of users would disagree.
We are almost in August. Last year this time LP 5.1.1 was pretty stable. No chance for MM and N is already here...
Edit: My opinions about MM and Sony shouldn't be taken as criticism of Sony open source developers (who work their butts off) or any other devs (myself included) who contribute to the code, but rather Sony Corporation itself. Sony doesn't want you to have custom roms.
If I am to blame community developers, then it would be for abandoning stable releases like LP 5.1.1 in favor of undercooked new ones like MM. That's double stupidity, because in addition to starting from ZERO, they are following (instead of leading) teenage users who would rather have a slightly changed "cool" user interface, as opposed to a rock solid stable release...
Click to expand...
Click to collapse
but, like you said, lollipop are stable, why still develop for it?
brickhayabusa said:
but, like you said, lollipop are stable, why still develop for it?
Click to expand...
Click to collapse
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...
optimumpro said:
Because stable and maintained are different things. Stable becomes outdated if not further developed. For example, all abandoned LPs are now outdated and shouldn't be used...
Click to expand...
Click to collapse
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..
Snp Mania2 said:
Then why xperia M is really awesome, they have a official cm13 nightly still updte every day, n now they're will building for awaken the Nougat, already tested n booted with Alpha release now,
it all by they devs is superior or factor xperia M devices are supported?
Will realy glad if Honami can like them..
Click to expand...
Click to collapse
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.
optimumpro said:
Because they are probably using 3.4 kernel together with older camera blobs. In case of honami, they have decided to move to 3.10 kernel and the newer good blobs are drm protected. And they are waiting for Sony aosp to improve 3.10 blobs, which should happen in the next 50-100 years. Because of this, CM is not working on honami. That's why there is not even one nightly MM for Z1. And since other "big" guys can only cut and paste from CM, there is nothing for Z1.
Click to expand...
Click to collapse
Sorry for this one sir,
This screenshoot i take from xda fecebook via someone of member z1 indonesia FB group, but i dont OP like u so i not understanding it, pls help for read that post at this link...
http://developer.sonymobile.com/build-aosp-nougat-7-0/
EDIT: looks like z1 never to be the Nougat :crying:
from here: http://www.xda-developers.com/sony-...g-aosp-7-0-nougat-for-its-xperia-smartphones/
looki looki!!!!
http://uploaded.net/f/ikvebh
santeria27 said:
looki looki!!!!
http://uploaded.net/f/ikvebh
Click to expand...
Click to collapse
U have try that rom?
No tested!!!
Sent from my Xperia Z1 using XDA-Developers mobile app
santeria27 said:
No tested!!!
Click to expand...
Click to collapse
Haha . Even i cant download that .
Spent 2 hours for downloading this.
Mirror: https://drive.google.com/open?id=0B5NqkvihftQXSDI5Vl9Na2h6ak0
Hey guys. I came over to see how many ROMs this phone has, and I was astounded to see the forum empty. Since this phone is supported by the open device program, I'd have thought there would be a vibrant developer community.
What's up with this? No developer interest?
Z5c is also supported by AOSP and there's also not much custom ROMs I guess so far biggest issue is this device is quite new and not so many devs bought it
That's surprising. It's the first time I've seen a device with full kernel support but still not much development.
Usually it's the other way around. Sources are fudged or not released, but developers still find ways to work around it.
andy356 said:
That's surprising. It's the first time I've seen a device with full kernel support but still not much development.
Usually it's the other way around. Sources are fudged or not released, but developers still find ways to work around it.
Click to expand...
Click to collapse
yeah the device is very good for development even better than Z5c because it does not have any heating issue, but still nothing
I guess we should wait and see if android 7 makes any difference...
Sony wiping camera keys at the time of bootloader unlock (the camera is a huge selling point for the phone) might have to do with this, it's very likely that devs would want to get TA backup working before focusing on developing ROMs for the phone. But since there aren't any devs here working on that either, we might simply have been doomed as well. The only custom ROM I've found so far was an AOSP Marshmallow build made by FreeXperia, plus Sony's device files released for building AOSP M and N.
Also supposedly 7.0 is around the corner so the few that are thinking about roming may be waiting until after its release. Time will tell.
I think the XC will get zero dev support. You can kinda see a trend in the developers support: I had the z3c which had tons of support, now when I look at the z5c forums there are only very few roms, and for the xc not even one developer has posted something yet. until it won't get easier to unlock and root the xperia phones without messing up the DRM protection there won't be a lot of support. I'm thinking about buying the z5c just for that reason.
:/ This is so bad on Sony's part. They try to give the impression that they're so pro development and pro custom ROMs, but then they mess up the camera if people actually want to do something.
andy356 said:
:/ This is so bad on Sony's part. They try to give the impression that they're so pro development and pro custom ROMs, but then then they mess up the camera if people actually want to do something.
Click to expand...
Click to collapse
if someone doesnt find a exploit to root on locked bootloader then nobody will be able to backup ta data. i wont buy a sony phone if rooting means loosing features of the phone.
z3c has support because the giefroot was once found and this enabled all dev to backup ta data with drm. even if they decided to unlock bootloader they were still able to restore ta and lock again bootloader.
sony's aosp way is almost useless for the majority of people. when samsung was at s1/s2/s3 you could flash what you want and no feature was lost as they was nothing related with drm but now there you also have knox and efuse. if you root you will even loose guarantee and this is not reversible.
I guess it's better to look for a Z3 Compact then. I don't want to deal with this DRM nonsense.
Thanks for all the info, guys. I appreciate it.
andy356 said:
I guess it's better to look for a Z3 Compact then. I don't want to deal with this DRM nonsense.
Thanks for all the info, guys. I appreciate it.
Click to expand...
Click to collapse
i bought a refurbished z3c again and had my battery replaced just because the z5c has this ****ty 810 snapdragon and the x compact a weird vibration motor (too loud) and several other reasons (no root on locked bootloader) and im fine.
ok maybe i get no nougat on this but i dont care because im still on kitkat because this has best battery handling and all apps are still working on kitkat.
Yeah Z5 compact is out of the picture because of the snapdragon 810. Otherwise my second choice after X Compact would have been that. Oh well. Z3 Compact serves the purpose just as well.
x10isrooted said:
i bought a refurbished z3c again and had my battery replaced just because the z5c has this ****ty 810 snapdragon and the x compact a weird vibration motor (too loud) and several other reasons (no root on locked bootloader) and im fine.
ok maybe i get no nougat on this but i dont care because im still on kitkat because this has best battery handling and all apps are still working on kitkat.
Click to expand...
Click to collapse
yeah as long as roms go, xperia x compact is out of choices but this phone is gonna get nougat and maybe android 8(or whatever version it's gonna be) so I would say go for it, Im really enjoying screen quality on this baby
I built CM13 but I'm not allowed to post in the dev section because I'm not cool enough
Source is at github: heicrd (just drop the local_manifests in, lunch cm_kugo-userdebug, mka bacon)
Flash zip with CM recovery (AndroPlus's TWRP doesn't work too well) or flash images with fastboot
I would post build links but I'm not allowed to post links either
Working:
Cellular/Data (had to switch APN from ATT Gophone to ATT Nextphone for my gophone sim in order to get data)
WiFi
Fingerprint Scanner
Camera
BT
SELinux
Not working (PATCHES WELCOME):
FM Radio (/dev/radio0 is missing)
Music (audio_hw_primary: start_output_stream: cannot set device: Invalid argument)
Not tested:
NFC
Encryption
Special thanks to Sony-Kitakami for serving as a reference
@EliWallace That's great news! All you need to become member is 10 posts, which you can easily gain from participating in the forum. Then you can post in the dev section.
It's good to see someone take the initiative. I would have liked to do it too, but my knowledge is limited to Android customisation and adb/fastboot commands. :/
I'm sure the other members here would be willing to give you a hand in beta testing and general feedback.
@EliWallace And please make sure you take care of GPL compliance from the very beginning. Devs and mods here take it very seriously. Don't want to see possibly the only custom ROM being bogged down by such pointless issues. Good luck!
andy356 said:
@EliWallace And please make sure you take care of GPL compliance from the very beginning.
Click to expand...
Click to collapse
Should be fully gpl compliant (source hosted on github: see first post). Most of it is just rebasing Sony-Kitakami commits to Loire/kugo or cherry-picking upstream commits (as described in the Sony aosp build guide; I didn't write a single line of original code).
In other news, Bluetooth works but fmradio does not.
andy356 said:
Devs and mods here take it very seriously. Don't want to see possibly the only custom ROM being bogged down by such pointless issues.
Click to expand...
Click to collapse
As they should.
EliWallace said:
I built CM13 but I'm not allowed to post in the dev section because I'm not cool enough
Source is at github: heicrd (just drop the local_manifests in, lunch cm_kugo-userdebug, mka bacon)
Flash zip with CM recovery (AndroPlus's TWRP doesn't work too well) or flash images with fastboot
I would post build links but I'm not allowed to post links either
Working:
Cellular/Data (had to switch APN from ATT Gophone to ATT Nextphone for my gophone sim in order to get data)
Audio
WiFi
Fingerprint Scanner
Camera
Not tested:
BT
NFC
Encryption
Special thanks to Sony-Kitakami for serving as a reference
Click to expand...
Click to collapse
You're cool enough to me Eli Do you know if the DRM kernel patch work for the XC?
charliebigpot said:
You're cool enough to me Eli Do you know if the DRM kernel patch work for the XC?
Click to expand...
Click to collapse
Interesting that the camera is working on your build. I build Aosp 7.0 and everthing is working but not the camera and deep sleep (only if bluetooth is enabled, but i think they have fixed it today).
You are mixing the kernel (from android 6.0/7.0) with device tree from android 7.1 and the camera is working.
@EliWallace Post 6 of the most random comments here if needs be. We need you in Dev asap
Great work!!