Sony RRO layers - OnePlus X General

Just a question, is there any OnePlus X rom that is compatible with RRO Layers ? If yes, wich ones ?
Most i can find use/support the CM Theme Engine, wich means they aren't compatible if i understood it properly.

In case you didn't notice, Layers is Depreciated now, Substratum has taken its Place. Some Google-fu will get you better results.
And yes, many ROMs use(d) Layers, a lot of them have now moved up from RRO to OMS, you can check my Index for a list of all available ROMS.

Joshwin Aranha said:
In case you didn't notice, Layers is Depreciated now, Substratum has taken its Place. Some Google-fu will get you better results.
And yes, many ROMs use(d) Layers, a lot of them have now moved up from RRO to OMS, you can check my Index for a list of all available ROMS.
Click to expand...
Click to collapse
Hum no i hadn't noticed, guess it's something else i missed (rahhh it's getting complicated in the end ).
Thanx for the info.

Related

Some projects that in my opinion should be combind...

Hi, I'm Itzik I'm a newbie and yes, I'm a complete ***ing n00b!
But before each and everyone of you discard my opinion as complete rubbish, please ask yourself this:
Should I not adopt a reasonable and efficient perspective for it came to be from an inferior being? (I believe most of reasonable people will get my point)
Therefore I resume:
There are certain projects here on i9100 section or should I say developers that should combine their efforts into a more efficient working method, there are certain projects that are being developed & published here that in core are the same.
Those MODs & themes are being developed separately by different developers and get published by different names when in fact, they are all fragmented parts of a whole.
So many developers, so much work time and resources are being diverted between so many different projects that eventually each one of them separately when applied, gets the devices to a very similar point, except for one or two (crucial ,I might add) features that are made differently and therefore, only fragmenting more the already messy and confusing situation at hand.
By now I believe most of you know what I'm talking about, and I bet there more people here like me that would like to see those combined projects become a reality.
Now, I want to clarify Myself, that under no circumstances am I saying that the work of those people is not important, or not good enough nor heaven forbid unappreciated, what I'm trying to say, is that if those developers would work together and distribute the work between them, it could help saving them a lot of work and time and make the end results much better.
Lets start with our beloved _JKay_, he practically changed the rules of the game with his MOD, in fact the only thing I find lacking in JKay's work is a more productive and efficient theming capability, witch is exactly what the other developers I'm talking about make complete.
I'm talking about those projects:
[THEME]ICS DOMINATION v4.4*DESIRE(Progress NEW 41%)Odex/Deodex*LPS/3/4/7/8/9/D/F*Live by Vertumus
[MOD] ICS-styled SystemUI for KPA/LP2/LP6/LPB/LPH/LPQ/LP7/LP3/LPS by Sboulema
[MOD][ALL ROMS] ICS Style Reloaded -[ 28/05 Green online! - soon CM9 ]- by Crussader
Now, what we have here are 3 projects that focuses on one objective: a theme that would give SAMSUNG's Stock based ROM's the look and feel of an AOSP based ROM.
What differs between them is that Vertumus's approach was theming the entire ROM while Sboulema's & Crussader's approaches ware a bit less ambitious as they only themed and tweaked the TouchWiz UI overall a bit.
To be precise:
Vertumus re-designed the whole TouchWiz UI framework to match a AOSP based framework on which he dressed his theme.
Sboulema's method was (much like JKay's) to replace the original PNG files on the TouchWiz UI framework to his own files.
Crussader's MOD is based on Vertumus's re-designed UI framework and Sboulema's files + he added lidroid's MOD which is one feature of many in JKay's MOD.
End result is 3 different MODs that basically give the user the same thing +/- a feature or two...
Combining those 3 projects (and others similar) into one project and working with JKay to match his framework to adopt those themes will save JKay the time and hassle of creating themes for his mod + making those 3 themes into 1 will make it easier on the developers that makes them to update the themes to match future firmware updates.
So, what say you?
Good Luck!!
It's a nice thought and plenty of devs/themers do co-operate whilst some are amazing enough on their own (jkay, vert etc).. you'll always get a lot of duplicate efforts as some innovate and others replicate.. which isn't necessarily a bad thing, can be a stepping stone to something innovative in the end
good thought
Nonsense.
Devs have specific stuff they like to work on (normally their own projects/kernels/roms), why should they team up & work on projects we want ?
They're not at our beck & call despite what you seem to think.
Instead of making threads like this, why don't you learn to code/theme/whatever & then work on the things you've mentioned ?
P.S - The three examples you've mentioned, that's not development. That's winzipping/theming. There's a difference.
Posters forget its a free mods choice as to how why what and where .
They are not here to make life easier for you but to develop stuff and thankfully allow us to use it or not .
That was the ethos behind this developers forum originally sadly now just a give me give my i want i want forum.
jje
MistahBungle said:
Nonsense.
Click to expand...
Click to collapse
If you say so, you know best.
MistahBungle said:
Devs have specific stuff they like to work on (normally their own projects/kernels/roms), why should they team up & work on projects we want?
Click to expand...
Click to collapse
True, but if you can tell the difference, those are not project I want or we want, those are projects that are already being worked by them.
I only recommended them to to gather up similar projects so it could ease-up their work, and help them make more much needed free time for their own personal life, family, career whatever.. everyone could use a little extra time on their hands...
MistahBungle said:
They're not at our beck & call despite what you seem to think.
Click to expand...
Click to collapse
You seem to have gotten the wrong impression, please understand that this totally & clearly not what I meant.
MistahBungle said:
Instead of making threads like this, why don't you learn to code/theme/whatever & then work on the things you've mentioned?
Click to expand...
Click to collapse
Had my I.Q level allowed me to, there are a lot of things I would have done myself instead of turning to people for help, but we all work with what we got... JKay and others like him got the brain, I got a 'wider picture' vision and you got.. well whatever it is you've got there mate, whatever makes you keep the flow man...
MistahBungle said:
P.S - The three examples you've mentioned, that's not development. That's winzipping/theming. There's a difference.
Click to expand...
Click to collapse
Be that as it may, and call it as you wish, end result is that they all work on different projects that eventually leads to one point, one way or the other.. combining their efforts would only help increase efficiency...
Sorry if I offended anyone as it was completely and entirely not my intention!
good day fellows...
JJEgan said:
Posters forget its a free mods choice as to how why what and where .
They are not here to make life easier for you but to develop stuff and thankfully allow us to use it or not .
That was the ethos behind this developers forum originally sadly now just a give me give my i want i want forum.
jje
Click to expand...
Click to collapse
I would like to refer you to my answer to MistahBungle, that would shed a bit light on my intentions...
Thank you but my comments remain for a large majority of users noobs or not .
I did not add to my post >> whereas the idea of combining stuff may well be a vast improvement . Its been done before suggested before and devs go their own way .
If you read the dev posts then the usual is master dev makes xxxx and along comes a new dev who is learning and releases a modification on xxxx and so it goes on .
Your probable point that a better end result can be achieved by combining devs is not wrong . Yes in my view SGS2 development tends to be rather repetitive try finding a gold ICS rom .
jje
PS Welcome to the forum

