[KERNEL] [15/04/10][5.1/3G+WIFI][Fix for empty directories after mount] [V18]

Search This thread
By:
Advanced…
glimmling

glimmling

Senior Member
Jan 27, 2011
245
109
tuetenmensch.blogspot.com
vorcers said:
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.
Click to expand...
Click to collapse

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
 
vorcers

vorcers

Senior Member
May 21, 2012
158
127
glimmling said:
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
Click to expand...
Click to collapse

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:
 
Last edited:
  • Like
Reactions: Harpratap
glimmling

glimmling

Senior Member
Jan 27, 2011
245
109
tuetenmensch.blogspot.com
vorcers said:
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 using the kernel... or it feels at least like this. :rolleyes:
Click to expand...
Click to collapse

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
 
  • Like
Reactions: vorcers
M

mpencexda

Senior Member
Nov 8, 2010
155
21
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.
 
Last edited:
vorcers

vorcers

Senior Member
May 21, 2012
158
127
mpencexda said:
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.
Click to expand...
Click to collapse

Can you explain your issue in detail? And can you access the files with OI Filemanager ? (I always use this manger for testing) Maybe it is working, but bsplayer doesn't "see" the files, because the media-scanner did not scan the cifs files. Did you try to open an mp3 or movie "manually" in the filemanager?
 
vorcers

vorcers

Senior Member
May 21, 2012
158
127
V18 / Android 5.1 for brave people

Hey Guys,

today I wanted to release V18, but I using for now Android 4.4.4 on my tablet because it has a better battery usage then Android 5.X.

Because I couldn't get the 5.1 rom running in multirom this is a new Version for brave people, because V18 is completely untested.

>= V17 has some changes: theoretically supports f2fs (default ext4, please change your fstab for yourself), nfs is build in, removed sound modules install - the modules are available in the zip.

Downloads:
Stock Android 5.1 - Only For Grouper

Good luck guys, I really don't know why I am still building this kernel. If you want an advice from me: You should maybe switch to carosa-Kernel this Kernel supports the same features as mine... if you not did it already... :confused:
 
Last edited:
  • Like
Reactions: Harpratap and glimmling
vorcers

vorcers

Senior Member
May 21, 2012
158
127
Release of V18 / Android 5.1

Hey Guys,

since Google added the Android 5.1 Tilapia Image, I now "officially" release V18. The kernel is the same build as in the untested version, so, if you flashed the untested grouper v18, you don't need to reflash this again.

As always: Links are in the first post.

vorcers
 
  • Like
Reactions: rezor92, glimmling and motorazrv3
W

williamlaw

Senior Member
Mar 31, 2011
328
10
after flashed, my n7 3g keep loading in logo but never enter os. f2fs is using
please advice.

thanks
 
W

williamlaw

Senior Member
Mar 31, 2011
328
10
how to run the command "echo 0 > /sys/module/baseband_xmm_power/parameters/bb_timeout" ?
From app or an ways ?

Thanks
 
You must log in or register to reply here.

Similar threads

AndDiSa
[ROM][NZH54D][2024/03/05][Asus Nexus 7 2012 WiFi/3G][F2FS/EXT4]Android 7.x AOSP
Replies
5K
Views
1M
R
ridley1000
mskip
[TOOLKIT] SKIPSOFT ANDROID TOOLKIT - NEXUS 7 - Drivers, Root, Recovery + MORE
Replies
2K
Views
2M
mskip
mskip
W
  • Sticky
[Toolkit] Wug's Nexus Root Toolkit v. 2.1.9
Replies
6K
Views
2M
T
tekhtime
Metallice
  • Locked
