Watch, Follow, &
Connect with Us

For forums, blogs and more please visit our
Developer Tools Community.


Welcome, Guest
Guest Settings
Help

Thread: Upgraded to Tokyo revealed that Android is very problematic


This question is not answered. Helpful answers available: 2. Correct answers available: 1.


Permlink Replies: 52 - Last Post: Mar 30, 2017 8:39 AM Last Post By: Markus Humm
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 7:29 AM
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 7:54 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
5. The memory consumption seems higher than the Berlin compiled version.

how do you check this ?
Dalija Prasnikar

Posts: 2,325
Registered: 11/9/99
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 8:18 AM   in response to: loki loki in response to: loki loki
loki loki wrote:
5. The memory consumption seems higher than the Berlin compiled version.

how do you check this ?

You can run Android Studio and observe your application while running.

--
Dalija Prasnikar
https://twitter.com/dalijap
https://plus.google.com/+DalijaPrasnikar
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 8:55 AM   in response to: Dalija Prasnikar in response to: Dalija Prasnikar
Dalija Prasnikar wrote:
loki loki wrote:
5. The memory consumption seems higher than the Berlin compiled version.

how do you check this ?

You can run Android Studio and observe your application while running.

--
Dalija Prasnikar
https://twitter.com/dalijap
https://plus.google.com/+DalijaPrasnikar

Hi

Thanks for the info. I will check it with Android Studio. Currently I used a task manager app that gives memory used by the apps on the device. I do acknowledge that it is not 100% accurate, but one can see when things are going south. That however is not my concern for now. Going from "working" to "not working" on Android is VERY concerning.

Regards
Stiaan
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:00 AM   in response to: loki loki in response to: loki loki
Am 25.03.2017 um 15:54 schrieb loki loki:
5. The memory consumption seems higher than the Berlin compiled version.

how do you check this ?

Hello,

not exactly about meassuring memory usage but maybe worth to vote for
anyway:

https://quality.embarcadero.com/browse/RSP-17159

Greetings

Markus
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 12:06 PM   in response to: Markus Humm in response to: Markus Humm
Markus Humm wrote:
Am 25.03.2017 um 15:54 schrieb loki loki:
5. The memory consumption seems higher than the Berlin compiled version.

how do you check this ?

Hello,

not exactly about meassuring memory usage but maybe worth to vote for
anyway:

https://quality.embarcadero.com/browse/RSP-17159

Greetings

Markus

Hi

Just voted!

Regards
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 7:35 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

What I've analysed so far:

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.

Confirmed.

2. TAniIndicator for example does work anymore.

Ouch! This thing royally screws up other components along with it. I'm still looking into this one.

3. Simple TEdit is very slow in response.

Seems OK to me. Can you describe this further?

4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application
useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is
actually showing!
7. Tab transistions is not happening at all.

I'll take a look at these later.

8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Is this in a plain app with a listbox of 10 items?

Can someone give some advise on how to start logging these issues as an urgent matter?

http://quality.embarcadero.com

Make sure you provide example code, and steps, where possible.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 10:58 PM   in response to: Dave Nottage in response to: Dave Nottage
Dave Nottage wrote:
Stiaan Pretorius wrote:

What I've analysed so far:

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.

Confirmed.

2. TAniIndicator for example does work anymore.

Ouch! This thing royally screws up other components along with it. I'm still looking into this one.

3. Simple TEdit is very slow in response.

Seems OK to me. Can you describe this further?

4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application
useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is
actually showing!
7. Tab transistions is not happening at all.

I'll take a look at these later.

8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Is this in a plain app with a listbox of 10 items?

Can someone give some advise on how to start logging these issues as an urgent matter?

http://quality.embarcadero.com

Make sure you provide example code, and steps, where possible.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi Dave

Our app in question is not a simple app at all. It is an application that is used to generate quotations for long term insurance. See my responses you your questions above:

3. Simple TEdit is very slow in response.
We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason, the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application
useless.
This works together with #3. Based on some user selections, some TListItems are enabled/disabled. The TListbox is never refreshed however. Again, the TEdits on the TListItems becomes useless. I will submit something to Quality.

6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is
actually showing!
Simple breakpoints will reveal this one.

7. Tab transistions is not happening at all.
It seems that the main thread becomes so busy with something else, that it cannot do anything else.

Keep in mind that the app worked perfectly compiled in Berlin. Now, I cant even think of deploying.

Is there a way that I can redirect my queries directly to you when logged on Quality?

Regards
Stiaan
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:17 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the
for is actually showing!
Simple breakpoints will reveal this one.

OK, I'll take a look at that, too,

7. Tab transistions is not happening at all.
It seems that the main thread becomes so busy with something else, that it cannot do anything else.

