Bristol Digest, Vol 550, Issue 1

Send Bristol mailing list submissions to
bristol@mailman.lug.org.uk

To subscribe or unsubscribe via the World Wide Web, visit
https://mailman.lug.org.uk/mailman/listinfo/bristol
or, via email, send a message with subject or body 'help' to
bristol-request@mailman.lug.org.uk

You can reach the person managing the list at
bristol-owner@mailman.lug.org.uk

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Bristol digest..."


Today's Topics:

1. Re: Android Screen Affects Boot!? (OT) (Alex Butcher)


----------------------------------------------------------------------

Message: 1
Date: Mon, 12 May 2014 10:43:30 +0100 (BST)
From: Alex Butcher <lug@assursys.co.uk>
To: Bristol and Bath Linux User Group <bristol@mailman.lug.org.uk>
Subject: Re: [bristol] Android Screen Affects Boot!? (OT)
Message-ID: <alpine.LFD.2.03.1405121038020.6703@nffheflf.pb.hx>
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed

On Fri, 9 May 2014, Peter Hemmings wrote:

> On 09/05/14 13:12, Alex Butcher wrote:
>> The only thing I can think of is that Android has a general problem with UI
>> lag. If the processor is busy doing something and you start prodding the
>> screen, those input events (sometimes!) get queued up only to then be
>> dequeued when the processor becomes less busy - by which time the on-screen
>> UI may have changed and the events may well go to the wrong UI elements
>> (i.e. not the things that were on screen when you originally touched it).
>
> Funny you should say that, when it froze it seemed to start working after a
> minute or two and I thought that it was all being queued up!
>
> What bugs me (excuse pun), is that I cannot see what its doing and will need
> to do some research finding how I can debug it should I have more problems.

First, enable the hidden 'Developer options' settings submenu by tapping
repeatedly on Settings->About phone->Build number repeatedly. Don't worry
that it's just an information entry; it'll confirm that you'll on your way
to being a developer!

Once enabled, go into Settings->Developer options and enable Show CPU usage,
show touches and Show touches.

That should help you determine whether your touchscreen is actually faulty,
or whether the device is just busy doing something else.

HTH,
Alex



------------------------------

_______________________________________________
Bristol mailing list
Bristol@mailman.lug.org.uk
https://mailman.lug.org.uk/mailman/listinfo/bristol

End of Bristol Digest, Vol 550, Issue 1
***************************************