yashsingh1/xdaforums huggingface dataset:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] coalee:
Hello guy

I am a noob here. Last weekend, I ordered a Oneplus 3T. The device should be arriving soon. My background is I own Nexus5 and I really love it. However, after been using it for 3 years. I decided to buy a new phone. Google Pixel Plus is a great phone but it too pricey for me. So, I bought Oneplus 3T instead. I have read a lot of post on this forum and other guides how to flash custom ROM. As I understand, from a new unbox phone, the process to flash is.

1)	turn on the phone, skip the first time setup then go to setting to enable Developer Option and enable USB debugging, OEM unlocking and enable Advance Reboot.

2)	Goto recovery mode and flash OxygenOS Open Beta 3 then reboot to the system

3)	Replete step 1 again then reboot to fastboot mode

4)	‘fastboot oem unlock’ to unlock bootloader then boot to recovery and wipe all data then boot to system

5)	replete step 1 again then boot into fastboot mode

6)	flash TWRP recovery, version twrp-3.1.0-1-oneplus3t, then turn off the phone

7)	turn on the phone and get into recovery mode, swipe right to allow system modification.

8)	Flash no-verity-opt-encrypt.zip then go to wipe(format) data, system and cache

9)	Flash LineageOS

10)	Flash Google Apps v. 20170120.zip

11)	Reboot

I hope I got the step right? Can someone kindly check and comment on the steps above please? Thanks in advance. :D
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Just Passing By:
No. You're off with your steps many are unnecessary.

Here's what I do:

1. Boot phone

2. Go through setup (just skip through it. You'll lose everything pretty soon)

3. Settings > Developer Options (you'll have to activate it from About phone) > OEM unlocking and Advanced restart (people are always like do USB debugging. I don't. It's never affected me and I've gone through this process many times, so do it if you want, but you don't have to)

4. Go to recovery

5. Update to whatever OOS version you want (I recommend 3.5.4)

6. Reboot

7. After you get back to home screen, reboot to bootloader

8. "fastboot oem unlock"

9. Select yes to allow unlocking

10. Phone will reboot to the recovery screen (IMPORTANT MAKE SURE YOUR PHONE REBOOTS ALL THE WAY TO THE RECOVERY SCREEN! You may screw this up but as it's rebooting, I recommend putting your phone on a table and letting it do its thing because you may mess with your phone if you don't and be more confused later)

11. Auto wipe from recovery

12. Reboot phone

13. Go through setup process once again (skip through if you want)

14. Settings > developer tools > advanced reboot

15. Reboot to fastboot

16. Go here and follow from step seven to the end

17. Once you finish rebooting (which I recommend you do), reboot back into TWRP, wipe and flash whatever you need.

I may have left stuff out. I'm doing this from memory. :silly:
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
See, thank you, that's the kind of reply I was expecting.

---------- Post added at 06:25 AM ---------- Previous post was at 06:22 AM ----------

I don't quite remember how I did my unlocking step by step, but the tutorial on OnePlus' forum is what I followed, and had no troubles throughout.

https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.475142/
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
No. Stick to OP. Tomsetup twrp use https://xdaforums.com/oneplus-3/one...recovery-official-twrp-oneplus-3-3t-t3543391; and use the twrp from this thread.

After taking a nandroid flash 4.1.0 (!) firmware from OP and wipe dalvik, system data and cache.

Flash latest rom and have fun!

los and my rom are open source. If the general, non-technical description from #3 does not match the details you want to know, you can easily diff yourself. You find the diffs attached - additionally I cherry-pick one commit and revert another (this is also open source; you find it in my local_manifest git, which is mentioned in #1):

#temp fix for ogg/vorbis
pushd hardware/qcom/audio-caf/msm8996
git fetch https://review.lineageos.org/LineageOS/android_hardware_qcom_audio refs/changes/64/163564/3 && git cherry-pick FETCH_HEAD
popd

#stop sim settings from crashing
pushd packages/services/Telephony
git revert --no-edit 3a782aa
popd

If you want to know the differences on technical level you have to learn - at least - git (the cli command - not github!), diff and patch, and some basic skills in reading c, c++ and java. Knowing gnu make is also an advantage!

The other dudes answering were right, when stating it's all in the first few postings: a general description without technical details for all, who don't want to dig in the technical mud - and all information to tell the differences on a technical level.

I hope this answers your question.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
It's important to follow OP! You missed wiping system...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Just Passing By:
I basically encompassed all that in step 17. All my steps were listed from a completely new phone straight out of a package to a working phone with TWRP. Even though I know he wants to flash your ROM most likely, I left it a bit ambiguous in the last step so that he can make his own choices on what to flash and wipe in terms of ROMs. Since I assume he's not a newbie in the Android scene, I assume that he knows how to clean wipe before flashing a new ROM.

Tl;dr: Basically, step 17 is when you get to flashing ROMs and I left it ambiguous which is why I didn't tell him to wipe system.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
I am on latest twrp 3.1. with ext4 everything and have no problems, dirty flashed and clean flashed many times no issues ?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
3.1.0-0 has many issues. 3.1.0-1 seems to be better. But the 3.0.4-1 I recommend is well tested and working for this rom. So I would like to stay with my recommendation till 3.1.0-x has proved to be working as well. Thanx formyour feedback!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Update

build 20170328

Changelog

Updated to latest LaOS sources

Since [MENTION=4405529]nvertigo67[/MENTION] is busy for the time being, he asked me to build and upload new ROM versions every few days. So here we go.

ROM: lineage-14.1-20170328-UNOFFICIAL-mad-murdock-oneplus3t.zip

MD5: ba122f74f9fb532a77c16c11be0955a8

Mirror: posting #2

Happy flashing!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I suppose dirty flashing works fine?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Yes. As usual. Same build method, same result. I build my own ROMs for quiet some time.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
.repo/local_manifest/oneplus/oneplus3t.xml is there and it's readable. That should work.

What does "repo list|grep oneplus" say?

Have you callad any command (but the curl command - btw, this command is changed, update local_manifest) with leading sudo? If so: "chown -R t-shock.t-shock ."

What does "ls -la $(which repo)" say?

You can also try using the repo-command of the laos repo instead of that from your $PATH: ".repo/repo/repo sync device/oneplus/oneplus3t"
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
The repo list|grep oneplus gives me no results

t-shock@t-shock:~/LOS/cm14$ repo list|grep oneplus
t-shock@t-shock:~/LOS/cm14$ repo list|grep oneplus
t-shock@t-shock:~/LOS/cm14$ chown -R t-shock.t-shock
chown: missing operand after ‘t-shock.t-shock’
Try 'chown --help' for more information.
t-shock@t-shock:~/LOS/cm14$ ls -la $
ls: cannot access '$': No such file or directory
t-shock@t-shock:~/LOS/cm14$ ls -la $cm14
total 144
drwxrwxr-x 31 t-shock t-shock 4096 Ιαν 31 19:05 .
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 16:58 ..
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 18:39 abi
drwxrwxr-x 4 t-shock t-shock 4096 Ιαν 31 18:39 android
lrwxrwxrwx 1 t-shock t-shock 19 Ιαν 31 18:39 Android.bp -> build/soong/root.bp
drwxrwxr-x 21 t-shock t-shock 4096 Ιαν 31 18:39 art
drwxrwxr-x 12 t-shock t-shock 4096 Ιαν 31 18:39 bionic
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 18:39 bootable
lrwxrwxrwx 1 t-shock t-shock 26 Ιαν 31 18:39 bootstrap.bash -> build/soong/bootstrap.bash
-rw-rw-r-- 1 t-shock t-shock 963 Ιαν 31 19:05 breakfast.log
drwxrwxr-x 10 t-shock t-shock 4096 Ιαν 31 19:40 build
drwxrwxr-x 12 t-shock t-shock 4096 Ιαν 31 18:39 cts
drwxrwxr-x 10 t-shock t-shock 4096 Ιαν 31 18:39 dalvik
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 18:39 developers
drwxrwxr-x 21 t-shock t-shock 4096 Ιαν 31 18:39 development
drwxrwxr-x 8 t-shock t-shock 4096 Ιαν 31 19:29 device
drwxrwxr-x 283 t-shock t-shock 12288 Ιαν 31 18:43 external
drwxrwxr-x 17 t-shock t-shock 4096 Ιαν 31 18:44 frameworks
drwxrwxr-x 15 t-shock t-shock 4096 Ιαν 31 18:44 hardware
drwxrwxr-x 18 t-shock t-shock 4096 Ιαν 31 18:44 libcore
drwxrwxr-x 5 t-shock t-shock 4096 Ιαν 31 18:44 libnativehelper
-r--r--r-- 1 t-shock t-shock 87 Ιαν 31 18:39 Makefile
-rw-rw-r-- 1 t-shock t-shock 1008 Ιαν 31 19:05 make.log
lrwxrwxrwx 1 t-shock t-shock 18 Ιαν 31 17:01 my-build -> my_tmp/my_build.sh
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 17:00 my_tmp
drwxrwxr-x 8 t-shock t-shock 4096 Ιαν 31 18:44 ndk
drwxrwxr-x 4 t-shock t-shock 4096 Ιαν 31 20:09 out
drwxrwxr-x 10 t-shock t-shock 4096 Ιαν 31 18:45 packages
drwxrwxr-x 6 t-shock t-shock 4096 Ιαν 31 18:45 pdk
drwxrwxr-x 7 t-shock t-shock 4096 Ιαν 31 18:45 platform_testing
drwxrwxr-x 21 t-shock t-shock 4096 Ιαν 31 18:48 prebuilts
drwxrwxr-x 9 t-shock t-shock 4096 Ιαν 31 19:05 .repo
drwxrwxr-x 25 t-shock t-shock 4096 Ιαν 31 18:48 sdk
drwxrwxr-x 23 t-shock t-shock 4096 Ιαν 31 18:48 system
drwxrwxr-x 3 t-shock t-shock 4096 Ιαν 31 18:48 toolchain
drwxrwxr-x 4 t-shock t-shock 4096 Ιαν 31 18:49 tools
drwxrwxr-x 6 t-shock t-shock 4096 Ιαν 31 18:49 vendor

t-shock@t-shock:~/LOS/cm14$ .repo/repo/repo sync device/oneplus/oneplus3t
error: project device/oneplus/oneplus3t not found
t-shock@t-shock:~/LOS/cm14$
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mumapizza:
Coming from oos 4.0.2 wifi performance is definatley worse
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Stick to the commands. "ls -la $(which repo)" is not "ls -la $", nor "ls -la $cm14"; "chown -R t-shock.t-shock ." is not "chown -R t-shock.t-shock"; look at the output of the commands - output is there for a reason:

chown: missing operand after ‘t-shock.t-shock’
Try 'chown --help' for more information.

How many error messages have you skiped during preparatio?

I suggest starting from scratch, stop if there is an error, and don't continue to the next command, until you have solved the issue. I had a reason not to make the commands in the README a script, they needed to be observed and action is required if they fail.

The README is marked as beta. Perhaps, there's something wrong or different (regarding linux environment i.e.), but we will never know, if we don't look at error messages...
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] t-shock:
Ok then

Thanks a lot

But during the repo sync (and until then) I had not issue. Everything was after it
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
[MENTION=4405529]nvertigo67[/MENTION] [MENTION=3044422]mad-murdock[/MENTION]

Nice job guys! Very well done! Quick question, regarding this rom...

Has the issue with the "Mobile Active Radio" bug been fixed in this build? When I got the phone I upgraded immediately to stock 4.0.2 and at first I loved everything about it, but after a few days of using the phone I became susceptible to this bug and sadly had to downgrade to 3.5.4

I use Xposed with 3.5.4 because there is a fix for this bug and so right now my system is working very well, but I'm running a bunch of Xposed modules to help out with the battery drain and the app hibernation. Ideally, I'd love to go back to 4.0.2 and use this rom, but I'm just concerned about getting this bug. Since Xposed is not yet working on Nougat, That's why I'm on MM right now.

With regards to the sRGB issue, I know you fixed the issue in the boot.img, but is this now part of the original download, or is it still an additional step to flash the fix? If it is included, could you update the third post to mention that it has been resolved? :)

Also I was going to say if it's not part of the image, couldn't you just write a simple shell script that would get executed after the rom flashes to make the adjustments you posted in post 53? https://xdaforums.com/showpost.php?p=70799426&postcount=53

Just one more thing, is the dm-verity issue patched in this rom?

Thanks in advance, and once again huge THANK YOU to you guys and everyone involved in this project! Keep up the great work!!!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
like throughput or like latency? measured how? connected to which kind of access point? nac or bgn or something very different?

give us info to work here.

---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------

can you link or otherwise explain what you mean by this?

sRGB will be switchable in options in next build.

dm-verity issue? you mean this? https://xdaforums.com/oneplus-3/how-to/fix-easy-method-removing-dm-verity-t3544339

I never understood why people are so upset about this warning in the first place. they already accepted the unlock warning. but well, yes, its just two simple fastboot commands to get rid of it.

not a rom issue though. also wouldnt be surprised if in a future bootloader update you cannot disable it anymore.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] m0d hipp¥:
[MENTION=3044422]mad-murdock[/MENTION],

Regarding the Mobile Active Radio bug - the best source of info I can provide regarding this bug/fix, is found here - http://repo.xposed.info/module/com.pyler.mobileradioactivefix

You will also find the link to the original thread the user posted on these forums.

Regarding the dm-verity, yes you're right. It's not a big deal really. More of just an annoyance. Let's hope though that next bootloader will remain "developer friendly" enough to still allow suppression of the message. At least on the OnePlus phones :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] knpk13:
It might actually be more secure to not have those bootloader unlocked and DM verity warnings. It's basically announcing (to potential thieves) that your device is insecure and giving them terms to Google; I'm not sure what the point is.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Mad Medik:
Is anyone having difficulty down loading the update? The download won't start for me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] cmattern:
Tethering issues with AT&T

I'm running the latest build and boot.img and have discovered that if I boot with my AT&T SIM card out I can access the hotspot settings, configure the SSID, set the encryption and password but as soon as I insert my SIM the section in setting is grayed out and will not become available again until I reboot WITHOUT the SIM card. Same SIM card with LineageOS 14.1 on my Nexus 6p work fine. Additionally I've used my daughter's T-Mobile SIM in the 3t and it works fine. The only combination that fails is the AT&T SIM in the 3t.

AT&T+6p=OK

T-Mobile+iPhone 5c=OK

T-Mobile+3t=OK

AT&T+3t=FAILURE

I've capture logs from both devices and about to go log diving but figured I'd ask if anyone had seen this or had any suggestions of what to look for specifically in the logs. My plan at this point is to scroll to the insertion time and then just read line by line so any clues would be better than this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] goosebickel:
You dont need that anymore, those changes are included in latest download.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
You are right. Sustained data rate on 5Ghz ac was about 8 -9 MB/s on 4.0.2 - on this 14.1 build it's only about 5 - 6 MB/s. (On a free channel with no traffic but the file transfer).

Perhaps that's due to the wifi's region code. I'm in Europe/Germany, my asus router is configured for Europe, but this rom is configured for "world regulatory domain", what is something like the smallest common amount of channels and features. On stock wifi region seems to be set according lanuage setting, cm up to 13 has a wifi region setting in wifi advanced setting (and I'm sure it's coming one day to 14.1, roo).

For the moment you can set it manually: with a root wnabled browser go to /system/etc/wifi/WCNSS_qcom_cfg.ini, line 227 and following. You can also try playing with indoor/outdoor flag.

Since wifi is otherwise stable and laos wifi country settings will be there one day, this is no peiority for me, YMMV.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
Then the thief is asked to enter a 10+ digit password and gives up in vein. That's why it's important to have encryption running.

About DM verity, it's required due to Google specifications. Search for the docs on official Android documentation.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
This bug is still around? I remember running into this on cm-12.1 on bacon - never expirienced this again since then.

On this rom I awesome battery life on standby (slightly better then stock - though screen on seems to be slightly higher then on stock), so I think/hope mobile active radio bug is no topic for us. I'm surprised, you had that one on stock.

If you try that hard to missunserstand, I think I can't do something about it... ;) In #1 I clearly state, that the 20170131 rom hasmall hotfixes build in, and you don't need to flash a boot.img. In #3 I'm talking about the workaround (manually set srgb mode). The post I referenced has still the reference to boot.img, but if you look at the dates... ;)

Anyway: the next update will havemthe srgb mode as color profile in LiveDisplay, and then I consider the issue fixed, and then I'llmremove it from #3.

No. I prefer to spend my time on getting thisnto settings - see above.

No. I shipped the first two versions of this rom with 4.0.2 firmware, which's bootloader is throwing the message (does no harm). From the next build on rom will come without firmware. If you want to get rid of this message, use 3.5.4 bootloader (only bootloader; not modem and radio). If your question aims on saftynet, remember this rom is prerooted.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] mad-murdock:
No need to go bug hunting. It's a feature. The SIM card - or to be more specific the network - can indeed tell the operating system to disable tethering. Depending on your contract. Afaik not many networks use that feature, but yours does.