Since my last post, I've discovered that transitions do not work for me, either.

Is there a way that I can redirect my queries directly to you when logged on Quality?

I don't think so. Probably better to make a post here, quoting the report number. Bear in mind that I'm interested in
finding the causes, and suggesting solutions/workarounds; I'm not directly involved in fixing the issues for
Embarcadero.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:21 PM   in response to: Dave Nottage in response to: Dave Nottage
Dave Nottage wrote:
Stiaan Pretorius wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the
for is actually showing!
Simple breakpoints will reveal this one.

OK, I'll take a look at that, too,

7. Tab transistions is not happening at all.
It seems that the main thread becomes so busy with something else, that it cannot do anything else.

Since my last post, I've discovered that transitions do not work for me, either.

Is there a way that I can redirect my queries directly to you when logged on Quality?

I don't think so. Probably better to make a post here, quoting the report number. Bear in mind that I'm interested in
finding the causes, and suggesting solutions/workarounds; I'm not directly involved in fixing the issues for
Embarcadero.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi Dave

It seems as one dig around, more issues comes to the surface. I have spent little time on Android, but I will do so tomorrow. I will work through this post to log the Quality JIRA numbers for reference.

Do I need to log calls for the issues you have discovered as well?

Regards
Stiaan
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:28 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

Do I need to log calls for the issues you have discovered as well?

No, I'll do those. Thanks.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:31 PM   in response to: Dave Nottage in response to: Dave Nottage
Dave Nottage wrote:
Stiaan Pretorius wrote:

Do I need to log calls for the issues you have discovered as well?

No, I'll do those. Thanks.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi

Thanks for the effort. It is much appreciated!

I will do some sample apps to highlight the issues.

Can you please send the JIRA numbers so that I can at least vote for them... ;-)

Regards
Stiaan
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:34 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

Can you please send the JIRA numbers so that I can at least vote for them... ;-)

Will do

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:57 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

Can you please send the JIRA numbers so that I can at least vote for them... ;-)

Here's the one for TAniIndicator:

https://quality.embarcadero.com/browse/RSP-17165

It also interferes (if set to Enabled) with the styling at least on TButton and TEdit, but does not for TListBox. I
haven't looked into it any further.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 25, 2017 11:33 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 26.03.2017 um 08:21 schrieb Stiaan Pretorius:
Dave Nottage wrote:
Stiaan Pretorius wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the
for is actually showing!
Simple breakpoints will reveal this one.

OK, I'll take a look at that, too,

7. Tab transistions is not happening at all.
It seems that the main thread becomes so busy with something else, that it cannot do anything else.

Since my last post, I've discovered that transitions do not work for me, either.

Is there a way that I can redirect my queries directly to you when logged on Quality?

I don't think so. Probably better to make a post here, quoting the report number. Bear in mind that I'm interested in
finding the causes, and suggesting solutions/workarounds; I'm not directly involved in fixing the issues for
Embarcadero.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi Dave

It seems as one dig around, more issues comes to the surface. I have spent little time on Android, but I will do so tomorrow. I will work through this post to log the Quality JIRA numbers for reference.

Do I need to log calls for the issues you have discovered as well?

Hello,

yes please log all issues you know about. You might do a short keyword
search before logging to check if it's already known, but better we have
duplicates in the system than missing reports!

After reporting post the numbers here so we can track them as well and
may be adding further information if we saw further effects etc.

If you're on maintenance then theres
https://www.embarcadero.com/en/support
where you can create up to 3 cases which EMBT must directly answer.
Sometimes you might get a hotfix via this route (at least I already got
something I needed implemented that way). But going down this route
requires QP reports and before going down this route it might be wise to
wait a few days until the QP report you're going to refer to has been
opened already. Opened means that EMBT looked at it and confirmed it.

Greetings

Markus
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 12:21 AM   in response to: Dave Nottage in response to: Dave Nottage
I wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

You might need to provide a bit more insight into this one. I created an app with a TListBox, added a couple of
TListBoxItems and added TEdits inside of each one. They were fairly responsive for me. I have a Nexus 5X device.

One issue I did have though: after entering a value in an edit, setting focus to the other, then going back to the
first, entering any more characters duplicated the value that was already in the edit. I believe this is an issue that
was already evident for devices with Android 6 or greater, but still obviously annoying.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 12:25 AM   in response to: Dave Nottage in response to: Dave Nottage
Dave Nottage wrote:
I wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

You might need to provide a bit more insight into this one. I created an app with a TListBox, added a couple of
TListBoxItems and added TEdits inside of each one. They were fairly responsive for me. I have a Nexus 5X device.

