Charging probelms (plus more) after Oreo update - Samsung Galaxy S8 Questions and Answers

I updated my S8 to Oreo a few weeks back (Samsung Experience 9.0) and ever since I have a plethora of problems.
The main one being that charging the device is now a battle...
I seem to have narrowed it down to using a fast charge power brick (2.0A)
I have tried the official Samsung unit and cable supplied with the phone, and good quality 3rd party cables and plugs....nothing works.
The device does not even register the cables existence.
BUT,
If I use a standard plug (< 2.0A), and a none Samsung cable it will charge
If I use a Samsung cable, it does not. Seemingly regardless of plug.
I've also noticed that the battery life has significantly reduced, come noon time, the deice is ready to be charged, showing less than 50% having been sat on my desk, with little to no use. (I only charge it at this point as I know it wont make it the rest of the day)
Some other issues I've noticed since the Oreo update...Wi-Fi seems choppy, slow and laggy, and I quite often get the " ! " next to the signal status bar icon.
And almost 100% of the time if I try to cast to one of my Chromecast or Google Home devices, the S8 does not see them (connected to same Wi-Fi SSID), meaning if I open Google Home app, and click top right to see my devices, they are....sometimes disabling and re-enabling Wi-Fi will fix this.
I spoke to what Samsung call their 'Tech Support' and it was beyond a joke...their solution...."Turn the phone off and on"...that was it, they could / would not offer any more support than this, and also claimed that I was the only 1 reporting this / these "potential issues"
I had another update pushed to my S8 yesterday (14.05.2018) which according to the docs was released 10.05.18 - G950FXXU1CRD7
This has not helped with anything....
Has anyone else had any of these or similar problems following Oreo update?
Does anyone know of any 'fix' if so?
TIA

While I can't help with most of the problems, see my post in another thread regarding wifi
https://forum.xda-developers.com/showpost.php?p=76518883&postcount=44

Titus_Andronicus said:
While I can't help with most of the problems, see my post in another thread regarding wifi
https://forum.xda-developers.com/showpost.php?p=76518883&postcount=44
Click to expand...
Click to collapse
Thanks for the link, but I've tried cache clears etc and nothing is helping, with any problems.
Last night, my S8 could not find my cast devices whilst my Android tablet could
Sent from my SM-G950F using Tapatalk

Little bump, anyone?
Sent from my SM-G950F using Tapatalk

Valiceemo said:
Little bump, anyone?
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
do you have this Laggy Navigation & Bar os at the same time Bar s8 oreo

MirceaForce said:
do you have this Laggy Navigation & Bar os at the same time Bar s8 oreo
Click to expand...
Click to collapse
Sorry, I'm not following?
I haven't noticed the OS itself being laggy, nor any problems with the nav bar.
Sent from my SM-G950F using Tapatalk

Valiceemo said:
Sorry, I'm not following?
I haven't noticed the OS itself being laggy, nor any problems with the nav bar.
Sent from my SM-G950F using Tapatalk
Click to expand...
Click to collapse
yes it happen after one week of usage after 250 hours of usage
how much is your up time ?

MirceaForce said:
yes it happen after one week of usage after 250 hours of usage
how much is your up time ?
Click to expand...
Click to collapse
No sorry, not seen that.
I've not kept track of my device up time and/o/ usage hours.
I have my device set to auto reboot every Friday.
I guess all I can offer is to advise to use this feature in the settings...maybe open a separate thread of your own?

Valiceemo said:
No sorry, not seen that.
I've not kept track of my device up time and/o/ usage hours.
I have my device set to auto reboot every Friday.
I guess all I can offer is to advise to use this feature in the settings...maybe open a separate thread of your own?
Click to expand...
Click to collapse
stop restart it and you will see the difference

MirceaForce said:
stop restart it and you will see the difference
Click to expand...
Click to collapse
why would I intentionally try and create another problem for myself....
This is a little off-topic now so id ask you start your own thread please so we can get back to the OP topic.
Hopefully someone can help me.

So I have just discovered yet another problem.....
When I connect my S8 to my windows laptop I cannot transfer files...I get a pop up telling me its slow charging.
I've disabled USB debugging in dev. options, not fixed anything.
USB configuration is set to WTP in dev. options.

