yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S Duos] kengnatural:
Could you please, give more information about the problem?

As I understand after flashing the latest build the "same problem" exists for you.

What was your previous build which was working for you?

---------- Post added at 06:14 PM ---------- Previous post was at 05:36 PM ----------

[MENTION=5448941]bknightx3[/MENTION],

I've read your posts about internal storage problem in other thread which you post in December. Unfortunately, you stopped giving additional info. This way it is not possible to provide any fix, because it is not known what to fix? The ROM or your phone.
[Samsung Galaxy S Duos] bknightx3:
When I access my internal storage the internal storage is empty.

My previous build was working is 20151127.
[Samsung Galaxy S Duos] kengnatural:
So your phone boots and works. Could you, please, provide the following info:

* Open the Terminal Emulator

* type the following command:

mount

* note the result

* type the following command:

df

* note the result

* put the noted results here so we can see how the partitions mounted.
[Samsung Galaxy S Duos] Stefan_Eberle:
Hi, I faced a bug (?) again ;)

I installed your latest build today (clean install), afterwards I installed some apps and now every new installation is aborted with

Available space is ~610 MiB :(

What can I do???
[Samsung Galaxy S Duos] kengnatural:
It's interesting. Was it a fresh install or you just flashed over old build?
[Samsung Galaxy S Duos] Stefan_Eberle:
I did a factory reset before and after install dalvik/Cache-wipe.
[Samsung Galaxy S Duos] kengnatural:
Could you please, open the terminal emulator, type the following command and send me the result:

df
[Samsung Galaxy S Duos] Stefan_Eberle:
u0_a59@kylessopen:/ $ df
Filesystem Size Used Free Blksize
/dev 311.5M 136.0K 311.4M 4096
/sys/fs/cgroup 311.5M 0.0K 311.5M 4096
/sys/fs/cgroup/memory: Permission denied
/mnt/asec 311.5M 0.0K 311.5M 4096
/mnt/obb 311.5M 0.0K 311.5M 4096
/mnt/fuse 311.5M 0.0K 311.5M 4096
/system 1.2G 547.9M 633.2M 4096
/cache 492.1M 102.4M 389.7M 4096
/data 1.8G 1.2G 586.0M 4096
/data/sdext2 3.7G 59.3M 3.6G 1024
/efs 11.8M 4.1M 7.7M 4096
/persist 7.9M 4.0M 3.8M 4096
/hidden 49.2M 27.9M 21.3M 4096
/mnt/shell/emulated: Permission denied
/storage/emulated 311.5M 0.0K 311.5M 4096
/mnt/media_rw/sdcard0: Permission denied
/storage/sdcard0 25.6G 21.6G 4.0G 8192
/storage/emulated/0 1.8G 1.2G 586.0M 4096
/storage/emulated/legacy 1.8G 1.2G 586.0M 4096
1|u0_a59@kylessopen:/$
[Samsung Galaxy S Duos] KlinkOnE:
I think its the hidden partition for some reason. I'll take it out of the fstab. I think no one uses it me too. If anyone wants it an init.d script will do the job on boot.

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] kengnatural:
Thanks. Could you please send me the result of "mount" command too?
[Samsung Galaxy S Duos] balindam bajpai:
[MENTION=4056424]kengnatural[/MENTION]

are u going to try to compile a new custom rom or a new cm built

and btw do u intend to build a omni rom

was just curious as u are referring to omni too much [MENTION=5484648]KlinkOnE[/MENTION]

have u given a thought in releasing any other kernel which would fix the performance issue that was

-small games 1mb~2mb run at a slow pace and that they lag but kinda run in slow motion type

thanks
[Samsung Galaxy S Duos] Stefan_Eberle:
u0_a59@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
/sys/fs/cgroup/memory cgroup rw,relatime,memory 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/vold/179:34
/data/sdext2 ext4 rw,seclabel,relatime,user_xattr,barrier=1,data=ordered 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/mmcblk0p22 /hidden ext4 rw,seclabel,nosuid,nodev,noatime,user_xattr,barrier=1,journal_async_commit,data=ordered,noauto_da_alloc 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_a59@kylessopen:/ $
[Samsung Galaxy S Duos] kengnatural:
If you mean another version of CM (12, etc), I'd like to do so but, unfortunately at this moment I don't have enough knowledge and experience to make it. I'm learning with the help of experienced XDA members such as [MENTION=5484648]KlinkOnE[/MENTION]. As I don't have any device which can run omni rom it is not possible for me to test it.

About slowness, personally I feel that graphic operations seems to be slow in comparison with stock ROM. For fixing such kind of things there is need for enough experience and spare time :)

---------- Post added at 08:52 PM ---------- Previous post was at 08:49 PM ----------

I applied the patch for fixing xpose issue mentioned bu you and trying to build a new ROM. Would you like me to remove the hidden partition from fstab in this build?
[Samsung Galaxy S Duos] Ashraf Iraqian:


i am tried to send file for my friend but i am shocked because my device rebooted again :D on latest version 2016/02/05

and now i will flash the bluetooth fix.zip file again maybe it will fix it :)

thank you for your work guys and you both tired with our device

but we need final build of th rom without any problem please ..like soft reboots or xposed installer or facebook app videos.

good luck

regards
[Samsung Galaxy S Duos] GiannisSma:
The bluetooth fix and theme uninstall fix is included to the 20160502 version?
[Samsung Galaxy S Duos] kengnatural:
Hi Ashraf,

I understand your disappointment.

You've just reported a new bug: "reboot during sending file through bluetooth".

Bluetooth_fix.zip will not help, it is already included into new build and it only fixed the issue "reboot when bluetooth is on". These are differend errors.

A new build with xposed patch will be issued soon.

Personally I think that these bugs will never be finished, there is need for more people involved in this. [MENTION=4925018]m4jonez[/MENTION] and [MENTION=5484648]KlinkOnE[/MENTION] have already made huge job making CM11 working in this unsupported by the vendor, slow device. If more people join them then the ROM will become stable faster.
[Samsung Galaxy S Duos] KlinkOnE:
Yes maybe remove it for the moment. Doesnt hurt.

Gesendet von meinem GT-P3110

---------- Post added at 09:09 PM ---------- Previous post was at 08:51 PM ----------

Yeah i know. I have no time atm. It frustrates me too.

I'll take care of this next days.

Nothing else other than cm has dualsim support as far as I know.

So no omni.

Gesendet von meinem GT-P3110
[Samsung Galaxy S Duos] kengnatural:
[MENTION=6402761]Stefan_Eberle[/MENTION]

I compared the mount result. There are some differences with mine.

And there is also mounted partition to /data/sdext2 directory. You told that wiped data/cache. Did you wipe system partition too, before flashing this ROM? May be there are some scripts in /etc/init.d? I assume that you did not twick your system after flashing the ROM.

This error does not happens on my phone.

Can you perform this test?

* wipe your system partition (no need for data partition)

* flash this rom

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

* reboot system

See if the error happens again. If the error does not happen try to repartition your sdcard, I mean remove the second partition and then use your sdcard.
[Samsung Galaxy S Duos] Saikat218:
here is the xposed solution

http://xdaforums.com/showpost.php?p=64063168&postcount=62 use this link and it works for me.
[Samsung Galaxy S Duos] kengnatural:
Ok. The same reason as in previous bluetooth errors, but now with other service. The crash does not happen if you turn the bluetooth through the Settings menu before sending a file...

Fix will be in the next build.

Thank you for your report.
[Samsung Galaxy S Duos] balindam bajpai:
so does that mean u dont have gts-7562 with u at the moment?
[MENTION=4056424]kengnatural[/MENTION] i think klinkone can easily guide u in compiling cm12 as the reason why he ist making cm12 is because he doesnt have enough hard disk memory which i think i would be having.

so maybe if u both can work side by side together it would be a huge boon for our device.
[MENTION=5484648]KlinkOnE[/MENTION] maybe we can go for slim or carbon?

thanks
[Samsung Galaxy S Duos] kengnatural:
Sorry, I thought that omni is for another type of device. I have S7562 .

Please, look for [MENTION=5484648]KlinkOnE[/MENTION]'s earlier posts about cm12, there are also other reasons than hard disk space.

My personal opinion: by now we have got working cm11 with some bugs. It would be correct and easier to try to fix these bugs and make the rom perfect for all S7562 users. Imagine that after a lot of time spending on cm12 ROM porting part of code from cm11 to it, a new ROM starts working on S7562 with the same bugs + new bugs... And instead of fixing them that time we are switching to cm13 :)

