hi, I got the prompt to update my phone.
I'm hesitant at the moment. I wish to know if any of you experienced lags, slowdowns or other problems in the new version of Android 12? Should I stick with 11?
I have installed it since yesterday and for now it works perfectly with no lags.
Software even feels a little bit faster
I've had mine reboot unexpectedly a couple of times. Haven't found the conditions causing it yet.
You guys should try debloating, i have an optimization guide thread here:
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com
Related
My sony z3 has gone back to sony for repair, so I got my i9250 out as a spare. It was installed with cm13, but as it hadn't been used for a while I updated to the latest nightly. all was good but the camera kept crashing, so i wiped everything, flashed cm13 and pico g-apps, but when it restarts google play, won't start. (nano is too big apparently??)
So i tried using cm12 and the relevant g-apps and got the same result
then i tried http://forum.xda-developers.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 and it just boot loops on the the 7.1 & kk versons
It will install cm13 & 12 and start no problems, but i need all my google contacts and stuff
Any suggestions??
jonallwright said:
My sony z3 has gone back to sony for repair, so I got my i9250 out as a spare. It was installed with cm13, but as it hadn't been used for a while I updated to the latest nightly. all was good but the camera kept crashing, so i wiped everything, flashed cm13 and pico g-apps, but when it restarts google play, won't start. (nano is too big apparently??)
So i tried using cm12 and the relevant g-apps and got the same result
then i tried http://forum.xda-developers.com/galaxy-nexus/development/rom-omap4-aosp-project-t3334574 and it just boot loops on the the 7.1 & kk versons
It will install cm13 & 12 and start no problems, but i need all my google contacts and stuff
Any suggestions??
Click to expand...
Click to collapse
Did you use Gapps Pico...? It's smallest...
Day by day letest changes makes ROM bigger, and then our phone doesn't have enough space for Gapps... That is reason....
While flashing, keep eye on Log of Custom Recovery, starting of flash checks space on device first and gives result, then see if Gapps got flashed or not...
Pico, Pico, Pico!
__Madddy said:
Did you use Gapps Pico...? It's smallest...
Day by day letest changes makes ROM bigger, and then our phone doesn't have enough space for Gapps... That is reason....
While flashing, keep eye on Log of Custom Recovery, starting of flash checks space on device first and gives result, then see if Gapps got flashed or not...
Click to expand...
Click to collapse
You can't use anything bigger than pico since Marshmallow (and I don't recommend anything bigger than pico, period). I have never had success with anything nano (the largest I have ever tried - and that was only with CM 13); however, pico has never done me wrong (I moved to Unlegacy Android - currently 7.1.0 - for performance issues that it fixes compared to CM13; yes, for some rather odd reason, Nougat performs better than MM on this device).
PGHammer said:
You can't use anything bigger than pico since Marshmallow (and I don't recommend anything bigger than pico, period). I have never had success with anything nano (the largest I have ever tried - and that was only with CM 13); however, pico has never done me wrong (I moved to Unlegacy Android - currently 7.1.0 - for performance issues that it fixes compared to CM13; yes, for some rather odd reason, Nougat performs better than MM on this device).
Click to expand...
Click to collapse
That's right Pico is the only option from MM and upper. It's very usefull the performance tip you give about Nougat.
I have installed last MM build from:
builds.unlegacy-android.cf/aosp-6.0/tuna (2017/01/09)
Everything goes well (even GPS), it's fast and reliable. But I have a doubt, should I wait till next Nougat (with GPS functional) or should I stay in MM with everything functional and good performance?
Is N release better in any aspect than MM?, obviously I miss the new improvements in Android N that have developed Google, but I mean general performance and hardware related issues.
I prefer an older Android release, faster and more stable than the newer one with more issues or slower.
Anybody can tell? Thanks in advance!
yossSP said:
That's right Pico is the only option from MM and upper. It's very usefull the performance tip you give about Nougat.
I have installed last MM build from:
builds.unlegacy-android.cf/aosp-6.0/tuna (2017/01/09)
Everything goes well (even GPS), it's fast and reliable. But I have a doubt, should I wait till next Nougat (with GPS functional) or should I stay in MM with everything functional and good performance?
Is N release better in any aspect than MM?, obviously I miss the new improvements in Android N that have developed Google, but I mean general performance and hardware related issues.
I prefer an older Android release, faster and more stable than the newer one with more issues or slower.
Anybody can tell? Thanks in advance!
Click to expand...
Click to collapse
So far, N has stood that meme on its head (compared to MM, L, KK, and even JB) and it's NOT the first OS for any device to have done so..
It's a meme that dates back to MS-DOS (that's right - it pre-dates Windows of any sort) and it's based on a canard that a newer OS is designed for newer hardware. While it CAN be true, there are reasons why the Galaxy Nexus in particular stands the meme on its head.
1. Basic storage capaciousness. Unlike most devices that succeeded it, the Galaxy Nexus in particular not only does NOT support microSD physically, it also does not lose over half the base storage to its firmware - in fact, PureNexus 7.1.1 - even installed as a pour-over upgrade from Unlegacy AOSP - takes up less than ten percent of the GNex storage space; all of 3 GB at worst. That means that more of the basic storage can be used for ZRAM - the Android equivalent of virtual memory in Linux distributions, Windows, or other modern OSes. More modern phone designs support microSD - which has itself grown in capacity as a storage mechanism; however, you pay a price in loss of first-tier storage capacity - every S-series Samsung phone proves it - how do ANY of them compare to the GNex in non-SD-based storage after firmware loadout? Also, you can't use microSD for ZRAM; if you need ZRAM, you must use free basic storage for it - and most modern Android devices simply don't have it to spare. (It's not just a phone problem; in fact, my Lenovo A7-30F - which supports microSD and is running Lollipop right now - illustrates the point rather painfully, despite being a tablet - it is also a MediaTek big.LITTLE "4+4" design that is hamstrung by the lack of ZRAM. Being able to throw more cores at the problem won't help when the processor is not the biggest problem.)
2. CPU vs. ZRAM - Performance of a given application on a given phone is NOT always determined by processor power; the same is, in fact true on OSes other than Android. Still , what happens merely in Android as ZRAM availability - which IS a secondary function of basic storage capacity - decreases? (This is whether the device supports microSD or not.) Does or does NOT performance decrease as basic storage fills up?
3. Not every app needs more CPU or GPU. Out of everything I've thrown at the PureNexus/GNex combo, only two apps (and one game) explicitly require Marshmallow or better - and in all three cases, they were designed for Marshmallow OR Nougat in the first place.
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
draccas said:
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
Click to expand...
Click to collapse
When you flash a new ROM are you restoring your apps/data from anything like titanium backup , swift or google etc , if not which gapps are you using it sounds to me like a software issue rather than ram ...
draccas said:
Hi all,
Since a few days I have troubles with my OnePlus 3 (bought two years ago and never have any problems).
It has random "soft" reboots (I don't see the OnePlus bios but only the ROM boot animation) or applications crashs.
I don't need to reenter my PIN code after those reboots, and apps that crashed are also randomly (sometime works, sometime not).
First time I saw the problem, I was on AOSP Extended ROM. Thinking that was a bug with the ROM, I try 3 others: LineageOS / Ressurection Remix / Omni but unfortunately the issue still here.
I also try various OnePlus firmware (OpenBeta29 and the lastest stable) but I no see differences.
So I suspect a material issue (maybe the RAM)?
But I'm not an expert in Android / device.
Someone already saw this problem?
If anybody can help me, thanks a lot. I love my OnePlus and I don't want to change it for the moment.
Click to expand...
Click to collapse
Without the proper logs you are sol.
Thanks for your responses.
I always do a "clean" flash in formatting all parititions.
I do not use backup/restore tools.
And I do not use Gapps nor microg. Only free apps founded on F-Droid repository.
... old school.
Concerning logs, I check on AOSP Extended and I saw a lot of "low memorry killer" or "no such memory" - but when I look the RAM, only 3.4 Gb was used on 6.
I'll try to get clean logs on my fresh install - but as I say the smartphone reboot in chain.
draccas said:
Thanks for your responses.
I always do a "clean" flash in formatting all parititions.
I do not use backup/restore tools.
And I do not use Gapps nor microg. Only free apps founded on F-Droid repository.
... old school.
Concerning logs, I check on AOSP Extended and I saw a lot of "low memorry killer" or "no such memory" - but when I look the RAM, only 3.4 Gb was used on 6.
I'll try to get clean logs on my fresh install - but as I say the smartphone reboot in chain.
Click to expand...
Click to collapse
Then I would relook at the rom you are running. And just a heads up. You will run into issues as there are core parts of android that run subpar without atleast micro g.
Are you sure about that? Is it not possible to use a pure Android without any gapps nor microg? I always done that before, and I never have issues. Howerver I try with AOSP Extended and microg: same trouble. Random reboots (sometimes 10 in 5 minutes, other times no reboots while some hours)...
So I'll try a full reset with official OxygenOS system and recovery. If the issue continue, I'll try to get proper logs.
Reverting to OxygenOS seems to resolve the problem. But I do not understand why...
I have been hanging around XDA for past 1 week or so, and have spent numerous hours in understanding Android/rooting/ROMs etc. As a software engineer, i had the basic background, to catch up on Android platform, which is new to me. Having covered everything here from "Intro to XDA/beginners" to Phone specific details, here is some questions, as i tread carefully into Android tinkering.
I have held onto an aging Tmobile S4, trying to avoid buying a new phone. Still running stock m919uvsfqa1 baseband (OTA early 2017). This was ok, since I do not play games / stream video / run social media apps etc. After 4 years of running acceptably, this phone started misbehaving in 2017. No hardware or software changes other than the factory reset to wipe data/cache (in last few days). Restored all apps/data, using Samsung smartswitch (I will write a guide on this later, as a thank you & give back, to XDA community). Phone seems to be revived after this factor reset/restore. I have 3 questions :
If i am only interested in stability / integrity / functionality in phone, should i stick to stock kitkat 4.4.4 (OR) should i risk it and upgrade to Oreo based LineageOS 15.1 (which i found on xda as End-of-Life) ?? (OR) any other custom rom recommendations (like marshmallow SlimRom) ? In my limited knowledge in reading various threads on XDA, i find only these two roms mentioned for stability.
In any case, i am considering rooting with CF-Auto-root, to get SuperSU and remove bloat/ads...... Perhaps i can install antivirus apps, since i won't be running the latest security patches available in Oreo (if i run older versions of custom ROM). Would you advise this for a Software engineer, who is newbie to Android ? (OR) simply play it safe and stick to the bloatware/stock ? (Note: I have already gone through guides on "what apps to install after rooting".)
CF-auto-root will stick to stock recovery. Is there any benefit for me in installing TWRP ?
Hello guys!
Any good reliable S21 FE debloater list?
(For snapdragon version)
Share it here please!
Thank you
jbs68 said:
Hello guys!
Any good reliable S21 FE debloater list?
(For snapdragon version)
Share it here please!
Thank you
Click to expand...
Click to collapse
Just follow the ONE UI, optimisation list.
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com
94burns said:
Just follow the ONE UI, optimisation list.
[DISCONTINUED] Samsung Galaxy One UI - Optimization Guide
THIS IS A SUGGESTED CONFIGURATION FOR SAMSUNG DEVICES OUT OF SUPPORT/CLOSED I - RECOMMENDED SETTINGS To Start With - Factory Reset before starting optimisations - Factory Reset after every Major update (One UI/Android) - Remove SIM before first...
forum.xda-developers.com
Click to expand...
Click to collapse
thats not really a debloater, with recent android versions even titanium backum cant uninstall system apps anymore. only freeze them. I remember on Sony devices there were lua's for twro that could do the job
I read that One UI 5.0 is released for S7 Plus in Europe. Lets discuss links and other options on how to flash it.
I am updating right now from Spain
Weirdly, Frija still shows Android 12 as the latest version. Anybody know which CSC I can use to download the latest full version for odin?
EUX shows Android 13
EUX,XEF, DBT, PHE,AUT... for T976B
IdroogI said:
EUX shows Android 13
Click to expand...
Click to collapse
Thank you for this. Flashed it after reading this. Working flawlessly.
For those who have already installed it, can you tell me if all the Good Lock modules are still working? In particular, I'm using the larger 10 x 7 Home Screen grid that's only available in HomeUp. I'd appreciate if someone can check if this still works under OneUI 5.0 on the S7+ ?
mickliq said:
For those who have already installed it, can you tell me if all the Good Lock modules are still working? In particular, I'm using the larger 10 x 7 Home Screen grid that's only available in HomeUp. I'd appreciate if someone can check if this still works under OneUI 5.0 on the S7+ ?
Click to expand...
Click to collapse
All Good Lock modules are updated to One ui 5,You just have to install the update after updating to One UI5, worth the redundancy.
I can concur, updated to One UI 5.0 (Android 13) and all seems uber stable and no loss of functionality.
Just received the update on my S7+ in the US. Installing now.
Still no update for my unlocked Fold4 though...
treoless said:
Just received the update on my S7+ in the US. Installing now.
Still no update for my unlocked Fold4 though...
Click to expand...
Click to collapse
Same, nothing for my ZF4 yet. Not really convinced there's much benefit to OneUI 5.0 on the Tab S7+ so not sure it's such a big deal the ZF4 is laggging a bit.
I installed One UI 5.0 on my regular Tab S7 (11 inch, EUX) and have to admit that I am very dissapointed. Samsung promised way more fluent animations, no annoying start-up lags anymore and an overall improvement in System stability. Non of that happens to be the case. My Tablet feels more laggy, compared to One UI 2.5/3.1.1. Even the Android Easter egg only gets shown on one side instead of full screen, which seems to be bug (No the pictures are not edited)
In my opinion, they rushed this update too fast, so that they can prove the point of releasing updates quicker than ever before now.
I will try out two things this week:
1) Reset the Tablet and see how it performs with 5.0 being freshly, clean installed
2) Downgrade to One UI 3.1, which, for me, was the last update that really changed something noticabely on my Tablet.
I miss those older days (2016-2020 especially), when new Android versions really changed things and introduced cool new stuff. Nowadays, I feel like we're stuck with the same Design and the same features with little to no changes after all.
halloo13 said:
I installed One UI 5.0 on my regular Tab S7 (11 inch, EUX) and have to admit that I am very dissapointed. Samsung promised way more fluent animations, no annoying start-up lags anymore and an overall improvement in System stability. Non of that happens to be the case. My Tablet feels more laggy, compared to One UI 2.5/3.1.1. Even the Android Easter egg only gets shown on one side instead of full screen, which seems to be bug (No the pictures are not edited)
In my opinion, they rushed this update too fast, so that they can prove the point of releasing updates quicker than ever before now.
I will try out two things this week:
1) Reset the Tablet and see how it performs with 5.0 being freshly, clean installed
2) Downgrade to One UI 3.1, which, for me, was the last update that really changed something noticabely on my Tablet.
I miss those older days (2016-2020 especially), when new Android versions really changed things and introduced cool new stuff. Nowadays, I feel like we're stuck with the same Design and the same features with little to no changes after all.
Click to expand...
Click to collapse
Android 12 was a big one. But yeah, I also noticed the Easter egg. It doesn’t even work.
Hi all,
I found myself opening a lot of tabs on XDA to figure out on how to upgrade my Tab S7+ Wifi - SM-T970 to newer Firmware versions while retaining Root (magisk). This is why I made myself a short guide. Then I decided to share it with you and the short guide went from short to medium sized.
I hope it helps. (The resources/drivers/programs I used can be found at the bottom of this comment. (no links, but Google will help you out)
Firmware Upgrade Guide Samsung Galaxy Tab S7+ | SM-T970 | CSC:EUX | while keeping/retaining Magisk Root.
1.Download Latest firmware on PC via Frija (CSC:EUX & Model:SM-T970 for me)
2.Extract ZIP Open extracted directory and delete ZIP.(I like to keep a clean overview, so optional)
3.In the directory you find BL, AP, CP, CSC & HOME_CSC files. If you use the Wifi only version of the Tablet, you can remove the CP file.
This leaves the BL file (should be left untouched), AP file & CSC & HOME_CSC files.
Choose one of the two CSC files to keep.
4.a. Want to Keep your data? Use Home_CSC....tar.md5 file using ODIN, other file can be removed.
4.b. Factory reset? Use other CSC file instead.
5.Move (not copy, but move) AP file (AP......tar.md5) to Tablet and patch whole file in Magisk (I am using the latest Canary Magisk version)
When this is done, move the patched AP file called magisk_patchedsomethingsomething back to the first extracted directory (step 2) AP-file name does not matter.
Connect tablet to PC with USB.
Using Terminal in ADB directory, use " adb devices" to check if PC can find tablet when tablet operates normally. Use command " adb reboot download" to boot the tablet directly into download mode.
Open ODIN (no settings need to be adjusted in ODIN other than selecting the correct files)
In ODIN,
Select AP ---select ---> magisk_patched.#######.tar
Select BL ---> BL_####.tar.md5
Select CSC ---> HOME_CSC_####.tar.md5
OR use CSC_####.tar.md5 if factory reset is required
Click Start. Wait. And enjoy!
Resources used:
-Friji v1.4.4 for downloading latest firmware real fast.
-Minimal ADB Fastboot v1.4.3.exe for minimalistic ADB-installation
-Samsung USB Driver for Mobile Phones (for PC to recognize the tablet in Download mode)
-Odin (I used the latest version v3.14.4)