Related
I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
bbabiuk said:
I am wondering about the difference between an original development ROM vs. A stock ROM variant on a nexus device.
To explain... My last device was an HTC one. There modified stock ROMs. And then there were the aosp or rather original development ROMs. It was quite easy to differentiate. Drivers etc as well as software was very proprietary in nature vs. a stock ROM. Even the GPE ROMs were stock variants.
The question I have is....what is the difference on a nexus? Is the software similar in nature but drivers different? I likely am doing poor job explaining it...or using the incorrect terminology. But I hope I have expressed it adequately.
Not that NY of this will likely stop me from flashing a custom ROM or 10... I just was curious. That was all.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
rootSU said:
On other devices, you have AOSP ROMs and Stock ROMs.
Stock ROMs cannot be compiled from source. They can have their apks decompiled and have smaller amendments made to the code that is revealed from this process and have some other basic functions added too via things like "dsi xda kitchen" and these roms generally belong in "Android development" forums. OEM's should be releasing stock kernel source code though, so this allows further amendments to be made by Stock ROM devs.
AOSP ROMs are compiled from source code as you know. Often, as the OEM can get away with only releasing kernel source code, AOSP devs have to hack drivers and libs or build open source alternatives to get things like the camera to work because the OEM may not have released the source code for the drivers or HAL. This is why on other devices, you often see early AOSP roms listing things not working like WiFi, Camera and other things that rely on hardware.
On Nexus devices, this is slightly different.
Stock ROMs on the Nexus still vary from AOSP. Google should be seen as an OEM. They have their own proprietary software such as the camera (photosphere) for example that they have not released the source code for. Obviously there is much less modification to the AOSP code for Nexus stock ROMs. Things like the frameworks will remain in large, the same. As with other device stock ROMs, the code is not directly available,. Even though it is very similar to AOSP, it isn't really. So all the ROMs in "Android development" are modified in the same way as other devices. Decompiled and "dsi xda kitchen"... Some AOSP apk's may be a direct shoe in though due to the massive similarities.
AOSP ROM devs don't have as much trouble as with other devices though. The AOSP source that is sync'd from the google repository can be built directly for the Nexus range (older devices excluded) without having to merge it with a device tree and drivers etc as the source already includes that.
Click to expand...
Click to collapse
Very thorough. I do have one other question then...
Then AOSP ROMs for Nexus devices should by the nature of the build process have everything working similarly to the stock ROMs. Things like Bluetooth not working quite right or green tints to cameras should not occur.
Sent from my Nexus 5 using XDA Premium 4 mobile app
*should* yes, but not guaranteed. Pure aosp should work immediately after compile. However, new functions are added by developers to the aosp code base to make the roms more functional and these commits can break each other or even existing functionality
-----------------------
Sent via tapatalk.
I do NOT reply to support queries over PM. Please keep support queries to the Q&A section, so that others may benefit
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
air2k57 said:
I found that "issues" on aosp based roms are there quite a bit. Cataclysm, for example, has a green line on every video I record in snap chat. Purity was great, but back key on portrait was always brighter than rest and had some visual glitches. I've yet to see a ROM as fast as stock android, or kernel that is same.
Sent from my Nexus 5 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the update. The nice thing about nexus devices is it is so simple to go back to stock. It was a real pain on my HTC one.
Sent from my Nexus 5 using XDA Premium 4 mobile app
No problem. I had htc one and it was indeed a pain. While I liked sense, I felt a need to root because of annoying apps it came with, or power saver notification that was always there. Not to mention, T-Mobile variant took ages to get updated, and when it did, it was buggy. The whole S-Off thing was a nightmare.
I've always found other devices, even nexus 4, to function better with custom ROMs and kernel. It took me awhile to root n5 though, simply because I was happy with everything. I did like ability to have center clock, or circle battery with %. However, in order to have those, you need aosp or gravity box that doesn't work with art due to xposed. Oh yea, pie I liked too, I like having more screen space.
Other than that, I am very happy stock. I ended up finding a really good mix with purity ROM and elementalx kernel. I liked elemental on HTC one a lot as well. And, it has cooler colors option, I do like the way it makes display look.
Last night I ended up unrooting and going stock to compare. Reason being, I got annoyed with bright back key in landscape and text on quick toggles in portrait ended up being cut off some. Performance wise, I am thinking that lure stock is still A bit quicker. Battery? Not sure yet, I got woken up at 7am by stupid weather alert, ended up unplugging my phone and leaving it on nightstand. It dropped from 99% to 95% in 4 hours idle. So about a % an hour. I remember Franco and elemental having better idea battery life though.
Sent from my Nexus 5 using xda app-developers app
Explain Life I'm 5: Besides CM acting like a$$hats, why do we care if they don't support the OPO anymore? Will we not continue to have every single Android update on Slim. PA, crRom and all the other awesome ROMS out there? I haven't received my OPO yet so I'm just trying to keep up while I patiently wait at the mail box everyday hoping to get it before the new year
If CM do decide to completely stop supporting this device, dropping CM11S/CM12S and CM11/CM12, you can wave goodbye to pretty much every custom ROM too because they basically all rely on CM at some point during their development. That isn't likely to happen though.
If CM decide to just drop official support for this device (CM11S/CM12S), it means there's some kind of a breach of contract happening because this phone was guaranteed to receive updates from CM for at least two years. Many people decided to go with this phone because it has CM on it, because it runs a ROM that's much more customisable than any other stock ROM on the market. It's like buying a Mercedes only to be told after six months that they're switching the AMG engine out for a Kia engine, nobody would be happy about that.
Transmitted via Bacon
timmaaa said:
If CM do decide to completely stop supporting this device, dropping CM11S/CM12S and CM11/CM12, you can wave goodbye to pretty much every custom ROM too because they basically all rely on CM at some point during their development. That isn't likely to happen though.
If CM decide to just drop official support for this device (CM11S/CM12S), it means there's some kind of a breach of contract happening because this phone was guaranteed to receive updates from CM for at least two years. Many people decided to go with this phone because it has CM on it, because it runs a ROM that's much more customisable than any other stock ROM on the market. It's like buying a Mercedes only to be told after six months that they're switching the AMG engine out for a Kia engine, nobody would be happy about that.
Transmitted via Bacon
Click to expand...
Click to collapse
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
TigerDNA said:
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
Click to expand...
Click to collapse
OnePlus is reportedly working on a CM-free version of a ROM for their phones, including their flagship, the One.
About the independent developers, yes, they are basing their builds on Cyanogen "base", but wouldnt be the end of the world if CM would stop developing their version, since Cyanogen is actually basing on a base Android ROM too, this means that somebody would take over the same features and develop them from scratch or even base from some of the open source from Cyanogen since, Android is Open and most of their developemt community is open too, and who knows, while it would take time, maybe will come with something better, not that i believe CM is bad.
Come on Oneplus, employ the guys over at slim roms or PA, let them make the roms for the phone if CM wants to be jackholes. My only concern is that, is it now possible that CM would push crappy updates to the phone just to be dicks, full of bugs and problems or worse, brick some phones?
TigerDNA said:
Obviously I'm no dev, but could a CM based ROM be compiled independent of CM just by having the source code. I just assumed in my few years of flashing crap that how it worked. As long as you had the source code from Google/OEM you could compile what ever you needed. Again, I have never tried to develop anything.
Click to expand...
Click to collapse
Satorikn said:
OnePlus is reportedly working on a CM-free version of a ROM for their phones, including their flagship, the One.
About the independent developers, yes, they are basing their builds on Cyanogen "base", but wouldnt be the end of the world if CM would stop developing their version, since Cyanogen is actually basing on a base Android ROM too, this means that somebody would take over the same features and develop them from scratch or even base from some of the open source from Cyanogen since, Android is Open and most of their developemt community is open too, and who knows, while it would take time, maybe will come with something better, not that i believe CM is bad.
Click to expand...
Click to collapse
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Transmitted via Bacon
---------- Post added at 01:34 PM ---------- Previous post was at 01:34 PM ----------
amd-dude said:
Come on Oneplus, employ the guys over at slim roms or PA, let them make the roms for the phone if CM wants to be jackholes. My only concern is that, is it now possible that CM would push crappy updates to the phone just to be dicks, full of bugs and problems or worse, brick some phones?
Click to expand...
Click to collapse
You're not serious are you?
Transmitted via Bacon
timmaaa said:
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Click to expand...
Click to collapse
I do, i am aware they its just not putting a base rom and skinning it, there's a lot of hardware architecture and software architecture (kernel) involved. But in this era, and open software, it would be a matter of time before somebody else can take charge, would not be the end of the world.
Kinda, I mean it's not impossible for CM to be childish and push bug filled software (after all their responses toward oneplus have not exactly oozed trustworthy)
amd-dude said:
Kinda, I mean it's not impossible for CM to be childish and push bug filled software (after all their responses toward oneplus have not exactly oozed trustworthy)
Click to expand...
Click to collapse
Honestly, it's a pretty ridiculous notion. The fact that they've had a falling out with OnePlus doesn't even for a second suggest that they'd take it out on the end user, and that's all they'd be doing.
Transmitted via Bacon
timmaaa said:
Honestly, it's a pretty ridiculous notion. The fact that they've had a falling out with OnePlus doesn't even for a second suggest that they'd take it out on the end user, and that's all they'd be doing.
Transmitted via Bacon
Click to expand...
Click to collapse
Well by screwing the end user they would screw oneplus, I honestly won't put anything past any company these days in the pursuit of money.
timmaaa said:
That isn't the case. There's so much stuff that relies on work done by CM, I'm not sure you're quite grasping exactly how integral to development CM are. It isn't just a base. It's the kernel, it's the device trees, the list goes on and on. Yes, if CM were to disappear there would still be development, but there'd be a massive hole to fill.
Transmitted via Bacon
Click to expand...
Click to collapse
I really don't know how much we rely on CM. I just think of it like, CM is free, once they release their stuff, anyone can take it and do what ever to it.
amd-dude said:
Well by screwing the end user they would screw oneplus, I honestly won't put anything past any company these days in the pursuit of money.
Click to expand...
Click to collapse
They have no reason to do so though. They would not benefit from it at all.
Transmitted via Bacon
I rather plain nexus like experience any cm is just too buggy and has been on every device I have owned and ran with their roms
Until recently I've used a Sony, but a couple of bad experiences (+ 2 bad replacements) and need for wireless charging due to work + other HW features this time round, means I've switched to a Samsung S7 (G930F). Yeah, I know, Exynos development, but I needed the hardware spec and it came up cheap. Anyhow, it's rooted, unlocked and running TWRP, and I'm trying out a couple of roms..
I usually run without GApps (no flames or "Why use android if not using GApps", please!), and I'm happy to run 6.x + Xposed, or 7.x without Xposed. But as I've only ever used AOSP variants/CM, I'm a bit unsure about choosing a rom based on modding the official Samsung firmware, so I thought I'd ask here to find about the differences "under the hood".
The most stable roms for the G930F seem to be stripped-down derivatives of Samsung official releases - but how close can I get to a stable AOSP experience? I'm not only thinking about the user interface, also about "under the hood" - some custom roms might just strip out Touchwiz and apps, others might strip out a lot more and try to clean up or get closer to a AOSP/CM style "clean" rom underneath. That's more what I'm after, a good quality stable clean rom that's trying to get close to AOSP/CM as much as Samsung makes possible and without GApps already built-in.
But at that point I'm basically lacking knowledge, so... How close do roms based on Samsung's firmware actually get to AOSP? What sort of things get left in that detract from "pure" android? Which roms are closer to AOSP under the hood, or strip out "more" of the Samsung/Gapps code?
Kryx Rom or Extreme Debloated + Nexus Conversion Pack or Google pixel rom
Use LineageOS if you are willing to deal with a few minor bugs.
I'm trying out Lineage right now - it's mostly fine, the main practical issue is an over-aggressive noise gate on phone calls, it cuts off words and makes speech hard to understand at the other end. Other issues I'm seeing are lack of power menu volume panel and crash bugs in the internal web view used by some apps. Not bad for pre-release.
One main question/concern with using a trimmed-down Samsung rom is, I haven't got any idea what Samsung do to AOSP Android/kernel, nor how much of it is undone. Gods know how often manufacturer mods have led to problems and weaknesses in an otherwise good product, and so it's not a theoretical question, manufacturer versions often seem to leave the entire firmware in quite an unknown state. I know there can't be any absolute answers, but any light-shedding would be really useful.
noob924 said:
Kryx Rom or Extreme Debloated + Nexus Conversion Pack or Google pixel rom
Click to expand...
Click to collapse
Kryx 1.2 is coming up with zip sig failure when I try to flash it. No sign that it shouldn't be signed, or is expected to come up with this error though, otherwise I'd try it anyway.
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
revdirty said:
Is there a technical reason that we have not seen any Custom Oreo roms released yet. I figured between all the RC releases of oreo leading up to the final build that the most popular roms (Pure Nexus, Resurrection Rom.. etc...) would have released 8.0 versions by now. Is it just too soon and unrealistic to expect that yet.. or an actual limitation in Oreo that is preventing builds? fyi.. im not like demanding one .. just curious on a technical level.
Click to expand...
Click to collapse
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Just from my point of view, finding the various aspects for my themes was a pain in the butt from N to O. Somethings that were once png are now vector images and that is just from a themers aspect,,,rom building is a whole other thing. I am sure there will be some soon.
I was thinking the exact same thing as OP. I hope this isn't the case for the Pixel 2 XL. My Nexus 6 is running a custom Oreo ROM and it's great so far. It's like a ghost town.
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Oreo appears buggy...
I will wait for Pure Nexus Oreo
udahy.manna said:
Hey guys, im currently using Pure nexus, i thought of waiting for the oreo version of pure nexus. But it seems like its gonna take a while.. So, shall i switch to official oreo or to wait for any custom rom?
How is battery life and performance in Oreo?.
Thanks in advance
Click to expand...
Click to collapse
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
cntryby429 said:
From my understanding, most devs don't work on betas but wait until a final build is published and this was supposedly a significant update to Android. Perhaps there's a lot to do to handle the project treble changes. XDA published an interesting article about it just today.
The pixel doesn't seem to be the super popular development device many expected it to be but I'm sure the Oreo builds will come soon enough.
Click to expand...
Click to collapse
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Why is custom ROM development on Pixel is very low?
hp13 said:
Why is custom ROM development on Pixel is very low?
Click to expand...
Click to collapse
Because it's an expensive device and it has this new crappy A/B partitions system
lorax70 said:
I'm not going to say switch to Oreo, but for me it's been pretty stable. It's no RR or PA by a long shot. Battery life seems ok, and comparable to
other nougot roms I've ran. Performance is comparable as well. I'm no gamer, so can't report on heavy usage, but I've had no issues with
my standard apps, youtube, slack, twitter etc..
I guess the only thing I'm real annoyed at is if you want to get into TWRP, you have to reboot to bootloader, and fastboot boot twrp.img. I don't know the
status of flashing twrp, but the fastboot method works well.
Rooted with SuperSU, and substratum working nicely. I can't stand the default navbar height, so installed the mod from "[MODS] Pixel OREO Aroma Mods Installer" and lowed my navbar to 42dpi, and am now content.
Now, once a Oreo custom mod like RR/PA is released (Haven't tried Pure Nexus) I'm switching.
Click to expand...
Click to collapse
The new official flashable TWRP is out and compatible with pixel Oreo.
yeah, I would give "O" a little time. It appears that some are starting to have a few issues with phones being bricked. It's possible that one of the 3 is not related, but certainly my advice would be to wait folks. This could be related directly to branded phones, but not exactly sure and would only be speculation at this point. It's possible the DEV's are waiting on a few areas...
https://forum.xda-developers.com/pixel/help/pixel-bricked-overnight-t3681377
https://forum.xda-developers.com/pixel/help/google-pixel-bricked-oreo-twice-ideas-t3671302
dantexaiver said:
I was just about to ask about the "State of Development" on the Pixel because I have been curious as to the lack of active development for Mods and ROMs. Hell my Wife's old Samsung Galaxy S4 still gets more development.
Could the A\B partitioning be a big factor in this?
I thought the Pixel would receive the same reaction like th Galaxy line and Google is a recognizable just like Samsung
Click to expand...
Click to collapse
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Golf c said:
I am usually a real patient guy, but I have to tell you, I am so over stock. I would never be rude enough to ask for an ETA, but cmon gentleman, I'm dieing here. Lol
Click to expand...
Click to collapse
Flash back to a nougat custom rom. Problem solved.
mitchdickson said:
Flash back to a nougat custom rom. Problem solved.
Click to expand...
Click to collapse
Haha, not quite.
Recently got a pixel after years of sony phones and am awaiting some Oreo custom roms. It's great I'm getting the latest OS updates straight away but the downside I guess is the newness means custom roms take longer. Now there's a working TWRP I'm hopeful we'll start to see custom Oreo roms appearing.
zelendel said:
The dual partition s is the reason. It makes developing roms a real pain. Developers have now added a dual partition setup to the list of things to avoid when getting devices.
Click to expand...
Click to collapse
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
nine7nine said:
citation, please?
that seems a bit silly, because A/B partitions are the new standard. it won't just be Google phones using it... plus, there are non stock ROMs that have made the jump to A/B.... lots of app devs have too....
Frankly, while it may add some complexity, it is far better for upgrades over OTA and makes total sense that it would be the next iteration for rolling out upgrades.
Click to expand...
Click to collapse
It is the standard for Google device. Notice how only Google devices use it?
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
A/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
zelendel said:
It is the standard for Google device. Notice how only Google devices use it?
Click to expand...
Click to collapse
Motorola has been testing it, including a device that utilizes it now. Same goes with Xaoimi... Furthermore, a/b partition is a part of AOSP... Oreo devices going forward will be making use of Project Treble and I suspect in the next year, you are going to see more vendors adopting the new partition scheme.
On top of that, all new mediatek and Qualcomm SOCs will support A/b partition schemes.
https://www.xda-developers.com/xiaomi-mi-a1-android-ab-partition/
https://www.xda-developers.com/moto-z2-force-ab-seamless-updates/
https://review.lineageos.org/#/c/156378/
https://source.android.com/devices/tech/ota/ab_updates
zelendel said:
They are great if you stay stock. But not for rom development. As for your citation, you would have to talk to developers about it.
Click to expand...
Click to collapse
Um, no. it's perfectly reasonable for an end use running a custom ROM to want/expect OTA upgrades that uses seamless updating, where supported.... I've been involved in ROM development, in the past. thanks.... for someone developing a ROM; ya, you will be flashing your custom builds, but for an end user not building from AOSP, lineageOS repositories; OTA is far bore reasonable...
zelendel said:
It is coming to the point that people will have to choice. Ota updates from Google or custom roms. Not gonna get both
Click to expand...
Click to collapse
lol. that comment makes zero sense, given the context... It's always been the case (for stock vs. custom roms) that you will be getting updates from one or the other, not both...
zelendel said:
IA/b partition will be like many things gs that Google added that oem remove. Like adaptable storage.
Click to expand...
Click to collapse
We will see, but given that Qualcomm and mediatek will be supporting it going forward and the revelations and direction of Project treble && VTS; I suspect that a/b partitions will become the norm...
the only question is what will Samsung do for future devices, since they unlike most vendors produce their own SOCs/Exynos boards.... I guess we will see when the next galaxy line is released.
Hi fellow xdains. I was wondering if any developer would build fuschia OS for our phone. If any Dev can comment on the feasibility of development ATM, and related info would be great.
Your thoughts?
i would have to guess no considering nobody will unlock the bootloader for the verizon variant. i really don't see a major port like this coming.
NoobInToto said:
Hi fellow xdains. I was wondering if any developer would build fuschia OS for our phone. If any Dev can comment on the feasibility of development ATM, and related info would be great.
Your thoughts?
Click to expand...
Click to collapse
I can comment. Fuschia OS is a toy and not a fully baked OS.
it would be rather useless on your phone. it's pretty much a demo, with no real applications that only recently could even run on bare metal / real hardware... it can run on the pixelbook (which is an x86 intel cpu laptop) and a few other devices...
it doesn't tun on our phone and you wouldn't want to run it, even if it did - unless you aren't interested in being able to make phone calls, browse the internet or do just about anything that you would normally need or want to do. lol
go watch some YouTube videos on it. you'll see for yourself that it's currently pretty useless...
I hope it fails hard, personally. I believe Google's biggest motivation for developing fuschia OS has more to do with licensing and wanting more control than anything else...
it's still an interesting project, but I can guarantee you, if it ever replaces android or chromeOS - your google device is going to be locked down compared to what it is now.
nine7nine said:
I can comment. Fuschia OS is a toy and not a fully baked OS.
it would be rather useless on your phone. it's pretty much a demo, with no real applications that only recently could even run on bare metal / real hardware... it can run on the pixelbook (which is an x86 intel cpu laptop) and a few other devices...
it doesn't tun on our phone and you wouldn't want to run it, even if it did - unless you aren't interested in being able to make phone calls, browse the internet or do just about anything that you would normally need or want to do. lol
go watch some YouTube videos on it. you'll see for yourself that it's currently pretty useless...
I hope it fails hard, personally. I believe Google's biggest motivation for developing fuschia OS has more to do with licensing and wanting more control than anything else...
it's still an interesting project, but I can guarantee you, if it ever replaces android or chromeOS - your google device is going to be locked down compared to what it is now.
Click to expand...
Click to collapse
I agree with you, but since pixel, google has been moving more and more towards locking more things up. At some point it will be like iOS I guess.
NoobInToto said:
I agree with you, but since pixel, google has been moving more and more towards locking more things up. At some point it will be like iOS I guess.
Click to expand...
Click to collapse
how so? what is more locked up since the Pixel?
google has always had their closed source apps and services, but beyond that the pixel is far more open than most android phones I've owned... there are security enhancements, but i don't see that as being locked up... so i'm not sure what ur talking about, in this regard.
the source code for the pixel is included in AOSP, google and the vast majority of retailers sell pixels with OEM unlocking, etc... it's just crappy carriers like Verizon that don't...
I think fuschia OS could be a sign of them going more in the direction of a permissive or more contolled and closed platform, but i'm not sure they'll be able to get it off the ground (many google projects fail or they drop them)...
I don't think the pixel is very closed or locked down though.
nine7nine said:
how so? what is more locked up since the Pixel?
google has always had their closed source apps and services, but beyond that the pixel is far more open than most android phones I've owned... there are security enhancements, but i don't see that as being locked up... so i'm not sure what ur talking about, in this regard.
the source code for the pixel is included in AOSP, google and the vast majority of retailers sell pixels with OEM unlocking, etc... it's just crappy carriers like Verizon that don't...
I think fuschia OS could be a sign of them going more in the direction of a permissive or more contolled and closed platform, but i'm not sure they'll be able to get it off the ground (many google projects fail or they drop them)...
I don't think the pixel is very closed or locked down though.
Click to expand...
Click to collapse
I'm no expert in this ,but I believe with pixel, google moved away a bit from aosp. It introduced more proprietary elements?
Usage wise I am not bothered with it. I'm happy with stock roms, I quit customizing.
NoobInToto said:
I'm no expert in this ,but I believe with pixel, google moved away a bit from aosp. It introduced more proprietary elements?
Usage wise I am not bothered with it. I'm happy with stock roms, I quit customizing.
Click to expand...
Click to collapse
well, they may have added in their typical proprietary soup, plus introduced some new bits, but I don't think they've moved away from aosp, anymore than would be typical... aosp is just the base system, after all... I've built aosp for the pixel in the past and added gapps.... sure, there are differences vs. stock, but not overly drastic...
the pixel 2 likely has more of a gap, but at the same time, once u drop gapps intoplace; i'm sure it's far less noticeable on aosp...
ya, i'm mostly happy with stock too. but I still use magisk, my own kernel, I tweak android a bit... and have been tinkering with xposed, since it was recently released for Oreo (although, it's currently a bit lack-luster due to lack of Oreo plugins).
nine7nine said:
well, they may have added in their typical proprietary soup, plus introduced some new bits, but I don't think they've moved away from aosp, anymore than would be typical... aosp is just the base system, after all... I've built aosp for the pixel in the past and added gapps.... sure, there are differences vs. stock, but not overly drastic...
the pixel 2 likely has more of a gap, but at the same time, once u drop gapps intoplace; i'm sure it's far less noticeable on aosp...
ya, i'm mostly happy with stock too. but I still use magisk, my own kernel, I tweak android a bit... and have been tinkering with xposed, since it was recently released for Oreo (although, it's currently a bit lack-luster due to lack of Oreo plugins).
Click to expand...
Click to collapse
Has there been any progress with xposed being compatible with safetynet? I loved using gravitybox with stock rom since it always seemed to be the most stable, feature-rich, customizable option of the custom roms, but xposed trips safetynet (last I checked) and imo that makes it unusable.
uodii said:
Has there been any progress with xposed being compatible with safetynet? I loved using gravitybox with stock rom since it always seemed to be the most stable, feature-rich, customizable option of the custom roms, but xposed trips safetynet (last I checked) and imo that makes it unusable.
Click to expand...
Click to collapse
That will probably never happen, as far as I know, there is no "progress"
Sent from my Pixel using XDA-Developers Legacy app