Related
Great news sony is just like xperia s working on aosp project
http://developer.sonymobile.com/201...r-xperia-z-on-sonys-github-open-source-video/
This would definitely help us!
Yep. Some of the devs doing apps and kernels for the device would probably be helped even more than us, and if they send fixes to the repo Sony could be helped as well.
Open source. It works, *****es!
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
As I understand it, CM usually uses proprietary blobs (binaries) extracted from the device they are building for, rather than open source alternatives coded by the community.
AOSP aims to use all open source code.
Someone correct me if I'm wrong
Sent from my C6603 using Tapatalk 2
Hi Entropy, could you help answer a question that was brought up in another thread while were on this AOSP topic. I'm curious to your thoughts on this.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Entropy, while were on this topic,could you enlighten us for this question that was brought up in another thread.
profete162 said:
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
Click to expand...
Click to collapse
Sent from my C6603 using Tapatalk 2
Perfectly clear and nice answer, thanks.
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
profete162 said:
Hey guys, as you have some knowledge that I don't, can someone explain me something...
The official AOSP from Sony seems to lack from some important drivers (camera and modem) because they are closed source.
I totally understand and that's not a problem for me.
What I don't understand is why CyanogenMod team has some open source drivers.. is that because they reverse engineered some stuff that Sony is not allowed to?
I really do not understand the difference between these two projects.
Click to expand...
Click to collapse
In some cases, our handling of blobs is a pretty serious grey area. That is, for example, why our official build instructions use the extract-files approach. Also, why our blob repos used for builds are maintained separately from our main source repos.
That reminds me, I need to look through the manuals/stock software for my device to see what sorts of legal terminology there is - e.g. what is actually said about the blobs in about->legal.
In some cases (such as modem and camera), the OEM has weirdo restrictions in terms of permission to release binaries. Qualcomm has some especially arcane rules for some items (mostly modem-related).
Also, in the case of AOSP master, blobs must be compatible with the current codebase - as a result, some of our backwards-compatibility hacks to work with released blobs aren't valid for "official upstream" AOSP.
If I am not completely stupid and understood previous post, can we summarize like this:
1) "drivers" for camera and modem are proprietary compiled files on the device that nobody can edit
2) Sony has the right to include these files on a Sony Rom (I guess they paid for these files?)
3) Sony cannot include these files on other Rom than the one shipped with the device, like an AOSP ROM. (even as a separate package?)
4) Cyanogen include these files on CMxx but (is? // is not?) allowed to
Is that right?
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Gitaroo said:
does AOSP mean turning the Z into a nexus phone basically? Sorry I am still new to the Android thing. What does this mean for update? Do we get it as soon as Google release a new one?
Click to expand...
Click to collapse
Will still require time to adapt it. But it'easier for the community devs and chances to get it are much higher than on other phones.
Sent Form my CM powered Sony Xperia Z.
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
All Snapdragon S3 (Scorpion) devices are in the same boat there. Samsung Scorpions just saw 4.1 only in the last week or so.
I hope they can retain Bravia engine!
I'm dowloading the source code now, let's see what I can do
Sent from my C6603 using xda app-developers app
Tom Fagerland said:
AOSP is pure open source, but to get that source running on any given phone you're almost guaranteed to have to use closed source blobs due to licensing. This is not a bad thing, and on the github site sony even gives a download link to all the blobs so you can use them
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
I was about to create a thread to share the news hehe
http://developer.sonymobile.com/201...or-xperia-z-on-sonys-github-open-source-video
I hope by doing this xperia z will turn to a nexus phone *grins*
babylonbwoy said:
It reminds me the Xperia S AOSP thread, lots of hope when they annouced it, but unable to provide a stock rom update to 4.1.2 ! Last one is from september and it's 4.0.4...
Click to expand...
Click to collapse
wouldnt Z be different. The S didnt have on screen navi keys and on top of that it was using a snapd 3 chip with 1gb of ram. Touch up was clearly needed for the S, however...
The Z is nearly the same as a Nexus 4 in nearly every way.
paperWastage said:
https://developers.google.com/android/nexus/drivers
then what are these binaries for Nexus devices?
Do devs use those closed-source binaries for building AOSP for nexus devices? (and difference is that Google obtained permissions from everyone to release the binaries?
Click to expand...
Click to collapse
Read my post again.
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.)
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
As everyone on here probably knows, z5 premium will not be getting any further security updates. Its timing couldn't have been any worse either. When I bought this premium phone (which costs almost as much as a flagship iphone), I didn't expect to have my security updates cut in just 2 years. I was planning to hang onto this phone for a few years until something worth upgrading to came out.
So like many who still own this phone, I am wondering is there anyway to keep my phone secure and still use it? My phone is unlocked and rooted and I am running the latest firmware. I unfortunately didn't back up my drm keys so I had to use the hack method to keep my phones functionality (fingerprint sensor, camera...etc) I'm wondering what is the best close to stock firmware to use to get the latest security updates and also how much functionality is lost by using those? It's to my understanding the camera only works the best with the official camera app and 4k only works on the album app and movie app. Will I lose 4k capability by switching to a custom firmware?
Any insight on any of this would be greatly appreciated.
Thanks to all who took the time to read this and a big thanks in advance to anyone who can provide any input.
Mostly updated custom kernel + custom ROMs (Sony Stock ROM + kernel based)
e.g. https://forum.xda-developers.com/z5-premium/development/m-rom-t3781969
and
https://forum.xda-developers.com/showpost.php?p=76269595&postcount=418
well, newer custom kernels will have WPA2 KRACK protection, protection/mitigation against Meltdown/Spectre (a class of timing-based) attacks and other fixes & improvements
updated binaries for e.g. wpa_supplicant might be needed but I haven't really looked into those details yet
Thanks. Is it possible to use a custom kernal like the one you provided in your second link with the latest official firmware (32.4.1.54) since I only care about updating my security?
Mike3009 said:
Thanks. Is it possible to use a custom kernal like the one you provided in your second link with the latest official firmware (32.4.1.54) since I only care about updating my security?
Click to expand...
Click to collapse
sure, flash TWRP (if not already done so),
do a backup of each partition separately (/boot , /data , /system)
and flash the kernel
it'll update /boot and modules in /system
zacharias.maladroit said:
sure, flash TWRP (if not already done so),
do a backup of each partition separately (/boot , /data , /system)
and flash the kernel
it'll update /boot and modules in /system
Click to expand...
Click to collapse
I appreciate the help and sorry for all the questions. Is backing up the partitions still necessary if I already have a backup of the firmware from xperifirm? Yes I already have TWRP because I used it to root my device. Also I'm assuming the kernal I want is on the first post of the second link you shared with me but there are two files to be downloaded and I'm not sure which to use. I'm on a z5 premium e6853.
Thanks again.
Mike3009 said:
I appreciate the help and sorry for all the questions. Is backing up the partitions still necessary if I already have a backup of the firmware from xperifirm? Yes I already have TWRP because I used it to root my device. Also I'm assuming the kernal I want is on the first post of the second link you shared with me but there are two files to be downloaded and I'm not sure which to use. I'm on a z5 premium e6853.
Thanks again.
Click to expand...
Click to collapse
I just flashed over the first one with fastboot. Worked fine. Security is still showing September 2017 though. Is there anyway I can know if I'm more secure now?
Mike3009 said:
I just flashed over the first one with fastboot. Worked fine. Security is still showing September 2017 though. Is there anyway I can know if I'm more secure now?
Click to expand...
Click to collapse
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
zacharias.maladroit said:
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
Click to expand...
Click to collapse
That's too bad. I guess it's as I thought; there's no real perfect solution to staying secure at the time being. Well, thanks for the kernal anyways. I can't believe how much better my phone is now. It has me puzzled why Sony didn't release it like this in the first place.
Mike3009 said:
As everyone on here probably knows, z5 premium will not be getting any further security updates. Its timing couldn't have been any worse either. When I bought this premium phone (which costs almost as much as a flagship iphone), I didn't expect to have my security updates cut in just 2 years. I was planning to hang onto this phone for a few years until something worth upgrading to came out.
So like many who still own this phone, I am wondering is there anyway to keep my phone secure and still use it? My phone is unlocked and rooted and I am running the latest firmware. I unfortunately didn't back up my drm keys so I had to use the hack method to keep my phones functionality (fingerprint sensor, camera...etc) I'm wondering what is the best close to stock firmware to use to get the latest security updates and also how much functionality is lost by using those? It's to my understanding the camera only works the best with the official camera app and 4k only works on the album app and movie app. Will I lose 4k capability by switching to a custom firmware?
Any insight on any of this would be greatly appreciated.
Thanks to all who took the time to read this and a big thanks in advance to anyone who can provide any input.
Click to expand...
Click to collapse
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
YasuHamed said:
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
Click to expand...
Click to collapse
Yeah I know, it's pathetic really. It's still a very current device as it was a very high spec phone when it was released. High spec phones like these don't get outdated that quickly. It's even more insulting that they cut support right as the meltdown vulnerability came out. They knew what they were doing -it's like a forced upgrade. Problem is: there is nothing released by Sony that really surpasses this phone in specs, or at least not enough for most people to be willing to spend all that cash on a new phone when their current one works perfectly. I don't see any compelling reason to run out and get an xz premium unless my phone breaks and dislike the xz2 premium. Oh well, I'll just have to use caution and hope for the best until a phone worth upgrading to comes out or my phone dies. Whatever happens first I suppose. Thanks for the sympathy.
Mike3009 said:
Yeah I know, it's pathetic really. It's still a very current device as it was a very high spec phone when it was released. High spec phones like these don't get outdated that quickly. It's even more insulting that they cut support right as the meltdown vulnerability came out. They knew what they were doing -it's like a forced upgrade. Problem is: there is nothing released by Sony that really surpasses this phone in specs, or at least not enough for most people to be willing to spend all that cash on a new phone when their current one works perfectly. I don't see any compelling reason to run out and get an xz premium unless my phone breaks and dislike the xz2 premium. Oh well, I'll just have to use caution and hope for the best until a phone worth upgrading to comes out or my phone dies. Whatever happens first I suppose. Thanks for the sympathy.
Click to expand...
Click to collapse
sony never forgets to disappoint their customers by keep releasing unfinished flagships on the frequency of new bulletins!
whole z series abandoned after z5p due to huge billions of book losses to sony in xperia project. the device should have been with 4gb ram! but instead it was kept on 3gb!
z5p is awesome device, stable, stays in control and maintain itself amazinly!
now xzp came out finally with 4gb ram (should have been 6)
where xz2p is coming with 6gb ram and strange bumpy design and misplaced finger print sensor!
i don't know what sony is up to!
What's really disappointing is the lack of roms being developed. The prices are getting pretty nice right now for the z5 premium after support was dropped making it an attractive, affordable 4k smartphone for new comers. Also for those of us who already own it, having at least one decent rom solution would be really nice. It's pretty sad that I'd have to give up some of the functionality that I paid for in order to continue to keep my device secure. I'm going to stick to official firmware with anti-virus along with this updated kernel and hope for the best. I'd very much appreciate it if anyone finds a good custom firmware solution, to please let me know. Thanks in advance.
YasuHamed said:
yes! sony treated this device as their step son!
released late 2015, hit market 2016, and was already in LEGACY DEVICES in 2017, the whole series discontinued and after many months they released android 7.1.1 and thats it, no more builds or updates!
feel sorry for the device, it has all the premium features but treated badly!
- the 4k capability depends on which 3rd party rom you are using! , btw not many roms are available for z5p
Click to expand...
Click to collapse
zacharias.maladroit said:
you take a look at the source in github
sorry, the ROM base is the same [and thus you're affected by the vulnerabilities, so best would be to re-enable SELinux which gives quite a good protection itself],
kernel-side however got you covered (well, it really depends how much the kernel is patched up).
You, of course, could try out RR, LineageOS which are somewhat more up-to-date (updates stopped being added November / December last year for Android 7.1.y),
but there you'd lose e.g. picture stabilization on video recording, MHL, MirrorLink, superior post-processing on pictures, etc.
The problem with these device (Snapdragon 810) is that Qualcomm dropped support for the msm8994 platform,
and since we're stuck with 3.10 kernel it's a community effort to get it patched up somewhat.
There'd be the possibility to upgrade & port the kernel to 4.4 but since the API, etc. would mismatch and newer drivers are missing it's basically not worth the effort
Click to expand...
Click to collapse
How can we enable selinux?