Database Users

[FW] New Firmware 2.3.26

So I was trying to get the new 2.3.20 firmware and I went to the Archos website. But it looks like there was a new firmware posted this morning. 2.3.26.
I don't know how to direct link, but i'll try.
http://update.archos.com/8/gen8/gen8_2.3.26/firmware_archos_android_gen8.aos

Version 2.3.26 - April 21st, 2011
Wi-Fi: fix cannot scan on an access point above channel 11 regression
Phone tethering: fix TCP/IP header compression setting crash
System stability: avoid Android reboot in case of missing audio
Media library: fix media libray not updated on hard drive based A70
Notification: decrease low battery notification volume
Application: attempt to solve Pandora application not able to switch songs
Application: solve music lag in applications using OGG format
Bluetooth GPS: increase compatibility with 3rd party applications
Display: avoid white/black screen happening sometimes when switching back the display on

Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.

Techngro said:
Thx jknut, i'm such a noob I forgot to post the changelog. I usually wait till theres a uruk version, but i'm gonna install now cause i'm fairly sure we'll get uruk in a couple of days.
Click to expand...
Click to collapse
Not that much of a noob, you posted the link to the firmware that should end my buggy horrors
Thanks jknut for the changelog

Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha

sw6lee said:
Hi, I have one question.
If I have the permanent root from churli (I'm sorry if I miss-spelled it..), do I just updated it regularly? I used to update all the firmwares by just downloading the firmware right on my A70 and install it right away.. but will that work if I have the root? I just rooted my A70 yesterday...and I'm a newbie haha
Click to expand...
Click to collapse
I just followed Steps 2, 3, 4 of Chulri's post. Chulri already has the new files for "fw 2.3.26 +rw" for Step 3. I like the optional Step 4 because I don't have to worry about holding down the volume button everytime I boot to get root.

Hi,
Has somebody tested this new release?
I updated to version 3.2.20 last week and I was very happy when I realized that cinema plugin was not required to play all the formats which I was not able to before the update (AAC, AC3, MPEG2, etc)
Can somebody confirm if this has not been "fixed"?
Thank you.

Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.

toyface said:
Well I have tried this new release and all I can say is bootloop, oh and to top it off I think that my right speaker has blown.
Archos I hope you're reading this, you need to sort your firmware releases out. Whilst you're at it Gingerbread would be nice. If you can put it on the Arnova with inferior hardware you have no excuse but to port it to the 101.
Click to expand...
Click to collapse
I just noticed the update when I went to the archosfans 2.3.20 bugs thread to report wifi drop powersave disabled while running tunein radio...
OTA update went fine, just waiting for A43 to charge up, then I'm going to do the A32 as well...
[EDIT]
Power LED blinking -> UI batt meter (and About Device) say 98% charge...
had this once with 2.3.20 showing 97% when LED blinking but next charge and thereafter showed 100% when LED blinking...
[/EDIT]

I had this Problem from the first day.
LED blinks and the battery show around 90%.
If i unplug the power the status goes to 98-100%, most 100%.
If i reboot the device with plugged power, the status is 75-90% after restart.
Sometimes the status falls to 87-91% if i plugged the power in.
I can live with it, but it is annoying.

did they remove bluetooth PAN tether ? I had dun/pan option while setting up BT tether with 2.3.20. but now no more that option. the probken for me is, i am using cdma phone(bell htc touch) but with BT DUN the Archos cannot dial CDMA number #777. I set bell APN (pda.bell.ca) it's not working. Actully even if it works I worry about it because it may charge me more.
Before with 2.3.20 , it worked perfect with BT PAN and my phone set to Internet sharing.

This update cleared up my waking-up issue.
It's pretty much an instant on now after the monitor idles off. Before, (after being off for more than a few minutes) it was a crap-shoot as to whether or not the screen would come on and I often had to fight with it and double, triple, quadruple tap the power button to get things alive. No longer.

still reboot cycles problems when charging the 101..problem started with these last 2 updates.

twit.tv app FCs all of the time with this fw...
I wonder why they released this one OTA as it seems to be more broken than .20 was...

youtube and many other flash video played in the browser hangs after about 15 seconds or so. Soemtime this causes the whole system to freeze requiring forced reboot.
This is the worse build so far, my A70 was most stable at 2.1.08.

Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.

Techngro said:
Wow. I am having the exact opposite experience with this firmware. I find the browser and flash to be very solid. Before I could never play even youtube mobile in HD without it freezing and forcing a hard reboot.
Also, i'm having less general freezes.
I am still having absolutely no luck whatsoever with tethering to my Android phone (cliq). It's driving me crazy cause this was one of the main reasons I went with Archos.
Have you guys done a full reinitialization? That's what I did and, even though it's a pain to reload all your files, it might help with many of the problems you are having.
Click to expand...
Click to collapse
As a matter of fact I did an Android reset to get away from some of the problems I was having with bootloops and such. This has helped with the general performance of the 101, which I'd say is down to the 64mb swap file I now enjoy.
I did have a couple bootloops until I enabled a lock screen pattern unlock and I have now experienced nothing but fairly good performance

It seems that 2.3.26 is different from vesions before

Need more language for External Keyboard Layout such as Thai

jakkrith said:
Need more language for External Keyboard Layout such as Thai
Click to expand...
Click to collapse
You'd probably be better off posting in the archosfans.com forum's bug list thread for 2.3.26 as Archos employees actually monitor that site and have actually even started some of the buglist/fw release threads... i.e. I'm not sure that they're even aware of the xda-devs gen8 section and even if they were would they bother to read it...

thinks its charging....

so i've noticed multiple times today (just got it yesterday, rooted) that the charging indicator flashes on and off. this keeps bringing it out of standby. although sometimes the screen turns on without it saying charging but that seems to be a known issue.
but whats up with the charging flashing

full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?

Strange
Never had this issue on my a500 - but have the exact same issue on my Samsung Intercept with a slightly damaged charging port - after unplugging the system will still show as charging and offer to mount as an external storage device - even though it's not plugged into anything.
Had the random screen on when I was still on a 3.0 based rom - have you registered your tablet with Acer and upgraded ota to 3.1? Can also manually flash 3.1 update.
best of luck!

i just updated my last post,
but yeah im on the latest ota 3.1 in the US and registered

lbhocky19 said:
full reset and its still doing it
actually i think it has to do something with rooting
i used this http://androidflip.com/how-to-root-acer-iconia-a500-with-stock-honeycomb-3-1/
but i unrooted and uninstalled and its not doing it now....
any other root method for 3.1?
Click to expand...
Click to collapse
Yes! Easy as hell too.
Check this out, and good luck!
(How to root a500 3.1 stock)
http://forum.xda-developers.com/showthread.php?t=1138228
(Edit: the method you linked to looks like the same method described here at XDA. May not solve your problem)

well cancel my happiness. did a reboot and now it fully thinks its charging. no flickering.
even plugged it in and unplugged and still says charging.
this time i plugged it in and rebooted. at least the notification went away
edit: and its back.

really strange....
May want to just return it and snag a new one if that is easy/possible.
After your full reset did you do any Modding/install any apps? May be possible something you are running is causing the issue, but I am really stumped on this one.
Could always get cwm running and reset the battery cache, but I am pretty doubtful that is gonna do anything.

same problem for me here.though I did not root my device yet.it shows charging with no charger plugged in.also recognized that my battery indicator sometimes remains on a certain percentage and hangs.after a restart it shows the actual battery level.I am on stock rom 3.0.1...maybe I send it back tomorrow.because this is really enoying...

yup. mine just started doing the hanging at one percentage til reboot

don´t know if it´s software or even hardware related

the fact that we have identical problems makes me think software

[Q] N4 USB stopped working yesterday

I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.

I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this

BigDig said:
I`m pretty sure it`s your cable....It happened to me the 2 months after purchase! Probably if you plug it in a wall ac charger it will say USB charging instead of AC! That`s what happened to me. I`m using my good old G2X usb cable and no more problems like this
Click to expand...
Click to collapse
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course

Ankst said:
The same cable works fine with with my Galaxy Nexus as well as my Nexus 7. Also I use different cables across different computers with the same working result with multiple devices, except the N4 of course
Click to expand...
Click to collapse
Try a different cable and see what happens! It won`t hurt...

BigDig said:
Try a different cable and see what happens! It won`t hurt...
Click to expand...
Click to collapse
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.

Ankst said:
Ok ok, I tried it, no luck. I'm starting to wonder if a windows update could have done this. It just makes no sense that other phones/tablets work with the same driver and this was working fine yesterday. Windows definitely sees the phone, but regardless of what signed or unsigned ADB/composite driver I try, it still has a yellow exclamation mark. But when I plug in the N7, no problem at all. There are many ways to get data to my device, so at the end of the day it isn't the end of the world, but it still frustrates me. I just purchased a second N4, still sealed in the box as a gift for the wife, so my only concern now is being able to unlock the bootloader on that phone so I can throw a rooted ROM on it. If I can't see that device, then I have issue. But I suppose since it'll be new out of the box, should that happen, I can turn to the Goog for support on that one. I'm just positive that there's somebody here smart enough to figure out why this has happened I've seen more complicated issues resolved.
Click to expand...
Click to collapse
I would have tried to flash another kernel if I were you to see if the problem persists

When I connect my N4 to my PC, it shows up in device manager as as a portable device and mtp works fine. Checking the driver version shows that it is using WMP drivers. When I turn on usb debugging, that connection gets added as other devices in device manager with a yellow exclamation point. My device is detected since it will pull the serial number in a command prompt. I haven't tried anything thru adb yet, but for accessing your folders on storage, that would be the mtp as portable device connection anyways. The key thing is making sure that you are getting that connection and using the WMP drivers, not the Android usb drivers.
Sent from my Nexus 4 using Tapatalk 4 Beta

Ankst said:
I have always been able to find an answer to the problems I've encountered, but this one has me stumped. I have owned and rooted and tinkered and broken and fixed every nexus phone, all because of the help I can find here. So first off, thanks for all the years.
My new problem. Yesterday morning I plugged in my Nexus 4 like I always do, and tinkered with my music folder (added and removed a few tracks, like always) and then drove to work happily listening to my music. When I got home late last night, I popped onto AP and read about a new play store apk, 4.1.10 and installed it (just like I always do when I can grab it sooner than OTA). That is the ONLY change to my phone from yesterday to today. When I plug my phone in to my computer today, I get the "windows doesn't recognize this device" message. So, I do the usual, I fire up the SDK Manager, update all the required bits of the SDK, pop into a device manager, find the unrecognized device, update driver and point it the google/usb_driver folder because that's what has always worked when running into this quirk. So today, nothing happens. Phone still isn't seen by Windows. I have the luxury of 3 computers (one of which is Ubuntu) and a laptop to test on, and all 4 say the same thing today. All 4 have also always worked without issue. I have a Nexus 7 as well, and it has no problems across the 4 computers, but I have not updated the Play Store on the N7 (and now I'm concerned if I do this will happen).
So I start searching to see what others are saying, and I've found that many people have *just* run into this problem (across various forums etc.). I also notice that on my N4, even though USB debugging is enabled, it's not working (as in the jelly bean icon in the notification bar doesn't even show up now). And switching between MTP and PTP makes no difference either. I've uninstalled the unrecognized device and hoped windows would find it on it's own again, but nothing. I cannot access the phone via ADB (or communicate via fastboot) and literally have no way to see the phone. I wouldn't call myself an expert by any means, but I have always been able to get through manual rooting, custom ROMS, flashing radios and bootloaders on every phone in the past. What am I missing here? Is it possible that the latest play store update has somehow "broken" the USB function? I use bigxie's JDQ39 odexed ROM, and so do many of my friends (I'm the guy they come to), and not had an issue until today. Does anybody out there have any idea why this happening? And to so many people within the past few days? Also, when I try to revert to the 4.1.6 version of the Play Store, it will not allow me to install a previous version. Since that's the only thing I can attribute this change to, who can tell me how to do that?
I appreciate anyone who digs into this, and if there's any info I can provide to help you help me, just let me know!
Edit: Used TB to uninstall the play store and reinstall 4.1.6, unfortunately no change.
Click to expand...
Click to collapse
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4

tyea said:
My situation is exactly like yours, for two PCs that used to recognize my N4. I tried another N4 that is stock and not rooted, and to my frustration it connected perfectly (MTP, adb, Fast boot). Something has corrupted our phones. Another symptom I have is I can only charge at USB rate with ac chargers that used to charge at ac rate. All this occurred around the 15th of May, when Google pushed the play store update. I haven't tried unrooting yet. I'm hesitant to get to bold on experimentation because I can't flash the phone with the PC anymore.
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!

Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4

Ankst said:
I knew I wasn't crazy! I understand your apprehension for experimentation, I sorta feel the same way. However, I've put some ROMs in some online storage and already put them on my device so I'm going to take the leap and hope I don't do any permanent damage. I've already overwritten my existing ROM more than once to see if it would correct it. So I have a different devs stock rooted ROM to try and a copy of CM 10.1 R3, I'll run those today and see if the suggestion of changing the kernel has any impact. I know there's a solution to this!
Click to expand...
Click to collapse
Ok, so here's my progress, and ultimately my conclusion. I just wiped and tried another stock rooted rom by teshxx, it wouldn't even boot. So, CM was my last hope. Again, wiped and installed CM 10.1 RC3 , flashed gapps, and it booted up. There was still some issue with some of the google services, but fixed easily enough by uninstalling them and reinstalling them from the play store. When I plug it into a computer, I *still* have the "usb device not recognized" error in windows. And usb debugging still doesn't activate even though it definitely sees usb as the connection by looking at the battery settings. I realize that charging through usb is a different voltage etc. and why it knows has no relation to usb debugging reacting to the usb cable. That being said, I have to conclude that by some freak of nature, the data path through the usb port on the phone has stopped working. Perhaps a power spike? Maybe there is a god and he hates me? I don't know, but seeing as CM would have rewritten the kernel as well, this is about as far as I'm willing to go to try to diagnose this. Now since I can't use a computer to re-lock the bootloader, I'm stuck with a busted usb port. The phone is clearly within a warranty time frame, with the exception that I unlocked the bootloader and voided that upon purchase. I guess my advice to anyone reading this, wait one year and one day before you bother, so should a hardware failure like this happen to you, you can have it replaced.
Out.

tyea said:
Ive tried multiple roms and kernels and nothing has helped. I just unrooted and no change. I think the usb firmware is corrupted, but don't know how to diagnose this. I even tried flashing different modems through the recovery (.27, .54, back to .48) and no change. I give up for now
LG-E960, Tapatalk b4
Click to expand...
Click to collapse
Same here, see final post

Fast charging not working and phone charging extremely slow

So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?

topaz330 said:
So I'm on the 935u for about a month and a half now and had no problems. All of a sudden today my phone stopped fast charging and is in fact charging extremely slow. I was on zero percent and put my phone on the charger around 6pm. It is now 1am and I'm at 49%. I'm thinking this is a hardware problem but before I bring the phone to Verizon I wanted to see if anyone else had this prob? Also will version give me a hard time since Im on the 935u software?
Click to expand...
Click to collapse
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.

Outbreak444 said:
If you're worried about Verizon giving you a hard time then flash back Verizon's firmware. But before your return it I would test out the functionality of fast charging and see what happens. If it works then why return it? Also if it works then I would say flash back to the U firmware and test again. Don't restore old settings or anything.
Or you could just start from where you are now and flash the U firmware over your current U firmware to reset any setting changes you have made. I know, it's a lengthy process but it's better than going back to the store and dealing with Verizon.
Click to expand...
Click to collapse
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.

topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk

amorrn said:
Rooted? If so, you have to go into the developer options to change the usb mode. There is no pop up on the phone, it defaults to charging mode.
Sent from my SM-G935V using Tapatalk
Click to expand...
Click to collapse
Nope not rooted.

topaz330 said:
turns out there might be an issue with my usb port. My phone won't even detect I connected it to my pc. It just shows charging. No options come up for media or anything. I can't even reset my phone to stock rom. This sucks.
Click to expand...
Click to collapse
topaz330 said:
Nope not rooted.
Click to expand...
Click to collapse
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.

Outbreak444 said:
Are you sure the cable is a data cable? If it's the stock cable then try to get ahold of another Samsung cable. Someone else had a similar problem with their S6 on another forum.
Click to expand...
Click to collapse
yep, its the stock cable. I plugged in my wifes s6 on it and it worked perfectly.

Anyway to flash stock rom without the use of odin or usb?

Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.

Action123 said:
Weirdly enough, I was having this same issue yesterday. Couldn't figure out what was going on - then tried a different cable and it charged normally. I think those Samsung cables aren't built very well. Ordering that PowerLine+ from Anker.
Click to expand...
Click to collapse
so verizon exchanged it via warranty no issues. They just checked to see if it was rooted whichi it wasn't and confirmed that the usb port was defective. All is well in the world again!

I was having this problem about 4 weeks ago. I tried everything but nothing worked. Rebooting would help for a bit then it would slow down to a crawl when I tried to wireless charge. Then I recalled I had taken an update recently and hadn't done a factory reset. I had traditionally always done one because in the past android was always buggy if you didn't. I thought android was supposed to have gotten better about taking updates without needing a FR so I had decided to do one without and had no problems for a while so forgot about it. When I realised that was the issue I saved as much as I could with Helium (normally I would use Titanium but I don't like the root method so for now have remained stock) and performed a FR. Since then I have had no issues and wireless charging works as expected.
TLDR: Backup everything and perform a factory reset.
Sent from my SM-P600 using XDA-Developers mobile app

Charging probelms (plus more) after Oreo update

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!