I just had a question on whether anyone knows any ROM devs that either keep as close to stock "vanilla" android, or if anyone knows the least amount of things that have to be coded to create a "vanilla" ROM.
I don't know if I am the only person who would like just straight up google android 2.3 to rn with their non-modded UI, but that is honestly what I'd like.
If I have to I will create my own as long as I know the super basic things I have to change to get it to run.
I had a G1 with CyanogenMod on it and while I enjoyed CM, I have no idea if they even plan to make a version of CM 7 for the shift.
killstapp said:
I just had a question on whether anyone knows any ROM devs that either keep as close to stock "vanilla" android, or if anyone knows the least amount of things that have to be coded to create a "vanilla" ROM.
I don't know if I am the only person who would like just straight up google android 2.3 to rn with their non-modded UI, but that is honestly what I'd like.
If I have to I will create my own as long as I know the super basic things I have to change to get it to run.
I had a G1 with CyanogenMod on it and while I enjoyed CM, I have no idea if they even plan to make a version of CM 7 for the shift.
Click to expand...
Click to collapse
This is probably the thread to check out http://forum.xda-developers.com/showthread.php?t=936822
why thank you good sir.
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!
I have a question is it possible to disable or uninstall touchwiz for android stock ? thanks
Unfortunately I do not think this is possible, you can install a launcher of your preference, but the rest of the interface will be Touchwiz. We will have to wait for an AOSP rom to come out, or for CM13 to become stable for daily use and available for all variants of the S6.
With the S6's in-house built Exynos and Samsungs lack of documentation on it, it could be a while before you see any stable AOSP based roms, I'm hoping someone will find a way soon
thommasnd said:
I have a question is it possible to disable or uninstall touchwiz for android stock ? thanks
Click to expand...
Click to collapse
Touchwiz is part of the system setup, so unless someone builds a fully working cyanogen build which is very difficult as Samsung don't release chips chipset sources you won't see complete removal of Touchwiz, you can change the launcher that's it.
sofir786 said:
Touchwiz is part of the system setup, so unless someone builds a fully working cyanogen build which is very difficult as Samsung don't release chips chipset sources you won't see complete removal of Touchwiz, you can change the launcher that's it.
Click to expand...
Click to collapse
ok thanks
Samsung have become (have they ever?) somewhat open source unfriendly. Being a big competitor against Apple may have something to do with it (don't want them stealing ideas or anything ?).
But yes, as the others said, because of so much proprietary shizzle under the hood, a lot of hardware specific code needs reverse engineering and testing intensively. Very time consuming for the guys that do it (so if/when they succeed, be kind and donate for the work).
To further complicate matters, Touchwiz isn't just a bolted on addition to provide something to look at. It is deeply integrated into some of the base code of the android system. Which is a p.i.t.a. for those of us that like to customise etc. Try to remove one part at the whole thing collapses into a mess.
Just so you know, work on a CyanogenMod 13 release is underway. But due to the undocumented hardware modules, the development is barely even beta status and only recommended for developers. But it is happening ?
(I really should sleep before posting, as I waffle a lot when I'm tired ?)