And the same thoughts for other ROMs.
[Samsung Galaxy S Duos] _AE_:
I can help in fixxing the BUGS

---------- Post added at 11:40 AM ---------- Previous post was at 11:40 AM ----------

Check this out http://xdaforums.com/s7562/development/cm11-12-rom-s7562-t3308611
[Samsung Galaxy S Duos] balindam bajpai:
[MENTION=4056424]kengnatural[/MENTION]

so are u trying to say that u along with some others are trying to build cm13?

---------- Post added at 06:56 AM ---------- Previous post was at 06:53 AM ----------

[MENTION=4056424]kengnatural[/MENTION]

so are u trying to say that u along with some others are trying to build cm13?
[Samsung Galaxy S Duos] KlinkOnE:
No

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] kengnatural:
Oh, no. I wanted to imagine a situation when cm12 is working with bugs and users want developers to fix them, but instead of fixing cm12 developers are trying to build cm13.
[Samsung Galaxy S Duos] _AE_:
Wait for the new fiX
[Samsung Galaxy S Duos] balindam bajpai:
[MENTION=4056424]kengnatural[/MENTION]

sorry i misunderstood

my mistake

btw best of luck for your work
[Samsung Galaxy S Duos] KlinkOnE:
Enough now! You've learned nothing! Edit your post remove the zip or you will be reported!

Same for your other thread!

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] bknightx3:
Sorry for late reply.

here is the logs in terminal

u0_a76@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=writeback,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

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

u0_a76@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 454.8M 726.3M 4096

/cache 492.1M 94.6M 397.6M 4096

/data 1.8G 1.1G 690.2M 4096

/efs 11.8M 4.1M 7.7M 4096

/persist 7.9M 4.0M 3.8M 4096

/storage/emulated 322.8M 0.0K 322.8M 4096

/mnt/media_rw/sdcard0: Permission denied

/storage/sdcard0 14.8G 2.0G 12.8G 32768

1|u0_a76@kylessopen:/ $
[Samsung Galaxy S Duos] kher paandiyan:
Soft Reebot while Clearing Data

Hi [MENTION=5484648]KlinkOnE[/MENTION] and [MENTION=4056424]kengnatural[/MENTION] my device face soft reboot while clearing Data of any installed apps. I'm using 20160105 build. Please do check this issue. :good:
[Samsung Galaxy S Duos] kengnatural:
From your mount:

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

From your df:

/storage/emulated 322.8M 0.0K 322.8M 4096

Your internal storage was not mounted properly (tmpfs). That's why it is empty after every restart.

Could you please provide your fstab and system information also:

* open the terminal emulator

* become root by the command:

su

(system will ask you to allow root permission. Allow it.)

* take the printout:

cat /fstab.qcom

* take the system and kernel info:

uname -a

* put the results here

---------- Post added at 03:25 PM ---------- Previous post was at 03:23 PM ----------

Please provide the detailed step by step procedure for reproducing the error. How do you clear the data?
[Samsung Galaxy S Duos] :
Can you please add WiFi direct support

I seriously need it to pair with my tv
[Samsung Galaxy S Duos] bknightx3:
here is the results:

u0_a76@kylessopen:/ $ su

root@kylessopen:/ # cat /fstab.qcom

# Android fstab file.

# The filesystem that contains the filesystem checker binary (typically /system) cannot

# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>

/dev/block/mmcblk0p16 /system ext4 ro,barrier=1 wait

/dev/block/mmcblk0p17 /cache ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,journal_async_commit wait,check

/dev/block/mmcblk0p17 /cache f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait

/dev/block/mmcblk0p25 /data ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,journal_async_commit wait,check,encryptable=footer,length=-16384

/dev/block/mmcblk0p25 /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,inline_xattr wait,nonremovable,encryptable=footer

/dev/block/mmcblk0p8 /boot emmc defaults defaults

/dev/block/mmcblk0p12 /recovery emmc defaults defaults

/dev/block/mmcblk0p19 /efs ext4 nosuid,nodev,barrier=1 wait,check

/dev/block/mmcblk0p11 /persist ext4 nosuid,nodev,barrier=1 wait

