Related
I have the Verizon flavor and passed on the upgrade due to my experience on my lg g2. My battery life went all to hell so i rolled back to kitkat and am quite happy to stay there. I'm curious as to how the upgrade is working for you on this device.
I personally love CM12.1 right now. It very (as in never) rarely crashes and for some reasons, apps seems to be more stable than on other roms. I have not experienced any battery issues and it seems to be the contrary for me because I am getting noticeably better battery life than before. Just to clarify things, I am running a V500, rooted, and running TWRP 2.8.
mach01 said:
I personally love CM12.1 right now. It very (as in never) rarely crashes and for some reasons, apps seems to be more stable than on other roms. I have not experienced any battery issues and it seems to be the contrary for me because I am getting noticeably better battery life than before. Just to clarify things, I am running a V500, rooted, and running TWRP 2.8.
Click to expand...
Click to collapse
That was not his question...
Although I recognize some things I don't like in official Lollipop for the VK810.4G, I like it. Smoother, faster, especially [insert plug here] on my maximum debloated stock ROM in my signature below [/insert plug here]. ?I'm a function over form guy, though.
Sent from my VK810 4G
Thanks for the reply. Hopefully some more will reply.
I upgraded my VK810 (Verizon) and I am not very happy with it. The battery life is similar to kitkat during normal use, but it is terrible at idle - burns 1.5%/hour overnight. It lags pretty regularly, sometimes even on the pin unlock screen for a few 5-10 seconds in the middle of entering.
I have done a full factory reset and set it up from scratch, which didn't improve the performance.
I am considering a flash of KK or even going back to JB. 4.2.2 was the most stable and bug-free version, in my opinion. I am reluctant to flash it, because it's a work tablet and I'd rather not risk bricking it. The only real reason I upgraded to LP was for the proper handling of trim on encrypted devices.
(I am not usually one to bash new releases. My Sony Z1c is incredible with LP, though it needed a factory reset to get there.)
rjkmadison said:
I upgraded my VK810 (Verizon) and I am not very happy with it. The battery life is similar to kitkat during normal use, but it is terrible at idle - burns 1.5%/hour overnight. It lags pretty regularly, sometimes even on the pin unlock screen for a few 5-10 seconds in the middle of entering.
I have done a full factory reset and set it up from scratch, which didn't improve the performance.
I am considering a flash of KK or even going back to JB. 4.2.2 was the most stable and bug-free version, in my opinion. I am reluctant to flash it, because it's a work tablet and I'd rather not risk bricking it. The only real reason I upgraded to LP was for the proper handling of trim on encrypted devices.
(I am not usually one to bash new releases. My Sony Z1c is incredible with LP, though it needed a factory reset to get there.)
Click to expand...
Click to collapse
Same here. Upgraded and not very happy with it. Has more issues connecting to hotspots in my house (issues I didn't have with KK) and it lags, a lot. Some things are certainly better, but I don't think it's any faster - if anything, just the opposite. Is anyone else having the lagging issues? I find it mostly when I'm playing games or doing things that tax the processor.
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.
I bought this phone only as a spare phone while my main phone is in repair.
Now I managed to install Lineage OS on it but it runs like molasses , very slow and sluggish.
I get that this phone is very old but I had a Nexus 5 in the past which has the same processor , it was much faster .
Is it only because of the higher resolution ? Or does it struggle with Marshmallow?
Can someone recommend a faster rom? It does not matter which Android version , I just want to use the phone without waiting minutes after a touch input until something happens.
@zsajak: such delays aren't caused by ROM and there's no fastest ROM. So if you're on MM-stock, deactivate/remove some unneeded apps or services. I'm happy with AospExtended 8.1, because I prefer slim AOSP, Oreo features and actual security updates. For me fast, stable and battery friendly.
I haven't been able to update my phone to the latest security update (April , 2022) it was 1051.54 MB
I believe I missed one ui 4.1 by not downloading it right away and now with Further security Updates I might have this issue
It's just an opinion I don't know what went wrong with my phone update
How can I manually Update my phone to one ui 4.1?
Rule #1 if your firmware is fast, stable and fulfilling its mission, let it be!
Upgrades can and do break things, you can upgrade at anytime but many times you can't do a rollback.
I have 2 stock N10+'s, one running on Android 10* and this one running on Pie. Its current load will be 2 yo this June, still snappy fast, very stable with minimal maintenance.
Security is not an issue.
*came loaded with 10 otherwise it still be on Pie
blackhawk said:
Rule #1 if your firmware is fast, stable and fulfilling its mission, let it be!
Upgrades can and do break things, you can upgrade at anytime but many times you can't do a rollback.
I have 2 stock N10+'s, one running on Android 10* and this one running on Pie. Its current load will be 2 yo this June, still snappy fast, very stable with minimal maintenance.
Security is not an issue.
*came loaded with 10 otherwise it still be on Pie
Click to expand...
Click to collapse
Thank you
I'll keep that in mind
mahdimllt said:
Thank you
I'll keep that in mind
Click to expand...
Click to collapse
Check the Samsung forums, Reddit, etc and see how others who upgraded are doing. Ignore the glowing reviews from the mainstream reviewers, just more fake news.
In Android 12 cpu cycle sucking scoped storage is fully active. As far as I can tell there's no way to tone down it's annoying behaviors much or its running in the background as it's a core feature.
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.