bump for help.....please!

Related

Android 5.0.1 Changes

While there are several threads announcing the release of Android 5.0.1, in regard to the Nexus 6, most of them seem to be filled with posts relating to the availability, instructions for sideloading, etc.
This thread is to discuss the CHANGES that you have noticed between 5.0 and 5.0.1, and as this is the Nexus 6 section, it should really relate to changes on that device only. You may list changes you've personally noticed, or published changes, but please indicate the source. I, like many of you, no doubt, am very curious to see what is new, fixed, broken, etc.
http://aosp.changelog.to/aosp-LRX21V-LRX22C.html
On 5.0 I kept having the cloud print service or whatever keep crashing, on 5.0.1 I had the Amazon kindle app keep showing a notification Amazon kindle stopped for about 12 hours and had to reboot my phone. (Kept throwing the notification up about every 20 minutes on 5.0.1)
My phone has also been unable to chromecast netflix for the last week and I have to use my gf's nexus 6 to chromecast netflix. Weird little problems with applications on both operating systems.
Edit: Finally re-installed netflix and it fixed chromecasting.
It would be nice to see a list of changes (In language a typical person speaks rather than the jumbled mess that those AOSP changes look like)
I agree. Those AOSP changes are not that easy to understand. Also, they are just to the Android Operating System but doesn't the OTA also contain a new Modem and possibly other driver updates that would fix other issues with our phones? Those fixes and changes would not be in the AOSP list.
On a second note, why does Google do this? They obviously know whats changed. How hard is it to publish a simple list?
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
agentfazexx said:
Is 5.0.1 fixing the slow text/multiple texts sent issue for Sprint users? People are getting my texts like 10 times quite frequently, I read somewhere that this version fixes that.
Click to expand...
Click to collapse
It doesn't.
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
I think I saw there is a new radio... Would be interested to know if signal reception is any better
Sent from my Nexus 6 using XDA Free mobile app
banzaiwolfe said:
It doesn't.
Click to expand...
Click to collapse
What does?
Sent from my Nexus 6 using XDA Free mobile app
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
fdan100 said:
On 5.0 I could not connect to my company’s Wi-Fi (it would show as ‘Saved’ but no connection).
On 5.0.1 I have no issues connecting to the same Wi-Fi.
Click to expand...
Click to collapse
sweet, thanks for letting me know that this works now.
digging in a little deeper
https://android.googlesource.com/platform/external/wpa_supplicant_8/+/1d13911
Work around AP misbehavior on EAPOL-Key descriptor version
It looks like some APs are incorrectly selecting descriptor version 3
(AES-128-CMAC) for EAPOL-Key frames when version 2 (HMAC-SHA1) was
expected to be used. This is likely triggered by an attempt to negotiate
PMF with SHA1-based AKM.
Since AES-128-CMAC is considered stronger than HMAC-SHA1, allow the
incorrect, but stronger, option to be used in these cases to avoid
interoperability issues with deployed APs.
This issue shows up with "WPA: CCMP is used, but EAPOL-Key descriptor
version (3) is not 2" in debug log. With the new workaround, this issue
is ignored and "WPA: Interoperability workaround: allow incorrect
(should have been HMAC-SHA1), but stronger (is AES-128-CMAC), descriptor
version to be used" is written to the log.
Bug: 18411110
Change-Id: I9ae12e8882adc9e785f6e4cef9f30b89bf72dcd2
Signed-off-by: Jouni Malinen <[email protected]>
Click to expand...
Click to collapse
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
The issue with the face unlock camera is fixed.
5.0 is had huge problems in dim rooms buy now no issues
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1
Click to expand...
Click to collapse
I was kinda seeing this too.
N6
land2634 said:
Hell, I'm on AT&T and have the slow text issue. It'll stay stuck on "sending" for 3-4 minutes sometimes. Not sure if it sends multiple times or not, haven't had anyone complain to me that they got the same message several times.
Click to expand...
Click to collapse
FWIW I'm on AT&T and have not had this happen to me even once.
jackpollard said:
I'm seriously noticing my battery is better then it was yesterday before I flashed 5..0.1 I was roughly 34%, which was not really bad, after 12 hours of my normal use. Today, 50%, same time as yesterday. I will keep an eye on it, but thats what I'm seeing. Everything else seems about the same to me.
Click to expand...
Click to collapse
Now that's more like it!
Not sure if it was 501 or the gplay music update, but my music sounds much more clear now. No more cloud print crashes.. Hoping my signal issue was fixed (sprint) but as im deployed right now i only use wifi.
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
cavalier11 said:
Is anyone else having issues adding an exchange email account using the Gmail app? BTW, I flashed my phone to the stock 5.0.1 (LRX22C) version. After returning to complete stock I rooted and flashed TWRP but the issue was present before I made those changes.
Click to expand...
Click to collapse
i am not having that issue with my exchange account and gmail app

