yashsingh1/xdaforums huggingface dataset:
[Nexus 7 Android Development] brainbeatuk:
Re: [KERNEL][WIFI][4.2.X] Included "Fix for empty app-mounted directories"

mount -o bind /mounts/Android/obb /data/media/obb

Have to do this script first then

mount -o bind /mounts/Android/data /data/media/0/Android/data

Managed to save game too, if you get permissions error try this script before mounting in cifs manager

Mount -o remount rw /

(No bind sorry)

I can't download from store games that have obb file for some reason however I have backup of apps so just restored and it reads data and obb file fine, its because I not bind mounted whole card and I have over 20gig of data on a reported 5x gig. Whereas before in storage it showed 1.00 tb on 4.1.2.

Workaround install to internal and cut and paste to smb server then reboot mount up.
[Nexus 7 Android Development] vorcers:
The user moncojoe asked me, if the Kernel is working is also working on the 3g. So I asked him for some Information.

First of all, some uname -a outputs: (3g from him, wifi from me)

3G: Stock with Android 4.2.1

root@android:/system # uname -a
Linux localhost 3.1.10-g22b4fcd #1 SMP PREEMPT Fri Nov 2 10:55:26 PDT 2012 armv7l GNU/Linux

Wifi: Stock with Android 4.2.1

shell@android:/ $ uname -a
Linux localhost 3.1.10-g22b4fcd #1 SMP PREEMPT Fri Nov 2 10:55:26 PDT 2012 armv7l GNU/Linux

They are the same. That surprised me. So I compared the nexus 7 factory images.

Results:

zImage 100% the same --> Extracted Factory Image

bootimg.cfg 100% the same --> Extracted Factory Image

initrd.img seems to differ... but "diff" on the extracted image doesn't give me any output. So, they are the same.

He flashed the Kernel, and he said it worked - but couldn't test 3g. Maybe someone can test it?

But for now, I would say, it is save to use my kernel with the 3g version. I will update the first post.

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

The command "Mount -o bind remount rw /" is (sorry) bull****. First of all, you need two directorys to bind something. I think you mean the command:

mount -o remount rw /

without bind.
[Nexus 7 Android Development] brainbeatuk:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories"

Oh yeah sorry my bad I'll edit. I confused myself yesterday tried so many different lines lol
[Nexus 7 Android Development] spthacker:
Great work!

Any chance you could add otg audio (external audio dac) support to it please :victory:
[Nexus 7 Android Development] vorcers:
I was asked if I can compile the new Android 4.2.2 Kernel. In fact, you can extract every kernel-config with an script located in linux source:

./scripts/extract-ikconfig /tmp/zImage > /tmp/config

So I can compile the kernel now :victory::victory:

As spthacker asked me to include usb-audio-support: There are other wishes to include some modules oder "features" in the kernel?

I consider to include all extra-modules (like nfs and other modules .... ) in the future as .ko modules, not directly included in kernel... So you need to modprobe/insmod the modules by hand. Don't be afraid, I will compile the cifs, utf8 and md5 module directly in the kernel.

A bit off-topic: Does someone get also hangs if you watch video over cifs? This is very annoying.... I couldn't fix this yet. Buffer-Mount-Options like rsize doesn't help.

One"Click"Mount

I am currently develop my first android-app. I make something like a universal-mounter, which supports mount usb and network shares. I am also planning to support the debuggerd method.

Here the first concept:

Well, there are some options in kernel-configuration I can add:

Do you know what else is needed?
[Nexus 7 Android Development] spthacker:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories"

O

I know bugger all to be honest :o

It's what is included in fauxs' Trinity and timurs kernels if that's any help?
[Nexus 7 Android Development] vorcers:
Released v3

I just released Kernel for 4.2.2. See First Post: http://xdaforums.com/showthread.php?t=2107224

I don't know. Maybe you want to install my new kernel and insmod the snd-*.ko modules (from the kernelmodules*.zip) and see if it works?
[Nexus 7 Android Development] spthacker:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories" (v3!)

Say what?

I can barely know what to do with flashing kernels!
[Nexus 7 Android Development] ThurstonX:
Thanks a lot :) Remarkably fast turnaround! I thought I might have to wait a while before moving on to 4.2.2. Good luck with your first app :fingers-crossed:
[Nexus 7 Android Development] vorcers:
Can someone test whether the adb works on 4.2.2 with v3?

I created for you a special kernel, which has the usb-sound modules build-in. See the attachments of this post. Please tell me, if it works.

Thanks :)
[Nexus 7 Android Development] spthacker:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories" (v3!)

