Database Users

OTA updates on AT&T

Hello this is my first post. Just wanted to say hi.
Well I have an unlocked G1 running on AT&T and I was wondering how are we suppose to get updates if they are OTA and I assume you would need t-mobile for that.
Is there a way to manually do it? Is there someway to download it directly to the phone from a source?
Thanks alot.

I sure wish I had that t-mobile SIM that I had. I assume it wont work if it is canceled right?
I have a feeling people who have them unlocked are going to get screwed and have security holes up the wazzoo...

i have talked to tmobile multiple times about this. no one seems to know the answer. I have a t-mobile sim card in my phone right now just to see if it will update. the card is the one that came with the phone, show it shows the t-mobile service, it just will not let me call or anything. I am hoping that it will update this way then I can put my att card back in. I will probably leave the t-mobile in every night while I sleep and the phone charges just to see if it will actually work. I will keep you guys posted as to if it works or not.

I have yet to get my OTA update and I am on T-mobile. I was going to unlock my phone, and I have a question. Does your G1 work ok with data on AT&T market and all? plz let me know I have someone that is tempted to buy one at full retail and just take mine after I have it unlocked.
Thanks

it would seem to me that legally, they have to provide the patch at some point due to the GPL... it also must be provided free of charge..
when they offer it is a different story, but legally, anyone who has it, who share it (if they knew where it was cached) with no legal issues

Only Google doesn't use the GPL.
But yes, that's true. The source for everything that's free-and-open (we know there are parts of the OS that aren't) should be made available. Whether or not (and/or when) they offer the update as a binary is anybody's guess, like most things with the G1/Android.

maybe the evil FSF will get involved!?

spyz88 said:
Is there a way to manually do it? Is there someway to download it directly to the phone from a source?
Click to expand...
Click to collapse
Yes there is.
http://androidcommunity.com/forums/f28/learn-how-to-update-using-your-microsd-card-5784/
Worked flawlessly and I'm now running RC29.

uberingram said:
Yes there is.
http://androidcommunity.com/forums/f28/learn-how-to-update-using-your-microsd-card-5784/
Worked flawlessly and I'm now running RC29.
Click to expand...
Click to collapse
The info is also posted on this forum/site under the development area... sorry I don't have a link handy.
--M

did we ever find out if OTA updates get pushed to G1's on other carriers automatically?

The will be pushed to all G1's on a data connection. I repeat ALL G1's on a DATA connection.

I am on AT&T and just got the OTA update yesterday morning. I found this instruction on the internet (could have been sticky from this site) on how to get OTA update the original way.
I download Anycut from app store, create a shortcut for Device info, scroll all the way down and click on download button. Your G1 will call home and it'll appears that nothing else is happening on the screen.
I did this around 9pm Sunday morning, leave my wifi on, phone plugged in for charging and when I woke up my G1 greeted me with new firmware update screen (RC30).
Few issues that I found:
Home and call button are not responding (nothing happen when pressed) and I had to do a system restore to fix it. G1 security screen stop working even after turning security on and off - system restore fixed this. The Built in IM stop working when trying to connect via AT&T Edge, it complain that IM program can't read my phone number off SIM card - WIFI + IM client works without any problems.

natt108 said:
Few issues that I found:
Home and call button are not responding (nothing happen when pressed) and I had to do a system restore to fix it. G1 security screen stop working even after turning security on and off
Click to expand...
Click to collapse
Noting that those are are all symptoms of a Setup Wizard call that ended badly somehow.
The guy who discovered this first:
http://inportb.com/2008/11/28/disabling-the-screen-lock-on-android/
I discovered it accidentally, by playing with Any Cut a little bit too much. Heh.

Ah... I see my experience with Setup Wizard funkiness is not an isolated case. At any rate, I did not have to perform a factory reset, as re-running Setup Wizard resolved the issue.

US Cellular (US991) Self-Updated

Just wanted to give a quick heads up to anybody else that has US Cellular and let you know that mine did a self-update at some point (from the US99110b it showed up with to US99110c).
I have NO IDEA when the phone did this, as I never got so much as a warning or a notification or anything (Hell, I have not even rebooted the device). Just figured I would check the "Software Status" for ***** & giggles after reading a couple posts on here and happened to notice it was at 10c now.
.......I mean I at least have the .kdz of my launch firmware so I can go back if needs be, just annoyed that these devices are doing what they want when they want at this point.......I've seen iRobot and I know this never leads anywhere good!!

was your device connected to wifi? curious if people that delete all saved wifi networks still get the OTA or not.
I've made a post in the lounge thread about these updates http://forum.xda-developers.com/showpost.php?p=61672737&postcount=622
I wonder if USCC would all you to swap the phone out for a 10B model since you did not initiate the OTA?

I just checked mine and it is updated. The auto update was checked. I unchecked it and unchecked the auto check for updates in software update on the about screen.
Sent from my LGUS991 using Tapatalk

Android Instant Tethering

http://www.theverge.com/2017/2/10/14579918/instant-tethering-android-now-available-pixel-nexus
So what's the deal with this? The article says it's coming, but no release date and it says it's for version 7.1.1, which we have, yet without this feature. Then it shows you how to access it in settings, but of course it isn't there, so I'm assuming it's showing you how to enable tethering when it's released.
EDIT: OK so earlier today I checked and did not have this setting. Then I checked right after writing this post and now the option is there. I have no idea what changed but I'm about to try this out. This is going to be great without root

I think they is manually activating it by region or some sort, so not everyone going get it at once but a select people at a time until everyone

FYI: I had to restart my phone before it showed up.

Won't detect OTA update (ATT)

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.

Android 10 Share Crash

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.