Good News!!! - Xperia Z3 Compact General

Sony releases lollipop binaries.
http://www.androidauthority.com/sony-releases-5-1-binaries-xperia-phones-594087/

Sony should just release Lollipop

Don't get that excited, lollipop on Samsung and motorola isn't ground breaking.

? Not sure I understand what that means. Nothing's ground breaking here, nor is there a claim for it.
Binaries help third party developers develop aosp based Roms for the device, and currently there's no aosp based ROM that can be considered daily driver for z3c (cm is close). So, if you are like me, waiting for more third party Roms for this device, I'd say the news above is exciting.

Related

[Q] Note 3 drivers & CyanoGenMod

Dear Note3 users,
I am wondering about buying the Note 3 - however, I am afraid it will turn out the same as with my Note 1 - lack of proper drivers for newer AOSP/CyanoGenMod and the resulting problems (especially - phone reboting when taking pictures and occasional UI stuttering etc.). I remember devs blaming Samsung for not releasing the source-code for the Exynos-based devices back then..
I suppose the current CM KitKat builds are fine with N3 - what about future builds, especially when moving beyond KitKat? Has Samsung done a better job at supporting the N3 and AOSP/CM thus far (when compared to the N1)?
Thanks for all your replies..
Jan
I can't answer your question directly - I don't use CM/AOSP - but I'm interested in the way you asked your question.
I don't see that Samsung have any onus or responsibility all to "support" CM and/or AOSP. As I understand it, they release the source codes for all drivers that they are legally obliged to and no more.
I'm sure the rest is a PITA for CM/AOSP devs, but is that unique to Samsung? Don't Sony, HTC etc do the same?
Personally the only thing I like about CM is the theme choices, and now there are Xposed modules to port many themes to TW based ROMs. If I wanted CM/AOSP, I'd buy a Nexus.
I've nothing against TW framework, it's never let me down, and I've had the SGS/2/3 and Note 2 previously. I don't use the TW launcher, stock icons or stock kernels. I have tried a fair few CM ROMs over the years, and never had a single one that was 100% bug free.
Put it this way - I like stability in my phone, and by definition any ROM that needs nightly builds isn't going to supply that "need".
My 2 cents. Whatever floats your boat is fine, that's why we don't use iphones

[ROM] *×xREQUESTx×* AOSP KitKat 4.4.2

We could REALLY use an AOSP ROM over here on the Galaxy Note 10.1 (2014) -P600/WiFi Only tablet.
I know there's someone out there who is interested in starting a new project as the first developer to produce an AOSP ROM for this kick ass device:fingers-crossed:
...hopefully!
So, who here is willing to donate? I know I DEFINITELY am!
Maybe we'd even be lucky enough to get an INCREDIBLE developer like we did for our TouchWiz HYPERDRIVE(sbreen94) <---- thanks for that!!!
Perhaps even @blindndumb or @albinoman887 would be interested!!?
IF YOU'RE WILLING TO DONATE FOR AN AOSP ROM, LET IT BE KNOWN!!!
and for P601
Correct me If I'm wrong, but Exynos 5 (P600) is not really supported by AOSP roms, so only Snapdragon variants like the P605 are likely to be compatible with any AOSP rom. It's likely better to purchase a P605 and run CM11, than wait for an Exynos 5 AOSP build.
Also, why would you want to remove the S-Pen features from a Tablet, who's main selling point is the S-Pen?
I won't be complaining if it happens but personally I can't really see any real benefits to having an ASOP Rom on this device at this point in time.
I prefer ASOP on the original note n7000 as you can get the latest Android OS that hasn't been released officially for that device. Also the older hardware is lacking and slow under the TW interface so you get big performance boost by having a lighter ROM.
This tablet has plenty of grunt and currently the latest Android OS so yeh not much point having ASOP imo.
With Android L coming out that might make a port more worthwhile
I would be happily willing to donate if someone prepares a P601 version.
I don't think Samsung releases binaries for the Exynos, so that's going good to add a layer of difficulty.
Plus with a device like this, you're going to lose a lot of functionality like all the spen stuff, multiwindows, floating Windows, ir transmitter, etc...

XZ1 Nougat

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

funny thing that older moto g's got cyan 14.1 but moto g4 plus didnt