help me understand

hi to all how any one that has the same setup will help me understand i will try and keep it short first im using samsung note 4 running 6.0.1 now
ok so here goes i use my gear 2 together with my note 4 as a trusted device you know like every time the gear 2 is close the device must stay unlocked but it does not stay unlocked and there is no Bluetooth disconnecting anything like this i look at that so battery is full the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage but i connect it now and its fine but after a wile (don't know the exact time here ) but say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on and there was nothing like it disconnecting it is as if the phone on its own make sure that it asks the finger print every now and again say like i leave it overnight the next morning first fingerprint then you can use the phone i hate this it kind of bugs me if the steal the phone and the range is to big the device will lock any way why lock when the gear 2 it near the phone any help please
honestly, i stopped reading after few seconds.
have you ever heard about punctuation? - you know, the thing that looks like dots and commas, makes reading much easier.
244 characters in 1 sentence.
wow dude, looks like you dont wanna get helped.
biebie29 said:
...say after 3 hours of no use i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near but it is still on...
Click to expand...
Click to collapse
From the Google Smart Lock support page (https://support.google.com/nexus/answer/6093922):
"Note: When you don't use your phone for 4 hours, and after you reboot your phone, you'll need to manually unlock it with your PIN, pattern or password"
It's a security feature.
EDIT: ...and, wow, yes, that was some run-on sentence!
Is there a root app to disable it or not
biebie29 said:
Hi to all. How any one that has the same setup will help me understand. I will try and keep it short. First, i'm using samsung note 4 running 6.0.1 now.
Ok, so here goes:
I use my gear 2 together with my note 4 as a trusted device. You know like every time the gear 2 is close, the device must stay unlocked. But it does not stay unlocked and there is no Bluetooth disconnecting, anything like this. I looked at that. Battery is full, the gear 2 and phone stayed together and there was no setting like disable and enabling of Bluetooth at any stage.
I connect it now and its fine, but after a while (don't know the exact time here ), say after 3 hours of no use, i press the power button and it asks for my pin or fingerprint as if the gear 2 is not near. The gear 2 is still on and there was nothing like disconnecting. As if the phone on its own make sure that it asks the finger print every now and again.
For example, i leave it overnight the next morning first fingerprint then you can use the phone.I hate this. It kind of bugs me if they steal the phone and the range is to big, the device will lock any way. Why lock when he gear 2 it near the phone? Any help please.
Click to expand...
Click to collapse
Fixed that for you
I really had to break that down to make it readable for me. But as others said, it's an Android feature. Afaik there is no way of disabling that all together. There might be some xposed module i haven't heard of, but with my moto360 i couldn't get it to work the way you'd want. Sorry mate
Kinsman-UK said:
It's a security feature
Click to expand...
Click to collapse
As the programmers use to says: Its a feature, not a bug
Some people are just plain jerks, and I wish XDA would take these "grammar police" trolls a bit more seriously and penalize them.
Perhaps OP is using a translator, or is from another country, or is young. That should not matter to any of us and we should offer our help regardless of whether he/she includes proper punctuation or not. I'm sure the effort he/she put into typing it was much greater than that of the ridiculous responses some of you gave.
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
biebie29 said:
thanks Crossvxm i appreciate that you came up for me its just i love the new 6.0.1 but there are a few new thing that google does not say and i thought it was a bug like my Bluetooth failing
Click to expand...
Click to collapse
The Note 4 is problematic all around, but 6.0.1 is a problem for every device that has it. It is the reason I left my Nexus 6P, and my Nexus 6. I have a Xiaomi Mi Max, also on 6.0.1 and it has the same major flaws I experienced on all devices running 6.0.1. The problems I speak of are the WiFi and Data stop working briefly while browsing the web, or downloading something. However, I believe this is an issue related to the security patches related to Qualcomm devices on 6.0.1. It seems like an overall radio problem.

anyone else experiencing random shutdown issue

Hi there,
I have been experiencing random shutdown on my one plus 5. It happened twice in 15 mins when I was listening to Spotify on my headphones.
Not sure if it's to do with the latest update or not .
Just wondering if anyone experienced this. I have also post on the 1+ community , hoping it's just some software glitch. Overall, it's an impressive phone. Oneplus should sort out there glitches before shipping the product out tho.
Yeah software glitch maybe try resetting your phone ..haven't had random reboots on mine so every device is not having it...if you can ..then replace yours otherwise enjoy it... there's always custom Roms...btw have u updated all software updates yet
Sent from my ONEPLUS A5000 using Tapatalk
wuj15 said:
Hi there,
I have been experiencing random shutdown on my one plus 5. It happened twice in 15 mins when I was listening to Spotify on my headphones.
Not sure if it's to do with the latest update or not .
Just wondering if anyone experienced this. I have also post on the 1+ community , hoping it's just some software glitch. Overall, it's an impressive phone. Oneplus should sort out there glitches before shipping the product out tho.
Click to expand...
Click to collapse
Probably a malfunctioning app, try a safe boot to see if it happens again or data factory reset.
wuj15 said:
Hi there,
I have been experiencing random shutdown on my one plus 5. It happened twice in 15 mins when I was listening to Spotify on my headphones.
Not sure if it's to do with the latest update or not .
Just wondering if anyone experienced this. I have also post on the 1+ community , hoping it's just some software glitch. Overall, it's an impressive phone. Oneplus should sort out there glitches before shipping the product out tho.
Click to expand...
Click to collapse
Do you have the latest update?
Nope all good here.
Happened today to my phone. Weird. Didn't happen again. I guess is a software bug or an app not working well.
Update
It only happened when I was using Spotify when my headphones plugged in.
All good here as well. Hmm. Spotify? That's strange. Have you tried other apps? Like black player?
Sent from my OnePlus 5 using XDA Labs
Hello, it happened to me this night, I was surprised when I woke up that my phone was on the pin-code screen. I didn't shut down my phone just put the plane mode. (4.5.5)
Happens to mine. Maybe 4-5 times since I got it. On 4.5.5.
Like, I will not use my phone, pull it out if my pocket and it'll be black, non responsive. I'm not completely sure if it's shut off already, or just non responsive, and need force shutdown.
Not much more to add than this :b
I have not experienced any random shutting down.
Any fix to that? I've had that happened to mine 7 times already since I got mine on June 26th. I've had the issue yesterday while sending a sticker on Facebook Messenger to a contact, and a couple of minutes before whilst playing Pokemon Go ... this is really borring. The last two times it happened, there was an update waiting to be installed (well, on the german servers at least, since I didn't have the update here in Belgium but once I used a proxy, I could download and install it), not this time tho.
I love the phone but my GF just told me to switch as if she has a problem or if I have a problem and can't use the phone, this would be really bad. I would prefere not to change, so if you guys have a solution, I'm all ears
---------- Post added at 10:15 AM ---------- Previous post was at 10:14 AM ----------
Any fix to that? I've had that happened to mine 7 times already since I got mine on June 26th. I've had the issue yesterday while sending a sticker on Facebook Messenger to a contact, and a couple of minutes before whilst playing Pokemon Go ... this is really borring. The last two times it happened, there was an update waiting to be installed (well, on the german servers at least, since I didn't have the update here in Belgium but once I used a proxy, I could download and install it), not this time tho.
I love the phone but my GF just told me to switch as if she has a problem or if I have a problem and can't use the phone, this would be really bad. I would prefere not to change, so if you guys have a solution, I'm all ears
ive heard somewhere that the power button easily gets pressed when in pocket causing shutdowns or restart
bug hunt
wuj15 said:
Hi there,
I have been experiencing random shutdown on my one plus 5. It happened twice in 15 mins when I was listening to Spotify on my headphones.
Not sure if it's to do with the latest update or not .
Just wondering if anyone experienced this. I have also post on the 1+ community , hoping it's just some software glitch. Overall, it's an impressive phone. Oneplus should sort out there glitches before shipping the product out tho.
Click to expand...
Click to collapse
Hello
We are come from ONEPLUS to check and resolve your issue.
Please capture the log for us:
1. Input *#800# from dialing interface, enter "oneplus logkit", delete history log
2. Click "save log"
3. Reproduce the issue and take a screenshot to record the time, then stay for a few minutes (better above ten minutes)
4. Click “save log” again to stop it, then send us the whole oem_log folder (file manager-storage) along with the screenshots
my email is : [email protected]
Thanks
Biou_Pilgrim said:
Hello, it happened to me this night, I was surprised when I woke up that my phone was on the pin-code screen. I didn't shut down my phone just put the plane mode. (4.5.5)
Click to expand...
Click to collapse
That also happened to me more than twice. Not only in the night. Most time if the phone will be charged. I use only the dash charger. I didn't put it in plane mode. Strange problem. I have no idea why this happens. In this situation the alarm clock or anything else isn't working.
dickdickerson said:
That also happened to me more than twice. Not only in the night. Most time if the phone will be charged. I use only the dash charger. I didn't put it in plane mode. Strange problem. I have no idea why this happens. In this situation the alarm clock or anything else isn't working.
Click to expand...
Click to collapse
Are you on Xposed? It is a known issue, phone reboots when fully charged and connected.
Sent from my OnePlus 5 using XDA Labs
elbuenzurdo said:
Are you on Xposed? It is a known issue, phone reboots when fully charged and connected.
Click to expand...
Click to collapse
Yes. Thanks for the hint.
Edit:
It should be fixed with Xposed 88.2 https://github.com/rovo89/XposedBridge/issues/203
dickdickerson said:
Yes. Thanks for the hint.
Edit:
It should be fixed with Xposed 88.2 https://github.com/rovo89/XposedBridge/issues/203
Click to expand...
Click to collapse
Sent from my OnePlus 5 using XDA Labs
Sometimes my phone switches off whilst uploading a big file to drive
I don't understand why it's happening even in their 5 series. The 3 series has this stupid problem as well. Really frustrating. One Plus needs to get a grip and get rid of this glitch ASAP if they wish to remain in the game.

Oreo is out

Oreo (8.1) is out for the swift 2 range! updating right now
The update wiped all my text messages except drafts. Ensure you back up your SMS beforehand.
swift 2x Oreo upgraded
I can report quick charge broken/malfunction?
I now have to use slower adapter to charge the phone, with the quick charger i now lose power instead of charging!
Dutchman01 said:
swift 2x Oreo upgraded
I can report quick charge broken/malfunction?
I now have to use slower adapter to charge the phone, with the quick charger i now lose power instead of charging!
Click to expand...
Click to collapse
It's a common issue and the update has been paused to solve this problem.
Abdullah S.A. said:
It's a common issue and the update has been paused to solve this problem.
Click to expand...
Click to collapse
This is why I have been on Oreo now for over a week. OK it's on a different phone (Nokia 6.1) with everything working well.
MAybe the 4 beta testers in Nederland missed this issue?
I liked the phone and what Wileyfox were doing but that changed with STK. Shame really.
Good luck and hope they sort out the update soon.
Dutchman01 said:
swift 2x Oreo upgraded
I can report quick charge broken/malfunction?
I now have to use slower adapter to charge the phone, with the quick charger i now lose power instead of charging!
Click to expand...
Click to collapse
I don't have quick charge issue on Swift 2X.
@ttpro (LEX720)
divvykev said:
This is why I have been on Oreo now for over a week. OK it's on a different phone (Nokia 6.1) with everything working well.
MAybe the 4 beta testers in Nederland missed this issue?
I liked the phone and what Wileyfox were doing but that changed with STK. Shame really.
Good luck and hope they sort out the update soon.
Click to expand...
Click to collapse
In fact they were 8 beta testers, wileyfox belgium requested another 4 lol.
Glad to hear you bought a new phone, enjoy it!
bujok said:
I don't have quick charge issue on Swift 2X.
@ttpro (LEX720)
Click to expand...
Click to collapse
Me neither, but a lot if people are having this issue
What is known about the second wave of updates?
Tberious said:
What is known about the second wave of updates?
Click to expand...
Click to collapse
It will fix some issues that have been found in the first one.
Abdullah S.A. said:
It will fix some issues that have been found in the first one.
Click to expand...
Click to collapse
Is there any imformation on dates of update? Will it be for 224B only or for 373J as well?
Tberious said:
Is there any imformation on dates of update? Will it be for 224B only or for 373J as well?
Click to expand...
Click to collapse
I do not know, probably after two weeks
New version is available to download!
Abdullah S.A. said:
New version is available to download!
Click to expand...
Click to collapse
do you have link already?
noiz13 said:
do you have link already?
Click to expand...
Click to collapse
Sorry mate i don't, but ur idea is great tho. Download the buggy uodate, install it, update to the latest one
Download the official Recovery SW82-WF-MARMITE-8.1-UOS273C-RECOVERY.zip from:
https://we.tl/lVLRdtfdJb
sha256: 72a0786998ac197c8deefa3433162a15d79c9f90e8bb2539a1755cded277cd2a
I updated my Magisk-Rooted Stock 7.1 by flashing using twrp - without dalvic-deletion - and reinstalled Magisk 16 right afterwards.
Everything works, but you will lose any previous received SMS.
fred0r said:
Download the official Recovery SW82-WF-MARMITE-8.1-UOS273C-RECOVERY.zip from:
https://we.tl/lVLRdtfdJb
sha256: 72a0786998ac197c8deefa3433162a15d79c9f90e8bb2539a1755cded277cd2a
I updated my Magisk-Rooted Stock 7.1 by flashing using twrp - without dalvic-deletion - and reinstalled Magisk 16 right afterwards.
Everything works, but you will lose any previous received SMS.
Click to expand...
Click to collapse
(you also lose them with the OTA - just fyi)
Charging problems
Hi there.
Last week, I got the OTA update for my Swift 2 Plus. Now, when I try to charge the phone I observe massive problems.
1. Charging with Quick Charge 3.0 does not appear possible. There even observe a reduction of the battery charge when connected to the charger.
2. Charging with a standard fast charger (2.1 Amps) is not really fast. It gives me about 25-30% overnight, if I switch off the phone.
3. Charging via the USB port of a computer is hardly possible. (It is at least so slow that no progress is recognizable.)
I tried already different chargers and different cables, without any improvement. The same chargers and cables work perfectly with two other identical phones (but without the update) and before the update, I did not observe any problems when charging my phone with the various chargers and cable. I also tried to clean the contacts on the phone, without any improvement, too.
The update which was offered to me was already the one of the second round. I understand (and observed myself) that the first update was withdrawn again, because of battery charging problems.
Is anyone aware of a (convenient) solution for my problem?
1. So far, I tried to get a solution from Wileyfox support. I guess that I don't have to tell anybody that my experiences with the support a more than disappointing. Several times I got the answer that my problem is forwarded to the Senior Team Leader who will get back to me shortly. (I'm still waiting, at least for a specification of the term "shortly".)
2. I also tried to connect the phone to the computer in order to save the relevant data and in order to check if I can transfer an update filed to the phone (with the idea to carry out an update manually). However, the phone is not recognized by the computer. The different options und USB-settings do not have any effect. (Note that developer mode ("Entwickleroptionen") is activated, of course.)
3. I considered to try the factory reset. However, it is not clear to me how a can assure, especially under the given circumstances that no data connection to the computer can be established, that I can restore my phone to the current status (with all apps, app data and documents) again.
Your help would be highly appreciated.
Thanks to everbody in advance.
Lacky
LackyLake said:
Hi there.
Last week, I got the OTA update for my Swift 2 Plus. Now, when I try to charge the phone I observe massive problems.
1. Charging with Quick Charge 3.0 does not appear possible. There even observe a reduction of the battery charge when connected to the charger.
2. Charging with a standard fast charger (2.1 Amps) is not really fast. It gives me about 25-30% overnight, if I switch off the phone.
3. Charging via the USB port of a computer is hardly possible. (It is at least so slow that no progress is recognizable.)
I tried already different chargers and different cables, without any improvement. The same chargers and cables work perfectly with two other identical phones (but without the update) and before the update, I did not observe any problems when charging my phone with the various chargers and cable. I also tried to clean the contacts on the phone, without any improvement, too.
The update which was offered to me was already the one of the second round. I understand (and observed myself) that the first update was withdrawn again, because of battery charging problems.
Is anyone aware of a (convenient) solution for my problem?
1. So far, I tried to get a solution from Wileyfox support. I guess that I don't have to tell anybody that my experiences with the support a more than disappointing. Several times I got the answer that my problem is forwarded to the Senior Team Leader who will get back to me shortly. (I'm still waiting, at least for a specification of the term "shortly".)
2. I also tried to connect the phone to the computer in order to save the relevant data and in order to check if I can transfer an update filed to the phone (with the idea to carry out an update manually). However, the phone is not recognized by the computer. The different options und USB-settings do not have any effect. (Note that developer mode ("Entwickleroptionen") is activated, of course.)
3. I considered to try the factory reset. However, it is not clear to me how a can assure, especially under the given circumstances that no data connection to the computer can be established, that I can restore my phone to the current status (with all apps, app data and documents) again.
Your help would be highly appreciated.
Thanks to everbody in advance.
Lacky
Click to expand...
Click to collapse
Hi!
Did you try to install a service COS13.1.5 ROM via QPST? I think it can resolve your problem, but ater this better to do not upgrade to 8.1 untill Wileyfox doesnt fix this bug.
nikith290 said:
Hi!
Did you try to install a service COS13.1.5 ROM via QPST? I think it can resolve your problem, but ater this better to do not upgrade to 8.1 untill Wileyfox doesnt fix this bug.
Click to expand...
Click to collapse
Thanks for your answer.
No. Definitely not. I have never heard of this possibility.
I have to investigate firstly how this installation can be carried out. I fear, if the installation requires the transfer of the ROM onto the phone via USB, that the lack of a data connection between the computer and the phone might finally prevent me from succeeding with this option.

"Searching for Android Wear updates" notifications

hello,
as the title says, i get these notifications all day long..
they appear for half a second and are gone before i can click on them.
the attached notification log shows that they pop up in irregular intervals, sometimes several times a minute.
i tried to disconnect and reset the watch, but the issue remains.
the problem came up just recently, but i didn't notice any updates.
any ideas what i can do?
watch: misfit vapor (fossil brand), android 8.0, wear os 1.5 (idk why it's not labled 2.something anymore, but it's definitely not the old 1.5 without playstore and so on..)
phone: sony xperia x compact, android 8.0
seems like a secomd reset made it a bit better.. now i get the notifications about 20 times a day..
what can that be? how often is normal?
could someone please check his log?
to get access you might have to enable developer options, then place a homescreen widget for settings -> notifications log
nobody?
xda isn't what it used to be...
I noticed the same. I belive it started after recent update of Google Wear.
I just installed Notification Saver app (my phone does not have notifation log option) and will revert back once I collect some information...
armsel said:
...will revert back once I collect some information...
Click to expand...
Click to collapse
Yeh, it is checking a lot sometimes, sometimes not that much (6 times a day yesterday!).
But today a lot more (attached picture)!
This is not normal...
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
A.D.I.O.S said:
thanks for the info, so it's a google problem.
i reported it now via the feedback button in the wear os app and i suggest you do the same.
hopefully they fix this soon..
Click to expand...
Click to collapse
I just did - although today it had only checked twice (so far), let's see...
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
A.D.I.O.S said:
yesterday i had about 70 checks..
it's so annoying an i think it's also draining the battery..
how about you @armsel ? problem still present? did you hear anything from google?
Click to expand...
Click to collapse
Nope, noting and I don't think they will ever revert back...
I didn't use my watch the past week or so... let me see next week if the problem persists.
just updated to wear os 2.0..
still the same..

Categories

Resources