[UNOFFICIAL][ROM] BETA LineageOS 16.0 for Galaxy Tab A 9.7 S-pen [SM-P550]

[retiredtab]

NOTE: There is no S-pen support. If you need S-pen, DO NOT USE THIS ROM.

I am not responsible for lost data, identity theft, lost money, security vulnerabilities, bricked devices or any other hardware or software malfunctions that comes as a result of flashing this ROM.

Try this build at your own risk. It's likely to have bugs and is EXPERIMENTAL as it is a work in progress. It boots and seems to work fine on my SM-P550, but I have only tested it for 24 hours. Problems will likley surface later?

I'm posting the rom to get more testers and help fixing the bugs.

BACKUP YOUR FILES and have a copy of your working image BEFORE trying my build.

https://androidfilehost.com/?w=files&flid=317066

What works.

1. bluetooth
2. wifi
3. brightness
4. external audio
5. GPS
6. audio through headphone jack
7. camera
8. touchscreen X-axis works properly
9. Google play store - use pico apps
10. flip flap smart cover

Note: first initial boot takes a bit longer, roughly 36 right to left circle animations or 1 minute 40 seconds without gapps. After that, it boots quicker.

Known problems.

1. TWRP X-axis touchscreen is mapped backwards.

If you want to flash using TWRP, remember the X-axis is mapped inverted. I used the latest TWRP 3.4.0.0 from

https://dl.twrp.me/gt510wifi/twrp-3.4.0-0-gt510wifi.img.tar.html

OR you can use the lineageos recovery image named s550-20200910-recovery.img. I tested it and it has the correct X-axis. Use adb sideload to push and flash the rom zip image.

adb sideload lineage-16.0-20200910-UNOFFICIAL-gt510wifi-s550-beta2.zip

2. Lineageos FM Radio app does not work.

I never use it, but I tried and it says FM operation failed. FM Radio also requires the tablet to have the LTE chipset which the S550 lacks.

Thanks/Credits

Thanks to @virsys for the SM-T550 build. The T550 is essentially the same as the P550, but without the S-pen support. I used his github repos at

https://github.com/VirsysElectron

I may fork his repo in the future. The T550 code at https://github.com/Galaxy-MSM8916 compiles without errors, but crashes at the boot logo.

Thanks to @nubianprince and @lividhen99 for ideas and suggestions on fixing the incorrect lcd density issue.

 

[retiredtab]

FAQ - I spent hundreds of hours building this rom. The least you can do is spend a few minutes reading everything before posting.

Q1) Does the build work on xyz?
A1) I have no idea. I only have the SM-P550. If you try this code on the SM-T550, the X-axis will be reversed. I may look at the code and put in a ifdef statement so that depending on the model number, it can handle the X-axis correctly so one image can possibly work on 2 tablets.

One user reported that this rom causes a boot loop on the SM-P555. So if you have this tablet and want to try this rom, just be prepared to revert your changes. According to this post by virsys

https://forum.xda-developers.com/ga...50-sm-t555-t3779257/post78327523#post78327523

"You have to use a different kernel config for the SM-T555. The versions here are compiled for the SM-T550 variant and will never work on a SM-T555 properly."

With the above, I can only assume that also applies to the P550 and P555.

Q2) Application xyz doesnt' work. Can you fix it?
A2) I only fix what I use. If you use app xyz and it doesn't work, then go back to the last rom that worked for you.

Q3) My tablet hangs or crashes with 16.0. This build is slow and buggy. Can you fix it?
A3) Go back to the last working stable rom for you. This is a work in progress and will have bugs and frequent changes.

Q4) Do you plan to update the rom?
A4) Yes as long as I have high speed Internet, I wil try to release the rom monthly to incorporate the security patches.

Q5) Do you plan to add S-pen?
A5) I don't use the S-pen, but if the code is easy to add and you can tell me where and how to add, I can try. You must provide a github repo and example code on how to add it. I will not answer any requests for S-pen support unless you can show code and repos. If it's too complex, I won't do it and since this is all open source, you are welcome to add it yourself, just like how I fixed the inverted X-axis.

Q6) Will there be a 17.1 release?
A6) Virsys' github has some 17.1 repos so I will try at some point in the future. No promises. I already built a beta SM-T350, the little brother to the T550, and it took a long time to work out all the bugs in 17.1. 16.0 should be more stable than 17.1 at this point in time.

Q7) How did you fix the inverted X-axis.
A7) For those who don't know, some of the T550 ROMs do boot and work on the P550, but without the S-pen. HOWEVER, the X-axis is reversed. You can read here on my initial testing.

https://forum.xda-developers.com/showpost.php?p=79018037&postcount=108

After some research, it wasn't that hard, but finding the right touchscreen driver and learning how the input system worked took a couple of days. Basically, you look at the kernel defconfig file and look for the CONFIG_TOUCHSCREEN setting. That will tell you what driver it's using.

kernel/samsung/msm8916/arch/arm/configs/msm8916_sec_gt510wifi_eur_defconfig

CONFIG_TOUCHSCREEN_ATMEL_MXT1664T=y

Then you look in the kernel/samsung/msm8916/drivers/input/touchscreen directory to find the correct driver.

The screen resolution of the P550 is 1024x768. For some reason, the current code thinks its 1024x1024 below. 1024x4=4096. It's numbered 0 to 4095. So the ABS_MT_POSITION_X is 4095.

[SIZE="3"]$ adb shell
gt510wifi:/ $ getevent -lp /dev/input/event1
add device 1: /dev/input/event1
  name:     "sec_touchscreen"
  events:
    KEY (0001): KEY_BACK              00fb                  00fd                  00fe                 
                BTN_TOOL_FINGER       BTN_TOUCH            
    ABS (0003): ABS_MT_SLOT           : value 0, min 0, max 9, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MAJOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_TOUCH_MINOR    : value 0, min 0, max 255, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_X     : value 0, min 0, max 4095, fuzz 0, flat 0, resolution 0
                ABS_MT_POSITION_Y     : value 0, min 0, max 4095, fuzz 0, flat 0, resolution 0
                ABS_MT_TRACKING_ID    : value 0, min 0, max 65535, fuzz 0, flat 0, resolution 0
                003e                  : value 0, min 0, max 1, fuzz 0, flat 0, resolution 0
    LED (0011): LED_MISC             
  input props:
    INPUT_PROP_DIRECT
gt510wifi:/ $[/SIZE]

The code to fix the inverted X-axis is easy. It's one line. Just 4095 minus the current x-axis position. However, if I can fix the code so it recognizes the tablet correctly as 1024x768, then 4095 changes to 3071 (768 x 4 = 3072).

[SIZE="3"]project kernel/samsung/msm8916/
diff --git a/drivers/input/touchscreen/mxt_t/mxtt.c b/drivers/input/touchscreen/mxt_t/mxtt.c
index 2e0a3fa0fa7..39e8eccabc9 100644
--- a/drivers/input/touchscreen/mxt_t/mxtt.c
+++ b/drivers/input/touchscreen/mxt_t/mxtt.c
@@ -671,7 +671,7 @@ static void mxt_report_input_data(struct mxt_data *data)
                        input_mt_report_slot_state(data->input_dev,
                                        MT_TOOL_FINGER, true);
                        input_report_abs(data->input_dev, ABS_MT_POSITION_X,
-                                       data->fingers[i].x);
+                                       4095-data->fingers[i].x);
                        input_report_abs(data->input_dev, ABS_MT_POSITION_Y,
                                        data->fingers[i].y);[/SIZE]

Update Nov 9. I found out later that if the wacom s-pen driver can be implemented reliably, the above patch is not required. That is, the wacom s-pen driver maps the x-axis correctly. Currently, I cannot make a reliable build with the 16.0 or 17.1 code without random reboots when the wacom driver is included. Even without the wacom driver, I'm having problems making a reliable 16.0 and 17.1 rom after the Sept 23 release.

 

[retiredtab]

TODO

1. Clean up the roomservice.xml so it's easier to read. Done
2. Try lineageos recovery image to see if X-axis is mapped correctly.
3. Fix huge screen problem at bootup.
4. Documentation for myself to help with possible future 17.1 and 18.0 builds. Done.
5. Look at possibility of making a P550 specific TWRP. Tried, too hard to do atm.
6. Look at possibility of adding S-pen support IF there is existing repo and working code.
7. The proper code name of the P550 is gt5note10wifi. I may change around the directory names and repos to reflect that.
8. Fork or mirror virsys repos in case they are deleted. Done.
9. Build userdebug release instead of eng release. Eng only used for testing. Done
10. Look at ifdef code to see if one rom image can work for both P550 and T550.

 

[retiredtab]

Sept 23 release
- Sept 5 security patches
- added onscreen navigation buttons

Sept 10 beta release
- initial release for testing and help fixing bugs
- CPU and GPU overclocked to 1.6Ghz and 650 respectively
- based on virsys SM-T550 github repos
- fixed X-axis inverted for P550
- incoporates Aug 5, 2020 security update. Sept 5 patches wasn't available when I built the rom.
- Sept 10 beta release will be removed once I get all the bugs fixed

These are the only changes I made to virsys repo with the roomservice.xml.

[SIZE="3"]$ repo diff

project device/samsung/gta-common/
diff --git a/lineage.mk b/lineage.mk
index e38302d..2248170 100644
--- a/lineage.mk
+++ b/lineage.mk
@@ -1,9 +1,9 @@
 # Release name
-PRODUCT_RELEASE_NAME := Samsung Galaxy Tab E
+PRODUCT_RELEASE_NAME := Samsung Galaxy Tab A

 # Boot animation
-TARGET_SCREEN_WIDTH := 800
-TARGET_SCREEN_HEIGHT := 1280
+TARGET_SCREEN_WIDTH := 768
+TARGET_SCREEN_HEIGHT := 1024

 # Inherit some common Lineage stuff.
 $(call inherit-product, vendor/lineage/config/common_full_tablet_wifionly.mk)
diff --git a/system_prop.mk b/system_prop.mk
index b06e47e..8ea92c8 100644
--- a/system_prop.mk
+++ b/system_prop.mk
@@ -1,3 +1,15 @@
+# lcd density
+PRODUCT_PROPERTY_OVERRIDES += \
+       ro.sf.lcd_density=160
+
+# Patch for google play store
+PRODUCT_PROPERTY_OVERRIDES += \
+       ro.opengles.version=196608
+
+# On screen nav keys
+PRODUCT_PROPERTY_OVERRIDES += \
+       qemu.hw.mainkeys=0
+
 # Radio
 PRODUCT_PROPERTY_OVERRIDES += \
        persist.radio.snapshot_enabled=1 \

project kernel/samsung/msm8916/
diff --git a/drivers/input/touchscreen/mxt_t/mxtt.c b/drivers/input/touchscreen/mxt_t/mxtt.c
index 2e0a3fa0fa7..39e8eccabc9 100644
--- a/drivers/input/touchscreen/mxt_t/mxtt.c
+++ b/drivers/input/touchscreen/mxt_t/mxtt.c
@@ -671,7 +671,7 @@ static void mxt_report_input_data(struct mxt_data *data)
                        input_mt_report_slot_state(data->input_dev,
                                        MT_TOOL_FINGER, true);
                        input_report_abs(data->input_dev, ABS_MT_POSITION_X,
-                                       data->fingers[i].x);
+                                       4095-data->fingers[i].x);
                        input_report_abs(data->input_dev, ABS_MT_POSITION_Y,
                                        data->fingers[i].y);
=== end repo diff ===