Is there any comparison matrix available comparing features of different ROM's?

Is there any thread around comparing different ROM's available feature wise? Kind of a matrix? With so many ROM featuring several common features and many unique ones it will be helpful if you are trying to find a ROM with similar feature if you are having trouble with what you are on.
webharsh said:
Is there any thread around comparing different ROM's available feature wise? Kind of a matrix? With so many ROM featuring several common features and many unique ones it will be helpful if you are trying to find a ROM with similar feature if you are having trouble with what you are on.
Click to expand...
Click to collapse
Don't think there are any at the moment..Maybe you should start a thread like that in the General section.
Good idea, but it could be huge and very time consuming keeping it up to date.
I saw something like this, I think in the Nexus 7 forums. It was just an Google Drive spreadsheet
My exams are just over, I might have the time to do that.
Any list of a few ROMs I should definitely try out?
jiayit said:
My exams are just over, I might have the time to do that.
Any list of a few ROMs I should definitely try out?
Click to expand...
Click to collapse
Try them all for a good comparison
There is something like.. 60-70 ROMs o_o
And I'd most likely make it into a Google spreadsheet, based on this: http://forum.xda-developers.com/showthread.php?t=2006616
Btw, would you guys want a detailed comparison, like for example
Nav Bar Height | Nav Bar Colour | Nav Bar Transparency
--------Yes-------------------No---------------------Yes---------------
or Customizable Navbar
------------- Yes
jiayit said:
There is something like.. 60-70 ROMs o_o
And I'd most likely make it into a Google spreadsheet, based on this: http://forum.xda-developers.com/showthread.php?t=2006616
Btw, would you guys want a detailed comparison, like for example
Nav Bar Height | Nav Bar Colour | Nav Bar Transparency
--------Yes-------------------No---------------------Yes---------------
or Customizable Navbar
------------- Yes
Click to expand...
Click to collapse
May be it can be started with ROM's from Original Android Development Forums with basic feature comparison like default Kernel, Navbar Customization (Yes, No, CM, AOKP), Pie (CM or PA), PA Colours, Center clock etc., per App DPI, ribbon etc.
webharsh said:
May be it can be started with ROM's from Original Android Development Forums with basic feature comparison like default Kernel, Navbar Customization (Yes, No, CM, AOKP), Pie (CM or PA), PA Colours, Center clock etc., per App DPI, ribbon etc.
Click to expand...
Click to collapse
Yup, I've made a rough draft but I don't have much support from the members, might just consider abandoning the project.. BRB while I find my thread.
Edit: here
http://forum.xda-developers.com/showthread.php?t=2283179
Only 1 person actually participated in the thread, is that saddening or saddening
jiayit said:
Yup, I've made a rough draft but I don't have much support from the members, might just consider abandoning the project.. BRB while I find my thread.
Edit: here
http://forum.xda-developers.com/showthread.php?t=2283179
Only 1 person actually participated in the thread, is that saddening or saddening
Click to expand...
Click to collapse
That looks great. Maybe we can start with a simpler (smaller?) format and smaller set of feature and make the spreadsheet shared so everyone can update it with their experience. Also instead of 60 something ROM, ROM's in original android development could be starting point.
webharsh said:
That looks great. Maybe we can start with a simpler (smaller?) format and smaller set of feature and make the spreadsheet shared so everyone can update it with their experience. Also instead of 60 something ROM, ROM's in original android development could be starting point.
Click to expand...
Click to collapse
Sorry, it's my first time messing with Google Docs, is there any way to moderate edits before they are saved? I think if I open the doc, some jokers will definitely delete the entire doc or something.
Thanks for the suggestions ^_^
Its a good project for someone.
-Sent from Marino's Nexus 4-
jiayit said:
Sorry, it's my first time messing with Google Docs, is there any way to moderate edits before they are saved? I think if I open the doc, some jokers will definitely delete the entire doc or something.
Thanks for the suggestions ^_^
Click to expand...
Click to collapse
Well I see a shared google doc for Nexus colors or something, we can make something similar. I'll try to dig something today to figure out what we can do.
webharsh said:
Well I see a shared google doc for Nexus colors or something, we can make something similar. I'll try to dig something today to figure out what we can do.
Click to expand...
Click to collapse
The thread is here: http://forum.xda-developers.com/showthread.php?t=2039607
And in post #6, OP mentioned that he has to make frequent backups. I'll have the weekend to flash as many ROMs as I can then!

