Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adoptable storage often not accessible after standby #90

Open
CiNcH83 opened this issue Dec 1, 2020 · 4 comments
Open

Adoptable storage often not accessible after standby #90

CiNcH83 opened this issue Dec 1, 2020 · 4 comments

Comments

@CiNcH83
Copy link
Owner

CiNcH83 commented Dec 1, 2020

There are several severe standby issues when adopting storage via some external USB memory device with the BRAVIA often not properly resuming from deep sleep and/or storage not being accessible thereafter.

Several resume glitches have been caught:

  • adopted storage becomes read-only (0B free memory)
  • adopted storage remains in a safely ejected state
  • system does not resume from deep sleep

All three scenarios are fatal for a system memory which only a reboot takes care of.

@CiNcH83 CiNcH83 added this to the FW V6.7140 milestone Dec 1, 2020
@CiNcH83 CiNcH83 self-assigned this Dec 1, 2020
@mattheweli
Copy link

I can confirm this issue is present also on HX90 model (VH1 platform) with FW 6.0414. The adopted storage in my case results on read-only state

@foreveryoungforty
Copy link

foreveryoungforty commented Dec 22, 2020

After the update to Android 9, I had also a lot of trouble with "disappearing" USB-sticks. in standby.
After a lot of experiments , the following seem to stand after one week.

  1. I reformatted the USB stick on my computer to NTFS (as I put large concert-files on the stick)
  2. copy the files on that stick - BUT first create a folder on the stick to put them in (in my case named Concerts) - for some bizarre reason, if you put the files directly on the USB , Android creates a dummy folder for them, and even puts an x before the foldername after some time....)
  3. to avoid deep sleep, go to settings >Network & Internet (my TV is in Dutch, so I translate the options on the spot here, hope they are right)
  • remote start ON
  • remote operate ON (I have 1 tablet as registered device)
  • home network : renderer ON (automatic access ON) and IP-handling normal and simple ON
    These things consume a bit more energy with TV in standby, but for me worth to avoid the other troubles.

Maybe not all 3 actions are necessary, I haven't tested them seperately.

@CiNcH83
Copy link
Owner Author

CiNcH83 commented Dec 22, 2020

I reformatted the USB stick on my computer to NTFS (as I put large concert-files on the stick)

This ticket is about adoptable storage (ext4 formatted), not removable storage.

remote start ON

I do not recommend using remote start, see this ticket. It has no effect in your case though since you also enabled IP Control.

IP-handling normal and simple ON
These things consume a bit more energy with TV in standby

IP Control is the setting that prevents deep sleep altogether. This means that the BRAVIA will permanently consume 20W. That's not a solution to me.

@foreveryoungforty
Copy link

IP Control is the setting that prevents deep sleep altogether. This means that the BRAVIA will permanently consume 20W. That's not a solution to me.

Thanks for your info - I will put remote start to OFF again after reading your ticket. and also have a try to put IP control to off.
Maybe the creating of own folders on my USB was enough in my case. I will see what that gives to my "issue" of "disappearing usb" since the 6.7140 firmware-update of 18 nov. (seems that a lot of users are struggling with this too)

@CiNcH83 CiNcH83 changed the title Adoptable Storage: Resuming from Deep Sleep often failing Adoptable storage often not accessible after standby Jun 11, 2021
@CiNcH83 CiNcH83 modified the milestones: FW V6.7140, FW V6.7165 Jun 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants