Re: For the problem that the screen does not return to sleep and once in Android ICSx86

[Flower]

HI,all.

I know this problem is to say, that it is a problem that has been discussed previously.

I found a comment that looks like this: If you look.

> Chih-Wei

> The resolution is the key.

> ICS forces hardware acceleration for

> higher resolution.

>

> Try to add HWACCEL = 0 to kernel cmdline.

> (force hw accel off)

Although when you add the "HWACCEL = 0", do I need to add another from the options that have already been added to around line 27 of the 0-auto-detect bootable \ newinstaller \ initrd \ scripts \?

Do not you be able to as so, rather than from the kernel command line must be added to the configuration file somewhere in advance?

2012年11月6日火曜日 18時07分18秒 UTC+9 Flower:

HI,all.

I have a problem now, I have been developing using ICSx86, the screen goes dark once you sleep, not to return as it is.

I would like to solve this problem. Do not you know something?

I did get a log in the log cat. I put up a part of the log.

D / dalvikvm (1349): GC_FOR_ALLOC freed 3K, 8% free 28968K/31367K, paused 12ms

D / dalvikvm (1349): GC_FOR_ALLOC freed 2657K, 12% free 27715K/31367K, paused 9ms

I / dalvikvm-heap (1349): Grow heap (frag case) to 31.879MB for 4997132-byte allocation

D / dalvikvm (1349): GC_CONCURRENT freed 6K, 11% free 32588K/36295K, paused 1ms +1 ms

D / dalvikvm (1349): GC_FOR_ALLOC freed 4881K, 24% free 27712K/36295K, paused 8ms

I / dalvikvm-heap (1349): Grow heap (frag case) to 31.876MB for 4997132-byte allocation

D / dalvikvm (1349): GC_CONCURRENT freed <1K, 11% free 32591K/36295K, paused 0ms +2 ms

D / AudioHardware (1132): AudioHardware pcm playback is going to standby.

D / AudioHardware (1132): closePcmOut_l () mPcmOpenCnt: 1

D / dalvikvm (1160): GC_CONCURRENT freed 666K, 13% free 8711K/9927K, paused 1ms +3 ms

W / ThrottleService (1160): unable to find stats for iface rmnet0

I / power (1160): *** set_screen_state 0

D / SurfaceFlinger (1160): About to give-up screen, flinger = 0x81e5bf0

E / SurfaceFlinger (1160): ioctl (35, VT_RELDISP, 1) failed 22 (Invalid argument)

E / libEGL (1160): validate_display: 188 error 3008 (EGL_BAD_DISPLAY)

W / WindowManager (1160): Failure taking screenshot for (177x135) to layer 21005

[Chih-Wei Huang]

2012/11/8 Flower <gagaha...@yahoo.co.jp>:

> HI,all.
>
> I know this problem is to say, that it is a problem that has been discussed
> previously.
> I found a comment that looks like this: If you look.
>
>> Chih-Wei
>
>> The resolution is the key.
>> ICS forces hardware acceleration for
>> higher resolution.
>>
>> Try to add HWACCEL = 0 to kernel cmdline.
>> (force hw accel off)

What you quoted is a very old post (one year ago?)

> Although when you add the "HWACCEL = 0", do I need to add another from the
> options that have already been added to around line 27 of the 0-auto-detect
> bootable \ newinstaller \ initrd \ scripts \?

As you have found, current boot script will
automatically set HWACCEL=0
if your framebuffer driver doesn't support
hardware acceleration.
So manually setting it is not necessary.

> Do not you be able to as so, rather than from the kernel command line must
> be added to the configuration file somewhere in advance?

--
Chih-Wei
Android-x86 project
http://www.android-x86.org

[Flower]

Mr. Chih-Wei, thank you.

Now, it is necessary to solve this problem anyway, I gather information.

As a result, I came upon the post. I apologize to the unpleasant.

> As you have found, current boot script will

> automatically set HWACCEL = 0

> if your framebuffer driver doesn't support

> hardware acceleration.

> So manually setting it is not necessary.

Although I do not know well,

If set to "HWACCEL = 0" automatically, why the problem happened now, I'm facing?

2012年11月8日木曜日 12時46分11秒 UTC+9 Chih-Wei Huang:

[Chih-Wei Huang]

2012/11/8 Flower <gagaha...@yahoo.co.jp>:

> Mr. Chih-Wei, thank you.
>
> Now, it is necessary to solve this problem anyway, I gather information.
> As a result, I came upon the post. I apologize to the unpleasant.
>
>> As you have found, current boot script will
>> automatically set HWACCEL = 0
>> if your framebuffer driver doesn't support
>> hardware acceleration.
>> So manually setting it is not necessary.
> Although I do not know well,
> If set to "HWACCEL = 0" automatically, why the problem happened now, I'm
> facing?

Well, what you talked about is a suspend/resume issue, right?
I didn't see any relationship to hw acceleration.

Suspend/resume is always a big issue of Android-x86 (or even Linux).
I (or any other current developer) am not the expert.
It's still an unsolved issue.
If you make some progress, welcome to contribute.

Regards,
Chih-Wei