Related
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
v1nsai said:
I've used a few other androids before with custom ROMs, and a major obstacle to stability seems to often be the fact that manufacturers typically don't include open source drivers, which leads to reverse engineered open source drivers being developed on xda, which often aren't as good as the binaries that can only be used with stock based ROMs.
Since the n5 is a Google phone, are the drivers open source as well?
Click to expand...
Click to collapse
https://developers.google.com/android/nexus/drivers
https://android-review.googlesource.com
As far as I know, the stock ROM on the Nexus 5 doesn't use any proprietary binaries so it stays closer to AOSP, which is why it also seems to perform "worse" in benchmarks and makes some people buy other devices because they have "better performance", lol.
the nexus 5 is a nexus, those drivers are made directly for the nexus 5, no hacking needed. other androids are different, they arent nexus.
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
yea, there are better roms than cm, almost all aosp based, not as bloated and much faster.
v1nsai said:
Sorry for delayed reply
Sounds like you guys are basically saying that since the N5 comes with real, untampered stock android so custom Roms are only marginally beneficial.
I'm gonna have to try this out, it sounds like Android the way it's supposed to be without all the carrier and manufacturer crap destroying it.
The fact that the CM thread is so quiet on this board really days a lot.
Click to expand...
Click to collapse
If CM thread is quiet, it's being overshadowed by superior ROMs. Unsure why anyone would choose it for a Nexus.
Stock ROM works but has zero options. Couldn't stand it without Xposed. Don't want Xposed because I want ART.
I'm saying flash SlimKat for ROM. Then flash Code_Blue kernel. My opinions are subject to change... several times a month. And TWRP or PhilZ for recovery. Stay away from stock CWM.
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
v1nsai said:
So the stock drivers can be used for any aosp ROM because the stock is aosp? Or are there licensing issues with that?
Click to expand...
Click to collapse
one and the same in this case
Now, lemme explain. I've seen this question asked in other forums as well, but I haven't seen an answer from a dev who would really know more about those specifics.
No, I'm not talking about AOSP theme flashed on TouchWiz. I mean, back on KitKat this WAS something I did often, and will probably do it again, but I'm talking totally swapping out some frameworks/libraries/under-the-hood stuff? Nexus 5 is the fastest device I've ever laid my hands on, and it's pure AOSP, but it camera was behaving... odd... from time to time.
I guess camera behavior scripts are really not easy, I've got a friend who's working precisely that, and he has a lot of headaches.
I'm talking probably nonsense, because TouchWiz is closed source except for the kernel, and modding AOSP frameworks to work with the TouchWiz ones (without knowing the code behind the latter) would be a lot of guessing and flashing again and again until it happens that the AOSP code you wrote is compatible with TouchWiz.
But mostly: the Nexus family is fast as hell, the Samsung firmware might be somewhat slower (not so sure after their take on Lollipop, DAMN dat thang actually can be fast!), but due to it's closed source it has more features (the stock camera, the S-Pen frameworks and software).
And last, but not least, if a dev reads this discussion and the thought of having to write a kernel for that passes through his head, he would probably react this way:
Code:
#define true false //Happy debugging suckers
...and do something actually useful with his time.
Your thoughts on the matter?
What you say is true, i was thinking of this three days ago when i flashed dirty unicorns rom, fantastic rom, fast as hell, but the camera on AOSP is soooo bad, and s-pen and s-view cover dont work, It's really so hard to port the stock camera app on AOSP??
I recall on the S2 there was an attempt to get the stock TW camera onto non-TW roms. If I recall rightly they had moderate success, with just a few of the features not working.
For me getting SPen features on non-TW roms is far more important. It's the only reason I won't go near non-stock roms on the Note 3.
The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has.
There was a TW based for for the s2, i9100. I think it was called chameleon rom? It was basically just Stock TW with the samsung camera app, but aosp dialer contacts, systemui etc
Beefheart said:
For me getting SPen features on non-TW roms is far more important. It's the only reason I won't go near non-stock roms on the Note 3.
Click to expand...
Click to collapse
THIS WOULD BE IDEAL.
Weirdly, i have seen the SPen SDK Nearly in all Lollipop Samsung roms, even on S4/S5, WHY?
celderic said:
There was a TW based for for the s2, i9100. I think it was called chameleon rom? It was basically just Stock TW with the samsung camera app, but aosp dialer contacts, systemui etc
Click to expand...
Click to collapse
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
WideBRs said:
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
Click to expand...
Click to collapse
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
sirobelec said:
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
Click to expand...
Click to collapse
but what would be simpler and more efficient? AOSP features to TW rom or vice versa? I think, from user side, i would be more interested in getting TW (like Spen) to AOSP I dont use many TW features
As someone who used to make hybrid ROMs, I can tell you porting touchwiz to aosp is near enough impossible. Porting aosp stuff to touchwiz is easier. Tw camera to aosp just won't happen
Certain Touchwiz apps rely on code implemented across nearly all the framework files
Libs as well? No chance
Reverse engineering thousands of individual files and even more lines of code makes it a task comparable to setting up your own os...and smali is nothing like Java...so its not an easy way of getting touchwiz source code at all
DSA said:
As someone who used to make hybrid ROMs, I can tell you porting touchwiz to aosp is near enough impossible. Porting aosp stuff to touchwiz is easier. Tw camera to aosp just won't happen
Certain Touchwiz apps rely on code implemented across nearly all the framework files
Libs as well? No chance
Reverse engineering thousands of individual files and even more lines of code makes it a task comparable to setting up your own os...and smali is nothing like Java...so its not an easy way of getting touchwiz source code at all
Click to expand...
Click to collapse
Just for the record, back when I had an S4, the phone spent the most time with BlackBox, and it's exactly your ROM which made me ask this question, but I didn't have much hope you'd answer yourself.
Huge thanks for the input.
This thread could be very much eased down with the release of the Galaxy S6.
Sammy agrees for less bloat and less distance from AOSP, quoting the "rumours", it will be 99% Google, which most probably is a result of their cross licensing deals for patents.
March seems definitely exciting, even 5.1 can be in sight if Sammy gets a bit Nexus-ish, which will most definitely be the only reason i would go for Exynos, otherwise, no Sammy without openly documented hardware.
PlutoDelic said:
This thread could be very much eased down with the release of the Galaxy S6.
Sammy agrees for less bloat and less distance from AOSP, quoting the "rumours", it will be 99% Google, which most probably is a result of their cross licensing deals for patents.
March seems definitely exciting, even 5.1 can be in sight if Sammy gets a bit Nexus-ish, which will most definitely be the only reason i would go for Exynos, otherwise, no Sammy without openly documented hardware.
Click to expand...
Click to collapse
They say it will be as _fast_ as a Nexus, not that they're going AOSP. No one here thinks Sammy would leave their beloved TouchWiz.
Of course, if come Sunday I receive the biggest plot twist in recent Android history and the S6 ships close-to-AOSP, I'll be one of the happiest people alive, but I don't believe it will happen. xD
WideBRs said:
Is it possible to bring AOSP systemui to a TW ROM? I mean, not just a theme, for example, the notifications panel behaviour, lockscreen, settings menu, etc.
Click to expand...
Click to collapse
not impossible but really hard to do hence why nobody has done it
sirobelec said:
^ this is precisely what I'm talking about.
A dev would have to get the AOSP frameworks and libraries and modify them in such a way that they'd work with the TouchWiz frameworks AND kernel.
@Morningstar said it a couple of posts above yours:
"The TW source code can be obtained fairly easily (for the most part) by reverse engineering the apks/framework files. Integrating core components from TW (ie. S Pen features) into AOSP, however, would be an incredibly huge undertaking, as it would require reworking the vast majority of framework files. That's not to say it couldn't be done, but it would take an insane amount of time and effort, and frankly, I just don't see it being worthwhile. There are alternatives (via apps or what have you) to every feature TW has."
Click to expand...
Click to collapse
Im using part of applications AOSP on TW ROM like contacts, Phone Dialer, MMS, wisard and some mods on framework styling but we can t get the receptive calls and provider and UI for example
Sent from my GT-I8552B using XDA Free mobile app
sirobelec said:
They say it will be as _fast_ as a Nexus, not that they're going AOSP. No one here thinks Sammy would leave their beloved TouchWiz.
Of course, if come Sunday I receive the biggest plot twist in recent Android history and the S6 ships close-to-AOSP, I'll be one of the happiest people alive, but I don't believe it will happen. xD
Click to expand...
Click to collapse
So far we havent seen anything software wise from the S6, seems like they are hiding things well, the moment N4/S5 got released we straight away knew how the UI looked like.
I think Sammy knows that the only way to sell exynos and not load other brands ARM adaption is by being more open. I know this is "wishful thinking" up to a point, but there is no way (most) Snapdragon N3/S5 users will upgrade to Exynos S6, and i hope they are aware of that.
to summarize:
Slighlty Debloated
TouchWiz Optimised
It's not that the links say much, but as i mentioned earlier, there has been a weird Patent agreement between Google, Cisco and Samsung (and Microsoft to a point), and S6 might be the first device to use them properly.
Vote for your Favourite *Unsupported* Rom to be given weeklies!
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!
Reserved for Results
Reserved for Results
Note3 Revive Team said:
Vote for your Favourite *Unsupported* Rom to be given weeklies!
Please Note i will only support the N9005, hlte.
Why?
Currently the amount of lollipop AOSP/CM based roms for the Note 3 is running a tad short for my liking, i believe in choice and i believe that if you have the hardware to do it, why not? I will be running this poll for a week to see which Roms you guys want to see rolling out for the Note 3 and i will roll them out to you on a weekly basis, i can probably build a few roms in a day so the top few will be what i choose to support.
If you want a Rom added to the Poll just ask me and i'll add it, so what are you waiting for? Vote and i'll start rolling them out!
Click to expand...
Click to collapse
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/
sirobelec said:
This one probably is just wishful thinking, due to the fact that back on JB/KK it was very difficult for the dev, now with LP it will be even more difficult.
There used to be a ROM for the S4 named BlackBox.
It was a hybrid between TouchWiz and AOSP, the dev ported AOSP frameworks and libraries to work with TouchWiz. The ROM was SICK. And not easy to do. Not sure if the ROM had an altogether different kernel or any TW kernel could work.
Wishful thinking... :/
Click to expand...
Click to collapse
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?
Note3 Revive Team said:
That is probably beyond my skills as ive never ported, only built from source, however i'll get in touch with the developer of that Rom and see if he is willing to lend a hand to try get that going for the Note 3, i honestly thought there would be more interest on this thread thou..
Any AOSP/CM roms you want for weeklies haha?
Click to expand...
Click to collapse
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.
sirobelec said:
As odd as it is, I got used to the close-to-stock TW ROMs. Don't mistake me, AOSP ROMs are fast as Hell, way more moddable, more beautiful, and I like that. However, for the way I use my Nope 3, close to stock suits my needs better.
Click to expand...
Click to collapse
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??
Note3 Revive Team said:
It's rare you find a samsung device where people are actually happy with Touchwizz
So is no one interested in suggesting weeklies for an AOSP Rom? Or perhaps i should make a custom stock (Not that there are enough already)?
I honestly thought there would be more interest in this thread! What's going on guys??
Click to expand...
Click to collapse
I believe it might be something like this...
The user base needs something entirely different from the two (three if you count MIUI) options, we've got used to it. And some people might have the ideas for something different but lack the skills to do it. On one side you have AOSP (most of the AOSP ROMs function and behave almost the same; simple fact, not bashing the work of anyone, I don't have the knowledge to bash it ), on the other - TouchWiz. Both have their uses.
I lack the knowledge on how to do it, apparently the whole team of Samsung that makes TouchWiz doesn't (xDDDDDDDDDDDDD)... to combine all the functionality of the device at it's top performance with a really sleek UI implementation that's different enough to make the user treat and use the device differently.
Otherwise, I'd theme TW with black, grey, blue, holo colors n stuff and make the UI look like the control panel of some spaceship seen in sci-fi. The device itself carries the "Galaxy" moniker, ffs, and Samsung made it sound and look like a f***ing toy!
Making an AOSP ROM then stabilizing it, from what I've read, is no easy task for the whole Google team, it seems...
I am afraid that the Note 3 simply lacks the attraction to crackheaded devs who would tear Ubuntu Touch's a** in half, merge it with AOSP then slap that combination on top of whatever's left of TouchWiz. xD We have most of the major AOSP ROMs, can't tweak too much TW because of it's damn closed source, and... that's that. :/
Sorry if this was incoherent.
P.S. I am also sorry if any of this seems disrespectful, I don't mean it to be, given the fact that you're willing to actually build the ROM that's most demanded. Wish you luck.
Those are 2 recognize ROMs since my Nexus 5. :laugh:
ps000000 said:
Those are 2 recognize ROMs since my Nexus 5. :laugh:
Click to expand...
Click to collapse
Well when i hit 10 posts, and perhaps a little more interest is gathered in the thread then i can get these builds of vanir and nameloss rolling out to the community.
I am suprised thou i really am that no one seems to use AOSP/CM roms on the galaxy note 3!
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.
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