=== roomservice.xml ===
<?xml version="1.0" encoding="UTF-8"?>
<manifest>

	<!-- common -->
  <project groups="device" name="VirsysElectron/android_device_samsung_msm8916-common" path="device/samsung/msm8916-common" remote="github" revision="lineage-16.0" />
  <project groups="device" name="LineageOS/android_device_samsung_qcom-common" path="device/samsung/qcom-common" remote="github" revision="lineage-16.0" />

	<!--hardware -->
  <project name="LineageOS/android_hardware_samsung" path="hardware/samsung" remote="github" revision="lineage-16.0" />

	<!-- overclock kernel -->
  <project name="VirsysElectron/android_kernel_samsung_msm8916" path="kernel/samsung/msm8916" remote="github" revision="lineage-16.0-oc" />

	<!--vendor -->
  <project groups="device" name="VirsysElectron/android_vendor_samsung_msm8916-common" path="vendor/samsung/msm8916-common" remote="github" revision="lineage-17.0" />
  <project groups="device" name="VirsysElectron/android_vendor_samsung_gt510wifi" path="vendor/samsung/gt510wifi" remote="github" revision="lineage-16.0" />

	<!--qcom audio-->
  <remove-project name="LineageOS/android_hardware_qcom_audio" />
  <project groups="qcom,qcom_audio,pdk" name="Galaxy-MSM8916/android_hardware_qcom_audio" path="hardware/qcom/audio-caf/msm8916" revision="lineage-16.0-caf-8916" />

	<!--boringssl needed for camera, other dependencies -->
  <project name="LineageOS/android_external_sony_boringssl-compat" path="external/sony/boringssl-compat" remote="github" revision="lineage-15.1" />
  <project name="LineageOS/android_packages_resources_devicesettings" path="packages/resources/devicesettings" />
  <project name="Galaxy-MSM8916/android-prebuilts-gcc-linux-x86-arm-arm-eabi-7.2" path="prebuilts/gcc/linux-x86/arm/arm-eabi-7.2" remote="github" revision="master" />

	<!--virsys repo for SM-T550 -->
  <project groups="device" name="VirsysElectron/android_samsung_gta-common" path="device/samsung/gta-common" remote="github" revision="lineage-16.0" />
  <project groups="device" name="VirsysElectron/android_device_samsung_gt510wifi" path="device/samsung/gt510wifi" remote="github" revision="lineage-16.0" />

 	<!--flipflap -->
  <project name="LineageOS/android_packages_apps_FlipFlap" path="packages/apps/FlipFlap" remote="github" />

</manifest>
[/SIZE]

 

[MrRoy3]

Thanks OP, works great so far, gave a new life to my device

 

[damismtz]

installed via adb or by odin?

 

[Severongas]

OMG Thanks a lot for this OP. I do use S-Pen however my device reboots randomly and frequently while on stock rom rendering it almost unusable, I am more than willing to sacrifice the pen in favor of stability. I will test it out and provide any feedback or address bugs if any.

Once again thanks for this, P550 seemed like a forgotten device.

 

[retiredtab]

I do use S-Pen however my device reboots randomly and frequently while on stock rom rendering it almost unusable

If your tablet operated perfectly when it was brand new with no random reboots on stock rom, it could be your battery is dying if you used it heavily for almost 4 to 5 years?

When the battery degrades, it can't provide enough "juice" or amps when needed for heavy CPU tasks and this could cause it to randomly reboot. Alternatively, sometimes cleaning and reseating the battery connector might help as well?

See

https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+A+9.7++Battery+Replacement/88890

 

[Severongas]

If your tablet operated perfectly when it was brand new with no random reboots on stock rom, it could be your battery is dying if you used it heavily for almost 4 to 5 years?

When the battery degrades, it can't provide enough "juice" or amps when needed for heavy CPU tasks and this could cause it to randomly reboot. Alternatively, sometimes cleaning and reseating the battery connector might help as well?

See

https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+A+9.7++Battery+Replacement/88890

That's the thing, other than it being 3-4 years old now it was mainly used by my son to browse YouTube, not even playing. So it's use was very low.

Recalling, I did had it running on 6.0.1 stock, then updated to Fenix Rom and some time later upgraded to 7.1.1 stock using Odin, that is when this started happening.

Update on your modded Rom, it has been running flawlessly since yesterday, only issue was when after flashing GApps Pixel Launcher crashed 5-10 secs after opening app drawer, however this was later fixed after updating to latest version of all apps.

Not a single random reboot and I can finally start using it once again! Thanks a lot for your work on this.

 

[retiredtab]

now it was mainly used by my son to browse YouTube, not even playing.

If youtube is the primary use, check out youtube vanced (no ads) and microg.

With the combo above, you do NOT need to install gapps of any kind. That way, your tablet will use less memory and less software.

https://vanced.app/
https://microg.org/

For pixel launcher, you can find it at fdroid.org instead of play store.

https://f-droid.org/en/packages/amirz.rootless.nexuslauncher/

The above is how I have one tablet setup. It works fine for me, but I can't guarantee that it will meet your requirements.

 

[retiredtab]

Sept 23 build up. See post #4 for changes.

 

[CW_texashack]