One issue I did have though: after entering a value in an edit, setting focus to the other, then going back to the
first, entering any more characters duplicated the value that was already in the edit. I believe this is an issue that
was already evident for devices with Android 6 or greater, but still obviously annoying.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi Dave

I suspect it has to do with all the components combined.

Can you add a TAniIndicator as well to the form? I enable and disable mine when needed, thus it is always on the form, but the visibility depends on the action.
Also, all my buttons have glow effects, which might also have an effect?

I will do some prototyping tomorrow and will have better info.

Regards
Stiaan

Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 12:27 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:
Dave Nottage wrote:
I wrote:

We have a listbox with various TListItems. Embedded on these TListItems are TEdit, TCalanders etc. For some reason,
the TEdit is unresponsive at best. I will try and put a test app together to submit to Quality.

Then it might be a combination of TEdit inside of a TListBoxItem. I'll check that out.

You might need to provide a bit more insight into this one. I created an app with a TListBox, added a couple of
TListBoxItems and added TEdits inside of each one. They were fairly responsive for me. I have a Nexus 5X device.

One issue I did have though: after entering a value in an edit, setting focus to the other, then going back to the
first, entering any more characters duplicated the value that was already in the edit. I believe this is an issue that
was already evident for devices with Android 6 or greater, but still obviously annoying.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog

Hi Dave

I suspect it has to do with all the components combined.

Can you add a TAniIndicator as well to the form? I enable and disable mine when needed, thus it is always on the form, but the visibility depends on the action.
Also, all my buttons have glow effects, which might also have an effect?

I will do some prototyping tomorrow and will have better info.

Regards
Stiaan


Something to note that another user is experiencing the similar issues: https://forums.embarcadero.com/thread.jspa?threadID=248182&tstart=0
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 12:35 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

I suspect it has to do with all the components combined.

Perhaps. It would help to know how many.

Can you add a TAniIndicator as well to the form?

Did that; no difference to the edit performance.

I enable and disable mine when needed, thus it is always on the
form, but the visibility depends on the action. Also, all my buttons have glow effects, which might also have an
effect?

See my first comment, above :-)

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 2:21 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 25.03.2017 um 15:29 schrieb Stiaan Pretorius:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

Hello,

I was able to do a short test of my 55 KLoc Berlin Android project under
Tokyo now. The device I'm running it on is really low end and has
Android 4.4.

The Berlin compiled version runs quite ok on this device, the Tokyo one
has slowdowns in scrolling (TVertScrollbox) and I looks like depending
on which actions you did it gets quite unuseable and I had the feeling
that it once even locked up. I terminated it then.

The application uses one control from the TMS FMX UI pack, but no
TAniIndicator and it uses a modified FMX.StdCtrls.pas unit, but I
already synced back the Tokyo changes.

I didn't recreate the modified styles I use yet.

Greetings

Markus
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 7:48 AM   in response to: Markus Humm in response to: Markus Humm
Markus Humm wrote:
Am 25.03.2017 um 15:29 schrieb Stiaan Pretorius:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

Hello,

I was able to do a short test of my 55 KLoc Berlin Android project under
Tokyo now. The device I'm running it on is really low end and has
Android 4.4.

The Berlin compiled version runs quite ok on this device, the Tokyo one
has slowdowns in scrolling (TVertScrollbox) and I looks like depending
on which actions you did it gets quite unuseable and I had the feeling
that it once even locked up. I terminated it then.

The application uses one control from the TMS FMX UI pack, but no
TAniIndicator and it uses a modified FMX.StdCtrls.pas unit, but I
already synced back the Tokyo changes.

I didn't recreate the modified styles I use yet.

Greetings

Markus

Hi Markus

Thank you for your efforts. I also use TMS FMX UIPack and the scrollboxes extensively to make provision for the virtual keyboard.

From what you are describing is very similar to my experience. I also had Android warning me that the app became unresponsive. Can you make you test sample available as I would like to test it on my devices. I have high end and low end devices available ranging from Android 4.2, 5 and 6.

Regards
Stiaan
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 8:24 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 26.03.2017 um 16:48 schrieb Stiaan Pretorius:
Markus Humm wrote:
Am 25.03.2017 um 15:29 schrieb Stiaan Pretorius:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

Hello,

I was able to do a short test of my 55 KLoc Berlin Android project under
Tokyo now. The device I'm running it on is really low end and has
Android 4.4.

The Berlin compiled version runs quite ok on this device, the Tokyo one
has slowdowns in scrolling (TVertScrollbox) and I looks like depending
on which actions you did it gets quite unuseable and I had the feeling
that it once even locked up. I terminated it then.

The application uses one control from the TMS FMX UI pack, but no
TAniIndicator and it uses a modified FMX.StdCtrls.pas unit, but I
already synced back the Tokyo changes.

I didn't recreate the modified styles I use yet.

