Just checked for ****s and giggles and it was there (SIO).
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
kristoff_sz said:
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
Click to expand...
Click to collapse
Fixed as in what? The sensor is probably as good as it'll get, the A50S and A51 seem to have different hardware, so it works better. Always readd fingerprints after an update, also add 1 fingerprint with both thumbs, so it's more reliable.
kristoff_sz said:
I've done this update already.
Nothing new at all, just security patch.
FP sensor still not fixed.
Click to expand...
Click to collapse
Are you using a screen protector? To be honest my FP sensor doesn't have a problem since like the August update or so. And I never had to re-register my fingerprints again since then.
I got the update aswell, props to Samsung that was really quick security update..
Polska XEO version, Android System battery drain bug still existing. In other countries is the same thing?
wojtas2max said:
Polska XEO version, Android System battery drain bug still existing. In other countries is the same thing?
Click to expand...
Click to collapse
Confirmed: battery drain and slower system response after ASL6 update. Hope samsung can fix this in next update
A505FN - Czech Republic
After the last update with the security patch date of February 1, after the first reboot, the screen crashed, including a touch response. I eliminated this by restarting the device but I was struggling with the Internet connection. Whether I was connected via wifi or a SIM card, the screen was disconnected from the Internet and either restarting the card or the whole device helped. After several hours of experiments I found out that the culprit is the application "Blokada", after its removal everything works as it should. I do not know if the problem was caused by "tweaking" Samsung update or some art of Google security policy, in any case, until then a great ad blocking application had to unfortunately have gone from the phone .......
janzrokycan said:
A505FN - Czech Republic
After the last update with the security patch date of February 1, after the first reboot, the screen crashed, including a touch response. I eliminated this by restarting the device but I was struggling with the Internet connection. Whether I was connected via wifi or a SIM card, the screen was disconnected from the Internet and either restarting the card or the whole device helped. After several hours of experiments I found out that the culprit is the application "Blokada", after its removal everything works as it should. I do not know if the problem was caused by "tweaking" Samsung update or some art of Google security policy, in any case, until then a great ad blocking application had to unfortunately have gone from the phone .......
Click to expand...
Click to collapse
Use AdGuard it has never failed me on non-rooted phones.
re
k3lcior said:
Use AdGuard it has never failed me on non-rooted phones.
Click to expand...
Click to collapse
Thank you for your answer, of course I installed AdGuard instead of Blokada and everything works. Today I can no longer imagine using a computer or smartphone without blocking ads, there are more and more annoying and spying. However, I was extremely satisfied with Blokada until the February update, unfortunately she had to leave. We will see if the manufacturer of this application responds and will release a new version that will not suffer from this ailment.
Charging issue after ATA1 UPDATE (February)
Is anyone else experiencing this, I swear after the update took it off the charger one last time phone restarted then after that it wouldn't charge anymore. At this point, I'm blaming the forced OTA for the problem meanwhile I've resorted back to my reliable S5. Amazon & Samsung both said that they couldn't RMA the phone because I missed my January 31st window.
haha and you're reporting me and blocking me because of truth.
My phone charges slower after the update. 15w fast charge feels like 10 w, and when I disable fast charge it won't charge and give me prompt something like "use the original samsung adapter or check the cable"
A505GUBS5ATB2 Combination
Hello friends, could anyone tell me if there is a combination rom for this update ? (A505GUBS5ATB2)
Thanks a lot!
Related
I am using the Focus and I used the Cheveronupdate tool like as soon as it came out, I have just done a 3min search to see what this update does for the focus. Has anyone else had this occur recently?
And the Update PR stunt (note)
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
ATT Focus
I also used the Chevron Updater and updated to 7390. I received a notification via Zune for the standard update last night and tried to update. Went through all steps and then I got an error 80180005 for which I could find no explanation, but the update failed. I then plugged my USB cable to the back USB ports on my laptop and the installation succeeded and changed the bootloader number, firmware and radio software numbers. These numbers were NOT CHANGED with the NoDo update from the CXhevron Updater method.
This is the Samsung firmware update.
I also unlocked my phone using Chevron to update to NOdO weeks ago but am yet to see the samsung firmware update.
buffalosolja42 said:
I guess the generic MS saying it will prevent your phone from updating is now proven false as well, granted I don't know if this update has done anything yet since I am on step 7 of it creating a backup file.
Click to expand...
Click to collapse
Not quite the case.
@BrandonWatson said:
@Strider_Aus our guidance remains - Walshed phones will not update past NoDo (specififcally build 7390)
Click to expand...
Click to collapse
well mine went through
without a hitch yes OS revision numbers didn't change and I am not sure about firmware. Can't tell you that I see any difference right now.
capacitive buttons should be less sensitive, and dont work if you press the screen on a different place at the same time (for gaming or video playback etc, accidently hitting back button, it should be disabled now)
camera should auto default to anti-shake setting ON.
screen should be responsive even on a soft surface (pillow)
this is what I read, not sure, can people confirm this? Is this also for the omnia7? Mine is at the store for repair but these things were some annoying things and will be nice if they are fixed on the omnia as well.
I have a Note II (N7100) from Germany (DBT), carrier-free, and was on the Samsung stock Jelly Bean LL7 (DBT) ROM. I only CF-Auto-Root'ed (and Triangle Away'ed) this ROM but that's enough to get a "Modified" system status and thus not being able to get system software update notifications (for example, manually triggering the check for new firmwares only gets you to the "wait, checking for new firmwares" window, which keeps checking forever until you cancel it).
...Or so I thought.
Yesterday I received the notification that the new MC3 firmware was available even though if I manually check for updates it never finishes the check and, above all, even though I DISABLED the automatic check for new updates since the system doesn't seem to be able to find new updates with a modified status!
Trying to accept the update only brought me to the same "wait, checking for new firmwares" window which still hung forever so I tried to connect to Kies (latest version, of course) and it too told me that the new MC3 firmware was available so I tried to update it through Kies and... it worked!
Previously I had temporarily checked "keep root" in SuperSU Pro and I had disabled USB Debug (which I need especially for GMD Gesture Control, which I also temporarily disabled).
The update was completely successful (if a bit long) and everything works perfectly fine.
Does somebody have an explanation for why I received the notification even though manual checks don't work and (especially) I even had the automatic checks disabled (thinking it doesn't work)?
At first I even thought it was a fake notification from some malware (although I have only a couple of games, which are the usual source of malware -which I have never got before BTW-, installed)! LOL
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Question is: did it kept your phone rooted? ( after you updated through Kies )
Answer is No root after update.
Sendt fra min GT-N7105 med Tapatalk2
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
That should not be possible and sounds to me like you have a serious fault there, and quite likely a fire hazard.
jca1981 said:
I had same problem until i updated with kies. yesterday my phone was so hot i almost got burned from touching it and almost discarged, even thougt i was in charger, i think i was because it was constant searching for update. my guess is the servers was overloaded so my phone could not get the update or samsung pulled the update before my phone could download it. my phone is Dansih version.
Click to expand...
Click to collapse
Actually I didn't mean it as a "problem" at all :laugh:
The overheating problem doesn't sound like something "normal" anyway, try doing something CPU-intensive like a benchmark or a heavy game for say 15 minutes and check the temperatures against another Note II doing similar tasks if you can, getting "almost burned" is NOT normal, you might have an HW fault (assuming of course you haven't OC'ed your phone).
Stressing CPUs/GPUs gets the phone *warm*, even "very warm" (they all are subjective definitions after all), but never "almost burning" hot!
carlitos66 said:
Question is: did it kept your phone rooted? ( after you updated through Kies )
Click to expand...
Click to collapse
I have SuperSU Pro and I checked Survival Mode but the SuperSU app wasn't there after the update.
TBH maybe simply reinstalling it from the market might have been all that was necessary but I simply re-rooted via PC Odin because I don't care about the warranty since my personal data on my devices are worth much more than the devices themselves to me (i.e. sending my devices for repair with my data on them is unthinkable to me and if they are broken in some way but can boot and can let me securely erase everything first then I can always "unroot" and "triangle away" later).
Root developers are saying don't take the updates. Few people are reporting that the updates made anything better. Don't take the updates if you can help it.
Follow the instructions below, and report back with your phone info (carrier, variant, software version, etc.). Also report if updates were successfully blocked, or if they installed anyway, or if you just get a nag screen. Thanks!
If your phone has already downloaded the update and is trying to install it, follow the advice here. This won't work for AT&T phones because they removed recovery mode.
Start here:
Get debloater (works without root!) and set up your computer so you can run ADB and connect with your phone. You may need to install the LG United Mobile Driver.
Please donate to the Debloater developer, gatesjunior! Debloater has made this so much easier!
There are many packages you can block that will improve the performance and battery life of your phone (see my blocked.txt below), but the packages you want to block that will hopefully prevent updates are:
LGDMSClient.apk (Blocking breaks WiFi calling setup on Sprint only.)
LGUpdateCenter.apk
LGFOTA.apk Two users reported calls going straight to voicemail with this blocked.
LGLDB.apk I don't know if it's related to updates but it seems to be MLT spyware.
Not all carriers will have all these files, but block what you do have and report any problems so I can update this post with what works and what doesn't
Carrier specific files:
Sprint users may want to block:
Sprint_Installer.apk
ItsOnService.apk
ItsOnUID.apk
Tierez reported that blocking the ItsOn files breaks WiFi. They also reported that blocking LGDMSClient.apk broke the WiFi calling setup screen.
Verizon users should block:
VerizonIgnite.apk, It's a post-sale bloatware installer. Thanks alan242!
@JeffXT inadvertently blocked a Verizon file that enabled tethering.
AT&T users should block:
WildTangent.apk
T-Mobile users should block:
AdaptClient.apk
This will break the software update screen in about phone and so far has prevented my phone from trying to update. My AT&T H810 hasn't tried to update and I can't force it to update since I blocked LGDMSClient.apk, but it seems we can't be too safe in preventing forced updates so leave no questionable package unblocked!
Something I also did during setup was to not agree to the optional LG EULA that would have allowed app updating. I've also blocked:
LGStartupEula.apk
LicenseProvider.apk
UnifiedEULA.apk
Don't block LGSystemServer.apk, it breaks notifications and other stuff (LED, sound, and vibration).
Autoprime is listing which software versions are updating the firmware to V1 here.
Good luck!
Don't block LGSystemSetup.apk or LGSetupWizard.apk! You'll need it to run if there phone gets reset. Ignore the blocked.txt file below.
phineous said:
After seeing the mysterious "security enhancements" mentioned in the AT&T release notes on the July 1st update I think it's important to prevent further updates incase they break future rooting methods. Also, why take their update if it's not shown to improve performance? Come on! There's an update to Uber, but no mention of touch screen fixes?!
FIrst, get debloater (works without root!)and set up your computer so you can run ADB and connect with your phone. You may need to install the LG United Mobile Driver.
There's a ton of packages you can block that will improve the performance and battery life of the phone, but the package you want to block to prevent updates is LGDMSClient.apk. This will break the software update screen in about phone and so far has prevented my phone from trying to update.
Good luck!
Click to expand...
Click to collapse
Just a quick heads up (might just be me, might be US Cellular in general....I am not sure) I went through and did this after hearing about different companies basically force feeding their clientel these OTA Updates and even though I did it all right down to the letter and did not skip anything my US991 still went ahead and did a forced update to 10c (not sure why or even when it did this, just know that it did at some point).
Hopefully they are not blocking any exploits with this stupid 10c update (which I assume they did as my device was running buttery smooth and had no issues that would have needed an update in order to correct).
Z3ldaFan88 said:
Just a quick heads up (might just be me, might be US Cellular in general....I am not sure) I went through and did this after hearing about different companies basically force feeding their clientel these OTA Updates and even though I did it all right down to the letter and did not skip anything my US991 still went ahead and did a forced update to 10c (not sure why or even when it did this, just know that it did at some point).
Hopefully they are not blocking any exploits with this stupid 10c update (which I assume they did as my device was running buttery smooth and had no issues that would have needed an update in order to correct).
Click to expand...
Click to collapse
Sorry to hear it didn't prevent your update.
I've added more files to block, and one to unblock in the OP.
phineous said:
Sorry to hear it didn't prevent your update.
Try blocking LGUpdateCenter.apk also. My AT&T H810 hasn't tried to update and I can't force it to update since I blocked LGDMSClient.apk. Seems we can't be too safe in preventing forced updates so leave no questionable package unblocked!
Something I also did during setup was to not agree to the optional LG EULA that would have allowed app updating. I've also blocked:
LGStartupEula.apk
LicenseProvider.apk
UnifiedEULA.apk
I've attached a Debloater blocked.txt that shows all the packages I've blocked.
Click to expand...
Click to collapse
No worries, it just is what it is (yeah I was angry about it, but not like I can do anything about it). I will certainly go through and block the rest of the applications that you mentioned though so hopefully I can prevent any future aggravations caused by these damn self-updates. Thanks for posting how you went about it and letting us know that (so far at least) it is going according to plan.
Holy Cow! I thought T-Mobile was bad with the bloat but jeez....AT&T makes our bloat look like....well, I dunno it's still bloat, but we've got a LOT less of it lol. I use the debloater tool, but UX 4.0 isn't that bad by its self. I removed all the T-Mo stuff and that's about it.
Thanks!
painedglass said:
Holy Cow! I thought T-Mobile was bad with the bloat but jeez....AT&T makes our bloat look like....well, I dunno it's still bloat, but we've got a LOT less of it lol. I use the debloater tool, but UX 4.0 isn't that bad by its self. I removed all the T-Mo stuff and that's about it.
Click to expand...
Click to collapse
Did removing the TMobile bloat affect wifi calling?
G4'ed it!
Not at all, less lag and a bit smoother. Battery lasts longer since apps that drain the battery are disabled. Just be smart about what you disable. It has a search feature, so I'll search for say "tmo" any apk or service with that search term in it will show up in the list, disable it and move on to the next apk/service. You dont even need to reboot, you can watch them get disabled in real time.
I just bought my second G4, trying the phone again. It is another Verizon model.
People raised interesting points about holding off on updates, in case it makes root more difficult, so I got the Debloater tool (that is awesome!) and tried to block the items listed in the original post.
With Verizon, I don't see an entry for "LGUpdateCenter.apk", so I could not block that one. I hope the remaining 5 will be enough to keep the update at-bay for now.
phineous, that's an interesting point about the optional LG EULA. I agreed to something from LG during initial setup today, I guess I didn't give any real thought to not agreeing.
I have not yet applied anyone's complete Debloater list, I guess I'm not quite brave enough for that just yet. I only went through and disabled things I could identify and knew I wouldn't need at the moment.
How many apks does the AT&T G4 have? My Tmobile has 273.
Replacing my earlier post, to avoid confusion: Verizon messed up something on my line. After a day, they got it fixed, and now I can use Advanced Calling on my G4, still with the original software (having not gotten the recent update). Everything seems to be working now.
RedOCtobyr said:
Replacing my earlier post, to avoid confusion: Verizon messed up something on my line. After a day, they got it fixed, and now I can use Advanced Calling on my G4, still with the original software (having not gotten the recent update). Everything seems to be working now.
Click to expand...
Click to collapse
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
GUGUITOMTG4 said:
How many apks does the AT&T G4 have? My Tmobile has 273.
Click to expand...
Click to collapse
I don't remember how many it came with originally, but I've blocked 85 out of a total of 297. I've probably installed about 57. I would guess around 240 originally.
flamadiddle said:
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
Click to expand...
Click to collapse
Don't let the salesperson set up the phone! They seem to delight in downloading updates. I'd keep the phone off or at least disable WiFi till I could connect it to a computer and Debloat it.
Good luck!
phineous said:
Don't let the salesperson set up the phone! They seem to delight in downloading updates. I'd keep the phone off or at least disable WiFi till I could connect it to a computer and Debloat it.
Good luck!
Click to expand...
Click to collapse
Yeah, that's the plan. I'd just like a frame of reference so I know if all my efforts to prevent the OTA work or if I was defeated before I even got the phone.
phineous said:
I don't remember how many it came with originally, but I've blocked 85 out of a total of 297. I've probably installed about 57. I would guess around 240 originally.
Click to expand...
Click to collapse
Wow 85 is such a relief I blocked just 34. At least it does not get high temps now.T-mobile seems to add much lesser bloat indeed. My 273 include around 40 downloaded apps.
flamadiddle said:
What's your Baseband Version and Build number? I'm buying the Verizon G4 this Saturday and would like to know if I have the OTA out of the box.
Click to expand...
Click to collapse
See attached. I believe the item of interest, relative to the OTA, is the Software Version. The new one (updated) ends in 611A, I think.
They did a brief setup at Best Buy for me. I Factory Reset when I got home, then Debloated the items that would start the update:
http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
RedOCtobyr said:
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
Click to expand...
Click to collapse
Look at how sneaky the carriers are now! It's a good thing the devs are being quiet about their root method.
RedOCtobyr said:
See attached. I believe the item of interest, relative to the OTA, is the Software Version. The new one (updated) ends in 611A, I think.
They did a brief setup at Best Buy for me. I Factory Reset when I got home, then Debloated the items that would start the update:
http://forum.xda-developers.com/g4/help/how-to-prevent-updates-g4-t3148650
But it wasn't until the next day, after another Factory Reset, that I forgot to Debloat those immediately, and had turned on the WiFi. I noticed when the update was halfway downloaded. Turned off WiFi, and turned on Airplane Mode, until I was able to Debloat the offending items.
No updates stuff since then, several days ago, even with WiFi on.
Click to expand...
Click to collapse
Exactly what I needed. Thank you! :good:
flamadiddle said:
Exactly what I needed. Thank you! :good:
Click to expand...
Click to collapse
You are welcome! Please report back if discover any problems or other files to block.
It's installing right now. The changelog only mentions Google patches.
Android security patch is on 5 november 2017 level.
The bluetooth security bug has been resolved, the WIFI security bug (KRACK) not yet. I didn't find any problems after updating.
Sho-Bud said:
The bluetooth security bug has been resolved, the WIFI security bug (KRACK) not yet. I didn't find any problems after updating.
Click to expand...
Click to collapse
I just got this phone a couple days ago & indeed,had three updates awaiting to be d/l & installed.
I had the Mate 9 earlier this year,so,most of what's on-board is familiar.
Not a single glitch/stutter/etc... the WI-FI is probably the best I've used to date,very quick to connect.
The extra RAM almost seems overkill,but,I like having those type of "problems",LOL.
Gonna go OT for a moment:
Are you stock,or rooted/ROM?
If the latter,would you be so kind as to post or PM links on bootloader unlock/TWRP/root/ROM?
THX! :good:
I'm on stock
Do any of you guys use Barclays?
After updating, mine is not working with any Barclays apps because they're saying it's rooted
Also, it keeps asking to authorise my car Bluetooth access to the contacts - and I have to do this 3 or 4 times, it never remembers the answer (even when I tick the box)
Any replies will be appreciated!!
charmz2k2 said:
Do any of you guys use Barclays?
After updating, mine is not working with any Barclays apps because they're saying it's rooted
Also, it keeps asking to authorise my car Bluetooth access to the contacts - and I have to do this 3 or 4 times, it never remembers the answer (even when I tick the box)
Any replies will be appreciated!!
Click to expand...
Click to collapse
I don't use Barclays. No problems when connecting to my car system, contact transfer fine.
Anyone having this problem where call doesn't connect with error of 'Call not sent'? This is doesn't happen when connected to Wi-Fi but happens most of the time otherwise and I have to re-try 2 times (sometimes 10 times) to get the call connected. I have tried clearing data for phone app but it didn't help. I am not seeing any reports on it in any beta discussion so I am guessing its not a beta problem? It never happened before the beta update and I installed the beta update from total reset instead of just updating.
Yes. Only happens when I am on Bluetooth connected to my car. I gave to call from the phone app instead of my driver control.
"Call not sent" error on Samsung Note10
I'm having a similar issue with my Note10, just shows "Call not sent.", whether connected or not to Android Auto or any other dock/bluetooth, it doesn't seem to fix the problem.
I have tried several active sim cards from different carriers which work fine in other phones, but in the Note10 I can only access the web and text. When trying to make a call with full signal bars and LTE next to it, it just shows "Call not sent". I've done all the usual restart, full factory reset from the recovery menu, even reflashed it via Odin with the latest firmware (N970U1_UES2BTA1) three times, then factory reset again, but it's doing the same. It seems to be a hardware problem, not a software glitch.
By the way, my phone is unlocked and I have checked the IMEI to make sure it's not blacklisted. I have also examined the charging port for any liquid damage, but it's completely clean and shiny. When I dial the test code *#0011# to compare the network status screen against a Samsung S9's, I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
Also, out of curiosity I have installed a couple of different phone dialers (Google Phone and Simpler Dialer), but the outcome is the same "Call not sent.".
Evidently there's a hardware problem with the Note10 series (some or all), because Samsung's own forum full of similar complaints.:=(
Same problem. Getting call not sent
Was not issue in Android 9. Only Android 10.
Galaxy note 10+ unlocked version on tmobile.
I've also had other random Bluetooth issues.
this issue got so bad, i am not able to make calls, unless i make multiple attempts.
so i just upgraded to the S20 Ultra. Same issue!!
Here are other factors and connected devices.
Connected to a Ford vehicle (Sync; 2017 Explorer)
Connected to Samsung Active2 smartwatch (but issues remained even when watch disconnected).
I've also tried to unpair / re-pair. To no avail...
Help!
Also here:
https://us.community.samsung.com/t5...-Android-Auto-after-upgrading-to/td-p/1077007
I am really glad I blocked updates, I am still running on Pie
billa said:
I've noticed that the "MIPI TEST SUCCESS" and "ASDiv: PASS THROUGH" at the bottom of the screen are MISSING on the Note10, which might have something to do with the failed calls.
(
Click to expand...
Click to collapse
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
ultramag69 said:
I have an Exynos Note 10+ I don't seem to have this problem and when I did the test you did I got "MIPI TEST SUCCESS" but nothing about ASDiv.
Could this be a problem with the Snapdragon chipset?
Click to expand...
Click to collapse
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
billa said:
It certainly could be, on all other phones I always see the "MIPI TEST SUCCESS" in test mode, but not on the N970U.
It might be fixed with a new update, unfortunately there's still nothing newer available than UES2BTA1 as of right now.
I have the feeling it's a hardware issue rather than software, in which case it's not going to be fixable, short of replacing the main board.
No idea, why this started happening mostly after the last update.
Click to expand...
Click to collapse
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
ultramag69 said:
Are you able to rollback?
As long as the bootloader is the same you might be able to go back to an update prior to the problem.
Not 100% sure but I believe the 5th number from the right in the build number is the bootloader version. Just need to make sure it is the same and you might be able to fix...
Sorry if I'm rambling, working on 3 hours sleep...
Click to expand...
Click to collapse
Right, but usually same bootloader version updates are just maintenance or critical security updates only.
Looks like some major changes have happened in the latest update, which could be causing the no call issue.
Just checked, and it's still the same version available.
Version: N970U1UES2BTA1/N970U1OYM2BTA1/N970U1UES2BTA1/N970U1UES2BTA1
OS: Q(Android 10)
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Chiming in late to the game with a Samsung Galaxy S20. I never had this issue with the new OS on my S10 but it started happening with the S20. It's also intermittent. Sometimes it works. I have tried unpairing and repairing. I have tried deleting the bluetooth device and reconnecting it. All to no avail. At least other folks recognize this issue and hopefully Samsung issue an update soon.
i have regerts (spelled wrong to be funny)
winol said:
I am really glad I blocked updates, I am still running on Pie
Click to expand...
Click to collapse
As nice as this phone is--I am annoyed with myself that I upgraded to Android 10--everything worked so great with 9!!! I wish there was a way to go backwards. I might investigate that, actually. I have a little downtime as of late.
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
i have Android 10 ui 2.1 with infinity rom 6.0 rom N975FD and everything works perfect including goodlock 2020
winol said:
I finally updated to android 10, ui 2.0, and, luckly, all is working fine, only thing I notice is that battery seems to last a little bit less…
Click to expand...
Click to collapse
For me, Android 10, whether UI 2.0 or 2.1
battery.... standby, is exceptional good .!
I am a power user, eg theming etc
so i don't worry or have time to worry,
about SOT ETC....
For me what matters is when , my device is sleeping.....!
/ if anything
is draining my device battery etc.
( Ihave about 200./300 apps.)
Suggestion... factory reset or did you already done that.?
See examples of device overnight
standby etc.
kingsfan33 said:
I found a solution!
Google Voice app was the culprit. I uninstalled and so far it has been working for 2 days without issues. Tried this on both my new S20 and the Note 10+.
Click to expand...
Click to collapse
THIS WAS THE FIX FOR ME! I'll have to research why Android 10 isn't playing nicely with Google Voice, but I'm glad I can hit call and it goes though, instead of hitting "send" over and over and over again!!!
S10+ Exynos, running Android 10 stock - same problem. Annoying as hell!
I can't uninstall GV because I use it for international calls.
Edit: BTW - it definitely seems to be affected by connected BT headset. As soon as I turn the BT headset off I am able to make the call (using MPOW headset, don't remember the exact model).
billa said:
But it's happening for others with or without the Google Voice app installed.
You may have had a different issue.
Click to expand...
Click to collapse
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
dhebi111 said:
I have had this issue so many times on my S20+ unlocked. Swipe and touch to call just doesn't work. I saw this thread today when I had multiple call not sent instances. I force stopped Google voice and the problem disappeared. If I have to make an international call, I just to start Google Voice.
Click to expand...
Click to collapse
Are you (were you at the time) connected to a BT headseat? It happens to me only when my headset is connected, and not just one - two different types of headseats and also happened once or twice when the phone was BT connected to my car. As soon as I disconnect the BT, all calls can be completed without a problem.