How Are All These ROMs Different?

If a ROM is based on CM12, ITS STILL CM12! The ROM may have features NOT included in stock CM12, BUT IT'S STILL CM12. (Euphoria, Temasek, Blisspop, etc)
If a ROM is based on AOSP, ITS STILL AOSP! The ROM may come with features not avaliable in stock AOSP , BUT ITS STILL BUTT-NAKED AOSP! (SlimSaber, Paranoid Android, XenonHD, etc)
The two things separating MOST ROMs (Performance wise) are the kernel, optimizations, and the toolchain the ROM is made/built with (Stock GCC/Linaro/Sabermod).
IMO: SABERMOD ROMS > LINARO ROMS> STOCK GCC ROMS
So to sum it all up, you guys are downloading the same based ROMs over & over. Its a placebo if you think one cm12 is far superior than another cm12 ROM. They're BOTH cm12 and are both good..
The KERNEL you decide to use will normally have the greatest impact on performance (STOCK, AK,TGM, TYR, FRANCO, ETC)
Please correct me if I'm incorrect. Thanks.
Well said my friend well said!
dragoi90 said:
Well said my friend well said!
Click to expand...
Click to collapse
Thanks?
del
bachera said:
del
Click to expand...
Click to collapse
What's your current rom & kernel?
A certain ROM can be faster than the other. Some have more optimisations for the specific device, so i dont really know what your point is. Some roms also have more features than the other, sometimes with a negative effect on the performance (think about dynamic status bars build in).
If all the roms are the same, why do you prefer sabermod over the other compilers?
Sent from my A0001 using XDA Free mobile app
mumaster20 said:
A certain ROM can be faster than the other. Some have more optimisations for the specific device, so i dont really know what your point is. Some roms also have more features than the other, sometimes with a negative effect on the performance (think about dynamic status bars build in).
If all the roms are the same, why do you prefer sabermod over the other compilers?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
We're talking specifically oneplus one roms. Device doesn't matter.
As for sabermod being superior, its subjective. I do recommend you download a kernel such as TGM, or TYR who offer both LINARO & SABERMOD versions and see which is faster/optimal. For me it has been Sabermod. Much snappier.
Edit: http://forum.xda-developers.com/oneplus-one/general/kernel-tgm-toolchain-testing-help-best-t3003754
What you're failing to realise here is that even though a great deal of ROMs are based on CM, many actually contain unique code and extra features, which can both have a positive or negative effect on performance, smoothness, battery life, and other aspects. If they didn't contain unique code they'd be seen as kangs and removed immediately. You're essentially saying that all ROMs are the same, and that only a different kernel can differentiate them. This is not only wildly inaccurate, it shows a gross lack of understanding about what actually goes into creating a ROM, and it's highly offensive to the developers who spend their spare time providing people like you with these ROMs completely free of charge.
Transmitted via Bacon
Good info. Thanks!
SensualPuma said:
Good info. Thanks!
Click to expand...
Click to collapse
No, it isn't good info, it's entirely incorrect.
Transmitted via Bacon
timmaaa said:
What you're failing to realise here is that even though a great deal of ROMs are based on CM, many actually contain unique code and extra features, which can both have a positive or negative effect on performance, smoothness, battery life, and other aspects. If they didn't contain unique code they'd be seen as kangs and removed immediately. You're essentially saying that all ROMs are the same, and that only a different kernel can differentiate them. This is not only wildly inaccurate, it shows a gross lack of understanding about what actually goes into creating a ROM, and it's highly offensive to the developers who spend their spare time providing people like you with these ROMs completely free of charge.
Transmitted via Bacon
Click to expand...
Click to collapse
That is very true. I do have a lack of understanding like most people who aren't developers.
However, I have searched & found no where on this forum a that explains what separates one CM12 rom from another CM12 rom besides the cherry picks, toolchain, and kernels.
That was my entire bases of creating this thread. To gain enlightenment and resolve confusion that myself and others may have.
OmegaBlaze said:
That was my entire bases of creating this thread. To gain enlightenment and resolve confusion that myself and others may have.
Click to expand...
Click to collapse
It doesn't seem like that at all though. The way you've worded your OP is a statement, like you've made some grand discovery. Rather than asking the question "how are all these ROMs different?", you're proclaiming "these ROMs are all exactly the same". It just isn't true.
I'm not going to go into the details, because honestly, I'm just not that articulate, I'd make a mess of it. But why not invite some of the devs of the ROMs you're talking about into this thread by tagging them? They would no doubt be able to explain exactly where your logic is incorrect, if they can be bothered of course.
Transmitted via Bacon
timmaaa said:
It doesn't seem like that at all though. The way you've worded your OP is a statement, like you've made some grand discovery. Rather than asking the question "how are all these ROMs different?", you're proclaiming "these ROMs are all exactly the same". It just isn't true.
I'm not going to go into the details, because honestly, I'm just not that articulate, I'd make a mess of it. But why not invite some of the devs of the ROMs you're talking about into this thread by tagging them? They would no doubt be able to explain exactly where your logic is incorrect, if they can be bothered of course.
Transmitted via Bacon
Click to expand...
Click to collapse
If developers feel like chiming in, they can. Most won't.
And we already know that all of these roms are NOT the same. Kanging is not allowed on XDA.
Please dont put words in my mouth. No where in my post or title does it state that all of these roms are the same.
OmegaBlaze said:
If developers feel like chiming in, they can. Most won't.
And we already know that all of these roms are NOT the same. Kanging is not allowed on XDA.
Please dont put words in my mouth. No where in my post or title does it state that all of these roms are the same.
Click to expand...
Click to collapse
No you don't say those exact words, but that is what it looks like your post is implying. If that isn't the case then you might need to clear up your OP a bit. Your last sentence says to correct you if you're wrong, that's exactly what I'm doing, the kernel and toolchain aren't the only things that separate these ROMs, not by a long shot.
Transmitted via Bacon
OmegaBlaze said:
Please dont put words in my mouth. No where in my post or title does it state that all of these roms are the same.
Click to expand...
Click to collapse
OmegaBlaze said:
If a ROM is based on CM12, ITS STILL CM12!
...
If a ROM is based on AOSP, ITS STILL AOSP!
...
So to sum it all up, you guys are downloading the same based ROMs over & over.
Click to expand...
Click to collapse
His summary of your words is fair enough and seems to capture the spirit of the point you were trying to make in the OP.
Honestly, I see a kernel of truth in the OP, no pun intended. There are lots of noobs around here trashing CyanogenMod for not squashing their pet bugs or fixing their favorite feature in a timely enough fashion. They usually post some garbage accusing CyanogenMod of delinquency or poor quality, then say something like, "This is a deal breaker for me. CyanogenMod is a bunch of jerks. I'm flashing back to xxx ROM," which is based on .... You guessed it: CyanogenMod! Then after a couple days, they're right back in the CyanogenMod nightly thread.
It's no wonder why devs don't post much in General. What profit would there be in it for them other than to be trashed by a bunch of thankless noobs over nothing?
This is isn't entirely true, as @timmaaa already pointed out. The ROMs which are AOSP like Slim, Euphoria get their code from CAF-AOSP. While the CM ROMs like temasek, Validus use the actual CM code, which itself is actually modified CAF-AOSP. Note that whatever I wrote is just for OPO as there isn't any TRUE or NATIVE AOSP Code for our device like there is for Nexus ones etc.
Also, Omni is very well Pure AOSP as those guys write their own open source versions of various hardware drivers etc and thus don't need the CAF variants
CafeKampuchia said:
His summary of your words is fair enough and seems to capture the spirit of the point you were trying to make in the OP.
Honestly, I see a kernel of truth in the OP, no pun intended. There are lots of noobs around here trashing CyanogenMod for not squashing their pet bugs or fixing their favorite feature in a timely enough fashion. They usually post some garbage accusing CyanogenMod of delinquency or poor quality, then say something like, "This is a deal breaker for me. CyanogenMod is a bunch of jerks. I'm flashing back to xxx ROM," which is based on .... You guessed it: CyanogenMod! Then after a couple days, they're right back in the CyanogenMod nightly thread.
It's no wonder why devs don't post much in General. What profit would there be in it for them other than to be trashed by a bunch of thankless noobs over nothing?
Click to expand...
Click to collapse
Yes, you kind of get of what i'm trying to say.
People flash rom xyz, get tired of it and flash rom "abc". Not knowing that rom "abc" is based off of xyz. You still have the same bugs, and same or only a negligible difference in performance.
That's what I meant by and AOSP is still an AOSP rom. Cm12 is still a Cm12 rom.
ViditM14 said:
This is isn't entirely true, as @timmaaa already pointed out. The ROMs which are AOSP like Slim, Euphoria get their code from CAF-AOSP. While the CM ROMs like temasek, Validus use the actual CM code, which itself is actually modified CAF-AOSP. Note that whatever I wrote is just for OPO as there isn't any TRUE or NATIVE AOSP Code for our device like there is for Nexus ones etc.
Also, Omni is very well Pure AOSP as those guys write their own open source versions of various hardware drivers etc and thus don't need the CAF variants
Click to expand...
Click to collapse
:good: Thanks for the enlightenment.
I never knew CAF-AOSP was Cyanogenmod. I thought is was just a slighty modded version over AOSP unrelated to CM.
I've also heard that OmniRom for our device is CAF-AOSP.
OmegaBlaze said:
:good: Thanks for the enlightenment.
I never knew CAF-AOSP was Cyanogenmod. I thought is was just a slighty modded version over AOSP unrelated to CM.
I've also heard that OmniRom for our device is CAF-AOSP.
Click to expand...
Click to collapse
Yep, But Omni gets it quite differently. They make many of own their stuff and always keep as close to AOSP as possible
OmegaBlaze said:
:good: Thanks for the enlightenment.
I never knew CAF-AOSP was Cyanogenmod. I thought is was just a slighty modded version over AOSP unrelated to CM.
I've also heard that OmniRom for our device is CAF-AOSP.
Click to expand...
Click to collapse
kindly change first post to contain only the answer
Sent from my A0001 using XDA Free mobile app

