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!!
Related
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
How come there is only one cm based kernel?
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Rudjgaard said:
Hi to everyone, got my phone yesterday, rooted unlocked and started off.
I come from some experience in the field (my first phone was an xperia)
and my stats show that I put effort and time into this community and am looking forward to start working on some projects.
(i am merely a builder not a developer)
Click to expand...
Click to collapse
Welcome to this forum and I hope you'll enjoy working with the community here
Would anyone be so kind and nice to give me a picture of current development status?
Are there major bugs being worked on from cm incompatibility?
Click to expand...
Click to collapse
AFAIK, there aren't any CM bug now, there was a camera lag at start up weeks ago, but now it's solved,
the only thing left is that camera quality on AOSP-Based ROM is not as good as it is on stock Sony FW,
The great thing going on now is that we're gonna have official AOSP support from Sony soon (all thanks to @jerpelea)
check these:
Unified kernel for msm8974 devices
Xperia AOSP Project
these are still new and their early stages, and hopefully we'll start using them soon:good:
How come there is only one cm based kernel?
Click to expand...
Click to collapse
To be honest, there aren't many devs how own or work for this device, even the cm-based kernel we have is ported from Z1 !
also I'm working on a brand new one with the latest features, but I think it'll take some time
What are the most common problems that have been mostly encountered?
Thanks for your replies, happy to be here, take care
Click to expand...
Click to collapse
Well as I mentioned, we don't have any major problems, as this device can get whatever Z1 can get, and Z1 is popular
except for one thing! the double tap to wake feature can't be ported from Z1 to our device as the two devices don't share the same touchscreen!
That's all I can remember right now
if you need any help, I'm always available,
and I'm looking forward to seeing your work
Best Regards,
Omar.
Thank you very much for your long and exhaustive answer.
I did see a camera workaround in the cm system.
Has anyone tried porting stock camera to cm? (Is it the actual camera hal responsible for qualiy or Sony proprietary rendering sw on album(are pics better/worse in fact when viewed on PC or from the phone's album? We did that on the lg with great results..
What about device blobs for the kernel are they closed source or do we have support from Sony?
Thanks again for all the info
Cheers
As title says.
i left my old Samsung S3 for a Sony Z3 mainly for the "promise" of more AOSP-like roms, because Sony thinks is "developer / community friendly".
Though my Z3 is rock stable with the latest official software, i find the lack of AOSP-CM love very disturbing: i really thought that "developer friendly" equals "more and better AOSP-CM for all".
that's not true.
Maybe because there are no people working on that device? (i konw that's close to a hobby, the whole AOSP-CM thing)
Maybe sony simply has better stock software (thus, no needs of further development)?
The only AOSP roms available at the moment are very buggy and looks like not actively developed; nonetheless that rom's thread is almost dead, with no evidence of active development.
The need of unlock the bootloader (and losing DRM, i have a backup), waste at least 45-60 minutes to setup a non-sony, bug filled rom is a nonsense.
I tried CyanogenMod (both standard and sabermod) and i only got to rollback to stock software, because of various and very annoying bugs (eg, auto-brightness, camera..).
the very last attempt ended with a screen damage (overheat) that forced me to a warranty-RMAconclusion (at least for me):
too complex and time-wasting to obtain root
lack of both quality/quantity of CM/AOSP roms (despite sony is "developer friendly")
lack of interest on this (Z3 D6603) device?
i'm not a developer... so i only speak for the (final) user side.
please tell me if i'm wrong.
Dont believe always all promises and its also the lag of people to have patients, far to find by some.
Agreed
I believe that they will be friendly after you unlock your phone's bootloader and void the precious warranty along with some of proprietary functions. It's like you have to sell your soul and a kidney to have that extra power (but you can get it back if you backed up your DRM keys thingy)
I am also understand that they have to protect their stuffs but let you have access to root and fastboot at the same time.
When I first unlocked the BL. The thing I missed a little bit is Bionz thingy but then I just gave up and bought a their mirrorless camera. Problem fixed but costs 4x price but enjoy manual mode and (most likely) actual G lenses!
smala said:
[*]lack of interest on this (Z3 D6603) device?
Click to expand...
Click to collapse
It's rare to see a Sony's ads in my country like 3% compared to 70% of Samsung's. Some of my friends looked at my phone and they have no idea that Sony phones existed. I'm like OMG guys...
The phone is good. I have a black one. 3GB of RAM, insane battery life, 8MP 21MP camera with their (so called) G Lens, super stylish Omni-Balance design and frontal dual speakers.
I'm actually really love this phone.
Oh and I would like to see when the single SIM models shares the same rom with dual SIM models. I first bought a really good dual SIM model without a clue and then instantly traded with single SIM one because that time I really want to try Existenz ROM (no cellular function). LOL at myself.
Ps. I also have that goddamn slightly yellow-ish stuff on my navbar (so I can't use tinted navbar because it was the most annoying thing ever.) with two brighter-than-the-rest (idk if that is called bright pixel or what) area. Not a big deal though.
Ps.2 This thing is like a toaster when flashing-backing up-restoring in recovery.
Sorry for a long reply. This is just my thought without being sarcastic except the first line. X D
I guess most of what the OP said was kind of true. However as I moved from my pretty heavily modified Nexus 5 to the Z3, I've seen no interest in rooting the device or adding functionality because the Z3 is good enough IMO. The screen is just how I want it, unlike my N5's extremely warm/orange display and the battery is amazing compared to the N5. For me the work to get root isn't worth it anymore (plus I need mobile banking) ?
Sent from my D6603 using Tapatalk
There are a good 6 or 7 great roms for Xperia z3 without unlocking your bootloader. Like Pandemics, Wolfbreaks, niaboc79. Take a look at the threads. I'm stuck with a z3 where I cant unlock bootloader, which pisses me off, so I'm grateful to these devs that produce such great roms for our z3. These devs are also on the ball. They respond to your stupid questions and politely help you.
I do wish that all sony phones were bootloader unlockable, but I guess the carrier plays some part too.
And then there is their concept MM combined with DRM restore, root, xposed and Gravitybox
And now that a root has been found for mm, both Ub and lb, there will be lots more development for the Z3
http://forum.xda-developers.com/showthread.php?t=3337357
smala said:
As title says.
i left my old Samsung S3 for a Sony Z3 mainly for the "promise" of more AOSP-like roms, because Sony thinks is "developer / community friendly".
Though my Z3 is rock stable with the latest official software, i find the lack of AOSP-CM love very disturbing: i really thought that "developer friendly" equals "more and better AOSP-CM for all".
that's not true.
Maybe because there are no people working on that device? (i konw that's close to a hobby, the whole AOSP-CM thing)
Maybe sony simply has better stock software (thus, no needs of further development)?
The only AOSP roms available at the moment are very buggy and looks like not actively developed; nonetheless that rom's thread is almost dead, with no evidence of active development.
The need of unlock the bootloader (and losing DRM, i have a backup), waste at least 45-60 minutes to setup a non-sony, bug filled rom is a nonsense.
I tried CyanogenMod (both standard and sabermod) and i only got to rollback to stock software, because of various and very annoying bugs (eg, auto-brightness, camera..).
the very last attempt ended with a screen damage (overheat) that forced me to a warranty-RMAconclusion (at least for me):
too complex and time-wasting to obtain root
lack of both quality/quantity of CM/AOSP roms (despite sony is "developer friendly")
lack of interest on this (Z3 D6603) device?
i'm not a developer... so i only speak for the (final) user side.
please tell me if i'm wrong.
Click to expand...
Click to collapse
go check out the other sections they suck the Sony forum is one of the best for sure.
smala said:
As title says.
i left my old Samsung S3 for a Sony Z3 mainly for the "promise" of more AOSP-like roms, because Sony thinks is "developer / community friendly".
Though my Z3 is rock stable with the latest official software, i find the lack of AOSP-CM love very disturbing: i really thought that "developer friendly" equals "more and better AOSP-CM for all".
that's not true.
Maybe because there are no people working on that device? (i konw that's close to a hobby, the whole AOSP-CM thing)
Maybe sony simply has better stock software (thus, no needs of further development)?
The only AOSP roms available at the moment are very buggy and looks like not actively developed; nonetheless that rom's thread is almost dead, with no evidence of active development.
The need of unlock the bootloader (and losing DRM, i have a backup), waste at least 45-60 minutes to setup a non-sony, bug filled rom is a nonsense.
I tried CyanogenMod (both standard and sabermod) and i only got to rollback to stock software, because of various and very annoying bugs (eg, auto-brightness, camera..).
the very last attempt ended with a screen damage (overheat) that forced me to a warranty-RMAconclusion (at least for me):
too complex and time-wasting to obtain root
lack of both quality/quantity of CM/AOSP roms (despite sony is "developer friendly")
lack of interest on this (Z3 D6603) device?
i'm not a developer... so i only speak for the (final) user side.
please tell me if i'm wrong.
Click to expand...
Click to collapse
There simply aren't alot of developers left developing on the z3. It is an aging device and most dev's move onto newer phones rather quickly. There are lots of good rom options for the z3 to keep you occupied. But if you were looking for more active development, I think you should have bought a z5 or held out for a zx.
Sent from my D6603 using Tapatalk
I came across several Devices like Samsung S2/3/4/5, Note 2/3/4, Sony Xperia S/Z/1/2/3, LG G2/4x, Nexus 4/7 and some more I think but the variety of Development is really one of the smallest here in Z3.
Actually I'm stuck at the Z3(no money) and got used to it but, except the Battery, it isn't that Killer I expected from it.
Well no, I don't need a Tissue
Downloaded the Slim Stock Sony from here, actually it is Version 5 with some really nice new Features (Launcher/Icons..) + Xposed + Gravity Box and I am happy.
Back in the the Samsung S2 days, many people were complaining about Samsungs politic about their Exynos Chips and Developers had hard times with it but now, just have a look at S3/S3 LTE Forums, always up-to-date.
I don't understand why there is no official Cyanogenmod 13 for the Z3, even the CM 12.1 is just nightly but unfortunately I lost touch to all this back in the S4 Active days so I have to wait for what will come.
On the other side, the Z3 is a stabile daily Device with no bigger Problems so it could be worse. And Android 6 is coming, sooner or later
BTW, my wife's Z5 (Telekom Germany) didn't get MM, yet.
Greetings,
Thomas
ohwarumbloss said:
I came across several Devices like Samsung S2/3/4/5, Note 2/3/4, Sony Xperia S/Z/1/2/3, LG G2/4x, Nexus 4/7 and some more I think but the variety of Development is really one of the smallest here in Z3.
Actually I'm stuck at the Z3(no money) and got used to it but, except the Battery, it isn't that Killer I expected from it.
Well no, I don't need a Tissue
Downloaded the Slim Stock Sony from here, actually it is Version 5 with some really nice new Features (Launcher/Icons..) + Xposed + Gravity Box and I am happy.
Back in the the Samsung S2 days, many people were complaining about Samsungs politic about their Exynos Chips and Developers had hard times with it but now, just have a look at S3/S3 LTE Forums, always up-to-date.
I don't understand why there is no official Cyanogenmod 13 for the Z3, even the CM 12.1 is just nightly but unfortunately I lost touch to all this back in the S4 Active days so I have to wait for what will come.
On the other side, the Z3 is a stabile daily Device with no bigger Problems so it could be worse. And Android 6 is coming, sooner or later
BTW, my wife's Z5 (Telekom Germany) didn't get MM, yet.
Greetings,
Thomas
Click to expand...
Click to collapse
No official CM due to, mainly, the camera bug.
They can't release a snapshot version with such a big issue.
Sent from my D6603 using XDA-Developers mobile app
I agree. This is why I personally will try out Samsung. Specifically the Galaxy S7 Edge. I always see Samsung devices getting a lot of attention from 3rd party developers. They always get fully working custom roms and such. I've been stuck to Sony for a really long time (ever since the Xperia X10 Mini Pro) and I'm tired to see all the devices I use to be quickly abandoned. The lack of development is seriously pissing me off (I'm not blaming anyone).
LeParkour012 said:
I agree. This is why I personally will try out Samsung. Specifically the Galaxy S7 Edge. I always see Samsung devices getting a lot of attention from 3rd party developers. They always get fully working custom roms and such. I've been stuck to Sony for a really long time (ever since the Xperia X10 Mini Pro) and I'm tired to see all the devices I use to be quickly abandoned. The lack of development is seriously pissing me off (I'm not blaming anyone).
Click to expand...
Click to collapse
The only thing why I really HATE Sony is that Bootloader Unlocking thing. I've got a Nexus 4 - unlocking the BL was super-easy and I'm using a custom rom till now.
Next phone was a Moto G - there was a bug which prevented me from unlocking (and rooting) it. But I posted on Motorola's forums and somebody from them helped me and gave me a testing bootloader - also unlocked and custom ROM till now.
But on Z3 I risk loosing DRM keys, good camera, video recording (!?) and YouTube playback - a REAL dealbreaker!
The "missing" development is not such a big thing for me, as the stock ROM is a really good base to work with - so far, I didn't miss that part at all.
But what I miss because of the locked bootloader is to have a recovery in recovery partition which is (more or less) guaranteed to work even when phone is totally messed up. Without unlocking, just to restore a twrp backup, I need to flash stock, root it, install XZDR and restore it - which takes at least 30minutes.
But for daily use, also with root, I'm satisfied with my Z3 with Stock + XZDR + SoundMod + Xposed.
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?