Having an issue flashing

i left it running for an hour and a half after flash and it keep just sitting on the boot animation. Restarted and same outcome. I tried flashing both ways, however i can't get it to boot for some reason. I did wipe data before i flashed, could that be the issue?

 

[retiredtab]

i left it running for an hour and a half after flash and it keep just sitting on the boot animation.

If you are using twrp to flash, I suggest wipe, advanced wipe, check dalvik/art cache, data, internal storage, cache and system. Then install rom zip (both work on my P550 tablet). After install rom zip, then use twrp to wipe, format data.

If using lineageos recovery, click factory reset, choose wipe data/factory reset, then wipe cache, then wipe system. Do each wipe twice. Then adb sideload the rom.

PS. I'm using my P550 to view your message with the latest Sept 23 rom so I know it boots on mine. I test all my roms that I upload to make sure it boots on my tablet and for the functionality that I put in post #1. I never shared untested roms.

 

[CW_texashack]

Thank you, I'll try this out.
I wasn't trying to say it was your fault or anything, I'm 99.9% sure it's my fault. I just thought maybe you had an idea what may be causing it to stick for me. It's obvious it's working fine as there's plenty other replies saying it works as well.

 

[aala27]

Hey @retiredtab,

I was working on getting RR rom on this tab and managed to get the S-Pen to work in portrait mode a few months ago (In landscape mode, I believe the axes are swapped and inverted which I have not been able to fix). I have just uploaded the kernel source that I was using to get this to work, which might be of interest to you.

https://github.com/aala27/samsung_P550_Kernel.git

I have used the following defconfig files in BoardConfig.mk:

TARGET_KERNEL_VARIANT_CONFIG := p550_defconfig
TARGET_KERNEL_CONFIG := common_defconfig
TARGET_KERNEL_SELINUX_CONFIG := selinux_p550_defconfig
TARGET_KERNEL_SELINUX_LOG_CONFIG := selinux_log_defconfig

Hope this helps.

Also note I am working on getting RR 8 (Android 10) on this tab. Managed to get it to boot but I am unable to get the audio to work from the loudspeakers

 

[retiredtab]

I was working on getting RR rom on this tab and managed to get the S-Pen to work in portrait mode a few months ago (In landscape mode, I believe the axes are swapped and inverted which I have not been able to fix). I have just uploaded the kernel source that I was using to get this to work, which might be of interest to you.

Also note I am working on getting RR 8 (Android 10) on this tab. Managed to get it to boot but I am unable to get the audio to work from the loudspeakers

@aala27, thanks for your post and sharing your code. Can you post your RR s-pen rom somewhere so I can download it and test it with the s-pen. I never used it on this tablet and want to see how it works.

I will download your code and have a look. Where do you get the s-pen code?

I tried compiling virsys Android 10 code, but I get stuck at a bootloop. I have been trying for weeks to figure out the problem, but no success so far. I know he has a working build dated June 2020, but his github repo only goes to March 2020 so it might not be updated with all the necesssary fixes?

If you want help fixing the audio on your 10 build, can you upload the rom so I can look at logcats?

Thanks.

 

[retiredtab]

@aala27, I was able to build your kernel and get the same results as you. S-pen works in portrait mode, but not in landscape.

Do you know which procedure or module draws the s-pen pointer?

Using adb shell and

getevent -l | grep event3,

I can see the coordinates being reported by the s-pen. They all look correct to me. The top left hand corner is 0,0 and the bottom right hand corner is 768, 1024. So top left hand corner is always 0,0 in portrait and landscape. Bottom right is always 768, 1024 in portrait and landscape.

gt510wifi:/ $ getevent -lp /dev/input/event3
add device 1: /dev/input/event3
  name:     "sec_e-pen"
  events:
    KEY (0001): KEY_BACK              KEY_UNKNOWN           00fe                  BTN_DIGI*
                BTN_TOOL_RUBBER       BTN_TOUCH             BTN_STYLUS            KEY_ALS_TOGGLE
    ABS (0003): ABS_X                 : value 1871, min 0, max 14745, fuzz 4, flat 0, resolution 0
                ABS_Y                 : value 13381, min 0, max 19660, fuzz 4, flat 0, resolution 0
                ABS_PRESSURE          : value 0, min 0, max 2047, fuzz 0, flat 0, resolution 0
                ABS_DISTANCE          : value 6, min 0, max 1024, fuzz 0, flat 0, resolution 0
    SW  (0005): 0013*
  input props:
    <none>[/SIZE]

