Ticket #810 (closed defect: upstream)

Opened 9 months ago

Last modified 7 months ago

Auto suspend timeout settings dont stick

Reported by: ssam Owned by: dos
Priority: major Milestone:
Component: Frameworkd / FSO Version: SHR-unstable
Keywords: Cc:

Description

on testing if i go into the power control, and increase the autosuspend timeout. then quit and then look again, it has reset to 40 seconds. the same with the other times.

Change History

in reply to: ↑ description   Changed 9 months ago by jth

Replying to ssam:

on testing if i go into the power control, and increase the autosuspend timeout. then quit and then look again, it has reset to 40 seconds. the same with the other times.

A primary major headache.

Workaround right now is to set your own default values in the configuration file /etc/frameworkd.conf
until saving is implemented.

  Changed 7 months ago by vancel35

I had this same problem, and I updated my values in /etc/frameworkd.conf. However it does not honor those settings either.

  Changed 7 months ago by TAsn

Closed dupe #787

  Changed 7 months ago by TAsn

  • owner changed from ainulindale to dos
  • status changed from new to assigned

It seems that shr-settings changes /etc/frameworkd.conf or something like that, instead of the new fsodeviced.conf config. dos1, can you confirm?

  Changed 7 months ago by dos

  • status changed from assigned to closed
  • resolution set to upstream
  • component changed from SHR Image to Frameworkd / FSO

No, shr-settings is using odeviced dbus calls to change that, and fsodeviced doesn't do its job :P

  Changed 7 months ago by TAsn

ssam, please open a ticket in freesmartphone.org.

  Changed 7 months ago by ssam

done
http://trac.freesmartphone.org/ticket/520

  Changed 7 months ago by TAsn

thanks.

Note: See TracTickets for help on using tickets.