The death of CMTE and possibilities for a new one

We all probably remember CMTE (CyanogenMod Theme Engine) and how it was killed in LineageOS. I had an idea of what could be added. In Paranoid Android 7, there is a new setting called "Color Engine" and what it allows you to do is change the accent color and other things to fix your needs. What if this was added to LineageOS? I feel it could be a good idea and it makes sense. Some people may prefer to just change the accent color. Now, I know, you'll say "Just get Substratum!" but so people don't want root. There are themes that let you do things like that but having this baked into the system would be awesome! :good: What would you like? Post your ideas in the comments!
substratum
Sent from my Nexus 5 using Tapatalk
The LineageOS team has been actively working on a Theme Engine.
It looks, to me, that they can't port the old CMTE as a whole but, they are trying to salvage what they can of the old CMTE and rework the it into LineageOS as a whole new Theme Engine.
If you want to see, just a portion of their work, then you can see it on the following Gerrit link.
https://review.lineageos.org/#/q/theme_engine
Just because it's been a while doesn't mean that it won't happen.
Yes, Substratum and a few others are out there that individuals can use in the meantime but, it'll come.
Patience is a virtue...
***Please Note: As always, I welcome any member to help with further valuable information/clarification for any of my posts.
Sent via Communicator [d2vzw] from the Bridge of the U.S.S. Enterprise.