/dev/block/mmcblk0p22 /hidden ext4 noatime,nosuid,nodev,barrier=1,noauto_da_alloc,journal_async_commit wait

/devices/platform/msm_sdcc.1/mmc_host/mmc1 auto auto defaults voldmanaged=sdcard0:auto

/devices/platform/msm_hsusb_host.0/usb1 auto auto defaults voldmanaged=usbdisk0:auto

/dev/block/zram0 none swap defaults zramsize=134217720

root@kylessopen:/ # uname -a

Linux localhost 3.0.79-klinkone-gab0e0a6 #1 PREEMPT Sat Jan 30 14:49:23 EET 2016 armv7l GNU/Linux

root@kylessopen:/ #
[Samsung Galaxy S Duos] georgedk:
you checked in settings to see if baseband changed to S7562XXLJ3 ?
[Samsung Galaxy S Duos] mysteryno46:
Basedband is XXLJ3.

I flashed CM11 over hungarian firmware. After complete boot I could see only 1 Sim, so I rebooted in Recovery and flash the Modem.zip attached in the post again. It made no changes.

Performance is not as smooth as I expected, but I totally appreciate the CM11 for our device. Finally Relieved now. Waiting for Rc2. :good:

Let me know if I can fix second sim problem anyhow. :confused:

Edit: Second sim issue fixed. I wiped everything again. Flashed everything again and it works now. Did work for first few minutes and then after a while when I unlocked the phone, I could see both sim networks.
[Samsung Galaxy S Duos] georgedk:
I am very pleased with this CM11 ... good battery for me .. changed just min freq to 245.
[Samsung Galaxy S Duos] janir02:
Any new updates in future????
[Samsung Galaxy S Duos] m4jonez:
Im working on it...

Now Im thinking on the Bluetooth driver incompability, but it is another big question.

Sent from my GT-S7562
[Samsung Galaxy S Duos] Orfhen27:
i found bug on performance setting on processor i cant change the value on maximum cpu frequency., but in minimum its stable..

and how to change the the permission set on file manager?. i cant see the file size.. plss response.. tnx
[Samsung Galaxy S Duos] GiannisSma:
The Max freq change but didn't update the setting to see the run mhz. If you see the mhz metter you see the max freq isnt goes up from your choice. For the file manager I suggest to use root explorer find it at playstore.
[Samsung Galaxy S Duos] banerjeeayan1996:
Increasing battery life.....:D:p

PRESS THANKS

REGARDS

banerjeeayan1996
[Samsung Galaxy S Duos] banerjeeayan1996:
Please someone fix the signal speed.

My regular speed is 156b/s when only one sim is activated but it reduces to 56b/s when two sims are activated.

PRESS THANKS

REGARDS

banerjeeayan1996
[Samsung Galaxy S Duos] Orfhen27:
ok thanks @GiannisSma& @banerjeeayan1996 on helping me always.. :good::)

any suggestion or tweaks to make it smooth & fast like cosmic., its kinda bit of laggy here on my phone.. :confused:

i already set the best setting but its laggy and not so smooth like cosmic.. :confused::eek:
[Samsung Galaxy S Duos] banerjeeayan1996:
Then try the init.d scripts from cosmic to this rom and also u can try some build.prop tweaks

PRESS THANKS

REGARDS

banerjeeayan1996

---------- Post added at 07:16 AM ---------- Previous post was at 07:15 AM ----------

PRESS THANKS

REGARDS

banerjeeayan1996

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

PRESS THANKS

REGARDS

banerjeeayan1996
[Samsung Galaxy S Duos] GiannisSma:
Maybe for the ''lag'' you mean the framerate. Check this:
[Samsung Galaxy S Duos] Orfhen27:
already tried this bro., any suggestion??
[Samsung Galaxy S Duos] vermouth22:
I've the same problem :/

no solution :(
[Samsung Galaxy S Duos] Orfhen27:
is it ok to install this?? or stay on default state of rom??., pls response, anyone else tried this??., give me feedback. tnx [AROMA]Script_All-In-One_V5.0_-_CM11_Defy http://xdaforums.com/showthread.php?p=49890173#post49890173
[Samsung Galaxy S Duos] KlinkOnE:
Propably not cause its for a different device. You may also take a look at the s7560m cm11 thread. There may be some questions already answered.http://xdaforums.com/showthread.php?t=2674091

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] Orfhen27:
but it said CM 11:confused:

