How to use PrintScreen key to capture screen?

[Brajib]

I have tried to use the PrintScreen / SysReq key to capture the Android screen but failed.

Android recognises the Keystroke but says:
Couldn't capture screenshot.
Couldn't save screenshot. Storage may be in use.

I searched the Google Play to find an application that may help me do so. But failed to find one, except a spanish, Como Hacer Captura de Pentalla. The English translation is:

How to make a screen capture.
I tried with the software. But didn't work with the aforementioned keystroke. Any suggestion?

[Chih-Wei Huang]

Currently screen capturing is only supported
in Intel i965 and QEMU virgl GPU.

What's your GPU?
Check Settings -> About -> OpenGL.



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

[Rajib Bando]

On 2/9/18, Chih-Wei Huang <cwh...@android-x86.org> wrote:
> Currently screen capturing is only supported
> in Intel i965 and QEMU virgl GPU.
>
> What's your GPU?
> Check Settings -> About -> OpenGL.

... ... ... ...
Thank you, Dr. Huang, for replying to my query once more...

Open GL Driver Version
GL Vendor: null
GL Renderer: null
GL Version: null

My other query in my other post: Since my computer, processor,
graphics card, ..., all are old, will the computer be able to handle
and run the latest Android-x86 version?

Thank you once again and regards.
Rajib

[Chih-Wei Huang]

2018-02-09 11:29 GMT+08:00 Rajib Bando <raji...@gmail.com>:
> On 2/9/18, Chih-Wei Huang <cwh...@android-x86.org> wrote:
>> Currently screen capturing is only supported
>> in Intel i965 and QEMU virgl GPU.
>>
>> What's your GPU?
>> Check Settings -> About -> OpenGL.
> ... ... ... ...
> Thank you, Dr. Huang, for replying to my query once more...
>
> Open GL Driver Version
> GL Vendor: null
> GL Renderer: null
> GL Version: null

Indeed you are using an very old version.
GL version should not be null since 6.0.
If will fallback to software rendering even
no supported GPU.

> My other query in my other post: Since my computer, processor,
> graphics card, ..., all are old, will the computer be able to handle
> and run the latest Android-x86 version?

How can I know?
Try yourself, please.

[Rajib Bando]

On 2/9/18, Chih-Wei Huang <cwh...@android-x86.org> wrote:

... ... ... ...

> How can I know?
> Try yourself, please.

... ...

I am sorry, Dr, Huang, that I could not make myself clearer. What I
wanted to know was the Minimum Specification for the *latest* android-x86 iso.

[Chih-Wei Huang]

2018-02-09 16:02 GMT+08:00 Rajib Bando <raji...@gmail.com>:
> On 2/9/18, Chih-Wei Huang <cwh...@android-x86.org> wrote:

> ... ... ... ...

>> How can I know?
>> Try yourself, please.

> ... ...
>
> I am sorry, Dr, Huang, that I could not make myself clearer. What I

> wanted to know was the Minimum Specification for the android-x86 iso.

There is no such spec.
Just test it to see if it works.

On the other hand, why don't you tell us
your device spec?

[Rajib Bando]

On 2/9/18, Chih-Wei Huang <cwh...@android-x86.org> wrote:
> There is no such spec.
> Just test it to see if it works.

I tested. It runs up to a point, and reboots. Is there a way to have a
log file of the steps of booting successfully gotten?
Otherwise, I will shoot with my camera and report.
... ... ... ...

> On the other hand, why don't you tell us
> your device spec?

... ... ... ...
Yes, Dr. Huang, of course! You have my graphics card's specification already.

RAM is 4GB DDR 667 Mhz.

-Display-
Resolution : 1360x768 pixels
Vendor : The X.Org Foundation
Version : 1.12.4
-Monitors-
Monitor 0 : 1360x768 pixels
-Extensions-

-Processor-
Name : AMD Sempron(tm) Processor LE-1250
Family, model, stepping : 15, 127, 2 (AMD Opteron/Athlon64/FX)
Vendor : AuthenticAMD
-Configuration-
Cache Size : 512kb
Frequency : 2000.00MHz
BogoMIPS : 4019.51
Byte Order : Little Endian
-Features-
FDIV Bug : no
HLT Bug : no
F00F Bug : no
Coma Bug : no
Has FPU : yes
-Cache-
Level 1 (Data) : 2-way set-associative, 512 sets, 64KB size
Level 1 (Instruction) : 2-way set-associative, 512 sets, 64KB size
Level 2 (Unified) : 16-way set-associative, 512 sets, 512KB size
-Capabilities-
fpu : Floating Point Unit
vme : Virtual 86 Mode Extension
de : Debug Extensions - I/O breakpoints
pse : Page Size Extensions (4MB pages)
tsc : Time Stamp Counter and RDTSC instruction
msr : Model Specific Registers
pae : Physical Address Extensions
mce : Machine Check Architeture
cx8 : CMPXCHG8 instruction
apic : Advanced Programmable Interrupt Controller
sep : Fast System Call (SYSENTER/SYSEXIT)
mtrr : Memory Type Range Registers
pge : Page Global Enable
mca : Machine Check Architecture
cmov : Conditional Move instruction
pat : Page Attribute Table
pse36 : 36bit Page Size Extensions
clflush : Cache Line Flush instruction
mmx : MMX technology
fxsr : FXSAVE and FXRSTOR instructions
sse : SSE instructions
sse2 : SSE2 (WNI) instructions
syscall : SYSCALL and SYSEXIT instructions
nx : No-execute Page Protection
mmxext : Extended MMX Technology
fxsr_opt
rdtscp : RDTSCP
lm : LAHF/SAHF in long mode
3dnowext : Extended 3DNow! Technology
3dnow : 3DNow! Technology
extd_apicid
pni : Streaming SIMD Extension 3 (Prescott New Instruction)
cx16 : CMPXCHG16B instruction
lahf_lm : LAHF/SAHF in long mode
extapic
cr8_legacy
3dnowprefetch

Regards,
Rajib

[Chih-Wei Huang]

Your CPU and RAM are pretty good to run Android.
The problem is the old AMD CPU doesn't support
x86 ABI defined by Google.

https://developer.android.com/ndk/guides/abis.html#x86

Did you test 32-bit or 64-bit version?
Some AMD owners reported 64-bit can't run
but 32-bit is OK.
You can try it.

[Rajib Bando]

Of course, 32, because Intel and AMD have common OpCodes for 32 bit.
64 is different. I have already tried, but failed. Any special booting
time cheatcode?

[Rajib Bando]

Perhaps this portion of the post on Fri, 9 Feb 2018 03:33:16 -0800
(PST) _missed_ your notice?