i'm a little impatient actually , since 4.6 beta 5 was the best rom i have ever used on my s4 .
would like to know around when can we expect 5.0 lollipop on the i9505 jflte ??
We don't officially support that device. You would need to keep an eye on the legacy community for an update. Asking for an ETA is really not going to get you an answer either.
#stayparanoid
I know we will have to see what the future brings but, are there any developers willing to develop custom roms for us Tab S owners?
I know CM12 is Available for the Non-LTE Variants, i am an LTE owner so, i dont have any sort of Lollipop on my T705, was just wondering, since Custom Development for T705 has stopped for a while (besides IronRom which is mainly a 805, and SkyHigh, which is my daily driver)
Satorikn said:
I know we will have to see what the future brings but, are there any developers willing to develop custom roms for us Tab S owners?
I know CM12 is Available for the Non-LTE Variants, i am an LTE owner so, i dont have any sort of Lollipop on my T705, was just wondering, since Custom Development for T705 has stopped for a while (besides IronRom which is mainly a 805, and SkyHigh, which is my daily driver)
Click to expand...
Click to collapse
is cm12 based on lolipop? if so how when lolipop hasnt been offically released?
sweetandsoursauce said:
is cm12 based on lolipop? if so how when lolipop hasnt been offically released?
Click to expand...
Click to collapse
CM12 is based on Lollipop.
Lollipop was Officially released quite a few months ago, what hasnt been released is Lollipop for the Samsung Galaxy Tab S Product Line.
So my question was, if we are to expect custom development from the current developers for the Tab S when Samsung releases its base rom for the Tab S, since this is a no-so-popular device.
sweetandsoursauce said:
is cm12 based on lolipop? if so how when lolipop hasnt been offically released?
Click to expand...
Click to collapse
Cm12 is based on lollipop/stock android. Why? Because someone ported/built a working build to make it work. Samsung takes ages to release lollipop.
---------- Post added at 02:59 AM ---------- Previous post was at 02:48 AM ----------
Satorikn said:
CM12 is based on Lollipop.
Lollipop was Officially released quite a few months ago, what hasnt been released is Lollipop for the Samsung Galaxy Tab S Product Line.
So my question was, if we are to expect custom development from the current developers for the Tab S when Samsung releases its base rom for the Tab S, since this is a no-so-popular device.
Click to expand...
Click to collapse
We will get custom rom development and maybe themes since samsung switched to png format.
Cm12 is based on lollipop/stock android. Why? Because someone ported/built a working build to make it work. Samsung takes ages to release lollipop.
Click to expand...
Click to collapse
See, this was something I was afraid of hearing because wouldn't there be a difference between ported/built working vs official samsung bult that is fully functional? Not saying the other cm12 isn't functional, my insecurity says theres ought to be something between developing a working carbon copy and the real version.
sweetandsoursauce said:
See, this was something I was afraid of hearing because wouldn't there be a difference between ported/built working vs official samsung bult that is fully functional? Not saying the other cm12 isn't functional, my insecurity says theres ought to be something between developing a working carbon copy and the real version.
Click to expand...
Click to collapse
What do you mean with the "real and carbon copy" versions?
Samsung implements a framework on top of android called Touchwiz for their devices, it's more than just a skin, and the personalization takes time. Samsung decides which devices to be updated first based on the sales of the device or if it's a new device as a magnet for sales.
CM(XX) is much closer to the The Stock Android Experience (AOSP), but since Samsung uses a closed code, and drivers, an implementation is never as perfect as an "Official" one. This is mainly due to the fact that CM implementations are more ports than direct implementations, but neither is a copy or the other, just two different approaches, and different outcomes.
I will still continue development of my SkyHigh kernels for LP TouchWiz based firmware. It's what I'll be using ..... unless I manage a miracle to scrounge the cash for the upcoming 8" Tab S2
Once firmware and LP kernel source is released, then I can start .
Hello.
I was wondering if there are any ROMs for the T113? I would like to have Lollipop on it.
Thanks,
Shane
my search came up emtpy handed... i hope there will be one soon... i dont like all the samsung overlay and i already have twrp...
I have a galaxy tab 3 8.0 and i would like to find a lollipop rom that is touchwiz style (to look like newer phones e.g. s5,s6). However i can't find anyting like it. I am new to all rooting and custom rom stuff. Would it be possible to flash a lollipop rom and then port lollipop version of touch wiz?
I am trying to make a custom rom Android 9.0 (Pie). Maybe in about two weeks. I'll let you know when it's finished. Uh... it's from 2016.
Hey guys, so Ive had a S4 (M919N MetroPCS variant) since it first came out. It originally had Jellybean (4.2.2) installed when I bought it. Long story short, I upgraded to AOSP KitKat 4.4.4 and then later upgraded to AOSP 6.0.1
But, I checked out my baseband on my phone and it says "M919NUVUAMF2". This indicates that I still have the Jellybean modem correct? And what are the consequences if I don't get the suited modem/bootloader for my device when upgrading unofficially. it hasn't affected my phone in any way and I've been going back and forth on ROMS from AOSP to TouchWiz varying from KitKat to Lollipop to Marshmallow. Is it essential for me to change my bootloader when flashing a new rom
There have been many cases of newer versions of Android being ported from a device that can run it. For example, Android 8 has been ported to the Galaxy S6 from the A8, and Android 6 has been ported to the Galaxy Note 3 from the Note 7. In both of these examples, the ROMs have been a port of the Samsung firmware with all the UI but modified to work on the phone.
However, on the Galaxy S5, the only port ROMs I've seen are Marshmallow, even S8-based TouchWiz ROMs are still based on Marshmallow. Marshmallow is still a relatively new version, but there will come a time where eventually support will die out just like KitKat and soon Lollipop.
The question I am asking is whether it is possible to port a Samsung firmware of a newer Android version to the Galaxy S5. If so, what steps would need to be taken? If not, why?