Android APK sanity check

classic Classic list List threaded Threaded
17 messages Options
Reply | Threaded
Open this post in threaded view
|

Android APK sanity check

Tore Nilsen via use-livecode
I rebuilt an apk with LC 9.0 today and it runs fine on my Pixel (OS 8.1)
but on my Samsung S5 (OS 6.0.1) it launches to a black screen and
immediately crashes. An answer dialog in preOpenCard never runs, so I
don't think the app even fully loads. The same app built a couple of
months ago with LC 9.0dp11 runs fine on the Samsung.

I thought it might be the change I made to the target version in the
manifest, but the problem still exists when I put the default manifest
back in. The minimum app version is set to KitKat (4.4) which should be
fine.

I'm just checking to see if anyone else has had trouble with LC 9.0 on
older phones.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
You might want to have a look at https://quality.livecode.com/show_bug.cgi?id=20954   Sounds very much like the issue you are having.

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J. Landman Gay via use-livecode
Sent: 30 May 2018 23:22
To: LiveCode Mailing List <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Android APK sanity check

I rebuilt an apk with LC 9.0 today and it runs fine on my Pixel (OS 8.1) but on my Samsung S5 (OS 6.0.1) it launches to a black screen and immediately crashes. An answer dialog in preOpenCard never runs, so I don't think the app even fully loads. The same app built a couple of months ago with LC 9.0dp11 runs fine on the Samsung.

I thought it might be the change I made to the target version in the manifest, but the problem still exists when I put the default manifest back in. The minimum app version is set to KitKat (4.4) which should be fine.

I'm just checking to see if anyone else has had trouble with LC 9.0 on older phones.

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
Hi all,

The first thing that came to my mind was the bug report that Paul
referenced, but I had a look at the Samsung S5 specs and it seems it has an
ARM chip, so it should not be affected by this bug.

@Jacque does that happen with any android standalone you build with LC
9.0.0, or just this particular one?

Best,
Panos
--

On Thu, May 31, 2018 at 9:01 AM, Paul Richards via use-livecode <
[hidden email]> wrote:

> You might want to have a look at https://quality.livecode.com/
> show_bug.cgi?id=20954   Sounds very much like the issue you are having.
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of
> J. Landman Gay via use-livecode
> Sent: 30 May 2018 23:22
> To: LiveCode Mailing List <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Android APK sanity check
>
> I rebuilt an apk with LC 9.0 today and it runs fine on my Pixel (OS 8.1)
> but on my Samsung S5 (OS 6.0.1) it launches to a black screen and
> immediately crashes. An answer dialog in preOpenCard never runs, so I don't
> think the app even fully loads. The same app built a couple of months ago
> with LC 9.0dp11 runs fine on the Samsung.
>
> I thought it might be the change I made to the target version in the
> manifest, but the problem still exists when I put the default manifest back
> in. The minimum app version is set to KitKat (4.4) which should be fine.
>
> I'm just checking to see if anyone else has had trouble with LC 9.0 on
> older phones.
>
> --
> Jacqueline Landman Gay         |     [hidden email]
> HyperActive Software           |     http://www.hyperactivesw.com
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
I created a plain do-nothing stack and it works on my Samsung. Then I
set the inclusions to same ones in my working project. The plain stack
then had the same misbehavior -- black screen and crash on launch.

One by one I turned off each inclusion, tested, and then turned it back
on and disabled the next one. It looks like the culprit is mergJSON.
With that included I get the crash, without it the apk behaves.

I'll submit my test stack and a bug report.

On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:

> Hi all,
>
> The first thing that came to my mind was the bug report that Paul
> referenced, but I had a look at the Samsung S5 specs and it seems it has an
> ARM chip, so it should not be affected by this bug.
>
> @Jacque does that happen with any android standalone you build with LC
> 9.0.0, or just this particular one?
>
> Best,
> Panos


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
Hi Jacque,
You have been one of the people on the List that has answered many of my
questions about building Android Applications. I do have an application that
uses mergJSON and the problem that I have is only during the initial
starting of the application after the APK is loaded. I also get a blank
initial screen. I found that if I close the application and then restart the
application - it runs. I have also had problems with applications locking up
on one Android Device and will run on another without problems. The problems
that I encountered were mainly opening data files across the internet on the
failing device. I actually solved some of those problems by putting a delay
after  I call for data across the internet. Both devices are using Android
5.1.1. The failing Device  is a Nexus 7 and the other device that doesn't
fail is a generic X10 Chinese cheaper Tablet. The only other problem I
noticed with LC 9 is a latency in starting the applications.

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J.
Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 12:10 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Re: Android APK sanity check

I created a plain do-nothing stack and it works on my Samsung. Then I set
the inclusions to same ones in my working project. The plain stack then had
the same misbehavior -- black screen and crash on launch.

One by one I turned off each inclusion, tested, and then turned it back on
and disabled the next one. It looks like the culprit is mergJSON.
With that included I get the crash, without it the apk behaves.

I'll submit my test stack and a bug report.

On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:

> Hi all,
>
> The first thing that came to my mind was the bug report that Paul
> referenced, but I had a look at the Samsung S5 specs and it seems it
> has an ARM chip, so it should not be affected by this bug.
>
> @Jacque does that happen with any android standalone you build with LC
> 9.0.0, or just this particular one?
>
> Best,
> Panos


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
Thanks for the comments. I've actually seen the problem with initial
startup on a few apps but in this case a relaunch still crashes. :(

Since you have a few older devices, it might help the team narrow down
what's affected if you try out my test stack. Bug report is here:
https://quality.livecode.com/show_bug.cgi?id=21325

I only have Android Marshmallow on my test phone(s) but I'm betting it
will fail with any older OS. Or it may be the version of Java I
installed, which I believe LC 9 required.

On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:

> Hi Jacque,
> You have been one of the people on the List that has answered many of my
> questions about building Android Applications. I do have an application that
> uses mergJSON and the problem that I have is only during the initial
> starting of the application after the APK is loaded. I also get a blank
> initial screen. I found that if I close the application and then restart the
> application - it runs. I have also had problems with applications locking up
> on one Android Device and will run on another without problems. The problems
> that I encountered were mainly opening data files across the internet on the
> failing device. I actually solved some of those problems by putting a delay
> after  I call for data across the internet. Both devices are using Android
> 5.1.1. The failing Device  is a Nexus 7 and the other device that doesn't
> fail is a generic X10 Chinese cheaper Tablet. The only other problem I
> noticed with LC 9 is a latency in starting the applications.
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 12:10 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> I created a plain do-nothing stack and it works on my Samsung. Then I set
> the inclusions to same ones in my working project. The plain stack then had
> the same misbehavior -- black screen and crash on launch.
>
> One by one I turned off each inclusion, tested, and then turned it back on
> and disabled the next one. It looks like the culprit is mergJSON.
> With that included I get the crash, without it the apk behaves.
>
> I'll submit my test stack and a bug report.
>
> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>> Hi all,
>>
>> The first thing that came to my mind was the bug report that Paul
>> referenced, but I had a look at the Samsung S5 specs and it seems it
>> has an ARM chip, so it should not be affected by this bug.
>>
>> @Jacque does that happen with any android standalone you build with LC
>> 9.0.0, or just this particular one?
>>
>> Best,
>> Panos
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
Hi Jacque,
I just tried your test stack and I can't get it to complete the APK to load
on either of my devices. This is odd. I tried loading my application right
after to make sure I hadn't made any changes to the Android Stand-Alone
settings and I was able to compile my application.


-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J.
Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 1:02 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Re: Android APK sanity check

Thanks for the comments. I've actually seen the problem with initial startup
on a few apps but in this case a relaunch still crashes. :(

Since you have a few older devices, it might help the team narrow down
what's affected if you try out my test stack. Bug report is here:
https://quality.livecode.com/show_bug.cgi?id=21325

I only have Android Marshmallow on my test phone(s) but I'm betting it will
fail with any older OS. Or it may be the version of Java I installed, which
I believe LC 9 required.

On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:

> Hi Jacque,
> You have been one of the people on the List that has answered many of
> my questions about building Android Applications. I do have an
> application that uses mergJSON and the problem that I have is only
> during the initial starting of the application after the APK is
> loaded. I also get a blank initial screen. I found that if I close the
> application and then restart the application - it runs. I have also
> had problems with applications locking up on one Android Device and
> will run on another without problems. The problems that I encountered
> were mainly opening data files across the internet on the failing
> device. I actually solved some of those problems by putting a delay
> after  I call for data across the internet. Both devices are using
> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only other
problem I noticed with LC 9 is a latency in starting the applications.

>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 12:10 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> I created a plain do-nothing stack and it works on my Samsung. Then I
> set the inclusions to same ones in my working project. The plain stack
> then had the same misbehavior -- black screen and crash on launch.
>
> One by one I turned off each inclusion, tested, and then turned it
> back on and disabled the next one. It looks like the culprit is mergJSON.
> With that included I get the crash, without it the apk behaves.
>
> I'll submit my test stack and a bug report.
>
> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>> Hi all,
>>
>> The first thing that came to my mind was the bug report that Paul
>> referenced, but I had a look at the Samsung S5 specs and it seems it
>> has an ARM chip, so it should not be affected by this bug.
>>
>> @Jacque does that happen with any android standalone you build with
>> LC 9.0.0, or just this particular one?
>>
>> Best,
>> Panos
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
Hi Jacque,
I just tried again and it worked.
My initial screen after the reload was blank but when I closed the app and
reloaded it, it actually works. When I clicked the button I get 1527802252
in the text field.
I actually had to change the identifier (in this case to "com.cpm.testapp" )
in the Android application window.

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of
Clarence Martin via use-livecode
Sent: Thursday, May 31, 2018 2:12 PM
To: 'How to use LiveCode' <[hidden email]>
Cc: [hidden email]
Subject: RE: Android APK sanity check

Hi Jacque,
I just tried your test stack and I can't get it to complete the APK to load
on either of my devices. This is odd. I tried loading my application right
after to make sure I hadn't made any changes to the Android Stand-Alone
settings and I was able to compile my application.


-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J.
Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 1:02 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Re: Android APK sanity check

Thanks for the comments. I've actually seen the problem with initial startup
on a few apps but in this case a relaunch still crashes. :(

Since you have a few older devices, it might help the team narrow down
what's affected if you try out my test stack. Bug report is here:
https://quality.livecode.com/show_bug.cgi?id=21325

I only have Android Marshmallow on my test phone(s) but I'm betting it will
fail with any older OS. Or it may be the version of Java I installed, which
I believe LC 9 required.

On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:

> Hi Jacque,
> You have been one of the people on the List that has answered many of
> my questions about building Android Applications. I do have an
> application that uses mergJSON and the problem that I have is only
> during the initial starting of the application after the APK is
> loaded. I also get a blank initial screen. I found that if I close the
> application and then restart the application - it runs. I have also
> had problems with applications locking up on one Android Device and
> will run on another without problems. The problems that I encountered
> were mainly opening data files across the internet on the failing
> device. I actually solved some of those problems by putting a delay
> after  I call for data across the internet. Both devices are using
> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only
> other
problem I noticed with LC 9 is a latency in starting the applications.

>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 12:10 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> I created a plain do-nothing stack and it works on my Samsung. Then I
> set the inclusions to same ones in my working project. The plain stack
> then had the same misbehavior -- black screen and crash on launch.
>
> One by one I turned off each inclusion, tested, and then turned it
> back on and disabled the next one. It looks like the culprit is mergJSON.
> With that included I get the crash, without it the apk behaves.
>
> I'll submit my test stack and a bug report.
>
> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>> Hi all,
>>
>> The first thing that came to my mind was the bug report that Paul
>> referenced, but I had a look at the Samsung S5 specs and it seems it
>> has an ARM chip, so it should not be affected by this bug.
>>
>> @Jacque does that happen with any android standalone you build with
>> LC 9.0.0, or just this particular one?
>>
>> Best,
>> Panos
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
In reply to this post by Tore Nilsen via use-livecode
The problem that I had, had  to do with the identifier name and had nothing
to do with anything else. I remember that from earlier problems that Panos
identified for me.
The test stack worked on both Android Devices that I have.
More info on my system:
Windows 10 computer with the Java jdk 1.8.0_171.

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J.
Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 1:02 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Re: Android APK sanity check

Thanks for the comments. I've actually seen the problem with initial startup
on a few apps but in this case a relaunch still crashes. :(

Since you have a few older devices, it might help the team narrow down
what's affected if you try out my test stack. Bug report is here:
https://quality.livecode.com/show_bug.cgi?id=21325

I only have Android Marshmallow on my test phone(s) but I'm betting it will
fail with any older OS. Or it may be the version of Java I installed, which
I believe LC 9 required.

On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:

> Hi Jacque,
> You have been one of the people on the List that has answered many of
> my questions about building Android Applications. I do have an
> application that uses mergJSON and the problem that I have is only
> during the initial starting of the application after the APK is
> loaded. I also get a blank initial screen. I found that if I close the
> application and then restart the application - it runs. I have also
> had problems with applications locking up on one Android Device and
> will run on another without problems. The problems that I encountered
> were mainly opening data files across the internet on the failing
> device. I actually solved some of those problems by putting a delay
> after  I call for data across the internet. Both devices are using
> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only other
problem I noticed with LC 9 is a latency in starting the applications.

>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 12:10 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> I created a plain do-nothing stack and it works on my Samsung. Then I
> set the inclusions to same ones in my working project. The plain stack
> then had the same misbehavior -- black screen and crash on launch.
>
> One by one I turned off each inclusion, tested, and then turned it
> back on and disabled the next one. It looks like the culprit is mergJSON.
> With that included I get the crash, without it the apk behaves.
>
> I'll submit my test stack and a bug report.
>
> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>> Hi all,
>>
>> The first thing that came to my mind was the bug report that Paul
>> referenced, but I had a look at the Samsung S5 specs and it seems it
>> has an ARM chip, so it should not be affected by this bug.
>>
>> @Jacque does that happen with any android standalone you build with
>> LC 9.0.0, or just this particular one?
>>
>> Best,
>> Panos
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
Thanks for testing. Maybe it's a Mac problem. The identifier shouldn't
matter in this case though, if you were originally using the unique one
I put into the stack. So that's odd too.

On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:

> The problem that I had, had  to do with the identifier name and had nothing
> to do with anything else. I remember that from earlier problems that Panos
> identified for me.
> The test stack worked on both Android Devices that I have.
> More info on my system:
> Windows 10 computer with the Java jdk 1.8.0_171.
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 1:02 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> Thanks for the comments. I've actually seen the problem with initial startup
> on a few apps but in this case a relaunch still crashes. :(
>
> Since you have a few older devices, it might help the team narrow down
> what's affected if you try out my test stack. Bug report is here:
> https://quality.livecode.com/show_bug.cgi?id=21325
>
> I only have Android Marshmallow on my test phone(s) but I'm betting it will
> fail with any older OS. Or it may be the version of Java I installed, which
> I believe LC 9 required.
>
> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>> Hi Jacque,
>> You have been one of the people on the List that has answered many of
>> my questions about building Android Applications. I do have an
>> application that uses mergJSON and the problem that I have is only
>> during the initial starting of the application after the APK is
>> loaded. I also get a blank initial screen. I found that if I close the
>> application and then restart the application - it runs. I have also
>> had problems with applications locking up on one Android Device and
>> will run on another without problems. The problems that I encountered
>> were mainly opening data files across the internet on the failing
>> device. I actually solved some of those problems by putting a delay
>> after  I call for data across the internet. Both devices are using
>> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
>> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only other
> problem I noticed with LC 9 is a latency in starting the applications.
>>
>> -----Original Message-----
>> From: use-livecode <[hidden email]> On Behalf Of J.
>> Landman Gay via use-livecode
>> Sent: Thursday, May 31, 2018 12:10 PM
>> To: How to use LiveCode <[hidden email]>
>> Cc: J. Landman Gay <[hidden email]>
>> Subject: Re: Android APK sanity check
>>
>> I created a plain do-nothing stack and it works on my Samsung. Then I
>> set the inclusions to same ones in my working project. The plain stack
>> then had the same misbehavior -- black screen and crash on launch.
>>
>> One by one I turned off each inclusion, tested, and then turned it
>> back on and disabled the next one. It looks like the culprit is mergJSON.
>> With that included I get the crash, without it the apk behaves.
>>
>> I'll submit my test stack and a bug report.
>>
>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>> Hi all,
>>>
>>> The first thing that came to my mind was the bug report that Paul
>>> referenced, but I had a look at the Samsung S5 specs and it seems it
>>> has an ARM chip, so it should not be affected by this bug.
>>>
>>> @Jacque does that happen with any android standalone you build with
>>> LC 9.0.0, or just this particular one?
>>>
>>> Best,
>>> Panos
>>
>>
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
I just took another look and I see that the identifier had reverted to
the default, so that explains why you had to change it. Even after I
reset it to something unique though it still fails here. It looks like
it's time for the LC guys to employ their magic.

On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:

> Thanks for testing. Maybe it's a Mac problem. The identifier shouldn't
> matter in this case though, if you were originally using the unique one
> I put into the stack. So that's odd too.
>
> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
>> The problem that I had, had  to do with the identifier name and had
>> nothing
>> to do with anything else. I remember that from earlier problems that
>> Panos
>> identified for me.
>> The test stack worked on both Android Devices that I have.
>> More info on my system:
>> Windows 10 computer with the Java jdk 1.8.0_171.
>>
>> -----Original Message-----
>> From: use-livecode <[hidden email]> On Behalf
>> Of J.
>> Landman Gay via use-livecode
>> Sent: Thursday, May 31, 2018 1:02 PM
>> To: How to use LiveCode <[hidden email]>
>> Cc: J. Landman Gay <[hidden email]>
>> Subject: Re: Android APK sanity check
>>
>> Thanks for the comments. I've actually seen the problem with initial
>> startup
>> on a few apps but in this case a relaunch still crashes. :(
>>
>> Since you have a few older devices, it might help the team narrow down
>> what's affected if you try out my test stack. Bug report is here:
>> https://quality.livecode.com/show_bug.cgi?id=21325
>>
>> I only have Android Marshmallow on my test phone(s) but I'm betting it
>> will
>> fail with any older OS. Or it may be the version of Java I installed,
>> which
>> I believe LC 9 required.
>>
>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>>> Hi Jacque,
>>> You have been one of the people on the List that has answered many of
>>> my questions about building Android Applications. I do have an
>>> application that uses mergJSON and the problem that I have is only
>>> during the initial starting of the application after the APK is
>>> loaded. I also get a blank initial screen. I found that if I close the
>>> application and then restart the application - it runs. I have also
>>> had problems with applications locking up on one Android Device and
>>> will run on another without problems. The problems that I encountered
>>> were mainly opening data files across the internet on the failing
>>> device. I actually solved some of those problems by putting a delay
>>> after  I call for data across the internet. Both devices are using
>>> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
>>> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only
>>> other
>> problem I noticed with LC 9 is a latency in starting the applications.
>>>
>>> -----Original Message-----
>>> From: use-livecode <[hidden email]> On Behalf
>>> Of J.
>>> Landman Gay via use-livecode
>>> Sent: Thursday, May 31, 2018 12:10 PM
>>> To: How to use LiveCode <[hidden email]>
>>> Cc: J. Landman Gay <[hidden email]>
>>> Subject: Re: Android APK sanity check
>>>
>>> I created a plain do-nothing stack and it works on my Samsung. Then I
>>> set the inclusions to same ones in my working project. The plain stack
>>> then had the same misbehavior -- black screen and crash on launch.
>>>
>>> One by one I turned off each inclusion, tested, and then turned it
>>> back on and disabled the next one. It looks like the culprit is
>>> mergJSON.
>>> With that included I get the crash, without it the apk behaves.
>>>
>>> I'll submit my test stack and a bug report.
>>>
>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>>> Hi all,
>>>>
>>>> The first thing that came to my mind was the bug report that Paul
>>>> referenced, but I had a look at the Samsung S5 specs and it seems it
>>>> has an ARM chip, so it should not be affected by this bug.
>>>>
>>>> @Jacque does that happen with any android standalone you build with
>>>> LC 9.0.0, or just this particular one?
>>>>
>>>> Best,
>>>> Panos
>>>
>>>
>>
>>
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
@Clarence, I just uploaded an apk I built on my Mac. Could you check the
bug report again and try the apk I put there? Thanks for your time.

On 5/31/18 5:49 PM, J. Landman Gay via use-livecode wrote:

> I just took another look and I see that the identifier had reverted to
> the default, so that explains why you had to change it. Even after I
> reset it to something unique though it still fails here. It looks like
> it's time for the LC guys to employ their magic.
>
> On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:
>> Thanks for testing. Maybe it's a Mac problem. The identifier shouldn't
>> matter in this case though, if you were originally using the unique
>> one I put into the stack. So that's odd too.
>>
>> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
>>> The problem that I had, had  to do with the identifier name and had
>>> nothing
>>> to do with anything else. I remember that from earlier problems that
>>> Panos
>>> identified for me.
>>> The test stack worked on both Android Devices that I have.
>>> More info on my system:
>>> Windows 10 computer with the Java jdk 1.8.0_171.
>>>
>>> -----Original Message-----
>>> From: use-livecode <[hidden email]> On Behalf
>>> Of J.
>>> Landman Gay via use-livecode
>>> Sent: Thursday, May 31, 2018 1:02 PM
>>> To: How to use LiveCode <[hidden email]>
>>> Cc: J. Landman Gay <[hidden email]>
>>> Subject: Re: Android APK sanity check
>>>
>>> Thanks for the comments. I've actually seen the problem with initial
>>> startup
>>> on a few apps but in this case a relaunch still crashes. :(
>>>
>>> Since you have a few older devices, it might help the team narrow down
>>> what's affected if you try out my test stack. Bug report is here:
>>> https://quality.livecode.com/show_bug.cgi?id=21325
>>>
>>> I only have Android Marshmallow on my test phone(s) but I'm betting
>>> it will
>>> fail with any older OS. Or it may be the version of Java I installed,
>>> which
>>> I believe LC 9 required.
>>>
>>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>>>> Hi Jacque,
>>>> You have been one of the people on the List that has answered many of
>>>> my questions about building Android Applications. I do have an
>>>> application that uses mergJSON and the problem that I have is only
>>>> during the initial starting of the application after the APK is
>>>> loaded. I also get a blank initial screen. I found that if I close the
>>>> application and then restart the application - it runs. I have also
>>>> had problems with applications locking up on one Android Device and
>>>> will run on another without problems. The problems that I encountered
>>>> were mainly opening data files across the internet on the failing
>>>> device. I actually solved some of those problems by putting a delay
>>>> after  I call for data across the internet. Both devices are using
>>>> Android 5.1.1. The failing Device  is a Nexus 7 and the other device
>>>> that doesn't fail is a generic X10 Chinese cheaper Tablet. The only
>>>> other
>>> problem I noticed with LC 9 is a latency in starting the applications.
>>>>
>>>> -----Original Message-----
>>>> From: use-livecode <[hidden email]> On Behalf
>>>> Of J.
>>>> Landman Gay via use-livecode
>>>> Sent: Thursday, May 31, 2018 12:10 PM
>>>> To: How to use LiveCode <[hidden email]>
>>>> Cc: J. Landman Gay <[hidden email]>
>>>> Subject: Re: Android APK sanity check
>>>>
>>>> I created a plain do-nothing stack and it works on my Samsung. Then I
>>>> set the inclusions to same ones in my working project. The plain stack
>>>> then had the same misbehavior -- black screen and crash on launch.
>>>>
>>>> One by one I turned off each inclusion, tested, and then turned it
>>>> back on and disabled the next one. It looks like the culprit is
>>>> mergJSON.
>>>> With that included I get the crash, without it the apk behaves.
>>>>
>>>> I'll submit my test stack and a bug report.
>>>>
>>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>>>> Hi all,
>>>>>
>>>>> The first thing that came to my mind was the bug report that Paul
>>>>> referenced, but I had a look at the Samsung S5 specs and it seems it
>>>>> has an ARM chip, so it should not be affected by this bug.
>>>>>
>>>>> @Jacque does that happen with any android standalone you build with
>>>>> LC 9.0.0, or just this particular one?
>>>>>
>>>>> Best,
>>>>> Panos
>>>>
>>>>
>>>
>>>
>>
>>
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
I just uploaded this to my Nexus7 and it works the same way. It initially opens with a blank screen and then opens correctly.

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J. Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 4:20 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: Re: Android APK sanity check

@Clarence, I just uploaded an apk I built on my Mac. Could you check the bug report again and try the apk I put there? Thanks for your time.

On 5/31/18 5:49 PM, J. Landman Gay via use-livecode wrote:

> I just took another look and I see that the identifier had reverted to
> the default, so that explains why you had to change it. Even after I
> reset it to something unique though it still fails here. It looks like
> it's time for the LC guys to employ their magic.
>
> On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:
>> Thanks for testing. Maybe it's a Mac problem. The identifier
>> shouldn't matter in this case though, if you were originally using
>> the unique one I put into the stack. So that's odd too.
>>
>> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
>>> The problem that I had, had  to do with the identifier name and had
>>> nothing to do with anything else. I remember that from earlier
>>> problems that Panos identified for me.
>>> The test stack worked on both Android Devices that I have.
>>> More info on my system:
>>> Windows 10 computer with the Java jdk 1.8.0_171.
>>>
>>> -----Original Message-----
>>> From: use-livecode <[hidden email]> On Behalf
>>> Of J.
>>> Landman Gay via use-livecode
>>> Sent: Thursday, May 31, 2018 1:02 PM
>>> To: How to use LiveCode <[hidden email]>
>>> Cc: J. Landman Gay <[hidden email]>
>>> Subject: Re: Android APK sanity check
>>>
>>> Thanks for the comments. I've actually seen the problem with initial
>>> startup on a few apps but in this case a relaunch still crashes. :(
>>>
>>> Since you have a few older devices, it might help the team narrow
>>> down what's affected if you try out my test stack. Bug report is here:
>>> https://quality.livecode.com/show_bug.cgi?id=21325
>>>
>>> I only have Android Marshmallow on my test phone(s) but I'm betting
>>> it will fail with any older OS. Or it may be the version of Java I
>>> installed, which I believe LC 9 required.
>>>
>>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>>>> Hi Jacque,
>>>> You have been one of the people on the List that has answered many
>>>> of my questions about building Android Applications. I do have an
>>>> application that uses mergJSON and the problem that I have is only
>>>> during the initial starting of the application after the APK is
>>>> loaded. I also get a blank initial screen. I found that if I close
>>>> the application and then restart the application - it runs. I have
>>>> also had problems with applications locking up on one Android
>>>> Device and will run on another without problems. The problems that
>>>> I encountered were mainly opening data files across the internet on
>>>> the failing device. I actually solved some of those problems by
>>>> putting a delay after  I call for data across the internet. Both
>>>> devices are using Android 5.1.1. The failing Device  is a Nexus 7
>>>> and the other device that doesn't fail is a generic X10 Chinese
>>>> cheaper Tablet. The only other
>>> problem I noticed with LC 9 is a latency in starting the applications.
>>>>
>>>> -----Original Message-----
>>>> From: use-livecode <[hidden email]> On
>>>> Behalf Of J.
>>>> Landman Gay via use-livecode
>>>> Sent: Thursday, May 31, 2018 12:10 PM
>>>> To: How to use LiveCode <[hidden email]>
>>>> Cc: J. Landman Gay <[hidden email]>
>>>> Subject: Re: Android APK sanity check
>>>>
>>>> I created a plain do-nothing stack and it works on my Samsung. Then
>>>> I set the inclusions to same ones in my working project. The plain
>>>> stack then had the same misbehavior -- black screen and crash on launch.
>>>>
>>>> One by one I turned off each inclusion, tested, and then turned it
>>>> back on and disabled the next one. It looks like the culprit is
>>>> mergJSON.
>>>> With that included I get the crash, without it the apk behaves.
>>>>
>>>> I'll submit my test stack and a bug report.
>>>>
>>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>>>> Hi all,
>>>>>
>>>>> The first thing that came to my mind was the bug report that Paul
>>>>> referenced, but I had a look at the Samsung S5 specs and it seems
>>>>> it has an ARM chip, so it should not be affected by this bug.
>>>>>
>>>>> @Jacque does that happen with any android standalone you build
>>>>> with LC 9.0.0, or just this particular one?
>>>>>
>>>>> Best,
>>>>> Panos
>>>>
>>>>
>>>
>>>
>>
>>
>
>


--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
Okay, I'm stumped. I have a Nexus 7 too, running Android 6.0.1. I put the
test apk on it and it crashes on launch every time. I tried relaunching
several times.

Thanks for the input, maybe the team can make something of it.
--
Jacqueline Landman Gay | [hidden email]
HyperActive Software | http://www.hyperactivesw.com
On May 31, 2018 8:31:33 PM Clarence Martin via use-livecode
<[hidden email]> wrote:

> I just uploaded this to my Nexus7 and it works the same way. It initially
> opens with a blank screen and then opens correctly.
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 4:20 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> @Clarence, I just uploaded an apk I built on my Mac. Could you check the
> bug report again and try the apk I put there? Thanks for your time.
>
> On 5/31/18 5:49 PM, J. Landman Gay via use-livecode wrote:
>> I just took another look and I see that the identifier had reverted to
>> the default, so that explains why you had to change it. Even after I
>> reset it to something unique though it still fails here. It looks like
>> it's time for the LC guys to employ their magic.
>>
>> On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:
>>> Thanks for testing. Maybe it's a Mac problem. The identifier
>>> shouldn't matter in this case though, if you were originally using
>>> the unique one I put into the stack. So that's odd too.
>>>
>>> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
>>>> The problem that I had, had  to do with the identifier name and had
>>>> nothing to do with anything else. I remember that from earlier
>>>> problems that Panos identified for me.
>>>> The test stack worked on both Android Devices that I have.
>>>> More info on my system:
>>>> Windows 10 computer with the Java jdk 1.8.0_171.
>>>>
>>>> -----Original Message-----
>>>> From: use-livecode <[hidden email]> On Behalf
>>>> Of J.
>>>> Landman Gay via use-livecode
>>>> Sent: Thursday, May 31, 2018 1:02 PM
>>>> To: How to use LiveCode <[hidden email]>
>>>> Cc: J. Landman Gay <[hidden email]>
>>>> Subject: Re: Android APK sanity check
>>>>
>>>> Thanks for the comments. I've actually seen the problem with initial
>>>> startup on a few apps but in this case a relaunch still crashes. :(
>>>>
>>>> Since you have a few older devices, it might help the team narrow
>>>> down what's affected if you try out my test stack. Bug report is here:
>>>> https://quality.livecode.com/show_bug.cgi?id=21325
>>>>
>>>> I only have Android Marshmallow on my test phone(s) but I'm betting
>>>> it will fail with any older OS. Or it may be the version of Java I
>>>> installed, which I believe LC 9 required.
>>>>
>>>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>>>>> Hi Jacque,
>>>>> You have been one of the people on the List that has answered many
>>>>> of my questions about building Android Applications. I do have an
>>>>> application that uses mergJSON and the problem that I have is only
>>>>> during the initial starting of the application after the APK is
>>>>> loaded. I also get a blank initial screen. I found that if I close
>>>>> the application and then restart the application - it runs. I have
>>>>> also had problems with applications locking up on one Android
>>>>> Device and will run on another without problems. The problems that
>>>>> I encountered were mainly opening data files across the internet on
>>>>> the failing device. I actually solved some of those problems by
>>>>> putting a delay after  I call for data across the internet. Both
>>>>> devices are using Android 5.1.1. The failing Device  is a Nexus 7
>>>>> and the other device that doesn't fail is a generic X10 Chinese
>>>>> cheaper Tablet. The only other
>>>> problem I noticed with LC 9 is a latency in starting the applications.
>>>>>
>>>>> -----Original Message-----
>>>>> From: use-livecode <[hidden email]> On
>>>>> Behalf Of J.
>>>>> Landman Gay via use-livecode
>>>>> Sent: Thursday, May 31, 2018 12:10 PM
>>>>> To: How to use LiveCode <[hidden email]>
>>>>> Cc: J. Landman Gay <[hidden email]>
>>>>> Subject: Re: Android APK sanity check
>>>>>
>>>>> I created a plain do-nothing stack and it works on my Samsung. Then
>>>>> I set the inclusions to same ones in my working project. The plain
>>>>> stack then had the same misbehavior -- black screen and crash on launch.
>>>>>
>>>>> One by one I turned off each inclusion, tested, and then turned it
>>>>> back on and disabled the next one. It looks like the culprit is
>>>>> mergJSON.
>>>>> With that included I get the crash, without it the apk behaves.
>>>>>
>>>>> I'll submit my test stack and a bug report.
>>>>>
>>>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> The first thing that came to my mind was the bug report that Paul
>>>>>> referenced, but I had a look at the Samsung S5 specs and it seems
>>>>>> it has an ARM chip, so it should not be affected by this bug.
>>>>>>
>>>>>> @Jacque does that happen with any android standalone you build
>>>>>> with LC 9.0.0, or just this particular one?
>>>>>>
>>>>>> Best,
>>>>>> Panos
>
>
> --
> Jacqueline Landman Gay         |     [hidden email]
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

RE: Android APK sanity check

Tore Nilsen via use-livecode
I have to agree. The APK file that you  provided did run on my Nexus7 but
had some bad effects on both o my Devices. My Android Program that I have
that's under development started having loading problems on my Nexus7 and
had to be removed through the apps settings under the Android Settings menu.
It now works again. This didn't happen when I ran your test script and
loaded through the Android App test menu. I also had to do a Reboot Reset on
the other Android Device in order to get that Android device to run "as
normal".
So, my conclusion is: The application that creates the APK file is somehow
corrupted but "sort of" runs. But once installed corrupts the Android System
(if that makes sense to you)., although it doesn't do this if created
locally via the Development "test" option. I haven't tried to used your test
script to create an APK file locally. I will try that a bit later and update
that result for you.
Later!

-----Original Message-----
From: use-livecode <[hidden email]> On Behalf Of J.
Landman Gay via use-livecode
Sent: Thursday, May 31, 2018 10:41 PM
To: How to use LiveCode <[hidden email]>
Cc: J. Landman Gay <[hidden email]>
Subject: RE: Android APK sanity check

Okay, I'm stumped. I have a Nexus 7 too, running Android 6.0.1. I put the
test apk on it and it crashes on launch every time. I tried relaunching
several times.

Thanks for the input, maybe the team can make something of it.
--
Jacqueline Landman Gay | [hidden email] HyperActive Software |
http://www.hyperactivesw.com On May 31, 2018 8:31:33 PM Clarence Martin via
use-livecode <[hidden email]> wrote:

> I just uploaded this to my Nexus7 and it works the same way. It
> initially opens with a blank screen and then opens correctly.
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.

> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 4:20 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: Re: Android APK sanity check
>
> @Clarence, I just uploaded an apk I built on my Mac. Could you check
> the bug report again and try the apk I put there? Thanks for your time.
>
> On 5/31/18 5:49 PM, J. Landman Gay via use-livecode wrote:
>> I just took another look and I see that the identifier had reverted
>> to the default, so that explains why you had to change it. Even after
>> I reset it to something unique though it still fails here. It looks
>> like it's time for the LC guys to employ their magic.
>>
>> On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:
>>> Thanks for testing. Maybe it's a Mac problem. The identifier
>>> shouldn't matter in this case though, if you were originally using
>>> the unique one I put into the stack. So that's odd too.
>>>
>>> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
>>>> The problem that I had, had  to do with the identifier name and had
>>>> nothing to do with anything else. I remember that from earlier
>>>> problems that Panos identified for me.
>>>> The test stack worked on both Android Devices that I have.
>>>> More info on my system:
>>>> Windows 10 computer with the Java jdk 1.8.0_171.
>>>>
>>>> -----Original Message-----
>>>> From: use-livecode <[hidden email]> On
>>>> Behalf Of J.
>>>> Landman Gay via use-livecode
>>>> Sent: Thursday, May 31, 2018 1:02 PM
>>>> To: How to use LiveCode <[hidden email]>
>>>> Cc: J. Landman Gay <[hidden email]>
>>>> Subject: Re: Android APK sanity check
>>>>
>>>> Thanks for the comments. I've actually seen the problem with
>>>> initial startup on a few apps but in this case a relaunch still
>>>> crashes. :(
>>>>
>>>> Since you have a few older devices, it might help the team narrow
>>>> down what's affected if you try out my test stack. Bug report is here:
>>>> https://quality.livecode.com/show_bug.cgi?id=21325
>>>>
>>>> I only have Android Marshmallow on my test phone(s) but I'm betting
>>>> it will fail with any older OS. Or it may be the version of Java I
>>>> installed, which I believe LC 9 required.
>>>>
>>>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
>>>>> Hi Jacque,
>>>>> You have been one of the people on the List that has answered many
>>>>> of my questions about building Android Applications. I do have an
>>>>> application that uses mergJSON and the problem that I have is only
>>>>> during the initial starting of the application after the APK is
>>>>> loaded. I also get a blank initial screen. I found that if I close
>>>>> the application and then restart the application - it runs. I have
>>>>> also had problems with applications locking up on one Android
>>>>> Device and will run on another without problems. The problems that
>>>>> I encountered were mainly opening data files across the internet
>>>>> on the failing device. I actually solved some of those problems by
>>>>> putting a delay after  I call for data across the internet. Both
>>>>> devices are using Android 5.1.1. The failing Device  is a Nexus 7
>>>>> and the other device that doesn't fail is a generic X10 Chinese
>>>>> cheaper Tablet. The only other
>>>> problem I noticed with LC 9 is a latency in starting the applications.
>>>>>
>>>>> -----Original Message-----
>>>>> From: use-livecode <[hidden email]> On
>>>>> Behalf Of J.
>>>>> Landman Gay via use-livecode
>>>>> Sent: Thursday, May 31, 2018 12:10 PM
>>>>> To: How to use LiveCode <[hidden email]>
>>>>> Cc: J. Landman Gay <[hidden email]>
>>>>> Subject: Re: Android APK sanity check
>>>>>
>>>>> I created a plain do-nothing stack and it works on my Samsung.
>>>>> Then I set the inclusions to same ones in my working project. The
>>>>> plain stack then had the same misbehavior -- black screen and crash on
launch.

>>>>>
>>>>> One by one I turned off each inclusion, tested, and then turned it
>>>>> back on and disabled the next one. It looks like the culprit is
>>>>> mergJSON.
>>>>> With that included I get the crash, without it the apk behaves.
>>>>>
>>>>> I'll submit my test stack and a bug report.
>>>>>
>>>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
>>>>>> Hi all,
>>>>>>
>>>>>> The first thing that came to my mind was the bug report that Paul
>>>>>> referenced, but I had a look at the Samsung S5 specs and it seems
>>>>>> it has an ARM chip, so it should not be affected by this bug.
>>>>>>
>>>>>> @Jacque does that happen with any android standalone you build
>>>>>> with LC 9.0.0, or just this particular one?
>>>>>>
>>>>>> Best,
>>>>>> Panos
>
>
> --
> Jacqueline Landman Gay         |     [hidden email]
> HyperActive Software           |     http://www.hyperactivesw.com
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode




_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode


_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
Hi

I have had the same problem Using old and very new android devices, where
the program will give a blank/black screen on different versions of Android
with no ryme or reason.

Sometimes it works on and older version of android with older hardware and
fails on a phone or tablet with say  the oreo version although the program
only needs a minimum of 4.1. and the api is correct.

The  same android on different hardware might or might not work (black
screen no errors reported no "crash")

YMMV.


Lagi

On 1 June 2018 at 11:31, Clarence Martin via use-livecode <
[hidden email]> wrote:

> I have to agree. The APK file that you  provided did run on my Nexus7 but
> had some bad effects on both o my Devices. My Android Program that I have
> that's under development started having loading problems on my Nexus7 and
> had to be removed through the apps settings under the Android Settings
> menu.
> It now works again. This didn't happen when I ran your test script and
> loaded through the Android App test menu. I also had to do a Reboot Reset
> on
> the other Android Device in order to get that Android device to run "as
> normal".
> So, my conclusion is: The application that creates the APK file is somehow
> corrupted but "sort of" runs. But once installed corrupts the Android
> System
> (if that makes sense to you)., although it doesn't do this if created
> locally via the Development "test" option. I haven't tried to used your
> test
> script to create an APK file locally. I will try that a bit later and
> update
> that result for you.
> Later!
>
> -----Original Message-----
> From: use-livecode <[hidden email]> On Behalf Of J.
> Landman Gay via use-livecode
> Sent: Thursday, May 31, 2018 10:41 PM
> To: How to use LiveCode <[hidden email]>
> Cc: J. Landman Gay <[hidden email]>
> Subject: RE: Android APK sanity check
>
> Okay, I'm stumped. I have a Nexus 7 too, running Android 6.0.1. I put the
> test apk on it and it crashes on launch every time. I tried relaunching
> several times.
>
> Thanks for the input, maybe the team can make something of it.
> --
> Jacqueline Landman Gay | [hidden email] HyperActive Software |
> http://www.hyperactivesw.com On May 31, 2018 8:31:33 PM Clarence Martin
> via
> use-livecode <[hidden email]> wrote:
>
> > I just uploaded this to my Nexus7 and it works the same way. It
> > initially opens with a blank screen and then opens correctly.
> >
> > -----Original Message-----
> > From: use-livecode <[hidden email]> On Behalf Of
> J.
>
> > Landman Gay via use-livecode
> > Sent: Thursday, May 31, 2018 4:20 PM
> > To: How to use LiveCode <[hidden email]>
> > Cc: J. Landman Gay <[hidden email]>
> > Subject: Re: Android APK sanity check
> >
> > @Clarence, I just uploaded an apk I built on my Mac. Could you check
> > the bug report again and try the apk I put there? Thanks for your time.
> >
> > On 5/31/18 5:49 PM, J. Landman Gay via use-livecode wrote:
> >> I just took another look and I see that the identifier had reverted
> >> to the default, so that explains why you had to change it. Even after
> >> I reset it to something unique though it still fails here. It looks
> >> like it's time for the LC guys to employ their magic.
> >>
> >> On 5/31/18 5:44 PM, J. Landman Gay via use-livecode wrote:
> >>> Thanks for testing. Maybe it's a Mac problem. The identifier
> >>> shouldn't matter in this case though, if you were originally using
> >>> the unique one I put into the stack. So that's odd too.
> >>>
> >>> On 5/31/18 5:07 PM, Clarence Martin via use-livecode wrote:
> >>>> The problem that I had, had  to do with the identifier name and had
> >>>> nothing to do with anything else. I remember that from earlier
> >>>> problems that Panos identified for me.
> >>>> The test stack worked on both Android Devices that I have.
> >>>> More info on my system:
> >>>> Windows 10 computer with the Java jdk 1.8.0_171.
> >>>>
> >>>> -----Original Message-----
> >>>> From: use-livecode <[hidden email]> On
> >>>> Behalf Of J.
> >>>> Landman Gay via use-livecode
> >>>> Sent: Thursday, May 31, 2018 1:02 PM
> >>>> To: How to use LiveCode <[hidden email]>
> >>>> Cc: J. Landman Gay <[hidden email]>
> >>>> Subject: Re: Android APK sanity check
> >>>>
> >>>> Thanks for the comments. I've actually seen the problem with
> >>>> initial startup on a few apps but in this case a relaunch still
> >>>> crashes. :(
> >>>>
> >>>> Since you have a few older devices, it might help the team narrow
> >>>> down what's affected if you try out my test stack. Bug report is here:
> >>>> https://quality.livecode.com/show_bug.cgi?id=21325
> >>>>
> >>>> I only have Android Marshmallow on my test phone(s) but I'm betting
> >>>> it will fail with any older OS. Or it may be the version of Java I
> >>>> installed, which I believe LC 9 required.
> >>>>
> >>>> On 5/31/18 2:46 PM, Clarence Martin via use-livecode wrote:
> >>>>> Hi Jacque,
> >>>>> You have been one of the people on the List that has answered many
> >>>>> of my questions about building Android Applications. I do have an
> >>>>> application that uses mergJSON and the problem that I have is only
> >>>>> during the initial starting of the application after the APK is
> >>>>> loaded. I also get a blank initial screen. I found that if I close
> >>>>> the application and then restart the application - it runs. I have
> >>>>> also had problems with applications locking up on one Android
> >>>>> Device and will run on another without problems. The problems that
> >>>>> I encountered were mainly opening data files across the internet
> >>>>> on the failing device. I actually solved some of those problems by
> >>>>> putting a delay after  I call for data across the internet. Both
> >>>>> devices are using Android 5.1.1. The failing Device  is a Nexus 7
> >>>>> and the other device that doesn't fail is a generic X10 Chinese
> >>>>> cheaper Tablet. The only other
> >>>> problem I noticed with LC 9 is a latency in starting the applications.
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: use-livecode <[hidden email]> On
> >>>>> Behalf Of J.
> >>>>> Landman Gay via use-livecode
> >>>>> Sent: Thursday, May 31, 2018 12:10 PM
> >>>>> To: How to use LiveCode <[hidden email]>
> >>>>> Cc: J. Landman Gay <[hidden email]>
> >>>>> Subject: Re: Android APK sanity check
> >>>>>
> >>>>> I created a plain do-nothing stack and it works on my Samsung.
> >>>>> Then I set the inclusions to same ones in my working project. The
> >>>>> plain stack then had the same misbehavior -- black screen and crash
> on
> launch.
> >>>>>
> >>>>> One by one I turned off each inclusion, tested, and then turned it
> >>>>> back on and disabled the next one. It looks like the culprit is
> >>>>> mergJSON.
> >>>>> With that included I get the crash, without it the apk behaves.
> >>>>>
> >>>>> I'll submit my test stack and a bug report.
> >>>>>
> >>>>> On 5/31/18 3:12 AM, panagiotis merakos via use-livecode wrote:
> >>>>>> Hi all,
> >>>>>>
> >>>>>> The first thing that came to my mind was the bug report that Paul
> >>>>>> referenced, but I had a look at the Samsung S5 specs and it seems
> >>>>>> it has an ARM chip, so it should not be affected by this bug.
> >>>>>>
> >>>>>> @Jacque does that happen with any android standalone you build
> >>>>>> with LC 9.0.0, or just this particular one?
> >>>>>>
> >>>>>> Best,
> >>>>>> Panos
> >
> >
> > --
> > Jacqueline Landman Gay         |     [hidden email]
> > HyperActive Software           |     http://www.hyperactivesw.com
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
> >
> >
> > _______________________________________________
> > use-livecode mailing list
> > [hidden email]
> > Please visit this url to subscribe, unsubscribe and manage your
> > subscription preferences:
> > http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription
> preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
>
> _______________________________________________
> use-livecode mailing list
> [hidden email]
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>
_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Reply | Threaded
Open this post in threaded view
|

Re: Android APK sanity check

Tore Nilsen via use-livecode
On 6/1/18 6:24 AM, Lagi Pittas via use-livecode wrote:

> I have had the same problem Using old and very new android devices, where
> the program will give a blank/black screen on different versions of Android
> with no ryme or reason.
>
> Sometimes it works on and older version of android with older hardware and
> fails on a phone or tablet with say  the oreo version although the program
> only needs a minimum of 4.1. and the api is correct.
>
> The  same android on different hardware might or might not work (black
> screen no errors reported no "crash")

If anyone else cares to test, the bug report could use your input if you
get a crash. So far, I'm the only one who is having a problem. There are
test files you can use and way too many logs at:

https://quality.livecode.com/show_bug.cgi?id=21325

--
Jacqueline Landman Gay         |     [hidden email]
HyperActive Software           |     http://www.hyperactivesw.com

_______________________________________________
use-livecode mailing list
[hidden email]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode