Related
All,
I had at one point got Wallet to work on my unrooted phone, but over the months, since I changed ROM's so often and I have everything restored via TitaniamBackup, that Wallet seems to be broken.
I tried looking at the links for installing Wallet but nothing works or at least seem confusing the way they word it.
Can someone point me to a installing Wallet for dummies or hit me up with the simple instructions.
Thansk!
What do you mean by broken? Does it give any errors?
First, everything looks like its working, it see's the amount I have and everything, and when I try to make a purchase, nothing happens. System don't recognize the payment.
So I deleted it and want to start fresh.
It's possible that the kiosk you used wasn't working properly. Some places don't maintain their paypass readers very well.
Jeez, didn't think like that. Now I deleted my Wallet for nothing instead of testing it out again.
Racer Of All said:
IMPORTANT! Please read!
While waiting to get my hands on one of these awesome phones I've been reading all I can about it. One thing I ran across in another forum was an issue people were having with the Nexuses & One X's and Google Wallet.
If you do not clear the Google Wallet settings before you do a hard reset/ROM flash, the secure element will be FOREVER BRICKED and you will NOT be able to ever use it for secure purposes such as Google Wallet purchases or future use of the secure element.
For some, this wont be a problem, but if you ever plan or at least want to have the option to use the google wallet, follow these simple steps before doing a hard reset or flashing a new ROM on your phone:
Launch Google Wallet
Hit menu button> Settings> Reset Google Wallet
You are now safe to flash a new ROM or reset your phone, Wallet will be waiting for you on the other side.
Clearing the app data or cache through settings or Titanium WILL NOT WORK! It HAS to be done within the Wallet app. This resets the secure certificate (?) and allows NFC to be used for secure purposes in the future.
---
While I understand the notion of keeping such functionality very secure, Google should have expressed the potential problem. Especially since hard resets are used as a solution when an ordinary user has a problem with their phone.
Frequently Asked Questions
Does this mean if this happens to me I wont be able to use NFC at all?
No. Not at all. NFC will still be functional for non-secure events, like Beam and NFC tag usage. This will only affect secure things, which at the moment is only Wallet.
Is there really no fix?
If you get the "secure element not responding" error, no. Of all the cases the only solution is to get a new phone. The secure element is permanently broken. In the future someone might find a fix, but that sounds unlikely. If you can swap your phone, do it.
How can I prevent this from happening?
If you don't do a lot of flashing, just remember to clear Wallet settings before flashing a new ROM. I would recommend to just leave Wallet cleared if you plan on flashing a lot, you forget once and that will be the end of your secure element.
I get a "Unsupported Device Error" yet Wallet still works, why?
This is a complete different error altogether and as a matter of fact, is not a big deal at all. This only shows up to root users and can easily be ignored -- Wallet will still work.
Why don't we have ROM devs cook in an auto-wiper when installing their ROM?
Only Wallet has the ability to access the phone's secure element, and it will likely be that way for the foreseeable future. A workaround would be to add an option before flashing anything to the recovery itself to ask people if they have cleared Wallet settings.
Wallet is asking for root permissions, should I grant them?
While there are no known repercussions to allowing root, as a general rule of thumb you should never allow root to an application you did not intend to give root access or do not know why it is requiring it. To be on the safe side (and in case something comes up in the future) deny root access to Wallet.
If I never set up Google Wallet will I be fine?
Yes. When you reset Wallet, its restores the secure element and the application data to how it was before an account was linked to your phone, therefore if you never set one up it will be the same as "restoring" an existing Wallet setup.
Wallet is stuck at "adding card" or "initializing account" or it tells me my device/carrier is not authorized, is my secure element toast?
Nope. This is a different message, Wallet activation is turned off at the moment. There is a potential fix but requires root. There are threads here and here about these issues. Please do not discuss Wallet activations here.
Sources:
http://rootzwiki.com/news/_/articles/secure-element-error-locking-users-out-of-google-wallet-r280
http://forum.xda-developers.com/showthread.php?t=1472117
http://androidforums.com/verizon-ga...t-problem-google-wallet-help.html#post4013169
http://androidforums.com/sprint-gal...65-sprint-google-wallet-root.html#post4376858
Click to expand...
Click to collapse
I'm posting this in development section cause alot of people will head straight to the dev section to root as they get their phones with the 32Gbs being shipped please read if u plan to use google wallet please read it to prevent from having a messed up phone if it
*********UPDATE 6/28/2012
Ok im getting reports of Google wallet not working even on stock devices i think it has something to do with sprint not for sure but think it has something to do with sprint trying to release a competitor app to google wallet making it impossible for both apps to control the secure element so youd have to choose between google wallet and sprints touch wallet nothing is confirmed but thats my assumption
http://www.techradar.com/news/phone...-to-launch-a-google-wallet-competitor-1084799
http://www.youtube.com/watch?v=gfstLqnTyzQ&feature=youtube_gdata_player
Complete video about it watch ^^^^^
Rev3ge07 said:
mods if u need to move or delete this thread sorry just thought it was important seeing how I'll never be able to use google wallet till I get a new galaxy sIII and as Roms are developed don't forget to clear ur google wallet settings
Click to expand...
Click to collapse
You did a reset already? I rooted and it says unsupported device but I believe it still works
Sent from my SPH-L710
xtrezpasor said:
You did a reset already? I rooted and it says unsupported device but I believe it still works
Sent from my SPH-L710
Click to expand...
Click to collapse
That just means google wallet knows ur rooted but ur ok but do not I repeat DO NOT wipe ur phone before clearing google wallet through the app not through settings u should be fine tho if u were to clear google wallet (through the settings like I said) and wipe and un root i can almost guarentee that message won't pop up
xtrezpasor said:
You did a reset already? I rooted and it says unsupported device but I believe it still works
Sent from my SPH-L710
Click to expand...
Click to collapse
And yea I did a wipe through CWM kinda screwed
Rev3ge07 said:
And yea I did a wipe through CWM kinda screwed
Click to expand...
Click to collapse
I'm sorry.... hopefully someone figured a way to fix it for you... if you have best buys protection plan they will replace it no deductible....
Sent from my SPH-L710
xtrezpasor said:
I'm sorry.... hopefully someone figured a way to fix it for you... if you have best buys protection plan they will replace it no deductible....
Sent from my SPH-L710
Click to expand...
Click to collapse
I'm confused tho idk much about development or android I just do a lot of testing of Roms but from what I've read NFC is built into the battery so I don't see why getting an origiNal battery wouldn't fix it but idk just my theory
Can you uninstall google wallet? And never worry about this?
master acehole said:
Can you uninstall google wallet? And never worry about this?
Click to expand...
Click to collapse
Completely up to u if u choose to uninstall I'm posting this for the users that want to use google wallet for myself I was excited to try it out that's why
Rev3ge07 said:
I'm confused tho idk much about development or android I just do a lot of testing of Roms but from what I've read NFC is built into the battery so I don't see why getting an origiNal battery wouldn't fix it but idk just my theory
Click to expand...
Click to collapse
I believe that the hardware in the phone that activates the nfc in the battery has a number assigned to it that matches a number in the operating system... like how my backup root can tell it's the save phone that did the backup or not our titanium offers to reset your id after you first flash... and that number is written into your Google wallet to stop theft... maybe using titanium you could restore your old android id? Just an idea but it might not work...
Sent from my SPH-L710
xtrezpasor said:
I believe that the hardware in the phone that activates the nfc in the battery has a number assigned to it that matches a number in the operating system... like how my backup root can tell it's the save phone that did the backup or not our titanium offers to reset your id after you first flash... and that number is written into your Google wallet to stop theft... maybe using titanium you could restore your old android id? Just an idea but it might not work...
Sent from my SPH-L710
Click to expand...
Click to collapse
Man right about now anything is a option for me gonna try it I kinda gave up on getting it fixed the forum i read basically left me with no hope
Rev3ge07 said:
Man right about now anything is a option for me gonna try it I kinda gave up on getting it fixed the forum i read basically left me with no hope
Click to expand...
Click to collapse
Let me know... maybe we just solved it lol
Sent from my SPH-L710
I never set it up before rooting and was aware of this but since i never set it up will i be alright? As soon as i rooted i backed up my factory image, did a factory reset and then set up GW... It asked for SU permissions and i didnt allow, however, i didnt enter a card yet to try and use it. I guess my question would be; when does it actually the error? Thanx...
Edit, And if is does give me the error when i enter card info, can restore the original image and will it fix itself or did rooting break this? Lol, thanx again...
Sent from my SPH-L710 using XDA
jr71x said:
I never set it up before rooting and was aware of this but since i never set it up will i be alright? As soon as i rooted i backed up my factory image, did a factory reset and then set up GW... It asked for SU permissions and i didnt allow, however, i didnt enter a card yet to try and use it. I guess my question would be; when does it actually the error? Thanx...
Edit, And if is does give me the error when i enter card info, can restore the original image and will it fix itself or did rooting break this? Lol, thanx again...
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
I think your ok. It's after you set it up if you then restore your be screwed
Sent from my SPH-L710
jr71x said:
I never set it up before rooting and was aware of this but since i never set it up will i be alright? As soon as i rooted i backed up my factory image, did a factory reset and then set up GW... It asked for SU permissions and i didnt allow, however, i didnt enter a card yet to try and use it. I guess my question would be; when does it actually the error? Thanx...
Edit, And if is does give me the error when i enter card info, can restore the original image and will it fix itself or did rooting break this? Lol, thanx again...
Sent from my SPH-L710 using XDA
Click to expand...
Click to collapse
yea i never set mine up as well, i opened the app to see wtf it was but never got pass the setup screen i just exited it....
Eww, no error here yet but when exactly did it error? When you just set up your account or when you gave card info?...
Sent from my SPH-L710 using XDA
Moving to General Forum but I will sticky it for now so its near the top.
Mark.
one important fact to keep in mind. so long as you have a nandroid backup of a time when google wallet worked, you can always restore that backup, reset google wallet while there, and then return to your new rom.
the proper way to do it is to reset it first, but it's not like if you forget, you're out of luck. just make sure you keep a backup of the last rom where you google wallet was working.
This should be stickied.
And title changed to "Google Wallet Users: Reset Wallet before flashing ROMs!"
jnadke said:
This should be stickied.
And title changed to "Google Wallet Users: Reset Wallet before flashing ROMs!"
Click to expand...
Click to collapse
huh..
Mark.
Hi everyone,
First of all, I just wanted to say thanks to everyone here for being such a great resource in the past. I have performed many roots via guides on here.
My real question, I was super excited to get KitKat and immediately accepted the AT&T Software Update...2 hours later I realized that my Portable WIFI Hotspot app was no longer functional due to the upgraded OS. I figured a factory reset would be fine since it wasnt KitKat when it first came to me, sadly it wasn't.
Does anyone have any advice for a work around? I have unlimited data with AT&T right now and do not wish to sacrafice that for hotspot services but it is a very convienent feature to have when I am on the go. I've thought of rooting, reverting (which didn't work), and search hours in the app store testing different ones.
Any and all advice/suggestions will be greatly appreciated
Thank you in advance guys and gals!:good:
There is no way around it without rooting, until they create another app, unless there is one that I don't know about. You need a modified framework file in the system directory, which cannot be accessed without root permissions. I'm guessing that you were using foxfi, like so many others around here. I might be wrong.
And next time, please do some research before accepting these toys, I mean OTAs. (I keep calling them toys, because the only reason I see why we so quickly rush to these OTAs is to play with them.) There is plenty of useful information here at XDA for you. Don't just look to fix your problem and then run. Some of the purposes of OTAs are to prevent rooting and block tethering (Foxfi has been broken a couple of times). When you do some more reading, you will see all of the problems that many are having around here after jumping to play with this new toy, I mean update, without waiting or doing enough research.
Personally, one of the best things I have done with my phone is not accepting this latest OTA.
ya, I completely regret not doing my usual research. I thought I read somewhere that you cant root this current version as well. If you can root, if someone could point me in the right direction I would greatly appreciate it, if not I can take a look around after work
The app was Portable WIFI Hotspot
Here you go if you need to root. It's in the general section.
http://forum.xda-developers.com/showpost.php?p=47747640&postcount=1
delete
I'm running stock AT&T 4.0.4 ROM, rooted with CWM. Google Play Services just updated to version 9.2.56 (034-124593566), and it's sucking my battery dry and making the phone run hot. I have a spare phone and brought it online, and the same thing happened as soon as Google Play Services updated. It is running anywhere from 50% to 80% of my battery when the screen is below 10%. Yep, it's using more than 10x what the screen requires. Battery that used to last 18 hours now lasts 2 to 3. Others have posted similar comments in the Play Store (like that's going to do any good). Common theme is it's older OSes.
I have tried disabling everything and it doesn't do any good. Too many things break if Google Play Services is removed. Going back to an old version is futile -- it self-updates within minutes. I tried GServiceFix and it works for few minutes, then the usage creeps up again.
I sent Google an email, but I expect nothing less than the run-around. So, I turn to XDA Developers.
First, is anyone else here still running stock, and did the same thing happen to you? How about on other ROMs (please specify)? Did you find a fix?
Assuming Google will do little to help, I need to do something to make my phone work right. So if there is a ROM where this is not a problem, I guess it's time to jump in. Problem is, some of the links in this forum are broken. I've found (or already had) most of what I think I need except a version or EFS Professional that works on our phone. I can find no working links to an older version that will do the job. I do have a Nandroid backup (also stored on my NAS), which I believe can restore the EFS, but I'd like to get just the EFS in case I need to load it to the system after flashing. None of the tools available in the Play Store seem to work on the Glide -- I end up with an empty backup directory.
My plan, assuming there is a Jellybean ROM without this issue, is to flash twrp-2.8.4-flashable.zip, since I understand TWRP is required for JB, then do another Nandroid backup with it, then flash whichever ROM is suggested to get over this. I've looked at Bubor's CM10.2, and it looks like it will fill my needs unless it also suffers this problem. If there is a reason I should update the Kernel, please let me know. I have not seen anything that makes me believe I need to.
Man, I wish one of the manufacturers would come out with a similarly sized new phone with a slide-out keyboard and AT&T compatible. I'd gladly upgrade, but there is nothing out there that meets my needs. Samsung S5 mini with slider -- I'm in.
Hi,
its one year later...
I'm with the same problem. Do you still have a solution?
Other ROMs have issues with camera and BT...
https://productforums.google.com/fo...rce=footer#!msg/play/uX3Xqk2gi_k/LurezyxjAgAJ
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.