P550 screen resolution is 1024 / 768 = 1.333 aspect ratio. 19660/14745 = 1.333. So "sec_e-pen" has correct resolution.

PS. The git file you uploaded had link which caused the compiler to stop. You had

dt-bindings -> /home/ali/rr9/kernel/samsung/msm8916/include/dt-bindings

Luckily, it was an easy fix for me to recode the link.

 

[aala27]

@aala27, I was able to build your kernel and get the same results as you. S-pen works in portrait mode, but not in landscape.

Do you know which procedure or module draws the s-pen pointer?

Using adb shell and

getevent -l | grep event3,

I can see the coordinates being reported by the s-pen. They all look correct to me. The top left hand corner is 0,0 and the bottom right hand corner is 768, 1024. So top left hand corner is always 0,0 in portrait and landscape. Bottom right is always 768, 1024 in portrait and landscape.

P550 screen resolution is 1024 / 768 = 1.333 aspect ratio. 19660/14745 = 1.333. So "sec_e-pen" has correct resolution.

PS. The git file you uploaded had link which caused the compiler to stop. You had

dt-bindings -> /home/ali/rr9/kernel/samsung/msm8916/include/dt-bindings

Luckily, it was an easy fix for me to recode the link.

This was done a while ago, however, I do recall finding out that the S-Pen uses wacom drivers. The driver is found in /drivers/input/touchscreen/wacom.

I have uploaded the RR Pie rom at the link below:

https://drive.google.com/file/d/1zQuvVOr_8eq0Q3vU-UagURcU-8t6sBUO/view?usp=sharing

I'll upload the RR 10 rom soon.

Thanks for the error. I have now corrected that.

 

[aala27]

@aala27, thanks for your post and sharing your code. Can you post your RR s-pen rom somewhere so I can download it and test it with the s-pen. I never used it on this tablet and want to see how it works.

I will download your code and have a look. Where do you get the s-pen code?

I tried compiling virsys Android 10 code, but I get stuck at a bootloop. I have been trying for weeks to figure out the problem, but no success so far. I know he has a working build dated June 2020, but his github repo only goes to March 2020 so it might not be updated with all the necesssary fixes?

If you want help fixing the audio on your 10 build, can you upload the rom so I can look at logcats?

Thanks.

Hey mate,

See link to RR 10 rom. It seems as through everything works ok except for the audio coming from the loudspeakers. Audio from headphones, bluetooth etc works fine. This was the same issue I had building the RR Pie rom but I used Virsys' fix and it worked for that rom. Not sure what the issue is now.

Let me know if you have any idea.

https://drive.google.com/file/d/1hns5Gf0ietXca1bZK5MwK6l7n4DsBoUZ/view?usp=sharing

Cheers,

 

[retiredtab]

See link to RR 10 rom. It seems as through everything works ok except for the audio coming from the loudspeakers.

It says I need a google account to get RR 10. I was able to download RR 9 without one. Can you please change the permissions so I can download 10 without a login? Once I download 10, I will see if I can help you by looking at the logcat.

BTW, I downloaded RR 9 and get the same results as you. The spen only works in portrait mode. 90, 180 and 270 have incorrect mouse pointer display.

Also, when I asked about which module or procedure, I wasn't asking about the driver (Wacom). As soon as I saw your P550_defconfig, I knew it was the wacom driver. What I'm asking is what module or program actually draws the mouse pointer that shows up the lcd.

When I look at getevent -l | grep event3, I think the wacom driver is properly reporting the X and Y coordinates where the pen is hovering or touching with 0,0 at top left corner and 768, 1024 at bottom right corner. I want to see the code where it actually takes the X and Y coordinates from the wacom driver and use them to draw the mouse pointer on the lcd.

Clearly, something in the code doesn't take into account of the screen rotation.

PS. I did a make clean so I can build an eng build so I can get some logcat messages. It will take 8 hours to compile. I'm also looking at the wacom driver code to see where I can put in some print statements with respect to the screen orientation.