I'll download and try flashing after work tonight :D
[Nexus 7 Android Development] spthacker:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories" (v3!)

Usb audio works just great thanks, just gotta find a music player that will see the cifs mounted folder
[Nexus 7 Android Development] ThurstonX:
DeadBeef will see CIFS-mounted folders. I use it to stream from my ReadyNAS.

Now you've got me wondering about USB Audio and how it works. Time for some reading!
[Nexus 7 Android Development] farhanito:
Re: [KERNEL][WIFI+3G][4.2.X] Included "Fix for empty app-mounted directories" (v3!)

I can't seems to insmod any snd-*.ko

Always came up with "no file or directory" errors or something.

lockd and sunrpc.ko loaded fine tho...

EDIT: looks like i need to load them in certain order
[Nexus 7 Android Development] vorcers:
I am currently working on the v4 version of my kernel, which support init.d and can auto-include (modprobe) the modules.
[Nexus 7 Android Development] ThurstonX:
I'm addicted to your kernels now :D

I mainly just wanted it for CIFS support. Can you please explain a little more fully the benefits of v4, when it arrives.

Thanks again for your efforts! Truly appreciated.

Cheers.
[Nexus 7 Android Development] tobiasth:
just a short question, is only the kernel needed for mounting support or is there anything needed to adjust/add inside a custom rom?
[Nexus 7 Android Development] vorcers:
I attached v4. For more Information look at the first post. I am also working hard to make a better One"Click"Mount. It will get something like fstab (to mount cifs and nfs and usb-devices and maybe other...) :highfive: You can follow my development at github: https://github.com/vorcers/oneclickmount

@ThurstonX

If you flash the kernelmodules*.zip at my kernel you will get (currently) also support for nfs and usb-audio. But if someone want some other kernel modules, I will compile and include them.

And v4 includes init.d support via busybox's run-parts.

@tobiasth

To support mounting without hjack debuggerd you just need to flash the kernel - the rom itself don't need to be changed. mkasick modified the mount function of the kernel.

