yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Duos] kengnatural:
In your mount printout I can see the line:

tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0

Which is strange. You allocated your internal memory in your virtual memory. If this is the case, then after every reboot your internal memory should be cleared.

Can you create a file in your internal memory and reboot the phone, after reboot see if this file exists there?

This problem is similar to the problem of [MENTION=5448941]bknightx3[/MENTION]. But he reported that after flashing the latest ROM his problem was solved.

---------- Post added at 09:54 PM ---------- Previous post was at 08:57 PM ----------

What build of ROM are you using? Compare some lines from your mount printout with mine (20160207 build):

yours: /dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
mine: /dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=writeback 0 0

yours: /dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
mine: /dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=writeback 0 0

yours: tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
yours: /dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
yours: /dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
mine: .... no such entries....

My mount output:

rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p16 /system ext4 ro,seclabel,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p17 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /data ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=writeback 0 0
/dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=writeback 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
[Samsung Galaxy S Duos] Stefan_Eberle:
OK, i´ll try - but later this day :)

I´m using the same build :confused:
[Samsung Galaxy S Duos] kengnatural:
Please provide the following infos from Settings->About phone:

CyanogenMode version

Kernel version

Build date
[Samsung Galaxy S Duos] Stefan_Eberle:
So, I tested: the file still remains after rebooting!

CM: 11-20160207-UNOFFICIAL-kylessopen

Kernel: 3.09.79-klinkone-gab0e0a6

user@archaic #1

Sun Feb 7 08:03:04 EET 2016

Date: Sun Feb 7 09:00:10 EET 2016

BTW: ATM I don´t have GApps installed, and there´s no Problem right now :) unfortunately though I can´t install any app, cause of missing PlayStore :mad:
[Samsung Galaxy S Duos] kengnatural:
Please, test if the files you write to your internal memory are there after reboot.
[Samsung Galaxy S Duos] Stefan_Eberle:
You mean to /storage/emulated/0 ? Then: yes, they ´re still there!!!
[Samsung Galaxy S Duos] kengnatural:
Yes. It is very strange as your /storage/emulated mounted to tmpfs. tmpfs is virtual memory file system. It keeps your files in the RAM+SWAP. As soon as you reboot, RAM content should be lost.
[Samsung Galaxy S Duos] Stefan_Eberle:
Hmmmm, and now???
[Samsung Galaxy S Duos] kengnatural:
I still could not understand your problem. Could you please, attach your /init.qcom.rc file here.

And /fstab.qcom.
[Samsung Galaxy S Duos] Stefan_Eberle:
here you are [MENTION=4056424]kengnatural[/MENTION]:
[Samsung Galaxy S Duos] eng4r:
As system partition is 1.2 gega Why not to repartition it to have like 700 in system and cache to be only 300 and remove hidden , then we get more 750 mega for data ?
[Samsung Galaxy S Duos] Stefan_Eberle:
So the Problem occures again! Without GApps. So there's no context with them!

Maybe i'll try another ROM this afternoon ;)
[Samsung Galaxy S Duos] kengnatural:
Your fstab and init script seems to be OK. Could you please zip and attach your /etc/init.d directory here for checking its scripts.

---------- Post added at 01:16 PM ---------- Previous post was at 01:15 PM ----------

Please also attach your /proc/partitions.
[Samsung Galaxy S Duos] Stefan_Eberle:
Here we go ;)
[Samsung Galaxy S Duos] kengnatural:
/proc/partitions is OK but your sdcard still has a second partition.

/etc/init.d is OK. No exstra scripts. Please check if your /data/local directory contains any script.

Did you take these data from the problematic ROM?
[Samsung Galaxy S Duos] Stefan_Eberle:
Yes, my card isn´t repartitioned yet, because I´ve got atm no possibility to do it, and whether with or w/o the sdcard - the problems are still present, so I thought, it´s not really important ;)