Greetings

Markus

Hi Markus

Thank you for your efforts. I also use TMS FMX UIPack and the scrollboxes extensively to make provision for the virtual keyboard.

From what you are describing is very similar to my experience. I also had Android warning me that the app became unresponsive. Can you make you test sample available as I would like to test it on my devices. I have high end and low end devices available ranging from Android 4.2, 5 and 6.

Regards
Stiaan

Hello,

unfortunatelly I can't. Its some app of my employer and current planning
is to not even put it into Google Play.

My app creates most of the controls visible on the mainly affected
screens at runtime in code. But that shouldn't change the situation.

Greetings

Markus
Eli M

Posts: 1,346
Registered: 11/9/13
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 8:15 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
My current theory is that the problem is in screen drawing + screen input.

So when you tap a button or drag your finger down a scroll bar it can't draw and accept the screen input at the same time (because of how the threading modal was changed).
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 8:25 AM   in response to: Eli M in response to: Eli M
Am 26.03.2017 um 17:15 schrieb Eli M:
My current theory is that the problem is in screen drawing + screen input.

So when you tap a button or drag your finger down a scroll bar it can't draw and accept the screen input at the same time (because of how the threading modal was changed).

Ok, let's assume you're right. How could that get fixed?

Greetings

Markus
Eli M

Posts: 1,346
Registered: 11/9/13
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 9:01 AM   in response to: Markus Humm in response to: Markus Humm
Not sure. The message queue needs to be pumped somehow. Application.ProcessMessages didn't change but doesn't work how it did either. TPlatformAndroid.InternalProcessMessages did change significantly.

It went from two threads where the main thread was the render thread and the TApplication thread was everything else to one thread and everything is now running synchronously render+timers+input. Maybe WindowManager.RenderIfNeeds; needs to be moved to it's own thread? Maybe TApplication.OnIdle can be pumped somehow.

procedure TPlatformAndroid.InternalProcessMessages;
var
  LDone: Boolean;
begin
  CheckSynchronize;
  TimerManager.ProcessQueueTimers;
 
  WindowManager.RenderIfNeeds;
  if not Terminating then
    try
      LDone := False;
      Application.DoIdle(LDone);
    except
      Application.HandleException(Application);
    end;
end;
 
procedure TApplication.ProcessMessages;
var
  AppService: IFMXApplicationService;
begin
  if TPlatformServices.Current.SupportsPlatformService(IFMXApplicationService, AppService) then
    while AppService.HandleMessage do { loop };
end;
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 8:43 AM   in response to: Eli M in response to: Eli M
On 3/26/2017 6:15 PM, Eli M wrote:
My current theory is that the problem is in screen drawing + screen input.

So when you tap a button or drag your finger down a scroll bar it can't draw and accept the screen input at the same time (because of how the threading modal was changed).