Development News Discussion

I think the pixel devices are a haven for android development. like a tree has a trunk and then branches , lol the pixels are like the trunk and other manufactures other than google are branches. not exactly but in someways, yes
THIS THREAD IS FOR CENTRALIZING DISSCUSSION
What android features are developers working on? What features do enthusiasts what to see?
Ideas, requests, reminders. Hopefully you'll be heard here
I would like phone theme-ing to be more compartmentalized.
Still wanna see a bootloader unlock for Verizon variant.
alladinscastle said:
I think the pixel devices are a haven for android development. like a tree has a truck and then branches , lol the pixels are like the truck and other manufactures other than google are branches. not exactly but in someways, yes
Click to expand...
Click to collapse
that's not really true. AOSP may be the trunk, but the pixel line is just a branch or two - Google just showcases their stuff on pixel devices first...
alladinscastle said:
THIS THREAD IS FOR CENTRALIZING DISSCUSSION
What android features are developers working on? What features do enthusiasts what to see?
Click to expand...
Click to collapse
doesn't it make more sense to encourage users to visit the dedicated thread of a given piece of software that developers already have created VS. trying to have a centralized thread?. ... I mean the pixel forum IS centralized and leads to all of the development, software and support threads already...I'm confused, i don't understand the point....?
alladinscastle said:
I would like phone theme-ing to be more compartmentalized.
Click to expand...
Click to collapse
how so?. ... I mean, as is theming is very compartmentalized, at least in terms of it being granular, on a per-app or overlay basis... therevarevstill a few annoyances with Theming, but it's not too bad...
Part1, first come first serve.
Part2 if we where to use this thread, there would be a better spread of knowledge and less harrassing OPs with cluttered responses, expectations, the usual
Part3 I would like to customize my device without using substratum theme. A more of a layer by layer or mix and match custom options that would be possible with coding approach. Bold- maybe, impossible- nothing. Using one's own choices or prereadied themes
https://www.xda-developers.com/otgs...stratum-themes-directly-on-a-phone-or-tablet/
Linking article for OTGSubs. Looks cool
abranson said:
Still wanna see a bootloader unlock for Verizon variant.
Click to expand...
Click to collapse
I'm Verizon, I got in early when the getting was hood
I thought of a few things like replacing stock boot image with modified signed one, but had an androidinfo.txt error, and if we can't get temp root to bypass, for now, maybe I can find a way to change my imei?
alladinscastle said:
Part1, first come first serve.
Click to expand...
Click to collapse
it doesn't change the fact that all of the OEMS/vendors are building roms using AOSP, not the pixel line... so not really first come first serve.
alladinscastle said:
Part2 if we where to use this thread, there would be a better spread of knowledge and less harrassing OPs with cluttered responses, expectations, the usual
Click to expand...
Click to collapse
you are talking about lumping the entire forum into one thread. meanwhile the forum is nicely divided into categories /sections and is easy to navigate.... furthermore, as a developer; I would prefer any discourse regarding any development that I do, happen in the thread that I created, rather than some mega thread with 100 different topics all overlapping with replies. that's super ineffective, would mean I would have an additional, very disorganized thread to follow and email notifications would be useless..... I can appreciate your intentions, but I can monitor my thread, no need for a third party to intervene.
I do think this is a great idea, for people to point out new articles, features or stuff elsewhere as a newsfeed or something and general discussion... but I think developers can manage their threads better than letting another party do it for them... or putting them in a position where they will have to monitor an additional thread...
alladinscastle said:
Part3 I would like to customize my device without using substratum theme. A more of a layer by layer custom options that would be possible with coding approach. Bold- maybe, impossible- nothing
Click to expand...
Click to collapse
substratum is a layer by layer approach. you can mix and match all that you like, changrle the priority / ordering of layers, etc, etc...
coding approach how? explain in detail, without being vague. do you have any code i can look at? .... I'm not sure that i see how you would accomplish any theming engine without direct ROM support, like the old cm theme engine or OMS/RRO support in AOSP.
Good to know on the AOSP. Maybe their ports will land on pixel soon?
It is unreasonable to see developers updating there's thread here. Very unreasonable. I thought I might see developers like yourself, thanks for the kernel, post here like say... I might start a new project, is their community support for this? That sort of thing. And the community post here with ideas, requests. That sort of thing. Could lead to more participation, and less threads being created that are simply comments that belong here.
The OTGSubs I found sounds like exactly what I was meaning. Just something to get more freedom from prereadied themes. The build your own theme engine. Holla, I do love ya'lls themes usually. I'm gonna go play with OTGSubs.
alladinscastle said:
Good to know on the AOSP. Maybe their ports will land on pixel soon?
Click to expand...
Click to collapse
youbare already running lots of code on your pixel that was committed upstream by Google's partners.
alladinscastle said:
It is unreasonable to see developers updating there's thread here. Very unreasonable. I thought I might see developers like yourself, thanks for the kernel, post here like say... I might start a new project, is their community support for this? That sort of thing. And the community post here with ideas, requests. That sort of thing. Could lead to more participation, and less threads being created that are simply comments that belong here.
Click to expand...
Click to collapse
I getcha. on a new project, I might do that, but for myself anyway; if I release a peice of software, then I'm still going to startba dedicated thread... so like a newsfeed; I could mention / link to it from here but that's about it.
but I can see what ur driving at now.
alladinscastle said:
The OTGSubs I found sounds like exactly what I was meaning. Just something to get more freedom from prereadied themes. The build your own theme engine. Holla, I do love ya'lls themes usually. I'm gonna go play with OTGSubs.
Click to expand...
Click to collapse
otgsubs is for substratum though. you said you didn't want substratum...I'm confused. lol.... iirc, there are several apps like this for modding or creating themes that make use of substratum / OMS.... nice to see more of that around though.
I'd love to see an exploit for vzw Pixel to root/unlock my bootloader.
ztotherad said:
I'd love to see an exploit for vzw Pixel to root/unlock my bootloader.
Click to expand...
Click to collapse
Wouldn't we all
Sent from my Pixel using Tapatalk
The January security update is now allowing deodex. I myself cannot bring myself to update yet. The work done on my phone now cannot be undone. Some where else in the forum it was said that themes (Subs) should be reset before flashing .
What else is locked or waiting to be found within pixel? Today I was hoping WiFi calling would be simple. I failed. Does someone know more about this topic or WiFi calling's ties to HD video calling? Also a screenshot. Yeah
I need too amend my prior post to say "HD voice"
alladinscastle said:
What else is locked or waiting to be found within pixel? Today I was hoping WiFi calling would be simple. I failed. Does someone know more about this topic or WiFi calling's ties to HD video calling? Also a screenshot. Yeah
Click to expand...
Click to collapse
I haven't taken/received the Jan update yet, but then again I'm not going to sideload it on my phone. I'm still hoping for an unlock like the pixel 2/XL2, but my hope is dwindling.
Here is something I found via Google about a bootloader exploit https://www.google.com/url?sa=t&sou...FjARegQIBhAB&usg=AOvVaw2mjG3yppFcxSunZI9TGsvi
snipinu said:
Here is something I found via Google about a bootloader exploit https://www.google.com/url?sa=t&sou...FjARegQIBhAB&usg=AOvVaw2mjG3yppFcxSunZI9TGsvi
Click to expand...
Click to collapse
honestly that looks old. it's talking about the oneplus 3/3T
edit: looking at it it may be feasible, but if it was then why has no one else taken it upon themselves to try to exploit? i would but i don't know the first thing about this stuff (exploiting exploits)
Talks about the pixel too some form of exploit. I just did a random search and found that PDF.
snipinu said:
Talks about the pixel too some form of exploit. I just did a random search and found that PDF.
Click to expand...
Click to collapse
yeah quick reading that's what i saw. I'd personally love to try to exploit the meltdown/spectre exploits, but idk if it's feasible.

Categories

Resources