Related
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
Overview
SlimROM, we all know it I guess..
Download
Zuk Z2
*Alpha: Feedback needed, unknown stability
SlimROM 6.0.1 - Alpha 1
Z2 Configurations
Device - Github Pending
Kernel - Github Pending
Kernel is unified and can also be used with Z2 Pro
Vendor - Github Pending
Alpha Notes:
This may not boot, but I'm like 99.9% sure it will. =<
I'm pretty sure my configurations are correct, we'll see right?
Although I don't own this device since others did the heavy lifting I feel very confident in my ability to update device configurations and maintain things as Android is updated over time
Great!
Is this official Slim?
Is Slim based on AOSP or CM?
Thanks.
vittogn said:
Great!
Is this official Slim?
Is Slim based on AOSP or CM?
Thanks.
Click to expand...
Click to collapse
AOSP
Incoming for Z2 Pro today ok? I had a few things I needed to resolve lol
Since nobody said anything negative about this firmware yet; I guess I can safely consider Z2 as stable.
InterfaceNode said:
AOSP
Incoming for Z2 Pro today ok? I had a few things I needed to resolve lol
Since nobody said anything negative about this firmware yet; I guess I can safely consider Z2 as stable.
Click to expand...
Click to collapse
That's fantastic. How many downloads did you get?
Is this based on the chinese slim rom? Just asking as it has the same bloatware.
I tested it for a few minutes:
- it boots just fine
- sim card detected
- W-LAN is not working for me. Can't turn it on.
- Bluetooth turns on, not tested
- GPS turns on, not tested
Restored a backup of a previous rom as I need my phone to function properly.
This is all the feedback I can give you for Alpha 1. There is sure to be more people getting involved in testing soon.
Best regards
Zuk z2 SlimROM 6.0.1 - Alpha 1
iceeyes91 said:
Is this based on the chinese slim rom? Just asking as it has the same bloatware.
I tested it for a few minutes:
- it boots just fine
- sim card detected
- W-LAN is not working for me. Can't turn it on.
- Bluetooth turns on, not tested
- GPS turns on, not tested
Restored a backup of a previous rom as I need my phone to function properly.
This is all the feedback I can give you for Alpha 1. There is sure to be more people getting involved in testing soon.
Best regards
Zuk z2 SlimROM 6.0.1 - Alpha 1
Click to expand...
Click to collapse
Very useful feedback, in the next build I will try to resolve wifi
It uses the same props as the Chinese version but considering I'm just bringing up HW I didn't feel the need to debloat at all honestly
Sorry, I'll be pushing the Z2 Plus/Pro/Whatever soon; if it also suffers wifi problems I'll at know that's kernel-side for sure.
I have not had the time really to mess around with heavy debugging; I am unsure if wifi driver issue is on the source-code or the kernel in this time but I imagine kernel.
InterfaceNode said:
Sorry, I'll be pushing the Z2 Plus/Pro/Whatever soon; if it also suffers wifi problems I'll at know that's kernel-side for sure.
I have not had the time really to mess around with heavy debugging; I am unsure if wifi driver issue is on the source-code or the kernel in this time but I imagine kernel.
Click to expand...
Click to collapse
When will the z2 pro build be uploaded?
MacLaughlin said:
When will the z2 pro build be uploaded?
Click to expand...
Click to collapse
Maybe 2-3 hours from now; I'm rebuilding again
In my defense I'm really not using many prebuilt things and am bringing up the kernel mostly from scratch; also notice the format my ROMs follow in the Z2 non-pro build.
The Z2 Pro configs I use seem to be spiked, but it shouldn't be a huge problem; it has just taken a little fixing..
InterfaceNode said:
Maybe 2-3 hours from now; I'm rebuilding again
In my defense I'm really not using many prebuilt things and am bringing up the kernel mostly from scratch; also notice the format my ROMs follow in the Z2 non-pro build.
The Z2 Pro configs I use seem to be spiked, but it shouldn't be a huge problem; it has just taken a little fixing..
Click to expand...
Click to collapse
Great. I'm getting excited.
---------- Post added at 08:56 PM ---------- Previous post was at 08:49 PM ----------
InterfaceNode said:
Maybe 2-3 hours from now; I'm rebuilding again
In my defense I'm really not using many prebuilt things and am bringing up the kernel mostly from scratch; also notice the format my ROMs follow in the Z2 non-pro build.
The Z2 Pro configs I use seem to be spiked, but it shouldn't be a huge problem; it has just taken a little fixing..
Click to expand...
Click to collapse
If you do the next port, something with theme engine would be nice like, aokp or du.
MacLaughlin said:
Great. I'm getting excited.
---------- Post added at 08:56 PM ---------- Previous post was at 08:49 PM ----------
If you do the next port, something with theme engine would be nice like, aokp or du.
Click to expand...
Click to collapse
I had something more special in mind
InterfaceNode said:
I had something more special in mind
Click to expand...
Click to collapse
And what should that be? Miui?
MacLaughlin said:
And what should that be? Miui?
Click to expand...
Click to collapse
I was thinking Sense, honestly
I really want to have a community project here but that would require some volunteers who have both devices, eh?
InterfaceNode said:
I was thinking Sense, honestly
I really want to have a community project here but that would require some volunteers who have both devices, eh?
Click to expand...
Click to collapse
Sense? Are you kidding me ????? I think everybody would be greatful if you could develop a more common rom. Nothing bloated.
MacLaughlin said:
Sense? Are you kidding me ????? I think everybody would be greatful if you could develop a more common rom. Nothing bloated.
Click to expand...
Click to collapse
I'll build and maintain AOSP either way no matter what; but I want to bring interesting things to this device too.
I will not build in the middle with things like CyanogenMod; I will build pure AOSP for people who want a more pure thing and then I will do vendor ROMs for folks who desire that.
Slim is almost pure, but not quite.
Really, Slim is just for bringing up these devices; once they are stable I'll build using the same code Google does on their AOSP devices so there will not be a difference
Edit: But the configs for Z2 Pro which I've KANG'd are really configured in a messed up way; a lot of proprietary things are missing.
CyanogenMod handles a lot in the way of not being as picky; not being subject to some things that will cause a fatal error when trying to build AOSP or something close to it like Slim or OmniROM..
the Z2 and Z2 pro are very, very similar devices, I had to use some core things from the Z2 model; the bring-up so far has been a bit brutal.
InterfaceNode said:
I'll build and maintain AOSP either way no matter what; but I want to bring interesting things to this device too.
I will not build in the middle with things like CyanogenMod; I will build pure AOSP for people who want a more pure thing and then I will do vendor ROMs for folks who desire that.
Slim is almost pure, but not quite.
Really, Slim is just for bringing up these devices; once they are stable I'll build using the same code Google does on their AOSP devices so there will not be a difference
Edit: But the configs for Z2 Pro which I've KANG'd are really configured in a messed up way; a lot of proprietary things are missing.
CyanogenMod handles a lot in the way of not being as picky; not being subject to some things that will cause a fatal error when trying to build AOSP or something close to it like Slim or OmniROM..
the Z2 and Z2 pro are very, very similar devices, I had to use some core things from the Z2 model; the bring-up so far has been a bit brutal.
Click to expand...
Click to collapse
Woah! If an AOSP comes to Z2 Pro, I think that will be the best thing ever. Thank you for your efforts in the ROM development for this device
syedtahir16 said:
Woah! If an AOSP comes to Z2 Pro, I think that will be the best thing ever. Thank you for your efforts in the ROM development for this device
Click to expand...
Click to collapse
In order of how pure a ROM is:
AOSP >> SlimROM/OmniROM >>>>> CyanogenMod >>>>>>> Everything else
InterfaceNode said:
In order of how pure a ROM is:
AOSP >> SlimROM/OmniROM >>>>> CyanogenMod >>>>>>> Everything else
Click to expand...
Click to collapse
Agreed. I used Nexus 4 for a long time and the pure android experience was incredible. Will definitely give slimrom a shot and see how that works on this device.
InterfaceNode said:
I'll build and maintain AOSP either way no matter what; but I want to bring interesting things to this device too.
I will not build in the middle with things like CyanogenMod; I will build pure AOSP for people who want a more pure thing and then I will do vendor ROMs for folks who desire that.
Slim is almost pure, but not quite.
Really, Slim is just for bringing up these devices; once they are stable I'll build using the same code Google does on their AOSP devices so there will not be a difference
Edit: But the configs for Z2 Pro which I've KANG'd are really configured in a messed up way; a lot of proprietary things are missing.
CyanogenMod handles a lot in the way of not being as picky; not being subject to some things that will cause a fatal error when trying to build AOSP or something close to it like Slim or OmniROM..
the Z2 and Z2 pro are very, very similar devices, I had to use some core things from the Z2 model; the bring-up so far has been a bit brutal.
Click to expand...
Click to collapse
Okay so no build for z2 pro for now?
MacLaughlin said:
Okay so no build for z2 pro for now?
Click to expand...
Click to collapse
I'm making another topic for it
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!!
I'm planning on buying the 4gb 128gb version from aliexpress, but there's no vanilla android(Pure stock android) rom for this phone. The reason why I want stock Android is because I need Gravitybox as it's a must when I get a new phone. So will we see an AOSP rom anytime soon?
Sent from my S3 using XDA-Developers mobile app
Only if you make for us.
No. Buy a OnePlus 3T. Or an HTC 10. Or an Honor 8, they have a mostly fully working cm13 ROM.
abdi7451 said:
No. Buy a OnePlus 3T. Or an HTC 10. Or an Honor 8, they have a mostly fully working cm13 ROM.
Click to expand...
Click to collapse
I was thinking of buying one of those as well but they all have dealbreaking issues.
OnePlus 3T: Poor display for VR
HTC 10: Too small
Honor 8: No 4K recording
Guess I'm stuck with the Axon 7.
flamingspartan3 said:
I was thinking of buying one of those as well but they all have dealbreaking issues.
OnePlus 3T: Poor display for VR
HTC 10: Too small
Honor 8: No 4K recording
Guess I'm stuck with the Axon 7.
Click to expand...
Click to collapse
And software is a bigger deal breaker than all of those things you've mentioned. At the end of the day, you do whatever you want to do, but the Axon 7 isn't as good as any of those mentioned phones, solely on the software experience and dev community.
We have an almost working CM13 that many use as daily driver and, IMHO, CM does not need Gravitybox (I agree AOSP badly needs it).
But if I could go back, I would take a harder look at OP3T for exactly the software issue.
kenturky said:
I'm planning on buying the 4gb 128gb version from aliexpress, but there's no vanilla android(Pure stock android) rom for this phone. The reason why I want stock Android is because I need Gravitybox as it's a must when I get a new phone. So will we see an AOSP rom anytime soon?
Sent from my S3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Gravity box works except for the quick settings tweaks.
Hola
Just to add my experience, I was one of those who really was interested in the Axon 7 since it was announced earlier this year (MWC 2016 in Feb??), so I purchased it the instant it was released. The hardware is undoubtedly top notch except:
1. The crappy capacitive buttons that are placed too close together.
2. Stupid vibration setup - Either on or off with no vibration intensity configuration.
3. Non-existent granular volume level controls - Yes you can increase or decrease the overall volume, but the increments are too far apart (this could be a software limitation though).
So I've used it for a month or so but because of the lack of a near complete AOSP or CM based ROM (mostly due to ZTE's slowness in providing source and a number of proprietary blobs), I really yearned for my ability to try different ROMs and flash different add-ons like I was accustomed to. So I end up buying the OnePlus 3T. Man it was nice to use and experience a phone that can garner so many devs. If only the 3T had dual front facing speakers, expandable storage, and that QHD res screen, then it would have been the best of the best in my opinion.
I am now back to using the Axon 7 using one of those slightly modified ZTE based ROMs with Xposed. I consume a lot of media on my phone. I still keep my 3T for testing out new dev ROMs like RR or CM.
Seems like OEMs can't make a phone that provides great hardware (e.g. A7) while providing access to firmware sources and letting dev community to thrive.
lafester said:
Only if you make for us.
Click to expand...
Click to collapse
Sorry bruh, I'm not a developer, and I didn't like programming much. Someone should port a stock rom from Oneplus 3/3t to this phone instead. That would be great.
abdi7451 said:
No. Buy a OnePlus 3T. Or an HTC 10. Or an Honor 8, they have a mostly fully working cm13 ROM.
Click to expand...
Click to collapse
Oneplus 3T? Nope, no card slot. HTC 10, overpriced junk, and single sim. Honor 8, Hisilicon Kirin, nope. I prefer snapdragon because most apps on the play store, and some special features are made uniquely for snapdragon chips.
Not interested in cm13/14 because I can't use gravitybox on it.
So the Axon 7 is a great buy. The 4gb/128gb version if sold in most countries will actually sell like hot cakes.
nupi said:
We have an almost working CM13 that many use as daily driver and, IMHO, CM does not need Gravitybox (I agree AOSP badly needs it).
But if I could go back, I would take a harder look at OP3T for exactly the software issue.
Click to expand...
Click to collapse
No CM13 doesn't need gravitybox, but I find more features on gravitybox than on CM13. CM13 doesn't work really well with gravitybox as I'm using it on my current phone till Rovo builds xposed for Android 7.1, and I'm currently experiencing some automatic shutdowns on this rom. I own a Jiayu s3,(Has a mediatek chipset)and I'm looking to upgrade to the Axon 7 because of the amazing speakers and the camera.
On the CM13 thread, it says that the GPS is working, but something is written about QC location. What's QC there?
awsomjgp said:
Gravity box works except for the quick settings tweaks.
Click to expand...
Click to collapse
I actually need the quick settings tweaks because I need the switcher. 2g only, 3g only, 4g only, 4g/3g. It's important because sometimes the phone automatically switches from 4g to 3g if it thinks the 4g signal is less. And 4g uses band 3, 1800MHz whereas 3g uses 2100MHz(no clue about the band number here).
So I need to keep it on 4g only in this case.
And in some areas, neither 4g nor 3g is available, so I'll have to make do with 2g.
Sent from my S3 using XDA-Developers mobile app
Qualcomm izat doesn't work but then again that is mostly superfluous if you have Google services.
Right now, GPS works on Cm13 but is not super accurate {probably 20 meters or so}
kenturky said:
I'm planning on buying the 4gb 128gb version from aliexpress, but there's no vanilla android(Pure stock android) rom for this phone. The reason why I want stock Android is because I need Gravitybox as it's a must when I get a new phone. So will we see an AOSP rom anytime soon?
Sent from my S3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Come on now people, we all know how it works by now. They are fixing some issues on CM13 as we speak. Once CM13 is made official, the custom rom flood gates will open. Give it time.
kenturky said:
. The reason why I want stock Android is because I need Gravitybox as it's a must when I get a new phone.
Click to expand...
Click to collapse
Gravity Box work perfect on Stock Rom, no need of AOSP ROM for GB to work.
Gravity Box and App Settings (v1.13) are my have to have modules in Xposed and they work great.
IMO the axon 7 is better than the one plus 3 or honor 8 (in terms of hardware) but the lack of roms is definitely a deal breaker for some people. However in about a week or so I'm going to start working on porting AOSP to the axon 7. Iv'e never ported a rom before so I can't make any promises on when it'll be done (if ever lol). I know a thing or two about programming so I think I'll be able to figure something out, so stay tuned!
andrew97b said:
IMO the axon 7 is better than the one plus 3 or honor 8 (in terms of hardware) but the lack of roms is definitely a deal breaker for some people.
Click to expand...
Click to collapse
You took the words right out of my mouth my mouth bruh.
However in about a week or so I'm going to start working on porting AOSP to the axon 7. Iv'e never ported a rom before so I can't make any promises on when it'll be done (if ever lol). I know a thing or two about programming so I think I'll be able to figure something out, so stay tuned!
Click to expand...
Click to collapse
It wouldn't be easy starting out now, and it'll take a while. You could start by heading over to the op3 thread and see any AOSP Marshmallow rom.
Then maybe ask in the Q&A section for porting this rom to the Axon 7.
Sent from my S3 using XDA-Developers mobile app
kenturky said:
I'm planning on buying the 4gb 128gb version from aliexpress, but there's no vanilla android(Pure stock android) rom for this phone. The reason why I want stock Android is because I need Gravitybox as it's a must when I get a new phone. So will we see an AOSP rom anytime soon?
Sent from my S3 using XDA-Developers mobile app
Click to expand...
Click to collapse
Gravitybox works on the stock OS.
XblackdemonX said:
Gravitybox works on the stock OS.
Click to expand...
Click to collapse
Oh well, do the quick settings tweaks like 2g/3g/4g switcher(network mode) work on the stock rom?
Sent from my S3 using XDA-Developers mobile app
kenturky said:
Oh well, do the quick settings tweaks like 2g/3g/4g switcher(network mode) work on the stock rom?
Sent from my S3 using XDA-Developers mobile app
Click to expand...
Click to collapse
I can find it in which menu ?
EDIT: No, playing with quicktiles messed with the boot. I see the lockscreen wallpaper and then the screen turns off/on/off/on/off...
XblackdemonX said:
I can find it in which menu ?
EDIT: No, playing with quicktiles messed with the boot. I see the lockscreen wallpaper and then the screen turns off/on/off/on/off...
Click to expand...
Click to collapse
Damn. Yeah it interfered with the system quicksettings, and caused a bootloop. I think I might have to go with the CM13 rom in this case.
Sent from my S3 using XDA-Developers mobile app
tabletalker7 said:
Come on now people, we all know how it works by now. They are fixing some issues on CM13 as we speak. Once CM13 is made official, the custom rom flood gates will open. Give it time.
Click to expand...
Click to collapse
Same thing happened with cm14 for the Moto X pure, once it got finished, more and more 7.1.1 roms started flooding in xD.
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?