If you look my app ( https://tinyurl.com/kkgsloe under tokyo) you can
see that in my own scrollbox i do only drawing texture on canvas,
nothing else ... and the speed go down from 60 fps on berlin to 25 fps
on tokyo. but the most important is that When i calculate the fps it's
when their is no finger on the screen and when the scroll is moving
itself via the inertia (calculated via timer)

my i think it's connected to the timer or something very badly designed
in the openGL, and quite sure this is du to the merge of the java ui
thread with the main delphi thread.

i m just scared that it's could be not just a line of code to correct
it, but will need a full regression of all the new code added to tokyo
(worse case)

Also it's a very bad practice to fully rework an unit like they do with
plateform.android.pas. sometime this is necessary, but when it it, very
very deep quality check must be done. here it's seam close to 0 quality
check was maded :(

Eli M

Posts: 1,346
Registered: 11/9/13
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 9:22 AM   in response to: loki loki in response to: loki loki
If a normal single thread OpenGL app that is based on a while loop looks like the below and DoStuff() (which would handle timers and input etc) takes more time than the frames per second would allow it is going to block which I think is what we're seeing. Or maybe if DoStuff() is slow it is allowed to be queued up instead of run which would mean input/timers are not executed every render.

The original 2 thread modal was a good choice apparently.

// operating systems with no message queue
   while FApp.destroyRequested = 0 do
    begin
      DoStuff();
      Repaint();
    end;
 
// under Windows
 while GetMessage(Msg, 0, 0, 0) do
  begin
    if Msg.Message = WM_QUIT then
      Break;
    TranslateMessage(Msg);
    DispatchMessage(Msg);
    InvalidateRect(FHandle, nil, False);
  end;
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 1:02 PM   in response to: Eli M in response to: Eli M
On 3/26/2017 7:22 PM, Eli M wrote:
If a normal single thread OpenGL app that is based on a while loop looks like the below and DoStuff() (which would handle timers and input etc) takes more time than the frames per second would allow it is going to block which I think is what we're seeing. Or maybe if DoStuff() is slow it is allowed to be queued up instead of run which would mean input/timers are not executed every render.

The original 2 thread modal was a good choice apparently.

// operating systems with no message queue
   while FApp.destroyRequested = 0 do
    begin
      DoStuff();
      Repaint();
    end;
 
// under Windows
 while GetMessage(Msg, 0, 0, 0) do
  begin
    if Msg.Message = WM_QUIT then
      Break;
    TranslateMessage(Msg);
    DispatchMessage(Msg);
    InvalidateRect(FHandle, nil, False);
  end;

actually i just updated my demo
(https://quality.embarcadero.com/browse/RSP-17162) to show the max fps
under berlin and tokyo

so under tokyo a form without any control (so normally a super fast
paint) take around 35 ms where on berlin it's took around 60 ms

so i don't really know if it's the screen drawing that is slow (because
nothing to draw here) or if it's something else

Eli M

Posts: 1,346
Registered: 11/9/13
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 5:10 PM   in response to: Eli M in response to: Eli M
Oddly I'm not seeing the problems on a Samsung Galaxy S6 phone but I do see them on a Nexus 7 tablet. Both running Android 6.0.1. Same app.
Marc Bonnaud

Posts: 14
Registered: 7/1/16
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 27, 2017 1:39 AM   in response to: Eli M in response to: Eli M
I also have problems with Android and 10.2

The easiest test : I open a brand new multi-device project, put a TButton, compile and launch : ok.

Then I add just a TViewport3D (a small 100 x 100 without resizing) under the TButton, complie and launch : splash screen, then black screen.

Tested on a Samsung Galaxy S7 Android 6.0.1 and on an Asus Shield K1 with Android 7.0

Same test with Berlin 10.1 (no update 1 or 2) : no problem.

If this can help :

- I installed with the ..._esd file (without uninstalling the Berlin 10.1 version) and asked to download and installed everything (except the german and japanese language), including the SDK.

- When I plugged the phone on the USB and asked it to be recognized under Android - Android SDK 24.3.3 32 bit - target in the project manager, a window told me I had to first download the drivers, which I accepted.

- Then a CMD/"MS-DOS" window opened where I noticed some of the downloaded files were labelled "25.0" and some others "API 22", which left me a bit puzzled.

- When exploring the C:\Users\Public\Documents\Embarcadero\Studio\19.0\ directory, I noticed that there's no "Platform SDKs" folder like there is under "18.0", but eveything is in "CatalogRepository".

- In the program files / Java folder, the two folders added on March 23 when I installed Tokyo are "jdk1.8.0_60" and "jre1.8.0_60", while I also have older "jrel1.8.0_121", "jdk1.8.0_66" and "jdk1.7.0_71" folders.

- Nevertheless, in the Options/SDK manager tab, the Keytool and jarsigner locations shown are C:\Program Files\Java\jdk1.8.0_66\bin\KeyTool.exe and C:\Program Files\Java\jdk1.8.0_66\bin\JarSigner.exe, in Berlin 10.1 the locations are those under "jdk1.7.0_71"
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 1:50 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

7. Tab transistions is not happening at all.

Can you provide a reproducable case for this? I'm unable to.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Thiago Nassif D...

Posts: 6
Registered: 1/11/10
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 2:06 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Well
I didn´t verified all these, but I´m not being able to put my Android apps to work anymore (crash, animation problems, show frames problemas..)
. There is something really wrong with tokyo. Waiting for fix.


Stiaan Pretorius wrote:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 26, 2017 2:07 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:

6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is
actually showing!

I've done a short test for this, with this code:

constructor TForm1.Create(AOwner: TComponent);
begin
  inherited;
  TMessageManager.DefaultManager.SubscribeToMessage(TApplicationEventMessage, ApplicationEventMessageHandler);
end;
 
procedure TForm1.ApplicationEventMessageHandler(const Sender: TObject; const M: TMessage);
begin
  case TApplicationEventMessage(M).Value.Event of
    TApplicationEvent.FinishedLaunching:
      Log.d('Launch finished. Splash disappeared?');
    TApplicationEvent.BecameActive:
      Log.d('BecameActive');
  end;
end;
 
procedure TForm1.FormActivate(Sender: TObject);
begin
  Log.d('FormActivate');
end;
 
procedure TForm1.FormShow(Sender: TObject);
begin
  Log.d('FormShow');
end;


Results:

Tokyo:

03-27 07:27:50.690: I/info(13616): FMX: Project2: FormShow
03-27 07:27:50.690: I/info(13616): FMX: Project2: FormActivate
03-27 07:27:50.690: I/info(13616): FMX: Project2: Launch finished. Splash disappeared?
03-27 07:27:50.791: I/info(13616): FMX: Project2: BecameActive

Berlin:

03-27 07:35:04.877: I/info(14044): FMX: Project2: FormShow
03-27 07:35:04.878: I/info(14044): FMX: Project2: FormActivate
03-27 07:35:04.878: I/info(14044): FMX: Project2: Launch finished. Splash disappeared?
03-27 07:35:04.908: I/info(14044): FMX: Project2: BecameActive

i.e. although a little unexpected, no difference.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 27, 2017 1:50 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 25.03.2017 um 15:29 schrieb Stiaan Pretorius:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

Hello,

they are working on this already (I had mail contact with somebody), but
it might really help to document as much of the different findings in QP
as possible.

I was being asked whether I think that the issues present are more
general than being issues in animation area.

For instance it could be useful to create a QP report about the issue
with enabling/disabling TListBoxItems and another one about the FormShow
and FormActivate events already firing while still showing the splash
screen.

Greetings

Markus
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 27, 2017 6:07 PM   in response to: Markus Humm in response to: Markus Humm
Markus Humm wrote:

For instance it could be useful to create a QP report about the issue
with enabling/disabling TListBoxItems and another one about the FormShow
and FormActivate events already firing while still showing the splash
screen.

..and be sure to include test projects that show differences between Berlin and Tokyo. For the events issue, I could
see no difference. The events seem to come "out of order", but they're the same for both Berlin and Tokyo. I'd also be
interested as to why it would be a problem at all anyway.

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 1:21 AM   in response to: Markus Humm in response to: Markus Humm
Markus Humm wrote:
Am 25.03.2017 um 15:29 schrieb Stiaan Pretorius:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

Hello,

they are working on this already (I had mail contact with somebody), but
it might really help to document as much of the different findings in QP
as possible.

I was being asked whether I think that the issues present are more
general than being issues in animation area.

For instance it could be useful to create a QP report about the issue
with enabling/disabling TListBoxItems and another one about the FormShow
and FormActivate events already firing while still showing the splash
screen.

Greetings

Markus

Hi Markus

Sorry for my delayed response, but I had a SSD failure Sunday evening. I only today can say that I'm ready to continue testing.

I will build a test app that contain most of the elements that I see a problematic and will submit to EMBT. I will also post it here.

Regards
Stiaan
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 8:45 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 28.03.2017 um 10:21 schrieb Stiaan Pretorius:


Hi Markus

Sorry for my delayed response, but I had a SSD failure Sunday evening. I only today can say that I'm ready to continue testing.

I will build a test app that contain most of the elements that I see a problematic and will submit to EMBT. I will also post it here.

Regards
Stiaan

Don't worry! Your efforts are valued and I hope you didn't looks much
data on that SSD. I will have to try to get at the data of my brothers
HDD by exchanging the PCB of it with the one from a used HDD of the very
same type as that HDD with 1 TB capacity is currently only recognized as
having 33 MB capacity. Not keen about doing this, but I need to do it to
save the data on it.

Greetings

Markus
Bob Carson

Posts: 62
Registered: 10/8/04
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 27, 2017 3:56 PM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
My Android apps or even a new app with just a window and a button run the splash display then app exits. (No Show using DX10.2) Same app works in andoid when compiled with DX10.1. (i.e. displays app window) No problems with Windows or OSX so far with 10.2. Is there something I need to set regarding the splash display in android using DX10.2 ? I have udated the Android SDK to 25.0.4 and 25.2.5 Tools. My choices are only v24 when setting the Android SDK in Delphi Tools/Options. I also need to set Zipalign.exe, adb.exe, aapt.exe to version 17 to remove info message in SDK Edit. Anyone else run into these settings?
roca robin

Posts: 140
Registered: 9/10/06
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 27, 2017 5:24 PM   in response to: Bob Carson in response to: Bob Carson
Bob Carson wrote:
My Android apps or even a new app with just a window and a button run the splash display then app exits. (No Show using DX10.2) Same app works in andoid when compiled with DX10.1. (i.e. displays app window) No problems with Windows or OSX so far with 10.2. Is there something I need to set regarding the splash display in android using DX10.2 ? I have udated the Android SDK to 25.0.4 and 25.2.5 Tools. My choices are only v24 when setting the Android SDK in Delphi Tools/Options. I also need to set Zipalign.exe, adb.exe, aapt.exe to version 17 to remove info message in SDK Edit. Anyone else run into these settings?

Hi,

Do you have an idea of this? https://forums.embarcadero.com/thread.jspa?threadID=248350&tstart=0

I have installed Delphi Berlin Trial,

When I make a new Android project and build or run it, I get NO ERROR....

But, when I used my old or already made Delphi Android project(dpr/dproj) it always said "Exec Error Path"

Can some experts here advice what to do,

thank you
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 8:46 AM   in response to: roca robin in response to: roca robin
Am 28.03.2017 um 02:24 schrieb roca robin:
Bob Carson wrote:
My Android apps or even a new app with just a window and a button run the splash display then app exits. (No Show using DX10.2) Same app works in andoid when compiled with DX10.1. (i.e. displays app window) No problems with Windows or OSX so far with 10.2. Is there something I need to set regarding the splash display in android using DX10.2 ? I have udated the Android SDK to 25.0.4 and 25.2.5 Tools. My choices are only v24 when setting the Android SDK in Delphi Tools/Options. I also need to set Zipali
gn.exe, adb.exe, aapt.exe to version 17 to remove info message in SDK Edit. Anyone else run into these settings?

Hi,

Do you have an idea of this? https://forums.embarcadero.com/thread.jspa?threadID=248350&tstart=0

I have installed Delphi Berlin Trial,

When I make a new Android project and build or run it, I get NO ERROR....

But, when I used my old or already made Delphi Android project(dpr/dproj) it always said "Exec Error Path"

Can some experts here advice what to do,

thank you

Hello,

what happens if you create a new dpr for tha old project and then add
all the source files to that one?
M;aybe something got messed up in .dpr or .dproj

Greetings

Markus
Shanil M

Posts: 62
Registered: 12/24/04
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 3:32 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
So...

From everything I have read, is it worth it to upgrade to Tokyo? I don't want my android app to break.

Stiaan and others - are you considering downgrading to Berlin? If not, why not?

thanks
Shanil
Thiago Nassif D...

Posts: 6
Registered: 1/11/10
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 3:48 AM   in response to: Shanil M in response to: Shanil M
I have tokyo.
For me, at this moment, it´s "broken" (for Android apps)
I´ve contacted Embarcadero support, but without any answer until this moment

Shanil M wrote:
So...

From everything I have read, is it worth it to upgrade to Tokyo? I don't want my android app to break.

Stiaan and others - are you considering downgrading to Berlin? If not, why not?

thanks
Shanil
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 4:31 AM   in response to: Thiago Nassif D... in response to: Thiago Nassif D...
Thiago Nassif DAmico wrote:
I have tokyo.
For me, at this moment, it´s "broken" (for Android apps)
I´ve contacted Embarcadero support, but without any answer until this moment

Shanil M wrote:
So...

From everything I have read, is it worth it to upgrade to Tokyo? I don't want my android app to break.

Stiaan and others - are you considering downgrading to Berlin? If not, why not?

thanks
Shanil

Hi Shanil

I was forced to "downgrade" back to Berlin. We are launching a massive multiplatform app in a month's time and I cannot afford any problems at this point. Please understand that I'm not negative about Tokyo. Being a developer I understand the risk of bringing in new code. I will in the mean time interface with EMBT to get these issues sorted.

Regards
Stiaan
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 8:48 AM   in response to: Thiago Nassif D... in response to: Thiago Nassif D...
Am 28.03.2017 um 12:48 schrieb Thiago Nassif DAmico:
I have tokyo.
For me, at this moment, it´s "broken" (for Android apps)
I´ve contacted Embarcadero support, but without any answer until this moment

1. Rest assured that they're working on these problems. I just don't
know why they're not a bit more public about it and just tell users:
ok, there might be something, but we're already investigating this

2. When answering a post please put your answer below the text you're
answering to. This is the norm here as this is not e-mail. Thanks.

Greetings

Markus
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 5:07 AM   in response to: Shanil M in response to: Shanil M
On 3/28/2017 1:32 PM, Shanil M wrote:
So...

From everything I have read, is it worth it to upgrade to Tokyo? I don't want my android app to break.

Stiaan and others - are you considering downgrading to Berlin? If not, why not?

thanks
Shanil

right now not possible still this bug is not corrected:
https://quality.embarcadero.com/browse/RSP-17162?filter=14008
i hope embt will take it seriously and will make an update 1 or a
dcu/pas patch very fastly ... so just wait i m sure they will do (i hope
they will do correctly so i prefer to wait week or even month than to
see a patch badly done) !
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 5:13 AM   in response to: loki loki in response to: loki loki

right now not possible still this bug is not corrected:
https://quality.embarcadero.com/browse/RSP-17162?filter=14008
i hope embt will take it seriously and will make an update 1 or a
dcu/pas patch very fastly ... so just wait i m sure they will do (i hope
they will do correctly so i prefer to wait week or even month than to
see a patch badly done) !

ok marco answer my saying they are investigated the issue. seam to be
connected to the change of threading model. anyway they are on it so
wait and we will see ...
Dave Nottage

Posts: 1,850
Registered: 1/7/00
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 5:18 AM   in response to: loki loki in response to: loki loki
loki loki wrote:

ok marco answer my saying they are investigated the issue

Answered where?

--
Dave Nottage [MVP, TeamB]
Hints, tips and tricks at: http://www.delphiworlds.com/blog
loki loki

Posts: 787
Registered: 7/1/02
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 5:30 AM   in response to: Dave Nottage in response to: Dave Nottage
On 3/28/2017 3:18 PM, Dave Nottage (TeamB) wrote:
loki loki wrote:

ok marco answer my saying they are investigated the issue

Answered where?

http://blog.marcocantu.com/blog/2017-march-delphi-102-released-today.html
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 28, 2017 8:53 AM   in response to: loki loki in response to: loki loki
Am 28.03.2017 um 14:30 schrieb loki loki:
On 3/28/2017 3:18 PM, Dave Nottage (TeamB) wrote:
loki loki wrote:

ok marco answer my saying they are investigated the issue

Answered where?

http://blog.marcocantu.com/blog/2017-march-delphi-102-released-today.html

Good to know. He really tried to answer all the questions!

Greetings

markus
Maxibyte Maxibyte

Posts: 5
Registered: 5/18/05
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 29, 2017 10:06 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Stiaan Pretorius wrote:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

I have the same problem!!!

Help!!!
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 29, 2017 10:55 AM   in response to: Maxibyte Maxibyte in response to: Maxibyte Maxibyte
Am 29.03.2017 um 19:06 schrieb Maxibyte Maxibyte:
Stiaan Pretorius wrote:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

I have the same problem!!!

Help!!!

Hello,

do you have a demo project showing the issue somewhat clearly enough you
could share with EMBT?

I can't unless some NDA exchange is initiated and that's currently a bit
too much of a hassle.

Afaik they can see some of the issues, but not all so such a demo would
be great.

Greetings

Markus
Stiaan Pretorius

Posts: 24
Registered: 1/2/09
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 29, 2017 9:46 PM   in response to: Markus Humm in response to: Markus Humm
Markus Humm wrote:
Am 29.03.2017 um 19:06 schrieb Maxibyte Maxibyte:
Stiaan Pretorius wrote:
Hi

I have upgraded to Tokyo and ported our multi-platform Delphi app from Berlin to Tokyo. Firstly note that our Berlin app worked perfectly on all platforms.

Once I have compiled the app and started testing, I realized that our Android version has become completely unusable. (Our iOS, Windows versions seems to be running OK.)

This is my analysis so far:
1. Application lost all effects...glow effects on buttons etc.
2. TAniIndicator for example does work anymore.
3. Simple TEdit is very slow in response.
4. TListBoxes are very slow. Enabling and disabling TListBoxItems takes seconds to complete, leaving the application useless.
5. The memory consumption seems higher than the Berlin compiled version.
6. FormShow and FormActivate is called when the Android splash is still showing. I still have no idea when the for is actually showing!
7. Tab transistions is not happening at all.
8. Application crashed after a while of waiting for some TListboxItems to appear. (10 of them)

Can someone give some advise on how to start logging these issues as an urgent matter?

Much appreciated!

Regards
Stiaan Pretorius

I have the same problem!!!

Help!!!

Hello,

do you have a demo project showing the issue somewhat clearly enough you
could share with EMBT?

I can't unless some NDA exchange is initiated and that's currently a bit
too much of a hassle.

Afaik they can see some of the issues, but not all so such a demo would
be great.

Greetings

Markus

Hi Markus

I'm going to put a Tokyo demo together with very much the same components, effect etc. together for EMBT. What would be the best mechanism for this? Going through quality?

This week has been crazy, so I will try and wrap that up today.

Regards
Stiaan
Markus Humm

Posts: 5,113
Registered: 11/9/03
Re: Upgraded to Tokyo revealed that Android is very problematic  
Click to report abuse...   Click to reply to this thread Reply
  Posted: Mar 30, 2017 8:39 AM   in response to: Stiaan Pretorius in response to: Stiaan Pretorius
Am 30.03.2017 um 06:46 schrieb Stiaan Pretorius:


Hi Markus

I'm going to put a Tokyo demo together with very much the same components, effect etc. together for EMBT. What would be the best mechanism for this? Going through quality?

This week has been crazy, so I will try and wrap that up today.

Regards
Stiaan

Hello,

a good mechanism would be to ask one of the product managers per e-mail
how to submit best so that it reaches the relevant persons quickest.

QP would of couse be a legimate way.

Greetings

Markus
Legend
Helpful Answer (5 pts)
Correct Answer (10 pts)

Server Response from: ETNAJIVE02