D DT1111 Member Licensed User Longtime User Oct 13, 2015 #1 Hi Erel I have managed to compile my program developed in older B4A with the latest B4A 5.2 without any problem. That is really good. Does that mean the app is now is going to run OK under Android 5.0 and beyond. Or is there something else I need to do like in the manifest etc. I just want to make sure. Plus the designer has a message that says an update is recommended in order to run more efficient and I can't remember what the update is.
Hi Erel I have managed to compile my program developed in older B4A with the latest B4A 5.2 without any problem. That is really good. Does that mean the app is now is going to run OK under Android 5.0 and beyond. Or is there something else I need to do like in the manifest etc. I just want to make sure. Plus the designer has a message that says an update is recommended in order to run more efficient and I can't remember what the update is.
S sorex Expert Licensed User Longtime User Oct 13, 2015 #2 that would be a .NET update (4.5.2 or something?) Upvote 0
Erel B4X founder Staff member Licensed User Longtime User Oct 13, 2015 #3 DT1111 said: Or is there something else I need to do like in the manifest etc. I just want to make sure. Click to expand... Go over this short tutorial: https://www.b4x.com/android/forum/threads/45967/#content You can find the link to .Net 4.5.2 here: https://www.b4x.com/b4a.html Upvote 0
DT1111 said: Or is there something else I need to do like in the manifest etc. I just want to make sure. Click to expand... Go over this short tutorial: https://www.b4x.com/android/forum/threads/45967/#content You can find the link to .Net 4.5.2 here: https://www.b4x.com/b4a.html
D DT1111 Member Licensed User Longtime User Oct 14, 2015 #4 Thanks. If incorporating the line below in the manifest makes the app Android L compliant, then that is easy enough. But my only gripe is, it turns background of most controls into grey. I have preference for the old look ie white background for textboxes, dropdown boxes, list etc. Is there something that I can do to preserve the old look and still make the app Lollipop compliant. Code: SetApplicationAttribute(android:theme, "@android:style/Theme.Holo.Light") I also notice that the app runs a lot slower especially when reading large data from a file when I use Code: <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Prior to that I was using just. What could be the cause? Code: <uses-sdk android:minSdkVersion="4" /> Upvote 0
Thanks. If incorporating the line below in the manifest makes the app Android L compliant, then that is easy enough. But my only gripe is, it turns background of most controls into grey. I have preference for the old look ie white background for textboxes, dropdown boxes, list etc. Is there something that I can do to preserve the old look and still make the app Lollipop compliant. Code: SetApplicationAttribute(android:theme, "@android:style/Theme.Holo.Light") I also notice that the app runs a lot slower especially when reading large data from a file when I use Code: <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Prior to that I was using just. What could be the cause? Code: <uses-sdk android:minSdkVersion="4" />
S sorex Expert Licensed User Longtime User Oct 14, 2015 #5 I didn't like the look on new tablets either and I added this to my manifest to correct most of it. android:theme="@android:style/Theme" Upvote 0
I didn't like the look on new tablets either and I added this to my manifest to correct most of it. android:theme="@android:style/Theme"
Erel B4X founder Staff member Licensed User Longtime User Oct 14, 2015 #6 DT1111 said: I also notice that the app runs a lot slower especially when reading large data from a file when I use Click to expand... The theme doesn't have any effect on the performance. Click on Ctrl + P to clean the project. It will force the debugger to make a full deployment and it will be faster. Upvote 0
DT1111 said: I also notice that the app runs a lot slower especially when reading large data from a file when I use Click to expand... The theme doesn't have any effect on the performance. Click on Ctrl + P to clean the project. It will force the debugger to make a full deployment and it will be faster.
D DT1111 Member Licensed User Longtime User Oct 14, 2015 #7 Thanks Sorex and Erel. I have tried as suggested and it definitely brought back the old look. Great but does it still make it Lollipop friendly? sorex said: android:theme="@android:style/Theme" Click to expand... Erel I did Ctrl+P and used the following. It is still slow. DT1111 said: <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Click to expand... Upvote 0
Thanks Sorex and Erel. I have tried as suggested and it definitely brought back the old look. Great but does it still make it Lollipop friendly? sorex said: android:theme="@android:style/Theme" Click to expand... Erel I did Ctrl+P and used the following. It is still slow. DT1111 said: <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Click to expand...
Erel B4X founder Staff member Licensed User Longtime User Oct 14, 2015 #8 So it is slow for other reasons. The theme used doesn't effect the performance. Make sure to test performance in release mode. Android is backwards compatible so it should work with Android 5+ as well. Upvote 0
So it is slow for other reasons. The theme used doesn't effect the performance. Make sure to test performance in release mode. Android is backwards compatible so it should work with Android 5+ as well.
D DT1111 Member Licensed User Longtime User Oct 14, 2015 #9 Hi Erel I have tested the performance in Release mode (previously was tested in Release Obfuscator mode) <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Click to expand... with and without theme and it is also slow. Erel said: Android is backwards compatible so it should work with Android 5+ as well. Click to expand... If I understand your statement, android:theme="@android:style/Theme" will enable the app to work in Android 5+. Is that correct? Upvote 0
Hi Erel I have tested the performance in Release mode (previously was tested in Release Obfuscator mode) <uses-sdk android:minSdkVersion="4" android:targetSdkVersion="14"/> Click to expand... with and without theme and it is also slow. Erel said: Android is backwards compatible so it should work with Android 5+ as well. Click to expand... If I understand your statement, android:theme="@android:style/Theme" will enable the app to work in Android 5+. Is that correct?
Erel B4X founder Staff member Licensed User Longtime User Oct 15, 2015 #10 As I said the performance is not related to the theme. If you want to further discuss the performance then you should start a new thread and explain what your app is doing and which part is slow. DT1111 said: If I understand your statement, android:theme="@android:style/Theme" will enable the app to work in Android 5+. Is that correct? Click to expand... Yes. Though it is safer to use Android 4 theme. Upvote 0
As I said the performance is not related to the theme. If you want to further discuss the performance then you should start a new thread and explain what your app is doing and which part is slow. DT1111 said: If I understand your statement, android:theme="@android:style/Theme" will enable the app to work in Android 5+. Is that correct? Click to expand... Yes. Though it is safer to use Android 4 theme.
D DT1111 Member Licensed User Longtime User Nov 2, 2015 #11 Would the following cause an issue in Android 5+ Code: #Region Activity Attributes #FullScreen: True #IncludeTitle: False #End Region Upvote 0
Would the following cause an issue in Android 5+ Code: #Region Activity Attributes #FullScreen: True #IncludeTitle: False #End Region