Related
I am having an issue where the call log in contacts not updating. Last thing it is showing is october. I tried to force stop and reset data. But last thing it is showing is october 31 for me. Anyone got a solution:?:crying::crying:
anyone can help?
Same issue need help...Any answers?
Hello all,
I have a unique issue where the most recent Android update caused my password to be truncated from 20 digits to 16 - now it won’t let me login to the phone when the phone starts up. I have 6 attempts left for a factory rest, whereby I lose all my data!
Samsung can’t help because I wasn’t logged into the Google Play Store, and this was a new phone and I haven’t backed up in about 2 weeks. I would like my data back, but that isn’t an option per Samsung, where I heard about this group.
Is there anyway to get my data back? And bypass this update to roll back without being able to login?
Dr. Fone won’t work because I didn’t have the USB Debugging option turned on. I can get into the boot menu, but have little recourse after that. This is a Hail Mary for anyone that might’ve experienced this or has thoughts on how to get my phone back on. Thanks in advance for reading!
And why would Google do this?! At least a big warning would’ve been helpful!
Best.
Hi,
I updated my Nokia 6 early yesterday morning, February 21st. The update was 1,7GB in total, don't know what it consisted of. The update came to my phone through standard automated update check, I got a notification to connect to WiFi, I did, the update downloaded and installed.
Apparently, it was the Android Pie update, though I didn't look that closely.
So, 100% stock ROM, no mods, fully official update method. No tricks. Connected to wall, 100% battery.
After the update the phone booted and asked to reboot to install operator updates. I'm not quite sure the exact wording of the message pop-up, but that's what it asked as far as I can remember. I agreed to reboot, the phone shut down, and never came back to life again.
It won't respond to any key presses. It's completely bricked.
I'm going to get it fixed in a shop, where it'll go to have its display changed anyway. I'm writing this here to ask, has anyone else had troubles with the update? It was rolled out in Finland apparently February 21st or 20th, or then I haven't reacted to the notification before. I'm quite unhappy with the state of the matters, since it seems to be the official update that bricked my phone.
So, anyone had any troubles with Android Pie update?
Mine bricked 2 days ago after the same Android pie update, 1.7 GB. I have tried flashing to no avail. Currently looking for ways to restore a bricked Nokia 6 TA-1021.
rwaithera said:
Mine bricked 2 days ago after the same Android pie update, 1.7 GB. I have tried flashing to no avail. Currently looking for ways to restore a bricked Nokia 6 TA-1021.
Click to expand...
Click to collapse
According to the service personnel, a small wonder happened when they plugged in my TA-1021 - the device started right up. It's quite extraordinary claim, since my phone was connected to my charger when it shut down, and it was showing 100% battery.
I have no reason for this, only speculation. The only explanation I can come up with outside of some divine intervention is, that the phone did not shut down after all. Instead, it was stuck on some loop with screen off and buttons inoperative. When it finally ran out of battery, it responded right away when it received more power.
I did not try and flash my phone myself. Nor did they flash it in the shop. It wasn't necessary, the phone is now fully functional.
Maybe try to plug it in briefly and see what happens. If nothing, then just unplug it again and try another time tomorrow. Btw. HMD Global's chat support was very responsive, so I highly recommend contacting them if you suspect that your case was caused by the updater itself.
Mine didn't get bricked, but it started having issues with Google accounts. After the update, all apps which use my Google account to login had login errors & I couldn't add Google accounts onto the device. I manually synced the account, removed the account & tried to add it again (shows a "sorry something went wrong" message everytime I try to add an account), wiped the cache, even factory reset it, but nothing helped. I finally had to spend some time learning how to downgrade it & was able to add accounts on the device again. But after I updated my device with Android 9 (V6.12) again, the issue came back.
my all google apps arent working on TA-1000
mine is completely bricked. wont turn on at all. TA-1033.
Is there anyway to fix this?
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Do you need to be connected to WiFi or have a certain battery level? Try charging to 100% and connecting to WiFi then manually search for the update.
What I had to do is go into the date and time and shut off auto time update and manually set it 2 days a head then mine found the update.
loffer said:
My S10+ will not detect the day one OTA update. I check every day and it says software up to date even thought its still on G975USQU1ASAT. AT&T says to contact Samsung and Samsung says to contact AT&T. Anyone else had this problem or have any idea how to fix it? I've already tried factory reset, clearing cache and data on the updater apps with no luck.
Click to expand...
Click to collapse
Two options:
1) Borrow someone else's sim or ask At&t for another
2) Download the S10+ OTA and update via SD
Did you put the sim that came with it in? I used my old sim and had the same problem till I changed the sim card.
Sorry for the late response and thanks for the suggestions. Just returned from vacation so I will try the suggestions. Also yes I used the sim they sent me. I suspect something got messed up in the sim provisioning as I came in as a new line then ported my number in. I will try putting my wife's sim in and report back. Thanks again!
Mine wouldn't detect an update. I'm only using mine on wifi as this one is just a spare phone for now.
To get the update though I needed to put in my att dim and put the date a week in the future. That's the only way I was able to actually get it to check the server.
I'm having the same exact problem. I purchased my S10+ directly from Samsung, but it was the AT&T model. I've been stuck on the ASAT baseband with the Feb 1 Security patch since day 1. I've been on the phone/chat with AT&T for the last 3 days. Each time they've promised that they have pushed the update to my phone, and every time I check, I get the "Software is up to date" message. I just tried setting the date to next week, restarted, and checked for the update..still nothing.
The same thing happened to me with my Note 8, but I was able to get around it using ODIN. I've told AT&T that I'm not paying my bill until this is resolved (like that's gonna do anything). Anyway, I'm at the breaking point on this, and not getting anywhere fast.
I just got the OTA update from AT&T for my V35 to Android 10. Now, whenever I try to Share from an app and the system Share panel is invoked, the Share panel starts to populate and then crashes and often takes the app with it. The only app that I can Share from now appears to be Firefox, but that doesn't appear to use the system Share but has its own.
Any ideas what could be going on? This is happening for my and my wife's phones (both V35). I contacted AT&T chat support and all they gave me was canned answers and then ended the chat; useless.
UPDATE 1: I found the problem with both phones is GroupMe. On the one phone I was able to get things working again by clearing the cache and data for GroupMe, uninstalling it, reinstalling it, and logging back in. For the other phone, this didn't work. I can Share when GroupMe isn't logged in, but once I log in, the Share crashes while populating. The only difference between the working phone and broken phone is that the working phone has a GroupMe account linked with Microsoft and the non-working phone has its GroupMe account linked with Google. So, it appears that a Google-account-GroupMe + Android 10 + Share is the broken combination. Now I'm really at a loss here.
UPDATE 2: Apparently I'm not the only one: https://www.reddit.com/r/AndroidQue...e_causing_android_system_share_menu_to_crash/
UPDATE 3: While GroupMe logged in with Microsoft was allowing Share to work on my phone for a while, Share has since stopped working while I'm logged into GroupMe. When I delete the data for GroupMe, I can share again. I've emailed GroupMe support about this matter and will report back. I'm currently running the latest version of GroupMe from the Play store: 5.47.4, released May 19, 2020
UPDATE 4: I've chatted with AT&T support a few more times. The first time was with Oliver, and that didn't go very well. I did manage to get a case number though. I was told that update V350AWM20i would be pushed to my phone in the next 24 hours which would fix the issue; I already have V350AWM30c, which is newer. I then spoke with Mike in a second chat session (which I started because Oliver hung up on me) and was told that my case has been escalated and I should at least hear back from AT&T in 24 hours. I'll keep updating this.
For sure GroupMe shouldn't be causing Android to crash, but Android shouldn't crash because of a bad app. IMO, both parties are at fault here.
UPDATE 5: I contacted AT&T today (they didn't contact me as they said they would) and they now say that I'll have a resolution by the 27th. GroupMe hasn't returned my request for support.
UPDATE 6: I contacted AT&T yesterday, the 26th, and they said that an update that would be pushed to my phone to fix the problem. They didn't know the version of the update that would be pushed. The update never came. Today, the 27th, I contacted AT&T again and they said that my case was closed and the the update was pushed. They said they pushed the latest version of Android Pie to my phone. So, here we go again. They decided they would re-open the case and would investigate my issue. For some reason they were under the impression that I opened a support ticket to get an update to Android 10. No one that I spoke with today could even tell me what my issue was, even after they read this post. I was transferred to another support agent where I sat for about an hour before quitting the chat. I only saw "Agent is typing..." and "Agent stopped typing" once, after about 45 minutes, but no actual interaction from the agent.
In other news, GroupMe has started replying to my request for support and apparently they can't open x265-encoded videos of a screen recording I took of the problem that they requested. I've sent them an x264-encoded screen recording to see where this goes.
UPDATE 7: I ended up calling AT&T support (866-344-6217) and spoke with a very helpful person who was able to correctly identify the problem and is escalating it to others, possibly LG, to see if the problem can be addressed. A remote control session was done with my phone where the problem was clearly reproduced. Such was the case even after clearing various cache and data for the app, web view, and system. I was informed that the problem will likely be solved by a hard reset of my phone. Apart from the obvious reason why I don't want to do that, the fact that this affects two of my phones the same indicates that it is an endemic software problem that should be addressed less this roll-out causes more problems for others. Since my phone has such a reliable reproduction and I need to schedule time to reset my phone, I'm holding off on doing this until I hear back about the escalations that AT&T is taking, which I'm expecting today, the 28th based on our conversation.
If anyone knows how to contact LG on this matter, or even AOSP, I'm all ears. It still should never be the case that a logged-in app should be able to crash the Share function in Android.
UPDATE 8: I just (8:49 am CST, May 28th) received a text message from AT&T saying that they were closing my "Urgent Case"; I was never called to inquire if my issue was resolved. Hopefully I'll still get the phone call I was promised later today.
UPDATE 9: I heard back from AT&T and they continue to work the issue. For reference, the model of my device is LM-V350AWM and it is SIM unlocked.
UPDATE 10: Microsoft GroupMe released an update to version 5.47.5 today which resolved the problem on my wife's phone. Thus, there are two solutions to this problem: 1) the comment below about turning off and on "Direct Share", and 2) installing the update for GroupMe. The reason why any installed app could cause the Android system to crash is still beyond me and hopefully is something that AT&T, Google, and LG can work out.
This happened to me last nite. I'm still on 9. Drove me cray untill I rebooted. Now I have some random app stop pop-ups, but sharing is fine.
Sent from my LM-V350ULM using Tapatalk
I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.
wizardofwoz said:
I had a similar issue. I had to disable the "direct share" and "nearby devices" under settings > network > sharing panel.
Oddly enough after verifying this fixed my issue I was able to re-enable them and sharing was still working.
Click to expand...
Click to collapse
This absolutely worked. I'll continue watching to see if the problem returns as GroupMe contacts work their way back into my Direct Share list. I do find it strange this came up after the upgrade. It seems that the upgrade process didn't reset/flush something related to the list of contacts related to GroupMe.