so any suggestion to make it smooth and faster??:angel:
[Samsung Galaxy S Duos] KlinkOnE:
Be Patient. Wait for the dev to release a new build. Be happy because it is android kitkat.

Gesendet von meinem GT-S7562
[Samsung Galaxy S Duos] Orfhen27:
yup,. :)

thinking of this.. :good::highfive::o:cool:
[Samsung Galaxy S Duos] Aman Dewett:
Xposed

[MENTION=4925018]m4jonez[/MENTION]

Can i use Xposed module with this???
[Samsung Galaxy S Duos] kher paandiyan:
Settings-->Apps-->Downloaded (or) All-->Installed App (or) System App-->Clear Data.
[Samsung Galaxy S Duos] :
Well how can I fix

Google play services

I tried the gapps it was working but some apps like gmail and YouTube says update Google play services on update it crashed

Sent from my GT-S7562
[Samsung Galaxy S Duos] kengnatural:
fstab is OK. Could you please send me /init.qcom.rc file also:

Terminal Emulator

su

cat /init.qcom.rc

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

I think you should just wait a bit until Google Play Services updated. It takes time and some applications using it may crash.

---------- Post added at 06:31 PM ---------- Previous post was at 06:05 PM ----------

I couldn't reproduce this error. Does not happen with my phone.
[Samsung Galaxy S Duos] :
Can you tell which version are you using
[Samsung Galaxy S Duos] kengnatural:
init.qcom.rc is OK. From your printout we can see that your internal memory should be mounted to /data/media. But from your mount printout we see that it mounted to tmpfs. May be there is a problem with permissions of /data/media, may be this directory does not exists. Did you wipe your data also when you flashed this ROM? If not, can you try wiping your data and test (don't forget to take backup first)? What is your working ROM now?
[Samsung Galaxy S Duos] bknightx3:
I already wipe my data. Same problem again.
[Samsung Galaxy S Duos] KlinkOnE:
could you please type the following in terminal and post the result

cat /proc/partitions

---------- Post added at 10:02 AM ---------- Previous post was at 09:07 AM ----------

OP updated with latest build by kengnatural

cm-11-20160207-UNOFFICIAL-kylessopen

latest build Changelog:

•mounting the "hidden" partition disabled

•obsolete start() and startvm() returned back to support xposed again

•fixed soft reboot issue when bluetooth is switched off and user sends some file using it
[Samsung Galaxy S Duos] prajjwal13:
Latest update has xposed installer error
[Samsung Galaxy S Duos] kengnatural:
Are you sure? What do you mean by "latest update"? 20160207?
[Samsung Galaxy S Duos] bknightx3:
[MENTION=5484648]KlinkOnE[/MENTION]

u0_a57@kylessopen:/ $ cat /proc/partitions

major minor #blocks name

253 0 131072 zram0

179 0 3817472 mmcblk0

179 1 20 mmcblk0p1

179 2 150 mmcblk0p2

179 3 20480 mmcblk0p3

179 4 1 mmcblk0p4

179 5 1000 mmcblk0p5

179 6 1000 mmcblk0p6

179 7 2000 mmcblk0p7

179 8 12288 mmcblk0p8

179 9 3072 mmcblk0p9

179 10 3072 mmcblk0p10

179 11 8192 mmcblk0p11

179 12 12288 mmcblk0p12

179 13 4096 mmcblk0p13

179 14 4096 mmcblk0p14

179 15 512 mmcblk0p15

179 16 1228800 mmcblk0p16

179 17 512000 mmcblk0p17

179 18 2048 mmcblk0p18

179 19 12288 mmcblk0p19

179 20 24576 mmcblk0p20

179 21 4096 mmcblk0p21

179 22 51200 mmcblk0p22

179 23 1000 mmcblk0p23

179 24 4096 mmcblk0p24

179 25 1901176 mmcblk0p25

179 32 15558144 mmcblk1

179 33 15554048 mmcblk1p1

u0_a57@kylessopen:/ $
[Samsung Galaxy S Duos] KlinkOnE:
Ok nothing wrong here.

Thanks
[Samsung Galaxy S Duos] kengnatural:
Check your /data and /data/media folder:

su

ls -l /data

ls -l /data/media