Ok so cyanogenmod.org got all moto devices listed and they said moto g series getting cyanogen 14.1 but moto g4 plus not anywhere in cyanogenmod.org list:crying:
I hate unofficial buggy ROMs
mayank.bhola1 said:
Ok so cyanogenmod.org got all moto devices listed and they said moto g series getting cyanogen 14.1 but moto g4 plus not anywhere in cyanogenmod.org list:crying:
I hate unofficial buggy ROMs
Click to expand...
Click to collapse
Official roms are buggy too if you ever tried nightlies or snapshots. And we will see, maybe official will come until cm statet it comes not
They didn't say all G family, they post this list:
falcon, peregrine, titan, thea, osprey
They are 1st 2nd and 3rd Gen.
FlaminisRex said:
They didn't say all G family, they post this list:
falcon, peregrine, titan, thea, osprey
They are 1st 2nd and 3rd Gen.
Click to expand...
Click to collapse
If it's not in the list, it will be added, thats possible.
@mayank.bhola1:
No need to scared and say it will never come. If you didn't have a proof, don't open such scaring threads "no official cyanogen 14.1" that's really annoying to others, because some people trust it and won't buy the device maybe(just an opinion)
I avoid anything cm based. Always worse on battery life.
trsix said:
I avoid anything cm based. Always worse on battery life.
Click to expand...
Click to collapse
That's not true that all cm based has "always" worse battery life. On my galaxy's I got more battery compared to Samsung roms(official or mod) and also on my other devices cm gives me more battery life then stock, even to aosp! Maybe you encountered bad experiences, but it totally depends on the device tree, drivers, modem, source, etc etc... And the knowledge of the dev :angel:
My experience with CM was that a lot of the features added where useless to me and they just added battery drain and new bugs. And when a bug was fixed in a nightly, there was a good chance that another two bugs would pop up.
Not cool if you really need to use your phone as a phone. Maybe OK if you don't have a job or you stay at home all the time.
SoNic67 said:
My experience with CM was that a lot of the features added where useless to me and they just added battery drain and new bugs. And when a bug was fixed in a nightly, there was a good chance that another two bugs would pop up.
Not cool if you really need to use your phone as a phone. Maybe OK if you don't have a job or you stay at home all the time.
Click to expand...
Click to collapse
So you concluding that we must stick to stock ROMs ??
Depends of what you do for living... and if need a reliable phone line for that.
SoNic67 said:
Depends of what you do for living... and if need a reliable phone line for that.
Click to expand...
Click to collapse
I knew a device which stock cos rom is the hell on earth(random reboots, bugs, freezes) compared to cm and nearly all people saying wow after flashing cm instead of staying on stock. CM is widely available for devices and always a chance to get more out of your device when the manufacturer gives up the development after launching the device or won't fix bugs in acceptable time.
Not the case here. Moto firmware is stable and not bloated.
CM is best after OEM leaves device support. I had Asus Zenfone 5 earlier but no official CM so developers made unofficial one but Asus had serious issues with bootloader unlock as no developer was able to resolve screen freeze issues. So running custom ROMs on that device was hell bad.
If you think making cm and make it official is easy then do it urself, we really want to see. Things are not same as 1st,2nd &3rd. The chipset are way different than the previous gen. So stop posting useless things. Dont open thread for you own satisfaction.
Just my $0.02 : The premise behind getting a custom ROM is that it's for those who have an above average idea about OS, customizations, working on a system level and such.
The whole argument about stability, and what one does for their living is a bit too far fetched in context of using a device that is dependable. Stock ROMs are made by OEMs keeping a novice end-user in view, who may or may not have sufficient time, knowledge or inclination of going beyond what the device came shipped with.
Custom ROMs and development is undertaken almost completely as a voluntary exercise by the devs, mostly on cost of their own resources and go far as to offer their work off forum threads which they'd personally support. Those flashing and modding devices are ones testing the work undertaken by devs, and even after a ROM gets official status, work on development continues with feedback from users and updating security, porting features from other devices, expanding customization et al.
Battery use, smoothness of UI, connectivity, stability, obviously are essential to one's experience of using their phone, but are highly dependent on how well one's put to use the abilities of their custom ROM, apart from what applications or settings one's gotten on, and that would come about only with experimenting, learning and keeping oneself updated with their device's software.
Stock ROMs, barring the few odd ones which run stock Android are almost always crammed with bloatware, uncustomizable UI/features and locked in to a mesh of regulatory compliances, OEM/vendor/third party interests and above all marketing the device as a product - which means you're good to go for just about as long as the OEM cares, and that isn't usually long enough given they'd obviously be focused on selling newer products.
So, it's just that mileage may vary but if you're willing to stick around to learn and experiment, customizing is the only way to truly own your phone.
Sent from my Moto G4 Plus using XDA Labs
Frances91 said:
...
Stock ROMs, barring the few odd ones which run stock Android are almost always crammed with bloatware, uncustomizable UI/features and locked in to a mesh of regulatory compliances, OEM/vendor/third party interests and above all marketing the device as a product - which means you're good to go for just about as long as the OEM cares, and that isn't usually long enough given they'd obviously be focused on selling newer products.
So, it's just that mileage may vary but if you're willing to stick around to learn and experiment, customizing is the only way to truly own your phone.
Sent from my Moto G4 Plus using XDA Labs
Click to expand...
Click to collapse
I think the G4 is close to AOSP. Using Xposed you can get many fancy features found in custom roms. GravityBox gives you much of what CM offers.
Security features make it much more difficult to customize a phone. Pay by phone, i.e. "Wallet" will become important.
Custom roms are used more now for keeping old phones current. Not that much happening with new phones. Look at CyanogenMod https://download.cyanogenmod.org/ to view this.
king200 said:
I think the G4 is close to AOSP. Using Xposed you can get many fancy features found in custom roms. GravityBox gives you much of what CM offers.
Security features make it much more difficult to customize a phone. Pay by phone, i.e. "Wallet" will become important.
Custom roms are used more now for keeping old phones current. Not that much happening with new phones. Look at CyanogenMod https://download.cyanogenmod.org/ to view this.
Click to expand...
Click to collapse
If you're considering using Xposed for the 'fancy features' and use wallet, and yet vouch for stock Roms I'm not sure what you're on to. You'd need for more mods running on a stock ROM which would anyways take months or even years to get updated to run latest Android versions. Some times you'd just stick around with frequent updates which are still two SDK versions behind the current official release, basically cycling through bloat, partner apps and constant rooting, modding to just keep your phone worth it's use.
As for new phones, it takes a fair amount of time, effort and understanding to access available sources and build a device tree from which custom ROMs are built.
Besides, not many users, unless they've specifically bought the new device to work on development, adopt customization till about several months after their purchase. As for CyanogenMod site they list the official ROMs, which are painstakingly built after months of testing. What you see on there are mostly devices which are either usually a year old or are stock Android - both being fitting scenarios for system level modifications to drive both performance and customization. You'd be hard pressed to find Android OEMs updating devices or even offering security patches for long.
Also, do remember MIUI, Oxygen and several other OEM ROMs that run across some of the most successful phones evolved from the custom ROMs community development.
And yeah, there's the custom kernels as well which almost always need a custom ROM.
Unless you've hit upon a groundbreaking counter claim to all the benefit of custom ROMs you would be among a tiny minority of informed users who ascribe to that idea. I would really like to benefit from what you can share about it, I am sure I can hit up the devs in my subscribed threads and help them make better decision with their time and efforts.
Sent from my Moto G4 Plus using XDA Labs