I am not sure if we should bypass this, since it is indeed a feature.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] myfrom:
Sorry for a noob question but if I'm coming from other Lineage OS based ROM, can I dirty flash or full wipe?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Look at 6p's apn settings and compare to 3t's; setup a new apn with the data from 6p. If that helps, I'll put the new at&t apn config in.

This posting is send from my tab utilizing 3t's 5GHz hotspot (vodafone.de).
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
General rule of thumb: try it, if any issues show up, before reporting them: clean flash and see, if they persists. [MENTION=3044422]mad-murdock[/MENTION] reported battery drain after dirty flashing over [MENTION=7896746]koenkk[/MENTION]'s builds.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Google Assistant seems to be missing from nvertigo's latest build? Can anyone confirm? I swear I could access it a few builds prior.

(Downloading mad-murdock's build, and latest GApps now, but I doubt that's gonna solve anything)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Jaizu:
Didn't check by myself, but make sure you have Google App and gapps installed.

If you still without that, remove data and cache from google app and play services and then open google app.

If you sitll without having that, add this to your build.prop

ro.opa.eligible_device=true
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Clearing cache and data worked, thank you!
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
Okay so, now after clearing Google app's and Play services' data & cache, I can't seem to be able to turn on location services. It pops up two messages, the second one so quickly, I can't even react to the first one (see attached video).

Any suggestions to fix it?

https://youtu.be/bM3nrpN0Zb4

EDIT1: Okay, so, after mindlessly tapping around in the Google settings, I went to "Location history", then "Manage activities", which force turned on "Location", and now I can toggle it too without giving me any errors.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] coalee:
Hi, i just want to check with you guy. Can i flash 4.1.0 firmware (from op) over 3T china model? Does it going to have effect on LTE band?

Cheers..
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I have A3010 aswell, works fine for me.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Gapps suckz.

[MENTION=535343]all[/MENTION]: What do you think about this thesis: Since google is trying to make gapps more and more proprietary in a way, that open source projects can't use them any more without droping elemantary parts of the open source android builds, we should drop support for gapps all together and use microg.

Personal note: whenever I read gapps in a posting I have no wish at all to finish reading... It's so annoying that this proprietary bull**** is not compatible to aosp. Google finally found a way to say android is open source, but not usable with gapps. This is - in deed - the opposite of open source! I would really love to get rid of this.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Lada333:
I understand that having GApps being.. well.. like this is just another problem you have to deal with, I have always been using 'nano' package, but I don't want to go even further below that, the "Okay Google" hotword comes in handy for me usually.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] :
Bluetooth crashes on OP3T when trying to add more devices

Already posted in Q&A section

Hi,

I wanted to post this here too as the problem I have is very specifiv to this ROM. Sorry for the double post.

Problem comes with all versions after the version of 16/03 which was my initial install version. The ones after I just dirty flashed first but the problem persisted. It was shortly gone after I cleaned the BT system app cache but came back on the next reboot.

So I decided to go for a full wipe and clean flash the latest LineageOS version for the OnePlus 3T from this thread here.

After I restored my apps I activated Bluetooth on the device and flawlessly connected my Smartwatch, a Gear S2. All good, all fine, all working.

AFTER that, when entering Settings => Bluetooth on the OP3T, there are 2 possible scenarios:

1) No other Bluetooth devices are around and emitting, the search stops after a few seconds saying that "no other BT devices are detected" ... makes sense.

2) There are other Bluetooth devices around and emitting, and based on my experience only one device is sufficient. The search goes on and on and on, after a while the screen freezes, and then the phone warm resets.

I was able to reproduce this inside my car when I tried to connect to the car audio system and also with my Bluetooth headset. Devices turned off => scenario 1, devices turned on and ready to connect => scenario 2.

Any idea here?
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] Primokorn:
Honestly I only flash custom ROMs that supports signature spoofing/microG project. Grass is greener on the open source (free/libre actually) side! Open source just means business for Google.

Please help me to put your unofficial builds on this list :)
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] coalee:
For update ROM to the new version, dirty flash. Do I have to wipe cache, Dalvik cache and system before I flash the new version? Thanks.
[OnePlus 3T ROMs, Kernels, Recoveries, & Other Deve] npeersab:
no