Related
I'm new to the tab s, and I hope there is a stable and relatively bug free ROM that is not lollipop. Marshmallow is too new, so I hope for kitkat. I really like Cyanogenmod, but it looks like the earliest CM ROM is 12.x which, I believe, is android 5. Yuk. Not interested in terrible battery life. Any suggestion for a real solid, fast, debugged ROM for the SM-T700? I'm getting my new tablet tomorrow, and I'll be ready to root, backup and reROM right away. Hate the bloat! Thanks!
Not quite sure what you mean about terrible battery life. How is that related to lollipop?
gruuvin said:
I'm new to the tab s, and I hope there is a stable and relatively bug free ROM that is not lollipop. Marshmallow is too new, so I hope for kitkat. I really like Cyanogenmod, but it looks like the earliest CM ROM is 12.x which, I believe, is android 5. Yuk. Not interested in terrible battery life. Any suggestion for a real solid, fast, debugged ROM for the SM-T700? I'm getting my new tablet tomorrow, and I'll be ready to root, backup and reROM right away. Hate the bloat! Thanks!
Click to expand...
Click to collapse
Since a few days have passed, and I've done a lot more reading than the average person wants to do to answer these questions, and I've flashed a new ROM, I'll answer my own questions for others looking into similar questions.
It looks like many devices out there have suffered from the Android 4 to Android 5 updates, especially those forced by manufacturers. The biggest undesirable symptom being painfully reduced battery life. This is debated all over, especially since your mileage may vary. Since you can find these complaints much more frequently than with other Android upgrades, and since Google quickly released Android 6, it's safe to say there are legitimate issues here. Often people claim no such issues if upgrading to Android 5.1 (instead of Android 5.0) and/or if upgrading via a full wipe then clean flash. And since this is not explicitly the conventional update method for most users (again, mfg pushes update) then it's reasonable to assume updates from Android 4 to Android 5 may really just flat out "SUCK". Whether it's Google's fault or phone MFGs fault, it makes no difference to the end user; they will avoid the version of Android if they can't trust it.
As far as a better, stable, debloated KitKat (Android 4.4.x) ROM goes ...... sorry, too late. Pretty much all focus has been on getting Android 5 working properly. There are CyanogenMod 11 ROMs for the T700, but don't hold your breath for anything "official". I am now running CyanogenMod 12.1 (Android 5.1) and it seems stable with no issues so far and the battery life doesn't seem much worse than it was when running stock the TouchWiz KitKat, which was nice but heavily bloated. This is after root, TWRP, backup, full wipe, then flash CM12.1 and gapps.
My first choice ROM would have been LiquidSmooth, because a lot of praise was given it for being stable and bug-free, but all the download links are dead, the website(s) are pretty lame, and the last builds are almost a year old, so I gave CM a shot, since there are still recent nightly builds, and it is working well.
On a side note: Android 6 (M) third party ROMS are still yet to be stable on all sorts of devices out there, and Google is about to release Android N, possibly as Android 7.
Cmon Google, get it together. Slow down and do things right, and quit making things worse, like the exSDcard restrictions.
This isn't the best news.
http://m.gsmarena.com/skype_for_lin..._to_autostart_launch_minimized-news-22752.php
We can probably safely say March or April. Oh well.
All kidding aside: llabtoofer just said within the next 3 weeks all you guys in Europe should have it. Enjoy
Sent from my HTC 10 using Tapatalk
Nougat is not ready for prime time. Not impressed at all. My custom MM rom works perfectly. I tried Nougat. Uninstalled.
Looks like soon it would be the US unlocked users getting angry : why the heck we're using a buggy version??
Even now it's EU users are complaining : when the heck could we taste nougat...??
tony_5309 said:
We can probably safely say March or April. Oh well.
All kidding aside: llabtoofer just said within the next 3 weeks all you guys in Europe should have it. Enjoy
Sent from my HTC 10 using Tapatalk
Click to expand...
Click to collapse
he said we will havw 2 months ago
Alpert3 said:
Looks like soon it would be the US unlocked users getting angry : why the heck we're using a buggy version??
Even now it's EU users are complaining : when the heck could we taste nougat...??
Click to expand...
Click to collapse
I have the US unlocked model and I'm using the latest firmware with Maximus HD and ElementalX installed, no complains at all so far the stock ROM was also fine the few weeks I used it
DeadPotato said:
I have the US unlocked model and I'm using the latest firmware with Maximus HD and ElementalX installed, no complains at all so far the stock ROM was also fine the few weeks I used it
Click to expand...
Click to collapse
Maximus HD is based on leaked EU update. And I am not talking about that.
Maybe you haven't seen what does the dev of Maximus say about the upcoming EU OTA?
No one has specified what "buggy" even means... is it something minor like a laggy UI or a major security vulnerability like stagefright?
*bugs* is a bull excuse in regards to no updates
while while they're fixing these bugs *with N then why didnt they continue to update our devices on MM with the monthly security updates ?
Europe unlocked devices haven't had an update since October & that came with the august 2016 security patch what happened too September, November , December, January
this fixed version of N will be out in February according to llabtoofer will likely be 7.0, we probably wont see 7.1 until spring (htc ultra hasn't even released yet & thats on 7.0)
Alpert3 said:
Maximus HD is based on leaked EU update. And I am not talking about that.
Maybe you haven't seen what does the dev of Maximus say about the upcoming EU OTA?
Click to expand...
Click to collapse
I'm taking about you said US users now will be angry about why they were left with a buggy firmware, and I'm telling you I used it with the stock ROM and I'm not angry about it. He said the EU build was more stable, that doesn't mean that the US was a bad build though and yes, it may be based on such firmware but I'm using it with the US one
DeadPotato said:
I'm taking about you said US users now will be angry about why they were left with a buggy firmware, and I'm telling you I used it with the stock ROM and I'm not angry about it. He said the EU build was more stable, that doesn't mean that the US was a bad build though and yes, it may be based on such firmware but I'm using it with the US one
Click to expand...
Click to collapse
Come on man, I am not saying US update isn't good. I am saying compare to EU update, US one is less responsive and less smooth. Been treated differently might make some users angry. #sense of humour#...
I am sure the US will also get the equivalent matching update around the same time
7.0 has been a mess, and even 7.1.1 has alot of problems, even on nexus/pixel devices. It would suck to be on 7.x and have that 30% battery bugg that alot of people experience. And thats just the obvious buggs.
7.x does not offer enough of a upgrade to make it worth having a buggy release. Esp if one is stuck with that buggy version for months.
I have the Nougat update on my T-Mobile HTC 10 completely stock not rooted and have experienced a few bugs.the day after I updated I took a picture and the phone froze went into a reboot and actually rebooted itself 4 times before it went back into the system. Had a random reboot another time and had an instance where my phone would not charge but a reboot fixed the issue
Sent from my HTC 10 using Tapatalk
And please remember there's no OS nor app is bug free in the world. It is an excuse but also the truth.
I bought iPhone 7 last just want to experience a "smooth OS", but it freezed while taking a picture, battery drops very quickly and phone got every hot randomly... So yeah, back to HTC.
jmkhenka said:
7.0 has been a mess, and even 7.1.1 has alot of problems, even on nexus/pixel devices. It would suck to be on 7.x and have that 30% battery bugg that alot of people experience. And thats just the obvious buggs.
7.x does not offer enough of a upgrade to make it worth having a buggy release. Esp if one is stuck with that buggy version for months.
Click to expand...
Click to collapse
I tried N for a bit on Viper and had bad battery drain so I went back to MM and still had that battery drain, I found out Facebook has been causing bad battery so I uninstalled it and Messenger and seems to be much better. I was wondering if Facebook was my issue on N as well or if it was Android N causing it. Guess I will stick with MM for now.
I've been on Nougat for some time now (unlocked) and I have noticed any issues. What exactly is the problem?
djbutter said:
I've been on Nougat for some time now (unlocked) and I have noticed any issues. What exactly is the problem?
Click to expand...
Click to collapse
Is your device US unlocked ? Do all your apps that auto sync or update do so while you're using battery saver, or while you're on data? Only way I can get gmail and other similarly syncing apps is on Wi-Fi without using battery saver
u
eckharttim said:
Is your device US unlocked ? Do all your apps that auto sync or update do so while you're using battery saver, or while you're on data? Only way I can get gmail and other similarly syncing apps is on Wi-Fi without using battery saver
Click to expand...
Click to collapse
i meant to say that I haven't noticed any issues, but clearly you understood me. ?
Anyway, I get push gmail notifications as usual, no issues there. I'm almost always only on mobile data, and rarely ever use battery saver. I have an unlocked stock US model.
The only minor issue I've noticed is that sometimes I don't get notified of whatsapp messages (via the notification shade), if multiple are received at around the same time.
The only bug i've found was in the Settings.
If you enter it, press back button and then try to enter again, it'll take some seconds to show up.
Everything else is ok.
Sent from my HTC 10!
Still on android 11 unrooted
getting updates notifications while now but not updated
Is it worth doing it now and all issues etc resolved
backed up to Google so anything else to do if I update
Rule #1 - if your platform is fast, stable and fulfilling its mission... let it be!
Upgrades can and do break things.
Backup all critical data redundantly to at least 2 hdds that are physically and electronically isolated from each other and the PC.
Never encrypt data drives.
Never disk clone media files/folders.
Copy/paste then verify size and if readable.
Lol no. At least not OOS. Stick with OOS11 or I've personally tried derp and nameless and ran nameless until the a12 blob update.
Yes, I agree w/ the above posts from what I've encountered. I'm on Derpfest with Arter97 kernel and is very nice but ROM is a little outdated in the android world since it's an April update and not being updated going forward. But honestly I'm pretty good with the device besides no speed wireless warp charging and not being able to use my DAC.
NO.
OOS 12 is ****.
Yes.
You are you. Every person use what they like/need on the phone. So you may have/not have any of them problems.
12 has worked great for my usage since it's release! Cheers
galaxys said:
12 has worked great for my usage since it's release! Cheers
Click to expand...
Click to collapse
That's on OP?
Even Pixel's have had reported issues with it.
My N10+'s will stay on 9 and 10... no issues.
The camera is more of a menace with Android 10, but that's a Samsung UI thing
Definitely don't want active scoped storage though. 12 seems too busy with nickel and dime permissions; not needed for trusted apps. If an app isn't trusted... it's not loaded; KISS.
blackhawk said:
That's on OP?
Even Pixel's have had reported issues with it.
My N10+'s will stay on 9 and 10... no issues.
The camera is more of a menace with Android 10, but that's a Samsung UI thing
Definitely don't want active scoped storage though. 12 seems too busy with nickel and dime permissions; not needed for trusted apps. If an app isn't trusted... it's not loaded; KISS.
Click to expand...
Click to collapse
Yes, on my 0nePlus 9 Pro and 10 Pro! Unlocked BL and Magisk loaded! Security is all over the map...
I wouldn't.
I'm still having silly issues that should have been fixed ages ago.
The app switcher UI freezes regularly.
The camera app glitches during video after a couple of minutes and the sound cuts out and video gets choppy.
Photos are often way over-exposed.
The "Always On" clock/display doesn't actually stay on.
I occasionally have issues with animation stuttering when scrolling and so on.
It was actually a pretty solid phone before I did the Android 12 update. I really should roll it back but I've just been lazy.
Weren't happy at all with OOS12. I used Derpfest and was happy with it, but as it's no longer maintained I needed something else.. Now on LineageOS 19.1 and I'm not searching for alternatives anymore, I'll probably use it until I switch phones. Battery isn't as good as on OOS11 (with custom kernel), but I manage a day without issues. You probably wouldn't if you're a phone gamer.
The 12 release for the 9 pro is poor. I only upgraded as it was a required step for my chosen ROM installation.
efex said:
Weren't happy at all with OOS12. I used Derpfest and was happy with it, but as it's no longer maintained I needed something else.. Now on LineageOS 19.1 and I'm not searching for alternatives anymore, I'll probably use it until I switch phones. Battery isn't as good as on OOS11 (with custom kernel), but I manage a day without issues. You probably wouldn't if you're a phone gamer.
Click to expand...
Click to collapse
hi...do you have any issues with phone calls and bluetooth???
Dr.Pagan said:
hi...do you have any issues with phone calls and bluetooth???
Click to expand...
Click to collapse
Normal phone calls work fine, no issues. I only use BT to listen to music, have a connected smart watch and libre sensor (diabetes sensor), all work fine (better than with OOS even). I do not use BT to answer calls, so I don't know how well that works.
For my experience oos12 was a great upgrade over oos11. Phone feels more smooth and I do get better battery life for my usage. A big noticeable difference in stand by drain while sleeping.
Spectre Nine said:
I wouldn't.
I'm still having silly issues that should have been fixed ages ago.
The app switcher UI freezes regularly.
The camera app glitches during video after a couple of minutes and the sound cuts out and video gets choppy.
Photos are often way over-exposed.
The "Always On" clock/display doesn't actually stay on.
I occasionally have issues with animation stuttering when scrolling and so on.
It was actually a pretty solid phone before I did the Android 12 update. I really should roll it back but I've just been lazy.
Click to expand...
Click to collapse
I keep seeing similar complaints to yours.
I would just roll it back. Android 13 is looking like it will be a complete fubar. Scoped storage is still an Apple nightmare. Malware is far easier to deal with than these "improvements"
I think that so far Android 9 is the zenith point for this platform; a good balance of functionality, usability and security. I have no issues with Pie on my stock N10+; fast, rock solid stable, reasonably secure and most importantly it's fulfilling its mission. It's a joy to use this device because it does what -I- want and it's very predictable. Predictability makes spotting malware much easier as well as basic troubleshooting. As such I spend very little time doing maintenance or troubleshooting. This load is over 2 yo now. That's what Android is capable of... or should be.
Find an OS version that works for you and adopt it for the life of the device
Still on Android 11 take it matter of choice to update or not
users still have issues with android 12?
if you go by that, people also have problems with oos 11 and not just with oos 12. I personally use oos12 and have no problems
ChrisFeiveel84 said:
if you go by that, people also have problems with oos 11 and not just with oos 12. I personally use oos12 and have no problems
Click to expand...
Click to collapse
Both 11 and 12 are a scoped storage mess.
Android 10 was the last version where scoped storage wasn't fully active by default.
Expect the potential need for a factory reset if you upgrade to 12. You may need to change settings and find other workarounds to get it running right.
Meet the green dot.
I did it, upgraded to OOS12 and I must admit there were some things I liked better battery life. But there were changes that I really really did not like.
I needed to fall back on Nova Launcher to get some of the visuals back and vibe back.
A couple of days ago I decided to put cRdoid A12 on it. I miss some options from OOS but overall I'm happier now.
Hello guys, should I be worried? I mean there's a lot of news circulating around about this issue but so far I font have this issue only fingerprint loss after update. Now should I be worried on this?
Lol, you should always worry when you update firmware
Rule #1- if a OS is running fast, stable and fulfilling its mission let it be!
This stock N10+ N975U hasn't been updated in 3 years. The current load is now close to 2.5 yo still fast, stable with minimal maintenance. It runs like a bat out of hell.
Mucking with the firmware is the best way to screw up an Android...
yesterday i was checking if there was a firmware upgrade for my phone (SM-A325F) on samfw. well for other reasons. i saw an update for other regions that was unusual. Samsung had bumped the binary bit version from 2 to 3. Now this scared me. since if the fw arrives for all the regions it will make it undowngradable to one ui 3.1 or 4.1. since I am using gsi's (Generic System Images) which is currently crdroid 9.2. It may cause a problem if samsung breaks something with the update. Since i wont be able to downgrade to older firmwares. Twrp might also be a problem since i have seen threads on a12 that some twrp versions do not work for some binary bit versions. That scared me. Although i could get around this by using repacksuper but still. I have a custom kernel made by myself that i am daily driving. it will make it hard to install since i'll have to decompress and repack boot.img. Then disabling encryption... i am pretty sure gsi's wont boot with encryption enabled. I have no idea on how i' disable it. without twrp. there might be ways i'd have to do research.
I might just be overthinking. but yes. i'll have to test when it comes out for my region. I am also waiting for one ui 5.1 which may also have bumped binary bit version.
D:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
blackhawk said:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
Click to expand...
Click to collapse
Exactly
blackhawk said:
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be!
Upgrades and updates can and do break Samsung's. It can easily turn into a time devouring hurt locker tour if it damages, alters or destroys features or functionalities you are using and depending on.
Doing nothing breaks nothing...
Click to expand...
Click to collapse
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Captain_cookie_200 said:
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Click to expand...
Click to collapse
such as 60Hz bug happening on most new gsi's where it wouls refuse to switch to 90Hz. Only with A13 vendor. A11 vendor works fine.
Captain_cookie_200 said:
thats true. but i have been facing weird issues with android 13 firmware's vendor. thats why i wanted to upgrade. I wont for now. It also seems a bit slow to me. unlike other people saying that running generic system images on their vendor works fine and smooth. while its laggy for me.
Click to expand...
Click to collapse
Between a rock and a hard place... Google punches these systems out too fast. Problems are a given. Best to stick with one version, find fixes, work arounds and be happy. Otherwise you'll constantly be mucking with it.
I'm still running 9 and 10 on my stock N10+'s. No way I'm upgrading. I prefer Pie though. Current load on this N10+ will be 3yo in June, still running fast and stable. Zero security issues in that time.
Scoped storage... No. It wasn't needed; it just causes headaches and unwarranted complexity.
Gookill invariably makes a mess out of anything they do (or kill it) eventually; it's their nature.
blackhawk said:
Between a rock and a hard place... Google punches these systems out too fast. Problems are a given. Best to stick with one version, find fixes, work arounds and be happy. Otherwise you'll constantly be mucking with it.
I'm still running 9 and 10 on my stock N10+'s. No way I'm upgrading. I prefer Pie though. Current load on this N10+ will be 3yo in June, still running fast and stable. Zero security issues in that time.
Scoped storage... No. It wasn't needed; it just causes headaches and unwarranted complexity.
Gookill invariably makes a mess out of anything they do (or kill it) eventually; it's their nature.
Click to expand...
Click to collapse
these bugs i face are expected since these are not device specific roms. but fix is always possible. One ui itself for this phone is kind of terrible otherwise i wouldnt have tampered with gsi's to start with
Captain_cookie_200 said:
these bugs i face are expected since these are not device specific roms. but fix is always possible. One ui itself for this phone is kind of terrible otherwise i wouldnt have tampered with gsi's to start with
Click to expand...
Click to collapse
Ive gotten excellent mileage from One UI once the device was optimized. Before it was optimized it was a mess. However Samsung firmware can vary widely from model to model, region, hardware and so on. That makes things more difficult and unpredictable.
Until you get on top on it Samsung is a pain. One reason I refuse to upgrade hardware, firmware or software is this device is running pretty clean, fulfilling its mission, requiring very little maintenance and it's fun to use.
blackhawk said:
Ive gotten excellent mileage from One UI once the device was optimized. Before it was optimized it was a mess. However Samsung firmware can vary widely from model to model, region, hardware and so on. That makes things more difficult and unpredictable.
Until you get on top on it Samsung is a pain. One reason I refuse to upgrade hardware, firmware or software is this device is running pretty clean, fulfilling its mission, requiring very little maintenance and it's fun to use.
Click to expand...
Click to collapse
welp for me its the opposite here. one ui is absolutely laggy with its terrible restricted animations for Mid range phones. Then it lags while doing normal tasks. i have found gsi's to be more smoother than one ui. I hate firmware upgrades too. but since this shet is weird and has litt unkown bugs no one has ever seen before upgrading to a newer fw is my only option. Otherwise i'd be stuck on one ui with terrible optimizations for this phone. My friends own the same Galaxy A32 4G and i have seen one ui lag on their phones. it is terrible.
Captain_cookie_200 said:
welp for me its the opposite here. one ui is absolutely laggy with its terrible restricted animations for Mid range phones. Then it lags while doing normal tasks. i have found gsi's to be more smoother than one ui. I hate firmware upgrades too. but since this shet is weird and has litt unkown bugs no one has ever seen before upgrading to a newer fw is my only option. Otherwise i'd be stuck on one ui with terrible optimizations for this phone. My friends own the same Galaxy A32 4G and i have seen one ui lag on their phones. it is terrible.
Click to expand...
Click to collapse
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
blackhawk said:
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
Click to expand...
Click to collapse
using floating.xml tweaks i made my one ui installation some what usable. also note... (haha note..) your note 10+ is an older flagship phone. while the galaxy A32 is a mid ranger that samsung pays less attention to. Thus we are hit with such bugs and terrible optimizations disabled features till to this day. obv samsung rigs the one ui experience on these phones on purpose. otherwise they'll be "too good". even using alot of tweaks and mod doesnt help improve it much. trust me i tried daily driving one ui with floating tweaks and others..
Captain_cookie_200 said:
using floating.xml tweaks i made my one ui installation some what usable. also note... (haha note..) your note 10+ is an older flagship phone. while the galaxy A32 is a mid ranger that samsung pays less attention to. Thus we are hit with such bugs and terrible optimizations disabled features till to this day. obv samsung rigs the one ui experience on these phones on purpose. otherwise they'll be "too good". even using alot of tweaks and mod doesnt help improve it much. trust me i tried daily driving one ui with floating tweaks and others..
Click to expand...
Click to collapse
Likely true. The older N10+ is likely a better choice than the newer midrange Samsung's due mostly to hardware but maybe firmware too. The newer Samsung flagships haven't turned out all that well either. The variable refresh rate displays are causing a lot of troubles across the board. Scoped storage is another CPU cycle sucking issue on Android 11 and higher.
5G can add to the problem; if in use it can use a lot of resources.
Rather than squander money on their Fold technology Samsung maybe should have thrown the money at it's midrange phones...
blackhawk said:
Hard to say why that is without playing with it.
One UI should be fast, stable and use very little battery. If you saw this N10+ out of the box though it could be described as what you are seeing. It was a handful at first. Literally getting less then half the SOT it gets now. The lagging generally is caused by junk running in the background, that was noticeably slowing down this phone. Using up possessor and modem bandwidth. Quit the terror
I eventually got it optimized using with Package Disabler, settings and a few 3rd party apps. It's a completely different experience from that hog mess it first was.
Click to expand...
Click to collapse
Got a list?
blackhawk said:
Likely true. The older N10+ is likely a better choice than the newer midrange Samsung's due mostly to hardware but maybe firmware too. The newer Samsung flagships haven't turned out all that well either. The variable refresh rate displays are causing a lot of troubles across the board. Scoped storage is another CPU cycle sucking issue on Android 11 and higher.
5G can add to the problem; if in use it can use a lot of resources.
Rather than squander money on their Fold technology Samsung maybe should have thrown the money at it's midrange phones...
Click to expand...
Click to collapse
this is exactly why i am never getting a samsung again. especially midrangers. they are wful. idk why samsung even bothers to make phones if they cant maintain it properly. Yet mor phones are being added to A series line up day by day.
Like a software update literally bricked my fingerprint on display. looking at the logs. my keystore is gone and using no matter what firmware it wont come back. great samsung. the last great thing abt this phone for me is gone now.
Yet i remember how upgrading to one ui 4.1 from 3.1 caused an issue where my ril would restart when using data. It would happen randomly. One ui 5 fixed this later on but wow samsung...
i had to resort to gsi's to get a working phone again since one ui 3.1 was slow af.
samsung has basically fuked me in every single way. and now i am just stuck with this thing for 4-5 years.
so to fix such annoying bugs that still exist. i my have to do the update... Yes ik it may cause my ability of downgrading to go away but still.. atleast i may get a better experience hopefully. otherwise welp ig i'll be stuck on one ui again. sucks to be me.
Captain_cookie_200 said:
this is exactly why i am never getting a samsung again. especially midrangers. they are wful. idk why samsung even bothers to make phones if they cant maintain it properly. Yet mor phones are being added to A series line up day by day.
Like a software update literally bricked my fingerprint on display. looking at the logs. my keystore is gone and using no matter what firmware it wont come back. great samsung. the last great thing abt this phone for me is gone now.
Yet i remember how upgrading to one ui 4.1 from 3.1 caused an issue where my ril would restart when using data. It would happen randomly. One ui 5 fixed this later on but wow samsung...
i had to resort to gsi's to get a working phone again since one ui 3.1 was slow af.
samsung has basically fuked me in every single way. and now i am just stuck with this thing for 4-5 years.
so to fix such annoying bugs that still exist. i my have to do the update... Yes ik it may cause my ability of downgrading to go away but still.. atleast i may get a better experience hopefully. otherwise welp ig i'll be stuck on one ui again. sucks to be me.
Click to expand...
Click to collapse
The N10+ Snap is still a good choice if you don't need to root if you can get one running on 9 or 10. The Exynos variant can be rooted but the hardware isn't as good. The spen is very useful.
I learned the hard way with my S4+ that it's a big mistake to upgrade/update the firmware especially on carrier phones. Haven't repeated that mistake.
I don't blame you for being irate about Samsung. They are a mess. The N10+ is the only Samsung I would consider getting even now.
I think this is getting off-topic.
Arealhooman said:
I think this is getting off-topic.
Click to expand...
Click to collapse
yeah it is. main purpose of my thread was if twrp breaks due to diff version of bootloader. because i wont be able to downgrade once i upgrade. I could patch my stock recovery for fadtbootd but i would still love to have twrp.
An update. so i built a kernel for this thing using source samsung released with the bumped bit version. flashed it on an older bit 2 firmware. it works fine and i am daily driving it now. i thought it wouldnt boot. but it does.
So looks like the update i previously refered to had SB3 boot loader. i saw it for nepal. while i just saw one ui 5.1 drop for this phone with the U3 boot loader. i am upgrading and i'll tell wether the twrp and other stuff works. If not i'll report any workarounds i used.