[KERNEL] M-Kernel [MOVED]
Replies
4K
Views
696K
FReaKRaNT
FReaKRaNT
sgt. meow
[KERNEL] [GPL] [4.3/4.4] [8th June] Oxydo -V18
Replies
1K
Views
275K
M
Mathsl

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 21
    vorcers
    vorcers
    Hey Guys,

    mkasick released in his thread a fix for the mounting problems in Android >= 4.2.

    Description of the issue:
    mkasick said:
    Android >= 4.2 breaks Dalvik-apps that mount file systems to be shared with other apps. This includes CifsManager, Mount Manager, essentially anything that mounts cifs shares, FUSE file sytems, etc. The symptom is that the mounted contents appear fine to app that peforms the mount operation (assuming the app itself provides the ability to browse the contents), but every other app only sees an empty directory at the mount point.
    Click to expand...
    Click to collapse

    As I said - mkasick released a solution - so I compiled my own kernel. Now we can again easy mount cifs and others! All old apps should work. Only limitation: the mount point needs to be outside of /storage (and also /mnt/sdcard/). Fix for this: Mount within /data/media/0 -- android will redirect the mount so you can access the mounted-files from this folders.

    The kernel is a "stock kernel" and also includes:
    • mkasick Patch
    • Built-In cifs, md4, utf8, nfs, f2fs (Since V17)
    • kexec hardboot patch (The full patch, allows boot as host and as guest)
    • As Modules: .ko: snd-usb-audio and all of its devices (Installed, but not modprobe'd since V17)
    • [Since V16/Android 5.0.2] Fix for baseband_xmm_power wakelock on tilapia (see Hints and Bugs since V16 / Android 5.0 / Lollipop ; for Android 4.4.4 see this post)

    mkasick recommends in his thread to patch dalavik, but for the stock-roms it is easier to patch the kernel.


    Known Bugs:
    • Since Android 5.0.X/V16: SELinux is now blocking the access of cifs/nfs even in read. Also nfs isn't loaded at boot time anymore. For more information look below.
    • Since Android 4.4.X: There is a known bug with mounting cifs (you can't write). The solution is (try at your own risk) here. If you want to do this workaround at boot-time, you can flash the zip linked here.
    • With SuperSU >= 1.50 && < 1.65 the mounted folders are empty. Please update! (For more Info see hide-box "SuperSU Information" below)

    Hints and Bugs since V16 / Android 5.0 / Lollipop:

    SELinux, cifs and nfs

    SELinux is since Android 5.0 "more" enforced. Because of that, even the read on nfs / cifs isn't working anymore without disabling selinux by "setenforce permissive" as root. Be careful, disabling selinux is an security hole. USB is still working with selinux at enforcing.

    Because of the same reason the nfs and sound modules are not loaded at boot anymore. Because I don't want to mess around with selinux at boot time, you can modprobe them yourself, if you need it. Run the following commands as root to use nfs / sound modules (a installed busybox is required):

    Activate sound modules:
    Code: 
    busybox modprobe snd-usb-audio

    Activate NFS File System:
    Code: 
    busybox modprobe nfs

    Workaround for baseband_xmm_power wakelock

    Some people have massive issues with tegra3 + cellular devices with the baseband_xmm_power wakelock. The wakelock drains all the battery. With V16 I included a possible fix for this. The fix is based on the work of jfmcbrayer and Sgt. Meow. By default, the fix isn't active and the kernel uses the stock behaviour.

    If you want to disable the wakelock entirely, you can flash this zip: CWM_activate_baseband_xmm_power_wakelock_workaround_vorcers_rev2.zip

    I used this this workaround for some time with Android 4.4.4 and I had no issues. Well, I did not test the mobile data... Please tell me, if something isn't working (And the workaround is active). I just wanted to get rid of that battery drain. I was on flight mode all time.

    Technical:

    The workaround is enabled by echoing a number into a baseband_xmm_power module parameters:
    Code: 
    echo 0 > /sys/module/baseband_xmm_power/parameters/bb_timeout

    Possible Values:
    < 0 - disable workaround, stock behaviour [Default (-1)]
    = 0 - disable the baseband_xmm_power wakelock completely
    > 0 - how long the wakelock can stay active, every time the wakelock is triggered, in 10ths of a second. Meaning: Value 5 = 500 ms, 10 = 1 second, 20 = 2 seconds....

    You find the patch I used in the actual Patchset. (Included since Android 5.0.2)


    Downloads

    (Kernels since v8 are only tested by me for the 3G version (tilapia) - but should also work with wifi (grouper).)

    The flash of the kernel shouldn't break anything, but I recommend to backup your system.

    Download-Links for grouper and tilapia:

    In V11 the kernel modules are placed in /data instead of /system. If you are upgrade from < V11 and you want to delete the modules in /system, you can delete the folder "/system/vorcers_kernelmodules" manually, or you use this CWM-Zip to delete.


    Download-Links only for grouper: (try on tilapia at your own risk)

    Extra-Links:

    Integration wishes for new kernelmodules to support new hardware are always welcome (you will get .ko's for my kernel)

    Have a lot of fun!


    Sources:
    http://xdaforums.com/showthread.php?t=2106480 (Mount fix)
    http://xdaforums.com/showthread.php?t=2104706 (Hardboot patch)
    http://source.android.com/source/building-kernels.html
    http://android-dls.com/wiki/index.php?title=HOWTO:_Unpack,_Edit,_and_Re-Pack_Boot_Images
    http://nek0s.blogspot.de/2012/12/nexus-7-ramdisk.html


    Changelog:

    Android 5.1: gf5d7b8b-v18 (2015/04/10)
    - Switched to gf5d7b8b / android-tegra3-grouper-3.1-lollipop-mr1
    - Build-In nfs
    - Disabled Module auto loading for snd-usb modules -- are still installed
    - Added f2fs Filesystem, untested, standard is ext4

    Android 5.0.2: g6ff7a51-v16 (2015/01/31)
    - Switched to g1e42d16 / android-tegra3-grouper-3.1-lollipop-release
    - Added Workaround for the baseband_xmm_power wakelock on tilapia (Please see "Hints and Bugs since V16 / Android 5.0 / Lollipop" for more information)
    - NFS and Sound Modules are not loaded anymore by default but can loaded manual via "busybox modprobe nfs" / "busybox modprobe snd-usb-audio".

    Android 4.4.4: g1e42d16-v13 (2014/06/06)
    - Switched to g1e42d16 / android-tegra3-grouper-3.1-kitkat-mr2

    Android 4.4.3: g4776c68-v12 (2014/06/03)
    - Updated Grouper and Tilapia ramdisks for Android 4.4.3.

    Android 4.4.2: g4776c68-v11 (2014/01/11)
    - To save space in /system, the kernel-modules had been moved from /system/vorcers_kernelmodules to /data/vorcers_kernelmodules.
    If you want to delete the modules in /system, you can use this zip: CWM_delete_system_vorcers_kernelmodules.zip
    - Nothing else is new

    Android 4.4.2: g4776c68-v10 (2013/12/11)
    - Updated Kernel Config and Ramdisks. (Both changed in Android 4.4.2/KOT49H)

    Android 4.4: g4776c68-v9 (2013/12/10)
    - Created separate files for grouper and tilapia (their ramdisk differ, kernel not)

    Android 4.4: g4776c68-v8 (2013/12/07)
    - Switched to Android 4.4: g4776c68 ; KRT16O (?) ; android-tegra3-grouper-3.1-kitkat-mr1 KRT16S is gee1a0b2 / (?)(?) android-tegra3-grouper-3.1-kitkat-mr0 (?)(?)

    Android 4.3: g1e8b3d8-v7 (2013/09/01)
    - Modules Support for Android 4.3
    - Packed all modules inside zip...
    - I go back to the old version scheme and only count up the numbers...

    Android 4.3: g1e8b3d8-v6 (2013/07/29)
    - Forgot somehow UTF8
    - Really added /proc/config.gz

    Android 4.3: g1e8b3d8-v5-km-v4 (2013/07/25)
    - Switched to Android 4.3: g1e8b3d8 ; jwr66v ; android-tegra3-grouper-3.1-jb-mr2
    - This kernel has also: /proc/config.gz and an loadable module support (Stock has not)
    - I also provided the patchset I used for Android 4.3

    Android 4.2.2: g05b777c-v4-km-v2 (2013/02/19)
    v4-Kernel (boot-grouper-vorcers-g05b777c-v4.zip):
    - Switched to different version schema: boot-grouper-vorcers-<android-kernel-hash>-v<count of changes of kernel (overall)> ; For the kernelmodules it is: kernelmodules-vorcers-<android-kernel-hash>-v<count of changes of kernel-modules (overall)>. This means for you: if the number is higher, there is something new :D Version-Number at Changelog: <android-kernel-hash>-v<count of changes of kernel (overall)> -km-v<count of changes of kernel-modules (overall)>
    - Added init.d (/system/etc/init.d/) support to the kernel/init.rc. If the directory exists, the scripts inside the directory get run via "run-parts" from busybox. This means: The script need to be runable (+x) and mustn't have an file-extension.
    - Removed the mount of /mounts out of init.rc (is now in an script called by init.rc)
    v2-Kernelmodules (kernelmodules-vorcers-g05b777c-v2.zip):
    - Made a CWM flashable package which autoloads the modules in my kernel.

    Android 4.2.1: v3 - boot-grouper-4.2.2-vorcers-v3.zip : (2013/02/15)
    - Switched to Android 4.2.2 - Kernel, jdq39, g05b777c, android-tegra3-grouper-3.1-jb-mr1.1
    - Added Modules for OTG-USB-Sound (see kernelmodules*.zip)
    Android 4.2.0: v2 (2013/01/19)
    - I added a tmpfs mount for /mounts, so you don't need to do "mount -o remount rw /" and create your inital-mountpoint yourself. /mounts is writeable by all apps. (done in init.rc)
    Android 4.2.0: v1 (2013/01/19)
    - inital release


    SuperSU Information:

    Information for SuperSU Users

    It seemed that SuperSU >= 1.50 && < 1.65 doesn't work correctly with this kernel. Well, the Version 1.65 seems to work again (The folders where empty after mount). The SuperSU Version 1.45 worked the best. If you want to use 1.45, you can download the old Flashable-Version here: http://download.chainfire.eu/343/SuperSU/UPDATE-SuperSU-v1.45.zip.

    As I said, the version 1.65 seems to work again. It maybe can happen, that the folders gets empty, after some time. This has been noticed with Version 1.60. But 1.65 not (yet).

    If you still have problems with the empty folders on my kernel, you should try superuser by koush.

    koush's superuser is opensource and is the same as in cyanogenmod. And with that, the mount-technique is working without bugs: https://play.google.com/store/apps/details?id=com.koushikdutta.superuser



    Some gimmick: One"click"mount-Shell-Script

    Because I want to get rid of stickmount, I written a little shell-script to mount all connected devices. It is very similar to stickmount, but it supports: ext, fat32, ntfs. Well, ntfs only, if you provide the path to an ntfs-3g binary. (In the variable NTFS_BINARY) I used in the script the paragon-ntfs binary. Just install the Paragon-App.

    Download V2.2: http://www.mediafire.com/download/rjmsdt06cf0cp6b/oneclickmountv22.sh.gz
    Download V3: http://www.mediafire.com/download/xppx2m3awcf3oq3/oneclickmount-v3-20130221172223.tar.gz

    glimmling created a tasker apk for this script. I but it still bases on v11 of the script.

    • from v3 on, ocm needs -m parameter. If you want the old behavior, use "-m auto"
    • from v3 on, ocm also mounts /dev/block/sdX partitons (e.g. /dev/block/sda), but only if my script can use a busybox with blkid with TYPE output. (I provided one)
    • I added in v3 an fstab-like future usable with -f <file> see my example.
    • Please be careful with the new v3. I works, but I would call it "beta"...
    • You can't run ocm >= v3 inside /mnt/sdcard. All files (except for ocm.fstab and ocm-library) need the x right. Copy the files too /data/local/, "chmod 777 *" them and run ocm from /data/local.
    example for ocm.fstab.
    syntax:
    Code: 
    <device> <mountpoint> <fs-type> <options>
    example:
    It is is very importent that the options seperated by one space!
    Code: 
    //192.168.100.1/username username cifs username=<username>,password=password,ro
192.168.100.1:/home/username nfs nfs nolock,ro
/dev/sda1 sda1 ntfs

    Thanks to:
    mkasick - for the patch
    farhanito - for the basic code in the .zip
    glimmling - for the tasker apk's running the One"click"mount-Shell-Script
    jfmcbrayer / Sgt. Meow - for the baseband_xmm_power wakelock workaround
    View
    5
    vorcers
    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
    View
    4
    vorcers
    vorcers
    I just released v8 for Android 4.4 and everything seems to work.... :victory:

    Download: http://www.mediafire.com/download/48xo4axdd2dpwnh/boot-grouper-vorcers-g4776c68-v8.zip



    I tested cifs-mounting in /mounts/, OI Filemanager and mxplayer where able to access the files.... I did that with SuperSU 1.80.

    I used with this kernel the newer kernel sources, https://android.googlesource.com/kernel/tegra/+/android-tegra3-grouper-3.1-kitkat-mr1

    I think these are the sources for KRT16O / Android 4.4.1... but it also works with KRT16S.
    View
    3
    vorcers
    vorcers
    Release of V18 / Android 5.1

    Hey Guys,

    since Google added the Android 5.1 Tilapia Image, I now "officially" release V18. The kernel is the same build as in the untested version, so, if you flashed the untested grouper v18, you don't need to reflash this again.

    As always: Links are in the first post.

    vorcers
    View
    3
    vorcers
    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 :) )
    View

New posts