Years ago I rooted a phone I had to the latest Android, only to find that the hardware wasn't up to running a more complicated OS, even the Cyanogen version that was equivalent to the original Android version didn't exactly breath much life into the old dog.
Given how shockingly poor the experience on my T820 can be on the stock ROM, I find myself once again tempted to give a custom one a go, but was wondering if the newer ROMs place significant additional load on the hardware? Is it worth the effort? Does it make them responsive?
I don't use the tablet for anything heavy-duty; mainly what I want is responsive browsing, Skype and some basic apps...
imacleod said:
Years ago I rooted a phone I had to the latest Android, only to find that the hardware wasn't up to running a more complicated OS, even the Cyanogen version that was equivalent to the original Android version didn't exactly breath much life into the old dog.
Given how shockingly poor the experience on my T820 can be on the stock ROM, I find myself once again tempted to give a custom one a go, but was wondering if the newer ROMs place significant additional load on the hardware? Is it worth the effort? Does it make them responsive?
I don't use the tablet for anything heavy-duty; mainly what I want is responsive browsing, Skype and some basic apps...
Click to expand...
Click to collapse
@imacleod,
Based on the views and comments I see for custom ROMs for your tablet, this ROM:
[ROM] SM-T820 TWEAKED....................[rom] sm-t820 tweaked
SM-T820 TWEAKED 5.1 ***** PIE ***** 20JUN2020 T820_CTD5_TWEAKED_5.1_DB4_by_rorymc928.zip Based on latest stock CTD5 firmware Tweaked, stable, zip aligned. SU/D Forced encryption disabled Deknoxed Debloated (GPU driver updated to latest...
forum.xda-developers.com
appears to be the best choice for improving your tablet's performance. If you are serious about installing it, check out the most recent posts in the thread. You will find a very useful post that goes into great details about how to install the ROM properly.
I feel you regarding sluggish performance on a stock Samsung tablet. I had a Samsung tablet a long time ago and it felt like watching paint dry when I tried to simply play a video. Also, what is it with the HUGE bezel size on Samsung tablets ? I recently bought a Lenovo Tablet and it has a very thin bezel.
In any event, good luck with your tablet !!
Thanks. I was hoping for some feedback from people that had applied a ROM to the S3, whether they found it transformational - or perhaps not - and whether the best idea is to go for the latest and greatest, or stick at the lowest level that's got general support.
I'm not one who's installed a custom firmware, but I see you've not got much response. This device was very expensive at launch, so was a hard reach for many people. Fewer people means fewer developers.
The custom firmware available for this device is quite sparse. In addition, there seems to be troubles getting all of the hardware to work correctly. They're not placing any load on the device as its the same kernel version as stock.
That being said, I do believe the S3 is past its support period, so will not be getting new firmware from Samsung.
Reading the fora for the custom firmware show that the device can be more responsive than stock (as long as you don't need the hardware that isn't working).
Additionally, rooting and debloating the stock firmware has shown increased performance for those who have done it (including myself). I'd recommend this route prior to attempting a custom firmware unless your primary goal is to ditch samsung and google.
undrwater said:
I'm not one who's installed a custom firmware, but I see you've not got much response. This device was very expensive at launch, so was a hard reach for many people. Fewer people means fewer developers.
The custom firmware available for this device is quite sparse. In addition, there seems to be troubles getting all of the hardware to work correctly. They're not placing any load on the device as its the same kernel version as stock.
That being said, I do believe the S3 is past its support period, so will not be getting new firmware from Samsung.
Reading the fora for the custom firmware show that the device can be more responsive than stock (as long as you don't need the hardware that isn't working).
Additionally, rooting and debloating the stock firmware has shown increased performance for those who have done it (including myself). I'd recommend this route prior to attempting a custom firmware unless your primary goal is to ditch samsung and google.
Click to expand...
Click to collapse
Thanks for the reply. I did actually take the plunge through the week and installed rorymc928's rom. So far, I'd say that it's more usable than stock - e.g. it's not so slow that entering a PIN after a restart hits the screen lockout out before I'm done - but not overly stunning when browsing (perhaps my expectations are too high). It has made me a lot less inclined to reach for a hammer/put it on eBay, and it may be the best balance between what's available and losing functions/features. If I feel brave I may try a more advanced tinker at some later point in time...
If you want to get an idea what Samsung thought was important for this tablet, watch some HDR content from youtube. Gorgeous!
But... Not really useful. Android tablets are a teeny niche, but someone should be able to produce something for the market!
Related
Galaxy Ace Has Now Been Given Updates To 2.3.6 In European Countries And Other.
India Still Has 2.3.4 which Is ddq6
Let Me Tell You Stock Roms Are Best Ones -
1. They Have No Bugs
2. They Are Made For Your Phone (Not Ported From Another Phones)
3. Have All Samsung Apps Like All share,etc.
Nd Much More..
Some People Hate Touch Wiz But Let Me Tell You That It Is Very Easy To Use.
Even I Think The Status Bar Is Ugly (LOL)
Yeah They Are Slow As Compared To Custom Ones But Still Is Pretty Good.
They Even Score Less Quadrant Scores But Still Are Stable.
I Recommend You To Use Stock Rom Until You Have Custom Roms Which Are Stable.
More To Come.
Thanks for your recommendation. Although having flashed several different custom roms (which were made for this phone) can you explain which ones you have tried?
Just wondering as some of the ones I have tried are just as stable as stock. and the improvements far outweigh the samsung bloatware that is preinstalled. (which can be added to the roms if you so wish anyway!)
to answer your points:
1- Stock roms have lots of bugs. SOD, lockscreen lag, Memory leaks, GPS connection issues to name a few
2- lots of roms are specifically made for the ace and not ported.
3- most samsung apps are not that great - They can be added if you really need allshare samsung apps, win cash and some game demos that cost £5 to play more than once which unless you root you cannot remove!!
The ace has small enough storage without apps that most dont want or need!
Its a matter of individual preference. They are both good in their own way. There both advantages and disadvantages to either rom. Still, you are entitled to your own opinion and they are to theirs.
very true, however saying stock roms are bug free is inaccurate.
Agree with PJ147, I'm running stock 2.3.3 and it's got several minor bugs - nothing disastrous but easily enough limitations to make the inquisitive person in me consider the possibility of flashing a custom rom. I haven't, purely for technical reasons and because you have to accept that a customRom requires a certain investment in time and attention.
The fact is that a vast amount of money has gone into creating your average stock-rom, whereas custom roms are the result of someone's singular hard graft and investment in time. There is only so far that a persons effort can be made to stretch with no financial incentive and very limited support. We're talking about a handful of enthusiasts competing against some wild expectation that they will be creating a vastly superior product to an organisation that makes millions from playing the same game.
If there is going to be a relevant point to this thread it's to dissuade your average punter from flippantly attempting to 'improve' their phone and use the achievements of others to profess their own genius - only to flip out when they realise not everything is perfect and that somehow they didn't get 'good value' when they paid the square root of **** all for their brand new Operating System.
PJ147 said:
Thanks for your recommendation. Although having flashed several different custom roms (which were made for this phone) can you explain which ones you have tried?
Just wondering as some of the ones I have tried are just as stable as stock. and the improvements far outweigh the samsung bloatware that is preinstalled. (which can be added to the roms if you so wish anyway!)
to answer your points:
1- Stock roms have lots of bugs. SOD, lockscreen lag, Memory leaks, GPS connection issues to name a few
2- lots of roms are specifically made for the ace and not ported.
3- most samsung apps are not that great - They can be added if you really need allshare samsung apps, win cash and some game demos that cost £5 to play more than once which unless you root you cannot remove!!
The ace has small enough storage without apps that most dont want or need!
Click to expand...
Click to collapse
Stock ROM's are disgusting because they are just there for people who use the phone for calling, messaging and listening to music. For advanced users like us, the stock ROM is a great disadvantage. After I flashed a new ROM, my friends go "WOW!!!" and you realise that you have more people surrounding you advice. Also, XDA welcomes you with open hands. For stock ROM, only the second hand phone shop welcomes you. Its time for all Stock ROM uses with wider thinking to take a stand.
Its All About Your Preference..
It Totally Depends On Your Usage And Your Preference.
Yes There Are Some Minor Bugs In Roms Which Can Be Neglected Some Times.
I Dont Have Any Offence For Custom Rom Lover Even I Do Like Some...
Even Now I Am Using Custom Rom Which Is Rushab's Ics Stock Actually Its Based On Stock Rom...
It Basically Depends You Like Samsung Apps Or Not,Or Stock Rom...
Enjoy
I prefer stock...now i use stock, boring of those custom rom that have so many bug than stock (it has bug but not to much)
Custom rom is for people who love theming and benchmark hunter
regards,
•ƒγяύs ργяσ™•
With my old tablet the custom roms always meant a performance increase too, but:
I've tried pretty much well every single custom rom available for this tablet by now and i still havent managed to find one that actually increases the performance of the tablet. When im running the stock firmware i get about 7500-7600 on quadrant and my browser is really responsive and stuff. There's not been a single custon rom out there that has even performed better then 5600 on quadrant. Is it just me, or are the custom roms not hat good performance wise?
EDIT: By better performance i mean how snappy the tablet feels, using benchmarks as a secondary frame of reference.
Not sure if quadrant is doing a good job. I also am getting same results as you with 7xxx for stock and 5xxx for all CM based ones. Although the CM roms feel smoother here.
Sent from my SGP311 using XDA Premium HD app
I abstained the vote cause the question does not bear a black and white / yes or no answer anymore these days.
In my humble opinion, and I picked up the smartphone / PDA / mobile device modding bug back about when this site catered to the the original HTC XDA almost exclusively, and Steve Jobs was merely having wet dreams about his iPhone (*1)... nodded RIMs have gotten to a state where they are overvalued. Saying a custom ROM is always way ahead of stock is like saying "one device with a fixed featureless fits everyone perfectly".
Custom ROMs had their deserved heyday when the industry loaded up near every carrier distributed smartphone with scrappy bloatware that made you weep. Depending on the mobile OS at any given time it was nigh impossible to get rid of that stuff, unless you flashed the whole shebang. From there on the custom ROM scene kinda exploded along with the market distribution of smartphones and later on tablets, certainly owed to the introduction of Android over older generation closed source systems, which enabled much more in-depth possibilities of adding novel features, fixing stuff that was basically broken out of the box and integrating all of this nicely.
(For a frame of reference: I tossed my PalmPilot and Nokia phone when the HTC Wallaby (Telekom MDA or so)hit the shelves... Early adopter by nature and I thought combining cellphones and PDAs, bother which I used avidly was the most revolutionary idea since the combustion engine. This was generation Windows Pocket PC, basically a PDA with cellphone feature thrown in as an afterthought (the antenna actually doubles a stylus compartment). Phone integration was a PITA on good days. On bad, long work days it might just happen that your moody battery would jump from 35% to flat out dead within a mere six minute phone call. Yet, no biggie right? Well, it was, the devices had no non volatile storage. Dead battery means go home, pray your last phone backup is recent enough and restore the entire thing. I spent a lot of time fixing this device (windows style - shoehorning in binary OS components from newer PocketPC versions and prodding the registry on the phone (!)...) to a point where it was almost usable as PDA only device, supplementing telephonly with a Nokia.
A while later better devices came out, PocketPc was scrapped for Windows Mobile and in high hopes I got a HTC Charmer. This looked like a more solid platform and indeed proper custom ROMa emerged, adding real functionality and allowing to get rid of carrier branded crap, later even RIMs emerged with Windows Mobile version updates never intended for that phone, some even taking the recent cutting edge HTC front-end, the first incarnation of Sense (I think it was called vanilla). I figured the really bad conceptual problems were fixed and merrily went along. But, as god hates my guts, I drained the battery accidentally, only to find that the phone would still go dead, deaf, dumb and wiped despite a good three or four years of technological progress. I was so confident that I neglected backups with that model and basically lost the majority of my stuff again. The Nokia dumbphone was back in the game, the HTC left a dent in the wall that required plaster and a patch of new wallpaper.
TL;DR: The first gen smartphones (PDA with cell module afterthought were such flawed concepts, badly integrated, that keeping recent backups and maintaining it operational took quite an effort on user side, on that sort of negated the higher productivity of using one altogether. But bear with me now, I am still circling around the point or two I want t. Make.
Because a few months after I abandoned smartphones for good (or so I thought) Apple coughed up their iPhone prototype and a few months later pumped it to market. I was amazed (not because of the technological feat, they were more or less throwing R&D money bricks at existing tech and concepts, however they exactly figured out what went wrong in the early generations, fixed that stuff, added fingerdriven multi-touch in favor of stylus driven displays and, this is the real kicker, in a time and age when the cool cell to have was a Nokia 8 Series or a decent, very small flipphone or clamshell they managed to brainwash their customers into what PDA and smartphone adopters at that time already knew - it's totally worth to dump the train of ever smaller telephony only cells for a much larger, more fragile device because of all the freedom and power those things offer you.
I kept my guard and obviously went for Android devices once I got back on the horse. HTC Desire, a backup Wildfire, Desire HD, Sensation, One S and a few tablets along the way. Now, here is the kicker. The Desire ran much better with a custom. The Wildfire could only be updated to a recent Android version with a custom ROM due to HTCs sometimes appalling quick update discontinuation. The Desire HD ran a basically stock custom ROM! But with lots of lovely icon eyecandy, so I stuck with that too. The Sensation benchmarked equally (give or take 5%) but the ROM added novel features, properly implemented, which I decided to stick with. But frankly, it was because I could. I would not have recommended a newbie to Android flashing to take the plunge. My current HTC One S has a recovery downloader and is rooted cause some essential apps I can't live without need it. Full custom ROM switch. I see no point. Android has come a long way. If today I have bloatware I can go to App Manager and disable them. Icon gone, runtime resource hogging gone. Many features that were the selling points for a custom ROM a while back are now natively incorporated.
This is just how I feel about my Sony SGP311 now. It runs 4.2.2 rooted, no recovery yet. This is planned, maybe at some point a stable, close to stock custom kernel to allow some overclocking on a per app basis for XBMC. But other than that it just Danny works. The Sony skin put over stock Androi. Is not that bad, and more to the point it never gave me the impression of hogging the system. Turn off what is useless to you, Office suite, walkway, etc and be on your merry way. It just comes down to what you do with the device, but as a custom ROM junkie who has just gotten off the habit, for me it makes no sense anymore.
Now, if you made it all the way here, I ran two benchmarks on my 4.2.2 root but stock. Maybe they aid you in your decision.
EDIT: the attachments are garbage. Here are proper links:
http://i.imgur.com/vMFEX1p.png
http://i.imgur.com/IEPVvMS.png
http://i.imgur.com/mB5MKSH.png
Also, none of the above is supposed to rain on the developers parade or something. I admire your skills and dedication over all those years, and there isn't a single custom ROM that went onto my devices withour a PayPal "crate of beer" donation ever. However, the fiddling, time spent reading up on custom ROM choice, issues and unlocking process etc is just not in relation for me anymore. Those thoughts are yours to reject, spindle, mutilate, adopt, oppose or plainly ignore... Just speaking for myself here.
Thanks for this! I was also trying to decide if I should be flashing a custom rom on my XTZ. I am itching to flash but couldn't come up with any strong reason to do so, probably for battery life and stock look?
Will be interesting to hear from another person who is a strong believer of flashing custom rom on XTZ.
Sent from my GT-N7105 using Tapatalk
i got slightly better score using a custom rom. Plus i get themes, expanded desktop and pie control which is a must for this tablet. I hope more xda developers develop for this tablet. Will reward with donations
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
4.3 too bugy for me
im using 4.2.2 cm rom FXP242-cm-10.1-20131021-UNOFFICIAL-pollux_windy.zip
i already sent team a donation hope to keep em motivated
Spartoi said:
By "better performance" do mean higher benchmark scores? Because any of the 4.3 ROMs I've tried are generally smoother than Sony's 4.2.2.
Click to expand...
Click to collapse
Sorry, the post was incomplete. Changed it.
r1ntse said:
Sorry, the post was incomplete. Changed it.
Click to expand...
Click to collapse
I prefer 4.2 ATM. I get close to 30 Mbps download speed on this ROM where on 4.3 roms only 2mbps download? Also video cam recording, screen is squashed on 4.3. Other than that they run great but I personally cant feel a performqnce boost from 4.3 to 4.2. I also installed crossbreader and Supercharger V6 script which addresses screen redraw lags, so if there is a slower issue with 4.2 i would have addressed it with these two mods and may not be able to tell.
It seems that 9 times out of 10 I read about a problem with an android, it's about an OS update breaking things:
"Can't root the latest stock ROM update nohow"
"Latest mfc ROM / CM / etc. incorporated XXX change and now I can't get Viper4Android / AutomateIt / whatever working"
"Latest 5.x ROM now requires root for the same app / action that didn't require root before"
"SELinux / Knox / etc. can't be disabled nohow on the latest ROM"
Personally I got everything working just the way I want on the rooted form of the stock 4.4.2 ROM that came with my LG G Pro 2
--and I'd strangle anyone who hits the update button on it (except I think rooting disabled the OTA update thing)
----and I have half a mind to buy another identical phone for backup, because this phone still seems to be able to go toe to toe with the latest flagships (1080p screen is plenty dense enough for my eyes, 3GB/32GB still seems to be the maximum amount of memory any phone packs, I could care less about new CPUs that eat batteries at the same rate that they increase performance) and more importantly, I'm very pessimistic about the prospects of being able to get Viper4Android, Xposed framework, VolumeSteps+, PBMC Mappings and AutomateIt all working on whatever ROM that comes with whatever next phone I would have to buy when this one breaks.
I read the adventures of those who upgrade their ROM nightly and run into a different compatibility problem every night the way I listen to the ravings of a lunatic walking out of a spectacular train wreck
And I have a friend whom I bought a Sony Z3 for who had gone through trying a dozen different ROMs in a few weeks. It's a brick now
You can argue that the older versions of Android would have more stability and mods, but most end users are not as tech savvy and are less demanding as yourself. All they need is a phone that functions properly for them. Usually developers release updates to fix stuff with the current firmware, so most end users would be tempted to do the update when it comes out. They would be less concerned with things like V4A and custom mods which require more knowledge. As for LG G Pro 2, I wouldn't say it's able to go head to head with other flagship phones, unless you used a custom ROM with it. Specifications wise, it will still lose out to most phones, because no matter how much you attempt to tweak the software, it is still limited by the hardware. Furthermore, when you compare the developer database to Samsung and Sony, LG has a much smaller database as compared to both manufacturers. You can find plenty of custom ROMs for Samsung and Sony phones, but not so for LG phones. Just my two cents.
Hi guys, I'm a jailbroken iPhone 6S+ user. I'm currently a slave to Apple's ecosystem (iPad, Apple TV, Watch but not a Mac) I apologize for the wall of text below, but I know you guys are always glad to give a helping hand.
I've been using iOS since the iPod Touch 2G, taking a break for a couple months only in the Galaxy S3 days, which was my first and only android experience. Many iOS users are in the same boat as me.
Android was a whole different thing back then. Nowadays, when I see the curved, bright and saturated screen of an S7 and how well it pairs with the material design, I feel like I'd love to give that a spin. My problem is that I've been fed constant complaints on behalf of android users, using different handsets and at different times. Here are my main concerns:
I've always heard that, after a "honeymoon" period, almost without fail, all android handsets start to experience stuttering, freezing, rebooting, framerate drops, etc. (maybe one of those at a time, sometimes all of those are common occurrences) does this happen? This is the most important one for me, because if there's something that none of my iPhones ever suffered from, was reduced performance.
Software glitches which are mostly hardware-specific. I've visited the 6P subreddit, only to find a plethora of people complaining about the camera app freezing or crashing, some focus issue I believe as well, or maybe just reduced performance in other parts of the OS (which is the purest form of android). I've also heard that Samsung's bloatware, although only a fraction of what it was back on the S3 days, still causes the phone to feel sluggish at times. Haven't heard about Huawei or HTC bloatware, but I have watched reviews which mentioned some lag here and there.
Software updates. The whole ordeal of having to choose a phone thinking about whether it will get updates in the future or not is pretty sad. I know that Nexus phones are guaranteed to get updates for two years I believe, but as I stated before, visiting the 6P subreddit, I've seen people complain about Google updating the OS but leaving bugs unresolved for several iterations of it. How do you handle this when choosing a phone?
Customization. If there's one area that I've been always convinced Android was leaps and bounds ahead of iOS was this. However, as a jailbroken iOS user, I find that I get most of what you guys can get out the box, but in a prettier package. As in, jb tweaks are very tightly integrated and always match the OS look and feel. In Android, you work with apps or, after rooting, with "modules" I think they're called. How do these differ from JB tweaks (stability-wise as well)? How different is the process of waiting for root vs waiting for a JB? Is rooting as necessary as jailbreaking?
Lastly:
Apps. I am aware of the differences in general app quality when comparing the App Store and the Play Store. Big names such as FB, Twitter, Instagram, etc are mostly the same. But when you start digging a little bit deeper, you find that there's a big difference in not only availability, but also variety and polish. At least, that's how my experience was and what I tend to hear from Android users. How's the Play Store these days? Has this changed a bit?
I apologize once again for the wall of text. If you could answer each point with one or two lines I'd be immensely grateful. Honestly, since these points are big question marks in my head right now, I wouldn't even know what handset to look into, because I don't want to be unpleasantly surprised later on. Android screens though... Damn. Most of them are sexy.
Anyway, thank you very much for your time. Any help is deeply appreciated.
Stuttering/Freezing. You might find this on some low-end devices but the "flagship" devices that I've used haven't suffered from this. This would generally be caused by lower end hardware (lower clocked CPU and lower RAM).
Software glitches. I own the 6P and have never had the camera crash or freeze, never had any software issues with this phone actually. Samsung phones are pretty well known to suffer from being sluggy, this is due to their Touchwiz UI which hogs quite a bit of RAM. The HTC devices I've owned haven't had this issue. Can't speak for Huawei's own UI. The Huawei 6P uses pure Android, I don't notice any real lag issues on this phone.
Updates. If you want guaranteed software updates your best bet is a Nexus. I've noticed no major bugs on the 6P apart from a 4G bug that was specific to an Australian carrier but that was patched pretty quickly. There have been things in Android that people label as bugs that haven't been patched immediately though. Even if you choose a device that may not be updated officially you will very often be able to update via a custom ROM, custom ROMs are often developed for devices long after official support has stopped.
Customization. Android is definitely far ahead in terms of customisation. Most people find customisation via a custom ROM (a customised version of the OS, sometimes based on the stock OS, sometimes based on AOSP (Android Open Source Project or "pure Android"), sometimes based on something like CyanogenMod). A ROM will almost always have extra features and tweaks, these features are usually very well implemented and tie in very nicely with the OS. When speaking about modules you'd be referring to Xposed Modules which are used with the Xposed Framework. Xposed basically opens up a lot of customisation ability, it requires root, it can be used on a stock ROM with root or with a custom ROM. There are a plethora of modules available, too many to even begin to list, the best way to see what they can achieve is to look in our Xposed Modules section. As for root in general, you don't generally need to wait for root like you would with jailbreaking. Having root access is also far more flexible than jailbreaking, you can pretty much do anything with your phone, you have full access to the otherwise blocked system partition. Root methods will vary from device to device but you'll usually need an unlocked bootloader. The easiest devices to root and modify are the Nexus devices, they're designed to be tinkered with, development phones first and foremost.
Apps. In the early days of Android, and even up until a few years ago, the Play Store really lacked in terms of availability and quality. The last few years have seen a dramatic increase in both areas though, there's a wide variety available and the quality has become top notch.
In summing up, it looks like the worries you have are misconceptions commonly held by Apple users.
As a former board level apple technician who used the first ever apple products in kindergarten nearly 30 years ago, I must say I can't even use an iPhone. With all respect, most of your thoughts are not accurate.
Sent from my Nexus 6P using XDA-Developers mobile app
I'd like to get to as close to vanilla as possible. Not a fan of Samsung's ui or bloat. I'm coming from the tab s1 which had some pretty good roms. There are none for this device and it's almost 6 months old. I would make one myself but lack the necessary skills
Most of the newer top end Samsung Tablets get very little developer support since they cost so much. Happens with every new tablet having people asking where the developer support is for it. Samsung newer UI much nicer and any vanilla roms would take away most of the functionality that makes the tablets great. Apparently the S5e has some dev support.
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Markeee said:
Problem is Samsung seems to be super slow with there updates for the S7.
I've owned the S7+ SM-T970 for like just a week and I'm already feeling impatient waiting still running off the Oct. update while I keep hearing about about UI 3.0 update hitting there flagship phones.
Do you think at some point down the road when or before OEM support ends we can look forward to some working roms or Treble GSI options ?
Click to expand...
Click to collapse
Not everyone gets the update at the same time (don't know how they handle when and who should receive the update). I only got a November update a few days ago (though some claimed to have already gotten it) and it offered few improvements. The tablet still feels the same as usual.
As one must choose between custom ROMs and Knox (especially warranty), I'm currently at a loss myself, and for the time being I haven't heard of anyone trying (or succeeded in) booting a GSI on S7/S7+ probably because of this, although it's theoretically possible (again thanks to Treble). At least we now have TWRP... it might be better if one day custom kernels become available.
So far this is the only tablet I know that can offer 120Hz display. My current phone (Razer Phone 2 which is also 120Hz-capable) still doesn't have a specialized ROM but I can already run GSIs on it with adequate performance. For new devices, going for GSI might be easier, but performance-wise it still has a way to go compared to specialized ROMs.
Think it has to do with the fact that snapdragon is locked on samsung