You just need to mount your devices at /data/media/0/ to see them also inside /mnt/sdcard. Android redirects it. Some same does also stickmount. Stickmount runs with debuggerd his mount commands in the same level as the kernels with mkasick's patch. I will post a final statement and how bad stickmount is written in my thread soon: http://xdaforums.com/showthread.php?t=2062768 (The reason why it doesn't work, is that we tried to mount inside of /storage, but we needed to mount inside /data/media/0.) I will post the complete mount script which is in /system/bin/debuggerd written. I need to do it, because chainfire didn't it. I can't understand that... So everyone can use that and there are not only two apps which support mounting in android 4.2. (Soon three, onecklickmount will support the debuggerd method :) )
[Nexus 7 Android Development] brainbeatuk:
Re: [KERNEL][WIFI+3G][4.2.X] Fix for empty app-mounted directories [g05b777c-v4-km-v2

You may know vorcer. What io scheduler would you use for an external hard drive.? Cfq i been guessing and is cache i good idea. Trying to improve datarate when i bindmount cifs folder to sdcard. Oh and you have to mount android/obb folder from external to. Data/media/obb. Then the files appear data/media/0/Android/obb. Fixed compatibility issue i had earlier but i forgot to post.

Is there a way to turn WiFi pm streaming setting off if its enabled? That should improve transfer rate.

Ill try kernel later. Don't fancy editing Motleys nexus 4 kernel too ill test :)

So doing same as I was previously I cannot acheive same results, can't seem to bind mount obb. I get a feeling that my hard drive may be at fault though.
[Nexus 7 Android Development] vorcers:
I just released One"Click"Mount Version 3. Be careful a bit, i didn't tested a lot but everything should work... I removed things and I added things.

Mainly an "fstab" feature... oh and I provided my own ntfs-3g and busybox version. Edit: fstab also supports automounting

@brainbeatuk

thanks for your mounting advice for obb... maybe someone other need this.

but with the io scheduler... I have really no idea. I never thought about that. But I need to investigate some time into kernel-config, because my config differs a lot from stock and I don't know why....
[Nexus 7 Android Development] brainbeatuk:
Re: [KERNEL][WIFI+3G][4.2.X] Fix for empty app-mounted directories [g05b777c-v4-km-v2

In pretty sure that latest build of pa ROM has broke compatibility with this. Was unable to install anything after bindmounting and in storage settings would not change calculation to 1tb again but kept recalculating. Ill try on stock in couple days as i know it worked on stock or carbon
[Nexus 7 Android Development] farhanito:
Re: [KERNEL][WIFI+3G][4.2.X] Fix for empty app-mounted directories [g05b777c-v4-km-v2

I have few mp3s on my network drive. Mounted on /data/media/0/ using cifsmanager.

Media library collected them and google play music played them fine. But streaming stopped whenever screen is off.

This doesn't happen when streamed using DLNA server-client setup.
[Nexus 7 Android Development] flamand:
I'd really appreciate it if someone could help me:

I flashed the v3 kernel. Changed my mount points in cifs manager to /data/media/0/... The first time I go to the folder (in ES), the error "SD Card empty, unmounted or not present" comes up. Not too bad because if I go up one level and then back down, everything appears. My real problem is that I can't play any media nor open any documents. If I copy them to my device it's okay, but not if I'm trying do it over the shares.
[Nexus 7 Android Development] vorcers:
Android 4.3!

Before anyone asks:

Since the Android 4.3 Stock-Images are out, (Link) I am able to build and test the new kernel with the patch.

The kernel source for Android 4.3 should be: https://android.googlesource.com/kernel/tegra.git/+/android-tegra3-grouper-3.1-jb-mr2

But it will take some time, it is done, if it is done. :cool:

Edit: Bad news, google removed the /proc/config.gz file in Android 4.3 on nexus 7... so I will need some more time to get the "original" stock experience + patch.

Edit2: We are lucky, google used CONFIG_IKCONFIG. I attached the original Nexus 7 4.3 Wifi config file.

Edit3: I have been asked to explain this a bit more. (I also made a mistake)

Google didn't used CONFIG_IKCONFIG_PROC, but CONFIG_IKCONFIG. With this option, the config is still stored inside the kernel. In this case, you can extract the .config with the following command, which is included in the kernel-sources / kernel headers:

scripts/extract-ikconfig <linux-kernel-file>

scripts is an sub-directory at the kernel-sources. Linux-kernel-file is the kernel itself. The bzImage or vmlinux or vmlinuz...
[Nexus 7 Android Development] vorcers:
Done!

I released my kernel for Android 4.3, please look into first post for links.

I still have some problems with the kernelmodules (nfs, sound, ...) this will still take some time. But cifs and mounting is fully operational. You can use it.
[Nexus 7 Android Development] ThurstonX:
Thank you! Just installed 4.3 and very happy to be back in business with your kernel and my CIFS mounts :)
[Nexus 7 Android Development] glimmling:
UTF-8 is working fine again with v6.

Thank you for the quick fix! :thumbup:

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[Nexus 7 Android Development] ThurstonX:
suddenly no CIFS

I've been using the latest kernel and the old kernel modules just fine under 4.3, CIFS were auto-mounting. I just rebooted and suddenly my CIFS mounts are empty. I've been using /mounts/<mountpoint>. I didn't change anything between them being visible and now empty.

I'm assuming an app like Mount Manager or CifsManager is needed, at least to define mountpoints, but maybe I'm mistaken in that. If not, how do I go about defining mountpoints? Do I need to edit an init.d script? I ask, because I have not done so in the past.

Is losing the CIFS mounts expected behavior under 4.3? I know you're working on a new set of kernel modules. Any ETA? And most importantly, any idea how to get CIFS to mount again?

Thanks!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

EDIT:

Just rebooted, and now CIFS are showing up under /mounts/<mountpoint> That's how I have Mount Manager set up. I uninstalled CifsManager for now, as I don't want any conflicts.

Now another reboot, and they're empty. It's very strange.
[Nexus 7 Android Development] glimmling:
I think, this is the same issue, I've got with SuperSu v1.51. Try it with SuperSu 1.45. This version is working fine with CIFS for me.

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[Nexus 7 Android Development] ThurstonX:
Ah, interesting. I've been following the SuperSU thread, and Chainfire did mention something about it. What's strange is that sometimes CIFS mount, then reboot, and they're empty. Did you experience that (sometimes empty, sometimes not) under SuperSU 1.51?

I've got SuperSU 1.45 ready-to-flash due to just such issues.

Thanks for the suggestion.
[Nexus 7 Android Development] glimmling:
With v1.51 the mounts were allways empty for me. Mounting with the terminal app resulted in output "device is busy", but it's a SuperSU issue. No problems with v1.45 so far.

Gesendet von meinem Nexus 7 mit Tapatalk 4 Beta
[Nexus 7 Android Development] ThurstonX:
Just wanted to thank you again, and to confirm what you said. At least 1.45 works. My only other question is, is there any way to get into the SuperSU app to adjust settings when running 1.45? My experience is that there isn't, as the app always prompts to update the binary. Once the binary is at 1.51 and the app is accessible, then settings can be made, and 1.45 re-flashed. A bit of a PITA, but worth it to have CIFS access.

Cheers.
[Nexus 7 Android Development] glimmling:
I don't get an autoprompt to update the su binary. Are you sure, the Play Store didn't made an autupdate of the SuperSU.apk after flashing v1.45 in recovery?
[Nexus 7 Android Development] ThurstonX:
Yeah, unfortunately. BUT my testing was done using CleanROM and faux123's kernel. It's possible one of those is forcing it. I tried using SuperSU's uninstaller (from 1.51), which definitely nuked root, and it was not re-installed upon reboot. I had to install the APK from the Play Store, but I flashed 1.45 again. Still got the prompt to update the binary when I went into the app. Did so, as I wanted to change the settings, then flashed 1.45 again. CIFS work, but I can't access the app without getting the binary update prompt.

For the life of me, I can't recall if I tested this on my previous configuration (stock 4.3 + vorcers' kernel). I may not have, having been excited just to have CIFS mounting again. Once I've got the CleanROM + faux123 config set up the way I want it, I'll make a backup in TWRP, then restore my previous config, just to see if I can access SuperSU without the prompt. That backup definitely has 1.45 installed.
[Nexus 7 Android Development] ThurstonX:
After monkeying around with CleanROM and various kernels, I finally got around to restoring my backup of vorcers' kernel + SuperSU 1.45. And like you, SuperSU behaves normally, not prompting me to update the binary, and showing SuperSU Pro 1.45. I don't auto-update apps. I'm funny that way. But when I go to the Play Store, a SuperSU update lists as available. Ignoring for now.

Nice to know I've got a truly stable config to fall back on. Reckon I'll stick with it for now. I've got an HTPC to build! :D
[Nexus 7 Android Development] glimmling:
Good luck with your next project! :fingers-crossed:
[Nexus 7 Android Development] ThurstonX:
Thanks! I can always mess around with the N7 while the OS installs and updates :)

