Related
I have flashed many Roms over the last year, Jedi Roms, Infamous Roms, Stock, and most recently Rushing's Shadow Rom. I have stuck to only Touchwiz based Roms since I need WiFi Calling to use my cell phone in my apartment.
The one thing I noticed every time I flashed is that the phone would get significantly slower after I rebooted the phone the first time after I installed a bunch of apps. (Not after the first one I do after the phone has resynch'ed contacts and stuff from google) Additionally, after a couple months the phone would get so slow that I would reflash a new Rom (generally, by this time a new version, but if a new version is not available, I usually switch Roms)
The apps I usually download include:
Google - YouTube, Maps
T-Mobile -Visual Voicemail
Media - Pulse, BeyondPod, a music player
Root stuff - Titanium, Rom toolbox, ES file explorer, etc.
Popular apps - Facebook, twitter, ebay, bank of america, etc.
Are any of these apps known to degrade the performance of your phone over time? Is there a way to diagnose which of these apps are running and when?
A second theory I have is that something on my SD card is either corrupt or not getting wiped properly. Then, these corrupt sectors/files cause performance to decrease over time? Has anybody heard of anything like this? Are there any utilities out there to look for corrupt file. Can anyone reccomend a SD cleaning app that might help if this is the case?
A third theory is that these customized Roms aren't as stable as they are thought to be. I don't believe this is the case since the developers on this forum are much smarter than me, and thoroughly test their roms. Additionally, I have seen this happen with Stock rooted also, which also discounts this theory.
Most of this is spit-balling so that people can see my symptoms (if you had similar symptoms, please share troubleshooting steps and resolution) as well as maybe trigger an idea in someone that has an easy fix to my issue. I like this phone a lot and I don't want to buy a new phone just to avoid these issues. I think this phone is still capable of handling the workload of a 2013 smartphone.
Please let me know any tests/logs that would help you help me solve this problem.
((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
benhofb said:
((if this is in the wrong place or has been covered before, I apologize...))
Hello all.
I just became the new owner of a family member's Samsung Galaxy S3 (AT&T). Already owning and tinkering with two xperia Ion's I wanted to have a little more freedom and experience Kitkat on the GS3.
I had no experience in unlocked bootloaders and all that, so I figured that I would let the Cyanogenmod Auto-Installer do the work for me and install CM11 on my device.
It worked great initially! No problems whatsoever aside from minor glitches here and there. As soon as I started installing some more apps and Xposed modules, I noticed that things were getting odd.
Eventually, my phone wouldn't connect to google's play services whatsoever. Despite countless resets of the phone itself and my modem/router, nothing seemed to help. Flushing the cache and dalvik didn't help either, nor did a factory reset. The issue kept coming back.
Thinking that perhaps another rom wouldn't have the problem, I installed C-Rom (which was based on 4.4.4 KK). It ran BEAUTIFULLY! It is sure one hell of a rom. But then, not too long after I had everything installed and running the way I wanted it to, it had the same errors as before.
I don't know how to explain the error other than the phone just generally messing up. I don't recall it ever having those issues on stock, but then again, it wasn't my phone on stock, and the first thing I did upon receiving it was put a custom rom on it.
But the error can only be explained as a general f***-up of the entire OS. Commands run brutally slow (I will launch the flashlight and it wont turn on until seconds, even minutes later. Alternatively, text messages take eons to send and receive, which I am positive is not an error on the AT&T side of things). Then, whenever I try to download or install an app from the play store, the application will download partially and then stall for what feels like eons. Some of the applications just stop there, and some I will find installed on the device some 30 minutes later. Not to mention that the signal icons on the quick setting tiles are all turned orange for some bizarre reason. Another bizarre issue is that no matter what, I can never launch the terminal to execute an htop, logcat, or anything! The terminal just stalls and eventually crashes, while it worked fine before.
I've checked online for errors similar to this, but haven't found anything that has helped the phone. Anyone out there who is willing to give this a crack or just point me in the right direction?
Thanks in advance.
Click to expand...
Click to collapse
It sounds like you're the modules you're installing are crashing your system. I'd suggest you do a clean flash of w/e rom you wanna rush (you seem to like C-rom) and run it clean for a few days. You can install apps and such but don't restore system apps and don't install modules.
If it runs fine after a few days, you can cherry-pick the modules you wanna use (make sure they're made for the sammy phones). Install one or two, test for a couple days and so on. You'll eventually find which one is messing with your system (if that's actually what's causing the problems).
All seems to be well now. I've isolated the problematic app after slowly restoring all my app data one at a time. I have since moved to a different rom (SOKP) and everything is going running smoothly! Surprisingly, it wasn't Xposed causing the issue, but a market app that displays system info similar to conky on Linux computers. Once I installed it, the system just crapped out. Signals dropped, the terminal froze, and none of my apps seemed to work properly. But once I uninstalled the app and reset my phone, all was well.
Thanks for pointing me in the right direction!
Well, the story goes:
My wife´s SGH-i474 (AT&T) had 4.1.2 installed, crappy reception, launcher buggy (it created more desktops everytime she wanted to delete one), and overall the phone felt laggy. She plays just 3 games, Farmville 2 CS, Candy Crush and Clash of Clans (she´s actually pretty good this one). Not too long ago, since the phone was only rooted to install greenify and link2sd to freeze the bloatware, she found out that it was possible to update the phone to a newer release; and I saw that there was an official OTA to 4.4.2, but since we are overseas, the stock update won´t go (it said that the phone was updated).
I dived into google and I saw that here on xda there was a method to get it into 4.4.2. And me, being the android guy and wanted to get lucky I tried it and succedded, but with one detail...
You see, I mentioned the games for a particular reason, 2 ouf of 3 work, Farmville for some reason doesn´t load (it gets to the loading screen and stays there at 0%). I left it overnight, with the option of leaving the screen on while charging, so that the phone won´t "sleep" to see if the game need to download a file and it was taking a long time, but no, 10 hours later it was still at 0%.
After that, I decided to install Logcat to see what was going on while the game at launch time. Surpringsinly, logcat was unable to save the log to the "sdcard". , another dive into google revealed that there was indeed a bug on the sdcard permissions (never knew that this kind of thing would happen to the gigantic Google, OMG ), and there were several fixes available, which I tried, even manually (just to see that the apps did indeed what they advertised, but to be true, the stock rom that I used had this fix already installed, thank you Mr even... or who ever went into the trouble of making all those files and instructions that helped me get into 4.4.2, I just don´t recall the nickname, but I do remember he has a beard )
Back to the point, I find it odd, that logcat was unable to write to the sdcard, and more odd that just a game was unable to work, because it worked before the update, but logcat doesn´t show anything related to "permission denied" to the Zynga app, nor to logcat itself when it wanted to write to the sdcard.
Since I am just a poweruser, I already wiped to stock and nothing changed, I tried another logcat application with the same result, so what I believe is that maybe the apps have something wrong, because I didn´t find anyone complaining about the stock rooted rom that I used. Besides that it was stock, and just rooted, I just wanted to know if anyone happened to have this problem and if they were able to fix it or have a workaround it.
Just to clarify, the phone works perfectly, and all the 51 apps that has installed (yep, she´s kinda a tech girl herself) work, except FV (which won´t go past 0% at the loading screen) and those to logcat applications that I used. (Catlog and Logviewer Lite, which can´t save logs to the sdcard), even the camera works and saved pics to the sdcard withouth problem (one of the things I saw reading is that maybe the camera would stop working but nope, just fine).
If you have any ideas, please, express yourself.
The kitkat update for google did in fact make it to where nothing could be written to sd. Google trying to get rid of sd cards for some stupid reason. Anyway, if the phone is rooted, try the xposed app with the external sd modules. Took care of my problems with that, not on my S3 because enewman17 is so damn awesome with his S3Rx rom that he took care of that, but on my Note 10.1 and Tab 4 fixed it right up
I see, could you be more specific about the xposed app, the name in fact, a search rendered quite a few, an I am not native english speaker.
I mustbe cursed hehe, I found the "app", is a framework, but guess what? I am unable to install because it is unable to write to the sdcard hehehe, I will give a try to the custom rom.
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
XDADoog said:
To mr Enewman, you sir, you deserve a cold beer, my wife is now happy, just a little glitch with the google keyboard at the first boot but after that excellent.
Click to expand...
Click to collapse
It is an outstanding ROM for sure. Glad it's working.
i want to downgrade my htc one m8 from lolipop to kitkat 4 again. can you please help me i dont like this os . kitkat was perfect
mohamedabdallah2010 said:
i want to downgrade my htc one m8 from lolipop to kitkat 4 again. can you please help me i dont like this os . kitkat was perfect
Click to expand...
Click to collapse
You need to unlock/s-off to get 100% downgrade, or, you can unlock bootloader, flash twrp, and install a kittkatt custom rom.
thanks
thanks but i was on iphone i dont know whats all this. can you please tell me steps
It's not a case of following some steps. What you want is very technical and not for someone with no prior knowledge of rooting Android phones.
What don't you like about lollipop? It's no different, visually, to Kit Kat on the M8
slower
its slower and more battery consume and i dont like the notifications
mohamedabdallah2010 said:
its slower and more battery consume and i dont like the notifications
Click to expand...
Click to collapse
Sounds like you update by OTA. In which case, updating by OTA and keeping user data is often the root of random issues. Try backing up any important personal data and doing a factory reset (to wipe user data - and NO this will not return you to a former OS version as some folks mistakenly believe). Lollipop isn't slower than KitKat in any significant way that I've noticed. You're probably seeing bugs due to conflicts with pre-existing user data (settings and apps).
Battery consumption may be due to the new radio. But it might also be a bug caused by pre-existing data, or you may just need to do a full charge-discharge cycle to properly calibrate the battery meter (mandatory after a major OS update).
Also, OTAs contain important security updates. So it should be considered that you won't have these if you "downgrade".
Something to consider - do you use Facebook Messenger? Turns out since the new Google Play services it's been eating battery like no one's business! Read the reviews on the Play Store for proof but it does seem to be linked to Lollipop and (for me) Google Play services 6.7.74
There's bugs even in OTA updates from 4.4.4 seems most if not all manufacturers having problems and they can really screw your handset up - apps consuming battery (not just Play Store) bad mobile internet, losing Wi-Fi , corrupting system, removing apps, deleting SDCard data.
Probably due to crap OTA "patched" system updates. Myself, once handset is back from warranty repair (12 days use, 4 of which OTA stuffed it up) I'll not use OTA again that's for sure.
Bashing away at my HTC Desire C
Since I've removed Facebook Messenger my phone is back to normal, battery life as it was on 4.4.4 and everything is OK so I'm happy (don't use FB Messenger enough to warrant having it!)
thanks
thank you all about reply's. i searched google and i see all people talking about battery and fb messanger on all phones. so you recommend to me to stay on lollipop ? but i dont like really this notification control
So I'm not alone in facing issues with Lollipop
When I update, I was getting terrible battery life so I performed a hard reset from bootloader.
Now almost everything is fine but Google Play Services, more specifically "Mobile radio active" has been eating into the standby time, not like before but still bad, goes on upto 3 hours. "Keep awake" also goes on upto 2 hours.
Any fix or suggestions would be helpful. I don't use Messenger and Facebook, as they were the major battery eaters.
Rather than keeping an eye on pointless stats, how long does your battery actually last? I honestly think people are making up issues. Now, the FB Messenger HAS been eating battery but once I removed that my battery life went back to normal
My battery was better but mobile data was screwed, WiFi only showing my router and no others, never used facebook (so it's not that app alone) blinkfeed consumed 46% of battery use. All on 4.4.4 update so to say people are making a big issue of it, yeah damn right, it was 100% better without the update!
Bashing away at my HTC Desire C
But that's your individual issue between your phone/router/apps/etc. I've had zero issues with Lollipop bar this one with FB Messenger since the new Google Play services so I uninstalled it and now I'm back to running perfectly so clearly the OTA update isn't the issue
Have you done a factory reset to clear out anything left over from 4.4.4? It's always recommended to do so, as annoying as it is, when moving to a new version of Android. I set my phone up from scratch and have no problems with 5.0.1
I have done... Update still goosed it, so maybe you having no problems it's you that's the lucky one! That's why it's back at HTC!
If these patched updates were any good nobody would have issues!
Makes more sense than... It's just your issue!
Bashing away at my HTC Desire C
---------- Post added at 07:47 PM ---------- Previous post was at 07:31 PM ----------
Uninstalling facebook so obviously not stock so the fact you're flashing quite possibly other ROM's negates your lack of problems. Fully stock phone updated worked worse than what I'm using now. Full stop.
There is also the fact I was told by my phone supplier that problems with updates are industry wide since 4.4.4 and if all the update are, are patches, then it's not going to be a quick fix, like it's known there's variations in the handsets with the carriers.
Bashing away at my HTC Desire C
If there were issues they'd pull the update and there'd be more media coverage. I've not flashed anything on my phone, I'm 100% stock and I've not rooted a phone in well over a year. My phone is running the latest Sense build released and have no issues. Now I only use about ten third party apps so it could just be that that means I'm not having issues. Or it could be I close all apps once I've finished with them. I don't know. But I don't think there's anything wrong with what HTC have released
Doesn't explain the problems people are having, my handset was working 100% A-ok the update which I never applied or accepted stuffed it, maybe it's not in the media because it's not affecting, like yourself, people who don't use it as heavily as others, like I said I've been told the industry is having problems with them, maybe the lucky ones less or not affected are low use.
Bashing away at my HTC Desire C
Who told you the industry is having issues, though? I've not heard of Samsung of LG owners having issues, nor those with Nexus devices (well, not huge numbers of people anyway!), so I don't think Lollipop as a whole is the issue at all. Now, I'm not saying people don't have issues, but I think those issues are down to individual setups (apps installed, usage, even the components used in that particular handset). Perhaps I am lucky, but if I am I've been lucky with every phone I've ever owned
thank you all . here is what i did. i did a hard reset and restored my data then installed whatsapp only and now my battery is back to be very good as it was on kitkat and better. i will install every single app one a day to check which one eating the battery. and i will update you with details. and i see much people talking about this issue on other sites and other handsets.thanks
For me battery works good sometimes and then suddenly starts losing charge during standby, so I check and find Mobile Radio Active has been eating away the battery, while this was not the case with 4.4.4. Even with FB and Messenger installed I didn't have any problems but now I do. I uninstalled both so battery is better than what it was with them but still I lose charge mysteriously in standby randomly.
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Agree with edor, Android flash tool, flash both slots, start all over
roirraW edor ehT said:
Remind me since I don't recall if it was brought up in your other thread about the issue, did you try Official Google Android Flash Tool yet?
Click to expand...
Click to collapse
I have not tried this. What would this be used for?
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
MarkAnthony121 said:
I have not tried this. What would this be used for?
Click to expand...
Click to collapse
To wipe the phone and start back fresh.
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Click to expand...
Click to collapse
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
ne0ns4l4m4nder said:
Agree with edor, Android flash tool, flash both slots, start all over
Click to expand...
Click to collapse
Not sure what that means sorry, can you elaborate?
roirraW edor ehT said:
To wipe the phone and start back fresh.
Just that. To start back fully fresh. Then if you do that take my advice from the other thread, don't restore backups from Google or anywhere, and initially only install your most critical apps. Once you determine you're not having the problem, install some more. Verify, repeat.
Click to expand...
Click to collapse
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
MarkAnthony121 said:
Not sure what that means sorry, can you elaborate?
Yes but I don't understand what "flash both slots" means. And wouldn't I get the same result by simply doing a factory reset and then proceeding with the method of installing everything manually and not from a backup? Why use the google flash tool vs factory reset?
Click to expand...
Click to collapse
At this point, that's more information than you really need to know to try to fix your phone. I don't want to overcomplicate things. You can look at Google search results for "Pixel flash both slots" if you really want to go down that road right now.
Spoiler: Some of the details you're asking for, but you don't need right now
In short, starting with the Pixel 1 in 2016, they have two copies of almost everything (except only one copy of user data). On a Pixel, and another phone that employs dual slots, when you receive an OTA update, it updates the copy of Android that you're not currently running, then reboots into the one it just updated, and once rebooted it goes ahead and updates the copy that you're no longer running, so they're both now updated.
Not all OEMs use the dual partition strategy, which is frustrating. When I briefly had the Note 10+ before the P6P came out, I was amazed that Samsung still hasn't adopted the method. It beats the old style OTA method that Samsung still uses to this day as far as I know where it takes 15-20 minutes or more to run the update while your phone is unable to be used at all, and then even when it boots up the next time Android has to finish the job "optimizing" your apps for the new update. Dual partitions for Android save a lot of time when updating the phone.
In some manual flashing processes, you end up with one slot with a different copy of what you have in the other slot - and you don't want that. The slots are referred to as Slot A and Slot B.
I can go further into detail but you don't really need that to fix your phone.
All you need to know right now is Official Google Android Flash Tool.
If you haven't already tried the factory reset, et cetera, which we had recommended to you at least once in the other thread, then by all means, you can try that. But if you're going to try that, you might as well just use the Official Google Android Flash Tool and ensure you are 100% stock. Official Google Android Flash Tool has fixed a good dozen or two folks' issues (I haven't been keeping count) in these forums in the past 2+ months.
So if the factory resetting doesn't solve things then you'll still have to try Official Google Android Flash Tool to be closer to sure that you tried everything that you could. We had already suggested the Factory Reset to you in the other thread. Since you created a new thread, I figured you might be looking for information you hadn't been given yet.
So the short answer is because Official Google Android Flash Tool will do an even more complete job of putting your phone back to 100% stock, with a lot less doubt than a simple factory reset. Sure, a factory reset, in theory, should get you the same thing, but there are all sorts of circumstances where a factory reset won't. Something is wrong with your phone and we don't know what it is.
There's the Factory Reset idea and then there's the Official Google Android Flash Tool idea - either coupled with the staggered manual installation of apps until you narrow down if it was a particular app causing the issue. It doesn't matter which one you choose to try first. If you try just a Factory Reset, and things still go haywire, then you'll still have to try Official Google Android Flash Tool after that. It's your choice, now pick one and go forth and hopefully reboot no more.
Also, I wasn't going to mention this but I will now. Forums generally discourage users from creating multiple threads about the same issue or posting about the same issue in multiple threads. You can always update the OP (opening/first post) if you need to, and give an update as a reply to your existing thread.
MarkAnthony121 said:
So I posted about this previously but here's more info and a clearer summary
The Issue:
Phone randomly reboots about an average of once per day. Screen freezes, goes black, comes back on for 3 seconds still frozen, then proceeds to reboot. I've kept track and 100% of of the time this seems to happen when I'm typing. Initially I thought it was Textra, but it has happened in Snapchat, and Twitch whenever the google keyboard is up. Google sent a replacement phone and the issues persists, and I find it hard to believe that both phone would have the exact same hardware issue. Furthermore it very much seems like a software issue considering it ONLY happens when the google keyboard is up.
My hope is that someone might have encountered this and has a simple solution although I doubt it. Unfortunately since I don't have another phone, I have to wait to obtain one before I do a safe mode test. And even if I do it's not realistic for me to test it that way because I'd have to spend hours typing away just to try to get the issue to occur (since it's not frequent like every 5 minutes).
I'm suspecting some data or a setting is getting transferred over from my previous backup that's affecting google keyboard or something of the sort. My next step will be a factory reset, and then reinstalling everything bit by bit manually. Of course I have to link my google account, but I won't have it automatically restore the backup. If that doesn't help then I'm at a loss. At that point I'd probably pick up a cheap Pixel 2XL as my daily, and use my P6Pro in safe mode as much as I can to try to trigger the issue I guess?
The Phone:
Pixel 6 Pro
Not Rooted
November 5 Update
Set up done using my google account to restore all apps and settings, not cable
Click to expand...
Click to collapse
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
For what it's worth, I've been using GBoard for 5+ years and have never had a problem.
96carboard said:
I've heard of freezing problems from others related to gboard. This would indeed appear to be a software flaw. I've never really used gboard since the first step for me was google-free AOSP, then put in my sim card and start using it (I don't like spyware).
Simplest solution for you would likely be to try a different soft keyboard. Personally, I would suggest finding one on f-droid rather than play store because open source.
Click to expand...
Click to collapse
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
MarkAnthony121 said:
I used to root back in the day and use a custom ROM. If I do that there's no automatic updates right? Have to reload a new ROM for updates?
Click to expand...
Click to collapse
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
roirraW edor ehT said:
Depends on the ROM. I believe GrapheneOS has OTA updates. I know some others over the years have had that, too. Certainly not most custom ROMs but some.
Click to expand...
Click to collapse
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions. Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much? It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward. And second question, will the flash tool give me the option to clear both slots ?
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
MarkAnthony121 said:
Thanks for all the help. (sorry for posting twice, I tried to delete the other) And I did appreciate the extra info so that I understood WHY I needed to do it this way and how it all functions.
Click to expand...
Click to collapse
You're very welcome!
MarkAnthony121 said:
Two final questions. On modern phones like this one, does running a custom rom really improve battery/performance much?
Click to expand...
Click to collapse
In my opinion, no, but the object of some ROMs (like GrapheneOS) are more geared towards very much increased security and avoidance of all the Google data-collecting that goes on with everything Google, although you can use some or most Google apps with GrapheneOS if you choose.
I've never actually tried GrapheneOS, though - I've only kept up with the two threads about them because I was curious about it. To me, starting with my first Pixel (I never owned a Nexus device), I liked stock Android way better for my purposes.
But just as for a lot of phone-related subjects, the answer to this question is very subjective. What's right for me isn't right for everyone. Everyone's needs are different. The only way of knowing for sure is to try it. You might try something and very quickly say "to heck with that, I'm going back", or you might say "oh, I like this loads better". I'm not a betting man unless something is a near 100% chance, so it's really a toss-up whether you would like a different ROM or not.
Also, how I handle my battery works great for me - but it wouldn't for everyone. I don't charge the phone until it gets down to 25%, and I try not to let it get any lower than 25%. I only charge the phone up to 75% when I can. I never charge overnight, and I never quick charge. That 50% range of battery still lasts me about 24 hours. My Pixel 1 battery is in great shape because of this habit. My wife's, on the other hand, since she didn't do this - her battery on her old Pixel 1 is relatively shot.
MarkAnthony121 said:
It's already pretty snappy for me, so I feel if I don't care about customizability it's probably not worth the effort for minimal reward.
Click to expand...
Click to collapse
Sounds as if you already have made up your mind to me. I mean, that's how I feel, and I like using Google's services for the most part. I'm more a function over form person. While I don't want something downright fugly, I really don't care what things look like - only how they do what I want them to do. Yet again, "how they do what I want them to do" is very subjective. The Samsung Galaxy Note 10+ didn't do what my wife and I wanted it to do, but we were both spoiled on the Pixel 1 before that. We don't regret our choice to go back to Pixel via the 6 Pro. For others, the Samsung phones are what they need.
MarkAnthony121 said:
And second question, will the flash tool give me the option to clear both slots ?
Click to expand...
Click to collapse
You don't want to "clear" both slots, you want to flash both slots. In answer to your question, I don't think you'll have a choice via the site (or offline flashing the full factory image). In other words, both slots are going to get flashed whether you like it or not. You would have to go to extra efforts to *not* flash both slots. Hence yet another reason why you don't have to worry about that aspect.
Google's official methods would never flash only one slot by default. That would be just plain idiotic of them.
Before you ask, the reason I recommend the site rather than offline flashing of the full factory image is:
It's more user-friendly.
It has solved problems when manually flashing the full factory image has not for some others with particular problems.
MarkAnthony121 said:
Oh and third, is it ok to link my google account, (to get my contacts and such) as long as I'm not restoring any backups from it?
Click to expand...
Click to collapse
Yes, absolutely, although in some cases I've recommended going completely fresh and not even doing that, at least before testing long enough to see if you have the issue. You certainly could go without putting your Google account in, etc, but I don't feel that's warranted at this point. The only time I think you should do that, in this case, is if you do it the other way (with your Google account), and you still have the same problem right away (without installing any additional apps).
Just remember don't install any additional apps to start with, long enough to be sure that the problem isn't happening. I know it's a painful process - I've done this before on several devices for different reasons. Usually, the cause of issues becomes evident but it's possible it won't be completely obvious.
FYI, just putting your Google account in will, I believe, possibly still automatically restore your phone's most basic settings but I could be wrong about that. You could always try it without your account at first, use the phone in it's limited state for long enough to know there's no problem, and only then put your Google account in.