Yes, in /data/local is a directory of Titanium Backup.

Yes, the datas are from the problematic ROM.

I just installed MightyBoy ROM - and the problem still exists :( It was a clean install - even with system-wipe!
[Samsung Galaxy S Duos] kengnatural:
You installed MightyBoy ROM and nothing changed - it means that the problem is not related to the ROM.

On the other hand your /data/local directory contains some other elements, you can check if these elements contain any script which can modify the mounting options. If nothing helps you, then I would start everything from zero:

* Wipe system, data, cache, dalvik cache, android security - everything keeping only sd card.

* Flash 20160207 build.

* Remove your sdcard (don't use it for a while)

* Reboot

* Take "mount" printout and attach here.

* Attach your "/data/local" directory too.

Don't install anything else before taking needed data. No gapps, no titanium backup, nothing else. Just fresh installed CM11.
[Samsung Galaxy S Duos] Stefan_Eberle:
I did, as you said:

the mount-printout:

u0_a52@kylessopen:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p16 /system ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0/dev/block/mmcblk0p17 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /data ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
u0_a52@kylessopen:/ $

in /data/local there´s only an empty folder named "tmp"

Just in case - the df-printout:

u0_a52@kylessopen:/ $ df
Filesystem Size Used Free Blksize
/dev 322.8M 136.0K 322.7M 4096
/sys/fs/cgroup 322.8M 12.0K 322.8M 4096
/mnt/asec 322.8M 0.0K 322.8M 4096
/mnt/obb 322.8M 0.0K 322.8M 4096
/mnt/fuse 322.8M 0.0K 322.8M 4096
/system 1.2G 381.7M 799.4M 4096
/cache 492.1M 69.5M 422.6M 4096
/data 1.8G 39.5M 1.7G 4096
/efs 11.8M 4.1M 7.7M 4096
/persist 7.9M 4.0M 3.8M 4096
/mnt/shell/emulated: Permission denied
/storage/emulated 322.8M 0.0K 322.8M 4096
/storage/emulated/0 1.8G 39.5M 1.7G 4096
/storage/emulated/legacy 1.8G 39.5M 1.7G 4096
1|u0_a52@kylessopen:/ $
[Samsung Galaxy S Duos] kengnatural:
Ok. The same problem. Could you get these (last) printouts and attach them here?

tune2fs -l /dev/block/mmcblk0p16
tune2fs -l /dev/block/mmcblk0p19
tune2fs -l /dev/block/mmcblk0p11

The printouts may be large enough, so please put them into a file and attach the file here.
[Samsung Galaxy S Duos] Stefan_Eberle:
OK, give me an hour or so, i have to leave for nightshift... :(
[Samsung Galaxy S Duos] Stefan_Eberle:
They´re tiny small :)

/block/mmcblk0p16 <
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: Permission denied while trying to open /dev/block/mmcblk0p16
Couldn't find valid filesystem superblock.
1|u0_a52@kylessopen:/ $

ev/block/mmcblk0p19 <
/system/bin/sh: ttune2fs: not found
127|u0_a52@kylessopen:/ $

ev/block/mmcblk0p11 <
tune2fs 1.41.14 (22-Dec-2010)
tune2fs: Permission denied while trying to open /dev/block/mmcblk0p11
Couldn't find valid filesystem superblock.
1|u0_a52@kylessopen:/ $
[Samsung Galaxy S Duos] kengnatural:
You should run it as a root user.
[Samsung Galaxy S Duos] kengnatural:
For mmcblk0p16 there are no differences. But for mmcblk0p19 and mmcblk0p11 default mount option differs between mine and yours:

yours: Default mount options: (none)
mine: Default mount options: journal_data_writeback

Unfortunately I don't know if it can be the reason.

How about the stock ROM? Does it work normally?
[Samsung Galaxy S Duos] khalykbek:
I think he need's to do repartition by Odin
[Samsung Galaxy S Duos] Stefan_Eberle:
And how do I do that?
[Samsung Galaxy S Duos] khalykbek:
As I know you can find the file for your phone that does this repartition by using Odin.

But there is a big risk that you hard break your phone.

I'm not sure if it is good solution of your problem.

So wait until KlinkOne or kengnatural will approve it.
[Samsung Galaxy S Duos] KlinkOnE:
I don't see any need to repartition as all partitions are there and of right size.

Everything exactly like on my device.

Really weird situation...

---------- Post added at 12:20 PM ---------- Previous post was at 11:59 AM ----------

Hi

could you please remember when this first began!

Have you tried the original rc3 meanwhile?
[Samsung Galaxy S Duos] kengnatural:
What recovery are you using?

Logically file system parameters are defined during formatting which is performed when you wipe your partitions in recovery program. May be your recovery is the reason.
[Samsung Galaxy S Duos] Stefan_Eberle:
Yesterday in the late afternoon I started as kenganatural said with zero. I wiped almost everything (wiping internal storage failed) and installed 160207 build. Since then no Problem appeared.

This morning I installed microGApps and then I tested to install one app after the other. Untill now the Problem didn't appear anymore :good:

So I stay at this level and look, what will happen in the future ;)

Yes, I tried every single build!

I'm using TWRP 2.8.0.5.
[Samsung Galaxy S Duos] KlinkOnE:
2.8.0.5?

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] kengnatural:
Just to be sure whether your problem is solved or not, check the output of the "mount" command. If the following line is present, then your problem still continues:

...
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
...
[Samsung Galaxy S Duos] Stefan_Eberle:
Sorry, I didn't check it. It's 2.8.0.1 [emoji6]
[Samsung Galaxy S Duos] kengnatural:
I think he could try the build with external sdcard as a physical primary configuration, it could solve his problem if nothing else helped :)
[Samsung Galaxy S Duos] Stefan_Eberle:
The line is present :(

I actually deleted the second partition oft my sdcard!

---------- Post added at 20:23 ---------- Previous post was at 20:22 ----------

Untill now the problem didn't appear again :good:

The hope will die at last ;)
[Samsung Galaxy S Duos] kengnatural:
If this line is present then your problem has not gone, it will appear as you fill your memory. Could you attach your "df" output here?
[Samsung Galaxy S Duos] Stefan_Eberle:
u0_a52@kylessopen:/ $ df

Filesystem Size Used Free Blksize

/dev 322.8M 136.0K 322.7M 4096

/sys/fs/cgroup 322.8M 12.0K 322.8M 4096

/mnt/asec 322.8M 0.0K 322.8M 4096

/mnt/obb 322.8M 0.0K 322.8M 4096

/mnt/fuse 322.8M 0.0K 322.8M 4096

/system 1.2G 602.5M 578.6M 4096

/cache 492.1M 115.7M 376.4M 4096

/data 1.8G 696.2M 1.1G 4096

/efs 11.8M 4.1M 7.7M 4096

/persist 7.9M 4.0M 3.8M 4096

/mnt/shell/emulated: Permission denied

/mnt/media_rw/sdcard0: Permission denied

/storage/sdcard0 29.5G 22.9G 6.6G 8192

/storage/emulated 322.8M 0.0K 322.8M 4096

/storage/emulated/0 1.8G 696.2M 1.1G 4096

/storage/emulated/legacy 1.8G 696.2M 1.1G 4096

1|u0_a52@kylessopen:/ $
[Samsung Galaxy S Duos] kengnatural:
/storage/emulated/0 1.8G 696.2M 1.1G 4096
/storage/emulated/legacy 1.8G 696.2M 1.1G 4096

It is solved :)
[Samsung Galaxy S Duos] Stefan_Eberle:
I hope so!

Thank you all :good:
[Samsung Galaxy S Duos] Stefan_Eberle:
Things are getting really weird :sad:

Disc space is present

