Hi everyone,
when I'm using AA and I unlock the phone, AA immediately goes down and few seconds later come back;
it's the same of removing the USB-cable and put it back. I'm sure it's not a cable problem, but a software one..
This problem started after the latest Samsung Galaxy Note 10 update was installed.
thanks to everyone will help me
EDIT: I tried to disinstall and reinstall AA; Clear cache of the entire phone by (stock) recovery; and many other attempts.
Phone - Samsung Galaxy Note 10 (Stock, no root)
Car - Audi A3 2020
Shandroid, I think it's the same issue as in this one:
AA Shutting down after screen unlock
Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place. I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I...
forum.xda-developers.com
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works
__Michael__ said:
I can confirm that the issue is related to the last Sammy update , I have downgraded to may update , now aa works
Click to expand...
Click to collapse
so no solutions for this problem except downgrade?
Hi, still no solution ? It's really annoying
I have read on other forums that Google has acknowledged an issue here, and that they have provided a fix to Samsung which should be included in the July patch. I was anxiously waiting for this fix, but after applying it, the problems is still not fixed on my EU Note10+. Anyone else who still has the AA problem on Samsung after applying the July patch?
gschot said:
I have read on other forums that Google has acknowledged an issue here, and that they have provided a fix to Samsung which should be included in the July patch. I was anxiously waiting for this fix, but after applying it, the problems is still not fixed on my EU Note10+. Anyone else who still has the AA problem on Samsung after applying the July patch?
Click to expand...
Click to collapse
Still have the problem instead of july patch installed.. don't know what to do to solve..
Shandroid_94 said:
Still have the problem instead of july patch installed.. don't know what to do to solve..
Click to expand...
Click to collapse
I guess wait for the August patch and see if it is fixed there. I must say that I find the AA connection very unstable anyhow, many spontaneous disconnects/reconnects.
gschot said:
I guess wait for the August patch and see if it is fixed there. I must say that I find the AA connection very unstable anyhow, many spontaneous disconnects/reconnects.
Click to expand...
Click to collapse
Let's see for August patch then
gaurika said:
Shandroid, I think it's the same issue as in this one:
AA Shutting down after screen unlock
Hi all guys, I've been missing a long time from here, so please be care enough to forgive me if I posted the thread in the wrong place. I'm currently using Android Auto and enjoying very much the amazing work made from Gabriele (AAAD, of which I...
forum.xda-developers.com
Click to expand...
Click to collapse
August patch did fix the issue! S10e
SOLVED with the ultimate security patch 1, August on my Note 10!
Fixed also for S10+ with August '21 patch. Finally!
Related
I've been having an issues with call forwarding since FlashFire update to Android 5. When I attempt to change the settings, I receive an "ERROR Network or SIM Card Issue" message. I checked with ATT technical support and they say this is a known issue with the ATT 5.0 update and they will release a patch for it soon. Does anyone know if we here at XDA will get a flashable patch as well? Thanks!
STraver said:
I've been having an issues with call forwarding since FlashFire update to Android 5. When I attempt to change the settings, I receive an "ERROR Network or SIM Card Issue" message. I checked with ATT technical support and they say this is a known issue with the ATT 5.0 update and they will release a patch for it soon. Does anyone know if we here at XDA will get a flashable patch as well? Thanks!
Click to expand...
Click to collapse
It might be worth waiting for them to actually release the patch before you go asking if we'll get it, seeing as they have no idea what the patch will be there's no telling if you will.
Rakuu said:
It might be worth waiting for them to actually release the patch before you go asking if we'll get it, seeing as they have no idea what the patch will be there's no telling if you will.
Click to expand...
Click to collapse
Ha! Good point. Thread closed.
I think I'm going to flashfire the Alliance ROM since that's not specifically based on the ATT version, it may not have that issue.
Samsung Device Support says that the current OTA update to 5.1.1 (G890AUCU3BOJE) fixes this issue for some, but not all devices. Reportedly Google is working on a patch, but no release date is available at this time. For me the issue started when moving from 4.4.2 to 4.4.4. I'm currently on 5.0.0 and still have the issue, still debating about rolling the dice on a flash to 5.1.1 to see if I am one of the lucky ones. Until then, GSM feature codes can be used:
http://www.geckobeach.com/cellular/secrets/gsmcodes.php
This morning i woke up and got a OTA Update notification http://i.imgur.com/3bBF2XB.png
I have not updated it yet cause my phone is rooted with TWRP.
according to sprint page, current version is L720VPUGOK3 its just bunch of bug fixes
Anyone else know whats included in the update or is it just bug fixes?
PritpalS said:
This morning i woke up and got a OTA Update notification http://i.imgur.com/3bBF2XB.png
I have not updated it yet cause my phone is rooted with TWRP.
according to sprint page, current version is L720VPUGOK3 its just bunch of bug fixes
Anyone else know whats included in the update or is it just bug fixes?
Click to expand...
Click to collapse
I've found that the carriers don't know what the hell a proper changelog is, regardless of device. I hope you are successful in finding out what the actual changes are.
Sent from my DROID Turbo using Tapatalk. Now powered by Android 5.1.1 and CyanogenMod 12.1, as well as the Google Apps Infrastructure
Hello. I installed CM13 on my S3 I9300 yesterday and it works flawlessly. The problem is with Xposed though. I installed it and updated it without any problems, no bootloops. But after I ENABLE the downloaded Module, I am required to reboot the phone, but it just stays in the boot loop, so I am required to use the Xposed uninstaller. Any suggestions??
@.ALph4.
You did not have to create a topic without first looking at the discussion of xposed for marshmallow, verifying for sure I'm having the same problem.
This was due to the new security patch of the month of November, causing bootloop when activating the modules. If you want to use xposed I advise you to try a previous version of cm13, I believe that from the 13th of that month, all will give this error, try one of the previous day.
EsromG5 said:
@.ALph4.
You did not have to create a topic without first looking at the discussion of xposed for marshmallow, verifying for sure I'm having the same problem.
This was due to the new security patch of the month of November, causing bootloop when activating the modules. If you want to use xposed I advise you to try a previous version of cm13, I believe that from the 13th of that month, all will give this error, try one of the previous day.
Click to expand...
Click to collapse
So do you think it will get fixed soon? Because I don't really wanna roll back right now and I can wait. Tnx for telling me this.
.ALph4. said:
So it should get fixed in few days? Because I don't really wanna reroll right now and I can wait. Tnx for telling me this.
Click to expand...
Click to collapse
Press the thank you button to really thank
On the issue correction, we must wait, it all depends on the time and patience of the developer of xposed, as I believe the cyanogenmod team will not change the security patch for this.
EsromG5 said:
Press the thank you button to really thank
On the issue correction, we must wait, it all depends on the time and patience of the developer of xposed, as I believe the cyanogenmod team will not change the security patch for this.
Click to expand...
Click to collapse
As long as they can fix it I am fine with waiting. Good to know that it isn't just my phone... Thanks man.
Just to be clear, it worked just fine before that November security patch??
Edit:F*** them. https://forum.cyanogenmod.org/topic...loop-when-modules-are-enabled/#comment-614420
Moving to Resurrection Remix.
.ALph4. said:
Just to be clear, it worked just fine before that November security patch??
Edit:F*** them. https://forum.cyanogenmod.org/topic...loop-when-modules-are-enabled/#comment-614420
Moving to Resurrection Remix.
Click to expand...
Click to collapse
F them for not supporting third party modifications and prioritizing security updates?
Sent from my Nexus 6P using XDA Labs
Hello.
Just wanted to mention, that today a new update reached my phone.
8.0.0.132 (C432) 2018.07.17:
Bugs: not tested yet
Fixes: ?
Date of Security Patch:
01.06.2018
Changelog:
This update adds the eRecovery feature and integrates Google security patches.
[System]
Adds the eRecovery feature to aumatically fix startup failures.
[Security]
Integrates Google security patches released in Jun 2018 for improved system security.
Click to expand...
Click to collapse
Old updates:
8.0.0.131 (C432) 2018.05.25:
Bugs:
?
Fixes:
?
Date of Security Patch:
01.05.2018
Changelog:
Google security updates May 2018
8.0.0.130 (C432) 2018.05.04:
Bugs:
-
Fixes:
Mirrorshare works again!
Date of Security Patch:
01.04.2018
Changelog:
Security Updates only.
Old:
-------------------------------------
8.0.0.128 2018.03.30:
Bugs:
Mirrorshare (sudden disconnect after establishing a connection)
Date of Security Patch:
01.03.2018
Sadly no changelog yet, but with this Update honor introduced faceunlock in Europe. :silly:
To activate it, go to:
Settings
Security & privacy
Face unlock
Then follow the instructions.
-------------------------------------
Greetings
Vsrookie
It seems that you are on the lucky side. I do not get a new Update on my device here in Germany.??
Weired... Always thought they deliver for every device?
vsrookie said:
Weired... Always thought they deliver for every device?
Click to expand...
Click to collapse
No nothing for the UK yet either.
The Huawei Servers actually have the Version 129 (Date: 02.04.2018). Unless we are getting a new Version via the OTA Update we should wait. For me it seems that these versions are still not final.
New build on fwf 129 2/4 but says not for device when check with imei
Sent from my LLD-L31 using Tapatalk
Hi.
Seems like the latest Update (128) broke my mirrorcast/streaming.
In the Update before it worked flawless.
I checked with Chromecast and a Sony and Samsung Tv.
Ive tested the Samsung TV in two different Networks.
In every test my device connects and disconnects immediatly.
Really annoing. Since my device is not routed its hard to investigate.
Greetings
Vsrookie
Just got update notifications 128 safe to update? what's new nothing in change log
Sent from my LLD-L31 using Tapatalk
Actually got face unlock in update nice
Feels very smooth will see over time if lag appears or also fixed
Sent from my LLD-L31 using Tapatalk
xzyk said:
No nothing for the UK yet either.
Click to expand...
Click to collapse
Can confirm now got the 128 update today 10Apr18 in the UK.
xzyk said:
Can confirm now got the 128 update today 10Apr18 in the UK.
Click to expand...
Click to collapse
Just arrived for me today, too. LLD-L31, Germany, plus FaceUnlock and Security Patch from 01.03. Very nice...
Seems smooth and battery better still get little judder lag transitioning from Google now feed back to home this could just be down to pixel launcher
Sent from my LLD-L31 using Tapatalk
me too got update notifications b128, no changelog...
not yet updated
EDIT: updated to b128, it seems smoother and better battery
After receiving version b128 ist seems that my WiFi connection ist getting Buggy. I have to reboot at least one a day to re-establish the WiFi connection.
n1v4 said:
After receiving version b128 ist seems that my WiFi connection ist getting Buggy. I have to reboot at least one a day to re-establish the WiFi connection.
Click to expand...
Click to collapse
Not had that issue maybe a clear cache in recovery fix or factory reset see if continue after
Sent from my LLD-L31 using Tapatalk
new camera software build too, with new options (AR lens) for kids.
Hi.
Can anyone confirm this?
vsrookie said:
...
Seems like the latest Update (128) broke my mirrorcast/streaming.
In the Update before it worked flawless....
Click to expand...
Click to collapse
Thanks!
Greetings
Vsrookie
Not had this yet on my UK device.
Is it possible roll out has been paused due to the issues listed on here? Why the 2 versions?
Any more UK users had this update yet?
jusumgeezer said:
Not had this yet on my UK device.
Is it possible roll out has been paused due to the issues listed on here? Why the 2 versions?
Any more UK users had this update yet?
Click to expand...
Click to collapse
I'm in UK had update on first device had to take back as had rattle and new one got update out the box as well
Sent from my LLD-L31 using Tapatalk
Still no OTA for me but interestingly the firmware finder tool now lists a new version for April security patches with version number B130
Received this today;
BSGL View attachment 4817271
Sent from my SM-G973U1 using Tapatalk
Yes. Same deal here after flashing U1 on Sprint phone?
I am on the AT&T firmware and have had this update for weeks now.
StoneyJSG said:
I am on the AT&T firmware and have had this update for weeks now.
Click to expand...
Click to collapse
Yes, Unlocked units get the updates after Carrier models, just curious why it is still showing August Security Patch when I already had the August Security Patch with the last update? Strange
Sent from my SM-G973U1 using Tapatalk
It may of just been something Samsung forgot to add in or patch and thus threw out a new update for it with the same security patch. That's my guess anyway.
StoneyJSG said:
It may of just been something Samsung forgot to add in or patch and thus threw out a new update for it with the same security patch. That's my guess anyway.
Click to expand...
Click to collapse
That's what I think. I don't remember the size of the first one, but I thought it was smaller than the second one.
I am still on ASGK, but I know soon AT&T will force me to whatever firmware is next whether I want to or not. A$$holez!
Just use a package disable and disable software update. I just recently updated but only when I enable it. I however I'm so sick of not having root or custom rom support and after I update it totally screws up my android auto and a few other apps after updating I may never update again. Does this mean we can install twrp recently? I really don't care about Knox and other samsung apps except for galaxy wear and maybe shealth for my insurance.
I don't see any strong reason to do rooting and custom ROM for my S10 as everything are already there with the stock OS from Samsung.
I did this update and not have l having trouble getting on lte.. what could I do to fix this? I'm on TMobile with unlocked phone.