Since we seem to want at least one thing in common from our N7s (i.e., CIFS), have you tried CleanROM (or any other ROM) with vorcers' or faux123's kernels, or any other kernel on stock 4.3? If so, do you have a favorite? I briefly tried M-Kernel (a-59), but it broke root completely. Seems like a real tweakers kernel, and when it moves from 'a' (Alpha) to 'mr' (Milestone Release), it could be fun to mess with.

If so, do you have a preference? Anyway, thanks for your thoughts, if you've the time.

Cheers.
[Nexus 7 Android Development] glimmling:
Oh yes, my preference is actually always a stock rooted ROM. :laugh:

I did some testings with other ROM's on my devices, but always returned to stock, because everything runs smoothly with mostly no bugs.

I prefer vorcers kernel, because it is mostly stock with some great additions and the patch.

On my N7 I have MultiROM by tassadar installed, so I could test an other ROM without touching my current setup. But I did this only two times wit PA and Transporter.

Besides that I have installed the Xposed framework by rovo89. There are some interesting modules to upgrade the features of the stock ROM.

So all in all I'm a very conservative user. ;)

Greetings!

[MENTION=4651935]vorcers[/MENTION]

I hope, we were not to much off-topic in the last posts...:o
[Nexus 7 Android Development] ThurstonX:
Thanks very much for sharing your experience. Gives me some things to explore.

After even my limited experimentation, I find I'm like you: fairly conservative.

And to get this thread back on topic.... vorcers, your kernel is still the best for stability and the very important feature of allowing me to get into SuperSU 1.45 without being prompted to update the damn binary! </end_rant> :silly: Thanks for indulging our OT conversation :D
[Nexus 7 Android Development] YayYouFixedIt:
The v6 4.3 kernel did not seem to work for me. I set up a freenas cifs in a virtualbox on manjaro. The faux123 kernel+the v2 kernel modules seem to be working. I mounted at /data/media/0 at this time fyi. Who needs local storage. Many thanks ;)

Edit: oh i did not see v4 kernel modules. Great job.
[Nexus 7 Android Development] vorcers:
You can't use the v2 modules with the v6 kernel. They are incompatible. Also, if you only use cifs, you don't need the extra kernel modules.

Can you explain the issue you have / had?

The modules only for NFS and some usb sound cards. You can't use them with other kernels - or - it shouldn't work.

