Re: Optimizing for small Android devices

So did Russia BTW. But Germany's problems were not simply that the tanks were more complex and expensive to manufacture. They were suffering from a severe shortage of materials, and also some design problems. The Tiger as I recall had a turret that had to be hand cranked. They were also so heavy

Re: Optimizing for small Android devices

Mark: Wow, yes, it does help! I hope you had a great Christimas and are refreshed ready to face all of us again (smile) Your entire email should be posted to some knowledge base somewhere! As for speed optimization: - Alternate images I will make 1 X images right away for my home "portal"

Re: Optimizing for small Android devices

On 2017-12-27 06:04, Sannyasin Brahmanathaswami via use-livecode wrote: Any thoughts in this area? In terms of images / screen resolution etc... The first thing to ensure is that *all* your images objects use the filename property rather than embedding the image data in the stackfile via the

Re: Optimizing for small Android devices

On 12/30/17 2:44 PM, Sannyasin Brahmanathaswami via use-livecode wrote: I think we need to wait until HQ weighs in on my bug report. Regardless of the fact that it works on iOS and Oreo, one has to wonder how on earth we can close a stack which is set to destroy on close, turn acceleratedRender

Re: Optimizing for small Android devices

Reading this in depth. yes, reallocation of bit map space is beyond the developer's realm… I spotted this too… RGB 565… Anyone using this and getting smaller files sizes ver current jpgs? I'm not seeing this as an option in Photoshop on Mac. How we reduced our Android app’s memory

Re: Optimizing for small Android devices

This looks very useful . I think we need to wait until HQ weighs in on my bug report. Regardless of the fact that it works on iOS and Oreo, one has to wonder how on earth we can close a stack which is set to destroy on close, turn acceleratedRendering to false (assume previously cached control

Re: Optimizing for small Android devices

Worth reading just to find out about the 57 MB app memory limit. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com On December 29, 2017 9:54:34 PM Richard Gaskin via use-livecode wrote: While looking for one o

Re: Optimizing for small Android devices

While looking for one of the URLs I included in my last post, I came across this: How we reduced our Android app’s memory footprint by 50% I have no idea if those strategies would make sen

Re: Optimizing for small Android devices

Sannyasin Brahmanathaswami wrote: > I would not even know where to start to understand what to what extent > an app is overloading RAM on Android. How do we measure this stuff. Settings -> Developer Options -> Running services That brings up a simple list of processes in memory, noting among o

Re: Optimizing for small Android devices

I certainly did not mean to imply by "only" that pointed to the market share of phones with 1 GB ram. OT: I was just reading Quora about how US overwhelming Germany with sheer numbers of tanks and jets that had much lower specs than German made tanks/planes. But we won on our sheer industrial p

Re: Optimizing for small Android devices

Sannyasin Brahmanathaswami wrote: > To what extent we can realistically fit this app onto a phone with > only 1GB of RAM… I don't know. "Only"? That's a lot of phones -- Richard Gaskin Fourth World S

Re: Optimizing for small Android devices

On 12/29/17 2:25 PM, Sannyasin Brahmanathaswami via use-livecode wrote: To what extent we can realistically fit this app onto a phone with only 1GB of RAM… I don't know. So it's a memory problem after all. Google is making/has made a slimmed-down version of Android specifically for India and

Re: Optimizing for small Android devices

FYI here is Aravind's from Kerala comments today. To what extent we can realistically fit this app onto a phone with only 1GB of RAM… I don't know. Perhaps this is useful for other Android developers looking for a broad base in Asia, although this may be all "old news" to most of you… here it i

Re: Optimizing for small Android devices

That's a different model than Google gave me. This one has better specs. I'm not sure how the CPU compares to the Snapdragon but in general it seems sufficient. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com

Re: Optimizing for small Android devices

This is the Galaxy Samung A7 2017 http://www.samsung.com/in/smartphones/galaxy-a7-2017-sm-a720f/SM-A720FZDDINS/ pertainly doesn't seem under powered…how is a "2017" two years old?... do they just pump out the same device and slap new date on it? but the hardward/components are the same as they

Re: Optimizing for small Android devices

On 12/28/17 4:50 PM, Sannyasin Brahmanathaswami via use-livecode wrote: So, "weird" … Galaxy Samsung A7 in India running Android version 7.0… --- problems Moto G4 Plus, London Android 7 -- users says it works just fine The Moto is 2 years newer, has a faster CPU, and double or triple the me

Re: Optimizing for small Android devices

Great pointer's Andy, I will try those browser checks… TS Net does not interact with either the browser or a mobile play that streams audio, so we are "on our own… " to Monitor those. Meanwhile this is from London, happy new user --- "So far so good. No problems, everything running smoothl

Re: Optimizing for small Android devices

Also are you making sure the destroyStack to true. This should be automatically done but there is no harm in forcing it. set the destroyStack of this stack to true It might also be useful to monitor these events in the browser widget and set a timer between the browserDocumentLoadBegin and brows

Re: Optimizing for small Android devices

I don't think its such an issue targeting the latest Android versions as Google's new developer rules as August 2018 will require that apps will be targeted at the last latest build. http://developers.googleblog.com/2017/12/improving-app-security-and-performance.html

Re: Optimizing for small Android devices

I am going thru Aravind's reports. His phone is top of the line Android… Samsung Galaxy A7 (3GB RAM) 7.0 Nougat, It appears that 8.1.9 RC 1 did not fix all the Android rendering issues… yes, the problem of leaving the app via home or app switch and coming back to the app, yes, that is solved

Re: Optimizing for small Android devices

If you limit your user base to Android 8.1 almost no one can use it. Right now it has a very tiny user base, I think only Pixel users have that version. It was just pushed to Pixels a little while ago. A whole lot of devices are still waiting for Android 7. On December 27, 2017 8:49:02 PM San

Re: Optimizing for small Android devices

@ Andy (cc support) Yes, I used tinyPng I have paid for their 50 image at a time option, awesome tool, I think we will get a site license of photoshop plug in… The home card(s) (navigation "portals) on the app are one big parent scrolling parent group with some subgroups. max 8 "rows) with the

Re: Optimizing for small Android devices

7 installs end of day one..yesterday End of today, up to 21 But with 61 crashes already! Yikes. So I expect it will get hit pretty hard... I put signs up around here and we are getting about 400 visitors a day… I expect about 50% of them are on Android… I'll have to keep the promotion quiet un

Re: Optimizing for small Android devices

Besides the memory footprint, there could be stress on the CPU when running scripts that aren't tightly optimized. You might see what can be pared down there. Big job, I know, with a project this large. On 12/26/17 11:04 PM, Sannyasin Brahmanathaswami via use-livecode wrote: Our new SivaSiva a

Re: Optimizing for small Android devices

Do you compress your png images? If not give this a try. https://tinypng.com - Andy Piddock My software never has bugs. It just develops random features. TinyIDE a Free alternative minimalist IDE Plugin for LiveCode Script editor Themer for LC http://2108.

Optimizing for small Android devices

Our new SivaSiva app expects a lot of horse power. If we want to optimize for smaller devices, I'm not sure where to begin. We can't really shrink graphics below 55k png for small thumbs… so if we have 8 of these on a card and a hero image around 200 K… we are talking about ~700K image data on