Impatient Users Cause Most Problems with Lollipop? - G 2014 Q&A, Help & Troubleshooting

After trolling the net for users experiences with Lollipop it would seem that most problems are caused by impatient phone owners side loading versions of 5.0.x that are not intended for their particular version of phone. Many manufacturers use different components during the build sequence of a model, so there is a certain amount of testing to ensure that any release of an OS is properly tested on the range of components built into the model, hence the different system versions released in different areas and at different times. I eventually got an OTA update for my XT1086 Dual sim and it works superbly. No problems, No memory leak, great multitasking, very fast, good battery performance, No problems with my sims or wifi
So are you one of the impatient ones with disasters? Or were you patient and well rewarded?
Or non of the above?

Related

Could 4.3 code for the radio be causing physical hardware failure?

I just replied to a question in the development thread where an N4 user, running stock 4.3 suddenly lost connectivity to his 5ghz router band, nothing changed on his phone but suddenly he loses connectivity to 5ghz band?
Of course this is a well known issue, impacting hundreds of users globally since the 4.3 update, and it got me thinking that just maybe the actual code written for the Wi-Fi radio drivers in 4.3 was overly aggressive in terms of the capabilities of the radio hardware in the N4 and actually physically damaged the hardware? Code can break hardware, we all know of devices that have been permanently bricked and became coasters - all because of bad code or a flash that went wrong.
What if the radio code written in 4.3 was to maximize signal strength to remedy the complaints of poor/slow Wi-Fi on many 4.2 devices, but was too aggressive for the radio hardware in our N4's causing it to basically overload and physically die? I've read of people who had no issues with their 5ghz channel (like me) then after updating to 4.3 completely lost 5ghz connectivity, and even after downgrading to factory 4.2 stock firmware STILL had no 5ghz connectivity. In my case after downgrading to 4.2 i still had no connectivity to both of my dual band Netgear routers, nor any other 5ghz band router I tried, complete 5ghz failure - downgrading to the same 4.2 firmware that had worked flawlessly before updating to 4.3! If it was just software then downgrading to the previous 4.2 firmware should have instantly resolved the 5ghz connectivity, right? If it worked without issue before then it should work without issue again. Except for many it simply remained broken, so it stands to reason that something else changed - i.e. the physical hardware was damaged.
Maybe that's why Google quietly shot out 4 different versions of 4.3 in an attempt to hide the fact that the radio code was too aggressive for some phones hardware? They perhaps toned down the radio code's aggressive push of the hardware, which might explain why some people don't have the issue, but it was already too late for phones with lower hardware tolerances and the damage was permanent.
I'm getting a replacement device from Google tomorrow and if the 5ghz band works out of the box on the stock 4.3 firmware, I'm highly likely to immediately downgrade to 4.2 stock as I have a strong feeling that its just a matterof time before i once again lose 5ghz connectivity just like the person i mentioned at the beginning of this post.
I suspect Kit Kat to use the same drivers as 4.3 so I'm staying clear of new builds until V5.0.
Of course if people regain 5ghz connectivity on Kit Kat I will stand corrected, but I'm willing to bet they don't - if functionality that worked fine on 4.2 can't be recovered by downgrading from 4.3, it's almost certainly damaged radio hardware, and no new versions can fix that.
Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app
THEBANDIT420 said:
Scary but probably unlikely I'm sure google knows the hardware limits of the devices and tests before it releases it. I mean google is generally try to play it safe then sorry like how high they set the CPU voltages.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Google releases their ROM's for numerous phone manufacturers, remember that ICS was the first android version that was cross compatible across all phones and tablets, the idea that it was easy to mass implement.
Consider the price of the N4 - $250 for 16gb model, about 40% of the price of a Samsung GS4! And the old saying that you get what you pay for. Junky screen compared to the SGS4 and other top price phones. Crap audio hardware compared to the fantastic sound chips Samsung uses. And most likely many other corners were cut to be able to release a 'flagship' device for less than half the price of the next major Android competitor (SGS4). It's straight forward economics, you get what you pay for. And I don't think Google realized that the tolerance levels of the N4's radio hardware were as low as I think they actually are, which is why they have been unable to resolve the issue in 4 quickly released 4.3 builds! I think they knew that the first release boosted signal strength in most other phones but didn't expect it to actually exceed the tolerances of lower end components that had to be used in the N4 which packs in all the top features of a high end phone at half the price!
I would never buy an LG flat screen TV, I'd always buy the Samsung simply because it's better quality in every way. I'm not sure why my brain didn't tell me this when I bought the N4. It was too good to be true at less than $250 for the latest Android phone? I think it was too good to be true!!
Let's watch Kit Kat roll out and watch these forums fill with p!seed people who still don't have reliable connectivity, and never will because their phone is physically broken.
Again, the acid test is to downgrade to say 4.1.2 and see if your 5ghz band works and your 2.4ghz speed flies, because it did when the phone was released back in December 2012 when it ran 4.1.1 or 4.1.2. I'm betting it won't work like it did and you still can't connect with the speed and reliability you once had. And if you can't get 5ghz connectivity on 4.3 you won't ever get it again because the hardware is cooked.
Globespy said:
Too long to quote.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Globespy said:
to long to quote
Click to expand...
Click to collapse
You don't buy lg TVs yet you bought a phone made by lg......
You bought the n4 but yet to YOU the s4 is WAY superior to it.....
Then I guess you know what you need to do then.....
Smh
Sent from my Nexus 4 using XDA Premium 4 mobile app
Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
Sent from my Nexus 4 using xda app-developers app
---------- Post added at 02:53 PM ---------- Previous post was at 02:49 PM ----------
PJcastaldo said:
Highly doubtful that the radio firmware is causing hardware failure. As for your example usually a phone bricks because something went wrong with the flash or an incorrect file was flashed and the file system is no longer accessible hence a black screen with no boot... or worse.. the the hardware its self isn't actually damaged.
And I think and still think the N4 is a great device. Its fast looks nice. I personally think the screen looks nice.. and takes great pictures. So... maybe you should go buy a Samsung...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Sent from my Nexus 4 using xda app-developers app
Globespy said:
[A lot of text]
Click to expand...
Click to collapse
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be the Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.
Zenety said:
Click to expand...
Click to collapse
So childish. I bought the N4 for thethe same reason most others did - it was sold as a flagship product for what was literally a 'steal'. I haven't had this many issues with a phone since I ditched windows and moved to Android when eclair came out. But I suppose this makes me a Mac fanboy now? Lol.
I actually have never owned a Mac - PC guy.
Johmama said:
A few things.
1. It seems you fail to grasp the purpose of the Nexus program.
2. I doubt Google would release software that damaged the hardware on the latest Nexus phone. That's kind of the point of the Nexus line; development. Not only for independent developers, but also internal Google ones. If this scenario were true, it definitely wouldn't be thethe Nexus phone that got broken, it would be a different one.
3. Assuming that the Nexus 4 is of lower quality than the GS4 since it is half the price, citing "simple economics" as a reason is just plain ignorant. There is a lot at play here, the two devices aren't in the same situation. Samsung is trying to make money off of the hardware so they mark it up. Google is just trying to showcase Android and offer an affordable top-end phone, so they don't mark up the price. Plus, they make their money off of their services.
4. Head over to this thread and start flashing different radios. I'll bet you 3,000 Internet Dollars that one of those radios fixes your WiFi issues.
Click to expand...
Click to collapse
This thread was started because of an idea, based on a problem that I've struggled with as well as friends who ate all nexus guys.
It was not to bash LG or Google - I've been around on this forum a LONG time and have bought many nexus phones and tablets, and have enjoyed them!
The last Gnex was not priced at the level the N4 released at, yet at that time Android phones had been selling as much as iPhone, I believe around that time worldwide sales surpassed them for the first time. I understand that Google has a different business model focused on selling software (actually their main business is advertising) and want to market their products at a lower price point than hardware manufacturers like HTC, Samsung etc. But when you do this you still cut corners. I'm not alone here in saying that the screen and sound hardware used in the sgs4 is just better. There's no argument. I could have bought one but I'm a nexus guy and have been for a while. I bought a sgs4 for my Gf, she loves that TW nonsense. But maybe just maybe I have a point about hardware failure given that the majority can't resolve it even going back to software that worked before!
Anyway, your recommendation of flashing different kernels may work for a few, but from looking at the hundreds of posts on numerous different sites (most notably Google's N4 support forum), it's clear that the majority are still having issues, me included which is why I just ordered a replacement phone which success today.
You see, I actually like the device - with a few tweaks here and there it can be vastly improved. Screen gamma can be fixed, sound quality too with things like viper.
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.
Globespy said:
If a problem that didn't exist on a previous build still exists when going back to that exact build then you tell me why? Something else has changed.
Click to expand...
Click to collapse
When you say you go back to a previous version of Android, how do you do it? Do you have a flashable zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?
Johmama said:
When you say you go back to a previous version of Android, how do you do it? Do you have a zip that you flash through recovery to return to the previous version, or do you grab the factory image from Google and run flash-all.bat?
Click to expand...
Click to collapse
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one (like the new one I'll get from Google in a few hours, running JWR66Y), except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3.
In case you are serious about your bet earlier, I'd like to have a few more bills for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.
Globespy said:
I've tried EVERYTHING, but with regard to stock images I use ADB to flash the factory firmware, which as you should know basically nukes the phone and whatever used to be on it is gone forever and what you have left is a pure stock phone just as you would receive from Google if you bought a new one - except my 5ghz radio doesn't work on any 5ghz router (both my wndr3700 & R6300, nor my neighbors dlink, Asus or Linksys routers) regardless of whether it's 4.1.1, 4.1.2, 4.2.x or 4.3! The same one in getting in about 5 hours which I know will be JWR66Y.
In case you are serious about your bet earlier, I'd like to have a few more bills to for fun money, so here is my money ($3K in 100's) - you can see my N4 with this actual thread showing (it's taken with a $5K camera so just zoom in) so you know I actually put my money where my mouth is.
And I know for 100% that in the case of my phone you are wrong because I've tried to fix this for over 3 months using every available option
So if you have time to sit on Skype today and you can walk me through the things you think will fix the 5ghz connectivity issues (kernels from faux, Franco, neo, semaphore, matrix and the list goes on), or maybe you think I haven't thought about build specific kernels like JSS, JWR or JLS?
I'm available all day my friend and as soon as you show me your cash then let's do it, but I can guarantee you will lose.
Heck, it's Friday so let's make it $5K (the extra bundle of $100 notes in the top of the pic) - I was thinking of new rims for my Porsche.
https://db.tt/dZz3Xpek
PS - I'm a 25 year veteran software developer for a prominent electronics firm - yeah I'm an old dude not a pot faced teen. I hope you have the chops to back up your words. And if you don't live in the US forget about it because I can't chase you down so easily when you don't pay up and vanish.
Click to expand...
Click to collapse
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.
It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.
lazer155 said:
It's not a hardware issue. I've had the same problem with certain hybrid radios like 33/84 as mentioned by the poster above. I switched to 33/54 and it started working okay. It's some software issue. It was very annoying but fixable with the right radio.
Click to expand...
Click to collapse
I get that these methods have worked for some but not all.
Let's get real basic.
If my phone had zero 5ghz issues on say 4.2.2 (with .54 radio), and then lost 5ghz connectivity on 4.3, then I flashed a completely clean version of that previous Google factory 4.2.2 firmware (which includes the .54 radio) and my phone now shows that indeed that old radio was installed, yet i still can't get 5ghz connectivity, then its not software only. Something changed that's not software, otherwise it should work. The phone has been returned to exactly the same way it was before the 4.3 update, every shred of the 4.3 build nuked as if it never existed. Yet part of it is not functional that used to be fine? There aren't too many things it could be - software or hardware. The software didn't change, I know that is factual as its the very same Google factory stock firmware. So......?????
Johmama said:
Ok, you're starting to get a little antagonistic here. I'm just trying to help you. In my previous post I was trying to ascertain whether or not you're flashing a new radio. When you flash back to an older version of Android, if you don't flash a new radio, it won't help your situation. So unless you run either
Code:
fastboot flash radio radio.img
or a script that has that in it, such as the flash-all.bat that comes with the factory image, you aren't really doing anything to fix your WiFi issues.
Head on over to the thread I posted previously, here, try flashing a few different radios, starting with the most recent, and see if that helps. In the same thread, someone else also had issues with 5Ghz WiFi which got fixed by flashing one of the hybrid radios. Check this post for the problem, this post for a link to the originally-posted hybrid radio that fixed that guy's problem. You don't necessarily need to use that hybrid radio, but it helped that poster; scroll down the page to read his post after he reported back.
Click to expand...
Click to collapse
PM sent. I'm just playing with you mate. I just got tired of people on the other end of an internet connection making bets they can't or won't follow through on. I am no novice and have been around long enough to know that my issue is not fixable. Trust me I've tried everything and then some. After trying all the potential fixes, I also bought a new router (the r6300), and tried 3-5 other routers and same problem every time. That's when I threw in the towel and sent for a replacement.
But thanks for your suggestions. I still think in my case it's hardware as I've ruled out software.
So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....
Globespy said:
So I just had a knock on the front door and have a new N4!
However, it came pre-installed with JDQ39 (4.2.2), and it connected no problem with both my routers.
Now I have a dilemma. Firstly, if this is indeed a new phone (packaging all looks like it has never been opened), then why wouldn't it come with 4.3 installed? It's been out for over 3 months. So chances are whilst it's a new phone, it was manufactured before June of this year.
I'm terrified to update it to 4.3 in case the same thing happens again and my 5ghz connection vanishes. And it seems that most people think that Kit Kat will use the same drivers as JB 4.3, so even if I wait until Kit Kat (hopefully later this month) I could end up with the same borked 5ghz band.
Maybe 4.2.2 is as good as it gets for this phone.......what to do what to do....
Click to expand...
Click to collapse
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.
Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?
Johmama said:
That is weird that it came with 4.2.2, it's been quite some time since 4.3 came out.
Anyway, have you tried something like this? I know you said you tried a few different routers after upgrading to 4.3, but maybe you just needed to make your 5Ghz channel static. I don't know how true this is, but in that thread they said that the channel switching function isn't the greatest at detecting conflicts and switching over. Of course, even if that's true it could just be his router.
I'm sorry, I'm just having a tough time believing that it's a software issue that permanently removed 5Ghz WiFi capabilities on the hardware. I'm sure it's possible; I've seen stranger things. My gut just keeps telling me that it isn't the cause in this case. If you want to, maybe try manually flashing different radios through adb so you know nothing else is getting touched and see if one removes the 5Ghz capability; then flash back. Mainly the .84 that comes with 4.3. If not, I guess just stay on 4.2.2 until the issue is resolved. Maybe a new radio will come with KitKat that no-one will have an issue with.
Click to expand...
Click to collapse
Thanks. Tried this with every channel on the 5ghz band, 2-digit and 3-digit channel.
_delice_doluca_ said:
Let's analyse;
first of all, I do not own the device. I have just sold my Note 2 and waiting for a good second hand Nexus 4 to show up in the local market. So I have no idea of this problem specifically. Just trying to help by looking into pieces.
- First, you should try to find anyone who used to lose 5GHz connection and than got it back. If there is a case then it is not related to hardware.
- Second you should be sure abour wiping every single code on your device. I don't know how thing are done in Nexus world but in Note 2, there is no certain ways of "deleting" every code. Maybe with a PIT file, not sure.
- I know that every chip or device or SoC manufacturer put their own non-software-controlled precautions to their "things". For example, you may choose to disable thermal throttiling of CPU by modifying a kernel but it will still cut the power once it reaches a pre-defined critical heat, regardless of the software. I am sure Wi-Fi antennas have this type of phsical/hardware protections.
- Besides; who would release a "voltage boosting software" without further testing it? (that could happen though, would not be the first time in the mobile devices' world)..
- What else, besides some un-down-gradeable driver or software, do you think, could possibly disable 5 GHz signal of antenna? Maybe it is about battery? I remember Nexus 4, first having USB OTG support but then removed both from advertisings and the sofware due to battery current limitin.. Maybe there is case like this?
- Any more investigable ideas?
Click to expand...
Click to collapse
Lots of great ideas. I've heard of only a few people who managed to get the 5ghz band back, although most still suffer from much slower speeds. If you run broad searches you will see that most people can't get it to work after they lose it, even downgrading the entire system to a build/radio that previously worked without issue - like me.
Using MrSkips toolkit it absolutely wipes any trace of the 4.3 ROM and any radio association, turning the phone back to how it was shipped (JDQ39). Yet still no luck. Not all hardware is created equally, just like certain CPU can overclock/undervolt the same amounts. Perhaps some radios have lower tolerances and die? It may sound strange, but not impossible.
I'm sticking with 4.2.2 until Kit Kat comes out and will wait a few weeks to see what happens. If people get 5ghz back then it's likely Google rewrote the radio code.

When does the S5 mini become dead as far as OS upgrades or security updates?

I am curious. I assumed lollipop was going to be the last one I would see, since the phone is over 2 years old. I love Android 6.0.2 now. I am curious how long I might expect to keep getting updates on the phone? I cannot find any "end of life" lists for the S5 mini so I am unsure.
Also, what would a worthy successor to the S5 mini be to be more up to date?
Morthawt said:
I am curious. I assumed lollipop was going to be the last one I would see, since the phone is over 2 years old. I love Android 6.0.2 now. I am curious how long I might expect to keep getting updates on the phone? I cannot find any "end of life" lists for the S5 mini so I am unsure.
Also, what would a worthy successor to the S5 mini be to be more up to date?
Click to expand...
Click to collapse
Depending on the range of the smartphone, the manufacturers give support of about 2 years, after that they are totally forgotten (except samsung, they forget the mid-range smartphones at 4 months LOL)
To tell you the truth, we s5 mini users, we are very lucky that samsung has remembered us, almost never happens
jimmy999x said:
Depending on the range of the smartphone, the manufacturers give support of about 2 years, after that they are totally forgotten (except samsung, they forget the mid-range smartphones at 4 months LOL)
To tell you the truth, we s5 mini users, we are very lucky that samsung has remembered us, almost never happens
Click to expand...
Click to collapse
Thanks. I thought it was weird when I saw an update come up for a whole new OS... I love my S5 mini again, although I am looking for an upgrade to save for that's similar size but better than what I have in the S5 mini. Closest I can figure is A3 2017 but not sure.
For now, till I get more info I will enjoy my renewed S5 mini with, now, epic battery life in comparison.
Morthawt said:
Thanks. I thought it was weird when I saw an update come up for a whole new OS... I love my S5 mini again, although I am looking for an upgrade to save for that's similar size but better than what I have in the S5 mini. Closest I can figure is A3 2017 but not sure.
For now, till I get more info I will enjoy my renewed S5 mini with, now, epic battery life in comparison.
Click to expand...
Click to collapse
Doze works very well in the s5 mini, is very good no doubt, personally I recommend using some custom rom, do not have samsung applications and are extremely fast, also have new versions of android (7.1.1 in this case) Of course they are in beta and contain bugs, but they are still very good
jimmy999x said:
Doze works very well in the s5 mini, is very good no doubt, personally I recommend using some custom rom, do not have samsung applications and are extremely fast, also have new versions of android (7.1.1 in this case) Of course they are in beta and contain bugs, but they are still very good
Click to expand...
Click to collapse
Well a while back I tried to get a standard rom that was not from DBT (my handset is german, from ebay and it was cheaper) but it would not boot up. So I had to re-flash stock DBT firmware to get it to work. I remember trying Cyanogen mod on my old S4 mini but the compass did not work and a few other things. I cannot use a rom if basic phone features don't work. But with my experience of trying a different rom on my S5 mini, I bet custom roms would not work. I did get it rooted a couple times though although now I stick with unrooted so more standard apps work.
Morthawt said:
Well a while back I tried to get a standard rom that was not from DBT (my handset is german, from ebay and it was cheaper) but it would not boot up. So I had to re-flash stock DBT firmware to get it to work. I remember trying Cyanogen mod on my old S4 mini but the compass did not work and a few other things. I cannot use a rom if basic phone features don't work. But with my experience of trying a different rom on my S5 mini, I bet custom roms would not work. I did get it rooted a couple times though although now I stick with unrooted so more standard apps work.
Click to expand...
Click to collapse
How strange, it is normal that the cyanogenmod build does not work well at first, since it is a progressive development, even let me guess, you have the variant g800h?
jimmy999x said:
How strange, it is normal that the cyanogenmod build does not work well at first, since it is a progressive development, even let me guess, you have the variant g800h?
Click to expand...
Click to collapse
F I believe.
Morthawt said:
F I believe.
Click to expand...
Click to collapse
That is very strange, since the custom rom of this forum work very well for the variants F / M / Y, since they are the same device but dedicated to different markets (M in my case since I am in South America), The problem lies in the H variant, since it assembles a totally different processor and it is difficult to compile some custom rom for that variant, you should try some, I personally recommend this rom, very very good, you still have to polish one or another detail, But can be used daily
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-aicp-12-1-nougat-t3565009
And if you are one of those who like to customize your android to the fullest, I recommend this rom
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-resurrection-remix-n-5-8-2-t3562523
Both are based on the latest version of android, greetings
jimmy999x said:
That is very strange, since the custom rom of this forum work very well for the variants F / M / Y, since they are the same device but dedicated to different markets (M in my case since I am in South America), The problem lies in the H variant, since it assembles a totally different processor and it is difficult to compile some custom rom for that variant, you should try some, I personally recommend this rom, very very good, you still have to polish one or another detail, But can be used daily
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-aicp-12-1-nougat-t3565009
And if you are one of those who like to customize your android to the fullest, I recommend this rom
https://forum.xda-developers.com/galaxy-s5-mini/development/rom-resurrection-remix-n-5-8-2-t3562523
Both are based on the latest version of android, greetings
Click to expand...
Click to collapse
Thanks. I have bookmarked it. Although it seems every rom I have seen has issues for some reason. Whether in my experience with Cyanogen where the compass stops working and something else which I care about, or that one and tethering and hotspot etc. I just have been kind of burned from the excitement of my first custom rom failing me on the feature front and seeing big known issues with other custom ones I have seen. Not to mention I would want to avoid having some apps refuse to work like my banking app, google apps or Android Pay etc. But I have bookmarked it though in case because it seems cyanogen mod's site has gone down, which is not a good sign and any way they never supported S5 mini which was depressing. Are there any roms that are feature-perfect with no show stoppers on the S5 mini?
Morthawt said:
Thanks. I have bookmarked it. Although it seems every rom I have seen has issues for some reason. Whether in my experience with Cyanogen where the compass stops working and something else which I care about, or that one and tethering and hotspot etc. I just have been kind of burned from the excitement of my first custom rom failing me on the feature front and seeing big known issues with other custom ones I have seen. Not to mention I would want to avoid having some apps refuse to work like my banking app, google apps or Android Pay etc. But I have bookmarked it though in case because it seems cyanogen mod's site has gone down, which is not a good sign and any way they never supported S5 mini which was depressing. Are there any roms that are feature-perfect with no show stoppers on the S5 mini?
Click to expand...
Click to collapse
Cyanogen mod died, now called lineage os, is basically the same, the s5 mini, does not have official support by cyanogen (lineage os), but fortunately in this forum we have developers who take the trouble to create custom roms for We, those 2 roms that I left in the links are extremely functional, maybe one or the other does not work, but what if
jimmy999x said:
Cyanogen mod died, now called lineage os, is basically the same, the s5 mini, does not have official support by cyanogen (lineage os), but fortunately in this forum we have developers who take the trouble to create custom roms for We, those 2 roms that I left in the links are extremely functional, maybe one or the other does not work, but what if
Click to expand...
Click to collapse
If I was unable to use a different country code or what ever (Like mine is DBT) firmware for the same actual legit firmware for my S5 mini, doesn't that mean a third party rom would equally fail to boot as well?
Morthawt said:
If I was unable to use a different country code or what ever (Like mine is DBT) firmware for the same actual legit firmware for my S5 mini, doesn't that mean a third party rom would equally fail to boot as well?
Click to expand...
Click to collapse
I do not understand exactly what you mean, but if the question is, if custom roms may or may not work in one country or another, as far as I know, they would have to work without any problem, as long as the bootloader is unlocked , A common problem is the loss of line, ie the device can not communicate with the operator, therefore no calls or sms, but that is solved using odin and flashing the baseband (there is also a post In this forum on that)
Firmware has various ones you can get based on the carrier or country or what ever. My phone needs me to download the DBT firmware. I tried choosing one someone recommended which was also a stock genuine rom for my phone but not DBT, it was one that they said was as close to raw Android possible. I flashed it and it would not boot. They gave me reasons and all kinds of complex more indepth things I would have to do all kinds of hacky piecemeal techniques to get the other rom to work. I was not interested, using odin, selecting a file and waiting is nerve racking enough for me without having to go 3 levels more complex than that. So the only thing I could do was flash the DBT version back on the phone and it worked again.
DBT is a very clean firmware in regard to branding so no need to switch to anything else, it has only 3 apps which can be uninstalled without rooting.
As for the updates I believe that Marshmallow is the final official update we're getting, there could be a couple security patch updates though. Like many users I was pleasantly surprised that we're getting 6.0.1 considering that we're talking about a 3 year old midrange Samsung which in smartphone years is a long time.
kom-pakt said:
DBT is a very clean firmware in regard to branding so no need to switch to anything else, it has only 3 apps which can be uninstalled without rooting.
As for the updates I believe that Marshmallow is the final official update we're getting, there could be a couple security patch updates though. Like many users I was pleasantly surprised that we're getting 6.0.1 considering that we're talking about a 3 year old midrange Samsung which in smartphone years is a long time.
Click to expand...
Click to collapse
Thanks.
I certainly was shocked when I saw 6.0.1 or Marshmallow or what ever it said on the screenshot. Jaw dropped with excitement.
I don't know how guys can use Samsung's BS. KitKat, Lolipop or Marshmallow they all run poorly on my mini, and there's a lot of annoying slowdowns even when just scrolling twitter.
inejco said:
I don't know how guys can use Samsung's BS. KitKat, Lolipop or Marshmallow they all run poorly on my mini, and there's a lot of annoying slowdowns even when just scrolling twitter.
Click to expand...
Click to collapse
I highly recommend you factory reset your device. Prior to this Marshmallow update my phone was a constipated donkey. Just slow and sluggish as hell even doing the most basic of things. I got the Marshmallow update and it did feel a lot better. I factory reset and put my crucial apps back on and my phone is perfect again.
I would really like to see video showing how quick it is. Because I believe it will still be slower than Slim6.
And when scrolling is slow I get triggered as f.
inejco said:
I would really like to see video showing how quick it is. Because I believe it will still be slower than Slim6.
And when scrolling is slow I get triggered as f.
Click to expand...
Click to collapse
I have no idea what Slim6 is. What I do know is I was getting ready to throw my phone in the trash and save up for a new phone, till I got the Marshmallow update. Now my phone feels like a brand spanking new upgrade after the crap experience I have been having. Snappy, responsive, everything is working well. Perfect. Pshhh not to mention idle battery life has vastly improved.
It's custom rom for F variant of S5 mini. Battery was never a problem for me on marshmallow from Samsung though.

Most reliable ROM? (Opinion thread)

I've been with my stock Droid Turbo since it released in October 2014; I'd like to upgrade to something newer, but nothing I've found has fit my requirements (big battery, <5.5" screen, non-glass back, headphone jack, no notch, Verizon compatible, preferably unlocked/unlockable). So far, my Turbo still does the job, so I've stuck with it; however, its battery is showing its age, and it hasn't gotten an update in quite some time. Obviously, I can replace the battery at some point, so that's not a problem; the issue of updates, on the other hand, is.
I've unlocked my phone long ago when Sunshine first released to root it, so that's not an issue. My issue is that this is my one and only phone, so I need it to be stable and I'm looking to have all of its features working. I know from browsing ROM threads in the past they've typically had issues with either stability or features not working, so I've been hesitant to jump ship from the stock ROM. I'm a security professional, though, so it bothers me how behind this phone is on security updates. I'd like to move beyond Marshmallow as well, but the security updates are my main concern.
So, with all that said, I'm looking to get some opinions from users of the Quark ROMS out there. As stated, stability and feature functionality are the most important things for me. Please let me know which ROM you would recommend for my situation, and why. I know the best solution would be to trial different ROMs myself and see which works best for me; but between work, family and kids, the time just isn't there to be without a phone I know I can rely on - so I'm seeking your advice.
Thanks in advance!
(If you've got any suggestions for a phone upgrade, feel free to chime in with those as well.)
I have been using NepoRood's AOKP ROM for about a year. It's great but since he broke the screen of his Turbo, he hasn't updated the ROM. I flash BHB27's kernel and hope the security updates in the kernel are enough.
lots of stable roms available with EVERYTHING working,
calsurferpunks LOS 14 is very stable and smooth
Viper OS is exceptionally smooth and fast, also very stable
RR 7.x i would not reccommend as it was a bit less stable than the above selections, but it has ALOT of features and is stable enough for a mention
i could not get AOSPExtended or mokee to work
didnt try CRDroid very long but seemed similar to RR 7.0
have not tried others yet, if i like a ROM upon trying it, i usually trial it for a month or more to get a good idea of the long term stability/usability of the ROM
This is not an endorsement of any ROMs. In the 3.5 years I owned three Quarks, I first used rooted stock Kitkat wth xposed/Gravity box, then Lollipop CM, then Resurrection Remix (both Marshmallow, then Nougat).
However, I keep a list of current ROMs for Quarks (Droid Turbo/Moto Turbo/Moto Maxx) and I read through all the ROM threads. I help when I can, when people have issues. So, I've seen a lot... The three ROMs I see people praise most often and seem to have less issues with are:
@bhb27 RR - Resurrection Remix (Nougat)
@calsurferpunk's LOS (Nougat) -- sort of a hybrid of RR and official LOS; it doesn't have the plethora of options RR has, but I never used all the options in RR. However, it does have LED notification and Moto apps Google Play permissions and a few others.
@NepoRood's AOKP ROM (Nougat) -- but now not updated as often as he owns another device.
Most of the other ROMs on the list are also fine. I am not criticizing them in any way. We appreciate all the ROMs this device has and all the hard maintainers do to help users. All the Nougat ROMs are compatible with ALL Quarks -- Droid Turbo/Moto Turbo/Moto Maxx. They're all the same phone (the way an LG G3 is an LG G3, no matter whether bought in UK or Canada. Some even have the exact same radio bands. Moto Maxx XT1250 = Droid Turbo XT1254, with same radio bands, same FCC ID. XT1250 runs on Verizon with a Verizon SIM card. BOTH the Moto Maxx XT1250 and Droid Turbo XT1254 were sold in the U.S. by different carriers, but they were the EXACT same phone. Point is, Motorola really messed things up by calling this phone different model names for different carriers/different parts of the world.
None of the LOS-based custom ROMs would be possible without @bhb27's kernel work, however. He not only maintains two ROMs, he also codes our "stock" LOS kernel, besides having an advanced standalone kernel and his TWRP work, plus apps like Turbo Toast.
OTHER
You don't say what carrier you are with. IF you are on Verizon with your Droid Turbo, and IF you want Verizon Volte, then you need @computerfreek274 stock-based Marshmallow ROM. It's the ONLY ROM that has VoLTE and Wi-Fi calling -- and only then for Verizon. Some Droid Turbo users on Verizon still use an LOS-based ROMs as they feel the many options those ROMs offer (like the nifty LED notification and security updates) are worth not having VoLTE. But others use this stock-based ROM because it's debloated Verizon firmware, has battery and speed tweaks, and they NEED Verizon VoLTE.
NOTE: No other Quarks have VoLTE and the Droid Turbo only has it on Verizon when using stock firmware or stock-based ROM. This ROM is only compatible with Droid Turbo (or Moto Maxx XT1250, since they're really the same device).
Click the link and look through the list.
Thank you all for your responses! They more or less affirm what I thought, but it is good to hear it directly rather than what I've gathered from bits and pieces in other threads. I'll have to give them some more consideration.
Chazz, I am on Verizon, and I would prefer to keep VoLTE, if I could. I didn't think any ROMs other than the stock-based one had gotten VoLTE working though; I knew there had been some development on it, but last I had seen, that development seemed to have stopped.
Does computerfreek's ROM get the new security patches baked into it, or is it on the same patch level as stock-from-Verizon? If it's at the same level, it wouldn't really cut it for me as those security patches are my main concern. I've considered it for the features before, but I decided that wasn't worth the wipe and resetting/reinstalling everything on my phone.
bigdav1178 said:
Does computerfreek's ROM get the new security patches baked into it, or is it on the same patch level as stock-from-Verizon? If it's at the same level, it wouldn't really cut it for me as those security patches are my main concern. I've considered it for the features before, but I decided that wasn't worth the wipe and resetting/reinstalling everything on my phone.
Click to expand...
Click to collapse
No, this is where the LOS ROMs excel, especially the ones where the maintainers are active and keep the ROMs updated. They have the latest Android security patches.
This is from that CF ROM thread a few months ago, and I can't find any information to refute it:
17th September 2017, 09:51 PM
Spott07 said:
No. This ROM is based on stock from Nov 2016, and does not have any security updates after that date.
Even the latest revision, ver 1.0.8, of CF's ROM was released a few months ago, before the Blueborne vulnerability set was announced, and so obviously could not contain any applicable updates.
Click to expand...
Click to collapse
Whereas you can see the update date in the title of these two threads:
ROM update! RR-N-v5.8.5-20180414-quark-Mod.zip
[ROM][Quarks][LOS 14.1 Unofficial][7.1.x][2018-04-17]
Both have April 2018 security patches.

Non EMUI Rom for Mate 20 PRO

(I have no permissions for ROMs sections so posting this here)
So it looks things are slowly moving , and we are able to unlock bootloader and root our devices.
User @auras76 was kind enough to bring as the first ROM available, but I guess I am not the only one looking forward to get rid of EMUI and its poor customisation layer
I hope once firm .173 hits general release we start getting more dev interest, but the goal of this thread is to find out if any dev could be potentially interested (or already planning) to work on a non-EMUI ROM
I can imagine a bounty could be organised for users to support financially this action.
What are everyone's thoughts on this?
Doubt you will see much development of any major Rom's if there is not a free way to unlock your bootloader as there just won't be that many unlocked devices
I am fully aware of that, however let´s hope that changes if/when .171 FW is generally available and allows bootloader unlock.
I just wanted to check if there would be a way to attract some devs here, even by supporting their work (purchasing a device? 10$ per person???)
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone.
If you think I'm exaggerating pick a custom ROM for the OP5, 5T, OP6 or 6T and look at the last several pages of user posts.
They will be users reporting bugs-often very serious ones.
If you pick an OP5 or 5T ROM many will no longer be in development. The last several pages before the ROM was abandoned will be users still reporting bugs that will never get fixed.
And that is on phones that are supposedly very development friendly.
The days of custom ROMs that improve a phone's functionality, speed and stability over the stock ROM died with Nexus phones but if you want to run a custom ROM anyway buying this phone makes pretty much no sense because Huawei is not developer friendly. They don't want owners of Huawei phones to unlock their bootloaders or run custom ROMs on Huawei devices. The same is true for Xiaomi and Samsung phones.
For that matter Google, the company behind Nexus phones which were the most developed friendly phones anyone could buy no longer wants people to use custom ROMs which is why they came up with the ROM certification program and safety net.
Apps that help phone owners bypass safety net are automatically banned from the Play Store. Whatever method Magisk uses to bypass Safety Net gets plugged by Google forcing the developer to come up with a new method that will stop working when it also gets plugged by Google.
The developer behind SuperSu said the writing was on the wall for original Android development several years ago and he knew what he was talking about.
Well, I thought XDA was exactly the place where people "like custom ROMS" and tinker with their phones.
I am coming exactly from OP phone so I know how scene works there.
OP phones are dev-friendly but not many people try different ROMs as Oxygen is probably the smoothest implementation layer of all manufacturers, so there is no need other to change other than fun.
But we are not talking about OP but Huawei here, which is the opposite case. Lousy software implementation, from battery management (see the Powergenie issues threads), to Huawei bloatware, notification handling, little customisation allowed.... So Huawei is not like OP but more like Xiaomi, heavily (not for good) customised Android version. And there might be not many OP ROMS, but check in Xiaomi land... many super stable versions that improve almost any Xiaomi device with AOSP or LOS versions.
As I said, maybe all it takes is to support a dev with a device for ROM release... I know I wouldn't be the only one looking forward to this.
Alright let's clear up what XDA is about.
It's a hub for developers. It's not a hub for people coming in with no knowledge demanding/posting hundreds of threads asking for ROMs for a device which is bootloader locked in most cases. Attitude like this steers developers away from devices because of noob communities. Look at the Samsung community on XDA.
Huwaei is still an infant when it comes to Android so they are learning the ins and outs of what works and what doesn't. Give em a break. They produce amazing devices with amazing technology. Just because it's locked doesn't mean you have to get your nickers in a twist because no one wants to develop for a new company on the Android scene. Give it some time. Maybe someone will come along and get the ball rolling for everyone and find a nice little backdoor in the bootloader and make it possible for everyone. Till then don't hold your breath and stamp your feet. Do your research before you flog out a grand on a device that might not have unofficial development for.
I really hope we can open this device up for more development, what could we do with unbridled access to the NPU, 3 rear cameras and the front 3d point cloud camera array
jhs39 said:
If you like custom ROMs so much buy a One Plus phone. Lots of custom ROMs and every custom ROM has bugs. There is no build of any custom ROM that doesn't have bugs and sometimes the bugs on "stable" versions of custom ROMs are so serious they impact the basic functionality of the phone. .
Click to expand...
Click to collapse
Had to pop in here to tell you you're completely wrong on that one.
Off the top of my head. No limits xXx for the OnePlus 5, not a single bug.
From Oreo 8.1 anyway.
A lot for devices have ROMs which surpass stock in more ways than one and have zero bugs
Further to my point and @ the OP.
The p20 pro has only seen ROMs because of the last few users / developers who have committed to Huawei/Honor devices and the fact that Honor view 10 ROMs work on the pro, in light of the changes made by Huawei IE: bootloader lock down, you will not see a lot of ROMs at all for your device in fact anyone who wants to root / flash / unlock their phones should not touch Huawei or Honor ever again, maybe (and that's a big maybe) the greedy pair of OEMs will see sense. But I doubt it.
Advice in short, dont buy their phones, I certainly won't ever again. They don't deserve it after what they've done.

Question Any opinions or advice on Android 12, One UI 4.0?

As we're seeing numerous bugs have plagued Android 12. The latest update is Samsung's 4th Final Release. What's your experience been and is it confirmed the update locks the bootloader on previously unlocked devices? I'm holding off on updating until some positive feedback is the norm.
Update to A12 with G998B/DS (Exynos) did not result in locking BL. But as BL is upgraded from 3 to 4, downgrade will not be possible. This is not a new phenomenon, this was always the case with BL-upgrades.
In existing thread there is already a lot of feedback/experience on A12 on the FW for exynos S21U. I see no need to also open same discussions in this new thread, unless it is specified to SD-versions.
OnnoJ said:
Update to A12 with G998B/DS (Exynos) did not result in locking BL. But as BL is upgraded from 3 to 4, downgrade will not be possible. This is not a new phenomenon, this was always the case with BL-upgrades.
In existing thread there is already a lot of feedback/experience on A12 on the FW for exynos S21U. I see no need to also open same discussions in this new thread, unless it is specified to SD-versions.
Click to expand...
Click to collapse
No posts in this link discusses the A12 Update, changing CSC is the topic, maybe you're confusing it with a different thread. I'm more interested in hearing from user's with a clean, stable update, Snapdragon or Exynos.
The answer is very simple...A12 is a new OS compared A11. This means it comes with its fair share of bugs. I'm sure you'd remember it took at least 6 or 7 iterations of A11 to get the perfect rom. You should expect the same with A12. I'm expecting by March 2022, we should have a fairly stable A12 rom for the S21Ultra.
That may be the case but I don't remember any Android 11 update with this many glitches and it's not restricted to Samsung, other brands are suffering as well even Pixel. I've always updated my device's whenever a new version is available with no issues but not this time around. Seems every other thread on XDA is reporting problems with A12.
varcor said:
That may be the case but I don't remember any Android 11 update with this many glitches and it's not restricted to Samsung, other brands are suffering as well even Pixel. I've always updated my device's whenever a new version is available with no issues but not this time around. Seems every other thread on XDA is reporting problems with A12.
Click to expand...
Click to collapse
Actually, the android version we got in our S21U (A11) was considerable a stable version since the OS was released last September while S21 was out in Feb..so basically we had a more refined version of the OS...A12 is fairly new and hopefully by Feb/ March, the OS will become stable as well...this is the case with any OS..be it Android or iOS
varcor said:
That may be the case but I don't remember any Android 11 update with this many glitches and it's not restricted to Samsung, other brands are suffering as well even Pixel. I've always updated my device's whenever a new version is available with no issues but not this time around. Seems every other thread on XDA is reporting problems with A12.
Click to expand...
Click to collapse
I personally think A12 is a potato release.
Every OS has misfires. iOS had iOS 7 and iOS 11.
Android had Lollipop (v5) - absolute lemon of an update.
A12 doesn't seem as bad, but it's a Meh update. From what I've seen, it's built around cosmetic changes mainly with some minimal privacy features peppered in to make it sound more creditworthy than it is. Every single manufacturer is struggling with it, including Google. Maybe OneUI 4.1 will bring a more stable version. But who knows?
All I know is that there aren't enough architectural or performance benefits baked into A12 that justify going one whole number up from A11.
That's just my opinion. Others may feel differently. But I tried it and couldn't suffer it on my phone more than 2 weeks. So I "downgraded" to a faster, peppier A11 build after a gruelling fortnight of hoping, praying, charging and resetting the phone till I couldn't stand it anymore!
The S21 Ultra is best experienced on A11, as of today. Updates may change it for the better, but that's a 'maybe' and 'later' in the same sentence and I'd like to see my device at its best behavior today!
"Every single manufacturer is struggling with it, including Google"
Google blew chunks with this puppy. The blame lies mainly with Google but Samsung is culpable as well, no way should they have released it without in depth testing to sort out compatibilities. You'd think they would have figured it out long ago.
varcor said:
"Every single manufacturer is struggling with it, including Google"
Google blew chunks with this puppy. The blame lies mainly with Google but Samsung is culpable as well, no way should they have released it without in depth testing to sort out compatibilities. You'd think they would have figured it out long ago.
Click to expand...
Click to collapse
I think Samsung means well, all things considered. As you say, they could've spent more time fine tuning the A12 releases. But they probably succumbed to the temptation of being one of the first to the table with the new OS. They're getting hammered in almost all markets by the Chinese brands and Apple is eating into their market share too. Release decisions may have been influenced by marketing rather than development. Dunno. Just a guess.
I have to commend their commitment to timely updates. Nobody on the Android camp is as pro-active with with OS updates on as many devices as Sammy is currently. They've come a long way from their TouchWiz days and OneUI is currently my favorite android UX after OxygenOS was neutered by Oppo.
I genuinely think they're trying their best to work with the material they have. The material however (A12) may be the bottleneck here.

Categories

Resources