Mount and df follow:

u0_a52@kylessopen:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p16 /system ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0/dev/block/mmcblk0p17 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /data ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/fuse /mnt/shell/emulated fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
tmpfs /storage/emulated tmpfs rw,seclabel,nosuid,nodev,relatime,mode=751,gid=1028 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
/dev/fuse /storage/emulated/legacy fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0

u0_a52@kylessopen:/ $ df
Filesystem Size Used Free Blksize
/dev 322.8M 136.0K 322.7M 4096
/sys/fs/cgroup 322.8M 12.0K 322.8M 4096
/mnt/asec 322.8M 0.0K 322.8M 4096
/mnt/obb 322.8M 0.0K 322.8M 4096
/mnt/fuse 322.8M 0.0K 322.8M 4096
/system 1.2G 602.5M 578.6M 4096
/cache 492.1M 92.5M 399.6M 4096
/data 1.8G 912.7M 914.7M 4096
/efs 11.8M 4.1M 7.7M 4096
/persist 7.9M 4.0M 3.8M 4096
/mnt/shell/emulated: Permission denied
/storage/emulated 322.8M 0.0K 322.8M 4096
/mnt/media_rw/sdcard0: Permission denied
/storage/sdcard0 29.5G 22.9G 6.6G 8192
/storage/emulated/0 1.8G 912.7M 914.7M 4096
/storage/emulated/legacy 1.8G 912.7M 914.7M 4096
1|u0_a52@kylessopen:/ $
[Samsung Galaxy S Duos] kengnatural:
Do all new programs you want to install give insufficient space errors? Or only some of them?

Try the following experimental build. It uses the external sdcard as a main external memory (physica primary configuration). It means that you will have only one physical sdcard. The space allocated for your emulated internal sdcard before will be used by applications and their internal data.

Be aware, in this configuration some applications may not work correctly if unmount your sdcard in working system.

https://www.androidfilehost.com/?fid=24415232478676108

---------- Post added at 07:06 PM ---------- Previous post was at 07:03 PM ----------

Don't forget to wipe everythig again just to be clear test.

After installation please put here your "mount" and "df" output.
[Samsung Galaxy S Duos] Stefan_Eberle:
All apps give that error! The real weird thing was that yesterday I wanted to install an app with ~2MiB that was rejected due space - directly after that I installed facebookapp which isn't really small - without any error (?) Now there isn't any app without error (not even an update is possible :( )

So I'm going to try your New build and give you the infos you demanded!
[Samsung Galaxy S Duos] kengnatural:
Yesterday you said that

.

Could you please clarify this? Did you mean wiping "data" partition by recovery? What error was this?
[Samsung Galaxy S Duos] Stefan_Eberle:
There was no specific error. Only after wipe there was written "failed". A wipe of system, cache & dalvik was succesfull!

So I go now to flash your ROM. Keep your fingers crossed!

---------- Post added at 19:50 ---------- Previous post was at 19:48 ----------

BTW: can I provide mount and df as one file vor should it be 2?
[Samsung Galaxy S Duos] khalykbek:
Well, I think you better install stock ROM by Odin

And after that clean install of cm

Because you are the only one who reporting such kind of problem

If that won't help you may think of repartiotioning by using PIT file

But it may hard brick your device
[Samsung Galaxy S Duos] kengnatural:
The "failed" message wiping data partition may be a key to your problem...

Attach as one file here. If you attach it as a code section, then please, embrace it in [ hide] ... [/hide] section so it will not take huge space.
[Samsung Galaxy S Duos] Stefan_Eberle:
Here we go again ;)

The complete wipe was succesfull and so was the Installation. Here the mount/df:

