Never seen such a low dev contribution for any of my Android devices. My moto is pretty much perfect, but there's always ways to improve it. Why is there so little activity on it? Are we just waiting for Cm or PA to support it?
Was it really necessary to start another 1 of these threads.. There's already 2 that are active.. Read and post there
We are waiting for you to make us a ROM! Get cracking!
CWick4141 said:
Was it really necessary to start another 1 of these threads.. There's already 2 that are active.. Read and post there
Click to expand...
Click to collapse
Where?
And I'd love to, but I'm useless
Serious answer.
The Moto X has a lot of proprietary code for things like moto assist, active display, and the low power ir sensors. Additionally, there is no official source for lollipop like there is for Nexus devices...making it difficult for ROM builders.
The Moto X (2013) had very little in the terms custom ROMs as well. There will probably be a few ROMs in the future, but don't expect a ROM community like there are for Nexus devices, it just won't happen.
That being said, the Moto X is damn near perfect straight out of the box. I am an avid flasher, and I really don't feel like I'm missing out on much with the stock experience on the Moto X.
Center status bar clock/date is really the only thing I miss.. Possibly a kernel but stock with trickster seem to be working well
I'd love to get Xposed modules back for some minor cosmetic and functional tweaking, but otherwise this phone is close to perfect already.
chrisrozon said:
I'd love to get Xposed modules back for some minor cosmetic and functional tweaking, but otherwise this phone is close to perfect already.
Click to expand...
Click to collapse
Yeah, Xposed is a total game changer. That's one of the main reasons I'm keeping both my X and N5 on KK for the foreseeable future.
mprziv said:
Serious answer.
The Moto X has a lot of proprietary code for things like moto assist, active display, and the low power ir sensors.
Click to expand...
Click to collapse
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
People also say that because the Moto X is such a close to stock device, there is a lack of interest in developing for it. I don't believe that either, because if that were true there would be no development for Nexus devices and, of course, those are the devices that get the most development.
mprziv said:
Additionally, there is no official source for lollipop like there is for Nexus devices...making it difficult for ROM builders.
Click to expand...
Click to collapse
I think this, in fact, is probably the one and only reason there is no development for Moto X devices. I don't know that much about what is needed to make a ROM, and someone can correct me if I'm wrong, but without the source for proprietary drivers for various hardware components in a device, you're kind of stuck.
What puzzles me is that Motorola promoted the "Pure Edition" as an unlocked edition of the 2nd Gen Moto X. But if they're not going to provide the source code needed for development, why did they bother? It's like a developers edition of a phone that's only good for non-developers.
I also don't really see how it benefits Motorola to block development. It's a relatively small portion of users who even bother with custom ROMs. But is the most enthusiastic portion of users, who can really help spread the buzz for a device. In addtion, custom ROMs often come up with smart ideas that later get adopted in stock ROMs. So their is a potential symbiotic relationship there. As it is, it just seems like Motorola alienates some of the biggest Android fans.
mprziv said:
That being said, the Moto X is damn near perfect straight out of the box. I am an avid flasher, and I really don't feel like I'm missing out on much with the stock experience on the Moto X.
Click to expand...
Click to collapse
Yeah, it's nice. With Xposed, as others say, it can be modified in similar ways as ROMs. But there are still some Motorola built in elements that I'd rather not see, so it's not pure stock, as is often suggested.
My real hangup is that ROMs, like Cyanogen, are much better at stripping out some of the most egregious tracking code. Providing privacy enhancements (again not just at the user feature level, but in the underlying code). And generally eliminating things that don't serve users, but do serve marketers/manufacturers. That's more important to me than a lot of the user interface modifications found in ROMs.
So with Xposed you can get an user interface experience that's pretty similar to a lot of ROMs, but their are other benefits that may be missing.
If I could get an official version of Cyanogen for the 2nd Gen Moto X, it would be a near perfect device to me. As it is, I still hesitate. Of course, there's the extremely similar Nexus 6, but I'm not into that huge size.
cb474 said:
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
People also say that because the Moto X is such a close to stock device, there is a lack of interest in developing for it. I don't believe that either, because if that were true there would be no development for Nexus devices and, of course, those are the devices that get the most development.
I think this, in fact, is probably the one and only reason there is no development for Moto X devices. I don't know that much about what is needed to make a ROM, and someone can correct me if I'm wrong, but without the source for proprietary drivers for various hardware components in a device, you're kind of stuck.
What puzzles me is that Motorola promoted the "Pure Edition" as an unlocked edition of the 2nd Gen Moto X. But if they're not going to provide the source code needed for development, why did they bother? It's like a developers edition of a phone that's only good for non-developers.
I also don't really see how it benefits Motorola to block development. It's a relatively small portion of users who even bother with custom ROMs. But is the most enthusiastic portion of users, who can really help spread the buzz for a device. In addtion, custom ROMs often come up with smart ideas that later get adopted in stock ROMs. So their is a potential symbiotic relationship there. As it is, it just seems like Motorola alienates some of the biggest Android fans.
Yeah, it's nice. With Xposed, as others say, it can be modified in similar ways as ROMs. But there are still some Motorola built in elements that I'd rather not see, so it's not pure stock, as is often suggested.
My real hangup is that ROMs, like Cyanogen, are much better at stripping out some of the most egregious tracking code. Providing privacy enhancements (again not just at the user feature level, but in the underlying code). And generally eliminating things that don't serve users, but do serve marketers/manufacturers. That's more important to me than a lot of the user interface modifications found in ROMs.
So with Xposed you can get an user interface experience that's pretty similar to a lot of ROMs, but their are other benefits that may be missing.
If I could get an official version of Cyanogen for the 2nd Gen Moto X, it would be a near perfect device to me. As it is, I still hesitate. Of course, there's the extremely similar Nexus 6, but I'm not into that huge size.
Click to expand...
Click to collapse
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it, but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Not a lot of incentive for a Dev to work on the moto x, not much can be gain only loss....I.e. You goto cm or aosp you lose not gain...for the most part. Really not a lot of incentive to work on this phone. Sure there might eventually be a cm or even pa or aosp ROM but who really wants that over stock with xposed?
Sent from my XT1095 using Tapatalk
cb474 said:
People say that, but this is often true of Samsung devices and devices like the HTC One, but they still get development.
Click to expand...
Click to collapse
There is nothing similar to active display and touchless control on Samsung's touchwiz or HTC's sense.
dobbs3x said:
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it,...
Click to expand...
Click to collapse
As I said in the post to which you claim to be replying, if that were the reason not to develop for the Moto X, then there would also be no developement for Nexus devices, since they have no bloat and arrive pure stock. The point of custom roms, obviously, is not just to get rid of bloat, but to add lots of features that do not exist elsewhere. Indeed, some roms are made so that people can have an HTC Sense or Samsung Touchwiz type of experience on a non-HTC or non-Samsung phone. Roms are hardly all about returning phones to a stock experience. So I think that argument is obviously wrong to anyone who thinks about it for a minute.
Look at the OnePlus One. It ships with Cyanogen. Zero bloat, already has the most popular custom rom on it. If this argument had any merit, there would be no development for it. But in fact there is tons of development for it. Because it's a totally open device and OnePlus One encourages development.
dobbs3x said:
...but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Click to expand...
Click to collapse
You wouldn't lose the proprietary features if Motorola released drivers necessary for them to work, as other cell phone manufacturers do, so this point begs the question (again, as I already said in the post you were supposedly responding to).
*
mprziv said:
There is nothing similar to active display and touchless control on Samsung's touchwiz or HTC's sense.
Click to expand...
Click to collapse
Samsung has their own weird hardware button layout, heart rate monitors, HTC has the oddball two lens camera in the M8. It doesn't matter what the feature is. All that matters is that there's some extra piece of hardware in there and it's going to need a driver and access to the hardware for developers to use it in a custom rom.
The difference, I believe, is that Samsung and HTC release the proprietary binaries and other source code, which makes it possible for developers to develop for their phones. Motorola, for whatever reason, has chosen not to do this. I think that is the only reason their is no development for the Moto X. So I think people are actually just misunderstanding what the problem is with development for the Moto X. (If some developer out their wants to chime in with more explanation of this, I'd be happy for some confirmation.)
All the other reasons people are repeating here are made up reasons that I think have nothing to do with how development actually happens. Repeating them, because someone else somewhere in the forum said it, does not make it true.
Motorola, it seems, just doesn't want people to develop for their devices and they prevent that by not releasing the binaries and source necessary to do so.
*
The point can even be taken another step. Because the hardware on the 1st and 2nd Gen Moto Xs is so nice and generally liked and because the 2nd Gen Moto X is in fact the basis for the Nexus 6 and extremely similar to it, I think that if the binaries and source code necessary were available, there would be a lot of development for the Moto X. So it has nothing to do with all the reasons people say about why there's no need to develop for the Moto X and everything, I believe, to do with Motorola blocking developers from developing for the Moto X.
Or maybe it's just the fact that it's a mediocre device that a lot of devs aren't going to purchase. I'm sending mine back after 4 days with it. Love the build quality, but I can't live with the mediocre screen, crappy camera and poor battery life.
Most devs, "dev" for popular devices and sadly, the moto x isn't one of them
I do not see the hate towards this device to be reasoned, at all. Battery (not so ****ty as I thought it would be, very similar to Nexus 5 so you can not linger on that )and camera (I also believe it to be better then Nexus 5's) are the payoffs of a great phone. What is wrong with the screen, NRG?
I had the first gen moto x, it has lots of development but they are all cm or aosp based Roms. Pretty much a dozen different Roms with either cm or aosp as the base. There is nothing special with them. Just someone is bored and wanted to try making a ROM. They bring nothing really useful to the device unless you really just like cm. Which you should of bought the one plus or a nexus. Trust me all the Roms developed for the first gen moto x are nothing crazy, just rehashed cm and aosp.
NRGZ28 said:
Or maybe it's just the fact that it's a mediocre device that a lot of devs aren't going to purchase. I'm sending mine back after 4 days with it. Love the build quality, but I can't live with the mediocre screen, crappy camera and poor battery life.
Most devs, "dev" for popular devices and sadly, the moto x isn't one of them
Click to expand...
Click to collapse
If you consider the X to be mediocre, I'd love to know what phone you think is high end. I burn through Android phones like they are candy, and to me, the X is hands down the best smartphone ever made. Sure there are phones with better screens, cameras, and battery life, but they all have other compromises, some that are far worse. The X's screen is only mediocre when side by side with a nicer one, the camera is more than sufficient, and my battery life has been amazing. There has never been an Android phone this mature and elegant, with performance to boot. The software is as close to perfect as you can get (talking KitKat here, I'm not sold on Lollipop), and the overall user experience is second to none, at least in my eyes. To each their own I suppose, but I just can't fathom how anybody can call the X a mediocre phone.
Why would you install a custom rom on the Moto X?
I think it is a compliment to the device there is no development and urgent need for different software. What is somebody going to improve software wise that isn't already present?
shadowspring said:
Why would you install a custom rom on the Moto X?
I think it is a compliment to the device there is no development and urgent need for different software. What is somebody going to improve software wise that isn't already present?
Click to expand...
Click to collapse
Exactly, its amazing. People buy a new Samsung , HTC or LG phone and immediately want to change everything on it. That doesn't say much for the original intent of the manufactures. With the Moto X line, most are completely satisfied with it right out of the box. Something those other phones can claim.
dobbs3x said:
Samsung and HTC etc. devices get Dev because they are bloated with touchwiz/sense etc., there is not a lot to do on the moto x besides throw some aosp, or cm roms at it, but then you lose the "proprietary" features that the moto x has (which is its selling point, if you bought this phone not because of active display or moto voice then you really bought the wrong phone).
Click to expand...
Click to collapse
Is that true ?
I was going to unlock bootloader and root this nice device in order to put some tweaks (DPI change, Apps Control, Ad blocker...), but if I lose the active display this is not going to be good...
I also would like to add that this phone is less famous than others blockbusters from HTC, LG or Samsung (at least in France). Developers seem to go to where there are many users for their ROMs, excluding Nexus' line. This and that Motorola doesn't release the binaries and source...
StiiLe said:
Is that true ?
I was going to unlock bootloader and root this nice device in order to put some tweaks (DPI change, Apps Control, Ad blocker...), but if I lose the active display this is not going to be good...
I also would like to add that this phone is less famous than others blockbusters from HTC, LG or Samsung (at least in France). Developers seem to go to where there are many users for their ROMs, excluding Nexus' line. This and that Motorola doesn't release the binaries and source...
Click to expand...
Click to collapse
You wont lose any features just from unlocking and rooting, only if you flash a custom ROM that doesn't have them built in.
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
H4X0R46 said:
Hey guys, just a quick question, is Cataclysm rom built off of a genuine stock system.img like the ones hosted on the google dev site? Or is some of it AOSP based? And if it is from stock genuine Android, isn't there some kind of legal issue with that? Just wondering this, I use Cataclysm and I LOVE IT! It's my daily driver! Thanks all!
Click to expand...
Click to collapse
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). Or if the dev is particularly dedicated then they might use an AOSP base because they want to keep up with all the bleeding edge enhancements to android which may or may not have any real benefit. When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
StykerB said:
The dev had an explanation of how it worked on the original thread. Android is open source and google releases sources for all the nexus devices and they also conveniently package them into flashable images to fix things. There was at least 1 release where the dev had to wait for the source to come out even though the factory images were out in order to do anything. So in short no there's no legal issue. The dev used open source files and modified them for non-profit. The reason no one else really does that type of mod is due to the fact that AOSP mods are widespread and people can just use others' code to incorporate them into the rom (or just use CM). When you target just 1 device by using its stock rom source then the mods have to be made for specifically that device (and why would anyone create code for 1 device when they could just use what works on virtually all devices) though the Nexuses are evidently similar enough to port between them hence the N5, 6, 5x, and 6p versions. The use of the stock source however meant that you kept the "rock solid stability" that Google's team of software engineers created so the dev could focus on adding features because the base he was working on was solid.
Click to expand...
Click to collapse
So all in all, Cataclysm is using stock Android and not AOSP, but done in a way that there are no legal issues? So in essence, flashing the system.img file from the dev site and adding Cataclysm mod to it is the the exact same difference as using the full Cataclysm installer? No AOSP added?
StykerB said:
.... "rock solid stability" that Google's team of software engineers created
Click to expand...
Click to collapse
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
NLBeev said:
That has a price:
- white ui, grey text on white bad readable; especially with sunlight;
- white background causes battery drain on amoled displays;
- pesky search bar; not removable or change to transparent;
- no option to change to a dark theme;
- N6 full resolution 2560 x 1440 not used;
- N6 native resolution = 493. G. sets it to 560 dpi;
- no option to kill running apps;
- code to use layers can't be used without rooting;
- G-apps not predestinated for layers.....etc.
Click to expand...
Click to collapse
Yes but would you rather not have something solid for people to build on? some of those things aren't even about stability... like the full resolution thing? assuming you're referring to onscreen buttons, and DPI is always on every device set in multiples of 80 for app standardization reasons. The overlay code for layers wasn't intended to be used for theming. Hence why google only used it for stuff like the ATT boot animation. and Google's apps and OS are separate and shouldn't be expected to adhere to a modding community's theme engine that they don't support. And dark themes were probably a design decision rather than actual stability issue.
StykerB said:
.....some of those things aren't even about stability... like the full resolution thing?....
Click to expand...
Click to collapse
You're right my list is not about stability only.
Using the N6 now for more than a year. I've seen a beta version with a dark theme, but it was removed. Why? Stability issues ?
To make the N6 acceptable for my daily use, especially battery life and readability, I had to change a lot of things. That has consequences for the stability. The N6 is still stable but I wouldn't say rock stable.
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
H4X0R46 said:
So all in all cataclysm is built using real Android? The main question in this thread lol But yea, AOSP does have it pros and cons as well as stock, I have to play devils advocate here and say that all roms do have their differences.
Click to expand...
Click to collapse
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
zelendel said:
Yes what he did was use the stock android package. But make no mistake. AOSP is the real android. There are very few diff between what google releases and AOSP. The main diff is thie closed sourced stuff Google adds.
Click to expand...
Click to collapse
Thanks! I was never sure just how much stuff is taken out of AOSP, but it's just small differences then. Glad I know that now! And hey, since we're on the subject, how are gapps legal? Aren't gapps those closed source bits that google DOES omit from AOSP? Play store and background things? Like, I know there's some legal thing where gapps shouldn't be preinstalled in an AOSP rom, but what's the grey area with gapps? Thanks again for the detailed description! Learning these things is good lol
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
zelendel said:
If you have a look around, legal means very little here.
Google has only issued a C&D order to CM to not enclude it in their roms. This is why no aosp has them built in by default.
Click to expand...
Click to collapse
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
H4X0R46 said:
LOL I had a feeling that was the case here on XDA haha but I love Android and the development is HUGE! No other mobile OS can match Google's Android! Thanks for answering my questions man! Appreciate the help! Have a good rest of the night! Or day depending on where you're from, I'm from USA lol
Click to expand...
Click to collapse
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
zelendel said:
Im in the US as well. Well kinda lol I live in Alaska.
Yes it is but that might becoming to an end soon. With more and more people closing off their source. This is a good and bad thing. We will see what happens. Also more and more OEM are gonna lock down their devices so people will have to pic. Things like mobile pay or modding their device.
Click to expand...
Click to collapse
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
H4X0R46 said:
Yea it's awful that people are making everything closed source! I'm a person who loves to tinker with my things, modded game consoles and phones and all, my hobby haha I just hope Android always stays open source! AOSP anyways. And are they starting to make Android devices more secure and non moddable? I hope the Nexus line always stays developer friendly, because I bought a Nexus for the sake of tinkering with it lol
Click to expand...
Click to collapse
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
zelendel said:
Honestly. It because of script kiddies. The ones that just build from others source and post roms. Doing nothing but changing some text. To be honest all it would take is Google to stop pushing code to aosp. Android development would die off at that point.
Yeah if you look at things like Samsung, some devices are not even rootable, Sony, if you unlock the bootloader you lose the camera functions, even China based companies are locking bootloaders. Xiaomi just started doing this and have refused to give some the unlock because it goes against their business plan.
As for the nexus. We should be OK but then you have things like the Mm kernel that was a pain to get root on. And you lose mobile payments. Also more and more apps are looking for things like root and xposed and then refusing to work if they are installed.
Click to expand...
Click to collapse
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
H4X0R46 said:
Also, why do almost all AOSP ROMs have the "KitKat" sounds? Is that just what's released in AOSP? The "knocking" sounds I mean.
Click to expand...
Click to collapse
To be honest I never noticed. I don't use any of the stock sounds.
H4X0R46 said:
I've definitely heard of apps looking for root and for xposed framework (both of which I can't live without and use), and a lot of phones from certain companies are completely out of my interest because of no moddability. I wonder if it's even possible to root newer Samsung phones because of Knox security, and I won't even touch an Xperia, I've heard that they merge a lot of partitions, like boot and recovery and things like that, too confusing and not worth it to me. I just hope Android development stays strong in the Nexus scene at least, I love my Nexus!
Click to expand...
Click to collapse
I dont think the Nexus line will see many issues other then root becoming harder to get.
Some Samsung devices cant be rooted. Like my buddy that is a samsung fan has a note 4, note 5 and a few Galaxy s5 in his house and all of them are locked down.
More and more people are too worried about things like warranty to even bother really. I even waited on updating the n6 until root was gotten for it.
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
HipKat said:
Pretty sure those can be rooted but you trip Knox which voids warranty. I haven't looked at Sammy phones since I had my S4 but I know the Note 4 and S5 had ROMs.
Click to expand...
Click to collapse
Nope no root for the note 5. Only some can be. The tmobile version doesn't lock the bootloader but the rest do.
As tripping Knox is not an option for many as it voids their warranty but flashing roms does that anyway.
Hello there, I'm planning to switch form my Mi 11 to a S20 FE 5g. Mainly because battery life and the option to use sd cards. My question is why there aren't any AOSP based custom ROMs? This phone seems pretty popular and isn't that expensive compared to other similar speced models.
Kizaru-sama said:
Hello there, I'm planning to switch form my Mi 11 to a S20 FE 5g. Mainly because battery life and the option to use sd cards. My question is why there aren't any AOSP based custom ROMs? This phone seems pretty popular and isn't that expensive compared to other similar speced models.
Click to expand...
Click to collapse
simple answer, it's proved really hard to get one basic feature to work on 2 separate roms. hopefully this changes one day.
3mel said:
simple answer, it's proved really hard to get one basic feature to work on 2 separate roms. hopefully this changes one day.
Click to expand...
Click to collapse
What basic feature? 2 seperate roms - because of the soc?
Kizaru-sama said:
What basic feature? 2 seperate roms - because of the soc?
Click to expand...
Click to collapse
the basic feature is network connection/signal. 2 separate roms, pixel experience and lineage.
3mel said:
the basic feature is network connection/signal. 2 separate roms, pixel experience and lineage.
Click to expand...
Click to collapse
What would be needed for it to work or what's not allowing it to?
Letrix said:
What would be needed for it to work or what's not allowing it to?
Click to expand...
Click to collapse
I guess a better understanding of how Samsung's blobs or drivers work.
apparently Samsung goes out of their way to make this stuff difficult.