Will the Moto G7 support 3rd party ROMs?

I am currently useing an Asus Zenfone 4 ZE554KL and it's the worst phone I ever owned. Updates from Asus is horrible and their Android skin is terrible. There is no community support for this device for 3rd party ROMs
I am looking at this phone as it has a headphone jack and a minimal notch. As it seems with every Android manufacturer besides Google, updates will be just as slow and that's unacceptable to me.
I am looking at this phone in hopes that it will support 3rd party ROMs such as Lineage OS or Pixel experience. I want to take my own control over updates.
Will this phone support 3rd party ROMs?
I don't do ROM development, but I believe some developers will because it should have good sales.
What about a treble compatible gsi?
What are you looking to get ported?
Preferably, anything that is as close to stock and direct from Google.
someaguy said:
Preferably, anything that is as close to stock and direct from Google.
Click to expand...
Click to collapse
We already have that with Stock lol. We got released Pie with a new clean look. I might look into an AOSP variant if that is what you are interested in, but that would be barebones.
While I appreciate that the G7 has stock Android, I see Motorola is still as slow as everyone else when updating there line as phones. If the community does it faster than Motorola to update to Android Q, then I will feel that this should be my next phone.
I am considering buying a moto 7 too. It is slated to get the Q update but nothing beyond.
I'm more interested in using custom ROMs such as lineageos which is google free. That brings up the question of whether the Moto 7 can be rooted (and unroofed). Does anyone know?

Categories

Resources