yashsingh1/xdaforums huggingface dataset:
[Galaxy Note GT-N7000 Android Development] madsun:
We only have Bauner to thank for the wonderful ROM. I am very indebted to him for extending the life of my phone beyond my wildest expectations. The Note GT-N7000 was a device well ahead of its time, atleast a couple of years ahead of its time.

I want to change my device(this is my primary device) but havent come across a device that has shaken the segment(like the Note did when it was released).....Hopefully the Note 6 will likely be my next device. I am also considering the HP Elite X3, the Samsung A9 Pro, The Huawei Mate 8(though the Kirin is underpowered) but none of these devices have been released in India yet.

I am looking for a Dual Nano-SIM device with a separate MicroSD slot, 4G LTE with VoLTE on both SIMs', with just a Full HD(or higher) AMOLED screen with all the combination of sensors which might be a rightful replacement for the Note that I am using.

Thanks once again Bauner. Will you be surprising us with Android N?

Regards, Madsun
[Galaxy Note GT-N7000 Android Development] bauner:
repo forall -c git reset --hard HEAD
repo sync

should reset everything to the default version

You tried to mix cm and du parts which will not work...
[Galaxy Note GT-N7000 Android Development] daneal2u:
Thanks for answering. But what I did was remove frameworks/base and pacakges/APPS/settings using rm -rf and then did a report sync. And these errors didn't show up :laugh:.

---------- Post added at 01:26 AM ---------- Previous post was at 01:17 AM ----------

I was sooo close to getting my build done and then this popped out of nowhere:silly:

frameworks/opt/telephony/../../../device/samsung/galaxys2-common/ril/telephony/java/com/android/internal/telephony/SamsungExynos4RIL.java:289: error: cannot find symbol
case RIL_REQUEST_SIM_GET_ATR: ret = responseString(p); break;
^
symbol: variable RIL_REQUEST_SIM_GET_ATR
location: class SamsungExynos4RIL
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
1 error
build/core/java.mk:394: recipe for target '/home/daneal2u/DU/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes-full-debug.jar' failed
make: *** [/home/daneal2u/DU/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes-full-debug.jar] Error 41
make: *** Waiting for unfinished jobs....
[Galaxy Note GT-N7000 Android Development] bauner:
maybe you miss this

https://github.com/CyanogenMod/andr...mmit/35b9bdf0cca220768c23edf7d81137cb01f4dde0
[Galaxy Note GT-N7000 Android Development] daneal2u:
This is what i get while trying to cherry pick.

daneal2u@daneal2u:~/DU$ cd frameworks/opt/telephony
daneal2u@daneal2u:~/DU/frameworks/opt/telephony$ git fetch https://github.com/CyanogenMod/android_frameworks_opt_telephony.git
remote: Counting objects: 8039, done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 8039 (delta 1663), reused 1663 (delta 1663), pack-reused 6374
Receiving objects: 100% (8039/8039), 2.82 MiB | 453.00 KiB/s, done.
Resolving deltas: 100% (3316/3316), completed with 216 local objects.
From https://github.com/CyanogenMod/android_frameworks_opt_telephony
* branch HEAD -> FETCH_HEAD
daneal2u@daneal2u:~/DU/frameworks/opt/telephony$ git cherry-pick 35b9bdf0cca220768c23edf7d81137cb01f4dde0
fatal: bad object 35b9bdf0cca220768c23edf7d81137cb01f4dde0
[Galaxy Note GT-N7000 Android Development] bauner:
try

git fetch https://github.com/CyanogenMod/android_frameworks_opt_telephony.git cm-13.0
git cherry-pick 35b9bdf0cca220768c23edf7d81137cb01f4dde0

and then resolve the conflicts if there any...

or port the changes yourself
[Galaxy Note GT-N7000 Android Development] tamaraxxx:
[MENTION=799465]bauner[/MENTION]

Got a new reboot yesterday. Phone was shut down at nigh and was only recharging.

