Is there no official cm13? 12.1 stopped months ago.
It only depends on if someone- anyone- is willing to be the maintainer for a device branch for it to be an "official" cm build. As long as they follow cm's policies and whatnot. I don't think many hobbyist developers have the tablet. What makes it more confusing is the "Tab S" really encompasses at least 5 variants (the 8.5" and 10.5" each offered in Wi-Fi only, LTE and US vs international versions) ... if not a few more variations. Edit: I just checked on Sammobile.com and there are 13 devices called Tab S. That's why Samsung is ridiculuous with how many models they spit out each year. Sometimes like 35+ different phone models in one year. It's silly but I digress.
And then you have to have the certain proprietary bits and pieces that may be required for the tablet to retain all of its features (bluetooth, Wi-Fi, GPS, sensors, modem, NFC, fingerprint reader, ANT radio, CPU, GPU, etc.) If you don't have all of those bits all you end up with is an official piece of s.
I don't know if we have the right proprietary bits and pieces for Android M to warrant an official CM13. Since Android M just dropped for the Galaxy Tab S series as we speak it could be a while off before its code is released... and then you've got to hope someone is interested in maintaining a device they may or may not personally own.
Related
I upgraded from the Nexus S, after receiving the ICS 4.0.3 update on it, to the Galaxy Nexus. ICS on my Nexus S was running pretty much flawless. I had none of the issues some other users had.
Anyway, seeing how awesome ICS was I decided Galaxy Nexus was a must for me. Thus the problems began. While I'm not experiencing so many issues as other users do I'm sick of random reboots, freezes. And I'm on 4.0.2 that feels slower then it should be. Seriously instead of an upgrade I FEEL LIKE I BOUGHT A VERY EXPENSIVE DOWNGRADE.
I thought these issues will be fixed soon and Google will release the 4.0.5 update but it seems there is no word of that.
I was underwhelmed with stock performance, these phones beg for a ROM upgrade. CM is moving along much faster now with lots of the typical CM settings being added for ICS. Stable, smooth and fast. Nightlies are back. If you require a ton of customizations there are a few other good roms available that might sacrifice some of the stability and smoothness.
Point being, you'll like this phone
Another one of these threads?
You realize that the CM team would fall into the same problems that the Android team currently does. At last count, there have been just over 1,000,000 unique Cyanogenmod installs... There are 850,000 Android handsets activated every day, from different manufacturers, carriers, regions, etc..
Believe it or not, it gets very hard to support devices when that many are sold. By comparison it is easy to support 1,000,000 installs. A small fraction of which are actually updating nightly. As far as custom ROMs go, CM covers a large # of devices and does it well, but to assume because they can handle that they could handle running an entire phone manufacturer is laughable.
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
This is old news… Samsung hired Steve Kondik, the CyanogenMod founder...
zeekiz said:
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
Click to expand...
Click to collapse
this should be posted as sticky as information to all
zeekiz said:
OP, massive leak on the next ICS update for the Galaxy Nexus.
http://www.youtube.com/watch?v=DksSPZTZES0
Click to expand...
Click to collapse
now that was funny!
The problem is this:
Google has no balls. These companies are making bank on phones without any or very low software costs.
What is needed is a better end user experience and to get that they have to get fragmentation under control. It doesn't need to go away it just can't be the retardation that currently is Android.
They need to do the following:
User should be able to choose between AOSP and custom skins for every device. This ends the lack of updates and compatibility issues that crop up with sense, blur etc.
Custom skins and apps should all be uninstallable. No bloat if the user doesn't want it.
They need to get hardware variance under control to help developers with compatibility. Its getting crazy trying to support all these different devices. We need far fewer hardware revisions and a tad more uniform releases. No reason to have 20 different handsets every year complicating everything from drivers, app compatibility, updates etc.
Aridon said:
They need to get hardware variance under control to help developers with compatibility. Its getting crazy trying to support all these different devices. We need far fewer hardware revisions and a tad more uniform releases. No reason to have 20 different handsets every year complicating everything from drivers, app compatibility, updates etc.
Click to expand...
Click to collapse
Clipped, but all of what you said makes sense, to me, an advanced n00b who may not have the technical insight to understand all the implications.
How many devices has ICS officially been rolled out for? 2, maybe 3 (sticking to phones here). Code has been out for ~5 months (?). Android is great, but its popularity has led to a plethora of devices with dramatically differing hardware and it takes a lot of work to make it work. To keep device manufacturers happy I'm sure this means sacrifices have to be made at the Google level in order for ICS to work on whichever strange collection of hardware components go into Phone X.
I wouldn't like to see hardware dictated across the board, variation is great, but it would be better if there were a very small collection of basic ingredients going into the cornucopia of phones, each with their own HW specs, often questionable.
I'm happy I used plethora and cornucopia in the same post.
Seriously I accidently (and stupidly) checked the G920 forums original android dev section and the blowup of AOSP based ROMs is just getting cruel as I sit on a crippled TW base :/.
Same SoC, yet no love
I feel your pain bro.
Same here :/ and I just got the phone , going to wait till next year for the s9/s9 plus
xdamember143 said:
Same here :/ and I just got the phone , going to wait till next year for the s9/s9 plus
Click to expand...
Click to collapse
OUCH I landed mine this Summer sometime and an Ex GF actually FRP locked it, so I was pretty happy just to break that lock, then found CM13 floating around here right after, & probably just assumed we were going full throttle like all other flagships from Sammy.
Even Android File Hosts developer counts.
Note 5 130ish devs reported? Like 7 pages of names.
s6 Edge+ devs reported at somewhere around 30 total. Is this even seriously happening?
They are ALL THE SAME DEVICE Why we don't just have an *Exynos7420 device area is beyond me, we would go alot further merging all the TWRP commits into a universal for whole SoC lineup then carrier Variants to simplify it all again, instead with the way it is I have no clue what is possible and a good idea or totally stupid and a bootloop in the making. >.<
Sent from my Samsung SM-G928F using XDA Labs
I feel like part of the problem may be users that don't roll up their sleeves and learn to contribute to the community. If there's a project you want to see, and it doesn't exist, start it. It looks like you'd have lots of greatful people.
hexavoodoomal said:
I feel like part of the problem may be users that don't roll up their sleeves and learn to contribute to the community. If there's a project you want to see, and it doesn't exist, start it. It looks like you'd have lots of greatful people.
Click to expand...
Click to collapse
How? There are plenty of projects on the same SoC with no desire to port to the 4 or 5 users (Us) that care
Personally I just sold this phone for $80 today over this, and the fact for 6mths its been nothing but a headache, 6mths of learning googling and tinkering, + probably 2tb in total internet data for this. I still don't quite understand the finer details of this device, and to be totally honest, I wouldn't want to, it all seems to be about rerouting and fixing up stuff to work around AOSP code.
If you really thought about getting an Exynos or a Samsung device in general just for tinkering and community involvement, it was your mistake from the start. even if the S6/Note 5 have more support than the edge plus (which mainly because of the sales/price difference between the regular edge and the plus) they are nothing but 10% of the support you will find for devices like the OnePlus, Xiaomi, Nexuses or even Crap Sony and mainly because these other manufacturers are more developer friendly and most of the time their code is very similar to AOSP.
Well if s6 , s6 edge and s6 edge+ are basically the same device, would s6 or s6 edge rom work on edge+?
justanpotato said:
Well if s6 , s6 edge and s6 edge+ are basically the same device, would s6 or s6 edge rom work on edge+?
Click to expand...
Click to collapse
It would. With (depends on which ROM) more or less modifications. MIUI in original development section is an S6 port.
Note 5 ROMs seems to be much easier to port (most likely just use an S6e+ kernel) because it's even more similar to our device.
Gesendet von meinem SM-G928C mit Tapatalk
Gh3ttoKiLL4 said:
It would. With (depends on which ROM) more or less modifications. MIUI in original development section is an S6 port.
Note 5 ROMs seems to be much easier to port (most likely just use an S6e+ kernel) because it's even more similar to our device.
Gesendet von meinem SM-G928C mit Tapatalk
Click to expand...
Click to collapse
Yes this is all true but the differences between the s6, s6 edge, s6e+, & also the note5 respectively share extremely similar traits with the other device that runs all kinds of fun stuff (Meizu Pro 5) and the only major difference I could grasp between them is the ODIN mode/Fastboot swaps + some minor stuff (hardware buttons, higher res camera, scanner on back of phone)
But they were still ALL the same manufacturing & SoC line (Sony Camera, Exynos7420) but the pro5 just magically somehow can be released with an Ubuntu Touch edition + CyanogenMod like cake??? I dont buy that man..... If it were such a hassle to do this phones hardware for devs, they wouldn't be just flexing it in the background like that......
cryptonx said:
If you really thought about getting an Exynos or a Samsung device in general just for tinkering and community involvement, it was your mistake from the start. even if the S6/Note 5 have more support than the edge plus (which mainly because of the sales/price difference between the regular edge and the plus) they are nothing but 10% of the support you will find for devices like the OnePlus, Xiaomi, Nexuses or even Crap Sony and mainly because these other manufacturers are more developer friendly and most of the time their code is very similar to AOSP.
Click to expand...
Click to collapse
Did you not see the comments or?
I got the device for free, I had no clue what was inside of it, also didn't care about the SoC since I had prior knowledge that Samsung would be a simple process with Odin & a CF package, what I hadn't counted on was TouchWiz still being the most bloated & unstable manufacturers slop on the market, also hadn't counted on it being the hardest overall to develop for, since most of the developers lost their XDA accounts eve attempting to bring CM13 up for the device, & don't get me wrong I have had plenty of HTC/Motorola devices & I sold my Nexus 7 not long ago, I'm familiar with AOSP (the thing these Samsung devs had to of started from) and just can't understand why they made is so much of a runaround process.
The A50 differs from the other A-series devices in terms of having an Exynos 9610 which has seen practically zero development and poor GSI compatibility. However, finally we have an Android One device with practically the same chipset.
The Motorola Action One comes with the Exynos 9609 which is the same as 9610 apart from having a 100 MHz lower clock speed. In the past, we had instances of Android One firmware being ported to similar devices, so it is possible for a capable developer to be able to create a functional port.
Of course, bugs are inevitable, especially in the areas of camera and wireless connectivity but hopefully with the right combination of blobs it might be possible to have a daily driver. Again, at this point there is nothing more to go on rather than hope, but it is great to have a sister device running stock Android.
So what do you think about future development prospects? Is there any developer with an A50 willing to have a go once the firmware for the One Action becomes available?
Nice let's Hope ?
Motorola one vision is already out since May, and it's exynos 9609 as well, running Android one.
You can check one vision forum if anyone is interested in system/vendor dump. I got it uploaded a while back.
I miss the old days of Android, specifically the galaxy S3 days. A major update to Android would be released and there would be countless roms that work with no issue on the device. I haven't had that experience in a long time. I thought that treble would bring that back (and even make it better), but that's certainly not the case. With every device needing a modified vendor image, treble doesn't circumvent the issue that when developers either don't exist for a device or leave a device, that device will be left in the dust at some point. The devices I used with treble either a. will have issues with sensors, vibrations, etc. or b. just don't boot. It seem like treble will work fine up the point where a manufacturer stops updating the device, so that the official drivers, etc. are available for that version treble. But as soon as the developer stops updating, and you want to use the next iteration of Android though treble, it won't work unless some dev puts in in work and makes it compatible. Otherwise, you're just left with treble roms at the same Android version where the manufacturer stopped updating at. Sure, you'll get security updates, but that is not good enough for me. I want a device to give me android updates for years.
Basically, I'm just venting about how disappointing this all is. Is there anything on the horizon to make any of this better?
My Samsung A3 is almost 5 years old and I still use it as my daily driver, I'm thinking about flashing Lineage OS to the device and I'm wondering what anybody's experiences were with using the OS as their daily driver. I will use it mostly for calling, texting and journaling. I also listen to music quite frequently. I don't intend on installing any of the popular apps.
I've been using LineageOS and Cyanogenmod forever. It works wonderfully and I do anything I can with the stock OS and more.
I run LineageOS on my Samsung Galaxy S5 Duos and use it as my daily driver. It's running Lineage 17.1 which is Android 10 (18.1/11 has just become available too) - not bad for a phone launched in February 2014, which is now over 7 years ago!
If it wasn't for this phone only having 2GB of RAM onboard a lay person probably wouldn't notice much difference compared to a more modern mid range phone.
With LineageOS there's a lot less bloat so Storage, RAM, CPU Performance, and Battery Life are all improved.
I went the whole way and the phone is rooted as well and to be honest I wouldn't look back. I bought this phone all those years ago specifically to do this and it's really paid off.
But remember the LineageOS ROMs are specific for each phone. So the first thing to do is to find the support thread here for your particular model and read through it for points relative to your specific device.
I really like the freedom that LineageOS and Root gives me to do whatever I like with my phone, all while getting monthly updates and having a support thread of like minded users (well actually many of them are way more power users than me). Daily driver performance is excellent.
When I buy a new phone it will again be a model that can run LineageOS and be rooted. And I'll do this immediately after purchasing the device. These days that also makes some chinese model phones a good option as they often have a good hardware to price value ratio, but terrible support and updates. So it's possible to use this good value hardware but combined with an excellent LineageOS ROM, support, and updates instead.
Hope that helps
eu7tFeTyT7vfPy said:
My Samsung A3 is almost 5 years old and I still use it as my daily driver, I'm thinking about flashing Lineage OS to the device and I'm wondering what anybody's experiences were with using the OS as their daily driver. I will use it mostly for calling, texting and journaling. I also listen to music quite frequently. I don't intend on installing any of the popular apps.
Click to expand...
Click to collapse
It's OK if you have A3 2016. But what's your motivation? Playing around? Avoiding Google spying? Impressing friends with new android version?
kurtn said:
It's OK if you have A3 2016. But what's your motivation? Playing around? Avoiding Google spying? Impressing friends with new android version?
Click to expand...
Click to collapse
Avoiding google spying No friends to impress lol!
jmh2002 said:
I run LineageOS on my Samsung Galaxy S5 Duos and use it as my daily driver. It's running Lineage 17.1 which is Android 10 (18.1/11 has just become available too) - not bad for a phone launched in February 2014, which is now over 7 years ago!
If it wasn't for this phone only having 2GB of RAM onboard a lay person probably wouldn't notice much difference compared to a more modern mid range phone.
With LineageOS there's a lot less bloat so Storage, RAM, CPU Performance, and Battery Life are all improved.
I went the whole way and the phone is rooted as well and to be honest I wouldn't look back. I bought this phone all those years ago specifically to do this and it's really paid off.
But remember the LineageOS ROMs are specific for each phone. So the first thing to do is to find the support thread here for your particular model and read through it for points relative to your specific device.
I really like the freedom that LineageOS and Root gives me to do whatever I like with my phone, all while getting monthly updates and having a support thread of like minded users (well actually many of them are way more power users than me). Daily driver performance is excellent.
When I buy a new phone it will again be a model that can run LineageOS and be rooted. And I'll do this immediately after purchasing the device. These days that also makes some chinese model phones a good option as they often have a good hardware to price value ratio, but terrible support and updates. So it's possible to use this good value hardware but combined with an excellent LineageOS ROM, support, and updates instead.
Hope that helps
Click to expand...
Click to collapse
Thank you for the detailed response, and for reminding me to check the support thread for my model! I also noticed that the less popular Chinese model phones had better price to hardware ratios and the only thing stopping me was exactly what you mentioned, though I'm doing this to an A3 I'll probably consider buying something of the sort in the future for when I want an upgrade. From your response, Lineage is looking hopeful!