Re: [android-developers] Re: A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

Could you give me a direction on how to use HTTP connection? I'm pretty new to Andoid programming Op dinsdag 1 november 2016 16:27:20 UTC+1 schreef Raymond Rodgers: > > I'm not familiar with the software you're using (on the server side), but > if the WebView is going to be invisible, why are

Re: [android-developers] Re: A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

On the serverside there will be a webpage which allows users to control a doorlock. An XML trigger has to be sent to this server. So the buttons will request a url like: https://10.10.100.25/index.phps?state=1 for opening a door and https://10.10.100.25/index.phps?state=0 for locking the door.

[android-developers] Re: A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

*KICK* I need help Op woensdag 26 oktober 2016 08:58:33 UTC+2 schreef a2netwo...@gmail.com: > > Hello, > > I wrote an (really basic) application to control access for a building. > This application exists of multiple buttons (10 in total). > Per door there are 2 buttons. One button acts as an

Re: [android-developers] A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

Nope .. I tried to clear the chache before loading a new URL or after loading the URL but it didn't work. Destroying the webview didn't work either. Op woensdag 26 oktober 2016 11:28:19 UTC+2 schreef sardar khan: > > Clear cache every time when you done loading one webview and about to >

Re: [android-developers] A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

Unfortunatly i started the party to early... the same error is occuring again... Op woensdag 26 oktober 2016 11:07:41 UTC+2 schreef sardar khan: > > Ok.np. > > On Wed, Oct 26, 2016 at 1:59 PM, > wrote: > >> Thank you very much... >> >> This problem has been resolved

Re: [android-developers] A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

Thank you very much... This problem has been resolved with clearing the cache webview.clearCache(true); webview.destroyDrawingCache(); However a Fatal signal 7 (SIGBUS) at 0x (code=128), thread 13497 (WebViewCoreThre) occurs so let's get to that one ... Op woensdag 26 oktober 2016

[android-developers] A/libc: Fatal signal 11 (SIGSEGV) at 0x0000001c (code=1), thread 25881 (WebViewCoreThre)

Hello, I wrote an (really basic) application to control access for a building. This application exists of multiple buttons (10 in total). Per door there are 2 buttons. One button acts as an pulse buton. When clicking the pulse button a timer function will be enabled and after 5 seconds the