yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] glimmling:
Sorry, I've written 4.2.2, but I updated to 4.4.2.

However, cifs mounting worked fine with 4.4. Now I added your options to my command, but that didn't helped:

busybox mount -o username=guest,uid=1023,gid=1023,noperm,iocharset=utf8 -t cifs //192.168.178.23/n7 /data/media/0/mounts/n7

I can see the files after mounting in the terminal as root with:

ls /data/media/0/mounts/n7/*

But none of my apps can see the files as a standard user.

Here is the output of:

mount | grep cifs

//192.168.178.23/n7 /data/media/0/mounts/n7 cifs rw,relatime,sec=ntlm,unc=\\192.168.178.23\n7,username=guest,uid=1023,forceuid,gid=1023,forcegid,addr=192.168.178.23,unix,posixpaths,serverino,acl,rsize=16384,wsize=1048576,actimeo=1 0 0

Gesendet von meinem Nexus 7 mit Tapatalk 4

---------- Post added at 12:05 PM ---------- Previous post was at 11:17 AM ----------

I think, there is something wrong with the patch for the grouper kernel.

I flashed your tilapia kernel on my grouper device and the files in the mounts are visible again. Can you please check the grouper kernel, if the patch is added correctly?

Thank you.

Gesendet von meinem Nexus 7 mit Tapatalk 4
[Nexus 7 Android Development] vorcers:
Please try again with the V10 for grouper. Maybe it failed, because you flashed the version for 4.4.0. They changed the ramdisk in 4.4.2. The kernel is in my zips - as in the original boot.img's exact the same. (md5sum - equal)
[Nexus 7 Android Development] glimmling:
V10 is working for me.

Thank you!
[Nexus 7 Android Development] marianux:
Vorcers, first of all thanks for all these work. Do you have a version of your kernel for the Nexus 7 2013 model ? In case not, could you build it ?, In case not again :), could you tell me where to start ?

Thanks again,

M.
[Nexus 7 Android Development] vorcers:
Sorry, I don't have a 2013 Nexus 7, so - no kernel. I will maybe create an for the nexus 10....

But you maybe use these hints... But you really should know how to compile linux kernels...

First off all, follow this guide: http://source.android.com/source/building-kernels.html ; I also posted on my first post other links I used (for extracting the boot images for example)

Download the https://android.googlesource.com/device/asus/flo-kernel/ git-repo and check out the kitkat-mr1-release branch. (This should be the kernel for 4.4.2)

Download the Factory images for the nexus 7 wifi and 3g versions

Check the boot.img ramdisk and kernel files (not md5sum on the whole file - you need to extract it and check file one by one, e.g. with diff, you also need to extract the ramdisk file) -- because the wifi and 4g ramdisks can differ. An the 2012 nexus 7 we have the SAME (md5-same) kernel but different ramdisks. So you also should check the kernel-images and extracted ramdisk-files.

Extract the kernel config from the kernel in the factory image with extract-ikconfig which is included in the scripts directory of the downloaded kernel source, put it to the kernel source root and name it .config

Apply the patch from makasik and other patches you want, maybe multirom

Run "make oldconfig" to make sure "all options are set".... for example makasik options or the hardboot-options

Run "make menuconfig" to add cifs or other modules to the kernel

Compile kernel with make

Patch the extracted ramdisk (init.rc) with makasik's patch

Pack all together

Be careful about what you need to use in wifi and the 4g Version.... the kernel configs and ramdisks can be different.

But I can also build the kernel for myself, but I can't test it and it could take a long time till it works... Or it could destroy your tablet, because you need to test it for me.I would provide you the zip file and you need to test... :rolleyes:

Good luck!
[Nexus 7 Android Development] marianux:
Thanks a lot. I will keep you updated of my advances. I am planing to put an OpenWRT router in my car in order to provide access to (a lot of) MP3 music. So I thought that CIFS was the natural option to mount a share, as far as I learned in this post, CIFS or mounting in the /sdcard space is not a feature that Android team is thinking to preserve. Do you think that mounting in NFS (or other) would be easier ?

Thanks again,

M.
[Nexus 7 Android Development] vorcers:
No. Android-Stock don't support NFS either.... if you you openwrt, why you don't use an minidlna Server and stream your music with an dlna client? this would also easierer, then Mount it every time....
[Nexus 7 Android Development] chfauc:
Hi vorcers,

does it then work to mount NFS?

I've been trying to mount NFS on my CM10.2 & CM11 with no success (touchpad user).

tx!
[Nexus 7 Android Development] vorcers:
What is an touchpad? if it is your device, I can't help you - my kernel only supports nexus 7 2012 (and in common, only stock Android... no cyanogenmod. With cm only the ramdisk needs to be changed... not the kernel. They removed makasiks init.rc patch in cm.) Please explain your problem in Detail...
[Nexus 7 Android Development] vorcers:
An early warning for Android > 4.4.2

This is something like a warning for you - the warning is: do not update to the successor of Android 4.4.2.

As Chainfire stated in its google+ post, some commits in aosp cause that you can't set the executive bit (x) in /data anymore - but a lot of root apps needs it to run thier scripts. /data *was* a good place for this.

I was interested in this, and I compiled the current master for my tilapia. Chainfire was right. This actually breaks root-apps. Following a log of my app "OneClickMount" (which I have not released yet):

tmp-mksh: <stdin>[8]: /data/data/oneclickmount/files/busybox: can't execute: Permission denied

The output above is from my build of Android > 4.4.2. With 4.4.2 everything works correct.

And - this is the second warning - in my test-build of > 4.4.2 I can not run "setenforce permissive":

|root@tilapia:/sdcard # setenforce permissive
setenforce: Could not set enforcing status: Permission denied

This is very importent, because we relay on this command (see first post) for mounting nfs and cifs correctly - because Kitkat (SELinux) breaks this. This problem can maybe solved by using an lowlevel context - Chainfire implemented an context-change since 1.90 in SuperSU. (-- wait -- or do we ? During the development of OneClickMount I mounted nfs and it worked - without having permissive set - maybe an update of SuperSU fixed this.</guess>)

You have been warned!

Off-Topic: I will try to solve these issues - if they are really happen in an Android Version > 4.4.2 - in OneClickMount - I don't think there is a useful kernel solution - the only thing I can imagine, to do setenforce permissive at boot - with "higher" rights. But this enforcing mode has its "right to exist" - for security reasons...

Screenshot of OneClickMount with mounted nfs (in attachments):
[Nexus 7 Android Development] sgt. meow:
Perhaps the dirtiest fix to the SELinux problem would be disabling it completely (unless KitKat+ somehow detects it and decides not to boot).

OR you could setenforce 0 in the ramdisk and if necessary enforce it at runtime.

This is interesting though.
[Nexus 7 Android Development] vorcers:
Its strange, but today I can do "setenforce Permissive" as root - I don't know why. With this - as expected - selinux prints the errors, but the app is working:

<5>[ 55.801182] type=1400 audit(1390480613.163:13): avc: denied { execute } for pid=1317 comm="sh" name="busybox" dev=mmcblk0p10 ino=114982 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:app_data_file:s0 tclass=file
<5>[ 55.801868] type=1400 audit(1390480613.163:14): avc: denied { execute_no_trans } for pid=1320 comm="sh" path="/data/data/oneclickmount/files/busybox" dev=mmcblk0p10 ino=114982 scontext=u:r:untrusted_app:s0 tcontext=u:object_r:app_data_file:s0 tclass=file

Anyway, I created a little script, which sets SELinux to permissive on boot. It is working on > 4.4.2, and the app is also working again. It is a cwm flashable zip, but you need a kernel with init.d support. If you don't want this anymore, just delete "01_set_selinux_permissive" in /system/etc/init.d. This also works with 4.4.2. (For anyone who as issues with SELinux, for example on writing in cifs-shares).

And again, I don't recommend this. It can open a door for malware. The zip is in the attachments.
[Nexus 7 Android Development] vorcers:
V11 and an hint for tilapia users

I decided to put the kernelmodules from now on in /data, instead of /system. (/data/vorcers_kernelmodules)

I did it, because the modules need ~17mb, and /system doesn't have much space - for other apps is not a lot of space left. For example, I got today 8 kb :eek:

V11 will install the modules in /data and my files in /system/etc/init.d has also been changed. Nothing else is new. Please look into first post for the links.

If you want to delete the kernel modules in /system after the flashing of v11, you can do it yourself with:

mount -o remount,rw /system
rm -rf /system/vorcers_kernelmodules
mount -o remount,ro /system

as root.

Or use your favorite (root) file manager.

Or use this CWM-Flashable zip: CWM_delete_system_vorcers_kernelmodules.zip. The zip does the same as the code above.

---------------------------

And some hint to tilapia users: because I am bugged of the "baseband_xmm_power" wakelock, I flashed the grouper image on my tilapia - this is working flawlessly. This means, you can use with your tilapia, grouper rom's. The only issue: you can't use 3G with that rom. But this is foreseeable I think... If you do, you also need to use the grouper-kernel....
[Nexus 7 Android Development] vorcers:
Version 12 released (Release for Android 4.4.3)

Hey Guys,

If someone is still using my kernel: I just released v12. It is the same kernel as in v11, but with a different ramdisk. (Android 4.4.3 changed the ramdisk)

Please also note, that my kernel is still using the Kernel-Version "3.1.10-g4776c68" (From Android 4.4.0), because Google did not release the actual kernel-branches for Android 4.4.2/4.4.3 in the tegra-kernel archive. ("kitkat-mr2-release", Android 4.4.3 stock kernel is: "3.1.10-g1e42d16")

This will be also my last release, because I don't think the 2012' Nexus 7 will get updates anymore. I will maybe create a updated version, if Google unlocks the tegra-kernel-4.4.3 branch.

In this manner... So long guys!

Have a good life and always fun with Android! :victory:

vorcers
[Nexus 7 Android Development] glimmling:
Thanks!

Do you think, you could release a version with "all-f2fs" support?

My n7 is getting slower and slower. Maybe a fresh start with a better filesystem will help.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] vorcers:
Do you have a specific patch or kernel in mind which sources I can use?
[Nexus 7 Android Development] glimmling:
I'm not sure, how the other devs did it, but there are already some f2fs roms in the "n7 original development" section (slimkat, carbon, omnirom, legokernel...).

The following thread seems to be a good start:

http://xdaforums.com/showthread.php?t=2634271

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] vorcers:
Thank you. I will do what I can, but it can take a while, because I only have time for complex researches on weekend. I will first try to make data-f2fs only and then investigate on all-f2fs.
[Nexus 7 Android Development] glimmling:
Thanks! I can wait. Take the time, you need. :)

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] Monfro:
Thank you very much for your efforts!!

I suggest using only the zimage, like faux or oxydo kernel.

Or you can compile with f2fs drivers and use agnostic flashing tool so the kernel can automatically detect the filesystem used:

http://xdaforums.com/showthread.php?t=2748975

It works very well.
[Nexus 7 Android Development] sgt. meow:
What changes are in the ramdisk? Can I take a peek?
[Nexus 7 Android Development] vorcers:
Version 13 Released

Hey Guys,

as announced, I release today v13, because Google opened the android-tegra3-grouper-3.1-kitkat-mr2 branch for tegra.

I haven't investigated in f2fs yet. But I want to release a f2fs and a non-f2fs Version, so I would have done this release anyway.

What do you mean? From 4.4.2 to 4.4.3? If you mean this, I attached the diff. (for tilapia, but it should be the same...)

I will have a look into this "agnostic" flashing tool. But just replacing the zImage would be useless, because I can't include makasiks patch.
[Nexus 7 Android Development] vorcers:
[Alpha] Kernel with F2FS Support !without! fstab

Hey guys,

I managed it to add the F2FS module to my kernel.

F2FS is working - I formated /cache as F2FS and the system mounted it.

What isn't working: I tried the same with /system. When I tried to restore an twrp backup it failed, because f2fs seems to need more space. (Note: TWRP identifies the filesystem by filename - this means, if you (for example) made a backup of system: system.ext4.win, TWRP formats /system as ext4 and restores the backup. If you rename the file to system.f2fs.win TWRP formats as F2FS.)

Here is the test kernel with F2FS support, but WITHOUT any fstab modifications:

grouper: http://www.mediafire.com/download/c...16-v13.9.1_f2fs_support_without_fstab_mod.zip

tilapia: http://www.mediafire.com/download/3...16-v13.9.1_f2fs_support_without_fstab_mod.zip

I will try it tomorrow again. To make it clear: My problem is, that F2FS seem to need more space. (And I don't want to format /data for the test ^^) I don't know if this is normal. The realistic option is to use only /data with F2FS.

If you want to test it yourself, you can use this to change the fstab. But remember, you will loose your data.

Recovery: I used the multirom recovery. It has in Advanced Wipe a nice option to change the filesystem type and supports F2FS. But remember, if you want to restore old backups, you need to rename them first from ext4 to f2fs.

A last note: This pre-v14 kernel with F2FS Support has no impact on your device, if you don't use f2fs. The kernel has the original grouper/tilapia fstab. No f2fs.
[Nexus 7 Android Development] glimmling:
Thank you for your work.:good:

I've upgraded my N7 to 4.4.3 with your v13 kernel today. All is working well. I will wait a few days before trying to convert /data to f2fs.

Kind regards.
[Nexus 7 Android Development] syamkumar.tpl:
I'm eagerly waiting for all-f2fs for stock ROM..
[Nexus 7 Android Development] glimmling:
Now I've tested your alpha kernel with data-f2fs, but the system did not boot, so I rolled back to ext4.

Maybe I've done something wrong? Here are my steps:

Backup /data in multirom-twrp to usb-otg

Wipe /data and change the filesystem to f2fs with multirom-twrp

Rename the data-nandroid ext4>f2fs

Restore the renamed data-nandroid

Prepare the agnostic-kernel-template.zip with your v14 kernel and flash it in twrp. Output is showing, that data-f2fs is detected and fstab.grouper.data-F2FS is copied to fstab.grouper

Booting the system, but it stucks in bootanimation

Could it have something to do with that?

http://xdaforums.com/showpost.php?p=53170585&postcount=87

Here is something, I've found about the disk usage.

http://xdaforums.com/showpost.php?p=51433509&postcount=1
[Nexus 7 Android Development] glimmling:
Hi vorcers,

I have seen, you edited the first post. V13 is also for 4.4.4. Thank you!

Since I flashed my N7 completely new, it is very responsive and nearly without lags, even without f2fs.
[Nexus 7 Android Development] vorcers:
[V14 Beta 1] Beta F2FS Kernel

Hello Guys,

I finally managed it to create the F2FS-Data-Only Version. ( = the kernel only uses F2FS for /data)

Download for Grouper for Android 4.4.3/4.4.4

Download for Tilapia for Android 4.4.3/4.4.4

It is basically the same as the V13.9.1 Version I posted earlier, but it uses the sepolicy file from legolas93' kernel. (Thanks to him). The sepolicy file was also the reason, why it didn't boot. Since it is a binary, I can't tell you which changes this contains. For F2FS I am using this patches.

Restore your /data files like I described it here or glimmling here. Remember that the recovery don't save/restore the content of /sdcard / /data/media. You need to save and restore this separately. I suggest to use the multirom recovery.

I restored my data completely without any issues. I did a quick test but I couldn't find any issues. I did not tested the performance by the way. You can do this if you want and you can tell us the results. :highfive:

vorcers

PS.: Don't expect anymore updates from me if this F2FS kernel is *really* working and Google doesn't release Android

5.0

(no, I do not call it Android "L") for the Nexus 7 2012.
[Nexus 7 Android Development] glimmling:
As always, thank you very much! :good: It seems, there is now a solution for the empty folders with Chainfires su binary and without the need to patch the kernel. I havn't tried it, but have a look at the links in this post:

http://xdaforums.com/showpost.php?p=53760495&postcount=537
[Nexus 7 Android Development] vorcers:
I tried it, and it is actually really working. You don't need the kernel patch anymore, if you use the SuperSU Option. But the issue that you can't write on cifs is still there.
[Nexus 7 Android Development] vorcers:
If someone is still using my kernel, please post a message. Otherwise I will not update my kernel for Android 5.0 and set the Thread to EOL.
[Nexus 7 Android Development] glimmling:
Hi vorcers. I would use it, because there seems to be no other kernel with cifs support for lollipop. Are you still using your N7?

I don't want you to make the work for just one person.

Btw, I am thinking to replace the N7 with a Sony Xperia Z3 Tablet Compact in the near future.

Thank you!

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] vorcers:
I am still using my nexus. But I still didn't created a new kernel, because Lollipop for the 3g isn't out. I would create the Kernel for myself anyway. If you want to test it, you should be able to create the kernel for grouper. :highfive: But don't expect it to soon. Maybe next weekend, or during the next week.
[Nexus 7 Android Development] glimmling:
Sounds good for me ☺

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] vorcers:
I actually had time and I was able to build it ^^

http://www.mediafire.com/download/drt6ai99bdyr4hv/boot-grouper-vorcers-android-5.0-v15.zip

Can you flash it and tell me if it is working? (Don't forget to to make a backup of your boot partition. ;) )

Includes as always: Multiboot, cifs, nfs, sound modules (I think these aren't working anyway or?), makasiks patch and the /mounts dir. But no f2fs support. I don't know if you are using f2fs... I used my experimental kernel for a few months with data-f2fs... Now again ext4. I can't notice any difference. :rolleyes:
[Nexus 7 Android Development] glimmling:
Perfect! ☺

It works without problems. There is only one small difference to KK. Now I have to set the SE Linux mode to permissive to mount a cifs share. On KK I only needed the permissive mode to have write access. But this is not a problem, I have a toggle shortcut on my homescreen (enforcing <> permissive).

Regarding nfs and the sound modules I can't tell you, if they are working, because I have never used them.

My /data partition is the default ext4. I think, the f2fs thing could be a placebo, because a clean install is always faster ?

Best regards and many thanks for the quick kernel!

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] vorcers:
I am happy that it is working and I could help you. Regarding selinux: this is quite interesting, but I already thought something like that, since selinux is more enforced in lollipop. I will try around a bit, if lollipop is released for tilapia.
[Nexus 7 Android Development] glimmling:
I just tested the SuperSu mounting workaround to compare the behaviour.

su --mount-master -c busybox mount ...

It needs the permissive mode too.

Gesendet von meinem Nexus 7 mit Tapatalk
[Nexus 7 Android Development] unknownprotocols:
Sound modules = maybe USB dac support? I can test, just don't want to waste time reflashing if that isn't what it means.
[Nexus 7 Android Development] glimmling:
I think, it is what you mean:

http://xdaforums.com/showpost.php?p=46920881&postcount=92
[Nexus 7 Android Development] Hotabych:
Thanks for kernel, can you make one with 2f2s support, I can test it.
[Nexus 7 Android Development] vorcers:
This is good to know. I think the mount-master operates down the line with the same environment like makasiks patch. If I would have more time I would investigate in this problem... Also cifs isn't working correctly in my network, it just "hangs"... but this is a problem of my LAN, not the Nexus or my kernel... NFS is working.

glimmling made a good point. Anyway, the sound-dac modules are available with my kernel. Also lollipop should support usb-dac, but I don't know what is needed for this. On Android < lollipop, you also needed to modify the rom. I don't know if it is working in lollipop out-of-the-box. It also depends on the hardware you are using. Maybe it isn't possible with the Nexus 7 2012, because it has not enough power-output. We also need to know, how this usb-dac-thing works in lollipop.

Sorry. Since (at least for me) f2fs made no noticeable difference in performance, I will not support it. This is maybe a bit egoistic, but I don't have so much time for Android hacking anymore... Also using f2fs in an 3.1 Kernel is highly experimental and I was lucky to get it running on Kitkat (f2fs is made for Kernels >= 3.4 (? or was it 3.10, I don't know...)).
[Nexus 7 Android Development] vorcers:
Release of V16 / Android 5.0.2 ## Release of V13-r2 for baseband_xmm_wakelock issues

Hey Guys,

I just released V16 for Lollipop.

There are changes in the use of the kernel related to lollipop.

The changes are:

- CIFS and NFS can't be accessed anymore (read or write) without disabling selinux (USB is still working on enforcing)

- NFS and Sound Modules can't get loaded on boot time anymore

- baseband_xmm_power workaround included for tilapia.

Please look in the first post for more details on the changes above, section "Hints and Bugs since V16 / Android 5.0 / Lollipop".

Android 4.4.4 regarding the baseband_xmm_timeout wakelock (V13-r2)

If you have the baseband_xmm_timeout_wakelock issue on tilapia and you don't want to update to lollipop you can use this kernel:

boot-tilapia-vorcers-g1e42d16-v13_r2-baseband_xmm_power_test_def_0.zip

This kernel disables the wakelock by default completely.
[Nexus 7 Android Development] glimmling:
Thank you for updating!

Since december I have a new device for the daily use (Sony Z3 Tablet Compact?), but I still own my Nexus 7 and will flash your kernel to keep it up to date :)

Gesendet von meinem SGP612 mit Tapatalk
[Nexus 7 Android Development] vorcers:
Hey, have a lot of fun with your new tablet! I hope it works better then the nexus 7 ^^

Thank you, that you are still using my kernel, I think besides me, you are the only one who is still using the kernel... or it feels at least like this. :rolleyes:
[Nexus 7 Android Development] glimmling:
Thanks. The Sony is very fast and has builtin Cifs without the need for root.

I recommended your kernel to a few people to fix their mounting issues. For example here http://xdaforums.com/showthread.php?t=2961875 and in the Cifs Manager app thread.

Gesendet von meinem SGP612 mit Tapatalk
[Nexus 7 Android Development] From_Vanov:
Hi Vorcers,

Thanks for your hard work! Just to let you know, that the link for Tilapia image v16 is incorrect - it points to v13 image instead. And yes, I have flashed the wrong image twice before I realized that :eek:

Regards,

From_Vanov
[Nexus 7 Android Development] vorcers:
Thanks for the advice, I fixed the link!
[Nexus 7 Android Development] mpencexda:
Thanks for the Kernel. I am using it for lolipop and even after setting selinux mode permissive I cannot get cifs to work. Is there something else I need to do. I can see the files via file explorer if opened via cifs manager. Also not able to browse to the mount point /data/media/0 from most apps like bsplayer and such.. Starting to think that cifs is just a lost cause on the newer android releases.