Ticket #1932 (closed defect: duplicate)

Opened 6 years ago

Last modified 6 years ago

Suspend mode OFF not working

Reported by: emartini Owned by: openmoko-devel
Priority: normal Milestone:
Component: Settings Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking: Estimated Completion (week):
HasPatchForReview: PatchReviewResult:
Reproducible: always

Description

Set suspsend mode to off => mobile goes into suspend mode after a while.

kernel: Om2008.8-gta02-20080826.uImage.bin
rootfs: Om2008.8-gta02-20080831.rootfs.jffs2

Change History

comment:1 in reply to: ↑ description Changed 6 years ago by jth

Duplicate of http://docs.openmoko.org/trac/ticket/1928
Please close this ticket.
/Johan

comment:2 Changed 6 years ago by michal.penka

I'm not sure that it's a the duplicate of [http://docs.openmoko.org/trac/ticket/1928 ], it's the opposite problem. I had a problem with Om2008.08 (images from 08. 08.), updated with zecke repos - only manual suspend worked with the POWER button.

Now I reflashed with the latest images (both 20080830 and 20080831, kernel 20080826) and the problem is OPPOSITE, I can't turn off or adjust the suspend policy neither from the Settings nor the Illume-config->Power menu. Manual suspend with POWER button works.

Tell me what can I do to help. I'm not developer though.

comment:3 Changed 6 years ago by jth

I know this is the same as the error as in 1928 as you use the same rootfs after 080829. About Om2008.8 from 08.08, I don't know and really don't care. I'm also no developer, but I'm still trying to get my MokoMakefile? to work so I can start to contribute. I'll see what I can do when I get the time. I flashed Neo 080827 with http://kopparv34.mine.nu/neo/ back when suspend worked fine. But after 080829 the opkg upgrade or rootfs-flash is bad, like for you and all other it stopped working, except for manual. And the setting is stuck at what the setting was set to when the upgrade was made and can't be changed. So if you flash with the above image and do not upgrade it should be ok. If you find what file is causing this issue so we can copy the working file from the good jffs2 image and attach the previous case, then many people will be happy I think. If not a new upgrade will fix this issue very soon anyway.

comment:4 Changed 6 years ago by marek

  • Status changed from new to closed
  • Resolution set to duplicate
  • Component changed from unknown to Settings

I also think this is a duplicate of #1928. Please comment there - I close this bug.

Note: See TracTickets for help on using tickets.