te:
>
>> Hi all,
>>
>> I just tested an older stack on my Android device, everything is fine.
>> Then I created a new stack for a little stack and always get this error
>> when selecting "Test" in the LC dev menu.
>> <https://www.drop
w.com
On August 11, 2022 5:31:36 AM Klaus major-k via use-livecode
wrote:
Hi all,
I just tested an older stack on my Android device, everything is fine.
Then I created a new stack for a little stack and always get this error
when selecting "Test" in the LC dev menu.
<https:/
On Aug 11, 2022, at 6:39 AM, Klaus major-k via use-livecode
>> wrote:
>> Am 11.08.2022 um 12:30 schrieb Klaus major-k via use-livecode
>> :
>>>
>>> Hi all,
>>>
>>> I just tested an older stack on my Android device, everything is fine.
>
or-k via use-livecode
>> :
>>
>> Hi all,
>>
>> I just tested an older stack on my Android device, everything is fine.
>> Then I created a new stack for a little stack and always get this error
>> when selecting "Test" in the LC dev menu.
>
> Am 11.08.2022 um 12:30 schrieb Klaus major-k via use-livecode
> :
>
> Hi all,
>
> I just tested an older stack on my Android device, everything is fine.
> Then I created a new stack for a little stack and always get this error
> when selecting "Test&
Hi all,
I just tested an older stack on my Android device, everything is fine.
Then I created a new stack for a little stack and always get this error
when selecting "Test" in the LC dev menu.
<https://www.dropbox.com/s/j89i1ewpxh5ixny/stream_install_failed.png?dl=0>
Only scri
-) and tested, she could create an APK which runs
> fine on her Android device.
>
> Then we downloaded the neccessary package for the barcode scanner from here
> https://dl.google.com/android/repository/google_m2repository_gms_v11_3_rc05_wear_2_0_5.zip
>
> Got the hint from here: <
Hi Paul,
> Am 21.10.2021 um 13:43 schrieb Paul Richards via use-livecode
> :
>
> Hi Klaus,
>
> I thought the Barcode scanner widget was only available in Indy & Business
> editions. Which may explain why it isn't showing up when built from Community
> edition.
ah, yes, did not see this inf
Sent: 21 October 2021 12:38
To: How to use LiveCode
Cc: Klaus major-k
Subject: All software installed, but no QR code scanner on Android device
Hi friends,
last week my customer and me (via TeamViewer) installed the latest Android
Studio on my customers machine, which runs Windows 10 64 bit.
W
Hi friends,
last week my customer and me (via TeamViewer) installed the latest Android
Studio on my customers machine, which runs Windows 10 64 bit.
We finally managed this ;-) and tested, she could create an APK which runs fine
on her Android device.
Then we downloaded the neccessary package
Hi friends,
last week my customer and me (via TeamViewer) installed the latest Android
Studio on my customers machine, which runs Windows 10 64 bit.
We finally managed this ;-) and tested, she could create an APK which runs fine
on her Android device.
Then we downloaded the neccessary package
On 9/8/17 8:46 PM, Sannyasin Brahmanathaswami via use-livecode wrote:
MobileBuildInfo for Android (see below)
Is anyone tracking this stuff? If so, what, from your analytics experience is
most useful? And why?
The most useful for me would be to get the hardware serial number for
tracking pur
Assuming we send data back to the mothership for analytic, then:
If we want to know all about the device running our app.
I asked myself: how much and how far can we go?
-- the platform
# gets us the bare minimum, OS
-- the screenrect
# that's useful especially for the myriad of Androids
gt;>>
>>>> --
>>>> Jacqueline Landman Gay | jac...@hyperactivesw.com
>>>> HyperActive Software | http://www.hyperactivesw.com
>>>>
>>>>
>>>>
>>>>
>>>> On August 2, 201
>>>> I just put my app on a galaxy tab E as a test.
>>>>
>>>> It is painfully slow, but not just in the LC portion of the app. The map,
>>>> delivered through a browser widget, is also slow.
>>>>
>>>> So, I used the regula
;>
>>> I just put my app on a galaxy tab E as a test.
>>>
>>> It is painfully slow, but not just in the LC portion of the app. The map,
>>> delivered through a browser widget, is also slow.
>>>
>>> So, I used the regular browser (chrome)
st put my app on a galaxy tab E as a test.
>>
>> It is painfully slow, but not just in the LC portion of the app. The map,
>> delivered through a browser widget, is also slow.
>>
>> So, I used the regular browser (chrome) at the webglearth website. That
>> was slow
Hi Hermann,
That page is a great resource!
Some of their measurements might be a good proxy for GPU power, like the max
viewport size and a couple others.
It would be preferable to fully internalize the system check. I will look
through the page source to see what JS commands they use to measu
> Jonathan wrote:
> It sounds like I need to find a way to detect the processing speed
> of the device.
Did you alread try to use webgl? See the source of
https://browserleaks.com/webgl
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please
rtion of the app. The map,
>> delivered through a browser widget, is also slow.
>>
>> So, I used the regular browser (chrome) at the webglearth website. That was
>> slow too, although not as bad. I think the main difference was that the map
>> div at their website i
h not as bad. I think the main difference was that the map
div at their website is small, so it takes less processing power.
I had thought I selected a midlevel Android device that can handle moderate
amounts of computation.
In y'alls' experience, are android devices just slow? Do they
. I think the main difference was that the map div
at their website is small, so it takes less processing power.
I had thought I selected a midlevel Android device that can handle moderate
amounts of computation.
In y'alls' experience, are android devices just slow? Do they hav
Mark Wieder wrote:
> On 05/01/2017 04:52 PM, Richard Gaskin via use-livecode wrote:
>
>> How many Android devices have an x86 processor?
>>
>> My hunch is that there are more C++ apps on Android than there are x86
>> devices they can't run on, but I have no data on that.
>>
>
> I believe all the
On 05/01/2017 04:52 PM, Richard Gaskin via use-livecode wrote:
How many Android devices have an x86 processor?
My hunch is that there are more C++ apps on Android than there are x86
devices they can't run on, but I have no data on that.
I believe all the Chromebooks have Intel chips. This in
Jan Schenkel wrote:
> So LiveCode is a bit of an outsider, as the apps it produces spend
> little time in the Dalvik/ART virtual machine. All scripts run in the
> native portion, and events are funneled from the VM into native code
> to be handled there.
This leaves me wondering which percentage
On Sat, 4/29/17, Richard Gaskin via use-livecode
wrote:
>
> [snip]
>
> I had thought one of the reasons Android uses the Dalvik and ART
> VMs is because they're VMs, separating the APIs from processor architectures.
>
> If so, then the LC engine for Android is bytecode rather than machine
> co
J. Landman Gay wrote:
> On 4/29/17 1:25 PM, Richard Gaskin via use-livecode wrote:
>>> If that is so why can LiveCode make standalones that run on ARM
>>> Android?
>>
>> But can you run an Android APK made with LiveCode on an ARM Linux OS?
>
> Seems to me, Richmond's question is the same as "Why c
On 4/29/17 1:25 PM, Richard Gaskin via use-livecode wrote:
If that is so why can LiveCode make standalones that run on ARM
Android?
But can you run an Android APK made with LiveCode on an ARM Linux OS?
Seems to me, Richmond's question is the same as "Why can't we run a Mac
app on Windows? Th
Richmond Mathewson wrote:
> On 4/29/17 6:13 pm, Richard Gaskin via use-livecode wrote:
>> So while we can build for a very wide range of Linux distros,
>> Android is Linux-based (as in, it uses the kernel and a handful
>> of other packages) but is not a Linux distro per se.
>>
>> I don't believe
a use-livecode wrote:
>>> Isn't Android a type of Linux?
>>>
>>> Arguably a Linux standalone should work better on x86 Android devices
>>> . . .
>>>
>>> So; here's LiveCode's next headache:
>>>
>>> How to build a
of Linux?
>>>
>>> Arguably a Linux standalone should work better on x86 Android devices
>>> . . .
>>>
>>> So; here's LiveCode's next headache:
>>>
>>> How to build a Linux standalone which can be installed on an x86
Android
>
86 Android devices
. . .
So; here's LiveCode's next headache:
How to build a Linux standalone which can be installed on an x86 Android
device.
Mobile limitations are fairly severe, and most of the IDE tools
wouldn't work.
That's not what I meant: I meant the ability to hi
On 4/28/17 3:03 PM, Richmond Mathewson via use-livecode wrote:
Isn't Android a type of Linux?
Arguably a Linux standalone should work better on x86 Android devices . . .
So; here's LiveCode's next headache:
How to build a Linux standalone which can be installed on an x86
Isn't Android a type of Linux?
Arguably a Linux standalone should work better on x86 Android devices . . .
So; here's LiveCode's next headache:
How to build a Linux standalone which can be installed on an x86 Android
device.
Richmond.
On 4/26/17 10:26 pm, Colin Holgate v
a use-livecode
Sent: Wednesday, April 26, 2017 2:45 PM
To: use-livecode@lists.runrev.com
Cc: jonathandly...@gmail.com
Subject: Will LiveCode run an x86 android device?
I see that it won't run on an x86 emulator - will it work on on actual x86
device?
Sent from
Does it run arm-emulation automatically or do we need to warn it?
The parts I use that are processor-intensive are running in the browser widget,
which I assume runs on both architectures.
Sent from my iPhone
> On Apr 26, 2017, at 3:37 PM, jonathandly...@gmail.com wrote:
>
> Lol - thank you -
Lol - thank you - that is what I meant.
Sent from my iPhone
> On Apr 26, 2017, at 3:12 PM, Richmond Mathewson via use-livecode
> wrote:
>
> I don't think LiveCode (the development environment) will work on
> Android of any sort: but it should develop standalones that work on Android.
>
> Rich
x86 Android devices can run ARM code in emulation. The performance would be
better if you could publish to x86, but the app should work.
> On Apr 26, 2017, at 12:22 PM, Mike Bonner via use-livecode
> wrote:
>
> I don't think you can build for x86 android but i'm not positive.
>
> On Wed, Apr
I don't think you can build for x86 android but i'm not positive.
On Wed, Apr 26, 2017 at 1:12 PM, Richmond Mathewson via use-livecode <
use-livecode@lists.runrev.com> wrote:
> I don't think LiveCode (the development environment) will work on
> Android of any sort: but it should develop standalon
I don't think LiveCode (the development environment) will work on
Android of any sort: but it should develop standalones that work on Android.
Richmond.
On 4/26/17 9:45 pm, Jonathan Lynch via use-livecode wrote:
I see that it won't run on an x86 emulator - will it work on on actual x86
device?
I see that it won't run on an x86 emulator - will it work on on actual x86
device?
Sent from my iPhone
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
On 9/12/16 6:38 PM, J. Landman Gay wrote:
So I tried on a Samsung S4. On that device, the "installing" dialog
appears and nothing else happens. I waited two or three minutes, then
had to force-quit LC because there is no way to cancel the dialog.
And on restarting, it did install. No idea what
On 9/12/16 5:17 PM, panagiotis merakos wrote:
If the device name is shown but it is dimmed, could it be the case that you
have not selected to build for Android?
Yes, sorry, that was it. We're sharing the stack back and forth and I
should have realized the setting had been changed.
But now i
> On 13 Sep 2016, at 8:17 AM, panagiotis merakos wrote:
>
> If the device name is shown but it is dimmed, could it be the case that you
> have not selected to build for Android?
The other option would be if the mode of your stack is not 1 or it’s not the
topStack.
Cheers
Monte
__
If the device name is shown but it is dimmed, could it be the case that you
have not selected to build for Android?
On 12 Sep 2016 22:15, "J. Landman Gay" wrote:
> Was there a change in RC2 in recognizing Android test devices? I've tried
> three different ones and LC won't allow any of them. Term
Was there a change in RC2 in recognizing Android test devices? I've
tried three different ones and LC won't allow any of them. Terminal
("adb devices") sees them, and they are in the LC Test Target menu, but
the device name is dimmed and can't be selected.
I've relaunched LC several times, plu
wrote:
Hi Rod,
There's a few things you can try here which should resolve the issue.
http://stackoverflow.com/questions/5584976/android-device-chooser-my-device-seems-offline
When this has happened in the past for me, an adb kill-server and adb
start-server usually sorts things out
HCI, Augmented Reality, Games and In-car Systems
www.rodmc.com
twitter: rodlux
On Thu, Jun 18, 2015 at 3:01 PM, Neil Roger wrote:
> Hi Rod,
>
> There's a few things you can try here which should resolve the issue.
>
>
> http://stackoverflow.com/questions/5584976/android-
Hi Rod,
There's a few things you can try here which should resolve the issue.
http://stackoverflow.com/questions/5584976/android-device-chooser-my-device-seems-offline
When this has happened in the past for me, an adb kill-server and adb
start-server usually sorts things out.
Kind Re
Dear All,
I am trying to get Livecode to install an app on an Andoird (Moto G) phone.
While LC sees the the device as a target test device each time it comes to
try and install the app I receive a "device offline* error. The device has
been configured for debugging and developing etc so seems to b
On 5/14/2015 7:14 PM, Mike Bonner wrote:
>
>> Hey all, I was given an android device. A Contixo kids tablet. The owner
>> things there is a hardware issue (white screen, touch works, sounds work,
>> but can't see anything.) I suspect a horked update has caused issu
On 5/14/2015 7:14 PM, Mike Bonner wrote:
Hey all, I was given an android device. A Contixo kids tablet. The owner
things there is a hardware issue (white screen, touch works, sounds work,
but can't see anything.) I suspect a horked update has caused issues.
Since I can't get to an
Is the tablet older than 1 year? From their website:
Warranty Information
1-Year Worry-Free Guarantee: Customer Service & Tech Support
http://www.contixo.net/pages/Contact-Us.html#mobile-phones-home
On Thu, May 14, 2015 at 8:14 PM, Mike Bonner wrote:
> Hey all, I was given an
Hey all, I was given an android device. A Contixo kids tablet. The owner
things there is a hardware issue (white screen, touch works, sounds work,
but can't see anything.) I suspect a horked update has caused issues.
Since I can't get to any settings (on purpose) does anyone know o
; >
> > > > > Am thinking about playing with LiveCode and Android.
> > > > >
> > > > > Might there be one that is used more or is a very common size or
> > > features
> > > > > that most people want or use?
> > > > >
&
>
> > >
> > > On Sat, Sep 21, 2013 at 7:21 AM, Jim sims
> > > >
> wrote:
> > >
> > > > Am thinking about playing with LiveCode and Android.
> > > >
> > > > Might there be one that is used more or is a very com
ze or
> features
> > > that most people want or use?
> > >
> > > Doesn't necessarily have to be the cheapest but be good for testing
> code
> > > and have common features I guess.
> > >
> > > Any suggestions on an Android device?
> > &
gt; Am thinking about playing with LiveCode and Android.
> > >
> > > Might there be one that is used more or is a very common size or
> features
> > > that most people want or use?
> > >
> > > Doesn't necessarily have to be the
here be one that is used more or is a very common size or features
> > that most people want or use?
> >
> > Doesn't necessarily have to be the cheapest but be good for testing code
> > and have common features I guess.
> >
> > Any suggestions on an An
want or use?
>
> Doesn't necessarily have to be the cheapest but be good for testing code
> and have common features I guess.
>
> Any suggestions on an Android device?
>
>
> sims
>
___
use-livecode mailing list
use-liveco
Am thinking about playing with LiveCode and Android.
Might there be one that is used more or is a very common size or features
that most people want or use?
Doesn't necessarily have to be the cheapest but be good for testing code
and have common features I guess.
Any suggestions on an An
Figured it out. After updating to Win7, I had forgotten to also
re-install the tablet-specific USB driver.
Thanks.
--
Nicolas Cueto
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage yo
On 6/19/12 5:37 AM, Nicolas Cueto wrote:
Hello All,
LC and my Android phone: no problem connecting and testing.
LC and my Android tablet: the "Devpt > Test target" menu is grayed,
and clicking on "Test" gives "Unknown deployment platform".
I get that error if I have specified an OS version in
Some devices have to be specifically set up in the android sdk. For
example, the kindle fire...
http://mobile.tutsplus.com/tutorials/android/getting-started-with-kindle-fire-development/
(there is an official amazon page for setting up the kindle fire but I
couldn't find it. The link above is pr
Hello All,
LC and my Android phone: no problem connecting and testing.
LC and my Android tablet: the "Devpt > Test target" menu is grayed,
and clicking on "Test" gives "Unknown deployment platform".
I realize this is a very vague question, since there's many factors at
play -- all of which I thi
65 matches
Mail list logo