u0_a52@kylessopen:/ $ mount
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,seclabel,nosuid,relatime,mode=755 0 0
devpts /dev/pts devpts rw,seclabel,relatime,mode=600 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,seclabel,relatime 0 0
selinuxfs /sys/fs/selinux selinuxfs rw,relatime 0 0
debugfs /sys/kernel/debug debugfs rw,relatime 0 0
none /sys/fs/cgroup tmpfs rw,seclabel,relatime,mode=750,gid=1000 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,seclabel,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/fuse tmpfs rw,seclabel,relatime,mode=775,gid=1000 0 0
/dev/block/mmcblk0p16 /system ext4 ro,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0/dev/block/mmcblk0p17 /cache ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p25 /data ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 0 0
/dev/block/mmcblk0p19 /efs ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/mmcblk0p11 /persist ext4 rw,seclabel,nosuid,nodev,relatime,user_xattr,barrier=1,data=ordered 0 0
/dev/block/vold/179:33 /mnt/media_rw/sdcard0 vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,relatime,uid=1023,gid=1023,fmask=0007,dmask=0007,allow_utime=0020,codepage=cp437,iocharset=iso8859-1,shortname=mixed,utf8,errors=remount-ro 0 0
/dev/fuse /storage/sdcard0 fuse rw,nosuid,nodev,relatime,user_id=1023,group_id=1023,default_permissions,allow_other 0 0
u0_a52@kylessopen:/ $
u0_a52@kylessopen:/ $ df
Filesystem Size Used Free Blksize
/dev 322.9M 136.0K 322.8M 4096
/sys/fs/cgroup 322.9M 12.0K 322.9M 4096
/mnt/asec 322.9M 0.0K 322.9M 4096
/mnt/obb 322.9M 0.0K 322.9M 4096
/mnt/fuse 322.9M 0.0K 322.9M 4096
/system 1.2G 371.1M 810.1M 4096
/cache 492.1M 69.4M 422.7M 4096
/data 1.8G 42.0M 1.7G 4096
/efs 11.8M 4.1M 7.7M 4096
/persist 7.9M 4.0M 3.8M 4096
/mnt/media_rw/sdcard0: Permission denied
/mnt/secure/asec: Permission denied
/storage/sdcard0 29.5G 23.1G 6.4,,G 8192
1|u0_a52@kylessopen:/ $

Without GApps vor anything else ;)

---------- Post added at 21:18 ---------- Previous post was at 21:17 ----------

Now lets try, if it works!
[Samsung Galaxy S Duos] kengnatural:
Good. Hope you will enjoy your phone :)
[Samsung Galaxy S Duos] kengnatural:
Dear all,

I noticed that starting from yesterday there were several downloads of the experimental build sent to [MENTION=6402761]Stefan_Eberle[/MENTION].

If you want to flash it over working system, please be informed that after flashing this way your internal (emulated) sdcard content will be hidden inside /data/media/0/ folder. You should manually move that content to the external sdcard (copy to the new place and delete from old place) or just wipe everything and perform fresh install.
[Samsung Galaxy S Duos] Stefan_Eberle:
So, after some days oft testing, I can say that the ROM works smooth as...

Thank you first for that!

Only 2 minor things I faced: I'm missing several widgets e.g. of MailDroid or BizCal. And XPosedFramework doesn't work. Installation is OK, but it doesn't take any effect! I tried gravityBox module and unbeloved hosts. Both installations gone right, but nothing happens :(

Could it be, that this is cause of the fact, that the apps are (partly) on the sdcard?
[Samsung Galaxy S Duos] kengnatural:
The changes with this version is minor in comparison with 20160207 build. If xposed worked for 20160207 it should work with this build too.

What do you mean with "apps are (partly) on the sdcard"? Do you mean that you moved some application to sdcard using Settings-Apps-On SD card feature? If it is the case try to move them back and see.
[Samsung Galaxy S Duos] Stefan_Eberle:
No, I don't use any app2sd feature. I only thought it, cause you said, that the intern and extern memory are one. If I interpreted it wrong, sorry!

Xposed worked with 0702-build (for me). I don't know, where the problem is.