Edit: which android version do you have?
[Nexus 7 Android Development] YayYouFixedIt:
Sorry my brain was in tacos. :) I didn't know about NFS so Ive been trying that instead. What happened was 4.3 cm10.2 would not go past the boot animation after installing v6. What actually happened I don't know but it appeared that installing v2 km after installing faux123 caused the cifs share to mount. Not too sure what happened.
[Nexus 7 Android Development] vorcers:
My kernel includes the Mount-Fix. But only for stock-rom. Cyanogenmod already has this fix in Dalvik. On Cyanogenmod, you don't need any part of my kernel at all! And installing my kernel modules would also be useless. You cannot load the modules. That only thing which is possible, that my script loads the NFS-Modules for you with are inside cyanogenmod. I recommend to delete my scripts inside /system/etc/init.d or reflash cyanogenmod. (Only the system, you don't need to factory reset)
[Nexus 7 Android Development] ImGeneralZod:
Help mounting shares on Sony PWS (WGC10/N)

Hello and thank you for making this Kernel.

I have a question and I'm hoping someone can help me. I have a Sony PWS (WGC10/N) with a 128GB SDHC card in it. I cannot get Mount Manager or CIFS Manager to mount the shares on this device. I can use any file explorer (Solid, Root, or EStrongs) to attach and I can even get Dice Player to attach. Below is what I enter and the error message I'm getting. Any help is greatly appreciated.

I'm using the 4.2.2 Kernel v4 with the modules v2 (Note: Mount Manager shows all of the modules loaded from the v2 file)

CIFS Manager:

Share Path: 192.168.40.1/USB

Mount Point: /data/media/0

Username: guest

PW: none

Error message: Mounting the share has failed with an error. Mount: Invalid argument

Mount Manager:

//192.168.40.1/USB

/data/media/0

Mount type: CIFS

User: guest

Error message: no such device or address
[Nexus 7 Android Development] vorcers:
at all

Our workaround seems to be broken with SuperSU 1.50 and there is nothing I can do about that. chainfire implemented the security features...

I will test today cyanogenmod as it has its own Superuser. If it works, I will switch to cyanogenmod. Sorry, guys, this is the end of the road for stock & cifs. At least if you don't want to use the debuggerd Method.

at general

It is a shot in the dark, but I think you have the wrong mount point. You need an directory inside /data/media/0, for example /data/media/0/cifs. I don't know what happens if you mount to /data/media/0. Or if this CAN work.

Hint: if you only want to use cifs, you don't need the kernel modules.
[Nexus 7 Android Development] ThurstonX:
Maybe this is a bad way to do it, but I use SuperSU 1.45 (APK and binary) with this kernel and the latest update (JWR66Y). CIFS works fine. Haven't noticed any other problems. YMMV.

If there's something wrong with the way I'm doing it, I'm all ears. But yes, SuperSU 1.51 breaks CIFS, regardless of kernel, as far as I can tell.
[Nexus 7 Android Development] vorcers:
I recommend to switch superuser.

Today I "found" another superuser, it is "superuser" by koush: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser

It is the same as it is used in cyanogenmod. It works really well, and the folders are not empty :)

Additionally, it is opensource. SuperSU isn't. You don't know which extra-code implemented chainfire in its app...
[Nexus 7 Android Development] ThurstonX:
I should note that I just upgraded SuperSU to 1.55, and it didn't break CIFS with your kernel, like 1.51 did. Just double-checked after booting this morning and it's still working.

It's good to know there's another superuser option. Thanks for sharing your find :)
[Nexus 7 Android Development] vorcers:
I just released v7 (http://www.mediafire.com/download/tcycmd1cgi71fpy/boot-grouper-vorcers-g1e8b3d8-v7.zip) The zip also contains the kernelmodules for nfs and usb-sound. I am too lazy to maintain two packages. As with the original package, the modules get automatically loaded at boot...

Attention: I switched to mediafire...

[MENTION=4925283]ThurstonX[/MENTION]

Thanks, I will test today 1.55 and tell if this works. But I will stay at superuser from koush.

Edit: Nope with 1.55 the mount succeeds, but the folders are empty.
[Nexus 7 Android Development] ThurstonX:
Hmmm, that's interesting. I use /mounts as my base dir, and Mount Manager. Not sure if this matters, but I was using SuperSU 1.45, with all CIFS mounted, then upgraded to 1.55 via the Play Store, and installed the binary via TWRP (per the SuperSU prompt). Two reboots later and still seeing my shares.
[Nexus 7 Android Development] glimmling:
Thanks for the update.

I tried SuperSu v1.55 as well and have also empty folders.

Are there any disadvantages with the other Superuser?

I want to get rid of the Play Store update notification, when staying with SuperSu v1.45

Gesendet von meinem Nexus 7 mit Tapatalk 4