Android Question B4XPages and SDK36

[BanditMrP]

Hi,

I have a couple of corporate apps that use B4XPages, and I just noticed that when I target SDK36 (B4A 14.0 at the moment), the orientation lock is lost.

Targeting SDK35 restores the orientation lock.

Is there something I'm missing somewhere that I need to add when targeting SDK36 to keep the orientation lock?

Any help much appreciated.

 

[Alessandro71]

check if this applies to you

Android Tutorial Thread 'Samsung One UI Orientation Warning!'

Nov 8, 2026

I am currently working on a cross platform B4XPages app using my Galaxy Tab A9+ to test and was tearing my hair out (what little I have left) because setting #SupportedOrientations: landscape was not locking the orientation. I also tried locking the orientation using the phone library ph.SetScreenOrientation(0) which was also ignored. I did try it on Bluestacks which worked as expected.

It turns out that the Samsung (not so) 'Smart' Setup decided that it should ignore the directive and set the flag for 'Landscape view for portrait apps' on for this application. Which meant that the...

• stevel05
• Replies: 3
• Forum: Tutorials & Examples

• 

 

[BanditMrP]

Thanks for the info.

Unfortunately, my app does not have that turned on in Settings->Advanced->Labs->Landscape view for portrait apps.

It is a Landscape only app - except when targeting SDK36 that doesn't seem to be enforced any more.

 

[Erel]

Does it happen on a tablet?

 

[BanditMrP]

I’ve checked and it happens on multiple apps, tablet and phone. A phone app that is locked to portrait and a tablet app that is locked to landscape. When targeting sdk36 the lock doesn’t work.

 

[Erel]

Make a test with this in the manifest editor:

AddApplicationText(
 <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
)

 

[Filippo]

Thanks for the info.

Unfortunately, my app does not have that turned on in Settings->Advanced->Labs->Landscape view for portrait apps.

It is a Landscape only app - except when targeting SDK36 that doesn't seem to be enforced any more.

On tablets running Android 16 or later, you can no longer restrict orientation; the system ignores all restrictions.

 

[BanditMrP]

Make a test with this in the manifest editor:

AddApplicationText(
 <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
)

I’ll give that a try later today - I’m with a different client at the moment. Thanks for the quick response.

 

[Erel]

On tablets running Android 16 or later, you can no longer restrict orientation; the system ignores all restrictions.

You can with this flag.

 

[Filippo]

You can with this flag.

It's too bad I didn't find out about this until today, because I've already started implementing my apps for tablets running Android 16 or higher in both orientations (portrait and landscape).
But I don't think it can do any harm.

 

[LucaMs]

But I don't think it can do any harm.

(I could be wrong, that happens to me often, lately.)

The potential "issue" is that `B4XPage_Created` might get re-executed when the orientation changes.

 

[Filippo]

The potential "issue" is that `B4XPage_Created` might get re-executed when the orientation changes.

“B4XPage_Created” isn't a problem for me because I don't use “B4XPage.”

 

[LucaMs]

“B4XPage_Created” isn't a problem for me because I don't use “B4XPage.”

1. This thread relates to B4XPages.
2. You really should create B4XPages projects

 

[BanditMrP]

Make a test with this in the manifest editor:

AddApplicationText(
 <property android:name="android.window.PROPERTY_COMPAT_ALLOW_RESTRICTED_RESIZABILITY" android:value="true" />
)

After testing - I can confirm this was an issue only on B4XPages applications, only on Tablets, and adding the code above solves the issue.

Many many thanks @Erel for the quick and accurate solution.