Log is attached below.
[Galaxy Note GT-N7000 Android Development] daneal2u:
Errors just keep popping up :( Im just about to give up hope on DU.

target Executable: blkid (/home/daneal2u/DU/out/target/product/n7000/obj/EXECUTABLES/blkid_intermediates/LINKED/blkid)
frameworks/opt/telephony/src/java/com/android/internal/telephony/BaseCommands.java:904: error: method does not override or implement a method from a supertype
@Override
^
frameworks/opt/telephony/src/java/com/android/internal/telephony/RIL.java:2655: error: cannot find symbol
case RIL_REQUEST_SIM_GET_ATR: ret = responseString(p); break;
^
symbol: variable RIL_REQUEST_SIM_GET_ATR
location: class RIL
frameworks/opt/telephony/src/java/com/android/internal/telephony/RIL.java:4824: error: cannot find symbol
RILRequest rr = RILRequest.obtain(RIL_REQUEST_SIM_GET_ATR, response);
^
symbol: variable RIL_REQUEST_SIM_GET_ATR
location: class RIL
frameworks/opt/telephony/../../../device/samsung/galaxys2-common/ril/telephony/java/com/android/internal/telephony/SamsungExynos4RIL.java:289: error: cannot find symbol
case RIL_REQUEST_SIM_GET_ATR: ret = responseString(p); break;
^
symbol: variable RIL_REQUEST_SIM_GET_ATR
location: class SamsungExynos4RIL
frameworks/opt/telephony/src/java/com/android/internal/telephony/CommandException.java:108: error: cannot find symbol
case RILConstants.INVALID_PARAMETER:
^
symbol: variable INVALID_PARAMETER
location: interface RILConstants
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
5 errors
build/core/java.mk:394: recipe for target '/home/daneal2u/DU/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes-full-debug.jar' failed
make: *** [/home/daneal2u/DU/out/target/common/obj/JAVA_LIBRARIES/telephony-common_intermediates/classes-full-debug.jar] Error 41
[Galaxy Note GT-N7000 Android Development] bauner:
As the phone entered the charging mode the reason is not to see in the log

it seems that you need to port some more commits from cm
[Galaxy Note GT-N7000 Android Development] daneal2u:
Im done with DU, just too complicated for a beginner like me. One last question: Im trying to build rr rom for i9082 but it has no cm13 device tree, only aosp 6.0 device tree. What do i need to do to the aosp (device & kernel) tree to make it compatible with rr? https://github.com/pawitp/android_device_samsung_i9082/tree/aosp-6.0
[Galaxy Note GT-N7000 Android Development] JerwinSayat:
Hi everyone. Why is my "sdcard0" changed its name to "^M" I dont know what happened. Do I need to worry?
[Galaxy Note GT-N7000 Android Development] bauner:
https://wiki.cyanogenmod.org/w/Doc:_porting_intro

I have done a (quick) overview and it seems that there are also the cm makefiles included. So it should be working directly or with only a few smaller adjustments
[Galaxy Note GT-N7000 Android Development] bauner:
I currently don't know why this will happen in some rare cases.

But it should also work without problems.

I had this also 1 time on the external sdcard and some days later (maybe because of some rebbots I did???) it changed back to normal.

Maybe also formatting your sdcard again as vfat in the recovery (or a filesystem check if you use the twrp recovery) will fix it.
[Galaxy Note GT-N7000 Android Development] JerwinSayat:
It is in ext4 format. Will I lost my data if I format it in recovery as vfat?
[Galaxy Note GT-N7000 Android Development] al.islam.333:
[IMG="is there any update to my boot loader???"]https://goo.gl/photos/V3uzzdE8rvf1ovkE8[/IMG]

https://goo.gl/photos/V3uzzdE8rvf1ovkE8
[Galaxy Note GT-N7000 Android Development] D@rekills4:
I don't see anything as "Bootloader" in my Settings.

It's probably showing up because of one of your mods.
[Galaxy Note GT-N7000 Android Development] bauner:
Formatting the sdcard will delete the data on it. So you should backup the data on it to your pc or to the other sdcard
[Galaxy Note GT-N7000 Android Development] daneal2u:
[MENTION=799465]bauner[/MENTION] will u add fsync to ur kernel as on forest kernel? This seems to greatly decrease app install times which is needed by our slow device and I haven't come thru any problems/disadvantages of using it.
[Galaxy Note GT-N7000 Android Development] bauner:
No because the risk of data loss after an crash or if you remove the battery would be very high with disabled fsync.
[Galaxy Note GT-N7000 Android Development] daneal2u:
OK no problem:o
[Galaxy Note GT-N7000 Android Development] daneal2u:
[MENTION=799465]bauner[/MENTION] i fixed the telephony issue with du. Now this one shows up. My build was about to be done maybe 5 more mins

Traceback (most recent call last):
File "./device/samsung/galaxys2-common/releasetools/galaxys2_ota_from_target_files", line 46, in <module>
main(sys.argv[1:])
File "/home/daneal2u/DU/build/tools/releasetools/ota_from_target_files", line 1737, in main
raise RuntimeError("can't determine the cache partition size")
RuntimeError: can't determine the cache partition size
build/core/Makefile:1626: recipe for target '/home/daneal2u/DU/out/target/product/n7000/du_n7000-ota-eng.daneal2u.zip' failed
make: *** [/home/daneal2u/DU/out/target/product/n7000/du_n7000-ota-eng.daneal2u.zip] Error 1

After commenting out those lines from ota_from_target_files, i get this

Improving vertex order...
Reticulating splines...
Traceback (most recent call last):
File "./device/samsung/galaxys2-common/releasetools/galaxys2_ota_from_target_files", line 46, in <module>
main(sys.argv[1:])
File "/home/daneal2u/DU/build/tools/releasetools/ota_from_target_files", line 1741, in main
WriteFullOTAPackage(input_zip, output_zip)
File "/home/daneal2u/DU/build/tools/releasetools/ota_from_target_files", line 684, in WriteFullOTAPackage
system_diff = common.BlockDifference("system", system_tgt, src=None)
File "/home/daneal2u/DU/build/tools/releasetools/common.py", line 1199, in __init__
b.Compute(self.path)
File "/home/daneal2u/DU/build/tools/releasetools/blockimgdiff.py", line 300, in Compute
self.WriteTransfers(prefix)
File "/home/daneal2u/DU/build/tools/releasetools/blockimgdiff.py", line 494, in WriteTransfers
max_allowed = cache_size * stash_threshold
TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'
build/core/Makefile:1626: recipe for target '/home/daneal2u/DU/out/target/product/n7000/du_n7000-ota-eng.daneal2u.zip' failed
make: *** [/home/daneal2u/DU/out/target/product/n7000/du_n7000-ota-eng.daneal2u.zip] Error 1
[Galaxy Note GT-N7000 Android Development] arnab:
Looks like you guys are using old unofficial twrp which was isorec compatible....I released official twrp for i9100. I am willing to release official twrp for n7000 too but the OP needs to do some tests. Also the new official recovery is cm-12.1 compatible. It happened bcoz of newer spolicies in the smdk4412 kernel...which renedered the older sepolicies useless.

Also

http://review.cyanogenmod.org/#/c/140097/

I came up with this commit with invaluable help from lanchon...It now directly generates lzo compatible recovery.img which the OP will understand.

https://github.com/TeamWin/android_...mmit/6b78333a99a48d8c82cb38b068dd892adbed4cbf

This is the original twrp tree made by me. Iam very sure this will work in n7000.

Anyways anybody who still has cm-12.1 tree can contact me..if u guys want official twrp for n7000...Il have to make very minor changes.

Also I gone thru the entire twrp commit in bauner's github...Its ditto same as mine with the exception that he changed the mountpoint names in boardconfig and twrp.fstab. So iam pretty sure I can ask Ethan Yonker(Lead twrp dev) to test for n7000.

This is my original commit for dirtyunicorns

https://github.com/kularny/android_...mmit/2399aff511a35588882904a2cdf59755559d4931

Anyways Il chalk out a tree for you guys within a day and Il ask EthanYonker to test it...If all goes perfect u guys will have a f2fs compatible, cm-12.1 compatible official twrp within a few days. Thanks.
[Galaxy Note GT-N7000 Android Development] bauner:
It looks like that you get the 2nd error because of the now missing cache_size
[Galaxy Note GT-N7000 Android Development] bauner:
I have a working 12.1 device tree for the n7000.

Do I understand you correct? If the twrp 3.0.2 will be built with cm12.1 it will work for cm12.1 and cm13 (also as isorec?)?

If yes I can build and test it.

I also got problems if I included the twrp 3.0.2 to the kernel ramdisk in cm13.

The ramdisk was to big and then my kernel refused to load modules with the error

section x reloc x sym 'xxxx': relocation 28 out of range (0xxxxxx -> 0xxxxxxx)

http://lkml.iu.edu/hypermail/linux/kernel/1101.1/00604.html
[Galaxy Note GT-N7000 Android Development] ishak isha:
brother.......will it stable........can ...this rom applicable for honor holly......

thankhs in advance ..awaiting for reply
[Galaxy Note GT-N7000 Android Development] arnab:
Yes we are building against cm-12.1 for the official twrp....u dnt need the main ramdisk...the ramdisk-recovery.cpio is needed... Earlier we had a boot.img and a recovery.img which was a clone of boot.img...so in that commit in gerrit we changed that...earlier the recovery.img consisted of the zimage+ramdisk...but now we only passed the recover_uncompresses_ramdisk and then lzop -9 it directly...the result is we get a direct recovery.img which is lzop compressed.

I also built earlier in M tree which rendered the L unusable... Its bcoz of the newer M sepolicies which the older cm12.1 kernel cant read... So ethan built twrp3 in cm12.1 tree and now its compatible with both.

So in short only yhe the ramdisk-recovery.cpio is needee... But now the whole process has been automated... U can just grab the resultant recovery.img and flash it via heimdall... Or directly image flash it via the recovery itself on the recovery partition.

My official twrp thread for i9100

http://xdaforums.com/galaxy-s2/development-derivatives/recovery-twrp-3-0-0-0-t3330457

Also plz provide a basic cm12.1 tree which is devoid of any modifications and which will directly work with the official tree.

Il add the twrp flags stuff myself and will make a few minor adjustments. Thanks.
[Galaxy Note GT-N7000 Android Development] :
Don't quote the entire post.

No, this is strictly for the Note 1.
[Galaxy Note GT-N7000 Android Development] afifwm:
how to fix random reboot :(
[Galaxy Note GT-N7000 Android Development] bauner:
Will it be a full reboot (starting on the n7000 logo) or a soft reboot (starting with the nightowl bootanimation)

If it is a fill reboot please post the file /proc/last_kmsg after your device is up again
[Galaxy Note GT-N7000 Android Development] bauner:
I have now built a working isorec twrp 3.0.2 for cm12.1 and cm13 with the stock cm12.1 source and uploaded the device tree here

https://github.com/bauner/cm-android_device_samsung_n7000/tree/twrp3-cm12.1

https://github.com/bauner/cm-android_device_samsung_galaxys2-common/tree/twrp3-cm12.1

It is working with the following 2 problems:

I had to lzop the recovery ramdisk myself

and

PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/ramdisk/twrp.fstab:recovery/root/etc/twrp.fstab

did not work for some reasons in cm12.1.

So I used this as workaround

https://github.com/bauner/cm-androi...mmit/32896e4ddd0bf62275dbae618d0ef6cf1d8a30bb

https://github.com/bauner/cm-androi...mmit/bcf0381a339c43e7b906f09eb9774241b91e6de2
[Galaxy Note GT-N7000 Android Development] arnab:
The flag BOARD_CUSTOM_GRAPHICS is no longer applicable in minui in bootable/recovery....Earlier 5.1 versions of recovery needed that..but from 6.0 minui.c has changed to minui.cpp and also this flag is no longer supported in android.mk of minui.
[Galaxy Note GT-N7000 Android Development] bauner:
ok then it would be possible to build it without modifications in galaxys2-common if I could find the reason why

PRODUCT_COPY_FILES += \
$(LOCAL_PATH)/ramdisk/twrp.fstab:recovery/root/etc/twrp.fstab

in n7000.mk will not copy the twrp.fstab in cm12.1 for me.

In cm13 it is working...
[Galaxy Note GT-N7000 Android Development] quini2k:
Hi!

I helped a friend install this ROM on his n7000 and, after one day of use, he's found no major problem.

Thanks in his name! ;)

Quini OPO
[Galaxy Note GT-N7000 Android Development] arnab:
TARGET_RECOVERY_FSTAB is not supported by twrp...It needs the way I did.

See here.

Under *RECOVERY.FSTAB*

See the way its done. By the way, have you checked the root/etc folder in your local out folder after compilation ???

---------- Post added at 07:30 PM ---------- Previous post was at 07:13 PM ----------

Hey u have selected the android-6.0 branch of twrp in cm-12.1 right ???
[Galaxy Note GT-N7000 Android Development] bauner:
I know but I don't know why the twrp.fstab will not get copied in cm12.1.

In cm13 it will get copied.

I have no twrp.fstab in the complete out folder.

If I use

TARGET_RECOVERY_FSTAB := device/samsung/n7000/ramdisk/twrp.fstab

I will have the file twrp.fstab as out/target/product/n7000/recovery/root/etc/recovery.fstab

and twrp will use it...

I use the omni 6.0 twrp branch
[Galaxy Note GT-N7000 Android Development] arnab:
But u cant disable TARGET_RECOVERY_FSTAB in official s2_common which will be used. Also placing this in device_n7000 will create a placebo.
[Galaxy Note GT-N7000 Android Development] bauner:
I also did not find out the reason... But with

TARGET_RECOVERY_FSTAB := device/samsung/n7000/ramdisk/twrp.fstabI get out/target/product/n7000/recovery/root/etc/recovery.fstab

and if I remove it I don't get the file (I have tested it a few times).

also if I leave the galaxys2-common default

TARGET_RECOVERY_FSTAB := device/samsung/galaxys2-common/rootdir/fstab.smdk4210

I get the fstab.smdk4210 as out/target/product/n7000/recovery/root/etc/recovery.fstab

Update:

I'm coming closer to find out what is wrong but I don't have more time today.

In the next days I will fix it
[Galaxy Note GT-N7000 Android Development] arnab:
Thats really strange. the local_path macro is also defined properly and ndk picks it up. U aren't using ccache stuff right??? Do a make clobber...Really strange.
[Galaxy Note GT-N7000 Android Development] shantia_73:
I didn't read previous pages, so forgive me if it was answered before.

First thanks again [MENTION=799465]bauner[/MENTION] for you great works.

I have a problem with camera. This is the first time I'm using CM13, so i don't know if older betas had this problem or not.

When i open Camera, going to front camera and shoot, a message comes up that says: "Can't connect to the camera".

So, is there any solution for that?
[Galaxy Note GT-N7000 Android Development] bauner:
You are right. Making pictures with the front camera is not working in beta5 and maybe in older versions too.

As workaround you could use the google camera https://play.google.com/store/apps/details?id=com.google.android.GoogleCamera
[Galaxy Note GT-N7000 Android Development] daneal2u:
[MENTION=799465]bauner[/MENTION] [MENTION=414800]arnab[/MENTION] While compiling DU for n7000 im constantly getting this error. I've downloaded the full source again but no use. Can anyone of u point out a solution. My local github, if it helps, https://github.com/daneal2u.

(using device-specific extensions from target_files)
--- can't determine the cache partition size ---
loaded device-specific extensions from /tmp/targetfiles-Tc1vFg/META/releasetools.py
using system.img from target-files
Total of 218112 4096-byte output blocks in 1250 input chunks.
Generating digraph...
Finding vertex sequence...
Reversing backward edges...
0/0 dependencies (0.00%) were violated; 0 source blocks stashed.
Improving vertex order...
Reticulating splines...
Traceback (most recent call last):
File "./device/samsung/galaxys2-common/releasetools/galaxys2_ota_from_target_files", line 46, in <module>
main(sys.argv[1:])
File "/home/daneal2u/DU/build/tools/releasetools/ota_from_target_files", line 1741, in main
WriteFullOTAPackage(input_zip, output_zip)
File "/home/daneal2u/DU/build/tools/releasetools/ota_from_target_files", line 684, in WriteFullOTAPackage
system_diff = common.BlockDifference("system", system_tgt, src=None)
File "/home/daneal2u/DU/build/tools/releasetools/common.py", line 1199, in __init__
b.Compute(self.path)
File "/home/daneal2u/DU/build/tools/releasetools/blockimgdiff.py", line 300, in Compute
self.WriteTransfers(prefix)
File "/home/daneal2u/DU/build/tools/releasetools/blockimgdiff.py", line 494, in WriteTransfers
max_allowed = cache_size * stash_threshold
TypeError: unsupported operand type(s) for *: 'NoneType' and 'float'
build/core/Makefile:1626: recipe for target '/home/daneal2u/DU/out/target/product/n70
[Galaxy Note GT-N7000 Android Development] arnab:
OMG which branch did u repo sync and which branch u cloned...U cloned m branch where u should clone m-caf

git clone -b m-caf https://github.com/DirtyUnicorns/android_build.git

Also run this while u download the whole source

repo init -u git://github.com/DirtyUnicorns/android_manifest.git -b m-caf

Like i said the source really helps you.
[Galaxy Note GT-N7000 Android Development] daneal2u:
SO U MEAN i delete my local source and download it all over again. anyways thanks for the help.:good:
[Galaxy Note GT-N7000 Android Development] bauner:
But the custom graphics.c is part of the default cm12.1 galaxys2-common device tree and without the changes I get errors in minui.old

bootable/recovery/minui.old/../../../device/samsung/galaxys2-common/recovery/graphics.c:208:5: error: conflicting types for 'gr_text'
int gr_text(int x, int y, const char *s, int bold)
^
In file included from bootable/recovery/minui.old/../../../device/samsung/galaxys2-common/recovery/graphics.c:39:0:
bootable/recovery/minui.old/minui.h:43:5: note: previous declaration of 'gr_text' was here
int gr_text(int x, int y, const char *s, ...);
^
bootable/recovery/minui.old/../../../device/samsung/galaxys2-common/recovery/graphics.c: In function 'gr_text':
bootable/recovery/minui.old/../../../device/samsung/galaxys2-common/recovery/graphics.c:208:46: warning: unused parameter 'bold' [-Wunused-parameter]
int gr_text(int x, int y, const char *s, int bold)

I have now updated

https://github.com/bauner/cm-android_device_samsung_n7000/tree/twrp3-cm12.1

and

https://github.com/bauner/cm-android_device_samsung_galaxys2-common/tree/twrp3-cm12.1

So now the only thing to find out is why the created ramdisk-recovery.img (with the lzop commit https://github.com/bauner/cm-androi...mmit/ebb4043dc19aba06ab19b68d66fd2c47bb4acbc5) is not a valid lzo file
[Galaxy Note GT-N7000 Android Development] arnab:
huh do u have lzop installed??? if yes run

lzop -dc recovery.img > recovery

You will get the ramdisk-recovery.cpio with recovery name

---------- Post added at 01:52 AM ---------- Previous post was at 01:51 AM ----------

Yup.

---------- Post added at 01:55 AM ---------- Previous post was at 01:52 AM ----------

[MENTION=799465]bauner[/MENTION] You should only take the recovery.img k.

---------- Post added at 01:58 AM ---------- Previous post was at 01:55 AM ----------

Why did u add this ???

$(LOCAL_PATH)/ramdisk/twrp.fstab:root/etc/twrp.fstab
[Galaxy Note GT-N7000 Android Development] bauner:
:(:crying: The recovery.img is working fine. I did an mistake and builded the bootimage istead of the recoveryimage

About $(LOCAL_PATH)/ramdisk/twrp.fstab:root/etc/twrp.fstab

I wrote in my last post

I don't find out why so I also left the

$(LOCAL_PATH)/ramdisk/twrp.fstab:recovery/root/etc/twrp.fstab

which does nothing for me
[Galaxy Note GT-N7000 Android Development] arnab:
But if u copy it to root/etc... It means /etc... It won't do anything... It has to be in the recovery so that the recovery bundles that.
[Galaxy Note GT-N7000 Android Development] bauner:
I also don't know what is going on here...

If I copy it to root/etc/twrp.fstab I will get it also in recovery/root/etc/twrp.fstab

If I copy it to recovery/root/etc/twrp.fstab (which should be the correct way and which works if I build in cm13 but not in cm12.1) I will get no twrp.fstab in the complete out/... folder

So I have left both to ensure that it will be on the right place in all conditions

Maybe could you try to build it in your cm12.1 tree if you will get also the same?
[Galaxy Note GT-N7000 Android Development] arnab:
I dnt have cm12.1 tree